• Tag : 4.21.0F

 
 

Two-way Ports for Tap Aggregation

Description While in Tap Aggregation mode, we support traffic only in one direction through either Tap ports- receiving packets from mirroring/Span ports and optical Tap, or Tool ports – sending out packets to customer devices. This feature allows bidirectional tx and rx capability on a single port in Tap Aggregation mode. Using the new tap-tool switchport mode we can enable both tap and tool configurations on an interface simultaneously. Platform Capabilities DCS-7280R DCS-7280R2 DCS-7500R DCS-7500R2 DCS-7020R Configuration The interface could be configured to allow traffic in both directions by using the following switchport command.    [no|default] switchport mode tap-tool The...
Continue reading →

Egress DSCP Rewrite

Description The feature allows to create a named TC-DSCP mapping that can be applied on an interface. Dscp of routed packets egressing out of the interface will be rewritten according to the map. The rewrite is applicable only for routed traffic. The feature can be configured only for routed ports. Platform compatibility DCS-7500R DCS-7500R2 DCS-7280R DCS-7280R2 We support named TC-DSCP maps on physical interfaces, sub-interfaces, port-channel interfaces and port-channel sub-interfaces in the platforms listed below from EOS release 4.25.2F DCS-7280R3 DCS-7500R3 Configuration Create a Rewrite Map (config)#qos map traffic-class to dscp <mapname> (config-mapname)#traffic-class <tc> to dscp <dscp> (config-mapname)#exit Apply the...
Continue reading →

Introduction to IPv6 Multicast-Routing

Overview IPv6 multicast routing protocols are used to distribute ipv6 datagrams to one or more recipients. IPv6 PIM builds and maintains multicast routing using reverse path forwarding (RPF) based on unicast routing table. IPv6 PIM is protocol-independent and can use routing tables consisting of OSPFv3, IPv6 BGP or static routes, for RPF lookup. MLD is used to discover multicast hosts and maintain group membership on directly attached link. IPv6 multicast-routing has been introduced in the 4.21.0F release and is supported on 7280R and 7500R. Source-specific multicast (SSM) is currently supported on L3 routed port. PIM Sparse Mode In PIM-SM, each...
Continue reading →

L2 Protocol Forwarding

Description Normally, a switch traps L2 protocol frames to the CPU. However, certain use-cases may require these frames to be forwarded. The L2 Protocol Forwarding feature provides a mechanism to control the behavior of L2 protocol frames received on a port or subinterface. L2 Protocol Forwarding was first introduced in EOS-4.21.0F. Since then, the feature has been extended to include different types of interfaces: Level of application of L2 Protocol Forwarding profile Supported since Type-5 Pseudowire Port EOS-4.21.0F All Ethernet Interfaces EOS-4.22.0F Sub-interfaces EOS-4.25.0F LAG Interfaces and LAG Sub-interfaces EOS-4.27.0F (Type-2 platform only) In EOS-4.21.0F, L2 Protocol Forwarding supports forwarding...
Continue reading →

Set TTL for PBRed packets

Description: The feature allows modification of the egress TTL of packets routed via PBR. It allows to modify the TTL of naked IP/IPv6 packet and the TTL of inner header for tunneled packet . The TTL action will be effective only when it is configured along with a set nexthop or nexthop-group action and the nexthop/nexthop-group is resolved and PMF profile is “tc-counters”. Supported Platforms: DCS7500R DCS7500R2 DCS7280R DCS7280R2 Configuration: Enable tc-counters Pmf profile: (config)#hardware tcam (config-hw-tcam)#system profile tc-counters (config-hw-tcam)#exit (config) Create a class-map: (config)#class type pbr match-any className (config-cmap-pbr-className)#match ip access-group aclName (config-cmap-pbr-className)#exit (config)# Create a policy-map: (config)#policy-map type...
Continue reading →

Qos Policy Map Counter

This feature is an extension of Qos Policy. It allows the user to configure Qos Policy Map counters. If a class-map is configured for a policer action then the conformed and non-conformed packet and byte counters are displayed for that class-map. Otherwise the number of packets and bytes hitting the class-map are shown. Platform compatibility DCS-7280E DCS-7020R DCS-7280R DCS-7280R2 DCS-7500R2 Configuration Following command allocates the Counter Engines for Qos which actually count and store the counter value. switch(config)#[no|default] hardware counter feature qos in Arad Fixed system Currently, there is not enough space in TCAM action bank for Qos counter feature. So...
Continue reading →

Tap Aggregation support per-linecard TCAM profile configuration

Description As of EOS-4.21.0F, CLI commands can specify different TCAM profiles for different linecards in Tap Aggregation mixed mode. Before this feature is added, only one TCAM profile can be configured for all linecards in Tap Aggregation mixed mode. To offer more flexibility, it is very desirable to be able to specify different profiles for different linecards.   Platform Capabilities DCS-7500 DCS-7500R DCS-7500R2 Configuration Command to enable TapAgg mode and configure a TCAM profile for a Linecard set: (config-tap-agg)# mode mixed module <Linecard list> [ profile <profile> ]   Command to disable TapAgg mode for a Linecard set: (config-tap-agg)# no/default...
Continue reading →

Multicast Route Counters

This feature provides per multicast route ingress packet and byte counters for multicast routed packets. Platform compatibility DCS-7020R DCS-7280R DCS-7500R Configuration Per multicast route ingress packet and byte counters can be enabled/disabled using the following commands: Arista(config)#[ no ] hardware counter feature multicast ipv4 Create and apply user defined Tcam profile with multicast counter feature db enabled: Example: Create a profile copying from default and modify it Arista(config)#hardware tcam Arista(config-hw-tcam)#profile <profileName> copy default Arista(config-hw-tcam-profileName)#feature counter multicast ipv4 Arista(config-hw-tcam-profileName-feature-counter-multicast-ipv4))#exit Arista(config-hw-tcam-profileName)#no feature mirror ip Arista(config-hw-tcam-profileName)#exit Arista(config-hw-tcam)#system profile <profileName> Status Show command to see per multicast route ingress packet and byte counters: Arista#...
Continue reading →

Tap aggregation QoS handling on tap ports

This article describes how QoS attributes are handled on tap ports as of EOS 4.20.5F. Prior to EOS 4.20.5F, QoS behavior was not enforced for tap aggregation ports, meaning that QoS behaviour for packets passing through the device were not changed. Platform compatibility DCS-7280E DCS-7280R DCS-7500E DCS-7500R DCS-7280R2 Note: QoS is not available on Tap aggregation ports on the DCS-7150. Configuration Trust mode of tap ports Tap ports are put in ‘no qos trust’ mode by default. This means that the QoS marking of an incoming packet is not trusted when determining the QoS attributes of the packet. Therefore the...
Continue reading →

ISIS-SR Global Adj-SID

Introduction This feature allows user to configure adjacency SID of global scope for IS-IS adjacencies. It is an extension to IS-IS Segment Routing static adjacency SID and IS-IS Segment Routing. Global adjacency SID can be configured per address family on any interface. They are configured as index and are advertised as those. This feature is currently supported for P2P interface. Configuration Global adjacency SID can be configured on interface configuration mode with command: [no|default] adjacency-segment <ipv4|ipv6> p2p index <value> global   Arista(config-if-Et1)#adjacency-segment ipv4 p2p ? index  Index to be assigned as Adj-SID for adjacency on this interface label  Label value...
Continue reading →

IS-IS Clear Command: clear isis neighbor

