|
|
The TrafficDirector application cannot communicate with SwitchProbe devices, Network Analysis Modules, or switches until you have added specific information about them using the Configuration Manager application.
The following sections contain more information about using Configuration Manager to perform those tasks:
Before the TrafficDirector application can communicate with a switch, it must know:
Before the TrafficDirector application can communicate with a SwitchProbe device, it must know:
Configuration Manager supports the following basic types of configurations:
For information about defining a SwitchProbe device as an agent in Configuration Manager, see "Adding an Agent Definition."
Configuration Manager provides an efficient way to install properties, thresholds, and resources on a variety of agents including data-link connection identifiers (DLCIs) and switch ports.
You first define all agent configuration in properties files that you create using the Property Editor application (see Chapter 6, "Working with Properties."). These files contain the monitoring configuration, or properties, you want to configure in the agent. You then use Configuration Manager to install these properties on selected agents.
To start Configuration Manager, follow these steps:
Step 1 Click the Admin radio button in the TrafficDirector main window.
Step 2 Click the Config Manager icon in the Admin level window.
The Configuration Manager window opens (Figure 3-1).
The Configuration Manager main window is divided into two panels.
For the TrafficDirector application to communicate with a SwitchProbe device, specific information about the device must exist in Configuration Manager. For example, for the TrafficDirector console to communicate with a SwitchProbe device, it would need:
Configuration Manager provides three radio buttons for SwitchProbe-related configurations:
Configuration Manager identifies all SwitchProbe devices that monitor network segments as agents. The term agent refers to the agent software in the SwitchProbe device, which the TrafficDirector console uses to communicate with a SwitchProbe device.
The following sections contain more information:
The following three configuration processes are involved in successfully defining a SwitchProbe device or switch using Configuration Manager:
1. Adding (creating) the SwitchProbe definition---This process involves:
(a) Selecting one of two radio buttons (Agent or Frame Relay) to identify the type of SwitchProbe device being defined.
(b) Assigning an agent name and specifying other information pertinent to locating the SwitchProbe device on the network.
If the device you are defining in Configuration Manager supports virtual interfaces such as, Virtual Circuits, DLCIs, or Virtual LANs, the TrafficDirector application automatically detects these interfaces immediately after you define the device as an agent in Configuration Manager. See Appendix A, "Troubleshooting" for more information.
2. Pinging the SwitchProbe location (testing)---After you have defined the SwitchProbe device as an agent in Configuration Manager, you should verify that the TrafficDirector console can communicate with this agent. This process involves selecting the agent name and clicking Test on the Configuration Manager window. If the test is successful, a successful test agent dialog box opens. If the test is unsuccessful, an unsuccessful test agent dialog box opens. See Appendix A, "Troubleshooting" for more information about troubleshooting and testing agents.
3. Installing the default properties file---A properties file is installed after you have defined the SwitchProbe device as an agent in Configuration Manager. The properties file installed on a device with multiple interfaces applies to all interfaces on that device. This process involves selecting the agent name on the Configuration Manager window and clicking Install. The TrafficDirector application installs a default properties file to the selected SwitchProbe device. This default properties file identifies the network domains that the SwitchProbe device monitors. You can change this file later or create a new file and apply it to the device. For more information about editing or creating properties files, see Chapter 6, "Working with Properties."
The procedures for adding a SwitchProbe definition (including installing the default properties file and testing whether the TrafficDirector application can communicate with the device), are described in "Adding an Agent Definition."
Before you begin using Configuration Manager, verify that you have the following information about each SwitchProbe device you want to define in Configuration Manager:
There are special configuration options you must consider when configuring the TrafficDirector application to communicate with SwitchProbe devices configured with multiple interfaces. In most cases, you can configure the physical and special interfaces associated with a SwitchProbe device as individual agents.
By configuring these types of interfaces as individual agents, you enable the TrafficDirector application to individually monitor the traffic associated with each interface. Physical interfaces on the SwitchProbe device refer to ports 1-16, which you can physically locate on the back panel of the device.
Special interfaces refer to software options embedded or enabled in the SwitchProbe device, such as NetFlow and FEC. Special interfaces can range from 49 to 64.
The following procedure describes how to define a SwitchProbe device as an agent in Configuration Manager. This procedure addresses:
To add the agent, follow these steps:
Step 1 From the Configuration Manager main window, select one of the following:
Step 2 Click Add.
The Add Agent or Add Frame Relay Agent window opens.
Step 3 In the Agent Name text box, type a name for the SwitchProbe device you are defining.
You can specify up to 15 alphanumeric characters.
Step 4 In the IP Address text box, enter the agent IP Address.
Step 5 At the Interface text box, do the following:
(a) In the Interface text box, specify the interface number of the monitor interface that is configured on the SwitchProbe device to manage the activity on a network segment. For Frame Relay WAN devices, the default is 3; for most other devices, the default is 1.
For more information about interfaces, see the Cisco SwitchProbe Installation and Configuration Guide.
(b) If the View button (next to the Interface text box) is enabled, click View to view and learn the list of physical interfaces (ports 1-16) and special interfaces (49-64) configured on the SwitchProbe device.
The View Interfaces dialog box opens, listing the physical and special interfaces configured on the SwitchProbe device (Figure 3-4).
Step 6 In the View Interface dialog box, do one of the following:
Step 7 In the Network drop down box (on the Add Agent dialog box), select the network topology supported on this SwitchProbe device: Frame Relay, Ethernet, Token Ring, FDDI, WAN, Fast Ethernet-FDX, Fast Ethernet-HDX, or ATM-FDX. (Use the interface type you selected in Step 5.)
Step 8 (Optional.) In the Description text box, specify a description (up to 30 characters) about this SwitchProbe configuration.
Step 9 In the community name text boxes, do the following:
(a) Read Community ---Specify the Read Community name configured on the device.
(b) Write Community---Specify the Write Community name configured on the device.
Step 10 In the Retries and Timeout text boxes, do the following:
(a) Retries---Specify the number of times you want the TrafficDirector console to attempt to reach the SwitchProbe device if there is no response. This value must be an integer between 1 and 1000.
(a) Timeout---Specify the length of time (in seconds) you want the TrafficDirector console to wait between each retry. This value must be an integer between 1 and 1000.
Step 11 In the Startup File text box, the name of the default Startup script appears. This script reinstalls the shared and custom properties files on the SwitchProbe device whenever the device reboots.
Step 12 In the Properties File text box, the name of the default properties file appears. The properties file you specify in this text box determines the monitoring configuration used by the SwitchProbe device. If you prefer to specify another properties file other than the default properties file name, click the Browse (...) button to locate the appropriate file name. For information about using and creating properties files, see Chapter 6, "Working with Properties."
Step 13 If the SQL Server text box is enabled, specify the host name of the SQL Server that is configured to log report information for this agent.
Step 14 To add this agent definition to Configuration Manager, do one of the following:
Step 15 To test whether the TrafficDirector console can communicate with this agent, select the agent name on the Configuration Manager window and click Test. Depending on the results of the test, of two test messages appear:
For more information about understanding test results, see Appendix A, "Troubleshooting."
Step 16 If you can communicate with the agent, you must install the properties file specified in the Add Agent dialog box. To install the properties file, select the agent name on the Configuration Manager window and click Install.
To edit the parameters associated with an agent, follow these steps:
Step 1 In the Configuration Manager main window, select the agent you want to edit.
Step 2 Click Edit.
The Edit Agent window opens.
Step 3 Change the fields you want to edit.
Use the guidelines described in "Adding an Agent Definition."
Step 4 Click OK to apply the changes made, or click Cancel to return to the Configuration Manager window without applying the modifications you made.
Step 5 Test the agent to verify that the TrafficDirector console can access the SwitchProbe device associated with this agent.
For more information about interpreting test results, see Appendix A, "Troubleshooting."
Step 6 If you changed the name of the properties file in the Edit Agent dialog box, you must click Install on the Configuration Manager window to associate the Properties File with the agent.
As network monitoring requirements change, you might not need to monitor a particular network segment. You might want to delete an agent definition existing in Configuration Manager.
When you delete an agent in the TrafficDirector application, the agent definition is removed from Configuration Manager. The SwitchProbe device that was associated with that agent definition remains connected to the network segment, and continues to gather information.
To delete an agent, follow these steps:
Step 1 In the Configuration Manager window, select the name of the agent you want to delete from the Agents list box.
Step 2 Click Delete.
A pop-up message is displayed and you must confirm that you want to delete the agent.
Step 3 Click Yes to delete the agent, or click No to return to the Configuration Manager window without deleting the agent.
Table 3-1 describes those SwitchProbe models that are enabled to monitor multiple network interfaces.
| SwitchProbe Model | Supported Interfaces | Description |
|---|---|---|
Ethernet | Multiple Ports | Supports multiple physical interfaces that can monitor individual network segments. |
Fast Ethernet | VLANs | Offers a Virtual LAN software option that can be toggled on to monitor Virtual LAN interfaces existing on the network segment. Can also support a VLAN Monitor software option, required to monitor individual VLAN interfaces on the network. (This option is purchased separately and installed on the SwitchProbe device.) |
WAN | DLCI | Supports DLCI interfaces. This type of device can autodiscover DLCIs on LMI and Annex D Frame Relay segments. If the segment does not use LMI or Annex D, each DLCI must be manually configured on the device. For more information about using Configuration Manager to configure Frame Relay DLCIs, see "Configuring Virtual, Physical, and Special Interfaces in SwitchProbe Devices and the Network Analysis Module." |
ATM | PVC | Supports ATM Permanent Virtual Circuits (PVC). You must manually configure PVC interfaces on the SwitchProbe device. |
Fast EtherChannel Fast Ethernet | FEC (trunk) | Supports a Fast Ethernet Channel software option that allows the device to aggregate the traffic of four separate FEC sub-channels (each 200 Mbps) into one full-duplex trunk (800 Mbps). For more information about configuration of FEC SwitchProbe devices, see "Configuring the TrafficDirector Application to Recognize FEC Subchannels." |
Ethernet | NetFlow | Supports a NetFlow software option that enables the device to receive traffic from a NetFlow-enabled router. For more information about configuring the TrafficDirector application to recognize NetFlow interfaces, see "Configuring the TrafficDirector Application to Recognize NetFlow Interfaces." |
You can use the Remote Login application to view or edit any interface setting in a SwitchProbe device. For more information, see Chapter 4, "Using Remote Login to Configure SwitchProbe Devices."
For information about configuring interface parameters on a SwitchProbe device, see the Cisco SwitchProbe Installation and Configuration Guide.
An agent group is a logical collection of agents that you define. You can create groups of agents based on physical location, topology, or for other unique purposes that you define.
You use Configuration Manager to create new agent groups, modify groups, view group definitions, or delete groups. Depending on your requirements, an agent can belong to one or more groups, or to no groups at all.
The following sections provide more information about agent groups:
The following list identifies some of the ways you can use agents groups:
You can include any Agent or Frame Relay Agent in an agent group.
After you add an agent to an agent group, the agent definition cannot be deleted in Configuration Manager until you remove the agent name from the agent group(s).
The following sections provide more information:
To add an agent group, follow these steps:
Step 1 In the Configuration Manager window, click the Agent Group radio button.
Step 2 Click Add.
The Add Group dialog box opens (Figure 3-7).
Step 3 Enter a group name.
The name can include up to 15 unique characters, must not contain spaces, and is case-sensitive.
Step 4 In the Agent List box, select the names of the agents (including Frame Relay) that you want to include in this agent group.
Step 5 Do one of the following:
If necessary, you can edit an agent group at any time. You can add or remove agents in a group, but you cannot change the name of the agent group.
To add or remove agents in an agent group, follow these steps:
Step 1 In the Configuration Manager window, click the Agent Group radio button.
Step 2 Select the name of the agent group you want to edit in the Agent Group list box.
Step 3 Click Edit.
The Edit Group dialog box opens, listing the agents in that group.
Step 4 Edit the agent group, by:
Step 5 Click OK to update the agent group and return to the Configuration Manager window.
The agents included in the agent group are displayed in the list box in the lower left corner of the Configuration Manager window.
When an agent group is no longer useful, you can delete the group. You can redefine the same or a similar group at a later time, if needed. Agent groups are simply logical groupings. When you delete an agent group, the individual agents that were part of the group are still available, and are listed in the agent list box on the Configuration Manager window and the TrafficDirector main window.
To delete an agent group, follow these steps:
Step 1 In the Configuration Manager window, click the Agent Group radio button.
Step 2 Select the name of the agent group you want to delete in the Agent Group list box.
Step 3 Click Delete.
A confirmation message appears asking if you want to proceed with deleting the group name selected.
Step 4 Click Yes to delete the agent group, or click No to return to the Configuration Manager window without deleting the agent group.
The TrafficDirector application supports the switches listed in Table 3-2. You define all switches in Configuration Manager by using the Add Switch dialog box. Depending on the switch type and whether the switch is attached to an external SwitchProbe device, the definition between switches and the type of data monitored by the TrafficDirector application can vary.
The following sections provide more information:
The TrafficDirector application supports the following remote monitoring (RMON) levels to monitor the traffic on switches.
After you define a switch with Configuration Manager, the TrafficDirector application automatically learns and displays the ports associated with that switch. In addition, for Catalyst 5000-series switches, the TrafficDirector application learns the Network Analysis Modules, virtual local area networks (VLANs), and Fast EtherChannels (FECs) configured in the switch.
All switch interfaces learned by the TrafficDirector application are displayed in the Interface list box (lower left panel) on the Configuration Manager window. You can view the different types of interfaces configured by clicking one the three Interface radio buttons (Figure 3-8).
Before adding a switch definition in Configuration Manager, verify the following information:
Roving involves installing a Network Analysis Module or connecting a SwitchProbe device to an analyzer port on the switch, then mirroring traffic from a selected switch port to the roving agent.
When you rove a port, VLAN, or FEC, the traffic is directed to the SPAN port. The roving agent examines this traffic as if it were receiving the packets directly. Although the analyzer port is a static, physical connection to the probe device, you can use Configuration Manager to dynamically rove any switch port that mirrors traffic from that switch port to the analyzer port.
When using a SwitchProbe device, and physically connecting the roving agent to the switch, you must add the agent to the TrafficDirector application.
When using a Network Analysis Module, you do not perform configuration tasks because the TrafficDirector application automatically discovers this device.
You must rove a selected switch port, VLAN, or FEC whenever you want to do the following:
A switch supports roving when it meets the following requirements:
When the TrafficDirector application detects a problem on a port using mini-RMON, additional data is often needed to resolve the problem, including extensive data captures and network layer host and conversation lists. You can use roving to take advantage RMON2 and RMON1 beyond mini-RMON.
For example, if you are using Traffic Monitor to monitor a switch and notice an unusually high amount of traffic on port 12, you can use Configuration Manager to rove port 12, install a number of domains, and start a variety of TrafficDirector applications to find the reasons for the extra traffic.
The following section contains information about:
To rove a switch port for RMON2 and extended RMON, follow these steps:
Step 1 Start Configuration Manager, if you have not already done so.
Step 2 Click the Switch radio button.
Step 3 Select the switch you want to rove from the switch list box.
All switch ports for the selected switch are displayed in the lower switch port list box.
Step 4 Select the switch port(s) to which you want to rove.
Step 5 Click Rove ON to the right of the switch port list box.
A dialog box opens that displays the currently roved port and asks for confirmation to continue roving.
Step 6 Do one of the following:
Step 7 Do one of the following:
You define switches in Configuration Manager so the TrafficDirector application can recognize and communicate with these devices in your network.
The Add button in Configuration Manager lets you add information about a switch using the Add Switch dialog box.
The Edit button in Configuration Manager lets you edit information previously defined about a switch using the Edit Switch dialog box.
When you add information about a switch in Configuration Manager, it is important to know that you also identify the names of any external SwitchProbe devices attached to the switch.
For example, if a SwitchProbe device is attached to the analyzer port, you must select the name of the roving agent on the Add or Edit Switch dialog box. The same is true if you had any dedicated SwitchProbe devices attached to a switch, you must identify the names of these dedicated agents.
When you add a switch to the TrafficDirector application, you must specify the type of switch you want to monitor. Based on your selection, you can use RMON1 or RMON2 or to monitor the switch.
Table 3-2 lists the switch models supported by the TrafficDirector application and the RMON support for each.
| Switch Type | RMON1/RMON21 | Mini- RMON2 | Roving RMON |
|---|---|---|---|
Catalyst 12003 | X |
|
|
Catalyst 1800 |
| X | X |
Catalyst 1900 |
| X | X |
Catalyst 1912 |
| X | X |
Catalyst 1924 |
| X | X |
Catalyst 2820 |
| X | X |
Catalyst 2900 |
| X | X |
Catalyst 2908XL |
| X | X |
Catalyst 2916XL |
| X | X |
Catalyst 2924XL |
| X | X |
Catalyst 2926 |
| X | X |
Catalyst 3000 |
| X | X |
Catalyst 3100 |
| X | X |
Catalyst 3200 |
| X | X |
Catalyst 3900 |
| X4 | X |
Catalyst 3924 |
| X | X |
Catalyst 5000 | X5 | X | X |
Catalyst 5002 | X5 | X | X |
Catalyst 5500 | X5 | X | X |
Catalyst 5505 | X5 | X | X |
Catalyst 5509 | X5 | X | X |
Generic |
| X |
|
After you add the switch, you can monitor network traffic for any ports on the switch, and any roving or dedicated agents associated with that switch.
To add a new switch definition, follow these steps:
Step 1 Start Configuration Manager, if you have not already done so.
Step 2 Click the Switch radio button.
Step 3 Click Add.
The Add Switch window opens (Figure 3-9).
Step 4 In the Switch Name text box, specify a name for the switch being defined.
The name you choose can be up to 15 alphanumeric characters and is case-sensitive. Both dashes and underscores are allowed, but spaces are not. The name must be unique, which means you cannot assign this name to another switch.
Step 5 In the IP Address text box, type the switch IP address.
This must be a valid IP address and must consist of numbers separated by decimal points.
Step 6 In the Switch Type drop down list box, select the type of switch being added.
See Table 3-2 for a complete list of switches supported by the TrafficDirector application.
Step 7 In the community names text boxes, do the following:
(a) Read Community---Specify the Read community name established on the switch.
(b) Write Community---Specify the Write community name established on the switch.
Step 8 In the Retries and Timeout text boxes, do the following:
(a) Retries---Specify the number of times you want the TrafficDirector console to attempt to reach the switch if there is no response. This value must be an integer between 1 and 1000. The default is 2.
(b) Timeout---Specify the length of time (in seconds) you want the TrafficDirector console to wait between each retry. This value must be an integer between 1 and 1000. The default is 5.
Step 9 If applicable, follow these steps to identify a roving SwitchProbe device that is physically connected to the switch:
(a) Click the button to the right of the Roving text box to display the Agent List dialog box.
(b) Select the agent name (assigned to the SwitchProbe device) on the Agent List dialog box.
(c) Click OK.
(d) In the Analyzer Port text box, identify the port name physically connected to the probe.
Step 10 If applicable, follow these steps to identify a Network Analysis Module that is installed in the switch:
(a) Leave the Roving Agent and Analyzer Port fields blank.
(b) Click OK.
Step 11 If applicable, follow these steps to specify one or more dedicated agents (SwitchProbe devices) attached to a trunk or server link:
(a) Click the button to the right of the Agent1 text box to display the Agent List dialog box.
(b) Select the agent name (assigned to the SwitchProbe device) on the Agent List dialog box.
(c) Click OK.
Step 12 In the Server drop-down list box, select Trunk if the dedicated probe is monitoring a trunk link (traffic between two switches), or select Server if the dedicated SwitchProbe device is monitoring a server link (traffic seen for the server connected to a switch port).
(a) Repeat Steps (a) through (c), for each dedicated SwitchProbe device attached to the switch.
You can define a maximum of four dedicated agents (SwitchProbe devices) per switch definition.
Step 13 In the Properties File text box, you can do one of the following:
Step 14 In the SQL Server text box, select the SQL server that will log report information for the switch.
When the SQL Server and the TrafficDirector software exist on the same host, the default name of local appears. For more information about configuring an SQL Server for logging, see Chapter 31, "Configuring and Generating Reports."
Step 15 To add the switch to Configuration Manager, do one of the following:
When you add a switch to the TrafficDirector application, the following things happen:
If you need to quickly determine if a switch is operational, or whether the TrafficDirector application can read and write to the MIB content on the switch, follow these steps:
Step 1 Click the Switch radio button in Configuration Manager or the TrafficDirector main window.
Step 2 Select the name of the switch you want to test in agent list box.
Step 3 Click Test.
When you test a switch, the TrafficDirector application queries the switch and displays a message informing you of the results:
For more information about these test messages and how to troubleshoot an agent, see Appendix A, "Troubleshooting."
After you add a switch, the TrafficDirector application automatically learns the ports and other interfaces currently associated with a switch.
If these interfaces in your network change, the TrafficDirector application can learn about these changes if you select the switch name in the Configuration Manager window and click Learn.
All interfaces associated with a switch are displayed in the Configuration Manager Interface list box (lower left panel). Use the three interface buttons (Ports, VLANs, FECs) to view the interfaces associated with a switch.
To view the name of the properties file assigned to switch ports, use the View Files button next to the interface list box in the Configuration Manager window.
To view the port properties files associated with a switch, follow these steps:
Step 1 Click the Switch radio button.
Step 2 Click the Port radio button.
The ports associated with the switch is displayed in the Configuration Manager Interface list box (lower left panel).
Step 3 Click the View Files radio button.
The names of the properties files associated with each port is displayed in the last column of the interface list box.
Step 4 To view traps associated with a port properties file, select a port.
The top right panel shows the domains configured in the properties file.
The lower right panel shows the configured thresholds.
To edit a switch definition in Configuration Manager, follow these steps:
Step 1 Click the Switch radio button.
Step 2 In the switch list box, select the name of the switch that you want to edit.
Step 3 Click Edit (to the right of the switch list box).
The Edit Switch dialog box opens.
Step 4 Edit the switch, using the guidelines described in "Editing Switch Definitions."
Step 5 Click OK to save your changes, or click Cancel to close the dialog box without saving your changes.
When you remove a switch from the network, or when there is no longer a need to monitor a switch, you can remove the switch definition in Configuration Manager.
To remove a switch definition, follow these steps:
Step 1 Click the Switch radio button.
Step 2 In the switch list box, select the name of the switch you want to delete.
Step 3 Click Delete.
The Delete Switch confirmation dialog box opens.
Step 4 Click Yes to delete the switch definition in Configuration Manager, or click No to cancel the delete operation and keep the specified switch definition.
Roving allows you to monitor individual interfaces supported by a switch. These interfaces can include:
The Network Analysis Module can rove multiple Ethernet ports, a single Fast EtherChannel port, or a VLAN.
SwitchProbe devices do not keep individual statistics for each port; therefore, Cisco recommends you use only one port or VLAN to rove at a time.
For any switch in the Cisco Catalyst 5000 family of switches, you can rove the VLANs and FECs configured in the switch. The roving VLANs feature is similar to the roving switch ports operation application feature. The packets on the VLAN are mirrored to the internal Network Analysis Module or to the physical analyzer port where an attached SwitchProbe device examines them.
To support the roving capability between VLANs and capture up-to-date statistics from a selected object, you also can reinitialize the counters on demand.
To rove a VLAN, follow these steps:
Step 1 In the Configuration Manager main window, click the Switch radio button.
Step 2 Select the switch containing the VLANs you want to rove.
Step 3 Click the VLAN radio button under the switch list to display all the VLANs configured in the selected switch.
Step 4 Select the VLAN you want to rove from the VLAN list.
Step 5 Click Rove ON to the right of the switch port list box.
A dialog box displays the VLAN that is currently roved (if any).
Step 6 Click Yes in the confirmation box.
Another dialog box prompts you to reinitialize the counters in the SwitchProbe device or Network Analysis Module.
Step 7 Click Yes to reset the statistical counters of the roving agent to zero, or click No to continue tracking statistics at the point where the counters concluded from the last roved VLAN.
The agent roves to the selected VLAN.
The following sections provide more information about roving:
The TrafficDirector application provides roving capability when the following requirements are met:
The TrafficDirector application supports multiport roving for all Cisco Catalyst 5000-series switches. Multiport roving lets you view traffic associated with one or more selected switch ports. If you have a Catalyst 5000-series switch configured, the TrafficDirector application enables you to rove up to 16 switch ports at one time.
You use the Configuration Manager Rove On button to rove to a selected interface (Port, FEC, VLAN).
You use the Configuration Manager Rove Off button to disable the roving operation in the switch.
To rove to an interface, follow these steps:
Step 1 Click the Switch radio button.
Step 2 In the switch list box, select the switch name.
Step 3 Click one of the interface radio buttons---Port, VLAN, or FEC.
The list of interfaces recognized by the TrafficDirector application is displayed in the interface list box.
Step 4 In the interface list box, select the port(s), VLAN, or FEC you want to rove.
Step 5 Click Rove ON.
Step 6 A dialog box opens in which you are asked to confirm the roving operation.
The next section provides information about interpreting roving messages:
Step 7 If you are roving to a Network Analysis Module, a popup window is displayed from which you select a property file. The default for the Network Analysis Module is NAMprop. Click OK to download the properties file, or click Cancel to cancel the download.
The following is a list of possible messages that might be displayed when roving one or more interfaces:
Explanation The TrafficDirector application is monitoring the ports specified.
Recommended Action Click Yes if you want to move to the selected port, or click No to cancel this rove operation.
Recommended Action Click Replace to clear the previously roved ports, or click Add to add the specified port to existing list of ports being monitored.
Recommended Action Click Yes to reset the counters, or click No to maintain the previous counters.
Recommended Action Click Yes to rove to the VLAN interface, or click No to cancel this rove operation.
Recommended Action Click Yes to rove to the FEC interface, or click No to cancel this rove operation.
You can use the TrafficDirector application to set thresholds on non-RMON MIB objects, such as a non-RMON object such as ifOutoctets (the number of bytes within a packet transmitted out of a router or switch port).
To set a threshold on a non-RMON object ID (OID), follow these steps:
Step 1 Edit the $NSHOME/usr/usrtrap.oid to include the non-RMON OID MIB.
Step 2 Start Configuration Manager.
Step 3 Select the switch.
Step 4 Click Custom.
Step 5 Select Property.
Step 6 In the bottom half of the screen, click Add.
Step 7 In the Stats Type field, click User Defined.
Step 8 Select the non-RMON OID from the trap variable field.
Step 9 Click OK.
Step 10 Click Install.
An alternate way to set the trap is to add the MIB to the $NSHOME/usr directory in the same format as the other *.mib files. You can then use the proxy SNMP feature with a SwitchProbe device to configure the trap.
Virtual interfaces (VLANs, PVCs, and DLCIs) are automatically learned when you click OK in either the Add or Edit Agent dialog box.
Physical interfaces (FECs) and Special interfaces (FEC and NetFlow) are automatically learned when you define the SwitchProbe IP address and click View in the Add or Edit Agent dialog box.
The following sections provide more information:
You can view the virtual interfaces (VLANs, PVCs, and DLCIs) associated with agent in the Interface list box on either the Configuration Manager window or TrafficDirector main window.
Figure 3-10 illustrates the Configuration Manager window displaying a list of DLCI interfaces associated with a Frame Relay agent.
The following sections provide more information about working with virtual interfaces:
You monitor virtual interfaces in almost the same way as other types of agents. For example, you can select a virtual interface and launch a TrafficDirector application to view the traffic associated with that interface.
The shared properties file installed on the agent also applies to all the virtual interfaces associated with that agent. Some types of virtual interfaces can have a Custom Properties file associated with them to identify the requirements for logging and threshold detection.
For example, you can install a Custom Properties file on these types of interfaces:
If any of the virtual interfaces change in your network environment, you can update them easily in Configuration Manager by selecting the agent name and clicking Learn.
The Frame Relay agent creates a DLCI interface for each permanent virtual circuit (PVC) it detects on a segment. These interfaces are learned by the TrafficDirector console when you add the Frame Relay agent in Configuration Manager.
The following sections provide more information about DLCI interfaces:
You can monitor each DLCI interface just as you would any other type of agent. You can install a shared properties file on the Frame Relay agent to automatically install the same domains on all of its DLCIs. Use custom properties files to configure traps and logging for individual DLCIs. For more information about creating and assigning properties files, see Chapter 6, "Working with Properties."
For each DLCI you can view in Configuration Manager, you can edit the CIR name and the CIR values assigned.
To assign a new name or edit the CIR values, follow these steps:
Step 1 In the Configuration Manager window, click the Frame Relay radio button.
Step 2 Select the name of the Frame Relay agent you want to edit.
Step 3 Click Learn to verify that the names of the DLCIs appearing in the Interface list box correspond with the latest DLCIs in your network.
All discovered DLCIs appear in the Interface list box in the lower left corner of the Configuration Manager window (Figure 3-11).
Step 4 Select the DLCI you want to edit.
Step 5 Click Edit (to the right of the Interface list box).
The Edit DLCI dialog box opens (Figure 3-12).
Step 6 In the Edit DLCI dialog box, modify the necessary information:
Step 7 Click OK to accept the new DLCI configuration.
Step 8 To update the Frame Relay agent with the latest changes, follow these steps:
(a) Select the Frame Relay agent from the Frame Relay agent list box.
(b) Click Download to download the new CIR values to the selected agent.
The View Interface dialog box (Figure 3-13) allows you to view and save physical and special interfaces configured on a SwitchProbe device as individual agents.
On the View Interface dialog box, you can choose to save one or more interfaces as agents. This feature allows you to monitor each interface just as you would any other type of agent.
For example, if you wanted to monitor the FEC trunk and each individual FEC subchannel configured on an FEC SwitchProbe device, you would save the interfaces 3, 4, 5,6, and 49 as individual agents. Later, you can redefine the properties assigned to an agent by attaching a custom properties file or editing a shared properties file.
For more information about working with properties files, see Chapter 6, "Working with Properties."
For more information about saving physical and special interfaces as agents, see "Adding an Agent Definition."
For specific information about configuring FEC Subchannels or NetFlow interfaces, see the following sections:
The TrafficDirector application allows you to view traffic associated with an FEC trunk and each FEC subchannel when you define an FEC SwitchProbe device as an agent in Configuration Manager.
The TrafficDirector applications learns the FEC subchannels when you click View on the Add or Edit Agent dialog box. To monitor the FEC trunk and its subchannels, you must save interfaces 3, 4, 5, 6, and 49 as agents in the View Interface dialog box.
After you save the FEC interfaces as agents, you can choose to monitor these interfaces as individual agents or as an agent group. To monitor them individually, use the Agents radio button. To monitor them as an agent group, use the Agent Group radio button.
The FEC trunk is interface 49. Therefore, to monitor the traffic associated with the entire FEC trunk, you select the agent name associated with interface 49. To monitor the individual subchannels, select any of the agent names associated with interfaces 3, 4, 5, and 6.
For more information about configuring these interfaces in TrafficDirector and saving them as agents, see "Adding an Agent Definition."
TrafficDirector can recognize NetFlow interfaces for the following types of devices:
You can view traffic associated with the NetFlow interfaces when you define a NetFlow-enabled device as an agent in Configuration Manager.
The TrafficDirector application learns the NetFlow interface(s) when you click View on the Add or Edit Agent dialog box. To monitor the aggregate NetFlow interface (50) or individual NetFlow interfaces (57-64), you must save the interface(s) as agents on the View Interface dialog box.
For information about configuring NetFlow interfaces on the SwitchProbe device, see the Cisco SwitchProbe Installation and Configuration Guide. For information about configuring NetFlow interfaces on the Network Analysis Module, see the Catalyst 5000 Series Network Analysis Module Configuration Note.
After you save the NetFlow interfaces as agents, you can choose to monitor the interfaces as individual agents or as an agent group. To monitor them individually, use the Agents radio button. To monitor them as an agent group, use the Agent Group radio button.
For more information about configuring these interfaces in TrafficDirector and saving them as agents, see "Adding an Agent Definition."
The TrafficDirector application can learn about virtual, physical, and special interfaces on a SwitchProbe device only after you properly configure the interfaces in the device during setup.
The following prerequisites must be met:
Posted: Mon Feb 8 15:14:50 PST 1999
Copyright 1989-1999©Cisco Systems Inc.