Table Of Contents
Performance Monitoring
Using Performance Monitoring
Opening Performance Monitoring
Configuring Statistical Threshold Events
Adding or Editing Events
Deleting Events
Event Reference
Configuring State-Change Events
Managing Event Reporting
Configuring Multiple Event Destinations
Ignoring ASE Events
Performance Monitoring
In Performance Monitoring, you configure each ASE to monitor network performance events. Once configured, ASEs continually monitor your network for statistical threshold and state-change events. When an event is triggered, Cisco WAPMS immediately posts notification in the Event Processor window so you can take corrective action.
Topics in this chapter include:
•
"Using Performance Monitoring"
•"Configuring Statistical Threshold Events" section—selecting which statistical threshold events the ASE reports and configuring settings that will trigger events
•"Configuring State-Change Events" section—selecting the types of state-change events the ASE will report
•"Managing Event Reporting" section—managing event reporting, which includes specifying other event destinations in addition to the current PAM and ignoring ASE events.
To configure multiple ASEs network-wide with the same performance monitoring settings, use the Templates tool in the PAM Manager application available on the PAM. See Chapter 4, "Managing ASEs Using PAM Manager," in the Cisco WAN Access Performance Management System System Administration Guide, 2.0.
Using Performance Monitoring
You initiate all performance monitoring configuration tasks from the Event Processor window. You open the Performance Monitoring Event Generation window through this window.
When the Performance Monitoring option is unavailable, either you have not selected a network element or your user ID does not have permission to use Performance Monitoring. Contact your PAM administrator.
Opening Performance Monitoring
Step 1 From the Event Processor window (the Cisco WAPMS home window), connect to a domain. (See the "Connecting to a Domain" section.)
Step 2 Use the Network Selector to select a network, site, and access line. (See the "Using the Network Selector" section.)
Step 3 On the Event Processor Tool bar, click Performance Monitoring.
Step 4 The Performance Monitoring Event Generation window, shown in Figure 4-1, appears.
Use the Performance Monitoring Event Generation window to select the statistical threshold events and state-change events to be reported by the current ASE, then choose where these events will be reported.
Figure 4-1 Performance Monitoring Event Generation Window
The window features include:
•Configured Statistical Threshold Events pane—view all currently configured statistical threshold events for the selected ASE. You can add, edit, and delete events from the list. Options and statistical events displayed here depend on the capability of the ASE.
The pane is unavailable for ASEs not allowing configuration of statistical threshold events. See the "Configuring Statistical Threshold Events" section
•Generate Event upon pane—designate the categories of state-change events the ASE will report. Specific events in each category vary according to the ASE and the network on which it resides. See the "Configuring State-Change Events" section.
•Ignore all Events from this ASE—direct the ASE to stop reporting events configured for it. Use this to temporarily turn off performance monitoring on an ASE without deleting configured events. Remember to clear this option to have the ASE resume event reporting.
•Destinations—configure the ASE to report events to multiple destinations. See the "Configuring Multiple Event Destinations" section.
After you close this window, you may want to assign priorities to state-change events. See the "Setting Global Event Priorities" section.
Configuring Statistical Threshold Events
A statistical threshold event is triggered when a variable exceeds a threshold you have set for it. For an ASE to report a statistical threshold event, you must first set statistical thresholds, which, when met or exceeded, will generate the event. No statistical threshold events are configured by default in an ASE. The maximum number of events you can configure are:
•1500 events for ATM ASEs
•512 events for HSSI ASEs
•64 events for other Frame Relay ASEs.
Note IP transport ASEs do not support statistical threshold events.
Adding or Editing Events
Step 1 Open the Performance Monitoring Event Generation window. See the "Using Performance Monitoring" section.
•To add a new event, click Add New Event.
•To edit an event, select it from the list, then click Edit.
The Statistical Threshold Event Configuration window, shown in Figure 4-2, appears.
Figure 4-2 Statistical Threshold Event Configuration Window
Step 2 From the Statistic drop-down list, select a statistic to monitor.
The statistics available in the drop-down list at any given time are appropriate to the selected ASE and the network on which it resides. No line events apply for the following physical layers: EIA.530, RS232, RS449, V.35, X.21, and HSSI. Table 4-1, Table 4-2, and Table 4-3 describe respectively all possible statistics for physical layer, Frame Relay, HDLC, and ATM ASEs.
Step 3 Assign a priority number to the event using higher numbers to indicate higher event severity.
You can filter events displayed in the Event Processor window according to the priority number set here. The valid range is 1-255. The default is 100.
Step 4 When Line Side is available, click To Network or From Network to specify the direction the ASE will monitor for the event.
Step 5 When the statistic applies to or is associated with a circuit, the PVC or VC drop-down list is available:
a. for Frame Relay ASEs (PVCs), select a DLCI circuit to monitor
b. for ATM ASEs (VCs), select a VPI/VCI circuit to monitor.
Step 6 In the Parameters pane, specify:
a. Threshold to specify a threshold the statistic must meet or exceed for an event to be generated when Value Rises To or Above is selected. Units for this setting depend on the statistic selected. For example, when you select T1 Errored Seconds for Statistic, Threshold units are seconds.
b. Hysteresis to set the hysteresis. For an event generated on a rising edge (specified in the Generate an Event When pane), hysteresis determines how far below the threshold the statistic must fall before the same event can be regenerated. For a falling-edge-generated event, hysteresis indicates how far above the threshold the statistic must rise before the same event can be regenerated. In all cases, the default hysteresis is "Threshold minus 10 percent," and the default measurement interval is 60 seconds. (For the Value Falls To or Below setting shown in Figure 4-2, 72 percent equals the threshold [80 percent] minus 10 percent of the threshold, or 8 percent.)
c. Measurement Interval to specify a measurement/time duration. The statistical threshold criteria must be met for this duration before Cisco WAPMS generates an event.
Step 7 In the Generate an Event When pane, specify whether to generate the event on a rising or falling edge of occurrence. Select:
•Value Rises To or Above to generate an event when the value of the statistic rises to or above the selected threshold.
•Value Falls To or Below to generate an event when the value of the statistic falls to or below the selected threshold, adjusted for hysteresis.
The actual text of these selections varies depending on the values you set in the Parameters pane.
Step 8 Click OK to confirm your settings or Cancel to ignore your changes and close the window.
When you are adding a statistical event, the event is added to the Configured Threshold Events list in the Performance Monitoring Event Generation window.
Deleting Events
Step 1 Open the Performance Monitoring Event Generation window (see the "Using Performance Monitoring" section).
Step 2 Select one or more events to delete from the Statistic list.
Step 3 Click Delete. A confirmation window prompts you to confirm your deletion. Click Yes to delete the selected events.
Event Reference
Consult the following tables for statistical threshold events listed by physical layer (Table 4-1), Frame Relay and HDLC (Table 4-2), and ATM (Table 4-3).
Table 4-1 Statistical Threshold Events—Physical Layer (Received on Interface Only)
Statistic
|
Description
|
DDS Bipolar Violations (BPVs)
|
Number of bipolar violations detected on the interface during the measurement interval.
|
DDS Errored Second
|
Number of DDS errored seconds detected during the measurement interval.
|
DDS Severely Errored Seconds
|
Number of DDS severely errored seconds detected during the measurement interval.
|
DS3/E3/OC-3 Errored Seconds
|
Number of DS3, E3 or OC-3 errored seconds detected during the measurement interval.
|
DS3/E3 FEBE Count
|
Number of far end block errors (FEBE) detected on the access line during the measurement interval.
|
DS3/E3/OC-3 Frame Error Count
|
Number of framing errors detected on the access line during the measurement interval.
|
DS3/E3/OC-3 Line Code Violation Count
|
Number of Line Coding Violations (LCV) detected on the access line during the measurement interval.
|
DS3/E3/OC-3 Severely Errored Seconds
|
Number of DS3, E3 or OC-3 severely errored seconds detected during the measurement interval.
|
DSL Drop Events
|
Number of times the interface dropped data due to buffer overruns or any other reason.
|
DSL Errored Seconds
|
Number of seconds in which one or more access line defects have occurred on the DSL interface.
|
DSL Negotiated Rate (to/from network)
|
Transmit or receive data rate (in bits per second) negotiated for the DSL interface.
|
DSL Rate Changes (to/from network)
|
Number of times the transmit or receive DSL Negotiated Rate (in bits per second) has been changed for the DSL interface.
|
DSL Severely Errored Seconds
|
Number of DSL severely errored seconds detected during the measurement interval.
|
DSL Signal Quality
|
Signal quality of the DSL interface as indicated by the signal-to-noise ratio on the receiver. The measurement unit is in tenth of a dB.
|
T1/E1 Bipolar Violations (BPVs)
|
Number of BPVs detected per measurement interval.
|
T1/E1 CRC Frame Errors
|
Number of CRC Errors (with ESF framing) or Frame Errors (with all other framing) received on the interface.
|
T1/E1 Errored Seconds
|
Number of errored seconds detected during the measurement interval.
|
T1/E1 Severely Errored Seconds
|
Number of severely errored seconds detected during the measurement interval.
|
E1 REBE Count
|
The number of remote end block errors (REBE) detected on the access line during the measurement interval.
|
Table 4-2 Statistical Threshold Events—Frame Relay/HDLC
Statistic
|
Description
|
Channel FCS/Align Errors (to/from network)
|
Number of Frame Check Sequence (FCS) or Align errors detected during the measurement interval.
|
Channel Throughput (to/from network)
|
Number of Kbits transmitted/received over the channel during the measurement interval.
|
Channel Utilization (to/from network)
|
Percentage of channel utilized during the measurement interval.
|
PVC Congested Seconds (to/from network)
|
(Frame Relay only) Number of seconds during the measurement interval in which a particular PVC experienced congestion.
|
PVC Utilization (to/from network)
|
(Frame Relay only) Percentage of a line rate utilized by a particular PVC during the measurement interval.
|
Utilization by <x Internet Application> (to/from network only)
|
Percentage of a PVC or HDLC circuit utilized by a particular Internet application during the measurement interval.
|
Utilization by <x protocol> (to network only) (Protocols shown correspond to those selected in Network Configuration.)
|
Percentage of the line speed utilized by the named protocol (x) on the indicated PVC or HDLC link during the measurement interval.
|
Table 4-3 Statistical Threshold Events—ATM
Statistic
|
Description
|
Channel Throughput (to/from network)
|
Number of Kbits per second transmitted/received over the channel during the measurement interval.
|
Channel Utilization (to/from network)
|
Percentage of ATM or Frame Relay channel utilized during the measurement interval.
|
HEC Correctable Error Count (to/from network)
|
Number of correctable HEC errors detected on channel during the measurement interval.
|
HEC Uncorrectable Error Count (to/from network)
|
Number of uncorrectable HEC errors detected on channel during the measurement interval.
|
PCR Utilization (to/from network)
|
Percentage of the PCR value utilized by a VC (VP or VC) during the measurement interval. When PCR is zero (as set in Network Configuration), line speed is used.
|
SCR Utilization (to/from network)
|
Percentage of the SCR value utilized by a VC (VP or VC) during the measurement interval. When SCR is zero (as set in Network Configuration), line speed is used.
|
Utilization by <x protocol> (to network only) (Protocols shown correspond to those selected in Network Configuration.)
|
(AAL-5 only) Percentage of line speed utilized by the named protocol (x) on the indicated VC during the measurement interval.
|
VP/VC Congested Seconds (to/from network)
|
Number of seconds during which cells with the congestion indication bit set have been transmitted/received on the circuit.
|
VP/VC Utilization (to/from network)
|
Percentage of line speed utilized by a particular VP or VC during the measurement interval.
|
Configuring State-Change Events
You can configure each ASE to report state-change events, depending on the ASE's capabilities.
A state-change event is triggered whenever certain changes in network states occur (including SNMP authentication failure). ASEs always report ASE Reboot and Data Collection Poll Failure events, so you do not need to select these state-change events in Performance Monitoring.
In the Performance Monitoring Event Generation window, you can configure the following event types:
•Link Layer and Circuit State Changes—configure the ASE to report events:
–when a Frame Relay or ATM access channel becomes operational or non-operational
–when a DLCI (Frame Relay) is active, inactive, or invalid
–when a VPI/VCI or VC (ATM) is active or inactive.
The option is unavailable for HDLC ASEs.
•Physical Layer State Changes—configure the ASE to report events when the physical access line becomes operational or non-operational.
For a partner ASE with more than one physical interface, events are reported on all relevant physical interfaces on the device.
•SNMP Authentication Failure—configure the ASE to report events when an incorrect SNMP community name is used in attempts to contact the ASE.
You can also assign priorities to state-change events by choosing the Setup > Domain Options menu option. For more information, see the "Setting Global Event Priorities" section.
For information on assigning priority levels to colors, see the "Assigning Event Priorities to Colors" section.
For information about individual state-change event messages, see "Network Events."
Managing Event Reporting
In Performance Monitoring, you can specify whether events from a given ASE should be reported to multiple destinations, temporarily not reported to a specific destination, or temporarily not reported at all.
Configuring Multiple Event Destinations
You can configure an ASE to report performance monitoring events to multiple destinations. For example, you may want an ASE to report events to a workstation running a third-party event manager, such as HP OpenView or IBM NetView. Each ASE stores its own event destination information and reports events to every configured event destination.
By default, the PAM that contains the ASE configuration is always an event destination. All PACs communicating with the PAM can view the events in the Event Processor window. PACs are not configured as event destinations.
This ASE-level option in Performance Monitoring retains the full event information, including the event-generating ASE's IP address. The event remains in SNMP trap format. This option is in contrast to the domain-level Event Forwarding option on the Setup menu. (See the "Event Forwarding" section.)
You can also temporarily disable ASE events from being forwarded to a specific destination, such as when that destination out of commission. Disabling a destination also saves you the effort of removing the destination from the ASE's configuration and adding it again later.
Step 1 In the Performance Monitoring Event Generation window, click Destinations.
The Event Destinations window, shown in Figure 4-3, appears.
Figure 4-3 Event Destinations Window
Step 2 You have three options:
•To add a workstation to the list of those receiving current notification of events from this ASE, click Add New Destination.
•To modify a destination's IP address or settings, select it, then click Edit.
•To remove a workstation from the list of those receiving current notification of events from this ASE, click Delete.
When adding or editing, the Event Destination Configuration window appears.
Step 3 In the IP Address text field, type the IP address of the workstation to be notified of events.
Step 4 To enable the ASE to return events to the specified workstation, clear Disabled.
To temporarily disable ASE events from being forwarded to a specific destination, click Disabled. When the destination is in use again, clear the Disabled option.
Step 5 Click OK.
Ignoring ASE Events
You may not always want the ASE to report events you have configured for it. For example, when you know an access line will be down for maintenance, you may not want the ASE to generate events during the maintenance interval.
In the Performance Monitoring Event Generation window, select the Ignore All Events from this ASE option, then click OK.
When you want the ASE to begin generating events again, return, then clear the Ignore option.
