Labeled traffic using ISIS L1 Default Route?
Guys,
Is it possible to have Labeled traffic using ISIS L1 Default Route (or any default route)? I guess the only way is to route-leak?
I tried "mpls ip default-route" and it doesn't work.
! Network:
R3
| |
R1 XR1
| |
R2 - XR2
!
! Network Setup:
!! ISIS + LDP b/w R1-R2-XR1-XR2 with R2 in L1 and rest L2
XR1=19.0.0.1
! Before
R2#show mpls forwarding-table
Local Outgoing Prefix Bytes Label Outgoing Next Hop
Label Label or Tunnel Id Switched interface
R2#
R2#show run | i default
mpls ip default-route
R2#show mpls fo
R2#show mpls forwarding-table
Local Outgoing Prefix Bytes Label Outgoing Next Hop
Label Label or Tunnel Id Switched interface
16 No Label 0.0.0.0/0 0 Gi0/2 10.0.12.1
No Label 0.0.0.0/0 0 Gi0/1 10.0.220.20
R2#
R2#traceroute 19.0.0.1 source lo0
Type escape sequence to abort.
Tracing the route to 19.0.0.1
VRF info: (vrf in name/id, vrf out name/id)
1 10.0.220.20 3 msec
10.0.12.1 2 msec
10.0.220.20 2 msec
2 10.0.119.19 2 msec
10.19.20.19 2 msec *
R2#
Comments
Your LDP peer should be known in the rib via a host route
So I guess even in case of static default-route (ip route 0.0.0.0 0.0.0.0), we need a host route (either via IGP or static route to host, like ip route 1.1.1.1 255.255.255.255 NH)?
I can't remember the precise command, but on XR you can issue a command for labeling the default route. Did you try it out?
conf t
mpls ldp
default ( and then i do not remember [:P] )
end
yes
!
Alessio
Hey,
No such command. Also, "mpls ip default-route" doesn't work. I tested it on IOS. For XR, its "mpls ldp default-route" which i haven't tested. Any case, its better to have specific routes that default route when dealing with LDP (or MPLS labeling in general)
You're absolutely right.
Longest match plays its role always and in everywhere (but multicast static routing [:(] )