Starting from version 8.9.03, BMC Network Automation is renamed to TrueSight Network Automation. This space contains information about TrueSight Network Automation 8.9.03 and the later service packs for 8.9. For earlier releases, see BMC Network Automation 8.9.

Finding the switch closest to an endpoint

A job with the Find Endpoint action returns the name of the closest switch to a specified problematic endpoint, and the port on which it is connected.

For more generic information about job creation, see Creating a job.

To run a Find Endpoint action

  1. On the Add Job page, select Add Action > Endpoint Actions > Find Endpoint.

  2. Enter information in the following fields:




    (Optional) Annotation assigned to the action.

    Bounding Span

    According to your security rights, allows you to select the Entire Network, Realm, or Group. When the Bounding Span is Realm or Group, you can use Filter Devices to select which devices to include in the action. Only routers and switches in this bounding span are visited during the search for the endpoint.

    Endpoint Address

    Enter the IP address of the endpoint.

  3. Click OK to add the action to the job.
    After a job run, the Job details page displays the input parameters and the completion status (for example, Succeeded or Failed).
  4. Select the status value in the Job details page to view the results in a pop-up window. The result shows the name of the managing switch and port, the traceroute transcript, and a list of the devices traversed by the action.


    • The Find Endpoint algorithm uses the traceroute command to find the IP address of the managing router for the endpoint.

      If the router has multiple IP addresses defined within it, and the IP address output of the traceroute command does not match the IP address stored in the TrueSight Network Automation application server database for the device, the algorithm fails. To work around this problem, the Configuration Profiled Dynamic field captures additional IP addresses from the configuration of Cisco IOS routers. These alternate addresses are checked during endpoint actions, in addition to the primary address of the device, when searching the database for the router. The Alternate Addresses Dynamic field is disabled by default, so if you need to work around this problem you must enable it, and then launch a Refresh Device Status Job to populate the field before attempting the endpoint action.
    • If a router in the traced path is an MSFC, the associated supervisor engine is treated as the next switch for reaching the target endpoint. Ensure that the supervisor engine (as well as the MSFC) is a managed device in the TrueSight Network Automation system, or the endpoint cannot be found.
Was this page helpful? Yes No Submitting... Thank you