Operation void checkValidSNC (SNCCreateData createData = NA, CIS SequenceOf TPData tpsToModify = empty list, CIS Boolean considerResources = True, CIS Boolean valid = NA), in Class MultiLayerSubnetwork

Documentation
Check whether a valid Subnetwork Connection can be created based on input parameters without actually creating it.
The test should check for the existence of hardware that will support the requested SNC. If the considerResources parameter is false, the check must be independent of the current specific resource usage in the subnetwork (as in createSNC). If the considerResources parameter is true, the check must consider the current specific resource usage in the subnetwork (as in activateSNC); in that case, the rules of the EMS' mode of operation apply to the check (see SNC Management Modes of Operation).
This operation also applies to bundled SNCs.
Operation Exceptions:
1. NOT_IMPLEMENTED - Raised when the EMS does not support this operation; i.e. the EMS may not support this
operation at all or may not support the specified value of considerResources.
2. INTERNAL_ERROR - Raised in case of non-specific EMS internal failure.
3. INVALID_INPUT - Raised if any input parameter is syntactically incorrect, or in case a bundled SNC is requested, the
GTP endpoints of the SNC do not match, i.e., the GTPs do not have the same number of CTPs and in a particular order
with respect to their layerRates or are not of the same layer rate.
4. NE_COMM_LOSS - Raised when communication to managed element is lost and this prevents checking the validity of
the SNC.
5. UNSUPPORTED_ROUTING_CONSTRAINTS - Raised when the EMS does not support the routing constraints specified.
6. USERLABEL_IN_USE - Raised when the userLabel uniqueness constraint is not met.
7. OBJECT_IN_USE - Raised when CC creation for the SNC would involve a TP that has an existing fixed CC that does
not match that required for the SNC.
8. UNABLE_TO_COMPLY - Raised when the EMS is unable to find a route for the SNC.
Raised when the EMS is unable to execute the request because at least one of the parameters although valid could 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.
Raised if the SNC could not be activated because the EMS cannot comply for a reason different from the ones above.
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
None
Postconditions
No change in the system.
Semantics

Arguments

createData
/* in */ The read-create attributes describing the subnetwork to be validated.
tpsToModify
/* in */ A list of TPs and parameters that would be applied to the potential SNC.
considerResources
/* in */ Indicates whether or not the subnetwork's equipment capabilities and the current resource states must be considered for potential activation of the subnetwork connection.
valid
/* out */ True if a valid subnetwork connection can be created as specified with respect to protection level and timeslot and False otherwise.