Load Balancing for a BGP Session

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.

set protocols bgp group external type external 
set protocols bgp group external peer-as 64501
set protocols bgp group external multipath 
set protocols bgp group external neighbor 10.0.1.1 
set protocols bgp group external neighbor 10.0.0.2 
set policy-options policy-statement loadbal from route-filter 10.0.0.0/16 orlonger 
set policy-options policy-statement loadbal then load-balance per-packet 
set routing-options forwarding-table export loadbal
set routing-options autonomous-system 64500

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 Junos OS CLI User Guide.

To configure the BGP peer sessions:

1. Configure the BGP group.

   content_copy zoom_out_map

   [edit protocols bgp group external]
   user@R1# set type external 
   user@R1# set peer-as 64501 
   user@R1# set neighbor 10.0.1.1 
   user@R1# set neighbor 10.0.0.2 
   

2. Enable the BGP group to use multiple paths.

   Note:

   To disable the default check requiring that paths accepted by BGP multipath must have the same neighboring autonomous system (AS), include the multiple-as option.

   content_copy zoom_out_map

   [edit protocols bgp group external]
   user@R1# set multipath
   

3. Configure the load-balancing policy.

   content_copy zoom_out_map

   [edit policy-options policy-statement loadbal]
   user@R1# set from route-filter 10.0.0.0/16 orlonger 
   user@R1# set then load-balance per-packet 
   

4. Apply the load-balancing policy.

   content_copy zoom_out_map

   [edit routing-options]
   user@R1# set forwarding-table export loadbal
   

5. Configure the local autonomous system (AS) number.

   content_copy zoom_out_map

   [edit routing-options]
   user@R1# set autonomous-system 64500
   

Results

From configuration mode, confirm your configuration by entering the 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.

[edit]
user@R1# show protocols
bgp {
    group external {
        type external;
        peer-as 64501;
        multipath;
        neighbor 10.0.1.1;
        neighbor 10.0.0.2;
    }
}

[edit]
user@R1# show policy-options
policy-statement loadbal {
    from {
        route-filter 10.0.0.0/16 orlonger;
    }
    then {
        load-balance per-packet;
    }
}

[edit]
user@R1# show routing-options
autonomous-system 64500;
forwarding-table {
    export loadbal;
}

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

Purpose

Verify that routes are learned from both routers in the neighboring AS.

Action

From operational mode, run the show route command.

