0

CLI + unifi = no device names

I have a unifi UDM SE and have installed the CLI and selected allow device names.

For a while it worked fine., then I found that all of the device names in the next DNS logs no longer display the names provided from unifi.  logs now show names like this: Device #BNTEA

 

when i uninstall and then reinstall the CLI, the logs show the correct device names for several minutes, then revert back to the Device #BNTEA type names.

 

Anyone have any ideas?

1 reply

null
    • Sarah.3
    • 1 mth ago
    • Reported - view

    It sounds like you're experiencing an issue with your UniFi UDM SE where the device names revert to generic identifiers after a short period. Here are some steps you can take to troubleshoot the problem:

    1. Check Device Naming Settings:

      • Ensure that the option to allow device names is still enabled in the UniFi Controller settings. Sometimes settings can revert after updates.

    2. Firmware Update:

      • Make sure your UDM SE is running the latest firmware. Updates often include bug fixes that may resolve issues like this.

    3. Reboot the UDM SE:

      • Try rebooting your UDM SE. This can help refresh connections and settings.

    4. Clear DNS Cache:

      • If the DNS cache is causing issues, clearing it might help. You can do this through the UniFi Controller.

    5. Check DHCP Settings:

      • Ensure that the DHCP settings are correctly configured. If devices are not consistently getting the expected names from DHCP, this could lead to the issue you're seeing.

    6. Monitor Logs:

      • Keep an eye on the logs after making these changes. Look for any errors or warnings that could provide more context about why the names revert.

    7. CLI Configuration:

      • After reinstalling the CLI, ensure that any configuration changes you made are saved correctly. Sometimes, changes may not persist if they aren’t applied properly.

    8. Contact Support:

      • If the issue persists, consider reaching out to Ubiquiti support for assistance. They may have additional insights or solutions for this specific problem.

    By following these steps, you should be able to identify the root cause of the issue. Let me know if you need further assistance!

Login to reply

Content aside

  • 1 mth agoLast active
  • 1Replies
  • 124Views
  • 2 Following