configure snmp on an esxi host

Configure SNMP for ESXi
based on this www

http://pubs.vmware.com/vsphere-50/topic/com.vmware.vsphere.monitoring.doc_50/GUID-8EF36D7D-59B6-4C74-B1AA-4A9D18AB6250.html

numbers in brackets indicate the step is optional

0
download and install the vsphere cli to desktop - from the vcli command prompt:

1
Display snmp agent configuration
**********
vicfg-snmp.pl --server esxi001.domain.com -s
**********
C:\>vicfg-snmp.pl --server esxi001.domain.com -s
Enter username: root
Enter password:
Current SNMP agent settings:
Enabled  : 0
UDP port : 161
Communities :
Notification targets :
Options :
EnvEventSource=indications

2
Configure SNMP Communities
**********
vicfg-snmp.pl --server esxi001 --username root --password Secret!! -c public1
**********
C:\>vicfg-snmp.pl --server esxi001 --username root --password Secret!! -c public1
Changing community list to: public1...
Complete.
C:\>vicfg-snmp.pl --server esxi001.domain.com -s
Enter username: root
Enter password:
Current SNMP agent settings:
Enabled  : 0
UDP port : 161
Communities :
public1
Notification targets :
Options :
EnvEventSource=indications

3
If the SNMP agent is not enabled, enable it by typing
**********
vicfg-snmp.pl --server esxi001 --username root --password Secret!! --enable
**********
C:\>vicfg-snmp.pl --server esxi001 --username root --password Secret!! --enable
Enabling agent...
Complete.
C:\>vicfg-snmp.pl --server esxi001.domain.com -s
Enter username: root
Enter password:
Current SNMP agent settings:
Enabled  : 1UDP port : 161
Communities :
public1
Notification targets :
Options :
EnvEventSource=indications

4
Configure the SNMP Agent to Send Traps
**********
vicfg-snmp.pl --server esxi001 --username root --password Secret!! -t solarwinds.domain.com@162/public1
**********
C:\>vicfg-snmp.pl --server esxi001 --username root --password Secret!! -t solarwinds.domain.com@162/public1
Changing notification(trap) targets list to: solarwinds.domain.com@162/public1...
Complete.

5
Send a test trap to verify that the agent is configured correctly by typing
**********
vicfg-snmp.pl --server esxi001 --username root --password Secret!! --test
**********
C:\>vicfg-snmp.pl --server esxi001 --username root --password Secret!! --test
Sending test nofication(trap) to all configured targets...
Complete. Check with each target to see if trap was received.

(6)
Configure the SNMP Agent for Polling (- not necessary - already done by default)
**********
vicfg-snmp.pl --server esxi001 --username root --password Secret!! -p 161
**********
C:\>vicfg-snmp.pl --server esxi001 --username root --password Secret!! -p 161
Changing udp port to 161...
Complete.

C:\>vicfg-snmp.pl --server esxi001.domain.com -s
Enter username: root
Enter password:
Current SNMP agent settings:
Enabled  : 1
UDP port : 161
Communities :
public1
Notification targets :
solarwinds.domain.com@162/public1
Options :
EnvEventSource=indications

(7)
Configure the Source used by the SNMP Agent for Hardware Events (- not necessary - already done by default)
**********
for vsphere4
vicfg-snmp.pl --server hostname --username username --password password -y sensors
for vsphere5
vicfg-snmp.pl --server esxi001 --username root --password Secret!! -y indications
**********
C:\>vicfg-snmp.pl --server esxi001 --username root --password Secret!! -y indications
Changing source of hardware event source: indications...
Complete.
C:\>vicfg-snmp.pl --server esxi001.domain.com --username root --password Secret!! -s
Current SNMP agent settings:
Enabled  : 1
UDP port : 161
Communities :
public1
Notification targets :
solarwinds.domain.com@162/public1
Options :
EnvEventSource=indications

8

Configure SNMP Management Client Software

After you have configured a vCenter Server system or a host to send traps, you must configure your management client software to receive and interpret those traps.

http://pubs.vmware.com/vsphere-50/topic/com.vmware.vsphere.monitoring.doc_50/GUID-D025D87A-E7E5-4747-995B-6FC3BB213B0F.html

(9)
Configure the SNMP Agent to Filter Traps
vicfg-snmp.pl --server hostname --username username --password password -n oid_list

From the vSphere CLI, vicfg-snmp.pl --server hostname --username username --password password -n oid_list
oid_list is a list of OIDs for the traps to filter, separated by commas. This list replaces any OIDs that were previously specificed using this command.
For example, to filter out coldStart (OID 1.3.6.1.4.1.6876.4.1.1.0) and warmStart (OID 1.3.6.1.4.1.6876.4.1.1.1) traps, type vicfg-snmp.pl --server hostname --username username --password password -n 1.3.6.1.4.1.6876.4.1.1.0,1.3.6.1.4.1.6876.4.1.1.1
To clear all trap filters, typevicfg-snmp.pl --server hostname --username username --password password -n reset

free vsphere tools and utilites

Flings
http://labs.vmware.com/

Top 10 Free Tools that must be in every VMware Administrators toolkit
http://vsphere-land.com/top-10-list/top-10-free-tools-that-must-be-in-every-vmware-administrators-toolkit.html

A List of FREE VMware vSphere Tools
http://kendrickcoleman.com/index.php/Tech-Blog/a-list-of-free-vmware-vsphere-tools.html

Top 10 Free VMware vSphere Tools and Utilities for 2011
http://www.kendrickcoleman.com/index.php/Tech-Blog/top-10-free-vmware-vsphere-tools-and-utilities-for-2011.html

VM Advanced ISO. Free Tools For Advanced Tasks
http://www.kendrickcoleman.com/index.php/Tech-Blog/vm-advanced-iso-free-tools-for-advanced-tasks.html

Foglight for Virtualization, Free Edition
http://www.quest.com/foglight-for-virtualization-free-edition/

vmware tools install upgrade error how to force uninstall

force uninstall of vmtools / vmware tools

mount the vmtools cdrom in the vm using VM -> Guest -> Install / Upgrade VMware Tools - choose interactive install

from the VM command prompt cd to the cdrom drive and run the command
setup64 /c
this does the uninstall - no reboot needed

then run setup64 (from gui) to reinstall
error when trying to upgrade = isolation.tools.guestInitiatedUpgrade.disable = "FALSE"

service mgmt-vmware stop start restart -ash: service: not found - Usage: /etc/init.d/hostd {start|stop|restart}

KB: 2030663

~ # service mgmt-vmware restart
-ash: service: not found

~ # /etc/init.d/hostd status
Usage: /etc/init.d/hostd {start|stop|restart}
~ # ps -s | grep hostd
16978 16978 hostd-worker         WAIT   UFUTEX 0-31 hostd
16979 16978 hostd-poll           WAIT   UPOL   0-31 hostd
16980 16978 hostd-worker         WAIT   USLP   0-31 hostd17006 16978 vix-high-p           WAIT   UPOL   0-31 hostd
17007 17007 nssquery             WAIT   UPIPER 0-31 /usr/libexec/hostd/nssquery
17008 16978 hostd-worker         WAIT   UFUTEX 0-31 hostd
17010 16978 hostd-worker         WAIT   UFUTEX 0-31 hostd
17011 16978 hostd-worker         WAIT   UFUTEX 0-31 hostd17087 16978 vix-poll             WAIT   UPOL   0-31 hostd
17275 16978 hostd-worker         WAIT   UFUTEX 0-31 hostd
17390 16978 hostd-worker         WAIT   UFUTEX 0-31 hostd
17506 16978 hostd-worker         WAIT   UFUTEX 0-31 hostd

~ # /etc/init.d/vpxa status
-ash: /etc/init.d/vpxa: not found