user@R1> show route 10.0.2.0
inet.0: 12 destinations, 15 routes (12 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

10.0.2.0/30        *[BGP/170] 03:12:32, localpref 100
                      AS path: 64501 I
                      to 10.0.1.1 via ge-1/2/0.0
                    > to 10.0.0.2 via ge-1/2/1.0
                    [BGP/170] 03:12:32, localpref 100
                      AS path: 64501 I
                    > to 10.0.1.1 via ge-1/2/0.0

user@R1> show route 10.0.2.0 detail
inet.0: 12 destinations, 15 routes (12 active, 0 holddown, 0 hidden)
10.0.2.0/30 (2 entries, 1 announced)
        *BGP    Preference: 170/-101
                Next hop type: Router, Next hop index: 262142
                Next-hop reference count: 3
                Source: 10.0.0.2
                Next hop: 10.0.1.1 via ge-1/2/0.0
                Next hop: 10.0.0.2 via ge-1/2/1.0, selected
                State: <Active Ext>
                Local AS: 64500 Peer AS: 64501
                Age: 3:18:30 
                Task: BGP_64501.10.0.0.2+55402
                Announcement bits (1): 2-KRT 
                AS path: 64501 I
                Accepted Multipath
                Localpref: 100
                Router ID: 192.168.2.1
         BGP    Preference: 170/-101
                Next hop type: Router, Next hop index: 602
                Next-hop reference count: 5
                Source: 10.0.1.1
                Next hop: 10.0.1.1 via ge-1/2/0.0, selected
                State: <NotBest Ext>
                Inactive reason: Not Best in its group - Active preferred
                Local AS: 64500 Peer AS: 64501
                Age: 3:18:30 
                Task: BGP_64501.10.0.1.1+53135
                AS path: 64501 I
                Accepted
                Localpref: 100
                Router ID: 192.168.3.1

Meaning

The active path, denoted with an asterisk (*), has two next hops: 10.0.1.1 and 10.0.0.2 to the 10.0.2.0 destination. The 10.0.1.1 next hop is copied from the inactive path to the active path.

Purpose

Verify that both next hops are installed in the forwarding table.

Action

From operational mode, run the show route forwarding-table command.

user@R1> show route forwarding-table destination 10.0.2.0
Routing table: default.inet
Internet:
Destination        Type RtRef Next hop           Type Index NhRef Netif
10.0.2.0/30        user     0                    ulst 262142     2
                              10.0.1.1           ucst   602     5 ge-1/2/0.0
                              10.0.0.2           ucst   522     6 ge-1/2/1.0

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 Junos OS CLI User Guide.

To configure Device R0:

1. Configure the interfaces.

   content_copy zoom_out_map

   [edit interfaces fe-1/2/0 unit 0]
   user@R0# set family inet address 10.1.0.1/30
   [edit interfaces fe-1/2/1 unit 0]
   user@R0# set family inet address 10.1.1.1/30
   [edit interfaces lo0 unit 0]
   user@R0# set family inet address 10.255.14.179/32
   

2. Configure EBGP.

   content_copy zoom_out_map

   [edit protocols bgp group ext]
   user@R0# set type external
   user@R0# set peer-as 65000
   user@R0# set neighbor 10.1.0.2
   user@R0# set neighbor 10.1.1.2
   

3. Enable multipath BGP between Device R0 and Device R1.

   content_copy zoom_out_map

   [edit protocols bgp group ext]
   user@R0# set multipath
   

4. Configure static routes to remote networks. These routes are not part of the topology. The purpose of these routes is to demonstrate the functionality in this example.

   content_copy zoom_out_map

   [edit routing-options]
   user@R0# set static route 10.1.10.10/32 reject
   user@R0# set static route 10.1.230.0/23 reject
   

5. Configure routing policies that accept the static routes.

   content_copy zoom_out_map

   [edit policy-options policy-statement agg_route term 1]
   user@R0# set from protocol static
   user@R0# set from route-filter 10.1.230.0/23 exact
   user@R0# set then accept
   [edit policy-options policy-statement test_route term 1]
   user@R0# set from protocol static
   user@R0# set from route-filter 10.1.10.10/32 exact
   user@R0# set then accept
   

6. Export the agg_route and test_route policies from the routing table into BGP.

   content_copy zoom_out_map

   [edit protocols bgp group ext]
   user@R0# set export test_route
   user@R0# set export agg_route
   

7. Configure the autonomous system (AS) number.

   content_copy zoom_out_map

   [edit routing-options]
   user@R0# set autonomous-system 65500
   

Results

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

user@R0# show interfaces
fe-1/2/0 {
    unit 0 {
        family inet {
            address 10.1.0.1/30;
        }
    }
}
fe-1/2/1 {
    unit 0 {
        family inet {
            address 10.1.1.1/30;
        }
    }
}
lo0 {
    unit 0 {
        family inet {
            address 10.255.14.179/32;
        }
    }
}

user@R0# show policy-options
policy-statement agg_route {
    term 0 {
        from {
            protocol static;
            route-filter 10.1.230.0/23 exact;
        }
        then accept;
    }
}
policy-statement test_route {
    term 1 {
        from {
            protocol static;
            route-filter 10.1.10.10/32 exact;
        }
        then accept;
    }
}

user@R0# show protocols
bgp {
    group ext {
        type external;
        export [ test_route agg_route ];
        peer-as 65000;
        multipath;
        neighbor 10.1.0.2;
        neighbor 10.1.1.2;
    }
}

user@R0# show routing-options
static {
    route 10.1.10.10/32 reject;
    route 10.1.230.0/23 reject;
}
autonomous-system 65500;

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

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 Junos OS CLI User Guide.

To configure Device R1:

1. Configure the interfaces.

   content_copy zoom_out_map

   [edit interfaces fe-1/2/0 unit 0]
   user@R1# set family inet address 10.1.0.2/30
   [edit interfaces fe-1/2/1 unit 0]
   user@R1# set family inet address 10.1.1.2/30
   [edit interfaces fe-1/2/2 unit 0]
   user@R1# set family inet address 10.12.0.1/30
   [edit interfaces lo0 unit 0]
   user@R1# set family inet address 10.255.71.24/32
   

2. Configure OSPF.

   content_copy zoom_out_map

   [edit protocols ospf area 0.0.0.0]
   user@R1# set interface fe-1/2/1.0
   user@R1# set interface 10.255.71.24
   

3. Enable Device R1 to accept the remote next hop.

   content_copy zoom_out_map

   [edit protocols bgp]
   user@R1# set accept-remote-nexthop
   

4. Configure IBGP.

   content_copy zoom_out_map

   [edit protocols bgp group int]
   user@R1# set type internal
   user@R1# set local-address 10.255.71.24
   user@R1# set neighbor 10.255.14.177
   

5. Configure EBGP.

   content_copy zoom_out_map

   [edit protocols bgp group ext]
   user@R1# set type external
   user@R1# set peer-as 65500
   user@R1# set neighbor 10.1.0.1
   user@R1# set neighbor 10.1.1.1
   

6. Enable multipath BGP between Device R0 and Device R1.

   content_copy zoom_out_map

   [edit protocols bgp group ext]
   user@R1# set multipath
   

7. Configure a routing policy that enables a single-hop external BGP peer (Device R1) to accept the remote next-hop 10.1.10.10 for the route to the 10.1.230.0/23 network.

   content_copy zoom_out_map

   [edit policy-options policy-statement agg_route term 1]
   user@R1# set from protocol bgp
   user@R1# set from route-filter 10.1.230.0/23 exact
   user@R1# set then next-hop 10.1.10.10
   user@R1# set then accept
   

8. Import the agg_route policy into the routing table on Device R1.

   content_copy zoom_out_map

   [edit protocols bgp group ext]
   user@R1# set import agg_route
   

9. Configure the autonomous system (AS) number.

   content_copy zoom_out_map

   [edit routing-options]
   user@R1# set autonomous-system 65000
   

Results

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

user@R1# show interfaces
fe-1/2/0 {
    unit 0 {
        family inet {
            address 10.1.0.2/30;
        }
    }
}
fe-1/2/1 {
    unit 0 {
        family inet {
            address 10.1.1.2/30;
        }
    }
}
fe-1/2/2 {
    unit 0 {
        family inet {
            address 10.12.0.1/30;
        }
    }
}
lo0 {
    unit 0 {
        family inet {
            address 10.255.71.24/32;
        }
    }
}

user@R1# show policy-options
policy-statement agg_route {
    term 1 {
        from {
            protocol bgp;
            route-filter 10.1.230.0/23 exact;
        }
        then {
            next-hop 10.1.10.10;
            accept;
        }
    }
}

user@R1# show protocols
bgp {
    accept-remote-nexthop;
    group ext {
        type external;
        import agg_route;
        peer-as 65500;
        multipath;
        neighbor 10.1.0.1;
        neighbor 10.1.1.1;
    }
    group int {
        type internal;
        local-address 10.255.71.24;
        neighbor 10.255.14.177;
    }
}
ospf {
    area 0.0.0.0 {
        interface fe-1/2/1.0;
        interface 10.255.71.24;
    }
}

user@R1# show routing-options
autonomous-system 65000;

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

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 Junos OS CLI User Guide.

To configure Device R2:

1. Configure the interfaces.

   content_copy zoom_out_map

   [edit interfaces fe-1/2/0 unit 0]
   user@R2# set family inet address 10.12.0.2/30
   [edit  interfaces lo0 unit 0]
   user@R2# set family inet address 10.255.14.177/32
   

2. Configure OSPF.

   content_copy zoom_out_map

   [edit protocols ospf area 0.0.0.0]
   user@R2# set interface fe-1/2/0.0
   user@R2# set interface 10.255.14.177
   

3. Configure IBGP.

   content_copy zoom_out_map

   [edit protocols bgp group int]
   user@R2# set type internal
   user@R2# set local-address 10.255.14.177
   user@R2# set neighbor 10.255.71.24
   

4. Configure the autonomous system (AS) number.

   content_copy zoom_out_map

   [edit routing-options]
   user@R1# set autonomous-system 65000
   

Results

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

user@R2# show interfaces
fe-1/2/0 {
    unit 0 {
        family inet {
            address 10.12.0.2/30;
        }
    }
}
lo0 {
    unit 0 {
        family inet {
            address 10.255.14.177/32;
        }
    }
}

user@R2# show protocols
bgp {
    group int {
        type internal;
        local-address 10.255.14.177;
        neighbor 10.255.71.24;
    }
}
ospf {
    area 0.0.0.0 {
        interface fe-1/2/0.0;
        interface 10.255.14.177;
    }
}

user@R2# show routing-options
autonomous-system 65000;

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

Purpose

Verify that Device R1 has a route to the 10.1.230.0/23 network.

Action

From operational mode, enter the show route 10.1.230.0 extensive command.

user@R1> show route 10.1.230.0 extensive
inet.0: 11 destinations, 13 routes (11 active, 0 holddown, 0 hidden)
Restart Complete
10.1.230.0/23 (2 entries, 1 announced)
TSI:
KRT in-kernel 10.1.230.0/23 -> {indirect(262142)}
Page 0 idx 1 Type 1 val 9168f6c
    Nexthop: 10.1.10.10
    Localpref: 100
    AS path: [65000] 65500 I
    Communities:
Path 10.1.230.0 from 10.1.0.1 Vector len 4.  Val: 1
        *BGP    Preference: 170/-101
                Next hop type: Indirect
                Address: 0x90c44d8
                Next-hop reference count: 4
                Source: 10.1.0.1
                Next hop type: Router, Next hop index: 262143
                Next hop: 10.1.0.1 via fe-1/2/0.0, selected
                Next hop: 10.1.1.1 via fe-1/2/2.0
                Protocol next hop: 10.1.10.10
                Indirect next hop: 91c0000 262142
                State: <Active Ext>
                Local AS: 65000 Peer AS: 65500
                Age: 2:55:31    Metric2: 0 
                Task: BGP_65500.10.1.0.1+64631
                Announcement bits (3): 2-KRT 3-BGP_RT_Background 4-Resolve tree 1 
                AS path: 65500 I
                Accepted Multipath
                Localpref: 100
                Router ID: 10.255.14.179
                Indirect next hops: 1
                        Protocol next hop: 10.1.10.10
                        Indirect next hop: 91c0000 262142
                        Indirect path forwarding next hops: 2
                                Next hop type: Router
                                Next hop: 10.1.0.1 via fe-1/2/0.0
                                Next hop: 10.1.1.1 via fe-1/2/2.0
                        10.1.10.10/32 Originating RIB: inet.0
                          Node path count: 1
                          Forwarding nexthops: 2
                                Nexthop: 10.1.0.1 via fe-1/2/0.0
                                Nexthop: 10.1.1.1 via fe-1/2/2.0
         BGP    Preference: 170/-101
                Next hop type: Indirect
                Address: 0x90c44d8
                Next-hop reference count: 4
                Source: 10.1.1.1
                Next hop type: Router, Next hop index: 262143
                Next hop: 10.1.0.1 via fe-1/2/0.0, selected
                Next hop: 10.1.1.1 via fe-1/2/2.0
                Protocol next hop: 10.1.10.10
                Indirect next hop: 91c0000 262142
                State: <NotBest Ext>
                Inactive reason: Not Best in its group - Update source
                Local AS: 65000 Peer AS: 65500
                Age: 2:55:27    Metric2: 0 
                Task: BGP_65500.10.1.1.1+53260
                AS path: 65500 I
                Accepted
                Localpref: 100
                Router ID: 10.255.14.179
                Indirect next hops: 1
                        Protocol next hop: 10.1.10.10
                        Indirect next hop: 91c0000 262142
                        Indirect path forwarding next hops: 2
                                Next hop type: Router
                                Next hop: 10.1.0.1 via fe-1/2/0.0
                                Next hop: 10.1.1.1 via fe-1/2/2.0
                        10.1.10.10/32 Originating RIB: inet.0
                          Node path count: 1
                          Forwarding nexthops: 2
                                Nexthop: 10.1.0.1 via fe-1/2/0.0
                                Nexthop: 10.1.1.1 via fe-1/2/2.0

Meaning

The output shows that Device R1 has a route to the 10.1.230.0 network with the multipath feature enabled (Accepted Multipath). The output also shows that the route has an indirect next hop of 10.1.10.10.

Purpose

Make sure that the multipath route with the indirect next hop is removed from the routing table when you deactivate the accept-remote-nexthop statement.

Action

1. From configuration mode, enter the deactivate protocols bgp accept-remote-nexthop command.

   content_copy zoom_out_map

   user@R1# deactivate protocols bgp accept-remote-nexthop
   user@R1# commit

2. From operational mode, enter the show route 10.1.230.0 command.

   content_copy zoom_out_map

   user@R1> show route 10.1.230.0 

3. From configuration mode, reactivate the statement by entering the activate protocols bgp accept-remote-nexthop command.

   content_copy zoom_out_map

   user@R1# activate protocols bgp accept-remote-nexthop
   user@R1# commit

4. From operational mode, reenter the show route 10.1.230.0 command.

   content_copy zoom_out_map

   user@R1> show route 10.1.230.0 
   
   inet.0: 11 destinations, 13 routes (11 active, 0 holddown, 0 hidden)
   Restart Complete
   + = Active Route, - = Last Active, * = Both
   
   10.1.230.0/23       *[BGP/170] 03:13:19, localpref 100
                         AS path: 65500 I
                       > to 10.1.0.1 via fe-1/2/0.0
                         to 10.1.1.1 via fe-1/2/2.0
                       [BGP/170] 03:13:15, localpref 100, from 10.1.1.1
                         AS path: 65500 I
                       > to 10.1.0.1 via fe-1/2/0.0
                         to 10.1.1.1 via fe-1/2/2.0

Meaning

When the accept-remote-nexthop statement is deactivated, the multipath route to the 10.1.230.0 network is removed from the routing table .

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.

Device R1

set interfaces ge-1/2/0 unit 0 description R1->R3
set interfaces ge-1/2/0 unit 0 family inet address 10.0.0.1/30
set interfaces ge-1/2/1 unit 0 description R1->R2
set interfaces ge-1/2/1 unit 0 family inet address 10.0.1.2/30
set interfaces lo0 unit 0 family inet address 192.168.0.1/32
set protocols bgp group external type external
set protocols bgp group external import bw-dis
set protocols bgp group external peer-as 64501
set protocols bgp group external multipath
set protocols bgp group external neighbor 10.0.1.1
set protocols bgp group external neighbor 10.0.0.2
set policy-options policy-statement bw-dis term a from protocol bgp
set policy-options policy-statement bw-dis term a from neighbor 10.0.1.1
set policy-options policy-statement bw-dis term a then community add bw-high
set policy-options policy-statement bw-dis term a then accept
set policy-options policy-statement bw-dis term b from protocol bgp
set policy-options policy-statement bw-dis term b from neighbor 10.0.0.2
set policy-options policy-statement bw-dis term b then community add bw-low
set policy-options policy-statement bw-dis term b then accept
set policy-options policy-statement loadbal from route-filter 10.0.0.0/16 orlonger
set policy-options policy-statement loadbal then load-balance per-packet
set policy-options community bw-high members bandwidth:65000:60000000
set policy-options community bw-low members bandwidth:65000:40000000
set routing-options autonomous-system 64500
set routing-options forwarding-table export loadbal

Device R2

set interfaces ge-1/2/0 unit 0 description R2->R1
set interfaces ge-1/2/0 unit 0 family inet address 10.0.1.1/30
set interfaces ge-1/2/1 unit 0 description R2->R3
set interfaces ge-1/2/1 unit 0 family inet address 10.0.2.2/30
set interfaces ge-1/2/1 unit 0 family iso
set interfaces lo0 unit 0 family inet address 192.168.0.2/32
set interfaces lo0 unit 0 family iso address 49.0001.1921.6800.0002.00
set protocols bgp group external type external
set protocols bgp group external export bgp-default
set protocols bgp group external export send-direct
set protocols bgp group external peer-as 64500
set protocols bgp group external multipath
set protocols bgp group external neighbor 10.0.1.2
set protocols isis interface ge-1/2/1.0
set protocols isis interface lo0.0
set policy-options policy-statement bgp-default from protocol static
set policy-options policy-statement bgp-default from route-filter 172.16.0.0/16 exact
set policy-options policy-statement bgp-default then accept
set policy-options policy-statement send-direct term 1 from protocol direct
set policy-options policy-statement send-direct term 1 then accept
set routing-options static route 172.16.0.0/16 discard
set routing-options static route 172.16.0.0/16 no-install
set routing-options autonomous-system 64501

Device R3

set interfaces ge-1/2/0 unit 0 description R3->R2
set interfaces ge-1/2/0 unit 0 family inet address 10.0.2.1/30
set interfaces ge-1/2/0 unit 0 family iso
set interfaces ge-1/2/1 unit 0 description R3->R1
set interfaces ge-1/2/1 unit 0 family inet address 10.0.0.2/30
set interfaces lo0 unit 0 family inet address 192.168.0.3/32
set interfaces lo0 unit 0 family iso address 49.0001.1921.6800.0003.00
set protocols bgp group external type external
set protocols bgp group external export send-direct
set protocols bgp group external export bgp-default
set protocols bgp group external peer-as 64500
set protocols bgp group external multipath
set protocols bgp group external neighbor 10.0.0.1
set protocols isis interface ge-1/2/0.0
set protocols isis interface lo0.0
set policy-options policy-statement bgp-default from protocol static
set policy-options policy-statement bgp-default from route-filter 172.16.0.0/16 exact
set policy-options policy-statement bgp-default then accept
set policy-options policy-statement send-direct term 1 from protocol direct
set policy-options policy-statement send-direct term 1 then accept
set routing-options static route 172.16.0.0/16 discard
set routing-options static route 172.16.0.0/16 no-install
set routing-options autonomous-system 64501

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 Junos OS CLI User Guide.

To configure the BGP peer sessions:

1. Configure the interfaces.

   content_copy zoom_out_map

   user@R1# set ge-1/2/0 unit 0 description R1->R3
   user@R1# set ge-1/2/0 unit 0 family inet address 10.0.0.1/30
   user@R1# set ge-1/2/1 unit 0 description R1->R2
   user@R1# set ge-1/2/1 unit 0 family inet address 10.0.1.2/30
   user@R1# set lo0 unit 0 family inet address 192.168.0.1/32
   

2. Configure the BGP group.

   content_copy zoom_out_map

   [edit protocols bgp group external]
   user@R1# set type external
   user@R1# set import bw-dis
   user@R1# set peer-as 64501
   user@R1# set neighbor 10.0.1.1
   user@R1# set neighbor 10.0.0.2
   

3. Enable the BGP group to use multiple paths.

   Note:

   To disable the default check requiring that paths accepted by BGP multipath must have the same neighboring autonomous system (AS), include the multiple-as option. Use the multiple-as option if the neighbors are in different ASs.

   content_copy zoom_out_map

   [edit protocols bgp group external]
   user@R1# set multipath
   

4. Configure the load-balancing policy.

   content_copy zoom_out_map

   [edit policy-options policy-statement loadbal]
   user@R1# set from route-filter 10.0.0.0/16 orlonger 
   user@R1# set then load-balance per-packet 
   

5. Apply the load-balancing policy.

   content_copy zoom_out_map

   [edit routing-options]
   user@R1# set forwarding-table export loadbal
   

6. Configure the BGP community members.

   This example assumes a bandwidth of 1 Gbps and allocates 60 percent to bw-high and 40 percent to bw-low. The reference bandwidth does not need to be the same as the link bandwidth.

   content_copy zoom_out_map

   [edit policy-options]
   user@R1# set community bw-high members bandwidth:65000:60000000
   user@R1# set community bw-low members bandwidth:65000:40000000
   

7. Configure the bandwidth distribution policy.

   content_copy zoom_out_map

   [edit policy-options bw-dis]
   user@R1# set term a from protocol bgp
   user@R1# set term a from neighbor 10.0.1.1
   user@R1# set term a then community add bw-high
   user@R1# set term a then accept
   user@R1# set term b from protocol bgp
   user@R1# set term b from neighbor 10.0.0.2
   user@R1# set term b then community add bw-low
   user@R1# set term b then accept
   

8. Configure the local autonomous system (AS) number.

   content_copy zoom_out_map

   [edit routing-options]
   user@R1# set autonomous-system 64500
   

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.

user@R1# show interfaces
ge-1/2/0 {
    unit 0 {
        description R1->R3;
        family inet {
            address 10.0.0.1/30;
        }
    }
}
ge-1/2/1 {
    unit 0 {
        description R1->R2;
        family inet {
            address 10.0.1.2/30;
        }
    }
}
lo0 {
    unit 0 {
        family inet {
            address 192.168.0.1/32;
        }
    }
}

user@R1# show protocols
bgp {
    group external {
        type external;
        import bw-dis;
        peer-as 64501;
        multipath;
        neighbor 10.0.1.1;
        neighbor 10.0.0.2;
    }
}

user@R1# show policy-options
policy-statement bw-dis {
    term a {
        from {
            protocol bgp;
            neighbor 10.0.1.1;
        }
        then {
            community add bw-high;
            accept;
        }
    }
    term b {
        from {
            protocol bgp;
            neighbor 10.0.0.2;
        }
        then {
            community add bw-low;
            accept;
        }
    }
}
policy-statement loadbal {
    from {
        route-filter 10.0.0.0/16 orlonger;
    }
    then {
        load-balance per-packet;
    }
}
community bw-high members bandwidth:65000:60000000;
community bw-low members bandwidth:65000:40000000;

user@R1# show routing-options
autonomous-system 64500;
forwarding-table {
    export loadbal;
}

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

Purpose

Verify that both routes are selected and that the next hops on the routes show a 60%/40% balance.

Action

From operational mode, run the show route protocol bgp detail command.

user@R1> show route 172.16/16 protocol bgp detail
inet.0: 9 destinations, 13 routes (9 active, 0 holddown, 0 hidden)
172.16.0.0/16 (2 entries, 1 announced)
        *BGP    Preference: 170/-101
                Next hop type: Router, Next hop index: 262143
                Address: 0x93fc078
                Next-hop reference count: 3
                Source: 10.0.0.2
                Next hop: 10.0.0.2 via ge-1/2/0.0 balance 40%
                Next hop: 10.0.1.1 via ge-1/2/1.0 balance 60%, selected
                State: **Active Ext>
                Local AS: 64500 Peer AS: 64501
                Age: 3:22:55 
                Task: BGP_64501.10.0.0.2+55344
                Announcement bits (1): 0-KRT 
                AS path: 64501 I
                Communities: bandwidth:65000:40000000
                Accepted Multipath
                Localpref: 100
                Router ID: 192.168.0.3
         BGP    Preference: 170/-101
                Next hop type: Router, Next hop index: 658
                Address: 0x9260520
                Next-hop reference count: 4
                Source: 10.0.1.1
                Next hop: 10.0.1.1 via ge-1/2/1.0, selected
                State: <NotBest Ext>
                Inactive reason: Not Best in its group - Active preferred
                Local AS: 64500 Peer AS: 64501
                Age: 3:22:55 
                Task: BGP_65001.10.0.1.1+62586
                AS path: 64501 I
                Communities: bandwidth:65000:60000000
                Accepted MultipathContrib
                Localpref: 100
                Router ID: 192.168.0.2

user@R1> show route 10.0.2.0 protocol bgp detail
inet.0: 9 destinations, 13 routes (9 active, 0 holddown, 0 hidden)
10.0.2.0/30 (2 entries, 1 announced)
        *BGP    Preference: 170/-101
                Next hop type: Router, Next hop index: 262143
                Address: 0x93fc078
                Next-hop reference count: 3
                Source: 10.0.1.1
                Next hop: 10.0.0.2 via ge-1/2/0.0 balance 40%
                Next hop: 10.0.1.1 via ge-1/2/1.0 balance 60%, selected
                State: <Active Ext>
                Local AS: 64500 Peer AS: 64501
                Age: 3:36:37 
                Task: BGP_65001.10.0.1.1+62586
                Announcement bits (1): 0-KRT 
                AS path: 64501 I
                Communities: bandwidth:65000:60000000
                Accepted Multipath
                Localpref: 100
                Router ID: 192.168.0.2
         BGP    Preference: 170/-101
                Next hop type: Router, Next hop index: 657
                Address: 0x92604d8
                Next-hop reference count: 4
                Source: 10.0.0.2
                Next hop: 10.0.0.2 via ge-1/2/0.0, selected
                State: <NotBest Ext>
                Inactive reason: Not Best in its group - Active preferred
                Local AS: 64500 Peer AS: 65001
                Age: 3:36:36 
                Task: BGP_65001.10.0.0.2+55344
                AS path: 64501 I
                Communities: bandwidth:65000:40000000
                Accepted MultipathContrib
                Localpref: 100
                Router ID: 192.168.0.3

Meaning

The active path, denoted with an asterisk (*), has two next hops: 10.0.1.1 and 10.0.0.2 to the 172.16/16 destination.

Likewise, the active path, denoted with an asterisk (*), has two next hops: 10.0.1.1 and 10.0.0.2 to the 10.0.2.0 destination.

In both cases, the 10.0.1.1 next hop is copied from the inactive path to the active path.

The balance of 40 percent and 60 percent is shown in the show route output. This indicates that traffic is being distributed between two next hops and that 60 percent of the traffic is following the first path, while 40 percent is following the second path.

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 a policy to advertise an aggregated bandwidth to BGP peers (starting with Router R1):

1. Configure the interfaces with IPv4 addresses.

   content_copy zoom_out_map

   [edit interfaces]
   user@R1# set ge-0/0/0 unit 0 description R1->R3
   user@R1# set ge-0/0/0 unit 0 family inet address 10.0.0.1/30
   user@R1# set ge-0/0/1 unit 0 description R1->R2
   user@R1# set ge-0/0/1 unit 0 family inet address 10.0.1.2/30
   user@R1# set ge-0/0/2 unit 0 description R1->R4
   user@R1# set ge-0/0/2 unit 0 family inet address 10.0.4.1/30
   

2. Configure the loopback address.

   content_copy zoom_out_map

   [edit interfaces]
   user@R1# set lo0 unit 0 family inet address 192.168.0.1/32
   

3. Configure the autonomous system for BGP hosts.

   content_copy zoom_out_map

   [edit routing-options]
   user@R1# set autonomous-system 65000
   

4. Configure EBGP on the external edge routers.

   content_copy zoom_out_map

   [edit protocols]
   user@R1# set bgp group external type external
   user@R1# set bgp group external import bw-dis
   user@R1# set bgp group external peer-as 65001
   user@R1# set bgp group external multipath
   user@R1# set bgp group external neighbor 10.0.1.1
   user@R1# set bgp group external neighbor 10.0.0.2
   user@R1# set bgp group external2 type external
   user@R1# set bgp group external2 peer-as 65002
   

5. Define a bandwidth distribution policy to assign a high bandwidth community to traffic destined to Router R3.

   content_copy zoom_out_map

   [edit policy-options]
   user@R1# set policy-statement bw-dis term a from protocol bgp
   user@R1# set policy-statement bw-dis term a from neighbor 10.0.1.1
   user@R1# set policy-statement bw-dis term a then community add bw-high
   user@R1# set policy-statement bw-dis term a then accept
   

6. Define a bandwidth distribution policy to assign a low bandwidth community to traffic destined to Router R2.

   content_copy zoom_out_map

   [edit policy-options]
   user@R1# set policy-statement bw-dis term b from protocol bgp
   user@R1# set policy-statement bw-dis term b from neighbor 10.0.0.2
   user@R1# set policy-statement bw-dis term b then community add bw-low
   user@R1# set policy-statement bw-dis term b then accept
   

7. Enable the feature to advertise aggregated bandwidth of 80,000,000 bytes to EBGP peer Router R4 over BGP sessions.

   content_copy zoom_out_map

   [edit policy-options]
   user@R1# set policy-statement aggregate_bw_and_limit_capacity then aggregate-bandwidth
   user@R1# set policy-statement aggregate_bw_and_limit_capacity then limit-bandwidth 80000000
   user@R1# set policy-statement aggregate_bw_and_limit_capacity then accept
   

8. Apply the aggregate_bw_and limit_capacity policy to EBGP group external2.

   content_copy zoom_out_map

   [edit protocols]
   user@R1# set bgp group external2 neighbor 10.0.4.2 export aggregate_bw_and_limit_capacity
   

9. Define a load balancing policy.

   content_copy zoom_out_map

   [edit policy-options]
   user@R1# set policy-statement loadbal from route-filter 10.0.0.0/16 orlonger
   user@R1# set policy-statement loadbal then load-balance per-packet
   

10. Apply the load balancing policy.

    content_copy zoom_out_map

    [edit routing-options]
    user@R1# set forwarding-table export loadbal
    

11. Configure the BGP community members. The first 16-bit number represents the local autonomous system. The second 32-bit number represents the link bandwidth in bytes per second. Configure a bw-high community with 60 percent of a 1-Gbps link and another community bw-low with 40 percent of a 1-Gbps link.

    Configure 60 percent of a 1-Gbps link to bw-high community and 40 percent to bw-low community.

    content_copy zoom_out_map

    [edit policy-options]
    user@R1# set community bw-high members bandwidth:65000:60000000
    user@R1# set community bw-low members bandwidth:65000:40000000
    

Purpose

To verify that BGP peering is complete and a BGP session is established between the routers,

Action

user@R1> show bgp summary
Groups: 2 Peers: 3 Down peers: 0
Table          Tot Paths  Act Paths Suppressed    History Damp State    Pending
inet.0
                      12          8          0          0          0          0
Peer                     AS      InPkt     OutPkt    OutQ   Flaps Last Up/Dwn State|#Active/Received/Accepted/Damped...
10.0.0.2              65001        153        149       0       0     1:07:23 4/6/6/0            0/0/0/0
10.0.1.1              65001        229        226       0       0     1:41:44 4/6/6/0            0/0/0/0
10.0.4.2              65002       1227       1227       0       0     9:10:27 0/0/0/0            0/0/0/0

Meaning

Router R1 has completed peering with Routers R2, R3, and R4.

Purpose

To verify that the extended community is present for each route path.

Action

From operational mode, run the show route protocol bgp detail command.

user@R1> show route 10.0.2.0 protocol bgp detail
inet.0: 20 destinations, 26 routes (20 active, 0 holddown, 0 hidden)
10.0.2.0/30 (2 entries, 1 announced)
        *BGP    Preference: 170/-101
                Next hop type: Router, Next hop index: 0
                Address: 0xb618990
                Next-hop reference count: 3
                Source: 10.0.1.1
                Next hop: 10.0.0.2 via ge-0/0/0.0 balance 40%
                Session Id: 0x0
                Next hop: 10.0.1.1 via ge-0/0/1.0 balance 60%, selected
                Session Id: 0x0
                State: <Active Ext> 
                Local AS: 65000 Peer AS: 65001 
                Age: 20:33 
                Validation State: unverified 
                Task: BGP_65001.10.0.1.1 
                Announcement bits (3): 0-KRT 2-BGP_Listen.0.0.0.0+179 3-BGP_RT_Background 
                AS path: 65001 I 
                Communities: bandwidth:65000:60000000 
                Accepted Multipath 
                Localpref: 100 
                Router ID: 128.49.121.137 
         BGP    Preference: 170/-101 
                Next hop type: Router, Next hop index: 595 
                Address: 0xb7a1330 
                Next-hop reference count: 9 
                Source: 10.0.0.2 
                Next hop: 10.0.0.2 via ge-0/0/0.0, selected 
                Session Id: 0x141
                State: <NotBest Ext> 
                Inactive reason: Not Best in its group - Active preferred 
                Local AS: 65000 Peer AS: 65001 
                Age: 20:33 
                Validation State: unverified 
                Task: BGP_65001.10.0.0.2 
                AS path: 65001 I 
                Communities: bandwidth:65000:40000000 
                Accepted MultipathContrib 
                Localpref: 100 
                Router ID: 128.49.121.132 

Meaning

Purpose

To verify that Router R1 is advertising the aggregate bandwidth to its external neighbors.

Action

user@R1> show route advertising-protocol bgp 10.0.4.2 10.0.2.0/30 detail 
inet.0: 20 destinations, 26 routes (20 active, 0 holddown, 0 hidden)
* 10.0.2.0/30 (2 entries, 1 announced)
 BGP group external2 type External
     Nexthop: Self
     AS path: [65000] 65001 I
     Communities: bandwidth:65000:80000000

Meaning

Router R1 is advertising the aggregated bandwidth of 80,000,000 bytes to its neighbors.

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 Junos OS CLI User Guide.

To configure Router R1:

1. Configure the interfaces to Router R2, Router R3, Router R4, and Router R5, and configure the loopback (lo0) interface.

   content_copy zoom_out_map

   [edit interfaces]
   user@R1# set fe-0/0/0 unit 12 family inet address 10.0.12.1/24
   user@R1# set fe-0/0/1 unit 13 family inet address 10.0.13.1/24
   user@R1# set fe-1/0/0 unit 14 family inet address 10.0.14.1/24
   user@R1# set fe-1/2/0 unit 15 family inet address 10.0.15.1/24
   user@R1#set lo0 unit 10 family inet address 10.0.0.10/32
   

2. Configure BGP on the interfaces, and configure IBGP route reflection.

   content_copy zoom_out_map

   [edit protocols bgp]
   user@R1# set group rr type internal
   user@R1# set group rr local-address 10.0.0.10
   user@R1# set group rr cluster 10.0.0.10
   user@R1# set group rr neighbor 10.0.0.20
   user@R1# set group rr neighbor 10.0.0.30
   user@R1# set group rr_rr type internal
   user@R1# set group rr_rr local-address 10.0.0.10
   user@R1# set group e1 type external
   user@R1# set group e1 neighbor 10.0.15.2 local-address 10.0.15.1
   user@R1# set group e1 neighbor 10.0.15.2 peer-as 2
   

3. Configure Router R1 to send up to six paths to its neighbor, Router R4.

   The destination of the paths can be any destination that Router R1 can reach through multiple paths.

   content_copy zoom_out_map

   [edit protocols bgp]
   user@R1# set group rr_rr neighbor 10.0.0.40 family inet unicast add-path send path-count 6
   

4. Configure OSPF on the interfaces.

   content_copy zoom_out_map

   [edit protocols ospf]
   user@R1# set area 0.0.0.0 interface lo0.10 passive
   user@R1# set area 0.0.0.0 interface fe-0/0/0.12
   user@R1# set area 0.0.0.0 interface fe-0/0/1.13
   user@R1# set area 0.0.0.0 interface fe-1/0/0.14
   user@R1# set area 0.0.0.0 interface fe-1/2/0.15
   

5. Configure the router ID and the autonomous system number.

   content_copy zoom_out_map

   [edit routing-options]
   user@R1# set router-id 10.0.0.10
   user@R1# set autonomous-system 1
   

6. If you are done configuring the device, commit the configuration.

   content_copy zoom_out_map

   user@R1# commit
   

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.

user@R1# show interfaces
fe-0/0/0 {
    unit 12 {
        family inet {
            address 10.0.12.1/24;
        }
    }
}
fe-0/0/1 {
    unit 13 {
        family inet {
            address 10.0.13.1/24;
        }
    }
}
fe-1/0/0 {
    unit 14 {
        family inet {
            address 10.0.14.1/24;
        }
    }
}
fe-1/2/0 {
    unit 15 {
        family inet {
            address 10.0.15.1/24;
        }
    }
}
lo0 {
    unit 10 {
        family inet {
            address 10.0.0.10/32;
        }
    }
}

user@R1# show protocols
bgp {
    group rr {
        type internal;
        local-address 10.0.0.10;
        cluster 10.0.0.10;
        neighbor 10.0.0.20;
        neighbor 10.0.0.30;
    }
    group e1 {
        type external;
        neighbor 10.0.15.2 {
            local-address 10.0.15.1;
            peer-as 2;
        }
    }
    group rr_rr {
        type internal;
        local-address 10.0.0.10;
        neighbor 10.0.0.40 {
            family inet {
                unicast {
                    add-path {
                        send {
                            path-count 6;
                        }
                    }
                }
            }
        }
    }
}
ospf {
    area 0.0.0.0 {
        interface lo0.10 {
            passive;
        }
        interface fe-0/0/0.12;
        interface fe-0/0/1.13;
        interface fe-1/0/0.14;
        interface fe-1/2/0.15;
    }
}

user@R1# show routing-options
router-id 10.0.0.10;
 autonomous-system 1;

Step-by-Step Procedure

To configure Router R2:

1. Configure the loopback (lo0) interface and the interfaces to Router R6 and Router R1.

   content_copy zoom_out_map

   [edit interfaces]
   user@R2# set fe-1/2/0 unit 21 family inet address 10.0.12.2/24
   user@R2# set fe-1/2/1 unit 26 family inet address 10.0.26.1/24
   user@R2# set lo0 unit 20 family inet address 10.0.0.20/32
   

2. Configure BGP and OSPF on Router R2’s interfaces.

   content_copy zoom_out_map

   [edit protocols]
   user@R2# set bgp group rr type internal
   user@R2# set bgp group rr local-address 10.0.0.20
   user@R2# set bgp group e1 type external
   user@R2# set bgp group e1 neighbor 10.0.26.2 peer-as 2
   user@R2# set ospf area 0.0.0.0 interface lo0.20 passive
   user@R2# set ospf area 0.0.0.0 interface fe-1/2/0.21
   user@R2# set ospf area 0.0.0.0 interface fe-1/2/1.28
   

3. For routes sent from Router R2 to Router R1, advertise Router R2 as the next hop, because Router R1 does not have a route to Router R6’s address on the 10.0.26.0/24 network.

   content_copy zoom_out_map

   [edit]
   user@R2# set policy-options policy-statement set_nh_self then next-hop self
   user@R2# set protocols bgp group rr neighbor 10.0.0.10 export set_nh_self
   

4. Configure the autonomous system number.

   content_copy zoom_out_map

   [edit]
   user@R2# set routing-options autonomous-system 1
   

5. If you are done configuring the device, commit the configuration.

   content_copy zoom_out_map

   user@R2# commit
   

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.

user@R2# show interfaces
fe-1/2/0 {
    unit 21 {
        family inet {
            address 10.0.12.2/24;
        }
    }
}
fe-1/2/1 {
    unit 26 {
        family inet {
            address 10.0.26.1/24;
        }
    }
}
lo0 {
    unit 20 {
        family inet {
            address 10.0.0.20/32;
        }
    }
}

user@R2# show protocols
bgp {
    group rr {
        type internal;
        local-address 10.0.0.20;
        neighbor 10.0.0.10 {
            export set_nh_self;
        }
    }
    group e1 {
        type external;
        neighbor 10.0.26.2 {
            peer-as 2;
        }
    }
}
ospf {
    area 0.0.0.0 {
        interface lo0.20 {
            passive;
        }
        interface fe-1/2/0.21;
        interface fe-1/2/1.28;
    }
}

user@R2# show policy-options
policy-statement set_nh_self {
    then {
        next-hop self;
    }
}

user@R2# show routing-options
 autonomous-system 1;

Step-by-Step Procedure

To configure Router R3:

1. Configure the loopback (lo0) interface and the interfaces to Router R7 and Router R1.

   content_copy zoom_out_map

   [edit interfaces]
   user@R3# set fe-1/0/1 unit 31 family inet address 10.0.13.2/24
   user@R3# set fe-1/0/2 unit 37 family inet address 10.0.37.1/24
   user@R3# set lo0 unit 30 family inet address 10.0.0.30/32
   

2. Configure BGP and OSPF on Router R3’s interfaces.

   content_copy zoom_out_map

   [edit protocols]
   user@R3# set bgp group rr type internal
   user@R3# set bgp group rr local-address 10.0.0.30
   user@R3# set bgp group e1 type external
   user@R3# set bgp group e1 neighbor 10.0.37.2 peer-as 2
   user@R3# set ospf area 0.0.0.0 interface lo0.30 passive
   user@R3# set ospf area 0.0.0.0 interface fe-1/0/1.31
   user@R3# set ospf area 0.0.0.0 interface fe-1/0/2.37
   

3. For routes sent from Router R3 to Router R1, advertise Router R3 as the next hop, because Router R1 does not have a route to Router R7’s address on the 10.0.37.0/24 network.

   content_copy zoom_out_map

   [edit]
   user@R3# set policy-options policy-statement set_nh_self then next-hop self
   user@R3# set protocols bgp group rr neighbor 10.0.0.10 export set_nh_self
   

4. Configure the autonomous system number.

   content_copy zoom_out_map

   [edit]
   user@R3# set routing-options autonomous-system 1
   

5. If you are done configuring the device, commit the configuration.

   content_copy zoom_out_map

   user@R3# commit
   

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.

user@R3# show interfaces
fe-1/0/1 {
    unit 31 {
        family inet {
            address 10.0.13.2/24;
        }
    }
}
fe-1/0/2 {
    unit 37 {
        family inet {
            address 10.0.37.1/24;
        }
    }
}
lo0 {
    unit 30 {
        family inet {
            address 10.0.0.30/32;
        }
    }
}

user@R3# show protocols
bgp {
    group rr {
        type internal;
        local-address 10.0.0.30;
        neighbor 10.0.0.10 {
            export set_nh_self;
        }
    }
    group e1 {
        type external;
        neighbor 10.0.37.2 {
            peer-as 2;
        }
    }
}
ospf {
    area 0.0.0.0 {
        interface lo0.30 {
            passive;
        }
        interface fe-1/0/1.31;
        interface fe-1/0/2.37;
    }
}
user@R3# show policy-options
policy-statement set_nh_self {
    then {
        next-hop self;
    }
}

user@R3# show routing-options
 autonomous-system 1;

Step-by-Step Procedure

To configure Router R4:

1. Configure the interfaces to Router R1 and Router R8, and configure the loopback (lo0) interface.

   content_copy zoom_out_map

   [edit interfaces]
   user@R4# set fe-1/2/0 unit 41 family inet address 10.0.14.2/24
   user@R4# set fe-1/2/1 unit 48 family inet address 10.0.48.1/24
   user@R4# set lo0 unit 40 family inet address 10.0.0.40/32
   

2. Configure BGP on the interfaces, and configure IBGP route reflection.

   content_copy zoom_out_map

   [edit protocols bgp]
   user@R4# set group rr type internal
   user@R4# set group rr local-address 10.0.0.40
   user@R4# set group rr neighbor 10.0.0.10
   user@R4# set group rr_client type internal
   user@R4# set group rr_client local-address 10.0.0.40
   user@R4# set group rr_client cluster 10.0.0.40
   

3. Configure Router R4 to send up to six paths to its neighbor, Router R8.

   The destination of the paths can be any destination that Router R4 can reach through multiple paths.

   content_copy zoom_out_map

   [edit protocols bgp]
   user@R4# set group rr_client neighbor 10.0.0.80 family inet unicast add-path send path-count 6
   

4. Configure Router R4 to receive multiple paths from its neighbor, Router R1.

   The destination of the paths can be any destination that Router R1 can reach through multiple paths.

   content_copy zoom_out_map

   [edit protocols bgp group rr family inet unicast]
   user@R4# set add-path receive
   

5. Configure OSPF on the interfaces.

   content_copy zoom_out_map

   [edit protocols ospf area 0.0.0.0]
   user@R4# set interface fe-1/2/0.41
   user@R4# set interface lo0.40 passive
   user@R4# set interface fe-1/2/1.48
   

6. Configure a policy that allows Router R4 to send Router R8 multiple paths to the 172.16.199.1/32 route.

   • Router R4 receives multiple paths for the 172.16.198.1/32 route and the 172.16.199.1/32 route. However, because of this policy, Router R4 only sends multiple paths for the 172.16.199.1/32 route.

     content_copy zoom_out_map

     [edit protocols bgp group rr_client neighbor 10.0.0.80 family inet unicast]
     user@R4# set add-path send prefix-policy allow_199 
     [edit policy-options policy-statement allow_199]
     user@R4# set from route-filter 172.16.199.1/32 exact 
     user@R4# set then accept
     

   • Router R4 can also be configured to send up-to 20 BGP add-path routes for a subset of add-path advertised prefixes.

     content_copy zoom_out_map

     [edit policy-options policy-statement allow_199]
     user@R4# set term match_199 from prefix-list match_199
     user@R4# set then add-path send-count 20
     

7. Configure the autonomous system number.

   content_copy zoom_out_map

   [edit routing-options]
   user@R4# set autonomous-system 1
   

8. If you are done configuring the device, commit the configuration.

   content_copy zoom_out_map

   user@R4# commit
   

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.

user@R4# show interfaces
fe-1/2/0 {
    unit 41 {
        family inet {
            address 10.0.14.2/24;
        }
    }
}
fe-1/2/1 {
    unit 48 {
        family inet {
            address 10.0.48.1/24;
        }
    }
}
lo0 {
    unit 40 {
        family inet {
            address 10.0.0.40/32;
        }
    }
}

user@R4# show protocols
bgp {
    group rr {
        type internal;
        local-address 10.0.0.40;
        family inet {
            unicast {
                add-path {
                    receive;
                }
            }
        }
        neighbor 10.0.0.10;
    }
    group rr_client {
        type internal;
        local-address 10.0.0.40;
        cluster 10.0.0.40;
        neighbor 10.0.0.80 {
            family inet {
                unicast {
                    add-path {
                        send {
                            path-count 6;
                            prefix-policy allow_199;
                        }
                    }
                }
            }
        }
    }
}
ospf {
    area 0.0.0.0 {
        interface lo0.40 {
            passive;
        }
        interface fe-1/2/0.41;
        interface fe-1/2/1.48;
    }
}

user@R4# show policy-options
policy-statement allow_199 {
    from {
        route-filter 172.16.199.1/32 exact;
    }
    from term match_199 {
        prefix-list match_199;
    }
        then add-path send-count 20;
    then accept;
}

user@R4# show routing-options
 autonomous-system 1;

Step-by-Step Procedure

To configure Router R5:

1. Configure the loopback (lo0) interface and the interface to Router R1.

   content_copy zoom_out_map

   [edit interfaces]
   user@R5# set fe-1/2/0 unit 51 family inet address 10.0.15.2/24
   user@R5# set lo0 unit 50 family inet address 10.0.0.50/32
   

2. Configure BGP on Router R5’s interface.

   content_copy zoom_out_map

   [edit protocols bgp group e1]
   user@R5# set type external
   user@R5# set neighbor 10.0.15.1 peer-as 1
   

3. Create static routes for redistribution into BGP.

   content_copy zoom_out_map

   [edit routing-options]
   user@R5# set static route 172.16.199.1/32 reject
   user@R5# set static route 172.16.198.1/32 reject
   

4. Redistribute static and direct routes into BGP.

   content_copy zoom_out_map

   [edit protocols bgp group e1 neighbor 10.0.15.1]
   user@R5# set export s2b
   [edit policy-options policy-statement s2b]
   user@R5# set from protocol static
   user@R5# set from protocol direct
   user@R5# set then as-path-expand 2
   user@R5# set then accept
   

5. Configure the autonomous system number.

   content_copy zoom_out_map

   [edit routing-options]
   user@R5# set autonomous-system 2
   

6. If you are done configuring the device, commit the configuration.

   content_copy zoom_out_map

   user@R5# commit
   

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.

user@R5# show interfaces
fe-1/2/0 {
    unit 51 {
        
        family inet {
            address 10.0.15.2/24;
        }
    }
}
lo0 {
    unit 50 {
        family inet {
            address 10.0.0.50/32;
        }
    }
}

user@R5# show protocols
bgp {
    group e1 {
        type external;
        neighbor 10.0.15.1 {
            export s2b;
            peer-as 1;
        }
    }
}

user@R5# show policy-options
policy-statement s2b {
    from protocol [ static direct ];
    then {
        as-path-expand 2;
        accept;
    }
}

user@R5# show routing-options
static {
    route 172.16.198.1/32 reject;
    route 172.16.199.1/32 reject;
}
 autonomous-system 2;

Step-by-Step Procedure

To configure Router R6:

1. Configure the loopback (lo0) interface and the interface to Router R2.

   content_copy zoom_out_map

   [edit interfaces]
   user@R6# set fe-1/2/0 unit 62 family inet address 10.0.26.2/24
   user@R6# set lo0 unit 60 family inet address 10.0.0.60/32
   

2. Configure BGP on Router R6’s interface.

   content_copy zoom_out_map

   [edit protocols]
   user@R6# set bgp group e1 type external
   user@R6# set bgp group e1 neighbor 10.0.26.1 peer-as 1
   

3. Create static routes for redistribution into BGP.

   content_copy zoom_out_map

   [edit]
   user@R6# set routing-options static route 172.16.199.1/32 reject
   user@R6# set routing-options static route 172.16.198.1/32 reject
   

4. Redistribute static and direct routes from Router R6’s routing table into BGP.

   content_copy zoom_out_map

   [edit protocols bgp group e1 neighbor 10.0.26.1]
   user@R6# set export s2b
   [edit policy-options policy-statement s2b]
   user@R6# set from protocol static
   user@R6# set from protocol direct
   user@R6# set then accept
   

5. Configure the autonomous system number.

   content_copy zoom_out_map

   [edit routing-options]
   user@R6# set autonomous-system 2
   

6. If you are done configuring the device, commit the configuration.

   content_copy zoom_out_map

   user@R6# commit
   

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.

user@R6# show interfaces
fe-1/2/0 {
    unit 62 {
        
        family inet {
            address 10.0.26.2/24;
        }
    }
}
lo0 {
    unit 60 {
        family inet {
            address 10.0.0.60/32;
        }
    }
}

user@R6# show protocols
bgp {
    group e1 {
        type external;
        neighbor 10.0.26.1 {
            export s2b;
            peer-as 1;
        }
    }
}

user@R6# show policy-options
policy-statement s2b {
    from protocol [ static direct ];
    then accept;
}

user@R6# show routing-options
static {
    route 172.16.198.1/32 reject;
    route 172.16.199.1/32 reject;
}
 autonomous-system 2;

Step-by-Step Procedure

To configure Router R7:

1. Configure the loopback (lo0) interface and the interface to Router R3.

   content_copy zoom_out_map

   [edit interfaces]
   user@R7# set fe-1/2/0 unit 73 family inet address 10.0.37.2/24
   user@R7# set lo0 unit 70 family inet address 10.0.0.70/32
   

2. Configure BGP on Router R7’s interface.

   content_copy zoom_out_map

   [edit protocols bgp group e1]
   user@R7# set type external
   user@R7# set neighbor 10.0.37.1 peer-as 1
   

3. Create a static route for redistribution into BGP.

   content_copy zoom_out_map

   [edit]
   user@R7# set routing-options static route 172.16.199.1/32 reject
   

4. Redistribute static and direct routes from Router R7’s routing table into BGP.

   content_copy zoom_out_map

   [edit protocols bgp group e1 neighbor 10.0.37.1]
   user@R7# set export s2b
   [edit policy-options policy-statement s2b]
   user@R7# set from protocol static
   user@R7# set from protocol direct
   user@R7# set then accept
   

5. Configure the autonomous system number.

   content_copy zoom_out_map

   [edit routing-options]
   user@R7# set autonomous-system 2
   

6. If you are done configuring the device, commit the configuration.

   content_copy zoom_out_map

   user@R7# commit
   

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.

user@R7# show interfaces
fe-1/2/0 {
    unit 73 {
        
        family inet {
            address 10.0.37.2/24;
        }
    }
}
lo0 {
    unit 70 {
        family inet {
            address 10.0.0.70/32;
        }
    }
}

user@R7# show protocols
bgp {
    group e1 {
        type external;
        neighbor 10.0.37.1 {
            export s2b;
            peer-as 1;
        }
    }
}

user@R7# show policy-options
policy-statement s2b {
    from protocol [ static direct ];
    then accept;
}

user@R7# show routing-options
static {
    route 172.16.199.1/32 reject;
}
 autonomous-system 2;

Step-by-Step Procedure

To configure Router R8:

1. Configure the loopback (lo0) interface and the interface to Router R4.

   content_copy zoom_out_map

   [edit interfaces]
   user@R8# set fe-1/2/0 unit 84 family inet address 10.0.48.2/24
   user@R8# set lo0 unit 80 family inet address 10.0.0.80/32
   

2. Configure BGP and OSPF on Router R8’s interface.

   content_copy zoom_out_map

   [edit protocols]
   user@R8# set bgp group rr type internal
   user@R8# set bgp group rr local-address 10.0.0.80
   user@R8# set ospf area 0.0.0.0 interface lo0.80 passive
   user@R8# set ospf area 0.0.0.0 interface fe-1/2/0.84
   

3. Configure Router R8 to receive multiple paths from its neighbor, Router R4.

   The destination of the paths can be any destination that Router R4 can reach through multiple paths.

   content_copy zoom_out_map

   [edit protocols]
   user@R8# set bgp group rr neighbor 10.0.0.40 family inet unicast add-path receive
   

4. Configure the autonomous system number.

   content_copy zoom_out_map

   [edit]
   user@R8# set routing-options autonomous-system 1
   

5. If you are done configuring the device, commit the configuration.

   content_copy zoom_out_map

   user@R8# commit
   

Purpose

Make sure that one or both of the following strings appear in the output of the show bgp neighbor command:

• NLRI's for which peer can receive multiple paths: inet-unicast

• NLRI's for which peer can send multiple paths: inet-unicast

Action

user@R1> show bgp neighbor 10.0.0.40
Peer: 10.0.0.40+179 AS 1       Local: 10.0.0.10+64227 AS 1    
  Type: Internal    State: Established    Flags: <Sync>
...  NLRI's for which peer can receive multiple paths: inet-unicast
...

user@R4> show bgp neighbor 10.0.0.10
Peer: 10.0.0.10+64227 AS 1     Local: 10.0.0.40+179 AS 1    
  Type: Internal    State: Established    Flags: <Sync>
...
  NLRI's for which peer can send multiple paths: inet-unicast
...

user@R4> show bgp neighbor 10.0.0.80
Peer: 10.0.0.80+55416 AS 1     Local: 10.0.0.40+179 AS 1    
  Type: Internal    State: Established  (route reflector client)Flags: <Sync>
  ,,,
  NLRI's for which peer can receive multiple paths: inet-unicast
  ...

user@R8> show bgp neighbor 10.0.0.40
Peer: 10.0.0.40+179 AS 1       Local: 10.0.0.80+55416 AS 1    
  Type: Internal    State: Established    Flags: <Sync>
  ...
  NLRI's for which peer can send multiple paths: inet-unicast
  ...

Purpose

Make sure that multiple paths to the 172.16.198.1/32 destination and multiple paths to the 172.16.199.1/32 destination are advertised to Router R4.

Action

user@R1> show route advertising-protocol bgp 10.0.0.40
inet.0: 21 destinations, 25 routes (21 active, 0 holddown, 0 hidden)
  Prefix                  Nexthop              MED     Lclpref    AS path
* 10.0.0.50/32            10.0.15.2                    100        2 2 I
* 10.0.0.60/32            10.0.0.20                    100        2 I
* 10.0.0.70/32            10.0.0.30                    100        2 I
* 172.16.198.1/32            10.0.0.20                    100        2 I
                          10.0.15.2                    100        2 2 I
* 172.16.199.1/32            10.0.0.20                    100        2 I
                          10.0.0.30                    100        2 I
                          10.0.15.2                    100        2 2 I
* 172.16.200.0/30            10.0.0.20                    100        2 I

Meaning

When you see one prefix and more than one next hop, it means that multiple paths are advertised to Router R4.

Purpose

Make sure that multiple paths to the 172.16.199.1/32 destination are received from Router R1 and advertised to Router R8. Make sure that multiple paths to the 172.16.198.1/32 destination are received from Router R1, but only one path to this destination is advertised to Router R8.

Action

user@R4> show route receive-protocol bgp 10.0.0.10
inet.0: 19 destinations, 22 routes (19 active, 0 holddown, 0 hidden)
  Prefix                  Nexthop              MED     Lclpref    AS path
* 10.0.0.50/32            10.0.15.2                    100        2 2 I
* 10.0.0.60/32            10.0.0.20                    100        2 I
* 10.0.0.70/32            10.0.0.30                    100        2 I
* 172.16.198.1/32            10.0.0.20                    100        2 I
                          10.0.15.2                    100        2 2 I
* 172.16.199.1/32            10.0.0.20                    100        2 I
                          10.0.0.30                    100        2 I
                          10.0.15.2                    100        2 2 I
* 172.16.200.0/30            10.0.0.20                    100        2 I

user@R4> show route advertising-protocol bgp 10.0.0.80
inet.0: 19 destinations, 22 routes (19 active, 0 holddown, 0 hidden)
  Prefix                  Nexthop              MED     Lclpref    AS path
* 10.0.0.50/32            10.0.15.2                    100        2 2 I
* 10.0.0.60/32            10.0.0.20                    100        2 I
* 10.0.0.70/32            10.0.0.30                    100        2 I
* 172.16.198.1/32            10.0.0.20                    100        2 I
* 172.16.199.1/32            10.0.0.20                    100        2 I
                          10.0.0.30                    100        2 I
                          10.0.15.2                    100        2 2 I
* 172.16.200.0/30            10.0.0.20                    100        2 I

Meaning

The show route receive-protocol command shows that Router R4 receives two paths to the 172.16.198.1/32 destination and three paths to the 172.16.199.1/32 destination. The show route advertising-protocol command shows that Router R4 advertises only one path to the 172.16.198.1/32 destination and advertises all three paths to the 172.16.199.1/32 destination.

Because of the prefix policy that is applied to Router R4, Router R4 does not advertise multiple paths to the 172.16.198.1/32 destination. Router R4 advertises only one path to the 172.16.198.1/32 destination even though it receives multiple paths to this destination.

Purpose

Make sure that Router R8 receives multiple paths to the 172.16.199.1/32 destination through Router R4. Make sure that Router R8 receives only one path to the 172.16.198.1/32 destination through Router R4.

Action

user@R8> show route receive-protocol bgp 10.0.0.40
inet.0: 18 destinations, 20 routes (18 active, 0 holddown, 0 hidden)
  Prefix                  Nexthop              MED     Lclpref    AS path
* 10.0.0.50/32            10.0.15.2                    100        2 2 I
* 10.0.0.60/32            10.0.0.20                    100        2 I
* 10.0.0.70/32            10.0.0.30                    100        2 I
* 172.16.198.1/32            10.0.0.20                    100        2 I
* 172.16.199.1/32            10.0.0.20                    100        2 I
                          10.0.0.30                    100        2 I
                          10.0.15.2                    100        2 2 I
* 200.1.1.0/30            10.0.0.20                    100        2 I

Purpose

On the downstream devices, Router R4 and Router R8, verify that a path ID uniquely identifies the path. Look for the Addpath Path ID: string.

Action

user@R4> show route 172.16.199.1/32 detail

inet.0: 18 destinations, 20 routes (18 active, 0 holddown, 0 hidden)
172.16.199.1/32 (3 entries, 3 announced)
        *BGP    Preference: 170/-101
                Next hop type: Indirect
                Next-hop reference count: 9
                Source: 10.0.0.10
                Next hop type: Router, Next hop index: 676
                Next hop: 10.0.14.1 via lt-1/2/0.41, selected
                Protocol next hop: 10.0.0.20
                Indirect next hop: 92041c8 262146
                State: <Active Int Ext>
                Local AS:     1 Peer AS:     1
                Age: 1:44:37    Metric2: 2 
                Task: BGP_1.10.0.0.10+64227
                Announcement bits (3): 2-KRT 3-BGP RT Background 4-Resolve tree 1 
                AS path: 2 I (Originator) Cluster list:  10.0.0.10
                AS path:  Originator ID: 10.0.0.20
                Accepted
                Localpref: 100
                Router ID: 10.0.0.10
                Addpath Path ID: 1
         BGP    Preference: 170/-101
                Next hop type: Indirect
                Next-hop reference count: 4
                Source: 10.0.0.10
                Next hop type: Router, Next hop index: 676
                Next hop: 10.0.14.1 via lt-1/2/0.41, selected
                Protocol next hop: 10.0.0.30
                Indirect next hop: 92042ac 262151
                State: <NotBest Int Ext>
                Inactive reason: Not Best in its group - Router ID
                Local AS:     1 Peer AS:     1
                Age: 1:44:37    Metric2: 2 
                Task: BGP_1.10.0.0.10+64227
                Announcement bits (1): 3-BGP RT Background 
                AS path: 2 I (Originator) Cluster list:  10.0.0.10
                AS path:  Originator ID: 10.0.0.30
                Accepted
                Localpref: 100
                Router ID: 10.0.0.10
                Addpath Path ID: 2
         BGP    Preference: 170/-101
                Next hop type: Indirect
                Next-hop reference count: 4
                Source: 10.0.0.10
                Next hop type: Router, Next hop index: 676
                Next hop: 10.0.14.1 via lt-1/2/0.41, selected
                Protocol next hop: 10.0.15.2
                Indirect next hop: 92040e4 262150
                State: <Int Ext>
                Inactive reason: AS path
                Local AS:     1 Peer AS:     1
                Age: 1:44:37    Metric2: 2 
                Task: BGP_1.10.0.0.10+64227
                Announcement bits (1): 3-BGP RT Background 
                AS path: 2 2 I
                Accepted
                Localpref: 100
                Router ID: 10.0.0.10
                Addpath Path ID: 3

user@R8> show route 172.16.199.1/32 detail

inet.0: 17 destinations, 19 routes (17 active, 0 holddown, 0 hidden)
172.16.199.1/32 (3 entries, 1 announced)
        *BGP    Preference: 170/-101
                Next hop type: Indirect
                Next-hop reference count: 9
                Source: 10.0.0.40
                Next hop type: Router, Next hop index: 1045
                Next hop: 10.0.48.1 via lt-1/2/0.84, selected
                Protocol next hop: 10.0.0.20
                Indirect next hop: 91fc0e4 262148
                State: <Active Int Ext>
                Local AS:     1 Peer AS:     1
                Age: 1:56:51    Metric2: 3 
                Task: BGP_1.10.0.0.40+179
                Announcement bits (2): 2-KRT 4-Resolve tree 1 
                AS path: 2 I (Originator) Cluster list:  10.0.0.40 10.0.0.10
                AS path:  Originator ID: 10.0.0.20
                Accepted
                Localpref: 100
                Router ID: 10.0.0.40
                Addpath Path ID: 1
         BGP    Preference: 170/-101
                Next hop type: Indirect
                Next-hop reference count: 4
                Source: 10.0.0.40
                Next hop type: Router, Next hop index: 1045
                Next hop: 10.0.48.1 via lt-1/2/0.84, selected
                Protocol next hop: 10.0.0.30
                Indirect next hop: 91fc1c8 262152
                State: <NotBest Int Ext>
                Inactive reason: Not Best in its group - Router ID
                Local AS:     1 Peer AS:     1
                Age: 1:56:51    Metric2: 3 
                Task: BGP_1.10.0.0.40+179
                AS path: 2 I (Originator) Cluster list:  10.0.0.40 10.0.0.10
                AS path:  Originator ID: 10.0.0.30
                Accepted
                Localpref: 100
                Router ID: 10.0.0.40
                Addpath Path ID: 2
         BGP    Preference: 170/-101
                Next hop type: Indirect
                Next-hop reference count: 4
                Source: 10.0.0.40
                Next hop type: Router, Next hop index: 1045
                Next hop: 10.0.48.1 via lt-1/2/0.84, selected
                Protocol next hop: 10.0.15.2
                Indirect next hop: 91fc2ac 262153
                State: <Int Ext>
                Inactive reason: AS path
                Local AS:     1 Peer AS:     1
                Age: 1:56:51    Metric2: 3 
                Task: BGP_1.10.0.0.40+179
                AS path: 2 2 I (Originator) Cluster list:  10.0.0.40
                AS path:  Originator ID: 10.0.0.10
                Accepted
                Localpref: 100
                Router ID: 10.0.0.40
                Addpath Path ID: 3

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 RR1:

1. Configure the interfaces with IPv4 addresses.

   content_copy zoom_out_map

   [edit interfaces]
   user@RR1# set ge-1/0/10 unit 0 description RR1->R2 
   user@RR1# set ge-1/0/10 unit 0 family inet address 10.0.12.1/24
   user@RR1# set ge-1/0/11 unit 0 description RR1->RR4 
   user@RR1# set ge-1/0/11 unit 0 family inet address 10.0.14.1/24
   user@RR1# set ge-1/0/12 unit 0 description RR1->R5 
   user@RR1# set ge-1/0/12 unit 0 family inet address 10.0.15.1/24
   user@RR1# set ge-1/0/13 unit 0 description RR1->R3 
   user@RR1# set ge-1/0/13 unit 0 family inet address 10.0.13.1/24
   

2. Configure the loopback address.

   content_copy zoom_out_map

   [edit interfaces]
   user@RR1# set lo0 unit 0 family inet address 10.0.0.10/32
   

3. Configure interior gateway protocol (IGP) such as OSPF or IS-IS.

   content_copy zoom_out_map

   [edit protocols]
   user@RR1# set ospf area 0.0.0.0 interface lo0.10 passive
   user@RR1# set ospf area 0.0.0.0 interface ge-1/0/10
   user@RR1# set ospf area 0.0.0.0 interface ge-1/0/13
   user@RR1# set ospf area 0.0.0.0 interface ge-1/0/11
   user@RR1# set ospf area 0.0.0.0 interface ge-1/0/12
   

4. Configure internal group rr for interfaces connecting to internal routers R2 and R3.

   content_copy zoom_out_map

   [edit protocols]
   user@RR1# set bgp group rr type internal
   user@RR1# set bgp group rr local-address 10.0.0.10
   user@RR1# set bgp group rr cluster 10.0.0.10
   user@RR1# set bgp group rr neighbor 10.0.0.20
   user@RR1# set bgp group rr neighbor 10.0.0.30
   

5. Configure load balancing for internal BGP group rr.

   content_copy zoom_out_map

   [edit protocols]
   user@RR1# set bgp group rr multipath
   

6. Configure internal group rr_rr for route reflectors.

   content_copy zoom_out_map

   [edit protocols]
   user@RR1# set bgp group rr_rr type internal
   user@RR1# set bgp group rr_rr local-address 10.0.0.10
   

7. Configure the addpath multipath feature to advertise contributor multiple paths only and limit the number of advertised multipaths to 6.

   content_copy zoom_out_map

   [edit protocols]
   user@RR1# set bgp group rr_rr neighbor 10.0.0.40 family inet unicast add-path send multipath
   user@RR1# set bgp group rr_rr neighbor 10.0.0.40 family inet unicast add-path send path-count 6
   

8. Configure EBGP on interfaces connecting to the external edge routers.

   content_copy zoom_out_map

   [edit protocols]
   user@RR1# set bgp group e1 type external
   user@RR1# set bgp group e1 neighbor 10.0.15.2 local-address 10.0.15.1
   user@RR1# set bgp group e1 neighbor 10.0.15.2 peer-as 64502
   

9. Define a policy loadbal_199 for per packet load balancing.

   content_copy zoom_out_map

   [edit policy-options]
   user@RR1# set prefix-list match_199 199.1.1.1/32
   user@RR1# set policy-statement loadbal_199 term match_100 from prefix-list match_199
   user@RR1# set policy-statement loadbal_199 from route-filter 199.1.1.1/32 exact
   user@RR1# set policy-statement loadbal_199 then load-balance per-packet
   

10. Apply the defined export policy loadbal_199.

    content_copy zoom_out_map

    [edit routing-options]
    user@RR1# set forwarding-table export loadbal_199
    

11. Configure the router ID and the autonomous system for BGP hosts.

    content_copy zoom_out_map

    [edit routing-options]
    user@RR1# set router-id 10.0.0.10
    user@RR1# set autonomous-system 64501
    

Purpose

Verify the available multipath routes for destination 199.1.1.1/32.

Action

From operational mode, run the show route 199.1.1.1/32 detail command on Router RR1.

user@RR1> show route 199.1.1.1/32 detail
inet.0: 22 destinations, 26 routes (22 active, 0 holddown, 0 hidden)
199.1.1.1/32 (3 entries, 2 announced)
        *BGP    Preference: 170/-101
                Next hop type: Indirect, Next hop index: 0
                Address: 0xae5cc90
                Next-hop reference count: 1
                Source: 10.0.0.20
                Next hop type: Router, Next hop index: 1118
                Next hop: 10.0.12.2 via lt-1/0/10.1, selected
                Session Id: 0x0
                Next hop type: Router, Next hop index: 1115
                Next hop: 10.0.13.2 via lt-1/0/10.9
                Session Id: 0x0
                Protocol next hop: 10.0.0.20
                Indirect next hop: 0xc409410 1048574 INH Session ID: 0x0
                Protocol next hop: 10.0.0.30
                Indirect next hop: 0xc409520 1048575 INH Session ID: 0x0
                State:  <Active Int Ext>
                Local AS:     1 Peer AS:     1
                Age: 4:03:29 	Metric2: 1
                Validation State: unverified
                Task: BGP_1.10.0.0.20
                Announcement bits (3): 2-KRT 3-BGP_RT_Background 4-Resolve tree 2
                AS path: 2 I
                Communities: 4713:100
                Accepted Multipath
                Localpref: 100
                Router ID: 10.0.0.20
         BGP    Preference: 170/-101
                Next hop type: Indirect, Next hop index: 0
                Address: 0xae0ec10
                Next-hop reference count: 4
                Source: 10.0.0.30
                Next hop type: Router, Next hop index: 1115
                Next hop: 10.0.13.2 via lt-1/0/10.9, selected
                Session Id: 0x0
                Protocol next hop: 10.0.0.30
                Indirect next hop: 0xc409520 1048575 INH Session ID: 0x0
                State: <NotBest Int Ext>
                Inactive reason: Not Best in its group - Router ID
                Local AS:  64501 Peer AS: 64501
                Age: 4:03:29 	Metric2: 1
                Validation State: unverified
                Task: BGP_1.10.0.0.30
                Announcement bits (1): 3-BGP_RT_Background
                AS path: 2 I
                Communities: 4713:100
                Accepted MultipathContrib
                Localpref: 100
                Router ID: 10.0.0.30
         BGP    Preference: 170/-101
                Next hop type: Router, Next hop index: 1105
                Address: 0xae0e970
                Next-hop reference count: 5
                Source: 10.0.15.2
                Next hop: 10.0.15.2 via lt-1/0/10.6, selected
                Session Id: 0x0
                State: <Ext>
                Inactive reason: AS path
                Local AS:     1 Peer AS:     2
                Age: 4:05:01
                Validation State: unverified
                Task: BGP_2.10.0.15.2
                AS path: 2 2 I
                Communities: 4713:100
                Accepted
                Localpref: 100
                Router ID: 10.0.0.50 

Meaning

The selective advertising multipath feature is enabled on Router RR1 and there is more than one nexthop available for route 199.1.1.1/32. The two available next hops for route 199.1.1.1/32 are 10.0.0.20 and 10.0.0.30.

Purpose

Verify that Router RR1 is advertising the multipath routes.

Action

From operational mode, run the show route advertising-protocol bgp 10.0.0.40 command on Router RR1.

user@RR1> show route advertising-protocol bgp 10.0.0.40
inet.0: 22 destinations, 26 routes (22 active, 0 holddown, 0 hidden)
  Prefix		  Nexthop	      MED     Lclpref    AS path
* 10.0.0.50/32            10.0.15.2                    100        2 2 I
* 10.0.0.60/32            10.0.0.20                    100        2 I
* 10.0.0.70/32            10.0.0.30                    100        2 I
* 198.1.1.1/32            10.0.0.20                    100        2 I
* 199.1.1.1/32            10.0.0.20                    100        2 I
                          10.0.0.30                    100        2 I

 

user@RR1> show route advertising-protocol bgp 10.0.0.40 detail  
inet.0: 22 destinations, 26 routes (22 active, 0 holddown, 0 hidden)
* 10.0.0.50/32 (1 entry, 1 announced)
 BGP group rr_rr type Internal
     Nexthop: 10.0.15.2
     Localpref: 100
     AS path: [1] 2 2 I
     Communities: 4713:100
     Addpath Path ID: 1
….* 199.1.1.1/32 (3 entries, 2 announced)
 BGP group rr_rr type Internal
     Nexthop: 10.0.0.20
     Localpref: 100
     AS path: [1] 2 I
     Communities: 4713:100
     Cluster ID: 10.0.0.10
     Originator ID: 10.0.0.20
     Addpath Path ID: 1
 BGP group rr_rr type Internal
     Nexthop: 10.0.0.30                 
     Localpref: 100                     
     AS path: [1] 2 I                   
     Communities: 4713:100              
     Cluster ID: 10.0.0.10              
     Originator ID: 10.0.0.30
     Addpath Path ID: 2

Meaning

Router RR1 is advertising two next hops 10.0.0.20 and 10.0.0.30 for route 199.1.1.1/32 to Router RR4.

Purpose

Multipath is not configured on Router RR4, therefore route 199.1.1.1/32 is not eligible for add-path. Verify that Router RR4 advertises only one route for 199.1.1.1/32 to Router R8.

Action

From operational mode, run the show route advertising-protocol bgp 10.0.0.80 command on Router RR4.

user@RR4> show route advertising-protocol bgp 10.0.0.80 detail 
inet.0: 20 destinations, 21 routes (20 active, 0 holddown, 0 hidden)
* 10.0.0.50/32 (1 entry, 1 announced)
 BGP group rr_client type Internal
     Nexthop: 10.0.15.2
     Localpref: 100
     AS path: [1] 2 2 I
     Communities: 4713:100
     Cluster ID: 10.0.0.40
     Originator ID: 10.0.0.10

     Addpath Path ID: 1
…
* 198.1.1.1/32 (1 entry, 1 announced)
 BGP group rr_client type Internal
     Nexthop: 10.0.0.20
     Localpref: 100
     AS path: [1] 2 I (Originator)
     Cluster list:  10.0.0.10
     Originator ID: 10.0.0.20
     Communities: 4713:100
     Cluster ID: 10.0.0.40
     Addpath Path ID: 1

* 199.1.1.1/32 (2 entries, 1 announced)
 BGP group rr_client type Internal
     Nexthop: 10.0.0.20
     Localpref: 100
     AS path: [1] 2 I (Originator)      
     Cluster list:  10.0.0.10
     Originator ID: 10.0.0.20
     Communities: 4713:100
     Cluster ID: 10.0.0.40
     Addpath Path ID: 1

Meaning

Since multipath is not enabled on Router RR4, only one path 10.0.0.20 is advertised to Router R8.

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 RR4:

1. Configure the interfaces with IPv4 addresses.

   content_copy zoom_out_map

   [edit interfaces]
   user@RR4# set ge-1/0/10 unit 0 description RR4->RR1 
   user@RR4# set ge-1/0/10 unit 0 family inet address 10.0.14.2/24
   user@RR4# set ge-1/0/11 unit 0 description RR4->R8 
   user@RR4# set ge-1/0/11 unit 0 family inet address 10.0.48.1/24
   

2. Configure the loopback address.

   content_copy zoom_out_map

   [edit interfaces]
   user@RR4# set lo0 unit 0 family inet address 10.0.0.40/32
   

3. Configure OSPF or any other interior gateway protocol (IGP).

   content_copy zoom_out_map

   [edit protocols]
   user@RR4# set ospf area 0.0.0.0 interface lo0.40 passive
   user@RR4# set ospf area 0.0.0.0 interface ge-1/0/10
   user@RR4# set ospf area 0.0.0.0 interface ge-1/0/11
   

4. Configure two IBGP groups rr for route reflectors and rr_client for clients of route reflectors.

   content_copy zoom_out_map

   [edit protocols]
   user@RR4# set bgp group rr type internal
   user@RR4# set bgp group rr local-address 10.0.0.40
   user@RR4# set bgp group rr family inet unicast add-path receive
   user@RR4# set bgp group rr neighbor 10.0.0.10
   user@RR4# set bgp group rr_client type internal
   user@RR4# set bgp group rr_client local-address 10.0.0.40 
   user@RR4# set bgp group rr_client cluster 10.0.0.40
   

5. Configure the feature to send multiple paths that contain 4713:100 community value only and limit the number of advertised multipaths to 6.

   content_copy zoom_out_map

   [edit protocols]
   user@RR4# set bgp group rr_client neighbor 10.0.0.80 family inet unicast add-path send prefix-policy addpath-communities-send-4713-100
   user@RR4# set bgp group rr_client neighbor 10.0.0.80 family inet unicast add-path send path-count 6
   

6. Define a policy addpath-community-members 4713:100 to filter prefixes with the community value 4713:100 and restrict the device to send up to 16 paths to Router R8. This limit overrides the previously configured add-path send path-count of 6 at the BGP group hierarchy level.

   content_copy zoom_out_map

   [edit policy-options]
   user@RR4# set community addpath-communities-send members 4713:100
   user@RR4# set policy-statement addpath-communities-send-4713-100 term term1 from protocol bgp
   user@RR4# set policy-statement addpath-communities-send-4713-100 term term1 from community addpath-communities-send
   user@RR4# set policy-statement addpath-communities-send-4713-100 term term1 then add-path send-count 16
   user@RR4# set policy-statement addpath-communities-send-4713-100 term term1 then accept
   

7. Configure the router ID and the autonomous system for BGP hosts.

   content_copy zoom_out_map

   [edit routing-options]
   user@RR4# set router-id 10.0.0.40
   user@RR4# set autonomous-system 64501
   

Purpose

Verify that Router RR4 can send multiple paths to Router R8.

Action

From operational mode, run the show route advertising-protocol bgp neighbor-address command on Router RR4.

user@RR4> show route advertising-protocol bgp 10.0.0.80 
inet.0: 20 destinations, 23 routes (20 active, 0 holddown, 0 hidden)
  Prefix                  Nexthop              MED     Lclpref    AS path
* 10.0.0.50/32            10.0.15.2                    100        2 2 I
* 10.0.0.60/32            10.0.0.20                    100        2 I
* 10.0.0.70/32            10.0.0.30                    100        2 I
* 198.1.1.1/32            10.0.0.20                    100        2 I
                          10.0.15.2                    100        2 2 I
* 199.1.1.1/32            10.0.0.20                    100        2 I
                          10.0.0.30                    100        2 I
                          10.0.15.2                    100        2 2 I

Meaning

Router RR4 is advertising multiple paths 10.0.0.20, 10.0.0.30, and 10.0.15.2 to Router R8.

Purpose

Verify that Router R8 is receiving the multipath routes from Router RR4.

Action

From operational mode, run the show route receive-protocol bgp neighbor-address command on Router R8.

user@R8> show route receive-protocol bgp 10.0.0.40 

inet.0: 19 destinations, 22 routes (19 active, 0 holddown, 0 hidden)
  Prefix                  Nexthop              MED     Lclpref    AS path
* 10.0.0.50/32            10.0.15.2                    100        2 2 I
* 10.0.0.60/32            10.0.0.20                    100        2 I
* 10.0.0.70/32            10.0.0.30                    100        2 I
* 198.1.1.1/32            10.0.0.20                    100        2 I
                          10.0.15.2                    100        2 2 I
* 199.1.1.1/32            10.0.0.20                    100        2 I
                          10.0.0.30                    100        2 I
                          10.0.15.2                    100        2 2 I
 

Meaning

Router R8 is receiving multiple next hops 10.0.0.20, 10.0.0.30, and 10.0.15.2 for route 199.1.1.1/32 from Router RR4.

Purpose

Router RR4 must advertise multipath routes with community value of 4713:100 only to Router R8.

Action

From operational mode, run the show route 199.1.1.1/32 detail command on Router RR4.

user@RR4> show route 199.1.1.1/32 detail
inet.0: 20 destinations, 23 routes (20 active, 0 holddown, 0 hidden)
199.1.1.1/32 (3 entries, 3 announced)
        *BGP    Preference: 170/-101
                Next hop type: Indirect, Next hop index: 0
                Address: 0xae0ea90
                Next-hop reference count: 6
                Source: 10.0.0.10
                Next hop type: Router, Next hop index: 1115
                Next hop: 10.0.14.1 via ge-1/0/10.4, selected
                Session Id: 0x0
                Protocol next hop: 10.0.0.20
                Indirect next hop: 0xc4091f0 1048581 INH Session ID: 0x0
                State: <Active Int Ext>
                Local AS:     1 Peer AS:     1
                Age: 4d 20:56:53        Metric2: 2 
                Validation State: unverified 
                Task: BGP_1.10.0.0.10 
                Announcement bits (3): 2-KRT 3-BGP_RT_Background 4-Resolve tree 2 
                AS path: 2 I (Originator) 
                Cluster list:  10.0.0.10 
                Originator ID: 10.0.0.20 
                Communities: 4713:100 
                Accepted 
                Localpref: 100 
                Router ID: 10.0.0.10 
                Addpath Path ID: 1 
         BGP    Preference: 170/-101 
                Next hop type: Indirect, Next hop index: 0 
                Address: 0xae0eb50 
                Next-hop reference count: 3 
                Source: 10.0.0.10 
                Next hop type: Router, Next hop index: 1115 
                Next hop: 10.0.14.1 via lt-1/0/10.4, selected 
                Session Id: 0x0 
                Protocol next hop: 10.0.0.30 
                Indirect next hop: 0xc409300 1048582 INH Session ID: 0x0 
                State:  <NotBest Int Ext> 
                Inactive reason: Not Best in its group - Router ID 
                Local AS:     1 Peer AS:     1 
                Age: 4d 20:56:53        Metric2: 2 
                Validation State: unverified 
                Task: BGP_1.10.0.0.10 
                Announcement bits (1): 3-BGP_RT_Background 
                AS path: 2 I (Originator) 
                Cluster list:  10.0.0.10 
                Originator ID: 10.0.0.30 
                Communities: 4713:100 
                Accepted 
                Localpref: 100 
                Router ID: 10.0.0.10 
                Addpath Path ID: 2 
         BGP    Preference: 170/-101 
                Next hop type: Indirect, Next hop index: 0 
                Address: 0xae0e9d0 
                Next-hop reference count: 4 
                Source: 10.0.0.10 
                Next hop type: Router, Next hop index: 1115 
                Next hop: 10.0.14.1 via lt-1/0/10.4, selected 
                Session Id: 0x0 
                Protocol next hop: 10.0.15.2 
                Indirect next hop: 0xc4090e0 1048580 INH Session ID: 0x0 
                State:  <Int Ext> 
                Inactive reason: AS path 
                Local AS:     1 Peer AS:     1 
                Age: 4d 20:56:53        Metric2: 2 
                Validation State: unverified 
                Task: BGP_1.10.0.0.10 
                Announcement bits (1): 3-BGP_RT_Background 
                AS path: 2 2 I 
                Communities: 4713:100 
                Accepted 
                Localpref: 100 
                Router ID: 10.0.0.10 
                Addpath Path ID: 3  

Meaning

Router RR4, is advertising three paths with community value of 4713:100 to Router R8.

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 PE1:

1. Configure the physical interfaces. Ensure to configure family mpls on the core facing interface.

   content_copy zoom_out_map

   [edit]
   user@PE1# set interfaces ge-0/0/0 unit 0 family inet address 172.16.12.2/30
   user@PE1# set interfaces ge-0/0/2 unit 0 family inet address 10.1.23.1/30
   user@PE1# set interfaces ge-0/0/2 unit 0 family mpls

2. Configure the loopback interfaces. The secondary loopback is optional and is applied under the routing instance in a later step.

   content_copy zoom_out_map

   [edit]
   user@PE1# set interfaces lo0 unit 0 family inet address 10.1.255.2/32 primary
   user@PE1# set interfaces lo0 unit 1 family inet address 10.1.255.22/32

3. Configure the router ID and the autonomous system number.

   content_copy zoom_out_map

   [edit]
   user@PE1# set routing-options router-id 10.1.255.2
   user@PE1# set routing-options autonomous-system 65000

4. Configure the OSPF protocol.

   content_copy zoom_out_map

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

5. Configure the RSVP protocol.

   content_copy zoom_out_map

   [edit]
   user@PE1# set protocols rsvp interface ge-0/0/2.0
   user@PE1# set protocols rsvp interface lo0.0

6. Configure the MPLS protocol and an LSP towards the ABR. Include the entropy-label option to add the entropy label to the MPLS label stack.

   content_copy zoom_out_map

   [edit protocols]
   user@PE1# set protocols mpls icmp-tunneling
   user@PE1# set protocols mpls label-switched-path pe1-abr to 10.1.255.4
   user@PE1# set protocols mpls label-switched-path pe1-abr entropy-label
   user@PE1# set protocols mpls interface ge-0/0/2.0
   user@PE1# set protocols mpls interface lo0.0

7. Configure IBGP using family inet labeled-unicast for the ABR peering and family inet-vpn for the PE2 peering. Enable entropy label capability for BGP labeled unicast.

   content_copy zoom_out_map

   [edit]
   user@PE1# set protocols bgp group ibgp type internal
   user@PE1# set protocols bgp group ibgp local-address 10.1.255.2
   user@PE1# set protocols bgp group ibgp family inet labeled-unicast entropy-label
   user@PE1# set protocols bgp group ibgp neighbor 10.1.255.4 family inet labeled-unicast rib inet.3
   user@PE1# set protocols bgp group ibgp neighbor 10.1.255.6 family inet-vpn unicast

8. Define a policy to export BGP VPN routes into OSPF. The policy is applied under OSPF in the routing instance.

   content_copy zoom_out_map

   [edit]
   user@PE1# set policy-options policy-statement bgp-to-ospf from protocol bgp
   user@PE1# set policy-options policy-statement bgp-to-ospf then accept

9. Define a load balancing policy and apply it under the routing-options forwarding-table. PE1 only has one path in the example therefore this step is not needed, but for this example we are applying the same load balancing policy on all devices.

   content_copy zoom_out_map

   [edit]
   user@PE1# set policy-options policy-statement pplb then load-balance per-packet
   user@PE1# set routing-options forwarding-table export pplb

10. Configure the Layer 3 VPN routing instance.

    content_copy zoom_out_map

    [edit]
    user@PE1# set routing-instances VPN-l3vpn instance-type vrf

11. Assign the interfaces to the routing instance.

    content_copy zoom_out_map

    [edit]
    user@PE1# set routing-instances VPN-l3vpn interface ge-0/0/0.0
    user@PE1# set routing-instances VPN-l3vpn interface lo0.1

12. Configure the route distinguisher for the routing instance.

    content_copy zoom_out_map

    [edit]
    user@PE1# set routing-instances VPN-l3vpn route-distinguisher 10.1.255.2:1

13. Configure a VPN routing and forwarding (VRF) target for the routing instance.

    content_copy zoom_out_map

    [edit]
    user@PE1# set routing-instances VPN-l3vpn vrf-target target:65000:1

14. Configure the protocol OSPF under the routing instance and apply the previously configured bgp-to-ospf policy.

    content_copy zoom_out_map

    [edit]
    user@PE1# set routing-instances VPN-l3vpn protocols ospf area 0.0.0.0 interface ge-0/0/0.0
    user@PE1# set routing-instances VPN-l3vpn protocols ospf area 0.0.0.0 interface lo0.1 passive
    user@PE1# set routing-instances VPN-l3vpn protocols ospf export bgp-to-ospf

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 P1:

1. Configure the physical interfaces.

   content_copy zoom_out_map

   [edit]
   user@P1# set interfaces ge-0/0/0 unit 0 family inet address 10.1.23.2/30
   user@P1# set interfaces ge-0/0/0 unit 0 family mpls
   user@P1# set interfaces ge-0/0/2 unit 0 family inet address 10.1.34.1/30
   user@P1# set interfaces ge-0/0/2 unit 0 family mpls

2. Configure the loopback interface.

   content_copy zoom_out_map

   [edit]
   user@P1# set interfaces lo0 unit 0 family inet address 10.1.255.3/32 primary

3. Configure the router ID.

   content_copy zoom_out_map

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

4. Configure the OSPF protocol.

   content_copy zoom_out_map

   [edit]
   user@P1# set protocols ospf traffic-engineering
   user@P1# set protocols ospf area 0.0.0.0 interface lo0.0 passive
   user@P1# set protocols ospf area 0.0.0.0 interface ge-0/0/0.0
   user@P1# set protocols ospf area 0.0.0.0 interface ge-0/0/2.0

5. Configure the RSVP protocol.

   content_copy zoom_out_map

   [edit]
   user@P1# set protocols rsvp interface ge-0/0/0.0
   user@P1# set protocols rsvp interface lo0.0
   user@P1# set protocols rsvp interface ge-0/0/2.0

6. Configure the MPLS protocol.

   content_copy zoom_out_map

   [edit]
   user@P1# set protocols mpls icmp-tunneling
   user@P1# set protocols mpls interface ge-0/0/0.0
   user@P1# set protocols mpls interface lo0.0
   user@P1# set protocols mpls interface ge-0/0/2.0

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 ABR:

1. Configure the physical interfaces.

   content_copy zoom_out_map

   [edit]
   user@ABR# set interfaces ge-0/0/0 unit 0 family inet address 10.1.34.2/30
   user@ABR# set interfaces ge-0/0/0 unit 0 family mpls
   user@ABR# set interfaces ge-0/0/2 unit 0 family inet address 10.1.45.1/30
   user@ABR# set interfaces ge-0/0/2 unit 0 family mpls
   user@ABR# set interfaces ge-0/0/3 unit 0 family inet address 10.1.45.5/30
   user@ABR# set interfaces ge-0/0/3 unit 0 family mpls

2. Configure the loopback interface.

   content_copy zoom_out_map

   [edit]
   user@ABR# set interfaces lo0 unit 0 family inet address 10.1.255.4/32 primary

3. Configure MPLS labels that the router uses for hashing the packets to its destination for load balancing.

   content_copy zoom_out_map

   [edit]
   user@ABR# set forwarding-options hash-key family mpls label-1
   user@ABR# set forwarding-options hash-key family mpls label-2
   user@ABR# set forwarding-options hash-key family mpls label-3
   user@ABR# set forwarding-options enhanced-hash-key family mpls no-payload

4. Configure the router ID and the autonomous system number.

   content_copy zoom_out_map

   [edit]
   user@ABR# set routing-options router-id 10.1.255.4
   user@ABR# set routing-options autonomous-system 65000

5. Configure the OSPF protocol.

   content_copy zoom_out_map

   [edit]
   user@ABR# set protocols ospf traffic-engineering
   user@ABR# set protocols ospf area 0.0.0.0 interface lo0.0 passive
   user@ABR# set protocols ospf area 0.0.0.0 interface ge-0/0/0.0
   user@ABR# set protocols ospf area 0.0.0.1 interface ge-0/0/2.0
   user@ABR# set protocols ospf area 0.0.0.1 interface ge-0/0/3.0

6. Configure the RSVP protocol.

   content_copy zoom_out_map

   [edit]
   user@ABR# set protocols rsvp interface lo0.0
   user@ABR# set protocols rsvp interface ge-0/0/0.0
   user@ABR# set protocols rsvp interface ge-0/0/2.0
   user@ABR# set protocols rsvp interface ge-0/0/3.0

7. Configure the MPLS protocol and specify the LSPs towards PE1 and PE2. Two LSPs are created towards PE2 for the purpose of load balancing traffic to show different LSPs and interfaces are used.

   content_copy zoom_out_map

   [edit]
   user@ABR# set protocols mpls icmp-tunneling
   user@ABR# set protocols mpls label-switched-path abr-pe1 to 10.1.255.2
   user@ABR# set protocols mpls label-switched-path abr-pe1 entropy-label
   user@ABR# set protocols mpls label-switched-path abr-pe2 to 10.1.255.6
   user@ABR# set protocols mpls label-switched-path abr-pe2 entropy-label
   user@ABR# set protocols mpls label-switched-path abr-pe2 primary to-r6-1
   user@ABR# set protocols mpls label-switched-path abr-pe2-2 to 10.1.255.6
   user@ABR# set protocols mpls label-switched-path abr-pe2-2 entropy-label
   user@ABR# set protocols mpls label-switched-path abr-pe2-2 primary to-r6-2
   user@ABR# set protocols mpls path to-r6-1 10.1.45.2 strict
   user@ABR# set protocols mpls path to-r6-1 10.1.56.2 strict
   user@ABR# set protocols mpls path to-r6-2 10.1.45.6 strict
   user@ABR# set protocols mpls path to-r6-2 10.1.56.6 strict
   user@ABR# set protocols mpls interface lo0.0
   user@ABR# set protocols mpls interface ge-0/0/0.0
   user@ABR# set protocols mpls interface ge-0/0/2.0
   user@ABR# set protocols mpls interface ge-0/0/3.0

8. Configure IBGP to both PE1 and PE2 using family inet labeled-unicast. Apply the policy to advertise the inet.3 loopback route from both PE1 and PE2. We show the policy in the next step.

   content_copy zoom_out_map

   [edit]
   user@ABR# set protocols bgp group ibgp type internal
   user@ABR# set protocols bgp group ibgp local-address 10.1.255.4
   user@ABR# set protocols bgp group ibgp family inet labeled-unicast rib inet.3
   user@ABR# set protocols bgp group ibgp neighbor 10.1.255.2 export send-inet3-pe2
   user@ABR# set protocols bgp group ibgp neighbor 10.1.255.6 export send-inet3-pe1

9. Define a policy to match on the loopback addresses for PE1 and PE2.

   content_copy zoom_out_map

   [edit]
   user@ABR# set policy-options policy-statement send-inet3-pe1 from route-filter 10.1.255.2/32 exact
   user@ABR# set policy-options policy-statement send-inet3-pe1 then accept
   user@ABR# set policy-options policy-statement send-inet3-pe2 from route-filter 10.1.255.6/32 exact
   user@ABR# set policy-options policy-statement send-inet3-pe2 then accept

10. Define a policy for load balancing and apply it under the routing-options forwarding-table.

    content_copy zoom_out_map

    [edit]
    user@ABR# set policy-options policy-statement pplb then load-balance per-packet
    user@ABR# set routing-options forwarding-table export pplb

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 P1:

1. Configure the interfaces. In this example we are putting the interface connected to Host1 in a bridge domain and creating an IRB interface for verifying connectivity to Host1.

   content_copy zoom_out_map

   [edit]
   user@P1# set interfaces ge-0/0/4 unit 0 family bridge interface-mode access
   user@P1# set interfaces ge-0/0/4 unit 0 family bridge vlan-id 100
   user@P1# set interfaces irb unit 0 family inet address 10.1.31.1/30

2. Configure the bridge domain.

   content_copy zoom_out_map

   [edit]
   user@P1# set bridge-domains v100 vlan-id 100
   user@P1# set bridge-domains v100 routing-interface irb.0

3. Configure a filter to capture the traffic. For this example we are capturing all traffic.

   content_copy zoom_out_map

   [edit]
   user@P1# set firewall family any filter test term 1 then count test
   user@P1# set firewall family any filter test term 1 then port-mirror
   user@P1# set firewall family any filter test term 1 then accept

4. Apply the filter to the PE1 facing interface.

   content_copy zoom_out_map

   [edit]
   user@P1# set interfaces ge-0/0/0 unit 0 filter input test

5. Configure the port mirroring options. For this example we are mirroring all traffic and sending it to Host1 connected to interface ge-0/0/4.

   content_copy zoom_out_map

   [edit]
   user@P1# set forwarding-options port-mirroring input rate 1
   user@P1# set forwarding-options port-mirroring family any output interface ge-0/0/4.0

Purpose

Verify that the entropy label capability path attribute is being advertised from the ABR to PE1 for the route to PE2.

Action

From operational mode, run the show route advertising-protocol bgp 10.1.255.2 detail command on Router ABR.

user@ABR> show route advertising-protocol bgp 10.1.255.2 detail

inet.3: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)
* 10.1.255.6/32 (1 entry, 1 announced)
 BGP group ibgp type Internal
     Route Label: 299952
     Nexthop: Self
     Flags: Nexthop Change
     MED: 2
     Localpref: 4294967294
     AS path: [65000] I
     Entropy label capable

