PowerConnect 6224/6224F/6224P/6248/6248P Release Notes
| Description |
|
| User Impact |
|
| Resolution |
| |
|
|
|
|
|
| ||||
| Cannot enter Daylight Saving |
| In summer time configuration page, in |
| In summer time configuration page, | ||||
| Time from Web interface. |
| recursive mode, clock zone field is not |
| in recursive mode, added | ||||
|
|
|
| accepting valid range. |
| appropriate regular expression in | |||
|
|
|
|
|
|
| validation. | ||
| Error message when changing |
| When priority is set through Web interface |
| Upon setting the priority to SNTP | ||||
| SNTP Server Priority from |
| for SNTP Server, and no encryption key is |
| server when no encryption key is | ||||
| Web interface. |
| configured, the system returns an error |
| configured, the key is now submitted | ||||
|
|
|
| message. |
| to the switch. | |||
| Custom Protocol VLAN shows |
| VLAN protocol group if configured for |
| Made modifications to the Switching | ||||
| incorrect VLAN ID. |
| custom protocol using ethertype did not |
| > VLAN > ProtocolGroup web page | ||||
|
|
|
| display the VLAN id in the Switching > |
| in order to resolve the issue. | |||
|
|
|
| VLAN > ProtocolGroup web page. |
|
|
|
| |
| NIM_events prints unknown |
| Unknown characters being displayed are |
| Properly initialized the variable. | ||||
| characters. |
| for the interface name. |
|
|
|
| ||
|
|
|
| <190> MAY 26 05:57:54 |
|
|
|
| |
|
|
|
| NIM[99904544]: nim_events.c(603) 367 |
|
|
|
| |
|
|
|
| %% Component NIM generated interface |
|
|
|
| |
|
|
|
| event Unknown Port Event (39) for |
|
|
|
| |
|
|
|
| interface ?j?????? (639). |
|
|
|
| |
| VLAN protocol groups not |
| Cannot select the protocol group on the |
| Display the group IDs in the list and | ||||
| visible in GUI. |
| Switching > VLAN > ProtocolGroup web |
| corresponding group name below it. | ||||
|
|
|
| page. |
|
|
|
| |
| Second protocol group not |
| In |
| Corrected the display of the | ||||
| shown in OpenManage GUI. |
| configured interfaces were not displayed |
| interfaces. | ||||
|
|
|
| properly. Web page affected Switching > |
|
|
|
| |
|
|
|
| VLAN > Protocol Group Table. |
|
|
|
| |
| Adding VLAN range issues. |
| 1. When adding a range of VLANs | 1. | Corrected the error | ||||
|
|
|
| to VLAN Database from Web |
|
| handling for this scenario. | ||
|
|
|
| Interface, an error message is | 2. | Increased the maximum | |||
|
|
|
| returned when no name is |
|
| length to 250 such that a | ||
|
|
|
| entered. |
|
| comma separated VLAN | ||
|
|
|
| 2. VLAN range is limited to 4 |
|
| list can be configured. | ||
|
|
|
| characters preventing adding |
|
|
|
| |
|
|
|
| certain ranges. |
|
|
|
| |
| Switch gives error message |
| On the interface ethernet CLI command, |
| String is converted to lower case | ||||
| when entered upper case letter |
| switch gives error message when entering |
| before processing. | ||||
| for interface value. |
| interface names in upper case letters. |
|
|
|
| ||
| Custom |
| Valid range of supported ethertypes is not |
| Add supported range in CLI help. | ||||
| does not display configurable |
| mentioned in CLI help. |
|
|
|
| ||
| ethertype value. |
|
|
|
|
|
|
| |
| Captive Portal login does not |
| Captive Portal user can get confused |
| Implemented logic that verifies the | ||||
| display error message for |
| since the login failure is not reported |
| session state. | ||||
| invalid credentials. |
| correctly. |
|
|
|
| ||
| OpenManage Web UI shows |
| Configuring Proxy ARP results in the ARP |
| Corrected the output of the MAC | ||||
| invalid MAC address (all 0s) in |
| Table web page displaying the MAC |
| Address in the ARP Table to be the | ||||
| ARP table. |
| address as all zeros. |
| same as the Dynamic Address | ||||
|
|
|
|
|
|
| Table web page. | ||
| Unable to authenticate a client |
| User authentication does not happen |
| The switch was assuming that the | ||||
| when radius server is given a |
| when there is no default radius server. |
| default named radius server will | ||||
| name |
|
|
|
| always be present. Therefore, when | |||
|
|
|
|
|
|
| no default named server is present | ||
|
|
|
|
|
|
| the switch will attempt to send it to | ||
|
|
|
|
|
|
| the next valid radius server. | ||
|
|
|
|
|
|
|
|
|
|
System Firmware Version 3.2.0.6 | Page 19 |
