Collect selected performance attributes at specific times.
Store these sampled performance attributes in the database of the attribute history server.
Poll performance data continuously and store it in the controller database.
View performance data by using the Performance Manager.
Export performance data to a flat file.

Note All collected performance data is stored for at least seven days in the database.

Devices on which you enable performance polling must be in the normal (commissioned) state.

: Cisco UGM checks that the device state is normal; performance polling is not affected by the state of device subcomponents.

Polling is turned on or off at the device level. All subcomponents in the device have polling either enabled or disabled along with the host device. Specify polling intervals at the MIB attribute level; the intervals are global.

: For example, if the user specifies that the Active DS0s attribute is to be sampled on all devices every five minutes, all Active DS0s in all the
Cisco UGM-managed devices with polling enabled are sampled every five minutes.

About Adding Devices to be Polled

fiveMin, fifteenMin, thirtyMin, sixtyMin polling periods—Device objects added during a polling cycle are polled only when the current cycle is completed. For example, if you start polling a device in the middle of a 15-minute cycle, no attribute of that device is polled in the current cycle; data from the device is polled in the next 15-minute cycle.
oneDay, sevenDay polling periods—If the number of new devices added (during a polling cycle) is more than half of the current number of devices being polled, the current polling cycle is discontinued, and all devices (including the new ones) are polled in the next new cycle.

: If the number of new devices added (during a polling cycle) is less than half the current number of devices being polled in the current cycle, no attribute of the new devices is polled in the current cycle; data from the new devices is polled in the next polling cycle.

Information on Dialog Tabs

Ethernet dialog tab refers to the Ethernet, Fast Ethernet, and GigaBit Ethernet ports.

Modem dialog tab refers to the modem and universal ports.

DS1 dialog tab refers to the DS1 port, DS1 channel, and E1 port.

Chassis dialog tab refers to the Cisco AS5350, AS5400, AS5800, and AS5850 devices.

DS0 dialog tab refers to the DS0 channel.

DS3 dialog tab refers to the DS3 port.

Others dialog tab contains attribute information that cannot be displayed by the Performance Manager. In order to view this data, export it to a flat file.
See the "Overview of the Performance Data Export File" section.

Note Select the Dynamic Update option to continuously refresh the properties data (under these tabs) every 10 seconds.

About Polling Intervals and the Number of Devices Polled

When you select polling intervals for device and subcomponent attributes and the number of devices to be polled, make sure that the peak load of performance polling does not exceed Cisco UGM management limits.

Consider these factors when selecting polling intervals:

Number of devices being polled simultaneously.
Number of ports being polled for each device. (This includes Ethernet ports, DS0 channels, DS1 ports and channels, DS3 ports, modem ports, and universal ports.)
Number of network interfaces with sub-queue for each device.

Note If the polling load in your system exceeds Cisco UGM capacity, the Performance Manager displays frequent "Missed Poll" messages. For an explanation of this message, see the "Missed Poll" section.

Selecting Performance Polling Intervals

Default performance polling intervals for the chassis and its subcomponents are:

Chassis—fifteen minutes
DS0, DS1, DS3, Modem, Ethernet, Others—none

To select or change the default or current performance polling interval:

Step 1 In the Map view, choose ASEMSConfig > PerfPollConfig > Open Global Performance Polling Configuration.

Step 2 Click the tab representing the system element to be polled.

See the "Information on Dialog Tabs" section for more details.

Step 3 Click one of the polling period choices: None, fiveMin, fifteenMin, thirtyMin, sixtyMin, oneDay, and sevenDay.

Step 4 Repeat Steps 2 and 3 until you have completed your polling interval selections.

Step 5 Click Save in the menu bar.

Step 6 Start performance polling as described in the "Starting and Stopping Performance Polling for the Chassis and Subcomponents" section.

Starting and Stopping Performance Polling for the Chassis and Subcomponents

Step 1 In the Map view, right-click the device, and choose Chassis > Start/Stop Performance Polling.

From the Map View, right-click a site (or other container) icon and select ASMainEM > Start/Stop Performance Polling. (Use this method to start or stop performance polling on multiple devices.)

Step 2 Select the performancePolling - ON option.

If you want to stop performance polling later, access this dialog box again and select the performancePolling - OFF option.

Step 3 Click the Save button.

Wait for the Action Report window to appear before leaving this screen.

Overview of Performance Data

With the Performance Manager, you can generate line charts or tables to view device and subcomponent performance for most attributes of managed devices— with the exception of those included in the Others tab.

Tip Some data cannot be viewed online; export it to a flat file; then, view it.

Line Charts and Tables

With line charts and tables, you can view device or card attribute data.
Cisco UGM plots data corresponding to attributes selected from a list in the Performance Manager dialog box.

Line charts plot a single attribute at a time, whereas tables can represent several attributes. The colored dots (in line charts) or cells (in tables) represent:

Green indicates that performance polling for the device has started.

Yellow indicates that a poll for an attribute was missed.

Red indicates that performance polling for the device has stopped.

The View button on the top navigation bar has a drop-down menu that allows you to enhance line charts by selecting:

Values—Plots the values of the samples collected during the line chart.
Points—Plots the time that the samples were collected during the line chart.

Device and Subcomponent Performance Attributes That You Can View

Table 8-1: Chassis Performance Attributes

Text Field	MIB Attribute Name	Description
Bad Community Uses	SNMPv2-MIB snmpInBadCommunityUses	Indicates the number of SNMP messages delivered to the SNMP host that represented an SNMP operation not allowed by the SNMP community named in the message.
Bad Community Names	SNMPv2-MIB snmpInBadCommunityNames	Indicates the number of SNMP messages delivered to the SNMP host that used an SNMP community name not recognized by the SNMP entity.
ISDN Cfg B-Channels in Use	CISCO-POP-MGMT-MIB cpmISDNCfgBChanInUseForAnalog	Indicates the number of configured ISDN B-channels that are currently occupied by both analog and digital calls.
Active DS0s	CISCO-POP-MGMT-MIB cmpActiveDS0	Indicates the number of DS0s that are currently in use.
ISDN Calls Rejected	CISCO-POP-MGMT-MIB cpmISDNCallsRejected	Indicates the number of rejected ISDN calls in this managed device.
ISDN Calls Cleared Abnormally	CISCO-POP-MGMT-MIB cpmISDNCallsClearedAbnormally	Indicates the number of connected ISDN calls that were cleared by an event other than: Transmission by the local end of a normal disconnect message. Reception by the remote end of a normal disconnect message.
ISDN No Resource	CISCO-POP-MGMT-MIB cpmISDNNoResource	Indicates the number of ISDN calls that were rejected because there was no B-channel available to handle the calls.
Average Busy 5 min	OLD-CISCO-CPU-MIB avgBusy5	Represents the 5-minute exponentially decayed moving average of the CPU busy percentage.
System Modems In Use	CISCO-MODEM-MGMT-MIB cmSystemModemsInUse	Indicates the number of network modems that are in these states: connected offHook loopback downloadFirmware
System Modems Available	CISCO-MODEM-MGMT-MIB cmSystemModemsAvailable	Indicates the number of network modems that are onHook.
System Modems Unavailable	CISCO-MODEM-MGMT-MIB cmSystemModemsUnavailable	Indicates the number of network modems that cannot accept calls.
System Modems Offline	CISCO-MODEM-MGMT-MIB cmSystemModemsOffline	Indicates the number of network modems that have been placed offline administratively.
System Modems Dead	CISCO-MODEM-MGMT-MIB cmSystemModemsDead	Indicates the number of network modems in one of these states: Bad downloadFirmwareFailed
Call Count	CISCO-MODEM-MGMT-MIB cpmCallCount	Indicates the number of calls that have occupied this DS0.

Table 8-2: Performance Attributes for the DS0 Port

Text Field

MIB Attribute Name

Description

Call Count

CISCO-MODEM-MGMT-MIB

cpmCallCount

