VMware/ESX

VMware ESXi
See VMware ESXi

Reference 1
What does ESX stand for? 


 * ESX is an acronym for Elastic Sky X
 * GSX is an acronym for Ground Storm X

Both names were confirmed by VMware employee JMills in this thread: http://communities.vmware.com/thread/20538

Source: vmfaq.com - What does ESX stand for?

Reference 2
ESX = Elastic or Electric Sky

GSX = Ground Sky

"early days west coast cali hippy advertising thinking from the boys in the states. They dont mean't anything and the X was added for acromyn :)"

Source: Abbreviation ESX

Reference 3
"I thought ESX was named by someone who could spell or had dyslexia - and was meant to be SEX!"

Source: Abbreviation ESX

Reference 4
"As the story goes, the founders of the product coined the names when they were students (hippies) at Berkley. You figure out the rest."
 * --jasonboche

Source: [http://www.petri.co.il/forums/showthread.php?t=15206 What does ESX stand for? - Petri.co.il forums by Daniel Petri]

Reference 5
"Today, I saw an article on acronyms on Yellow-Bricks which reveals the secret. Furthermore, there's a link to a video interview with Mike DiPetrillo which elaborates on the matter (about 21:30)


 * ESX: Elastic Sky X
 * GSX: Ground Storm X

The two names was invented by some marketing people hired by VMware. VMware didn't like it too much so they shortened it to ES and GS and the X was added just to make it sound more technical!"

Source: Virtual Infrastructure Tips - VMware: What does ESX stand for? - http://www.vi-tips.com/2010/08/what-does-esx-stand-for.html

"Of course the big question is where the “X” comes from in ESX, GSX etc. To be honest I don’t know but according to VMware old-timer Mike Di Petrillo (source is this interview (21:30) by Rodney Haywood) the X had been added by an Engineer to make it sound technical and cool!"

Source: VMware related acronyms » Yellow Bricks - http://www.yellow-bricks.com/2010/07/29/vmware-related-acronyms/?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed:+YellowBricks+%28Yellow+Bricks%29&utm_content=Netvibes

"Lastly Mike discusses the feature of VMware that he thinks is just way cool, after all he has been working with virtualization for longer than most of us. Also Mike reveals how ESX got its name. Do you know what the three letters stand for?"

Source: Musings of Rodos: Mike DiPetrillo from VMware talks Cloud - http://rodos.haywood.org/2010/04/mike-dipetrillo-from-vmware-talks-cloud.html (VIDEO)

COS
Service Console OS (COS)

The ESX userspace environment, known as the "Service Console" (or as "COS" or as "vmnix"), derives from a modified version of Red Hat Linux, (Red Hat 7.2 for ESX 2.x and Red Hat Enterprise Linux 3 for ESX 3.x). In general, this Service Console provides management interfaces (CLI, webpage MUI, Remote Console). This VMware ESX hypervisor virtualization approach provides lower overhead and better control and granularity for allocating resources (CPU-time, disk-bandwidth, network-bandwidth, memory-utilization) to virtual machines, compared to so-called "hosted" virtualization, where a base OS handles the physical resources. It also increases security.

NFS Mount
esxcfg-nas -a newpu -o newpu -s /home/esx

Service Console
???

Switch Interace: esxcfg-vswif -a vswif33 -p "private cos" -i 192.168.200.10 -n 255.255.255.0

Service Console: esxcfg-vmknic --add --ip=DHCP --netmask=255.255.255.0 "Service Console"

Managed Object Browser (MOB)
The MOB is a Web-based server application hosted on all ESX hosts and vCenter Server systems. The MOB lets you explore the objects on the system and obtain information about available properties and methods. It’s a great tool for investigating server-side objects and for learning about the VMware Infrastructure object model. 

https:// /mob

Enable SSH Access

 * 1) Press Alt-F1 to access the console
 * 2) Login as a 'root' at the console
 * 3) Edit /etc/ssh/sshd_config
 * 4) * vi /etc/ssh/sshd_config
 * 5) Navigate to the line saying PermitRootLogin no and  change it to Yes.
 * 6) * PermitRootLogin Yes
 * 7) Restart SSH service:
 * 8) * service sshd restart

References:
 * How to activate root SSH access in ESX 4.0 | ESX Virtualization

Log files
ESX Server host agent log – /var/log/vmware/hostd.log – Contains information on the agent that manages and configures the ESX Server host and its virtual machines (Search the file date/time stamps to find the log file it is currently outputting to). /var/log/vmware/hostd.log

NOTE: hostd.log also contains the build and version number

Service Console – /var/log/messages – This log is the log from the Linux kernel (service console), which is generally only potentially useful in the case of a host hang, crash, authentication issue, or 3rd party app acting up. This log has NOTHING to do with virtual machines. The SERVICE CONSOLE (red hat kernel) has NO awareness of the VMs (worlds) running on the VMKERNEL. /var/log/messages

esx.conf

vpxa.log

Which ESX log file | VMwarewolf

/var/log/messages - only COS related things (not very useful) /var/log/vmkernel - good log of vm startup and storage usage, and other errors /var/log/vmware/hostd.log - very verbose log of systems messages

Build Numbers
ESX 3.5.0 Update 1 = Build 64607 ESX 3.5.0 Update 2 = Build 110268 ESX 3.5.0 Update 3 = Build 123630 ESX 3.5.0 Update 4 = Build 153875 ESX 3.5.0 Update 5 = Build 207095

ESX 4.0 = Build 164009 - Released 21 May 2009 ESX 4.0 Update 1 = Build 208167 - Released 19 Nov 2009 ESX 4.0 Update 2 = Build 261974 - Released 10 June 2010

ESX 4.1 = Build 260247 - Released 13 July 2010

References:
 * VMware ESX 3.5 Update to Build Number ~ What the
 * VMware ESX 4 Update to Build Number ~ What the
 * VMware ESX 4.1 Update to Build Number ~ What the

Maintanance Mode
Below is the command which you will have to execute from SVC Console to enter host into maintenance mode

vimsh -n -e /hostsvc/maintenance_mode_enter

To exit maintenance mode

vimsh -n -e /hostsvc/maintenance_mode_exit

Now next question is how I check whether host is in maintenance mode.Here is it…

vimsh -n -e /hostsvc/runtimeinfo | grep inMaintenanceMode | awk '{print $3}'

Source: How to set ESX Host into maintenance mode from Service console « Lets Design, Implement and do Administration of ESX3 - http://vmzare.wordpress.com/2007/08/24/how-to-set-esx-host-into-maintenance-mode-from-service-console/

PXE Install
References:
 * PXE Boot and Kickstart ESX Installer | Tyler Lesmann - http://www.tylerlesmann.com/2009/mar/14/pxe-boot-and-kickstart-esx-installer/
 * VMware Communities: PXE Kickstart of ESX 3.0.1 problems - http://communities.vmware.com/message/509320
 * VMware Communities: ESX 3.0 deploying host using RIS - http://communities.vmware.com/message/466174

Get VMware Version
vmware -v VMware ESX 4.1.0 build-260247 VMware ESXi 4.1.0 build-260247

vmware -l VMware ESX 4.1.0 GA   VMware ESXi 4.1.0 GA

cat /etc/issue   # ESX only VMware ESX 4.1 (Kandinsky)

/proc/vmware/version   # ESX only VMware ESX 4.1.0 [Releasebuild-260247], built on May 18 2010 vmklinux        Version 4.1, Build: 260247, Interface: ddi_9_1 Built on: May 18 2010 ...

vimsh -n -e 'hostsvc/hostsummary' | grep fullName   # ESX only fullName = "VMware ESX 4.1.0 build-260247",

References:
 * VMware KB: Determining VMware Software Version and Build Number - http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=392
 * VMware Communities: how to check esx version from command... - http://communities.vmware.com/message/1162223

Removing Password Requirements
VMware KB: ESX and ESXi 4.x password requirements and restrictions - http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1012033

ESX 4.0
/etc/pam.d/system-auth-generic

password  required   /lib/security/$ISA/pam_passwdqc.so   min=8,8,8,7,6 similar=deny match=0 password  required   /lib/security/$ISA/pam_passwdqc.so   min=0,0,0,0,0 similar=deny match=0 password  required   pam_cracklib.so try_first_pass retry=3 password  required   /lib/security/$ISA/pam_passwdqc.so   min=8,8,8,7,6 similar=deny match=0 enforce=none
 * 1) Change the line:
 * to:
 * or
 * 1) or - my favorite:

ESX 4.1
/etc/pam.d/system-auth password       required        /lib/security/$ISA/pam_passwdqc.so          min=8,8,8,7,6 similar=deny match=0 # to password        required        /lib/security/$ISA/pam_passwdqc.so          min=8,8,8,7,6 similar=deny match=0  enforce=none
 * 1) change

To ensure changes persist across reboots: chmod +t /etc/pam.d/system-auth

partitions
To view disks and partitions fdisk -l

Device UID
SCSI disk devices are found here: /vmfs/devices/disks/

Options: -l|--list                 List all Logical Devices known on this system with device information.

-c|--compact-list          List all Logical Devices each on a                             single line, with limited information.

List disk devices: (includes Device UID, and a whole lot of other information) esxcfg-scsidevs -l

List disk devices in compact form: (includes Device UID, Device Type, Console Device and Size) esxcfg-scsidevs -c

Megaraid example: mpx.vmhba1:C0:T0:L0 Size: 208854 MB  Display Name: Local MegaRAID Disk (mpx.vmhba1:C0:T0:L0) Console Device: /vmfs/devices/disks/mpx.vmhba1:C0:T0:L0 Devfs Path: /vmfs/devices/disks/mpx.vmhba1:C0:T0:L0 Vendor: MegaRAID Model: LD 0 RAID1  208G  Revis: 413G SCSI Level: 2 Is Pseudo: false Status: on ...

ATA Example: t10.ATA_____HDS722516VLSA80_______________________________VN6DMRCDFHDJBE Device Type: Direct-Access Size: 152590 MB  Display Name: Local ATA Disk (t10.ATA_____HDS722516VLSA80_______________________________VN6DMRCDFHDJBE) Plugin: NMP Console Device: /vmfs/devices/disks/t10.ATA_____HDS722516VLSA80_______________________________VN6DMRCDFHDJBE Devfs Path: /vmfs/devices/disks/t10.ATA_____HDS722516VLSA80_______________________________VN6DMRCDFHDJBE Vendor: ATA      Model: HDS722516VLSA80   Revis: V34O SCSI Level: 5 Is Pseudo: false Status: on ...

Fusion-io example: mpx.vmhba1:C0:T0:L0 Device Type: Direct-Access Size: 307610 MB  Display Name: Local VMware Disk (mpx.vmhba1:C0:T0:L0) Console Device: /dev/fio/c0d0 Devfs Path: /vmfs/devices/disks/mpx.vmhba1:C0:T0:L0 Vendor: VMware   Model: Block device      Revis: 1.0 SCSI Level: 2 Is Pseudo: false Status: on

vmhba
Option: -a|--hbas                 Print HBA devices with identifying information

List HBAs: esxcfg-scsidevs -a

Fusion-io example: vmhba4 iomemory-vsl      link-n/a  block.fio/c1d1:0                        (0:5:0.0) Adapter for iomemory-vsl Adapter for iomemory-vsl

match hba to disk device
Option: -A|--hba-device-list      Print a mapping between HBAs and the devices it                            provides paths to.

esxcfg-scsidevs -A # hbas to device uid

Fusion-io example: vmhba4     mpx.vmhba4:C0:T1:L0

esxcfg-scsidevs
esxcfg-scsidevs -l # full list esxcfg-scsidevs -c # compact list (device uid, console device, size) esxcfg-scsidevs -a # hbas esxcfg-scsidevs -A # hbas to device uid

esxcfg-scsidevs Print the mappings between vmhba names and /dev names -l|--list                 List all Logical Devices known on this system with device information. -c|--compact-list          List all Logical Devices each on a                           single line, with limited information. -u|--uids                 List all Device Unique Identifiers with their primary name. -d|--device               Used to filter the --list, --compact-list and uids commands to limit output to a                          specific device. -m|--vmfs                 Print mappings for VMFS volumes to their Service Console partitions and vmhba names. -f|--vfat                 Print mappings for VFAT volumes to their Service Console partitions and vmhba names. -a|--hbas                 Print HBA devices with identifying information -A|--hba-device-list      Print a mapping between HBAs and the devices it                           provides paths to. -o|--offline-cos-dev      Offline the COS device corresponding to this vmkernel device. -n|--online-cos-dev       Bring online the COS device corresponding to this vmkernel device. -h|--help                 Show this message.

Add Disk to VM
Standard disk: 75,76c75,80 < scsi0.present = "FALSE" < scsi0:0.present = "FALSE" --- > scsi0.present = "TRUE" > scsi0:0.present = "TRUE" > scsi0.sharedBus = "none" > scsi0.virtualDev = "pvscsi" > scsi0:0.fileName = "/vmfs/volumes/4e3c68af-77789258-cb02-1cc1def3ece6/test.vmdk" > scsi0:0.deviceType = "scsi-hardDisk"

Independent and persistent disk: scsi0.present = "FALSE" scsi0:0.present = "FALSE"

scsi0.present = "TRUE" scsi0:0.present = "TRUE" scsi0.sharedBus = "none" scsi0.virtualDev = "pvscsi" scsi0:0.fileName = "/vmfs/volumes/fio0/test.vmdk" scsi0:0.mode = "independent-persistent" scsi0:0.deviceType = "scsi-hardDisk"

NAS
Network Attached Storage (NFS)

Add NAS: esxcfg-nas -a -o newpu -s /home/esx newpu

[root@esx41 ~]# esxcfg-nas -a -o newpu -s /home/esx newpu Connecting to NAS volume: newpu newpu created and connected.

[root@esx41 ~]# esxcfg-nas -l newpu is /home/esx from newpu mounted

NAS Errors
[root@esx41 ~]# esxcfg-nas -a -o newpu -s /home/esx newpu Connecting to NAS volume: newpu Unable to connect to NAS volume newpu: Unable to mount, no VMkernel TCP stack found

Solution: Add VMkernel interface

---

[root@esx41 ~]# esxcfg-nas -a -o newpu -s /home/esx newpu Connecting to NAS volume: newpu Unable to connect to NAS volume newpu: Unable to complete Sysinfo operation. Please see the VMkernel log file for more details.

Solution: Target is on other network, give VMkernel a default gateway

---

[root@esx40 ~]# esxcfg-nas -a -o newpu -s /home/esx newpu Connecting to NAS volume: newpu Unable to connect to NAS volume newpu: Unable to resolve hostname newpu

Solution: DNS Resolution error. Check name or add missing nameservers.

Change Network IP Address
See current ip with: esxcfg-vswif -l

Set hostname in /etc/sysconfig/network and then: hostname [HOSTNAME] service network restart

Static IP Address: /etc/sysconfig/network GATEWAY=10.0.0.1

/etc/hosts 10.0.0.100 myesxserver.mydomain.com myesxserver

hostname myesxserver.mydomain.com

esxcfg-vswif -i 10.0.0.100 -n 255.255.255.0 vswif0
 * 1) this will read and set the gateway from /etc/sysconfig/network


 * 1) service network restart  # not needed

Dynamic IP Address: /etc/sysconfig/network # GATEWAY=10.0.0.1

/etc/hosts # 10.0.0.100 myesxserver.mydomain.com myesxserver

esxcfg-vswif -i DHCP vswif0


 * 1) service network restart  # not needed

References:
 * VMware KB: Changing the IP address, default gateway, and hostname of the Service Console in ESX - http://kb.vmware.com/kb/4309499

ESX Networking Files
Sample from a ESX 4.0 DHCP system - Service Console:

The system's hostname is 'esx3', but I can't figure out where this is configured in the system, must be coming from DHCP!

/etc/hosts: 127.0.0.1 localhost
 * 1 localhost

/etc/sysconfig/network: NETWORKING=yes HOSTNAME=localhost IPV6_AUTOCONF=no NETWORKING_IPV6=no