~ # ps -s | grep vpxa
16987 16987 vpxa                 WAIT   UFUTEX 0-31 /opt/vmware/vpxa/vpx/vpxa
16997 16987 vpxa                 WAIT   UPOL   0-31 /opt/vmware/vpxa/vpx/vpxa
16998 16987 vpxa                 WAIT   USLP   0-31 /opt/vmware/vpxa/vpx/vpxa
16999 16987 vpxa                 WAIT   UFUTEX 0-31 /opt/vmware/vpxa/vpx/vpxa
17001 16987 vpxa                 WAIT   UFUTEX 0-31 /opt/vmware/vpxa/vpx/vpxa
17002 16987 vpxa                 WAIT   UFUTEX 0-31 /opt/vmware/vpxa/vpx/vpxa
17003 16987 vpxa                 WAIT   UFUTEX 0-31 /opt/vmware/vpxa/vpx/vpxa
17004 16987 vpxa                 WAIT   UFUTEX 0-31 /opt/vmware/vpxa/vpx/vpxa
17005 16987 vpxa                 WAIT   UFUTEX 0-31 /opt/vmware/vpxa/vpx/vpxa
17271 16987 vpxa                 WAIT   UFUTEX 0-31 /opt/vmware/vpxa/vpx/vpxa
17278 16987 vpxa                 WAIT   UFUTEX 0-31 /opt/vmware/vpxa/vpx/vpxa
17279 16987 vpxa                 WAIT   UFUTEX 0-31 /opt/vmware/vpxa/vpx/vpxa
17282 16987 vpxa                 WAIT   UFUTEX 0-31 /opt/vmware/vpxa/vpx/vpxa
17293 16987 vpxa                 WAIT   UFUTEX 0-31 /opt/vmware/vpxa/vpx/vpxa
17294 16987 vpxa                 WAIT   UFUTEX 0-31 /opt/vmware/vpxa/vpx/vpxa
17295 16987 vpxa                 WAIT   UFUTEX 0-31 /opt/vmware/vpxa/vpx/vpxa
17296 16987 vpxa                 WAIT   UFUTEX 0-31 /opt/vmware/vpxa/vpx/vpxa
17297 16987 vpxa                 WAIT   UFUTEX 0-31 /opt/vmware/vpxa/vpx/vpxa

great post on how to change vmnic numbering

http://www.virten.net/2012/09/esxi-change-vmnic-vmhba-numbering/


cp /etc/vmware/esx.conf /etc/vmware/esx.conf.old

vi /etc/vmware/esx.conf

Search for “vmnic” (press /vmnic<ENTER>)
press n for next occurance and N for previous.

/device/000:000:26.0/owner = "vmkernel"
/device/000:000:29.0/owner = "vmkernel"
/device/000:000:31.2/vmkname = "vmhba0"
/device/000:001:00.0/vmkname = "vmnic0"
/device/000:001:00.1/vmkname = "vmnic1"
/device/000:001:00.2/vmkname = "vmnic2"
/device/000:001:00.3/vmkname = "vmnic3"
/device/000:001:00.4/vmkname = "vmnic4"
/device/000:001:00.5/vmkname = "vmnic5"
/device/000:003:00.0/vmkname = "vmnic6"
/device/000:003:00.1/vmkname = "vmnic7"
/device/000:067:00.0/vmkname = "vmhba1"
/device/000:068:00.0/vmkname = "vmhba2"

Change the vmnic label. (Move the cursor to the label, press r for “replace” and enter the new number)


Search again for “vmnic” (press /vmnic<ENTER>) until you find something like this

/net/pnic/child[0000]/duplex = "full"
/net/pnic/child[0000]/mac = "90:b1:1c:0f:7a:fb"
/net/pnic/child[0000]/name = "vmnic0"
/net/pnic/child[0000]/speed = "10000"
/net/pnic/child[0000]/virtualMac = "00:50:56:5f:7a:fb"
/net/pnic/child[0001]/duplex = "full"
/net/pnic/child[0001]/mac = "90:b1:1c:0f:7a:fd"
/net/pnic/child[0001]/name = "vmnic1"
/net/pnic/child[0001]/speed = "10000"
/net/pnic/child[0001]/virtualMac = "00:50:56:5f:7a:fd"
/net/pnic/child[0002]/mac = "90:b1:1c:0f:7a:ff"
/net/pnic/child[0002]/name = "vmnic2"
/net/pnic/child[0002]/virtualMac = "00:50:56:5f:7a:ff"
/net/pnic/child[0003]/mac = "90:b1:1c:0f:7b:01"
/net/pnic/child[0003]/name = "vmnic3"
/net/pnic/child[0003]/virtualMac = "00:50:56:5f:7b:01"
/net/pnic/child[0004]/mac = "90:b1:1c:0f:7b:03"
/net/pnic/child[0004]/name = "vmnic4"
/net/pnic/child[0004]/virtualMac = "00:50:56:5f:7b:03"
/net/pnic/child[0005]/mac = "90:b1:1c:0f:7b:05"
/net/pnic/child[0005]/name = "vmnic5"
/net/pnic/child[0005]/virtualMac = "00:50:56:5f:7b:05"

