Managing the Performance of Cisco UGM Devices

Note With Cisco UGM, you can select frequency of data polling and SNMP trap forwarding destinations. When making these selections, consider the number of managed ports and devices in your network, and be aware that your selections affect system performance and scalability.

With the Performance Manager, you can:

Collect selected performance attributes at specific times.
Store SNMP-polled performance attributes in the database of the attribute history server.
Enable or disable data collection (by device) at specified intervals.
View SNMP-polled performance data (stored in the attribute history server) by using the Performance Manager.
Performance polling is carried out only on devices in the normal (commissioned) state. Performance polling is not affected by the state of device components.
SNMP polling is turned on or off at the device level. All components in the device have polling either enabled or disabled with the host device. Specify polling intervals at the MIB attribute level; the intervals are global.

For example, if you specify 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.

Note Cisco UGM can monitor only predefined performance attributes. You cannot modify or add attributes.

Overview of SNMP Polling

This section contains the following:

About Adding SNMP MIB Attributes to be Polled

fiveMin, fifteenMin, thirtyMin, sixtyMin polling periods—SNMP MIB attributes 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 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 Performance Polling Configuration Dialog Tabs

Chassis and Chassis... tabs refer to the Cisco AS5300, AS5350, AS5400, AS5800, and AS5850 managed devices.
DS0 dialog tab refers to the DS0 channel.
DS1 and DS1... dialog tabs refer to the DS1 port, DS1 channel, and E1 port.
DS3 dialog tab refers to the DS3 port.
DSP dialog tab refers to the DSP port.
Ethernet Port dialog tab refers to the Ethernet, Fast Ethernet, and GigaBit Ethernet ports.
Modem dialog tab refers to the modem and universal ports.
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 "Exporting a 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 component 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, DSP ports, voice ports, modem ports, and universal ports.)

Note If the polling load in your system exceeds Cisco UGM capacity, frequent "Missed Poll" messages appear.

Selecting Performance Polling Intervals

Default performance polling intervals for sampling SNMP MIB attributes from the device and its components are:

Chassis—fifteen minutes
DS0, DS1, DS1..., DS3, DSP, Ethernet, Modem—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 Performance Polling Configuration Dialog Tabs" section for more details.

Step 3 Select 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.

Start performance polling as described in the "Starting and Stopping Performance Polling for the Device and its Components" section.

Starting and Stopping Performance Polling for the Device and its Components

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 From the devices listed on the left, select the devices to be polled.

Step 3 Select the performancePolling - ON option.

If you want to stop performance polling later, select the performancePolling - OFF option.

Step 4 Click the Save button.

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

Overview of Real-Time Display of SNMP-Polled Performance Data

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

Tip You cannot view some data online; export it to a flat file; then, view it.

Line Charts and Tables

With line charts and tables, you can view SNMP-polled device or card attribute data. Cisco UGM plots data corresponding to attributes that you select 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.

Overview of SNMP MIB Performance Attributes That You Can View

Table 6-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.
Average Busy 5 min	OLD-CISCO-CPU-MIB avgBusy5	Represents the 5-minute exponentially degraded 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
ISDN Cfg B-Channels in Use	CISCO-POP-MGMT-MIB cpmISDNCfgBChanInUse	Indicates the number of configured ISDN B-channels that are currently occupied by both analog and digital calls.
ISDN Cfg B-Channels in Use for Analog	CISCO-POP-MGMT-MIB cpmISDNCfgBChanInUseForAnalog	Indicates the number of configured ISDN B-channels that are currently occupied by analog calls.
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.
PPP Calls	CISCO-POP-MGMT-MIB cpmPPPCalls	Indicates the current number of active PPP calls received by the managed device.
V110 Calls	CISCO-POP-MGMT-MIB cpmV110Calls	Indicates the current number of active V.110 calls received by the managed device.
V120 Calls	CISCO-POP-MGMT-MIB cpmV120Calls	Indicates the current number of active V.120 calls received by the managed device.
Modem Calls Rejected	CISCO-POP-MGMT-MIB cpmModemCallsRejected	Number of modem calls rejected.
Modem Calls Cleared Abnormally	CISCO-POP-MGMT-MIB cpmModemCallsClearedAbnormally	Number of modem calls that cleared abnormally.
Modem Calls No Resource	CISCO-POP-MGMT-MIB cpmModemNoResource	Indicates the number of modem calls that were rejected because there was no modem available to handle the call.
Active DS0s	CISCO-POP-MGMT-MIB cpmActiveDS0s	Indicates the number of DS0s that are currently in use.

Table 6-2 Performance Attribute for the DS0 Port

Text Field

MIB Attribute Name

Description

Call Count

CISCO-POP-MGMT-MIB

cpmCallCount

Indicates the number of calls that have occupied this DS0.

Table 6-3 Performance Attributes for the DS1 Port

Text Field	MIB Attribute Name	Description
RFC1406dsx1ConfigTable
Line Status (from RFC1406dsx1ConfigTable)	RFC1406 dsx1LineStatus	Indicates the line status of the interface, and contains loopback, failure, received alarm, and transmitted alarm information.
Elapsed Seconds	RFC1406 dsx1TimeElapsed	Indicates the number of seconds elapsed since the beginning of the current polling period.
Valid Interval	RFC1406 dsx1ValidIntervals	Indicates the number of previous intervals for which valid data was collected.
RFC1406dsx1CurrentTable
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.
Controlled Slip Seconds	RFC1406 dsx1CurrentCSSs	Indicates the number of controlled slip seconds 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.
Bursty Errored Seconds	RFC1406 dsx1CurrentBESs	Indicates the number of bursty errored 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.
Path Code Violations	RFC1406 dsx1CurrentPCVs	Indicates the number of path coding violations encountered by a DS1 interface in the current fifteen-minute interval.
Degraded Minutes	RFC1406 dsx1CurrentDMs	Indicates the number of degraded minutes encountered by a DS1 interface in the current fifteen-minute interval.
RFC1406dsx1TotalTable
Errored Seconds	RFC1406 dsx1TotalESs	Indicates the total number of errored seconds encountered by a DS1 interface in the previous 24-hour interval.
Severely Errored Seconds	RFC1406 dsx1TotalSESs	Indicates the total number of severely errored seconds encountered by a DS1 interface in the previous 24-hour interval.
Severely Errored Framing Seconds	RFC1406 dsx1TotalSEFSs	Indicates the total number of severely errored framing seconds encountered by a DS1 interface in the previous 24-hour interval.
Unavailable Seconds	RFC1406 dsx1TotalUASs	Indicates the total number of unavailable seconds encountered by a DS1 interface in the previous 24-hour interval.
Controlled Slip Seconds	RFC1406 dsx1TotalCSSs	Indicates the total number of controlled slip seconds encountered by a DS1 interface in the previous 24-hour interval.
Path Code Violations	RFC1406 dsx1TotalPCVs	Indicates the total number of path coding violations encountered by a DS1 interface in the previous 24-hour interval.
Line Errored Seconds	RFC1406 dsx1TotalLESs	Indicates the total number of line errored seconds encountered by a DS1 interface in the previous 24-hour interval.
Bursty Errored Seconds	RFC1406 dsx1TotalBESs	Indicates the total number of bursty errored seconds encountered by a DS1 interface in the previous 24-hour interval.
Degraded Minutes	RFC1406 dsx1TotalDMs	Indicates the total number of degraded minutes encountered by a DS1 interface in the previous 24-hour interval.
Line Code Violations	RFC1406 dsx1TotalLCVs	Indicates the total number of line coding violations encountered by a DS1 interface in the previous 24-hour interval.
RFC1406dsx1FarEndCurrentTable
Elapsed Seconds	RFC1406 dsx1FarEndTimeElapsed	Indicates the number of seconds elapsed since the beginning of the far-end-current measurement period.
Valid Intervals	RFC1406 dsx1FarEndValidIntervals	Indicates the number of previous far end intervals for which valid data was collected.
Errored Seconds	RFC1406 dsx1FarEndCurrentESs	Indicates the number of far end errored seconds encountered by a DS1 interface in the current fifteen-minute interval.
Severely Errored Seconds	RFC1406 dsx1FarEndCurrentSESs	Indicates the number of far end severely errored seconds encountered by a DS1 interface in the current fifteen-minute interval.
Severely Errored Framing Seconds	RFC1406 dsx1FarEndCurrentSEFSs	Indicates the number of far end severely errored framing seconds encountered by a DS1 interface in the current fifteen-minute interval.
Unavailable Seconds	RFC1406 dsx1FarEndCurrentUASs	Indicates the number of unavailable seconds encountered by a DS1 interface in the current fifteen-minute interval.
Controlled Slip Seconds	RFC1406 dsx1FarEndCurrentCSSs	Indicates the number of far end controlled slip seconds encountered by a DS1 interface in the current fifteen-minute interval.
Line Errored Seconds	RFC1406 dsx1FarEndCurrentLESs	Indicates the number of far end line errored seconds encountered by a DS1 interface in the current fifteen-minute interval.
Path Code Violations	RFC1406 dsx1FarEndCurrentPCVs	Indicates the number of far end path coding violations encountered by a DS1 interface in the current fifteen-minute interval.
Bursty Errored Seconds	RFC1406 dsx1FarEndCurrentBESs	Indicates the number of far end bursty errored seconds encountered by a DS1 interface in the current fifteen-minute interval.
Degraded Minutes	RFC1406 dsx1FarEndCurrentDMs	Indicates the number of far end degraded minutes encountered by a DS1 interface in the current fifteen-minute interval.
RFC1406dsx1FarEndTotalTable
Errored Seconds	RFC1406 dsx1FarEndTotalESs	Indicates the number of far end errored seconds encountered by a DS1 interface in the previous 24-hour interval.
Severely Errored Seconds	RFC1406 dsx1FarEndTotalSESs	Indicates the number of far end severely errored seconds encountered by a DS1 interface in the previous 24-hour interval.
Severely Errored Framing Seconds	RFC1406 dsx1FarEndTotalSEFSs	Indicates the number of far end severely errored framing seconds encountered by a DS1 interface in the previous 24-hour interval.

Table 6-4 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 framing 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.

Table 6-5 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.
Last Change	IF-MIB ifLastChange	Indicates the value of the sysUpTime variable at the time when the interface entered its current operational state. If the current state was entered before the last Cisco UGM reboot, this field is 0.
Out Queue Length	IF-MIB ifOutQLen	Indicates the number of packets in the output packet queue.
In Multicast Pkts	IF-MIB ifInMulticastPkts	Indicates the number of packets delivered by this sublayer to a higher sublayer, which were addressed to a multicast address at this sublayer.
In Broadcast Pkts	IF-MIB ifInBroadcastPkts	Indicates the number of packets delivered by this sublayer to a higher sublayer, which were addressed to a broadcast address at this sublayer.
Out Multicast Pkts	IF-MIB ifOutMulticastPkts	Indicates the total number of packets that higher-level protocols requested be transmitted, and which were addressed to a multicast address at this sublayer. This number includes packets that were discarded or not sent.
Out Broadcast Pkts	IF-MIB ifOutBroadcastPkts	Indicates the total number of packets that higher-level protocols requested be transmitted, and which were addressed to a broadcast address at this sublayer. This number includes packets that were discarded or not sent.
HC In Octets	IF-MIB ifHCInOctets	Indicates the total number of octets received on this interface (including framing characters).
HC In Ucast Pkts	IF-MIB ifHCInUcastPkts	Indicates the number of packets (not addressed to a multicast or broadcast address) delivered by this sublayer to a higher sublayer This object is a 64-bit version of ifInUcastPkts.
HC In Multicast Pkts	IF-MIB ifHCInMulticastPkts	Indicates the number of packets delivered by this sublayer to a higher sublayer, which were addressed to a multicast address at this sublayer. This object is a 64-bit version of ifInMulticastPkts.
HC In Broadcast Pkts	IF-MIB ifHCInBroadcastPkts	Indicates the number of packets delivered by this sublayer to a higher sublayer, which were addressed to a broadcast address at this sublayer. This object is a 64-bit version of ifInBroadcastPkts.
HC Out Octets	IF-MIB ifHCOutOctets	Indicates the total number of octets (including framing characters) transmitted out of the interface. This object is a 64-bit version of ifOutOctets.
HC Out Ucast Pkts	IF-MIB ifHCOutUcastPkts	Indicates the total number of packets that higher-level protocols requested be transmitted, and which were not addressed to a multicast or broadcast address at this sublayer. This number includes packets that were discarded or not sent. This object is a 64-bit version of ifOutUcast Pkts.
HC Out Multicast Pkts	IF-MIB ifHCOutMulticastPkts	Indicates the total number of packets that higher-level protocols requested be transmitted, and which were addressed to a multicast address at this sub-layer. This number includes packets that were discarded or not sent. This object is a 64-bit version of ifOutMulticastPkts.
HC Out Broadcast Pkts	IF-MIB ifHCOutBroadcastPkts	Indicates the total number of packets that higher-level protocols requested be transmitted, and which were addressed to a broadcast address at this sub-layer. This number includes packets that were discarded or not sent. This object is a 64-bit version of ifOutBroadcastPkts.
Interface Speed	IF-MIB ifSpeed	Represents an estimate of the interface's current bandwidth in bits per second.

Table 6-6 Performance Attributes for Modem and Universal Ports

Text Field	MIB Attribute Name	Description
Ring No Answer	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.
Modem State	CISCO-MODEM-MGMT-MIB cmState	Indicates the current state of the modem: unknown—the current state of the modem is unknown. onHook—the condition similar to hanging up a telephone receiver. The call cannot enter a connected state when the modem in onHook. offHook—the condition similar to picking up a telephone receiver to dial or answer a call. connected—the modem is in a state where it can transmit or receive data over the communications line. busiedOut—the modem has been taken out of service and cannot send or receive calls. disabled—the modem is in a reset state and non-functional. bad—the modem is suspected or proven to be bad. The operator can take it out of service. loopback—the modem is currently running back-to-back loopback testing. downloadFirmware—the modem is currently downloading firmware. downloadFirmwareFailed—the modem is not operational because the firmware download failed.
Call Direction	CISCO-MODEM-MGMT-MIB cmCallDirection	Indicates the direction of the current or previous call (incoming or outgoing).
Call Phone Number	CISCO-MODEM-MGMT-MIB cmCallPhoneNumber	Indicates the dialed outgoing phone number of the current or previous call.
Caller ID	CISCO-MODEM-MGMT-MIB cmCallerID	Identifies the source of the current or previous call.
Manufacturer ID	CISCO-MODEM-MGMT-MIB cmManufacturerID	Identifies the modem with a hardware revision number, firmware revision number, feature set, and serial number.

Table 6-7 Performance Attributes for the DSP Port

Text Field	MIB Attribute Name	Description
CISCO-DSP-MGMT-MIB-cdspStatusTable
Total Channels	CISCO-DSP-MGMT-MIB cdspTotalChannels	The total number of channels in the DSP. This value is predetermined by the DSP functionality upon initialization. 0 indicates that the channelized DSP mode is turned off.
Channels in Use	CISCO-DSP-MGMT-MIB cdspInUseChannels	The number of channels reserved for serving calls. This value is incremented when the DSP channel is reserved for call setup and is decremented after the DSP channel is free (when the call is disconnected). Note Channels In Use/Total x 100% = DSP utilization.
Active Channels	CISCO-DSP-MGMT-MIB cdspActiveChannels	The number of channels used by active calls to process media stream. This value is decremented after the reserved DSP channel enters call connection state and is decremented after the call is disconnected. Note If the difference between the Active Channels and Channels In Use is greater than 2, you have dangling channels.

Overview of SNMP MIB Performance Attributes that You Cannot View

You cannot view the following attributes by using the Performance Manager; the attributes are uncharted data. Export the data to flat files (see the "Exporting a File" section).

Note This section includes attribute information from the Others tab in the Global Performance Polling Configuration dialog box. In order to view this data, export it to a flat file.

The default polling period for items under the Others tab is None.

Table 6-8 Performance Attributes Under the Others Tab

Text Field	MIB Attribute Name	Description
CISCO-MEMORY-POOL-MIB
ciscoMemoryPoolTable		Contains memory pool monitoring entries.
Memory Pool Name	ciscoMemoryPoolName	Identifies the memory pool.
Memory Pool Free	ciscoMemoryPoolFree	Indicates the number of bytes from the memory pool that is currently unused on the managed device.
Memory Pool Used	ciscoMemoryPoolUsed	Indicates the number of bytes from the memory pool that is currently in use by applications on the managed device.
CISCO-ENVMON-MIB
ciscoEnvMonSupplyStatusTable		Contains power supply status entries maintained by the environmental monitor card.
ciscoEnvMonSupplyStatusDescr		Describes the power supply being monitored.
CISCO-PROCESS-MIB
cpmCPUTotalTable		Contains overall CPU statistics.

Table 6-9 Performance Attributes for Export Only

Text Field	MIB Attribute Name	Description
Call Phone Number	CISCO-MODEM-MGMT-MIB cmCallPhoneNumber	Indicates the dialed outgoing phone number of the current or previous call.
Caller ID	CISCO-MODEM-MGMT-MIB cmCallerID	Identifies the source of the current or previous call.
Manufacturer ID	CISCO-MODEM-MGMT-MIB cmManufacturerID	Identifies the modem with a hardware revision number, firmware revision number, feature set, and serial number.

Text Field

MIB Attribute Name

Description

Call Phone Number

CISCO-MODEM-MGMT-MIB

cmCallPhoneNumber

Indicates the dialed outgoing phone number of the current or previous call.

Caller ID

CISCO-MODEM-MGMT-MIB

cmCallerID

Identifies the source of the current or previous call.

Manufacturer ID

CISCO-MODEM-MGMT-MIB

cmManufacturerID

Identifies the modem with a hardware revision number, firmware revision number, feature set, and serial number.

Viewing SNMP-Polled 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 list in the left panel, click the performance data that you want to view.

See the "Line Charts and Tables" 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 component 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

About Action Reports

File Export Properties dialog fields are updated when you click Save; only the last update for a field is visible in this dialog box. However, all display field updates appear in the Action Report, which 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."

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>

Overview of Near Real-Time Display of Redundancy Attributes

Cisco UGM supports these features in the following devices:

Cisco AS5800
Cisco AS5850

Redundancy and split mode functionality is also described in:

Overview of Redundancy MIB Attributes

Table 6-10 Cisco AS5800 Redundancy Dialog Box MIB Attribute

Text Field	MIB Attribute Name	Description
Redundancy Status	RedundancyStatus CISCO-C8500-REDUNDANCY-MIB	The operational status of a card.

Text Field

MIB Attribute Name

Description

Redundancy Status

RedundancyStatus

CISCO-C8500-REDUNDANCY-MIB

The operational status of a card.

Table 6-11 Cisco AS5850 Redundancy Dialog Box MIB Attributes

