Version

Argent SNMP Monitor 8.0A-0610 and 8.0A-0701

Date

25 February 2007

Summary

There is an issue with Turbo Mode for the Argent SNMP Monitor which affects Main Engines and Daughter Engines.

Technical Background

When Turbo Mode is activated on the Main Engine, all monitoring is fine for all products except the Argent SNMP Monitor. Error messages showing

skipped for pure IP node

can be seen in Relator Trace Logs for IP Devices monitored in the Argent SNMP Monitor. Below is a sample of a Relator Trace Log:

Mon Feb 12 11:35:03.886 ARGENTSERVERNAME argentserviceaccount Submitted

Mon Feb 12 11:35:03.870 ARGENTSERVERNAME argentserviceaccount Rule 'SNMP_RULE_NAME' is skipped for pure IP node '192.168.X.X' in Relator RELATOR_NAME

Mon Feb 12 11:40:03.903 ARGENTSERVERNAME argentserviceaccount Submitted

Mon Feb 12 11:40:03.903 ARGENTSERVERNAME argentserviceaccount Rule 'SNMP_RULE_NAME' is skipped for pure IP node '192.168.X.X' in Relator RELATOR_NAME

Mon Feb 12 11:45:03.749 ARGENTSERVERNAME argentserviceaccount Submitted

Mon Feb 12 11:45:03.733 ARGENTSERVERNAME argentserviceaccount Rule 'SNMP_RULE_NAME' is skipped for pure IP node '192.168.X.X' in Relator RELATOR_NAME

Mon Feb 12 11:50:06.172 ARGENTSERVERNAME argentserviceaccount Submitted

Mon Feb 12 11:50:06.172 ARGENTSERVERNAME argentserviceaccount Rule 'SNMP_RULE_NAME' is skipped for pure IP node '192.168.X.X' in Relator RELATOR_NAME

Mon Feb 12 11:55:14.628 ARGENTSERVERNAME argentserviceaccount Submitted

Daughter Engines experience the same issue when Turbo Mode is turned on.

Resolution

The work around is to turn off Turbo Mode from the registry for the Argent SNMP Monitor to 0 in

\HKEY_LOCAL_MACHINE\SOFTWARE\Argent\ArgentSNMPMonitor\Turbo Monitoring

This is a known issue and will be resolved in a future version.