04-23-2005 01:40 PM - edited 03-02-2019 10:33 PM
I work for a small but fast growing company. We have more than doubled the number of end stations in the past year from 200 to ~ 500. Currently, the network is not properly modularized or configured for redundancy and we need to get a handle on the redundancy issue so we can continue to accomadate our rapid growth.
Our current design is more or less hub and spoke. We have a 6509 w/ dual sups as the core switch. Currently, this is the only L3 switch in the network. Attached to it via vlan trunks are 1 4006 w/ servers connected to it, 1 4006 that acts as an access switch for user workstations and 1 3750 access switch with end stations. I have various smaller switches attached to the 4000's and 3750, but I would consider the 6509, 2 4006's and the 3750 the core of the network.
This month a new building will be coming online. It will have a 4507 with sup IV's (L3) that will act as the access/distribution switch for the building. It too will connect to the 6509.
So, you can see the dilema. If we lose the 6509, we loose almost everything.
I am looking for suggestions on how to clean up this mess.
My initial thought is to replace the 4006 with servers attached to it with a L3 4500. Then, form a L3 triangle backbone out of the two 4500's and 1 6509. I can then attach the 3750 and remaining 4006 to any 2 of the 3 switches that form the backbone, using vlan trunks and HSRP.
My manager thinks we should connect the 6509, new 4500 and the 4000 (with servers) together using VLAN Trunks. He basically wants to form a Layer 2 triangle backbone and use uplinkfast and backbonefast. I don't think this is a very good idea, but I am not sure why, other than it just seems easier to troubleshoot and implement a layer 3 core.
If you have made it this far thanks for taking the time to read this. Any help is greatly appreciated!!
04-28-2005 06:37 AM
If every node of a network is to have network node redundancy, the advanced redundancy management of Ethernet networks has to be taken into consideration, as well as two completely independent networks and two communications ports on connected devices. There are two ways to get two communication ports on your connected devices. If your device already has 2 Ethernet ports, you can label them Port A and Port B. If you use 1-port devices, the devices need to be upgraded to two Ethernet ports for the purpose of determining the primary and secondary homing paths.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide