Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-72-2189213.1
Update Date:2017-02-23
Keywords:

Solution Type  Problem Resolution Sure

Solution  2189213.1 :   NBI SNMP V3 Interface - Wrong UAM/UIM Format In SNMP Trap  


Related Items
  • Oracle Communications EAGLE (Software)
  •  
Related Categories
  • PLA-Support>Sun Systems>CommsGBU>Global Signaling Solutions>SN-SND: Tekelec EMS
  •  




In this Document
Symptoms
Cause
Solution
References


Created from <SR 3-12174897561>

Applies to:

Oracle Communications EAGLE (Software) - Version E5-MS 46.2 to EAGLE 46.2 [Release E5-MS 46.0 to EAGLE 46.0]
Tekelec

Symptoms

On : E5-MS 46.2 version, E5-MS (Production)

ACTUAL BEHAVIOR
---------------
E5MS46.2 send the UAM/UAM code via SNMP V3 in a wrong format to NMS tool. Normally all UIM/UAM numbers are four-digit, e.g. 0048 - Terminal failed.

The display in E5MS is correct but in the SNMP Trap E5MS send the code 48 - Terminal failed instead 0048.

In E5MS-Version 45.0.1. the SNMP-Traps (V2C) are correct and the UIM/UAM-code is four-digit.

EXPECTED BEHAVIOR
-----------------------
The E5MS should send the full four digits of UAM and should not remove 0 from the two digit or three digit UAMs.
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Create a two digit or three digit alarm on the Eagle (e.g. UAM 0048)
2. See the alarm displayed on E5MS with full code 0048
3. Check SNMP trap sent by E5MS to NMS tool. It will be only 48 and not the full 0048

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, NMS system cannot correctly identify the alarm code as it expects four digits, but is getting only two.

Cause

In release 46.2; there is a code change due to which the EventID is read and used without padding.
Hence the preceding zeros are missed.

Solution

The issue is resolved by upgrading to OCEEMS version 46.2.0.0.1-462.13.0 or higher.The following bug outlines this solution:

The solution will do the following:
1. Will use the Event ID as standard four digit code hence the zeros will not be removed.
 

References

<BUG:22805651> - SR: OCEEMS 46.2 DOES NOT PROPERLY PAD THE UAM/UIM IN THE SNMP TRAP.

Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback