I have hub router with various spokes on serial links to other networks in the same AS number, but off this hub router I have a fa link to a RIP to network. The RIP network has a large routing table but all route back to this hub, can I advertise a default route or do something elase to keep it dynamic?
ip address 22.214.171.124 255.255.255.252
ip address 126.96.36.199 255.255.255.0
no ip split-horizon eigrp 100
no ip split-horizon eigrp 40
clock rate 2000000
frame-relay map ip 188.8.131.52 122 broadcast
frame-relay map ip 184.108.40.206 123 broadcast
no frame-relay inverse-arp
router eigrp 100
redistribute rip metric 100 100 255 1 1500
network 220.127.116.11 0.0.0.0
network 10.10.10.0 0.0.0.255
network 18.104.22.168 0.0.0.255
redistribute connected metric 1
redistribute eigrp 100 metric 2
Rip Spoke network
ip address 22.214.171.124 255.255.255.252
I guess I could just add a default route on the RIP router and remote the RIP router config.
There are several things in this config that puzzle me. And I can not be sure how they might relate to the question that you are asking about reducing the size of the routing table.
- the split horizon configurations mention both eigrp 40 and 100. But the config has only 100. What is eigrp 40? What does it do? How does it relate to this network?
- router eigrp configuration has network statements for networks 126.96.36.199 and for 10.10.10.0 but no interfaces with these addresses. So what are these addresses and how do they relate to this network?
Given what you have described I believe that you do not need to redistribute eigrp into rip. There is no need to advertise the eigrp learned routes out to the RIP spoke. You just need to be sure that the RIP spoke has a default route pointing back to the hub. It is more difficult to determine what needs to be done on the hub router in terms of the RIP networks. One alternative could be to continue to run RIP on the hub router so that it dynamically learns the routes from the spoke, and perhaps redistributes them into eigrp so that the other spokes learn the networks from the RIP side. Or perhaps you could configure a static route that summarizes the RIP routes and just redistribute that into eigrp so that the eigrp spokes are aware of that network.
Sorry to confuse you, it was my fault as the 188.8.131.52 is just a loopback I'm advertising to other networks and the eigrp 40 is an old network I was testing with that hung off another eigrp spoke.
Just another question, on another network a site is OSPF and has a spoke that is connected to area 0 via a virtual link, I want to make it a totally stub area to reduce the routing table, but I can't if it is a virtual link, so what options do I have?
The option that comes to mind would be to configure a GRE tunnel from the spoke to a router that does have an area 0 connection. You could then configure the spoke as being in its own totally stub area. From a technical perspective I know that this would work. Whether it would achieve what you really want, and how it would change traffic flows is something that you will need to evaluate as you decide whether this is a good option for you.
Question We run asr9001 with XR 6.1.3, and we have a very long delay to
login w/ SSH 1 or 2 to the device compare to IOS device. After
investigation, the there is 1s delay between the client KEXDH_INIT and
the server (XR) KEXDH_REPLY. After debug ssh serv...
Introduction The purpose of this document is to demonstrate the Open
Shortest Path First (OSPF) behavior when the V-bit (Virtual-link bit) is
present in a non-backbone area. The V-bit is signaled in Type-1 LSA only
if the router is the endpoint of one or ...
Hi, I am seeing quite a few issues with patch install and wanted to
share my experience and workaround to this. Login to admin via CLI, then
access root with the “shell” command Issue “df –h” and you’ll probably
see the following directory full or nearly ...