Cisco Cisco Prime Optical 10.3 Technical References
TM FORUM Implementation Statement (IS) Template and Guidelines
2.33.4 SNC Type Transitions Related to the ModifySNC Operation
The following table indicates the EMS support of SNC Type transitions that can be invoked through the
modifySNC() operation. Although the EMS can provide support for transitions among all SNC Types, the MTNM
interface only defines the transitions between ST_SIMPLE and ST_ADD_DROP_A or ST_ADD_DROP_Z to be
mandatory, when modifySNC() is supported. Note that ST_ADD_DROP_Z bi-directional is new for Phase 3.
modifySNC() operation. Although the EMS can provide support for transitions among all SNC Types, the MTNM
interface only defines the transitions between ST_SIMPLE and ST_ADD_DROP_A or ST_ADD_DROP_Z to be
mandatory, when modifySNC() is supported. Note that ST_ADD_DROP_Z bi-directional is new for Phase 3.
1. Indicate the supported transitions by placing the word “supported” in the appropriate cells (this should, at
least, include the mandatory transitions). The other cells should be blank.
The modification of the SNC’s Static Protection Level does not impact the SNC type. The EMS may support the
modification of an unprotected SNC to being a partially, fully or highly protected SNC while maintaining the same
SNC type.
modification of an unprotected SNC to being a partially, fully or highly protected SNC while maintaining the same
SNC type.
In order to complete the following table, the EMS supplier should do the following:
2. For each supported transition, indicate the GOI.
3. For ST_EXPLICIT to ST_EXPLICIT or other SNC type to/from ST_EXPLICIT, the GOI needs to be
described for different ST_EXPLCIT traffic flows (e.g. for ST_EXPLICIT to ST_SIMPLE the SNC
modification is supported as Hitless whenever only inactive protection legs are removed).
modification is supported as Hitless whenever only inactive protection legs are removed).
Page 82 of 115
TeleManagement Forum 2007
TMF814Av3.1