Next-Hop-Based Dynamic Tunnels

Step-by-Step Procedure

The following example requires that you 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.

To configure Device PE1:

1. Configure the device interfaces including the loopback interface of the device.

   content_copy zoom_out_map

   [edit interfaces]
   user@PE1# set ge-0/0/0 unit 0 family inet address 10.0.0.2/8
   user@PE1# set ge-0/0/1 unit 0 family inet address 192.0.2.1/24
   user@PE1# set ge-0/0/1 unit 0 family mpls
   user@PE1# set lo0 unit 0 family inet address 10.127.0.2/8
   

2. Configure a static route for routes from Device PE1 with Device P1 as the next-hop destination.

   content_copy zoom_out_map

   [edit routing-options]
   user@PE1# set static route 10.33.0.0/16 next-hop 192.0.2.2
   

3. Configure the router-ID and autonomous system number for Device PE1.

   content_copy zoom_out_map

   [edit routing-options]
   user@PE1# set router-id 10.127.0.2
   user@PE1# set autonomous-system 65100
   

4. (PTX Series only) Configure policy control to resolve the MPLS-over-UDP dynamic tunnel route over select prefixes.

   content_copy zoom_out_map

   [edit routing-options dynamic-tunnels]
   user@PTX-PE1# set forwarding-rib inet.0 inet-import dynamic-tunnel-fwd-route-import
   

5. (PTX Series only) Configure the inet-import policy for resolving dynamic tunnel destination routes over .

   content_copy zoom_out_map

   [edit policy-options]
   user@PTX-PE1# set policy-statement dynamic-tunnel-fwd-route-import term 1 from route-filter 10.127.0.4/32 exact
   user@PTX-PE1# set policy-statement dynamic-tunnel-fwd-route-import term 1 then accept
   user@PTX-PE1# set policy-options policy-statement dynamic-tunnel-fwd-route-import then reject
   

6. Configure IBGP peering between the PE devices.

   content_copy zoom_out_map

   [edit protocols]
   user@PE1# set bgp group IBGP type internal
   user@PE1# set bgp group IBGP local-address 10.127.0.2
   user@PE1# set bgp group IBGP family inet-vpn unicast
   user@PE1# set bgp group IBGP neighbor 10.127.0.4
   

7. Configure OSPF on all the interfaces of Device PE1, excluding the management interface.

   content_copy zoom_out_map

   [edit protocols]
   user@PE1# set ospf area 0.0.0.0 interface ge-0/0/1.0
   user@PE1# set ospf area 0.0.0.0 interface lo0.0 passive
   

8. Enable next-hop-based dynamic GRE tunnel configuration on Device PE1.

   Note:

   This step is required only for illustrating the implementation difference between next-hop-based dynamic GRE tunnels and MPLS-over-UDP tunnels.

   content_copy zoom_out_map

   [edit routing-options]
   user@PE1# set dynamic-tunnels gre next-hop-based-tunnel
   

9. Configure the MPLS-over-UDP tunnel parameters from Device PE1 to Device PE2.

   content_copy zoom_out_map

   [edit routing-options]
   user@PE1# set dynamic-tunnels udp-dyn-tunnel-to-pe2 source-address 10.127.0.2
   user@PE1# set dynamic-tunnels udp-dyn-tunnel-to-pe2 udp
   user@PE1# set dynamic-tunnels udp-dyn-tunnel-to-pe2 destination-networks 10.127.0.0/24
   

10. Configure a VRF routing instance on Device PE1 and other routing instance parameters.

    content_copy zoom_out_map

    [edit routing-instances]
    user@PE1# set MPLS-over-UDP-PE1 instance-type vrf
    user@PE1# set MPLS-over-UDP-PE1 interface ge-0/0/0.0
    user@PE1# set MPLS-over-UDP-PE1 route-distinguisher 10.127.0.2:1
    user@PE1# set MPLS-over-UDP-PE1 vrf-target target:600:1
    

11. Enable BGP in the routing instance configuration for peering with Device CE1.

    content_copy zoom_out_map

    [edit routing-instances]
    user@PE1# set MPLS-over-UDP-PE1 protocols bgp group pe1-ce1 peer-as 65200
    user@PE1# set MPLS-over-UDP-PE1 protocols bgp group pe1-ce1 neighbor 10.0.0.1 as-override
    

Purpose

Verify the BGP peering status between Device PE1 and Device PE2, and the BGP routes received from Device PE2.

Action

From operational mode, run the show bgp summary and show route receive-protocol bgp ip-address table bgp.l3vpn.0 commands.

user@PE1> show bgp summary
Groups: 2 Peers: 2 Down peers: 0
Table          Tot Paths  Act Paths Suppressed    History Damp State    Pending
bgp.l3vpn.0
                       2          2          0          0          0          0
Peer                     AS      InPkt     OutPkt    OutQ   Flaps Last Up/Dwn State|#Active/Received/Accepted/Damped...
10.127.0.4             65100        139        136       0       0       58:23 Establ
  bgp.l3vpn.0: 2/2/2/0
  MPLS-over-UDP-PE1.inet.0: 2/2/2/0
10.10.0.1               65200        135        136       0       0       58:53 Establ
  MPLS-over-UDP-PE1.inet.0: 1/1/1/0

user@PE1> show route receive-protocol bgp 10.127.0.4 table bgp.l3vpn.0
bgp.l3vpn.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)
  Prefix                  Nexthop              MED     Lclpref    AS path
  10.127.0.4:1:127.0.0.5/8
*                         10.127.0.4                  65100        65200 I

Meaning

• In the first output, the BGP session state is Establ, which means that the session is up and the PE devices are peered.

• In the second output, Device PE1 has learned a BGP route from Device PE2.

Purpose

Verify the routes in the inet.3 routing table and the dynamic tunnel database information on Device PE1.

Action

From operational mode, run the show route table inet.3, show dynamic-tunnels database terse, show dynamic-tunnels database, and show dynamic-tunnels database summary commands.

user@PE1> show route table inet.3
inet.3: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
10.127.0.0/24     *[Tunnel/300] 00:21:18
                      Tunnel
127.0.0.4/8     *[Tunnel/300] 00:21:18
                      Tunnel Composite

user@PE1> show dynamic-tunnels database terse
Table: inet.3

Destination-network: 10.127.0.0/24
Destination         Source          Next-hop                  Type        Status
10.127.0.4/8      10.127.0.2     0xb395b10 nhid 613        udp         Up

user@PE1> show dynamic-tunnels database
Table: inet.3
. . .
Tunnel to: 10.127.0.4/32
  Reference count: 2
  Next-hop type: UDP
    Source address: 10.127.0.2 Tunnel Id: 2
    Next hop: tunnel-composite, 0xb395b10, nhid 613
      VPN Label: Push 299776 Reference count: 3
      Traffic Statistics: Packets 0, Bytes 0
      State: Up

user@PE1> show dynamic-tunnels database summary
Dynamic Tunnels,  Total 1 displayed
GRE Tunnel: 
Active Tunnel Mode, Next Hop Base
  IFL Based,  Total 0 displayed, Up 0, Down 0
  Nexthop Based,  Total 0 displayed, Up 0, Down 0
RSVP Tunnel: 
  Total 0 displayed
UDP Tunnel: 
  Total 1 displayed, Up 1, Down 0

Meaning

• In the first output, because Device PE1 is configured with the MPLS-over-UDP tunnel, a tunnel composite route is created for the inet.3 routing table route entry.

• In the remaining outputs, the MPLS-over-UDP tunnel is displayed with the tunnel encapsulation type, tunnel next hop parameters, and tunnel status.

Purpose

Verify the routes in the inet.3 routing table and the dynamic tunnel database information on Device PE2.

Action

From operational mode, run the show route table inet.3, and the show dynamic-tunnels database terse commands.

user@PE2> show route table inet.3
inet.3: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

10.127.0.0/24      *[Tunnel/300] 00:39:31
                      Tunnel
10.127.0.2/32     *[Tunnel/300] 00:24:53
                      Tunnel Composite

user@PE1> show dynamic-tunnels database terse
Table: inet.3

Destination-network: 127.0.0.0/8
Destination         Source          Next-hop                  Type        Status
10.127.0.2/32      10.127.0.4     0xb395450 nhid 615        udp         Up  

Meaning

The outputs show the MPLS-over-UDP tunnel creation and the next-hop ID assigned as the next-hop interface, similar to Device PE1.

Purpose

Verify that Device PE1 and Device PE2 are configured to maintain the indirect next hop to forwarding next-hop binding on the Packet Forwarding Engine forwarding table.

Action

From operational mode, run the show krt indirect-next-hop command on Device PE1 and Device PE2.

user@PE1> show krt indirect-next-hop
Indirect Nexthop:
Index: 1048574 Protocol next-hop address: 10.127.0.4
  RIB Table: bgp.l3vpn.0                
  Label: Push 299776           
  Policy Version: 1                     References: 1
  Locks: 3                              0xb2ab630
  Flags: 0x0                              
  INH Session ID: 0x0
  INH Version ID: 0
  Ref RIB Table: unknown
        Tunnel type: UDP, Reference count: 3, nhid: 613
        Destination address: 10.127.0.4, Source address: 10.127.0.2
        Tunnel id: 2, VPN Label: Push 299776, TTL action: prop-ttl
      IGP FRR Interesting proto count : 1
      Chain IGP FRR Node Num          : 1
         IGP Resolver node(hex)       : 0xb3c70dc   
         IGP Route handle(hex)        : 0xb1ae688      IGP rt_entry protocol        : Tunnel
         IGP Actual Route handle(hex) : 0x0            IGP Actual rt_entry protocol : Any

user@PE2> show krt indirect-next-hop
Indirect Nexthop:
Index: 1048575 Protocol next-hop address: 10.127.0.2
  RIB Table: bgp.l3vpn.0                
  Label: Push 299776           
  Policy Version: 1                     References: 2
  Locks: 3                              0xb2ab740
  Flags: 0x0                              
  INH Session ID: 0x0
  INH Version ID: 0
  Ref RIB Table: unknown
        Tunnel type: UDP, Reference count: 3, nhid: 615
        Destination address: 10.127.0.2, Source address: 10.127.0.4
        Tunnel id: 1, VPN Label: Push 299776, TTL action: prop-ttl
      IGP FRR Interesting proto count : 2
      Chain IGP FRR Node Num          : 1
         IGP Resolver node(hex)       : 0xb3d3a28   
         IGP Route handle(hex)        : 0xb1ae634      IGP rt_entry protocol        : Tunnel
         IGP Actual Route handle(hex) : 0x0            IGP Actual rt_entry protocol : Any

Meaning

The outputs show that a next-hop-based dynamic MPLS-over-UDP tunnel is created between the PE devices.

Problem

The next-hop-based dynamic MPLS-over-UDP tunnel configuration is not taking effect.

Solution

To troubleshoot the next-hop-based MPLS-over-UDP tunnel configuration, use the following traceroute commands at the [edit routing-options dynamic-tunnels] statement hierarchy:

• traceoptions file file-name

• traceoptions file size file-size

• traceoptions flag all

For example:

[edit routing-options dynamic-tunnels]
traceoptions {
    file udp_dyn_pe1.wri size 4294967295;
    flag all;
}

Step-by-Step Procedure

The following example requires that you 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.

To configure Router R0:

1. Configure Router R0’s interfaces, including the loopback interface.

   content_copy zoom_out_map

   [edit interfaces]
   user@R0# set ge-0/0/0 unit 0 family inet address 192.0.2.1/24
   user@R0# set ge-0/0/1 unit 0 family inet address 198.51.100.1/24
   user@R0# set ge-0/0/2 vlan-tagging
   user@R0# set ge-0/0/2 unit 0 vlan-id 1
   user@R0# set ge-0/0/2 unit 0 family inet address 172.16.0.1/16
   user@R0# set lo0 unit 0 family inet address 10.1.1.1/32
   

2. Assign the router ID and autonomous system number for Router R0.

   content_copy zoom_out_map

   [edit routing-options]
   user@R0# set router-id 10.1.1.1
   user@R0# set autonomous-system 100
   

3. Configure IBGP peering between the routers.

   content_copy zoom_out_map

   [edit protocols]
   user@R0# set bgp group IBGP type internal
   user@R0# set bgp group IBGP local-address 10.1.1.1
   user@R0# set bgp group IBGP family inet-vpn unicast
   user@R0# set bgp group IBGP neighbor 20.1.1.1
   user@R0# set bgp group IBGP neighbor 30.1.1.1
   

