OCEEMS SNMP Traps Do Not Send Correct ID For Alarms
(Doc ID 2397421.1)
Last updated on MAY 14, 2018
Applies to:Oracle Communications EAGLE (Software) - Version E5-MS 46.2 and later
In OCEEMS we have configured some servers to be sent SNMP traps. That works well except one field into every trap is not the same that we observe in E5-MS system; that field is ID, or in MIB terminology :
We are able to observe all traps going to customer management systems by setting a tcpdump job in 162 port as follows:
In the OCEEMS DB, we can see following entry in the Event table:
We need your help for correcting this issue and that E5-MS sends correct ID, as customers needs to correlate alarms information.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!