I have inherited a large govt based hp procurve network with a flattened core of 10 5406zl switches and number other layer 2 switches. Over the last year I have had to fix and standardize many things like spanning tree and I have installed all these on a 10 gig uplinks. When I look in the switch configs most everything is running on the default vlan 1 so we have a huge broadcast domain. My predecessor has all sorts of RIP, OSPF, and static routing going on that in some cases is bouncing the data all over the place for no reason until it finally hits a switch to get them out to the internet or to somewhere that makes sense. So while I have made a ton of progress here I would like to take this to the next level and get the vlans established, and get the routing and the ip default-gateway set to a best practices standard. My question here revolves around what other professionals would consider best practices on getting things set up correctly here. For example - should the vlans on all switches have an ip address or should the vlan ip addresses be only on the core switch vlans? Where should the default route on all switches point to? Is there a need to use an ip default-gateway? I'm making an assumption here that we have a top of broadcast traffic arping the whole network. Looking forward to wveryone opinion as to maybe how they may have their procurve network set up that might help me get mine in proper order. In our case we are using several cisco asa's and a fortinet virtual firewall. The fortinet is doing multiple isp load balancing and is currently the pc's default gateway and the default route (the 0.0.0.0 route) on most of the switches in the network. thanks in advance.
