Schedule assistance ahead of time
If installation assistance for the OmniBridge is needed, please schedule ahead of time.
Schedule the installation a few days ahead:
1 hour slots are available M-F from 9AM to 5PM and are first come, first serve, with Holiday and other exceptions.
(After hours available for extra fee. Consult your OmniNet sales rep for details)
WAN network considerations
Does the customer have a static IP from their ISP? Do they use it?
Do you have to configure the OmniBridge with a static IP?
>>>!!Have this information ready before production cut over!!<<<
If ISP mode is simply a DHCP enabled LAN network, an available LAN port on the modem is all that is needed.
Preconfigure LAN network
Bring the OmniBridge (OBR) online before taking to customer site (Port 1 is WAN)
Configure the first Zone (Port 6) to match the customer's network scheme if replacing their router. Or set to desired subnets.
>>>Do not use ISP DNS servers. Check DHCP servers and DNS servers for forwarders to make sure to switch away from any ISP DNS servers<<<
Connect a test computer and make sure you get an IP in the DHCP range you expect.
Test Internet connectivity from the test computer.
Verify you see the DCHP lease in the management portal.
Multiple LAN networks (Zones) are available based on subscription type.
-> Lite = 1 Network, Standard=3 Networks, Pro=12 Networks
Customer Site Survey Suggestions
This section is critical if you are not typically in charge of the customer's Firewall and network management.
Check existing LAN for static IPs
Site survey would reveal if any devices are configured with static IPs. As such, you need to identify this and be ready to update the DNS servers if they are relying on ISP DNS servers. This will not work. Please be ready to switch device to use public DNS server.
>>>Make sure any static IP device do not fall within your configured DHCP scope<<<
Check existing DHCP Server
DHCP server is included with your OmniBridge. Make sure to set the scope outside of any statically configured IPs.
Note: You are not required to use OmniBridge's DHCP server. If you have a local DHCP server and prefer to use it instead, be sure to turn off the OmniBridges DHCP server. Additionally, make sure your local DHCP server is not handing out DNS server from the customers ISP.
Existing Port forwards
Make sure to identify ANY public facing DNS records that need to be updated once the cutover is live, BEFORE GOING LIVE.
It is critical to identify any port forwarding as this will require to be setup with the new dedicated IP address provide by OmniNET. Make sure this subscription has a port forward IP if needed! Go ahead and add port forward entries to the Remote Access section labeled "Port Forwarding".
>>>Very important if customer has onsite email server or website. This is important to prepare ahead of time since public DNS propagation can take some time.<<<
Make sure you have access to any wireless routers and or access points that will be used to bridge wireless clients to the OmniBridge protected network.
>>>If you're leveraging former router, make sure you understand how to switch the router to access point mode to prevent secondary routers<<<
Go ahead and add your SSL-VPN users to have those accounts ready to go.
You can test to make sure you can ping the OmniBridge gateway if you have it online.
3rd Party Tunnels
Be sure to identify any live site to site tunnels that may be configured with 3rd party vendors. This should be planned ahead of time with the vendor. Contact OmniNet support ahead of time to help guide you on what we will need.
>>>3rd Party Tunnels require cooperation from the vendor. Make the proper plans prior to live cutover!!<<<
Be sure to identify if any VLANs are being used on the network. If they are only on 1 flat network (For example PCs and VOIP phones have the same subnet), then this wont be necessary. If they do have VLANs, be sure to understand which VLANs are currently configured to match configuration on the OmniBridge.
Note: If VLANs are needed, we recommend you engage OmniNet support to discuss VLAN implementations prior to cutover