0% found this document useful (0 votes)

141 views191 pages

Mib Guide

Uploaded by

arabe.codz

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

141 views191 pages

Mib Guide

Uploaded by

arabe.codz

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

Oracle® Communications Session

Border Controller
MIB Guide

Release S-Cz9.1.0
F51861-09
October 2024
Oracle Communications Session Border Controller MIB Guide, Release S-Cz9.1.0

F51861-09

Copyright © 2022, 2024, Oracle and/or its affiliates.

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, software documentation, data (as defined in the Federal Acquisition Regulation), or related
documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then
the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any
programs embedded, installed, or activated on delivered hardware, and modifications of such programs) and Oracle
computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial
computer software," "commercial computer software documentation," or "limited rights data" pursuant to the applicable
Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, reproduction,
duplication, release, display, disclosure, modification, preparation of derivative works, and/or adaptation of i) Oracle
programs (including any operating system, integrated software, any programs embedded, installed, or activated on
delivered hardware, and modifications of such programs), ii) Oracle computer documentation and/or iii) other Oracle
data, is subject to the rights and limitations specified in the license contained in the applicable contract. The terms
governing the U.S. Government's use of Oracle cloud services are defined by the applicable contract for such services.
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®, Java, MySQL, and NetSuite are registered trademarks of Oracle and/or its affiliates. Other names may be
trademarks of their respective owners.

Intel and Intel Inside 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, Epyc, and the AMD logo
are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open
Group.

This software or hardware and documentation may provide access to or information about content, products, and
services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all
warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an
applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss,
costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth
in an applicable agreement between you and Oracle.
Contents
About this Guide
My Oracle Support viii

Revision History

1 SNMP Configuration
Overview 1-1
Basic SNMP Parameters 1-1
SNMPv1v2 Community Configuration 1-2
SNMPv1v2 Trap Receiver Configuration 1-2
SNMP IPv6 Support 1-2
SNMP Configuration Overview 1-2
Configure SNMP System and Agent Parameters 1-2
SNMPv3 1-3
SNMPv3 Users 1-4
Configure an SNMPv3 User Identity 1-4
SNMPv3 User Groups 1-5
Configure SNMPv3 User Group 1-5
SNMPv3 Manager Access 1-7
Configure SNMPv3 Manager Access 1-7
SNMPv3 Views 1-8
Specify SNMPv3 View Access to a MIB 1-8
SNMPv1 and SNMPv2 1-9
SNMPv1v2 Community Configuration 1-9
Configure the SNMP Community 1-9
SNMPv1v2 Trap Receiver Configuration 1-10
Configure Trap Receivers 1-10
Specify an NMS for EMS Generated Traps 1-11
Enabling Administrative Trap Types 1-12
Enabling Media Supervision Traps 1-13
View SNMP Address, Statistics and User Information 1-13

iii
Consideration for HA Nodes 1-15

2 Introduction to MIBs and Traps

About MIBs 2-1
Object Identifiers and Instance IDs 2-1
MIB Tree Structure 2-2
Managed Objects 2-4
Scalar MIB Objects 2-4
Table MIB Objects 2-4
SNMP Traps 2-4
MIBs Supported 2-4
Standard MIBS 2-4
Enterprise MIBs 2-5
Traps 2-6
Standard Traps 2-6
Enterprise Traps 2-7
apSyslog Traps ([Link]) 2-7
apSysMgmt Traps ([Link]) 2-7
apSwinventory Traps ([Link]) 2-17
apEnvMon Traps ([Link]) 2-17
apLicense Traps ([Link]) 2-17
apSecurity Traps ([Link]) 2-18
apSLB Traps ([Link]) 2-21
apH323 Traps ([Link]) 2-21
apDiameter Traps ([Link]) 2-22
apDnsAlg Traps ([Link]) 2-22
apSip Traps ([Link]) 2-22
apApps Traps ([Link]) 2-23
apAclDropOverThresholdTrap Objects 2-24
apUSBC Traps ([Link]) 2-24
Specify an NMS for EMS Generated Traps 2-24
Persistent indexing of SNMP Tables 2-25
Log Levels and syslog Level Severities 2-26
Log Levels 2-26
syslog Level Severities 2-27
Mapping Trap Filter Levels to syslog and Alarm Severities 2-27
Platform sysObjectIDs 2-28

3 Standard SNMP GET Requests

Interfaces Object 3-1

iv
Interface Table 3-1
Interface Description in MIB 3-4
ifXTable Table 3-6
ip Object 3-10
ipAddrTable Table 3-13
icmp Object 3-14
TCP Object 3-15
tcpConnTable Table 3-17
UDP Object 3-17
System Object 3-18
Object Resource Information Object 3-20
SNMP Object 3-20
Physical Entity Table 3-21

4 Enterprise SNMP GET Requests

Applications MIB ([Link]) 4-1
apAppsENUMServerStatusTable Table 4-1
apAppsDnsServerStatusTable 4-1
apAppsStirMIBObjects Table 4-2
apAppsStirServerTable 4-3
apAppsStirServerStatsTable 4-3
apAppsStirAgentStatsTable 4-6
apAppsStirSipInterfaceStatsTable 4-9
apAppsStirRealmStatsTable 4-12
apAppsStirSystemStatsTable 4-15
apDosThresholdCountersGroup 4-17
MSRP MIB Objects 4-18
Codec and Transcoding MIB ([Link]) 4-35
apCodecPairStatsTable 4-38
Transcoding Capacity in System Management MIB ([Link]) 4-38
Diameter MIB ([Link]) 4-39
DNS ALG MIB ([Link]) 4-40
apDNSALGServerStatusTable 4-40
apDNSALGStatsTable 4-41
Environment Monitor MIB ([Link]) 4-42
H.323 MIB ([Link]) 4-46
License MIB ([Link]) 4-46
Security MIB ([Link]) 4-48
apSecurityCertificateTable 4-49
SIP MIB ([Link]) 4-49
syslog MIB ([Link]) 4-57

v
System Management MIB ([Link]) 4-59
Notes on ENUM Server Names 4-79
Software Inventory MIB ([Link]) 4-80
Multicore Monitoring MIB ([Link]) 4-81
apUsbcSysDPDKObjects 4-84
apUsbcSysScalingObjects 4-84

5 SNMP-based Application Features

SNMP Reporting of Message Rate Statistics 5-1
apSIPRateIntfStatsTable 5-1
apSIPRateAgentStatsTable 5-1
apDnsAlgServerRateStatsTable 5-2
apEnumServerRateStatsTable 5-2
SNMP Reporting of Message Data Counters 5-2
Call Duration Counters for SNMP Retrieval 5-2
Local and Remote Call Termination (BYE) Counters for SNMP Retrieval 5-2
SIP Method Counters for SNMP Retrieval 5-3
SRVCC Objects for SNMP Retrieval 5-3
Rx Policy Server Objects for SNMP Retrieval 5-3
IKE Session Agent Objects for SNMP Retrieval 5-3
IMS-AKA Session Agent Objects for SNMP Retrieval 5-3
SRTP Session Agent Objects for SNMP Retrieval 5-4
Transcoding Load Objects for SNMP Retrieval 5-4
FQDN-resolved Session Agent Statistics SNMP Retrieval 5-5
CAC Utilization Statistics via SNMP 5-6
SNMP Get for CAC Utilization 5-6
CAC Utilization Traps 5-8
External Policy Server Connection Status Reporting 5-9

A System Alarms
Alarm Severities A-11

vi
About this Guide

The Oracle Communications Session Border Controller MIB Reference 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
• 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.

Documentation Set
The following table describes the documentation set for this release.

Document Name Document Description

Acme Packet 3900 Hardware Installation Contains information about the components and
Guide installation of the Acme Packet 3900.
Acme Packet 4600 Hardware Installation Contains information about the components and
Guide installation of the Acme Packet 4600.
Acme Packet 4900 Hardware Installation Contains information about the components and
Guide installation of the Acme Packet 3950 and Acme Packet
4900.
Acme Packet 6100 Hardware Installation Contains information about the components and
Guide installation of the Acme Packet 6100.
Acme Packet 6300 Hardware Installation Contains information about the components and
Guide installation of the Acme Packet 6300.
Acme Packet 6350 Hardware Installation Contains information about the components and
Guide installation of the Acme Packet 6350.
Release Notes Contains information about the current documentation set
release, including new features and management
changes.
Known Issues & Caveats Contains known issues and caveats
Configuration Guide Contains information about the administration and
software configuration of the Service Provider Session
Border Controller (SBC).

vii
About this Guide

Document Name Document Description

ACLI Reference Guide Contains explanations of how to use the ACLI, as an
alphabetical listings and descriptions of all ACLI
commands and configuration parameters.
Maintenance and Troubleshooting Guide Contains information about SBC logs, performance
announcements, system management, inventory
management, upgrades, working with configurations, and
managing backups and archives.
MIB Guide Contains information about Management Information Base
(MIBs), Oracle Communication'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),
examples of scalar and table objects.
Accounting Guide Contains information about the SBC’s accounting support,
including details about RADIUS and Diameter accounting.
HDR Guide Contains information about the SBC’s Historical Data
Recording (HDR) feature. This guide includes HDR
configuration and system-wide statistical information.
Admin Security Guide Contains information about the SBC’s support for its
Administrative Security license.
Security Guide Contains information about security considerations and
best practices from a network and application security
perspective for the SBC family of products.
Platform Preparation and Installation Guide Contains information about upgrading system images and
any pre-boot system provisioning.
Call Traffic Monitoring Guide Contains information about traffic monitoring and packet
traces as collected on the system. This guide also includes
WebGUI configuration used for the SIP Monitor and Trace
application.
HMR Guide Contains information about configuring and using Header
Manipulation Rules to manage service traffic.
REST API Contains information about the supported REST APIs and
how to use the REST API interface.

Documentation Accessibility
For information about Oracle's commitment to accessibility, visit the Oracle Accessibility
Program website at [Link]

My Oracle Support
My Oracle Support ([Link] is your initial point of contact for all product
support and training needs. A representative at Customer Access Support (CAS) can assist
you with My Oracle Support registration.
Call the CAS main number at 1-800-223-1711 (toll-free in the US), or call the Oracle Support
hotline for your local country from the list at [Link]
[Link]. When calling, make the selections in the sequence shown below on the Support
telephone menu:
1. Select 2 for New Service Request.
2. Select 3 for Hardware, Networking, and Solaris Operating System Support.

viii
About this Guide

3. Select one of the following options:

• For technical issues such as creating a new Service Request (SR), select 1.
• For non-technical issues such as registration or assistance with My Oracle Support,
select 2.

You are connected to a live agent who can assist you with My Oracle Support registration and
opening a support ticket.
My Oracle Support is available 24 hours a day, 7 days a week, 365 days a year.

Emergency Response
In the event of a critical service situation, emergency response is offered by the Customer
Access Support (CAS) main number at 1-800-223-1711 (toll-free in the US), or call the Oracle
Support hotline for your local country from the list at [Link]
[Link]. The emergency response provides immediate coverage, automatic escalation, and
other features to ensure that the critical situation is resolved as rapidly as possible.
A critical situation is defined as a problem with the installed equipment that severely affects
service, traffic, or maintenance capabilities, and requires immediate corrective action. Critical
situations affect service and/or system operation resulting in one or several of these situations:
• A total system failure that results in loss of all transaction processing capability
• Significant reduction in system capacity or traffic handling capability
• Loss of the system's ability to perform automatic system reconfiguration
• Inability to restart a processor or the system
• Corruption of system databases that requires service affecting corrective actions
• Loss of access for maintenance or recovery operations
• Loss of the system ability to provide any required critical or major trouble notification
Any other problem severely affecting service, capacity/traffic, billing, and maintenance
capabilities may be defined as critical by prior discussion and agreement with Oracle.

Locate Product Documentation on the Oracle Help Center Site

Oracle Communications customer documentation is available on the web at the Oracle Help
Center (OHC) site, [Link] You do not have to register to access these
documents. Viewing these files requires Adobe Acrobat Reader, which can be downloaded at
[Link]
1. Access the Oracle Help Center site at [Link]
2. Click Industries.
3. Under the Oracle Communications sub-header, click the Oracle Communications
documentation link.
The Communications Documentation page appears. Most products covered by these
documentation sets appear under the headings "Network Session Delivery and Control
Infrastructure" or "Platforms."
4. Click on your Product and then Release Number.
A list of the entire documentation set for the selected product and release appears.
5. To download a file to your location, right-click the PDF link, select Save target as (or
similar command based on your browser), and save to a local folder.

ix
About this Guide

Access to Oracle Support

Oracle customers that have purchased support have access to electronic support through My
Oracle Support. For information, visit [Link]
or visit [Link] if you are hearing impaired.

x
Revision History
The following table provides the revision history for this document.

Date Description
March 2022 • Initial release.
May 2022 • Updates apSysMgmt Traps ([Link]) in
the Enterprise Traps section.
August 2022 • Adds MSRP MIBs for S-Cz9.1.0p2
February 2023 • Updates temperatures alarms for
3900/3950/4900.
• Added missing Enterprise Traps.
May 2023 • Clarifies the admin write fail and succeed
traps.
• Adds apSwinventory Traps topic.
• Adds values for apEnvMonPhyCardState.
September 2023 • Extends upon the FQDN session-agent
statistics function.
November 2023 • Adds STIR/SHAKEN traps to ap-Apps Traps.
August 2024 • Fix MIB table for apAppsStirServerTable
October 2024 • Adds OID numbers for CAC utilization traps.
• Corrects three apSigRealmStats statistics
descriptions.
• Removes erroneous references to the
deprecated TSCF feature.

xi
1
SNMP Configuration
The Simple Network Management Protocol (SNMP) allows you to monitor system and health
conditions for an Oracle Communications Session Border Controller (SBC) through an external
network management (northbound) system, such as the Oracle Communications Session
Delivery Manager or an SNMP manager. The system supports SNMPv3, v2 or v1 to interface
with a range of external NMS systems.

Note:
SNMP configuration is not required for the service operation of the SBC, but is
performed on the majority of systems. Most network administrators are familiar with,
or become familiar with SNMP.

Overview
SNMP is comprised of three groups of settings on a Oracle Communications Session Border
Controller (SBC). These settings includes:
• System-wide configuration
• Access Configuration, including:
– SNMPv1v2 Community Settings
– SNMP IPv3 Authentication, Encryption and Filter Settings
• Trap Receiver Configuration
You can configure an SNMP manager to query the SBC or be a trap receiver. You can
configure an SNMP manager to perform both functions by configuring two snmp-address-
entry elements that have the same IP address, but different names.

Basic SNMP Parameters

The Oracle Communications Session Border Controller (SBC) includes several parameters
that control basic SNMP functionality and are common to both SNMPv1v2 and SNMPv3
deployments. The MIB-related elements are for informational purposes, and are helpful if set.
The remainder of the parameters determine if certain SBC events are reported to the SNMP
system.
System-wide configurations including:
• Enable SNMP operation (enabled by default)
• System-related contact information
• Enable the SBC to send information within traps, including:
– syslog
– authentication

1-1
Chapter 1
SNMP Configuration Overview

– environmental
– system monitoring

SNMPv1v2 Community Configuration

SNMPv1v2 community configuration consists of setting a community name, an access mode
and IP addresses of the servers. Configurations accept multiple addresses. You can provide
both READ and WRITE mode to a single manager by creating two objects with different names
and access modes, but the same IP address.
Determine your planned name, address type (IPv4 vs IPv6) and modes before starting.

SNMPv1v2 Trap Receiver Configuration

Determine the community, addressing (IPv4 or IPv6) and filter level for each trap receiver
before configuration.

Note:
Configure each Oracle Communications Session Delivery Manager that manages an
SBC as trap receivers on the SBC.

SNMP IPv6 Support

The Oracle Communications Session Border Controller supports IPv6 addressing. This
includes trap receiver configuration, statistics, and information within traps that use varbind
data types (InetAddress and InetAddressType).

SNMP Configuration Overview

Use the to configure SNMP on the Oracle Communications Session Border Controller:
1. Configure SNMP System and Agent Parameters.
2. Configure SNMPv3 or SNMPv2.
3. Enable SNMP Traps.

Configure SNMP System and Agent Parameters

High level SNMP identification is configured by all SNMP users. This information includes
system-level management Information, system contact information, system name and location
information and is applicable to both SNMPv1v2 and SNMPv3 deployments. The Oracle®
Communications Session Border Controller MIB Reference Guide includes detail on SNMP
data.
1. Access the system-config configuration element.

ORACLE# configure terminal

ORACLE(configure)# system
ORACLE(system)# system-config
ORACLE(system-config)#

1-2
Chapter 1
SNMPv3

2. Type select to begin editing the system-config object.

ORACLE(system-config)# select
ORACLE(system-config)#

3. mib-system-contact—Specifies contact information that is used within SBC MIB

transactions. This value is a textual identification and usually contains information about
the company system contact person.

4. mib-system-name—Specifies the identity of this SBC that is presented within MIB

transactions, which is the FQDN of the node.

5. mib-system-location—Specifies the physical location of the SBC that is reported within

MIB transactions. This parameter is reported when an SNMP GET is issued by the NMS
for the MIB-II sysLocation variable. This parameter has no direct relation to the location
field in the system configuration element.

6. snmp-agent-mode —Select the operating mode of the SNMP agent.

• v1v2—(Default) The SNMP agent supports SNMPv1 and SNMPv2. Configure the The
snmp-community and trap-receiver elements only.
• v3—The SNMP agent supports SNMPv3, but can also support SNMPv2 through
snmp-user-group element configuration.

Note:
To create a v2 snmp-user-group, you configure the mp-model parameter to
v1v2 and leave the community-string parameter blank. The system then
matches hosts' SNMP version 2 community strings with the user-list
parameter value. You also configure snmp-user-entry and snmp-address-
entry elements to complete your v2 group configuration.

7. snmp-engine-id-suffix—Uniquely identifies the SNMP Engine by specifying a unique

suffix for the SNMPEngineID. This attribute is optional.
8. snmp-rate-limit—Set the rate limit for SNMP traffic to prevent SNMP from interfering with
service traffic. The range is from 0 to 9999 packets per second. The default is zero, which
applies no limit.
9. lower-snmp-priority—This option allows you to lower the priority of the SNMP processing
task to prevent SNMP from interfering with service processing.

ORACLE(system-config)options +lower-snmp-priority=enabled

If you type the option without the plus sign, you overwrite any previously configured
options. To append the new option to the options list, prepend the new option with a plus
sign as shown in the previous example.
10. Type done to save your configuration.

SNMPv3
The Oracle Communications Session Border Controller supports SNMPv3 by default. To
secure your SNMPv3 system, you must configure SNMP users and groups, SNMP managers,
and view access to MIB trees. SNMPv3 provides the SNMP agent and SNMP Network

1-3
Chapter 1
SNMPv3

Management System (NMS) with protocol security enhancements used to protect your system
against a variety of attacks, such as increased authentication, privacy, MIB object access
control and trap filtering capabilities.

SNMPv3 Users
An identity must be created for an SNMPv3 user to specify their name, security protocol
choices, passwords for secure authentication and privacy, and the ability to receive secured
traps. You configure SNMPv3 users to protect your SNMPv3 system from any unauthorized
SNMP agent that uses message capture and replay or a network traffic source that uses an
incorrect password or security level.

Configure an SNMPv3 User Identity

1. Access the system configuration element.

ORACLE# configure terminal

ORACLE(configure)# system
ORACLE(system)#

2. Type snmp-user-entry and press Enter. The system prompt changes to let you know that
you can begin configuring individual parameters used to create an identity for an SNMPv3
user.

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

3. user-name—Enter the name of the user authorized for retrieving SNMPv3 traps.
Values:
• <user name string>—that is 1 to 24 characters.
4. auth-protocol—Specify the authentication protocol.
• sha256—HMAC-SHA2-256 authentication protocol.
• sha512—(Default) HMAC-SHA2-512 authentication protocol.
5. priv-protocol—Specify the privacy algorithm.
• aes128—Authenticates using the AES128 algorithm.
6. auth-password—Enter the authorization password for this user.
Value:
• <password-string>— that is 6 to 64 characters.
7. priv-password—Enter the privilege password for this user.
Value:
• <password-string>— that is 6 to 64 characters.
8. address-list—Enter the host IP address(es) that are associated with this user.
• <address-string>— that is 1 to 24 characters. You can specify multiple address list
names by enclosing them within brackets "()".
9. Type done to save your configuration.

1-4
Chapter 1
SNMPv3

Note:
Repeat the previous steps if you need to add more SNMPv3 users.

SNMPv3 User Groups

A group of SNMPv3 users can be specified for easy management and access control.
Each SNMPv3 user can be configured to belong to a specific security model and security level.
You can choose either the SNMPv1 and v2 model or the SNMPv3 model (which is selected for
you by default). When you assign a security level to a group, this level is consistent for all
users within this group and the security level can be used across multiple SBC devices. Also,
these security levels determine how data is encrypted to prevent information leaks and stop an
unauthorized user from scrambling the contents of an SNMP packet.
The following security levels can be assigned to an SNMPv3 group:
• The default authPriv security level specifies that the user group is authenticated by using
either the HMAC-SHA2-256 or HMAC-SHA2-512 authentication protocols and the privacy
password is encrypted using the AES128 authentication protocol. Using this security level
provides user authentication and ensures message privacy so that the trap is not tampered
with during transit.
• The noAuthNoPriv security level specifies that the user group is authenticated by a string
match of the user name and requires no authorization and no privacy similar to SNMPv1
and SNMPv2.
• The authNoPriv security level specifies that the user group is authenticated by using either
the HMAC-SHA2-256 or HMAC-SHA2-512 authentication protocols to produce a key used
to authenticate the trap and ensure the identity of the user.
You can also configure an SNMPv3 user group to allow the co-existence of multiple SNMP
message version types at the same time, specify a list of users belonging to the group, and
assign the group privilege to read, write, and add SNMP objects and receive trap notifications.

Configure SNMPv3 User Group

1. Access the system configuration element.

ORACLE# configure terminal

ORACLE(configure)# system
ORACLE(system)#

2. Type snmp-group-entry and press Enter. The system prompt changes to let you know
that you can begin configuring individual parameters used to configure a group of users
that belong to a particular security model who can read, write, and add SNMP objects and
receive trap notifications.

ORACLE(system)# snmp-group-entry
ORACLE(snmp-group-entry)#

3. name <group-name-string>—Specify a group name that is 1 to 24 characters for the

SNMPv3 group name.
4. mp-model—Specify the SNMP message processing model.
Values:

1-5
Chapter 1
SNMPv3

• v1v2—The SNMPv1 and SNMPv2 model.

• v3—The SNMPv3 model (default).

Note:
If the mp-model parameter is specified with the v1v2 value, the community-
string parameter (not configured) defines a coexistence configuration where
SNMP version 2 messages with the community string from the hosts is indicated
by the user-list parameter, and the corresponding snmp-user-entry and snmp-
address-entry elements are accepted.

5. security-level—Specify the security level of the SNMP group, which are consistent for the
user and can be used across multiple SBC devices.
• noAuthNoPriv—This value specifies that the user group is authenticated by a string
match of the user name and requires no authorization and no privacy similar to
SNMPv1 and SNMPv2. This value is specified with the mp-model parameter and its
v1v2 value and can only be used with the community-string parameter not specified.
• authNoPriv—This value specifies that the user group is authenticated by using either
the HMAC-SHA2-256 or HMAC-SHA2-512 authentication protocols to produce a key
used to authenticate the trap and ensure the identity of the user.
• authPriv—This default value specifies that the user group is authenticated by using
either the HMAC-SHA2-256 or HMAC-SHA2-512 authentication protocols and the
privacy password is encrypted using the AES128 algorithm. Using this security level
provides user authentication and ensures message privacy so that the trap is not
tampered with during transit. This value is specified with the SNMP mp-model
parameter and its v3 value.

Note:
If there is a switchover on a high-availability SBC device, the SNMPEngineID
varies and your network management system (NMS) should be updated with the
SNMPEngineID of the standby SBC device.

6. community-string <community-string>—Specify the community name that is 1 to 24

characters to allow the co-existence of multiple SNMP message version types at the same
time for this security group.
7. user-list <user-name string>—Specify a name for the user list that is 1 to 24 characters
and must match the name of the user-name parameter of the snmp-user-entry element
to configure user host names.
8. read-view <group-read-view-string>—Specify the name of the SNMP group's read view
for a collection of MIB subtrees that can be 1 to 24 characters.
9. write-view <group-write-view-string>—Specify the name of the SNMP group's write view
for a collection of MIB subtrees that can be 1 to 24 characters.
10. notify-view <group-notify-view-string>—Specify the name of the SNMP group's trap
notification view for a collection of MIB subtrees that can be 1 to 24 characters.
11. Type done to save your configuration.

1-6
Chapter 1
SNMPv3

Note:
Repeat the previous steps if you need to add more groups.

SNMPv3 Manager Access

You identify an SNMPv3 manager by adding its name and IP address to authenticate and
interpret traffic, such as secure traps that it receives from the SNMP agent device (SBC). This
traffic is kept private during transit by using time stamps and boot counts to protect against
delayed packets.

Configure SNMPv3 Manager Access

1. Access the system configuration element.

ORACLE# configure terminal

ORACLE(configure)# system
ORACLE(system)#

2. Type snmp-address-entry and press Enter. The system prompt changes to let you know
that you can begin configuring individual parameters used to identify the SNMP manager.

ORACLE(system-config)# snmp-address-entry
ORACLE(snmp-address-entry)#

3. name—Specify a name to be referenced when operating with this manager.

Value:
• <management-hostname-string>—that is 1 to 24 characters and is used to specify the
name for the SNMPv3 target IP address.
4. address—Specify the IP address of the manager. The parameter requires an IP address
followed by either the mask, in number of bits, or the port number.

ORACLE(snmp-address-entry)# <ip-address> [/<num-bits>][:port]

Values:
• <ip-address>—IP address in IPv4 or IPv6 standard format.
• /<num-bits>—specifies the mask, in number of bits, used to route to the address.
• <:port>—this optional parameter to enter a subnetwork (subnet) mask. The default
subnet mask is [Link]. Set this value if the manager is a trap-receiver. Do
not set this value if the manager is performing queries.
5. trap-filter-level— Set this value if the manager is a trap-receiver. Select a priority level
that is equal to or lower than the value of the filter-level. Do not set this value if the
manager is performing queries.
Values:
• "" (Default)—The field's setting is blank. The user is not configured to receive any
trap.
• ALL—A user can view all trap conditions.

1-7
Chapter 1
SNMPv3

• Minor—A user can view trap error conditions that exist on a device.
• Major—A user can view trap critical conditions that exist on a device.
• Critical—A user can view trap conditions that require an immediate action for a
device.
6. Type done to save your configuration.

Note:
Repeat the previous steps if you need to add more SNMPv3 target IP addresses.

SNMPv3 Views
SNMPv3 utilizes a view-access-control model (VACM) for checking whether a specific type of
access to a specific managed object is allowed through the SNMPv3. You can configure
individual parameters used to include or exclude view access to single or multiple MIB OID
nodes for an SNMPv3 view name.

Specify SNMPv3 View Access to a MIB

1. Access the system configuration element.

ORACLE# configure terminal

ORACLE(configure)# system
ORACLE(system)#

2. Type snmp-view-entry and press Enter. The system prompt changes to let you know that
you can begin configuring individual parameters used to include or exclude view access.

ORACLE(system)# snmp-view-entry
ORACLE(snmp-view-entry)#

3. name Specify the SNMPv3 view name.

Valid value:
• <SNMP-view-name-string>—that is 1 to 24 characters.
4. included-list— Use this parameter to include view access to a MIB OID subtree or
multiple OID subtrees for this SNMPv3 view name.
Valid value:
• <OID(s)>—Object Identifier number separated by a dot (.), in which each subsequent
number is a sub-identifier. Each subtree OID starts with the prefix [Link].
For example:
– [Link].6
– ([Link].2 [Link].4.1.9148) - You can enter multiple values enclosed in
parenthesis and separated by space or comma.
5. Repeat the previous step if you need to include or exclude additional views.
6. excluded-list—Use this parameter to exclude view access to a MIB OID node for this
SNMPv3 view name.
Valid value:

1-8
Chapter 1
SNMPv1 and SNMPv2

• <OID(s)>— Object Identifier number separated by a dot (.), in which each subsequent
number is a sub-identifier. Each subtree OID starts with the prefix [Link].
For example:
– [Link].4.1.9148.3.3
– ([Link].4.1.9148.3.3 [Link].4.1.9148.3.5) - You can enter multiple values
enclosed in parenthesis and separated by space or comma.
7. Type done to save your configuration.

Note:
Repeat the previous steps if you need to add more SNMPv3 views.

SNMPv1 and SNMPv2

Use this task if you selected v1v2 for the snmp-agent-mode parameter in the system-config
element to configure SNMPv1 and SNMPv2, which includes the configuration of the SNMP
community and the trap receiver.

SNMPv1v2 Community Configuration

Configure the SNMP Community

1. Access the snmp-community configuration element.

ORACLE# configure terminal

ORACLE(configure)# system
ORACLE(system)# snmp-community
ORACLE(snmp-community)#

2. Type community-name to specify the SNMP community name of an active community

where this Oracle Communications Session Border Controller can send or receive SNMP
information.

3. access-mode—Set the access level for all network management servers (NMSs) defined
within this SNMP community. The access level determines the permissions that other NMS
hosts can wield over this Oracle Communications Session Border Controller. The default is
read-only. The valid values are:
• read-only—allows GET requests.
• read-write—unsupported.
4. ip-addresses—Specify a valid IPv4 or IPv6 address within this SNMP community that
corresponds to one or more NMS that monitors or configures this SBC. If you are

1-9
Chapter 1
SNMPv1 and SNMPv2

specifying more than one IP address, separate each IP address with a space and enclose
with parenthesis.

ORACLE#(snmp-community)ip-addresses ([Link] [Link])

5. Type done to save your configuration.

SNMPv1v2 Trap Receiver Configuration

Determine the community, addressing (IPv4 or IPv6) and filter level for each trap receiver
before configuration.

Note:
Configure each Oracle Communications Session Delivery Manager that manages an
SBC as trap receivers on the SBC.

Configure Trap Receivers

1. Access the trap-receiver configuration element.

ORACLE# configure terminal

ORACLE(configure)# system
ORACLE(system)# trap-receiver
ORACLE(trap-receiver)#

2. Select the trap-receiver object to specify a trap receiver.

ORACLE(trap-receiver)# select
<ip-address>:

ORACLE(trap-receiver)#

3. ip-address — Set the IPv4 or IPv6 address of an authorized network management system
(NMS) where traps are sent. If you do not specify a port number, the default SNMP trap
port of 162 is be used.
4. filter-level — Set the filter level threshold that indicates the severity level at which a trap is
to be sent to this particular trap receiver. The default for this parameter is critical.
Example: When a trap with a severity level of critical is generated, the SNMP agent sends
this trap only to NMSs that are configured in a trap-receiver element and have a filter-level
value of critical.
The following table maps Syslog and SNMP alarms to trap receiver filter levels.

Filter Level Syslog Severity Level (SNMP) Alarm Severity

Level
Critical Emergency (1) Emergency
Critical (2) Critical
Major Emergency (1) Emergency
Critical (2) Critical
Major (3) Major

1-10
Chapter 1
Specify an NMS for EMS Generated Traps

Filter Level Syslog Severity Level (SNMP) Alarm Severity

Level
Minor Emergency (1) Emergency
Critical (2) Critical
Major (3) Major
Minor (4) Minor
All Emergency (1) Emergency
Critical (2) Critical
Major (3) Major
Minor (4) Minor
Warning (5) Warning
Notice (6)
Info (7)
Trace (8)
Debug (9)

When configuring the trap-receiver element for use with Oracle Communications Session
Element Manager systems, Oracle recommends that the value of filter-level be set to All
for that configuration element that includes those servers.
5. community-name — Set the community name to which this trap receiver belongs. This
community must be defined in the SNMP community element.
6. Type done to save your configuration.

Specify an NMS for EMS Generated Traps

You must configure a northbound network management server (NMS) such as an SNMP
management system as the receiver of element manager system (EMS) traps. An EMS, such
as the Session Element Manager, generates the (EMS MIB) traps shown in the table below
when it detects the following conditions:
• There is a failure to discover or rediscover a SBC configuration.
• There is a failure to save a SBC configuration.
• There is a failure to activate a SBC configuration.
• There are missing components when validating a SBC configuration.
• The node status changes from reachable to unreachable.

Trap Name Description

1-11
Chapter 1
Enabling Administrative Trap Types

Trap Name Description

apEMSInvalidConfigD Generated when EMS validates a discovered SBC’s configuration (for example
iscoveredNotification confirms each referenced realm is configured) and detects missing components.
The trap contains the time and the SBC node ID.
apEMSNodeUnreach Generated when a node’s status changes from reachable to unreachable. The
ableNotification trap contains the SBC’s node ID and the time of the event.
apEMSNodeUnreach Generated when a node’s status changes from unreachable to reachable. The
ableClearNotification trap contains the SBC’s node ID and the time of the event.

Enabling Administrative Trap Types

Use this task to enable traps for certain Oracle Communications Session Border Controller
(SBC) events that are reported to a network management system. These settings are
applicable to both SNMPv1v2 and SNMPv3 deployments. The SBC does not require you to
enable traps other than those in the following steps.
1. Access the system-config configuration element.

ORACLE# configure terminal

ORACLE(configure)# system
ORACLE(system)# system-config
ORACLE(system-config)#

2. Type select to begin editing the system-config object.

ORACLE(system-config)# select
ORACLE(system-config)#

3. enable-snmp-monitor-traps—When this parameter is enabled, the Oracle

Communications Session Border Controller generates traps with unique trap-IDs for each
syslog event. If this parameter is disabled , a single trap-ID is used for all events, with
different values in the description string. The default is disabled. The valid values are:
• enabled | disabled
4. enable-snmp-auth-traps—Set whether the SNMP authentication traps are enabled. If an
SNMP request fails authentication because of SNMP community mismatch, the SNMP
request will be rejected. This field determines if an SNMP trap will be sent in response to
the authentication failure. The default is disabled. Valid values for this parameter are:
• enabled | disabled
5. enable-env-monitor-traps—Set whether or not the SNMP environment monitor traps are
enabled. Environment traps include main board PROM temperature, power supplies, fan
speeds, etc. The default is disabled. Valid values for this parameter are:
• enabled | disabled
6. enable-snmp-syslog-notify—Set whether SNMP traps are sent when the system
generates an alarm message. The SNMP agent sends a trap when an alarm is generated
if the following conditions are met:
• SNMP is enabled.
• This field is enabled.
• The syslog severity level is equal to or greater than the severity level configured in the
SNMP Syslog Level field.

1-12
Chapter 1
Enabling Media Supervision Traps

The default is disabled. Valid values are:

• enabled | disabled
7. snmp-syslog-his-table-length—Set the length of the syslog trap history table. When a
syslog message that meets the SNMP syslog level field criteria is generated and SNMP is
enabled, the SNMP agent adds that message to a history table. This parameter indicates
the number of entries the table can contain. The default is 1. The valid range is:
• Minimum—1
• Maximum—500
Once the last table entry is filled, the oldest entry will be overwritten with a new entry.
8. snmp-syslog-level—Set the log severity level threshold that will cause the syslog trap to
be sent to an NMS. When this criteria is met and the appropriate SNMP trap is sent, an
entry is written to the SNMP Syslog History Table. The default is warning. The following
are valid values:
• emergency | critical | major | minor | warning | notice | info | trace | debug | detail

Enabling Media Supervision Traps

The Oracle Communications Session Border Controller (SBC) sends the following media
supervision trap when functioning as a border gateway and the media supervision timer
expires:

apSysMgmtMediaSupervisionTimerExpTrap NOTIFICATION-TYPE
OBJECTS { apSysMgmtCallId }
STATUS current
DESCRIPTION
" The trap will be generated when a media supervision timer
has expired. This behavior is disabled by default but may
be enabled by changing the 'media-supervision-traps'
parameter of the 'media-manager' configuration element. The
included object is the call identifer for the call which had
the timer expire."
::= { apSystemManagementMonitors 34 }

Note:
The system does not send this trap when functioning as an integrated SBC.

The media supervision trap is disabled by default. You can enable the trap by changing the
media-supervision-traps parameter to enabled in the media-manager configuration element.

View SNMP Address, Statistics and User Information

The user can view real-time information on agent traffic using the show snmp-info command.
show snmp-info address—View the traffic to and from the SNMPv3 addresses that you
configured in Superuser mode. For example:

<device># show snmp-info address

snmp-address-entry

1-13
Chapter 1
View SNMP Address, Statistics and User Information

name : acme82
address : [Link]:161
mask : [Link]
total requests in : 3
total replies out : 3
total traps out : 1
snmp-address-entry
name : acmepc58
address : [Link]:161
mask : [Link]
total requests in : 0
total replies out : 0
total traps out : 1

show snmp-info statistics—View the SNMP agent mode and statistics for the SNMP engine
in Superuser mode. For example:

<device># show snmp-info statistics

SNMP Agent Mode : V3
SNMP Engine ID Base : 0x800023bc05ac1e50e8
SNMP Engine ID Suffix :
SNMP Engine ID : 0x800023bc05ac1e50e8
SNMP Engine Boots : 622
Total packets in : 17
Total packets out : 10
Total traps out : 2
Unknown security models : 0
Invalid Messsages : 0
Unsupported SecLevels : 0
Not In Time Windows : 0
Unknown User Names : 1
Unknown EngineIDs : 3
Stats Wrong Digests : 0
Decryption Errors : 0

show snmp-info snmp-user—View information and traffic associated with SNMP users in
Superuser mode. For example:

<device># show snmp-info snmp-user

snmp-user-entry
name : snmpuser1
auth-protocol :
auth-password :
priv-protocol :
priv-password :
address-list : address1 address2
total requests in : 0
total get reqs in : 0
total next reqs in: 0
total replies out : 0
total traps out : 0

1-14
Chapter 1
Consideration for HA Nodes

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 Oracle Communications Session Border Controller.

1-15
2
Introduction to MIBs and Traps
This chapter describes Management Information Bases (MIBs) and the correlation between
system alarms and the MIBs that support traps. It also 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.

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, [Link].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.[Link].1024.[Link].3000
• tcpConnState is the OID
• [Link] is an IPv4 address
• 1024 is the port number
• [Link] is another IPv4 address
• 3000 is another port number

2-1
Chapter 2
About 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 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 [Link].4.1.9148.[Link].1.

2-2
Chapter 2
About MIBs

iso
(1)

org 1.3
(3)

dod 1.3.6
(6)

[Link]
internet
(1)

directory mgmt experimental private [Link].4

(1) (2) (3) (4)

mib-2 enterprise [Link].4.1

(1) (1)

systems (1) acmepacket [Link].4.1.9148

Interfaces (2) (9148)
ip (4)
icmp (5)
tcp (6)
udp (7) acmePacketMgmt (3) [Link].4.1.9148.3
apSystemManagementModule (2) [Link].4.1.9148.3.2
apSysMgmtMIBObjects (1) [Link].4.1.9148.3.2.1
apSysMgmtGeneralObjects (1) [Link].4.1.9148.[Link]
apSysCPUUtil (1) [Link].4.1.9148.[Link].1
apSysMemoryUtil (2) [Link].4.1.9148.[Link].2
apSysHealthScore (3) [Link].4.1.9148.[Link].3
apSysRedundancy (4) [Link].4.1.9148.[Link].4

The diagram shows the Acme Packet node has the value 9148; this is Oracle's vendor-specific
number that uniquely identifies an Acme Packet product MIB. This node is the highest level of
the private (proprietary) branch containing Acme Packet managed objects. The number 9148
was assigned by the Internet Assigned Numbers Authority (IANA).

2-3
Chapter 2
MIBs Supported

Managed Objects
Managed objects are made up of one or more object instances, which are essentially
variables. Managed objects can be scalar (defining a single object instance) or tabular
(defining multiple, related instances).

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.

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.

MIBs Supported
The system supports both standard MIBs and Oracle-specific MIBs (enterprise MIBs). The
configurable system elements are identified in the MIBs provided by Oracle. Every 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

2-4
Chapter 2
MIBs Supported

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 [Link].[Link].0, which is the OID for sysUpTime).
Oracle provides the following standard MIBs:
• [Link]
• [Link]
• [Link]
• [Link]
• [Link] (Oracle supports the ifName entry of the ifXTable, which is an extension to
the interface table and which replaces ifExtnsTable. See RFC 2863 for details.)
• [Link]
• [Link]
• [Link]
• [Link]

