Please enable JavaScript.
Coggle requires JavaScript to display documents.
ECMS2 Course - Coggle Diagram
ECMS2 Course
Meraki Auto VPN
Uses UDP Hole Punching to establish VPN-Tunnels
Each VPN enabled device registers itself in the Cisco Meraki cloud
Source UDP: 32768 - 61000
Destination UDP: 9350
If only Hub -2- Spoke traffic is preferred; Use Meraki support to enable this
Tunnel count limitations based on MX Type
Tunnel count formula from Hubs perspective: N-1 x L (where N = hub count and L = spoke count)
Full mesh by default (spoke -2- spoke tunnels are dynamic)
802.11 Association Process
Probe request
Probe Response
Authentication Request
Authentication Response
Association Request
Association Response
Connection Monitor
Physical Connection
ARP Tests
DNS Resolvement
Internet Connection (ICMP & HTTP GET)
Air Marshal (wIPS)
Spoofs
Packet Floods
Roque APs
Malicious Broadcasts
MV Advanced Analytics
Motion Search 2.0
Motion Heat Maps
Object Detection
Local status page
mx.meraki.com (LAN IP)
switch.meraki.com (1.1.1.100)
ap.meraki.com (10.128.128.126)
Firmware
Easier (automated) process
less downtime through rolling upgrades
All devices at once
Insight
Licenses are per device; not per network
Licenses are transferable between devices
Keep MX models in mind while purchasing licenses
Switch Stacking
Virtual == Making configuration on multiple ports of different switches whitin a network
Fysical == Combining multiple switches to one logical switch. (Can have 1-8 members)
MX Modes
Concentrator Mode (One Armed)
NAT (Routed) Mode
API
Scannning API (RealTime data)
Dashboard API (Information gathering about Meraki configured devices)