- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- MSA Storage
- >
- P2000 MSA G3 Controller B network degraded (but st...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-26-2019 02:27 AM
03-26-2019 02:27 AM
P2000 MSA G3 Controller B network degraded (but still seems to be working)
Hi all,
I've got an odd issue on an old P2000 G3 MSA storage system. It has 2 controllers both of which are working fine and a number of expansion units (again all working as expected). I noted that it was reporting that controller B's network management port was 'degraded' . Sure enough 'show system' is reporting the system as degraded and I can see a red X against the controller B manangement port. Show FRUS however says alll subcompoents are in OK state, show controllers again is fine, show cache-parameters is OK,... I can also connect to the system over ssh on both controllers. What I can't seem to do is connect to the WEBUI on controller B. I've tried restart MC to see if that helps. No. I've also run ping tests from both controllers.
Controller A can ping its gateway with no issues. It can also ping controller B. Controller B however is reporting it cannot or can only intermittently ping the default gateway and it's partner controller A.
So all a bit odd really. If it was failed I'd expect no access at all, yet I can ssh onto it.
Both controller are running TS230P006 which I am guessing is pretty old however we had not seen any issues until recently.
My next plan is probably to fail everything onto controller A and then re-seat controller B to see if the issue clears. If not I guess the next step is a new controller but given the issues I've had in the past being sent controllers with way newer firmware and then having the controllers refuse to talk to each other that will be a last resort.
If anyone has seen this type of issue before or has any suggestions it would be most welcome.
thanks
Ad.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-26-2019 04:55 AM
03-26-2019 04:55 AM
Re: P2000 MSA G3 Controller B network degraded (but still seems to be working)
Your plan seems fine but you can also try full power cycle of the MSA by plan a downtime for this activity.
If still issue persists then you can try with single controller by keeping other controller in shutdown state and check if everything working fine or not.
Yes firmware too much old so any unpredictable or odd behavior is expected.
Is this MSA not in HPE support? You can try upgrading latest firmware.
UPGRADE NOTE:
If upgrading from an older version of firmware it may require a multiple step process to get to TS252.
If below TS230 then upgrade to TS230P008 first, then TS240P004, and then TS250P003 before upgrading to TS252P005. If the firmware is between the mentioned versions, it is recommended to follow through the steps as well.
Hope this helps!
Regards
Subhajit
I am an HPE employee
If you feel this was helpful please click the KUDOS! thumb below!
***********************************************************************************
I work at HPE
HPE Support Center offers support for your HPE services and products when and how you need it. Get started with HPE Support Center today.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-26-2019 09:59 AM
03-26-2019 09:59 AM
Re: P2000 MSA G3 Controller B network degraded (but still seems to be working)
Hello,
You might try to unplug the network cable from the management port on controller B. Then do a ping to the IP address of the B controller management port just to confirm there is no other device on your network set to the same IP address. Once you confirm there is not a duplicate IP address, reconnect the network cable and test the connection.
Sometime either the network port is not fully connected or the duplicate IP address causes the issue. If that does not correct the problem try switching network cables between the A & B management ports on the controllers just to confirm it is not your network cable or switch ports.
There are lots of fixes for the management ports and management controllers between TS230 and current supported firmware TS252P005. While I understand you have not yet had issues, upgrading to avoid hitting problems already corrected in current firmware should be a consideration worth thinking over. Plus it makes replacing a controller much easier when on current firmware versions!
As mentioned previously there is an upgrade path you will need to follow.
UPGRADE NOTE:
If upgrading from an older version of firmware it may require a multiple step process to get to TS252.
If below TS230 then upgrade to TS230P008 first, then TS240P004, and then TS250P003 before upgrading to TS252P005. If the firmware is between the mentioned versions, it is recommended to follow through the steps as well.
Good luck!
Cheers,
Shawn
I work for HPE