You may need to quickly determine if an agent--common agent, switch, or Frame Relay agent--is operational. You can easily test any agent added to TrafficDirector by using the Test Agent utility in the TrafficDirector main window. To check the status of an agent, take the following steps:
Step 1 Select the Agent or Frame Relay radio button, depending on the type of agent you want to test.
Step 2 Select the agent, switch, or Frame Relay agent that you want to test from the TrafficDirector main window agent list box.
Step 3 Click the Test Agent icon.
Step 4 The Agent Test window opens (Figure 16-1). The agent is operational and the Agent Test window lists general, interface, and system information for the agent.
If the agent is not operational, the information in the dialog box indicates whether the agent can be reached, and if so, whether the read community string, the write community string, or both has failed (Figure 16-2).
Step 5 Click OK when you have read the information.
Figure 16-1: Agent Test Window
Figure 16-2: Agent Test Window (Failed to Communicate Message)
The following information is displayed in the Agent Test window:
| IP Address
| The IP address of the agent's management interface.
|
| Ping
| As part of the agent test, TrafficDirector pings the agent to make sure it is accessible and active on the network. This field displays the ping result: Passed or Failed.
|
| Read Community
| The SNMP read community string for the agent.
|
| Write Community
| The SNMP write community string for the agent.
|
| Protocol Monitoring
| Whether the agent supports RMON2 application-layer protocol monitoring.
|
| Resource Monitoring
| Whether the Resource Monitor option is enabled for the agent. This option is required if you want to configure round-trip delays and proxy SNMP gets (pings). This option is for SwitchProbes only.
|
| Interface Number
| The number of the management interface for the agent.
|
| Description
| The media type.
|
| Interface Type
| The type of interface distinguished according to the physical link protocol described in RFC 1213.
|
| Physical Address
| The MAC address of the agent.
|
| Number of Interfaces
| The number of network interfaces on the agent.
|
| Net Speed
| An estimate of the current bandwidth of the interface, in bytes per second.
|
| DTE Speed
| An estimate of the DTE circuit speed, in bits per second. (For full duplex links only.)
|
| DCE Speed
| An estimate of the DCE circuit speed, in bits per second. (For full duplex links only.)
|
| Description
| The device model, as defined by the network administrator.
|
| Contact
| The name of the network administrator responsible for the agent and a contact point.
|
| SysName
| The agent name, as assigned by the network administrator.
|
| Location
| The physical location of the agent, as described by the network administrator.
|
| UpSince
| The date and time the agent became operational on the network. This also indicates when the agent was last booted.
|
You should routinely test any new or modified switch before you use it. To test a switch, take the following steps.
Step 1 Select the Switch radio button in the TrafficDirector main window.
Step 2 Select the switch you want to test from the Switch list box.
Step 3 Click the Test Agent icon.
Step 4 If the switch is operational, the Switch Test window opens (Figure 16-3). If the switch is not operational, the information in the Switch Test window confirms whether the switch can be reached, and if so, whether the read, write, or both community strings have failed.
Figure 16-3: Switch Test Window
Step 5 Click OK when you have finished viewing the information.
The following information is displayed in the Switch Test window for the switch:.
| IP Address
| The IP address of the management interface for the switch.
|
| Ping
| As part of the switch test, TrafficDirector pings the switch to make sure it is accessible and active on the network. This field displays the ping result: Passed or Failed.
|
| Read Community
| The SNMP read community string for the switch.
|
| Write Community
| The SNMP write community string for the switch.
|
| Description
| The device model, as defined by the network administrator.
|
| Contact
| The name of the network administrator responsible for the switch and a contact point.
|
| SysName
| The switch name, as assigned by the network administrator.
|
| Location
| The physical location of the switch, as described by the network administrator.
|
| UpSince
| The date and time that the switch became operational on the network. This also indicates when the switch was last booted.
|
| Roving Agent
| The name of the roving agent defined for the switch, if any.
|
| Analyzer Port
| The number of the switch port that the roving agent is physically connected to, if any.
|
| Monitor Port
| This port currently being roved, if applicable. The monitor port is the switch port that the roving agent is currently monitoring.
|
