anupamphoghat1
1 Copper

All the zones affected for a host connected to VMAX

Solaris host HBA connected to VSAN 431 will automatically re-scan it's fabric level storage targets after adding new zones with VMAX. Interestingly enough this temporarily disrupts active I/O to DMX arrays (ones not being added/modified at all) resulting in host level SCSI retries.

Note: xxxxxxxxxxxxxx5d is DMX and xxxxxxxxxxxxxx1c is VMAX.

Zone being added (form VMAX):

zone name z_nus954pb_hba0_0 vsan 431

member fcalias nus954pb_hba0_0

member fcalias nde410_fa08e0

Existing zone on fabric (for DMX storage):

zone name nus954pb_hba0_0_ndeXXX_fa14b0 vsan 431

    member fcalias nde040_fa14b0

    member fcalias nde035_fa14b0

    member fcalias nus954pb_hba0_0

Logs from host's /var/adm/messages during zoneset activation & distribution:

Jun  4 22:30:53 au11qap650tels2 unix: /pci@bd,600000/SUNW,emlxs@1/fp@0,0 (fcp2):

Jun  4 22:30:53 au11qap650tels2         Lun=0 for target=60033 disappeared

Jun  4 22:30:53 au11qap650tels2 unix: /pci@bd,600000/SUNW,emlxs@1/fp@0,0 (fcp2):

Jun  4 22:30:53 au11qap650tels2         Lun=0 for target=6004a disappeared

Jun  4 22:30:54 au11qap650tels2 unix: ssd52 at fp2: name wxxxxxxxxxxxxxx1c,0, bus address 70037

Jun  4 22:30:54 au11qap650tels2 unix: ssd52 is /pci@bd,600000/SUNW,emlxs@1/fp@0,0/ssd@wxxxxxxxxxxxxxx1c,0

Jun  4 22:30:54 au11qap650tels2 unix: WARNING: /pci@bd,600000/SUNW,emlxs@1/fp@0,0/ssd@wxxxxxxxxxxxx5d1c,0 (ssd52):

Jun  4 22:30:54 au11qap650tels2         Corrupt label; wrong magic number

Jun  4 22:30:54 au11qap650tels2 unix: /pci@bd,600000/SUNW,emlxs@1/fp@0,0/ssd@wxxxxxxxxxxxa5d1c,0 (ssd52) online

Jun  4 22:30:55 au11qap650tels2 unix: WARNING: /pci@bd,600000/SUNW,emlxs@1/fp@0,0/ssd@wxxxxxxxxxxxad5d,11 (ssd2):

Jun  4 22:30:55 au11qap650tels2         Error for Command: write(10)               Error Level: Retryable

Jun  4 22:30:55 au11qap650tels2 unix:   Requested Block: 5188480                   Error Block: 5188480

Jun  4 22:30:55 au11qap650tels2 unix:   Vendor: EMC                                Serial Number: xxxxxxxxa

Jun  4 22:30:55 au11qap650tels2 unix:   Sense Key: Unit Attention

Jun  4 22:30:55 au11qap650tels2 unix:   ASC: 0x29 (power on, reset, or bus reset occurred), ASCQ: 0x0, FRU: 0x0

Jun  4 22:31:09 au11qap650tels2 unix: WARNING: /pci@bd,600000/SUNW,emlxs@1/fp@0,0/ssd@wxxxxxxxxxxxxx9d,24 (ssd3):

Jun  4 22:31:09 au11qap650tels2         Error for Command: write(10)               Error Level: Retryable

Jun  4 22:31:09 au11qap650tels2 unix:   Requested Block: 265328                    Error Block: 265328

Jun  4 22:31:09 au11qap650tels2 unix:   Vendor: EMC                                Serial Number: 4259B000a

Jun  4 22:31:09 au11qap650tels2 unix:   Sense Key: Unit Attention

Jun  4 22:31:09 au11qap650tels2 unix:   ASC: 0x29 (power on, reset, or bus reset occurred), ASCQ: 0x0, FRU: 0x0

Jun  4 22:31:11 au11qap650tels2 unix: ses21 at glm1: target 5 lun 0

Jun  4 22:31:11 au11qap650tels2 unix: ses21 is /pci@9c,700000/pci@1/pci@1/scsi@2,1/ses@5,0

What is the reason behind this............as we don't see any disruption if we add a zone with DMX array.

Tags (2)
0 Kudos
3 Replies
StephanieP1
3 Argentium

Re: All the zones affected for a host connected to VMAX

Hello,

The team is going to move this thread to the Support Forums Community where it can be addressed.

Thanks,

Stephanie

0 Kudos
RFritz11
3 Zinc

Re: All the zones affected for a host connected to VMAX

Hi, We've moved your question to the Symmetrix Support Forums where it should receive prompt attention. Thanks.

0 Kudos
Mabro1
4 Tellurium

Re: All the zones affected for a host connected to VMAX

Updated and edited post to remove unique identifier information to protect the security of your post.

0 Kudos