Making Additional Customizations › Set Up Application Mapping › Import Application Mapping Rules › Import Custom Application Mapping Rules

Import Custom Application Mapping Rules

You can create application mapping rules of a single type by importing a properly formatted .csv file. Example .csv files are provided, which show the required fields to include in the import file for each rule type.

Follow these steps:

1. Log in to the NFA console server or stand-alone server as a user who is a member of the Administrators group.
2. Open a command prompt.
3. Open the example import file for your rule type:
   • All (ToS) rule - tos.csv
   • Host rule with a specified protocol - server-protocol.csv
   • Host rule without a specified protocol - server.csv
   • Subnet rule - subnet.csv
   • NBAR2 rule - nbar2.csv
4. Follow the format in the example file for your rule type:
   • The first row in the file is the column name row, which identifies the fields. Leave the first row exactly as it is shown in the example file. Do not change the spelling or order of the column name row.
   • Add a row below the top row for each rule that you want to import.
   • Enter values for each required field.

     Separate the field values with commas. Do not include a comma inside any value string. A comma signals the import utility to go the next field.

     All fields are required except for the desc (Description) field. To specify a blank desc value, enter only a comma (with no space).

   • The import file columns correspond to the following columns on the Application Definitions page:
     • name = Name: Rule name
     • desc = (Optional) Description
     • protocolName - Protocol
       To specify all protocols, enter the value -1.
     • tos = ToS (Type of Service)
       To specify all ToS, enter the value -1.
     • ip = IP/Subnet: Host IP address
     • mask = IP/Subnet: Subnet addition to the host IP address
     • newPort = Destination Port
     • beginPort = Start Port: Starting port in a port range or port number for a server-protocol rule
     • endPort = End Port: Ending port in a port range
     • applicationID = NBAR2 Application ID

     Some fields apply only to particular rule types, as shown in the table at the end of these steps.

5. Go to the directory that contains the .csv file. The following command shows the default location:

   cd <install_path>\reporter\racmd
   

   where:

   <install_path> is the product installation path. The product installation path is C:\CA\NFA by default.

   racmd is the directory that contains the .csv import file. The file is written to this directory when you install the product.

6. Perform the import by entering the following command:

   racmd -import nbar2.csv
   

   where:

   nbar2.csv is the name of the application mapping rule file that you want to import. The command string is based on the expectation that the racmd command and .csv file are in their default location. If you have moved the .csv file, include the fully qualified path (the path and file name).

   If any errors occur during the import, error messages are shown. If no message is returned, the import succeeded with no problems.

7. (Optional) Verify that the rules are listed on the Applications 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.

8. (Optional) Verify that the application traffic is labeled appropriately in the following locations:
   • Enterprise Overview page: Top Protocols report
   • Interface page: All reports that show protocol data
   • Custom Reporting page and Analysis page: Protocol Index, which you use to select protocols to filter a new or edited report
9. (Optional) Combine or separate traffic for selected applications if you like, as discussed in Set Up Application Mapping.

The following table lists the fields that apply to each rule type. List the fields in the order shown in the import file example, not the order shown in the table.