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.

English  

English

Example: Configuring Packet Forwarding Engine FIB Localization

Requirements

Before you begin:

1. Configure device interfaces and loopback interface addresses.
2. Configure static routes.
3. Configure OSPF and OSPFv3 and make sure that OSPF adjacencies and OSPF routes to loopback addresses are established.

• A T320, T640,T1600, or MX Series router.
• Junos OS Release 11.4 or later running on the router for T-Series routers. Junos OS Release 12.3 or later running on the router for MX Series routers..

Overview

In this example, you configure the chassis for IPv4 and IPv6 routes and FIB localization on Router R0 and then configure the edge-facing Packet Forwarding Engines on FPC0 as fib-remote and the core-facing Packet Forwarding Engines on FPC1 and FPC2 as fib-local. You then configure a routing policy named fib-policy with the no-route-localize option to ensure that all routes from a specified route filter are installed on the FIB-remote FPC.

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 route localization or FIB localization for IPv4 and IPv6 traffic.
   [edit chassis]user@R0# set route-localization inetuser@R0# set route-localization inet6
2. Configure the Packet Forwarding Engine of an FPC as either fib-local or fib-remote.
   [edit chassis]user@R0# set fpc 0 route-localization fib-remoteuser@R0# set fpc 1 route-localization fib-localuser@R0# set fpc 2 route-localization fib-local
3. Configure the routing policy by including the no-route-localize statement to enable the forwarding table policy to mark route prefixes such that the routes are installed into forwarding hardware on the FIB-remote Packet Forwarding Engines.
   [edit policy-options]user@R0# set policy-statement fib-policy term a from route-filter 4.4.4.4/32 exactuser@R0# set policy-statement fib-policy term a then no-route-localizeuser@R0# set policy-statement fib-policy term b from route-filter fec0:4444::4/128 exactuser@R0# set policy-statement fib-policy term b then no-route-localizeuser@host# set policy-statement fib-policy then accept

   Note: At least, one Packet Forwarding Engine must be configured as fib-local for the commit operation to be successful. If you do not configure fib-local for the Packet Forwarding Engine, the CLI displays an appropriate error message and the commit fails.

Results

From configuration mode, confirm your configuration by entering the show chassis and show policy-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 Policy Configuration
• Verifying FIB-Localization Configuration
• Verifying Routes After the Policy Is Applied

Verifying Policy Configuration

Purpose

Verify that the configured policy exists.

Action

Issue the show policy fib-policy command to check that the configured policy fib-policy exists.

Policy fib-policy:
    Term a:
        from
             route filter:
                 4.4.4.4/32 exact
        then no-route-localize
    Term b:
        from
             route filter:
                 fec0:4444::4/128 exact
        then no-route-localize
    Term unnamed:
        then accept

Verifying FIB-Localization Configuration

Purpose

Verify FIB-localization configuration details by using the show route localization and show route localization detail commands.

Action

FIB localization ready FPCs (and FIB-local Forwarding Engine addresses)
  FIB-local:  FPC2(4,5)
  FIB-remote: FPC0, FPC1
  Normal:     FPC3, FPC4, FPC5, FPC6, FPC7

FIB localization ready FPCs (and FIB-local Forwarding Engine addresses)
  FIB-local:  FPC2(4,5)
  FIB-remote: FPC0, FPC1
  Normal:     FPC3, FPC4, FPC5, FPC6, FPC7
FIB localization configuration
  Protocols:  inet, inet6
  FIB-local:  FPC2
  FIB-remote: FPC0, FPC1
Forwarding Engine addresses
  FPC0: 1
  FPC1: 2
  FPC2: 4, 5
  FPC3: 6
  FPC4: 8
  FPC5: 11
  FPC6: 13
  FPC7: 15

Verifying Routes After the Policy Is Applied

Purpose

Verify that routes with the no-route-localize policy option are installed on the fib-remote FPC.

Action

inet.0: 30 destinations, 30 routes (29 active, 0 holddown, 1 hidden)
4.4.4.4/32 (1 entry, 1 announced)
TSI:
KRT in-kernel 4.4.4.4/32 -> {130.168.0.2 Flags no-localize}
                                          ^^^^^^^^^^^^^^^^^
        *Static Preference: 5
                Next hop type: Router, Next hop index: 629
                Next-hop reference count: 3
                Next hop: 130.168.0.2 via ge-1/0/4.0, selected
                State: <Active Int="">                 
						 Age: 10:33                 
						 Task: RT                 
						 Announcement bits (1): 0-KRT                 
						 AS path: I</Active
>