Problems Fixed In V3.0.5 Address Table; Problem Overview; Problem Detail - 3Com 4007 Release Note

36 C 4: R
HAPTER ELEASE
Problems Fixed in
v3.0.5 Address Table
I F S F
SSUES OR WITCH ABRIC
The "instability" issue caused by TCMP messages not being processed
properly in MPLA configurations, has been fixed. Stimulus such as
Address Table MIB walks, or Address Tracker application queries, on any
of the v3.0.0 devices had caused a problem where other "high
availability" features would be forced to adjust as a reaction to
unprocessed TCMP messages. MPLA with TCMP configurations and
allClosed VLANs had problems in this area.
The problem with SNMP GetNext commands not being processed
properly has been partially fixed, such that MAC addresses now return
upon command from the CLI and MIB walk queries. However, general
response time to these queries is slow due to the limitations of the ASIC
and various processes vying for shared resources.

Problem Overview

If SNMP tools like SNMX or GetMany (Jeff Case Tools), are used to
execute address table MIB walks against v3.0.5 code, these requests will
time out at times and not return all MAC addresses requested. The
Transcend Address Tracker application exacerbates this condition and
causes traffic to slowdown, which is recoverable once Address Tracker
query processes are shut down.
Manual requests (from the CLI or Web interfaces) and non-automated
requests do not cause this problem. MAC addresses are returned
smoothly from requests from the CLI or Web interface.

Problem Detail

SNMP applications that query
a3ComSysBridgeVlanPortAddressRemoteAddress
and the other "allClosed VLAN" address table MIBS may cause traffic
slowdowns if issued asynchronously with multiple variable binds as
described below:
Asynchronous requests — an SNMP request that is sent by an SNMP
program before the previous request has been processed, and
responded to, by the EME in the system.
Multiple Variable Binds — SNMP packets should not contain more
than one Get request per SNMP packet. There are no issues with
Synchronous SNMP with one variable bind per SNMP packet.
However, the processing capability of some modules prohibits a timely
SNMP response to the gathering agent, in which case the SNMP
M
ODULES