GreenLake Administration
- Community Home
- >
- Networking
- >
- Legacy
- >
- Switches, Hubs, Modems
- >
- ProCurve + HP GbE2c + vSphere 4
Switches, Hubs, and Modems
1848042
Members
2374
Online
104022
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-22-2010 10:33 PM
02-22-2010 10:33 PM
ProCurve + HP GbE2c + vSphere 4
For the environment:
ProCurve + HP GbE2c + vSphere 4
I need VM's from different networks on the same vSwitch to access my production network. I assume I tag the vlans on 5406zl and the GbE2c and create the vm port groups (vlans) within the vswitch and assign vm's to the port groups... doesnt work!
I have everything working without vlans configured on the GbE2c's and vm environment - with vlans configured and tagged on the procurves, works great!
I believe the problem is with the GbE2c re: the vlan tagging. I proper downlinks (to vm env.) + xconnnects (17,18) and uplinks (trks procurve) in the equation, but re: of having the pvid and vlan tagging on and configured, traffic still does not pass.
Please advise!
ProCurve + HP GbE2c + vSphere 4
I need VM's from different networks on the same vSwitch to access my production network. I assume I tag the vlans on 5406zl and the GbE2c and create the vm port groups (vlans) within the vswitch and assign vm's to the port groups... doesnt work!
I have everything working without vlans configured on the GbE2c's and vm environment - with vlans configured and tagged on the procurves, works great!
I believe the problem is with the GbE2c re: the vlan tagging. I proper downlinks (to vm env.) + xconnnects (17,18) and uplinks (trks procurve) in the equation, but re: of having the pvid and vlan tagging on and configured, traffic still does not pass.
Please advise!
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-24-2010 08:26 PM
02-24-2010 08:26 PM
Re: ProCurve + HP GbE2c + vSphere 4
Ports on the Gbe2c switch must be tagged and then added to the VLANs you need:
cfg/port x/tag e
cfg/l2/vlan x/add 1
Same must be done for xconnect (trk1) if used and the uplinks. On the Procurve switch, port or trunks connecting to the gbe2c must added as tagged member of each VLAN.
vlan x
tagged 1
On the ESX host, you need to assign the same VLANs, that should work fine.
cfg/port x/tag e
cfg/l2/vlan x/add 1
Same must be done for xconnect (trk1) if used and the uplinks. On the Procurve switch, port or trunks connecting to the gbe2c must added as tagged member of each VLAN.
vlan x
tagged 1
On the ESX host, you need to assign the same VLANs, that should work fine.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-05-2011 12:30 PM
04-05-2011 12:30 PM
Re: ProCurve + HP GbE2c + vSphere 4
I'm interested to know if this actually works now and if so what your configuration looks like on the VM and switch sides.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2026 Hewlett Packard Enterprise Development LP