|
|
TrafficDirector has a utility called Trend Reporter. In order to utilize this utility, an SQL server version 6.0 or above must be installed and configured to work in conjunction with TrafficDirector. Installing this utility requires configurations on the NT server side including creating the SQL device, adding the appropriate database, and adding users with correct permissions.
This chapter covers step by step configuration of the SQL server as needed to work with Trend Reporter, the SQL client, and steps needed to begin generating reports.
To set server and client network options, take these steps:
Step 1 Go to the SQL program group and select SQL Setup.
Step 2 Click on the Change Network Support box. Make sure that only TCP/IP sockets is checked.
By default Named Pipes will be checked.
Step 3 Go to the SQL program group and select SQL Client Configuration Utility.
Step 4 Click on the Net Library tab.
Step 5 Change the Default Network from Named Pipes to TCP/IP Sockets.
Step 6 Click on the Advanced tab and type the server name.
Step 7 Change DLL name to TCP/IP sockets.
Step 8 Next to the connection string, click on Locate.
A list of three DLLs pops up.
Step 9 Select dbmssocn.
Step 10 Click Done.
Step 11 Click Add/Modify.
Step 12 Click Done to close window.
To register the SQL server, take these steps:
Step 1 Launch the SQL Enterprise Manager from the SQL Server Program group.
Step 2 Click Server from the top menu bar and click Register Server.
Step 3 In the Server field, either type the server name or select it from the pull-down menu.
This name should be the name of the NT server.
Step 4 Make sure Use Standard Security is checked. The Login ID will be sa. Do not use a password.
Step 5 Click Register.
You should now get a green light next to the server name in the Enterprise Manager window. If you get an error, the server does not exist. Go to the SQL Server Program group and select Service Manager. Both MSSQLserver and SQLExecutive processes should be started.
Step 6 Try stopping both and restarting both processes and try registering the server again.
To create the database, take these steps:
Step 1 Click the SQL Enterprise Manager icon.
Step 2 Click Manage from menu bar and select Database Devices.
The Manage Database Devices window opens.
Step 3 Click the icon in the upper left of the window.
This allows you to create new database device.
Step 4 Name this device NETSQL and give it a size of about 300 MB.
This example database size is based on six agents with one RMON domain with default aging. Actual size will vary based on how many domains and agents will be polled. You can change the size of the device at any time.
Step 5 Click Create Now.
NETSQL displays in the bar graph.
Step 6 Close this window.
Step 7 Select Manage from the menu bar, then select Databases.
Step 8 Click the icon in the upper left of screen.
This allows you to create a new database which will be part of the new database device NETSQL that you created.
Step 9 Name this Database NSTREND_DB.
The size of this database cannot be greater than that of the database device.
Step 10 Select Create Now.
Step 11 Close the window.
Step 12 Go to the Server Manager window and click on Server Name.
This should show a tree structure of everything you have installed.
Step 13 Click on Databases then click on NSTREND_DB.
Step 14 Select Manage from menu bar and select Groups.
Step 15 Create a user group called NETSQLUSERS.
This will be associated with NSTREND_DB.
Step 16 Add the individual user who perform the reporting.
Make sure Permit is checked along with the default, correct user name. Also, select netsqlusers under Group and not Public, which is the default.
Step 17 Highlight NSTREND_DB and select Manage from top menu bar then select Databases.
Step 18 Click the middle icon in the upper left of the screen to edit.
Step 19 Select the Options tab and click Truncate Log on Checkpoint.
This will save space for data in the database.
Step 20 Select the Permissions tab and give both Netsqlusers and the user you created All permissions.
To install the client, take these steps:
Step 1 Insert the SQL Server CD in the drive where you plan to install TrafficDirector.
Step 2 Run SETSUP.EXE in the i386 directory.
Step 3 Under Setup Options, choose Utilities Only.
Once this is installed, an ISQL/w icon is created.
Step 4 Click on the ISQL/w icon from the SQL Server Program Group and enter the SQL Server IP address, and the user name and password for the user you just created on the server.
Step 5 Select Connect.
Step 6 An SQL query box opens.
Step 7 Minimize this utility.
You must stay connected when you install TrafficDirector on this machine.
To install TrafficDirector, take these steps:
Step 1 Click Admin in the upper right of the NSM window.
Step 2 Click on New.
Step 3 Enter the SQL Server Name, IP address of the server, user name that you created under NETSQLUSERS, and a password for the user.
By default, the password displays as multiple asterisks. Backspace over these to enter an appropriate password.
Step 4 Now enter Y or N for logging server.
Step 5 Select OK.
Information is written to a file called nsserv.srv in the /NSHOME/usr directory
Step 6 Edit each agent for which you will be logging to the database.
Use Config Manager to edit the agent. At the bottom of the Edit Agent window there is a field to specify the SQL server. Select the button next to this entry and select the server name from the earlier step.
Step 7 Select OK to modify.
Step 8 Create pollers for each agent you modified in the earlier step. Use Config Manager to highlight the agent and select Properties.
Step 9 Select Add and enable the appropriate groups and polling for that probe.
Step 10 Select OK and return to the Config Manager window.
Step 11 Select Install to update the agent with the new information.
You should see the logging daemons come up minimized in the task bar below.
Now that you have set up polling against an agent and domain, the tables will start to be built in the SQL database. To modify object permissions so you can read information, take these steps:
Step 1 Go back to the SQL Server and display the Server Manager window.
Step 2 Move down the directory structure until you see NSTREND_DB.
Step 3 With NSTREND_DB highlighted, click on Object from the menu bar at the top and click on Permissions.
Step 4 Click on the By Object tab.
A list of objects created when you set up polling displays. In the box underneath, the group NETSQLUSERS should be present along with the user created in this group.
Step 5 For each object, grant All permissions to NETSQLUSERS and to the user.
Step 6 Select Set to give group and user permission to the object.
Now that object permissions are successfully granted, you should be able to perform reporting through Trend Reporter. Based on a minimum polling of one minute for statistics and protocol in the poller, you can get the first report after about 15 minutes. If polling is set higher, you must wait until the first sample is created.
If the poller is configured properly and we are attached to the SQL server, the following daemons should come up upon launching TrafficDirector: IP Ping snapshot daemon, Master snapshot daemon, and extraction daemon. These daemons must be running properly in order for the reporting functionality to work. If you are attached to the SQL server, polling is set up, and either of these daemons do not come up, try following:
Step 1 Shut down all daemons and close TrafficDirector.
Step 2 Go to the NSHOME/usr directory and delete all .ctl and .log files.
.ctl files are control files which keep track of daemon processes. It is possible that.ctl file information does not get removed when TrafficDirector is brought down, therefore next time you bring up TrafficDirector, it thinks the daemons are already running.
Step 3 Bring up TrafficDirector and all daemons should be operational.
|
|