Error / Status | Fault - MTR Not Connected when using a hostname in MTR component

Learn how to troubleshoot and resolve the issue of the MTR component not being connected when using a hostname, ensuring that your system functions smoothly and efficiently.

Updated at March 5th, 2024

Affected Products

Hardware Model/Series
Core processors
Software
QDS 9.9.0, 9.9.1, 9.4.5 LTS

Message

In the MTR component in Q-SYS Designer Software, the IP Address / Host field will accept either the IP address or hostname of the MTR compute device.  When using a hostname, the status of the MTR component is “Fault - MTR Not Connected”, but when using the MTR compute's IP address the status is OK.


Definition | Causes

When the MTR component is configured to connect via hostname, and the MTR compute is scheduled for automatic ,nightly reboots, it is possible that the underlying IP address may change with a new assignment from the DHCP server over extended durations. If the IP address changes does change, the MTR component will lose connectivity to the MTR compute and enter a fault state.


Solution | Workaround

  • In Cores running firmware 9.9.0/9.9.1, a reboot is required to pick up the proper IP address.
  • Configure a DNS server in Core Manager under the Network Basic section. Contact the network administrator of the network on which the MTR compute resides for details on which DNS server should be used.
  • If a Core firmware version below 9.10 is required, set a static IP address for the MTR compute. This will prevent the MTR compute from getting a new IP address from the DHCP server when it reboots for update.
  • If the MTR compute requires a DHCP address configuration, update the core to firmware 9.10.

Note

This issue is resolved in QDS 9.10. Use the suggestions above if using LTS.