Enterprise MIBs
Oracle provides the following enterprise MIBs:

MIB Name Description

[Link] 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 [Link] file.
• MIB capabilities include support for the contents of the MIBs listed
in this table. Refer to the individual MIBs for details.
[Link] Management interface on the SBC.
[Link] Codec and transcoding information generated by systems.
[Link] EMS traps.
[Link] OID assignments for Acme Packet hardware components.
[Link] Fan speed, temperature, and power supply for the system. It also sends
out traps when status changes occur.
[Link] Status of your licenses.
[Link] Descriptions of the different SBC versions.
[Link] Information about the Acme Management Interface running on the
SBC.

2-5
Chapter 2
Traps

MIB Name Description

[Link] syslog messages generated by the 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 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.
[Link] Status of the system (for example, system memory or system health).
[Link] General information about the system’s top-level architectural design.
[Link] Status of the boot images, configuration information, and bootloader
images for the system.
[Link] Textual conventions used in enterprise MIBs.

Traps
A trap is initiated by tasks to report that an event has happened on the system. SNMP traps
enable an SNMP agent to notify the NMS of significant events using an unsolicited SNMP
message.
Oracle uses SNMPv2c. These notification definitions are used to send standard and 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 syslog MIB or the System Management MIB).

Standard Traps
The following table identifies the standard traps that the 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.

2-6
Chapter 2
Traps

Trap Name Description

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 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.
This trap is not associated with a system alarm.

Enterprise Traps
The following sections list traps available on the Oracle Communications Session Border
Controller. Traps are divided by the mib file they are contained within.

apSyslog Traps ([Link])

The following traps are found in [Link]. They are used generally for reporting on
environmental changes.

Trap Description
apSyslogMessageGenerated: Generated by a syslog event. For example, this trap
[Link].4.1.9148.[Link].1 is generated if a switchover alarm occurs (for High
Availability (HA) system peers only), or if an HA
system peer times out or goes out-of-service.

apSysMgmt Traps ([Link])

The [Link] includes the following traps, which are generally used for system
management.

Trap Description
apSysMgmtGroupTrap: Generated when a significant threshold for a
[Link].4.1.9148.[Link].1 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 apSysMgmtGroupTrap is generated. If
the health score (for HA peers only) falls below 60,
the apSysMgmtGroupTrap is generated. This trap
is sent for sessions only if tiered thresholds for
sessions have been configured in system-config,
alarm-threshold. If no tiered thresholds have been
configured for sessions, then the
apSysMgmtLicenseCapacity is sent.

2-7
Chapter 2
Traps

Trap Description
apSysMgmtGroupClearTrap: Generated when the SBC’s system resource use or
[Link].4.1.9148.[Link].2 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.
apSysMgmtFanTrap Generated if a fan unit speed falls below the
[Link].4.1.9148.[Link].3 monitoring level.
apSysMgmtGatewayUnreachableTrap: Generated if the gateway specified becomes
[Link].4.1.9148.[Link].10 unreachable by the system.
apSysMgmtCfgSaveFailTrap: Generated if an error occurs while the system is
[Link].4.1.9148.[Link].13 trying to save the configuration to memory.
apSysMgmtAuthenticationFailedTrap: Generated upon an unsuccessful login attempt.
[Link].4.1.9148.[Link].16 The trap includes the following information:
• level (login, user, priv, shell, li-admin,
provisioners)
• protocol (console, telnet, ftp, ssh, sftp, http,
https)
• origin (<IP address>:<port>)
apSysMgmtAlgdCPULoadTrap: Generated if the CPU utilization percentage of
[Link].4.1.9148.[Link].24 application tasks has exceeded the threshold algd-
load-limit.
apSysMgmtAlgdCPULoadClearTrap: Generated when the CPU utilization percentage of
[Link].4.1.9148.[Link].25 application tasks has fallen below the threshold
algd-load-limit.
apSysMgmtENUMStatusChangeTrap: Generated if the reachability status of an ENUM
[Link].4.1.9148.[Link].27 server changes; contains:
• apENUMConfigName
• apENUMServerIpAddress
• apENUMServerStatus
apSysMgmtCollectorPushSuccessTrap: Generated when the collector successfully
[Link].4.1.9148.[Link].44 completes a push operation.
apSysMgmtGatewaySynchronizedTrap: Generated when the default gateway is
[Link].4.1.9148.[Link].49 synchronized in the ARP table.
apSysMgmtCallRecordingStateChangeTrap: Generated when a call recording server changes
[Link].4.1.9148.[Link].50 state.
apSysMgmtCDRPushReceiverFailureTrap: Generated when an enabled CDR push receiver
[Link].4.1.9148.[Link].53 fails. Returns the address, the address type, and
the failure reason code.
apSysMgmtCDRPushReceiverFailureClearTrap: Generated when an enabled CDR push receiver
[Link].4.1.9148.[Link].54 resumes normal operation after a failure.
apSysMgmtCDRPushAllReceiversFailureTrap: Generated when all enabled CDR push receivers
[Link].4.1.9148.[Link].55 fail.
apSysMgmtCDRPushAllReceiversFailureClearTrap Generated when one or more enabled CDR push
[Link].4.1.9148.[Link].56 receivers return to normal operation after failures
were encountered on all push receivers.
apSysMgmtRejectedMesagesThresholdExeededTr Generates when the number of rejected messages
ap exceeds the configured threshold within the
[Link].4.1.9148.[Link].57 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 [Link] file.

2-8
Chapter 2
Traps

Trap Description
apSysMgmtAdminAuditLogFullTrap: Generated when one of the audit logs full threshold
[Link].4.1.9148.[Link].58 is met:
• time interval
• file size
• percentage full
apSysMgmtAdminAuditLogFullClearTrap: Generated when free audit log storage space
[Link].4.1.9148.[Link].59 becomes available.
apSysMgmtAdminAuditPushFailTrap: Generated when the audit file transfer fails.
[Link].4.1.9148.[Link].60
apSysMgmtAdminAuditPushFailClearTrap: Generated when the audit file is successfully
[Link].4.1.9148.[Link].61 transferred.
apSysMgmtAdminAuthLockoutTrap: Generated upon system lockout after multiple
[Link].4.1.9148.[Link].64 authentication failures.
apSysMgmtCdrFileDeleteTrap Generated when a CDR file is deleted because of
[Link].4.1.9148.[Link].70 lack of space on the partition or the drive exceeds
the number of files specified.
apSysMgmtExpDOSTrap Generated when a device exceeds configured
[Link].4.1.9148.[Link].2 thresholds and is denied access by the SBC.
apSysMgmtGatewayUnreachableClear Generated when the system determines that the
[Link].4.1.9148.[Link].21 gateway in question is once again reachable.
apSysMgmtH323InitFailTrap Generated if an H.323 stack has failed to initialize
[Link].4.1.9148.[Link].12 properly and has been terminated.
apSysMgmtHardwareErrorTrap: Provides a text string indicating the type of
[Link].4.1.9148.[Link].14 hardware error that has occurred. If the message
text exceeds 255 bytes, the message is truncated
to 255 bytes.
apSysMgmtInetAddrWithReasonDOSTrap: Generated when an IP address is placed on a deny
[Link].4.1.9148.[Link].4 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.
apSysMgmtInetAddrTrustedToUntrustedDOSTrap Generated when an IP is placed on a untrusted list
[Link].4.1.9148.[Link].5 from trusted list. Contains the ip address that has
been demoted, the realm-id of that IP (if available) ,
and the URI portion of the SIP From header of the
message that caused the demotion.
apSysMgmtInterfaceStatusChangeTrap: Generated when there is a change in the status of
[Link].4.1.9148.[Link].26 the SIP interface; either the SIP interface is in
service or constraints have been exceeded.
• apSysMgmtSipInterfaceRealmName—Realm
identifier for the SIP interface (OID
[Link].4.1.9148.[Link])
• apSysMgmtSipInterfaceIP—IP address of the
first SIP port in the SIP interface (OID
[Link].4.1.9148.[Link])
• apSysMgmtSipInterfaceStatus—Code is 0
(OID [Link].4.1.9148.[Link])
• apSysMgmtSipInterfaceStatusReason—Status
reasons and in-service (3) and
constraintExceeded (4) (OID
[Link].4.1.9148.[Link])

2-9
Chapter 2
Traps

Trap Description
apSysMgmtLDAPStatusChangeTrap: Generated if the status of whether a LDAP server is
[Link].4.1.9148.[Link].42 reachable changes.
apSysMgmtMediaBandwidthTrap: Generated if bandwidth allocation fails at a
[Link].4.1.9148.[Link].7 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: Generated when the percentage rate of failure for
[Link].4.1.9148.[Link].19 media bandwidth allocation decreases to the
default allowable threshold.
apSysMgmtMediaOutofMemory: Generated if the media process cannot allocate
[Link].4.1.9148.[Link].8 memory.
apSysMgmtMediaOutOfMemoryClearr: Generated when the alarm for insufficient memory
[Link].4.1.9148.[Link].20 for media processes is cleared manually.
apSysMgmtMediaPortsTrap: Generated if port allocation fails at a percentage
[Link].4.1.9148.[Link].6 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: Generated if the port allocation failure rate drops
[Link].4.1.9148.[Link].18 below the system’s default acceptable threshold.
apSysMgmtMediaUnknownRealm: Generated if the media process cannot find an
[Link].4.1.9148.[Link].9 associated realm for the media flow.
apSysMgmtNTPClockSkewTrap: Generated if the NTP has to adjust the clock by
[Link].4.1.9148.[Link].43 more than 1000 seconds.
apSysMgmtNTPServerUnreachableTrap: Generated if the specified NTP server becomes
[Link].4.1.9148.[Link].30 unreachable.
• apSysMgmtNTPServer—Server that is or was
formerly unreachable (OID
[Link].4.1.9148.[Link])
apSysMgmtNTPServerUnreachableClearTrap: Generated when an NTP server deemed
[Link].4.1.9148.[Link].31 unreachable subsequently becomes reachable.
apSysMgmtNTPServiceDownTrap: Generated if all configured NTP servers are
[Link].4.1.9148.[Link].32 unreachable.
apSysMgmtNTPServiceDownClearTrap: Generated if NTP service again becomes available.
[Link].4.1.9148.[Link].33
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: Generated if a power supply is powered down,
[Link].4.1.9148.[Link].1 powered up, inserted/present or removed/not
present.

2-10
Chapter 2
Traps

Trap Description
apSysMgmtPushServerUnreachableTrap: Generated if the system collector cannot reach a
[Link].4.1.9148.[Link].28 specified server; used with the historical data
recording (HDR) feature.
apSysMgmtPushServerUnreachableClearTrap: Generated if the system collector can again reach
[Link].4.1.9148.[Link].29 a specified server that was unreachable; used with
the historical data recording (HDR) feature.
apSysMgmtRadiusDownTrap: Generated if all or some configured RADIUS
[Link].4.1.9148.[Link].11 accounting servers have timed out from a RADIUS
server.

2-11
Chapter 2
Traps

Trap Description
apSysMgmtRadiusDownClearTrap: Generated when some or all of the previously
[Link].4.1.9148.[Link].22 unreachable RADIUS servers can be again be
reached.

Note:
The SBC searches
for a TACACS+
server until it finds an
available one and
then stops searching.
However, in the
TACACS+ SNMP
implementation,
SNMP expects the
SBC to make
connection attempts
to all servers. When
there is only one
TACACS+ server and
that server goes
down, the SBC
behaves normally,
sending a
apSysMgmtTacacsDo
wnTrap trap when the
server goes down,
and a
apSysMgmtTacacsDo
wnClearTrap trap
when the server
comes back up.
When there is more
than one TACACS+
server and the active
server goes down, an
apSysMgmtTacacsDo
wnTrap trap is sent,
indicating that some
servers are down and
the next server is
tried. If all servers fail,
an
apSysMgmtTacacsDo
wnTrap is sent
indicating that all
servers are down. If
one of the servers
comes back up while
the rest are still down,
an
apSysMgmtTacacsDo
wnTrap is sent
indicating that some
servers are still down.

2-12
Chapter 2
Traps

Trap Description
apSysMgmtTacacsDownTrap Generated when a TACACS+ server becomes
[Link].4.1.9148.[Link].78 unreachable.

2-13
Chapter 2
Traps

Trap Description
apSysMgmtTacacsDownClearTrap Generated when a TACACS+ server that was
[Link].4.1.9148.[Link].79 unreachable becomes reachable.
apSysMgmtRealmIcmpFailureTrap: Generated when ICMP heartbeat failure occurs.
[Link].4.1.9148.[Link].51
apSysMgmtRealmIcmpFailureClearTrap: Generated when ICMP heartbeat failure clears.
[Link].4.1.9148.[Link].52
apSysMgmtRegCacheThresholdTrap: Generated when the number of contacts stored in
[Link].4.1.9148.[Link].46 the registration cache exceeds the configured
threshold.
apSysMgmtRegCacheThresholdClearTrap: Generated when the number of contacts stored in
[Link].4.1.9148.[Link].47 the registration cache falls below the configured
threshold.
apSysMgmtRealmMinutesExceedTrap: Generated if the monthly minutes for a realm are
[Link].4.1.9148.[Link].40 exceeded.
apSysMgmtRealmMinutesExceedClearTrap: Generated if monthly minutes for a realm are reset.
[Link].4.1.9148.[Link].41
apSysMgmtRealmStatusChangeTrap: Generated when there is a change in the status of
[Link].4.1.9148.[Link].45 the realm constraints.
apSysMgmtRedundancyTrap: Generated if a state change occurs on either the
[Link].4.1.9148.[Link].5 primary or secondary system in a redundant (HA)
pair.
apSysMgmtSAStatusChangeTrap: Generated when a session agent is declared
[Link].4.1.9148.[Link].15 unreachable or unresponsive for the following
reasons:
• signaling timeout (H.323 and SIP)
• session agent does not respond to SIP pings
(SIP only)
When session agents are declared unreachable or
unresponsive, they are placed out-of-service for a
configurable period of time.
apSysMgmtSipRejectionTrap: Generated when a SIP INVITE or REGISTRATION
[Link].4.1.9148.[Link].1 request fail.
apSysMgmtSpaceAvailThresholdTrap: Generated when the space available on a partition
[Link].4.1.9148.[Link].68 crosses a configured space threshold.
apSysMgmtSpaceAvailThresholdClearTrap: Generated when the space available on a partition
[Link].4.1.9148.[Link].69 falls below the lowest configured threshold.
apSysMgmtSurrogateRegFailed: Generated if a SIP user attempts to register more
[Link].4.1.9148.[Link].39 than the configured, allowable number of times;
supports SIP surrogate registration for IMS.
• apSysMgmtSurrogateRegHost (OID
[Link].4.1.9148.[Link].35)
• apSysMgmtSurrogateRegAor (OID
[Link].4.1.9148.[Link].36)
apSysMgmtSystemStateTrap: Generated when the SBC is instructed to change
[Link].4.1.9148.[Link].17 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)

2-14
Chapter 2
Traps

Trap Description
apSysMgmtTaskDelete: Generated to described what task was deleted.
[Link].4.1.9148.[Link] 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: [Reserved for future use.]
[Link].4.1.9148.[Link].23 Generated when a task is deleted; it reads
apSysMgmtTaskDelete and includes the test in the
trap.
apSysMgmtTaskSuspendTrap: Generated if a critical task running on the system
[Link].4.1.9148.[Link].4 enters a suspended state.
apSysMgmtTempTrap: Generated if the temperature falls below the
[Link].4.1.9148.[Link].2 monitoring level.
apSysMgmtAdminWriteFailTrap: Generated when a write to the admin audit or a
[Link].4.1.9148.[Link].62 history file fails.
apSysMgmtAdminWriteFailClearTrap: Generated when a write to the admin audit or a
[Link].4.1.9148.[Link].63 history file succeeds after a write to either had
previously failed.
apSysMgmtExtPolicyServerConnDownTrap Generated when the SBC is unable to connect to
[Link].4.1.9148.[Link].74 an external policy server
apSysMgmtExtPolicyServerConnEstTrap Generated when the SBC is able to re-establish a
[Link].4.1.9148.[Link].75 connection with an external policy server
apSecurityOCSRDownNotification: Generated when an OSCR server becomes
[Link].4.1.9148.[Link].0.1 unreachable.
apSecurityOCSRUpNotification: Generated when an OSCR server becomes
[Link].4.1.9148.[Link].0.2 available.
apSysMgmtOCSRDownTrap: Generated if all or some of the configured OSCR
[Link].4.1.9148.[Link].80 accounting servers are down.
apSysMgmtOCSRDownClearTrap: Generated if all OSCR accounting servers have
[Link].4.1.9148.[Link].81 resumed communications.
apSysMgmntH248AssociationLostClearTrap This trap will be generated when an H248 control
[Link].4.1.9148.[Link].36 association between a border gateway and session
controller has been restored. The included object is
the border gateway identifier.
apSysMgmntH248AssociationLostTrap This trap will be generated when an H248 control
[Link].4.1.9148.[Link].35 association between a border gateway and session
controller is lost. The included object is the border
gateway identifier.
apSysMgmtDatabaseRegCacheCapClearTrap The trap will be generated when the number of
[Link].4.1.9148.[Link].77 database-type contacts stored in the registration
cache falls below the licensed threshold.
apSysMgmtDatabaseRegCacheCapTrap The trap will be generated when the number of
[Link].4.1.9148.[Link].76 database-type contacts stored in the registration
cache exceeds the licensed threshold.
apSysMgmtH248PortMapUsageClearTrap The trap will be generated when the port map
[Link].4.1.9148.[Link].85 usage on H.248 core side Goes down below 90%.
apSysMgmtH248PortMapUsageTrap The trap will be geenerated when the port map
[Link].4.1.9148.[Link].84 usage on H.248 core side Exceeds 90%.

2-15
Chapter 2
Traps

Trap Description
apSysMgmtLPLookupExceededTrap The trap will be generated the first time the
[Link].4.1.9148.[Link].65 Additional Local Policy Lookups limit is reached in
the recent window period. This trap will only occur
once during a window period.
apSysMgmtMediaSupervisionTimerExpTrap The trap will be generated when a media
[Link].4.1.9148.[Link].34 supervision timer has expired. This behavior is
disabled by default but may be enabled by
changing the 'media-supervision-traps' parameter
of the 'media-manager' configuration element. The
included object is the call identifier for the call
which had the timer expire.
apSysMgmtSataAccessErrorTrap The trap will be generated when there is fatal
[Link].4.1.9148.[Link].71 access error on the SATA hard drive.
apSysMgmtShortSessionExceedTrap The trap will be generated when the amount of
[Link].4.1.9148.[Link].48 short sessions in a realm exceeds the short
session threshold within the short session window.
apSysMgmtSingleUnitRedundancyTrap The trap will generated a slot's status changes. The
[Link].4.1.9148.[Link].3 varbinds contain the new information for the
generating slot.
apSysMgmtSipInterfaceRegCacheThresholdClearT The trap will be generated when the number of
rap contacts stored in the registration cache falls below
[Link].4.1.9148.[Link].83 the configured threshold for the sip interface.
apSysMgmtSipInterfaceRegCacheThresholdTrap The trap will be generated when the number of
[Link].4.1.9148.[Link].82 contacts stored in the registration cache exceeds
the configured threshold for the sip interface.
apSysMgmtTcaClearTrap The trap will be generated when a Threshold
[Link].4.1.9148.[Link].73 Crossing Alert counter has fallen below the lowest
configured TCA reset-threshold value
apSysMgmtTcaTrap The trap will be generated when a Threshold
[Link].4.1.9148.[Link].72 Crossing Alert counter crosses a configured TCA
threshold

apSysMgmtGroupTrap Traps
The apSysMgmtGroupTrap ([Link].4.1.9148.[Link].1) can convey multiple traps by
identifying a system event and corresponding value. The apSysMgmtGroupClearTrap
([Link].4.1.9148.[Link].2) is sent when this condition is cleared, according to the application.

apSysMgmtTrapType Description
apSysXCodeOpusCapacity When Opus session utilization exceeds 90%, this
[Link].4.1.9148.[Link].46 object is sent in the apSysMgmtGroupTrap. When
utilization falls below 85%, the
apSysMgmtGroupClearTrap is sent.
apSysXCodeSILKCapacity When SILK session utilization exceeds 90%, this
[Link].4.1.9148.[Link].47 object is sent in the apSysMgmtGroupTrap. When
utilization falls below 85%, the
apSysMgmtGroupClearTrap is sent.

2-16
Chapter 2
Traps

apSysMgmtTrapType Description
apSysResrvdNsepSessionCapacity When enabled, the system detects when it has
[Link].4.1.9148.[Link].50 exceeded either the minor, major or critical number
of reserved NSEP sessions, it sends this object in
the apSysMgmtGroupTrap. These thresholds are,
by default, 70%, 80% and 90% of your reserved
NSEP session pool, respectively.
When NSEP session utilization falls below the
triggered threshold, the system sends the
apSysMgmtGroupClearTrap.

apSwinventory Traps ([Link])

The following traps are found in [Link]. They are used generally for reporting
on configuration changes.

Trap Description
apSwCfgActivateNotification: Generated when an activate-config command is
[Link].4.1.9148.[Link].1 issued and the configuration has been changed at
running time.
This trap includes the next two objects in this table.
apSwCfgTrapPreviousVersion The previous version before this trap happened
[Link].4.1.9148.[Link].1
apSwCfgTrapCurrentVersion The current version after this trap happened
[Link].4.1.9148.[Link].2

apEnvMon Traps ([Link])

The following traps are found in [Link]. They are used generally for reporting
on environmental changes.

Trap Description
apEnvMonI2CFailNotification: Sent when the Inter-IC bus (I2C) state changes
[Link].4.1.9148.[Link].1 from normal (1) to not functioning (7).
apEnvMonPortChangeNotification: For the AP4500 only. Generated if a physical port is
[Link].4.1.9148.[Link].5 inserted/present or removed/not present.
apEnvMonStatusChangeNotification: Sent when any entry of any environment monitor
[Link].4.1.9148.[Link].2 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.

apLicense Traps ([Link])

The following traps are found in [Link]. They are used generally for reporting on
environmental changes.

2-17
Chapter 2
Traps

Trap Description
apLicenseApproachingCapacityNotification: Generated when the total number of active
[Link].4.1.9148.[Link].1 sessions on the system (across all protocols) is
within 98 - 100% of the licensed capacity.
apLicenseNotApproachingCapacityNotification: Generated when the total number of active
[Link].4.1.9148.[Link].2 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).
apLicenseExpirationWarningNotification This trap is sent when a license is within 7 days of
[Link].4.1.9148.[Link].3 expiration.

apSecurity Traps ([Link])

The following traps are found in [Link].

Trap Description
apSecurityTunnelFailureNotification: Generated when an IPSec IKEV2 tunnel cannot be
[Link].4.1.9148.[Link].0.1 established.
apSecurityRadiusFailureNotification The notification will be generated whenever
[Link].4.1.9148.[Link].0.2 RADIUS authentication request fails.
apSecurityAuthFailureThresholdNotification Generated when IKE DDos auth-failure-threshold is
[Link].4.1.9148.[Link].0.3 reached and report mode includes SNMP trap.
apSecurityTacacsFailureNotification Generated when TACACS+ authentication request
[Link].4.1.9148.[Link].0.4 fails due to one of the following reasons:
• a TACACS+ daemon becomes unreachable
• an unreachable TACACS+ daemon becomes
reachable
• an authentication error occurs
• an authorization error occurs
apSecurityTunnelFailureInetNotification The notification will be generated whenever IPSEC
[Link].4.1.9148.[Link].0.5 IKEV2 tunnel fails to establish.
apSecurityAuthFailureThresholdInetNotification Generated when IKE DDos auth-failure-threshold is
[Link].4.1.9148.[Link].0.6 reached and report mode includes SNMP trap.
apSecurityTunnelDPDNotification: Generated when an IPSec IKEV2 tunnel fails
[Link].4.1.9148.[Link].0.1 because of Dead Peer Detection (DPD).
apSecurityIPsecTunCapNotification This notification is sent when the percentage of
[Link].4.1.9148.[Link].0.2 licensed IPsec tunnels exceeds an IPsec tunnel
alarm threshold. The apSecurityIPsecTunCapPct
object indicates the current percentage.
apSecurityIPsecTunCapClearNotification This trap is sent when the percentage of licensed
[Link].4.1.9148.[Link].0.3 IPsec tunnels no longer exceeds an IPsec tunnel
alarm threshold. The apSecurityIPsecTunCapPct
object indicates the current percentage.
apSecurityTunnelDPDInetNotification The notification will be generated whenever IPSEC
[Link].4.1.9148.[Link].0.4 IKEV2 tunnel fails due to Dead Peer Detection
(DPD).
apSecurityCRLInvalidNotification: Generated when an invalid CRL is detected.
[Link].4.1.9148.[Link].0.1
apSecurityCRLRetrievalFailNotification This notification is sent when there is a failure in
[Link].4.1.9148.[Link].0.1 CRL retrieval.

2-18
Chapter 2
Traps

Trap Description
apSecurityCRLRetrievalClearNotification This notification is sent when there is a success in
[Link].4.1.9148.[Link].0.2 CRL retrieval.
apSecurityCertExpiredNotification This trap is generated periodically if a locally
[Link].4.1.9148.[Link].0.1 installed certificate has expired. The interval of
minutes between this trap being generated is
configured in the local-cert-exp-trap-int
parameter.
apSecurityCertExpireSoonNotification This trap is generated if a locally installed
[Link].4.1.9148.[Link].0.2 certificate will soon expire. The number of days
before expiration in which this trap is sent is
configured in the local-cert-exp-warn-period
parameter.
apSecurityGTPLinkFailureNotification This notification is sent when there is a link failure
[Link].4.1.9148.[Link].0.1 with GGSN/PGW on GTP Profile.
apSecurityGTPLinkClearNotification This notification is sent when the link is restored
[Link].4.1.9148.[Link].0.2 with GGSN/PGW on GTP Profile.
apSecurityTacacsDownLocalAuthUsedTrap The trap will be generated when a user remotely
[Link].4.1.9148.[Link].0.1 logs into a system configured for TACACS+
authentication and is authenticated locally by the
system because all of the configured and enabled
TACACS+ servers have become unreachable or
unresponsive.
apSecurityTacacsDownLocalAuthUsedClearTrap The trap will be generated when a user remotely
[Link].4.1.9148.[Link].0.2 logs into a system configured for TACACS+
authentication and is successfully authenticated
(i.e., access accepted or denied) remotely by a
configured and enabled TACACS+ server.
apSecurityTlsEncryptionFailureNotification These notifications are sent when there is a failure
[Link].4.1.9148.[Link].0.1 during TLS packet encryption.
The MIB objects involved are:
• apSecuritySrcAddressFamily
([Link].4.1.9148.[Link])
• apSecuritySrcAddress
([Link].4.1.9148.[Link])
• apSecuritySrcPort
• apSecurityDstAddressFamily
([Link].4.1.9148.[Link])
• apSecurityDstAddress
([Link].4.1.9148.[Link])
• apSecurityDstPort
• apSecurityTlsEncryptionFailureCause
([Link].4.1.9148.[Link])
• apSecurityTlsCipherSuite
([Link].4.1.9148.[Link])
• apSecurityTlsSessionId
([Link].4.1.9148.[Link])
• apSecurityTlsPacketFailureCount
([Link].4.1.9148.[Link])

2-19
Chapter 2
Traps

Trap Description
apSecurityTlsDecryptionFailureNotification These notifications are sent when there is a failure
[Link].4.1.9148.[Link].0.2 during TLS packet decryption.
The MIB objects involved are:
• apSecuritySrcAddressFamily
([Link].4.1.9148.[Link])
• apSecuritySrcAddress
([Link].4.1.9148.[Link])
• apSecuritySrcPort
• apSecurityDstAddressFamily
([Link].4.1.9148.[Link])
• apSecurityDstAddress
([Link].4.1.9148.[Link])
• apSecurityDstPort
• apSecurityTlsDecryptionFailureCause
([Link].4.1.9148.[Link])
• apSecurityTlsCipherSuite
([Link].4.1.9148.[Link])
• apSecurityTlsSessionId
([Link].4.1.9148.[Link])
• apSecurityTlsPacketFailureCount
([Link].4.1.9148.[Link])
apSecuritySrtpEncryptionFailureNotification These notifications are sent when there is a failure
[Link].4.1.9148.[Link].0.1 during SRTP packet encryption.
The MIB objects involved are:
• apSecuritySrcAddressFamily
([Link].4.1.9148.[Link])
• apSecuritySrcAddress
([Link].4.1.9148.[Link])
• apSecuritySrcPort
• apSecurityDstAddressFamily
([Link].4.1.9148.[Link])
• apSecurityDstAddress
([Link].4.1.9148.[Link])
• apSecurityDstPort
• apSecuritySrtpEncryptionFailureCause
([Link].4.1.9148.[Link])
• apSecuritySrtpEncrAlgorithm
([Link].4.1.9148.[Link])
• apSecuritySrtpAuthAlgorithm
([Link].4.1.9148.[Link])

2-20
Chapter 2
Traps

Trap Description
apSecuritySrtpDecryptionFailureNotification These notifications are sent when there is a failure
[Link].4.1.9148.[Link].0.2 during SRTP packet decryption.
The MIB objects involved are:
• apSecuritySrcAddressFamily
([Link].4.1.9148.[Link])
• apSecuritySrcAddress
([Link].4.1.9148.[Link])
• apSecuritySrcPort
• apSecurityDstAddressFamily
([Link].4.1.9148.[Link])
• apSecurityDstAddress
([Link].4.1.9148.[Link])
• apSecurityDstPort
• apSecuritySrtpDecryptionFailureCause
([Link].4.1.9148.[Link])
• apSecuritySrtpEncrAlgorithm
([Link].4.1.9148.[Link])
• apSecuritySrtpAuthAlgorithm
([Link].4.1.9148.[Link])
apSecurityAuthFailureThresholdInetNotification

apSLB Traps ([Link])

The following traps are found in [Link]. They are used generally for reporting on the
Session Load Balancer.

Trap Description
apSLBEndpointCapacityThresholdTrap The trap will be generated when the number of
[Link].4.1.9148.[Link].1 endpoints on the SLB exceeds the configured
threshold.
apSLBEndpointCapacityThresholdClearTrap The trap will be generated when the number of
[Link].4.1.9148.[Link].2 endpoints on the SLB falls below the configured
threshold.
apSLBUntrustedEndpointCapacityThresholdTrap The trap will be generated when the number of
[Link].4.1.9148.[Link].3 untrusted endpoints on the SLB exceeds the
configured threshold.
apSLBUntrustedEndpointCapacityThresholdClearTra The trap will be generated when the number of
p untrusted endpoints on the SLB falls below the
[Link].4.1.9148.[Link].4 configured threshold.

apH323 Traps ([Link])

The following traps are found in [Link]. They are used generally for reporting on
environmental changes.

Trap Description
apH323StackMaxCallThresholdTrap: Generated when the number of H.323 calls
[Link].4.1.9148.[Link].1 increases the percentage of the max calls
threshold.
apH323StackMaxCallThresholdClearTrap: Generated when the number of H.323 calls
[Link].4.1.9148.[Link].2 decreases to below the lowest max calls threshold.

2-21
Chapter 2
Traps

apDiameter Traps ([Link])

The following traps are found in [Link].

Trap Description
apDiameterAcctSrvrUpTrap: Generated when a Diameter Accounting Server
.[Link].4.1.9148.[Link].2.0.1 goes up.
apDiameterAcctSrvrDownTrap: Generated when a Diameter Accounting Server
[Link].4.1.9148.[Link].2.0.2 goes down.
apAcctMsgQueueFullTrap: Generated when the accounting message queue is
[Link].4.1.9148.[Link].2.0.3 full and all accounting servers are down.
apAcctMsgQueueFullClearTrap: Generated when the apAcctMsgQueueFullTrap
[Link].4.1.9148.[Link].2.0.4 condition clears.
apDiameterSrvrErrorResultTrap: Generated when the Diameter Server returns 3xxx
[Link].4.1.9148.[Link].2.0.5 (Protocol Errors), 4xxx (Transient Failures), or 5xxx
(Permanent Failure) Result-Code AVP (268).
apDiameterSrvrSuccessResultTrap: After an error result, generated when the Diameter
[Link].4.1.9148.[Link].2.0.6 Server returns a 2xxx (Success) Result-Code AVP
(268).

apDnsAlg Traps ([Link])

The following traps are found in [Link].

Trap Description
apDnsAlgStatusChangeTrap Generated if the reachability status of an DNS-ALG
[Link].4.1.9148.[Link].0.1 server changes from In-Service to either Timed out
or Out of Service.
apDnsAlgStatusChangeClearTrap Generated if the reachability status of an DNS-ALG
[Link].4.1.9148.[Link].0.2 server changes from either Timed out or Out of
Service to In-Service.
apDnsAlgConstraintStateChangeTrap Generated if a DNS-ALG configuration object's
[Link].4.1.9148.[Link].0.3 constraints state changes from In-Service to
Constraints Exceeded.
apDnsAlgConstraintStateChangeClearTrap Generated if a DNS-ALG configuration object's
[Link].4.1.9148.[Link].0.4 constraints state changes from Constraints
Exceeded to In-Service.
apDnsAlgSvrConstraintStateChangeTrap Generated if a DNS Server (i.e. IP-Address)
[Link].4.1.9148.[Link].0.5 constraints state changes from In-Service to
Constraints Exceeded.
apDnsAlgSvrConstraintStateChangeClearTrap Generated if a DNS Serve (i.e. IP-Address)
[Link].4.1.9148.[Link].0.6 constraints state changes from Constraints
Exceeded to In-Service.

apSip Traps ([Link])

The following traps are found in [Link].

2-22
Chapter 2
Traps

Trap Name Description

