After creating an application mapping for port 443 all 443 traffic has been renamed to that custom application name
search cancel

After creating an application mapping for port 443 all 443 traffic has been renamed to that custom application name

book

Article ID: 106200

calendar_today

Updated On:

Products

CA Network Flow Analysis (NetQos / NFA)

Issue/Introduction

After creating an application mapping for port 443 or another port, all 443 traffic has been renamed to that custom application name in Protocol Trend Reports. 

 

Environment

Release: RAIB1H99000-9.3-Network Flow Analysis-Interface Bundle-Hardware
Component:

Cause

Improper configuration of the Destination Port field when creating an application mapping.

The "Destination Port" field should be different then the original port and it should be a port number ideally over 65000 so that it is not in use by another application.


User-added image

Resolution

To resolve this follow the steps below on 9.5.0 and earlier:


1.  Go into the Admin->Application Definitions page and delete the Application Definition that caused the problem.


2.  On the Console server open a command prompt  and run:

mysql reporter 
delete from protocol_domains where description not in(select description from application_mappings); 


3. Recreate the Application Definition with a destination port over 65000 that is not currently in use by any other application like below:


User-added image