Specifications

Clarifications, Known Behaviors, and Problems
ExtremeWare v6.2.1 Release Notes Page 31
IPX Routing
Tuning
In larger environments, it is helpful to increase the IPX SAP and IPX RIP update intervals to reduce
CPU load (e.g. from default of 60 to 120 seconds).
To increase route stability, you may wish to increase the hold multiplier (default is 3 for 180 seconds), To
modify these parameters use the following CLI commands: (4859).
config ipxrip <vlan name> update-interval <time> hold-multiplier <number>
config ipxsap <vlan name> update-interval <time> hold-multiplier <number>
IPX and Round-Robin Loadsharing
Due to packet sequencing problems, it is not recommended that IPX loadsharing run in conjunction
with the round-robin loadsharing algorithm (8733/9467).
IPX Performance Testing Using Traffic Generators
When using traffic generation equipment to test the wire-speed capability of IPX routing, if entries are
allowed to age out with the ports remaining active, those entries cannot be re-learned on that port and
will not be forwarded at wire-speed. Restarting the port or clearing the FDB will not address this issue.
In a “real-world” IPX environment, clients and servers generally do not lose communication with the
directly attached switch for the FDB entries to age out (9338).
IPX and Bi-Directional Rate Shaping
Bi-directional Rate Shaping is not supported in conjunction with IPX traffic (9226/9153).
Security and Access Policies
RADIUS
When RADIUS authentication is configured on a BlackDiamond switch, upon reboot, the user will see
the following message indicating that the system is initializing before authentication messages will be
transmitted to the configured Radius server(s) (7046):
“Warning: Radius is going to take one minute to initialize.”
TACACS+ and RADIUS
If TACACS or RADIUS is enabled, but access to the TACACS/RADIUS primary and secondary server
fails, the switch uses its local database for authentication.
Server Load Balancing
Default Ping Health Checking
For Transparent and Translational modes, the L3 PING is enabled for all members of a pool when it is
defined. If a server is configured not to respond to ICMP Echo Requests, the server will be marked