Meraki MX105 Router/Security Appliance
Meraki MX105 Router/Security Appliance available through HTS — Throughput: 3 Gbps (Stateful) / 1 Gbps (VPN), WAN ports: 2x 2.5GbE RJ45, 2x 10G SFP+, LAN ports: 4x 1GbE RJ45, 2x 10G SFP+.
Cisco MerakiSecurity Appliances
Meraki MX450 Router/Security Appliance
Meraki MX450 Router/Security Appliance available through HTS — Throughput: 6 Gbps (Stateful) / 2 Gbps (VPN), WAN ports: 2x 10G SFP+, LAN ports: 8x 1GbE RJ45, 8x 1G SFP, 8x 10G SFP+.
- SKU
- MX450-HW
MSRP$39,240.97
Our price$26,581.49
Save $12,659.48(32.26% off)
BackorderMore than a box on a truck.
- Configuration scoped to your quoteWe can pre-configure network and security hardware to your spec before it ships — VLANs, PoE budgets, firmware set — scoped and priced in your quote, not assumed into every order.
- One support line, end to endOne support line, not a manufacturer RMA queue — the team that configures it is the team you call.
- Professional installation availableProfessional installation and site turn-up available from the HTS field team.
- One vendor across your networkOne vendor, one invoice, one point of accountability across your whole network.
Add to quote workspaceVolume pricing, deployment services, and verified availability confirmed upon request.
Specifications
| Throughput | 6 Gbps (Stateful) / 2 Gbps (VPN) |
|---|---|
| WAN ports | 2x 10G SFP+ |
| LAN ports | 8x 1GbE RJ45, 8x 1G SFP, 8x 10G SFP+ |
| Recommended clients | Up to 10,000 |
| Form factor | 1U Rackmount |
| Product role | Cisco documents the MX as an enterprise security and SD-WAN appliance designed for distributed deployments that require remote administration |
| Site-to-site connectivity | Cisco documents AutoVPN as the MX architecture for building VPN connectivity between sites |
| Management model | Every MX in this family is administered from the Meraki dashboard rather than per-device CLI |
| Sizing basis | Cisco publishes per-model client and throughput guidance; enabling additional security services reduces effective throughput, so sizing is done against intended feature set rather than port count |