Designing and Managing Behavior Models
-
Getting Started with NerveCenter Client - Setting Up Alarm-Instance Filters - Filtering Alarms by IP Range -
When you filter alarms by IP range, you are specifying that you only want to display alarm instances in the NerveCenter Client from particular nodes identified by their IP addresses.
See IP Subnet Filter Exclusion Rules, for more information about filtering alarms by IP ranges.
Although you can create a filter simply based on an IP range, a single filter can contain any combination of:
For information on how to build an alarm-instance filter based on severities and property groups, see the respective section listed below:
To create an alarm filter based on an IP range:
Configuration
from the Client
menu.The Client Configuration dialog is displayed.
Alarm Filter Modification
tab.The Alarm Filter Modification page is displayed.
New
button.The Alarm Filter Definition dialog is displayed.
This is the dialog you use to define your filter.
Subnet
text field.The IP address must consist of four octets separated by periods.
Mask
text field.The subnet mask must consist of four octets separated by periods. Taken together with the subnet address, this mask defines the subnet whose nodes you're monitoring.
Exclusion
text field, enter the last octet of the IP address of any node on the subnet that you're not monitoring.You can enter multiple exclusions separated by commas. You can also enter a range of excluded nodes using a hyphen. For example, if you enter 24, 76-78 in the Exclusion field, the nodes whose addresses end in 24, 76, 77, and 78 will be excluded by the filter.
Add
button.
Filter Name
field.
OK
button.The Alarm Filter Definition dialog is closed and you return to the Client Configuration dialog box.
You've now defined an alarm filter based on an IP range. Before the client will use the filter, however, you must associate the filter with a server. For instructions on how to create this association, see the section Associating a Filter with a Server.
When you filter by subnet, you specify which subsets of nodes are managed by NerveCenter. Filtering does not apply to nodes that have been imported from a file or from another NerveCenter. For an example, see IP Subnet Filter Examples.
You can exclude specific nodes that belong to the filter by entering an exclusion. To exclude one or more nodes, you must specify the full subnet and mask, and then enter the individual nodes you want excluded. Enter the part of the IP address that is not affected by the subnet's mask.
NerveCenter filters Class B and C networks.
In a Class C network, the first three octets of the address specify the network and the last octet specifies the host. For example, in network 194.123.45.0, the 194.123.45 value pertains to the network. The remaining octet is used to identify nodes (up to 254) on the network, and you can exclude nodes by specifying ID values in this octet.
For a Class B network, only the first two octets of the address specify the network. For example, in network 132.45.0.0, the 132.45 value pertains to the network. The remaining two octets are used to identify nodes, and you can exclude nodes by specifying ID values in these two octets.
In the following example, the node whose IP address is 134.204.179.40 is excluded from the filter (the node is filtered out and, therefore, is not managed by NerveCenter).
134.204.179.0
255.255.255.0
40
The following three examples (each on a separate line) illustrate valid exclusions:
7,8,9,15
7, 8, 9, 15
8,7,9,15
For example, you can enter as an exclusion range: 40-60
You can also enter the range in inverse order: 60-40
134.204.179.0
255.255.255.0
7,8,9
134.204.179.0
255.255.255.0
40-60
134.204.179.0
255.255.255.0
70-90
134.204.179.0
255.255.255.0
40-60,70-90
134.204.179.0
255.255.255.0
7-9,31,33,40-60
The following examples can help you understand how to filter nodes for Class B and C networks.
The following subnet filters are for two sample nodes:
The filter values in Class C Network Exampleshave the following effects on the sample nodes:
The following subnet filters are for two sample nodes:
The mask you use for this filter is 255.255.0.0.
Class B Filter Examples (Set One)
If you use a subnet mask of 255.255.240.0, you would get different results.
You must first apply the filter before determining the node's ID. The filter values in the table below have the following effects:
Class B Filter Examples (Set Two)
When you filter alarms by severity, you are specifying that you only want to display alarm instances in the NerveCenter Client from particular nodes identified by the severity of the alarm instance's state.
Although you can create a filter simply based on severity, a single filter can contain any combination of:
For information on how to build an alarm-instance filter based on IP range and property groups, see the respective section listed below:
To create an alarm filter based on severity:
Configuration
from the Client
menu.The Client Configuration dialog is displayed.
Alarm Filter Modification
tab.The Alarm Filter Modification page is displayed.
New
button.The Alarm Filter Definition dialog is displayed.
This is the dialog you use to define your filter.
Severity
tab.The Severity tab is displayed.
Available Severities
list, for each severity you want to use in your filter, select the severity and then select the >>
button. That is, you want to see information about alarm instances whose states have these severities.
The severities in this list box are the union of the severities defined by all of the servers to
which you're connected. Optionally, you can also add a user-defined severity to the list of
severities to filter by entering a severity in the And User-specified Severity
text box, and
then selecting the >>
button.
The name of the severity is moved to the Selected Severities
list. Information about alarm
instances with this severity will be displayed in the alarm summary views.
To remove a severity from the Selected Severities
list, select the severity and then select the
<<
button.
Filter Name
field.
OK
button.The Alarm Filter Definition dialog is closed and you return to the Client Configuration dialog box.
You've now defined an alarm filter based on severity. Before the client will use the filter, however, you must associate the filter with a server. For instructions on how to create this association, see the section Associating a Filter with a Server.
When you filter alarms by property groups, you are specifying that you only want to display alarm instances in the NerveCenter Client from particular nodes belonging to one or more property groups.
Although you can create a filter simply based on membership within a property group, a single filter can contain any combination of:
For information on how to build an alarm-instance filter based on an IP range and severities, see the respective section listed below:
To create an alarm filter based on property groups:
Configuration
from the Client
menu.The Client Configuration dialog is displayed.
Alarm Filter Modification
tab.The Alarm Filter Modification tab is displayed.
New
button.The Alarm Filter Definition dialog is displayed.
This is the dialog you use to define your filter.
Property Group
tab.The Property Group tab is displayed.
Available Property Groups
list, for each property group of each alarm instance's node, perform the steps below for each property group you want to be part of the filter. That is, you want to see information about instances whose nodes belong to these property groups.The property groups in this list box are the union of the property groups defined by all of the servers to which you're connected.
The name of the property group is moved to the Selected Property Groups
list. Information
about alarm instances with this property will be displayed in the alarm summary views.
Optionally, you can also add a user-defined property group to the list of properties to filter by
entering a property group in the And User-specified Property Group
text box, and then
selecting the >>
button.
To remove a property group from the Selected Properties
list, select the property group and
then select the <<
button.
Filter Name
field.
OK
button.The Alarm Filter Definition dialog is closed and you return to the Client Configuration dialog box.
You've now defined an alarm filter based on property groups. Before the client will use the filter, however, you must associate the filter with a server. For instructions on how to create this association, see the section Associating a Filter with a Server.
When you define an alarm filter, that filter is not used to filter alarm instances from all connected servers. It is only used to filter alarm instances from a server with which you have explicitly associated it.
To associate an alarm filter with a NerveCenter server:
Configuration
from the Client
menu.The Client Configuration dialog is displayed.
The name of the server appears in the Server Name
text field in the Connection Information
group box. This is the server with which you will associate your alarm filter.
Alarm Filter Selection
tab.The Alarm Filter Selection page is displayed.
Available Filters
list.This is the filter you want to associate with the server you selected in step 2.
>>
button to move the filter from the Available Filters
list to the Selected Filters
list.
To remove a filter from the Selected Filters
list, select the filter and then select the <<
button.
OK
button at the bottom of the dialog. Setting Up Alarm-Instance Filters | Rules for Associating Filters with Alarms |
29 July 2003 |