Unable to identify any F5 Devices on Network

This issue was handled through email, but I will post the solution here for others who may experience the same problem.

 

Handled through email:

 

 

This is a result of not authorizing the update of the big3d agent. If you’re using the Discovery Wizard, there is a check-box to authorize the update. If you’re using the command line, there is an option (/Discover:UpdateBig3d) to allow the update.

 

 

This updates the Big3d agent (/usr/sbin/big3d) to the version that ships with 10.0.1 on Big-IPs that you discover. If you are using the Big-IP as a GTM, you may notice a short (~30 second)disruption as GTM re-initializes.

 

 

If you are using LTM only, there is no effect, unless the LTM is being monitored by a GTM, the LTM will appear to be offline for a brief period of time (less than a minute), and this could cause GTM to redirect traffic to another data center until the big3d update is completed. Therefore, if you are using GTM, you should discover LTMs from each data center separately so they don’t go offline all at once.