VMware Cloud Community
escapem2
Enthusiast
Enthusiast
Jump to solution

Network Settings Disabled DCUI

hi guys

I had some networking issues so I had to remove one vmnic from the management network made of vmnic0 - vmnic1. I had to remove vmnic0

In six servers removing vmnic0 worked OK, but in this server gave me some errors I think since I don't remember pretty well related with IPv6...

the problem with this server is after the error Network Settings are disabled and I am not able to reconfigure vmnics in fact now server has no IP

any idea how to fix this, directly in the cli console I see the vSwitch0 which has the Management Network, which I fact I tried leaving only vmnic1 is not working yet

vSw.png

vmnic.png

Disabled.png

ip.png

thanks a lot

Reply
0 Kudos
1 Solution

Accepted Solutions
ssbkang
Enthusiast
Enthusiast
Jump to solution

OK, if it's in production, need to be fixed via esxcli.

Apparently, the Management VMKernel is removed from the Management Port group as it says "0.0.0.0" on the third screenshot.

Just to make sure, run esxcli network ip interface list to check if there are any VMKernels.

It won't generate any output if there is none.

Now, run esxcli network ip interface add -i=vmk0 -p="Management Network -M="MAC Address"" to create a VMKernel for management. It is very important to put in the right MAC Address of the Uplink (in your case, the MAC Address of vmnic1, 5c:f3......)

One thing to note is vmk(number) should be the number that doesn't conflict. For example, if there are 2 VMKernels, vmk0 and vmk1, vmk2 should be used.

Now, you will be able to configure the Management Network via DCUI.

If you want to set ipv4 settings via esxcli, run esxcli network ip interface ipv4 set  -i=vmk0 -I=x.x.x.x -N=x.x.x.x -t=static

  • -i is the VMKernel name
  • -I (capital i) is the Management IP Address
  • -N is the subnet mask
  • -t=static represents it will be a static IP Address, not DHCP

Hope this helps.

Steven.

View solution in original post

Reply
0 Kudos
7 Replies
ssbkang
Enthusiast
Enthusiast
Jump to solution

Hi, If this ESXi isn't in a production yet, I would recommend you to restore the network settings. It takes time to fix using esxcli! Network Restore Options -> Restore Standard Switch Regards, Steven.

Reply
0 Kudos
escapem2
Enthusiast
Enthusiast
Jump to solution

I prefer esxcli since I have VMs in production

Reply
0 Kudos
ssbkang
Enthusiast
Enthusiast
Jump to solution

OK, if it's in production, need to be fixed via esxcli.

Apparently, the Management VMKernel is removed from the Management Port group as it says "0.0.0.0" on the third screenshot.

Just to make sure, run esxcli network ip interface list to check if there are any VMKernels.

It won't generate any output if there is none.

Now, run esxcli network ip interface add -i=vmk0 -p="Management Network -M="MAC Address"" to create a VMKernel for management. It is very important to put in the right MAC Address of the Uplink (in your case, the MAC Address of vmnic1, 5c:f3......)

One thing to note is vmk(number) should be the number that doesn't conflict. For example, if there are 2 VMKernels, vmk0 and vmk1, vmk2 should be used.

Now, you will be able to configure the Management Network via DCUI.

If you want to set ipv4 settings via esxcli, run esxcli network ip interface ipv4 set  -i=vmk0 -I=x.x.x.x -N=x.x.x.x -t=static

  • -i is the VMKernel name
  • -I (capital i) is the Management IP Address
  • -N is the subnet mask
  • -t=static represents it will be a static IP Address, not DHCP

Hope this helps.

Steven.

Reply
0 Kudos
zXi_Gamer
Virtuoso
Virtuoso
Jump to solution

If your network is down, then I am wondering how your Server is still under production. It might be that the virtual machines portgroups are managed by a different vswitch with another uplink.

However, coming to your topic, the "greyed out" options might arise if you have enabled DHCP and the removal of the vmnic0 lead to reclaiming of the IP based on the new mac address from vmnic1 which for many reasons could fail. [dhclient timing out on vmnic1, no ips, still queries with vmnic0 mac address]

I also find that the VMkernel port is treated as a virtual machine portgroup instead of management.

Check this page, since it almost similar to your case. vSphere 5 Networking Bug #2 Affects Management Network Connectivity - VMtoday

Also, I would suggest, to unlink the vmnic1 from the vswitch0 and delete the portgroup Management_network and create a new one as suggested by skan with

esxcfg-vmknic -a - i DHCP -p VMKernel

escapem2
Enthusiast
Enthusiast
Jump to solution

thanks a lot skan070 I will try first thing in the morning

Yes zXi_Gamer I have 4 vmnics 2 for Management and vMotion and 2 more for Virtual Networks that's why my VMs are still alive Smiley Happy

Reply
0 Kudos
escapem2
Enthusiast
Enthusiast
Jump to solution

it's fixed thanks a lot

some time ago I had this issue and we were in a run and I rebooted the server now I know that is not needed.

# esxcli network ip interface list

this command showed that  vmk1 and vmk2 were used

vmks.png

and when running this command

# esxcli network ip interface add -i=vmk0 -p="Management Network" -M="MAC Address"

Error message

unable to add vmkernel interface error was a vmkernel nic for connection point already exists


so I removed vmk1 and vmk2

# esxcli network ip interface remove -i vmk1

# esxcli network ip interface remove -i vmk2


After that options in DCUI were enabled. Smiley Happy

Reply
0 Kudos
ssbkang
Enthusiast
Enthusiast
Jump to solution

Glad to hear it's been fixed!

Reply
0 Kudos