| Asset ID: |
1-71-2295525.1 |
| Update Date: | 2017-08-11 |
| Keywords: | |
Solution Type
Technical Instruction Sure
Solution
2295525.1
:
HOW to Understand OCUDR Trap Format
| Related Items |
- Oracle Communications User Data Repository
|
| Related Categories |
- PLA-Support>Sun Systems>CommsGBU>Broadband Network Solutions>SN-SND: Tekelec UDR
|
In this Document
Created from <SR 3-15218364051>
Applies to:
Oracle Communications User Data Repository - Version UDR 12.1 and later
Tekelec
Goal
This document provides additional information help explain the OCUDR TRAP structure as it applies to MIBs.
Solution
The following is the OCUDR TRAP OID structure that the SNMP agent should be prepared to receive.
TRAP OID: <ORIGINAL_OID>.<TRAPFLAG>.<SRCNODEID>.<ALARMNUMBER>.<SIZEOFINSTANCE>.<INSTANCEDATA>
For example, below TrapOID for alarm 13071is shown below:
1.3.6.1.4.1.323.5.3.32.1.1.3.5.1.4.1.164.149.45.0.13071.4.80.82.79.86
ORIGINAL_OID: 1.3.6.1.4.1.323.5.3.32.1.1.3.5.1.4, this is the OID from the MIB file.
The following information is not provided in customer documentation and will help customers understand the OID structure.
TRAPFLAG = 1, either 0 or 1, so here if the Local trap is disabled then it will be set to 1 in the trap oid,
SRCNODEID = 164.149.45.0 , here this value is calclated based on the entry present in the srcNode. This is determined from the NODEINFO table. In this example, the nodeId is A1173.045.
From ITU X.731 Information technology - Open Systems Interconnection - Systems management: State management function
Source indicator: Section (8.2.2.1)
This parameter, when present, indicates the source of the operation that led to the generation of this notification type. It can have one of the following values.
- resource operation: The notification was generated in response to a state attribute value change effected through the internal operation of the resource.
- management operation: The notification was generated in response to a state attribute value change effected through an SMI management operation applied across the managed object boundary external to the managed object.
- unknown: It is not possible to determine the source of the operation.
If nodeId = A1173.045 , then level is A, 1173 is the ClusterNumber 045 is the MemberNumber and RUNID can be retrieved from the server using echo $RUNID, so in my enviornment RUNID is 0.
(level << 4 ) | ((ClusterNumber & 0xf00) >> 8) = ('A' << 4 ) | ((1173 & 0xf00) >> 8) = (0x41 << 4 ) | ((0x495 & 0xf00) >> 8) = 0xA4 = 164
1173 & 0xff = 0x495 & 0xff = 149
45 & 0xff = 0x2D & 0xff 0x2D = 45;
RUNID & 0xff = 0 & 0xff = 0
so finally 164.149.45.0 will be used as SRCNODEID.
ALARMNUMBER = 13071 , this is the eventnumber/alarmid from the AppEventLog tables.
SIZEOFINSTANCE = 4, this the size of the instance string from the AppEventLog_001 table for the alarm which is generated so in this case the size of the instance is 4.
INSTANCEDATA = 80.82.79.86 (PROV), this the value of the instance which is used from the AppEventLog_001 table so here the value of the instace is PROV so PROV decimal value will be appended to the final trap OID.
so P -> 80
R -> 82
O -> 79
V -> 86
so finally 80.82.79.86 will be used as INSTANCEDATA.
Similarly all the trapOIDs with in the MIB is calculated.
mysql> select * from AppEventLog_001 where eventNumber = 13071;
+------+-----------+----------+---------------------+---------+-------------+----------+-----------+---------------------------------------------------------------------------------------------------------+----------------+
| part | srcNode | severity | timeStamp | task | eventNumber | instance | eventData | errInfo | additionalInfo |
+------+-----------+----------+---------------------+---------+-------------+----------+-----------+---------------------------------------------------------------------------------------------------------+----------------+
| 0 | A1173.045 | ^^ | 1611745169468401377 | udrprov | 13071 | PROV | |
IDB_ENDTBL/CLR cursor at end of table [IdbBaseIter.cxx.cmf:209]
^^ [26904:ProvController.C:
INSTANCEDATA = PROV
Related document: See OCUDR MIB; Doc ID 2283955.1
Attachments
This solution has no attachment
