|
|
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:
The TrafficDirector application can use network statistics to create long-term trend reports with the Trend Reporter application. To do so, you must set up one or more SQL servers to log to a SQL database.
An embedded SQL database is bundled with the TrafficDirector application 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 the TrafficDirector software is installed.
The TrafficDirector application 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 have the central site gather the reporting information from each remote site and compile reports globally.
To properly set up the SQL server environment to log TrafficDirector data, you must perform these major tasks:
Step 2 Identify the desired aging and utilization parameters to determine how long historical data is maintained in the SQL database. You use the Configure Rollup application to do this. See the section "Logging and Aging Data for Reporting" in the chapter "Configuring SQL Servers for Reporting" in Using the TrafficDirector Application for more information.
Step 3 Associate the SQL servers with the appropriate agent definition. You use the Configuration Manager application to do this. See the chapter "Using Configuration Manager" in Using the TrafficDirector Application for more information.
The Configure Servers application lets you define the address and access information that the TrafficDirector application requires to either write to or read from an SQL database.
Although each copy of the TrafficDirector application writes only to a single SQL server, you can use this application to configure the TrafficDirector application to read from multiple SQL servers.
You use Configure Servers to designate read-only servers for distributed reporting. The TrafficDirector application 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."
 |
Note You do not need to create a logging server during the TrafficDirector installation. The logging server automatically becomes the same system where the TrafficDirector application resides. |
Although the TrafficDirector application 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.
To configure read-only SQL servers to read data and generate reports, follow these steps:
The Configure SQL Servers window is displayed.
Step 2 Select Edit > New.
The Add Server Entry window is displayed.
Step 3 Enter the following information in the Add Server Entry window:
|
Note This name is used only by the TrafficDirector application and does not need to match the network name defined for the server. |
Step 4 To accept the server configuration and add the SQL server to the TrafficDirector configuration files, click OK.
After you define the SQL server as part of the TrafficDirector installation process, and established utilization and aging parameters for logging, you must associate the appropriate server with each agent installed in the TrafficDirector application.
To associate the server with each agent, follow these steps:
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 correct SQL server definition is assigned to the agent.
Step 8 If necessary, repeat Steps 3 through 7 for each agent.
You may sometimes 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:
To edit a server definition, follow these steps:
Step 2 Select the SQL server entry you want to edit.
Step 3 Select Edit > Edit.
The Edit Server Entry window is displayed.
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.
To delete a SQL server definition, follow these steps:
Step 2 Select the SQL server entry you want to delete.
Step 3 Select Edit > Delete.
The TrafficDirector software deletes the SQL server configuration and removes it from the Configure SQL Servers main window.
Posted: Mon Jun 5 09:40:48 PDT 2000
Copyright 1989 - 2000©Cisco Systems Inc.