/etc/sysconfig/network-scripts/ifcfg-vswif0: DEVICE=vswif0 HOTPLUG=yes MACADDR=00:50:56:42:bb:77 ONBOOT=yes PORTGROUP="Service Console" BOOTPROTO=dhcp DHCLIENT_IGNORE_GATEWAY=yes DHCPV6C=no IPV6INIT=no IPV6_AUTOCONF=no PEERDNS=yes

---

Sample from a hard coded and DHCP ESX 4.1 system - Service Console(s):

/etc/hosts: 127.0.0.1      localhost
 * 1            localhost

10.50.47.105   bossy.oeey.com bossy

/etc/sysconfig/network: NETWORKING=yes HOSTNAME=bossy IPV6_AUTOCONF=no NETWORKING_IPV6=no GATEWAY=10.50.44.1

/etc/sysconfig/network-scripts/ifcfg-vswif0: (not sure how, but able to connect to this interface, even though not default gw) DEVICE=vswif0 MACADDR=00:50:56:4e:25:22 ONBOOT=yes PORTGROUP="Service Console" BOOTPROTO=dhcp DHCLIENT_IGNORE_GATEWAY=yes DHCPV6C=no IPV6INIT=no IPV6_AUTOCONF=no PEERDNS=no

/etc/sysconfig/network-scripts/ifcfg-vswif0: (primary static interface) DEVICE=vswif1 MACADDR=00:50:56:45:8c:c7 ONBOOT=yes PORTGROUP="Service Console 2" BOOTPROTO=static BROADCAST=10.50.44.255 DHCPV6C=no IPADDR=10.50.44.94 IPV6INIT=no IPV6_AUTOCONF=no NETMASK=255.255.255.0

VMkernel Networking
esxcfg-vswitch -l esxcfg-vmknic -l esxcfg-route -l
 * 1) List:

esxcfg-vswitch vSwitch0 -L vmnic0
 * 1) Tie physical interface as virtual switch uplink

esxcfg-vswitch vSwitch0 --add-pg="VMkernel" esxcfg-vmknic -a -i 10.50.43.228 -n 255.255.255.0 "VMkernel"   # vmk0 esxcfg-route 10.50.43.1
 * 1) Add Static

esxcfg-vswitch vSwitch0 --add-pg="VMkernel" esxcfg-vmknic -a -i DHCP "VMkernel"   # vmk0 esxcfg-vmknic -l # to see what address was assigned
 * 1) Add DHCP

esxcfg-nas -a newpu -o newpu -s /home/esx
 * 1) NFS Mount:

esxcfg-vmknic -d "VMkernel" esxcfg-vswitch vSwitch0 --del-pg="VMkernel"
 * 1) Remove:

List Virtual Switches: esxcfg-vswitch -l

List VMkernel interfaces: esxcfg-vmknic -l

List default route for VMkernel: esxcfg-route -l

Add VMkernel interface: esxcfg-vmknic --add --ip=DHCP --netmask=255.255.255.0 "Service Console"

Set the VMkernel default gateway: esxcfg-route 192.168.0.1 esxcfg-route -a default 192.168.0.1

Physical NICs
List physical network interfaces: esxcfg-nics -l

Virtual Switches
List virtual switches: esxcfg-vswitch -l

Create a new virtual switch: esxcfg-vswitch –a vSwitch1

Add a new portgroup to the virtual switch: esxcfg-vswitch –A "Some Group" vSwitch1

Up-link vmnic1 to the new virtual switch with the command: esxcfg-vswitch –L vmnic1 vSwitch1

References:
 * Configuring networking from the ESX service console command line - http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1000258

vmkernel
List vmkernel network interfaces, MAC addresses and IP addresses: esxcfg-vmknic -l
 * 1) vmk0

List vmkernel routes and default gateway: esxcfg-route -l

Virtual Switch Interface
Note: ESX ONLY

Change IP address: 1. set default gateway in /etc/sysconfig/network with 'GATEWAY=10.0.0.1' 2. set IP with: # esxcfg-vswif -i 10.0.0.100 -n 255.255.255.0 vswif0 3. execute: # service network restart

