Cisco Cisco MDS 9000 NX-OS Software Release 6.2 Notas de publicación
35
Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 6.2(3n)
OL-29201-05
Caveats
Condition: This issue only affects FCSP encrypted ports on MDS 9700 DS-X9448-768K9 and MDS
9500 DS-X9248-256K9 and DS-X9232-256K9 switching modules after an ISSU or ISSD to an
affected version of NX-OS.
9500 DS-X9248-256K9 and DS-X9232-256K9 switching modules after an ISSU or ISSD to an
affected version of NX-OS.
Workaround: Only a switch reload will recover from this situation. The switch must be running a
fixed release of NX-OS (NX-OS 6.2(11) or above) before the reload to prevent the issue from
recurring after recovery.
fixed release of NX-OS (NX-OS 6.2(11) or above) before the reload to prevent the issue from
recurring after recovery.
None of the following steps alone will not recover the port functionality:
–
Shut/no-shut the affected port.
–
Reloading the affected linecard.
–
Removing the FCSP configuration and re-configuring FCSP.
–
Upgrading to NX-OS 6.2(11) or above.
•
CSCtr50223
Symptom: On the MDS 9513 switch, when an MSM-18/4 module boots up, it sends a request to the
supervisor module to mount the modflash on the MSM-18/4 module. If there is a timeout or error in
response, the following syslog message displays:
supervisor module to mount the modflash on the MSM-18/4 module. If there is a timeout or error in
response, the following syslog message displays:
2011 Jul 14 01:18:13 sw-dc5-br2-12 %LC_MNT_MGR-SLOT3-2-LC_MNT_MGR_ERROR: SUP mount
failed. MTS receive timedout
2011 Jul 14 01:19:06 sw-dc5-br2-12 %PROC_MGR-SLOT3-2-ERR_MSG: ERROR: PID 1144
(lc_mnt_mgr) exited abnormally, exit status (0xa)
2011 Jul 14 01:19:06 sw-dc5-br2-12 %MODULE-2-MOD_MINORSWFAIL: Module 3 (serial:
JAE1141ZB43) reported a failure in service lc_mnt_mgr
This issue might be seen when the supervisor module is unusually busy and cannot process the
mount request from the MSM-18/4 module, or the actual mount command on the supervisor takes a
long time.
mount request from the MSM-18/4 module, or the actual mount command on the supervisor takes a
long time.
Workaround: Reload the MSM-18/4 module in the same slot/module where the modflash mount
failed. A request will be sent to the supervisor to mount the modflash.
failed. A request will be sent to the supervisor to mount the modflash.
•
CSCub40020
Symptom: After an In Service Software Upgrade (ISSU), In Service Software Downgrade (ISSD),
or supervisor switchover, devices fail to FLOGI into the switch, and the following error is logged in
the syslog:
or supervisor switchover, devices fail to FLOGI into the switch, and the following error is logged in
the syslog:
%FLOGI-1-MSG_FLOGI_REJECT_FCID_ERROR after upgrade/switchover
Condition: This situation occurs if one or all of the following occur:
1.
The Max flogi key is greater than 65535. The key can get this high if there are repeated FLOGIs
on an interface. After the key exceeds 65535, this issue occurs. However, this situation does not
impact end devices.
on an interface. After the key exceeds 65535, this issue occurs. However, this situation does not
impact end devices.
2.
If a supervisor switchover, such as ISSU, ISSD, or system switchover occurs when the key is
greater than 65535, Fibre Channel Identifiers (FC IDs) can be dropped from the FLOGI table.
The end devices continue to function normally until they are logged out and then attempt to
relogin.
greater than 65535, Fibre Channel Identifiers (FC IDs) can be dropped from the FLOGI table.
The end devices continue to function normally until they are logged out and then attempt to
relogin.
3.
If after both 1 and 2 above have occurred and then an end device is rebooted on the affected
interface, that end device might not be able to log back in.
interface, that end device might not be able to log back in.
Workaround: You must first resolve the issue with the device on the interface with the Max flogi
key over 65535, such as FLOGI rejects or port security, to prevent the FLOGI key from
incrementing.
key over 65535, such as FLOGI rejects or port security, to prevent the FLOGI key from
incrementing.