Release Notes G.07. 53
Software Fixes
Release G.07.27 9/05/03
IRDP (PR_98092) — IRDP (ICMP Router Discovery Protocol) did not return a router
address to the requesting PC.
LACP (PR_98026) — Dynamic active or passive LACP ports do not aggregate into the trunk
group resulting in STP loops.
Mgmt (PR_96924) — Device unmanageable when heavily loaded with software routing.
POST (PR_98922) — Known good module fails to come up under heavy stress conditions.
Routing (PR_94958) — Routing performance degrades after 10 minutes of continued
traffic. Traffic was being routed in software due to a prematurely aged out MAC entry. ARPs
will now be sent out 1/minute to reinstate a proper MAC entry with a valid ARP entry.
Routing (PR_95616) — Packets dropped when routing packets from a Trunk Group and
the destination is the same Trunk Group.
STP (PR_97602) — Trunking & RSTP enabled, broadcast storm
Trunks (PR_90615/91727) — Traffic not forwarding on a trunk group using ports from 2
modules.
Web (PR_82157) — On a “First Time Install” instance of the web interface, missing graphic
on the pop up window.
Web (PR_90858) — “VLAN Name” text field won't clear after 12 characters are entered.
Web/CLI (PR_89900) — Though the Web UI reports excessive CRC/Alignment errors, these
errors were not recorded by CLI port counters.
Release G.07.27 9/05/03
WEB (PR_82530) — Browsers running with Sun Java versions 1.3.x can result in the
browser closing. Sun Java versions 1.4.x can result in very high CPU utilization in the switch,
which causes problems for protocol processing (e.g. STP, IGMP, CDP, console, etc.) and other
processes that require the CPU.
Release G.07.26 8/13/03
ARP (PR_91694) — When port monitoring is enabled, the switch does not forward
broadcast ARPs out all ports.
Trunks (PR_91727) — Connectivity problems when a trunk is connected to different
modules in the same switch.
16