Managing Interfaces › How to Poll Critical Interfaces Faster than Noncritical Interfaces › Set an Interface Filter

Set an Interface Filter

By default, the factory network interface monitoring profile includes a filter to prevent modeling interfaces that are administratively down. In addition, interfaces with a type (ifType) of 1 (Other) or 24 (Loopback) are not modeled, regardless if those interfaces are administratively up or down. IPSLAs with the rttMonCtrlAdminOwner MIB object that contains the string “Network Health" are not modeled either.

Filtering reduces the number of interfaces that are monitored, which reduces unwanted data collection and network traffic.

In addition to polling only administratively up interfaces, you also want to poll the most critical interfaces more frequently. To isolate and poll only these interfaces faster, you add a second filter condition to the interface filter associated with your custom monitoring profile. This second filter condition isolates the critical interfaces by finding only interfaces that contain "uplink" in their description.

Note: Log in as the administrator to perform this task.

Follow these steps:

1. Select your interfaces monitoring profile (called "Uplink Interfaces") from the Monitoring Profiles page.
2. Click Interface metric family row on the Metric Families tab and click Edit Filter.

   Note: Do not click directly on the metric family name, because it is linked to take you to the metric family definition. Instead, click the row the metric family name is in to activate the Edit Filter option.

3. Click the Add Condition button.

   Note: Multiple conditions are connected with an "and" operation. That is, all conditions must be met to satisfy the filter.

4. Configure the filter conditions with the following options and click Save:
   • Attribute: Description
   • Operation: Contains
   • Filter Value: uplink

   Note: The Filter Value field is case-sensitive.

   Consider the following details about additional attributes you can use for filtering:

   • For Speed In and Speed Out, you can use a decimal in the text field (such as 1.544) and can specify bps, Kbps, Mbps, or Gbps.
   • For more information about configuring Type (that is, ifType), see the iana web site: http://www.iana.org/assignments/ianaiftype-mib.
   • For Description and Alias, you can use a regular expression for filtering only when you select the Matches Regex or the Does Not Match Regex operation.

   When you save your changes, the filter criteria display on the Metric Families tab. You can now apply this monitoring profile to the appropriate device collection to begin polling your selected interfaces.

Note: Data Aggregator applies filtering after discovery. Interface components that do not match the filter criteria are not polled. If you add or edit an Interface filter after you run a discovery, polling on these components stops. These interface components are not displayed in CA Performance Center dashboards and data views.