ExtremeXOS 15.4.2-Patch1-3 RelNotes PDF

ExtremeXOS Release Notes
Software Version ExtremeXOS 15.4.2-Patch1-3

Published September 2014
120864-00 Rev 11
Published September 2014
120864-00 Rev 11
120864-00 Rev 11
Copyright 2014 Extreme Networks, Inc. All Rights Reserved.
Legal Notices
Extreme Networks, Inc., on behalf of or through its wholly-owned subsidiary, Enterasys Networks,
Inc., reserves the right to make changes in specifications and other information contained in this
document and its website without prior notice. The reader should in all cases consult
representatives of Extreme Networks to determine whether any such changes have been made.
The hardware, firmware, software or any specifications described or referred to in this document
are subject to change without notice.
Trademarks
Extreme Networks and the Extreme Networks logo are trademarks or registered trademarks of
Extreme Networks, Inc. in the United States and/or other countries.
All other names (including any product names) mentioned in this document are the property of
their respective owners and may be trademarks or registered trademarks of their respective
companies/owners.
For additional information about Extreme Networks trademarks, go to: www.extremenetworks.com/
company/legal/trademarks/
Support
For product support, including documentation, visit: www.extremenetworks.com/support/
Contact
Extreme Networks, Inc.
145 Rio Robles
San Jose, CA 19534
Tel: +1 408-579-2800
Toll-free: +1 888-257-3000
3 ExtremeXOS 15.4.2 Release Notes
Table of Contents
Overview.............................................................................................................7
New and Corrected Features in ExtremeXOS 15.4.2 ........................................................................... 8
Re-authentication Using Simple Network Management Protocol (SNMP) for Network
Management System (NMS) Operation ............................................................................................. 8
Supported Platforms ............................................................................................................................ 8
Multi-chassis Link Aggregation GroupLink Aggregation Control Protocol (MLAG-
LACP) Enhancements ................................................................................................................................ 8
New and Corrected Features in ExtremeXOS 15.4.1 ............................................................................ 9
Egress sFlow Sampling ............................................................................................................................. 9
Limitations ...............................................................................................................................................10
Changed CLI Commands ...................................................................................................................10
Energy Efficient Ethernet ......................................................................................................................... 11
CLI Commands ....................................................................................................................................... 11
L3 Interface Scaling .................................................................................................................................... 12
Supported Platforms ........................................................................................................................... 12
Handling a Mixed Stack Configuration ........................................................................................ 12
Viewing Configuration Details ........................................................................................................ 12
OpenFlow Enhancements ....................................................................................................................... 13
Limitations ............................................................................................................................................... 14
Port-Based Link Aggregation Group (Load Sharing) .................................................................. 15
Limitations ............................................................................................................................................... 15
Changed CLI Commands ................................................................................................................... 15
Identity Management (IDM) Role-Based VLANs ........................................................................... 16
Limitations ............................................................................................................................................... 16
Cisco Discovery Protocol (CDP v1) ............................................................................................................ 17
Limitations ............................................................................................................................................... 17
CLI Commands ...................................................................................................................................... 18
Static Ethernet and Time Division Multiplexing (TDM) Multi-Protocol Label Switching
(MPLS) Pseudowire (PW) ....................................................................................................................... 18
Supported Platforms for Static Ethernet Pseudowire .......................................................... 19
Supported Platforms for TDM MPLS Pseudowire ................................................................... 19
CLI Commands ...................................................................................................................................... 19
Selective VLAN Mapping to Virtual Private LAN Service (VPLS) ........................................... 19
Limitations ..............................................................................................................................................20
ExtremeXOS 15.4.2 Release Notes
Table of Contents
4
Pseudowire (PW) Label-Switched Path (LSP) Load Sharing ..................................................20
Supported Platforms ..........................................................................................................................20
Limitations ..............................................................................................................................................20
New CLI Commands ...........................................................................................................................20
Proactive Service Framework ................................................................................................................ 21
Limitations ............................................................................................................................................... 21
New CLI Commands ............................................................................................................................ 21
Changed CLI Commands .................................................................................................................. 22
Non-Extreme Networks Optics Licensing ....................................................................................... 22
Transparent Interconnection of Lots of Links (TRILL) ............................................................... 23
Supported Platforms .......................................................................................................................... 23
Limitations .............................................................................................................................................. 23
New CLI Commands ........................................................................................................................... 25
Dynamic Host Configuration Protocol (DHCP) Smart Relay Support for Secondary IP ad-
dress IDs ........................................................................................................................................................ 28
New CLI Commands ........................................................................................................................... 28
Port-Specific VLAN Tagging ................................................................................................................. 29
Limitations .............................................................................................................................................. 29
Changed CLI Commands ..................................................................................................................30
Access Control List (ACL) Customer VLAN ID (CVID) Match Criteria .................................30
Supported Platforms ..........................................................................................................................30
Limitations ..............................................................................................................................................30
Multi-Protocol Label Switching/Virtual Private LAN Services (MPLS/VPLS) Enhance-
ments ............................................................................................................................................................... 31
Joint Interoperability Test Command (JITC) Compliance ................................................................ 31
New Hardware Supported in ExtremeXOS 15.4 .................................................................................. 32
Hardware No Longer Supported ............................................................................................................... 32
ExtremeXOS Hardware and Software Compatibility Matrix .......................................................... 32
Upgrading to ExtremeXOS .......................................................................................................................... 33
Downloading Supported MIBs .................................................................................................................... 33
Tested Third-Party Products ....................................................................................................................... 34
Tested RADIUS Servers ........................................................................................................................... 34
Tested Third-Party Clients ..................................................................................................................... 34
PoE Capable VoIP Phones ...................................................................................................................... 34
Extreme Switch Security Assessment ..................................................................................................... 35
DoS Attack Assessment .......................................................................................................................... 35
ICMP Attack Assessment ........................................................................................................................ 35
Port Scan Assessment ............................................................................................................................. 35
Service Notifications ....................................................................................................................................... 35
Table of Contents
ExtremeXOS 15.4.2 Release Notes 5
Limits .................................................................................................................37
Open Issues, Known Behaviors, and Resolved Issues................................85
Open Issues ........................................................................................................................................................ 85
Corrections to Open Issues Table ............................................................................................................ 105
Known Behaviors ........................................................................................................................................... 109
Resolved Issues in ExtremeXOS 15.4.2-Patch1-3 .................................................................................118
Resolved Issues in ExtremeXOS 15.4.2 ....................................................................................................121
Resolved Issues in ExtremeXOS 15.4 .......................................................................................................133
ExtremeXOS Documentation Corrections .................................................149
ACLs .................................................................................................................................................................... 149
ELRP ......................................................................................................................................................................151
End of Support for BlackDiamond 12800 Series Switches ............................................................152
Multi-cast VLAN Registration .....................................................................................................................152
Network Login: Web-Based Authentication ........................................................................................152
Policies and Security ......................................................................................................................................153
RADIUS Server Client Configuration .......................................................................................................153
Rate Limiting/Meters .................................................................................................................................... 154
sFlow Sampling ................................................................................................................................................155
ExtremeXOS Concepts Guide Change .............................................................................................155
ExtremeXOS Command Reference Change ..................................................................................155
Show Ports Transceiver Information Command ............................................................................... 156
Configuring VMANs (PBNs) ....................................................................................................................... 156
VRRP ....................................................................................................................................................................157
ExtremeXOS 15.4.2 Release Notes
Table of Contents
6
1
Overview
These release notes document ExtremeXOS
15.4.2-Patch1-3, which adds and corrects

features, adds supported hardware, and resolves software deficiencies.
This chapter contains the following sections:
New and Corrected Features in ExtremeXOS 15.4.2 on page 8
New and Corrected Features in ExtremeXOS 15.4.1 on page 9
Joint Interoperability Test Command (JITC) Compliance on page 31
New Hardware Supported in ExtremeXOS 15.4 on page 32
Hardware No Longer Supported on page 32
ExtremeXOS Hardware and Software Compatibility Matrix on page 32
Upgrading to ExtremeXOS on page 33
Downloading Supported MIBs on page 33
Tested Third-Party Products on page 34
Extreme Switch Security Assessment on page 35
Service Notifications on page 35
Overview
New and Corrected Features in ExtremeXOS 15.4.2
This section lists the feature corrections supported in ExtremeXOS 15.4.2 software:
Re-authentication Using Simple Network Management Protocol (SNMP) for
Network Management System (NMS) Operation on page 8
Multi-chassis Link Aggregation GroupLink Aggregation Control Protocol
(MLAG-LACP) Enhancements on page 8
Re-authentication Using Simple Network Management Protocol
(SNMP) for Network Management System (NMS) Operation
This feature adds a proprietary MIB (EXTREME-MAC-AUTH-MIB) to ExtremeXOS that allows
an NMS to force re-authentication of clients authenticated using MAC-based or dot1x
authentication.
Supported Platforms
All platforms
Multi-chassis Link Aggregation GroupLink Aggregation Control
Protocol (MLAG-LACP) Enhancements
When MLAG LACP is configured, if both MLAG peers go down and then one of them never
boots up, the connection between the remote node and the single MLAG peer stays
logically down. This feature requires the MLAG peer in active state to send LACP PDUs with
its MAC address or configured LACP addresses even when MLAG peering is not established,
thus maintaining the connection between remote node and single MLAG peer.
It is recommended that you configure LACP MAC on both MLAG peers to minimize the
traffic disruption when the second MLAG peer comes up.
Supported Platforms
All platforms
Overview
New and Corrected Features in ExtremeXOS 15.4.1
This section lists the feature corrections supported in ExtremeXOS 15.4.1 software:
Egress sFlow Sampling on page 9
Energy Efficient Ethernet on page 11
L3 Interface Scaling on page 12
OpenFlow Enhancements on page 13
Port-Based Link Aggregation Group (Load Sharing) on page 15
Identity Management (IDM) Role-Based VLANs on page 16
Cisco Discovery Protocol (CDP v1) on page 17
Static Ethernet and Time Division Multiplexing (TDM) Multi-Protocol Label
Switching (MPLS) Pseudowire (PW) on page 18
Selective VLAN Mapping to Virtual Private LAN Service (VPLS) on page 19
Pseudowire (PW) Label-Switched Path (LSP) Load Sharing on page 20
Proactive Service Framework on page 21
Non-Extreme Networks Optics Licensing on page 22
Transparent Interconnection of Lots of Links (TRILL) on page 23
Dynamic Host Configuration Protocol (DHCP) Smart Relay Support for
Secondary IP address IDs on page 28
Port-Specific VLAN Tagging on page 29
Access Control List (ACL) Customer VLAN ID (CVID) Match Criteria on
page 30
Multi-Protocol Label Switching/Virtual Private LAN Services (MPLS/VPLS)
Enhancements on page 31
Egress sFlow Sampling
Previous releases of ExtremeXOS already have sFlow sampling functionality, but it was
restricted to the ingress port traffic. This enhancement of this feature extends the sampling
to the egress traffic as well, both unicast and multicast streams. When egress sFlow
sampling is enabled on a port, the sFlow agent in hardware samples the egress traffic on
that port and these sampled packets are further processed by slow path and are then
passed to the collector. The rate at which the packets are sampled can be controlled
through the user configuration.
Supported Platforms
All Summit series switches
BlackDiamond 8800 series switches
BlackDiamond X8 series switches
Overview
Limitations
Due to the hardware limitations, destination port information is not be supported for
multicast traffic. The output interface index is set to 0.
The egress sFlow sampling does not support de-duplication of packets.
For multicast traffic, the sampling rate, sample pool of the egress sFlow sampled
datagram, is set to zero, because the source ID of the egress sampled multicast packet
is unknown.
For L3 unicast traffic, unmodified packets are sampled and the destination port is
supplied if the L3 traffic is directed within a single port group. When the egress port
and ingress port are on different port groups, then modified packets are sampled and
destination ports are supplied.
For L3 multicast traffic, unmodified packets are sampled and destination port is set to
zero.
Packets dropped due to egress ACL are sampled.
In flooding cases (unicast and multicast), the packets are sampled before packet
replication (if the ingress and member ports are in the same port group, then a single
copy of the packet is sampled even though egress sFlow is enabled on more than one
member port).
In flooding cases (unicast and multicast), if the member ports are spread across
different port group, packets are sampled on a per port group basis.
In flooding cases the least configured sampling rate among the member ports on a port
group is considered as the sample rate (even though if we configure different sample
rates on member ports, egress sampling will be performed based on least configured
sample rate among the member ports on a port group.
Changed CLI Commands
Changes are in bold.
enable sflow ports <port_list> {ingress | egress | both}
Additionally, the following command is modified to show the type of sFlow configured on
the physical interface:
show sflow configuration
Overview
Energy Efficient Ethernet
IT organizations benefit from reducing the power consumption of network equipment,
which in turn reduces energy usage and lowers overall operating costs.
Energy efficient Ethernet (EEE) is used during idle periods by the PHYs to reduce power. If
EEE is not used, the PHY draws full power even when not sending traffic. Enabling EEE
significantly reduces the power consumption of the switch.
Within ExtremeXOS, a PHY/switch combination (BlackDiamond and Summit switches) or a
PHY with AutoGrEEEn capability (E4G cell site routers) is needed to allow EEE to work. In a
typical setup, the PHY and switch communicate when to enter or exit low power idle (LPI)
mode.
AutoGrEEEn technology implements the EEE standard (802.3az specification) directly in
PHYs on E4G cell site routers, enabling EEE mode when interfacing with non-EEEenabled
MAC devices. This allows you to make existing network equipment EEE-compliant by
changing the PHY devices.
Supported Platforms
BlackDiamond X8 10G48T switches
1

Summit 670V-48T switches
1
Summit X440
2
E4G-200 and E4G-400 cell site routers
3
CLI Commands
config port portlist eee enable <on | off>
show port portlist eee
1. EEE is only supported at 10G on this card.
2. All copper ports support EEE.
3. EEE is implemented using AutoGrEEEn.
Overview
L3 Interface Scaling
The L3 interface scaling feature increases the number of routed interfaces from 512 to 2,048
on those switches that can support 2,048 L3 interfaces in hardware. See IP router
interfaces limit under Table 1. This feature allows you to configure L3 (routed) interfaces by
assigning IPv4 and/or IPv6 addresses on VLAN interfaces as follows:
All 2,048 VLAN interfaces are IPv4 routed.
All 2,048 VLAN interfaces are IPv6 routed on selected platforms.
Combination of IPv4 and IPv6 routed VLAN interfaces totaling 2,048.
Supported Platforms
Summit X670 and X770 series switches
1

Handling a Mixed Stack Configuration
The L3 interface scaling feature is not supported on all platforms, so you must consider
stack configurations that contain a mix of supported and unsupported slots. These
configurations are described as follows, and help to dynamically modify the maximum
number of supported L3 interfaces:
The maximum number of L3 interfaces supported is initially computed based on the
configuration of the stack during boot time, and is limited by the slot that can support
the least number of L3 interfaces.
When a slot is hot plugged, it can boot up only if the number of configured L3
interfaces is fewer than what is supported by the slot being inserted. Consequently the
maximum number of L3 interfaces is recomputed across all slots, including the newly
inserted slot.
When a slot is removed from a stack, the maximum number of L3 interfaces supported
by the platform is recomputed excluding the slot that was removed.
Viewing Configuration Details
Use the max router interfaces field of the show vr command to view the
maximum number of router interfaces that are supported.
1. Individual switches and in stacks.
Overview
OpenFlow Enhancements
The ExtremeXOS OpenFlow implementation enables an external OpenFlow Controller to
manipulate data flows within an Extreme Networks switch using a standard protocol to
dynamically configure a flow table abstraction. Flow table entries consist of a set of packet
matching criteria (L2, L3, and L4 packet headers), a set of actions associated with a flow
(flood, modify, forward, divert to controller, etc.), and a set of per flow packet and byte
counters. Flow table entries are implemented using hardware ACLs and FDB entries.
ExtremeXOS supports a subset of OpenFlow classification capabilities, forwarding actions,
and statistics operations.
ExtremeXOS Release 15.4 provides the following OpenFlow enhancements:
Increases the number of supported OpenFlow VLANs. ExtremeXOS 15.3 supported a
single OpenFlow VLAN. ExtremeXOS 15.4 increases this limit to the memory scaling
capabilities of the platform.
Adds VLAN ID editing functions (VLAN ID add, strip, and modify).
Adds source and destination MAC modify actions to the platforms that can support it.
Supports the increased scaling of simple L2 flows by including the use of the FDB table
to support OpenFlow flows.
Adds OpenFlow platform support for BlackDiamond X8 and BlackDiamond 8800 series
switches using select interface cards. OpenFlow works with a single management/
master switch fabric module. Failover with dual management/master switch fabric
modules is not supported.
Provides the ability for multiple OpenFlow controllers to be configured to support high
availability.
Provides for VLANs to be configured for OpenFlow control. The same port on a switch
can support both OpenFlow-managed and non-OpenFlow managed VLANs.
Supported Platforms
ExtremeXOS wide-key ACL platform is required to support OpenFlow because of the
potential for L2, L3, and L4 simultaneous header match conditions. OpenFlow is supported
on the following platforms:
Summit X440, X430, X460, X480, X670, X770 series switches
E4G-200 and 400 cell site routers
BlackDiamond X8 series switches (with a single management module)
BlackDiamond 88008900 xl-series and c-series (with a single master switch fabric
module)
Overview
Limitations
Supported platforms do not implement both packet and byte counters simultaneously
on dynamic ACL entries. Only packet counters are supported in the current
implementation. Counters are not supported with FDB flows.
IN_PORT, FLOOD, NORMAL, and TOS/DSCP editing actions are not supported.
Flows implemented using ACL hardware have platform limitations on the simultaneous
combinations of flow match conditions that can be supported. These limitations are
described in each version of ExtremeXOS Release Notes under the Limits section, and in
the Flow Match combinations table in The ExtremeXOS Concepts Guide. When receiving
a flow match combination that cannot be supported with the platforms ACL hardware,
the switch generates an OpenFlow error message to the controller.
Flows implemented using FDB entries are subject to normal FDB constraints, including
platform dependent table sizes.
Platforms using hardware-accelerated aging do not provide aging based on SA-Mac and
DA-Mac activity at a per-entry level, thus flows may never reach idle timeout expiration
due to SA-Mac activity. The same behavior, never reaching idle timeout expiration, is
also true for L2 flows that are shadowed by ACL flows. Hard timeout functions correctly.
ExtremeXOS OpenFlow supports one physical table, and ingress table. The concept of
an emergency flow table is not supported.
OpenFlow 1.0 describes a secure fail model where a switch immediately removes all of
its flows when it loses connectivity to its controller. ExtremeXOS implements an open
fail mode. In this mode the switch maintains its existing flows after losing connectivity
to a controller. The open fail model is required to support controller high availability
solutions.
High availability for controllers is available through the following two mechanisms:
Some controller clusters present a single IP address. The switch treats the cluster as
a single controller.
Some controller clusters present multiple IP addresses. The switch connects
simultaneously to primary and secondary controller targets and enables the
controllers to manage failover.
OpenFlow, XNV, and IDM are all features that enable an external agent to control
resources on a switch. Due to their interaction models and resource requirements, these
features are mutually exclusive. The ExtremeXOS OpenFlow implementation prevents
these services from being simultaneously configured on the same port.
NOTE
There are other ExtremeXOS features that may not perform optimally when configured
on OpenFlow-enabled VLANs or switch ports with OpenFlow-supported VLANS. We
make no attempt to prevent you from configuring additional services on these interfaces.
Overview
Port-Based Link Aggregation Group (Load Sharing)
Port-based load sharing is a useful tool for addressing certain types of networking
problems involving link aggregation. Network designers should carefully consider both the
advantages and disadvantages of port-based load sharing before deciding to use it in their
networks.
Supported Platforms
1
Limitations
Distribution is limited to 16 aggregator ports.
Port-based load sharing groups cannot be created if any custom load sharing groups
exist on the switch. Likewise, no custom load sharing groups can be created if any port-
based load sharing groups exist on the switch.
On BlackDiamond X8 series switches, distribution keys may only be programmed if the
fabric on the slot is configured to use packet (address-based) hashing. Port-based load
sharing can distribute a maximum of 12 aggregator ports when fabric packet hashing is
not configured.
Changes are bolded.
enable sharing <port> grouping <port_list> {algorithm
[address-based {L2 | L3 | L3_L4 | custom} | port-based]} {lacp
| health-check}
configure sharing port-based key [<load_sharing_key> | default] ports
<port_list>
show sharing port-based keys {ports <port_list>}
show sharing <port> port-based distribution {ports <port_list>}
Overview
Identity Management (IDM) Role-Based VLANs
Previous versions of ExtremeXOS identity management (IDM) require that ports on which
the users/devices are connected can only be added statically to VLANs. There was no
mechanism to classify traffic from an identity (device/ user) to a particular VLAN. For this
new feature, when an identity is detected and the role is determined, ExtremeXOS
dynamically creates the VLAN that is required for the identity to send traffic. If the identity
was deleted, aged out, or is moved, its VLAN is pruned to preserve bandwidth. This feature
leverages MVRP to add uplink ports to the dynamically created VLAN.
This feature is enabled on a per-port basis. IDM requires that the port on which role-based
VLANs are enabled be part of a default or base (not necessarily the default) VLAN as
untagged. This default or base VLAN for the port is the VLAN on which untagged packets
are classified to when no VLAN configuration is available for the MAC address. This default
VLAN should be present before enabling the feature and the port should have already been
added to this VLAN manually before enabling the feature. Enabling this feature on a port
results in a failure if either of the following conditions is true:
IDM is not enabled globally.
IDM is not enabled on the port.
Supported Platforms
All platforms.
Limitations
The IDM role-based VLAN feature cannot be enabled on NetLogin-enabled ports.
Changes are bolded.
configure identity-management role-based-vlan [add | delete] ports
[<port_list> | all]
configure identity-management role <role_name> {tag [<tag> | none]} {vr
[<vr_name> | none]}
Additionally, the show identity-management command now displays role-based
VLAN enabled ports, VLAN tag, and VR Name. Also, the flag is now available to indicate
dynamically added by IDM.
Overview
Cisco Discovery Protocol (CDP v1)
This feature adds support for Cisco Discovery Protocol (CDP v1). CDP v1 is a proprietary
protocol designed by Cisco to help administrators collect information about nearby, and
directly connected, devices. Support of listening, lifting, and periodic transmission of the
CDP v1 PDUs is implemented in this current release.
ExtremeXOS-CDP v1 runs on top of the controlled port of an 802 MAC client. If port access
is being controlled by IEEE 802.1X, the port must be authorized prior to CDP v1 protocol
receive functionality. CDP v1 must also run over an aggregated MAC client, and the CDP v1
protocol information must run over all the physical MAC clients of the aggregated ports.
The spanning tree state of a port does not affect the transmission of CDP v1 PDUs.
Each CDP v1 message contains information identifying the source port as a connection
endpoint identifier. It also contains at least one network address which can be used by a
network management system to reach a management agent on the device (via the
indicated source port). Each CDP v1 message contains a time-to-live value, which tells the
recipient CDP v1 when to discard each element of learned topology information.
By default, ExtremeXOS-CDP v1 feature is disabled.
Supported Platforms
All platforms.
Limitations
Feature applies to CDP version 1 only.
SNMP for this feature is not supported.
While this feature is mainly for network-endpoint devices, it can also be used in
network-network devices that have CDP v1 support.
When port access is controlled by NetLogin, the port must be authorized prior to
receiving CDP v1 packets.
CDP v1 with IPv6 is not supported in this release.
Overview
CLI Commands
[enable | disable] cdp ports [<port_list> | all]
configure cdp frequency <seconds>
configure cdp hold-time <seconds>
configure cdp device-id [<device_id> | system-mac]
clear cdp neighbor [device-id <device_id> | all]
clear cdp counters {ports <port_list>}
show cdp
show cdp ports {<port_list>}
show cdp neighbor {detail}
show cdp counters {ports <port_list>}
Static Ethernet and Time Division Multiplexing (TDM) Multi-
Protocol Label Switching (MPLS) Pseudowire (PW)
Static Multi-Protocol Label Switching (MPLS) pseudowires (PWs) are configurable point-to-
point emulated circuits that have statically configured MPLS PW labels. Static PWs do not
use targeted Label Distribution Protocol (LDP) to negotiate setup and exchange peer
status. They can use any type of MPLS tunnel label-switched paths (LSPs). When used in
conjunction with static routes and static LSPs, no routing protocol, such as Open Shortest
Path First (OSPF) or Intermediate System to Intermediate System (IS-IS), and no label
distribution protocol, such as LDP or Resource Reservation Protocol-Traffic Engineering
(RSVP-TE), are needed to provision and manage static PWs. Management of such a
network can provide a disruptive architectural solution for building large backhaul networks
that are easy to provision, operate, and incrementally expand. Since protocols are no longer
required to set up emulated circuits over MPLS, capabilities are also available to proactively,
or on-demand, verify end-to-end PW connectivity and provide remote endpoint status as
well as provide options for configuring redundant PWs to maintain high network availability.
Statically configured PWs provide greater administrative and management control over the
network. It also allows MPLS PWs to be configured across a network when no label
distribution protocol is running. This can simplify the operational management and reduce
equipment interoperability issues that can arise when deploying routing packet networks.
Provided a tested and proven network management platform is used to centralize the
network configuration and monitoring, operating expense and equipment costs can be
reduced.
Static PWs are created by adding a peer with configured labels. If the configured labels are
not in the allowable range or are already in use by some other statically configured entity,
such as static LSPs, then the command is rejected. Once a static PW is created, the labels
for that PW can be changed without deleting and re-adding the peer. The Circuit Emulation
Service (CES) or L2VPN can remain operational during the change; however, the PW does
go down and come back up.
Overview
Supported Platforms for Static Ethernet Pseudowire
BlackDiamond 8900-XL and -40G
BlackDiamond X8
Summit X770, X670, X480, and X460
Supported Platforms for TDM MPLS Pseudowire
CLI Commands
configure ces ces_name add peer ipaddress ipaddress fec-id-
type pseudo-wire pw_id {static-pw transmit-label
outgoing_pw_label receive-label incoming_pw_label}{lsp
lsp_name}
configure {l2vpn} vpls <vpls_name> add peer ipaddress
<ipaddress> {core} {full-mesh} {static-pw transmit-label
<outgoing_pw_label> receive-label <incoming_pw_label>}
configure l2vpn vpws <vpws_name> add peer ipaddress
<ipaddress> {static-pw transmit-label <outgoing_pw_label>
receive-label <incoming_pw_label>}
configure {l2vpn} vpls <vpls_name> peer <ipaddress> static-pw
[{transmit-label <outgoing_pw_label>}{receive-label
<incoming_pw_label>}]
configure l2vpn vpws <vpws_name> peer static-pw [{transmit-
label <outgoing_pw_label>} {receive-label
<incoming_pw_label>}]
configure mpls labels max-static <max_static_labels>
show mpls label usage
Selective VLAN Mapping to Virtual Private LAN Service (VPLS)
VMAN customer edge ports (CEPs) can filter incoming frames matching a set of VIDs.
Multiple VMANs can have CEP ports that are on the same Ethernet port provided that the
VIDs do not overlap. This feature adds the capability to assign VMANs with CEP ports to a
VPLS.
VMAN is the VLAN stacking (Q-in-Q) feature in ExtremeXOS. There are two types of ports:
access and network. The access port can be unaware or aware of the VLAN. The customer
edge port is the VLAN-aware port of the VMAN. This is also known as selective Q-in-Q.
Supported Platforms
Overview
Limitations
Cannot assign multiple VMANs to a VPLS.
No support for SNMP and/or XML assigning of VMANs with CEP ports to VPLS.
Counter and ingress rate-limiting per CVID.
Pseudowire (PW) Label-Switched Path (LSP) Load Sharing
This feature increases the number of named Label-Switched Paths (LSPs) to be configured
per L2VPN pseudowires (PWs) for use as the transport LSP from 1 to 16. This includes
Resource Reservation Protocol (RSVP-TE) LSPs and static LSPs. This feature also provides
Equal-Cost Multi-path (ECMP) address-based hashing on L2VPN ingress nodes when
transmitting into Link Aggregation Group (LAG).
Supported Platforms
Limitations
Label Distribution Protocol (LDP) LSPs are not supported.
Hardware counters are supported for PW packet counts only (VC LSP), not transport
LSP (outer label).
RSVP-TE FRR is not supported.
ECMP is not supported in slow-path forwarding.
Virtual Private Wire Service (VPWS) is not supported.
ECMP is not supported for flood traffic (unknown unicast, multicast, broadcast). These
packets go over only one LSP.
When multiple LSPs are configured for use by a PW, the hardware counts packets for
the PW only, not individual LSPs associated with the PW.
New CLI Commands
[enable|disable] l2vpn sharing
show l2vpn sharing
NOTE
ACLs may be used instead to implement counter and ingress rate limiting.
Overview
This command is modified to display the status of L2VPN sharing configuration:
show vpls detail
This command is modified to display a message when multiple transport LSPs are
configured for a VPLS PW and LSP sharing is not enabled. This message only appears once
per switch boot:
configure vpls <vplsName> peer <peerAddress> add mpls lsp
<lspName>
Proactive Service Framework
This feature enables the switch to proactively send basic configuration and operation
information to a cloud-hosted collector for the purpose of assisting the Extreme Networks
TAC to resolve customer-reported issues.
Limitations
This feature uses SSL to secure the switch information transmission on the Internet. SSL
functionality is provided by a separate XMOD, called ssh.xmod. If the feature is enabled
and ssh.xmod is not installed, the switch information is transmitted as clear text.
XMOD applications can be dynamically upgraded without restarting the switch, but the
upgraded XMOD version must match the installed ExtremeXOS version.
New CLI Commands
[enable | disable] tech-support collector
configure tech-support add collector [<hostname> |
<ip_address>] tcp-port <port> {vr <vr_name>} {from
<source_ip_address>} {ssl [on | off]}
configure tech-support collector [<hostname> | <ip_address>]
tcp-port <port> {vr <vr_name>} {from <source_ip_address>}
{ssl [on | off]}
configure tech-support delete collector [all | <hostname> |
<ip_address>]
configure tech-support collector [all | <hostname> |
<ip_address>] frequency [bootup [on | off]| error-detected
[on | off]| daily [on {time <hour>} | off]]
configure tech-support collector [all | <hostname> |
<ip_address>] data-set [summary | detail]
run tech-support report {now | in <hours>} {collector [all |
<hostname> | <ip_address>]}
show tech-support collector {<hostname> | <ip_address>}
Overview
show tech-support {[all | <area>]{detail} {logto [file]}}
Non-Extreme Networks Optics Licensing
Starting with ExtremeXOS 15.4, Extreme Networks will begin issuing a
purchasable software license, non-Extreme Optics to use optical devices
from third-party vendors on 40G and 100G ports. Currently this feature only
issues warning messages, but the actual restriction of the ports will be
implemented in a future release.
Like other feature licenses, once the license is applied to a specific switch, that switch is
permanently enabled to allow the unrestricted use of non-Extreme Networks optical
devices. Without the license, ports which are attached to such devices are continuously
restricted.
The devices subject to restriction are:
QSFP+ SR4
QSFP+ LR4
QSFP+ passive copper 0.5m, 1m, 3m, and 5m cable
QSFP+ active optical 5m, 10m, 20m, 50m, and 100m cable
QSFP+ to SFP+ fan 0ut passive copper 3m and 5 m cable - QSFP+ end
The show ports configuration and show ports information detail
commands include flags showing the summary status of non-Extreme Networks optical
devices:
Licensedthe optics license is installed (the 40G+ device is unrestricted, but still
unsupported by Extreme Networks TAC.
Unsupportedthe non-Extreme Networks device is unsupported by Extreme Networks,
but is unrestricted because it does not require a license (1G/10G).
Unlicensedthe non-Extreme Networks 40G+ device may be restricted in a future
release.
NOTE
This feature restriction does not apply to stacking ports.
Overview
Transparent Interconnection of Lots of Links (TRILL)
Transparent Interconnection of Lots of Links (TRILL) is packet encapsulation standard
specifically designed to meet the requirements of the data center. It is similar to Service
Provider Bridging (SPB) and Virtual Private LAN Service (VPLS), but it is different in a few
key areas. Like Multi-Protocol Label Switching (MPLS), TRILL is considered a Layer 2
protocol. From the end station device perspective, the network looks like a large, flat Layer
2 network.
Within the network, bridge traffic is transported across the network using Layer 3 route
forwarding techniques. Similar to SPB and VPLS, the TRILL packet payload includes the
entire Ethernet packet starting with the destination MAC address (DA) field in the Ethernet
header through the Ethernet PDU (but does not include the FCS). TRILL also requires edge
TRILL networking devices, referred to as RBridges, to learn both local MAC address port/
VLAN bindings and remote network MAC address TRILL link/VLAN bindings associated
with egress RBridges.
The TRILL standard is documented in RFC6325.
Supported Platforms
TRILL is supported on the following platforms:
Summit X670 series switches
1
Summit X770 32x40G series switches
1
Limitations
Multicast, flood, and broadcast traffic is limited to 6G per 240G packet processor.
Multicast is not supported. All multicast traffic is transmitted over a single DTree.
Only supports forwarding to one neighbor RBridge per port.
No support for Hybrid TRILL VLANs. A VLAN must either be a TRILL network VLAN or
an access VLAN.
Hybrid ports are not supported (though VLANs can have TRILL network ports and
native 802.1Q Ethernet ports in the same VLAN).
On a transit Rbridge, the VLANs being transported still consume hardware resources
(multicast indices and FDB entries) if VLAN pruning is enabled, even if the VLAN is not
present on the transit Rbridge.
Hitless failover high availability is not supported.
TRILL is supported on the default VR only.
Network recovery times are similar to other routing protocols, such as Open Shortest
Path First (OSPF).
No Operations and Management (OAM) protocol (for example, Bi-directional
Forwarding Detection [BFD]) fault detection is providedonly link LoL and Hello
timeouts,
No RBridge TRILL peering authentication to prevent network spoofing.
1. Individual switches and in stacks.
Overview
IGMP snooping must be disabled on access VLANs before they are added to TRILL
(disable igmp snooping vlan vlan_name).
MLAG and TRILL are not supported on the same VLANs/ports. Enabling MLAG for a
different set of VLANs/ports puts the entire switch in software learning mode, including
TRILL FDB entries.
The following protocol features cannot be configured on a TRILL network VLAN:
IP forwarding
IP routing protocols
IP multicast protocols
MPLS
ESRP
Ring protocols (for example: EAPS, ERPS)
MLAG
Private VLANs
VLAN translation
VLAN aggregation
VMANs
VPLS
VRRP
STP
Customer edge ports (CEP)
Multicast snooping
Any type of tunneling (for example: GRE, IPv6-to-IPv4, IPv6-in-IPv4)
Protocols such as STP, EAPS, ERPS, and ELRP can be configured on TRILL access VLANs
and function correctly in some network configurations. You cannot configure IP addresses
on TRILL access VLANs.
Although not specifically designed to support this, VMAN packets with an outer VMAN tag
of Ethertype 0x8100 can be carried over a TRILL network provided they are treated as
basic Ethernet-tagged packets.
Overview
New CLI Commands
enable trill
disable trill
configure trill add access tag <first_tag> {- <last_tag>}
configure trill delete access tag < first_tag > {- <
last_tag >}
configure trill designated-vlan desired <vlan_name>
configure trill add network vlan <vlan_name>
configure trill delete network vlan [<vlan_name> | all]
create trill nickname <nickname_id> {nickname-priority
<id_priority>} {root-priority <root_priority>} {name
<nickname_string>}
delete trill nickname [<nickname_id> | <nickname_string> |
all]
configure trill nickname [<nickname_id> | <nickname_string>]
{new-nicknname <new_nickname_id>} {nickname-priority
<nickname_id_priority>} {root-priority <new_root_priority>}
{name <new_nickname_string>}
configure trill ports [<port_list> | all] protocol [enable |
disable]
configure trill ports [<port_list> | all] {drb-election
<priority>}
configure trill ports [<port_list> | all] {link-type
[broadcast | point-to-point]}
configure trill ports [<port_list> | all] {metric [<metric> |
automatic]}
configure trill system-id [switch-mac | <system_id>]
configure trill pseudonode [enable | disable]
configure trill inhibit-time <seconds>
configure trill maintenance-mode [enable | disable]
configure trill sharing max-next-hops <max_next_hops>
configure trill mtu size <mtu_size>
configure trill mtu probe [enable | disable]
configure trill mtu probe fail-count <probes_sent>
configure trill tree prune vlans [enable | disable]
configure trill timers lsp [generation-interval
<generation_seconds> | refresh-interval <refresh_seconds> |
lifetime <lifetime_seconds> | transmit-interval
<transmit_milliseconds> | retransmit-interval
<restransmit_seconds> |checksum [enable | disable]]
configure trill timers spf {restart <restart_interval>}
{interval <seconds>}
configure trill timers spf backoff-delay {minimum
<minimum_delay>} {maximum <maximum_delay>}
Overview
configure trill timers hello {multiplier <number>} {interval
[<seconds> | minimal]}
configure trill timers csnp {interval <seconds>}
show trill {detail | counters}
show trill rbridges
show trill neighbor {nickname <nickname> | system-id
<system_id> | mac-address <mac_address>}
show trill neighbor {nickname <nickname> | system-id
<system_id> | mac-address <mac_address>}
show trill ports {<port_list>} {counters {no-refresh |
detail}}
show trill lsdb {lsp-id <lsp_id> | detail}
show trill distribution-tree {[pruning vlan | rpf]
{<dtree_nickname>}}
clear trill counters
ping trill {count <count>} {interval <interval>}
<rbridge_nickname>
traceroute trill <rbridge_nickname>
Overview
The following ExtremeXOS CLI commands have been modified to support TRILL feature.
The syntax of these commands is not changed:
create [fdbentry | fdb] <mac-addr> {vlan} <vlan_name> rbridge
<egress_nickname_id>
delete [fdbentry | fdb] <mac-addr> {vlan} <vlan_name> rbridge
<egress_nickname_id>
clear fdb rbridge [<egress_nickname_id> | all]
show fdb {rbridge [<nickname_id> | all]}
The following command behavior is modified to support the TRILL feature:
If a VLAN is deleted that has TRILL configured, the VLAN is removed from the list of
TRILL-configured VLANs automatically. The TRILL links associated with the VLAN are
immediately torn down.
If learning is disabled on a TRILL access VLAN, learning of egress RBridge to remote
MAC addresses is also disabled. Thus, all unicast traffic is flooded across the traffic since
no learning takes place.
If packet flooding is disabled on a TRILL access VLAN, unknown unicast, broadcast, and
multicast packets are discarded by the RBridge. MAC address to egress RBridge FDB
entries must be configured to forward traffic.
The command show vlan output is modified to include the RBridge flag (h). If TRILL
is enabled on the VLAN, then the h-flag is displayed indicating that the VLAN can peer
with other RBridges in a TRILL network.
The show vlan vlan_name command includes a new line indicating if TRILL is
enabled and whether the VLAN is a TRILL network VLAN or an access VLAN.
The configured FDB aging time applies to RBridge FDB entries.
Creating an FDB tracking entry performs the same function for RBridge FDB entries as
it does for native VLAN FDB entries.
Overview
Dynamic Host Configuration Protocol (DHCP) Smart Relay
Support for Secondary IP address IDs
This feature adds capabilities to the Dynamic Host Configuration Protocol (DHCP) Relay
module in ExtremeXOS to include secondary IP addresses of the VLAN as the gateway
address (giaddr) while relaying a DHCP request. There are two modes of operation:
sequential and parallel.
Supported Platforms
All platforms.
New CLI Commands
configure bootprelay {ipv4 | ipv6} include-secondary
{sequential | parallel | off} {vr <vr_name>}
configure bootprelay {ipv4 | ipv6} {vlan} <vlan_name>
include-secondary {sequential | parallel | off}
unconfigure bootprelay {ipv4 | ipv6} {vlan} <vlan_name>
include-secondary
show bootprelay configuration ipv4
The following show commands are modified to show secondary IP address information:
show bootprelay
show bootprelay ipv6
Overview
Port-Specific VLAN Tagging
This feature allows bridging of frames with different VLAN IDs that have been trunked by
third-party equipment. Frames with different VLAN IDs are treated as belonging to the
same VLAN.
Different VLAN IDs can be on different ports or on the same ports. Different VLAN IDs are
used to accept packets to the VLAN, and the right VLAN ID is used when forwarding the
frames out. The same VLAN ID on different ports can be associated with different VLANs.
Forwarding can also be done over L2VPN when the switches are connected with
pseudowires.
Supported Platforms
BlackDiamond 8800 xl-series only switches
Summit X480, X460, X670, and X770 series switches
Limitations
Protocols are not supported on port-specific VLAN tags. They are prevented from being
configured.
VMANs are not supported.
Configuration input and output are only through the CLI.
IP unicast/multicast forwarding is not supported.
Within a single broadcast domain (VLAN) there is only one MAC address. When a MAC
address is learned on different tag (on the same port or on a different port), it is
considered a MAC move.
Multicast is not supported. Internet Group Management Protocol (IGMP) snooping must
be disabled.
VLAN translation functionality is essentially provided by port-specific VLAN tag, so
port-specific VLAN tag cannot be part of VLAN translation (either as a translation
VLAN, or a member VLAN).
VLANs with a port-specific tag cannot be part of a private VLAN.
Remote-mirroring is not supported on VLANs with port-specific tags.
Overview
configure {vlan} vlan_name add ports [port_list | all]
{tagged {<tag>} | untagged} {{stpd} stpd_name} {dot1d | emistp
| pvst-plus}}
configure {vlan} vlan_name delete ports [all | port_list
{tagged <tag>}]
create fdbentry <mac_addr> vlan <vlan_name> [ports
<port_list> {tagged <tag>} | blackhole]
configure ports port_list {tagged <tag>} vlan vlan_name [limit-
learning number {action[blackhole | stop-learning]} | lock-
learning | unlimited-learning | unlocklearning]
Additionally, the output of the following commands is modified to show VLAN bridging
information:
show vlan
show port info detail
show fdb
Access Control List (ACL) Customer VLAN ID (CVID) Match
Criteria
This access control list (ACL) match criteria feature allows you to specify access-lists that
filter on the inner-VLAN-id field of a double-tagged packet. You can use this match criteria
in the following ways:
Tagged VMAN portsinstalling an ACL matching CVID on ingress or egress matches the
inner VID of a double-tagged packet on a tagged VMAN port.
Untagged VMAN ports with port-CVIDinstalling an ACL matching CVID on ingress
matches the port-CVID inserted into an untagged packet entering this VMAN.
CEP VMAN ports (with or without VPLS)installing an ACL matching CVID on ingress
or egress matches the single VLAN tag on a CEP VMAN port (without translation).
CEP VMAN ports with CVID translation (with or without translation)installing an ACL
matching CVID on ingress matches the post-translation CVID. Installing an ACL
matching CVID on egress matches the post-translation CVID.
Supported Platforms
All Summit series switches
BlackDiamond 8800 and BlackDiamond X8 series switches
Limitations
Platforms that do not support egress ACLs do not support this match criteria on egress.
Using CVID with an egress ACL does not match egress packets matching the port-CVID,
since the CVID has been stripped.
Using CVID does not provide symmetrical results when applied to VMAN CEP ports also
enabling CVID translation. Ingress ACLs match the CVID after ingress translation, while
egress ACLs also match the CVID after egress translation.
Overview
Multi-Protocol Label Switching/Virtual Private LAN Services
(MPLS/VPLS) Enhancements
The following EMS logs allow you to track Multi-Protocol Label Switching (MPLS) protocols,
some label-switched paths (LSPs), pseudowires (PWs) and MPLS interface operational
states. These logs are at the Info level and are not generated in the default log output
(the default level for MPLS is Warning).
LSPs
MPLS.ChgStaticIngrLSPState
MPLS.ChgStaticTrnstLSPState
MPLS.ChgStaticEgrLSPState
MPLS.RSVPTE.ChgIngrLSPState
Pseudowires
MPLS.L2VPN.ChgPWState
MPLS Protocol Interfaces
MPLS.ChgIfState
MPLS.ChgProtoState
MPLS.LDP.ChgProtoState
MPLS.RSVPTE.ChgProtoState
The following commands are modified to show additional information:
show tech mpls
show mpls rsvp-te lsp
Joint Interoperability Test Command (JITC)
Compliance
If you require Joint Interoperability Test Command (JITC) compliance, you can use the
command configure snmp compatibility get-bulk reply-too-big-
action [standard | too-big-error] to change ExtremeXOS from Ridgeline-
compatible mode (standard), the default mode, to JITC-compliant mode (too-big-
error).
Please note that switching to JITC-compliant mode causes Ridgeline to display potentially
unreliable information.
NOTE
CES.TDM.PWUp and CES.TDM.PWDown EMS logs already exist.
Overview
New Hardware Supported in ExtremeXOS 15.4
This section lists the new hardware supported in ExtremeXOS 15.4:
Summit X770 32x40G series switches
Hardware No Longer Supported
The following hardware is no longer supported in ExtremeXOS 15.4:
Summit X150
Summit X250e
Summit X350e
Summit X450e
Summit x450a
Summit X650
ExtremeXOS Hardware and Software
Compatibility Matrix
The ExtremeXOS Hardware and Software Compatibility Matrix provides information about
the minimum version of ExtremeXOS software required to support BlackDiamond and
Summit switches, as well as SFPs, XENPAKs, XFPs, and other pluggable interfaces.
The latest version of the ExtremeXOS Hardware and Software Compatibility Matrix can be
found at:
www.extremenetworks.com/documentation
Overview
Upgrading to ExtremeXOS
See Software Upgrade and Boot Options in the ExtremeXOS Concepts Guide for
instructions on upgrading ExtremeXOS software. Following are miscellaneous hitless
upgrade notes:
Beginning with ExtremeXOS 12.1, an ExtremeXOS core image (.xos file) must be
downloaded and installed on the alternate (non-active) partition. If you try to download
to an active partition, the error message "Error: Image can only be
installed to the non-active partition." is displayed. An ExtremeXOS
modular software package (.xmod file) can still be downloaded and installed on either
the active or alternate partition.
SummitX software is required for E4G cell site routers.
Beginning with ExtremeXOS 15.4, a limited hitless upgrade procedure is supported on
the BlackDiamond X8 and BlackDiamond 8800 series switches For more information,
see the ExtremeXOS Concepts Guide.
Downloading Supported MIBs
The Extreme Networks MIBs are located on the eSupport website under Download
Software Updates, located at:
https://esupport.extremenetworks.com/
Overview
Tested Third-Party Products
This section lists the third-party products tested for ExtremeXOS 15.2.
Tested RADIUS Servers
The following RADIUS servers are fully tested:
MicrosoftInternet Authentication Server
Meetinghouse
FreeRADIUS
Tested Third-Party Clients
The following third-party clients are fully tested:
Windows 7
Windows Vista
Linux (IPv4 and IPv6)
Windows XP (IPv4)
PoE Capable VoIP Phones
The following PoE capable VoIP phones are fully tested:
Avaya 4620
Avaya 4620SW IP telephone
Avaya 9620
Avaya 4602
Avaya 9630
Avaya 4621SW
Avaya 4610
Avaya 1616
Avaya one-X
Cisco 7970
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 standard2
Overview
Siemens OpenStage 20
Extreme Switch Security Assessment
DoS Attack Assessment
Tools used to assess DoS attack vulnerability:
Network Mapper (NMAP)
ICMP Attack Assessment
Tools used to assess ICMP attack vulnerability:
SSPing
Twinge
Nuke
WinFreeze
Port Scan Assessment
Tools used to assess port scan assessment:
Nessus
Service Notifications
To receive proactive service notification about newly released software or technical service
communications (for example, field notices, product change notices, etc.), please go to:
www.extremenetworks.com/services/service_notification_form.aspx
Overview
2
Limits
This chapter summarizes the supported limits in ExtremeXOS 15.4.2-Patch1-3.
Table 1 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.
The scaling and performance information shown in Table 1 is provided for the purpose of assisting
with network design. It is recommended that network architects and administrators design and
manage networks with an appropriate level of network scaling head room. The scaling and
performance figures provided have been verified using specific network topologies using limited
switch configurations. There is no guarantee that the scaling and performance figures shown are
applicable to all network topologies and switch configurations and are provided as a realistic
estimation only. If you experience scaling and performance characteristics that you feel are
sufficiently below what has been documented, contact Extreme Networks technical support for
additional assistance.
The route limits shown in Table 1 for IPv4 and IPv6 routing protocols are software limits only. The
actual hardware limits may be higher or lower than the software limits, based on platform. The
hardware limits for specific platforms are specified as "IPv4/IPv6 routes (LPM entries in hardware)"
in the following table.
On products other than the BlackDiamond 8900 xl-series, BlackDiamond X8 series, and Summit
X480 series, it is not advised to have greater than 25,000 total IP routes from all routing protocols.
Adverse effects can occur with routing tables larger than this, especially when a single network
event or CLI command affects a significant number of routes. For example, just after such a
network event, the added system load will cause a save configuration command to time out.
NOTE
The term BlackDiamond 8000 e-series refers to all BlackDiamond 8500 e-series and
8800 e-series modules.The term BlackDiamond 8000 series refers to all
BlackDiamond 8500, 8800, and 8900 series modules.
Limits
Table 1: Supported Limits
Metric Product Limit
AAA (local)maximum number of
admin and local user accounts.
All platforms 16
Access lists (meters)maximum
number of meters.
BlackDiamond 8000 series
e-series, group of 24 ports
c-series
8900-10G24X-c, group of 12 ports
8900 xl-series, 8900-G96T-c
8900-40G6X-xm
BlackDiamond X8 series
E4G-200
Summit X440, X430 per group of 24
ports
Summit X460, E4G-400, per group of 24
ports
Summit X480
Summit X670 with VIM4-40G4x
Summit X480 with VIM3-40G4X
Summit X770
512
2,048 ingress,
256 egress
1,024 ingress,
256 egress
4,096 ingress,
512 egress
512 ingress
512 egress
512 ingress,
512 egress
1,024 ingress
256 egress
512 ingress
2,048 ingress,
256 egress
4,096 ingress,
512 egress
512 ingress
512 egress
1,024 ingress,
512 egress
Access lists (policies)suggested
maximum number of lines in a
single policy file.
All platforms 300,000
Limits
Access lists (policies)maximum
number of rules in a single policy
file.
a
c-series, group of 24 ports
e-series, group of 24 ports
BlackDiamond 8900
8900-10G24X-c modules, group of 12
ports
8900-G96T-c modules, group of 48
ports
8900 xl-series
8900-40G6X-xm
Summit X440, X430 group of 24 ports
Summit X460, E4G-400
Summit X480
Summit X670
VIM4-40G4x
Summit X480
VIM3-40G4X
Summit X770
4,096 ingress,
512 egress
1,024 ingress
2,048 ingress,
512 egress
8,192 ingress,
1,024 egress
61,440 (up to)
2,048 ingress,
1,024 egress
2,048 ingress,
1,024 egress
1,024 ingress
4,096 ingress,
512 egress
(up to) 61,440
ingress,
1,024 egress
2,048 ingress
1,024 egress
2048 ingress
1024 egress
4,096 ingress
1,024 egress
Table 1: Supported Limits (Continued)
Limits
Access lists (slices)number of
ACL slices.
c-series, group of 48 ports
8900-10G24X-c modules, group of 12
ports
8900-G96T-c modules, group of 48
ports
8900 xl-series
8900-40G6X-xm
E4G-200
Summit X440, X430
Summit X480
Summit X670
VIM4-40G4x
Summit X480
VIM3-40G4X
Summit X770
16
12 ingress,
4 egress
16 ingress,
4 egress
17
b
10 ingress,
4 egress
10 ingress,
4 egress
8 ingress,
4 egress
4 ingress
16 ingress,
4 egress
17
b
ingress,
4 egress
10 ingress,
4 egress
10 ingress,
4 egress
12 ingress
4 egress
AVB (audio video bridging)
maximum number of active
streams
NOTE: * It is recommended that
you do not use on more than 8
ports on this switch.
Summit X440, X460
Summit X670
Summit X430
1,024
4,096
100*
BFD sessionsmaximum number
of BFD sessions
All platforms (default timers1 sec)
BlackDiamond X8 and 8800 (minimal
timers50 msec)
All Summits
(minimal timers100 msec)
512
10
c
10
c
Limits
BGP (aggregates)maximum
number of BGP aggregates.
All platforms with Core license or higher 256
BGP (networks)maximum
number of BGP networks.
All platforms with Core license or higher
1,024
1,024
BGP (peers)maximum number of
BGP peers.
NOTE: * With default keepalive and
hold timers.
BlackDiamond xl-series
Summit X460, X670, X770
E4G-400, E4G-200
Summit X480
512
512
512
128*
128*
512
BGP (peer groups)maximum
number of BGP peer groups.
Summit X480
All platforms
(except BlackDiamond X8 series,
BlackDiamond 8900 series, and Summit
X480) with Core license or higher
128
128
128
64
BGP (policy entries)maximum
number of BGP policy entries per
route policy.
BGP (policy statements)
maximum number of BGP policy
statements per route policy.
All platforms with Core license or higher 1,024
BGP multi-cast address-family
routes maximum number of
multi-cast address-family routes.
BlackDiamond 8900 xl-series
Summit X460, X670, X770
Summit X480
E4G-400
25,000
524,256 (up to)
b
25,000
25,000
524,256 (up to)
b
25,000
BGP (unicast address-family
routes)maximum number of
unicast address-family routes.
Summit X460, X670, X770
Summit X480
E4G-400
25,000
524,256 (up to)
b
25,000
25,000
524,256 (up to)
b
25,000
Limits
BGP (non-unique routes)
maximum number of non-unique
BGP routes.
Summit X460, X670, X770
Summit X480
E4G-400, E4G-200
25,000
1,200,000
25,000
25,000
1,000,000
25,000
BGP ECMPmaximum number of
equalcost multipath for BGP and
BGPv6.
All platforms, except Summit X440 2, 4, or 8
BGPv6 (unicast address-family
routes) maximum number of
unicast address family routes.
BlackDiamond 8800 c-series
BlackDiamond 8000 e-series
Summit X460
Summit X480
Summit X670, X770
E4G-400
20,000
6,000
240
8,000
6,000
20,000
8,000
6,000
BGPv6 (non-unique routes)
maximum number of non-unique
BGP routes
Summit X460
Summit X480, X670, X770
E4G-400
24,000
18,000
720
24,000
18,000
24,000
18,000
BOOTP/DHCP relaymaximum
number of BOOTP or DHCP servers
per virtual router.
All platforms 4
BOOTP/DHCP relaymaximum
number of BOOTP or DHCP servers
per VLAN.
All platforms 4
CES TDM pseudowiresmaximum
number of CES TDM pseudowires
per switch.
E4G-200 and E4G-400 256
Connectivity fault management
(CFM)maximum number or CFM
domains.
All platforms 8
CFMmaximum number of CFM
associations.
All platforms 256
Limits
CFMmaximum number of CFM up
end points.
Summit series
32
32
32
down end points.
Summit series X460, E4G-200, E4G-400
(non-load shared ports)
Summit series X460, E4G-200, E4G-400
(load shared ports)
Summit series
All other platforms
32
32
256
32
32
32
remote end points per up/down
end point.
All platforms 2,000
CFMmaximum number of dot1ag
ports.
All platforms 128
segments.
All platforms 1,000
CLEAR-Flowtotal number of rules
supported. The ACL rules plus
CLEAR-Flow rules must be less
than the total number of supported
ACLs.
Summit X440
Summit X670
Summit X480, Summit X770
4,096
4,096
4,096
1,024
2,048
4,096
Data Center Bridging eXchange
(DCBX) protocol Type Length
Value (TLVs)maximum number of
DCBX application TLVs.
All platforms 8
Dynamic ACLsmaximum number
of ACLs processed per second.
NOTE: Limits are load dependent.
BlackDiamond 8800 with c-series MSM
and I/O modules
Summit X480, X670
with 50 DACLs
with 500 DACLs
8
8
8
10
5
Limits
EAPS domainsmaximum number
of EAPS domains.
NOTE: An EAPS ring that is being
spatially reused cannot have more
than four configured EAPS
domains.
Summit series (except X430), E4G-200,
E4G-400
Summit X430
64
64
32
4
EAPSv1 protected VLANs
maximum number of protected
VLANs.
Summit series, E4G-200, E4G-400
2,000
4,000
1,000
EAPSv2 protected VLANs
VLANs.
2,000
4,000
500
ELSM (vlan-ports)maximum
number of VLAN ports.
5,000
5,000
5,000
ERPS domainsmaximum number
of ERPS domains without CFM
configured
Summit series (except X430),
E4G-200, E4G-400
Summit X430
32
32
32
4
ERPS domainsmaximum number
of ERPS domains with CFM
configured.
Summit series non-CSR platforms
Summit X460
E4G-200, E4G-400
16
16
16
32
32
ERPSv1 protected VLANs
VLANs.
2,000
2,000
1,000
ERPSv2 protected VLANs
VLANs
2,000
2,000
500
ESRP groupsmaximum number
of ESRP groups.
All platforms 7
ESRP domainsmaximum number
of ESRP domains.
Summit series
64
64
128
64
Limits
ESRP VLANsmaximum number
of ESRP VLANs.
BlackDiamond X8 and 8900 series
Summit series
1,000
2,048
1,000
ESRP (maximum ping tracks)
maximum number of ping tracks
per VLAN.
All platforms 8
ESRP (IP route tracks)maximum
IP route tracks per VLAN.
All platforms 8
ESRP (VLAN tracks)maximum
number of VLAN tracks per VLAN.
All platforms 1
Forwarding ratemaximum L2/L3
software forwarding rate.
Summit series, except Summit X770
Summit X770
10,000 pps
20,000 pps
10,000 pps
16,000 pps
FDB (blackhole entries)
maximum number of unicast
blackhole FDB entries.
8900 c-series
8900 xl-series
8900-40G6X-xm
E4G-200, E4G-400
Summit X440, X430
Summit X480
Summit X460
Summit X670
VIM4-40G4x
Summit X770
32,000
8,000
32,000
524,288 (up to)
b
128,000
128,000
32,000
16,000
524,288 (up to)
b
32,000
128,000
288,000
d
FDB (blackhole entries)
maximum number of multi-cast
blackhole FDB entries.
All Summit series switches, except X770
Summit X770
1,024
1,024
1,024
4,000
Limits
FDB (maximum L2 entries)
maximum number of MAC
addresses.
BlackDiamond 8000 (system), except
8900 xl-series
E4G-200, E4G-400
Summit X440, X430
Summit X480
Summit X480
VIM3-40G4X
Summit X460
SummitStack (except X480)
Summit X670
Summit X770
32,768
e
8,192
e
128,000
e
524,488 (up to)
b
128,000
e
32,000
e
16,000
e
524,488 (up to)
b
128,000
e
32,768
e
128,000
e
128,000
e
288,000
d

e
FDB (Maximum L2 entries)
maximum number of multi-cast
FDB entries.
BlackDiamond X8
BlackDiamond 8800
All Summit series switches, except X770
Summit X770
1,024
4,000
FIP Snooping VLANs BlackDiamond X8 768
BlackDiamond 8800 (8900-40G6X-c
only)
Summit X670
FIP Snooping Virtual Links
(FPMA mode) per port group
BlackDiamond X8 1,908
only)
Summit X670
FIP Snooping FCFs
(with perimeter port) per port
group
BlackDiamond X8 238
only)
FIP Snooping FCFs
(with Enode-to-FCF port)
BlackDiamond X8 212
only)
Summit X670
Identity managementmaximum
number of Blacklist entries.
All platforms 512
Limits
number of Whitelist entries.
All platforms 512
number of roles that can be
created.
All platforms 64
role hierarchy depth allowed.
All platforms 5
number of attribute value pairs in a
role match criteria.
All platforms 16
of child roles for a role.
All platforms 8
number of policies/dynamic ACLs
that can be configured per role.
All platforms 8
number of LDAP servers that can
be configured.
All platforms 8
number of Kerberos servers that
can be configured.
All platforms 20
database memory-size.
All platforms 6449, 152
Identity management
recommended number of identities
per switch.
NOTE: Number of identities per
switch is for a default identity
management database size (512
Kbytes) across all platforms.
All platforms 100
Identity management
recommended number of ACL
entries per identity.
NOTE: Number of ACLs per
identity based on system ACL
limitation.
All platforms 20
number of dynamic ACL entries
configured as an individual
dynamic rule, or as an ACL entry in
a policy file.
All platforms (except Summit X430)
Summit X430
500
512
Limits
IGMP sendermaximum number
of IGMP senders per switch (IP
multi-cast compression disabled).
l
NOTE: Assumes source-group-vlan
mode.
BlackDiamond 8900-10G24X-c modules
BlackDiamond 8900-G96T-c modules
BlackDiamond 8900-40G6X-xm
E4G-200, E4G-400
Summit X440
Summit X480
Summit X460
Summit X670
VIM4-40G4x
Summit X770
2,048
f
500
g
2,048
f
4,096
f
3,000
g
4,096
f
4,096
h
2,048
64
4,096
2,048
3,000
g
4,000
IGMP sendermaximum number
of IGMP senders per switch (IP
multi-cast compression enabled).
l
mode.
For additional limits, see:
Layer-2 IPMC forwarding
caches(IGMP/MLD/PIM
snooping) in mac-vlan mode.
on page 59
caches (IGMP/MLD/PIM
snooping) in mixed-mode. on
page 59
E4G-200
E4G-400
Summit X440
Summit X460
Summit X480
Summit X670
VIM4-40G4x
Summit X770
6,000
g
500
g
6,000
g
12,000
b
3,000
g
6,000
g h
3,000
g
6,000
g
192
g
6,000
g
12,000
b
3,000
g
16,000
Limits
IGMP snooping per VLAN filters
maximum number of VLANs
supported in per-VLAN IGMP
snooping mode.
E4G-200, E4G-400
Summit X440
Summit X460, X670
Summit X480
Summit X770
2,000
448
1,000
4,000
1,000
1,000
1,000
448
1,000
4,000
2,000
IGMPv1/v2 SSM-map entries
maximum number of IGMPv1/v2
SSM mapping entries.
All platforms 500
IGMPv1/v2 SSM-MAP entries
maximum number of sources per
group in IGMPv1/v2 SSM mapping
entries.
All platforms 50
IGMPv2 subscribermaximum
number of IGMPv2 subscribers per
port.
m
Summit series (except Summit X460,
X480, X770, and X670)
Summit X460, X480, X670, E4G-400
Summit X770
2,000
2,000
2,000
1,000
2,000
3,000
switch.
m
X770, and X670)
Summit X460, X480, X670, E4G-400
Summit X770
20,000
20,000
20,000
10,000
20,000
25,000
IGMPv3 maximum source per
groupmaximum number of
source addresses per group.
All platforms 250
Limits
port.
m
X770)
Summit X770
1,000
2,000
5,000
3,000
1,000
2,500
2,000
switch.
m
Summit series (except Summit X460 and
X770)
Summit X770
10,000
20,000
30,000
30,000
10,000
20,000
30,000
IP ARP entries in software
maximum number of IP ARP
entries in software.
NOTE: May be limited by hardware
capacity of FDB (maximum L2
entries).
Summit X770
All other platforms
13,1072
i
20,480
IP ARP entries in software with
distributed mode onmaximum
number of IP ARP entries in
software with distributed mode on.
BlackDiamond 8000 series with
8900-MSM128 or MSM-48c, and only
8900 xl-series I/O modules
BlackDiamond 8000 series with any I/O
modules that are not 8900 xl-series
All other platforms
260,000
100,000
28,000
N/A
Limits
IPv4 ARP entries in hardware with
distributed mode onmaximum
number of IP ARP entries in
hardware with distributed mode on
Per BlackDiamond 8900-10G8X-xl, up to
260,000 per system
Per BlackDiamond 8900-G48X-xl or
8900-G48T-xl, up to 130,000 per system
Per BlackDiamond 8000 c-series, up to
18,000 per system
BlackDiamond 8900-40G6X-xm, up to
22,000 per system
BlackDiamond X8 series, up to 28,000
per system
All other platforms
32,500
b
16,250
b
8,000
8,000
12,000
N/A
minimum LPM routesmaximum
recommended number of IPv4 ARP
entries in hardware, with minimum
LPM routes present. For
BlackDiamond 8800,
BlackDiamond X8, E4G, and
Summit series switches, assumes
number of IP route reserved entries
is 100 or less.
BlackDiamond 8800 c-, xm-series
E4G-200
E4G-400
Summit X440
Summit X670
Summit X460, X480
Summit X770
8,000
1,000
g
16,000
16,000
8,000
16,000
412
8,000
16,000
106,000
i
maximum LPM routesmaximum
recommended number of IPv4 ARP
entries in hardware, with maximum
LPM routes present. For
BlackDiamond 8800,
Summit series, assumes number of
IP route reserved entries is
maximum.
E4G-200
E4G-400
Summit X440
Summit X460, X480
Summit X670
Summit X770
6,000
g
500
g
12,000
g
12,000
g
6,000
g
12,000
g
380
12,000
g
6,000
g
96,000
i
Limits
IPv4 remote hosts in hardware
with zero LPM routesmaximum
recommended number of IPv4
remote hosts (hosts reachable
through a gateway) in hardware
when LPM routing is not used. For
BlackDiamond 8800,
Summit series, assumes number of
IP route reserved entries is 0, and
number of IPv4 ARP entries
present is 100 or less.
E4G-200
E4G-400
Summit X440
Summit X460
Summit X480
Summit X670
Summit X770
18,000
g
1,000
g
40,000
b
22,000
g
28,000
g
18,000
g
20,000
g
448
20,000
g
40,000
b
22,000
g
172,000
i
IPv4 routesmaximum number of
IPv4 routes in software
(combination of unicast and multi-
cast routes).
BlackDiamond 8900 xl-series with
8900-MSM128 or MSM-48c
All other BlackDiamond 8000 series
hardware
Summit X440
Summit X460, X670, E4G-400, E4G-200
SummitStack or standalone
Summit X480
SummitStack or standalone
Summit X770
524,256 (up to)
b
25,000
25,000
256
25,000
524,256 (up to)
b
25,000
IPv4 routes (LPM entries in
hardware) number of IPv4 routes
in hardware.
E4G-200, E4G-400
Summit X440
Summit X460
Summit X480
Summit X670
Summit X770
12,000
480
524,256 (up to)
bj
16,000
e
16,000
e
12,000
32
12,000
524,256 (up to)
bj
16,000
j
16,000
IPv6 addresses on an interface
maximum number of IPv6
addresses on an interface.
All platforms 255
Limits
IPv6 addresses on a switch
maximum number of IPv6
addresses on a switch
E4G-200, E4G-400
Summit X440
Summit X460, X480
Summit X770, X670
512
512
512
254
512
2,048
IPv6 host entries in hardware
maximum number of IPv6 neighbor
entries in hardware.
BlackDiamond 8900-10G24X-c modules
BlackDiamond 8900-G96T-c modules
E4G-200
E4G-400
Summit X440
Summit X460, X670
Summit X480
Summit X770
3,000
g
250
g
2,000
g
4,000
g
8,192 (up to)
b
3,000
g
2,000
g
3,000
g
192
3,000
g
8,192 (up to)
b
36,750
IPv6 routes (LPM entries in
hardware)maximum number of
IPv6 routes in hardware.
BlackDiamond 8900 xm-series
E4G-200, E4G-400
Summit X440
Summit X460
Summit X670
Summit X480
Summit X770
6,000
240
8,000
245,760 (up to)
b
8,000
6,000
16
6,000
8,000
245,760 (up to)
b
8,000
IPv6 routes with a mask greater
than 64 bits in hardware
maximum number of such IPv6
LPM routes in hardware.
BlackDiamond 8000 c-, e-, xm-series
E4G-200, E4G-400
Summit X440, X460, X670, X770
Summit X480
256
245,760 (up to)
b
256
256
256
245,760 (up to)
b
Limits
IPv6 routes in software
maximum number of IPv6 routes in
software.
BlackDiamond 8900 xl-series with 8900-
MSM128 or MSM-48c
All other BlackDiamond 8000 series
hardware
Summit X460, X670, X770,
E4G-200, E4G-400, SummitStack, or
standalone
Summit X440
Summit X480, SummitStack, or
standalone
245,760 (up to)
b
25,000
25,000
25,000
256
245,760 (up to)
b
IP router interfacesmaximum
number of VLANs performing IP
routingexcludes sub VLANs (IPv4
and IPv6 interfaces).
Summit X670, X770, and BlackDiamond
X8
Summit X440
All other platforms
2,048
254
512
IP multi-cast static routes
maximum number of permanent
multi-cast IP routes.
All platforms 1,024
IP unicast static routesmaximum
number of permanent IP unicast
routes.
All platforms 1,024
IP route sharing (maximum
gateways)configurable maximum
number of configurable gateways
used by equal cost multipath OSPF,
BGP, IS-IS, or static routes. Routing
protocol OSPF is limited to 16
ECMP gateways per destination.
Routing protocols BGP and IS-IS
are limited to 8 ECMP gateways per
destination.
All platforms 2, 4, 8, 16, or 32
Limits
IP route sharing (total
destinations)maximum number
of unique destinations used by
multipath OSPF, OSPFv3, BGP, IS-
IS, or static routes.
NOTE: For platforms with limit of
524,256, the total number of
"destination+gateway" pairs is
limited to 1,048,512. For example, if
the number of unique destinations
is 524,256, only 2 gateways per
destination is supported.
For other platforms, each limit is
based on up to 8 gateways per
destination for BGP and IS-IS
routing protocols, up to 16
gateways per destination for OSPF,
or up to 32 gateways per
destination for static routes.
Summit X460, E4G-200, E4G-400
Summit X480
Summit X670, X770
E4G-200, E4G-400
12,256
480
524,256 (up to)
b
16,352
16,000
12.256
524,256 (up to)
b
16,352
12,256
IP route sharing (total
combinations of gateway sets)
maximum number of combinations
of sets of adjacent gateways used
by multipath OSPF, BGP, IS-IS, or
static routes.
BlackDiamond 8800 c-, xl-, and xm-series
default maximum gateways of 4
if maximum gateways is 2
Summit X460, X480, X670, X770, E4G-
200, E4G-400
510
1,022
254
126
62
30
62
14
6
2
510
1,022
254
126
62
510
1,022
254
126
62
IP multinetting (secondary IP
addresses)maximum number of
secondary IP addresses per VLAN.
All platforms 64
Limits
IS-IS adjacenciesmaximum
number of supported IS-IS
adjacencies.
Summit X460, X480, X670,
X770, E4G-400
E4G-200
128
128
255
128
256
IS-IS ECMPmaximum number of
equal cost multipath for IS-IS.
All platforms, except Summit X440 2, 4, or 8
IS-IS interfacesmaximum number
of interfaces that can support IS-IS.
All platforms 255
IS-IS routers in an area
recommended maximum number
of IS-IS routers in an area.
Summit X480
All other platforms
128
256
IS-IS route origination
of routes that can be originated by
an IS-IS node.
Summit X480
Summit X460, X670, X770, E4G-400
E4G-200
20,000
20,000
30,000
30,000
20,000
25,000
IS-IS IPv4 L1 routes in an L1
routerrecommended maximum
number of IS-IS Level 1 routes in a
Level 1 IS-IS router.
Summit X480
Summit X460, X670, X770, E4G-400
25,000
25,000
120,000
50,000
25,000
IS-IS IPv4 L2 routes
of IS-IS Level 2 routes.
Summit X480
Summit X460, X670, X770, E4G-400
25,000
25,000
120,000
50,000
25,000
IS-IS IPv4 L1 routes in an L1/L2
number of IS-IS Level 1 routes in an
L1/L2 IS-IS router.
Summit X460, X480, X670, X770, E4G-
400
20,000
20,000
20,000
20,000
Limits
IS-IS IPv6 L1 routes in an L1
Level 1 IS-IS router.
Summit X480
Summit X460, X670, X770, E4G-400
10,000
10,000
40,000
25,000
10,000
IS-IS IPv6 L2 routes
of IS-IS Level 2 routes.
Summit X480
Summit X460, X670, X770, E4G-400
10,000
10,000
40,000
25,000
10,000
IS-IS IPv6 L1 routes in an L1/L2
L1/l2 router.
Summit X480
Summit X460, X670, X770, E4G-400
10,000
10,000
15,000
15,000
10,000
IS-IS IPv4/IPv6 L1 routes in an L1
Level 1 IS-IS router. The numbers
documented are based on 50%
IPv4 routes and 50% IPv6 routes.
Summit X480
Summit X460, X670, X770, E4G-400
20,000
20,000
60,000
40,000
20,000
IS-IS IPv4/IPv6 L2 routes in an L2
Level 2 IS-IS router. The numbers
documented are based on 50%
IPv4 routes and 50% IPv6 routes.
Summit X480
Summit X460, X670, X770, E4G-400
20,000
20,000
60,000
40,000
20,000
IS-IS IPv4/IPv6 L1 routes in an L1/
L2 routerrecommended
maximum number of IS-IS Level 1
routes in a Level 1/Level2 IS-IS
router. The numbers documented
are based on 50% IPv4 routes and
50% IPv6 routes.
Summit X460, X480, X670, X770, E4G-
400
20,000
20,000
20,000
20,000
Jumbo framesmaximum size
supported for jumbo frames,
including the CRC.
All platforms 9,216
L2 VPN: VCCV (pseudowire Virtual
Circuit Connectivity Verification)
VPNs per switchmaximum
number of VCCV enabled VPLS
VPNs.
All platforms 16
Limits
L2 VPN: VPLS MAC addresses
maximum number of MAC
addresses learned by a switch.
E4G-200, E4G-400
Summit X460
Summit X480
Summit X670, Summit X670V-48t,
Summit X770
Summit X480-40G VIM
512,000
128,000
128,000
32,000
32,000
512,000
128,000
121,000
L2 VPN: VPLS VPNsmaximum
number of VPLS virtual private
networks per switch.
BlackDiamond 8900-40G6x-xm
E4G-200, E4G-400
Summit 460
Summit X480, X670, Summit X670V-48t,
Summit X770
Summit X480-40G VIM
1,023
1,023
1,023
1,000
1,000
1,023
1,023
L2 VPN: VPLS peersmaximum
number of VPLS peers per VPLS
instance.
Summit X670V-48t, Summit X480-40G
VIM
E4G-200, E4G-400
64
32
64
64
64
64
32
L2 VPN: LDP pseudowires
maximum number of pseudowires
per switch.
E4G-200, E4G-400
Summit X460
Summit X480
Summit X670
Summit X670V-48t
Summit X480-40G VIM
Summit X770
7,000
3,000
7,000
1,000
1,000
7,000
3,000
7,000
3,000
7,800
Limits
L2 VPN: static pseudowires
maximum number of static
pseudowires per switch.
BlackDiamond X8
Summit X460
Summit X770
Summit X480, Summit X670V-48t
Summit X480-40G, Summit X670
E4G-200, E4G-400
7,000
3,000
7,000
2,000
7,800
7,000
3,000
2,000
L2 VPN: Virtual Private Wire
Service (VPWS) VPNsmaximum
number of virtual private networks
per switch.
Summit X460
Summit X480-40G VIM
Summit X670
Summit X670V-48t
E4G-200, E4G-400
1,000
4,000
2,047
2,047
4,000
4,000
2,047
4,000
1,000
Layer-2 IPMC forwarding caches
(IGMP/MLD/PIM snooping) in mac-
vlan mode.
NOTE: IPv6 and IPv4 L2 IPMC
scaling is the same for this mode.
BlackDiamond 8800 e-series switches
BlackDiamond 8800 c- and xl-series
switches
BlackDiamond 8800 xm-series switches
E4G-200 and E4G-400 cell site routers,
Summit X460, X480
Summit X670
Summit X440
Summit X770
2,000
8,000
15,000
15,000
8,000
15,000
4,000
77,500
k
(IGMP/MLD/PIM snooping) in
mixed-mode.
NOTE: IPv6 and IPv4 L2 IPMC
scaling is the same for this mode.
BlackDiamond 8800 xl- and c-series
switches
BlackDiamond X8, Summit X670
E4G-200 and E4G-400 cell site routers,
Summit X460, X480
Summit X440
Summit X770
N/A
8,000
15,000
15,000
8,000
4,000
77,500
k
Limits
(PIM, MVR, PVLAN) in mixed-
mode.
g
NOTE: IPv6 L3 IPMC scaling is 50%
of these limits in this mode.
BlackDiamond 8800 xl- and c-series
switches
E4G-200 cell site routers, Summit X670
E4G-400 cell site routers, Summit X460,
X480
Summit X440
Summit X770
N/A
6,000
3,000
6,000
3,000
6,000
192
77,500
k
Load sharingmaximum number
of loadsharing groups.
NOTE: The actual number of load-
sharing groups that can be
configured is limited by the number
of physical ports present in the
switch or SummitStack.
BlackDiamond 8000 series without 8900-40G6X-xm
With distributed IP ARP mode off
(default)
128
With distributed IP ARP mode on 64
BlackDiamond 8000 series with 8900-40G6X-xm using
address-based custom algorithm
(default)
128
BlackDiamond 8000 series with 8900-40G6X-xm with L2, L3
or L3_L4 algorithm configured for any group
(default)
127
SummitStack with X670 with L2, L3 or
L3_L4 algorithm configured for any
group
127
All other SummitStack configurations and
Summit series switches
128
BlackDiamond X8 series using address-based custom
algorithm
(default)
384
BlackDiamond X8 series with L2, L3 or L3_L4 algorithm
configured for any group
(default)
127
Limits
Load sharingmaximum number
of ports per load-sharing group.
NOTE:
* For custom algorithm
** For L2, L3, L3, L4 algorithms
NOTE: For a mix of Summit X770
and Summit X670 series switches
in a stack, the limits are the Summit
X670 limits.
BlackDiamond X8 series 64
Summit X670 (standalone) 32 *
16 **
Summit X670 (stacked) 64 *
16 **
Summit X770 (standalone) 32
Summit X770 (stacked) 64
All other Summit series, SummitStacks,
and BlackDiamond 8000 series switches
8
Logged messagesmaximum
number of messages logged locally
on the system.
MAC address learning rate
hardware learning rate
E4G-200 22 msec
MAC-based securitymaximum
number of MAC-based security
policies.
All platforms 1,024
Mirroring (filters)maximum
number of mirroring filters.
NOTE: This is the number of filters
across all the active mirroring
instances.
Summit series
128
128
128
Mirroring (monitor port)
maximum number of monitor ports.
All platforms 1
Mirroring, one-to-many (filters)
maximum number of one-to-many
mirroring filters.
NOTE: This is the no. of filters
across all the active mirroring
instances
Summit series
128
128
128
Mirroring, one-to-many (monitor
port)maximum number of one-
to-many monitor ports.
All platforms 16
Limits
Maximum mirroring instances
NOTE: Only two or four mirroring
instance will be active at a time
depending on the mirroring filter
added to it. There are four
hardware resource slots. Each
single instance uses one such slot,
while each ingress plus egress
instance uses two slots. So this
allows the you to use a total of four
slots, while there are no more then
two egress instances. The
maximum possible combination for
mirroring instances:
1 4 ingress
2 3 ingress + 1 egress
3 2 ingress + 2 egress
4 2 (ingress + egress)
5 1 (ingress + egress) + 2
ingress
6 1 (ingress + egress) + 1
egress + 1 ingress
All platforms 16
(including default
mirroring
instance)
MLAG portsmaximum number of
MLAG ports allowed.
Summit series
768
768
768
MLAG peersmaximum number of
MLAG peers allowed.
Summit series
1
1
1
MPLS RSVP-TE interfaces
maximum number of interfaces.
All platforms 32
MPLS RSVP-TE ingress LSPs
maximum number of ingress LSPs.
All platforms 2,000
MPLS RSVP-TE egress LSPs
maximum number of egress LSPs.
All platforms 2,000
MPLS RSVP-TE transit LSPs
maximum number of transit LSPs.
All platforms 2,000
MPLS RSVP-TE pathsmaximum
number of paths.
All platforms 1,000
MPLS RSVP-TE profilesmaximum
number of profiles.
All platforms 1,000
MPLS RSVP-TE EROsmaximum
number of EROs per path.
All platforms 64
Limits
MPLS RSVP-TE LDP-enabled
interfacesmaximum number of
MPLS LDP configured interfaces
per switch.
Summit X460, X670
Summit X480, Summit X480-40G VIM,
Summit X670V-48t, Summit X770
E4G-200, E4G-200
32
64
64
64
64
32
MPLS RSVP-TE fast rerouteMPLS
RSVP-TE fast reroute (FRR)
switching time.
E4G-200 50 msec
MPLS LDP peersmaximum
number of MPLS LDP peers per
switch.
Summit X480, Summit X480-40G VIM,
Summit X670V-48t, Summit X770
E4G-400, E4G-200
32
64
64
64
64
32
MPLS LDP adjacenciesmaximum
number of MPLS LDP adjacencies
per switch.
E4G-200, E4G-400
Summit X460, X480, X670
Summit X670V-48t, Summit X480-40G
VIM, Summit X770
50
64
50
50
50
64
MPLS LDP ingress LSPsmaximum
number of MPLS LSPs that can
originate from a switch.
E4G-200
E4G-400
Summit X460, X480
Summit X670, Summit X670V-48t,
Summit X480-40G VIM,
Summit X770
4,000
2,048
2,048
2,048
4,000
4,000
2,048
MPLS LDP Sessionsmaximum
number of MPLS LDP sessions.
E4G-200 32
Limits
MPLS LDP transit LSPsmaximum
number of MPLS transit LSPs per
switch.
E4G-200
E4G-400
Summit X460, Summit X480, Summit
X770, Summit X670V-48t
Summit X670, Summit X480-40G
4,000
3,000
4,000
2,700
4,000
4,000
3,000
MPLS LDP egress LSPsmaximum
number of MPLS egress LSPs that
can terminate on a switch.
E4G-200
E4G-400
Summit X460, X480,
Summit X670V-48t
Summit X670,
Summit x480-40G VIM
Summit X770
7,000
3,000
7,000
2,700
6,700
7,000
3,000
8,000
MPLS static egress LSPs
maximum number of static egress
LSPs.
BlackDiamond 8900-40G
BlackDiamond X8
Summit X460, Summit X480, Summit
X670V-48t
Summit X770
E4G-200
E4G-400
7,000
3,000
7,000
7,000
3,000
8,000
2,700
6,700
MPLS static ingress LSPs
maximum number of static
ingress LSPs.
BlackDiamond X8
Summit x480-40G, Summit X670,
Summit x670V-48t, Summit X770
E4G-200
E4G-400
4,000
2,048
2,048
4,000
2,048
2,048
4,000
Limits
MPLS static transit LSPs
maximum number of static transit
LSPs
BlackDiamond X8
Summit X460, Summit X480, X670V-48t,
Summit X770
E4G-200
E4G-400
4,000
3,000
4,000
4,000
3,000
2,700
4,000
MSDP active peersmaximum
number of active MSDP peers.
Summit X460, X480, X670, E4G-400
Summit X770
32
64
64
16
64
MSDP SA cache entriesmaximum
number of entries in SA cache.
Summit X460, X480, X670, E4G-400
Summit X770
16,000
16,000
16,000
8,000
16,000
MSDP maximum mesh groups
maximum number of MSDP mesh
groups.
Summit X460, X480, X670, E4G-400
Summit X770
8
16
16
4
16
Limits
Multi-cast listener discovery
(MLD) IPv6 multi-cast data
sendermaximum number of IPv6
multi-cast streams supported on a
switch
l g
mode.
caches(IGMP/MLD/PIM
on page 59
page 59
E4G-200
E4G-400
Summit X440
Summit X460
Summit X480
Summit X670
Summit X770
1,000
250
1,000
1,000
3,000
3,000
1,500
3,000
90
3,000
3,000
1,500
4,096
(MLD) snooping per-VLAN
filtersmaximum number of
VLANs supported in per-VLAN
MLD snooping mode.
BlackDiamond e-series
E4G-400, Summit X460
Summit X480
Summit X440
Summit X770
250
1,000
500
2,000
500
500
1,000
2,000
250
500
1,200
(MLD)v1 subscribersmaximum
number of MLDv1 subscribers per
port
m
BlackDiamond xl-series
BlackDiamond X8 Series
Summit X440, SummitStack
Summit X460, X480, X670, E4G-400
Summit X770
500
1,500
1,500
750
1,500
2,500
switch
m
Summit X460, X480, X670, E4G-400
Summit X770
10,000
10,000
5,000
10,000
27,500
Limits
port
m
BlackDiamond xl series
Summit X460, X480, X670, E4G-400
Summit X770
500
2,500
2,000
1,000
2,000
4,000
switch
m
BlackDiamond xl series
Summit X460, X480, X670, E4G-400
Summit X770
10,000
10,000
5,000
10,000
40,000
(MLD)v2 maximum source per
groupmaximum number of
source addresses per group
All platforms 200
Multi-cast VLAN registration
(MVR)maximum number of MVR
senders per switch (IP multi-cast
compression disabled).
mode.
8900-10G24X-c modules
8900-G96T-c modules
8900 xl-series
8900-40G6X-xm
E4G-200
E4G-400
Summit X440
Summit X480
Summit X460
Summit X670
VIM4-40G4x
Summit X770
2,048
f
500
g
2,048
f
4,096
f
4,096
f
3,000
g
4,096
2,048
500
g
1,024
2,048
2,048
3,000
g
4,096
Limits
Multi-cast VLAN registration
(MVR)maximum number of MVR
senders per switch (IP multi-cast
compression enabled).
mode.
mode.g on page 60
8900-40G6X-xm module
Summit X440
Summit X480
Summit X670
VIM4-40G4x
Summit X770
6,000
g
500
g
6,000
g
12,000
b
6,000
g
3,000
g
192
g
6,000
g
12,000
b
3,000
g
6,300
Network loginmaximum number
of clients being authenticated on
MAC-based VLAN enabled ports.
BlackDiamond 8000 series (clients per
module/per system)
Summit series
1,024
1,024
1,024
Network loginmaximum number
of dynamic VLANs.
Summit X430
2,000
1,024
Network login VLAN VSAs
maximum number of VLANs a
client can be authenticated on at
any given time.
All platforms 10
OSPFv2/v3 ECMPmaximum
number of equal cost multipath
OSPFv2 and OSPFv3.
All platforms, except Summit X440 2, 4, 8, or 16
OSPFv2 areasas an ABR, how
many OSPF areas are supported
within the same switch.
All platforms 8
OSPFv2 external routes
of external routes contained in an
OSPF LSDB.
Summit X460, X670, X770
Summit X480
E4G-400
E4G-200
20,000
130,000
20,000
5,000
130,000
5,000
5,000
Limits
OSPFv2 inter- or intra-area
routesrecommended maximum
number of inter- or intra-area
routes contained in an OSPF LSDB
with one ABR in OSPF domain.
Summit X460, X670
E4G-400
Summit X480, X770
7,000
7,000
7,000
2,000
2,000
7,000
OSPFv2 interfacesrecommended
maximum number of OSPF
interfaces on a switch.
NOTE: Active interfaces limit, with
Advanced Edge license.
(See below for Core license limits.)
All platforms
4
All platforms with Core license or higher
(active interfaces only)
400
OSPFv2 linksmaximum number
of links in the router LSA.
All platforms, except Summit X770
Summit X770
400
419
OSPFv2 neighborsmaximum
number of supported OSPF
adjacencies.
BlackDiamond X8 Series
Summit X460, X670, X770
Summit X440
Summit X480
E4G-400, E4G-200
128
255
255
128
128
255
128
OSPFv2 routers in a single area
of routers in a single OSPF area.
Summit X460, X670, X770
Summit X480
E4G-400
100
200
100
50
200
50
OSPFv2 virtual linksmaximum
number of supported OSPF virtual
links.
OSPFv3 areasas an ABR, the
maximum number of supported
OSPFv3 areas.
Limits
OSPFv3 external routes
of external routes.
Summit X460, X670, X770
Summit X480
E4G-400
10,000
10,000
60,000
10,000
60,000
10,000
OSPFv3 inter- or intra-area
routesrecommended maximum
number of inter- or intra-area
routes.
Summit X460, X670, X770
Summit X480
E4G-400
6,000
6,000
6,000
3,000
6,000
3,000
OSPFv3 interfacesmaximum
number of OSPFv3 interfaces.
NOTE: Active interfaces only, with
Advanced Edge license.
(See below for Core license limits.)
All platforms
4
NOTE: With Core license or higher.
(See above for Advanced Edge license
limits.)
Summit X460, X670, X770
Summit X480
E4G-400
256
256
384
128
384
128
OSPFv3 neighborsmaximum
number of OSPFv3 neighbors.
Summit X460, X670, X770
Summit X480
E4G-400
64
64
128
64
128
64
OSPFv3 virtual linksmaximum
number of OSPFv3 virtual links
supported.
Limits
PIM IPv4 snoopingmaximum
number of (S,G) entries
programmed in the hardware (IP
multi-cast compression disabled).
mode.
8900-G96T-c modules
8900 xl-series
8900-40G6X-xm
E4G-200
E4G-400
Summit X440
Summit X460
Summit X480
Summit X670
VIM4-40G4x
Summit X770
2,048
f
500
f
2,048
f
4,096
f
4,096
f
3,000
g
4,096
2,048
2,048
64
2,048
4,096
3,000
g
4,096
PIM IPv4 snoopingmaximum
number of (S,G) entries
programmed in the hardware (IP
multi-cast compression enabled).
mode.
caches(IGMP/MLD/PIM
on page 59
page 59
E4G-200
E4G-400
8900-40G6X-xm
Summit X440
Summit X480
Summit X460
Summit X670
VIM4-40G4x
Summit X770
6,000
g
500
g
6,000
g
12,000
b
6,000
g
3,000
g
6,000
g
3,000
g
192
g
12,000
b
6,000
g
3,000
g
66,500
Limits
PIM IPv4maximum routes
maximum number of (S,G) entries
installed in the hardware (IP multi-
cast compression disabled).
mode.
8900-G96T-c modules
8900 xl-series
8900-40G6X-xm
E4G-200
E4G-400
Summit X440
Summit X480
Summit X460
Summit X670
VIM4-40G4x
Summit X770
2,048
f
500
g
2,048
f
4,096
f
4.096
f
3,000
g
4,094
2,048
2,048
64
g
4,096
2,048
3,000
g
4,096
PIM IPv4maximum routes
installed in the hardware (IP multi-
cast compression enabled).
mode.
mode.g on page 60
E4G-200
E4G-400
8900-40G6X-xm modules
Summit X440
Summit X480
Summit X460
Summit X670
VIM4-40G4x
Summit X770
6,000
g
500
g
6,000
g
12,000
b
6,000
f
3,000
g
6,000
g
3,000
g
192
12,000
b
6,000
g
3,000
g
66,500
Limits
PIM IPv4-SSM (maximum SSM
(S,G) entries installed in the
hardware with PIM SSM
configuration (IP multi-cast
compression disabled).
mode.
8900-G96T-c modules
8900 xl-series
8900-40G6X-xm
E4G-200
E4G-400
Summit X440
Summit X480
Summit X460
Summit X670
VIM4-40G4x
Summit X770
2,048
f
500
g
2,048
f
4,096
f
15,000
3,000
g
4,094
2,048
2,048
64
4,096
2,048
3,000
g
4,096
PIM IPv4-SSM (maximum SSM
(S,G) entries installed in the
hardware with PIM SSM
configuration (IP multi-cast
compression enabled).
mode.
mode.g on page 60
E4G-200
E4G-400
8900-40G6X-xm
Summit X440
Summit X480
Summit X460
Summit X670
VIM4-40G4x
Summit X770
6,000
g
500
g
6,000
g
12,000
b
6,000
g
3,000
g
6,000
g
3,000
g
192
g
12,000
b
6,000
g
3,000
g
66,500
Limits
PIM IPV6 (maximum routes)
installed in the hardware.
mode.
E4G-200
E4G-400
Summit X440
Summit X460
Summit X480
Summit X670
Summit X770
1,000
250
1,000
1,000
3,000
3,000
1,500
3,000
90
3,000
3,000
1,500
4,096
PIM IPv4 (maximum interfaces)
maximum number of PIM active
interfaces.
All platforms 512
maximum number of PIM snooping
enabled interfaces.
All platforms 512
PIM IPv4 Limitsmaximum
number of multi-cast groups per
rendezvous point
All platforms 180
number of multi-cast sources per
group
All platforms 175
number of dynamic rendezvous
points per multi-cast group
All platforms 145
PIM IPv4 Limitsstatic rendezvous
points
All platforms 32
maximum number of PIM active
interfaces
All platforms 512
number of multicast group per
rendezvous point
All platforms 70
number of multicast sources per
group
All platforms 43
number of dynamic rendezvous
points per multicast group
All platforms 64
Limits
number of secondary address per
interface
All platforms 70
PIM IPv6 Limitsstatic rendezvous
points
All platforms 32
Policy-based routing (PBR)
redundancymaximum number of
flow-redirects.
All platforms 256
n
Policy-based routing (PBR)
redundancymaximum number of
next hops per each flow-direct.
All platforms 32
n
Port-specific VLAN tags
maximum number of port-specific
VLAN tags
All platforms 1,023
Port-specific VLAN tags
maximum number of port-specific
VLAN tag ports
BlackDiamond X8 and BlackDiamond
8800 xl-series
Summit X480
Summit X460-48t
Summit X460-24x, X670-48x
Summit X670V-48t
Summit X670v-48t stack
Summit X770
E4G-400
E4G-200
8,090
3,800
7,200
3,400
3,600
7,200
6,400
3,400
3,800
Private VLANsmaximum number
of subscribers. Assumes a
minimum of one port per network
and subscriber VLAN.
BlackDiamond 8800 c-, e-, xl-series
with eight modules of 48 ports
8900-G96T-c modules
Summit series
383
767
767
One less than the
number of
available user
ports
of private VLANs with an IP
address on the network VLAN.
NOTE: This limit is dependent on
the maximum number of private
VLANs in an L2-only environment if
the configuration has tagged and
translated ports.
Summit X770, X460, X480
Summit X670
Summit X440
All other platforms
1,024
2,046
256
512
Limits
of private VLANs in an L2-only
environment.
BlackDiamond 8800 c-, e-series
E4G-200
E4G-400
Summit X440
Summit X480
Summit X670
Summit X460
Summit X770
384
2,046
2,046
597
1,280
254
2,046
597
820
1,282
PTP/1588v2 Clock Ports Summit X770 and
E4G cell site routers
32 for boundary
clock
1 for ordinary
clock
PTP/1588v2 Clock Instances Summit X770 and
2 combinations:
Transparent
clock +
ordinary clock
Transparent
clock +
boundary
clock
PTP/1588v2 Unicast Static Slaves Summit X770 and
40 entries per
clock port
PTP/1588v2 Unicast Static Masters Summit X770 and
10 entries per
clock type
Route policiessuggested
maximum number of lines in a
route policy file.
RIP neighborsmaximum number
of RIP neighbors.
E4G-200 256
RIP interfaces on a single router
of RIP routed interfaces on a
switch.
Summit X440
Summit X460
Summit X480
Summit X670, X770
E4G-400
256
256
384
128
256
384
256
256
Limits
RIPng learned routesmaximum
number of RIPng routes.
Summit X480
Summit X460, X670
Summit X770
E4G-400
E4G-200
3,000
3,000
5,000
5,000
3,000
10,000
3,000
10,000
Spanning Tree (maximum
STPDs)maximum number of
Spanning Tree Domains on port
mode EMISTP.
All platforms (except Summit X430 and
Summit X440)
Summit X440
Summit X430
64
32
16
Spanning Tree PVST+maximum
number of port mode PVST
domains.
NOTE:
Maximum of 10 active ports per
PVST domain when 256 PVST
domains are configured.
Maximum of 7 active ports per
PVST domain when 128 PVST
domains are configured.
switches
Summit X670, X770
Summit X460, X480, X440
Summit X430
E4G-400
256
256
128
50
128
Spanning Treemaximum number
of multiple spanning tree instances
(MSTI) domains.
Summit X440)
Summit X440
Summit X430
64
32
5
of VLANs per MSTI.
NOTE: Maximum number of 10
active ports per VLAN when all
500 VLANs are in one MSTI.
All platforms (except Summit X460,
X440, X430, and E4G-400)
Summit X460 and E4G-400
Summit X440
Summit X430
500
600
250
100
of VLANs on all MSTP instances.
All platforms (except Summit X460,
X440, X430, X770, and E4G-400)
Summit X460, X770, E4G-400
Summit X440
Summit X430
1,000
1,024
500
200
Spanning Tree (802.1d domains)
maximum number of 802.1d
domains per port.
All platforms 1
Limits
Spanning Tree (number of
ports)maximum number of ports
including all Spanning Tree
domains.
Summit X440)
Summit X440
Summit X430
4,096
2,048
1,024
Spanning Tree (maximum
VLANs)maximum number of STP
protected VLANs (dot1d and
dot1w).
Summit X770
Summit X460 and E4G-400
Summit X430
All other platforms
1,024
1,024
600
128
560
SSH (number of sessions)
maximum number of simultaneous
SSH sessions.
All platforms 8
Static MAC multi-cast FDB
entriesmaximum number of
permanent multi-cast MAC entries
configured into the FDB.
Summit X460, X480, X670, X430
E4G-400
1,024
1,024
1,024
1,024
Syslog serversmaximum number
of simultaneous syslog servers that
are supported.
All platforms 4
Telnet (number of sessions)
maximum number of simultaneous
Telnet sessions.
All platforms 8
TRILLtrees rooted from switch BlackDiamond X8
Summit X670, X770
1
1
TRILLcomputed trees BlackDiamond X8
Summit X670, X770
1
1
TRILLTRILL VLANs BlackDiamond X8
Summit X670, X770
4
4
TRILLforwarding VLANs BlackDiamond X8
Summit X670, X770
4,095
4,095
TRILLforwarding ports BlackDiamond X8
Summit X670, X770
All
All
TRILLRBridge FDB entries BlackDiamond X8
Summit X670
Summit X770
128,000
128,000
288,000
TRILLECMP RBridge next hops BlackDiamond X8
Summit X670, X770
8
8
Limits
TRILLneighbor adjacencies BlackDiamond X8
Summit X670, X770
32
32
TRILLnodes BlackDiamond X8
Summit X670, X770
256
256
TRILLlinks BlackDiamond X8
Summit X670, X770
2,000
2,000
Virtual routersmaximum number
of user-created virtual routers that
can be created on a switch.
NOTE: Virtual routers are not
supported on Summit X440 series
switches.
BlackDiamond 8000 c-, xl-, xm-series
E4G-200, E4G-400
Summit X460, X480, X670, X770
63
63
63
63
Virtual router forwarding (VRFs)
maximum number of VRFs that can
be created on a switch.
NOTE: * Subject to other system
limitations.
BlackDiamond 8000 c-, xl-, xm-series
Summit X460, X480, X670, X770
E4G-400, E4G-200
960 *
Virtual router protocols per VR
maximum number of routing
protocols per VR.
All platforms 8
Virtual router protocols per
switchmaximum number of VR
protocols per switch.
All platforms 64
VLAN aggregationmaximum
number of port-VLAN
combinations on any one
superVLAN and all of its
subVLANs.
Summit X440
1,000
256
VLANsincludes all VLANs. All platforms 4,094
VLANsmaximum number of port-
specific tag VLANs.
Summit X480, X670, X670V-48t,
BlackDiamond 8800 xl-series only,
Summit X460, X770, X480 E4G-400,
BlackDiamond X8 xl-series
E4G-200
1,023
4,093
2,047
VLANsmaximum number of port-
specific tag VLAN ports
Summit X480, X460, X670, X670V-48t,
BlackDiamond 8800 xl-series only,
BlackDiamond X8, E4G-400, E4G-200
BlackDiamond X8 xl-series
Summit X770
Summit X480
4,096
32,767
8,192
16,383
Limits
VLANs (Layer 2)maximum
number of Layer 2 VLANs.
All platforms 4,094
VLANs (Layer 3)maximum
number of Layer 3VLANs.
All platforms 2,000
VLANs (maximum active port-
based)(Maximum active ports
per VLAN when 4,094 VLANs are
configured with default license)
Summit X670, X480, X460, X770
E4G-400
Summit X440
E4G-200
Summit X430
32
32
16
12
1
VLANs (maximum active
protocol-sensitive filters)
number of simultaneously active
protocol filters in the switch.
All platforms 15
VLAN translationmaximum
number of translation VLANs.
Assumes a minimum of one port
per translation and member VLAN.
with eight modules of 48 ports
8900-G96T-c modules
Summit series
383
767
767
One less than the
number of
available user
ports
number of translation VLAN pairs
with an IP address on the
translation VLAN.
NOTE: This limit is dependent on
the maximum number of
translation VLAN pairs in an L2-
only environment if the
configuration has tagged and
translated ports.
Summit X770, X460, X480
Summit X670
Summit X440
All other platforms
1,024
2,046
256
512
number of translation VLAN pairs
in an L2-only environment.
BlackDiamond 8800 c-, e-series
Summit X460
E4G-400, E4G-200
Summit X440
Summit X480, X670, X770
Summit X430
384
2,046
2,046
2,000
2,000
512
2,046
100
Limits
VRRP (v2/v3-IPv4) (maximum
instances)maximum number of
VRRP instances for a single switch,
with Advanced Edge license or
higher.
BlackDiamond X8, 8800 c-series MSM-
48c, and BlackDiamond 8900 xl-series
8900-MSM128
Summit X770, X670
E4G-200, E4G-400
Summit X460
Summit X480
Summit X440
511
511
255
255
511
30
VRRP (v3-IPv6) (maximum
instances)maximum number of
VRRP instances for a single switch,
with Advanced Edge license or
higher.
(VRRP-VRRPv3-IPv6)
BlackDiamond X8, 8800 c-series MSM-
48c, and BlackDiamond 8900 xl-series
8900-MSM128
Summit X770, X670
E4G-200, E4G-400
Summit X460
Summit X480
Summit X440
511
511
255
255
255
15
VRRP (v2/v3-IPv4/IPv6)
(maximum VRID)maximum
number of unique VRID numbers
per switch.
All platforms with Advanced Edge license
or higher
7
(maximum VRIDs per VLAN)
maximum number of VRIDs per
VLAN.
or higher
7
VRRP (maximum ping tracks)
maximum number of ping tracks
per VLAN.
or higher
8
VRRP (v2/v3-IPv4) (maximum
ping tracks)maximum number of
ping tracks per VRRP Instance
under 128 VRRP instances, with
Advanced Edge license or higher.
All platforms, except the Summit X440
Summit X440
Hello interval: 20 centiseconds
Hello interval: 1 second
8 (20
centisecond or 1
second hello
interval)
2
4
VRRP (v3-IPv6) (maximum ping
tracks)maximum number of ping
tracks per VRRP Instance under 128
VRRP instances, with Advanced
Edge license or higher.
All platforms, except the Summit X440
Summit X440
Hello interval: 20 centiseconds
Hello interval: 1 second
8 (20
centisecond or 1
second hello
interval)
1 (IPv6)
1 (IPv6)
Limits
(maximum iproute tracks)
maximum number of IP route
tracks per VLAN.
or higher
8
maximum number of VLAN tracks
per VLAN.
or higher
8
XML requestsmaximum number
of XML requests per second.
NOTE: Limits are dependent on
load and type of XML request.
These values are dynamic ACL data
requests.
with 100 DACLs
with 500 DACLs
with 100 DACLs
with 500 DACLs
Summit X480, X670
with 100 DACLs
with 500 DACLs
10
3
10
3
4
1
XNV authenticationmaximum
number of VMs that can be
processed (combination of local
and network VMs).
All platforms 2,048
XNV database entriesmaximum
number of VM database entries
(combination of local and network
VMs).
XNV database entriesmaximum
number of VPP database entries
(combination of local and network
VPPs).
All platforms 2,048
XNV dynamic VLANMaximum
number of dynamic VLANs created
(from VPPs /local VMs)
All Platforms 2,048
XNV local VPPsmaximum
number of XNV local VPPs.
All platforms
(except Summit X430)
Ingress
Egress
Summit X430
Ingress
2,048
512
1,024
XNV policies/dynamic ACLs
maximum number of policies/
dynamic ACLs that can be
configured per VPP.
o
All platforms
Ingress
Egress
Summit X430
Ingress
8
4
8
Limits
XNV network VPPsmaximum
number of XNV network VPPs.
o
All platforms
Ingress
Egress
Summit X430
Ingress
2,048
512
1,024
a. The table shows the total available.
b. Limit depends on setting configured for configure forwarding external-tables.
c. When there are BFD sessions with minimal timer, sessions with default timer should not be used.
d. Based on forwarding internal table configuration "l2-only.
e. Effective capacity varies based on actual MAC addresses and VLAN IDs used and hash algorithm selected.
f. Applies only if all enabled BlackDiamond 8000 I/O modules are BlackDiamond 8000 c-, xl-, or xm-series modules.
g. Effective capacity varies based on actual IP addresses and hash algorithm selected, but is higher for BlackDiamond 8000 c-, xl-,
xm-series modules, BlackDiamond X8, E4G cell site routers, and Summit X460, X480, and X670 switches compared to
BlackDiamond 8000 e-series modules.
h. For the MVR feature in the BlackDiamond X8 series switches, the number of senders applies only when there are few egress VLANs
with subscribers. If there are many VLANs with subscribers, the limit is substantially less. Only 500 senders are supported for 100
VLANs. It is not recommended to exceed these limits.
i. Based on forwarding internal table configuration "l3-and-ipmc.
j. The limit depends on setting configured with configure iproute reserved-entries.
k. Based on forwarding internal table configuration "l3-and-ipmc".
l. The IPv4 and IPv6 multi-cast entries share the same hardware tables, so the effective number of IPv6 multi-cast entries depends on
the number of IPv4 multi-cast entries present and vice-versa.
m. If IGMP and MLD are simultaneously configured on the switch, the number of effective subscribers supported would be
appropriately lessened.
n. Sum total of all PBR next hops on all flow redirects should not exceed 1024.
o. The number of XNV authentications supported based on system ACL limitations.
Limits
3
Open Issues, Known Behaviors,
and Resolved Issues
This chapter describes items needing further clarification and behaviors that might not be
intuitive. It also includes the items that have been resolved.
Open Issues on page 85
Corrections to Open Issues Table on page 105
Known Behaviors on page 109
Resolved Issues in ExtremeXOS 15.4.2-Patch1-3 on page 118
Resolved Issues in ExtremeXOS 15.4.2 on page 121
Resolved Issues in ExtremeXOS 15.4 on page 133
Open Issues
The following are the open issues for supported features in ExtremeXOS 15.4.2-Patch1-3.
NOTE
Extreme Networks is transitioning to a new software defect numbering system. Previously,
software defect ID numbers were prefaced with the letters PD; they will now be
prefaced with XOS. During this transition period, some software defects will have the
old format ID and some will have the new one.
Table 2: Open Issues, Platform-Specific and Feature PDs
ID Number Description
General
xos0052480 Pinging an IPv6 destination address produces an error message and
doesnt succeed even though the destination address is reachable via IBGP/
EBGP. With the configuration the same, but with an IBGP equivalent static
route created, pinging the destination succeeds.
PD4-4348784051 Enabling third-party optics does not prevent log message about unlicensed
optics to appear.
PD4-4326818358 Kernel error messages should provide additional debug information
regarding the failure encountered.
PD4-4402508304 IPFIX tags 152 (flowStartMilliseconds) and 153 (flowEndMilliseconds) should
be added to the existing IPFIX template.
PD4-4119732781 The below statement appears multiple times for the command install
image: "This image will be used only after rebooting the switch!"
PD4-4150425121 Disabled is listed as a link state in show sharing command, but the
command disable port changes the link state to R. Since disabled is a
port state, not a link state, it should not be listed.
PD4-4017947496 Ports do not go to down state (through Tri Speed BASET link) while
executing command debug hal configure ports <ports-list>
link down.
Open Issues, Known Behaviors, and Resolved Issues
PD4-3387133462 The command show cli commands displays an infinite list of repeated
commands.
PD4-3822705407 Process netTools ends unexpectedly with signal 6 when creating a row in
the pingCtlTable with pingCtlTestName length greater than 31 bytes.
PD4-3800664331 SNTP cannot be enabled at the same time as NTP is enabled, but you can
enable both NTP and SNTP at a time while executing the command in the
order 1.enable ntp 2.enable sntp.
PD4-3937931224 With multiple IP address movement and parallel mode on one VLAN and
sequential on another VLAN, parallel DHCP discovery is not sent for all the
secondary IP addresses configured.
PD4-3674095924 AvgFlr is always greater than maxFlr(100000) when doing an SNMP walk
on MIB objects: mefSoamLmCurrentAvailStatsBackwardAvgFlr
,mefSoamLmCurrentStatsForwardAvgFlr,mefSoamLmHistoryAvailStatsForw
ardAvgFlr, mefSoamLmHistoryStatsForwardAvgFlr.
PD4-3581580021 ACL with deny action not working with ARP traffic.
PD4-3658579481 Frame-loss measurements are not working on LAG ports in EXOS 15.4.1, for
Summit X460 stacks and BlackDiamond 8800 series switches.
PD4-3803762611 Pinging an IPv6 destination address produces an error message and
doesnt succeed even though the destination address is reachable via IBGP/
EBGP. With the configuration the same, but with an IBGP equivalent static
route created, pinging the destination succeeds.
BlackDiamond 8800 Series Switches
xos0056040 In BlackDiamond 8800 series switches, some IPv4 routes are not installed
in routing table when the order of route advertisement is changed. Also,
behavior is different across different platforms.
PD4-4362816466 On BlackDiamond 8800 series switches, applying a policy file to all port
produces an error message that the rule hardware was "full for vlan *, port
2:96". The error messages start with port 2:8 and go through port 2:96.
PD4-4144185567 <Erro:HAL.MPLS.Error> MSM-A: Unable to get slot/port for modid/port: 0/
30.
PD4-4216890981 Kernel module exvlan ends unexpectedly while disabling/enabling trunk
ports.
PD4-4169800701 When rebooting BlackDiamond 8900 Xl and Summit X480 series switches
with maximum supported external routes, OSPF neighbors stay in loading
state.
PD4-4030640832 Ports stop forwarding traffic when egress mirroring is configured on some
other port.
PD4-4110051877 Process rtmgr ends unexpectedly with signal 6 immediately after slot 4
goes to failed state due to async queue growing:
Process rtmgr pid 1358 died with signal 6 Code: 497670 24630001
addiu v1,v1,1 497674 1469fffb bne v1,t1,0x497664 497678 24c60004
addiu a2,a2,4 49767c <11000008>beq t0,zero,0x4976a0 497680
24a50004 addiu a1,a1,4 497684 8d030090 lw v1,144(t0) 497688
25290001 addiu t1,t1,1 49768c 08125d8d j 0x497634
PD4-4231366171 Slots 9 and 10 are not recognized by OpenFlow.
Table 2: Open Issues, Platform-Specific and Feature PDs (Continued)
PD4-3840526049 On a switch in edge mode, if you configure OSPF on about four VLANs
that are configured you get the following warning message:
* (Engineering) X670V-48t.36 # config ospf add vlan all area 0 Error:
Unsupported command for OSPF Edge system We need to enable ospf on
vlan individually. But configuring vlan with ipv6 mode and enabling ospfv3
on all vlan at a time is allowed. * (pacman debug) X460-48t.52 # config
ospfv3 add vlan all area 0 * (pacman debug) X460-48t.53 #
PD4-3724972621 OSPFv3 neighbors stay in initial state after installing ExtremeXOS 15.4.1.
BlackDiamond X8 Series Switches
PD4-4396564007 Identity-management entries display IP addresses in reverse order in both
the CLI and MIBs. For example, 10.54.21.101 appears as 101.21.54.10.
PD4-4110051926 Watchdog reboots management module (MM) when a neighboring switch
reboots.
PD4-4105627707 DHCP packets from sub-VLANs are not egressing through the super VLAN
ports.
PD4-4160801166 I/O slots fail while trying to create 1K access VLANs in BlackDiamond series
switches which are TRILL edge RBridges.
PD4-4187112470 Soft watchdog expiration and kernel thread stuck when IPv6 traffic is
received on an ECMP set.
PD4-4184425081 Backup management module is incorrectly reporting fabric module slot as
empty after running diagnostics.
NOTE: This occurs only if you run diagnostics on the slots and the backup
management module simultaneously.
PD4-4144590128 The error <Erro:HAL.MPLS.Error> MM-A: ILM instance 872677376 not
found appears after issuing the command clear counters mpls
rsvp-te.
PD4-4230199725 When VRRPv6 (BlackDiamond X8 is VRRP master) and router-discovery is
enabled on the VLAN, switch is not sending router-advertisement packets
with source MAC VMAC. Switch is sending single router-advertisement
packet with source MAC physical switch MAC. The switch has to send
another router-advertisement packet with source MAC as VMAC and it
contains prefix information.
PD4-3979046745 The "Hop Count Check Fail Drops" counter in the show trill counter
command output is not incrementing when it receives hop counter = 0
TRILL frames. This issue does not occur on Summit X670 series switches.
PD4-3956394996 Get bulk on last OID on MIB tree is supposed to respond with a single
varBind containing endOfMibView exception, but for the Extreme MPLS
MIB, the get-next operation failed or had errors.
PD4-3937468363 The ISISv6 L2 adjacency state flaps as down/up with ECMP routes and
unidirectional traffic. The following are the associated log messages:
08/12/2013 20:47:34.10 <Info:ISIS.NFSM.AdjChg> v4-0004.9652.B4C9
(LAN): level 2 state changed LAN Neighbor Up -> LAN Neighbor Down
(LAN): level 2 state changed LAN Neighbor Down -> LAN Neighbor Init
(LAN): level 2 state changed LAN Neighbor Init -> LAN Neighbor Up
(LAN): level 2 state changed LAN Ne
PD4-3936923037 ISIS IPv6 ECMP traffic is not flowing. This issue does not occur with ISIS
IPv4.
PD4-3936419583 The command unconfig vlan ipv4 ipaddress causes ISIS ipv6
adjacencies.
PD4-3830266601 Occasionally, after executing the command config ports all
partition 4x10G, the following error message appears:
"<Erro:HAL.Sys.Error> MM-A: pibPortPktBufLog: getPifBySlotPort failed,
slot 1 port 5:
PD4-3929327296 With export e-BGP enabled, ISIS L2Ext routes are removed in level-1-2
when disabling/enabling slots.
Workaround: Save, and then reboot, the switch. All ISIS L2Ext routes are
installed properly.
PD4-3924997996 ISISv6 adjacencies keep flapping even though all ports are up after
executing the command disable/enable slot <slot number>.
PD4-3917270947 After management module failover the following error message appears:
<Erro:Kern.MPLS.Error> Slot-6: Ingress EXP MAP create failed on unit = 2
rv = -17 (Feature not initialized)
PD4-3810364861 The IPv4 address in the command show isis neighbor detail
appears in the reverse order.
PD4-3927637491 Process mpls ends unexpectedly with signal 11 on LSR node after changing
the LSP path from secondary to primary on PE node.
PD4-3941294703 While VPLS and L3VPN traffic is flowing, disable OSPF, wait for few
seconds, and then disable MPLS. After about five minutes, enable MPLS,
and then enable OSPF. This sequence of commands may cause the switch
to stop responding.
PD4-3764665205 Tree insertion fails after restarting ports with traffic flowing bidirectionally.
Summit Series Switches
xos0056225 With switches that are VRRP active-active masters with IPv6 addresses
configured, executing the command restart ports all, and then
immediately executing restart process vrrp produces the
following error:
<Erro:Kern.Error> exvlan: exvlan_ioctl_handler:3061:
ERROR: failed to configure 0x29 for
fe80:0000:0000:0000:0000:0000:5e00:0201/64, ifindex:
3023: -17
Workaround: Wait for VRRP instances to return to master state after
executing restart ports all before executing restart process
vrrp.
xos0056028 With switches that are VRRP active-active masters with IPv6 addresses
configured, the following critical error messages appear when executing
the command restart ports all:
<Crit:VRRP.System.SyscallFail> System call sendmsg()
failed: Invalid argument. Advert not sent.
PD4-4324594141 Some traffic loss can occur with CEP in L2.
Workaround: Delete, and then re-add L2 CEP.
PD4-4300989301,
PD4-4350150176
Summit series switches do not provide correct information on whether or
not fans are field replaceable (this information is not exposed through CLI
commands, but can be seen through SNMP queries).
PD4-4464975979 On Summit X770 series switches, partitioned 10G ports 77, 78, 81, and 82
do not appear in the output of the command edp ports all. As a
result, bi-directional traffic across these ports does not flow even though
the ports are up with speed 10G.
Workaround: For Summit X770 series switches, use 4952 in 40G, unless
153 are all partitioned for 10G. Use 101104 in 40G, unless 53104 are all
partitioned for 10G. When stack support is enabled on 103104, 101102
should be configured in 40G mode.
PD4-4234323829 EDP ports do not appear between two Summit X770 series switches when
disabling stacking support in a switch when all ports 1102 are partitioned
to 10G.
Workaround: If ports 53 through 102 are all 10G and stacking support is
enabled, then after disabling or unconfiguring stacking support,
reconfigure 101104 as all 10G or all 40G.
PD4-4248871785 On Summit X770 series switches, after setting up ACLs on VLANs with
jumbo frames enabled on all ports, disabling jumbo frames causes a
process to end unexpectedly and the switch is rebooted.
PD4-4218939786 On Summit X770 40G ports, with forwarding mode CT for both IXIA and
Summit X770 switch, RFC 2544 throughput testing shows variations in
maximum latency.
PD4-4237748957 On Summit X770 series switches, after removing fan module 1 from fan tray
1, the show fan command doesnt display information about other
connected fan modules.
PD4-4399373411 On Summit X440 stacks, when trying to enable static load sharing with
custom algorithm, an error occurs.
PD4-4406011663 On Summit X440 stacks, setting the source-address to 'mac' or 'ip',
assigning a policy to an IDM role, and then refreshing the policy causes
polMgr to stop responding because IdMgr does not clean up the policies in
the primary or backup nodes and they are not in sync.
PD4-4348079554 AVB is not supported on Summit X770 series switches. Time stamp support
for gPTP should be added for the platform.
PD4-4275071431 MLAG performance (switchover time after link failure, FDB check pointing
after ISC link goes up, etc.) on single-link connections between MLAG
nodes and peer switches are not consistent with multiple iterations.
PD4-4255808573 When MLAG ports are enabled/disabled, <Crit:VSM.ParmInv> messages
appear:
<Crit:VSM.ParmInv> : Argument Ingress Port Instance
has an invalid value 16777217
07/30/2012 22:22:37.27 <Erro:Kern.Error> : exvlan:
handleVsmKernelRequest:7311: handleVsmKernelRequest
Invalid Ingress port: 1000001 got
PD4-3939429048 40G ports connected with passive copper cable or 3M fiber cable (using
Q+SR4) are flapped more than once after detecting transceiver medium on
Summit X770 series switches.
PD4-4198495910 On Summit X670 series switches with correlated QoS profiles (QP2QP6)
created and mapped on the RBridges, when the native traffic has priority
value in the 802.1Q tag set to a value other than 0 (15), the RBridge is only
replacing the 802.1Q tag in the inner tag, but not in the outer tag for
ingress unknown unicast or multicast traffic. This works correctly for known
unicast traffic.
PD4-4092831911 Netlogin is disabled on a port after deleting destination VLAN that is part
of a private VLAN.
PD4-4120826241 DRB does not show the AF assignments of a third RBridge on the link.
PD4-4214138427 Summit X670 series switches take 25 minutes to delete an active port from
511 VRRP VLANs configured over user VRFs.
PD4-4055849611 Summit X480 series switches stop responding when there is a link flap with
BGP neighbor (BGP neighbor from Internet routing table is learned).
Application watchdog ends process 1084 (epm) in state 2. Process epm pid
1084 ends unexpectedly with signal 6.
PD4-4219628311 The following error message appears when disable mirroring in a Summit
X670v stack:
<Erro:HAL.Port.Error> Slot-1: SFP I2C read/write
failure 2480 <Erro:HAL.Port.Error> Slot-1: Failed
configuring speed 10 Gbps for tri-speed SFP on port
1 due to hardware error <Erro:HAL.Port.Error> Slot-
1: Failed configuring speed for multi speed SFP
onport 1 <Erro:HAL.Port.Error> Slot-1: Failed to
reinstate auto-negotiation to off on port 1:1 (rv=-
1) <Erro:HAL.Port.Error> Slot-1: SFP I2C read/write
failu This issue is not observed with Everest
platforms
PD4-4161633135 On Summit X670 series switches, for a VPLS with two peers, the second
peer counter display is wrongly aligned in output of command show mpls
statistics l2vpn (second peer has extra space at start so RxBytes
value is displayed near TxPackets column).
PD4-4267031486,
PD4-4038790514
In Summit X460 series switches, the 10G links from XGM modules flap at
random times.
PD4-4195503161 Memory leaks occur and system stops responding when 200 (S;G)s are
forwarded towards a large number of PIM-enabled VLANs. Each VLAN
contains several ports with IGMP receivers present.
PD4-4109718552 On Summit X770 series switches, unconfig mgmt ipaddress does
not clear the established telnet/SSH session.
PD4-4195077796 On Summit X460/X440 stack, standby node is not coming up after the
stack disable/enabled command from the standby node.
PD4-4120672546 ARP learning is not occurring for wire-rate ARP request traffic (after save
and reboot) in management port.
PD4-4045566743 On Summit X670 stack, kernel errors occur after deleting EAPS domain:
<Erro:Kern.Card.Error> Slot-2: exvlan:
setVpifState:3013: KERNEL_EXVLAN_ERROR: failed to
find VPIF 50001850 [slot 256 port 3] on VLAN
1000027
PD4-4045566731 On Summit X670 series switches, when LACP sharing is disabled, the
following error messages appear:
09/24/2013 13:33:09.46 <Warn:HAL.Card.Warning> Slot-
1: Function pointer is not initialized. Caller:
0x422e18 Parm1: 0x1000002 Parm2: 0xf4248 Warning:
Any config on the master port is lost (STP, IGMP
Filter, IGMP Static Group, MAC-Security, CFM, TRILL,
etc.)
09/24/2013 13:33:09.71 <Warn:HAL.FDB.Warning> Slot-2:
pibAddPortCPUFilter(2:6, 6, 00:e0:2b:00:00:04, 21, 0)
- MAC/STP/Flood mismatch for CPU filter.
PD4-4215590681 On Summit X770 series switches, you cannot enable stacking-support
when all ports are partitioned to 10G.
PD4-4213145609 Kern card error message appear after run failover on Summit X770 160G
series switches when all partitioned 10G ports are in the default VLAN:
<Erro:Kern.Card.Error> Slot-1: VLAN Set untagged
port(u 0, p 59, v 1) returns error - Operation
timed out
<Erro:Kern.Card.Error> Slot-1: InstallRule:
bcm_field_entry_install returned "Operation timed
out"(-9) for group_pri 11 group_id 2, rule_id 1063
rule_pri 4087(unit 0) <Erro:HAL.VLAN.Error> Slot-2:
bcm_port_ipmc_enable failed for slot 1, port: 100 rv
-9
PD4-4231373074 Both TRILL data traffic and native frame traffic are getting dropped at the
edge TRILL switch after the next hop goes down.
PD4-4082817071 On Summit X480 series switches, ISIS adjacencies are flapping
continuously after adding 100 VLANs to ISIS (scaled scenario).
PD4-4157261364 On Summit X670 series switches when CEP and CNP is configured on LAG
ports, CEP grabs all the packets (even out of range VID streams and
untagged streams are flowing through CEP).
PD4-4202493957 L3 routing deny action is not working for L3 routing traffic on Summit
X770 320G stacking. Works fine on Summit X770 160G stacking.
PD4-4131287631 On Summit X440 series switches, policy manager hangs up while changing
the source-address mode from MAC to IP, and then back to MAC. This
occurs when refreshing the policy mapped to the IDM role.
PD4-4182004031 For Summit X460 series switches, switch HAL and OpenFlow processes go
high when adding a large amount of flows (~2,000).
PD4-4165740580 On Summit X770 series switches, stack goes to dual-master condition after
run failover with L2 or L3 traffic.
PD4-4162653370 Stack port state goes to "No Neighbor" after slot is rebooted or after run
failover in 160G Summit X770 stack while sending line rate traffic (flooding,
unicast, or broadcast traffic). Stack port state is operational after rebooting
the stack or some times after removing, and then re-inserting that
particular link, so that in a daisy chain topology rebooting the whole stack
splits the system into two separate stacks.
PD4-4108843431 Add warning for PoE firmware upgrade.
PD4-4136843075 Getting internal error messages while looking at egress port qosmonitor
after issuing any QoS command such as: enable diffser exam
port all, enable diffser repla port all, disable
diffser exam port all, or disable diffser repla port
all:
* (Beta) Slot-1 Stack.34 # sh port 1:93 2:73
qosmonitor Error: Internal error --> no response to
stats request for port 1:93.
PD4-4108881531 When sending packet out messages to controller for 1 to N dataplane ports,
the packets didn't appear on the output ports. Incorrect port errors.
PD4-4199493591 On Summit X440 series switches with around 500 identities, on restarting
the Idmgr process, the idmgr process ends unexpectedly with signal 11.
PD4-4214505021 On Summit X770 series switches, VRRP traffic convergence time is greater
(10 seconds) after rebooting the VRRP master compared to Summit X460
and X670 (3 seconds) series switches. The switch has VRRP and OSPF for
forwarding traffic to uplink.
PD4-4198620031 On Summit X670 series switches, parallel network ports to generic L2
switch causes multicast traffic looping after transient network events.
PD4-4170673942 Packet buffer cells are not drained out when fabric flow control is disabled
in a stack and also when PFC RX pause is disabled/enabled during user
stream and PFC frames are active in the switch.
PD4-4147204751 Untagged L2 traffic stops when one-to-many remote mirroring is enabled,
and then it doesn't resume when the mirroring is disabled.
Workaround: Remove affected ports from the VLAN, and then add them
back.
PD4-4141018861 On Summit X670 series switches, you are unable to scale FDB beyond
4,064 which are learned over pseudowires.
PD4-4113498130 On Summit X480 series switches, in BGP scaling environments when
disabling some IBGP or EBGP peers, some other sessions flap.
PD4-4113498121 On Summit X480 series switches, when re-advertising all routes, entire BGP
sessions go to idle, and then established after a couple minutes.
PD4-4157742201 In Summit X440 series switches, the process exsshd ends unexpectedly
with signal 11:
EFENCE enabled crash #0 ssh_event_handler
(program=program@entry=0x7fff7360) at ssh_event.c:1013 1013
if (idle->seconds > 0 &&
PD4-3996812307 In Summit X670 3-node stack, sometimes after reboot, the master and
backup nodes do not come in sync. Eventually, the following error appears:
--- Failed to checkpoint configuration: timed out
(after 500 seconds) while waiting for configuration
checkpoint save operation to finish ( hal is still
not saved) 09/05/2013 15:39:24.00 <Erro:cm.chkpErr>
Slot-1: Failed to checkpoint configuration: timed
out (after 500 seconds) while waiting for
configuration checkpoint save operation to finish (
hal is still not saved) ---
PD4-4214958167 On Summit X670 series switches, TRILL neighbors are not learned on the
TRILL switch after the next hop router goes down.
PD4-3996783004 Egress ACL in VMAN is not working in X480 series switches.
PD4-4200294671 In Summit X460 series switches in 511 VRRP scaling, while disabling a port
in the VRRP master, the state changes correctly again when enabling the
port. VRRP master backup state flapping in backup switch gets stuck.
PD4-3797993347 On Summit X440 stacks, running failover more than two or three times
causes the counter to fail to update in the new master.
PD4-4367864734,
PD4-3924998629
On Summit X460 series switches, process VLAN ends unexpectedly with
signal 11 during clean up.
PD4-3773002372 On Summit X440 series switches, clearing the policy counters produces the
error:
"6/07/2013 18:46:02.50 <Erro:HAL.IPv4ACL.Error> Slot-
2: Counter clear failed unit 9 rId 557 rv -13", but
the counter is still cleared. 11/08/2013 12:13:02.15
<Erro:HAL.IPv4ACL.Error> Slot-2: Counter flush
failed unit 17
PD4-3777036691 Kernel error occurs in the EMS log output when deleting the network VLAN
[PVLAN] in a MLAG environment.
PD4-3717316170 EAPS convergence time is more than 110 milliseconds on Summit X670
series switches.
PD4-3927303395 On Summit X670v series switches, switch stops responding after issuing
the command restart process isis in level 1-2 with unicast traffic.
Workaround: Remove, and then restore the power to the switch to make it
boot properly.
PD4-3900660089 On Summit X460/X670 series switches, system ends unexpectedly with
"Process isis pid 1599 died with signal 11" when deleting ISIS area with
multiple CSNPs configuration.
PD4-3723298881 LOG_PARAM variables in show upm history details command
shows the incorrect values.
PD4-3916116702 Kernel error occurs if egress ACL with {mirror-cpu; log} action is applied.
PD4-3805543771 RSTP port transition takes longer than usual to come to forwarding state if
STPD is disabled, and then enabled.
PD4-3877669812 For XNV NMS authentication, the command show vm-tracking shows
the incorrect VM IP address.
PD4-3973356901 gPTP: After increasing the priority1 value of the gPTP GM, the slave nodes
still receive the old priority value, and BMC selection fails.
PD4-3952055471 For Summit X440 series switches, the command show access-list
does not show the number of policies applied to a particular IDM role for a
particular port, even though the policies are applied successfully to the port
and the counter is incremented.
PD4-3968575921 AVB is not supported on the Summit X770 series switches. Time stamp
support for gPTP should be added for the platform.
PD4-4105541191 After disabling stacking, and then rebooting, 10G partitioned ports should
unconfigure and come back up as 40G ports. However, an additional
reboot of the switch is required to reset the ports.
PD4-3615311551 On Summit X670 series switches, untagged packets processed by
OpenFlow are being redirected with 802.1Q tags.
PD4-4051479591 Summit X770 series switches pseudowire statistics are not working.
PD4-3918240371 For Summit X440 series switches, executing a MAC move on a role-based
IDM-enabled port, and then changing it back to the original port, causes a
loop as log messages are logged continuously, which are particular to the
role-based VLAN, even though one port is inactive.
PD4-3918278631 Unable to clear the switch log using the command check policy
<policy_name> if the policy file does not exist on the switch.
PD4-3784308167 Do not use the CLI to manually delete FDB entries created by MSRP for
AVB streams. If you manually delete an FDB entry for an AVB stream, the
switch stops forwarding stream traffic until all listeners for the stream leave,
and then at least one listener re-joins the stream.
PD4-3796335941 MSRP propagation fails when egress rate limit is configured and then
unconfigured back to default no limit.
SummitStack
PD4-4204243320 With stacking enabled, the command configure stacking-support
stack-ports all selection native shows invalid options:
For Summit X480/X460 (SS), 80G/160G/320G options appear.
For Summit X770, 80G option appears.
For Summit X460/480 (ssv80), 160G/320G options appear.
Selecting an invalid option does not produce any errors.
PD4-4237002081 LACP does not form properly after executing restart ports when the
LACP ports are VPLS service ports (Stack node).
Workaround: Disable, and then enable sharing.
PD4-4110730965 Executing the command debug hal configure stacking port
1/2 disable in Summit X670v stack produces the following errors:
10/17/2013 05:25:21.31 <Erro:HAL.Card.Error> Slot-1:
Timed out waiting for response to query media type
slot 2 10/17/2013
05:25:26.31 <Erro:HAL.Card.Error> Slot-1: Timed out
waiting for response to query media type slot 2
0/17/2013 07:47:11.69 <Crit:NM.NodeStateFail> Slot-1:
Slot-2 has failed for the reason of "Dual Master".
10/17/2013 07:47:11.80 <Crit:NM.NodeStateFail> Slot-
1: Slot-4 has failed for the reason of
PD4-4144185547 Kernel errors occur when disabling MPLS on ingress LER (D15 and D16).
PD4-4174846660 In Summit X670-X670-X670-X770 stacks, it is taking around 15 minutes for
the stack ports on a Summit X770 to come up (to go to operational state)
when stack neighbor to the Summit X770 goes down and comes back up
(after failover).
PD4-4126410039 The following kernel errors are impacting VPLS sessions after rebooting
switch:
Oct 23 22:43:46 BA-CO-NSNP_75 <Erro:Kern.MPLS.Error>
(ems_main.c:447) Unable to destroy L3 egress
forwarding object for unit 0, egress obj = 100811,
returnCode = Entry not found
PD4-4230511805 IPv6 ping fails in stack and chassis in PSTag configuration.
PD4-4096933651 System stops responding with "process devmgr pid 1431 signal 5" error with
IPv6_Services clean up session in Summit X670v 160G stack.
PD4-4171709003 In Summit X670 stacks, the following error messages appear after
executing the command debug hal show optic-info slot 3,
and then saving and rebooting:
<Erro:HAL.Port.Error> Slot-3: getQSFPInfo(748) Error
reading eeprom <Warn:Kern.Card.Warning> Slot-3: i2c-
1: shid_eeprom_read:3244 I/O failed, addr 0x0050 rd/
wr 0 cmd 127 proto 1, rc 145 This is not observed
with 15_4_0_40 build
PD4-3837812966 Process exsh pid 1711 ends unexpectedly with signal 6 when you disable,
and then enable stack user ports multiple time using CLI scripting.
PD4-3819233111 Traffic is looping on stack ports in a Summit X480 stack after executing run
failover. System recovers (loop ends) after flapping stack ports in one of
the stack nodes.
PD4-3798455038 "Dropped CM_MSG" messages appearing while stack is booting up for the
fist time. Observed the following error messages when native v80 stack is
booting up for the first time:
Slot-5: Dropped CM_MSG_CHKP_STANDBY_BANNER_FROM_CFG:
Length 16 Peer 72 (primary) Slot-5: Dropped
CM_MSG_CHKP_STANDBY_BANNER_ACK: Length 14 Peer 72
(primary) Slot-5: Dropped CM_MSG_CHKP_STANDBY_BANNER:
Length 14 Peer 72 (primary) Slot-5: Dropped
CM_MSG_CONFIG_COREDUMP_STANDBY: Length 16 Peer 72
(primary) Slot-5: Dropped CM_MSG_CONFIG_STANDBY: Length 396 Pee
E4G-200 and 400 Cell Site Routers
PD4-4183447262 PTP state switches between normal loop and bridged in switch, when PTP
is configured over LAG/MLAG. Also, the mean path delay shows larger
values.
PD4-4183447243 PTP boundary clock functionality fails to work and fails to provide clock to
switches configured as unicast-slave on the switch, which has configuration
that uses more hardware filters.
PD4-4137916297 Frame loss availability status shows as unavailable even though LMMs are
sent and LMRs are received correctly.
PD4-3837445670 On E4G-200-12x cell site routers, BASET optics link comes up at 1 Gbps
when speed is set to 10Mbps. This issue does not occur when using BASET
to connect between E4G200/E4G400 cell site routers and Summit X460/
X480 series switches.
On E4G-200-12 cell site routers, BASET optics links do not come up after a
switch reboot and links are up on partner side. Only BASET links are
coming up after removing, and then inserting the BASET optics on the
E4G-200-12x cell site routers.
Workaround: Remove, and then insert the BASET optics on the E4G-200-
12x cell site router.
PD4-3787649088 On a configuration with L2 VPN and L3 VPNs, during reboot and when
performing a disable and then enable MPLS the following error messages
appear:
<Erro:Kern.MPLS.Error>
extreme_mpls_del_l3vpn_label_nhindex_xref: MPLS L3VPN
NH Index intf: 0x4c, label = 0x74, Entry not found
in btree rv = -7 (Entry not found)
ACLs
xos0057044 ARP-ACL match critera "arp-sender-address" and "arp-target-address"
does not work on BlackDiamond 8800 10G8Xc, G8Xc. G24Xc, G48Xc,
G48Tc, and 10G4Xc modules. The error message is:
create access-list a1 "arp-sender-address
10.10.10.11/24" "permit; count PacketCount1
PD4-4264913050 When a semicolon is missing from ACL matching criteria, the ACL process
ends unexpectedly.
PD4-3846657690 When creating a large number of super-VLANs and sub-VLANs, error
messages may appear regarding the lack of hardware resources to install
ACL rules.
PD4-4251345301 Egress-ACL counters do not work on the following (but not restricted to)
chassis-based platforms:
BlackDiamond 8800 G48Te, 10G4Xc, G24Xe, and 10G24Xc.
PD4-3932248611 Access-list counter stops working when applied to a VLAN.
PD4-3570615834 Able to create a static ACL from the policy file named "any.pol".
When using the command unconfigure access-list, the access-list
still remains and appears in the output of the show access-list
command. Because any is a keyword , the command unconfigure
access-list any is actually removing the ACL from wildcard,
including all VLANs and all ports, but not the ACL Itself. The switch does
not produce any error or warning messages if you create this access-list.
BGP
xos0056978 Issuing the command enable bgp neighbor <peer ipv6
address> twice causes BGP to send notification message to peer.
xos0056429 When restarting BGP process, error showing that neighborship registration
has failed appears repeatedly until the process restart completes.
Workaround: Wait for restart of BGP process to complete.
xos0055848 Export of BGPv6 routes through OSPFv3 does not occur after disabling,
and then enabling OSPF.
PD4-4078613531 After creating a BGP neighbor on a switch, but leaving it disabled, enable
graceful restart for BGP, and then restart BGP. Graceful restart takes 10
minutes when all configured peers are admin down.
PD4-3875291701 BGP is not choosing the EBGP route as the best route when it is received
by same nlri from many peers (both EBGP & IBGP).
PD4-3783767871 IPv6 multicast routes with longer AS paths are preferred over routes with
shorter AS paths after an export policy that appends an AS number is
configured on one peer. This issue does not occur for IPv6 unicast routes.
Workaround: Bounce BGP on the neighbor.
IP Routing Protocols
PD4-4308318263,
PD4-4308318281
When the PIM cache is populated with entries and SNMP bulkwalk is done
on the OID.
SNMPv2-SMI::experimental.61.1.1.4.1.7.225.1.1.1.50.1.1.2.255.255.255.255
The following errors appear:
(1) Address with invalid format [0] from Function
pimCache_t_get, Line 1320
pimRp_t_get, Line 2510
PD4-4068687011 BGP not handling dynamic VRF label changes.
PD4-4200853291 After a failover, RTMgr is not updating the rt table to reflect the use of a
RSVP-TE LSP.
PD4-4178014881 Watchdog expiration occurs while disabling the egress port of a VLAN
created in VRF. Switches continuously produce error messages. The
problem resolves only after the port is enabled.
PD4-3916642021 Traffic loss occurs when disabling or enabling ISIS or link flap on egress
with unicast traffic.
PD4-3940979242 ISIS process ends unexpectedly while configuring interlevel-filter with
lengthy policy file name.
PD4-3865161175 The process rtmgr ends unexpectedly with signal 11 while rebooting
neighboring switch. Core was generated by:
`./rtmgr update'.^M Program terminated with signal
11, Segmentation fault.^M #0 rtCloneRtForECMPRt
(destRt=destRt@entry=0x7fff63b8,
destGw=destGw@entry=0x7fff62e8, ^M
destV6Nh=destV6Nh@entry=0x7fff6450,
dImmdv6Nh=dImmdv6Nh@entry=0x7fff6440, srcRt=0x8f7068,
resGw=0x0)^M at rtMgrECMP.c:272^M 272
destRt->gw->immdNh = resGw->v4Nh;^M ^M
PD4-3865160334 The process rtmgr ends unexpectedly with signal 11 when rebooting a
neighboring switch:
\ Program terminated with signal 11, Segmentation
fault.^M #0 0x00445cac in rn_lookup_less
(n=<optimized out>, head=<optimized out>) at
radix.c:315^M 315 if (t->rn_bmask
& v[t->rn_off])^M
PD4-3924757043 On BlackDiamond X8 series switches, system ends unexpectedly with
process isis pid 7224 signal 6 after a run msm-failover with 110
adjacencies.
PD4-3924756921 ISISv6 routes with wide metric set are not installed in the routing table
even though they were learned from neighbor and installed in LSDB. Also,
ISISv6 routes with wide metric set are not get into routing table after
several reboots on a Summit X670v series switch. This issue does not occur
with IPv4 routes.
PD4-3874480036 On E4G cell site routers, OSPFv3 routes are learned correctly, and traffic is
not forwarding through OSPFv3 routes with configured neighbor-discovery
cache entry (static).
PD4-3910324705 In IPv4 ISIS L1 adjacency, L2 unicast traffic does not forward to egress port
in Summit X670v stack (160G). This issue does not occur with IPv6 ISIS L1
adjacency.
PD4-3910324621 ISIS adjacency is formed for IPv4 when one switch has IPv6 only and the
other switch has both IPv4 and IPv6 enabled.
PD4-3790035443 Disabling BGP export-policy in VPN VRF is not getting reflected in the
show configuration command.
PD4-3970398557 Cannot add DHCP-enabled VLAN into the ISIS domain.
PD4-3945032241 In ISISv6 while adding IPv6 VLAN into ISIS area, system stops responding
with process vlan pid 1433 died with signal 6" error.
PD4-3946303092 Without enabling wide metric, you are able to export IPv6 routes from
other protocols with metric greater than 64 into ISIS.
NOTE: For IPv4, router is it working.
PD4-3915306781 With graceful restart enabled, ISIS routes are withdrawn from adjacent peer
once after run msm-failover or restart process isis
(routes are re-advertised to adjacent only after adjacent reaches up state).
PD4-3861037262 No (S;G)s are created even if SAs are found in the MSDP SA cache. The
command pim show route does not display the route toward the
source, even if the routing table on the last hop router contains it via two
MEBGP paths.
PD4-3864392001 The following error messages are logged while executing run failover
or run msm failover:
07/15/2013 13:01:01.00 <Warn:Kern.IPv4FIB.Warning> Slot-5: dest
0x01010197 / 32 nexthop 0x05010402: Unable to add route to unit 0, rc
Entry exists. Shadow problem.
07/15/2013 13:01:01.01 <Warn:Kern.IPv6FIB.Warning>
Slot-5: dest 310A:0001:0004:0002:0000:0000:0000:0000
/ 64 nexthop 0000:0000:0000:0000:0000:0000:0000:0000
Unable to add route to unit 0, rc Entry not found.
Shadow problem
07/15/2013 13:01:01.01 <Warn:Kern.IPv6FIB.Warning>
Slot-8: dest 310A:0001:0004:0005:0000:0000:0000:0000
/ 64
PD4-3861037262 No (S;G)s are created even if SAs are found in MSDP SA cache. The route
to the source does not appear even if the routing table on the last hop
router contains it via two MEBGP paths.
PD4-3709468301 A last hop router without any upstream neighbors does not forward
received traffic towards its clients. This is seen when IGMP reports are
received after the traffic has been started. If IGMP reports are first received,
and then traffic is started, the last hop router forwards the traffic.
PD4-3786800615 Log message appears when PIM is enabled on the loopback VLAN.
PD4-3865986001 OSPF state moving from waiting to DR immediately after configuring the
priority value on the OSPF-enabled VLAN.
PD4-3861037251 Static multicast routes added with protocol OSPF have a higher preference
over MIBGP routes.
PD4-3824452831 The switch forwards traffic partially towards the client after the ingress port
is disabled, and then enabled.
PD4-3945032263 Executing the command enable isis area a100 export ipv6
ospfv3 FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF causes
the switch to fail and produce error: Process isis pid 7155 died with signal 6.
Workaround: Don't use all FFs export policy.
MLAG
xos0054332 Packet loss of up to 350 ms occurs when deleting member ports from ISC
LAGs.
xos0056324 On Summit X670 series switches, MLAG ports move to ready state after
issuing the commands restart ports all, and then restart
process vsm. LACP MLAG ports are removed from aggregator and not
added back.
Workaround: Disable, and then re-enable ports.
xos0056368 After disabling sharing over ISC ports when MLAG peers are up, the
following kernel errors appear:
<Erro:Kern.Error> exvlan:
MPLS
PD4-4402704521 The command configure vr delete vr-default protocol
mpls does not clear LSP counters (HAL outing label usage) from
hardware.
PD4-4127725131 The following kernel errors are impacting VPLS sessions after rebooting the
switch:
(Core VPLS node) 10/24/2013 06:23:13.43
<Erro:Kern.MPLS.Error> Slot-3: MPLS
bcm_tr_mpls_trunk_port_list_update(add) failed for
unit = 1 vpn = 0x7333, port = 0x800680d vp =
0x18000df0, rv = -14 (No resources for operation)
PD4-3515595431 The command show mpls label usage doesn't correctly show
outgoing label hardware capabilities.
PD4-3672329441 Can't configure the same egress label in different static LSPs.
PD4-3818120671 Process hal pid 7040 ends unexpectedly with signal 11 during CleanUp in
MPLS-OAM module. Problem occurs on new stackables, new stack, and
BlackDiamond 8800 series switches.
PD4-4163132141 VPLS CEP and ACL CVID Match Criteria : Egress ACL CVID match criteria is
not working properly on CNP (untagged VMAN port) when CEP is also
configured on the same port. It is working on Ingress side.
Workaround: Use the "vlan-id" match criteria, instead of the "cvid" match
criteria.
OpenFlow
PD4-4176554711 Number of transmitted packets for the OpenFlow queue Tx counter is not
updating correctly.
PD4-4182004725 A flow with double enqueue action is not adding.
PD4-4231366215 FDB entry idle timeout does not count down correctly and the entry is
installed as dynamic instead of static.
QoS
PD4-3834464406 The command show port 1:1 qosmonitor produces an internal
error after trying to clear the counter using "0" symbol.
Security
PD4-4418298177 With multiple IP address movement and parallel mode on one VLAN and
sequential on another VLAN, parallel DHCP discovery is not sent for all the
secondary IP addresses configured.
PD4-4315249830 With a mix of both valid and invalid policies, multiple role refreshes on
scaled users (512) causes a memory leak.
PD4-4315249822 Policies with unsupported attributes incorrectly cause ACLs to be installed.
SNMP
PD4-4326286751 Issuing the command snmpset to set string length to 1,500 causes the
error: Process snmpMaster pid 1826 died with signal 11.
PD4-4387181761 SNMP walk on ICMP MIB shows results for VR-mgmt for chassis and VR-
default for standalone Summit series switches when global statistics should
show consolidated statistics of all VRs, or show consistent information for
all platforms.
PD4-3995727641 SNMP user created with permanent storage-type is getting deleted even
after rebooting because of the no dirty bit set for the SNMP operation on
UsmEntry table.
PD4-4230220706 The trap ipv6IfStateChange is not fetching the instanceId, so the trap is
showing improperly.
PD4-3640633490 There is no provision for read only or Read/write modes for dynamic_rule
as access-profile.
PD4-3714872811 SNMP set on atTable is not working.
STP
PD4-3463519811 Tagged port is being removed from the MSTI Instance when the same port,
which is untagged in a different VLAN, is also binded to the MSTI instance.
PD4-3850592564 No warning message appears when deleting an STP-enabled LAG port (link
aggregation with LACP) from a VLAN, though the port is deleted from the
STP domain. However, when deleting a non-LAG port from the VLAN, the
following warning message appears: Warning: STP port (1:1) is lost due to
port is deleted from VLAN.
TRILL
PD4-4213803037 After installing ExtremeXOS 15.4.1, the following errors appear:
11/26/2013 15:24:28.38 <Erro:Kern.TRILL.Error>
extreme_custom_trill_l3_egr_obj_destroy_async_rtn:
TRILL Multipath Egress Object Destroy: nickname:
0x3a map entry not found in btree rv = -7 (Entry
not found)
11/26/2013 15:24:28.38 <Erro:Kern.TRILL.Error>
extreme_trill_del_nickname_egrobj_xref: TRILL
nickname = 0x3a gport = 0xffffffff, map entry not
found in btree rv = -7 (Entry not found)
PD4-4231373061 Broadcast traffic for a specific group of VLANs are getting lost after the
next hop is rebooted and then comes back up.
PD4-4017637045 Multicast traffic is not getting distributed across the LAG ports on the
native side after getting decapsulated at the RBridge.
PD4-3270556852 After changing the system-id (6 octets) to user defined rather than switch
MAC address, traffic forwarding stops.
PD4-3890107020 Remote native VLAN traffic is still forwarded/received at the local RBridge
even after deleting the access VLAN association.
PD4-3906172771 With correlated QoS profiles (QP2QP6) created and mapped on the
RBridges, when the native traffic has priority value in the 802.1Q tag set to
a value other than 0 (15), the RBridge is only replacing the 802.1Q tag in
the inner tag, but not in the outer tag for the ingress unknown unicast or
multicast traffic. It works correctly for known unicast traffic.
PD4-4160663867 In 3-node ring topology, after running restart trill network ports on switch1
and switch2 respectively, traffic forwarding does not resume on these
switches.
Workaround: Execute the command clear fdb.
VLANs
PD4-4165078759 Unable to ping network VLAN interface IP address from subscriber VLAN
side after executing the command restart process vsm on MLAG
switches and disabling ports on remote node.
PD4-4142830351 When an ARP request is sent from the isolated VLAN on one switch to the
network VLAN on another switch, there is no ARP reply after the IP
address of the network VLAN is unconfigured on the first switch.
PD4-4211546301 With loopback port configuration, known L2 traffic from network VLAN
port to isolated VLAN port should not get flooded.
PD4-4184397524 IP multicast traffic isn't being forwarded on the PSTAG VLAN when it is
sharing the same port as another VLAN that has IGMP snooping enabled.
VRRP
PD4-4134851121 IPv6 neighbor advertisements for VRRP VIP uses VMAC as source MAC
address instead of switch MAC address.
PD4-4092277711 In VRRP scaling environment, switches stop responding for 1318 seconds
while enabling and disabling VRRP. Switches execute commands after
opening another session on the switch.
Corrections to Open Issues Table
The following table lists open issues that were erroneously listed in the Open Issues table
(Table 2) of the previous revision of this release note for ExtremeXOS 15.4. These issues
have been removed from the current Table 2.
Table 3: Erroneously Listed Issues in the Open Table of ExtremeXOS 15.4
PD Number Description Reason Issue Was Removed
PD4-4235154651 Add a debug command to display
which ECMP gateway is used by
hardware given packet header
information.
Issue is a feature request, not an
issue.
PD4-3957503827 The show bootprelay counter
information in the backup is not in
sync with the master after failover.
Not found to be a problem.
PD4-4110051988 Process pim ends unexpectedly with
signal 11 while doing run
msmfailover in aggregation switch:
Process pim pid 1415 died
with signal 11 Code:
42cb2c 3c03004f lui
v1,0x4f 42cb30 8c635270
lw v1,21104(v1)
42cb34 8d020140 lw
v0,320(t0) 42cb38
<0810afcb>j 0x42bf2c
42cb3c ac4300d4 sw
v1,212(v0) 42cb40
93a20059 lbu v0,89(sp)
42cb44 00002021 addu
a0,zero,zero 42cb48
02202821 addu a1,s1,zero
42cb4c afa20010 sw
v0,16(sp)
Cannot reproduce this problem.
PD4-3741852522 After deleting VRRP instances,
switches fail to send a final VRRP
advertisement with priority = 0.
PD4-4215752740 Backup management module
reporting an I/O slot as empty when
the I/O card is present. This occurs
only when you run extended
diagnostics on the I/O cards and the
backup management module
simultaneously.
PD4-4085364300 Not getting PTP follow-up message
when Summit X770 series switches
are configured as 2-step PTP masters.
PD4-4175991254 Summit X460 series switches stop
responding after configuring 256
VLANs with IPv6 addresses.
PD4-3653301462 On Summit X670 series switches,
when scaling to 4,094 OpenFlow-
enabled VLANs on five ports, issuing
the command unconfig switch
all causes HAL process to end
unexpectedly.
OpenFlow cannot install default rules/
operate in external TCAM mode.
issue occurs when scaling to a
maximum number of VLANS (4,093),
disabling OpenFlow, and then
enabling OpenFlow. FDB logging
errors occur and a hung FDB default
rule is installed into the ACL manager.
OpenFlow is now stuck in the
connecting state and does not
reconnect to the controller.
Workaround: Reboot the switch.
PD4-3837405662 FDB is not learned properly when
client source MAC is learned from a
different port.
PD4-3782977647 When adding the dynamic VLAN
created by Netlogin to private VLAN
as the subscriber, the VLAN should
get deleted from the switch.
PD4-3633965825 After creating 256 VLANs, 1 CFM
domain, 256 associations, 256 end
points, and 256 CFM segments on
switches, enable LMM and DMM on-
demand transmission.
Now after performing an SNMP walk
on table
mefSoamLmCurrentAvailStatsTable,
restarting the process dot1ag, and
then performing an SNMP walk on
table
mefSoamLmCurrentAvailStatsTable,
an error occurs.
PD4-4114434094,
PD4-4114434171,
PD4-4114434254
The command unconfigure idm
doesnt delete IDM created by
enable idm command when there
arent any IDM-enabled ports.
PD4-3837031867 An SNMP set request for
trapDestTable to configure a trap
receiver fails.
PD4-3847762541 When switch receives IP address from
BootP server, the server IP address is
not displayed in the show dhcp-
client state command.
PD4-4154434642 Process netTools ends unexpectedly
with signal 11 when efence is enabled.
process etmon pid 1296 ends
unexpectedly with signal 6.
Not found to be a problem
PD4-4154434616 Process polMgr ends unexpectedly
with signal 6 when efence is enabled.
PD4-4128654311 Efence:
BGP_AllowLoopedAs_NewStack -
EFENCE Enabled for bgp process :
DCBGP crash with signal 11 while
issuing the command "configure bgp
peer-group peer1 dont-allowas-in".
Program terminated with signal 11,
Segmentation fault. This crash is
consistently happening in all BGP
modules in different command
execution. #0 0x2aee6e1c in
dispatchWorkCancel
(work=0x2c1cdf80) at dispatch.c:2222
2222 if (!work ||
!CHECK_TAG(work,
TAG_DISPATCH_WORK)) 2223
return DISPATCH_FAILURE;
PD4-4130606621 System ends unexpectedly with
"process isis pid 1590 signal 6" error
after executing the command debug
epm disable heapdbg
process all. This issue appears
one time out of five times with efence
enabled.
system ends unexpectedly with
"kernel oops" error while IPv6 VLAN
clean up session.
PD4-4228355471 System ends unexpectedly with
"Process devmgr pid 1448 died with
signal 5" error, during clean up
session.
PD4-3796335991 Excessive amount of time taken for
MSRP stream to switch over from one
port to another.
OSPF process ends unexpectedly with
signal 6.
PD4-3924668881 Switches report the following error
messages and watchdog reboots the
master node while traffic is running
over night:
<Warn:Kern.Card.Warning>
Slot-1: bcmRX: page
allocation failure.
order:0, mode:0x20
<Warn:HAL.Sys.Warning>
Slot-1: Switch low on
Memory. OS KBytes total
1030596 free 1604
<Warn:HAL.Sys.Warning>
Slot-1: Switch low on
Memory. DMA Kbytes total
1030596 free 1604 bcmRX:
page allocation failure.
order:0, mode:0x20 Epm
application wdg timer
warning - 20 sec, kepc
0x80557634(__cond_resched+0
x20/0x4c) uepc 0x2acf5204
Resolved.
PD4-4015917587 The following error occurs while
executing the command debug hal
configure ports 1:18
shutdown:
<Erro:HAL.Port.Error> MM-
A: aspenCardPortShutDown -
SIOCGMIIPHY on eth33882123
failed: No such device
PD4-4147433171 Process netTools ends unexpectedly
with signal 11 when efence is enabled
on netTools.
PD4-4133205040 Process dot1ag pid 1496 ends
unexpectedly with signal 11 when
switch boots up with Efence enabled
for dot1ag.
PD4-4148525900 Add TRILL HAL EMS mnemonics and
get XML files reviewed.
Known Behaviors
The following are limitations in ExtremeXOS system architecture that have yet to be
resolved.
Table 4: Known Behaviors, Platform-Specific and Feature PDs
General
PD4-3946654417 snmpwalk on ESRP table fails:
SNMPv2-SMI::enterprises.1916.1.12.2 = No Such Object available on this
agent at this OID
PD4-3970322310 MPLS:LDP: Egress LER is not advertising label mapping messages for OSPF
routes.
PD4-3586076001 Error message should start with keyword Error rather than with the %
sign.
PD4-3912550540 The shell ends unexpectedly when entering the command configure
vlan v1 ipaddress 10.1.0/, and then pressing TAB for command
completion.
PD4-3872223461 Switch is not generating ICMP redirect messages.
PD4-3912263889 Typing the vr command incorrectly (adding a space v<space>r.) causes
process CLImaster to end unexpectedly with signal 11.
PD4-3734904546 sa-cache entry check failed for below scenarios:
Originate SA cache (with first hop router and rendezvous point are the
same)
Originate SA cache only if we are rendezvous point (or RP = first hop
router = DR)
Originate SA cache only if we are PMBR and rendezvous point and first
hop router
PD4-3317546201 Two issues in MAC-VLAN Mode:
Multicast cache entry for IGMP/MLD group is not deleted from hardware
even after adding matching static FDB entry onto a different port in the
same VLAN.
Multicast cache entry for IGMP/MLD group is not created in hardware
after deleting matching FDB entry.
Workaround:
1 Issue command: clear igmp|mld snooping vlan
<vlan_name> [vlanname on which the fdbentry is created or
deleted]. This command flushes the entire VLAN.
2 Issue the command: debug mcmgr clear <grp_Ip>
<src_Ip> <vlan_name> [User has to know the src_Ip and
grp_Ip on which the cache is created].
PD4-3348898271 The static DHCP binding is not saved in the configuration, so saving, and
then rebooting, loses the binding.
PD4-3109929170 After removing the zone, the debug command still displays the policy as
NwZonePolicy. The mapping should be corrected to the policy itself as the
zone is removed.
PD4-468366251 A network login client is not authenticated if the username is 32 characters.
Only 31 character user names are supported, even if the user can create a
32-character username.
PD4-3315488109 After VLAN tag is modified on PMBR, traffic is not forwarded through
dense circuit.
Workaround: Enable MLD snooping on all interfaces.
PD4-3251586520 The IGMP groups are not deleted from the MVR VLAN when leave packets
are sent in the edge VLAN.
Workaround: Enable proxy when MVR is configured.
PD4-3352005341 Ping from ESRP master switch to host connected to ESRP slave (connected
via host attach port) fails when the switch to which the host is connected
is master for another ESRP domain.
PD4-3206377171 After a policy attached as a MVR static address range is modified, the ports
for all MVR VLAN groups are deleted, while the addresses that are
permitted by the policy are not deleted.
PD4-3320002080 Sending vr-value as vr1 with vlan-tag from vm-map file with no user vr
configured in the switch results in no vlan-tag and vr-name creation for
that VM, and then creating user vr vr1 and running repository synch does
not create vm with vlan-tag and vr vr1 as configured in vm-map files.
Workaround: Restart process vmt and do run vmt repository synch.
PD4-3154851418 When both dynamic VLAN uplink port is configured and ISC port is
configured dynamic VLAN created, add the uplink port as tagged, but the
flag is only *11gV (should be with both "U" and "V" flag).
PD4-3269060537 The command clear fdb does not zero dropped counter in show fdb
command.
PD4-3215358251 The help text (by pressing TAB) does not appear after issuing the
command configure vrrp vrrpvlan vrid 1 authentication
none.
PD4-3075918118 VM Statistics - Egress counter is not working.
PD4-3098599761 Changing from untagged to tagged traffic with the same VLAN tag does
not add the ports as tagged and this results in traffic loss.
PD4-3080980181 When STP is configured and enabled the dynamic VLAN propagation
suddenly vanishes.
PD4-3143967884 After authenticating two computers using the dot1x authentication method,
a Remote Desktop session between two computers fails.
Workaround: Enable computer-only authentication using the procedure
from the Microsoft Windows knowledge base: http://
support.microsoft.com/kb/929847.
PD4-2039102228 There is no CLI command to verify which control and protected VLANs
belongs to which ERPS domains. Also missing are flags reserved for ERPS
in show vlan command.
Table 4: Known Behaviors, Platform-Specific and Feature PDs (Continued)
PD4-2744727326 clear bgp or show bgp commands should fail in VRF context.
PD4-2770013534 Valid MLD messages with unspecified address (::), are treated as valid MLD
packets. instead, these should be silently dropped.
PD4-2770013437 MLD protocol Timer value is not inherited from the current querier's query
messageinstead it is always the configured value on this router.
PD4-2835155421 On a private VLAN [network VLAN] translated port, the packets egressing
when captured, shows the subscriber VLAN tag instead of Network VLAN.
PD3-57182431 For the incoming traffic with alignment errors, the "RX Align" counter in the
output of the show ports <port number> rxerrors command is
not incremented. Instead, the "RX CRC" counter is incremented.
PD4-1663984367 Whenever a (*, G) join is received, all hardware entries installed on non
upstream (*, G) interfaces are cleared. Therefore, every 60 seconds, the L2
switching is affected, traffic comes to the CPU, and entries are re-learned.
PD4-2110742669 When using SCP to transfer files to an Extreme switch, the transfer fails
with an "incomplete command" error.
BlackDiamond Series Switches
PD4-3915998731 On BlackDiamond 8800 series switches, FDB entries learned over EAPS
ring ports are not flushed during EAPS failover when the switch is
configured as an EAPS transit node.
PD4-3925446987 On BlackDiamond X8 series switches, when you enable sharing with one of
the member ports being a part of a VMAN, you are not warned that the
port will be deleted from the VMAN.
PD4-3780371771 Jumbo frame fragmented packets are sent to incorrect VLAN.
PD4-3652083671 On BlackDiamond 8800 series switches, the loopback port LED does not
blink with mirroring enabled.
PD4-3305214940 On BlackDiamond X8 series switches, IGMP groups learned on an MLAG
port are removed when the MLAG port goes down.
PD4-3266706442 The command clear counters followed by show port congestion
results in an error if executed within about eight seconds of each other on
BlackDiamond 8800 series switches.
PD4-3155474589 In BlackDiamond 8800 series switches, port flapping can occur when
enabling mirroring instance with loopback port configured.
PD4-2938691821 For the BlackDiamond X8 series switches, differv value is not getting
replace when dot1p examination is enabled on ingress port with diffserv
replacement enabled for slow path l3 traffic.
PD4-2339271510, PD4-
2180251961
For the BlackDiamond 8800 series switches, when running the show tech
command on a backup master switch fabric module, an error message is
displayed.
PD4-2854254274 For the BlackDiamond X8 and 8800 series switches, L3 traffic with IPv4
options or IPv6 ext. headers is not sent to the CPU when redirected by
flow-redirection.
Summit Series Switches
PD4-4429113409 Kern card error messages appear after run failover on Summit X770
160G series switches when all partitioned 10G ports are in the default
VLAN:
Slot-1: VLAN Set untagged port(u 0, p 59, v 1)
returns error - Operation timed out
Slot-1: InstallRule: bcm_field_entry_install returned
"Operation timed out"(-9) for group_pri 11 group_id
2, rule_id 1063 rule_pri 4087(unit 0) Slot-2:
bcm_port_ipmc_enable failed for slot 1, port: 100 rv
-9
PD4-4168387781 "Erro:EDP.ProcPDUFail" error logs are generated when trying to run L2
jumbo frame traffic for a long time across LACP links.
PD4-4105104951 On Summit X770 series switches, upgrading or downgrading the license
without rebooting causes the switch to stop working.
PD4-4130284867 In Summit X480 series switches where the external table is configured for
l2/l3 mode, L3 traffic from known source MAC is dropped at ingress side
when learning is disabled on ingress port.
PD4-4113664381 On Summit X770 series switches, the command terminate process
telnetd forceful causes the current SSH session to stop working
(same behavior occurs for telnet session, if exsshd is terminated forcefully
in current telnet session).
PD4-3999379047 On Summit X770 series switches, VPLS session goes down after enabling
MPLS PHP.
PD4-3966411597 QoS queue for VMAN untagged traffic (customer VLAN traffic) differs
between Summit X670 and X460 series switches.
PD4-3802664719 With mirroring enabled, applying egress ACL with mirror as action modifier
produces an error.
PD4-3822824451 On Summit X440 series switches and E4G-200 cell site routers, when
creating an IPv6 interface and enabling VLAN mirroring to it, an error
message appears stating that the port could not be added, but the output
of the show mirror command shows that the VLAN was added.
PD4-3678073021 Per VLAN IGMP filter is not working in the image summitX-15.4.0.1-br-
ACLEnhancements-5.xos".
PD4-3314306502 On Summit X450a/e switches with XGM2-2bt modules, normal/extended
diagnostics fail.
PD4-3285450101 PIM signal 6 ends unexpectedly when disabling or enabling OSPF on
Summit X670 stacks. Process PIM pid 1528 ends unexpectedly with signal
6.
PD4-3321289371 On Summit X460 series switches, flows are not removed when
disconnected from controller.
PD4-3241288551 On Summit X440 series switches, IPv6 neighbor discovery is not
happening to VRRP virtual IP in VRRPv3 MLAG setup.
PD4-3231034335 On Summit 80G stacks, JFFS2 warning messages occur while rebooting
the 80G stack.
PD4-3332304721 On Summit X480 series switches, PIM process ends unexpectedly when
executing show pim ipv6 after creating multiple PIMv6-enabled VLANs.
PD4-3037333500 In Summit X670-48x series switches, only SFP+_SR (SOURCEPHOTONICS)
ports are not coming up after restarting the port (25) and then save and
reboot. This issue does not occur with Summit 650-24x and BlackDiamond
8800 series switches.
Workaround: Disable, and then enable the far-end port.
PD4-3349524091 On Summit X460/X440 series switches, slot 2 reboots when more than the
maximum permitted FDB entries are learned.
PD4-2913932450 QSFP+LR (ColorChip) optics link is coming up when connected back-to-
back and after a save and reboot of ExtremeXOS fails to detect the media
type when a Q+LR4 in ports <port lists> on Summit X480-24x series
switches.
Workaround: Only the media type is getting properly set after unplug/plug
the optics from ports. This issue is not seen with QSFP+ SR4 on Summit
X480 series switches.
PD4-2760140871 For Summit X670 series switches, dynamically learned FDB entries on non-
FIP snooping VLANs disappear after FIP snooping is disabled and re-
enabled on the VLAN.
PD4-2835588361 For Summit X670 series switches, the show conf bgp command is not
vr-aware. VR-default BGP config appears even though inside vrf-a context.
It should show BGP config for vrf-a
PD4-1637091230 With 4,000 VPWS sessions, traffic recovery takes approximately 8 minutes
before a port flap occurs.
Workaround: On a Summit X460, it is recommended that you only
configure 1,000 VPWS instances.
E4G-200 and E4G-400 Cell Site Routers
PD4-4140787691 Flag state does not revert to state "SMA" when the ccm transmit intervals
are reverted to same value from different configured values.
PD4-3316332889 ESVT fails to run even with just 10 ERPS rings configured in an E4G-200
cell site router node. ACL slice errors occur due to a hardware limitation.
PD4-3312009417 TDM UDP PWE fails to work when created between PE routers.
TransmittedTDM packets are not received at the destination,
ACL
PD4-2649674514 Policies with "redirect-port-list" as the action modifier do not get installed
on a G48Te2 nor a 10G2Xc. It is not installed on either Summit X450a nor
x450e.
PD4-2761666711 Redirect port list changes its behavior when sending slow path traffic.
PD4-1933402713,
PD4-1933225935
The ACL action "copy-cpu-and-drop" is not copying EAPS control packets
to the CPU.
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. Access Control List
limitations fall into two areas: physical and virtual.
Physical LimitsSummit X450a and Summit X450e series switches:
The per-VLAN, wildcard (port any), and single-port access list installation
limitations are 1,024 rules for the Summit X450e and 2048 rules for the
Summit X450a.
Physical LimitsBlackDiamond 8800 a-series and e-series modules:
The per-VLAN, wildcard (port any), and single-port access list installation
limitations are 1,024 rules for the e-series modules, and 2048 rules for the
a-series modules.
Extreme Networks recommends that you configure ACLs as per-VLAN,
wildcard, or single-port. If either of the following is true, you will have to
configure ACLs with multi-port lists:
Your application requires that ports do not have a homogeneous ACL
policy.
When BlackDiamond 8800 original series modules are operational in the
same chassis, it may be necessary to configure ACLs to specific port-lists
instead of as wildcard or per-VLAN. This is because the original series
modules have smaller physical limits.
Virtual LimitsSummit X450a and Summit X450e series switches:
When configuring a multi-port ACL, use the following guideline. The total
ACL count (as calculated by ACL rules times ports applied to) should not
exceed 48,000 total ACL rules.
For example, applying a 1,000 rule policy file to a 48 port multi-port list is
supported (1,000 rules * 48 ports in the list <= 48,000).
Virtual LimitsBlackDiamond 8800 a-series and e-series modules:
When configuring a multi-port ACL, use the following guideline. For any a-
series or e-series blade in the system, its total ACL count (as calculated by
ACL rules times ports applied to) should not exceed 48,000 total ACL
rules.
For example, applying a 1,000 rule policy file to a 48 port multi-port list on
an a-series module on slot 1 and an e-series module in slot 2 is fine. Neither
module exceeds the 48,000 total ACL rules.
Excessive boot times and CPU resource starvation can be seen with larger
total rule counts. If your application requires additional capacity, contact
Extreme Networks.
BGP
PD4-2216087479 A confederation ID is used as an aggregator ID when in a confederation
instead of an AS-number.
PD4-2125200453 A backup slot does not come up when rebooted with 1,000 non-unique
routes on a Summit X480 stack.
EAPS
PD4-3685679711 EAPS convergence time with L2 multicast traffic in EXOS 15.4.1
(ACL_Enhancement Image) is greater than what it is in EXOS 15.3.2.
IP Protocols
PD4-3840263690 Sometime OSPF routes are not added to the routing table even though
their learned from peer devices.
PD4-3632921367 ECMP-PIM: Traffic recovers after up to 60 seconds when the route toward
the source is withdrawn/re-advertised.
PD4-3564310831 ECMP-PIM: Up to two minutes of traffic loss occurs when ESRP slave
switch transitions to master.
PD4-3512662174 IGMP Loopback-MVR: Invalid group version occurs when a static group is
configured and an Ixia group expires.
PD4-3356887520 L2 data forwarding is not occurring after reconfiguring static MVR policy.
PD4-3302624090 The following error messages occur when disabling ports on an MLAG
server node, which are connected to an MLAG peer, or when rebooting the
server node:
11/29/2012 18:36:28.73
<Erro:IPMC.VSM.FndISCRecvrFail> MSM-A: ISC receiver
not found for VLAN esrpv17, group 227.17.31.2, ISC
256:1
11/29/2012 18:36:28.73
<Erro:IPMC.VSM.FndISCRecvrFail> MSM-A: ISC receiver
not found for VLAN esrpv17, group 227.17.31.3, ISC
256:1
PD4-3197436651 The display log message from the command show ipstats changed
from "Router Interface on VLAN vlan1_2" to "Router Interface vlan1_2".
MLAG
xos0055451 With auto LACP MAC configuration for MLAG peers, MLAG ports are
removed from the LACP aggregator and added back when the second
MLAG peer comes up.
Workaround: Configure common LACP MAC on both MLAG peers.
MPLS
PD4-521915271 The Internet Group Management Protocol (IGMP) group reports may
occasionally change from Version 2 to Version 3.
PD4-581950231 Multi-cast traffic is not received even though the rendezvous point
(rendezvous point) tree and source information is shown in the PIM cache
table
PD4-475414505 In more complex topologies, detour Label Switched Path (LSP) connections
are not set up.
PD4-475414370 The following warning message is seen numerous times after changing
VLAN Virtual Private LAN Services (VPLS) mappings:
<Warn:MPLS.LDP.InternalProb>
PD4-464587012 All unicast traffic routed by MPLS is stopped when penultimate hop
popping (PHP) is enabled on all MPLS VLANs. VPLS traffic is not impacted.
PD3-203917264 If an LSP is already Up, and an ERO is added such that a subsequent path
calculation will fail, the LSP will remain Up, and at the same time, continue
to retry to calculate a new path with the new ERO. This situation is not
clearly visible in the show mpls rsvp-te lsp detail output. The
retry counters incrementing is really the only indication that this is
happening. The fields showing the "Msg Src," "Msg Time,"
"Error code," and "Error Value" should be shown because the
reason for the path calculation failure is shown in these fields.
PD3-93069318 Only VLANs configured as protocol any should be added to MPLS.
PD3-92653036 The show mpls label, show mpls rsvp-te label, and show
mpls rsvp-te lsp command output currently does not display egress
LSPs using advertised implicit NULL labels.
PD3-157687121 ExtremeXOS software uses Control Channel Type 2 to indicate router alert
label mode. In MPLS Router Alert Label mode, VCCV packets are
encapsulated in a label stack. However, the existing VCCV packets are sent
like a stack without any PW label.
PD3-104731701 When a traceroute is performed by setting the MPLS TTL to the IP TTL,
ExtremeXOS does not correctly send back an ICMP response. The result is
* characters in the traceroute for the routers that timed out. If a route is
available, ExtremeXOS should attempt to send back an ICMP response.
PD3-93630853 LDP should not advertise a label mapping for a direct VLAN that does not
have IP forwarding enabled.
PD3-139423053 Running the show mpls rsvp-te lsp summary command on a
system configured with 2,000 ingress LSPs takes an excessive amount of
time to process.
PD3-111544904 When a router receives an explicit NULL label, it is incorrectly treated as an
implicit NULL label, so rather than sending label 0, no label is sent.
PD3-184989177 When an LDP advertise static setting is set to all, all static routes
are treated as egress routes and egress LSPs are created. That is, a label is
generated and advertised for the static route. If the router at the end of the
static route advertises a label matching that static route, the LSP that was
previously an egress LSP becomes a transit LSP. An ingress LSP should also
be created whenever a label is received, however, the ingress LSP is never
created.
Workaround: Do not use the LDP advertise static all
configuration in situations where an ingress LSP for a static route is
required.
PIM
PD4-3817878867 Switches fail when traffic is sent for 4,000 (S;G)s when PIM IPv6 is
configured in dense mode with state refresh enabled.
Workaround: Do not exceed 3,000 (S;G)s on PIM-DM with state refresh
enabled.
PD4-3912263796 When PIM is configured on user VR, process pim pid 8064 ends
unexpectedly with signal 11.
PD4-3842583955 Peer ingress VLAN appears as unknown for 6 out of 12 (S;G)s on both
MLAG peers after the port corresponding to the SPT path is disabled.
Security
PD4-4345139584 Uninstalling SSH XMOD produces the error "Error: Failed to install image -
mount: mounting /dev/mtdblock2 on /exos failed: Device or resource busy.
PD4-3579524975 Enabling NetLogin on an IDM role-based VLAN-enabled port should
produce the error:
ERROR: NetLogin cannot be enabled on Identity
Management Role-Based VLAN enabled ports
But instead the following error appears:
ERROR: NetLogin not enabled on Identity Management
Role-Based VLAN enabled ports.
PD4-3617428061 Back-up repeatedly generates the same error message when issuing the
command unconfig idm.
SNMP
PD4-4096165502 For Summit X670V-48X: "extremePowerSupplySource.1" and
"extremePowerSupplySource.2" MIBs always show value as "2(ac)" even DC
powersupply is present in the switch.
PD4-3653928680 extreme.my MIB has many OID information defined more than once.
TRILL
PD4-3190014744 VLAN tag with "0" appears as extra encapsulation for TRILL hello packets
on native VLAN ports, as well in designated VLAN ports.
VLANs
PD4-3134856251 The following error message appears when deleting dynamic VLANs:
mvrpLeaveCheck_cb: VID: 1003 not found. mvrpLeaveCheck_cb: VID: 1002
not found.
Resolved Issues in ExtremeXOS 15.4.2-Patch1-3
The following issues were resolved in ExtremeXOS 15.4.2-patch1-3. ExtremeXOS 15.4.2-
patch1-3 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.7, ExtremeXOS 12.2.2-patch1-12, ExtremeXOS 12.3.6,
ExtremeXOS 12.4.5, ExtremeXOS 12.5.5, ExtremeXOS 12.6.5.2-patch1-3, ExtremeXOS 12.7.1,
ExtremeXOS 15.1.5.4-patch1-8, ExtremeXOS 15.2.4.5-patch1-5, ExtremeXOS 15.3.1.4-patch1-41
and ExtremeXOS 15.3.4.6. For information about those fixes, see the release notes for the
specific release.
Table 5: Resolved Issues, Platform-Specific and Feature PDs in ExtremeXOS 15.4.2-
Patch1-3
General
xos0047180 EMS process ends unexpectedly when a large quantity of logs are targeted
to the console.
xos0050905 The following error appears while deleting the member port from sharing
group on ISC ports:
"<Crit:vlan.err.fileIOCTL> System call ioctl failed:
informCfgVlanRemPorts and 8 <Erro:Kern.Error> exvlan:
configVlanRemovePort:2432: KERNEL_EXVLAN_ERROR: Failed
to find vpif"
xos0053748 The snmpMaster process ends unexpectedly when snmpMaster is restarted
after changing engine-id.
xos0053970 NTP process ends unexpectedly during switch reboot
xos0054825 Error message "Dropped CM_MSG_EXEC: Length 356 Peer 59
(snmpSubagent)" appears in log after switch reboot.
xos0054940 SNMP requests should be forwarded to back-end client when configuration
load or configuration save operation is in progress.
xos0055212 After restart ports all on multiple PE/P nodes, RSVP-TE LSP do not
come up. The error Protocol Error - Routing Problem (24)" appears.
xos0055627 EDP process ends unexpectedly when a malformed packet contains greater
than 200-character length VLAN information.
xos0055783 Switches drop packets and display "Invalid MAC Binding" error when you
remove an existing client and connect a different client with the same IP
address.
xos0055939 EXSH assert failure occurs when executing commands containing port lists
separated by commas when last port number is followed by TAB key
sequence.
xos0056339 FDB learning does not occur after deleting/adding subscriber VLAN from
PVLAN.
xos0056364 On BlackDiamond X8 and 8800 series switches, with distributed ARP
turned on, L3 traffic doesn't egress after a link failover, even though ARP
entries have been learned and they are pointing to the correct ports. The
traffic starts flowing after executing the command <i>clear iparp</i>.
xos0056977 Client authenticated using netlogin dot1x gets incorrect IP address due to
delay in moving port to success VLAN.
xos0056995 IPv6 traffic for routes with mask length >64 are not forwarded after clearing
FDB.
xos0057013 IPv6 traffic for routes with mask lengths greater than 64 characters is
slowpath forwarded if switch has tunnels configured or when destination
MAC address of the IPv6 packet is a virtual MAC address.
xos0057043 With MLAG and PVLAN configured, after disabling MLAG port, IP ARP
entries continue to point to disabled MLAG port, instead of ISC port, causing
traffic loss.
xos0057088 Cannot log on using SSH with a 32-character or greater password. After
eight logon attempts, no more SSH connections are permitted.
xos0057159 ACL process ends unexpectedly when deleting access-list network zone.
xos0057321 EDP process ends unexpectedly during switch reboot when VLAN name has
32 or greater characters.
xos0056020 L3 traffic ingressing on the ISC link from an MLAG peer is not egressing
the appropriate egress MLAG port after L3 forwarding.
Occurs only with jumbo frames enabled on a few of the ports.
xos0056054 Disabling user-created mirror instance with ACL filter fails when a default
mirror instance is enabled with ACL filter.
xos0057045 Unable to match ARP packets using ACL match criteria "arp-sender-
address" and "arp-target-address" in c-series I/O modules.
xos0057384 Hardware learning is not enabled on the sharing member ports after
deleting an MLAG peer.
xos0057771 Packet loss occurs during RSVP fallback scenario.
xos0057804 If the same port is used for CEP-VPLS + Untagged-VMAN(L2), then all CEP-
VPLS traffic goes by Untagged-VMAN(L2).
xos0057808 Packet loss occurs due to hardware convergence during RSVP fallback
scenario.
xos0057375 Multi-cast cache entries for local mcast group (for example, 224.0.0.x/24)
go out of sync between hardware units and software.
xos0057354 Kernel gets stuck after issuing the command clear fdb, followed by MSM
failover when switch has highly scaled FDB and ARP entries.
xos0057422 Need to limit the kernel error log messages when packets are dropped.
xos0057561 Enabling mirroring on BD8K with MSMs other than MSM-128 causes VRRP/
LACP flap.
Patch1-3 (Continued)
xos0050424 Slot goes into failed state after running extended diagnostics.
xos0054748 When BlackDiamond X8 QSFP+ LR4 optic is disabled, the link goes to
disabled state as expected. When it is enabled, the link remains in ready
state instead of going back to active state
xos0055993 On BlackDiamond X8 switches with BDX8-100G4X cards, RSVP failover
takes 48 seconds.
Summit Family Switches
xos0054109 FDB entries learned on MLAG ports are never aged out if the ports support
hardware aging.
xos0054573 L2 traffic is not flooded to network and subscriber VLAN ports after
restarting process vsm.
Summit X460 Series Switches
xos0055217 On Summit X460 stacks, EDP does not work in XGM3SB-4sf VIM modules.
xos0057916 Default debounce timer should be set to zero on stacking ports.
xos0055416 On Summit X460 series switches, after enabling jumbo frames on 10G ports
on XGM modules, doing either a save and reboot or changing port speed
settings removes the jumbo frames setting.
xos0057024 Remote ports connected to 10G ports from XGM3 card experience link flap
and stacking link formed using ports from XGM3 card experience link flap.
xos0054362 After learning around 10K FBB entries, MPLS FDBs are not cleared from
hardware if the clear fdb command is executed.
xos0057454 FDB entries are not aged out after two continuous MAC address moves.
xos0057752 On Summit X480 series switches when untagged VLAN packets are
received on tagged VMAN ports, which in turn receive from untagged
VMAN ports bursts of more than 500 packets in line rate, some FDB entries
are not learned in hardware.
xos0055074 On Summit X670v-48x series switches, links go down after rebooting if the
ports are configured with auto negotiation off and the speed is 1G on both
peers when using a mini Gigabit interface converter.
xos0057258 IPv4 unicast traffic can be dropped by hardware if the destination IP
address resides on a high-numbered front-panel port (port # 64 and
greater), and if more than 32 ARPs are present.
xos0057772 For Summit X770 series switches, IPv6 unicast traffic destined to local IPv6
host with a switch interface mask greater than 64-bits, is not forwarded
after clearing FDB.
Patch1-3 (Continued)
Resolved Issues in ExtremeXOS 15.4.2
The following issues were resolved in ExtremeXOS 15.4.2. ExtremeXOS 15.4.2 includes all
fixes up to and including ExtremeXOS 11.6.5.3, and earlier, ExtremeXOS 12.0.5, ExtremeXOS
12.1.7, ExtremeXOS 12.2.2-patch1-12, ExtremeXOS 12.3.6, ExtremeXOS 12.4.5, ExtremeXOS
12.5.5, ExtremeXOS 12.6.3, ExtremeXOS 12.6.5, ExtremeXOS 12.7.1, ExtremeXOS 15.1.5,
ExtremeXOS 15.2.4, ExtremeXOS 15.3.3, and ExtremeXOS 15.4.1. For information about those
fixes, see the release notes for the specific release.
Table 6: Resolved Issues, Platform-Specific and Feature PDs in ExtremeXOS 15.4.2
General
xos0056109 Traffic loss occurs for 1530 seconds, when PIM non-designated router
changes to designated router.
xos0054097 Intermittently, MLAG local link state stays in the ready state after VSM
process is restarted.
xos0048613 With about five LACP LAGs with active member ports in each LAG,
executing the command restart ports all three times produces the
following error:
<Warn:LACP.UnackTimerExp> Unack timer expired for LAG
25 262148 Instance 4 index 4
xos0049499 BlackDiamond 8800 series switches stop responding after executing the
command delete vman test. This issue occurs with ExtremeXOS 15.2.1,
15.2.2, 15.3.1, 15.3.2, 15.3.3, and 15.4.1, This issue does not occur with
v15_1_2_12.
This issue occurs with BlackDiamond 8800 (MSM-128/48c) and
BlackDiamond X8 series switches, and Summit V80 stacks. BlackDiamond
X8 series switches stop responding for up to 4 minutes and 39 seconds
when deleting VMANs. The BlackDiamond 8800/Summit stack stops
responding for up to 1 minute.
xos0051050 PoE process ends unexpectedly when executing show inline-power
info detail ports <port list> command.
xos0052210 Routing tables do not update after resetting RIP neighborship when two
RIP routers export the same routes to two different ASBRs.
xos0052365 Unconfiguring L3VPN and then configuring it again results in BGP failing to
advertise the routes.
xos0052661 Should not be allowed to change existing OSPF interface to another area
when OSPF is enabled.
xos0053012 Changing instance ID along with timer when OSPFv3 neighborship goes
down.
xos0053543 Switches respond to GARP attacks for an IP address that is configured as a
static IP ARP entry with switch MAC addresses, but switches should
respond with MAC addresses listed in the static IPARP entry.
xos0053610 LLDP detect and undetect events are not properly triggered when
netlogin,identity management and UPM are running on the same port.
xos0053789 Some valid MLD packets are rejected as error packets.
xos0053848 In SummitStacks, VRRP MAC addresses are not checkpointed to other slots
after those slots are rebooted.
xos0053886 Deleting a user-created virtual router causes the switch to become
unresponsive when SNTP is enabled for that virtual router.
xos0054097 Intermittently, MLAG local link state remains in ready state after starting
VSM process.
xos0054120 Enabling IPv6 smart relay at VR level is not forwarding the relay-forward
solicit from having multiple bootpv6 relay enabled agents.
xos0054214 Only one ELRP log message occurs even with two loop conditions.
xos0054221 Switches learn MAC addresses from the STP-blocked ports if AVB is
enabled.
xos0054270 Configuring a DHCP-address-range for management VLANs should not be
allowed.
xos0054486 VRRP MAC addresses are not programmed in hardware if the corresponding
hash bucket is already full with other normal MAC address entries.
xos0054614 The virtual router (VR) information is not included when tech-support
collector is added with virtual router option. VR information is ignored.
But the VR information is included when configuration using configure tech-
support collector.
xos0054661 The help description for the command show lacp member-port
<port> should show "port" instead of "port-list.
xos0054842 The command upload debug produces errors when the same policy is
applied for SNMP and Telnet as access-profiles.
xos0054864 IPFIX tags 152(flowStartMilliseconds) and 153(flowEndMilliseconds) should
be added to the existing IPFIX template.
xos0054989 Quiting or exiting the BCM shell with at least one uppercase letter causes
the bcm.shell thread to end.
xos0055028 CDP neighborship is not detected when TLV app is enabled on peer
switches.
xos0055055 CliMaster ends unexpectedly with signal 6 when a Telnet session loses
connectivity to the switch during command execution.
xos0055091 In BlackDiamond X8 and BlackDiamond 8800 series switches, with
distributed ARP turned on, L3 traffic doesn't egress after a link failover, even
though ARP is learned correctly and pointing to correct port. The traffic
starts flowing after executing the command clear iparp.
xos0055093 IPMC: Multi-cast cache creation can fail for reserved multi-cast addresses
(for example, 224.0.0.x/8) on VLANs with IP addresses configured and 100+
active ports.
xos0055234 Enhance the output of the command debug hal show sys-health-
check to include I/O card memory information and async queue counters.
xos0055238 The length in the CCM MA header is different for MA Primary VID. This
creates a problem if an S/K/TOR/ExtremeXOS CFM operation uses a MA
VID name. When this occurs, the following type of error appears:
03/05/2014 10:27:57.46 Received invalid cfm on port
14, VLAN "Video2101"; MA Identifier does not match
configured MEP's Identifier
xos0055257 After many reboots VRRP instance stays in INIT state when ELSM and VRRP
are running over the same single port.
xos0055316 With VPLS enabled, ARP packets are dropped when ingress and egress
ports are present on different units.
xos0055372 IGMP joins received on MLAG designated router (DR) interfaces need to be
checkpointed to non-DR MLAG peer interfaces, but this fails after link flaps:
<Summ:pim.debug.Log> (pimrt.c:3228) addIgmpJoin: Not
a DR for circuit (CCTV_SERVER_FARM). Skip adding IGMP
join
xos0055476 DHCP decline packets are dropped if their client address field is 0.0.0.0.
xos0055513 With CDP enabled, the EDP process ends unexpectedly after receiving
malformed CDP packets.
xos0055585 Multicast traffic recovers in up to 60 seconds when an ingress port on a first
hop router (FHR) is disabled. Two FHRs exist that are connected to the
same multi-access VLAN.
xos0055611 PIM does not failover to alternate source received from the MSDP peers
when the primary source fails.
xos0055662 Delays triggering a cyclic UPM profile cause the next FireTime to be
calculated using the delayed current time.
xos0055685 UPM process ends unexpectedly after executing the command show
config upm repeatedly.
xos0055754 Lawful Intercept users logging on using SSH generate logon authentication
events.
xos0055849 Enabling ACL and mirror log filters shows the Lawful Intercept user dynamic
ACL binding/unbinding and enable/disable mirror information to admin
users.
xos0056115 Some VRRP VLANs change state when ports belonging to VRRP VLANs
when are disabled, and then enabled.
xos0048730 When MLAG ports are enabled, and then disabled, the following error
message appears:
07/30/2012 22:22:37.27 <Erro:Kern.Error> : exvlan:
xos0052683 Summit X460 stacks do not come up using one port in alternate and
another port in native mode for stacking
xos0052881 When meters are configured for several egress ACL rules, the hardware
might be mis-configured when ACL rules are forced to be moved in the
TCAM. This causes meters to be applied to a wrong ACL rule.
xos0053093 On Summit X770 series switches, Hybrid Scheduling is not working on all
scheduling nodes (SP, WRR, WDRRQ).
xos0053152 On Summit X670 series switches, user-defined mirror instances are not
working if ACLs (with mirror rule) are applied on VMANs/VLANs.
xos0053227 VLAN statistics are not working after a VLAN with base PSTAG is removed
and added back to ports.
xos0053310 On Summit X770 series switches, partitioned 10G ports 77,78,81,82 do not
appear in output of command edp ports all. Due to this, bi-directional
traffic across these ports is not working even though the port is up with
speed 10G.
xos0053551 Deleting untagged VMAN ports that are tagged ports on other VMANs
produces the error "Jumbo still enabled".
xos0053681 On Summit X480 series switches, kernel errors occur after disabling all ports
in the transit node in the LSP path:
<Erro:Kern.MPLS.Error> MPLS
bcm_esw_mpls_port_match_vlan_del failed for unit = 0,
port = 0x8000002 vp = 0x1ae, match_vlan = 1565
match_inner_vlan = 1565, rv = -7 (Entry not found).
xos0053790 Kernel oops occurs when changing the netlogin MAC authentication
database order and then restarting the process netlogin.
xos0053987 Summit X770 series switches produce kern card error messages because
they are unable to allocate memory for DAD messages when trying to scale
to 2,000 L3 IPv6 VLANs.
xos0054038 Flooding occurs on enable/disable of EAPS ring port on Summit X770 series
switches.
xos0054050 Greater EAPS convergence time occurs for Summit X770 series switches.
xos0054076 In X670v-48x SummitStacks, kernel error messages appear while enabling/
disabling diffserv on all ports.
xos0054078 ACL rules are not used fully in ACL slice even though the ACL slices have
available rules. When configuring VLAN statistic for all 512 VLANs, only 128
rules of 256 available rules are used.
xos0054086 VLAN Aggregation configurations are not removed after rebooting the
switch when configuring dynamic VLAN as the sub-VLAN.
xos0054092 Summit X770 series switches should not support 450 W PSUs.
xos0054179 MAC learning limit with stop action is not working for pstag as unlimited-
learning is configured for other pstag when both pstags are added on the
same port.
xos0054180 Management port becomes unresponsive and stops transmitting traffic at
random times if peer switch has auto-negotiation turned off.
xos0054216 On Summit X770 series switches, traffic received on LAG member ports
(Service VLAN) is not forwarded to VPLS peers and FDB learning does not
occur.
xos0054229 When STP port priority is set to zero, then the show configuration
stp output does not reflect the configured priority value zero.
xos0054260 Unable to ping IPv6 interfaces created on Summit X430 series switches.
xos0054266 In the output of show cfm detail, some entries do not appear after
disabling the LACP ports.
xos0054357 In Summit X250 and X450 series switches, MAC addresses are not getting
learned on port 1.
xos0054388 On Summit X430 series switches (except X430-24t) L2 IP multi-cast cache
entries are not getting programmed in hardware, and therefore the multi-
cast traffic is software-forwarded instead.
xos0054595 MVR feature commands should be blocked on the Summit X430 series
switches as this feature is not supported.
xos0054718 In Summit X440 series switches, data packets are dropped on the ports
when an ACL with a dsap match condition is applied.
xos0054793 EEPROM values cannot be retrieved in Summit X670 and X670V for some
SFP and SFP+ optics.
xos0055187 On Summit X770 series switches, PTP is not working after saving and
rebooting.
xos0055233 In SummitStacks, ports stop forwarding traffic when egress mirroring is
configured in some other port.
xos0055308 MVRP fails to add egress ports to dynamic VLANs after an RSTP
reconvergence. As a result, L2 unicast traffic isnt switched.
xos0055505 On Summit X480 series switches with VIM4-40G4X modules, some FDB
entries become stale after learning a large number of FDB entries in a batch
from ports on the VIM4-40G4X modules.
xos0055986 On Summit X460-G2 160G stacks, kernel panic occurs when IP ARP entries
are cleared while continuous incremental IP ARP traffic is being forwarded.
SummitStack
xos0053427 Netlogin process ends unexpectedly when you log on through netlogin
web-based authentication.
xos0053974 In SummitStacks, the following error message appears regarding the backup
node when clearing IP multi-cast entries:
Slot-2: adj 0.0.0.0: # L3 hash table entries already
0.
xos0054288 Control packets (VRRP, OSPF, BGP, etc) originating on Summit X670X770
stack nodes and egressing on 40G ports in backup or standby node are
prepended with an extra 4-byte VLAN header with VLAN-ID 0 after failover.
Effectively, packets egressing have two VLAN tags with tag-id 0x8100. This
causes ping failures, VRRP flaps, and OSPF neighbors in down state.
Forcing the control packets to egress via 40G ports in stack master does
not produce the issue.
xos0054776 SNMP query on SummitStacks for extremeMemoryMonitorsystem does not
return memory usage details of backup node.
xos0054883 Known multicast traffic not load shared between the two stack links in V320
trunk.
xos0055321 In SummitStack, unknown traffic is duplicated and tunnelled to VPLS peers
after stack failover.
xos0055980 In SummitStack, traffic passing through a port from a backup node stops
after adding that port to another VLAN with port-specific tag configuration.
xos0053683 DHCP packets from sub-VLANs are not egressing through the super VLAN
ports.
xos0053960 BlackDiamond X8 series switches fail to learn SMACs on pseudowires.
xos0054460 The amount of time that HAL is "busy" after disabling a slot has increased
from around 10 seconds to over 90 seconds from ExtremeXOS 15.4.1 to 15.5.1.
xos0054464 Dhcp-binding upload logs are shown in reverse format. Also, while adding
binding restoration, the IP addresses are added in reverse format.
xos0054886 Process OSPFV3 ends unexpectedly with signal 6 when doing management
module failover when switch is configured with different OSPFv2 and
OSPFv3 sessions, and OPSFv2, OSPFv3 virtual links.
xos0054952 Traffic is not forwarding to mirrored ports are running management module
failover.
xos0055493 BlackDiamond X8 or Summit X670-t series switches acting as PE-nodes for
LSP loadsharing are not distributing traffic into multiple LSPs.
xos0052294 A port in the ISC VLAN is incorrectly allowed to be configured as an MLAG
port.
xos0052349 Process rtmgr ends unexpectedly with signal 11 while disabling an I/O slot in
a BGP configuration.
xos0053396 Ports stop forwarding traffic when egress mirroring is configured on some
other port.
xos0054051 CVID" as match criteria does not work with egress ACLs on BlackDiamond
8900-G48T-xl and 10G24Xc switches.
xos0054103 Switches remain in RTSync state for more than four minutes during bootup.
xos0054130 LAG ports are not added to the aggregation group after a master switch
fabric module failover followed by a port restart.
xos0054170 In BlackDiamond 8800 series switches, warning message "cannot
disable ctrl" appears during boot-up.
xos0054163 DHCP binding restoration does not work after a reboot on with dual master
switch fabric module.
xos0054202 In BlackDiamond 8800 series switches, some I/O cards go into the failed
state after issuing the command disable/enable ports all.
xos0054227 Error messages appear while disabling/enabling I/O manually with port
isolation configurations.
xos0054239 On BlackDiamond 8800 and BlackDiamond X8 series switches, slowpath
forwarding of IPv4 packets can occur if there is contention for IP hardware
table resources.
The destination IP for slowpath forwarding can be for a local host for which
there is a resolved ARP entry, but which was removed from the Layer 3
hardware table due to contention from IPv4 or IPv6 multicast or other
unicast hosts. The destination IP for slowpath forwarding can also be for a
remote host (a host reachable via a gateway), if all IPv4 LPM routes either
do not fit in the LPM hardware table, or exceed the number of routes
reserved using the command configure iproute reserved-entries
<num_routes_needed> slot <slot>.
xos0054262 "Could not derive slot/port from modid/port" error
messages appear while doing master switch fabric module failover with
VPLS traffic.
xos0054263 With BlackDiamond 8800 series switches with MSM-B as master, EPM
process ends unexpectedly when performing an SNMP query to check
download image status.
xos0054311 The error message Unable to connect to slot" appears when
executing the command show access-list usage acl-slice
port <port number>.
xos0054317 Switches send IGMPv3 query during master switch fabric module failover
even though there is no IGMPv3 configured.
xos0054350 The error message "bcm_l2_traverse failed Internal error"
appears after an MSM failover followed by executing the command clear
fdb.
xos0055438 In BlackDiamond 8800 series switches, optimize the memory usage of I/O
cards to provide more free memory after bootup.
xos0055712 On the I/O module in the shell, issuing async clear, and then clear
fdb on the master switch fabric module, kernel panic can occur on the I/O
module.
xos0055804 Multi-port mirroring not working when the loopback port is on a 10G24X-c
module.
E4G-200 and 400 Cell Site Routers
xos0052535 CFM fails to recover from faulty state after the control VLAN is disabled/
enabled in a transit switch. Due to this, ERPS stays in protection state.
xos0054000 Unable to create LAG groups on a port where ERPS was configured
previously with CFM.
ACLs
xos0051897 The command show access-list dynamic rule does not show
the mirroring stance name for a non-permanent dynamic ACL with mirror
action modifier after executing failover twice in a stack or BlackDiamond
switch. Also, traffic is mirrored even if you disable/delete the mirror
instance.
xos0052473 Should not be able to create more than 2,048 meters.
xos0052701 When you try to associate multiple VLANs as sub-VLANs within another
VLAN, a warning message appears regarding the ACLs not being installed.
xos0054104 ACL process ends unexpectedly when policies are removed from identity-
management role after an unsuccessful ACL policy refresh event due to slice
full condition.
BGP
xos0052351 Creating BGP neighbors with a peer group configuration does not inherit
the outbound route-policy associated with the peer group.
xos0054136 BGP export policy with match condition "next-hop" is not working correctly.
ESRP
xos0053647 After rebooting after a failover from master to backup there is no issue, but
after performing another failover, the ports in some ESRP member VLANs in
slave are unblocked, but ports in ESRP master VLAN are blocked. This
creates a situation where ports in ESRP member VLAN are unblocked in
both ESRP master and slave. This causes traffic loops.
xos0055259 ERPS status stays in idle state even when CFM detects port link down
events.
xos0055375 ERPS status is idle, even though there is an CFM underlaying alarm.
xos0055959 ERPS rings do not move to protection state after disabling a ring port.
FDB
xos0052149 Failover FDB on VLAN information to the backup does not synchronize with
master on having VMT dynamic enabled on the ports. Also, incorrect VLAN
information is appearing on the master and backup.
xos0053410 OSPFv3 is sending IPv6 addresses instead of the prefix in the address prefix
field of the link LSA when the IPv6 address of a VLAN is configured with
mask 97 and above.
xos0053808 The process OSPFv3 ends unexpectedly with signal 11 when unconfiguring
and reconfiguring IPv6 addresses on loopback VLAN.s
xos0053962 ISIS hello packets are dropped when its IP-MTU size is greater than 1,500.
xos0054056 The process rtmgr signal 11 ends unexpectedly after executing the
commands show iproute mpls and disable/enable mpls.
xos0054112 OSPFv3 cost is missing when deleting or adding VLANs from OSPFv3.
xos0054215 Restarting the OSPF process OSPF individually works, whereas restarting
process class OSPF does not work.
xos0054338 When jumbo frames are enabled on some ports, LACP error
"pibL3MTUExceededInstallFilterLag" appears after disable sharing
in one port and enable sharing on another port.
xos0054349 Packets are software forwarded after an master switch fabric module
failover followed by executing the command clear fdb.
xos0054389 In the show ospfv3 interface vlan <vlan_name> command
output, the instance-id does not reset to default value 0 even after deleting
the VLAN from OSPFv3.
xos0054503 Cant delete an OSPFv3 area even if there is no OSPFv3 interface present in
that area.
xos0054540 Deleting OSPFv3 interfaces from backbone areas and adding them to new
areas fails.
MPLS
xos0055857 FDB entries are not learned after changing VMAN tags when VMANs are
associated with VPLS.
xos0053440 With established LDP peers, the command show mpls ldp lsp
prefix 103.0.0.0/24 detail does not update the Rx packets.
xos0054029 Untagged VMAN-VPLS traffic is egress filtered when it is on the same port
as CEP-VPLS, and egress filtering is enabled on the port.
xos0054052 Ping doesnt work on VPLS VLANs across pseudowires.
xos0054285 VPWS feature no longer works after configuring MLAG.
xos0054297 Executing the command show mpls statistics l2vpn immediately
after executing the command clear counters produces the following
error message:
"Error: MPLS statistics database is not defined"
xos0054327 L2VPN sharing with spoke pseudowires does not work as expected.
xos0054341 VPLS is not passing traffic for around one minute after disabling/enabling
VPLS VLAN.
xos0054458 Traffic is not load balanced when backup LSP is active using RSVP-TE.
xos0054530 Pseudowires stay in signaling state after adding down MPLS LSPs to them
when L2VPN sharing is enabled.
xos0054571 Ping does not work from customer edge to provider edge access VLANs if
the access VLANs are associated with VPLS.
xos0055465 FDB entries are not learned using VPLS when switch is in software learning
mode.
xos0056114 Packets are not passing over VPLS when PS tag is configured in service
VLAN.
ScreenPlay
xos0054048 ScreenPlay does not properly display details relating to ports and VLANs.
xos0054313 Unable to disable/enable port using ScreenPlay.
Security
xos0051067 For TACACS+ and RADIUS servers, when setting the shared secret key in
encrypted form with characters "&" and "<" , the show configuration
aaa output shows a different secret key from what was actually set.
xos0054037 Process ipSecurity ends unexpectedly when receiving 64-byte TCP/IP
frames with flags TCP FIN, URG, and PSH bits.
xos0054158 DoS protect in simulated mode shows that ACLs are added, but no traffic is
blocked.
xos0054316 While enabling ip-security source-ip-lockdown on a few ports, ACL
resources are used inefficiently resulting in ACL slice full condition.
xos0054668 IDMgr process ends unexpectedly with signal 6 when detecting multiple
LLDP identites.
xos0055194 With option-82 enabled, DHCP request packets contain incomplete circuit-id
information when string exceeds 15 characters.
xos0055232 The output from the command show ssl does not show complete
information.
xos0055488 OpenSSL versions 1.0.1 through 1.0.1f contain a flawed TLS/DTLS heartbeat
functionality (RFC6520) that allows attackers to retrieve private memory of
an application that uses the vulnerable OpenSSL.
For more information, go to http://www.kb.cert.org/vuls/id/720951.
TRILL
xos0053873 TRILL process ends unexpectedly with signal 11 after executing the
command configure trill maintenance-mode enable. Switches
do not reboot though. The command show trill shows maintenance-
mode is still disabled.
xos0053983 In the following topology: IXIA---Switch1---Switch2---Switch3---IXIA, bi-
directional traffic is sent to switch1 and switch3. After executing the
command disable/enable trill on switch3, switch2 is no longer
forwarding traffic even though switch1 and switch3 are both transmitting
traffic to switch2. The issue exists whether switch2 is a BlackDiamond X8 or
Summit X670.
VLANs
xos0054010 ACL with match condition snap-8192, matches multi-cast traffic as well.
xos0054353 Switches stop responding when performing SNMP walk for the following
MIB: snmpwalk -v2c -c public -r 5 -t 5 10.69.9.75 1.3.6.1.4.1.1916.1.4.17.1
xos0056253 FDB is learned with disable learning on ports when port-specific tag is
added to the VLAN.
VRRP
xos0054060 VRRPv2 dual master with sub-second advertisement Interval.
Resolved Issues in ExtremeXOS 15.4
The following issues were resolved in ExtremeXOS 15.4. ExtremeXOS 15.4 includes all fixes
up to and including ExtremeXOS 11.6.5.3, and earlier, ExtremeXOS 12.0.5, ExtremeXOS 12.1.7,
ExtremeXOS 12.2.2-patch1-12, ExtremeXOS 12.3.6, ExtremeXOS 12.4.5, ExtremeXOS 12.5.5,
ExtremeXOS 12.6.3, ExtremeXOS 12.6.5, ExtremeXOS 12.7.1, ExtremeXOS 15.1.5, ExtremeXOS
15.2.4, and ExtremeXOS 15.3.3. For information about those fixes, see the release notes for
the specific release.
Table 7: Resolved Issues, Platform-Specific and Feature PDs in ExtremeXOS 15.4
General
PD4-4083220327 Unable to create new VLAN using XML.
PD4-4086689113 Incomplete kernel log messages appear in show log command output.
PD4-4198984121 With switch filtering S-VLAN-addressed frames when configured for C-
VLAN operation, drop provider bridge MVRP address (01-90- C2-00-00-
0D) when MVRP is enabled. Right stream is not always preempted.
PD4-3322786971 Advertisement interval shows zero in show vrrp command.
PD4-3666064156 The command show configuration vlan |mirroring causes the
CliMaster process to end unexpectedly.
This problem does not occur if you add a space after using the vertical bar
(|) or use include options like show configuration vlan |
mirroring.
This problem occurs with all show commands when you use a vertical bar.
PD4-4072824539 Switch forwards GARP reply packet by changing the source MAC with its
own MAC address to the same sub-VLAN in which it is received. This
produces and IP address conflict with other vendor routers.
PD4-3868736267 Description string for ports cannot include spaces.
PD4-3770840750 Remove static password from BIOS.
PD4-3634029356 Process exsh ends unexpectedly with signal 5 after enabling mirroring to
any port.
PD4-3678701407 CLI parser is placing the caret in the incorrect location and a missing
quotation mark.
PD4-3643883907 CLI parser is placing the caret at the incorrect spot for command with
invalid port number.
PD4-3702110799 CLI Parse Tree: Memory leak of CLI arguments comprising the arg list is
being accumulated.
PD4-3657714750 CLI options and tab completions are mis-aligned and therefore the CLI
produces errors when it should not.
PD4-4059336236 UPM process ends unexpectedly when you attempt to run a UPM profile.
PD4-3858989117 OSPFv3 neighborship is not established across an MPLS L2VPN cloud when
a service VLAN port is part of another VLAN where the IPv6 address is
configured.
PD4-3799029871 LDP: Process rtmgr pid 1550 ends unexpectedly with signal 11.
PD4-3734904701 The following error appears in the log when a port is deleted from a L2
multicast MAC.:
<Erro:HAL.FDB.Error> Invalid number of ports to
delete from an existing L2 Multicast MAC
01:0203:04:05:0b vlan=-xf4248
PD4-3605317270 For PIM-IGMP snooping, every 30 seconds, traffic sent for static groups and
receiver (router port) bounces.
PD4-3607696884 Check for gPTP destination for MAC address on packet receive, along with
ethertype check, instead of just ethertype check.
PD4-3178426264 Add Energy-Efficient Ethernet support to ExtremeXOS.
PD4-1678280326 File system commands such as ls .* exposes internal files.
PD4-3200169071 Within VR CLI context unable to configure the MLAG peer IP address
without specifying the VR <vrname> parameters.
PD4-3338939478 ESRPv6 + DAD: Duplicate IPv6 address is detected though there is no
duplicate address while disabling/enabling ports between ESRP master and
L2 switch.
PD4-1402339707 The following Warning message should be deleted for BlackDiamond 8900
xl- and c-series cards when the switch is supporting 256 VRRP instances:
WARNING: Number of VRs has reached the recommended
maximum (128).
PD4-3604746776 Configuring TDM UDP CESoP pseudowire with unsupported UDP port range
does not produce warning messages.
PD4-3735274521 Process VMT process ends unexpectedly when enabling VM-tracking from
Ridgeline.
PD4-3908211905 Six ARP requests are generated for every packet with an unknown
destination when there should be only two requests.
PD4-3964907890 When configuring an EAPS ring port that is also a mirror port used for
remote mirroring, an error occurs.
PD4-3819192600 Disabling, and then enabling, sharing of a LAG port in VRRP-enabled VLANs
should be allowed without requiring disabling VRRP.
PD4-3955966073 Error message appears while receiving LACP marker PDU from other vendor
products.
PD4-3735477892 Jumbo frame-sized packets are not fragmented and thus dropped if ingress
port and egress LAG member port fall on the same unit.
PD4-3743455964 STP port status moves from blocking to forwarding state when a VLAN tag
is changed.
PD4-3600411991 When a load sharing port is added to five or more STP domains, show
sharing detail output has "Error: Missing inputs, cannot process" and
it is not showing more than five STP domains.
PD4-3746064251 Traffic from service VMAN is not forwarded out of VPLS tunnel if service
VMAN port is associated with a LAG.
PD4-3539042771 Deleting an untagged port of a VMAN that is assigned to VPLS causes
traffic for tagged VLAN and CEP ports to be discarded.
PD4-3539042778 Removing a VMAN with untagged port from VPLS followed by removing a
VLAN with tagged port from VPLS, disrupts traffic for the VMAN with CEP
port on the same port as the untagged VMAN and tagged VLAN.
PD4-3710524706 During authentication, a user rejected by Radius/TACACS server should not
be allowed to authenticate via local database.
PD4-3553937513 Existing account password cannot be changed if password string contains
'&' or '<' special characters.
PD4-3664359498 Applying access-profile to SSH2 produces an error.
PD4-3747603680 ELRP-disabled port is appears as enabled on ScreenPlay.
PD4-3889145592 The Kerberos-related rules are not uninstalled after triggering Kerberos
detection.
PD4-3715382228 The command disable ip-security arp learning learn-
from-arp vlan <vlan_name> ports <ports> appears
incorrectly in show configuration.
PD4-3966431930 The command enable netlogin dot1x guest-vlan ports
<port no> configuration disappears after rebooting the switch.
PD4-3978670314 Process climaster ends unexpectedly in legacy CLI mode when commands
like configure, clear, and show, which have an enter option after them,
are executed.
PD4-3687171778 In show log output the peer-id logged for MLAG port events is different
from the configured peer-id.
PD4-3282517473 Help message does not appear for the symbol "|" in some CLI commands.
PD4-3621399094 File system commands like 'ls .*' from CLI prompt exposes internal files.
PD4-3938573760 Protocols deleted from a user-created VR stay in the stopped state and
error message appears after trying to save the configuration.
PD4-3683540269 In CLI scripting, $READ statements in both IF and ELSE conditions are
executed at the same time even though only one of the IF/ELSE condition is
satisfied.
PD4-3894198226 Egress mirroring does not work for CPU-generated packets when the
mirrored and mirroring ports reside on different units.
PD4-3955776775 Loops are created after disabling, and then enabling VLANs that contains
ports with the software redundant port feature enabled.
PD4-3649152417 VSM memory leak occurs on backup slot when link state changes.
PD4-3249665236 Need to automatically adjust for ingress and egress time stamp latency. This
problem causes the latency between switches to seem longer than it
actually is, which can keep gPTP from working (specifically from becoming
asCapable) on certain links, particularly BASE-T links.
PD4-3583325783 Ignore the reserved field in the talker message, and reset it to zero.
PD4-3645327006 Received LeaveAll causes registrations to expire (listener).
PD4-3645326972 Transmitted LeaveAll causes registrations to expire (domain).
PD4-3583325751 Occasionally, Summit series switches stop responding when running with
298 listeners and 294 talkers.
PD4-3650034577 Listener deregistration proxy is not currently implemented.
PD4-3657864803 In MVRP, don't forward frames with MVRP MAC DA.
PD4-3799025391 Occasionally, when Summit X430 series switches reboot, ExtremeXOS
doesn't fully initialize (one or more processes remain in "LoadCfg" state).
PD4-3347131581 On Summit X440 switches, OpenFlow needs support to respond with
ALL_TABLES_FULL.
PD4-3346145041 On Summit X440 switches, OpenFlow action to output special port
controller does not work when used with a multiple action.
PD4-4178247741 The following error log occurred on a Summit X430 switch while running
AVB: <Erro:Kern.Error> ems: (ems_main.c:471) BUG:
scheduling while atomic: fdb/1220/0x10000200.
PD4-3752494335 The wrong QoS profiles are used for AVB on Summit X670V-48t switches.
PD4-3716427706 Support AVB on Summit X430 series switches.
PD4-3660435514 UNH TEST: MSRP.c.35.1.3MSRPDU Protocol Version
Need to implement handling for future MSRP versions.
PD4-3660435458 Failing test Test MVRP.c.11.1.5Use of ProtocolVersion.
Handling for MVRP future protocol versions is not implemented.
PD4-3751374191 In Summit X440-24x series switches, front panel ports from 1 to 16 dont go
to the active state even though they are connected; they stay in the ready
state, whereas ports from 1 to 28 move to active state after connecting to
another switch.
The issue occurs in standalone and stacks of Summit X440-24x-10G series
switches.
PD4-3470152622 In Summit X440-24x-10G/24p series switches, SX optics are not entering
the active state even when the connected between Summit X440-24x-10G
series switches. BASET link is coming up in these ports.
PD4-3799118556 Implementation of rate limiting on the management Ethernet port is not in
effect for the Summit X430 series switches.
PD4-3553805121 On Summit X430 series switches, you are unable to download and install
bootROM image through the CLI.
PD4-3478131812 Summit X440 stack displays the following warning message during stack
boot up without any configuration:
<Warn:Kern.Card.Warning> Slot-5: i2c-1:
shid_eeprom_tlv_readv:10785 I/O failed, addr 0x0057
rd/wr 0 cmd 0 proto 2, rc 145
shid_9506_write:91 I/O failed, addr 0x0020 rd/wr 0
cmd 9 proto 2, rc 145
shid_9506_init:67 I/O failed, addr 0x0020 rd/wr 0 cmd
11 proto 2, rc 145
<Warn:HAL.Sys.Warning> Slot-2: Got an unknown
checkpoint message (49452)
PD4-3528154577 On Summit X430 series switches, the show power command displays the
state as "Present" instead of "Empty/Power Failed/Powered Off/Powered
On".
PD4-3665980230 In Summit X440 series switches, traffic is not properly redirected when the
redirected ports are across switches.
PD4-3566485046 On Summit X440-24x-10 G switches, Tx/Rx flow control is not working.
PD4-3496982495 In Summit X430 series switches, multi-port FDB not working on all ports
configured on a switch.
PD4-3752494982 Enabling AVB causes continuous errors like: <Crit:MRP.ParmInv> Invalid
Parameter mvrpPort : (nil)
PD4-3745132292 A more meaningful error message should appear when you type the partial
command show msrp streams de, rather than the error:
args(<destination_mac_addr>)": no such element in array.
PD4-3678111867 The command show msrp talker and listener output needs a
line for total streams.
PD4-3683687317 "Error: Maximum number of timers exceeded" error appears when AVB is
enabled for all ports on Summit X670 series switches.
PD4-3732868787 Incorrect "Dec" field in command show msrp talkers ingress-
and-egress stream-id.
PD4-3744816030 On Summit X670 series switches, enable/disable AVB causes
Erro:HAL.PTP.Error.
PD4-3761438209 On Summit X430 series switches, process HAL ends unexpectedly with
signal 11.
PD4-3801691810 On Summit X670 series switches, process rtmgr ends unexpectedly with
signal 11 after executing the command config iproute add.
PD4-2897495711 Summit X480 series switches stop operating with exstart/exchange with 64
OSPFv3 neighbors.
PD4-3715628671 The default IPMC forwarding look-up in the Summit X430 switches is
incorrect.
PD4-3432539001 Reverting the VMAN Ethernet-type to default causes 802.1q egressing traffic
E-type to 0x88a8.
PD4-3064998712 In Summit X480 series switches with VIM3-40G4X and SummitStack, the
following error message occurs after issuing save and reboot with custom
LACP load sharing:
<Erro:HAL.Port.CfgTrunkFail> Failed to configure load
sharing group 27 on slot 1 unit 0: Entry not found
Traffic does not appear to be affected. This problem
does not occur with version ExtremeXOS 15.1.2.12.
PD4-3762256576 L2MC entries limited to 1,024 on Summit X670 series switches (should
support 8,000).
PD4-2488384169 In Summit X440 series switches, the maximum number of L3 interface
supported is 256 only. Switch allows user to create more than 256 L3
VLANs and displays no error/warning message.
PD4-3736310801 VRRP IPv6 master found on an MLAG peer gets stuck in Init after all ports
are disabled/enabled.
PD4-3603702297 For EAPSv2, when segment ports and shared ports are disabled, and then
enabled, in very quick succession, sometimes the segment port can remain
blocked for up to 10 seconds.
PD4-3746321094 ERPS with ELSM malfunctioning when CFM/CCM is enabled.
PD4-3955966425 For Summit X460 series switches, ScreenPlay does not display device
images.
PD4-2562996591 MIB value for OID extremeInputPowerVoltage is incorrect or null for Summit
X460 series switches, E4G-400 cell site routers, and BlackDiamond 8800
series switches.
PD4-3896834010 Summit switches do not display power usage under show power detail
when redundant power supply is unplugged, and then plugged back in.
PD4-4010837605 For Summit X440 series switches, fan failure messages appear randomly in
log even though the fan is in working condition.
PD4-3747290416 In Summit stacks, false fan failure SNMP traps are triggered.
PD4-3747350653 In Summit X670 series switches, known unicast traffic is not shared between
the stacking ports when v320 G stacking is enabled.
PD4-3657842918 In Summit X440 series switches, slot fails while sending multicast packet
from one node to another.
PD4-3683625771 In Summit X440 series switches, mirroring fails after a save and reboot
when an active port is configured as a loopback port.
PD4-3597610655 Summit stacks in ring mode get converted to daisy-chain mode or dual
master state after rebooting. This happens when stacking is formed using
alternate stack ports having SFP+ from Sumitomo Electric and OpNext
vendors.
PD4-3755290543 Summit X440-48p switches are not delivering power after enabling the
following modules: SSH2, QoS, Diffserv, and LLDP.
PD4-3649152546 VIM module ports are not initialized properly if the switch was booted with
a different configuration in which the VIM module ports were not present.
SummitStack
PD4-3749178525 After failover in stack, show configuration command shows the
details about the LI mirror instance.
PD4-3784189712 Part Information for stack node power supplies does not appear, or is only
partially visible, in the show power detail command from the master.
PD4-3394937567 On Summit X670V-48x stacks, the following warning messages appear on
reboot:
<Warn:HAL.Port.Warning> Setting EDC mode to SR_LR
for userport 48 failed (-3)
<Warn:HAL.Port.Warning> Getting EDC mode to SR_LR for
userport 48 failed (-3)
PD4-3682688331 The following error messages appear while rebooting a Summit X440-24x-
10G stack:
shid_9506_init:67 I/O failed, addr 0x0020 rd/wr 0 cmd
8 proto 2, rc 145
05/06/2013 16:41:44.51 <Warn:Kern.Card.Warning> Slot-
4: i2c-1: shid_9506_init:52 I/O failed, addr 0x0020
PD4-3971032840 WideKey_ACL: ACL process ends unexpectedly with signal 6:
#0 0x2ac494d0 in dmGetObjInfoIndex (obj_id=33619968,
name=0x0) at dmdb.c:41
41 if( dmObjDB[i] ).
PD4-3749178401 After executing the second failover in a SummitStack the access-list created
by liuser appears on admin session and the admin is able to use or delete
the access-list. Also, the LI user lacks the privilege to use the access-list.
PD4-3705853173 Process devmanager ends unexpectedly with signal 5.
PD4-3763533283 The snmpwalk results in lexicographic errors on Summit stack switches
(PD4-2288889611) problem is not fixed on the following stack condition:
3-node stacking
slot 1: backup
2: master
3: standby
PD4-3298731387 In Summit X670v/x670-48x switch stacks, media type does not appear in
command show port configuration output after run failover without
any configuration.
PD4-3921771500 Part information for power supplies of stack nodes does not appear or is
partially obscured in show power detail from master. Also, part
information for power supplies of stack standby nodes does not appear in
show power detail from master.
PD4-3282121167 During EAPS/STP failover, the following error messages appear (it seems for
some IPv4/IPv6 multicast groups egress port does not get added in MM-B.):
<Erro:HAL.SM.Error> MM-B: esfmEntityAddEgressPort:
entity does not exist 12/13/2012 16:45:19.26
<Erro:HAL.SM.Error> MM-B: esfmEntityAddIngressPort:
entity does not exist entity=60 12/13/2012
16:45:19.26 <Erro:HAL.SM.Error> MM-B:
esfmEntityAddIngressPort: entity same error messages are
observed while doing disable/enable slot.
PD4-3215758818 Applying an ACL that contains both a slow-path and hardware rule is not
being applied correctly.
PD4-3748384377 ESVT does not work; no packets are making it to the ports connecting the
switches.
PD4-3767829275 OSPFV3 ends unexpectedly with signal 11 when deleting/adding member
ports in LACP/LAG.
PD4-3555060888 SNMP gets for BgpPeerTable displays error: "Lexicographical ordering error
detected"
PD4-3555060838 SNMP gets on bgp4PathAttrTable return values for routes from only one
peer, even though there are routes from multiple peers.
PD4-3749178342 Process cfgmgr pid 5917 ends unexpectedly with signal 4 after executing
the restart process bgp command:
Program terminated with signal 4, Illegal
instruction.
[New process 5917]
#0 0xb7fd3eb8 in simple_timer_is_expired
(timer=0x807d2a0) at simple_timer.c:115
115 }
PD4-3660174580 BlackDiamond X8 series switches discard OSPFv3 LSAs for certain prefixes
when the number of prefixes is at least 16.
PD4-3651656741 BlackDiamond X8 series switches fail to apply inter-area filter policy in OSPF
(Message-Get Handle "extern2" interare policy type 2 Data 16777216 failed).
PD4-3603689227 While using DAD to detect duplicate IP addresses, DAD does not detect all
duplicate IP addresses.
PD4-3746321055 Junk IPv6 address appears switch log message when user logs on with IPv4
address through XML.
PD4-3659934141 ACL policy with match conditions like "arp-sender-address" or "arp-target-
address" does not work.
PD4-3821836501 FPGA version and bootROM version do not appear correctly after updating.
PD4-3394909101 Execution of command show log message nvram is very slow.
PD4-4047334270 The error message "bcm_vlan_port_get failed" appears in the output of the
command debug hal show switch-manager vlan.
PD4-3585523118 ExtremeXOS 15.2.1/ScreenPlay: Temperature row is showing RED even
when the slots are running under recommended normal temperature level
(25100 C).
PD4-3571353340 Power budget calculation is not accurate in the show power budget
output.
PD4-3818645461 LACP port does not become active after enabling the ports.
PD4-4095826315 When one master switch fabric module (MSM) is at version ExtremeXOS
15.4.1 and another has a version earlier than version ExtremeXOS 15.4.1, the
following errors may appear:
"<Info:HAL.Port.RateLimit> MSM-B: Flood Rate Limiting
activated on Port 7:193"
These messages can be ignored until you upgrade the MSM.
PD4-3745167193 EXOS_CPU_MONITOR : for OID of extreme CPU Monitor System Table,
snmpCheckKeyValue ------fails
PD4-2231030022 The script "default.xsf" loads before all slots are operational and returns
"Some errors while loading script" error message.
PD4-3763533301 Process rtmgr crash with signal 11 occurs after deleting the routes in the PE.
PD4-3672900190 Continuous messages appear on the BlackDiamond 8800 series switches
console in the advanced edge license mode. The BlackDiamond 8800
switch has OSPF configuration and PIM-SM configuration to form
neighborship with a Summit X480.
PD4-3291342581 While executing run msm fail-over command on BlackDiamond 8800
series switches, the following error messages appear:
11/23/2012 18:05:09.47 <Erro:Kern.Card.Error> Slot-
9: exSmIpmcBitmapSetComplete: failed to set bitmap,
group=39, unit=1, err=-7 11/23/2012 18:05:09.47
<Erro:Kern.Card.Error> Slot-9:
exSmIpmcBitmapSetComplete: failed to set bitmap,
group=74, unit=1, err=-7 01/16/2013 16:13:57.14
<Erro:HAL.SM.Error> MSM-A: aspenSmIpmcAddEgressPort:
group does not exist 01/16/2013 16:13:57.14
<Erro:HAL.IPv6Mc.Error> MSM-A: SM failed to add
PD4-3820269786 When distributed ARP mode is enabled with a significant number of ARP
entries, the next hop MAC address in the hardware is entered incorrectly
producing L3 reachability issues.
PD4-3778998471 The process mcmgr ends unexpectedly in an MLAG peer switch when an
ISC is added as a router port.
PD4-3573825955 Traffic fails to switch over to next available gateway after removing master
switch fabric module physically.
PD4-3534217537 Remote mirroring on a source switch is enabling software learning after
rebooting the switch with the configuration.
E4G Cell Site Routers
PD4-3189248300 In E4G-400 cell site routers, the command show configuration CES
is showing a default configuration and payload is getting changed when
adding E1 MF in pseudowire.
PD4-3418752871 When E4G-200-12X cell site routers are operated below -35C, the E4G-CLK
module may not come up.
Additionally, ExtremeXOS restarts repeatedly due to a PCIe access
exception.
PD4-3759692627 In normal L2 VLAN TDM UDP pseudowire traffic is forwarded to the CPU,
unless IP forwarding or loopback is enabled on the VLAN. Need a CLI check
to ensure that IP forwarding is enabled on VLANs that have TDM IP
pseudowires.
PD4-2988764571 TDM MEF-8 pseudowire goes down when IP forwarding is enabled on
transport VLAN.
ACLs
PD4-3803186901 In Summit X480 series switches, you cannot create 4096 ACL meters.
PD4-4214618876 Memory leak occurs after creating and deleting ACL network-zones with IP/
MAC attributes.
PD4-4213803680 Memory leak occurs after configuring and unconfiguring ACL policies that
have network-zones.
PD4-4214074273 The access-list policy is not applied when using destination-zone attribute in
the rule entry for the first time.
PD4-4214074114 ACL that permits a specific TCP port range does not work if the destination-
zone attribute appears in the policy file.
PD4-4213889932 ACL process signal 6 ends unexpectedly when refreshing zone policies.
PD4-4181588294 ACL rule to match all IPv6 packets is incorrectly matching all other packets,
as well when match condition source-address ::/0 is used.
PD4-3624118212 Missing semi-colon after mirror-CPU action modifier ends ACL process
unexpectedly even though check policy reports successful.
PD4-3735860737 Changing ACL rule-compression port counters mode from shared to
dedicated does not take effect even after unconfiguring and then
reconfiguring all ACL policies.
PD4-3896140275 System ACL rule corresponding to IP multicast control packets is not
uninstalled even after executing the command configure
ipmcforwarding to-cpu off port <all ports>.
AVB
PD4-4240972555 Switches learn source MAC addresses on gPTP, LACP, and LLDP packets.
These packets may be transmitted over blocked ports, which can cause
incorrect source MAC address learning of a switch MAC address by the
switchs peer. This incorrect MAC address learning may disrupt in-band
traffic destined to the switchs MAC address.
PD4-4240339930 If an MSRP stream has more than one listener, and then all but the last
listener are terminated, the switch sends a leave message toward the talker
for the stream. As a result, the switch may send a leave message for a
stream that has an active listener, which prevents that listener from
receiving the stream data until another listener joins the stream.
BGP
PD4-3445591850 DCBGP process ends unexpectedly after deleting a disabled IBGP peer after
a BGP process restart.
PD4-4119249815 IPv6 routes learned by BGP are not reachable even though they appear in
the output of the show iproute ipv6 command.
PD4-2673641839 Switches are not advertising to their IBGP and EBGP peers the direct routes
(for locally connected ESRP member VLAN) redistributed via the BGP
network command when they are ESRP slaves, and then become masters.
PD4-2248362101 The AS path for the dampened routes does not appear.
PD4-3218758011 In BGP executing the command enable bgp peer-group p1
capability ipv4-unicast produces the following error:
Error: missing close-brace and the cli does not
work
PD4-4019373011 Process dcbgp ends unexpectedly when creating a BGPv6 neighbor with an
IPv6 address greater than 32 characters.
EAPS
PD4-3430977491 The send-igmp-query keyword should be deprecated in the EAPS and
ERPS configure eaps multicast commands.
ESRP
PD4-3638894408 Configuring ESRP HA port to multiple VLANs in the same group should not
be allowed.
PD4-3936248185 Restart timer configuration appears in command show config esrp
output even if it is the same as the default value.
PD4-3579843151 Manual ESRP failover takes neighbor time-out instead of normal hello time-
out.
PD4-3992717614 Traffic originating from an ESRP master switch to the host attached to the
ESRP slave switch fails when host attach port is part of two different ESRP
domains that reside in the same ESRP group.
PD4-3745284232 Link local address DAD state changes to tentative, which incorrectly brings
down the routing interface.
PD4-3605317320 PIM: After a switch reboots, PIM operational status is up for a VLAN that
does not have any active ports. If the VLAN is disabled, PIM operational
status still appears up. The issue is occurs only for PIM IPv4.
PD4-3605317200 PIM-ECMP-source based hashing: Traffic loss occurs for six minutes after
master switch fabric module failover occurs on the first hop router.
PD4-3605317125 ECMP-PIM: The first hop router forwards the traffic via two paths after a
rendezvous point location change. This state lasts for up to approximately
three minutes.
PD4-3605317065 ECMP-PIM: Traffic loss and excessive CPU utilization occur after L2/L3
connectivity between last hop router/first hop router/rendezvous point is
lost on ECMP path.
The first hop router starts flooding the rendezvous point with register
packets. The rendezvous point responds with register stop packets, but the
first hop router seems to ignore them.
PD4-3605317015 ECMP-PIM: The fist hop router transmits duplicate traffic after an iBGP path
change for approximately 30 seconds to two minutes.
PD4-3605316965 ECMP-PIM: The traffic fully recovers after 3.30 minutes after the ingress
VLAN on the first hop router is disabled/enabled.
PD4-3605316915 ECMP-PIM: excessive CPU utilization and traffic loss occurs for
approximately three minutes on the rendezvous point after the OSPF area
ID is modified on the first hop router.
PD4-3672900239 ECMP-PIM-MSDP: Traffic never recovers after an rendezvous point change
and an OSPF route bounce.
PD4-3565382741 Router is not re-advertising OSPFv3 routes with new link-local addresses
when the link-local addresses are changed.
PD4-4077560753 System ends unexpectedly with "Process isis pid 1616 died with signal 11"
error after deleting ISIS area from ISIS-IPRoute-Compress module on
BlackDiamond 8800 and Summit X460 series switches.
PD4-3490122907 Executing the following commands cause the system to stop working:
configure iproute add default [{<gateway> {<metric>}
{vr <vrname>}{unicast-only | multicast-only}} | {lsp
<lsp_name> {<metric>}}]
configure iproute add [<ipaddress> <netmask> |
<ipNetmask>] lsp <lsp_name> {metric} {multicast |
multicast-only | unicast | unicast-only} {vr
<vrname>}
PD4-3518776440 ECMP-PIM-SMv6: After a link local address is replaced, the downstream
neighbor does not update its (S;G)s and (*;G)s and 50% traffic loss occurs.
PD4-3698242152 Disabling/enabling the port in the VLAN Lagg1_Lcore1 produces warning
OSPF messages.
PD4-3091884271 Increase the severity for IPv4MC and IPv6Mc group table full messages so
that they appear in the log by default.
PD4-3048923401 The conf igmp snooping forwarding-mode command is
overriding the configuration of the configure forwarding ipmc
lookup-key command. It should not, since the latter command affects
IPv4 and IPv6 and supports newer options. Need to deprecate the igmp
snooping command.
PD4-3897846462 OSPF sends LS update packets with checksum 0xffff.
PD4-4007632107 ABR stops translating AS external routes (type 7) to another area (type 5)
after OSPF is configured with graceful restart.
PD4-3814562890 Changing OSPFv3 timers to area 0.0.0.0 affects all areas.
PD4-3855305064 OSPFv3 stub nosummary is not working/configurable.
PD4-3801692027 For PIMv6, traffic drop occurs when all ports are restarted on a last hop
router/rendezvous point connected to a multi-access VLAN.
PD4-3831014417 Secondary IP address for a VLAN is unusable after deletion and then re-
configuration of any other existing secondary IP address in the same VLAN.
PD4-4014670293 Some VPNv4 routes do not appear after disabling and then enabling the
port of a switch that is connected to a 12+ PE over the single port.
MPLS
PD4-3976362585 In VPLS, FDB is not learned on service VLAN ports after a switch reboot.
PD4-4089565096 Need CLI option in VPLS to tunnel Layer 2 control packets (LACP, EDP, STP,
etc.) across VPLS cloud.
PD4-3858989010 OSPF neighbourship over L2 VPN fails when IGMP snooping filter per-VLAN
is configured on the switch.
PD4-3041215900 MPLS.RSVPTE.InternalProb: 0x00002102-34 (327) error
occurs while querying the route. Log is generated after NSLO failover in
MPLS system.
PD4-2686425957 MPLS label ranges should be configurable.
OpenFlow
PD4-3716427501 With ten flows in the switch, send flow to modify some of the flows, and
then disable OpenFlow, an OpenFow process goes down.
Security
PD4-3643292293 Debug commands are not recognized and not accepted when debug mode
is not enabled.
PD4-3966431930 The enable netlogin dot1x guest-vlan ports <port no>
configuration disappears after rebooting the switch.
PD4-3917791218 ID Manager: Bind for open LDAP is not working.
PD4-4102955114 A new CLI is needed enable/disable local authentication in TACACS when
the client IP address is excluded in the TACACS server list.
SNMP
PD4-3022182521 downloadNotMaster(3) is not the correct option in download status
messages.
PD4-3878679047 IP addresses are truncated in switch's log message when SNMP walk is
executed a with an incorrect community name.
PD4-3553937843 Process snmpSubagent ends unexpectedly with signal 6 when retrieving
one of the variable in the ifentry.
STP
PD4-3672899749 Spanning-tree participation is lost for a trunk after switch reboot.
VLANs
PD4-3353962932 PVLANs can be configured as EAPS control VLANs.
PD4-3747603805 Unable to delete the port from the a VLAN via the snmpset operation.
VMAN
PD4-3621148540 VMAN traffic egressing LAG ports is suppressed if LAG ports are configured
to use secondary ethertype.
PD4-3802664280 Kernel error message appears while configuring CEP translation for two
different VMANs with the same port and same target VLAN ID.
VRRP
PD4-3955966234 Process rtmgr ends unexpectedly with signal 11 after disabling, and then
enabling a port in the switch with VRRP configuration.
PD4-3641036572 HAL memory leak occurs while flapping VRRP backup.
XML
PD4-3679406587 Switch console/Telnet session continues executing any command after
clicking save config tab in ScreenPlay.
PD4-3896401550 Need a CLI command to configure a source IP to send an XML notification.
PD4-3583969302 Configuring SNMP community name with special characters is getting
rejected.
4
ExtremeXOS Documentation
Corrections
This chapter lists corrections to the ExtremeXOS 15.4 Concepts Guide and ExtremeXOS 15.4
Command Reference.
ACLs on page 149
ELRP on page 151
End of Support for BlackDiamond 12800 Series Switches on page 152
Multi-cast VLAN Registration on page 152
Network Login: Web-Based Authentication on page 152
Policies and Security on page 153
RADIUS Server Client Configuration on page 153
Rate Limiting/Meters on page 154
sFlow Sampling on page 155
Show Ports Transceiver Information Command on page 156
Configuring VMANs (PBNs) on page 156
VRRP on page 157
ACLs
ExtremeXOS Concept Guide
Chapter 20: ACLs, under the heading ACL Rule Syntax
PD4-4367440234
The following text (bullet point):
mirrorSends a copy of the packet to the monitor (mirror) port (ingress only, and
supported in egress only in x460 and E4G400 switches).
Should be changed to:
mirrorSends a copy of the packet to the monitor (mirror) port (ingress only, and
supported in egress only on Summit X460 series switches and E4G-400 cell site routers).
Rules that contain mirror as an action modifier use a separate slice.
ExtremeXOS Concepts Guide
Chapter 20: ACLs, under the heading Apply ACL Policy Files
PD4-4197196994
ExtremeXOS Documentation Corrections
The following note should appear:
Chapter 3: Managing the Switch
xos0057249
The following text should be removed from multiple places under the
indicated chapter:
Only source-address match is supported.
Access-lists that are associated with one or more applications
cannot be directly deleted. They must be unconfigured from the
application first, and then deleted from the CLI.
Default counter support is added only for ACL rules and not for
policy files. For policy files, you must configure count action.
NOTE
If an ACL needs to be installed for traffic that is L3 routed and the ingress
and egress ports are on different packet-processing units/ different slots
with any of the following features enabled, then you should install the
policy on a per-port basis, rather than applying it as a wildcard/VLAN-
based ACL:
MLAG
PVLAN
Multiport-FDB
ELRP
ExtremeXOS User Guide, section "Using ELRP to Perform Loop Tests
xos0057320
The following known limitation of ELRP on VPLS service VLANs for Summit X480 series
switches should appear:
On Summit X480 series switches, ELRP does not detect a loop when enabled on a VPLS
service VLAN. This is a hardware limitation.
You can work around this limitation using an ACL that copies the ELRP packets to the
switch:
1 Find out the switch's MAC address and ELRP destination MAC address.
The ELRP PDU's destination MAC address would be the switch MAC address with 01
for the first octet. For example, if the switch MAC address is 00:04:96:51:12:32, then
the ELRP PDU's destination MAC address is 01:04:96:51:12:32.
2 Create an ACL that moves the packets to the CPU that are destined to the ELRP
destination MAC address and having Self MAC as the source address.
create access-list elrp_lift "ethernet-source-address
<switch_ethernet_source_address>; ethernet-destination-address
<ELRP_Dest>" "copy-cpu-and-drop"
In this example,
create access-list elrp_lift "ethernet-source-address
00:04:96:51:12:32; ethernet-destination-address
01:04:96:51:12:32" "copy-cpu-and-drop"
3 Now associate the access-list with the VPLS service VLAN on which the ELRP is to be
enabled or apply it to the entire switch by the use of any option.
configure access-list add "elrp_lift" first any
or
configure access-list add "elrp_lift" first vlan <vlan_name>
NOTE
While this procedure deals with this limitation, you use one more ACL rule. So, if there
are other Extreme Network devices in the service VLAN network that do not run
VPLS, then it is recommended that you enable ELRP on those devices instead of
using this workaround which will consume ACL resources.
End of Support for BlackDiamond 12800 Series Switches
ExtremeXOS Concepts Guide and Command Reference
Throughout the documentation
PD4-4586509611
ExtremeXOS 15.2 and later does not support the BlackDiamond 12800 series switches. Any
reference implying support is incorrect.
Multi-cast VLAN Registration
Chapter 42: Multi-cast Routing and Switching under the heading Multi-cast VLAN
Registration
PD4-4356120873
Network Login: Web-Based Authentication
Chapter 23: Network Login under the heading Web-Based Authentication
PD4-4433918271
Under the heading Configure the Redirect Page, the following text:
By default, the redirect URL value is http://www.extremenetworks.com.
Should be changed to:
By default, the redirect URL value is http://www.extremenetworks.com and default re-
direction takes a maximum of 20 seconds (the default netlogin-lease-timer + 10 seconds).
Re-direct time can be changed by tuning the netlogin-lease-timer.
NOTE
Multi-cast VLAN registration is not supported on Summit X430 series switches.
Policies and Security
Chapter 20: ACLs > Policy-Based Routing > Layer 2 Policy-Based
Redirect
xos0057861
The following note should appear
RADIUS Server Client Configuration
ExtremeXOS Command Reference
Chapter 23: Security Commands under the configure radius server client-ip
command
PD4-4385727966
The following note should appear::
NOTE
"redirect-port" or "redirect-port-list" does not work for L3-switched
packets matching ACL, if distributed IP ARP feature is turned on.
NOTE
You should enable loopback mode on the VLAN associated with RADIUS if the
RADIUS connectivity is established using a front panel port on a SummitStack.
Rate Limiting/Meters
ExtremeXOS User Guide for the configure ports qosprofile command
xos0057795
Need to include the following line above the example section:
"If max-burst-size has configured as "0", then it will use maximum
available burst value."
Also, change the following:
The max-burst-size parameter is the amount of traffic above the value
in the cir-rate parameter that is allowed to burst from the port(s) for a
short duration.
To:
The max-burst-size parameter is the amount of traffic above the value
in the cir-rate parameter that is allowed to burst from the port(s) for a
short duration. If max-burst-size has configured as "0", then it uses the
maximum available burst value.
sFlow Sampling
ExtremeXOS Concepts Guide and ExtremeXOS Command Reference
PD4-4347653204
ExtremeXOS Concepts Guide Change
Chapter 12: Status Monitoring and Statistics under the heading Enable sFlow on the
Desired Ports
Under the first bullet point, the text:
enable sflow ports port_list {ingress | egress | both}
The ingress, egress, and both options allow you to configure the sFlow type on a given set
of ports. If you do not configure an sFlow type, by default ingress sFlow sampling is
configured on the port.
Should be:
enable sflow ports all | port_list
By default ingress sFlow sampling is configured on the port.
ExtremeXOS Command Reference Change
Chapter 13: Commands for Status Monitoring and Statistics under the command enable
sflow ports
The command syntax:
enable sflow ports port_list {ingress}
Should be:
enable sflow ports all | port_list
Additionally:
Remove the description of "ingress" from Syntax Description table.
Under the heading History, remove the content "The ingress, egress, and both
keywords were added in ExtremeXOS 15.3"
Show Ports Transceiver Information Command
ExtremeXOS Command Reference Guide
Chapter 6: Commands for Configuring Slots and Ports on a Switch, under the command
show ports transceiver information
PD4-3928242896
Configuring VMANs (PBNs)
Chapter 14: VMAN (PBN), under the heading Configuring VMANs (PBNs)
PD4-4356948061
Several corrections are required for the table Port Support for Combined VMAN Roles and
VLANs":
Superscripts 5, 6, 7, 8, 9 are misprinted as a, b, c, d, e, correspondingly. Also, the
superscript in the row "Summit X440, X460, X480, X60, and X770,and E4G-200 and
E4G-400" should change to 9.
The following footnote explanations should be corrected as follows:
5Subsets of this group are also supported. That is, any two of these items are
supported.
6When a CNP is combined with a CEP or tagged VLAN, any CVIDs not explicitly
configured for a CEP or tagged VLAN are associated with the CNP.
7A PNP (tagged VMAN) and a CNP (untagged VMAN) or CEP cannot be
combined on a port for which the selected VMAN ethertype is 0x8100.
8The VMAN ethertype must be set to 0x8100, which is different from the default
value (0x88a8).
9If the secondary VMAN ethertype is selected for the port, it must be set to
0x8100.
NOTE
In the show ports transceiver information output, the Rx/Tx power
values shown may be +/- 3dB from the actual value due to limitations of SFP
and the accuracy depends on the SFP vendor. For accurate power measurement,
it is recommended to use a power meter.
VRRP
Chapter 31: VRRP under the heading "VRRP Guidelines"
xos0056279
The VRRP guidelines should change to the following:
The following guidelines apply to using VRRP:
The maximum number of supported VRIDs per interface is seven.
An interconnect link between VRRP routers should not be used,
except when VRRP routers have hosts directly attached.
A maximum of 128 VRID instances are supported on the router. This
number can be extended up to 256 based on the license and
hardware; refer to the release notes for the maximum limit.
Up to seven unique VRIDs can be configured on the router.
VRRP and other L2 redundancy protocols can be simultaneously
enabled on the same switch.
We do not recommend simultaneously enabling VRRP and ESRP on
the same switch.
When VRRP and BOOTP/DHCP relay are both enabled on the
switch, the relayed BOOTP agent IP address is the actual switch IP
address, not the virtual IP address.
VRRP and ESRP cannot be configured on the same VLAN or port.
This configuration is not allowed.
RFC 5798 describes a situation where a master VRRP router takes
on a duplicate IP address due to interaction with the duplicate
address detection (DAD) feature. To prevent such duplicate
addresses, the DAD feature is disabled whenever a VRRP router is
configured for IPv6 or IPv4.
A VRRP router instance can be configured with multiple IP
addresses on the same subnet or on different subnets, provided that
all virtual IP addresses match the subnet address of a VLAN on the
switch. For example, if a host switch has VLAN IP addresses in the
1.1.1.x and 2.2.2.x subnets, then that VRRP router instance can contain
virtual IP addresses in both those subnets as well.
If a VRRP router instance is assigned priority 255, then the host
router must own all the IP addresses assigned to the VRRP router
instance. That is, each virtual IP address.
When a VRRPv2 instance spans routers using ExtremeXOS version
12.6 and earlier and routers using ExtremeXOS version 12.7 and later,
routers using ExtremeXOS version 12.6 and earlier log packet-size
warning messages.
VRRP scaling numbers differs based on the license and hardware
used; please refer the release notes for individual scaling limits.
Seven unique VRIDs can be configured on a router.
The maximum number of VIPs supported for a single VRRP instance
is 255.

ExtremeXOS 15.4.2-Patch1-3 RelNotes PDF

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

ExtremeXOS 15.4.2-Patch1-3 RelNotes PDF

Uploaded by

Copyright:

Available Formats

ExtremeXOS Release Notes

Software Version ExtremeXOS 15.4.2-Patch1-3

15.4.2-Patch1-3, which adds and corrects

You might also like