Installation guide

54
Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 5.2(6)
OL-27554-01
Caveats
2012 Jul 12 10:31:56 MDS03 %SANTAP-SLOT3-4-ST_NEAR_MAX_LUNS_PER_HOST: Warning:
Approaching
MAX_LUNS_PER_HOST(256) limit for Host 1:2:3:4:5:6:7:8, DVT
1:2:3:4:5:6:7:8. Existing num luns 230
2012 Jul 12 10:31:56 MDS03 %SANTAP-SLOT3-4-ST_NEAR_MAX_LUNS_PER_HOST: Warning:
Approaching
MAX_LUNS_PER_HOST(256) limit for Host 1:2:3:4:5:6:7:8, DVT
1:2:3:4:5:6:7:8. Existing num luns 230
2012 Jul 12 10:31:57 MDS03 %SANTAP-SLOT3-4-ST_NEAR_MAX_LUNS_PER_HOST: Warning:
Approaching
2012 Jul 12 10:31:59 MDS03 %SANTAP-SLOT3-2-ST_MAX_LUNS_PER_HOST_REACHED:
MAX_LUNS_PER_HOST(256) limit reached for Host 1:2:3:4:5:6:7:8, DVT
1:2:3:4:5:6:7:8. Cannot Install Lun 0xyyyy
2012 Jul 12 10:32:00 MDS03 %PROC_MGR-SLOT3-2-ERR_MSG: ERROR: PID xxxx (ps_stap)
killed
with signal (11)
Workaround: This issue is resolved.
• CSCub27133
Symptom: Following an ISSU or ISSD, DMM is not configured on a a module where IPFC and
DMM were previously configured.
Workaround: This issue is resolved.
• CSCtr01652
Symptom: The F port trunking and channeling between a Cisco MDS switch and a Cisco UCS
server fails with the following error:
%PORT-5-IF_PORT_QUIESCE_FAILED: Interface fcx/y port quiesce failed due to
failure reason: Force Abort Due to Link Failure (NOS/LOS) (0x119)
%PORT-5-IF_DOWN_OLS_RCVD: %$VSAN X%$ Interface fcx/y is down (OLS received)
port-channel X <>
Condition: Certain organizational unique identifiers (OUIs) are not being recognized as a result of
which port channel fails.
Workaround: This issue is resolved.
Note In Cisco MDS Release 5.2.6, these OUIs are added: 0x002a6a, 0x00defb, and 0x8c604f.
Open Caveats
• CSCtn72391
Symptom: Following a switch reload or a software upgrade, the startup configuration occasionally
does not display feature FCIP.
Workaround: Once the switch is completely up, copy the running configuration to the startup
configuration by entering the copy running-config startup-config command.
• CSCtr10877
Symptom: Following an ISL flap that isolates some switches in the fabric (and the corresponding
FCR peers) and then later merges them again, some FCR peers might get out of sync with the SSM
switch FCR peer (that is, the FCR peer that owns a configuration) during the peer discovery phase.
Consequently, some application flows might not come online, or might even get deleted.