Text Field	MIB Attribute Name	Description
Configuration Tab
Redundancy Mode	cRFCfgRedundancyMode CISCO-RF-MIB	Indicates the type of redundancy currently in effect.
Redundancy Mode Description	cRFCfgRedundancyModeDescr CISCO-RF-MIB	Describes the redundancy mode indicated by cRFCfgRedundancyMode.
Split Mode	cRFCfgSplitMode CISCO-RF-MIB	Indicates whether redundant units can synchronize with each other: False—Communication is permitted, and the standby unit is reset to recover. True—Communication is not permitted, and the standby unit will not recover.
Maintenance Mode	cRFCfgMaintenanceMode CISCO-RF-MIB	Indicates whether redundant units can synchronize with each other: False—Communication is permitted, and the redundant system is in a normal (non-maintenance) mode. True—Communication is not permitted, and the redundant system is in a maintenance mode.
Notifications Enabled	cRFCfgNotifsEnabled CISCO-RF-MIB	Allows the enabling/disabling of redundancy subsystem notifications.
Notification Timer	cRFCfgNotifTimer CISCO-RF-MIB	When the standby unit progresses to the "standbyHot" state, asynchronous messages are sent from the active device to the standby device. These messages must be acknowledged. If the active device receives the acknowledgement during the time period specified, progression is normal. If the time ends without an acknowledgement, a switch of activity occurs.
Minimum Notification Timer	cRFCfgNotifTimerMin CISCO-RF-MIB	The minimum acceptable value for the notification timer.
Maximum Notification Timer	cRFCfgNotifTimerMax CISCO-RF-MIB	The maximum acceptable value for the notification timer.
Keep Alive Threshold	cRFCfgKeepaliveThresh CISCO-RF-MIB	Indicates the number of lost keep-alive attempts tolerated before a failure condition is declared and a SWACT notification is sent.
Minimum Keep Alive Threshold	cRFCfgKeepaliveThreshMin CISCO-RF-MIB	Indicates the minimum number of keep-alive attempts.
Maximum Keep Alive Threshold	cRFCfgKeepaliveThreshMax CISCO-RF-MIB	Indicates the maximum number of keep-alive attempts.
Keep Alive Timer	cRFCfgKeepaliveTimer CISCO-RF-MIB	The redundancy subsystem expects to receive a keep-alive request within this time period. If a keep-alive request is not received within this time, a SWACT notification is sent.
Minimum Keep Alive Timer	cRFCfgKeepaliveTimerMin CISCO-RF-MIB	The minimum acceptable value for the cRFCfgKeepaliveTimer object.
Maximum Keep Alive Timer	cRFCfgKeepaliveTimerMax CISCO-RF-MIB	The maximum acceptable value for the cRFCfgKeepaliveTimer object.
Status Tab
Unit Id	cRFStatusUnitId CISCO-RF-MIB	Represents a unique identifier for this device. This identifier is read from the device backplane.
Redundancy Status	RFState CISCO-RF-MIB	Indicates the current state of the redundancy subsystem: notKnown—The state is unknown. disabled—Redundancy is not operational on this device. initialization—Necessary system services are being established on this device. negotiation—The peer unit is going through discovery and negotiation. standbyCold—The standby unit is receiving redundancy notification. standbyColdConfig—The standby device's startup configuration is being updated from the active device's running configuration. standbyColdFileSys—The standby device's file system is being updated from the active device. standbyColdBulk—Data is being synchronized between the active and standby devices. standbyHot—Data is being synchronized between the active and standby devices; the standby device is ready to take control. activeFast—Indicates call maintenance efforts during a SWACT.
		activeDrain—Indicates cleanup operations. activePreconfig—Indicates that the device is active but has not read its configuration. activePostconfig—Indicates that the device is active and is processing its configuration. active—Indicates that the device is active and processing calls.
Peer Unit Id	cRFStatusPeerUnitId CISCO-RF-MIB	Represents a unique identifier for the peer device. This identifier is read from the device backplane.
Peer Unit State	cRFStatusPeerUnitState CISCO-RF-MIB	The current redundancy state on the peer unit.
Primary Mode	cRFStatusPrimaryMode CISCO-RF-MIB	Indicates if this device is the primary (True) or secondary device (False). Primary and secondary modes are not synonymous with active and standby modes. A primary or secondary device can be in either active or standby mode. The primary device takes precedence over the secondary device when negotiating activity (usually at initialization).
Duplex Mode	cRFStatusDuplexMode CISCO-RF-MIB	Indicates if the redundant peer unit has been detected: True—the peer has been detected. False—the peer has not been detected.
Manual SWACT Inhibit	cRFStatusManualSwactInhibit CISCO-RF-MIB	Indicates if a manual switch of activity is allowed: True—the manual switch is not allowed. False—the manual switch is allowed.
Last SWACT Reason Code	cRFStatusLastSwactReasonCode CISCO-RF-MIB	Indicates the reason for the last switch in activity.

