VMware Cloud Community
teich
Contributor
Contributor

Rebooting turns my VMkernel portgroups into standard portgroups!

We just updated one of our ESXi servers to 130755, and are now running into a STRANGE issue.

We have a NFS NAS on a different network from our "service console" network.

I go and create a VMkernel portgroup on that network, add storage, add VMs, all is great.

Then I reboot the ESXi server.

When it comes back up, the EXACT same portgroup is now a normal VM portgroup, and I can't access my storage anymore.

To make things really fun, I can't delete these subverted portgroups either, getting "Unable to delete portgroup XXX for the following reason: VM Kernel NIC"

The first pic attached is before reboot, the second after. Look at the "VMKernel Test Connectivty" portgroup in vSwitch0.

For CLI types, here's the RCLI output:

BEFORE:

3(NXDOMAIN):~# esxcfg-vswitch --server vh10.int.replicatetech.com -l
Enter username: root
Enter password: 
Switch Name     Num Ports       Used Ports      MTU     Uplinks
vSwitch0        64              4               1500    vmnic0          

  PortGroup Name        VLAN ID   Used Ports      Uplinks
  VMkernel test connectivity100       0               vmnic0          
  VLAN 118              118       0               vmnic0          
  no-frag-full-span-v3010         0               vmnic0          
  VLAN 101              101       0               vmnic0          
  Management Network    101       1               vmnic0          

Switch Name     Num Ports       Used Ports      MTU     Uplinks
vSwitch1        64              1               1500                    

  PortGroup Name        VLAN ID   Used Ports      Uplinks
  IP Storage eprec      255       0                               
  IP Storage deprecate  255       0    

3(NXDOMAIN):~# esxcfg-vmknic --server vh10.int.replicatetech.com -l
Enter username: root
Enter password: 
Interface  Port Group                    IP Address        Netmask           MAC Address       
vmk0       Management Network            172.22.101.10     255.255.255.0     00:1f:29:0b:6f:da 

AFTER:

3(NXDOMAIN):~# esxcfg-vswitch --server vh10.int.replicatetech.com -l
Enter username: root
Enter password: 
Switch Name     Num Ports       Used Ports      MTU     Uplinks
vSwitch0        64              4               1500    vmnic0          

  PortGroup Name        VLAN ID   Used Ports      Uplinks
  VMkernel test connectivity100       0               vmnic0          
  VLAN 118              118       0               vmnic0          
  no-frag-full-span-v3010         0               vmnic0          
  VLAN 101              101       0               vmnic0          
  Management Network    101       1               vmnic0          

Switch Name     Num Ports       Used Ports      MTU     Uplinks
vSwitch1        64              1               1500                    

  PortGroup Name        VLAN ID   Used Ports      Uplinks
  IP Storage eprec      255       0                               
  IP Storage deprecate  255       0     

3(NXDOMAIN):~# esxcfg-vmknic --server vh10.int.replicatetech.com -l
Enter username: root
Enter password: 
Interface  Port Group                    IP Address        Netmask           MAC Address       
vmk0       Management Network            172.22.101.10     255.255.255.0     00:1f:29:0b:6f:da 

Anyone out there have any insight?

Oren

Use RDA to help find and fix network problems http://www.replicatetech.com/trial.html
0 Kudos
2 Replies
SuryaVMware
Expert
Expert

Are you sure about the first cli screenshot. coz i dont see a VMkernel,vmk , interface in the first screenshot

for portgroup "VMkernel test connectivity100"

-Surya

0 Kudos
teich
Contributor
Contributor

Looks like the ordering got mixed when I uploaded.

Picture 2.png is before.

Picture 3.png is after.

Picture 2.png - look at the bottom of the first switch, and you can see 172.22.100.10 as a VMKernel portgroup

Use RDA to help find and fix network problems http://www.replicatetech.com/trial.html
0 Kudos