Performing Advanced Administration › Map Applications › Create a Host Application Mapping Rule

Create a Host Application Mapping Rule

Create a Host application rule to combine traffic that originates from a particular host. For example, the Host application rule lets users easily report the total traffic from a particular server or from an application on the server.

Follow these steps:

1. Open the Application Definitions page:
   1. Select Administration from the NFA console menu.

      The Administration page opens.

   2. Select Application Definitions in the Administration menu.

   The Application Definitions page opens.

2. Verify that Application Mapping is the selected value for Rules.
3. Click Add Rule.

   The Add Application Mapping dialog opens.

4. Select Host from the list of rule types at the top of the dialog.

   The Add Application Mapping dialog switches to Host rule mode.

5. Specify values for the following settings:
   • Host: Specifies the IP address of the server whose network traffic you are mapping.
   • ToS: Specifies the Type of Service (ToS) to use as a filter for the collected data. To match all ToS values, accept the default value of ALL or leave the ToS box blank.
   • Protocol: Specifies the protocol of the data that will be affected by the rule, either TCP or UDP.
   • Port: Specifies the port to use for collecting data. To match all ports, accept the default value of ALL or leave the Port box blank.
   • Destination Port: Specifies the target port that will collect the mapped data.
   • Name: Identifier for the rule as it is listed on the Application Definitions page.
   • Description: (Optional) Supplies additional descriptive text to identify the rule type and use.

   Note: Multiple application mapping rules that have the same protocol and port destination settings will have the same name.

6. When the values are correct for all the required fields, click Save.

   The Add Application Mapping dialog closes. The new rule is included in the Application Mapping rule list.

7. (Optional) Run reports to verify that all of the traffic on the designated target port fits the rule.
8. (Optional) Once you notice the effects that new or changed application mapping rules have on reports, you may want to rename the protocol to identify it more clearly for other users.