This post is more than 5 years old
259 Posts
0
7288
cisco alias management
I know how to create alias' for new host/wwn attachments to our cisco 9513 directors but I don't know how to "change" the alias name for an existing wwn alias.
the only commands I can find in the manuals refer to setting alias on a new wwn:
the sequence of commands to set the initial alias/:
config t
device-alias database
device-alias name alias_name pwwn 10:00:00:00:c9:73:a1:34
device-alias commit
if I try to enter in a new alias for a wwn that already has an alias present, I get the error 'alias already present' and it doesn't take the new alias name I want to assign.
the only commands I can find in the manuals refer to setting alias on a new wwn:
the sequence of commands to set the initial alias/:
config t
device-alias database
device-alias name alias_name pwwn 10:00:00:00:c9:73:a1:34
device-alias commit
if I try to enter in a new alias for a wwn that already has an alias present, I get the error 'alias already present' and it doesn't take the new alias name I want to assign.
Smiley6
5 Posts
0
April 30th, 2008 06:00
Example:
MDS9506-01# show device-alias database
device-alias name x335-1 pwwn 21:01:00:e0:8b:b0:72:17
Total number of entries = 1
MDS9506-01# config terminal
Enter configuration commands, one per line. End with CNTL/Z.
MDS9506-01(config)# device-alias database
MDS9506-01(config-device-alias-db)# device-alias rename x335-1 x335-1-new
MDS9506-01(config-device-alias-db)# exit
MDS9506-01(config)# device-alias commit
MDS9506-01(config)# end
MDS9506-01# sho device-alias database
device-alias name x335-1-new pwwn 21:01:00:e0:8b:b0:72:17
Total number of entries = 1
MDS9506-01#
dynamox
2 Intern
2 Intern
•
20.4K Posts
0
April 30th, 2008 06:00
fcalias rename current-name new-name vsan vsanid
jimkunysz
259 Posts
0
April 30th, 2008 06:00
I'm so used to the quality of EMC documentation that the cisco documentation leaves something to be desired.
Thanks.
kmcintyre1
1 Message
0
June 10th, 2011 06:00
One more last question: Is renaming a device-alias disruptive to the hosts? Can it be done online?
Thanks!
hersh1
197 Posts
0
June 13th, 2011 06:00
It is a non-disruptive change so it can be done online.
airxpress
3 Posts
0
September 25th, 2012 11:00
I cant seem to find this in any documentation stating that it is non-disruptive. Can anyone show me where this can be found? Thanks
hersh1
197 Posts
0
September 25th, 2012 11:00
I'm not really sure it will specfically say anywhere that its non-disruptive. The logic on why this is the case is because zones contain WWNs and NOT device-aliases. The GUI and CLI simply display the device-alias instead of the WWN as a reference. Therefore changing the device-alias doesn't change the zoning and thus no outage.
airxpress
3 Posts
0
September 25th, 2012 13:00
Even when operating in enhanced mode?
Device alias supports two modes: basic and enhanced mode.
• When device alias runs in the basic mode, all applications function like the applications on the 3.0
switches. When you configure the basic mode using device aliases, the application immediately
expands to pWWNs. This behavior continues until the mode is changed to enhanced.
• When device alias runs in the enhanced mode, all applications accept the device-alias configuration
in the native format. The applications store the device alias name in the configuration and distribute
it in the device alias format instead of expanding to pWWN. The applications track the device alias
database changes and take actions to enforce it.
From my understanding if I were to rename the device-alias it will update the zones as well.
ajbarth
14 Posts
0
October 3rd, 2012 12:00
when renaming a device-alias in enhanced mode, any zones which have it as a member will get updated.