Related Documentation
- M, MX, PTX, T Series
- Point-to-Multipoint LSPs Overview in the Junos OS MPLS Applications Configuration Guide
Example: Configuring an RSVP-Signaled Point-to-Multipoint LSP on Logical Systems
In this example, multiple logical systems in a physical router act as a collection of paths for an RSVP-signaled point-to-multipoint LSP. The logical systems are chained together and connected internally over a series of logical tunnel (lt) interfaces.
Requirements
This example uses the following hardware and software components:
- One MX Series router running logical systems. You do not need to use an MX Series router for the logical systems. You can use any Juniper Networks router that supports logical systems.
- On the MX Series router, the logical systems are connected using logical tunnel (lt) interfaces. For more information, see Example: Connecting Logical Systems Within the Same Router Using Logical Tunnel Interfaces on MX Series Routers and Example: Connecting Logical Systems Within the Same Router Using Logical Tunnel Interfaces. An alternative to using lt interfaces is to create external back-to-back interconnections between ports on the router.
- Four customer-edge (CE) devices running in separate physical devices. You do not need to use routers for the CE devices. For example, the CE devices can be EX Series Ethernet Switches.
- Junos OS Release 12.1 or later running on the MX Series router.
On M Series Multiservice Edge and T Series Core Routers, you can create an lt interface if you have a Tunnel Services PIC installed on an Enhanced FPC in your routing platform.
On M40e routers, you can create an lt interface if you have a Tunnel Services PIC. (An Enhanced FPC is not required.)
On an M7i router, lt interfaces can be created by using the integrated Adaptive Services Module.
On an MX Series router, as is shown in this example, the master administrator can configure lt interfaces by including the tunnel-services statement at the [edit chassis fpc slot-number pic number] hierarchy level.
Overview
In this example, the logical systems serve as the transit, branch, and leaf nodes of a single point-to-multipoint LSP. Logical system LS1 is the ingress node. The branches go from LS1 to LS5, LS1 to LS7, and LS1 to LS4. Static unicast routes on the ingress node (LS1) point to the egress nodes.
The following topologies are supported:
- A single logical system in a physical router. The logical system is one node in an RSVP-signaled point-to-multipoint LSP.
- Multiple logical systems in a physical router, with each logical system acting as a label-switched router (LSR). The multiple logical systems can be unconnected, connected to each other internally with lt interfaces, or connected to each other externally with back-to-back connections.
- One RSVP-signaled point-to-multipoint LSP, with some nodes being logical systems and other nodes being physical routers.
Topology Diagram
Figure 1 shows the topology used in this example.
Figure 1: RSVP-Signaled Point-to-Multipoint LSP on Logical Systems

Configuration
- Configuring the MX Series Router to Support Logical Tunnel Interfaces
- Configuring the Ingress LSR (Logical System LS1)
- Configuring the Transit and Egress LSRs (Logical Systems LS2, LS3, LS4, LS5, LS6, and LS7)
- Configuring Device CE1
- Configuring Device CE2
- Configuring Device CE3
- Configuring Device CE4
CLI Quick Configuration
To quickly configure this example, copy the following commands, paste them into a text file, remove any line breaks, change any details necessary to match your network configuration, and then copy and paste the commands into the CLI at the [edit] hierarchy level.
Router R1
Device CE1
Device CE2
Device CE3
Device CE4
Configuring the MX Series Router to Support Logical Tunnel Interfaces
Step-by-Step Procedure
The following example requires you to navigate various levels in the configuration hierarchy. For information about navigating the CLI, see Using the CLI Editor in Configuration Mode in the CLI User Guide.
This procedure is required for MX Series routers only. If you have an M Series or T Series router, skip this procedure.
To enable lt interfaces on the MX Series router:
- Run the show chassis fpc command to verify that
the router has a DPC, MPC, or MIC installed and is in the online state.
user@host> show chassis fpc
Temp CPU Utilization (%) Memory Utilization (%) Slot State (C) Total Interrupt DRAM (MB) Heap Buffer 0 Empty 1 Empty 2 Online 31 3 0 1024 14 21
This output shows that slot 0 and slot 1 are empty. Slot 2 is online.
- This command creates several tunnel interface types, including gr, ip, and lt. For this example, the important one is the lt interface.
Configure FPC slot 2 to support lt interfaces.
[edit]user@host# set chassis fpc 2 pic 0 tunnel-services bandwidth 1g Commit the configuration.
[edit]user@host# commituser@host# exit- Run the show interfaces terse command to verify
that the router has an lt interface.
user@host> show interfaces terse
Interface Admin Link Proto Local Remote ... gr-2/0/10 up up ip-2/0/10 up up lt-2/0/10 up up ...
Configuring the Ingress LSR (Logical System LS1)
Step-by-Step Procedure
To configure Logical System LS1:
From the main router, configure the logical system.
[edit]user@R1# set logical-systems LS1Commit the configuration.
[edit]user@R1# commituser@R1# exit- Set the CLI to view the logical system.
user@R1> set cli logical-system LS1
Logical system: LS1
user@R1:LS1>
Configure the interfaces, interface encapsulation, and protocol families.
[edit]user@R1:LS1# edit interfaces[edit interfaces]user@R1:LS1# set ge-2/0/2 unit 0 description R1-to-CE1user@R1:LS1# set ge-2/0/2 unit 0 family inet address 10.0.244.10/30user@R1:LS1# set lt-2/0/10 unit 1 description LS1-to-LS2user@R1:LS1# set lt-2/0/10 unit 1 encapsulation ethernetuser@R1:LS1# set lt-2/0/10 unit 1 peer-unit 2user@R1:LS1# set lt-2/0/10 unit 1 family inet address 2.2.2.1/24user@R1:LS1# set lt-2/0/10 unit 1 family mplsuser@R1:LS1# set lt-2/0/10 unit 8 description LS1-to-LS6user@R1:LS1# set lt-2/0/10 unit 8 encapsulation ethernetuser@R1:LS1# set lt-2/0/10 unit 8 peer-unit 6user@R1:LS1# set lt-2/0/10 unit 8 family inet address 6.6.6.1/24user@R1:LS1# set lt-2/0/10 unit 8 family mplsuser@R1:LS1# set lt-2/0/10 unit 9 description LS1-to-LS3user@R1:LS1# set lt-2/0/10 unit 9 encapsulation ethernetuser@R1:LS1# set lt-2/0/10 unit 9 peer-unit 3user@R1:LS1# set lt-2/0/10 unit 9 family inet address 3.3.3.1/24user@R1:LS1# set lt-2/0/10 unit 9 family mplsuser@R1:LS1# set lo0 unit 1 family inet address 100.10.10.10/32user@R1:LS1# exitEnable RSVP, MPLS, and OSPF on the interfaces.
[edit]user@R1:LS1# edit protocols[edit protocols]user@R1:LS1# set rsvp interface lt-2/0/10.1user@R1:LS1# set rsvp interface lt-2/0/10.8user@R1:LS1# set rsvp interface lt-2/0/10.9user@R1:LS1# set rsvp interface lo0.1user@R1:LS1# set mpls interface lt-2/0/10.1user@R1:LS1# set mpls interface lt-2/0/10.8user@R1:LS1# set mpls interface lt-2/0/10.9user@R1:LS1# set mpls interface lo0.1user@R1:LS1# set ospf area 0.0.0.0 interface ge-2/0/2.0user@R1:LS1# set ospf area 0.0.0.0 interface lt-2/0/10.1user@R1:LS1# set ospf area 0.0.0.0 interface lt-2/0/10.8user@R1:LS1# set ospf area 0.0.0.0 interface lt-2/0/10.9user@R1:LS1# set ospf area 0.0.0.0 interface lo0.1Configure the MPLS point-to-multipoint LSPs.
[edit protocols]user@R1:LS1# set mpls label-switched-path LS1-LS5 to 100.50.50.50user@R1:LS1# set mpls label-switched-path LS1-LS5 p2mp p2mp1user@R1:LS1# set mpls label-switched-path LS1-LS7 to 100.70.70.70user@R1:LS1# set mpls label-switched-path LS1-LS7 p2mp p2mp1user@R1:LS1# set mpls label-switched-path LS1-LS4 to 100.40.40.40user@R1:LS1# set mpls label-switched-path LS1-LS4 p2mp p2mp1- This causes the ingress routes to be installed in the inet.0 routing table. By default, MPLS performs traffic engineering for BGP only. You need to enable MPLS traffic engineering on the ingress LSR only.
Enable MPLS to perform traffic engineering for OSPF.
- This causes the shortest-path first (SPF) algorithm to take into account the LSPs configured under MPLS.
Enable traffic engineering for OSPF.
Configure the router ID.
[edit]user@R1:LS1# edit routing-options[edit routing-options]user@R1:LS1# set router-id 100.10.10.10Configure static IP unicast routes with the point-to-multipoint LSP name as the next hop for each route.
[edit routing-options]user@R1:LS1# set static route 5.5.5.0/24p2mp-lsp-next-hop p2mp1user@R1:LS1# set static route 7.7.7.0/24 p2mp-lsp-next-hop p2mp1user@R1:LS1# set static route 4.4.4.0/24 p2mp-lsp-next-hop p2mp1user@R1:LS1# exitIf you are done configuring the device, commit the configuration.
[edit]user@R1:LS1# commit
Configuring the Transit and Egress LSRs (Logical Systems LS2, LS3, LS4, LS5, LS6, and LS7)
Step-by-Step Procedure
To configure the transit and egress LSRs:
Configure the interfaces, interface encapsulation, and protocol families.
[edit]user@R1# edit logical-systems[edit logical-systems]user@R1# set LS2 interfaces lt-2/0/10 unit 2 description LS2-to-LS1user@R1# set LS2 interfaces lt-2/0/10 unit 2 encapsulation ethernetuser@R1# set LS2 interfaces lt-2/0/10 unit 2 peer-unit 1user@R1# set LS2 interfaces lt-2/0/10 unit 2 family inet address 2.2.2.2/24user@R1# set LS2 interfaces lt-2/0/10 unit 2 family mplsuser@R1# set LS2 interfaces lt-2/0/10 unit 10 description LS2-to-LS5user@R1# set LS2 interfaces lt-2/0/10 unit 10 encapsulation ethernetuser@R1# set LS2 interfaces lt-2/0/10 unit 10 peer-unit 5user@R1# set LS2 interfaces lt-2/0/10 unit 10 family inet address 5.5.5.1/24user@R1# set LS2 interfaces lt-2/0/10 unit 10 family mplsuser@R1# set LS2 interfaces lo0 unit 2 family inet address 100.20.20.20/32user@R1# set LS3 interfaces lt-2/0/10 unit 3 description LS3-to-LS1user@R1# set LS3 interfaces lt-2/0/10 unit 3 encapsulation ethernetuser@R1# set LS3 interfaces lt-2/0/10 unit 3 peer-unit 9user@R1# set LS3 interfaces lt-2/0/10 unit 3 family inet address 3.3.3.2/24user@R1# set LS3 interfaces lt-2/0/10 unit 3 family mplsuser@R1# set LS3 interfaces lt-2/0/10 unit 12 description LS3-to-LS4user@R1# set LS3 interfaces lt-2/0/10 unit 12 encapsulation ethernetuser@R1# set LS3 interfaces lt-2/0/10 unit 12 peer-unit 4user@R1# set LS3 interfaces lt-2/0/10 unit 12 family inet address 4.4.4.1/24user@R1# set LS3 interfaces lt-2/0/10 unit 12 family mplsuser@R1# set LS3 interfaces lo0 unit 3 family inet address 100.30.30.30/32user@R1# set LS4 interfaces ge-2/0/0 unit 0 description R1-to-CE4user@R1# set LS4 interfaces ge-2/0/0 unit 0 family inet address 10.0.104.9/30user@R1# set LS4 interfaces lt-2/0/10 unit 4 description LS4-to-LS3user@R1# set LS4 interfaces lt-2/0/10 unit 4 encapsulation ethernetuser@R1# set LS4 interfaces lt-2/0/10 unit 4 peer-unit 12user@R1# set LS4 interfaces lt-2/0/10 unit 4 family inet address 4.4.4.2/24user@R1# set LS4 interfaces lt-2/0/10 unit 4 family mplsuser@R1# set LS4 interfaces lo0 unit 4 family inet address 100.40.40.40/32user@R1# set LS5 interfaces ge-2/0/3 unit 0 description LS1-to-CE1user@R1# set LS5 interfaces ge-2/0/3 unit 0 family inet address 10.0.224.10/30user@R1# set LS5 interfaces lt-2/0/10 unit 5 description LS5-to-LS2user@R1# set LS5 interfaces lt-2/0/10 unit 5 encapsulation ethernetuser@R1# set LS5 interfaces lt-2/0/10 unit 5 peer-unit 10user@R1# set LS5 interfaces lt-2/0/10 unit 5 family inet address 5.5.5.2/24user@R1# set LS5 interfaces lt-2/0/10 unit 5 family mplsuser@R1# set LS5 interfaces lo0 unit 5 family inet address 100.50.50.50/32user@R1# set LS6 interfaces lt-2/0/10 unit 6 description LS6-to-LS1user@R1# set LS6 interfaces lt-2/0/10 unit 6 encapsulation ethernetuser@R1# set LS6 interfaces lt-2/0/10 unit 6 peer-unit 8user@R1# set LS6 interfaces lt-2/0/10 unit 6 family inet address 6.6.6.2/24user@R1# set LS6 interfaces lt-2/0/10 unit 6 family mplsuser@R1# set LS6 interfaces lt-2/0/10 unit 11 description LS6-to-LS7user@R1# set LS6 interfaces lt-2/0/10 unit 11 encapsulation ethernetuser@R1# set LS6 interfaces lt-2/0/10 unit 11 peer-unit 7user@R1# set LS6 interfaces lt-2/0/10 unit 11 family inet address 7.7.7.1/24user@R1# set LS6 interfaces lt-2/0/10 unit 11 family mplsuser@R1# set LS6 interfaces lo0 unit 6 family inet address 100.60.60.60/32user@R1# set LS7 interfaces ge-2/0/1 unit 0 description R1-to-CE3user@R1# set LS7 interfaces ge-2/0/1 unit 0 family inet address 10.0.134.10/30user@R1# set LS7 interfaces lt-2/0/10 unit 7 description LS7-to-LS6user@R1# set LS7 interfaces lt-2/0/10 unit 7 encapsulation ethernetuser@R1# set LS7 interfaces lt-2/0/10 unit 7 peer-unit 11user@R1# set LS7 interfaces lt-2/0/10 unit 7 family inet address 7.7.7.2/24user@R1# set LS7 interfaces lt-2/0/10 unit 7 family mplsuser@R1# set LS7 interfaces lo0 unit 7 family inet address 100.70.70.70/32Enable RSVP, MPLS, and OSPF on the interfaces.
[edit]user@R1# edit logical-systems[edit logical-systems]user@R1# set LS2 protocols rsvp interface lt-2/0/10.2user@R1# set LS2 protocols rsvp interface lt-2/0/10.10user@R1# set LS2 protocols rsvp interface lo0.2user@R1# set LS2 protocols mpls interface lt-2/0/10.2user@R1# set LS2 protocols mpls interface lt-2/0/10.10user@R1# set LS2 protocols mpls interface lo0.2user@R1# set LS2 protocols ospf area 0.0.0.0 interface lt-2/0/10.2user@R1# set LS2 protocols ospf area 0.0.0.0 interface lt-2/0/10.10user@R1# set LS2 protocols ospf area 0.0.0.0 interface lo0.2user@R1# set LS3 protocols rsvp interface lt-2/0/10.3user@R1# set LS3 protocols rsvp interface lt-2/0/10.12user@R1# set LS3 protocols rsvp interface lo0.3user@R1# set LS3 protocols mpls interface lt-2/0/10.3user@R1# set LS3 protocols mpls interface lt-2/0/10.12user@R1# set LS3 protocols mpls interface lo0.3user@R1# set LS3 protocols ospf area 0.0.0.0 interface lt-2/0/10.3user@R1# set LS3 protocols ospf area 0.0.0.0 interface lt-2/0/10.12user@R1# set LS3 protocols ospf area 0.0.0.0 interface lo0.3user@R1# set LS4 protocols rsvp interface lt-2/0/10.4user@R1# set LS4 protocols rsvp interface lo0.4user@R1# set LS4 protocols mpls interface lt-2/0/10.4user@R1# set LS4 protocols mpls interface lo0.4user@R1# set LS4 protocols ospf area 0.0.0.0 interface ge-2/0/0.0user@R1# set LS4 protocols ospf area 0.0.0.0 interface lt-2/0/10.4user@R1# set LS4 protocols ospf area 0.0.0.0 interface lo0.4user@R1# set LS5 protocols rsvp interface lt-2/0/10.5user@R1# set LS5 protocols rsvp interface lo0.5user@R1# set LS5 protocols mpls interface lt-2/0/10.5user@R1# set LS5 protocols mpls interface lo0.5user@R1# set LS5 protocols ospf area 0.0.0.0 interface ge-2/0/3.0user@R1# set LS5 protocols ospf area 0.0.0.0 interface lt-2/0/10.5user@R1# set LS5 protocols ospf area 0.0.0.0 interface lo0.5user@R1# set LS6 protocols rsvp interface lt-2/0/10.6user@R1# set LS6 protocols rsvp interface lt-2/0/10.11user@R1# set LS6 protocols rsvp interface lo0.6user@R1# set LS6 protocols mpls interface lt-2/0/10.6user@R1# set LS6 protocols mpls interface lt-2/0/10.11user@R1# set LS6 protocols mpls interface lo0.6user@R1# set LS6 protocols ospf area 0.0.0.0 interface lt-2/0/10.6user@R1# set LS6 protocols ospf area 0.0.0.0 interface lt-2/0/10.11user@R1# set LS6 protocols ospf area 0.0.0.0 interface lo0.6user@R1# set LS7 protocols rsvp interface lt-2/0/10.7user@R1# set LS7 protocols rsvp interface lo0.7user@R1# set LS7 protocols mpls interface lt-2/0/10.7user@R1# set LS7 protocols mpls interface lo0.7user@R1# set LS7 protocols ospf area 0.0.0.0 interface ge-2/0/1.0user@R1# set LS7 protocols ospf area 0.0.0.0 interface lt-2/0/10.7user@R1# set LS7 protocols ospf area 0.0.0.0 interface lo0.7- This causes the SPF algorithm to take into account the LSPs configured under MPLS.
Enable traffic engineering for OSPF.
[edit logical-systems]user@R1# set LS2 protocols ospf traffic-engineeringuser@R1# set LS3 protocols ospf traffic-engineeringuser@R1# set LS4 protocols ospf traffic-engineeringuser@R1# set LS5 protocols ospf traffic-engineeringuser@R1# set LS6 protocols ospf traffic-engineeringuser@R1# set LS7 protocols ospf traffic-engineering Configure the router IDs.
[edit logical-systems]user@R1# set LS2 routing-options router-id 100.20.20.20user@R1# set LS3 routing-options router-id 100.30.30.30user@R1# set LS4 routing-options router-id 100.40.40.40user@R1# set LS5 routing-options router-id 100.50.50.50user@R1# set LS6 routing-options router-id 100.60.60.60user@R1# set LS7 routing-options router-id 100.70.70.70If you are done configuring the device, commit the configuration.
[edit logical-systems]user@R1# commit
Results
From configuration mode, confirm your configuration by entering the show logical-systems command. If the output does not display the intended configuration, repeat the instructions in this example to correct the configuration.
Configuring Device CE1
Step-by-Step Procedure
To configure Device CE1:
Configure an interface to Logical System LS1.
[edit]user@CE1# edit interfaces[edit interfaces]user@CE1# set ge-1/3/2 unit 0 family inet address 10.0.244.9/30user@CE1# set ge-1/3/2 unit 0 description CE1-to-LS1user@CE1# exitConfigure static routes from Device CE1 to the three other customer networks, with Logical System LS1 as the next hop.
[edit]user@CE1# edit routing-options[edit routing-options]set static route 10.0.104.8/30 next-hop 10.0.244.10set static route 10.0.134.8/30 next-hop 10.0.244.10set static route 10.0.224.8/30 next-hop 10.0.244.10user@CE1# exitIf you are done configuring the device, commit the configuration.
[edit]user@CE1# commit
Results
From configuration mode, confirm your configuration by entering the show interfaces and show routing-options commands. If the output does not display the intended configuration, repeat the instructions in this example to correct the configuration.
Configuring Device CE2
Step-by-Step Procedure
To configure Device CE2:
Configure an interface to Logical System LS5.
[edit]user@CE2# edit interfaces[edit interfaces]user@CE2# set ge-1/3/3 unit 0 family inet address 10.0.224.9/30 user@CE2# set ge-1/3/3 unit 0 description CE2-to-LS5user@CE2# exitConfigure a static route from Device CE2 to CE1, with Logical System LS5 as the next hop.
[edit]user@CE2# edit routing-options[edit routing-options]user@CE2# set static route 10.0.244.8/30 next-hop 10.0.224.10user@CE2# exitIf you are done configuring the device, commit the configuration.
[edit]user@CE2# commit
Results
From configuration mode, confirm your configuration by entering the show interfaces and show routing-options commands. If the output does not display the intended configuration, repeat the instructions in this example to correct the configuration.
Configuring Device CE3
Step-by-Step Procedure
To configure Device CE3:
Configure an interface to Logical System LS7.
[edit]user@CE3# edit interfaces[edit interfaces]user@CE3# set ge-2/0/1 unit 0 family inet address 10.0.134.9/30 user@CE3# set ge-2/0/1 unit 0 description CE3-to-LS7user@CE3# exitConfigure a static route from Device CE3 to CE1, with Logical System LS7 as the next hop.
[edit]user@CE3# edit routing-options[edit routing-options]user@CE3# set static route 10.0.244.8/30 next-hop 10.0.134.10user@CE3# exitIf you are done configuring the device, commit the configuration.
[edit]user@CE3# commit
Results
From configuration mode, confirm your configuration by entering the show interfaces and show routing-options commands. If the output does not display the intended configuration, repeat the instructions in this example to correct the configuration.
Configuring Device CE4
Step-by-Step Procedure
To configure Device CE4:
Configure an interface to Logical System LS4.
[edit]user@CE4# edit interfaces[edit interfaces]user@CE4# set ge-3/1/3 unit 0 family inet address 10.0.104.10/30 user@CE4# set ge-3/1/3 unit 0 description CE4-to-LS4Configure a static route from Device CE4 to CE1, with Logical System LS4 as the next hop.
[edit]user@CE4# edit routing-options[edit routing-options]user@CE4# set static route 10.0.244.8/30 next-hop 10.0.104.9user@CE4# exitIf you are done configuring the device, commit the configuration.
[edit]user@CE4# commit
Results
From configuration mode, confirm your configuration by entering the show interfaces and show routing-options commands. If the output does not display the intended configuration, repeat the instructions in this example to correct the configuration.
Verification
Confirm that the configuration is working properly.
- Verifying Connectivity
- Verifying the State of the Point-to-Multipoint LSP
- Checking the Forwarding Table
Verifying Connectivity
Purpose
Make sure that the devices can ping each other.
Action
Run the ping command from CE1 to the interface on CE2 connecting to LS5.
user@CE1> ping 10.0.224.9
PING 10.0.224.9 (10.0.224.9): 56 data bytes 64 bytes from 10.0.224.9: icmp_seq=0 ttl=61 time=1.387 ms 64 bytes from 10.0.224.9: icmp_seq=1 ttl=61 time=1.394 ms 64 bytes from 10.0.224.9: icmp_seq=2 ttl=61 time=1.506 ms ^C --- 10.0.224.9 ping statistics --- 3 packets transmitted, 3 packets received, 0% packet loss round-trip min/avg/max/stddev = 1.387/1.429/1.506/0.055 ms
Run the ping command from CE1 to the interface on CE3 connecting to LS7.
user@CE1> ping 10.0.134.9
PING 10.0.134.9 (10.0.134.9): 56 data bytes 64 bytes from 10.0.134.9: icmp_seq=0 ttl=61 time=1.068 ms 64 bytes from 10.0.134.9: icmp_seq=1 ttl=61 time=1.062 ms 64 bytes from 10.0.134.9: icmp_seq=2 ttl=61 time=1.053 ms ^C --- 10.0.134.9 ping statistics --- 3 packets transmitted, 3 packets received, 0% packet loss round-trip min/avg/max/stddev = 1.053/1.061/1.068/0.006 ms
Run the ping command from CE1 to the interface on CE4 connecting to LS4.
user@CE1> ping 10.0.104.10
PING 10.0.104.10 (10.0.104.10): 56 data bytes 64 bytes from 10.0.104.10: icmp_seq=0 ttl=61 time=1.079 ms 64 bytes from 10.0.104.10: icmp_seq=1 ttl=61 time=1.048 ms 64 bytes from 10.0.104.10: icmp_seq=2 ttl=61 time=1.070 ms ^C --- 10.0.104.10 ping statistics --- 3 packets transmitted, 3 packets received, 0% packet loss round-trip min/avg/max/stddev = 1.048/1.066/1.079/0.013 ms
Verifying the State of the Point-to-Multipoint LSP
Purpose
Make sure that the ingress, transit, and egress LSRs are in the Up state.
![]() | Note: For this example, the show rsvp session command displays the same output as the show mpls lsp p2mp command. |
Action
Run the show mpls lsp p2mp command on all of the LSRs. Only the ingress LSR is shown here.
user@R1> set cli logical-system LS1
Logical system: LS1
user@R1:LS1> show mpls lsp p2mp
Ingress LSP: 1 sessions P2MP name: p2mp1, P2MP branch count: 3 To From State Rt P ActivePath LSPname 100.40.40.40 100.10.10.10 Up 0 * LS1-LS4 100.70.70.70 100.10.10.10 Up 0 * LS1-LS7 100.50.50.50 100.10.10.10 Up 0 * LS1-LS5 Total 3 displayed, Up 3, Down 0 ...
Checking the Forwarding Table
Purpose
Make sure that the routes are set up as expected by running the show route forwarding-table command. Only the routes to the remote customer networks are shown here.
Action
user@R1:LS1> show route forwarding-table
Routing table: default.inet Internet: Destination Type RtRef Next hop Type Index NhRef Netif ... 10.0.104.8/30 user 0 3.3.3.2 ucst 1006 6 lt-2/0/10.9 10.0.134.8/30 user 0 6.6.6.2 ucst 1010 6 lt-2/0/10.8 10.0.224.8/30 user 0 2.2.2.2 ucst 1008 6 lt-2/0/10.1 ...
Related Documentation
- M, MX, PTX, T Series
- Point-to-Multipoint LSPs Overview in the Junos OS MPLS Applications Configuration Guide
Published: 2012-11-15
Related Documentation
- M, MX, PTX, T Series
- Point-to-Multipoint LSPs Overview in the Junos OS MPLS Applications Configuration Guide