Download Print this page

Network Management - Enterasys X-PEDITION E9.1.7.0 Release Notes

System firmware version e9.1.7.0

Advertisement

Multicast
On a non-T-series line card, it is recommended that access ports be used when running a multicast
routing protocol such as PIM or DVMRP, due to the fact that multicast packets can be replicated to
only one IP VLAN in an 802.1Q trunk port.
On a T-series line card, multicast packets will be replicated to multiple IP VLANs in an 802.1Q trunk
port. The following table summarizes this capability:
Unique VLAN IDs Per Port
When using Cisco IP/TV version 3.2, multicast traffic that crosses several consecutive Q-trunk links
may experience a slight delay when setting up the hardware flows. This can cause the first IP/TV
client on a subnet's Video and Audio stream to be out of sync (by less than 1 second) and the
stream will not play properly on the first try. Stopping or pausing the stream, then restarting it will
usually re-sync the buffers. Other clients on the subnet do not experience delays.

Network Management

Changing the status of an SNMP target to "disable" (through the snmp set target xxx status
disable command) will not disable the target. Instead, it will continue to send traps.
Power On Self-Test (POST)
Entering the system set poweron-selftest quick command in the ER16's configuration causes the
system to display the following errors during "DIAG BOOT TEST":
%DDT-E-MEMORY_ALIASING, Memory error @ 0x70000000 ; Possible aliasing with: 0x70800000
%DDT-E-MEMORY_ALIASING, Memory error @ 0x70000004 ; Possible aliasing with: 0x70800004
%DDT-E-MEMORY_ALIASING, Memory error @ 0x70000008 ; Possible aliasing with: 0x70800008
%DDT-I-MEM_MAX_ERRORS, Max Errors Reached; Suppressing further errors for this test
%DDT-I-MEM_INFO, $Memory Failure : SOPP Memory MAIN DRAM [16775168 bytes]
%DDT-E-SOPP_MEM_TEST, (Slot 5) : SOPP Memory Test : FAILED
%DDT-E-GE_MODULE, GE Module (Slot 5) : FAILED
These errors are incorrect and should be ignored.
Protocol Independent Multicast (PIM-SM)
When an IP interface is configured on a VLAN, and configured to run PIM, multicast data traffic
exiting the interface will be sent on all ports belonging to the VLAN.
PIM-SM and PIM IGMP cannot be enabled on an interface including a SmartTRUNK.
DVMRP and PIM will not exchange route information or traffic when both exist on the same router.
Firmware versions E9.0.5.0 or later do not allow PIM and DVMRP to operate simultaneously.
OSPF-ASE routes and BGP routes may not import into the multicast Router Information Base (RIB)
without a reboot.
The X-Pedition does not support more than one PIM sparse domain configuration.
PIM IGMP does not allow for static joins at this time.
If multiple WAN Virtual Circuits are added to a VLAN, and an interface is created from that VLAN,
multicast traffic will be flooded out both VCs on the interface.
10/02/03 P/N: 9038090-53
F0615-J
KNOWN RESTRICTIONS AND LIMITATIONS
Number of Ports Per Card
8
16
32
1,2, and 4 (2,4, and 8 on the ER16)
Subject to Change Without Notice
16 (32 on the ER16)
8 (16 on the ER16)
I.D.
Hardware
Limitation
F4495
I.D.
F2074
I.D.
F0619
I.D.
F2013
F2025
F2161
F2162
F2165
F2166
F2167
Page: 24 of 31

Advertisement

loading

This manual is also suitable for:

X-pedition series