cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1208
Views
10
Helpful
2
Replies

Using MDS 9148 switches that are ISL'd, how do you edit vsans from any of those switches?

AnonymousXi
Level 1
Level 1

I'm having trouble editing a vsan that is ISL'd between switchABC and switchXYZ. They are ISL'd across fc1/47 and fc1/15, respectively. For example, I have vsan 3 with a full zoneset on switchABC, and an empty vsan 3 (no zones, no zoneset) on switchXYZ. I would like to be able to edit vsan 3 on both switches. If I create a zone and zoneset on vsan 3 on switchXYZ, I lose all my zonesets on switchABC when I activate it. Why is this? Ideally, I'd like to be able to edit vsan 3 regardless of which switch I'm on. Thanks.

Snipped from show interface:

Trunk vsans (admin allowed and active) (1,3)
Trunk vsans (up) (1,3)
Trunk vsans (isolated) ()
Trunk vsans (initializing) ()

2 Replies 2

AnonymousXi
Level 1
Level 1

I found the answer on here. Looks like I need to use "zone mode enhanced vsan <vsan number>". Changes to the vsan on either switch no longer overwrite each other.

Correct, and here a few hints, just in case

https://supportforums.cisco.com/document/109756/configuring-and-troubleshooting-mds-enhanced-zoning#Zoning_Lock_and_Lock_Owners

Zoning Lock and Lock Owners

The zoning lock is issued to a single user on a single switch. Only one user is allowed to hold the lock. If for some reason the lock is held by another user, and the lock has to be cleared forcefully, issue “no commit” with the force flag.

switch (config)# no zone commit vsan 1 force

switch# clear zone lock vsan <vsan_id>

 

Identifying the Lock Owner

If you’re locked out, follow these steps.

  1. Determine which switch (domain) has the lock
  2. Determine which user has the lock on that switch
  3. Clear the lock for that user on that switch.

 

Determining Switch holding lock

If there is a lock, Zone configuration attempt displays error or Zone database locked due to update in progress

 

switch-1(config)# zoneset name azone vsan 10

Zoning database update in progress, command rejected

 

Show zone status command displays what switch has the lock

 

switch-1# show zone status vsan 10

VSAN: 10 default-zone: deny distribute: active only Interop: default

    mode: enhanced merge-control: allow

    session: remote [dom: 100][ip: 10.87.100.22]  // this switch is having the lock

    hard-zoning: enabled broadcast: enabled

Default zone:

    qos: none broadcast: disabled ronly: disabled

---snip---

 

Confirm remote (Adj) switch and domain ID for vsan 10

 

switch-1# show fcs ie vsan 10

 

IE List for VSAN: 10

--------------------------------------------------------------------

IE-WWN                   IE     Mgmt-Id  Mgmt-Addr (Switch-name)

--------------------------------------------------------------------

20:0a:00:05:30:01:b1:b3  S(Loc) 0xfffc67 10.87.100.23 (switch-1)

20:0a:00:0b:fd:a7:72:41  S(Adj) 0xfffc64 10.87.100.22 (switch-2)

20:0a:00:0d:ec:19:43:c1  S(Adj) 0xfffc66 10.87.100.16 (switch-3)

[Total 3 IEs in Fabric]

 

Telnet to remote switch holding the lock (10.87.100.22) and confirm local (Loc) switch has domain ID 100  (0x64)

 

switch-2# show fcs ie vsan 10

 

IE List for VSAN: 10

-------------------------------------------------------------------

IE-WWN                   IE     Mgmt-Id  Mgmt-Addr (Switch-name)

-------------------------------------------------------------------

20:0a:00:05:30:01:b1:b3  S(Adj) 0xfffc67 10.87.100.23 (switch-1)

20:0a:00:0b:fd:a7:72:41  S(Loc) 0xfffc64 10.87.100.22 (switch-2)

20:0a:00:0d:ec:19:43:c1  S(Rem) 0xfffc66 10.87.100.16 (switch-3)

[Total 3 IEs in Fabric]

 

switch-2# show fcdomain domain-list vsan 10

 

Number of domains: 3

Domain ID              WWN

---------    -----------------------

0x67(103)    20:0a:00:05:30:01:b1:b3 [Principal]

0x64(100)    20:0a:00:0b:fd:a7:72:41 [Local]

0x66(102)    20:0a:00:0d:ec:19:43:c1

 

Determining User Holding Lock

Show zone status command displays user who has the lock

 

switch-2# show zone status vsan 10

VSAN: 10 default-zone: deny distribute: active only Interop: default

    mode: enhanced merge-control: allow

    session: cli [admin]       // user "admin" is holding the lock.

    hard-zoning: enabled broadcast: enabled

Default zone:

    qos: none broadcast: disabled ronly: disabled

---snip---

 

Clear the Lock

Contact admin to determine if this is an active session. If not active, clear the lock.

 

switch-2# clear zone lock vsan 10

 

Confirm that lock has been cleared

 

switch-2# show zone status vsan 10

VSAN: 10 default-zone: deny distribute: active only Interop: default

    mode: enhanced merge-control: allow

    session: none                    // Session field shows none

    hard-zoning: enabled broadcast: enabled

Default zone:

    qos: none broadcast: disabled ronly: disabled

---snip---

 

Changing back to Basic Zoning

If for some reason you need to change back to basic zoning follow these steps:

1) Check that the active and full zone set do not contain any configuration that is specific to the enhanced zoning mode. If there is any such config, remove it and then cross check the SAN working.

2) Change the operation mode to basic zoning. Doing this will grant you a fabric wide lock and distribute zoning information.

3) Apply the configuration changes and release the lock from all switches in the fabric.