apSipSecInterfaceRegThresholdExce Generated if the total number of registrations on all secondary
ededTrap: SIP interfaces exceeds the configured threshold.
[Link].4.1.9148.[Link].2.0.1
apSipSecInterfaceRegThresholdClear Generated if the total number of registrations on all secondary
Trap: SIP interfaces falls below the configured threshold.
[Link].4.1.9148.[Link].2.0.2
apSipSurvivabilityModeEnter The trap will be generated when SIP interface enters
[Link].4.1.9148.[Link].2.0.1 Survivability Mode.
apSipSurvivabilityModeExit The trap will be generated when SIP interface exits Survivability
[Link].4.1.9148.[Link].2.0.2 Mode and resumes normal operation.
apSipCACUtilAlertTrap Generated if the apSipCACUtilTrapValue exceeds the
[Link].4.1.9148.[Link].2.0.1 monitoring threshold set in the cac-trap-threshold configured
in a realm or session agent.
apSipCACUtilClearTrap Generated when the CAC utilization thresholds fall below the
[Link].4.1.9148.[Link].2.0.2 cac-trap-threshold configured in a realm or session agent.
apSipRecRecDlgFailNotify, This trap will be generated when a Recording Dialog fails to
[Link].4.1.9148.[Link].0.1 send a timely response to a requests, typically an in-dialog
OPTIONS request.
apSipRecCommSessionNotify This trap will be generated when a Communications Session is
[Link].4.1.9148.[Link].0.2 terminated because a recording dialog could not be established
or prematurely terminated.

apApps Traps ([Link])

The [Link] includes the following traps.

Trap Description
apAppsENUMServerStatusChangeTrap Generated if the reachability status of an ENUM
[Link].4.1.9148.[Link].1.0.1 server changes.
apAppsDnsServerStatusChangeTrap Generated if the reachability status of a DNS
[Link].4.1.9148.[Link].2.0.1 server changes.
apAclDropOverThresholdTrap Generated when the acl drop ratio exceeds the
[Link].4.1.9148.[Link].4.0.1 configured threshold.
apAclDropOverThresholdClearTrap Generated when the acl drop ratio goes below the
[Link].4.1.9148.[Link].4.0.2 configured threshold.
apMonitorCollectorDownTrap Generated when there is a disconnect between a
[Link].4.1.9148.[Link].3.0.1 Session Border Controller and a CommMonitor.
apMonitorCollectorClearTrap Generated when a Session Border Controller
[Link].4.1.9148.[Link].3.0.2 reconnects with the CommMonitor and normal
operation resumes.
apStirServerUnreachableTrap Generated when experiencing repeated sequential
[Link].4.1.9148.[Link].5.0.1 REST STI server response timeouts the SBC.
apStirServerUnreachableClearTrap Generated when experiencing repeated sequential
[Link].4.1.9148.[Link].5.0.2 REST STI server response timeouts the SBC stop
occurring.

2-23
Chapter 2
Traps

apAclDropOverThresholdTrap Objects
The following objects, which are part of the apAclDropOverThresholdTrap, are not available
with an SNMP GET.

MIB Object Description

apAclDropType ACL drop type.
[Link].4.1.9148.[Link].1
apAclDropCount ACL drop count within monitor time window.
[Link].4.1.9148.[Link].2
apAclDropRatio ACL drop ratio as permillage of current time
[Link].4.1.9148.[Link].3 window.

apUSBC Traps ([Link])

The following traps are found in [Link].

Trap Name Description

apUsbcSysThreadUsageExceededTra The trap is generated when a thread is exceeding pre-defined
p usage.
[Link].4.1.9148.[Link].1.1
apUsbcSysThreadUsageClearTrap The trap is generated when a thread is dropping back under
[Link].4.1.9148.[Link].1.2 pre-defined usage.
apUsbcSysThreadUsageOverloadEna The trap is generated when a thread cpu overload is activated.
bleTrap
[Link].4.1.9148.[Link].1.3
apUsbcSysThreadUsageOverloadDisa The trap is generated when a thread cpu overload is de-
bleTrap activated.
[Link].4.1.9148.[Link].1.4
apUsbcSysThreadNotRespondingTrap The trap is generated when a thread is not responding.
[Link].4.1.9148.[Link].1.0.7
apMutexDeadLockDetectedTrap The trap is generated when the system detects a deadlock.
[Link].4.1.9148.[Link].1.0.5
apMutexDeadLockClearTrap The trap is generated when the system detects that a deadlock
[Link].4.1.9148.[Link].1.0.6 us clear.
apUsbcSysFdCountClearTrap The trap will be generated when the FD count drops below the
[Link].4.1.9148.[Link].2.0.2 pre-defined threshold.
apUsbcSysFdCountExceedingTrap The trap will be generated when the FD count is over a
[Link].4.1.9148.[Link].2.0.1 threshold.

Specify an NMS for EMS Generated Traps

2-24
Chapter 2
Persistent indexing of SNMP Tables

• There is a failure to save a SBC configuration.

• There is a failure to activate a SBC configuration.
• There are missing components when validating a SBC configuration.
• The node status changes from reachable to unreachable.

Trap Name Description

apEMSDiscoveryFailu Generated when EMS fails to discover or rediscover a SBC configuration. The
re trap is generated from any discovery or rediscovery failure initiated by the SOAP
XML API, EMS, or system processing. The trap contains the SBC’s node ID, the
start and end time of the discovery or rediscovery operation, and the user who
initiated the operation.
apEMSSaveFailure Generated when EMS fails to save a configuration. The trap is generated by a
save failure whether initiated by the SOAP XML API or EMS GUI for save/
activate, save or offline save operations. The trap contains the SBC node ID, the
start and stop time of the save configuration attempt, and the user initiating the
save operation.
apEMSActivateFailure Generated when EMS fails to activate a configuration, whether initiated from the
SOAP XML API or EMS GUI for the save/activate or activate operations.
apEMSInvalidConfigD Generated when EMS validates a discovered SBC’s configuration (for example
iscoveredNotification confirms each referenced realm is configured) and detects missing components.
The trap contains the time and the SBC node ID.
apEMSNodeUnreach Generated when a node’s status changes from reachable to unreachable. The
ableNotification trap contains the SBC’s node ID and the time of the event.
apEMSNodeUnreach Generated when a node’s status changes from unreachable to reachable. The
ableClearNotification trap contains the SBC’s node ID and the time of the event.

Persistent indexing of SNMP Tables

Certain Oracle Communications Session Border Controller proprietary MIB tables support
persistent indexing across reboots. The purpose is to maintain the value of that object so that
after a reboot or configuration reload, the value that identifies an object remains the same.
Please be aware of the following three limitations:

ObjectID Wrapping
The maximum value of an object that is persistently indexed is 4294967295. In the unlikely
event that the Net-Net SBC exhausts all index values, it will wrap beginning with the first,
lowest, unused index number.

Consecutive Table Entries

For any two consecutive table entries, the indices from ObjectID are not guaranteed to be
consecutive. The value of an ObjectID reflects the order when the object is created.

Persistent Exception
Using the backup-config and the restore-backup-config commands do not impact the index
persistency. But, if a configuration file created on one Net-Net SBC is loaded on another Net-
Net SBC, the element IDs were assigned by the first Net-Net SBC are likely to be different that
the IDs used on the second Net-Net SBC.
If, after a backup is created, an element is deleted from the configuration and then later
created again, the element's ID will probably change. Then, if the operator restores an older
backup, a change in the MIB ID of the object will result.

2-25
Chapter 2
Log Levels and syslog Level Severities

MIB Table in MIB file Persistent Index

apSigRealmStatsTable [Link] apSigRealmStatsRealmIndex
[Link].4.1.9148.[Link].4
apCombinedSessionAgentStatsT [Link] apCombinedStatsSessionAgentIn
able dex
[Link].4.1.9148.[Link].1
apSipSessionAgentStatsTable [Link] apSipSAStatsSessionAgentIndex
[Link].4.1.9148.[Link].2
apH323SessionAgentStatsTable [Link] apH323SAStatsSessionAgentInd
[Link].4.1.9148.[Link].3 ex

Log Levels and syslog Level Severities

There is a direct correlation between log levels and syslog level severities. This correlation can
be used for syslog MIB reference purposes.

Log Levels
The following table defines the log levels by name and number, and provides a description of
each level.

Numerical Code Log Level Description

1 EMERGENCY The most severe condition within the system which
requires immediate attention. If you do not attend to it
immediately, there could be physical, irreparable
damage to your system.
2 CRITICAL A serious condition within the system which requires
attention as soon as it is noted. If you do not attend to
these conditions immediately, there may be physical
damage to your system.
3 MAJOR Functionality has been seriously compromised. As a
result, there may be loss of functionality, hanging
applications, and dropped packets. If you do not
attend to this situation, your system will suffer no
physical harm, but it will cease to function.
4 MINOR Functionality has been impaired to a certain degree
and, as a result, you may experience compromised
functionality. There will be no physical harm to your
system. However, you should attend to it as soon as
possible in order to keep your system operating
properly.
5 WARNING The system has noted some irregularities in its
performance. This condition is used to describe
situations that are noteworthy. Nonetheless, you
should attend to it in order to keep your system
operating properly.
6 NOTICE All used for Oracle customer support purposes.
7 INFO
8 TRACE
9 DEBUG

2-26
Chapter 2
Log Levels and syslog Level Severities

syslog Level Severities

The following table defines the syslog levels by severity and number against the University of
California Berkeley Software Distribution (BSD) syslog severities (by level and number).
Refer to the Example Log Message column to view example syslog-related content/messages.

syslog Level (Numerical Code) BSD syslog Severity Level (Number)

EMERGENCY (1) Emergency - system is unusable (0)
CRITICAL (2) Alert - action must be taken immediately (1)
MAJOR (3) Critical - critical conditions (2)
MINOR (4) Error - error conditions (3)
WARNING (5) Warning - warning conditions (4)
NOTICE (6) Notice - normal, but significant condition (5)
INFO (7) Informational - informational messages (6)
TRACE (8) Debug - debug level messages (7)
DEBUG (9)

Mapping Trap Filter Levels to syslog and Alarm Severities

Although there is no direct correlation between system alarms and the generation of SNMP
traps, traps can be mapped to syslog and alarm severities through trap filters that are
configured in the filter-level field of the trap-receiver configuration element of the ACLI. The
following table shows this mapping.

filter-level Field Filter Level Description syslog Level Alarm

Value (Numerical Code) Severity
Levels
CRITICAL The SNMP agent sends a trap for all alarms EMERGENCY (1) EMERGENCY
and syslogs with a severity level that is CRITICAL (2) CRITICAL
greater than or equal to CRITICAL (with a
lesser log level numerical code). The
corresponding NMS receives only error
events.
MAJOR The SNMP agent sends a trap for all alarms EMERGENCY (1) EMERGENCY
and syslogs with a severity level that is CRITICAL (2) CRITICAL
greater than or equal to MAJOR (with a MAJOR (3) MAJOR
lesser log level numerical code). The
corresponding NMS receives warning and
error events.
MINOR The SNMP agent sends a trap for all alarms EMERGENCY (1) EMERGENCY
and syslogs with a severity level that is CRITICAL (2) CRITICAL
greater than or equal to MINOR (i.e., with a MAJOR (3) MAJOR
lesser log level numerical code) a generate
MINOR (4) MINOR
a trap. The corresponding NMS receives
informational, warning, and error events.

2-27
Chapter 2
Platform sysObjectIDs

filter-level Field Filter Level Description syslog Level Alarm

Value (Numerical Code) Severity
Levels
ALL The SNMP agent sends a trap for all EMERGENCY (1) EMERGENCY
alarms, syslogs, and other traps. The CRITICAL (2) CRITICAL
corresponding NMS receives informational, MAJOR (3) MAJOR
warning, and error events.
MINOR (4) MINOR
WARNING (5) WARNING
NOTICE (6)
INFO (7)
TRACE (8)
DEBUG (9)

The following table describes the types of events that an NMS can receive.

Event Category Description

Error Indicates a catastrophic condition has occurred (e.g., an internal temperature
reading exceeds the recommendation).
Warning Indicates pending failures or unexpected events (e.g., at the console, you typed
the wrong password three consecutive times)
Informational Represents non-critical conditions (e.g., an event can indicate to an administrator
that a configuration element has changed).

For more information about the filter-level field specifically or the trap-receiver element in
general, refer to the Configuration via the ACLI chapter of the Administration and Configuration
Guide for the ACLI.

Platform sysObjectIDs
Each hardware platform in the Acme Packet 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.

Platform sysObjectID
Acme Packet 3900 apNetNet3900: [Link].4.1.9148.1.3.3
Acme Packet 3950 apNetNet3950: [Link].4.1.9148.1.3.4
Acme Packet 4900 apNetNet4900: [Link].4.1.9148.1.1.4
Acme Packet 4600 apNetNet4600: [Link].4.1.9148.1.1.3
Acme Packet 6100 apNetNet6100: [Link].4.1.9148.1.5.2
Acme Packet 6300 apNetNet6300: [Link].4.1.9148.1.5.1

2-28
3
Standard SNMP GET Requests
This section explains the standard SNMP GET requests supported by the Oracle
Communications Session Border Controller. SNMP uses five basic messages, one of which is
the GET request that is used to query for information on or about a network entity.

Interfaces Object

MIB Object Object ID: [Link].2.1.2 + Description

ifNumber .1 The number of network interfaces
(regardless of their current state)
present on this system.
ifTable .2 A list of interface entries. The
number of entries is given by the
value of ifNumber.

Interface Table
The following table describes the standard SNMP Get support for the interfaces table, which
contains information on the entity's interfaces. Each interface is thought of as being attached to

3-1
Chapter 3
Interfaces Object

a subnetwork. (Note that this term should not be confused with subnet, which refers to an
addressing partitioning scheme used in the Internet suite of protocols.)

3-2
Chapter 3
Interfaces Object

3-3
Chapter 3
Interfaces Object

Interface Description in MIB

The ifDescr object in the ifEntry object in ifTable is a string of up to 255 characters. It
currently contains the name of the interface only. This change adds to the ifDescr string,

3-4
Chapter 3
Interfaces Object

separated from the first part by a space, a keyword that represents the internal interface type.
The values can be {ETH, FE, GE, OC, XE, null}.
RFC 3635 supercedes RFC 2665. RFC 2665 recommends, but RFC 3635 requires, that all
Ethernet-like interfaces use an ifType of ethernetCsmacd (6) regardless of the speed that the
interface is running or the link-layer encapsulation in use. Heretofore, Oracle Communications
Session Border Controllers could return values of fastEthernet (62) and gigaEthernet (117),
but, in accordance with RFC 3635, will now return ethernetCsmacd (6) for all Ethernet interface
types. To let users determine the type of Ethernet interface more readily than by some other
method, Oracle has changed the syntax for ifDescr to include the interface type.
The current values of ifDescr are either the names of physical or network interfaces (for
example, "wancom0", "lo", "s1p0", "Access", or "Core"), or, for sub-interfaces, interface names
appended with sub-interface numbers (for example, "Access.22" or "Core.33"). This change
adds to the ifDescr string, separated from the first part by a space, a keyword that represents
the internal interface type rather than the actual queried value. The current set of possible
values is {ETH, FE, GE, XE, null}.
Examples:
• wancom0 GE
• lo (Second part empty)
• s1p0 GE
• s0p0 XE
• Access GE
• Access.22 (Second part empty)
• Core.33 (Second part empty)

3-5
Chapter 3
ifXTable Table

ifXTable Table
The ifXTable is available to support 64-bit counters for interface statistics. Only Gets are
supported for this MIB Table, and are supported on all interfaces.

3-6
Chapter 3
ifXTable Table

3-7
Chapter 3
ifXTable Table

3-8
Chapter 3
ifXTable Table

3-9
Chapter 3
ip Object

ip Object
The following table describes the standard SNMP Get support for the IP group. Implementation
of the IP group is mandatory for all systems. The IP address table contains this entity's IP
addressing information

3-10
Chapter 3
ip Object

3-11
Chapter 3
ip Object

3-12
Chapter 3
ip Object

ipAddrTable Table
The table of addressing information relevant to this entity's IPv4 addresses.

3-13
Chapter 3
icmp Object

icmp Object
The following table describes the standard SNMP Get support for the Internet Control Message
Protocol (ICMP) group. Implementation of the ICMP group is mandatory for all systems.

MIB Object Object ID: [Link].2.1.5 + Description

icmpInMsgs .1 Total number of ICMP messages
which the entity received. (Note
that this counter includes all
those counted by icmpInErrors.)
icmpInErrors .2 Number of ICMP messages
which the entity received but
determined as having ICMP-
specific errors (bad ICMP
checksums, bad length, and so
on).
icmpInDestUnreachs .3 Number of ICMP Destination
Unreachable messages received.
icmpInTimeExcds .4 Number of ICMP Time Exceeded
messages received.
icmpInParmProbs .5 Number of ICMP Parameter
Problem messages received.
icmpInSrcQuenchs .6 Number of ICMP Source Quench
messages received.
icmpInRedirects .7 Number of ICMP Redirect
messages received.
icmpInEchos .8 Number of ICMP Echo (request)
messages received.
icmpInEchoReps .9 Number of ICMP Echo Reply
messages received.
icmpInTimestamps .10 Number of ICMP Timestamp
(request) messages received.
icmpInTimestampReps .11 Number of ICMP Timestamp
Reply messages received.
icmpInAddrMasks .12 Number of ICMP Address Mask
Request messages received.
icmpInAddrMaskReps .13 Number of ICMP Address Mask
Reply messages received.
icmpOutMsgs .14 Total number of ICMP messages
which this entity attempted to
send. (This counter includes all
those counted by icmpOutErrors.)
icmpOutErrors .15 Number of ICMP messages
which this entity did not send due
to problems discovered within
ICMP such as a lack of buffers.
This value does not include errors
discovered outside the ICMP
layer such as the inability of IP to
route the resultant datagram. In
some implementations there may
be no types of error which
contribute to this counter's value.

3-14
Chapter 3
TCP Object

MIB Object Object ID: [Link].2.1.5 + Description

icmpOutDestUnreachs .16 Number of ICMP Destination
Unreachable messages sent.
icmpOutTimeExcds .17 Number of ICMP Time Exceeded
messages sent.
icmpOutParmProbs .18 Number of ICMP Parameter
Problem messages sent.
icmpOutSrcQuenchs .19 Number of ICMP Source Quench
messages sent.
icmpOutRedirects .20 Number of ICMP Redirect
messages sent. For a host, this
object will always be zero, since
hosts do not send redirects.
icmpOutEchos .21 Number of ICMP Echo (request)
messages sent.
icmpOutEchoReps .22 Number of ICMP Echo Reply
messages sent.
icmpOutTimestamps .23 Number of ICMP Timestamp
(request) messages sent.
icmpOutTimestampReps .24 Number of ICMP Timestamp
Reply messages sent.
icmpOutAddrMasks .25 Number of ICMP Address Mask
Request messages sent.
icmpOutAddrMaskReps .26 Number of ICMP Address Mask
Reply messages sent.

TCP Object
The following table describes the standard SNMP Get support for the TCP connection table,
which contains information about this entity's existing TCP connections.

3-15
Chapter 3
TCP Object

3-16
Chapter 3
UDP Object

tcpConnTable Table
Per connection, [Link]: [Link].[Link].1.x Refer to the following table
for all objects per connection.

MIB Object Object ID: Description

[Link].[Link].1 +
tcpConnState .1 State of this TCP connection. The only value which
may be set by a management station is
deleteTCB(12). Accordingly, it is appropriate for an
agent to return a badValue response if a management
station attempts to set this object to any other value. If
a management station sets this object to the value
deleteTCB(12), then this has the effect of deleting the
TCB (as defined in RFC 793) of the corresponding
connection on the managed node, resulting in
immediate termination of the connection. As an
implementation-specific option, an RST segment may
be sent from the managed node to the other TCP
endpoint (note however that RST segments are not
sent reliably).
tcpConnLocalAddress .2 Local IP address for this TCP connection. In the case
of a connection in the listen state which is willing to
accept connections for any IP interface associated
with the node, the value is [Link].
tcpConnLocalPort .3 Local port number for this TCP connection.
tcpConnRemAddress .4 Remote IP address for this TCP connection.
tcpConnRemPort .5 Remote port number for this TCP connection.

UDP Object
The following table describes the standard SNMP Get support for the UDP group.
Implementation of the UDP group is mandatory for all systems which implement the UDP. The
UDP listener table contains information about this entity's UDP end-points on which a local
application is currently accepting datagrams.

MIB Object Object ID: [Link].2.1.7 + Description

udpInDatagrams .1 Total number of UDP datagrams
delivered to UDP users.

3-17
Chapter 3
System Object

UDP Listener Table

MIB Object Object ID: [Link].[Link] + Description

udpLocalAddress .1 Local IP address for this UDP
listener. In the case of a UDP
listener which is willing to accept
datagrams for any IP interface
associated with the node, the
value is [Link].
updLocalPort .2 Local port number for this UDP
listener.

System Object
The following table describes the standard SNMP Get support for the system group which is a
collection of objects common to all managed systems.

3-18
Chapter 3
System Object

layer functionality
1 physical (for example, repeaters)
2 datalink/subnetwork (for example, bridges)
3 internet (for example, supports IP)
4 end-to-end (for example, supports TCP)
7 applications (for example., supports SMTP)

For systems including OSI protocols, layers 5 and 6 may also be counted.

3-19
Chapter 3
SNMP Object

Object Resource Information Object

The following table describes the standard SNMP Get support for the object resource
information which is a collection of objects which describe the SNMPv2 entity's (statistically
and dynamically configurable) support of various MIB modules.

SNMP Object
The following table describes the standard SNMP Get support for the SNMP group which is a
collection of objects providing basic instrumentation and control of an SNMP entity.

3-20
Chapter 3
Physical Entity Table

Physical Entity Table

Oracle Communications Session Border Controller implements the Physical Entity table from
the Entity MIB (RFC 2737). The following table describes the standard SNMP Get support for
the Entity group, which is a collection of multiple logical entities supported by a single SNMP
agent.

MIB Object Object ID: [Link].[Link].1.1.1 Description

+
entPhysicalIndex .1 The index for this entry.

3-21
Chapter 3
Physical Entity Table

3-22
Chapter 3
Physical Entity Table

3-23
Chapter 3
Physical Entity Table

3-24
Chapter 3
Physical Entity Table

3-25
Chapter 3
Physical Entity Table

3-26
Chapter 3
Physical Entity Table

3-27
Chapter 3
Physical Entity Table

3-28
Chapter 3
Physical Entity Table

3-29
4
Enterprise SNMP GET Requests
This section explains the proprietary enterprise SNMP GET requests supported by the system.
The SNMP GET is used to query for information on or about a network entity.

Applications MIB ([Link])

The Apps mib ([Link]) contains tables related ENUM, DNS, DoS threshold and STIR
statistics and states.

apAppsENUMServerStatusTable Table
The following table all configured ENUM servers' status.

MIB Object Description

apAppsENUMServerStatusEntry Numbered table entry.
[Link].4.1.9148.[Link].1.1.1
apAppsENUMConfigName The name of the enum-config element that
[Link].4.1.9148.[Link].[Link] contains this ENUM server.
apAppsENUMServerInetAddressType The internet address type of this ENUM server.
[Link].4.1.9148.[Link].[Link]
apAppsENUMServerInetAddress The IP address of this ENUM server.
[Link].4.1.9148.[Link].[Link]
apAppsENUMServerStatus The status of this ENUM server.
[Link].4.1.9148.[Link].[Link]

apAppsDnsServerStatusTable
The following table all configured ENUM servers' status.

MIB Object Description

apAppsDnsServerStatusEntry An entry designed to hold the status of a single
[Link].4.1.9148.[Link].2.1.1 DNS server
apAppsDnsInterfaceName The name of the dns interface that contains this
[Link].4.1.9148.[Link].[Link] dns server.
apAppsDnsServerInetAddressType The internet address type of this DNS server.
[Link].4.1.9148.[Link].[Link]
apAppsDnsServerInetAddress The IP address of this DNS server.
[Link].4.1.9148.[Link].[Link]
apAppsDnsServerStatus The status of this DNS server.
[Link].4.1.9148.[Link].[Link]

4-1
Chapter 4
Applications MIB ([Link])

apAppsStirMIBObjects Table
The apAppsStirMIBObjects is an object that consists of all the STIR-related tables. This table
collects and assembles all STIR/SHAKEN MIB data for presentation using SNMP.
Tables within the apAppsStirMIBObjects ([Link].4.1.9148.[Link].4) table include:
• apAppsStirServerTable ([Link].4.1.9148.[Link].4.1), which references:
– apAppsStirServerEntry
– apStirServerIndex
– apStirServerName
• apAppsStirStatsTable ([Link].4.1.9148.[Link].4.2), which references:
– apAppsStirStatsEntry
– apStirStatsServerIndex
– apCounterStatsType
– apStirServerStats
– apStirStatsType
• apAppsStirAgentTable ([Link].4.1.9148.[Link].4.3), which references:
– apAppsStirAgentEntry
– apStirAgentIndex
– apStirAgentName
• apAppsStirAgentStatsTable ([Link].4.1.9148.[Link].4.4), which references:
– apAppsStirAgentStatsEntry
– apStirStatsAgentIndex
– apCounterStatsAgentType
– apStirAgentStatsType
– apStirAgentStats
• apAppsStirSipInterfaceTable ([Link].4.1.9148.[Link].4.5), which references:
– apAppsStirSipInterfaceEntry
– apStirSipInterfaceIndex
– apStirSipInterfaceName
• apAppsStirSipInterfaceStatsTable ([Link].4.1.9148.[Link].4.6), which references:
– apAppsStirSipInterfaceStatsEntry
– apStirStatsSipInterfaceIndex
– apCounterStatsSipInterfaceType
– apStirSipInterfaceStatsType
– apStirSipInterfaceStats
• apAppsStirRealmTable ([Link].4.1.9148.[Link].4.7), which references:
– apAppsStirRealmEntry

4-2
Chapter 4
Applications MIB ([Link])

– apStirRealmIndex
– apStirRealmName
• apAppsStirRealmStatsTable ([Link].4.1.9148.[Link].4.8), which references:
– apAppsStirRealmStatsEntry
– apStirStatsRealmIndex
– apCounterStatsRealmType
– apStirRealmStatsType
– apStirRealmStats
• apAppsStirSystemStatsTable ([Link].4.1.9148.[Link].4.9) , which references:
– apAppsStirSystemStatsEntry
– apCounterStatsSystemType
– apStirSystemStatsType
– apStirSystemStats

apAppsStirServerTable
The table lists STIR server names with object apStirServerName indexed by a persistent index
apStirServerIndex.

apAppsStirServerStatsTable
The following table collects information on all configured STIR servers' status.
The apStirServerName OID is [Link].4.1.9148.[Link].[Link].
The apAppsStirServerStatsTable uses three variables to specify each object, as follows:
1. The first index is the server index.
This component of the SNMP table uses the config-object ID the system creates when you
create the object. The STI server labels are contained in OID APAPPS-
MIB::apStirServerName.
2. The second index is an enumeration of the counter types:
• recent = 1
• total = 2
• permax = 3
3. The third index is the data category.
For example, the apStirServerStats instances have an OID of the form apStirServerStats.x.y.z,
where:
• apStirServerStats is [Link].4.1.9148.[Link].[Link];
• x is the stir server's index;
• y is the ApCounterStatsType (recent = 1, total = 2, or permax = 3)
• z is the data category
Each data category is found within each ApCounterStatsType. The "asQueries" category, for
example, is found within the recent, total, and permax counter types.

4-3
Chapter 4
Applications MIB ([Link])

MIB Object Object ID [Link].4.1.9148.[Link].[Link].x

apStirServerStats.<index>.[Link] 1.1
apStirServerStats.<index>.[Link] 2.1
apStirServerStats.<index>.[Link] 3.1

To find the complete OID for a data category:

1. Start with the OID of apStirServerStats ( [Link].4.1.9148.[Link].[Link])
2. Append your server index (for example, [Link].4.1.9148.[Link].[Link].10).
3. Append your ApCounterStatsType (for example, [Link].4.1.9148.[Link].[Link].10.2)
4. Append your data category (for example, [Link].4.1.9148.[Link].[Link].10.2.1)
OID [Link].4.1.9148.[Link].[Link].10.2.1 gets the total number (ApCounterStatsType = 2)
of queries made to the AS server (data category = 1) for STIR server 10.

MIBs in Release SC-Z9.1.0p9 and later

Data Category Name Data Category Number Description

asQueries .1 Queries made to the named AS
server
asSuccessResponses .2 Successful responses received
from the named AS server
asFailResponses .3 Failed responses received from
the named AS server
asFailServiceException .4 Failed responses received from
the named AS server caused by
a service exception
asFailPolicyException .5 Failed responses received from
the named AS server caused by
a policy exception
vsQueries .6 Queries made to the named VS
server
vsSuccessResponses .7 Successful responses received
from the named VS server
vsFailResponses .8 Successful responses received
from the named VS server
vsSuccessVerification .9 Successful verifications received
from the named VS server
vsFailVerification .10 Failed responses received from
the named VS server indicating
verification failure
vsFailServiceException .11 Failed responses received from
the named VS server caused by
a service exception
vsFailPolicyException .12 Failed responses received from
the named VS server caused by
a policy exception
serverUnreachable .13 Number of unsuccessful attempts
to reach a server
asSentInviteswithShakenPASSpo .14 Sent INVITES that included a
rtA SHAKEN passport with
attestation level A

4-4
Chapter 4
Applications MIB ([Link])

Data Category Name Data Category Number Description

asSentInviteswithShakenPASSpo .15 Sent INVITES that included a
rtB SHAKEN passport with
attestation level B
asSentInviteswithShakenPASSpo .16 Sent INVITES that included a
rtC SHAKEN passport with
attestation level C
asSentInviteswithdivPASSport .17 Sent INVITES that included a DIV
passport
vsReceivedInviteswithNoPASSpo .18 Recevied INVITEs that had no
rt passport
vsReceivedInviteswithShakenPAS .19 Received INVITEs that had at
Sport least one SHAKEN passport
vsReceivedInviteswithDivPASSpo .20 Received INVITEs that had at
rt least one DIV passport
vsSentInviteswithTNValidationPas .21 Sent INVITES that included a TN
sed validation that passed
vsSentInviteswithTNValidationFail .22 Sent INVITES that included a TN
ed validation that failed
vsSentInviteswithNoTNValidation .23 Sent INVITES that included a no
TN validation parameter
asServiceUnreachable .24 Number of unreachable Service
to AS
vsServiceUnreachable .25 Number of unreachable Service
to VS Server
vsInviteRejected .26 Number of calls rejected based
on verstat and reason code from
sti-vs server
apStirStatsTypeMax .27 Marker indicating the end of the
stats types

The apStirStatsTypeMax marks the end of the defined types. No object should have the index
with its value. If an object has this value, the number of the apStirServerStatsType values has
been expanded and either this MIB Guide or the MIB Package should be updated.

MIBs in Release SC-Z9.1.0 through SC-Z9.1.0p8

Data Category Name Data Category Number Description

4-5
Chapter 4
Applications MIB ([Link])

Data Category Name Data Category Number Description

vsSuccessResponses .7 Successful responses received
from the named VS server
vsFailResponses .8 Failed responses received from
the named VS server
vsSuccessVerification .9 Successful verifications received
from the named VS server
vsFailVerification .10 Failed responses received from
the named VS server indicating
verification failure
vsFailServiceException .11 Failed responses received from
the named VS server caused by
a service exception
vsFailPolicyException .12 Failed responses received from
the named VS server caused by
a policy exception
serverUnreachable .13 Number of unsuccessful attempts
to reach a server

apAppsStirAgentStatsTable
The following tables collect information on all configured STIR session agents' status. The
apAppsStirAgentStats reference is the name for all apAppsStirAgentStatsTable stats elements.
The apStirAgentName OID is [Link].4.1.9148.[Link].[Link].
The apAppsStirAgentStatsTable uses three variables to specify each object, as follows:
1. The first index is the STIR session agent index.
This component of the SNMP table uses the config-object ID the system creates when you
create the object. The STI agent labels are contained in OID APAPPS-
MIB::apStirAgentName.
2. The second index is an enumeration of the counter types:
• recent = 1
• total = 2
• permax = 3
3. The third index is the data category.
For example, the apAppsStirAgentStats instances have an OID of the form
apAppsStirAgentStats.x.y.z, where:
• apStirAgentStats is [Link].4.1.9148.[Link].[Link]
• x is the STIR sesion agent's index
• y is the ApCounterStatsType (recent = 1, total = 2, or permax = 3)
• z is the data category
Each data category is found within each ApCounterStatsType. The "asQueries" category, for
example, is found within the recent, total, and permax counter types.

4-6
Chapter 4
Applications MIB ([Link])

MIB Object Object ID [Link].4.1.9148.[Link].[Link].x

apStirAgentStats.<index>.[Link] 1.1
apStirAgentStats.<index>.[Link] 2.1
apStirAgentStats.<index>.[Link] 3.1

To find the complete OID for a data category:

1. Start with the OID of apStirAgentStats ([Link].4.1.9148.[Link].[Link])
2. Append your STIR session agent index (for example, [Link].4.1.9148.[Link].[Link].10).
3. Append your ApCounterStatsType (for example, [Link].4.1.9148.[Link].[Link].10.2)
4. Append your data category (for example, [Link].4.1.9148.[Link].[Link].10.2.1)
OID [Link].4.1.9148.[Link].[Link].10.2.1 gets the total number (ApCounterStatsType = 2)
of queries made to the AS server (data category = 1) for STIR session agent 10.

Data Categories in Release SC-Z9.1.0p9 and later

Data Category Name Data Category Number Description

4-7
Chapter 4
Applications MIB ([Link])

Data Category Name Data Category Number Description

asSentInviteswithShakenPASSpo .15 Sent INVITES that included a
rtB SHAKEN passport with
attestation level B
asSentInviteswithShakenPASSpo .16 Sent INVITES that included a
rtC SHAKEN passport with
attestation level C
asSentInviteswithdivPASSport .17 Sent INVITES that included a DIV
passport
vsReceivedInviteswithNoPASSpo .18 Recevied INVITEs that had no
rt passport
vsReceivedInviteswithShakenPAS .19 Received INVITEs that had at
Sport least one SHAKEN passport
vsReceivedInviteswithDivPASSpo .20 Received INVITEs that had at
rt least one DIV passport
vsSentInviteswithTNValidationPas .21 Sent INVITES that included a TN
sed validation that passed
vsSentInviteswithTNValidationFail .22 Sent INVITES that included a TN
ed validation that failed
vsSentInviteswithNoTNValidation .23 Sent INVITES that included a no
TN validation parameter
vsInviteRejected .26 Number of calls rejected based
on verstat and reason code from
sti-vs server
apStirStatsTypeMax .27 Marker indicating the end of the
stats types

Data Categories in Release SC-Z9.1.0 through SC-Z9.1.0p8

Data Category Name Data Category Number Description

4-8
Chapter 4
Applications MIB ([Link])

Data Category Name Data Category Number Description

vsSuccessVerification .9 Successful verifications received
from the named VS server
vsFailVerification .10 Failed responses received from
the named VS server indicating
verification failure
vsFailServiceException .11 Failed responses received from
the named VS server caused by
a service exception
vsFailPolicyException .12 Failed responses received from
the named VS server caused by
a policy exception

apAppsStirSipInterfaceStatsTable
The following table collects information on all configured sip-interface status. The
apStirSipInterfaceStats reference is the name for all apAppsStirSipInterfaceStatsTable stats
elements.
The apStirSipInterfaceName OID is [Link].4.1.9148.[Link].[Link].
The apAppsStirSipInterfaceStatsTable uses three variables to specify each object, as follows:
1. The first index is the sip-interface index.
This component of the SNMP table uses the config-object ID the system creates when you
create the object. The STI labels are contained in OID APAPPS-
MIB::apStirSipInterfaceName.
2. The second index is an enumeration of the counter types:
• recent = 1
• total = 2
• permax = 3
3. The third index is the data category.
For example, the apStirSipInterfaceStats instances have an OID of the form
apAppsStirSipInterfaceStats.x.y.z, where:
• apAppsStirSipInterfaceStats is [Link].4.1.9148.[Link].[Link]
• x is the sip-interface index
• y is the ApCounterStatsType (recent = 1, total = 2, or permax = 3)
• z is the data category
Each data category is found within each ApCounterStatsType. The "asQueries" category, for
example, is found within the recent, total, and permax counter types.

MIB Object Object ID [Link].4.1.9148.[Link].[Link].x

apAppsStirSipInterfaceStats.<index>.[Link] 1.1
ries

4-9
Chapter 4
Applications MIB ([Link])

MIB Object Object ID [Link].4.1.9148.[Link].[Link].x

apAppsStirSipInterfaceStats.<index>.[Link] 2.1
es
apAppsStirSipInterfaceStats.<index>.[Link] 3.1
eries

To find the complete OID for a data category:

1. Start with the OID of apStirSipInterfaceStats ([Link].4.1.9148.[Link].[Link])
2. Append your sip-interface index (for example, [Link].4.1.9148.[Link].[Link].3).
3. Append your ApCounterStatsType (for example, [Link].4.1.9148.[Link].[Link].3.2)
4. Append your data category (for example, [Link].4.1.9148.[Link].[Link].3.2.1)
OID [Link].4.1.9148.[Link].[Link].3.2.1 gets the total number (ApCounterStatsType = 2) of
queries made to the AS server (data category = 1) for sip-interface 3.

Data Categories in Release SC-Z9.1.0p9 and later

Data Category Name Data Category Number Description

4-10
Chapter 4
Applications MIB ([Link])

Data Category Name Data Category Number Description

asSentInviteswithShakenPASSpo .15 Sent INVITES that included a
rtB SHAKEN passport with
attestation level B
asSentInviteswithShakenPASSpo .16 Sent INVITES that included a
rtC SHAKEN passport with
attestation level C
asSentInviteswithdivPASSport .17 Sent INVITES that included a DIV
passport
vsReceivedInviteswithNoPASSpo .18 Recevied INVITEs that had no
rt passport
vsReceivedInviteswithShakenPAS .19 Received INVITEs that had at
Sport least one SHAKEN passport
vsReceivedInviteswithDivPASSpo .20 Received INVITEs that had at
rt least one DIV passport
vsSentInviteswithTNValidationPas .21 Sent INVITES that included a TN
sed validation that passed
vsSentInviteswithTNValidationFail .22 Sent INVITES that included a TN
ed validation that failed
vsSentInviteswithNoTNValidation .23 Sent INVITES that included a no
TN validation parameter
vsInviteRejected .26 Number of calls rejected based
on verstat and reason code from
sti-vs server
apStirStatsTypeMax .27 Marker indicating the end of the
stats types

Data Categories in Release SC-Z9.1.0 through SC-Z9.1.0p8

Data Category Name Data Category Number Description

4-11
Chapter 4
Applications MIB ([Link])

Data Category Name Data Category Number Description

apAppsStirRealmStatsTable
The following table collects information on all configured STIR realm' status. The
apRealmServerStats reference is the name for all apAppsStirRealmStatsTable stats elements.
The apStirRealmName OID is [Link].4.1.9148.[Link].[Link].
The apAppsStirRealmStatsTable uses three variables to specify each object, as follows:
1. The first index is the realm index.
This component of the SNMP table uses the config-object ID the system creates when you
create the object. The STI labels are contained in OID APAPPS-MIB::apStirRealmName.
2. The second index is an enumeration of the counter types:
• recent = 1
• total = 2
• permax = 3
3. The third index is the data category.
For example, the apAppsStirRealmStats instances have an OID of the form
apAppsRealmServerStats.x.y.z, where:
• apStirRealmStats is [Link].4.1.9148.[Link].[Link]
• x is the realm index
• y is the ApCounterStatsType (recent = 1, total = 2, or permax = 3)
• z is the data category
Each data category is found within each ApCounterStatsType. The "asQueries" category, for
example, is found within the recent, total, and permax counter types.

MIB Object Object ID [Link].4.1.9148.[Link].[Link].x

apStirRealmStats.<index>.[Link] 1.1
apStirRealmStats.<index>.[Link] 2.1
apStirRealmStats.<index>.[Link] 3.1

To find the complete OID for a data category:

1. Start with the OID of apStirRealmStats ([Link].4.1.9148.[Link].[Link])
2. Append your realm index (for example, [Link].4.1.9148.[Link].[Link].3).

4-12
Chapter 4
Applications MIB ([Link])

3. Append your ApCounterStatsType (for example, [Link].4.1.9148.[Link].[Link].3.2)

4. Append your data category (for example, [Link].4.1.9148.[Link].[Link].3.2.1)
OID [Link].4.1.9148.[Link].[Link].3.2.1 gets the total number (ApCounterStatsType = 2) of
queries made to the AS server (data category = 1) for realm 3.

MIBs in Release SC-Z9.1.0p9 and later

Data Category Name Data Category Number Description

asQueries .1 Queries made to the named AS
server
asSuccessResponses .2 Successful responses received
from the named AS server
asFailResponses .3 Failed responses received from
the named AS server
asFailServiceException .4 Failed responses received from
the named AS server caused by
a service exception
asFailPolicyException .5 Failed responses received from
the named AS server caused by
a policy exception
vsQueries .6 Queries made to the named VS
server
vsSuccessResponses .7 Successful responses received
from the named VS server
vsFailResponses .8 Successful responses received
from the named VS server
vsSuccessVerification .9 Successful verifications received
from the named VS server
vsFailVerification .10 Failed responses received from
the named VS server indicating
verification failure
vsFailServiceException .11 Failed responses received from
the named VS server caused by
a service exception
vsFailPolicyException .12 Failed responses received from
the named VS server caused by
a policy exception
asSentInviteswithShakenPASSpo .14 Sent INVITES that included a
rtA SHAKEN passport with
attestation level A
asSentInviteswithShakenPASSpo .15 Sent INVITES that included a
rtB SHAKEN passport with
attestation level B
asSentInviteswithShakenPASSpo .16 Sent INVITES that included a
rtC SHAKEN passport with
attestation level C
asSentInviteswithdivPASSport .17 Sent INVITES that included a DIV
passport
vsReceivedInviteswithNoPASSpo .18 Recevied INVITEs that had no
rt passport
vsReceivedInviteswithShakenPAS .19 Received INVITEs that had at
Sport least one SHAKEN passport
vsReceivedInviteswithDivPASSpo .20 Received INVITEs that had at
rt least one DIV passport

4-13
Chapter 4
Applications MIB ([Link])

Data Category Name Data Category Number Description

vsSentInviteswithTNValidationPas .21 Sent INVITES that included a TN
sed validation that passed
vsSentInviteswithTNValidationFail .22 Sent INVITES that included a TN
ed validation that failed
vsSentInviteswithNoTNValidation .23 Sent INVITES that included a no
TN validation parameter
vsInviteRejected .26 Number of calls rejected based
on verstat and reason code from
sti-vs server
apStirStatsTypeMax .27 Marker indicating the end of the
stats types

MIBs in Release SC-Z9.1.0 through SC-Z9.1.0p8

Data Category Name Data Category Number Description

4-14
Chapter 4
Applications MIB ([Link])

apAppsStirSystemStatsTable
The following table collects information on the system's status. The apStirSystemStats
reference is the name for all apAppsStirSystemStatsTable stats elements.
The apAppsStirSystemStatsTable uses two variables to specify its data, as follows:
1. The first is an enumeration of the counter types:
• recent = 1
• total = 2
• permax = 3
2. The second is the data category.
For example, the apStirSystemStats instances have an OID of the form apStirSystemStats.y.z,
where:
• y is the ApCounterStatsType (recent = 1, total = 2, or permax = 3)
• z is the data category
Each data category is found within each ApCounterStatsType. The "asQueries" category, for
example, is found within the recent, total, and permax counter types.

MIB Object Object ID [Link].4.1.9148.[Link].[Link]

[Link] 1.1
[Link] 2.1
[Link] 3.1

To find the complete OID for a data category:

1. Start with the OID of apStirSystemStats ([Link].4.1.9148.[Link].[Link])
2. Append your ApCounterStatsType (for example, [Link].4.1.9148.[Link].[Link].2)
3. Append your data category (for example, [Link].4.1.9148.[Link].[Link].2.1)
OID1.[Link].1.9148.[Link].[Link].2.1 gets the total number (ApCounterStatsType = 2) of
queries made to the AS server (data category = 1) for the system.

MIBs in Release SC-Z9.1.0p9 and later

Data Category Name Data Category Number Description

4-15
Chapter 4
Applications MIB ([Link])

Data Category Name Data Category Number Description

vsQueries .6 Queries made to the named VS
server
vsSuccessResponses .7 Successful responses received
from the named VS server
vsFailResponses .8 Successful responses received
from the named VS server
vsSuccessVerification .9 Successful verifications received
from the named VS server
vsFailVerification .10 Failed responses received from
the named VS server indicating
verification failure
vsFailServiceException .11 Failed responses received from
the named VS server caused by
a service exception
vsFailPolicyException .12 Failed responses received from
the named VS server caused by
a policy exception
asSentInviteswithShakenPASSpo .14 Sent INVITES that included a
rtA SHAKEN passport with
attestation level A
asSentInviteswithShakenPASSpo .15 Sent INVITES that included a
rtB SHAKEN passport with
attestation level B
asSentInviteswithShakenPASSpo .16 Sent INVITES that included a
rtC SHAKEN passport with
attestation level C
asSentInviteswithdivPASSport .17 Sent INVITES that included a DIV
passport
vsReceivedInviteswithNoPASSpo .18 Recevied INVITEs that had no
rt passport
vsReceivedInviteswithShakenPAS .19 Received INVITEs that had at
Sport least one SHAKEN passport
vsReceivedInviteswithDivPASSpo .20 Received INVITEs that had at
rt least one DIV passport
vsSentInviteswithTNValidationPas .21 Sent INVITES that included a TN
sed validation that passed
vsSentInviteswithTNValidationFail .22 Sent INVITES that included a TN
ed validation that failed
vsSentInviteswithNoTNValidation .23 Sent INVITES that included a no
TN validation parameter
vsInviteRejected .26 Number of calls rejected based
on verstat and reason code from
sti-vs server
apStirStatsTypeMax .27 Marker indicating the end of the
stats types

4-16
Chapter 4
Applications MIB ([Link])

MIBs in Release SC-Z9.1.0 through SC-Z9.1.0p8

Data Category Name Data Category Number Description

apDosThresholdCountersGroup
The following group includes all configured DoS threshold counters.

SNMP MIB
[Link]
apDosThresholdCountersGroup
[Link].4.1.9148.3.16.5

This table lists and describes the apDosThresholdCountersGroup MIB objects. To form the
OID, add [Link].4.1.9148.3.16.5 to the value in the OID # column. The OID for Trusted Minor
Counter, for example, is [Link].4.1.9148.[Link].

MIB Object Object ID Description

[Link].4.1.9148.3.16.5 +
apDosTrustedMinorCounter .1 Counter incremented, when
trusted bandwidth crossed the
minor threshold percentage

4-17
Chapter 4
Applications MIB ([Link])

MIB Object Object ID Description

[Link].4.1.9148.3.16.5 +
apDosTrustedMajorCounter .2 Counter incremented, when
trusted bandwidth crossed the
major threshold percentage
apDosTrustedCriticalCounter .3 Counter incremented, when
trusted bandwidth crossed the
critical threshold percentage
apDosUntrustedMinorCounter .4 Counter incremented, when
untrusted bandwidth crossed the
minor threshold percentage
apDosUntrustedMajorCounter .5 Counter incremented, when
untrusted bandwidth crossed the
major threshold percentage
apDosUntrustedCriticalCounter .6 Counter incremented, when
untrusted bandwidth crossed the
critical threshold percentage
apDosArpMinorCounter .7 Counter incremented, when ARP
bandwidth crossed the minor
threshold percentage
apDosArpMajorCounter .8 Counter incremented, when ARP
bandwidth crossed the major
threshold percentage
apDosArpCriticalCounter .9 Counter incremented, when ARP
bandwidth crossed the critical
threshold percentage

MSRP MIB Objects

The following tables describe the SNMP MSRP Get query objects for the SIP MIB (ap-
[Link]). There are two categories, including system-wide statistics and realm specific
statistics:
• MSRP System Objects—These OIDs append to apMSRPKPISystemStats
([Link].4.1.9148.[Link].[Link].*). These OIDs are within [Link] under the
package apAppsMSRPKPISystemStatsTable.
• MSRP Realm Objects—These OIDs append to apMSRPKPIRealmStats
([Link].4.1.9148.[Link].[Link].*). These OIDs are within [Link] under the
package apAppsMSRPKPIRealmTable.

System Level Objects

The table below lists and describes the GET query names for MSRP Extended system KPI
Objects when reporting on the system.

GET Query Name Object IDs: Description

[Link].4.1.9148.[Link].[Link].
(counter type).+
msrp-AvgSENDTransTx 1 The average number of MSRP
SEND transactions transmitted by
the SBC per session

4-18
Chapter 4
Applications MIB ([Link])

GET Query Name Object IDs: Description

[Link].4.1.9148.[Link].[Link].
(counter type).+
msrp-AvgChatSENDTransTx 2 The average number of CHAT
message SEND transactions
transmitted by the SBC per
session
msrp-AvgIsTypingSENDTransTx 3 The average number of IsTyping
message SEND transactions
transmitted by the SBC per
session
msrp-AvgReceiptSENDTransTx 4 The average number of Receipt
message SEND transactions
transmitted by the SBC per
session
msrp-AvgSENDMsgBytesTx 5 The average number of bytes in
SEND transactions transmitted by
the SBC per session
msrp-AvgChatSENDMsgBytesTx 6 The average number of bytes in
CHAT message SEND
transactions transmitted by the
SBC per session
msrp- 7 The average number of bytes in
AvgIsTypingSENDMsgBytesTx IsTyping message SEND
transactions transmitted by the
SBC per session
msrp- 8 The average number of bytes in
AvgReceiptSENDMsgBytesTx Receipt message SEND
transactions transmitted by the
SBC per session
msrp-SENDMsgBytesTx 9 The number of bytes in MSRP
SEND transactions transmitted by
the SBC
msrp-ChatSENDMsgBytesTx 10 The number of bytes in Chat
message SEND transactions
transmitted by the SBC
msrp-IsTypingMsgBytesTx 11 The number of bytes in IsTyping
message SEND transactions
transmitted by the SBC
msrp-ReceiptMsgBytesTx 12 The number of bytes in Receipt
message SEND transactions
transmitted by the SBC
msrp-SuccessREPORTTransTx 13 The number of Success Reports
transmitted by the SBC
msrp-FailureREPORTTransTx 14 The number of Failure Reports
transmitted by the SBC
msrp- 15 The average number of bytes in
AvgSuccessREPORTMsgBytesT Success Reports transmitted by
x the SBC per session
msrp-AvgREPORTFailureBytesTx 16 The average number of bytes in
Failure Reports transmitted by the
SBC per session
msrp-AvgREPORTFailureRateTx 17 The average number of Success
and Failure Reports that were
Failure Reports transmitted by the
SBC

4-19
Chapter 4
Applications MIB ([Link])

GET Query Name Object IDs: Description

[Link].4.1.9148.[Link].[Link].
(counter type).+
msrp- 18 The average number of Success
AvgREPORTSuccessRateTx and Failure Reports that were
Success Reports transmitted by
the SBC
msrp-REPORTResp400Tx 19 The total number of Report
responses that were 400
messages transmitted by the
SBC
msrp-REPORTResp401Tx 20 The total number of Report
responses that were 401
messages transmitted by the
SBC
msrp-REPORTResp403Tx 21 The total number of Report
responses that were 403
messages transmitted by the
SBC
msrp-REPORTResp404Tx 22 The total number of Report
responses that were 404
messages transmitted by the
SBC
msrp-REPORTResp408Tx 23 The total number of Report
responses that were 408
messages transmitted by the
SBC
msrp-REPORTResp413Tx 24 The total number of Report
responses that were 413
messages transmitted by the
SBC
msrp-REPORTResp415Tx 25 The total number of Report
responses that were 415
messages transmitted by the
SBC
msrp-REPORTResp423Tx 26 The total number of Report
responses that were 423
messages transmitted by the
SBC
msrp-REPORTResp424Tx 27 The total number of Report
responses that were 424
messages transmitted by the
SBC
msrp-REPORTResp425Tx 28 The total number of Report
responses that were 425
messages transmitted by the
SBC
msrp-REPORTResp428Tx 29 The total number of Report
responses that were 428
messages transmitted by the
SBC
msrp-REPORTResp481Tx 30 The total number of Report
responses that were 481
messages transmitted by the
SBC

4-20
Chapter 4
Applications MIB ([Link])

GET Query Name Object IDs: Description

[Link].4.1.9148.[Link].[Link].
(counter type).+
msrp-REPORTResp501Tx 31 The total number of Report
responses that were 501
messages transmitted by the
SBC
msrp-REPORTResp506Tx 32 The total number of Report
responses that were 506
messages transmitted by the
SBC
msrp- 33 The average number of bytes in
AvgREPORTFailureBytes400Tx 400 Report Failure messages
transmitted by the SBC
msrp- 34 The average number of bytes in
AvgREPORTFailureBytes401Tx 401 Report Failure messages
transmitted by the SBC
msrp- 35 The average number of bytes in
AvgREPORTFailureBytes403Tx 403 Report Failure messages
transmitted by the SBC
msrp- 36 The average number of bytes in
AvgREPORTFailureBytes404Tx 404 Report Failure messages
transmitted by the SBC
msrp- 37 The average number of bytes in
AvgREPORTFailureBytes408Tx 408 Report Failure messages
transmitted by the SBC
msrp- 38 The average number of bytes in
AvgREPORTFailureBytes413Tx 413 Report Failure messages
transmitted by the SBC
msrp- 39 The average number of bytes in
AvgREPORTFailureBytes415Tx 415 Report Failure messages
transmitted by the SBC
msrp- 40 The average number of bytes in
AvgREPORTFailureBytes423Tx 423 Report Failure messages
transmitted by the SBC
msrp- 41 The average number of bytes in
AvgREPORTFailureBytes424Tx 424 Report Failure messages
transmitted by the SBC
msrp- 42 The average number of bytes in
AvgREPORTFailureBytes425Tx 425 Report Failure messages
transmitted by the SBC
msrp- 43 The average number of bytes in
AvgREPORTFailureBytes428Tx 428 Report Failure messages
transmitted by the SBC
msrp- 44 The average number of bytes in
AvgREPORTFailureBytes481Tx 481 Report Failure messages
transmitted by the SBC
msrp- 45 The average number of bytes in
AvgREPORTFailureBytes501Tx 501 Report Failure messages
transmitted by the SBC
msrp- 46 The average number of bytes in
AvgREPORTFailureBytes506Tx 506 Report Failure messages
transmitted by the SBC
msrp-TransResponsesTx 47 The total number of Responses
transmitted by the SBC

4-21
Chapter 4
Applications MIB ([Link])

GET Query Name Object IDs: Description

[Link].4.1.9148.[Link].[Link].
(counter type).+
msrp-SuccessTransResponsesTx 48 The total number of Success
Responses transmitted by the
SBC
msrp-TransResp400Tx 49 The total number of 400
Responses transmitted by the
SBC
msrp-TransResp401Tx 50 The total number of 401
Responses transmitted by the
SBC
msrp-TransResp403Tx 51 The total number of 403
Responses transmitted by the
SBC
msrp-TransResp404Tx 52 The total number of 404
Responses transmitted by the
SBC
msrp-TransResp408Tx 53 The total number of 408
Responses transmitted by the
SBC
msrp-TransResp413Tx 54 The total number of 413
Responses transmitted by the
SBC
msrp-TransResp415Tx 55 The total number of 415
Responses transmitted by the
SBC
msrp-TransResp423Tx 56 The total number of 423
Responses transmitted by the
SBC
msrp-TransResp424Tx 57 The total number of 424
Responses transmitted by the
SBC
msrp-TransResp425Tx 58 The total number of 425
Responses transmitted by the
SBC
msrp-TransResp428Tx 59 The total number of 428
Responses transmitted by the
SBC
msrp-TransResp481Tx 60 The total number of 481
Responses transmitted by the
SBC
msrp-TransResp501Tx 61 The total number of 501
Responses transmitted by the
SBC
msrp-TransResp506Tx 62 The total number of 506
Responses transmitted by the
SBC
msrp-AvgSENDTransRx 63 The average number of MSRP
SEND transactions received by
the SBC per session
msrp-AvgChatSENDTransRx 64 The average number of CHAT
message SEND transactions
received by the SBC per session

4-22
Chapter 4
Applications MIB ([Link])

GET Query Name Object IDs: Description

[Link].4.1.9148.[Link].[Link].
(counter type).+
msrp-AvgIsTypingSENDTransRx 65 The average number of IsTyping
message SEND transactions
received by the SBC per session
msrp-AvgReceiptSENDTransRx 66 The average number of Receipt
message SEND transactions
received by the SBC per session
msrp-AvgSENDMsgBytesRx 67 The average number of bytes in
SEND transactions received by
the SBC per session
msrp-AvgChatSENDMsgBytesRx 68 The average number of bytes in
Chat message SEND
transactions received by the SBC
per session
msrp- 69 The average number of bytes in
AvgIsTypingSENDMsgBytesRx IsTyping message SEND
transactions received by the SBC
per session
msrp- 70 The average number of bytes in
AvgReceiptSENDMsgBytesRx Receipt message SEND
transactions received by the SBC
per session
msrp-SENDMsgBytesRx 71 The number of bytes in MSRP
SEND transactions received by
the SBC
msrp-ChatSENDMsgBytesRx 72 The number of bytes in Chat
message SEND transactions
received by the SBC
msrp-IsTypingMsgBytesRx 73 The number of bytes in IsTyping
message SEND transactions
received by the SBC
msrp-ReceiptMsgBytesRx 74 The number of bytes in Receipt
message SEND transactions
received by the SBC
msrp-SuccessREPORTTransRx 75 The number of Success Reports
received by the SBC
msrp-FailureREPORTTransRx 76 The number of Failure Reports
received by the SBC
msrp- 77 The average number of bytes in
AvgSuccessREPORTMsgBytesR Success Reports received by the
x SBC per session
msrp- 78 The average number of bytes in
AvgREPORTFailureBytesRx Success Reports received by the
SBC per session
msrp-AvgREPORTFailureRateRx 79 The average number of Reports
received by the SBC that were
Failure Reports
msrp- 80 The average number of Reports
AvgREPORTSuccessRateRx received by the SBC that were
Success Reports
msrp-REPORTResp400Rx 81 The total number of Report
responses conveying 400
messages received by the SBC

4-23
Chapter 4
Applications MIB ([Link])

GET Query Name Object IDs: Description

[Link].4.1.9148.[Link].[Link].
(counter type).+
msrp-REPORTResp401Rx 82 The total number of Report
responses conveying 401
messages received by the SBC
msrp-REPORTResp403Rx 83 The total number of Report
responses conveying 403
messages received by the SBC
msrp-REPORTResp404Rx 84 The total number of Report
responses conveying 404
messages received by the SBC
msrp-REPORTResp408Rx 85 The total number of Report
responses conveying 408
messages received by the SBC
msrp-REPORTResp413Rx 86 The total number of Report
responses conveying 413
messages received by the SBC
msrp-REPORTResp415Rx 87 The total number of Report
responses conveying 415
messages received by the SBC
msrp-REPORTResp423Rx 88 The total number of Report
responses conveying 423
messages received by the SBC
msrp-REPORTResp424Rx 89 The total number of Report
responses conveying 424
messages received by the SBC
msrp-REPORTResp425Rx 90 The total number of Report
responses conveying 425
messages received by the SBC
msrp-REPORTResp428Rx 91 The total number of Report
responses conveying 428
messages received by the SBC
msrp-REPORTResp481Rx 92 The total number of Report
responses conveying 481
messages received by the SBC
msrp-REPORTResp501Rx 93 The total number of Report
responses conveying 501
messages received by the SBC
msrp-REPORTResp506Rx 94 The total number of Report
responses conveying 506
messages received by the SBC
msrp- 95 The average number of Failure
AvgREPORTFailureBytes400Rx Report bytes conveying 400
messages received by the SBC
per session
msrp- 96 The average number of Failure
AvgREPORTFailureBytes401Rx Report bytes conveying 401
messages received by the SBC
per session
msrp- 97 The average number of Failure
AvgREPORTFailureBytes403Rx Report bytes conveying 403
messages received by the SBC
per session

4-24
Chapter 4
Applications MIB ([Link])

GET Query Name Object IDs: Description

[Link].4.1.9148.[Link].[Link].
(counter type).+
msrp- 98 The average number of Failure
AvgREPORTFailureBytes404Rx Report bytes conveying 404
messages received by the SBC
per session
msrp- 99 The average number of Failure
AvgREPORTFailureBytes408Rx Report bytes conveying 408
messages received by the SBC
per session
msrp- 100 The average number of Failure
AvgREPORTFailureBytes413Rx Report bytes conveying 413
messages received by the SBC
per session
msrp- 101 The average number of Failure
AvgREPORTFailureBytes415Rx Report bytes conveying 415
messages received by the SBC
per session
msrp- 102 The average number of Failure
AvgREPORTFailureBytes423Rx Report bytes conveying 423
messages received by the SBC
per session
msrp- 103 The average number of Failure
AvgREPORTFailureBytes424Rx Report bytes conveying 424
messages received by the SBC
per session
msrp- 104 The average number of Failure
AvgREPORTFailureBytes425Rx Report bytes conveying 425
messages received by the SBC
per session
msrp- 105 The average number of Failure
AvgREPORTFailureBytes428Rx Report bytes conveying 428
messages received by the SBC
per session
msrp- 106 The average number of Failure
AvgREPORTFailureBytes481Rx Report bytes conveying 481
messages received by the SBC
per session
msrp- 107 The average number of Failure
AvgREPORTFailureBytes501Rx Report bytes conveying 501
messages received by the SBC
per session
msrp- 108 The average number of Failure
AvgREPORTFailureBytes506Rx Report bytes conveying 506
messages received by the SBC
per session
msrp-TransResponsesRx 109 The total number of Response
transactions received by the SBC
msrp-SuccessTransResponsesRx 110 The total number of Success
Response transactions received
by the SBC
msrp-TransResp400Rx 111 The total number of Response
transactions conveying 400
messages received by the SBC

4-25
Chapter 4
Applications MIB ([Link])

GET Query Name Object IDs: Description

[Link].4.1.9148.[Link].[Link].
(counter type).+
msrp-TransResp401Rx 112 The total number of Response
transactions conveying 401
messages received by the SBC
msrp-TransResp403Rx 113 The total number of Response
transactions conveying 403
messages received by the SBC
msrp-TransResp404Rx 114 The total number of Response
transactions conveying 404
messages received by the SBC
msrp-TransResp408Rx 115 The total number of Response
transactions conveying 408
messages received by the SBC
msrp-TransResp413Rx 116 The total number of Response
transactions conveying 413
messages received by the SBC
msrp-TransResp415Rx 117 The total number of Response
transactions conveying 415
messages received by the SBC
msrp-TransResp423Rx 118 The total number of Response
transactions conveying 423
messages received by the SBC
msrp-TransResp424Rx 119 The total number of Response
transactions conveying 424
messages received by the SBC
msrp-TransResp425Rx 120 The total number of Response
transactions conveying 425
messages received by the SBC
msrp-TransResp428Rx 121 The total number of Response
transactions conveying 428
messages received by the SBC
msrp-TransResp481Rx 122 The total number of Response
transactions conveying 481
messages received by the SBC
msrp-TransResp501Rx 123 The total number of Response
transactions conveying 501
messages received by the SBC
msrp-TransResp506Rx 124 The total number of Response
transactions conveying 506
messages received by the SBC

Realm Level Objects

The table below lists and describes the GET query names for MSRP Extended system KPI
Objects when reporting on realms.

GET Query Name Object IDs: Description

[Link].4.1.9148.[Link].[Link].
(realm ID).(counter type).+
msrp-AvgSENDTransTx 1 The average number of MSRP
SEND transactions transmitted by
the SBC per session

4-26
Chapter 4
Applications MIB ([Link])

GET Query Name Object IDs: Description

[Link].4.1.9148.[Link].[Link].
(realm ID).(counter type).+
msrp-AvgChatSENDTransTx 2 The average number of CHAT
message SEND transactions
transmitted by the SBC per
session
msrp-AvgIsTypingSENDTransTx 3 The average number of IsTyping
message SEND transactions
transmitted by the SBC per
session
msrp-AvgReceiptSENDTransTx 4 The average number of Receipt
message SEND transactions
transmitted by the SBC per
session
msrp-AvgSENDMsgBytesTx 5 The average number of bytes in
SEND transactions transmitted by
the SBC per session
msrp-AvgChatSENDMsgBytesTx 6 The average number of bytes in
CHAT message SEND
transactions transmitted by the
SBC per session
msrp- 7 The average number of bytes in
AvgIsTypingSENDMsgBytesTx IsTyping message SEND
transactions transmitted by the
SBC per session
msrp- 8 The average number of bytes in
AvgReceiptSENDMsgBytesTx Receipt message SEND
transactions transmitted by the
SBC per session
msrp-SENDMsgBytesTx 9 The number of bytes in MSRP
SEND transactions transmitted by
the SBC
msrp-ChatSENDMsgBytesTx 10 The number of bytes in Chat
message SEND transactions
transmitted by the SBC
msrp-IsTypingMsgBytesTx 11 The number of bytes in IsTyping
message SEND transactions
transmitted by the SBC
msrp-ReceiptMsgBytesTx 12 The number of bytes in Receipt
message SEND transactions
transmitted by the SBC
msrp-SuccessREPORTTransTx 13 The number of Success Reports
transmitted by the SBC
msrp-FailureREPORTTransTx 14 The number of Failure Reports
transmitted by the SBC
msrp- 15 The average number of bytes in
AvgSuccessREPORTMsgBytesT Success Reports transmitted by
x the SBC per session
msrp-AvgREPORTFailureBytesTx 16 The average number of bytes in
Failure Reports transmitted by the
SBC per session
msrp-AvgREPORTFailureRateTx 17 The average number of Success
and Failure Reports that were
Failure Reports transmitted by the
SBC

4-27
Chapter 4
Applications MIB ([Link])

GET Query Name Object IDs: Description

[Link].4.1.9148.[Link].[Link].
(realm ID).(counter type).+
msrp- 18 The average number of Success
AvgREPORTSuccessRateTx and Failure Reports that were
Success Reports transmitted by
the SBC
msrp-REPORTResp400Tx 19 The total number of Report
responses that were 400
messages transmitted by the
SBC
msrp-REPORTResp401Tx 20 The total number of Report
responses that were 401
messages transmitted by the
SBC
msrp-REPORTResp403Tx 21 The total number of Report
responses that were 403
messages transmitted by the
SBC
msrp-REPORTResp404Tx 22 The total number of Report
responses that were 404
messages transmitted by the
SBC
msrp-REPORTResp408Tx 23 The total number of Report
responses that were 408
messages transmitted by the
SBC
msrp-REPORTResp413Tx 24 The total number of Report
responses that were 413
messages transmitted by the
SBC
msrp-REPORTResp415Tx 25 The total number of Report
responses that were 415
messages transmitted by the
SBC
msrp-REPORTResp423Tx 26 The total number of Report
responses that were 423
messages transmitted by the
SBC
msrp-REPORTResp424Tx 27 The total number of Report
responses that were 424
messages transmitted by the
SBC
msrp-REPORTResp425Tx 28 The total number of Report
responses that were 425
messages transmitted by the
SBC
msrp-REPORTResp428Tx 29 The total number of Report
responses that were 428
messages transmitted by the
SBC
msrp-REPORTResp481Tx 30 The total number of Report
responses that were 481
messages transmitted by the
SBC

4-28
Chapter 4
Applications MIB ([Link])

GET Query Name Object IDs: Description

[Link].4.1.9148.[Link].[Link].
(realm ID).(counter type).+
msrp-REPORTResp501Tx 31 The total number of Report
responses that were 501
messages transmitted by the
SBC
msrp-REPORTResp506Tx 32 The total number of Report
responses that were 506
messages transmitted by the
SBC
msrp- 33 The average number of bytes in
AvgREPORTFailureBytes400Tx 400 Report Failure messages
transmitted by the SBC
msrp- 34 The average number of bytes in
AvgREPORTFailureBytes401Tx 401 Report Failure messages
transmitted by the SBC
msrp- 35 The average number of bytes in
AvgREPORTFailureBytes403Tx 403 Report Failure messages
transmitted by the SBC
msrp- 36 The average number of bytes in
AvgREPORTFailureBytes404Tx 404 Report Failure messages
transmitted by the SBC
msrp- 37 The average number of bytes in
AvgREPORTFailureBytes408Tx 408 Report Failure messages
transmitted by the SBC
msrp- 38 The average number of bytes in
AvgREPORTFailureBytes413Tx 413 Report Failure messages
transmitted by the SBC
msrp- 39 The average number of bytes in
AvgREPORTFailureBytes415Tx 415 Report Failure messages
transmitted by the SBC
msrp- 40 The average number of bytes in
AvgREPORTFailureBytes423Tx 423 Report Failure messages
transmitted by the SBC
msrp- 41 The average number of bytes in
AvgREPORTFailureBytes424Tx 424 Report Failure messages
transmitted by the SBC
msrp- 42 The average number of bytes in
AvgREPORTFailureBytes425Tx 425 Report Failure messages
transmitted by the SBC
msrp- 43 The average number of bytes in
AvgREPORTFailureBytes428Tx 428 Report Failure messages
transmitted by the SBC
msrp- 44 The average number of bytes in
AvgREPORTFailureBytes481Tx 481 Report Failure messages
transmitted by the SBC
msrp- 45 The average number of bytes in
AvgREPORTFailureBytes501Tx 501 Report Failure messages
transmitted by the SBC
msrp- 46 The average number of bytes in
AvgREPORTFailureBytes506Tx 506 Report Failure messages
transmitted by the SBC
msrp-TransResponsesTx 47 The total number of Responses
transmitted by the SBC

4-29
Chapter 4
Applications MIB ([Link])

GET Query Name Object IDs: Description

[Link].4.1.9148.[Link].[Link].
(realm ID).(counter type).+
msrp-SuccessTransResponsesTx 48 The total number of Success
Responses transmitted by the
SBC
msrp-TransResp400Tx 49 The total number of 400
Responses transmitted by the
SBC
msrp-TransResp401Tx 50 The total number of 401
Responses transmitted by the
SBC
msrp-TransResp403Tx 51 The total number of 403
Responses transmitted by the
SBC
msrp-TransResp404Tx 52 The total number of 404
Responses transmitted by the
SBC
msrp-TransResp408Tx 53 The total number of 408
Responses transmitted by the
SBC
msrp-TransResp413Tx 54 The total number of 413
Responses transmitted by the
SBC
msrp-TransResp415Tx 55 The total number of 415
Responses transmitted by the
SBC
msrp-TransResp423Tx 56 The total number of 423
Responses transmitted by the
SBC
msrp-TransResp424Tx 57 The total number of 424
Responses transmitted by the
SBC
msrp-TransResp425Tx 58 The total number of 425
Responses transmitted by the
SBC
msrp-TransResp428Tx 59 The total number of 428
Responses transmitted by the
SBC
msrp-TransResp481Tx 60 The total number of 481
Responses transmitted by the
SBC
msrp-TransResp501Tx 61 The total number of 501
Responses transmitted by the
SBC
msrp-TransResp506Tx 62 The total number of 506
Responses transmitted by the
SBC
msrp-AvgSENDTransRx 63 The average number of MSRP
SEND transactions received by
the SBC per session
msrp-AvgChatSENDTransRx 64 The average number of CHAT
message SEND transactions
received by the SBC per session

4-30
Chapter 4
Applications MIB ([Link])

GET Query Name Object IDs: Description

[Link].4.1.9148.[Link].[Link].
(realm ID).(counter type).+
msrp-AvgIsTypingSENDTransRx 65 The average number of IsTyping
message SEND transactions
received by the SBC per session
msrp-AvgReceiptSENDTransRx 66 The average number of Receipt
message SEND transactions
received by the SBC per session
msrp-AvgSENDMsgBytesRx 67 The average number of bytes in
SEND transactions received by
the SBC per session
msrp-AvgChatSENDMsgBytesRx 68 The average number of bytes in
Chat message SEND
transactions received by the SBC
per session
msrp- 69 The average number of bytes in
AvgIsTypingSENDMsgBytesRx IsTyping message SEND
transactions received by the SBC
per session
msrp- 70 The average number of bytes in
AvgReceiptSENDMsgBytesRx Receipt message SEND
transactions received by the SBC
per session
msrp-SENDMsgBytesRx 71 The number of bytes in MSRP
SEND transactions received by
the SBC
msrp-ChatSENDMsgBytesRx 72 The number of bytes in Chat
message SEND transactions
received by the SBC
msrp-IsTypingMsgBytesRx 73 The number of bytes in IsTyping
message SEND transactions
received by the SBC
msrp-ReceiptMsgBytesRx 74 The number of bytes in Receipt
message SEND transactions
received by the SBC
msrp-SuccessREPORTTransRx 75 The number of Success Reports
received by the SBC
msrp-FailureREPORTTransRx 76 The number of Failure Reports
received by the SBC
msrp- 77 The average number of bytes in
AvgSuccessREPORTMsgBytesR Success Reports received by the
x SBC per session
msrp- 78 The average number of bytes in
AvgREPORTFailureBytesRx Success Reports received by the
SBC per session
msrp-AvgREPORTFailureRateRx 79 The average number of Reports
received by the SBC that were
Failure Reports
msrp- 80 The average number of Reports
AvgREPORTSuccessRateRx received by the SBC that were
Success Reports
msrp-REPORTResp400Rx 81 The total number of Report
responses conveying 400
messages received by the SBC

4-31
Chapter 4
Applications MIB ([Link])

GET Query Name Object IDs: Description

