Discovery: In the Discovery Access, why are some IP's skipped with an End State of Opt1stScan or OptNotBestIP?

Version 2
    Share This:

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.


    BMC Discovery


    BMC Discovery 11.3


    BMC Discovery



    Scenario: A device (i.e. a network device or server) has three different IPs:,, and All of these IP's are being scanned in a single Discovery run. The results might look like this:, result success, result Skipped - Opt1stScan, result Skipped - Opt1stScan

    Why are the final IPs skipped?

    (For a Spanish language version of this KA please see 000182389) 




    Legacy ID:KA345994


    In this case, Discovery has scanned first, and the scan was successful. For the other two IP's, the scan gets as far as the list of interfaces, then realises it's the same device that has already been scanned, so it stops there with a status of "Opt1stScan". The end result is only one Network Device node that includes all the interfaces.

    On subsequent scans, Discovery remembers which IP the switch was discovered on (the "best" IP), and doesn't attempt to scan the others. The results might look like this:, result success, result Skipped - OptNotBestIP, result Skipped - OptNotBestIP

    This continues until the "Scan optimization timeout" (by default 7 days - see Administration / Model Maintenance) is reached. Then another "initial" scan will be done against the IP's. This is done because a given IP may have been reassigned to another device, so it can't be skipped indefinitely.

    The term "best IP" is somewhat misleading. It simply denotes the endpoint that Discovery has processed first. It's not possible to configure which IP Discovery will choose. 

    This behavior is by design.



    Article Number:


    Article Type:

    Solutions to a Product Problem

      Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles