Thanks for the reply.
I have noticed I made some mistakes and type-o's in my post, some of the IPs are not right according to my diagram but they are fake so it doesn't matter, I suppose. I have added a diagram of what I am changing my network to. I don't have the routers in place yet and all my VLANs are trunked back to my co-lo currently.
I think I understand some what but a bit confused.
1. No really need to run EIGRP on the switches
2. Each router should have a network config for any subnet that is configured on it, inside or outside.
3. Each router should have a default route of the next hop of the "outside" interface
4. Other than the default gateway why would I add static routes? Is that not the point of EIGRP so I dont have to keep up with configuring static routes?
5. My core router should have redistribute static added to the EIGRP table
6. I see you are using different EIGRP AS 101 and 102? I thought I had to use the same AS on my network if I wanted to share all my routes with all my routers.
I am going to have several sub-networks at each of my sites, I am a small service provider and each of my clients get a unique VLAN and public IP block of the size they request. Some clients request NAT services as well thus the sample config I game in my original post.
Thoughts moving forward and thanks again!
- sample-diagram.jpg
- 348 KB
sample diagram
by: mikecrPosted on 2009-08-13 at 20:02:43ID: 25094969
Keep in mind that you need to specifiy the network of the adjacent router also. So if you have a connection of 192.168.192.1 on RouterA and an interface on RouterB that has 192.168.192.2, you need to advertise that network also.
Looks like this:
Outside interface - 192.168.192.1 255.255.255.0
Inside interface - 45.101.128.1 255.255.255.0
router eigrp 101
network 192.168.192.0 0.0.0.255
network 45.101.128.0 0.0.0.255
no auto-summary
Also, you don't have to put EIGRP on your switches, only the router. If you have more than one subnet at a location, advertise it in EIGRP to the rest of the sites. This can be done one of two ways. You either add the network in your Eigrp config or you redistribute static routes.
Looks like this:
router eigrp 102
network 192.168.192.0 0.0.0.255
network 45.101.128.0 0.0.0.255
network 45.117.128.0 0.0.0.255
no auto-summary
Static route on router for next hop to this network.
ip route 45.117.128.0 255.255.255.0 45.101.128.2
OR
router eigrp 102
network 192.168.192.0 0.0.0.255
network 45.101.128.0 0.0.0.255
redistribute static
no auto-summary
Static route on router for this network.
ip route 45.117.128.0 255.255.255.0 45.101.128.2
Either way you get the same net effect. You should try to leave switches as they are. The addage is switch when you can, route when you must. Unless you have multiple networks at the same site and static routes would be excessive, it's best to run it slim with just default gateways configured, no EIGRP. This way you have a high performance network. If you start racking up the subnets then you may have to move that route.
If you have multiple switches on a network with multiple subnets, it is best to create the routable vlans on one switch and make it the core and the rest are trunked to it using VTP. One switch does all the routing between vlans if needed and everything else is fast switched which improves network performance because you don't have all the switches doing a route table lookup just to find out where their going. If you wish, you could put EIGRP on that particular core router and advertise those networks to the router, but like I said, you can get the same net effect just adding them on the router and it takes the burden off the switch to run a routing protocol.