|
|
This appendix tells you how to integrate TrafficDirector applications with the following managers:
The software needed to integrate TrafficDirector with OpenView or NetView/6000 is automatically copied during installation. The following directories are copied:
| $NSHOME/ums/fsd_ov | |
| $NSHOME/ums/fsd_ov/bin | Contains executable scripts |
| $NSHOME/ums/fsd_ov/fields | Contains OV or NV Field registration file |
| $NSHOME/ums/fsd_ov/symbols | Contains OV or NV Symbol registration file |
| $NSHOME/ums/fsd_ov/config | Contains sample configuration files |
| $NSHOME/ums/fsd_ov/registration | Contains OV or NV registration files to start TrafficDirector applications |
| $NSHOME/ums/fsd_ov/bitmaps | Contains bitmaps for SwitchProbe agents that the ipmap application uses to represent SwitchProbe agents on network maps |
To install the TrafficDirector OpenView or NetView/6000 files, use the following procedure:
Step 1 Stop all open ovw sessions.
Step 2 Run the install script, install.ovfiles.sh, to install the OpenView or NetView/6000 related files in the /usr/ov directory. (This script assumes that $OVHOME is set to /usr/ov. If it is not, you must either edit the install script or copy the files by hand.)
Step 3 Edit OpenView or NetView/6000 files:
For each RMON agent (SwitchProbe agent or Cisco IOS embedded RMON agent) on your network, add that device System Object Identifier to the /usr/OV/conf/C/oid_to_sym file, followed by ":Net Device:SwitchProbe". A list of entries reflecting various Cisco IOS embedded RMON agents is located in the $NSHOME/ums/fsd_ov/config/oid_to_sym_traffdir file.
For each RMON agent on your network, you should also add a similar line to the /usr/OV/conf/C/oid_to_type file, followed by ":Cisco:SwitchProbe". You can find a list of example entries for this file in the $NSHOME/ums/fsd_ov/config/oid_to_type_traffdir file.
Step 4 Query the setting for system object id (OID) from the Systems Group.
Step 5 Edit the file /usr/OV/fields/C/snmp_fields by adding "RMON Agent" to the "SNMPAgent" fields Enumeration.
Step 6 Run the OpenView or NetView/6000 Windows program to add the SwitchProbe symbol and fields to the OpenView or NetView/6000 database. To do so, run ovstart. Then enter the following:
/usr/OV/bin/ovw -fields
This command creates a new symbol called "SwitchProbe" under an existing symbol class Net Device. In addition, a new enumerated value, Cisco Systems, is assigned to the Vendor field. Similarly, a new enumerated value, RMON Agent, is assigned to the SNMP Agent field. You can use these new field values and symbol type to locate SwitchProbe agents or embedded RMON agents in OpenView or NetView/6000 network maps.
Step 7 Start an OpenView or NetView/6000 session by entering:
/usr/OV/bin/ovw
Several TrafficDirector applications, when launched from an OpenView or NetView/6000 Windows session, require an Xterm window. You can find the Xterm executable in the /usr/X11/bin directory. For Sun, the path is /usr/openwin/bin. You must add this directory to your execution path. You can do this in csh as follows:
setenv PATH /usr/X11/bin:$PATH
For other shells (sh, ksh), enter the following:
PATH=/usr/bin/X11:'$PATH'; export PATH;
You must set the NSHOME environment variable before you start an OpenView or NetView/6000 session.
To add an RMON agent (SwitchProbe agent or embedded RMON agent) to an OpenView or NetView/6000 map, use the following steps.
Step 1 To define the required TrafficDirector 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 probes you need to add. Parameters you need to define are Community, Polling Interval, Retry Timeout, and number of retries. See the corresponding manuals for more details.
Step 2 Add RMON 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 RMON agent is installed.
Step 4 From the Edit>Add Object... dialog, select the RMON agent symbol and drag it to the open submap. An Add Object dialog is displayed. In this Add Object dialog, enter information about the RMON agent.
Step 5 Click OK. An RMON agent symbol is displayed on the open submap. This segment connects to the segment and turns green.
To verify that an RMON agent is added correctly, select the device that was just added and query its SNMP MIB. To do so, use the Monitor>MIB Values... menu item. Ensure that the setting for system object id is correct. Then make sure the object capabilities indicate Cisco Systems as the vendor and the SNMP Agent field is set to RMON Agent--these object capabilities must be set like this.
TrafficDirector (tdir) originates a daemon process (dvtrapd) when it is run. This daemon tries to open port 162 to listen to SNMP traps. If it cannot do so, it tries to register with the OpenView API to receive 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 trap daemon. It 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 traps is included in $NSHOME/ums/fsd_ov/config/fsdtrapd.conf. You must add this trap information to the umbrella management system event configuration database for it to recognize traps from TrafficDirector agents.
You can integrate TrafficDirector 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 TrafficDirector 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 functions. As appropriate, TrafficDirector functions are sensitive to the objects currently selected on the OpenView map. This means you can select an RMON agent (probe) on the map, and then start a function for that probe. The menu structure is as follows:
| tdir>tdir | Just like running the tdir application. Selecting a probe is not required with this menu item. |
| tdir>Domain View | nsdommgr application runs on the selected probe. |
| tdir>Data Capture | Just like running nsdcap. The application runs on all selected probes. |
| tdir>Protocol Decode | Just like running nspdec. Selecting a probe is not required with this menu item. |
| tdir>Filter Editor | Just like running nsfilted. Selecting a probe is not required with this menu item. |
| tdir>Remote Login | nslogin application starts for the selected probe. If you select two or more probes, the menu item is not available. |
| tdir>Statistics>Pkt Distr | xnmgraph application, showing the packet size distribution, starts. |
| tdir>Statistics>Prot Distr | xnmgraph application, showing the protocol distribution, starts. |
| tdir>Trap Destinations>Add | dvadmin application starts for the selected probe. You are prompted to enter the target host and trap-community values you want to add. |
| tdir>Trap Destinations>Delete | dvadmin application starts for the selected probe. You are prompted to enter the target host and trap-community values you want to delete. |
| tdir>Trap Destinations>List | dvadmin application starts for the selected probe. You are provided with a list of trap destinations configured in the probe. |
| tdir>Domain>Install | dvinst application starts for the selected probes. You are prompted to enter the configuration file name. |
| tdir>Domain>List | dvlist application starts for the selected probes. |
If you have problems, try any of the tips described below:
This section lists the files you need to integrate TrafficDirector with SunNet Manager. They can be found in the $NSHOME/ums/fsd_ov directory. Some are standard SunNet Manager files. These files provide an icon for agents in a SunNet manager map and let you launch a number of TrafficDirector applications from the icon.
| README | The text file containing this information. |
| swtichprobe.schema | The schema file for the agent (SwitchProbe agent or Cisco IOS embedded RMON agent). |
| swtichprobe.icon | The icon for an RMON agent. |
| switchprobe.iconmask | The icon mask for an RMON agent. |
| fsdoids.mib | TrafficDirector MIB that defines TrafficDirector sysoids and trap types in a format that can be compiled by mib2schema. |
| fsdadmin.mib | TheTrafficDirector proprietary administrative MIB for trap administration. |
They can be found in the $NSHOME/ums/fsd_ov directory.
Copy switchprobe.schema to a user schema directory, $NSMHOME/agents (usually), and copy switchprobe.icon and switchprobe.iconmask to the icon directory, typically $NSMHOME/icons. To create data requests, use the RMON MIB schema shipped with SunNet Manager. For more information about creating data requests, see the SunNet Manager documentation.
|
|