Unable to resolve log source IP to hostname via DNS using TIBCO LogLogic LMI
Article ID: KB0077528
Updated On:
| Products | Versions |
|---|---|
| TIBCO LogLogic Log Management Intelligence | all versions |
Description
If your log sources device names do not update via DNS after the scheduled daily maintenance cycle then there are a few troubleshooting steps to take to determine why the hostname updates failed.
Issue/Introduction
This article provides troubleshooting steps for determining why some or all log sources' device names did not update via DNS in LogLogic LMI.
Resolution
Here are some troubleshooting ideas for determining why device names didn't update via DNS:
1. Ensure the global DNS refresh setting is enabled in the Administration->System Settings page. If it's disabled then enable it if all log sources without hostnames failed to update. If only some hostnames failed to update then confirm if their individual log source setting for DNS refresh is disabled (if the global setting is on) to explain why only specific log sources were affected. If the global setting is disabled then for the device names to be updated they must have their individual DNS refresh setting enabled.
2. Also, verify that the LMI appliance is configured with at least one DNS server (using its IP, not its hostname, to avoid relying on DNS) and that the DNS server is available and accessible from LMI. You can combine this with the next troubleshooting step to be verify both simultaneously.
3. Lastly, if only certain device names didn't update then perform a manual lookup of an affected device IP. This is known as a reverse lookup; forward lookups involve using the hostname to resolve to an IP address. Both forward and reverse lookups must be successful for the device name to be updated. You can use the nslookup command (logged in via the 'toor' account) on the appliance's command line to perform the lookup verification in both directions.
1. Ensure the global DNS refresh setting is enabled in the Administration->System Settings page. If it's disabled then enable it if all log sources without hostnames failed to update. If only some hostnames failed to update then confirm if their individual log source setting for DNS refresh is disabled (if the global setting is on) to explain why only specific log sources were affected. If the global setting is disabled then for the device names to be updated they must have their individual DNS refresh setting enabled.
2. Also, verify that the LMI appliance is configured with at least one DNS server (using its IP, not its hostname, to avoid relying on DNS) and that the DNS server is available and accessible from LMI. You can combine this with the next troubleshooting step to be verify both simultaneously.
3. Lastly, if only certain device names didn't update then perform a manual lookup of an affected device IP. This is known as a reverse lookup; forward lookups involve using the hostname to resolve to an IP address. Both forward and reverse lookups must be successful for the device name to be updated. You can use the nslookup command (logged in via the 'toor' account) on the appliance's command line to perform the lookup verification in both directions.
Feedback
Yes
No
Powered by
