I agree with routing at the access layer. Just make sure you get all the features you need. Currently, multicast is not supported with IPBASE code but that will be added in an upcoming release. If you are running EIGRP, you can use the stub feature on the IPBASE code and save money. There is a big cost difference between IPBASE and IPSERVICES.

We have 2 pairs of fiber in each closet back to the core. I will setup routing in the access layer this week in my test environment. Would HSRP still be utilized for redundancy between access layer and distribution switches? Any speed issues with intervlan routing if servers are in their own vlan. I agree about the dual supervisors, not sure if the boss will like the pricing. Thanks for your help.

If you route at all layers, no HSRP is needed. Vlan on access switch is the default gateway for the subnet. Load balancing is accomplished by routed uplinks. Inter vlan routing is just as fast as switching--there will be no peformance hit.

Thanks for the response. Any recommendations in terms of the switches in the collapsed core/distribution layer. Obviously I will need enough fiber ports for all of the closets feeding back. Would a 3750 get the job done, or do I need to go with a 4500 series.

Hello,

The switch for collapsed/core distribution layer depends on the number of fiber links and traffic terminating on the core/distribution.

First of all you have to select the design/configuration for the access layer. As you have 60 users per wiring closet that means you require atleast one 48 port and one 24 port switch per closet. If you are using seperate switches per wiring closet, inturn you would need 30 fiber ports per distribution switch.

My Idea for the access switch would be :

1. Use a stack of 3750's one 48 port and one 24 port and inturn run one fiber from eack stack switch to each of the distribution switch.

2. Use cat4503 chassis at each wiring closet which will give you, PS redundancy, more sclability and easy migration to 10GE in future.

Using both the options will use only 15 ports on each distribution/core chassis.

If you are using any of the options above then you can use either 4506 or 4507R chassis at the distri/core layer.If you need an intra-chassis CPU level redundancy then you can use 4507R otherwise 4506 or 4507R with a single CPU will solve your purpose.

HTH,

-amit singh

Excellent. Thank you. Question once the vlans hit the distribution layer/core. What is best practice for routing to a pix firewall/remote sites connected via MPLS. Just static routes on the dist./core switches pointing to those locations. Would I run a routing protocol here? Connection to the MPLS cloud will be a catalyst 3550. MPLS will be up in 3 months or so, that's why I am trying to use money in the budget for equipment/redesign. Also, in this setup, would their be a connection between the 2 distribution switches? Again, thanks for your help.