Z4C Datasheet

Overview

The Cisco Meraki Z4C teleworker gateway is an enterprise class firewall, VPN gateway and router. This device offers wireless connectivity with WiFi 6, five gigabit ethernet ports, including a built-in PoE-enabled port for VoIP phones and other PoE powered devices. The Z4C is designed to securely extend the power of Meraki cloud managed networking to almost any location. With a built-in LTE modem, the Z4C simplifies any deployment that requires a backup cellular uplink, or is positioned in a remote location.

Features

Software Features

Managed via Cisco Meraki Dashboard
Automatic Firmware upgrades
L3/L7 Stateful Firewall
1:1 and 1:Many NAT
Configurable VLANs / DHCP support
Static Routing
Client VPN endpoint
Meraki AutoVPN and IPSec VPN endpoint
Custom Traffic Shaping

Historical Client Usage statistics
Netflow support
Syslog integration
Remote Packet Capture tools
IPv6 Support
802.1X wired and wireless support

Hardware Features

Built-in WiFi 6 Wireless Capabilities
Built-in PoE+ capabilities
Built-in LTE Cellular capabilities

Context and Comparisons

	Z4C
Single Wired WAN Uplink	Yes
Cellular Uplink	Yes
Stateful Firewall Throughput	500 Mbps
Maximum VPN Throughput	250 Mbps
Security Throughput	300 Mbps
PoE Capabilities	Yes, 1x GbE RJ45 LAN Ports (802.3at)
WiFi	Dual-band 2x2 WiFi 6
Backup Cellular Uplink	Built-in CAT12 LTE Modem with 2x External LTE Antennas
Recommended use case	Up to 15 devices

Technical Breakdown

WAN Interfaces

Z4C

1x Dedicated GbE RJ45

1x Built-in CAT12 LTE Modem

LAN Interface

Z4C

4x Dedicated GbE RJ45

802.11 Wireless Interface

	Z4C
Radio Information	802.11a/b/g/n/ac/ax (2.4 or 5Ghz) 2x2 MU-MIMO
Antennas	2 x 2 MU-MIMO with two spatial streams
Maximum Data Rate	1.5 Gbps*

* Refers to maximum over-the-air data frame rate capability of the radio chipset, and may exceed data rates allowed by IEEE 802.11ax operation.

Signal Coverage Patterns

5GHz WiFi

5GHz signal coverage patterns on the X-Y plane.

5GHz signal coverage patterns on the X-Z plane.

5GHz signal coverage patterns on the Y-Z plane.

2.4 GHz WiFi

2.4GHz signal coverage patterns on the X-Y plane.

2.4GHz signal coverage patterns on the X-Z plane.

2.4GHz signal coverage patterns on the Y-Z plane.

Throughput and Capabilities

	Z4C
Recommended Use Case	Up to 15 devices
Max Stateful Firewall Throughput in NAT mode	500 Mbps
Max VPN Throughput	250 Mbps

Physical

	Z4C
Mount Type	Desktop / Wall Mount
Dimensions (h x d x w)	7.9 x 4.41 x 1.04 in / 200 x 112 x 26 mm
Weight	1.1 lbs / 0.487 kg
Power Supply	50W DC
Power Load (idle/max)	15W / 46W
Operating Temperature	32°F - 113°F 0°C - 45°C
Storage and Transportation Temperature	-4°F - 158°F -20°C - 70° C
Humidity	5% to 95%

Ordering Guide

Model SKU	Description
Z4C-HW	Meraki Z4C Cloud Managed Teleworker Gateway

Accessories

Accessory	Description
MA-PWR-50WAC	Meraki MX Replacement Power Adapter (Z4/C) (50 Watts AC)
MA-PWR-CORD-US	1x AC Power Cable, US plug
MA-PWR-CORD-EU	1x AC Power Cable, EU plug
MA-PWR-CORD-UK	1x AC Power Cable, UK plug
MA-PWR-CORD-AU	1x AC Power Cable, AU plug

Configure your Dashboard Network

The following is a brief overview only of the steps required to add an Z4C to your network. For detailed instructions about creating, configuring and managing Meraki networks, refer to our Managing Dashboard Networks document. Additional resources can also be found via: documentation.meraki.com.

Login to http://dashboard.meraki.com. If this is your ﬁrst time, create a new account.
Find the network to which you plan to add your Z4C or create a new network.
Add your Z4C to your network. You will need your Meraki order number (found on your invoice) or the serial number of each Z4C, which looks like Qxxx-xxxx-xxxx, and is found on the bottom of the unit. If a license key was purchased at the same time then you should have received it via email.
Go to the map / ﬂoor plan view and place each Z4C on the map by clicking and dragging it to the location where you plan to mount it.

Warranty

Z-Series Warranty coverage periods are as follows:

Product	Warranty Period	Warranty Information
Z4C	Lifetime
Z4C Accessories	1 Year	The following are considered accessories: SFP Modules, all mounting kits and stands, interface modules, additional power cords

Product

Warranty Period

Warranty Information

Z4C

Lifetime

Z4C Accessories

1 Year

The following are considered accessories:

SFP Modules, all mounting kits and stands, interface modules, additional power cords

Additional warranty information can be found on the Return Policy and Requesting a RMA page of the Cisco Meraki website.

If your Cisco Meraki device fails and the problem cannot be resolved by troubleshooting, contact support to address the issue. Once support determines that the device is in a failed state, they can process an RMA and send out a replacement device free of charge. In most circumstances, the RMA will include a pre-paid shipping label so the faulty equipment can be returned.

In order to initiate a hardware replacement for non-functioning hardware that is under warranty, you must have access to the original packaging the hardware was shipped in. The original hardware packaging includes device serial number and order information, and may be required for return shipping.

Meraki Z4C devices have been tested and found to comply with the limits for a Class B digital device, pursuant to part 15 of the FCC rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This equipment generates, uses and can radiate radio frequency energy and, if not installed and used in accordance with the instructions, may cause harmful interference to radio communications. However, there is no guarantee that interference will not occur in a particular installation.

Troubleshooting

Common Event Log Messages

Common event logs exist for wired, WiFi, and cellular events. As such, no specific Z4C event log entries are required at this time.

For more general information about navigating the Event Log and the types of Events that could be expected please check out our Event Log documentation.