Rate and give feedback:  Feedback Received. Thank You!

Rate and give feedback: 

X

This document helped resolve my issue

Yes No

Additional Comments

800 characters remaining

May we contact you if necessary?

Name:  

E-mail: 

Enter a valid Email ID

Need product assistance? Contact Juniper Support

Submit

This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply.

Example: Redistributing OSPF Routes into IS-IS

Requirements

No special configuration beyond device initialization is required before configuring this example.

Overview

Export policy can be applied to IS-IS to facilitate route redistribution.

Junos OS does not support the application of import policy for link-state routing protocols like IS-IS because such policies can lead to inconsistent link-state database (LSDB) entries, which in turn can result in routing inconstancies.

In this example, OSPF routes 192.168.0/24 through 192.168.3/24 are redistributed into IS-IS area 49.0002 from Device R2.

In addition, policies are configured to ensure that Device R1 can reach destinations on the 10.0.0.44/30 network, and that Device R3 can reach destinations on the 10.0.0.36/30 network. This enables end-to-end reachability.

Figure 1 shows the topology used in this example.

Figure 1: IS-IS Route Redistribution Topology

CLI Quick Configuration shows the configuration for all of the devices in Figure 1. The section Step-by-Step Procedure describes the steps on Device R2. Step-by-Step Procedure describes the steps on Device R3.

Configuration

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.

Step-by-Step Procedure

1. Configure the network interfaces.
   [edit interfaces]user@R2# set fe-1/2/1 unit 0 description to-R5user@R2# set fe-1/2/1 unit 0 family inet address 10.0.0.37/30user@R2# set fe-1/2/1 unit 0 family isouser@R2# set fe-1/2/0 unit 0 description to-OSPF-networkuser@R2# set fe-1/2/0 unit 0 family inet address 10.0.0.45/30user@R2# set lo0 unit 0 family inet address 172.16.9.7/32user@R2# set lo0 unit 0 family iso address 49.0002.0172.0016.0907.00
2. Configure IS-IS on the interface facing Device R1 and the loopback interface.
   [edit protocols isis]user@R2# set interface fe-1/2/1.0user@R2# set interface lo0.0
3. Configure the policy that enables Device R1 to reach the 10.0.0.44/30 network.
   [edit policy-options policy-statement send-direct-to-isis-neighbors]user@R2# set from protocol directuser@R2# set from route-filter 10.0.0.44/30 exactuser@R2# set then accept
4. Apply the policy that enables Device R1 to reach the 10.0.0.44/30 network.
   [edit protocols isis]user@R2# set export send-direct-to-isis-neighbors
5. Configure OSPF on the interfaces.
   [edit protocols ospf]user@R2# set area 0.0.0.1 interface fe-1/2/0.0user@R2# set area 0.0.0.1 interface lo0.0 passive
6. Configure the OSPF route redistribution policy.
   [edit policy-options policy-statement ospf-isis term 1]user@R2# set from protocol ospfuser@R2# set from route-filter 192.168.0.0/22 longeruser@R2# set then accept
7. Apply the OSPF route redistribution policy to the IS-IS instance.
   [edit protocols isis]user@R2# set export ospf-isis
8. Configure the policy that enables Device R3 to reach the 10.0.0.36/30 network.
   [edit policy-options policy-statement send-direct-to-ospf-neighbors]user@R2# set from protocol directuser@R2# set from route-filter 10.0.0.36/30 exactuser@R2# set then accept
9. Apply the policy that enables Device R3 to reach the 10.0.0.36/30 network.
   [edit protocols ospf]user@R2# set export send-direct-to-ospf-neighbors

Step-by-Step Procedure

1. Configure the network interfaces.

   Multiple addresses are configured on the loopback interface to simulate multiple route destinations.

   [edit interfaces]user@R3# set fe-1/2/0 unit 0 family inet address 10.0.0.46/30user@R3# set lo0 unit 0 family inet address 192.168.1.1/32user@R3# set lo0 unit 0 family inet address 192.168.2.1/32user@R3# set lo0 unit 0 family inet address 192.168.3.1/32user@R3# set lo0 unit 0 family inet address 192.168.0.1/32
2. Configure static routes to the loopback interface addresses.

   These are the routes that are redistributed into IS-IS.

   [edit routing-options static]user@R3# set route 192.168.0.0/24 discarduser@R3# set route 192.168.1.0/24 discarduser@R3# set route 192.168.3.0/24 discarduser@R3# set route 192.168.2.0/24 discard
3. Configure OSPF on the interfaces.
   [edit protocols ospf area 0.0.0.1]user@R3# set interface fe-1/2/0.0user@R3# set interface lo0.0 passive
4. Configure the OSPF policy to export the static routes.
   [edit policy-options policy-statement ospf term 1]user@R3# set from protocol staticuser@R3# set then accept
5. Apply the OSPF export policy.
   [edit protocols ospf]user@R3# set export ospf

Results

From configuration mode, confirm your configuration by entering the show interfaces, show protocols, show policy-options, and show routing-options commands. If the output does not display the intended configuration, repeat the instructions in this example to correct the configuration.

If you are done configuring the device, enter commit from configuration mode.

Verification

Confirm that the configuration is working properly.

• Verifying OSPF Route Advertisement
• Verifying Route Redistribution
• Verifying Connectivity

Verifying OSPF Route Advertisement

Purpose

Make sure that the expected routes are advertised by OSPF.

Action

From operational mode on Device R2, enter the show route protocol ospf command.

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

192.168.0.0/24     *[OSPF/150] 03:54:21, metric 0, tag 0
                    > to 10.0.0.46 via fe-1/2/0.0
192.168.0.1/32     *[OSPF/10] 03:54:21, metric 1
                    > to 10.0.0.46 via fe-1/2/0.0
192.168.1.0/24     *[OSPF/150] 03:54:21, metric 0, tag 0
                    > to 10.0.0.46 via fe-1/2/0.0
192.168.1.1/32     *[OSPF/10] 03:54:21, metric 1
                    > to 10.0.0.46 via fe-1/2/0.0
192.168.2.0/24     *[OSPF/150] 03:54:21, metric 0, tag 0
                    > to 10.0.0.46 via fe-1/2/0.0
192.168.2.1/32     *[OSPF/10] 03:54:21, metric 1
                    > to 10.0.0.46 via fe-1/2/0.0
192.168.3.0/24     *[OSPF/150] 03:54:21, metric 0, tag 0
                    > to 10.0.0.46 via fe-1/2/0.0
192.168.3.1/32     *[OSPF/10] 03:54:21, metric 1
                    > to 10.0.0.46 via fe-1/2/0.0
224.0.0.5/32       *[OSPF/10] 03:56:03, metric 1
                         MultiRecv

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

Meaning

The 192.168/16 routes are advertised by OSPF.

Verifying Route Redistribution

Purpose

Make sure that the expected routes are redistributed from OSPF into IS-IS.

Action

From operational mode on Device R1, enter the show route protocol isis command.

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

10.0.0.44/30       *[IS-IS/160] 03:45:24, metric 20
                    > to 10.0.0.37 via fe-1/2/0.0
172.16.9.7/32      *[IS-IS/15] 03:49:46, metric 10
                    > to 10.0.0.37 via fe-1/2/0.0
192.168.0.0/24     *[IS-IS/160] 03:49:46, metric 10
                    > to 10.0.0.37 via fe-1/2/0.0
192.168.0.1/32     *[IS-IS/160] 03:49:46, metric 11, tag2 1
                    > to 10.0.0.37 via fe-1/2/0.0
192.168.1.0/24     *[IS-IS/160] 03:49:46, metric 10
                    > to 10.0.0.37 via fe-1/2/0.0
192.168.1.1/32     *[IS-IS/160] 03:49:46, metric 11, tag2 1
                    > to 10.0.0.37 via fe-1/2/0.0
192.168.2.0/24     *[IS-IS/160] 03:49:46, metric 10
                    > to 10.0.0.37 via fe-1/2/0.0
192.168.2.1/32     *[IS-IS/160] 03:49:46, metric 11, tag2 1
                    > to 10.0.0.37 via fe-1/2/0.0
192.168.3.0/24     *[IS-IS/160] 03:49:46, metric 10
                    > to 10.0.0.37 via fe-1/2/0.0
192.168.3.1/32     *[IS-IS/160] 03:49:46, metric 11, tag2 1
                    > to 10.0.0.37 via fe-1/2/0.0

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

Meaning

The 192.168/16 routes are redistributed into IS-IS.

Verifying Connectivity

Purpose

Check that Device R1 can reach the destinations on Device R3.

Action

From operational mode, enter the ping command.

PING 192.168.1.1 (192.168.1.1): 56 data bytes
64 bytes from 192.168.1.1: icmp_seq=0 ttl=63 time=2.089 ms
64 bytes from 192.168.1.1: icmp_seq=1 ttl=63 time=1.270 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=63 time=2.135 ms

Meaning

These results confirm that Device R1 can reach the destinations in the OSPF network.