Indicates the number of calls that have occupied this DS0.

Table 8-3: Performance Attributes for the DS1 Port

Text Field	MIB Attribute Name	Description
Line Status (from RFC1406dsx1ConfigTable)	RFC1406 dsx1LineStatus	Indicates the line status of the interface, and contains loopback, failure, received alarm, and transmitted alarm information.
Errored Seconds	RFC1406 dsx1CurrentESs	Indicates the number of errored seconds encountered by a DS1 interface in the current fifteen-minute interval.
Severely Errored Seconds	RFC1406 dsx1CurrentSESs	Indicates the number of severely errored seconds encountered by a DS1 interface in the current fifteen-minute interval.
Errored Framing Seconds	RFC1406 dsx1CurrentSEFs	Indicates the number of errored framing seconds encountered by a DS1 interface in the current fifteen-minute interval.
Line Code Violations	RFC1406 dsx1CurrentLCVs	Indicates the number of line code violations encountered by a DS1 interface in the current fifteen-minute interval.
Controlled Slip Seconds	RFC1406 dsx1CurrentCSSs	Indicates the number of controlled slip seconds encountered by a DS1 interface in the current fifteen-minute interval.
Path Coding Violations	RFC1406 dsx1CurrentPVCs	Indicates the number of path coding violations encountered by a DS1 interface in the current fifteen-minute interval.
Line Errored Seconds	RFC1406 dsx1CurrentLESs	Indicates the number of line errored seconds encountered by a DS1 interface in the current fifteen-minute interval.
Unavailable Seconds	RFC1406 dsx1CurrentUASs	Indicates the number of unavailable seconds encountered by a DS1 interface in the current fifteen-minute interval.

Table 8-4: Performance Attributes for Ethernet, Fast Ethernet, and Giga Ethernet Ports

Text Field	MIB Attribute Name	Description
In/Out Octets	IF-MIB ifInOctets ifOutOctets	Indicates the number of incoming or outgoing octets handled by the card.
In/Out Errors	IF-MIB ifInErrors ifOutErrors	Indicates the number of incoming or outgoing packet errors for the card since the last restart.
In Ucast Pkts	IF-MIB ifInUcastPkts	Indicates the number of packets, delivered by this sublayer to a higher sublayer that was not addressed to a multicast or broadcast address at this sublayer.
In NUcast Pkts	IF-MIB ifInNUcastPkts	Indicates the number of packets, delivered by this sublayer to a higher sublayer, that was addressed to a multicast or broadcast address at this sublayer.
In/Out Discards	IF-MIB ifInDiscards ifOutDiscards	Indicates the number of incoming or outgoing packets discarded since the last restart.
In Unknown Protos	IF-MIB ifInUnknownProtos	Packet-oriented interfaces—Indicates the number of packets, received by the interface, that were discarded due to an unknown or unsupported protocol. Character-oriented or fixed-length interfaces that support protocol multiplexing—Indicates the number of transmission units received by the interface that were discarded due to an unknown or unsupported protocol. If an interface does not support protocol multiplexing, this counter is always 0.
Out Ucast Pkts	IF-MIB ifOutUcastPkts	Indicates the number of packets that high-level protocols requested to be transmitted, but were not addressed to a multicast or broadcast address at this sublayer. This number includes packets that were discarded or not sent.
Out NUcast Pkts	IF-MIB ifOutNUcastPkts	Indicates the number of packets that high-level protocols requested to be transmitted, and were addressed to a multicast or broadcast address at this sublayer. This number includes packets that were discarded or not sent.

Table 8-5: Performance Attributes for Modem and Universal Ports

Text Field	MIB Attribute Name	Description
Ring No Answers	CISCO-MODEM-MGMT-MIB CmRingNoAnswers	Indicates calls which were ringing, but were unanswered at this modem.
Incoming Connection Failures	CISCO-MODEM-MGMT-MIB cmIncomingConnectionFailures	Indicates the number of incoming connection requests that this modem answered but failed to train with the other DCE. This object exists only for modems which have cmManageable to be true.
Incoming Connection Completions	CISCO-MODEM-MGMT-MIB cmIncomingConnectionCompletions	Indicates the number of incoming connection requests that this modem answered and successfully trained with the other DCE. This object exists only for modems which have cmManageable to be true.

Text Field

MIB Attribute Name

Description

Ring No Answers

CISCO-MODEM-MGMT-MIB

CmRingNoAnswers

Indicates calls which were ringing, but were unanswered at this modem.

Incoming Connection Failures

CISCO-MODEM-MGMT-MIB

cmIncomingConnectionFailures

Indicates the number of incoming connection requests that this modem answered but failed to train with the other DCE.

This object exists only for modems which have cmManageable to be true.

Incoming Connection Completions

CISCO-MODEM-MGMT-MIB

cmIncomingConnectionCompletions

Indicates the number of incoming connection requests that this modem answered and successfully trained with the other DCE.

This object exists only for modems which have cmManageable to be true.

Table 8-6: Performance Attributes for the DS3 Port

Text Field	MIB Attribute Name	Description
Line Status (from RFC1407dsx3ConfigTable)	RFC1407 dsx3LineStatus	Indicates the line status of the interface, and contains loopback, failure, received alarm, and transmitted alarm information.
P-bit Errored Seconds	RFC1407 dsx3CurrentPESs	Indicates the number of P-bit errored seconds encountered by a DS3 interface in the current fifteen-minute interval.
P-bit Severely Errored Seconds	RFC1407 dsx3CurrentPSESs	Indicates the number of P-bit severely errored seconds encountered by a DS3 interface in the current fifteen-minute interval.
Errored Framing Seconds	RFC1407 dsx3CurrentSEFSs	Indicates the number of severely errored seconds encountered by a DS3 interface in the current fifteen-minute interval.
Line Code Violations	RFC1407 dsx3CurrentLCVs	Indicates the number of line coding violations encountered by a DS3 interface in the current fifteen-minute interval.
Path P-bit Coding Violations	RFC1407 dsx3CurrentPCVs	Indicates the number of P-bit coding violations encountered by a DS3 interface in the current fifteen-minute interval.
Line Errored Seconds	RFC1407 dsx3CurrentLESs	Indicates the number of line errored seconds encountered by a DS3 interface in the current fifteen-minute interval.
Unavailable Seconds	RFC1407 dsx3CurrentUASs	Indicates the number of unavailable seconds encountered by a DS3 interface in the current fifteen-minute interval.

Performance Attributes that You Cannot View

The following attributes cannot be viewed by Performance Manager; the attributes are uncharted data. Export the data to flat files.

Table 8-7: Performance Attributes in the Others Tab

Text Field	MIB Attribute Name	Description
Queue Number within the Queue Set	CISCO-QUEUE-MIB cQStatsQNumber	In FIFO queuing, this value is always 2. In priority queuing, this value indicates priority: High=0 Medium=1 Normal=2 Low=3 In custom queuing, this value is the queue number referenced in the access list. In weighted fair queuing, this value is the queue number associated with the traffic stream identified.
Number of Messages in the Sub-Queue	CISCO-QUEUE-MIB cQStatsDepth	Indicates the number of messages currently in the subqueue.
Max Number of Messages Permitted in the Sub-Queue	CISCO-QUEUE-MIB cQStatsMaxDepth	Indicates the number of messages permitted in the subqueue.
Number of Messages Discarded from the Queue	CISCO-QUEUE-MIB cQStatsDiscards	Indicates the number of messages discarded from this queue since the restart of performance polling.
ciscoEnvMonSupplyStatusDescr	CISCO-ENVMON-MIB ciscoEnvMonSupplyStatusDescr	Describes the power supply being monitored.
Memory Pool Name	CISCO-MEMORY-POOL-MIB	Identifies the memory pool.
Memory Pool Free	CISCO-MEMORY-POOL-MIB ciscoMemoryPoolFree	Indicates the number of bytes from the memory pool that are currently unused on the managed device.
Memory Pool Used	CISCO-MEMORY-POOL-MIB ciscoMemoryPoolUsed	Indicates the number of bytes from the memory pool that are currently in use by applications on the managed device.
ciscoPingSentPackets	CISCO-PING-MIB ciscoPingSentPackets	Indicates the number of ping packets sent to the target.
ciscoPingReceivedPackets	CISCO-PING-MIB ciscoPingReceivedPackets	Indicates the number of ping packets received from the target.
ciscoPingMinRtt	CISCO-PING-MIB ciscoPingMinRtt	Indicates the minimum round-trip time taken by the packets in this sequence.
ciscoPingAvgRtt	CISCO-PING-MIB ciscoPingAvgRtt	Indicates the average round-trip time taken by the packets in this sequence.
ciscoPingMaxRtt	CISCO-PING-MIB ciscoPingMaxRtt	Indicates the maximum round-trip time taken by the packets in this sequence.
ciscoPingCompleted	CISCO-PING-MIB ciscoPingCompleted	Indicates when all the packets in this sequence have been responded to or have been timed out.

