17-2
Cisco ONS 15454 DWDM Reference Manual, R8.5
78-18343-02
Chapter 17 Performance Monitoring
17.1 Threshold Performance Monitoring
17.1 Threshold Performance Monitoring
Thresholds are used to set error levels for each PM parameter. You can set individual PM threshold
values from the Cisco Transport Controller (CTC) card view Provisioning tab. For procedures about
provisioning card thresholds, such as line and path thresholds, refer to the Cisco ONS 15454 DWDM
Procedure Guide.
During the accumulation cycle, if the current value of a PM parameter reaches or exceeds its
corresponding threshold value, a threshold crossing alert (TCA) is generated by the node and is
displayed by CTC. TCAs provide early detection of performance degradation. When a threshold is
crossed, the node continues to count the errors during a given accumulation period. If zero is entered as
the threshold value, generation of TCAs is disabled but performance monitoring continues.
Note Due to memory limitations and the number of TCAs generated by different platforms, you can manually
add or modify the following two properties to the platform property file (CTC.INI for Windows and
.ctcrc for UNIX) to fit the need:
• ctc.15xxx.node.tr.lowater=yyy (where xxx is platform and yyy is the number of the lowater mark.
The default lowater mark is 25.)
• ctc.15xxx.node.tr.hiwater=yyy (where xxx is platform and yyy is the number of the hiwater mark.
The default hiwater mark is 50.)
If the number of the incoming TCA is greater than the hiwater mark, the node will keep the latest lowater
mark and discard older ones.
Change the threshold if the default value does not satisfy your error monitoring needs. For example,
customers with a critical OC192/STM64 transponder installed for 911 calls must guarantee the best
quality of service on the line; therefore, they lower all thresholds on the client side so that the slightest
error raises a TCA.
Note When LOS, LOS-P, or LOF alarms occur on TXP and MXP trunks, ITU-T G.709/SONET/SDH TCAs
are suppressed. For details, see Chapter 16, “Alarm and TCA Monitoring and Management.”
17.2 Transponder and Muxponder Card Performance
Monitoring
This section lists PM parameters for transponder cards (TXP_MR_10G, TXP_MR_2.5G,
TXPP_MR_2.5G, TXP_MR_10E, TXP_MR_10E_C, and TXP_MR_10E_L), muxponder cards
(MXP_2.5G_10G, MXP_2.5G_10E, MXP_2.5G_10E_C, MXP_2.5G_10E_L, MXP_MR_2.5G,
MXPP_MR_2.5G, MXP_MR_10DME-C, and MXP_MR_10DME-L), GE_XP, 10GE_XP, and
ADM-10G cards. The transponder and muxponder PM parameters are divided into Optics PM, Payload
PM, and OTN PM tabs. The tabs displayed vary depending on the card installed. For more information,
see the “17.2.1 Optics PM Window” section on page 17-4, the “17.2.2 Payload PM Window” section
on page 17-5, or the “17.2.3 OTN PM Window” section on page 17-10.
For ONS 15454 ANSI nodes, Figure 17-1 shows where overhead bytes detected on the
application-specific integrated circuits (ASICs) produce PM parameters for the TXP_MR_10G card.
The remaining transponder and muxponder cards perform similarly to this illustration.
To Next Page
Loading...
Need help?
General
