Cisco Cisco MDS 9000 NX-OS Software Release 5.2
45
Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 5.2(8d)
Caveats
%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.
If the Max flogi key value is greater than 65535 before any supervisor switchover, ISSU, or ISSD,
use the shutdown and then no shutdown command on the interface. Consequently, the Max flogi
key value must be checked before any supervisor switchover. However, if the supervisor switchover
has already occurred and logging in are failing, you must follow either of these steps:
use the shutdown and then no shutdown command on the interface. Consequently, the Max flogi
key value must be checked before any supervisor switchover. However, if the supervisor switchover
has already occurred and logging in are failing, you must follow either of these steps:
–
Contact Cisco TAC to implement a nondisruptive recovery. This requires special files not
accessible to customers.
accessible to customers.
–
Suspend the VSAN and wait for 5 minutes and then unsuspend the VSAN of the affected devices
on the switch. This action is disruptive to all devices in that VSAN connected to this switch.
on the switch. This action is disruptive to all devices in that VSAN connected to this switch.
More Information: For detailed information about this issue, see the
.
•
CSCuh49283
Symptom: One of the symptoms is observed:
–
A zone member goes offline.
–
A Registered State Change Notification (RSCN) is not sent to zone members.
–
The device-mapping entry, port world wide name (pWWN) associated to a device alias is not
displayed in the Dynamic Port VSAN Membership (DPVM) database.
displayed in the Dynamic Port VSAN Membership (DPVM) database.
–
The show running-configuration ivr command does not display the changes when a device
alias member in an Inter-VSAN Routing zone (IVR zone) is renamed.
alias member in an Inter-VSAN Routing zone (IVR zone) is renamed.