VMware has got a nice step-by-step guide on how to do this here. However, I would like to mention a few important things:
- before you change the IP of the existing service console, just in case add another service console port and test you connection. You can never know
- you cannot do it from vClient. Open a local console or a remote one. Modify the conf files as described in VMware KB. Restart the network service (if you use ssh console, your connection will be dropped).
- if you use VLANs, after you execute esxcfg-vswif -i a.b.c.d -n w.x.y.z vswif0, do execute the following command:
esxcfg-vswitch vSwitch0 -v vlan_number -p ‘Service Console’
where vSwithc0 is your vSwitch with service console portgroup, vlan_number is replaced with your VLAN and ‘Service Console’ is the name of the portgroup.
- if you want to change the hostname as well you will need reboot. You can change the hostname first from vClient, reboot and change IP address from the console or do all the things at the same time and reboot after that. If you do not change the hostname from ‘DNS and routing’ part in vClient, make sure you change the hostname and IP both in /etc/hosts and in /etc/vmware/esx.conf
- I found some info on the internet that to change the service console network configuration you need to delete and recreate the whole vSwitch. That’s not true.
- Last but not least, you’d better have access to the server with local cosnole (or RSA/DRAC/iLO). As I said, you never know…