Operation void setIntendedRoute (Name routeId = NA, CIS SequenceOf Structs::AVP additionalInfo = empty list), in Class SubnetworkConnection

Documentation
The operation allows an NMS to request to set the addressed route as intended route. The formerly intended route (if different from addressed) is no longer the intended one, in order to respect the rule that an SNC must have one intended route, and only one. The addressed route can be in any administrative / actual state.
Note: The relationship between Bundled SNC service and the SNC with Multiple Routes feature requires further study and is not applicable for v3.0.
In case of failure:
The errorReason field of the exception will contain the reason for the failure.
Operation Exceptions:
1. NOT_IMPLEMENTED - Raised when an 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 is syntactically incorrect.
4. ENTITY_NOT_FOUND - Raised when routeId reference an object that does not exist.
5. UNABLE_TO_COMPLY - 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 additionalInfo.
If the EMS cannot determine the reason it could not comply, it is also allowed to throw UNABLE_TO_COMPLY.

Protocol |  | Qualification |
Exceptions |  | Size |
Time |  | Concurrency | Sequential
Export Control | PublicAccess |  |

Preconditions
The addressed route has to exist.
Postconditions
The addressed route is the intended one, and the formerly intended route is a backup one.
Semantics

Arguments

routeId
/* in */ The identifier of the route.
additionalInfo
/* inout */ Allows the communication of additional information which is not explicitly modelled.