2-68
User Guide for the Cisco Network Analysis Module (NAM) Traffic Analyzer, 5.0
OL-22617-01
Chapter 2 Setting Up The NAM Traffic Analyzer
Classification
Table 2-33, Applications describes the fields on the Applications setup page.
This section provides the following procedures:
• Creating a New Application, page 2-68
• Editing an Application, page 2-69
• Deleting a Protocol, page 2-70
Creating a New Application
When defining applications, you will be able to view and select from a list of candidate IP addresses and
port numbers for the traffic being analyzed. You can create additional ports to enable the NAM to handle
additional traffic for standard applications.
To create a new application:
Step 1 Choose Setup > Classification > Applications.
The Applications screen displays.
Step 2 Choose the type you would like to create and click Create.
The Application Configuration window displays.
Step 3 Enter a name in the Name field.
Step 4 Enter a Selector value. This is an arbitrary number, unique within an engine-id. It will be automatically
assigned if left blank.
Tab l e 2-33 Applications
Field Description
Application Standard protocols, or name given by the user (if user-created).
Protocol/Port Application protocol and port.
The port is an arbitrary number you assign to handle the additional ports for
the protocol family. This protocol number must be unique so it does not
conflict with standard protocol/port assignments.
The port number range will vary depending on the protocol type selected.
Selector An arbitrary number, unique within an engine-id. It will be automatically
assigned if left blank.
This allows you to configure applications consistently across multiple NAMs,
so that the same user-created application is exported with the same value. This
should be used when configuring the same custom applications on multiple
NAMs.
Engine ID Will show “Custom” if it was user-created.
Application Tag Pre-defined for standard protocols.
For user-created, the application tag is a combination of the engine ID and the
Selector. The 32 bit is generated by using the engine ID as the highest order
byte, and the Selector makes up the other 3 bytes.
Description Full name of the protocol.