Specifications

ExtremeXOS 12.4.1 Release Notes

2 Limits

This chapter summarizes the supported limits in ExtremeXOS 12.4.1.

Supported Limits

Table 38 summarizes tested metrics for a variety of features, as measured in a per-system basis unless

otherwise noted. These limits may change but represent the current status. The contents of this table

supersede any values mentioned in the ExtremeXOS Concepts Guide.

NOTE

The term “BlackDiamond 8000 e-series” refers to all BlackDiamond 8500 e-series and 8800 e-series modules.

NOTE

The term “BlackDiamond 8000 series” refers to all BlackDiamond 8500, 8800, and 8900 series modules.

NOTE

The scaling and performance information shown in Table 38 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.

NOTE

The route limits shown in Tab le 38 for IPv4 and IPv6 routing protocols are software limits only. The actual hardware

limits may be 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.

NOTE

On certain BlackDiamond 8000 and Summit products, it is not advised to have greater than 25,000 total IP routes

from all routing protocols. This includes a BlackDiamond 8000 series switch with an 8500-MSM24, MSM-G8X or

MSM-48, and Summit X250e, X450, X450a, X450e, or X650 switches, either in a SummitStack or standalone.

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.