Support Support Downloads Knowledge Base Apex Support Portal Community

Knowledge Base

Search our Knowledge Base sites to find answers to your questions.

Ask All Knowledge Base Sites All Knowledge Base Sites JunosE Defect (KA)Knowledge BaseSecurity AdvisoriesTechnical BulletinsTechnotes Sign in to display secure content and recently viewed articles

[Junos] Information about the 'Number of data route tunnel through' field in the output of the 'show mpls lsp bypass' command

0

0

Article ID: KB26151 KB Last Updated: 17 Jan 2013Version: 1.0
Summary:
This article provides information about the Number of data route tunnel through field, which is found in the output of the show mpls lsp bypass command.
Symptoms:
Information about the Number of data route tunnel through field, which is found in the output of the show mpls lsp bypass command.
Cause:

Solution:
The Number of data route tunnel through field displays the number of RSVP route entries that are protected by the bypass LSP. The following example describes what a data route is:

Sample configuration of LSP being enabled with node-link protection:
sco@mx-960-3-re0# show logical-systems marton protocols mpls
path-mtu {
    rsvp mtu-signaling;
}
icmp-tunneling;
optimize-timer 120;
label-switched-path MARTONVASAR-TO-SAJOSZOGED {
    to 172.17.0.3;
    ldp-tunneling;
    node-link-protection;
}
interface ge-2/1/8.0;
interface ge-2/0/2.0;
interface ge-2/0/0.0;
interface ge-2/0/1.0;
Output of the MPLS LSP Bypass that is created to protect primary LSP traffic:
sco@mx-960-3-re0# run show mpls lsp bypass logical-system marton extensive
Ingress LSP: 1 sessions

172.17.0.3
From: 172.17.0.22, LSPstate: Up, ActiveRoute: 0
LSPname: Bypass->10.3.22.2
LSPtype: Static Configured
Suggested label received: -, Suggested label sent: -
Recovery label received: -, Recovery label sent: 299792
Resv style: 1 SE, Label in: -, Label out: 299792
Time left: -, Since: Fri Oct 5 16:20:13 2012
Tspec: rate 0bps size 0bps peak Infbps m 20 M 9192
Port number: sender 1 receiver 50258 protocol 0
Type: Bypass LSP
Number of data route tunnel through: 1
Number of RSVP session tunnel through: 0
PATH rcvfrom: localclient
Adspec: sent MTU 4066
Path MTU: received 4066
PATH sentto: 10.22.36.3 (ge-2/0/2.0) 1 pkts
RESV rcvfrom: 10.22.36.3 (ge-2/0/2.0) 1 pkts
Explct route: 10.22.36.3 10.3.36.3
Record route: <self> 10.22.36.3 10.3.36.3
Total 1 displayed, Up 1, Down 0

Egress LSP: 0 sessions
Total 0 displayed, Up 0, Down 0

Transit LSP: 0 sessions
Total 0 displayed, Up 0, Down 0
In the above output, you can see one data route through the bypass tunnel. So what is the data route? The output value indicates the number of RSVP route entries that are protected by the Bypass LSP.

The following output displays the RSVP route in the inet.3 table. So, these entries generally point to the lo0 address on the routers; between which LSP is signalled:
[edit]
sco@mx-960-3-re0# run show route protocol rsvp logical-system marton       

inet.0: 18 destinations, 18 routes (17 active, 0 holddown, 1 hidden)

inet.3: 5 destinations, 8 routes (3 active, 0 holddown, 4 hidden)
+ = Active Route, - = Last Active, * = Both

172.17.0.3/32      *[RSVP/7/1] 5d 22:16:05, metric 1000
                    > to 10.3.22.2 via ge-2/0/1.0, label-switched-path MARTONVASAR-TO-SAJOSZOGED
                      to 10.22.36.3 via ge-2/0/2.0, label-switched-path Bypass->10.3.22.2

iso.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)

mpls.0: 8 destinations, 8 routes (8 active, 0 holddown, 0 hidden)

Now, you will see how the adding of IPv6-tunneling affects the output of the above command:

