Configuring Frame Relay Agents

Adding Frame Relay Agents

Editing Frame Relay Agents

Deleting Frame Relay Agents

Editing DLCIs

Configuring Frame Relay Agents

The chapter describes how to configure Frame Relay agents. The following sections contain more information:

Adding Frame Relay Agents

To add a Frame Relay agent, follow these steps:

Step 1 Start Configuration Manager, if you have not already done so.

(For more information about Configuration Manager, see Chapter 3, "Using Configuration Manager.")

Step 2 Click the FrameRelay radio button.

Step 3 Click Add.

The Add Frame Relay Agent window opens.

Step 4 Enter the information in the following appropriate fields:

Agent Name

Name of the agent. Can be up to 15 alphanumeric characters and is case sensitive. You can use dashes and underscores. On Windows NT, the first eight characters of the agent name must be unique.

IP Address

Valid IP address for the agent. Must consist of numbers separated by decimal points.

Interface

Number of the interface you want to monitor. The default is 1. WAN and high-speed interfaces are always 3 or above.

Network

Topology that the specified interface is monitoring.

Description

Description of agent. Use up to 30 characters.

Read Community

Read community string for the agent. The default is public.

Retries

Number of times the TrafficDirector application tries to reach the agent if it gets no response. The value must be an integer and be equal to 1 or greater. The default is 2.

Write Community

Write community string for the agent. The default is public.

Timeout

Length of time (in seconds) that the TrafficDirector application waits before retrying an SNMP request. The value must be an integer and be greater than or equal to 1. The default is five seconds.

Startup File

Name of a startup file. This is a script that reinstalls both the shared and custom properties files defined for the agent if the agent reboots. To reinstall the properties files on an agent, the startup script must contain a line that runs the dvcfg command-line utility against the selected agent. For example:

dvcfg agent_name
or
dvcfg $1

Properties File

Shared properties file that contains the configuration you want to install on the agent. The default shared properties file is "default," which matches the default monitoring configuration the probe device boots up with.

SQL Server

SQL server logging the agent. On Windows, this is the SQL server to which the TrafficDirector application polling the agent is logging data. There is no default value on Windows, because all SQL servers must be defined using the TrafficDirector Configure SQL Servers application, even if the SQL server resides on the same station as the TrafficDirector application that is logging the agent.

Agent Name	Name of the agent. Can be up to 15 alphanumeric characters and is case sensitive. You can use dashes and underscores. On Windows NT, the first eight characters of the agent name must be unique.
IP Address	Valid IP address for the agent. Must consist of numbers separated by decimal points.
Interface	Number of the interface you want to monitor. The default is 1. WAN and high-speed interfaces are always 3 or above.
Network	Topology that the specified interface is monitoring.
Description	Description of agent. Use up to 30 characters.
Read Community	Read community string for the agent. The default is public.
Retries	Number of times the TrafficDirector application tries to reach the agent if it gets no response. The value must be an integer and be equal to 1 or greater. The default is 2.
Write Community	Write community string for the agent. The default is public.
Timeout	Length of time (in seconds) that the TrafficDirector application waits before retrying an SNMP request. The value must be an integer and be greater than or equal to 1. The default is five seconds.
Startup File	Name of a startup file. This is a script that reinstalls both the shared and custom properties files defined for the agent if the agent reboots. To reinstall the properties files on an agent, the startup script must contain a line that runs the dvcfg command-line utility against the selected agent. For example: dvcfg agent_name or dvcfg $1
Properties File	Shared properties file that contains the configuration you want to install on the agent. The default shared properties file is "default," which matches the default monitoring configuration the probe device boots up with.
SQL Server	SQL server logging the agent. On Windows, this is the SQL server to which the TrafficDirector application polling the agent is logging data. There is no default value on Windows, because all SQL servers must be defined using the TrafficDirector Configure SQL Servers application, even if the SQL server resides on the same station as the TrafficDirector application that is logging the agent.

Step 5 Do one of the following:

Click OK to add the agent and return to the Configuration Manager main window.
Click Apply to add the new Frame Relay agent without exiting the Add Frame Relay Agent window.
Click Cancel to quit and return to the Configuration Manager main window without adding the agent.

