- Written by Huong Nguyen
- Posted on 11月 13, 2019
- Updated on 10月 12, 2023
- 15249 Views
Support for DHCPv4 (RFC 2131) and DHCPv6 Server (RFC 8415) was added to EOS-4.22.1 and EOS-4.23.0 respectively. EOS DHCP server leverages ISC Kea as backend. The router with DHCP Server enabled acts as a server that allocates and delivers network addresses with desired configuration parameters to its hosts.
- Written by Huong Nguyen
- Posted on 12月 20, 2019
- Updated on 12月 5, 2023
- 13148 Views
Support for DHCPv4 (RFC 2131) and DHCPv6 Server (RFC 8415) was added to EOS-4.22.1 and EOS-4.23.0 respectively. EOS DHCP server leverages ISC Kea as backend. The router with DHCP Server enabled acts as a server that allocates and delivers network addresses with desired configuration parameters to its hosts.
- Written by Lavanya Conjeevaram
- Posted on 6月 29, 2016
- Updated on 4月 22, 2024
- 11211 Views
ECMP Hash visibility CLI determines the output interface for an ECMP set based on the flow parameters supplied by the user. Ingress interface, source IP address, destination IP address and IP protocol are the required parameters. L4 source and destination ports and VLAN identifier are optional, but should be specified if the packet has them.
- Written by Amit Ranpise
- Posted on 11月 11, 2019
- Updated on 5月 10, 2024
- 14375 Views
As described in the Multi-VTEP MLAG TOI, singly connected hosts can lead to suboptimal peer-link utilization. By adding a local VTEP to each MLAG peer, the control plane is able to advertise singly connected hosts as being directly behind a specific local VTEP / MLAG peer.
- Written by Deepak Sebastian
- Posted on 11月 12, 2019
- Updated on 5月 7, 2024
- 11286 Views
This feature adds support for offloading BFD Transmit path to hardware (ASIC) for specific types of BFD sessions. This will improve accuracy of transmit timer implementations for BFD (especially with fast timers like 50 ms) and relieve pressure on the main CPU in scenarios of scale.
- Written by Deepak Sebastian
- Posted on 12月 20, 2019
- Updated on 4月 27, 2020
- 10311 Views
This feature adds support for offloading BFD Transmit path to hardware (ASIC) for specific types of BFD sessions.
- Written by Johnny Chen
- Posted on 11月 12, 2019
- Updated on 3月 7, 2025
- 8446 Views
This feature provides support for per-interface ingress/egress packet/byte counters for both IPv4 and IPv6.
- Written by Pratik Mangalore
- Posted on 12月 14, 2020
- Updated on 2月 4, 2025
- 14601 Views
IP Locking is an EOS feature configured on an Ethernet Layer 2 port. When enabled, it ensures that a port will only permit IP and ARP packets with IP source addresses that have been authorized. As of EOS-4.25.0F release update, IP Locking can run in two modes - IPv4 Locking (which will be referred to as IP Locking) and IPv6 Locking, which can be configured using the commands mentioned in the below sections. IP Locking prevents another host on a different interface from claiming ownership of an IP address through either IP or ARP spoofing.
- Written by Shyam Kota
- Posted on 11月 6, 2019
- Updated on 3月 20, 2025
- 10022 Views
This feature allows setting the desired maximum VOQ latency. Drop probabilities are adjusted in hardware to meet this limit.
- Written by Tom Meng
- Posted on 11月 11, 2019
- Updated on 12月 6, 2023
- 7945 Views
Power management is a way to limit the total available power to be used for Power over Ethernet (PoE) ports. Without power management, the total amount of power that the power supply units (PSU) are able to provide is used. Power management can be used to create power redundancies. For example, if a system has 2 1050W PSUs, the feature can set the total available power to be 800W for PoE. With this configuration, 1 PSU is sufficient to power the system and the unused PSU acts as a backup source, thus giving the system a 1+1 redundancy.
- Written by Josh Pfosi
- Posted on 6月 11, 2019
- Updated on 1月 15, 2025
- 13903 Views
This feature adds support for CPU traffic policy capable of matching and acting on IP traffic which would otherwise