Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Routing Protocols

  • AS loop check in BGP Networks (PTX10016)—We have enabled Autonomous systems (AS) path loop check for external BGP (EBGP) and internal BGP (IBGP) sessions by default. The loop check is made in the BGP peer's AS path domain. Use this feature to configure and manage AS path loop detection on Junos devices.

    You can disable AS path loop check for IBGP sessions including all routing instances using the statement no-loop-check statement at the [edit protocols bgp defaults ibgp] hierarchy level.

    [See no-loop-check.]

  • BGP prefix limit based on route target to limit VPN prefixes (PTX10016)—Typically L3VPN deployments limit routes at the customer edge peer level with the prefix-limit configuration for a BGP peer family. We have shifted this control to a central location such as the route reflector or a ASBR so that routes originating at all sites in a VPN are taken into account. BGP maintains and enforces the prefix limit as specified by the route target communities originating at various VPN sites to limit the number of prefixes a BGP peer can advertise or receive to conserve resources.

    [See prefix-limit.]

  • Configure BGP keepalive value independent of holdtimer value (PTX10001-36MR)— BGP uses hold time to terminate unresposive sessions, which is reset each time a BGP message is received on a BGP connection. In the absence of any BGP message a keepalive timer runs that triggers a keepalive message type when it expires. By default, this keepalive timer is one third of the negotiated BGP hold time, if greater than zero. You can now configure the keepalive timer independently of the hold time between 1 second through 21845 seconds. Include the keepalive-time statement at the [edit protocols bgp] hierarchy level.

    [See keepalive-time .]

  • Generate static RT-Constrain route based on community/wildcard (PTX10016)—When the RT-Constrain feature is partially deployed in a network, the resource saving benefit is lost. We have extended the static RT-Constrain feature to generate host static RT-Constrain entries from fully qualified route targets configured in the routing policy. You can assign BGP communities or a wildcard route target on the static RT-Constrain route. You can also configure the static RT-Constrain route's origin AS in the NLRI while retaining the global AS number.

  • IS-IS multi-instance support over a single interface (ACX7020, ACX7024, ACX7100, ACX7332, ACX7348, ACX7509, PTX10001-36MR, PTX10002-36QDD, PTX10004, PTX10008, PTX10016, QFX5130, QFX5220, QFX5230-64CD, QFX5240, QFX5241-32OD, and QFX5700)—We have enhaced the IS-IS multi-instance feature to support multiple IS-IS instances on the same logical interface with instance identifier TLV 7.

    Include the instance-id statement at the [edit protocols isis-instance name hierarchy level.

    [See How to Configure Multiple Independent IGP Instances of IS-IS.]

  • Selectively disable NH validation based on Community/RT/RD (PTX10016)—Define a BGP import policy to selectively disable next hop resolution. The policy action sets the next hop to fictitious instead of indirect next hop and avoids resolving the next hop for routes that match the community specified in the policy.

  • Replace BGP AS path to maintain network interoperability (PTX10008)—Define a routing policy to match and replace a list of autonomous systems (AS) numbers or private AS numbers with the local AS number of the BGP peering session to maintain network interoperability. This configuration works only on AS sequences and not on AS sets. In addition to using external BGP (EBGP), enable internal BGP (IBGP) to leverage this capability in route-reflector scenarios. Include the policy action as-path-replace as-list | private statement at the [edit policy-options policy-statement statement-name then] hierarchy level to activate the feature.

    [See Autonomous Systems for BGP Sessions.]