cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

SNMP GENERIC DEVICE ERROR=39 /sfm event

MariettaAlmeida
Organizer

Hi all,

im trying to connect an Aruba switch with snmp generic device extension but get this error:

MariettaAlmeida_0-1676652377029.png

Content

Failed to assign monitoring configuration to ActiveGate. Reason: UNKNOWN_ERROR:Status DEVICE_TIMEOUT_ERROR (39) returned from 1 agents (192.xxx: Agent(192.xxx😞 GetBulk timout args: 1.3.6.1.2.1.1.5.0 : request timeout (after 2 retries) [status code=39]);
 
thanks all 
8 REPLIES 8

DanielS
DynaMight Guru
DynaMight Guru

Hi @MariettaAlmeida can you check connectivity between the AG and the device?

Has the device some filter rules that may be preventing the AG to establish a connection?

The true delight is in the finding out rather than in the knowing.

mariusz_cwiklin
Contributor

Is your Aruba switch configured with SNMP v2c or 3 version?

We are getting this kind of errors for all devices where manufacturers allow only SNMP v1, which is not supported by Dynatrace SNMP extension.

Hi @mariusz_cwiklin SNMPv2

Ilya7
Participant

We have the same problem and we opened a support ticket for this issue. We use SNMP v2c.

I'll give you an update as soon as we have a solution.

@Ilya7 would be kind from you, yes please let me know how it goes !

Hi @Ilya7 is there any news about your ticket? We'd really appreciate it if you share it with the Community, in case more people are facing the same. Thank you! 

The only constant is change. Finding ways for great things to happen!

Hello @Ana_Kuzmenchuk@MariettaAlmeida,

solving the ticket took a while because we were troubleshooting a lot. 

As it turned out Dynatrace expects the response to be from the exact same IP adress the request was sent to. In our case we have two cisco devices which can be adressed through a single IP adress. The response then comes from one of those devices with a sligtly different IP adress. 

So if you have an adress mapping, a loadbalancer or something alike the extension likely won't work. 

We didn't realise it was a problem since we can do snmpgets and snmpwalks through the CLI from any machine and we would get an immediate response.

tl;dr: Response must come from the exact same IP the request is sent to.

Best regards,
Ilya

Wow, thanks a lot for such a detailed explanation! Accepting it as a solution now 😉

The only constant is change. Finding ways for great things to happen!

Featured Posts