Table Of Contents
Reporting
Retrieving Data
Viewing the Contents of the Reporting Database
Retrieving Data from a Device
Viewing Scheduled Data Retrieval Tasks
Adding Scheduled Data Retrieval Tasks
Activating Scheduled Data Retrieval Tasks
Deactivating Scheduled Data Retrieval Tasks
Deleting Scheduled Data Retrieval Tasks
Data Retrieval from Archive
Enabling and Disabling Data Archiving
Retrieving Data from Archive
Understanding Report Groups
Monitoring Reports Overview
Report Granularity
Report Metrics
Report Instance Properties
Global Monitoring Reports
User Monitoring Reports
Policy Monitoring Reports
Traffic Discovery Reports
Traffic Discovery Report Order Property
Demographic Data and Class Popularity Reports
Web and Streaming Reports
Mail and News Reports
P2P Reports
VoIP Reports
Citrix Reports
IM Reports
SAP Reports
MS-SQL Reports
ActiveX Reports
MS Exchange Reports
Oracle Reports
Managing Report Instances
Creating a Report Instance
Modifying an Existing Report Instance
Deleting a Report Instance
Managing Reports
Viewing Completed Reports and Reports in Progress
Viewing Report Results
Deleting Reports in Progress
Reporting
This module explains the methods by which the operator of the Application Performance Assurance Device Console (APADC) defines the data retrieval parameters, as well as the means of converting this data into usable reports from the Network Module Enhanced Application Performance Assurance (NME-APA).
•
Retrieving Data
•Understanding Report Groups
•Managing Report Instances
•Managing Reports
Retrieving Data
The APADC builds reports from the traffic monitoring data that is retrieved from the NME-APA devices. The retrieved monitoring data is stored in a relational database and the APADC report generators query this database to create reports when requested by the user.
The APADC stores only 24-hours of data from a device in the database due to size and performance considerations. There are three ways to populate this database:
1. Use the "Retrieve Now" operation—This operation retrieves the most recent monitoring data (up to 24-hours) from the connected NME-APA device and places it in the database. The user initiates the operation by clicking a button in the APADC user interface.
2. Create a scheduled data retrieval task—A data retrieval task retrieves the most recent monitoring data (up to 24-hours) from a specified NME-APA device at a scheduled time. This feature is convenient if, for example, you would like to see the same type of report at the same time on a daily basis. In this case, you might schedule a retrieval task for 8:00 AM so that you can generate a report of the previous day's activity for viewing when you arrive at the office at 9:00 AM. There can be at most one data retrieval task defined in APADC at a time. The APADC user can also perform a "Retrieve Now" operation at any time for a device that has an active data retrieval task.
3. Retrieve data from the APADC's data archive—The database can hold only 24-hours of data; however, a user may want to view traffic behavior over longer periods; for example, a comparison between the current data and the previous week's data can provide valuable insights into network traffic utilization. The APADC can accommodate this type of analysis through its data archive.The APADC can archive up to 30 days of data for each managed NME-APA device. The user selects the timespan (up to 24-hours in length) in the archived data and specifies that this data be placed in the database. By repeating this process for different periods of time and for different devices, the user can gain an understanding of traffic behavior across the network over many days.
Note that each of these operations completely replaces the contents of the database and that the database can hold only 24-hours of data for one device. Note also that the time required to retrieve data from a device or the data archive varies depending on the amount of data that has been collected over the time span requested. Retrieval times can be lengthy if detailed traffic RDRs have been configured.
•Viewing the Contents of the Reporting Database
•Retrieving Data from a Device
•Viewing Scheduled Data Retrieval Tasks
•Adding Scheduled Data Retrieval Tasks
•Activating Scheduled Data Retrieval Tasks
•Deactivating Scheduled Data Retrieval Tasks
•Deleting Scheduled Data Retrieval Tasks
•Data Retrieval from Archive
Viewing the Contents of the Reporting Database
Step 1 In the Navigation pane, select Reporting > Data Retrieval.
The Data Retrieval screen appears in the Configuration pane, displaying the Last Retrieval information in the top portion. This shows which device has data in the reporting database, and the time the data was collected.
Figure 5-1
Retrieving Data from a Device
Step 1 In the Navigation pane, select Reporting > Data Retrieval.
The Data Retrieval screen appears in the Configuration pane.
Step 2 To retrieve data immediately, click Retrieve Data Now.
Note You must be connected to a device to retrieve data.
Viewing Scheduled Data Retrieval Tasks
Step 1 In the Navigation pane, select Reporting > Data Retrieval.
The Data Retrieval screen appears in the Configuration pane, displaying the Data Retrieval Tasks box in the lower portion.
Figure 5-2
Adding Scheduled Data Retrieval Tasks
Step 1 In the Navigation pane, select Reporting > Data Retrieval.
The Data Retrieval screen appears in the Configuration pane displaying the Data Retrieval Tasks box in the lower portion.
Step 2 Click Add.
The Add RDR Task window appears.
Figure 5-3
Step 3 In the Task Name field, enter a meaningful name for the task.
Step 4 From the Device drop-down list, choose the device from which you want to retrieve data.
Step 5 Click the Calendar to select a start date.
Note The Start Date field is disabled, forcing the user to select the date with the Calendar.
Step 6 In the Start Time fields, enter the hour and minute at which you want the task to begin.
Step 7 In the Repeat Every field, enter the interval between retrievals in hours and minutes.
Step 8 In the End After field, enter the number of times you want the retrieval task to occur.
Step 9 Click OK.
The Data Retrieval screen reappears with the new Data Retrieval Task listed.
Figure 5-4
Activating Scheduled Data Retrieval Tasks
Step 1 In the Navigation pane, select Reporting > Data Retrieval.
The Data Retrieval screen appears in the Configuration pane displaying the Data Retrieval Tasks box in the lower portion.
Step 2 Click the radio button next to the Retrieval Task that you want to activate.
The Status field indicates the following:
•Active—Task runs according to its time parameters.
•Inactive—Task does not run until it is activated.
Step 3 Click Activate.
The Data Retrieval Task shows Active in its Status field and runs according to its time parameters.
Figure 5-5
Deactivating Scheduled Data Retrieval Tasks
Step 1 In the Navigation pane, select Reporting > Data Retrieval.
The Data Retrieval screen appears in the Configuration pane displaying the Data Retrieval Tasks box in the lower portion.
Step 2 Click the radio button next to the Retrieval Task that you want to deactivate.
The Status field indicates the following:
•Active—Task runs according to its time parameters.
•Inactive—Task does not run until it is activated.
Step 3 Click Deactivate.
The Data Retrieval Task shows Inactive in its Status field and does not run until it is activated.
Figure 5-6
Deleting Scheduled Data Retrieval Tasks
Step 1 In the Navigation pane, select Reporting > Data Retrieval.
The Data Retrieval screen appears in the Configuration pane, displaying the Data Retrieval Tasks box in the lower portion.
Step 2 Click the radio button next to the Retrieval Task you want to delete.
Step 3 Click Delete.
The Retrieval Task is removed from the list.
Data Retrieval from Archive
When data archiving is enabled for a device, the APADC creates an internal task which retrieves all new RDR files from the device every 30 minutes. The NME-APA device creates a new RDR file every 30 minutes, so one file is retrieved on average when the internal task runs. The initial execution of this task may retrieve many files if they have not been previously uploaded to APADC.
The NME-APA device keeps only the last 24-hours of RDR files in its file system. Files older than 24-hours are automatically purged from the device.
The APADC keeps up to 30 days of retrieved RDR files for a device. Files older than 30 days are automatically deleted from the APADC server file system.
You can perform the following tasks:
•Enabling and Disabling Data Archiving
•Retrieving Data from Archive
Enabling and Disabling Data Archiving
Step 1 In the Navigation pane, select Reporting > Data Retrieval > Retrieval from Archive.
The Retrieval from Archive screen appears in the Configuration pane.
Figure 5-7
Step 2 Click Change Archive Settings.
The Configure Archiving dialog appears displaying the Enable/Disable Archiving form. The Configure Archiving dialog lists all of the NME-APA devices known to the APADC.
Figure 5-8
Step 3 To enable archiving of data for a device, check the Enable/Disable checkbox for that device. To disable archiving, uncheck the Enable/Disable checkbox for that device.
Note The checkbox for a device is disabled if there is an active Data Retrieval Task for the device, or if the user is currently performing a Retrieve Now operation for the device. In both cases, the archive for the device is automatically updated by the operation, so it is not possible to enable or disable archiving.
Step 4 Click OK.
The archiving changes take effect.
If you refresh the Retrieval from Archive page, the names of the enabled devices appear immediately above the Change Archive Settings button.
Retrieving Data from Archive
Step 1 In the Navigation pane, select Reporting > Data Retrieval > Retrieval from Archive.
The Retrieval from Archive screen appears in the Configuration pane. The screen shows the archived time intervals for each device that has archiving enabled. Discontinuous time ranges appear if no RDR data was generated on the device over one or more half-hour intervals.
Step 2 Click the radio button next to the desired device.
Step 3 Click Retrieve.
The Retrieve Data from Archive screen appears in the Configuration pane.
Figure 5-9
Step 4 From the Available Time Range(s) drop-down list, choose a time range.
Step 5 In the Start Date field, choose the start date of the retrieved data.
Step 6 In the Start Time fields, enter the start time (hours and minutes) of the retrieved data.
These fields are automatically set to the start date and time of the selected time range. You may change the date and time, but you must choose a value that is within the selected time range.
Step 7 In the Duration fields, enter the duration of the retrieved data.
The duration must be in 30 minute increments. You must enter a duration such that when it is added to the start date and time it does not exceed the end of the selected time range. Also, the time range cannot exceed 24 hours.
Step 8 Click OK.
Data is retrieved from the archive for the specified time range and is written into the reporting database. Any previous data in the reporting database is first deleted.
Note Retrieval from archive can be time-consuming if a large time range is specified.
Upon completion of the archive retrieval, the Retrieval from Archive screen appears in the Configuration pane. The retrieved time range is shown under the Current Data in DB heading.
Understanding Report Groups
The APA Device Console includes report groups that you use to generate report instances. The groups are organized according to common themes. Each report group allows you to create new report instances. Default filter values are assigned to the properties, some of which are common to all the instances in a given group. You can impose additional constraints by configuring the properties.
You generate a report instance by selecting a report group from the list of available groups in the Groups view.
There are two main categories of reports:
•Monitoring reports—Show how network resources are used for selected classes at various granularities (global, policy, user)
•Traffic Discovery reports—Provide statistical information about network activity and help identify the characteristics of the traffic traversing the network
Monitoring Reports Overview
Monitoring reports provide information about the distribution and consumption of network resources. This information helps you understand how the network is used at different granularities (such as for the entire link, for traffic generated by all users in a particular policy usage counter, or for traffic generated by a particular user). These reports are critical for tuning the Class Control solution's configuration according to changing network patterns.
Monitoring reports are created from Link Usage, Policy Usage, and Real-Time User Usage Raw Data Records (RDRs). These RDRs (that are generated by the NME-APA platform) provide periodic usage information (at the various granularities) that is processed according to the selected report group to provide the final report.
Monitoring reports typically show a specific metric for a set of class usage counters at a selected granularity, such as bandwidth for P2P and Browsing class usage counters at a link granularity, or volume for the Streaming class usage counter for users in the Gold policy usage counter.
You select the class usage counters on which to report via the APA Device Console. The available class usage counters are those defined in the class configuration of the NME-APA platform from which the reports are generated.
•Report Granularity
•Report Metrics
Report Granularity
A report instance's granularity controls which traffic the generated report addresses. Two granularities are supported:
•Global—Provides visibility into all traffic processed by the NME-APA platforms being reported on. Use global granularity to view the global distribution of network resources (for example, total P2P bandwidth for the last 24 hours).
•User—Provides insight into the activity of a single user defined in the Class Control solution. Use user granularity to view how a particular user is using network resources (for example, the number of P2P sessions generated by a particular user for each hour during the last 12 hours). User reports are available for those users flagged for real-time reporting. See Configuring Real-Time User RDRs, page 3-33 and the "Editing Users" section on page 4-3.
Each report group generates reports in a specific granularity. Each type of report is accessible from the corresponding report group.
Report Metrics
A metric is the statistic being reported on. The following metrics are available:
•Bandwidth—The total bandwidth consumed by the selected classes. By default, a bandwidth report is displayed as a stacked-area chart, where each area indicates the bandwidth used by a particular class.
When generating a bandwidth report, you can select the direction: upstream, downstream, or both.
You can also display an hourly average of bandwidth. This is recommended when you are generating a report for many hours. In this case a single data point per hour is usually sufficient: it reduces the quantity of data displayed, improving performance and the visualization of the data.
•Volume—The total volume (in kilobytes or megabytes) for a specific period of time, for the selected class usage counters. As opposed to the bandwidth metric, which provides normalized volume over time, volume reports give the total volume consumed, grouped by specific time durations. By default, a volume report is displayed as a stacked-bar chart, where each bar/series indicates the volume of a particular class usage counter.
Volume reports give the accumulated usage either for specific durations of time (hours or days), or for the entire duration of the report. For example: a Global Hourly Usage Volume report displays a bar that accounts for the total volume consumed by each class usage counter during each hour of the selected time frame, and a Global Aggregated Usage Volume per Class report accounts for all volume of each class usage counter for the entire time frame of the report.
•Sessions—The number of sessions. A session is a single network transaction (for example, RTSP stream or P2P file download). By default, a sessions report is displayed as a stacked-bar chart, where each bar/series indicates the total number of sessions of a particular class usage counter.
Like volume reports, sessions reports can be grouped into specific durations (hours or days), in order to account for the total number of sessions in a particular hour/day consumed by a particular class usage counter.
Report Instance Properties
Table 5-1 lists properties that appear in report groups that belong to more than one group group. (Properties of report instances that belong to only one group are listed with the description of the group.)
Table 5-1 Common Properties of Report Instances
Property
|
Field Type
|
Default
|
Comments
|
Items to Focus on
|
One of the following is included in most report groups:
|
—
|
—
|
—
|
Classes to view
|
Multiple Choice
|
(not set)
|
When not set, all classes are selected.
|
Select classes to view
|
Multiple Choice
|
(not set)
|
When not set, all classes are selected.
|
Focus on the class
|
Single Choice
|
(not set)
|
When not set, all classes are selected.
|
One of the following is included in many report groups:
|
—
|
—
|
—
|
Policy
|
Single Choice
|
(not set)
|
Mandatory property.
|
Name of user to focus on
|
Free Text
|
(not set)
|
Mandatory property for User group group report instances.
IP address (decimal format) or user name.
|
Time Boundaries —See note following table.
|
Starting after date
|
Time/Date
|
(not set)
|
—
|
Ending before date
|
Time/Date
|
(not set)
|
When not set, the report is bound to the current time.
|
From the last number of hours
|
Free Text
|
24
|
Table D-2 Ignored when the Starting After Date and Ending Before Date properties are both set.
|
From the last number of Days
|
Free Text
|
7
|
—
|
Specific Time
|
Date/Time
|
(not set)
|
Mandatory property.
Appears in three report instance types instead of the other three time boundary properties.
The selected time is rounded to the nearest hour/day.
|
Traffic Parameters
|
Link to Focus
|
Multiple Choice
|
(not set)
|
List of available links to focus.
|
One of the following is included in many report groups:
|
—
|
—
|
—
|
Traffic Direction
|
Single Choice
|
Depends on report group
|
Depends on report group:
•Direction only
•Direction and metric
|
Metric to order
|
Single Choice
|
Depends on report group
|
Depends on report group and metric:
•Metric only
•Metric and direction
|
Data Show
|
Pick BW Over
|
Single Choice
|
1 Hour
|
—
|
NME-APA IP to view
|
Single Choice
|
At installation: (not set)
Thereafter: most recent assigned value
|
Mandatory property.
IP address of specific NME-APA device.
|
Units of results
|
Single Choice
|
Depends on report group
|
—
|
Limit number of results
|
Free Text
|
10
|
—
|
Average Data by Hour
|
Boolean
|
TRUE
|
If this option is selected, a single, average value is calculated for each hour of the report. This option is recommended when generating the report for 24 or more hours.
|
Show other Consumption
|
Boolean
|
FALSE
|
—
|
Aggregation Period
|
Single Choice
|
Hourly
|
—
|
User Id
|
Free Text
|
(not set)
|
Pattern that represent group of users.
|
•All report instances include the NME-APA IP to view property, which enables filtering to a specific NME-APA platform. This property is mandatory and persistent. Persistent means that the current value is used for all subsequent reports until the value is changed.
•Time Boundaries properties occur in all report instances except for Top Users, Top Talkers, and Relative Consumption of Top Users. These properties are:
–Starting After Date
–Ending Before Date
–From the Last Number of Hours/Days
The property From the last number of hours/days is set to a default value in all report instances. When all three Time Boundaries properties are set, the From the last number of hours/days property is ignored. When the property Ending before date is not set, the report is bound to the current time.
Global Monitoring Reports
The Global Monitoring group of reports allows you to view statistics about the traffic bandwidth or volume that was consumed. The bandwidth and volume consumption can be displayed per class for the entire link.
The Global Monitoring group includes the following reports:
•Global Aggregated Usage Volume per Class—Shows the total volume of traffic (upstream and downstream) for each class usage counter (for all traffic, regardless of user or policy)
•Global Bandwidth per Class—Shows the distribution of bandwidth among the different classes defined in the system for all traffic, regardless of user or policy
•Global Concurrent Session per Class—Shows the distribution of concurrent sessions among the different class usage counters defined in the system
•Global Hourly Aggregated Minutes per Class—Shows the total number of minutes used for each class usage counter defined in the system, grouped by hour
•Global Hourly Usage Sessions per Class—Shows the distribution of sessions among the different class usage counters defined in the system, grouped by hour
•Global Hourly Usage Volume per Class—Shows the distribution of volume among the different class usage counters defined in the system, grouped by hour
User Monitoring Reports
The User Monitoring group of reports allows you to view statistics about the bandwidth or volume of traffic used by the user. The reports are provided per class usage counter for the total volume consumed by the user. A Top Users report identifies the users that consume the largest traffic volume. User bandwidth and volume reports can be generated for those users configured for real-time monitoring. See the "Editing Users" section on page 4-3 for a description of how to configure real-time users.
The User Monitoring group includes the following reports:
•Top Users—Shows a list of the top user volume consumption in a specific hour/day
•User Aggregated Usage Volume per Class—Shows the most popular class usage counter for a particular user
•User Bandwidth per Class—Shows the distribution of bandwidth among the different class usage counters defined in the system for a particular user
•User Hourly Aggregated Minutes per Class—Shows the total number of minutes used for each class usage counter for a specific policy usage counter defined in the system, grouped by hour
•User Hourly Usage Sessions per Class—Shows the hourly distribution of sessions among the different class usage counters defined in the system for a particular user
•User Hourly Usage Volume per Class—Shows the hourly distribution of volume among the different class usage counters defined in the system for a particular user
Policy Monitoring Reports
The Policy Monitoring group of reports allows you to view statistics about the bandwidth or volume of traffic used by the user. The bandwidth and volume consumption are displayed per policy.
The Policy Monitoring group includes the following reports:
•Policy Aggregated Usage Volume per Class—Shows the total volume of traffic (upstream and downstream) for each class usage counter for a specific policy
•Policy Bandwidth per Class—Shows the distribution of bandwidth among the different classes defined in the system for all traffic for a specific policy
•Policy Concurrent Sessions per Class—Shows the distribution of concurrent sessions among the difference class usage counters for a specific policy
•Policy Hourly Aggregated Minutes per Class—Shows the total number of minutes used for each class usage counter defined in the system, grouped by hour for a specific policy
•Policy Hourly Usage Sessions per Class—Shows the distribution of sessions among the different class usage counters defined in the system, grouped by hour for a specific policy
•Policy Hourly Usage Volume per Class—Shows the distribution of volume among the different class usage counters defined in the system, grouped by hour for a specific policy
Traffic Discovery Reports
The Traffic Discovery group of reports allows you to view statistics compiled from the source and destination IP addresses and ports of the system traffic. They are useful for obtaining information about the general activity in the IP network, and they are the key for defining the system's class configuration.
Traffic discovery reports are based on the information in Transaction RDRs.
Traffic discovery reports generate histograms and distribution charts that are grouped by a selected criterion and sorted by the selected order parameter. For example, a Top Protocols report is sorted by total volume.
Table 5-2 Property of Traffic Discovery Reports only
Property
|
Field Type
|
Default
|
Comments
|
Items to Focus on
|
—
|
—
|
—
|
Group remaining clients into single value
|
Boolean
|
False
|
When set to true, the number you select for the parameter 'Limit Number of Results to*', determines how many users have a separate usage bar in the report: the remaining client's usage is represented as a single bar.
A special IP address '0.0.0.0' is used to represent the 'remaining other clients'.
|
Note The reports in this group are not per user; they supply general port and IP address information.
The Traffic Discovery - Statistics group includes the following reports:
•Top IP Protocols—Shows the most popular IP protocol for certain classes
•Top Client IP to Server Port—Shows the most popular client IP to server port for certain classes
•Top Server IP to Server Port—Shows the most popular server IP to server port for certain classes
•Top Client IP to Server IP and Server Port—Shows the most popular server IP and server port for certain classes.
•Top Clients—Shows the most popular client IP for certain classes
Note Client refers to the IP address of the flow initiator. It may be located on the user side or on the network side.
•Top Servers—Shows the most popular servers for certain classes
Note Server refers to the IP address of the other side of the flow initiator. It may be located on the Upstream Volume.
•Top Protocols—Shows the most popular protocol for certain classes
•Top Class Ports—Shows the most popular server ports of a certain class or classes
•Top Client IP to Server IP—Shows the most popular client IP to server IP for certain classes
•Top Server Ports—Shows the most popular server ports for certain classes
Traffic Discovery Report Order Property
The metric to order property indicates the value by which the report is sorted. Possible values are:
•Upstream Volume
•Downstream Volume
•Both Directions Volume—Total upstream and downstream volume
•Hit-Count—Number of transactions
You can limit each report to a specific number of results, which allows you to focus on the top areas of activity (according to the selected value).
Demographic Data and Class Popularity Reports
The Demographic Data and Class Popularity group of report groups allows you to view statistics of the demographic data.
The Demographic Data and Class Popularity group includes the following reports:
•Class Popularity among Users—Shows the percentage of users using a specific class defined in the system
•Relative Consumption of Top Users—Shows the relative consumption of a specific number of users compared to "other"
•Global Active User per Class—Shows the distribution of users among the different classes defined in the system for all traffic, regardless of user or policy
•Class Popularity among Users (Average)—Shows the total number of users using a specific class compared to users using all other classes
•Policy Active User per Class—Shows the distribution of bandwidth among the different classes defined in the system for specific user policy
•Class Popularity among Users of a Specific Policy—Shows the percentage of users defined in the system for a specific user policy using a specific class defined in the system
•Class Popularity among Users of a Specific Policy (Average)—Shows the total number of users defined in the system for a specific user policy using a specific class defined in the system
Web and Streaming Reports
The Web and Streaming group of reports allows you to compile statistics presenting the most popular servers or hosts for the various predefined system classes (such as Browsing, Streaming, and Downloading) and for user-defined classes.
These reports cannot be generated using data collected from an NME-APA platform running in asymmetric routing classification mode.
Table 5-3 Property of Web and Streaming Group Reports only
Property
|
Field Type
|
Default
|
Comments
|
Items to Focus on
|
—
|
—
|
—
|
Where host contains
|
Free Text
|
(not set)
|
Filter to hosts containing the given pattern.
|
The Web and Streaming group includes the following reports:
•Top FTP Servers—Shows the most popular FTP file hosts
•Top Class Servers—Shows the most popular servers of a certain class or classes
•Top Rtsp Hosts—Shows the most popular real-time streaming protocol (RTSP) servers
•Top Web Hosts—Shows the most popular web servers
•Top MMS Servers—Shows the most popular MMS hosts
Mail and News Reports
The Mail and News group of reports allows you to view statistics of the mail and news traffic.
These reports cannot be generated using data collected from an NME-APA platform running in asymmetric routing classification mode.
The Mail and News group includes the following reports:
•Top Email Account Owners—Shows the top e-mail account owners
•Top NNTP Consumers—Shows the top NNTP consumers
•Top Newsgroups—Shows the most popular newsgroups
•Top NNTP Servers—Shows the most popular NNTP hosts
•Top SMTP Servers—Shows the most popular SMTP hosts
•Top Email Recipients—Shows the top e-mail recipients
•Top POP3 Servers—Shows the most popular POP3 hosts
•Top User to Newsgroups—Shows the top user to newsgroups for certain classes
•Top Email Sender—Shows the top e-mail sender
P2P Reports
The P2P group of reports allows you to view statistics of the P2P traffic.
These reports cannot be generated using data collected from an NME-APA platform running in asymmetric routing classification mode.
The P2P group includes the following reports:
•Top P2P Uploaders—Shows the most popular P2P upload consumers
•Top P2P Consumers—Shows a list of the top P2P user volume consumption
•Top P2P Protocols—Shows the most popular P2P protocol for certain classes
•Top P2P Downloaders—Shows the top P2P download consumers
VoIP Reports
The VoIP group of reports allows you to view statistics of the VoIP traffic.
These reports cannot be generated using data collected from an NME-APA platform running in asymmetric routing classification mode.
Table 5-4 Property of VoIP Group Groups only
Property
|
Field Type
|
Default
|
Comments
|
Data Show
|
—
|
—
|
—
|
Codec to filter
|
Multiple Choice
|
(not set)
|
—
|
The VoIP group includes the following reports:
•Global Hourly Call Minutes per Class—Shows the distribution of call minutes among the different VoIP class usage counters defined in the system, grouped by day
•User Bandwidth per VoIP Class—Shows the distribution of bandwidth among the different VoIP classes defined in the system for the traffic of users in a specific policy
•Global VoIP Codec Distribution
•Global VoIP Packets Loss
•Top SIP Domains—Shows the most popular SIP Domains
•Global VoIP MOS Distribution
•Policy Hourly Call Minutes per Class—Shows the distribution of call minutes among the different VoIP class usage counters defined in the system, grouped by day
•Global Hourly Average VoIP MOS
•User Hourly Call Minutes per Class—Shows the distribution of call minutes among the different VoIP class usage counters defined in the system, grouped by day
•Global Hourly Average VoIP Packets Loss
•Global VoIP MOS
•Global VoIP Jitter
•Top Talkers—Shows a list of the top talker volume, session, or minutes consumption in a specific hour or day for a specific VoIP class or for all VoIP classes
•Policy Bandwidth per VoIP Class—Shows the distribution of bandwidth among the different VoIP classes defined in the system for the traffic of users in a specific policy
•Policy Concurrent Calls per VoIP Class—Shows the distribution of concurrent sessions among the different VoIP class usage counters defined in the system, grouped by day
•Global Concurrent Calls per VoIP Class—Shows the distribution of concurrent sessions among the different VoIP class usage counters defined in the system, grouped by day
•Global Bandwidth per VoIP Class—Shows the distribution of bandwidth among the different VoIP classes defined in the system for all traffic, regardless of user or policy
•Global Hourly Average VoIP Jitter
Citrix Reports
The Citrix group includes the following reports:
•Global Bandwidth per Citrix Subprotocol
•Top Citrix Subprotocols
•User Bandwidth per Citrix Subprotocol
IM Reports
The IM group includes the following reports:
•Global Bandwidth per IM Type
•IM Top Users per Message Type
•User Bandwidth per IM Type
SAP Reports
The SAP group includes the following reports:
•TOP SAP Servers
•SAP User Bandwidth
•SAP Global Bandwidth
MS-SQL Reports
The MS-SQL group includes the following reports:
•MS-SQL Global Bandwidth
•MS-SQL User Bandwidth
•MS-SQL Top Users
ActiveX Reports
The ActiveX group includes the following reports:
•ActiveX Top Users
•ActiveX Global Bandwidth
•ActiveX User Bandwidth
MS Exchange Reports
The Exchange group includes the following reports:
•MS Exchange Top Users
•MS Exchange Global Bandwidth
•MS Exchange User Bandwidth
Oracle Reports
The Oracle group includes the following reports:
•Top Oracle Servers
•Oracle Global Bandwidth
•Oracle User Bandwidth
Managing Report Instances
•Creating a Report Instance
•Modifying an Existing Report Instance
•Deleting a Report Instance
Creating a Report Instance
Step 1 In the Navigation pane, select Reporting > Running Reports.
The Reports screen appears in the Configuration pane displaying the list of all reports.
Step 2 To filter reports alphabetically, from the Show All drop-down list choose an alphabetical range.
Note You can also go directly to your desired group of reports by selecting one of the child nodes under Running Reports in the Navigation pane.
Step 3 From the list, click the type of report which you would like to use to create a report instance.
The list of associated report instances appears.
Figure 5-10
Step 4 Click Create Instance.
The Modify Report Instance screen appears in the Configuration pane.
Figure 5-11
Step 5 Modify the report instance parameters to produce the desired report.
Step 6 Click Save.
The report instance is saved and can be viewed on the Running Reports screen.
Modifying an Existing Report Instance
Step 1 In the Navigation pane, select Reporting > Running Reports.
The Reports screen appears in the Configuration pane, displaying the list of all reports.
Step 2 To filter reports alphabetically, from the Show All drop-down list choose an alphabetical range.
Note You can also go directly to your desired group of reports by selecting one of the child nodes under Running Reports in the Navigation pane.
Step 3 From the list, choose the type of report for which you want to modify a report instance.
The list of associated report instances appears.
Step 4 Click on the report instance you want to modify.
The Modify Report Instance screen appears in the Configuration pane.
Figure 5-12
Step 5 Modify the report instance parameters to produce the desired report.
Changing the name of the report instance renames the report instance.
Step 6 Click Save.
The report instance is saved and can be viewed on the Running Reports screen.
Deleting a Report Instance
Step 1 In the Navigation pane, select Reporting > Running Reports.
The Reports screen appears in the Configuration pane, displaying the list of all Reports.
Step 2 To filter reports alphabetically, from the Show All drop-down list choose an alphabetical range.
Note You can also go directly to your desired group of reports by selecting one of the child nodes under Running Reports in the Navigation pane.
Step 3 From the list, choose the type of report for which you want to delete a report instance.
The list of associated report instances appears.
Step 4 Click the check boxes next to the report instance or instances that you want to delete.
Step 5 Click Delete Instance(s).
The report instance or instances are deleted from the list.
Managing Reports
•Viewing Completed Reports and Reports in Progress
•Deleting Reports in Progress
•Viewing Report Results
Viewing Completed Reports and Reports in Progress
Step 1 In the Navigation pane, select Reporting > Running Reports.
The Reports screen appears in the Configuration pane displaying the list of all reports.
Step 2 Click the Current Reports tab.
The Running Reports screen appears listing all reports that are running and those that have completed.
Figure 5-13
To set the frequency for refreshing the list of reports, from the Auto-Refresh drop-down list choose the desired frequency.
Viewing Report Results
Step 1 In the Navigation pane, select Reporting > Running Reports.
The Reports screen appears in the Configuration pane displaying the list of all reports.
Step 2 Click the Current Reports tab.
The Running Reports screen appears listing all reports that are running and those that have completed.
Step 3 Click on the report that you want to view.
The Report Result window appears with the results of the report displayed.
Note If the file is a .jpg, you can save it using your browser's Save Picture function. If the file is a .csv, you can right-click on the provided link and choose "Save As".
Deleting Reports in Progress
Step 1 In the Navigation pane, select Reporting > Running Reports.
The Reports screen appears in the Configuration pane displaying the list of all reports.
Step 2 Click the Current Reports tab.
The Running Reports screen appears listing all reports that are running and those that have completed.
Step 3 Check the check boxes next to the report or reports that you want to delete.
Step 4 Click Delete.
The report is removed from the list.