Static vswif0 IP address: (from console) service network stop service network start
 * 1) edit GATEWAY= on /etc/sysconfig/network
 * 2) set with: esxcfg-vswif -i 10.0.0.100 -n 255.255.255.0 vswif0
 * 3) esxcfg-vswif -i [NEW_IP_ADDRESS] -n [MASK_ADDRESS] vswif0

DHCP address: esxcfg-vswif -i DHCP vswif0  # case sensitive

List virtual switch interfaces and IP addresses: (ESX only) esxcfg-vswif -l
 * 1) vswif0

Service Console presetup: esxcfg-vswitch –a vSwitch1 esxcfg-vswitch –A "Service Console" vSwitch1 esxcfg-vswitch –L vmnic1 vSwitch1

Create the vswif (Service Console) interface: esxcfg-vswif –a vswif0 –i 192.168.1.10 –n 255.255.255.0 –p "Service Console"

Delete the vswif interface: esxcfg-vswif -d vswif0

To bring up and down a vswif interface: ifconfig vswif0 down ifconfig vswif0 up

List vmnic and vswif interfaces, MAC addresses and IP addresses: (ESX only) ifconfig
 * 1) vmnic0, vswif0

ESX vswif0 network configuration: (ESX only) /etc/sysconfig/network-scripts/ifcfg-vswif0

DEVICE=vswif0 MACADDR=00:50:56:45:6a:6a ONBOOT=yes PORTGROUP="Service Console" BOOTPROTO=dhcp DHCPV6C=no IPV6INIT=no IPV6_AUTOCONF=no

DEVICE=vswif0 MACADDR=00:50:56:45:6a:6a ONBOOT=yes PORTGROUP="Service Console" BOOTPROTO=static DHCPV6C=no IPV6INIT=no IPV6_AUTOCONF=no IPADDR=10.0.0.10 NETMASK=255.255.255.0

Gateway: (remove 'gateway' if DHCP) /etc/sysconfig/network

NETWORKING=yes HOSTNAME=bossy IPV6_AUTOCONF=no NETWORKING_IPV6=no GATEWAY=10.0.0.1

References:
 * Configuring networking from the ESX service console command line - http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1000258

Example of Rebuilding Network
Deleteing Existing: esxcfg-vswitch -U vmnic0 # remove uplink esxcfg-vswif -d vswif0 esxcfg-vswitch --del-pg "Service Console" vSwitch0 # may not be needed (can also use -D) esxcfg-vswitch -d vSwitch0

List Virtual Switches: esxcfg-vswitch -l

Add Virtual Switch: esxcfg-vswitch -a kswitch

Switch Name     Num Ports   Used Ports  Configured Ports  MTU     Uplinks kswitch         128         1           128               1500 PortGroup Name       VLAN ID  Used Ports  Uplinks
 * 1) esxcfg-vswitch -l

List physical nics: esxcfg-nics -l Name   PCI           Driver      Link Speed     Duplex MAC Address       MTU    Description vmnic0 0000:01:00.00 e1000e      Up   100Mbps   Full   68:05:ca:02:75:1f 1500   Intel Corporation 82574L Gigabit Network Connection
 * 1) esxcfg-nics -l

Uplink a physical nic to the virtual switch: (warning - vmnic can only be tied to one switch at a time) esxcfg-vswitch –L vmnic0 kswitch

Set nic uplink: esxcfg-vswitch kswitch -L vmnic0

Switch Name     Num Ports   Used Ports  Configured Ports  MTU     Uplinks kswitch         128         2           128               1500    vmnic0 PortGroup Name       VLAN ID  Used Ports  Uplinks
 * 1) esxcfg-vswitch -l

Add a "Virtual Machine Port Group" Port Group for VM usage: esxcfg-vswitch -A "VM Network" kswitch
 * 1) esxcfg-vswitch --add-pg "VM Network" kswitch

Add "Service Console Port" Port Group: esxcfg-vswitch -A "Service Console" kswitch # "Service Console" can be what ever you would like (ie SConsole)

