For Something Will Be Lost

Enabling SNMP on ESX

SNMP di ESX secara default disable , untuk mensetting dan mengenable kan nya berikut stepnya:

1. snmpconf -i

Tampilan yang akan muncul :
                The following installed configuration files were found:

                                1:  ./snmpd.conf

                                2:  /usr/share/snmp/snmpd.conf

                Would you like me to read them in?  Their content will be merged with the

                output files created by this session.

                Valid answer examples: “all”, “none”,”3″,”1,2,5″

                Read in which (default = all):

Kemudian pilih : all

Tampilan yang akan muncul :

                I can create the following types of configuration files for you.

                Select the file type you wish to create:

                (you can create more than one as you run this program)

                   1:  snmpd.conf

                   2:  snmptrapd.conf

                   3:  snmp.conf

                Other options: quit

Kemudian pilih : 1

                The configuration information which can be put into snmpd.conf is divided

                into sections.  Select a configuration section for snmpd.conf

                that you wish to create:

                    1:  Access Control Setup

                   2:  Extending the Agent

                   3:  Monitor Various Aspects of the Running Host

                   4:  Agent Operating Mode

                   5:  Trap Destinations

                   6:  System Information Setup

                Other options: finished

Kemudian pilin : 6

                Select from:

                   1:  The [typically physical] location of the system.

                   2:  The contact information for the administrator

                   3:  The proper value for the sysServices object.

                Other options: finished, list

Kemudian pilih : 1

                The location of the system: esx1.agit.com

Kemudian pilih : 2

                The contact information: ryo.fadzrin@ag-it.com

Kemudian finished

                The configuration information which can be put into snmpd.conf is divided

                into sections.  Select a configuration section for snmpd.conf

                that you wish to create:

                 1:  Access Control Setup

                  2:  Extending the Agent

                   3:  Monitor Various Aspects of the Running Host

                   4:  Agent Operating Mode

                   5:  Trap Destinations

                   6:  System Information Setup

                Other options:

Kemudian pilih : 1

Akan muncul

                Select from:

                   1:  a SNMPv3 read-write user

                   2:  a SNMPv3 read-only user

                   3:  a SNMPv1/SNMPv2c read-only access community name

                  4:  a SNMPv1/SNMPv2c read-write access community name

                Other options: finished, list

Kemudian pilih : 3

akan muncul

                Configuring: rocommunity

                Description:

                a SNMPv1/SNMPv2c read-only access community name

                arguments:  community [default|hostname|network/bits]

                 The community name to add read-only access for: sera (sesuai dengan nama community yang di inginkan)

                The hostname or network address to accept this community name from [RETURN for all]:

                The OID that this community should be restricted to [RETURN for no-restriction]:

Langkah sudah selesai, jalankan perintah finished sampai keluar

                Select File: quit

                Error: An snmpd.conf file already exists in this directory.

                ‘overwrite’, ‘skip’, ‘rename’ or ‘append’? : overwtite

Langkah selanjutnya :

2. /etc/init.d/snmpd start

3. /etc/init.d/snmpd status

4. snmpwalk -v 1 -c sera localhost

5.chkconfig snmpd on

6.esxcfg-firewall –e snmpd

VMware VirtualCenter service does not start automatically after reboot

1. Click Start > Run.
2. Type services.msc and press Enter.
3. Locate any services that VirtualCenter requires. For example, SQLEXP_VIM or ADAM_VCMSDS.
4. Open the service properties and note the Service Name. For example, MSSQL$SQLEXP_VIM .
5. In the Run dialog, type Regedit.exe and press Enter. Browse to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\vpxd.
6. Double-click the DependOnService key and add the Service name using the name identified in step 4.
7. Close Regedit.
8. Go back to the Services window and open the service properties for the service identified in step 3.
9. On the Dependencies tab, verify the VMware VirtualCenter service is listed as depending on the service.
10. Repeat steps 3 to 9 for any services that VirtualCenter requires.

how to fix if your vm orphaned in inventory

If one of your virtual machines become orphaned do the following to get it online. follow this step to solved the problem

1.Launch Virtual Center or Virtual Client
2.Right click on the orphaned virtual machine
3.Select ‘Remove from Inventory’
4.Now select the host that you would like the VM to reside on
5.Then click on the Configuration Tab
6.Under the Hardware Pane located on the left, click on Storage
7.You should see on the right all the Datastores
8.Now double click on the Datastore where the Virtual Machine VMX file resides, this will launch the ‘Datastore Browser’
9.Now locate the VMX file.
10.Right click on the file and choose ‘Add to Inventory’
11.Go through the wizard and your Virtual Machine should appear online again.

