Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Routing Protocols

  • Support for configuring multiple independent IGP instances of IS-IS (PTX10001-36MR, PTX10003, and PTX10008)—You can configure and run multiple independent interior-gateway protocol (IGP) instances of IS-IS simultaneously on a router.

    Note:

    You cannot configure the same logical interface in multiple IGP instances of IS-IS.

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

  • Support for Layer 2 circuit, Layer 2 VPN, and VPLS services with BGP-labeled unicast (PTX10008)—You can configure BGP PIC Edge protection for Layer 2 circuit, Layer 2 VPN, and VPLS (BGP VPLS, LDP VPLS, and FEC 129 VPLS) services with BGP-labeled unicast as the transport protocol. BGP PIC Edge using the BGP-labeled unicast transport protocol helps to protect traffic failures over border nodes (ABR and ASBR) in multidomain networks. Multidomain networks are typically used in metro-aggregation and mobile backhaul network designs.

    [See Load Balancing for a BGP Session.]

  • Support for flexible algorithms in IS-IS for segment routing–traffic engineering (SR-TE) (PTX10001-36MR, PTX10004, and PTX10008)—You can thin-slice a network by defining flexible algorithms that compute paths using different parameters and link constraints based on your requirements. For example, you can define a flexible algorithm that computes a path to minimize the IGP metric and another flexible algorithm to compute a path based on the traffic engineering metric to divide the network into separate planes. This feature enables networks without a controller to configure traffic engineering and utilize segment routing capability of a device.

    To define a flexible algorithm, include the flex-algorithm statement at the [edit routing-options] hierarchy level. To configure a device to participate in a flexible algorithm include the flex-algorithm statement at the [edit protocols isis segment routing] hierarchy level.

    [See Understanding IS-IS Flexible Algorithms for Segment Routing.]

  • Support for relaxing BGP router ID format from /32 to a nonzero ID per RFC 6286 (PTX10001-36MR, PTX10003, PTX10008)—You can establish a BGP connection using a BGP ID that is a 4-octet, unsigned, nonzero integer. The ID must be unique only within the autonomous system (AS) per RFC 6286.

    [See router-id]

  • Support for implicit filter for default EBGP route propagation behavior without policies per RFC 8212 (PTX10001-36MR, PTX10004, and PTX10008)—We’ve introduced a new configuration hierarchy defaults ebgp no-policy at the existing [edit protocols bgp] hierarchy level. The configuration option separates the default policy for receive and advertise into different clauses (accept, reject, or reject-always). As a result, the route propagation behavior of the EBGP speaker varies independently from its default behavior.

    [See Implicit filter for Default EBGP Route Propagation Behavior without Policies and defaults]