Last Modified: Oct 13, 2023
Opened: Oct 20, 2022 Severity: 3-Major
A TCP connection establishes from BIG-IP to BIG-IQ.
An extra Java connection is listed under netstat.
When refreshing the stats, BIG-IP also fetches the stats from BIG-IQ, to fetch the stats from BIG-IQ, a Java connection establishes from BIG-IP to BIG-IQ. Here, the BIG-IQ is discovered in the BIG-IP. If BIG-IP is not discovered in BIG-IQ, there the issue does not exist.
Updating the property "rest.common.device.automatic.refresh.enabled" to "true" from /etc/rest.BIG-IP.properties, the connection does not establish from BIG-IP to BIG-IQ. Note: We do not have a workaround for SSL Orchestrator. Workaround is not applicable for SSL Orchestrator.