Forum Discussion
BIG IP DNS Virtual Server Auto Discovery with RD
Guys
I am wonder if you can help. I am struggling to get Auto discovery working between my BIG IP DNS and LTM appliances. The are running 13.0 HF3. I just cant figure out why this is failing. All appliances are running the same version of big3d. They have all exchange certs. iqdump is showing traffic, however nothing is getting enumerated for the VS on the LTMs. For example
<!-- Connected to big3d at: ::ffff:172.16.32.250:4353 -->
<!-- Subscribing to syncgroup: default -->
<!-- Sat May 18 23:12:50 2019 -->
<xml_connection>
<version>13.0.0</version>
<big3d>big3d Version 13.0.0.3.0.1679</big3d>
<kernel>linux</kernel>
<!-- Sat May 18 23:12:56 2019 -->
<server>
<pkts>1307710</pkts>
<pkts_in>834222</pkts_in>
<pkts_out>473488</pkts_out>
<tot_bytes>588972246</tot_bytes>
<tot_bytes_in>177526767</tot_bytes_in>
<tot_bytes_out>411445479</tot_bytes_out>
<cpu>0</cpu>
<uptime>20017</uptime>
<active>1</active>
<maintainance>0</maintainance>
<big3d_log_level>notice</big3d_log_level>
<monitor>0</monitor>
<snmp>0</snmp>
<path>0</path>
<trace>0</trace>
<monitor_active>0</monitor_active>
<snmp_active>0</snmp_active>
<path_active>0</path_active>
<trace_active>0</trace_active>
</server>
What am i doing wrong?
Even if I manually add a VS on the DNS appliance, it tells me the VS is down with a big3d timeout error.
- Lokesh
Nimbostratus
When experiencing auto-discovery issues, you can use the following troubleshooting steps to determine the root cause:
- Confirm that the BIG-IP virtual servers do not use address translation
- Verify time synchronization
- Confirm iQuery communication
- Verify that the big3d process is broadcasting the virtual server and link data
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com