07-29-2003 04:25 AM - edited 03-02-2019 09:11 AM
When configuring the eigrp aggregate on an interface, eigrp create sends the aggregated route to neighbor and installed the route for that aggregated subnet to point to Null0 interface with admin distance of 5.
The bandwidth and delay factors that are used to calculate the metrics. Does anyone know where those factors come from. Looks like these numbers are different for different aggregated subnets too.
Thanks,
Hung
07-29-2003 04:38 AM
The bandwidth and delay should be the bandwidth and delay of the lowest cost metric among the components. So, for instance, notice there are two loopback interfaces on this router:
interface Loopback0
bandwidth 1000
ip address 144.1.1.1 255.255.255.255
delay 500
!
interface Loopback1
ip address 144.1.2.2 255.255.255.255
!
The bandwidth and delay are set on one, and not on the other. If we look in the topo table, we see:
2651A#sho ip eigrp topo 144.1.1.1/32
IP-EIGRP (AS 100): Topology entry for 144.1.1.1/32
State is Passive, Query origin flag is 1, 1 Successor(s), FD is 2688000
Routing Descriptor Blocks:
0.0.0.0 (Loopback0), from Connected, Send flag is 0x0
Composite metric is (2688000/0), Route is Internal
Vector metric:
Minimum bandwidth is 1000 Kbit
Total delay is 5000 microseconds
Reliability is 255/255
Load is 1/255
Minimum MTU is 1514
Hop count is 0
2651A#sho ip eigrp topo 144.1.2.2/32
IP-EIGRP (AS 100): Topology entry for 144.1.2.2/32
State is Passive, Query origin flag is 1, 1 Successor(s), FD is 128256
Routing Descriptor Blocks:
0.0.0.0 (Loopback1), from Connected, Send flag is 0x0
Composite metric is (128256/0), Route is Internal
Vector metric:
Minimum bandwidth is 10000000 Kbit
Total delay is 5000 microseconds
Reliability is 255/255
Load is 1/255
Minimum MTU is 1514
Hop count is 0
They have two different metrics. The discard route generated by the autosummary code says this:
2651A#sho ip eigrp topo 144.1.0.0
IP-EIGRP (AS 100): Topology entry for 144.1.0.0/16
State is Passive, Query origin flag is 1, 1 Successor(s), FD is 128256
Routing Descriptor Blocks:
0.0.0.0 (Null0), from 0.0.0.0, Send flag is 0x0
Composite metric is (128256/0), Route is Internal
Vector metric:
Minimum bandwidth is 10000000 Kbit
Total delay is 5000 microseconds
Reliability is 255/255
Load is 1/255
Minimum MTU is 1514
Hop count is 0
It chose the lower of the two metrics. As for the other loopback, without any metric defined, where did that metric come from? For each interface type, there is a defined bandwidth and delay. For the loopback interface, we can see what those are by looking at show interface on the loopback interface defined:
2651A#show int lo0
Loopback0 is up, line protocol is up
Hardware is Loopback
Internet address is 144.1.1.1/32
MTU 1514 bytes, BW 1000 Kbit, DLY 5000 usec,
reliability 255/255, txload 1/255, rxload 1/255
....
All of the above applies to manually generated aggregates, as well as automatically created ones. For static routes pointing out an interface, EIGRP will pick up the bandwidth and delay of the interface the route points out.
Russ.W
07-29-2003 04:39 AM
Teh admin distance of 5 is defaulkt for the summary address in EIGRP , AD is only locally significant to that router , when you are summarizing on a router once traffic destined for one of the subnets you are summarizing arrives at that router it assumes there will be a more specific router on that router.
For example say uou have the command ip summary address 192.168.0.0 255.255.252.0 configured , this summarizes 192.168.0.0 to 192.168.3.0 . Any traffic destined to 192.168.0.0-192.168.3.255 will go to the interface that the summary address is applied on , If there is a more specific route then the traffic wil lbe forwarded if not traffic is router to null 0
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