Switches, Hubs, and Modems
Showing results for 
Search instead for 
Did you mean: 

5406zl and 5412zl vlan

New Member

5406zl and 5412zl vlan

Hi All

I'm new to HP ProCurve and have read most doc's and forums about vlan. My vlans are working across 2x5406zl and 1x5412zl.

I'm not sure if my setup is correct and need advise and direction on configuring the vlans on multi switches. They are connected with fibre.

The Core is running 2 vlans. 1 for servers and 1 for pc's. The others are only running 1 vlan for pc's, but need to add a 2nd for wireless devices.

I need to manage each switch. The default gateway on the core is to a Cisco router with routes for each subnet back to the core. The core - servers will allocate dhcp to the different subnets and each subnet is on it's own vlan/switch.

I still need to add the ip helper-address to the vlans for dhcp.

Attach is my config of all 3 switches.

Any help and direction will be appreciated.
Honored Contributor

Re: 5406zl and 5412zl vlan

vlan 1
name "SwitchC"
vlan 1
name "SwitchB"
vlan 1
name "VLAN100"

as you span VLAN1 across several switches, this seems unlogical to do!
Give them the same name "Servers" or "PCs" on all switches.

Use command like :
vlan 1
tagged A2,Trk1
on all ports the connect to annother switch, for all vlans that must cross this connection(s).

so basically for a new vlan, on every switch, add :
name "Wifi"
untagged ...,...
(for edge ports)
tagged ...,...
(for conenction to other switches)
no untagged ...,...
(for all ports you certainly don't want to carry this vlan.)
ip address
(on the core that need to route this vlan.)
ip helper
(on the core switch, that routes to the dhcp-server)

The default gateway on the core is to a Cisco router with routes for each subnet back to the core.
I don't understand that, if the core is routing between the local subnets, it also does the route back!

Re: 5406zl and 5412zl vlan

There is a couple of things that I would like to comment about your configuration.

1. Don't use the Default VLAN (VLAN 1) for anything. It is, if the same as Cisco, switched in software, whereas other VLANs is switched in faster hardware. Also the Default VLAN is used by the switch for things like exchange information about VTP, STP etc.

2. It's considered good practice to have all your VLANs on all your switches (Some Cisco "good" practice. Some like it, some don't)

3. Keep the IP-address subnets consistent across switches.
For example you have on Switch 5406zl (SwitchB) and Switch 5406zl (Alpret_Core).

4. Keep the VLAN names consistent across switches.
For example you have Switch 5406zl (Alpret_Core) VLAN1 name "VLAN100" and Switch 5406zl (SwitchB) VLAN1 name "SwitchB".

5. Make a Management-VLAN that's primary VLAN. The primary VLAN is used for the things like the stacking feature, timep server, the switches management IP-address and more. A good thing to hold away from users data, IMO.

I don't quite get your routes:
Switch 5406zl (SwitchB)
ip default-gateway
ip route vlan 400
That is two default gateways; one going to and one going to vlan 400.


Switch 5406zl (Alpret_Core)
ip route
ip route
ip route vlan 200
ip route vlan 400
ip route vlan 500
You route traffic from a subnet on a VLAN to the same VLAN ?

And then theres RIP... why?

You say you have a Cisco-router to do interVLAN-routing.
What I would do is:
1. Remove all routes at all switches
2. Remove ip routing
3. Configure your Cisco-routers LAN-interface to have a logic/virtual interface for each VLAN.
4. Configure default-gateway on all switches to one IP-address @ the Cisco-routers LAN-interface

Try search for "Router on a stick".

Besides that I would:
* Remove IP-addresses on all VLANs except the management-VLAN
* Remove RIP - not necessary
* Add ip-helper addresses