4. Configure OSPF on all the interfaces of Router R0, excluding the management interface.

   content_copy zoom_out_map

   [edit protocols]
   user@R0# set ospf traffic-engineering
   user@R0# set ospf area 0.0.0.0 interface lo0.0 passive
   user@R0# set ospf area 0.0.0.0 interface all
   

5. Configure RSVP on all the interfaces of Router R0, excluding the management interface.

   content_copy zoom_out_map

   [edit protocols]
   user@R0# set rsvp interface all
   user@R0# set rsvp interface fxp0.0 disable
   

6. Enable next-hop-based dynamic GRE tunnel configuration on Router R0.

   content_copy zoom_out_map

   [edit routing-options]
   user@R0# set dynamic-tunnels gre next-hop-based-tunnel
   

7. Configure the dynamic GRE tunnel parameters from Router R0 to Router R1.

   content_copy zoom_out_map

   [edit routing-options]
   user@R0# set dynamic-tunnels T1 source-address 192.0.2.1
   user@R0# set dynamic-tunnels T1 gre
   user@R0# set dynamic-tunnels T1 destination-networks 192.0.2.0/24
   

8. Configure the dynamic GRE tunnel parameters from Router R0 to Router R2.

   content_copy zoom_out_map

   [edit routing-options]
   user@R0# set dynamic-tunnels T2 source-address 198.51.100.1
   user@R0# set dynamic-tunnels T2 gre
   user@R0# set dynamic-tunnels T2 destination-networks 198.51.100.0/24
   

9. Configure a virtual routing and forwarding (VRF) routing instance on Router R0, and assign the interface connecting to Host 1 to the VRF instance.

   content_copy zoom_out_map

   [edit routing-instances]
   user@R0# set VPN1 instance-type vrf
   user@R0# set VPN1 route-distinguisher 100:100
   user@R0# set VPN1 vrf-target target:100:1
   user@R0# set VPN1 vrf-table-label
   user@R0# set VPN1 interface ge-0/0/2.0
   

10. Configure an external BGP session with Host 1 for the VRF routing instance.

    content_copy zoom_out_map

    [edit routing-instances]
    user@R0# set VPN1 protocols bgp group External type external
    user@R0# set VPN1 protocols bgp group External family inet unicast
    user@R0# set VPN1 protocols bgp group External peer-as 200
    user@R0# set VPN1 protocols bgp group External neighbor 172.16.0.1
    

11. Configure anti-spoofing protection for the VRF routing instance on Router R0. This enables reverse path forwarding check for the next-hop-based dynamic tunnels, T1 and T2, on Router 0.

    content_copy zoom_out_map

    [edit routing-instances]
    user@R0# set VPN1 routing-options forwarding-table ip-tunnel-rpf-check mode strict
    

Purpose

Verify the OSPF and BGP peering status between the Router R0 and Routers R1 and R2.

Action

From operational mode, run the show ospf neighbor and show bgp summarycommands.

user@R0> show ospf neighbor
Address          Interface              State     ID               Pri  Dead
192.0.2.2        ge-0/0/0.0             Full      20.1.1.1         128    32
198.51.100.2     ge-0/0/1.0             Full      30.1.1.1         128    32

user@R0> show bgp summary
Groups: 2 Peers: 3 Down peers: 1
Table          Tot Paths  Act Paths Suppressed    History Damp State    Pending
bgp.l3vpn.0          
                       0          0          0          0          0          0
Peer                     AS      InPkt     OutPkt    OutQ   Flaps Last Up/Dwn State|#Active/Received/Accepted/Damped...
20.1.1.1                100        182        178       0       0     1:20:27 Establ
  bgp.l3vpn.0: 0/0/0/0
30.1.1.1                100        230        225       0       0     1:41:51 Establ
  bgp.l3vpn.0: 0/0/0/0
172.16.0.1              200          0          0       0       0     1:42:08 Establ

Meaning

The OSPF and BGP sessions are up and running between the Routers R0, R1, and R2.

Purpose

Verify the status of the next-hop-based dynamic GRE tunnels between the Router R0 and Routers R1 and R2.

Action

From operational mode, run the show route table inet.3, and the show dynamic-tunnels database terse commands.

user@R0> show route table inet.3

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

192.0.2.0/24       *[Tunnel/300] 01:47:57
                      Tunnel
192.0.2.2/24       *[Tunnel/300] 01:47:57
                      Tunnel Composite

198.51.100.0/24    *[Tunnel/300] 01:47:57
                      Tunnel
198.51.100.2/24    *[Tunnel/300] 01:47:57
                      Tunnel Composite

user@R0> show dynamic-tunnels database terse
Table: inet.3

Destination-network: 192.0.2.0/24
Destination 			Source 			Next-hop 					Type 		Status
192.0.2.2/24 	 192.0.2.1 	0xb395e70 nhid 612 		gre 	  Up

Destination-network: 198.51.100.0/24
Destination 			Source 					Next-hop 					Type 		Status
198.51.100.2 	 198.51.100.1 	0xb395e70 nhid 612 		gre 	  Up

Meaning

The two next-hop-based dynamic GRE tunnels, Tunnel 1 and Tunnel 2, are up.

Purpose

Verify that the reverse path forwarding check has been enabled on the VRF routing instance on Router R0.

Action

From the operational mode, run the show krt table VPN1.inet.0 detail.

user@R0> show krt table VPN1.inet.0 detail
KRT tables:
VPN1.inet.0                   : GF: 1 krt-index: 8     ID: 0 kernel-id: 8
        flags: (null)
        tunnel rpf config data : enable, strict, filter [0], 0x2
        tunnel rpf tlv data : enable, strict, filter [0], 0x4
        unicast reverse path: disabled
        fast-reroute-priority: 0
        Permanent NextHops
          Multicast        : 0 Broadcast : 0
          Receive          : 0   Discard   : 0
          Multicast Discard: 0   Reject    : 0
          Local            : 0   Deny      : 0
          Table            : 0

Meaning

The configured reverse path forwarding check is enabled on the VRF routing instance in the strict mode.

Step-by-Step Procedure for R1

R1 and R5 have a similar configuration so we will only show the step-by-step procedure for R1.

