Routing

Hi All,

Just want to know whether we can do or similar as per title subject on MX box? Below is the url example on PTX.

http://www.juniper.net/techpubs/en_US/junos12.2/topics/topic-map/policy-default-packet-transport.html

thanks

Hi,

you can use the very same technique on all Junos platforms. This includes MX.

--
Click the star for kudos if you think I earned it.
If this post solves your problem, please mark this post as "Accepted Solution".

Hi kronicklez,

This is applicable only for PTX platform which has limited PFE/FPC resources to accomodate IPv4/IPv6 prefixes. Hence by default, the BGP routes are not installed in forwarding-table of FPC though we can still see the route in routing-table.

With the knob "install-to-fib", user is allowed to override this default behvaiour and allow IPv4/IPv6 prefix installation in PFE.

These knobs should be hidden in other platform and even if you enable it by typing it completely, you will see message as not-supported like below:

show policy-options policy-statement new
##
## Warning: statement ignored: unsupported platform (mx480)
##
then no-install-to-fib;

Regards

Surya

Hi Surya / Pantunes,

Even it said not supported in MX actually it work or not to achieved the objective as per title? Or do we need to tune the config on MX to achieved the objective.

Thanks and appreciate your feedback.

Hi kronicklez,

If the objective is to have BGP routes active in routing-table (RIB) but then should not be installed in forwarding-table (FIB), then you can define the policy as below:

suryak@MX480> show configuration routing-options forwarding-table
export [ no-fib-alternate ];

suryak@MX480> show configuration policy-options policy-statement no-fib-alternate
term a {
    from {
        protocol bgp;
        neighbor 2.2.2.2;
        route-filter 48.1.2.0/23 exact;
    }
    then reject;
}
term b {
    then {
        load-balance per-packet;
        accept;
    }
}

suryak@MX480> show route receive-protocol bgp 2.2.2.2 table inet.0

inet.0: 51 destinations, 51 routes (50 active, 0 holddown, 1 hidden)
  Prefix		  Nexthop	       MED     Lclpref    AS path
* 48.1.2.0/23             2.2.2.2                      100        I
* 50.0.0.0/8              2.2.2.2                      100        I

suryak@MX480> show route protocol bgp table inet.0

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

48.1.2.0/23        *[BGP/170] 00:05:08, localpref 100, from 2.2.2.2
                      AS path: I, validation-state: unverified
                    > to 10.8.1.2 via ae0.0
                      to 20.8.1.2 via ae1.0
50.0.0.0/8         *[BGP/170] 00:06:45, localpref 100, from 2.2.2.2
                      AS path: I, validation-state: unverified
                    > to 10.8.1.2 via ae0.0
                      to 20.8.1.2 via ae1.0


suryak@MX480> show route forwarding-table destination 48.1.2.0/23 table default
Routing table: default.inet
Internet:
Destination        Type RtRef Next hop           Type Index    NhRef Netif
default            perm     0                    rjct       36     1

suryak@MX480> show route forwarding-table destination 50.0.0.0/8 table default
Routing table: default.inet
Internet:
Destination        Type RtRef Next hop           Type Index    NhRef Netif
50.0.0.0/8         user     0                    indr  1048575     2
                                                 ulst  1048574     6
                              10.8.1.2           ucst      592     2 ae0.0
                              20.8.1.2           ucst      562     4 ae1.0

Regards

Surya

Hi Surya,

Thanks for your kindness. That's what i need. Thanks again.