We have a couple of 6509's that are setup for load-balancing/failover...both have identical vlans with one being a standby and the primary. We're running IEGRP for routing.
My question is, we have a 3750 which all the workstations plug in to...is it generally recommended to set up trunks from the 3750 to the 6509s and have the 6509s be the gateway, or is it better to set up layer 3 links, have the 3750 be the gateway and let EIGRP make all the routing decisions to the 6509s?
The trend these days is to deploy a routed access layer, if the application permits, of course. The reasons for doing so are primarily:
1. To decrease convergenece time in the event of an outage, since routing protocols do converge faster than STP.
2. Minimize the chance of suffering a layer 2 loop, since the switched environemnt will be greatly reduced in size. This is called L3 isolation
3. Traffic load banlancing across equal cost multiple paths -- what Cisco refers to as ECMP.
If you go with the routed access layer design, you must know that you cannot span the user VLANs across the distro/core layer. The VLAN will be confined to the local access switch. If all the users terminate their connections on the same switch, then this could be the way to go.
If you are deploying a collapsed core, i would definitely go with the routed access design.
A switched access layer with L2 trunks uplinked to a routed distro layer does provide more scalabiliaty, especially in the data Center (server farm). But I see your concern is with the campus/user environment.
Feel free to post more concerns/questions. Hope my ramblings helped.
[toc:faq]The ProblemOn traditional switches whenever we have a trunk
interface we use the VLAN tag to demultiplex the VLANs. The switch needs
to determine which MAC Address table to look in for a forwarding
decision. To do this we require the switch to do...
[toc:faq]Introduction:Netdr is a tool available on a RSP720, Sup720 or
Sup32 that allows one to capture packets on the RP or SP inband. The
netdr command can be used to capture both Tx and Rx packets in the
software switching path. This is not a substitut...
IntroductionOSPF, being a link-state protocol, allows for every router
in the network to know of every link and OSPF speaker in the entire
network. From this picture each router independently runs the Shortest
Path First (SPF) algorithm to determine the b...