The operation is used to activate the input route and deactivate the current (or partial) route(s), if different from input route. 
The operation does not affect the administrativeState of any route. The restoration process may re-route again, e.g. in case of failures.

In case of failure:
No exception thrown, except in the cases listed below. If the SNC or any of its network resources have changed as a result of this operation, then no exception can be thrown so that the sncState can be passed back to the NMS. The resulting sncState will be either PARTIAL or ACTIVE.
The sncState will be PARTIAL if not all cross-connects (of given input route) on MEs have been successfully set up, and there is not an active route. Moreover one or more of the cross-connects to be removed may be still be active, this leads to two (or more) routes in PARTIAL state.
The sncState will be ACTIVE if all cross-connects (of given input route) on MEs have been successfully set up, but one or more of the cross-connects (of any of the other partial routes) to be removed are still active, this leads to one route in ACTIVE state and another (or more) route in PARTIAL state. The errorReason parameter is set accordingly.

Recovery scenarios: this operation can be performed again addressing
- an already active route, in order to retry the deactivation of other route(s) in partial state
- a partial route, in order to retry its activation (and retry, if needed, the deactivation of other partial routes as well).

The EMS will apply the transmission parameters specified in the tpsToModify parameter (same behaviour as setTPData). They may be applied before or after the creation of the CCs, as appropriate. Existing TP transmission parameters for which no changes were requested in tpsToModify will be left unchanged. However, the alarm reporting on the CTPs and the containing TPs may be turned on by the EMS as part of this request, unless otherwise specified via the transmission parameter "AlarmReporting". A similar behaviour is also allowed for the serviceState parameter, which may be set to IN_SERVICE for the CTPs and the containing TPs. See TransmissionParameters object.
If a given entry in the list of transmission parameters specified in the TPData_T can not be successfully applied to the TP, for any reason, then the errorReason field is appended with an appropriate reason text. Applying transmission parameters is best-effort and the resulting values of the transmission parameters are provided in the updated tpsToModify parameter.

An already active SNC route can be activated again; the EMS is allowed to not send the commands to the ME a second time for the cross connect establishment however the commands may be sent for the transmission parameters.

Note: The relationship between Bundled SNC service and the SNC with Multiple Routes feature requires further study and is not applicable for v3.0.

Operation Exceptions:
1. NOT_IMPLEMENTED - Raised when the EMS does not support this operation.
2. INTERNAL_ERROR - Raised in case of non-specific EMS internal failure.
3. INVALID_INPUT - Raised when any input parameter (e.g. tpsToModify) is syntactically incorrect.
4. OBJECT_IN_USE - Raised when the route can not be activated because of CC or CTP conflicts with an
    active route of another SNC (with equal or higher priority).
5. ENTITY_NOT_FOUND - Raised when routeId or tpsToModify reference a route/TP object that does not exist.
6. NE_COMM_LOSS - Raised when communication to managed element is lost and this prevents any change to
    the SNC.
7. NOT_IN_VALID_STATE - Raised where the SNC would involve a CTP that is not connectable due to the state of
    the server TP or in the case of inverse multiplexing where the SNC would involve a CTP that is not connectable
    due to the state of the client TP.
8. UNABLE_TO_COMPLY - Raised when the EMS can not meet the tolerableImpact requested by the NMS.
    Raised when the EMS is unable to execute the request because at least one of the parameters although valid can not
    be set and that parameter is identified as "not best effort" in the supporting document LayeredParameters.pdf
    associated to the TransmissionParameters object or in the additionalInfo attribute; i.e. the whole operation will be
    rejected if one parameter fails that must be set. This is potentially usable for cases where a parameter must be set for
    the SNC to be valid.
    Raised if the route cannot be activated because the EMS cannot comply for a reason different than the ones above.
    If the EMS cannot determine the reason it could not comply, it is also allowed to throw UNABLE_TO_COMPLY.
