Change of IP Address leaves ESX box off network

[Keano]

Working with a 'dev' ESX box, I have encountered the following issues.

Dont want to re-install ESX unless I have to.......

I have moved my ESX box from one building to another within the site, meaning that I have had to change its IP address, VLAN etc.

I have not been able to see the box on the network since. I followed the procedure below to make the changes.

Logged into the server as root and ran the command

"esxcfg-vswif -d vswif0"

Ran the command to change the ip address, subnet mask and broadcast address.

"esxcfg-vswif -a vswif0 -p Service\ Console -i 10.1.1.1 -n 255.255.255.0 -b 10.1.1.255"

Changed the default gateway, by editing the network file located at /etc/sysconfig/network.

"cd /etc/sysconfig"

"vi network"

Used vi to go to location of the default gateway using the arrow keys.

Changed the hostname file by editing the hosts file located at /etc/hosts.

"cd /etc"

"vi hosts"

Saved config then restarted the ESX box.

I have checked that all the comms connections are 'Up.' All ports on the switch are set to Auto-Auto.

Can anyone provide any assistance? Greatly appreciated.

[dkfbp]

What is your gateway on the new network?

Try the command: ifconfig and tell me the ip address, broadcast address and subnet mask under vswif0.

When I am changing IP on my ESX servers I don't delete vswif0. I just use the command: esxcfg-vswif -i x.x.x.x -n x.x.x.x vswif0 and then edit the /etc/sysconfig/network file for the gateway. Then I do a "service network restart". Have you done a "service network restart"?

Frank

[merse]

Have you set the VLAN tag for the Service Console portgroup? Don't really want to post such an obvious question but is the physical switch port configured correctly? 9/10 times I've had connectivity issues it's been the end beyond ESX that's been the problem...

[Keano]

Thanks,

I have restarted the box several times now. I assume that would restart the service network.

IP address is 172.25.20.37

Gateway on the new network is 172.25.20.192

Broadcast address is 172.25.20.63

Subnet Mask is 255.255.252.0 (I think...will check)

[virtualdud3]

Are you able to ping/connect to the ESX host from other machines on the same subnet?

If so, you might try connecting to the ESX host via the VI client, and then correct the default gateway/hostname through the VI client.

###############

If you found this information useful, please consider awarding points for "Correct" or "Helpful". Thanks!!!

[Keano]

Thanks,

I am relying on the comms team to ensure that the physical switch port is configured correctly. The ports are configured to Auto-Auto speed.

I have not set the VLAN tag for the Service Console portgroup. I dont know how to do this through the Command Console.

[dkfbp]

I think you should verify what kind of a network it is.

Your ip is 172.25.20.37 and your broadcast address is 172.25.20.63 Normally that would mean you

are on a 255.255.255.224 network and your ip address range would be 172.25.20.33 -> 172.25.20.62

The gateway you have defined is 172.25.20.192 which does not belong to the scope. Please verify your network

configuration. It could be related to what I just mentioned.

Frank

[Keano]

No, I have not been able to ping/connect from the same subnet.

I can't connect from the VI client as the problem I'm having means the box is not on the network.

Thanks.

[virtualdud3]

I realize that if you are having network issues, you may not be able to connect even from the same subnet. FYI, I have seen these problems where the IP address changes, but the default gateway gets borked therefore it is possible to connect via the VI client from the same subnet - this is why I asked.

###############

If you found this information useful, please consider awarding points for "Correct" or "Helpful". Thanks!!!

[merse]

I have not set the VLAN tag for the Service Console portgroup. I dont know how to do this through the Command Console.

Do you just have a single NIC mapped to a virtual switch servicing the SC? Unless you've got more than one portgroup connected to the virtual switch and multiple trunked pNICs you won't need to tag the VLAN ID anyway but for future reference command to change it:

esxcfg-vswitch vSwitch1 -p "Service Console" -v 10 -v =123 where 123 is your VLAN ID.

[Keano]

I have rechecked my Network Settings supplied by comms team

Gateway details & Subnet Mask supplied were incorrect.

IP address is 172.25.20.37

Gateway on the new network supplied originally was 172.25.20.192, it should be 172.25.20.1

Broadcast address is 172.25.20.63

Subnet Mask supplied originally was 255.255.252.0. I have changed this to 255.255.255.192.

I can now contact the box via the network.

Thanks to all contributors for their helpful suggestions.