VMware Cloud Community
shmaya
Contributor
Contributor

ESX 3.5 display worng ip address

Hello all,

I need help with ESX 3.5, I upgraded my previous version of ESX 3.0 to ESX 3.5 with latest build, that enable you to keep your VMs as they are.

After the installation completed successfully, The display shows a new ip but, when i try to connect vi Virtual Infrastructur client with the new ip, it won't log in but, if log in with the old ip, it lets log in.

After i accesse the server with the old ip, I tried to start a vm and got a general system error.

Could anyone help with this issue, I will realy appreciate it.

Reply
0 Kudos
10 Replies
christianZ
Champion
Champion

just to be sure - you are using the newest VI client 2.5 too, aren't you?

Reply
0 Kudos
shmaya
Contributor
Contributor

Yes i am, even throw web access the VMs won't work.

Reply
0 Kudos
christianZ
Champion
Champion

Can you post following outputs here:

esxcfg-vswif -l

ifconfig

esxupdate -l query

Reply
0 Kudos
shmaya
Contributor
Contributor

# esxcfg-vswif -l

Name Port Group IP Address Netmask Broadcast Enabled DHCP

vswif0 Service Console 126.0.1.179 255.0.0.0 126.255.255.255 true true

# ifconfig

lo Link encap:Local Loopback

inet addr:127.0.0.1 Mask:255.0.0.0

UP LOOPBACK RUNNING MTU:16436 Metric:1

RX packets:39 errors:0 dropped:0 overruns:0 frame:0

TX packets:39 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:0

RX bytes:2478 (2.4 Kb) TX bytes:2478 (2.4 Kb)

vmnic0 Link encap:Ethernet HWaddr 00:15:17:17:F0:3C

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

RX packets:1806 errors:0 dropped:0 overruns:0 frame:0

TX packets:475 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:1000

RX bytes:171329 (167.3 Kb) TX bytes:376614 (367.7 Kb)

Base address:0x2020 Memory:b8820000-b8840000

vmnic1 Link encap:Ethernet HWaddr 00:15:17:17:F0:3D

UP BROADCAST MULTICAST MTU:1500 Metric:1

RX packets:0 errors:0 dropped:0 overruns:0 frame:0

TX packets:0 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:1000

RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

Base address:0x2000 Memory:b8800000-b8820000

vswif0 Link encap:Ethernet HWaddr 00:50:56:49:FA:88

inet addr:126.0.1.179 Bcast:126.255.255.255 Mask:255.0.0.0

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

RX packets:1570 errors:0 dropped:0 overruns:0 frame:0

TX packets:435 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:1000

RX bytes:154341 (150.7 Kb) TX bytes:373314 (364.5 Kb)

# esxupdate -l query

Installed software bundles:

-


Name -


--- Install Date --- --- Summary ---

3.0.1-32039 09:34:09 05/15/07 Full 3.0.1 release of VMware ESX Serve r

3.5.0-64607 04:58:39 05/15/08 Full bundle of ESX 3.5.0-64607

New packages:

LGTOaama-5.1.2-1

LGTOaamvm-5.1.2-1

VMware-vpxa-2.0.0-27704

Missing packages:

VMware-esx-drivers-net-bcm5700-7.3.5-32039

VMware-esx-drivers-scsi-lpfcdd-v732-7.3.2.1vmw-32039

VMware-esx-drivers-scsi-qla2200-v7.07-7.7.4.1vmw-32039

VMware-esx-drivers-scsi-qla2300-v7.07-7.7.4.1vmw-32039

Reply
0 Kudos
shmaya
Contributor
Contributor

ESX shows in console ip - 126.0.1.186

but in ifconfig it shows 126.0.1.179

Reply
0 Kudos
shmaya
Contributor
Contributor

ESX shows in console ip - 126.0.1.186

but in ifconfig it shows 126.0.1.179

Reply
0 Kudos
christianZ
Champion
Champion

> Name Port Group IP Address Netmask Broadcast Enabled DHCP

>vswif0 Service Console 126.0.1.179 255.0.0.0 126.255.255.255 true true

First you are using dhcp - maybe not the best thing here.

>VMware-vpxa-2.0.0-27704

Second - your vpxa agent is not updated correctly.

Reply
0 Kudos
shmaya
Contributor
Contributor

Do you think this what's causing the error when i start the VMs?

it is related to the wrong ip address shown in the ESX console?

Reply
0 Kudos
christianZ
Champion
Champion

I would think so.

You have not the right VC agent - but you work with VC 2.5 and the ip mismatch is not healthy also.

With such config you shouldn't go back in production. First clear all these errors.

Reply
0 Kudos
shmaya
Contributor
Contributor

ok, i'll try it, thanks for the help.

Reply
0 Kudos