Cisco AJ732A - MDS 9134 Fabric Switch Release Note page 39

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
port-wwn (vendor) :50:01:10:a0:00:16:d0:f6
[HOSBILLYGIRL]
node-wwn :50:01:10:a0:00:16:d0:f7
class :3
node-ip-addr :0.0.0.0
ipa :ff ff ff ff ff ff ff ff
fc4-types:fc4_features :scsi-fcp:init
symbolic-port-name :
symbolic-node-name :HPAE311A FW:v4.00.23 DVR:v9.1.3.16
port-type :N
port-ip-addr :0.0.0.0
fabric-port-wwn :23:03:00:0d:ec:3b:ad:40
hard-addr :0x000000
permanent-port-wwn (vendor) :50:01:10:a0:00:16:d0:f6
The SymbolicNodeName in Device Manager does not get populated into Fabric Manager for Model,
Firmware, and Driver.
Workaround: This issue is resolved.
CSCsr18556
•
Symptom: License records are not removed if a fabric is purged from the database. License
information might be incorrect if the same fabric is added back in to Fabric Manager at a later time.
Workaround: This issue is resolved.
CSCsr28197
•
Symptom: The error messages for Device-Alias Merge failures need to be more be enhanced to
allow customers to pinpoint offending Device Aliases or pWWNs associated with the merge failure.
Workaround: This issue is resolved.
• CSCsr28302
Symptom: DPVM Merge failure messages need to be enhanced to help customers determine why
the merge failed.
Workaround: This issue is resolved.
• CSCsu37199
Symptom: Errors on the management port (mgmt0 or eth1) may be seen in the output of the show
logging log command.
%KERN-3-SYSTEM_MSG: eth1: error in ethGetNextRxBuf %KERN-3-SYSTEM_MSG: eth1: stop
internals failed %KERN-3-SYSTEM_MSG: eth1: error in rx %KERN-3-SYSTEM_MSG: eth1: error
in rx %KERN-3-SYSTEM_MSG: eth1: error in rx %KERN-3-SYSTEM_MSG: eth1: error in rx
%KERN-3-SYSTEM_MSG: eth1: error in rx
In rare cases this may result in a kernel panic which causes a supervisor switchover.
Workaround:This issue is resolved.
CSCsu37854
•
Symptom: The syslog dialog box in Device Manager does not display all logs.
Workaround: This issue is resolved.
CSCsu42003
•
Symptom: When an FCIP tunnel is configured with IPsec between an MDS 9222i switch and an
MDS 9216i switch, it fails to come up if an ACL with TCP permit is configured. This causes a
mismatch and causes the security association (SA) policy creation to fail in IPsec on the supervisor.
Workaound: This issue is resolved.
OL-14116-10
Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 3.3(2)
Caveats
39