For a Cloud-Link that was previously stable (Not a new installation)
- Power Cycle the ISP modem followed by the Cloud-Link
- Check with the ISP to make sure there are no issues on their end
- Swap the network cables out for known good cables (From Cloud-Link to uplink and downlinks)
- Check if there are power outages in the area, and confirm the Cloud-Link has a reliable power source (Recommend the Cloud-Link is be installed with the use of a reliable UPS to connect networking equipment in order to help filter power surges and power outages and also to help protect equipment)
Check for Upstream Issues (Cloud-Link, Uplink/Modem, ISP and path to MDS Data Center)
- Check for ISP issues - If you experience a sudden onset of symptoms on an install that was previously fine and there have been no other changes, it is very possible that the ISP is experiencing issues. A call to ISP is recommended to rule out that possibility and others. You can also test by checking for packet loss along the route to our datacenter.
To do this: First, identify the datacenter public IP address. You can do this by performing a google search for “whats my ip” while connected to the Cloud-Link OR you can refer to the Mdsmanager.com Cloud-Link landing page for the Cloud-Link in question.
While NOT on MDS, directly connected to modem test the following:
- Ping 18.104.22.168 and look for drops/timeouts or very high latency. We recommend using ping –l 800 to increase the packet size. It will make dropped packets more obvious
- Run Winmtr to the Cloud-Link's public/datacenter IP you got from above - look for packet loss along the path
- Is this site on DSL? If so, check the MTU. - Make sure they are not having fragmentation issues. If they are, this may require a MTU adjustment on the modem. To test for MTU issues, go to http://www.letmecheck.it/mtu-test.php and run the test while directly connected to their modem (Not through MDS) and send MDS support a screenshot of result. If the larger number is 1500 then no further changes are likely needed.
- Check to make sure the line is not saturated. - Is the customer on a shared subscription? If other devices are saturating the line upstream it can create issues for the Cloud-Link. Test #1 could give a clue about this. The ISP may let you know the line is being saturated if you call in.
Check for Downstream Issues (From Cloud-Link to internal network)
- Disconnect downstream devices - Leave the Cloud-Link connected and disconnect all other downstream networks. If the Cloud-Link remains stable, it suggests a downstream issue (internal network issue).
If the issue is downstream, the following steps can help.
- Check for wired network loops - Did someone perhaps cause a network loop? This will wreak havoc on any network. Make sure no one recently started adding network switches or plugging in loose cables. The most effective way to narrow this down is to disconnect downstream portions of the network and see if it stabilizes and slowly plug in the downstream devices until you find the loop. Ask if any technology vendors came in recently to modify any network attached equipment.
- Check for wireless network loops - Did someone bridge their wired and wireless adapters? This may cause a slower network loop but can still cause major issues.
- Check for bad switches or bad NICs - Sometimes switches, switch ports, or NICs can go bad. Using the isolation method and slow re-introduction from check # 2 above can help identify this as well..
Check MDS hardware
- Upgrade the Firmware - If the Cloud-Link is very unstable, it is not recommended to attempt a Firmware update. However, if it only goes down occasionally, ask support if there is a newer, more stable firmware. If there is, check to see when the client has a 10 minute window for support to push the new Firmware upgrade to the Cloud-Link to see if the newer firmware helps relieve the symptoms. You can also try connecting the Cloud-Link to another network to see if it stabilizes before upgrading the firmware.
- Swap the Cloud-Link - Do you have a spare Cloud-Link? Test with a different Cloud-Link to see if issues subside. If they do, this would identify an issue with the specific Cloud-Link.