S e n d f e e d b a c k t o n x 5 0 0 0 - d o c f e e d b a c k @ c i s c o . c o m
39-2
Cisco Nexus 5000 Series Switch CLI Software Configuration Guide
OL-16597-01
Chapter 39 Distributing Device Alias Services
Device Alias Databases
•
The device alias application uses the Cisco Fabric Services (CFS) infrastructure to enable efficient
database management and distribution. Device aliases use the coordinated distribution mode and the
fabric-wide distribution scope (see
Chapter 21, “Using Cisco Fabric Services”
).
•
Basic and enhanced modes. See the
“Device Alias Modes” section on page 39-4
.
•
Device aliases used to configure zones, IVR zones, or port security features are displayed
automatically with their respective pWWNs in the
show
command output.
Device Alias Requirements
Device aliases have the following requirements:
•
You can only assign device aliases to pWWNs.
•
There must be a one-to-one relationship between the pWWN and the device alias that maps to it.
•
A device alias name is restricted to 64 alphanumeric characters and may include one or more of the
following characters:
–
a to z and A to Z
–
Device alias names must begin with an alphabetic character (a to z or A to Z).
–
1 to 9
–
- (hyphen) and _ (underscore)
–
$ (dollar sign) and ^ (up caret)
Zone Aliases Versus Device Aliases
Table 39-1
compares the configuration differences between zone-based alias configuration and device
alias configuration.
Device Alias Databases
The device alias feature uses two databases to accept and implement device alias configurations.
•
Effective database—The database currently used by the fabric.
Table 39-1
Comparison Between Zone Aliases and Device Aliases
Zone-Based Aliases
Device Aliases
Aliases are limited to the specified VSAN.
You can define device aliases without specifying the VSAN
number. You can also use the same definition in one or more
VSANs without any restrictions.
Zone aliases are part of the zoning configuration. The
alias mapping cannot be used to configure other features.
Device aliases can be used with any feature that uses the pWWN.
You can use any zone member type to specify the end
devices.
Only pWWNs are supported.
Configuration is contained within the zone server
database and is not available to other features.
Device aliases are not restricted to zoning. Device alias
configuration is available to the FCNS, zone, fcping, and
traceroute applications.
Summary of Contents for N5010P-N2K-BE
Page 50: ...Se n d f e e d b a ck t o n x 5 0 0 0 d o c f e e d b a ck c i s c o c o m ...
Page 102: ...Se n d f e e d b a ck t o n x 5 0 0 0 d o c f e e d b a ck c i s c o c o m ...
Page 240: ...Se n d f e e d b a ck t o n x 5 0 0 0 d o c f e e d b a ck c i s c o c o m ...
Page 312: ...Se n d f e e d b a ck t o n x 5 0 0 0 d o c f e e d b a ck c i s c o c o m ...
Page 400: ...Se n d f e e d b a ck t o n x 5 0 0 0 d o c f e e d b a ck c i s c o c o m ...
Page 418: ...Se n d f e e d b a ck t o n x 5 0 0 0 d o c f e e d b a ck c i s c o c o m ...
Page 436: ...Se n d f e e d b a ck t o n x 5 0 0 0 d o c f e e d b a ck c i s c o c o m ...
Page 658: ...Se n d f e e d b a ck t o n x 5 0 0 0 d o c f e e d b a ck c i s c o c o m ...