ReadyLinks Switch Showing Offline in ReadyView

If your ReadyLinks switch is not showing online in ReadyView, work through the checks below in order. Most offline issues are caused by basic network connectivity, time sync, or DNS problems — confirming each item below will resolve the majority of cases.

Overview of checks

1. Check the ReadyView connection on the switch via console/Telnet/SSH
2. Verify the switch has a valid IP address
3. Verify DNS server configuration
4. Verify the switch's local time
5. Verify firewall configuration

1. Check the ReadyView connection on the switch

Connect to the switch via console, Telnet, or SSH and run the following command to view its ReadyView connection status:

GL-8xCH# show readyview connection all
--------- ReadyView Connection Information ---------
rlicloud_443
ReadyView Status: On
Connection Status: Connected
Authentication Method: Password
ReadyView File Status: Exists
--------- ReadyView Connection Information ---------
cloud_rl_io_443
ReadyView Status: On
Connection Status: Connected
Authentication Method: Password
ReadyView File Status: Exists

What to look for:

• Connection Status: Connected — the switch is successfully connected to ReadyView. If the switch still does not appear online in the ReadyView dashboard, contact our support team for further assistance.
  • If you removed the default superuser account or changed its password on the switch and its showing connected via the CLI command, but not in ReadyView please review this guide:  Changing the Default Password on ReadyLinks Switches 
• Connection Status: Not Connected — continue to the next troubleshooting steps below.

2. Verify the switch has a valid IP address

The switch needs a routable IP on its management VLAN before it can reach ReadyView. Run the following command to confirm:

GL-8xCH# show vlan interface
VLAN INTERFACE    TYPE    IPv4 ADDRESS/NETMASK/GATEWAY            SECONDARY IP    IPv6
----------------------------------------------------------------------------------------
VLAN-INTERFACE32  DHCP    10.10.32.11/255.255.255.0/10.10.32.1

What to look for:

• A valid IPv4 address, netmask, and default gateway should be listed for your management VLAN.
• If no IP address is listed, configure a VLAN interface with either a DHCP-assigned or static IP address.
• If using DHCP, verify the switch received a lease and that no IP conflict exists on the network.

How to configure a management VLAN and IP

Use the following commands to create a management VLAN, tag it on an uplink interface, and assign an IP address to the VLAN interface. Replace <vlan id>, the uplink port, and the IP details as appropriate for your environment. Valid port names include Ghn1–Ghn24, Fiber/G1, Fiber/G2, RJ45/G1, and RJ45/G2.

Static IP:

configure terminal
vlan <vlan id>
name management
switchport tagged ethernet <uplink port>
end
int vlan <vlan id>
ip address <ip-address> <netmask> <gateway>

DHCP:

configure terminal
vlan <vlan id>
name management
switchport tagged ethernet <uplink port>
end
int vlan <vlan id>
ip address dhcp

3. Verify DNS server configuration

ReadyView is reached by hostname, so DNS resolution must be working. Run the following command to check your DNS configuration:

GL-8xCH# show dns
Dynamic DNS mode
nameserver 8.8.8.8
nameserver 1.1.1.1

Notes:

• If the switch is using DHCP, DNS servers are typically pushed automatically.
• If the switch is configured with a static IP address, you will need to set DNS servers manually.

Test DNS resolution against the ReadyView cloud hostname using traceroute:

GL-8xCH# traceroute cloud.readylinks.io
traceroute to cloud.readylinks.io (168.61.23.187), 30 hops max, 38 byte packets

What to look for:

• The hostname cloud.readylinks.io should resolve to an IP address (shown in parentheses at the start of the output).
• If the traceroute is unable to resolve the hostname, review your DNS server configuration and confirm the configured nameservers are reachable.

How to manually configure DNS servers

If the switch is using a static IP address (or DHCP is not providing DNS), set the nameservers manually. Replace x.x.x.x with your primary and secondary DNS server addresses.

configure terminal
dns nameserver1 x.x.x.x nameserver2 x.x.x.x

4. Verify the switch's local time

Cloud services validate TLS certificates against the current time. A switch with an incorrect date or time will fail to establish a secure connection to ReadyView and appear offline. Run the following command to check the switch's local time:

GL-8xCH# show clock
Local Time:
        Tue  May  26  14:27:19  2026

What to look for:

• The displayed time should match the current local time (within a few minutes).
• If the time is incorrect, configure NTP on the switch. As a quick connectivity test, you can also verify the switch can reach time.google.com.

How to configure NTP (SNTP)

The following command points the switch at Google's public time server. Adjust the zone and time offsets if your switch should display local time instead of UTC.

configure terminal 
sntp client server-address time.google.com response-time 3 zone-offset <GMT #> time-offset 0

5. Verify firewall configuration

Ensure your firewall is configured to allow the following traffic through:

Still stuck?

Please reach out to our ReadyLinks support specialists for further assistance.