Checking Redundancy ID of Cisco AS5800 and AS5850 Devices

Step 1 In the Map Viewer Physical view, right-click the redundancy container object.

Step 2 Select Open Redundancy Properties...

For Cisco AS5800 devices, the dial shelf ID (entered when redundancy was configured) appears.

For Cisco AS5850 devices, the unique backplane identifier (read automatically) appears.

Checking the Redundancy Status of a Cisco AS5800 Device

Step 1 In the Map Viewer, right-click the device object.

Step 2 Select Chassis > Open Redundancy Status...

One of these values appears:

Active
Standby
Not configured—indicates that the device is configured for split mode operation
N/A—indicates that the IOS image installed on the device does not support redundancy

Checking the Redundancy Configuration of a Cisco AS5850 Device

Step 1 In the Map Viewer, right click the device object.

Step 2 Select Chassis > Open Redundancy Status and Configuration...

Step 3 Click the Configuration tab.

The values in this dialog tab are described in the "Overview of Redundancy MIB Attributes" section.

Checking the Redundancy Status of a Cisco AS5850 Device

Step 1 In the Map Viewer, right click the device object.

Step 2 Select Chassis > Open Redundancy Status and Configuration...

Step 3 Click the Status tab.

The values in this dialog tab are described in the "Overview of Redundancy MIB Attributes" section.

Overview of Modem and Universal Port Management

Cisco UGM manages modems by periodically polling modems on device objects in normal state. The current state of a modem is defined by the CISCO-MODEM-MGMT-MIB.cmState object.

About Modem States

This section describes states implemented by the CISCO-MODEM-MGMT-MIB.

unknown—Indicates that the current state of the modem is unknown.
onHook—Indicates a condition similar to hanging up a telephone receiver. The call cannot enter a connected state when the modem is onHook.
offHook—Indicates a condition similar to picking up a telephone receiver in order to dial or answer a call.
connected—Indicates that the modem can transmit or receive data over the communications line.
busiedOut—Indicates that the modem is taken out of service and cannot make outgoing calls or receive incoming calls.
disabled—Indicates that the modem is in a reset state and nonfunctional.
bad—Indicates that the modem is suspected or proven to be bad.
loopback—Indicates that the modem is running back-to-back loopback testing.
downloadFirmware—Indicates that the modem is currently downloading firmware.
downloadFirmwareFailed—Indicates that the modem is not operational because of a failed attempt to download firmware.

Note For an explanation of modem states see the "Setting Modem-Level Status Polling" section.

About Modem Conditions

When a modem is operating, it is in one of these states:

onHook
offHook
connected

When a modem has problems, it is in one of these states:

unknown
bad
downloadFirmwareFailed.

When a modem is offline, it is in one of these states:

busiedOut
disabled
loopback
downloadFirmware.

About the Modem Management Alarm

Cisco UGM's modem state polling feature identifies and monitors modem-related events and raises an alarm if necessary. An operational modem does not have any alarms raised against it.

A modem management alarm generates this message:

Modem/UP is offline in state <STATE>.

A warning-severity alarm is raised if a modem goes from the operational or problematic condition to the offline condition.
A minor-severity alarm is raised if a modem goes from the operational or offline condition to the problematic condition.

The current alarm is cleared if the modem changes state and moves to a different condition.

Modem states are described in the "About Modem States" section, and modem conditions are described in the "About Modem Conditions" section.

Setting Modem-Level Status Polling

Note In the Cisco Universal Gateway Manager Settings dialog box, the values you enter depend on the total number of managed devices in your network. You may need to change this value a few times in order to determine the optimum setting for your network.

Step 1 In Map View, choose ASEMSConfig > EMS > Settings.

Step 2 In the Modem-Level Status Polling field, enter an integer that is 300 seconds or larger. The default is 305 seconds.

This value sets the modem status polling interval for all modems installed in Cisco UGM-managed devices.

Step 3 Click Save.

Overview of Controller Logging Levels

