User Guide for the Cisco Application Networking Manager 5.2.2
Monitoring Your Network
Downloads: This chapterpdf (PDF - 2.8MB) The complete bookPDF (PDF - 28.37MB) | Feedback

Monitoring Your Network

Table Of Contents

Monitoring Your Network

Setting Up Devices for Monitoring

Device Monitoring Features

Using Dashboards to Monitor Devices and Virtual Contexts

ACE Dashboard

Device Information Table

License Status Table

High Availability Table

ACE Device Configuration Summary Table

Context With Denied Resource Usage Detected Table

Device Resource Usage Graph

Top 10 Current Resources Table

Control Plane CPU/Memory Graphs

ACE Virtual Context Dashboard

ACE Virtual Context Device Configuration Summary Table

Context With Denied Resource Usage Detected Table

Context Resource Usage Graph

Load Balancing Servers Performance Graphs

ANM Group Dashboard

Managed Devices Table

Context With Denied Resource Usage Detected Table

ANM Group Device Configuration Summary Table

Top 10 Current Resources Table

Latest 5 Alarms Notifications Table

Latest 5 Critical Events Table

Contexts Performance Overview Graph

Monitoring Device Groups

Monitoring Devices

Monitoring the System

Monitoring Resource Usage

Monitoring Virtual Context Resource Usage

Monitoring System Traffic Resource Usage

Monitoring System Non-Connection Based Resource Usage

Monitoring Traffic

Displaying Device-Specific Traffic Data

Monitoring Load Balancing

Monitoring Load Balancing on Virtual Servers

Monitoring Load Balancing on Real Servers

Monitoring Load Balancing on Probes

Monitoring Load Balancing Statistics

Monitoring Application Acceleration

Displaying the Polling Status of All Managed Objects

Setting Polling Parameters

Enabling Polling on Specific Devices

Disabling Polling on Specific Devices

Enabling Polling on All Devices

Disabling Polling on All Devices

Configuring Historical Trend and Real Time Graphs for Devices

Exporting Historical Data

Monitoring Events

Configuring Alarm Notifications on ANM

Displaying Alarm Notifications

Displaying Alarms in ANM

Displaying Email Notifications

Displaying Traps

Configuring SMTP for Email Notifications

Displaying Network Topology Maps

Testing Connectivity


Monitoring Your Network



Note When naming ACE objects (such as a real server, virtual server, parameter map, class map, health probe, and so on), enter an alphanumeric string of 1 to 64 characters, which can include the following special characters: underscore (_), hyphen (-), and dot (.). Spaces are not allowed.

If you are using ANM with an ACE module or ACE appliance and you configure a named object at the ACE CLI, keep in mind that ANM does not support all of the special characters that the ACE CLI allows you to use when configuring a named object. If you use special characters that ANM does not support, you may not be able to import or manage the ACE using ANM.


The ANM Monitor function allows you to monitor key areas of system usage. The following functionality is provided under Monitor in ANM:

Dashboards—Operate as a central location for you to view monitoring results and track potential issues. There are three types of dashboards in ANM: ANM/Group Dashboard, ACE Dashboard, and Context Dashboard. Each dashboard provides quick access to all relevant monitoring pages. See the "Using Dashboards to Monitor Devices and Virtual Contexts" section.

Events—Lists events originated from devices through syslog, SNMP traps. See the "Monitoring Events" section.

Alarm Notifications—Allows you to define thresholds and view alarms. See the "Configuring Alarm Notifications on ANM" section and the "Displaying Alarm Notifications" section.

Settings—Allows you to do the following:

Display the current polling status of all the objects that ANM manages. See the "Displaying the Polling Status of All Managed Objects" section.

Set global polling and SMTP configurations. See the "Setting Polling Parameters" section.

Export historical data. See the "Exporting Historical Data" section.

Topology maps—Allows you to display a network topology map based on a selected virtual or real server. See the "Displaying Network Topology Maps" section.

Tools—Allows you to verify connectivity (using the ping command) between a virtual context and an IP address that you specify. See the "Testing Connectivity" section.


Note When ANM is unable to retrieve information for a monitored statistic, it displays one of the following status conditions in the table cell:

N/A (Not Available)—Indicates that ANM was unable to poll the device for the information for one of the following reasons:

ANM is experiencing polling errors with the device.

ANM is not able to communicate with the device.

If a poll was recently initiated, ANM is in the process of gathering information from the device.

Not Supported—Indicates that the device does not have the capability to provide the information. This condition can be caused when the device does not have the necessary SNMP instrumentation. It is possible that another similar device type is able to provide the statistical information because it has been updated with the necessary SNMP instrumentation.

Not Applicable—Indicates that the particular information is not valid or not applicable for the device type, or ANM is unable to retrieve the information from the device because the information is not available through SNMP for the device type.


Before using the Monitoring functions, make sure that your devices are properly configured for polling (see the "Setting Up Devices for Monitoring" section).

Setting Up Devices for Monitoring

In order for ANM to successfully monitor your devices, you must configure the devices correctly for polling as show in Table 17-1.

Table 17-1 Configuring Devices for Monitoring 

Device Type
How to Configure
Parameters to Configure

ACE modules

Configure parameters on the Admin context only.

All devices must have a routable IP address from the ANM.

The management policy with the SNMP protocol must be associated to the IP address.

You must enable SNMPv2c with a matching SNMP community string between ANM and the devices to be polled. (See the "Configuring Virtual Contexts" section.)

Before using the Monitoring functions, you must enable monitoring on all devices that you want ANM to monitor (see the "Setting Polling Parameters" section).

ACE appliances

Configure parameters on the Admin context only.

CSS

Configure parameters on the CSS devices that you want ANM to monitor. You cannot use ANM to configure the CSS.

All devices must have a routable IP address from the ANM.

For CSS devices, you must enable SNMPv2c with a matching SNMP community string between ANM and the devices to be polled. (See the "Configuring CSS Primary Attributes" section.)

For CSM devices, you must enable SNMPv2c with a matching SNMP community string on the Cat6K chassis in which the CSM resides. (See the "Configuring CSM Primary Attributes" section.)

Before using the Monitoring functions, you must enable monitoring on all devices that you want ANM to monitor (see the "Setting Polling Parameters" section).

CSM

Configure parameters on the Cat6K chassis (in which the CSM resides) that you want ANM to monitor. You cannot use ANM to configure the CSM.


Related Topics

Device Monitoring Features

Using Dashboards to Monitor Devices and Virtual Contexts

Monitoring Devices

Device Monitoring Features

ANM provides several features that allow you to monitor your devices when you click Monitor:

Dashboards—Operate as a central location for you to view device and context monitoring results and track potential issues. There are three types of Dashboards in ANM: ANM/Group Dashboard, ACE Dashboard, and ACE Virtual Context Dashboard. Each Dashboard provides quick access to all relevant monitoring pages. See the "Using Dashboards to Monitor Devices and Virtual Contexts" section.

System View—Provides device information and a general overview of your system as a whole, including High Availability (HA) information and licensing information. System View is available only for CSS and CSM devices. See the "Monitoring the System" section.

Resource Usage—Provides resource usage information on connections and features. See the "Monitoring Resource Usage" section. Resource usage is not available for CSS or CSM devices.

Traffic Summary—Provides traffic information for your devices. Traffic Summary is available only for the ACE module, ACE appliance, and CSS. See the "Monitoring Traffic" section.

Load Balancing—Provides virtual server information and load balancing statistics. See the "Monitoring Load Balancing" section and the "Monitoring Load Balancing Statistics" section.

Application Acceleration—Displays optimization statistics for ACE appliances on which you have configured application acceleration functions. See the "Monitoring Application Acceleration" section. This feature is only available on ACE appliances.

Polling Settings—Allows you to set polling parameters. See the "Setting Polling Parameters" section.

Historical Graphs—Allows you to view historical data for a group of monitoring page statistics. See the "Configuring Historical Trend and Real Time Graphs for Devices" section.

Using Dashboards to Monitor Devices and Virtual Contexts

ANM dashboards allow for faster and more accurate assessment and analysis of device and virtual context health and usage, as well as performance. Corresponding monitoring views allow for quick access to details for further investigation into potential problems highlighted in the dashboards. Graphs, as well as monitoring screens, allow you to view historical data and compare the performance with the peer objects.


Note All client browsers require that you enable Adobe Flash Player 9 to properly display the monitoring graphs provided in ANM.


Dashboards in ANM provide:

A central location for you to view monitoring highlights.

Emphasis on potential issues that require your attention.

Quick access to relevant ANM pages for more detailed monitoring data.

In each dashboard, there are a relevant set of dashboard panes. The information shown in the dashboard panes differ based on the device or groups that you select in the device tree. The dashboard panes are moveable element inside the dashboard that can be minimized/maximized, moved, and, if desired, removed from view. You can also display a larger (full) window view for a dashboard window.


Note Changes made to dashboard layout or pane selections are only applicable for the current session. Those changes are not maintained by ANM the next time you access an ANM dashboard.


The dashboard tables and graphs autorefresh every two minutes. If desired, you can disable autofreshing by clicking the Pause Autofresh button in the upper-right corner of the dashboard.


Note All dashboard contents are under Role-Based Access Control (RBAC). Options will be grayed or not displayed if proper permission has not been granted to the logged in user by the administrator. See the "How ANM Handles Role-Based Access Control" section for more information about RBAC in ANM.


This section includes the following topics:

ACE Dashboard

ACE Virtual Context Dashboard

ANM Group Dashboard

ACE Dashboard

The ACE Dashboard displays the information related to the ACE module or ACE appliance that is selected in the device tree. You access the ACE Dashboard by selecting Monitor > Devices > ACE > Dashboard.

Figure 17-1 illustrates the individual components of the ACE Dashboard.


Note The ANM software version that displays across the top of the window varies depending on your version of ANM.


Figure 17-1 Example ACE Device Dashboard

To enhance your viewing of the monitoring information in the ACE Dashboard, you can perform the following actions:

Click and drag an individual dashboard pane to move it to another location within the ACE Dashboard.

Use the Collapse/Expand buttons at the top right side of each dashboard pane to minimize/maximize a pane within the ACE Dashboard.

Click the Remove button to remove a dashboard pane from the ACE Dashboard. Click the Bring Back Closed Dashboard Panes button at the top of the ACE Dashboard to open the closed dashboard pane.


Note When you close any of the panes in a dashboard by clicking the Remove button, all of the headers in the other dashboard panes turn black to indicate that a pane has been closed. To return the dashboard panes to normal, click the Bring Back Closed Dashboard Panes button to reload the removed dashboard pane.


Click the Screen View (Full)/Screen View (Normal) buttons to display a larger (full) window view for the ACE Dashboard.

Changes made to dashboard layout or pane selections are only applicable for the current session. Those changes are not maintained by ANM the next time you access the ACE Dashboard.

The components of the individual ACE Dashboard panes are described in the following sections.

Device Information Table

License Status Table

High Availability Table

ACE Device Configuration Summary Table

Context With Denied Resource Usage Detected Table

Device Resource Usage Graph

Top 10 Current Resources Table

Control Plane CPU/Memory Graphs

Device Information Table

The Device Information table lists the details that will identify the status of the selected ACE. It includes the following fields:

Host Name—Host name of the ACE module or ACE appliance.

Device Status—Device reachability status through SNMP and XML connectivity (Up or Down).

Device Type—ACE device specifics for the ACE module or ACE appliance.

Management IP—Management IP address of the admin virtual context.

Number of Contexts—Number of configured contexts, including the Admin context and configured user contexts.

Software Version—Release software version of the ACE module or ACE appliance.

Note When you import the ACE module or ACE appliance software version A5(2.0) or later with the NPE software, you will see NPE displayed with the ACE version in the version column.

Last Boot Reason—Reason for the last reboot of the ACE (if available).

Uptime—Length of time that the ACE has been up and running.

The data shown in this table is collected during device discovery as well as during periodic monitor polling. The timestamp shown in the status bar is from the last polled time of the Admin virtual context.

License Status Table

The License Status table lists the license status of the selected ACE device. ANM uses the ACE show license status CLI command to obtain the license details. The timestamp shown in the status bar is from the last polled time of the Admin virtual context.

High Availability Table

The HA Peer Information table lists the details of the HA peer, if configured in HA mode. It includes the following information:

HA/FT Interface State—State of the local ACE. See the "ACE High Availability Polling" section.

My IP Address—IP address of the local ACE.

Peer IP Address—IP address of the peer ACE.

Software Compatibility—Status of whether the software version of the local ACE and the software version of the peer ACE are compatible. Possible states are the INIT, COMPATIBLE, or INCOMPATIBLE state.

License Compatibility—Status of whether the license of the local ACE and the license of the peer ACE are compatible. Possible states are the INIT, COMPATIBLE, or INCOMPATIBLE state.

Number of FT Groups—Number of configured FT groups.

Number of Heartbeats Transmitted—Total number of heartbeat packets transmitted.

Number of Heartbeats Received—Total number of heartbeat packets received.

This data is collected during periodic monitoring polling. The timestamp shown in the status bar is from the last polled time of the Admin virtual context.

ACE Device Configuration Summary Table

The Device Configuration Summary table displays the following information:

Virtual Servers—Total count of virtual servers configured in all contexts and the count of virtual servers that are in the In Service or Out of Service state. ANM also identifies virtual servers that have a Status Not Available state (due to polled failing, polled disable, and so on) and have a Status Not Supported state (due to a lack of ACE SNMP support). A hyperlink enables you to view load balancing virtual server monitoring information based on the identified state (see the "Monitoring Load Balancing on Virtual Servers" section). For example, if you click the In Service hyperlink, you will see only the virtual servers that are currently in service.

Real Servers—Total count of real servers configured in all contexts and the count of real servers that are in In Service and Out of Service. A hyperlink enables you to view load balancing real server monitoring information based on the identified state (see the "Monitoring Load Balancing on Real Servers" section). For example, if you click the In Service hyperlink, you will see only the real servers that are currently in service.

Probes—Total count of probes configured in all contexts and the count of probes that are in the In Service and Out of Service state. A hyperlink enables you to view load balancing probe monitoring information based on the identified state (see the "Monitoring Load Balancing on Probes" section). For example, if you click the In Service hyperlink, you will see only the probes that are currently in service.

Gigabit Ethernets—(ACE appliance only) Total count of Gigabit Ethernet physical interfaces configured on the ACE appliance based on their operational status of Up and Down. A hyperlink enables you to view traffic summary information based on the identified state (see the "Monitoring Traffic" section). For example, if you click the Up hyperlink, you will see only the Gigabit Ethernet physical interfaces that currently have an operational status of Up.

VLANs—Total count of VLANs configured and the count of VLANs based on operational status - Up and Down. A hyperlink enables you to view traffic summary information based on the identified state (see the "Monitoring Traffic" section). For example, if you click the Up hyperlink, you will see only the VLAN interfaces that currently have an operational status of Up.

Port Channels—(ACE appliance only) Total count of port channels configured on the ACE appliance based on their operational status of Up and Down. A hyperlink enables you to view traffic summary information based on the identified state (see the "Monitoring Traffic" section). For example, if you click the Up hyperlink, you will see only the port channels that currently have an operational status of Up.

BVIs—Total count of BVI interfaces and the count of BVI interfaces based on their operational status of Up and Down. A hyperlink enables you to view traffic summary information based on the identified state (see the "Monitoring Traffic" section). For example, if you click the Up hyperlink, you will see only the BVI interfaces that currently have an operational status of Up.