1. Enter configuration mode on R1.

2. Configure the interface connected to R2 and interface lo0. Make sure to configure both family inet and iso. Family iso is needed for protocol IS-IS.

   content_copy zoom_out_map

   [edit]
   user@R1# set interfaces xe-0/2/0 unit 0 description R1-to-R2
   user@R1# set interfaces xe-0/2/0 unit 0 family inet address 192.168.12.1/30
   user@R1# set interfaces xe-0/2/0 unit 0 family iso
   user@R1# set interfaces lo0 unit 0 family inet address 192.168.255.1/32
   user@R1# set interfaces lo0 unit 0 family iso address 49.0001.1920.1682.5501.00
   

3. Configure the Router ID.

   content_copy zoom_out_map

   [edit]
   user@R1# set routing-options router-id 192.168.255.1
   

4. Configure protocols IS-IS. Routes are advertised between R1 and R2 using the IS-IS protocol.

   content_copy zoom_out_map

   [edit]
   user@R1# set protocols isis interface xe-0/2/0.0
   user@R1# set protocols isis interface lo0.0
   user@R1# set protocols isis level 1 disable
   

5. Enter commit on R1 from the configuration mode.

Step-by-Step Procedure for R2

R2 and R4 have a similar configuration so we will only show the step-by-step procedure for R2.

1. Enter configuration mode on R2.

2. Configure the interfaces connected to R1 and R3 and interface lo0. Ensure to configure both familyinet and iso on the interface connected to R1 and lo0.

   content_copy zoom_out_map

   [edit]
   user@R2# set interfaces xe-0/2/0 description R2-to-R1
   user@R2# set interfaces xe-0/2/0 unit 0 family inet address 192.168.12.2/30
   user@R2# set interfaces xe-0/2/0 unit 0 family iso
   user@R2# set interfaces xe-0/2/1 description R2-to-R3
   user@R2# set interfaces xe-0/2/1 unit 0 family inet address 10.1.23.1/30
   user@R2# set interfaces lo0 unit 0 family inet address 10.1.255.2/32
   user@R2# set interfaces lo0 unit 0 family iso address 49.0001.0010.1255.0002.00
   

3. Configure protocols IS-IS for the interface connected to R1. The export policy to advertise BGP routes into IS-IS is shown in the policy configuration step.

   content_copy zoom_out_map

   [edit]
   user@R2# set protocols isis interface xe-0/2/0.0 
   user@R2# set protocols isis interface lo0.0
   user@R2# set protocols isis level 1 disable
   user@R2# set protocols isis export export-bgp
   

4. Configure the OSPF protocol for the interface connected to R3 for lo0 reachability.

   content_copy zoom_out_map

   [edit]
   user@R2# set protocols ospf area 0.0.0.0 interface xe-0/2/1.0
   user@R2# set protocols ospf area 0.0.0.0 interface lo0.0
   

5. Configure the router-id and autonomous-system, and IBGP between R2 and R4. The export policy to advertise IS-IS routes into BGP is shown in the policy configuration step.

   content_copy zoom_out_map

   [edit]
   user@R2# set routing-options router-id 10.1.255.2
   user@R2# set routing-options autonomous-system 65000
   user@R2# set protocols bgp group iBGP type internal
   user@R2# set protocols bgp group iBGP local-address 10.1.255.2
   user@R2# set protocols bgp group iBGP family inet unicast
   user@R2# set protocols bgp group iBGP export export-isis
   user@R2# set protocols bgp group iBGP neighbor 10.1.255.4
   

6. Configure the BGP and IS-IS export policies that were applied during the previous steps. The export-bgp policy is applied to protocols IS-IS as an export to advertise BGP routes into IS-IS and the export-isis policy is applied to BGP as an export to advertise IS-IS routes into BGP. The next-hop self option allows R2 to advertise the IS-IS routes into BGP with R2 as the next-hop instead of the interface next-hop of R1.

   content_copy zoom_out_map

   [edit]
   user@R2# set policy-options policy-statement export-bgp term t1 from protocol bgp
   user@R2# set policy-options policy-statement export-bgp term t1 then accept
   user@R2# set policy-options policy-statement export-isis term t1 from protocol isis
   user@R2# set policy-options policy-statement export-isis term t1 then next-hop self
   user@R2# set policy-options policy-statement export-isis term t1 then accept
   

7. Configure the IP-IP dynamic tunnel Tunnel-01 from R2 to R4. The configuration option resolution-ribs inet.3 allows for route resolution to take place in inet.3 and is needed to establish the tunnel.

   content_copy zoom_out_map

   [edit]
   user@R2# set routing-options resolution rib inet.0 resolution-ribs inet.3
   user@R2# set routing-options dynamic-tunnels Tunnel-01 source-address 10.1.255.2
   user@R2# set routing-options dynamic-tunnels Tunnel-01 ipip
   user@R2# set routing-options dynamic-tunnels Tunnel-01 destination-networks 10.1.255.0/24
   

8. (Optional) - Alternative configuration for the IP-IP dynamic tunnel Tunnel-01 from R2 to R4. Instead of configuring the resolution-ribs inet.3 you can configure the tunnel preference lower than the protocol next-hop preference for the route to the tunnel endpoint. The route for R4 is learned using OSPF and has a preference of 10 and the default preference of the tunnel is 305. Configure the tunnel preference lower than the OSPF preference allows the tunnel to be preferred and to establish.

   content_copy zoom_out_map

   [edit]
   user@R2# set routing-options dynamic-tunnels Tunnel-01 source-address 10.1.255.2
   user@R2# set routing-options dynamic-tunnels Tunnel-01 ipip
   user@R2# set routing-options dynamic-tunnels Tunnel-01 destination-networks 10.1.255.0/24 preference 9
   

9. Enter commit from the configuration mode on R2.

Step-by-Step Procedure for R3

1. Enter configuration mode on R3.

2. Configure the interfaces connected to R2 and R4 and interface lo0.

   content_copy zoom_out_map

   [edit]
   user@R3# set interfaces xe-0/2/0 unit 0 description R3-to-R2
   user@R3# set interfaces xe-0/2/0 unit 0 family inet address 10.1.23.2/30
   user@R3# set interfaces xe-0/2/1 unit 0 description R3-to-R4
   user@R3# set interfaces xe-0/2/1 unit 0 family inet address 10.1.34.1/30
   user@R3# set interfaces lo0 unit 0 family inet address 10.1.255.3/32
   

