Specifications

80 ExtremeWare 7.4.3 Installation and Release Notes
Clarifications, Known Behaviors, and Resolved Issues
Spanning Tree Protocol
All ports of a default VLAN are now shown as part of the default STP domain s0 on an Alpine switch
(PD3-27096541).
Stacking
When eight Summit 200 switches are connected, stack formation no longer fails (PD3-26798611).
Clearing a console session on a slave slot now functions properly (PD3-26482929).
Layer 2 forwarding is no longer affected if a slot with a load share link is rebooted (PD3-27134464).
On a Summit 200-48t switch, load sharing traffic is no longer sent on the master port only
(PD3-21484658).
In a two switch stack, the switch no longer stops responding when issuing any of the following CLI
commands:
enable stp
disable stp
enable vrrp
disable vrrp
enable eaps
(PD3-25926111)
If a stack reboots while multicast streams are on, after the formation of the stack, tStackTask and
tNetTask no longer show high CPU utilization (PD3-28633931).
If a stack reboots while the multicast streams are on, it no longer takes a considerable amount of time to
form the protocol adjacencies (PIM, RIP, and OSPF) (PD3-28632362).
On the slave switch, the link status no longer shows as active even after disabling the port
(PD3-28831248).
The number of active ports displayed after a save and reboot is now correct (PD3-26925793).
Stacking port information in ifTable is now accurate (PD3-26629639).
The display for interface type for stack port is now correct in the interfaceEntry MIB table
(PD3-26654772).
The link speed for the stack port displays in the interfaceEntry MIB table (PD3-26654788).
Change in the link status trap is no longer missed (PD3-26752662).
Summit switches that are used as a stack master switch no longer cause traffic to stop forwarding and
the switch to reboot after a watchdog timer reset (PD3-26784871).
SNMP
When exercising the route table in the FDB MIB with dot1dTpFdbTable enabled, high CPU utilization
messages are no longer displayed in the syslog (PD2-102926801).