Cisco Cisco Transport Manager 9.1 Technical References
MTNM IMPLEMENTATION STATEMENT TEMPLATES AND GUIDELINES
TMF 814Av3.0
TeleManagement Forum 2003
99
In Mode A, a CC, active or not, can only belong to at most one SNC. In the case of non-singleton
subnetworks, an exception to the non-sharing rule is made for SNCs of a broadcast system, i.e.,
a multipoint connection. The legs of a multipoint connection are represented as individual SNCs.
The legs of a broadcast system may share CCs and always share the same source CTP.
subnetworks, an exception to the non-sharing rule is made for SNCs of a broadcast system, i.e.,
a multipoint connection. The legs of a multipoint connection are represented as individual SNCs.
The legs of a broadcast system may share CCs and always share the same source CTP.
Mode A is best for EMSs that only support singleton subnetworks (i.e., subnetwork consisting of a
single managed element) and that do not keep a database of pending SNCs. Mode A might be
popular with vendors having lightweight switch-bound EMSs.
single managed element) and that do not keep a database of pending SNCs. Mode A might be
popular with vendors having lightweight switch-bound EMSs.
4.4.2 Mode B
In Mode B, the goal is for the EMS to represent the current network configuration as well as
potential “future” SNCs that have been prepared by the NMS, but not yet activated. The Pending
state can also be used in situations where SNC share CCs at different times. For example, SNC1
is used by customer A from 8am to 8pm every day. SNC2 shares many CCs with SNC1 but is
only used by Customer B from 9pm to 7am every day. When SNC1 is in the Active state, SNC2
is put in the Pending state, and vice versa.
potential “future” SNCs that have been prepared by the NMS, but not yet activated. The Pending
state can also be used in situations where SNC share CCs at different times. For example, SNC1
is used by customer A from 8am to 8pm every day. SNC2 shares many CCs with SNC1 but is
only used by Customer B from 9pm to 7am every day. When SNC1 is in the Active state, SNC2
is put in the Pending state, and vice versa.
An SNC’s entry and exit to and from the Pending state is controlled solely by the NMS. Neither
the EMS or craft intervention can put an SNC into (or remove an SNC from) the Pending state.
the EMS or craft intervention can put an SNC into (or remove an SNC from) the Pending state.
4.4.3 Mode C
In Mode C, the goal is for the EMS to represent only the current network configuration (as was
the case with Mode A). Contrary to Mode A, it does not limit sharing of CCs among SNCs, and
does not attempt to have a one-to-one correspondence between the network configurations and
the SNC configurations.
the case with Mode A). Contrary to Mode A, it does not limit sharing of CCs among SNCs, and
does not attempt to have a one-to-one correspondence between the network configurations and
the SNC configurations.
Mode C is best for EMSs that support non-singleton subnetworks and that do not keep a
database of pending SNCs. This mode has an advantage over Mode A, because it allows SNC
reorganizations without traffic interruption (only useful in non-singleton subnetworks). For
example, if the EMS currently has two “consecutive” SNCs that the NMS wants to merge into one
“larger” SNC, this can be done without interrupting traffic by creating and activating the larger
SNC, then deactivating and deleting the two consecutive SNCs.
database of pending SNCs. This mode has an advantage over Mode A, because it allows SNC
reorganizations without traffic interruption (only useful in non-singleton subnetworks). For
example, if the EMS currently has two “consecutive” SNCs that the NMS wants to merge into one
“larger” SNC, this can be done without interrupting traffic by creating and activating the larger
SNC, then deactivating and deleting the two consecutive SNCs.
4.4.4 Mode D
Mode D is basically a combination of Modes B and C. This Mode is favored by vendors (or
service providers) that have a feature rich NMS that can take advantage of the Pending state
(related to scheduling features) and the sharing of Active CCs.
service providers) that have a feature rich NMS that can take advantage of the Pending state
(related to scheduling features) and the sharing of Active CCs.
4.5 Example Probable Cause Template
The following example illustrates the use of the probable cause template defined in Section
2.1.6.1. The example is based on actual SDH and WDM equipment that are managed according
to ITU principles. The "Transmission" alarms (from TPs) are from a submarine equipment type
that uses Forward Error Correction, or FEC: a method based on Reed-Solomon encoding that
enables errors to be not only detected, but corrected.
2.1.6.1. The example is based on actual SDH and WDM equipment that are managed according
to ITU principles. The "Transmission" alarms (from TPs) are from a submarine equipment type
that uses Forward Error Correction, or FEC: a method based on Reed-Solomon encoding that
enables errors to be not only detected, but corrected.
The following conventions are used in Table 4-2.