[Link].4.1.9148.[Link].[Link].
(realm ID).(counter type).+
msrp-REPORTResp401Rx 82 The total number of Report
responses conveying 401
messages received by the SBC
msrp-REPORTResp403Rx 83 The total number of Report
responses conveying 403
messages received by the SBC
msrp-REPORTResp404Rx 84 The total number of Report
responses conveying 404
messages received by the SBC
msrp-REPORTResp408Rx 85 The total number of Report
responses conveying 408
messages received by the SBC
msrp-REPORTResp413Rx 86 The total number of Report
responses conveying 413
messages received by the SBC
msrp-REPORTResp415Rx 87 The total number of Report
responses conveying 415
messages received by the SBC
msrp-REPORTResp423Rx 88 The total number of Report
responses conveying 423
messages received by the SBC
msrp-REPORTResp424Rx 89 The total number of Report
responses conveying 424
messages received by the SBC
msrp-REPORTResp425Rx 90 The total number of Report
responses conveying 425
messages received by the SBC
msrp-REPORTResp428Rx 91 The total number of Report
responses conveying 428
messages received by the SBC
msrp-REPORTResp481Rx 92 The total number of Report
responses conveying 481
messages received by the SBC
msrp-REPORTResp501Rx 93 The total number of Report
responses conveying 501
messages received by the SBC
msrp-REPORTResp506Rx 94 The total number of Report
responses conveying 506
messages received by the SBC
msrp- 95 The average number of Failure
AvgREPORTFailureBytes400Rx Report bytes conveying 400
messages received by the SBC
per session
msrp- 96 The average number of Failure
AvgREPORTFailureBytes401Rx Report bytes conveying 401
messages received by the SBC
per session
msrp- 97 The average number of Failure
AvgREPORTFailureBytes403Rx Report bytes conveying 403
messages received by the SBC
per session

4-32
Chapter 4
Applications MIB ([Link])

GET Query Name Object IDs: Description

[Link].4.1.9148.[Link].[Link].
(realm ID).(counter type).+
msrp- 98 The average number of Failure
AvgREPORTFailureBytes404Rx Report bytes conveying 404
messages received by the SBC
per session
msrp- 99 The average number of Failure
AvgREPORTFailureBytes408Rx Report bytes conveying 408
messages received by the SBC
per session
msrp- 100 The average number of Failure
AvgREPORTFailureBytes413Rx Report bytes conveying 413
messages received by the SBC
per session
msrp- 101 The average number of Failure
AvgREPORTFailureBytes415Rx Report bytes conveying 415
messages received by the SBC
per session
msrp- 102 The average number of Failure
AvgREPORTFailureBytes423Rx Report bytes conveying 423
messages received by the SBC
per session
msrp- 103 The average number of Failure
AvgREPORTFailureBytes424Rx Report bytes conveying 424
messages received by the SBC
per session
msrp- 104 The average number of Failure
AvgREPORTFailureBytes425Rx Report bytes conveying 425
messages received by the SBC
per session
msrp- 105 The average number of Failure
AvgREPORTFailureBytes428Rx Report bytes conveying 428
messages received by the SBC
per session
msrp- 106 The average number of Failure
AvgREPORTFailureBytes481Rx Report bytes conveying 481
messages received by the SBC
per session
msrp- 107 The average number of Failure
AvgREPORTFailureBytes501Rx Report bytes conveying 501
messages received by the SBC
per session
msrp- 108 The average number of Failure
AvgREPORTFailureBytes506Rx Report bytes conveying 506
messages received by the SBC
per session
msrp-TransResponsesRx 109 The total number of Response
transactions received by the SBC
msrp-SuccessTransResponsesRx 110 The total number of Success
Response transactions received
by the SBC
msrp-TransResp400Rx 111 The total number of Response
transactions conveying 400
messages received by the SBC

4-33
Chapter 4
Applications MIB ([Link])

GET Query Name Object IDs: Description

[Link].4.1.9148.[Link].[Link].
(realm ID).(counter type).+
msrp-TransResp401Rx 112 The total number of Response
transactions conveying 401
messages received by the SBC
msrp-TransResp403Rx 113 The total number of Response
transactions conveying 403
messages received by the SBC
msrp-TransResp404Rx 114 The total number of Response
transactions conveying 404
messages received by the SBC
msrp-TransResp408Rx 115 The total number of Response
transactions conveying 408
messages received by the SBC
msrp-TransResp413Rx 116 The total number of Response
transactions conveying 413
messages received by the SBC
msrp-TransResp415Rx 117 The total number of Response
transactions conveying 415
messages received by the SBC
msrp-TransResp423Rx 118 The total number of Response
transactions conveying 423
messages received by the SBC
msrp-TransResp424Rx 119 The total number of Response
transactions conveying 424
messages received by the SBC
msrp-TransResp425Rx 120 The total number of Response
transactions conveying 425
messages received by the SBC
msrp-TransResp428Rx 121 The total number of Response
transactions conveying 428
messages received by the SBC
msrp-TransResp481Rx 122 The total number of Response
transactions conveying 481
messages received by the SBC
msrp-TransResp501Rx 123 The total number of Response
transactions conveying 501
messages received by the SBC
msrp-TransResp506Rx 124 The total number of Response
transactions conveying 506
messages received by the SBC

Note:
The system establishes realm level stats OIDs for the first (or single) realm by adding
the system-assigned realm identifier and the type and category as the suffix (.first
realm identifier.*.*) to the base OID. Should there be multiple realms, the OID is
similarly numbered using the suffix (.second realm identifier.*.*) for the second realm,
and (.third realm identifier.*.*) for the third realm and so forth.

4-34
Chapter 4
Codec and Transcoding MIB ([Link])

Codec and Transcoding MIB ([Link])

The following table describes the SNMP GET query names for the Codec and Transcoding
MIB ([Link]). The apCodecMIBObjects object has the OID [Link].4.1.9148.3.7.1. The
apCodecRealmStatsTable object has the OID [Link].4.1.9148.[Link]. The
apCodecRealmStatsEntry object has the OID [Link].4.1.9148.[Link].1.

apCodecMIBObjects

SNMP GET Query Name Object ID: Description

[Link].4.1.9148.[Link].1
+
apCodecRealmCountOther .1 Count of the SDP media streams
received in the realm which negotiated to
a codec not defined in this table.
apCodecRealmCountPCMU .2 Count of SDP media streams received in
the realm which negotiated to the PCMU
codec.
apCodecRealmCountPCMA .3 Count of SDP media streams received in
the realm which negotiated to the PCMA
codec.
apCodecRealmCountG722 .4 Count of SDP media streams received in
the realm which negotiated to the G722
codec.
apCodecRealmCountG723 .5 Count of SDP media streams received in
the realm which negotiated to the G723
codec.
apCodecRealmCountG726-16 .6 Count of SDP media streams received in
the realm which negotiated to the
G726-16 codec.
apCodecRealmCountG726-24 .7 Count of SDP media streams received in
the realm which negotiated to the
G726-24 codec.
apCodecRealmCountG726-32 .8 Count of SDP media streams received in
the realm which negotiated to the
G726-32 codec.
apCodecRealmCountG726-40 .9 Count of SDP media streams received in
the realm which negotiated to the
G726-40 codec.
apCodecRealmCountG728 .10 Count of SDP media streams received in
the realm which negotiated to the G728
codec.
apCodecRealmCountG729 .11 Count of SDP media streams received in
the realm which negotiated to the G729
codec.
apCodecRealmCountGSM .12 Count of SDP media streams received in
the realm which negotiated to the GSM
codec.
apCodecRealmCountILBC .13 Count of SDP media streams received in
the realm which negotiated to the iLBC
codec.
apCodecRealmCountAMR .14 Count of SDP media streams received in
the realm which negotiated to the AMR
codec.

4-35
Chapter 4
Codec and Transcoding MIB ([Link])

SNMP GET Query Name Object ID: Description

[Link].4.1.9148.[Link].1
+
apCodecRealmCountEVRC .15 Count of SDP media streams received in
the realm which negotiated to the EVRC
codec.
apCodecRealmCountH261 .16 Count of SDP media streams received in
the realm which negotiated to the H261
codec.
apCodecRealmCountH263 .17 Count of SDP media streams received in
the realm which negotiated to the H.263
codec.
apCodecRealmCountT38 .18 Count of SDP media streams received in
the realm which negotiated to the T.38
codec.
apCodecRealmCountAMRWB .19 Count of SDP media streams received in
the realm which negotiated to the AMR-
WB codec.
apCodecRealmCountEVRC0 .20 Count of SDP media streams received in
the realm which negotiated to the
EVRC0 codec.
apCodecRealmCountEVRC1 .21 Count of SDP media streams received in
the realm which negotiated to the
EVRC1 codec.
apCodecRealmCountEVRCB .22 Count of SDP media streams received in
the realm which negotiated to the
EVRCB codec.
apCodecRealmCountEVRCB0 .23 Count of SDP media streams received in
the realm which negotiated to the
EVRCB0 codec.
apCodecRealmCountEVRCB1 .24 Count of SDP media streams received in
the realm which negotiated to the
EVRCB1 codec.
apCodecRealmCountOpus .25 Count of SDP media streams received in
the realm which negotiated to the Opus
codec.
apCodecRealmCountSILK .26 Count of SDP media streams received in
the realm which negotiated to the SILK
codec.
apCodecRealmCountT140 .27 Count of SDP media streams received in
the realm which negotiated to the T.140
codec.
apCodecRealmCountBAUDOT .28 Count of SDP media streams received in
the realm which negotiated to the
BAUDOT codec.
apCodecRealmCountH264 .29 Count of SDP media streams received in
the realm which negotiated to the H.264
codec.
apCodecRealmCountEVRCNW .30 The count of SDP media streams
received in the realm which negotiated to
the EVRCNW codec.
apCodecRealmCountEVRCNW0 .31 The count of SDP media streams
received in the realm which negotiated to
the EVRCNW0 codec.

4-36
Chapter 4
Codec and Transcoding MIB ([Link])

SNMP GET Query Name Object ID: Description

[Link].4.1.9148.[Link].1
+
apCodecRealmCountEVRCNW1 .32 The count of SDP media streams
received in the realm which negotiated to
the EVRCNW1 codec
apCodecRealmCountEVS .33 The count of SDP media streams
received in the realm which negotiated to
the EVS codec.

apTranscodingMIBObjects
The apTranscodingMIBObjects object has the OID [Link].4.1.9148.3.7.2. The
apCodecTranscodingRealmStatsTable object has the OID [Link].4.1.9148.[Link]. The
apTranscodingRealmStatsEntry object has the OID [Link].4.1.9148.[Link].1.

SNMP GET Query Name Object ID: Description

[Link].4.1.9148.[Link].1 +
apCodecRealmSessionsTransparent .1 Number of sessions in the realm
that did not use any DSP
resources for transcoding or
transrating.
apCodecRealmSessionsTransrated .2 Number of sessions in the realm
that had a common codec but
used DSP resources to modify
packetization rate.
apCodecRealmSessionsTranscoded .3 Number of sessions in the realm
that had used DSP resources to
transcode between codecs.

apCodecTranscodingResourceMIBObjects
The apCodecTranscodingResourceMIBObjects object has the OID [Link].4.1.9148.[Link]. It
contains 5 OIDS that return overall system transcoding counts and statistics.

SNMP GET Query Name Object ID: Description

[Link].4.1.9148.[Link] +
apCodecTranscodingResourcesT .1 Total number of transcoding
otal sessions available on the system.
apCodecTranscodingResourcesC .2 Number of transcoding sessions
urrent currently in-use.
apCodecTranscodingResourcesH .3 Highest number of transcoding
igh sessions simultaneously in-use
since system reboot or manual
statistic reset.
apCodecTranscodingInUsePerce .4 Transcoding sessions currently
ntCurrent in-use as a percentage of total
available sessions.
apCodecTranscodingInUsePerce .5 Transcoding sessions
ntHigh simultaneously in-use since
system reboot or manual statistic
reset expressed as a percentage
of total available sessions.

4-37
Chapter 4
Codec and Transcoding MIB ([Link])

apCodecPairStatsTable
This table, found in the [Link], provides a listing of all unique codec pairs currently
being transcoding and the session count of that pair currently in use. It conveys the same
information displayed in the show xcode codecs command. Use the apCodecTable for
correlation between Codec name (apCodecName) and Codec index (apCodecIndex) to define
apCodecPairAIndex and apCodecPairBIndex. When Ptimes for call legs in the codec pair
differ, they will be included as additional indices. When digit translation is active on the call and
digit translation types differ across call legs, indication of which call leg uses which digit
translation type is output as well. Use the ApCodecDigitTypes object for digit type value
correlation.

MIB Object Object ID: Description

[Link].4.1.9148.[Link] +
apCodecPairStatsEntry .1 Entry of this table. Note that the
end point A is the one with
smaller or equal apCodecIndex.
apCodecPairAIndex .1.1 The index of the first codec in the
pair
apCodecPairBIndex .1.2 The index of the second codec in
the pair
apCodecPairAPValue .1.3 The p value in the end point A. A
value of zero indicates the value
is not provided.
apCodecPairBPValue .1.4 The p value in the end point B. A
value of zero indicates the value
is not provided.
apCodecPairADigitType .1.5 The digit type index in the end
point A.
apCodecPairBDigitType .1.6 The digit type index in the end
point B.
apCodecPairTranscodingCurrent .1.7 The current number of
transcoding sessions for this
codec-pair since system reboot or
manual statistic reset.
apCodecPairTranscodingHigh .1.8 The highest number of
transcoding sessions in use for
this codec-pair since system
reboot or manual statistic reset.

Transcoding Capacity in System Management MIB ([Link])

The following VARBINDs are used in Transcoding related traps. They may not be polled and
retrieved using an SNMP GET.
The apSysMgmtMIBObjects object has the OID [Link].4.1.9148.3.2.1. The
apSysMgmtGeneralObjects object has the OID [Link].4.1.9148.[Link].

SNMP Object Name Object ID: Description

[Link].4.1.9148.[Link] +
apSysXCodeCapacity .34 Percentage of transcoding utilization.
apSysXCodeAMRCapacity .35 Percentage of licensed AMR
transcoding sessions.

4-38
Chapter 4
Diameter MIB ([Link])

SNMP Object Name Object ID: Description

[Link].4.1.9148.[Link] +
apSysXCodeAMRWBCapacity .36 Percentage of licensed AMR-WB
transcoding sessions.
apSysXCodeEVRCCapacity .39 Percentage of licensed EVRC
transcoding sessions.
apSysXCodeEVRCBCapacity .40 Percentage of licensed EVRCB
transcoding sessions.
apSysAcpTlsEnabled .41 A value of TRUE indicates ACP over
TLS connection is supported and
enabled. A FALSE value indicates
ACP over TLS connection is not
enabled
apSysXCodeG729Capacity .42 The percentage of licensed G729
transcoding utilization
apSysXCodeOpusCapacity .46 The percentage of licensed Opus
transcoding utilization (non pollable).
apSysXCodeSILKCapacity .47 The percentage of licensed SILK
transcoding utilization (non pollable).

Diameter MIB ([Link])

The Diameter MIB ([Link]) contains one table (apDiamClfErrorStatsTable:
[Link].4.1.9148.[Link].2.1) and 6 traps. There are numerous objects that are included within
the traps, and these objects are not accessible from outside of the traps.
The apDiamClfErrorStatsTable lists Diameter Clf error status.

SNMP GET Query Name Object ID: Description

[Link].4.1.9148.[Link].2.1 +
apDiamClfErrorStatsEntry .1 N/A
apDiamClfExtPolSvrIndex .1.1 An integer for the sole purpose of
indexing the external policy servers.
apDiamClfExtPolSvrName .1.2 External policy server name
apDiamClfErrorsRecent .1.3 Number of diameter errors in recent
period received on e2 interface with the
CLF.
apDiamClfErrorsTotal .1.4 Total number of diameter errors in life
time received on e2 interface with the
CLF.
apDiamClfErrorsPerMax .1.5 PerMax count of diameter errors in life
time received on e2 interface with the
CLF.

The following objects in the ap-diameter MIB are only available in the trap notifications:

SNMP GET Query Name Object ID: Description

[Link].4.1.9148.[Link].1 +
apDiamAcctSrvrHostName .1 The Diameter Accounting Server
host name.

4-39
Chapter 4
DNS ALG MIB ([Link])

SNMP GET Query Name Object ID: Description

[Link].4.1.9148.[Link].1 +
apDiamAcctSrvrIPPort .2 The Diameter Accounting Server
IP address and port number:
[Link]:P
apDiamAcctSrvrOriginRealm .3 The Diameter Accounting Server
Origin Realm.
apDiamAcctSrvrOriginHost .4 The Diameter Accounting Server
Origin Host.
apDiamAcctSrvrTransportType .5 The Diameter Accounting Server
Transport Type.
apAcctMsgQueueAvailCurrent .6 The current measured
percentage value of space
available
apAcctMsgQueueMinorThreshold .7 The current configured minor
threshold value.
apAcctMsgQueueMajorThreshold .8 The current configured major
threshold value.
apAcctMsgQueueCriticalThreshol .9 The current configured critical
d threshold value.
apDiameterResultCode 10 The Result-Code AVP (268) value
RFC 3588, 7.1. Result-Code AVP

DNS ALG MIB ([Link])

The DNS ALG mib ([Link]) contains tables related to capturing dns-alg constraints and
other statistics.

apDNSALGServerStatusTable
This table, found in the [Link], provides a listing of DNS ALG status of a the DNS ALG
server. It conveys the same information displayed in the show dnsalg status command. This
table is indexed by the DNS ALG server

MIB Object Object ID: Description

[Link].4.1.9148.[Link].1 +
apDNSALGServerStatusEntry .1 An entry designed to hold the
status of a single DNSALG
server.
apDNSALGConfigIndex .1.1 An integer for the sole purpose of
indexing the DNS-ALG
configuration. Only one DNS-ALG
configuration is allowed per a
realm.
apDNSALGServerIndex .1.2 An integer for the sole purpose of
indexing the Dns Server
Attributes in a DNS-ALG config.
Each DNS-ALG configuration can
have multiple Dns Server
Attributes.

4-40
Chapter 4
DNS ALG MIB ([Link])

MIB Object Object ID: Description

[Link].4.1.9148.[Link].1 +
apDNSALGConfigName .1.4 The name of the dns-alg config
element that contains this DNS-
ALG server.
apDNSALGServerRealm .1.5 The name of the server realm
element that contains this DNS-
ALG server.
apDNSALGDomainSuffix .1.6 The name of the domain suffix
element that contains this DNS-
ALG server.
apDNSALGServerIpAddress .1.7 The IP address of this DNS-ALG
server.
apDNSALGServerStatus .1.8 The status of this DNS-ALG
server.
• 0 - in service
• 1 - lover priority
• 2 - out of service,
unreachable.

apDNSALGStatsTable
This table, found in the [Link], provides a listing of DNS ALG statistics and counts for a
specific realm. It conveys the same information displayed in the show dnsalg stats command.
This table is indexed by the DNS ALG realm.

MIB Object Object ID: Description

[Link].4.1.9148.[Link].2 +
apDnsALGStatsEntry .1 Entry of this table.
apDnsAlgClientRealmIndex .1.1 Index of this table.
apDnsAlgClientRealmName .1.2 The name of the realm that
contains this DNS-ALG server.
apDnsAlgCurrentQueries .1.3 Total number of lifetime queries
received on the DNS-ALG server
in the given realm.
apDnsAlgTotalQueries .1.4 Total number of lifetime queries
received on the DNS-ALG server
in the given realm.
apDnsAlgCurrentSucess .1.5 Number of success responses in
a recent period received on the
DNS-ALG server in the given
realm.
apDnsAlgTotalSucess .1.6 Total number of lifetime success
responses received on the DNS-
ALG server in the given realm.
apDnsAlgCurrentNotFound .1.7 Number of not-found responses
in a recent period received on the
DNS-ALG server in the given
realm.
apDnsAlgTotalNotFound .1.8 Total number of lifetime not-found
responses in received on the
DNS-ALG server in the given
realm.

4-41
Chapter 4
Environment Monitor MIB ([Link])

MIB Object Object ID: Description

[Link].4.1.9148.[Link].2 +
apDnsAlgCurrentTimeOut .1.9 Number of time-out responses in
a recent period received on the
DNS-ALG server in the given
realm.
apDnsAlgTotalTimeOut .1.10 Total number of time-out
responses in a life time received
on the DNS-ALG server in the
given realm.
apDnsAlgCurrentBadStatus .1.11 Number of bad status responses
in a recent period received on the
DNS-ALG server in the given
realm.
apDnsAlgTotalBadStatus .1.12 Total number of bad status
responses in a lifetime received
on the DNS-ALG server in the
given realm.
apDnsAlgCurrentOtherFailures .1.13 Number of other failure
responses in a recent period
received on the DNS-ALG server
in the given realm.
apDnsAlgTotalOtherFailures .1.14 Total number of other failure
responses in a lifetime received
on the DNS-ALG server in the
given realm.
apDnsAlgAvgLatency .1.15 Average observed one-way
signalling latency during the
period in milliseconds.
apDnsAlgMaxLatency .1.16 Maximum observed one-way
signalling latency during the
period in milliseconds.
apDnsAlgMaxBurstRate .1.17 Maximum burst rate of traffic
measured during the period
(combined inbound and
outbound).

Environment Monitor MIB ([Link])

The following table describes the SNMP GET query names for the Environment Monitor MIB
([Link]).
To form the OID for an object, append the value in the OID column to [Link].4.1.9148.3.3.1.
For example, the OID for apEnvMonI2CState is [Link].4.1.9148.[Link].

4-42
Chapter 4
Environment Monitor MIB ([Link])

SNMP GET OID Description

Query Name
apEnvMonI2CStat 1 State of the environmental monitor located in the chassis. Values
e are:
• initial (1): environment is at the initial state
• normal (2): environment is good; for example at low
temperature
• minor (3): environment is not good; for example fans speed
is more than minor alarm threshold but less than major
alarm threshold
• major (4): environment is bad; for example an speed is
more than major alarm threshold, but less than critical alarm
threshold
• critical (5): environment is very bad; for example fan speed
is more than critical alarm threshold
• shutdown (6): environment is at its worst, the system should
be shutdown immediately
• notPresent (7): environmental monitor is not present
• notFunctioning (8): environmental monitor does not function
properly; for example, IC2 failure or temperature sensor
generates abnormal data
• unknown (9): no information available because of internal
error

The apEnvMonVoltageStatusEntry object has the OID [Link].4.1.9148.[Link].1.1. This object

is deprecated.
The apEnvMonTemperatureStatusEntry object has the OID [Link].4.1.9148.[Link].1.1.
To form the OID for an object, append the value in the OID column to
[Link].4.1.9148.[Link].1.1. For example, the OID for apEnvMonTemperatureStatusType is
[Link].4.1.9148.[Link].1.1.2.

SNMP GET OID Description

Query Name
apEnvMonTemper 2 Indicates the entity being monitored for temperature. Values are:
atureStatusType • ds1624sMain (1)
• ds1624sCPU (2)
• lm84 (3)
• lm75 (4)
• lm75Main (5)
• lm75Cpu (6)
• lm75Phy (7)
apEnvMonTemper 3 Description of the temperature being monitored. It has the value of the
atureStatusDescr Main Board PROM Temperature (in Celsius).
apEnvMonTemper 4 The current temperature of the main board PROM in Celsius.
atureStatusValue

4-43
Chapter 4
Environment Monitor MIB ([Link])

SNMP GET OID Description

Query Name
apEnvMonTemper 5 Current state of the temperature which can have one of the following
atureState values:
• 1: initial: Temperature is at its initial state.
• 2: normal: The temperature is normal.
• 6: shutdown: The system should be shutdown immediately
• 7: not present: The temperature sensor does not exist
• 8: not functioning: The temperature sensor is not functioning properly.
• 9: unknown. Cannot obtain information due to an internal error.
Values specific to 3900/3950/4900:
• 3: minor alarm - the temperature is greater than or equal to 69.7
degrees Celsius and less than 73.8 degrees Celsius.
• 4: major alarm. The temperature is greater than or equal to 73.8
degrees Celsius and less than 77.9 degrees Celsius.
• 5: critical alarm. The temperature is greater than or equal to 77.9
degrees Celsius.
In general, the critical alarm is sent at 95% of the maximum allowed
temperature, the major alarm at 90%, and the minor alarm at 85%.
apEnvMonTemper 6 Slot for which this temperature is found.
atureSlotID
apEnvMonTemper 7 Type of module found in this slot.
atureSlotType

The apEnvMonFanStatusEntry object has the OID [Link].4.1.9148.[Link].1.1.

SNMP GET Query Name Object ID: Description

[Link].4.1.9148.[Link].1.1
+
apEnvMonFanStatusType .2 Location of the fan, which can have one of
the following values:
11: fan1
12: fan2
13: fan3
14: fan4
apEnvMonFanStatusDescr .3 Textual description of the fan.
apEnvMonFanStatusValue .4 Current measurement of fan speed in
percentage.

4-44
Chapter 4
Environment Monitor MIB ([Link])

SNMP GET Query Name Object ID: Description

[Link].4.1.9148.[Link].1.1
+
apEnvMonFanState .5 Current state of the fan speed which can
have one of the following values:
1: initial. The temperature is at its initial state.
2: normal. The fan speed is normal.
3: minor. The fan speed is between 75% and
90% of the full fan speed
4: major. The fan speed is between 50% and
75% of the full fan speed
5: critical. The fan speed is less than 50% of
the full fan speed.
6: shutdown. The system should be shutdown
immediately
7: not present. The fan sensor does not exist.
8: not functioning. The fan sensor is not
functioning properly.
9: unknown. Cannot obtain information due to
an internal error.
apEnvMonFanState .6 Current state of the fan being monitored.
apEnvMonFanSlotID .7 Slot where this fan is found. A zero is
returned if this fan is not the type slot.

The apEnvMonPowerSupplyStatusEntr object has the OID [Link].4.1.9148.[Link].1.1.

SNMP GET Query Name Object ID: Description

[Link].4.1.9148.[Link].1.1 +
apEnvMonPowerSupplyStatusType .2 Location of the power supply,
which can have one of the
following values:
0: left power supply B
1: right power supply A
3: slot
apEnvMonPowerSupplyStatusDescr .3 Textual description of the power
supply.
apEnvMonPowerSupplyState .4 Current state of the power supply.
Values:
2: normal. The power supply is
normal.
7: not present: The power supply
sensor does not exist.

The apEnvPhyCardStatusEntry object has the OID [Link].4.1.9148.[Link].1.1.

SNMP GET Query Name Object ID: Description

[Link].4.1.9148.[Link].1.1 +
apEnvMonPhyCardStatusDescr .3 Textual description of the phy card.

4-45
Chapter 4
H.323 MIB ([Link])

SNMP GET Query Name Object ID: Description

[Link].4.1.9148.[Link].1.1 +
apEnvMonPhyCardState .4 The current state of the phy card.
Values:
1: initial.
2: normal.
3: minor.
4: major.
5: critical.
6: shutdown. The system should be
shutdown immediately
7: not present. The sensor does not
exist.
8: not functioning. The sensor is not
functioning properly.
9: unknown. Cannot obtain
information due to an internal error.
10: undetectable. The component is
not detectable.

H.323 MIB ([Link])

The following table describes the SNMP GET query names for the H.323 MIB ([Link]).
The apH323MIBObjects object has the OID [Link].4.1.9148.3.10.1, the apH323StackTable
object has the OID [Link].4.1.9148.[Link], and the apH323StackEntry object has the OID
[Link].4.1.9148.[Link].1.

SNMP GET Query Name Object ID: Description

[Link].4.1.9148.[Link].1 +
apH323StackName .1 Configured H.323 stack name.
apH323StackCurrentCalls .2 Number of current calls.

License MIB ([Link])

The following table describes the SNMP GET query names for the License MIB (ap-
[Link]). The apLicenseEntry object has the OID [Link].4.1.9148.[Link].1.

SNMP GET Query Object ID: Description

Name [Link].4.1.9148.[Link].1
+
apLicenseKey .2 Key, not applicable to the first index, which
represents the consolidated license. Displays
N/A.
apLicenseCapacity .3 Maximum number of simultaneous sessions
allowed by a system for all combined protocols.
apInstallDate .4 Installation time and date in the following format:
hh:mm:ss Month Day Year. Displays N/A if a
license is not enabled.

4-46
Chapter 4
License MIB ([Link])

SNMP GET Query Object ID: Description

Name [Link].4.1.9148.[Link].1
+
apLicenseBeginDate .5 Installation time and date in the following format:
hh:mm:ss month day year. Displays N/A if a
license is not enabled.
apLicenseExpireDate .6 Expiration time and date in the following format:
hh:mm:ss Month Day Year. Displays N/A if a
license is not enabled.
apLicenseSIPFeature .7 Value that indicates whether a Session Initiation
Protocol (SIP) license is present. A value of 1
indicates that SIP licensing is enabled. A value of
2 indicates that SIP licensing is not enabled.
apLicenseMGCPFeatur .8 Not Supported.
e
apLicenseH323Feature .9 Value that indicates whether a H.323 Protocol
license is present. A value of 1 indicates that
H.323 licensing is enabled. A value of 2 indicates
that H.323 licensing is not enabled.
apLicenseIWFFeature .10 Value that indicates whether a Interworking
Feature (IWF) license is present. A value of 1
indicates that IWF licensing is enabled. A value of
2 indicates that IWF licensing is not enabled.
apLicenseQOSFeature .11 Value that indicates whether a Quality of Service
(QoS) license is present. A value of 1 indicates
that QoS licensing is enabled. A value of 2
indicates that QoS licensing is not enabled.
apLicenseACPFeature .12 Value that indicates whether a Acme Control
Protocol (ACP) license is present. A value of 1
indicates that ACP licensing is enabled. A value
of 2 indicates that ACP licensing is not enabled.
apLicenseLPFeature .13 Value that indicates whether a Local Policy (LP)
license is present. A value of 1 indicates that LP
licensing is enabled. A value of 2 indicates that
LP licensing is not enabled.
apLicenseSAGFeature .14 Value that indicates whether a Session Agent
Group (SAG) license is present. A value of 1
indicates that SAG licensing is enabled. A value
of 2 indicates that SAG licensing is not enabled.
(load balancing feature)
apLicenseACCTFeature .15 Value that indicates whether a ACCT license is
present. An ACCT license allows the system to
create connections and send CDRs to one or
more RADIUS servers. A value of 1 indicates that
ACCT licensing is enabled. A value of 2 indicates
that ACCT licensing is not enabled.
apLicenseHAFeature .16 Value that indicates whether a High Availability
(HA) license is present. A value of 1 indicates that
HA licensing is enabled. A value of 2 indicates
that HA licensing is not enabled.
apLicensePACFeature .17 Value that indicates whether a PAC license is
present. A value of 1 indicates that PAC licensing
is enabled. A value of 2 indicates that PAC
licensing is not enabled.
apLicenseIKEFeature .18
apLicenseIPsecTunCap .19 IPsec Tunnel Capacity

4-47
Chapter 4
Security MIB ([Link])

SNMP GET Query Object ID: Description

Name [Link].4.1.9148.[Link].1
+
apLicenseAuthFeature .20
apLicenseDatabaseReg .21
Feature
apLicenseDatabaseReg .22 Database registration contact capacity
Cap
apLicenseSLBEndpoint .23 SLB endpoint capacity
Cap
apLicenseAMRLicense .24 AMR codec licensed capacity
dCap
apLicenseAMRWBLice .25 AMR-WB codec licensed capacity
nsedCap
apLicenseEVRCLicens .26 EVRC codec licensed capacity
edCap
apLicenseEVRCBLicen .27 EVRCB codec licensed capacity
sedCap
apLicenseOPUSLicens .28 OPUS codec licensed capacity
edCap
apLicenseSILKLicense .29 SILK codec licensed capacity
dCap
apLicenseEVSLicensed .30 EVS codec licensed capacity
Cap

Security MIB ([Link])

The following table describes the SNMP GET query names for the Security MIB (ap-
[Link]).
The apSecurityMIBObjects object has the OID [Link].4.1.9148.3.9.1.

SNMP GET Query Name Object ID: Description

[Link].4.1.9148.3.9.1 +
apSecurityOCSRIpAddress .5 OCSR server IP Address
apSecurityOCSRHostname .6 OCSR server hostname

The apSecurityTacacsTable object has the OID [Link].4.1.9148.[Link], and the

apSecurityTacacsEntry object has the [Link].4.1.9148.[Link].1.

SNMP GET Query Name Object ID: Description

[Link].4.1.9148.[Link].1
+
apSecurityTacacsCliCommands .3 Number of CLI commands sent
for TACACS+ accounting
apSecurityTacacsSuccessAuthentication .4 Number of successful TACACS+
authentication requests
apSecurityTacacsFailureAuthentication .5 Number of failed TACACS+
authentication requests
apSecurityTacacsSuccessAuthorization .6 Number of successful TACACS+
authorization requests

4-48
Chapter 4
SIP MIB ([Link])

SNMP GET Query Name Object ID: Description

[Link].4.1.9148.[Link].1
+
apSecurityTacacsFailureAuthorization .7 Number of failed TACACS+
authorization requests

apSecurityCertificateTable
This table, found in the [Link], provides information about installed security
certificates and their expiration. It conveys the same information displayed in the show
security certificates command.

MIB Object Object ID: Description

[Link].4.1.9148.[Link] +
apSecurityCertificateEntry .1 The certificate entry.
apSecurityCertificateConfigId .1.1 The internal configuration ID of
the certificate.
apSecurityCertificateIndex .1.2 The internal index of the
certificate. Combined with
configuration ID is the unique ID
of a certificate.
apSecurityCertificateRecordNam .1.3 The SBC's configuration record
e name for the certificate.
apSecurityCertificateCertSubject .1.4 The security certificate subject.
apSecurityCertificateCertStart .1.5 The start time and date of the
security certificate.
apSecurityCertificateCertExpire .1.6 The expiration time and date of
the security certificate.
apSecurityCertificateCertIssuer .1.7 The issuer of the security
certificate.
apSecurityCertificateCertIsCA .1.8 Boolean value indicating if the
certificate is a CA certificate.

SIP MIB ([Link])

The following table describes the SNMP Get query names for the SIP MIB ([Link]).
The apSipMIBGeneralObjects object has the OID [Link].4.1.9148.[Link].1.

SNMP GET Query Name Object ID: Description

[Link].4.1.9148.[Link]. +
apSipSecInterfaceTotalRegistrations .1.1 Total number of registrations on all
secondary SIP interfaces.
apSipSecInterfaceRegThreshold .1.2 The maximum threshold for
registrations on all secondary SIP
interfaces. If this threshold is
exceeded, an alarm is raised.
apSipSecInterfaceClearThreshold .1.3 The threshold for registrations on
all secondary SIP interfaces to
clear an alarm.

4-49
Chapter 4
SIP MIB ([Link])

SNMP GET Query Name Object ID: Description

[Link].4.1.9148.[Link]. +
apSipVideoCallsActive .2.1 Total number of Active Video Calls
apSipAudioCallsActive .2.2 Total number of Active Audio Calls
apSipSRVCCStatsTotalSuccess .3.1 Total successful SRVCC HO
apSipSRVCCStatsTotalFailed .3.2 Total failed SRVCC HO
apSipSRVCCStatsTotalCallsAfterAns .3.3 Total calls subjected to SRVCC
wer after answer
apSipSRVCCStatsAfterAnswerSucce .3.4 Total successful SRVCC HO after
ss answer
apSipSRVCCStatsAfterAnswerFailed .3.5 Total failed SRVCC HO after
answer
apSipSRVCCStatsTotalCallsDuringAl .3.6 Total calls subjected to SRVCC
erting during alerting.
apSipSRVCCStatsDuringAlertingSuc .3.7 Total successful SRVCC HO
cess during alerting.
apSipSRVCCStatsDuringAlertingFail .3.8 Total failed SRVCC HO during
ed alerting.
apSipSRVCCStatsAtcfCancel .3.9 Total ATCF cancellations
apSipSRVCCStatsEmergencySucce .3.10 Total successful SRVCC HO for
ss Emergency calls
apSipSRVCCStatsEmergencyFailed .3.11 Total failed SRVCC HO for
Emergency calls
apSipSRVCCStatsEatfCancel .3.12 Total EATF Cancellations
apSipSRVCCStatsTotalCallsDuringPr .3.13 Total calls subjected to SRVCC
eAlerting during pre-alerting
apSipSRVCCStatsDuringPreAlerting .3.14 Total successful SRVCC HO
Success during pre-alerting
apSipSRVCCStatsDuringPreAlerting .3.15 Total failed SRVCC HO during pre-
Failed alerting
apSipStatsActiveSubscriptionsRegEv 4.1 Number of Active Reg Event
t Subscriptions in the SBC.
apSipStatsPerMaxSubscriptionsReg 4.2 Lifetime PerMax Reg Event
Evt Subscriptions count in the SBC.
apSipStatsMaximumActiveSubscripti 4.3 Count of Lifetime Maximum Active
onsRegEvt Reg Event Subscriptions in the
SBC
apSipStatsTotalSubscriptionsRegEvt 4.4 Count of Lifetime Total Reg Event
Subscriptions in the SBC.

Object Group Object Name Description

Object group in apSipSecInterfaceRegObjectsGroup Object group to monitor
[Link] Includes: registrations for secondary
apSipSecInterfaceTotalRegistrations SIP interfaces.
apSipSecInterfaceRegThreshold
apSipSecInterfaceClearThreshold
(apSipObjectGroups 1)
Object in ap- apSipSecInterfaceTotalRegistrations Total number of registration
[Link] (apSipSecInterfaceObjects 1) on all secondary SIP
interfaces.

4-50
Chapter 4
SIP MIB ([Link])

Object Group Object Name Description

Object in ap- apSipSecInterfaceRegThreshold The max threshold for
[Link] (apSipSecInterfaceObjects 2) registrations on all
secondary interfaces
beyond which a trap is
generated.
Object in ap- apSipSecInterfaceClearThreshold The threshold for
[Link] (apSipSecInterfaceObjects 3) registrations on all
secondary SIP interfaces
below which a clear trap is
generated.
Object group in apSipRegEvtSubStatsObjects Object group to monitor
[Link] (apSipMIBGeneralObjects 4) registration event
subscriptions in the SBC.

MSRP Objects for SNMP

GET Query Name Object ID: Description

[Link].4.1.9148.[Link].5. +
apSipMSRPFdTableSize 1 The number of entries in the
MSRP File Descriptor Table. The
actual object counter on physical
platforms is 32-bit long while on
virtual platforms it is 64-bit.
apSipMSRPSessionIdTableSize 2 The number of entries in the
MSRP Session-Id table.
apSipMSRPActiveSessions 3 The number of total Active MSRP
Sessions.
apSipMSRPMaxActiveSessions 4 The number of max active MSRP
sessions.
apSipMSRPEstablishedSessions 5 Total number of MSRP
Established Sessions.
apSipMSRPProvisionedSessions 6 Total number of MSRP
Provisioned Sessions.
apSipMSRPFinishedSessions 7 Total number of MSRP Finished
Sessions.
apSipMSRPAcceptedConnection 8 Total number of Accepted
s Connections in MSRP sessions.
apSipMSRPConnectedConnectio 9 Total number of Connected
ns Connections in MSRP sessions.
apSipMSRPReleasedConnection 10 Total number of Released
s Connections in MSRP sessions.
apSipMSRPStreamRequestRecei 11 Total number of Stream Requests
ved Received in MSRP sessions.
apSipMSRPStreamRequestSent 12 Total number of stream Requests
Sent in MSRP sessions.
apSipMSRPStreamResponseRec 13 Total number of Stream
eived Responses Received in MSRP
sessions.

4-51
Chapter 4
SIP MIB ([Link])

GET Query Name Object ID: Description

[Link].4.1.9148.[Link].5. +
apSipMSRPStreamResponseSen 14 Total number of Stream
t Responses Sent in MSRP
sessions.
apSipMSRPGlobalBufferedData 15 Current Global Buffer Data size
for MSRP sessions.
apSipMSRPFlowAdd 16 Total number of MSRP Nat Flows
Added.
apSipMSRPFlowDelete 17 Total number of MSRP Nat Flows
Deleted.
apSipMSRPFailedSessionsCann 18 Total number of Failed MSRP
otRoute Sessions due to No Session
Route Failure.
apSipMSRPFailedSessionsCann 19 Total number of Failed MSRP
otConnect Sessions that can not connect.
apSipMSRPFailedSessionsFinger 20 Total number of Falied MSRP
printMismatch Sessions due to Fingerprint
Mismatches.
apSipMSRPFailedMessagesCan 21 Total number of Message Send
notBeSent Failures in MSRP sessions.
apSipMSRPFailedMessagesMalf 22 Total number of Malformed
ormed Messages Received in MSRP
sessions.
apSipMSRPSendQFullEvents 23 Total number of TCP Send-Q Full
Events in MSRP sessions.
apSipMSRPSendQCongestedEv 24 Total number of TCP Send-Q
ents Congested Events in MSRP
sessions.
apSipMSRPSendQCongestionRe 25 Total number of TCP Send-Q
lievedEvents Relieved Events in MSRP
sessions.
apSipMSRPStreamErrorNoTransI 26 Total number of No Trans-Id
d Stream Errors in MSRP sessions.
apSipMSRPStreamErrorNoMsgT 27 Total number of No Message
ype Type Stream Errors in MSRP
Sessions.
apSipMSRPStreamErrorNoByteL 28 Total number of No Byte Length
ength stream Errors in MSRP Sessions.
apSipMSRPBufferLimitExceeded 29 Total number of Buffer Limit
Exceeded Errors in MSRP
Sessions.
apSipMSRPFailedConnectionInit 30 Total number of Connection
Attempts Failed in MSRP
Sessions.
apSipMSRPSessReprovMismatc 31 Total number of Session
h Reprovision Mismatches.
apSipMSRPTcpListenErrors 32 Total number of TCP Listen
Errors in MSRP Sessions.
apSipMSRPTcpConnectError 33 Total number of TCP Connect
Errors in MSRP Sessions.
apSipMSRPTcpError 34 Total number of TCP Errors in
MSRP Sessions.

4-52
Chapter 4
SIP MIB ([Link])

GET Query Name Object ID: Description

[Link].4.1.9148.[Link].5. +
apSipMSRPNoFromHeaderSessi 35 Total number of FROM Header
onID without a session-id in MSRP
Sessions.
apSipMSRPNoFromHeader 36 Total number of Messages
without FROM Header in MSRP
Sessions.
apSipMSRPFromHdrAddrParseE 37 Total number of FROM Header
rror Parse errors in MSRP Sessions.
apSipMSRPNoFromHdrAddr 38 Total number of FROM Header
with no Address in MSRP
Sessions.
apSipMSRPNoFromHdrPort 39 Total number of FROM Header
with no port in MSRP Sessions.
apSipMSRPNoFromHdrAuthority 40 Total number of From Header
with no Authority in MSRP
Sessions.
apSipMSRPFromHdrSrvMismatc 41 Total number of FROM Header
h service type mismatches in
MSRP Sessions.
apSipMSRPSendFailNoDestFd 42 Total number of send failures due
to No Destination File Descriptor
found in MSRP Sessions.
apSipMSRPSendFailedNoDstSes 43 Total number of send failures due
sion to No Destination Session found
in MSRP Sessions.
apSipMSRPNoToHeaderSessionI 44 Total number of TO Headers
D without a session-id in MSRP
Sessions.
apSipMSRPNoToHeader 45 Total number of Messages
without TO Header in MSRP
Sessions.
apSipMSRPToHdrAddrParseError 46 Total number of TO Headers
Parse errors in MSRP Sessions.
apSipMSRPNoToHdrAddr 47 Total number of TO Headers with
no Address in MSRP Sessions.
apSipMSRPNoToHdrPort 48 Total number of TO Headers with
no port in MSRP Sessions.
apSipMSRPNoToHdrAuthority 49 Total number of TO Headers with
no Authority in MSRP Sessions.
apSipMSRPToHdrSrvMismatch 50 Total number of TO Header
service type mismatches in
MSRP Sessions.
apSipMSRPNoDestFdEntry 51 Total number of No Destination
File Descriptor Entry Errors in
MSRP Sessions.
apSipMSRPTcpSendFailure 52 Total number of TCP Send
Failures in MSRP Sessions.
apSipMSRPFdTableInsertErrorCo 53 Total number of Insert Collisions
llision errors in File Descriptor Table.
apSipMSRPFdTableInsertErrorNo 54 Total number of No Data Insert
Data Errors in File Descriptor Table.

4-53
Chapter 4
SIP MIB ([Link])

GET Query Name Object ID: Description

[Link].4.1.9148.[Link].5. +
apSipMSRPFdTableInsertErrorM 55 Total number of Memory Insert
emory Errors in File Descriptor Table.
apSipMSRPFdTableInsertErrorM 56 Total number of Max Hops Insert
axHops Errors in File Descriptor Table.
apSipMSRPFdTableInsertErrorBa 57 Total number of Bad Insert Errors
d in File Descriptor Table.
apSipMSRPSessionTableInsertEr 58 Total number of Insert Collisions
rorCollision Errors in Session Table.
apSipMSRPSessionTableInsertEr 59 Total number of No Data Insert
rorNoData Errors in Session Table.
apSipMSRPSessionTableInsertEr 60 Total number of Memory Insert
rorMemory Errors in Session Table.
apSipMSRPSessionTableInsertEr 61 Total number of Max Hops Insert
rorMaxHops Errors in Session Table.
apSipMSRPSessionTableInsertEr 62 Total number of Bad Insert Errors
rorBad in Session Table.
apSipMSRPFlowToSessionTableI 63 Total number of Insert Errors in
nsertError Flow-To-Session Table.
apSipMSRPNumPreProvSession 64 Total number of PreProvisioned
s Sessions in MSRP Sessions.
apSipMSRPNumPreProvMessag 65 Total number of PreProvision RX
es Messages in MSRP Sessions.
apSipMSRPConnectionStateNoS 66 Total number of Sockets in Initial
ession State in MSRP Sessions.
apSipMSRPConnectionStateListe 67 Total number of Sockets in
ning Listening State in MSRP
Sessions.
apSipMSRPConnectionStatePen 68 Total number of Sockets in
ding Pending State in MSRP
Sessions.
apSipMSRPConnectionStateCon 69 Total number of Sockets in
necting Connecting State in MSRP
Sessions.
apSipMSRPConnectionStateCon 70 Total number of Sockets in
nected Connected State in MSRP
Sessions.
apSipMSRPConnectionStateEsta 71 Total number of Sockets in
blished Established State in MSRP
Sessions.
apSipMSRPConnectionStateFinis 72 Total number of Sockets in
hed Finished State in MSRP
Sessions.
apSipMSRPConnectionStateRele 73 Total number of Sockets in
ased Released State in MSRP
Sessions.
apSipMSRPUnqualifiedConnectio 74 Total number of Sockets in
ns Unqualified Status in MSRP
Sessions.
apSipMSRPSessionStateNone 75 Total number of Sessions in Initial
State.
apSipMSRPSessionStateListenin 76 Total number of Sessions in
g Listening State.

4-54
Chapter 4
SIP MIB ([Link])

GET Query Name Object ID: Description

[Link].4.1.9148.[Link].5. +
apSipMSRPSessionStatePreProv 77 Total number of Sessions in Pre-
isioned Provisioned State.
apSipMSRPSessionStateProvisio 78 Total number of Sessions in
ned Provisioned State.
apSipMSRPSessionStateEstablis 79 Total number of Sessions in
hed Established State.
apSipMSRPSessionStateFinishe 80 Total number of Sessions in
d Finished State.
apSipMSRPClosedFdTableSize 81 Closed FD Table Size.
apSipMSRPClosedFdTableInsert 82 Total number of Insert Errors in
Errors Closed File Descriptor Table.
apSipMSRPNumFdForcedReleas 83 Total number of Forced Release
es File Descriptor in MSRP
Sessions.
apSipMSRPNumForcedReleased 84 Total number of Forced Release
ListenFdNotFound Listen File Descriptor Not Found
in MSRP Sessions.
apSipMSRPNumForcedReleased 85 Total number of Forced Release
ForkedFdNotFound Forked File Descriptor Not Found
in MSRP Sessions.
apSipMSRPNumListenFdForced 86 Total number of Forced Release
Released Listen File Descriptor in MSRP
Sessions.
apSipMSRPRequestBytesReceiv 87 Total number of Request Bytes
ed Received in MSRP Sessions.
apSipMSRPRequestBytesSent 88 Total number of Request Bytes
Sent in MSRP Sessions.
apSipMSRPResponseBytesRecei 89 Total number of Response Bytes
ved Received in MSRP Sessions.
apSipMSRPResponseBytesSent 90 Total number of Response Bytes
Sent in MSRP Sessions.
apSipMSRPUnqualifiedClose 91 Total number of Unqualified
Closes in MSRP Sessions.
apSipMSRPUnconnectedClose 92 Total number of File Descriptor
did not get any connection in
MSRP Sessions.
apSipMSRPAcceptErrorClose 93 Total number of Accept Error
Closes in MSRP Sessions.
apSipMSRPPreProvisionClose 94 Total number of Pre-provision
Closes in MSRP Sessions.
apSipMSRPReadErrorClose 95 Total number of Read Error
Closes in MSRP Sessions.
apSipMSRPStreamErrorClose 96 Total number of Stream Error
Closes in MSRP Sessions.
apSipMSRPBufferClose 97 Total number of Buffer Error
Closes in MSRP Sessions.
apSipMSRPReleaseNotificationF 98 Total number of Release
ailures Notification send failures.
apSipMSRPReleaseNotificationU 99 Total number of Unsent Release
nsentNoId Notifications due to No session
ID.

4-55
Chapter 4
SIP MIB ([Link])

GET Query Name Object ID: Description

[Link].4.1.9148.[Link].5. +
apSipMSRPReleaseNotificationU 100 Total number of Unsent Release
nsentNoFd Notifications due to invalid File
Descriptor.
apSipMSRPReleaseNotificationU 101 Total number of Unsent Release
nsentNoListenFd Notifications due to No Listen File
Descriptor.
apSipMSRPAcceptedConnection 102 Total number of CEMA Accepted
sCema Connections.
apSipMSRPConnectedConnectio 103 Total number of CEMA
nsCema Connected Connections.
apSipMSRPActiveCemaSessions 104 Total number of Active CEMA
Sessions.
apSipMSRPEstablishedSessions 105 Total number of Established
Sessmatch Sessmatch Sessions.
apSipMSRPProvisionedSessions 106 Total number of Provisioned
Sessmatch Sessmatch Sessions.
apSipMSRPActiveSessmatchSes 107 Total number of Active
sions Sessmatch Sessions.
apSipMSRPMessageFromHost 108 Total number of Messages
Received from Host in MSRP
Sessions.
apSipMSRPMessageToHost 109 Total number of Messages Sent
to Host in MSRP Sessions.
apSipMSRPMessageToHostFail 110 Total number of Messages Sent
to Host Failed in MSRP sessions.

Rate Statistics for Method Events

When configured, the SBC calculates SUCCESS, TIMEOUT and FAILURE percentages of
client and server transactions for the SUBSCRIBE, NOTIFY and MESSAGE methods and
makes them available via SNMP OIDs. The SBC contains these OIDs within
apSipMethodStatsEventCount ([Link].4.1.9148.[Link].10.1.4.*). These OIDs are
established in [Link] under the apSipMethodStatsTable package.

SNMP GET Query Name Object ID: Description

[Link].4.1.9148.[Link].10.1.4.*
eventSuccessRate 9.1.55 Success Rate of SUBSCRIBE
request on server transaction
eventTimeoutRate 9.1.56 Timeout Rate of SUBSCRIBE
request on server transaction
eventFailureRate 9.1.57 Failure Rate of SUBSCRIBE
request on server transaction
eventSuccessRate 9.2.55 Success Rate of SUBSCRIBE
request on client transaction
eventTimeoutRate 9.2.56 Timeout Rate of SUBSCRIBE
request on client transaction
eventFailureRate 9.2.57 Failure Rate of SUBSCRIBE
request on client transaction
eventSuccessRate 10.1.55 Success Rate of NOTIFY request
on server transaction

4-56
Chapter 4
syslog MIB ([Link])

SNMP GET Query Name Object ID: Description

[Link].4.1.9148.[Link].10.1.4.*
eventTimeoutRate 10.1.56 Timeout Rate of NOTIFY request
on server transaction
eventFailureRate 10.1.57 Failure Rate of NOTIFY request
on server transaction
eventSuccessRate 10.2.55 Success Rate of NOTIFY request
on client transaction
eventTimeoutRate 10.2.56 Timeout Rate of NOTIFY request
on client transaction
eventFailureRate 10.2.57 Failure Rate of NOTIFY request
on client transaction
eventSuccessRate 13.1.55 Success Rate of MESSAGE
request on server transaction
eventTimeoutRate 13.1.56 Timeout Rate of MESSAGE
request on server transaction
eventFailureRate 13.1.57 Failure Rate of MESSAGE
request on server transaction
eventSuccessRate 13.2.55 Success Rate of MESSAGE
request on client transaction
eventTimeoutRate 13.2.56 Timeout Rate of MESSAGE
request on client transaction
eventFailureRate 13.2.57 Failure Rate of MESSAGE
request on client transaction

syslog MIB ([Link])

The following table describes the SNMP GET query names for the syslog MIB ([Link]).

Note:
Form the Object Identifier (OID) Number by concatenating the OID of apSyslogBasic
([Link].4.1.9148.[Link]) with the OID termination number.

SNMP GET Query Name Object ID: Description

[Link].4.1.9148.[Link] +
apSyslogNotificationsSent .1 Number of apSyslogMessageGenerated
notifications sent. This number may include
notifications that were prevented from being
transmitted due to reasons such as resource
limitations and/or non-connectivity. If one is
receiving notifications, one can periodically
poll this object to determine if any
notifications were missed. If so, a poll of the
apSyslogHistoryTable might be appropriate.
apSyslogNotificationsEnabl .2 Information about whether or not
ed apSyslogMessageGenerated notifications will
be sent when a syslog message is generated
by the device. Disabling notifications does not
prevent syslog messages from being added to
the apSyslogHistoryTable.

4-57
Chapter 4
syslog MIB ([Link])

SNMP GET Query Name Object ID: Description

[Link].4.1.9148.[Link] +
apSyslogMaxLevel .3 Information about which syslog severity levels
will be processed. Any syslog message with a
log-level value greater than this value will be
ignored by the syslog agent. Note that
severity numeric values increase as their
severity decreases (for example, major (3) is
more severe than debug (9).
apSyslogMsgIgnores .4 Number of syslog messages which were
ignored, meaning that there is no need to
send an apSyslogMessageGenerated
notification. A message will be ignored if it
has a log level value greater than the
apSyslogMaxLevel value.
apSyslogMsgDrops .5 Number of syslog messages which could not
be processed due to lack of system
resources. Most likely, this will occur at the
same time that syslog messages are
generated to indicate this lack of resources.
Increases in this object's value may serve as
an indication that system resource levels
should be examined via other MIB objects. A
message that is dropped will not appear in the
history table, and no notification will be sent
for this message.

Note:
Form the Object Identifier (OID) Number by concatenating the OID of
apSyslogHistory ([Link].4.1.9148.[Link]) with the OID termination number.

SNMP GET Query Name Object ID: Description

[Link].4.1.9148.[Link]
+
apSyslogHistTableMaxLeng .1 Upper limit for the number of entries that the
th apSyslogHistoryTable may contain. A value of 0
will prevent any history from being retained.
When the apSyslogHistoryTable is full, the
oldest entry will be deleted and a new one will
be created.
apSyslogHistMsgsFlushed .2 Number of entries that have been removed from
the apSyslogHistoryTable in order to make room
for new entries. Use this to determine whether
the polling frequency on the history table is fast
enough and/or if the size of the history table is
large enough such that messages are not
missed.

4-58
Chapter 4
System Management MIB ([Link])

Note:
Form the Object Identifier (OID) Number by concatenating the OID of
apSyslogHistoryEntry ([Link].4.1.9148.[Link].3) with the OID termination number.

SNMP GET Query Object ID: Description

Name [Link].4.1.9148.[Link].3
+
apSyslogHistIndex .1 Monotonically increasing integer for the sole
purpose of indexing messages. When it reaches
the maximum value, the agent wraps the value
back to 1.
apSyslogHistFrom .2 Process name and host of the sending client (for
example, anyclient@[Link])
apSyslogHistLevel .3 Log level of the message.
apSyslogHistType .4 Textual identification for the log type, which
categorizes the log message.
apSyslogHistContent .5 Text of the syslog message. If the text of the
message exceeds 255 bytes, it is truncated to 255
bytes.
apSyslogHistTimestam .6 Value of sysUpTime when this message was
p generated.

System Management MIB ([Link])

The following table describes the SNMP GET query names for the System Management MIB
([Link]).
Note that the apSigRealmStats MIB is populated for realms on which H.323 and SIP are
configured; this supports aggregate statistics for H.323 and SIP. A note like this one appears
with the OID information shown in the table below.

SNMP GET Query Name Object ID: Description

[Link].4.1.9148.[Link]
+
apSysCPUUtil .1 Percentage of CPU utilization. This value
reflects the mean CPU utilization for all cores
on the system. For a system with 4 cores, the
number reported here is (CPU0 + CPU1 +
CPU2 + CPU3)/4. This value is updated very
second.
apSysMemoryUtil .2 Percentage of memory utilization.
apSysHealthScore .3 System health percentage, with a system
health percentage value of 100 (100%) being
the healthiest.

4-59
Chapter 4
System Management MIB ([Link])

SNMP GET Query Name Object ID: Description

[Link].4.1.9148.[Link]
+
apSysRedundancy .4 For HA pairs, information about whether this
SBC is active or standby. Possible values are:
initial(1): system is at initial stage
active(2): system is active
standby(3): system is standby
outOfService(4): system is out of service
For a Standalone system, a value of (2) is
returned.
apSysGlobalConSess .5 Total instant number of global concurrent
sessions at the moment.
apSysGlobalCPS .6 System-wide global calls per second. This
counter is calculated based on a sliding
window of 100 seconds.
apSysNATCapacity .7 Percentage of NAT table in Content
Addressable Memory (CAM) utilization.
apSysARPCapacity .8 Percentage of ARP table (in CAM) utilization.
apSysState .9 Current system state. Online denotes regular
call processing and offline implies no call
processing occurring but other administrative
functions are available.
apSysLicenseCapacity .10 Percentage of licensed sessions currently in
progress.
apSysSipStatsActiveLocalCo .11 Number of currently cached registered
ntacts contacts in the SBC.
apSysMgcpGWEndpoints .12 Not Supported.
apSysH323Registration .13 Number of H.323 registrations in the SBC.
apSysRegCacheLimit .14 Maximum number of contacts to be accepted
into the registration cache. A value of 0
indicates no limit.
apSysApplicationCPULoadRa .16 This value reflects the load of the sipd
te application on the cores where the threads
have been scheduled. Thus if there are two
sipd threads running on individual cores, a
and b, the number reported here is (CPUa +
CPUb)/2.
apSysRejectedMessages .18 Number of messages rejected by the SBC due
to matching criteria.
apSysSipEndptDemTrustToU .19 Global counter for SIP endpoint demotion from
ntrust trusted to untrusted.
apSysSipEndptDemUntrustTo .20 Global counter for SIP endpoint demotion from
Deny untrusted to deny.
apSysMgcpEndptDemTrustTo .21 Not Supported.
Untrust
apSysMgcpEndptDemUntrust .22 Not Supported.
ToDeny
apSysSipTotalCallsRejected .25 Global counter for SIP calls that are rejected
by the SBC
apSysCurrentEndptsDenied .26 Global counter for current endpoints denied by
the SBC

4-60
Chapter 4
System Management MIB ([Link])

SNMP GET Query Name Object ID: Description

[Link].4.1.9148.[Link]
+
apSysSipStatsActiveSubscript .27 An unsigned 32-bit integer that specifies the
ions current global count of active SIP
subscriptions.
apSysSipStatsPerMaxSubscri .28 An unsigned 32-bit integer that specifies the
ptions maximum global count of SIP subscriptions
initiated during any 100 second period since
the last SBC re-boot.
apSysSipStatsPerMaximumA .29 An unsigned 32-bit integer that specifies the
ctiveSubscriptions maximum global count of active SIP
subscriptions since the last SBC re-boot.
apSysSipStatsTotalSubscripti .30 An unsigned 32-bit integer that specifies the
ons global count of active SIP subscriptions since
the last SBC r e-boot.
apSysMgmtH248MgcName .31 Not Supported.
apSysMgmtH248Realm .32 Not Supported.
apSysMgmtH248PortMapUsa .33 Not Supported.
ge
apSysCPULoadAvgOneMinut .43 The percentage of CPU Load across all cores
e measured over 1 minute.
apSysCPULoadAvgFiveMinut .44 The percentage of CPU Load across all cores
e measured over 5 minutes.
apSysCPULoadAvgFiftnMinut .45 The percentage of CPU Load across all cores
e measured over 15 minutes.

The apSysMgmtCPULoadAvgGroup object has the OID [Link].4.1.9148.[Link].31, and is an

object that monitors CPU Load Average across all CPU cores for 1, 5, and 15 minutes.
The apSysStorageSpaceTable object has the OID [Link].4.1.9148.[Link].23, and the
apSysStorageSpaceEntry object has the OID [Link].4.1.9148.[Link].23.1.

SNMP GET Query Object ID: Description

Name [Link].4.1.9148.[Link].23.1
+
apSysVolumeIndex .1 Monotonically increasing integer for the
purpose of indexing volumes.
apSysVolumeName .2 Name of the volume.
apSysVolumeTotalSpace .3 Total size of the volume in MB.
apSysVolumeAvailSpace .4 Total space available on the volume in KB.

The apCombinedSessionAgentStatsEntry object has the OID [Link].4.1.9148.[Link].1.1.

This table object reflects statistics found in the show sipd agents ACLI command.

4-61
Chapter 4
System Management MIB ([Link])

SNMP GET Query Name Object ID: Description

[Link].4.1.9148.[Link].1.1
+
apCombinedStatsSessionAgentIndex .1 A monotonically
increasing integer for
the sole purpose of
indexing session
agents. When it
reaches the
maximum value the
agent wraps the value
back to 1.
apCombinedStatsSessionAgentHostname .2 The hostname of the
session agent for
which the following
statistics are being
calculated.
apCombinedStatsSessionAgentType .3 The type of the
specified session
agent, either SIP or
H323.
apCombinedStatsCurrentActiveSessionsInbound .4 Number of current
active inbound
sessions.
This value is found on
the ACLI at show
sipd agents,
"Inbound Active"
column.
apCombinedStatsCurrentSessionRateInbound .5 Current inbound
session rate in CPS.
This value is found on
the ACLI at show
sipd agents,
"Inbound Rate"
column.
apCombinedStatsCurrentActiveSessionsOutbound .6 Number of current
active outbound
sessions.
This value is found on
the ACLI at show
sipd agents,
"Outbound Active"
column.
apCombinedStatsCurrentSessionRateOutbound .7 Current outbound
session rate in CPS.
This value is found on
the ACLI at show
sipd agents,
"Outbound Rate"
column.
apCombinedStatsTotalSessionsInbound .8 Total number of
inbound sessions
during the 100
second sliding
window period.

4-62
Chapter 4
System Management MIB ([Link])

SNMP GET Query Name Object ID: Description

[Link].4.1.9148.[Link].1.1
+
apCombinedStatsTotalSessionsNotAdmittedInbou .9 Total number of non-
nd bandwidth constraints
that exceeded
rejections on inbound
sessions (for
example, max-
sessions, burst rate,
etc.).
apCombinedStatsPeriodHighInbound .10 Highest number of
concurrent inbound
sessions during the
period.
apCombinedStatsAverageRateInbound .11 Average rate of
inbound sessions
during the 100
second sliding
window period in
CPS.
This value is found on
the ACLI at show
sipd agents,
"Inbound Rate"
column.
apCombinedStatsTotalSessionsOutbound .12 Total number of
outbound sessions
during the 100
second sliding
window period.
apCombinedStatsTotalSessionsNotAdmittedOutbo .13 Total number of non-
und bandwidth constraints
that exceeded
rejections on
outbound sessions
(for example, max-
sessions, burst rate,
etc.).
apCombinedStatsPeriodHighOutbound .14 Highest number of
concurrent outbound
sessions during the
100 second sliding
window period.
apCombinedStatsAverageRateOutbound .15 Average rate of
outbound sessions
during the 100
second sliding
window period in
CPS.
This value is found on
the ACLI at show
sipd agents,
"Outbound Rate"
column.

4-63
Chapter 4
System Management MIB ([Link])

SNMP GET Query Name Object ID: Description

[Link].4.1.9148.[Link].1.1
+
apCombinedStatsMaxBurstRate .16 Maximum burst rate
of traffic measured
during the 100
second sliding
window period
(combined inbound
and outbound).
This value is found on
the ACLI at show
sipd agents, "Max
Burst" counter.
apCombinedStatsPeriodSeizures .17 Total number of
seizures during the
100 second sliding
window period.
apCombinedStatsPeriodAnswers .18 Total number of
answered sessions
during the 100
second sliding
window period.
apCombinedStatsPeriodASR .19 The answer-to-
seizure ratio,
expressed as a
percentage.
For example, a value
of 90 would represent
90%, or .90.
apCombinedStatsAverageLatency .20 Average observed
one-way signalling
latency during the
period.
apCombinedStatsMaxLatency .21 Maximum observed
one-way signalling
latency during the
100 second sliding
window period.
apCombinedStatsSessionAgentStatus .22 The current status of
the specified session
agent, which is
expressed as INS,
OOSnonresp,
OOSconstraintsviolati
on, BecomingOOS, or
ForcedOOS.

The apSipSessionAgentStatsEntry object has the OID [Link].4.1.9148.[Link].2.1.

4-64
Chapter 4
System Management MIB ([Link])

SNMP GET Query Name Object ID: Description

[Link].4.1.9148.[Link].2.1
+
apSipSAStatsSessionAgentIndex .1 A monotonically increasing
integer for the sole
purpose of indexing
session agents. When it
reaches the maximum
value the agent wraps the
value back to 1.
apSipSAStatsSessionAgentHostname .2 The hostname of the
session agent for which
the following statistics are
being calculated.
apSipSAStatsSessionAgentType .3 The type of the specified
session agent, either SIP
or H323.
apSipSAStatsCurrentActiveSessionsInbound .4 Number of current active
inbound sessions.
apSipSAStatsCurrentSessionRateInbound .5 Current Inbound Session
rate in CPS.
apSipSAStatsCurrentActiveSessionsOutboun .6 Number of current active
d outbound sessions.
apSipSAStatsCurrentSessionRateOutbound .7 Current outbound session
rate in CPS.
apSipSAStatsTotalSessionsInbound .8 Total number of inbound
sessions during the 100
second sliding window
period.
apSipSAStatsTotalSessionsNotAdmittedInbou .9 Total number of inbound
nd sessions rejected due to
insufficient bandwidth.
apSipSAStatsPeriodHighInbound .10 Highest number of
concurrent inbound
sessions during the 100
second sliding window
period.
apSipSAStatsAverageRateInbound .11 Average rate of inbound
sessions during the 100
second sliding window
period in CPS.
apSipSAStatsTotalSessionsOutbound .12 Total number of outbound
sessions during the 100
second sliding window
period.
apSipSAStatsTotalSessionsNotAdmittedOutb .13 Total number of outbound
ound sessions rejected because
of insufficient bandwidth.
apSipSAStatsPeriodHighOutbound .14 Highest number of
concurrent outbound
sessions during the 100
second sliding window
period.

4-65
Chapter 4
System Management MIB ([Link])

SNMP GET Query Name Object ID: Description

[Link].4.1.9148.[Link].2.1
+
apSipSAStatsAverageRateOutbound .15 Average rate of outbound
sessions during the 100
second sliding window
period in CPS.
apSipSAStatsMaxBurstRate .16 Maximum burst rate of
traffic measured during the
100 second sliding window
period (combined inbound
and outbound).
apSipSAStatsPeriodSeizures .17 Total number of seizures
during the 100 second
sliding window period.
apSipSAStatsPeriodAnswers .18 Total number of answered
sessions during the 100
second sliding window
period.
apSipSAStatsPeriodASR .19 The answer-to-seizure
ratio, expressed as a
[Link] example, a
value of 90 would
represent 90%, or .90.
apSipSAStatsAverageLatency .20 Average observed one-
way signaling latency
during the 100 second
sliding window period.
apSipSAStatsMaxLatency .21 Maximum observed one-
way signaling latency
during the 100 second
sliding window period.
apSipSAStatsSessionAgentStatus .22 The current status of the
specified session agent,
which is expressed as
INS, OOSnonresp,
OOSconstraintsviolation,
BecomingOOS, or
ForcedOOS.

The apH323SessionAgentStatsTable object has the OID [Link].4.1.9148.[Link].3, and the

apH323SessionAgentStatsEntry has the OID [Link].4.1.9148.[Link].3.1.

SNMP GET Query Name Object ID: Description

[Link].4.1.9148.[Link].3.1
+
apH323SAStatsSessionAgentIndex .1 A monotonically
increasing integer for
the sole purpose of
indexing session agents.
When it reaches the
maximum value the
agent wraps the value
back to 1.

4-66
Chapter 4
System Management MIB ([Link])

SNMP GET Query Name Object ID: Description

[Link].4.1.9148.[Link].3.1
+
apH323SAStatsSessionAgentHostname .2 The hostname of the
session agent for which
the following statistics
are being calculated.
apH323SAStatsSessionAgentType .3 The type of the specified
session agent, H323.
apH323SAStatsCurrentActiveSessionsInbound .4 Number of current active
inbound sessions.
apH323SAStatsCurrentSessionRateInbound .5 Current Inbound
Session rate in CPS.
apH323SAStatsCurrentActiveSessionsOutboun .6 Number of current active
d outbound sessions
apH323SAStatsCurrentSessionRateOutbound .7 Current outbound
session rate in CPS
apH323SAStatsTotalSessionsInbound .8 Total Number of inbound
sessions during the 100
second sliding window
period.
apH323SAStatsTotalSessionsNotAdmittedInbou .9 Total number of inbound
nd sessions rejected due to
insufficient bandwidth.
apH323SAStatsPeriodHighInbound .10 Highest number of
concurrent inbound
sessions during the 100
second sliding window
period.
apH323SAStatsAverageRateInbound .11 Average rate of inbound
sessions during the 100
second sliding window
period in CPS.
apH323SAStatsTotalSessionsOutbound .12 Total number of
outbound sessions
during the 100 second
sliding window period.
apH323SAStatsTotalSessionsNotAdmittedOutb .13 Total number of
ound outbound sessions
rejected because of
insufficient bandwidth.
apH323SAStatsPeriodHighOutbound .14 Highest number of
concurrent outbound
sessions during the 100
second sliding window
period.
apH323SAStatsAverageRateOutbound .15 Average rate of
outbound sessions
during the 100 second
sliding window period in
CPS.

4-67
Chapter 4
System Management MIB ([Link])

SNMP GET Query Name Object ID: Description

[Link].4.1.9148.[Link].3.1
+
apH323SAStatsMaxBurstRate .16 Maximum burst rate of
traffic measured during
the 100 second sliding
window period
(combined inbound and
outbound).
apH323SAStatsPeriodSeizures .17 Total number of seizures
during the 100 second
sliding window period.
apH323SAStatsPeriodAnswers .18 Total number of
answered sessions
during the 100 second
sliding window period.
apH323SAStatsPeriodASR .19 The answer-to-seizure
ratio, expressed as a
percentage. For
example, a value of 90
would represent 90%,
or .90.
apH323SAStatsAverageLatency .20 Average observed one-
way signalling latency
during the 100 second
sliding window period.
apH323SAStatsMaxLatency .21 Maximum observed
one-way signalling
latency during the 100
second sliding window
period
apH323SAStatsSessionAgentStatus .22 The current status of the
specified session agent,
which is expressed as
INS, OOSnonresp,
OOSconstraintsviolation
, BecomingOOS, or
ForcedOOS

The apSigRealmStatsTable object has the OID [Link].4.1.9148.[Link].4 and the

apSigRealmStatsEntry object has the OID [Link].4.1.9148.[Link].4.1.

Note:
This table is populated for realms on which H.323 and SIP are configured; this
supports aggregate statistics for H.323 and SIP.

4-68
Chapter 4
System Management MIB ([Link])

SNMP GET Query Name Object ID: Description

[Link].4.1.9148.[Link].4.1
+
apSigRealmStatsRealmIndex .1 A monotonically
increasing integer for
the sole purpose of
indexing realms.
When it reaches the
maximum value the
agent wraps the value
back to 1.
apSigRealmStatsRealmName .2 The name of the realm
for which the following
statistics are being
calculated.
apSigRealmStatsCurrentActiveSessionsInbound .3 Number of current
active inbound
sessions.
apSigRealmStatsCurrentSessionRateInbound .4 Current inbound
session rate in calls
per second (CPS)
during the sliding
window period. For
example, if the query
is made at 65th
second after SBC
application restart,
CPS from 36th to 65th
second is considered
for this statistics
calculation (sliding
window period = 30
sec).
apSigRealmStatsCurrentActiveSessionsOutbound .5 Number of current
active outbound
sessions.
apSigRealmStatsCurrentSessionRateOutbound .6 Current outbound
session rate in calls
per second (CPS)
during the sliding
window period. For
example, if the query
is made at 65th
second after SBC
application restart,
CPS from 36th to 65th
second is considered
for this statistics
calculation (sliding
window period = 30
sec).
apSigRealmStatsTotalSessionsInbound .7 Total number of
inbound sessions
during the 100 second
sliding window period.

4-69
Chapter 4
System Management MIB ([Link])

SNMP GET Query Name Object ID: Description

[Link].4.1.9148.[Link].4.1
+
apSigRealmStatsTotalSessionsNotAdmittedInbou .8 Total number of
nd inbound sessions
rejected because of
insufficient bandwidth.
apSigRealmStatsPeriodHighInbound .9 Highest number of
concurrent inbound
sessions during the
100 second sliding
window period.
apSigRealmStatsAverageRateInbound .10 Average rate of
inbound sessions
during the 100 second
sliding window period
in CPS.
apSigRealmStatsTotalSessionsOutbound .11 Total number of
outbound sessions
during the 100 second
sliding window period.
apSigRealmStatsTotalSessionsNotAdmittedOutbo .12 Total number of
und outbound sessions
rejected because of
insufficient bandwidth.
apSigRealmStatsPeriodHighOutbound .13 Highest number of
concurrent outbound
sessions during the
100 second sliding
window period.
apSigRealmStatsAverageRateOutbound .14 Average rate of
outbound sessions
during the 100 second
sliding window period
in CPS.

4-70
Chapter 4
System Management MIB ([Link])

SNMP GET Query Name Object ID: Description

[Link].4.1.9148.[Link].4.1
+
apSigRealmStatsMaxBurstRate .15 Burst rate of traffic
(both inbound and
outbound) measured
during the current
window period. The
time period is equal to
the value of the
configuration
parameter burst-rate-
window in the session
constraint. It is equal
to 1 if not configured.
Its value is the number
of active calls plus 1
divided by the time
period.

N
o
t
e
:
T
h
i
s
i
s
d
i
f
f
e
r
e
n
t
f
r
o
m
t
h
e
M
a
x
B
u
r

4-71
Chapter 4
System Management MIB ([Link])

SNMP GET Query Name Object ID: Description

[Link].4.1.9148.[Link].4.1
+

s
t
R
a
t
e
v
a
l
u
e
i
n
t
h
e
A
C
L
I
c
o
m
m
a
n
d
"
s
h
o
w
s
i
p
d
r
e
a
l
m
"
.
I
n
t
h
e
A
C
L
I
,
i

4-72
Chapter 4
System Management MIB ([Link])

SNMP GET Query Name Object ID: Description

[Link].4.1.9148.[Link].4.1
+

t
i
s
t
h
e
h
i
g
h
-
w
a
t
e
r
m
a
r
k
d
u
r
i
n
g
t
h
e
w
i
n
d
o
w
p
e
r
i
o
d
.

apSigRealmStatsPeriodSeizures .16 Total number of

seizures during the
100 second sliding
window period.
apSigRealmStatsPeriodAnswers .17 Total number of
answered sessions
during the 100 second
sliding window period.

4-73
Chapter 4
System Management MIB ([Link])

SNMP GET Query Name Object ID: Description

[Link].4.1.9148.[Link].4.1
+
apSigRealmStatsPeriodASR .18 The answer-to-seizure
ratio, expressed as a
percentage. For
example, a value of 90
would represent 90%,
or .90.
apSigRealmStatsAverageLatency .19 Average observed
(not supported) one-way signaling
latency in milliseconds
during the period.
apSigRealmStatsMaxLatency .20 Maximum observed
(not supported) one-way signaling
latency in milliseconds
during the period.
apSigRealmStatsMinutesLeft .21 Number of monthly-
minutes left in the pool
per calendar year for a
given realm.
apSigRealmStatsMinutesReject .22 Peg counts of the
number of calls
rejected because the
monthly-minutes
constraints are
exceeded.
apSigRealmStatsShortSessions .23 Lifetime number of
sessions whose
duration was less than
the configured short
session durations.
apSigRealmStatsAverageQoSRFactor .24 Average QoS factor
observed during the
period.
apSigRealmStatsMaximumQoSFactor .25 Maximum QoS factor
observed during the
period.
apSigRealmStatsCurrentMajorRFactorExceeded .26 Peg counts of the
number of times the
major Rfactor
threshold was
exceeded during the
period.
apSigRealmStatsTotalMajorRFactorExceeded .27 Peg counts of the
number of times the
major Rfactor
threshold was
exceeded during the
lifetime.
apSigRealmStatsCurrentCriticalRFactorExceeded .28 Peg counts of the
number of times the
critical Rfactor
threshold was
exceeded during the
period.

4-74
Chapter 4
System Management MIB ([Link])

SNMP GET Query Name Object ID: Description

[Link].4.1.9148.[Link].4.1
+
apSigRealmStatsTotalCriticalRfactorExceeded .29 Peg counts of the
number of times the
critical Rfactor
threshold was
exceeded during the
lifetime.
apSigRealmStatsRealmStatus .30 Current status of the
specified realm, which
is expressed as INS,
constraintviolation, or
callLoadReduction.
apSigRealmStatsActiveLocalContacts .31 An unsigned 32-bit
integer that specifies
the current domain
count of active SIP
registrations.
apSigRealmStatsActiveSubscriptions .32 Number of active
subscriptions for the
given realm.
apSigRealmStatsPerMaxSubscriptions .33 Lifetime PerMax
subscriptions count for
the given realm.
apSigRealmStatsMaximumActiveSubscriptions .34 Count of lifetime
maximum active
subscriptions for the
given realm.
apSigRealmStatsTotalSubscriptions .35 Count of lifetime total
subscriptions for the
system.

The apSysMgmtNetMgmtCtrlObjects object has the OID [Link].4.1.9148.[Link], the

apNetMgmtCtrlStatsTable object has the OID [Link].4.1.9148.[Link].1, and the
apNetMgmtCtrlStatsEntry object has the OID [Link].4.1.9148.[Link].1.1.

SNMP GET Query Name Object ID: Description

[Link].4.1.9148.[Link].1.1 +
apNetMgmtCtrlStatsName .1 Name of the network
management control (NMC)
the for which statistics are
being calculated.
apNetMgmtCtrlStatsType .2 Type of specified NMC: gap-
rate, gap-percent, or priority.
apNetMgmtCtrlStatsIncomingTotal .3 Total number of incoming
calls matching a destination
identifier of the NMC.
apNetMgmtCtrlStatsRejectedTotal .4 Number of
apNetMgmtCtrlStatsIncomin
gTotal that are rejected.
apNetMgmtCtrlStatsStatsDivertedTotal .5 Number of
apNetMgmtCtrlStatsIncomin
gTotal that are diverted.

4-75
Chapter 4
System Management MIB ([Link])

SNMP GET Query Name Object ID: Description

[Link].4.1.9148.[Link].1.1 +
apNetMgmtCtrlStatsStatsIncomingCurrent .6 Number of incoming calls
during the current period that
match a destination identifier
apNetMgmtCtrlStatsStatsRejectedCurrent .7 Number of
apNetMgmtCtrlStatsIncomin
gCurrent that are rejected.
apNetMgmtCtrlStatsStatsDivertedCurrent .8 Number of
apNetMgmtCtrlStatsIncomin
gCurrent that are diverted.
apNetMgmtCtrlStatsIncomingPeriodMax .9 Maximum number of
incoming calls during a
period that match a
destination identifier of the
NMC.
apNetMgmtCtrlStatsStatsRejectedPeriod .10 Number of
Max apNetMgmtCtrlStatsIncomin
gPeriodMax that are
rejected.
apNetMgmtCtrlStatsStatsDivertedPeriodM .11 Number of
ax apNetMgmtCtrlStatsIncomin
gPeriodMax that are
diverted.
apNetMgmtCtrlStatsState .12 The state of the specified
network management
control, which can be
disabled or enabled

The apSysMgmtMIBENUMServerStatusObjects object has the OID [Link].4.1.9148.[Link],

the apENUMServerStatusTable object has the OID [Link].4.1.9148.[Link].1, and the
apENUMServerStatusEntry object has the OID [Link].4.1.9148.[Link].1.1.

SNMP GET Query Object ID: Description

Name [Link].4.1.9148.[Link].1.1
+
apENUMConfigname .1 Name of the ENUM configuration element that
contains this ENUM server.
apENUMServerIpAddre .2 IP address of this ENUM server.
ss
apENUMServerStatus .3 Status of this ENUM server.

The apSysMgmtMIBNSEPStatsObjects object has the OID [Link].4.1.9148.[Link].

SNMP GET Query Name Object ID: Description

[Link].4.1.9148.[Link] +
apNSEPStatsCurentActiveSessionsInbo .1 Number of currently active
und inbound NSEP sessions.
apNSEPStatsTotalSessionsInbound .2 Total number of inbound NSEP
sessions during lifetime.
apNSEPStatsPeriodHighInbound .3 Highest number of concurrent
inbound NSEP sessions during
the period.

4-76
Chapter 4
System Management MIB ([Link])

SNMP GET Query Name Object ID: Description

[Link].4.1.9148.[Link] +
apNSEPStatsPeriod .4 The period for which all
statistics are collected (in
seconds). (Currently a non-
configurable value of 30
minutes.)
apNSEPStatsReserveCurrentSessions .6 Number of incoming NSEP
calls from reserved NSEP
session pool that occurred
during current time period
apNSEPStatsReservePeriodHigh .7 Maximum number of incoming
NSEP calls from reserved
NSEP session pool that
occurred during a single time
period.
apNSEPStatsReserveTotal .8 Total number of incoming
NSEP calls from reserved
NSEP session pool that
occurred during lifetime period.

The apNSEPStatsRPHTable object has the OID [Link].4.1.9148.[Link].5, and the

apNSEPStatsRPHEntry object has the OID [Link].4.1.9148.[Link].5.1.

SNMP GET Query Name Object ID: Description

[Link].4.1.9148.[Link].5.1
+
apNSEPStatsRPHValue .1 The specific RPH
value used for
indexing
([Link]).
apNSEPStatsRPHCurrentActiveSessionsInbound .2 Number of current
active inbound NSEP
sessions for this
specific RPH value.
apNSEPStatsRPHTotalSessionsInbound .3 Total number of
inbound NSEP
sessions for this
specific RPH value
during lifetime.
apNSEPStatsRPHPeriodHighInbound .4 Highest number of
concurrent
inbound NSEP
sessions during the
period for this specific
RPH value.
apNSEPStatsRPHTotalSessionsNotAdmittedInbou .5 Total number of
nd inbound NSEP
sessions rejected for
this specific RPH
value during lifetime.
apNSEPStatsRPHCurrentActiveSessionsOutbound .6 Number of current
active outbound
NSEP sessions for
this specific RPH
value.

4-77
Chapter 4
System Management MIB ([Link])

SNMP GET Query Name Object ID: Description

[Link].4.1.9148.[Link].5.1
+
apNSEPStatsRPHTotalSessionsOutbound .7 Total number of
outbound NSEP
sessions for this
specific RPH value
during lifetime.
apNSEPStatsRPHPeriodHighOutbound .8 Highest number of
concurrent outbound
NSEP sessions
during the period for
this specific RPH
value.
apNSEPStatsRPHTotalSessionsNotAdmittedOutbo .9 Total number of
und outbound NSEP
sessions rejected for
this specific RPH
value during lifetime

The apLDAPServerStatusTable object has the OID [Link].4.1.9148.[Link].1, and the

apLDAPServerStatusEntry object has the OID [Link].4.1.9148.[Link].1.1.

SNMP GET Query Object ID: Description

Name [Link].4.1.9148.[Link].1.
1+
apLDAPConfigName .1 Name of the LDAP configuration element that
contains this LDAP server.
apLDAPServerIPAddres .2 IP address of this LDAP server.
s
apLDAPServerStatus .3 Status of this LDAP server.

The apSysMgmtTrapTable object has the OID [Link].4.1.9148.[Link].1, and the

apSysMgmtTrapTableEntry object has the OID [Link].4.1.9148.[Link].1.1.

SNMP GET Query Name Object ID: Description

[Link].4.1.9148.[Link].1.1
+
apTrapTableSystemTime .1 System time of the session border controller.
apTrapTableInstanceInde .2 Instance index of the trap ID incremented with
x a resolution of a second.
apTrapTableNumVariable .3 Number of informarion encoded in the trap.
s
apTrapTableSysUptime .4 SNMP sysUpTime when the trap was
generated.
apTrapTableTrapID .5 Trap ID assoicated with the fault condition.

The apSysMgmtTrapInformationTable object has the OID [Link].4.1.9148.[Link].2, and the

apSysMgmtTrapInformationTableEntry object has the OID [Link].4.1.9148.[Link].2.1.

4-78
Chapter 4
System Management MIB ([Link])

SNMP GET Query Name Object ID: Description

[Link].4.1.9148.[Link].2.
1+
apTrapInformationTableDataInde .1 Index of the information encoded in the
x trap.
apTrapInformationTableDataType .2 SNMP type enumerated encoded in the
trap.
snmpTypeInteger is the size of integer
snmpTypeObjectIpAddress is an octet
string of length 4
apTrapInformationTableDataLen .3 Octet length of the information encoded
gth in the trap.
apTrapInformationTableDataOcte .4 Information represented in octets:
ts snmpTypeInteger,
snmpTypeObjectCounter32,
snmpTypeObjectGauge,
snmpTypeObjectOpaque, and
snmpUnsignedInteger32 are 4 octets
long
snmpType counter is 8 octets long
snmpTypeObjectIpAddress,
snmpTypeObjectNSAPAddress are 4
octets long
Data is aligned in network order.

The apSysMgmtInterfaceObjects object has the OID [Link].4.1.9148.[Link], the

apSysMgmtPhyUtilTable object has the OID [Link].4.1.9148.[Link].1, and the
apSysMgmtPhyUtilTableEntry object has the OID [Link].4.1.9148.[Link].1.1

SNMP GET Query Object ID: Description

Name [Link].4.1.9148.[Link].1.1 +
apPhyUtilTableRxUtil .1 RX network utilization of the physical port
measured over a one second period.
apPhyUtilTableTxUtil .2 TX network utilization of the physical port
measured over a one second period

Notes on ENUM Server Names

Note that the characters of the name are given in the ASCII values because of SNMP’s
restrictions. This representation affects the order in which entries in the table appear. Entries
are listed:
• By the length of their names
• Then by a comparison of the characters they contain; this comparison is not limited to
alphabetical order in that uppercase letter precede lowercase characters
• Last, by the IP address of the server for that entry
Take, for example, the case where there are three ENUM configurations:
• aaa, with servers [Link] and [Link]
• BBB, with servers [Link] and [Link]
• cc, with server [Link]

4-79
Chapter 4
Software Inventory MIB ([Link])

The entries would appear in the following order, with the following instance IDs:
1. cc [Link] would appear first because cc is the shortest name), and would be represented
by the instance ID: … .[Link].2.2.2
2. BBB entries would be next, sorted by IP address, because “BBB” is considered less than
aaa, and would be represented by the instance IDs: … .[Link].[Link] and
… .[Link].[Link]
3. aaa entries would appear last, represented by the instance IDs: ... .[Link].[Link]
and ... .[Link].[Link]

