Cisco AP776A - Nexus Converged Network Switch 5020 Примітка до випуску - Сторінка 21

Переглянути онлайн або завантажити pdf Примітка до випуску для Перемикач Cisco AP776A - Nexus Converged Network Switch 5020. Cisco AP776A - Nexus Converged Network Switch 5020 26 сторінок. Cisco nexus 5000 series release notes release 4.1(3)n1(1) (ol-16601-01 h0, july 2009)
Також для Cisco AP776A - Nexus Converged Network Switch 5020: Примітка до випуску (48 сторінок), Примітка до випуску (44 сторінок), Примітка до випуску (26 сторінок), Примітка до випуску (22 сторінок), Короткий довідник (14 сторінок), Примітка до випуску (3 сторінок)

Cisco AP776A - Nexus Converged Network Switch 5020 Примітка до випуску
S e n d d o c u m e n t a t i o n c o m m e n t s t o n x 5 0 0 0 - d o c f e e d b a c k @ c i s c o . c o m
Resolved Caveats—Cisco NX-OS Release 4.0(1a)N1(1)
This section lists the resolved caveats for this release.
OL-16601-01
CSCsu66201
Symptom: If the name server IP address is unreachable, the TACACS daemon gets stuck trying to
resolve the server names. While it is stuck, TACACS commands, including common commands such
as show running-config and copy running-config startup-config, are not processed.
Workaround: Fix the network connectivity to the name server IP address.
CSCso65934
Symptom: Virtual interfaces are created by specifying the interface name in configuration mode. If
the interface does not exist, the system creates the interface, and then enters interface configuration
mode. If the user role prohibits access to that interface, this CLI is rejected and the user does not
enter interface configuration mode, although the interface is created. Similarly, if a user does not
have access to a virtual interface, the interface can still be deleted with the no interface command.
Workaround: None.
CSCso82992
Symptom: Delete and insert role scopes for a role may fail and display the following error:
entry already exists
The problem occurs when you execute the following steps:
Delete all role scopes for a role.
Insert new role scopes for the same role.
Workaround: Repeat the above steps once again.
CSCso91286
Symptom: When TACACS+ authentication is used to authenticate AAA users using ACS, the Cisco
Cisco Nexus 5000 Series switch ignores the user to role binding information specified in theACS.
Users are logged in with their default roles. The default role for a new user is network-operator and
for a user who is an administrator is network-admin.
Workaround: The user-to-role binding needs to be configured locally on the Cisco Nexus 5000
Series switch for the role binding to take effect.
CSCsu32247
Symptom: The Cisco Nexus 5000 Series switch executes the power on self test (POST) at bootup
to validate hardware integrity of the ASICs. When a Fibre Channel port is connected to an HBA,
the HBA driver could assert a LOS that causes a false failure to be reported by POST for one of the
ASICs. As a result, all the ports serviced by the ASIC on the GEM are marked for hwFailure.
Workaround: Bypass POST at bootup by performing the following steps:
switch(config)# diagnostic bootup level bypass
switch(config)# copy running-config startup-config
switch(config)# reload
CSCsv05115
Symptom: The Cisco Nexus 5000 Series switch crashes if CFS callhome is enabled on a it after a
CFS callhome commit is performed on an attached MDS.
Cisco Nexus 5000 Series and Cisco Nexus 2000 Series Release Notes, Release 4.1(3)N1(1)
Caveats
21