Static Virtual LANs (VLANs)
Switch | A1 | A3 | A6 | A7 | B2 | B4 | B5 | B9 | C2 | C3 | C6 | C8 |
Management VLAN (VID = 7) | Y | N | N | Y | Y | Y | N | N | Y | N | N | N |
Marketing VLAN (VID = 12) | N | N | N | N | N | N | N | N | N | Y | Y | Y |
Shipping Dept. VLAN (VID = 20) | N | Y | Y | N | N | N | N | N | N | N | N | N |
Y | Y | Y | Y | Y | Y | Y | Y | Y | Y | Y | Y | |
|
|
|
|
|
|
|
|
|
|
|
|
|
Preparation
1.Determine a VID and VLAN name suitable for your Management VLAN.
2.Determine the IP addressing for the Management VLAN (DHCP/Bootp or
Manual.3.Plan your Management VLAN topology to use ProCurve switches that support this feature. (See the list on page
•Ports to which you will connect authorized management stations (such as Port A7 in figure
•Ports on one switch that you will use to extend the Management VLAN to ports on other ProCurve switches (such as ports A1 and B2 or B4 and C2 in figure
Hubs dedicated to connecting management stations to the Management VLAN can also be included in the above topology. Note that any device connected to a hub in the Management VLAN will also have Management VLAN access.
4.Configure the Management VLAN on the selected switch ports.
5.Test the management VLAN from all of the management stations autho rized to use the Management VLAN, including any
N o t e | If you configure a Management VLAN on a switch by using a Telnet connection |
| through a port that is not in the Management VLAN, then you will lose |
| management contact with the switch if you log off your Telnet connection or |
| execute write memory and reboot the switch. |
|
|