Vyatta NOS documentation

Learn how to install, configure, and operate Vyatta Network Operating System (Vyatta NOS), which helps to drive our virtual networking and physical platforms portfolio.

Show Page Sections

New features – Broadcom Jericho2 (BCM88690) platform

New CLI commands associated with the new features can be found in configuration and operational commands sections.

QoS – Increase configuration limits for 100G for hardware platforms

This feature increased the limit from 10G to 100G

QoS counters in CLI and MIBs

This feature added CLI statistics for the Jericho2 platform and to the ATT-VROUTER-QOS-MIB.

Support for IPv4/v6 multicast

This feature provides multicast packet replication and forwarding for IPv4 and IPv6 packets in the hardware forwarding path for the Jericho2 platform with the following PIM protocol modes.

  • PIM Dense Mode (DM)
  • PIM Sparse Mode (SM)
  • PIM Source Specific Multicast (SSM)

Control plane policing

This feature implements rate-limiting on the Jericho2 platform with the following selection criteria.

  • Link local multicast packets
  • IPv6 packets with extension headers
  • IPv4 fragmented packets
  • OSPF multicast packets
  • OSPF packets
  • BGP packets
  • ICMPv4 and ICMPv6 packets
  • LDP UDP packets
  • BFD UDP packets
  • RSVP packets
  • PIM packets
  • IP multicast packets
  • UDP packets
  • TCP packets
  • Default – matches all other packets

Routing control plane – BGP PIC edge

The BGP PIC Edge feature builds upon the BGP Best External feature introduced in the 2009 release.

The BGP Best External feature enables selecting and distributing a BGP backup path between PE routers. BGP PIC Edge allows installing the selected BGP backup path into the RIB which is distributed to the Dataplane and installed in hardware. In the event of loss of connectivity detected by BFD leading to the loss of the primary path, the backup path is used instead. BGP Best External only allows one backup path to be selected and installed into the RIB.

BFD support

This feature will program BFD sessions into hardware on the Jericho2, BFD support for the Qumran AX platform was provided in release 2005.

The sessions will start in software, then move to hardware when transitioning to UP state.

There are some limitations on what can be programmed into the hardware. The list of identified HW limitations are the following:

  • IPv4 BFD Authentication not supported
  • Supports a maximum of 8 unique intervals (at a granularity of 3.3 msec)