Generic Cisco Device - Error

[Hasan]

Hi Team, 

I have configured Cisco extension 1.12.3 for a device but i am getting below error, Please help on this.

"Failed to assign monitoring configuration to ActiveGate. Reason: GENERIC_ERROR:Status GENERIC_ERROR (27) returned from 1 agents (10.132.67.12: Agent(10.132.67.12): GetBulk returned an error: wrong digest [status code=27]);"

Here is the configuration done.

[PacoPorro]

Can you check if you have special chars in the password?

[Hasan]

No Special characters in password.

[JamesKitson · Accepted solution]

Most likely it's either an incorrect password or incorrect v3 authentication details selected

An example: https://community.cisco.com/t5/network-management/inventory-not-updated/td-p/1601235

I'd suggest trying to use an snmp command line tool to run a test query and you can use that to verify/work out the proper authentication settings your device wants and then you can plug those in to the extension configuration. It will be much quicker than trying to figure it out through updating the config and waiting for errors.

Once you get a manual test working the extension/data source should be able to use those same settings and work as well. If not, it likely merits a support case for review.

[Hasan]

Hi Team 

We are able to see the connectivity sharing the snaps of the same 

Now getting below error can you please help me troubleshoot this

[JamesKitson · Accepted solution]

That particular timeout error is occurring during the 'fastcheck' which is a very lightweight lookup just to see if that ActiveGate can make a simple SNMP query to that target host.

Similar to before, I'd suggest doing a simple snmp get of that OID showing up in the error using that same authentication and from the ActiveGate you believe should be able to connect. If you are able to demonstrate that, or if you get stuck you would need to work with support to dig into it further.

[amnanoor]

Hi there -

We are currently observing errors in the F5 Big-IP extension for the prodcss-lb-web2 monitor in Dynatrace

The WEB1 (prodcss-lb-web1) monitor is working as expected.

The WEB2 (prodcss-lb-web2) monitor is consistently failing.

• No changes have been made on our side that could have caused this issue.

Initial validation shows that the issue is isolated to the web2 node, while the configuration and setup remain consistent across both nodes.

[YeudyGomez]

Good morning Hasan, I hope you're doing well. Were you able to fix this error?

[Hasan]

Hi, Good Morning.

Yes the issue is fixed and working fine, I had shared the input from james with customer team who worked internally and shared updated credentials with us which worked.

Thanks