Move the cursor to the line and press dd for each line you want to delete.

reboot

configuring LLDP and cdp

esxcfg-vswitch vSwitch0 -b
shows current status - which is listen

esxcfg-vswitch vSwitch0 -B both
sets esx host to broadcast and listen

use
esxcli network vswitch standard set -c both -v vSwitch0
for esxi5


command to run on the switch:

show lldp info remote-device



thanks to http://rickardnobel.se/vswitch-cdp-with-hp-switches/

echo to stdout all the commands in a script

put this at the top of the file
#!/bin/bash -x

for esxi
#!/bin/ash -x

Configuring networking from the ESX service console KB 1000258

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1000258

change uplink / nic settings from the command line - esxcfg-nics

esxcfg-nics -l
esxcfg-nics -s 100 -d full vmnic0

esxi5
esxcli network nic set -n vmnic# -S speed -D duplex

maintenance mode cli

maintenance mode cli esxi4 & 5


vim-cmd hostsvc/maintenance_mode_enter

vim-cmd hostsvc/maintenance_mode_exit

Network/Storage firmware and recommended driver version in ESXi/ESX 4.x and 5.x - VID DID SVID and SDID

KB: 1027206
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1027206
Determining Network/Storage firmware and driver version in ESXi/ESX 4.x and 5.x

******************
EXTRACT for NIC
To determine the recommended driver for the card, we must obtain the Vendor ID (VID), Device ID (DID), Sub-Vendor ID (SVID), and Sub-Device ID (SDID) using the vmkchdev command:
# vmkchdev -l |grep vmnic0
002:01.0 8086:100f 15ad:0750 vmkernel vmnic0
In this example, the values are:

◦VID = 8086
◦DID = 100f
◦SVID = 15ad
◦SDID = 0750
5.You can now search the VMware Compatibility Guide for the Vendor ID (VID), Device ID (DID), Sub-Vendor ID (SVID), and Sub-Device ID (SDID). In some cases, you may need to do a text search to narrow down the particular card.

******************

Resolution
Note: In ESXi 5.x, the swfw.sh command is supplied with the vm-support support bundle collection tool. The swfw.sh command can be used to identify the firmware and driver versions of hardware connected to the host. To run this command, use this path:
# /usr/lib/vmware/vm-support/bin/swfw.sh

Obtaining Host Bus adapter driver and firmware information
To determine the driver and firmware version of a Host Bus Adapter:
•To determine the firmware version of a Host Bus Adapter, see Identifying the firmware of a Qlogic or Emulex FC HBA (1002413).

•To obtain the driver version of a Host Bus Adapter on an ESXi/ESX host:

1.Open a console to the ESXi/ESX host. For more information, see Unable to connect to an ESX host using Secure Shell (SSH) (1003807) or Using Tech Support Mode in ESXi 4.1 and ESXi 5.x (1017910).

2.Obtain the driver type that the Host Bus Adapter is currently using:
# esxcfg-scsidevs -a
You see output similar to:
vmhba0  ata_piix   link-n/a  ide.vmhba0    (0:7.1) Intel Corporation Virtual Machine Chipset
vmhba1  mptspi     link-n/a  pscsi.vmhba1  (0:16.0) LSI Logic / Symbios Logic LSI Logic Parallel SCSI Controller
vmhba32 ata_piix   link-n/a  ide.vmhba32   (0:7.1) Intel Corporation Virtual Machine Chipset
Note: The second column shows the driver that is configured for the HBA.