Meaning

The output shows that the host PE2 with the IP address of 10.1.255.6 has the entropy label capability and the route label that is used. The host is advertising the entropy label capability to its BGP neighbors.

Purpose

Verify that Router PE1 receives the entropy label advertisement for Router PE2.

Action

From operational mode, run the show route protocol bgp 10.1.255.6 extensive command on Router PE1.

user@PE1> show route protocol bgp 10.1.255.6 extensive

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

inet.3: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)
10.1.255.6/32 (1 entry, 1 announced)
        *BGP    Preference: 170/1
                Next hop type: Indirect, Next hop index: 0
                Address: 0x7b3ffd4
                Next-hop reference count: 2, key opaque handle: 0x0, non-key opaque handle: 0x0
                Source: 10.1.255.4
                Next hop type: Router, Next hop index: 0
                Next hop: 10.1.23.2 via ge-0/0/2.0, selected
                Label-switched-path pe1-abr
                Label operation: Push 299952, Push 299808(top)
                Label TTL action: prop-ttl, prop-ttl(top)
                Load balance label: Label 299952: Entropy label; Label 299808: None; 
                Label element ptr: 0x93d6bf8
                Label parent element ptr: 0x93d6c20
                Label element references: 3
                Label element child references: 2
                Label element lsp id: 0
                Session Id: 0
                Protocol next hop: 10.1.255.4
                Label operation: Push 299952
                Label TTL action: prop-ttl
                Load balance label: Label 299952: Entropy label; 
                Indirect next hop: 0x758c05c - INH Session ID: 0
                State: <Active Int Ext>
                Local AS: 65000 Peer AS: 65000
                Age: 1:33:11    Metric: 2       Metric2: 2 
                Validation State: unverified 
                Task: BGP_65000.10.1.255.4
                Announcement bits (2): 3-Resolve tree 1 4-Resolve_IGP_FRR task 
                AS path: I 
                Accepted
                Route Label: 299952
                Localpref: 4294967294
                Router ID: 10.1.255.4
                Session-IDs associated:
                Session-id: 324 Version: 3
                Thread: junos-main 
                Indirect next hops: 1
                        Protocol next hop: 10.1.255.4 Metric: 2 ResolvState: Resolved
                        Label operation: Push 299952
                        Label TTL action: prop-ttl
                        Load balance label: Label 299952: Entropy label; 
                        Indirect next hop: 0x758c05c - INH Session ID: 0
                        Indirect path forwarding next hops: 1
                                Next hop type: Router
                                Next hop: 10.1.23.2 via ge-0/0/2.0
                                Session Id: 0
                                10.1.255.4/32 Originating RIB: inet.3
                                  Metric: 2 Node path count: 1
                                  Forwarding nexthops: 1
                                        Next hop type: Router
                                        Next hop: 10.1.23.2 via ge-0/0/2.0
                                        Session Id: 0

