ContributorWe are currently facing a scenario where the IP address of our Meraki devices changes upon reboot, which subsequently triggers a DFA alert. To streamline our operations and reduce manual intervention, we are exploring the possibility of capturing these IP changes and updating them automatically in SL.
Meraki assets are onboarded through SNMP.
ModeratorHello,
This is more of a general question, so you may throw some people off the trail by specifying Meraki devices. This scenario will apply to any devices with dynamic IP addresses that you discover and track via IP address.
Is there a specific question you're asking? Devices discovered with SL1 that have IP addresses that change will cause the problem you are describing if SL1 is using IP address as the unique identifier. When the IP address changes, SL1 has no way to know that device is a different one than before (unless you configure some other item as the unique identifier).
Is it possible for you to discover these via hostname instead? That would likely solve your problem.
Beyond this, we encourage you to use our API based Meraki monitoring solution as SNMP monitoring is very limited by Meraki. Thanks!
