Oracle Communications Session Border Controller

(1)

Formerly Net-Net Session Director

(2)

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government. This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

(3)

About this Guide . . . vii

Introduction . . . vii

Supported Platforms . . . vii

About the Net-Net MIB Reference Guide . . . viii

Documented Objects and Traps. . . viii

Acme Packet Platform sysObjectIDs . . . ix

Revision History . . . ix

Acme Packet MIBs . . . 11

Overview . . . 11

About MIBs . . . 11

About Managed Objects . . . 13

About SNMP Traps . . . 13

SNMPv3 Secure Traps . . . 13

Authentication and Privacy . . . 14

Enabling SNMPv3 . . . 14

Consideration for HA Nodes . . . 15

ACLI Instructions and Examples . . . 15

MIBs Supported by Acme Packet . . . 17

About Traps . . . 19

Standard Traps. . . 19

Enterprise Traps. . . 20

Net-Net EMS Traps . . . 25

Net-Net System Alarms . . . 26

Alarm Clearing . . . 37

Acme Packet Log Levels and syslog Level Severities . . . 38

Acme Packet Log Levels . . . 38

syslog Level Severities. . . 39

Mapping Trap Filter Levels to syslog and Alarm Severities. . . 39

Standard SNMP GET Requests . . . 41

Introduction . . . 41

(4)

Interface Scalar Example . . . .43

Interface Table Examples . . . .43

ifName Support (RFC 2863) . . . .44

Examples of ifIndex Values . . . .44

High Capacity MIB Counters (ifXtable Support) . . . .45

IP Group . . . .48

IP Scalar Example . . . .50

IP Address Table Example . . . .51

ICMP Group . . . .52

ICMP Scalar Example. . . .53

TCP Group . . . .54

TCP Scalar Example . . . .56

TCP Connection Table Example . . . .56

UDP Group . . . .57

UDP Scalar Example . . . .57

UDP Table Example . . . .58

System Group . . . .58

System Scalar Example. . . .59

Object Resource Information. . . .60

SNMP Group . . . .61

SNMP Scalar Example . . . .62

Physical Entity Table (rfc2737.mib). . . .63

entPhysicalTable Example . . . .67

entity Physical Table Scalar Example . . . .68

Enterprise SNMP GET Requests . . . .69

Introduction . . . .69

Acme Packet syslog MIB (ap-slog.mib) . . . .69

Syslog Scalar Example . . . .71

Syslog History Table Examples . . . .71

Acme Packet System Management MIB (ap-smgmt.mib) . . . .72

System Management Scalar Examples . . . .83

Session Statistical Group Table Examples . . . .84

SIP Session Agent Statistics Table Example. . . .85

H.323 Session Agent Statistics Table Example . . . .85

Signaling Realm Statistics Table Example . . . .86

Notes on ENUM Server Names . . . .87

Acme Packet License MIB (ap-license.mib). . . .88

(5)

Acme Packet Environment Monitor MIB (ap-env-monitor.mib) . . . 92

I2C State Scalar Examples . . . 96

Voltage Status Table Examples. . . 96

Temperature Status Table Examples . . . 96

Fan Status Table Examples . . . 97

Power Supply Status Table Examples . . . 97

Acme Packet H.323 MIB (ap-h323.mib) . . . 97

Acme Packet Security MIB (ap-security.mib) . . . 97

Acme Packet Diameter MIB (ap-diameter.mib). . . 98

Acme Packet SIP MIB (ap-sip.mib) . . . 99

Acme Packet Codec and Transcoding MIB (ap-codec.mib) . . . 100

Transcoding Capacity in Acme Packet System Management MIB (ap-smgmt.mib) . . . 103

Acme Packet (ap-usbcsys.mib) Multicore Monitoring MIB . . . 103

References . . . 105

Overview . . . 105

Enterprise Trap Examples . . . 107

Overview . . . 107

Enterprise Trap Examples. . . 107

snmp-community and trap-receiver Elements. . . 107

syslog MIB Trap Examples . . . 108

System Management MIB Trap Example . . . 120

(6)

(7)

Introduction

The Oracle Communications Session Border Controller HDR Resource Guide provides

information about the following:

• Management Information Base (MIBs)

• Acme Packet’s enterprise MIBs

• General trap information, including specific details about standard traps and

enterprise traps

• Simple Network Management Protocol (SNMP) GET query information,

including standard and enterprise SNMP GET query names, object identifier

names and numbers, and descriptions

• Example of scalar and table objects

• This guide also describes the correlation between system alarms and the MIBs

that support traps, and it provides reference information about log levels, syslog

level severities (the protocol used for the network logging of system and

network events), and trap receiver filter levels. Appendix A contains several trap

examples. Appendix B contains the location of documents where you can obtain

more information.

Supported

Platforms

Release Release S-CZ7.1.2 is supported on the Acme Packet 4500 and Acme Packet

6300 series platforms.

The following table lists the members that comprise the documentation set for this

release:

Document Name Document Description Acme Packet 4500 System Hardware

Installation Guide

Contains information about the components and installation of the Acme Packet 4500 system. Acme Packet 6300 Hardware

Installation Guide

Contains information about the components and installation of the Acme Packet 6300 system.

Release Notes Contains information about the current documentation set release, including new features and management changes. ACLI Configuration Guide Contains information about the administration and

software configuration SBC.

(8)

ABOUT THIS GUIDE

About the Net-Net MIB Reference Guide

Documented

Objects and Traps

This Net-Net SBC MIB Reference Guide only documents the traps and objects

supported in the release version S-CZ7.1.2 for the AP3820, AP4500, AP6100, and

AP6300 platforms. Acme Packet enterprise MIBs, however, can contain additional

traps and objects not documented here.

Enterprise MIB files are global across all Net-Net session border controllers. Each

MIB contains a superset of objects and traps for all Net-Net SBC:

• platforms

• current releases

• prior releases

In addition, a MIB might contain objects and traps intended for future releases. For

example, the ap-smgmt.mib might contain traps intended for support in release

Release S-CZ7.1.2.

Objects and traps are not supported in this release version and not documented in

this guide if they are intended for a:

• platform other than the 4000

• future release

You can verify what is supported in this release version by:

1. Reviewing the list of supported capabilities in MIB README.txt.

2. Reading the capability descriptions in the ap-agentcapability.mib to identify

which object and/or notification groups they contain and in which MIB those

groups are located.

Maintenance and Troubleshooting Guide

Contains information about Net-Net SBC logs, performance announcements, system management, inventory management, upgrades, working with configurations, and managing backups and archives.

MIB Reference Guide Contains information about Management Information Base (MIBs), Enterprise MIBs, general trap information, including specific details about standard traps and enterprise traps, Simple Network Management Protocol (SNMP) GET query information (including standard and enterprise SNMP GET query names, object identifier names and numbers, and descriptions), examples of scalar and table objects. Accounting Guide Contains information about the SBC’s accounting support,

including details about RADIUS accounting.

HDR Resource Guide Contains information about the SBC’s Historical Data Recording (HDR) feature. This guide includes HDR configuration and system-wide statistical information. Administrative Security Essentials Contains information about the SBC’s support for its

(9)

Acme Packet

Platform

sysObjectIDs

Each hardware platform in the Net-Net family has a designated system object ID

(sysObjectID). In addition to the system object ID, each platform includes a

descriptive string (sysDescr) comprised of the product name followed by a string

identifying the full software version operating on the system.

The table below provides sysObjectID values for all Net-Net platforms and their

corresponding sysDescr values. X stands for a string value of the software version,

such as SCX6.1.0.

Platform

sysObjectID

Object Identifier Name:

Number

sysDescr

Net-Net 4250 apNetNet4250:

1.3.6.1.4.1.9148.1.1.1

Acme Packet Net-Net 4000 Series SBC X Net-Net 4500 apNetNet4500:

1.3.6.1.4.1.9148.1.1.2

Acme Packet Net-Net 4500 X Net-Net 3800

(Sku 3810)

apNetNet3800:

1.3.6.1.4.1.9148.1.3.1

Acme Packet Net-Net 3800 X Net-Net 3820 apNetNet3820:

1.3.6.1.4.1.9148.1.3.2

Acme Packet Net-Net 3820 X Net-Net 6000 series apNetNet6000Series:

1.3.6.1.4.1.9148.1.5

Net-Net 6000 Series Net-Net 6300: apNetNet6300

1.3.6.1.4.1.9148.1.5.1

The Net-Net 6300 product

Revision History

This section contains a revision history for this document.

Date Description July 17, 2013 September 2013 January 2014 October 2014 April 2015

DIAMETER Rf

Charging Failure and

Recover Detection

The Net-Net SBC can detect and send a trap when Diameter Rf transport interface

has failed and when it has recovered. If multiple transport failures have been

• Initial Release

•

Updated apEnvMonFanStatusType and

removed all references to sd2

•

Updated

apSigRealmStatsAverageLatency and

apSigRealmStatsMaxLatency to (not

supported

• Corrects references to power supply orientation

(10)

ABOUT THIS GUIDE

detected, SNMP traps are sent for each failure. Local alarms are also generated for

these events.

• apDiameterAcctSrvrUpTrap

• apDiamAcctSrvrDownTrap

DIAMETER Internal

Errors

The Net-Net SBC creates internal errors and sends traps upon a CCF returning an

_{error-containing ACA.}

• apDiameterSrvrErrorResultTrap

• apDiameterSrvrSuccessResultTrap

Diameter Rf Charging

Buffering and Storage

Diameter Rf Charging, Buffering, and Storage enables the Net-Net SBC to buffer all

_{accounting requests (ACR) in memory for a configurable number of ACRs. The}

Net-Net SBC sends an SNMP trap when accounting records begin to drop from the

buffer due to an overflow condition. Subsequently, a clearing SNMP trap is sent once

the fault condition is removed.

• apAcctMsgQueueFullTrap

• apAcctMsgQueueFullClearTrap

Registrations on

Secondary Interfaces

New objects and traps are added to monitor the total number of registrations on

_{secondary interfaces.}

(11)

Overview

This chapter describes Acme Packet

®

Management Information Bases (MIBs) and

the correlation between Net-Net

®

system alarms and the MIBs that support traps. It

also provides reference information about Acme Packet log levels, syslog level

severities (the protocol used for the network logging of system and network events),

and trap receiver filter levels.

About MIBs

Each network device managed by SNMP must have a MIB that describes its

manageable objects. MIBs are collections of objects or definitions that define the

properties of the managed objects. Each managed object has specific characteristics.

The manager relies upon the database of definitions and information about the

properties of managed resources and the services the agents support. When new

agents are added to extend the management domain of a manager, the manager

must be provided with a new MIB component that defines the manageable features

of the resources managed through that agent.

The data types and the representations of resources within a MIB, as well as the

structure of a particular MIB, are defined in a standard called the Structure of

Management Information (SMI).

Object Identifiers and

Instance IDs

Each managed object/characteristic has a unique object identifier (OID) consisting

_{of numbers separated by decimal points (for example, 1.3.6.1.4.1.9148.1); numeric}

OIDs can also be translated into human-readable form. The MIB associates each

OID with a readable label and various other parameters related to the object. The

OID identifies the location of a given managed object within the MIB tree hierarchy

by listing the numbers in sequence from the top of the tree down to the node,

separated by dots.

By specifying a path to the object through the MIB tree, the OID allows the object to

be uniquely identified. The digits below the enterprise OID in the tree can be any

sequence of user-defined numbers chosen by an organization to represent its private

MIB groups and managed objects.

An instance ID identifies developments that have occurred for the managed object.

The instance ID values are represented as a combination of the OID and the table

index. For example, you can find the following instance ID in the TCP connection

table:

tcpConnState.127.0.0.1.1024.127.0.0.1.3000

•

tcpConnState

is the OID

•

127.0.0.1

is an IPv4 address

•

1024

is the port number

(12)

ACME PACKET MIBS

MIB Tree Structure

MIBs are arranged in a tree-structured fashion, similar in many ways to a operating

system directory structure of files. The following diagram illustrates a MIB tree with

a sample of the standard MIBs shown under the mib-2 node and a sample of a Acme

Packet system management enterprise MIB under the enterprise node. (The listing

is only a partial sample of the MIB contents.)

The diagram shows how the OID is a concatenation of the prior addresses up to that

point. For example, the OID for apSysCPUUtil is 1.3.6.1.4.1.9148.3.2.1.1.1.

DFPH3DFNHW0JPW DS6\VWHP0DQDJHPHQW0RGXOH DS6\V0JPW0,%2EMHFWV DS6\V&388WLO DS6\V0HPRU\8WLO DS6\V+HDOWK6FRUH DS6\V5HGXQGDQF\ RUJ GRG LQWHUQHW DFPHSDFNHW DS6\V0JPW*HQHUDO2EMHFWV V\VWHPV ,QWHUIDFHV LS LFPS WFS XGS LVR GLUHFWRU\ PJPW H[SHULPHQWDO SULYDWH PLE HQWHUSULVH

(13)

Scalar MIB Objects

Scalar MIB objects contain one precise piece of data (also referred to as discrete).

These objects are often distinguished from the table objects by adding a

.0

(dot-zero)

extension to their names. Many SNMP objects are scalar. That is, the operator

merely has to know the name of the object and no other information. Discrete

objects often represent summary values for a device, particularly useful for scanning

information from the network for the purposes of comparing network device

performance. If the extension (instance number) of the object is not specified, it can

be assumed as

.0

(dot-zero). See the Enterprise SNMP Get Requests chapter for

examples of scalar MIB objects.

Table MIB Objects

Table MIB objects contain multiple pieces of management data. These objects are

distinguished from the scalar objects by requiring a

.

(dot) extension to their names

that uniquely distinguishes the particular value being referenced. The

.

(dot)

extension is also referred as the instance number of an SNMP object. In the case of

table objects, this instance number is the index into the SNMP table. (In the case of

scalar objects, this instance number is zero.)

SNMP tables allow parallel information to be supported. Tables are distinguished

from scalar objects, in that tables can grow without bounds. For example, SNMP

defines the ifDescr object as a standard SNMP object, which indicates the text

description of each interface supported by a particular device. Since network devices

can be configured with more than one interface, this object could only be

represented as an array. By convention, SNMP objects are always grouped in an

Entry directory, within an object with a Table suffix. (The ifDescr object described

above resides in the ifEntry directory contained in the ifTable directory.) See the

Enterprise SNMP Get Requests chapter for examples of table MIB objects.

About SNMP Traps

The MIB also contains information about SNMP traps, which enable an agent to

notify the management station of significant events by way of an unsolicited SNMP

message. When an element sends a TRAP packet, it can include OID and value

information (bindings) to clarify the event.

SNMPv3 Secure Traps

The Net-Net SBC supports SNMPv3, which provides the SNMP agent and SNMP

Network Management System (NMS) with authentication, privacy, and access

control during the delivery of secured traps. Currently, SNMPv3 traps are supported

on the Net-Net SBC; SNMPv3 Get/Get-Bulk/Set actions are not supported at this

time.

By default, the Net-Net SBC supports SNMPv1v2. If you want to retain existing

SNMPv1v2 behavior, you do not need to update configuration. You can enable

SNMPv3 at any time, at which point SNMPv1v2 configurations are ignored, and

only SNMPv3 encrypted traps are sent to associated external SNMP managers.

Snmp-agent-mode, an attribute under system-config, allows you to select the

(14)

ACME PACKET MIBS

Authentication and

Privacy

SNMPv3 employs a User-Based Security Model (USM). The two protocols used for

authentication and privacy are:

• Authentication—HMAC-SHA-96

• Privacy—CBC-DES

Four parameters generate keys under the designated algorithm:

• SNMPEngineID—The unique identifier for the SNMP Engine. This value is

a specially formatted string for use in the SNMP.

• User name—The user’s name as defined under snmp-user-entry.

• Authorization password—The authorization password configured under the

snmp-user-entry configuration. This parameter is used to derive the

authentication key.

• Privacy password—You set the privacy password in the snmp-user-entry

configuration. It is used to derive the password key.

Password-to-Key

Conversion

There are two distinct passwords in SNMPv3. The authentication password is

_{manipulated using the HMAC-SHA-96 algorithm to produce a key used to}

authenticate the trap. Authentication ensures the identity of the user and that the

trap has not been tampered with in transit. Likewise, the privacy password is

manipulated using the CBC-DES algorithm to ensure message privacy.

One user is associated by a name, an authentication password and a privacy

password. These three parameters are always consistent for the user and can be used

across multiple SBCs. The key generation differs from one SBC to another due to the

varying SNMPEngineIDs. This ensures that a compromised key for one SBC does

not compromise the keys for other SBCs associated with the same user.

Enabling SNMPv3

The table below gives a brief overview of the SNMPv3 configuration on your

Net-Net SBC. The Caveats column describes the SNMPv1V2 configuration attributes

that are ignored if SECURE-TRAP mode is enabled.

Configuration Description Caveat

snmp-agent-mode Set this attribute to SECURE-TRAP to enable SNMPv3.

Once SNMPv3 is enabled, the snmp-community and snmp-community-name attributes are ignored.

snmp-engine-id-suffix

Set this attribute as a string to customize and uniquely identify the SNMP Engine.

The show snmp-info command has been expanded to include the SNMP Engine Base, the SNMP Engine Suffix, and the SNMP Engine ID.

snmp-user-entry Enter the user name, authorization password and privacy password.

(15)

Retaining Existing

SNMPv1v2 Behavior

If you are upgrading to software version S-CX6.3.0 or above and want to retain your

_{existing SNMP configurations, you do not need to take any action. The Net-Net SBC}

sets snmp-agent-mode to V1V2 by default, disabling all SNMPv3 configurations.

Downgrading

Software After

Enabling SNMPv3

If you enable SNMPv3 on an SBC running S-CX6.3.0 or above, and you downgrade

to a previous software version, the software does not recognize the SNMPv3

configuration objects or attributes.

Consideration for

HA Nodes

Key pairs are generated based on the user and SNMPEngineID. In the event of a

switchover, the SNMPEngineID will vary. The user’s NMS should be updated with

the SNMPEngineID of the standby SBC.

ACLI Instructions

and Examples

This section shows you how to enable SNMPv3 on your system, how to add users,

and how to add users to authorized trap receivers.

Enabling SNMPv3

To enable SNMPv3 on the Net-Net SBC for sending secured traps:

1. In Superuser mode, type configure terminal and press <Enter>.

ACMEPACKET# configure terminal

2. Type system and press <Enter>.

ACMEPACKET(configure)# system

3. Type system-config and press <Enter>.

ACMEPACKET(system)# system-config ACMEPACKET(system-config)#

4. snmp-agent-mode—To enable support, change this parameter from its default

(V1V2) to SECURE-TRAP.

ACMEPACKET(system-config)# snmp-agent-mode secure-trap

5. snmp-engine-id-suffix—To set a unique suffix for the SNMPEngineID, enter

a string. This attribute is optional.

ACMEPACKET(system-config)# snmp-engine-id-suffix Group1Unit3

Users and Password

Configuration

To configure users for SNMPv3:

1. In Superuser mode, type configure terminal and press <Enter>.

2. Type system and press <Enter>.

IP address of the NMS that receives secured traps. user-list Add users who are authorized to

receive secured traps.

(16)

ACME PACKET MIBS

3. Type snmp-user-entry and press <Enter>.

ACMEPACKET(system)# snmp-user-entry ACMEPACKET(snmp-user-entry)#

4. user-name—Enter the name for this user. This value is required and must be

unique.

ACMEPACKET(snmp-user-entry)# user-name monitor

5. auth-password—Enter the authorization password for this user. Passwords

must be 6-24 characters long. The password will be shown as “****” regardless

of the length. This value is required.

ACMEPACKET(snmp-user-entry)# auth-password ****

The system will prompt you to enter the password again.

6. priv-password—Enter the privacy password for this user. Passwords must be

6-24 characters long. The password will be shown as “****” regardless of the

length. This value is required.

ACMEPACKET(snmp-user-entry)# priv-password ****

The system will prompt you to enter the password again.

Adding Authorized

Trap Receivers

To add users as authorized trap-receivers:

1. In Superuser mode, type configure terminal and press <Enter>.

2. Type system and press <Enter>.

3. Type trap-receiver and press <Enter>.

ACMEPACKET(system)# trap-receiver ACMEPACKET(trap-receiver)#

4. ip-address—Enter the IP address and port for the NMS that supports SNMPv3.

ACMEPACKET(trap-receiver)# ip-address 172.30.0.82:1620

5. user-list—Add or subtract users to the list using (+) and (-) symbols.

(17)

(enterprise MIBs). The configurable Net-Net system elements are identified in the

MIBs provided by Acme Packet. Every Net-Net system maintains a database of

values for each of the definitions written in these MIBs.

Standard MIBS

The values in the standard MIBs are defined in RFC-1213, (one of the governing

specifications for SNMP). A standard MIB includes objects to measure and monitor

IP activity, TCP activity, UDP activity, IP routes, TCP connections, interfaces, and

general system description. Each of these values is associated both an official name

(such as sysUpTime, which is the elapsed time since the managed device was

booted) and a numeric value expressed in dot-notation (such as 1.3.6.1.2.1.1.3.0,

which is the OID for sysUpTime).

Acme Packet provides the following standard MIBs:

• rfc3411-framework.mib

• rfc1907-snmpv2.mib

• rfc2011-ip.mib

• rfc2737-entity.mib

• rfc2863-if.mib (Acme Packet supports the ifName entry of the ifXTable, which is

an extension to the interface table and which replaces ifExtnsTable. See RFC

2863 for details.)

• ianaiftype.mib

• rfc4001-inetAddr.mib

• rfc4022-tcp.mib

• rfc4113-udp.mib

Acme Packet

Enterprise MIBs

Acme Packet provides the following enterprise MIBs:

MIB Name Description

ap-agentcapability.mib Details the SNMP agent’s capabilities that includes support for different modules:

• SNMPv2 capabilities support the SNMPv2 MIB and include the systemGroup, snmpGroup, snmpCommunityGroup, and snmpBasicNotificationsGroup variables.

• MIB-II capabilities support MIB-II and include the User Datagram Protocol (UDP)-MIB (udpGroup) variables and some, but not all of the IF-MIB (ifGeneralGroup and ifPacketGroup), IP-MIB (ipGroup and icmpGroup), and TCP-MIB (tcpGroup) variables. For more information about which variables are currently supported, refer to the ap-agentcapability.mib file.

• MIB capabilities include support for the contents of the Acme Packet MIBs listed in this table. Refer to the individual MIBs for details.

ap-ami.mib Acme Packet management interface on the Net-Net SBC. ap-codec.mib Codec and transcoding information generated by Acme Packet

(18)

ACME PACKET MIBS

ap-ems.mib Net-Net EMS traps.

ap-entity-vendortype.mib Acme Packet OID assignments for Acme Packet hardware components.

ap-env-monitor.mib Fan speed, voltage, temperature, and power supply for the Net-Net system. It also sends out traps when status changes occur. ap-license.mib Status of your Net-Net licenses.

ap-products.mib Descriptions of the different Net-Net SBC versions.

ap-security.mib Information about the Acme Management Interface running on the Net-Net SBC.

ap-slog.mib syslog messages generated by the Net-Net system via SNMP. Used for the network logging of system and network events, the syslog protocol facilitates the transmission of event notification messages across networks. The Acme Packet syslog MIB can also be used to allow remote log access. The SNMP system manager references syslog to find out about any and all syslog messages.

If the following conditions are present, the SNMP agent sends an SNMP trap when a message is sent to the syslog system: • The system configurations’s snmp-enabled parameter is

set to enabled.

• The system configuration’s enable-snmp-syslog-notify parameter is set to enabled.

• The actual syslog severity level is of equal or greater severity than the severity level configured in the system config’s snmp-syslog-level field.

No trap is sent under the following conditions:

• A syslog event is generated and the system config’s enable-snmp-syslog-notify parameter is set to disabled. • The actual syslog severity level is of lesser severity (for

example, higher numerical code value) than the severity level configured in the system config’s snmp-syslog-level parameter.

ap-smgmt.mib Status of the Net-Net system (for example, system memory or system health).

ap-smi.mib General information about the Net-Net system’s top-level architectural design.

ap-swinventory.mib Status of the boot images, configuration information, and bootloader images for the Net-Net system.

ap-tc.mib Textual conventions used in Acme Packet enterprise MIBs.

(19)

system. A trap is initiated by tasks to report that an event has happened on the

Net-Net system. SNMP traps enable an SNMP agent to notify the NMS of significant

events using an unsolicited SNMP message.

Acme Packet uses SNMPv2c. These notification definitions are used to send

standard traps and Acme Packet’s own enterprise traps.

Traps are sent according to the criteria established in the following:

• IETF RFC 1907 Management Information Base for Version 2 of the Simple Network

Management Protocol

• IETF RFC 2233 The Interfaces Group MIB using SMIv2

• Appropriate enterprise MIB (for example the Acme Packet syslog MIB or the

Acme Packet System Management MIB).

Standard Traps

The following table identifies the standard traps that the Net-Net system supports.

Trap Name Description

linkUp The SNMPv2 agent detects that the ifOperStatus object of an interface has transferred from the down state to the up state. The ifOperStatus value indicates the other state.

linkDown The SNMPv2 agent detects that the ifOperStatus object of an interface has transferred from the up state to the down state. The ifOperStatus value indicates the other state.

coldStart The SNMPv2 agent is reinitializing itself and its configuration may have been altered.

This trap is not associated with a Net-Net system alarm. authenticationFailure The SNMPv2 agent received a protocol message that

was not properly authenticated. If the snmp-enabled and enable-snmp-auth-traps fields in the ACLI’s system-config element are set to enabled a

snmpEnableAuthenTraps object is generated.

(20)

ACME PACKET MIBS

Enterprise Traps

The following table identifies the proprietary traps that Net-Net system supports.

apEnvMonI2CFailNotification: 1.3.6.1.4.1.9148.3.3.4.0.1

Sent when the Inter-IC bus (I2C) state changes from normal (1) to not functioning (7). apEnvMonPortChangeNotification:

1.3.6.1.4.1.9148.3.3.4.0.5

For Net-Net SBC 4500 only. Generated if a physical port is inserted/present or removed/not present.

apEnvMonStatusChangeNotification: 1.3.6.1.4.1.9148.3.3.4.0.2

Sent when any entry of any environment monitor table changes in the state of a device being monitored. To receive this trap, you need to set the system config’s enable- env- monitor- table value to enabled.

apH323StackMaxCallThresholdTrap: 1.3.6.1.4.1.9148.3.10.3.0.1

Generated when the number of H.323 calls increases the percentage of the max calls threshold.

apH323StackMaxCallThresholdClearTrap: 1.3.6.1.4.1.9148.3.10.3.0.2

Generated when the number of H.323 calls decreases to below the lowest max calls theshold.

apLicenseApproachingCapacityNotification: 1.3.6.1.4.1.9148.3.5.3.0.1

Generated when the total number of active sessions on the system (across all protocols) is within 98 - 100% of the licensed capacity.

apLicenseNotApproachingCapacityNotification: 1.3.6.1.4.1.9148.3.5.3.0.2

Generated when the total number of active sessions on the system (across all protocols) has gone to or below 90% of its licensed capacity (but no sooner than 15 seconds after the original alarm was triggered).

apSecurityTunnelFailureNotification: 1.3.6.1.4.1.9148.3.9.3.1.0.1

Generated when an IPSec IKEV2 tunnel cannot be established. apSecurityTunnelDPDNotification:

1.3.6.1.4.1.9148.3.9.3.2.0.1

Generated when an IPSec IKEV2 tunnel fails because of Dead Peer Detection (DPD). apSyslogMessageGenerated:

1.3.6.1.4.1.9148.3.1.2.0.1

Generated by a syslog event. For example, this trap is generated if a switchover alarm occurs (for High Availability (HA) Net system peers only), or if an HA Net-Net system peer times out or goes out-of-service.

apSysMgmtAlgdCPULoadTrap: 1.3.6.1.4.1.9148.3.2.6.0.24

Generated if the CPU utilization percentage of application tasks has exceeded the threshold algd-load-limit.

apSysMgmtAlgdCPULoadClearTrap: 1.3.6.1.4.1.9148.3.2.6.0.25

Generated when the CPU utilization percentage of application tasks has fallen below the threshold algd-load-limit.

apSysMgmtRejectedMesagesThresholdExeededTr ap

1.3.6.1.4.1.9148.3.2.6.0.57

Generates when the number of rejected messages exceeds the configured threshold within the configured window. This trap is used for both whitelists and HMR rejected messages. The trap does not indicate which feature enabled this trap. To indicate which messages and rules generated the trap, you can consult the matched.log file. apSysMgmtAdminAuditLogFullTrap:

1.3.6.1.4.1.9148.3.2.6.0.58

Generated when one of the audit logs full threshold is met: • time interval

• file size • percentage full apSysMgmtAdminAuditLogFullClearTrap:

1.3.6.1.4.1.9148.3.2.6.0.59

Generated when free audit log storage space becomes available. apSysMgmtAdminAuditPushFailTrap:

1.3.6.1.4.1.9148.3.2.6.0.60

Generated when the audit file transfer fails. apSysMgmtAdminAuditPushFailClearTrap:

1.3.6.1.4.1.9148.3.2.6.0.61

Generated when the audit file is successfully transferred. apSysMgmtAdminAuthLockoutTrap:

1.3.6.1.4.1.9148.3.2.6.0.64

(21)

1.3.6.1.4.1.9148.3.2.6.0.16 using the console fails for any reason; also sent when if a user fails authentication on the console or over FTP, SSH, or SFTP. The trap sent to all configured trap receivers includes the following information:

• administration and access level (SSH, user, enable) • connection type (Telnet or console)

FTP support is new to Release C5.0. apSysMgmtCallRecordingStateChangeTrap:

1.3.6.1.4.1.9148.3.2.6.0.50

Generated when a call recording server changes state.

apSysMgmtCdrFileDeleteTrap Generated when a CDR file is deleted because of lack of space on the partition or the drive exceeds the number of files specified.

apSysMgmtCDRPushReceiverFailureTrap: 1.3.6.1.4.1.9148.3.2.6.0.53

Generated when an enabled CDR push receiver fails. Returns the address, the address type, and the failure reason code.

apSysMgmtCDRPushReceiverFailureClearTrap: 1.3.6.1.4.1.9148.3.2.6.0.54

Generated when an enabled CDR push receiver resumes normal operation after a failure.

apSysMgmtCDRPushAllReceiversFailureTrap: 1.3.6.1.4.1.9148.3.2.6.0.55

Generated when all enabled CDR push receivers fail. apSysMgmtCDRPushAllReceiversFailureClearTrap

1.3.6.1.4.1.9148.3.2.6.0.56

Generated when one or more enabled CDR push receivers return to normal operation after failures were encountered on all push receivers.

apSysMgmtCfgSaveFailTrap: 1.3.6.1.4.1.9148.3.2.6.0.13

Generated if an error occurs while the system is trying to save the configuration to memory.

apSysMgmtCollectorPushSuccessTrap: 1.3.6.1.4.1.9148.3.2.6.0.44

Generated when the collector successfully completes a push operation. apSysMgmtENUMStatusChangeTrap:

1.3.6.1.4.1.9148.3.2.6.0.27

Generated if the reachability status of an ENUM server changes; contains: • apENUMConfigName

• apENUMServerIpAddress • apENUMServerStatus apSysMgmtExpDOSTrap:

1.3.6.1.4.1.9148.3.2.8.0.2

Generated when a device exceeds configured thresholds and is denied access by the Net-Net SBC.

apSysMgmtFanTrap: 1.3.6.1.4.1.9148.3.2.6.0.3

Generated if a fan unit speed falls below the monitoring level. apSysMgmtGatewaySynchronizedTrap:

1.3.6.1.4.1.9148.3.2.6.0.49

Generated when the default gateway is synchronized in the ARP table. apSysMgmtGatewayUnreachableTrap:

1.3.6.1.4.1.9148.3.2.6.0.10

Generated if the gateway specified becomes unreachable by the system. apSysMgmtGatewayUnreachableClear:

1.3.6.1.4.1.9148.3.2.6.0.21

Generated when the Net-Net determines that the gateway in question is once again reachable.

apSysMgmtGroupTrap: 1.3.6.1.4.1.9148.3.2.3.0.1

Generated when a significant threshold for a Net-Net system resource use or health score is exceeded. For example, if Network Address Translation (NAT) table usage, Address Resolution Protocol (ARP) table usage, memory usage, or Central Processing Unit (CPU) usage reaches 90% or greater of its capacity, the

(22)

ACME PACKET MIBS

apSysMgmtGroupClearTrap: 1.3.6.1.4.1.9148.3.2.3.0.2

Generated when the Net-Net SBC’s system resource use or its health score returns to levels that are within thresholds. For example, NAT table usage or memory usage could return to acceptable levels, and the systems health score could return to a level above 60.

apSysMgmtH323InitFailTrap: 1.3.6.1.4.1.9148.3.2.6.0.12

Generated if an H.323 stack has failed to initialize properly and has been terminated.

apSysMgmtHardwareErrorTrap: 1.3.6.1.4.1.9148.3.2.6.0.14

Provides a text string indicating the type of hardware error that has occurred. If the message text exceeds 255 bytes, the message is truncated to 255 bytes.

apSysMgmtInetAddrWithReasonDOSTrap: 1.3.6.1.4.1.9148.3.2.8.0.4

Generated when an IP address is placed on a deny list because of denial-of-service attempts. It provides the IP address that has been demoted, the realm ID of that IP address (if available), the URI portion of the SIP From header for the message that caused the demotion, and the reason for the demotion.

apSysMgmtInterfaceStatusChangeTrap: 1.3.6.1.4.1.9148.3.2.6.0.26

Generated when there is a change in the status of the SIP interface; either the SIP interface is in service or constraints have been exceeded.

• apSysMgmtSipInterfaceRealmName—Realm identifier for the SIP interface (OID 1.3.6.1.4.1.9148.3.2.5.24)

• apSysMgmtSipInterfaceIP—IP address of the first SIP port in the SIP interface (OID 1.3.6.1.4.1.9148.3.2.5.25)

• apSysMgmtSipInterfaceStatus—Code is 0 (OID 1.3.6.1.4.1.9148.3.2.5.26) • apSysMgmtSipInterfaceStatusReason—Status reasons and in-service (3) and

constraintExceeded (4) (OID 1.3.6.1.4.1.9148.3.2.5.27) apSysMgmtLDAPStatusChangeTrap:

1.3.6.1.4.1.9148.3.2.6.0.42

Generated if the status of whether a LDAP server is reachable changes. apSysMgmtMediaBandwidthTrap:

1.3.6.1.4.1.9148.3.2.6.0.7

Generated if bandwidth allocation fails at a percentage higher or equal to the system’s default threshold rate.

Bandwidth allocation failure rates are checked every 30 seconds. The trap is sent when the failure rate is at 50% or higher. After that time, the trap is sent every 30 seconds until the failure rate drops below 35%. The clear trap is sent once the failure rate drops below 5%.

apSysMgmtMediaBandwidthClearTrap: 1.3.6.1.4.1.9148.3.2.6.0.19

Generated when the percentage rate of failure for media bandwidth allocation decreases to the default allowable threshold.

apSysMgmtMediaOutofMemory: 1.3.6.1.4.1.9148.3.2.6.0.8

Generated if the media process cannot allocate memory. apSysMgmtMediaOutOfMemoryClearr:

1.3.6.1.4.1.9148.3.2.6.0.20

Generated when the alarm for insufficient memory for media processes is cleared manually.

apSysMgmtMediaPortsTrap: 1.3.6.1.4.1.9148.3.2.6.0.6

Generated if port allocation fails at a percentage higher or equal to the system’s default threshold rate.

Port allocation failure rates are checked every 30 seconds. The trap is sent when the failure rate is at 50% or higher. After that time, the trap is sent every 30 seconds until the failure rate drops below 35%. The clear trap is sent once the failure rate drops below 5%.

apSysMgmtMediaPortsClearTrap: 1.3.6.1.4.1.9148.3.2.6.0.18

Generated if the port allocation failure rate drops below the system’s default acceptable threshold.

apSysMgmtMediaUnknownRealm: 1.3.6.1.4.1.9148.3.2.6.0.9

Generated if the media process cannot find an associated realm for the media flow. apSysMgmtNTPClockSkewTrap:

1.3.6.1.4.1.9148.3.2.6.0.43

Generated if the NTP has to adjust the clock by more than 1000 seconds.

(23)

1.3.6.1.4.1.9148.3.2.6.0.30 _• _{apSysMgmtNTPServer—Server that is or was formerly unreachable (OID} 1.3.6.1.4.1.9148.3.2.5.31)

apSysMgmtNTPServerUnreachableClearTrap: 1.3.6.1.4.1.9148.3.2.6.0.31

Generated when an NTP server deemed unreachable subsequently becomes reachable.

apSysMgmtNTPServiceDownTrap: 1.3.6.1.4.1.9148.3.2.6.0.32

Generated if all configured NTP servers are unreachable. apSysMgmtNTPServiceDownClearTrap:

1.3.6.1.4.1.9148.3.2.6.0.33

Generated if NTP service again becomes available.

apSysMgmtPhyUtilThresholdTrap Generated when the media port’s utilization crosses a configured threshold. Indicates whether the OverloadProtection feature is active.

apSysMgmtPhyUtilThresholdClearTrap Generated when a media port’s utilization falls below the lowest configured threshold.

apSysMgmtPowerTrap: 1.3.6.1.4.1.9148.3.2.6.0.1

Generated if a power supply is powered down, powered up, inserted/present or removed/not present.

apSysMgmtPushServerUnreachableTrap: 1.3.6.1.4.1.9148.3.2.6.0.28

Generated if the system collector cannot reach a specified server; used with the historical data recording (HDR) feature.

apSysMgmtPushServerUnreachableClearTrap: 1.3.6.1.4.1.9148.3.2.6.0.29

Generated if the system collector can again reach a specified server that was unreachable; used with the historical data recording (HDR) feature.

apSysMgmtRadiusDownTrap: 1.3.6.1.4.1.9148.3.2.6.0.11

Generated if all or some configured RADIUS accounting servers have timed out from a RADIUS server.

apSysMgmtRadiusDownClearTrap: 1.3.6.1.4.1.9148.3.2.6.0.22

Generated when some or all of the previously unreachable RADIUS servers can be again be reached.

apSysMgmtRealmIcmpFailureTrap: 1.3.6.1.4.1.9148.3.2.6.0.51

Generated when ICMP heartbeat failure occurs. apSysMgmtRealmIcmpFailureClearTrap:

1.3.6.1.4.1.9148.3.2.6.0.52

Generated when ICMP heartbeat failure clears. apSysMgmtRegCacheThresholdTrap:

1.3.6.1.4.1.9148.3.2.6.0.46

Generated when the number of contacts stored in the registration cache exceeds the configured threshold.

apSysMgmtRegCacheThresholdClearTrap: 1.3.6.1.4.1.9148.3.2.6.0.47

Generated when the number of contacts stored in the registration cache falls below the configured threshold.

apSysMgmtRealmMinutesExceedTrap: 1.3.6.1.4.1.9148.3.2.6.0.40

Generated if the monthly minutes for a realm are exceeded. apSysMgmtRealmMinutesExceedClearTrap:

1.3.6.1.4.1.9148.3.2.6.0.41

Generated if monthly minutes for a realm are reset. apSysMgmtRealmStatusChangeTrap:

1.3.6.1.4.1.9148.3.2.6.0.45

Generated when there is a change in the status of the realm constraints. apSysMgmtRedundancyTrap:

1.3.6.1.4.1.9148.3.2.6.0.5

Generated if a state change occurs on either the primary or secondary system in a redundant (HA) pair.

apSysMgmtSAStatusChangeTrap: 1.3.6.1.4.1.9148.3.2.6.0.15

Generated when a session agent is declared unreachable or unresponsive for the following reasons:

• signaling timeout (H.323 and SIP)

• session agent does not respond to SIP pings (SIP only)

(24)

ACME PACKET MIBS

apSysMgmtSipRejectionTrap: 1.3.6.1.4.1.9148.3.2.10.0.1

Generated when a SIP INVITE or REGISTRATION request fail. apSysMgmtSpaceAvailThresholdTrap:

1.3.6.1.4.1.9148.3.2.6.0.68

Generated when the space available on a partition crosses a configured space threshold.

apSysMgmtSpaceAvailThresholdClearTrap: 1.3.6.1.4.1.9148.3.2.6.0.69

Generated when the space available on a partition falls below the lowest configured threshold.

apSysMgmtSurrogateRegFailed: 1.3.6.1.4.1.9148.3.2.6.0.39

Generated if a SIP user attempts to register more than the configured, allowable number of times; supports SIP surrogate registration for IMS.

• apSysMgmtSurrogateRegHost (OID 1.3.6.1.4.1.9148.3.2.5.5.35) • apSysMgmtSurrogateRegAor (OID 1.3.6.1.4.1.9148.3.2.5.5.36) apSysMgmtSystemStateTrap:

1.3.6.1.4.1.9148.3.2.6.0.17

Generated when the Net-Net SBC is instructed to change the system-state or the transition from becoming offline to online occurs. This trap contains one field called apSysMgmtSystemState, and that field has three values:

• online(0)

• becoming-offline(1) • offline(2)

apSysMgmtTaskDelete:

1.3.6.1.4.1.9148.3.2.5.24 Generated to described what task was deleted.

From Release C4.1.4 and C5.1.0 forward, this trap contains text noting that the time has been reset when the system clock time and remote clock time are too far skewed.

apSysMgmtTaskDeleteTrap:

1.3.6.1.4.1.9148.3.2.6.0.23 [Reserved for future use.]

Generated when a task is deleted; it reads apSysMgmtTaskDelete and includes the test in the trap.

apSysMgmtTaskSuspendTrap: 1.3.6.1.4.1.9148.3.2.6.0.4

Generated if a critical task running on the system enters a suspended state. apSysMgmtTempTrap:

1.3.6.1.4.1.9148.3.2.6.0.2

Generated if the temperature falls below the monitoring level. apSysMgmtAdminWriteFailTrap:

1.3.6.1.4.1.9148.3.2.6.0.62

Generated when a write to file fails. apSysMgmtAdminWriteFailClearTrap:

1.3.6.1.4.1.9148.3.2.6.0.63

Generated when a write to file succeeds. apSwCfgActivateNotification:

1.3.6.1.4.1.9148.3.4.3.0.1

Generated when an activate-config command is issued and the configuration has been changed at running time.

apSecurityOCSRDownNotification: 1.3.6.1.4.1.9148.3.9.3.3.0.1

Generated when an OSCR server becomes unreachable. apSecurityOCSRUpNotification:

1.3.6.1.4.1.9148.3.9.3.3.0.2

Generated when an OSCR server becomes available. apSysMgmtOCSRDownTrap:

1.3.6.1.4.1.9148.3.2.6.0.80

Generated if all or some of the configured OSCR accounting servers are down. apSysMgmtOCSRDownClearTrap:

1.3.6.1.4.1.9148.3.2.6.0.81

Generated if all OSCR accounting servers have resumed communications. apSecurityCRLInvalidNotification:

1.3.6.1.4.1.9148.3.9.3.4.0.1

Generated when an invalid CRL is detected.

(25)

Refer to Appendix A for examples of enterprise traps.

Net-Net EMS Traps

This section describes the Net-Net EMS traps contained in the Acme Packet EMS

MIB. Net-Net EMS generates traps when it detects the following:

• failure to discover or rediscover a Net-Net SBC configuration

• failure to save a Net-Net SBC configuration

• failure to activate a Net-Net SBC configuration

• missing components when validating a Net-Net SBC configuration

• node status change from reachable to unreachable

You need to configure an external server as the receiver for these traps.

Net-Net EMS generates the following traps:

.1.3.6.1.4.1.9148.3.13.1.2.2.0.1 apDiameterAcctSrvrDownTrap: 1.3.6.1.4.1.9148.3.13.1.2.2.0.2

Generated when a Diameter Accounting Server goes down. apAcctMsgQueueFullTrap:

1.3.6.1.4.1.9148.3.13.1.2.2.0.3

Generated when the accounting message queue is full and all accounting servers are down.

apAcctMsgQueueFullClearTrap: 1.3.6.1.4.1.9148.3.13.1.2.2.0.4

Generated when the apAcctMsgQueueFullTrap condition clears. apDiameterSrvrErrorResultTrap:

1.3.6.1.4.1.9148.3.13.1.2.2.0.5

Generated when the Diameter Server returns 3xxx (Protocol Errors), 4xxx (Transient Failures), or 5xxx (Permanent Failure) Result-Code AVP (268).

apDiameterSrvrSuccessResultTrap: 1.3.6.1.4.1.9148.3.13.1.2.2.0.6

After an error result, generated when the Diameter Server returns a 2xxx (Success) Result-Code AVP (268).

apSipSecInterfaceRegThresholdExceededTrap: 1.3.6.1.4.1.9148.3.15.2.1.2.0.1

Generated if the total number of registrations on all secondary SIP interfaces exceeds the configured threshold.

apSipSecInterfaceRegThresholdClearTrap: 1.3.6.1.4.1.9148.3.15.2.1.2.0.2

Generated if the total number of registrations on all secondary SIP interfaces falls below the configured threshold.

apEMSDiscoveryFailure Generated when Net-Net EMS fails to discover or rediscover a Net-Net SBC configuration. The trap is generated from any discovery or rediscovery failure initiated by the SOAP XML API, Net-Net EMS, or system processing. The trap contains the Net-Net SBC’s node ID, the start and end time of the discovery or rediscovery operation, and the user who initiated the operation.

(26)

Net-Net System

Alarms

A Net-Net system alarm is triggered when a condition or event happens within

either the Net-Net system hardware or software. Given a specific alarm, the Net-Net

system generates the appropriate SNMP trap. These traps include a description of

the event or condition that caused the trap to be generated; or provides information

associated with the alarm, such as the interface ID (

ifIndex

)/status or object

identifier/object type integer values.

The following table maps Net-Net system alarms to SNMP traps. This table includes

the following information:

• alarm names

• alarm IDs

• alarm severities (including threshold values)

• alarm causes

• example log messages

In addition, this table specifies the type of traps that are generated for SNMP and the

trap reference locations (the supported MIB or RFC).

apEMSActivateFailure Generated when Net-Net EMS fails to activate a configuration, whether initiated from the SOAP XML API or Net-Net EMS GUI for the save/activate or activate operations.

apEMSInvalidConfigDiscoveredNotification Generated when Net-Net EMS validates a discovered Net-Net SBC’s configuration (for example confirms each referenced realm is configured) and detects missing components. The trap contains the time and the Net-Net SBC node ID.

apEMSNodeUnreachableNotification Generated when a node’s status changes from reachable to unreachable. The trap contains the Net-Net SBC’s node ID and the time of the event. apEMSNodeUnreachableClearNotification Generated when a node’s status changes from

unreachable to reachable. The trap contains the Net-Net SBC’s node ID and the time of the event.

(27)

Hardware Alarms

FAN STOPPED 65537 CRITICAL: any fan speed is <50%. Or speed of two or more fans is >50% and <75%. MAJOR: speed of two or more fans is > 75% and < 90%. Or speed of one fan is >50% and <75% and the other two fans are at normal speed. MINOR: speed of one fan> 75% and <90%, the other two fans are at normal speed.

Fan speed failure. NOTE: If this alarm occurs, the Net-Net system turns up the fan speed to the fastest possible speed. fan speed: XXXX, XXXX, XXXX (where xxxx xxxx xxxx is the revolutions per minute (RPM) of each fan on the fan module) apSyslogMessageGenerated (ap-slog.mib) apEnvMonStatusChangeNotificati on (ap-env-monitor.mib) apSysMgmtFanTrap (ap-smgmt.mib) TEMPERATURE HIGH 65538 SD1: CRITICAL: >70°C MAJOR: >60°C MINOR: >50°C SD2: CRITICAL: >75°C MAJOR: >65°C MINOR: >55°C SD3: CRITICAL: >105°C MAJOR: >95°C MINOR: >85°C Fans are obstructed or stopped. The room is abnormally hot. Temperature: XX.XX C (where XX.XX is the temperature in degrees) apSyslogMessageGenerated (ap-slog.mib) apEnvMonStatusChangeNotificati on (ap-env-monitor.mib) apSysMgmtTempTrap (ap-smgmt.mib) ENVIRONMENTAL SENSOR FAILURE

65539 CRITICAL The environmental sensor component cannot detect fan speed and temperature.

Hardware monitor failure! Unable to monitor fan speed and temperature!

apSyslogMessageGenerated (ap-slog.mib)

apEnvMonI2CFailNotification (ap-env-monitor.mib) PLD POWER A FAILURE 65540 MINOR Power supply A has

failed.

(28)

PLD POWER A UP 65541 MINOR Power supply A is now present and functioning.

Back Power Supply A is present! apSyslogMessageGenerated (ap-slog.mib) apEnvMonStatusChangeNotificati on (ap-env-monitor.mib) apSysMgmtPowerTrap (ap-smgmt.mib)

NOTE: If the Net-Net system boots up with one power supply, the health score is 100, and an alarm is not generated. If another power supply is then added to that same Net-Net system, this alarm is generated, but the health score is not decremented.

PLD POWER B FAILURE 65542 MINOR Power supply B has failed.

Back Power Supply B has failed! apSyslogMessageGenerated (ap-slog.mib) apEnvMonStatusChangeNotificati on (ap-env-monitor.mib) apSysMgmtPowerTrap (ap-smgmt.mib) PLD POWER B UP 65543 MINOR Power supply B is

now present and functioning.

Back Power Supply B is present! apSyslogMessageGenerated (ap-slog.mib) apEnvMonStatusChangeNotificati on (ap-env-monitor.mib) apSysMgmtPowerTrap (ap-smgmt.mib)

NOTE: If the Net-Net system boots up with one power supply, the health score is 100, and an alarm is not generated. If another power supply is then added to that same Net-Net system, this alarm is generated, but the health score is not decremented.

(29)

or >1.8v MINOR: 1.4v to 1.55v or 1.65v to 1.8v Host Processor 7457 Version 1.0 CRITICAL: <1.0v or >1.6v MINOR: 1.00v to 1.35v or 1.45v to 1.6v Version 1.1 and later CRITICAL: <1.0v or >1.6v MINOR: 1.00v to 1.25v or 1.35v to 1.6v on (ap-env-monitor.mib)

PLD VOLTAGE ALARM 5V 65546 Host Processor 7455 CRITICAL: <1.4v or >1.8v MINOR: 1.4v to 1.55v or 1.65v to 1.8v Host Processor 7457 Version 1.0 CRITICAL: <1.0v or >1.6v MINOR: 1.00v to 1.35v or 1.45v to 1.6v Version 1.1 and later CRITICAL: <1.0v or >1.6v MINOR: 1.00v to 1.25v or 1.35v to 1.6v apSyslogMessageGenerated (ap-slog.mib) apEnvMonStatusChangeNotificati on (ap-env-monitor.mib) PLD VOLTAGE ALARM CPU 65547 Host Processor 7455 Host Processor 7457 apSyslogMessageGenerated (ap-slog.mib) apEnvMonStatusChangeNotificati on (ap-env-monitor.mib) PHY0 Removed 65550 MAJOR Physical interface

(30)

PHY0 Inserted 65552 MAJOR Physical interface card 0 was inserted. apSyslogMessageGenerated (ap-slog.mib) apEnvMonStatusChangeNotificati on (ap-env-monitor.mib) PHY1 Removed 65553 MAJOR Physical interface

card 1 was removed. apSyslogMessageGenerated (ap-slog.mib) apEnvMonStatusChangeNotificati on (ap-env-monitor.mib) PHY1 Inserted 65554 MAJOR Physical interface

card 1 was inserted. apSyslogMessageGenerated (ap-slog.mib) apEnvMonStatusChangeNotificati on (ap-env-monitor.mib) System Alarms LINK UP ALARM GIGPORT

131073 MINOR Gigabit Ethernet interface 1 goes up.

Slot 0 port 0 UP linkUp (IETF RFC 2233) LINK UP ALARM

GIGPORT

131074 MINOR Gigabit Ethernet interface 2 goes up.

Slot 1 port 0 UP linkUp(IETF RFC 2233) LINK DOWN ALARM

GIGPORT

131075 MAJOR Gigabit Ethernet interface 1 goes down.

Slot 0 port 0 DOWN linkDown (IETF RFC 2233)

LINK DOWN ALARM GIGPORT

131076 MAJOR Gigabit Ethernet interface 2 goes down.

LINK UP ALARM VXINTF 131077 MINOR Control interface 0 goes up.

wancom0 UP linkUp (IETF RFC 2233) LINK UP ALARM VXINTF 131078 MINOR Control interface 1

goes up.

wancom1 UP linkUp (IETF RFC 2233) LINK UP ALARM VXINTF 131079 MINOR Control interface 2

goes up.

wancom2 UP linkUp (IETF RFC 2233) LINK DOWN ALARM

VXINTF

131080 MAJOR Control interface 0 goes down.

wancom0 DOWN linkDown (IETF RFC 2233) LINK DOWN ALARM

VXINTF

wancom1 DOWN linkDown (IETF RFC 2233) LINK DOWN ALARM

VXINTF

wancom2 DOWN linkDown (IETF RFC 2233) LINK UP ALARM FEPORT 131083 MAJOR Fast Ethernet slot

0, port 0 goes up.

Slot 0 port 0 UP linkUp (IETF RFC 2233) LINK UP ALARM FEPORT 131084 MAJOR Fast Ethernet slot

1, port 0 goes up.

Slot 1 port 0 UP linkUp (IETF RFC 2233) LINK UP ALARM FEPORT 131085 MINOR Fast Ethernet slot

0, port 1 goes up.

1, port 1 up.

(31)

LINK UP ALARM FEPORT 131087 MINOR Fast Ethernet slot 0, port 2 goes up.

1, port 2 goes up.

0, port 3 goes up.

1, port 3 goes up.

Slot 1 port 3 UP linkUp (IETF RFC 2233) LINK DOWN ALARM

FEPORT

131091 MAJOR Fast Ethernet slot 0, port 0 goes down.

LINK DOWN ALARM FEPORT

CPU UTILIZATION 131099 MINOR CPU usage reached 90% or greater of its capacity.

CPU usage X% over threshold X%

apSysMgmtGroupTrap (ap-smgmt.mib) MEMORY UTILIZATION 131100 CRITICAL Memory usage

reached 90% or greater of its capacity. Memory usage X% over threshold X% apSysMgmtGroupTrap (ap-smgmt.mib)

HEALTH SCORE 131101 MAJOR Net-Net system’s health score fell below 60. Health score X is under threshold (where X is the health score) apSysMgmtGroupTrap (ap-smgmt.mib)

NAT TABLE UTILIZATION 131102 MINOR NAT table usage reached 90% or greater of its capacity.

NAT table usage X% over threshold X%

(32)

ACME PACKET MIBS

ARP TABLE UTILIZATION 131103 MINOR ARP table usage reached 90% or greater of its capacity.

ARP table X% over threshold X%

apSysMgmtGroupTrap (ap-smgmt.mib)

REDUNDANT SWITCH-TO-ACTIVE

131104 CRITICAL A state transition occurred from Standby/Becoming Standby to BecomingActive. Switchover, <state to state>, active peer <name of HA peer> has timed out

or Switchover,

<state to state>, active peer <name of HA peer> has unacceptable health (x) (where x is the health score) or Switchover, <state to state>, forced by command apSyslogMessageGenerated (ap-slog.mib) apSysMgmtRedundancyTrap (ap-smgmt.mib) REDUNDANT SWITCH-TO-STANDBY

131105 CRITICAL A state transition occurred from Active/BecomingAc tive to BecomingStandby/ RelinquishingActive . Switchover, <state to state>, peer <name of HA peer> is healthier (x) than us (x) (where x is the health score) or Switchover, <state to state>, forced by command apSyslogMessageGenerated (ap-slog.mib) apSysMgmtRedundancyTrap (ap-smgmt.mib)

REDUNDANT TIMEOUT 131106 MAJOR An HA Net-Net system peer was not heard from within the configured silence window.

Peer <name of HA peer> timed out in state x, my state is x (where x is the state (e.g., BecomingStandby)) apSyslogMessageGenerated (ap-slog.mib) apSysMgmtRedundancyTrap (ap-smgmt.mib)

(33)

REDUNDANT OUT OF SERVICE

131107 CRITICAL Unable to synchronize with Active HA Net-Net system peer within BecomingStandby timeout. Unable to synchronize with Active redundant peer within BecomingStandby timeout, going OutOfService or activate-config failed, process busy or activate-config failed, must do save-config before activating. or activate-config failed, could not get current config version from file or

activate-config failed, could not set running config version to file. apSyslogMessageGenerated (ap-slog.mib) apSysMgmtRedundancyTrap (ap-smgmt.mib)

The activate-config failed log message appears for those cases in which the execution of the activate config command failed on the standby Net-Net SBC.

SYSTEM TASK SUSPENDED

131108 CRITICAL A Net-Net system task (process) suspends or fails. Task X suspended, which decremented health by 75! (where X is the task/process name) apSyslogMessageGenerated (ap-slog.mib) apSysMgmtTaskSuspendTrap (ap-smgmt.mib) Media Alarms MBCD ALARM OUT OF MEMORY 262145 CRITICAL: for flow MAJOR: for media (if server cannot allocate a new context)

No further memory can be allocated for MBCD.

Flow: Cannot create free port list for realm.

Media Server: Failed to allocate new context. apSyslogMessageGenerated (ap-slog.mib) apSysMgmtMediaOutofMemory (ap-smgmt.mib) MBCD ALARM UNKNOWN REALM 262147 MAJOR: if media server is adding a new flow Media server is unable to find realm interface.

Realm type (ingress, egress, hairpin) X, not found apSyslogMessageGenerated (ap-slog.mib) apSysMgmtUnknownRealm (ap-smgmt.mib) MBCD ALARM OUT OF BANDWIDTH 262149 CRITICAL: failure rate = 100% MAJOR: failure rate > or = 50%

The realm is out of bandwidth.

Out of bandwidth apSyslogMessageGenerated (ap-slog.mib) apSysMgmtMediaBandwidthTrap (ap-smgmt.mib) MBCD ALARM OUT OF PORTS 262150 CRITICAL: failure rate = 100% MAJOR: failure rate > or = 50%

The realm is out of steering ports.

Out of steering ports apSyslogMessageGenerated (ap-slog.mib)

apSysMgmtMediaPortsTrap (ap-smgmt.mib)

(34)

ACME PACKET MIBS

GATEWAY UNREACHABLE

dynamic ID

MAJOR The Net-Net SBC lost ARP connectivity to a front interface gateway. gateway X.X.X.X unreachable on slot Y port Z subport ZZ (where X.X.X.X is the IPv4 address of the front interface gateway, Y is the front interface slot number, Z is the front interface port number, and ZZ is the subport ID)

apSysMgmtGatewayUnreachableT rap

(ap_smgmt.mib)

NOTE: The value of this alarm ID is dynamic. That is, it changes based on a numbers of factors, but the total alarm ID range falls between 196608 and 262143. The alarm ID is calculated based on the compilation of the following information: a hexidecimal number that represents the VLAN ID and the front interface port/slot numbers.

(35)

Application Alarms RADIUS ACCOUNTING CONNECTION DOWN 327681 CRITICAL: if all enabled and configured Remote Authentication Dial-in User Service (RADIUS) accounting server connections have timed-out without response from the RADIUS server

MAJOR: if some, but not all configured RADIUS accounting server connections have timed-out without response from the RADIUS server. The enabled connections to RADIUS servers have timed-out without a response from the RADIUS server.

CRITICAL: All enabled accounting connections have been lost! Check accounting status for more details. MAJOR: One or more enabled accounting connections have been lost! Check accounting status for more details.

apSyslogMessageGenerated (ap-slog.mib)

apSysMgmtRadiusDownTrap (ap-smgmt.mib)

ENUM SERVER STATUS New to Release C5.0 XX CRITICAL: All ENUM servers are unreachable MAJOR: Some ENUM servers are unreachable The enabled connections to ENUM servers have been lost.

CRITICAL: All ENUM Servers are currently unreachable! MAJOR: One or more ENUM Servers are currently unreachable! apSysMgmtENUMStatusChangeTr ap (ap-smgmt.mib) H.323 ALARM STACK INITIALIZATION FAILURE

(36)

ACME PACKET MIBS

For additional information about system alarms for the components of the Net-Net

system, refer to the Alarms section of the Monitoring via the ACLI chapter of the

Net-Net Administration and Configuration Guide for the ACLI.

Configuration Alarms CFG ALARM SAVE FAILED

393217 MAJOR The save-config command execution failed on a standby Net-Net SBC peer operating as part of an HA pair. save-config failed on targetName!/code

full, config sync stopped!

or save-config failed on

targetName!/code

full, config sync stopped! (where the targetName is the target name (tn) configured in the boot parameters) apSyslogMessageGenerated (ap-slog.mib) apSysMgmtCfgSaveFailTrap (ap-smgmt.mib) License Alarm LICENSE APPROACH CAPACITY

Oracle Communications Session Border Controller

Formerly Net-Net Session Director

About this Guide . . . vii

Introduction . . . vii

Supported Platforms . . . vii

Related Documentation . . . vii

About the Net-Net MIB Reference Guide . . . viii

Documented Objects and Traps. . . viii

Acme Packet Platform sysObjectIDs . . . ix

Revision History . . . ix

Acme Packet MIBs . . . 11

Overview . . . 11

About MIBs . . . 11

About Managed Objects . . . 13

About SNMP Traps . . . 13

SNMPv3 Secure Traps . . . 13

Authentication and Privacy . . . 14

Enabling SNMPv3 . . . 14

Consideration for HA Nodes . . . 15

ACLI Instructions and Examples . . . 15

MIBs Supported by Acme Packet . . . 17

About Traps . . . 19

Standard Traps. . . 19

Enterprise Traps. . . 20

Net-Net EMS Traps . . . 25

Net-Net System Alarms . . . 26

Alarm Clearing . . . 37

Acme Packet Log Levels and syslog Level Severities . . . 38

Acme Packet Log Levels . . . 38

syslog Level Severities. . . 39

Mapping Trap Filter Levels to syslog and Alarm Severities. . . 39

Standard SNMP GET Requests . . . 41

Introduction . . . 41

Interface Scalar Example . . . .43

Interface Table Examples . . . .43

ifName Support (RFC 2863) . . . .44

Examples of ifIndex Values . . . .44

High Capacity MIB Counters (ifXtable Support) . . . .45

IP Group . . . .48

IP Scalar Example . . . .50

IP Address Table Example . . . .51

ICMP Group . . . .52

ICMP Scalar Example. . . .53

TCP Group . . . .54

TCP Scalar Example . . . .56

TCP Connection Table Example . . . .56

UDP Group . . . .57

UDP Scalar Example . . . .57

UDP Table Example . . . .58

System Group . . . .58

System Scalar Example. . . .59

Object Resource Information. . . .60

SNMP Group . . . .61

SNMP Scalar Example . . . .62

Physical Entity Table (rfc2737.mib). . . .63

entPhysicalTable Example . . . .67

entity Physical Table Scalar Example . . . .68

Enterprise SNMP GET Requests . . . .69

Introduction . . . .69

Acme Packet syslog MIB (ap-slog.mib) . . . .69

Syslog Scalar Example . . . .71

Syslog History Table Examples . . . .71

Acme Packet System Management MIB (ap-smgmt.mib) . . . .72

System Management Scalar Examples . . . .83

Session Statistical Group Table Examples . . . .84

SIP Session Agent Statistics Table Example. . . .85

H.323 Session Agent Statistics Table Example . . . .85

Signaling Realm Statistics Table Example . . . .86

Notes on ENUM Server Names . . . .87

Acme Packet License MIB (ap-license.mib). . . .88

Acme Packet Environment Monitor MIB (ap-env-monitor.mib) . . . 92

I2C State Scalar Examples . . . 96

Voltage Status Table Examples. . . 96

Temperature Status Table Examples . . . 96

Fan Status Table Examples . . . 97

Power Supply Status Table Examples . . . 97

Acme Packet H.323 MIB (ap-h323.mib) . . . 97

Acme Packet Security MIB (ap-security.mib) . . . 97

Acme Packet Diameter MIB (ap-diameter.mib). . . 98

Acme Packet SIP MIB (ap-sip.mib) . . . 99