EJECUCIÓN DE LAS EVALUACIONES DE AUDITORÍA EXTERNA

CAS can accept data from different sources, including Cisco NAM. However, NAM is not a DCRUM component, so CAS must be configured to work with NAM and to know how to interpret the data.

Before You Begin

You should familiarize yourself with issues related to time synchronization and performance as described in Special Considerations for Using NAM in Data Center Real User Monitoring

[p. 28]. An understanding of these concepts will enable you to choose appropriate values for the corresponding configuration parameters.

You need to have administrative rights to perform configuration steps on the CAS. A set of properties must be tuned to acquire meaningful results in the reports. These properties are accessed on the User properties screen. To access User properties, type:

http://CAS_server/userpropertiesadmin

in the Web browser's Address bar and press [Enter]. The User properties screen enables you to view and modify a large number of report server settings. Select the required setting, enter the required value, and click Set value.

To configure CAS to receive data from NAM:

1. Optional: Configure the length of the interval at which CAS will interrogate NAM appliances.

Choosing a value:

• Use the default value of 150 seconds (2.5 minutes) if the NAM report interval is set to 5 minutes, as it normally would be in situations where it is supplying data to CAS and there is no danger of data duplication.

• To reduce jitter in reported data, the length of the interval at which CAS interrogates NAM should fit two or more times within the length of the report interval used by CAS.

• For information on how to check or modify the value of the NAM report interval, see

Configuring NAM 5 [p. 33].

• For a discussion on advisable report interval values, see Special Considerations for Using NAM in Data Center Real User Monitoring [p. 28].

The corresponding configuration parameter (NAM_GET_FILE_PERIOD) can be accessed in

CAS on the User properties screen.

2. Optional: Configure CAS monitoring interval. Choosing a value:

• If CAS is also receiving data from one or more AMD devices, the interval at which it will generate its data records will be taken from the AMDs.

• If only NAM appliances are connected, however, you may need to explicitly set the length of the interval or leave it at the default value of 5 minutes.

The corresponding configuration parameter (NAM_ZDATA_PERIOD) can also be modified on the User properties screen.

3. Optional: Enable AMD and NAM traffic deduplication. Choosing a value:

• If AMD and Cisco NAM monitor the same traffic and the same CAS receives data for software services from these devices, the mechanism for deduplication built in to the report server can be enabled.

• Use NAM_AMD_DEDUPLICATION_VALID_TIME, which you can access on the User

properties screen. This property sets the number of minutes for which the report server

will retain a record of those software service sessions that have been reported by AMDs. During this time, matching sessions reported by Cisco NAM devices will be marked as duplicate and discarded.

You should set this feature to three times the size of the monitoring interval (in minutes). A value of zero disables the deduplication mechanism. You must restart the server to put your changes into effect.

4. Optional: Synchronize DCRUM service names with NAM application names.

If the same traffic is monitored by AMD devices and NAMs, to avoid data duplication you should ensure that the service names defined for the AMDs are the same as the application names used by NAMs.

The software services and NAM application mapping is configurable by

NAM_APPLICATION_MAPPING property on the User properties screen.

By default, mapping is turned off. The property has three values:

off

No mapping is effective, NAM application and software service names are mixed and duplication can occur when AMD and NAM monitor the same traffic.

cisco-to-cpwr

NAM application names take precedence and all software service names will be given NAM application names as defined in the mapping file.

cpwr-to-cisco

Software service names take precedence and all NAM application names will be renamed to software service names as defined in the mapping file.

You must restart the report server to put your changes into effect.

To synchronize application names reported by NAM appliances and software service names monitored by AMDs, the CAS uses a configuration file stored on the report server's hard disk in the config directory (for example: <install_dir>\config). The

cisco-application-map.properties file contains a mapping of NAM application

names to software service names. Each line is a pair of the form:

cisco\u0020app\u0020name=compuware software service name

where the spaces on the left side of the equation must be replaced by the string “\u0020”. The strings are not case sensitive.

You do not need to restart server after changing this file.

Example 1. Sample NAM application names to software service names mapping Cisco=Compuware

Cisco\u0020name=Compuware name

For information on how to define service names on DCRUM, see Basic Monitoring Configuration in the Data Center Real User Monitoring Web Application Monitoring User Guide.

Attaching Cisco Network Analysis Module to RUM