Cisco Cisco Prime Optical 10.0 Referências técnicas
TM FORUM Implementation Statement (IS) Template and Guidelines
routed only on resources (CTPs) which NetworkAccessDomain value is equal to such NAD/VPN (or is “free”, if
the FAD allows it).
the FAD allows it).
4.8 Root Cause Alarm Indication
The Root Cause Alarm Indication (RCAI) feature allows the EMS to indicate a distinction between raw (i.e., un-
correlated) alarms, and root cause alarm indications.
correlated) alarms, and root cause alarm indications.
The NMS can use the filtering capability of the Notification Service in conjunction with the RCAI field to
• receive only raw alarms, i.e., alarms with the root cause alarm field set to FALSE,
• receive only RCAIs, i.e., alarms with the root cause alarm field set to TRUE, or
• receive both raw alarms and RCAIs.
• receive only RCAIs, i.e., alarms with the root cause alarm field set to TRUE, or
• receive both raw alarms and RCAIs.
The following suggestions are noted concerning usage of the RCAI:
1. If a single alarm persists but does not get correlated with any other alarm, two notifications are
expected (the raw alarm and the RCAI associated with the uncorrelated raw alarm).
2. There is no field in the RCAI or the raw alarms that points to the other correlated alarms. The idea is to
keep the interface as simple as possible and still allow for the reporting of RCAIs.
3. The raw alarms result in notifications immediately. The RCAI is generated after the correlation window
closes (the length of the correlation window is an implementation issue for the EMS/NE vendor).
4. RCAIs usually clear after all related raw alarms clear and stay cleared for a persistence interval.
The above points are just suggestions concerning how the RCAI feature could work. Since these suggestions
relate to EMS implementation, they are not included in the requirements of the Business Agreement document.
relate to EMS implementation, they are not included in the requirements of the Business Agreement document.
ITU-T Recommendation M.2140, Transport Network Event Correlation, provides additional detail concerning
how RCAI might be supported.
how RCAI might be supported.
Some common questions and answers concerning the proposed model:
Doesn’t a notification need to be sent when a raw alarm latter gets declared as a root cause?
In the proposed model, raw alarms do not "change" to root causes. If the root cause of several alarms
is identified to be the same as a previous raw alarm, a new root cause alarm indication could be sent to
the NMS. Both the original raw alarm and the root cause would be treated as separate alarms in terms
of notifications sent over the EMS-NMS interface. Each would be cleared separately.
is identified to be the same as a previous raw alarm, a new root cause alarm indication could be sent to
the NMS. Both the original raw alarm and the root cause would be treated as separate alarms in terms
of notifications sent over the EMS-NMS interface. Each would be cleared separately.
What notification is sent when a previously declared root cause is now related to another root cause?
If the EMS decides that it has found a better root cause, the EMS could clear the original root cause
and declare a new root cause.
and declare a new root cause.
4.9 FTP
Examples
In order to represent managed element with several layers of flexibility, the MTNM team has added support for
Floating TPs in v3.0.
Floating TPs in v3.0.
An example managed element with several layers of flexibility is shown in Figure Error! No text of specified
style in document.-4 and Figure Erro No text of specified style in document.- . (Figure Error! No text of
specified style in document.-4 is the usual "elevation" figure where layers are shown stacked vertically one
above the other - server layers are always beneath client layers. Figure Error! No text of specified style in
document.-5 is a "plane" figure where the layout is "horizontal", as if all the lines in Figure Error! No text of
specified style in document.-4 were twisted to make them parallel. This allows multiplexing to be shown, and
is easier to relate to hardware. [Note that Figure Error! No text of specified style in document.-5 shows four
style in document.-4 and Figure Erro No text of specified style in document.- . (Figure Error! No text of
specified style in document.-4 is the usual "elevation" figure where layers are shown stacked vertically one
above the other - server layers are always beneath client layers. Figure Error! No text of specified style in
document.-5 is a "plane" figure where the layout is "horizontal", as if all the lines in Figure Error! No text of
specified style in document.-4 were twisted to make them parallel. This allows multiplexing to be shown, and
is easier to relate to hardware. [Note that Figure Error! No text of specified style in document.-5 shows four
Page 96 of 115
TeleManagement Forum 2007
TMF814Av3.1