Tag :: IPv4

This document describes the CLI introduced to change the default hardware FEC allocation scheme for IPv4/IPv6 attached routes. By default, level2 hardware FECs are allocated for attached IPv4/IPv6 routes. To change the default hardware FEC allocation scheme, this CLI can be used. 

Tagging traffic with a drop precedence is a method that can be used to differentiate traffic flows over a given

This feature introduces the show bgp evpn sanity ( brief | detail )command. This command displays which EVPN configuration attributes are inconsistent as well as potential errors in the EVPN operational state.

This feature introduces support for scaling both IPv4 and IPv6 hosts on our devices. Existing MDB profiles offer a maximum host scale of 128k with unique MAC rewrites. However, if hosts share the MAC rewrites, the scale can reach up to 204k. To address this issue, we are introducing a new MDB profile that will support a host scale of up to 192k when each host has a unique MAC rewrite. If hosts share the MAC rewrites, the scale can reach up to 256k.

This feature when configured enables users to rewrite the DSCP of the GUE encapsulated header on IP-over-UDP tunnels while preserving the TOS value of the inner IP ( IPv4 / IPv6 ) payload. Starting from software version 4.34.1F, the CLI configuration to enable or disable DSCP preserve globally on the egress interface introduces a clear distinction in the behavior of GUE encapsulation on the core facing interface of the IP-over-UDP tunnels.

This document is an extension to the decap group feature, that allows IPv4 addresses to be configured and used as part of a group. Now we will be able to configure IPv4 prefixes as a decap group.

The document describes an extension of the decap group feature, that allows IPv6 addresses to be configured and used

The document describes an extension of the decap group feature, that allows IPv6 addresses to be configured and used as part of a group. IP-in-IP packets with v6 destination matching a configured decap group IP will be decapsulated and forwarded based on the inner header. That will allow any IP-to-IP packet type to be decapsulated, i.e. IPv4 in IPv4, IPv4 in IPv6, IPv6 in IPv4 and IPv6 in IPv6.

This feature provides multipath router id, a new multipath mode to control the behavior of RPF selection. In the

Multipath color is a new multicast multipath mode for controlling PIM RPF selection. In the default multipath

In order to support PIM/IPv4 multicast routing on EOS switches with Broadcom Tomahawk4 ASICs, multicast support using ALPM is required. This works in both 3-level Algorithmic Longest Prefix Match (ALPM) capabilities and 2-level ALPM.

This document describes the prefix counter feature and is intended for customers who are familiar with and are using VRF selection policies (see linked TOI for details). In short, the prefix counter feature enables traffic matching a VRF selection policy to be counted on a per-prefix/per-route basis. This is limited to IPv4 traffic and prefixes of length 32.