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

ISSUES RESOLVED IN E9.1.7.0
10/02/03 P/N: 9038090-53 Subject to Change Without Notice Page: 21 of 31
F0615-J
Protocol Independent Multicast (PIM-SM) I.D.
When running PIM in an equal cost multi-path environment, if a multicast traffic link goes down and
comes back up, the client may receive duplicate packets. F4436
If a user comments the pim global start command out of the configuration, the router will write a
Layer-3 drop flow when it receives a new multicast stream. The status of the stream does not
change when the command is commented back into the configuration. F4440
An X-Pedition running PIM-SM will not allow the re-routing of multicast traffic out of the Q-trunk port
on which it was received. Furthermore, the router may assign a multicast stream to an incorrect
replication index F4500
F4523
F4676
If PIM-SM is enabled on an interface associated with a VLAN whose ID is greater than 2,047, the
router may drop packets. F4518
F4463
If a multicast server sends traffic across a Q-trunk to a PIM-SM-enabled router during a reboot, the
client may not receive the packets after the router finishes booting. F4601
F4439
Remote Authentication Dial-In Service (RADIUS) I.D.
An issue was found and corrected that involves users who authenticate through an X-Pedition to a
RADIUS server. Contact Enterasys Networks Global Technical Assistance Center for additional
information. F3720
Remote Monitor (RMON) I.D.
Packet and byte counts for RMON2 tables are inaccurate. F4031
Changing the RMON configuration from rmon set lite| standard| professional default-tables yes
to rmon set lite| standard| professional default-tables no while RMON is enabled may cause the
router to core. F4331
When a user executes the help (?) option for the rmon show packet-capture captured-packets
command, a description is not available for the control-index option. F4386
Secure Shell (SSH) I.D.
The SSH client leaks 136 bytes of memory for each outbound SSH client session established to a
remote SSH server. To reclaim this memory, users must reboot the X-Pedition. F3432
Continuous attempts (in quick succession) to connect to another device via SSH may cause the
router to stop responding. F4234
Simple Network Management Protocol (SNMP) I.D.
The read-only community string may discover a read-write community string when querying
particular MIBs. F3396
The snmp set mib command lists MIBs that users may not enable or disable. F4141
When querying a ctCDP MIB on a VLAN whose ID is greater than 512, the X-Pedition may core. F4303
The X-Pedition implements the any option of the snmp set group command only partially. F4382
SmartTRUNK I.D.
The smarttrunk show distribution command may display statistics for a blocked STP-enabled
SmartTRUNK. F4186
Using the vlan multi-add command to add a non-existing SmartTRUNK port to a multi-VLAN group
will cause the router to core. F4508