Project Drivers
- Eleven locations connected using expensive MPLS and dedicated T1 circuits
- Remote connectivity couldn’t be centrally managed
- Client’s existing connectivity provider would only support the equipment provided by them
- Those configurations were static and didn’t support a move away from MPLS and/or T1
Solution Components
- Meraki MX Firewalls with internet connections
- MX100 Firewalls at the main IT office
- MX64 Firewalls at remote locations, remotely implemented by an s4nets’ engineer
Impact
- Using Meraki MX Firewalls to provide software-defined connectivity provided the client with centralized management and control over how individual sites were managed
- Redundant connectivity at the main office minimizing outages
- The Return on Investment (ROI) for removing MPLS and T1 circuits and moving to SD-WAN paid for the hardware and implementation services in five months