IPv6-tunneling is now being for LSP:
sco@mx-960-3-re0# show logical-systems marton protocols mpls
path-mtu {
    rsvp mtu-signaling;
}
ipv6-tunneling;
icmp-tunneling;
optimize-timer 120;
label-switched-path MARTONVASAR-TO-SAJOSZOGED {
    to 172.17.0.3;
    ldp-tunneling;
    node-link-protection;
}
interface ge-2/1/8.0;
interface ge-2/0/2.0;
interface ge-2/0/0.0;
interface ge-2/0/1.0;
Now, after enabling IPv6-tunneling, a new RSVP route is added to inet6.3, apart from the existing IPv4 entry in inet.3. The newly added entry has the IPv4 address embedded under IPv6 and this entry is counted towards the New data route under bypass:
[edit]
sco@mx-960-3-re0# run show route logical-system marton table inet6.3       

inet6.3: 3 destinations, 4 routes (3 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

::ffff:1.1.1.4/128 *[LDP/9] 00:04:30, metric 1000
                    > to 10.22.101.3 via ge-2/1/8.0
::ffff:1.1.1.5/128 *[LDP/9] 00:04:21, metric 2000
                    > to 10.3.22.2 via ge-2/0/1.0, label-switched-path MARTONVASAR-TO-SAJOSZOGED
                      to 10.22.36.3 via ge-2/0/2.0, label-switched-path MARTONVASAR-TO-SAJOSZOGED
::ffff:172.17.0.3/128                    *[RSVP/7/1] 00:04:29, metric 1000
                    > to 10.3.22.2 via ge-2/0/1.0, label-switched-path MARTONVASAR-TO-SAJOSZOGED
                      to 10.22.36.3 via ge-2/0/2.0, label-switched-path Bypass->10.3.22.2
                    [LDP/9] 00:04:21, metric 1000
                    > to 10.3.22.2 via ge-2/0/1.0, label-switched-path MARTONVASAR-TO-SAJOSZOGED
                      to 10.22.36.3 via ge-2/0/2.0, label-switched-path MARTONVASAR-TO-SAJOSZOGED
The ouput of the show mpls bypass LSP command displays the value of 2 for the number of data routes, which takes into account the newly created IPv6 address:
sco@mx-960-3-re0# ...how mpls lsp bypass logical-system marton extensive
Ingress LSP: 1 sessions

172.17.0.3
From: 172.17.0.22, LSPstate: Up, ActiveRoute: 0
LSPname: Bypass->10.3.22.2
LSPtype: Static Configured
Suggested label received: -, Suggested label sent: -
Recovery label received: -, Recovery label sent: 299792
Resv style: 1 SE, Label in: -, Label out: 299792
Time left: -, Since: Fri Oct 5 16:20:13 2012
Tspec: rate 0bps size 0bps peak Infbps m 20 M 9192
Port number: sender 1 receiver 50258 protocol 0
Type: Bypass LSP
Number of data route tunnel through: 2
Number of RSVP session tunnel through: 0
PATH rcvfrom: localclient
Adspec: sent MTU 4066
Path MTU: received 4066
PATH sentto: 10.22.36.3 (ge-2/0/2.0) 1 pkts
RESV rcvfrom: 10.22.36.3 (ge-2/0/2.0) 1 pkts
Explct route: 10.22.36.3 10.3.36.3
Record route: <self> 10.22.36.3 10.3.36.3
Total 1 displayed, Up 1, Down 0

Egress LSP: 0 sessions
Total 0 displayed, Up 0, Down 0

Transit LSP: 0 sessions
Total 0 displayed, Up 0, Down 0
Note: Using the 'install' command under LSP to add the IPv4 prefix will cause the above counter to increment, based on the number of prefixes being protected by LSP.
Comment on this article > Affected Products Browse the Knowledge Base for more articles related to these product categories. Select a category to begin.

Getting Up and Running with Junos

Getting Up and Running with Junos Security Alerts and Vulnerabilities Product Alerts and Software Release Notices Problem Report (PR) Search Tool EOL Notices and Bulletins JTAC User Guide Customer Care User Guide Pathfinder SRX High Availability Configurator SRX VPN Configurator Training Courses and Videos End User Licence Agreement Global Search