[j-nsp] MX5-T logical-routers question
Magnus Bergroth
bergroth at nordu.net
Tue May 22 09:58:20 EDT 2012
Juniper has a bug in their LT interface implementation on MX80 in 11.4,
that misses to decrement ttl on logical tunnel interfaces. That's why
you don't see R2 in the traceroute. They haven't released in which
version they are going to fix it yet.
Kindly
Magnus
On 2012-05-22 14:32, Mihai Gabriel wrote:
> Hello,
>
> I am trying to test some features with an MX5-T router with
> logical-systems but my results are below expectations and I don't
> understand what's wrong.
> The topology and the config are very simple: R1 --- R2 ---R3 :
>
>
> mx5t# run show version
>
> Hostname: mx5t
> Model: mx5-t
> JUNOS Base OS boot [11.4R2.14]
> JUNOS Base OS Software Suite [11.4R2.14]
> JUNOS Kernel Software Suite [11.4R2.14]
> JUNOS Packet Forwarding Engine Support (MX80) [11.4R2.14]
> JUNOS Online Documentation [11.4R2.14]
> JUNOS Routing Software Suite [11.4R2.14]
>
> mx5t# show chassis
>
> fpc 1 {
> pic 0 {
> tunnel-services {
> bandwidth 1g;
> }
> inactive: adaptive-services {
> service-package layer-2;
> }
> }
> pic 1 {
> tunnel-services {
> bandwidth 1g;
> }
> }
> }
> network-services ip;
>
> mx5t# show R1
> interfaces {
> lt-1/1/10 {
> unit 12 {
> encapsulation ethernet;
> peer-unit 21;
> family inet {
> address 10.10.10.1/24;
> }
> family iso;
> family mpls;
> }
> }
> lo0 {
> unit 1000 {
> family inet {
> address 1.1.1.1/32;
> }
> family iso {
> address 49.0001.1111.1111.00;
> }
> }
> }
> }
> protocols {
> rsvp {
> interface all;
> }
> mpls {
> label-switched-path mihai {
> to 3.3.3.3;
> no-cspf;
> }
> interface all;
> }
> isis {
> interface all;
> }
> }
>
> mx5t# show R2
> interfaces {
> lt-1/1/10 {
> unit 21 {
> encapsulation ethernet;
> peer-unit 12;
> family inet {
> address 10.10.10.2/24;
> }
> family iso;
> family mpls;
> }
> unit 23 {
> encapsulation ethernet;
> peer-unit 32;
> family inet {
> address 10.10.20.2/24;
> }
> family iso;
> family mpls;
> }
> }
> lo0 {
> unit 1001 {
> family inet {
> address 2.2.2.2/32;
> }
> family iso {
> address 49.0001.2222.2222.00;
> }
> }
> }
> }
> protocols {
> rsvp {
> interface all;
> }
> mpls {
> interface all;
> }
> isis {
> interface all;
> }
> }
>
> mx5t# show R3
> interfaces {
> lt-1/1/10 {
> unit 32 {
> encapsulation ethernet;
> peer-unit 23;
> family inet {
> address 10.10.20.3/24;
> }
> family iso;
> family mpls;
> }
> }
> lo0 {
> unit 1003 {
> family inet {
> address 3.3.3.3/24;
> }
> family iso {
> address 49.0001.3333.3333.00;
> }
> }
> }
> }
> protocols {
> rsvp {
> interface all;
> }
> mpls {
> interface all;
> }
> isis {
> interface all;
> }
> }
>
>
> While a ping from R1 loopback to R3 loopback is successful , a traceroute
> from R1 to R3 doesn't show the transit router R2 (I tried with and without
> mpls), and a lsp from R1 to R3 is failing to come up.
>
> x5t# run show route logical-system R1
>
> inet.0: 7 destinations, 7 routes (7 active, 0 holddown, 0 hidden)
> + = Active Route, - = Last Active, * = Both
>
> 1.1.1.1/32 *[Direct/0] 01:07:53
> > via lo0.1000
> 2.2.2.2/32 *[IS-IS/15] 01:02:44, metric 10
> > to 10.10.10.2 via lt-1/1/10.12
> 3.3.3.0/24 *[IS-IS/15] 01:02:20, metric 20
> > to 10.10.10.2 via lt-1/1/10.12
> 3.3.3.3/32 *[IS-IS/15] 01:02:20, metric 20
> > to 10.10.10.2 via lt-1/1/10.12
> 10.10.10.0/24 *[Direct/0] 01:07:53
> > via lt-1/1/10.12
> 10.10.10.1/32 *[Local/0] 01:07:53
> Local via lt-1/1/10.12
> 10.10.20.0/24 *[IS-IS/15] 01:02:44, metric 20
> > to 10.10.10.2 via lt-1/1/10.12
>
> iso.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)
> + = Active Route, - = Last Active, * = Both
>
> 49.0001.1111.1111/56
> *[Direct/0] 01:02:59
> > via lo0.1000
>
> mpls.0: 3 destinations, 3 routes (3 active, 0 holddown, 0 hidden)
> + = Active Route, - = Last Active, * = Both
>
> 0 *[MPLS/0] 01:00:09, metric 1
> Receive
> 1 *[MPLS/0] 01:00:09, metric 1
> Receive
> 2 *[MPLS/0] 01:00:09, metric 1
> Receive
>
> mx5t# run show route logical-system R2
>
> inet.0: 8 destinations, 8 routes (8 active, 0 holddown, 0 hidden)
> + = Active Route, - = Last Active, * = Both
>
> 1.1.1.1/32 *[IS-IS/15] 01:03:04, metric 10
> > to 10.10.10.1 via lt-1/1/10.21
> 2.2.2.2/32 *[Direct/0] 01:08:13
> > via lo0.1001
> 3.3.3.0/24 *[IS-IS/15] 01:02:40, metric 10
> > to 10.10.20.3 via lt-1/1/10.23
> 3.3.3.3/32 *[IS-IS/15] 01:02:40, metric 10
> > to 10.10.20.3 via lt-1/1/10.23
> 10.10.10.0/24 *[Direct/0] 01:08:13
> > via lt-1/1/10.21
> 10.10.10.2/32 *[Local/0] 01:08:13
> Local via lt-1/1/10.21
> 10.10.20.0/24 *[Direct/0] 01:08:13
> > via lt-1/1/10.23
> 10.10.20.2/32 *[Local/0] 01:08:13
> Local via lt-1/1/10.23
>
> iso.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)
> + = Active Route, - = Last Active, * = Both
>
> 49.0001.2222.2222/56
> *[Direct/0] 01:03:19
> > via lo0.1001
>
> mpls.0: 3 destinations, 3 routes (3 active, 0 holddown, 0 hidden)
> + = Active Route, - = Last Active, * = Both
>
> 0 *[MPLS/0] 01:00:29, metric 1
> Receive
> 1 *[MPLS/0] 01:00:29, metric 1
> Receive
> 2 *[MPLS/0] 01:00:29, metric 1
> Receive
>
> mx5t# run show route logical-system R3
>
> inet.0: 7 destinations, 7 routes (7 active, 0 holddown, 0 hidden)
> + = Active Route, - = Last Active, * = Both
>
> 1.1.1.1/32 *[IS-IS/15] 01:02:41, metric 20
> > to 10.10.20.2 via lt-1/1/10.32
> 2.2.2.2/32 *[IS-IS/15] 01:02:50, metric 10
> > to 10.10.20.2 via lt-1/1/10.32
> 3.3.3.0/24 *[Direct/0] 01:08:23
> > via lo0.1003
> 3.3.3.3/32 *[Local/0] 01:08:23
> Local via lo0.1003
> 10.10.10.0/24 *[IS-IS/15] 01:02:50, metric 20
> > to 10.10.20.2 via lt-1/1/10.32
> 10.10.20.0/24 *[Direct/0] 01:08:23
> > via lt-1/1/10.32
> 10.10.20.3/32 *[Local/0] 01:08:23
> Local via lt-1/1/10.32
>
> iso.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)
> + = Active Route, - = Last Active, * = Both
>
> 49.0001.3333.3333/56
> *[Direct/0] 01:03:29
> > via lo0.1003
>
> mpls.0: 3 destinations, 3 routes (3 active, 0 holddown, 0 hidden)
> + = Active Route, - = Last Active, * = Both
>
> 0 *[MPLS/0] 01:00:39, metric 1
> Receive
> 1 *[MPLS/0] 01:00:39, metric 1
> Receive
> 2 *[MPLS/0] 01:00:39, metric 1
> Receive
>
> mx5t# run ping logical-system R1 3.3.3.3 source 1.1.1.1
> PING 3.3.3.3 (3.3.3.3): 56 data bytes
> 64 bytes from 3.3.3.3: icmp_seq=0 ttl=64 time=0.521 ms
> 64 bytes from 3.3.3.3: icmp_seq=1 ttl=64 time=0.493 ms
> 64 bytes from 3.3.3.3: icmp_seq=2 ttl=64 time=0.524 ms
> 64 bytes from 3.3.3.3: icmp_seq=3 ttl=64 time=0.497 ms
> ^C
> --- 3.3.3.3 ping statistics ---
> 4 packets transmitted, 4 packets received, 0% packet loss
> round-trip min/avg/max/stddev = 0.493/0.509/0.524/0.014 ms
>
> mx5t# run traceroute logical-system R1 3.3.3.3
> traceroute to 3.3.3.3 (3.3.3.3), 30 hops max, 40 byte packets
> 1 3.3.3.3 (3.3.3.3) 0.948 ms 4.208 ms 0.448 ms
>
> mx5t# run show mpls lsp extensive logical-system R1
> Ingress LSP: 1 sessions
>
> 3.3.3.3
> From: 1.1.1.1, State: Dn, ActiveRoute: 0, LSPname: mihai
> ActivePath: (none)
> LSPtype: Static Configured
> LoadBalance: Random
> Encoding type: Packet, Switching type: Packet, GPID: IPv4
> Primary State: Dn
> Priorities: 7 0
> SmartOptimizeTimer: 180
> 1 May 22 14:35:12.385 Originate Call
> Created: Tue May 22 14:35:11 2012
> Total 1 displayed, Up 0, Down 1
>
> mx5t# run show mpls lsp extensive logical-system R3
> Ingress LSP: 0 sessions
> Total 0 displayed, Up 0, Down 0
>
> Egress LSP: 1 sessions
>
> 3.3.3.3
> From: 1.1.1.1, LSPstate: Up, ActiveRoute: 0
> LSPname: mihai, LSPpath: Primary
> Suggested label received: -, Suggested label sent: -
> Recovery label received: -, Recovery label sent: -
> Resv style: 1 FF, Label in: 3, Label out: -
> Time left: 152, Since: Tue May 22 14:35:12 2012
> Tspec: rate 0bps size 0bps peak Infbps m 20 M 1500
> Port number: sender 1 receiver 55769 protocol 0
> PATH rcvfrom: 10.10.10.1 (lt-1/1/10.32) 81 pkts
> Adspec: received MTU 1500
> PATH sentto: localclient
> RESV rcvfrom: localclient
> Record route: 10.10.10.1 <self>
> Total 1 displayed, Up 1, Down 0
>
>
> Do I miss something or my box is crazy?:)
>
> Regards
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
More information about the juniper-nsp
mailing list