VMware Cloud Community
ronald_higgins
Contributor
Contributor

ESX 3.5: Loss of vlan use after Service Console IP Change

Greetings fellow forumites,

I'm hoping you can shed some light on on a problem that i'm having with vlans post Service Console move.

Initially when setting up my ESX i set up (SC) in VLAN100, and any VM's i needed to set up on the same IP Range/ VLAN i stuck in the "VM Network" Port Group which worked fine because the native vlan was 100.

Our Networks team then set up a trunk and pushed all the required VLAN's down the trunk, and i configured the PortGroups as required for VM's that needed different VLANs. All worked sweetly.

However, we've had to move the Service Console off VLAN100 and onto VLAN200.

So at the console i issued "esxcfg-vswif -i new_ipaddress -n new_subnet vswif0" and ammended the gateway.

Our Networks team then changed the native vlan to 200.

Restarted the networking and everything is working 100% except for for VM's that still needs to be in VLAN100. The Portgroup is configured and VLANID set to 100, but the VM's

just cant see the outside world (gateway).

Is there anything you guys can think of that I missed that would cause this?

On a side note, in VC, if you hover your mouse over the network adapter's Observed IP Addresses you'll get a pop up window for about 3 seconds of all the VLANS it knows about, is there any other place this can be viewed ?

Best Regards

Ronald

Reply
0 Kudos
3 Replies
Rubeck
Virtuoso
Virtuoso

Can you try to do a "vmware-vim-cmd /hostsvc/net/query_networkhint | grep -i -A2 vlanid" , which will display all detected networks and VLAN IDs seen by your physical NICs ?

You output dosn't seem to show any dot1Q tags...

/Rubeck

ronald_higgins
Contributor
Contributor

Hi Rubeck,

Thanks for the command vmware-vim-cmd /hostsvc/net/query_networkhint | grep -i -A2 vlanid, it gave me a lot more info and i was able to see what was going on.

For some reason yet undertimed, the VLAN100 is being seen by the ESX as another VLANID, as soon I used that VLAN in the PortGroup everything started working,

the network chaps are having a dig as too why though Smiley Happy

Thanks for the assist!

Reply
0 Kudos
Rubeck
Virtuoso
Virtuoso

Glad to help out and to hear it works again.. Smiley Happy

Hope that the network guys find the reason to why its being tagged with an incorrect VLAn ID ..

/Rubeck

Reply
0 Kudos