How to troubleshoot SNMP GET issues with Oracle Auto Service Request (ASR) Manager (Doc ID 1609484.1)

Last updated on MAY 07, 2021

Applies to:

Purpose

The ASR Manager uses the SNMP GET protocol to query ASR assets for additional fault information.
This is limited to the following products and fault telemetry sources:

• M-series servers (M3000, M4000, M5000, M9000), XSCF service processor
• Solaris 10 on ASR-qualified Oracle server that require FMA for ASR

These products send fault events to the ASR Manager using the SNMP TRAP protocol.
The ASR Manager uses the SNMP GET to retrieve additional fault information, such the FRU part number, serial number, and slot location,  from the product. This important information allows Oracle to streamline the service delivery process. When SNMP GET fails, Oracle support engineers will need to manually request diagnostics, which delays service.

The ASR Manager "test_snmp_get" command is used to verify SNMP GET connectivity.
Failure reasons include:

• incorrect asset configuration
  • Incorrect community string.
    The ASR Manager and all assets need to be configured to use the same community string. The default is "public" but it can be changed if needed.
• network configuration on routers and firewalls that prohibit the SNMP GET traffic

Notes:

• The "test_snmp_get" command is available in ASR Manager version 4.7 or later. ASR software download available on Doc ID 1185493.1.
• The "test_snmp_get" command does not work with an M-Series XSCF configured to use SNMP v.3. This is a known issue and is expected to be fixed in a future release of the ASR Manager.
  

Troubleshooting Steps

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.