MSA Storage
1819658 Members
3483 Online
109605 Solutions
New Discussion

Re: HPE msa2050 sas problem with connection

 
spidertech
Occasional Contributor

HPE msa2050 sas problem with connection

Hello,

I have an HPE msa 2050 sas on which I have configured a sas connection with 3 hosts. Connections in the host tab showed up automatically. I connected the machines one by one (first the first port from controller A to the first host, port configuration on the device, then the first port from controller B to the first host, port configuration on the device, and then the next server). Connections look fine (see photo). From these hosts, I created a FOC group on the hpe msa 2050 and mapped the drives to this group. Then I set up a cluster failover on Windows Hyper-V 2019. Cluster passed the verification without errors, disks from the array connected without a problem, migration between machines works fine, but one thing worries me, when I run the get-initiatorport command in powershell on node 1 and node 3, it shows me nothing, while on node 2 it shows me all connections (shown in screenshots). It seems to me that on each server should be visible two connections and not all on one host.

Can someone confirm to me if the configuration on HPE is good or has anyone encountered something like this and is it normal?     

pula.PNGhost map.PNGhost-map.PNGsas-connection.PNGsas.PNG

 

 

2 REPLIES 2
JonPaul
HPE Pro

Re: HPE msa2050 sas problem with connection

@spidertech 
Are the firmware and drivers the same on Node 2 and Node 3?
Also check for other HPE Smart Array software components windows may require the Smart Storage Administrator components to read the HBA correctly.

I work for HPE
HPE Support Center offers support for your HPE services and products when and how you need it. Get started with HPE Support Center today.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]
spidertech
Occasional Contributor

Re: HPE msa2050 sas problem with connection

@JonPaul 

Hi,

The drivers on node 1 and node 2 are the same, while on node 3 they are newer. However, node 1 and node 3 have the same issue, so it's probably not a matter of drivers. As for the smart storage administrator components, I don't have them available for download; they are no longer accessible.