- Community Home
- >
- Networking
- >
- Legacy
- >
- Switches, Hubs, Modems
- >
- Re: Procurve 2848 Management VLAN Communication
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
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
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- 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-08-2006 01:52 AM
тАО02-08-2006 01:52 AM
Thanks for your help in advance.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-08-2006 03:03 AM
тАО02-08-2006 03:03 AM
SolutionThe function of the management VLAN is to make a secure VLAN for management. One of the ways it is secured, is by making sure other VLAN's do not have access to the management VLAN.
So this is a feature of the management VLAN.
You can read about it in chapter 2 of the Advanced Traffic Management guide: ftp://ftp.hp.com/pub/networking/software/2600-2800-4100-6108-AdvTraff-Oct2005-59908853.pdf
Why do you want to use the management VLAN? Maybe there are other ways to accomplish what you want with it.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-08-2006 03:12 AM
тАО02-08-2006 03:12 AM
Re: Procurve 2848 Management VLAN Communication
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-08-2006 03:52 AM
тАО02-08-2006 03:52 AM
Re: Procurve 2848 Management VLAN Communication
You could then use authorized IP managers to control who (what IP addresses) are allowed to manage the switches.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-08-2006 04:18 AM
тАО02-08-2006 04:18 AM
Re: Procurve 2848 Management VLAN Communication
EXAMPLE
vlan 10 (IT)
vlan 20 (Management) Set as Management
vlan 30 (Servers)
vlan 40 (Printers)
vlan 50 (Desktops)
My understanding was that the Management vlan ip address was the only way to manage the switches. No switch interfaces will be set within this vlan.
The main concern was how the IT staff could configure the switches if the vlan that IT was on and the Management vlan could not communicate between each other. I am thinking if I set up the IT vlan and Management vlan on a router on a stick config, (sub-interfaces on one port for each vlan on a router) the IT and Management vlan will be able to talk.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-08-2006 09:23 AM
тАО02-08-2006 09:23 AM
Re: Procurve 2848 Management VLAN Communication
The management feature is for making extra security regarding management, by making one VLAN only accessible from within that VLAN.
The router on a stick solution will not work with a management VLAN also, because this is part of that feature. From the manual:
Configures a secure Management VLAN by creating an isolated network for managing the following ProCurve switches that support this feature:
├в ┬в
Series 2600 switches ├в ┬в Series 4100gl switches
├в ┬в
Series 2600-PWR switches ├в ┬в Series 5300xl switches
├в ┬в
Series 2800 switches ├в ┬в Switch 6108
├в ┬в
Series 3400cl switches
Access to this VLAN, and to the switch├в s management functions (Menu, CLI, and web browser interface) is available only through ports configured as members.
├в
Multiple ports on the switch can belong to the Management VLAN. This allows connections for multiple management stations you want to have access to the Management VLAN, while at the same time allowing Management
VLAN links between switches configured for the same Management
VLAN.
├в
Only traffic from the Management VLAN can manage the switch, which means that only the workstations and PCs connected to ports belonging to the Management VLAN can manage and reconfigure the switch.
--------------------------------------------
So if you want to be able to manage the switches from a VLAN that is also used as a production VLAN, you will need to remove the management VLAN. If you still want to control access to the management features, use the authorized IP managers feature.
I hope this cleared things up.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-08-2006 09:36 AM
тАО02-08-2006 09:36 AM
Re: Procurve 2848 Management VLAN Communication
I read that guide and everything is making sense now. I thought from everything else I had read that there had to be a Management vlan.
Putting PC's in the management vlan though basically makes those pc's worthless for anything but configuring the switches so I will just have to shut off the management vlan.
Thanks again.