3.To view the driver version in use, run the command:
# vmkload_mod -s HBADriver |grep Version
For example, to check the mptspi driver:
# vmkload_mod -s mptspi |grep Version
Version: Version 4.00.37.00.30vmw, Build: 721907, Interface: 9.0, Built on: May 18 2012
In this example, the driver version is 4.00.37.00.30vmw.
To obtain the driver version for all HBAs in the system with a single command, use:
# for a in $(esxcfg-scsidevs -a |awk '{print $2}') ;do vmkload_mod -s $a |grep -i version ;done

4.To determine the recommended driver for the card, we must obtain the Vendor ID (VID), Device ID (DID), Sub-Vendor ID (SVID), and Sub-Device ID (SDID) using the vmkchdev command:
# vmkchdev -l |grep vmhba1
000:16.0 1000:0030 15ad:1976 vmkernel vmhba1
In this example, the values are:

■VID = 1000
■DID = 0030
■SVID = 15ad
■SDID = 1976
To obtain vendor information for all HBAs in the system using a single command:
# for a in $(esxcfg-scsidevs -a |awk '{print $1}') ;do vmkchdev -l |grep $a ;done

5.You can now search the VMware Compatibility Guide for the Vendor ID (VID), Device ID (DID), Sub-Vendor ID (SVID), and Sub-Device ID (SDID). In some cases, you may need to do a text search to narrow down the particular card.
Note: You can check the ESXi/ESX host version with the command:

# vmware -v
Obtaining Network card driver and firmware information
To determine the version information for a physical network interface card in vSphere ESXi/ESX 4.x and 5.x:

1.Open a console to the ESXi/ESX host. For more information, see Unable to connect to an ESX host using Secure Shell (SSH) (1003807) or Using Tech Support Mode in ESXi 4.1 and ESXi 5.x (1017910).

2.Obtain a list of network interface cards and names.
In ESXi/ESX 4.x, run this command:
# esxcfg-nics -l
For example:
# esxcfg-nics -l
Name    PCI         Driver Link Speed    Duplex MAC Address
vmnic0  00:02:04.00 ACME   Up   1000Mbps Full   01:23:45:67:89:AB
vmnic1  00:02:05.00 ACME   Up   1000Mbps Full   01:23:45:67:78:AC
In ESXi 5.x, run this command:
# esxcli network nic list

3.Use the ethtool -i command to display available information for one of the network interfaces, specifying its name from step 2:
# ethtool -i VMNic_name
For example:
# ethtool -i vmnic0
driver: ACME
version: 1.2.3a-1vmw
firmware-version: 7.8.9
bus-info: 0000:02:04.00
To obtain information from ethtool -i for all network adapters at once, you can run the following command:
for a in $(esxcfg-nics -l|awk '{print $1}'|grep [0-9]) ;do ethtool -i $a;done

4.To determine the recommended driver for the card, we must obtain the Vendor ID (VID), Device ID (DID), Sub-Vendor ID (SVID), and Sub-Device ID (SDID) using the vmkchdev command:
# vmkchdev -l |grep vmnic0
002:01.0 8086:100f 15ad:0750 vmkernel vmnic0
In this example, the values are:

◦VID = 8086
◦DID = 100f
◦SVID = 15ad
◦SDID = 0750
To obtain vendor information for all NICs in the system using a single command:
# for a in $(esxcfg-nics -l |awk '{print $1}' |grep [0-9]) ;do vmkchdev -l |grep $a ;done

5.You can now search the VMware Compatibility Guide for the Vendor ID (VID), Device ID (DID), Sub-Vendor ID (SVID), and Sub-Device ID (SDID). In some cases, you may need to do a text search to narrow down the particular card.
Note: You can check the ESXi/ESX host version with the command:
# vmware -v

6.From both the ESXi/ESX version and the network type, you then know the version of the driver to use. Any driver updates are available on the VMware downloads page.

ESXi4 mount idrac iso and update nic drivers vmkload_mod

Driver versions Before:
~ # vmkload_mod -s bnx2x | grep Version
 Version: Version 1.72.54.v41.1, Build: 00000, Interface: ddi_9_1 Built on: May  9 2012