Viewing Performance Data

User-specified polling intervals may sometimes be delayed due to other system processes. If you want to view new attributes or the latest polled data:

Click Now—The latest polled data appears.
Click Refresh—New attribute data or changes to the format appear.

Step 1 To view Performance Manager data, locate and right-click the object whose performance data you want to view, and choose Tools >Performance Manager.

Step 2 In the left-side list box, click the performance data you want to view.

See the "" section.

Step 3 (Optional) Modify the Time Period box settings. These settings tell the Performance Manager to display data collected from a starting to ending time and date.

Step 4 Click the Line Chart or Table Display tab to view your data in the appropriate form.

Step 5 (Optional) If you selected Line Chart, select Values or Points if required.

See the "Line Charts and Tables" section.

Overview of the Performance Data Export File

With Cisco UGM, you can export inventory, performance, and alarm data to ASCII files and send them to an external system by using File Transfer Protocol (FTP).

The interval at which performance data is exported to flat files is tied to the interval at which performance polling takes place. Changing the performance polling interval also changes the data export interval.

For details on changing the performance polling interval, see the "Selecting Performance Polling Intervals" section.

Cisco UGM creates a performance data file for each polling interval that you select. You can create six performance data files at any time:

fiveMin.export
fifteenMin.export
thirtyMin.export
sixtyMin.export
oneDay.export
sevenDay.export

Each data file contains performance data for all attributes sampled at that polling interval.

For example, if Line Code Violations and Out NUcast Pkts are sampled every five minutes, the polled data for these attributes is in the fiveMin.export file. However, if the same attributes are polled once a day, the polled data is now in the oneDay.export file.

You can create performance data export files at the device level to include all subcomponent data, or at the port level, consisting of data from a single attribute.

Location of the Performance Data Export Files

All performance data files are saved in the CEMF_BaseDir directory on the server.

For a description of performance data files, see the "Overview of the Performance Data Export File" section.

The directory path and filename for each device's performance data file is:

CEMF_BaseDir/Physical:_SiteName_AS5xxxDeviceName.PollingInterval.EXPORT

where:

CEMF_BaseDir—Is the base directory input from the Performance tab of the File Export Properties dialog box. (See the "Exporting a File" section.)

: You specify this segment of the path.

SiteName—Is the name of the site object under which the performance polled managed device is located. This is automatically generated by Cisco UGM.
AS5xxxDeviceName—Is the hostname or IP Address of the performance polled managed device. This is automatically generated by Cisco UGM.

Example of Performance Data File Location

If the 172.24.217.25 device is located under Physical > Site-1, and /tmp/Oct-3-test is the input directory for file export, this export file under the /tmp/Oct-3-test directory:

Physical:_Site-1_172.24.217.25.fifteenMin.EXPORT

Exporting a File

Step 1 In the Physical view, select and right-click the object for which you want to export performance data.

Step 2 Choose ASEMSConfig > File Export > Open File Export Properties > Performance.

Step 3 In the Export Type field, select Continuous.

Step 4 Enter a storage path for the file.

See the "Location of the Performance Data Export Files" section.

Step 5 Select an action to be performed when file aging occurs:

none—Disables aging; File Age and Aging Directory fields are ignored.
delete—Deletes the aged file from the disk.
move—Moves the aged file into the aging directory.
moveTarCompress—Compresses the aged file; then adds it to the FileExport.tar file which, if it does not already exist, is created in the Aging Directory.

Step 6 Specify the maximum size (in KBytes) of a file before the selected aging action is performed. Export then continues in the newly created file.

Step 7 Specify where the file should be moved to (or moveTarCompressed to) when aging occurs.

If you enter a non-existent directory path, it is automatically created.
This field does not apply to the delete aging action.
The directory string that you enter must end with a trailing / (forward slash).
If the Action field is set to moveTarCompress, FileExport.tar is created in the Aging Directory to contain aged files.

Step 8 Click Save. An Action Report is generated.

See the "About Action Reports" section.

Example: Performance Export Data Format

Performance export data for scalar attributes is formatted as follows:

<DATA-TIME>|<ATTRIBUTE NAME> <Value>

2000/09/08-10:43:51 EDT|CISCO-MODEM-MGMT-MIB.cmSystemModemsDead 0
2000/09/08-10:43:51 EDT|CISCO-MODEM-MGMT-MIB.cmSystemModemsOffline 0
2000/09/08-10:43:51 EDT|CISCO-MODEM-MGMT-MIB.cmSystemModemsUnavailable 
0
2000/09/08-10:43:51 EDT|CISCO-MODEM-MGMT-MIB.cmSystemModemsAvailable 
60
2000/09/08-10:43:51 EDT|CISCO-MODEM-MGMT-MIB.cmSystemModemsInUse 0
.
.
.
Performance export data for table attributes is formatted as follows:
<DATA-TIME>|<TABLE NAME>|<Column-1 Name>|...|<Column-n Name>|<Value of 
Column-1>|...|<Value of Column-n>
2000/09/08-10:43:52 
EDT|ASMainEMPerfPollmodule.aSGenericNetworkIfIfPartialTable|IF-MIB.ifI
ndex|IF-MIB.ifInErrors|IF-MIB.ifOutErrors|IF-MIB.ifInUcastPkts|IF-MIB.
ifOutUcastPkts|IF-MIB.ifInDiscards|IF-MIB.ifOutDiscards|IF-MIB.ifInNUc
astPkts|IF-MIB.ifOutNUcastPkts|IF-MIB.ifInOctets|IF-MIB.ifOutOctets|IF
-MIB.ifInUnknownProtos
********|1|0|0|0|0|0|0|0|0|0|0|0
********|2|0|0|0|0|0|0|0|0|0|0|0
********|3|0|0|0|0|0|0|0|0|0|0|0
********|4|0|0|0|0|0|0|0|0|0|0|0
********|5|0|0|0|0|0|0|0|0|0|0|0
********|6|0|0|0|0|0|0|0|0|0|0|0
********|7|0|0|0|0|0|0|0|0|0|0|0
********|8|0|0|0|0|0|0|0|0|0|0|0
********|9|0|0|0|0|0|0|0|0|0|0|0
********|10|0|0|0|0|0|0|0|0|0|0|0
********|11|0|0|0|0|0|0|0|0|0|0|0
********|12|0|0|0|0|0|0|0|0|0|0|0
********|13|0|0|0|0|0|0|0|0|0|0|0
********|14|0|0|0|0|0|0|0|0|0|0|0
.
.
.

About Action Reports

File Export Properties dialog fields are updated when you click on Save; only the last update for a field is visible in the dialog. However, all display field updates are written to the Action Report.

The Action Report appears either because the action was processed or was interrupted.

The maximum number of characters in the report is limited to approximately 500,000.

A timestamped termination message is always written to the report, even if the report is "full."

Table of Contents

Managing the Performance of Cisco UGM Devices

Managing the Performance of
Cisco UGM Devices