3. Configure the Router ID.

   content_copy zoom_out_map

   [edit]
   user@R3# set routing-options router-id 10.1.255.3
   

4. Configure the OSPF protocol for the interfaces connected to R2 and R4 for lo0 reachability.

   content_copy zoom_out_map

   [edit]
   user@R3# set protocols ospf area 0.0.0.0 interface xe-0/2/0.0
   user@R3# set protocols ospf area 0.0.0.0 interface xe-0/2/1.0
   user@R3# set protocols ospf area 0.0.0.0 interface lo0.0 passive
   

5. Enter commit from configuration mode on R3 device.

Results

Verify your configuration by checking the below configurations from devices as follows:

Here's how you can verify configurations on R2:

user@R2# show interfaces

xe-0/2/0 {
    description R2-to-R1;
    unit 0 {
        family inet {
            address 192.168.12.2/30;
        }
        family iso;
    }
}
xe-0/2/1 {
    description R2-to-R3;
    unit 0 {
        family inet {
            address 10.1.23.1/30;
        }
    }
}
lo0 {
    unit 0 {
        family inet {
            address 10.1.255.2/32;
        }                               
        family iso {
            address 49.0001.0010.1255.0002.00;
        }
    }
}

user@R2# show routing-options

resolution {
    rib inet.0 {
        resolution-ribs inet.3;
    }
}
router-id 10.1.255.2;
autonomous-system 65000;
dynamic-tunnels {
    Tunnel-01 {
        source-address 10.1.255.2;
        ipip;
        destination-networks {
            10.1.255.0/24;
        }
    }
}

user@R2# show protocols

bgp {
    group iBGP {
        type internal;
        local-address 10.1.255.2;
        family inet {
            unicast;
        }
        export export-isis;
        neighbor 10.1.255.4;
    }
}
isis {
    interface xe-0/2/0.0;
    interface lo0.0;
    level 1 disable;
    export export-bgp;
}
ospf {
    area 0.0.0.0 {
        interface xe-0/2/1.0;
        interface lo0.0;
    }
}

user@R2# show policy-options

policy-statement export-bgp {
    term t1 {
        from protocol bgp;
        then accept;
    }
}
policy-statement export-isis {
    term t1 {
        from protocol isis;
        then {
            next-hop self;
            accept;
        }
    }
}

Step-by-Step Procedure for R1

R1 and R5 have a similar configuration so we will only show the step-by-step procedure for R1.

1. Enter configuration mode on R1.

2. Configure the interface connected to R2 and interface lo0. Make sure to configure both family inet and iso. Family iso is needed for protocol IS-IS.

   content_copy zoom_out_map

   [edit]
   user@R1# set interfaces xe-0/2/0 unit 0 description R1-to-R2
   user@R1# set interfaces xe-0/2/0 unit 0 family inet address 192.168.12.1/30
   user@R1# set interfaces xe-0/2/0 unit 0 family iso
   user@R1# set interfaces lo0 unit 0 family inet address 192.168.255.1/32
   user@R1# set interfaces lo0 unit 0 family iso address 49.0001.1920.1682.5501.00
   

3. Configure the Router ID.

   content_copy zoom_out_map

   [edit]
   user@R1# set routing-options router-id 192.168.255.1
   

4. Configure protocols IS-IS. Routes are advertised between R1 and R2 using the IS-IS protocol.

   content_copy zoom_out_map

   [edit]
   user@R1# set protocols isis interface xe-0/2/0.0
   user@R1# set protocols isis interface lo0.0
   user@R1# set protocols isis level 1 disable
   

5. Enter commit on R1 from the configuration mode.

Step-by-Step Procedure for R2

R2 and R4 have a similar configuration so we will only show the step-by-step procedure for R2.

1. Enter configuration mode on R2.

2. Configure the interfaces connected to R1 and R3 and interface lo0. Ensure to configure both familyinet and iso on the interface connected to R1 and lo0, and to configure both familyinet and mpls on the interface connected to R3.

   content_copy zoom_out_map

   [edit]
   user@R2# set interfaces xe-0/2/0 description R2-to-R1
   user@R2# set interfaces xe-0/2/0 unit 0 family inet address 192.168.12.2/30
   user@R2# set interfaces xe-0/2/0 unit 0 family iso
   user@R2# set interfaces xe-0/2/1 description R2-to-R3
   user@R2# set interfaces xe-0/2/1 unit 0 family inet address 10.1.23.1/30
   user@R2# set interfaces xe-0/2/0 unit 0 family mpls
   user@R2# set interfaces lo0 unit 0 family inet address 10.1.255.2/32
   user@R2# set interfaces lo0 unit 0 family iso address 49.0001.0010.1255.0002.00
   

3. Configure protocols IS-IS for the interface connected to R1. The export policy to advertise BGP routes into IS-IS is shown in the policy configuration step.

   content_copy zoom_out_map

   [edit]
   user@R2# set protocols isis interface xe-0/2/0.0 
   user@R2# set protocols isis interface lo0.0
   user@R2# set protocols isis level 1 disable
   user@R2# set protocols isis export export-bgp
   

4. Configure the OSPF protocol for the interface connected to R3 for lo0 reachability.

   content_copy zoom_out_map

   [edit]
   user@R2# set protocols ospf area 0.0.0.0 interface xe-0/2/1.0
   user@R2# set protocols ospf area 0.0.0.0 interface lo0.0
   

5. Configure the LDP and MPLS protocols for the interface connected to R3.

   content_copy zoom_out_map

   [edit]
   user@R2# set protocols ldp interface xe-0/2/1.0
   user@R2# set protocols mpls interface xe-0/2/1.0
   

6. Configure the router-id and autonomous-system under the routing-options hierarchy, and configure IBGP between R2 and R4. The import policy to add a community to the routes learned using BGP and the export policy to advertise IS-IS routes into BGP is shown in the policy configuration step. Ensure to include extended-nexthop-color option to the family inet unicast configuration to allow resolution using the inetcolor.0 table.

   content_copy zoom_out_map

   [edit]
   user@R2# set routing-options router-id 10.1.255.2
   user@R2# set routing-options autonomous-system 65000
   user@R2# set protocols bgp group iBGP type internal
   user@R2# set protocols bgp group iBGP local-address 10.1.255.2
   user@R2# set protocols bgp group iBGP import ipip-tunnel-color
   user@R2# set protocols bgp group iBGP family inet unicast extended-nexthop-color
   user@R2# set protocols bgp group iBGP export export-isis
   user@R2# set protocols bgp group iBGP neighbor 10.1.255.4

