-
Cisco Application Velocity System User Guide (Software Version 5.0)
-
Preface
-
Product Overview
-
AVS Description
-
Appliance Administration
-
Command Line Interface
-
Configuration Reference
-
AppScreen Configuration
-
Management Console
-
Reporting
-
NMS Integration
-
Availability Manager Clustering
-
Database Maintenance
-
Logs
-
SNMP MIB
-
Deployment Options
-
Frequently Asked Questions and Troubleshooting
-
Anonymous Base File Statistical Model
-
Regular Expressions
-
AppScreen Rules DTD
-
Glossary
-
Index
-
Table Of Contents
Example Query with HP OpenView
Example Graph with HP OpenView
NMS Integration
The application appliance includes a Network Management System (NMS) integration feature that makes the AppScope performance data available via SNMP MIBs to a NMS. This allows an administrator at a NMS console to identify and investigate performance issues.
Note
If you have installed only a Cisco AVS 3120 Application Velocity System, NMS integration and reporting features are not available and you will not see a Reports folder in the menu at the left side of the Management Console window. You must be running the Management Console on a Cisco AVS 3180 Management Station in order to see the Report items in the Management Console. This note does not apply to users who have performed software upgrades to AVS 5.0 from older software products or on the Velocity Appliance.
This chapter describes the NMS integration features and the user interface via which you manage it.
Transaction Grouping
AppScope collects statistics for each transaction that it measures. It is possible to use the NMS feature to get a global summary of the statistics for all transactions. However, it is generally more useful to collect and display statistics based on some logical grouping of transactions.
A transaction group is a set of transactions whose statistics will be collected and grouped together for reporting and analysis. A transaction group can be based either on transaction types or on business transactions, but not on a mixture of the two.
A transaction group based on transaction types is defined by specifying the transaction type and source location of the transactions. Such a transaction group definition can include zero or more transaction types, and zero or more source locations. A transaction group based on business transactions is defined in a similar way, but with business transactions rather than transaction types. Examples of transaction groups are shown in Table 9-1.
Source locations are defined by using the Manage Locations command as described in the "Managing Locations" section.
Transaction types are defined by using the Transaction Types command as described in the "Defining Transaction Types" section.
Business transactions are defined by using the Business Transaction Types command as described in the "Defining Business Transactions" section.
After you have defined any source locations and transaction types or business transactions that you need, you define the transaction groups by using the Transaction Groups command as described next in "Defining Transaction Groups".
Defining Transaction Groups
After you have defined any source locations and transaction types or business transactions that you need, you define transaction groups by using the Transaction Groups command. Each transaction group definition can include zero or more transaction types or business transactions, and zero or more source locations. Examples of transaction groups are shown in Table 9-1.
Use the Transaction Groups command (under the Reports folder in the left pane) to view a list of all defined transaction groups, as shown in Figure 9-1.
Figure 9-1 Transaction Groups Page
Each row in the table lists one saved transaction group; the transaction group name is shown, followed by its short name, type, ID, the transaction types included in the group, the locations included in the group, and the data collection status (enabled or disabled).
Each transaction group has a system-assigned integer ID. The ID numbers start with the value 101 and they are incremented by one for each new group. Old values are not reused, even if a new group has the same name as a deleted group. The ID serves as the SNMP index into the statistics table.
To add a transaction group based on transaction types, click the Create Transaction Group link above the table. To add a transaction group based on business transactions, click the Create Business Transaction Group link above the table. Click the Edit or Delete links next to a transaction group to edit or delete the transaction group.
You can disable data collection for any transaction group so that you can temporarily stop collecting data for a group without having to delete it. To disable data collection for a group, click the Disable link next to it. If it is already disabled and you want to enable data collection, click the Enable link.
Adding a Transaction Group
You can add a transaction group by clicking either the Create Transaction Group or Create Business Transaction Group link above the table. The create/edit transaction group page is displayed, as shown in Figure 9-2.
Figure 9-2 Create/Edit Transaction Group Page
Enter a name for the transaction group in the Name field, and enter a short name in the Short Name field.
To enable or disable data collection for this transaction group, check or uncheck the Enable box next to Data Collection.
In the Transaction Types (or Business Transaction Types) area, add all the desired transaction or business transaction types to this group by moving them from the Available list on the left to the Selected list on the right. To add a transaction type, select it in the Available list and click Add. To remove a transaction type, select it in the Selected list and click Remove. You can Control-click to select multiple entries in a list and Shift-click to select a range.
In the Locations area, add all the desired locations to this group by moving them from the Available list on the left to the Selected list on the right. To add a location, select it in the Available list and click Add. To remove a location, select it in the Selected list and click Remove. You can Control-click to select multiple entries in a list and Shift-click to select a range. You create locations by using the Manage Locations command, described in the "Managing Locations" section.
To save the transaction group, click Save, or to cancel its creation or editing, click Cancel.
Note that a group with no transaction types and no locations is valid. Such a group collects statistics for all transactions.
Editing a Transaction Group
You can edit a transaction group by clicking the Edit link on the same row as the group. The create/edit transaction group page is displayed, as shown in Figure 9-2. The process for editing a transaction group is exactly the same as described in the "Adding a Transaction Group" section.
Deleting a Transaction Group
You can delete a transaction group by clicking the Delete link on the same row as the group. A confirmation dialog will ask you to confirm the deletion.
Data Lifecycle
The AppScope SNMP agent has a data aggregator that collects the AppScope transaction type statistics every 5 minutes and the business transaction statistics every 60 minutes by default. These intervals can be changed by editing the following parameters in the console.properties file:
•
NMS_AGGREGATION_DURATION_IN_MINS=5•
NMS_BT_AGGREGATION_DURATION_IN_MINS=60The default location of this file is $AVS_HOME/console/jboss-3.0.1_tomcat-4.0.4/server/default/deploy/condenser-mbeans.sar/properties/console.properties. The Management Console needs to be restarted after making any changes. Note that if you upgraded the product from a previous version, the NMS_BT_AGGREGATION_DURATION_IN_MINS parameter might not exist in this file and you can change the value simply by adding it.
When the user issues an SNMP Get query (for example, through an NMS Manager such as HP OpenView), the AppScope SNMP agent returns transaction type statistics for the immediately preceding 5 minutes. This aggregation duration can be adjusted. However, the aggregation duration must be equal to or greater than the collection interval.
As each collection interval goes by, the most recent statistics are collected and stored in the data aggregator, and the least recent statistics are dropped. Using an SNMP Get query, the client application can retrieve the statistics for only the most recent aggregation duration number of minutes. For example, the client cannot ask for data from an earlier point in time, or data for a longer duration.
If you wish to save and access historical SNMP data, you can use one of these methods:
•
•
Also, the same statistical data that is available via SNMP is stored in the AppScope database for longer-term access via AppScope reports, or any database or reporting tool that you would like to use.
MIB Data Elements
The following data points are collected for each defined transaction group:
•
•
•
•
•
•
•
•
•
The Percent Optimized is the percentage of Optimized to Passthrough (rounded to the nearest whole percentage point). For example, Percent Optimized Numhits is the percentage of optimized hits; if this is 80%, then 80% of hits were optimized and 20% were passthrough. Percent Optimized Page Time is (Average Optimized Page Time / Average Passthrough Page Time) * 100; if this is 30%, then the average optimized page takes 30% of the time that the average passthrough page takes.
The data elements described above are represented in an SNMP Management Information Base (MIB). The MIB is available at: $AVS_HOME/console/jboss-3.0.1_tomcat-4.0.4/server/default/deploy/fgconsole.war/FgnAppScopeStatsAggregatorMib.txt. It is also available through the Management Console at this URL: http://consoleIPAddress:consolePort/fgconsole/FgnAppScopeStatsAggregatorMib.txt
The AppScope statistics MIB is organized as an SNMP table as follows:
•
•
For a detailed description of the AppScope statistics MIB, see "SNMP MIB."
SNMP Data Access
Any SNMP-compliant client application can query the AppScope SNMP agent, using the SNMP GET operation, to get the current AppScope statistics. Examples include:
•
•
•
Example Query with HP OpenView
Using the HP OpenView MIB Browser, you can navigate the AppScope MIB, select the data element of interest, and click Start Query to get the value(s). For example:
Notice that there are two values shown:
•
•
As mentioned above, the MIB indexes correspond to the defined Transaction Group IDs. To view the value for these indexes, you can do another query, this time on the transactionGroupName element:
Example Graph with HP OpenView
In the OpenView MIB Browser, you can click on a data element/index, and click Graph to graph the data. Here is an example graph:
Thresholds and Alerts
The AppScope SNMP agent does not directly support SNMP traps, or defining and checking thresholds for the data that it collects. Instead, users can use an external program to poll the AppScope agent, check the data against thresholds, and take some action if the threshold is crossed.
Examples of this type of event management are:
•
•