Meaning

Router PE1 receives the entropy label capability advertisement from its BGP neighbor.

Purpose

Verify equal-cost multipath (ECMP) to PE2.

Action

From operational mode, run the show route table mpls.0 and show route forwarding-table label <label>commands on Router ABR.

user@ABR> show route table mpls.0

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

0                  *[MPLS/0] 2w1d 23:02:11, metric 1
                       Receive
1                  *[MPLS/0] 2w1d 23:02:11, metric 1
                       Receive
2                  *[MPLS/0] 2w1d 23:02:11, metric 1
                       Receive
13                 *[MPLS/0] 2w1d 23:02:11, metric 1
                       Receive
299936             *[VPN/170] 2d 21:47:02
                    >  to 10.1.34.1 via ge-0/0/0.0, label-switched-path abr-pe1
299952             *[VPN/170] 2d 21:47:02
                    >  to 10.1.45.2 via ge-0/0/2.0, label-switched-path abr-pe2
                       to 10.1.45.6 via ge-0/0/3.0, label-switched-path abr-pe2-2

ruser@ABR> show route forwarding-table label 299952 
Routing table: default.mpls
MPLS:
Destination        Type RtRef Next hop           Type Index    NhRef Netif
299952             user     0                    ulst  1048575     2
                              10.1.45.2         Swap 299824      516     2 ge-0/0/2.0
                              10.1.45.6         Swap 299840      572     2 ge-0/0/3.0
