Tagging between vSwitch and physical switch

[Asha D]

Hi,

We have HP c7000 enclosure with two BL460c blades(not using Virtual connect).we have installed ESX 4.0 on both the blade servers.we have 2 virtual switch for 2 ESX servers and each switch have default VM network.Now we have created one port group "servers" in both vSwitch with same name and VLAN ID 10.

We are using HP procurve 8212zl swicth.only one NIC port of blade enclosure is connected to HP procurve switch.we have 2 VLANs "default VLAN" and "servers" VLAN in Switch.VLAN ID 10 is assigned to "servers" VLAN.We tagged the blade enclosure port to "servers" VLAN and IP routing is also enabled.

But problem is we are not ping the systems between VM network and Servers VLAN.

Please any help to resolve the issue?

Regards

Asha

[Antonio Milanese]

Hi,

which IC modules..passthrough, GbE2c or Cisco?

best regards,

Antonio

[Asha D]

Hi,

It passes through
HP blade server->GbE2c -->HP procurve 8212Zl

Regards
Asha

[Asha D]

Hi,

In our HP GBE2c Blade switch we are getting following alert message
"ALERT ip: cannot contact default gateway 192.168.1.x"
is this may the issues for communication of vlans created in the server and procurve switch or any other configuration(like vlan tagging) we have to do in the HP GBE2c switch..
kindly help to solve this issue.

Regards
Asha

[Antonio Milanese]

Hello,

every ports down to procurve switch must be a tagged member of each tagged VLAN you use in a ESX vPG/vSwitch:

vPG(tag VID=10)->internal gbe2c(tag VID=10)-> procurve (tag VID=10)

if you have two gbe2c xconnected enable vlan tag on p17,p18


on gbe2c with cli (or you can use webmgnt):

cfg/port port_x
tag/e
cfg/l2/vlan vid_y
en
add port_x

on 8212zl:
conf t
vlan vid_y
tagged port_x
ip address xx.xx.xx.xx/24 (or your VLAN ip/mask)

the native VLAN is by default untagged so nothing special here.
On procurve you must enable ip routing to allow intervlan traffic:

conf t
ip routing

If (x)STP is running lower gbe2c ICs brigde priority so the 8212zl is the root. Ah IIRC using EBIPA there are some problem since it hard set to VID 4095 and interface 256 (p19 )for management.


Hope this solve your problem, regards

Antonio