Cisco Nexus 5000 Series Switch CLI Software Configuration Guide (OL-16597-01, July 2009)

• Each zone alias has only one member.

• The member type is pWWN.

If any name or definition conflict exists, the zone aliases are not imported.

Ensure that you copy any required zone aliases to the device alias database as required by your configuration.

When an import operation is complete, the modified alias database is distributed to all other switches in the

physical fabric when you perform the commit operation. If you do not want to distribute the configuration to

other switches in the fabric, you can perform the abort operation and the merge changes are completely

discarded.

Importing a Zone Alias

To import the zone alias for a specific VSAN, perform this task:

Procedure

PurposeCommand or Action

Enters configuration mode.switch# configuration terminal

Step 1

Imports the fcalias information for the

specified VSAN.

switch(config)# device-alias import fcalias

vsan vlan-id

Step 2

Device Alias Database Merge Guidelines

When merging two device alias databases, follow these guidelines:

• Verify that two device aliases with different names are not mapped to the same pWWN.

• Verify that two identical pWWNs are not mapped to two different device aliases.

• Verify that the combined number of device aliases in both databases does not exceed 8K (8191 device

aliases) in fabrics running Cisco MDS SAN-OS Release 3.0 (x) and earlier, and 20K in fabrics running

Cisco MDS SAN-OS Release 3.1(x) and later.

If the combined number of device entries in both databases exceeds the supported configuration limit, then

the merge will fail. For example, if database N has 6000 device aliases and database M has 2192 device aliases,

and you are running SAN-OS Release 3.0(x) or earlier, then this merge operation will fail. Merge operations

will also fail if there is a device alias mode mismatch.