The ‘clear isis neighbor’ command can be used to delete and possibly re-establish IS-IS adjacencies on a box. Issuing the command will bring down some or all adjacencies on the box. These adjacencies may or may not be formed again depending on the protocol state of the devices between which the adjacency was set up. The time taken for this re-establishment if any, will depend on the IS-IS hello interval in use. The adjacencies to be cleared can be on an interface, belong to a specific level and/or be the ones formed with a given neighbor (identified by system-Id or...
Continue reading →

RIB Route Control: FIB Policy

Description RIB Route Control is a collection of mechanisms for controlling how IP routing table entries get used.  FIB Policy provides control over which best paths in the RIB get programmed into the forwarding table (FIB).  This can be used to reduce the number of FIB table entries in order to avoid unplanned exhaustion of hardware forwarding resources. FIB Policy is enabled separately for IPv4 and IPv6 routes.  The policy is specified using a route map, which indicates which routes are allowed for programming in the FIB.  Filtering a route—denying for FIB programming—using FIB policy does not prevent it from...
Continue reading →

CLI Command “show interfaces capabilities default”

Description The show interfaces capabilities default command provides static interface capability information.  This command outputs the default capabilities of the specified interfaces.  By ‘default capabilities’, we mean the set of capabilities unaffected by an external hardware component. For example, a transceiver is an external hardware component. This command’s output does not factor in the capabilities of a transceiver; rather, it only accounts for the capabilities of the system architecture. This command provides the speed, auto-negotiation, error correction, and modulation capabilities (when applicable) of a system’s ports.  This command solves a different problem than its sister command show interfaces capabilities because...
Continue reading →

MPLS Tunnel Support for Traceroute and PMTU Discovery

Description IP traceroute and path MTU (PMTU) discovery both require that routers send ICMP reply messages to the host that invokes each network function.  When the route to the destination host traverses an MPLS label-switched path (LSP), the label switching routers (LSRs) will also need to send ICMP reply messages to the originating host. The MPLS ICMP tunneling feature enables these LSRs to generate ICMP reply messages and deliver them to the originating host using the same LSP on which the frame was received.  Once the frame exits the LSP, it is assumed that the ICMP reply can be routed...
Continue reading →

PTP Monitoring

Description This feature allows users to view most recent history of offset from master, mean path delay and skew values via CLI command and optionally generate syslogs. To generate syslogs, users must configure threshold values for each metric, and whenever the switch sees an unusual data, it will generate a syslog. Recording and displaying recent history is enabled by default so the data is available in show tech-support command, but syslog feature is disabled by default, and user must configure in order to generate them. Platform compatibility This feature is available on all PTP supported products. Configuration Arista(config)#[no] ptp monitor Enables or disables...
Continue reading →

DhcpRelay agent source-address option

Introduction: DHCP relay agent uses one of the addresses configured on the interface as the source IP when relaying messages to the DHCP server. DHCP clients will acquire an address in this subnet. If an interface has multiple addresses configured and it is intended for DHCP clients to acquire addresses in a specific subnet, this particular address can be specified as the source-address for the DHCP server. DhcpRelay agent will use this address as the source IP and update the giaddr and link-address when relaying messages to the corresponding server. Release Updates EOS-4.24.0F Added support for CLI option to configure...
Continue reading →

DHCPv6 Snooping Remote-ID (Option-37) Insertion

Description DHCPv6 relay supports Remote-ID option (37) insertion in relay messages providing the Layer-3 interface name on which DHCPv6 relay is configured. However, the DHCPv6 relay can’t provide Layer-2 information. This feature implements DHCPv6 snooping functionality to intercept DHCPv6 messages and insert Remote-ID option containing Layer 2 information such as VLAN and interface name. Remote-ID option uses the message format described in RFC4649, remote-id field contains DHCP Unique Identifier with LinkLayerAddress (DUID-LL) to achieve uniqueness and sub-option is a string representation of Layer-2 interface name and VLAN number separated by ‘:’ character. For example, a DHCP solicit message received on...
Continue reading →

Ahost

Description Ahost is a generic Fedora-based Linux OS primarily for the purposes of hosting cEOS. It has a 64-bit kernel (EosKernel) and a 32-bit userspace. It is provided as a SWI called Ahost.swi. Platform compatibility DCS-7050CX3-32S DCS-7050SX3-48YC12 DCS-7060CX-32S-ES DCS-7060CX-32S-SSD DCS-7260CX3-64 Configuration To load Ahost on a box running EOS: Copy Ahost.swi to /mnt/flash/ on the box Modify the boot-config (/mnt/flash/boot-config) to point to Ahost.swi: SWI=flash:/Ahost.swi Reboot the box   Installation of Ahost.swi through onie-installer is supported on White Boxes in experimental mode.   Ahost acquires its IP over DHCP. This may result in a different IP address than the one...
Continue reading →

Reload Console Logs

Starting in the EOS-4.21.0F release, reload console logs are available to help in debugging of unexpected reloads. The output of the serial console is available following any reload whether it is planned or unplanned. This output can be used to help debug unexpected reloads. This output complements the existing ‘show reload cause’ command. Platform compatibility As of the EOS-4.21.0F release, reload console logs are supported on the following platforms:   DCS-7020TR-48   DCS-7020TRA-48   DCS-7050SX-72Q   DCS-7050SX2-72Q   DCS-7050TX-72Q   DCS-7060SX2-48YC6   DCS-7160-48TC6   DCS-7160-48YC6   DCS-7260CX3-64   DCS-7280CR2A-30   DCS-7280CR2K-30   DCS-7280QRA-C36S   DCS-7280SR-48C6   DCS-7280SR2-48YC6   DCS-7280SR2A-48YC6  ...
Continue reading →

Support for new OpenConfig paths

Description These are the release notes and configuration guide for the OpenConfig feature in the 4.21.0F release. This release supports reading and streaming various OpenConfig configuration and state models over gNMI (gRPC Network Management Interface), RESTCONF, and NETCONF transports. A subset of the configuration models may also be modified over these transports, see below. All client transactions that modify device configuration provide the same atomicity guarantees that are provided by sessions in the CLI. Platform compatibility All Configuration The following section outlines configuration options for OpenConfig, NETCONF, and RESTCONF transport methods. Native OpenConfig CLI gNMI Transport This starts a gRPC...
Continue reading →

Follow

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

Join other followers: