ExtremeXOS 15.7.1 Release Notes

ExtremeXOS 15.7.1 Release Notes
ExtremeXOS Release Notes
Software Version ExtremeXOS 15.7
121109-00 Rev02
Published May 2015
121109-00 Rev02
Copyright © 2015 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 95134
Tel: +1 408-579-2800
Toll-free: +1 888-257-3000
Table of Contents
Overview.....................................................................................................................7
New and Corrected Features in ExtremeXOS 15.7 ..............................................................................................7
Bridge and Q-Bridge Management Information Bases (MIBs) .............................................................. 9
Supported Platform ......................................................................................................................................... 9
Limitations ........................................................................................................................................................... 9
Open Shortest Path First (OSPF)v2/v3 Import Policy Improvements ..............................................10
Supported Platform ........................................................................................................................................10
Affected Commands ......................................................................................................................................10
ExtremeXOS Trivial File Transfer Protocol (TFTP) Client MTU/Block-Size Configuration ......... 11
Supported Platform ......................................................................................................................................... 11
Changed CLI Commands ............................................................................................................................... 11
ExtremeXOS I/O Native Applications Support ........................................................................................... 12
Supported Platforms ...................................................................................................................................... 12
New CLI Commands ....................................................................................................................................... 12
ExtremeXOS Web-Based GUI: Chalet ............................................................................................................. 13
Supported Platforms ...................................................................................................................................... 13
Label-Switched Path (LSP) Fast Failover ...................................................................................................... 13
Supported Platforms ...................................................................................................................................... 13
Limitations ..........................................................................................................................................................14
Changed CLI Commands ..............................................................................................................................14
Multi-protocol Label Switching (MPLS) Resource Reservation Protocol - Traffic Engineering
(RSVP-TE) Explicit Route Option (ERO) Exclude Option ...............................................................14
Supported Platforms ......................................................................................................................................14
Changed CLI Commands .............................................................................................................................. 15
Clear Internet Protocol Address Resolution Protocol (IPARP)/Clear Neighbor-Discovery Refresh ...................................................................................................................................................................... 17
Supported Platforms ...................................................................................................................................... 18
Changed CLI Commands .............................................................................................................................. 19
Minimum Number of Link Aggregation Control Protocol (LACP) Link Aggregate Group (LAG)
Members ..............................................................................................................................................................19
Supported Platforms .....................................................................................................................................20
New CLI Commands ......................................................................................................................................20
Changed CLI Commands .............................................................................................................................20
AAA: Ability to Administer All Default User Accounts ............................................................................ 21
Supported Platforms ...................................................................................................................................... 21
New CLI Commands ....................................................................................................................................... 21
Network Time Protocol (NTP) over Management Port .......................................................................... 22
Supported Platforms ..................................................................................................................................... 22
New CLI Commands ...................................................................................................................................... 22
Limitations ......................................................................................................................................................... 22
Changed CLI Commands ............................................................................................................................. 22
Dynamic Host Configuration Protocol (DHCPv6) Relay—Install Routes for Snooped Delegated
IPv6 Prefixes ..................................................................................................................................................... 23
Supported Platforms ..................................................................................................................................... 23
Limitations ......................................................................................................................................................... 23
New CLI Commands ...................................................................................................................................... 23
3
Table of Contents
Multicast Listener Discovery (MLD) Source Specific Multicast (SSM) Mapping ...........................24
Supported Platforms .....................................................................................................................................24
Limitations .........................................................................................................................................................24
New CLI Commands ......................................................................................................................................24
Changed CLI Commands .............................................................................................................................24
Virtual Machine (VM) Tracking Enhancements for NetSight ................................................................ 25
Supported Platforms ..................................................................................................................................... 25
Network Logon Enhancements for NetSight ..............................................................................................26
Supported Platforms .....................................................................................................................................26
Configuring Power Budget Capability for Summit X430-8p Switches ............................................ 27
CLI Commands ................................................................................................................................................ 27
Zero Touch Provisioning ......................................................................................................................................28
Supported Platforms ..................................................................................................................................... 28
New CLI Commands ......................................................................................................................................28
31-Bit Prefixes on IPv4 Interfaces (RFC 3021) .............................................................................................29
Supported Platforms .....................................................................................................................................30
Limitations .........................................................................................................................................................30
Priority Flow Control (PFC) Statistics per Port ..........................................................................................30
Supported Platforms .....................................................................................................................................30
New CLI Commands ......................................................................................................................................30
Entity Management Information Base (MIB) Port Support .................................................................... 31
Supported Platforms ..................................................................................................................................... 32
Limitations ......................................................................................................................................................... 32
Spanning Tree Protocol (STP) Enhancements ........................................................................................... 32
Supported Platforms ..................................................................................................................................... 32
New CLI Commands ...................................................................................................................................... 33
Changed CLI Commands .............................................................................................................................34
Private Virtual Local Area Networks (PVLANs) Management Information Base (MIB) ............ 35
Supported Platforms ..................................................................................................................................... 35
MAC Address Locking .......................................................................................................................................... 35
Supported Platforms ..................................................................................................................................... 35
Limitations .........................................................................................................................................................36
New CLI Commands ......................................................................................................................................36
Open Shortest Path First (OSPF)v3 Point-to-Point Interfaces ............................................................ 37
Supported Platforms ..................................................................................................................................... 37
CLI Commands ................................................................................................................................................38
ExtremeXOS Secure Shell/Secure Copy Protocol (SSH/SCP) Client Upgrade Using OpenSSH
38
Supported Platforms .....................................................................................................................................38
Limitations .........................................................................................................................................................39
Changed CLI Commands .............................................................................................................................39
Link Aggregation Group (LAG)—Multiple VLAN Registration Protocol (MVRP) Enhancements
39
Supported Platforms .................................................................................................................................... 40
Limitations ........................................................................................................................................................ 40
Changed CLI Commands ..............................................................................................................................41
OpenFlow v1.3 and Pseudowire Multiprotocol Label Switching (MPLS) .........................................43
Supported Platforms .....................................................................................................................................43
Limitations .........................................................................................................................................................44
ExtremeXOS 15.7 Release Notes
4
Table of Contents
Static Generalized Precision Time Protocol (gPTP) Port Roles ...........................................................44
Supported Platforms .....................................................................................................................................44
New CLI Commands ......................................................................................................................................44
Protocol Independent Multicast (PIM) Enhancement: Shortest-Path Tree (SPT) Threshold Option “Infinity” .....................................................................................................................................................45
Supported Platforms .....................................................................................................................................45
Changed CLI Commands .............................................................................................................................45
Deprecation of Domain Field from Open Shortest Path First (OSPF)v3 Commands ........................46
ExtremeXOS Images for Summit X480 Series Switches ...............................................................................46
New Hardware Supported in ExtremeXOS 15.7 .................................................................................................47
Hardware No Longer Supported .............................................................................................................................47
Hardware Issues in ExtremeXOS 15.6 and Later ................................................................................................47
Joint Interoperability Test Command (JITC) Compliance .............................................................................48
ExtremeXOS Hardware/Software Compatibility and Recommendation Matrices .............................48
Compatibility with NetSight .......................................................................................................................................48
Upgrading to ExtremeXOS .........................................................................................................................................49
Downloading Supported MIBs ..................................................................................................................................49
Tested Third-Party Products .....................................................................................................................................49
Tested RADIUS Servers .......................................................................................................................................49
Tested Third-Party Clients ..................................................................................................................................50
PoE Capable VoIP Phones ..................................................................................................................................50
Extreme Switch Security Assessment .................................................................................................................... 51
DoS Attack Assessment ....................................................................................................................................... 51
ICMP Attack Assessment ..................................................................................................................................... 51
Port Scan Assessment ........................................................................................................................................... 51
Service Notifications ...................................................................................................................................................... 51
Limits.........................................................................................................................52
Open Issues, Known Behaviors, and Resolved Issues .....................................106
Open Issues ..................................................................................................................................................................... 106
Known Behaviors ........................................................................................................................................................... 110
Resolved Issues in ExtremeXOS 15.7 ......................................................................................................................112
ExtremeXOS 15.7 Release Notes
5
Table of Contents
ExtremeXOS Documentation Corrections......................................................... 123
ACLs ................................................................................................................................................................................... 124
Configure Access-List VLAN-ACL-Precedence Command Usage Guidelines .....................................125
Configure IP-MTU VLAN Command Syntax Description ..............................................................................126
Command Reference ...........................................................................................................................................126
User Guide ................................................................................................................................................................126
Debounce Commands .................................................................................................................................................127
Configure stack-ports debounce time ..........................................................................................................127
Description .......................................................................................................................................................127
Syntax Description ........................................................................................................................................127
Default ................................................................................................................................................................127
Usage Guidelines ...........................................................................................................................................127
Example .............................................................................................................................................................127
History: ...............................................................................................................................................................127
Platforms Availability ...................................................................................................................................127
Show stack-ports debounce .............................................................................................................................128
Description .......................................................................................................................................................128
Syntax Description ........................................................................................................................................128
Default ................................................................................................................................................................128
Usage Guidelines ...........................................................................................................................................128
Example .............................................................................................................................................................128
History ................................................................................................................................................................128
Platform Availability .....................................................................................................................................128
Extreme Networks Virtualization (XNV), Identity Management (IDM), and Network Time Protocol
(NTP) ..........................................................................................................................................................................129
MLAG ..................................................................................................................................................................................129
Rate Limiting/Meters .................................................................................................................................................. 130
Remote Mirroring ......................................................................................................................................................... 130
Routing Policies ...............................................................................................................................................................131
Synchronize Command ...............................................................................................................................................132
TACACS Server ..............................................................................................................................................................132
ExtremeXOS 15.7 Release Notes
6
1
Overview
These release notes document ExtremeXOS® 15.7.1 which adds features, adds
supported hardware, and resolves software deficiencies.
This chapter contains the following sections:
•
New and Corrected Features in ExtremeXOS 15.7 on page 7
•
Deprecation of Domain Field from Open Shortest Path First
(OSPF)v3 Commands on page 46
•
ExtremeXOS Images for Summit X480 Series Switches on page 46
•
New Hardware Supported in ExtremeXOS 15.7 on page 47
•
Hardware No Longer Supported on page 47
•
Hardware Issues in ExtremeXOS 15.6 and Later on page 47
•
Joint Interoperability Test Command (JITC) Compliance on page 48
•
ExtremeXOS Hardware/Software Compatibility and
Recommendation Matrices on page 48
•
Compatibility with NetSight on page 48
•
Upgrading to ExtremeXOS on page 49
•
Downloading Supported MIBs on page 49
•
Tested Third-Party Products on page 49
•
Extreme Switch Security Assessment on page 51
•
Service Notifications on page 51
New and Corrected Features in ExtremeXOS 15.7
This section lists the new and corrected features supported in the ExtremeXOS 15.7
software:
•
Bridge and Q-Bridge Management Information Bases (MIBs) on
page 9
•
Open Shortest Path First (OSPF)v2/v3 Import Policy Improvements
on page 10
•
ExtremeXOS Trivial File Transfer Protocol (TFTP) Client MTU/BlockSize Configuration on page 11
•
ExtremeXOS I/O Native Applications Support on page 12
•
ExtremeXOS Web-Based GUI: Chalet on page 13
•
Label-Switched Path (LSP) Fast Failover on page 13
7
Overview
•
Multi-protocol Label Switching (MPLS) Resource Reservation
Protocol - Traffic Engineering (RSVP-TE) Explicit Route Option
(ERO) Exclude Option on page 14
•
Clear Internet Protocol Address Resolution Protocol (IPARP)/Clear
Neighbor-Discovery Refresh on page 17
•
Minimum Number of Link Aggregation Control Protocol (LACP) Link
Aggregate Group (LAG) Members on page 19
•
AAA: Ability to Administer All Default User Accounts on page 21
•
Network Time Protocol (NTP) over Management Port on page 22
•
Dynamic Host Configuration Protocol (DHCPv6) Relay—Install
Routes for Snooped Delegated IPv6 Prefixes on page 23
•
Multicast Listener Discovery (MLD) Source Specific Multicast (SSM)
Mapping on page 24
•
Virtual Machine (VM) Tracking Enhancements for NetSight on
page 25
•
Network Logon Enhancements for NetSight on page 26
•
Configuring Power Budget Capability for Summit X430-8p Switches
on page 27
•
Zero Touch Provisioning on page 28
•
31-Bit Prefixes on IPv4 Interfaces (RFC 3021) on page 29
•
Priority Flow Control (PFC) Statistics per Port on page 30
•
Entity Management Information Base (MIB) Port Support on page 31
•
Spanning Tree Protocol (STP) Enhancements on page 32
•
Private Virtual Local Area Networks (PVLANs) Management
Information Base (MIB) on page 35
•
MAC Address Locking on page 35
•
Open Shortest Path First (OSPF)v3 Point-to-Point Interfaces on
page 37
•
ExtremeXOS Secure Shell/Secure Copy Protocol (SSH/SCP) Client
Upgrade Using OpenSSH on page 38
•
Link Aggregation Group (LAG)—Multiple VLAN Registration Protocol
(MVRP) Enhancements on page 39
•
OpenFlow v1.3 and Pseudowire Multiprotocol Label Switching
(MPLS) on page 43
•
Static Generalized Precision Time Protocol (gPTP) Port Roles on
page 44
•
Protocol Independent Multicast (PIM) Enhancement: Shortest-Path
Tree (SPT) Threshold Option “Infinity” on page 45
ExtremeXOS 15.7 Release Notes
8
Overview
Bridge and Q-Bridge Management Information Bases
(MIBs)
This feature:
•
•
Implements the following objects/tables as defined by RFC 4363:
•
dot1qBase group
•
dot1qPortVlanTable under dot1qVlan group
•
dot1qVlanStaticTable under dot1qVlan group
Adds dot1BasePortTable support into the existing Bridge MIB on ExtremeXOS.
Managed objects for transparent bridging are defined in the Bridge MIB. The
original IEEE 802.1D is augmented by IEEE 802.1Q-2003 to provide support for
virtual bridged LANS where a single bridged physical LAN network can be used to
support multiple logically bridged LANs (VLANs), each of which offers a service
approximately the same as that defined by IEEE 802.1D.
The Q-Bridge MIB, defined in RFC 4363 and now transferred to IEEE8021-QBRIDGE-MIB, provides a standard Simple Network Management Protocol (SNMP)
mechanism to retrieve VLAN specific information.
Supported Platform
•
BlackDiamond X8 and BlackDiamond 8800 series switches
•
Summit X770, X670, X670-G2, X480, X460, X460-G2, X440, and X430 series
switches
•
E4G-200 and E4G-400 cell site routers
Limitations
The groups and tables listed above are implemented as read-only.
ExtremeXOS 15.7 Release Notes
9
Overview
Open Shortest Path First (OSPF)v2/v3 Import Policy
Improvements
This feature allows Import Policy to be used by OSPFv2/v3 to install routes
selectively into the switch routing table.
Previously, routing protocol OSPFv2/v3 applied routing policies with keyword
“import-policy”, which could only be used to change the attributes of routes
installed into the switch routing table. This feature now provides the flexibility of
using import policy to determine the routes to be added to or removed from the
routing table.
To prevent routes from being added to the routing table, the policy file must
contain a matching rule with action “deny”. If there is no matching rule for a
particular route, or the keyword “deny” is missing in the rule, the default action is
“permit”, which means that route is installed into the routing table.
Supported Platform
•
BlackDiamond X8 and BlackDiamond 8800 series switches
•
Summit X770, X670, X670-G2, X480, X460, and X460-G2 series switches
•
E4G-200 and E4G-400 cell site routers
Affected Commands
No commands have been added nor modified. The following existing commands
apply import policy in OSPFv2/v3:
configure ospf import-policy [<policy-name> | none]
configure ospfv3 import-policy [<policy-name> | none]
ExtremeXOS 15.7 Release Notes
10
Overview
ExtremeXOS Trivial File Transfer Protocol (TFTP) Client
MTU/Block-Size Configuration
This feature adds support in ExtremeXOS commands for a configurable block-size
option when transferring files using Trivial File Transfer Protocol (TFTP).
TFTP is a simple, lock-step, file transfer protocol that allows a client to get or put a
file onto a remote host. TFTP is very simple to implement in a small node's limited
ROM space. However, use of a 512-octet block-size is not efficient on LANs with a
maximum transition unit (MTU) that may be 1,500 octets or greater.
This TFTP feature allows the client to negotiate with the server for a block-size
more applicable to the network medium. This helps support TFTP over smallersized MTU WAN links and to take advantage of larger LAN MTUs, such as jumbo
frames.
Supported Platform
•
BlackDiamond X8 and BlackDiamond 8800 series switches
•
Summit X770, X670, X670-G2, X480, X460, X460-G2, X440, and X430 series
switches
•
E4G-200 and E4G-400 cell site routers
Changed CLI Commands
The following commands have a configurable block-size option added (shown in
bold). If you do not specify a block-size, it defaults to 1,400 bytes.
tftp [<ip-address> | <host-name>] {-v <vr_name>} {-b
<block_size>} [-g | -p] [ {-l [ memorycard <local-filememcard> | internal-memory <local-file-internal> | <local-file>
] } {-r <remote-file> } | {-r <remote-file> } {-l [ memorycard
<local-file-memcard> | internal-memory <local-file-internal> |
<local-file> ] } ]
tftp get [<ip-address> | <host-name>] {vr <vr_name>} {blocksize <block_size>} <remote-file> { memory-card {<local-filememcard>} | internal-memory {<local-file-internal>} | <localfile> } {force-overwrite}
tftp put [<ip-address> | <host-name>] {vr <vr_name>} {blocksize <block_size>} [ memory-card <local-file-memcard> |
internal-memory <local-file-internal> | <local-file> ] {<remotefile>}
ExtremeXOS 15.7 Release Notes
11
Overview
upload configuration [<ipaddress> | <hostname>] <filename> {
{vr} <vr-name> } {block-size <block_size>}
upload log <ipaddress> {vr <vr_name>} {block-size
<block_size>} <filename> {messages [memory-buffer | nvram]}
{severity <severity> {only}} {chronological} {match <regex>}
upload debug [<ipaddress> | <hostname>] {{vr} <vrname>} {block-
size <block_size>}
download image [[<hostname> | <ipaddress>] <filename> {{vr}
<vrname>} {block-size <block_size>} | memorycard <filename>]
{<partition>} {msm <slotid> | mm <slotid> | slot <slot-number>}
download bootrom [<hostname> | <ipaddress>] <filename> {{vr}
<vrname>} {block-size <block_size>} {msm <slotid> | mm
<slotid> | slot <slot-number>}
ExtremeXOS I/O Native Applications Support
This feature provides means to extend the native capabilities of ExtremeXOS
through Python processes, and includes:
•
Python Software Developers Kit (SDK), which includes EXPY, an ExtremeXOSenabled Python container.
•
Python bindings to ExtremeXOS libraries, for use by EXPY and any other
python-enabled process.
Supported Platforms
•
BlackDiamond X8 and BlackDiamond 8800 series switches
•
Summit X770, X670, X670-G2, X480, X460, X460-G2, X440, and X430 series
switches
•
E4G-200 and E4G-400 cell site routers
New CLI Commands
create process <name> python-module <python-module> {start
[auto | on-demand]} {vr <vr-name>} {description
ExtremeXOS 15.7 Release Notes
12
Overview
<description>} {<arg1> {<arg2> {<arg3> {<arg4> {<arg5>
{<arg6> {<arg7> {<arg8> {<arg9>}}}}}}}}}
delete process <name>
show process
ExtremeXOS Web-Based GUI: Chalet
Chalet is a web-based user interface for setting up and viewing information about a
switch. Chalet removes the need to know and remember commands in a command
line environment. Viewable on desktop and mobile with a quick logon and intuitive
navigation, Chalet features a quick setup mode for configuring switches quickly.
Basic data surrounding port utilization, power, and Quality of Service (QoS) are
available, and more advanced users can configure multiple VLANs, create Access
Control Lists (ACLs), and configure Audio Video Bridging (AVB). Chalet is
packaged with the ExtremeXOS 15.7.1 image for all platforms.
Supported Platforms
•
BlackDiamond X8 and BlackDiamond 8800 series switches
•
Summit X770, X670, X670-G2, X480, X460, X460-G2, X440, and X430 series
switches
•
E4G-200 and E4G-400 cell site routers
Label-Switched Path (LSP) Fast Failover
ExtremeXOS Multiprotocol Label Switching (MPLS) provides support for Redundant
Resource Reservation Protocol - Traffic Engineering (RSVP-TE) label-switched
paths (LSPs), which allows the configuration of a primary and up to two secondary
paths for a particular LSP. To reduce the traffic loss over a Redundant RSVP-TE
LSP when switching to a different path, ExtremeXOS MPLS now allows the path to
be switched without dataplane updates to any routes or pseudowires that are using
the LSP. This enhancement significantly reduces the number of dataplane changes
and results in reduced traffic loss during the switch. Primary LSP paths using fastreroute (FRR) detour LSPs also benefit from this enhancement when the point of
local repair (PLR) is at the ingress node.
Supported Platforms
•
BlackDiamond X8 and BlackDiamond 8800 series switches
•
Summit X770, X670, X670-G2, X480, X460, and X460-G2 series switches
•
E4G-200 and E4G-400 cell site routers
ExtremeXOS 15.7 Release Notes
13
Overview
Limitations
•
Failover times are always affected by failure detection times.
•
Only redundant RSVP-TE LSPs (including primary FRR LSPs) benefit from this
feature.
•
Circuit Emulation Services (CES) Pseudowires (PWs) do not benefit from this
feature.
Changed CLI Commands
Debug commands, such as debug mpls show lspdb now display the new
abstracted tunnel index, and debug mpls show tech nhlfe-index displays
the nhlfe-index usage.
Multi-protocol Label Switching (MPLS) Resource
Reservation Protocol - Traffic Engineering (RSVP-TE)
Explicit Route Option (ERO) Exclude Option
This feature allow the path for a Resource Reservation Protocol - Traffic
Engineering (RSVP-TE) Label-Switched Path (LSP) to be calculated to avoid certain
hops.
With traffic engineering RSVP-TE LSPs, it is often advantageous to prevent the
primary and secondary paths of a Redundant RSVP-TE LSP from overlapping
because if the paths overlap, the LSP may not be protected, since if that section of
the path becomes non-functional, both paths will go down. The
mplsTunnelHopTable defined in RFC 3812 allows a hop to be defined as “include” or
“exclude”. ExtremeXOS previously only supported “include”, meaning that the
defined hop had to be included in the path calculation. This feature adds support
for “exclude”, which allows you to define a hop that must be avoided in the path
calculation.
Supported Platforms
•
BlackDiamond X8 and BlackDiamond 8800 series switches
•
Summit X770, X670, X670-G2, X480, X460, and X460-G2 series switches
•
E4G-200 and E4G-400 cell site routers
ExtremeXOS 15.7 Release Notes
14
Overview
Changed CLI Commands
configure mpls rsvp-te path <path_name> add ero {{include}
<ipNetmask> [strict | loose] | exclude <ipNetmask>} {order
<number>}
The following show commands now show “exclude” option path information
(shown in bold):
show mpls rsvp-te path
(pacman debug) J1.15 # show mpls rs path
Path Name #LSP #ERO Ord# ERO IP Netmask Type Inc/Exc
-------------------------------------------------------path1
1
1
100 9.50.1.2/32 strict include
path2
1
1
100 9.50.1.2/32 n/a
exclude
show mpls rsvp-te path detail
(pacman debug) J1.16 # show mpls rs path det
Path Name : path1
Hop List Index
: 1
Path Option Index: 1
#ERO/Hops
: 1
#LSP References : 1
ERO
: Order# IpAddress/Mask Type Inc/Exc
--------------------------------------: 100
9.50.1.2/32 strict include
Path Name : path2
Hop List Index : 2
Path Option Index : 1
#ERO/Hops : 1
#LSP References : 1
ERO
ExtremeXOS 15.7 Release Notes
: Order# IpAddress/Mask Type Inc/Exc
15
Overview
: 100
9.50.1.2/32
n/a exclude
show mpls rsvp-te lsp detail
(pacman debug) J1.17 # show mpls rs lsp det
Ingress LSP Name: lsp_to_baha
Destination
: 11.100.100.4 Admin Status : Enabled
IP Traffic
: Allow #VPLS Cfgd
VPN Traffic
: Allow #VPLS In-Use : 0
ExtremeXOS 15.7 Release Notes
: 0
16
Overview
Path Name: path1
Oper Status : Enabled UpTime : 0d:0h:4m:49s
Profile Name : default
Peak Rate : 0 Kbps Max Burst Size : 0 Kb
Committed Rate : 0 Kbps Setup/Hold Priority: 7/0
Record Route : Enabled
MTU : Use Local I/F
Tunnel ID : 1 Ext Tunnel ID : 11.100.100.1
LSP ID : 0 State Changes : 1
LSP Type : Primary Bandwidth Cfgd : False
Activity : Active
Failures : 0 Retries-since last failure : 0
Retries-Total : 0
Configured ERO: Order IP Address/Mask Type Inc/Exc
100 9.50.1.2/32
strict include
Advertised Label: n/a Received Label : 0x00434
Rx Packets : n/a Tx Packets : -Rx Bytes : n/a Tx Bytes : -Next Hop I/F : 9.50.1.1 - j1-j2vlan1
Next Hop Addr : 9.50.1.2
Record Route : Indx
IP Address Label
:
1
9.50.1.2
0x00434
:
2
9.54.1.4
0x00434
Clear Internet Protocol Address Resolution Protocol
(IPARP)/Clear Neighbor-Discovery Refresh
This feature enhances the clear iparp and clear neighbor-discovery
commands by adding an ability to clear only inactive neighbor entries. When
refresh keyword is specified, clear iparp refresh and clear neighbordiscovery refresh solicit all neighbor entries, delete all non-responding/
ExtremeXOS 15.7 Release Notes
17
Overview
inactive entries and keep all active entries, without impacting IPv4/IPv6 traffic for
active entries.
Supported Platforms
•
BlackDiamond X8 and BlackDiamond 8800 series switches
•
Summit X770, X670, X670-G2, X480, X460, X460-G2, X440, and X430 series
switches
•
E4G-200 and E4G-400 cell site routers
ExtremeXOS 15.7 Release Notes
18
Overview
Changed CLI Commands
Changes are shown in bold:
clear iparp {<ip_addr> {{vr} <vr_name>} | {vlan}
<vlan_name> | {vr} <vr_name>} {refresh}
clear neighbor-discovery {cache {ipv6}} { <ipv6_addr>
{{vr} <vr_name>} | {vlan} <vlan_name> | {vr} <vr_name> }
{refresh}
Show Iparp and Show Neighbor-Discovery Output
When clear iparp refresh or clear neighbor-discovery refresh
is executed, the switch sends out ARP request/neighbor solicit for every suitable
entry and marks each entry with indicating that ARP response or neighbor
advertisement has not been received from the neighbor. After an ARP response or
neighbor advertisement is received from the neighbor, the asterisk (*) is cleared
from the entry.
Minimum Number of Link Aggregation Control Protocol
(LACP) Link Aggregate Group (LAG) Members
The LAG minimum links feature allows you to configure a value for the minimum
number of active links to keep the entire LAG up.
For example, for a LAG consisting of four ports and the minimum links set to two,
at least two links must be up for the LAG to be up. When the LAG falls below two
active links, the entire LAG is brought down, and all applications using this LAG are
informed that the LAG is down. Previously, the implicit minimum link value was one,
meaning that if there was at least one link up, the entire LAG stayed up.
For static LAGs, the number of active physical member port links is checked to see
if it is greater than or equal to the user-configured minimum link value. If so, the
LAG remains up. If this test fails, the static LAG is brought down and all applications
receive a Link-Down message for this LAG. As soon as the number of active
physical member ports equals or exceeds the configured minimum link value, the
static LAG is brought up and all applications receive a Link-Up message for this
LAG.
ExtremeXOS 15.7 Release Notes
19
Overview
In the case of LACP, how many member ports LACP has requested to be added to
the LAG is tracked. After successfully negotiating with its peer, LACP sends a
request to add a member port to the LAG. When the number of member ports
LACP has requested to be added to the LAG drops below the configured minimum
link value, the LACP LAG is be brought down and all applications receive a LinkDown message for this LAG. As soon LACP has added enough member ports so
that the total equals or exceeds the configured minimum link value, the LAG is
brought up and all applications receive a Link-Up message for this LAG.
Both static and LACP LAGs can be used with Multiple Link Aggregation Group
(MLAG) on either the ISC or the MLAG ports.
Supported Platforms
•
BlackDiamond X8 and BlackDiamond 8800 series switches
•
Summit X770, X670, X670-G2, X480, X460, X460-G2, X440, and X430 series
switches
•
E4G-200 and E4G-400 cell site routers
New CLI Commands
configure sharing <port> minimum-active <min_links_active>
Changed CLI Commands
The following show commands now display the configured minimum link value:
show port <port> sharing
show lacp lag <port> detail
ExtremeXOS 15.7 Release Notes
20
Overview
AAA: Ability to Administer All Default User Accounts
Accounts can be disabled or enabled locally using read/write access. Even all
administrative privileged accounts and user privileged accounts can be disabled.
Lawful-Intercept accounts are disabled under user privileged option.
This enable/disable command affects the following North Bound Interfaces (NBIs)
in management access realm:
•
Console
•
Telnet
•
SSH
•
HTTP
•
XML
Supported Platforms
•
BlackDiamond X8 and BlackDiamond 8800 series switches
•
Summit X770, X670, X670-G2, X480, X460, X460-G2, X440, and X430 series
switches
•
E4G-200 and E4G-400 cell site routers
New CLI Commands
enable account [all {admin | user} | <name>]
disable account [all {admin | user} | <name>]
ExtremeXOS 15.7 Release Notes
21
Overview
Network Time Protocol (NTP) over Management Port
Network Time Protocol (NTP) is a protocol for synchronizing clocks of servers or
network entities using TCP/IP-based networks which have a coherent variable
latency. It is designed particularly to resist the effects of variable latency by using a
jitter buffer. NTP provides Coordinated Universal Time Clock (UTC). However, no
information about time zones or daylight saving time is transmitted. NTP uses a
hierarchical, semi-layered system of levels of clock sources. Each level of this
hierarchy is termed a stratum and is assigned a layer number starting with 0 (zero)
at the top. The stratum level defines its distance from the reference clock and exists
to prevent cyclical dependencies in the hierarchy.
This feature adds configuring NTP on any one virtual router at a time. By default
NTP is configured on VR-Default, which can be changed to other virtual routers.
Supported Platforms
•
BlackDiamond X8 and BlackDiamond 8800 series switches
•
Summit X770, X670, X670-G2, X480, X460, X460-G2, and X440 series switches
•
E4G-200 and E4G-400 cell site routers
New CLI Commands
configure ntp vr <vr-name>
Limitations
NTP must be disabled globally before changing the virtual router for NTP, and
should be enabled again afterwards. All present NTP VLAN configurations are
deleted when changing the virtual router.
Changed CLI Commands
The output of the show ntp command now shows which virtual router NTP has
been configured on (shown in bold):
XNTP
: Enabled
Authentication
: Disabled
Broadcast-Client
: Disabled
VR configured
: <vr-name>
ExtremeXOS 15.7 Release Notes
22
Overview
Dynamic Host Configuration Protocol (DHCPv6) Relay—
Install Routes for Snooped Delegated IPv6 Prefixes
This feature provides a way for the ExtremeXOS DHCPv6 Relay Agent to install
routes for ensuring reachability to DHCPv6 clients that get their IP addresses from
customer edge switches which distribute a delegated IPv6 prefix to the clients.
Supported Platforms
•
BlackDiamond X8 and BlackDiamond 8800 series switches
•
Summit X770, X670, X670-G2, X480, X460, X460-G2, X440, and X430 series
switches
•
E4G-200 and E4G-400 cell site routers
Limitations
This feature enhances the behavior of the Relay Agent, which resides between a
delegating router and a requesting router, in adding routing information for the
snooped delegated prefixes. It does not provide the capability to be a delegating
router, which can delegate prefixes, nor a requesting router, which can allocate IPv6
addresses after receiving a delegated prefix.
New CLI Commands
configure bootprelay ipv6 prefix-delegation snooping [on
{vlan} <vlan_name> | off [{vlan} <vlan_name> | vlan all]]
clear bootprelay ipv6 prefix-delegation snooping [{ipv6prefix} <ipv6_prefix> | ipv6-prefix all] [{vlan}
<vlan_name> | vlan all]
configure bootprelay ipv6 prefix-delegation snooping add
<ipv6_prefix> <ipv6Gateway> {vlan} <vlan_name> valid-time
<valid_time>
show bootprelay ipv6 prefix-delegation snooping {{vlan}
<vlan_name>}
ExtremeXOS 15.7 Release Notes
23
Overview
Multicast Listener Discovery (MLD) Source Specific
Multicast (SSM) Mapping
This feature enables MLDv1 hosts to participate in Source Specific Multicast (SSM).
The Multicast Listener Discovery (MLD) Source Specific Multicast (SSM) Mapping
feature is an IPv6 equivalent of the IPv4 feature, Internet Group Management
Protocol (IGMP) SSM Mapping. The MLD SSM Mapping feature allows you to
configure mapping entries, thereby enabling MLDv1 hosts to participate in SSM
functionality by sending MLDv1 reports. You can configure the sources and group/
group ranges for which SSM functionality has to be applied. You can also configure
Domain Name System (DNS) names for a group/group range.
Supported Platforms
•
BlackDiamond X8 and BlackDiamond 8800 series switches
•
Summit X770, X670, X670-G2, X480, X460, X460-G2, and X440 series switches
•
E4G-200 and E4G-400 cell site routers
Limitations
•
Only 50 sources (static or dynamic) are allowed for each group address/group
range. The DNS server may send only 15 IPv6 source addresses in its response,
thereby limiting the number of dynamic sources supported.
•
Only one DNS name is allowed for each group address/group range.
New CLI Commands
[enable | disable] mld ssm-map {{vr} <vrname>}
configure mld ssm-map add <v6groupnetmask> [<v6sourceip> |
<src_domain_name>] {{vr} <vrname>}
configure mld ssm-map delete <v6groupnetmask> [<v6sourceip>
| <src_domain_name> | all] {{vr} <vrname>}
unconfigure mld ssm-map {{vr} <vrname>}
show mld ssm-map {<v6groupnetmask>} {{vr} <vrname>}
refresh mld ssm-map <v6groupnetmask> {{vr} <vrname>}
Changed CLI Commands
Changes are in bold.
ExtremeXOS 15.7 Release Notes
24
Overview
For the refresh igmp command “dns group” is now optional:
refresh igmp ssm-map {dns group} [<grpipaddress> <netmask>
| <ipNetmask>] {{vr} <vrname>}
Virtual Machine (VM) Tracking Enhancements for
NetSight
Previously, when XNV is enabled on Multiple Link Aggregation Group (MLAG)enabled ports, both MLAG peers authenticate the VM independently. Now, to
integrate with NetSight and Network Access Control (NAC), provided MLAG peers
have ISC connectivity, only one MLAG peer authenticates a VM that is learned on
an MLAG port.
When ISC connectivity between MLAG peers is established, the peer with the
highest IP address is chosen to be the authenticator. This peer Authenticates a
virtual machine (VM) based on the chosen authentication method. The result of the
authentication is checkpointed by the authenticator to its peer so that the same
virtual port profile (VPP) gets applied to the VM on both peers.
When the MLAG peer that is the authenticator goes down, the other peer detects
that the authenticator is down and re-authenticates the VM at the next
authentication interval. The peer that takes over as the authenticator does not reauthenticate the VMs immediately, but waits for the re-authentication timer to
expire.
VMs learned on non-MLAG ports are authenticated by the detecting peer.
Supported Platforms
•
BlackDiamond X8 and BlackDiamond 8800 series switches
•
Summit X770, X670, X670-G2, X480, X460, X460-G2, and X440 series switches
•
E4G-200 and E4G-400 cell site routers
ExtremeXOS 15.7 Release Notes
25
Overview
Network Logon Enhancements for NetSight
Network logon (Netlogon) controls the admission of user packets into a network by
allowing MAC addresses from users that are properly authenticated. Netlogon is
controlled on a per-port basis. When Netlogon is enabled on a port, that port does
not forward any packets until authentication occurs. Netlogon is capable of three
types of authentication: Web-based, MAC-based, and 802.1X.
This feature add support for multiple authentication protocols on a netlogonenabled port. You must specify the authentication protocol priority or order per
port, which dictates the action for the client or supplicant that is getting
authenticated on this port. You can use the command line to configure the
authentication protocol order. By default the protocol precedence order for a
netlogon enabled port is:
1 Dot1x
2 MAC
3 Web-based
Supported Platforms
•
BlackDiamond X8 and BlackDiamond 8800 series switches
•
Summit X770, X670, X670-G2, X480, X460, X460-G2, X440, and X430 series
switches
•
E4G-200 and E4G-400 cell site routers
ExtremeXOS 15.7 Release Notes
26
Overview
Configuring Power Budget Capability for Summit X4308p Switches
You can now configure the budgeted Power over Ethernet (PoE) power reserved
for all power devices for Summit X430-8p switches from 60–90 W.
The default power budget is 60 W. If you set the reserved budget to greater than
the default value, a warning message notifies you that you can exceed the default
budget only on a standalone desktop configuration.
If the power consumed by devices on the switch exceeds the configured budget,
new ports requiring power are either denied or other lower priority ports are
disconnected.
CLI Commands
configure inline-power budget <num_watts> [slot <slot> |
NULL]
unconfigure inline-power budget [slot <slot> | NULL]
show inline-power
ExtremeXOS 15.7 Release Notes
27
Overview
Zero Touch Provisioning
The Zero Touch Provisioning feature enables switches “out of the box” to
automatically gain a management IP address and configuration without serial
cables and manual configuration:
•
Management port address: Configures an IPv4 Link-Local IP management port
address allowing for easier access to the switch by connecting with a Web
browser to http://0xa9fe<last 2 MAC chars>, where <last 2 MAC
chars> is the last two alphanumeric groups in the MAC address found on the
switch label.
For example:
For MAC address: 00:04:96:97:E9:EE
Use http://0xa9fee9ee (or just 0xa9fee9ee)
•
Receives and Option 43 or Option 125 messages (if both Option 43 and 125
messages are in the DHCP reply, Option 125 is implemented):
•
Option 43 for ExtremeXOS image updates; configuration, policy, and script
files
•
Option 125 for NetSight trap address
The Zero Touch Provisioning feature starts automatically when booting up a switch,
unless one the following conditions is true:
•
Configuration file is present.
•
Management IP address is present.
•
License has been configured.
•
You enter disable auto-provisioning command.
•
debug mode is enabled.
Supported Platforms
•
BlackDiamond X8 and BlackDiamond 8800 series switches
•
Summit X770, X670, X670-G2, X480, X460, X460-G2, X440, and X430 series
switches
•
E4G-200 and E4G-400 cell site routers
New CLI Commands
disable auto-provision
show auto-provision {{vr} <vr_name>}
ExtremeXOS 15.7 Release Notes
28
Overview
31-Bit Prefixes on IPv4 Interfaces (RFC 3021)
You can now configure IPv4 addresses with 31-bit prefixes on both network VLANs
and the Management VLAN. Applications (for example, Ping) and protocols (for
example, OSPF) can use the IPv4 interfaces configured with these 31-bit prefixes.
After the introduction of Classless Inter-Domain Routing (CIDR), the 32-bit IPv4
address has been partitioned into two parts that go by various names but can be
called the prefix and the host-number:
IP-address = <Prefix> <Host-number>
Two host number values are traditionally reserved:
•
All ones: This value indicates a directed broadcast on the network indicated by
the prefix.
•
All zeroes: With the original “classed” definition of IPv4 addresses, the address
value indicated the length of the prefix, so a prefix (to be used as a route key,
for example) could be determined from just an IPv4 address. To distinguish IPv4
addresses that specified prefixes from those that specified hosts, the hostnumber value of all-zeroes was reserved for IPv4 addresses that specified
prefixes.
RFC 3021 defines the practice of not reserving the all-ones and all-zeros host
number values on networks with 31-bit prefixes.
There is no new commands for this feature. The only changes are values allowed in
the commands.
For example:
configure {vlan} <vlan_name> ipaddress [ <ipaddress>
{<netmask>} | <ipNetmask>]
255.255.255.254 is allowed for <netmask>
/31 is allowed in <ipNetmask> (for example, 192.168.0.1/31)
ExtremeXOS 15.7 Release Notes
29
Overview
Supported Platforms
•
BlackDiamond X8 and BlackDiamond 8800 series switches
•
Summit X770, X670, X670-G2, X480, X460, X460-G2, X440, and X430 series
switches
•
E4G-200 and E4G-400 cell site routers
Limitations
Directed broadcasts cannot be sent from other networks to a network using a 31-bit
prefix.
Priority Flow Control (PFC) Statistics per Port
This feature introduces a new command that displays the number of priority flow
control (PFC) pause control frames sent and received on a specific port.
Supported Platforms
The following platforms support the PFC feature in the new command:
•
•
BlackDiamond 8800 switches with 8900-MSM128 and the following switch
modules:
•
BlackDiamond 8900-10G24X-c modules (manufacturing number 800397-00)
•
BlackDiamond 8900-40G6X-xm modules, 40G ports and 10G ports when in
4x10 partition mode
The following Summit series switches:
•
Summit X460 switches, 10G ports
•
Summit X460G2 switches, 1G and 10G ports
•
Summit X670 switches, 1G and 10G ports
•
Summit X670V switches, 1G, 10G, and 40G ports
•
Summit X670-G2 switches, 1G, 10G, and 40G ports
•
Summit X770-32q, 10G and 40G ports
New CLI Commands
show port {port_list} flow-control {rx-pauses} {tx-pauses}
{no-refresh}
ExtremeXOS 15.7 Release Notes
30
Overview
Entity Management Information Base (MIB) Port Support
The Entity management information base (MIB) provides a standard Simple
Network Management Protocol (SNMP) mechanism to retrieve device-specific
information. It provides a standard mechanism to indicate device hierarchy using
SNMP, to determine what physical entities are managed by the agent, and thereby
to be able to communicate with the agent about a particular physical entity and
understand its hierarchical position in the chassis.
ExtremeXOS 15.7 adds the following:
•
Supports entPhysicalMfgDate, entPhysicalUris, and entPhysicalUUID.
Previously, the Entity MIB in ExtremeXOS was implemented based on RFC 2737.
The enhancement to the latest version 4 as defined by RFC 6933 adds the
following three additional MIB objects for each physical entity:
entPhysicalMfgDate, which contains the manufacturing date of the managed
entity; entPhysicalUris, which provides additional identification information
about the physical entity; and entPhysicalUUID, which provides a unique
identification about the physical entity.
•
Implements entAliasMappingTable and entPhysicalContainsTable.
The enhancement to the latest version of the MIB adds three additional groups.
Previously, of the various groups defined by the RFC for the Entity MIB,
ExtremeXOS only implemented the entityPhysical group The other groups
defined in the RFC are entityLogical group, entityMapping group, entityGeneral
group, and entitiyNotification group. The group entityLogical describes the
logical entities managed by a single agent. In ExtremeXOS, an agent represents
a single logical entity; therefore, this table has not been implemented. The
group entityMapping contains three tables. The entLPMappingTable table, which
contains mappings between logical entities and the physical components
supporting that entity, is not implemented since ExtremeXOS only supports one
logical entity. The tables entAliasMappingTable and entPhysicalContainsTable
are implemented for ExtremeXOS 15.7.
•
Implements physical port support for the entityPhysical group
Physical ports are currently not supported in entityPhysical Group. They will be
added into entityPhysical Group, grouped by slot as appropriate using
relationships specified in entPhysicalContainedIn.
ExtremeXOS 15.7 Release Notes
31
Overview
Supported Platforms
•
BlackDiamond X8 and BlackDiamond 8800 series switches
•
Summit X770, X670, X670-G2, X480, X460, X460-G2, X440, and X430 series
switches
•
E4G-200 and E4G-400 cell site routers
Limitations
entPhysicalUris and entPhysicalAssetID are implement as read-only objects.
Spanning Tree Protocol (STP) Enhancements
This enhancement to the ExtremeXOS Spanning Tree Protocol (STP)
implementation provides:
•
Loop protect
STP requires switches to send Bridge Protocol Data Units (BPDUs) bidirectionally and build the topology database. If a port only allows traffic oneway (Uni-directional link failure), and the switch still sees that port as up, a loop
can form without the switch detecting it. This loop protect feature avoids loops
by checking if a BPDU timeout occurs on a port, and then changes the state to
“discarding” until a BPDU is received.
•
Backup root bridge
The backup root bridge becomes the root bridge when the primary root bridge
is unavailable due to failure, malfunction, or administrative errors.
•
Multisource detection
Multisource detection is a feature that prevents network disruption due to
excessive topology changes caused by a full duplex port transmitting multiple
BPDUs with different source MAC addresses, and hence different BPDU
information.
Supported Platforms
•
BlackDiamond X8 and BlackDiamond 8800 series switches
•
Summit X770, X670, X670-G2, X480, X460, X460-G2, X440, and X430 series
switches
•
E4G-200 and E4G-400 cell site routers
ExtremeXOS 15.7 Release Notes
32
Overview
New CLI Commands
clear {stpd} <stpd_name> ports <port_list> protocolmigration
configure {stpd} <stpd_name> backup-root [on | off]
configure {stpd} <stpd_name> ports auto-edge [on | off]
<port_list>
configure {stpd} <stpd_name> ports loop-protect [on | off]
<port_list>
configure {stpd} <stpd_name> ports loop-protect partner
[capable | incapable] <port_list>
configure {stpd} <stpd_name> tx-hold-count <tx_hold_count>
configure {stpd} <stpd_name> ports restricted-tcn [on |
off] <port_list>
configure {stpd} <stpd_name> trap backup-root [on | off]
configure {stpd} <stpd_name> trap new-root [on | off]
configure {stpd} <stpd_name> trap bpdu-restrict [on | off]
configure {stpd} <stpd_name> trap loop-protect [on | off]
configure {stpd} <stpd_name> trap topology-change {edgeports} [on | off]
configure {stpd} <stpd_name> dispute-threshold [<threshold>
| none] <port_list>
configure {stpd} <stpd_name> loop-protect event-window
<interval_time>
configure stpd filter-method [system-wide| port-based]
ExtremeXOS 15.7 Release Notes
33
Overview
Changed CLI Commands
The following commands are modified to show various aspects of this feature.
show stp port
Modified to show loop protect, partner capabilities, restricted TCN status, operator
edge, and auto edge status.
show stp
Modified to show all trap status, loop protect threshold value, and loop protect
event window values.
show stp detail
Modified to show all trap status loop protect, threshold value, and loop protect
event window values.
show stp ports non forwarding reason
Modified to show the non-forwarding reason on ports.
show stp ports blocked ports
Modified to show all blocked ports in spanning tree.
show stp ports counters
Modified to show all counters for spanning tree.
show MSTP digest value
Modified to shows MSTP digest value.
configure stpd filter-method [system-wide| port-based]
show stpd
Modified to show STP filter method.
ExtremeXOS 15.7 Release Notes
34
Overview
Private Virtual Local Area Networks (PVLANs)
Management Information Base (MIB)
ExtremeXOS 15.7 now has the following MIB tables:
•
PVLAN Table supporting GET/SET.
•
PVLAN Member VLAN Table supporting GET/SET
and the following changes to existing MIB tables:
•
Modifications to extremeVlanOpaqueControlTable for adding translated ports.
•
Modifications to extremeVlanOpaqueTable to display translated VLAN ports.
Supported Platforms
•
BlackDiamond X8 and BlackDiamond 8800 series switches
•
Summit X770, X670, X670-G2, X480, X460, X460-G2, X440, and X430 series
switches
•
E4G-200 and E4G-400 cell site routers
MAC Address Locking
This feature introduces the ability to limit access to a port to specified MAC
addresses or a maximum number of MAC addresses on a first-come first-served
basis. MAC address locking locks a port to one or more MAC addresses, preventing
connection of unauthorized devices via a port. With MAC locking enabled, the only
frames forwarded on a MAC address locked port are those with the configured or
dynamically selected MAC addresses for that port.
Supported Platforms
•
BlackDiamond X8 and BlackDiamond 8800 series switches
•
Summit X770, X670, X670-G2, X480, X460, X460-G2, X440, and X430 series
switches
•
E4G-200 and E4G-400 cell site routers
ExtremeXOS 15.7 Release Notes
35
Overview
Limitations
•
MAC address locking cannot be enabled along with existing limit learning and
lock learning features.
•
MAC address locking is not be supported on ports in the VPLS service VLAN.
New CLI Commands
enable mac-locking
disable mac-locking
enable mac-locking [port_list | all]
disable mac-locking [port_list | all]
configure mac-locking ports <port_list> learn-limit-action
[disable-port | remain-enabled]
configure mac-locking ports <port_list> first-arrival
limit-learning <learn_limit>
configure mac-locking ports <port_list> static limitlearning <learn_limit>
configure mac-locking ports <port_list> static [add |
enable | disable] station <station_mac_address>
configure mac-locking ports <port_list> static delete
station [<station_mac_address> | all]
configure mac-locking ports <port_list> first-arrival aging
[enable | disable]
configure mac-locking ports <port_list> first-arrival moveto-static
configure mac-locking ports <port_list> first-arrival linkdown-action [clear-macs | retain-macs]
configure mac-locking ports <port_list> trap {violation |
threshold} [on | off]
configure mac-locking ports <port_list> log {violation |
threshold} [on | off]
ExtremeXOS 15.7 Release Notes
36
Overview
clear mac-locking station [all | {mac
<station_mac_address>} {first-arrival | static} {ports
<port_list>}]
clear mac-locking disabled-state ports <port_list>
show mac-locking {ports <port_list>}
show mac-locking stations {first-arrival | static} {ports
<port_list>}
Open Shortest Path First (OSPF)v3 Point-to-Point
Interfaces
This feature for OSPFv3 is similar to OSPFv2 point-to-point interfaces, which is
already supported in ExtremeXOS. Point-to-point interfaces skip designated router/
backup designated router (DR/BDR) election and reach operational state faster.
The links on these interfaces do not require network link-state advertisement
(LSAs) and the type of intra-area prefix LSAs generated by DRs. Network
topologies that can use links with only one neighbor can take advantage of the
speed and efficiency of point-to-point interfaces.
Supported Platforms
•
BlackDiamond X8 and BlackDiamond 8800 series switches
•
Summit X770, X670, X670-G2, X480, X460, and X460-G2 series switches
•
E4G-200 and E4G-400 cell site routers
ExtremeXOS 15.7 Release Notes
37
Overview
CLI Commands
The command to configure OSPFv3 point-to-point interfaces was available in
ExtremeXOS, but support was missing:
configure ospfv3 {domain <domainName>} add [{vlan} <vlan-name> |
{tunnel} <tunnel-name>] {instance-id <instanceId>} area <areaidentifier> {link-type [auto | broadcast | point-to-point]}
{passive}
There are no changes to the command, but support is added to configure the linktype for an interface and the warning message that previously appeared when linktype was specified is removed:
Warning! Link type configuration is not supported
Link type will always be automatically determined
ExtremeXOS Secure Shell/Secure Copy Protocol (SSH/
SCP) Client Upgrade Using OpenSSH
This feature upgrades SSH client/SCP client behavior using OpenSSH from
openssh-3.9p1 to openssh-6.5p1.
Only SSH version 2 is supported.
SCP file transfers to the switch include the following file types: configuration (cfg),
script (xsf and py), policy (pol), SSH key (ssh).
SCP file transfers from the switch include the following file types: configuration
(cfg), script (xsf and py), policy (pol), and SSH key (ssh).
Supported Platforms
•
BlackDiamond X8 and BlackDiamond 8800 series switches
•
Summit X770, X670, X670-G2, X480, X460, X460-G2, and X440, and X430
series switches
•
E4G-200 and E4G-400 cell site routers
ExtremeXOS 15.7 Release Notes
38
Overview
Limitations
•
Only password-based authentication is supported for SSH/SCP client.
•
SCP client does not support upload of image or BootROM files (for example:
xos, xmod, and xtr).
•
SCP client does not support download of image or BootROM files (for example:
xos, xmod, and xtr) from EXOS SCP server.
•
Only supports transfer of files such as cfg, xsf, py, pol, and ssh files to/from the
switch.
•
Current version of openssl is not Federal Information Processing Standards
(FIPS) compliant.
Changed CLI Commands
The following commands are changed for this feature. Removed items are struck
through and added items are in bold.
ssh2 {cipher [3des | blowfish] <cipher>} {mac <mac>}
{compression [on | off]} {port <port>} {user <username>} {vr
<vr_name>} <user@host> {<remote_command>}
cp2 {cipher [3des | blowfish] <cipher>} {mac <mac>}
{compression [on | off]} {port <port>} {vr <vr_name>} [
<user@host:file> <local-file> | <local-file> <user@host:file> ]
Link Aggregation Group (LAG)—Multiple VLAN
Registration Protocol (MVRP) Enhancements
Link aggregation allows an increased bandwidth and resilience by using a group of
ports to carry traffic in parallel between switches. Multiple ports can be aggregated
into one logical port. MVRP can be enabled on the logical port. The MVRP control
packets are transmitted on any available physical port of the LAG. The peer on the
other side receives the packet and processes it as if it is received on the logical
port. MVRP supports both dynamic (LACP) as well as static load sharing. MVRP
data structure is based on port Instance. All dynamic VLANs created or propagated
for a given port are stored for each port Instance. For normal ports, the port
Instance corresponds to the PIF port instance, and for LAG ports, the port Instance
corresponds to the LIF port Instance. The port instance is not shown in any of the
standard show commands, though it is available as a part of the debug commands.
Once MVRP is enabled on the master port, addition/deletion of individual links is
supported. MVRP packets received on the newly added link are accounted
instantaneously.
ExtremeXOS 15.7 Release Notes
39
Overview
Supported Platforms
•
BlackDiamond X8 and BlackDiamond 8800 series switches
•
Summit X770, X670, X670-G2, X480, X460, X460-G2, and X440, and X430
series switches
•
E4G-200 and E4G-400 cell site routers
Limitations
•
The individual ports of the LAG, including the master port, should not have
MVRP configuration prior to grouping.
•
MVRP can be enabled/disabled only on master port. The individual links cannot
be configured.
•
Once sharing is disabled, MVRP configuration of the master port is lost (default
is disabled).
•
The statistics and counters shown on the MVRP show commands are a
cumulative counter for all links added together. There are no per link counters.
•
The actual load sharing of the traffic is beyond MVRP's domain and should take
place as per the configured LAG setting. MVRP just adds the LAG port to the
VLAN(s).
ExtremeXOS 15.7 Release Notes
40
Overview
Changed CLI Commands
The following command is updated to show MVRP information. Changes are shown
in bold.
show vlan <vlan_name>
show vlan sys_vlan_0100
VLAN Interface with name sys_vlan_0100 created dynamically by
MVRP
Admin State:
802.1Q Tag 100
Enabled
Description:
Tagging:
None
Virtual router: VR-Default
IPv4 Forwarding: Disabled
IPv6 Forwarding: Disabled
IPv6:
None
STPD:
None
Protocol:
Match all unfiltered protocols
Loopback:
Disabled
NetLogin:
Disabled
QosProfile:
None configured
Egress Rate Limit Designated Port: None configured
Flood Rate Limit QosProfile: None configured
Ports:
1. (Number of active ports=1)
Tag: *2gH
Flags: (*) Active, (!) Disabled, (g) Load Sharing port
(b) Port blocked on the vlan, (m) Mac-Based port
(a) Egress traffic allowed for NetLogin
(u) Egress traffic unallowed for NetLogin
(t) Translate VLAN tag for Private-VLAN
(s) Private-VLAN System Port, (L) Loopback port
ExtremeXOS 15.7 Release Notes
41
Overview
(e) Private-VLAN End Point Port
(x) VMAN Tag Translated port
(G) Multi-switch LAG Group port
(H) Dynamically added by MVRP
ExtremeXOS 15.7 Release Notes
42
Overview
OpenFlow v1.3 and Pseudowire Multiprotocol Label
Switching (MPLS)
This feature provides limited support of OpenFlow v1.3 and includes controlling a
Multiprotocol Label Switching (MPLS) Pseudowire overlay network using OpenFlow:
•
Adds support for OpenFlow version 1.3 by upgrading to OpenVswitch (OVS)
version 2.1.
•
The OpenFlow Group table is supported for MPLS flows only; otherwise, only a
single table is supported.
•
L2VPN with static Pseudowire and static MPLS tunnel (using OpenFlow vendor
extensions).
•
MPLS label switching (for Pseudowire only).
•
Forwarding between normal VLAN/VMAN and OpenFlow Pseudowires using
standard Ethernet flooding and learning.
•
Enabling OpenFlow-controlled traffic and normal traffic to be sent and received
on the same VLAN/port.
•
Adds a new global “hybrid” mode operation to allow switches to operate as a
normal switch, but also allow a controller to install flows that can affect any port
and/or any VLAN.
•
Continues to support existing OpenFlow capabilities and scale that were
implemented in previous version of ExtremeXOS (v15.4.1).
Supported Platforms
NOTE
MPLS features are only supported on platforms that support MPLS. The
Summit X430 and X440 do not support MPLS.
•
BlackDiamond X8 [all modules; single Master Switch Fabric Module (MSM) only]
•
BlackDiamond 8800 [8900 (XL-series) and C-series; single Management Module
(MM) only]
•
Summit X770, X670, X480, X460, and X440
ExtremeXOS 15.7 Release Notes
43
Overview
Limitations
•
This features is not a full implementation of OpenFlow (see earlier list of
supported OpenFlow v1.3 capabilities)
•
Does not include implementing a controller or application.
•
MPLS and Pseudowire instances are limited by platform capabilities.
•
Access controll list (AC)L-based rule scale is limited by platform capabilities.
•
Forwarding database (FDB)-based rules are limited by platform FDB sizes.
•
Failover is not supported on chassis.
•
Stacking is not supported.
Static Generalized Precision Time Protocol (gPTP) Port
Roles
The Generalized Precision Time Protocol (gPTP) port role feature allows you to
enable or disable the Best Master Clock Algorithm (BMCA) function of gPTP.
Enabling BMCA selects the Grandmaster, builds the time-synchronization spanning
tree, and selects the port roles. If you disable BMCA and the switch should not be
the Grandmaster Clock, then you must select the ports on which gPTP is enabled to
take on the SlavePort role. If no port is configured for the SlavePort role, the switch
behaves as the Grandmaster, and all ports on the which gPTP is enabled take on
the MasterPort role.
Supported Platforms
Summit X770, X670, X670-G2, X460, X460-G2, and X440, and X430 series
switches
New CLI Commands
configure network-clock gptp bmca [on | off]
configure network-clock gptp slave-port [<port_no> | none]
ExtremeXOS 15.7 Release Notes
44
Overview
Protocol Independent Multicast (PIM) Enhancement:
Shortest-Path Tree (SPT) Threshold Option “Infinity”
This enhancement adds a new option for the shortest-path tree (SPT) threshold
parameter that causes the last hop router (LHR) to not switch over to SPT from
rendezvous point (RP) tree. When this option is configured, an LHR or intermediary
route does not build (S;G)s entries; instead traffic paths are based on (*;G)s only.
Supported Platforms
•
BlackDiamond X8 and BlackDiamond 8800 series switches
•
Summit X770, X670, X670-G2, X480, X460, X460-G2, and X440 series switches
•
E4G-200 and E4G-400 cell site routers
Changed CLI Commands
The following command is changed (shown in bold):
configure {ipv4|ipv6} pim spt_threshold infinity
ExtremeXOS 15.7 Release Notes
45
Overview
Deprecation of Domain Field from Open Shortest
Path First (OSPF)v3 Commands
For ExtremeXOS 15.7, the domain field is deprecated from all OSPFv3 commands.
ExtremeXOS Images for Summit X480 Series
Switches
Due to additional functionality and new platforms supported, the ExtremeXOS 15.6
and later software image is too large to download onto the Summit X480 series
switches. To resolve this issue, Summit X480 series switches now have two
separate software image files used for both individual switches and stacks that
include Summit X480 series switches.
Table 1: Summit X480 Series Switches Software Image Files
Main Install image
Diagnostic image
Content
All Summit X480 content
(except diagnostics)
Summit X480 diagnostics
File Name
summitX48015.6.xx.yy.xos
summitX480-15.6.xx.yydiagnostics.xmod
File Type
Standard ExtremeXOS image
XMOD image
Installation
Notes
• Installing the main
To update to a newer version of the
diagnostics, you download and
install the latest XMOD version. The
diagnostics XMOD can be installed
to the active or standby partition
and diagnostics can be used
immediately. There is no need to
reboot or any other action to
complete the installation.
SummitX480 image over a
previous release leaves the
previous installation of the
diagnostics image intact, as it
is stored separately from the
main ExtremeXOS image. You
can continue to use the
previously installed diagnostic
version to run diagnostics.
• The Summit XMODs, such as
SSH can be used with the
summitX480 ExtremeXOS
image.
ExtremeXOS 15.7 Release Notes
46
Overview
The following scenarios will produce an error or warning message:
•
Not having the diagnostic image installed on a Summit X480 series switch or
slot.
•
Installing the main Summit X480 image without the diagnostics image present.
•
Installing the general Summit image (summitX-15.7.xx.yy.xos, rather
than the Summit X480-specific image) on a Summit X480 series switch.
NOTE
If Summit X480 series switches require rescue recovery, you can use the
summitX-15.7.xx.yy.xos file image, and this image installs the
diagnostics capability.
New Hardware Supported in ExtremeXOS 15.7
This section lists the new hardware supported in ExtremeXOS 15.7:
•
BDXB-100G4X-XL I/O modules for the BlackDiamond X8 series switches
Hardware No Longer Supported
The following hardware is no longer supported in ExtremeXOS 15.7.1:
•
8500-G24X-e
•
8500-G48T-e
•
8500-MSM24
Hardware Issues in ExtremeXOS 15.6 and Later
The E4G-200 cell site router front panel alarm DB15 connector capabilities are not
currently supported.
ExtremeXOS 15.7 Release Notes
47
Overview
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-toobig-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.
ExtremeXOS Hardware/Software Compatibility
and Recommendation Matrices
The ExtremeXOS Hardware/Software Compatibility and
Recommendation Matrices 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/Software Compatibility and
Recommendation Matrices can be found at:
www.extremenetworks.com/documentation
Compatibility with NetSight
ExtremeXOS 15.7 is compatible with NetSight version 6.1 and later.
ExtremeXOS 15.7 Release Notes
48
Overview
Upgrading to ExtremeXOS
For instructions about upgrading ExtremeXOS software. see the “Software Upgrade
and Boot Options” chapter in the ExtremeXOS User Guide. The 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 Summit X480 series switches, starting with ExtremeXOS 15.6, two separate
software image files are used for both individual switches and stacks that
include Summit X480 series switches. For more information, see ExtremeXOS
Images for Summit X480 Series Switches on page 46.
Downloading Supported MIBs
The Extreme Networks MIBs are located on the eSupport website under Download
Software Updates, located at:
https://esupport.extremenetworks.com/
Tested Third-Party Products
This section lists the third-party products tested for ExtremeXOS 15.5.
Tested RADIUS Servers
The following RADIUS servers are fully tested:
•
Microsoft—Internet Authentication Server
•
Meetinghouse
•
FreeRADIUS
ExtremeXOS 15.7 Release Notes
49
Overview
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 standard–2
•
Siemens OpenStage 20
•
Siemens OpenStage 40
•
Siemens OpenStage 60
•
Siemens OpenStage 80
ExtremeXOS 15.7 Release Notes
50
Overview
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 register at:
http://www.extremenetworks.com/support/service-notification-form
ExtremeXOS 15.7 Release Notes
51
2
Limits
This chapter summarizes the supported limits in ExtremeXOS 15.7.1.
Table 2 summarizes tested metrics for a variety of features, as measured in a persystem 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 books.
NOTE
The term “BlackDiamond 8000 e-series” refers to all BlackDiamond 8500 eseries and 8800 e-series modules. The term “BlackDiamond 8000 series”
refers to all BlackDiamond 8500, 8800, and 8900 series modules.
The scaling and performance information shown in Table 2 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 2 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.
ExtremeXOS 15.7 Release Notes
52
Limits
Table 2: Supported Limits
Metric
Product
Limit
AAA (local)—maximum number
of admin and local user accounts.
All platforms
8
Access lists (meters)—maximum
number of meters.
BlackDiamond 8000 series
e-series, group of 24 ports
c-series
BlackDiamond 8900 series
8900-10G24X-c, group of 12 ports
8900 xl-series, 8900-G96T-c
8900-40G6X-xm
BlackDiamond X8 a-series modules
BlackDiamond X8-100G4X and BDX X8100G4X-XL modules
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
Access lists (policies)—suggested
maximum number of lines in a
single policy file.
ExtremeXOS 15.7 Release Notes
512
2,048 ingress,
256 egress
1,024 ingress,
256 egress
4,096 ingress,
512 egress
512 ingress
512 egress
512 ingress,
512 egress
8,192 ingress,
1,024 egress
1,024 ingress
256 egress
512 ingress
2,048 ingress,
256 egress
4,096 ingress,
512 egress
512 ingress
512 egress
Summit X770, X670-G2, X460-G2
1,024 ingress,
512 egress
All platforms
300,000
53
Limits
Table 2: Supported Limits (Continued)
Metric
Product
Access lists (policies)—maximum
number of rules in a single policy
file.a
BlackDiamond 8000 series
c-series, group of 24 ports
e-series, group of 24 ports
BlackDiamond 8900
8900-10G24X-c modules, group of 12
ports
Limit
4,096 ingress,
512 egress
1,024 ingress
2,048 ingress,
512 egress
8900-G96T-c modules, group of 48
ports
8,192 ingress,
1,024 egress
8900 xl-series
8900-40G6X-xm
61,440 (up to)
2,048 ingress,
1,024 egress
BlackDiamond X8 a-series modules
BlackDiamond X8-100G4X modules
BlackDiamond XB-100G4X-XL modules
Summit X440, X430 group of 24 ports
2,048 ingress,
1,024 egress
8,192 ingress,
1,024 egress
139,264 ingress
1,024 egress.
1,024 ingress
Summit X460, E4G-400
Summit X480
Summit X670
VIM4-40G4x
Summit X480
Summit X480
VIM3-40G4X
4,096 ingress,
512 egress
(up to) 61,440
ingress,
1,024 egress
2,048 ingress
1,024 egress
8,192 ingress/
1,024 egress
2048 ingress
1024 egress
Summit X770, X670-G2, X460-G2
E4G-200
ExtremeXOS 15.7 Release Notes
4,096 ingress
1,024 egress
2,048 ingress/
512 egress
54
Limits
Table 2: Supported Limits (Continued)
Metric
Product
Limit
Access lists (slices)—number of
ACL slices.
BlackDiamond 8000 series
c-series, group of 48 ports
16
BlackDiamond 8900 series
8900-10G24X-c modules, group of 12
ports
12 ingress,
4 egress
8900-G96T-c modules, group of 48
ports
8900 xl-series
8900-40G6X-xm
BlackDiamond X8 a-series modules
BlackDiamond X8-100G4X modules
BlackDiamond XB-100G4X-XL modules
E4G-200
16 ingress,
4 egress
17b
10 ingress,
4 egress
10 ingress,
4 egress
16 ingress,
4 egress
17 ingress
4 egress
8 ingress,
4 egress
Summit X440, X430
4 ingress
Summit X460, E4G-400, X460-G2
Summit X480
Summit X670
VIM4-40G4x
Summit X480
VIM3-40G4X
Summit X770, X670-G2
16 ingress,
4 egress
17b 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.
ExtremeXOS 15.7 Release Notes
Summit X440, X460, X460-G2
Summit X670, X670, X670-G2
Summit X430
1,024
4,096
100*
55
Limits
Table 2: Supported Limits (Continued)
Metric
Product
Limit
BFD sessions—maximum number
of BFD sessions.
All platforms (default timers—1 sec)
BlackDiamond X8 and 8800 (minimal
timers—50 msec)
All Summits
(minimal timers—100 msec)
512
10c
10c
BGP (aggregates)—maximum
number of BGP aggregates.
All platforms (except E4G-200, X430,
and X440) with Core license or higher
256
BGP (networks)—maximum
number of BGP networks.
All platforms (except E4G-200, X430,
and X440) with Core license or higher
BlackDiamond X8 series
1,024
BlackDiamond X8 series
BlackDiamond 8000 series
BlackDiamond xl-series
All Summits, except X480, X440, X430,
E4G-200
E4G-400
Summit X480
512
512
512
128*
128*
512
BGP (peer groups)—maximum
number of BGP peer groups.
BlackDiamond 8900 series
BlackDiamond 8800
BlackDiamond X8 series
Summit X480
Summit X770, X670-G2, X670v-48t,
X670, X460-G2, X460 (with Core
license or higher)
128
64
128
128
64
BGP (policy entries)—maximum
number of BGP policy entries per
route policy.
All platforms (except E4G-200, X430,
and X440) with Core license or higher
256
BGP (policy statements)—
maximum number of BGP policy
statements per route policy.
All platforms (except E4G-200, X430,
and X440) with Core license or higher
1,024
BGP multicast address-family
routes—maximum number of
multicast address-family routes.
BlackDiamond 8900 xl-series
524,256 (up to)b
25,000
1,048,544 (up
to)m
25,000
BGP (peers)—maximum number
of BGP peers.
NOTE: With default keepalive and
hold timers.
BlackDiamond X8 series
BlackDiamond X8-100G4X-XL modules
Summit X460, X460-G2, X670, X670G2, X770
Summit X480
1,024
524,256 (up to)b
25,000
E4G-400
ExtremeXOS 15.7 Release Notes
56
Limits
Table 2: Supported Limits (Continued)
Metric
Product
Limit
BGP (unicast address-family
routes)—maximum number of
unicast address-family routes.
BlackDiamond 8900 xl-series
524,256 (up to)b
25,000
1,048,544 (up
to) m
25,000
524,256 (up to)b
25,000
BGP (non-unique routes)—
maximum number of non-unique
BGP routes.
BlackDiamond 8900 xl-series
BlackDiamond X8 series
BlackDiamond X8 with 100G4X-XL
modules
Summit X460, X460-G2, X670, X670G2, X770
Summit X480
E4G-400
1,200,000
24,000
1,200,000
BGP ECMP—maximum number of
equalcost multipath for BGP and
BGPv6.
All platforms, except Summit X430,
X440, and E4G-200
BlackDiamond 8800 G48Te2 (for
BGPv6)
2, 4, or 8
BGPv6 (unicast address-family
routes)—maximum number of
unicast address family routes.
BlackDiamond 8900 xl-series
BlackDiamond 8800 c-series
BlackDiamond 8000 e-series
BlackDiamond X8 series
BlackDiamond X8-100G4X-XL modules
Summit X460, X460-G2
Summit X480
Summit X670, X670-G2, X770
E4G-400
20,000
6,000
240
8,000
20,000
BlackDiamond 8900 xl-series
BlackDiamond 8800 c-series
BlackDiamond 8000 e-series
BlackDiamond X8 series
BlackDiamond X8-100G4X-XL modules
Summit X460, X460-G2
Summit X480, X670, X670-G2, X770
E4G-400
24,000
18,000
720
24,000
24,000
BGPv6 (non-unique routes)—
maximum number of non-unique
BGP routes
BlackDiamond X8 series
BlackDiamond X8-100G4X-XL modules
Summit X460, X460-G2, X670, X670G2, X770
Summit X480
E4G-400
25,000
1,000,000
25,000
N/A
6,000
20,000
8,000
6,000
18,000
24,000
18,000
ExtremeXOS 15.7 Release Notes
57
Limits
Table 2: Supported Limits (Continued)
Metric
Product
Limit
BOOTP/DHCP relay—maximum
number of BOOTP or DHCP
servers per virtual router.
All platforms, except Summit X430
4
BOOTP/DHCP relay—maximum
number of BOOTP or DHCP
servers per VLAN.
All platforms, except Summit X430
4
CES TDM pseudowires—maximum
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
All platforms
256
BlackDiamond 8000 series
BlackDiamond X8 series
Summit series
32
32
32
BlackDiamond 8000 series
BlackDiamond X8 series
Summit series X460, E4G-200, E4G400 (non-load shared ports)
32
32
All other platforms
32
All platforms
2,000
All Summits, except X430
128
All platforms
1,000
NOTE: With Advanced Edge
license or higher.
CFM—maximum number of CFM
associations.
NOTE: With Advanced Edge
license or higher.
CFM—maximum number of CFM
up end points.
NOTE: With Advanced Edge
license or higher.
CFM—maximum number of CFM
down end points.
NOTE: With Advanced Edge
license or higher.
CFM—maximum number of CFM
remote end points per up/down
end point.
256 (non-load
shared ports)
32 (load shared
ports)
NOTE: With Advanced Edge
license or higher.
CFM—maximum number of
dot1ag ports.
NOTE: With Advanced Edge
license or higher.
CFM—maximum number of CFM
segments.
NOTE: With Advanced Edge
license or higher.
ExtremeXOS 15.7 Release Notes
58
Limits
Table 2: Supported Limits (Continued)
Metric
Product
Limit
CFM—maximum number of MIPs.
All platforms
256
BlackDiamond X8, BlackDiamond 8800
Summit X440, X430
Summit X670
Summit X460, X460-G2, X770, X670G2
Summit X480
E4G-200
E4G-400
4,096
1,024
2,048
4,094
Data Center Bridging eXchange
(DCBX) protocol Type Length
Value (TLVs)—maximum number
of DCBX application TLVs.
All platforms
8
DHCPv6 Prefix Delegation
Snooping—Maximum number of
DHCPv6 prefix delegation
snooped entries.
All platforms
256
(with Underlying
Protocol Ripng)
128
(with Underlying
protocol
OSPFv3)
1,024
(with static
routes)
Dynamic ACLs—maximum
number of ACLs processed per
second.
Summit X480, X670
with 50 DACLs
with 500 DACLs
BlackDiamond X8
BlackDiamond 8800
NOTE: With Advanced Edge
license or higher.
CLEAR-Flow—total number of
rules supported. The ACL rules
plus CLEAR-Flow rules must be
less than the total number of
supported ACLs.
NOTE: Limits are load dependent.
8,192
2,048
4,094
10
5
N/A
N/A
EAPS domains—maximum
number of EAPS domains.
NOTE: An EAPS ring that is being
spatially reused cannot have more
than four configured EAPS
domains.
BlackDiamond 8000 series
BlackDiamond X8 series
Summit series (except X430), E4G-200,
E4G-400
Summit X430
64
64
32
EAPSv1 protected VLANs—
maximum number of protected
VLANs.
BlackDiamond 8000 series
BlackDiamond X8 series
Summit series, E4G-200, E4G-400
2,000
2,000
1,000
ExtremeXOS 15.7 Release Notes
4
59
Limits
Table 2: Supported Limits (Continued)
Metric
Product
Limit
EAPSv2 protected VLANs—
maximum number of protected
VLANs.
BlackDiamond 8000 series
BlackDiamond X8 series
All Summits (except X430, X440),
E4G-200, E4G-400
2,000
2,000
500
ELSM (vlan-ports)—maximum
number of VLAN ports.
BlackDiamond 8000 series
BlackDiamond X8 series
All Summits, E4G-200, E4G-400
5,000
5,000
5,000
ERPS domains—maximum
number of ERPS domains without
CFM configured
BlackDiamond 8800 series
BlackDiamond X8 series
Summit series (except X430), E4G-200,
E4G-400
Summit X430
32
32
32
BlackDiamond 8800 series
BlackDiamond X8 series
Summit X440, X770, X670, X670-G2,
X480, X460-G2
Summit X460
Summit X430
E4G-200, E4G-400
16
16
16
ERPSv1 protected VLANs—
maximum number of protected
VLANs.
BlackDiamond 8800 series
BlackDiamond X8 series
All Summits, E4G-200, E4G-400
2,000
2,000
1,000
ERPSv2 protected VLANs—
maximum number of protected
VLANs
BlackDiamond 8800 series
BlackDiamond X8 series
All Summits (except X430), E4G-200,
E4G-400
2,000
2,000
500
ESRP groups—maximum number
of ESRP groups.
All platforms
7
ESRP domains—maximum
number of ESRP domains.
All platforms
64
ESRP VLANs—maximum number
of ESRP VLANs.
BlackDiamond 8800
BlackDiamond X8
All Summits
E4G-200. E4G-400
1,000
2,048
1,000
1,000
ESRP (maximum ping tracks)—
maximum number of ping tracks
per VLAN.
All platforms (except Summit X430)
8
ESRP (IP route tracks)—maximum
IP route tracks per VLAN.
All platforms (except Summit X430)
8
ERPS domains—maximum
number of ERPS domains with
CFM configured.
ExtremeXOS 15.7 Release Notes
4
32
4
32
60
Limits
Table 2: Supported Limits (Continued)
Metric
Product
Limit
ESRP (VLAN tracks)—maximum
number of VLAN tracks per
VLAN.
All platforms (except Summit X430)
1
Forwarding rate—maximum L2/L3
software forwarding rate.
BlackDiamond 8000 series
BlackDiamond X8 series
Summit X770
Summit X670-G2
Summit X670
Summit X480
Summit X460-G2
Summit X460
Summit X440
E4G-200
E4G-400
10,000 pps
20,000 pps
16.000 pps
29,028 pps
14,829 pps
14,509 pps
29,037 pps
5,222 pps
5,418 pps
8,718 pps
5,536 pps
FDB (blackhole entries)—
maximum number of unicast
blackhole FDB entries.
BlackDiamond 8800 c-series
BlackDiamond 8000 e-series
BlackDiamond 8900 series
8900 c-series
8900 xl-series
32,000
8,000
8900-40G6X-xm
BlackDiamond X8 a-series modules
BlackDiamond X8-100G4X modules
BlackDiamond XB-100G4X-XL modules
E4G-200, E4G-400
Summit X440, X430
Summit X480
Summit X460
Summit X460-G2
Summit X670 VIM4-40G4x,
X480 VIM3-40G4X
Summit X770, X670-G2
Summit X670, X670v-48t
ExtremeXOS 15.7 Release Notes
32,000
524,288 (up to)b
128,000
128,000
384,000
384,000 d
32,000
16,000
524,288 (up to)b
32,000
49,152e
128,000
294,912e
130,000e
61
Limits
Table 2: Supported Limits (Continued)
Metric
Product
Limit
FDB (blackhole entries)—
maximum number of multicast
blackhole FDB entries.
BlackDiamond 8000 series
BlackDiamond X8 series
Summit X480, X460-G2, X460, X440,
X430
Summit X770, X670, X670-G2, X670v48t, X480 VIM3-40G4X
E4G-200, E4G-400
1,024
1,024
1,024
BlackDiamond 8000 c-series
BlackDiamond 8000 e-series
BlackDiamond 8000 (system), except
8900 xl-series
BlackDiamond 8900 xl-series
BlackDiamond X8 a-series modules
BlackDiamond X8-100G4X modules
BlackDiamond BDX X8-100G4X-XL
modules
32,768f
8,192f
128,000f
FDB (maximum L2 entries)—
maximum number of MAC
addresses.
E4G-200, E4G-400
Summit X440, X430
Summit X480 (40G4X)
Summit X460
Summit X460-G2, X670-G2
Summit X670
Summit X770
FDB (Maximum L2 entries)—
maximum number of multicast
FDB entries.
FIP Snooping VLANs
4,096
1,024
524,488 (up to)b
128,000f
384,000f
1,048,576 (up
to)b g
32,000f
16,000f
524,488 (up to)b
32,000f
288,000f
128,000f
294,912e f
BlackDiamond X8
BlackDiamond 8800
Summit X770, X670, X670-G2
Summit X480, X460, X460-G2, X430,
X440
E4G-200, E4G-400
1,024
1,024
4,096
1,024
BlackDiamond X8
768
1,024
BlackDiamond 8800 (8900-40G6X-c
only)
Summit X670
FIP Snooping Virtual Links
(FPMA mode) per port group
BlackDiamond X8
1,908
BlackDiamond 8800 (8900-40G6X-c
only)
Summit X670
ExtremeXOS 15.7 Release Notes
62
Limits
Table 2: Supported Limits (Continued)
Metric
Product
Limit
FIP Snooping FCFs
(with perimeter port) per port
group
BlackDiamond X8
238
FIP Snooping FCFs
(with Enode-to-FCF port)
BlackDiamond X8
BlackDiamond 8800 (8900-40G6X-c
only)
212
BlackDiamond 8800 (8900-40G6X-c
only)
Summit X670
Identity management—maximum
number of Blacklist entries.
All platforms, except Summit X430.
Summit X430
512
N/A
Identity management—maximum
number of Whitelist entries.
All platforms, except Summit X430.
Summit X430
512
N/A
Identity management—maximum
number of roles that can be
created.
All platforms, except Summit X430.
Summit X430
64
N/A
Identity management—maximum
role hierarchy depth allowed.
All platforms, except Summit X430.
Summit X430
5
N/A
Identity management—maximum
number of attribute value pairs in
a role match criteria.
All platforms, except Summit X430.
Summit X430
16
N/A
Identity management—maximum
of child roles for a role.
All platforms, except Summit X430.
Summit X430
8
N/A
Identity management—maximum
number of policies/dynamic ACLs
that can be configured per role.
All platforms, except Summit X430.
Summit X430
8
N/A
Identity management—maximum
number of LDAP servers that can
be configured.
All platforms, except Summit X430.
Summit X430
8
N/A
Identity management—maximum
number of Kerberos servers that
can be configured.
All platforms, except Summit X430.
Summit X430
20
N/A
Identity management—maximum
database memory-size.
All platforms, except Summit X430.
Summit X430
512
N/A
Identity management—
recommended number of
identities per switch.
All platforms, except Summit X430.
Summit X430
100
N/A
NOTE: Number of identities per
switch is for a default identity
management database size (512
Kbytes) across all platforms.
ExtremeXOS 15.7 Release Notes
63
Limits
Table 2: Supported Limits (Continued)
Metric
Product
Limit
Identity management—
recommended number of ACL
entries per identity.
All platforms, except Summit X430.
Summit X430
20
N/A
Identity management—maximum
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
N/A
IGMP sender—maximum number
of IGMP senders per switch (IP
multicast compression disabled).r
BlackDiamond 8800 c-series
BlackDiamond 8000 e-series
BlackDiamond 8900-10G24X-c modules
BlackDiamond 8900-G96T-c modules
BlackDiamond 8900-40G6X-xm
BlackDiamond 8900 xl-series
BlackDiamond X8 a-series modules
BlackDiamond X8-100G4X and BDX X8100G4X-XL L modules
E4G-200, E4G-400
Summit X440
Summit X480
Summit X460
Summit X460-G2
Summit X670
Summit X670-G2
Summit X770
Summit X430
2,048h
500i
2,048h
4,096h
3,000i
4,096h
4,096j
16,384e
NOTE: Number of ACLs per
identity based on system ACL
limitation.
NOTE: Assumes source-groupvlan mode.
ExtremeXOS 15.7 Release Notes
2,048
64
4,096
2,048
4,096
3,000i
4,096i
4,096
64
64
Limits
Table 2: Supported Limits (Continued)
Metric
Product
Limit
IGMP sender—maximum number
of IGMP senders per switch (IP
multicast compression enabled).r
NOTE: Assumes source-groupvlan mode.
For additional limits, see:
• Layer-2 IPMC forwarding
caches—(IGMP/MLD/PIM
snooping) in mac-vlan mode.
on page 79
BlackDiamond 8800 c-series
BlackDiamond 8000 e-series
BlackDiamond 8900-10G24X-c modules
BlackDiamond 8900-G96T-c modules
BlackDiamond 8900-40G6X-xm
BlackDiamond 8900 xl-series
BlackDiamond X8 a-series modules
BlackDiamond X8-100G4X and BDX X8100G4X-XL modules
E4G-200
E4G-400
Summit X440
Summit X460
Summit X460-G2
Summit X480
Summit X670
Summit X770, X670-G2
Summit X430
2,048i
500i
2,048i
4,096i
3,000i
12,000i
4,096b
64,000i
BlackDiamond 8800 c-series
BlackDiamond 8000 e-series
BlackDiamond 8900 c-series
BlackDiamond 8900 xl-series
BlackDiamond 8900-40G6X-xm
BlackDiamond X8 a-series modules
BlackDiamond X8-100G4X and BDX X8100G4X-XL modules
E4G-200, E4G-400
Summit X440
Summit X460, X670, X440
Summit X460-G2
Summit X480
Summit X770, X670-G2
2,000
448
1,000
4,000
1,000
1,000
4,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
• Layer-2 IPMC forwarding
caches— (IGMP/MLD/PIM
snooping) in mixed-mode. on
page 79
IGMP snooping per VLAN filters—
maximum number of VLANs
supported in per-VLAN IGMP
snooping mode.
ExtremeXOS 15.7 Release Notes
3,000i j
6,000i j
192i
6,000i
21,000i
12,000i
3,000
66,500i
192
1,000
448
1,000
1,350
4,000
2,000
65
Limits
Table 2: Supported Limits (Continued)
Metric
Product
Limit
IGMPv2 subscriber—maximum
number of IGMPv2 subscribers
per port.s
BlackDiamond 8800 c-series
BlackDiamond 8900 c-series
BlackDiamond X8 series
Summit X430, X460, E4G-200, E4G400, X440
Summit X480, X670, X670v-48t
Summit X770, X670-G2, X460-G2
2,000
2,000
2,000
1,000
BlackDiamond 8800 c-series
BlackDiamond 8900 c-series
BlackDiamond X8 series
Summit X430, X440, E4G-200
Summit X460, X460-G2, X480, X670,
E4G-400, X670v-48t
Summit X770, X670-G2
20,000
20,000
20,000
10,000
IGMPv3 maximum source per
group—maximum number of
source addresses per group.
All platforms
250
IGMPv3 subscriber—maximum
number of IGMPv3 subscribers
per port.s
BlackDiamond 8800 e-series
BlackDiamond 8800 c-series
BlackDiamond 8900 series
BlackDiamond X8 series
Summit X480, X670, X670v-48t, E4G200, X440
Summit X770, X670-G2, X460-G2
Summit X460, E4G-400
1,000
2,000
5,000
3,000
1,000
BlackDiamond 8800 e-series
BlackDiamond 8800 c-series
BlackDiamond 8900 series
BlackDiamond X8 series
Summit X670, X670v-48t, X480, E4G200, X440
Summit X460, X460-G2, E4G-400
Summit X770, X670-G2
10,000
20,000
30,000
30,000
10,000
BlackDiamond X8-100G4X modules
Summit X670-G2, X770
Summit X670, X480, X460, X440, X430
Summit X460-G2
E4G-200, E4G-400
229,374 (up to)k
131,072(up to)k
20,480
57,344 (up to)k
20,480
IGMPv2 subscriber—maximum
number of IGMPv2 subscribers
per switch.s
IGMPv3 subscriber—maximum
number of IGMPv3 subscribers
per switch.s
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).
ExtremeXOS 15.7 Release Notes
2,000
4,000
20,000
30,000
4,000
2,000
20,000
30,000
66
Limits
Table 2: Supported Limits (Continued)
Metric
Product
IP ARP entries in software with
distributed mode on—maximum
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
BlackDiamond X8 series
All other platforms
IPv4 ARP entries in hardware with
distributed mode on—maximum
number of IP ARP entries in
hardware with distributed mode
on
IPv4 ARP entries in hardware with
minimum LPM routes—maximum
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.
ExtremeXOS 15.7 Release Notes
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
BlackDiamond 8800 c-, xm-series
BlackDiamond 8000 e-series
BlackDiamond 8900 xl-series
BlackDiamond X8 a-series
BlackDiamond X8-100G4X modules
BlackDiamond BDX X8-100G4X-XL
modules
E4G-200
E4G-400
Summit X440
Summit X670, X480 (40G4X)
Summit X460, X480
Summit X460-G2
Summit X770, X670-G2
Limit
260,000
100,000
28,000
N/A
32,500b
16,250b
8,000
8,000
12,000
N/A
8,000
1,000i
16,000
16,000
182,000(up to)k l
282,000l
8,000
16,000
412
8,000
16,000
50,000 (up to)k
108,000(up to)k
67
Limits
Table 2: Supported Limits (Continued)
Metric
Product
Limit
IPv4 ARP entries in hardware with
maximum LPM routes—maximum
recommended number of IPv4
ARP entries in hardware, with
maximum LPM routes present.
For BlackDiamond 8800,
BlackDiamond X8, E4G, and
Summit series, assumes number
of IP route reserved entries is
“maximum.”
BlackDiamond 8800 c-, xm-series
BlackDiamond 8000 e-series
BlackDiamond 8900 xl-series
BlackDiamond X8 a-series
BlackDiamond X8-100G4X modules
6,000i
500i
12,000i
12,000i
172,000 (up to)k
l
E4G-200
E4G-400
Summit X440
Summit X460, X480
Summit X670, X480 VIM3-40G4X
Summit X770, X670-G2
6,000i
12,000i
380
12,000i
6,000i
98,000 (up to)k
43,000 (up to)k
Summit X460-G2
IP flow information export
(IPFIX)—number of simultaneous
flows.
BlackDiamond 8900 xl-series modules
BlackDiamond 8900 c-series modules
BlackDiamond X-100G4X and BDX X8100G4X-XL modules
Summit X460-24t/x/p, X460-G2
Summit X480, X460-48t/x/p
E4G-400
ExtremeXOS 15.7 Release Notes
4,096 ingress,
4,096 egress
4,096 ingress,
4,096 egress
2,048 ingress,
2,048 egress
2,048 ingress,
2,048 egress
4,096 ingress,
4,096 egress
2,048 ingress,
2,048 egress
68
Limits
Table 2: Supported Limits (Continued)
Metric
Product
Limit
IPv4 remote hosts in hardware
with zero LPM routes—maximum
recommended number of IPv4
remote hosts (hosts reachable
through a gateway) in hardware
when LPM routing is not used.
For BlackDiamond 8800,
BlackDiamond X8, E4G, and
Summit series, assumes number
of IP route reserved entries is 0,
and number of IPv4 ARP entries
present is 100 or less.
BlackDiamond 8800 c-series
BlackDiamond 8000 e-series
BlackDiamond 8900 xl-series
BlackDiamond 8900-40G6X-xm
BlackDiamond X8 a-series
BlackDiamond X8-100G4X and X8100G4X-XLmodules
E4G-200
E4G-400
Summit X440
Summit X460
Summit X460-G2
Summit X480
Summit X670, X480 VIM3-40G4X
Summit X770, X670-G2
18,000i
1,000i
40,000b
22,000i
28,000i
311,000 (up to)k
IPv4 routes—maximum number of
IPv4 routes in software
(combination of unicast and
multicast routes).
BlackDiamond 8900 xl-series with
8900-MSM128 or MSM-48c
All other BlackDiamond 8000 series
hardware
BlackDiamond X8 series
BlackDiamond X8 with BDX X8100G4X-XL modules
Summit X440
Summit X460, X670, X770, X670-G2,
X460-G2
Summit X480
524,256 (up to)b
25,000
l
18,000i
20,000i
448
20,000i
73,000k
40,000b
22,000i
176,000 (up to)k
25,000
1,048,544 (up
to)m
256
25,000
524,256 (up to)b
25,000
E4G-200, E4G-400
ExtremeXOS 15.7 Release Notes
69
Limits
Table 2: Supported Limits (Continued)
Metric
Product
Limit
IPv4 routes (LPM entries in
hardware)— number of IPv4
routes in hardware.
BlackDiamond 8800 c-series
BlackDiamond 8000 e-series
BlackDiamond 8900 xl-series
12,000
480
524,256 (up to)b
n
BlackDiamond 8900-40G6X-xm
BlackDiamond X8 series
BlackDiamond BDX X8-100G4X-XL
modules
E4G-200, E4G-400
Summit X440
Summit X460, X460-G2
Summit X480
16,000e
16,000e
1,048,544 (up
to) o
12,000
32
12,000
524,256 (up to)b
n
Summit X480 VIM3-40G4X
Summit X670
Summit X770, X670-G2
16,000n
12,000
16,000
IPv6 addresses on an interface—
maximum number of IPv6
addresses on an interface.
All platforms
255
IPv6 addresses on a switch—
maximum number of IPv6
addresses on a switch
BlackDiamond 8000 series
BlackDiamond X8 series
E4G-200, E4G-400
Summit X440
Summit X460, X480
Summit X770, X670, X670-G2, X460-G2
512
2,048
512
254
512
2,048
ExtremeXOS 15.7 Release Notes
70
Limits
Table 2: Supported Limits (Continued)
Metric
Product
Limit
IPv6 host entries in hardware—
maximum number of IPv6
neighbor entries in hardware.
BlackDiamond 8800 c-, xm-series
BlackDiamond 8000 e-series
BlackDiamond 8900-10G24X-c modules
BlackDiamond 8900-G96T-c modules
BlackDiamond 8900 xl-series
BlackDiamond X8 a-series
BlackDiamond X8-100G4X and BDX X8100G4X-XL modules
E4G-200
E4G-400
Summit X440
Summit X460, X670, X480 VIM340G4X
Summit X770, X670-G2
Summit X480, X670v-48t
Summit X460-G2
3,000i
250i
2,000i
4,000i
8,192 (up to)b i
3,000i
49,000i p
BlackDiamond 8800 c-series
BlackDiamond 8000 e-series
BlackDiamond 8900 xm-series
BlackDiamond 8900 xl-series
6,000
240
8,000
245,760 (up to)b
8,000
524,288 (up to)
IPv6 routes (LPM entries in
hardware)—maximum number of
IPv6 routes in hardware.
BlackDiamond X8 series
BlackDiamond BDX X8-100G4X-XL
modules
E4G-200, E4G-400
Summit X440
Summit X460, X460-G2
Summit X670, X480 (VIM3-40G4X),
X670, X670-G2, X770
Summit X480
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
BlackDiamond 8000 xl-series
BlackDiamond X8 series
BlackDiamond BDX X8-100G4X-XL
modules
E4G-200, E4G-400
Summit X440, X460, X460-G2, X670,
X670-G2, X770, X480 (VIM3-40G4X)
Summit X480
ExtremeXOS 15.7 Release Notes
2,000i
3,000i
192i
3,000i
36,750i
6,000i
22,000i
p
6,000
16
6,000
8,000
245,760 (up to)b
256
245,760 (up to)b
256
524,288 (up to)
p
256
256
245,760 (up to)b
71
Limits
Table 2: Supported Limits (Continued)
Metric
Product
Limit
IPv6 route sharing in hardware—
route mask lengths for which
ECMP is supported in hardware.
Summit X460, X480, X670, X670V-48t
E4G-200, E4G-400
BlackDiamond 8800 (all I/O modules,
except G48Te2)
Summit X460-G2, X670-G2, X770
0–128
0–128
0–128
BlackDiamond X8 a-series
BlackDiamond X8-100G4X modules
BlackDiamond X8-100G4X-XL modules
Summit X440, X430
BlackDiamond 8800 G48Te2
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
BlackDiamond X8 series
BlackDiamond X8 with BDX X8100G4X-XL modules
Summit X460, X460-G2, X670, X670G2, X770, E4G-200, E4G-400
Summit X480
0–64 (> 64
single path only)
0–128
0–64 (> 64
single path only)
0–128 p
N/A
N/A
245,760 (up to)b
25,000
25,000
524,288 (up to)
p
25,000
245,760 (up to)b
256
Summit X440
IP router interfaces—maximum
number of VLANs performing
IPv4 and/or IPv6 routing.
Excludes sub-VLANs.
Summit X460-G2, X670, X770, X670G2, and BlackDiamond X8
BlackDiamond 8800
Summit X440
Summit X480, X460
E4G-200, E4G-400
2,048
IP multicast static routes—
maximum number of permanent
multicast IP routes.
All platforms (except Summit X430,
X440)
Summit X430, X440
1,024
IP unicast static routes—maximum
number of permanent IP unicast
routes.
All platforms (except Summit X430,
X440)
Summit X430, X440
1,024
ExtremeXOS 15.7 Release Notes
512
254
512
512
32
32
72
Limits
Table 2: Supported Limits (Continued)
Metric
Product
Limit
IP route sharing (maximum
gateways)—Configurable
maximum number of gateways
used by equal cost multipath
OSPF, BGP, IS-IS, static routes, or
L2VPNs. 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.
Static routes are limited to 32
next-hops. L2VPNs are limited to
16 LSPs per pseudowire on
platforms that support 32
gateways, and 64 LSPs per
pseudowire on platforms that
support 64 gateways.
All platforms, except Summit X430,
X440, X670, and BlackDiamond X8
Summit X670, BlackDiamond X8
2, 4, 8, 16, or 32
2, 4, 6, 8, 16, 32,
or 64
N/A
N/A
IP route sharing (total
destinations)—maximum number
of unique destinations used by
multipath OSPF, OSPFv3, BGP, ISIS, or static routes.
BlackDiamond 8800 c-series
BlackDiamond 8000 e-series
BlackDiamond 8900 xl-series
12,256
480
524,256 (up to)b
NOTE: For platforms with limit of
524,256 or higher, the total
number of "destination+gateway"
pairs is limited to 2,097,024. For
example, if the number of unique
destinations is 524,256, only 2
gateways per destination is
supported.
BlackDiamond 8900-40G6X-xm
BlackDiamond X8
BlackDiamond BDX X8-100G4X-XL
modules
16,352
16,352
1,048,544 (up
to) m
12.256
524,256 (up to)b
16,352
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.
ExtremeXOS 15.7 Release Notes
Summit X430, X440
BlackDiamond 8800 G48Te2 (for IPv6)
E4G-200, E4G-400
Summit X480
Summit X670, X670-G2, X770, X480
(VIM3-40G4X)
Summit X460-G2, X460
12,256
73
Limits
Table 2: Supported Limits (Continued)
Metric
Product
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 xmseries
default maximum gateways of 4
if maximum gateways is 2
if maximum gateways is 8
if maximum gateways is 16
if maximum gateways is 32
BlackDiamond 8000 e-series
default maximum gateways of 4
if maximum gateways is 2
if maximum gateways is 8
if maximum gateways is 16
if maximum gateways is 32
BlackDiamond X8 series, Summit X670
default maximum gateways of 4
if maximum gateways is 2
if maximum gateways is 8
if maximum gateways is 16
if maximum gateways is 32
if maximum gateways is 64
Summit X460, X460-G2, X480, X670,
X670-G2, X770, E4G-200, E4G-400
default maximum gateways of 4
if maximum gateways is 2
if maximum gateways is 8
if maximum gateways is 16
if maximum gateways is 32
Limit
510
1,022
254
126
62
30
62
14
6
2
510
1,022
254
126
62
30
510
1,022
254
126
62
IP multinetting (secondary IP
addresses)—maximum number of
secondary IP addresses per
VLAN.
BlackDiamond 8800
BlackDiamond X8
All Summits, except X440, X430
Summit X440
64
64
255
32
IS-IS adjacencies—maximum
number of supported IS-IS
adjacencies.
BlackDiamond 8000 series
BlackDiamond X8 series
BlackDiamond 8900 xl-series
Summit X440, X460, X460-G2, X480,
X670, X670-G2, X770
E4G-200
E4G-400
128
128
255
128
All platforms, except Summit X440,
X430
BlackDiamond 8800 G48Te2 (for IPv6)
2, 4, or 8
All platforms, except Summit X440,
x430
255
IS-IS ECMP—maximum number of
equal cost multipath for IS-IS.
IS-IS interfaces—maximum
number of interfaces that can
support IS-IS.
ExtremeXOS 15.7 Release Notes
256
128
N/A
74
Limits
Table 2: Supported Limits (Continued)
Metric
Product
Limit
IS-IS routers in an area—
recommended maximum number
of IS-IS routers in an area.
Summit X480
All other platforms, except Summit
X440, X430
128
256
IS-IS route origination—
recommended maximum number
of routes that can be originated
by an IS-IS node.
BlackDiamond 8000 series
BlackDiamond X8 series
BlackDiamond BDX X8-100G4X-XL
modules
BlackDiamond 8900 xl-series
Summit X460, X460-G2, X670, X670G2, X770, X480,
E4G-400
E4G-200
20,000
20,000
30,000
BlackDiamond 8000 series
BlackDiamond X8 series
BlackDiamond BDX X8-100G4X-XL
modules
BlackDiamond 8900 xl-series
Summit X480
Summit X460, X460-G2, X670, X670G2, X770
E4G-200, E4G-400
25,000
25,000
120,000
IS-IS IPv4 L2 routes—
recommended maximum number
of IS-IS Level 2 routes.
BlackDiamond 8000 series
BlackDiamond X8 series
BlackDiamond BDX X8-100G4X-XL
modules
BlackDiamond 8900 xl-series
Summit X480
Summit X460, X460-G2, X670, X670G2, X770
E4G-200, E4G-400
20,000
25,000
120,000
120,000
50,000
25,000
25,000
IS-IS IPv4 L1 routes in an L1/L2
router—recommended maximum
number of IS-IS Level 1 routes in
an L1/L2 IS-IS router.
BlackDiamond 8000 series
BlackDiamond X8 series
BlackDiamond 8900 xl-series
Summit X460, X460-G2, X480, X670,
X670-G2. X770
E4G-200, E4G-400
20,000
20,000
20,000
20,000
IS-IS IPv4 L1 routes in an L1
router—recommended maximum
number of IS-IS Level 1 routes in a
Level 1 IS-IS router.
ExtremeXOS 15.7 Release Notes
30,000
20,000
20,000
25,000
120,000
50,000
25,000
25,000
20,000
75
Limits
Table 2: Supported Limits (Continued)
Metric
Product
Limit
IS-IS IPv6 L1 routes in an L1
router—recommended maximum
number of IS-IS Level 1 routes in a
Level 1 IS-IS router.
BlackDiamond 8000 series
BlackDiamond X8 series
BlackDiamond BDX X8-100G4X-XL
modules
BlackDiamond 8900 xl-series
Summit X480
Summit X460, X460-G2, X670, X670G2, X770, E4G-400
10,000
10,000
40,000
BlackDiamond 8000 series
BlackDiamond X8 series
BlackDiamond X8 BDX X8-100G4X-XL
modules
BlackDiamond 8900 xl-series
Summit X480
Summit X460, X460-G2, X670, X670G2, X770
E4G-200, E4G-400
10,000
10,000
40,000
40,000
15,000
10,000
BlackDiamond 8000 series
BlackDiamond X8 series
BlackDiamond BDX X8-100G4X-XL
modules
BlackDiamond 8900 xl-series
Summit X480
Summit X460, X460-G2, X670, X670G2, X770, E4G-400
10,000
10,000
15,000
BlackDiamond 8000 series
BlackDiamond X8 series
BlackDiamond BDX X8-100G4X-XL
modules
BlackDiamond 8900 xl-series
Summit X480
Summit X460, X460-G2, X670, X670G2. X770
E4G-200, E4G-400
20,000
20,000
60,000
60,000
40,000
20,000
IS-IS IPv6 L2 routes—
recommended maximum number
of IS-IS Level 2 routes.
IS-IS IPv6 L1 routes in an L1/L2
router—recommended maximum
number of IS-IS Level 1 routes in a
L1/l2 router.
IS-IS IPv4/IPv6 L1 routes in an L1
router—recommended maximum
number of IS-IS Level 1 routes in a
Level 1 IS-IS router. The numbers
documented are based on 50%
IPv4 routes and 50% IPv6 routes.
ExtremeXOS 15.7 Release Notes
40,000
25,000
10,000
10,000
15,000
15,000
10,000
20,000
76
Limits
Table 2: Supported Limits (Continued)
Metric
Product
Limit
IS-IS IPv4/IPv6 L2 routes in an L2
router—recommended maximum
number of IS-IS Level 2 routes in
a Level 2 IS-IS router. The
numbers documented are based
on 50% IPv4 routes and 50% IPv6
routes.
BlackDiamond 8000 series
BlackDiamond X8 series
BlackDiamond BDX X8-100G4X-XL
modules
BlackDiamond 8900 xl-series
Summit X480
Summit X460,X460-G2, X670, X670-G2,
X770
E4G-200, E4G-400
20,000
20,000
60,000
IS-IS IPv4/IPv6 L1 routes in an L1/
L2 router—recommended
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.
BlackDiamond 8000 series
BlackDiamond X8 series
BlackDiamond 8900 xl-series
Summit X460, X460-G2, X480, X670,
X670-G2, X770
E4G-200, E4G-400
20,000
20,000
20,000
20,000
Jumbo frames—maximum size
supported for jumbo frames,
including the CRC.
All platforms
9,216
L2 VPN: VCCV (pseudowire Virtual
Circuit Connectivity Verification)
VPNs per switch—maximum
number of VCCV enabled VPLS
VPNs.
All platforms, except Summit X440,
X430
16
L2 VPN: VPLS MAC addresses—
maximum number of MAC
addresses learned by a switch.
BlackDiamond 8900 xl-series
BlackDiamond 8900-40G6X-xm
BlackDiamond X8 a-series modules
BlackDiamond X8-100G4X modules
BlackDiamond BDX X8-100G4X-XL
modules
E4G-200, E4G-400
Summit X460
Summit X480
Summit X670, Summit X670V-48t,
Summit X770
Summit X480 (40G VIM)
Summit X670-G2
Summit X460-G2
512,000
128,000
128,000
384,000
1,048,576
ExtremeXOS 15.7 Release Notes
60,000
40,000
20,000
20,000
20,000
g
32,000
32,000
512,000
128,000
121,000
140,000
55,000
77
Limits
Table 2: Supported Limits (Continued)
Metric
Product
Limit
L2 VPN: VPLS VPNs—maximum
number of VPLS virtual private
networks per switch.
BlackDiamond 8900 xl-series
BlackDiamond 8900-40G6x-xm
BlackDiamond X8 series
E4G-200, E4G-400
Summit X460, X460-G2, X480, X670,
X670V-48t, X480 (40G VIM), X770,
X670-G2
1,023
1,023
1,023
1,023
1,023
L2 VPN: VPLS peers—maximum
number of VPLS peers per VPLS
instance.
BlackDiamond 8900 xl-series
BlackDiamond 8900-40G6x-xm
BlackDiamond X8 series
Summit X770, X670-G2, X670v-48t,
X480, X460-G2
Summit X670, X460
E4G-200, E4G-400
64
64
64
64
L2 VPN: LDP pseudowires—
maximum number of pseudowires
per switch.
BlackDiamond 8900 xl-series
BlackDiamond 8900-40G6X-xm
BlackDiamond X8 series
E4G-200, E4G-400
Summit X770
Summit X670-G2, X670v-48t, X480
Summit X670
Summit X460-G2
Summit X460
7,000
3,000
7,000
1,000
7,800
7,000
3,000
7,116
1,000
L2 VPN: static pseudowires—
maximum number of static
pseudowires per switch.
BlackDiamond 8900 xl-series,
BlackDiamond X8
BlackDiamond 8900-40G6X-xm
Summit X460, X480, X670V-48t
Summit X770
Summit X480-40G, Summit X670
Summit X670-G2, X460-G2
E4G-200
E4G-400
7,116
3,020
7,116
15,308
3,020
7,000
2,764
6,860
ExtremeXOS 15.7 Release Notes
32
32
78
Limits
Table 2: Supported Limits (Continued)
Metric
Product
Limit
L2 VPN: Virtual Private Wire
Service (VPWS) VPNs—maximum
number of virtual private
networks per switch.
Summit X460
Summit X480, X770
Summit X480-40G VIM
Summit X670
Summit X670V-48t
BlackDiamond 8900 xl-series
BlackDiamond 8900-40G6X-xm
BlackDiamond X8 series
Summit X670-G2
Summit X460-G2
E4G-200, E4G-400
1,000
4,000
2,047
2,047
4,000
4,000
2,047
4,000
4,090
1,023
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
BlackDiamond X8 series switches
E4G-200, E4G-400
Summit X480, X460
Summit X670, X670V
Summit X440
Summit X770, X670-G2
Summit X460-G2
Summit X430
2,000
BlackDiamond 8800 e-series switches
BlackDiamond 8800 xl- and c-series
switches
BlackDiamond 8800 xm-series switches
BlackDiamond X8, Summit X670,
X670V
E4G-200 and E4G-400 cell site routers,
Summit X460
Summit X440
Summit X770, X670-G2
Summit X460-G2
Summit X480
N/A
8,000
Layer-2 IPMC forwarding caches—
(IGMP/MLD/PIM snooping) in
mixed-mode.
NOTE: IPv6 and IPv4 L2 IPMC
scaling is the same for this mode.
ExtremeXOS 15.7 Release Notes
8,000
15,000
15,000
8,000
8,000
15,000
4,000
77,500k
24,576q
5,000
15,000
15,000
8,000
4,000
77,500k
24,576q
8,000
79
Limits
Table 2: Supported Limits (Continued)
Metric
Product
Limit
Layer-3 IPMC forwarding caches—
(PIM, MVR, PVLAN) in mixedmode.i
BlackDiamond 8800 e-series switches
BlackDiamond 8800 xl- and c-series
switches
BlackDiamond 8800 xm-series switches
BlackDiamond X8 a-series modules
BlackDiamond X8-100G4X and modules
E4G-200 cell site routers, Summit X670
E4G-400 cell site routers, Summit
X460, X480, X670V
Summit X440
Summit X770, X670-G2
Summit X460-G2
N/A
6,000
NOTE: IPv6 L3 IPMC scaling is
50% of these limits in this mode.
Load sharing—maximum number
of loadsharing groups.
NOTE: The actual number of loadsharing groups that can be
configured is limited by the
number of physical ports present
in the switch or SummitStack.
3,000
6,000
64,000
3,000
6,000
192
77,500k
21,000k
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
With distributed IP ARP mode off
(default)
128
With distributed IP ARP mode on
64
BlackDiamond 8000 series with 8900-40G6X-xm with L2,
L3 or L3_L4 algorithm configured for any group
With distributed IP ARP mode off
(default)
127
With distributed IP ARP mode on
63
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
With distributed IP ARP mode off
(default)
384
With distributed IP ARP mode on
384
BlackDiamond X8 series with L2, L3 or L3_L4 algorithm
configured for any group
ExtremeXOS 15.7 Release Notes
With distributed IP ARP mode off
(default)
127
With distributed IP ARP mode on
63
80
Limits
Table 2: Supported Limits (Continued)
Metric
Product
Limit
Load sharing—maximum number
of ports per load-sharing group.
BlackDiamond X8 series
64
Summit X460-G2 (standalone)
32
Summit X670 (standalone)
32 *
16 **
Summit X670 (stacked)
Summit X670-G2 (stacked)
64 *
16 **
Summit X770 (standalone)
Summit X670-G2 (standalone)
Summit X460-G2 (standalone
32
Summit X770 (stacked)
Summit X670-G2 (stacked)
Summit X460-G2 (stacked)
64
All other Summit series, SummitStacks,
E4G cell site routers, and BlackDiamond
8000 series switches
8
Logged messages—maximum
number of messages logged
locally on the system.
All platforms
20,000
MAC address learning rate—
E4G-200
22 msec
MAC-based security—maximum
number of MAC-based security
policies.
All platforms
1,024
MAC Locking—Maximum number
of MAC locking stations that can
be learned on a port.
All platforms
64
(static MAC
locking stations)
600
(first arrival MAC
locking stations)
NOTE:
For custom algorithm
*For L2 and L3 algorithms
NOTE: For a mix of Summit X770
and Summit X670 series switches
in a stack, the limits are the
Summit X670 limits.
hardware learning rate
ExtremeXOS 15.7 Release Notes
81
Limits
Table 2: Supported Limits (Continued)
Metric
Product
Limit
Maximum mirroring instances
All platforms
16
(including
default mirroring
instance)
BlackDiamond 8000 series
BlackDiamond X8 series
All Summit series
E4G cell site routers
128
128
128
128
BlackDiamond 8000 series
BlackDiamond X8 series
All Summit series
E4G cell site routers
128
128
128
128
Mirroring, one-to-many (monitor
port)—maximum number of oneto-many monitor ports.
All platforms
16
MLAG ports—maximum number
of MLAG ports allowed.
BlackDiamond 8000 series
BlackDiamond X8 series
All Summit series, except X430
E4G cell site routers
768
768
768
768
MLAG peers—maximum number
of MLAG peers allowed.
All platforms, except Summit X430
2
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
NOTE: The Summit X430 can only
support one egress mirroring
instance.
Mirroring (filters)—maximum
number of mirroring filters.
NOTE: This is the number of filters
across all the active mirroring
instances.
Mirroring, one-to-many (filters)—
maximum number of one-tomany mirroring filters.
NOTE: This is the no. of filters
across all the active mirroring
instances
ExtremeXOS 15.7 Release Notes
82
Limits
Table 2: Supported Limits (Continued)
Metric
Product
Limit
MPLS RSVP-TE interfaces—
maximum number of interfaces.
All platforms, except Summit X440 and
X430
32
MPLS RSVP-TE ingress LSPs—
maximum number of ingress
LSPs.
All platforms, except Summit X440 and
X430
2,000
MPLS RSVP-TE egress LSPs—
maximum number of egress
LSPs.
All platforms, except Summit X440 and
X430
2,000
MPLS RSVP-TE transit LSPs—
maximum number of transit LSPs.
All platforms, except Summit X440 and
X430
2,000
MPLS RSVP-TE paths—maximum
number of paths.
All platforms, except Summit X440,
X430, and X670-G2
Summit X670-G2
1,000
All platforms, except Summit X440,
X430, and X670-G2
Summit X670-G2
1,000
MPLS RSVP-TE EROs—maximum
number of EROs per path.
All platforms, except Summit X440 and
X430
64
MPLS RSVP-TE fast reroute—MPLS
RSVP-TE fast reroute (FRR)
switching time.
E4G-200
50 msec
MPLS LDP peers—maximum
number of MPLS LDP peers per
switch.
Summit X460, Summit X670
Summit X480, Summit X480 (40G
VIM), X670V-48t, X770, X670v-48t
BlackDiamond 8900 xl-series
BlackDiamond 8900-40G6x-xm
BlackDiamond X8 series
Summit X670-G2, X460-G2
E4G-400, E4G-200
32
64
BlackDiamond 8900 xl-series
BlackDiamond 8900-40G6x-xm
BlackDiamond X8 series
E4G-200, E4G-400
Summit X460, X480, X670, X460-G2
Summit X670V-48t, X480 (40G VIM),
X770, X670-G2
50
64
50
50
50
MPLS RSVP-TE profiles—
maximum number of profiles.
MPLS LDP adjacencies—maximum
number of MPLS LDP adjacencies
per switch.
ExtremeXOS 15.7 Release Notes
2,000
2,000
64
64
64
128
32
64
83
Limits
Table 2: Supported Limits (Continued)
Metric
Product
Limit
MPLS LDP ingress LSPs—
maximum number of MPLS LSPs
that can originate from a switch.
BlackDiamond 8900 xl-series
BlackDiamond 8900-40G6X-xm
BlackDiamond X8 series
E4G-200
E4G-400
Summit X460, X480
Summit X670, X670V-48t, X480 (40G
VIM), X770
Summit X670-G2
Summit X460-G2
4,000
2,048
2,048
2,048
4,000
4,000
2,048
Summit X460, X670
Summit X480, X670V-48t, X770
Summit X670-G2, X460-G2
BlackDiamond 8900 xl-series
BlackDiamond 8900-40G6x-xm
BlackDiamond X8 series
E4G-200, E4G-200
32
64
MPLS LDP Sessions—maximum
number of MPLS LDP sessions.
BlackDiamond 8900 xl-series
BlackDiamond 8900-40G6x-xm
BlackDiamond X8 series
Summit X770, X670v-48t, X480
Summit X670-G2, X460-G2
Summit X670, X460
E4G-200, E4G-400
64
64
64
64
128
32
32
MPLS LDP transit LSPs—maximum
number of MPLS transit LSPs per
switch.
BlackDiamond 8900 xl-series
BlackDiamond 8900-40G6X-xm
BlackDiamond X8 series
E4G-200
E4G-400
Summit X460, X480, X770, X670V-48t,
X670-G2, X460-G2
Summit X670, X480 (VIM3-40G4x)
4,000
3,000
4,000
2,700
4,000
4,000
MPLS LDP-enabled interfaces—
maximum number of MPLS LDP
configured interfaces per switch.
ExtremeXOS 15.7 Release Notes
2,048
4,000
128
64
64
64
32
3,000
84
Limits
Table 2: Supported Limits (Continued)
Metric
Product
Limit
MPLS LDP egress LSPs—maximum
number of MPLS egress LSPs that
can terminate on a switch.
BlackDiamond 8900 xl-series
BlackDiamond 8900-40G6X-xm
BlackDiamond X8 series
E4G-200
E4G-400
Summit X460, X480, X670V-48t
Summit X670, X480 (VIM3-40G4x)
Summit X770
Summit X670-G2, X460-G2
7,000
3,000
7,000
2,700
6,700
7,000
3,000
8,000
4,000
MPLS static egress LSPs—
maximum number of static
egress LSPs.
BlackDiamond 8900 xl-series,
BlackDiamond X8
BlackDiamond 8900-40G
Summit X460, X480, X670V-48t, X460G2
Summit X480 (VIM3-40G4x), X670
Summit X770
Summit X670-G2
E4G-200
E4G-400
MPLS static ingress LSPs—
maximum number of static
ingress LSPs.
MPLS static transit LSPs—
maximum number of static transit
LSPs
ExtremeXOS 15.7 Release Notes
7,116
3,020
7,116
3,020
8,000
15,308
2,700
6,860
BlackDiamond 8900 xl-series
BlackDiamond 8900-40G
BlackDiamond X8
Summit X460, X480, X460-G2
Summit x480-40G, X670, x670V-48t,
X770, X670-G2
E4G-200
E4G-400
4,000
2,048
2,048
4,000
BlackDiamond 8900 xl-series
BlackDiamond 8900-40G
BlackDiamond X8
Summit X460, X480, X670V-48t, X770,
X670-G2, X460-G2
Summit X480-40G, X670
E4G-200
E4G-400
4,000
3,000
4,000
4,000
2,048
2,048
4,000
3,000
2,700
4,000
85
Limits
Table 2: Supported Limits (Continued)
Metric
Product
Limit
MSDP active peers—maximum
number of active MSDP peers.
BlackDiamond 8000 series
BlackDiamond X8 series
BlackDiamond 8900 series
Summit X460, X480, X670, E4G-400,
X670-G2, X460-G2
Summit X770
32
64
64
16
BlackDiamond 8000 series
BlackDiamond X8 series
BlackDiamond 8900 series
Summit X460, X480, X670, E4G-400
Summit X670-G2, X460-G2, X770
16,000
16,000
16,000
8,000
MSDP SA cache entries—
maximum number of entries in
SA cache.
64
14,000
MSDP maximum mesh groups—
maximum number of MSDP mesh
groups.
Multicast listener discovery (MLD)
IPv6 multicast data sender—
maximum number of IPv6
multicast streams supported on a
switchr i
NOTE: Assumes source-groupvlan mode.
For additional limits, see:
• Layer-2 IPMC forwarding
caches—(IGMP/MLD/PIM
snooping) in mac-vlan mode.
on page 79
• Layer-2 IPMC forwarding
caches— (IGMP/MLD/PIM
snooping) in mixed-mode. on
page 79
ExtremeXOS 15.7 Release Notes
BlackDiamond 8000 series
BlackDiamond X8 series
BlackDiamond 8900 series
Summit X460, X480, X670, E4G-400,
X460-G2
Summit X770, X670-G2
8
16
16
4
BlackDiamond 8800 c-series
BlackDiamond 8800 e-series
BlackDiamond 8900 c-series
BlackDiamond 8900-40G6X-xm
BlackDiamond 8900 xl-series
BlackDiamond X8 series
E4G-200
E4G-400
Summit X440
Summit X460, X460-G2
Summit X480
Summit X670
Summit X770, X670-G2
1,000
250
1,000
1,000
3,000
3,000
1,500
3,000
90
3,000
3,000
1,500
14,000
16
86
Limits
Table 2: Supported Limits (Continued)
Metric
Product
Limit
Multicast listener discovery (MLD)
snooping per-VLAN filters—
maximum number of VLANs
supported in per-VLAN MLD
snooping mode.
BlackDiamond e-series
BlackDiamond 8800 c-series
BlackDiamond 8900 c-series
BlackDiamond 8900 xl-series
BlackDiamond 8900-40G6X-xm
BlackDiamond X8 a-series modules
BlackDiamond X8 100G4X and BDX X8100G4X-XL modules
E4G-400, Summit X460, X460-G2
Summit X480
Summit X440
Summit X670, E4G-200
Summit X770, X670-G2
250
1,000
500
2,000
500
500
2,000
BlackDiamond 8800 c-series
BlackDiamond xl-series
BlackDiamond X8 Series
Summit X440
Summit X460, X460-G2, X480, X670,
E4G-400
Summit X770, X670-G2
500
1,500
1,500
750
BlackDiamond 8800 series
BlackDiamond X8 series
Summit X440
Summit X460, X480, X670, E4G-400,
X460-G2
Summit X770, X670-G2
10,000
10,000
5,000
BlackDiamond 8800 c-series
BlackDiamond xl series
BlackDiamond X8 series
Summit X440, SummitStack
Summit X460, X480, X670, E4G-400,
X460-G2
Summit X770, X670-G2
500
2,500
2,000
1,000
BlackDiamond 8800 series
BlackDiamond xl series
Summit X440, SummitStack
Summit X460, X480, X670, E4G-400,
X460-G2
Summit X770, X670-G2
10,000
10,000
5,000
Multicast listener discovery
(MLD)v1 subscribers—maximum
number of MLDv1 subscribers per
ports
Multicast listener discovery
(MLD)v1 subscribers—maximum
number of MLDv1 subscribers per
switchs
Multicast listener discovery
(MLD)v2 subscribers—maximum
number of MLDv2 subscribers per
ports
Multicast listener discovery
(MLD)v2 subscribers—maximum
number of MLDv2 subscribers per
switchs
ExtremeXOS 15.7 Release Notes
1,000
2,000
250
500
1,200
1,500
4,000
10,000
30,000
2,000
4,000
10,000
30,000
87
Limits
Table 2: Supported Limits (Continued)
Metric
Product
Limit
Multicast listener discovery
(MLD)v2 maximum source per
group—maximum number of
source addresses per group
All platforms, except Summit X430
200
Multicast VLAN registration
(MVR)—maximum number of
MVR senders per switch (IP
multicast compression disabled).
BlackDiamond 8800 c-series
BlackDiamond 8000 e-series
BlackDiamond 8900 series
8900-10G24X-c modules
8900-G96T-c modules
8900 xl-series
8900-40G6X-xm
BlackDiamond X8 a-series modules
BlackDiamond X8-100G4X and BDX X8100G4X-XL modules
E4G-200
E4G-400
Summit X440
Summit X460, X460-G2, X480
Summit X670
VIM4-40G4x
Summit X770, X670-G2
2,048h
500i
BlackDiamond 8800 c-series
BlackDiamond 8000 e-series
BlackDiamond 8900 c-series
BlackDiamond 8900 xl-series
BlackDiamond X8 a-series modules
BlackDiamond X8-100G4X and BDX X8100G4X-XL modules
8900-40G6X-xm module
Summit X440
Summit X460, X460-G2, E4G-400
Summit X480
Summit X670
VIM4-40G4x
Summit X770, X670-G2
6,000i
500i
6,000i
12,000b
6,000i
59,000
BlackDiamond 8000 series (clients per
module/per system)
BlackDiamond X8 series
Summit series
1,024
NOTE: Assumes source-groupvlan mode.
Multicast VLAN registration
(MVR)—maximum number of
MVR senders per switch (IP
multicast compression enabled).
NOTE: Assumes source-groupvlan mode.
For additional limits, see:
Layer-3 IPMC forwarding caches—
(PIM, MVR, PVLAN) in mixedmode.i on page 80
Network login—maximum number
of clients being authenticated on
MAC-based VLAN enabled ports.
ExtremeXOS 15.7 Release Notes
2,048h
4,096h
4,096h
3,000i
4,096
4,096
2,048
500i
1,024
2,048
3,000i
4,096
3,000i
192i
6,000i
12,000b
3,000i
66,500
1,024
1,024
88
Limits
Table 2: Supported Limits (Continued)
Metric
Product
Limit
Network login—maximum number
of dynamic VLANs.
All platforms
2,000
Network login VLAN VSAs—
maximum number of VLANs a
client can be authenticated on at
any given time.
All platforms
10
OSPFv2/v3 ECMP—maximum
number of equal cost multipath
OSPFv2 and OSPFv3.
All platforms, except Summit X440,
X430, and E4G-200)
E4G-200
BlackDiamond 8800 G48Te2 (for IPv6)
16
OSPFv2 areas—as an ABR, how
many OSPF areas are supported
within the same switch.
All platforms (except X430, X440)
8
OSPFv2 external routes—
recommended maximum number
of external routes contained in an
OSPF LSDB.
BlackDiamond 8000 series
BlackDiamond 8900 xl-series
BlackDiamond X8 series
BlackDiamond BDX X8-100G4X-XL
modules
Summit X460, X670, X770, X670-G2,
X460-G2
Summit X480
E4G-400
E4G-200
20,000
130,000
20,000
130,000
BlackDiamond 8000 series
BlackDiamond 8900 xl-series
BlackDiamond X8 series
Summit X460, X670, X670-G2, X460G2
E4G-400
Summit X480, X770
7,000
7,000
7,000
2,000
OSPFv2 inter- or intra-area
routes—recommended maximum
number of inter- or intra-area
routes contained in an OSPF
LSDB with one ABR in OSPF
domain.
OSPFv2 interfaces—
recommended maximum number
of OSPF interfaces on a switch.
ExtremeXOS 15.7 Release Notes
5,000
130,000
5,000
5,000
2,000
7,000
NOTE: Active interfaces limit, with
Advanced Edge license.
(See below for Core license limits.)
All platforms (except X430)
OSPFv2 links—maximum number
of links in the router LSA.
8
N/A
4
All platforms (except X430 and X440)
with Core license or higher (active
interfaces only)
400
All platforms, except Summit X770 and
X430
Summit X770
400
419
89
Limits
Table 2: Supported Limits (Continued)
Metric
Product
Limit
OSPFv2 neighbors—maximum
number of supported OSPF
adjacencies.
BlackDiamond 8000 series
BlackDiamond 8900 xl-series
BlackDiamond X8 Series
Summit X460, X670, X770, X440,
X670-G2, X460-G2
Summit X480
E4G-400, E4G-200
128
255
255
128
255
128
OSPFv2 routers in a single area—
recommended maximum number
of routers in a single OSPF area.
BlackDiamond 8000 series
BlackDiamond 8900 xl-series
BlackDiamond X8 series
Summit X460, X670, X770, X670-G2,
X460-G2
Summit X480
E4G-400
100
200
100
50
OSPFv2 virtual links—maximum
number of supported OSPF
virtual links.
All platforms (except X430 and X440)
with Core license or higher
32
OSPFv3 areas—as an ABR, the
maximum number of supported
OSPFv3 areas.
All platforms (except X430 and X440)
with Core license or higher
16
OSPFv3 external routes—
recommended maximum number
of external routes.
BlackDiamond 8000 series
BlackDiamond X8 series
BlackDiamond BDX X8-100G4X-XL
modules
BlackDiamond 8900 xl-series
Summit X460, X670, X770, X670-G2,
X460-G2
Summit X480
E4G-400
10,000
10,000
60,000
BlackDiamond 8000 series
BlackDiamond X8 series
BlackDiamond 8900 xl-series
Summit X460, X670, X770, X670-G2,
X460-G2
Summit X480
E4G-400
6,000
6,000
6,000
3,000
OSPFv3 inter- or intra-area
routes—recommended maximum
number of inter- or intra-area
routes.
ExtremeXOS 15.7 Release Notes
200
50
60,000
10,000
60,000
10,000
6,000
3,000
90
Limits
Table 2: Supported Limits (Continued)
Metric
Product
OSPFv3 interfaces—maximum
number of OSPFv3 interfaces.
NOTE: Active interfaces only, with
Advanced Edge license.
(See below for Core license limits.)
All platforms (except X430)
Limit
4
NOTE: With Core license or higher.
(See above for Advanced Edge license
limits.)
BlackDiamond 8000 series
BlackDiamond X8 series
BlackDiamond 8900 xl-series
Summit X460, X670, X770
Summit X480
Summit X670-G2, X460-G2
E4G-200, E4G-400
256
256
384
128
384
256
256
BlackDiamond 8000 series
BlackDiamond X8 series
BlackDiamond 8900 xl-series
Summit X460, X670, X770, X670-G2,
X460-G2
Summit X480
E4G-400
64
64
128
64
OSPFv3 virtual links—maximum
number of OSPFv3 virtual links
supported.
All platforms (except X430 and X440)
with Core license or higher
16
PIM IPv4 snooping—maximum
number of (S,G) entries
programmed in the hardware (IP
multicast compression disabled).
BlackDiamond 8800 c-series
BlackDiamond 8000 e-series
BlackDiamond 8900 series
8900-10G24X-c modules
8900-G96T-c modules
8900 xl-series
8900-40G6X-xm
BlackDiamond X8 a-series modules
BlackDiamond X8-100G4X andBDX X8100G4X-XL modules
E4G-200
E4G-400
Summit X440
Summit X460
Summit X480, X460-G2, X770, X670G2
Summit X670
2,048h
500h
OSPFv3 neighbors—maximum
number of OSPFv3 neighbors.
NOTE: Assumes source-groupvlan mode.
ExtremeXOS 15.7 Release Notes
128
64
2,048h
4,096h
4,096h
3,000i
4,096
4,096
2,048
2,048
64
2,048
4,096
3,000i
91
Limits
Table 2: Supported Limits (Continued)
Metric
Product
Limit
PIM IPv4 snooping—maximum
number of (S,G) entries
programmed in the hardware (IP
multicast compression enabled).
BlackDiamond 8800 c-series
BlackDiamond 8000 e-series
BlackDiamond 8900 c-series
BlackDiamond 8900 xl-series
BlackDiamond X8 a-series modules
BlackDiamond X8-100G4X and BDX X8100G4X-XL modules
E4G-200
E4G-400
8900-40G6X-xm
Summit X440
Summit X480
Summit X460
Summit X670
Summit X770, X670-G2
Summit X460-G2
6,000i
500i
6,000i
12,000b
6,000i
59,000i
BlackDiamond 8800 c-series
BlackDiamond 8000 e-series
BlackDiamond 8900 series
8900-10G24X-c modules
8900-G96T-c modules
8900 xl-series
8900-40G6X-xm
BlackDiamond X8 a-series modules
BlackDiamond X8-100G4X and BDX X8100G4X-XL modules
E4G-200
E4G-400
Summit X440
Summit X480, X670-G2, X460-G2
Summit X460
Summit X670
Summit X770
2,048h
500i
NOTE: Assumes source-groupvlan mode.
For additional limits, see:
• Layer-2 IPMC forwarding
caches—(IGMP/MLD/PIM
snooping) in mac-vlan mode.
on page 79
• Layer-2 IPMC forwarding
caches— (IGMP/MLD/PIM
snooping) in mixed-mode. on
page 79
PIM IPv4—maximum routes—
maximum number of (S,G) entries
installed in the hardware (IP
multicast compression disabled).
NOTE: Assumes source-groupvlan mode.
ExtremeXOS 15.7 Release Notes
3,000i
6,000i
3,000i
192i
12,000b
6,000i
3,000i
66,500
21,000
2,048h
4,096h
4.096h
3,000i
4,094
4,096
2,048
2,048
64i
4,096
2,048
3,000i
4,096
92
Limits
Table 2: Supported Limits (Continued)
Metric
Product
Limit
PIM IPv4—maximum routes—
maximum number of (S,G) entries
installed in the hardware (IP
multicast compression enabled).
BlackDiamond 8800 c-series
BlackDiamond 8000 e-series
BlackDiamond 8900 c-series
BlackDiamond 8900 xl-series
BlackDiamond X8 a-series modules
BlackDiamond X8-100G4X and BDX X8100G4X-XL modules
E4G-200
E4G-400
8900-40G6X-xm modules
Summit X440
Summit X480
Summit X460
Summit X670
Summit X770, X670-G2
Summit X460-G2
6,000i
500i
6,000i
12,000b
6,000f
59,000f
BlackDiamond 8800 c-series
BlackDiamond 8000 e-series
BlackDiamond 8900 series
8900-10G24X-c modules
8900-G96T-c modules
8900 xl-series
8900-40G6X-xm
BlackDiamond X8 a-series modules
BlackDiamond X8-100G4X and BDX X8100G4X-XL modules
E4G-200
E4G-400
Summit X440
Summit X480, X670-G2, X460-G2
Summit X460
Summit X670
Summit X770
2,048h
500i
NOTE: Assumes source-groupvlan mode.
For additional limits, see:
Layer-3 IPMC forwarding caches—
(PIM, MVR, PVLAN) in mixedmode.i on page 80
PIM IPv4-SSM (maximum SSM
routes)—maximum number of
(S,G) entries installed in the
hardware with PIM SSM
configuration (IP multicast
compression disabled).
NOTE: Assumes source-groupvlan mode.
ExtremeXOS 15.7 Release Notes
3,000i
6,000i
3,000i
192
12,000b
6,000i
3,000i
66,500
21,000
2,048h
4,096h
15,000
3,000i
4,094
4,094
2,048
2,048
64
4,096
2,048
3,000i
4,096
93
Limits
Table 2: Supported Limits (Continued)
Metric
Product
Limit
PIM IPv4-SSM (maximum SSM
routes)—maximum number of
(S,G) entries installed in the
hardware with PIM SSM
configuration (IP multicast
compression enabled).
BlackDiamond 8800 c-series
BlackDiamond 8000 e-series
BlackDiamond 8900 c-series
BlackDiamond 8900 xl-series
BlackDiamond X8 a-series modules
BlackDiamond X8-100G4X and BDX X8100G4X-XL modules
E4G-200
E4G-400
8900-40G6X-xm
Summit X440
Summit X480
Summit X460
Summit X670
Summit X770, X670-G2
Summit X460-G2
6,000i
500i
6,000i
12,000b
6,000i
59,000i
BlackDiamond 8800 c-series
BlackDiamond 8800 e-series
BlackDiamond 8900 c-series
BlackDiamond 8900-40G6X-xm
BlackDiamond 8900 xl-series
BlackDiamond X8 a-series modules
BlackDiamond X8-100G4X and BDX X8100G4X-XL modules
E4G-200
E4G-400
Summit X440
Summit X460, X460-G2, X480
Summit X670
Summit X770, X670-G2
1,000
250
1,000
1,000
3,000
3,000
30,000e
PIM IPv4 (maximum interfaces)—
maximum number of PIM active
interfaces.
All platforms, except Summit X430 and
X440
Summit X440
512
PIM IPv4 (maximum interfaces)—
maximum number of PIM
snooping enabled interfaces.
All platforms, except Summit X430
512
PIM IPv4 Limits—maximum
number of multicast groups per
rendezvous point
All platforms, except Summit X430
180
NOTE: Assumes source-groupvlan mode.
For additional limits, see:
Layer-3 IPMC forwarding caches—
(PIM, MVR, PVLAN) in mixedmode.i on page 80
PIM IPv6 (maximum routes)—
maximum number of (S,G) entries
installed in the hardware.
NOTE: Assumes source-groupvlan mode.
ExtremeXOS 15.7 Release Notes
3,000i
6,000i
3,000i
192i
12,000b
6,000i
3,000i
66,500
21,000
1,500
3,000
90
3,000
1,500
30,000
253
94
Limits
Table 2: Supported Limits (Continued)
Metric
Product
Limit
PIM IPv4 Limits—maximum
number of multicast sources per
group
All platforms, except Summit X430
175
PIM IPv4 Limits—maximum
number of dynamic rendezvous
points per multicast group
All platforms, except Summit X430
145
PIM IPv4 Limits—static
rendezvous points
All platforms, except Summit X430
32
PIM IPv6 (maximum interfaces)—
maximum number of PIM active
interfaces
All platforms, except Summit X430
512
PIM IPv6 Limits—maximum
number of multicast group per
rendezvous point
All platforms, except Summit X430
70
PIM IPv6 Limits—maximum
number of multicast sources per
group
All platforms, except Summit X430
43
PIM IPv6 Limits—maximum
number of dynamic rendezvous
points per multicast group
All platforms, except Summit X430
64
PIM IPv6 Limits—maximum
number of secondary address per
interface
All platforms, except Summit X430
70
PIM IPv6 Limits—static
rendezvous points
All platforms, except the Summit X430
32
Policy-based routing (PBR)
redundancy—maximum number
of flow-redirects.
All platforms
256t
Policy-based routing (PBR)
redundancy—maximum number
of next hops per each flow-direct.
All platforms
32t
Port-specific VLAN tags—
maximum number of port-specific
VLAN tags
All platforms
1,023
ExtremeXOS 15.7 Release Notes
95
Limits
Table 2: Supported Limits (Continued)
Metric
Product
Limit
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, X670-G2
Summit X460-G2
E4G-400
E4G-200
8,090
Private VLANs—maximum
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
BlackDiamond X8 series
Summit X770
Summit X670-G2, X670v-48t
Summit X670
Summit X480
Summit X460-G2, X460
Summit X440
Summit X430
E4G-200
E4G-400
383
767
103
63
47
23
53
25
27
11
33
Private VLANs—maximum
number of private VLANs with an
IP address on the network VLAN.
Summit X770, X670-G2, X460-G2
Summit X670, X480, X460, X460, X480
Summit X440
E4G-200, E4G-400
1,024
512
127
512
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.
ExtremeXOS 15.7 Release Notes
3,800
7,200
3,400
3,600
7,200
6,400
4,000
3,400
3,800
96
Limits
Table 2: Supported Limits (Continued)
Metric
Product
Limit
Private VLANs—maximum
number of private VLANs in an
L2-only environment.
BlackDiamond 8800 c-, e-series
BlackDiamond 8900 series
BlackDiamond X8 series
E4G-200
E4G-400
Summit X440
Summit X480
Summit X670
Summit X460
Summit X770, X670-G2, X460-G2
384
2,046
2,046
597
1,280
127
597
597
820
1,280
PTP/1588v2 Clock Ports
Summit X770, X460-G2, X670-G2, and
E4G-200, E4G-400 cell site routers
32 for boundary
clock
1 for ordinary
clock
PTP/1588v2 Clock Instances
Summit X770, X670-G2, X460-G2, and
E4G-200, E4G-400 cell site routers
2 combinations:
• Transparent
clock +
ordinary clock
• Transparent
clock +
boundary
clock
PTP/1588v2 Unicast Static Slaves
Summit X770, X670-G2, X460-G2, and
E4G-200, E4G-400 cell site routers
40 entries per
clock port
PTP/1588v2 Unicast Static Masters
Summit X770, X670-G2, X460-G2, and
E4G-200, E4G-400 cell site routers
10 entries per
clock type
Route policies—suggested
maximum number of lines in a
route policy file.
All platforms
10,000
RIP Learned Routes—maximum
number of RIP routes supported
without aggregation.
All platforms, except Summit X430
10,000
RIP neighbors—maximum number
of RIP neighbors.
E4G-200
256
ExtremeXOS 15.7 Release Notes
97
Limits
Table 2: Supported Limits (Continued)
Metric
Product
Limit
RIP interfaces on a single router—
recommended maximum number
of RIP routed interfaces on a
switch.
BlackDiamond 8000 series
BlackDiamond X8 series
BlackDiamond 8900 xl-series
Summit X440
Summit X460, X670-G2, X460-G2
Summit X480
Summit X670, X770
E4G-400
256
256
384
128
256
384
256
256
RIPng learned routes—maximum
number of RIPng routes.
BlackDiamond 8000 series
BlackDiamond X8 series
BlackDiamond 8900 xl-series
Summit X480
Summit X460, X670, X670-G2, X460G2, X770
E4G-200
3,000
3,000
5,000
5,000
3,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
Spanning Tree PVST+—maximum
number of port mode PVST
domains.
BlackDiamond X8 and 8900 series
switches
Summit X670, X770, X670-G2
Summit X460, X480, X440, X460-G2
Summit X430
E4G-400
256
All platforms (except Summit X430 and
Summit X440)
Summit X440
Summit X430
64
NOTE:
• Maximum of 10 active ports
per PVST domain when 256
PVST domains are configured.
• Maximum of 7 active ports per
3,000
32
16
256
128
50
128
PVST domain when 128 PVST
domains are configured.
Spanning Tree—maximum
number of multiple spanning tree
instances (MSTI) domains.
ExtremeXOS 15.7 Release Notes
32
5
98
Limits
Table 2: Supported Limits (Continued)
Metric
Product
Limit
Spanning Tree—maximum
number of VLANs per MSTI.
BlackDiamond X8
BlackDiamond 8800
BlackDiamond 8900 MSM 128/XL
Summit X770, X670-G2, X670v-48t,
X670
Summit X480, X460-G2, X460
E4G-200
E4G-400
Summit X440
Summit X430
500
500
500
500
BlackDiamond X8
BlackDiamond 8800
BlackDiamond 8900 MSM 128/XL
Summit X770
Summit X670-G2, X670v-48t, X670,
X480
Summit X460-G2, X460
E4G-200
E4G-400
Summit X440
Summit X430
1,000
1,000
1,000
1,024
1,000
Spanning Tree (802.1d domains)—
maximum number of 802.1d
domains per port.
All platforms
1
Spanning Tree (number of
ports)—maximum number of
ports including all Spanning Tree
domains.
All platforms (except Summit X430 and
Summit X440)
Summit X440
Summit X430
4,096
Spanning Tree (maximum
VLANs)—maximum number of
STP-protected VLANs (dot1d and
dot1w).
BlackDiamond X8
BlackDiamond 8800
BlackDiamond 8900 MSM 128/XL
Summit X770
Summit X670-G2, X670v-48t, X670,
X480
Summit X460-G2, X460
E4G-200
E4G-400
Summit X440
Summit X430
1,024
1,024
1,024
1,024
560
NOTE: Maximum number of 10
active ports per VLAN when all
500 VLANs are in one MSTI.
Spanning Tree—maximum
number of VLANs on all MSTP
instances.
ExtremeXOS 15.7 Release Notes
600
500
600
250
100
1,024
1,000
1,024
500
200
2,048
1,024
600
500
600
500
128
99
Limits
Table 2: Supported Limits (Continued)
Metric
Product
Limit
SSH (number of sessions)—
maximum number of
simultaneous SSH sessions.
All platforms
8
Static MAC multicast FDB
entries—maximum number of
permanent multicast MAC entries
configured into the FDB.
BlackDiamond 8000 c-, e-, xl-series
BlackDiamond X8 series
All Summits
E4G-200, E4G-400
1,024
Syslog servers—maximum
number of simultaneous syslog
servers that are supported.
All platforms
4
Telnet (number of sessions)—
maximum number of
simultaneous Telnet sessions.
All platforms
8
TRILL—trees rooted from switch
BlackDiamond X8
Summit X670, X770
1
1
TRILL—computed trees
BlackDiamond X8
Summit X670, X770
1
1
TRILL—TRILL VLANs
BlackDiamond X8
Summit X670, X770
4
4
TRILL—forwarding VLANs
BlackDiamond X8
Summit X670, X770
4,095
4,095
TRILL—forwarding ports
BlackDiamond X8
Summit X670, X770
All
All
TRILL—RBridge FDB entries
BlackDiamond X8
Summit X670
Summit X770
128,000
128,000
288,000
TRILL—ECMP RBridge next hops
BlackDiamond X8
Summit X670, X770
8
8
TRILL—neighbor adjacencies
BlackDiamond X8
Summit X670, X770
32
32
TRILL—nodes
BlackDiamond X8
Summit X670, X770
256
256
TRILL—links
BlackDiamond X8
Summit X670, X770
2,000
2,000
ExtremeXOS 15.7 Release Notes
1,024
1,024
100
Limits
Table 2: Supported Limits (Continued)
Metric
Product
Limit
Virtual routers—maximum
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
BlackDiamond X8 series
E4G-200, E4G-400
Summit X460, X460-G2, X480, X670,
X670-G2, X770
63
Virtual router forwarding (VRFs)—
maximum number of VRFs that
can be created on a switch.
All platforms, except Summit X440,
X430
960 *
Virtual router protocols per VR—
maximum number of routing
protocols per VR.
All platforms, except Summit X440,
X430
8
Virtual router protocols per
switch—maximum number of VR
protocols per switch.
All platforms, except Summit X440,
X430
64
VLAN aggregation—maximum
number of port-VLAN
combinations on any one
superVLAN and all of its
subVLANs.
All platforms (except Summit X430,
X440)
Summit X440, X430
1,000
VLANs—includes all VLANs.
All platforms
4,094
BlackDiamond 8800 xl-series only,
BlackDiamond X8 series
BlackDiamond X8 xl-series
Summit X460, X770, X480,
E4G-400, X670-G2, X460-G2
Summit X670, X670V-48t
E4G-400
E4G-200
1,023
Summit X460, X670, X670V-48t, X460G2, BlackDiamond 8800 xl-series only,
BlackDiamond X8, E4G-400, E4G-200
BlackDiamond X8 xl-series
Summit X770, X670-G2
Summit X480
4,096
63
63
63
NOTE: Subject to other system
limitations.
256
NOTE: ExtremeXOS supports only
4,092 user-configurable VLANs.
(VLAN 1 is the default VLAN, and
4,095 is the management VLAN,
and you may not configure them.)
VLANs—maximum number of
port-specific tag VLANs.
VLANs—maximum number of
port-specific tag VLAN ports
ExtremeXOS 15.7 Release Notes
4,093
4,093
1,023
4,093
2,047
32,767
8,192
16,383
101
Limits
Table 2: Supported Limits (Continued)
Metric
Product
Limit
VLANs (Layer 2)—maximum
number of Layer 2 VLANs.
All platforms
4,094
VLANs (Layer 3)—maximum
number of VLANs performing
IPv4 and/or IPv6 routing.
Excludes sub-VLANs.
Summit X460-G2, X670, X770, X670G2, and BlackDiamond X8
Summit X440
Summit X480, X460
E4G-200, E4G-400
2,048
VLANs (maximum active portbased)—(Maximum active ports
per VLAN when 4,094 VLANs are
configured with default license)
BlackDiamond X8
BlackDiamond 8800 series
Summit X770, X670-G2, X670v-48t,
X670, X480, X460-G2, X460
E4G-200
E4G-400
Summit X440
Summit X430
32
32
32
VLANs (maximum active
protocol-sensitive filters)—
number of simultaneously active
protocol filters in the switch.
All platforms
15
VLAN translation—maximum
number of translation VLANs.
Assumes a minimum of one port
per translation and member
VLAN.
BlackDiamond 8000 a-, c-, e-, xl series
with eight
modules of 48
ports (383)
8900-G96T-c
modules (767)
103
63
47
53
53
57
11
33
25
27
Summit X770
Summit X670-G2, X670v-48t
Summit X670
Summit X480
Summit X460-G2
Summit X460
E4G-200
E4G-400
Summit X440
Summit X430
ExtremeXOS 15.7 Release Notes
254
512
512
12
32
13
1
102
Limits
Table 2: Supported Limits (Continued)
Metric
Product
Limit
VLAN translation—maximum
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 L2only environment if the
configuration has tagged and
translated ports.
Summit X770, X670-G2
Summit X670, X480, X460
Summit X460-G2
E4G-200, E4G-400
Summit X440
1,024
512
1,024
512
127
VLAN translation—maximum
number of translation VLAN pairs
in an L2-only environment.
BlackDiamond 8800 c-, e-series
BlackDiamond 8900 xl-series
BlackDiamond X8 series
Summit X460
E4G-400, E4G-200
Summit X440, X430
Summit X480, X670, X770, X670-G2,
X460-G2
384
2,046
2,046
2,000
2,000
512
2,046
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 MSM48c, and BlackDiamond 8900 xl-series
8900-MSM128
Summit X770, X670, X670-G2, X460G2, X480
E4G-200, E4G-400
Summit X460
Summit X440
511
BlackDiamond X8, 8800 c-series MSM48c, and BlackDiamond 8900 xl-series
8900-MSM128
Summit X770, X670, X670-G2, X460-G2
E4G-200, E4G-400
Summit X460
Summit X480
Summit X440
511
VRRP (v2/v3-IPv4/IPv6)
(maximum VRID)—maximum
number of unique VRID numbers
per switch.
All platforms with Advanced Edge
license or higher, except Summit X430
7
VRRP (v2/v3-IPv4/IPv6)
(maximum VRIDs per VLAN)—
maximum number of VRIDs per
VLAN.
All platforms with Advanced Edge
license or higher, except for Summit
X430
7
VRRP (v3-IPv6) (maximum
instances)—maximum number of
VRRP instances for a single
switch, with Advanced Edge
license or higher.
(VRRP-VRRPv3-IPv6)
ExtremeXOS 15.7 Release Notes
511
128
255
32
511
255
255
255
15
103
Limits
Table 2: Supported Limits (Continued)
Metric
Product
Limit
VRRP (v2/v3-IPv4/IPv6)
(maximum ping tracks)—
maximum number of ping tracks
per VLAN.
All platforms with Advanced Edge
license or higher, except Summit X430
8
VRRP (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
8 (20
centisecond or 1
second hello
interval)
VRRP (v3-IPv6) (maximum ping
tracks)—maximum number of
ping tracks per VRRP Instance
under 128 VRRP instances, with
Advanced Edge license or higher.
Summit X440
Hello interval: 20 centiseconds
Hello interval: 1 second
All platforms, except the Summit X440
Summit X440
Hello interval: 20 centiseconds
Hello interval: 1 second
1
1
8 (20
centisecond or 1
second hello
interval)
1 (IPv6)
1 (IPv6)
VRRP (v2/v3-IPv4/IPv6)
(maximum iproute tracks)—
maximum number of IP route
tracks per VLAN.
All platforms with Advanced Edge
license or higher, except Summit X430
8
VRRP (v2/v3-IPv4/IPv6)—
maximum number of VLAN tracks
per VLAN.
All platforms with Advanced Edge
license or higher, except Summit X430
8
XML requests—maximum number
of XML requests per second.
NOTE: Limits are dependent on
load and type of XML request.
These values are dynamic ACL
data requests.
BlackDiamond 8800 c-series
with 100 DACLs
with 500 DACLs
BlackDiamond 8900 series
with 100 DACLs
with 500 DACLs
Summit X480, X670
with 100 DACLs
with 500 DACLs
10
3
10
3
4
1
XNV authentication—maximum
number of VMs that can be
processed (combination of local
and network VMs).
All platforms, except Summit X430
2,048
XNV database entries—maximum
number of VM database entries
(combination of local and
network VMs).
All platforms, except Summit X430
16,000
XNV database entries—maximum
number of VPP database entries
(combination of local and
network VPPs).
All platforms, except Summit X430
2,048
ExtremeXOS 15.7 Release Notes
104
Limits
Table 2: Supported Limits (Continued)
a.
b.
c.
d.
e.
f.
g.
h.
i.
j.
k.
l.
m.
n.
o.
p.
q.
r.
s.
t.
u.
Metric
Product
Limit
XNV dynamic VLAN—Maximum
number of dynamic VLANs
created (from VPPs /local VMs).
All Platforms, except Summit X430
2,048
XNV local VPPs—maximum
number of XNV local VPPs.
All platforms, except Summit X430
Ingress
Egress
2,048
512
XNV policies/dynamic ACLs—
maximum number of policies/
dynamic ACLs that can be
configured per VPP.u
All platforms, except Summit X430
Ingress
Egress
8
4
XNV network VPPs—maximum
number of XNV network VPPs.u
All platforms, except Summit X430
Ingress
Egress
2,048
512
The table shows the total available.
Limit depends on setting configured for configure forwarding external-tables.
When there are BFD sessions with minimal timer, sessions with default timer should not be used.
Based on in “none more-l2” mode.
Based on forwarding internal table configuration "more l2”.
Effective capacity varies based on actual MAC addresses and VLAN IDs used and hash algorithm selected.
Based on “l2-only mode”.
Applies only if all enabled BlackDiamond 8000 I/O modules are BlackDiamond 8000 c-, xl-, or xm-series modules.
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 and X480 switches compared to
BlackDiamond 8000 e-series modules.
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.
Based on forwarding internal table configuration "more l3-and-ipmc”.
Based on forwarding external table configuration “none” and forwarding internal table configuration "more l3-and-ipmc”.
Based on forwarding external table configuration "l3-only ipv4".
The limit depends on setting configured with configure iproute reserved-entries.
Based on forwarding external table configuration "l3-only ipv4”.
Based on forwarding external table configuration "l3-only ipv6”.
Based on forwarding internal table configuration "l2-and-l3”.
The IPv4 and IPv6 multicast entries share the same hardware tables, so the effective number of IPv6 multicast entries
depends on the number of IPv4 multicast entries present and vice-versa.
If IGMP and MLD are simultaneously configured on the switch, the number of effective subscribers supported would be
appropriately lessened.
Sum total of all PBR next hops on all flow redirects should not exceed 1024.
The number of XNV authentications supported based on system ACL limitations.
ExtremeXOS 15.7 Release Notes
105
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.
This chapter contains the following sections:
•
Open Issues on page 106
•
Known Behaviors on page 110
•
Resolved Issues in ExtremeXOS 15.7 on page 112
Open Issues
The following are new open issues for supported features found in ExtremeXOS
15.7.1.
Table 3: Open Issues, Platform-Specific, and Feature Change Requests (CRs)
CR Number
Description
General
xos0060713
Executing the command clear cpu-monitoring sets the dirty
bit(*).
xos0057231
An FDB entry created by ARP with "i" flag set is not removed from the
FDB table after a static entry for the same IP address is added with a
different MAC value.
xos0059234
Disabling NetLogin on ports may cause a system crash.
xos0053450
Bootp_Relay with Option 82: Client connected VLAN with more than
one port with option on and check "on" and policy "keep". Check is not
working.
xos0057297
When MD5 password is different for both broadcast server and client,
the NTP session is established anyway, and no warning is indicated in
"leap indicator".
xos0057356
The output of the show ntp association 1.1.1.1
statistics command shows the local interface IP address as NTP
association IP address or 0.0.0.0.
Workaround: Running clear counter command corrects the IP
address.
xos0057392
NTP session still shows synchronized after disabling port in NTP client
interface.
xos0057517
With global NTP server configured and an NTP session established
between server and broadcast client, after disabling NTP, the peer
looses it active peer status (*), but for the broadcast client, status (*) is
not removed.
xos0058349
Enabling DHCP on Management VLAN with IP address already
configured does not produce error.
106
Open Issues, Known Behaviors, and Resolved Issues
Table 3: Open Issues, Platform-Specific, and Feature Change Requests (CRs)
CR Number
Description
xos0058668
After rebooting DHCPv6, client stuck up in rebooting state.
BlackDiamond X8 Series Switches
xos0058842
Tagged VLAN traffic is dropped at ingress of 100G4X-XL module port,
when the same port is added to another CEP-VMAN VPLS.
This issue does not occur on non-100G4X-XL modules/ports.
xos0059214
GRE tunnel traffic for some destinations is slow-path forwarded after
running two failovers.
xos0059633
On L2VPN session between BlackDiamond X8 series switches with
traffic established over RSVP primary path, restarting MPLS on Provider
Edge (PE) switches produces the following MPLS kernel errors:
01/08/2015 08:37:13.64 <Erro:Kern.MPLS.Error> Slot-5:
extreme_mpls_del_tid_vp_nh_xref: MPLS TID+VP->NH tid
= 1, vp : 0x4 map entry not found in btree rv = -7
(Entry not found)
xos0059927
For the 100G4X and 100G4X-XL modules, tagged data traffic is not
going to untagged service VMAN after deleting tagged service VMAN
from the VPLS instance, and then creating new untagged service VMAN
and attaching it to the VPLS.
BlackDiamond 8800 Series Switches
xos0057741
Deleting a shared group from BlackDiamond 8800 series switches
deletes the port linked to MVRP, but the dynamic VLAN still holds the
port.
Summit Family Switches
xos0058437
For Summit X460 and X670-G2 series switches, the buffer for Weighted
Random Early Detection (WRED) queues is incorrectly allocated at 10%
of shared memory plus minimum guarantee, when it should be 100% of
shared memory plus minimum guarantee.
xos0060258
After failover, ports are not added to aggregator in LACP with passive
mode. Port are added correctly when switches are in active mode
(default state).
xos0058868
Configuring SRP for a port after disabling VLAN containing the port,
puts the master port of SRP in unblocking state. FDB is learned through
that port, though VLAN is disabled. After un-configuring SRP for the
ports present in the VLAN, this unblocks redundant port also, causing
loop in the network.
xos0059373
Gigabit Ethernet compliance of 100LX10 optics appears as "UNKNOWN"
in debug hal show optic-info command.
xos0057605
Summit X460 and X460-G2 series switches and E4G-200 cell site
routers have more than one option slot. For these platforms,
entPhysicalDesc Object in entPhysicalTable returns "Option Slot-1" for
two option-card slots.
xos0059345
When 100LX10,100FX without PHY optics are inserted in 10G SFP+
ports, no warning log messages occur to indicate that these optics are
not supported on 10G SFP+ ports.
ExtremeXOS 15.7 Release Notes
107
Open Issues, Known Behaviors, and Resolved Issues
Table 3: Open Issues, Platform-Specific, and Feature Change Requests (CRs)
CR Number
Description
SummitStack
xos0060218
In Summit X670-G2 stacks, with bi-directional L2 multicast traffic
running, running failover produces the following error message:
<Erro:HAL.LAG.CfgFail> Slot-2: Failed to configure
link aggregation group 1:10 on slot 1 unit 0:
Operation timed out
xos0058407
On SummitStacks with Summit X670 and X670 as MLAG peers and
connected over LACP LAG, and L2VPN is configured with primary
Explicit Route Option (ERO) and secondary ERO. While traffic is
flowing, performing a slot failover produces error messages.
xos0058637
On Summit X670 stacks, the following MPLS kernel errors occur when
after issuing the command delete VPLS all:
“Slot-1 BA-CO-NSNP_75.17 # Oct 24 02:03:23
BA-CO-NSNP_75 <Erro:Kern.MPLS.Error>
(ems_main.c:446)
bcm_custom_extr_vfp_action_mpls_inport_set(remo
ve) failed for unit = 0 vpn = 0x65, port =
0x800000f vp = 0x18000191, rv = -13 (Invalid
identifier)”
Summit X460-G2 Series Switches
xos0059395
Summit X460-G2-1G switches do not produce warning log messages
(not compatible) when 100LX10 optics are inserted in the highest
numbered 1G ports.
xos0055999
For Summit X670-G2 and X460-G2 series switches, currently the
ENTITY-MIB:entPhysicalIsFRU for fan and power modules shows the
values as FALSE. However since these fan modules and power modules
are replaceable units, this should be shown as TRUE.
BGP
xos0058441
After creating a BGP peering session between link local IPv6 addresses
with the scope ID specified, deleting the VLAN containing link local IPv6
address. and then issuing the command show configuration
bgp, switch reboots with “Epm application wdg timer
warning” error message.
xos0058666
BGP multicast routes are not displayed in routing table when origin is
specified.
ERPS
xos0061263
Traffic fails to flow when there are multiple failures in the major ring.
ExtremeXOS 15.7 Release Notes
108
Open Issues, Known Behaviors, and Resolved Issues
Table 3: Open Issues, Platform-Specific, and Feature Change Requests (CRs)
CR Number
Description
MPLS
xos0057448
After adding more than two or three Explicit Route Option (ERO)
Excludes to primary path, the command show mpls rsvp-te
lsp my_lsp1 detail shows "Path Computation
Failure" for the primary path and is using the secondary path as
observed in the command traceroute mpls lsp my_lsp1.
xos0057509
When primary path is configured with strict source and added link with
exclude option, label-switched path (LSP) comes up.
In secondary path adding Explicit Route Option (ERO) with loose
source and excluding the same link, LSP never comes up.
xos0057834
After restarting MPLS, disabling primary path makes secondary path go
down.
xos0058421
VPWS (tag include): Outer dot1q tag is missing from frame received on
remote Provider Edge (PE) switch.
xos0057510
Traffic is dropped on switches after disabling primary when RSVP labelswitched path (LSP) is fast reroute enabled.
Workaround: Issue command restart process mpls.
xos0058974
After deleting, and then adding VPWS tunnel (rapidly, by using script)
the mpls statistics l2vpn counters stops incrementing.
xos0059530
Disabling, and then enabling MPLS on primary path P node is causing
data traffic loss at ingress of a VPLS Provider Edge (PE) switch for 15
seconds. Sometimes this causes VPLS to go into signal state, which can
cause traffic loss. P node should tear down the LSP/primary path before
disabling MPLS/RSVP, so that LSP can move to secondary path quickly.
PoE
xos0050402
The command enable inline-power legacy does not power up
pre-standard PoE devices, such as Cisco phone 7940/7960 that do not
work with IEEE 802.3af standard detection and legacy capacitive
detection. The enable inline-power legacy command now
powers up legacy PoE devices that rely on the capacitive detection
instead.
OSPF
xos0059560
After reboot, OSPFv3 fails to select the best path to destination.
Workaround: Disable, and then enable OSPFv3.
xos0059569
OSPFv3 external routes flap and traffic loss occurs when introducing
new ABR which has reachability to destination.
RIP
xos0058173
Route policy created in a RIP VLAN to permit some routes in network
range 192.168.0.0/24, denies all the RIP routes learned via that particular
VLAN interface.
ExtremeXOS 15.7 Release Notes
109
Open Issues, Known Behaviors, and Resolved Issues
Known Behaviors
The following are limitations in ExtremeXOS system architecture that have yet to
be resolved.
Table 4: Known Issues, Platform-Specific, and Feature Change Requests (CRs)
CR Number
Description
General
xos0058855
MLAG-PIM-SSM: Traffic loss for a subscriber occurs when another
subscriber leaves on a two-peer MLAG setup.
Workaround: Increase the leave-timeout and last membership query
interval to 2 seconds.
xos0055791
Block size option is not available in bootROM download image
command.
Generally an image is downloaded from bootROM either when the
switch is newly purchased or for an emergency recovery (for example,
when switch is constantly rebooting without getting a command line
prompt), so only minimal arguments are provided for the command (for
example, IP address, gateway, and download image location).
xos0057718
SCP2 file transfer from external SCP client does not work. OpenSSH
uses the RCP protocol, which is disabled in the ExtremeXOS for security
reasons. Consequently, OpenSSH SCP does not work with the
ExtremeXOS SSH implementation.
Workaround: To transfer files, use SFTP instead of SCP from external
clients.
xos0058944
PVLAN network-tagged packets are allowed to ingress on subscriber
VLAN ports.
BlackDiamond 8800 Series Switches
xos0058703
IPv6 ECMP is not supported on BlackDiamond 8800 G48Te2 modules.
Summit Family Switches
xos0059482
Configuring QoSprofile X to “0” using peak_rate or maxBw does not
work. All traffic is forwarded as if QoSprofile X is set to 100% maxBw.
IP Routing Protocols
xos0057722
Duplicated traffic is seen when SPT threshold is set to 'infinity' on
WMLAG peers
Workaround: Do not set SPT threshold at ‘infinity’ in MLAG and WMLAG
topologies. Since no (S;G)s are created, no checkpoint occurs and this
results in duplicated traffic.
ExtremeXOS 15.7 Release Notes
110
Open Issues, Known Behaviors, and Resolved Issues
Table 4: Known Issues, Platform-Specific, and Feature Change Requests (CRs)
CR Number
Description
MPLS
xos0058780
On Summit X460-G2 and X670-G2 series switches, and BlackDiamond
X8 switches with XB-100G4X-XL modules, the command show mpls
statistics l2vpn displays double the TxPackets count as the actual
packets transmitted over the VPLS.
OSPF
xos0057100
The command unconfigure ospfv3 is not removing the VLANs
from the OSPFv3 domain. All the neighbors are still visible.
STP
xos0058362
Ports configured as auto with auto-edge feature turned on, do not have
this status correctly shown in show <stpd> port command. Port
operation mode appears as “Point-point”.
Workaround: Port operation mode appears correctly in show
<stpd> port detail command.
ExtremeXOS 15.7 Release Notes
111
Open Issues, Known Behaviors, and Resolved Issues
Resolved Issues in ExtremeXOS 15.7
The following issues were resolved in ExtremeXOS 15.7. ExtremeXOS 15.7 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, ExtremeXOS 15.4.1,
ExtremeXOS 15.5.1, ExtremeXOS 15.5.2, ExtremeXOS 15.6.1, and ExtremeXOS 15.6.2.
For information about those fixes, see the release notes for the specific release.
Table 5: Resolved Issues, Platform-Specific, and Feature Change Requests
(CRs)
CR Number
Description
General
xos0057421
Fixed vulnerability in OpenSSL 1.0.1 through 1.0. that can affect:
• THTTPD
•
•
•
•
•
Tech Support feature
Optics licensing feature
OpenFlow
XMLC
CLI master one-time debug password feature
xos0056340
Unknown Layer 2 traffic from Isolated subscriber VLANs are
forwarded to the remote MLAG ports, even though local MLAG
ports are up.
xos0056987
With ELSM enabled on port p1 on two switches, with 10 seconds
as the ELSM hello interval, and trap receiver configured on the
both switches (or managed in Ridgeline, which configures the
trap receiver by itself), and then disable/enable port p1 on both
switches.
Switches send two linkup traps.
xos0054199
Ingress traffic stalls on port when switches receive continuous
802.3x pause frames on egress ports for that traffic stream.
xos0055108
The bound IP address is not being reflected in the command
show vlan.
xos0059851
When a DHCP client receives an IP address that conflicts with a
static IP address configured in a VLAN, the static IP address is
removed from the VLAN and the DHCP client stops.
xos0053584
sFlow displays incorrect VLAN tag when collecting on tagged
VMAN ports.
xos0059222
sFlow-sampled packets are flooded out of VLANs when these
same packets are software learned.
xos0056683
CCM sender TLV not recognized due to switches using different
SenderID TLVs to convey the same information (IP address).
ExtremeXOS 15.7 Release Notes
112
Open Issues, Known Behaviors, and Resolved Issues
Table 5: Resolved Issues, Platform-Specific, and Feature Change Requests
(CRs) (Continued)
CR Number
Description
xos0057407
Hops fields in DHCP packets are not incremented when
processed by Bootprelay.
xos0057601
The command disable ip-security arp learning
learn-from-arp vlan <vlan_name> port <portname>
is not saved/applied after reboot.
xos0055398
Authentication fails for a Netlogon client in dot1x mode, since
the port added untagged in one VLAN cannot be moved to
another VLAN.
xos0057199
The output of the command ls <filename> displays the last
accessed time stamp instead of the last modified time stamp.
xos0053350
The TFTP put and get commands do not support the current
working directory operaor ( .) in their arguments. The default
working directory is always taken as the /cfg directory
irrespective of the current directory from which the command is
issued.
xos0057606
"enable cli prompting" is allowed inside UPM/CLI scripts.
xos0058393
The TCL command clock format is not available for CLI
scripting and attempting to use it produces an error.
xos0059037
Pre-emphasis show command displays incorrect values for nonSummit X460 series switches’ slots in mixed stacks.
xos0059243
The process exsh ends unexpectedly after executing a show
command with a port list followed by invalid letters (for
example, show port 1:1,1:2ab), and then pressing TAB.
xos0056191
Executing the command show temperature from a usercreated account returns an error.
xos0056228
TFTP get operation fails when the remote file exists in second
level sub-directory.
xos0059661
Running extended diagnostics on backup MSM (Master Switch
Fabric Module) can, under certain rare conditions, cause the
cfmgr process to end unexpectedly on the master MSM.
xos0059579
SFP+ ports do not link up with active optical breakout cable.
Cable is identified as not supported and treated as a 3rd-party
cable.
xos0058968
Error log "Function Pointer Database is not fully
initialized" appears during bootup on non-Summit
platforms.
xos0053046
The command delete meter <meter-name> produces the
error "Error: Timeout awaiting meter deletion" and
the meter is not removed from master switch, but the meter is
removed from backup switch.
ExtremeXOS 15.7 Release Notes
113
Open Issues, Known Behaviors, and Resolved Issues
Table 5: Resolved Issues, Platform-Specific, and Feature Change Requests
(CRs) (Continued)
CR Number
Description
BlackDiamond 8800 Series Switches
xos0054970
BlackDiamond 8800-xl cards and Summit X480 series switches
should not allow Layer 2 Protocol Tunneling and Filtering to be
configured over VPLS/VPWS.
xos0059605
Sys-health-check output shows false fabric port flap events
between Master Switch Fabric Module (MSM) and I/O module.
xos0057624
On a PVLAN, after restarting process VRRP on the VRRP master
switch, traffic loss occurs in the switch.
BlackDiamond X8 Series Switches
xos0053636
Changing the IP MTU on VLANs, causes rtmgr process to end
unexpectedly.
xos0054860
Configuring, and then unconfiguring, large ACL policy files two
or three few times causes the ACL to fail during subsequent
installs.
xos0054861
Incorrect frame delay measurements occur on BlackDiamond X8
and 8800 series switches since kernel time stamping for
software end points isn’t supported.
xos0055433
The tDiag process occasionally ends unexpectedly after
executing show debug system-dump MM B from MM-A,
when MM-B does not contain system dump.
xos0056184
Removing primary Management module (MM) causes LAGs to
bounce.
xos0056300
Traffic does not switch back to primary port when smart
redundancy is enabled.
xos0057352
Kernel crash occurs when there is a Layer 2 loop in the network.
xos0057560
Accessing ScreenPlay while running a script can cause the
thttpd process to end unexpectedly with the following error:
<Erro:DM.Error> MM-A: Process thttpd Failed MMA rebooted
xos0057643
On Summit X460-G2, X770, and BlackDiamond switches, slow
learning rates occur for scaled multicast traffic in l2-and-l3-andipmc mode.
xos0058375
ACLs to match VLAN-ID, CVID parameters do not work for slow
path forwarded packets.
xos0058568
Some front panel ports cannot be enabled after rebooting the I/
O module.
xos0058847
After second Master Switch Fabric Module (MSM) failover,
backup root gets has incorrect STP bridge ID.
xos0059104
ACL policies are not installed in hardware after management
module failover.
xos0059156
VRRP control packets are dropped due to congestion in tx
queue under scaled environments.
ExtremeXOS 15.7 Release Notes
114
Open Issues, Known Behaviors, and Resolved Issues
Table 5: Resolved Issues, Platform-Specific, and Feature Change Requests
(CRs) (Continued)
CR Number
Description
xos0059343
The process snmpMaster might end unexpectedly during
upgrade from ExtremeXOS 15.3 to 15.5 for some SNMP
community names.
xos0059733
LSP load sharing does not occur on Summit X460-G2 and
BlackDiamond X8-100G4X switches.
Summit Family Switches
xos0052494
RSTP port transition takes longer than usual to go to forwarding
state if STPD is disabled, and then enabled.
xos0053409
After enabling third-party optic license, traffic should be
forwarded in 40G and log messages about third-party optics
should not occur.
xos0053755
Should have same session ID appear in both show session
command and log target field in show log configuration
command.
xos0055637
With two flows installed on the a Summit X440 series switch,
only one flow is recognized.
xos0056230
SNMP query on “extremeMemoryMonitorsystemTable” does not
show backup information, if slot2 is master and slot1 is backup.
xos0056296
Make p2p calculations more robust against negative path delay
measurements.
xos0056704
Cannot overwrite dynamic unicast addresses with static
multiport unicast addresses.
xos0056812
Non-default configuration for mac-lockdown-timeout is removed
from the configuration when mac-lockdown-timeout is disabled
on a port.
xos0057106
When mirroring is configured to be triggered through clearflow,
mirroring does not work and produces the following error:
06/26/2014 17:14:16.40
<Warn:HAL.IPv4ACL.Warning> : Could not enable
mirroring for ACL rule since mirror acl-rule-1
is not active.
xos0057897
Orphan static route not preserved after reboot when ECMP
route exists.
xos0058040
DNS name resolve fails when name-server is first added to VRdefault, then to VR-mgmt, and then deleted from VR-default.
xos0058048
AVB data traffic sent with dot1p “2” priority at wire-rate causes
gPTP port state to flap.
xos0058050
After 20 minutes of running audio, noise periodically occurs.
xos0058537
Switches become unresponsive and drop traffic when they have
a high number of traffic streams and AVB enabled ports.
xos0059447
Can use Python scripts to access debug shell and execute
commands even though debug mode is not enabled making
switches vulnerable to unauthorized use.
ExtremeXOS 15.7 Release Notes
115
Open Issues, Known Behaviors, and Resolved Issues
Table 5: Resolved Issues, Platform-Specific, and Feature Change Requests
(CRs) (Continued)
CR Number
Description
xos0056878
Summit X440 series switches are not inserting the MSTI
Configuration Message (MSTI Vector information for MSTI
instance 1) into BPDU packets when configured as the root
bridge for both the CIST (stpd s0) and for MSTI 1 (stpd s1) in
region 1.
SummitStack
xos0053998
In Summit X670 stacks, the following error messages appear
after executing the command debug hal show opticinfo 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
xos0056075
After issuing the command restart process ospf-5 on a
SummitStack, H-VPLS (spoke) nodes fail to encapsulate packets
to VPLS pseudowires. Traffic is restored after about 15 minutes.
xos0057767
Static FDB associated with VPLS service VLAN is not
programmed in hardware after reboot when disable
learning is configured.
xos0058142
System crashes with “process nodemgr pid 1595 signal 5” error
when master slot is rebooted with maximum number of portbased mirroring filters configured and multicast traffic.
xos0058430
SummitStack firmware versions reported by SNMP are not valid.
xos0056179
Commands use inconsistent syntax for value ranges, some of
which are incorrect and/or misleading.
xos0058133
SummitStacks use slot MAC address in DHCP packets when
enabling DHCP on Management VLAN.
Summit X430 Series Switches
xos0057663
For Summit X430 series switches, the command show
inline-power shows incorrect value for budgeted power as
set in the command config inline-power budget.
xos0059524
Link status is incorrect when auto-polarity setting is off.
ExtremeXOS 15.7 Release Notes
116
Open Issues, Known Behaviors, and Resolved Issues
Table 5: Resolved Issues, Platform-Specific, and Feature Change Requests
(CRs) (Continued)
CR Number
Description
Summit X440 Series Switches
xos0058068
Summit X440-24tDC switches are reporting maximum
temperature limit 60°C under normal conditions.
xos0058184
When the designated router (DR) receives a register-stop
message from the rendezvous point (RP), it starts a registerstop timer to maintain this state. Just before the register-stop
timer expires, the DR sends a null-register message to the RP to
allow the RP to refresh the register-stop information at the DR.
Summit X440 series switches acting as DRs do not send null
register before the register-stop timer expires.
xos0058300
Packets are dropped on combo ports when the preferred
medium is configured as copper force.
xos0058301
In Summit X440 series switches, error message "mounting /
dev/hda4 on /data failed" appears during bootup.
xos0058547
In Summit X440-24t switches, the maximum hotspot
temperature should be changed to 70°C.
xos0058889
The output of the show fans command always indicates no
fan installed (“Empty”).
xos0056738
Summit X440 series switches do not drop the IGMP Query
Message with an invalid IGMP checksum.
Summit X450 Series Switches
xos0057647
Packets are forwarded to CPU after deleting the VLAN with
disable learning.
Summit X460 Series Switches
xos0051266
ExtremeXOS 15.7 Release Notes
In Summit X460 stacks, backup does not get configuration
synchronized, when forming a stack with only one stacking port
using alternate stacking mode.
117
Open Issues, Known Behaviors, and Resolved Issues
Table 5: Resolved Issues, Platform-Specific, and Feature Change Requests
(CRs) (Continued)
CR Number
Description
xos0055518
On Summit X460 series switches with OpenFlow enabled,
switches boot up with the following error messages:
“Error while loading structure
<cfgTechSupport><basic>1</basic><hour>0</
hour><srcipaddress>10.68.63.86</
srcipaddress><hostname><![CDATA[12.38.14.200]]><
/hostname><sslEnabled>0</sslEnabled><port>800</
port><daily>0</daily><isDefault>1</
isDefault><bootup>1</bootup><automatic>1</
automatic><nameIndex><![CDATA[12.38.14.200]]></
nameIndex><errorDetected>0</
errorDetected><vrName><![CDATA[VR-Mgmt]]></
vrName></cfgTechSupport>: Source IP address
10.68.63.86 does not belong to the VR VR-Mgmt.
<cfgTechSupport>”
“Error while loading structure
<openflowGlobalConfig><numVlans>2</
numVlans><version>0</version><fdb>0</
fdb><isEnabled>1</isEnabled></
openflowGlobalConfig>: Error: Invalid OpenFlow
version<openflowGlobalConfig>”
xos0056342
Misleading power supply unit (PSU) traps are sent when PSUs
are inserted or powered on/off.
xos0058043
MSRP: packets are dropped when bandwidth is increased to 611
M.
xos0058053
Summit Stack run failover takes longer than usual time to boot
the backup node.
xos0058248
Summit X460 series switches change boot image after Installing
an xmod image.
xos0058589
SummitStack reboots due to temperature out of range
messages.
xos0059131
Debounce timer is not getting configured if stack ports reside in
different units. Also, pre-emphasis configuration should be
rejected in alternate stacking mode.
xos0059671
On Summit X460 series switches with 750 W power supplies
installed, log messages "Power usage data unknown"
appear.
Summit X460-G2 Series Switches
xos0055189
In Summit X460-G2 stacks, the command show power fails to
display power usage and produces the error "Failed reading
Slot-B power on time" during slot reboot.
xos0057245
In Summit X460G2-24p-G4, 24t/p, and 48t/p (1G types), links do
not come up for 100 Mbps and 10/100/1000 Base-T optics.
xos0059240
High CPU utilization and MAC learn thrashing occurring on fabric
links forming a X460-G2 stack.
ExtremeXOS 15.7 Release Notes
118
Open Issues, Known Behaviors, and Resolved Issues
Table 5: Resolved Issues, Platform-Specific, and Feature Change Requests
(CRs) (Continued)
CR Number
Description
xos0059577
On Summit X460G2 series switches, can’t install ExtremeXOS
SSH XMOD image.
xos0057346
Link flaps occur when optics such as 10/100/1000 Base-T or
100FX is inserted into Summit X460-G2 and X480 series
switches.
xos0056971
In Summit 670G2-72x and Summit 460-G2 stacks, executing a
failover produces the following Kernel error:
Erro:Kern.Card.Error> Slot-1: KICM: Could not
change SP1 type for NONE neighbor.
idx1=0,idx2=0
Summit X670 Series Switches
xos0055917
With OpenFlow v1.3 enabled, the switch stops responding after
executing the disable openflow command. This problem
does not occur when the switch has OpenFlow v1.0 enabled.
xos0059128
In Summit X670 series switch, all LEDs are blinking at a faster
rate.
Summit X770 Series Switches
xos0053986
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.
xos0059573
Factory installed image incorrectly references “x450” in the
image name.
AVB
xos0058603
PTP follow up does not happen correctly when correction field is
greater than 32 bits.
ACL
xos0054720
With network-zone configured, the command show accesslist port 1:1 detail reverses the IP address match
criteria.
xos0056423
The command show access-list meter port does not
display the meters applied on the port via policy.
xos0057328
ACL rule to match IPv6 packets with arbitrary mask is not
working as expected.
xos0059330
With dual master switch fabric module (MSM) installed, clearflow ACL intermittently fails.
ERPS
xos0056122
Configuring MEP IDs through ERPS (for dynamic CFM creation)
commands are unavailable.
xos0057141
Default VLAN cannot be added as a protected VLAN to an ERPS
ring.
ExtremeXOS 15.7 Release Notes
119
Open Issues, Known Behaviors, and Resolved Issues
Table 5: Resolved Issues, Platform-Specific, and Feature Change Requests
(CRs) (Continued)
CR Number
Description
xos0058464
In ERPS rings, blocking the control channel by deleting the ports
from the control VLAN causes a short loop in the ring.
xos0057179
ESRP feature is not enabled immediately after the installing an
Advance Edge license.
FDB
xos0059146
With port-specific tags configured, source MAC addresses are
removed and re-learned for all incoming ARP packets causing
flooded traffic a for short time interval.
IP General
xos0052696
Static routes are installed in route manager when the next hop is
configured as its own loopback or as a local VLAN interface IP
address.
xos0058801
IPv4 ECMP route entries learned by a routing protocol are
sometimes removed from hardware when one of the next hop
gateways goes down, but other gateways remain up.
xos0059581
Rtmgr process ends unexpectedly when OSPF external routes
are deleted from the route table.
IP MLD
xos0054105
Source IP addresses for MLDv1 hosts in user-defined PIM SSM
range are not resolved.
xos0054121
Problem with storing SSM mapping entries with SSM mapping
entries in hierarchal manner.
xos0057688
The command clear ipmc fdb does not clear IPv6 multicast
entries.
IP PIM
xos0053818
System stops responding when PIM is disabled for the ingress
interface an on MLAG peer when there is a forwarding egress
interface and at least another one asserted.
xos0054101
W-MLAG-PIM: (*;G)s should not be created on non-designated
router (DR) after PIM is bounced. Ingress interface for PIM DR is
an MLAG VLAN with clients present.
MLAG
xos0053412
After peer reboots, MLAG ports remain in ready state.
xos0053469
MLAG health check: Hello packets are exchanged temporarily
when the alternate path is restored after ISC connectivity is lost.
xos0053744
MLAG health check: Manually disabled MLAG ports that are part
of static/LACP sharing are re-enabled by alternate health check.
xos0058873
FDB entries are learned incorrectly on VMANs in MLAG peers
when the MLAG ports are CEP ports for multiple VMANs with
different CVIDs.
ExtremeXOS 15.7 Release Notes
120
Open Issues, Known Behaviors, and Resolved Issues
Table 5: Resolved Issues, Platform-Specific, and Feature Change Requests
(CRs) (Continued)
CR Number
Description
MPLS
xos0058880
Packets are not switched to primary path after recovering from
path failure in MPLS RSVP-TE.
xos0056994
Unable to add EAPS shared ports to VLANs even after
disassociating them from VPLS domains.
OpenFlow
xos0058117
After enabling, and then disabling, OpenFlow globally and on a
VLAN with standard mode, you cannot enable learning on the
VLAN anymore.
xos0055315
When sending 300 packets to hit the of Default_0 flow, the
switch is forwarding 3 packets to the controller through packet
In message and floods the rest packets out of other OpenFlow
ports.
xos0055946
In 5-node setup, after installing the OpenFlow groups and flows
using OVS commands, the transit node is not forwarding traffic
to all applicable switches.
xos0056061
The OpenFlow switch is not actively sending out hello messages
when the 3-way TCP connection is established.
OSPF
xos0058056
OSPF-opaque, LSA-related configurations do not appear in
output of the show configuration command.
xos0059305
OSPF consumes a large amount of memory when a large
number of Link State Acknowledgment packets are queued up
for transmission.
xos0057538
OSPFv3 fails to select the best cost external route.
PoE
xos0058473
Operator-set power is rounded down to the nearest 1.0 Watt.
Ports display the configured maximum allocated power, rather
than the actual power. This can lead to power being denied to
devices requesting power under the configured limit.
xos0058994
POE is not delivering power to several model phones when
legacy mode is enabled.
Python
xos0058120
After running the command debug cli run python
exosjson.py getnext mod.struct, running the command
show configuration produces the error: “couldn't open
"./config/xos_config.xsl": no such file or
directory.”
xos0058835
Python scripts can disable command line output after the script
finishes.
ExtremeXOS 15.7 Release Notes
121
Open Issues, Known Behaviors, and Resolved Issues
Table 5: Resolved Issues, Platform-Specific, and Feature Change Requests
(CRs) (Continued)
CR Number
Description
RIP
xos0058683
RIP packets are dropped when another VLAN has a secondary
IP address configured.
STP
xos0059002
Checkpoint errors occur during execution of STP debug
command if switch contains many STP-enabled VLANs.
VLAN
xos0057435
ExtremeXOS 15.7 Release Notes
Packets are dropped when learning is disabled in a VLAN when
its associated ports are configured with limit learning in another
VLAN.
122
4
ExtremeXOS Documentation
Corrections
This chapter lists corrections to the ExtremeXOS 15.7 User Guide and ExtremeXOS
15.7 Reference Guide.
This chapter contains the following sections:
•
•
ACLs on page 124
•
•
•
Configure IP-MTU VLAN Command Syntax Description on page 126
•
•
•
•
•
•
MLAG on page 129
Configure Access-List VLAN-ACL-Precedence Command Usage Guidelines
on page 125
Debounce Commands on page 127
Extreme Networks Virtualization (XNV), Identity Management (IDM), and
Network Time Protocol (NTP) on page 129
Rate Limiting/Meters on page 130
Remote Mirroring on page 130
Routing Policies on page 131
Synchronize Command on page 132
TACACS Server on page 132
123
ExtremeXOS Documentation Corrections
ACLs
Basic Switch Operation ExtremeXOS User Guide, 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.
Policies and Security ExtremeXOS User Guide, Chapter 5: “ACLs” > “ACL Rule Syntax
Details”
xos0058670
Change the match conditions fields "IGMP-type number" and "IGMP-code number"
to "ICMP-type number" and "ICMP-code number".
The corresponding description fields state the correct match conditions (for
example, "ICMP-type number" and "ICMP-code-number"), but the match condition
fields are misprinted as "IGMP-type number" and "IGMP-code number", respectively.
ExtremeXOS 15.7 Release Notes
124
ExtremeXOS Documentation Corrections
Configure Access-List VLAN-ACL-Precedence Command
Usage Guidelines
ExtremeXOS Command Reference for the configure access-list
vlan-acl-precedence command
xos0060123
Change usage guidelines from:
“The following feature applies to only policy-file based ACLs that are applied on a
VLAN. Use this command to switch between two VLAN-based ACL configuration
modes. In the shared vlan-aclprecedence mode, VLAN-based ACL rules share the
same precedence with other types of ACL rules. This is the default mode and
provides the same behavior as in the previous software releases. In the dedicated
vlan-acl-precedence mode, VLAN-based ACL rules have different precedence
compared to other types of ACL rules. The dedicated mode yields improved
installation performance for VLAN based access-lists but may affect hardware rule
utilization in some configurations.”
To:
“The following feature applies to only policy-file based ACLs that are applied on a
VLAN. Use this command to switch between two VLAN-based ACL configuration
modes. In the shared vlan-aclprecedence mode, VLAN-based ACL rules share the
same precedence with other types of ACL rules and provides the same behavior as
in the previous software releases. In the dedicated vlan-acl-precedence mode,
VLAN-based ACL rules have different precedence compared to other types of ACL
rules and this is the default mode. The dedicated mode yields improved installation
performance for VLAN based access-lists but may affect hardware rule utilization in
some configurations.”
ExtremeXOS 15.7 Release Notes
125
ExtremeXOS Documentation Corrections
Configure IP-MTU VLAN Command Syntax Description
ExtremeXOS Command Reference and ExtremeXOS User Guide for the configure
ip-mtu command
xos0061010
Command Reference
In the Syntax Description table, change the description from:
“mtu - Specifies the IP maximum transmission unit (MTU) value. Range is from 1500
to 9194.”
To:
“mtu - Specifies the IP maximum transmission unit (MTU) value. Range is from 1,500
to 9,194. However, the command allows the maximum limit up to 9,216 considering
port configuration, such as tagging which influences the L2 header size. However,
values greater than 9,194 may lead to packet loss and are not recommended.”
User Guide
Under the title Jumbo Frames > IP Fragmentation with Jumbo Frames:
Need to change the following content from:
“The ip-mtu value ranges between 1500 and 9194, with 1500 the default.”
To:
The ip-mtu value ranges between 1,500 and 9,194, with 1,500 the default. However,
the command allows the maximum limit up to 9,216 considering port configuration,
such as tagging which influences the L2 header size. However, values greater than
9,194 may lead to packet loss and are not recommended.”
ExtremeXOS 15.7 Release Notes
126
ExtremeXOS Documentation Corrections
Debounce Commands
ExtremeXOS Command Reference
xos0060723
The following two debounce commands should appear:
Configure stack-ports debounce time
configure stack-ports {port-list} debounce time [default|time]
Description
Configures debounce time feature on the stacking ports.
Syntax Description
port-list
Specifies one or more stacking ports.
default
Configure the default value “0”
<milliseconds> Time in milliseconds. Range is 0 (no debouncing) to 5000.
Default
Default debounce time value is 0
Usage Guidelines
Debounce timer can be configured to override the false link flaps i.e. link flaps that
happens in a milliseconds interval.
Example
configure stack-ports 1:1 1:2 debounce time 150
History:
Available from ExtremeXOS 15.3.4
Platforms Availability
All stackable switches.
ExtremeXOS 15.7 Release Notes
127
ExtremeXOS Documentation Corrections
Show stack-ports debounce
show stack-ports {port-list} debounce
Description
Displays the current debounce time configured in stack-ports
Syntax Description
port-list
Specifies one or more stacking ports.
Default
N/A
Usage Guidelines
To view the current debounce time configured in stack-ports. Specifying the stackport allows to view the debounce time for particular stack-port alone.
Example
show stack-ports 1:1 1:2 debounce
Following is the example output:
Stack Debounce
Port Time (ms)
----- -------------1:1
0
1:2
0
History
Available from ExtremeXOS 15.3.4
Platform Availability
All stackable switches.
ExtremeXOS 15.7 Release Notes
128
ExtremeXOS Documentation Corrections
Extreme Networks Virtualization (XNV), Identity
Management (IDM), and Network Time Protocol (NTP)
ExtremeXOS User Guide, ExtremeXOS Feature License Requirements
xos0057855
The L2 Edge license no longer supports Extreme Networks Virtualization (XNV),
Identity Management (IDM), and Network Time Protocol (NTP) features from
ExtremeXOS 15.5.2 onwards for the Summit X430 series switches.
MLAG
Basic Switch Operation ExtremeXOS User Guide, under Basic Switch Operation >
MLAG > MLAG-LACP
xos0059921
Add the following note:
NOTE
When LACP shared ports are configured as MLAG
ports, a LAG ID change after MLAG peer reboot may
result in MLAG ports being removed and re-added to
the aggregator. To avoid the MLAG port flap, it is
recommended to configure a common LACP MAC in
both the MLAG peers using the command configure
mlag peer <peer_name> lacp-mac
<lacp_mac_address>.
ExtremeXOS 15.7 Release Notes
129
ExtremeXOS Documentation Corrections
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.”
Remote Mirroring
ExtremeXOS User Guide
xos0058665
Add information about remote mirroring guidelines:
“One-to-many remote mirroring does not work as expected where 'mirror-to' ports
can receive double-tagged packets. This is due to hardware limitation and applies to
the following platforms:
•
•
Summit X150, X250e, X350, X450, X450e, X450a.
BlackDiamond modules: G48T, G48P, 10G4X, G24X, a-series, e-series, c-series
(except 8900 cards), and 8500 series modules
ExtremeXOS 15.7 Release Notes
130
ExtremeXOS Documentation Corrections
Routing Policies
ExtremeXOS User Guide under Routing Policies > Routing Policy File Syntax > Policy
Action Statements
xos0060766
In the Policy Actions table, for the "community set" attribute replace the existing
text with the following text:
In the Action column:
“community set [no-advertise | no-export | noexport-76subconfed |
<community_num> | <as_num> : <community_num>];”
In the corresponding Description column:
“Replaces the existing community attribute of a route by the community specified
by the action statement. Community must be enclosed in double quotes ("").”
Also, add the following note:
NOTE
Multiple communities cannot generally be used in “community
set” attribute in a BGP policy file. However, you can effectively
set multiple communities by using two sets of attributes as
shown in following example:
entry permit-anything-else {
if {
} then {
community set "2342:6788";
community add "2342:6789 2342:6790";
permit;
}
}
ExtremeXOS 15.7 Release Notes
131
ExtremeXOS Documentation Corrections
Synchronize Command
ExtremeXOS Command Reference for the synchronize command
xos0059976
The following text:
“ExtremeXOS software does not allow a synchronize operation on a
SummitStack between a Summit X460 or X670 switch and a Summit
X480 switch. If one is attempted, the following message is displayed:...”
Should be:
“ExtremeXOS software does not allow a synchronize operation on a
SummitStack between a Summit X460 ,X670 or X440 switch and a
Summit X480 switch. If one is attempted, the following message is
displayed:...”
TACACS Server
ExtremeXOS User Guide under Security > Authenticating Management Sessions
Through a TACACS+ Server > Configuring the TACACS+ Client for Authentication
and Authorization
xos0060212
The following new topic should appear, Changing the TACACS+ Server:
To change a TACACS+ server configuration to avoid service interruption with
respect to authentication and authorization:
NOTE
When only a single TACACS+ server is configured, you must
disable TACACS-authorization (if enabled) before reconfiguring
the TACACS+ server.
1 Unconfigure existing primary TACACS+ server (the TACACS+ server will failover
to the secondary server) by issuing the following command:
unconfigure tacacs server [primary | secondary]
2 Configure new primary TACACS+ server by issuing the following command:
configure tacacs [primary | secondary] server [ipaddress |
hostname] {tcp_port} client-ip ipaddress {vr vr_name}
ExtremeXOS 15.7 Release Notes
132
ExtremeXOS Documentation Corrections
3 Configure the shared-secret password for the primary TACACS+ server by issuing
the following command:
configure tacacs [primary | secondary] shared-secret
{encrypted} string
NOTE
Only after configuring the shared-secret password for the
primary server, TACACS+ will fallback to primary server from
secondary.
4 Unconfigure the existing secondary TACACS+ server by issuing the following
command:
unconfigure tacacs server [primary | secondary]
5 Configure the new secondary TACACS+ server by issuing the following
command:
configure tacacs [primary | secondary] server [ipaddress |
hostname] {tcp_port} client-ip ipaddress {vr vr_name}
6 Configure the shared-secret password for the secondary TACACS+ server by
issuing the following command:
configure tacacs [primary | secondary] shared-secret
{encrypted} string
NOTE
The command disable tacacs is not required while changing
TACACS+ servers, and it is recommended to “disable tacacsauthorization” (if enabled), before disabling TACACS+.
ExtremeXOS 15.7 Release Notes
133
ExtremeXOS Documentation Corrections
ExtremeXOS 15.7 Release Notes
134
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertising