Configure Performance Monitoring

Performance monitoring (PM) parameters are used by service providers to gather, store, set thresholds for, and report performance data for early detection of problems. The user can retrieve both the current and historical PM counters for the various controllers in several intervals.

PM for optical parameters include laser bias current, transmit and receive optical power, mean polarization mode dispersion, accumulated chromatic dispersion, and received optical signal-to-noise ratio (OSNR). These parameters simplify troubleshooting operations and enhance data that can be collected directly from the equipment.

Configure PM Parameters

You can configure the performance monitoring parameters for the OTS controllers. To configure PM parameters, use the following commands.

configure

controller controllertype R/S/I/P { pm { 15-min | 24-hour | 30-sec } ots { report | threshold } { opr | opt }value }

commit

Examples

The following is a sample in which the performance monitoring parameters of OTS controller is configured in 24 hour intervals. 


configure
controller ots 0/1/0/0 pm 24-hour ots report opr max-tca enable
commit

The above command enables the maximum TCA (Threshold Crossing Alert) for opr (optical power received) of ots 0/1/0/0 controller in 24 hour intervals. 


configure
controller ots 0/1/0/0 pm 24-hour ots threshold opr max 4000
commit

The above command sets the maximum TCA for opr of ots 0/1/0/0 controller in 24 hour intervals.

The PM collector starts and collects controller data at the following intervals.

  • 30 seconds interval - 30 samples jitter provision of 6 seconds

  • 15 minutes interval - 32 samples jitter provision of 45 seconds

  • 24 hours interval - 1 sample jitter provision of 45 seconds

The jitter provides for any computation delay for data collected at the data provider PM engine.

View PM Parameters

Use this procedure to view the performance monitoring parameters for OTS controllers.

Procedure

show controllers controllertype R/S/I/P { pm { current | history } { 15-min | 24-hour | 30-sec | flex-bin } { optics lane-number }{ bucket bucket-number }

The bucket parameter must be specified for pm history.

Example:

RP/0/RP0/CPU0:ios# show controllers ots 0/1/0/0 pm current 15-min optics 1

Displays the current performance monitoring parameters of the Optics controller in 15 minute intervals. 


Thu Mar 16 15:07:21.093 CET

Optics in the current interval [15:00:00 - 15:07:21 Thu Mar 16 2017]

Optics current bucket type : Valid
MIN AVG MAX Threshold TCA Threshold TCA
(min) (enable) (max) (enable)
LBC[% ] : 0.2 4.5 18.6 0.0 NO 0.0 NO 
OPT[dBm] : -40.00 -0.40 8.00 -50.00 NO 10.00 NO 
OPR[dBm] : -17.52 -17.01 -16.90 -50.00 NO 10.00 NO 

Last clearing of "show controllers OPTICS" counters never

The show controllers command occasionally returns the wrong bucket. For example, the following command query at "Mon May 29 15:02:05.697 CEST" must have returned the bucket for the interval [15:01:30 - 15:02:00 Mon May 29 2017] while it returned the previous bucket [15:01:00 - 15:01:30 Mon May 29 2017]. 

RP/0/RP0/CPU0:ios# show controllers optics 0/1/0/4 pm history 30-sec optics 1 bucket 5

Displays the current performance monitoring parameters of the Optics controller in 15 minute intervals related to bucket 5. 


Mon May 29 15:02:05.697 CEST

Optics in interval 1 [15:01:00 - 15:01:30 Mon May 29 2017]

Optics history bucket type : Valid
              MIN       AVG       MAX 
LBC[% ]    : 335.3     341.3     352.3  
OPT[dBm]   : 1.90      2.01      2.10   
OPR[dBm]   : -12.20    -12.16    -12.10 

Last clearing of "show controllers OPTICS" counters never