A: With Multapplied SD-WAN software, there is no need to create a VPN for voice. Our Quality of Service (QoS) profile allows you to define and manage high priority data to be placed in a priority queue or ‘Class of Service”.
A: With MNI SD-WAN, these IPsec tunnels and the “support” needed to maintain and manage them is a thing of the past. You create what we call a ‘Space’ on the Management Server, you then build the profile for the customer site on the Management Server. It is a few fields and pop downs. Place the customer in the space and all the “VPN” data is built for you. To add a new site, you build the site profile, add it to the Space and all sites in the space now know how to communicate to this new site.
A: MNI SD-WAN feature called Private WAN (PWAN) allows one to create a private virtual MPLS-like environment to securely connect all your sites. Choose from AES 128, AES 256 or Salsa20 256 encryption ciphers to keep your data private. This coupled with our proprietary tunnel technology that moves your data by the packet over multiple circuits, adds yet another layer of security to your data.
A: This depends on if you are a single site customer or a multi-site PWAN organization and where you want to put it. You can install the firewall at the site, placing the firewall between your LAN and the SD-WAN CPE. You can place your Firewall in the data center. The Firewall can be dedicated or could be FaaS (Firewall as a Service) provided by your SD-WAN provider.
A: Yes. Multapplied is fully white label so you’re able to license, manage, and control your own SD-WAN product under your brand name.
A: A key part of our product is a centralized configuration server. Technicians use a web application on this server to manage, monitor and report on each CPE.
You need to provide the following:
- Server hardware for the configuration server (can be virtualized).
- Server hardware for at least one, but preferably two aggregation servers (should not be virtualized).
- Bandwidth to the aggregators appropriate for the amount of traffic you expect your customers to use.
- A small network and server for CPE provisioning (can be virtualized).
- IP addresses for each server, as well as a public /30 (recommended) subnet for each CPE. After you provide remote access to your servers, we will configure the environment and network.
A: Use the web interface to configure their options, Internet connection info, and bonded IP address. The system will assign an API key to their CPE. Then boot the CPE on the provisioning network, providing the API key when requested. The whole process takes less than 20 minutes, most of which is the CPE configuring its operating system automatically. Some of our partners use API to automate this process.
A: No, if you resell DSL lines from a provider that forwards PPP authentication requests to your own Radius server. Our application integrates with the open-source FreeRadius server to completely manage PPP credentials for you. We will build API based integrations to other ISP operations systems as required.
A: After you provide hardware, connectivity, and remote access, we will configure the server and add it to your environment. This can take as little as 10 minutes, excluding operating system install time.
A: Redundant aggregators can be configured upon request. Alternatively, in the event of a failure you can use the web interface to switch a customer to a different aggregation server. We will add support for application-level aggregator failover in a future release.
A: Redundant configuration servers can be configured upon request. Note that a failed configuration server has no effect on customer traffic; only management, monitoring, and reporting functions are impacted.