Specifications

Clarifications and Known Behaviors
ExtremeWare 7.3.1b3 Release Notes 65
• Static FDB entries
If the switch reaches the limit of available port tags, the following messages appear in the syslog:
<WARN:HW> tNetTask: Reached maximum otp index allocation
<WARN:HW> tBGTask: Reached maximum otp index allocation
If this occurs, you must compromise some features (for example, mirroring) in order to expand your use
of other functionality. (1-E5U7Y).
WinSCP2 Not Supported
The application WinSCP2.exe is not supported. Using WinSCP2 does not cause any problems
(1-A5C6C).
BlackDiamond
Secondary MSM Access Error
The following access error might be logged in the show diagnostics command output while the
secondary MSM is in the reset state after running the
synchronize command:
07/14/2004 14:51:50.00 <Crit:ENG> ENG: trxdiag: Twister access on MSM-B failed
(tmp=31)
This does not affect switch performance and there is no need for any hardware replacement
(PD3-1437438, PD3-1437361).
Loopback Port Must be on Same Module on a BlackDiamond Switch
The loopback port must be on the same module as the rate shaped ports. Though you can configure a
loopback port on another module, this is still not a supported configuration. This applies to
BlackDiamond switches only (PD2-124299901).
Two Trap Messages Sent for Hard Reset/Soft Reset on BlackDiamond 6816
When performing a hard reset/soft reset on a BlackDiamond 6816 with SNMP traps configured, two
SNMP traps are sent. On the BlackDiamond 6816 this behavior occurs repeatedly with both MSM-A and
MSM-B having MSM3s (PD3-1135809).
Targeted LDP Sessions Become Operational When MPLS is Disabled
Issuing the command, show mpls ldp, might display operational targeted LDP sessions, even on
switches with MPLS disabled. The TLS tunnel VC state is displayed as “Complete” and the LSP state is
displayed as “Down.” No traffic traverses the tunnel. There is no workaround (PD2-229043816).
BGP Fast Fail-over Does Not Work for Change of IP Address
If a BGP session exists with fast-failover enabled and the connection has been established with large
keepalive and hold timer values, if you change the IP address, BGP will continue to stay in the
established state until the hold timer expires.