tmf854.v1 > SNCState_T LOCATION: file:/xsd/networkResources/SubnetworkConnection.xsd
SECTIONS: Basic | XML | Reference Overview | TOC | No TOC | Help
tmf854.v1
The SNCState_T Simple Type
The SNCState enum is used to represent the various states that an SNC may take. The following states may be supported by the EMS, depending on the SNC management mode of operation used by the EMS. See SNC Management Modes Of Operation for details. SNCS_PENDING: the SNC has been created by an NMS and has not been activated by any NMS; or the SNC has been successfully deactivated by an NMS. That state has no relationship with the network state of the cross- connects of the SNC. It is allowable for an EMS to not support the SNCS_PENDING state and to reject any operation that attempts to put an SNC into SNCS_PENDING state. SNCS_ACTIVE: the SNC is not in pending state, a route has been assigned to the SNC and all cross-connects for the SNC are active in the network. SNCS_PARTIAL: the SNC is not in pending state, and either a route has not been assigned to the SNC, or not all of the cross-connects of the SNC are active in the network. This may or may not include activated SNCs for which there are currently no active cross- connects in the network, depending on the SNC management mode of operation.It is possible that, in some EMSes, this state be unreachable. SNCS_NONEXISTENT: this is not an SNC state per se, as it applies to "non-existent SNCs". It is used in the interface to report SNCs that have been deleted. See SNCState state diagram for details on valid transitions.
Simple Type SNCState_T
SNCState_T is derived from string type. There are several restrictions on the value. The schema processor preserves value's whitespace. Enumeration values are (SNCS_NONEXISTENT | SNCS_PENDING | SNCS_ACTIVE | SNCS_PARTIAL).

Enumeration | Description
SNCS_NONEXISTENT |
SNCS_PENDING |
SNCS_ACTIVE |
SNCS_PARTIAL |

XML
-<xsd:simpleType name="SNCState_T"> -<xsd:annotation> <xsd:documentation> The SNCState enum is used to represent the various states that an SNC may take. The following states may be supported by the EMS, depending on the SNC management mode of operation used by the EMS. See SNC Management Modes Of Operation for details. SNCS_PENDING: the SNC has been created by an NMS and has not been activated by any NMS; or the SNC has been successfully deactivated by an NMS. That state has no relationship with the network state of the cross- connects of the SNC. It is allowable for an EMS to not support the SNCS_PENDING state and to reject any operation that attempts to put an SNC into SNCS_PENDING state. SNCS_ACTIVE: the SNC is not in pending state, a route has been assigned to the SNC and all cross-connects for the SNC are active in the network. SNCS_PARTIAL: the SNC is not in pending state, and either a route has not been assigned to the SNC, or not all of the cross-connects of the SNC are active in the network. This may or may not include activated SNCs for which there are currently no active cross- connects in the network, depending on the SNC management mode of operation.It is possible that, in some EMSes, this state be unreachable. SNCS_NONEXISTENT: this is not an SNC state per se, as it applies to "non-existent SNCs". It is used in the interface to report SNCs that have been deleted. See SNCState state diagram for details on valid transitions. </xsd:documentation> </xsd:annotation> -<xsd:restriction base="xsd:string"> <xsd:enumeration value="SNCS_NONEXISTENT" /> <xsd:enumeration value="SNCS_PENDING" /> <xsd:enumeration value="SNCS_ACTIVE" /> <xsd:enumeration value="SNCS_PARTIAL" /> </xsd:restriction> </xsd:simpleType>

﻿

Uses
Type (1) string

Used-By
Element (1) SubnetworkConnection_T/sncState

Generated by WSDLdoc ©