Cisco Meraki - Teridion
Deployment Guide
A Teridion Technical Guide
Teridion Product Management June 2019
A Technical Guide For Integration Of The Teridion for Enterprise
Cloud WAN Service and Cisco Meraki MX/Z Security Appliances
A TERIDION TECHNICAL PAPER | 2
CONTENTS
Introduction
Solution Overview
Prerequisites
Initial Preparations
Connecting the Appliances
Creating the Teridion Network
Configuration of the Cloud Gateway Appliance
Configuration of the CPE Appliance
Extra Configuations
Additional Resources
3
4
5
6
7
9
12
17
21
22
A TERIDION TECHNICAL PAPER | 3
Introduction
Together, Teridion and Cisco Meraki provide a powerful end-to-end WAN solution. The
complementary nature of the features of both products gives the enterprise a comprehensive,
high-performance WAN solution.
This guide is a reference document that details the optimal integration configuration for Cisco
Meraki MX series appliances and Teridion For Enterprise. The Cisco Meraki - Teridion reference
deployment takes just minutes to implement, and supports Teridion’s acceleration for site-to-site
and site-to-internet combined with Cisco Meraki SD-WAN capabilities, including failover to Auto
VPN for high availability. This fully integrated solution delivers optimized end-to-end performance
and reliability.
• An economical alternative for MPLS networks with comparable SLAs for performance and reliability.
• Improved SaaS application performance with reliability comparable to on-premises applications.
• The lowest possible latency, packet loss, and jitter metrics for video and UCaaS applications.
• Fast and reliable connectivity to workloads located in any public cloud provider globally, with full multi-cloud and hybrid cloud support.
• Consistent performance for any site-to-site connections by maximizing throughput while minimizing loss and latency.
• All that while using Cisco Meraki’s best-of-class cloud security and control over the
network edge.
Be
ne
fits
A TERIDION TECHNICAL PAPER | 4
Solution Overview
For the Cisco Meraki and Teridion integration solution, each site will have two MX appliances, one
for each of the following roles:
• Cloud Gateway appliance
• Customer Premises Equipment (CPE) appliance.
In normal operation, the Cloud Gateway appliance is connected via a 3rd party VPN connection to
the Teridion edge.
All site-to-site traffic is accelerated across this connection. To realize the optimal cost/performance
ratio, site-to-cloud and site-to-Internet traffic may be accelerated across the VPN connection to the
Teridion edge, or run to the public Internet, based on policies implemented on the CPE appliance.
In the unlikely event that the Teridion edge is not available for a particular location, this configuration
allows site-to-site traffic to and from that location to failover to a Cisco Meraki Auto-VPN connection
terminated on the CPE appliance, while all site-to-cloud and site-to-Internet traffic is rerouted to the
public Internet through the Cloud Gateway appliance.
Normal And Failover Operation: Single ISP Topology
A TERIDION TECHNICAL PAPER | 5
a. For sites where bandwidth is up to 100 Mbps, and/or only internet acceleration is
required: MX64 or higher (Only MXs with two WAN ports, consult your Sales Engineer
for specific builds)
b. For sites where bandwidth is over 100 Mbps, and site-to-site acceleration is
required: MX68 or higher (consult your Sales Engineer for specific builds)
Normal And Failover Operation: Dual ISP Topology
Prerequisites
Cisco Meraki MX Requirements
1. Cisco Meraki MX requirements for Cloud Gateway appliance:
2. Cisco Meraki MX requirements for CPE appliance:
If using an MX64, you’ll need to configure the LAN4 port as a WAN
port: You can toggle the LAN4 port between LAN and Internet, through
Uplink configuration under the Local status tab.
a. MX67 (consult your Sales Engineer for specific builds)
A TERIDION TECHNICAL PAPER | 6
Organizations and Networks
Two organizations are required. You’ll assign all the Cloud Gateway appliances to one
organization, and all the CPE appliances to the other. You can find instructions on how to create
new organizations here.
For each MX, a new “Network” must be created in the relevant organization and the MX
appliances allocated to those new networks. You can find the instructions on how to create new
networks and claim devices to them here.
Initial preparations
1. Create a new organization for the Cloud-Gateway appliances and give it a name (e.g.:
“{Company-Name}-Cloud-Appliance-Org”).
2. Create a new organization for the CPE appliances and give it a name (e.g.: “{Company-
Name}-CPE-Applicance-Org”).
3. Create a new network in the Cisco Meraki Dashboard for each one of the MX appliances in
the relevant organization according to this guide.
The CPE organization can be any existing organization in the Cisco- Meraki
dashboard.
a. Give your new network a meaningful name (e.g.: “Cloud Gateway Appliance - London”).
b. Under “Network Type”, choose “Security appliance”.
c. Under “Network Configuration”, choose “Default Meraki configuration”.
d. In the “Devices” section, click “Add devices” and enter the serial number of the relevant
MX appliance to add it to the inventory.
e. Attach the added device to the newly created network.
A TERIDION TECHNICAL PAPER | 7
Connecting the Appliances
Appliances can be connected to a single ISP, or to dual ISPs for additional redundancy. Set your
appliance connections according to the relevant instructions below.
1. CPE appliance WAN-2: used to route site-to-Internet traffic through Teridion.
2. CPE appliance, any LAN port: used to route site-to-site traffic through Teridion.
3. CPE applicance WAN-1: used for site-to-site traffic over Auto-VPN as a fail-over, and for site-to-
Internet traffic that does not need to be accelerated .
Networks with a single ISP connection
Each port on the CPE appliance may be connected to any LAN port on the Cloud Gateway
appliance.
A TERIDION TECHNICAL PAPER | 8
1. CPE Appliance WAN-2: used to route site-to-Internet traffic through Teridion.
2. CPE Appliance, any LAN port: used to route site-to-site traffic through Teridion.
3. CPE Appliance WAN-1: used for site-to-site traffic over Auto-VPN and as a fail-over and for
site-to-Internet traffic that does not need to be accelerated (Connects directly to the ISP).
Networks with dual ISP connections
Connections 1 and 2 on the CPE appliance may be connected to any LAN port on the Cloud
Gateway appliance.
A TERIDION TECHNICAL PAPER | 9
Creating the Teridion network
To create your Teridion network, log into the Teridion portal (my.teridion.com) using the credentials
provided in your welcome email.
Each site created in the Teridion Portal will have three sequential statuses:
Draft- After clicking ‘Save’ for a site, the site will be in draft mode. Draft mode is like a “waiting
room” where sites are kept until you’re ready to commit the entire job for configuration. While sites
are in draft mode, you can freely edit them, and no configuration adds or changes are pushed to
Teridion.
In-progress- After saving all required sites in draft mode, select ‘Deploy New Sites’. This will send
all site information to Teridion to create the network and change all sites’ status to ‘In-progress’.
Ready- Once the configuration is complete and the network is in service, the status will change to
‘Ready’. At this point, the IPSec tunnels to the Teridion edge can be created.
Once you click ‘Deploy New Sites’, the network creation process begins, and all routes
and Teridion Cloud Routers are deployed. This may take up to 24 hours, and during that
time you won’t be able to deploy any additional sites or make changes to the Teridion
configuration.
CONFIG
Value of FormSITE NAME
SITE NAME
SITE STATUS
Afton House, SL67AU, Slough
SITE NAME
Bangalore Engineering
Houston
London
Bangalore, Karnataka, India63.89.138.226
SITE TYPE
Mesh
Mesh
Mesh
Mesh
Mesh
Mesh
Mesh
Mesh
236.92.241.27
193.167.27.116
SITE IP
333 8th Ave, New York, NY
15813 Saddleback, Phoenix, AZ
300 Brannan, San Francisco, CA
35 Harbor Blvd, San Diego, CA
170 Compton Blvd, Los Angeles, CA
3010 Eastside, Houston, TX
LOCATION COMMIT
10TB
1TB
1TB
250GB
20TB
5TB
10TB
5TB
LAST CONNECTION
NOW
NOW
NOW
NOW
NOW
NOW
1/14/19 12:36:40
BAND- WIDT H
400MB
100MB
100MB
10MB
1GB
200MB
400MB
10MB
SECONDARY TERIDION IP
79.236.138.155
13.82.80.29
207.138.154.107
5.169.215.148
89.124.76.83
151.203.7.19
118.175.26.19
PRIMARY TERIDION IP
242.135.227.202
225.84.29.162
149.1.57.16
170.143.167.199
30.235.209.165
164.235.193.37
202.20.60.65
STATUS
IN PROGRESSDRAFT READYUPLOAD SITE CSVEDIT SELECTION
CREATE A SITE
LOGOUTMENU
Los Angeles Warehouse 152.106.97.190
New York 12.113.237.107
167.101.111.112
12.68.55.215
44.202.12.0
Phoenix
San Francisco
San Diego Sales O�ce
A TERIDION TECHNICAL PAPER | 10
CONFIGPREFERENCES
CONFIG
HEALTH NETWORK
LOREM IPSUM
LOREM IPSUM
SITE STATUS
SITE NAME SITE TYPE SITE IP LOCATION LICENSE BANDWIDT H SECONDARY TERIDIAN IP
PRIMARY TERIDIAN IP STATUS
ADD YOUR SITES Manually Configure your site or Upload a CSV file
1
CONFIGURE A SITE
BULK UPLOAD CSV
GET TEMPLATE
CREATE YOUR NETWORK. After you deploy your sites, configuration will be locked
for up to 24 hours as Teridion completes your setup.
2
DEPLOY NEW SITES
LOGOUTMENU
Navigate to Menu > Config. Add sites by choosing ‘Configure a site’ or using the csv bulk upload.
A csv template is available.
If sites have already been created in your deployment, then the Config page will show the existing
sites. You’ll select ‘Create A Site’ or choose the csv upload to add your sites.
CONFIG
Value of FormSITE NAME
SITE NAME
SITE STATUS
Afton House, SL67AU, Slough
SITE NAME
Bangalore Engineering
Houston
London
Bangalore, Karnataka, India63.89.138.226
SITE TYPE
Mesh
Mesh
Mesh
Mesh
Mesh
Mesh
Mesh
Mesh
236.92.241.27
193.167.27.116
SITE IP
333 8th Ave, New York, NY
15813 Saddleback, Phoenix, AZ
300 Brannan, San Francisco, CA
35 Harbor Blvd, San Diego, CA
170 Compton Blvd, Los Angeles, CA
3010 Eastside, Houston, TX
LOCATION COMMIT
10TB
1TB
1TB
250GB
20TB
5TB
10TB
5TB
LAST CONNECTION
NOW
NOW
NOW
NOW
NOW
NOW
1/14/19 12:36:40
BAND- WIDT H
400MB
100MB
100MB
10MB
1GB
200MB
400MB
10MB
SECONDARY TERIDION IP
79.236.138.155
13.82.80.29
207.138.154.107
5.169.215.148
89.124.76.83
151.203.7.19
118.175.26.19
PRIMARY TERIDION IP
242.135.227.202
225.84.29.162
149.1.57.16
170.143.167.199
30.235.209.165
164.235.193.37
202.20.60.65
STATUS
IN PROGRESSDRAFT READYUPLOAD SITE CSVEDIT SELECTION
CREATE A SITE
LOGOUTMENU
Los Angeles Warehouse 152.106.97.190
New York 12.113.237.107
167.101.111.112
12.68.55.215
44.202.12.0
Phoenix
San Francisco
San Diego Sales O�ce
A TERIDION TECHNICAL PAPER | 11
Site name - Provide a meaningful name to your site.
Location- fill the city, state (if in US) and country of your site.
Site bandwidth - Your upstream and downstream connection speeds. Teridion will use these
values to allow you to monitor your bandwidth usage.
Site type: Spoke or Hub/Mesh- When selecting Hub/Mesh, the site will be connected to all
other Hub/Mesh sites, and may also have spoke sites connected to it.
Site IP- Enter the public IP address of the site.
Site ID- Enter the IP address assigned to the WAN interface (this value defaults to site IP). If the
device is behind a NAT, the site ID will be the internal IP of the WAN interface. To get the right
IPs from your Cisco Meraki configuration, in the Cisco Meraki Dashboard, go to Security & SD-WAN > Appliance Status > Uplink. You’ll find the Public IP under General and the Internal IP
under WAN > IP (DHCP)
Monitoring IP- Selecting a monitoring IP address will enable Teridion to present a complete
view of network performance all the way to your site. The default value is the site IP, but it can
be any other pingable public IP at the site.
Site subnets - Insert all subnets behind the site that will use the IPSec tunnel (in CIDR notation,
e.g. 192.168.120.0/24). Include all subnets where the field ‘Use VPN’ is marked as ‘Yes’ in the
Cisco Meraki Dashboard (under Security & SD-WAN > Site-to-site VPN > VPN Settings > Local Networks)
For each MX you connect to Teridion, you’ll create a Teridion site. Remember, clicking ‘Deploy New
Sites’ will ‘lock’ the portal until the network is created, so hold off until you finish saving all your
required sites for this network.
For each site, you’ll complete the following fields:
A TERIDION TECHNICAL PAPER | 12
CPE Support multiple tunnels (Yes/No) - Selecting YES will create a redundant path
configuration
IPSec policies - Choose the Cisco Meraki template or fill custom policies for authentication,
encryption, DH group and lifetime for phase 1 and phase 2
Once the network is up, navigate to Menu > Config. The Teridion endpoint IPs for each site can be
found in the ‘Primary Teridion IP’ column. These IPs will be used to configure the IPSec tunnel on the
MX’s ‘Non-Meraki VPN peers’ section.
When all sites are added, click ‘Deploy New Sites’. An email notification will be sent to you once the
network is ready.
CONFIG
LOGOUTMENU
SITE STATUS
SITE NAMESITE TYPE
SITE IP LOCATION LICENSE LAST CONNECTION
BAND- WIDT H
SECONDARY TERIDION IP
PRIMARY TERIDION IP
STATUS
IN PROGRESSDRAFT READYUPLOAD SITE CSVEDIT SELECTION
DEPLOY NEW SITESCREATE ANOTHER SITE
Configuration of the Cloud Gateway Appliance
Next, you’ll configure your Cloud Gateway appliances. Repeat those steps for each Cloud Gateway
appliance you’re setting up.
For each appliance, you’ll implement this configuration:
• Configure the Cloud Appliance LAN (VLAN A) <-> CPE Appliance WAN1 link between the
appliances (site-to-site and site-to-Internet failover).
For a dual ISP configuration, the CPE Appliance WAN1 link will be connected
directly to the ISP and not through the Cloud Gateway Appliance
For the best IPSec performance, choose ‘PFS Group’ as ‘Off’ on the Phase 2
settings.
IPre-shared Secret - Choose a strong pre-shared secret. Remember to save it for configuring
the tunnel on the Cisco Meraki Dashboard; you won’t be able to view the key in the Teridion
Portal after you create it.
A TERIDION TECHNICAL PAPER | 13
• Configure the Cloud Gateway Appliance LAN (VLAN B) <-> CPE Appliance WAN2 link between
the appliances (site-to-Internet through Teridion).
• Configure the Cloud Gateway Appliance LAN (VLAN C) <-> CPE Appliance LAN (VLAN C) link
between the appliances (site-to-site through Teridion).
• Create new static routes to the LAN segments behind the CPE Appliance (Pointing to the CPE
Appliance address on the LAN-LAN connection between the appliances).
• Create tags for each network (used to activate and assign a VPN connection for each site).
• Create the VPN connection to Teridion.
• Assign a tag to the relevant VPN.
• Set “Use VPN” on the static routes that were created for the LAN segments, CPE Appliance
WAN2, and on the LAN-LAN link between the appliances.
Execute these steps to build your configuration:
1. Create new VLANs: A VLAN should be created for each of the connections between the
appliances.
i. CPE-Appliance WAN 1 traffic (Auto VPN and failover).
ii. CPE-Appliance WAN 2 traffic (Teridion site-to-Internet traffic).
iii. CPE-Appliance LAN traffic (Teridion site-to-site traffic).
a. Navigate to Security & SD-WAN > Addressing & VLANs.
b. Under ‘Routing’, Verify the ‘Use VLANs’ checkbox is checked.
c. Add the new VLANs, by choosing ‘Add VLAN’ in the ‘Subnets’ section.
d. The following VLANs will be created in order to connect the Cloud-Gateway-Appliance to
the CPE-Appliance:
Only for single ISP networks
A TERIDION TECHNICAL PAPER | 14
e. Check ‘In VPN’ check appliance only for the VLANs created for the WAN 2 v and LAN
connections (Will be done only on the Cloud-Appliance).
f. Assign an unused /30 subnet for each.
g. Choose a unique VLAN ID for each subnet.
h. For each VLAN provide a name that describes its role (e.g. “To-{Site-Name}-CPE-
Appliance-WAN1”).
i. Choose the highest IP in the subnet range as the MX IP of the Cloud Gateway Appliance.
2. Assign the new VLANs to the MX’s LAN ports:
a. All used ports should be enabled.
b. All used ports should have “Type” - “Access”.
c. Assign the first LAN port to the ‘CPE-WAN 1’ VLAN.
d. Assign the second LAN port to the ‘CPE-WAN 2’ VLAN.
e. Assign the third LAN port to the LAN-LAN VLAN (site-to-site through Teridion).
Only for single ISP networks
A TERIDION TECHNICAL PAPER | 15
3. Create a static route for the LAN segments behind the CPE-Appliance:
a. Click ‘Add Static Route’
b. Assign static route with a meaningful name (e.g.. CGW to CPE-LAN-192.168.x.x/24)
c. Under ‘Subnet’ - insert the LAN subnet behind the CPE-Appliance
d. Under ‘Next hop IP’ - insert the IP address of the CPE-Appliance (On the site-to-site
Subnet, link number 2 on the diagram).
e. Under “Active”- choose “Always”.
f. Check the “In VPN” checkbox to allow the static route to be advertised in the VPN
connection that will be configured later in this guide.
4. Create a tag for each network (This tag will be used to associate the network to its relevant
VPN connection):
a. On the Meraki Dashboard, Navigate to Organization > Overview.
b. Select the checkbox next to each site you want to tag.
c. Click ‘Tag’ > Insert a tagname for the network (i.e. “{Site-Name}-To-Teridion-VPN”) > ‘Add’
5. Create VPN tunnels to the Teridion network:
On the Meraki Dashboard, Navigate to Security & SD-WAN > site-to-site VPN and add a peer
for the Teridion edge node assigned to this site:
a. Name the peer.
b. Public IP: Insert the endpoint IP provided in the Teridion Portal (public IP address).
A TERIDION TECHNICAL PAPER | 16
e. Pre-shared Secret: Insert the same secret you chose for the site in the Teridion Portal.
f. Availability: Select the tag you have created for that site in the previous section
g. Confirm.
h. In the ‘VPN Settings’ section- verify that the VLANS for ‘WAN 2’, ‘LAN (Teridion-site-to-site)’
and the static routes to the LAN segments behind the CPE appliance are marked ‘Yes’ under
the ‘Use VPN’ field.
c. Private subnets: Insert 0.0.0.0/0, Each peer will have the same private subnets. This does
not cause an overlapping conflict because each will be tagged to a different network with the
availability selector.
d. IPsec policies: Insert the same policies you have defined for the site in the Teridion Portal.
For the best IPSec performance, choose ‘PFS Group’ as ‘Off’ on the Phase 2
settings.
A TERIDION TECHNICAL PAPER | 17
Next, you’ll configure your CPE appliances. Repeat those steps for each CPE appliance you’re
setting up.
For each appliance, you’ll implement this configuration:
• Configure the LAN-P2P link between the CPE appliance and the Cloud Gateway appliance (This
LAN-P2P link will be used to route site-to-site traffic that should be accelerated with Teridion).
• Create new static routes to the other sites P2P links (Pointing to the Cloud Gateway appliance
address on the LAN-LAN connection between the appliances).
• Create new static routes to the other sites LAN segments (Pointing to the Cloud Gateway
address on the LAN-LAN connection between the appliances).
Execute these steps to build your configuration:
Configuration of the CPE Appliance
1. Configure LAN-LAN P2P for site-to-site traffic with Teridion:
a. Navigate to Security & SD-WAN > Addressing & VLANs.
b. Under ‘Routing’, Verify the ‘Use VLANs’ checkbox is checked
c. Add the new VLANs, by choosing ‘Add VLAN’ in the ‘Subnets’ section:
ii. Add/Keep any other VLAN for the LAN segment of your network
• Assign the same /30 subnet that was chosen in the Cloud Gateway Appliance for this
traffic
• Provide a name for the VLAN
• Choose the lowest usable IP in the subnet range as the MX IP
• Uncheck the ‘In VPN’ checkbox
Recommended: Choose the same VLAN ID as chosen on the Cloud
Appliance.
• Make sure the ‘In VPN’ checkbox is checked for the LAN segments VLANs.
i. Create a VLAN for the CPE Appliance LAN traffic (Teridion site-to-site traffic)
A TERIDION TECHNICAL PAPER | 18
a. All used ports should be enabled
b. All used ports should have ‘Type’ - ‘Access’
c. Assign a LAN port to Teridion - site-to-site (LAN) VLAN
d. Assign the other ports to the other VLANS as needed
2. Assign the VLANs to ports:
3. Create a static route for the LAN segments of the other sites’s CPE Appliances (Pointing
to the Cloud Gateway appliance address on the LAN-LAN connection between the
appliances).
This step is not required for deployments that require site-to-Internet acceleration
only.
Repeat the following steps for each of the subnets in the LAN segment of the other sites
that should communicate with the site you are configuring.
a. Click ‘Add Static Route’
b. Assign static route with a meaningful name (e.g. Site1 through CGW)
c. Under ‘Subnet’ - insert the subnet of the LAN segment of the other site
d. Under ‘Next hop IP’ - Insert the IP address of the Cloud Appliance on the LAN-LAN
connection between the appliances.
e. Under ‘Active’- choose ‘While host responds to ping’
f. Don’t check the ‘In VPN’ checkbox
i. Under ‘Host to ping’ insert default gateway address of that segment (e.g.: if a route to
192.168.1.0/24 is entered, the “Host to ping” address will be the default gateway of the
192.168.1.0/24 segment).
This will assure failover to WAN-1 (Auto VPN) in case there is any issue with the IPSec
tunnel or the Teridion network.
A TERIDION TECHNICAL PAPER | 19
4. Create a static route on each one of the CPE Appliances for the Point-To-Point link subnets
between the other CPE Appliances and their respective Cloud Gateway Appliances. The
next hop of that route will be the Cloud Gateway Applianceof the local site:
a. Click ‘Add Static Route’
b. Assign static route with a meaningful name (e.g. ‘To-{Site-Name}-CPE-Appliance to {Site-
Name}-Cloud Gateway appliance P2P’)
c. Under ‘Subnet’ - insert the subnet of the ‘Teridion site-to-site’ VLAN of the other site
d. Under ‘Next hop IP’ - insert the IP address of the local Cloud Gateway appliance (Pointing
to the Cloud Gateway appliance address on the LAN-LAN connection between the
appliances).
e. Under ‘Active’- choose ‘Always’
f. Don’t check the ‘In VPN’ checkbox
5. Configure the LAN VLANs to use VPN:
a. Navigate to Security & SD-WAN > site-to-site VPN > VPN Settings,
b. In the ‘Uplink statistics’ section, test connectivity to 8.8.8.8 (or other publicly available
servers) as a default destination
c. In the ‘Use VPN’ field- mark all the VLANs you have created for the LAN segments of the
site as ‘Yes’. Mark the rest of the VLANs as ‘NO’.
6. Configure site-to-site and site-to-Internet Failover to Auto-VPN:
a. Navigate to Security & SD-WAN > SD-WAN & Traffic Shaping
b. Under Flow preferences > Internet traffic
Steps i-iv in this example show how to route all traffic through the Teridion network.
You can use the ‘Flow Preference’ feature to determine which traffic should be routed
through the Teridion network.
A TERIDION TECHNICAL PAPER | 20
i. Click ‘Add a preference’
ii. Choose ‘Any’ under ‘Protocol’
iii. Input ‘Any’ under ‘Source’
iv. Input ‘Any’ under ‘Destination’
v. Choose ‘WAN 2’ under ‘Preferred Uplink’
c. Under SD-WAN policies > VPN traffic
i. Click ‘Add a preference’
ii. Under ‘Traffic filters’ > ‘Add’> ‘Custom expressions’ choose
• Protocol - choose ‘Any’
• Source - choose ‘Any’
• Click ‘Add expression’
iii. Under Policy > ‘Preferred uplink’ choose ‘WAN 1’
iv. Under ‘Failover if’ choose ‘Uplink down’
A TERIDION TECHNICAL PAPER | 21
Cloud-Gateway appliance Organization:
1. Disable Hub-To-Hub routing in the Cloud-Gateway organization.
2. Disable DPD for all the appliances in the Cloud-Gateway organization.
CPE appliance:
1. Quick internet Fail-Over timers.
2. Enable Active-Active Auto-VPN feature.
Extra Configurations
Once you’ve completed these steps, your Cisco-Meraki support team or your dedicated Cisco-Meraki
SE will finalize the configuration, the following featured need to be changed with the help of Cisco
Meraki TAC:
A TERIDION TECHNICAL PAPER | 22
contact info
Email: [email protected]
SAN FRANCISCO
300 Brannan St., Suite 101
San Francisco, CA 94107
1-844-TERIDION
TERIDION PARTNER PROGRAM
Interested in becoming a Teridion reseller? Let’s talk.
www.teridion.com
ISRAEL
Bazel St 25, 1st Floor
Petah Tikva, Israel
+972 77-220-0077
RESOURCESTeridion Whitepaper: The Internet Backbone Problem
Teridion Whitepaper: Teridion For Enterprise Technical Overview
Teridion Whitepaper: Teridion For SaaS Technical Overview
Connect with us:
Request A Demo
