cc/td/doc/product/rtrmgmt/sw_ntman/cwsimain/cwsi2/cwsiug2
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table of Contents

Setting Up Filters

Setting Up Filters

Before you start a data capture session or create a custom domain, you must determine the type and extent of the data to collect for display and analysis. You select an appropriate filter to screen the incoming data when you start a data capture session or create a custom domain.

TrafficDirector includes several predefined filters for most data capture and domain requirements. If you need filtering parameters that are not available in the predefined filters, you can use Filter Editor to edit a filter or create a new filter to meet your requirements.

To collect only selected data, you can create a set of filters that are either inclusive or exclusive, and that pass, capture, and store only the packets that meet the filter criteria. You start with a filter format that uniquely describes the specific characteristics of the frame that must be matched to accept or reject data packets from the data capture buffers.

When you have created a filter, you must insert it into the filter definition used for the data capture session.

Guidelines for Filter Types and Specifying Field Values

Before you start adding or modifying filters, you should be aware of the different ways you can specify field values. Except for the filter name, which is required, the remaining fields are optional; define only those fields that fit your needs.

TrafficDirector includes an extensive listing of filter formats. Each format has many fields that correspond to definable areas in different packet types.

Understanding Filter Types

You can choose from two filter types: physical or logical. The filter type depends on the filter format you select. A physical filter is topology-specific. This means that the filter criteria you define must be used with a specific media type, and is applied to frames at fixed positions.


Note Use a Token Ring-specific physical filter only on Token Ring topologies.

The predefined physical filters are as follows:

You can use a logical filter on any network. TrafficDirector applies the criteria you specify at the appropriate position in a packet regardless of the topology. Logical filters are useful because they save you work. For example, if you need to apply an IP filter on a Token Ring network and on an Ethernet network, you can define one filter that works on both.

Specifying Values When Defining Filters

When you define filters, you can use different numeric styles for values: decimal, hexadecimal (hex), binary, or IP address format (dotted). The numeric style you use to specify values depends on: whether the field is single-byte or multi-byte, and whether the field is tied to a certain type, such as MAC address, which accepts only a hex value. To find out whether a field is single-byte or multi-byte, open any predefined filter format file, in your $NSHOME/usr directory. For example, to find out how many bytes are required in the Time to Live field in an IP filter format, you would enter the following from your $NSHOME/usr directory:

type ip.ff

The filter format file (ip.ff) is displayed, showing the fields defined for the IP filter type, the number of bytes required for each field, and any specific value type associated with a field (such as MACADDR, the MAC address type).

Working with Single-Byte Fields

You can specify the following numeric types in single-byte fields, keeping in mind any restrictions as noted:

Hex These values must contain characters from the hex numeric set, 0 to 9 or a to f. However, if a hex value you specify is all numeric, TrafficDirector translates it as a decimal number.
Decimal These values must contain all numbers and no dots. For example, if you want to specify Time to Live as 128 seconds, enter 128, not 128.00.
Binary These values are only 0s and 1s, and must begin with a capital B.
Wildcards There are two acceptable wildcards when you only want to specify part of a numeric value. For hex or decimal numbers, you can specify an uppercase X as a wildcard. This X is a placeholder for one byte of information for decimal values, or four bits for hex values. For binary numbers, you must use a lowercase x as a wildcard and as a placeholder for one bit of information.

Working With Multiple-Byte Fields

In multiple-byte fields, you can specify the following numeric types, keeping in mind any restrictions as noted:

Hex These values must contain characters from the hex numeric set, 0 to 9 or a to f. However, if a hex value you specify is all numeric, TrafficDirector translates it as a decimal number.
Decimal These values in multiple-byte fields can contain numbers and dots. Keep in mind, however, that TrafficDirector reads each side of a dot as a separate number. For example, if you specify a number as 255.255.255.75, TrafficDirector reads four values: 255, 255, 255, and 75.
Binary These numbers are only 0s and 1s and must begin with a capital B.
Wildcards There are two acceptable wildcards for specifying part of a numeric value. For hex or decimal numbers, you can specify an uppercase X. This X is a placeholder for one byte of information for decimal values, or four bits for hex values. For binary numbers, use a lowercase x as a wildcard and as a placeholder for one bit of information.
Binary and hex combination You can use a combination of binary and hex values in any multibyte field. This is especially useful when you want to capture multicast packets on different network topologies.

Adding New Filter Definitions

To add a new filter, take the following steps:

Step 1 Click the Filter Editor icon in the TrafficDirector main window.

The Filter Editor window opens (Figure 13-1).



Figure 13-1: Filter Editor Window



Step 2 Select Edit>New Filter.

The New Filter window opens (Figure 13-2).


Step 3 Enter a name for the new filter in the Filter Name field. Specify up to eight letters, numbers, dashes, or underscores. The name must begin with a letter.

Step 4 Select a format from the Filter list box, then click Select Format.

The Add Filter window changes to display all the field names that apply to the filter format you selected. Depending on your selection, you might see only three fields or two pages of fields. For example, if you selected the TCP filter format, the New Filter window displays field names for all the rectangles shown in the window, and the PgDn button is enabled. You can click this button to see the rest of the fields available for defining the filter. Click PgUp to toggle back to the first page of the window.



Figure 13-2:
New Filter Window



Step 5 Enter field information as needed. Some fields may already contain values.

Step 6 Click OK to add the filter and display it in the filter list.

Editing Filter Definitions

To edit an existing filter definition, take the following steps:

Step 1 Click the Filter Editor icon in the TrafficDirector main window.

The Filter Editor window (Figure 13-1) opens.


Step 2 Select the filter you want to edit from the filter list.

Step 3 Click Edit.

The Edit Filter window opens. This window is the same as the New Filter window, except that the fields are already filled in with the values you last specified.


Step 4 Edit the fields you want to change.

Step 5 Click OK to create the new filter or click Cancel to quit.

Deleting a Filter Definition

When you no longer need a filter, you can delete the filter definition to conserve system resources. To delete a filter definition from the filter list, take the following steps:

Step 1 Click the Filter Editor icon in the TrafficDirector main window.

The Filter Editor window opens (Figure 13-1).


Step 2 Select the filter you want to delete from the filter list.

Step 3 Click Delete.

Step 4 Click OK to delete the filter definition, or click Cancel to quit without deleting the filter definition.

hometocprevnextglossaryfeedbacksearchhelp
Copyright 1989-1997 © Cisco Systems Inc.