SNMP varbinds changed order in 2022.4

dcoats 3 months ago

Has anyone else found that the snmp varbinds used in creating alert messages have incremented by 1? I can certainly go and 'fix' it, however one of the alerts was in varbind 10 and fixing it would mean using varbind 11 which doesn't exist. This has completely broken the tool for us. Did I miss something? Here is an example of how we are formatting alert messages for snmp traps:

${N=OLM.AlertingMacros;M=OLMAlertMessage.VbData10}

Cross-posted to Alert Lab as well.

0 darryld 3 months ago

For what it is worth I have exactly the same problem, right down to the use of VbData10. Did you open a support call?
Cancel
Up 0 Down

Reply

Verify Answer

Cancel
0 dcoats 3 months ago in reply to darryld

I opened a case a week or so ago but they haven't produced an explanation or possible fix yet. There is a global variable that you can modify to allow more than 10 varbinds. I incremented that and then 'fixed' the problem myself. I just hope this isn't going to happen now whenever I upgrade. You can modify that varbinds variable in the 'Advanced Configuration' under the 'Global' tab. Search for 'AlertMaximumTrapVarBindings'. Advance Config page is here: http://<your-server>/Orion/Admin/AdvancedConfiguration/Global.aspx
Cancel
Up 0 Down

Reply

Verify Answer

Cancel
0 darryld 3 months ago in reply to dcoats

Thanks for the info. I'll give it a go
Cancel
Up 0 Down

Reply

Verify Answer

Reject Answer

Cancel
0 abakus 1 month ago

If you use the macro for displaying the whole trap, do you see the trap id (1.3.6.1.6.3.1.1.4.1) twice there? I think the shift by 1 is caused by this.
Cancel
Up 0 Down

Reply

Verify Answer

Cancel