Thursday, May 16, 2013

Create NutanixVswitch from scratch


There have been few instances migrating to and from Distributed Vswitch can cause the nutanix v
switch to be deleted or have wrong config. This will cause Genesis to crash and not start.

From CVM: ping -I 192.168.5.254 192.168.5.1  to verify if Internal Nutanixvswitch is good.

Error Message in data/logs/genesis.out:
2012-11-06 13:57:42 ERROR node_manager.py:2378 Could not load the local ESX configuration

Sample of right config of NutanixVswitch

~ # esxcfg-vswitch -l
Switch Name      Num Ports   Used Ports  Configured Ports  MTU     Uplinks
vSwitchNutanix                   128         3           128               1500
  PortGroup Name        VLAN ID  Used Ports  Uplinks
  svm-iscsi-pg                         0        1
  vmk-svm-iscsi-pg                 0        1

Make sure these info matches.
- No uplink interfaces
- Used ports 3
- Portgroup and # of used ports
- Name of the vswitch

Sample of vmknic: ( make sure subnet mask and ip address and enabled=true matches)

~ # esxcfg-vmknic -l
Interface  Port Group/DVPort   IP Family IP Address    Netmask         Broadcast      \
 MAC Address       MTU     TSO MSS   Enabled Type               
vmk1       vmk-svm-iscsi-pg    IPv4      192.168.5.1   255.255.255.0   192.168.5.255   \
00:50:56:62:5a:e4 1500    65535     true    STATIC        

Commands to recreate the nutanix Vswitch:


1. esxcfg-vswitch -a vSwitchNutanix ( this needs to be done via CLI)

2. esxcfg-vswitch -A "svm-iscsi-pg" vSwitchNutanix

3. esxcfg-vswitch -A "vmk-svm-iscsi-pg" vSwitchNutanix
4. If vmknic does not exist,
esxcfg-vmknic -a -i 192.168.5.1 -n 255.255.255.0 -p vmk-svm-iscsi-pg
5. esxcfg-vmknic -l

6. enable the 192.168.5.1 vmknic
esxcfg-vmknic -e vmk1

7. On CVM , verify eth1 is part of svm-iscsi-pg (edit settings of CVM in Vcenter)

8.ifconfig eth1 and eth1:1 to verify if the ports are up and ip address is
configured correctly ( 192.168.5.2 and 192.168.5.254 respectively)