Meraki Cloud Firewall SNMP Inbound

SOLVED
Fabian1
Getting noticed

Meraki Cloud Firewall SNMP Inbound

Hi everyone,

 

on the firewall info page there is a new entry 

209.206.48.0/20, 216.157.128.0/20, 158.115.128.0/19Your network(s) AnyUDPinboundSNMP trapsAccess points, MX Security Appliance, Switches

 

How am I supposed to set this on the MX? When I put this on the outbound rules, it says it's not part of my network, of course. But there are only IPv6 inbound rules to be set on the config page. So how am I supposed to set this on the MX?

 

Best

Fabian

1 ACCEPTED SOLUTION
Brash
Head in the Cloud

The SNMP traps rule is for inbound traffic from the Meraki cloud to your premises.

SNMP traps are sent from Meraki cloud to an SNMP server behind a public IP.

https://documentation.meraki.com/General_Administration/Monitoring_and_Reporting/SNMP_Overview_and_C...

 

To allow this traffic through an MX, you would configure port forwarding or inbound NAT under the Firewall configuration.

View solution in original post

4 REPLIES 4
Brash
Head in the Cloud

The SNMP traps rule is for inbound traffic from the Meraki cloud to your premises.

SNMP traps are sent from Meraki cloud to an SNMP server behind a public IP.

https://documentation.meraki.com/General_Administration/Monitoring_and_Reporting/SNMP_Overview_and_C...

 

To allow this traffic through an MX, you would configure port forwarding or inbound NAT under the Firewall configuration.

ww
Kind of a big deal
Kind of a big deal

Its strange that it shows up now...  I  have snmp disabled

Brash
Head in the Cloud

Good point, seems to be a static entry in the table rather than dynamically appearing when in use.

Probably worth submitting feedback as I can't imagine most customers would be using SNMP traps alongside email alerts and other monitoring.

MyHomeNWLab
Building a reputation

The SNMP Trap feature is a Beta feature.

 

SNMP Overview and Configuration - Cisco Meraki
https://documentation.meraki.com/General_Administration/Monitoring_and_Reporting/SNMP_Overview_and_C...

> Enabling Traps
> Contact Meraki Support to have the feature enabled on the desired organization

 

However, it appears to have recently been opened to the public.
Therefore, it is additionally displayed in Firewall Info.

 

In my Org1 environment, I activated it when it was Beta.
However, in my Org2 environment, it appears without activation.

Get notified when there are additional replies to this discussion.
Welcome to the Meraki Community!
To start contributing, simply sign in with your Cisco account. If you don't yet have a Cisco account, you can sign up.
Labels