Forum Discussion
AltocumulusBig-IQ: VS connection/pool stats visible, but Virtual Server health status not displayed
I have version 8.4.0 Big-IQ and 17.1.3 Big-IP VE(Azure). Required communication is flowing from what I can tell between Big-IP<->DCD and Big-IP<->CM and necessary ports open. However, when I enable stats collection, it comes back with 'Version: not available" for Stats Collection Agent. In the CM restjavad logs, it mentions that Big-IP doesn't have version(8.1.0.1), so keeps trying to reinstall version 8.1.0.1 continuously. Although Big-IP clearly does have that version downloaded/installed from Big-IQ. I have other devices with same version of iapp.analytics and its fine.
Main issue is that we cant see Virtual Server health(green/red). Although when I go to 'Monitoring' tab, I can see Virtual Server/Pool connection stats once I 'Enable' stats. So stats are being sent from Big-IP VE.
I removed/re-imported services but that didn't help. Im not sure if I need to clear-rest-storage on Big-IP. Although Im hesitant to do that, since license is managed from Big-IQ. Last resort could be remove devices completely and re-add.
This never worked for this particular HA pair. Configuring stats collection is new for this pair.
Thoughts? Anybody have similar issue?
This is now resolved. I noticed we had 2 self-ups configured on the DCDs. One to push stats from Big-IP, however we have another that is the official discovery IP for the DCD, that was used to transfer app and retrieve VS/pool object status. I missed that on firewall drops and routes. So glad it ended up being more straight forward.
from F5 Document........."Although the BIG-IP system pushes the statistics data to the DCD, bi-directional connectivity using port 443 is still required. The DCD retrieves object status (online, offline, disabled, and so on) by connecting to the BIG-IP and transferring the Analytics iApp output file."
4 Replies
- Anoop_Jayadharan
Cirrostratus
Did you try restarting the restjavad and restnoded services on either end?
jparri2323Anoop_Jayadharan, only on big-ip side for now, as other big-ip devices are working properly. However, yes I was looking to go ahead and do that on Big-IQ as well after hours just in case. I will respond back with results. Also, I have a case open with F5.
- jparri2323
Anoop_Jayadharan, restarted services on both ends but no luck. I'll see what F5 has to say. In the end, something might just be out of sync and device removal/re-add might be last resort.
- jparri2323
This is now resolved. I noticed we had 2 self-ups configured on the DCDs. One to push stats from Big-IP, however we have another that is the official discovery IP for the DCD, that was used to transfer app and retrieve VS/pool object status. I missed that on firewall drops and routes. So glad it ended up being more straight forward.
from F5 Document........."Although the BIG-IP system pushes the statistics data to the DCD, bi-directional connectivity using port 443 is still required. The DCD retrieves object status (online, offline, disabled, and so on) by connecting to the BIG-IP and transferring the Analytics iApp output file."