Certificates—Total count of SSL certificates and the count of SSL certificates that are expiring beyond 30 days, expired, or that are expiring within 30 days. A hyperlink accesses a popup window for you to view the SSL certificates list based on the selection, displaying the certificate name, device name, days to expire, expiration date, and the date it was evaluated for you to determine the days to expire. Certificates are considered expired it their expiration date is within the next day (rounded down the next day). A hyperlink in the device name allows you to navigate to the context-based SSL Certificate configuration page (see the "Using SSL Certificates" section).


Note The Certificates information does not apply to the ACE NPE software version (see the "Information About the ACE No Payload Encryption Software Version" section).


This data is collected during discovery as well as during periodic monitoring polling. The timestamp shown in the status bar indicates a varying poll time; that is, different virtual contexts were polled and those context had different time stamps. The earliest time stamp of the polled virtual contexts is displayed in the status bar.

All counts shown in the Device Configuration Summary table are based on the operational status of the monitored objects listed above.

Out Of Service—Indicates any status other than In Service (for example, Out Of Service, Failed, or Disabled).

Status not available—Indicates that ANM was unable to poll the operational status of this object. The display of this operational status could be due to polling errors or the device was unreachable. Also, if a poll was recently initiated, this operational status could indicate that ANM is in the process of collecting data.

Status not supported—Indicates that the device does not have the capability to provide an operational status of this object. The display of this operational status could be due to missing SNMP instrumentation on earlier ACE devices.

Context With Denied Resource Usage Detected Table

The Context With Denied Resource Usage Detected table lists all contexts for which the resource request is denied after reaching the maximum limit. An increase in the deny count (that is, the deny rate) results in the relevant context resource type appearing in this table. ANM obtains the count information by using the ACE show resource usage CLI command, which collects the information from the following MIBs: crlResourceLimitReqsDeniedCount and crlRateLimitResourceReqsDeniedCount.

This table includes the following information:

Context—Name of the configured context that contains a denied resource.

Resource Type—Type of system resource in the context.

Denies/Second—Number of denied resources (per second) as a result of oversubscription or resource depletion.

Total Deny Count—Number of denied uses of the resource since the resource statistics were last cleared.

Last Polled Count—Date and time of the last time that ANM polled the device to display the current values.


Note The Context With Denied Resource Usage Detected table does not display the sticky denied resource count because this count does not increment when the ACE sticky resources are exhausted. The ACE's sticky table can hold a maximum of four million entries (four million simultaneous users). When the table reaches the maximum number of entries, additional sticky connections cause the table to wrap and the first users become unstuck from their respective servers.


A hyperlink allows you to access the Resource Usage monitoring page to view a detailed list of resources used and denied counts (see the "Monitoring Resource Usage" section).

Device Resource Usage Graph

For each resource type, the ACE Dashboard displays the Top 3 virtual contexts that consume the resources in the Device Resource Usage graph (see Figure 17-2).


Note The SSL Connection Rate graph entry does not apply to the ACE NPE software version (see the "Information About the ACE No Payload Encryption Software Version" section).


Figure 17-2 Device Resource Usage Graph

A tooltip is added to display the Top 3 context names and their consumption, consumption of the resource by rest of the contexts and the total consumption by all contexts. This data is collected by ANM by using the ACE show resource usage CLI command. The timestamp shown in the status bar indicates a varying poll time; that is, different virtual contexts were polled and those context had different time stamps. The earliest time stamp of the polled virtual contexts is displayed in the status bar.

To toggle the display of the Device Resource Usage graph in the monitoring window:

Click View As Chart to display the object data as a graph.

Click View As Grid to display the object data as a numerical line grid.


Note If you want to save the graph as a JPEG file for archive or other purposes, click the Show As Image button. When you mouse over the graph, the Image Toolbar appears. From the Image Toolbar, you can save the graph as a JPEG or send it in an email. You can also print the graph if desired.

If you want to export object data to Microsoft Excel for archive or other purposes, click the Export to Excel link in the View As Grid object display.


Hyperlinks allow you to access the individual resource usage page for more details (see the "Monitoring Resource Usage" section).


Note ACL Memory (for ACE module and ACE appliance) and Application Acceleration (for ACE appliance only) do not appear in the Device Resource Usage graph. To view the detailed counters, click the hyperlink to access individual resource usage page.


Top 10 Current Resources Table

The Top 10 Resource Usage table (see Figure 17-3) displays the Top 10 resource types that have been evaluated for high resource utilization. The resource with highest utilization appears at the top. This data is collected by ANM by using the ACE show resource usage CLI command.

Figure 17-3 Top 10 Current Resources Table—ACE Dashboard

This table includes the following information:

Last Hour—Plot of high resource utilization during the past hour.

Resource Name—Type of system resource in the context.

Used By—Name of the virtual context that is placing the high demands on the resource. The Global Pool usage is critical in the setup where one or more contexts are configured to make use of the global pool once their reserved resource are depleted and resource is free in the global pool. In this situation, if the global pool is depleted, multiple contexts may be starved for resource.


Note Contexts configured to make use of the global pool will not be evaluated for the Top 10 Resource Usage table.


Current Usage—Active concurrent instances or the current rate of the resource.

Average—Average value of resource usage (based on the last hour).

Max.—Highest value of resource usage (based on the last hour).

Last Polled Time—Date and time of the last time that ANM polled the device to display the current values.

Hyperlinks allow you to access the individual resource usage page for more details (see the "Monitoring Resource Usage" section).

You can choose to show or hide the syslog buffer information that displays in the Top 10 Current Resources pane. You may want to hide this information because it will always show 100 percent after the buffer becomes full and starts to wrap. For more information, see the "Managing the Syslog Buffer Display in the All Devices Dashboard" section.

Control Plane CPU/Memory Graphs

The Control Plane CPU/Memory graphs (see Figure 17-4) show the utilization of the ACE CPU. This data consists of two graphs:

The Control Plane CPU Usage graph shows the utilization of the ACE CPU as a percentage.

The Control Plane Memory graph displays the consumed memory on Kbytes. A tooltip is added to display the Cache Memory, Total Memory, Shared Memory, Buffer Memory, and Free Memory usage as a percentage.

To toggle the display of the Control Plane CPU/Memory graph in the monitoring window:

Click View As Chart to display the object data as a graph.

Click View As Grid to display the object data as a numerical line grid.


Note If you want to save the graph as a JPEG file for archive or other purposes, click the Show As Image button. When you mouse over the graph, the Image Toolbar appears. From the Image Toolbar, you can save the graph as a JPEG or send it in an email. You can also print the graph if desired.

If you want to export object data to Microsoft Excel for archive or other purposes, click the Export to Excel link in the View As Grid object display.


Figure 17-4 Control Plane CPU/Memory Graphs

ACE Virtual Context Dashboard

The ACE Virtual Context Dashboard displays monitoring information for an ACE virtual context selected from the device tree,. You access the ACE Virtual Context Dashboard by selecting Monitor > Devices > virtual_context > Dashboard.

Figure 17-5 illustrates the individual components of the ACE Virtual Context Dashboard.


Note The ANM software version that displays across the top of the window varies depending on your version of ANM.


Figure 17-5 ACE Virtual Context Dashboard

To enhance your viewing of the monitoring information in the ACE Virtual Context Dashboard, you can perform the following actions:

Click and drag an individual dashboard pane to move it to another location within the ACE Virtual Context Dashboard.

Use the Collapse/Expand buttons at the top right side of each dashboard pane to minimize/maximize a pane within the ACE Virtual Context Dashboard.

Click the Remove button to remove a dashboard pane from the ACE Virtual Context Dashboard. Click the Bring Back Closed Dashboard Panes button at the top of the ACE Virtual Context Dashboard to open the closed dashboard pane.


Note When you close any of the panes in a dashboard by clicking the Remove button, all of the headers in the other dashboard panes turn black to indicate that a pane has been closed. To return the dashboard panes to normal, click the Bring Back Closed Dashboard Panes button to reload the removed dashboard pane.


Click the Screen View (Full)/Screen View (Normal) buttons to display a larger (full) window view for the ACE Dashboard.

Changes made to dashboard layout or pane selections are only applicable for the current session. Those changes are not maintained by ANM the next time you access the ACE Virtual Context Dashboard.

The components of the individual ACE Virtual Context Dashboard panes are described in the following topics.

ACE Virtual Context Device Configuration Summary Table

Context With Denied Resource Usage Detected Table

Context Resource Usage Graph

Load Balancing Servers Performance Graphs

ACE Virtual Context Device Configuration Summary Table

The Device Configuration Summary table displays the following information:

Virtual Servers—Total count of virtual servers configured in all contexts and the count of virtual servers that are in the In Service and Out of Service state. ANM also identifies virtual servers that have a Status Not Available state (due to polled failing, polled disable, and so on) and have a Status Not Supported state (due to a lack of ACE SNMP support). A hyperlink enables you to view load balancing virtual server monitoring information based on the identified state (see the "Monitoring Load Balancing on Virtual Servers" section). For example, if you click the In Service hyperlink, you will see only the virtual servers that are currently in service.

Real Servers—Total count of real servers configured in all contexts and the count of real servers that are in In Service and Out of Service. A hyperlink enables you to view load balancing real server monitoring information based on the identified state (see the "Monitoring Load Balancing on Real Servers" section). For example, if you click the In Service hyperlink, you will see only the real servers that are currently in service.

Probes—Total count of probes configured in all contexts and the count of probes that are in the In Service and Out of Service state. A hyperlink enables you to view load balancing probe monitoring information based on the identified state (see the "Monitoring Load Balancing on Probes" section). For example, if you click the In Service hyperlink, you will see only the probes that are currently in service.

Gigabit Ethernets—(ACE appliance only) Total count of Gigabit Ethernet physical interfaces configured on the ACE appliance based on their operational status of Up and Down. A hyperlink enables you to view traffic summary information based on the identified state (see the "Monitoring Traffic" section). For example, if you click the Up hyperlink, you will see only the Gigabit Ethernet physical interfaces that currently have an operational status of Up.

VLANs—Total count of VLANs configured and the count of VLANs based on operational status - Up and Down. A hyperlink enables you to view traffic summary information based on the identified state (see the "Monitoring Traffic" section). For example, if you click the Up hyperlink, you will see only the VLAN interfaces that currently have an operational status of Up.

Port Channels—(ACE appliance only) Total count of port channels configured on the ACE appliance based on their operational status of Up and Down. A hyperlink enables you to view traffic summary information based on the identified state (see the "Monitoring Traffic" section). For example, if you click the Up hyperlink, you will see only the port channels that currently have an operational status of Up.

BVIs—Total count of BVI interfaces and the count of BVI interfaces based on their operational status of Up and Down. A hyperlink enables you to view traffic summary information based on the identified state (see the "Monitoring Traffic" section). For example, if you click the Up hyperlink, you will see only the BVI interfaces that currently have an operational status of Up.

Certificates—Total count of SSL certificates and the count of SSL certificates that are expiring beyond 30 days, expired, or that are expiring within 30 days. A hyperlink accesses a popup window for you to view the SSL certificates list based on the selection, displaying the certificate name, device name, days to expire, expiration date, and the date it was evaluated for you to determine the days to expire. Certificates are considered expired it their expiration date is within the next day (rounded down the next day). A hyperlink in the device name allows you to navigate to the context-based SSL Certificate configuration page (see the "Using SSL Certificates" section).

Counts are based on the selected ACE virtual context and not for all ACE virtual contexts.

This data is collected during discovery as well as during periodic monitoring polling. The timestamp shown in the status bar indicates a varying poll time; that is, different virtual contexts were polled and the contexts had different time stamps. The earliest time stamp of the polled virtual contexts is displayed in the status bar.

All counts shown in the Device Configuration Summary table are based on the operational status of the monitored objects listed above.

Out Of Service—Indicates any status other than In Service (for example, Out Of Service, Failed, or Disabled).

Status not available—Indicates that ANM was unable to poll the operational status of this object. The display of this operational status could be due to polling errors or the device was unreachable. Also, if a poll was recently initiated, this operational status could indicate that ANM is in the process of collecting data.

Status not supported—Indicates that the device does not have the capability to provide an operational status of this object. The display of this operational status could be due to missing SNMP instrumentation on earlier ACE devices.

Context With Denied Resource Usage Detected Table

The Context With Denied Resource Usage Detected table lists all contexts for which the resource request is denied after reaching the maximum limit. An increase in the deny count (that is, the deny rate) will result in the relevant context resource type to appear in this table. This data is collected by ANM by using the ACE show resource usage CLI command.

This table includes the following information:

Context—Name of the configured context that contains a denied resource.

Resource Type—Type of system resource in the context.

Denies/Second—Number of denied resources (per second) as a result of oversubscription or resource depletion.

Total Deny Count—Number of denied uses of the resource since the resource statistics were last cleared.

Last Polled Count—Date and time of the last time that ANM polled the device to display the current values.


Note This information is collected from the following MIBs: crlResourceLimitReqsDeniedCount and crlRateLimitResourceReqsDeniedCount.


A hyperlink allows you to access the Resource Usage monitoring page to view a detailed list of resources used and denied counts (see the "Monitoring Resource Usage" section).

Context Resource Usage Graph

The Context Resource Usage graph (see Figure 17-5) displays the details of each resource type utilized by the selected contexts. For each resource type, the graph includes the following monitoring statistics: Used, Global Available, and Guaranteed. This data is collected by ANM by using the ACE show resource usage CLI command.

To toggle the display of the Context Resource Usage graph in the monitoring window:

Click View As Chart to display the object data as a graph.

Click View As Grid to display the object data as a numerical line grid.


Note If you want to save the graph as a JPEG file for archive or other purposes, click the Show As Image button. When you mouse over the graph, the Image Toolbar appears. From the Image Toolbar, you can save the graph as a JPEG or send it in an email. You can also print the graph if desired.

If you want to export object data to Microsoft Excel for archive or other purposes, click the Export to Excel link in the View As Grid object display.


Hyperlinks allow you to access the individual resource usage page for more details (see the "Monitoring Resource Usage" section).


Note ACL Memory (for ACE module and ACE appliance) and Application Acceleration (for ACE appliance only) do not appear in the Device Resource Usage graph. To view the detailed counters, click the hyperlink to access individual resource usage page.


Load Balancing Servers Performance Graphs

The Load Balancing Servers Performance graphs (see Figure 17-6) are as follows:

Top 5 Virtual Servers—Displays the top five virtual servers in the selected virtual context. You can select from server statistics (such as High Connection Rate, Dropped Connection Rate, and so on) that are collected by ANM polling for top performance evaluation.

Top 5 Real Servers—Displays the top five real servers in the selected virtual context. You can select from server statistics (such as High Connection Rate, Dropped Connection Rate, and so on) that are collected by ANM polling for top performance evaluation.

You select the statistic from the Select Statistics drop-down list.

To toggle the display of a Load Balancing Servers Performance graph in the monitoring window:

Click View As Chart to display the object data as a graph.

Click View As Grid to display the object data as a numerical line grid.


Note If you want to save the graph as a JPEG file for archive or other purposes, click the Show As Image button. When you mouse over the graph, the Image Toolbar appears. From the Image Toolbar, you can save the graph as a JPEG or send it in an email. You can also print the graph if desired.

If you want to export object data to Microsoft Excel for archive or other purposes, click the Export to Excel link in the View As Grid object display.


