The SR3_CAGE_SERVO node was found in the state, SR3_CAGE_SERVO_RUNNING this morning. The nominal state for this node is CAGE_SERVO_OFF, and it was changed on Oct. 23. Cecking in with Jeff and Sheila, this was left on accidentally and we will need to revert it on a lock loss.
Please being this back to CAGE_SERVO_OFF on next lock loss.
To be a bit more clear, in this SR3_CAGE_SERVO running state, the node is continually servoing H1:SUS-SR3_M1_DITHER_P_OFFSET.