New in This Document
Summary of Enhancements in FastIron Release 10.0.20b_cd1
Summary of Enhancements in FastIron Release 10.0.20a
|
Feature |
Description |
Reference |
|---|---|---|
| Anycast Gateway with VXLAN | Anycast gateway with Virtual Extensible Local Area Network (VXLAN) allows the same gateway IP addresses to be used across all Virtual Tunnel End Points (VTEPs) in a VXLAN network. This ensures that every VTEP can act as the default gateway for the devices connected to it. | Anycast Gateway with VXLAN |
| BGP EVPN Multihoming1 | For BGP-EVPN Multihoming (MH), a customer device or network (CE) can connect simultaneously to multiple edge nodes. This multi-attachment capability offers redundant, all-active connectivity to the EVPN core network and extends this redundancy across the entire network connected to the core. | BGP EVPN Multihoming |
| Rapid Spanning Tree Protocol (2004 standard) IEEE 802.1w | Support for RSTP (IEEE 802.1D 2004 standard) introduced. ICX switches supported the 2001 standard previously. | Rapid Spanning Tree Protocol |
| Stacking support for MCT on ICX 7550 | Support for MCT on ICX 7550 switches including stacking is introduced | MCT Board Type Compatibility |
| Updates to address defects | Updated: Minor updates on content throughout to address defects. | All chapters |
| Minor editorial updates | Updated: Minor editorial updates were made throughout the Configuration Guide. | All chapters |
Key Features and Enhancements in FastIron 10.0.20
| Feature | Description | Reference |
|---|---|---|
| BGP EVPN | BGP Ethernet Virtual Private Network (EVPN) provides an efficient control plane protocol for VXLAN. When BGP EVPN is configured for a VXLAN, remote Virtual Tunnel End Points (VTEPs) and Virtual Network Identifiers (VNIs) do not need to be manually configured, and remote MAC addresses can be learned via the control plane. VTEPs in a VxLAN network can use BGP EVPN to exchange locally learned Layer 2 and Layer 3 destinations with remote VTEPs. | BGP EVPN VXLAN |
| IPoE S-tag and C-Tag VLANs | When configuring selective Q-in Q tunneling, customer VLANs (CVLANs) can be added or replaced, enhancing traffic management capabilities in environments where complex VLAN handling is required. When Internet Protocol over Ethernet (IPoE) service-tagged (S-tag) and customer-tagged (C-tag) VLANs are enabled, traffic from different clients or tenants can be segregated, ensuring the efficient use of available VLAN IDs and simplifying the network configuration. | Adding or Replacing a Customer VLAN for Q-in-Q Tunneling |
| Layer 2 Trace Route Utility | This feature traces the traffic path through a specified device in a VLAN. | Layer 2 Trace Route Utility |
| Assigning different VLAN IDs to reserved VLANs | The reserved-vlan-map command now allows VLAN 4090
to be re-assigned in addition to VLANs 4091 and 4092. |
Assigning a Different VLAN ID to Default and Reserved VLANs |
| Updates to address defects | Updated: Minor updates on content throughout to address defects. | All chapters |
| Minor editorial updates | Updated: Minor editorial updates were made throughout the Configuration Guide. | All chapters |
- A maximum of two Virtual Tunnel End Points (VTEPs) are supported to participate in multihoming (Dualhoming). ↩