Acme Packet (MOSC)

MOSC Banner

Oracle Communications Session Border Controller SNMP trap severity

edited Jan 2, 2020 3:46AM in Acme Packet (MOSC) 7 commentsAnswered ✓

When we configure AP4600 to send out SNMP traps, those traps do not include severity information.

Is it possible to replicate the internal alarm severity (minor, major, critical) in SNMP trap sent to trap receiver?

example, internal major alarm

805503220 14      4 2019-02-18 15:59:47     2019-02-18 15:59:47

Count   Description

1 gateway xxx.xxx.xxx.xxx unreachable on slot 0 port 3 subport 244

and corresponding SNMP trap:

Mon Feb 18 15:59:47 2019 .1.3.6.1.4.1.9148.3.1.2.0.1 Normal "Status Events" xxx.xx.xxx.xx - When a syslog message is generated by the device a sbc1 3 unknown gateway xxx.xxx.xxx.xxx unreachable on slot 0 port 3 subport 244 179:10:56:23.87

Note: for SNMP traps, acliconfiguration document includes sentence "The trap does not contain information associated with configured severity for that value."

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

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

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center