ZIA Overview

ZIA offers a security stack solution from the cloud for internet and SaaS connections. ZIA acts like a secure web gateway where 0.0.0.0/0 traffic will be routed for inspection and enforcement prior to internet termination.  

This document describes how to configure and troubleshoot Zscaler Internet Access IPSEC peers with the Meraki security appliance (MX/Z platforms).

 

Prerequisites

• Zscaler account 

• ZIA instance (any cloud)

• Meraki MX/Z device (running MX15+ firmware)

• Meraki MX/Z Site-to-site VPN enabled

 

Enable Meraki site-to-site VPN

Site-to-site VPN settings are accessible through the Security & SD-WAN > Configure > Site-to-site VPN page.

There are three options for configuring the MX-Z's role in the Auto VPN topology:

• Off: The MX-Z device will not participate in site-to-site VPN.

• Hub (Mesh): The MX-Z device will establish VPN tunnels to all remote Meraki VPN peers that are also configured in this mode, as well as any MX-Z appliances in hub-and-spoke mode that have the MX-Z device configured as a hub.

• Spoke: This MX-Z device (spoke) will establish direct tunnels only to the specified remote MX-Z devices (hubs). Other spokes will be reachable via their respective hubs unless blocked by site-to-site firewall rules.

 

Gather details from Zscaler

IP addresses or hostnames of the ZIA Public Service Edges

1. Go to config.zscaler.com/<Zscaler Cloud Name>/cenr.

You can find the name of your cloud in the URL your admins use to log into the Zscaler service. For example, if an organization logs into admin.zscalertwo.net, then that organization's cloud name is zscalertwo.net. So, you would go to config.zscaler.com/zscalertwo.net/cenr. To learn more, see What is my cloud name for ZIA?

2. Go to Cloud Enforcement Node Ranges.

3. Under VPN Host Name, find the two data centers closest to the organization's location. Choose one as the destination for your primary IPSec VPN tunnel and the other as the destination for your backup IPSec VPN tunnel. 

4. If you need the IP addresses of the ZIA Public Service Edges, resolve the hostnames.

 

Configuration

You can create Site-to-site VPN tunnels between a Security Appliance or a Teleworker Gateway and a ZIA endpoint device under the Non-Meraki VPN peers section on the Security & SD-WAN > Configure > Site-to-site VPN page. Simply click "Add a peer" and enter the following information:

* Required

1. Name*

   • A name for the remote device or VPN tunnel

You can give any name.

2. IKE Version*

   • What IKE version to use - IKEv2 

   • IKEv2 enables the Local ID field and the predefined Zscaler Preset 

The Zscaler preset is available in IKEv2. You can manually override the Zscaler preset by overriding the IPSec policy.

3. IPSec policies*

   • The IPSec policy to use

   • You can override the predefined Zscaler Preset 

You will need to remove the 3DES options for the crypto cyphers as Zscaler is removing support for DES and 3DES

Recommended IPSec policy settings:

4. Public IP*

   • The public IP address of the remote device

Go to config.zscaler.com/<Zscaler Cloud Name>/cenr. You can find the name of your cloud in the URL your admins use to log into the Zscaler service. For example, if an organization logs into admin.zscalertwo.net, then that organization's cloud name is zscalertwo.net. So, you would go to config.zscaler.com/zscalertwo.net/cenr. To learn more, see What is my cloud name for ZIA?

For the IP addresses of the ZIA Public Service Edges, resolve the hostname.

5. User FQDN

   • This is an optional configuration and can be configured to the remote peer’s UserFQDN (e.g. user@domain.com)

This parameter is only required if you are using the UFQDN or XAUTH authentication type. Specify the fully qualified domain name as a string (e.g., "testvpn.antest.com").

6. Remote ID

   • An optional configuration can be configured to the Remote ID of the remote peer. 

7. Private subnets*

   • The subnets behind the third-party device that you wish to connect to over the VPN. 0.0.0.0/0 can also be specified to define a default route to this peer.

   • Note that if an MX-Z device is configured with a default route (0.0.0.0/0) to a Non-Meraki VPN peer, traffic will not fail over to the WAN, even if the connection goes down. Hence, when the peer fails, all traffic will be routed to NULL. Meraki is working on DIA failover/failback conditions (TBD).

Configure 0.0.0.0/0 as ZIA will be the default gateway for MX LAN VPN participants.

8. Preshared secret*

   • The preshared secret key (PSK)

Navigate to the VPN Credentials section in Authentication

9. Availability*

• Availability settings to determine which appliances in your Dashboard Organization will connect to the peer.

You can create networks by going to Organization > Monitor > Overview page. For more information, read here.

Primary and backup ZIA support 

Meraki MX/Z platforms do not have native primary and backup ZIA peering at this time, but we have created a API configuration guide as a workaround. For more information, read here.

 

Non-Meraki VPN firewall 

You can add firewall rules to control what traffic is allowed to pass through the VPN tunnel. These rules will apply to outbound VPN traffic to/from from all MX-Z appliances in the Organization that participate in site-to-site VPN. These rules are configured in the same manner as the Layer 3 firewall rules described on the Firewall Settings page of this documentation. Note that VPN Firewall rules will not apply to inbound traffic or to traffic that is not passing through the VPN.

 

Serviceability 

24/7 Support 

Cisco Meraki Support is available 24/7 to Enterprise customers for assistance with resolving network issues and providing answers to questions not covered by the documentation. For more information, read here.