HPE Storage Solutions Forum - Storage Area Networks (SAN) - Small and Medium Business
Share |



MSA 2040 G4 - Locking ID to register Advance Data Services?Open in a New Window

Hi all, i have a new MSA 2040 G4 storage and i need to register my MSA Advanced Data Services LTU. Visiting http://MyEnterpriseLicense.hpe.com i have to imput my Entitlement Order Number. After that the page asks for the "Locking ID" . Where can i find this?

 

Thank you in advance, George

 

Register new MSA 2040 G4 to hpe.comOpen in a New Window

Greedings All! I have a new MSA 2040 G4 Storage and i want to register it at hpe.com under my account. But under "Link warranties" the page wants to input both Serial Number and Product Number. What sould i use for my MSA?

Thank you in advance, George

 

Migrating from MSA 2012sa to MSA 2042, data copying questionOpen in a New Window

Hi,

I have a pretty basic setup with two ESXi servers connected to the MSA 2012sa by SAS and we are getting ready to migrate to an MSA 2042 connected by FC.

The 2012 SAN has two volumes, one for storing VMs and another one for enterprise files. I only have a vSphere Essentials licence, so no vMotion.

What would be the best and fastest way to copy all my data to the new SAN.

Downtime is possible during the week-ends but if I could do some steps during production time, that would be a big plus.

Right now my plan was to connect the new SAN to both ESXi servers and use vCenter to shutdown then migrate the VMs (storage only) to the new SAN.

Is there a better way without getting vMotion? Maybe some HP SAN tool I don't know about.

Thanks

 

MSA 2040 VASAOpen in a New Window

Hi,
I've read in HP specification page / document for MSA 2040 that supports VMware VASA, but I don't understand how to get this functionality. For configure VASA, on VMware side, the requested parameters are "Storage Provider" url:port and user/passw. I'm not able to find information about this, neither in MSA 2040 web configuration page or cli, neither HP documentation. Are needed some additional license or software? Someone can help me?

Thanks in advance

 

P2040 what if a Vraid fail on virtual poolOpen in a New Window

Hi

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

 

 

MSA 2040 LUN 0Open in a New Window

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?

 

HP MSA 2040 SAS Dual Controller as Shared StorageOpen in a New Window

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.

 

Controller Rebooting itselfOpen in a New Window

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  

 

Update FirmwareOpen in a New Window

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.

 

Connecting MSA30/MSA20 to MSA100/MSA1500Open in a New Window

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

 

Connecting MSA 1040 10GbE dual controller storage with HPE FlexFabric 5700 32XGT 8XG 2QSFP+ SwitchOpen in a New Window

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

 

recovering vdiskOpen in a New Window

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

 

Not operating one of the two controllers hp MSA p2000 G3Open in a New Window

When planning a power failure in the building, we had to turn off the HP P2000 G3 MSA Array Systems (2 controllers and 2 power supply unit). When the LED on the front panel of the figure 8.

Behind PUF flashes orange. Login to the web interface can not be on one controller. In putty can be connected to any controller, first login, but in the performance of any team, does not give any result. If you pull out a broken controller, the HP MSA P2000 G3 works. Tried to swap flash, replace the batteries in the controller, the controllers were reversed, I tried to run only broken the controller - there is no result. The logs only this error - Supercapacitor failure. Status cell 1voltage is too high (24). Article: failure (12) (p2: 3088 (or 3190,3283,3317,3139,3232), p3: 0).

 

HP Storageworks G3 P2000 Firmware? IssueOpen in a New Window

Hello Everyone.

We recently had a power failure and afterwards when our p2000 came back online, one of the controllers seems to have failed. The MAC and IP both show as all 0 and it will not take any settings push to it through ssh. The commands return as successful, but there is no actual change.

We went through one of our supplier for a refurbished controller and slipped it in. It had a higher firmware version and the upgrading of the other one appeared to go well. However the expander controller code version appears to be different between them despite a match. 

The logs are now continuously being spammed every 5 minutes with the error seen in the second picture

( The firmware version is not compatible, HP SPS-CHASSIS 2028)

When I restart the new controller in A, it seems like the data failover is working when I restart controller A. Controller statistics shows new data reading and writing on B when this occurs. 

I'm hoping I can get a little more insight into these behaviors as i'm fairly certain I have exhausted my searching attempts.

Thank you.

 

firmware.PNGwarnings.PNGrearview.PNG

 

Storageworks MSA 2312fc deadOpen in a New Window

Dear community,

I wanted to replace my server rack and shutdown all components, also my MSA 2312fc. After shutdown I detach power and replace my rack.

Unfortunately all hardware starts without problems except my MSA 2312fc. Both power supply indicators displays only green. The front error indicator of the MSA displays orange.

The harddisk indicators glows only for 2 seconds when switching the MSA on or when detaching a harddisk and attaching again.

All led indicators on the back of both (!) fc-controllers are off, the CLIs doesn't answer. IT seems, that both controllers are dead. But: after opening one controller I saw that there is a standard power plug on the board. Connecting this power plug the controller is alive again. Therefore I changed the backplane (only single point of failure), because of the guess that the controllers get no power. Unfortunately without success story...

Is there any idea?

My second question: FC is nice, but oversized for my home. If there is no chance to bring the 2312fc back to life, is it possible, to replace the harddisk (6 x 1 TB as RAID 5) in a MSA 2312i iSCSI without data loss? (Financially more attractive than a FC ;-)

Thx and best regards
Jörg

 

MSA 2040 MPIO (along with recent change from linear to virtual disk groups)Open in a New Window

So previously, running vSphere 6, configured with MPIO (each host has 2 controllers to SAN, 1 to controller a, and 1 to controller b), using round robin (of course both links are active, but only 1 serves I/O because of disk group ownership).

Upgraded to vSphere 6.5, and more recently, I migrated from linear to virtual disk groups (deleted linear, created virtual, migrated data back).

Anyways, all is good. However I'm noticing one thing while doing failover tests, not sure if it's the vSphere upgrade, or the change from linar to virtual. I'm thinking it's the switch to virtual, but would like confirmation.

Previously with MPIO, disk group ownership, there is a prefered path, however if the iSCSI network connection went down, the other controller would service I/O, and the datastore would remain functioning (it would fall over to the non-owned controller).

However now, ESXi still reports both paths as active and valid, however if I pull the network cable (or disable a path), the I/O doesn't switch to the other controller.

I'm wondering if by switching to virtual, the entire controller needs to go offline for the other controller to service I/O to the disk group?

Cheers

 

MSA2040 Direct Attached FC - Move 1 Server to other room using single mode fiberOpen in a New Window

Dear,

We are currently running a small dual Server<>SAN VMware system in a single rack.

These are the components:

 

SAN: 1x K2R80A               HP MSA 2040 ES SAN DC SFF Storage

Server: 2x 752689-B21   HP DL380 Gen9 E5-2650v3 Perf WW Svr

Server HBA: 4x QW971A              HP SN1000Q 16Gb 1P FC HBA

SAN => Server cable: 4x AJ835A               HP 2m Multi-mode OM3 LC/LC FC Cable

Transceivers: 1x C8R24A HP MSA 2040 16Gb SW FC SFP 4 Pk

 

Now, we want to move 1 server to another location using a single mode fiber connection, 500 metres away. The current interfaces are setup at 8Gb/s and we want to keep it that way. Is it possible to purchase single mode SFP modules for the MSA2040 and the server? Is it possible to mix single and multimode SFP modules in the MSA2040? Or do we need to install redundant fiber switches to convert from multimode to single mode just for this 1 dual connection?

 

Best Regards,

 

Joris

 

HP 2040 SAN StorageOpen in a New Window

Hi,

I have an HP 2040 Storage with me connected to Cisco nexus 2k. Our network team is facing challenge in pinging the management port on the storage.They confirm that the speed on the mgmt port is set to 100mbps and it should be changed to 1gbps or Auto so that they can communicate with the switch.

I would like to know whethet its possible to modify the speed and duplex type of the management port on the storage usign CLI or GUI. If its possible then please provide the commands or steps to do the same.

 

Thanks,

U.K

 

MSA1040 Radius or Active DirectoryOpen in a New Window

Hi,

I have a MSA2312i and a MSA1040 where I want to authenticate logins via Radius or Active Directory but I'can't find anyting in the User Guides.

Can you please help!

Regards

Marcus

 

DAC Copper Cable J9283B or DAC Copper Cable 487655-B21 What to choose?Open in a New Window

Hi,

We purshaced recently a HP MSA 1040 with two controllers iSCSI 10GbE.

We want to attach it to a CISCO switch SG350XG-2F10 with a direct cable, in the documentation there are two options for us, but we don't know which to choose

HPE X242 10G SFP+ to SFP+ 3m Direct Attach Copper Cable J9283B

or

HP BladeSystem c-Class 10GbE SFP+ to SFP+ 3m Direct Attach Copper Cable 487655-B21

And if someone could explain what is the diffrence between the two cables.

 

Thanks in advance.

Regards

Contact Us

Vivit Worldwide
P.O. Box 18510
Boulder, CO 80308

Email: info@vivit-worldwide.org

Mission

Vivit's mission is to serve
the Hewlett Packard
Enterprise User
Community through
Advocacy, Community,
and Education.