Restart

1. SDP Leaf Node provides API for Restart workflow.

2. The SDP Leaf Node accepts the command if :-

   1. Operational state of the SDP Leaf node is ON/OFF/INIT/STANDBY/ALARM

3. The SDP Leaf Node rejects the command if :-

   1. Operational state of SDP Leaf node is FAULT/UNKNOWN .

4. The following state requirements are applied for the command execution :-

   1. SDP Subarray is in any of the ‘observation state’ - FAULT,ABORTED,RESOURCING,CONFIGURING,IDLE,READY,SCANNING

   2. SDP Subarray node is available .

5. The command execution involves below key operations :-

   1. Check for SDP Subarray obsState is done.

      • If it is in any of the RESOURCING/IDLE/CONFIGURING/SCANNING/READY obsState :-

        1. Abort command is sent to SDP Subarray.

        2. Once Abort command transitions SDP Subarray to ABORTED obsState , Restart command is sent to SDP Subarray.

      • If it is FAULT/ABORTED , Restart command is sent to SDP Subarray.

   1. When Restart is invoked on the SDP Subarray.

      • If SDP Subarray reports rejection/failure, command failure is reported as ‘RESULT_CODE - FAILED’ on Long Running Command Result attribute of the SDP leaf node.

      • If SDP Subarray accept command , the TMC SDP leaf node will wait for command completion.

6. The SDP leaf node monitors the progress of command via the SDP sub-array node ObsState transitions and the long running command results.

   1. Command is successful when the SDP Subarray Node transitions to EMPTY ObsState. This is reported as ‘RESULT_CODE - OK’ on Long Running Command Result attribute of the Subarray node.

   2. Command failure is reported in any of the below cases as ‘RESULT_CODE - FAILED’ on Long Running Command Result attribute of the TMC SDP Subarray leaf node.

      • The SDP Subarray reports error event when command is invoked .

      • The command times out if SDP SubarrayNode does not transition to EMPTY within the timeout period specified by CommandTimeOutDefault property specified in helm chart of the SDP Leaf Node .