Hyperlinks allow you to access the corresponding monitoring screens for more details:

Monitoring Load Balancing on Virtual Servers

Monitoring Load Balancing on Real Servers

Figure 17-6 Load Balancing Servers Performance Graphs

ANM Group Dashboard

The ANM Group Dashboard displays overall information of the ANM server. You can specify to view details for the ANM-created All Devices Group and for a user-defined ANM device group (see the "Monitoring Device Groups" section). You access the ANM Group Dashboard by choosing Monitor > Devices > Groups > All Devices > Dashboard.


Note The ANM Group Dashboard may not display the latest information if the periodic polling is disabled. To enable periodic polling, see the "Enabling Polling on All Devices" section.


Figure 17-7 illustrates the individual components of the ANM Group Dashboard.


Note The ANM software version that displays across the top of the window varies depending on your version of ANM.


Figure 17-7 ANM Group Dashboard

To enhance your viewing of the monitoring information in the ANM Group Dashboard, you can perform the following actions:

Click and drag an individual dashboard pane to move it to another location within the ANM Group Dashboard.

Use the Collapse/Expand buttons at the top right side of each dashboard pane to minimize/maximize a pane within the ANM Group Dashboard.

Click the Remove button to remove a dashboard pane from the ANM Group Dashboard. Click the Bring Back Closed Dashboard Panes button at the top of the ANM Group Dashboard to open the closed dashboard pane.


Note When you close any of the panes in a dashboard by clicking the Remove button, all of the headers in the other dashboard panes turn black to indicate that a pane has been closed. To return the dashboard panes to normal, click the Bring Back Closed Dashboard Panes button to reload the removed dashboard pane.


Click the Screen View (Full)/Screen View (Normal) buttons to display a larger (full) window view for the ACE Dashboard.

Changes made to dashboard layout or pane selections are only applicable for the current session. Those changes are not maintained by ANM the next time you access the ANM Group Dashboard.

The components of the individual ANM Group Dashboard panes are described in the following sections.

Managed Devices Table

Context With Denied Resource Usage Detected Table

ANM Group Device Configuration Summary Table

Top 10 Current Resources Table

Latest 5 Alarms Notifications Table

Latest 5 Critical Events Table

Contexts Performance Overview Graph

Managed Devices Table

The Managed Devices table displays the total count of devices in the selected ANM device group and the count based on the state (Up or Down) of the imported ACE modules, ACE appliances, CSM, GSS, and CSS devices. The data shown in this table are collected during device discovery as well as during periodic monitor polling. The state of the individual device is identified from its XML connectivity and SNMP status (whichever is applicable). The most recent information is used to identify device status.

Click the Device Details hyperlink to view a popup window containing the following device information:

Device Name—Name of the device managed by ANM.

State—Operational state of the device (Up or Down). If the State is Down, ANM displays whether the state has been detected through SNMP or XML.

Device Type—Device type assigned to the imported device by ANM (for example, ACE v 2.0).

# of VCs—Number of configured ACE virtual contexts, including the Admin context and configured user contexts. This value is only applicable for the ACE module and ACE appliance.

Last Polled Time—Date and time of the last time that ANM polled the device to display the current values.

The data shown in this table is collected during device discovery as well as during periodic monitor polling. The timestamp shown in the status bar indicates a varying poll time; that is, different virtual contexts were polled and the contexts had different time stamps. The earliest time stamp of the polled virtual contexts is displayed in the status bar.

Hyperlinks in the popup window allow you to access the individual ACE Device Dashboard for more details (see the "ACE Dashboard" section).

Context With Denied Resource Usage Detected Table

The Context With Denied Resource Usage Detected table lists all contexts for which the resource request is denied after reaching the maximum limit. An increase in the deny count (that is, the deny rate) will result in the relevant context resource type to appear in this table. This data is collected by ANM by using the ACE show resource usage CLI command.

This table includes the following information:

Context—Name of the configured context that contains a denied resource.

Resource Type—Type of system resource in the context.

Denies/Second—Number of denied resources (per second) as a result of oversubscription or resource depletion.

Total Deny Count—Number of denied uses of the resource since the resource statistics were last cleared.

Last Polled Count—Date and time of the last time that ANM polled the device to display the current values.


Note This information is collected from the following MIBs: crlResourceLimitReqsDeniedCount and crlRateLimitResourceReqsDeniedCount.


A hyperlink allows you to access to Resource Usage monitoring page to view a detailed list of resources used and denied counts (see the "Monitoring Resource Usage" section).

ANM Group Device Configuration Summary Table

The Device Configuration Summary table displays the following information:

Virtual Servers—(ACE only) Total count of virtual servers configured in all contexts and the count of virtual servers that are in the In Service and Out of Service state. ANM also identifies virtual servers that have a Status Not Available state (due to polled failing, polled disable, and so on) and have a Status Not Supported state (due to a lack of ACE SNMP support). A hyperlink enables you to view load balancing virtual server monitoring information based on the identified state (see the "Monitoring Load Balancing on Virtual Servers" section). For example, if you click the In Service hyperlink, you will see only the virtual servers that are currently in service.

Real Servers—(ACE only) Total count of real servers configured in all contexts and the count of real servers that are in In Service and Out of Service. A hyperlink enables you to view load balancing real server monitoring information based on the identified state (see the "Monitoring Load Balancing on Real Servers" section). For example, if you click the In Service hyperlink, you will see only the real servers that are currently in service.

Probes—(ACE only) Total count of probes configured in all contexts and the count of probes that are in the In Service and Out of Service state. A hyperlink enables you to view load balancing probe monitoring information based on the identified state (see the "Monitoring Load Balancing on Probes" section). For example, if you click the In Service hyperlink, you will see only the probes that are currently in service.

Gigabit Ethernets—(ACE appliance only) Total count of Gigabit Ethernet physical interfaces configured on the ACE appliance based on their operational status of Up and Down. A hyperlink enables you to view traffic summary information based on the identified state (see the "Monitoring Traffic" section). For example, if you click the Up hyperlink, you will see only the Gigabit Ethernet physical interfaces that currently have an operational status of Up.

VLANs—(ACE only) Total count of VLANs configured and the count of VLANs based on operational status - Up and Down. A hyperlink enables you to view traffic summary information based on the identified state (see the "Monitoring Traffic" section). For example, if you click the Up hyperlink, you will see only the VLAN interfaces that currently have an operational status of Up.

Port Channels—(ACE appliance only) Total count of port channels configured on the ACE appliance based on their operational status of Up and Down. A hyperlink enables you to view traffic summary information based on the identified state (see the "Monitoring Traffic" section). For example, if you click the Up hyperlink, you will see only the port channels that currently have an operational status of Up.

BVIs—(ACE only) Total count of BVI interfaces and the count of BVI interfaces based on their operational status of Up and Down. A hyperlink enables you to view traffic summary information based on the identified state (see the "Monitoring Traffic" section). For example, if you click the Up hyperlink, you will see only the BVI interfaces that currently have an operational status of Up.

Certificates—(ACE only) Total count of SSL certificates and the count of SSL certificates that are valid, expired, or that are expiring within 30 days. A hyperlink accesses a popup window for you to view the SSL certificates list based on the selection, displaying the certificate name, device name, days to expire, expiration date, and the date it was evaluated for you to determine the days to expire. Certificates are considered expired it their expiration date is within the next day (rounded down the next day). A hyperlink in the device name allows you to navigate to the context-based SSL Certificate configuration page (see the "Using SSL Certificates" section).

GSS VIP Answers—(GSS only) Total number of configured VIP answers and their operating state, which is either Active or Other. The Other state can indicate any of the following states: Suspended, Operational Suspended, Unknown, Failed, or N/A.

GSS DNS Rules—(GSS only) Total number of configured DNS rules and their operating state, which is either Active or Other. The Other state can indicate either the Suspended or N/A states.

This data is collected during discovery as well as during periodic monitoring polling. The timestamp shown in the status bar indicates a varying poll time; that is, different virtual contexts were polled and the contexts had different time stamps. The earliest time stamp of the polled virtual contexts is displayed in the status bar.

All counts shown in the Device Configuration Summary table are based on the operational status of the monitored objects listed above.

Out Of Service—Indicates any status other than In Service (for example, Out Of Service, Failed, or Disabled).

Status not available—Indicates that ANM was unable to poll the operational status of this object. The display of this operational status could be due to polling errors or the device was unreachable. Also, if a poll was recently initiated, this operational status could indicate that ANM is in the process of collecting data.

Status not supported—Indicates that the device does not have the capability to provide an operational status of this object. The display of this operational status could be due to missing SNMP instrumentation on the CSS or on earlier ACE devices.

Top 10 Current Resources Table

The Top 10 Resource Usage table (see Figure 17-8) displays the top 10 resource types that have been evaluated for high resource utilization. The resource with highest utilization appears at the top. This data is collected by ANM by using the ACE show resource usage CLI command.

Figure 17-8 Top 10 Current Resources Table—ANM Group Dashboard

This table includes the following information:

Last Hour—Plot of high resource utilization during the past hour.

Resource Name—Type of system resource in the context.

Used By—Name of the virtual context that is placing the high demands on the resource. The Global Pool usage is critical in the setup where one or more contexts are configured to make use of the global pool once their reserved resource are depleted and resource is free in the global pool. In this situation, if the global pool is depleted, multiple contexts may be starved for resource.


Note Contexts configured to make use of the global pool will not be evaluated for the Top 10 Resource Usage table.


Current Usage—Active concurrent instances or the current rate of the resource.

Average—Average value of resource usage (based on the last hour).

Max.—Highest value of resource usage (based on the last hour).

Last Polled Time—Date and time of the last time that ANM polled the device to display the current values.

Hyperlinks allow you to access the individual resource usage page for more details (see the "Monitoring Resource Usage" section).

You can choose to show or hide the syslog buffer information that displays in the Top 10 Current Resources pane. You may want to hide this information because it will always show 100 percent after the buffer becomes full and starts to wrap (see the "Managing the Syslog Buffer Display in the All Devices Dashboard" section).

Latest 5 Alarms Notifications Table

The Latest 5 Alarm Notification table (Figure 17-9) displays the most recent five alarms for ANM along with a summary that explains the number of Critical, Major, Minor, and Informational alarms. This function interacts with the user-configured ANM alarm and threshold features (see the "Configuring Alarm Notifications on ANM" section).

Figure 17-9 Latest 5 Alarms Notifications Table


Note By default, no thresholds are configured in ANM.


This table includes the following information:

Device—Name of the ACE device (appliance or module).

Severity— Severity level of the threshold, which can be one of the following: Info, Critical, Major, Minor.

Time—ANM timestamp at which the alarm occurred.

Category—Alarm name.

Details—Additional information about the alarm.

A hyperlink allow you to view alarm notifications (see the "Displaying Alarm Notifications" section).

Latest 5 Critical Events Table

The Latest 5 Critical Events table display most recent five critical events that ANM receives from devices, including traps and high severity syslogs. ANM displays a summary that explains the number of Emergency, Alert, and Critical alarms. ANM displays critical events if the imported ACE device has been configured to send syslogs and traps to ANM. For information about configuring the ACE to send syslogs and traps, see either the Cisco Application Control Engine Module System Message Guide or the Cisco 4700 Series Application Control Engine Appliance System Message Guide.

Figure 17-10 Latest 5 Critical Events Table

The following details are shown in the Critical Events table:

Device/Context—ACE device name and virtual context where the event occurred.

Time—ANM timestamp at which the alarm occurred.

Type—Displays if the event appears in a syslog or a trap.

Details—Additional information about the critical event.

A hyperlink allow you to view all events collected by ANM (see the "Monitoring Events" section).

Contexts Performance Overview Graph

The Contexts Performance Overview graph displays the top five virtual contexts based on user-configurable resource statistic such as ACL Memory, Bandwidth, and so on. You select the resource from the Select Statistics drop-down list. This data is collected by ANM by using the ACE show resource usage CLI command.

Figure 17-11 Context Performance Graph

To toggle the display of the top five virtual context chart in the Contexts Performance Overview graph:

Click View As Chart to display the resource statistic as a graph.

Click View As Grid to display the resource statistic as a numerical line grid.


Note If you want to save the graph as a JPEG file for archive or other purposes, click the Show As Image button. When you mouse over the graph, the Image Toolbar appears. From the Image Toolbar, you can save the graph as a JPEG or send it in an email. You can also print the graph if desired.

If you want to export object data to Microsoft Excel for archive or other purposes, click the Export to Excel link in the View As Grid object display.


Monitoring Device Groups

You can display monitoring information for device groups that you create in Cisco License Manager (see the "Configuring User-Defined Groups" section). When you choose Monitor > Devices > Groups > device_group, all monitoring features that are supported on any of the devices in the device group are displayed. Because some monitoring features, for example, Application Acceleration, are not supported on all device types, you can click the following buttons at the bottom of the Monitor screens to change what information appears:

Show Polled Devices—By default, only the devices in the device group that support the specified feature are displayed.

Show All Devices—All devices in the device group are shown on the Monitoring results window, whether or not the feature you selected is supported on all the devices.

For example, if you create a device group that contains an ACE appliance and several other different device types, then choose Monitor > Devices > Groups > device_group > Application Acceleration, by default, only the ACE appliance appears in the Application Acceleration window because the other device types in the device group do not support this feature. If you click Show Polled Devices, all devices in the device group are displayed.

When viewing monitoring information, you might see N/A, which indicates that ACE Device Manager was not able to obtain the specified value. In addition, the monitoring window displays N/A in certain fields for which polling has not been executed.

Related Topics

Setting Up Devices for Monitoring

Device Monitoring Features

Using Dashboards to Monitor Devices and Virtual Contexts

Monitoring Devices

Monitoring Devices

ANM monitors activities on ACE, CSS, and CSM devices. When you choose Monitor > Devices, you can view device information. Using SNMP and CLI commands, ANM gathers information about your devices and displays the information.


Note If you get a warning message indicating that monitoring is not enabled or functioning, you must enable statistic monitoring on the device. See the "Setting Polling Parameters" section.


Table 17-2 lists the features that appear under Monitor > Devices, depending on which device type you choose in the device tree.

Table 17-2 Supported Features According to Device Type

Device Type Selected in the
Device Tree
Supported Features Displayed Under
Dashboard
System View
Resource Usage 1
Traffic Summary
Load Balancing
Application Acceleration
Polling Settings

ACE module

 

X

-

X

X

X

-

-

Admin context

X

-

X

X

X

-

X

User context

X

-

X

X

X

-

X

ACE appliance

 

X

-

X

X

X

X

-

Admin context

X

-

X

X

X

X

X

User context

X

-

X

X

X

X

X

CSS

 

-

X

-

X

X2

-

X

CSM

 

-

X

-

-

X

-

X

GSS

 

-

-

-

-

-

-

X

Groups3

 

X

-

X

X

X

X

-

1 See the "Monitoring Resource Usage" section for information about the options available under Resource Usage.

2 CSS devices support Virtual Servers only, so you do not see the Load Balancing > Statistics menu option.

3 By default, all monitoring features that are supported on any of the devices in the device group appear when you select a device group. See the "Using Dashboards to Monitor Devices and Virtual Contexts" section for more information about monitoring various device types within a device group.


Related Topics

Using Dashboards to Monitor Devices and Virtual Contexts

Monitoring the System

Setting Up Devices for Monitoring

Device Monitoring Features

Setting Polling Parameters

Configuring Historical Trend and Real Time Graphs for Devices

Monitoring the System

Cisco License Manager provides a System View that displays device information and a general overview of your system as a whole. System View is available only for CSS and CSM devices. If a CSM has crashed, you can use the System View to find out when and why the crash occurred and display information that affects the module. The System View also displays High Availability (HA) information and licensing information.


Note To monitor the ACE module or appliance, use the Device Dashboard function of ANM. See the "Using Dashboards to Monitor Devices and Virtual Contexts" section for details.



Note ANM does not support monitoring of chassis.


Procedure


Step 1 Choose Monitor > Devices > device > System View.

The information that appears depends on what device type you select in the device tree.

The System View displays the following information:

Device Information

High Availability

License Status

Module Information (for CSS devices only)


Note You can sort the information displayed in the table by clicking on a column heading.


Step 2 Click Poll Now to instruct ANM to poll the devices and display the current values.

Step 3 Click OK when asked if you want to poll the devices for data now.


Related Topics

Setting Up Devices for Monitoring

Device Monitoring Features

Setting Polling Parameters

Monitoring Traffic

Configuring Historical Trend and Real Time Graphs for Devices

Monitoring Resource Usage

ANM provides resource usage so that you can easily determine if you need to reallocate resources to a particular virtual context, view traffic usage in your contexts, or determine available usage for your contexts. There are three modes in which ANM provides resource usage for ACEs:

Virtual-context based resource usage—You must select a virtual context from the device tree to view resource usage specific to the context (see the "Monitoring Virtual Context Resource Usage" section).

System-wide resource usage—You must select an ACE module or appliance from the device tree to view system-wide information and to display the following options:

Connections—Displays traffic resource usage information. See the "Monitoring System Traffic Resource Usage" section.

Features—Displays non-connection based resource usage information. See the "Monitoring System Non-Connection Based Resource Usage" section.

Dashboard usage—You can select an ACE module, ACE appliance, or ACE virtual context from the device tree, and then choose Monitor > Devices > ACE > Dashboard. See the "Using Dashboards to Monitor Devices and Virtual Contexts" section.

See the "Configuring Virtualization" chapter of either the Cisco Application Control Engine Module Virtualization Configuration Guide or the Cisco 4700 Series Application Control Engine Appliance Virtualization Configuration Guide for the maximum resource usage value for each attribute.

Monitoring Virtual Context Resource Usage

ANM displays resource usage for virtual contexts as explained in the following steps.

See the "Configuring Virtualization" chapter of either the Cisco Application Control Engine Module Virtualization Configuration Guide or the Cisco 4700 Series Application Control Engine Appliance Virtualization Configuration Guide for the maximum resource usage value for each attribute.

Procedure


Step 1 Choose Monitor > Devices > virtual_context > Resource Usage.

The information in Table 17-3 appears in the Resource Usage window.

Table 17-3 Virtual Context Resource Usage Field Descriptions 

Field
Description

ACL Memory (Bytes)

ACL memory usage

Application Acceleration (Connections)

Number of application acceleration connections.

Note This field displays if you selected an ACE appliance in the device tree.

Bandwidth (Bytes/Sec)

Bandwidth in bytes per second.

Concurrent Connections (Connections)

Number of simultaneous connections.

Connection Rate (Connections/Sec)

Connections per second.

HTTP-comp rate

HTTP compression rate.

Note This field displays when you select one of the following device types from the device tree: An ACE appliance (any version) or an ACE module version A4(1.0) or later.

Inspect Connection Rate (Connections/Sec)

RTSP/FTP inspection connections per second.

MAC Miss Rate (Connections/Sec)

MAC miss traffic punted to CP packets per second.

Management Connection Rate (Connections)

Number of management connections.

Management Traffic Rate (Connections/Sec)

Management traffic bytes per second.

Proxy Connection Rate (Connections)

Proxy connections.

Regular Expression Memory (Bytes)

Regular expressions usage in bytes.

SSL Connection Rate (Transactions/Sec)

SSL (Secure Sockets Layer) connections per second.

Note The ssl-connections rate resource does not display with the ACE NPE software version (see the "Information About the ACE No Payload Encryption Software Version" section).

Sticky Entries

Number of sticky table entries.

Syslog Buffer Size (Bytes)

Syslog message buffer size in bytes.

Syslog Message Rate (Messages/Sec)

Syslog messages transmitted in messages per seconds.

Throughput (Bytes/Sec)

Displays through-the-ACE traffic. This is a derived value (you cannot configure it directly) and it is equal to the bandwidth rate minus the mgmt-traffic rate for the 1-Gbps and 2-Gbps licenses.

Translation Entries

Current number of network and port address translations.


Step 2 (Optional) Click Poll Now to instruct ANM to poll the devices and display the current values, and click OK when prompted if you want to poll the devices for data now.

Step 3 (Optional) To display a historical trend graph of resource data for the virtual context, select up to four resources from the list and click Graph.

The Resource Usage Graph appears (see the "Configuring Historical Trend and Real Time Graphs for Devices" section for details).


Related Topics

Monitoring System Traffic Resource Usage

Monitoring System Non-Connection Based Resource Usage

Configuring Historical Trend and Real Time Graphs for Devices

Monitoring System Traffic Resource Usage

ANM displays system-wide traffic resource usage as explained in the following steps. See the "Configuring Virtualization" chapter of either the Cisco Application Control Engine Module Virtualization Configuration Guide or the Cisco 4700 Series Application Control Engine Appliance Virtualization Configuration Guide for the maximum resource usage value for each attribute.


Note You must select an ACE module or appliance from the device tree to view system-wide traffic resource usage information as shown in the following steps.


Procedure


Step 1 Choose Monitor > Devices > ACE > Resource Usage > Connections.

The current resource usage information appears as shown in Table 17-4.


Note There might be a slight delay because the resource usage information is gathered in real-time.


Table 17-4 Resource Usage Connections Field Descriptions

Field
Description

Context

Name of the virtual context

Conc. Conn. %

Number of simultaneous connections

Mgmt. Conn. %

Number of management connections

Proxy Conn. %

Proxy connections

Bandwidth (Bytes/S) %

Bandwidth in bytes per second

Throughput (Bytes/S)

Note This field appears when you select an ACE in the device tree.

Throughput in bytes per second

Conn. Rate (Conn./S) %

Connections per second

SSL Conn. Rate (Trans./S) %

SSL (Secure Sockets Layer) connections per second

Note The SSL Conn. Rate field does not display with the ACE NPE software version (see the "Information About the ACE No Payload Encryption Software Version" section).

Mgmt. Traffic Rate
(Conn./S) %

Management traffic connections per second

MAC Miss Rate (Conn./S) %

MAC miss traffic punted to CP packets per second

Insp. Conn. Rate (Conn./S) %

RTSP/FTP inspection connections per second

App. Acc. Conn. %

Number of application acceleration connections.

Note This field appears when you select an ACE appliance in the device tree.

HTTP-Comp Rate %

HTTP compression rate.

Note This field appears when you select one of the following device types from the device tree: An ACE appliance (any version) or an ACE module version A4(1.0) or later.



Note If any of the percentages that display in the Resource Usage Connections table exceed 100 percent, this is an indication that a license on the ACE was recently installed or uninstalled using either ANM or the CLI. To correct the display problem, manually synchronize the Admin context of the ACE with the CLI (see the "Synchronizing Virtual Context Configurations" section).


Step 2 Click Poll Now to instruct ANM to poll the devices and display the current values.

Step 3 Click OK when asked if you want to poll the devices for data now.


Related Topics

Monitoring Virtual Context Resource Usage

Monitoring System Non-Connection Based Resource Usage

Monitoring System Non-Connection Based Resource Usage

ANM displays system-wide, non-connection-based resource usage as explained in the following steps.


Note You must select an ACE module or appliance from the device tree to view the non-connection based resource usage information as shown in the following steps.



Step 1 Choose Monitor > Devices > ACE > Resource Usage > Features.

The current resource usage information appears shown in Table 17-5.


Note There might be a slight delay because the resource usage information is gathered real-time.


Table 17-5 Resource Usage Features Field Descriptions  

Field
Description

Context

Name of the virtual context

Translation Entries %

Current number of network and port address translations

ACL Memory (Bytes) %

ACL memory usage in bytes

RegEx Memory (Bytes) %

Regular expressions memory usage in bytes

Syslog Buffer Size (Bytes) %

Syslog message buffer size in bytes

Syslog Message Rate (Messages/S) %

Syslog messages per second


Step 2 Click Poll Now to instruct ANM to poll the devices and display the current values.

Step 3 Click OK when asked if you want to poll the devices for data now.


Related Topics

Monitoring Virtual Context Resource Usage

Monitoring System Traffic Resource Usage

Configuring Historical Trend and Real Time Graphs for Devices

Monitoring Traffic

ANM determines traffic information for your ACE module, ACE appliance, or CSS devices by calculating the delta traffic values since the last polling cycle and displays the resulting values. You can view traffic summary information as shown in the steps below.


Note ANM may not display the latest traffic summary information if the periodic polling is disabled. To enable periodic polling, see the "Enabling Polling on All Devices" section.



Note To get traffic data polled directly from a device, click on an interface name that appears in the Interface column. See the "Displaying Device-Specific Traffic Data" section.


Procedure


Step 1 Choose Monitor > Devices > device > Traffic Summary.

The information shown in Table 17-6 appears in the Traffic Summary page.


Note You can click on any column heading to sort the table by that column.


Table 17-6 Traffic Summary Fields  

Field
Description

Device

Fully-qualified device name. This field does not appear for CSS devices.

Interface

Name of the interface. Click the interface hyperlink to get traffic data polled directly from the device as shown in Table 17-7.

Admin Status

User-specified status of the device, which can be one of the following states:

Up

Down

Testing, which indicates that no operational packets can be passed.

Operational Status

Current operational status of the device, which can be one of the following states:

Up

Down

Testing, which indicates that no operational packets can be passed

Unknown

Dormant, which indicates the interface is waiting for external actions (such as a serial line waiting for an incoming connection)

Not present, which indicates the interface has missing components

Packets In / Sec

This field appears for ACEs only.

Per second, the number of packets delivered by this sub-layer to a higher (sub-)layer, which were not addressed to a multicast or broadcast address at this sub-layer.

Packets Out / Sec

This field appears for ACEs only.

Per second, the total number of packets that higher-level protocol requested be transmitted, and which were not addressed to a multicast or broadcast address at this sub-layer, including those that were discarded or not sent.

Bytes In / Sec

Number of octets received, including framing characters, per second.

Bytes Out / Sec

Number of octets per second transmitted out of the interface, including framing characters.

Errors In / Sec

Number of inbound packets discarded per second because they contained errors or because of an unknown or unsupported protocol.

Errors Out / Sec

Number of outbound packets discarded per second because they contained errors or because of an unknown or unsupported protocol.

Last Polled

Date and time of the last time that ANM polled the device to display the current values. This field appears if viewing traffic summary data at a device level or at a device group level in the device tree.

Note The Last Polled time stamp appears in the table heading if viewing traffic summary data at a virtual context level.


Step 2 (Optional) Click Poll Now to instruct ANM to poll the devices and display the current values and click OK when prompted if you want to poll the devices for data now.


Note Even if the periodic polling is enabled, ANM polls all the devices thus ignoring the statistics defined during the periodic polling.


Step 3 (Optional) To display a historical trend graph of traffic information, select up to four interfaces from the list and click Graph.

The Resource Usage Graph appears (see the "Configuring Historical Trend and Real Time Graphs for Devices" section for details).

Step 4 (Optional) Choose a device, and click Details to see specific traffic information for the selected device (see the "Displaying Device-Specific Traffic Data" section).


Related Topics

Displaying Device-Specific Traffic Data

Configuring Historical Trend and Real Time Graphs for Devices

Displaying Device-Specific Traffic Data

You can display device-specific traffic data.

Procedure


Step 1 Choose Monitor > Devices > device > Traffic Summary.

Hyperlinked device names appear in the Interface column.

Step 2 Choose a hyperlinked device name.

The Traffic Summary Details window appears. The information shown in Table 17-7 appears.


Note You can click on a column heading to sort the table by that column.


Table 17-7 Traffic Summary Details Window Description

Device Type
Field
Description

ACE and CSS

Bytes In

Total number of octets received on the interface, including framing characters

Bytes Out

Total number of octets transmitted out of the interface, including framing characters

Discarded Inbound Packets

Number of inbound packets which were discarded even though no errors were detected to prevent their being delivered to a higher-layer protocol

Discarded Outbound Packets

Number of outbound packets which were discarded even though no errors were detected to prevent their being transmitted

Inbound Packet Errors

Total number of inbound packet errors

Inbound Packets with Unknown Protocol

Total number of packets received via the interface which were discarded because of an unknown or unsupported protocol

Outbound Packet Errors

Total number of outbound packet errors

Packets In

Number of packets delivered by this sub-layer to a higher (sub-)layer, which were not addressed to a multicast or broadcast address at this sub-layer

Packets Out

Number of packets that higher-level protocols requested be transmitted, and which were not addressed to a multicast or broadcast address at this sub-layer, including those that were discarded or not sent

CSS only

Active TCP

Current number of active TCP flows on the interface

Active UDP

Current number of active UDP flows on the interface

FCB Count

Number of unused fastpath flow control blocks for the interface

TCP Average

Five second moving average of TCP flows per second on the interface

TCP Current

Number of new TCP flows within last second on the interface

TCP High

Maximum number of TCP flows in any one second interval on the interface

TCP Total

Total TCP flows on the interface

UDP Average

Five second moving average of UCP flows per second on the interface

UDP Current

Number of new UDP flows within last second on the interface

UDP High

Maximum number of UDP flows in any one second interval on the interface

UDP Total

Total UDP flows on the interface


Step 3 Click OK to close the window and return to the Traffic Summary window.


Related Topics

Monitoring Traffic

Monitoring Load Balancing

ANM monitors load balancing and allows you to view the information associated with virtual servers, real servers, probes, and load balancing statistics.

This section includes the following topics:

Monitoring Load Balancing on Virtual Servers

Monitoring Load Balancing on Real Servers

Monitoring Load Balancing on Probes

Monitoring Load Balancing Statistics

Monitoring Load Balancing on Virtual Servers

ANM monitors load balancing and allows you to display the associated virtual server information as shown in the following steps.


Note ANM may not display the latest virtual server information if the periodic polling is disabled. To enable periodic polling, see the "Enabling Polling on All Devices" section.



Note You can display additional load-balancing information about real servers, such as the number of servers that are functioning properly, and probes, such as viewing if an excessing number of probes are failing, by clicking the hyperlink in the respective columns in Table 17-8.


Procedure


Step 1 Choose Monitor > Devices > device > Load Balancing > Virtual Servers.

Depending on the device type you selected in the device tree, the information described in Table 17-8 appears.


Note For the ACE appliance and the ACE module running A2(3.0), click the Advanced Editing Mode button to show/hide additional load balancing virtual server monitoring fields.



Note If you select a CSS device from the device tree, the navigation path does not include Load Balancing; the path is Monitor > Devices > CSS_device > Virtual Servers.


Table 17-8 Load Balancing Virtual Server Monitoring Information 

Device Type
Field
Description

All

Virtual Server

Name of the virtual server.

Note If a virtual server is associated with primary and backup server farms, two entries appear in the table: One for the primary server farm and one for the backup server farm.