...

Meaning

The output shows an ECMP for the label used for the BGP labeled unicast route.

Purpose

Verify the routes to CE2.

Action

From operational mode, run the show route table VPN-l3vpn.inet.0 172.16.255.7 extensive and show route table VPN-l3vpn.inet.0 192.168.255.7 extensivecommands on Router PE1.

user@PE1> show route table VPN-l3vpn.inet.0 172.16.255.7 extensive

VPN-l3vpn.inet.0: 10 destinations, 10 routes (10 active, 0 holddown, 0 hidden)
172.16.255.7/32 (1 entry, 1 announced)
TSI:
OSPF area : 0.0.0.0, LSA ID : 172.16.255.7, LSA type : Summary
KRT in-kernel 172.16.255.7/32 -> {indirect(1048574)}
        *BGP    Preference: 170/-101
                Route Distinguisher: 10.1.255.6:1
                Next hop type: Indirect, Next hop index: 0
                Address: 0x7b40434
                Next-hop reference count: 9, key opaque handle: 0x0, non-key opaque handle: 0x0
                Source: 10.1.255.6
                Next hop type: Router, Next hop index: 515
                Next hop: 10.1.23.2 via ge-0/0/2.0, selected
                Label-switched-path pe1-abr
                Label operation: Push 299824, Push 299952, Push 299808(top)
                Label TTL action: prop-ttl, prop-ttl, prop-ttl(top)
                Load balance label: Label 299824: None; Label 299952: Entropy label; Label 299808: None; 
                Label element ptr: 0x93d6c98
                Label parent element ptr: 0x93d6bf8
                Label element references: 1
                Label element child references: 0
                Label element lsp id: 0
                Session Id: 140
                Protocol next hop: 10.1.255.6
                Label operation: Push 299824
                Label TTL action: prop-ttl
                Load balance label: Label 299824: None;
...

user@PE1> show route table VPN-l3vpn.inet.0 192.168.255.7 extensive 
VPN-l3vpn.inet.0: 10 destinations, 10 routes (10 active, 0 holddown, 0 hidden)
192.168.255.7/32 (1 entry, 1 announced)
TSI:
OSPF area : 0.0.0.0, LSA ID : 192.168.255.7, LSA type : Summary
KRT in-kernel 192.168.255.7/32 -> {indirect(1048574)}
        *BGP    Preference: 170/-101
                Route Distinguisher: 10.1.255.6:1
                Next hop type: Indirect, Next hop index: 0
                Address: 0x7b40434
                Next-hop reference count: 9, key opaque handle: 0x0, non-key opaque handle: 0x0
                Source: 10.1.255.6
                Next hop type: Router, Next hop index: 515
                Next hop: 10.1.23.2 via ge-0/0/2.0, selected
                Label-switched-path pe1-abr
                Label operation: Push 299824, Push 299952, Push 299808(top)
                Label TTL action: prop-ttl, prop-ttl, prop-ttl(top)
                Load balance label: Label 299824: None; Label 299952: Entropy label; Label 299808: None; 
                Label element ptr: 0x93d6c98
                Label parent element ptr: 0x93d6bf8
                Label element references: 1
                Label element child references: 0
                Label element lsp id: 0
                Session Id: 140
                Protocol next hop: 10.1.255.6
                Label operation: Push 299824
                Label TTL action: prop-ttl
                Load balance label: Label 299824: None;
