VMware Cloud Community
gparker
Enthusiast
Enthusiast
Jump to solution

Change the Service Console's vlan id, and now cannot connect

Hi,

My ESX 3.5 server has vSwitch0 with a Service Console PG and a VMotion PG on it. There are 2 physical NICs assigned to this vSwitch, which are uplinked to 2 physical network switches.

The netoeking guys assigned vlan id 200 to the 2 ports on the physical switches that the 2 pNICs are plugged into. In the VI client, if I edit the properties of vSwitch0->Service Console and set the vlan to 200, I completely lose connectivity to the host. I can't ping the SC IP address any longer. I have a keyboard/monitor connected to the host and when I login to the SC, I can't ping the SC's default gateway or anything.

I used esxcfg-vswitch to set the SC's vlan id to 0 (all) and bingo!, I can talk to the host again and it can talk out. The network guys arrure me that they've set the vlan id=200 on the physical switch ports OK. So what's going wrong?

FWIW, we also have an ESX4 host configured similarily to the 3.5 host and it's communicating fine. It's SC has vlan=200 and uplinked to the same physical switches.

George.

0 Kudos
1 Solution

Accepted Solutions
danm66
Expert
Expert
Jump to solution

the switch port config's aren't the same between the working and non-working hosts. see http://kb.vmware.com/kb/1003806 for example config

View solution in original post

0 Kudos
1 Reply
danm66
Expert
Expert
Jump to solution

the switch port config's aren't the same between the working and non-working hosts. see http://kb.vmware.com/kb/1003806 for example config

0 Kudos