Known Problems in Release 3.0.5
61
■
The following MIB objects have write access according to the RFC’s.
However, 3Com implementation does not let you change these values
to anything other than the default value:
■
ifAdminStatus, ipDefaultTTL, etherStatsDataSource, ipRouteAge
■
The Administration Console interface incorrectly displays the following
unsupported trap:
■
MIB-II: Authentication Failure
■
Because the 64-bit counters in the ifXTable are read-only counters,
you cannot reset them. Attempting to do so results in no response
from the SNMP agent, and the values are not set.
■
If you reset the 9-port 1000BASE-SX Gigabit Ethernet Layer 2
Switching Module from the EME, you see MIB II Cold Start and Link
Up traps from the module, but you do not see a Link Down trap. The
normal
Link Up... Link Down... Link Up
sequence has probably
occurred and the module has reset, even though you did not see a
Link Down trap.
Ethernet
■
The following Ethernet statistics are not reset after you enter the
module baseline set
command:
■
rxPeakFrameRate, txPeakFrameRate, rxPeakByteRate,
txPeakByteRate
■
If a bridging loop exists on a switching module or switch fabric
module, output from the
ethernet detail
command can take up to
30 minutes to display. (30080)
Bridging
■
The bridge incorrectly forwards frames that are sent to their own port
MAC address.
■
Once the bridge address table times out, if the MAC address was
learned by a loopback port, ping packets are dropped and the bridge
port stats
same segment discard
counter increases. If the MAC
address was learned by the sourceport, ping packets go through
successfully.You can tell if you have a bad cable by monitoring the
same segment discard
counter. (30250)
Summary of Contents for 4007
Page 10: ......
Page 32: ...32 CHAPTER 3 RELEASE ISSUES FOR MANAGEMENT MODULES...
Page 64: ...64 CHAPTER 5 RELEASE ISSUES FOR LAYER 2 SWITCHING MODULES...
Page 128: ......