...

Meaning

The output shows the same labels are used for both routes.

Purpose

Verify connectivity and to use for verifying load balancing.

Action

From operational mode, run the ping 172.16.255.7 source 172.16.12.1 rapid count 100 and ping 192.168.255.7 source 192.168.255.1 rapid count 200commands on Router PE1.

user@CE1> ping 172.16.255.7 source 172.16.12.1 rapid count 100
PING 172.16.255.7 (172.16.255.7): 56 data bytes
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
--- 172.16.255.7 ping statistics ---
100 packets transmitted, 100 packets received, 0% packet loss
round-trip min/avg/max/stddev = 5.369/6.070/8.828/0.612 ms

user@CE1> ping 192.168.255.7 source 192.168.255.1 rapid count 200 
PING 192.168.255.7 (192.168.255.7): 56 data bytes
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
--- 192.168.255.7 ping statistics ---
200 packets transmitted, 200 packets received, 0% packet loss
round-trip min/avg/max/stddev = 5.086/5.994/10.665/0.649 ms

Meaning

The output shows pings are successful.

Purpose

Verify load balancing.

Action

From operational mode, run the show mpls lsp ingress statistics command on the ABR.

user@ABR> show mpls lsp ingress statistics
Ingress LSP: 3 sessions
To              From            State     Packets            Bytes LSPname
10.1.255.2      10.1.255.4      Up            300            30000 abr-pe1
10.1.255.6      10.1.255.4      Up            200            20000 abr-pe2
10.1.255.6      10.1.255.4      Up            100            10000 abr-pe2-2
Total 3 displayed, Up 3, Down 0

