Solved

Oracle dbconsole SNMP traps are recieved as coming from 127.0.0.1

Posted on 2011-09-19
7
731 Views
Last Modified: 2012-05-12
I am trying to configure SNMP trap alerts on an Oracle DB server.
The server is running a local instance of OEM dbconsole. I am NOT running GridControl.

I have configure the dbconsole to with a Notification Method to send snmp traps to my 3rd party trap receiver.
I can use the "Test SNMP Trap" button in the dbconsole to send a test trap to the receiver.
The test trap is received with one problem....
The receiver is seeing the trap as coming from the localhost address of 127.0.0.1 .
This has to be on the Oracle side of things. I have lots of other servers sending traps to this receiver both RedHat and Windows that work fine.
It looks like dbconsole is setting the snmp "aggent-addr" field to the 127.0.0.1 address.
Any ideas how to fix this so the receiver sees the traps as coming from the actual address of the sending host?

I am not sure if this an issue with Oracle setup, hosts file, snmp.conf file or other.
0
Comment
Question by:afcnoc
  • 3
  • 2
7 Comments
 
LVL 34

Expert Comment

by:Duncan Roe
ID: 36572538
Is the trap coming from the same system that runs Oracle? 127.0.0.1 is fine if so, otherwise completely wrong. Systems don't have a "real" address - they just have a number of network interfaces each with its own address. The local interface at 127.0.0.1 is one of these.
0
 

Author Comment

by:afcnoc
ID: 36573885
I do understand IP networking.
When the EM dbconsole send it's trap to the trap reciever (running on a different server, not the Oracle server) it is seen by the trap reciever as coming from the 127.0.0.1 address and not the address bound to the NIC in the db server.
Example:
The DB server has a single NIC connected to the network.
The IPv4 address bound to this NIC is 192.168.1.2
When the trap reciever gets the trap, it sees the trap as coming from the 127.0.0.1.
It should see the trap as coming from 192.168.1.2 not the loopback/local host address.
This is certainly not normal.

I have other RedHat servers with the same snmpd.conf file sending traps to this trap reciever and all of their traps are seen as coming from the IP of the NIC.
Granted, none of these serevers is running Oracle so the traps are coming from other agents. But their traps are still seen as coming from the correct IP.
0
 

Author Comment

by:afcnoc
ID: 36574188
I ran another test to try and isolate this issue.
I have hardware "health" agents running on the DB server that send SNMP traps to the same reciever.
I triggered some traps via the health agents and they were seen by the receiver as coming from the IP address of the NIC. Not the 127.0.0.1 address.
I really think this is an EM dbconsole issue putting the wrong IP in the SNMP trap for some reason.
0
 

Accepted Solution

by:
afcnoc earned 0 total points
ID: 37041732
I figured it out.
I had to add a line to the hosts file on the DB server that had the IP/hostname of the DB server.
0
 
LVL 34

Expert Comment

by:Duncan Roe
ID: 37043549
Yes you need that. Good pickup
0

Featured Post

New! My Passport Wireless Pro Wi-Fi Mobile Storage

Portable wireless storage to offload, edit, and stream anywhere.

High-capacity, wireless mobile storage designed to accompany professional photographers and videographers in the field to easily offload, edit and stream captured photos and high-definition videos.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

How to Create User-Defined Aggregates in Oracle Before we begin creating these things, what are user-defined aggregates?  They are a feature introduced in Oracle 9i that allows a developer to create his or her own functions like "SUM", "AVG", and…
Using SQL Scripts we can save all the SQL queries as files that we use very frequently on our database later point of time. This is one of the feature present under SQL Workshop in Oracle Application Express.
This video shows how to Export data from an Oracle database using the Original Export Utility.  The corresponding Import utility, which works the same way is referenced, but not demonstrated.
This video shows how to copy an entire tablespace from one database to another database using Transportable Tablespace functionality.

914 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

12 Experts available now in Live!

Get 1:1 Help Now