This article is meant as a deep dive for Cloud-Link deployments. As you familiarize yourself with Cloud-Link deployments you'll find the call outs below are comparable to switching customer over to a new ISP. Please review the other support articles to familiarize yourself with other useful topics. This is meant solely to assist with Cloud-Link deployments.
Cloud-Link (Lite, Standard subscriptions)
4 LAN ports
1 Network segment (254 clients)
Cloud-Link Pro (Pro Subscriptions)
8 LAN ports
Up to 4 Network segments (Combination of Wired or wireless networks) at 254 clients each (1k clients)
Article for Pro multi-network setup:
Survey: Customer Site Review
1. ISP performance
Make sure customer has a solid ISP provider
2. ISP WAN - Is the modem in bridge mode or router mode? Please be sure to familiarize yourself with our Partner Config Tool before you go onsite if you need to set a static IP (When in bridge mode)
Decide whether to use the Cloud-Link's DHCP server or not. If the customer has an internal DHCP server, you can turn off the Cloud-Link's DHCP and let the local server handle it.
Warning: Make sure their existing DHCP server is not running on the existing router your replacing. If it is, prepare to replace it with another DHCP server or leverage the Cloud-Link's DHCP during cutover.
- If using the Cloud-Link's DHCP, make sure static devices are outside of DHCP scope.
- ISP provided DNS servers are not compatible with OmniNet services.
4. DNS Server
- If using an internal DNS server(s), AND using the Cloud-Link DHCP: update the DNS server setting in the MDSMANAGER.com portal to use your internal DNS servers.
- If using an internal DNS server(s) AND NOT using Cloud-Link DHCP: Your existing DHCP server is managing this
- If you are needing to use custom DNS server(s) with Cloud-Link DHCP: Update your Cloud-Link's DHCP server settings to your custom DNS server of choice
- If using external DNS server(s) AND NOT using Cloud-Link DHCP: Your existing DHCP server is managing this
5. Client Static IPs
Review and find out what static devices customer has on site. Make sure to locate any devices that may need their static information updated at cutover time. (Printers, servers, network camera systems, etc.)
Note: ISP provided DNS servers are not recommend when on Cloud-Link
- Note which devices are using DNS ISP and prepare to update accordingly
- Be sure to check for any DNS forwarding to ISP DNS servers as well (Typically leveraged when using internal DNS servers)
6. Port Forwarding
Identify any existing port forwarding needs and make sure you have the right subscription. Plus subscriptions include port forwarding IPs. Speak with your OmniNet agent if you have questions on subscription types.
7. DSL and MTU
If customer ISP has DSL there is likely going to be an MTU adjustment needed. Read the following OmniNet article and speak with ISP about the possibility of adjusting MTU to account for additional packet padding as per article:
1. When your receive the Cloud-Link you are going to install, run through the setup wizard and plug it into a free LAN port from your office. Make sure the network settings match what your going to install at your client and that traffic is flowing correctly etc. Run a Shieldtest from your Shieldtest.com URL
2. Engage support team for any questions or for seeing if scheduling assistance for your install time is available before deployment
1. Hang off internal network before disrupting production and use a laptop verify Cloud-Link is online and testing is good to go
2. Install Cloud-Link in-line in front of client traffic with WAN port on uplink and internal clients hanging off the Cloud-Link LAN ports.
3. Test to make sure the customers services are functional (Email, Phones, Printers+Scan to email, Web Browsing, Port Forwards)
4. Run Shieldtest
- ISP Provided Email Services: ISPs may blocking incoming SMTP connections from another network. When switching to OmniNet, your customers connections will be sourcing from OmniNet network and not their own. Be careful to review with ISP email hosting provider to make sure this will not be an issue. Some allow connections as long as its secure SMTP. Again consult with ISP Email hosting provider as to whitelist the IP or to let you know what ports to use for SMTP if coming from outside their network.
- External DNS records - If hosting services onsite, be sure to review customer external DNS records and prepare to update to the port forwarding IP provided by your OmniNet subscription (Make sure you signed up for a port forwarding subscription as this is needed!!!)
- ISP DNS Servers - ISPs tend to block DNS queries from networks no their own. Don't use ISP DNS servers.
- Familiarize yourself with the Partner config tool for setting static IPs. If you have question on how to use it, contact our support team.
- RESET BUTTON - DO NOT HIT IT...unless OmniNet support is asking you to. You will be required to use the Partner Config Tool in the link above to fix this.
- Unreliable ISP - Business internet is a must. Reliable business internet is even better. Make sure you reviewing the customers network. When you put tunneling services over an unreliable foundation, it wont make for the ideal experience
Additional Troubleshooting resources: