Hi All,

I have fine workinfg disk arrays consisting of

   1) MSA1000 and one MSA30

   2) MSA1500 with 2  MSA20

They work fine with my OpenVMS system

However  I needed some more disk space. So I connected another MSA30 to the second SCSI connecttion on my MSA1000. I was realy disapointed when the new disks did not show up in the MSA1000 controller: I could only see the "old" disks.

Then I tried to connect a MSA20 to the MSA1500. I had to insert an extra SCSI controler into the MSA1500. But also here only the "old" disk are seen.by the MSA1500 controller. When I login directly to the MSA20 a "show disks" list all the disks. I'm a little worried by the the displayed enclosure id of the MSA20 (which is 01) and is equal to the one displayed on one of the "old" boxes.

What am I missing, and how can I get my MSA1000 & MSA1500 to the the new MSA20 & MSA30 boxes?

                              Regards

                                      Jouk

I want to connect my MSA 1040 10GbE dual controller storage with HPE FlexFabric 5700 32XGT 8XG 2QSFP+ Switch using 10GbE cables. Please suggest me which cable should i use and the technology behind this? is there any options without any DAC cable? if it is DAC cable how should it be connected ? 

Thanks

TURJO

I have a vdisk that does not raise, for an electrical problem 7 of its 8 disks passed to status leftovr, apply the troubleshouting to erase the metadata, the disks passed to AVAIL status, but I could not add or remove the spare to see if it rebuilds me The vdisk, gives me error: Unable to modify the vdisk spare settings. The target vdisk is offline Virtual disk is offline (00c0ff10da380000379b4e5800000000) - Virtual disk is offline. - apply trust not in operation, - verify vdisk vd01 fix yes.not in operation.  Someone will have recovered this fault, there must be a lower level command that allows me to make a recovering of the raid5 by re-entering their disks ?.

Current status attachment.

only one controller.

Current Controller Versions Component Controller A Controller B Bundle Version TS201P007 Not Present Storage Controller Code Version T201P04 Not Present Storage Controller Loader Code Version 23.008 Not Present Memory Controller FPGA Code Version F400R02 Not Present Management Controller Code Version L201R024 Not Present Management Controller Loader Code Version not set Not Present Expander Controller Code Version 1130 Not Present CPLD Code Version 13 Not Present

The disks in the vdisk were leftover and you erased all of the metadata on them?

Well, in this case your vdisk is gone, consider to delete it.

There is a way to " dequarantine" a vdisk, but you already erased the metadata ...

See chapter " Removing a vdisk from quarantine" in SMU user guide.

For which firmware version should I update the: TS201P007 I tried with several and I could not, I would like to help me with the correct one. Thank you.

Thanks for your help.

There will be some troubleshooting to recover the metadata from the disks and recover the vdisk? In unix you can.

Do we talk about a P2000 aka MSA2000 G3?

Yes, HP MSA P2000 G3

brand new version TS252P005

http://h20564.www2.hpe.com/hpsc/swd/public/detail?sp4ts.oid=4118572&swItemId=MTX_89ecaf1f05e94eb0a1d614d7e8&swEnvOid=4064

Support are asking for the serial number for my virtual SAN. I have looked on the hosts and no sign of a serial number which I'm told will start CZ3 or SGH.

Can anyone help with this please.

Thanks

Hi

I have a dual controller MSA2000fc g1, attached to a 2nd enclosure (each controller is attached). The MSA is attached to a windows server by fibre only from controller A (not best practice I know)

I have noticed in last moth or so that controller B is rebooting itself, im getting errors like below.

I have also attached full log file for reference,

Info 2017-02-10 17:05:34 141 B6235 Management Controller IP address changed to: IP changed to: xx.xx.xx..111
Info 2017-02-10 17:05:33 139 B6234 Management Controller booted. MC code version: W420R58

Everything points to a problem with Controller B but before Before I start replacing parts, id like to get more info on these errors so i can make a better decision as what to replace.

As a side note, I have 2 disks fail (RAID 5 setup) last summer and had to rebuild array from scratch. Could these new errors be related to my probelms kast year as  result of an underlying issue, or is it just a new issue?

Thanks in advance for any help

 Info  2017-02-14 12:34:21  111 A6109  Host link up Chan0: 2 Loop IDs, External Device(s)  
Warning  2017-02-14 12:34:21  112 A6108  Host link down Chan0  
Info  2017-02-14 12:33:10  111 A6107  Host link up Chan0: 1 Loop ID  
Warning  2017-02-14 12:33:10  112 A6106  Host link down Chan0  
Info  2017-02-14 04:11:24  310 A6105  Discovery and initialization of enclosure data has completed following a rescan.  
Info  2017-02-14 04:11:20  310 B6264  Discovery and initialization of enclosure data has completed following a rescan.  
Info  2017-02-14 04:11:04  19 A6104  Rescan bus done. Reason Code: 0. Found 18 drives, 2 Drive Enclosures  
Info  2017-02-14 04:10:57  211 A6103  SAS Topology Change: Chan0, 194 elements, 4 expanders, 2 native levels, 2 partner levels, 40 device PHYs  
Info  2017-02-14 04:10:53  114 A6102  Drive link down Chan0  
Info  2017-02-14 04:10:52  19 B6263  Rescan bus done. Reason Code: 0. Found 18 drives, 2 Drive Enclosures  
Info  2017-02-14 04:10:46  211 B6262  SAS Topology Change: Chan0, 194 elements, 4 expanders, 2 native levels, 2 partner levels, 40 device PHYs  
Info  2017-02-14 04:10:41  114 B6261  Drive link down Chan0  
Info  2017-02-14 04:09:18  310 A6101  Discovery and initialization of enclosure data has completed following a rescan.  
Info  2017-02-14 04:09:14  310 B6260  Discovery and initialization of enclosure data has completed following a rescan.  
Info  2017-02-14 04:08:58  19 A6100  Rescan bus done. Reason Code: 0. Found 18 drives, 2 Drive Enclosures  
Info  2017-02-14 04:08:51  211 A6099  SAS Topology Change: Chan0, 194 elements, 4 expanders, 2 native levels, 2 partner levels, 40 device PHYs  
Info  2017-02-14 04:08:47  114 A6098  Drive link down Chan0  
Info  2017-02-14 04:08:46  19 B6259  Rescan bus done. Reason Code: 0. Found 18 drives, 2 Drive Enclosures  
Info  2017-02-14 04:08:37  211 B6258  SAS Topology Change: Chan0, 194 elements, 4 expanders, 2 native levels, 2 partner levels, 40 device PHYs  
Info  2017-02-14 04:08:33  114 B6257  Drive link down Chan0  
Info  2017-02-14 04:07:14  181 B6256  LAN configuration parameters have been set  
Info  2017-02-14 04:07:11  141 B6255  Management Controller IP address changed to: IP changed to: xx.xx.xx..111  
Info  2017-02-14 04:07:10  139 B6254  Management Controller booted. MC code version: W420R58  
Info  2017-02-11 23:34:49  33 B6253  Time/date has been changed to 2017-02-11 23:34:48  
Info  2017-02-10 22:55:43  310 B6252  Discovery and initialization of enclosure data has completed following a rescan.  
Info  2017-02-10 22:55:39  310 A6097  Discovery and initialization of enclosure data has completed following a rescan.  
Info  2017-02-10 22:55:15  19 B6251  Rescan bus done. Reason Code: 0. Found 18 drives, 2 Drive Enclosures  
Info  2017-02-10 22:55:08  211 B6250  SAS Topology Change: Chan0, 194 elements, 4 expanders, 2 native levels, 2 partner levels, 40 device PHYs  
Info  2017-02-10 22:55:04  19 A6096  Rescan bus done. Reason Code: 0. Found 18 drives, 2 Drive Enclosures  
Info  2017-02-10 22:55:03  114 B6249  Drive link down Chan0  
Info  2017-02-10 22:54:57  211 A6095  SAS Topology Change: Chan0, 194 elements, 4 expanders, 2 native levels, 2 partner levels, 40 device PHYs  
Info  2017-02-10 22:54:52  114 A6094  Drive link down Chan0  
Info  2017-02-10 22:53:52  310 B6248  Discovery and initialization of enclosure data has completed following a rescan.  
Info  2017-02-10 22:53:29  310 B6247  Discovery and initialization of enclosure data has completed following a rescan.  
Info  2017-02-10 22:53:25  310 A6093  Discovery and initialization of enclosure data has completed following a rescan.  
Info  2017-02-10 22:53:11  19 B6246  Rescan bus done. Reason Code: 0. Found 18 drives, 2 Drive Enclosures  
Info  2017-02-10 22:53:04  211 B6245  SAS Topology Change: Chan0, 194 elements, 4 expanders, 2 native levels, 2 partner levels, 40 device PHYs  
Info  2017-02-10 22:53:00  114 B6244  Drive link down Chan0  
Info  2017-02-10 22:53:00  19 A6092  Rescan bus done. Reason Code: 0. Found 18 drives, 2 Drive Enclosures  
Info  2017-02-10 22:52:49  211 A6091  SAS Topology Change: Chan0, 194 elements, 4 expanders, 2 native levels, 2 partner levels, 40 device PHYs  
Info  2017-02-10 22:52:48  211 B6243  SAS Topology Change: Chan0, 194 elements, 4 expanders, 2 native levels, 2 partner levels, 40 device PHYs  
Info  2017-02-10 22:52:45  114 A6090  Drive link down Chan0  
Info  2017-02-10 22:51:28  181 A6089  LAN configuration parameters have been set  
Info  2017-02-10 22:51:25  141 A6088  Management Controller IP address changed to: IP changed to: xx.xx.xx..110  
Info  2017-02-10 22:51:24  139 A6087  Management Controller booted. MC code version: W420R58  
Info  2017-02-10 17:08:06  310 B6242  Discovery and initialization of enclosure data has completed following a rescan.  
Info  2017-02-10 17:08:00  310 A6086  Discovery and initialization of enclosure data has completed following a rescan.  
Info  2017-02-10 17:07:41  310 B6241  Discovery and initialization of enclosure data has completed following a rescan.  
Info  2017-02-10 17:07:25  19 A6085  Rescan bus done. Reason Code: 0. Found 18 drives, 2 Drive Enclosures  
Info  2017-02-10 17:07:19  211 B6240  SAS Topology Change: Chan0, 193 elements, 4 expanders, 2 native levels, 2 partner levels, 40 device PHYs  
Info  2017-02-10 17:07:13  211 A6084  SAS Topology Change: Chan0, 194 elements, 4 expanders, 2 native levels, 2 partner levels, 40 device PHYs  
Info  2017-02-10 17:07:09  114 A6083  Drive link down Chan0  
Info  2017-02-10 17:07:08  19 B6239  Rescan bus done. Reason Code: 0. Found 18 drives, 2 Drive Enclosures  
Info  2017-02-10 17:07:02  211 B6238  SAS Topology Change: Chan0, 194 elements, 4 expanders, 2 native levels, 2 partner levels, 40 device PHYs  
Info  2017-02-10 17:06:58  114 B6237  Drive link down Chan0  
Info  2017-02-10 17:05:38  181 B6236  LAN configuration parameters have been set  
Info  2017-02-10 17:05:34  141 B6235  Management Controller IP address changed to: IP changed to: xx.xx.xx..111  
Info  2017-02-10 17:05:33  139 B6234  Management Controller booted. MC code version: W420R58  
Info  2017-02-10 05:34:49  33 B6233  Time/date has been changed to 2017-02-10 05:34:48  
Info  2017-02-09 05:34:47  33 B6232  Time/date has been changed to 2017-02-09 05:34:48  
Info  2017-02-08 23:55:45  310 A6082  Discovery and initialization of enclosure data has completed following a rescan.  
Info  2017-02-08 23:55:44  310 B6231  Discovery and initialization of enclosure data has completed following a rescan.  
Info  2017-02-08 23:55:25  19 B6230  Rescan bus done. Reason Code: 0. Found 18 drives, 2 Drive Enclosures  
Info  2017-02-08 23:55:18  211 B6229  SAS Topology Change: Chan0, 194 elements, 4 expanders, 2 native levels, 2 partner levels, 40 device PHYs  
Info  2017-02-08 23:55:14  19 A6081  Rescan bus done. Reason Code: 0. Found 18 drives, 2 Drive Enclosures  
Info  2017-02-08 23:55:13  114 B6228  Drive link down Chan0  
Info  2017-02-08 23:55:07  211 A6080  SAS Topology Change: Chan0, 194 elements, 4 expanders, 2 native levels, 2 partner levels, 40 device PHYs  
Info  2017-02-08 23:55:03  114 A6079  Drive link down Chan0  
Info  2017-02-08 23:53:43  310 B6227  Discovery and initialization of enclosure data has completed following a rescan.  
Info  2017-02-08 23:53:37  310 A6078  Discovery and initialization of enclosure data has completed following a rescan.  
Info  2017-02-08 23:53:22  19 B6226  Rescan bus done. Reason Code: 0. Found 18 drives, 2 Drive Enclosures  
Info  2017-02-08 23:53:16  211 B6225  SAS Topology Change: Chan0, 194 elements, 4 expanders, 2 native levels, 2 partner levels, 40 device PHYs  
Info  2017-02-08 23:53:12  19 A6077  Rescan bus done. Reason Code: 0. Found 18 drives, 2 Drive Enclosures  
Info  2017-02-08 23:53:11  114 B6224  Drive link down Chan0  
Info  2017-02-08 23:53:05  211 A6076  SAS Topology Change: Chan0, 194 elements, 4 expanders, 2 native levels, 2 partner levels, 40 device PHYs  
Info  2017-02-08 23:53:01  114 A6075  Drive link down Chan0  
Info  2017-02-08 23:51:39  181 A6074  LAN configuration parameters have been set  
Info  2017-02-08 23:51:34  141 A6073  Management Controller IP address changed to: IP changed to: xx.xx.xx..110  
Info  2017-02-08 23:51:33  139 A6072  Management Controller booted. MC code version: W420R58  
Info  2017-02-08 17:34:48  33 B6223  Time/date has been changed to 2017-02-08 17:34:47  
Info  2017-02-08 04:53:25  310 A6071  Discovery and initialization of enclosure data has completed following a rescan.  
Info  2017-02-08 04:53:19  310 B6222  Discovery and initialization of enclosure data has completed following a rescan.  
Info  2017-02-08 04:53:04  19 A6070  Rescan bus done. Reason Code: 0. Found 18 drives, 2 Drive Enclosures  
Info  2017-02-08 04:52:58  211 A6069  SAS Topology Change: Chan0, 194 elements, 4 expanders, 2 native levels, 2 partner levels, 40 device PHYs  
Info  2017-02-08 04:52:53  19 B6221  Rescan bus done. Reason Code: 0. Found 18 drives, 2 Drive Enclosures  
Info  2017-02-08 04:52:53  114 A6068  Drive link down Chan0  
Info  2017-02-08 04:52:46  211 B6220  SAS Topology Change: Chan0, 194 elements, 4 expanders, 2 native levels, 2 partner levels, 40 device PHYs  
Info  2017-02-08 04:52:41  114 B6219  Drive link down Chan0  
Info  2017-02-08 04:51:23  310 A6067  Discovery and initialization of enclosure data has completed following a rescan.  
Info  2017-02-08 04:51:17  310 B6218  Discovery and initialization of enclosure data has completed following a rescan.  
Info  2017-02-08 04:51:02  19 A6066  Rescan bus done. Reason Code: 0. Found 18 drives, 2 Drive Enclosures  
Info  2017-02-08 04:50:55  211 A6065  SAS Topology Change: Chan0, 194 elements, 4 expanders, 2 native levels, 2 partner levels, 40 device PHYs  
Info  2017-02-08 04:50:50  19 B6217  Rescan bus done. Reason Code: 0. Found 18 drives, 2 Drive Enclosures  
Info  2017-02-08 04:50:50  114 A6064  Drive link down Chan0  
Info  2017-02-08 04:50:43  211 B6216  SAS Topology Change: Chan0, 194 elements, 4 expanders, 2 native levels, 2 partner levels, 40 device PHYs  
Info  2017-02-08 04:50:40  114 B6215  Drive link down Chan0  
Info  2017-02-08 04:49:20  181 B6214  LAN configuration parameters have been set  
Info  2017-02-08 04:49:17  141 B6213  Management Controller IP address changed to: IP changed to: xx.xx.xx..111  
Info  2017-02-08 04:49:16  139 B6212  Management Controller booted. MC code version: W420R58  
Info  2017-02-06 17:34:48  33 B6211  Time/date has been changed to 2017-02-06 17:34:47  
Info  2017-02-03 23:34:48  33 B6210  Time/date has been changed to 2017-02-03 23:34:47  
Info  2017-02-01 11:34:48  33 B6209  Time/date has been changed to 2017-02-01 11:34:47  
Info  2017-01-31 12:09:37  111 A6063  Host link up Chan0: 2 Loop IDs, External Device(s)  
Warning  2017-01-31 12:09:36  112 A6062  Host link down Chan0  
Info  2017-01-31 12:08:28  111 A6061  Host link up Chan0: 1 Loop ID  
Warning  2017-01-31 12:08:25  112 A6060  Host link down Chan0  
Info  2017-01-29 23:34:48  33 B6208  Time/date has been changed to 2017-01-29 23:34:47  
Info  2017-01-29 12:00:20  310 A6059  Discovery and initialization of enclosure data has completed following a rescan.  
Info  2017-01-29 12:00:15  310 B6207  Discovery and initialization of enclosure data has completed following a rescan.  
Info  2017-01-29 11:59:59  19 A6058  Rescan bus done. Reason Code: 0. Found 18 drives, 2 Drive Enclosures  
Info  2017-01-29 11:59:52  211 A6057  SAS Topology Change: Chan0, 194 elements, 4 expanders, 2 native levels, 2 partner levels, 40 device PHYs  
Info  2017-01-29 11:59:48  19 B6206  Rescan bus done. Reason Code: 0. Found 18 drives, 2 Drive Enclosures  
Info  2017-01-29 11:59:48  114 A6056  Drive link down Chan0  
Info  2017-01-29 11:59:41  211 B6205  SAS Topology Change: Chan0, 194 elements, 4 expanders, 2 native levels, 2 partner levels, 40 device PHYs  
Info  2017-01-29 11:59:37  114 B6204  Drive link down Chan0  
Info  2017-01-29 11:58:14  310 A6055  Discovery and initialization of enclosure data has completed following a rescan.  
Info  2017-01-29 11:58:08  310 B6203  Discovery and initialization of enclosure data has completed following a rescan.  
Info  2017-01-29 11:57:54  19 A6054  Rescan bus done. Reason Code: 0. Found 18 drives, 2 Drive Enclosures  
Info  2017-01-29 11:57:46  211 A6053  SAS Topology Change: Chan0, 194 elements, 4 expanders, 2 native levels, 2 partner levels, 40 device PHYs  
Info  2017-01-29 11:57:42  19 B6202  Rescan bus done. Reason Code: 0. Found 18 drives, 2 Drive Enclosures  
Info  2017-01-29 11:57:42  114 A6052  Drive link down Chan0  
Info  2017-01-29 11:57:35  211 B6201  SAS Topology Change: Chan0, 194 elements, 4 expanders, 2 native levels, 2 partner levels, 40 device PHYs  
Info  2017-01-29 11:57:31  114 B6200  Drive link down Chan0  
Info  2017-01-29 11:56:13  181 B6199  LAN configuration parameters have been set  
Info  2017-01-29 11:56:09  141 B6198  Management Controller IP address changed to: IP changed to: xx.xx.xx..111  
Info  2017-01-29 11:56:08  139 B6197  Management Controller booted. MC code version: W420R58  

