Where does 2 subnets come from

[Amafsha1]

Hello,  

I have 2 different /24 subnets I'm working with here, but why am I getting such different route types?

What is the difference between these 2 subnets?

WAN# sh ip route 172.29.94.0

Routing entry for 172.29.94.0/24
Known via "static", distance 1, metric 0
Redistributing via bgp 65425
Advertised by bgp 65425
Routing Descriptor Blocks:
172.31.255.6
Route metric is 0, traffic share count is 1
* 172.31.255.2
Route metric is 0, traffic share count is 1

WAN#sh ip route 172.29.93.0
Routing entry for 172.29.93.0/24
Known via "eigrp 1", distance 170, metric 25600512
Tag 65520, type external
Redistributing via bgp 65425, eigrp 1
Advertised by bgp 65425 route-map eigrp-to-bgp
Last update from 172.31.255.2 on GigabitEthernet0/0/2, 2d04h ago
Routing Descriptor Blocks:
* 172.31.255.2, from 172.31.255.2, 3d04h ago, via GigabitEthernet0/0/2
Route metric is 25600512, traffic share count is 1
Total delay is 20 microseconds, minimum bandwidth is 100 Kbit
Reliability 255/255, minimum MTU 1500 bytes
Loading 7/255, Hops 1
Route tag 65520

[Seb Rupik]

Hi there,
Both routes have been installed in the routing table by different means.
We can see that 172.29.94.0/24 is a static route which has next-hop IP addresses 172.31.255.6 and 172.31.255.2 . Both have an equal metric so the router will load-balance between them. The asterisk denotes that 172.31.255.2 is currently the active route for new traffic. There are two types of load-balancing 'process-switching' and 'fast-switching'. You will notice that the asterisk will keep rotating between the two entries.

172.29.93.0/24 has been learnt by an dynamic routing protocol, namely EIGRP. As such you get significantly more information. Further information can be gained from querying the EIGRP process itself.
We can see that there is only one next-hop for this destination subnet.


cheers,
Seb.

[Amafsha1]

ok thank you for explaining.  I just have one more question.  That last ip route I showed you was on our bgp mpls wan router.  Now, I move 1 hop down to the core where all our svis and routing happens.  Now on the core I type in the show ip routes again for those same subnets

So is the core saying that any packet destined for 172.29.93.0 needs to go to through the 172.31.255.5 interface E2/23 in that direction?  and for the 172.29.94.0 does that mean that we don't have an entry specificially for the 172.29.94.0/24 network in the routing table, so it gets classified as 0.0.0.0 and heads to 163.15.15.2, which is our firewall address.   Am I on the right page here?

CORE# sh ip route ip 172.29.93.0
IP Route Table for VRF "default"
'*' denotes best ucast next-hop
'**' denotes best mcast next-hop
'[x/y]' denotes [preference/metric]
'%<string>' in via output denotes VRF <string>

172.29.93.0/24, ubest/mbest: 1/0
*via 172.31.255.5, Eth2/23, [170/25600768], 3d20h, eigrp-1, external, tag 65520

CORE# sh ip route ip 172.29.94.0
IP Route Table for VRF "default"
'*' denotes best ucast next-hop
'**' denotes best mcast next-hop
'[x/y]' denotes [preference/metric]
'%<string>' in via output denotes VRF <string>

0.0.0.0/0, ubest/mbest: 1/0
*via 163.15.15.2, [1/0], 1y1w, static