12 CHAPTER 3: RELEASE ISSUES FOR INTERFACE MODULES
5 If you are going to leave the slot empty, cover it with a blank faceplate
to ensure proper airflow and cooling in the chassis.
Do Not Configure
When a Module Is
Removed
■ If you remove any interface module that contains ports assigned to a
VLAN (other than VLAN 1), subsequently make configuration changes
that are written to NVRAM (such as enabling STP), and then re-insert
the module, the module will be reset to factory defaults, whereby all
ports are returned to the default VLAN.
However, once you bind an IP interface to a VLAN, that interface will
be removed if you delete the VLAN through the management
interface.
Known Problems This section describes known problems that apply to Interface Modules at
this release.
System
■ At the Administration Console, entering a seemingly valid command
string (two or more commands taken from menus and nested
submenus) may not work. If this situation occurs, enter commands
separately from one menu prompt at a time.
VLAN Configuration
■ If you remove and then re-insert a module into the same slot, the
module may be reset to factory defaults, whereby all ports are
returned to the default VLAN.
■ When a module has several VLANs, and is moved to another slot, and
then back to the original slot, all VLAN settings for the module are
erased.
SNMP Management
■ Static routes cannot be created or removed via the MIB.
■ RIP Receive Mode cannot be disabled via the MIB.
■ The a3ComVlanIfTable is not implemented in this device. Please use
the dot1qVlanStaticTable to create an manage VLANs via the MIB.
■ At the present time, SNMP download of Switch Fabric Management
Module (SFMM) software is not supported.
Web-based
Management
■ Not all commands provided by the command line interface are
available through the Web interface. For example, you cannot create
multiple IP interfaces for a single VLAN through the Web interface.
