Technical data

44 Known limitations and considerations in this release
217316-A Rev 00
Bandwidth management
Filters
• When you enable filters on ports, the filters may affect ports other than those
on which the filters were configured. This problem exists when the Filter
Mode is set to Forward and the Port DefaultAction is set to Drop. For
example, if you enable a filter set on port 9/12, the PC that connects to port
10/12 [8648TX(E)] can no longer send data to networks through which the
default gateway for unknown destinations must be used. However, paths
known locally or through OSPF work correctly. (Q00912316)
ATM
• When you apply filters to an ATM port and set the default port action to drop,
if an ARP entry for the next hop out of an ATM interface times out, the entry
is never relearned and all outbound traffic will be dropped from that interface.
However, if you set the action to forward, the ARP entry never ages and no
connectivity problems occur.
The problem can be fixed by bouncing the ATM port or when ingress packets
are received on the ATM interface or PVC. (Q00818603-01)
• The ATM card becomes disabled after receiving the following error message:
SW ERROR smMsgSend: failed take the wait Semaphore.
(Q00859608)
Caution: For a default VLAN when the aging-timer is set from the CLI,
the VLAN is reflected correctly on Device Manager. When the VLAN is
set from Device Manager, it is reflected correctly in CLI. But for a
non-default VLAN, this is not the case. For example, a change from the
CLI is not reflected in Device Manager, and a change in Device Manager
is not reflected in the CLI.
Since the aging-timer functionality works correctly in the CLI, use the
CLI to change the aging-time field. (Q00915466)