This post is more than 5 years old
124 Posts
0
4031
Renaming the VSAN
Hi,
I have just recently installed a cisco 9513 Switch and created few vsans on it. It is still not on production , so i wana change the naming convention of the vsan that i have created , is there any command to do that. I only saw commands related to alias/zone/zoneset rename, would be a great help, if some could jot down the steps for me , really appreciate your help. I got the DMX FA ports connected on this switch but with only one Host, so nothin critical running on it for now.
Like for e.g
vsan1111 -> needs to be vsan1201.
I have just recently installed a cisco 9513 Switch and created few vsans on it. It is still not on production , so i wana change the naming convention of the vsan that i have created , is there any command to do that. I only saw commands related to alias/zone/zoneset rename, would be a great help, if some could jot down the steps for me , really appreciate your help. I got the DMX FA ports connected on this switch but with only one Host, so nothin critical running on it for now.
Like for e.g
vsan1111 -> needs to be vsan1201.
healyj
141 Posts
0
November 28th, 2017 07:00
Hi there,
In our efforts to clean up the forum, we came across your question / statement.
If the question / statement is still valid, not expired and you need an update please reach out again and we try to get it answered.
As for now we set it to “answered.”
Regards,
Jim
eduardo_b_steph
6 Posts
0
August 26th, 2009 12:00
Do you have Fabric Manager installed?
I believe you can rename using Fabric Manager
StorageAdmin2
124 Posts
0
August 26th, 2009 17:00
modaslam
217 Posts
0
August 27th, 2009 09:00
can you kindly post the code to do that.
StorageAdmin2
124 Posts
0
September 1st, 2009 23:00
1. Delete the zones & Zonesets
using no zone/zoneset name
2. Delete the vsan ->
#config t
# vsan database
#sh vsan
# no vsan
3. Create the new vsan in vsan database using
# vsan
4. Create zone/zonesets
I didn't have the FM installed that time, so had to use cli only. Hope the steps are clear. This was for a new switch, so i could afford to do this
modaslam
217 Posts
0
September 3rd, 2009 10:00
I was expecting a rename command like the way we rename a zoneset.
hersh1
197 Posts
0
September 3rd, 2009 10:00
vsan XX name NEW_VSAN_NAME
SAN-F-TEST-D07-9120# show vsan 80
vsan 80 information
name:VSAN0080 state:active
interoperability mode:default
loadbalancing:src-id/dst-id/oxid
operational state:up
SAN-F-TEST-D07-9120# conf
Enter configuration commands, one per line. End with CNTL/Z.
SAN-F-TEST-D07-9120(config)# vsan database
SAN-F-TEST-D07-9120(config-vsan-db)# vsan 80 name changeVSANname
SAN-F-TEST-D07-9120(config-vsan-db)# do show vsan 80
vsan 80 information
name:changeVSANname state:active
interoperability mode:default
loadbalancing:src-id/dst-id/oxid
operational state:up
SAN-F-TEST-D07-9120(config-vsan-db)#
I did this on all our VSANs without an issue. I just ran those commands with debug vsan all and there was quite a bit of info pushed to the console. I haven't looked through to see if it points to any disruptive steps yet. I do know I still had my vsan configuration after I ran those commands in the past. If I get time I will update the thread with what I find in the debug data.
StorageAdmin2
124 Posts
0
September 3rd, 2009 17:00
I am not talking about vsan name , that can be done as you said without any issues. I mentioned the process where incase you need to change the vsan ID (vsan 80), so in my case i wanted to make it 1111, due to some naming conventions followed in my company. So all those steps above are to change the vsan id and not the name.
Hope , it is more clear now
I understand hulks concern, we cannot afford to drop a vsan in a production environment,i just had a new toy to play with so could afford to modify the settigns
Message was edited by:
Bhat
hersh1
197 Posts
0
September 4th, 2009 12:00
Sorry for the confusion.
And by the way it looks like the only thing changing the VSAN name did was remove the ability to use it in interop modes 3 and 4.
RRR
1 Rookie
1 Rookie
•
5.7K Posts
0
September 10th, 2009 06:00
Then put all old-VSAN ports in the new VSAN (disruptive !!!). You might want to do topsan first and make sure you have 2 paths again after the change and then change the bottomsan.
I used the GUI.