Hi, I'm have a problem with ptrg on mikrotik router, my oid PPP interface is changed after down and if this interface PPP up again the sensor still mark red in graphic, how I can solve for OID changed dynamically?

Sorry for my bad english :D

Thanks

Article Comments

Hello, we appreciate your contact.

Within the SNMP Compatibility Options from the Device in PRTG check the Port Identification setting, it needs to be set in a way that PRTG is able to locate the same interface with a new index once it changes, PRTG will only be able to recognize it if the name is kept unchanged.

Please note that in some cases you may be able to configure Index Persistance in your monitored device, to prevent indexes from changing in the first place.

Best Regards,


Mar, 2016 - Permalink

Hi Luciano, Thanks for your reply, I has follow you instruction and the result is same, my prtg still can't update graphic sensor for dynamic ppp client interface, I change port identification from Auto to ifalias, ifname and ifdesc but no one in options can work, the sensor namer is not changed just ifport is changed every my interface up again.

About Index Persistence, where I can configure it, are in my router or in my device monitoring device in prtg?, can you give link tutorial for Index persistence in prtg?

Thanks Ael


Mar, 2016 - Permalink

Hello Ael,

The ifIndex persistence needs to be configured in the device itself. You can check with the manufacturer to see if this is possible. For Cisco devices it will be possible with the syntax snmp-server ifindex persist , see this article.

Best regards, Felix


Mar, 2016 - Permalink

Hi Felix, Thanks for your reply, I has search in wiki mikrotik for ifindex persistence but looks like this is not support for mikrotik, but, Thanks for your help


Mar, 2016 - Permalink

i'm having this problem too, i can't find any of the command "ifindex persistence" or similiar in the mikrotik


Dec, 2017 - Permalink

Hi,

You can also choose different unique identifiers for the SNMP interfaces. Open the settings of the device and unfold the Port Identification settings. Ensure that the chosen option is uniquely configured on the device and re-add the sensors.

This should resolve it as well.

Best regards, Felix


Dec, 2017 - Permalink