Can you please share the image of the cable after filing it. 

Also any link from where can we buy new MSA 1000 RJ45Z serial cable. 

The partno. is 259992-001 or 316131-001.

Hi All,

I have fine workinfg disk arrays consisting of

   1) MSA1000 and one MSA30

   2) MSA1500 with 2  MSA20

They work fine with my OpenVMS system

However  I needed some more disk space. So I connected another MSA30 to the second SCSI connecttion on my MSA1000. I was realy disapointed when the new disks did not show up in the MSA1000 controller: I could only see the "old" disks.

Then I tried to connect a MSA20 to the MSA1500. I had to insert an extra SCSI controler into the MSA1500. But also here only the "old" disk are seen.by the MSA1500 controller. When I login directly to the MSA20 a "show disks" list all the disks. I'm a little worried by the the displayed enclosure id of the MSA20 (which is 01) and is equal to the one displayed on one of the "old" boxes.

What am I missing, and how can I get my MSA1000 & MSA1500 to the the new MSA20 & MSA30 boxes?

                              Regards

                                      Jouk

Just an update:

Re-installed ESXi on hosts (fresh install instead of upgrade), also deleted and recreated disk groups and volumes on the SAN. Appears to be working now.

Wondering if this has something to do with the original volumes being created before changing SAN LUN option "Not Ready" to "Illegal Request" inside of the SMU.

Either way, working now.

You should be able to do it online if the host's connected to the SAN support it.

AFAIK, you can expand disk groups on the MSA 2040 (add disks) if they are linear volumes, however if I recall you cannot do this with volumes on virtual disk groups.

After adding the disks, wait for the completion of the operation and then rescan the storage on the hosts, the added space should be available.

Hi,

Can the "HP MSA 2040 SAS Dual Controller" be used as a shared storage to build a Hyper-V cluster of 4 HP DL380 Gen9 Nodes (with windows server 2016)? all nodes are directly connected to the MSA with dual MiniSAS cables.

Thanks.

Thank you, i have performed all test successfully 

Hi,
recently I've reconfigured all storage pools and I've started assigning volumes from LUN ID 1, leaving free LUN ID 0 , as suggested from some colleagues. Is this correct or not? I have this doubt because now, after a rescan, all hosts are still seeing a LUN 0 ID device for every other LUNs defined, but the reported device type is "enclosure", while other LUNs is rightly reported as "disk". What does it means?

Hi

do we loose whole virtual pool in case of loosing any of it's internal Vraids ?