Since the array seems to be in a OK status it appears that their DAC cables are working correctly. As stated above, check the host port status. With the customer NOT booting from iSCSI, I would recommend using the Windows software iSCSI initiator. Start simple :-) have they logged the iSCSI adapter into the array? Other protocols (FC and SAS) just automatically log into devices but iSCSI will only connect to the devices you specify. The MSA engineering manager also added this: If those cables are not within specs the array may not be able to discover the cable. The other item I would check is to make sure they have supported DAC cables. This will clear all the configuration information that may be causing the problem but does not help the customer configure the system like the Configuration Wizard would. A more drastic approach would be to do a restore defaults factory. To get to the Configuration Wizard they should be in the Home Topic select Action and then select Configuration Wizard. The last step of the Wizard will configure their host port settings. If the customer starts at the beginning of the Wizard they can perform or verify each step to validate their current configuration. If they do suspect there is residual configuration blocking the access they may want to walk through the Configuration Wizard. It is pretty hard to tell from that photo exactly what is occurring. Access to the LUN and it's data should be available throughout.Īsked my experts and got this back from one of my MSA support experts: Then restart (wait 5 minutes for things to settle) then shutdown the other storage controller. Once they have the MPIO and see multiple paths they should test the configuration by shutting down one of the array storage controllers and should see changes in the MPIO Paths but should still have access to the LUNs. You can see that with the one device with 2 paths I only see one disk (Not Initialized) in disk managerĭang, I just noticed that my black down arrow got changed to yellow. This indicates use all optimized paths until they are gone then use the unoptimized The owning controller (each controller owns disk-groups/Pools with the other controller being a non-preferred option) being optimized and the non-owning controller unoptimized.ĭown (Yellow) Arrow: The MPIO Policy, this should automatically set to "Round-Robin w/ Subset ". Right Arrow: the 2 paths to the LUN, note the Path State one if Active/Optimized the other Active/Unoptimized this indicates that the device is seen (Active) on both controllers. Open properties of the MSA multipath device 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. 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.Ģ. 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 Comments
Leave a Reply. |