HPE GreenLake Administration
- Community Home
- >
- Networking
- >
- Legacy
- >
- Switches, Hubs, Modems
- >
- VLAN Routing Management VLAN
Switches, Hubs, and Modems
1826219
Members
2864
Online
109691
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
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
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
05-27-2011 05:32 AM
05-27-2011 05:32 AM
VLAN Routing Management VLAN
Hello,
I am hoping you can help me,
I have recently set up the following infrastructure and have been running into some difficulties with getting the intra vlan routing working the way I want it to.
Layer 3 VLAN routing switch - HP Procurve 6200yl
2 x HP Procurve 2910AL (server switches)
HP P4500 G2 SAN
A VMware infrastructure sits on top of this.
I have created VLAN's for an ISCSI, Production and a DMZ network and tagged these across the switches. Routing works between the switches and the networks are isolated as expected.
The P4500 G2 SAN's do not have a seperate network interface to go onto the management/production network. Routes need to be in place between the iSCSI and Production VLAN's to ensure that we can use the email alerting functionality on the SAN as the source IP address when it sends will be on the iSCSI subnet and theemail server and DNS is located on the Production subnet.
The issue is that I need to be able to route bewteen the Production VLAN and the iSCSI VLAN to get this to work. I also would ideally like to be able to enable the management VLAN on the Production subnet so that I can web access the switches from the main network and utilise Procurve manager to manage all of the companies switch infrastructure from a single management station.
It would seem that I am unable to route between the VLAN which I elect to be the management VLAN, I need to enable the management VLAN so that I can web access the switches from the main network.
The VLAN's I have created which are not enabled as the management VLAN route OK with no issues but as soon as I enable the management VLAN I can no longer route as before on the VLAN enabled for management.
My question is, is there a way around this so that I can ultimately achieve the following goals?
1. Be able to send emails from the P4500 G2 SAN's using the DNS and Email systems on the Production VLAN without loosing connectivty to the switches & procurve manager.
2. Be able to web access the switches if required from the Production VLAN - this can be either by using IP routing or the same IP subnet assigned to that VLAN.
3. Be able to manage all of the switches using Pro Curve Manager
I have attached the config of the core routing switch for you to take a look at.
Any assistance you can provide or another way to get this to work would be greatly appreciated.
Many Thanks
Harry
I am hoping you can help me,
I have recently set up the following infrastructure and have been running into some difficulties with getting the intra vlan routing working the way I want it to.
Layer 3 VLAN routing switch - HP Procurve 6200yl
2 x HP Procurve 2910AL (server switches)
HP P4500 G2 SAN
A VMware infrastructure sits on top of this.
I have created VLAN's for an ISCSI, Production and a DMZ network and tagged these across the switches. Routing works between the switches and the networks are isolated as expected.
The P4500 G2 SAN's do not have a seperate network interface to go onto the management/production network. Routes need to be in place between the iSCSI and Production VLAN's to ensure that we can use the email alerting functionality on the SAN as the source IP address when it sends will be on the iSCSI subnet and theemail server and DNS is located on the Production subnet.
The issue is that I need to be able to route bewteen the Production VLAN and the iSCSI VLAN to get this to work. I also would ideally like to be able to enable the management VLAN on the Production subnet so that I can web access the switches from the main network and utilise Procurve manager to manage all of the companies switch infrastructure from a single management station.
It would seem that I am unable to route between the VLAN which I elect to be the management VLAN, I need to enable the management VLAN so that I can web access the switches from the main network.
The VLAN's I have created which are not enabled as the management VLAN route OK with no issues but as soon as I enable the management VLAN I can no longer route as before on the VLAN enabled for management.
My question is, is there a way around this so that I can ultimately achieve the following goals?
1. Be able to send emails from the P4500 G2 SAN's using the DNS and Email systems on the Production VLAN without loosing connectivty to the switches & procurve manager.
2. Be able to web access the switches if required from the Production VLAN - this can be either by using IP routing or the same IP subnet assigned to that VLAN.
3. Be able to manage all of the switches using Pro Curve Manager
I have attached the config of the core routing switch for you to take a look at.
Any assistance you can provide or another way to get this to work would be greatly appreciated.
Many Thanks
Harry
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
Support
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP