VMAX engunity

[Srinivas Adusumalli]

Hello All,

 

Hope every one is doing good !! Recently I encountered a Funny issue with VMAX enguinity when I was trying to expand thin striped meta. :-)

 

 

Primus note :

 

Support told me this is a known code bug. Fix is in 5875.269.201 (with epack 5875_269/0031 / 5875_201/5011)

 

 

Subject: ETA emc291729: Symmetrix VMAX and VMAXe: Minimum required Enginuity levels to support online Meta Volume expansion or converting Concatenated to Striped Meta Volume at Enginuity 5875

 

The following is a Primus(R) eServer solution:

ID: emc291729
Domain: EMC1
Solution Class: 3.X Compatibility

Goal       ETA emc291729: Symmetrix VMAX and VMAXe: Minimum required Enginuity levels to support online Meta Volume expansion or converting Concatenated to Striped Meta Volume at Enginuity 5875

Fact       EMC Technical Advisory (ETA)

Fact       Product: Symmetrix VMAX Series

Fact       Product: Symmetrix VMAXe

Fact       Enginuity: 5875

Fact       Configuration: Meta Volume

Fact       Configuration: Striped Meta Volume

Fact       Device Emulation: Fixed Block Architecture (FBA)

Fact       Feature: Meta LUN Expansion

Symptom    Error code: XX12 occurring on SAF

Symptom    Error code: AB3E occurring on SAF

Symptom    Error code: xx10

Change     Online Meta expansion.

Change     Expanding an existing Striped Meta Volume.

Change     Meta change from Concatenated to Striped.

Change     Converting a Meta Volume from Concatenated to Striped.

Cause      Enginuity issue:  To guarantee safe and proper Meta expansion operation at Enginuity 5875, Symmetrix VMAX and VMAXe systems must upgrade to the recommended  Enginuity Pack/Registered Build described in this EMC Technical Advisory (ETA).  EMC is proactively releasing this Enginuity Pack/Registered Build to address several Enginuity issues that might negatively impact such operation. 

Fix        An Enginuity Pack/Registered Build is available for this issue at 5875.231.172 and 5875.249.188. If performing a Meta expansion in your environment is required or you believe you may have encountered this issue, contact the EMC Customer Support Center or your local EMC service representative to determine if an Enginuity upgrade is appropriate for your environment and quote this solution ID.

 

 

Error message

03/01/2013 09:08:47.737    724   5380 EMC:SMC                   iSymConfigChangeCont iSymConfigChangeControl: session_id = 1

03/01/2013 09:08:47.768    724   5380     {

03/01/2013 09:08:47.768    724   5380       add dev 2060:2069 to meta 1D32, protect_data=TRUE, bcv_meta_head=2057;

03/01/2013 09:08:47.768    724   5380     }

03/01/2013 09:08:47.784    724   5380 EMC:SMC                   iSymConfigChangeCont iSymConfigChangeControl: session_id = 1

03/01/2013 09:08:47.924    724   5380     Committing configuration changes..........................Started.

03/01/2013 09:08:50.096    724   5380     Committing configuration changes..........................Queued.

03/01/2013 09:09:15.549    724   5380     SID 000192603682:     Script handling returned sts code 0xc05: Message 0x00000C05.0xA1B2:

Script Aborted due to Regulator limitations!

Please call EMC Customer Support Center.

03/01/2013 09:09:15.549    724   5380     SID 000192603682: API msg : This feature is temporarily disabled at your Enginuity code level. Please examine the SYMAPI log file for details

03/01/2013 09:09:22.033    724   5380     SID 000192603682:     Script handling returned sts code 0xc05: Message 0x00000C05.0xA1B2:

Script Aborted due to Regulator limitations!

Please call EMC Customer Support Center.

03/01/2013 09:09:22.033    724   5380     SID 000192603682: API msg : This feature is temporarily disabled at your Enginuity code level. Please examine the SYMAPI log file for details

03/01/2013 09:09:22.033    724   5380     COMMIT requesting required resources......................Failed.

03/01/2013 09:09:22.064    724   5380 EMC:SMC                   iSymConfigChangeCont iSymConfigChangeControl: session_id = 1

03/01/2013 09:09:22.424    724   5380     Closing configuration change request......................Closed.

03/01/2013 09:09:23.658    724   5380     Terminating session with configuration server.............Done.

 

EMC chat response for this error message.

 

1:33:24 AM	Rahul1 K.: That should not matter I believe, the error you are getting is due to some patch as far as I remember...still researching
11:34:27 AM	sri...@cdw.com: k ..
11:35:53 AM	sri...@cdw.com: if that is case How can I check whether it has been done or not ?
11:38:19 AM	Rahul1 K.: When a script aborts due to Regulator limitations, this means that the planned change is being blocked by the Regulator feature.The Regulator is a safeguard that allows EMC to inhibit scripts which may cause a Data Unavailable or Data Loss (DUDL) event. In each case a workaround or an Enginuity fix needs to be applied before the script can be run