ExtremeXOS Release Notes Software Version ExtremeXOS 12.5.4 Extreme Networks, Inc. 3585 Monroe Street Santa Clara, California 95051 (888) 257-3000 (408) 579-2800 http://www.extremenetworks.
AccessAdapt, Alpine, Altitude, BlackDiamond, Direct Attach, ExtremeWorks Essentials, Ethernet Everywhere, Extreme Enabled, Extreme Ethernet Everywhere, Extreme Networks, Extreme Standby Router Protocol, Extreme Turbodrive, Extreme Velocity, ExtremeWare, ExtremeWorks, ExtremeXOS, Go Purple Extreme Solution, ExtremeXOS ScreenPlay, ReachNXT, Ridgeline, Sentriant, ServiceWatch, Summit, SummitStack, Triumph, Unified Access Architecture, Unified Access RF Manager, UniStack, XNV, the Extreme Networks logo, the Alp
Contents Chapter 1: Overview................................................................................................................................... 5 Feature Corrections in ExtremeXOS 12.5.4 .............................................................................................................5 Feature Corrections in ExtremeXOS 12.5.3 .............................................................................................................6 Feature Corrections in ExtremeXOS 12.5.2 .....
Contents Resolved Issues in ExtremeXOS 12.5.2.6 .............................................................................................................92 Resolved Issues in ExtremeXOS 12.5.2.5 .............................................................................................................92 Resolved Issues in ExtremeXOS 12.5.1 ................................................................................................................97 ExtremeXOS 12.5.
1 Overview CHAPTER These Release Notes document ExtremeXOS® 12.5.4, which resolves software deficiencies. This chapter contains the following sections: ● Feature Corrections in ExtremeXOS 12.5.4 on page 5 ● Feature Corrections in ExtremeXOS 12.5.3 on page 6 ● Feature Corrections in ExtremeXOS 12.5.2 on page 6 ● New Features and Functionality in ExtremeXOS 12.5.1 on page 11 ● New Hardware Supported in ExtremeXOS 12.5.4 on page 13 ● New Hardware Supported in ExtremeXOS 12.5.
Overview Feature Corrections in ExtremeXOS 12.5.3 This section lists the feature corrections supported in ExtremeXOS 12.5.3 software: ● BFD Static Routes—The Bidirectional Forwarding Detection (BFD) feature can be used to bring down static routes when the host link fails. Without BFD, static routes always remain operationally Up because there is no dynamic routing protocol to report network changes. This can lead to a black hole situation, where data is lost for an indefinite duration.
Overview # Add ports to the VLAN configure vlan v1 add ports 1 configure vlan v2 add ports 2 # Enable ELRP on the create VLANs enable elrp-client configure elrp-client periodic v1 ports all interval 5 log configure elrp-client periodic v2 ports all interval 5 log # Add the ethertype to the protocol configure protocol IP add snap 0x00bb configure protocol decnet add snap 0x00bb VLANs v1 and v2 can then detect the loop on their respective broadcast domains.
Overview ● Revised QoS Meters Description—For ExtremeXOS 12.5.2 and later, the description of QoS meters is changed as follows: On BlackDiamond® 8800 series switches, SummitStack™, and Summit® family switches that are supported by this software release, meters are a per-VLAN resource. For example, if you assign a 50 Mbps meter to a VLAN, the total throughput for all ports in that VLAN is limited to 50 Mbps.
Overview Table/Group Supported Variables Comments extremeVMMappingIngressVPPNa me The ingress policy associated with the VM/MAC address. Note that this may refer to a policy without a corresponding entry in the extremeVMVPPTable if a network policy mapping refers to a nonexistent policy. This would indicate an error in the policy mapping file that is consulted if network authentication fails. When creating an entry in this table, this name must refer to an existing, valid, local policy.
Overview Table/Group ● Supported Variables Comments extremeVMDetectedResultIngress Indicates the result of a VM entry into the network and indicates whether the policy applied or not in ingress direction policyApplied(1) indicates that the named policy was successfuly applied to the port. policyNotApplied(2) indicates that the named policy was not applied to the port. policyInvalid(3) indicates that the named policy was either invalid or missing, and could not be applied to the port.
Overview New Features and Functionality in ExtremeXOS 12.5.1 This section lists the new features and functionality supported in ExtremeXOS 12.5.1 software: ● ACL Match Condition—Based on IEEE 802.1p, this feature provides the ability to create an access list (ACL) based on VLAN tag priority information. ● Access Profile Logging—This feature provides ACL support for traffic reaching the following applications: SNMP, Telnet, SSH2, and HTTP/HTTPS. This is in addition to using policy files to add ACLs.
Overview ● Extreme Network Virtualization (XNV)—The Extreme Network Virtualization (XNV) feature, which is also known as Virtual Machine (VM) tracking, supports VM port movement, port configuration for VMs, and VM inventory on network switches. The XNV feature enables a switch to configure switch ports in response to VM detection and port movement and report VM activity to network management software.
Overview ● Priority Flow Control—This feature provides the functionality to allow traffic associated with certain priorities to be paused while traffic associated with other priorities on the same port continues to flow. ● Round Robin LAG—The round robin algorithm is used to select a member from a LAG to route a packet rather than using a hash algorithm that is based on the L2/l3 address fields of the packet.
Overview New Hardware Supported in ExtremeXOS 12.5.2 No new hardware support is being introduced in ExtremeXOS 12.5.2. New Hardware Supported in ExtremeXOS 12.5.1 The following modules are supported in ExtremeXOS 12.5.
Overview Supported Hardware Refer to the Extreme Networks hardware installation guides for more information about supported hardware. The following tables list the software filenames for the hardware that requires software. BlackDiamond 8800 Series of Switches Component Support BlackDiamond 8800 and BlackDiamond 8806 components supported with ExtremeXOS 12.
Overview Table 1: BlackDiamond 8800 Series of Switches Component Support (Continued) BlackDiamond 8810 and BlackDiamond 8806 Components ExtremeXOS Filenames ExtremeXOS Required BootROM Version 600/900 W AC PSU (Model # 41050/PS 2431) (BlackDiamond 8806 only) N/A 11.6.1.9 N/A 1200 W DC PSU (Model # 60021/PS 2350) N/A 11.3.2.6 N/A NOTE Upgrading the BootROM on a BlackDiamond 8810 or BlackDiamond 8806 switch is not automatic when software is upgraded.
Overview Following are the part numbers for the BlackDiamond 10808 modules with the Rev. D ASIC: Table 3: BlackDiamond 10808 I/O Modules with Part Numbers I/O Module 8000 Level Part No. 9000 Level Part No. G60T 804403-00, after Rev. 16 904015-00 BlackDiamond 10808 60-port 10/100/1000BASET RJ-45 Module 11.2.1.3 804408-00, after Rev. 03 904015-10 BlackDiamond 10808 60-port 10/100/1000BASET RJ-45 Module 11.2.1.3 804402-00, after Rev.
Overview Table 4: BlackDiamond 12800 Series Switches Component Support (Continued) BlackDiamond 12802/12804 Components ExtremeXOS Filenames ExtremeXOS Required BootROM Version GM-20XTR N/A 11.4.1.4 N/A GM-20XT N/A 11.4.1.4 N/A GM-20T N/A 11.4.1.4 N/A PSU Controller N/A 11.4.1.4 2.13 700/1200 W AC PSU (Model # 60020/PS 2336) N/A 11.4.1.4 N/A 1200 W DC PSU (Model # 60021/PS 2350) N/A 11.4.1.
Overview Table 5: BlackDiamond 20800 Series Switch Component Support (Continued) BlackDiamond 20800 Components ExtremeXOS Filenames ExtremeXOS Required MM Basic bd20k-12.5.4.5.xos 12.3.2 uC FPGA: S BootROM PSUCTRL Fan Tray (BlackDiamond 20808) 2.9 0.3.e 0.2.1 3.0 N/A 12.3.2 uC (shown as “Revision”) Fan Tray (BlackDiamond 20804) Firmware Version Required with ExtremeXOS 12.5.3 2.9 N/A 12.4.1 uC (shown as “Revision”) 2.
Overview Summit X250e Component Support Summit X250e components supported with ExtremeXOS 12.5, and the minimum BootROM version required by the switch to support each component, include Table 7: Summit X250e Component Support ExtremeXOS Filenames Minimum ExtremeXOS Required Minimum BootROM Version Summit X250e-24p summitX-12.5.4.5.xos 12.0.1.11 1.0.3.0 Summit X250e-48p summitX-12.5.4.5.xos 12.0.1.11 1.0.3.0 Summit X250e-24t summitX-12.5.4.5.xos 12.0.1.11 1.0.3.
Overview Table 8: Summit X450a and X450e Component Support (Continued) ExtremeXOS Filenames Minimum ExtremeXOS Required Minimum BootROM Version XGM2-2sf (Summit X450a and X450e series only) summitX-12.5.4.5.xos 12.2.1 N/A XGM2-2bt (Summit X450a and X450e series only) summitX-12.5.4.5.xos 12.2.1 N/A Summit X450a and X450e Components Summit X460 Component Support Summit X460 components supported with ExtremeXOS 12.
Overview Summit X650 Component Support Summit X650 components supported with ExtremeXOS 12.5, and the minimum BootROM version required by the chassis to support each component, include: Table 11: Summit X650 Component Support ExtremeXOS Filenames Minimum ExtremeXOS Required Minimum BootROM Version Summit X650-24x summitX-12.5.4.5.xos 12.3.1 1.0.5.5 Summit X650-24t summitX-12.5.4.5.xos 12.3.1 1.0.5.5 VIM1-SummitStack summitX-12.5.4.5.xos 12.3.1 N/A VIM1-10G8X summitX-12.5.4.5.xos 12.3,.
Overview Table 13: BlackDiamond 8800 Series of Switches SFP+ Support (Continued) SFP ExtremeXOS Required LR SFP+ 12.3.1 SFP+ twin coax cable 12.3.1 SFPs supported on the BlackDiamond 10808 switch with ExtremeXOS 12.5, and the minimum ExtremeXOS version required, include: Table 14: BlackDiamond 10808 Switch SFP Support SFP ExtremeXOS Required LX100 SFP 12.0.1.11 SX SFP 10.1.0 LX SFP 10.1.0 ZX SFP 10.1.0 1000BASE-T SFP 11.1.1.9 1000BX SFP 11.6.1.
Overview SFPs supported on the BlackDiamond 20800 switch with ExtremeXOS 12.5, and the minimum ExtremeXOS version required, include: Table 17: BlackDiamond 20800 Switch SFP Support SFP ExtremeXOS Required SX SFP 12.2 LX SFP 12.2 ZX SFP 12.2 LX100 12.2 BXU 12.2 BXD 12.2 SFPs supported on the Summit X150 series switches with ExtremeXOS 12.
Overview SFPs supported on the Summit X350 series switches with ExtremeXOS 12.5, and the minimum ExtremeXOS version required, include: NOTE The XGM2-2sf ports are 10Gb SFP+ ports and do not support 1-Gb optics (PD4-739782255). Table 20: Summit X350 Series Switches SFP/SFP+ (XGM2-2sf Option Card Required) Support SFP ExtremeXOS Required SX SFP 12.0.3.16 LX SFP 12.0.3.16 ZX SFP 12.0.3.16 LX100 SFP 12.0.3.16 1000BX SFP 12.0.3.16 ER SFP+ 12.3.3 SR SFP+ 12.2.1 LR SFP+ 12.2.
Overview Table 21: Summit X450a Switch SFP/SFP+ (XGM2-2sf Option Card Required) Support SFP ExtremeXOS Required 100FX/1000LX SFP 11.6.1.9 • Summit X450a-24x, ports 1 through 20 Note: Not supported on combo ports. LX100 SFP 12.0.1.11 1000BX SFP 11.6.1.9 SFPs supported on the Summit X450e switch with ExtremeXOS 12.5, and the minimum ExtremeXOS version required, include: NOTE The XGM2-2sf ports are 10-Gb SFP+ ports and do not support 1-Gb optics (PD4-739782255).
Overview Table 23: Summit X460 SFP/SFP+ (XGM3-2sf Option Cared Required) Support (Continued) SFP ExtremeXOS Required 10GBASE-SR SFP+ 12.5.1 10GBASE-LR SFP+ 12.5.1 100BASE-FX SFP 12.5.1 100BASE-LX10 SFP 12.5.1 100BASE-FX SFP 12.5.1 SFPs supported on the Summit X480 switch with ExtremeXOS 12.5, and the minimum ExtremeXOS version required, include: Table 24: Summit X480 SFP Support SFP ExtremeXOS Required SX mini-GBIC 12.4.1 LX mini-GBIC 12.4.1 ZX mini-GBIC 12.4.
Overview Table 25: Summit X650 Series Switches SFP/SFP+ Support SFP ExtremeXOS Required 1000 BASE-T SFP, not supported on ports 23, 24 12.3.1 LX100 SFP, not supported on ports 23, 24 12.2.1 ZX SFP, not supported on ports 23, 24 12.2.1 XENPAK Module Support XENPAK modules supported on the BlackDiamond 10808 switch with ExtremeXOS 12.5, and the minimum ExtremeXOS version required, include: Table 26: BlackDiamond 10808 Switch XENPAK Support XENPAK Module ExtremeXOS Required LR 11.1.1.9 ER 11.1.1.
Overview XENPAK modules supported on the Summit X350 switch with ExtremeXOS 12.5, and the minimum ExtremeXOS version required, include: Table 29: Summit X350 Switch XENPAK Support XENPAK Module ExtremeXOS Required SR 12.0.3.16 LR 12.0.3.16 ER 12.0.3.16 LX4 12.0.3.16 ZR 12.0.3.16 XENPAK modules supported on the Summit X450a switch with ExtremeXOS 12.5, and the minimum ExtremeXOS version required, include: Table 30: Summit X450a Switch XENPAK Support XENPAK Module ExtremeXOS Required SR 11.6.
Overview XFP Module Support XFP modules supported on the BlackDiamond 8800 series of switches with ExtremeXOS 12.5, the minimum ExtremeXOS version required include: Table 32: BlackDiamond 8800 Series of Switches XFP Support XFP Module ExtremeXOS Required SR 11.6.1.9 LR 11.6.1.9 ER 12.0.2.25 DWDM 12.1.2.17 ZR 12.1.2.17 Tunable DWDM 12.5.1 XFP modules supported on the BlackDiamond 20800 switch with ExtremeXOS 12.
Overview Table 35: Summit X450a and X450e Series Switch XFP Support (Continued) XFP Module ExtremeXOS Required DWDM 12.5.1 ZR 12.1.2.17 XFP modules supported on the Summit X480 series switch with ExtremeXOS 12.5, the minimum ExtremeXOS version required, and the manufacturers supported include: Table 36: Summit X480 Series Switch XFP Support XFP Module ExtremeXOS Required SR 12.4.1 LR 12.4.1 ER 12.4.1 ZR 12.4.1 DWDM 12.4.1 Tunable DWDM 12.5.
Overview ExtremeXOS Command Line Support The following is true for all Summit X150 and X350 series switches: ● Summit X150 and X350 series switches do not support L3 functionality; this platform does not support CLI commands for L3 functionality. ● Summit X150 and X350 series switches do not support stacking; all CLI commands for stacking are not supported on this platform.
Overview ● Cisco 7910 ● Cisco 7960 ● ShoreTel ShorePhone IP 212k ● ShoreTel ShorePhone IP 560 ● ShoreTel ShorePhone IP 560g ● ShoreTel ShorePhone IP 8000 ● ShoreTel ShorePhone IP BB 24 ● Siemens OptiPoint 410 standard–2 ● Siemens OpenStage 20 ● Siemens OpenStage 40 ● Siemens OpenStage 60 ● Siemens OpenStage 80 Extreme Switch Security Assessment DoS Attack Assessment Tools used to assess DoS attack vulnerability: ● Network Mapper (NMAP) ICMP Attack Assessment Tools used to assess I
Overview ExtremeXOS 12.5.
2 Limits CHAPTER This chapter summarizes the supported limits in ExtremeXOS 12.5.4. Supported Limits Table 37 summarizes tested metrics for a variety of features, as measured in a per-system basis unless otherwise noted. These limits may change but represent the current status. The contents of this table supersede any values mentioned in the ExtremeXOS Concepts Guide. NOTE The term “BlackDiamond 8000 e-series” refers to all BlackDiamond 8500 e-series and 8800 e-series modules.
Limits Table 37: Supported Limits Metric Product Access lists (meters)—maximum number of meters, BlackDiamond 8000 series Limit e-series, group of 24 ports 512 a-series, group of 24 ports 1,024 c-series 2,048 ingress, 256 egress BlackDiamond 8900 series 8900-10G24X-c, group of 12 ports 1,024 ingress, 256 egress 8900 xl-series, 8900-G96T-c 4,096 ingress, 512 egress Summit X150, X250e, X350, X450e group of 24 ports 512 Summit X450a, group of 24 ports 1,024 Summit X460 group of 24 ports 2,
Limits Table 37: Supported Limits (Continued) Metric Product Access lists (slices)—number of ACL slices.
Limits Table 37: Supported Limits (Continued) Metric Product Limit BGP (peers)—maximum number of BGP peers. BlackDiamond 8000 series 256* BlackDiamond xl-series 512 BlackDiamond 10808 512 256 MSM-1XL MSM-1 BlackDiamond 12800 series 256* 512 MSM-5, MSM-5R MSM-6R BlackDiamond 20800 series 512 Summit X450a, X460, X650 128* Summit X480 512 * With default keepalive and hold timers. BGP (peer groups)—maximum number of BGP peer groups.
Limits Table 37: Supported Limits (Continued) Metric Product Limit BGP (non-unique routes)—maximum number of non-unique BGP routes (LPM entries is limited to support TCAM entries on a BlackDiamond 10808). BlackDiamond 8000 series 25,000 BlackDiamond 8900 xl-series 1,000,000 BlackDiamond 10808 MSM-1XL MSM-1 2,000,000 900,000 BlackDiamond 12800 series MSM-5, MSM-5R MSM-6R BGP multicast address-family routes — maximum number of multicast addressfamily routes.
Limits Table 37: Supported Limits (Continued) Metric Product Limit CFM—maximum number of CFM down end points. BlackDiamond 8000 series 32 BlackDiamond 10808 1,000 BlackDiamond 12800 series 1,000 BlackDiamond 20800 series 1,000 Summit series 32 CFM—maximum number of CFM remote end points per up/down end point. All platforms 64 CFM—maximum number of dot1ag ports. All platforms 128 CFM—maximum number of CFM segments.
Limits Table 37: Supported Limits (Continued) Metric Product Limit ESRP domains—maximum number of ESRP domains.
Limits Table 37: Supported Limits (Continued) Metric Product Limit FDB (maximum L2 entries)—maximum number of MAC addresses.
Limits Table 37: Supported Limits (Continued) Metric Product Limit Identity management—--maximum database memory-size. All platforms except BlackDiamond 20800 series 64–49,152 Identity management—--recommended number of identities per switch. All platforms except BlackDiamond 20800 series 100 All platforms except BlackDiamond 20800 series 20 Identity management—-maximum number of dynamic ACL entries configured as an individual dynamic rule, or as an ACL entry in a policy file.
Limits Table 37: Supported Limits (Continued) Metric Product Limit IGMP snooping per VLAN filters— maximum number of VLANs supported in per-VLAN IGMP snooping mode. BlackDiamond 8800 a-series 1,000 BlackDiamond 8800 c-series 2,000 BlackDiamond 8000 e-series 448 BlackDiamond 8900 xl-series 4,000 Summit X150, X250e, X350, X450e 448 Summit X450a, X460, X650 1,000 Summit X480 4,000 IGMPv1/v2 SSM-map entries—maximum number of IGMPv1/v2 SSM mapping entries.
Limits Table 37: Supported Limits (Continued) Metric Product Limit IGMPv3 subscriber—maximum number of IGMPv3 subscribers per switch.
Limits Table 37: Supported Limits (Continued) Metric Product Limit IPv4 ARP entries in hardware with maximum LPM routes—maximum recommended number of IPv4 ARP entries in hardware, with maximum LPM routes present. For BlackDiamond 8800 and Summit series, assumes number of IP route reserved entries is “maximum.
Limits Table 37: Supported Limits (Continued) Metric Product Limit IPv4 routes (LPM entries in hardware)— number of IPv4 routes in hardware.
Limits Table 37: Supported Limits (Continued) Metric Product Limit IPv6 routes (LPM entries in hardware)— maximum number of IPv6 routes in hardware.
Limits Table 37: Supported Limits (Continued) Metric Product IP route sharing (total destinations)— maximum number of unique destinations used by multipath OSPF, OSPFv3, BGP, IS-IS, or static routes. OSPFv3 only applies to BlackDiamond 10808 and BlackDiamond 12800 series, which support ECMP for IPv6.
Limits Table 37: Supported Limits (Continued) Metric Product Limit IS-IS adjacencies—maximum number of supported IS-IS adjacencies.
Limits Table 37: Supported Limits (Continued) Metric Product Limit IS-IS IPv4 L2 routes—recommended maximum number of IS-IS Level 2 routes. BlackDiamond 8000 series 25,000 BlackDiamond 8900 xl-series 120,000 BlackDiamond 10808 MSM-1 MSM-1XL 120,000 180,000 BlackDiamond 12800 series MSM-5 MSM-5R MSM-6R IS-IS IPv4 L1 routes in an L1/L2 router— recommended maximum number of ISIS Level 1 routes in an L1/L2 IS-IS router.
Limits Table 37: Supported Limits (Continued) Metric Product Limit IS-IS IPv6 L2 routes—recommended maximum number of IS-IS Level 2 routes. BlackDiamond 8000 series 10,000 BlackDiamond 8900 xl-series 40,000 BlackDiamond 10808 MSM-1 MSM-1XL 30,000 65,000 BlackDiamond 12800 series MSM-5 MSM-5R MSM-6R IS-IS IPv6 L1 routes in an L1/L2 router— recommended maximum number of ISIS Level 1 routes in a L1/l2 router.
Limits Table 37: Supported Limits (Continued) Metric Product Limit IS-IS IPv4/IPv6 L2 routes in an L2 router—recommended maximum number of IS-IS Level 2 routes in a Level 2 IS-IS router. The numbers documented are based on 50% IPv4 routes and 50% IPv6 routes.
Limits Table 37: Supported Limits (Continued) Metric Product Limit MAC-in-MAC—maximum number of SVLANs. BlackDiamond 10808 (1G DRAM) 2,000 BlackDiamond 12800 series (512 DRAM) 2,000 MAC-in-MAC—maximum number of BVLANs. BlackDiamond 20800 series Mirroring (filters)—maximum number of mirroring filters. BlackDiamond 8000 series 128 BlackDiamond 10808 64 BlackDiamond 12800 series 64 BlackDiamond 20800 series 128 Summit series 128 Mirroring (monitor port)—maximum number of monitor ports.
Limits Table 37: Supported Limits (Continued) Metric Product Limit MPLS LDP ingress LSPs—maximum number of MPLS LSPs that can originate from a switch.
Limits Table 37: Supported Limits (Continued) Metric Product Limit Multicast VLAN registration (MVR)— maximum number of MVR senders per switch (IP multicast compression disabled).
Limits Table 37: Supported Limits (Continued) Metric Product Limit OSPF ECMP—maximum number of equal cost multipath OSPF.
Limits Table 37: Supported Limits (Continued) Metric Product Limit OSPFv3 external routes—recommended maximum number of external routes.
Limits Table 37: Supported Limits (Continued) Metric Product Limit PIM snooping—maximum number of (S,G) entries programmed in the hardware (IP multicast compression disabled). BlackDiamond 8800 c-series 2,048c BlackDiamond 8000 e-series 500c BlackDiamond 8900 series 8900-10G24X-c modules 8900-G96T-c modules 8900 xl-series PIM snooping—maximum number of (S,G) entries programmed in the hardware (IP multicast compression enabled).
Limits Table 37: Supported Limits (Continued) Metric Product Limit PIM—maximum routes—maximum number of (S,G) entries installed in the hardware (IP multicast compression enabled).
Limits Table 37: Supported Limits (Continued) Metric Product Private VLANs—maximum number of subscribers. Assumes a minimum of one port per network and subscriber VLAN. BlackDiamond 8800 a-, c-, e-, xl-series with eight modules of 48 ports 8900-G96T-c modules Limit 383 767 BlackDiamond 10808 1,400 BlackDiamond 12800 series 1,400 Summit series One less than the number of available user ports Private VLANs—maximum number of private VLANs with an IP address on the network VLAN.
Limits Table 37: Supported Limits (Continued) Metric Product Limit RIP interfaces on a single router— recommended maximum number of RIP routed interfaces on a switch.
Limits Table 37: Supported Limits (Continued) Metric Product Limit RSVP-TE profiles—maximum number of profiles. BlacDiamond 8900 xl-series 1,000 BlackDiamond 10808 1,000 BlackDiamond 12800 R-series 1,000 BlackDiamond 20800 series 1,000 Summit X460, X480 1,000 BlacDiamond 8900 xl-series 64 BlackDiamond 10808 64 BlackDiamond 12800 R-series 64 BlackDiamond 20800 series 64 Summit X460, X480 64 Spanning Tree (maximum STPDs)— maximum number of Spanning Tree Domains on port mode EMISTP.
Limits Table 37: Supported Limits (Continued) Metric Product Limit Static MAC multicast FDB entries— maximum number of permanent multicast MAC entries configured into the FDB. BlackDiamond 8000 a-, c-, e-, xl-series 1,024 BlackDiamond 10808 1,024 BlackDiamond 12800 series 1,024 Summit X150, X350, X250e, X450a, X450e, X460, X480, X650 1,024 Syslog servers—maximum number of simultaneous syslog servers that are supported.
Limits Table 37: Supported Limits (Continued) Metric Product Limit VLANs—maximum number of virtual ports. BlackDiamond 12804 50,029 BlackDiamond 20800 series 50,029 VLANs (Layer 2)—maximum number of Layer 2 VLANs. All platforms 4,094 VLANs (Layer 3)—maximum number of Layer 3 VLANs. All platforms 512 VLANs (maximum active port-based)— number of simultaneously active portbased VLANs.
Limits Table 37: Supported Limits (Continued) Metric Product Limit VPLS: MAC addresses in an H-VPLS network—maximum number of MAC address learned by a switch in an evenly distributed hierarchical VPLS BlackDiamond 10808 60,000 BlackDiamond 12800 R-series 60,000 BlackDiamond 8900 xl-series 524,288 (up to)b Note: Increasing the number of spokes per VPLS will decrease the maximum number of MAC addresses that can be learned.
Limits Table 37: Supported Limits (Continued) Metric Product VRRP (maximum instances)—maximum number of VRRP instances for a single switch. BlackDiamond 8800 c-series MSM-48c Limit 256 BlackDiamond 8900 xl-series 8900-MSM128 256 BlackDiamond 20800 series 256 All other platforms with Advanced Edge license or higher 128 VRRP (maximum VRID)—maximum number of unique VRID numbers per switch.
Limits Table 37: Supported Limits (Continued) Metric Product Limit XNV database entries—maximum number of VPP database entries (combination of local and network VPPs). All platforms 2,048 XNV local VPPs—maximum number of XNV local VPPs.e All platforms XNV network VPPs—maximum number of XNV network VPPs.e All platforms Ingress Egress Ingress Egress 2,048 512 2,048 512 a. b. c. d. The table shows the total available; see the note included in PD3-77983510.
3 Open Issues, Known Behaviors, and Resolved Issues CHAPTER This chapter describes items needing further clarification and behaviors that might not be intuitive. It also includes the items that have been resolved. This chapter contains the following sections: ● Open Issues on page 69 ● Known Behaviors on page 85 ● Resolved Issues In ExtremeXOS 12.5.4 on page 87 ● Resolved Issues in ExtremeXOS 12.5.3 on page 89 ● Resolved Issues in ExtremeXOS 12.5.
Open Issues, Known Behaviors, and Resolved Issues Table 38: Open Issues, Platform-Specific and Feature PDs (Continued) PD Number Description PD4-723933144 After adding a sub-VLAN to a super-VLAN on a Summit X450 switch, the following message is displayed: : ACL filter hardware full for unit 1 PD4-2110742669 When using SCP to transfer files to an Extreme switch, the transfer fails with an "incomplete command" error.
Open Issues, Known Behaviors, and Resolved Issues Table 38: Open Issues, Platform-Specific and Feature PDs (Continued) PD Number Description PD4-1883558321 When using IdMgr, the configure identity-management add port all command is not enabling IdMgr on any ports. Workaround: Use the configure identity-management add port command to enable IdMgr on ports.
Open Issues, Known Behaviors, and Resolved Issues Table 38: Open Issues, Platform-Specific and Feature PDs (Continued) PD Number Description PD3-132508261 When issuing the enable jumbo-frame port all command on a BlackDiamond 8800, the MTU size for the VLAN is not configured. Sending 5,000 byte traffic works correctly. However, if you disable jumbo-frames on the egress port the error message Packet too big is displayed.
Open Issues, Known Behaviors, and Resolved Issues Table 38: Open Issues, Platform-Specific and Feature PDs (Continued) PD Number Description PD4-1621694181 The following error is seen on a BlackDiamond 10800 series switch when it reboots with a DHCP client configuration. MSM-A: Error while loading "ipBrForward": Workaround: Run the show log match error command again. PD4-1603284873 Route compression is not working properly when a system experiences a TCAM full condition.
Open Issues, Known Behaviors, and Resolved Issues Table 38: Open Issues, Platform-Specific and Feature PDs (Continued) PD Number Description PD4-742951283 An I/O slot fails due to a Tx data memory overflow and generates the following error message: MSM-A: skylerHC-1184: skyler12 on slot 1 (4 errors):TX Data Memory Overflow: reg 0x32 value 0x01000001 wanted (0x00000000) got (0x01000000) PD4-740255437 Policy files are not refreshed when generating 30,000 rules.
Open Issues, Known Behaviors, and Resolved Issues Table 38: Open Issues, Platform-Specific and Feature PDs (Continued) PD Number Description PD4-1586685991 Traffic is not shaped on a BlackDiamond 20800 series switch if ports are added to a vMAN after configuring an ACL. PD4-1394425195 DUT allows you to create large traffic queues without displaying an error message.
Open Issues, Known Behaviors, and Resolved Issues Table 38: Open Issues, Platform-Specific and Feature PDs (Continued) PD Number Description PD4-506754505 When creating a dynamic egress ACL to deny all traffic, the traffic still hits the ARP reply counter but not denying the packets. PD4-450852442 When configuring an ACL and using the keyword denyAll in the create accesslist command, the action is not stopping the ARP reply packets.
Open Issues, Known Behaviors, and Resolved Issues Table 38: Open Issues, Platform-Specific and Feature PDs (Continued) PD Number Description PD4-847978862 A monitor port does not come up after enabling a port after a DUT is rebooted with a disabled monitor port. The following error is displayed while rebooting: MM-A: voyagerCardPowerEnabl e:1144:- Invalid System mode information returned from dm. dmGetSystemMode () = 33 08/15/2009 16:47:02.47 < Erro:HAL.Card.
Open Issues, Known Behaviors, and Resolved Issues Table 38: Open Issues, Platform-Specific and Feature PDs (Continued) PD Number Description PD4-1867670001 VM-tracking synchronization status is complete before all policy files are downloaded to a switch. PD4-1857577536 A switch shows the SSH status as "Module not loaded" when upgrading the switch from ExtremeXOS 12.1.5.1 to v1252b0-br-ssh-license-1 with Extreme Networks SSH software module (ssh.xmod) license file.
Open Issues, Known Behaviors, and Resolved Issues Table 38: Open Issues, Platform-Specific and Feature PDs (Continued) PD Number Description PD4-749682632 You cannot run the configure port auto on command on XGM2-2bt ports. PD3-127401831 On a Summit X250e platform with 128 VRRP instances that are advertised for 100 milliseconds, the feature "don't preempt" is not working properly.
Open Issues, Known Behaviors, and Resolved Issues Table 38: Open Issues, Platform-Specific and Feature PDs (Continued) PD Number Description PD4-1799417357 Process snmpMaster is terminated with signal 11 in a Summit X460 stack. PD4-1561059387, PD4-697651413 Error messages are generated when trying to over-subscribe the bandwidth for an operationally up RSVP-TE LSP.
Open Issues, Known Behaviors, and Resolved Issues Table 38: Open Issues, Platform-Specific and Feature PDs (Continued) PD Number Description PD4-1937523122 In ExtremeXOS 12.5, BGP with graceful restart enabled functions as graceful restart "aware-only" when operating with an ExtremeXOS 12.6 BGP with graceful restart configuration.
Open Issues, Known Behaviors, and Resolved Issues Table 38: Open Issues, Platform-Specific and Feature PDs (Continued) PD Number Description PD4-476351932 Performing a restart process mpls or restart process ospf on a spoke node in an HVPLS setup causes the Label Distribution Protocol (LDP) peer to go down with the core node. Workaround: Disable and enable MPLS.
Open Issues, Known Behaviors, and Resolved Issues Table 38: Open Issues, Platform-Specific and Feature PDs (Continued) PD Number Description PD4-521915271 The Internet Group Management Protocol (IGMP) group reports may occasionally change from Version 2 to Version 3. PD4-339945634 When a load-sharing group is a member of a mirrored VLAN, packets ingressing on the member of the load-sharing group in the mirrored VLAN should be mirrored.
Open Issues, Known Behaviors, and Resolved Issues Table 38: Open Issues, Platform-Specific and Feature PDs (Continued) PD Number Description QoS PD3-67431351 Configuring an ingress traffic queue and an egress traffic queue association to multiple ports in sequential order generates the following error: Egress queue already associated to this ingress queue Configuration failed on backup MSM, command execution aborted! RIP PD4-1650568630 A RIP/RIPng process crash occurs when scaling ESRP for 128 domains
Open Issues, Known Behaviors, and Resolved Issues Table 38: Open Issues, Platform-Specific and Feature PDs (Continued) PD Number Description WAN PHY PD3-101226461 When show wan-phy commands are run on non WAN PHY ports, the ports display the headers. It should only display the error wan command is not supported on non-wanphy port 25. Known Behaviors The following are limitations in ExtremeXOS system architecture that have yet to be resolved.
Open Issues, Known Behaviors, and Resolved Issues Table 39: Known Behaviors, Platform-Specific and Feature PDs (Continued) PD Number Description ACL PD3-77983510 Summit X450a and Summit X450e series switches and BlackDiamond 8800 a-series and e-series modules provide more powerful ACL capabilities. Because of this, the amount and complexity of ACL rules will naturally impact the time needed to process and apply the ACL rules to the switch. This will also impact switch bootup time.
Open Issues, Known Behaviors, and Resolved Issues Resolved Issues In ExtremeXOS 12.5.4 The following issues were resolved in ExtremeXOS 12.5.4. ExtremeXOS 12.5 includes all fixes up to and including ExtremeXOS 11.1.4.4, ExtremeXOS 11.2.3.3, ExtremeXOS 11.3.4.5, ExtremeXOS 11.4.4.7, ExtremeXOS 11.5.2.10, ExtremeXOS 11.6.5.3, ExtremeXOS 12.0.5, ExtremeXOS 12.1.5, ExtremeXOS 12.2.2, ExtremeXOS 12.3.5, and ExtremeXOS 12.4.4. For information on those fixes, see the release notes for the specific release.
Open Issues, Known Behaviors, and Resolved Issues Table 40: Resolved Issues, Platform-Specific and Feature PDs (Continued) PD Number Description BlackDiamond 8800 Series Switches PD4-1956113551 On a BlackDiamond 8800 series switch, CFM and STP packets generated by the switch are not sent out from the ports configured as PVLAN "translated" ports.
Open Issues, Known Behaviors, and Resolved Issues Table 40: Resolved Issues, Platform-Specific and Feature PDs (Continued) PD Number Description Spanning Tree Protocol PD4-2012749890, PD4-1780972901 Renaming a VLAN and deleting the STP domain to which it has an auto-bind relation, auto-binding it to a new STP domain displays the following error: Error: Cannot enable auto-bind for vlan v2 to STP domain s2, it is the carrier vlan of STP domain s1 PD4-2094536435, PD4-2093639778 After making STP configura
Open Issues, Known Behaviors, and Resolved Issues Table 41: Resolved Issues, Platform-Specific and Feature PDs (Continued) PD Number Description PD4-1957143110, PD4-1034683284 You cannot load a script using a flow-redirect configuration when a VLAN is down. PD4-1947222056, PD4-1937692011 Copying large configuration files through SCP fails. PD4-1917632030, PD4-1857823251 A mismatch between a PIM multicast cache and a hardware binding results in traffic loss.
Open Issues, Known Behaviors, and Resolved Issues Table 41: Resolved Issues, Platform-Specific and Feature PDs (Continued) PD Number Description PD4-1967466724 When a port is added as untagged in a service vMAN and tagged in a service VLAN, traffic received on the service VLAN port may be sent using the untagged service vMAN tunnel. PD4-1969098018 An interoperability issue with a VPLS L2 VPN includes a dot1q tag option on untagged service vMAN tunnels between ExtremeXOS 12.4.3 and ExtremeXOS 12.5.
Open Issues, Known Behaviors, and Resolved Issues Resolved Issues in ExtremeXOS 12.5.2-patch1-1 The following issues were resolved in ExtremeXOS 12.5.2-patch1-1. ExtremeXOS 12.5 includes all fixes up to and including ExtremeXOS 11.1.4.4, ExtremeXOS 11.2.3.3, ExtremeXOS 11.3.4.5, ExtremeXOS 11.4.4.7, ExtremeXOS 11.5.2.10, ExtremeXOS 11.6.5.3, ExtremeXOS 12.0.5, ExtremeXOS 12.1.5, ExtremeXOS 12.2.2, ExtremeXOS 12.3.4, and ExtremeXOS 12.4.2.
Open Issues, Known Behaviors, and Resolved Issues Table 44: Resolved Issues, Platform-Specific and Feature PDs (Continued) PD Number Description PD4-1820555257, PD4-966386662 Local multicast packets (packets destined for a well known reserved multicast address such as 224.0.0.x) are flooded in hardware for BlackDiamond 8800 series and Summit family switches. PD4-1771736843 The xmld process crashes with signal 6 when opening a SOAP session using a session ID larger than 64 characters.
Open Issues, Known Behaviors, and Resolved Issues Table 44: Resolved Issues, Platform-Specific and Feature PDs (Continued) PD Number Description BlackDiamond 8800 Series Switch PD4-1865375583, PD4-1854613879 On a BlackDiamond 8800 series switch, multicast packets are sent directly to the CPU instead of being forwarded in hardware.
Open Issues, Known Behaviors, and Resolved Issues Table 44: Resolved Issues, Platform-Specific and Feature PDs (Continued) PD Number Description PD4-1588054183 Summit X480 switches are not using EXP bits to map VLAN traffic to the correct QoS profile. PD4-1507160161 VPLS Tx and Rx counters are not incrementing on Summit X460 switches. PD4-1820711421, PD4-1572169451 Power cycling a stack node causes a packet drop of 8 seconds in some rare scenarios even though LAG is configured across stack nodes.
Open Issues, Known Behaviors, and Resolved Issues Table 44: Resolved Issues, Platform-Specific and Feature PDs (Continued) PD Number Description IGMP PD4-1757733744, PD4-1453474837 IGMP membership query packets are seen on a port when IGMP is disabled but IGMP snooping is enabled. To resolve this issue, run the disable igmp proxy-query vlan command. MPLS PD4-1704766794, PD4-1687280681 IP multicast packets received on a service vMAN/VLAN may not be flooded through a VPLS tunnel.
Open Issues, Known Behaviors, and Resolved Issues Resolved Issues in ExtremeXOS 12.5.1 The following issues were resolved in ExtremeXOS 12.5.1. ExtremeXOS 12.5 includes all fixes up to and including ExtremeXOS 11.1.4.4, ExtremeXOS 11.2.3.3, ExtremeXOS 11.3.4.5, ExtremeXOS 11.4.4.7, ExtremeXOS 11.5.2.10, ExtremeXOS 11.6.5.3, ExtremeXOS 12.0.5, ExtremeXOS 12.1.5, ExtremeXOS 12.2.2, ExtremeXOS 12.3.4, and ExtremeXOS 12.4.2. For information on those fixes, see the release notes for the specific release.
Open Issues, Known Behaviors, and Resolved Issues Table 45: Resolved Issues, Platform-Specific and Feature PDs (Continued) PD Number Description PD4-1232976130, PD4-1221696686 ExtremeXOS software is unable to upgrade an ExtremeXOS software license to any switch that has a serial number beginning with 0953x-xxxx using the enable license file command. Workaround: Enable the license by running the enable license command.
Open Issues, Known Behaviors, and Resolved Issues Table 45: Resolved Issues, Platform-Specific and Feature PDs (Continued) PD Number Description PD4-1601047171, PD4-1598240578 STP crashes when making topology changes to a domain name containing more than 29 characters. Workaround: Use STP domain names that are less than 30 characters. PD4-1530467581, PD4-1535593829 An untagged packet that is size 1,518 and ingressing an 8900-G48X-xl module is getting slowpath L3 forwarded.
Open Issues, Known Behaviors, and Resolved Issues Table 45: Resolved Issues, Platform-Specific and Feature PDs (Continued) PD Number Description PD4-1552576654, PD4-1508905375 A BlackDiamond 20800 series switch is unable to ping and learn ARP traffic in a vMAN and VLAN interconnected network setup. PD4-1585599449, PD4-1409776545 When receiving a specific CFM packet, the switch displays the following error message: Error: can't read xmlData.
Open Issues, Known Behaviors, and Resolved Issues Table 45: Resolved Issues, Platform-Specific and Feature PDs (Continued) PD Number Description EAPS PD4-1566287981, PD4-1206057921 If EAPS ring ports are added to a VLAN before protecting the VLAN from EAPS, the EAPS secondary port may not be blocking the protected VLAN. PD4-1482379577, PD4-1248684161 The ExtremeXOS CLI does not prevent a user from enabling BOOTP on an EAPS control VLAN.
Open Issues, Known Behaviors, and Resolved Issues Table 45: Resolved Issues, Platform-Specific and Feature PDs (Continued) PD Number Description PD4-1493262737, PD4-1197366638 Ports become active and start forwarding traffic before STP is operational when rebooting. VPLS PD4-1517234959, PD4-1509628441 When sending VPLS traffic for approximately 100 E-LANs, traffic for one of the E-LANs may get lost. ExtremeXOS 12.5.
