deddard
03-16-2005, 08:17 PM
Anyone know any links where I can get some info on where to find details about hardware and configs for Cisco routers and switches in a multi-layer switched network, specifically building redundant routing links?
Here's the problem:
In the final semester of CCNA Cisco Network Academy. As part of the course we design a WAN. two of the LANs within the wan are pretty large - the largest is 750 nodes. The case study calls for fairly basic stuff just showing one switch connected to the router, divided into VLANs - this is no problem, we can do this bit in our sleep.
However, as an aside (it isn't required for the case study,- we just like to know 'how and why!') we've decided that when we create the logical diagrams/ costing etc, we would actually like to know how to implement redundancy.
our basic design goes something like
Core router
I
I
Distribution layer router
I
I
Access layer switches
I
I
Hosts
In real life this simple scenario wouldn't be acceptable, as the vlans couldn't trunk without a router interface, and if they only had a single interface to talk to (i.e. one router) then they wouldn't be able to communicate between vlans.
what we'd like to know is how to configure something like the following:
**************Core router
************* I ****** I
Distribution Router1*****Distribution Router 2
****** I************* I
******Access layer switches
The 'I' represents a link. the '*' is just to space the diagram out!
The problem we see is that both routers need to route for the same subnets, which would tie them up in knots using normal configs
Any pointers to how we could get this to work? (links to relevant sites would be great)
I know - we must be mad going into it this far if we don't need to, but if a job's worth doing (even if it is CCNP stuff!) it's worth doing well.
Here's the problem:
In the final semester of CCNA Cisco Network Academy. As part of the course we design a WAN. two of the LANs within the wan are pretty large - the largest is 750 nodes. The case study calls for fairly basic stuff just showing one switch connected to the router, divided into VLANs - this is no problem, we can do this bit in our sleep.
However, as an aside (it isn't required for the case study,- we just like to know 'how and why!') we've decided that when we create the logical diagrams/ costing etc, we would actually like to know how to implement redundancy.
our basic design goes something like
Core router
I
I
Distribution layer router
I
I
Access layer switches
I
I
Hosts
In real life this simple scenario wouldn't be acceptable, as the vlans couldn't trunk without a router interface, and if they only had a single interface to talk to (i.e. one router) then they wouldn't be able to communicate between vlans.
what we'd like to know is how to configure something like the following:
**************Core router
************* I ****** I
Distribution Router1*****Distribution Router 2
****** I************* I
******Access layer switches
The 'I' represents a link. the '*' is just to space the diagram out!
The problem we see is that both routers need to route for the same subnets, which would tie them up in knots using normal configs
Any pointers to how we could get this to work? (links to relevant sites would be great)
I know - we must be mad going into it this far if we don't need to, but if a job's worth doing (even if it is CCNP stuff!) it's worth doing well.