To view statistics for a selected virtual server, click the virtual server hyperlink. The Virtual Server Details popup window appears containing the individual statistic, associated counter value, and a description of the statistic. Click OK to close the popup window.

IP Address

IP address of the virtual server.

Port

Port to be used for the specified protocol.

# Rservers Up

Number of servers up/Number of total servers configured.

Note You can click on the hyperlink in this column to view statistics for the real servers configured for the specified virtual server. See the "Monitoring Load Balancing on Real Servers" section.

ACEs, CSM

# Probes Failed

For the ACE, this field displays Number of probes failed/Number of probes configured.

For the CSM, this field displays Number of probes failed.

Note For an ACE, you can click on the number displayed to view the statistics for the probes configured for the specified virtual server. See the "Monitoring Load Balancing on Probes" section.

Operational Status

The state of the server, which can be:

Inservice—Indicates the server is in service.

Out of Service—Indicates the server is out of service.

Current Connections

Current number of connections.

Conns/Sec.

Number of connections per second that the device receives.

ACEs only

Device

Fully-qualified device name.

Protocol

Protocol the virtual server supports, which can be:

Any—Indicates the virtual server is to accept connections using any IP protocol.

TCP—Indicates that the virtual server is to accept connections that use TCP.

UDP—Indicates that the virtual server is to accept connections that use UDP.

Service Policy

Policy map applied to the device.

DWS

Operating state of the Dynamic Workload Scaling feature for the associated server farm, which can be:

N/A—Not applicable; the virtual server's server farm is not configured for Dynamic Workload Scaling.

Local—The server farm is configured for Dynamic Workload Scaling, but the ACE is load-balancing traffic to the local VM Controller VMs only.

Expanded—The server farm is configured for Dynamic Workload Scaling and the ACE is sending traffic to the local and remote VM Controller VMs.

Dropped Conns/Sec.

Number of connections per second that the ACE discarded.

Server Farm

Name of the server farm associated with the virtual server.

Action

Indicates if the device is functioning as a primary server (Primary) or a backup server (Backup).

 

Algorithm

Type of predictor algorithm specified on the load balancer, which can be:

Roundrobin

Leastconn

Hash URL

Hash Address

Hash Cookie

Hash Header

Last Polled

Date and time of the last time that ANM polled the device to display the current values. This field appears if viewing virtual server data at a device level or at a device group level in the device tree.

Note The Last Polled time stamp appears in the table heading if viewing virtual server data at a virtual context level.

ACE appliance, ACE module running A2(3.0)
(Advanced Editing Mode button)

Client Packets/Sec

Number of packets per second received from the client.

Client Bytes/Sec

Number of bytes per second received from the client.

Server Packets/Sec

Number of packets per second received from the server.

Server Bytes/Sec

Number of bytes per second received from the server.

Drops/Sec Conn Rate Limit

Number of active connection drops per second based on the connection rate limit of the real server

Drops/Sec Max Conn Limit

Number of active connection drops per second based on the maximum allowable number of active connections to a real server.

ACEs, CSS, CSM

Admin Status

User-specified status of the virtual server, which can be:

In Service—Indicates the server is in service.

Out of Service—Indicates the server is out of service.


Step 2 (Optional) Use the display toggle button () located above the table to control which virtual servers ANM displays as follows:

Show ANM Recognized Virtual Servers—Displays only virtual servers that match ANM's virtual server definition (see the "Virtual Server Configuration and ANM" section).

Show All Virtual Servers—Displays virtual servers that match ANM's virtual server definition and those that do not match this definition but that ANM can recognize as virtual servers using SNMP polling.


Note The display toggle button displays only when you have the "Display All Virtual Servers in Monitoring & Operations page" advanced setting feature enabled (see the "Managing the Display of Virtual Servers in the Operations and Monitoring Windows" section).


Step 3 (Optional) Use the function buttons described in Table 17-9 to update the virtual server information displayed, view graph information, or view the topology map.

Table 17-9 Virtual Server Monitoring Window Function Buttons 

Function Button
Description

Poll Now

Instructs ANM to poll the devices and display the current values. Choose one or more virtual servers and click Poll Now.


Note Even if the periodic polling is enabled, ANM polls all the devices thus ignoring the statistics defined during the periodic polling.


Graph

Displays a historical trend graph of virtual server information for a specific virtual server. Choose 1 to 4 virtual servers and click Graph.

For more information, see the "Configuring Historical Trend and Real Time Graphs for Devices" section.

Topology

Displays the network topology map for a specific virtual server. Choose a virtual server and click Topology.


Note The topology map feature is not available when the Virtual Server table is set to Show All Virtual Servers. Use the display toggle button () to ensure that the Virtual Servers table is set to Show ANM
Recognized Virtual Servers (see Step 2).


The ANM Topology window appears, displaying the virtual server and associated network nodes. For information about using the topology map, see the "Displaying Network Topology Maps" section.



Related Topics

Monitoring Load Balancing on Real Servers

Monitoring Load Balancing on Probes

Configuring Historical Trend and Real Time Graphs for Devices

Monitoring Load Balancing on Real Servers

ANM monitors load balancing and allows you to view the associated real server information.


Note ANM may not display the latest real server information if the periodic polling is disabled. To enable periodic polling, see the "Enabling Polling on All Devices" section.


Procedure


Step 1 Choose Monitor > Devices > device > Load Balancing > Real Servers.

Depending on the device type you selected in the device tree, the information described in Table 17-10 appears.

Table 17-10 Load Balancing Real Server Monitoring Information  

Device Type
Field
Description

All

Real Server

Name of the real server. To view statistics for a selected real server, click the real server hyperlink. The Real Server Details popup window appears containing the individual statistic, associated counter value, and a description of the statistic. Click OK to close the popup window.

IP Address

IP address of the real server. This field appears only for real servers specified as hosts.

Port

Port number used for the server port address translation (PAT).

Admin Status

The specified state of the server, which can be:

Inservice—Indicates the server is in service.

Out of Service—Indicates the server is out of service.

In Service Standby—Indicates the server is a backup server and remains inactive unless the primary server fails. If the primary server fails, the backup server becomes active and starts accepting connections.

Operational Status

The state of the server, which can be:

Inservice—Indicates the server is in service.

Out of Service—Indicates the server is out of service.

Inservice Standby—Indicates the server is a backup server and remains inactive unless the primary server fails. If the primary server fails, the backup server becomes active and starts accepting connections.

Probe Failed—Indicates that ANM did not receive a response to a health probe that it sent to the server.

VM

Indicator that the real server is, or is not, a VMware virtual machine as follows:

- (dash)—The real server is not a VMware VM.

Yes—The real server is a VMware VM. To view details about the VM, click Yes. The Virtual Machine Details popup window appears and provides the following information about the VM:

Full path—Full path to the VM.

DNS Name—DNS name of the VM.

IP Address—VM IP address.

State—Operating state of the VM (for example, poweredOn).

Guest OS—Guest operating system (for example, Red Hat Enterprise Linux 5 (32-bit)).

Host—Host IP address.

Memory (MB)—Amount of memory.

CPU (MHz)—CPU frequency.

Triggered Alarms—Number of recorded triggered alarm conditions.

Click OK to close the Virtual Machine Details popup window.

Weight

Weight assigned to the real server.

ACE, CSM

Server Farm

Primary server farm to use for load balancing.

Current Connections

Number of current connections to this server. If this field indicates N/A, the database does not have any information about current connections. If this field is 0, the database received an SNMP response of 0.

Connections Rate

Connections per second.

Dropped Connections Rate

Dropped connections per second.

ACEs Only

Device

Fully qualified device name.

Locality

Field that pertains to the ACE module A4(2.0), ACE appliance A4(2.0), and later releases of either device type only. Locality also requires that you have the ACE configured for Dynamic Workload Scaling (see the "Configuring Dynamic Workload Scaling" section).

Possible values for real server locality are as follows:

N/A—Not available; the ACE cannot determine the real server location (local or remote). A possible cause for this issue is that Dynamic Workload Scaling is not configured correctly.

Local—The real server is located in the local network.

Remote—The real server is located in the remote network. The ACE bursts traffic to this server when the local real server's CPU and/or memory usage reaches the specified maximum threshold value.

Last Polled

Date and time of the last time that ANM polled the device to display the current values. This field appears if viewing virtual server data at a device level or at a device group level in the device tree.

Note The Last Polled time stamp appears in the table heading if viewing virtual server data at a virtual context level.

CSSs Only

Total Connections

Total number of connections.


Step 2 (Optional) Use the function buttons described in Table 17-11 to update or change the real server information displayed.

Table 17-11 Real Server Monitoring Window Function Buttons 

Function Button
Description

Poll Now

Instructs ANM to poll the devices and display the current values. Choose one or more real servers and click Poll Now. Click OK when asked if you want to poll the devices for data now.

Graph

Displays a historical trend graph of real server information for the specified real servers. Choose 1 to 4 real servers and click Graph. Choosing multiple real servers allows you to compare information.

For more information, see the "Configuring Historical Trend and Real Time Graphs for Devices" section.

Topology

Displays the network topology map for the specified real server. Choose a real server and click Topology.

The ANM Topology window appears, displaying the real server and associated network nodes. For information about using the topology map, see the "Displaying Network Topology Maps" section.



Related Topics

Monitoring Load Balancing

Monitoring Load Balancing on Probes

Configuring Historical Trend and Real Time Graphs for Devices

Monitoring Load Balancing on Probes

To check the health and availability of a real server, the ACE periodically sends a probe to the real server. If you notice an excessive number of probes failing, you can view the monitoring information as shown in the following steps.


Note ANM may not display the latest monitoring information if the periodic polling is disabled. To enable periodic polling, see the "Enabling Polling on All Devices" section.


Procedure


Step 1 Choose Monitor > Devices > ACE > Load Balancing > Probes.

The probe information described in Table 17-12 appears.

Table 17-12 Load Balancing Probes Monitoring Information

Field
Description

Device

Name of the ACE managed by ANM.

Probe

Name of the probe.

To view statistics for a selected probe, click the probe hyperlink. The Probe Details popup window appears containing the following probe statistics:

Failed Probes—Total number of failed probes.

Health of Probes—Health of the probe. Possible values are PASSED or FAILED.

Probes Passed—Total number of passed probes.

Click OK to close the Probe Details popup window.

Type

Type of probe. For a complete list of probe types and their descriptions, see Table 8-11.

Real Server

Name of the real server that the probe is associated with.

Server Farm

Name of the server farm that the probe is associated with.

Port

Port number that the probe uses. By default, the probe uses the port number based on its type.

Probe IP Address

Destination or source address for the probe.

Probed Port

Source of the probe's port number.

Probe Health

Health of the probe. Possible values are PASSED or FAILED.

Passed Rate

Rate of passed probes

Failed Rate

Rate of failed probes

Last Polled

Time stamp for the last probe. This field appears if viewing probe data at a device level or at a device group level in the device tree.

Note The Last Polled time stamp appears in the table heading if viewing probe data at a virtual context level.


Step 2 (Optional) Click Poll Now to instruct ANM to poll the devices and display the current values.

Step 3 (Optional) To view the details associated with a specific probe, choose a probe from the list and click Details.

The show probe probe_name detail CLI command output appears in a popup window.

Step 4 Click OK when asked if you want to poll the devices for data now.


Related Topics

Monitoring Load Balancing

Monitoring Load Balancing Statistics

Configuring Historical Trend and Real Time Graphs for Devices

Monitoring Load Balancing Statistics

You can monitor load balancing on your ACE and CSM devices as shown in the following procedure.


Note ANM may not display the latest load balancing statistics monitoring information if the periodic polling is disabled. To enable periodic polling, see the "Enabling Polling on All Devices" section.


Procedure


Step 1 Choose Monitor > Devices > device > Load Balancing > Statistics.

The Load Balancing Statistics Monitoring Information window displays the information described in Table 17-13.

 

Table 17-13 Load Balancing Statistics Monitoring Information  

Device Type
Field
Description

ACEs only

Device

Name of the device

L4 Policy Connections

Number of Layer 4 policy connections

L7 Policy Connections

Number of Layer 7 policy connections

Failed Connections

Number of failed connections

Dropped L4 Policy Connections

Number of dropped Layer 4 policy connections

Dropped L7 Policy Connections

Number of dropped Layer 7 policy connections

Rejected Connections Due To No Policy Match

Number of connections rejected because they did not match policies

Rejected Connections Due To ACL Deny

Number of connections rejected due to ACL parameters

Rejected Connections Due To L7 Config Changes

Number of rejected connections due to Layer 7 configuration changes

Connection Timed Out

Number of times the connection timed out

Last Polled

Date and time of the last time that ANM polled the device to display the current values

CSM only

Statistic

Name of the monitored statistic

Value

Statistic value

Rate

Statistic rate

Description

Explanation of the monitored CSM statistic


Step 2 (Optional) Click Poll Now to instruct ANM to poll the devices and display the current values and click OK when prompted if you want to poll the devices for data now.

Step 3 (Optional) To display a historical trend graph of load balancing statistics, select up to four objects from the list and click Graph.

The Resource Usage Graph appears (see the "Configuring Historical Trend and Real Time Graphs for Devices" section for details).


Related Topics

Testing Connectivity

Configuring Historical Trend and Real Time Graphs for Devices

Monitoring Application Acceleration

If you have configured application acceleration functions on the ACE, you can monitor the optimization statistics as shown in the following steps.


Step 1 Choose Monitor > Devices > device > Application Acceleration.

The Application Acceleration information appears as shown in Table 17-14.


Note For connection-based syslogs, the following additional parameters are displayed: Source IP, Source Port, Destination IP, Destination Port, and Protocol Information. This allows you to sort and filter on these fields if desired.


.

Table 17-14 Application Acceleration Monitoring View 

Field
Statistic
Description

Condenser Information

Total HTTP Unoptimized Requests Received

Total number of end-user HTTP request the condenser has received that cannot be optimized

Accumulated Bytes Received

Accumulated size (in bytes) of each end-user requested object

Total Responses in Bytes

Accumulated size (in bytes) of responses, both for condensable and non-condensable end-user HTTP requests

Total Abandons of Delta Optimization

Total number of abandons of delta optimization requests

Cacheable Objects Statistics

Total Objects Served from Cache

Total number of cacheable objects served from the cache, excluding the not-modified replies

Accumulated Bytes Served

Accumulated size (in bytes) of the cacheable objects served from the cache, excluding not-modified replies

Total Objects Not Found in Cache

Total number of cacheable objects not found in the cache

Accumulated Bytes Not Found

Accumulated size (in bytes) of the cacheable objects not found in the cache

Total IMS Requests for Valid Cache

Total number of IMS requests for valid copies of objects in the cache

Total Missed IMS Requests

Total number of IMS request for objects that either do not exist or are stale in the cache

Total Non-Cacheable Object Requests

Total number of non-cacheable object requests

Total Requests with Not Modified Responses

Total number of requests for stale objects that have the response from the origin server as not modified

Flash Forward Objects Statistics

Successful Transformations

Total number of successful transformations for FlashForward objects

Unsuccessful Transformations

Total number of unsuccessful transformations for FlashForward objects

Total HTTP Requests

Total number of HTTP requests (excluding the IMS requests) for the transformed FlashForward objects

Total IMS Requests

Total number of IMS requests for transformed FlashForward objects


Step 2 Click Poll Now to instruct ANM to poll the devices and display the current values.

Step 3 Click OK when asked if you want to poll the devices for data now.


Related Topics

Configuring Application Acceleration and Optimization

Displaying the Polling Status of All Managed Objects

You can display the polling status of the following objects that ANM manages: ACE virtual contexts and CSS, CSM, and GSS devices. Because ACE devices are partitioned into virtual contexts that can be polled individually, the polling status window displays the status of each ACE virtual context. From the polling status window, you have the option to restart polling to a virtual context or device that currently has polling disabled.

Guidelines and Restrictions

The time it takes the Polling Status window to reflect global changes that you make to the polling status or polling interval varies depending on the number of managed objects being polled. For information about making global polling changes, see the "Enabling Polling on All Devices" section.

Procedure


Step 1 Choose Monitor > Settings > Polling Status.

The Polling Status window appears.

Table 17-15 Polling Status Window 

Field
Description

Name

Name of the object polled. For all ACE devices, the context names associated with each ACE. For all other object types, such as a GSS, the device name.

Type

Type of object polled. The type will either be Virtual Context to indicate an ACE virtual context or a specific device type, such as GSS.

Polling Config

Polling configuration operational state: Enabled or Disabled. For more information, see the "Setting Polling Parameters" section.

Polling Interval

Frequency at which ANM polls the object.

Polling Status

Current polling status of the managed object:

Missing SNMP Credentials—SNMP credentials are not configured for this object; statistics are not collected. Add SNMPv2c credentials to fix this error.

Not Polled—SNMP polling has not started. For a virtual context, this problem might occur when the virtual context is first created from ANM and the SNMP credentials are not configured. Add SNMPv2c credentials to fix this error.

Polling Failed—SNMP polling failed due to some internal error. Try restarting polling to enable SNMP collection again.

Polling Started—No action is required. Everything is working properly. Polling states will display activity.

Polling Timed Out—SNMP polling has timed out. This problem might occur if the wrong credentials were configured or might be caused by an internal error (such as SNMP was configured incorrectly or the destination is not reachable). Verify that SNMP credentials are correct. If the problem persists, restart polling to enable SNMP collection again.

Unknown—SNMP polling is not working due to one of the above-mentioned conditions. Check the SNMPv2c credential configuration.

Last Polled Time

Time stamp of the last time ANM polled the object.

CLI Sync Status

(ACE virtual contexts only) Administrative configuration status of the context as follows:

Import Failed—The context did not import successfully. This problem could have occurred when the device was added to ANM or when the context was synchronized. Synchronize the context so that you can manage it (Config > Devices > ACE > context > Sync).

OK—The context is synchronized with the ACE CLI.

Out of Sync—The context is managed by ANM but the configuration for the context on the device differs from the configuration managed by ANM. For information on synchronizing contexts, see the "Synchronizing Virtual Context Configurations" section.

Unprovisioned—The context has been removed from the ACE using the CLI but has not been removed from ANM. To remove unprovisioned contexts, synchronize the associated Admin context.

For all polled objects that are not virtual contexts, the value N/A appears in this column because ANM does not support auto synchronization for CSS and CSM devices. It supports this feature for GSS software version 4.1(2) only.

Last CLI Sync Status Change

(ACE virtual contexts only) Time stamp of the last CLI synchronization with ANM.

For all polled objects that are not virtual contexts, the value N/A appears in this column because ANM does not support auto synchronization for CSS and CSM devices. It supports this feature for GSS software version 4.1(2) only.


Step 2 (Optional) To restart polling of an object, check the check box associated with the object and click Restart Polling.


Related Topics

Setting Polling Parameters

Setting Polling Parameters

You set polling parameters differently depending on the device type:

ACE devices—You set polling on specific virtual contexts or configure global polling.

CSM devices—You specify a single polling setting used by ANM.

CSS devices—You specify a single polling setting used by ANM.

GSS devices—You specify a single polling setting used by ANM for VIP Answers operation and configuration states and DNS Rules configuration states.

When you choose Monitoring, the monitoring data for your devices is extracted from cache. The Monitoring window refreshes every two minutes as new monitoring data is gathered.

When you import a context or device into ANM, the polling interval is set to 5 minutes by default. You can modify the polling parameter on each device (see the "Enabling Polling on Specific Devices" section) or you can modify the global parameter polling setting to change the polling parameters for all devices (see the "Enabling Polling on All Devices" section).

This section includes the following topics:

Enabling Polling on All Devices

Disabling Polling on Specific Devices

Enabling Polling on Specific Devices

Disabling Polling on All Devices

Enabling Polling on Specific Devices

Procedure


Step 1 Choose Monitor > Devices > context > Polling Settings.

Step 2 In the Polling Stats field, click Enable.

Step 3 From the Background Polling Interval field, choose a polling interval.

Step 4 Click Deploy Now to save and apply the polling parameters.


Related Topics

Disabling Polling on Specific Devices

Enabling Polling on All Devices

Disabling Polling on All Devices

Displaying the Polling Status of All Managed Objects

Disabling Polling on Specific Devices

Procedure


Step 1 Choose Monitor > Devices > context > Polling Settings.

Step 2 In the Polling Stats field, click Disable.

Step 3 Click Deploy Now to disable polling.


Related Topics

Enabling Polling on Specific Devices

Enabling Polling on All Devices

Disabling Polling on All Devices

Displaying the Polling Status of All Managed Objects

Enabling Polling on All Devices

You can enable polling and set the polling interval for all devices. Some of the configuration and monitoring screens, which are extensively used, may require you to perform polling very frequently. You can select such specific categories and enable periodic polling. This helps ANM to improve the scalability and the performance of the application.

Guidelines and Restrictions

This topic includes the following guidelines and restrictions:

Currently this feature is available for any user under the ANM Inventory role task. When a user is assigned this task, global polling configuration changes made are applied to all devices, irrespective of the domains that are assigned for this user.

The time it takes the Polling Status window to reflect global changes that you make to the polling status or polling interval varies depending on the number of managed objects being polled. For information about viewing polling information, see the "Displaying the Polling Status of All Managed Objects" section.

Procedure


Step 1 Choose Monitor > Settings > Global Polling Configuration.

Step 2 In the Periodic Polling field, click Enable.

Step 3 From the Available list, choose the statistical categories that you want to poll and double-click or use the arrow to move them from the available to the selected column. If no categories are selected, all the categories in the Available list are polled.

The Categories table displays the categories that you can select for polling and the respective ANM pages where the polled data is displayed (see Table 17-16).

Table 17-16 Categories Table

Categories
ANM Page Updated

Virtual Server Operational Stats only

Config > Operations > Virtual Servers

Monitor > Devices > Load Balancing > Virtual Servers

Config > Devices > Load Balancing > Virtual Servers

All Virtual Server Stats

Monitor > Devices > Load Balancing > Virtual Servers

Config > Operations > Virtual Servers

Config > Devices > Load Balancing > Virtual Servers

Monitor > Devices > Dashboard

Interface

Config > Devices > Network > Interfaces

Monitor > Devices > Traffic Summary

Monitor > Devices > Dashboard

Device State and Resource Monitoring

Monitor > Devices > Resource Usage

Monitor > Devices > Dashboard

All Real Server Stats

Monitor > Devices > Load Balancing > Real Servers

Config > Operations > Real Servers

Monitor > Devices > Dashboard

Application Acceleration (4710 only)

Monitor > Devices > Application Acceleration

Real Server Operational Stats only

Config > Operations > Real Servers

Monitor > Devices > Load Balancing > Real Servers

Config > Devices > Load Balancing > Real Servers

Probes

Monitor > Devices > Load Balancing > Probes

Config > Devices > Load Balancing > Health Monitoring

Monitor > Devices > Dashboard


Step 4 From the Background Polling Interval field, choose a polling interval.

Step 5 Click OK to save and apply the polling parameters.


Note When you perform the Poll Now operation on the categories selected in Step 3, ANM ignores the statistics defined here and polls all the devices displaying the current values.



Related Topics

Enabling Polling on Specific Devices

Disabling Polling on Specific Devices

Disabling Polling on All Devices

Displaying the Polling Status of All Managed Objects

Disabling Polling on All Devices

You can disable polling all devices as shown in the following steps.


Note Dashboards, monitoring pages, and configuration pages in ANM may not display the latest information if the periodic polling is disabled.


Procedure


Step 1 Choose Monitor > Settings > Global Polling Configuration.

Step 2 In the Polling Stats field, click Disable.


Note When you disable polling all devices, you will not receive any alarm notification for the threshold groups that you configured in Monitor > Alarm Notifications > Threshold Groups (see "Configuring Alarm Notifications on ANM" section).


Step 3 Click OK.

Polling is disabled.


Related Topics

Enabling Polling on Specific Devices

Disabling Polling on Specific Devices

Enabling Polling on All Devices

Displaying the Polling Status of All Managed Objects

Configuring Historical Trend and Real Time Graphs for Devices

ANM allows you to store historical data for a selected list of statistics calculated over the last hour, 2-hour, 4-hour, 8-hour, 24-hour, or month interval. You can view this historical data as a statistical graph from specific Monitor > Devices monitoring screens. For each monitoring page, default statistics are defined and the graph is drawn for the selected object(s) from the page. ANM also allows you to display real-time statistical information related to the selected monitoring window.


Note All client browsers require that you enable Adobe Flash Player 9 to properly display the monitoring graphs provided in ANM.


Historical graphs are available from the following Monitor > Device monitoring windows:

Traffic Summary window (CSS and ACE devices)

Load Balancing > Virtual Server window (CSM and ACE)

Load Balancing > Real Server window (CSM, CSS, and ACE devices)

Load Balancing > Statistics window (ACE and CSM devices)

Virtual Context-Based Resource Usage (ACE devices)

In each monitoring view window, click the Graph button to view the Graph page. From this page, you can view up to a maximum of four individual graphs of object data. Tooltips appears within each graph to allow you to see the datapoint values used for plotting.

If you choose, you can overlay multiple objects for comparison on the same graph. Each graph grid provides a comma-separated list of select statistics.

ANM supports a maximum of four lines per historical graph. The number of lines in a graph indicates the number of combinations of statistics and the objects (which can be a virtual server, real server, virtual context, and so on). For example, if you select two statistics and two real servers, then the number of possible combinations that can be displayed in a graph is four.


Note The time displayed in all graphs is shown in ANM server time, not in client time.


Procedure


Step 1 Choose Monitor > Devices to view device information.

Step 2 Choose the specific monitoring window from which you want to display historical data graphs for a selected list of items.

Table 17-17 shows the different monitoring window types and how to select one.

Table 17-17 Selecting a Monitoring Window 

To Access....
Select...

Resource Usage window

Monitor > Devices > virtual_context > Resource Usage

Traffic Summary window

Monitor > Devices > Traffic Summary

Virtual Servers window

Monitor > Devices > Load Balancing > Virtual Servers

Real Servers window

Monitor > Devices > Load Balancing > Real Servers

Statistics window

Monitor > Devices > Load Balancing > Statistics


Step 3 Check the check boxes of up to four objects in the selected monitoring window that you want to view and click Graph.

The graph window appears. ANM updates the monitoring window with the graph of the selected objects (see Figure 17-12).


Note The ANM software version that displays across the top of the window varies depending on your version of ANM.


Figure 17-12 Displaying Historical Graphs

Step 4 (Optional) To enhance your viewing of the graphs, use the Collapse/Expand buttons to minimize or maximize a graph in the monitoring window.

Step 5 (Optional) Use the graphing tools described in Table 17-18 to modify the display.

Table 17-18 Historical Graph Tools

Tool
Description

Add Graph button

Adds a graph to the selected monitoring window.

View As Chart
and
View As Grid icons

Toggles the display of an object graph in the monitoring window between a grid and a graph.

The grid displays include the Export to Excel hyperlink that allows you to export object data to Microsoft Excel for archiving or other purposes.

Show As Image icon

Allows you to save the graph as a JPEG file for archiving or other purposes. When you mouse over the graph, the Image Toolbar appears. From the Image Toolbar, you can save the graph as a JPEG or send it in an e-mail. You can also print the graph if desired.

Select button (upper)

Allows you to add one or more objects to a graph in the monitoring window to compare the performance of one object with its peer for the selected statistics. Do the following:

a. In the graph that contains the object you want to replace, click the upper Select button.


Note You cannot perform this function from the Resource Usage graph window, which contains only one Select button. This button is used for selecting multiple statistics (see Select button (lower)).


The Objects Selector popup window appears.

b. From the Objects Selector popup window, choose up to four objects and do one of the following:

Click OK to return to the graph window, which displays your selected objects.

Click Cancel to ignore any selections and return to the original graph.

Select button (lower)

To select multiple statistics for display in a graph in the monitoring window, perform the following steps:

a. In the graph of the object that you want to add statistics, click the lower Select button within the graph.

The Select Stats popup window appears.


Note The Resource Usage graph window contains only one Select button; click this button.


b. From the Select Stats popup window, choose the statistics to add to the graph.

You can choose up to four statistics for display in a graph and the object statistics must be of the same unit of measure (for example, bytes/sec.). The selected statistics appear in the existing object graph in the monitoring window.

Do one of the following:

Click OK to return to the graph window, which displays your selected statistics.

Click Set As Default And Draw Graph to set the current selections as the default objects to graph and return to the graph window, which displays your selected statistics.

Click Cancel to ignore any selections and return to the original graph.

Time drop-down list

Modifies the time interval for the accumulated statistics displayed in a graph. Time interval choices include the average data calculated during the last hour, 2-hour, 4-hour, 8-hour, 24-hour, or 30-day (last month) interval. The time choices also include the Real Time option, which displays a maximum of 3 minutes of data at 10-second intervals (not configurable).

Note the following usage considerations for the time interval for accumulated statistics:

When you specify to view average data calculated during the last hour, 2-hour, 4-hour, or 8-hour interval, raw data points collected by ANM within the selected time period will be displayed. For example, when you specify to view the data of the last hour, if ANM has been collecting data for over an hour at a default 5-minute interval, you will see 12 data points on the graph.

When you specify to view average data calculated during the last 24-hour interval, consolidated hourly data points will be displayed. For example, if ANM has been collecting data for more than 24 hours, you will see 24 data points on the graph.

When you specify to view average data calculated during the last 30-day interval, consolidated daily data points will be displayed. For example, if ANM has been collecting data for over 30 days, you will see 30 data points on the graph.


Step 6 To exit the display of graphs, click Exit Graph.

Exporting Historical Data


Note The data export feature requires either the ANM_ADMIN role or a role with a ANM_System privilege other than no-access.


You can enable or disable the data export feature that allows ANM to export the historical data that it collects on the network devices that it manages. You create a data file purging policy to enable or disable the data export feature and define the purging attributes associated with this feature.

By default, the data export feature is enabled, allowing ANM to export the raw statistical data that it collects during a polling session to the comma-separated values (CSV) data files in the following directory:

/var/lib/anm/export/historical-data/date-stamp

where date-stamp is the directory name, which is based on the date when the file was created and uses the format YYYY-MM-DD. For example, 2010-05-25. The exported data is saved to the files according to device type (for example, ACE_MODULE, CSS, or CSM) and its record type (for example, RT_INT or RT_CPU).

The data export feature includes a data dictionary (stats-export.dict), which defines the device type and record type and can be used to interpret the data content and format of the exported files. You can download the data dictionary, which is written in XML, and display its content using IE browser or any XML editor/viewer, such as Stylus Studio. The data dictionary can be used as a tool when writing a script to extract specific data from a data file. For example, you can create a script that extracts data based on a device type, such as an ACE, that shows interface statistics for a virtual context within the ACE.