Software Inventory MIB ([Link])

The following table describes the SNMP GET query names for the Software Inventory MIB (ap-
[Link]).

SNMP GET Query Object ID: Description

Name [Link].4.1.9148.[Link].1.1 +
apSwBootDescr .2 Description of the software image which may
consist of a filename, data and time this image
was built or the unique identifier of the software.
For example:
boot image: [Link]/[Link] for host
address is [Link], and image name is
[Link]
boot image: /tffs0/[Link] for boot from flash 0
and image name is [Link]
boot loader: bank0:03/18/2005 [Link] for boot
from bank 0, and version is March 18 2005,
[Link]’.
apSwBootType .3 Type of software image. A value of 1 indicates a
boot Image. A value of 2 indicates a bootloader
image.
apSwBootStatus .4 Status of the software image. A value of 1
indicates an image that is currently being used. A
value of 2 indicates a previously used image.

The object apSwInventoryCfgObjects has the OID [Link].4.1.9148.[Link].

SNMP GET Query Name Object ID: Description

[Link].4.1.9148.[Link] +
apSwCfgCurrentVersion .1 Current version of the saved configuration.
apSwCfgRunningVersion .2 Current version of the running configuration.

The object apSwCfgBackupEntry has the OID [Link].4.1.9148.[Link].3.1.

SNMP GET Query Object ID: Description

Name [Link].4.1.9148.[Link].3.1 +
apSwCfgBackupName .2 Description of the configuration filename, for
example: p1604, 063004-cfg.

4-80
Chapter 4
Multicore Monitoring MIB ([Link])

Multicore Monitoring MIB ([Link])

A variety of statistics that report information on the CPUs/Cores within the Oracle
Communications Session Border Controller are available via the [Link] MIB.
These statistics are:

Object Name Object ID: Description

[Link].4.1.9148.3.17 +
apUsbcSysModule
apUsbcSysMIBObjects .1
apUsbcSysObjects .1.1
apUsbcSysCpuUtilAll .1.1.1 The percentage of total Cpu utilization.
apUsbcSysCpuCount .1.1.2 The number of cpus for this system.
apUsbcSysCpuSpeedMHz .1.1.3 The speed in MHz of the cpus for this
system.
apUsbcSysMemSzMB .1.1.4 The number of megabytes of all cpus
for this system.
apUsbcSysMemSzGB .1.1.5 The number of gigabytes of all cpus for
this system. This value is derived from
the apUsbcSysMemSzMB object.
apUsbcSysAppMemUtil .1.1.6 The number of megabytes of memory
used by the applications.
apUsbcSysKernelMemUtil .1.1.7 The number of megabytes of memory
used by the kernel.
apUsbcSysMyBogoMips .1.1.8 The processor speed measured in
millions of instructions per second per
processor, calculated by the kernel at
boot time.
apUsbcSysAllBogoMips .1.1.9 The sum of all bogo mips(millions of
instructions per second) of all cpus for
this system.
apUsbcSysCpuTblObjects .1.1.10
apUsbcSysCpuTable .[Link] A read-only table to hold information
for a cpu indexed by the cpu number i
+ 1.
apUsbcSysCpuEntry .[Link].1 A entry designed to hold the status of
a single Cpu.
apUsbcSysCpuNum .[Link].1.1 The cpu number + 1 of this entry.
apUsbcSysCpuUtil .[Link].1.2 The percent of cpu utilization of this
cpu.
apUsbcSysSmMsgRate .[Link] Session Manager SIP Messages,
Enum Messages, and Cx Diameter
messages per second
apUsbcSysThreadObjects .1.2 A collection of objects providing the
USBC thread level statistics.
apUsbcThreadUsageTableO .1.2.1 An identifier provided for each object
bject in the thread usage table.
apUsbcThreadUsageTable .[Link] A table to hold the thread usage
information, on a Session Border
Controller.

4-81
Chapter 4
Multicore Monitoring MIB ([Link])

Object Name Object ID: Description

[Link].4.1.9148.3.17 +
apThreadUsageEntry .[Link].1 A table entry designed to hold the
thread usage information, on a
Session Border Controller.
apThreadId .[Link].1.1 The instance index of the thread.
apThreadName .[Link].1.2 The name of the thread.
apThreadCurrentUsage .[Link].1.3 The current cpu usage of the thread.
Multiply by 100 from % value.
apThreadOverloaded .[Link].1.4 Indicator if thread is in overload
control.
apUsbcThreadEventTableO .1.2.2 An object within the table holding
bject thread event information.
apUsbcThreadEventTable .[Link] A table to hold the thread event
information, on a Session Border
Controller. These are all read only.
apThreadEventEntry .[Link].1 A table entry designed to hold the
thread event information, on a Session
Border Controller.
apThreadEventPendingCurr .[Link].1.1 The event pending Active counter.
ent
apThreadEventPendingCurh .[Link].1.2 The event pending High counter.
igh
apThreadEventPendingWind .[Link].1.3 The event pending window.
ow
apThreadEventPendingTotal .[Link].1.4 The event pending Total counter.
apThreadEventPendingMaxi .[Link].1.5 The event pending PerMax counter.
mum
apThreadEventPendingHigh .[Link].1.6 The event pending High counter.
apThreadEventDroppedCurr .[Link].1.7 The event dropped Active counter.
ent
apThreadEventDroppedCur .[Link].1.8 The event dropped High counter.
high
apThreadEventDroppedWin .[Link].1.9 The event dropped window.
dow
apThreadEventDroppedTota .[Link].1.10 The event dropped Total counter.
l
apThreadEventDroppedMax .[Link].1.11 The event dropped PerMax counter.
imum
apThreadEventDroppedHigh .[Link].1.12 The event dropped High counter.
apThreadLatencyPendingAv .[Link].1.13 The thread average latency.
erage
apThreadLatencyPendingM .[Link].1.14 The thread max latency.
ax
apThreadLatencyProcessin .[Link].1.15 The thread average latency.
gAverage
apThreadLatencyProcessin .[Link].1.16 The thread max latency.
gMax
apUsbcSipObjects .1.2.3 An object grouping SIPD-related per-
thread CPU utilization information.
apSipNumberOfThreads .[Link] Number of SIP threads.
apSipAverageCpuUtil .[Link] Average CPU utilization.

4-82
Chapter 4
Multicore Monitoring MIB ([Link])

Object Name Object ID: Description

[Link].4.1.9148.3.17 +
apSipPendingAverageLaten .[Link] The average latency of SIP Pending
cy events.
apSipPendingMaxLatency .[Link] The max latency of SIP Pending
events.
apSipProcessingAverageLat .[Link] The average latency of SIP Processing
ency events.
apSipProcessingMaxLatenc .[Link] The max latency of SIP Processing
y events.
apUsbcAtcpObjects .1.2.4 An object grouping ATCP-related per-
thread CPU utilization information.
apAtcpNumberOfThreads .[Link] Number of ATCP threads.
apAtcpAverageCpuUtil .[Link] Average CPU utilization.
apAtcpPendingAverageLate .[Link] The average latency of ATCP Pending
ncy events.
apAtcpPendingMaxLatency .[Link] The max latency of ATCP Pending
events.
apAtcpProcessingAverageL .[Link] The average latency of ATCP
atency Processing events.
apAtcpProcessingMaxLaten .[Link] The max latency of ATCP Processing
cy events.
apUsbcMbcdObjects .1.2.5 An object grouping MBCD-related per-
thread CPU utilization information.
apMbcdNumberOfThreads .[Link] Number of MBCD threads.
apMbcdAverageCpuUtil .[Link] Average CPU utilization.
apUsbcEbmdObjects .1.2.6
apEbmdNumberOfThreads .[Link] Number of EBMD threads.
apEbmdAverageCpuUtil .[Link] Average CPU utilization.
apUsbcDnsObjects .1.2.7
apDnsNumberOfThreads .[Link] Number of DNS threads.
apDnsAverageCpuUtil .[Link] Average CPU utilization.
apUsbcSysThreadNotRespo System Thread is not responding
ndingTrap

This MIB reflects statistics displayed by the show platform cpu, show platform cpu-load,
and show platform memory commands. The following screen capture is annotated with the
correspondence.

ORACLE#show platform cpu

CPU count : 8 //apUsbcSysCpuCount
CPU speed : 2301 MHz //apUsbcSysCpuSpeedMHz
CPU model : Intel(R) Core(TM) i7-3615QE CPU @ 2.30GHz
CPU flags : [...]

CPU workload: Capacity : 80000 bogoMIPS //apUsbcSysAllBogoMips

App load : 4599 bogoMIPS //apUsbcSysMyBogoMips

ORACLE> show platform cpu-load

Total load: 9% //apUsbcSysCpuUtilAll
CPU#00 4% //apUsbcSysCpuNum + apUsbcSysCpuUtil
CPU#01 13% //apUsbcSysCpuNum + apUsbcSysCpuUtil

4-83
Chapter 4
Multicore Monitoring MIB ([Link])

ORACLE> show platform memory Mem

Total : 1892 MB //apUsbcSysMemSzMB Mem App : 213 MB //apUsbcSysAppMemUtil Mem
OS : 849 MB //apUsbcSysKernelMemUtil

apUsbcSysDPDKObjects
This group of objects, found in the [Link], provide a listing of DPDK statistics.

MIB Object Object ID: Description

[Link].4.1.9148.[Link].13 +
apUsbcSysDPDKFwdPurpose .1 A bitset representing Forwarding
cores. 1s represent forwarding
cores, while 0s represent non-
forwarding cores.
apUsbcSysDPDKDOSPurpose .2 A bitset representing DoS cores.
Bits set to 1 represent DoS cores,
while 0s represent non-DoS
cores.
apUsbcSysDPDKSigPurpose .3 A bitset representing signaling
cores. Bits set to 1 represent
signaling cores, while 0s
represent non-signaling cores.
apUsbcSysDPDKTransPurpose .4 A bitset representing transcoding
Cores. Bits set to 1 represent
transcoding cores, while 0s
represent non-transcoding cores.
apUsbcSysDPDKCmdLine .5 System CmdLine string - as
defined in /proc/cmdline.
(including relevant bootparams.)
apUsbcSysDPDKFileMem .6 Total DPDK File Memory.
apUsbcSysDPDKSysMem .7 Total DPDK System Memory
apUsbcSysDPDKNum1G .8 Number of 1GB Hugepages
allocated.
apUsbcSysDPDKNum2MB .9 Number of 2MB hugepages
allocated.
apUsbcSysDPDKHypervisorType .10 The description regarding the
system type and what hypervisor
the system is running on (OVM,
KVM, VMWare,...).
apUsbcSysDPDKAddFwdCores .11 Number of additional cores that
may be used for forwarding.
apUsbcSysDPDKAddSigCores .12 Number of additional cores that
may be used for signaling.
apUsbcSysDPDKAddTransCores .13 Number of additional cores that
may be used for transcoding.

apUsbcSysScalingObjects
This group of objects, found in the [Link], provide a listing of objects relating to
scaling VMs.

4-84
Chapter 4
Multicore Monitoring MIB ([Link])

MIB Object Object ID: Description

[Link].4.1.9148.[Link].12+
apUsbcSysEstSessions .1 Estimated number of unecrypted
media sessions.
apUsbcSysEstG711G729Trans .2 Estimated number of G711<-
>G729 transcoded media
sessions.
apUsbcSysEstSigTPS .3 Estimated number of signaling
TPS.
apUsbcSysEstACLs .4 Estimated number of ACLs.
apUsbcSysEstTCP .5 Estimated number of TCP
connections.
apUsbcSysEstTLS .6 Estimated number of TLS
connections.
apUsbcSysEstVLANs .7 Estimated number of VLANs.

4-85
5
SNMP-based Application Features
This chapter contains Oracle Communications Session Border Controller features that involve
SNMP reporting on application activity.

SNMP Reporting of Message Rate Statistics

The message rate statistics feature enables the system to provide message rate statistics for
SIP, DNS, and ENUM traffic via ACLI and HDR output. These statistics can be retrieved via
SNMP.
Message rate statistics are available through four tables. These tables correspond to SIP
Method message rate per SIP Interface, SIP Method message rate per SIP Agent, DNS ALG
message rate, and ENUM server message rate. Ensure that the following parameters are
enabled for the type of statistics you wish to collect:

Statistic Type configuration element parameter

SIP Message Rate sip-config extra-method-stats
DNS Message Rate media-manager, dns-config extra-dnsalg-stats
ENUM Message Rate sip-config extra-enum-stats

Note:
Enabling extra-method-stats performs additional functions. Refer to this parameter's
description in the ACLI Reference Guide to see what other functionality you are
enabling.

apSIPRateIntfStatsTable
This table, found in the [Link], provides a listing of SIP message rate statistics per SIP
interface. It conveys the same information displayed in the show sipd rate interface
command. The table is indexed by the SIP Interface index and SIP method. The SIP Interface
to index number mapping is found in the apSipInterfaceTable in [Link]. The SIP method to
index mapping is found in the ApSipMethod object in [Link].

apSIPRateAgentStatsTable
This table, found in the [Link], provides a listing of SIP message rate statistics per SIP
agent (SIP session agent). It conveys the same information displayed in the show sipd rate
agent command. The table is indexed by the SIP agent index and SIP method. The SIP Agent
to index number mapping is found in the apSipAgentTable in [Link]. The SIP method to
index mapping is found in the ApSipMethod object in [Link].

5-1
Chapter 5
SNMP Reporting of Message Data Counters

apDnsAlgServerRateStatsTable
This table, found in the [Link], provides a listing of message rate statistics for a
specific DNS Alg Server. It conveys the same information displayed in the show dnsalg rate
realm-id and show dnsalg rate server-ip-addr commands. The table is indexed by the DNS
ALG realm index and DNS ALG server index. The table of rate statistics also includes the DNS
ALG server IP address and IP address type (IPv4 or IPv6). If a DNS ALG client realm, DNS
ALG server, and IP address are not configured, then the combination of those indices will
return no data. The DNS ALG Server to index mapping is found in the apDnsAlgServerTable in
the [Link]. The DNS ALG realm to index mapping is found in the
apDnsAlgConfigTable in the [Link].

apEnumServerRateStatsTable
This table, found in the [Link], provides a listing of ENUM message rate statistics for a
specific ENUM server. It conveys the same information displayed in the show enum rate
command. This table is indexed by the ENUM configuration name, ENUM Server IP address
and IP address type (IPv4 or IPv6).

SNMP Reporting of Message Data Counters

The message data counter statistics feature enables the system to provide message rate
statistics for Call Duration, Call Termination and SIP Methods output. These statistics can be
retrieved via SNMP.

Call Duration Counters for SNMP Retrieval

Call duration counters are available by way of SNMP retrieval. These counters are the same
as that reported by the show sipd agents and show sipd realms commands. The pertinent
MIB objects are found in the [Link] file.
The applicable Call Duration counters and tables include:
• apSipSACallInfoStatusTable, which contains:
– apSipSAStatsTotalCallDurationInbound
– apSipSAStatsTotalCallDurationOutbound
• apSigRealmCallInfoStatusTable, which contains:
– apSigRealmStatsTotalCallDurationInbound
– apSigRealmStatsTotalCallDurationOutbound

Local and Remote Call Termination (BYE) Counters for SNMP Retrieval
Local and Remote Call Termination (BYE) counters are available by way of SNMP retrieval.
These counters are the same as that reported by the show sipd agents and show sipd
realms commands. The pertinent MIB objects are found in the [Link] file.
• apSipSaCallInfoStatusTable, including the Call Termination (BYE) counters:
– apSipSAStatsTotalCallDropsNormal
– apSipSAStatsTotalCallDropsLocal

5-2
Chapter 5
SNMP Reporting of Message Data Counters

• apSigRealmCallInfoStatusTable, including the Call Duration counters:

– apSigRealmStatsTotalCallDropsNormal
– apSigRealmStatsTotalCallLocal

SIP Method Counters for SNMP Retrieval

Global SIP method counters are available by way of SNMP retrieval. These SIP Method
counters are the same as that reported by the show sipd <method> command. The pertinent
MIB objects are found in the [Link] file.
The apSipMethodStatsTable holds counters:
• apSipMethodStatsEventCount for each SIP method.
• apSipMethodStatsIndex, whether that SIP method is from server- or client- transaction
perspective.
• apSipMethodStatsTransType, and the returned SIP response code.
• apSipMethodStatsEventCode associated with that method transaction and perspective.

SRVCC Objects for SNMP Retrieval

SRVCC counters are available from the apSipSRVCCStatsobjects. The OID prefix is
[Link].4.1.9148.[Link].3 which is found in the [Link] file. The These counters
are the same as that reported by the show sipd srvcc command.
The apSipSRVCCStatsobjects contains numerous SRVCC statistics and corresponds to the
show sipd srvcc command and the sip-srvcc HDR group.

Rx Policy Server Objects for SNMP Retrieval

Rx policy server counters are available from the apDiamRxPolicyServerStatsTable. The OID
prefix is [Link].4.1.9148.[Link].2.3 which is found in the [Link] file.

The apDiamRxPolicyServerStatsTable contains numerous policy server statistics and

corresponds to the show policy-server stats command and the ext-Rx-policy-server HDR
group.
When system boots, every policy server object is assigned id which persists across
subsequent reboots. If policy server objects are deleted, the id does not change. This is similar
to how session agent objects have persistent indexing.

IKE Session Agent Objects for SNMP Retrieval

IKE Session Agent counters are available from apSecuritySAIKEStats. The OID prefix is
[Link].4.1.9148.3.9.5.1which is found in the [Link] file.

The apSecuritySAIKEStats contains numerous session agent statistics concerning IKE traffic
and corresponds to the show sa stats ike command and sa-ike HDR group.

IMS-AKA Session Agent Objects for SNMP Retrieval

IMS-AKA session agent counters are available from apSecuritySAIMSAKAStats. The OID
prefix is [Link].4.1.9148.[Link] which is found in the [Link] file.

5-3
Chapter 5
SNMP Reporting of Message Data Counters

The apSecuritySAIMSAKAStats contains numerous IMS-AKA session agent statistics and

corresponds to the show sa stats ims-aka all command and sa-imsaka HDR group.

SRTP Session Agent Objects for SNMP Retrieval

SRTP Session Agent counters are available from apSecuritySASRTPStats. The OID prefix is
[Link].4.1.9148.[Link] which is found in the [Link] file.

The apSecuritySASRTPStats contains numerous session agent statistics concerning SRTP

traffic and corresponds to the show sa stats srtp command and sa-srtp HDR group.

Transcoding Load Objects for SNMP Retrieval

Transcoding load and resource utilization counters are available in the [Link] file. There
are three groups which are presented, currently active transcoded session per licensed codec,
maximum licensed capacity per licensed codec, load per DSP.

Active Transcoded Sessions

The apCodecTranscodingResourceUtilMIBObjects, OID: [Link].4.1.9148.[Link] presents the
current number of active sessions of licensed codecs. This is found in [Link].

This object corresponds to show xcode load ACLI Command and xcode-codec-util HDR
group.

DSP Load of Transcoding Module

The apCodecTranscodingTCULoadStatsTable, OID: [Link].4.1.9148.[Link].1 presents a
table of the following information in [Link]:
• TCU identifier
• TCM Identifier
• DSP Identifier
• Session Count for that DSP
• Current load for that DSP
• Peak load for that DSP
• DSP Overload state

Note:
If the DSP is neither Active nor Overloaded then that DSP will not appear as an
instance of the table.

This object corresponds to show xcode load -detail ACLI Command and xcode-tcm-util HDR
group.

Licensed Codec Capacity

MIB Objects that present maximum capacity of licensed codecs are found in ap-
[Link], as part of the apLicenseEntry, OID:[Link].4.1.9148.[Link].1

5-4
Chapter 5
FQDN-resolved Session Agent Statistics SNMP Retrieval

This object corresponds to show xcode load ACLI Command and xcode-codec-util HDR
group.

FQDN-resolved Session Agent Statistics SNMP Retrieval

When FQDN-resolved Session Agent Statistics are enabled, you can retrieve each IP target's
session agent statistics via SNMP.
The apSipAgentTable returns a list of configured sessions agent with an index corresponding
and configuration name. The mapping of index to configuration name is persistent across
system reboot.
The index of the additional entries that correspond to the individual IP targets are identified by
starting at 10000000. Because the IP targets that are retrieved from the DNS server may
change on any DNS query, they are not persistent across a reboot. An snmpwalk query on
asSIPAgentTable appears as:

SNMPv2-SMI::enterprises.9148.[Link].[Link] = STRING: "[Link]"

SNMPv2-SMI::enterprises.9148.[Link].3.1.210000000 = STRING:
"[Link]#[Link]"
SNMPv2-SMI::enterprises.9148.[Link].3.1.210000001 = STRING:
"[Link]#[Link]"

The following snmpwalk query on asSipSessionAgentStatsTable appears as:

SNMPv2-SMI::enterprises.9148.[Link].[Link] = INTEGER: 36
SNMPv2-SMI::enterprises.9148.[Link].2.1.1.10000000 = INTEGER: 1000000
SNMPv2-SMI::enterprises.9148.[Link].2.1.1.10000001 = INTEGER: 1000001
SNMPv2-SMI::enterprises.9148.[Link].[Link] = STRING: "[Link]"
SNMPv2-SMI::enterprises.9148.[Link].2.1.2.10000000 = STRING:
"[Link]#[Link]"
SNMPv2-SMI::enterprises.9148.[Link].2.1.2.10000001 = STRING:
"[Link]#[Link]"
SNMPv2-SMI::enterprises.9148.[Link].[Link] = INTEGER: 1
SNMPv2-SMI::enterprises.9148.[Link].2.1.3.10000000 = INTEGER: 1
SNMPv2-SMI::enterprises.9148.[Link].2.1.3.1000001 = INTEGER: 1
SNMPv2-SMI::enterprises.9148.[Link].[Link] = Gauge32: 0
SNMPv2-SMI::enterprises.9148.[Link].2.1.4.10000000 = Gauge32: 0
SNMPv2-SMI::enterprises.9148.[Link].2.1.4.10000001 = Gauge32: 0
FQDN-resolved Session Agent Statistics SNMP Traps

The apSysMgmtSAStatusChangeTrap trap is generated when a session agent's individual IP

target changes state. The values populated in each of these trap's fields/varbinds include:
• [Link].[Link].0—System uptime
• [Link].[Link].4.1.0—OID of the trap
• [Link].4.1.9148.[Link].0—hostname/FQDN of the SA
• [Link].4.1.9148.[Link].0—IP address of the SA
• [Link].4.1.9148.[Link].0—state (Inservice/Out of Service)
• [Link].4.1.9148.[Link].0—status (Inservice/standby/Out of Service)

5-5
Chapter 5
CAC Utilization Statistics via SNMP

This feature requires that you enable the sa-routes-stats and sa-routes-traps parameters in
the sip-config. This feature also requires that the session agent's ping-all-addresses function
be active.

CAC Utilization Statistics via SNMP

