Installation guide

60
Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 5.2(6)
OL-27554-01
Caveats
switch(config)# ivr aam pre-deregister-check
switch(config)# show ivr aam pre-deregister-check
AAM pre-deregister check status
--------------------------
FAILURE
There are merged entries or AAM has not been enabled with the following switches:
switch swwn 20:00:00:0d:ec:3e:f4:c0
Workaround : Disable IVR and AAM support on FCR and flap the ports:
switch (config)# no fc-redirect ivr-support enable
switch (config)# no ivr aam register
AAM is currently disabled. No change will be made.
switch (config)#
switch (config)# ivr commit
distribution not enabled
switch (config)# int fc1/17
switch (config-if)# shut
switch (config-if)# no shut
switch (config-if)# sh int fc1/17 br
-------------------------------------------------------------------------------
Interface Vsan Admin Admin Status SFP Oper Oper Port
Mode Trunk Mode Speed Channel
Mode (Gbps)
-------------------------------------------------------------------------------
fc1/17 1 FL -- up swl FL 2 --
switch (config-if)#
• CSCtz09820
In Generation 4 modules, the following errors might be observed. They are not a cause for concern
to the normal operation of the hardware. These errors are logged in the onboard persistent log and
can be viewed by entering the show logging onboard exception-log command after attaching to the
module.
TBIRD_FWD_EBM_0_SER_PARITY_XXX : Informational
TBIRD_FWD_EBM_0_PACK0_EPR_DROP : Informational
TBIRD_FWD_EBM_1_PACK3_MISS_SOF : Informational
TBIRD_FWD_EBM_1_PACK0_MISS_EOP : Informational
TBIRD_FWD_EBM_1_PACK0_SF_TOO_SMALL : Informational
These errors are reported when there are internal correctable conditions encountered during
operation, and the corrective action is taken. They do not necessarily indicated a problem with the
switch or module.
The following error can occur in cases of corrupted frames in the ingress path (due to a bad cable or
SFP). It does not necessarily indicated a problem with the switch hardware.
THB_IPA_IPA0_INTR_FLD_ERR_FROM_MEM : Warning
Workaround: None.
• CSCtz19169
Symptom: After the primary KMC fails over to the secondary, KMC performance suffers. The
system attempts to reacquire connectivity to the primary KMC for each operation, and the system
waits for that attempt to time out before using the secondary KMC. Waiting for the timeout creates
a significant delay for failed over operations, particularly when scaled.
This symptom occurs when the primary KMC fails (because of loss of connectivity).