Cisco ONS 15454 - Remote Monitoring-Managed Pms

2-60
Cisco ONS SONET TL1 Command Guide, R6.0
Chapter 2 Procedures and Provisioning
2.10 Remote Monitoring-Managed PMs
Step 6 Switch the traffic back onto the working high-density card:
Input Format:
SW-TOWKG-EQPT:[<TID>]:<AID>:<CTAG>::[<MODE>],[<DIRN>];
Input Example:
SW-TOWKG-EQPT::SLOT-16:123::FRCD,BTH;
Step 7 Repeat these steps to upgrade the other low-density card in the protection group.
2.10 Remote Monitoring-Managed PMs
This section describes the retrieval, threshold setting, threshold crossing alerts (TCAs) and scheduled
performance monitoring (PM) reporting for all the remote monitoring (RMON)-managed PM data in the
Cisco ONS 15454, ONS 15327, ONS 15310-CL and ONS 15600.
Note Cisco ONS 15600 does not support RMONTH commands. For ONS 15600, RMON counts can be
retrieved using TL1 commands, but RMON thresholds cannot be set using TL1.
The cards that support RMON PMs include: G1K-4, ML1000-2/ML100T-12, FC_MR-4, ASAP-4,
MXP_MR_2.5G/MXPP_MR_2.5G, and ML-100T-8/CE-100T-8. The PM types for these cards include
Ethernet statistic types defined in standard SNMP/RMON MIB, and also include other statistic types
managed by RMON, for example, the Fibre Channel statistic types.
When creating an RMON threshold, there are two threshold values that need to be specified. The first
threshold is the rising threshold and the other is the falling threshold. There are other parameters that
need to be specified when creating the RMON threshold, for example, the startup type and the sample
type.
Note There can be more than one threshold defined for each RMON statistic type.
The current bucket is not defined by the RMON. RMON-managed PM only shows the history data of the
PMs and the data accumulated since the last time the counters are cleared (RAW-DATA).
In the RMON TCA, the accumulation time period is not the predefined PM bucket accumulation time,
such as 15-MIN or 1-DAY. It can be any integer (any time greater than 10 seconds) that is defined when
creating the RMON threshold.
Note For platform-specific PM information, refer to the Procedure Guide and Reference Manual of that
platform.