Reviewing log data
- /logs/: Includes BlueCat Gateway system logs.
- /app_log/: Includes logs specific to the BlueCat Overlay for Microsoft application.
- /app_data/: Includes JSON-formatted files that contain data gathered from Microsoft servers.
If you suspect that the data is not processed as intended, review the log files within the /app_log/ directory. For further troubleshooting, you can review the JSON files within the /app_data/ directory to analyze the data that has been imported from the Microsoft servers.
Reviewing common errors
When reviewing the execution logs, you might see errors and warnings when importing data from your Microsoft DNS and DHCP servers. Log files use the following naming convention: overlay_YYYYMMDD_HHMMSS.
The following table outlines error messages that can be found in the log files, including a possible cause of the error and suggested actions to resolve the issue.
|Log message||Possible cause||Suggested action|
|Option ID <id>, MSFT Name: <option name> not implemented yet||The specified DHCP option is not yet supported.||If this option is critical to your infrastructure, contact Customer Care for assistance.|
|Unable to add DNS record <record> zone (<zone name>). Missing Linked DNS Record||The associated host record does not exist in Address Manager.||Verify if that host record was skipped due to a missing network or due to an invalid format. Ensure the host record exists in DNS and can be added to Address Manager successfully.|
|Unable to add the IP addresses to Host record. Network not found.||The IP address could not be added to a Host record, as a network in Address Manager could not be found.||Import the network if it belongs to a DHCP Scope. Otherwise, consider creating the network manually.|
|Unable to add range due to overlap with gateway.||A DHCP range cannot start with first address in the network.||Verify if the range overlaps with default gateway or router address.|
|Too many DHCPv4 roles in network||The network cannot have more than 2 DHCP Roles. This can indicate a rogue or misconfigured DHCP Server, or that there is an overlapping network deployed to different DHCP servers.||Verify that the DHCP network does not overlap with an existing "managed" network in Address Manager. Alternatively, you can import this network in a new configuration.|
|Invalid MAC address for IP||The MAC address is not a valid 12 digit hexadecimal number. This occurs if the DHCP server recorded client UID instead of the hardware address.||If the IP address is a reservation, consider updating the MAC address.|
|No data returned by server||This error can be logged for different reasons that can result in
the unsuccessful execution of remote Powershell commands. The most
common failures are due to the following:
||Verify the connection information and ensure that the Windows Server is running DNS or DHCP services.|
|Zone Primary could not be found or Zone Type not supported||The DNS Zone configuration did not return a valid IP address of the Primary DNS Server. This can also occur if the zone type is not supported by the solution.||Verify the DNS configuration on the Microsoft Windows DNS Server for valid IP address or name.|