Guest

Cisco TrafficDirector

Product Installation Guide (No title available)

 Feedback

Table of Contents

This appendix describes how to set up SQL databases as a repository of network statistics to be used in reports, and contains the following information:

TrafficDirector can use network statistics to create long-term trend reports with the Trend Reporter application. To do this, you must set up one or more SQL servers to log to a SQL database.

An embedded SQL database is bundled with TrafficDirector that you can use on HP-UX and AIX platforms. You have many options for configuring the database. All logged data is stored on the same system as the one on which TrafficDirector is installed.

Options for Collecting Statistics

TrafficDirector supports a distributed database architecture so you can track statistics from multiple sites. You can define multiple network management stations to monitor your network locally, then collect the information from these stations into one centralized SQL database.

By setting up the logging mechanism to perform most agent polling locally, you can avoid excessive traffic to and from the central SQL database.

You can also configure your environment so each local site generates reports based on the data gathered locally, or so the central site gathers the reporting information from each remote site and compiles reports globally.

To properly set up the SQL server environment to log TrafficDirector data:


Step 1   Use the Configure SQL Servers application to define any read-only servers from which to obtain statistics for the logging server.

See the "Configuring SQL Servers for Reporting" chapter of Using the TrafficDirector Application for detailed information.

Step 2   Use the Configure Rollup application to identify the desired aging and utilization parameters to determine how long historical data is maintained in the SQL database.

For more information, see the section "Logging and Aging Data for Reporting" in the "Configuring SQL Servers for Reporting" chapter of Using the TrafficDirector Application.

Step 3   Use the Configuration Manager application to associate the SQL servers with the appropriate agent definition.

See the "Using Configuration Manager" chapter of Using the TrafficDirector Application.


Defining SQL Servers to TrafficDirector

You use the Configure Servers application to define the address and access information that TrafficDirector requires to write to or read from a SQL database.

Although each copy of TrafficDirector writes only to a single SQL server, you can use this application to configure TrafficDirector to read from multiple SQL servers.

Use Configure Servers to designate read-only servers for distributed reporting. TrafficDirector can write only to one SQL Server database; however, it can read data from multiple databases for distributed reporting. You also use Configure Servers to define this information. See the next section, "Defining Read-Only Servers."

Defining Read-Only Servers


Note   You do not need to create a logging server during TrafficDirector installation. The logging server automatically becomes the same system where TrafficDirector resides.

Although TrafficDirector can only write report data to one SQL Server as the logging server, the distributed reporting feature allows it to read data from multiple SQL servers to generate trend reports.


Step 1   Click the Config Servers icon in the Admin level of TrafficDirector.

The Configure SQL Servers window opens.

Step 2   Select Edit > New.

The Add Server Entry window opens.

Step 3   Enter the following information in the Add Server Entry window:

Field Description

Server Name

The name you want to define the SQL server, up to a maximum of 15 alphanumeric, case-sensitive characters. You can use hyphens and underscores in the name.

Note This name is used only by TrafficDirector and does not need to match the network name defined for the server.

IP Address

The IP address of the distributed database (created by another instance of TrafficDirector) from which you want TrafficDirector to read data.

TCP Port

The TCP port that the SQL daemon running on the remote server uses to communicate with the SQL database. The default port is 3000, and is defined in the .traffdir.cshrc or .traffdir.sh file.
The port number must match the msqld TCP port defined in
the .traffdir.cshrc or .traffdir.sh file of the network management station logging to the database.



Step 4   To accept the server configuration and add the SQL server to the TrafficDirector configuration files, click OK.


Associating SQL Servers with Agents

After you define the SQL server as part of TrafficDirector installation process and establish utilization and aging parameters for logging, you must associate the appropriate server with each agent installed in TrafficDirector.


Step 1   From TrafficDirector main window, click the Admin button.

Step 2   Click the Config Manager icon.

Step 3   Select an agent.

Step 4   Click Edit.

Step 5   Click the SQL Server list box.

Step 6   Select the appropriate server for the agent.

Step 7   Click OK twice.

The SQL server definition is assigned to the agent.

Step 8   If necessary, repeat Steps 3 through 7 for each agent.


Maintaining SQL Server Definitions

You might need to edit a SQL server definition or delete a definition that is no longer needed. If so, you can change the TCP port assignment if the msqld port changes on the remote network management station.

You can either edit or delete the SQL server definitions as outlined in the following sections:

Editing Server Definitions


Step 1   Click the Config Servers icon in the Admin level of TrafficDirector.

Step 2   Select the SQL server entry you want to edit.

Step 3   Select Edit > Edit.

The Edit Server Entry window opens.

Step 4   Change any of the parameters for the selected SQL server entry.

Step 5   To accept the server definition and add the SQL server to the TrafficDirector configuration files with the new changes, click OK.


Deleting Server Definitions


Step 1   Click the Config Servers icon in the Admin level of TrafficDirector.

Step 2   Select the SQL server entry you want to delete.

Step 3   Select Edit > Delete.

TrafficDirector deletes the SQL server configuration and removes it from the Configure SQL Servers main window.