Application mappings in the NNM iSPI Performance for Traffic (iSPI for Traffic)
The application mapping feature of the NNM iSPI Performance for Traffic enables network traffic characterization by associating network traffic with applications.
The iSPI for Traffic provides over 300 out of the box application mappings and a default application mapping group-DefaultAppMapGroup. The mappings are based on industry standards and the well-known destination ports reserved for use by various applications (for example, port 80 for HTTP and port 161 for SNMP).
The iSPI for Traffic also provides extensive flexibility for defining custom mappings specific to your IT environment and monitoring requirements.
The iSPI for traffic supports two ways to manage (adding/editing) application mapping:
Using the configuration UI
Using the CLI (command line interface) tool
Managing Application Mappings using the configuration UI
The iSPI for Traffic Configuration page allows you to manage application mappings. Refer to the Application Mappings section in “NNM iSPI Performance for Traffic online help” for complete details and options on using the configuration UI (user interface).
With the UI, to define the condition expression, you must first add the Boolean operators (AND or OR) and then add conditions to these operators. When combining multiple operators, it might become a little confusing for the operators to follow the right order.
Editing app maps require deleting existing conditions and replacing them with new required ones. Multiple application mappings cannot be defined at one time using the UI. Also filters with conditions need to be structured properly based on the requirement.
Managing Application Mappings using the CLI Tool
The iSPI for Traffic provides a command-line utility, nmstrafficfiltappmaptool.ovpl to manage the application mappings. This is very useful as it allows you to add and edit multiple application mapping definitions in a single step and also lets you backup mappings.
Defining and managing complex and multiple application mappings is easier and simpler when CLI is used as the definition is in plain text and defining the conditions is just like writing in plain English. Another bigger advantage is that multiple mappings can be added at once or edited at once.
nmstrafficfiltappmaptool.ovpl is available in the Traffic Master bin folder. Refer to the man page of the tool for complete list of options provided by the tool.
The tool takes input from a text file. You can easily create one using the following steps.
First create an input file. Let’s say Input.txt
Each line in the file defines one Application mapping definition. There are 3 comma separated fields in each line.
First field defines the “Condition” based on different attributes
E.g. Simple condition like: Port = 510
Or a complex condition like: (ProducerIP like 15.200.*.* OR ProducerIP like 16.200.*.* AND Port = 500),
Second field (App=”name”) is the name of the Application mapping
E.g. App = Test1
Third field is the name of the Application mapping Group to be used.
E.g. AppGroups = DefaultAppMapGroup
Here is an example Input.txt file with two application mapping definitions looks like below:
Port = 510,App = Test1,AppGroups = DefaultAppMapGroup
(ProducerIP like 15.200.*.* OR ProducerIP like 16.200.*.* AND Port = 500),App = Test2,AppGroups = DefaultAppMapGroup
Care should be taken with the syntax of the fields while defining the application mappings in the input file. Delimiter, Operands, Operators, Closing braces for the condition, Name of the Application and Application mapping should be proper. Otherwise the iSPI will fail to process that mapping and configurations will not be applied.
Let’s look at some common tasks for managing the Application Mappings:
Add new application mappings:
Create the application mapping definition rules in a text file e.g. NewMappings.txt. Import it with option overwrite=false. This will append new application mapping definitions from NewMappings.txt to the system.
To delete some of the application mappings, Export the application mappings to a file using export option and then delete the lines which needs to be removed and import the file using overwrite=true option.
Backup and Restore the application mappings:
Run the command line tool with export option. This will back up the application mappings defined in the system and export into a file.
The NNM iSPI Performance for Traffic is optimized to provide the best performance while processing certain patterns of application mappings. Do keep in mind the best practices while defining custom application mappings to effectively visualize application traffic even for very large networks carrying a huge traffic volume.
About the author: Nirupama has been in HP NMC team for over 8 years with experience in testing different products in the NMC portfolio like NNM and different Performance iSPIs. She is presently with the NNM iSPI performance for Traffic team.
Nirupama has M.Tech degree in Computer Science from University of Mysore, India.
The whole BSM solution including network management will be on display at HP Discover June 2-4 in Las Vegas. Stop by to get a demonstration, ask questions or just say hello. Uncover the unknown.