MSA P2000 Controller error & CLI access

Hi all,
   MY client has a P2000 msa, this morning around 5.30am i received and alert:

There is a problem with a FRU. (FRU type: Controller module A, enclosure: 1, product ID: AJXXXA, SN: CNXXXXXX288, version: F, related event serial number: B2XXX4, related event code: 313) EVENT ID:#B2XXX5 EVENT CODE:314 EVENT SEVERITY:Error EVENT TIME:2015-10-30 05:26:01

From what i can see everything is running via module B and the hardware redundancy has saved our bacon. I now have the problem of access to the device and the best way to get it. The initial notes we had for the web GUI was on X.X.X.67 but we are getting no response from this but that was not unexpected as Module A had failed. when connecting to module B X.X.X.211 i get the HP logo in the browser tab BUT only a grey screen from that point forward.

I have telnet access to the unit via Putty on X.X.X.211 so i can see the devices is responding to something. Now the information online is a little limited, has anyone complete troubleshooting on the MSA before via CLI and if So can you point me in the right direction in relation to the above error.

Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Philip ElderTechnical Architect - HA/Compute/StorageCommented:
Both controller modules have LAN connections and/or serial connections?

EDIT: When hitting CLI are you prompted to enter a UN/Password?
andyalderSaggar maker's framemakerCommented:
Login via putty using serial or telnet, user manage, password !manage.

First I would try a different browser, if that doesn't solve the GUI problem with the working controller you can run "restart MC B". You can also restart MC A although that may not work if it's broken. MC is the management controller and restarting it will not affect I/O.

You can also "restart SC A" and see if controller A works after that (or just reseat it),  SC is storage controller. "Restart SC B" will stop all I/O since it's the running storage controller so don't do that without stopping host access first.

Also in the log file you need  to post a couple of entries before and after the event code:314 since that just means a FRU has failed and there's probably more info just before that event.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
ncomperAuthor Commented:
they were the correct commands, I did find them before you posted back but your answer is correct. Thanks
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.