7. Configure the IP-IP dynamic tunnel Tunnel-01 from R2 to R4. The colors configuration option allows the tunnel to be created in the inetcolor.0 route table. The dyn-tunnel-attribute-policy set-dynamic-tunnel-ep configures a static tunnel endpoint. The policy is shown with the policy configuration step.

   content_copy zoom_out_map

   [edit]
   user@R2# set routing-options dynamic-tunnels Tunnel-01 source-address 10.1.255.2
   user@R2# set routing-options dynamic-tunnels Tunnel-01 ipip
   user@R2# set routing-options dynamic-tunnels Tunnel-01 destination-networks 10.1.255.0/24 dyn-tunnel-attribute-policy set-dynamic-tunnel-ep
   user@R2# set routing-options dynamic-tunnels Tunnel-01 destination-networks 10.1.255.0/24 colors 100
   

8. Configure the policies that were applied during the previous configuration steps. The export-bgp policy advertises BGP routes into IS-IS. The export-isis policy advertises IS-IS routes into BGP with changing the next-hop to R2. The ipip-tunnel-color policy applies the community to the route that is matched on in the colors configuration for the dynamic tunnel. The set-dynamic-tunnel-ep policy configures R4 as the tunnel endpoint.

   content_copy zoom_out_map

   [edit]
   user@R2# set policy-options policy-statement export-bgp term t1 from protocol bgp
   user@R2# set policy-options policy-statement export-bgp term t1 then accept
   user@R2# set policy-options policy-statement export-isis term t1 from protocol isis
   user@R2# set policy-options policy-statement export-isis term t1 then next-hop self
   user@R2# set policy-options policy-statement export-isis term t1 then accept
   user@R2# set policy-options policy-statement ipip-tunnel-color term term-01 from route-filter 192.168.255.5/32 exact
   user@R2# set policy-options policy-statement ipip-tunnel-color term term-01 then community add red
   user@R2# set policy-options policy-statement ipip-tunnel-color term term-01 then accept
   user@R2# set policy-options policy-statement set-dynamic-tunnel-ep term t1 from route-filter 10.1.255.4/32 exact
   user@R2# set policy-options policy-statement set-dynamic-tunnel-ep term t1 then tunnel-end-point-address 10.1.255.4
   user@R2# set policy-options policy-statement set-dynamic-tunnel-ep term t1 then accept
   user@R2# set policy-options community red members color:0:100
   

9. Enter commit from the configuration mode.

Step-by-Step Procedure for R3

1. Enter configuration mode on R3.

2. Configure the interfaces connected to R2 and R4 and interface lo0. Ensure to configure both family inet and mpls on the interfaces connected to R2 and R4.

   content_copy zoom_out_map

   [edit]
   user@R3# set interfaces xe-0/2/0 unit 0 description R3-to-R2
   user@R3# set interfaces xe-0/2/0 unit 0 family inet address 10.1.23.2/30
   user@R3# set interfaces xe-0/2/0 unit 0 family mpls
   user@R3# set interfaces xe-0/2/1 unit 0 description R3-to-R4
   user@R3# set interfaces xe-0/2/1 unit 0 family inet address 10.1.34.1/30
   user@R3# set interfaces xe-0/2/1 unit 0 family mpls
   user@R3# set interfaces lo0 unit 0 family inet address 10.1.255.3/32
   

3. Configure the Router ID.

   content_copy zoom_out_map

   [edit]
   user@R3# set routing-options router-id 10.1.255.3
   

4. Configure the OSPF protocol for the interfaces connected to R2 and R4 for lo0 reachability.

   content_copy zoom_out_map

   [edit]
   user@R3# set protocols ospf area 0.0.0.0 interface xe-0/2/0.0
   user@R3# set protocols ospf area 0.0.0.0 interface xe-0/2/1.0
   user@R3# set protocols ospf area 0.0.0.0 interface lo0.0 passive
   

5. Configure the LDP and MPLS protocols for the interfaces connected to R2 and R4.

   content_copy zoom_out_map

   [edit]
   user@R2# set protocols ldp interface xe-0/2/0.0
   user@R2# set protocols ldp interface xe-0/2/1.0
   user@R2# set protocols mpls interface xe-0/2/0.0
   user@R2# set protocols mpls interface xe-0/2/1.0
   

6. Enter commit from configuration mode on R3 device.

Results

Verify your configuration by checking the below configurations from the devices.

Here's how you can check the configurations on R2:

user@R2# show interfaces

xe-0/2/0 {
    description R2-to-R1;
    unit 0 {
        family inet {
            address 192.168.12.2/30;
        }
        family iso;
    }
}
xe-0/2/1 {
    description R2-to-R3;
    unit 0 {
        family inet {
            address 10.1.23.1/30;
        }
        family mpls;
    }
}
lo0 {
    apply-groups-except global;
    unit 0 {
        family inet {
            address 10.1.255.2/32;
        }
        family iso {
            address 49.0001.0010.1255.0002.00;
        }
    }
}

user@R2# show protocols

bgp {
    group iBGP {
        type internal;
        local-address 10.1.255.2;
        import ipip-tunnel-color;
        family inet {
            unicast {
                extended-nexthop-color;
            }
        }
        export export-isis;
        neighbor 10.1.255.4;
    }
}
isis {
    interface xe-0/2/0.0;
    interface lo0.0;
    level 1 disable;
    export export-bgp;
}
ldp {
    interface xe-0/2/1.0;
}
mpls {
    interface xe-0/2/1.0;
}
ospf {
    area 0.0.0.0 {
        interface xe-0/2/1.0;
        interface lo0.0;
    }
}

user@R2#show routing-options

router-id 10.1.255.2;
autonomous-system 65000;
dynamic-tunnels {
    Tunnel-01 {
        source-address 10.1.255.2;
        ipip;
        destination-networks {
            10.1.255.0/24 {
                dyn-tunnel-attribute-policy set-dynamic-tunnel-ep;
                colors 100;
            }
        }
    }
}

