PaperSac

Have you messed up or somehow deleted your service console on your VMWare server? Have you moved your ESX server to a new VLAN, subnet, or facility? How do you get your ESX server to respond via the Service Console if the IP addresses don’t match? The answer is esxcfg-vswif.

esxcfg-vswif - This is the tool to manage your Ethernet interfaces for the Service Console. Forget what you used in previous versions of ESX Server, the “eth” prefix is history.

First things first: Type “esxcfg-vswif –l” to get a listing of you current vswif settings.

# esxcfg-vswif -l

Name Port Group IP Address Netmask Broadcast Enabled DHCP

vswif0 Service Console 192.168.200.30 255.255.255.0 192.168.200.255 true false

In this example you see that we have vswif configured and set to 192.168.200.30. –But what if you type “esxcfg-vswif –l” and get no result? Well you don’t have vswif0 set up, and probably do not even have the virtual switch configured either. –I’ll address that shortly.

If you need to simply change the IP for the Service Console, it’s a simple 3 step process.

1. Remove the current vswif0 via the following command:
   

# esxcfg-vswif –d vswif0

1. Recreate the new vswif0 port via the following command:
   

# esxcfg-vswif –a –I 192.168.200.230 –n 255.255.255.0 –b 192.168.200.255 –p “Service Console”

1. Modify the default gateway to match your new VLAN:
   

# vi /etc/sysconfig/network

If you are in real trouble and have hosed your vswitch0 as well, do the following:

1. Check to see if you have a vswitch configured:
   

# esxcfg-vswitch -l

1. If you don’t have anything for vswitch0, let’s create something:
   

# esxcfg-vswitch –add-pg=”Service Console ” vSwitch0

1. Now you can add your vswif0 port settings as above.
   

Trackback URI | Comments RSS