Hi,

Do you have Fabric Manager installed?
I believe you can rename using Fabric Manager

I already did that using CLI, thanks anyways

Bat,

can you kindly post the code to do that.

Steps :

1. Delete the zones & Zonesets
using no zone/zoneset name vsan xxxx

2. Delete the vsan ->
#config t
# vsan database
#sh vsan
# no vsan -> whichever you want to delete.

3. Create the new vsan in vsan database using

# vsan name

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

droping a vsan would be very expensive.

I was expecting a rename command like the way we rename a zoneset.

If the vsan is already created just run this:

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.

Hersh,
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

OK I think I'm following. My confusion came from the fact you were changing the VSAN ID to straighten out a naming convention. I'm guessing now you were trying to straighten out your VSAN IDs so they make sense between your different fabrics and not the actual name associated with the VSAN ID.

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.

I needed something like this a while ago and what I did was to create a new VSAN and then copy the old VSAN to the new VSAN (right click on the old one) and afterwards remove the old one. Don't forget to activate the new VSAN.

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.