Download Print this page

Cisco Dial NMS Implementation Manual page 113

Cisco systems basic dial nms implementation guide

Advertisement

After a filter is set up, HPOV will not discover devices unless they are defined by the filter. Edit the
filter each time a new device is added to the network.
For more information about discovery filters, go to http://www.openview.hp.com
The filter file is located in the /etc/opt/OV/share/conf/C directory. A sample file is shown in the
following step-by-step example. The file has been manually edited and abbreviated to include a specific
node list and filter list for this case study:
Node list—A list of specific devices. In the example, the list is called TheNetNodes. There are two
devices in the list: AS5800-1 and AS5800-2.
Filter list—A list of attributes for the specified devices. In the example, the list is called
TheNetFilters, which specifies the filtering attributes for the devices in the node list. For example,
all devices must be SNMP compliant and Cisco devices.
To see a complete filter file, go to
http://www.cisco.com/univercd/cc/td/doc/cisintwk/intsolns/dialnms/filter.txt
To set up and edit a discovery filter, follow these steps:
Find the filters file on your Unix workstation:
aurora:/etc/opt/OV/share/conf/C ->ls
filters
oid_to_sym
Edit the filters file by using a text editor to include a node list and a filter list for your network
environment:
aurora:/etc/opt/OV/share/conf/C ->vi filters
//
// @(#)$OV_CONF/$LANG/filters
// @(#)HP OpenView NNM Release B.05.01
// @(#)Copyright (c) 1990-1997 Hewlett-Packard Company
// $Revision: /main/TORNADO/NNM_NT/5 $
//
// This is the default filter file.
// which may be useful in your environment.
// these filters and/or add your own.
// for more information on this file.
// NOTE: The behavior of topology filters in a distributed environment
// changed as of DFIX 5027.
// patch level.
This should be considered the correct specification of
// how topology filtering behaves in a distributed environment.
//
// Sets are a simple way to list string values to test
// against in a filter.
// for membership in a set defined here.
//
Sets {
//
// These are simple examples of sets.
//
servers "Set of Servers" { "sv1", "sv2", "sv3" }
gateways "Backbone gateways " { "gw1", "gw2", "gw3" }
TheNetNodes "TheNet Node List" { "AS5800-1", "AS5800-2" }
trapd.conf
Jun 21 1997
$Date: 1997/01/13 19:35 UTC $
These filters are examples
Feel free to modify
See OVfilterIntro(5)
This file documents the behavior as of that
The "IN" operator tests a field value

Advertisement

loading