AudioCodes Gateway & Session Border Controller Series
SimpleNetwork
ManagementProtocol
Mediant 800 Gateway & E-SBC
Version 7.2
Notice
Mediant 800 SBC | S NMP Reference Guide
Notice
Information contained in this document is believed to be accurate and reliable at the time
of printing. However, due to ongoing product improvements and revisions, AudioCodes
cannot guarantee accuracy of printed material after the Date Published nor can it accept
responsibility for errors or omissions. Updates to this document can be downloaded from
This document is subject to change without notice.
Date Published: November-09-2020
WEEE EU Directive
Pursuant to the WEEE EU Directive, electronic and electrical waste must not be disposed of
with unsorted waste. Please contact your local recycling authority for disposal of this product.
Customer Support
Customer technical support and services are provided by AudioCodes or by an authorized
AudioCodes Service Partner. For more information on how to buy technical support for
AudioCodes products and for contact information, please visit our website at
AudioCodes continually strives to produce high quality documentation. If you have any
comments (suggestions or errors) regarding this document, please fill out the Documentation
Feedback form on our website at https://online.audiocodes.com/documentation-feedback.
Stay in the Loop with AudioCodes
Related Documentation
Document Name
SBC-Gateway Series Release Notes for Latest Release Versions
SBC-Gateway Series Release Notes for Long Term Support Versions
HTTP Proxy NGINX Alarms145
Active Alarm Table Alarm148
Analog Port Alarms149
Analog Port SPI Out-of-Service Alarm149
Analog Port High Temperature Alarm150
Analog Port Ground Fault Out-of-Service Alarm151
Analog Line Left Off-hook Alarm152
Media Alarms152
Media Realm Bandwidth Threshold Alarm152
Call Quality Alarms153
Answer-Seizure Ratio Threshold Alarm153
Average Call Duration Threshold Alarm154
Network Effectiveness Ratio Threshold Alarm155
No Route to IP GroupAlarm156
Intrusion Detection Alarms157
IDS Policy Alarm157
SNMP Event Traps (Notifications)158
Intrusion Detection System (IDS)159
IDS Threshold Cross Notification Trap159
IDS Blacklist Notification Trap159
Web User Access Denied due to Inactivity Trap160
Web User Activity LogTrap161
Keep-Alive Trap162
- viii -
Content
Performance MonitoringThreshold-Crossing Trap162
HTTP Download Result Trap163
Dial Plan File Replaced Trap164
High-Availability (HA)165
Redundant Board Trap165
Hitless Software UpgradeStatus Trap166
SecureShell (SSH) Connection Status Trap167
SIP Proxy Connection Lost per Proxy Set Trap168
Cold Start Trap169
Authentication Failure Trap169
Board Initialization Completed Trap170
ConfigurationChange Trap170
Link Up Trap171
Link Down Trap171
Enhanced BIT Status Trap171
Mediant 800 SBC | S NMP Reference Guide
8 Advanced SNMP Features173
SNMP NAT Traversal173
Systems173
High-Availability Systems174
SNMP Administrative State Control174
This document provides you with supplementary information on Simple Network
Management Protocol (SNMP) based management for your AudioCodes device. This
information complements the information provided by the device's User's Manual , and
includes SNMP configuration, SNMP traps (events and alarms), and SNMP performance
monitoring MIBs.
●The SNMP MIB manual is supplied in the SoftwareRelease Package delivered
with the device.
●For large deployments (for example, multiple devices in globally distributed
enterprise offices) that need to be managed by central personnel, it is
recommendedto use AudioCodes One Voice Operations Center (OVOC). OVOC
is not includedinthe device's supplied package. Contact AudioCodes for more
information on its OVOC solutionfor large VoIP deployments.
Mediant 800 SBC | S NMP Reference Guide
- 1 -
CHAPTER2 SNMP Overview
2SNMP Overview
Simple Network Management Protocol (SNMP) is a standards-based network control protocol
for managing elements in a network. The SNMP Manager, usually implemented by a thirdparty Network Management System (NMS) or AudioCodes One Voice Operations Center
(OVOC), connects to an SNMP Agent (embedded on a remote Network Element (NE) to
perform network element Operation, Administration, Maintenance, and Provisioning (OAMP).
Both the SNMP Manager and the NE refer to the same database to retrieve information or
configure parameters. This database is referred to as the Management Information Base
(MIB), and is a set of statistical and control values. Apart from the standard MIBs documented
in IETF RFCs, SNMP additionally enables the use of proprietary MIBs, containing non-standard
information set (specific functionality provided by the Network Element).
Directives, issued by the SNMP Manager to an SNMP Agent, consist of the identifiers of SNMP
variables (referred to as MIB object identifiers or MIB variables) along with instructions to
either get the value for that identifier, or set the identifier to a new value (configuration). The
SNMP Agent can also send unsolicited events towards an EMS, called SNMP traps.
Mediant 800 SBC | S NMP Reference Guide
The definitions of MIB variables supported by a particular agent are incorporated in descriptor
files, written in Abstract Syntax Notation (ASN.1) format, made available to EMS client
programs so that they can become aware of MIB variables and their usage.
The device contains an embedded SNMP Agent supporting both general network MIBs (such
as the IP MIB), VoP-specific MIBs (such as RTP) and proprietary MIBs (acGateway, acAlarm,
acMedia, acControl, and acAnalog MIBs) enabling a deeper probe into the interworking of the
device. All supported MIB files are supplied to customers as part of the release.
SNMP Standards and Objects
This section discusses the SNMP standards and SNMP objects.
SNMP Message Standard
Four types of SNMP messages are defined:
■ Get: A request that returns the value of a named object.
■ Get-Next: A request that returns the next name (and value) of the "next" object supported
by a network device given a valid SNMP name.
■ Set: A request that sets a named object to a specific value.
■ Trap: A message generated asynchronously by network devices. It notifies the network
manager of a problem apart from the polling of the device.
Each of these message types fulfills a particular requirement of network managers:
■ Get Request: Specific values can be fetched via the "get" request to determine the
performance and state of the device. Typically, many different values and parameters can
- 2 -
CHAPTER2 SNMP Overview
be determined via SNMP without the overhead associated with logging into the device, or
establishing a TCP connection with the device.
■ Get Next Request: Enables the SNMP standard network managers to "walk" through all
SNMP values of a device (via the "get-next" request) to determine all names and values
that a device supports.
■ Get-Bulk: Extends the functionality of GETNEXT by allowing multiple values to be returned
for selected items in the request. This is accomplished by beginning with the first SNMP
object to be fetched, fetching the next name with a "get-next", and repeating this
operation.
■ Set Request: The SNMP standard provides a action method for a device (via the "set"
request) to accomplish activities such as disabling interfaces, disconnecting users, clearing
registers, etc. This provides a way of configuring and controlling network devices via
SNMP.
■ Trap Message: The SNMP standard furnishes a mechanism for a device to "reach out" to a
network manager on their own (via the “trap" message) to notify or alert the manager of a
problem with the device. This typically requires each device on the network to be
configured to issue SNMP traps to one or more network devices that are awaiting these
traps.
Mediant 800 SBC | S NMP Reference Guide
The above message types are all encoded into messages referred to as "Protocol Data Units"
(PDUs) that are interchanged between SNMP devices.
SNMP MIB Objects
The SNMP MIB is arranged in a tree-structure, similar to a disk directory structure of files. The
top-level SNMP branch begins with the ISO "internet" directory, which contains four main
SNMP branches:
■ "mgmt": Contains the standard SNMP objects usually supported (at least in part) by all
network devices.
■ “private": Contains those "extended" SNMP objects defined by network equipment
vendors.
■ "experimental" and "directory": Also defined within the "internet" root directory, are
usually devoid of any meaningful data or objects.
The "tree" structure described above is an integral part of the SNMP standard, though the
most pertinent parts of the tree are the "leaf" objects of the tree that provide actual
management data regarding the device. Generally, SNMP leaf objects can be partitioned into
two similar but slightly different types that reflect the organization of the tree structure:
■ Discrete MIB Objects: Contain one precise piece of management data. These objects are
often distinguished from "Table" items (below) by adding a “.0" (dot-zero) extension to
their names. The operator must merely know the name of the object and no other
information.
- 3 -
CHAPTER2 SNMP Overview
■ Table MIB Objects: Contain multiple pieces of management data. These objects are
distinguished from "Discrete" items (above) by requiring a "." (dot) extension to their
names that uniquely distinguishes the particular value being referenced. The "." (dot)
extension is the "instance" number of an SNMP object. For "Discrete" objects, this
instance number is zero. For "Table" objects, this instance number is the index into the
SNMP table. SNMP tables are special types of SNMP objects, which allow parallel arrays of
information to be supported. Tables are distinguished from scalar objects, such that
tables can grow without bounds. For example, SNMP defines the "ifDescr" object (as a
standard SNMP object) that 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 can 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).
SNMP Extensibility Feature
Mediant 800 SBC | S NMP Reference Guide
One of the principal components of an SNMP manager is a MIB Compiler, which allows new
MIB objects to be added to the management system. When a MIB is compiled into an SNMP
manager, the manager is made "aware" of new objects that are supported by agents on the
network. The concept is similar to adding a new schema to a database.
Typically, when a MIB is compiled into the system, the manager creates new folders or
directories that correspond to the objects. These folders or directories can typically be viewed
with a "MIB Browser", which is a traditional SNMP management tool incorporated into
virtually all network management systems.
The act of compiling the MIB allows the manager to know about the special objects supported
by the agent and access these objects as part of the standard object set.
Supported MIBs
The device contains an embedded SNMP agent supporting the MIBs listed below. A description
in HTML format for all supported MIBs can be found in the MIBs directory in the release
package.
■ Standard MIB (MIB-2): The various SNMP values in the standard MIB are defined in RFC
1213. The standard MIB includes various objects to measure and monitor IP activity, TCP
activity, UDP activity, IP routes, TCP connections, interfaces, and general system
description.
●The standard icmpStatsTable and icmpMsgStatsTable under MIB-2 support ICMP
statistics for both IPv4 and IPv6.
●The inetCidrRouteTable (from the standard IP-FORWARD-MIB) supports both IPv4 and
IPv6.
- 4 -
CHAPTER2 SNMP Overview
■ System MIB (under MIB-2): Standard system group: sysDescr, sysObjectID, sysUpTime,
sysContact, sysName, sysLocation, and sysServices. You can replace the value of
sysObjectID.0 with a variable value using the ini file parameter SNMPSysOid. This
parameter is polled during startup and overwrites the standard sysObjectID.
SNMPSysName is an administratively assigned name for this managed node. By
convention, this is the node's fully-qualified domain name (FQDN). If the name is
unknown, the value is the zero-length string. If the [HostName] ini file parameter is
configured, its' value overwrites the value of SNMPSysName.
■ RTP MIB: The MIB is supported according to RFC 2959. It contains objects relevant to the
RTP streams generated and terminated by the device and to the RTCP information related
to these streams.
The inverse tables are not supported.
■ Notification Log MIB: Standard MIB (RFC 3014 - iso.org.dod.internet.mgmt.mib-2)
supported for implementation of Carrier Grade Alarms.
Mediant 800 SBC | S NMP Reference Guide
■ Alarm MIB: IETF MIB (RFC 3877) Supported as part of the implementation of Carrier Grade
Alarms.
■ SNMP Target MIB: (RFC 2273) Allows for configuration of trap destinations and trusted
managers.
■ SNMP MIB: (RFC 3418) Allows support for the coldStart and authenticationFailure traps.
■ SNMP Vacm MIB: (RFC 3415) Implements the view-based Access Control Model.
■ SNMP Community MIB: (RFC 3584) Implements community string management.
■ ipForward MIB: (RFC 2096) Fully supported.
■ RTCP-XR: (RFC) implements the following partial support:
●The rtcpXrCallQualityTable is fully supported.
●In the rtcpXrHistoryTable, support of the RCQ objects is provided only with no more
than 3 intervals, 15 minutes long each.
●Supports the rtcpXrVoipThresholdViolation trap.
■ ds1 MIB: supports the following:
●dsx1ConfigTable: partially supports the following objects with SET and GET applied:
◆dsx1LineCoding
◆dsx1LoopbackConfig
◆dsx1LineStatusChangeTrapEnable
◆dsx1CircuitIdentifier
- 5 -
CHAPTER2 SNMP Overview
All other objects in this table support GET only.
●dsx1CurrentTable
●dsx1IntervalTable
●dsx1TotalTable
●dsx1LineStatusChange trap
■ acPSTN MIB:
●acSonetSDHTable: currently has one entry (acSonetSDHFbrGrpMappingType) for
selecting a low path mapping type. Relevant only for PSTN applications. (Refer to the
MIB for more details.)
In addition to the standard MIBs, the complete product series contains proprietary MIBs:
■ AC-TYPES MIB: lists the known types defined by the complete product series. This is
referred to by the sysObjectID object in the MIB-II.
■ AcBoard MIB: includes the acTrap group.
Mediant 800 SBC | S NMP Reference Guide
Each proprietary MIB contains a Configuration subtree for configuring the related parameters.
In some, there also are Status and Action subtrees.
■ AcAnalog MIB
■ acControl MIB
■ acMedia MIB
■ acSystem MIB
■ acSysInterfaceStatusTable: supports the networking multiple interfaces feature status.
This table reflects all the device's active interfaces. The lines indices consist of both the
Entry Index and the Type Index. The table contains the following columns:
●Entry Index - related Interface index in the interface configuration table (if the table is
empty,i.e., there is only single IP address, the index appears with 0)
●Type Index - 1 for IP Address and 2 for IPv6 Link-Local Address
●Application Types - type assigned to the interface
●Status Mode - interface configuration mode
●IP Address - IP address (either IPv4 or IPv6) for this interface
●Prefix Length - number of ‘1’ bits in this interface’s net mask
●Gateway - default gateway
●Vlan ID - VLAN ID of this interface
●Name - interface’s name
●Primary DNS Server IP Address - IP address of primary DNS server for this interface
- 6 -
CHAPTER2 SNMP Overview
●Secondary DNS Server IP Address - IP address of secondary DNS server for this
interface
■ acSysModuleTable
■ acPSTN MIB
■ acGateway MIB: This proprietary MIB contains objects related to configuration of the SIP
device. This MIB complements the other proprietary MIBs. The acGateway MIB includes
the following groups:
●Common: parameters common to both SIP and H.323.
●SIP: SIP only parameters.
■ AcAlarm: This is a proprietary carrier-grade alarm MIB. It is a simpler implementation of
the notificationLogMIB and the IETF suggested alarmMIB (both supported).
The acAlarm MIB has the following groups:
●ActiveAlarm: straight forward (single indexed) table listing all currently active Alarms
together with their bindings (the Alarm bindings are defined in acAlarm.
acAlarmVarbinds and also in acBoard.acTrap. acBoardTrapDefinitions. oid_1_3_6_1_
4_1_5003_9_10_1_21_2_0).
Mediant 800 SBC | S NMP Reference Guide
●acAlarmHistory: straight forward (single indexed) table listing all recently sent Alarms
together with their bindings (the Alarm bindings are defined in acAlarm.
acAlarmVarbinds and also in acBoard.acTrap. acBoardTrapDefinitions. oid_1_3_6_1_
4_1_5003_9_10_1_21_2_0).
The table size can be altered by one of the following:
The table size (i.e., number of contained alarms) can be any value between 10 and 1,000
(default is 500)
- 7 -
CHAPTER2 SNMP Overview
●A detailedexplanation of each parametercan be viewed in theMIB Description
●A detaileddescription in HTML format of all MIBs can be found in the MIBs
●Not all groups in the MIB are implemented.
●MIB Objects that aremarked as 'obsolete' are not implemented.
●When a parameter is Set to a new value via SNMP, the changemay affect device
●The current (updated) device configuration parameters areconfigured on the device
SNMP Interface Details
This subsection describes details of the SNMP interface needed when developing an Element
Management System (EMS) for any AudioCodes devices, or to manage a device with a MIB
browser.
Mediant 800 SBC | S NMP Reference Guide
field.
directory (included in theRelease package).
functionality immediately or may require that the device be soft reset for the
change to take effect. This depends on the parameter type.
providedthe user doesn't load an ini file to the device after reset. Loadingan ini file
after reset overrides the updated parameters.
There are several alternatives for SNMP security:
■ SNMPv2c community strings
■ SNMPv3 User-based Security Model (USM) users
■ SNMP encoded over IPSec
■ Various combinations of the above
Currently, both SNMP and ini file commands and downloads are not encrypted. For ini file
encoding, refer to the device's User's Manual.
SNMP Community Names
By default, the device uses a single, read-only community string of "public" and a single readwrite community string of "private". Up to five read-only community strings and up to five
read-write community strings, and a single trap community string can be configured. Each
community string must be associated with one of the following predefined groups:
Table 2-1: SNMP Predefined Groups
GroupGet AccessSet AccessSends Traps
ReadGroupYesNoYes
ReadWriteGroupYesYesYes
TrapGroupNoNoYes
- 8 -
CHAPTER2 SNMP Overview
Configuring Community Strings via the Web
For detailed information on configuring community strings through the Web interface, refer to
the device's User's Manual.
Configuring Community Strings via the ini File
The following ini file parameters are used to configure community strings:
■ SNMPREADONLYCOMMUNITYSTRING_<x> = '#######'
■ SNMPREADWRITECOMMUNITYSTRING_<x> = '#######'
Where <x> is a number from 0 through 4. Note that the '#' character represents any
alphanumeric character. The maximum length of the string is 19 characters that can include
only the following:
■ Upper- and lower-case letters (a to z, and A to Z)
■ Numbers (0 to 9)
Mediant 800 SBC | S NMP Reference Guide
■ Hyphen (-)
■ Underline (_)
Configuring Community Strings via SNMP
To configure community strings, the EMS must use the standard snmpCommunityMIB. To
configure the trap community string, the EMS must also use the snmpTargetMIB.
➢ To add a read-only v2user community string:
1. Add a new row to the snmpCommunityTable with CommunityName v2user.
2. Add a row to the vacmSecurityToGroupTable for SecurityName v2user, GroupName
ReadGroup and SecurityModel snmpv2c.
➢ To delete the read-only v2user community string:
1. If v2user is being used as the trap community string, follow the procedure for changing
the trap community string. (See below.)
2. Delete the snmpCommunityTable row with CommunityName v2user.
3. Delete the vacmSecurityToGroupTable row for SecurityName v2user, GroupName
ReadGroup and SecurityModel snmpv2c.
➢ To add a read-write v2admin community string:
1. Add a new row to the snmpCommunityTable with CommunityName v2admin.
2. Add a row to the vacmSecurityToGroupTable for SecurityName v2admin, GroupName
ReadWriteGroup and SecurityModel snmpv2c.
- 9 -
CHAPTER2 SNMP Overview
➢ To delete the read-write v2admin community string:
1. If v2admin is being used as the trap community string, follow the procedure for changing
the trap community string. (See below.)
2. Delete the snmpCommunityTable row with a CommunityName of v2admin and
GroupName of ReadWriteGroup.
➢ To change the only read-write community string from v2admin to v2mgr:
1. Follow the procedure above to add a read-write community string to a row for v2mgr.
2. Set up the EM such that subsequent set requests use the new community string, v2mgr.
3. If v2admin is being used as the trap community string, follow the procedure to change the
trap community string. (See below.)
4. Follow the procedure above to delete a read-write community name in the row for
v2admin.
Mediant 800 SBC | S NMP Reference Guide
The following procedure assumes that a row already exists in the snmpCommunityTable for
the new trap community string. The trap community string can be part of the TrapGroup,
ReadGroup, or ReadWriteGroup. If the trap community string is used solely for sending traps
(recommended), then it should be made part of the TrapGroup.
➢ To change the trap community string:
1. Add a row to the vacmSecurityToGroupTable with these values: SecurityModel=2,
SecurityName=the new trap community string, GroupName=TrapGroup, ReadGroup or
ReadWriteGroup. The SecurityModel and SecurityName objects are row indices.
You must add GroupName and RowStatus on the same set.
2. Modify the SecurityName field in the appropriate row of the snmpTargetParamsTable.
3. Remove the row from the vacmSecurityToGroupTable with SecurityName=the old trap
community string.
SNMPv3 USM Users
You can configure up to 10 User-based Security Model (USM) users (referred to as SNMPv3
user). Each SNMPv3 user can be configured to one of the following security levels:
Table 2-2: SNMPv3 Security Levels
Security LevelsAuthenticationPrivacy
noAuthNoPriv(1)nonenone
authNoPriv(2)MD5 or SHA-1none
- 10 -
CHAPTER2 SNMP Overview
Security LevelsAuthenticationPrivacy
authPriv(3)MD5 or SHA-1DES, 3DES, AES128, AES192, or AES256
Each SNMPv3 user must be associated with one of the predefined groups listed in the following
table:
The first (initial) SNMPv3 user can only be configured through a management interface
other than SNMP (i.e., Web interface, configuration ini file, or CLI). Once configured,
additional users can be configured through the SNMP interface as well.
Configuring SNMPv3 Users via ini File
Use the [SNMPUsers] ini file table parameter to add, modify, and delete SNMPv3 users. The
[SNMPUsers] ini table is a hidden parameter. Therefore, when you load the ini file to the device
using the Web interface, the table is not included in the generated file.
Table 2-4: SNMPv3 Table Columns Description
ParameterDescriptionDefault
Row numberTable index. Its valid range is 0 to 9.N/A
SNMPUsers_UsernameName of the v3 user. Must be unique. The maximum
N/A
length is 32 characters.
- 11 -
CHAPTER2 SNMP Overview
ParameterDescriptionDefault
Mediant 800 SBC | S NMP Reference Guide
SNMPUsers_
AuthProtocol
SNMPUsers_
PrivProtocol
Authentication protocol to be used for this user.
Possible values are 0 (none), 1 (MD5), 2 (SHA-1)
Privacy protocol to be used for this user. Possible
values are 0 (none), 1 (DES), 2 (3DES), 3 (AES128), 4
0
0
(AES192), 5 (AES256)
SNMPUsers_AuthKeyAuthentication key.""
SNMPUsers_PrivKeyPrivacy key.""
SNMPUsers_GroupThe group that this user is associated with. Possible
0
values are 0 (read-only group), 1 (read-write group),
and 2 (trap group). The actual group will be
ReadGroup<sl>, ReadWriteGroup<sl> or
TrapGroup<sl> where <sl> is the SecurityLevel
(1=noAuthNoPriv, 2=authNoPriv, 3=authPriv)
Keys can be entered in the form of a text password or in the form of a localized key in hex
format. If using a text password, then it should be at least 8 characters in length. Below is an
example showing the format of a localized key:
26:60:d8:7d:0d:4a:d6:8c:02:73:dd:22:96:a2:69:df
The following sample configuration creates three SNMPv3 USM users.
■ The user v3user is set up for a security level of noAuthNoPriv(1) and is associated with
ReadGroup1.
■ The user v3admin1 is setup for a security level of authNoPriv(2), with authentication
protocol MD5. The authentication text password is “myauthkey” and the user is
associated with ReadWriteGroup2.
- 12 -
CHAPTER2 SNMP Overview
■ The user v3admin2 is setup for a security level of authPriv(3), with authentication protocol
SHA-1 and privacy protocol DES. The authentication text password is “myauthkey”, the
privacy text password is “myprivkey”, and the user is associated with ReadWriteGroup3.
Configuring SNMPv3 Users via SNMP
To configure SNMPv3 users, the EMS must use the standard snmpUsmMIB and the
snmpVacmMIB.
➢ To add a read-only, noAuthNoPriv SNMPv3 user, v3user:
1. Clone the row with the same security level. After the clone step, the status of the row will
be notReady(3).
2. Activate the row. That is, set the row status to active(1).
3. Add a row to the vacmSecurityToGroupTable for SecurityName v3user, GroupName
ReadGroup1 and SecurityModel usm(3).
Mediant 800 SBC | S NMP Reference Guide
A row with the same security level (noAuthNoPriv) must already exist in the
usmUserTable. (see theusmUserTable for details).
➢ To delete the read-only, noAuthNoPriv SNMPv3 user, v3user:
1. If v3user is associated with a trap destination, follow the procedure for associating a
different user to that trap destination. (See below.)
2. Delete the vacmSecurityToGroupTable row for SecurityName v3user, GroupName
ReadGroup1 and SecurityModel usm.
3. Delete the row in the usmUserTable for v3user.
➢ To add a read-write, authPriv SNMPv3 user, v3admin1:
1. Clone the row with the same security level.
2. Change the authentication key and privacy key.
3. Activate the row. That is, set the row status to active(1).
4. Add a row to the vacmSecurityToGroupTable for SecurityName v3admin1, GroupName
ReadWriteGroup3 and SecurityModel usm(3).
A row with the same security level (authPriv) must already exist in the usmUserTable
(see the usmUserTable for details).
➢ To delete the read-write, authPriv SNMPv3 user, v3admin1:
1. If v3admin1 is associated with a trap destination, follow the procedure for associating a
different user to that trap destination. (See below.)
- 13 -
CHAPTER2 SNMP Overview
2. Delete the vacmSecurityToGroupTable row for SecurityName v3admin1, GroupName
ReadWriteGroup1 and SecurityModel usm.
3. Delete the row in the usmUserTable for v3admin1.
Trusted Managers
By default, the SNMP agent accepts Get and Set requests from any IP address, as long as the
correct community string is used in the request. Security can be enhanced implementing
Trusted Managers. A Trusted Manager is an IP address from which the SNMP agent accepts
and processes Get and Set requests. An element management can be used to configure up to
five Trusted Managers.
The concept of Trusted Managers is considered to be a weak form of security and therefore is
not a required part of SNMPv3 security, which uses authentication and privacy. Trusted
Managers for the devices' SNMP agent are applicable only for SNMPv2c users. An exception to
this is when the community string is not the default string (‘public’/’private’), at which time
Trusted Managers are applicable for SNMPV2c users alongside SNMPv3 users.
Mediant 800 SBC | S NMP Reference Guide
If Trusted Managers are defined, then all community strings work from all Trusted
Managers. In other words, there is no way to associate a community string with
specific Trusted Managers.
Configuring Trusted Managers via ini File
To set the Trusted Managers table from start up, write the following in the ini file:
SNMPTRUSTEDMGR_X = D.D.D.D
Where X is any integer between 0 and 4 (0 sets the first table entry, 1 sets the second and so
on), and D is an integer between 0 and 255.
Configuring Trusted Managers via SNMP
To configure Trusted Managers, the Element Management System (EMS) must use the SNMPCOMMUNITY-MIB and snmpCommunityMIB and the snmpTargetMIB.
The following procedure assumes the following: at least one configured read-write community;
currently no Trusted Managers; TransportTag for columns for all snmpCommunityTable rows
are currently empty.
➢ To add the first Trusted Manager:
1. Add a row to the snmpTargetAddrTable with these values: Name=mgr0, TagList=MGR,
Params=v2cparams.
- 14 -
CHAPTER2 SNMP Overview
2. Add a row to the snmpTargetAddrExtTable table with these values: Name=mgr0, snm-
pTargetAddrTMask=255.255.255.255:0. The agent does not allow creation of a row in this
table unless a corresponding row exists in the snmpTargetAddrTable.
3. Set the value of the TransportTag field on each non-TrapGroup row in the
snmpCommunityTable to MGR.
The following procedure assumes the following: at least one configured read-write community;
currently one or more Trusted Managers; TransportTag for columns for all rows in the
snmpCommunityTable are currently set to MGR. This procedure must be done from one of
the existing Trusted Managers.
➢ To add a subsequent Trusted Manager:
1. Add a row to the snmpTargetAddrTable with these values: Name=mgrN, TagList=MGR,
Params=v2cparams, where N is an unused number between 0 and 4.
2. Add a row to the snmpTargetAddrExtTable table with these values: Name=mgrN, snm-
pTargetAddrTMask=255.255.255.255:0.
Mediant 800 SBC | S NMP Reference Guide
An alternative to the above procedure is to set the snmpTargetAddrTMask column while you
are creating other rows in the table.
The following procedure assumes the following: at least one configured read-write community;
currently two or more Trusted Managers; taglist for columns for all rows in the
snmpCommunityTable are currently set to MGR. This procedure must be done from one of
the existing trusted managers, but not the one that is being deleted.
➢ To delete a Trusted Manager (not the last one):
■ Remove the appropriate row from the snmpTargetAddrTable.
The change takes effect immediately. The deleted trusted manager cannot access the device.
The agent automatically removes the row in the snmpTargetAddrExtTable.
The following procedure assumes the following: at least one configured read-write community;
currently only one Trusted Manager; taglist for columns for all rows in the
snmpCommunityTable are currently set to MGR. This procedure must be done from the final
Trusted Manager.
➢ To delete the last Trusted Manager:
1. Set the value of the TransportTag field on each row in the snmpCommunityTable to the
empty string.
2. Remove the appropriate row from the snmpTargetAddrTable.
The change takes effect immediately. All managers can now access the device. The agent
automatically removes the row in the snmpTargetAddrExtTable.
- 15 -
CHAPTER2 SNMP Overview
SNMP Ports
The SNMP Request Port is 161 and the SNMP Trap Port is 162. These port numbers for SNMP
requests and responses can be changed, by using the [SNMPPort] ini file parameter. The valid
value is any valid UDP port number. The default is 161 (recommended).
Multiple SNMP Trap Destinations
An agent can send traps to up to five managers. For each manager you need to define the
manager IP address and trap receiving port along with enabling the sending to that manager.
You can also associate a trap destination with a specific SNMPv3 USM user. Traps are sent to
this trap destination using the SNMPv3 format and the authentication and privacy protocol
configured for that user.
To configure the Trap Managers table, use one of the following methods:
■ Web interface (refer to the device's User's Manual)
■ ini file (see Configuring Trap Managers via ini File below)
Mediant 800 SBC | S NMP Reference Guide
■ SNMP (see Configuring Trap Managers via SNMP on page18)
Configuring Trap Managers via Host Name
One of the five available SNMP managers can be defined using the manager's host name (i.e.,
FQDN). This can be configured using the ini file parameter [SNMPTrapManagerHostName].
When this parameter value is defined for this trap, the device at start up tries to resolve the
host name. Once the name is resolved (i.e., the IP address is found), the resolved IP address
replaces the last entry of the trap manager table (defined by the parameter
[SNMPManagerTableIP_x]) and the last trap manager entry of snmpTargetAddrTable in the
snmpTargetMIB. The port is 162 (unless specified otherwise). The row is marked as 'used' and
the sending is 'enabled'.
When using 'host name' resolution, any changes made by the user to this row in either MIBs
are overwritten by the device when a resolving is redone (once an hour).
Some traps may be lost until the nameresolving is complete.
Configuring Trap Managers via ini File
In the ini file, the following parameters can be set to enable or disable the sending of SNMP
traps. Multiple trap destinations can be supported on the device by setting multiple trap
destinations in the ini file.
■ SNMPManagerTrapSendingEnable_<x>: indicates whether or not traps are to be sent to
the specified SNMP trap manager. A value of ‘1’ means that it is enabled, while a value of
‘0’ means disabled. The <x> represents a number 0, 1, or 2, which is the array element
index. Currently, up to five SNMP trap managers is supported.
- 16 -
CHAPTER2 SNMP Overview
■ SNMPManagerTrapUser_<x>: indicates to send an SNMPv2 trap using the trap user
community string configured with the SNMPTrapCommunityString parameter. You may
instead specify an SNMPv3 user name.
The following is an example of entries in the ini file regarding SNMP. The device can be
configured to send to multiple trap destinations.
; SNMP trap destinations
; The device maintains a table of trap destinations containing 5
; rows. The rows are numbered 0..4. Each block of 5 items below
; applies to a row in the table.
;
; To configure one of the rows, uncomment all 5 lines in that
; block. Supply an IP address and if necessary, change the port
; number.
;
; To delete a trap destination, set ISUSED to 0.
;
;SNMPManagerTableIP_0=
;SNMPManagerTrapPort_0=162
;SNMPManagerIsUsed_0=1
;SNMPManagerTrapSendingEnable_0=1
;SNMPManagerTrapUser_0=’’
;
;SNMPManagerTableIP_1=
;SNMPManagerTrapPort_1=162
;SNMPManagerIsUsed_1=1
;SNMPManagerTrapSendingEnable_1=1
;SNMPMANAGERTRAPUSER_1=’’
;
;SNMPManagerTableIP_2=
;SNMPManagerTrapPort_2=162
;SNMPManagerIsUsed_2=1
;SNMPManagerTrapSendingEnable_2=1
;SNMPManagerTrapUser_2=’’
;
;SNMPManagerTableIP_3=
;SNMPManagerTrapPort_3=162
;SNMPManagerIsUsed_3=1
;SNMPManagerTrapSendingEnable_3=1
;SNMPManagerTrapUser_3=’’
;
;SNMPMANAGERTABLEIP_4=
;SNMPManagerTrapPort_4=162
;SNMPManagerIsUsed_4=1
The same information that is configurable in the ini file can also be configured via the
acBoardMIB.
Configuring SNMP Engine ID
The [SNMPEngineIDString] ini file parameter configures the SNMP engine ID. The ID can be a
string of up to 36 characters. Once defined, the device must be reset for the parameter to take
effect.
Mediant 800 SBC | S NMP Reference Guide
The default value is 00:00:00:00:00:00:00:00:00:00:00:00 (12 Hex characters). The provided key
must be set with 12 Hex values delimited by ‘:’.
If the supplied key does not pass validation of the 12 Hex values input or it is set with the
default value, the engine ID is then generated, according to RFC 3411.
Before setting this parameter, all SNMPv3 users must be deleted, otherwise the configuration
is ignored.
When the device operates in HA mode, the SNMPEngineIDString parameter has the
same value for both active and redundant devices (i.e., system identifier). If the
devices return to Standalone mode (i.e., non-HA mode), you must configure the
parameter to a NULL value (i.e., no value) on both devices. When the devices reset to
the standalone mode, each device automatically sets this parameter to a unique value
based on its serial number(S/N).
Configuring Trap Managers via SNMP
The snmpTargetMIB interface is available for configuring trap managers.
➢ To add an SNMPv2 trap destination:
■ Add a row to the snmpTargetAddrTable with these values: Name=trapN, TagList=AC_TRAP,
Params=v2cparams, where N is an unused number between 0 and 4
All changes to the trap destination configuration take effect immediately.
➢ To add an SNMPv3 trap destination:
1. Add a row to the snmpTargetAddrTable with these values: Name=trapN, TagList=AC_TRAP,
Params=usm<user>, where N is an unused number between 0 and 4, and <user> is the
- 18 -
CHAPTER2 SNMP Overview
name of the SNMPv3 that this user is associated with.
2. If a row does not already exist for this combination of user and SecurityLevel, add a row to
the snmpTargetParamsTable with these values: Name=usm<user>, MPModel=3(SNMPv3),
SecurityModel=3 (usm), SecurityName=<user>, SecurityLevel=M, where M is either 1
(noAuthNoPriv), 2(authNoPriv) or 3(authPriv).
All changes to the trap destination configuration take effect immediately.
➢ To delete a trap destination:
■ Remove the appropriate row from the snmpTargetAddrTable.
■ If this is the last trap destination associated with this user and security level, you could
also delete the appropriate row from the snmpTargetParamsTable.
➢ To modify a trap destination:
You can change the IP address and or port number for an existing trap destination. The same
effect can be achieved by removing a row and adding a new row.
Mediant 800 SBC | S NMP Reference Guide
■ Modify the IP address and/or port number for the appropriate row in the
snmpTargetAddrTable.
➢ To disable a trap destination:
■ Change TagList on the appropriate row in the snmpTargetAddrTable to the empty string.
➢ To enable a trap destination:
■ Change TagList on the appropriate row in the snmpTargetAddrTable to ‘AC_TRAP’.
■ Change TagList on the appropriate row in the snmpTargetAddrTable to "AC_TRAP".
- 19 -
CHAPTER3 Carrier-Grade Alarm System
3Carrier-Grade Alarm System
The basic alarm system has been extended to a carrier-grade alarm system. A carrier-grade
alarm system provides a reliable alarm reporting mechanism that takes into account EMS
outages, network outages, and transport mechanism such as SNMP over UDP.
A carrier-grade alarm system is characterized by the following:
■ The device allows an EMS to determine which alarms are currently active in the device.
That is, the device maintains an active alarm table.
■ The device allows an EMS to detect lost alarms and clear notifications [sequence number
in trap, current sequence number MIB object]
■ The device allows an EMS to recover lost alarm raise and clear notifications [maintains a
log history]
■ The device sends a cold start trap to indicate that it is starting. This allows the EMS to
synchronize its view of the device's active alarms.
Mediant 800 SBC | S NMP Reference Guide
When the SNMP alarm traps are sent, the carrier-grade alarm system does not add or delete
alarm traps as part of the feature. This system provides the mechanism for viewing of history
and current active alarm information.
Active Alarm Table
The device maintains an active alarm table to allow an EMS to determine which alarms are
currently active in the device. Two views of the active alarm table are supported by the agent:
■ acActiveAlarmTable in the enterprise AcAlarm
■ alarmActiveTable and alarmActiveVariableTable in the IETF standard AcAlarm MIB (rooted
in the MIB tree)
The acActiveAlarmTable is a simple, one-row per alarm table that is easy to view with a MIB
browser.
Alarm History
The device maintains a history of alarms that have been sent and traps that have been cleared
to allow an EMS to recover any lost raise or clear traps. Two views of the alarm history table
are supported by the agent:
■ acAlarmHistoryTable in the enterprise AcAlarm - a simple, one-row per alarm table, that is
easy to view with a MIB browser.
■ nlmLogTable and nlmLogVariableTable in the standard NOTIFICATION-LOG-MIB
- 20 -
CHAPTER4 Topology MIB Objects
4Topology MIB Objects
This section describes the topology of the MIB objects.
Physical Entity (RFC 2737)
The following groups are supported:
■ entityPhysical group: Describes the physical entities managed by a single agent.
■ entityMapping group: Describes the associations between the physical entities, logical
entities, interfaces, and non-interface ports managed by a single agent.
■ entityGeneral group: Describes general system attributes shared by potentially all types of
entities managed by a single agent.
■ entityNotifications group: Contains status indication notifications.
Mediant 800 SBC | S NMP Reference Guide
IF-MIB (RFC 2863)
The following interface types are presented in the ifTable:
■ ethernetCsmacd(6): for all Ethernet-like interfaces, regardless of speed, as per RFC 3635
■ ds1(18): DS1-MIB
■ voiceFXO(101): Voice Foreign Exchange Office
■ voiceFXS(102): Voice Foreign Exchange Station
The numbers in the brackets above refer to the IANA's interface-number.
For each interface type, the following objects are supported:
Ethernet Interface
Table 4-1: Ethernet Interface
ifTable & ifXTableValue
ifIndexConstructed as defined in the device's Index format.
ifDescrEthernet interface.
ifTypeethernetCsmacd(6)
ifMtu1500
ifPhysAddress00-90-8F plus acSysIdSerialNumber in hex.Will be same for
both dual ports.
ifAdminStatusAlways UP. [Read Only] - Write access is not required by the
- 21 -
CHAPTER4 Topology MIB Objects
ifTable & ifXTableValue
ifOperStatusUp or Down corresponding to acAnalogFxsFxoType where
ifLastChangeThe value of sysUpTime at the time the interface entered its
ifInOctetsThe number of octets in valid MAC frames received on this
ifInUcastPktsAs defined in IfMIB.
ifInDiscardsAs defined in IfMIB.
Mediant 800 SBC | S NMP Reference Guide
standard. Support for 'testing' is not required.
Unknown is equal to Down.
current operational state.
interface, including the MAC header and FCS. This does
include the number of octets in valid MAC Control frames
received on this interface.
ifInErrorsThe sum for this interface of dot3StatsAlignmentErrors,
dot3StatsFCSErrors, dot3StatsFrameTooLongs, and
dot3StatsInternalMacReceiveErrors.
ifInUnknownProtosAs defined in IfMIB.
ifOutOctetsThe number of octets transmitted in valid MAC frames on
this interface, including the MAC header and FCS. This
does include the number of octets in valid MAC Control
frames transmitted on this interface.
ifOutUcastPktsAs defined in IfMIB.
ifOutDiscardsAs defined in IfMIB.
ifOutErrorsThe sum for this interface of: dot3StatsSQETestErrors,
dot3StatsLateCollisions, dot3StatsExcessiveCollisions,
dot3StatsInternalMacTransmitErrors and
dot3StatsCarrierSenseErrors.
ifNameEthernet port #1 or# 2
ifInMulticastPktsAs defined in IfMIB.
ifInBroadcastPktsAs defined in IfMIB.
ifOutMulticastPktsAs defined in IfMIB.
ifOutBroadcastPktsAs defined in IfMIB.
- 22 -
CHAPTER4 Topology MIB Objects
ifTable & ifXTableValue
Mediant 800 SBC | S NMP Reference Guide
ifHCInOctets
ifHCOutOctets
64-bit versions of counters. Required for ethernet-like
interfaces that are capable of operating at 20 Mb/s or
faster, even if the interface is currently operating at less
than 20 Mb/s.
64-bit versions of packet counters. Required for ethernetlike interfaces that are capable of operating at 640 Mb/s or
faster, even if the interface is currently operating at less
than 640 Mb/s.
Therefore, will be constant zero.
ifHCOutBroadcastPkts
ifLinkUpDownTrapEnableSet to disabled (2). Refer to [RFC 2863].
ifPromiscuousModeConstant False. [R/O]
ifConnectorPresentConstant True.
ifAliasAn 'alias' name for the interface as specified by a network
manager (NVM)
ifCounterDiscontinuityTimeAs defined in IfMIB.
DS1 Interface
The DS1 interface is applicable only to digital PSTN interfaces.
Table 4-2: DS1 Digital Interface
ifTableValue
ifDescrDigital DS1 interface.
ifTypeds1(18).
ifMtuConstant zero.
ifSpeedDS1 = 1544000, or E1 = 2048000, according to dsx1LineType
ifPhysAddressThe value of the Circuit Identifier [dsx1CircuitIdentifier]. If
no Circuit Identifier has been assigned this object should
have an octet string with zero length.
ifAdminStatusTrunk’s Lock & Unlock during run time. In initialization
- 23 -
CHAPTER4 Topology MIB Objects
ifTableValue
ifOperStatusUp or Down, according to the operation status.
ifLastChangeThe value of sysUpTime at the time the interface entered its
ifXTableValue
ifNameDigital# acTrunkIndex
ifLinkUpDownTrapEnableSet to disabled(2)
ifHighSpeedSpeed of line in Megabits per second: 2
ifConnectorPresentSet to true(1) normally, except for cases such as DS1/E1
Mediant 800 SBC | S NMP Reference Guide
process we need to refer the Admin-Status parameter.
current operational state.
over AAL1/ATM where false(2) is appropriate
ifCounterDiscontinuityTimeAlways zero.
- 24 -
CHAPTER5 File Management
5File Management
SNMP supports file download, upload, and removal.
Downloading a File to the Device
The file URL is set in the appropriate MIB object under the acSysHTTPClient subtree (refer to
the subtree objects description for the URL form). The download can be scheduled using the
acSysHTTPClientAutoUpdatePredefinedTimeandacSysHTTPClientAutoUpdateFrequency
objects. It can also be a manual process using acSysActionSetAutoUpdate. In this case (only)
and as long as one URL is set at a time, the result can be viewed in acSysActionSetAutoUpdateActionResult. In both cases, the acHTTPDownloadResult trap is sent,
indicating the success or failure of the process.
acSysActionSetActionId can be set to any value and can be used to indicate an action
performed by a certain manager.
Mediant 800 SBC | S NMP Reference Guide
A successful process also ends with the file name in the appropriate object under the acSysFile
subtree or in the acCASFileTable or the acAuxiliaryFiles subtree, along with the URL being
erased from the object under the acSysHTTPClient subtree.
●The action result (both in the acSysActionSetAutoUpdateActionResult object and
acHTTPDownloadResult trap) forthe Voice Prompt and XML indicates only that
the file reached thedevice and has no indication on the application’s ability to parse
the file.
●The action result in acSysActionSetAutoUpdateActionResult is reliable as long as
only one file is downloadedat a time.
Uploading and Deleting a File
File upload is the procedure of sending a file from the device to the manager. Deleting a file is
erasing it from the device, an offline action that requires a reset for it to be applied. The
acSysUpload subtree holds all relevant objects.
■ acSysUploadFileURI indicates the file name and location along with the file transfer
protocol (HTTP or NFS), for example, “http:\\server\filename.txt”.
■ acSysUploadFileType and acSysUploadFileNumber are used to determine the file to be
uploaded along with its instance when relevant (for CAS or Video Font).
■ acSysUploadActionID is at the disposal of the manager and can be used to indicate that a
certain manager has performed the action.
■ acSysUploadActionType determines the action that occurs and triggers it off at the same
time.
- 25 -
CHAPTER5 File Management
File upload using SNMP is supported only for ini files; file removal using SNMP is
supportedfor all files except ini files.
Mediant 800 SBC | S NMP Reference Guide
- 26 -
CHAPTER6 Performance Monitoring
6Performance Monitoring
Performance measurements (performance monitoring) are available for third- party
performance monitoring systems through an SNMP interface. These can be polled at
scheduled intervals by an external poller or utility in the management server or other offboard systems.
The device provides performance measurements in the form of two types:
■ Gauges: Gauges represent the current state of activities on the device. Gauges, unlike
counters, can decrease in value and like counters, can increase. The value of a gauge is the
current value or a snapshot of the current activity on the device at that moment.
■ Counters: Counters always increase in value and are cumulative. Counters, unlike gauges,
never decrease in value unless the server is reset, which causes the counters to reset to
zero (0).
The device's performance measurements are provided by the following proprietary MIBs that
are located under the acPerformance subtree, iso (1).org (3).dod (6).internet (1).private
(4).enterprises(1).AudioCodes(5003).acPerformance(10):
Mediant 800 SBC | S NMP Reference Guide
■ acPMMedia: Media-related (voice) monitoring such as RTP and DSP. The MIB includes the
following parameters:
●Number of active DSP channels
●Channels used for each coder
●Discarded packets in robust RTP filter
●Media Networking subtree - an array of packet behavior parameters such as delay,
jitter, transmitted/received and lost RTP bytes and packets.
●Media Networking Aggregated subtree - displays similar data only for the entire device
and includes TDM-IP and IP-IP calls.
●Channel Utilization subtree - parameters regarding channel use by fax, modem, TDM-
IP calls, RTP, SRTP, multicast source and modem relay
●Streaming Cache subtree - hit count, miss count and server request count
■ acPMControl: Control protocol-related (SIP) monitoring such as connections, commands.
●CP Connection subtree – parameters include connection lifetime/state, counters for
commands, retransmissions, active contexts, command success/failure and process
time, transaction processing time and call attempts
●SIP subtree
■ acPMAnalog: Analog channels off-hook state (one table only).
■ acPMPSTN: PSTN-related monitoring such as channel use and trunk utilization. All
statistics in this MIB are per trunk:
●Number of active channels
- 27 -
CHAPTER6 Performance Monitoring
●Trunk activity
●Number of channels that are in/out of service and in maintenance
■ acPMSystem: General device monitoring:
●IP connection.
●Discarded UDP packets due to unknown port
●System Net Utils subtree – transmitted/received bytes/packets, discarded packets
●System Network subtree – DHCP response time/request count and STUN-related
statistics
●System Multicast subtree – multicast IP packets received, multicast IP packets
●System Congestion subtree – congestion state for general resources, DSP resources,
IP resources, conference resources
Mediant 800 SBC | S NMP Reference Guide
●System NFS subtree – NFS-related parameters
Performance monitoring MIBs all have an identical, fixed structure, which includes two major
subtrees:
■ Configuration subtree: Allows configuration of general attributes of the MIB and specific
attributes of the monitored objects. This subtree includes:
●Reset Total Counters: Resets the "total" (see below) objects in all the MIB’s tables, if
they are defined.
●Attributes subtrees: Number of subtrees in which scalars are used to configure high
and low thresholds for relevant tables.
■ Data subtree: Consists of monitored data and statistics, and includes:
●Time From Start Of Interval object: GETs the time in seconds from the beginning of the
current interval.
●Data tables: All have similar structure. Not all possible columns appear in all of them.
The specific structure of a table (i.e. what columns are defined) is parameter specific.
The only column that always appears is the interval column. The information in each
column is a statistical attribute of the parameter being measured.
The device measures performance at fixed intervals of 15 minutes. The device keeps a record
of the last two completed intervals. These intervals are used as a key in the MIB tables in which
the performance monitoring results are presented. There are one or two indices in each table.
If there are two, the first is a sub-set in the table (e.g., trunk number) and the second (or the
single where there is only one) index represents the interval number:
■ 0: Current interval (not completed)
■ 1: Last completed interval
- 28 -
CHAPTER6 Performance Monitoring
■ 2: Second last completed interval
When the current interval (Interval 0) completes (reaches 15 minutes), Interval 2 is discarded,
Interval 1 becomes Interval 2, Interval 0 becomes Interval 1, and a new Interval 0 is created.
●The interval’s start time is synchronized with the device’s clock so that the
intervals begin on the hour (e.g., 12:00). If you are usingNTP, thenit is likely that
the last interval within the first hour after device startup will be cut short to
accommodate for this synchronization.
●Some performance monitoringparameters support a history with more than two
intervals. These includeconference calls, trunk-test calls and digit-collect
requests.
●An attribute whose value is -1 means that the attribute isn’t relevant at that point of
time.
●If the device has just started up and the first measuring interval has not elapsed,
intervals 1 and 2 are not applicable and theirdata values are typically displayed as
"-1" or as empty cells.
Mediant 800 SBC | S NMP Reference Guide
The following figure shows an example of a monitored parameter, in this case, the number of
utilized B-channels in a single trunk:
The x-axis is the time within the interval; the y-axis is the number of used channels. The
parameter’s value is a gauge. While the interval index is 0 (i.e., current interval), any GET on
the parameter value will return a y-axis value at that moment. When the interval is complete
(index 1 or 2), the gauge value is no longer relevant and other attributes become relevant such
as the average (area in green divided by the interval length in seconds), which is called timebased statistics.
The following figure shows an example of the last three intervals. In this example, the device
was powered up at 11:24. The first interval (of 15 minutes) ended at 11:39 and the second
interval (of 15 minutes) ended at 11:54. The current interval (Interval 0) has not completed the
15 minutes. Typically, you would want the measured performance of the last completed
interval (i.e., Interval 1).
- 29 -
CHAPTER6 Performance Monitoring
The performance monitoring MIB tables can include the following properties (columns):
■ Table specific index: This is a table key.
■ Interval: Indicates the measured interval (0,1, or 2), which is a table key.
■ Val: Indicates the value of the gauge or counter. This is the snapshot view of the device's
current activity.
●Counter: Cumulative value (only increases).
●Gauge: Fluctuates in value (increases and decreases).
Mediant 800 SBC | S NMP Reference Guide
■ Average: Indicates the average value within the interval.
■ Max: Indicates the maximum gauge value during the interval.
■ Min: Indicates the minimum gauge value during the interval.
■ Volume: Indicates the number of times the gauge or counter was updated (i.e., the
volume of change), for example:
●For a trunk utilization element, the volume indicates how many calls were made and
released.
●For the Ethernet connection status element, the volume indicates how many network
connections and disconnections occurred.
■ Thresholds:
●TimeBelowLowThreshod: Indicates the percent (%) of the interval time for which the
gauge was below the low threshold (if defined).
●TimeAboveHighThreshod: Indicates the percent (%) of the interval time for which the
gauge was above the high threshold (if defined).
●TimeBetweenThresholds: Indicates the percent (%) of the interval time for which the
gauge was between the low and high thresholds (if defined).
The following figure shows an example of how the device calculates thresholds. The purple
bar indicates the time when the element was below the low threshold (about 40% of the
interval time), the blue bar indicates the time when the element was between the low and
high threshold (about 30%), and the red bar indicates the time when the element was
above the high threshold (about 30%).
- 30 -
CHAPTER6 Performance Monitoring
Mediant 800 SBC | S NMP Reference Guide
The SNMP trap event acPerformanceMonitoringThresholdCrossing is sent every time the
high or low threshold of a Performance Monitored MIB object is crossed (see Performance
Monitoring Threshold-Crossing Trap on page162). The severity field is 'indeterminate'
when the crossing is above the threshold and 'cleared' when it returns to below the
threshold. The trap's 'source varbind' indicates the object for which the threshold is
crossed. To enable this feature, load an ini file to the device with the following parameter
setting:
PM_EnableThresholdAlarms = 1
Once enabled, you can change the low and high threshold values from their default
values, through ini file by using the following syntax:
●<MIB Source Name>: The source name of the MIB (e.g., PM_TrunkUtilization, PM_
NetUtilKBytes, and PM_gwIPGroupOutINVITEDialogs)
●<Low Threshold>: Defines the low-threshold value
●<High Threshold>: Defines the high-threshold value
The value "15" in the syntax is the measuring interval, which is always fixed at 15 minutes.
The following is an example of an ini file that configures the acPMSIPIPGroupOutInviteDialogsTable performance monitoring MIB (OID 1.3.6.1.4.1.5003.10.8.2.52.35) with a
low threshold of 10 and a high threshold of 18:
- 31 -
CHAPTER6 Performance Monitoring
PM_gwIPGroupOutINVITEDialogs= '1,10,18,15'
If you download (save) the device's ini file, it includes all SNMP performance
monitoringMIBs whose thresholds (low and/or high) you have changed from default. To
apply these same threshold values to other devices, load the file to the other devices.
■ FullDayAverage: Indicates the 24-hour average.
■ Total: (Applicable only to Counters) Indicates the summation of all counter values. In
other words, it does not reset to zero for each new interval. However, the total does reset
after a device reset. In addition, you can reset this property per MIB module, by setting
the ResetTotal object to the value 2:
■ StateChanges: Indicates the number of times a state (mostly active/non-active) was
toggled.
Not all the properties listed above are applicable to every Performance Monitoring MIB.
Properties that are not applicable are displayed as "-1" or as an empty cell.
SNMP Performance Monitoring MIBs
This section describes the Performance Monitoring SNMP MIBs.
- 32 -
CHAPTER6 Performance Monitoring
The tables in this section use check marks "√" and crosses "x" to indicate support for
the specific MIB property:
●"G/C": gauge / counter
●"Int": measuredinterval
●"Val": valueof gauge orcounter
●"Min": minimum gauge value
●"Max": maximum gauge value
●"Avg": averagewithin theinterval
●"TbLT": percentage of interval time that value was below low threshold
●"TbT": percentageof interval time that value was between low and high thresholds
●"TaHT": percentage of interval time that value was above high threshold
●"HT": configured or default highthreshold
●"LT": configured or default low threshold
Performance Monitoring MIBs for IP Network Interfaces
Mediant 800 SBC | S NMP Reference Guide
The following table lists the performance monitoring MIBs for IP network interfaces.
Table 6-1: Performance Monitoring MIBs for IP Network Interface
G
I
Performance Monitoring MIB
V
/
n
C
t
a
l
MinM
ax
A
v
g
Tb
LT
T
TaHTHTL
b
T
■ MIB Name: acPMNetUtilKBytesTable
■ OID: 1.3.6.1.4.1.5003.10.11.2.31.1
■ Source Name: PM_NetUtilKBytes
Indicates the number of Kbytes
(1000 bytes) received and
G1
üüüüüüüûû
5
transmitted on the interface (Index
0 is transmit; Index 1 is receive),
including those received in error,
from the beginning of the current
collection interval as indicated by
the time interval.
T
OVOC parameter name: Number of
Incoming / Outgoing Kbytes
Indicates the number of incoming
and outgoing packets from the
interface (Index 0 is transmit; Index
1 is receive), from the beginning of
the current collection interval as
indicated by time Interval.
OVOC parameter name: Number of
Outgoing / Incoming Pkts.
Indicates the number of
malformed IP packets received on
the interface during the last
interval. These are packets which
are corrupted or discarded due to
errors in their IP headers, including
bad checksums, version number
mismatch, other format errors,
time-to-live exceeded, errors
discovered in processing their IP
options, etc.
C1
5
- 34 -
üûûûûûûûû
CHAPTER6 Performance Monitoring
Performance Monitoring MIB
OVOC parameter name: Number of
Incoming Discarded Pkts.
Performance Monitoring MIBs for Media Realms
The following table lists the performance monitoring MIBs for Media Realms.
Table 6-2: Performance Monitoring MIBs for Media Realms
Mediant 800 SBC | S NMP Reference Guide
G
I
V
/
n
C
t
a
l
MinM
ax
A
v
g
Tb
LT
T
TaHTHTL
b
T
T
G
I
Performance Monitoring MIB
/
n
C
t
■ MIB Name: acPMMediaRealmPacketLossRxTable
■ OID: 1.3.6.1.4.1.5003.10.8.2.53.10
■ Source Name: PM_MediaRealmPacketLossRx
Indicates the received RTP packet loss
(reported by RTCP) per Media Realm.
G1
5
■ MIB Name: acPMMediaRealmPacketLossTxTable
■ OID: 1.3.6.1.4.1.5003.10.8.2.53.11
■ Source Name: PM_MediaRealmPacketLossTx
Indicates the transmitted RTP packet
loss (reported by RTCP) per Media
Realm.
G1
5
V
M
M
a
i
a
l
n
x
T
A
v
g
T
b
b
L
T
T
û ü ü ü ü ü ü
û ü ü ü ü ü ü
T
a
H
T
HTLT
5030
5030
■ MIB Name: acPMMediaRealmBytesTxTable
■ OID: 1.3.6.1.4.1.5003.10.8.2.53.1
■ Source Name: PM_MediaRealmBytesTx
Indicates the number of bytes received
in RTCP data, per Media Realm.
Indicates the current number of
established calls pertaining to a
Trunk Group for IP-to-Tel calls.
G1
üûûûûûûûû
5
Trunks
The following table lists the performance monitoring MIB for trunks.
Table 6-7: Performance Monitoring MIBs for Trunks
Performance
Monitoring MIB
■ MIB Name: dsx1IntervalTable
■ OID: 1.3.6.1.2.1.10.18.8
G/CIntValMinMaxAvgTbLTTbTTaHTHTL
T
- 55 -
CHAPTER6 Performance Monitoring
Mediant 800 SBC | S NMP Reference Guide
Performance
Monitoring MIB
The DS1 Interval
Table contains
various statistics
collected by each
DS1 Interface over
the previous 24
hours. The past 24
hours are broken
into 96 completed
15-minute intervals.
Each row in this
table represents
one such interval
(identified by
dsx1IntervalNumbe
r) for one specific
instance (identified
by
dsx1IntervalIndex:
G/CIntValMinMaxAvgTbLTTbTTaHTHTL
G15
üûûûûûûûû
T
■ dsx1IntervalESs:
Number of
Errored Seconds
(OVOC
parameter
name: Trunk
Errored
Seconds)
■
dsx1IntervalCSS
s: Number of
Controlled Slip
Seconds (OVOC
parameter
name: Trunk
Controlled Slip
Seconds)
Indicates the number of channels
currently in use (busy) per trunk group.
For example, if the device has 240
channels and the threshold is set to 106, if
the number of concurrent busy channels
exceeds 106, this threshold alarm is sent.
Note that if a trunk is in LOF state, this
MIB counts only the channels that are
used.
Indicates the percentage (%) of channels
currently in use (busy) per trunk group.
The device supports configuration of a
busy channel threshold per trunk group,
which when exceeded, sends an SNMP
alarm. For example, if a device has 200
voice channels and the threshold is set to
90%, if the number of concurrent busy
channels exceeds 90% (i.e., 180 channels),
this threshold alarm is sent.
Indicates the duration (in seconds) that all
channels of a specific trunk group were
G1
üûûûûûûûû
5
- 60 -
CHAPTER6 Performance Monitoring
Mediant 800 SBC | S NMP Reference Guide
G
I
V
M
M
Performance Monitoring MIB
concurrently busy, if this scenario occurs.
For example, if trunk group #3 has 200
channels and all these were concurrently
busy for 60 seconds, then this MIB will
display 60 for this trunk group. Note that
trunks that are out of service or not
configured (set to NONE) are considered
"busy" in this calculation.
Indicates the percentage (%) of time
within a 15-minute polling interval, that all
channels in a specific trunk group were
busy simultaneously. This measurement
is sent only at the end of the interval
(beginning of the current interval), so
each measurement reflects the previous
interval. For example, assume that all
trunks of a trunk group were busy for 6
minutes during an interval. The MIB will
send a measurement of 40% (i.e., 6
minutes / 15 minutes * 100). In other
words, all trunks of the trunk group were
simultaneously busy for 40% of the time
during this 15-minute interval.
This section describes the performance monitoring MIBs of the SBC application.
SBC Sessions
The following table lists the performance monitoring MIBs for SBC sessions. For MIBs that
have low and high thresholds, if a threshold is crossed the device sends the acPerformanceMonitoringThresholdCrossing trap (see Performance Monitoring Threshold-Crossing
Trap on page162).
Table 6-9: Performance Monitoring MIBs for SBC Sessions
G
I
Performance Monitoring MIB
/
n
C
t
■ MIB Name: acPMSIPSBCAttemptedCallsTable
■ OID: 1.3.6.1.4.1.5003.10.8.2.52.42
■ Source Name: PM_gwSBCAttemptedCalls
V
a
l
M
in
M
A
T
T
Ta
a
v
b
b
x
g
LT
T
HTL
H
T
T
Indicates the number of attempted
SBC calls. It applies only to SIP dialoginitiating INVITE messages and
counts both incoming and outgoing
C1
- 62 -
üüüüüüü
5
00
CHAPTER6 Performance Monitoring
Performance Monitoring MIB
legs per call. Therefore, each
successful call increments the
counter by 2. If the INVITE fails
Classification stage, only the
incoming side is counted (i.e.,
counter incremented only by 1).
Indicates the total number of
established calls that were
disconnected because no RTP
packets (media) were received for a
user-defined period (configured by
the BrokenConnectionEventTimeout
parameter).
C1
üûûûûûûûû
5
■ MIB Name: acPMSBCInShortCallsTable
■ OID: 1.3.6.1.4.1.5003.10.8.2.54.152.1
■ Source Name: PM_gwSBCInShortCalls
Indicates the total number of
incoming calls whose duration was
less than the value configured by the
- 64 -
C1
üûûûûûûûû
5
CHAPTER6 Performance Monitoring
Performance Monitoring MIB
ShortCallSeconds parameter.
■ MIB Name: acPMSBCOutShortCallsTable
■ OID: 1.3.6.1.4.1.5003.10.8.2.54.152.2
■ Source Name: PM_gwSBCOutShortCalls
Mediant 800 SBC | S NMP Reference Guide
G
I
V
/
n
a
C
t
l
M
in
M
A
T
T
Ta
a
v
b
b
x
g
LT
T
HTL
H
T
T
Indicates the total number of
outgoing calls whose duration was
less than the value configured by the
ShortCallSeconds parameter.
C1
üûûûûûûûû
5
■ MIB Name: acPMSBCInAttemptedRegistrationsTable
■ OID: 1.3.6.1.4.1.5003.10.8.2.54.153.1
■ Source Name: PM_gwSBCInAttemptedRegistrations
Indicates the number of incoming
attempted SBC registrations.
C1
üûûûûûûûû
5
■ MIB Name: acPMSBCOutAttemptedRegistrationsTable
■ OID: 1.3.6.1.4.1.5003.10.8.2.54.153.2
■ Source Name: PM_gwSBCOutAttemptedRegistrations
Indicates the number of outgoing
attempted SBC registrations.
C1
üûûûûûûûû
5
■ MIB Name: acPMSBCInSuccessfulRegistrationsTable
■ OID: 1.3.6.1.4.1.5003.10.8.2.54.154.1
■ Source Name: PM_gwSBCInSuccessfulRegistrations
Indicates the number of incoming
successful registrations.
of established calls per
IP Group that were
disconnected because
no RTP packets (media)
were received for a
user-defined period
(configured by the
BrokenConnectionEven
tTimeout parameter).
■ MIB Name: acPMSBCIPGroupInShortCallsTable
■ OID: 1.3.6.1.4.1.5003.10.8.2.54.152.5
■ Source Name: PM_gwSBCIPGroupInShortCalls
Indicates the number
C15
üûûûûûûûû
of incoming calls per IP
Group, whose duration
was less than the value
configured by the
ShortCallSeconds
parameter.
HT
HTLT
■ MIB Name: acPMSBCIPGroupOutShortCallsTable
■ OID: 1.3.6.1.4.1.5003.10.8.2.54.152.6
■ Source Name: PM_gwSBCIPGroupOutShortCalls
Indicates the number
C15
üûûûûûûûû
of outgoing calls per IP
Group, whose duration
was less than the value
configured by the
ShortCallSeconds
parameter.
Indicates the number of
outgoing successful
registrations per SRD.
C15
üûûûûûûûû
HT
HTLT
SBC Call Admission Control
The following table lists the performance monitoring MIBs for SBC Call Admission Control.
Performance monitoring is performed per:
■ SRD/IP Group
■ Incoming, outgoing, or both
■ SIP request types - INVITE, SUBSCRIBE, OTHER, or ALL
Performance monitoring is provided by the acGateway MIB.
For MIBs with high and low thresholds, if a threshold is crossed the device sends the acPerformanceMonitoringThresholdCrossing trap (see Performance Monitoring Threshold-Crossing
Trap on page162).
Table 6-12: Performance Monitoring MIBs for SBC Call Admission Control
Performance Monitoring MIB
G
I
V
M
M
/
n
a
i
a
C
t
l
n
x
T
A
b
v
L
g
T
T
T
a
b
T
HTL
H
T
T
■ MIB Name: acPMSIPSRDDialogsTable
■ OID: 1.3.6.1.4.1.5003.10.8.2.52.17
- 78 -
CHAPTER6 Performance Monitoring
Mediant 800 SBC | S NMP Reference Guide
G
Performance Monitoring MIB
/
C
■ Source Name: PM_gwSRDDialogs
Indicates the number of all dialogs
currently being handled by the SBC per
SRD.
G1
■ MIB Name: acPMSIPSRDInviteDialogsTable
■ OID: 1.3.6.1.4.1.5003.10.8.2.52.18
■ Source Name: PM_gwSRDINVITEDialogs
Indicates the number of all calls (initiated
by SIP:INVITE) currently being handled
by the SBC per SRD.
G1
■ MIB Name: acPMSIPSRDSubscribeDialogsTable
I
V
M
M
n
a
i
a
t
l
n
x
T
A
b
v
L
g
T
T
T
a
b
H
T
T
üûûûûûûûû
5
üûûûûûûûû
5
HTL
T
■ OID: 1.3.6.1.4.1.5003.10.8.2.52.19
■ Source Name: PM_gwSRDSUBSCRIBEDialogs
Indicates the number of all SUBSCRIBE
dialogs (initiated by SIP:SUBSCRIBE)
currently being handled by the SBC per
SRD.
G1
■ MIB Name: acPMSIPSRDOtherDialogsTable
■ OID: 1.3.6.1.4.1.5003.10.8.2.52.20
■ Source Name: PM_gwSRDOtherDialogs
Indicates the number of all dialogs other
than INVITE and SUBSCRIBE (initiated by
SIP:REGISTER) currently being handled
by the SBC per SRD.
G1
■ MIB Name: acPMSIPIPGroupDialogsTable
■ OID: 1.3.6.1.4.1.5003.10.8.2.52.21
üûûûûûûûû
5
üûûûûûûûû
5
■ Source Name: PM_gwIPGroupDialogs
Indicates the number of all dialogs
currently being handled by the SBC per
- 79 -
G1
üûûûûûûûû
5
CHAPTER6 Performance Monitoring
Mediant 800 SBC | S NMP Reference Guide
G
I
Performance Monitoring MIB
IP Group.
/
n
C
t
■ MIB Name: acPMSIPIPGroupSubscribeDialogsTable
■ OID: 1.3.6.1.4.1.5003.10.8.2.52.23
■ Source Name: PM_gwIPGroupSUBSCRIBEDialogs
Indicates the number of all SUBSCRIBE
dialogs (initiated by SIP:SUBSCRIBE)
currently being handled by the SBC, per
IP Group.
Indicates the number of all other dialogs
other than INVITE and SUBSCRIBE
(initiated by SIP:REGISTER) currently
being handled by the SBC per IP Group.
G1
5
■ MIB Name: acPMSIPIPGroupInOtherDialogsTable
■ OID: 1.3.6.1.4.1.5003.10.8.2.52.34
■ Source Name: PM_gwIPGroupInOtherDialogs
Indicates the number of all incoming
dialogs other than INVITE and
SUBSCRIBE (initiated by SIP:REGISTER)
currently being handled by the SBC per
IP Group.
G1
5
üûûûûûûûû
üûûûûûûûû
- 80 -
CHAPTER6 Performance Monitoring
Mediant 800 SBC | S NMP Reference Guide
G
I
Performance Monitoring MIB
/
n
C
t
■ MIB Name: acPMSIPIPGroupOutOtherDialogsTable
■ OID: 1.3.6.1.4.1.5003.10.8.2.52.37
■ Source Name: PM_gwIPGroupOutOtherDialogs
Indicates the number of all outgoing
dialogs other than INVITE and
SUBSCRIBE (initiated by SIP:REGISTER)
currently being handled by the SBC per
IP Group.
G1
üûûûûûûûû
5
■ MIB Name: acPMSIPIPGroupInInviteDialogsTable
■ OID: 1.3.6.1.4.1.5003.10.8.2.52.32
■ Source Name: PM_gwIPGroupInINVITEDialogs
V
M
M
a
i
a
l
n
x
T
A
b
v
L
g
T
T
T
a
b
T
HTL
H
T
T
Indicates the number of incoming calls
(SIP INVITE) per IP Group.
The following table lists the performance monitoring MIBs for SBC Quality of Service.
Performance monitoring is performed per SRD, IP Group or global (all). Major and Minor
thresholds can be configured for each performance monitoring metric through the Web
interface (only). If the thresholds are crossed, an SNMP alarm is sent (see
acASRThresholdAlarm, AcNERThresholdAlarm, and acACDThresholdAlarm).
Table 6-13: Performance Monitoring MIBs for SBC Call Quality of Service
Performance
Monitoring MIB
■ MIB Name: acPMSBCAsrTable
■ OID: 1.3.6.1.4.1.5003.10.8.2.54.49
■ Source Name: PM_gwSBCASR
Indicates the
Answer-seizure
Ratio (ASR) for all
(global) entities
(i.e., all IP Groups
and SRDs).
G/CIntValMinMaxAvgTbLTTbTTaHTHTLT
G15
üüüüûûûûû
■ MIB Name: acPMSBCIPGroupAsrTable
- 84 -
CHAPTER6 Performance Monitoring
Mediant 800 SBC | S NMP Reference Guide
Performance
Monitoring MIB
G/CIntValMinMaxAvgTbLTTbTTaHTHTLT
■ OID: 1.3.6.1.4.1.5003.10.8.2.54.50
■ Source Name: PM_gwSBCIPGroupASR
Indicates ASR per
G15
üüüüûûûûû
IP Group.
■ MIB Name: acPMSBCSrdAsrTable
■ OID: 1.3.6.1.4.1.5003.10.8.2.54.51
■ Source Name: PM_gwSBCSRDASR
Indicates ASR per
G15
üüüüûûûûû
SRD.
■ MIB Name: acPMSBCNerTable
■ OID: 1.3.6.1.4.1.5003.10.8.2.54.55
■ Source Name: PM_gwSBCNER
Indicates the
G15
üüüüûûûûû
Network
Effectiveness
Ratio (NER) for all
(global) entities
(i.e., all IP Groups
and SRDs).
■ MIB Name: acPMSBCIPGroupNerTable
■ OID: 1.3.6.1.4.1.5003.10.8.2.54.56
■ Source Name: PM_gwSBCIPGroupNER
Indicates NER per
G15
üüüüûûûûû
IP Group.
■ MIB Name: acPMSBCSrdNerTable
■ OID: 1.3.6.1.4.1.5003.10.8.2.54.57
■ Source Name: PM_gwSBCSRDNER
Indicates NER per
G15
SRD.
■ MIB Name: acPMSBCAcdTable
üüüüûûûûû
- 85 -
CHAPTER6 Performance Monitoring
Mediant 800 SBC | S NMP Reference Guide
Performance
Monitoring MIB
G/CIntValMinMaxAvgTbLTTbTTaHTHTLT
■ OID: 1.3.6.1.4.1.5003.10.8.2.54.52
■ Source Name: PM_gwSBCACD
Indicates the
G15
üüüüûûûûû
Average Call
Duration (ACD)
for all (global)
entities (i.e., all IP
Groups and
SRDs).
■ MIB Name: acPMSBCIPGroupAcdTable
■ OID: 1.3.6.1.4.1.5003.10.8.2.54.53
■ Source Name: PM_gwSBCIPGroupACD
Indicates ACD
G15
üüüüûûûûû
per IP Group.
■ MIB Name: acPMSBCSrdAcdTable
■ OID: 1.3.6.1.4.1.5003.10.8.2.54.54
■ Source Name: PM_gwSBCSRDACD
Indicates ACD
G15
üüüüûûûûû
per SRD.
■ MIB Name: acPMSBCInCapsTable
■ OID: 1.3.6.1.4.1.5003.10.8.2.54.59
■ Source Name: PM_gwSBCInCPS
Indicates the
G15
üüüüûûûûû
number of
incoming calls
per second.
SBC Calls Per Second
The following table lists the performance monitoring MIBs for SBC calls per second (CPS).
- 86 -
CHAPTER6 Performance Monitoring
Table 6-14: Performance Monitoring MIBs for SBC Calls Per Second
Performance
Monitoring
G/CIntValMinMaxAvgTbLTTbTTaHTHTLT
MIB
■ MIB Name: acPMSBCInCapsTable
■ OID: 1.3.6.1.4.1.5003.10.8.2.54.59
■ Source Name: PM_gwSBCInCPS
Mediant 800 SBC | S NMP Reference Guide
Indicates
G15
üüüüûûûûû
the number
of CPS for
incoming
SBC calls.
■ MIB Name: acPMSBCOutCapsTable
■ OID: 1.3.6.1.4.1.5003.10.8.2.54.60
■ Source Name: PM_gwSBCOutCPS
Indicates
G15
üüüüûûûûû
the number
of CPS for
outgoing
SBC calls.
■ MIB Name: acPMSBCSrdInCapsTable
■ OID: 1.3.6.1.4.1.5003.10.8.2.54.63
■ Source Name: PM_gwSBCSRDInCPS
Indicates
G15
üüüüûûûûû
the number
of CPS for
incoming
SBC calls per
SRD.
■ MIB Name: acPMSBCSrdOutCapsTable
■ OID: 1.3.6.1.4.1.5003.10.8.2.54.64
■ Source Name: PM_gwSBCSRDOutCPS
Indicates
G15
üüüüûûûûû
the number
- 87 -
CHAPTER6 Performance Monitoring
Performance
Monitoring
G/CIntValMinMaxAvgTbLTTbTTaHTHTLT
MIB
of CPS for
outgoing
SBC calls per
SRD.
■ MIB Name: acPMSBCIPGroupInCapsTable
■ OID: 1.3.6.1.4.1.5003.10.8.2.54.61
■ Source Name: PM_gwSBCIPGroupInCPS
Mediant 800 SBC | S NMP Reference Guide
Indicates
the number
of CPS for
incoming
SBC calls per
IP Group.
G15
üüüüûûûûû
■ MIB Name: acPMSBCIPGroupOutCapsTable
■ OID: 1.3.6.1.4.1.5003.10.8.2.54.62
■ Source Name: PM_gwSBCIPGroupOutCPS
Indicates
the number
of CPS for
outgoing
SBC calls per
IP Group.
G15
üüüüûûûûû
Performance Monitoring MIBs for High Availability
The following table lists the performance monitoring MIBs for the High Availability (HA) mode.
Table 6-15: Performance Monitoring MIBs for High-Availability
Indicates packet loss (in %) on the HA
Maintenance interface from Active to
Redundant device, where 0% indicates no
packet loss.
G1
ü ü ü ü ü ü ü
5
■ High threshold:
acPMHAAttributesHALinkActiveToRedu
ndantPacketLossPercentageHighThresh
old (1.3.6.1.4.1.5003.10.11.1.38.3)
■ Low threshold:
acPMHAAttributesHALinkActiveToRedu
ndantPacketLossPercentageLowThresh
old (1.3.6.1.4.1.5003.10.11.1.38.4)
Performance Monitoring MIB for DSP Resource Utilization
305
The following table lists the SNMP MIB that reports the percentage of DSP resources utilized by
the device. Low and high thresholds can also be defined, which if crossed, the SNMP trap
event, acPerformanceMonitoringThresholdCrossing is sent by the device.
- 89 -
CHAPTER6 Performance Monitoring
Table 6-16: Performance Monitoring MIB for DSP Utilization
Performance Monitoring MIB
■ MIB Name: acPMDSPUsageTable
■ OID: 1.3.6.1.4.1.5003.10.7.2.25
■ Source Name: PM_VEDSPUsage
Mediant 800 SBC | S NMP Reference Guide
G
I
V
/
n
C
t
a
l
MinM
ax
A
T
T
v
bL
g
T
b
T
TaHTH
LT
T
Indicates the percentage (%) of DSP
resources utilized by the device. A
value of 0% indicates that no DSP
resources have been used; a value
of 100% indicates that all DSP
resources have been used.
snmpMIB(1). snmpMIBObjects(1). snmpTraps(5). coldStart(1) sent at system
initialization.
Mediant 800 SBC | S NMP Reference Guide
●Enterprise acBoardEvBoardStarted: generated at the end of system initialization. This
is more of an "application-level" cold start sent after all the initializing process is over
and all the modules are ready
■ linkDown
■ linkup
■ entConfigChange
■ dsx1LineStatusChange (Applicable only to Digital Series)
Proprietary Traps
This section provides information on proprietary SNMP traps supported by the device. There is
a separation between traps that are alarms and traps that are not (i.e., logs). All traps have the
same structuremadeupof thesame16varbinds(VariableBinding),i.e.,
1.3.6.1.4.1.5003.9.10.1.21.1. For a list of the varbinds, see Trap Varbinds on the next page.
The source varbind is composed of a string that details the device component from which the
trap is being sent (forwarded by the hierarchy in which it resides). For example, an alarm from
an SS7 link has the following string in its source varbind: acBoard#1/SS7#0/SS7Link#6. The SS7
link number is specified as 6 and is part of the only SS7 module in the device that is placed in
slot number 1 (in a chassis) and is the module to which this trap relates. For devices where
there are no chassis options, the slot number is always 1.
Full proprietary trap definitions and trap varbinds are found in AcBoard MIB and AcAlarm MIB.
All traps are sent from the SNMP port (default 161).
- 91 -
Loading...
+ hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.