Connexion MSA 2052 et esxi 6.0

[nkl92]

Bonjour,

je rencontre un problème de connexion entre ma baie MSA2052 et serveur DL380p GEN8 avec vsphere 6.0. En effet au démarrage du serveur esx on à bien les disques mais le démarrage bloque :

Google Translated

Hi,

I'm having a connection problem between my MSA2052 array and DL380p GEN8 server with vsphere 6.0. Indeed at the start of the esx server we have good disks but the startup blocks:

2019-02-20T18:46:55.940Z cpu22:34830 opID=be214dd3)World: 15571: VC opID HB-SpecSync-host-15@0-168d1e5f-44-8d04 maps to vmkernel opID be214dd3
2019-02-20T18:46:55.940Z cpu22:34830 opID=be214dd3)Config: 681: "HostLocalSwapDirEnabled" = 0, Old Value: 0, (Status: 0x0)
2019-02-20T18:47:05.265Z cpu12:33257)<4>hpsa 0000:0a:00.0: Acknowledging event: 0x80000002 (HP SSD Smart Path configuration change)
2019-02-20T18:47:05.311Z cpu12:33257)<6>hpsa 0000:0a:00.0: added scsi 2:2:0:0: Enclosure HP SPS-CHASSIS PHYS DRV SSDSmartPathCap- En- Exp
2019-02-20T18:47:15.316Z cpu5:33251)<4>hpsa 0000:0a:00.0: Acknowledging event: 0x80000002 (HP SSD Smart Path configuration change)
2019-02-20T18:47:15.383Z cpu5:33251)<6>hpsa 0000:0a:00.0: added scsi 2:2:1:0: Direct-Access HP EG0900FBVFQ PHYS DRV SSDSmartPathCap- En- Exp=
2019-02-20T18:47:15.383Z cpu5:33251)<6>hpsa 0000:0a:00.0: added scsi 2:2:2:0: Direct-Access HP EG0900FBVFQ PHYS DRV SSDSmartPathCap- En- Exp=
2019-02-20T18:47:15.383Z cpu5:33251)<6>hpsa 0000:0a:00.0: added scsi 2:2:3:0: Direct-Access HP EG001200JWJNK PHYS DRV SSDSmartPathCap- En- Exp=
2019-02-20T18:47:15.383Z cpu5:33251)<6>hpsa 0000:0a:00.0: added scsi 2:2:4:0: Direct-Access HP EG001200JWJNK PHYS DRV SSDSmartPathCap- En- Exp=
2019-02-20T18:47:15.383Z cpu5:33251)<6>hpsa 0000:0a:00.0: added scsi 2:2:5:0: Direct-Access HP EG001200JWJNK PHYS DRV SSDSmartPathCap- En- Exp=
2019-02-20T18:47:15.383Z cpu5:33251)<6>hpsa 0000:0a:00.0: added scsi 2:2:6:0: Direct-Access HP EG001200JWJNK PHYS DRV SSDSmartPathCap- En- Exp=
2019-02-20T18:47:15.383Z cpu5:33251)<6>hpsa 0000:0a:00.0: added scsi 2:2:7:0: Direct-Access HP EG001200JWJNK PHYS DRV SSDSmartPathCap- En- Exp=
2019-02-20T18:47:15.383Z cpu5:33251)<6>hpsa 0000:0a:00.0: added scsi 2:2:8:0: Direct-Access HP EG001200JWJNK PHYS DRV SSDSmartPathCap- En- Exp=
2019-02-20T18:47:15.383Z cpu5:33251)<6>hpsa 0000:0a:00.0: added scsi 2:2:9:0: Direct-Access HP EG001200JWJNK PHYS DRV SSDSmartPathCap- En- Exp=
2019-02-20T18:47:15.383Z cpu5:33251)<6>hpsa 0000:0a:00.0: added scsi 2:2:10:0: Direct-Access HP EG001200JWJNK PHYS DRV SSDSmartPathCap- En- Exp
2019-02-20T18:47:15.383Z cpu5:33251)<6>hpsa 0000:0a:00.0: added scsi 2:2:11:0: Direct-Access HP EG001200JWJNK PHYS DRV SSDSmartPathCap- En- Exp
2019-02-20T18:47:15.383Z cpu5:33251)<6>hpsa 0000:0a:00.0: added scsi 2:2:12:0: Direct-Access HP EG001200JWJNK PHYS DRV SSDSmartPathCap- En- Exp
2019-02-20T18:47:15.383Z cpu5:33251)<6>hpsa 0000:0a:00.0: added scsi 2:2:13:0: Direct-Access HP EG001200JWJNK PHYS DRV SSDSmartPathCap- En- Exp
2019-02-20T18:47:15.383Z cpu5:33251)<6>hpsa 0000:0a:00.0: added scsi 2:2:14:0: Direct-Access HP EG001200JWJNK PHYS DRV SSDSmartPathCap- En- Exp
2019-02-20T18:47:15.385Z cpu5:33251)ScsiScan: 1746: Add path: vmhba3:C2:T1:L0
2019-02-20T18:47:15.385Z cpu5:33251)ScsiPath: 5569: Plugin 'NMP' claimed path 'vmhba3:C2:T1:L0'
2019-02-20T18:47:15.410Z cpu5:33251)vmw_psp_fixed: psp_fixedSelectPathToActivateInt:479: Changing active path from NONE to vmhba3:C2:T1:L0 for device "Unregistered Devi
2019-02-20T18:47:15.410Z cpu5:33251)StorageApdHandler: 982: APD Handle Created with lock[StorageApd-0x4302769fe5c0]
2019-02-20T18:47:15.410Z cpu5:33251)ScsiEvents: 501: Event Subsystem: Device Events, Created!
2019-02-20T18:47:15.410Z cpu5:33251)VMWARE SCSI Id: Id for vmhba3:C2:T1:L0
0x50 0x00 0xcc 0xa0 0x71 0x10 0x24 0xd4 0x45 0x47 0x30 0x39 0x30 0x30

