Eva4000 cv9.1

 
Sarek
Occasional Contributor

Eva4000 cv9.1

Have a eva4000 (xcs611)

Have installed cv9.1 (the old version 8.01 dind't work anymore and was uninstalled).
When the install is done we have to discover the eva. This doesn't work. In the loggin i see the following:

Sep/7/2009 15:30:39.393713, ccb2_fsscsi, 6628, 2212, 1, dev_win, 448, 00000000 1d 00 00 00 64 00 * d *
Sep/7/2009 15:30:39.394052, ccb2_fsscsi, 6628, 2212, 1, dev_win, 501, ScsiDevice::_passThroughOut failed: ERR:02-E0028 (CCB2) SCSI_BUSY
Sep/7/2009 15:30:39.394121, ccb2_fsscsi, 6628, 2212, 1, dev_win, 502, Opcode: Send Diagnostic
Sep/7/2009 15:30:39.394179, ccb2_fsscsi, 6628, 2212, 1, dev_win, 503, CDB:
Sep/7/2009 15:30:39.394260, ccb2_fsscsi, 6628, 2212, 1, dev_win, 504, 00000000 1d 00 00 00 64 00 * d *
Sep/7/2009 15:30:39.394351, ccb2_fsscsi, 6628, 2212, 1, scsilun, 423, Send diag to: \\.\Scsi3: failed: ERR:02-E0028 (CCB2) SCSI_BUSY
Sep/7/2009 15:30:39.394415, ccb2_fsscsi, 6628, 2212, 1, scsilun, 424, Status: 40
Sep/7/2009+-------------------- EVENT HISTORY for thread: 2212 BEFORE ERROR -----------------------+
Sep/7/2009| 15:30:39.394527, cv_scmi, 6628, 2212, 2, evagpsctlrpath, 328, failed to send command to SCMI: ERR:02-E0028 (CCB2) SCSI_BUSY
Sep/7/2009+-------------------- END OF EVENT HISTORY. ERROR EVENT FOLLOWS ------------------------+
Sep/7/2009 15:30:39.394614, cv_scmi, 6628, 2212, 1, realscmi, 789, SCMI command failed. Fn: 4012-SCMI_F_NSC_GET_IDENTITY. Err: ERR:02-E0028 (CCB2) SCSI_BUSY
Sep/7/2009 15:30:39.394889, cv_scmi, 6628, 2212, 1, realscmi, 1413, SCMI transport failure: SCMITRANS_ERR
Sep/7/2009 15:30:39.394967, cv_scmi, 6628, 2212, 1, support, 945, Protocol version could not be determined
Sep/7/2009 15:30:39.395049, cveva, 6628, 2212, 1, evaimpl, 484, Failed to get ctlr path info with path uid = PBA24F29SVU0DA:\\.\Scsi3:-0-1-0
Sep/7/2009 15:30:39.395147, cveva, 6628, 2212, 1, evaimpl, 356, Ignoring failed path: PBA24F29SVU0DA:\\.\Scsi3:-0-1-0
Sep/7/2009 15:30:39.395366, cveva, 6628, 2212, 1, sob_discovery, 348, Failed to get controller list: (0) Successful Status
Sep/7/2009 15:30:39.396305, cveva, 6628, 2212, 2, sob_discovery, 280, ******************************************************************
Sep/7/2009 15:30:39.396378, cveva, 6628, 2212, 2, sob_discovery, 281, * Config
Sep/7/2009 15:30:39.396473, cveva, 6628, 2212, 2, sob_discovery, 282, *
Sep/7/2009 15:30:39.397124, cveva, 6628, 2212, 2, sob_discovery, 298, * No arrays discovered
Sep/7/2009 15:30:39.397187, cveva, 6628, 2212, 2, sob_discovery, 298, *
Sep/7/2009 15:30:39.397279, cveva, 6628, 2212, 2, sob_discovery, 298, * Path Vendor Product Product Node Serial Valid
Sep/7/2009 15:30:39.397401, cveva, 6628, 2212, 2, sob_discovery, 298, * Rev WWN Number
Sep/7/2009 15:30:39.397505, cveva, 6628, 2212, 2, sob_discovery, 298, * ---------------- ------ ------- ------- ------------------- -------------- -----
Sep/7/2009 15:30:39.397601, cveva, 6628, 2212, 2, sob_discovery, 298, * \\.\Scsi2:-0-1-0 HP HSV200 6110 5000-1FE1-500F-84E0 PBA24F19SV50K4 Valid
Sep/7/2009 15:30:39.397696, cveva, 6628, 2212, 2, sob_discovery, 298, * \\.\Scsi2:-0-2-0 HP HSV200 6110 5000-1FE1-500F-84E0 PBA24F29SVU0DA Valid
Sep/7/2009 15:30:39.397790, cveva, 6628, 2212, 2, sob_discovery, 298, * \\.\Scsi3:-0-0-0 HP HSV200 6110 5000-1FE1-500F-84E0 PBA24F19SV50K4 Valid
Sep/7/2009 15:30:39.397885, cveva, 6628, 2212, 2, sob_discovery, 298, * \\.\Scsi3:-0-1-0 HP HSV200 6110 5000-1FE1-500F-84E0 PBA24F29SVU0DA Valid
Sep/7/2009 15:30:39.397948, cveva, 6628, 2212, 2, sob_discovery, 298, *
Sep/7/2009 15:30:39.398006, cveva, 6628, 2212, 2, sob_discovery, 301, *
Sep/7/2009 15:30:39.398083, cveva, 6628, 2212, 2, sob_discovery, 302, ******************************************************************
Sep/7/2009 15:30:39.398192, cveva, 6628, 2212, 2, sob_discovery, 156, ******************************************************************
Sep/7/2009 15:30:39.398263, cveva, 6628, 2212, 2, sob_discovery, 157, * Stats
Sep/7/2009 15:30:39.398331, cveva, 6628, 2212, 2, sob_discovery, 160, * CCB object counts:
Sep/7/2009 15:30:39.398416, cveva, 6628, 2212, 2, sob_discovery, 187, ******************************************************************
Sep/7/2009 15:30:39.398485, cveva, 6628, 2212, 2, sob_discovery, 144, SOB discovery complete

With evaperf ls command i get the following output:

C:\Program Files\Hewlett-Packard\EVA Performance Monitor>evaperf.exe ls

Device Path Target LUN Product Product Ctlr Serial Hardware Name
Node
ID ID ID Rev. Ver.

---------- ---- ------ --- ------- ------- ------- -------------- -------- -----
-------------- -------------------
\\.\Scsi2: 0 1 0 HSV200 6110 50K4(B) PBA24F19SV50K4 200 5000-
1FE1-500F-84E0 5000-1FE1-500F-84E0
\\.\Scsi2: 0 2 0 HSV200 6110 U0DA(A) PBA24F29SVU0DA 200 5000-
1FE1-500F-84E0 5000-1FE1-500F-84E0


C:\Program Files\Hewlett-Packard\EVA Performance Monitor>

I have looked at the SAN zoning and this is good.

Any ideas anyone
2 REPLIES 2
Víctor Cespón
Honored Contributor

Re: Eva4000 cv9.1

CV and Evaperf see both controllers so does not seem a SAN problem. ¿did you try to restart Command View service?

Also, try cvutil release_locks -wwn

is the WWN of that EVA.
Sarek
Occasional Contributor

Re: Eva4000 cv9.1

release_locks -wwn done for bothe the HBA controllers. No change.