When prompted put in your credentials (the one you would use to log into the SMU) Just enter the controllers IP and press Open An easy method to do this is to use a piece of software called Putty. Get more information using CLI –Ī good way to gather more information is to telnet or ssh into the working controller’s command line interface (CLI). However, when I tried to log in it would either give an unsuccessful login or state that the controller was ‘initializing’. Overall there wasn’t a lot of information to go off aside from confirmation that a serious error had occurred on Controller A and as a result Controller B had initiated the failover process.Ĭontroller A was still powered on and ping able, plus I could get to it’s SMU. In my case I was getting the error below:Įrror: Critical Error Fault Type: NMI p1: 0x037454E, p2: 0x0000000 ….
Using the SMU you can use the event logs as a first step to identifying the error/problem First step is to log into the SMU (Storage Management Utility) –
I was able to gather information and ultimately bring the controller back up. In my case the faulty controller was brought to my attention by the health ember light on the front of the SAN and using the methods displayed in this article. This post is going to focus more on dual controller setups, with both a Controller A and a Controller B. In this post we are going to look at basic troubleshooting steps a System Administrator can carry out to identify and potentially resolve a faulty storage controller in a HP MSA 2040.
0 kommentar(er)
