Cisco MDS SanOS Troubleshooting Guide -- Troubleshooting Distributed Device Alias Services

From DocWiki

This section describes how to troubleshoot and resolve problems that might occur when using device aliases.

Contents 1 Overview 2 Initial Troubleshooting Checklist 2.1 Merge Failure Messages 2.2 Merge Validation Failure Messages 2.3 Commit Failure Messages 2.4 Verifying Device Alias Database Status Using the CLI 2.5 Limitations and Restrictions 3 Merge Failure Issues 3.1 Resolving Duplicate Device Alias Names 3.2 Resolving Mapping a pWWN to Different Device Alias Names 3.3 Resolving Mode Mismatch 3.4 Resolving Merge Failures in Mixed Fabric 3.5 Resolving a Validation Failure 3.6 Resolving Merge in Progress Issues 4 Validation and Commit Failure Issues 4.1 Resolving Database Conflicts 4.2 Resolving Application Busy Situations 4.3 Resolving Database Size Issues 4.4 Resolving Mode Issues

Overview

When you configure different features for a Cisco MDS 9000 Family switch, such as zoning, DPVM, or port security, you must specify the correct device name each time. An inaccurate device name can cause unexpected results. You can circumvent this problem by defining and using device aliases.

A device alias is a user-friendly name for a port WWN (pWWN) that can be used in all configuration commands as required. All switches in the Cisco MDS 9000 Family support Distributed Device Alias Services (device aliases).

Initial Troubleshooting Checklist

Device alias problems may result in merge, commit, or validation failures, and resolution requires gathering information about the specific failure and the fabric configuration. Begin troubleshooting device alias issues by checking the following items:

Checklist	Check off
Verify the device alias mode (basic or enhanced).
Verify that device alias distribution is enabled.
Verify that the fabric is not locked.

Merge Failure Messages

Merge Validation Failure Messages

Commit Failure Messages

Verifying Device Alias Database Status Using the CLI

Limitations and Restrictions

Merge Failure Issues

Resolving Duplicate Device Alias Names

Resolving Mapping a pWWN to Different Device Alias Names

Resolving Mode Mismatch

Resolving Merge Failures in Mixed Fabric

Resolving a Validation Failure

Resolving Merge in Progress Issues

Validation and Commit Failure Issues

Resolving Database Conflicts

Resolving Application Busy Situations

Resolving Database Size Issues

Resolving Mode Issues