All,
I'm still struggling with some of the frame-relay concept. In the DSG
two multipoint sub-interfaces are used with the same IP subnet:
interface Serial2/0.25 multipoint
ip address 150.100.100.2 255.255.255.0
ip rip authentication mode md5
ip rip authentication key-chain R2R5
frame-relay map ip 150.100.100.5 205 broadcast
!
interface Serial2/0.26 multipoint
ip address 150.100.100.2 255.255.255.0
ip rip authentication mode md5
ip rip authentication key-chain R2R6
frame-relay map ip 150.100.100.6 206 broadcast
But, when we look at the routing table:
R2#sh ip route 150.100.100.5
Routing entry for 150.100.100.0/24
Known via "connected", distance 0, metric 0 (connected, via interface)
Redistributing via rip
Advertised by rip
Routing Descriptor Blocks:
* directly connected, via Serial2/0.26
Route metric is 0, traffic share count is 1
directly connected, via Serial2/0.25
Route metric is 0, traffic share count is 1
R2#sh ip route 150.100.100.6
Routing entry for 150.100.100.0/24
Known via "connected", distance 0, metric 0 (connected, via interface)
Redistributing via rip
Advertised by rip
Routing Descriptor Blocks:
* directly connected, via Serial2/0.26
Route metric is 0, traffic share count is 1
directly connected, via Serial2/0.25
Route metric is 0, traffic share count is 1
two identical routes exist towards a next hop.
The thing that I still can't grasp is the relation between the IP
routing table and the frame-relay map.
>From the routing table point of view there are two identical paths
towards the next hop, yet always the correct path seems to be picked. How?
Regards,
Frank
_______________________________________________
For more information regarding industry leading CCIE Lab training, please visit
www.ipexpert.com
