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 m d s f e e d b a c k - d o c @ c i s c o . c o m
Symptom: A Cisco MDS 9000 switch does not respond to an FDISC request from an attached
switch with NPV enabled if the MDS 9000 switch is already processing an FDISC request for the
same pWWN. This symptom might be seen if the downstream device has NPV mode enabled, and
the MDS 9000 switch is processing an FDISC request for the same pWWN and no ABTS request is
sent to cancel the in-progress FDISC request.
Workaround: This issue is resolved.
CSCtd04154
•
Symptom: The DMM CPP interface cpp1/1/1 does not come up unless there is an active port in
VSAN 1, which is the DMM management VSAN. This symptom might be seen when an interface
is either not defined or is not up in VSAN 1.
Workaround: This issue is resolved.
CSCti38286
•
Symptom: When you create a DMM job, DMM might intermittently display the following message:
DMM_JOB_INFRA_FC_REDIRECT_SETUP_ERR.
This symptom might be seen when there are two or more paths to a host, multiple paths to existing
storage, and multiple paths to the new storage.
Workaround: This issue is resolved.
CSCtj84690
•
Symptom: When you upgrade from Cisco NX-OS Release 4.1(3a) to NX-OS Release 5.0(1a),
certain ports are brought down because of diagnostics failure. Messages similar to the following are
displayed:
2010 Jul
Module image download process. Please wait until completion...
2010 Jul
Module image download process. Download successful.
2010 Jul
of module 5 ended
2010 Jul
current-status is MOD_STATUS_ONLINE/OK
2010 Jul
%$VSAN 10%$ Interface fc5/37 is down (Diag failure)
2010 Jul
%$VSAN 10%$ Interface fc5/38 is down (Diag failure)
2010 Jul
%$VSAN 10%$ Interface fc5/39 is down (Diag failure)
The following information is written to the logs:
5) Event:E_DEBUG, length:84, at 242335 usecs after Mon Jul
PortBits 0xfff000000000
All interfaces that were brought down with "Diag failure" were listed in an exception that happened
before the upgrade occurred.
Workaround: This issue is resolved.
CSCtk18444
•
Symptom: When a ICMP error packet (type 3 code 4) is received, there is no way to track the sender
of the error packet or to determine the MTU size provided in the error packet.
Workaround: This issue is resolved. The code has been enhanced to print the entire ICMP packet
in both the receive and send path when the debug ips ipstack icmp port command is enabled.
OL-21012-04
5 19:33:39 MDSSWITCH %IMAGE_DNLD-SLOT5-2-IMG_DNLD_STARTED:
5 19:33:57 MDSSWITCH %IMAGE_DNLD-SLOT5-2-IMG_DNLD_COMPLETE:
5 19:35:00 MDSSWITCH %MODULE-5-LCM_MODULE_UPGRADE_END: Upgrade
5 19:35:00 MDSSWITCH %PLATFORM-5-MOD_STATUS: Module 5
5 19:35:00 MDSSWITCH %PORT-5-IF_DOWN_LOOPBACK_DIAG_FAILURE:
5 19:35:00 MDSSWITCH %PORT-5-IF_DOWN_LOOPBACK_DIAG_FAILURE:
5 19:35:00 MDSSWITCH %PORT-5-IF_DOWN_LOOPBACK_DIAG_FAILURE:
[103] 3170:ohms_lc_exception: ERROR: Exception from module 5
Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 5.0(4b)
Caveats
5 19:35:00 2010
35
Печатать страницу