ISSUES RESOLVED IN E8.2.1.1
10/24/01 P/N: 9038090-17 CUSTOMER RELEASE NOTES Page: 13 of 34
F0615-F Subject to Change Without Notice
Internet Packet Exchange (IPX) I.D.
When using a non-Ethernet II encapsulation type for IPX traffic, a novel client may not be able to
communicate with its server for several minutes after a reboot; the X-Pedition may be using the
wrong frame type for some SAP packets. This issue was resolved in E8.2.0.1.
F1375
With this release, IPX task priorities have been changed, and the following situations will no longer
cause a core dump:
• Actions on ports with IPX configured (example: losing a link)
• Hot-swapping a module with configured IPX interfaces
This issue was resolved in E8.1.0.10.
F1498
Layer-3 I.D.
When an exit port is disconnected, flows will not be removed if traffic directed toward the
disconnected port does not decrease. This results in improper failover to other/backup routes. This
issue originally appeared in E8.0.1.2, and was resolved in E8.1.0.11.
F1582
F1588
Layer-3 traffic may encounter difficulties with efficient flow setup. This issue originally appeared in
E8.1.0.4, and was resolved in E8.1.0.12.
F1827
Layer-4 Bridging I.D.
When enabling Layer-4 bridging (vlan enable l4-bridging on xxx) on a VLAN containing
SmartTRUNKs, duplicate packet issues may occur.
Example: A packet going into st.1 will emerge from st.2 twice.
F1234
When Layer-4 bridging is enabled on both IP and IPX VLANs located on same port(s), the X-
Pedition may core dump while trying to delete a Layer-3 IPX flow entry during aging. This issue was
resolved in E8.1.0.9
F1287
When using Layer-4 bridging, a 'tcp-established' ACL will not function properly. This issue was
resolved in E8.1.0.7.
F1455
Layer-4 bridging hardware flows will be deleted (age-out) every 5 minutes when using the GMAC or
OCMAC chipsets. This issue was resolved in E8.2.0.3.
F1636
Link-Aggregation Control Protocol (LACP) I.D.
LACP advertisement packets will not transmit correctly if an LACP SmartTRUNK contains ports in
the lower channels only.
F1510
With this release, LACP has progressed from a static implementation to a dynamic implementation
more closely reflecting the 802.3ad standard; this is due to the dynamic configuration of LAGs and
link allocation.
F1536
Multicast I.D.
Adding a SmartTRUNK to a VLAN containing a multicast source will stop multicast traffic from
routing. This issue was resolved in E8.1.0.10.
F0942
Multicast traffic does not pass correctly across Q-trunks on 1000Base-SX and 1000Base-LX (fiber
gigabit) ports, or 10/100Base-TX (copper gigabit) ports. This issue was resolved in E8.1.0.10.
F1571
Multicast group joins that appear on the same port as multicast traffic will prevent any subsequent
client attempting to join (on the same line card) from receiving traffic.
F1576
(5 pages)
Manymanuals.com
Manymanuals.de
Manymanuals.fr
Manymanuals.it
Manymanuals.pl
Manymanuals.cz
Manymanuals.es
Manymanuals-pt.com
Commentaires sur ces manuels