- About this Manual
- Chapter 1, Shelf and Backplane Hardware
- Chapter 2, Common Control Cards
- Chapter 3, Electrical Cards
- Chapter 4, Optical Cards
- Chapter 5, Ethernet Cards
- Chapter 6, Storage Access Networking Cards
- Chapter 7, Card Protection
- Chapter 8, Cisco Transport Controller Operation
- Chapter 9, Security
- Chapter 10, Timing
- Chapter 11, Circuits and Tunnels
- Chapter 12, SONET Topologies and Upgrades
- Chapter 13, Management Network Connectivity
- Chapter 14, Alarm Monitoring and Management
- Chapter 15, Performance Monitoring
- Chapter 16, SNMP
- Appendix A, Hardware Specifications
- Appendix B, Administrative and Service States
- Appendix C, Network Element Defaults
- 15.1 Threshold Performance Monitoring
- 15.2 Intermediate Path Performance Monitoring
- 15.3 Pointer Justification Count Performance Monitoring
- 15.4 Performance Monitoring Parameter Definitions
- 15.5 Performance Monitoring for Electrical Cards
- 15.5.1 EC1-12 Card Performance Monitoring Parameters
- 15.5.2 DS1_E1_56 Card Performance Monitoring Parameters
- 15.5.3 DS1-14 and DS1N-14 Card Performance Monitoring Parameters
- 15.5.4 DS3-12 and DS3N-12 Card Performance Monitoring Parameters
- 15.5.5 DS3-12E and DS3N-12E Card Performance Monitoring Parameters
- 15.5.6 DS3i-N-12 Card Performance Monitoring Parameters
- 15.5.7 DS3XM-6 Card Performance Monitoring Parameters
- 15.5.8 DS3XM-12 Card Performance Monitoring Parameters
- 15.5.9 DS3-EC1-48 Card Performance Monitoring Parameters
- 15.6 Performance Monitoring for Ethernet Cards
- 15.7 Performance Monitoring for Optical Cards
- 15.8 Performance Monitoring for Optical Multirate Cards
- 15.9 Performance Monitoring for Storage Access Networking Cards
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 electrical cards, Ethernet cards, optical cards, optical multirate cards, and storage access networking (SAN) cards in the Cisco ONS 15454.
For information about enabling and viewing PM values, refer to the Cisco ONS 15454 Procedure Guide.
Chapter topics include:
•Threshold Performance Monitoring
•Intermediate Path Performance Monitoring
•Pointer Justification Count Performance Monitoring
•Performance Monitoring Parameter Definitions
•Performance Monitoring for Electrical Cards
•Performance Monitoring for Ethernet Cards
•Performance Monitoring for Optical Cards
•Performance Monitoring for Optical Multirate Cards
•Performance Monitoring for Storage Access Networking Cards
Note For information on PM parameters for Transponder and Muxponder cards, and DWDM cards, refer to Cisco ONS 15454 DWDM Reference Manual.
Note For additional information regarding PM parameters, refer to 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.
15.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 on provisioning card thresholds, such as line, path, and SONET thresholds, refer to the Cisco ONS 15454 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 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.
When TCAs occur, CTC displays them. An example is T-UASP-P in the Cond column (shown in Figure 15-1), where the "T-" indicates a threshold crossing. In addition, for certain electrical cards, "RX" or "TX" is appended to the TCA description, as shown (see red circles). The RX indicates that the TCA is associated with the receive direction, and TX indicates the TCA is associated with the transmit direction.
Figure 15-1 TCAs Displayed in CTC
The ONS 15454 SONET electrical cards for which RX and TX are detected and appended to the TCA descriptions are shown in Table 15-1.
Note Due to limitations of memory and the number of TCAs generated by different platforms, you can manually add/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, it 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 DS-1 installed for 911 calls must guarantee the best quality of service on the line; therefore, they lower all thresholds so that the slightest error raises a TCA.
15.2 Intermediate Path Performance Monitoring
Intermediate path performance monitoring (IPPM) allows transparent monitoring of a constituent channel of an incoming transmission signal by a node that does not terminate that channel. Many large networks only use line terminating equipment (LTE), not path terminating equipment (PTE). Table 15-2 shows ONS 15454 cards that are considered LTE.
|
|
EC1-12 card |
|
|
|
OC3 IR 4/STM1 SH 1310 |
OC3 IR/STM1 SH 1310-8 |
OC12 IR/STM4 SH1310 |
OC12 LR/STM4 LH1310 |
OC12 LR/STM4 LH 1550 |
OC12 IR/STM4 SH 1310-4 |
OC48 IR 13101 |
OC48 LR 1550 |
OC48 IR/STM16 SH AS 13101 |
OC48 LR/STM16 LH AS 1550 |
OC48 ELR/STM16 EH 100 GHz |
OC48 ELR 200 GHz |
OC192 SR/STM64 IO 1310 |
OC192 IR/STM64 SH 1550 |
OC192 LR/STM64 LH 1550 |
OC192 LR/STM64 LH ITU 15xx.xx |
TXP_MR_10G |
MXP_2.5G_10G |
MXP_MR_2.5G |
MXPP_MR_2.5G |
1 An OC-48 IR card used in a bidirectional line switched ring (BLSR) does not support IPPM during a protection switch. |
ONS 15454 Software R3.0 and higher allows LTE cards to monitor near-end PM data on individual synchronous transport signal (STS) payloads by enabling IPPM. After enabling IPPM provisioning on the line card, service providers can monitor large amounts of STS traffic through intermediate nodes, thus making troubleshooting and maintenance activities more efficient.
IPPM occurs only on STS paths that have IPPM enabled, and TCAs are raised only for PM parameters on the IPPM enabled paths. The monitored IPPM parameters are STS CV-P, STS ES-P, STS SES-P, STS UAS-P, and STS FC-P.
Note Far-end IPPM is not supported by all OC-N cards. It is supported by OC3-4 and EC-1 cards. However, SONET path PMs can be monitored by logging into the far-end node directly.
The ONS 15454 performs IPPM by examining the overhead in the monitored path and by reading all of the near-end path PM values in the incoming direction of transmission. The IPPM process allows the path signal to pass bidirectionally through the node completely unaltered.
See Table 15-3 for detailed information and definitions of specific IPPM parameters.
15.3 Pointer Justification Count Performance Monitoring
Pointers are used to compensate for frequency and phase variations. Pointer justification counts indicate timing errors on SONET 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.
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.
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. Positive pointer adjustments occur when the frame rate of the SPE is too slow in relation to the rate of the STS-1.
You must enable PPJC and NPJC performance monitoring parameters for LTE cards. See Table 15-2 for a list of Cisco ONS 15454 LTE cards. In CTC, the count fields for PPJC and NPJC PMs appear white and blank unless they are enabled on the card view Provisioning tab.
See Table 15-3 for detailed information and definitions of specific pointer justification count PM parameters.
15.4 Performance Monitoring Parameter Definitions
Table 15-3 gives definitions for each type of PM parameter found in this chapter.
15.5 Performance Monitoring for Electrical Cards
The following sections define PM parameters for the EC1-12, DS1/E1-56, DS1-14, DS1N-14, DS3-12, DS3-12E, DS3N-12, DS3N-12E, DS3i-N-12, DS3XM-6, DS3XM-12, and DS3/EC1-48 cards.
15.5.1 EC1-12 Card Performance Monitoring Parameters
Figure 15-2 shows signal types that support near-end and far-end PMs. Figure 15-3 shows where overhead bytes detected on the application specific integrated circuits (ASICs) produce PM parameters for the EC1-12 card.
Figure 15-2 Monitored Signal Types for the EC1-12 Card
Note The XX in Figure 15-2 represents all PMs listed in Table 15-4 with the given prefix and/or suffix.
Figure 15-3 PM Read Points on the EC1-12 Card
Table 15-4 lists the PM parameters for the EC1-12 cards.
Note If the CV-L(NE and FE) falls in the range 51-61 for EC1,then, the user might see discrepancy in the SES and the UAS-L values. However, ES-L will be in the nearest accuracy. For a few seconds, in a given 10 seconds interval, the number of CV-L counted may not cross the CV count criteria for SES, (due to system/application limitation for the below mentioned ranges) ;as a consequence of which there may not be 10 continuous SES, thus UAS will not be observed.
15.5.2 DS1_E1_56 Card Performance Monitoring Parameters
Figure 15-4 shows signal types that support near-end and far-end PMs.
Figure 15-4 Monitored Signal Types for the DS1/E1-56 Card
Figure 15-5 shows where overhead bytes detected on the ASICs produce PM parameters for the DS1/E1-56 card.
Figure 15-5 PM Read Points on the DS1/E1-56 Card
Table 15-5 lists the PM parameters for the DS1/E1-56 card.
15.5.3 DS1-14 and DS1N-14 Card Performance Monitoring Parameters
Figure 15-6 shows the signal types that support near-end and far-end PMs.
Figure 15-6 Monitored Signal Types for the DS1-14 and DS1N-14 Cards
Note The XX in Figure 15-6 represents all PMs listed in Table 15-6 with the given prefix and/or suffix.
Figure 15-7 shows where overhead bytes detected on the ASICs produce PM parameters for the DS1-14 and DS1N-14 cards.
Figure 15-7 PM Read Points on the DS1-14 and DS1N-14 Cards
Table 15-6 describes the PM parameters for the DS1-14 and DS1N-14 cards.
Note Far-end DS1 performance monitoring values are valid only when the DS1 line is set to extended super frame (ESF).
15.5.3.1 DS-1 Facility Data Link Performance Monitoring
Facility Data Link (FDL) performance monitoring enables an ONS 15454 DS1N-14 card to calculate and report DS-1 error rate performance measured at both the near-end and far-end of the FDL. The far-end information is reported as received on the FDL in a performance report message (PRM) from an intelligent channel service unit (CSU).
To monitor DS-1 FDL PM values, the DS-1 must be set to use ESF format and the FDL must be connected to an intelligent CSU. For procedures for provisioning ESF on the DS1N-14 card, refer to the Cisco ONS 15454 Procedure Guide.
The monitored DS-1 FDL PM parameters are CV-PFE, ES-PFE, ESA-PFE, ESB-PFE, SES-PFE, SEFS-PFE, CSS-PFE, UAS-PFE, FC-PFE, and ES-LFE. See Table 15-3 for detailed information and definitions of specific FDL DS1 PM parameters.
15.5.4 DS3-12 and DS3N-12 Card Performance Monitoring Parameters
Figure 15-8 shows the signal types that support near-end and far-end PMs. Figure 15-9 shows where overhead bytes detected on the ASICs produce PM parameters for the DS3-12 and DS3N-12 cards.
Figure 15-8 Monitored Signal Types for the DS3-12 and DS3N-12 Cards
Note The XX in Figure 15-8 represents all PMs listed in Table 15-7 with the given prefix and/or suffix.
Figure 15-9 PM Read Points on the DS3-12 and DS3N-12 Cards
The PM parameters for the DS3-12 and DS3N-12 cards are described in Table 15-7.
|
|
|
---|---|---|
CV-L |
CV-P |
CV-PFE |
15.5.5 DS3-12E and DS3N-12E Card Performance Monitoring Parameters
Figure 15-10 shows the signal types that support near-end and far-end PMs.
Figure 15-10 Monitored Signal Types for the DS3-12E and DS3N-12E Cards
Note The XX in Figure 15-10 represents all PMs listed in Table 15-8 with the given prefix and/or suffix.
Figure 15-11 shows where overhead bytes detected on the ASICs produce PM parameters for the DS3-12E and DS3N-12E cards.
Figure 15-11 PM Read Points on the DS3-12E and DS3N-12E Cards
Table 15-8 describes the PM parameters for the DS3-12E and DS3N-12E cards.
|
|
|
|
|
---|---|---|---|---|
CV-L |
AISS-P |
CV-P |
CVCP-PFE |
CV-PFE |
1 The C-bit PMs (PMs that contain the text "CP-P") are applicable only if the line format is C-bit. 2 DS3(N)-12E cards support SAS-P only on the receive (Rx) path. 3 The SASCP parameter is also displayed as "undefined" for near-end parameter though it is a far-end parameter. |
15.5.6 DS3i-N-12 Card Performance Monitoring Parameters
Figure 15-12 shows the signal types that support near-end and far-end PMs.
Figure 15-12 Monitored Signal Types for the DS3i-N-12 Cards
Note The XX in Figure 15-12 represents all PMs listed in Table 15-9 with the given prefix and/or suffix.
Figure 15-13 shows where overhead bytes detected on the ASICs produce PM parameters for the DS3i-N-12 cards.
Figure 15-13 PM Read Points on the DS3i-N-12 Cards
Table 15-9 describes the PM parameters for the DS3i-N-12 card.
|
|
|
|
|
---|---|---|---|---|
CV-L |
AISSP-P |
CV-P |
CVCP-PFE |
CV-PFE |
1 The C-Bit PMs (PMs that contain the text "CP-P") are applicable only if the line format is C-Bit. 2 DS3i-N-12 cards support SAS-P only on the Rx path. 3 The SASCP parameter is also displayed as "undefined" for near-end parameter though it is a far-end parameter. |
15.5.7 DS3XM-6 Card Performance Monitoring Parameters
Figure 15-14 shows the signal types that support near-end and far-end PMs.
Figure 15-14 Monitored Signal Types for the DS3XM-6 Card
Note The XX in Figure 15-14 represents all PMs listed in Table 15-10 with the given prefix and/or suffix.
Figure 15-15 shows where the overhead bytes detected on the ASICs produce PM parameters for the DS3XM-6 card.
Figure 15-15 PM Read Points on the DS3XM-6 Card
Table 15-10 lists the PM parameters for the DS3XM-6 cards.
|
|
|
|
|
|
|
|
|
---|---|---|---|---|---|---|---|---|
CV-L |
AISS-P |
AISS-P |
CV-V |
CV-P |
CVCP-PFE |
CV-VFE |
CV-PFE |
ES-NP ES-NPFE SES-NP SES-NPFE UAS-NP UAS-NPFE |
1 The C-Bit PMs (PMs that contain the text "CP-P") are applicable only if the line format is C-Bit. 2 Parameter received from far-end direction only. 3 DS3XM-6 cards support SAS-P only on the Rx path. 4 The SASCP parameter is also displayed as "undefined" for near-end parameter though it is a far-end parameter. |
15.5.8 DS3XM-12 Card Performance Monitoring Parameters
Figure 15-16 shows the signal types that support near-end and far-end PMs.
Figure 15-16 Monitored Signal Types for the DS3XM-12 Card
Note The XX in Figure 15-16 represents all PMs listed in Table 15-11 with the given prefix and/or suffix.
Figure 15-17 shows where the overhead bytes detected on the ASICs produce PM parameters for the DS3XM-12 card.
Figure 15-17 PM Read Points on the DS3XM-12 Card
Table 15-11 lists the PM parameters for the DS3XM-12 cards.
|
|
|
|
|
|
|
|
|
|
---|---|---|---|---|---|---|---|---|---|
CV-L |
AISS-P |
AISS-P |
CV-V |
CV-P |
CVCP-PFE |
CV-VFE |
CV-PFE |
CSS |
ES-NP ES-NPFE SES-NP SES-NPFE UAS-NP UAS-NPFE |
1 The C-Bit PMs (PMs that contain the text "CP-P") are applicable only if the line format is C-Bit. 2 Parameter received from far-end direction only. 3 DS3XM-12 cards support SAS-P only on the Rx path. 4 The SASCP parameter is also displayed as "undefined" for near-end parameter though it is a far-end parameter. |
15.5.9 DS3-EC1-48 Card Performance Monitoring Parameters
Figure 15-18 shows the signal types that support near-end and far-end PMs.
Figure 15-18 Monitored Signal Types for the DS3/ EC1-48 Card
Note The XX in Figure 15-18 represents all PMs listed in Table 15-12 with the given prefix and/or suffix.
Figure 15-19 shows where the overhead bytes detected on the ASICs produce PM parameters for the DS3-EC1-48 card.
Figure 15-19 PM Read Points on the DS3/EC1-48 Card
Table 15-12 lists the PM parameters for the DS3/EC1-48 cards.
|
|
|
|
|
---|---|---|---|---|
CV-L |
AISS-P |
CV-P |
CVCP-PFE |
CV-PFE |
1 The C-Bit PMs (PMs that contain the text "CP-P") are applicable only if the line format is C-Bit. 2 DS3/EC1-48 cards support SAS-P only on the Rx path. 3 The SASCP parameter is also displayed as "undefined" for near-end parameter though it is a far-end parameter. |
Note If the CV-L(NE and FE) falls in the range 51-61 for DS3,then, the user might see discrepancy in the SES and the UAS-L values. However, ES-L will be in the nearest accuracy. For a few seconds, in a given 10 seconds interval, the number of CV-L counted may not cross the CV count criteria for SES, (due to system/application limitation for the below mentioned ranges); as a consequence of which there may not be 10 continuous SES, thus UAS will not be observed.
15.6 Performance Monitoring for Ethernet Cards
The following sections define PM parameters and definitions for the ONS 15454 E-Series, G-Series, ML-Series, and CE-Series Ethernet cards.
15.6.1 E-Series Ethernet Card Performance Monitoring Parameters
CTC provides Ethernet performance information, including line-level parameters, port bandwidth consumption, and historical Ethernet statistics. The E-Series Ethernet performance information is divided into the Statistics, Utilization, and History tabbed windows within the card view Performance tab window.
15.6.1.1 E-Series Ethernet Statistics Window
The Ethernet Statistics window lists Ethernet parameters at the line level. The Statistics window provides buttons to change the statistical values shown. The Baseline button resets the displayed statistics values to zero. The Refresh button manually refreshes statistics. Auto-Refresh sets a time interval at which automatic refresh occurs.
Table 15-13 defines the E-Series Ethernet card statistics parameters.
15.6.1.2 E-Series Ethernet Utilization Window
The Utilization window shows the percentage of transmit (Tx) and receive (Rx) line bandwidth used by the Ethernet ports during consecutive time segments. The Mode field displays the real-time mode status, such as 100 Full, which is the mode setting configured on the E-Series port. However, if the E-Series port is set to autonegotiate the mode (Auto), this field shows the result of the link negotiation between the E-Series and the peer Ethernet device attached directly to the E-Series port.
The Utilization window provides an Interval drop-down list that enables you to set time intervals of 1 minute, 15 minutes, 1 hour, and 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 Ethernet port (that is, 1 Gbps). The maxBaseRate for E-Series Ethernet cards is shown in Table 15-14.
|
|
---|---|
STS-1 |
51840000 |
STS-3c |
155000000 |
STS-6c |
311000000 |
STS-12c |
622000000 |
Note Line utilization numbers express the average of ingress and egress traffic as a percentage of capacity.
Note The E-Series Ethernet card is a Layer 2 device or switch and supports Trunk Utilization statistics. The Trunk Utilization statistics are similar to the Line Utilization statistics, but shows the percentage of circuit bandwidth used rather than the percentage of line bandwidth used. The Trunk Utilization statistics are accessed through the card view Maintenance tab.
15.6.1.3 E-Series Ethernet History Window
The Ethernet History window lists past Ethernet statistics for the previous time intervals. 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 15-15. The parameters are defined in Table 15-13.
|
|
---|---|
1 minute |
60 |
15 minutes |
32 |
1 hour |
24 |
1 day (24 hours) |
7 |
15.6.2 G-Series Ethernet Card Performance Monitoring Parameters
CTC provides Ethernet performance information, including line-level parameters, port bandwidth consumption, and historical Ethernet statistics. The G-Series Ethernet performance information is divided into the Statistics, Utilization, and History tabbed windows within the card view Performance tab window.
15.6.2.1 G-Series Ethernet Statistics Window
The Ethernet Statistics window lists Ethernet parameters at the line level. The Statistics window provides buttons to change the statistical values shown. The Baseline button resets the displayed statistics values to zero. The Refresh button manually refreshes statistics. Auto-Refresh sets a time interval at which automatic refresh occurs. The G-Series Statistics window also has a Clear button. The Clear button sets the values on the card to zero, but does not reset the G-Series card.
Table 15-16 defines the G-Series Ethernet card statistics parameters.
|
|
---|---|
Time Last Cleared |
A time stamp indicating the last time statistics were reset. |
Link Status |
Indicates whether the Ethernet link is receiving a valid Ethernet signal (carrier) from the attached Ethernet device; up means present, and down means not present. |
Rx Packets |
Number of packets received since the last counter reset. |
Rx Bytes |
Number of bytes received since the last counter reset. |
Tx Packets |
Number of packets transmitted since the last counter reset. |
Tx Bytes |
Number of bytes transmitted since the last counter reset. |
Rx Total Errors |
Total number of receive errors. |
Rx FCS |
Number of packets with a FCS error. FCS errors indicate frame corruption during transmission. |
Rx Alignment |
Number of packets with received incomplete frames. |
Rx Runts |
Measures undersized packets with bad CRC errors. |
Rx Shorts |
Measures undersized packets with good CRC errors. |
Rx Jabbers |
The total number of frames received that exceed the 1548-byte maximum and contain CRC errors. |
Rx Giants |
Number of packets received that are greater than 1530 bytes in length. |
Rx Pause Frames |
Number of received Ethernet IEEE 802.3z pause frames. |
Tx Pause Frames |
Number of transmitted IEEE 802.3z pause frames. |
Rx Pkts Dropped Internal Congestion |
Number of received packets dropped due to overflow in G-Series frame buffer. |
Tx Pkts Dropped Internal Congestion |
Number of transmit queue drops due to drops in the G-Series frame buffer. |
HDLC Errors |
High-level data link control (HDLC) errors received from SONET/SDH (see Note). |
Rx Unicast Packets |
Number of unicast packets received since the last counter reset. |
Tx Unicast Packets |
Number of unicast packets transmitted. |
Rx Multicast Packets |
Number of multicast packets received since the last counter reset. |
Tx Multicast Packets |
Number of multicast packets transmitted. |
Rx Broadcast Packets |
Number of broadcast packets received since the last counter reset. |
Tx Broadcast Packets |
Number or broadcast packets transmitted. |
Note Do not use the HDLC errors counter to count the number of frames dropped because of HDLC errors, because each frame can fragment into several smaller frames during HDLC error conditions and spurious HDLC frames can be generated. If HDLC error counters are incrementing when no SONET path problems should be present, it might indicate a problem with the quality of the SONET path. For example, a SONET protection switch generates a set of HDLC errors. However, the actual values of these counters are less significant than the fact that they are changing.
15.6.2.2 G-Series Ethernet Utilization Window
The Utilization window shows the percentage of Tx and Rx line bandwidth used by the Ethernet ports during consecutive time segments. The Mode field displays the real-time mode status, such as 100 Full, which is the mode setting configured on the G-Series port. However, if the G-Series port is set to autonegotiate the mode (Auto), this field shows the result of the link negotiation between the G-Series and the peer Ethernet device attached directly to the G-Series port.
The Utilization window provides an Interval drop-down list that enables you to set time intervals of 1 minute, 15 minutes, 1 hour, and 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 Ethernet port (that is, 1 Gbps). The maxBaseRate for G-Series Ethernet cards is shown in Table 15-14.
Note Line utilization numbers express the average of ingress and egress traffic as a percentage of capacity.
Note Unlike the E-Series, the G-Series card does not have a display of Trunk Utilization statistics, because the G-Series card is not a Layer 2 device or switch.
15.6.2.3 G-Series Ethernet History Window
The Ethernet History window lists past Ethernet statistics for the previous time intervals. 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 15-15. The listed parameters are defined in Table 15-16.
15.6.3 ML-Series Ethernet Card Performance Monitoring Parameters
CTC provides Ethernet performance information for line-level parameters and historical Ethernet statistics. The ML-Series Ethernet performance information is divided into the Ether Ports and Packet-over-SONET (POS) Ports tabbed windows within the card view Performance tab window.
15.6.3.1 ML-Series Ether Ports Window
Table 15-17 defines the ML-Series Ethernet card Ether Ports PM parameters.
15.6.3.2 ML-Series POS Ports Window
In the ML-Series POS Ports window, the parameters displayed depend on the framing mode employed by the ML-Series card. The two framing modes for the POS port on the ML-Series card are HDLC and frame-mapped generic framing procedure (GFP-F). For more information on provisioning a framing mode, refer to Cisco ONS 15454 Procedure Guide.
Table 15-18 defines the ML-Series Ethernet card POS Ports HDLC parameters. Table 15-19 defines the ML-Series Ethernet card POS Ports GFP-F parameters.
15.6.4 CE-Series Ethernet Card Performance Monitoring Parameters
CTC provides Ethernet performance information, including line-level parameters, port bandwidth consumption, and historical Ethernet statistics. The CE-Series card Ethernet performance information is divided into Ether Ports and POS Ports tabbed windows within the card view Performance tab window.
15.6.4.1 CE-Series Card Ether Port Statistics Window
The Ethernet Ether Ports Statistics window lists Ethernet parameters at the line level. The Statistics window provides buttons to change the statistical values shown. The Baseline button resets the displayed statistics values to zero. The Refresh button manually refreshes statistics. Auto-Refresh sets a time interval at which automatic refresh occurs. The CE-Series Statistics window also has a Clear button. The Clear button sets the values on the card to zero, but does not reset the CE-Series card.
During each automatic cycle, whether auto-refreshed or manually refreshed (using the Refresh button), statistics are added cumulatively and are not immediately adjusted to equal total received packets until testing ends. To see the final PM count totals, allow a few moments for the PM window statistics to finish testing and update fully. PM counts are also listed in the CE-Series card Performance > History window.
Table 15-20 defines the CE-Series card Ethernet port parameters.
|
|
---|---|
Time Last Cleared |
A time stamp indicating the last time statistics were reset. |
Link Status |
Indicates whether the Ethernet link is receiving a valid Ethernet signal (carrier) from the attached Ethernet device; up means present, and down means not present. |
ifInOctets |
Number of bytes received since the last counter reset. |
rxTotalPkts |
Number of received packets. |
ifInUcastPkts |
Number of unicast packets received since the last counter reset. |
ifInMulticastPkts |
Number of multicast packets received since the last counter reset. |
ifInBroadcastPkts |
Number of broadcast packets received since the last counter reset. |
ifInDiscards |
The number of inbound packets that were chosen to be discarded even though no errors had been detected to prevent their being deliverable to a higher-layer protocol. One possible reason for discarding such a packet could be to free buffer space. |
ifInErrors |
The number of inbound packets (or transmission units) that contained errors preventing them from being deliverable to a higher-layer protocol. |
ifOutOctets |
Number of bytes transmitted since the last counter reset. |
txTotalPkts |
Number of transmitted packets. |
ifOutDiscards1 |
Number of outbound packets which were chosen to be discarded even though no errors had been detected to prevent their transmission. A possible reason for discarding such packets could be to free up buffer space. |
ifOutErrors1 |
Number of outbound packets or transmission units that could not be transmitted because of errors. |
ifOutUcastPkts2 |
Number of unicast packets transmitted. |
ifOutMulticastPkts2 |
Number of multicast packets transmitted. |
ifOutBroadcastPkts2 |
Number of broadcast packets transmitted. |
dot3StatsAlignment |
A count of frames received on a particular interface that are not an integral number of octets in length and do not pass the FCS check. |
dot3StatsFCSErrors |
A count of frames received on a particular interface that are an integral number of octets in length but do not pass the FCS check. |
dot3StatsSingleCollisionFrames2 |
A count of successfully transmitted frames on a particular interface for which transmission is inhibited by exactly on collision. |
dot3StatsFrameTooLong |
A count of frames received on a particular interface that exceed the maximum permitted frame size. |
etherStatsUndersizePkts |
The total number of packets received that were less than 64 octets long (excluding framing bits, but including FCS octets) and were otherwise well formed. |
etherStatsFragments |
The total number of packets received that were less than 64 octets in length (excluding framing bits but including FCS octets) and had either a bad FCS with an integral number of octets (FCS Error) or a bad FCS with a nonintegral number of octets (Alignment Error). Note It is entirely normal for etherStatsFragments to increment. This is because it counts both runts (which are normal occurrences due to collisions) and noise hits. |
etherStatsPkts64Octets |
The total number of packets (including bad packets) received that were 64 octets in length (excluding framing bits but including FCS octets). |
etherStatsPkts65to127 |
The total number of packets (including bad packets) received that were between 65 and 127 octets in length inclusive (excluding framing bits but including FCS octets). |
etherStatsPkts128to255 |
The total number of packets (including bad packets) received that were between 128 and 255 octets in length inclusive (excluding framing bits but including FCS octets). |
etherStatsPkts256to511 |
The total number of packets (including bad packets) received that were between 256 and 511 octets in length inclusive (excluding framing bits but including FCS octets). |
etherStatsPkts512to1023Octets |
The total number of packets (including bad packets) received that were between 512 and 1023 octets in length inclusive (excluding framing bits but including FCS octets). |
etherStatsPkts1024to1518Octets |
The total number of packets (including bad packets) received that were between 1024 and 1518 octets in length inclusive (excluding framing bits but including FCS octets). |
etherStatsBroadcastPkts |
The total number of good packets received that were directed to the broadcast address. Note that this does not include multicast packets. |
etherStatsMulticastPkts |
The total number of good packets received that were directed to a multicast address. Note that this number does not include packets directed to the broadcast address. |
etherStatsOversizePkts |
The total number of packets received that were longer than 1518 octets (excluding framing bits, but including FCS octets) and were otherwise well formed. Note that for tagged interfaces, this number becomes 1522 bytes. |
etherStatsJabbers |
The total number of packets received that were longer than 1518 octets (excluding framing bits, but including FCS octets), and had either a bad FCS with an integral number of octets (FCS Error) or a bad FCS with a nonintegral number of octets (Alignment Error). |
etherStatsOctets |
The total number of octets of data (including those in bad packets) received on the network (excluding framing bits but including FCS octets |
etherStatsCollisions2 |
Number of transmit packets that are collisions; the port and the attached device transmitting at the same time caused collisions. |
etherStatsCRCAlign |
The total number of packets received that had a length (excluding framing bits, but including FCS octets) of between 64 and 1518 octets, inclusive, but had either a bad FCS with an integral number of octets (FCS Error) or a bad FCS with a nonintegral number of octets (Alignment Error). |
etherStatsDropEvents2 |
Number of received frames dropped at the port level. |
rxPauseFrames1 |
Number of received pause frames. |
txPauseFrames1 |
Number of transmitted pause frames. |
rxPktsDroppedInternalCongestion1 |
Number of received packets dropped due to overflow in frame buffer. |
txPktsDroppedInternalCongestion1 |
Number of transmit queue drops due to drops in frame buffer. |
rxControlFrames1 |
Number of received control frames. |
mediaIndStatsRxFramesTruncated1 |
Number of received frames with length of 36 bytes or less. |
mediaIndStatsRxFramesTooLong1 |
Number of received frames that are too long. The maximum is the programmed maximum frame size (for VSAN support); if the maximum frame size is set to default, then the maximum is the 2112 byte payload plus the 36 byte header, which is a total of 2148 bytes. |
mediaIndStatsRxFramesBadCRC1 |
Number of received frames with CRC error. |
mediaIndStatsTxFramesBadCRC1 |
Number of transmitted frames with CRC error. |
mediaIndStatsRxShortPkts1 |
Number of received packets that are too small. |
1 For CE1000-4 only 2 For CE100T-8 only |
15.6.4.2 CE-Series Card Ether Ports Utilization Window
The Ether Ports Utilization window shows the percentage of Tx and Rx line bandwidth used by the Ethernet ports during consecutive time segments. The Utilization window provides an Interval drop-down list that enables you to set time intervals of 1 minute, 15 minutes, 1 hour, and 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 Ethernet port (that is, 1 Gbps). The maxBaseRate for CE-Series Ethernet cards is shown in Table 15-14.
Note Line utilization numbers express the average of ingress and egress traffic as a percentage of capacity.
15.6.4.3 CE-Series Card Ether Ports History Window
The Ethernet Ether Ports History window lists past Ethernet statistics for the previous time intervals. 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 15-15. The listed parameters are defined in Table 15-16.
15.6.4.4 CE-Series Card POS Ports Statistics Parameters
The Ethernet POS Ports statistics window lists Ethernet POS parameters at the line level. Table 15-21 defines the CE-Series Ethernet card POS Ports parameters.
|
|
---|---|
Time Last Cleared |
A time stamp indicating the last time that statistics were reset. |
Link Status |
Indicates whether the Ethernet link is receiving a valid Ethernet signal (carrier) from the attached Ethernet device; up means present, and down means not present. |
ifInOctets |
Number of bytes received since the last counter reset. |
rxTotalPkts |
Number of received packets. |
ifInDiscards1 |
The number of inbound packets that were chosen to be discarded even though no errors had been detected to prevent their being deliverable to a higher-layer protocol. One possible reason for discarding such a packet could be to free buffer space. |
ifInErrors1 |
The number of inbound packets (or transmission units) that contained errors preventing them from being deliverable to a higher-layer protocol. |
ifOutOctets |
Number of bytes transmitted since the last counter reset. |
txTotalPkts |
Number of transmitted packets. |
ifOutOversizePkts1 |
Packets greater than 1518 bytes transmitted out a port. |
gfpStatsRxFrame2 |
Number of received GFP frames. |
gfpStatsTxFrame2 |
Number of transmitted GFP frames. |
gfpStatsRxCRCErrors |
Number of packets received with a payload FCS error. |
gfpStatsRxOctets2 |
Number of GFP bytes received. |
gfpStatsTxOctets2 |
Number of GFP bytes transmitted. |
gfpStatsRxSBitErrors |
Sum of all the single bit errors. In the GFP CORE HDR at the GFP-T receiver, these are correctable. |
gfpStatsRxMBitErrors |
Sum of all the multiple bit errors. In the GFP CORE HDR at the GFP-T receiver, these are uncorrectable. |
gfpStatsRxTypeInvalid |
Number of receive packets dropped due to Client Data Frame UPI errors. |
gfpStatsRxCIDInvalid1 |
Number of packets with invalid CID. |
gfpStatsCSFRaised |
Number of GFP Client signal fail frames detected at the GFP-T receiver. |
ifInPayloadCrcErrors1 |
Received payload CRC errors. |
ifOutPayloadCrcErrors1 |
Transmitted payload CRC errors. |
hdlcPktDrops |
Number of received packets dropped before input. |
1 Applicable only for CE100T-8 2 Applicable only for CE1000-4 |
15.6.4.5 CE-Series Card POS Ports Utilization Window
The POS Ports Utilization window shows the percentage of Tx and Rx line bandwidth used by the POS ports during consecutive time segments. The Utilization window provides an Interval drop-down list that enables you to set time intervals of 1 minute, 15 minutes, 1 hour, and 1 day. Line utilization is calculated with the following formulas:
Rx = (inOctets * 8) / (interval * maxBaseRate)
Tx = (outOctets * 8) / (interval * maxBaseRate)
The interval is defined in seconds. The maxBaseRate is defined by raw bits per second in one direction for the Ethernet port (that is, 1 Gbps). The maxBaseRate for CE-Series cards is shown in Table 15-14.
Note Line utilization numbers express the average of ingress and egress traffic as a percentage of capacity.
15.6.4.6 CE-Series Card Ether Ports History Window
The Ethernet POS Ports History window lists past Ethernet POS ports statistics for the previous time intervals. 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 15-15. The listed parameters are defined in Table 15-20.
15.7 Performance Monitoring for Optical Cards
This section lists PM parameters for ONS 15454 optical cards, including the OC-3, OC-12, OC-48, and OC-192 cards. Figure 15-20 shows the signal types that support near-end and far-end PMs.
Figure 15-20 Monitored Signal Types for the OC-3 Cards
Note The XX in Figure 15-20 represents all PMs listed in Table 15-22, Table 15-23, and Table 15-24 with the given prefix and/or suffix.
Figure 15-21 shows where overhead bytes detected on the ASICs produce PM parameters for the OC3 IR 4 SH 1310 and OC3 IR SH 1310-8 cards.
Figure 15-21 PM Read Points on the OC-3 Cards
Note For PM locations relating to protection switch counts, see the Telcordia GR-253-CORE document.
Table 15-22 and Table 15-23 list the PM parameters for OC-3 cards.
|
|
|
|
|
---|---|---|---|---|
CV-S |
CV-L |
CV-P |
CV-LFE |
CV-PFE |
1 The STS Path (FE) PMs are valid only for the OC3-4 card on ONS 15454. |
Table 15-24 lists the PM parameters for OC-12, OC-48, and OC-192 cards.
Note If the CV-L(NE and FE) falls in a specific range, then, the user might see discrepancy in the SES and the UAS-L values. However, ES-L will be in the nearest accuracy. For a few seconds, in a given 10 seconds interval, the number of CV-L counted may not cross the CV count criteria for SES, (due to system/application limitation for the below mentioned ranges); as a consequence of which there may not be 10 continuous SES, thus UAS will not be observed. The corresponding (error) range for the line rates is as shown in Table 15-25.
|
|
---|---|
OC3 |
154-164 |
OC12 |
615-625 |
OC48 |
2459-2470 |
OC192 |
9835-9845 |
15.8 Performance Monitoring for Optical Multirate Cards
This section lists PM parameters for the optical mutirate card, also known as the MRC-12 card.
Figure 15-22 shows where overhead bytes detected on the ASICs produce PM parameters for the MRC-12 card.
Figure 15-22 PM Read Points for the MRC-12 Card
Table 15-26 lists the PM parameters for MRC-12 card.
15.9 Performance Monitoring for Storage Access Networking Cards
The following sections define PM parameters and definitions for the SAN card, also known as the FC_MR-4 or Fibre Channel card.
CTC provides FC_MR-4 performance information, including line-level parameters, port bandwidth consumption, and historical statistics. The FC_MR-4 card performance information is divided into the Statistics, Utilization, and History tabbed windows within the card view Performance tab window.
15.9.1 FC_MR-4 Statistics Window
The Statistics window lists parameters at the line level. The Statistics window provides buttons to change the statistical values shown. The Baseline button resets the displayed statistics values to zero. The Refresh button manually refreshes statistics. Auto-Refresh sets a time interval at which automatic refresh occurs. 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. Table 15-27 defines the FC_MR-4 card statistics parameters.
15.9.2 FC_MR-4 Utilization Window
The Utilization window shows the percentage of Tx and Rx line bandwidth used by the ports during consecutive time segments. The Utilization window provides an Interval drop-down list that enables you to set time intervals of 1 minute, 15 minutes, 1 hour, and 1 day. Line utilization is calculated with the following formulas:
Rx = (inOctets + inPkts * 24) * 8 / 100% interval * maxBaseRate
Tx = (outOctets + outPkts * 24) * 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 or 2 Gbps). The maxBaseRate for FC_MR-4 cards is shown in Table 15-28.
|
|
---|---|
STS-24 |
850000000 |
STS-48 |
850000000 x 21 |
1 For 1 Gbps of bit rate being transported, there are only 850 Mbps of actual data because of 8b->10b conversion. Similarly, for 2 Gbps of bit rate being transported, there are only 1700 Mbps (850 Mbps x 2) of actual data. |
Note Line utilization numbers express the average of ingress and egress traffic as a percentage of capacity.
15.9.3 FC_MR-4 History Window
The History window lists past FC_MR-4 statistics for the previous time intervals. 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 15-29. The listed parameters are defined in Table 15-27.