Zone problem between storage and blade

[adam900331]

Hy!

I have Cisco SAN switch (DS-C9132T-K9). I created some zone for the standalone servers and storage. And also create zones for my blade and storage. I have 3 blade server:

ESX1 pwwn: 50:01:43:80:02:a4:90:00

ESX2 pwwn: 50:01:43:80:02:a4:90:04

ESX3 pwwn: 50:01:43:80:02:a4:90:08

Storage pwwn: 24:70:00:c0:ff:28:cc:a5

The zones configuration for the blade:

zone name ESX1_MSA1 vsan 101
member pwwn 50:01:43:80:02:a4:90:00
member pwwn 24:70:00:c0:ff:28:cc:a5

zone name ESX2_MSA1 vsan 101
member pwwn 50:01:43:80:02:a4:90:04
member pwwn 24:70:00:c0:ff:28:cc:a5

zone name ESX2_MSA1 vsan 101
member pwwn 50:01:43:80:02:a4:90:08
member pwwn 24:70:00:c0:ff:28:cc:a5

I activated the zoneset, but unfortunatelly the servers couldn't see the storage.

The connection between the standalone servers and storage works correctly. What is the different If I create zone for blade servers?

Thanks.

[marce1000]

 - You have  two zones named  ESX2_MSA1 ; is that intended , or a typo ?

 M.

[adam900331]

Sorry, I wrote it wrong. The coerrect zone name is:

zone name ESX3_MSA1 vsan 101
member pwwn 50:01:43:80:02:a4:90:08
member pwwn 24:70:00:c0:ff:28:cc:a5

[marce1000]

  - Remember to activate the zoneset if applicable with : zoneset activate....
  - Check flogi status with :  show fcns database ...
  - Verify active zones using :  show zone active ...
  - Check logs on the SAN switch  with : show logging 

 M.

[adam900331]

Thanks.

I see all connected device which is part of the zone config.

Can I check the unzoned devices WWNs? I run the following comman: sh zone analysis active

And I see there are 5 unzoned devices:

Number of devices zoned in vsan: 45/50 (Unzoned: 5)

And also checked the following command: sh zone internal event-history errors

There are some error which is regarding the port where the affected blade and the storage is connected:

2024 Jan 16 22:36:22.150049: E_DEBUG [181] mts_drop:2985 proc(/isan/bin/zone_server) errno(22) msg_ref does not have valid msg payload



2024 Jan 16 22:36:22.150018: E_DEBUG [181] ref_payload_get(/isan/bin/zone_server) Invalid payload/mtsbuf(0xf4f0d404) found



2024 Jan 16 22:36:22.147724: E_DEBUG [110] zone [4517]: Lc entry for fc1/2 at slot 0 not found


2024 Jan 16 22:36:22.147690: E_DEBUG [110] zone [4517]: Lc entry for fc1/4 at slot 0 not found


2024 Jan 16 22:36:22.147644: E_DEBUG [110] zone [4517]: Lc entry for fc1/6 at slot 0 not found


2024 Jan 16 22:31:09.786449: E_DEBUG [181] mts_drop:2985 proc(/isan/bin/zone_server) errno(22) msg_ref does not have valid msg payload



2024 Jan 16 22:31:09.786424: E_DEBUG [181] ref_payload_get(/isan/bin/zone_server) Invalid payload/mtsbuf(0xf4f0d404) found



2024 Jan 16 22:31:09.784361: E_DEBUG [110] zone [4517]: Lc entry for fc1/4 at slot 0 not found


2024 Jan 16 22:31:09.784313: E_DEBUG [110] zone [4517]: Lc entry for fc1/8 at slot 0 not found


2024 Jan 16 22:24:58.526362: E_DEBUG [181] mts_drop:2985 proc(/isan/bin/zone_server) errno(22) msg_ref does not have valid msg payload



2024 Jan 16 22:24:58.526337: E_DEBUG [181] ref_payload_get(/isan/bin/zone_server) Invalid payload/mtsbuf(0xf4f0d104) found



2024 Jan 16 22:24:58.524075: E_DEBUG [110] zone [4517]: Lc entry for fc1/4 at slot 0 not found


2024 Jan 16 22:24:58.524023: E_DEBUG [110] zone [4517]: Lc entry for fc1/2 at slot 0 not found


2024 Jan 16 22:24:58.523961: E_DEBUG [110] zone [4517]: Lc entry for fc1/18 at slot 0 not found


2024 Jan 16 22:15:44.811695: E_DEBUG [181] ref_payload_get(/isan/bin/zone_server) Invalid payload/mtsbuf(0xf4f0d504), snode/msgid (mtsbuf:102/b43bd12) (msg-ref:101/2609c09)

I don't know what does it mean. We connected the devices to the switch with the logs timestamp.

Thanks.

[adam900331]

Do you have any idea?

[adam900331 · Accepted solution]

The zone problem is resolved, I modified the zone configuration and forget to activate the zoneset. After I activated the zoneset, the affected host and storage communication works.