E5MS :: Wrong Time Format In SNMP-Trap (NBI) (Doc ID 1968289.1)

Last updated on FEBRUARY 15, 2017

Applies to:

Oracle Communications EAGLE (Hardware) - Version E5-MS 45.0 to E5-MS 46.0 [Release E5-MS 45.0 to E5-MS 46.0]
Tekelec

Symptoms

On : E5-MS 45.0.1 version, E5-MS

ACTUAL BEHAVIOR
---------------
There is no timestamp Timezone (local offset) in the SNMP trap sent to far end.
e.g. missing "local offset", e.g. UTC+2.

EXPECTED BEHAVIOR
-----------------------
The time-stamps have to be analogical to ISO 8601 / RFC 3339.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Send SNMP trap via E5MS to far end
2. Take trace of trap received at far end
3. There will not be any local offset information in the trap

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, the far end cannot determine what is reference time for the timestamp mentioned in the SNMP trap.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms