Integrating the TrafficDirector Application with Other Managers

Installing Integration Software

Integrating with HP OpenView

Integrating with IBM NetView/6000

Adding Agents to OpenView or NetView Maps

OpenView or NetView Trap Integration

OpenView or NetView Application Integration

Troubleshooting Tips

Integrating with HP OpenView (Microsoft Windows NT)

About Trap Integration

Updating Object IDs

Integrating the TrafficDirector Application with Other Managers

This appendix describes how to integrate the TrafficDirector application with the following network management applications:

Hewlett-Packard OpenView (OV)
IBM NetView/6000 (NV)
HP OpenView (Microsoft Windows version of the TrafficDirector application only)

The following topics describe how you use the TrafficDirector application with these other applications:

Installing Integration Software

The software needed to integrate agents (SwitchProbe devices and embedded RMON agents) with OpenView or NetView/6000 is automatically copied during installation.

Table F-1 lists the installation directories.

Table F-1: Installation Directories

Directory Contains

$NSHOME/ums/fsd_ov

$NSHOME/ums/fsd_ov/bin

Executable scripts

$NSHOME/ums/fsd_ov/fields

OV or NV Field registration file

$NSHOME/ums/fsd_ov/symbols

OV or NV Symbol registration file

$NSHOME/ums/fsd_ov/config

Sample configuration files

$NSHOME/ums/fsd_ov/registration

OV or NV registration files to start TrafficDirector applications

$NSHOME/ums/fsd_ov/bitmaps

Bitmaps for SwitchProbe devices that the ipmap application uses to represent SwitchProbe devices on network maps

Directory	Contains
$NSHOME/ums/fsd_ov
$NSHOME/ums/fsd_ov/bin	Executable scripts
$NSHOME/ums/fsd_ov/fields	OV or NV Field registration file
$NSHOME/ums/fsd_ov/symbols	OV or NV Symbol registration file
$NSHOME/ums/fsd_ov/config	Sample configuration files
$NSHOME/ums/fsd_ov/registration	OV or NV registration files to start TrafficDirector applications
$NSHOME/ums/fsd_ov/bitmaps	Bitmaps for SwitchProbe devices that the ipmap application uses to represent SwitchProbe devices on network maps

Integrating with HP OpenView

To integrate the TrafficDirector application with HP OpenView, follow these steps:

Step 1 Stop all open ovw sessions.

Step 2 Enter the following command:

cd $NSHOME/ums/fsd_ov/bin ./install.ovfiles.ovw

Step 3 Edit the OpenView files as follows:

For each agent (SwitchProbe device or embedded RMON agent) on your network, add that device's system object identifier (sysoid) to the file /etc/opt/OV/share/conf/oid_to_sym, followed by :Net Device:SwitchProbe.

: A list of entries is displayed, reflecting various IOS-embedded RMON agents is located in the $NSHOME/ums/fsd_ov/config/oid_to_sym_TrafficDir file.

For each agent on your network, add a similar line to the /etc/opt/OV/share/conf/oid_to_type file, followed by :Cisco Systems:SwitchProbe Agent.

: You can find a list of example entries for this file in the file $NSHOME/ums/fsd_ov/config/oid_to_type_TrafficDir.

Note

Monitor > MIB Values

Step 4 Query the setting for the sysoid from the Systems Group.

Step 5 Edit the file /etc/opt/OV/share/fields/C/snmp_fields by adding the line RMON Agent to the SNMP Agent fields enumeration.

Step 6 Run the OpenView program to add the symbol and fields to the OpenView database.

To do so, enter the following command:

ovstart

Step 7 Enter the following command to create a new symbol under an existing symbol class Net Device:

/opt/OV/bin/ovw -fields

A new enumerated value is assigned to the Vendor field. A new enumerated value---RMON Agent---is assigned to the SNMP Agent field. You can use these field values and symbol types to locate SwitchProbe devices or embedded RMON agents in OpenView network maps.

Step 8 Start an OpenView windows session by entering the following command:

/opt/OV/bin/ovw

Note

Step 9 Several applications, when started from an OpenView session, require an Xterm window. You can find the Xterm executable in the /usr/x11/bin directory. For Sun systems, the path is /usr/openwin/bin. You must add this directory to your execution path.

In the csh shell, enter the following command:

setenv PATH /usr/X11/bin:$PATH

For other shells (sh, ksh), enter the following command:

PATH=/usr/bin/X11:'$PATH'; export PATH;

Integrating with IBM NetView/6000

To integrate the TrafficDirector application with IBM NetView/6000, follow these steps:

Step 1 Stop all open ovw sessions.

Step 2 Enter the following command to install the NetView/6000-related files:

cd $NSHOME/ums/fsd_ov/bin ./install.ovfiles.nv

Step 3 Edit the NetView/6000 files as follows:

For each agent (SwitchProbe device or embedded RMON agent) on your network, add that device's system object identifier (sysoid) to the file /usr/OV/conf/C/oid_to_sym, followed by :Net Device:SwitchProbe.

: A list of entries is displayed, reflecting various IOS-embedded RMON agents is located in the file $NSHOME/ums/fsd_ov/config/oid_to_sym_TrafficDir.

For each agent on your network, add a similar line to the /usr/OV/conf/C/oid_to_type file, followed by :Cisco Systems:SwitchProbe Agent.

: You can find a list of example entries for this file in the file $NSHOME/ums/fsd_ov/config/oid_to_type_TrafficDir.

Note

Monitor > MIB Values

Step 4 Query the setting for the sysoid from the Systems Group.

Step 5 Edit the file /usr/OV/fields/C/snmp_fields by adding the line RMON Agent to the SNMP Agent fields enumeration.

Step 6 Run the NetView/6000 program to add the symbol and fields to the NetView/6000 database.

To do so, enter the following command:

ovstart

Step 7 Enter the following command to create a new symbol under an existing symbol class Net Device:

/usr/OV/bin/ovw -fields

This command creates a new symbol under an existing symbol class Net Device. A new enumerated value is assigned to the Vendor field. Another new enumerated value---RMON Agent---is assigned to the SNMP Agent field. You can use these field values and symbol types to locate SwitchProbe devices or embedded RMON agents in NetView/6000 network maps.

Step 8 Start a NetView/6000 windows session by entering the following command:

/usr/OV/bin/ovw

Note

Step 9 Several applications, when started from a NetView/6000 session, require an Xterm window. You can find the Xterm executable in the /usr/x11/bin directory. For Sun systems, the path is /usr/openwin/bin. You must add this directory to your execution path.

In the csh shell, enter the following command:

setenv PATH /usr/X11/bin:$PATH

For other shells (sh, ksh), enter the following command:

PATH=/usr/bin/X11:'$PATH'; export PATH;

This section also includes information about the following topics:

Adding Agents to OpenView or NetView Maps

To add an agent (SwitchProbe device or embedded RMON agent) to an OpenView or NetView/6000 map, follow these steps:

Step 1 To define the required agents in the /usr/OV/conf/snmp.conf file, in an ovw session, select Options > SNMP Configuration to define the SNMP-related parameters for all the SwitchProbe devices you need to add.

You must define the following parameters:

Community
Polling Interval
Retry Timeout
Number of retries

Step 2 Add agents to the OpenView or NetView/6000 maps using one of the following methods:

Let the OpenView or NetView/6000 discovery process discover agents. To do so, select Options > Topology Polling. If you chose this method, this procedure is now complete.
Add the agents manually. To do so, select Edit > Add Object.
Continue with Step 3.

Step 3 Open the segment submap for the segment where the agent is installed.

Step 4 From the Edit > Add Object dialog, select the agent symbol and drag it to the open submap.

The Add Object dialog box opens.

Step 5 In the Add Object dialog, enter information about the agent.

Step 6 Click OK.

An agent symbol is displayed on the open submap. This segment connects to the segment and turns green.

To verify that an agent is added correctly, select the device that was just added and query its SNMP MIB. To do so, select Monitor > MIB Values... Make sure the setting for system object id is correct. Then make sure the object capabilities indicate Cisco as the vendor and the SNMP Agent field is set to TrafficDirector Agent.

OpenView or NetView Trap Integration

The TrafficDirector rmonmgr application originates a daemon process (dvtrapd) when it is run. This daemon opens port 395 to listen to SNMP traps. The results of this process, including any error conditions, are logged in the file $NSHOME/usr/dvtrap.log. The Alert Monitor application needs the TrafficDirector daemon. The application is transparent to OpenView or NetView/6000 trap services.

The /usr/OV/conf/trapd.conf file defines various traps that the umbrella management system can understand. An example of TrafficDirector application traps is included in $NSHOME/ums/fsd_ov/config/fsdtrapd.conf. You must add this trap information to the umbrella management system's event configuration database for it to recognize traps from agents.

Note Do not edit trapd.conf. See the man page for trapd.conf for information on adding trap support.

The TrafficDirector application includes three trap daemons:

dvtrapd (the default)
dvtrapd.ovw (for OpenView or NetView)

To fully integrate traps with OpenView or NetView, follow these steps:

Step 1 Start the TrafficDirector application on the local system.

Step 2 Go to $NSHOME/bin.

Step 3 Click the Admin radio button.

Step 4 Click the Remote Login icon.

Step 5 Enter 11 and press Enter.

Step 6 Enter the following command at the command-line prompt:

set trap_port 162

Step 7 Enter quit and press Enter to exit command-line mode.

Step 8 Enter 12 and press Enter to reboot the device.

Step 9 Exit from Remote Login.

Step 10 Modify $NSHOME/usr/default.dvp to remove the comment character from the snmp-trap-port line so that it reads as follows:

snmp-trap-port: 162	 #Additional trap port

Step 11 Replace dvtrapd with dvtrapd.ovw by following these steps for OpenView or NetView:

mv dvtrapd dvtrapd.non_ovw
cp dvtrapd.ovw dvtrapd

Step 12 Enter the command chmod 4755 trapd*.

Step 13 If it is running, kill dvtrapd.

Step 14 Start HP OpenView or NetView.

Step 15 Start the TrafficDirector application.

Step 16 At the console, enter the following command to verify whether dvtrapd is running:

ps -ef | grep dvtrapd*

Step 17 If it is not running, start it manually.

Step 18 From the TrafficDirector application, set the trap you want.

OpenView or NetView Application Integration

You can integrate applications with OpenView or NetView/6000 by using a combination of Application Registration files, the Symbol Registration file, and the Field Registration file. You can use any of the commonly used features of OpenView or NetView/6000 (such as the locate capability, custom symbols, or map selection lists) with agents. The following functions are provided as part of the OpenView or NetView/6000 integration effort:

A unique OpenView or NetView/6000 symbol for agents defined under the class "Net Device."
The ability to start the TrafficDirector application, Traffic Monitor, Protocol Monitor and Data Capture from an ovw session.
The ability to locate agents on an open map. To locate agents, select the Locate menu and then Symbol type, Vendor Name, or SNMP Agent type.

A new menu item, Monitor > TrafficDirector, has been added to the OpenView menu hierarchy. From this menu, you can run TrafficDirector application functions. As appropriate, TrafficDirector application functions are sensitive to the objects currently selected on the OpenView map. You can select an RMON agent (SwitchProbe device) on the map, then start a TrafficDirector application function for that SwitchProbe device. The menu structure is as follows:

TrafficDirector > TrafficDirector---Emulates running the TrafficDirector application. Selecting a SwitchProbe device is not required with this menu item.
TrafficDirector > Traffic Monitor---grpktmon application runs on the selected SwitchProbe device.
TrafficDirector > Data Capture---Emulates running txdcap. The application runs on all selected SwitchProbe devices.
TrafficDirector > Protocol Monitor---Emulates running grdommon. Selecting a SwitchProbe device is not required with this menu item.

Troubleshooting Tips

If you encounter problems, try any of the following troubleshooting tips:

Make sure your $NSHOME environment variable is set to point to the directory where your TrafficDirector applications are installed.
If SwitchProbe devices are not responding to OpenView or NetView/6000, but are responding to TrafficDirector applications, or vice versa, make sure the community strings are set appropriately. For the TrafficDirector application, the community string access is determined by the device's entry in the $NSHOME/usr/agent.lst file. You can change the community string by editing the agent information from Configuration Manager.
If you get an INVALID_AGENT error message when starting TrafficDirector applications that require an agent as a parameter, make sure you have a valid entry in the TrafficDirector agent list. Use the same name used by the OpenView or NetView/6000 map. If the names do not match, the TrafficDirector application looks for the agent IP address in the agent list, but it assumes interface number one. For many agents, this is not the correct interface.
If you have problems starting a TrafficDirector application from OpenView or NetView/6000 when the application requires an agent name as an argument, you can instead run txman and start applications from it.

Integrating with HP OpenView (Microsoft Windows NT)

To integrate HP's OpenView for Windows, tested for version 7.2.2, see the instructions in the file readme.ovw in directory nshome\ums\fsd_ov. This directory contains the readme file and the fsdoids.mib file, which contains the sysoids and trap definitions.

This is an example file that allows a user drop-in integration of TrafficDirector applications to the Hewlett Packard OpenView product.

Step 1 Install the TrafficDirector application, if you have not already done so.

Step 2 Change to the OV directory by entering the following command:

cd  c:\ov

Step 3 Edit the XOVSRVR.INI file in the following manner:

In the [Programs] section, add the following lines.

RMONMGR=c:nshome\bin\rmonmgr.exe
GRPKTMON=c:nshome\bin\grpktmon.exe
NSDCAP=c:nshome\bin\nsdcap.exe

Note

In the [MenuIDs] section, add the following lines:

FSD=TrafficDirector..,OV_IDMMONITOR,Launch TrafficDirector

In the [CommandIDs] section, add the following lines:

FSDA=&TrafficDirector, FSD,0x101,OVM_ENABLED,txman,,
Launch TrafficDirector...!
FSDB=&Traffic Monitor,FSD,0x102,OVM_ENABLED,GRPKTMON,,Launch TrafficDirector Traffic Monitor...!
FSDC=&Protocol Monitor,FSD,0x103,OVM_ENABLED,GRDOMMON,,Launch TrafficDirector Protocol Monitor...!
FSDD=&Data Capture,FSD,0x104,OVM_ENABLED,TXDCAP,,Launch TrafficDirector Data Capture...!

About Trap Integration

The TrafficDirector application trap generated when an alarm entry crosses its rising threshold and generates an event that is configured for sending SNMP traps. Any traps generated on the network are received on ports 162 and 395.

Updating Object IDs

A set of system object IDs for the TrafficDirector suite of SwitchProbe devices is contained in the file fsdoids.mib. Modify the devices file in your ovfiles directory to reflect these values.

IMPORTS
        enterprises, OBJECT-TYPE
FROM RFC1065-SMI;
	frontier      OBJECT IDENTIFIER ::= { enterprises 141 }

	mibdoc    	OBJECT IDENTIFIER ::= { frontier 1 }
	netscout1      	OBJECT IDENTIFIER ::= { mibdoc   1 }
	netscout2	OBJECT IDENTIFIER ::= { mibdoc 	 2 }
-- netscout 1 branch	
	administrative  OBJECT IDENTIFIER ::= { netscout1 1 }
	reservedns12	OBJECT IDENTIFIER ::= { netscout1 2 }
	nsTraps		OBJECT IDENTIFIER ::= { netscout1 3 }
-- netscout 2 branch
	reservedns21	OBJECT IDENTIFIER ::= { netscout2 1 }
	console		OBJECT IDENTIFIER ::= { netscout2 2 }
	proxy		OBJECT IDENTIFIER ::= { netscout2 3 }
	reservedns24	OBJECT IDENTIFIER ::= { netscout2 4 }

	-- sysoid values
	probe6010	OBJECT IDENTIFIER ::= { netscout1 6010 }	
	probe6020	OBJECT IDENTIFIER ::= { netscout1 6020 }
	probe6030	OBJECT IDENTIFIER ::= { netscout1 6030 }
	probe6040	OBJECT IDENTIFIER ::= { netscout1 6040 }
	probe6050	OBJECT IDENTIFIER ::= { netscout1 6050 }
	probe6060	OBJECT IDENTIFIER ::= { netscout1 6060 }
	probe6070	OBJECT IDENTIFIER ::= { netscout1 6070 }
	probe7101	OBJECT IDENTIFIER ::= { netscout1 7101 }
	probe7102	OBJECT IDENTIFIER ::= { netscout1 7102 }
	probe7103	OBJECT IDENTIFIER ::= { netscout1 7103 }
	probe7201	OBJECT IDENTIFIER ::= { netscout1 7201 }
	probe7203	OBJECT IDENTIFIER ::= { netscout1 7203 }
	probe7211	OBJECT IDENTIFIER ::= { netscout1 7211 }
	probe7213	OBJECT IDENTIFIER ::= { netscout1 7213 }
	probe7221	OBJECT IDENTIFIER ::= { netscout1 7221 }
	probe7223	OBJECT IDENTIFIER ::= { netscout1 7223 }
	probe7301	OBJECT IDENTIFIER ::= { netscout1 7301 }
	probe7302	OBJECT IDENTIFIER ::= { netscout1 7302 }
	probe7303	OBJECT IDENTIFIER ::= { netscout1 7303 }
	probe7401	OBJECT IDENTIFIER ::= { netscout1 7401 }
	probe7501	OBJECT IDENTIFIER ::= { netscout1 7501 }
	probe7502	OBJECT IDENTIFIER ::= { netscout1 7502 }
	probe7503	OBJECT IDENTIFIER ::= { netscout1 7503 }
	probe7504	OBJECT IDENTIFIER ::= { netscout1 7504 }

Table of Contents

Integrating the TrafficDirector Application with Other Managers