user@R2#show policy-options

policy-statement export-bgp {
    term t1 {
        from protocol bgp;
        then accept;
    }
}
policy-statement export-isis {
    term t1 {
        from protocol isis;
        then {
            next-hop self;
            accept;
        }
    }
}
policy-statement ipip-tunnel-color {
    term term-01 {
        from {
            route-filter 192.168.255.5/32 exact;
        }
        then {
            community add red;
            accept;
        }
    }
}
policy-statement set-dynamic-tunnel-ep {
    term t1 {
        from {
            route-filter 10.1.255.4/32 exact;
        }
        then {
            tunnel-end-point-address 10.1.255.4;
            accept;
        }
    }
}
community red members color:0:100;

Step-by-Step Procedure for R1

R1 and R5 have a similar configuration so we will only show the step-by-step procedure for R1.

1. Enter configuration mode on R1.

2. Configure the interface connected to R2 and interface lo0. Make sure to configure both family inet and iso. Family iso is needed for protocol IS-IS.

   content_copy zoom_out_map

   [edit]
   user@R1# set interfaces xe-0/2/0 unit 0 description R1-to-R2
   user@R1# set interfaces xe-0/2/0 unit 0 family inet address 192.168.12.1/30
   user@R1# set interfaces xe-0/2/0 unit 0 family iso
   user@R1# set interfaces lo0 unit 0 family inet address 192.168.255.1/32
   user@R1# set interfaces lo0 unit 0 family iso address 49.0001.1920.1682.5501.00
   

3. Configure the Router ID.

   content_copy zoom_out_map

   [edit]
   user@R1# set routing-options router-id 192.168.255.1
   

4. Configure protocols IS-IS. Routes are advertised between R1 and R2 using the IS-IS protocol.

   content_copy zoom_out_map

   [edit]
   user@R1# set protocols isis interface xe-0/2/0.0
   user@R1# set protocols isis interface lo0.0
   user@R1# set protocols isis level 1 disable
   

5. Enter commit on R1 from the configuration mode.

Step-by-Step Procedure for R2

R2 and R4 have a similar configuration so we will only show the step-by-step procedure for R2.

1. Enter configuration mode on R2.

2. Configure the interfaces connected to R1 and R3 and interface lo0. Ensure to configure both familyinet and iso on the interface connected to R1 and lo0, and to configure both familyinet and mpls on the interface connected to R3.

   content_copy zoom_out_map

   [edit]
   user@R2# set interfaces xe-0/2/0 description R2-to-R1
   user@R2# set interfaces xe-0/2/0 unit 0 family inet address 192.168.12.2/30
   user@R2# set interfaces xe-0/2/0 unit 0 family iso
   user@R2# set interfaces xe-0/2/1 description R2-to-R3
   user@R2# set interfaces xe-0/2/1 unit 0 family inet address 10.1.23.1/30
   user@R2# set interfaces xe-0/2/0 unit 0 family mpls
   user@R2# set interfaces lo0 unit 0 family inet address 10.1.255.2/32
   user@R2# set interfaces lo0 unit 0 family iso address 49.0001.0010.1255.0002.00
   

3. Configure protocols IS-IS for the interface connected to R1. The export policy to advertise BGP routes into IS-IS is shown in the policy configuration step.

   content_copy zoom_out_map

   [edit]
   user@R2# set protocols isis interface xe-0/2/0.0 
   user@R2# set protocols isis interface lo0.0
   user@R2# set protocols isis level 1 disable
   user@R2# set protocols isis export export-bgp
   

4. Configure the OSPF protocol for the interface connected to R3 for lo0 reachability.

   content_copy zoom_out_map

   [edit]
   user@R2# set protocols ospf area 0.0.0.0 interface xe-0/2/1.0
   user@R2# set protocols ospf area 0.0.0.0 interface lo0.0
   

5. Configure the LDP and MPLS protocols for the interface connected to R3.

   content_copy zoom_out_map

   [edit]
   user@R2# set protocols ldp interface xe-0/2/1.0
   user@R2# set protocols mpls interface xe-0/2/1.0
   

6. Configure the router-id and autonomous-system under the routing-options hierarchy, and configure IBGP between R2 and R4. The import policy to add a community to the routes learned using BGP and the export policy to advertise IS-IS routes into BGP and set the tunnel attributes is shown in the policy configuration step. Ensure to include the extended-nexthop-tunnel option with the family inet unicast configuration to allow resolution using the inetcolor.0 table.

   content_copy zoom_out_map

   [edit]
   user@R2# set routing-options router-id 10.1.255.2
   user@R2# set routing-options autonomous-system 65000
   user@R2# set protocols bgp group iBGP type internal
   user@R2# set protocols bgp group iBGP local-address 10.1.255.2
   user@R2# set protocols bgp group iBGP family inet unicast extended-nexthop-tunnel
   user@R2# set protocols bgp group iBGP export export-tunnel-route
   user@R2# set protocols bgp group iBGP neighbor 10.1.255.4

7. Configure routing options on R2 to create a tunnel from R2 to R4. The bgp-signal option enables the tunnel creation signaled by BGP. The colors configuration option allows the tunnel to be created in the inetcolor.0 route table.

   content_copy zoom_out_map

   [edit]
   user@R2# set routing-options dynamic-tunnels Tunnel-01 source-address 10.1.255.2
   user@R2# set routing-options dynamic-tunnels Tunnel-01 bgp-signal
   user@R2# set routing-options dynamic-tunnels Tunnel-01 destination-networks 10.1.255.0/24 colors 100
   

