Dell PowerConnect 6224P Release Notes - Page 22

The RADIUS Server Status web was - 24 port switch

Page 22 highlights

Description Changing Radius Timeout from Web interface inadvertently changes Priority to same value. Radius Servers always show active status. Interface Configuration web page would not allow the user to set the MTU size to zero. PCs or clients do not authenticate after reboot and logging back on (802.1x). Web Display of Rapid Spanning Tree only displays first 10 interface ports Web Global Portfast applies Portfast on trunk switchports IGMP Snooping failing on PC6200 stack of two switches User Impact Changing the Timeout Duration field on the RADIUS Server Configuration web page would also change the Priority field to the same value. The RADIUS Server Status web page was always displaying the server's status as active. Interface Configuration web page restricted the user to configure the IP MTU from 68-9198. Windows Vista clients were not getting reauthenticated after the PC rebooted. The Rapid Spanning Tree Table web page would only display the first 10, and potential incorrect interfaces. Activating global portfast from the Web Interface applies portfast to trunk interfaces (Switching>Spanning_Tree>Global_Settings). When removing portfast globally via the CLI, it will not remove it from trunks. Two copies of DLF/Bcast/Unknown unicast packet will be sent out of the port 1 to 24 if two PC6248 switches are stacked using both the stack ports to form stack trunk. Resolution Correct the API to properly set the RADIUS priority. Retrieved the server status the same as the CLI for each row in the web page display. Changed the weg page IP MTI field do allow the following values to be configured: 0 or 68-9198. Modified the state machine to move to connecting state to trigger the sending of the EAP-REQ packet. Corrected the web page backend API to retireve all of the applicable interfaces. While applying Portfast via the GUI, no check was present to know what the switchport access of a particular interface was hence the portfast was being applied even on trunk switchports. Modified the driver layer to ignore this trunk-id while destroying external trunks. 20 System Firmware Version 3.2.0.6

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34

20
System Firmware Version 3.2.0.6
Description
User Impact
Resolution
Changing Radius Timeout from
Web interface inadvertently
changes Priority to same value.
Changing the Timeout Duration field on the
RADIUS Server Configuration web page would
also change the Priority field to the same value.
Correct the API to properly set the
RADIUS priority.
Radius Servers always show
active status.
The RADIUS Server Status web page was
always displaying the server’s status as active.
Retrieved the server status the same as
the CLI for each row in the web page
display.
Interface Configuration web page
would not allow the user to set the
MTU size to zero.
Interface Configuration web page restricted the
user to configure the IP MTU from 68-9198.
Changed the weg page IP MTI field do
allow the following values to be
configured: 0 or 68-9198.
PCs or clients do not authenticate
after reboot and logging back on
(802.1x).
Windows Vista clients were not getting re-
authenticated after the PC rebooted.
Modified the state machine to move to
connecting state to trigger the sending of
the EAP-REQ packet.
Web Display of Rapid Spanning
Tree only displays first 10 interface
ports
The Rapid Spanning Tree Table web page
would only display the first 10, and potential
incorrect interfaces.
Corrected the web page backend API to
retireve all of the applicable interfaces.
Web Global Portfast applies
Portfast on trunk switchports
Activating global portfast from the Web
Interface applies portfast to trunk interfaces
(Switching>Spanning_Tree>Global_Settings).
When removing portfast globally via the CLI, it
will not remove it from trunks.
While applying Portfast via the GUI, no
check was present to know what the
switchport access of a particular
interface was hence the portfast was
being applied even on trunk switchports.
IGMP Snooping failing on PC6200
stack of two switches
Two copies of DLF/Bcast/Unknown unicast
packet will be sent out of the port 1 to 24 if two
PC6248 switches are stacked using both the
stack ports to form stack trunk.
Modified the driver layer to ignore this
trunk-id while destroying external trunks.