000014595 - SNMP requests against aserver do not work after the aserver is restarted.

Document created by RSA Customer Support Employee on Jun 16, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000014595
Applies ToRSA Access Manager 6.0.4
SNMP
IssueSNMP requests against aserver do not work after the aserver is restarted.
SNMP get request returns the error "No Such Object available on this agent at this OID" when requesting a counter from the aserver after the aserver has been restarted.
Cause If the asever is stopped and a specific SNMP "get" request returns an error the SNMP get will continue to return an error for that counter even if the aserver is restarted. This problem occurs because the aserver fails to create a new SNMP connection pool.   If a GET is created for a separate counter, or an SNMP "walk" is done against a separate portion of the MIB database a new connection will be created.  This problem only occurs if a custom listen port is defined in the aserver.conf file.
ResolutionThis problem has been resolved in hotfix 6.0.4.15 for Access Manager 6.0.4.  Please contact RSA Customer Support and request this hotfix, or the latest cumulative hotfix for your platform.  Note that this hotfix is for 6.0.4 and if you are on an earlier version of Access Manger you must patch to 6.0.4 prior to applying this hotfix.
Workaround

The Access Manager aserver is configured to listen on a unique port for SNMP registration

cleartrust.aserver.instrumentation.listen.port=6000

Legacy Article IDa44508

Attachments

    Outcomes