Switch Name     Num Ports   Used Ports  Configured Ports  MTU     Uplinks kswitch         128         1           128               1500 PortGroup Name       VLAN ID  Used Ports  Uplinks VM Network           0        0 Service Console      0        0
 * 1) esxcfg-vswitch -l

Create a Service Console Virtual Switch Interface in the "Service Console" port group esxcfg-vswif --add --ip DHCP --portgroup "Service Console" vswif0 # must be named vswif[0-99]
 * 1) esxcfg-vswif -a -i DHCP -p "Service Console" vswif0
 * 2) esxcfg-vswif --add --ip 10.50.2.100 --netmask 255.255.255.0 --portgroup "Service Console" vswif0  # must be named vswif[0-99]

Set default gateway in /etc/sysconfig/network (only if assigning static IP) GATEWAY=10.50.2.1

Restart network service (so default gateway takes affect) service network restart

NOTE: Now you can SSH into the system

---

Add a "VMkernel Port" for NFS:

esxcfg-vswitch -A "VMkernel" kswitch esxcfg-vmknic -a -i DHCP "VMkernel"   # vmk0 esxcfg-vmknic -l

esxcfg-vmknic -a -i 10.50.2.150 -n 255.255.255.0 "VMkernel"   # vmk0 esxcfg-route 10.50.2.1
 * 1) static method:

Add NFS NAS: esxcfg-nas -a newpu -o newpu -s /home/esx

---

Result:

Switch Name     Num Ports   Used Ports  Configured Ports  MTU     Uplinks kswitch         128         4           128               1500    vmnic0
 * 1) esxcfg-vswitch -l

PortGroup Name       VLAN ID  Used Ports  Uplinks KNetwork             0        0           vmnic0 NFS                  0        1           vmnic0 SConsole             0        1           vmnic0

Name    Port Group/DVPort   IP Family IP Address                              Netmask                                 Broadcast        Enabled   TYPE vswif1  SConsole            IPv4      10.50.2.189                             255.255.255.0                           10.50.2.255      true      STATIC [root@localhost newpu]# esxcfg-route -l VMkernel Routes: Network         Netmask          Gateway          Interface 10.50.2.0       255.255.255.0    Local Subnet     vmk0 default         0.0.0.0          10.50.2.1        vmk0
 * 1) esxcfg-vswif -l

Name   PCI           Driver      Link Speed     Duplex MAC Address       MTU    Description vmnic0 0000:01:00.00 e1000e      Up   100Mbps   Full   68:05:ca:02:75:1f 1500   Intel Corporation 82574L Gigabit Network Connection
 * 1) esxcfg-nics -l

Interface Port Group/DVPort   IP Family IP Address                              Netmask         Broadcast       MAC Address       MTU     TSO MSS   Enabled Type vmk0      NFS                 IPv4      10.50.2.160                             255.255.255.0   10.50.2.255     00:50:56:72:61:44 1500    65535     true    DHCP
 * 1) esxcfg-vmknic -l

VMkernel Routes: Network         Netmask          Gateway          Interface 10.50.2.0       255.255.255.0    Local Subnet     vmk0 default         0.0.0.0          10.50.2.1        vmk0
 * 1) esxcfg-route -l

Kernel IP routing table Destination    Gateway         Genmask         Flags Metric Ref    Use Iface 10.50.2.0      0.0.0.0         255.255.255.0   U     0      0        0 vswif1 169.254.0.0    0.0.0.0         255.255.0.0     U     0      0        0 vswif1 0.0.0.0        10.50.2.1       0.0.0.0         UG    0      0        0 vswif1
 * 1) route -n

lo       Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436  Metric:1 RX packets:969 errors:0 dropped:0 overruns:0 frame:0 TX packets:969 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:3420227 (3.2 MiB) TX bytes:3420227 (3.2 MiB)
 * 1) ifconfig

vmnic0   Link encap:Ethernet  HWaddr 68:05:CA:02:75:1F UP BROADCAST RUNNING MULTICAST MTU:1500  Metric:1 RX packets:4513 errors:0 dropped:0 overruns:0 frame:0 TX packets:624 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:475743 (464.5 KiB) TX bytes:80271 (78.3 KiB) Interrupt:49

