IBM Storage The online community where IBM Storage users meet, share, discuss, and learn. Join the Community
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.