Port Suspended Or Disabled After Dpvm Activation; Dpvm Merge Failed - Cisco 9134 - MDS Multilayer Fabric Switch Troubleshooting Manual

Chapter 11 Troubleshooting VSANs, Domains, and FSPF
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 Suspended or Disabled After DPVM Activation

Symptom
database activation.
Table 11-10 Port Suspended or Disabled After DPVM Activation
Symptom Possible Cause
A port in a static DPVM database maps a connected
VSAN that was device to a nonexistent VSAN.
operational goes into
suspended or disabled
state after DPVM
database activation.

DPVM Merge Failed

Symptom
Table 11-11 DPVM Merge Failed
Symptom Possible Cause
DPVM merge failed. DPVM operational parameters in the
two merging fabrics are different.
OL-9285-05
A port in a static VSAN that was operational goes into suspended or disabled state after DPVM
DPVM merge failed.
Dynamic Port VSAN Membership Issues
Solution
Choose Switches > Interfaces > FC Physical in Fabric
Manager or use the show interface CLI command to check
the interface status for a dynamic VSAN-related failure.
Create the VSAN or map the device to another VSAN.
Solution
Choose Fabricxx > All VSANs > DPVM in Fabric
Manager e or use the show dpvm CLI command to verify
the DPVM configuration in both fabrics. Manually
reconcile any differences before attempting to merge the
fabrics. Use the show cfs merge status name dpvm CLI
command to verify the merge status.
Cisco MDS 9000 Family Troubleshooting Guide, Release 3.x
11-15