Dell PowerConnect 7024 Примітки до випуску - Сторінка 23
Переглянути онлайн або завантажити pdf Примітки до випуску для Перемикач Dell PowerConnect 7024. Dell PowerConnect 7024 27 сторінок. Upgrading from version 2.x.x.x or 3.x.x.x or 4.x.x.x or 5.x.x.x to 5.1.9.3 firmware
Також для Dell PowerConnect 7024: Оновлення прошивки (24 сторінок)
Друкувати сторінку
PowerConnect M6220/M6348/8024/8024F/M8024/M8024-k/
7024/7048/7024P/7048P/7024F/7048R/7048R-RA Release Notes
Known Issues
Summary
DUT delivers more
power than the PD
requested via LLDP in
high power mode.
L3 routing NSF failover
data plane on dynamic
LAG - loss duration up
to 5 seconds for large
configurations
Trunk mode VLANs
transmit tagged frames
only
Speed/duplex
commands available for
interfaces which require
auto-negotiation
ST : Stack member
response times to ICMP
ping requests in a 12
unit stack are larger
than for stack master
Issue with protocol
based VLAN
configuration
migration.
Read/write user allowed
read only access when
authentication method
is used as TACACS.
TFTP gives no reason
for file download
failures.
CLI command stack-
port config rejection
does not display the
cause.
The 'acct-port'
command does not have
'no' version.
System Firmware Version 4.1.0.6
User Impact
DUT may draw more power than negotiated at
short cable lengths. PD may draw more power
than negotiated, but power loss due to cable
impedance is compensated for so that devices
with average or longer cable length will receive
adequate power.
Interruption of voice, video and data service for
duration of loss. Data plane loss during failover
should not exceed 50 ms.
Not compatible with other vendors trunk modes.
Confusion about how to configure links.
No user impact expected. Observed occasional
outlier response time up to 500 ms for stack
members in a large stack configuration with
heavy traffic. Average response time is well
under 100 ms for stack members. All response
times are well within ping limits.
The command vlan protocol group required a
string parameter in earlier versions; now it
requires an integer parameter.
The user always gets Read-Only access if using
TACACS as a means for HTTP authentication,
even if the TACACS user is Read/Write capable.
Generic failure message is issued.
If a user enters an invalid interface, a generic
error message is issued.
The user can configure the acct-port to the
default using the positive form of the command
Workaround
None – system assumes 5.8W average loss
due to cable length and delivers 5.8W extra
power to ensure device receives requested
power.
Disable portfast and auto-portfast on physical
ports configured in a LAG.
Administrators can configure "general" mode
VLANs, which transmit PVID frames
untagged and all other VLAN frames tagged.
General mode is compatible with other
vendor's trunk mode behavior.
Documentation and CLI prompt clearly states
which commands are applicable to which
interfaces. Only use speed/duplex commands
on fiber interfaces. Only use speed
auto/duplex auto commands on copper
interfaces.
None required.
The software recognizes if the group name is
alphanumeric, however it will not work when
the name of the group is numeric (for example
2, 3, etc.).
User can configure the same TACACS user
locally and use LOCAL authentication
method for HTTP. The user will be able to get
access based on the local user access level
(Read-write or Read-only).
Administrators can ping the TFTP server from
the switch. Administrators should ensure the
TFTP server is available, the requested file is
available, and the permissions are set
correctly.
Utilize the show stack-port command to
identify stack port configuration issues.
Configure the acct-port to the default using
the acct-port 1813 command in Radius
accounting mode.
Page 21