Enterasys Networks X-PEDITION E9.1.7.0 - Manual (Page 20)

ISSUES RESOLVED IN E9.1.7.0
10/02/03 P/N: 9038090-53 Subject to Change Without Notice Page: 20 of 31
F0615-J
Hot Swap I.D.
Under rare circumstances, the system may occasionally core when hot swapping a line card into the
router. F2333
Internet Protocol (IP) I.D.
If an X-Pedition with ip enable reverse flow all configured receives an invalid TCP/UDP packet of a
specific type, the router may core. F4345
Layer-4 I.D.
An X-Pedition configured with Layer-4 bridging will respond incorrectly to an ICMP request that is
not destined for the router. F4359
F4297
Link Aggregate Control Protocol (LACP) I.D.
LACP SmartTRUNK connections that use either the default timeout value or the “short” timeout
value may not successfully restore the connection with another system that has rebooted. F4405
F3910
Load Balancing I.D.
The load-balancing group and server options app-int and ping-int will not function properly if set to
a value greater than 255. F4421
Memory I.D.
When a user adds ports to a SmartTRUNK via the smarttrunk add ports <portlist> to <smarttrunk>
command, a small memory leak may occur if the command fails. F4443
If an X-Pedition SSH client using SSHv1 fails to connect to a remote SSH server during the key
exchange phase, the router may leak up to several hundred bytes of memory (based on system
configuration). F4456
Multicast I.D.
When a multicast index changes, some flows may not update to the new index, causing the
X-Pedition to send untagged flows over a Q-trunk. F3794
UDP multicast packets with a TTL=1 cause the X-Pedition to allocate Q-trunk replication indices
without an associated hardware flow. F4446
Open Shortest Path First (OSPF) I.D.
Under extremely rare circumstances, the X-Pedition may core if it attempts to calculate the SPF on
an entry that is no longer valid when the router adds or deletes large amounts of OSPF ASE routes. F4273
The default route is missing from the route table for a stubby or totally stubby area. F4554
Protocol Independent Multicast (PIM-SM) I.D.
An unlikely sequence of route changes may cause the X-Pedition to core. F3283
F3758
If the X-Pedition’s configuration contains the pim igmp trace local-options none and ip-router
global set trace-state on commands, PIM IGMP trace messages continue to display on the screen. F4313