J'ai ensuite supprimé les pools et volumes, arrêté le serveur esxi et j'ai activé l'option Missing LUN Response: request illegal et redémarré le serveur. Là pas de message de blocage au démarrage et en me connectant sur vsphere je vois les périphériques donc bingo et bien non, car après j'ai paramétré les pools et volumes sur la baie mais un rescan à fait que ça a planté l'esxi et j'ai du redémarré et revenir au même point de départ sans que je puisse retrouver mais disques sur vpshere malgré plusieurs configurations et redémarrage.

Google Translated

I then deleted the pools and volumes, stopped the esxi server and enabled the Missing LUN Response: request illegal option and restarted the server. There is no blocking message at startup and connecting to vsphere I see the devices so bingo and no, because after I set the pools and volumes on the bay but a rescan that has planted the esxi and I restarted and return to the same starting point without being able to find but vpshere disks despite several configurations and restart.

2019-02-20T18:47:15.420Z cpu5:33251)ScsiDeviceIO: 7047: QErr is correctly set to 0x0 for device naa.5000cca0711024d4.
2019-02-20T18:47:15.438Z cpu5:33251)ScsiDeviceIO: 7544: Could not detect setting of sitpua for device naa.5000cca0711024d4. Error Not supported.
2019-02-20T18:49:31.290Z cpu13:33041)ScsiEvents: 300: EventSubsystem: Device Events, Event Mask: 180, Parameter: 0x4304afe74630, Registered!
2019-02-20T18:49:31.297Z cpu21:33031)ScsiScan: 1746: Add path: vmhba3:C2:T2:L0
2019-02-20T18:49:31.298Z cpu21:33031)ScsiScan: 1746: Add path: vmhba3:C2:T3:L0
2019-02-20T18:49:31.300Z cpu21:33031)ScsiScan: 1746: Add path: vmhba3:C2:T4:L0
2019-02-20T18:49:31.301Z cpu21:33031)ScsiScan: 1746: Add path: vmhba3:C2:T5:L0
2019-02-20T18:49:31.302Z cpu21:33031)ScsiScan: 1746: Add path: vmhba3:C2:T6:L0
2019-02-20T18:49:31.303Z cpu21:33031)ScsiScan: 1746: Add path: vmhba3:C2:T7:L0
2019-02-20T18:49:31.304Z cpu21:33031)ScsiScan: 1746: Add path: vmhba3:C2:T8:L0
2019-02-20T18:49:31.305Z cpu21:33031)ScsiScan: 1746: Add path: vmhba3:C2:T9:L0
2019-02-20T18:49:31.306Z cpu21:33031)ScsiScan: 1746: Add path: vmhba3:C2:T10:L0
2019-02-20T18:49:31.307Z cpu21:33031)ScsiScan: 1746: Add path: vmhba3:C2:T11:L0
2019-02-20T18:49:31.309Z cpu21:33031)ScsiScan: 1746: Add path: vmhba3:C2:T12:L0
2019-02-20T18:49:31.310Z cpu21:33031)ScsiScan: 1746: Add path: vmhba3:C2:T13:L0

Merci pour votre aide.

Thanks for your help.

[RaviTyagi]

Hello 

Greetings !

As per the hypervisor logs shared by you , i do not see a problem with it .  have you got your MSA checked by the HPE Hardware Team , If Not Please reach out to them for further support .

Regards,

RRT

I am an HPE Employee

[nkl92]

Hello
Thanks for your reply, no I did not have the service MSA support, because in the logs the bay is well seen but when starting the Esx clui-ci crashes on Could not detect setting of Sitpua for device Naa. 50000398e8818325.
Ok I contact the MSA service Thank you.

regards