UNSOLVED

SergP

updated

10 years ago

S

SergP

2 Posts

0

2951

July 26th, 2016 05:00

VNX5500: What is the meaning of a CLARiiON call-home event number 0x71518010 Host SPA Storage Array **** SP N/A SoftwareRev 7.33.2 (0.51) BaseRev 05.32.000.5.215 Description Internal state violation error.

File: D:/Views/c4a4996c998afad9199c85441aaf3632.stg/catmerge/mgmt/NDU/NDULib/ToC.cpp Line: 2045 Details: Found 0 active UtilityPartition packages  71 51 80 10 .

  • kelleg

    6 Operator

    •

    4537 Posts

    1283

    0

    Posted August 2nd, 2016 09:00

    That error code 0x71518010 occurs during an NDU and is alerting you to an issue. Below is the description of the error code.

    "The NDU software detected an internal state violation."

    Generally this would cause the NDU to fail. I would recommend opening a service request with EMC to determine what the issue was.

    glen

  • rbrigden

    8 Posts

    1283

    0

    Posted December 14th, 2016 15:00

    Hi SergP,

    I have had these error conditions (several times) on my VNX(1) 5300 and followed them through with EMC support, They seem to follow a disk replacement and transition.

    There is a Restricted View article that EMC will eventually point you to:

    Knowledge Base Article 000451405

    Cause:

    "An NDU package that has the [TRANSIENT] flag set to [TRUE] in its associated [ToC.txt] file will be installed on both SP's and then disappears [ie removed and associated directory deleted] after the NDU completes. In this case both SP's still have a directory so the package was not completely removed.

    Since the exists and was not removed, if any software (ie CIMOM in this case) makes a call to the ToC::Discover() method it returns a list of the packages. While going through each package it checks the associated TOC.txt for each one, and reports the results. The above message means "I checked this package and found that it is not active and not prior" which makes sense considering that this package is supposed to be a transient package [not present] but it is. For all purposes this is a benign message and will go away the next time the SP rebooted"

    There appear to be three options to rectify this condition:

    Option 1: Ignore it.

    Option 2: Restart the K10Governor on each SP one-at-a-time and if this does not correct the issue then reboot each SP.

    Option 3: Reboot each SP, which will cause the transient package to be removed.

    I hope this helps.

    regards

    Rob