Meaning

The output shows the first ping from the previous command used LSP abr-pe2-2 and the second ping used LSP abr-pe2.

Purpose

Verify the entropy label is different between the pings that were used.

Action

On Host 1, run the tcpdump -i eth1 -n.

user@Host1# tcpdump -i eth1 -n
...
13:42:31.993274 MPLS (label 299808, exp 0, ttl 63) (label 299952, exp 0, ttl 63) (label 7, exp 0, ttl 63) (label 1012776, exp 0, ttl 0) 
(label 299824, exp 0, [S], ttl 63) IP 172.16.12.1 > 172.16.255.7: ICMP echo request, id 32813, seq 9, length 64
...
13:43:19.570260 MPLS (label 299808, exp 0, ttl 63) (label 299952, exp 0, ttl 63) (label 7, exp 0, ttl 63) (label 691092, exp 0, ttl 0) 
(label 299824, exp 0, [S], ttl 63) IP 192.168.255.1 > 192.168.255.7: ICMP echo request, id 46381, seq 9, length 64

Meaning

The output shows the different value for the entropy label for the two different ping commands.

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 Junos OS CLI User Guide.

To configure Device PE0:

1. On routers with Modular Port Concentrators (MPCs), enable enhanced IP network services.

   content_copy zoom_out_map

   [edit chassis]
   usr@PE0# set network-services enhanced-ip
   

2. Configure the device interfaces.

   content_copy zoom_out_map

   [edit interfaces]
   user@PE0# set ge-0/0/0 unit 0 description PE0->P0
   user@PE0# set ge-0/0/0 unit 0 family inet address 10.0.0.5/24
   user@PE0# set ge-0/0/0 unit 0 family iso
   user@PE0# set ge-0/0/0 unit 0 family inet6 address 2001:db8::1/32
   user@PE0# set ge-0/0/0 unit 0 family mpls 
   user@PE0# set ge-0/0/1 unit 0 description PE0->P1
   user@PE0# set ge-0/0/1 unit 0 family inet address 10.0.0.1/24
   user@PE0# set ge-0/0/1 unit 0 family iso
   user@PE0# set ge-0/0/1 unit 0 family inet6 address 2001:db8::2/32
   user@PE0# set ge-0/0/1 unit 0 family mpls 
   user@PE0# set ge-0/0/2 unit 0 description PE0->CE0
   user@PE0# set ge-0/0/2 unit 0 family inet address 172.16.0.1/30
   user@PE0# set ge-0/0/2 unit 0 family inet6 address 2001:db8::10/32
   user@PE0# set ge-0/0/2 unit 0 family mpls 
   

3. Configure the loopback interface.

   content_copy zoom_out_map

   [edit interfaces]
   user@PE0# set lo0 unit 0 family inet address 192.168.0.1/32
   

4. Configure MPLS and LDP on all interfaces excluding the management interface.

   content_copy zoom_out_map

   [edit protocols]
   user@PE0# set mpls ipv6-tunneling
   user@PE0# set mpls interface all
   user@PE0# set mpls interface fxp0.0 disable 
   user@PE0# set ldp track-igp-metric
   user@PE0# set ldp interface all
   user@PE0# set ldp interface fxp0.0 disable 
   

5. Configure an IGP on the core-facing interfaces.

   content_copy zoom_out_map

   [edit protocols]
   user@PE0# set ospf area 0.0.0.0 interface all
   user@PE0# set ospf area 0.0.0.0 interface fxp0.0 disable
   user@PE0# set ospf area 0.0.0.0 interface lo0.0 passive
   user@PE0# set ospf area 0.0.0.0 interface ge-0/0/1.0 metric 1000 
   user@PE0# set ospf3 area 0.0.0.0 interface all
   user@PE0# set ospf3 area 0.0.0.0 interface fxp0.0 disable
   user@PE0# set ospf3 area 0.0.0.0 interface lo0.0 passive
   user@PE0# set ospf3 area 0.0.0.0 interface ge-0/0/1.0 metric 1000 
   

6. Configure IBGP connections with the other PE devices.

   content_copy zoom_out_map

   [edit protocols]
   user@PE0# set bgp group ibgp type internal
   user@PE0# set bgp group ibgp local-address 192.168.0.1
   user@PE0# set bgp group ibgp family inet labeled-unicast per-prefix-label
   user@PE0# set bgp group ibgp family inet6 labeled-unicast explicit-null
   user@PE0# set bgp group ibgp export nhself
   user@PE0# set bgp group ibgp neighbor 192.168.0.4 description PE1
   user@PE0# set bgp group ibgp neighbor 192.168.0.5 description PE2 
   

7. Configure EBGP connections with the customer devices.

   content_copy zoom_out_map

   [edit protocols]
   user@PE0# set bgp group ebgp type external
   user@PE0# set bgp group ebgp local address 192.168.0.1
   user@PE0# set bgp group ebgp family inet labeled-unicast
   user@PE0# set bgp group ebgp family inet6 labeled-unicast 
   user@PE0# set bgp group ebgp peer-as 64497
   user@PE0# set bgp group ebgp neighbor 172.16.0.2 description CE0 
   

8. Configure the load-balancing policy.

   content_copy zoom_out_map

   [edit policy-options]
   user@PE0# set policy-statement lb then load-balance per-packet
   

9. Configure a next-hop self policy.

   content_copy zoom_out_map

   [edit policy-options]
   user@PE0# set policy-statement nhself then next-hop self 
   

10. Enable the BGP PIC edge feature.

    content_copy zoom_out_map

    [edit routing-options]
    user@PE0# set protect core
    

11. Apply the load-balancing policy.

    content_copy zoom_out_map

    [edit routing-options]
    user@PE0# set forwarding-table export lb  
    

12. Assign the router ID and autonomous system (AS) number.

    content_copy zoom_out_map

    [edit routing-options]
    user@PE0# set router-id 192.168.0.2
    user@PE0# set autonomous-system 64496
    

Purpose

Confirm that BGP PIC edge is working.

Action

From Device PE0, run the show route extensive command.

user@PE0> show route 192.168.1.5 extensive
inet.0: 236941 destinations, 630411 routes (236940 active, 0 holddown, 1 hidden)
20.1.1.1/32 (3 entries, 2 announced)
        State: <CalcForwarding> 
TSI: 
KRT in-kernel 192.168.1.5/24 -> {indirect(1048574), indirect(1048575)}         
        @BGP    Preference: 170/-101                 
                Next hop type: Indirect, Next hop index: 0                 
                Address: 0xafd09d0                 
                Next-hop reference count: 236886                 
                Source: 192.168.0.4                 
                Next hop type: Router, Next hop index: 623                 
                Next hop: 10.0.0.2 via ge-0/0/1.0, selected                 
                Session Id: 0x140                 
                Protocol next hop: 192.168.0.4                 
                Indirect next hop: 0xab3b980 1048574 INH Session ID: 0x144                 
                State: <Active Int Ext ProtectionPath ProtectionCand>                 
                Local AS:   64496 Peer AS:   64496                 
                Age: 1:11       Metric2: 2                  
                Validation State: unverified                  
                Task: BGP_100.192.168.0.5                 
                Announcement bits (1): 6-Resolve tree 2                  
                AS path: 64497 I                 
                Accepted MultipathUnequal                 
                Localpref: 100                 
                Router ID: 192.168.0.5                 
                Indirect next hops: 1                         
												 Protocol next hop: 192.168.0.5 Metric: 2                         
						 						 Indirect next hop: 0xab3b980 1048574 INH Session ID: 0x144                         
												 Indirect path forwarding next hops: 1                                 
																 Next hop type: Router                                 
																 Next hop: 10.0.0.2 via ge-0/0/1.0                                 
																 Session Id: 0x140                         
												 192.168.0.5/32 Originating RIB: inet.0                           
													 Metric: 2                       Node path count: 1                           
													 Forwarding nexthops: 1                                 
																 Nexthop: 10.0.0.2 via ge-0/0/1.0          
      BGP    Preference: 170/-101                 
						  Next hop type: Indirect, Next hop index: 0                 
						  Address: 0xafd0970                 
						  Next-hop reference count: 196735                 
						  Source: 192.168.0.4                 
						  Next hop type: Router, Next hop index: 624                 
						  Next hop: 10.0.0.6 via ge-0/0/0.0, selected                 
						  Session Id: 0x141                 
							Protocol next hop: 192.168.0.4                 
							Indirect next hop: 0xab3c240 1048575 INH Session ID: 0x145                 
							State: <NotBest Int Ext ProtectionCand>                 
							Inactive reason: Not Best in its group - IGP metric                 
							Local AS:   100 Peer AS:   100                 
							Age: 1:05       Metric2: 1001                  
							Validation State: unverified                  
							Task: BGP_100.192.168.0.4                 
							AS path: 200 400 I                 
							Accepted                                 
							Localpref: 100                 
							Router ID: 192.168.0.4                 
							Indirect next hops: 1                         
											Protocol next hop:  192.168.0.4 Metric: 1001                         
											Indirect next hop: 0xab3c240 1048575 INH Session ID: 0x145                         
											Indirect path forwarding next hops: 1                                 
															Next hop type: Router                                 
															Next hop: 10.0.0.6 via ge-0/0/0.0                                 
															Session Id: 0x141                         
											192.168.0.4/32 Originating RIB: inet.0                           
												Metric: 1001                    Node path count: 1                           
												Forwarding nexthops: 1                                 
															Nexthop: 10.0.0.6 via ge-0/0/0.0         
#Multipath Preference: 255                        
									Next hop type: Indirect, Next hop index: 0                 
									Address: 0xd330f90                 
									Next-hop reference count: 304062                 
									Next hop type: Router, Next hop index: 623                 
									Next hop: 10.0.0.6 via ge-0/0/0.0, selected                 
									Session Id: 0x140                 
									Next hop type: Router, Next hop index: 624                 
									Next hop: 10.0.0.2 via ge-0/0/1.0                 
									Session Id: 0x141                 
									Protocol next hop: 192.168.0.4                 
									Indirect next hop: 0xab3b980 1048574 INH Session ID: 0x144 Weight 0x1                     
									Protocol next hop: 192.168.0.5                 
									Indirect next hop: 0xab3c240 1048575 INH Session ID: 0x145 Weight 0x4000                  
									State:   <ForwardinOnly Int Ext>               
									Inactive reason: Forwarding use only                 
									Local AS:   64496                  
									Age: 1:05       Metric2: 2                  
									Validation State: unverified                  
									Task: RT                 
									Announcement bits (1): 0-KRT                  
									AS path: 64497 I  
 

Meaning

Junos OS uses the next hops and the weight values to select a backup path when a link failure occurs. The next-hop weight has one of the following values:

• 0x1 indicates the primary path with active next hops.

• 0x4000 indicates the backup path with passive next hops.

Purpose

Check the forwarding and kernel routing-table state by using the show route forwarding-table command.

Action

From Device PE0, run the show route forwarding-table destination 192.168.1.5 extensive command.

user@PE0> show route forwarding-table destination 192.168.1.5 extensive
  Routing table: default.inet [Index 0]  
Internet:      

Destination:  192.168.1.5/24   
	 Route type: user                     
	 Route reference: 0                   Route interface-index: 0      
	 Multicast RPF nh index: 0                
	 Flags: sent to PFE    
	 Next-hop type: unilist               Index: 1048576  Reference: 7401    
	 Next-hop type: indirect              Index: 1048574  Reference: 2                                         Weight: 0x1     
	 Nexthop: 10.0.0.6   
	 Next-hop type: unicast               Index: 623      Reference: 8       
	 Next-hop interface: ge-0/0/0.0    Weight: 0x1    
	 Next-hop type: indirect              Index: 1048575  Reference: 2                                         Weight: 0x4000   
	 Nexthop: 10.0.0.2   
	 Next-hop type: unicast               Index: 624      Reference: 8       
	 Next-hop interface: ge-0/0/1.0    Weight: 0x4000 

Meaning

Junos OS uses the next hops and the weight values to select a backup path when a link failure occurs. The next-hop weight has one of the following values:

• 0x1 indicates the primary path with active next hops.

• 0x4000 indicates the backup path with passive next hops.