EasyManuals Logo

Cisco MDS 9000 Series Configuration Guide

Cisco MDS 9000 Series
344 pages
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Page #202 background imageLoading...
Page #202 background image
This example shows a sample message on a switch in which the validation is rejected:
2007 Apr 10 00:00:06 switch-2 %DEVICE-ALIAS-3-MERGE_VALIDATION_REJECTED:
Failed SAP: 110 Reason: inter-VSAN zone member cannot be in more than one
VSAN Expln:
This example shows the syslog message on a switch that is managing the merge, and in which the validation is rejected:
2007 Apr 9 16:41:22 switch-1 %DEVICE-ALIAS-3-MERGE_VALIDATION_FAILED: Failed
SWWN: 20:00:00:0d:ec:04:99:40 Failed SAP: 110 Reason: inter-VSAN zone member cannot be in more than
one
VSAN Expln:
Step 4 Use the show device-alias internal validation-info command on the switch managing the merge, and examine the output.
This example shows that SAP 110 on switch 20:00:00:0d:ec:04:99:40 (switch-2) rejected the validation. The status
message shows the reason for the failure along with the system application number:
switch# show device-alias internal validation-info
Validation timer: 0s
Per SAP Info Table:
===================
SAPS: 0
MTS Buffer Array Details:
=========================
Buffers: 0
Local Status:
=============
Num Reqs Sent: 0 20:00:00:0d:ec:04:99:40
Num SAPs Done: 0
Failed SAP : 0 Status: success Expln:
Remote Status:
==============
CFS Resp Rcvd: TRUE
Failed SWWN : 20:00:00:0d:ec:04:99:40
SAP : 110 Status: inter-VSAN zone member cannot be in more than one VSAN <=== Status
Expln:
Step 5 Use the show system internal mts sup sap number description command to find the application that rejected the
configuration on the switch that rejected the validation.
In this example, the application that rejected the device-alias validation was the IVR process.
switch# show system internal mts sup sap 110 description
IVR-SAP
Step 6 Analyze the device-alias validation failure. This analysis is dependent on the application that failed the validation as well
as the device-alias database configuration.
In this example, IVR is failing the validation. To troubleshoot this problem, begin by reviewing the device-alias databases
that are being merged. Use the show device-alias database command from the switch managing the merge for each
fabric.
switch# show device-alias database
device-alias name A1 pwwn 21:01:01:01:01:01:01:01
device-alias name A2 pwwn 21:01:01:01:01:01:01:02 => Pre-merge: A2 defined on switch-1
Cisco MDS 9000 Series Fabric Configuration Guide, Release 8.x
180
Distributing Device Alias Services
Resolving a Validation Failure

Table of Contents

Other manuals for Cisco MDS 9000 Series

Questions and Answers:

Question and Answer IconNeed help?

Do you have a question about the Cisco MDS 9000 Series and is the answer not in the manual?

Cisco MDS 9000 Series Specifications

General IconGeneral
CategorySwitch
Operating SystemCisco NX-OS
PortsVaries by model
ProtocolsFibre Channel (FC), Fibre Channel over IP (FCIP), iSCSI
RedundancyRedundant supervisors, power supplies, and fans
ManagementCisco Data Center Network Manager (DCNM), CLI, SNMP
Virtualization SupportVSANs (Virtual SANs)
Security FeaturesFibre Channel Security Protocol (FC-SP)
Hot Swappable Componentspower supplies, fans
Power Supply OptionsAC and DC options available

Related product manuals