Telefónica SD-WAN Service - Meraki - Part 1/2

Meraki Cloud...

Is offered in the way of SaaS and hosted by AWS.

Is offered in the way of PaaS and can be deployed on Meraki DataCenters or on Telefónica premises.

Is offered in the way of SaaS and hosted by Meraki DataCenters.

Is offered in the way of SaaS and deployment can be chosen: Meraki DataCenters, AWS or Azure.

Regarding security features, Meraki MX device...

Offers a typical UTP: FW, AMP, IDS/IPS, Content Filtering, NAT & Port Forwarding.

Offers a Next Generation Firewall, including DLP and Sandboxing.

Does not offer security features except ACLs, given that it is an SD-WAN gateway.

All the security features are delegated automatically to Cisco Umbrella.

Meraki MX device...

Has CLI (Command Line Interface) IOS-XE alike.

Has no CLI. It only has the Local Status Page.

Has a proprietary CLI which can be accessed only from Meraki Dashboard.

Has a Linux alike CLI which can be accessed only from its Local Status Page.

Meraki Z device has lower performance than MX device and...

Is exactly the same as MX except the external box/aspect.

Is the same as MX except the external box/aspect and it has only one WAN uplink.

Cannot join Auto VPN overlay given that it is for teleworkers.

For performance reasons it does not support security features at all.

MX working as NAT Mode supports dynamic routing towards the underlay (WAN side).

True, it supports BGP, OSPF and IS-IS.

False, MX does not support dynamic routing for any of the possible working modes.

False, MX NAT Mode does not support it, but Meraki is working on BGP towards WAN side in future releases.

False, it supports BGP and it is used in Telefónica Service for the gateway between non-migrated to migrated sites.

Telefónica Service uses MX One-Armed VPN Concentrator Mode...

To be the gateway between legacy sites (non SD-WAN) and SD-WAN sites.

To centralize Internet SmartBreakout in the hub of the customer network.

To be the gateway between a public/Internet only site and a private/MPLS only site.

It is not used by Telefónica Service. MX NAT Mode is enough.

QoS & Traffic Shaping on MX device...

Works exactly the same than in the case of Cisco IOS-XE devices.

Has only 3 queues: High, Medium and Low.

MX devices do not support Traffic Shaping.

Has 4 queues and Dashboard does not offer data for troubleshooting.

Telefónica Service monitoring is based on...

Proactive requests to REST API and listening to Webhooks (both from/to Meraki Cloud & Dashboard).

Direct SNMP towards MX devices, using both OIDs requests and traps subscriptions.

Direct SNMP towards Meraki Dashboard, using both OIDs requests and traps subscriptions.

Proactive HTTPS requests towards Meraki API.

The service raised by Telefónica in Germany is offering...

MX device as a pure perimeter firewall.

MX device as both First or Second Level Equipment/Device.

MX device as First Level Equipment/Device, removing the current CPE present on customer premises.

MX device as Second Level Equipment/Device, keeping the CPE already present on customer premises.

Given that the MX device is raised in Telefónica Germany as Second Level Equipment/Device...

Provisioning shall be done always using Zero Touch Deployment, getting network configuration from CPE working as DHCP Server.

The only way to provision the MX device is by manual intervention (field technician).

Zero Touch Provisioning can be implemented by the field technician configuring everything in the Local Status Page.

It is possible to implement Zero Touch Deployment. Therefore, no field technician is needed to rack and wire the device.

Telefónica SD-WAN Service - Meraki - Part 1/2

More Surveys