Enterasys SSR-GLX70-01 Instrukcja Użytkownika Pobierz pdf (Strona 17)

ISSUES RESOLVED IN E8.2.1.1

10/24/01 P/N: 9038090-17 CUSTOMER RELEASE NOTES Page: 17 of 34

F0615-F Subject to Change Without Notice

SmartTRUNK I.D.

In E8.1.0.0 and later releases, secondary SmartTRUNK ports are incorrectly forced into the blocking

state when their links come up. It takes up to 30 seconds before these ports can settle to the correct

STP state, resulting in lost traffic during that time frame. This issue was resolved in E8.1.0.7.

F1162

F1163

When a physical port in a SmartTRUNK is disconnected, the learned Layer-2 table entries are

removed from the disabled port. As a result, Layer-2 activities will increase. This issue was resolved

in E8.1.0.7.

F1261

F1297

BPDUs may incorrectly display the same cost for SmartTRUNK ports with different link speeds. F1423

SmartTRUNK links may be affected when the Huntgroup protocol is enabled on SmartTRUNKs

while the Control Module is too busy to send or receive Huntgroup PDUs.

NOTE: This issue was resolved in conjunction with a timer fix used to correct a VRRP packet delay

issue. For more information, please see “VRRP” on page 19 of these Release Notes.

F1433

SmartTRUNKs may prematurely age-out Layer-2 table entries, causing those entries to be

relearned at 5 minute intervals.

F1612

Specifying an uncreated SmartTRUNK through the smarttrunk lacp aggregator command (Active

configuration) will cause the X-Pedition to crash.

F1746

Spanning Tree Protocol (STP) I.D.

Command conflicts between BPDU filtering and enabling STP on ports are not adequately detected.

NOTE: With this release, the system will now detect these conflicts and give the user an opportunity

to correct them. This issue was resolved in E8.2.0.2.

F1149

A core dump may occur on an X-Pedition running System Firmware version E8.1.2.0 or higher when

a spanning-tree packet is received on a WAN port connected to another router using System

Firmware version E8.1.0.6 or lower.

NOTE: This issue does not occur when the routers on both ends of a WAN connection are using

System Firmware prior to versions E8.1.0.6 and E8.1.2.0. In addition, this does not occur with any

System Firmware versions E8.2.X.X. This issue was resolved in E8.1.0.7.

F1428

If a topology change occurs, and an X-Pedition is the root bridge both before and after the change,

the X-Pedition will send out a new root bridge trap regardless of its previous function as the root.

This issue was resolved in E8.1.0.7.

F1437

The stp filter-bpdu all-ports command will not apply BPDU filtering to newly hot-swapped

modules. In order to filter BPDU from new modules, the user should either comment this command

out and back in, or negate and re-enter it. This issue was resolved in E8.1.0.9.

F1468

Changes in STP root bridge variables (example: hello_time, forward_delay, max_age) will not be

detected by non-root routers. This causes the X-Pedition to continue sending a TCN BPDU to the

root bridge until the variables are returned to their original values. This issue was resolved in

E8.2.0.1.

F1490

The X-Pedition will continue to forward VLAN-tagged BPDUs on a Q-trunk when STP is disabled.

This issue was resolved in E8.2.0.3.

01630

The stp enable port command fails to initialize STP on some ports when multiple ports are

specified.

F1687

BPDU filtering fails after a port is added to a VLAN. This issue was resolved in E8.2.0.3. 01691

Statistics I.D.

The “In-errors” field, produced through the statistics show ip-interface all command, displays

inaccurate information.

F1751

1 2 ... 12 13 14 15 16 17 18 19 20 21 22 ... 33 34

Komentarze do niniejszej Instrukcji

Brak uwag

Enterasys SSR-GLX70-01 Instrukcja Użytkownika Strona 17

Komentarze do niniejszej Instrukcji

Powiązane produkty i podręczniki dla Networking Enterasys SSR-GLX70-01