Each record/row in the exported data file contains the following information:

Timestamp (in the format defined by the data dictionary)

Device-type

Optional record-type (defined in the data dictionary and used to define the format of each record)

Managed entity name (fully qualified name of the managed object with which the statistical data is associated; it should have the same name shown in the historical graph)

List of statistical data (list order is defined in the data dictionary associated with the record-type)

The first line of each exported data file is a header describing the column of each row. Each field of the record is separated by the separator character, which is currently defined in the data dictionary as the comma. If the metric value is unknown, its value is left empty. Each record is separated by a new line character.

The following data file content sample shows the data file header followed by the statistical information:

DeviceType, RecordType, Timestamp, ManagedEntity, Current Connections, Total Connections, 
Dropped Connections, Total Client Packets, Total Server Packets, Total Client Bytes, Total 
Server Bytes, Total Drops Due To Maximum Connection Limit, Total Drops Due To Connection 
Rate Limit, Total Drops Due To Bandwidth Limit 
DT-ACE-VC,RT-VS,2010-05-28-14:21:08,172.23.244.130:2:Admin/test/global,0,0,0,0,0,0,0,0,0,0
DT-ACE-APPLIANCE-VC,RT-VS,2010-05-28-14:21:08,172.23.244.212:Admin/test_vs_3/global,0,0,0,
0,0,0,0,0,0,0
 
   

The header column names DeviceType, RecordType, Timestamp, and ManagedEntity are mandatory. The definitions of the mandatory headers can be found in the following data dictionary XML tags:

DeviceType definition is inside the device-type tag.

RecordType definition is inside the record-type tag.

ManagedEntity definition is inside the managed-entity tag.

The column names that follow the mandatory names are the display names of the statistic.

Guidelines and Restrictions:

The data export guidelines and restrictions are as follows:

The time at which ANM exports the data file is not configurable.

By default, ANM exports raw historical data only. Snapshots and consolidated historical data (average, minimum, maximum) are not exported.

The data export purging operation guidelines and restrictions are as follows:

ANM purges exported data according to the configurable purging policy. By default, the purging policy instructs ANM to purge the data file if it stays for more than 32 days or the total combined export data is bigger than 10000 M (10 G) of disk space or the disk usage is more than 80 percent.

You can configure ANM to send an email notification to up to five recipients when the disk space usage is higher than the defined threshold.

Each purge action removes at least one day of exported statistical data.

Procedure


Step 1 Choose Monitor > Settings > Historical Data Export.

The Historical Data Export window appears.

Step 2 Configure the data export purging policy as shown in Table 17-19.

Table 17-19 Historical Data Export Fields 

Item
Description

Enabling Historical Data Saving

Check box for saving historical data to the database and exporting the data to a file as follows:

Unchecked—Historical data is not exported to the database.

Checked—Historical data is exported to the database and saved to a file. This is the default setting.


Note If the historical data is not required, we recommend you to uncheck this option and avoid saving the data to the database. This helps to improve the performance of the database.


Retention Period (In Days)

Maximum number of days that ANM is to keep the exported data files. The valid range is 1 to 365 days. The default is 32.

Maximum Size Of Exported Data (In MBytes)

Maximum allowable size of the data file to export. The valid range is 100 MB to 100000 MB. The default is 10000 MB.

Current Size Of Exported Data (In MBytes)

(Read only) Current size of the data file.

Disk Space Utilization Threshold (In %)

Percentage of disk space that the data file can utilize.

Current Disk Space Utilization (In %)

(Read only) Current amount of disk space that the data file is utilizing.

Do You Want To Disable Data Export

Check box for enabling or disabling the data export feature as follows:

Unchecked—Data export is enabled. This is the default setting.

Checked—Data export is disabled.

E-mail Address To Send Notification When Disk Usage Is Greater Than Disk Space Utilization Threshold Setting

Email addresses that ANM sends a notification to when the amount of disk space utilized by the data file exceeds the specified Disk Space Utilization Threshold value. ANM sends an email notification only once every 24 hours even when threshold-exceeding condition persists.

Enter an email address and click the right arrow to add it to the list of email addresses to receive notifications. You can specify up to five email addresses. To edit or remove an address from the list, use the left arrow or double-click the address to move it to the edit box where you can modify or delete it.


Note For email notifications, you must specify an SMTP server to use for outgoing emails (see the "Configuring SMTP for Email Notifications" section).


Status

Current status of the data export feature as follows:

RUNNING—Data export is enabled. An alert message may display in parenthesis next to the Running status.

STOP—Data export is disabled.

To change the status, see the Do You Want To Disable Data Export checkbox.

Statistical Data Last Purge At

(Read only) Server time when ANM last purged the data file.

Reason For Purging

(Read only) Reason why ANM purged the data file; retention period, total size of the exported data file, or disk space usage.

Location Of Exported Data

(Read only) Path to the exported data files: /var/lib/anm/export/historical-data.


Step 3 (Optional) To download a copy of the data dictionary in zip file format, click Download Data Dictionary.

Step 4 To save the current data file purging policy, click Save.


Related Topics

Configuring SMTP for Email Notifications

Monitoring Events

The events captured in the Events table include both ACE syslog events and SNMP trap events. A procedure for viewing both types of events and details of information extracted from the syslog are shown below. Fields providing traffic-oriented sorting capability, specifically the information signified by the column heads in the Events Fields window, shown in Table 17-20 (Source IP, Source Port, Destination IP, Destination Port, and Protocol) are only available for the ACE syslogs.


Note We do not recommend that you send a high volume of syslogs to ANM. ANM will only process and persist syslogs at 100 messages per second. Any additional syslogs sent to ANM beyond that rate will be discarded. To address this behavior, set the syslog severity level to a setting that is no higher than the warning level (a severity level of 4-Warning). See the "Configuring Virtual Context Syslog Settings" section for details.


Assumptions

To receive events from devices, the devices must have syslog and SNMP traps configured correctly. See the "Configuring Virtual Context Syslog Settings" section and the "Configuring SNMP for Virtual Contexts" section.

Procedure


Step 1 Choose Monitor > Events.

ANM displays all events received from ACE for Syslog and SNMP traps for all virtual contexts. See Table 17-20 for a description of the displayed information, which is extracted from the syslog.

You can sort information in the table by clicking on a column heading. This allows you to group events and help troubleshooting traffic information.

Table 17-20 Monitor > Events Fields 

Field
Description

Syslog ID/SNMP ID

Displays the Syslog ID and SNMP ID. If the event is a trap, this field is empty.

Severity

Indicates the syslog severity level as described in Table 6-5.

Origination Time

Date and time that the event was last changed in the database.

Source IP

Displays the source name that is reporting the event, for example, <chassis/slot>:virtual_context.

Source Port

Displays the source port.

Destination IP

Displays the IP address of the destination if available.

Destination Port

Displays the destination port if available.

Protocol

Protocol used in the syslog.

Detail

Provides additional detail about the event.


Table 17-21 displays the complete list of published ACE syslogs where source and destination IP, ports and protocols are parsed so that the designated table fields populate.


Note Only the ACE syslog messages shown in this table will populate the Events window fields explained in Table 17-20. Syslogs and traps not in this table will populate fields with a 0.


Table 17-21 ACE Syslogs Fields with Perishable Traffic Oriented Sorting Information 

Syslog
Message Contents

ACE-1-106021

Deny protocol reverse path check from source_address to dest_address on interface interface_name

ACE-4-106023

Deny protocol number | name src incoming-interface:src-ip dst outgoing-interface:dst-ip by access-group "acl-name" (hash 1, hash 2)

ACE-6-302022

Built TCP connection id for interface:real-address/real-port (mapped-address/mapped-port) to interface:real-address/real-port (mapped-address/mapped-port)

ACE-6-302023

Teardown TCP connection id for interface:real-address/real-port to interface:real-address/real-port duration hh:mm:ss bytes bytes [reason]

ACE-6-302024

Built UDP connection id for interface:real-address/real-port (mapped-address/mapped-port) to interface:real-address/real-port (mapped-address/mapped-port)

ACE-6-302025

Teardown UDP connection id for interface:real-address/real-port to interface:real-address/real-port duration hh:mm:ss bytes bytes

ACE-6-302026

Built ICMP connection for faddr/NATed_ID gaddr/icmp_type laddr/icmpID

ACE-6-302027

Teardown ICMP connection for faddr/NATed ID gaddr/icmp_type laddr/icmpID

ACE-6-302028

Built TCP connection id for interface: real-address/real-port (mapped-address/mapped-port) to interface: real-address/real-port (mapped-address/mapped-port)

ACE-6-302029

Teardown TCP connection id for interface: real-address/real-port to interface: real-address/real-port duration hh:mm:ss bytes bytes [reason]

ACE-6-302030

Built UDP connection id for interface: real-address/real-port (mapped-address/mapped-port) to interface: real-address/real-port (mapped-address/mapped-port)

ACE-6-302031

Teardown UDP connection id for interface: real-address/real-port to interface: real-address/real-port duration hh:mm:ss bytes bytes

ACE-4-313004

Denied ICMP type=icmp_type, from source_address on interface interface_name to dest_address:no matching session

ACE-4-410001

Dropped UDP DNS packet_type from source_interface:source_address/source_port to dest_interface:dest_address/dest_port; error_length_type length length bytes exceeds max_length_type limit of maximum_length bytes.



Related Topics

Monitoring Devices

Performing Device Audit Trail Logging

Configuring Alarm Notifications on ANM

To set up Monitoring alarm notifications, you define a threshold group and specify the statistics to be monitored by ANM for the threshold group. When the value for a specific statistic rises above the setting you specify, an alarm is issued to alert you.


Note CISCO-EPM-NOTIFICAITON-MIB is used for ANM alarms notification.


You can specify how you are notified when thresholds are crossed:

Alarm notification, which you view at Monitor > Alarm Notifications > Alarms.

Email notification.

Traps.

Mobile device alarm notification. This method requires ANM 5.1 or later and a supported mobile device with the Cisco ANM Mobile app. For more information about ANM Mobile, see Chapter 19 "Using ANM Mobile."


Note Threshold crossing is detected using periodic polling. If a threshold is crossed between polling cycles, it is possible that ANM License Manager might not issue an alert if the condition recovers before the next polling cycle.


Guidelines and Restrictions

For certificates that you have loaded on the ACE, you can configure ANM to issue an alarm notification when the certificate expiration date is approaching. ANM performs certificate expiration computations every 24 hours. The computation begins each time ANM is started. Every subsequent computation occurs 24 hours thereafter.


Note The Certificates window (Config > Devices > context > SSL > Certificates) contains the Expiry Date field, which displays the certificate expiration date. Due to a known issue with the ACE module and appliance, it is possible that this field displays either "Null" or characters that cannot be parsed or that are unreadable. When this issue occurs, ANM cannot track the certificate expiration date. If the certificate is defined in a threshold group configured for certificate expiration alarm notifications and this issue occurs, ANM may not issue an expiration alarm when expected or it may issue a false alarm. If you encounter this issue, remove the certificate from the ACE, reimport it, and then verify that the correct expiration date appears in the Certificates window.


Prerequisites

For email notifications, you have specified an SMTP server to use for outgoing emails (see the "Configuring SMTP for Email Notifications" section).

Procedure


Step 1 Choose Monitor > Alarm Notifications > Threshold Groups, and click Add.

Step 2 In the Properties section, enter the name and description for the threshold group.

Step 3 In the Threshold Settings section, click Add and then enter the following information shown in Table 17-22.

Table 17-22 Threshold Settings Fields

Field
Description

Device Type

Choose the device type to include in the threshold group. VC indicates ACE virtual context.

Category

Choose a statistic to include in the threshold group. Table 17-23 identifies and describes the types of statistics available for each device type.

Note We do not recommend that you include ACL Memory (ACE module and ACE appliance) or Current Application Acceleration Connections (ACE appliance only) as statistics in a threshold group. The values provide through the associated show resource usage CLI command regarding the utilization of these two threshold parameters does not accurately reflect the real usage of these two resources.

Assert on Value

Enter a value to define the threshold. When the statistic exceeds this value, an alarm is issued. Some values are displayed as percentages as indicated by the percent sign (%).

In the case of SSL certificate expiration, assert on value indicates the number of days before certificate expiration. Alarms will be updated daily to indicate the number of days remaining until certificate expiration. If the email is configured, you will be sent email daily alerting you to the number of days left before expiration.

Clear Value

Enter a value on which to clear the alarm.

In the case of SSL certificate expiration, the setting has no relevance. When an expired certificate is deleted, the alarm is removed from ANM on the subsequent certificate evaluation. This happens every 24 hours.

Notify on Clear

Check the Notify on Clear check box to receive an email notification to the specified address when the alarm is cleared.

Severity

Choose a severity level for this threshold, which can be Critical, Info, Major, or Minor.


Table 17-23 provides details for the Category field found in Table 17-22.

Table 17-23 Monitoring Thresholds by Device Type 

Category
Threshold
Description
ACE 4710 Appliance
 

ACL Memory

Percentage of memory allocated for ACLs.

Note We do not recommend that you include ACL Memory as a statistic in a threshold group. The value provided through the associated show resource usage CLI command regarding the utilization of ACL memory does not accurately reflect the real usage of this resource.

Bandwidth

Percentage of throughput.

Concurrent Connections

Percentage of simultaneous connections.

Current Application Acceleration Connections

Percentage of application acceleration connections.

Note We do not recommend that you include Current Application Acceleration Connections as a statistic in a threshold group. The value provided through the associated show resource usage CLI command regarding the utilization of application acceleration connections does not accurately reflect the real usage of this resource.

Current Connection Rate

Percentage of connections of any kind.

Current HTTP Compression Rate

Percentage of compression for HTTP data.

Inspect Connection Rate

Percentage of application protocol inspection connections.

MAC Miss Rate

Percentage of messages destined for the ACE that are sent to the control plane when the encapsulation is not correct in packets.

Management Connections

Percentage of management connections.

Management Traffic Rate

Percentage of management traffic connections.

Proxy Connections Rate

Percentage of proxy connections.

Regular Expression Memory

Percentage of regular expression memory.

SSL Connection Rate

Percentage of SSL connections.

Sticky

Percentage of entries in the sticky table.

Syslog Buffer Size

Percentage of the syslog buffer.

Syslog Message Rate

Percentage of syslog messages per second.

Translation Entries

Percentage of network and port address translations.

Device

Device Status

ACE operating status changes from Up to Down and vice versa.

ACE 4710 Appliance VC

Application Acceleration

Condenser State

State of the condenser.

HA

Redundancy State

ACE virtual context HA or fault tolerance (FT) state changes. Possible FT states are Active, Standby Hot, and Other, which represents all other FT states, including the following:

Non-Redundant—Virtual context is not included in any FT group.

Unknown—Virtual context becomes inaccessible, for example if the ACE that it resides in becomes unresponsive.

Interface

Interface Operational State

Operational state of the interface.

Probes

Probe Health State

Operational health of the health monitoring probe.

Real Server1

Real Server Current Connections

Number of current connections on a real server.

Real Server Operational State

Operational state of a real server.

SLB Stat

Layer 4 Policy Connections

Number of Layer 4 policy connections.

Layer 7 Policy Connections

Number of Layer 7 policy connections.

SSL Certificate Management

SSL certificate expiration (in days)

Number of days left before SSL certificate expires whose value minus one will send a warning email with the specified severity. ANM updates this field daily.

Virtual Server1

Virtual Server Current Connections

Number of active virtual server connections.

Virtual Server Operational State

Operational state of a virtual server.

ACE Module
 

ACL Memory

Percentage of memory allocated for ACLs.

Note We do not recommend that you include ACL Memory as a statistic in a threshold group. The value provided through the associated show resource usage CLI command regarding the utilization of ACL memory does not accurately reflect the real usage of this resource.

Bandwidth

Percentage of bandwidth.

Concurrent Connections

Percentage of simultaneous connections.

Current Connection Rate

Percentage of connections of any kind.

Current HTTP Compression Rate

Percentage of compression for HTTP data. This field appears only for an ACE module version A4(1.0) or later.

Inspect Connection Rate

Percentage of application protocol inspection connections.

MAC Miss Rate

Percentage of messages destined for the ACE that are sent to the control plane when the encapsulation is not correct in packets.

Management Connections

Percentage of management connections.

Management Traffic Rate

Percentage of management traffic connections.

Proxy Connections

Percentage of proxy connections.

Regular Expression Memory

Percentage of regular expression memory.

SSL Connection Rate

Percentage of SSL connections.

Syslog Buffer Size

Percentage of the syslog buffer.

Sticky

Percentage of entries in the sticky table.

Syslog Message Rate

Percentage of syslog messages per second.

Throughput

Percentage of throughput.

Translation Entries

Percentage of network and port address translations.

Device

Device Status

ACE operating status changes from Up to Down and vice versa.

ACE Module VC

HA

Redundancy State

ACE virtual context HA or fault tolerance (FT) state changes. Possible FT states are Active, Standby Hot, and Other, which represents all other FT states, including the following:

Non-Redundant—Virtual context is not included in any FT group.

Unknown—Context becomes inaccessible, for example if the ACE that it resides in becomes unresponsive.

Interface

Interface Operational State

Operational state of the interface.

Probes

Probe Health

Operational health of the health monitoring probe.

Real Server1

Real Server Current Connections

Number of current connections on a real server.

Real Server Operational State

Operational state of a real server.

SLB Stat

Layer 4 Policy Connections

Number of Layer 4 policy connections.

Layer 7 Policy Connections

Number of Layer 7 policy connections.

SSL Certificate Management

SSL certificate expiration (in days)

Number of days left before SLL certificate expires whose value minus one will send a warning email with the specified severity. ANM updates this field daily.

Virtual Server1

Virtual Server Current Connections

Number of active virtual server connections.

Virtual Server Operational State

Operational state of a virtual server.

CSM Module

Real Server

Real Server Connections

Number of real server connections.

Real Server Current State

Operational state of a real server.

SLB Stat

Current Opened Connections

Number of open connections.

Layer 4 Policy Connections

Number of Layer 4 policy connections.

Layer 7 Policy Connections

Number of Layer 7 policy connections.

SLB Virtual Server

Virtual Server Connections

Number of virtual server connections.

Virtual Server State

Operational state of a virtual server.

System

CSM Fault Tolerance State

Fault tolerance state of the CSM.

Device

Device Status

CSM operating status changes from Up to Down and vice versa.

CSS

Interface

Average TCP Packets

Average number of TCP packets.

Interface Operational State

Operational state of the interface.

Max TCP Packets

Maximum number of TCP packets.

Real Server

Active Service Connections

Number of active real server connections.

Real Server State

State of a real server.

System

CSS Fault Tolerance State

Fault tolerance state of the CSS.

CSS Module State

State of a CSS module.

Virtual Server

Virtual Server State

Current state of a virtual server.

Device

Device Status

CSS operating status changes from Up to Down and vice versa.

GSS

Device

Device Status

GSS operating status changes from Up to Down and vice versa.

1 Category choices support mobile device notifications.


Step 4 Click OK.

Step 5 In Device Selection, choose the device type to include in the threshold group.

The available devices appear in the Available Items field.


Note Make sure that the device type you select in this field is supported by the threshold that you selected in the Category field in Step 3. If the device type you select is not supported by the threshold you selected, you will not receive alarm notifications.


Step 6 Click on a device in the Available Items field, and then the arrow (>) to move the device to the Selected Items field.

Step 7 In the Notify By section, do the following:

a. In the E-mail field, enter the email address that you want to receive notification email.

See the "Displaying Email Notifications" section for information contained in the email notifications. If you do not select this field, you must view alarm notifications by selecting Monitor > Alarm Notifications > Alarm.


Note You must configure the required host parameters, IP address and port, to send email notifications. See the "Configuring SMTP for Email Notifications" section.


b. Check the Domain sensitive email notification check box to receive filtered email about certificate expirations for the certificates defined in the current domain only. The emails are sent to the email address configured for the RBAC user definition (see the "Managing User Accounts" section). Uncheck this check box to disable this feature.


Note This attribute appears only when the selected device type is either the ACE 4710 VC or the ACE VC and the category type is set to SSL Certificate expirations (in days).


c. In the Traps field, enter the host IP Address and port number of the machine to which the traps are sent.

See the "Displaying Traps" section for information contained in the traps.

d. Check the Mobile Notifications check box to allow ANM to send alarm notifications to supported smart devices that use the ANM Mobile app. This notification option is available when you choose threshold settings in Step 3 for real or virtual servers for device types ACE 4710 VC and ACE VC.

See the "Setting Up and Viewing Mobile Device Alarm Notifications" section for information about setting up alarm notifications on your mobile device.

Step 8 Do one of the following:

Click Save to save the threshold group settings.

Click Cancel to cancel the threshold group settings and return to the Threshold Groups page.


Note If the periodic polling is disabled, you will not receive alarm notifications for the threshold group that you just configured.



Related Topics

Configuring SMTP for Email Notifications

Displaying Alarm Notifications

Displaying Alarm Notifications

You can display the alarm notification that ANM issues when the value for a statistic exceeds a specified threshold value. Depending on how you specified to be notified when a threshold is crossed, you can view all alarm notifications, email notifications, or alarm traps.

Guidelines and Restrictions

Threshold crossing is detected using periodic polling. If a threshold is crossed between polling cycles, it is possible that ANM License Manager might not issue an alert if the condition recovers before the next polling cycle.

Prerequisites

You have configured alarm notifications as described in the "Configuring Alarm Notifications on ANM" section.

This section includes the following topics:

Displaying Alarms in ANM.

Displaying Email Notifications.

Displaying Traps.

Displaying Alarms in ANM

You can display the alarms that ANM issues when the value for a statistic exceeds a specified threshold value.

Guidelines and Restrictions

This topic includes the following guidelines and restrictions:

ANM displays only the alarms for the devices that are in the domain definition of the RBAC user logged into ANM.

If an alarm has been cleared, it does not appear on the Monitor > Alarm Notifications > Alarms page. This page displays active alarms only.

Prerequisites

You have configured alarm notifications as described in the "Configuring Alarm Notifications on ANM" section.

Procedure


Step 1 Choose Monitor > Alarm Notifications > Alarms.

The Alarms window appears, displaying the list of alarm notifications issued by ANM. Table 17-24 describes the information displayed for each notification.

Table 17-24 ANM Alarm Notification Content 

Field
Description

Source ID

ANM server IP address that issued the alarm

Severity

Specified severity level of the threshold, which can be one of the following:

Info

Critical

Major

Minor

Origination Time

Time the alarm was issued

Threshold Group

Specified threshold group name

Category

Alarm name

Component

Component name, for example, VLAN20

State/Value

Specified state or value of the alarm

Detail

Displays additional information about the alarm.

Notes

Allows you to add any notes to this alarm.


:

Step 2 (Optional) To view a statistical graph of a component with an issue, choose an alarm notification and click Graph The Component With Issue.

The Graph popup window appears, showing an analysis of the default statistical units being measured (y-axis) to date and time (x-axis). The component type determines the default statistical units being measured. For example, the units being measured for the real server component type is the number of connections.


Note This button can only be used with alarm notifications for the following component types: real server, virtual server, or interface.



Related Topics

Configuring SMTP for Email Notifications

Configuring Alarm Notifications on ANM

Displaying Email Notifications

Displaying Email Notifications

After you configure alarm notifications (see the "Configuring Alarm Notifications on ANM" section) and specify to receive notification email, when the value for a specific statistic rises above the setting you specify, ANM sends an email to alert you.

Table 17-25 describes the information contained in the email alarm notification.

Table 17-25 Email Alarm Notification Content 

Field
Description

ANM Server Host Name

ANM server host name

ANM Server IP Address

ANM server IP address

Device ID

Device name

Component Name

Component name, for example, VLAN20

Severity

Specified severity level of the threshold, which can be one of the following:

Info

Critical

Major

Minor

Time

Time the alarm was issued

Alarm Name

Specified name of the alarm

Alarm Value

Specified value of the alarm

Threshold Assert Value

Specified value on when to issue the alarm

Threshold Group Name

Specified threshold group name

Alarm State

State of the alarm which can be one of the following:

Active

Clear


Related Topics

Configuring Alarm Notifications on ANM

Displaying Alarm Notifications

Displaying Traps

After you configure alarm notifications (see the "Configuring Alarm Notifications on ANM" section) and specify to send traps to a trap receiver, when the value for a specific statistic rises above the setting you specify, ANM issues a trap to alert you.

Related Topics

Configuring Alarm Notifications on ANM

Displaying Alarm Notifications

Configuring SMTP for Email Notifications

You can specify that email notifications be sent each time a monitoring threshold is crossed. You can request alert emails when configuring a threshold group (Monitor > Alarm Notifications > Threshold Groups) or when enabling the historical data export feature (Monitor > Settings > Historical Data Export).


Note You must configure ANM with your SMTP server information to receive email notifications.


Assumption

You have configured threshold crossing alerts (see the "Configuring Alarm Notifications on ANM" section) or enabled the historical data export feature (see the "Exporting Historical Data" section).

Procedure


Step 1 Choose Monitor > Settings > SMTP Configuration.

Step 2 In the SMTP Server to Send E-mail Notifications field, enter your SMTP server.

Step 3 (Optional) In the MAIL FROM for all Email notifications field, enter the source email address to use for email notifications.

By default, the Mail From address is anm@hostname.

Step 4 Click Deploy Now to apply the SMTP configuration.


Related Topics

Exporting Historical Data

Monitoring Events

Configuring Alarm Notifications on ANM

Displaying Email Notifications

Displaying Network Topology Maps

This section shows how to display and use the network topology maps that display the nodes on your network based on the virtual or real server that you select. Figure 17-13 shows a sample network topology map.


Note The ANM software version that displays across the top of the window varies depending on your version of ANM.


Figure 17-13 Sample ANM Topology Map

Table 17-26 describes the callouts shown in Figure 17-13.

Table 17-26 Network Topology Map Components 

Item
Description

1

Topology map tool bar that contains the following tools:

Layout—Changes the direction in which the network map appears. Choose one of the following options from the drop-down list: Top to Bottom or Left to Right.

Zoom—Modifies the size of the network map. Click and drag the slide bar pointer to adjust the map size.

Magnifier—Toggle button that enables or disables the magnifier tool. When enabled, moving your mouse over the the topology map magnifies the area that the mouse is over.

Fit Content—Fits the topology map to the window.

Overview—Toggle button that enables or disables the Overview Window tool (see Callout 3).

Undo—Sets the network node icons back to their previous positions.

Redo—Redoes the changes that you made before you clicked Undo.

Print—Sends the topology map to the network printer.

Exit—Closes the topology map and returns to the previous window.

2

Topology Map—Displays network node mapping.

The node icons display the following information related to the node:

Name

IP address (virtual and real servers only)

Port (real servers only)

Operational state (virtual and real servers only)

When you hover over a network node icon, the node type appears, for example ACE Virtual Server, Server Farm, or Real Server. Other possible operations when you hover over a network node icon are as follows:

Real servers only—When you have an ACE configured for Dynamic Workload Scaling and you mouseover an associated real server icon, information appears that identifies which data center the real server is located in: local or remote. A timestamp also appears that specifies when the information was obtained.

Server farms only—When you mouseover a server farm icon, the following Dynamic Workload Scaling status information appears:

Local—The ACE is using the server farm's local real servers only for load balancing. A timestamp specifies when the information was obtained.

Burst—The ACE is bursting traffic to the server farm's remote real servers because the load of the local real servers has exceeded the specified usage threshold (based on the average CPU and/or memory usage). A timestamp specifies when the information was obtained.

N/A—Not applicable (Dynamic Workload Scaling is not available).

For more information about Dynamic Workload Scaling, see the "Dynamic Workload Scaling Overview" section.

To view details about a network node, right-click on the node and choose Show Details from the popup menu. To reposition a node in the map, click and drag the node icon to a new position. The node interconnect lines move with the node.

3

Overview Window—Provides a combined functionality of the scroll bars and zoom tool as follows:

Position tool (a)—Click and drag the shaded box to move around the topology map.

Zoom tool (b)—Click and drag the shaded box handle (located in lower right corner) and to zoom in or out of the topology map.

Click the Overview toggle button in the map tool bar to display or hide the Overview window.


Table 17-27 shows the locations in the ANM GUI where you can access the topology maps for real servers and virtual servers.

Table 17-27 ANM Topology Map GUI Locations

GUI location
For more information, see . . .

Config > Operations > Real Servers

Using the Real Server Topology Map

Config > Operations > Virtual Servers

Using the Virtual Server Topology Map

Monitor > Devices > Loadbalancing > Real Servers

This section.

Monitor > Devices > Loadbalancing > Virtual Servers


Procedure


Step 1 Do one of the following:

Display the list of virtual servers by choosing Monitor > Devices > context > Loadbalancing > Virtual Servers.

The Virtual Servers window appears with the table of configured virtual servers.

Display the list of real servers, choose Monitor > Devices > context > Loadbalancing > Real Servers.

The Real Servers window appears with the table of configured virtual servers.

Step 2 From the servers table, check the check box next to the server whose topology map you want to display.

Step 3 From the servers window, click Topology.

The ANM Topology window displays the topology map for the selected virtual or real server. For information about using the topology map tools, see Figure 17-13 and Table 17-26.

Step 4 (Optional) To close the topology map and return to the previous window, from the ANM Topology window, click Exit.


Testing Connectivity

You can verify the connectivity (using the ping command) between ANM and the IP address you specify.


Note The Ping feature is disabled if you have not imported any devices into the ANM server.


Procedure


Step 1 Choose Monitor > Tools > Ping.

Step 2 From the object selector field, choose the device you want to test.

Step 3 Enter the information shown in Table 17-28.

Table 17-28 Ping Fields

Field
Description

IP Address Type

Choose either IPv4 or IPv6 for the address type of the real server. This field appears only for ACE module and ACE appliance software version A5(1.0) or later, which supports IPv4 and IPv6.

IP Address

IP address of the real server to which you want to ping.

Elapsed Time

Elapsed time before the ping request is declared a failure.

Repeat

Number of times to repeat the test.

Datagram Size

Value for the argument size (size of the packet) of the ping command.


Step 4 Click Start to run the connectivity test.

After the test completes, the results are displayed.

Step 5 Do one of the following:

Click New to enter new parameters and create a new ping test.

Click Restart to rerun the connectivity test.


Related Topics

Setting Up Devices for Monitoring