Enterasys Networks E9.1.7.0 Unique Vlan IDs Per Port Number of Ports Per Card, Network Management

Page 24

KNOWN RESTRICTIONS AND LIMITATIONS

 

Multicast

 

 

 

 

I.D.

 

On a non-T-series line card, it is recommended that access ports be used when running a multicast

 

Hardware

 

routing protocol such as PIM or DVMRP, due to the fact that multicast packets can be replicated to

 

Limitation

 

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

Number of Ports Per Card

 

 

 

 

 

 

8

16 (32 on the ER16)

 

 

 

 

 

 

 

 

 

 

 

 

 

 

16

8 (16 on the ER16)

 

 

 

 

 

 

32

1,2, and 4 (2,4, and 8 on the ER16)

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

When using Cisco IP/TV version 3.2, multicast traffic that crosses several consecutive Q-trunk links

 

F4495

 

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

 

 

 

 

I.D.

 

Changing the status of an SNMP target to “disable” (through the snmp set target xxx status

 

F2074

 

disable command) will not disable the target. Instead, it will continue to send traps.

 

 

 

 

 

 

 

 

 

 

Power On Self-Test (POST)

 

 

 

 

I.D.

 

Entering the system set poweron-selftest quick command in the ER16’s configuration causes the

 

F0619

 

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)

 

 

 

I.D.

 

When an IP interface is configured on a VLAN, and configured to run PIM, multicast data traffic

 

F2013

 

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.

 

F2025

 

DVMRP and PIM will not exchange route information or traffic when both exist on the same router.

 

F2161

 

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)

 

F2162

 

without a reboot.

 

 

 

 

 

 

The X-Pedition does not support more than one PIM sparse domain configuration.

 

F2165

 

 

 

 

 

PIM IGMP does not allow for static joins at this time.

 

F2166

 

If multiple WAN Virtual Circuits are added to a VLAN, and an interface is created from that VLAN,

 

F2167

 

multicast traffic will be flooded out both VCs on the interface.

 

 

 

 

 

 

 

 

 

 

 

10/02/03 P/N: 9038090-53

Subject to Change Without Notice

Page: 24 of 31

 

 

 

 

 

 

 

 

 

F0615-J

 

 

 

 

 

Image 24
Contents Customer Release Notes IntroductionGlobal Support System Firmware Specification System Firmware SpecificationRelease Naming Convention Release Naming ConventionRelease Naming Convention Hardware / Boot FIRMWARE/ System Firmware Compatibility Hardware / Firmware CompatibilityExample Part Description SSR-2-SER SSR-2-SER-AASSR-2-SERC SSR-2-SERC-AASSR-PCMCIA SSR-PS-16-DCSSR-PS-8 SSR-PS-8-DCXP-2-SER-AA XP-2-SERC-AAXP-2-SERCE-AA XP-2-SX-AAAPHY-29IR XP-APHY-21XP-APHY-22 XP-APHY-29IRHardware Requirements Hardware Requirements TableXP-2-HSSI-AA SSR-GLX29-02-AASSR-GLX70-01-AA SSR-GSX21-02-AAER16-HSSI-02-CK ER16-SERC-04-AAER16-SERCE-04-A Network Management Software Support Network Management Software SupportNMS Platform Version Part Number Installation and Configuration Notes Installation and Configuration NotesNEW Features and Enhancements in E9.1.7.0 NEW Features and Enhancements in E9.1.7.0Display of the System Fpga Revision New LineGigabit Ethernet ER16-OS16-01 Part Number Connectivity Description Maximum LengthIssues Resolved in E9.1.7.0 Issues Resolved in E9.1.7.0Hot Swap Internet Protocol IPLayer-4 Link Aggregate Control Protocol LacpRemote Authentication Dial-In Service Radius Remote Monitor RmonSecure Shell SSH Simple Network Management Protocol SnmpTerminal Access Controller Access Control System TACACS+ Spanning Tree Protocol STPSyslog SystemKnown Restrictions and Limitations Known Restrictions and LimitationsPower On Self-Test Post Unique Vlan IDs Per Port Number of Ports Per CardNetwork Management Routing Information Protocol RIP Informational Notes and Statements Informational Notes and StatementsCompliance / Standard Support Compliance SupportIeee Standards MIB Support Lacp Ieee Standards SupportIetf Draft Standards Support Draft No TitleIetf Standards MIB Support ATM MIBIetf Experimental MIB Support Frame Relay Standard SupportFddi Standard Support Enterasys Networks Private Enterprise MIB SupportSnmp Trap Support Enterasys Networks Private Enterprise Trap Support