HP MSA 2050 \ DL380 Gen10 \ Windows 2019 Hyper V Host iSCSI errors

[imhofc]

Hello

We have a MSA 2050 with 1 pool. Connected via 10GB fiber to a DL380 Gen 10 Server (2 Xeon Processors & 128GB RAM). Direct connection (no switch) Controller A1 and Controller B1 ports are connected via fiber to the back of the DL380 10GB Network Card.

This worked for a couple years. We had a data incident and I had to rebuild the Server and MSA with all new drives. Everything is setup now.

I am using iSCSI to connect the Windows 2019 DC Edition. We use this as a Hyper V Host only. The Guests are using the mapped iSCSI drive as the location of the VHDX file.

The Guests are extremly slow to respond at times. In event viewer of the Hosts I see iSCSI error messages. Guests have 4 vCPU and 16GB RAM. Just OS installed on guests. No apps yet.

Event ID 129 

The description for Event ID 129 from source iScsiPrt cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

\Device\RaidPort1

Event ID 39

Initiator sent a task management command to reset the target. The target name is given in the dump data.

Event ID 9

Target did not respond in time for a SCSI request. The CDB is given in the dump data.

Im affraid maybe I missed a setting from a few years ago because this setup worked great before i had to replace all the drives and setup everythging again.

Thanks

[support_s]

System recommended content:

1. HPE MSA Firmware Release Notes for MSA 1050 (VE270P002-02) and MSA 2050/2052 (VL270P002-02)

2. HPE MSA Firmware Release Notes for MSA 1050 (VE270P004) and MSA 2050/2052 (VL270P004)

Please click on "Thumbs Up/Kudo" icon to give a "Kudo".

Thank you for being a HPE valuable community member.

[ArunKKR]

Hi,

From MSA end there are not many settings you could change.

Ensure that jumbo frames is enabled or disabled end to end.
The jumbo frames setting should be identical in both host server and MSA.
You could try to shut down the storage controller A so that Pool ownership changes to controller B and check whether same errors are being reported.
This step will help you rule out any SFP or FC cable issues in controller A path.
Network card drivers/firmware could be updated to the latest version using SPP disk.
Configure MPIO if not done already.
Update MSA controller firmware as well to the latest version VL270P008.
The steps in below guide should be common even for Windows 2019:

https://www.hpe.com/psnow/doc/a00038738en_us

[ArunKKR]

Hi,  Apart from changes in network card settings after operating system reimage, I cant think of any reason why this could happen.

[support_s]

Hello,

Let us know if you were able to resolve the issue.

If you have no further query, and you are satisfied with the answer then kindly mark the topic as Solved so that it is helpful for all community members.

Please click on "Thumbs Up/Kudo" icon to give a "Kudo".

Thank you for being a HPE valuable community member.