3PAR7200 LD degraded Currently: mag as Created: cage

[CRD]

Good day

Need some advice. I want to do firmware upgrades on 3PAR7200 array but when I run the readyness check it gives the below output. I want to know if I will run into any problems if I contnue with the firmware upgrade?

Has anybody else had this issue before?

Logical Disk tp-1-sd-3.0 is degraded Currently: mag as Created: cage
Logical Disk tp-1-sd-3.1 is degraded Currently: mag as Created: cage
Logical Disk tp-1-sd-3.15 is degraded Currently: mag as Created: cage
Logical Disk tp-1-sd-3.16 is degraded Currently: mag as Created: cage

current OS version: 322 MU4 + patches

I want to install the last patches for 322 MU4 and then I want to upgrade to 322 MU6 + patches.

Any advise will be much appreciated.

[Josh94K]

Hello @CRD 
Hope you are doing well!

Prerequisites for updating Procedure

•Determine the current 3PAR OS version, hardware type, and final, fully supported update 3PAR OS for each 3PARStoreServ Storage system participating in the RC pair relationship.

•Verify each storage system is in a healthy state.

•As a best practice, ensure all connected hosts are dual-path

•Determine the website to obtain the required 3PAR OS versions. See HPE 3PAR OS update Overview

.•Review the release notes for each required 3PAR OS version and apply the recommended patches.

Additional information
for additional info please refer: https://support.hpe.com/hpesc/public/docDisplay?cc=us&docId=emr_na-c02660486&lang=en-us


It would be best to resolve all hardware issues before proceeding with the upgrade. 

@CRD  I hope this helps! 
If you feel this was helpful, Please HIT that KUDOS!  thumb below!

Note: "While I am an HPE Employee, all of my comments (whether noted or not), are my own and are not any official representation of the company."

[sbhat09 · Accepted solution]

Hello @CRD,

This is not a critical error to cause problems with firmware upgrade.
The error is due to - The LD was created as per 'ha cage' norms. But now the LDs are as per 'ha mag' level of availability.

If you want to fix this before OS upgrade:

1. You can try 'compactcpg' for the CPG to which those LDs belong. (I am not 100% sure it will fix the issue. But certainly will NOT cause any issues. As compactcpg will re-arrange the LDs, hoping this may help to resolve the issue as well)

2. If possible, you can consider moving the VVs from the current CPG (in which the LDs are degraded) to a new CPG. Or even create a new CPG (with same dev type, set size and ha type) and move the VVs to there. You may require '3PAR Dynamic Optimization' or 'Unified' license for this.

Please let me know if you need further assistance on this.

Regards,
Srinivas Bhat

If you feel this was helpful please click the KUDOS! thumb below!

[CRD]

Thanks sbhat09 for the feedback its much appreciated.

How to I check to which VV's these degraded LD's belong too? I have tried to check but could not pin point the VV's.

Do you perhaps know?

Dynamic optimization is enabled on this array.

[CRD]

Oh yes and point 1 you mentioned I have already done

[sbhat09]

You can check it with the command showldmap <LD_name>

Regards,
Srinivas Bhat

If you feel this was helpful please click the KUDOS! thumb below!

[sbhat09]

Oh Great! Could that help to fix the issue?

Regards,
Srinivas Bhat

If you feel this was helpful please click the KUDOS! thumb below!

[CRD]

Thank you 

Ill check which VV's they belong too and then follow your advice and see what happens.

Point nr 1 did not help but lets see point nr 2.

Ill provide feedback afterwards

Will work on this tomorrow