Enterasys SSR-GLX70-01 Manual de usuario Pagina 25

  • Descarga
  • Añadir a mis manuales
  • Imprimir
  • Pagina
    / 34
  • Tabla de contenidos
  • MARCADORES
  • Valorado. / 5. Basado en revisión del cliente
Vista de pagina 24
KNOWN RESTRICTIONS AND LIMITATIONS
10/24/01 P/N: 9038090-17 CUSTOMER RELEASE NOTES Page: 25 of 34
F0615-F Subject to Change Without Notice
Routing I.D.
Aggressive internal testing has uncovered a weakness in some configurations containing static
routes. Configurations using only dynamic routing are unaffected.
Erroneously configured static routes may produce a routing loop. As a result, excessive CPU
utilization can occur when an improperly configured upstream router sends ICMP redirect messages
to a downstream router. It appears this problem has been present in the Enterasys Networks
System Firmware since the 2.1.0.0 release.
Routing protocols (e.g. OSPF, BGP, RIP) automatically discover and correct any loops in dynamic
routing configurations. In these cases, no excessive CPU utilization will occur.
Simple Network Management Protocol (SNMP) I.D.
Sets to dot1qPvid in the Q MIB will fail for ports on line cards that do not support Layer-4 bridging. F1020
Querying for dot1dStpPortEntry MIBs will return incorrect values for STP-disabled ports. In addition,
querying for the constant dot1dStpHoldTime will return “0” rather than “1”.
F1093
VLANs created via the CLI with names containing spaces cannot be modified using the IETF Q MIB.
Workaround: Remove spaces from VLAN names.
F1245
The use of the snmp set target command has changed in E8.2.0.0. It is now allowed to configure
multiple targets with the same IP address and different community strings. Traps will not be sent to
a target if the community string specified on the target is not configured.
F1258
Attempting to set the dot1qPvid MIB on a PVST enabled port should produce an error. At this time it
does not.
F1260
Attempting to set the dot1qPvid MIB for a port that has been forbidden from that VLAN should
produce an error. At this time it does not.
F1446
SmartTRUNK I.D.
Huntgroup protocol supports up to 256 ports. In the ER16, Huntgroup protocol is supported only for
modules in slots 1 through 7. SmartTRUNK without Huntgroup protocol is supported for all modules.
F0480
BPDU may incorrectly display the same cost for SmartTRUNK ports with different link speeds. F1423
Hot-swapping a line card several times will change the default Layer-2 aging time. A port on the line
card in this condition may not be added to a SmartTRUNK port.
08724
Spanning Tree Protocol (STP) I.D.
BPDU filtering fails on all ports after any port-mirroring command is negated.
Workaround: After negating a port-mirroring command, negate and then re-enter the stp bpdu
filtering command to turn BPDU filtering back on.
F1722
The X-Pedition does not recognize (and subsequently will not filter) VLAN-tagged BPDUs. When
such a BPDU is received, it will be learned and forwarded as a normal Layer-2 packet.
Because E8.2.0.2 and releases prior to it will VLAN-tag BPDUs when STP is disabled, System
Firmware version E8.2.0.3 and above should be used on any X-Pedition with a Q-trunk connection.
F1726
Statistics I.D.
The statistics show port-errors command incorrectly reports greater-than-1518-byte frames as
Cyclic Redundancy Check errors.
F1388
Vista de pagina 24
1 2 ... 20 21 22 23 24 25 26 27 28 29 30 ... 33 34

Comentarios a estos manuales

Sin comentarios