Up Arrow: The multipath device shown in device manager This requires a reboot to fully be operational but you may see changes in Device Manager before rebooting. I can have 2 LUNs from one MSA 1040 or I can have Two LUN #1 from different MSA 1040s and they will be kept separately.
Msa device discovery tool for windows full#
So I suggested using "MSA 1040" this will actually pull products "MSA 1040*" into MPIO, you will still see the full product string in device manager and each product and LUN will be unique i.e. It does a compare from the beginning and will allow anything after. Up Arrow: this is purely to let you know that the vendor string (HP) must be 8 characters "HP " and the product can be up to 16 characters. Left Arrow: this is the device hardware ID for the MSA 2040 for the MSA 1040 use "HP MSA 1040" (six spaces) You can see the "add session" button and specifically choose the Initiator IP and Target IPs. I don't think the customer has a second session to the MSA 1040 target which means they only have a single path (not good). Note: You can create multiple sessions using the same initiator and target IPs which is not helpful The identifiers are not helpful but you can dig in other areas to see that these are actually 2 independent paths. one is connected to the A controller IP the other to the B controller IP. Left Arrow: there are 2 sessions (logins) to the array. Right Arrow: click the properties of the discovered target Up Arrow: It's connected to the 1 target IQN - 1 IQN for all MSA target ports
There are a lot of things in this screenshot. (Emphasis added by me)Īttached is a screenshot of a system I have connected to an MSA 2040. This is serious as any controller shutdown could cause a data outage. The MSA 1040 is still not incorporated into MPIO and they only have a single PATH They have 2 different LUNs presented to the host from the onboard Smart Array which is why they are seeing Two "HP LOGICAL VOLUME" multipath devices.Ģ.
Msa device discovery tool for windows driver#
The Smart Array Controller will not present multiple paths so this is minor, they are just running through another driver (MPIO) when talking to this device. The LOGICAL VOLUME should not be included in MPIO I think the customer is still missing on a couple of points.ġ. Here is what I heard back from my MSA program manager. There are major issues with the configuration.
0 kommentar(er)
