Loading
search-img

dennis_reinhardt asked a question.

August 5, 2020 at 9:51 AM
Beacon - Discovery & Inventory Rule - "Calculating NMAP range strings" took 30 minutes in Discovery.log

Hi @ll

I noticed today that the step "Calculating NMAP range strings" on our beacons always takes about 30 minutes on average, which I consider to be very long and I wanted to hear your opinion about it.

Discovery & Inventory Rule for vCenter Scan - Discovery.log

 

- we've disabled the use of previously discovered devices, due to some issues

 

- Maybe it's possible to tweak the Beacon registry with some additional NMAP commands to peed up this process 
  • 2 answers
  • 173 views

  • dennis_reinhardt

    Hi,

    last week we've updated the customer system up to 2020 R1 On-Prem and the issue is now gone.

    Best,

    Dennis

    Selected as Best

  • JohnSorensenDK (Flexera Software)

    @dennis_reinhardt  

    I know that you've been approached by support on this issue.

    Please share your findings with the community if you believe others could benefit from its resolution once you've found the root cause.

    Thanks,

    Expand Post

  • dennis_reinhardt

    Hi,

    last week we've updated the customer system up to 2020 R1 On-Prem and the issue is now gone.

    Best,

    Dennis

    Selected as Best

Related  Product Forums


                     → Flexera One



                      → Snow Atlas



                      → FlexNet Manager



                      → Snow License Manager



                       → App Broker


       Need help finding an answer?


        Ask a Question →


+1.800.374.4353
CONTACT SALES SUPPORT HUB FLEXERA REVENERA
© 2026 Flexera. All rights reserved.
Privacy policy Terms and conditions Revenera Community Help
Loading
Beacon - Discovery & Inventory Rule - "Calculating NMAP range strings" took 30 minutes in Discovery.log