Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 6.2(1) (OL-29201-01, April 12, 2013)

31
Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 6.2(1)
OL-29201-01
Caveats
Usage for bootflash://
switch# copy bootflash:rcfg tftp://10.106.177.220/test
Trying to connect to tftp server......
Connection to server Established. Copying Started.....
|
TFTP put operation was successful
Copy complete.
switch# copy bootflash:rcfg tftp://172.22.35.100/test
Trying to connect to tftp server......
Connection to server Established. Copying Started.....
|
TFTP put operation was successful
Copy complete.
switch#
• CSCug17272
Symptom: You cannot use Cisco DCNM Release 6.2(1) to configure a DMM job.
Workaround: Configure the DMM job from the command-line interface rather than from Cisco
DCNM.
• CSCug22090
Symptom: When an ISSU occurs from Cisco NX-OS Release 5.2(6b) to Release 6.2(1), LLDP
command-line interface (CLI) commands are not available. In this situation, LLDP is running and
traffic is flowing normally even after the ISSU, but the CLI commands are not available.)
This symptom might be seen when feature-set fcoe was enabled on the original image, and feature
lldps commands were working in the original image. Following the ISSU to Cisco NX-OS Release
6.2.1 image, the commands are not available.
Workaround: Following the ISSU, enter the feature lldp command on the switch to make the
LLDP commands available on the switch.
switch(config)# feature lldp
switch(config)# show lldp ?
• CSCug25141
Symptom: The power consumption displayed in the output of the show environment power
command is different than the actual power consumption. The command output shows a higher value
than the actual value.
This symptom might be seen under normal operating conditions for the Cisco MDS 9710 switch.
Workaround: None.
• 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:
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.