Deploy windows 2003server menggunakan template, dengan vcenter diatas windows 2008

sempet bingung juga dimana yah lokasi file sysprep untuk vcenter yg running di atas windows 2008,kutak-katik , cari sana-sini akhirnya ketemu juga. file location nya berada pada C:\ProgramData\VMware\VMwareVirtualCenter\sysprep. copy file deploy.cab dari installer CD windows 2003, lalu extract ke dalam C:\ProgramData\VMware\VMwareVirtualCenter\sysprep, selesai dan template siap di gunakan dengan menggenerated SID baru

Installing Vmware Vcenter prerequisit on windows 2008 R2

there is a 32-bit option, so vCenter has no trouble installing; however, once things move in the 64-bit direction, there are two items that you’ll need to address before the vCenter installation will be successful:

• The need for the .NET Framework 3.5.1.
• The need for a 32-bit Database Source Name (DSN)/ODBC connection pointing to the vCenter database.

Important notes
Before we proceed, you should be aware of these important product and article notes: 

• Although VMware indicates that small organizations can safely run vCenter on a 32-bit OS, it recommends that administrators consider 64-bits for all new installations.

 

• If you’re installing vCenter on a virtual machine running under vSphere/ESX 4, you should know that support for Windows Server 2008 R2 is currently experimental. Even though everything will probably work just fine, VMware won’t provide support if you have problems.
• This article assumes that you have already followed VMware’s guidance as outlined in the documentation and created a database and database user for vCenter. For my purposes, I created a database named VCDB and a SQL Server account named vcenteruser.
• Bear in mind that VMware does not yet support vCenter on Windows Server 2008 R2. Proceed at your own risk!

.NET Framework 3.5.1
To install the .NET Framework 3.5.1 on Windows Server 2008 R2, follow these steps:

1. Open Server Manager.
2. Select the Features navigation item.
3. On the Feature Summary page, click Add Features.
4. When you get to the Select Features page of the wizard, expand the .NET Framework 3.5.1 Features option.
5. Select the .NET Framework 3.5.1 item. (Do not choose to install both the .NET Framework 3.5.1 and WCF Activation together–doing so will force the installation of IIS 7.5, which will interfere with vCenter’s Web services.) Figure A shows you the Select Features window.
6. Click the Next button.
7. On the Confirm Installation Selections page, click the Install button to complete the process.

32-bit DSN to the vCenter database
When you create a DSN on an out-of-the-box Windows Server 2008 R2 system, the DSN is created as a 64-bit object, whereas the vCenter installer will only be looking for 32-bit DSNs. In order to create a 32-bit DSN on your 64-bit Windows Server 2008 R2 server, you need to download and install the SQL Server Native Client on your server and use the new client’s utilities to create the DSN. For this article, I’m using SQL Server 2005 because that is what we’re using in production at Westminster College.

The SQL Server Native Client is included as a part of the SQL Server 2005 Feature Pack. From the Feature Pack download page, download the X64 package under the SQL Server 2005 Native Client option. Although you’re installing the 64-bit package, this is only because you’re installing the tool to a 64-bit operating system; the package includes a method to create 32-bit DSNs. Once you download the package, install it.

Next, go to Start and, in the Search box, type odbcad32. Select the odbcad32 option under the Programs heading to run this utility.

This is a 32-bit version of the ODBC Data Source Administrator utility; in this utility, create a System DSN that points to your vCenter database. To do so, follow these steps:

1. Select the System DSN tab.
2. Click the Add button.
3. On the first page of the Create New Data Source wizard, choose SQL Native Client.
4. When prompted, provide a name and description of the new System DSN and indicate on which SQL Server the vCenter database resides.
5. For my example, I’ve used SQL Server authentication. On the authentication page, choose the authentication method most appropriate for your use. If you use SQL Server authentication, use the same login ID and password that you created as per the VMware documentation. This page is shown in Figure C
6. When prompted, test the data source to make sure it’s set up properly

figure C

When you’re done, you will see the vCenter DSN appear in the ODBC Data Source Administrator.

Summary
With these two items in place, your vCenter installation should proceed without interruption. The true test will come when you get to the installation step that asks you to provide the 32-bit DSN that you want to use for the vCenter database. If you’ve set the DSN up properly that DSN will be available to you; if it’s not set up properly, make sure that you didn’t accidentally create a 64-bit DSN.