Submit a ticketCall us

whitepaperYour VM Perplexities Called, and They Need You to Read This.

Virtualization can give you enormous flexibility with future workloads and can be a key enabler for other areas, like cloud computing and disaster recovery. So, how can you get a handle on the performance challenges in your virtual environment and manage deployments without erasing the potential upside? Learn the four key areas you need to be focusing on to help deliver a healthy and well-performing data center.

Get your free white paper.

Home > Success Center > Netflow Traffic Analyzer (NTA) > NTA - Knowledgebase Articles > Top 100 Endpoints: Error while loading legend

Top 100 Endpoints: Error while loading legend

Created by Brian O'Donovan, last modified by MindTouch on Jun 23, 2016

Views: 969 Votes: 1 Revisions: 6


The following error is displayed when viewing the Top XX Endpoints resource in NTA:

Error while loading legend

The following error is also displayed when navigating to the Endpoint Details view for a specific endpoint.

Not a valid IPSort


All NTA versions


This occurs when the endpoint hostname has invalid characters. NTA complies with RFC 952 and valid characters for hostname are: [a-z][A-Z][0-9].-


Note: Simply replacing the hostname in the SQL database will not resolve the issue as the name will returned to the previous value after seven days.

Perform any of the following options to permanently resolve this:

Option 1 (preferred)

Rename the device in DNS so that the hostname is compliant with RFC 952. The next tine DNS name resolution is performed by NTA [default 7 days, Configurable from NTA Settings page] the correct hostname will be updated and the issue will be resolved.

Option 2

  1. In the SQL database, locate the problematic hostname in NetFlowResolvedAddress table.
  2. Note the hostname's IP address.
  3. Go to C:\Windows\System32\drivers\etc and add the following row to the host file:
    IP address from step 2] [new hostname]
  4. On the website, go to the NetFlow Settings page.
  5. Set the Default number of days to wait until next DNS lookup field to 1 day.
  6. Wait 1 day until IP Address is resolved.
  7. Once the charts are displayed again, change the Default number of days to wait until next DNS lookup field back to 7 days.

Option 3

Note: In the following example, the hostname with the issue is E:Aruba Wireless Controller. The ":" is the invalid character.

On the main server, use the URL: http://localhost/Orion/TrafficAnalys...%202%20Minutes (replace XXX with node ID that collect Flows with this IP address.


  1. Locate the IP address (column IPAddressSort) in the SQL database for the hostname E:Aruba Wireless Controller and use it in the link. For example, http://localhost/Orion/TrafficAnalysis/NetflowEndpointDetails.aspx?NetObject=NE:181018000007;N:XXX;T:Last%202%20Minutes
  2. Press Edit and change the hostname in a valid format.
  3. Wait 10 minutes and display TOP XX Endpoints for last 5 minutes.


Last modified