This post is more than 5 years old

50 Posts

4368

July 5th, 2007 12:00

MDS9509, zone active but not used

I mostly use ECC 5.2 SP5 to manage (zone) the switches, but I have used FM 3.1 and Cisco Cli 3.1 . Using any/all these tools is there some way to detect that an active zone is not actually being used? I'm in the process of cleaning up zones and while I know most of things that can be removed there can be some unpleasant surprises

2.2K Posts

July 6th, 2007 08:00

Ok, I see the challenge you are referring to. Not having control over you entire SAN infrastructure is going to make that more difficult and an ongoing task it sounds like.

Using the command "show zoneset active vsan XX" can still help you in this. If you run the command it will show all the zones in the active zoneset, but it will also place an asterisk next to wwn's that are currently logged into the fabric.

Below is the same zone copied from the output in the "show zoneset active vsan XX" command from one of my switches. The first one is with the server online. The second one is how the zone looks with the server shutdown.

zone name XXXXXX vsan XX
* fcid 0x020000 [pwwn 21:00:00:e0:8b:85:fc:d1]
* fcid 0x021eef [pwwn 50:06:01:63:30:60:36:22]
* fcid 0x021def [pwwn 50:06:01:6a:30:60:36:22]

zone name XXXXXX vsan XX
pwwn 21:00:00:e0:8b:85:fc:d1
* fcid 0x021eef [pwwn 50:06:01:63:30:60:36:22]
* fcid 0x021def [pwwn 50:06:01:6a:30:60:36:22]

You could also compare the "show zoneset active vsan XX" output with the "show flogi" or "show fcns database" output. This will give you the list of wwn's logged into the switch that you can compare against the list of zone memberships.

2.2K Posts

July 5th, 2007 13:00

Bruce,
You can look at the active Zoneset to determine which zones are in use. With the CLI you can compare the current active zoneset against the entire list of zones for each VSAN.

show zoneset active vsan XX

show zoneset vsan XX

In the Fabric Manager GUI you can enter into the Zone Database for each VSAN and by viewing the Zoneset container you will see which zones are active.

Is that what you were looking for?

Aran

50 Posts

July 6th, 2007 07:00

First we are using wwn zoning. Determining active zones is easy, the question is "is an active zone actually being used". Lets say a SAN attached server P1 gets replaced. By our convention, the hba should get put in a cleanup pile and a change control generated to clean up zones and masking. What has happened is someone reuses the card in P2 and since its already zoned to our production DMX all they do is mask the necessary disk. So I come along and say "this zone for P1 is not used, after all the server is gone". I remove the zone and server P2 quits working because the zone was still being used.

50 Posts

July 6th, 2007 10:00

Thanks, that is what I was looking for.

1 Rookie

 • 

33 Posts

July 31st, 2011 18:00

we have same o/p but different issue

initiator is up and currently in zone

initiator is in VSAN 402 and targets are in VSAN 203.

VSAN 203

zone name IVRZ_IVR_VSAN203_ST3380-Tapes-2 vsan 203
    pwwn 10:00:00:00:c9:90:7b:29 [ST3380-hba2p1] <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
  * fcid 0xa10003 [pwwn 50:05:07:63:0f:4a:89:68] [TS3500_Caro_LTO3h708]
  * fcid 0xa10004 [pwwn 50:05:07:63:0f:4a:89:6b] [TS3500_Caro_LTO4h711]
  * fcid 0xa10000 [pwwn 50:05:07:63:0f:4a:89:73] [TS3500_Caro_LTO4h63]
  * fcid 0xa10001 [pwwn 50:05:07:63:0f:4a:89:77] [TS3500_Caro_LTO4h67]
  * fcid 0xa10007 [pwwn 50:05:07:63:0f:4a:89:7b] [TS3500_Caro_LTO4h6b]

VSAN402

zone name IVRZ_IVR_VSAN203_ST3380-Tapes-2 vsan 402
  * fcid 0x4c0003 [pwwn 10:00:00:00:c9:90:7b:29] [ST3380-hba2p1]
  * fcid 0xc1e166 [pwwn 50:05:07:63:0f:4a:89:68] [TS3500_Caro_LTO3h708]
  * fcid 0xc1e164 [pwwn 50:05:07:63:0f:4a:89:6b] [TS3500_Caro_LTO4h711]
  * fcid 0xc1e176 [pwwn 50:05:07:63:0f:4a:89:73] [TS3500_Caro_LTO4h63]
  * fcid 0xc1e17c [pwwn 50:05:07:63:0f:4a:89:77] [TS3500_Caro_LTO4h67]
  * fcid 0xc1e174 [pwwn 50:05:07:63:0f:4a:89:7b] [TS3500_Caro_LTO4h6b]
CM013#

server is not able to see target now .

what could be the issue?

No Events found!

Top