Version

Argent for SNMP 1204-B or earlier

Date

26 Sep 2012

Summary

Resolving status is irrelevant to the original event.

For example,

Value of OID B was used to resolve the event because of value of OID A has breached the condition defined in a Rule.

Technical Background

In event resolving mechanism, Argent is comparing data on a particular object/counter/instance before and after event.

Click For Full Size

In normal circumstances, the name of comparing object name should fit the length allowed. However, for SNMP monitoring, OIDs being monitored might appear very long.

When the comparing object name exceeds, the name is trimmed. All OIDs will “look” the same in the compare mechanism. Therefore value of any OIDs in the same pattern (after trimming) will resolve original event.

Resolution

To resolve the issue, we increase length allowed in COMPARE mechanism.

Step 1 – Modify Argent Registry

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ARGENT\ARGENT_CONSOLE\SERVER

EVENT_COMPARE_TEXT_LENGTH = 100 (for HEX) or 256 (for DECIMAL)

Click For Full Size

Step 2 – Modify Argent Database Table

In Argent AT Database, go to Table “ARGSOFT_AAC_CONSOLE“, we can find a column name “COMPARE“.

Change the length from 64 to 256.

Click For Full Size