• Tag : 4.25.1F


Storm control in bits-per-second

Description The existing storm control interface configuration mode CLI commands have been extended to support a new configuration option: bits per seconds (bps). Platform compatibility This new configuration option is supported on: 7300X3 7368 CCS-720XP DCS-7050X3 DCS-7060X4 Configuration For the existing percentage parameter command, traffic policing can be specified as a percentage of the link speed. The following is an example of the existing command: Arista(config-if-Et1)#storm-control broadcast level 50 The above command can be modified to specify the link rate instead by using the “rate” keyword. The configuration command appears as follows: Arista(config-if-Et1)#storm-control broadcast level ? LEVEL Maximum bandwidth percentage...
Continue reading →

Head-End-Replicated DHCP Packets Suppression in VXLAN Network

Description In VXLAN networks, broadcast DHCP requests are head-end-replicated to all VXLAN tunnel endpoints (VTEP). If a DHCP relay helper address is configured on more than one VTEP, each such VTEP relays the DHCP request to the configured DHCP server. This could potentially overwhelm the DHCP server as it would receive multiple copies of broadcast packets originated from a host connected to one of the VTEPs. In Figure 1, a DHCP request from DHCP Client1 is head-end-replicated to all VTEPs. DHCP Relay on VTEPs B and C will also forward this request to the DHCP server, resulting in three copies...
Continue reading →

Support for Multicast NAT

Description Multicast NAT is a feature that performs NAT translations on multicast traffic. It can be configured under SVIs, routed ports, and Port Channels. Feature History Release Update 4.25.1F Egress SNAT and ingress DNAT Egress Twice NAT 4.26.2F Ingress SNAT and egress DNAT Ingress Twice NAT Platform Compatibility DCS-7050X3 series CCS-720XP series Configuration Configuration of Multicast NAT is similar to the existing NAT CLI configuration commands. Below are sample configurations for setting up static multicast NAT translation. 1) Twice NAT on egress interface Ethernet8 for multicast traffic coming from host ingressing on interface Ethernet7. # Enable Routing switch(config)#ip...
Continue reading →

Redistribution of leaked BGP routes into OSPF / OSPFv3

Description This document describes the feature that allows the redistribution of VRF-leaked BGP routes into OSPFv2 and OSPFv3. An optional route-map can be configured to redistribute a particular subset of the leaked BGP routes. Such a route-map can be used to perform matching based on prefix and tag. Platform compatibility This feature is supported on all platforms in multi-agent routing mode. Configuration The command ‘redistribute bgp [ include leaked ] [ route-map <route-map-name> ]’ is used to redistribute VRF-leaked BGP routes into OSPF. Note that configuring ‘redistribute bgp include leaked …’ will result in the redistribution of not only the...
Continue reading →

Route-Map Match Ospf Instance Support

Description This feature adds support for the match ospf instance <instanceID> clause under the route-map config. This clause allows filtering of routes based on the OSPFv2 instance Identifier when redistributing OSPFv2 routes into IS-IS or BGP. Platform compatibility This feature is platform independent. Configuration This feature is configured under route map config. Command: [no|default] match ospf instance <instanceID> switch(config)#route-map rm1 permit 10 switch(config-route-map-rm1)#match ospf ? instance Route instance switch(config-route-map-rm1)#match ospf instance ? <1-65535> OSPF instance identifier Show commands The following command can be used to show information about all the configured match clause in the route maps switch#show route-map route-map...
Continue reading →

Dynamic NAT profiles

Description This article describes Dynamic NAT profile options that are configurable in EOS on DCS-7050X3 and CCS-720XP systems. Two types of profile exist and can be used depending on the use case: NAT Port Translation NAPT (more resources allocated for NAPT) Address-only NAT (more resources allocated for address-only NAT). The two profiles share the same hardware resources so configuring them is a matter of balance of resources. The resource itself will be specifically formatted to suit the type of entry that we want to program into it. Thus two different types of entry won’t fit in the same resource at...
Continue reading →

PTP Monitoring: Filtering

Description Since the introduction of PTP Monitoring feature[1], PTP is capable of recording recent metrics for offset-from-master, skew and mean path delay, and emits a syslog whenever one of the metrics exceeds a certain threshold configured through “ptp monitor threshold <metric> <value>”. Now, instead of emitting a syslog, the PTP agent will be able to drop the bad metric through “ptp monitor threshold drop”. This can provide relief in an environment where an unstable upstream master propagates ptp timestamps to the downstream PTP devices, in turn affecting downstream servers relying on the PTP time. Platform compatibility All platforms where PTP...
Continue reading →

Support for setting DN bit in OSPF

Description This document describes the OSPFv2 feature that allows the setting of “Down” (DN) bit in type-5 and type-7 LSAs. The DN Bit is a loop prevention mechanism implemented when OSPF is used as CE – PE IGP protocol. Its usage in OSPF is explained by RFC4576. By default, OSPF honors the DN-bit in type-3, type-5 or type-7 LSAs in non-default VRFs. This means that LSAs with DN bit set will not be used in SPF calculation, and any routes carried by such LSAs will not be installed in the routing table. DN bit can be set in type-5 and...
Continue reading →

MRU Enforcement

Description MRU (maximum receive unit) enforcement provides the ability to drop frames that exceed a configured threshold on the ingress interface. Platform compatibility DCS-7020 DCS-7280R DCS-7280R2 DCS-7280R3 (Starting in 4.25.1F) DCS-7500R DCS-7500R2 DCS-7500R3 (Starting in 4.25.1F) Change Log 4.25.0F – initial release Support for MRU enforcement on Ethernet, Port-Channel and Sub-interfaces. 4.25.1F Support MRU enforcement on 7280R3 and 7500R3 platforms Support for per-chip MRU drop counter Configuration MRU is configurable per-interface, and can be configured on Ethernet and Port-Channel interfaces. Frames with size greater than the configured MRU value will be dropped on the ingress, and will not be forwarded...
Continue reading →


Get every new post on this blog delivered to your Inbox.

Join other followers: