• Expected to run on port 443.

• Requires agent has correct SSL root certificates installed to trust Cisco Catalyst vManage.

• The vManage controller must be specified in Highlight with the DNS name listed on the SSL certificate.

• The agent must support a TLS client version that matches the TLS version on the vManage controller.
  Note: There is a option on the controller to Ignore certificate errors which disables all certificate validation. However, this is a security risk and not advised.

Highlight uses the following API calls to discover the devices and state of the network. Highlight only uses Read Only calls for all information collected. If you have any questions on how we use this information, please contact us.

Process Discovery Results

If selected, locations are created within Highlight using the vManage SiteID; otherwise all watches are created in a single Highlight location.

A watch is created for each interface discovered with the following characteristics:

port-type

“transport” (Additional port types may be added in the future)

af-type

“ipv4”

if-oper-status

“Up”

Once watches are created, they are polled for new data every 180 seconds.

• The poll requests are throttled to a maximum of 10 x vManage “total_cpu_count” (obtained during discovery).

• All responses from each batch of requests need to be completed before another batch of concurrent requests will be sent.

• Currently the polling of all watches is scheduled within a 90 second window to allow time for delays in API replies. The time between starting each poll for a given device remains 180 seconds.