Then we create the mapping to the second serverAll looks fine on the blades, this way - until a volume is created in Disk Management - exactly like you do - no drive letter, mpio correctly configured.Unfortunately, this never survives a reboot - sometimes not even that long.
The BSOD cycle starts with BAD_POOL_HEADER & "Unable to write to read only memory" (issues). Add MPIO feature through Server Manager and reboot4.Remove the explicit mapping ticks in the SMU, and eventually the server will startReally gets frustrating - the HP 2nd Line Techs and their HP MS Specialists are trawling through HPS reports & Kernel Dumps now - this has dragged on for months with no success. After reboot run this command from an elevated command prompt "mpclaim -n -i -a" then reboot again (This grabs both paths and combines them into one redundant path)5.
Now after the second reboot check Disk Management again and you will notice that only6. HP-MSA P2000-Controller-CPU-SSH.Bring disk online and initialise and create volume (Obviously only do this once on Host1 if its a clustered setup)Sorry about the delay - was jumping through HP hoops on Thursday & Friday. Collects statistics on the activity of a controller (CPU), and raises alerts when thresholds are crossed. Configuration: ssh user account and password, ssh port, thresholds expressed in MB/s. Do not use passwords with accented characters or interpretable under Linux. Available from version 4.14.How can the flexibility of the HP P2000 G3 MSA Array Systems help remedy large storage needs and small budgets By offering high-performance 8 Gb FC, Combo.Hi Guys I found the answer myself, hope this helps others!StorageWorks.
0 kommentar(er)
