|
|
This chapter provides an explanation of collection tasks and reports categorized under the Monitoring menu option, as follows:
Figure 8-1, "Monitoring Menu," provides a view of the Monitoring menu in the menu task bar.
This section contains the following categories:
Accounting data is collected to provide end-to-end usage information on VPN-based network traffic and to provide a complete billing solution. Collected accounting data is used by the Accounting Server for various levels of aggregation for accounting reports and API accounting information.
Prior to collecting VPN Accounting data, implement the following sections:
Prior to collecting VPN Accounting data, implement the following steps for each and every PE router, to determine whether SNMP is enabled. If SNMP is enabled, these steps will lead you to the first GUI path. If SNMP is not enabled, these steps will direct you on how to enable SNMP.
Step 2 Go into the enable state.
Step 3 Enter the command show snmp.
Step 4 Determine whether the following line is present:
% SNMP agent not enabled
Step 5 If the line in Step 4 is not present, you have determined that SNMP is enabled. Then enter the show run command to view the SNMP community strings at the end of the configuration file. If you have more routers to verify, return to Step 1 and follow these steps for the next router that you want to verify. Otherwise, proceed to the "NetFlow Settings on the Router" section.
If the line in Step 4 is present, proceed to Step 6.
Step 6 To turn on SNMP, at the prompt, enter the command config t.
Step 7 Enter the following commands:
snmp-server community <userstring> RO
snmp-server community <userstring> RW
If you have more routers to verify, return to Step 1 and follow these steps for the next router that you want to verify.
 |
Note These SNMP strings must agree with those listed in the target password database for each router. (Refer to Chapter 3 in the Cisco VPN Solutions Center: MPLS Solution User Guide.) |
NetFlow Collector must be running.
ip flow-export version 5
ip flow-export destination <ipaddress> <port>
|
Note The VERSION and PORT parameters must coincide with the settings configured in the NetFlow Collector. |
Step 2 Activate the CE-facing MAJOR Interface, as follows:
ip route-cache flow
Step 3 To see current flows in the router flow-cache, issue the following command:
show ip cache flow
NetFlow Collector uses a pre-allocated cache, which by default has 64K entries where each flow (uni-directional) gets one entry. Each entry uses 68 bytes. The number of NetFlow Collector entries can be expanded if traffic requirements and machine resources warrant, as follows:
ip flow-cache entries <#>
Implement the following steps:
#Set format to Comma Separated for VPNSC:
CSV_FORMAT YES
#Use long file names with dates:
LONG_OUTPUTFILE_SUFFIX yes
Step 2 On the NetFlow Collector device, edit the nfconfig.file file as follows:
#Use the Detail Call Record aggregation scheme for VPNSC:
Thread DETCALLREC
Aggregation DetailCallRecord
Period 30
Port 9996
State Active
DataSetPath /opt/CSCOnfc/Data
Binary Yes
Compression No
Max Usage
|
Note Failure to do this results in blank VPN accounting reports. |
To collect VPN accounting data, implement the following steps:
|
Note An alternative to selecting Monitoring > Collect VPN Accounting Data is to select Tools > Tasks and then in the Actions menu item select New Task > Collect VPN Accounting Data and click Ok. Both paths navigate to the same wizard. |
The resulting window is shown in Figure 8-3, "Collect VPN Accounting DataIntro." Be sure to read the recommended scheduling frequency.
Step 2 Click Next to continue.
The next window, as shown in Figure 8-4, "Selecting Devices for Accounting Collection," allows you to specify the NetFlow Collector from which to collect accounting information.
Step 3 In the window in Figure 8-4, "Selecting Devices for Accounting Collection," first click the Network drop-down menu to choose a specific network.
This window has two panels with the column headings Network, Name, Domain, and Role. The upper panel includes all the targets selected in this step. The lower panel will be populated to include all the targets that you choose in Step 4 and Step 5, that is, all the collectors.
In the upper panel, you can sort the collectors on each of the column headings, Network, Name, Domain, and Role. Just click that column header to sort on it.
Step 4 This step explains how to move devices to the lower panel, thus selecting the NetFlow Collector hosts (indicated as Net Flow in the Role column) from which accounting data will be collected.
If you do not select any devices in the upper panel, you can select Add All and all the devices appear in the lower panel. If you select one or more devices, you can click Add and only those devices appear in the lower panel.
|
Note For traffic to be properly mapped across the VPN network, all NetFlow collectors must be collected from in a single task. |
Step 5 If you decide not to choose the devices now listed in the lower panel, you can either select Remove All to eliminate all the selections in the lower panel, or you can select those devices that you want to eliminate and click Remove.
You can continue editing the set of devices in the lower panel by repeating Step 4 and Step 5.
Step 6 Click Next, when you want to choose the devices that appear in the lower block as the collectors for which accounting data will be collected.
Step 7 In the next window, as shown in Figure 8-5, "Providing a Task Name for Collection of Accounting Data," provide a unique Task Name. Then click Next.
Step 8 In the next window, you can choose to schedule the task by selecting Yes and clicking Next. In this case the next step is Step 9.
You can choose not to schedule the task by selecting No and clicking Next. In this case, the next step is Step 10.
Step 9 If you chose to schedule the task, in the next window, choose the scheduling directions and click Next. See Chapter 11, "Scheduling," for a full detailed description of scheduling.
Step 10 If you did not schedule the task, you are informed that "The task manager is about to save the task." If you did schedule the task, you are informed that "The task manager is about to save and schedule the task." If you want to change your mind on the scheduling instructions, click Back and return to Step 8 or Step 9. When you are ready to save and schedule the task, click Next.
Step 11 You are informed that "All steps are done." Click Close to close the wizard.
|
Note Now that you have collected data for accounting, you can view this data as directed in the "View Accounting Reports" section. |
This section contains the following categories:
The SLA server collects the relevant performance data, stores it persistently, aggregates it, and presents useful reports (see the "View SLA Reports" section). The SLA server is based on the SA Agent MIB. The MPLS VPN Solution software leverages the SA Agent MIB to monitor SLA performance on a 24 x 7 basis. Using the MIB, you can monitor network traffic for the popular protocols: Dynamic Host Configuration Protocol (DHCP), Domain Name System (DNS), Hyper text Transfer Protocol (HTTP), Internet Control Message Protocol Echo (ICMP Echo), Jitter (voice jitter), Transmission Control Protocol Connect (TCP Connect), and User Datagram Protocol Echo (UDP Echo).
Prior to provisioning SLA definitions and collecting SLA data, implement the following sections:
Prior to collecting SA Agent data for SLA, implement the following steps for each and every router, to determine whether SNMP is enabled. If SNMP is enabled, these steps will lead you to the first GUI path. If SNMP is not enabled, these steps will direct you on how to enable SNMP.
Step 2 Go into the enable state.
Step 3 Enter the command show snmp.
Step 4 Determine whether the following line is present:
% SNMP agent not enabled
Step 5 If the line in Step 4 is not present, you have determined that SNMP is enabled. Then enter the show run command to view the SNMP community strings at the end of the configuration file. If you have more routers to verify, return to Step 1 and follow these steps for the next router that you want to verify. Otherwise, proceed to Step 8.
If the line in Step 4 is present, proceed to Step 6.
Step 6 To turn on SNMP, at the prompt, enter the command config t.
Step 7 Enter the following commands:
snmp-server community <userstring> RO
snmp-server community <userstring> RW
If you have more routers to verify, return to Step 1 and follow these steps for the next router that you want to verify.
Step 8 To provision a UDP Echo SLA, enter the following command on the router:
service udp-small-servers
Step 9 To provision a Jitter SLA, enter the following command on the router and the destination router:
rtr responder
|
Note These SNMP strings must agree with those listed in the target password database for each router. (Refer to Chapter 3 in the Cisco VPN Solutions Center: MPLS Solution User Guide.) |
To set up the Device Inventory repository, implement the following steps:
Step 2 Choose the target network by double-clicking on the network of your choice.
Step 3 From the resulting window, select SNMP-configured routers and click on Actions.
Step 4 Then choose either Edit Target or Edit Multiple. Choose the Passwords option and confirm that the router passwords and SNMP strings concur with what is configured on the routers.
Step 5 To populate the IP addresses into the Device Inventory repository, choose Tools > Tasks > Actions > New Task > Populate Interface Information for Cisco Router Targets and follow this wizard.
To set up the VPN repository, implement the following steps:
Step 2 Refer to Chapter 3 of the Cisco VPN Solutions Center: MPLS Solution User Guide for steps to confirm the CE's SA Agent status.
|
Note An alternative to selecting Monitoring > Provision SLA Definitions and Collect SLA Data is to select Tools > Tasks and then in the Actions menu item select New Task > Provision SLA Definitions and Collect SLA Data and click Ok. Both paths navigate to the same wizard. |
The first window informs you this wizard creates/deletes SLA definitions on SA Agent enabled routers and collects data for SLA monitoring.
Step 2 Click Next to continue.
The next window, as shown in Figure 8-7, "Selecting an SLA Operation," allows you to select one of the following options:
Step 3 After you make your selection, click Next to continue.
When you select Create SLA, you can create one or more SA Agent probes on one or more routers.
When you navigate from Monitoring > Provision SLA Definitions and Collect SLA Data and then choose Create SLA, you can then implement the following steps:
The next window, as shown in Figure 8-8, "Selecting CEs to Create SLAs," allows you to select one or more CEs.
Step 2 Click the VPN drop-down menu to choose a specific VPN associated with the Customer chosen in
Step 1.
The CEs for the chosen customer and VPN appear in the pane with the column headings CE Name, Network Name, and Domain Name.
Step 3 Select one or more CEs for which you want to create SLAs. Press the Ctrl key to highlight multiple CEs.
Step 4 Click Next to continue.
The next window is shown in Figure 8-9, "Selecting an IP Address for Each CE."
Step 5 For each CE click the drop-down menu to choose a specific source IP address for that CE.
Step 6 Click Next to continue.
The next window is shown in Figure 8-10, "Selecting Values for SLA Common Parameters."
Step 7 Enter the values for the common SLA parameters that are needed for each of the protocols.
The fields in Figure 8-10, "Selecting Values for SLA Common Parameters," are as follows:
.
| ToS Value | Binary Value | Meaning |
|---|---|---|
7 | 111 | In contract, best class |
6 | 110 | In contract, second best class |
5 | 101 | In contract, third best class |
4 | 100 | In contract, worst class |
3 | 011 | Out of contract, best class |
2 | 010 | Out of contract, second best class |
1 | 001 | Out of contract, third best class |
0 | 000 | Out of contract, worst class |
Step 8 Click Next to continue.
The next window is shown in Figure 8-11, "Selecting a Protocol and Protocol Specific Data."
Step 9 Select a protocol and enter the fields associated with it.
The protocols and the protocol-specific parameters are as follows:
Step 10 Press the Add button to the right of the top data field in Figure 8-17, "Selecting the DHCP Protocol and its Specific Data." Data will appear in the top data field based on all the parameters you specify.
Step 11 Create SLAs for other protocols by selecting other protocols, one at a time, completing the fields associated with the protocol, and pressing the Add button.
Step 12 If after you review the data in the top data field, you decide to eliminate an SLA or multiple sequential SLAs, highlight the SLA or press the Ctrl button and highlight multiple SLAs, and then click the Delete button to the right of the top data field.
Step 13 After you have the SLAs that you want to create correctly specified in the top data field, click Next to continue.
The next window is shown in Figure 8-18, "Providing a Task Name for Creation of SLAs."
Step 14 Provide a unique Task Name.
Step 15 Click Next.
Step 16 In the next window, you can choose to schedule the task by selecting Yes and clicking Next. In this case the next step is Step 17.
Otherwise, you can choose not to schedule the task by selecting No and clicking Next. In this case, the next step is Step 18.
Step 17 If you chose to schedule the task, in the next window, choose the scheduling directions and click Next. See Chapter 11, "Scheduling," for a full detailed description of scheduling.
Step 18 If you did not schedule the task, you are informed that "The task manager is about to save the task." If you did schedule the task, you are informed that "The task manager is about to save and schedule the task." If you want to change your mind on the scheduling instructions, click Back and return to Step 16 or Step 17. When you are ready to save and schedule the task, click Next.
Step 19 You are informed that "All steps are done." Click Close to close the wizard.
Delete SLA deletes an SA Agent probe from the router.
When you navigate from Monitoring > Provision SLA Definitions and Collect SLA Data and then choose Delete SLA, you can then implement the following steps:
The next window, as shown in Figure 8-19, "Selecting CEs to Delete SLAs," allows you to select one or more CEs.
Step 2 Click the VPN drop-down menu to choose a specific VPN.
The CEs for the chosen customer and VPN appear in the pane with the column headings CE Name, Network Name, and Domain Name.
Step 3 Select one or more CEs for which you want to delete SLAs. Press the Ctrl key to highlight multiple CEs.
Step 4 Click Next to continue.
The next window is shown in Figure 8-20, "Selecting SLAs to Delete."
Step 5 Highlight one or more SLAs to delete.
Step 6 Press the Ctrl key to highlight multiple CEs.
Step 7 Click Next to continue.
The next window is shown in Figure 8-21, "Providing a Task Name for Deletion of SLAs."
Step 8 Provide a unique Task Name.
Step 9 Click Next.
Step 10 In the next window, you can choose to schedule the task by selecting Yes and clicking Next. In this case the next step is Step 11.
You can choose not to schedule the task by selecting No and clicking Next. In this case, the next step is Step 12.
Step 11 If you chose to schedule the task, in the next window, choose the scheduling directions and click Next. See Chapter 11, "Scheduling," for a full detailed description of scheduling.
Step 12 If you did not schedule the task, you are informed that "The task manager is about to save the task." If you did schedule the task, you are informed that "The task manager is about to save and schedule the task." If you want to change your mind on the scheduling instructions, click Back and return to Step 10 or Step 11. When you are ready to save and schedule the task, click Next.
Step 13 You are informed that "All steps are done." Click Close to close the wizard.
Collect Data for SLA Monitoring downloads SLA statistics collected over the last hour from one or more specified routers. The specified routers have the relevant SA Agent probes programmed on them, which are collecting SLA statistics.
|
Note Data for a new SLA does not appear until one hour after the creation of the SLA. |
When you navigate from Monitoring > Provision SLA Definitions and Collect SLA Data and then choose Collect Data for SLA Monitoring, you can then implement the following steps:
The next window, as shown in Figure 8-22, "Selecting CEs to Collect Data for SLA Monitoring," allows you to select one or more CEs.
Step 2 Click the VPN drop-down menu to choose a specific VPN.
The CEs for the chosen customer and VPN appear in the pane with the column headings CE Name, Network Name, and Domain Name.
Step 3 Select one or more CEs from which you want to collect SA Agent data. Press the Ctrl key to highlight multiple CEs.
Step 4 Click Next to continue.
The next window to appear is shown in Figure 8-23, "Providing a Task Name to Collect Data for SLA Monitoring."
Step 5 Provide a unique Task Name.
Step 6 Then click Next.
Step 7 In the next window, you can choose to schedule the task by selecting Yes and clicking Next. In this case the next step is Step 8.
You can choose not to schedule the task by selecting No and clicking Next. In this case, the next step is Step 9.
Step 8 If you chose to schedule the task, in the next window, choose the scheduling directions and click Next. See Chapter 11, "Scheduling," for a full detailed description of scheduling.
Step 9 If you did not schedule the task, you are informed that "The task manager is about to save the task." If you did schedule the task, you are informed that "The task manager is about to save and schedule the task." If you want to change your mind on the scheduling instructions, click Back and return to Step 7 or Step 8. When you are ready to save and schedule the task, click Next.
Step 10 You are informed that "All steps are done." Click Close to close the wizard.
This section contains the following categories:
When you collect VPN routing information, you collect all VPN routing related tables from a Cisco router. You collect the VRF table, VPN CEF table, and BGP tag table. All these tables are correlated into one table called the VFIT (VPN Forwarding Info Table). This VFIT table is stored in the collection repository.
The MPLS VPN Solution accounting and auditing modules use the VFIT table for their internal calculation. When the accounting collection is scheduled, a new VFIT table is automatically collected as part of that process, but the auditing does not collect a new VFIT table. The auditor uses the last VFIT table in the repository. Therefore, for a meaningful audit, before you run the audit you should Collect VPN Routing Information, which collects the VFIT table.
To set up routers for collection, be sure to implement the following requirements:
When setting up collection from routers, be sure that all the routers have the same prompts as in the csm.properties file for netsys.router.loginprompt and netsys.router.passwordprompt. The default values match the default values on Cisco routers. They are as follows:
netsys.router.loginprompt = Username:
netsys.router.passwordprompt = Password:
If you use nonstandard router prompts in the csm.properties file, be sure you set the same values for all the routers from which you collect.
For the collection module of MPLS VPN Solution, enable or disable the Domain Name Server (DNS) on the routers. If DNS is not properly configured on the routers, collections will fail due to a time-out.
|
Note Enabling DNS causes DNS to handle the name resolution. Otherwise, name resolution is handled by the routers. |
To enable DNS, enter the following commands on the router:
ip domain-lookup
ip name-server <a.b.c.d>
where: <a.b.c.d> is a valid DNS.
To disable DNS, it is important to enter the following command on all routers:
no ip domain-lookup
To collect VPN routing information for Audit Routing, implement the following steps:
|
Note An alternative to selecting Monitoring > Collect VPN Routing Information is to select Tools > Tasks and then in the Actions menu item select New Task > Collect VPN Routing Information and click Ok. Both paths navigate to the same wizard. |
Step 2 An introduction explains that this will set up a scheduled task that collects VPN routing information from Cisco routers. This information is necessary for the Use VPN routing information during audits behavior modifier option of the audit reports. The information is also used to generate VPN accounting reports (accessible from the Monitoring menu). Click Next to continue.
Step 3 The next window, as shown in Figure 8-25, "Selecting Devices for VPN Routing Information Collection,"allows you to specify devices for which to collect VPN routing information.
In the window in Figure 8-25, "Selecting Devices for VPN Routing Information Collection," first click the Network drop-down menu to choose the device from a specific network.
This window has two panels with the column headings Network, Name, Domain, and Role. The upper panel includes all the routers selected by choosing a network from the Network drop-down menu. The lower panel will be populated to include all the routers that you choose in Step 4 and Step 5.
In the upper panel, you can sort the routers on each of the column headings, Network, Name, Domain, and Role. Just click that column header to sort on it.
Step 4 This step explains how to move routers from the upper panel to the lower panel, thus selecting the routers from which VPN routing information is collected.
|
Note Select only PEs, because there is no VPN routing information in CEs. Do NOT use the Add All button. |
If you do not select any devices in the upper panel, you can select Add All and all the devices appear in the lower panel. If you select one or more devices, you can click Add and only those devices appear in the lower panel.
Step 5 If you decide not to choose the devices now listed in the lower panel, you can either select Remove All to eliminate all the selections in the lower panel, or you can select those devices that you want to eliminate and click Remove.
You can continue editing the set of routers in the lower panel by repeating Step 4 and Step 5.
Step 6 Click Next, when you want to choose the devices that appear in the lower block as the devices for which VPN routing information will be collected.
Step 7 In the next window, as shown in Figure 8-26, "Providing a Task Name for Collection of VPN Routing Information," provide a unique Task Name. Then click Next.
Step 8 In the next window, you can choose to schedule the task by selecting Yes and clicking Next. In this case the next step is Step 9.
You can choose not to schedule the task by selecting No and clicking Next. In this case, the next step is Step 10.
Step 9 If you chose to schedule the task, in the next window, choose the scheduling directions and click Next. See Chapter 11, "Scheduling," for a full detailed description of scheduling.
Step 10 If you did not schedule the task, you are informed that "The task manager is about to save the task." If you did schedule the task, you are informed that "The task manager is about to save and schedule the task." If you want to change your mind on the scheduling instructions, click Back and return to Step 8 or Step 9. When you are ready to save and schedule the task, click Next.
Step 11 You are informed that "All steps are done." Click Close to close the wizard.
This section contains the following categories:
Collect router configuration files to audit services provisioned by MPLS VPN Solution. You must do this after you populate targets and the directory repository and prior to any other steps.
To set up routers for collection, be sure to implement the following requirements:
When setting up collection from routers, be sure that all the routers have the same prompts as in the csm.properties file for netsys.router.loginprompt and netsys.router.passwordprompt. The default values match the default values on Cisco routers. They are as follows:
netsys.router.loginprompt = Username:
netsys.router.passwordprompt = Password:
If you use nonstandard router prompts in the csm.properties file, be sure you set the same values for all the routers from which you collect.
For the collection module of MPLS VPN Solution, be sure to enable or disable the DNS on each router, as appropriate. If DNS is not properly configured on the routers, collections will fail due to a time-out.
|
Note Enabling DNS causes the specified DNS server to handle the name resolution. Otherwise, name resolution is handled by the router. |
To enable DNS, enter the following commands on the router:
ip domain-lookup
ip name-server <a.b.c.d>
where: <a.b.c.d> is a valid DNS server.
To disable DNS, it is important to enter the following command on the router:
no ip domain-lookup
To collect router configuration files, implement the following steps:
|
Note An alternative to selecting Monitoring > Collect Router Configuration Files is to select Tools > Tasks and then in the Actions menu item, select New Task > Collect Router Configuration Files and click Ok. Both paths navigate to the same wizard. |
Step 2 The next window provides information about the choices: collecting the Cisco router configuration from the selected routers or importing Cisco router configuration files. This is just an information window; click Next to continue.
Step 3 The next window is shown in Figure 8-28, "Action to Perform for Collect Router Configuration."
This window allows you to collect router configuration information from either of the following:
Step 4 Click Next to continue.
Live collection of router configuration performs a telnet operation to the routers to collect the running configuration of each router.
For collection of router configuration, you have navigated from VPN Console > Monitoring > Collect Router Configuration > Live Collection of Router Configuration. Implement the following steps:
In the window in Figure 8-29, "Selecting Devices for Router Configuration Collection," first click the Network drop-down menu to choose a specific network.
This window has two panels with the column headings Network, Name, Domain, and Role. The upper panel includes all the routers within the network selected from the Network drop-down menu. The lower panel will be populated to include all the routers that you choose in Step 2 and Step 3.
In the upper panel, you can sort the routers on each of the column headings, Network, Name, Domain, and Role. Just click that column header to sort on it.
Step 2 This step explains how to move routers from the upper panel to the lower panel, thus selecting the routers from which router configuration data is collected.
If you do not select any devices in the upper panel, you can select Add All and all the devices appear in the lower panel. If you select one or more devices, you can click Add and only those devices appear in the lower panel.
Step 3 If you decide not to choose the routers now listed in the lower panel, you can either select Remove All to eliminate all the selections in the lower panel, or you can select those devices that you want to eliminate and click Remove.
You can continue editing the set of routers in the lower panel by repeating Step 2 and Step 3.
Step 4 Click Next, when you want to choose the devices that appear in the lower block as the devices from which router configuration data will be collected.
Step 5 The next window is shown in Figure 8-30, "Selecting Additional Configuration Collection Options."
The window in Figure 8-30, "Selecting Additional Configuration Collection Options," allows you to Mask passwords in collected files or not. Masked passwords appear as "XXXX" in the collected configuration.
Step 6 Leave the default of Mask passwords in collected files or unselect it.
Step 7 Click Next to continue.
The next window is shown in Figure 8-31, "Providing a Task Name for Live Collection of Router Configuration."
Step 8 Provide a unique Task Name.
Step 9 Click Next.
Step 10 In the next window, you can choose to schedule the task by selecting Yes and clicking Next. In this case the next step is Step 11.
You can choose not to schedule the task by selecting No and clicking Next. In this case, the next step is Step 12.
Step 11 If you chose to schedule the task, in the next window, choose the scheduling directions and click Next. See Chapter 11, "Scheduling," for a detailed description of scheduling.
Step 12 If you did not schedule the task, you are informed that "The task manager is about to save the task." If you did schedule the task, you are informed that "The task manager is about to save and schedule the task." If you want to change your mind on the scheduling instructions, click Back and return to Step 10 or Step 11. When you are ready to save and schedule the task, click Next.
Step 13 You are informed that "All steps are done." Click Close to close the wizard.
Collected router configurations that exist in files in a directory can be imported.
|
Note It is critical that each filename being imported is the same as the name of the corresponding router. If a domain name is defined, this must be used as an extension to the filename. For example, if the router name is Router1 and the domain name is mydomain.com, the name of the file must be Router1.mydomain.com. All files in this directory must be configuration files. |
To import router configurations from files, you have navigated from VPN Console > Monitoring > Collect Router Configuration > Import Router Configuration from Files. Implement the following steps:
The next window, as shown in Figure 8-33, "Selecting Name of Network that Contains the Routers Corresponding to the Configuration Files to Import," allows you to select the name of the network containing the routers for the configuration files that you want to import.
Step 2 Click the drop-down menu and click the network.
Step 3 Click Next to continue.
Step 4 In the next window, as shown in Figure 8-34, "Providing a Task Name for Importing Router Configurations," provide a unique Task Name.
Step 5 Click Next to continue.
Step 6 In the next window you can choose to schedule the task by selecting Yes and clicking Next. In this case, the next step is Step 7.
You can choose not to schedule the task by selecting No and clicking Next. In this case, the next step is Step 8.
Step 7 If you chose to schedule the task, in the next window, choose the scheduling directions and click Next. See Chapter 11, "Scheduling," for a detailed description of scheduling.
Step 8 If you did not schedule the task, you are informed that "The task manager is about to save the task." If you did schedule the task, you are informed that "The task manager is about to save and schedule the task." If you want to change your mind on the scheduling instructions, click Back and return to Step 6 or Step 7. When you are ready to save and schedule the task, click Next.
Step 9 You are informed that "All steps are done." Click Close to close the wizard.
This section contains the following categories:
Router configurations, known as configuration files, are usually collected at regular intervals and then examined for changes that affect the way the routers do their jobs. The normal collection process does not separate the routers whose configuration files have changed from the routers whose configuration files have not changed. However, the routers whose configuration files have changed are the only ones that need to be collected. SmartCollector finds the routers whose configuration files have changed and puts them in a group to have their configuration files collected.
With SmartCollector, we create a task and schedule it to be run once. When it executes, all the targeted routers are instructed to advise the MPLS VPN Solution software using the Simple Network Management Protocol (SNMP) of any change to their configuration files. MPLS VPN Solution, through the trapcatcher daemon, notes these traps and keeps track of the routers whose configuration files have changed, and thus need to be collected. The purpose of configuring traps (SmartCollector) is to efficiently collect router configuration files from a set of routers grouped by network.
An example of the potential substantial savings is a scenario in which a network has 200 routers but the configuration files for only 20 of the routers have changed. In this example, SmartCollector only collects the configuration files for the 20 that have changed rather than for all 200 routers. If on average only 10% of the routers have their configuration files changed between scheduled collections, each SmartCollection takes only 10% of the resources of a full collection.
Note that periodically (as determined by the cycle_t variable in csm.properties), the scheduler ignores the reduced target list and collects from all routers in the original target list. Thus even those routers whose traps failed to reach the MPLS VPN Solution are collected periodically.
The following is an example of the flow of execution:
1. Create collect router configuration files, as explained in the "Collect Router Configuration Files" section, for network N1 (which contains routers: R0, R1, R2, R3, R4).
2. Every hour, the scheduler executes a Collect Config task, which collects from the routers: R0, R1, R2, R3, nd R4.
3. The weakness with this process is that most router configuration files will not have changed and effort is wasted.
4. Solution: Execute Register for config---change traps for the specified routers in network N1. This task instructs all IOS version 12.x based routers to inform MPLS VPN Solution via SNMP traps if configuration files change (from the terminal or by trivial file transfer protocol (tftp)).
5. Starting with the next execution of a Collect Config task, the Collect Config task collects the configuration files of only those routers that have sent SNMP traps to MPLS VPN Solution, signifying that their configuration files may have changed.
6. Every time period defined in the csm.properties file by the cycle_t parameter, the Collect Config task makes a complete collection.
7. In this example, let us assume that the cycle_t parameter is set to 250 minutes, and let us assume that the Collect Config task is scheduled to execute every hour starting at 1:00 p.m. Let us also assume that the Register for config---change traps task was initiated at 1:25 p.m.
8. At 1:00 p.m. a complete collection is executed.
9. No Collect Config task executes when Register for config---change traps executes at 1:25 p.m.
10. At 2:00 p.m., 3:00 p.m., 4:00 p.m., 5:00 p.m., and 6:00 p.m., the Collect Config task executes but collects configuration files only for those routers that have sent traps and are in the Collect Config task's original list of targets.
11. At 7:00 p.m. a full collection occurs, based on the following logic:
|
Note The clock starts for the cycle_t parameter with the first collection after Register for config---change traps. The next full collection is the first Collect Configs task scheduled after meeting the minimum of the cycle_t parameter, based on SmartCollector. |
To set up prior to configuring traps, be sure to implement the following requirements:
When setting up collection from routers, be sure that all the routers have the same prompts as in the csm.properties file for netsys.router.loginprompt and netsys.router.passwordprompt. The default values match the default values on Cisco routers. They are as follows:
netsys.router.loginprompt = Username:
netsys.router.passwordprompt = Password:
If you use nonstandard router prompts in the csm.properties file, be sure you set the same values for all the routers from which you collect.
For the collection module of MPLS VPN Solution, enable or disable the DNS on the routers. If DNS is not properly configured on the routers, collections will fail due to a time-out.
|
Note Enabling DNS causes DNS to handle the name resolution. Otherwise, name resolution is handled by the routers. |
To enable DNS, enter the following commands on the router:
ip domain-lookup
ip name-server <a.b.c.d>
where: <a.b.c.d> is a valid DNS.
To disable DNS, it is important to enter the following command on all routers:
no ip domain-lookup
Prior to entering the GUI path for configuring traps, implement the following steps for each and every router, to determine whether SNMP is enabled. If SNMP is enabled, these steps will lead you to the first GUI path. If SNMP is not enabled, these steps will direct you on how to enable SNMP.
Step 2 Go into the enable state.
Step 3 Enter the command show snmp.
Step 4 Determine whether the following line is present:
% SNMP agent not enabled
Step 5 If the line in Step 4 is not present, you have determined that SNMP is enabled. Then enter the show run command to view the SNMP community strings at the end of the configuration file. If you have more routers to verify, return to Step 1 and follow these steps for the next router that you want to verify. Otherwise, proceed to the "Populate Interface Information for Cisco Router Targets" section.
If the line in Step 4 is present, proceed to Step 6.
Step 6 To turn on SNMP, at the prompt, enter the command config t.
Step 7 Enter the following commands:
snmp-server community <userstring> RO
snmp-server community <userstring> RW
If you have more routers to verify, return to Step 1 and follow these steps for the next router that you want to verify.
|
Note These SNMP strings must agree with those listed in the target password database for each router. (Refer to Chapter 3 in the Cisco VPN Solutions Center: MPLS Solution User Guide.) |
Prior to registering the config change traps, you must populate the router interfaces in the directory repository, as follows.
From the VPN Console window, choose Monitoring > Configure Traps > Populate Interface Information for Cisco Router Targets, as shown in Figure 8-35, "Populate Interface Information for Cisco Router Targets."
|
Note An alternative to selecting Monitoring > Configure Traps > Populate Interface Information for Cisco Router Targets is to select Tools > Tasks and then in the Actions menu item select New Task > Populate Interface Information for Cisco Router Targets and click Ok. Both paths navigate to the same wizard. |
After you finish navigating through this wizard, you may choose to read the "Register for ConfigChange Traps" section. This explains what happens when you register for config change traps.
This section explains how to register configuration file change traps, which indicates the routers (SmartCollector) for which data will be collected only if the routers have changed.
If Collect Config tasks are running and you initiate SmartCollection by registering for traps, the PEs MUST be IOS version 12.x to return traps.
Step 2 Follow the wizard.
|
Note An alternative to selecting Monitoring > Configure Traps > Register for Config---Change Traps is to select Tools > Tasks and then in the Actions menu item select New Task > Register for config---change traps and click Ok. Both paths navigate to the same wizard. |
|
Note Configuration files for the routers that are not selected for SmartCollection are not collected. |
Step 3 The first window, as shown in Figure 8-37, "Register for configchange trapsIntro," explains the process. Click Next to continue.
Step 4 The next window allows you to continue to "Register to receive Cisco router config---change traps." Click Next to continue.
Step 5 The next window, as shown in Figure 8-38, "Selecting Devices," allows you to specify the routers that should send traps to MPLS VPN Solution.
In the window in Figure 8-38, "Selecting Devices," first click the Network drop-down menu to choose a specific network.
This window has two panels with the column headings Network, Name, Domain, and Role. The upper panel includes all the routers selected in this step. The lower panel will be populated to include all the routers that you choose in Step 6 and Step 7. The SmartCollector only collects data from the routers that have changed.
In the upper panel, you can sort the routers on each of the column headings, Network, Name, Domain, and Role. Just click that column header to sort on it.
Step 6 This step explains how to move devices to the lower panel, thus selecting the router configuration files that will be collected only when the router configuration files change.
If you do not select any routers in the upper panel, you can select Add All and these will appear in the lower panel. If you select one or more routers, you can click Add and only those routers will appear in the lower panel.
Step 7 If you decide not to choose the routers now listed in the lower panel, you can either select Remove All to eliminate all the selections in the lower panel, or you can select those routers that you want to eliminate and click Remove.
You can continue editing the set of routers in the lower panel by repeating Step 6 and Step 7.
Step 8 Click Next, when you want to choose the routers that appear in the lower block as the routers for which data will be collected only when the router configuration files change.
|
Note All the unchosen routers from the chosen network are not collected by the Collect Config tasks. |
Step 9 In the next window, as shown in Figure 8-39, "Providing a Task Name to Register for ConfigChange Traps," provide a Task Name. Then click Next.
Step 10 In the next window you can choose to schedule the task by selecting Yes and clicking Next. In this case, the next step is Step 11.
You can choose not to schedule the task by selecting No and clicking Next. In this case, the next step is Step 12.
Step 11 If you chose to schedule the task, in the next window, choose the scheduling directions and click Next. See Chapter 11, "Scheduling," for a detailed description of scheduling.
Step 12 If you did not schedule the task, you are informed that "The task manager is about to save the task." If you did schedule the task, you are informed that "The task manager is about to save and schedule the task." If you want to change your mind on the scheduling instructions, click Back and return to Step 10 or Step 11. When you are ready to save and schedule the task, click Next.
Step 13 You are informed that "All steps are done." Click Close to close the wizard.
This section explains how to deselect routers that you initially chose by SmartCollector, as explained in the "Register for ConfigChange Traps" section. After this procedure is completed, configuration files for all routers are collected whenever a collect configuration task is selected by the scheduler.
Step 2 Follow the wizard.
|
Note An alternative to selecting Monitoring > Configure Traps > Deregister for Config---Change Traps is to select Tools > Tasks and then in the Actions menu item select New Task > Deregister for config---change traps and click Ok. Both paths navigate to the same wizard. |
The first window explains the process.
Step 3 Click Next to continue.
|
Note An alternative to selecting Monitoring > Configure Traps > Deregister for Config---Change Traps is to select Tools > Tasks and then in the Actions menu item select New Task > Deregister for config---change traps and click Ok. Both paths navigate to the same wizard. |
The next window allows you to continue to "Deregister to receive Cisco router config---change traps."
Step 4 Click Next to continue.
The next window, as shown in Figure 8-41, "Selecting Devices Not to Trap," allows you to specify routers not to be trapped.
Step 5 In the window in Figure 8-41, "Selecting Devices Not to Trap," first click the Network drop-down menu to choose a specific network.
This window has two panels with the column headings Network, Name, Domain, and Role. The upper panel includes all the routers chosen in this step. The lower panel will be populated to include all the routers that you choose in Step 6 and Step 7, that is all the routers that will return to the status of collecting data at all times.
In the upper panel, you can sort the routers on each of the column headings, Network, Name, Domain, and Role. Just select that column header to sort on it.
Step 6 This step explains how to move routers to the lower panel, thus selecting the routers that will return to the status of collecting data at all times.
If you do not select any routers in the upper panel, you can select Add All and these will appear in the lower panel. If you select one or more routers, you can click Add and only those routers will appear in the lower panel.
Step 7 If you decide not to choose the routers in the lower panel, you can either select Remove All to eliminate all the selections in the lower panel, or you can select those routers that you want to eliminate and click Remove. You can continue editing the set of routers in the lower panel by repeating Step 6 and Step 7.
Step 8 Click Next, when you want to choose the routers that appear in the lower block as the routers that will return to the status of collecting data at all times.
Step 9 In the next window, as shown in Figure 8-42, "Providing a Task Name to Deregister for ConfigChange Traps," provide a Task Name. The click Next.
Step 10 In the next window you can choose to schedule the task by selecting Yes and clicking Next. In this case, the next step is Step 11.
You can choose not to schedule the task by selecting No and clicking Next. In this case, the next step is Step 12.
Step 11 If you chose to schedule the task, in the next window, choose the scheduling directions and click Next. See Chapter 11, "Scheduling," for a detailed description of scheduling.
Step 12 If you did not schedule the task, you are informed that "The task manager is about to save the task." If you did schedule the task, you are informed that "The task manager is about to save and schedule the task." If you want to change your mind on the scheduling instructions, click Back and return to Step 10 or Step 11. When you are ready to save and schedule the task, click Next.
Step 13 You are informed that "All steps are done." Click Close to close the wizard.
The file csm.properties holds information for target collector files in the variables prefixed with netsys.datacollector.cct. You can use a text editor to reset the properties for the csm.properties file. These files, their defaults, and what they represent are explained in Table 8-2, "Property Settings for SmartCollector."
| Property | Default Value | Explanation |
|---|---|---|
sc_port | 1607 | The value is the port location at which the SmartCollector listens for traps. |
sc_delay | 120 | The value is the number of seconds between writing traps to the repository. |
tc_targets | tc_targets | This location is where all traps are kept. This file is for internal use. |
gc_targets | gc_targets | This location is where all unused traps are kept.This file is for internal use. |
gc_failures | This location is where all failed traps are kept. This file is for internal use. | |
cycle_t | 250 | The value is the number of minutes between full collections. |
The following is the default of what you will find in the csm.properties file:
netsys.datacollector.cct.sc_port = 1607netsys.datacollector.cct.sc_delay = 120
netsys.datacollector.cct.tc_targets = tc_targets
netsys.datacollector.cct.gc_targets = gc_targets
netsys.datacollector.cct.gc_failures = gc_failures
netsys.datacollector.cct.cycle_t = 250
Accounting reports, which are based on processed accounting data, provide network usage and planning information. Billing systems can get the traffic usage from the Accounting Server, which leverages collected accounting data and provides complete billing services to customers.
After collecting VPN accounting data, explained in the "Collect VPN Accounting Data" section, you can view reports about VPN accounting data. As shown in Figure 8-43, "Choose from View Accounting Reports," from the VPN Console window, choose Monitoring > View Accounting Reports, followed by one of the following types of reports:
For information within the Accounting Reports, first see the generic report fields and their explanations in Chapter 12, "Reports Overview." Additionally each report has a report-specific Results pane and bottom task bar information.
Traffic Summary reports are time-based drill-down reports that display total packets and total K bytes for traffic that can be mapped to the VPN world (VPN Traffic) and otherwise to Unmappable Traffic. Traffic Summary acts as a starting point to get to other reports.
To display a Traffic Summary report, implement the following step:
You receive a report similar to the example in Figure 8-45, "Example Traffic Summary Report."
For a description of the Traffic Summary report, first see the explanation of the generic report fields in "Reports Overview." The section Results Pane for Traffic Summary Report provides information specific to the Traffic Summary report.
The columns of information are as follows:
Application Type Summary reports provide total packets and total K bytes for each application type.
To display an Application Type Summary report, implement the following step:
You receive a report similar to the example in Figure 8-47, "Example Application Type Summary Report."
For a description of the Application Type Summary report, first see the explanation of the generic report fields in "Reports Overview." The section Results Pane for Application Type Summary Report provides information specific to the Application Type Summary report.
The columns of information are as follows:
Customer Summary reports provide total packets and total K bytes for each customer plus drill-down reports for customer site, type of service, and application type.
To display a Customer Summary report, implement the following step:
You receive a report similar to the example in Figure 8-49, "Example Customer Summary Report."
For a description of the Customer Summary report, first see the explanation of the generic report fields in "Reports Overview." The section Results Pane for Customer Summary Report provides information specific to the Customer Summary report.
The columns of information are as follows:
PE to PE Traffic Summary provides a report of all traffic between PE to PE plus drill-down reports for: PE to connected CE; PE to remote CE; PE traffic; PE to CE.
To display a PE to PE Traffic Summary report, implement the following step:
You receive a report similar to the example in Figure 8-51, "Example PE to PE Traffic Summary Report."
For a description of the PE to PE Traffic Summary report, first see the explanation of the generic report fields in "Reports Overview." The section Results Pane for PE to PE Traffic Summary Report provides information specific to the PE to PE Traffic Summary report.
The columns of information are as follows:
CE to CE Traffic Summary provides a report of all traffic between CE to CE.
To display a CE to CE Traffic Summary report, implement the following steps:
You receive a window similar to the example in Figure 8-53, "Customer Chooser for CE to CE Traffic Summary."
Step 2 In the Select a Customer pane in Figure 8-53, "Customer Chooser for CE to CE Traffic Summary," highlight the row or rows that indicate the customer or customers you want to select.
Step 3 In the Report Time Level drop-down list, select from among the following choices:
Step 4 Click OK to generate a report based on the information you specified in this window, as shown in Figure 8-54, "Example CE to CE Traffic Summary Report." If you click Cancel, you will return to the VPN Console window.
For a description of the CE to CE Traffic Summary report, first see the explanation of the generic report fields in "Reports Overview." The section Results Pane for CE to CE Traffic Summary Report provides information specific to the CE to CE Traffic Summary report.
The columns of information are as follows:
Type of Service Summary reports provide total packets and total K bytes for each TOS.
To display a Type of Service Summary report, implement the following step:
You receive a report similar to the example in Figure 8-56, "Example Type of Service Summary Report."
For a description of the Type of Service Summary report, first see the explanation of the generic report fields in "Reports Overview." The section Results Pane for Type of Service Summary Report provides information specific to the Type of Service Summary report.
The columns of information are as follows:
Customer Traffic Volume (CECE) reports on all traffic volume for a specific customer between CE to CE in packets or K bytes (by TOS).
To display a Customer Traffic Volume (CE---CE) report, implement the following steps:
You receive a window similar to the example in Figure 8-58, "CE Chooser for Customer Traffic Volume (CECE)."
Step 2 In the Customer drop-down menu in Figure 8-58, "CE Chooser for Customer Traffic Volume (CECE)," click to get a list of Customers.
Step 3 Select the customer for which you want information.
In the Customer pane, each row of information is about a specific CE for the specified Customer. It includes the following columns of information and a row for each CE.
|
Note In the Customer pane, you can click the column header name for any column you want to sort. |
Step 4 Select a CE for which you want information and highlight that row.
Step 5 In the Direction pane, select either Origin or Destination to select traffic originated from or targeted to the selected CE, respectively.
Step 6 In the Report Time Level drop-down list, select from among the following choices:
Step 7 Click OK to generate a report based on the information you specified in this window, as shown in Figure 8-59, "Example Customer Traffic Volume (CECE) Report." If you click Cancel, you will return to the VPN Console window.
For a description of the Customer Traffic Volume (CE---CE) report, first see the explanation of the generic report fields in "Reports Overview." The section Results Pane for Customer Traffic Volume (CECE) Report provides information specific to the Customer Traffic Volume (CE---CE) report.
The columns of information are as follows:
Network Traffic Volume (PEPE) reports on all traffic volume between PE to PE in packets or K bytes (by TOS).
To display a Network Traffic Volume (PE---PE) report, implement the following steps:
You receive a window similar to the example in Figure 8-61, "PE Chooser for Network Traffic Volume (PEPE)."
In the PE pane, each row of information is about a specific PE. It includes the following columns of information.
|
Note In the PE pane, you can click the column header name for any column you want to sort. |
Step 2 Select one or more PEs for which you want information and highlight those rows.
Step 3 In the Direction pane, select whether you want to view the Origin, to select traffic originated from the selected PEs, or the Destination, to select traffic targeted toward the selected PEs.
Step 4 In the Report Time Level drop-down list, select from among the following choices:
Step 5 Click OK to generate a report based on the information you specified in this window, as shown in Figure 8-62, "Example Network Traffic Volume (PEPE) Report." If you click Cancel, you will return to the VPN Console window.
For a description of the Network Traffic Volume (PE---PE) report, first see the explanation of the generic report fields in "Reports Overview." The section Results Pane for Network Traffic Volume (PEPE) Report provides information specific to the Network Traffic Volume (PE---PE) report.
The columns of information are as follows:
Traffic Volume (PECE) reports on all traffic between PE to CE (by TOS).
To display a Traffic Volume (PE---CE) report, implement the following steps:
You receive a window similar to the example in Figure 8-64, "PE Chooser for Traffic Volume (PECE).
In the PE pane, each row of information is about a specific PE. It includes the following columns of information.
|
Note In the PE pane, you can click the column header name for any column you want to sort. |
Step 2 Select one or more PEs for which you want information and highlight those rows.
Step 3 In the Direction pane, select whether you want to view the Origin, to select traffic originated from the selected PEs, or the Destination, to select traffic targeted toward the selected PEs.
Step 4 In the Report Time Level drop-down list, select from among the following choices:
Step 5 Click OK to generate a report based on the information you specified in this window, as shown in Figure 8-65, "Example Traffic Volume (PECE) Report." If you click Cancel, you will return to the VPN Console window.
For a description of the Traffic Volume (PE---CE) report, first see the explanation of the generic report fields in "Reports Overview." The section Results Pane for Traffic Volume (PECE) Report provides information specific to the Traffic Volume (PE---CE) report.
The columns of information are as follows:
Prior to viewing the committed access rate (CAR) management information bases (MIB) reports, you need to poll a router's CAR MIB, as explained in the "Poll a Router's CAR MIB" section. The CAR MIB status data is collected and kept in the repository. The aggregator aggregates the data to generate hourly, daily, weekly, monthly, and yearly data.
You can view the collected data in the repository. From the VPN Console window, choose Monitoring > View CAR MIB Reports, followed by one of the following types of reports, as shown in Figure 8-66, "Choose from View CAR MIB Reports":
To display the CAR MIB status for specific managed customer CE routers, implement the following steps:
You receive a window similar to the example in Figure 8-68, "Customer Chooser for CAR MIB Report by Customer."
Step 2 In the Select a Customer pane in Figure 8-68, "Customer Chooser for CAR MIB Report by Customer," highlight only one customer for which you want report information.
|
Note The wizard will inappropriately allow you to select more than one customer. Do not do this. If you select more than one customer, only the first customer in the list appears in the report. |
Step 3 In the Report Time Level drop-down list, select from among the following choices:
Step 4 Click OK to generate a report based on the information you specified in this window, as shown in Figure 8-69, "Example CAR MIB Status Report by Customer." If you click Cancel, you will return to the VPN Console window.
For a description of the CAR MIB Status Report by customer, first see the explanation of the generic report fields in "Reports Overview." The following sections provide information specific to the CAR MIB Status Report, by customer:
The columns of information are as follows:
|
Note If the Interface Name field defaults to DUMMY, run the wizard explained in the "Populate Interface Information for Cisco Router Targets" section. Then rerun this report. |
Selections in the bottom task bar for CAR MIB Status Report by customer include the following:
To display the CAR MIB status for specific PE routers, implement the following steps:
You receive a window similar to the example in Figure 8-71, "Network Chooser for CAR MIB Report by Network."
Step 2 In the Select a Network pane in Figure 8-71, "Network Chooser for CAR MIB Report by Network," highlight only one network for which you want report information.
|
Note The wizard will inappropriately allow you to select more than one network. Do not do this. If you select more than one network, only the first network in the list appears in the report. |
Step 3 In the Report Time Level drop-down list, select from among the following choices:
Step 4 Click OK to generate a report based on the information you specified in this window, as shown in Figure 8-72, "Example CAR MIB Status Report by Network." If you click Cancel, you will return to the VPN Console window.
For a description of the CAR MIB Status Report by network, first see the explanation of the generic report fields in "Reports Overview." The "Results Pane for CAR MIB Status Report, By Network" section provides information specific to the CAR MIB Status Report, by network.
The columns of information are as follows:
|
Note If the Interface Name field defaults to DUMMY, run the wizard explained in the "Populate Interface Information for Cisco Router Targets" section. Then rerun this report. |
This report shows all collected data in the database not collected by SNMP. It can be used as a debugging tool to determine whether your collections were successful and available for other reports or applications. From the VPN Console window, choose Monitoring > View Data Reports, as shown in Figure 8-73, "Choose View Data Reports."
For information within the Data Reports, first see the generic report fields and their explanations in Chapter 12, "Reports Overview." Additionally, data reports have a report-specific Results pane, as shown in the section Results Pane for Data Reports.
The result of choosing View Data Reports is like the example in Figure 8-74, "Example of Data Reports."
Data can be collected from different types of sources. Data can currently be collected from a target or a network. The types of information in this report are the following:
After collecting SA Agent data for SLA monitoring, explained in the "Provision SLA Definitions and Collect SLA Data" section, you can view reports about the aggregated data. From the VPN Console window, choose Monitoring > View SLA Reports followed by one of the following types of reports, as shown in Figure 8-75, "Choose from View SLA Reports."
For information within the SLA Reports, first see the generic report fields and their explanations in Chapter 12, "Reports Overview." Additionally each report has a report-specific Results pane and bottom task bar information.
When you choose Summary Report, you can drill down to time-based reports that show the parameters: Connectivity as a percentage, Max. Delay in milliseconds, and Threshold Violation as a percentage. These parameters are available in annual, monthly, weekly, daily, and hourly reports. For each parameter, you can generate detailed reports that show more related parameters. The reports can be aggregated by: Source Router (the source of the SLA), SLA identifier, customer name, or VPN name.
To display a Summary Report, implement the following step:
You receive a report similar to the example in Figure 8-77, "Example Summary Report."
For a description of the Summary Report, first see the explanation of the generic report fields in "Reports Overview." The following sections provide information specific to the Summary Report:
The columns of information are as follows:
Selections in the bottom task bar for Summary Report include the following:
|
Note You can navigate to different types of reports from the Summary Report. |
When you choose to Aggregate By and the report shows only one parameter, either Connectivity %, Max. Delay (ms), or Threshold Violation %, then in the monthly, weekly, and daily report levels the following color scheme appears:
|
Note In these reports green indicates a good state and red indicates a state to be concerned about. |
Jitter Report displays statistics that are measured only by Voice Jitter SLAs originated in a selected router. The reports are time based. They show hourly, daily, weekly, monthly, and annual data and can be aggregated by: SLA ID, source router, destination router, VPN, or Customer. Each of the following arguments are shown both in the direction of source to destination and in the direction of destination to source:
To display a Jitter Report, implement the following steps:
You receive a window similar to the example in Figure 8-79, "CE Chooser for Jitter Report."
Step 2 In the Customer drop-down menu in Figure 8-79, "CE Chooser for Jitter Report," click to get a list of Customers.
Step 3 Select the customer for which you want information.
In the Customer pane, each row of information is about a specific CE for the specified Customer. It includes the following columns of information and a row for each CE.
|
Note In the Customer pane, you can click the column header name for any column you want to sort. |
Step 4 Select a CE for which you want information and highlight that row.
Step 5 In the Direction pane, select whether you want to view the traffic going Forward or Backward from the selected CE.
Step 6 In the Jitter Parameter drop-down list, select from among the following choices:
Step 7 In the Report Time Level drop-down list, select from among the following choices:
Step 8 Click OK to generate a report based on the information you specified in this window, as shown in Figure 8-80, "Example Jitter ReportForward Max. Jitter Aggregated by Destination Router." If you click Cancel, you will return to the VPN Console window.
For a description of the Jitter Report, first see the explanation of the generic report fields in "Reports Overview." The following sections provide information specific to the Jitter Report:
The first column depends on your selection from Aggregate By and subsequent columns depend on the time level you chose.
Selections in the bottom task bar for Jitter Report include the following:
HTTP Report displays statistics that are measured only by HTTP SLAs. The reports are time based. They show hourly, daily, weekly, monthly, and annual data.
To display an HTTP Report, implement the following step:
The resulting types of reports are explained in the following sections:
For each summary report, you can drill down to the corresponding stages report. The stages are the different HTTP protocol stages: dns lookup, tcp connection, and transaction. The reports show the distribution in percentage of parameters among these three stages.
The parameters are:
Similar to the SLA Summary report, the Summary HTTP Report shows the arguments: percentage of connectivity, Max Delay in milliseconds, and percentage of Threshold violation, which may each be aggregated by SLA ID, source router, VPN, or Customer. See the example in Figure 8-82, "Summary HTTP Report Aggregated by Source Router."
From each Summary HTTP Report, you can drill down to the corresponding stages report from the Stages Report drop-down menu in the bottom task bar. The stages are the different HTTP protocol stages: DNS, TCP Connection, and Transaction. The reports show the distribution in percentage of arguments in the stages: Round Trip Time (ms), Timeouts (#), and Errors (#). See the example in Figure 8-83, "HTTP Stages ReportRound Trip Time Aggregated by Source Router."
Customer Packet Drop (CECE) provides reports that show the packet drop percentage among CEs of a specific customer. This information is measured only for the SLAs with the Jitter protocol. The reports are aggregated by class of service. The reports are annually, monthly, weekly, daily, and hourly. You can navigate along the time scale.
To display a Customer Packet Drop (CECE) report, implement the following step:
You receive a window similar to the example in Figure 8-85, "CE Chooser for Customer Packet Drop (CECE)."
The information about Figure 8-85, "CE Chooser for Customer Packet Drop (CECE)," is explained in the following categories:
Step 2 In the Customer drop-down menu in Figure 8-85, "CE Chooser for Customer Packet Drop (CECE)," select one or more rows to select one or more CEs.
In the Customer pane, each row of information is about a specific CE for the specified Customer. It includes the following columns of information and a row for each CE.
|
Note In the Customer pane, you can click the column header name for any column you want to sort. |
Step 3 Select one or more CEs for which you want information and highlight those rows.
Step 4 In the Direction pane, select whether you want to view the Origin, to select traffic originated from the selected PEs, or the Destination, to select traffic targeted toward the selected PEs.
Step 5 In the Report Time Level drop-down list, select from among the following choices:
Step 6 Click OK to generate a report based on the information you specified in this window, as shown in Figure 8-86, "Example Customer Packet Drop (CECE) Report." If you click Cancel, you will return to the VPN Console window.
The columns of information are as follows:
|
Note N/A means there were no completions for this SLA; no meaningful value can be calculated. |
Customer Round Trip Delay (CECE) provides reports that show the Max/Min and Avg. round-trip time (in milliseconds) among CEs of a specific customer. The statistics are for all the probe types. The reports are aggregated by class of service. The reports are annually, monthly, weekly, daily, and hourly. You can navigate along the time scale.
To display a Customer Round Trip Delay (CECE) report, implement the following step:
You receive a window similar to the example in Figure 8-88, "CE Chooser for Customer Round Trip Delay (CECE)."
Step 2 In the Customer drop-down menu in Figure 8-88, "CE Chooser for Customer Round Trip Delay (CECE)," select one or more rows to select one or more CEs.
In the Customer pane, each row of information is about a specific CE for the specified Customer. It includes the following columns of information and a row for each CE.
|
Note In the Customer pane, you can click the column header name for any column you want to sort. |
Step 3 Select one or more CEs for which you want information and highlight those rows.
Step 4 In the Report Time Level drop-down list, select from among the following choices:
Step 5 Click OK to generate a report based on the information you specified in this window, as shown in Figure 8-89, "Example Customer Round Trip Delay (CECE) Report." If you click Cancel, you will return to the VPN Console window.
The columns of information are as follows:
|
Note N/A means there were no completions for this SLA; no meaningful value can be calculated. |
Network Packet Drop (PEPE) provides reports that show the packet drop percentage among all the shadow SA Agent CEs in the network. The network packet drop between PEs is measured by the shadow SA Agent CEs that are connected to the PEs. This information is measured only for the SLAs with the Jitter protocol. The reports are aggregated by class of service. The reports are annually, monthly, weekly, daily, and hourly. You can navigate along the time scale.
To display a Network Packet Drop (PEPE) report, implement the following steps:
You receive a window similar to the example in Figure 8-91, "CE Chooser for Network Packet Drop (PEPE)."
Step 2 In the Customer drop-down menu in Figure 8-91, "CE Chooser for Network Packet Drop (PEPE)," select one or more rows to select one or more PEs.
|
Note In the Customer pane, you can click the column header name for any column you want to sort. |
Step 3 Select one or more CEs for which you want information and highlight those rows.
Step 4 In the Direction pane, choose either Origin or Destination to select SLAs originated or targeted to this shadow SA Agent CE, respectively
Step 5 In the Report Time Level drop-down list, select from among the following choices:
Step 6 Click OK to generate a report based on the information you specified in this window, as shown in Figure 8-92, "Example Network Packet Drop (PEPE) Report." If you click Cancel, you will return to the VPN Console window.
The columns of information are as follows:
|
Note N/A means there were no completions for this SLA. |
Network Round Trip Delay (PEPE) provides reports that show the Max/Min and Avg. round-trip time among shadow SA Agent CEs in the network. The statistics are for all the probe types. The reports are aggregated by class of service. The reports are annually, monthly, weekly, daily, and hourly. You can navigate along the time scale.
To display a Network Round Trip Delay (PEPE) report, implement the following steps:
You receive a window similar to the example in Figure 8-94, "CE Chooser for Network Round Trip Delay (PEPE)."
In the Customer pane, each row of information is about a shadow SA Agent CE. It includes the following columns of information and a row for each CE.
|
Note In the Customer pane, you can click the column header name for any column you want to sort. |
Step 2 Select one or more CEs for which you want information and highlight those rows.
Step 3 In the Direction pane, choose either Origin or Destination to select SLAs originated or targeted to this shadow SA Agent CE, respectively
Step 4 In the Report Time Level drop-down list, select from among the following choices:
Step 5 Click OK to generate a report based on the information you specified in this window, as shown in Figure 8-95, "Example Network Round Trip Delay (PEPE) Report." If you click Cancel, you will return to the VPN Console window.
The columns of information are as follows:
|
Note N/A means there were no completions for this SLA. |
SLA Definition provides a report that shows all the SLAs on the SA Agent routers from which data was collected. The SLA Definition report shows the SLA ID given to each SLA. SLAs in the report may have been deleted but are kept in the SLA Definition to match the old collected data.
To display an SLA Definition report, implement the following step:
You receive a window similar to the example in Figure 8-97, "Example SLA Definition Report."
The Results pane gives rows of information.
|
Note Click on the column label to sort by that type. For example, if you sort on Source, the IP addresses are displayed numerically. |
The columns help you identify the particular SLA for which you can show the statistics in the reports. The columns indicate the following:
Verification reports track status information from executed collections. The status information is associated with each individual target. Each collection attempt generates a set of attributes and corresponding status for each target accessed by the collection. Attributes are used to track the success or failure of various operations such as accessing a target or collecting information.
These reports provide a quick way to check whether there are any connectivity problems to collected targets (for example, any bad passwords or unreachable targets).
The data is merged into a database of most current information, with newer values overwriting older values. The reports accessible from View Verification Reports provide views of subsets of this data. A short delay may occur between when the collection completes and when the data is visible in these reports.
From the VPN Console window, choose Monitoring > View Verification Reports, as shown in Figure 8-98, "Choose View Verification Reports."
For information within the Verification Reports, first see the generic report fields and their explanations in Chapter 12, "Reports Overview." Additionally, verification reports have unique information in the following sections:
The result of choosing View Verification Reports is like the example in Figure 8-99, "Example of Verify Collect Latest Summary."
This first report provides a summary of the latest connectivity and collection information for all targets. Each row provides a count of how many targets had the listed status for the listed attribute. This report provides a quick way to determine whether there are problems with connections. The columns indicate the following:
As shown in Figure 8-99, "Example of Verify Collect Latest Summary," the bottom task bar includes the following buttons, which when clicked provide new reports:
|
Note The All Attributes button shows on the bottom task bar from the Network Summary report. |
Click the Network Summary button to get this report. It provides the same information as in Figure 8-99, "Example of Verify Collect Latest Summary." However, the information is broken down by network and an additional column Network is added, as shown in Figure 8-100, "Example of Verify Collect Latest Network Summary."
Click the Connectivity button to get this report. It provides detailed connectivity information for each target, as shown in Figure 8-101, "Example of Verify Collect Latest Connectivity."
The purpose of this report is to show any connectivity problems encountered during collections. The first three columns identify a target and the remaining columns provide the connectivity status for the target. This report can be used, for example, to identify any invalid password problems encountered during collections.
The columns indicate the following:
Click the Collections button to get this report, as shown in Figure 8-102, "Example of Verify Collect Latest Collections."
This report does not contain data in this release.
The columns indicate the following:
Click the All Attributes button to get this report, as shown in Figure 8-103, "Example of Verify Collect Latest Attributes."
The columns indicate the following:
Posted: Thu Apr 20 16:31:42 PDT 2000
Copyright 1989 - 2000©Cisco Systems Inc.