TheOracle Communications Session Border Controller allows you to retrieve information on
current session utilization and burst rate as a percentage of their configured maximums on per
session-agent and/or realm basis. The Oracle Communications Session Border Controller
uses the configured max-session and max-burst-rate settings in conjunction with a
percentage formula to calculate this value. The system also uses an ACLI configuration setting
to establish the threshold at which trap and trap clear messages are sent from the SNMP
agent to the configured manager(s).
The user must load the MIB version associated with this software version on all pertinent
SNMP managers to query these CAC utilization (occupancy) values and interpret the traps. In
addition, the user must configure the threshold at which the system generates the CAC
utilization trap. Note that the corresponding clear trap uses the same threshold setting, sending
the clear trap when utilization falls below 90% of the threshold.

SNMP Get for CAC Utilization

Using a MIB browser, the user can query the current percentage utilization values for both
max-session and max-burst-rate for any session-agent or realm. The calculations for these
utilization levels are:
• Session utilization level = (current session count * 100 ) / max-sessions
• Burst rate utilization level = (current burst rate * 100 ) / max-burst-rate
The MIB objects associated with these statistics are parallel for session agent and realm and
include a table to contain the objects, an object associating the objects containing the values
with the applicable table, and objects containing the values themselves. These objects are
listed below.
The MIB objects containing CAC utilization data for Session Agents are listed below.
The object establishing the statistics table for session agent CAC utilization follows:

--apSip Session Agent Connection Admission Control Stats Table

apSipSaCacStatsTable OBJECT-TYPE
SYNTAX SEQUENCE OF ApSipSaCacStatsEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"SIP Session Agent Connection Admission Control Stats Table."
::= { apSipMIBTabularObjects 5 }

The object establishing the session agent CAC utilization statistics objects follows:

apSipSaCacStatsEntry OBJECT-TYPE
SYNTAX ApSipSaCacStatsEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Connection Admission Control Statistics."

5-6
Chapter 5
CAC Utilization Statistics via SNMP

AUGMENTS { apSipSessionAgentStatsEntry }
::= { apSipSaCacStatsTable 1 }
The session agent CAC utilization statistics values include:
ApSipSaCacStatsEntry ::= SEQUENCE {
apSipSaCacSessionUtilLevel Gauge32,
apSipSaCacBurstRateUtilLevel Gauge32
}

The above objects, specifying the CAC utilization value for sessions and burst rate utilization
for session agents include:

apSipSaCacSessionUtilLevel OBJECT-TYPE
SYNTAX Gauge32
UNITS "percentage"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Current session utilization level."
::= { apSipSaCacStatsEntry 1 }
apSipSaCacBurstRateUtilLevel OBJECT-TYPE
SYNTAX Gauge32
UNITS "percentage"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Current burst rate utilization level."
::= { apSipSaCacStatsEntry 2 }

The MIB objects containing CAC utilization data for Realms are listed below.
The object establishing the statistics table for realm CAC utilization follows:

--apSig Realm Connection Admission Control Stats Table

apSigRealmCacStatsTable OBJECT-TYPE
SYNTAX SEQUENCE OF ApSigRealmCacStatsEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Realm Connection Admission Control Stats Table."
::= { apSipMIBTabularObjects 6 }

The object establishing the realm CAC utilization statistics objects follows:

apSigRealmCacStatsEntry OBJECT-TYPE
SYNTAX ApSigRealmCacStatsEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Connection Admission Control Statistics."
AUGMENTS { apSigRealmStatsEntry }
::= { apSigRealmCacStatsTable 1 }

5-7
Chapter 5
CAC Utilization Statistics via SNMP

The session agent CAC utilization statistics values include:

ApSigRealmCacStatsEntry ::= SEQUENCE {

apSigRealmCacSessionUtilLevel Gauge32,
apSigRealmCacBurstRateUtilLevel Gauge32
}

The above objects, specifying the CAC utilization value for sessions and burst rate utilization
for realms include:

apSigRealmCacSessionUtilLevel OBJECT-TYPE
SYNTAX Gauge32
UNITS "percentage"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Current session utilization level."
::= { apSigRealmCacStatsEntry 1 }
apSigRealmCacBurstRateUtilLevel OBJECT-TYPE
SYNTAX Gauge32
UNITS "percentage"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Current burst rate utilization level."
::= { apSigRealmCacStatsEntry 2 }

CAC Utilization Traps

TheOracle Communications Session Border Controller can issue a trap when either the value
of max-session or CAC burst rate exceeds a configured value. The system only sends one trap
when the threshold is exceeded. When the value falls back under 90% of this threshold, the
Oracle Communications Session Border Controller sends a clear trap.
You configure the value that triggers these traps as a percentage of the max-session and max-
burst-rate settings configured for the applicable session agent and/or realm. The system uses
the same setting to specify when to send both the sessions and burst rate traps. The name of
this parameter is the cac-trap-threshold.
For realms, you configure a session-constraint element with the cac-trap-threshold setting
and apply that session constraint to the realm. For a session agent however, you configure the
cac-trap-threshold directly within the session agent's configuration. You must express the
value as a number less than 100. There is no default setting; the system does not generate a
trap if you have not configured this setting.
The apSipCACUtilAlertTrap identifies the threshold exceeded on a per-element and per-value
(session count or burst rate) for each trap, including:
• apSipSaCacSessionUtilLevel
• apSipSaCacBurstRateUtilLevel
• apSipRealmCacSessionUtilLevel
• apSipRealmCacBurstRateUtilLevel
Trap OIDs include:

5-8
Chapter 5
External Policy Server Connection Status Reporting

• apSipCACUtilAlertTrap—[Link].4.1.9148.[Link].2.0.1
• apSipCACUtilClearTrap—[Link].4.1.9148.[Link].2.0.2

External Policy Server Connection Status Reporting

When the Oracle Communications Session Border Controller (SBC) loses connection to the
external policy server or an attempt is unsuccessful, the SBC generates an SNMP trap. In
addition to this trap, the SBC generates major or minor, non-health effecting alarms. When a
connection is restored, the SBC sends a clear trap and clears the associated alarm.

Note:
The SBC does not raise SNMP traps or connection down alarms when you cause the
event with a configuration change, such as disabling a server element.

Enterprise Traps
The following table identifies the proprietary traps that the ap-diameter supports.

Trap Name Description

apSysMgmtExtPolicyServerConnDownTrap Generated when the SBC is unable to connect to
[Link].4.1.9148.[Link].74 an external policy server
apSysMgmtExtPolicyServerConnEstTrap Generated when the SBC is able to re-establish a
[Link].4.1.9148.[Link].75 connection with an external policy server

These traps contain the following information:

• Name of the policy server as it is configured on the SBC
• FQDN of the policy server cluster (This is left empty if the policy server is entered as an IP
address)
• IP Address and port of the active policy server in the form <IP-Address>:<Port>
• Realm to which the policy server belongs
• Operation type (RACF/CLF) of the policy server
A connection is deemed successful when the Diameter CER/CEA transaction completes. In
the case of FQDN, a connection-established trap is sent when each policy server in the top-
level cluster completes its CER/CEA action.
During a reboot, a connection-down trap is sent initially. An attempt is made to connect; if the
attempt is successful, a connection-established trap is sent. Upon every subsequent failed
attempt to establish a connection, the SBC makes another attempt without an additional trap.
During a switchover, the newly activated SBC behaves in the same way as a reboot process.
Initially, a connection down trap is sent. An attempt is made to connect; if the attempt is
successful, a connection-established trap is sent. After the switchover, and upon every
subsequent failed attempt to establish a connection, the SBC makes another attempt without
an additional trap.
In the event that a transport protocol connection is established but a Diameter connection is
unsuccessful, the existing connection is closed and a connection down trap is sent.

5-9
Chapter 5
External Policy Server Connection Status Reporting

Alarms
Alarms that correspond with the traps above notify the user, as follows:
• When the SBC sends a connection down trap for a connection configured within a policy
server cluster, it generates a minor alarm.
• When the SBC sends a connection down trap for a connection configured with an IP
address and port, it generates a minor alarm.
• When the diameter connection is re-established, the SBC clears the alarm.
• When all connections associated with a single ext-policy-server are down, the SBC
generates a major alarm.
The table below shows alarm information associated with a failed connection to an ext-policy-
server.

Name/ID Severity/Health Cause(s) Log Message Traps Generated

Degradation
APP_ALARM_EPS MINOR/0 Connection to External Policy apSysMgmtExtPoli
_RACF_CONN_FAI External Policy Server (RACF) cyServerConnDow
L Server is lost. connection lost!!! nTrap

You see this alarm using the display-alarms command.

ORACLE# display-alarms
1 alarms to show
ID Task Severity First Occurred Last Occurred
327689 97 4 2018-03-20 [Link] 2018-03-20 [Link]
Count Description
1 External Policy Server (RACF) connection lost!!!

When multiple server connections are lost, the alarm appears as follows:

ORACLE# display-alarms
1 alarms to show
ID Task Severity First Occurred Last Occurred
327689 97 4 2018-03-20 [Link] 2018-03-20 [Link]
Count Description
1 2 External Policy Server (RACF) connections lost!!!

The alarm definition is as follows:

• Definition: APP_ALARM_LOST_RACF_CONN - ID: 327689
• Text: External Policy Server (RACF) connection lost!!!
• Definition: APP_ALARM_LOST_CLF_CONN - ID: 327690
• Text: External Policy Server (CLF) connection lost!!!
These alarms remain cleared as long as all diameter connections are established. The alarm
text provides counts of the number of connections that are down, which the system updates as
connections go down or are re-established.
The alarm text differs, based on the number of servers down, as follows:
• External Policy Server (RACF) connection lost!!!" (one connection down)

5-10
Chapter 5
External Policy Server Connection Status Reporting

• 2 External Policy Servers (RACF) connection lost!!!" (more than one connection down)

5-11
A
System Alarms
A system alarm is triggered when a condition or event happens within either the system
hardware or software. Given a specific alarm, the 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 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).

Alarm Name Alarm Alarm Cause(s) Example Log Trap Generated (Trap
ID Severity Message Reference)
FAN STOPPED 65537 CRITICAL: Fan speed fan speed: apSyslogMessageGenera
any fan failure. XXXX, XXXX, ted
speed is NOTE: If this XXXX ([Link])
<50%. Or alarm occurs, (where xxxx apEnvMonStatusChange
speed of two the system xxxx xxxx is the Notification (ap-env-
or more fans turns up the revolutions per [Link])
is >50% and fan speed to minute (RPM)
apSysMgmtFanTrap (ap-
<75%. the fastest of each fan on
[Link])
MAJOR: possible the fan module)
speed of two speed.
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.

A-1
Appendix A

Alarm Name Alarm Alarm Cause(s) Example Log Trap Generated (Trap
ID Severity Message Reference)
TEMPERATURE 65538 apEnvMonFa Fans are Temperature: apSyslogMessageGenera
HIGH nState is set obstructed or [Link] C ted
to minor (M) stopped. The (where [Link] ([Link])
or critical (C) room is is the apEnvMonStatusChange
depending on abnormally temperature in Notification (ap-env-
the speed hot. degrees) [Link])
(RPM) of any
apSysMgmtTempTrap
fan.
([Link])
Acme Packet
4600/6100/6
300/6350:
• M: <
8000
• C: <
5000
(MINOR: a
fan is pulled)
Acme Packet
3950/4900:
• M: <
5500
inlets
• M: <
5000
outlets
• C: <
3666
inlets
• C: <
3333
outlets
Acme Packet
3900:
• M: <
6000
• C: <
4000
Acme Packet
1100:
• C: <
4000
Note: Fans
may not be
removed in
the field for
the Acme
Packet 3900
or 1100.
ENVIRONMENTA 65539 CRITICAL The Hardware apSyslogMessageGenera
L SENSOR environmental monitor failure! ted
FAILURE sensor Unable to ([Link])
component monitor fan apEnvMonI2CFailNotificat
cannot detect speed and ion
fan speed and temperature!
([Link])
temperature.

A-2
Appendix A

Alarm Name Alarm Alarm Cause(s) Example Log Trap Generated (Trap
ID Severity Message Reference)
PLD POWER A 65540 MINOR Power supply Back Power apSyslogMessageGenera
FAILURE A has failed. Supply A has ted
Note: PLD stands failed! ([Link])
for Programmable apEnvMonStatusChange
Logical Device Notification
([Link])
apSysMgmtPowerTrap
([Link])
PLD POWER A 65541 MINOR Power supply Back Power apSyslogMessageGenera
UP A is now Supply A is ted
Note: If the system present and present! ([Link])
boots up with one functioning. apEnvMonStatusChange
power supply, the Notification
health score is
([Link])
100, and an alarm
is not generated. If apSysMgmtPowerTrap
another power ([Link])
supply is then
added to that
same system, this
alarm is
generated, but the
health score is not
decremented.
PLD POWER B 65542 MINOR Power supply Back Power apSyslogMessageGenera
FAILURE B has failed. Supply B has ted
failed! ([Link])
apEnvMonStatusChange
Notification
([Link])
apSysMgmtPowerTrap
([Link])
PLD POWER B 65543 MINOR Power supply Back Power apSyslogMessageGenera
UP B is now Supply B is ted
Note: If the system present and present! ([Link])
boots up with one functioning. apEnvMonStatusChange
power supply, the Notification
health score is
([Link])
100, and an alarm
is not generated. If apSysMgmtPowerTrap
another power ([Link])
supply is then
added to that
same system, this
alarm is
generated, but the
health score is not
decremented.

A-3
Appendix A

Alarm Name Alarm Alarm Cause(s) Example Log Trap Generated (Trap
ID Severity Message Reference)
PHY0 Removed 65550 MAJOR Physical N/A apSyslogMessageGenera
interface card ted
0 was ([Link])
removed. apEnvMonStatusChange
Notification
([Link])
PHY0 Inserted 65552 MAJOR Physical N/A apSyslogMessageGenera
interface card ted
0 was inserted. ([Link])
apEnvMonStatusChange
Notification
([Link])
PHY1 Removed 65553 MAJOR Physical N/A apSyslogMessageGenera
interface card ted
1 was ([Link])
removed. apEnvMonStatusChange
Notification
([Link])
PHY1 Inserted 65554 MAJOR Physical N/A apSyslogMessageGenera
interface card ted
1 was inserted. ([Link])
apEnvMonStatusChange
Notification
([Link])

The following table lists the supported system alarms.

Alarm Name Alarm Alarm Causes Example Log Trap Generated (Trap
ID Severity Message Reference)
COMM MONITOR 327716 Major CommMonitor One or more apMonitorCollectorDown
CONNECTION (Hex disconnected CommMonitors Trap
DOWN 50024) are ([Link])
disconnected
LINK UP ALARM 131073 MINOR Gigabit Slot 0 port 0 UP linkUp (IETF RFC 2233)
GIGPORT Ethernet
interface 1
goes up.
LINK UP ALARM 131074 MINOR Gigabit Slot 1 port 0 UP linkUp(IETF RFC 2233)
GIGPORT Ethernet
interface 2
goes up.
LINK DOWN 131075 MAJOR Gigabit Slot 0 port 0 linkDown (IETF RFC
ALARM GIGPORT Ethernet DOWN 2233)
interface 1
goes down.
LINK DOWN 131076 MAJOR Gigabit Slot 1 port 0 linkDown (IETF RFC
ALARM GIGPORT Ethernet DOWN 2233)
interface 2
goes down.

A-4
Appendix A

Alarm Name Alarm Alarm Causes Example Log Trap Generated (Trap
ID Severity Message Reference)
LINK UP ALARM 131077 MINOR Control wancom0 UP linkUp (IETF RFC 2233)
VXINTF interface 0
goes up.
LINK UP ALARM 131078 MINOR Control wancom1 UP linkUp (IETF RFC 2233)
VXINTF interface 1
goes up.
LINK UP ALARM 131079 MINOR Control wancom2 UP linkUp (IETF RFC 2233)
VXINTF interface 2
goes up.
LINK DOWN 131080 MAJOR Control wancom0 linkDown (IETF RFC
ALARM VXINTF interface 0 DOWN 2233)
goes down.
LINK DOWN 131081 MAJOR Control wancom1 linkDown (IETF RFC
ALARM VXINTF interface 1 DOWN 2233)
goes down.
LINK DOWN 131082 MAJOR Control wancom2 linkDown (IETF RFC
ALARM VXINTF interface 2 DOWN 2233)
goes down.
LINK UP ALARM 131083 MAJOR Fast Ethernet Slot 0 port 0 UP linkUp (IETF RFC 2233)
FEPORT slot 0, port 0
goes up.
LINK UP ALARM 131084 MAJOR Fast Ethernet Slot 1 port 0 UP linkUp (IETF RFC 2233)
FEPORT slot 1, port 0
goes up.
LINK UP ALARM 131085 MINOR Fast Ethernet Slot 0 port 1 UP linkUp (IETF RFC 2233)
FEPORT slot 0, port 1
goes up.
LINK UP ALARM 131086 MINOR Fast Ethernet Slot 1 port 1 linkUp (IETF RFC 2233)
FEPORT slot 1, port 1 DOWN
up.
LINK UP ALARM 131087 MINOR Fast Ethernet Slot 0 port 2 UP linkUp (IETF RFC 2233)
FEPORT slot 0, port 2
goes up.
LINK UP ALARM 131088 MINOR Fast Ethernet Slot 1 port 2 UP linkUp (IETF RFC 2233)
FEPORT slot 1, port 2
goes up.
LINK UP ALARM 131089 MINOR Fast Ethernet Slot 0 port 3 UP linkUp (IETF RFC 2233)
FEPORT slot 0, port 3
goes up.
LINK UP ALARM 131090 MINOR Fast Ethernet Slot 1 port 3 UP linkUp (IETF RFC 2233)
FEPORT slot 1, port 3
goes up.
LINK DOWN 131091 MAJOR Fast Ethernet Slot 0 port 0 linkDown (IETF RFC
ALARM FEPORT slot 0, port 0 DOWN 2233)
goes down.
LINK DOWN 131092 MAJOR Fast Ethernet Slot 1 port 0 linkDown (IETF RFC
ALARM FEPORT slot 1, port 0 DOWN 2233)
goes down.
LINK DOWN 131093 MAJOR Fast Ethernet Slot 0 port 1 linkDown (IETF RFC
ALARM FEPORT slot 0, port 1 DOWN 2233)
goes down.

A-5
Appendix A

Alarm Name Alarm Alarm Causes Example Log Trap Generated (Trap
ID Severity Message Reference)
LINK DOWN 131094 MAJOR Fast Ethernet Slot 1 port 1 linkDown (IETF RFC
ALARM FEPORT slot 1, port 1 DOWN 2233)
goes down.
LINK DOWN 131095 MAJOR Fast Ethernet Slot 0 port 2 linkDown (IETF RFC
ALARM FEPORT slot 0, port 2 DOWN 2233)
goes down.
LINK DOWN 131096 MAJOR Fast Ethernet Slot 1 port 2 linkDown (IETF RFC
ALARM FEPORT slot 1, port 2 DOWN 2233)
goes down.
LINK DOWN 131097 MAJOR Fast Ethernet Slot 0 port 3 linkDown (IETF RFC
ALARM FEPORT slot 0, port 3 DOWN 2233)
goes down.
LINK DOWN 131098 MAJOR Fast Ethernet Slot 1 port 3 linkDown (IETF RFC
ALARM FEPORT slot 1, port 3 DOWN 2233)
goes down.
CPU UTILIZATION 131099 MINOR CPU usage CPU usage X% apSysMgmtGroupTrap
reached 90% over threshold ([Link])
or greater of its X%
capacity.
MEMORY 131100 CRITICAL Memory usage Memory usage apSysMgmtGroupTrap
UTILIZATION reached 90% X% over ([Link])
or greater of its threshold X%
capacity.
HEALTH SCORE 131101 MAJOR system’s Health score X apSysMgmtGroupTrap
health score is under ([Link])
fell below 60. threshold
(where X is the
health score)
NAT TABLE 131102 MINOR NAT table NAT table apSysMgmtGroupTrap
UTILIZATION usage reached usage X% over ([Link])
90% or greater threshold X%
of its capacity.
ARP TABLE 131103 MINOR ARP table ARP table X% apSysMgmtGroupTrap
UTILIZATION usage reached over threshold ([Link])
90% or greater X%
of its capacity.
REDUNDANT 131104 CRITICAL A state Switchover, apSyslogMessageGenera
SWITCH-TO- transition <state to ted
ACTIVE occurred from state>, active ([Link])
Standby/ peer <name of apSysMgmtRedundancyT
BecomingStan HA peer> has rap
dby to timed out or
([Link])
BecomingActiv Switchover,
e. <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

A-6
Appendix A

Alarm Name Alarm Alarm Causes Example Log Trap Generated (Trap
ID Severity Message Reference)
REDUNDANT 131105 CRITICAL A state Switchover, apSyslogMessageGenera
SWITCH-TO- transition <state to ted
STANDBY occurred from state>, peer ([Link])
Active/ <name of HA apSysMgmtRedundancyT
BecomingActiv peer> is rap
e to healthier (x)
([Link])
BecomingStan than us (x)
dby/ (where x is the
RelinquishingA health score)
ctive. or Switchover,
<state to
state>, forced
by command
REDUNDANT 131106 MAJOR An HA system Peer <name of apSyslogMessageGenera
TIMEOUT peer was not HA peer> timed ted
heard from out in state x, ([Link])
within the my state is x apSysMgmtRedundancyT
configured (where x is the rap
silence state (e.g.,
([Link])
window. BecomingStand
by))
REDUNDANT 131107 CRITICAL Unable to Unable to apSyslogMessageGenera
OUT OF SERVICE synchronize synchronize ted
Note: The with Active HA with Active ([Link])
activate-config system peer redundant peer apSysMgmtRedundancyT
failed log message within within rap
appears for those BecomingStan BecomingStand
([Link])
cases in which the dby timeout. by timeout,
execution of the going
activate config OutOfService
command failed or
on the standby activate-config
SBC. 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.

A-7
Appendix A

Alarm Name Alarm Alarm Causes Example Log Trap Generated (Trap
ID Severity Message Reference)
SYSTEM TASK 131108 CRITICAL A system task Task X apSyslogMessageGenera
SUSPENDED (process) suspended, ted
suspends or which ([Link])
fails. decremented apSysMgmtTaskSuspend
health by 75! Trap
(where X is the
([Link])
task/process
name)

The following table lists the supported media alarms.

Alarm Name Alarm Alarm Cause(s) Example Log Trap Generated (Trap
ID Severity Message Reference)
MBCD ALARM 262145 CRITICAL: No further Flow: Cannot apSyslogMessageGenera
OUT OF for flow memory can create free port ted
MEMORY MAJOR: for be allocated for list for realm. ([Link])
media (if MBCD. Media Server: apSysMgmtMediaOutofM
server cannot Failed to emory
allocate a allocate new
([Link])
new context) context.
MBCD ALARM 262147 MAJOR: if Media server is Realm type apSyslogMessageGenera
UNKNOWN media server unable to find (ingress, ted
REALM is adding a realm interface. egress, hairpin) ([Link])
new flow X, not found apSysMgmtUnknownReal
m
([Link])
MBCD ALARM 262149 CRITICAL: The realm is Out of apSyslogMessageGenera
OUT OF failure rate = out of bandwidth ted
BANDWIDTH 100% bandwidth. ([Link])
MAJOR: apSysMgmtMediaBandwi
failure rate > dthTrap
or = 50%
([Link])
MBCD ALARM 262150 CRITICAL: The realm is Out of steering apSyslogMessageGenera
OUT OF PORTS failure rate = out of steering ports ted
100% ports. ([Link])
MAJOR: apSysMgmtMediaPortsTr
failure rate > ap
or = 50%
([Link])
SRTP MAJOR Decryption for SRTP apSecuritySrtpDecryption
DECRYPTION SRTP packets Decryption FailureNotification
ERROR fails. Failed ([Link])
SRTP 327744 MAJOR Encryption SRTP apSecuritySrtpEncryption
ENCRYPTION integrity check Encryption FailureNotification
ERROR for SRTP Failed ([Link])
packets fails.
TLS MAJOR Decryption for TLS Decryption apSecurityTlsDecryptionF
DECRYPTION TLS packets Failed ailureNotification
ERROR fails. ([Link])
TLS MAJOR Encryption TLS Encryption apSecurityTlsEncryptionF
ENCRYPTION integrity check Failed ailureNotification
ERROR for TLS ([Link])
packets fails.

A-8
Appendix A

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 hexadecimal
number that represents the VLAN ID and the front interface port/slot numbers.

The following table lists the supported application alarms.

A-9
Appendix A

Alarm Name Alarm Alarm Cause(s) Example Log Trap Generated (Trap
ID Severity Message Reference)
RADIUS 327681 CRITICAL: if The enabled CRITICAL: All apSyslogMessageGenera
ACCOUNTING all enabled connections to enabled ted
CONNECTION and RADIUS accounting ([Link])
DOWN configured servers have connections apSysMgmtRadiusDownT
Remote timed-out have been lost! rap
Authenticatio without a Check
([Link])
n Dial-in User response from accounting
Service the RADIUS status for more
(RADIUS) server. details.
accounting MAJOR: One or
server more enabled
connections accounting
have timed- connections
out without have been lost!
response Check
from the accounting
RADIUS status for more
server details.
MAJOR: if
some, but not
all configured
RADIUS
accounting
server
connections
have timed-
out without
response
from the
RADIUS
server.
ENUM SERVER XX CRITICAL: The enabled CRITICAL: All apSysMgmtENUMStatus
STATUS All ENUM connections to ENUM Servers ChangeTrap
New to Release servers are ENUM servers are currently ([Link])
C5.0 unreachable have been lost. unreachable!
MAJOR: MAJOR: One or
Some ENUM more ENUM
servers are Servers are
unreachable currently
unreachable!
H.323 ALARM 327682 CRITICAL The H.323 [H.323 | IWF] apSyslogMessageGenera
STACK stack has failed stack <stack- ted
INITIALIZATION to initialize name> has ([Link])
FAILURE properly and is failed to ([Link])
terminated. initialize and is
terminated

The following table lists the supported configuration alarms.

A-10
Appendix A
Alarm Severities

Alarm Name Alarm Alarm Cause(s) Example Log Trap Generated (Trap
ID Severity Message Reference)
CFG ALARM 393217 MAJOR The save- save-config apSyslogMessageGenera
SAVE FAILED config failed on ted
command targetName!/ ([Link])
execution code full, config apSysMgmtCfgSaveFailTr
failed on a sync stopped! ap
standby SBC or
([Link])
peer operating save-config
as part of an failed on
HA pair. targetName!/
code full, config
sync stopped!
(where the
targetName is
the target name
(tn) configured
in the boot
parameters)

The following table lists the supported license alarms.

Alarm Name Alarm Alarm Cause(s) Example Log Trap Generated (Trap
ID Severity Message Reference)
LICENSE 50004 MAJOR Total session apSyslogMessageGenera
APPROACH count is ted
CAPACITY approaching ([Link])
the license apLicenseApproachingCa
capacity pacityNotification
allowed (98%
([Link])
or higher)
This alarm is
cleared when
total sessions
is less than
90% of license
capacity.

For additional information about system alarms for the components of the system, refer to the
Alarms section of the Monitoring via the ACLI chapter of the Administration and Configuration
Guide for the ACLI.

Alarm Severities
The system architecture includes five levels of alarm severity. These levels have been
designated so that the system can take action that is appropriate to the situation triggering the
alarm.

Alarm Severity Description

Emergency Requires immediate attention. If you do not attend to this condition immediately, there
will be physical, permanent, and irreparable damage to your system.
Critical System is inoperable, causing a complete loss of service in a production environment.
Requires attention as soon as it is noted.

A-11
Appendix A
Alarm Severities

Alarm Severity Description

Major Functionality has been seriously compromised. This situation might cause loss of
functionality, hanging applications, and dropped packets. If you do not attend to this
situation, your system will suffer no physical harm, but it will cease to function.
Minor Functionality has been impaired to a certain degree. As a result, you might experience
compromised functionality. You should attend to this type of alarm as soon as possible
in order to keep your system operating properly.
Warning Some irregularities in performance. This condition describes situations that are
noteworthy, however, you should attend to this condition in order to keep your system
operating properly. For example, this type of alarm might indicate the system is
running low on bandwidth and you may need to contact your Oracle customer support
representative to arrange for an upgrade.

A-12

Oracle SNMP - Support Reference Guide (2001)
No ratings yet
Oracle SNMP - Support Reference Guide (2001)
270 pages
SBC Scz730 HDR
No ratings yet
SBC Scz730 HDR
88 pages
HP P9000
No ratings yet
HP P9000
53 pages
Technical Document: Niagara SNMP Guide
No ratings yet
Technical Document: Niagara SNMP Guide
54 pages
Sun GlassFish Message Queue 4.4 Administration Guide
No ratings yet
Sun GlassFish Message Queue 4.4 Administration Guide
476 pages
Oracle Esbc-Release-Notes 9.2
No ratings yet
Oracle Esbc-Release-Notes 9.2
55 pages
Simphony Documentation F85293 - 03
No ratings yet
Simphony Documentation F85293 - 03
58 pages
Understanding SNMP for Network Management
100% (1)
Understanding SNMP for Network Management
31 pages
Overview of SNMP Protocol and Management
No ratings yet
Overview of SNMP Protocol and Management
31 pages
System Administration Toolkit:: Using SNMP Data
No ratings yet
System Administration Toolkit:: Using SNMP Data
10 pages
SNMP for Network Admins
No ratings yet
SNMP for Network Admins
10 pages
Understanding SNMP for Network Management
No ratings yet
Understanding SNMP for Network Management
29 pages
2.1 SNMP-1
No ratings yet
2.1 SNMP-1
14 pages
SNMP Agent Simulator Overview and Features
No ratings yet
SNMP Agent Simulator Overview and Features
7 pages
DCN - SNMP
No ratings yet
DCN - SNMP
31 pages
SNMP Tutorial: Managing Network Protocols
No ratings yet
SNMP Tutorial: Managing Network Protocols
28 pages
SNMP Management and MIB Overview
No ratings yet
SNMP Management and MIB Overview
28 pages
CNS Module 5
No ratings yet
CNS Module 5
16 pages
Network Manager Guide
No ratings yet
Network Manager Guide
22 pages
Hitachi Virtual Storage Platform VSP G10
No ratings yet
Hitachi Virtual Storage Platform VSP G10
58 pages
Network Management Protocols
No ratings yet
Network Management Protocols
35 pages
Multiple Application Integration Guide: Oracle ATG One Main Street Cambridge, MA 02142 USA
No ratings yet
Multiple Application Integration Guide: Oracle ATG One Main Street Cambridge, MA 02142 USA
34 pages
CP SNMP BestPracticesGuide
No ratings yet
CP SNMP BestPracticesGuide
40 pages
SNMP HW
No ratings yet
SNMP HW
11 pages
SNMP Guide
No ratings yet
SNMP Guide
16 pages
SNMP Tutorial: DR Pipat Sookavatana CPEN 1331
No ratings yet
SNMP Tutorial: DR Pipat Sookavatana CPEN 1331
44 pages
Understanding Simple Network Management Protocol
No ratings yet
Understanding Simple Network Management Protocol
64 pages
Monitor SNMP
No ratings yet
Monitor SNMP
36 pages
SNMP Paper Patrol
No ratings yet
SNMP Paper Patrol
63 pages
OPS Admin
No ratings yet
OPS Admin
198 pages
Support For Allied Telesis Enterprise Mibs in Alliedware Plus™
No ratings yet
Support For Allied Telesis Enterprise Mibs in Alliedware Plus™
138 pages
SNMP Guide for IT Infrastructure
No ratings yet
SNMP Guide for IT Infrastructure
22 pages
SC41-5412-00 Simple Network Management Protocol (SNMP) Support
0% (1)
SC41-5412-00 Simple Network Management Protocol (SNMP) Support
83 pages
22 SNMP Configuration
100% (1)
22 SNMP Configuration
17 pages
Lecture3 SNMP
No ratings yet
Lecture3 SNMP
29 pages
As400 SNMP
No ratings yet
As400 SNMP
324 pages
Pysnmp
No ratings yet
Pysnmp
26 pages
Overview of SNMP and Its Versions
100% (1)
Overview of SNMP and Its Versions
54 pages
SNMP - PPT - Brian Candler
No ratings yet
SNMP - PPT - Brian Candler
27 pages
Manual - SNMP Developers Guide
No ratings yet
Manual - SNMP Developers Guide
140 pages
SNMP Tutorial: Management Protocol Guide
No ratings yet
SNMP Tutorial: Management Protocol Guide
44 pages
SNMP Configuration Guide
No ratings yet
SNMP Configuration Guide
130 pages
Networking
No ratings yet
Networking
91 pages
01 System Administration Guide Basic
No ratings yet
01 System Administration Guide Basic
464 pages
How To Make Bootable Pen-Drive For Solaris 11
No ratings yet
How To Make Bootable Pen-Drive For Solaris 11
136 pages
OPS Security
No ratings yet
OPS Security
112 pages
Explanation of Mib's and SNMP Traps, When Configured With Unisphere For VMAX
No ratings yet
Explanation of Mib's and SNMP Traps, When Configured With Unisphere For VMAX
4 pages
Lec-3 NM SNMP
No ratings yet
Lec-3 NM SNMP
37 pages
Mar 2012
No ratings yet
Mar 2012
3 pages
Motion in 1-D - DPP 04 (Of Lec 06) - (2.0 2023 PW Star)
No ratings yet
Motion in 1-D - DPP 04 (Of Lec 06) - (2.0 2023 PW Star)
5 pages
Types of Sensors and Their Uses
No ratings yet
Types of Sensors and Their Uses
6 pages
Thermodynamics Question Bank
No ratings yet
Thermodynamics Question Bank
2 pages
IFRS E-Learning for Finance Pros
No ratings yet
IFRS E-Learning for Finance Pros
8 pages
Strategic Management Midterm Exam Question B Answer-2
No ratings yet
Strategic Management Midterm Exam Question B Answer-2
3 pages
Failed Intubation Drill Jan 10
100% (1)
Failed Intubation Drill Jan 10
1 page
Dissertations Aryman
No ratings yet
Dissertations Aryman
12 pages
Java - Linkedin Skill Assessments Quizzes
No ratings yet
Java - Linkedin Skill Assessments Quizzes
49 pages
High-Performance Speech Neuroprosthesis
No ratings yet
High-Performance Speech Neuroprosthesis
32 pages
Hershey's ERP Implementation Failure Analysis
100% (1)
Hershey's ERP Implementation Failure Analysis
31 pages
T Rec G.709.1 201701 S!!PDF e
No ratings yet
T Rec G.709.1 201701 S!!PDF e
30 pages
人工智能算法卷1 基础算法扫描版 1st Edition Jeffery Heaton Full Study Access
No ratings yet
人工智能算法卷1 基础算法扫描版 1st Edition Jeffery Heaton Full Study Access
55 pages
Internship Report: Finance at Pertamina
No ratings yet
Internship Report: Finance at Pertamina
41 pages
FET Mobility in Iodine-Doped P3HT
No ratings yet
FET Mobility in Iodine-Doped P3HT
6 pages
3-Cheese Pizza Recipe Lab Manual
No ratings yet
3-Cheese Pizza Recipe Lab Manual
3 pages
CNG Dispenser Service Manual v.1.1.6
No ratings yet
CNG Dispenser Service Manual v.1.1.6
129 pages
Paris Airport Car Rental Confirmation
No ratings yet
Paris Airport Car Rental Confirmation
2 pages
SAP General Ledger Migration Service - Overview Presentation
No ratings yet
SAP General Ledger Migration Service - Overview Presentation
30 pages
Microcontroller Programming Procedure For Vision 2286 v.2
No ratings yet
Microcontroller Programming Procedure For Vision 2286 v.2
11 pages
CGT Corporation Financial Analysis Quiz
No ratings yet
CGT Corporation Financial Analysis Quiz
3 pages
SCX1500A-3 Crane Specs & Capacities
100% (1)
SCX1500A-3 Crane Specs & Capacities
44 pages
PUC-II Chemistry Model Question Paper
100% (1)
PUC-II Chemistry Model Question Paper
8 pages
24 Philes and What They Mean... Which Philes Describes You?: Mike50 in Philes - 2 Years Ago (Edited)
No ratings yet
24 Philes and What They Mean... Which Philes Describes You?: Mike50 in Philes - 2 Years Ago (Edited)
23 pages
Rurouni Kenshin: The Beginning - AsianWiki - 1607227806486
No ratings yet
Rurouni Kenshin: The Beginning - AsianWiki - 1607227806486
5 pages
Road Alignment
100% (1)
Road Alignment
17 pages
Demonstration Models For Teaching Structural Mechanics: W. G. Godden
No ratings yet
Demonstration Models For Teaching Structural Mechanics: W. G. Godden
84 pages
Shaw, K.A., & Hagemans, I. (2015) - Gentrification Without Displacement' and The Consequent Loss of Place
No ratings yet
Shaw, K.A., & Hagemans, I. (2015) - Gentrification Without Displacement' and The Consequent Loss of Place
19 pages
What We Say Matters Practicing Nonviolent Communication ISBN 1645471047, 9781645471042 Full Book Download
No ratings yet
What We Say Matters Practicing Nonviolent Communication ISBN 1645471047, 9781645471042 Full Book Download
14 pages