- About this Manual
- Chapter 1, Shelf Assembly Hardware
- Chapter 2, Card Reference
- Chapter 3, Node Reference
- Chapter 4, Network Reference
- Chapter 5, Cisco Transport Controller Operation
- Chapter 6, Security Reference
- Chapter 7, Timing Reference
- Chapter 8, Manage Network Connectivity
- Chapter 9, Alarm and TCA Monitoring and Management
- Chapter 10, Performance Monitoring
- Chapter 11, SNMP
- Appendix A, Hardware Specifications
- Appendix B, Administrative and Service States
- Appendix C, Network Element Defaults
- 10.1 Threshold Performance Monitoring
- 10.2 Transponder and Muxponder Card Performance Monitoring
- 10.3 DWDM Card Performance Monitoring
- 10.3.1 Optical Amplifier Card Performance Monitoring Parameters
- 10.3.2 Multiplexer and Demultiplexer Card Performance Monitoring Parameters
- 10.3.3 4MD-xx.x Card Performance Monitoring Parameters
- 10.3.4 OADM Channel Filter Card Performance Monitoring Parameters
- 10.3.5 OADM Band Filter Card Performance Monitoring Parameters
- 10.3.6 Optical Service Channel Card Performance Monitoring Parameters
- 10.4 Optics and 8b10b PM Parameter Definitions
- 10.5 ITU G.709 and ITU-T G.8021 Trunk-Side PM Parameter Definitions
- 10.6 Full RMON Statistics PM Parameter Definitions
- 10.7 FEC PM Parameter Definitions
- 10.8 SONET PM Parameter Definitions
- 10.9 SDH PM Parameter Definitions
- 10.10 Pointer Justification Count Performance Monitoring
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. In this chapter, PM parameters and concepts are defined for transponder, muxponder, and dense wavelength division multiplexing (DWDM) cards in the Cisco ONS 15454 including optical amplifier, multiplexer, demutiplexer, optical add/drop multiplexer (OADM), and optical service channel (OSC) cards.
Note Unless otherwise specified, "ONS 15454" refers to both ANSI and ETSI shelf assemblies.
For information about enabling and viewing PM values, refer to the Cisco ONS 15454 DWDM Procedure Guide.
Chapter topics include:
•Threshold Performance Monitoring
•Transponder and Muxponder Card Performance Monitoring
•DWDM Card Performance Monitoring
•Optics and 8b10b PM Parameter Definitions
•ITU G.709 and ITU-T G.8021 Trunk-Side PM Parameter Definitions
•Full RMON Statistics PM Parameter Definitions
•SONET PM Parameter Definitions
•Pointer Justification Count Performance Monitoring
Note For additional information regarding PM parameters, refer to ITU G.826, ITU-T G.8021, ITU G.709, Telcordia documents GR-1230-CORE, GR-820-CORE, GR-499-CORE, and GR-253-CORE, and the ANSI T1.231 document entitled Digital Hierarchy - Layer 1 In-Service Digital Transmission Performance Monitoring.
10.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 9 "Alarm and TCA Monitoring and Management."
10.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), and 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). 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 "Optics PM Window" section, the "Payload PM Window" section, or the "OTN PM Window" section.
For ONS 15454 ANSI nodes, Figure 10-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.
Figure 10-1 ONS 15454 ANSI Node PM Read Points for TXP_MR_10G Card
For ONS 15454 ETSI nodes, Figure 10-2 shows where overhead bytes detected on the ASICs produce PM parameters for the TXP_MR_10G card. The remaining transponder and muxponder cards perform similarly to this illustration.
Figure 10-2 ONS 15454 ETSI Node PM Read Points on TXP_MR_10G Cards
10.2.1 Optics PM Window
The Optics PM window lists parameters at the trunk and client side for all transponder and muxponder cards. The Optics PM window provides buttons to change the statistical values shown. The Refresh button manually refreshes statistics. Auto-Refresh sets a time interval at which automatic refresh occurs. In the Historical PM subtab, the Clear button sets the values on the card to zero. All counters on the card are cleared. The Help button activates context sensitive help. Table 10-1 lists the trunk-side and client-side optics PM parameters.
|
|
---|---|
Laser Bias (Avg,%) |
Average Laser Bias Current (Laser Bias Avg) is the average percentage of laser bias current during the PM time interval. |
Laser Bias (Max,%) |
Maximum Laser Bias Current (Laser Bias Max) is the maximum percentage of laser bias current during the PM time interval. |
Laser Bias (Min,%) |
Minimum Laser Bias Current (Laser Bias Min) is the minimum percentage of laser bias current during the PM time interval. |
Link Status |
Indicates if the Fibre Channel link is receiving a valid Fibre Channel signal (carrier) from the attached Fibre Channel device. Up means present, and down means not present. |
Rx Optical Pwr (Min,dBm) |
Minimum Receive Optical Power (Rx Optical Pwr Min, dBm) is the minimum received optical power during the PM time interval. |
Rx Optical Pwr (Avg,dBm) |
Average Receive Optical Power (Rx Optical Pwr Avg, dBm) is the average received optical power during the PM time interval. |
Rx Optical Pwr (Max,dBm) |
Maximum Receive Optical Power (Rx Optical Pwr Max, dBm) is the maximum received optical power during the PM time interval. |
Tx Optical Pwr (Min,dBm)1 |
Minimum Transmit Optical Power (Tx Optical Pwr Min, dBm) is the minimum optical power transmitted during the PM time interval. |
Tx Optical Pwr (Avg,dBm)1 |
Average Transmit Optical Power (Tx Optical Pwr Avg, dBm) is the average optical power transmitted during the PM time interval. |
Tx Optical Pwr (Max,dBm)1 |
Maximum Transmit Optical Power (Tx Optical Pwr Max, dBm) is the maximum optical power transmitted during the PM time interval. |
1 On the trunk side, this PM is not available for the following cards: TXP_MR_2.5G, TXPP_MR_2.5G, MXP_MR_2.5G, and MXPP_MR_2.5G. |
10.2.2 Payload PM Window
The Payload PM window subtabs change depending on the card provisioning. For more information about provisioning TXP and MXP cards, refer to the "Provision Transponder and Muxponder Cards" chapter in the Cisco ONS 15454 DWDM Procedure Guide. Possible Payload PM subtabs are: SONET, SDH, Statistics, Utilization, and History. The following buttons function the same on all of the tabs. Not all tabs have all of these buttons.
•The Refresh button manually refreshes statistics.
•Auto-Refresh sets a time interval at which automatic refresh occurs.
•The Baseline button resets the displayed statistics values to zero.
•(Statistics window only) The Clear button allows you to set the values to zero for displayed statistics, all statistics for a port, and all statistics for all optical ports on a card.
•The Help button activates context sensitive help.
For a list of the payload PM provisioning options for all transponder and muxponder cards, refer to the Cisco ONS 15454 DWDM Procedure Guide. The options selected in the Provisioning tab can affect the parameters displayed in the Performance > Payload PM tab.
Table 10-2 lists the PM parameter types that appear when a particular port type is provisioned for a transponder or muxponder card.
|
|
---|---|
SONET/SDH (including 10G Ethernet WAN Phy) |
SONET or SDH PMs |
10G Ethernet LAN Phy |
Full remote monitoring (RMON) statistics |
ESCON |
Payload PMs are not applicable to 2R port types. |
1 The port type is provisioned from card view on the Provisioning > Pluggable Port Modules tab. For pluggable port module (PPM) provisioning procedures, refer to the Cisco ONS 15454 DWDM Procedure Guide. 2 Performance monitoring parameters are displayed from the card view on the Performance tab. |
10.2.2.1 Payload PM SONET/SDH Window
Table 10-3 lists SONET/SDH layer near-end and far-end PM parameters listed in the card view on the Performance > Payload PM > SONET or SDH tab. SONET/SDH layer PMs are available when the client type is set to OC3/STM1, OC12/STM4, or OC48/STM16 on the TXP_MR_2.5G or when OC192/STM64 is set on the TXP_MR_10G, TXP_MR_10E, TXP_MR_10E_C, or TXP_MR_10E_L on ONS 15454 SONET nodes. OC48/STM16 trunk PMs are available on MXP_MR_2.5G and MXPP_MR_2.5G cards on ONS 15454 SONET or ONS 15454 SDH nodes. OC48/STM16 client PMs are available on MXP_MR_10DME_C, MXP_MR_10DME_L, MXP_2.5G_10G, MXP_2.5G_10E, MXP_2.5G_10E_C, and MXP_2.5G_10E_L cards on ONS 15454 SONET or ONS 15454 SDH nodes. For PM definitions, see Table 10-27 and Table 10-28.
SONET |
|
|
|
CV-LFE |
CV-L |
Applicable standard is Telcordia GR-253. |
|
SDH |
MS-BBE |
RS-BBE |
Applicable standard is Telcordia GR-253. |
1 Applicable to optical channel (OCH) and Client (CLNT) facilities. 2 For MXP_MR_2.5G and MXPP_MR_2.5G cards, these parameters are shown in the Performance > Payload PM > SONET PM tabs in the card view. |
10.2.2.2 Payload PM Statistics Window
Table 10-4 lists the 10 Gigabit Ethernet (10 GE) payload statistics that are available on the TXP_MR_10G, TXP_MR_10E, TXP_MR_10E_C, and TXP_MR_10E_L cards. PPM provisioning must be completed under the card view Provisioning > Pluggable Port Modules tab for 10 GE to be enabled. For PPM provisioning procedures, refer to the Cisco ONS 15454 DWDM Procedure Guide. The parameters are listed under card view on the Performance > Payload PM > Statistics tab. For 10 GE payload definitions, see Table 10-25.
Note Utilization PMs are also available per port.
Table 10-5 lists the payload PM parameters that are available on the TXP_MR_2.5G and the TXPP_MR_2.5G cards when the ONE_GE or FC1G client type is enabled. For PPM provisioning procedures, refer to the Cisco ONS 15454 DWDM Procedure Guide. For payload definitions, see the "Optics and 8b10b PM Parameter Definitions" section and the "Full RMON Statistics PM Parameter Definitions" section.
Note Payload PM is not available for the 2FC client type.
Table 10-6 lists the payload PM parameters that are available on the MXP_MR_2.5G and the MXPP_MR_2.5G cards when the ONE_GE or the FC1G client type is enabled. For PPM provisioning procedures, refer to the Cisco ONS 15454 DWDM Procedure Guide. For payload definitions, see the "Optics and 8b10b PM Parameter Definitions" section and the "Full RMON Statistics PM Parameter Definitions" section.
Table 10-7 lists the FC client-side payload PM parameters. FC payload PMs are available on the FC port on both the MXP_MR_2.5G and the MXPP_MR_2.5G cards when the FC1G client type is enabled. For PPM provisioning procedures, refer to the Cisco ONS 15454 DWDM Procedure Guide. For payload definitions, see the "Full RMON Statistics PM Parameter Definitions" section.
Table 10-8 lists the Transparent Generic Framing Procedure (GFP-T) payload PMs. The GFP-T payload PMs are available on the GFP port on both the MXP_MR_2.5G and the MXPP_MR_2.5G cards when the ONE_GE or the 1 FC client type is enabled. GFP-T payload PMs are also available on the client port on both the MXP_MR_2.5G and the MXPP_MR_2.5G cards when the 1 FC client type is enabled. For PPM provisioning procedures, refer to the Cisco ONS 15454 DWDM Procedure Guide. For payload definitions, see the "Full RMON Statistics PM Parameter Definitions" section.
|
---|
gfpStatsCSFRaised |
10.2.2.3 MXP_MR_2.5G/MXPP_MR_2.5G Payload Utilization Window
The Payload PM Utilization window in the card view Performance > Payload> Utilization tab shows the percentage of transmit (Tx) and receive (Rx) line bandwidth used by the ports during consecutive time segments. This tab cannot be viewed unless the appropriate PPM port type is provisioned. For PPM provisioning procedures, refer to the Cisco ONS 15454 DWDM Procedure Guide. The Utilization window provides an Interval list that enables you to set time intervals of 15 minutes or 1 day. Line utilization is calculated with the following formulas:
Rx = (inOctets + inPkts * 20) * 8 / 100% interval * maxBaseRate
Tx = (outOctets + outPkts * 20) * 8 / 100% interval * maxBaseRate
The interval is defined in seconds. The maxBaseRate is defined by raw bits per second in one direction for the port (that is, 1 Gbps). The maxBaseRate for MXP_MR_2.5G and MXPP_MR_2.5G cards is shown for the ONS 15454 nodes in Table 10-9.
|
|
---|---|
STS-1/VC3 |
51840000 |
STS-3c/VC4 |
155000000 |
STS-6c/VC4-2c |
311000000 |
STS-12c/VC4-4c |
622000000 |
Note Line utilization numbers express the average of ingress and egress traffic as a percentage of capacity.
10.2.2.4 Payload History Window
The Payload PM History window in the card view Performance > Payload > History tab lists past statistics for the previous time intervals. This tab cannot be viewed unless the appropriate PPM port type is provisioned. For PPM provisioning procedures, refer to the Cisco ONS 15454 DWDM Procedure Guide. Depending on the selected time interval, the History window displays the statistics for each port for the number of previous time intervals as shown in Table 10-10.
|
|
---|---|
15 minutes |
32 (current and previous) |
1 day (24 hours) |
2 (current and previous) |
10.2.3 OTN PM Window
The OTN tab has an ITU-T G.709 PM subtab and an FEC subtab. Both subtabs provide buttons to change the statistical values shown in the Performance tab. The Refresh button manually refreshes statistics. Auto-Refresh sets a time interval at which automatic refresh occurs. The Baseline button resets the displayed statistics values to zero. The Statistics window also has a Clear button. The Clear button sets the values on the card to zero. All counters on the card are cleared. The Help button activates context sensitive help. For more information about provisioning optical transport network (OTN) settings, refer to the Cisco ONS 15454 DWDM Procedure Guide.
Table 10-11 lists the OTN PM provisioning options for all transponder and muxponder cards. The options selected in the Provisioning tab affects the parameters displayed in the Performance > OTN PM tab.
|
|
---|---|
MXPP_MR_2.5G |
— |
MXP_2.5G_10E |
G.709 |
MXP_2.5G_10E_C |
G.709 |
MXP_2.5G_10E_L |
G.709 |
MXP_2.5G_10G |
G.709 |
MXP_MR_2.5G |
— |
MXP_MR_10DME_C |
G.709 |
MXP_MR_10DME_L |
G.709 |
TXPP_MR_2.5G |
G.709 |
TXP_MR_10E |
G.709 |
TXP_MR_10E_C |
G.709 |
TXP_MR_10E_L |
G.709 |
TXP_MR_10G |
G.709 |
TXP_MR_2.5G |
G.709 |
1 OTN provisioning is performed from card view on the Provisioning > OTN > OTN Lines, G.709 Thresholds, and FEC Thresholds tabs. |
Table 10-12 lists the OTN trunk-side PM parameters listed on the G.709 tab. OTN PMs are available when ITU G.709 is enabled from the card view Provisioning > OTN > OTN Lines tab. OTN PMs are not available on MXP_MR_2.5G and MXPP_MR_2.5G cards. For ITU G.709 section and path monitoring PM definitions, see the "ITU G.709 and ITU-T G.8021 Trunk-Side PM Parameter Definitions" section.
|
|
---|---|
BBE-SM |
ITU G.709 standard section monitoring |
BBE-PM |
ITU G.709 standard path monitoring |
1 Applicable to OCH facility. |
Table 10-13 lists the forward error correction (FEC) PM parameters. FEC PMs are available when ITU-T G.709 is enabled and FEC is set to standard or enhanced. These parameters are provisioned from the card view Provisioning > OTN > OTN Lines tab. FEC PMs are not available on MXP_MR_2.5G and MXPP_MR_2.5G cards. For PM definitions, see the "FEC PM Parameter Definitions" section.
|
|
---|---|
Bit Errors |
BIT-EC |
Uncorrectable Words |
UNC-WORDS |
1 Applicable to OCH facility. |
Table 10-14 lists ONS 15454 optics and 8b10b PM parameters. For ONS 15454 optics and 8b10b definitions, see the "Optics and 8b10b PM Parameter Definitions" section.
|
|
---|---|
LBCL-AVG |
CGV |
1 The TXP_MR_2.5G and TXPP_MR_2.5G card Enterprise System Connection (ESCON) payload does not support optics PMs on the client port due to Small Form-factor Pluggable (SFP)-imposed restrictions. 2 Applicable to TXP_MR_2.5G and TXPP_MR_2.5G cards only. |
10.3 DWDM Card Performance Monitoring
The following sections define PM parameters and definitions for the ONS 15454 OPT-PRE, OPT-BST, OPT-BST-L, OPT-AMP-L, 32MUX-O, 32DMX-O, 32DMX, 32DMX-L, 4MD-xx.x, AD-1C-xx.x, AD-2C-xx.x, AD-4C-xx.x, AD-1B-xx.x, AD-4B-xx.x, OSCM, OSC-CSM, 32WSS, and 32WSS-LDWDM cards.
10.3.1 Optical Amplifier Card Performance Monitoring Parameters
The PM parameters for the OPT-PRE, OPT-AMP-L, OPT-BST, and OPT-BST-L cards are listed Table 10-15. For ONS 15454 optics definitions, see the "Optics and 8b10b PM Parameter Definitions" section.
|
|
---|---|
OPT |
OPR |
10.3.2 Multiplexer and Demultiplexer Card Performance Monitoring Parameters
The PM parameters for the 32MUX-O, 32WSS, 32WSS-L, 32DMX, 32DMX-L, and 32DMX-O cards are listed in Table 10-16. For ONS 15454 optics definitions, see the "Optics and 8b10b PM Parameter Definitions" section.
|
|
---|---|
OPR |
OPT |
10.3.3 4MD-xx.x Card Performance Monitoring Parameters
The PM parameters for the 4MD-xx.x cards are listed in Table 10-17. For ONS 15454 optics definitions, see the "Optics and 8b10b PM Parameter Definitions" section.
|
|
---|---|
OPR |
OPT |
10.3.4 OADM Channel Filter Card Performance Monitoring Parameters
The PM parameters for the AD-1C-xx.x, AD-2C-xx.x, and AD-4C-xx.x cards are listed in Table 10-18. For ONS 15454 optics definitions, see the "Optics and 8b10b PM Parameter Definitions" section.
|
|
---|---|
OPR |
OPT |
10.3.5 OADM Band Filter Card Performance Monitoring Parameters
The PM parameters for the AD-1B-xx.x and AD-4B-xx.x cards are listed in Table 10-19. For ONS 15454 optics definitions, see the "Optics and 8b10b PM Parameter Definitions" section.
|
|
---|---|
OPR |
OPT |
10.3.6 Optical Service Channel Card Performance Monitoring Parameters
For ONS 15454 ANSI nodes, Figure 10-3 shows where overhead bytes detected on the ASICs produce PM parameters for the OSCM and OSC-CSM cards.
Figure 10-3 ONS 15454 ANSI Node PM Read Points on OSCM and OSC-CSM Cards
For ONS 15454 ETSI nodes, Figure 10-4 shows where overhead bytes detected on the ASICs produce PM parameters for the OSCM and OSC-CSM cards.
Figure 10-4 ONS 15454 ETSI Node PM Read Points on OSCM and OSC-CSM Cards
The ONS 15454 ANSI node PM parameters for the OSCM and OSC-CSM cards are listed in Table 10-20. For PM definitions, see the "SONET PM Parameter Definitions" section. For optics PM definitions, see the "Optics and 8b10b PM Parameter Definitions" section.
|
|
|
---|---|---|
CV-S |
CV-L |
OPWR |
1 Applicable to OC3 2 Applicable to OTS facilities |
|
|
|
---|---|---|
RS-BBE |
MS-BBE |
OPT |
10.4 Optics and 8b10b PM Parameter Definitions
Table 10-22 lists Cisco ONS 15454 optics and 8b10b PM parameter definitions.
10.5 ITU G.709 and ITU-T G.8021 Trunk-Side PM Parameter Definitions
Table 10-25 defines the ITU G.709 and ITU-T G.8021 section monitoring trunk-side PM parameters. For more information, see the "Transponder and Muxponder Card Performance Monitoring" section.
Table 10-24 defines the ITU G.709 path monitoring trunk-side PM parameters. For more information, see the "Transponder and Muxponder Card Performance Monitoring" section.
10.6 Full RMON Statistics PM Parameter Definitions
Table 10-25 defines the MXP_MR_2.5G, MXPP_MR_2.5G, TXP_MR_10E, TXP_MR_10E_C, and TXP_MR_10E_L card full RMON statistics PM parameters. For more information, see the "Transponder and Muxponder Card Performance Monitoring" section.
10.7 FEC PM Parameter Definitions
Table 10-26 defines the MXP_MR_2.5G, MXPP_MR_2.5G, TXP_MR_10E, TXP_MR_10E_C, and TXP_MR_10E_L card FEC PM parameters. For more information, see the "Transponder and Muxponder Card Performance Monitoring" section.
10.8 SONET PM Parameter Definitions
Table 10-27 gives definitions for each type of SONET PM parameter available on an ONS 15454 ANSI node. These parameters become available when the client type is set to OC-3, OC-12, or OC-48 on a TXP_MR_2.5G or TXPP_MR_2.5G card or to OC-192 on a TXP_MR_10G, TXP_MR_10E, TXP_MR_10E_C, or TXP_MR_10E_L card. The OC-48 client PM is available on MXP_2.5_10G, MXP_2.5G_10E, MXP_2.5G_10E_C, MXP_2.5G_10E_L, MXP_MR_10DME_C, and MXP_MR_10DME_L cards. The OC-48 trunk PM is available on MXP_MR_2.5G and MXPP_MR_2.5G cards.
10.9 SDH PM Parameter Definitions
Table 10-28 gives definitions for each type of SDH PM parameter available on an ONS 15454 ETSI node. These parameters become available when the client type is set to STM-1, STM-4, or STM-16 on a TXP_MR_2.5G or TXPP_MR_2.5G card or to STM-64 on a TXP_MR_10G, TXP_MR_10E, TXP_MR_10E_C, or TXP_MR_10E_L card. The STM-16 client PM is available on MXP_2.5G_10G, MXP_2.5G_10E, MXP_2.5G_10E_C, MXP_2.5G_10E_L, MXP_MR_10DME_C, and MXP_MR_10DME_L cards. The STM-16 trunk PM is available on MXP_MR_2.5G and MXPP_MR_2.5G cards.
10.10 Pointer Justification Count Performance Monitoring
For the MultiService Transport Platform (MSTP), only the MXP_2.5G_10G card uses pointer justification counts. Pointers are used to compensate for frequency and phase variations. Pointer justification counts indicate timing errors on networks. When a network is out of synchronization, jitter and wander occur on the transported signal. Excessive wander can cause terminating equipment to slip.
Slips cause different effects in service. Voice service has intermittent audible clicks. Compressed voice technology has short transmission errors or dropped calls. Fax machines lose scanned lines or experience dropped calls. Digital video transmission has distorted pictures or frozen frames. Encryption service loses the encryption key, causing data to be transmitted again.
For ONS 15454 ANSI nodes, pointers provide a way to align the phase variations in STS and VT payloads. The STS payload pointer is located in the H1 and H2 bytes of the line overhead. Clocking differences are measured by the offset in bytes from the pointer to the first byte of the STS synchronous payload envelope (SPE) called the J1 byte. Clocking differences that exceed the normal range of 0 to 782 can cause data loss.
For ONS 15454 ETSI nodes, pointers provide a way to align the phase variations in VC4 payloads. The VC4 payload pointer is located in the H1 and H2 bytes of the AU pointers section and is a count of the number of bytes the VC4 path overhead (POH) J1 byte is away from the H3 byte, not including the section overhead bytes. Clocking differences are measured by the offset in bytes from the pointer to the first byte of the VC4 POH called the J1 byte. Clocking differences that exceed the normal range of 0 to 782 can cause data loss.
There are positive (PPJC) and negative (NPJC) pointer justification count parameters. PPJC is a count of path-detected (PPJC-PDET-P) or path-generated (PPJC-PGEN-P) positive pointer justifications. NPJC is a count of path-detected (NPJC-PDET-P) or path-generated (NPJC-PGEN-P) negative pointer justifications depending on the specific PM name. PJCDIFF is the absolute value of the difference between the total number of detected pointer justification counts and the total number of generated pointer justification counts. PJCS-PDET-P is a count of the one-second intervals containing one or more PPJC-PDET or NPJC-PDET. PJCS-PGEN-P is a count of the one-second intervals containing one or more PPJC-PGEN or NPJC-PGEN.
A consistent pointer justification count indicates clock synchronization problems between nodes. A difference between the counts means that the node transmitting the original pointer justification has timing variations with the node detecting and transmitting this count. For ONS 15454 SONET nodes, positive pointer adjustments occur when the frame rate of the SPE is too slow in relation to the rate of the STS-1. For ONS 15454 SDH nodes, positive pointer adjustments occur when the frame rate of the path overhead (POH) is too slow in relation to the rate of the VC4.
In CTC, the count fields for PPJC and NPJC PMs appear white and blank unless they are enabled on the card view Provisioning tab.