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-71-1931959.1
Update Date:2015-03-13
Keywords:

Solution Type  Technical Instruction Sure

Solution  1931959.1 :   How To Change The SNMP Trap Severity  


Related Items
  • Oracle Communications Policy Management
  •  
Related Categories
  • PLA-Support>Sun Systems>CommsGBU>Broadband Network Solutions>SN-SND: Tekelec Policy
  •  




In this Document
Goal
Solution


Created from <SR 3-9629875041>

Applies to:

Oracle Communications Policy Management - Version POLICY 10.5.1 and later
Information in this document applies to any platform.

Goal

Can the Severity Levels of SNMP traps be changed?

Solution

According to the comcol-tc-mib, (text convention mib) the severity of traps is as follows:

ComcolAlarmSeverity ::= TEXTUAL-CONVENTION
  STATUS current
  DESCRIPTION
  "Alarm severity values"
  SYNTAX INTEGER {
  critical(1),
  major(2),
  minor(3),
  info(4),
  clear(5)
}
and this text convention is imported into PCRF-ALARM-MIB, so these are the severity values the PCRF will send.


To change the severity values to the SNMP system on our product would be considered an enhancement request. To request any enhancements to the product, you will need to do so via your Oracle Sales Account team, to make a Request For Feature (RFF)


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