STRM Default Application Configuration Guide
2
D
EFINING
A
PPLICATION
M
APPINGS
Figure 1-1
Example of Application View
You can edit the user defined mapping file to ensure specific traffic is appropriately
classified in the STRM interface. However, STRM also includes default application
IDs, which you can view in the Applications View of the STRM interface. For
example, in
Figure 1-1
, the Chat group includes the default AOL group, which is
defined in the default mapping file to ensure all AOL traffic is assigned a value of
3001. For more information on the default values, see
Chapter 2
Default
Applications
.
Note: For more information on enabling or disabling application detection, see the
STRM Administration Guide.
Defining
Application
Mappings
To define application mappings:
Step 1
Using SSH, log in to STRM.
Step 2
Open the following file:
/store/configservices/staging/globalconfig/user_application_
mapping.conf
Note: To edit the name of the user_application_mapping.conf file, you can edit the
User Application Mapping parameter in the Flow Processor configuration window.
For more information, see the STRM Administration Guide. If the
user_application_mapping.conf does not exist in your system, create the file and
place the empty in the above directory.
Step 3
Update the file, as necessary.
When updating the file, note the following:
•
Each line in the file indicates a new mapped application. You can specify
multiple mappings (each on a seperate line) for the same application.
•
You can specify a wildcard character * for any of the fields. The wildcard
character must be used alone and not part of a comma separated list. The
wildcard character indicates that this field applies to all flows.
