Finding endpoints
Problem: On certain Windows versions, the Find Endpoint job cannot locate the managing switch correctly.
Explanation: The Find Endpoint job does the following:
- Executes a traceroute command to the target, which allows TrueSight Network Automation to figure out the closest router to the target.
- On the closest router, it executes:
- show arp to find the MAC address of the target and the interface of the target is returned.
- show cdp neighbor to check if the interface of the target, if found, is actually connected to another device.
- If another device is connected to the interface, TrueSight Network Automation logs into the target and repeats step 2.
- Repeats step 3 until no neighbor is detected, which means that the target is connected to the current device.
For the Find Endpoint actions to work, all devices between the 'managing router' (closest router to the target) and the 'managing switch' (switch on which the target is connected) must all be managed by TrueSight Network Automation. Also, the current implementation only supports Cisco IOS and CatOS devices and all these devices must have cdp (Cisco Discovery Protocol) enabled.
User response
The issue has been fixed in version 8.9.01. If you have modified the value of tracerouteLastLine before upgrade, make the following changes in the BCAN_DATA\global.properties file after upgrade:
Search for the word trace.
The following code snippet is an excerpt of the global.properties file:# Following are the values for Windows
#tracerouteCmd=tracert -d
#tracerouteRegex=^\\d+[\\s*|\\S*]*?(\\S*)$
tracerouteLastLine=4- Comment tracerouteLastLine by adding '#' and set its value to 3.
- Save the file and restart the web service.
When you retry, the Find Endpoint job grabs the last line.
Related topic