Integrating NerveCenter with a Network
Management Platform
-
Integrating NerveCenter with IBM NetView for AIX - Using NetView as a node source - Filtering nodes from IBM NetView for AIX -
When using NetView as a source of information about nodes , it is important to determine which of the nodes in NetView's database NerveCenter will manage. NerveCenter does not need to monitor every node on your network.
There are several methods for restricting which nodes in NetView's node database will be placed in NerveCenter's node list:
NerveCenter allows you to monitor managed nodes that have particular capabilities. Typically NetView assigns these capabilities to a node to determine applicable management activities. Some examples of these capabilities are isRouter, isHub, and isIP.
To filter using a node's capabilities:
Node Source
tab.The Node Source page is displayed.
If this field is left blank, NerveCenter will not filter using a node's capability.
NerveCenter will monitor any node that matches at least one of the capabilities in the list.
Save
.The NerveCenter Server adds the new capabilities filter. It also closes and opens a new connection with the platform adapter. NerveCenter automatically performs a resynchronization with NetView's database.
New nodes will be added. Any node that is marked Autodelete (the default) will be deleted.
NerveCenter allows you to monitor managed nodes according to their particular system object identifiers (OIDs).
A node's System Object ID is an SNMP MIB-II object in the system group. It identifies the SNMP agent software running on the device. It is, however, commonly used to identify the type and vendor of the device because a particular vendor's agent usually runs on that vendor's devices.
To filter using a node's system object identifier:
Node Source
tab.NerveCenter displays the Node Source page.
If this field is left blank, NerveCenter will not filter using a node's system OID.
NerveCenter will monitor any node that matches at least one of the OID in the list.
For example, an administrator may want to restrict NerveCenter to nodes running SNMP agents from either Cisco or Hewlett-Packard nodes by typing the following:
Any device with an OID matching either of these numbers will be included in the NerveCenter nodes database.
Save
.The NerveCenter Server adds the new OID filter. It also closes and opens a new connection with the platform adapter. NerveCenter automatically resynchronizes with NetView's database.
New nodes will be added. Any node that is marked Autodelete (the default) will be deleted.
In addition to filtering nodes by OIDs and capabilities, NerveCenter allows you to filter out all nodes that do not belong to one or more subnets. NerveCenter determines the subnet by combining a specific IP address with a subnet mask. NerveCenter can filter by subnets of both Class B and Class C networks. In Class B networks, the first two octets specify the network while in Class C networks the first three octets identify the network.
The following table illustrates some filter configurations and their results:
Sample Subnet Filters and Their Results for a Class C Network
In addition to filtering out all but an entire subnet, NerveCenter allows you to exclude a specific node or range of nodes within the remaining subnet.
The following table illustrates some filter configurations with exclusions and their results.:
Sample Subnet Filters with Exclusions and Their Results
NerveCenter can determine automatically or manually subnet criteria used to filter nodes by IP address.
To configure NerveCenter to determine subnet criteria automatically:
IP Filters
tab.The IP Filters page is displayed.
Automatic
.Setting the method to automatic tells NerveCenter to ignore any address filters you enter and use instead the server's masks as a filter. NerveCenter calculates the subnet address and mask using the IP address and mask of each network interface card on the server.
Save
.NerveCenter will now automatically use the server's masks as a filter.
To set the subnet criteria manually:
IP Filters
tab.The IP Filters page is displayed.
Manual
.When the method is set to manual, NerveCenter will only use the subnet addresses listed in IP Address Filters area. If the IP Address Filters list is empty, NerveCenter ignores a node's subnet when determining if the node will be part of the node database.
A node's subnet address combines the node's IP address with the subnet mask.
Add
. The subnet address and mask address will be added to the IP Address Filters list.
The IP Address Filter List with Several Subnet Addresses
Save
.
NerveCenter monitors any address falling within the subnet and not excluded by the filter.
Previous: Synchronization with IBM NetView for AIX | Next: Identifying Parent-Child Relationships |
Please send comments or corrections to Information Development | This file was last updated on 10 October 2000 |