vswif1   Link encap:Ethernet  HWaddr 00:50:56:42:E4:E3 inet addr:10.50.2.189 Bcast:10.50.2.255  Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500  Metric:1 RX packets:2235 errors:0 dropped:0 overruns:0 frame:0 TX packets:332 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:190827 (186.3 KiB) TX bytes:42265 (41.2 KiB)

---

Issues:

I get the following error when I try to connect from vCenter Server: Call "Datacenter.QueryConnectionInfo" for object "MyDC" on vCenter Server "VCENTERSERVER5" failed.

Cause:
 * VMware KB: Adding an ESX/ESXi host to the vCenter Server inventory fails with the error: Call "datacenter.queryconnectioninfo" for object on vCenter Server failed - http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1027672
 * This is a generic message meaning the system was unable to contact the server

Solution:
 * Check the IP configuration, such as default gateway for the Service Console.

Default Network Config
[root@kesx ~]# esxcfg-vswitch -l Switch Name     Num Ports   Used Ports  Configured Ports  MTU     Uplinks vSwitch0        128         3           128               1500    vmnic0

PortGroup Name       VLAN ID  Used Ports  Uplinks VM Network           0        0           vmnic0 Service Console      0        1           vmnic0

[root@kesx ~]# esxcfg-vswif -l Name    Port Group/DVPort   IP Family IP Address                              Netmask                                 Broadcast        Enabled   TYPE vswif0  Service Console     IPv4      10.50.2.150                             255.255.255.0                           10.50.2.255      true      DHCP

[root@kesx ~]# esxcfg-route -l VMkernel Routes: Network         Netmask          Gateway          Interface

[root@kesx ~]# esxcfg-vmknic -l Interface Port Group/DVPort   IP Family IP Address                              Netmask         Broadcast       MAC Address       MTU     TSO MSS   Enabled Type

[root@kesx ~]# esxcfg-nics -l Name   PCI           Driver      Link Speed     Duplex MAC Address       MTU    Description vmnic0 0000:01:00.00 e1000e      Up   100Mbps   Full   68:05:ca:02:75:1f 1500   Intel Corporation 82574L Gigabit Network Connection

Kernel IP routing table Destination    Gateway         Genmask         Flags Metric Ref    Use Iface 10.50.2.0      0.0.0.0         255.255.255.0   U     0      0        0 vswif0 169.254.0.0    0.0.0.0         255.255.0.0     U     0      0        0 vswif0 0.0.0.0        10.50.2.1       0.0.0.0         UG    0      0        0 vswif0
 * 1) route -n

[root@kesx ~]# ifconfig lo       Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436  Metric:1 RX packets:7800 errors:0 dropped:0 overruns:0 frame:0 TX packets:7800 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:8472281 (8.0 MiB) TX bytes:8472281 (8.0 MiB)

vmnic0   Link encap:Ethernet  HWaddr 68:05:CA:02:75:1F UP BROADCAST RUNNING MULTICAST MTU:1500  Metric:1 RX packets:90318 errors:0 dropped:0 overruns:0 frame:0 TX packets:690 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:9202842 (8.7 MiB) TX bytes:70457 (68.8 KiB) Interrupt:49

vswif0   Link encap:Ethernet  HWaddr 00:50:56:4B:0B:4D inet addr:10.50.2.150 Bcast:10.50.2.255  Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500  Metric:1 RX packets:41349 errors:0 dropped:0 overruns:0 frame:0 TX packets:667 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:3646060 (3.4 MiB) TX bytes:71611 (69.9 KiB)

VMDirectPath IO
keywords: PCI Passthrough

See VMDirectPath IO

VMware Infrastructure Client
VMware KB: VMware Infrastructure Client for Linux systems - http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1006095


 * Currently, VMware Infrastructure Client is only available for Windows systems. It is not available for Linux systems.


 * However, VI Web Access, a subset of VI Client functionality, can be used from Linux systems. For more information about VI Web Access, see http://www.vmware.com/pdf/vi3_35/esx_3/r35/vi3_35_25_web_access.pdf