UDP Application Mappings are showing up like "UDP-65510" instead of the name defined when creating the application mapping.
<Please see attached file for image>
When you create an Application Mapping in NFA, it updates several database tables including application_mappings, protocol_domains, and protocol_definitions.
When you create a UDP Application Mapping it only creates an entry for TCP in the protocol_definitions and protocol_domains tables. When data gets mapped to the new UDP application mapping, it will create an entry in protocol_definitions but doesn't create a corresponding row in the protocol_domains tables. NFA attempts to get the names from the protocol_domains table, if there is no entry in the protocol_domains table, it uses whatever is in the protocol_definitions table which defaults to just the protocol and port number like 'UDP-65510".
NFA 9.3.3 and earlier.
1. Go to the NFA->Admin->Protocol Names page.
2. Click "Select A Protocol"
<Please see attached file for image>src="/servlet/servlet.FileDownload?file=0150c000004AKEcAAO" alt="protocolname.png" width="780" height="338">
3. Search based on "Port Number" and "UDP Ports"
<Please see attached file for image>src="/servlet/servlet.FileDownload?file=0150c000004AKEaAAO" alt="portnumber.png" width="513" height="310">
And find the problem destination port and select it:
4. Once selected click "Edit Protocol" and update the "Protocol Name" field to what you want to be displayed and click Submit.
<Please see attached file for image>src="/servlet/servlet.FileDownload?file=0150c000004AKEbAAO" alt="protocolConfig.png" width="383" height="200">
5. Go back to the report and you should immediately see the new name reflected in your reports.
<Please see attached file for image>src="/servlet/servlet.FileDownload?file=0150c000004AKEZAA4" alt="graph.png" width="881" height="204">