- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- HPE 3PAR StoreServ Storage
- >
- 3par Cage0 Degraded
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
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
04-12-2019 03:12 AM
04-12-2019 03:12 AM
3par Cage0 Degraded
Hello Guys,
After upgrading the 3par enclosures and adding two new ones (2nodes and 8 eclosures currently), Cage 0 is going to degraded state after the activity.
Everything is working smoothly, and there is no impact on the services, however the Cage0 is not showing any error from CLI but from the Management Consle GUI, it is giving degraded.
See below the cli output:
HP-3PAR cli% showcage -d cage0
Id Name LoopA Pos.A LoopB Pos.B Drives Temp RevA RevB Model FormFactor
0 cage0 1:0:1 0 --- 0 24 25-27 - 4078 DCN1 SFF
-----------Cage detail info for cage0 ---------
Position: ---
Interface Board Info Card0 Card1
Firmware_status - Current
Product_Rev - 4078
State(self,partner) -,- OK,OK
VendorId,ProductId -,- HP,DCN1
Master_CPU - No
SAS_Addr - 50050CC10230567E
Link_Speed(DP1,Internal) -,- 6.0Gbps,6.0Gbps
Locate - Off
PS PSState ACState DCState Fan State Fan0_Speed Fan1_Speed Locate
ps0 OK OK OK OK Low Low Not Available
ps1 OK OK OK OK Low Low Not Available
-------------Drive Info-------------- --PortA-- --PortB--
Drive DeviceName State Temp(C) LoopState LoopState
0:0 5000c500769f9254 Normal 25 OK -
1:0 5000c500769f6dfc Normal 25 OK -
2:0 5000c500765899f4 Normal 25 OK -
3:0 5000c500769f8ec8 Normal 25 OK -
4:0 5000c5007657e360 Normal 25 OK -
5:0 5000c500765dafac Normal 25 OK -
6:0 5000c50076ad614c Normal 25 OK -
7:0 5000c500769fd1b4 Normal 26 OK -
8:0 5000c5007657e0d8 Normal 26 OK -
9:0 5000c5007657e678 Normal 26 OK -
10:0 5000c500769f6948 Normal 27 OK -
11:0 5000c500769ff44c Normal 27 OK -
12:0 5000c50076a8c868 Normal 26 OK -
13:0 5000c50076a00dd0 Normal 26 OK -
14:0 5000c50076a7bc04 Normal 26 OK -
15:0 5000c50076a7b7e8 Normal 26 OK -
16:0 5000c50076a7b7cc Normal 25 OK -
17:0 5000c500769fc6bc Normal 25 OK -
18:0 5000c50076a7b1fc Normal 25 OK -
19:0 5000c500769f9d8c Normal 26 OK -
20:0 5000c500769fbd64 Normal 26 OK -
21:0 5000c500769ffc48 Normal 25 OK -
22:0 5000c50076a0018c Normal 25 OK -
23:0 5000c500769f6a90 Normal 26 OK -
HP-3PAR cli%
Hasanyone faced this before? Can a reboot fix the problem?
and if the reboot can fix the problem, does it affect the data or the other nodes?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-16-2019 06:35 AM
04-16-2019 06:35 AM
Re: 3par Cage0 Degraded
Hello Lelie,
It seems one of the IFCs is missing. If we look at the showcage output, cage 0 not reporting the Card 0 information. Also all PDs reporting only one path (LoopState).
I am an HPE Employee.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]