|
|
The following topics describe how you use the TrafficDirector application with these other applications:
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.
| 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 |
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.nvw
Step 3 Edit the OpenView files as follows:
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
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
This section also includes information about the following topics:
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 probe devices you need to add.
You must define the following parameters:
Step 2 Add agents to the OpenView or NetView/6000 maps using one of the following methods:
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.
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.
The TrafficDirector application includes three trap daemons:
To fully integrate traps with OpenView, NetView, or SunNet Manager, 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:
Step 12 Enter the command chmod 4755 trapd*.
Step 13 If it is running, kill dvtrapd.
Step 14 Start HP OpenView, NetView, or SunNet Manager.
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.
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 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:
If you encounter problems, try any of the following troubleshooting tips:
Table F-2 lists the files you need to integrate the TrafficDirector application with SunNet Manager. Some are standard SunNet Manager files. These files provide an icon for agents in a SunNet manager map, and allow you to start some of the TrafficDirector applications from the icon.
| File | Description |
|---|---|
README | Text file containing this information. |
TrafficDirector.schema | Schema file for the agent (SwitchProbe device or embedded RMON agent). |
TrafficDirector.icon | Icon for an agent. |
TrafficDirector.iconmask | Icon mask for an agent. |
fsdoids.mib | MIB that defines TrafficDirector application sysoids and trap types in a format that can be compiled by mib2schema. |
fsdadmin.mib | Proprietary administrative MIB for trap administration. |
To integrate the TrafficDirector application with SunNet Manager on Solaris platforms, follow these steps:
Step 1 Log into the Solaris system as superuser.
Step 2 Copy the file SwitchProbe.schema to a user's schema directory (usually $SNMHOME/agents).
Step 3 Copy the files SwitchProbe.icon and SwitchProbe.iconmask to the icon directory (usually $SNMHOME/icons).
Step 4 Copy the files fsoids.mib and fsadmin.mib to a user's schema directory (usually $SNMHOME/agents).
Step 5 Run $SNMHOME/bin/mib2schema fsdoids.mib.
To run SunNet Manager, follow these steps:
Step 1 Set the $NSHOME variable.
Step 2 To run for the first time, use snm -1.
Step 3 Add SwitchProbe agents to SNM.
Step 4 Click Headstart.
Step 5 Double click the map.
Step 6 Select Edit>Create.
Step 7 Select TrafficDir from the list box.
Step 8 Enter the following agent information:
Step 9 Select fsdoids.
Step 10 Click Apply.
Step 11 Select the newly created agent.
Step 12 Click the right mouse button.
Step 13 Select Tools.
Step 14 Select TrafficDirector.
Step 15 Add the same agent to the TrafficDirector application (if it is not already there).
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:
RMONMGR=c:nshome\bin\rmonmgr.exe
GRPKTMON=c:nshome\bin\grpktmon.exe
NSDCAP=c:nshome\bin\nsdcap.exe
FSD=TrafficDirector..,OV_IDMMONITOR,Launch TrafficDirector
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...!
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.
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 }
Posted: Mon Apr 5 13:08:00 PDT 1999
Copyright 1989-1999©Cisco Systems Inc.