Oracle Key Manager (OKM): Unable To Configure SNMPv2 - errors with 'Verify that the SNMP Manager is reachable and is a valid SNMP Manager'

Asset ID:	1-72-1472498.1
Update Date:	2012-07-04
Keywords:

Solution Type Problem Resolution Sure

Solution 1472498.1 : Oracle Key Manager (OKM): Unable To Configure SNMPv2 - errors with 'Verify that the SNMP Manager is reachable and is a valid SNMP Manager'

Applies to:

Oracle Key Manager - Version 2.3 to 2.5 [Release 2.0]
Information in this document applies to any platform.

Symptoms

When trying to confguring a SNMP manager in the OKM GUI, after adding the SNMP Manager ID, Description, Network address (trap receiver), checked 'Flags' and setting the SNMPv2 Protocol Version, then clicking 'save', the OKM GUI reports the following error:

'Verify that the SNMP Manager is reachable and is a valid SNMP Manager. Retry when reachable and, if using SNMPv3, specify a correct username and passphrase.'

The message is also seen in the Systemdump -> KMSAuditLogEntries.txt file.

E1B2CB4150181F1A00000000000006A7        E1B2CB4150181F1A        kma_01       SNMP Management Operations      Medium Term Retention   Modify SNMP Manager Details     Cannot contact the SNMP Manager or it is not a valid SNMP Manager       Error   000188000347    2012-06-19 14:22:35.172185+00   nick    159.81.106.53   SNMP Manager ID = SNMP01, Description = SNMP rec 01 receiver, SNMP Manager Network Address = 10.170.214.61, Enabled = TRUE, User Name =  , SNMP Protocol Version = v2   Verify that the SNMP Manager is reachable and is a valid SNMP Manager. Retry when reachable and, if using SNMPv3, specify a correct username and passphrase.

However the SNMP receiver receives an inform request:

1340115750 2012-06-19 14:22::36 [159.81.106.105] [INFORM, SNMP v2c, community public] Cold Start 0 BINDS SNMPv2-MIB::snmpTrapOID.0 = SUN-SNMP::prod.22.99       SUN-SNMP::prod.22.99.3 = "Test SNMP Message"

Changes

No changes made.

Cause

When OKM sends a SNMP inform request, it will go out on port 162 to the SNMP receiver, and the response will be sent back to the OKM server by via port 161. Port 161 was not open on the firewall.

Solution

Make sure that port 161 is open on the firewall between the SNMP trap receiver and the OKM server.

Attachments

This solution has no attachment