Q&A: How does the Hybrid Connector iApp work? – F5 Silverline Knowledge Base

Question

How does the Hybrid Connector iApp work?

Here is some additional info about how the Hybrid Connector iApp works:

The iApp uses the Silverline credentials entered to retrieve an API token (can be seen: F5 Silverline Portal > Config > Hybrid Configuration > API Tokens).
Then, if applicable, the iApp iterates through the Sync-Failover group to gather the BIG-IPs that need to be registered with Silverline. This happens if the device is not a standalone BIG-IP.
The iApp creates a Device Token for each BIG-IP, which is a combination of the each device's base MAC address and chassis id.
The iApp sends a registration call, using the API Token retrieved in Step #1, to define each BIG-IP to Silverline.
Each Device Token can be seen in the Silverline Portal, in the second column of the Hybrid BIG-IP Management page.
The iApp creates multiple configuration objects (data groups, iCall scripts, etc) which are used for multiple on-prem -> Silverline API calls (signals).
Connector iApp Signal Types:
1. Platform details can be found in the F5 Support Solution: SOL9476
2. Additionally, F5's Software Support Policy: SOL5903

Device Registration (from Step #4 above)
Health Check: The BIG-IP sends a Health Check signal to F5 Silverline every minute.
Inventory Check-In: 2x a day, the BIG-IP sends an inventory signal to F5 Silverline, that includes Platform (model) and software revision info.

All three of these signals can be viewed on the API Activity Log page within the F5 Silverline Portal, under the Audit section (Portal -> Audit -> API Activity Log):