Performance monitoring
|
Feature Name |
Release Information |
Feature Description |
|---|---|---|
| Performance Monitoring Enhancements |
Cisco IOS XR Release 24.4.1 |
You can now view historical Performance Monitoring (PM) parameters for the past 1 to 7 days for the 24-hour interval on these controllers:
This feature enhances data collection directly from the equipment, providing a comprehensive view of performance over time. Parameter added:
|
Performance monitoring (PM) parameters help service providers gather and store performance data, set thresholds, and report results. This process enables early detection of network issues.
You can configure and retrieve PM counters for various controllers in 30-second, 15-minute, or 24-hour flex-bin intervals.
These parameters simplify troubleshooting operations and enhance the data collected directly from the equipment.
 Note |
Downgrade to 7.11.1 or earlier releases from 24.1.1 can lead to a restart of the pm_collector process. To avoid this, clear the PM historical data before the downgrade using these commands: Use these commands if you are already experiencing a continuous pm_collector restart. |
Configure the PM parameters
Follow these steps to configure PM parameters:
Procedure
|
Run the show controller controllertype R/S/I/P { pm { current | history} { 30-sec 15-min | | 24-hour } { optics | ether | fec | otn | prbs| flex-bin} linenumber command to configure the controllers. Example:This sample configures the performance monitoring parameters for the optics controller at 24-hour intervals. Example:This sample configures the performance monitoring parameters for the Ethernet controller at 15-minute intervals. Example:This sample configures the performance monitoring parameters for the Coherent DSP controller at 30-second intervals. |
View the PM parameters
Follow these steps to configure the PM parameters:
Procedure
|
Step 1 |
Run the show controllers controllertype R/S/I/P { pm { current | history } { 30 sec | 15-min | 24-hour } { optics | ether | fec | otn | prbs} linenumber } command to display the current performance monitoring parameters of the controller with 15-minute intervals. Example:This sample displays the current performance monitoring parameters of the Optics controller with 15-minute intervals. Example:This sample displays the current performance monitoring parameters of the client Optics controller with 15-minute intervals. Example:This sample displays the current performance monitoring parameters of the client Ethernet controller with 15-minute intervals. Example:This sample displays the current performance monitoring for FEC on the Coherent DSP controller 15-minute intervals: Example:This sample displays the current performance monitoring parameters for PRBS of the Coherent DSP controller with 15-minute intervals: Example:This sample displays the current performance monitoring FEC parameters of the coherentDSP OTN with 15-minute intervals: Example:Example:Example:Example:Example:Example:Example:From Release 24.2.11, the show controllers command output displays post FEC BER and pre FEC BER for the Ethernet controllers of the 2.4T and 2.4TX cards. |
|
Step 2 |
Run the show controllers controllertype R/S/I/P { pm { current | history } { 30 sec | 15-min | 24-hour } { optics | ether | fec | otn | prbs} linenumber } command to display the current performance monitoring parameters of the controller with 30-minute intervals. Example:This sample displays the current performance monitoring of PCS of the Ethernet controller with 30-second intervals: Example:This sample displays the history performance monitoring of PCS of the Ethernet controller with 30-second intervals: |
|
Step 3 |
Run the show controllers controllertype R/S/I/P { pm { current | history } { 30 sec | 15-min | 24-hour } { optics | ether | fec | otn | prbs} linenumber } command to display the current performance monitoring parameters of the controller with 10-second intervals as flexi-bin. Example:This sample displays the current performance monitoring parameters of the trunk optics controller with 10-second intervals as flexi-bin: Example:This sample displays the history performance monitoring parameters of the trunk optics controller with 10-second intervals as flexi-bin: Example:This sample displays the current performance monitoring parameters of the coherentDSP controller as flexi-bin: |
|
Step 4 |
Run the show controllers controllertype R/S/I/P { pm { current | history } { 30 sec | 15-min | 24-hour } { optics | ether | fec | otn | prbs} linenumber } command to display the current performance monitoring FEC parameters of the coherentDSP OTN. Example:This sample displays the current performance monitoring FEC parameters of the coherentDSP OTN with 15-minute intervals: Example:This sample displays the current performance monitoring for OTN parameters of the ODU-Flex with 15-minute intervals: |
Clear the PM parameters
Procedure
|
Run the clear controller controllertype R/S/I/P pm command to clear performance monitoring parameters for Ethernet and CoherentDSP controllers. Example:This sample shows how to clear the PM parameters on the CoherentDSP controller. Example:This sample shows how to clear the PM parameters on the Ethernet controller. |
PM history persistence
PM history parameters for Optics, Ethernet, and coherent DSP controllers are retained even after a line card cold reload, line card warm reload, XR reload, Calvados reload, RP reload, Hw-module all reload, power cycle, or upgrade of the NCS 1014 chassis.
After a software upgrade to the latest release, you can view the history performance monitoring parameters from the previous release. The PM history persistence is supported for 30-second, 15-minute, and 24-hour bucket types.
However, this list describes the time required to fill all historical buckets for each bucket type. After the buckets are full, no errors appear when you fetch PM historical data.
-
For 30-second bucket type, 15 minutes is required to fill 30 historical buckets.
-
For 15-minute bucket type, 8 hours is required to fill 32 historical buckets.
-
For 24-hour bucket type, 24 hours are required to fill 7 historical bucket.
PM counters are updated continuously in the current bucket for all bucket types: flex, 30-second, 15-minute, and 24-hour. When the timer expires for a bucket type, the current PM data moves to the historical PM bucket. This process is called rollover. After rollover, the current PM data becomes available as historical PM data.
If the controller is deleted or removed, PM data remains persistent for three hours. If the controller does not return within three hours, the PM data is cleared because the controller is considered no longer in use.
Limitations of PM history persistence
If the NCS 1014 reloads during the rollover period, one of these scenarios occurs:
-
A complete PM bucket may be missing, and the system marks the next PM bucket as Invalid.
-
PM bucket expiry message appears as follows:
RP/0/RP0/CPU0:ios#show controllers hundredGigECtrlr 0/3/0/2/2 pm history 30-sec ether 29 Fri Apr 1 01:32:20.646 UTC History data is empty, Verify at least one collection period is expired -
PM bucket interval is marked as Invalid and counters are updated as zero.
-
PM bucket interval is marked as Invalid and counters are updated as nonzero.
Instantaneous Q-Margin
Scenarios on Instantaneous Q-margin
In these scenarios, the initial few PM buckets are displayed as valid although the instantaneous Q-margin values are displayed as invalid in those buckets. The PM is performed for 30 sec, 15 mins, and 24 hours, respectively.
Scenarios where this issue occurs include:
-
Shutdown or enable optics
-
Trunk rate change
-
Fiber cuts
To address these situations, avoid considering the initial PM bucket readings when monitoring the instantaneous Q-margin values for these scenarios.
This sample shows that, in certain scenarios, the initial PM bucket readings are invalid. Later, the PM bucket readings become valid, even when the instantaneous Q-margin value remains invalid.
RP/0/RP0/CPU0:ios#show controllers coherentDSP 0/2/0/0 pm history flex-bin fec 1
Fri Sep 22 14:17:01.008 IST
g709 FEC in interval 1 [14:16:50 - 14:17:00 Fri Sep 22 2023]
Flexible bin interval size: 10 seconds
FEC history bucket type : Valid
EC-BITS : 25615718133 UC-WORDS : 0
MIN AVG MAX
PreFEC BER : 3.37E-03 3.49E-03 3.90E-03
PostFEC BER : 0E-15 0E-15 0E-15
Q : 8.60 8.60 8.60
Q_margin : 2.50 2.56 2.60
Instantaneous Q_margin : 2.20 2.20 2.20
Now, the PM buckets are valid although the instantaneous Q-margin value is invalid.
RP/0/RP0/CPU0:ios#show controllers coherentDSP 0/2/0/0 pm history 30-sec fec 1
Sep 22 08:52:03.750 UTC
g709 FEC in interval 1 [08:51:50 - 08:52:00 Fri Sep 22 2023]
FEC history bucket type : Invlid
EC-BITS : 35072302421 UC-WORDS : 0
MIN AVG MAX
PreFEC BER : 5.20E-03 5.30E-03 5.64E-03
PostFEC BER : 0E-15 0E-15 0E-15
Q : 8.10 8.10 8.10
Q_margin : 2.10 2.10 2.10
Instantaneous Q_margin : 1.80 1.80 1.80
View Ethernet statistics
You can access and view the Performance Monitoring statistics for the Ethernet controllers.
Procedure
|
Run the show controller controllertype R/S/I/P pm command to view the performance monitoring statistics for the Ethernet controllers. Example:
|
Feedback