Filter
Top Products
24 COREBUILDER 6000 EXTENDED SWITCHING SOFTWARE REVISION 8.2.3
■ 3Com recommends that you hot-swap one module at a time (except FESMs
and FSMs, as described in the previous System Issue). After you hot-swap
one module, wait until the system completes full initialization before you
install another module. One indication that initialization is complete is that
the Administration Console prompt appears. Under certain circumstances,
hot-swapping during initialization can cause a cold system boot, disrupting
bridging.
■ When the first FDDI MAC address of an FSM is assigned to the backplane,
FDDI ports are renumbered.
■ A maximum of four interfaces per system may have RMON group Host or
RMON group Matrix enabled. A maximum of two interfaces per module can
have RMON groups enabled.
■ The ESM supports only RMON groups 1 through 4.
■ Packet filtering on the transmit path is not available on frames that are
routed by the CoreBuilder system.
■ Roving Analysis is not supported on a port with an assigned IP router
interface.
■ Roving Analysis is not supported on the FESM.
■ A Roving Analysis frame over a remote TMM-FE connection is truncated if
the frame is greater than 1495 bytes.
■ When configuring Roving Analysis on an ESM, the system accepts an
unknown MAC address as the analyzer port.
■ Bridging performance and routing performance are degraded on a Roving
Analysis monitor port, or if RMON Host or Matrix groups are configured.
■ EFSM packet filters can access packet data through byte 64 in packet.
■ A maximum of 254 unique RMON Owner descriptions (etherStatsOwner,
historyControlOwner, alarmOwner, and eventOwner) can be configured.
■ When you install revision 8.2.0 of CoreBuilder 6000 Intelligent Switching
software on a LMM+ that is running revision 8.2.3 Extended Switching
software and you have defined non-IP VLANs, you must reset NVRAM
immediately after installing the 8.2.0 Intelligent Switching software into
flash memory. Immediately after the Console displays the message
Installation complete, enter this command:
system nvdata reset