When the IOSConfigCtrl, ASMainCtrl, ASFaultStandAlone, and ASPerformInv controllers start, they read values from the database and set their logging levels accordingly.

These logging levels are stored even if Cisco EMF and Cisco UGM stop operation. The logging levels are erased only if you reset the database.

Tip You can set logging levels for several controllers at the same time by selecting their corresponding objects from the list in the left pane of the dialog box.

Setting Controller Logging Levels

The Controller Logging Level dialog box allows you to change the logging levels on the ASMainCtrl, IOSConfigCtrl, ASFaultStandAlone, and ASPerformInv controllers.

Step 1 From the Map Viewer, double-click LoggingConfiguration.

The Controller Logging Level dialog box opens.

Step 2 Right-click one or more of the controller objects listed in the left panel:

ASMainCtrlLog
IOSConfigCtrlLog
ASFaultStandAloneLog
ASPerformInvLog

Step 3 Select Change Controller Logging Level.

Step 4 Select On or Off values for each of the following:

Debug Flag

When you select On, the debug values are written to the controller log selected earlier.

When you select Off, the debug values for this controller log are ignored.

Info Flag

When you select On, the debug values are written to the controller log selected earlier.

When you select Off, the debug values for this controller log are ignored.

Warning Flag

When you select On, the debug values are written to the controller log selected earlier.

When you select Off, the debug values for this controller log are ignored.

Error Flag

When you select On, the debug values are written to the controller log selected earlier.

When you select Off, the debug values for this controller log are ignored.

Note When you first start Cisco UGM, the following values are in effect:
Debug and Info flags are Off
Warning and Error flags are On

Step 5 Click Save.

The changes take effect immediately.

About System Log Files

Each controller creates a log file:

ASMainCtrl.log
IOSConfigCtrl.log
ASFaultStandAlone.log
ASPerformInv.log

These log files are located in CEMFROOT/logs.

When a log file reaches its maximum size, its content is moved into a file with the same name and .old extension. (Example: ASMainCtrl.old.)

Modifying the Size of Log Files

Step 1 Locate the corresponding .ini file in the CEMFROOT/config/init/ directory.

Step 2 In the logger section of the .ini file, enter the size (in KBytes):

[logger] #include "loggercommon.include" loggingName = xxxxCtrl maxLogfileSize =5000

(In this example, the user specified a 5 MB log file.)

Step 3 Stop and restart Cisco EMF.

When the .log file reaches the maximum size that you specified, it is archived to a corresponding .old file, and a new .log file is created.

Table of Contents

Managing the Performance of Cisco UGM-Controlled Devices

Overview of Performance Management Features

Overview of SNMP Polling

About Adding SNMP MIB Attributes to be Polled

Information on Performance Polling Configuration Dialog Tabs

About Polling Intervals and the Number of Devices Polled

Selecting Performance Polling Intervals

Starting and Stopping Performance Polling for the Device and its Components

Overview of Real-Time Display of SNMP-Polled Performance Data

Line Charts and Tables

Overview of SNMP MIB Performance Attributes That You Can View

Overview of SNMP MIB Performance Attributes that You Cannot View

Viewing SNMP-Polled Performance Data

Overview of the Performance Data Export File

Location of the Performance Data Export Files

Example of Performance Data File Location

About Action Reports

Exporting a File

Example: Performance Export Data Format

Overview of Near Real-Time Display of Redundancy Attributes

Overview of Redundancy MIB Attributes

Checking Redundancy ID of Cisco AS5800 and AS5850 Devices

Checking the Redundancy Status of a Cisco AS5800 Device

Checking the Redundancy Configuration of a Cisco AS5850 Device

Checking the Redundancy Status of a Cisco AS5850 Device

Overview of Modem and Universal Port Management

About Modem States

About Modem Conditions

About the Modem Management Alarm

Setting Modem-Level Status Polling

Overview of Controller Logging Levels

Setting Controller Logging Levels

About System Log Files

Modifying the Size of Log Files

Managing the Performance of
Cisco UGM-Controlled Devices