8. Configure the policies that were applied during the previous configuration steps. The export-bgp policy advertises BGP routes into IS-IS. The export-tunnel-route policy advertises the IS-IS route from R1 into BGP with the tunnel-attribute and changes the next-hop to R2. The tunnel-attr-01 tunnel-attribute sets the tunnel-type, the tunnel endpoint, and the color matched on in the colors configuration for the dynamic tunnel.

   content_copy zoom_out_map

   [edit]
   user@R2# set policy-options policy-statement export-bgp term t1 from protocol bgp
   user@R2# set policy-options policy-statement export-bgp term t1 then accept
   user@R2# set policy-options policy-statement export-tunnel-route term t1 from route-filter 192.168.255.1/32 exact
   user@R2# set policy-options policy-statement export-tunnel-route term t1 then tunnel-attribute set tunnel-attr-01
   user@R2# set policy-options policy-statement export-tunnel-route term t1 then next-hop self
   user@R2# set policy-options policy-statement export-tunnel-route term t1 then accept
   user@R2# set policy-options tunnel-attribute tunnel-attr-01 tunnel-type ipip
   user@R2# set policy-options tunnel-attribute tunnel-attr-01 tunnel-color 100
   user@R2# set policy-options tunnel-attribute tunnel-attr-01 remote-end-point 10.1.255.4
   

9. Enter commit from the configuration mode.

Step-by-Step Procedure for R3

1. Enter configuration mode on R3.

2. Configure the interfaces connected to R2 and R4 and interface lo0. Ensure to configure both family inet and mpls on the interfaces connected to R2 and R4.

   content_copy zoom_out_map

   [edit]
   user@R3# set interfaces xe-0/2/0 unit 0 description R3-to-R2
   user@R3# set interfaces xe-0/2/0 unit 0 family inet address 10.1.23.2/30
   user@R3# set interfaces xe-0/2/0 unit 0 family mpls
   user@R3# set interfaces xe-0/2/1 unit 0 description R3-to-R4
   user@R3# set interfaces xe-0/2/1 unit 0 family inet address 10.1.34.1/30
   user@R3# set interfaces xe-0/2/1 unit 0 family mpls
   user@R3# set interfaces lo0 unit 0 family inet address 10.1.255.3/32
   

3. Configure the Router ID.

   content_copy zoom_out_map

   [edit]
   user@R3# set routing-options router-id 10.1.255.3
   

4. Configure the OSPF protocol for the interfaces connected to R2 and R4 for lo0 reachability.

   content_copy zoom_out_map

   [edit]
   user@R3# set protocols ospf area 0.0.0.0 interface xe-0/2/0.0
   user@R3# set protocols ospf area 0.0.0.0 interface xe-0/2/1.0
   user@R3# set protocols ospf area 0.0.0.0 interface lo0.0 passive
   

5. Configure the LDP and MPLS protocols for the interfaces connected to R2 and R4.

   content_copy zoom_out_map

   [edit]
   user@R2# set protocols ldp interface xe-0/2/0.0
   user@R2# set protocols ldp interface xe-0/2/1.0
   user@R2# set protocols mpls interface xe-0/2/0.0
   user@R2# set protocols mpls interface xe-0/2/1.0
   

6. Enter commit from configuration mode on R3 device.

Purpose

Verify routes sent by using BGP protocol.

Action

R2

user@R2> show route protocol bgp

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

192.168.255.5/32   *[BGP/170] 01:21:51, MED 10, localpref 100, from 10.1.255.4
                      AS path: I, validation-state: unverified
                    >  via Tunnel Composite, IPoIP (src 10.1.255.2 dest 10.1.255.4-100<c> tunnel-endpoint 10.1.255.2)

inet.3: 3 destinations, 3 routes (3 active, 0 holddown, 0 hidden)

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

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

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

inetcolor.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)

Meaning

The output shows the routes from BGP.

Purpose

Verify the routes received through BGP by using the following operational mode commands.

Action

R2

user@R2> show route receive-protocol bgp 10.1.255.4 192.168.255.5 extensive

inet.0: 18 destinations, 18 routes (18 active, 0 holddown, 0 hidden)
* 192.168.255.5/32 (1 entry, 1 announced)
     Accepted
     Nexthop: 10.1.255.4
     MED: 10
     Localpref: 100
     AS path: I 
     Tunnel type: ipip, Tunnel color: 100, Remote end point: 10.1.255.2

Meaning

The R2 output indicates the routes received on the devices.

Purpose

Verify the dynamic tunnel is up and BGP signaled.

Action

R2

user@R2> show dynamic-tunnels database
*- Signal Tunnels #- PFE-down
Table: inet.3       

Destination-network: 10.1.255.0/24

*- Signal Tunnels #- PFE-down
Table: inetcolor.0  

Destination-network: 10.1.255.0-0<c>/24

Tunnel to: 10.1.255.4-100<c>/64
  Reference count: 3
  Next-hop type: IPoIP (bgp-signalled forwarding-nexthop)     Tunnel-endpoint: 10.1.255.2
    Source address: 10.1.255.2
    Next hop: tunnel-composite, 0x76b7238, nhid 592
      Reference count: 2
      Ingress Route: [OSPF] 10.1.255.4/32, via metric 2
      Tunnel Endpoint Ingress Route: [Direct] 10.1.255.2/32
      Traffic Statistics: Packets 0, Bytes 0 
      State: Up
  Aggregate Traffic Statistics:
    Tunnel Encapsulation: Dest 10.1.255.2, Src 10.1.255.2, IPoIP, Tunnel-Id 1
    Traffic Statistics: Packets 0, Bytes 0 

Meaning

The R2 output indicates the tunnel is up and BGP signaled.

Purpose

To verify the route resolution of the route in the inetcolor.0 table, use the show route table inetcolor.0 operational mode commands.

Action

user@R2> show route table inetcolor.0

inetcolor.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

10.1.255.0-0<c>/24                
                   *[Tunnel/305] 01:33:33
                       Tunnel
10.1.255.4-100<c>/64                
                   *[Tunnel/305] 01:28:44, metric 2
                       Tunnel Composite, BGP-Signal (src 10.1.255.2 dest 10.1.255.4-100<c>)

Meaning

The R2 output indicates the tunnel to 10.1.255.4 is BGP signaled.

Purpose

Verify R1 can ping R5 by using the ping 192.168.255.5 source 192.168.255.1 count 2 operational mode command.

Action

user@R1>ping 192.168.255.5 source 192.168.255.1 count 2
PING 192.168.255.5 (192.168.255.5): 56 data bytes
64 bytes from 192.168.255.5: icmp_seq=0 ttl=63 time=2.784 ms
64 bytes from 192.168.255.5: icmp_seq=1 ttl=63 time=1.904 ms

--- 192.168.255.5 ping statistics ---
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max/stddev = 1.904/2.344/2.784/0.440 ms

Meaning

The output from R1 shows that R1 can ping R5.