~ #
~ # vmkload_mod -s cnic | grep Version
 Version: Version 1.72.50.v41.1, Build: 00000, Interface: ddi_9_1 Built on: May  2 2012
~ # vmkload_mod -s bnx2i | grep Version
 Version: Version 2.72.10.v41.2, Build: 00000, Interface: ddi_9_1 Built on: Apr  2 2012
~ # vmkload_mod -s bnx2 | grep Version
 Version: Version 2.2.1l.v41.1, Build: 00000, Interface: ddi_9_1 Built on: Apr 19 2012
~ #
Driver versions After:
~ # vmkload_mod -s bnx2x | grep Version
 Version: Version 1.74.22.v41.1, Build: 00000, Interface: ddi_9_1 Built on: Dec 20 2012
~ # vmkload_mod -s cnic | grep Version
 Version: Version 1.74.04.v41.3, Build: 00000, Interface: ddi_9_1 Built on: Dec 20 2012
~ # vmkload_mod -s bnx2i | grep Version
 Version: Version 2.74.07.v41.1, Build: 00000, Interface: ddi_9_1 Built on: Sep 6 2012
~ # vmkload_mod -s bnx2 | grep Version
 Version: Version 2.2.3e.v41.1, Build: 00000, Interface: ddi_9_1 Built on: Aug 28 2012
~ #


To update or add drivers on existing ESX installations using esxupdate:
   (for ESX only)
1. Power on the ESX host and log into an account with administrator capability.
2. Place the driver CD in the CD-ROM drive of the ESX host.
3. Mount the driver CD.
4. Navigate to <cd mount point>/offline-bundle/ and locate the
   <offline-bundle>.zip file.
5. Run the esxupdate command to install drivers using the offline bundle.
   esxupdate --bundle=<offline-bundle>.zip update

dev # vmkload_mod iso9660
Module iso9660 loaded successfully
/dev # ls /dev/cdrom
mpx.vmhba40:C0:T0:L0                  vml.0005000000766d68626134303a303a30
mpx.vmhba42:C0:T0:L0                  vml.0005000000766d68626134323a303a30
/dev # /sbin/vsish -e set /vmkModules/iso9660/mount mpx.vmhba40:C0:T0:L0
VSISHCmdSet():Set failed: Not supported
/dev # /sbin/vsish -e set /vmkModules/iso9660/mount mpx.vmhba42:C0:T0:L0
/dev # ls -al /vmfs/volumes/cdrom
ls: /vmfs/volumes/cdrom: No such file or directory
/dev # ls -al /vmfs/volumes/CDROM
lrwxr-xr-x    1 root     root                 20 May  3 17:57 /vmfs/volumes/CDROM -> mpx.vmhba42:C0:T0:L0
/dev # cd /vmfs/volumes/CDROM
/vmfs/volumes/mpx.vmhba42:C0:T0:L0 # ls
DOC          DRIVERS.XML  OFFLINE_     SOURCE       TRANS.TBL    _RPM


/vmfs/volumes/mpx.vmhba42:C0:T0:L0 # ls
DOC          DRIVERS.XML  OFFLINE_     SOURCE       TRANS.TBL    _RPM
/vmfs/volumes/mpx.vmhba42:C0:T0:L0 # cd OFFLINE_/
/vmfs/volumes/mpx.vmhba42:C0:T0:L0/OFFLINE_ # pwd
/vmfs/volumes/CDROM/OFFLINE_
/vmfs/volumes/mpx.vmhba42:C0:T0:L0/OFFLINE_ # esxupdate --bundle=BCM_B000.ZIP update
Unpacking cross_vmware-esx-dr.. ######################################## [100%]
Removing packages :vmware-esx.. ######################################## [100%]
Installing packages :cross_vm.. ######################################## [100%]
Running [vmkmod-install.sh]...
ok.
Running [/sbin/esxcfg-secpolicy -p /etc/vmware/secpolicy]...
ok.
The update completed successfully, but the system needs to be rebooted for the
changes to be effective.
/vmfs/volumes/mpx.vmhba42:C0:T0:L0/OFFLINE_ #