Primary Storage

 View Only
Expand all | Collapse all

V3700 cluster failure(2 node of system is service state with error)

  • 1.  V3700 cluster failure(2 node of system is service state with error)

    Posted Wed March 30, 2022 09:09 AM
    Hello,
         I have issue about V3700, It have the problem 2 node is service state all. Can fixed by Recover ?
    I need step for fixed this issue, Thank you very much.

    ------------------------------
    Apidesh D.
    Technical HW Systems

    ------------------------------


  • 2.  RE: V3700 cluster failure(2 node of system is service state with error)

    Posted Thu March 31, 2022 02:41 AM
    Edited by Istvan Buda Thu March 31, 2022 02:45 AM
    Hello,

    You need to login to either the service gui or the cli.
    Service gui can be accessed through the service ip address or the cluster address plus "/service" like  "10.10.10.10/service".

    https://www.ibm.com/docs/en/v3700/7.8.1?topic=interface-accessing-service-assistant

    Then check the error code, and solve the problem.
    https://www.ibm.com/docs/en/v3700/7.8.1?topic=codes-error

    Then you need to select either nodecanister, then select "stopservice" or "exit service state" then click "Go" button.

    At CLI use "stopservice" command.
    https://www.ibm.com/docs/en/v3700/7.8.1?topic=commands-stopservice

    You can share any error code to be able to suggest more specific.

    Good Luck.


    ------------------------------
    Istvan Buda
    ------------------------------



  • 3.  RE: V3700 cluster failure(2 node of system is service state with error)

    User Group Leader
    Posted Fri April 01, 2022 05:33 AM

    Just to clarify on this:

    Nodes in service are there for one of 3 reasons:

    1: The Node has been put into service state automatically via a remove node operation (rmnodecanister or similar)

    2: the Node has been manually put in to service by the user as part of a service operation (using the satask startservice command line or GUI equivalent).

    3: The node has an error which prevents it from being able to run IO.

    Of these three, the first two can be cleared with a stopservice operation, as that is mean to clear node error 690 (node is in service due to rmnode or startsevice).

    If this node has an error that is causing it to be in service, you need to first clear the condition that is causing the error.  If you clear this condition, the node will automatically start up without the need to stopservice.

    Hardware errors may require replacement parts, but there are a few "software is broken" errors that result from the image on disk being corrupted or a repeating software condition causing system instability (node error 564).  Please follow the directed support procedure for the node error identified by the service node, which will likely involve contacting support.



    ------------------------------
    Evelyn Perez
    ------------------------------