How to monitor the Dual MX in Monitoring ?

[DineshSingh]

I need clarification on whether SNMP (polling and traps) has limits similar to API calls:
1. How can I retrieve the OID for a specific device through SNMPwalk?
2. Are there any tools or commands you recommend for this purpose?
3. How can I identify custom OIDs if the device has them?
4. Are there any rate limits or thresholds for SNMP polling or traps, similar to API rate limits?
5. Does SNMP have rate limits similar to API calls?
6. What factors influence SNMP limits (e.g., polling frequency, device capacity)?
7. Are there any best practices or configurations to optimize SNMP performance and avoid hitting these limits?

Dual MX has the same IP, like primary and secondary. 
I can't fetch the details of the secondary router details. 

Can you guys advise me how I can achieve this?

[alemabrahao]

1 - How can I retrieve the OID for a specific device through SNMPwalk?

You can use the snmpwalk command to retrieve OIDs. 

snmpwalk -v2c -c public <device_ip> .1.3.6.1.2.1

This command will walk through the MIB tree starting at the specified OID.

2 - Are there any tools or commands you recommend for this purpose?

Besides snmpwalk, you can use tools like SNMPSoft Tools, iReasoning MIB Browser, and Paessler SNMP Tester.

3 - How can I identify custom OIDs if the device has them?

To identify custom OIDs, you can check the device's MIB files provided by the Meraki.
As mentioned before, use the snmpwalk command to walk through the entire MIB tree and identify custom OIDs.

4 - Are there any rate limits or thresholds for SNMP polling or traps, similar to API rate limits?

SNMP does not have strict rate limits like APIs, but excessive polling can lead to performance issues. It's essential to balance the polling frequency to avoid overloading the network and devices.

5 - Does SNMP have rate limits similar to API calls?

While SNMP does not have explicit rate limits, the performance can be affected by the frequency of polling and the number of devices being monitored. It's crucial to configure polling intervals appropriately.

6- What factors influence SNMP limits (e.g., polling frequency, device capacity)?

*Higher frequency can lead to network congestion.
*Devices have a limit on how many SNMP requests they can handle simultaneously.
* High volume of SNMP traffic can impact overall network performance.

7 - Are there any best practices or configurations to optimize SNMP performance and avoid hitting these limits?

Set appropriate intervals based on the criticality of the device (e.g., 3-5 minutes for critical devices, 10-30 minutes for less critical ones).
Use SNMPv3 for better security and performance.
Limit Scope of Polling.
Restrict SNMP access to specific IP addresses.

Regarding the Dual MX with the same IP for primary and secondary, I'm not sure, maybe you might need to configure the SNMP settings to differentiate between the two devices.

But what I can think of at this moment is to monitor via WAN IP, since the IPs for each MX are different. Unless the IPs are behind a NAT.

[Hasen]

You can use SNMP (Simple Network Management Protocol) and other network monitoring tools. To retrieve OIDs for a specific device using SNMPwalk, you can access Meraki’s MIB files from the dashboard under Organization > Configure > Settings > SNMP. Running an SNMP walk command such as snmpwalk -v2c -c [community_string] [device_ip] can help you fetch supported OIDs.

For SNMP operations, tools like Net-SNMP, SNMP Tester, and platforms like Zabbix or SolarWinds can automate polling and monitoring. If you need to identify custom OIDs, reviewing Meraki’s SNMP documentation or engaging in community forums can be helpful. While API calls have rate limits, SNMP functions differently. Polling frequency and device capacity influence SNMP performance, so setting an optimal polling interval prevents excessive resource usage.

Since both MX devices share the same IP in an HA setup, monitoring the secondary MX directly can be difficult. To work around this, you can configure Meraki Dashboard alerts to notify you of status changes, set up SNMP traps for real-time alerts, and monitor the network’s overall health through external tools.