HP PROCURVE INTER VLAN ROUTING

TFGreen
TFGreen used Ask the Experts™
on
I inherited a very large network about 3 years ago that was in a variety of messes.  Over that time I have cleaned things up and tuned it to where it works and functions wonderfully.  Everything is in working order and spanning tree is working perfectly.  

HOWEVER

What I inherited is a big network with mostly everything on vlan 1 and oh, did I happen to mention everything on a /16 network mask  - oh the horrors.

So things are at the point now where I need to start segmenting the network with various vlans and subnets, so the fun begins for me.

I've come up with a common concept like most business would use and I'll be vlanning the network initially by putting each switch on its own vlan  and untagging / tagging the appropriate ports and uplinks as needed.  In this scenario each switch will be its own broadcast domain.  

The network is mostly 8212zl / 8206zl / 6506zl based switches, there is NO intervlan routing now.  

I have labbed up 2 - 5406zl switches and put 2 vlans on one and 2 vlans on the other.

The ultimate goal of intervlan routing for us will be for the subnets to get to the dhcp servers with ip helper statements so they get the appropriate addresses and or course to ultimately get to the internet.  All pcs gurrently use the same gateway today.  In the future they will be using the vlan address as their gateway.

I have attached the configs from both switches so you can see where I am going with this.

I don't want a router on a stick solution.

Thanks in advance for any helpful recommendation you can give me to implement inter vlan routing.


our internet firewall / load balancer is a virtual device - a Fortigate VM with an address of 10.1.0.200 which we use now as the gateway on all pc's.

thanks in advance.
vlan3040
vlan1020
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Datacenter Technician
Top Expert 2012
Commented:
The very basic version would be:
- decide on a core device
- set up all vlans on core
- only give IPs to all vlan interfaces on core
- set up core with default route to fortigate
- check IP routing is enabled on core
- set the addresses of core as the gw of the subnets
- implement ip helpers for dhcp as needed
- connect switches to core with vlan trunks

What you do not want to do (most likely)(in this case):
- assign IP addresses to every vlan on every switch
- enable IP routing on every switch
- dynamic routing

Tamas

Author

Commented:
That is exactly what I thought and will do - thank you so much.

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial