RLink PDU — Unable to Connect to Network
Step 1 – Check Physical Connections
- Verify the Ethernet cable is securely connected to:
- The R-Link network port
- The network switch port
- Disconnect and reconnect the cable on both ends.
- Check the link/activity LEDs:
- On the R-Link network port
- On the switch port
Expected Result
- LEDs should be solid or blinking.
If No LEDs Are Present
- Try a different Ethernet cable.
- Try a different switch port.
- Test with a known working cable/device.
Step 2 – Verify the Switch Port
- Confirm the switch port is enabled.
- Ensure the port is not disabled or blocked.
- Verify the correct VLAN is assigned.
Ask the Network Team to Confirm
- Port status is UP
- Correct VLAN configuration
- No port security restrictions
- MAC address is visible on the switch
Step 3 – Check IP Address Assignment If Using DHCP
- Verify the DHCP server is reachable.
- Check whether the R-Link device received an IP address.
Verify the Following
- IP Address
- Subnet Mask
- Default Gateway
- DNS Server
Common Symptoms
| Symptom | Possible Cause |
|---|---|
| 169.x.x.x IP | DHCP issue |
| No IP address | Network/VLAN issue |
| Wrong subnet | Incorrect VLAN |
Step 4 – Test Network Connectivity
- Ping the default gateway from the device or connected system.
Example:
ping <gateway_ip>
- Ping another device in the same network.
- Ping an external address if internet access is required.
Expected Result
- Successful replies received.
If Ping Fails
- Check VLAN configuration.
- Check routing/firewall settings.
- Verify gateway availability.
Step 5 – Verify VLAN Configuration
- Confirm the R-Link device is connected to the correct VLAN.
- Verify switch port configuration:
- Access mode or trunk mode
- Native VLAN settings
Common Issue
- Device connected to incorrect AV VLAN.
Step 6 – Reboot the R-Link Device
- Perform a normal reboot of the R-Link device.
- Wait for the device to fully boot.
If Issue Persists
- Power off the device completely.
- Wait 60 seconds.
- Power the device back on.
After Reboot
- Check if network LEDs return.
- Verify IP address assignment again.
Step 7 – Access the Device Web Interface
- Open a web browser.
- Browse to:
http://<device_ip>
or
https://<device_ip>
Expected Result
- Web interface loads successfully.
If Web Interface Does Not Open
- Verify device IP address.
- Confirm PC is on same network.
- Check firewall restrictions.
- Verify device is online.
Step 8 – Check Firewall and Security Policies
- Verify the device is not blocked by:
- Firewall policies
- NAC/802.1X authentication
- Network security restrictions
- Request the IT/network team to whitelist the device if necessary.
Step 9 – Check for IP Address Conflict
- Verify no other device is using the same IP address.
- Check DHCP reservations if applicable.
Symptoms of IP Conflict
- Intermittent connectivity
- Random disconnects
- Duplicate IP warnings
Step 10 – Verify Firmware Version
- Check the currently installed firmware/software version.
- Compare with the latest approved version.
Outdated Firmware May Cause
- Network instability
- DHCP failures
- Device disconnects
- Update firmware if required.
Step 11 – Perform Factory Reset (Last Resort)
Perform only if approved and configuration backup is available.
- Backup current configuration.
- Perform factory reset.
- Reconfigure network settings.
- Reconnect device to the network.
How do I manage devices remotely so that I don't need to escalate issues as they happen?
Our SPORTrack platform gives you the ability to remotely monitor and manage all of your devices, across the globe. Check out the SPORTrack platform here.