Table Of Contents
Monitor Performance
Before You Begin
NTP-B73 Enable Performance Monitoring
DLP-B121 Enable Pointer Justification Count Performance Monitoring
DLP-B122 Enable Intermediate-Path Performance Monitoring
NTP-B195 Monitor Electrical or Optical Performance
DLP-B123 View Electrical PM Parameters
DLP-B261 Refresh PM Counts for a Different Port
DLP-B124 Refresh Electrical or Optical PM Counts at Fifteen-Minute Intervals
DLP-B318 Refresh Electrical or Optical PM Counts at One-Day Intervals
DLP-B126 Monitor Near-End PM Counts
DLP-B127 Monitor Far-End PM Counts
DLP-B129 Reset Current PM Counts
DLP-B130 Clear Selected PM Counts
DLP-B260 Set Auto Refresh Interval for Displayed PM Counts
DLP-B317 View Optical OC-N PM Parameters
DLP-B319 Monitor PM Counts for Selected Signal Types
NTP-B198 Monitor Ethernet Performance
DLP-B256 View Ethernet Statistics PM Parameters
DLP-B257 View Ethernet Utilization PM Parameters
DLP-B259 Refresh Ethernet PM Counts at a Different Time Interval
DLP-B258 View Ethernet History PM Parameters
NTP-B235 Create or Delete Ethernet RMON Thresholds
DLP-B334 Create Ethernet RMON Alarm Thresholds
DLP-B335 Delete Ethernet RMON Alarm Thresholds
Monitor Performance
Performance monitoring (PM) parameters are used by service providers to gather, store, threshold, and report performance data for early detection of problems. For more PM information, details, and definitions refer to the Cisco ONS 15327 Reference Manual. This chapter explains how to enable and view performance monitoring statistics for the Cisco ONS 15327.
Before You Begin
Before performing any of the following procedures, investigate all alarms and clear any trouble conditions. Refer to the Cisco ONS 15327 Troubleshooting Guide as necessary.
This section lists the chapter procedures (NTPs). Turn to a procedure for applicable tasks (DLPs).
1. 
B73 Enable Performance Monitoring—Complete as needed.
2. B195 Monitor Electrical or Optical Performance—Complete as needed.
3. B198 Monitor Ethernet Performance—Complete as needed.
4. B235 Create or Delete Ethernet RMON Thresholds—Complete as needed.
Note For additional information regarding PM parameters, refer to the Digital transmission surveillance section in Telcordia's GR-1230-CORE, GR-820-CORE, GR-499-CORE, and GR-253-CORE documents, and in the ANSI document entitled Digital Hierarchy - Layer 1 In-Service Digital Transmission Performance Monitoring.
NTP-B73 Enable Performance Monitoring
Purpose
|
This procedure enables performance monitoring.
|
Tools/Equipment
|
None
|
Prerequisite Procedures
|
None
|
Required/As Needed
|
As needed
|
Onsite/Remote
|
Onsite or remote
|
Security Level
|
Provisioning or higher
|
Step 1 Complete the "DLP-B60 Log into CTC" task at the node you want to monitor. If you are already logged in, continue with Step 2.
Step 2 Complete the "DLP-B121 Enable Pointer Justification Count Performance Monitoring" task if you need to monitor clock synchronization.
Step 3 Complete the "DLP-B122 Enable Intermediate-Path Performance Monitoring" task if you need to monitor large amounts of STS traffic through intermediate nodes.
Stop. You have completed this procedure.
DLP-B121 Enable Pointer Justification Count Performance Monitoring
Purpose
|
This task enables pointer justification counts, which provide a way to align the phase variations in STS and VT payloads and to monitor the clock synchronization between nodes. A consistent, large pointer justification count indicates clock synchronization problems between nodes.
|
Tools/Equipment
|
None
|
Prerequisite Procedures
|
B60 Log into CTC
|
Required/As Needed
|
As needed
|
Onsite/Remote
|
Onsite or remote
|
Security Level
|
Provisioning or higher
|
Step 1 In node view, double-click the card where the line terminates (drops), called a line-terminating equipment (LTE) card. The card view appears.
Table 7-1 lists the Cisco ONS 15327 LTE cards.
Table 7-1 Traffic Cards that Terminate the Line (LTEs)
Line Terminating Equipment
|
OC3 IR 1310
|
OC12 IR 1310
|
OC12 LR 1550
|
OC48 IR 1310
|
OC48 LR 1550
|
|
Step 2 Click the Provisioning > Line tabs.
Step 3 Click the PJStsMon# menu and make a selection based on the following rules:
•The default value Off means pointer justification monitoring is disabled.
•The values 1 to N are the number of STSs on the port. One STS per port can be enabled from the PJStsMon# card menu.
Figure 7-1 shows the PJStsMon# menu on the Provisioning window.
Figure 7-1 Line Tab for Enabling Pointer Justification Count Parameters
Step 4 In the State field, confirm that the port is in service (IS).
Step 5 If the port is IS, click Apply and go to Step 7.
Step 6 If the port is out of service (OOS, OOS_MT, OOS_AINS), select IS in the State field and click Apply.
Step 7 Click the Performance tab to view PM parameters. Figure 7-2 shows pointer justification counts. Refer to the Cisco ONS 15327 Reference Manual for more PM information, details, and definitions.
Note In CTC, the count fields for PPJC and NPJC PM parameters appear white and blank unless they are enabled on the Provisioning > Line tabs.
Figure 7-2 Viewing Pointer Justification Counts
Step 8 Return to your originating procedure (NTP).
DLP-B122 Enable Intermediate-Path Performance Monitoring
Purpose
|
This task enables intermediate-path performance monitoring (IPPM), which allows you to monitor large amounts of STS traffic through intermediate nodes.
|
Tools/Equipment
|
None
|
Prerequisite Procedures
|
B60 Log into CTC
|
Required/As Needed
|
As needed
|
Onsite/Remote
|
Onsite or remote
|
Security Level
|
Provisioning or higher
|
Note The monitored IPPM parameters are STS CV-P, STS ES-P, STS SES-P, STS UAS-P, and STS FC-P. For more information about IPPM parameters, refer to the Cisco ONS 15327 Reference Manual.
Step 1 In node view, double-click the LTE card you want to monitor. The card view appears.
See Table 7-1 for a list of Cisco ONS 15327 LTE cards.
Step 2 Click the Provisioning tab.
Step 3 Click the SONET STS tab. Figure 7-3 shows the SONET STS tab in the Provisioning window.
Figure 7-3 SONET STS Tab for Enabling IPPM
Step 4 Check the check box in the Enable IPPM column for the STS you want to monitor.
Step 5 Click Apply.
Step 6 Click the Performance tab to view PM parameters. For IPPM parameter definitions, refer to the Cisco ONS 15327 Reference Manual.
Step 7 Return to your originating procedure (NTP).
NTP-B195 Monitor Electrical or Optical Performance
Purpose
|
The Performance Monitoring window allows you to view node near-end or far-end performance on a selected card and port at specified time intervals to detect possible performance problems.
|
Tools/Equipment
|
None
|
Prerequisite Procedures
|
Before you monitor performance, be sure you have created the appropriate circuits and provisioned the card according to your specifications. For more information, see "Create Circuits and VT Tunnels" and "Change Port Settings."
|
Required/As Needed
|
As needed
|
Onsite/Remote
|
Onsite or remote
|
Security Level
|
Retrieve or higher
|
Step 1 Complete the "DLP-B60 Log into CTC" task at the node you want to monitor. If you are already logged in, continue to Step 2.
Step 2 Complete the "DLP-B123 View Electrical PM Parameters" task as needed.
Step 3 As needed, use the following tasks to change the display of electrical PM counts:
•B261 Refresh PM Counts for a Different Port
•B124 Refresh Electrical or Optical PM Counts at Fifteen-Minute Intervals
•B318 Refresh Electrical or Optical PM Counts at One-Day Intervals
•B319 Monitor PM Counts for Selected Signal Types
•B126 Monitor Near-End PM Counts
•B127 Monitor Far-End PM Counts
•B129 Reset Current PM Counts
•B130 Clear Selected PM Counts
•B260 Set Auto Refresh Interval for Displayed PM Counts
Step 4 Complete the "DLP-B317 View Optical OC-N PM Parameters" task as needed.
Step 5 As needed, use the following tasks to change the display of optical PM counts:
•B261 Refresh PM Counts for a Different Port
•B124 Refresh Electrical or Optical PM Counts at Fifteen-Minute Intervals
•B318 Refresh Electrical or Optical PM Counts at One-Day Intervals
•B126 Monitor Near-End PM Counts
•B127 Monitor Far-End PM Counts
•B319 Monitor PM Counts for Selected Signal Types
•B129 Reset Current PM Counts
•B130 Clear Selected PM Counts
•B260 Set Auto Refresh Interval for Displayed PM Counts
•B319 Monitor PM Counts for Selected Signal Types
Stop. You have completed this procedure.
DLP-B123 View Electrical PM Parameters
Purpose
|
This task enables you to view DS-1 or DS-3 PM counts on an XTC card to detect possible performance problems.
|
Tools/Equipment
|
None
|
Prerequisite Procedures
|
B60 Log into CTC
|
Required/As Needed
|
As needed
|
Onsite/Remote
|
Onsite or remote
|
Security Level
|
Retrieve or higher
|
Step 1 In node view, double-click an XTC card. The card view appears.
Step 2 Click the Performance tab (Figure 7-4).
Figure 7-4 Viewing Electrical Performance Monitoring Information
Step 3 Click the DS1 tab or DS3 tab to view the desired PM parameters.
The PM parameter names appear on the left portion of the window in the Param column. The PM values appear on the right portion of the window in the Curr (current) and Prev-n (previous) columns. For PM parameter definitions, refer to the Cisco ONS 15327 Reference Manual.
Step 4 Return to your originating procedure (NTP).
DLP-B261 Refresh PM Counts for a Different Port
Purpose
|
This task changes the window view to display PM counts for another port on a multiport card.
|
Tools/Equipment
|
None
|
Prerequisite Procedures
|
B60 Log into CTC
|
Required/As Needed
|
As needed
|
Onsite/Remote
|
Onsite or remote
|
Security Level
|
Retrieve or higher
|
Step 1 In node view, double-click an XTC card (for electrical PM counts) or an OC-N card. The card view appears.
Step 2 Click the Performance tab.
Step 3 From the Port drop-down menu, choose the desired port to highlight your selection.
Step 4 Click Refresh. The PM counts for the newly selected port appear.
Step 5 Return to your originating procedure (NTP).
DLP-B124 Refresh Electrical or Optical PM Counts at Fifteen-Minute Intervals
Purpose
|
This task changes the window view to display PM counts in 15-minute intervals.
|
Tools/Equipment
|
None
|
Prerequisite Procedures
|
B60 Log into CTC
|
Required/As Needed
|
As needed
|
Onsite/Remote
|
Onsite or remote
|
Security Level
|
Retrieve or higher
|
Step 1 In node view, double-click an XTC card (for electrical PM counts) or an OC-N card. The card view appears.
Step 2 Click the Performance tab.
Step 3 Click the 15 min radio button.
Step 4 Click Refresh. Performance monitoring parameters appear in 15-minute intervals synchronized with the time of day.
Step 5 View the Curr column to find PM counts for the current 15-minute interval.
Each monitored performance parameter has corresponding threshold values for the current time period. If the value of the counter exceeds the threshold value for a particular 15-minute interval, a threshold crossing alert (TCA) is raised. The PM number represents the counter value for each specific performance monitoring parameter.
Step 6 View the Prev-n columns to find PM counts for the previous 15-minute intervals.
Note If a complete 15-minute interval count is not possible, the value appears with a yellow background. An incomplete or incorrect count can be caused by monitoring for less than 15 minutes after the counter started, changing node timing settings, changing the time zone settings, replacing a card, resetting a card, or changing port states. When the problem is corrected, the subsequent 15-minute interval appears with a white background.
Step 7 Return to your originating procedure (NTP).
DLP-B318 Refresh Electrical or Optical PM Counts at One-Day Intervals
Purpose
|
This task changes the window to display PM parameters in 1-day intervals.
|
Tools/Equipment
|
None
|
Prerequisite Procedures
|
B60 Log into CTC
|
Required/As Needed
|
As needed
|
Onsite/Remote
|
Onsite or remote
|
Security Level
|
Retrieve or higher
|
Step 1 In node view, double-click an XTC card (for electrical PM counts) or an OC-N card. The card view appears.
Step 2 Click the Performance tab.
Step 3 Click the 1 day radio button.
Step 4 Click Refresh. Performance monitoring appears in 1-day intervals synchronized with the time of day.
Step 5 View the Curr column to find PM counts for the current 1-day interval.
Each monitored performance parameter has corresponding threshold values for the current time period. If the value of the counter exceeds the threshold value for a particular 1-day interval, a TCA is raised. The PM number represents the counter value for each performance monitoring parameter.
Step 6 View the Prev-n columns to find PM counts for the previous 1-day intervals.
Note If a complete count over a 1-day interval is not possible, the value appears with a yellow background. An incomplete or incorrect count can be caused by monitoring for less than 24 hours after the counter started, changing node timing settings, changing the time zone settings, replacing a card, resetting a card, or changing port states. When the problem is corrected, the subsequent 1-day interval appears with a white background.
Step 7 Return to your originating procedure (NTP).
DLP-B126 Monitor Near-End PM Counts
Purpose
|
This task enables you to view near-end PM counts for the selected card and port.
|
Tools/Equipment
|
None
|
Prerequisite Procedures
|
B60 Log into CTC
|
Required/As Needed
|
As needed
|
Onsite/Remote
|
Onsite or remote
|
Security Level
|
Retrieve or higher
|
Step 1 In node view, double-click an XTC card (for electrical PM counts) or an OC-N card. The card view appears.
Step 2 Click the Performance tab.
Step 3 Click the Near End radio button.
Step 4 Click Refresh. All PM parameters for the selected card on the incoming signal appear. For PM parameter definitions refer to the Cisco ONS 15327 Reference Manual.
Step 5 View the Curr column to find PM counts for the current time interval.
Step 6 View the Prev-n columns to find PM counts for the previous time intervals.
Step 7 Return to your originating procedure (NTP).
DLP-B127 Monitor Far-End PM Counts
Purpose
|
Use this task to view far-end PM parameters for the selected card and port.
|
Tools/Equipment
|
None
|
Prerequisite Procedures
|
B60 Log into CTC
|
Required/As Needed
|
As needed
|
Onsite/Remote
|
Onsite or remote
|
Security Level
|
Retrieve or higher
|
Step 1 In node view, double-click an XTC card (for electrical PM counts) or an OC-N card. The card view appears.
Step 2 Click the Performance tab.
Step 3 Click the Far End radio button.
Note Only cards that allow far-end performance monitoring have this button as an option.
Step 4 Click Refresh. All PM parameters recorded by the far-end node for the selected card on the outgoing signal appear. For PM parameter definitions refer to the Cisco ONS 15327 Reference Manual.
Step 5 View the Curr column to find PM counts for the current time interval.
Step 6 View the Prev-n columns to find PM counts for the previous time intervals.
Step 7 Return to your originating procedure (NTP).
DLP-B129 Reset Current PM Counts
Purpose
|
This task uses the Baseline button to clear the PM count displayed in the current time interval, but it does not clear the cumulative PM count. This task allows you to see how quickly PM counts rise.
|
Tools/Equipment
|
None
|
Prerequisite Procedures
|
B60 Log into CTC
|
Required/As Needed
|
As needed
|
Onsite/Remote
|
Onsite or remote
|
Security Level
|
Retrieve or higher
|
Step 1 In node view, double-click an XTC card (for electrical PM counts), Ethernet card, or an OC-N card. The card view appears.
Step 2 Click the Performance tab.
Step 3 Click Baseline.
Note The Baseline button clears the PM counts displayed in the current time interval, but does not clear the PM counts on the card. When the current time interval expires or the window view changes, the total number of PM counts on the card and in the window appear in the appropriate column. The baseline values are discarded if you change views to a different window and then return to the Performance Monitoring window.
Step 4 View the current statistics column(s) to observe changes to PM counts for the current time interval.
Step 5 Return to your originating procedure (NTP).
DLP-B130 Clear Selected PM Counts
Purpose
|
This task uses the Clear button to clear specified PM counts depending on the option selected.
|
Tools/Equipment
|
None
|
Prerequisite Procedures
|
B60 Log into CTC
|
Required/As Needed
|
As needed
|
Onsite/Remote
|
Onsite or remote
|
Security Level
|
Superuser
|
Caution Pressing the Clear button can mask problems if used incorrectly. This button is commonly used for testing purposes. After pressing this button the current bin is marked invalid. Also note that the UAS state is not cleared if you were counting UAS; therefore, this count could be unreliable when UAS is no longer counting.
Step 1 In node view, double-click an Ethernet card, XTC card (for electrical PM counts), or an OC-N card. The card view appears.
Step 2 Click the Performance tab.
Step 3 Click Clear.
Step 4 From the Clear Statistics menu, choose one of three options:
•Displayed statistics: Clearing displayed statistics erases from the card and the window all PM counts associated with the current combination of statistics on the selected port. This means that the selected time interval, direction, and signal type counts are erased from the card and the window.
•All statistics for port x: Clearing all of the statistics for port x erases from the card and the window all PM counts associated with all combinations of the statistics on the selected port. This means that all time intervals, directions, and signal type counts are erased from the card and the window.
•All statistics for card: Clearing all of the statistics for the card erases from the card and the window display all PM counts for all ports.
Step 5 From the Clear Statistics menu, click Yes to clear the selected statistics.
Step 6 View the displayed columns to verify that the selected PM counts have been cleared.
Step 7 Return to your originating procedure (NTP).
DLP-B260 Set Auto Refresh Interval for Displayed PM Counts
Purpose
|
This task changes the window auto-refresh intervals for updating the displayed PM counts.
|
Tools/Equipment
|
None
|
Prerequisite Procedures
|
B60 Log into CTC
|
Required/As Needed
|
As needed
|
Onsite/Remote
|
Onsite or remote
|
Security Level
|
Retrieve or higher
|
Step 1 In node view, double-click an Ethernet card, XTC card (for electrical PM counts), or an OC-N card. The card view appears.
Step 2 Click the Performance tab.
Step 3 Click the Auto-refresh drop-down menu and choose one of six options:
•None: This option disables the auto-refresh feature.
•15 Seconds: This option sets the window auto-refresh to 15-second time intervals.
•30 Seconds: This option sets the window auto-refresh to 30-second time intervals.
•1 Minute: This option sets the window auto-refresh to 1-minute time intervals.
•3 Minutes: This option sets the window auto-refresh to 3-minute time intervals.
•5 Minutes: This option sets the window auto-refresh to 5-minute time intervals.
Step 4 Click Refresh. The PM counts for the newly selected auto-refresh time interval appear.
Depending on the selected auto-refresh interval, the displayed PM counts automatically update when each refresh interval completes. If the auto-refresh interval is set to None, the displayed PM counts are not updated unless you click the Refresh button.
Step 5 Return to your originating procedure (NTP).
DLP-B317 View Optical OC-N PM Parameters
Purpose
|
This task enables you to view PM counts on an optical (OC-N) card and port to detect possible performance problems.
|
Tools/Equipment
|
None
|
Prerequisite Procedures
|
B60 Log into CTC
|
Required/As Needed
|
As needed
|
Onsite/Remote
|
Onsite or remote
|
Security Level
|
Retrieve or higher
|
Step 1 In node view, double-click an OC-N card. The card view appears.
Step 2 Click the Performance tab (Figure 7-5).
Figure 7-5 Viewing Optical Performance Monitoring Information
Step 3 The PM parameter names appear on the left portion of the window in the Param column. The PM values appear on the right portion of the window in the Curr (current) and Prev-n (previous) columns. For PM parameter definitions, refer to the Cisco ONS 15327 Reference Manual.
Step 4 Return to your originating procedure (NTP).
DLP-B319 Monitor PM Counts for Selected Signal Types
Purpose
|
This task enables you to monitor near-end or far-end PM counts for specific signals on a selected card and port.
|
Tools/Equipment
|
None
|
Prerequisite Procedures
|
B60 Log into CTC
|
Required/As Needed
|
As needed
|
Onsite/Remote
|
Onsite or remote
|
Security Level
|
Retrieve or higher
|
Step 1 In node view, double-click an XTC card (for electrical PM counts) or an OC-N card. The card view appears.
Step 2 Click the Performance tab.
Note Different port and signal-type menus appear depending on the card type and the circuit type. The appropriate types (DS1, DS3, VT path, STS path, OC-N section and OC-N line) appear based on the card. For example, the OC-48 card lists the OC-48 port and STS path PM parameters as signal-types. You can select both the OC-48 port and the STS within the specified OC-48.
Step 3 Click the Port/Line drop-down menu and highlight the desired port/line. (Options vary depending on the card.)
Step 4 Click the signal type drop-down menu and highlight the desired signal. (Options vary depending on the card.)
Step 5 Click Refresh. All PM counts recorded by the near-end or far-end node appear for the specified outgoing signal type on the selected card and port. For PM parameter definitions, refer to the Cisco ONS 15327 Reference Manual.
Step 6 View the Curr column to find PM counts for the current time interval.
Step 7 View the Prev-n columns to find PM counts for the previous time intervals.
Step 8 Return to your originating procedure (NTP).
NTP-B198 Monitor Ethernet Performance
Purpose
|
This procedure allows you to view node transmit and receive performance on an Ethernet card and port at specified time intervals to detect possible performance problems.
|
Tools/Equipment
|
None
|
Prerequisite Procedures
|
Before you monitor performance, be sure you have created the appropriate circuits and provisioned the card according to your specifications. For more information, see "Create Circuits and VT Tunnels" and "Change Port Settings."
|
Required/As Needed
|
As needed
|
Onsite/Remote
|
Onsite
|
Security Level
|
Retrieve or higher
|
Step 1 Complete the "DLP-B60 Log into CTC" task at the node you want to monitor. If you are already logged in, continue with Step 2.
Step 2 Complete the "DLP-B256 View Ethernet Statistics PM Parameters" task as needed.
Step 3 As needed, use the following tasks to change the display of Ethernet statistical PM counts:
•B260 Set Auto Refresh Interval for Displayed PM Counts
•B129 Reset Current PM Counts
•B130 Clear Selected PM Counts
Step 4 Complete the "DLP-B257 View Ethernet Utilization PM Parameters" task as needed.
Step 5 As needed, use the "DLP-B259 Refresh Ethernet PM Counts at a Different Time Interval" task to change the display of Ethernet utilization PM counts.
Step 6 Complete the "DLP-B258 View Ethernet History PM Parameters" task as needed.
Step 7 As needed, use the following tasks to change the display of Ethernet history PM counts:
•B261 Refresh PM Counts for a Different Port
•B259 Refresh Ethernet PM Counts at a Different Time Interval
Stop. You have completed this procedure.
DLP-B256 View Ethernet Statistics PM Parameters
Purpose
|
This task enables you to view current statistical PM counts on an E-Series or G-Series Ethernet card and port to detect possible performance problems.
|
Tools/Equipment
|
None
|
Prerequisite Procedures
|
B60 Log into CTC
|
Required/As Needed
|
As needed
|
Onsite/Remote
|
Onsite or remote
|
Security Level
|
Retrieve or higher
|
Step 1 In node view, double-click an E-Series or G-Series Ethernet card. The card view appears.
Step 2 Click the Performance tab.
Step 3 Click the Statistics subtab (Figure 7-6).
Figure 7-6 Statistics Window on the Card View Performance Tab
Step 4 Click Refresh. Performance monitoring statistics for each port on the card appear.
The PM parameter names appear on the left portion of the window in the Param column. The parameter numbers appear on the right portion of the window in the Port # columns. For PM parameter definitions refer to the Cisco ONS 15327 Reference Manual.
Step 5 View the Port # columns to see the current PM statistics for each port.
Step 6 Return to your originating procedure (NTP).
DLP-B257 View Ethernet Utilization PM Parameters
Purpose
|
This task enables you to view line utilization PM counts on an E-Series or G-Series Ethernet card and port to detect possible performance problems.
|
Tools/Equipment
|
None
|
Prerequisite Procedures
|
B60 Log into CTC
|
Required/As Needed
|
As needed
|
Onsite/Remote
|
Onsite or remote
|
Security Level
|
Retrieve or higher
|
Step 1 In node view, double-click an E-Series or G-Series Ethernet card. The card view appears.
Step 2 Click the Performance tab.
Step 3 Click the Utilization subtab (Figure 7-7).
Figure 7-7 Utilization Window on the Card View Performance Tab
Step 4 Click Refresh. Performance monitoring utilization values for each port on the card appear.
Step 5 View the Port # column to find the port you want to monitor.
Step 6 View the Prev-n columns to find Tx and Rx bandwidth utilization values for the previous time intervals.
Step 7 Return to your originating procedure (NTP).
DLP-B259 Refresh Ethernet PM Counts at a Different Time Interval
Purpose
|
This task changes the window view to display specified PM counts in time intervals depending on the interval option selected.
|
Tools/Equipment
|
None
|
Prerequisite Procedures
|
B60 Log into CTC
|
Required/As Needed
|
As needed
|
Onsite/Remote
|
Onsite or remote
|
Security Level
|
Retrieve or higher
|
Step 1 In node view, double-click an E-Series or G-Series Ethernet card. The card view appears.
Step 2 Click the Performance tab.
Step 3 Click the Utilization tab or the History tab.
Step 4 Click the Interval drop-down menu button.
Step 5 Choose one of four options:
•1 min: This option displays the specified PM counts in one-minute time intervals.
•15 min: This option displays the specified PM counts in fifteen-minute time intervals.
•1 hour: This option displays the specified PM counts in one-hour time intervals.
•1 day: This option displays the specified PM counts in one-day (24-hour) time intervals.
Step 6 Click Refresh. The PM counts refresh with values based on the chosen time interval.
Step 7 Return to your originating procedure (NTP).
DLP-B258 View Ethernet History PM Parameters
Purpose
|
This task enables you to view historical PM counts at selected time intervals on an E-Series or G-Series Ethernet card and port to detect possible performance problems.
|
Tools/Equipment
|
None
|
Prerequisite Procedures
|
B60 Log into CTC
|
Required/As Needed
|
As needed
|
Onsite/Remote
|
Onsite or remote
|
Security Level
|
Retrieve or higher
|
Step 1 In node view, double-click an E-Series or G-Series Ethernet card. The card view appears.
Step 2 Click the Performance tab.
Step 3 Click the History subtab (Figure 7-8).
Figure 7-8 History Window on the Card View Performance Tab
Step 4 Click Refresh. Performance monitoring statistics appear for each port on the card.
The PM parameter names appear on the left portion of the window in the Param column. The parameter numbers appear on the right portion of the window in the Port # columns. For PM parameter definitions refer to the Cisco ONS 15327 Reference Manual.
Step 5 View the Port # columns to see the current PM statistics for each port.
Step 6 Return to your originating procedure (NTP).
NTP-B235 Create or Delete Ethernet RMON Thresholds
Purpose
|
Use this procedure to create or delete remote monitoring (RMON) Ethernet thresholds for the ONS 15327.
|
Tools/Equipment
|
None
|
Prerequisite Procedures
|
None
|
Required/As Needed
|
As needed
|
Onsite/Remote
|
Onsite or remote
|
Security Level
|
Provisioning or higher
|
Step 1 Complete the "DLP-B60 Log into CTC" task. If you are already logged in, continue with Step 2.
Step 2 Perform any of the following tasks as needed:
•B334 Create Ethernet RMON Alarm Thresholds
•B335 Delete Ethernet RMON Alarm Thresholds
Stop. You have completed this procedure.
DLP-B334 Create Ethernet RMON Alarm Thresholds
Purpose
|
This procedure sets up RMON to allow network management systems to monitor Ethernet ports.
|
Tools/Equipment
|
None
|
Prerequisite Procedures
|
B24 Verify Card Installation
|
Required/As Needed
|
As needed
|
Onsite/Remote
|
Onsite or remote
|
Security Level
|
Provisioning or higher
|
Step 1 Double-click the Ethernet card where you want to create the RMON alarm thresholds.
Step 2 In card view, click the Provisioning > Ether Thresholds tabs.
Step 3 Click Create.
The Create Ether Threshold dialog box appears (Figure 7-9).
Figure 7-9 Creating RMON Thresholds
Step 4 From the Slot drop-down menu, choose the appropriate Ethernet card.
Step 5 From the Port drop-down menu, choose the applicable port on the Ethernet card you selected.
Step 6 From the Variable drop-down menu, choose the variable. See Table 7-2 for a list of the Ethernet threshold variables available in this field.
Table 7-2 Ethernet Threshold Variables (MIBs)
Variable
|
Definition
|
iflnOctets
|
Total number of octets received on the interface, including framing octets
|
iflnUcastPkts
|
Total number of unicast packets delivered to an appropriate protocol
|
ifInMulticastPkts (G-Series only)
|
Number of multicast frames received error free
|
ifInBroadcastPkts (G-Series only)
|
The number of packets, delivered by this sublayer to a higher (sub)layer, which were addressed to a broadcast address at this sublayer
|
ifInDiscards (G-Series only)
|
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
|
iflnErrors
|
Number of inbound packets discarded because they contain errors
|
ifOutOctets
|
Total number of transmitted octets, including framing packets
|
ifOutUcastPkts
|
Total number of unicast packets requested to transmit to a single address
|
ifInMulticastPkts (G-Series only)
|
Number of multicast frames received error free
|
ifInBroadcastPkts (G-Series only)
|
The number of packets, delivered by this sublayer to a higher (sub)layer, which were addressed to a broadcast address at this sublayer
|
ifInDiscards (G-Series only)
|
The number of inbound packets that were chosen to be discarded even though no errors had been detected that would prevent their delivery to a higher-layer protocol
|
dot3statsAlignmentErrors
|
Number of frames with an alignment error, that is, frames with a length that is not an integral number of octets and where the frame cannot pass the frame check sequence (FCS) test
|
dot3StatsFCSErrors
|
Number of frames with framecheck errors, that is, where there is an integral number of octets, but an incorrect FCS
|
dot3StatsSingleCollisionFrames (not supported by E-Series or G-Series)
|
Number of successfully transmitted frames that had exactly one collision
|
dot3StatsMutlipleCollisionFrame(not supported by E-Series or G-Series)
|
Number of successfully transmitted frames that had multiple collisions
|
dot3StatsDeferredTransmissions (not supported by E-Series or G-Series)
|
Number of times the first transmission was delayed because the medium was busy
|
dot3StatsLateCollision (not supported by E-Series or G-Series)
|
Number of times that a collision was detected later than 64 octets into the transmission (also added into collision count)
|
dot3StatsExcessiveCollision (not supported by E-Series or G-Series)
|
Number of frames where transmissions failed because of excessive collisions
|
dot3StatsCarrierSenseErrors (G-Series only)
|
The number of transmission errors on a particular interface that are not otherwise counted
|
dot3StatsSQETestErrors (G-Series only)
|
A count of times that the SQE TEST ERROR message is generated by the PLS sublayer for a particular interface
|
etherStatsUndersizePkts
|
Number of packets received with a length less than 64 octets
|
etherStatsFragments
|
Total number of packets that are not an integral number of octets or have a bad FCS, and that are less than 64 octets long
|
etherStatsPkts64Octets
|
Total number of packets received (including error packets) that were 64 octets in length
|
etherStatsPkts65to127Octets
|
Total number of packets received (including error packets) that were 65 to 172 octets in length
|
etherStatsPkts128to255Octets
|
Total number of packets received (including error packets) that were 128 to 255 octets in length
|
etherStatsPkts256to511Octets
|
Total number of packets received (including error packets) that were 256 to 511 octets in length
|
etherStatsPkts512to1023Octets
|
Total number of packets received (including error packets) that were 512 to 1023 octets in length
|
etherStatsPkts1024to1518Octets
|
Total number of packets received (including error packets) that were 1024 to 1518 octets in length
|
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
|
etherStatsJabbers
|
Total number of packets longer than 1518 octets that were not an integral number of octets or had a bad FCS
|
etherStatsOctets
|
The total number of octets of data (including those in bad packets) received on the network (excluding framing bits but including FCS octets)
|
etherStatsCollisions
|
Best estimate of the total number of collisions on this segment
|
etherStatsCollisionFrames
|
Best estimate of the total number of frame collisions on this segment
|
etherStatsCRCAlignErrors
|
Total number of packets with a length between 64 and 1518 octets, inclusive, that had a bad FCS or were not an integral number of octets in length
|
receivePauseFrames (G series only)
|
The number of received IEEE 802.x pause frames
|
transmitPauseFrames (G series only)
|
The number of transmitted IEEE 802.x pause frames
|
receivePktsDroppedInternal
Congestion (G series only)
|
The number of received frames dropped due to frame buffer overflow as well as other reasons
|
transmitPktsDroppedInternal
Congestion (G series only)
|
The number of frames dropped in the transmit direction due to frame buffer overflow as well as other reasons
|
txTotalPkts
|
Total number of transmit packets
|
rxTotalPkts
|
Total number of receive packets
|
Step 7 From the Alarm Type drop-down menu, indicate whether the event will be triggered by the rising threshold, falling threshold, or both the rising and falling thresholds.
Step 8 From the Sample Type drop-down menu, choose either Relative or Absolute. Relative restricts the threshold to use the number of occurrences in the user-set sample period. Absolute sets the threshold to use the total number of occurrences, regardless of time period.
Step 9 Type in an appropriate number of seconds for the Sample Period.
Step 10 Type in the appropriate number of occurrences for the Rising Threshold.
Note For a rising type of alarm, the measured value must move from below the falling threshold to above the rising threshold. For example, if a network is running below a falling threshold of 400 collisions every 15 seconds and a problem causes 1001 collisions in 15 seconds, this occurrence raises an alarm.
Step 11 Enter the appropriate number of occurrences in the Falling Threshold field. In most cases a falling threshold is set lower than the rising threshold.
Note A falling threshold is the counterpart to a rising threshold. When the number of occurrences is above the rising threshold and then drops below a falling threshold, it resets the rising threshold. For example, when the network problem that caused 1001 collisions in 15 minutes subsides and creates only 799 collisions in 15 minutes, occurrences fall below a falling threshold of 800 collisions. This resets the rising threshold so that if network collisions again spike over a 1000 per 15 minute period, an event again triggers when the rising threshold is crossed. An event is triggered only the first time a rising threshold is exceeded (otherwise a single network problem might cause a rising threshold to be exceeded multiple times and cause a flood of events).
Step 12 Click OK to complete the procedure.
Step 13 Return to your originating procedure (NTP).
DLP-B335 Delete Ethernet RMON Alarm Thresholds
Step 1 Double-click the Ethernet card where you want to delete the RMON alarm thresholds.
Step 2 In card view, click the Provisioning > Ether Thresholds tabs.
Step 3 Click the RMON alarm threshold that you want to delete.
Step 4 Click Delete. The Delete Threshold dialog box appears.
Step 5 Click Yes to delete that threshold.
Step 6 Return to your originating procedure (NTP).
Feedback