: If you clicked OK or Apply, the name of the newly added Frame Relay agent is displayed in the Configuration Manager main window. Any DLCIs discovered by the new Frame Relay interface are displayed in the bottom left list box.

Step 6 Click Test to confirm that the new agent can be reached.

For more information, see Chapter 2 "Testing the Operational Status of an Agent."

Editing Frame Relay Agents

When you have added a Frame Relay agent to the TrafficDirector application, you can edit it at any time and change any of the parameters you specified when you added the agent. For example, you might want to change the timeout or retry times of an agent to meet changing network conditions or monitoring requirements.

Note You cannot rename an existing Frame Relay agent; this is the only parameter you cannot modify. To work around this, use the Edit Frame Relay window to create a new Frame Relay agent with the same parameters and the name you want, then delete the original agent.

Step 1 Start Configuration Manager, if you have not already done so.

(For more information about Configuration Manager, see Chapter 3, "Using Configuration Manager.")

Step 2 Click the FrameRelay radio button.

Step 3 Click Edit.

The Edit FrameRelay window opens. This window is the same as the Add Frame Relay Agent window, except that the fields are already filled in.

Step 4 Edit the fields.

For more information, see "Adding Frame Relay Agents."

Step 5 Click OK to replace the original Frame Relay agent with the modified agent, or click Cancel to return to the Configuration Manager main window without modifying the agent.

Step 6 Select the Frame Relay agent you just modified.

Step 7 Click Test to see if it can be reached.

For more information, see Chapter 2 "Testing the Operational Status of an Agent."

Deleting Frame Relay Agents

As your network monitoring requirements change, you might not need to monitor a certain network segment and you might want to delete the Frame Relay agent from the TrafficDirector application. When you delete an agent, the actual agent remains connected to the network segment and continues to gather information, but the TrafficDirector application can no longer monitor the data it collects.

To delete a Frame Relay agent, follow these steps:

Step 1 Start Configuration Manager, if you have not already done so.

(For more information about Configuration Manager, see Chapter 3, "Using Configuration Manager.")

Step 2 Click the FrameRelay radio button.

Step 3 Select the Frame Relay agent you want to delete from the Agents list box.

Step 4 Click Delete.

Step 5 Click Yes to delete the agent, or click No to return to the Configuration Manager main window without deleting the agent.

Editing DLCIs

For each DLCI you are monitoring on a Frame Relay interface, you can assign a name and download new committed information rate (CIR) values to the agent. The name you assign to a DLCI is displayed in all TrafficDirector DLCI monitoring displays (for example, Traffic Monitor and All Talkers). The default DLCI name is DLCI-number. The CIR values that you specify are downloaded and configured in the agent when you click Download.

To edit DLCIs, follow these steps:

Step 1 Start Configuration Manager, if you have not already done so.

(For more information about Configuration Manager, see Chapter 3, "Using Configuration Manager.")

Step 2 Click the FrameRelay radio button.

A list of Frame Relay agents is displayed in the Agents list box.

Step 3 Select the Frame Relay agent for which you want to edit DLCIs.

Step 4 Click Learn to learn DLCIs on the selected Frame Relay agent.

A list of all discovered DLCIs is displayed in the DLCI list box.

Step 5 Select the DLCI you want to edit.

Step 6 Click Edit (to the right of the DLCI list box).

The Edit DLCI window opens.

Step 7 Enter the following information in the DLCI window:

DLCI Name---The name you want to assign to the DLCI number. Can be up to 15 alphanumeric characters and is case sensitive.
CIR DTE---The CIR of the DTE circuit.
CIR DCE---The CIR of the DCE circuit.

Step 8 Click OK to accept the new DLCI configuration and map the name you specified to the selected DLCI.

Step 9 Go to Step 9, or click Cancel to close the Edit DLCI window without saving the new DLCI configuration.

The new CIR configuration is not downloaded to the agent until you click Download.

Step 10 Select the Frame Relay agent you are working with from the agents list box.

Step 11 Click Download.

The TrafficDirector application downloads the new CIR values (specified in Step 7) to the selected agent.

Table of Contents