Host assignment in a multi path environment
Example: Host A initiator 1 and Host A initiator 2 assigned to Device-1. Device-1 should have the same LUN ID (LUN 0 for ex.) for both initiators.
Failover
• LUNs getting stuck in transition do not get reported in the NT event log; however, IOs will fail due to the drives being no longer available to the OS.
• Controller not coming up. You can attempt to bring the controller back online by checking the status of the controller using the CLI command “controller info”. If held in reset, do “peer enable”. If the controller is not held in reset do “peer disable” and then “peer enable”.
• Once controller is on line, do a CLI “array failback” or right click the enclosure in the ServeRAID GUI and select “failback storage”. This will move the logical drives assigned to that controller back to their preferred path.
Logical Units
• When LUNs are first mapped to the host the initial scan and device discovery can take an extremely long time and leave the logical drives on the alternate controller
• This issue has been resolved in the next DSM release.
Arrays
Controllers