550-08889 05.01 SBC Core 11.01.00R000 Alarms and Troubleshooting

SBC Core
Alarms and Troubleshooting Guide

Software Release: 11.01.00R000
Document Revision: 05.01
Published: December 15, 2022
https://ribboncommunications.com 550-08889
Copyright
© 2020-2022 Ribbon Communications Operating Company, Inc. © 2020-2022 ECI Telecom Ltd. All rights reserved. The compilation (meaning the
collection, arrangement and assembly) of all content on this site is protected by U.S. and international copyright laws and treaty provisions and may not
be used, copied, reproduced, modified, published, uploaded, posted, transmitted or distributed in any way, without prior written consent of Ribbon
Communications Inc.
Disclaimer and Restrictions

The publication is for information purposes only and is subject to change without notice. This publication does not constitute a commitment on the part of
Ribbon. While reasonable efforts have been made in the preparation of this publication to assure its accuracy, Ribbon assumes no liability resulting from
technical or editorial errors or omissions, or for any damages whatsoever resulting from the furnishing, performance, or use of the information contained
herein. Ribbon reserves the right to make changes to this publication and to Ribbon products without notice in its sole discretion. This publication is not
meant to define any interfaces between Ribbon products and any third-party hardware or software products.
Warranties
THIS INFORMATION IS PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NONINFRINGEMENT. IN NO
EVENT SHALL RIBBON BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OR PERFORMANCE OF THIS INFORMATION, EVEN IF
ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Compliance with Applicable Laws and Export Control Laws

The information in this publication is subject to all applicable U.S. federal, state, and local laws. The customer use, distribution, and transfer of any
technical information shall be in compliance with all applicable export and import laws and regulations. All Ribbon products and publications are
commercial in nature; and the use, duplication, or disclosure by the United States Government is subject to the restrictions set forth in DFARS 252.227-
7013 and FAR 52.227-19.
Trademarks
The trademarks, logos, service marks, trade names, and trade dress (“look and feel”) on this website, including without limitation the RIBBON and
RIBBON logo marks, are protected by applicable US and foreign trademark rights and other proprietary rights and are the property of Ribbon
Communications Operating Company, Inc. or its affiliates. Any third-party trademarks, logos, service marks, trade names and trade dress may be the
property of their respective owners. Any uses of the trademarks, logos, service marks, trade names, and trade dress without the prior written consent of
Ribbon Communications Operating Company, Inc., its affiliates, or the third parties that own the proprietary rights, are expressly prohibited.
UNCONTROLLED COPY: The original content is stored in an electronic database and is “write protected”; it may be altered only by authorized persons.
While copies may be printed, it is not recommended. Viewing of the original content electronically ensures access to the current content. Any hardcopies
taken must be regarded as uncontrolled copies.
For access to the technical documentation, log in through Ribbon Support Services website at
https://ribboncommunications.com/services/support-services/technical-documentation
Copyright © 2020-2022 Ribbon Communications Operating Company, Inc. (''Ribbon''). © 2020-2022 ECI Telecom Ltd. Page 2
1. SBC Core Alarms Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.1 Alarms vs Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
1.1.1 Alarm Field Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
1.1.2 SNMP Trap Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
1.2 Alarms Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
1.2.1 Critical Alarms List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
1.2.2 Major Alarms List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
1.3 SBC Alarm Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
1.3.1 Accounting Services Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
1.3.2 Call Processing Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
1.3.3 Database Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
1.3.4 Dialog Transparency Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
1.3.5 Diameter Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
1.3.6 Distributed SBC (D-SBC) Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
1.3.7 Domain Name Server (DNS) Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
1.3.8 DSP Availability Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
1.3.9 Dynamic Blacklist Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
1.3.10 Gateway Signaling Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
1.3.11 GETS and WPS Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
1.3.12 H248 Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
1.3.13 Internal Micro-Services Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
1.3.14 IP Interface Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
1.3.15 JSRC Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
1.3.16 Lawful Intercept Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
1.3.17 License Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
1.3.18 Machine Congestion Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219
1.3.19 Master Trunk Group Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
1.3.20 Media Port Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
1.3.21 Media Port Redundancy Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231
1.3.22 Monitoring Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
1.3.23 Network Management Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
1.3.24 Node Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240
1.3.25 Node Resources Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
1.3.26 OAM Node Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
1.3.27 Path Check Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262
1.3.28 Platform Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300
1.3.29 Policy Server Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321
1.3.30 Registration Event Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335
1.3.31 Resource Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337
1.3.32 SBC SWe Active Profile Commit Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339
1.3.33 Security Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340
1.3.34 SIP Recording Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359
1.3.35 SIP Resource Priority Header (RPH) Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361
1.3.36 SIP Signaling Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362
1.3.37 Softswitch Client Services Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379
1.3.38 Sonus WebRTC Gateway (WRTC) Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384
1.3.39 Tone and Announcement Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387
1.3.40 Surrogate Registration Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 388
1.3.41 Trunk Group Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392
1.3.42 VNFM Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 400
1.3.43 GPU Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 409
1.4 New and Deprecated Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 409
2. SBC Core Troubleshooting Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413
2.1 Basic Debugging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415
2.2 Debugging OOS Reasons for GR-HA Port Connections with ARP-Based Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417
2.3 Debugging SBC SWe in Public Cloud . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 420
2.3.1 Debug General SBC SWe Public Cloud . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 421
2.3.2 Debug SBC SWe in AWS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 422
2.3.3 Debug SBC SWe in Azure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429
2.3.4 Debug SBC SWe in GCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 435
2.3.5 Recovering SSH Key Access in Public Cloud and Updating User Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 439
2.4 Debugging SBC SWe Virtual and in Private Cloud . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442
2.4.1 Cloud Diagnostic Tool User Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 445
2.5 For Troubleshooting Only - How to Enable ssh Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 456
2.6 SBC Troubleshooting Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 458
2.7 Troubleshooting SBC Using Debug Event Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 461
2.8 Using SBC Packet Collector for Core Dump Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 464
2.9 Using Test Calls and IP Trunk Group Blocking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 468
2.10 Using the SSReq Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 469
2.10.1 Using SSReq . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 472
2.10.2 SSReq User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 478
2.10.3 Status Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 489
2.10.4 Viewing a Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 490
2.10.5 Response Field Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 491
2.10.6 SSReq Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 496
SBC Core Alarms Guide
Table of Contents
Alarms vs Traps
Alarm Field Definitions
SNMP Trap Management
Alarms Management
Critical Alarms List
Major Alarms List
SBC Alarm Details

Accounting Services Alarms
Call Processing Alarms
Database Alarms
Dialog Transparency Alarm
Diameter Alarms
Distributed SBC (D-SBC) Alarms
Domain Name Server (DNS) Alarms
DSP Availability Alarms
Dynamic Blacklist Alarms
Gateway Signaling Alarms
GETS and WPS Alarms
H248 Alarms
Internal Micro-Services Alarms
IP Interface Alarms
JSRC Alarms
Lawful Intercept Alarms
License Alarms
Machine Congestion Alarms
Master Trunk Group Alarms
Media Port Alarms
Media Port Redundancy Alarms
Monitoring Alarms
Network Management Alarms
Node Alarms
Node Resources Alarms
OAM Node Alarms
Path Check Alarms
Platform Alarms
Policy Server Alarms
Registration Event Alarms
Resource Alarms
SBC SWe Active Profile Commit Alarms
Security Alarms
SIP Recording Alarms
SIP Resource Priority Header (RPH) Alarms
SIP Signaling Alarms
Softswitch Client Services Alarms
Sonus WebRTC Gateway (WRTC) Alarms
Tone and Announcement Alarm
Surrogate Registration Alarms
Trunk Group Alarms
VNFM Alarms
GPU Alarms
New and Deprecated Alarms
This guide provides detailed alarm and event information related to the SBC Core platform to aid in isolating and troubleshooting system fault
conditions.
Each event listing in this guide provides the event definition, severity level, associated event codes, impact to system, action to take to rectify the
fault condition, as well as event repetition and clearing information.
Info
For consolidated lists of Critical and Major alarms, refer to Critical Alarms List and Major Alarms List.
Alarms vs Traps
In this section: Related articles:
Overview Alarm Field Definitions

Alarm Definition SNMP Trap Management
SNMP Trap Definition
How to Configure SNMP Trap Targets
SNMP Traps
SNMP - Trap Target
SNMP - CLI
Show Table Alarms, Alarms - CLI
Administration - Traps and SNMP (EMA)
OAM - Alarm,Dashboard - Alarms (EMA)
Overview
The SBC, like other Ribbon devices, uses SNMP traps to notify management applications of events. SNMP traps are the messages that notify a
management client that an event has occurred on the SBC node. These traps are not displayed in EMA and can be viewed from Insight EMS or
other SNMP manager configured as a trap target. In case of error scenario, a trap is initiated at the device and forwarded to the EMS or to the
other SNMP manager for processing.
You can configure up to 32 trap targets on the SBC.
Alarm Definition
A trap is considered an alarm when there is a condition that needs attention by the operator. Some alarms clear themselves, such as a port up
/down alarm. Other alarms require manual intervention to clear.
Alarms provide alerts/warnings of abnormal activity such as a software failures, system faults, exceptions, hardware issues, and so on. Alarms
are primarily viewed using the CLI and EMA interfaces. Some major and critical alarms also have LED indicators on the SBC physical server.
The SBC displays alarms according to the following categories:
Current alarms
History alarms
Current Alarms
The Current Alarms screen displays the alarms that are not cleared. Current alarms are viewed using EMA and CLI.
To display the current alarms using CLI, execute the following command:
% show table alarms currentStatus
The results display similar to the figure Current alarms (displayed in CLI mode):
Current alarms (displayed in CLI mode)
To display the Current alarms using EMA,
On the SBC main screen, navigate to Monitoring > Dashboard > Alarms > Current Alarms
History Alarms
History Alarms provides historical information about the alarms which occurred on the system, such as the time when the alarms were added
/updated/modified/cleared. Historical alarm details are displayed using CLI or from the EMA Dashboard.
For example, to display the list of alarms which occurred on the SBC, type the following command in the CLI:
> show table alarms historyStatus
The output is displayed similar to the figure below:
History alarms output.
To view the cleared alarms in the SBC EMA, from the EMA menu navigate to Monitoring > Dashboard > Alarms > Cleared Alarms.
The status of the alarms are also available in the following locations of the EMA:
Current Alarms - All > Alarms > Current Status

History Alarms - All > Alarms > History Status
For additional details with viewing alarms and configuring SBC for alarms, refer:
CLI: Show Table Alarms, Alarms - CLI
EMA: OAM - Alarm, Dashboard - Alarms
SNMP Trap Definition

Traps are events reported by the SNMP devices. Some SNMP traps are also alarms, which require attention by the operator from the UI (EMA)
or CLI.
References:
To configure trapTarget using CLI: How to Configure SNMP Trap Targets

To configure trap Target using EMA: SNMP - Trap Target
To configure traps using EMS SNMP Trap Management
To view the the related alarms, type the command:
show table alarms currentStatus
To view trap configuration details, refer to
CLI: SNMP - CLI

EMA: Administration - Traps and SNMP
SNMP Traps
The following SNMP traps are not implemented as alarms.
Category SBC Core Traps
Encryption sonusCdbEncryptionKeyRegeneratedNotification
sonusCdbEncryptionKeyZeroizedNotification
ConnexIp sonusConnexIpSystemCEFanFailureNotification
sonusConnexIpSystemCEFanNormalNotification
sonusConnexIpSystemCESlotDryupNotification
sonusConnexIpSystemCESlotFailedNotification
Call Processor sonusCpCdrServerNewXferPendingNotification
sonusCpCdrServerPendingQueueEmptiedNotification
sonusCpCdrServerSwitchoverNotification
sonusCpConfigCommitFailNotification
sonusCpConfigCommitSucceedNotification
sonusCpConfigHaInSyncNotify
sonusCpConfiguredExceedSystemLimit
sonusCpDataAgentAddStreamNotification
sonusCpDataAgentRemoveStreamNotification
sonusCpEventLogDirectoryCreateErrorNotification
sonusCpEventLogFileClosedNotification
sonusCpEventLogFileCountChngNotification
sonusCpEventLogFileCreatedNotification
sonusCpEventLogFileDeletedNotification
sonusCpEventLogFileFilterLevelChngNotification
sonusCpEventLogFileMaxEventMemSizeChngNotification
sonusCpEventLogFileMsgQueueChngNotification
sonusCpEventLogFileRenamedNotification
sonusCpEventLogFileSizeChngNotification
sonusCpEventLogFileSkipped
sonusCpEventLogFileStateNotification
sonusCpEventLogRolloverFastNotification
sonusCpEventLogRolloverScheduledNotification
sonusCpEventLogRolloverStoppedNotification
sonusCpEventLogSaveToChngNotification
sonusCpEventMgrAlarmAckStateUpdate
sonusCpEventMgrAlarmCommentUpdate
sonusCpEventMgrAlarmManualClear
sonusCpfRcrDcfErrorRateClearedNotification
sonusCpLicenseBundleExpireWarningNotification
sonusCpLicenseBundleRenewedNotification
sonusCpLicenseExpireSoonWarningNotification
sonusCpLicenseExpireWarningNotification
sonusCpLicenseFingerprintMismatch
sonusCpLicenseHostSerialUnavailable
sonusCpLicensePeerSerialMismatch
sonusCpLicenseReleased
sonusCpLicenseServerNameResolutionError
sonusCpMaxPacketLengthErrorRateClearedNotification
sonusCpMaxPacketLengthErrorRateExceededNotification
sonusCpNiceRecLicenseExpireSoonWarningNotification
sonusCpNiceRecLicenseExpireWarningNotification
sonusCpNifByteEnableBusErrorNotification
sonusCpNifCodeViolationErrorRateClearedNotification
sonusCpNifCodeViolationErrorRateExceededNotification
sonusCpNifCrcErrorRateClearedNotification
sonusCpNifCrcErrorRateExceededNotification
sonusCpNifDataControlFifoErrorNotification
sonusCpNifDroppedPacketsRateExceededNotification
sonusCpNifMailBoxNotification
sonusCpNifNackPacketReadErrorNotification
sonusCpNifNackPrefetchErrorNotification
sonusCpNifPacketPointerErrorNotification
sonusCpNifPacketSizeErrorNotification
sonusCpNifPageViolationErrorNotification
sonusCpNifParityErrorNotification
sonusCpNifPartitionErrorNotification
sonusCpNifPrefetchParityErrorNotification
sonusCpNifRateDroppedPacketsClearedNotification
sonusCpNifRbrFullErrorNotification
sonusCpNifRbrLogicalPageErrorNotification
sonusCpNifRbrPrefetchEmptyErrorRateClearedNotification
sonusCpNifRbrTimeoutNotification
sonusCpNifRcrAckErrorNotification
sonusCpNifRcrDcfErrorRateExceededNotification
sonusCpNifRcrErrorRateClearedNotification
sonusCpNifRcrErrorRateExceededNotification
sonusCpNifRcrInconsistencyErrorNotification
sonusCpNifRcrRingFullErrorNotification
sonusCpNifRcrShadowParityErrorNotification
sonusCpNifResourceErrorRateClearedNotification
sonusCpNifResourceErrorRateExceededNotification
sonusCpNifResponseCountErrorNotification
sonusCpNifRingOverflowErrorRateClearedNotification
sonusCpNifRingOverflowErrorRateExceededNotification
sonusCpNifWredDroppedPacketsRateClearedNotification
sonusCpNifWredDroppedPacketsRateExceededNotification
sonusCpNodeHaPortDownNotification
sonusCpNtpServerReachableNotification
sonusCpRadiusServerFailedNotification
sonusCpRadiusServerPacketsFlushedNotification
sonusCpSoftwareUpgradeCommittedNotification
sonusCpSoftwareUpgradeRevertNotification
sonusCpSystemCEOperationalNotification
sonusCpSystemCoredumpSpaceWarningNotification
sonusCpSystemCriticalUserEventNfy
sonusCpSystemFaultAvalancheControlPacketDroppedNotify
sonusCpSystemFaultyHardDiskNotify
sonusCpSystemInfoUserEventNfy
sonusCpSystemLocalDiskBadVolumeNotification
sonusCpSystemLocalDiskMisMatchNotification
sonusCpSystemLocalDiskSpaceReadOnlyNotification
sonusCpSystemLocalDiskTooManyFilesNotification
sonusCpSystemLocalDiskWritableNotification
sonusCpSystemMajorUserEventNfy
sonusCpSystemMemoryModuleFaultNotify
sonusCpSystemMinorUserEventNfy
sonusCpSystemNotMacAddressOwnerNotification
sonusCpSystemReadonlyFileSystemNotify
sonusCpSystemRestoreConfigNotification
sonusCpVmRedundancyModeNotification
H.248 sonusH248ScFailoverTxStatusNotification
Fingerprint sonusInvalidFingerPrintNotification
IPv6 sonusIPv6DuplicateManualReviewNoRebootNotification
sonusIPv6DuplicateManualReviewRebootingNotification
OCSP sonusInvalidOcspResponseReceived
sonusNoValidOcspResponseReceived
sonusOcspConnectionFailed
sonusOcspExceptionResponse
sonusOcspResponseUnknown
OpenSSL sonusOpenSSLCRNGTestFailedNotification
sonusOpenSSLPairwiseConsistencyTestFailedNotification
PIPE sonusPipeTMControlModifiedNotification
sonusPipeTMControlProvisionedNotification
sonusPipeTMControlRemovedNotification
Policy Server sonusPolicyServerCallProcessTimeHighThresholdNotification
sonusPolicyServerCallProcessTimeLowThresholdNotification
sonusPolicyServerCongestionNotification
sonusPolicyServerDbConnSuccessNotification
sonusPolicyServerPipeMWIQueueLevelChanged
sonusPolicyServerScpTimeoutNotification
sonusPolicyServerTMControlAppliedNotification
SBX sonusSbxAccountingIntermediateRecordNotification
sonusSbxArsEndPointBlacklistedNotification2
sonusSbxArsEndPointBlacklistedNotification2V6
sonusSbxArsEndPointRecoveredNotification2
sonusSbxArsEndPointRecoveredNotification2V6
sonusSbxArsEndPointsRecoveredNotification2
sonusSbxCallFailureNoDspExceedThresholdNotification
sonusSbxCallProcLongDurationCallTimeout
sonusSbxCallRejectsDueToSessionLicenseClearNotification
sonusSbxDBLActionMajorNotification
sonusSbxDBLClearActionMajorNotification
sonusSbxDropSipMessageFromUnknownSourceNotification
sonusSbxDspAvailG711OnSetCrossThresholdNotification
sonusSbxDspAvailG711PacketAbateCrossThresholdNotification
sonusSbxDspFpgaVersionCheckFailureNotification
sonusSbxFailedCertificateReCheck
sonusSbxIceStunMsgValidationFailNotification
sonusSbxIceStunMsgValidationFailNotificationV6
sonusSbxIceTimerExpiryNotification
sonusSbxIceTimerExpiryNotificationV6
sonusSbxLvmLinkDetectionGroupSwitchoverNotification
sonusSbxLvmPrimaryPhyPacketPortActiveNotification
sonusSbxLvmSecondaryPhyPacketPortActiveNotification
sonusSbxNetMgmtClientInformReqQueueFlushedNotification
sonusSbxNetMgmtClientInformReqQueueFullNotification
sonusSbxNodeResourceCallTraceSignalingEnabledNotification
sonusSbxNodeResourcesCallTraceHitGAPNotification
sonusSbxNodeResourcesCallTraceHitNotification
sonusSbxNodeResourcesFeatureKeyStateChangeNotification
sonusSbxSipMultipleContactsPerAorSigPortExhaustedNotification
sonusSbxSipRegistrantPortChangeNotification
sonusSbxSipSignalingPortRangeRcbCleanpOnCrlfFailure
sonusSbxSipSignalingPortRangeRegistrationFailedNotification
sonusSbxSipSmDropLargeSipPduOverUdpNotification
sonusSbxSipSmDropLargeSipPduOverUdpNotificationV6
sonusSbxSipSmMonServerTcpConnFailureNotification
sonusSbxSipSmMonServerTcpConnFailureNotificationV6
sonusSbxSipTgRegLimitReachedNotification
sonusSbxSscsRejectIndNotification
sonusSbxSscsTransErrorNotification
sonusSbxSubscriptionToRegEventPackageFailedNotification
sonusSbxTrunkGroupAutomaticControlActive3
sonusSbxTrunkGroupManualControlActive3
sonusSbxTrunkGroupOutOfResourcesNotification2
sonusSbxTrunkGroupTrafficControlConfChanged2
SSH sonusSshHostKeyRegeneratedNotification
sonusSshHostKeyZeroizedNotification
SWe sonusSWeNewActiveProfileCommitNotification
System Security sonusSystemSecurityAccountConfigChange
sonusSystemSecurityAccountCreatedNotification
sonusSystemSecurityAccountDisabledNotification
sonusSystemSecurityAccountManuallyDeletedNotification
sonusSystemSecurityAccountNewGroupNotification
sonusSystemSecurityAccountReEnabled
sonusSystemSecurityAccountRemovedNotification
sonusSystemSecurityAccountSshKeyChange
sonusSystemSecurityLargeConsoleSessionLog
sonusSystemSecurityNewPrivateHashingKey
sonusSystemSecurityOsAccountReEnabled
Alarm Field Definitions

Dashboard - Alarms
Overview
Severity Mapping Rules
Overview
The SBC Core alarm notifications are defined by the fields: Severity, Description, Impact, Action, Clearing, Repetition, Instance Fields, and Event
Code(s).
Severity: Represents the severity level assigned by the device and is displayed in bold green font directly underneath the alarm name.
Possible severity levels are: Critical, Major, Minor, and Informational. See Severity Mapping Rules below.
Definition: Describes the purpose of the alarm.
Impact: Describes the impact to the system when the indicated failure or fault occurs.
Action: Details the action to be taken by the operator to eliminate/prevent the failure condition. When appropriate, step-by-step
procedures will be provided. Traps do not have clearing events.
Clearing: This field identifies how an alarm clears from the Fault Manager Event List. Alarm clearing is either automatic or manual.
Repetition: Identifies if an alarm is repeated for each occurrence of a particular failure relating to the same managed object instance.
When appropriate, repetition interval information is included in this field.
Instance Fields: By default, all alarms are instanced by a source host and trap type. For some alarms, an Instance ID field is included to
uniquely identify the alarms. The Instance ID is created by appending values of the instance fields to the fault instance information. In
this Guide, when instance fields exist for an alarm, the Instance Fields category in the alarm description is populated with one or more
instance fields.
Event Code(s): Identifies detailed event information contained in the alarm (event levels and classes, threshold types, clearing strings,
and so forth). This field may not always be included.
Refer to Dashboard - Alarms to learn more about viewing alarms from the EMA.
Severity Mapping Rules

The following table describes the rules used to map the SonusEventLevel to EMS display severity level. EMS severity names are color-coded to
correspond with the EMS GUI alarm color convention.
SonusEventLevel Description Action to Take EMS
Severity
critical Call impairment is either already occurring or is Requires immediate operator action. Contact Ribbon TAC; may CRITICAL
imminent require reconnecting cables, replacing components, or rebuilding
a drive.
major Future call impairment is a significant concern. Take action as soon as possible. Contact Ribbon TAC; may MAJOR
require reconnecting cables, replacing components, or rebuilding
a drive.
minor Low-impacting situations or conditions. Normally, Determine if error is routine (minor), or indicative of a significant MINOR
calls/revenue are not impacted by these low- problem.
severity events.
informational Intended to help the user identify potential future Usually requires no immediate operator action. WARNING
problems.
In this section:
Registering/Configuring Insight SNMP Network Management Station for SBC

Creating a View in EMA
Viewing Traps
Clearing Traps
SNMP Traps
The SBC, like other Ribbon devices, uses SNMP traps to notify management applications of events. SNMP traps are the messages that notify a
management client that an event has occurred on the SBC node. These traps are not displayed in EMA and can be viewed from Insight EMS or
other SNMP manager configured as a trap target. In case of error scenario, a trap is initiated at the device and forwarded to the EMS or to the
other SNMP manager for processing.
You can configure up to 32 trap targets on the SBC.
The supported configurable SNMP trap types are SNMP v1, v2, and v3.
The following command is executed in CLI to configure the SNMP traps:
% set oam snmp trapTarget myTarget ipAddress <ip address> state enabled
Registering/Configuring Insight SNMP Network Management Station for SBC

Perform the following steps to register the SBC node:
1. Log into the InsightTM Web-based Element Management System.
EMS Screen
2. The Users & Roles window appears. Select Insight Administration from the Network Mgmnt roll-up (left hand side of the Users &
Roles window).
2.
Register SBC EMS
3. The Insight Administration window appears. Select SBC 5x00 from the Register Node drop-down menu.
SBC EMS Registration
4.
4. Provide the name of the SBC in the Name field.
5. Provide the Agent Login and Agent Password (default: admin/admin).
6. Provide the information in Default IP Address for Host 1 and Host 2.
7. Click Register.
Creating a View in EMA

Perform the following steps to create a view:
1. Select Fault Manager from the Network Mgmnt roll-up (left hand side of the Users & Roles window). The Fault Manager window
appears.
View Creation
2. Select the Views tab.

3. Select All from the Resource Groups drop-down menu.
4. Select Create. The Create View option appears.
5. Provide a view name in the View Name field.
6. In the Bars option, select Create.
Device selection for view creation
7. Select the devices from the Available Devices and place them in the Selected Devices option.
8. Click OK. A view for the selected device will be created.
9. Click Save. The view is saved and displayed in the left side pane.
Saved View
Viewing Traps
Perform the following steps to view the traps:
1. Select Real-Time tab from the Fault Manager window.

2. Select All from the Resource Groups drop-down menu.
3. Select the view from the Views drop-down menu. Click Open. The view is displayed.
3.
View Traps
4. Double-click the Total Events bar. The Event Names appear for the selected device.
Viewing Traps
Clearing Traps
Perform the following steps to clear a trap:
1. Select the trap to be cleared.
Select alarm to clear
2. Select Clear from the Operations drop-down menu. The trap is cleared from the list.
Cleared alarm
SNMP Traps
The SBC supports following generic SNMP traps apart from the application specific traps or alarms:
authenticationFailure
coldStart
linkDown
linkUp
The traps are triggered under specific conditions. For detailed information about these traps, refer to the relevant Trap page using the links
provided in the table below.
Generic SNMP Trap Support
Generic SNMP Trap Conditions
authenticationFailure - MINOR When an SNMP request with mismatch of community name is received.
coldStart - INFORMATIONAL When an SNMP entity has reinitialized itself and its configuration might have been altered.
linkDown - CRITICAL When an SNMP entity detects that one of its communication links is down.
linkUp - INFORMATIONAL When an SNMP entity detects that one of its lost communication links is reinstated.
authenticationFailure - MINOR
Type: MINOR
Object ID 1.3.6.1.6.3.1.1.5.5
Description This trap signifies that the SNMPv2 entity that is acting in an agent role, has received a protocol message that is not properly
authenticated.
While all implementations of the SNMPv2 are capable of generating this trap, the snmpEnableAuthenTraps object indicates if
this trap was generated.
Note: This trap is also applicable to SNMPv3. The SNMPv3 authenticationFailure trap is triggered when an SNMP request with
a bad authentication password is received.
Repetition Yes. Repeats each time a manager sends a request to an agent with an invalid community string.
Event None
Codes
Instance None
Fields
Action Identify the offending source.
Impact A large number of failures may indicate there is a login attack on the system.
Clearing Manual
coldStart - INFORMATIONAL
Type: INFORMATIONAL
Object ID 1.3.6.1.6.3.1.1.5.1
Description This alarm is sent after a reboot, and signifies that the SNMP entity, acting in an agent role, is re-initializing itself and its
configuration may have been altered.
Probable causes:
Operator-initiated. The switch was shut off, and then turned back on.
The device momentarily lost, and then regained power.
Repetition None
Event None
Codes
Instance None
Fields
Action Check why the system restarted and that there are no intermittent power supply issues. Ensure redundant power supply is
connected to the system.
Impact Results in a temporary loss of trapping capability.
Clearing Manual
linkDown - CRITICAL
Type: CRITICAL
Obj 1.3.6.1.6.3.1.1.5.3
ect
ID
De This alarm signifies that the SNMP entity, acting in an agent role, has detected that the ifOperStatus object for one of its
scri communication links is about to enter the down state from some other state (but not from the notPresent state). This other state is
pti indicated by the included value of ifOperStatus.
on
Re None
peti
tion
Eve ifIndex—A unique value, greater than zero, for each interface. It is recommended that values are assigned contiguously starting from
nt 1. The value for each interface sub-layer must remain constant at least from one re-initialization of the entity's network management
Co system to the next re-initialization.
des
ifAdminStatus—The desired state of the interface:
up(1)
down(2)
testing(3)
The testing(3) state indicates that no operational packets can be passed. When a managed system initializes, all interfaces start
with ifAdminStatus in the down(2) state. As a result of either explicit management action or per configuration information retained
by the managed system, ifAdminStatus is then changed to either the up(1) or testing(3) states (or remains in the down(2) state).
ifOperStatus—The current operational state of the interface:
up(1)
down(2)
testing(3)
unknown(4)
dormant(5)
notPresent(6)
lowerLayerDown(7)
The testing(3) state indicates that no operational packets can be passed. If ifAdminStatus is down(2) then ifOperStatus should be down
(2).
If ifAdminStatus is changed to up(1), then ifOperStatus should either change or remain in one of the following states:
Change to up(1) state if the interface is ready to transmit and receive network traffic.
Change to dormant(5) state if the interface is waiting for external actions (such as a serial line waiting for an incoming connection).
Remain in the down(2) state if and only if there is a fault that prevents it from going to the up(1) state.
Remain in the notPresent(6) state if the interface has missing (typically, hardware) components.
Inst ifIndex
anc
e
Fiel
ds
Act
ion 1. Determine what circumstances caused the link to go down, and rectify.
2. Bring the link back up.
Imp Network connectivity is lost for the interface specified.

act
Cle Automatic; linkUp

ari
ng
linkUp - INFORMATIONAL
Type: INFORMATIONAL
Obj 1.3.6.1.6.3.1.1.5.4
ect
ID
De This alarm signifies that the SNMP entity, acting in an agent role, has detected that the ifOperStatus object for one of its
scri communication links left the down state and transitioned into some other state (but not into the notPresent state). This other state is
pti indicated by the included value of ifOperStatus.
on
Re None
peti
tion
Eve ifIndex—A unique value, greater than zero, for each interface. It is recommended that values are assigned contiguously starting from
nt 1. The value for each interface sub-layer must remain constant at least from one re-initialization of the entity's network management
Co system to the next re-initialization.
des
ifAdminStatus—The desired state of the interface:
up(1)
down(2)
testing(3)
The testing(3) state indicates that no operational packets can be passed. When a managed system initializes, all interfaces start
with ifAdminStatus in the down(2) state. As a result of either explicit management action or per configuration information retained
by the managed system, ifAdminStatus is then changed to either the up(1) or testing(3) states (or remains in the down(2) state).
ifOperStatus—The current operational state of the interface:
up(1)
down(2)
testing(3)
unknown(4)
dormant(5)
notPresent(6)
lowerLayerDown(7)
The testing(3) state indicates that no operational packets can be passed. If ifAdminStatus is down(2) then ifOperStatus should be down
(2).
If ifAdminStatus is changed to up(1), then ifOperStatus should either change or remain in one of the following states:
Change to up(1) state if the interface is ready to transmit and receive network traffic.
Change to dormant(5) state if the interface is waiting for external actions (such as a serial line waiting for an incoming connection).
Remain in the down(2) state if and only if there is a fault that prevents it from going to the up(1) state.
Remain in the notPresent(6) state if the interface has missing (typically, hardware) components.
Inst ifIndex
anc
e
Fiel
ds
Act None required.

ion
Imp Network connectivity is restored for the interface specified.

act
Cle Automatic; clears in 2 minutes.

ari
ng
Alarms Management

Types of Alarms
Major Alarms List
Viewing the Current Alarms
Dashboard - Alarms
Clearing Alarms
Viewing the Cleared Alarms
Types of Alarms
EMA displays the following alarm tables:
Current
Cleared
The cleared alarm table displays all the alarms of type "clear" or "manual clear" from the historical alarms table. In addition, EMA also includes
extended history by including clearing traps received from the platform.
Each time an alarm is cleared, a trap is also sent. As the EMA stores that trap in its own database table, it effectively allows an
extended alarm history.
Alarm management also contains two types of alarms based on the functionality:
SET — A SET alarm has one or more clear alarms associated with it. A set alarms enables the alarm LED based on priority.
CLEAR — A clear alarm disabled the alarm led when all alarms of that level are cleared. There are two types of clearing actions.
Manual CLEAR. A manual clear alarm is a set alarm without a clearing alarm. An operator must manually remove the alarm
from the alarm screen using CLI/EMA.
Automatic CLEAR. An automatic clearing alarm associates a clearing alarm to one or more set alarms, and is cleared without
any human interference. For example, sonusCpNtpUpNotification clears both sonusCpNtpDownNotification and son
usCpNtpAllServersOutOfSyncNotification.
All alarm types can be manually cleared.
Viewing the Current Alarms

To view the Current Alarms, in EMA, navigate to Monitoring > Dashboard > Alarms > Current Alarms. The Current Alarms window is
displayed.
To view the Cleared Alarms, in EMA, navigate to Monitoring > Dashboard > Alarms > Cleared Alarms. The Cleared Alarms window is
displayed.
For more information on viewing alarms in the EMA, refer to the section Dashboard - Alarms.
Clearing Alarms
To clear a raise or current alarm, navigate to Monitoring > Dashboard > Alarms > Current Alarms.
1. Select the alarm by clicking the radio button from the table you want to clear.
2. Click Edit Alarm to edit the selected alarm.
3. Select the Cleared radio button.

4. Click the Save icon. The alarm will be cleared from the Current Alarms table.
For more information, refer to Dashboard - Alarms.
Viewing the Cleared Alarms

To view the cleared alarms, navigate to Monitoring > Dashboard > Alarms > Cleared Alarms.
For more information on cleared alarms, refer to Dashboard - Alarms.

A consolidated list of SBC Core Critical alarms is provided below. For complete alarm details, refer to SBC Alarm Details.
ALARM CATEGORY ALARMS

1. sonusSbxCallAccountingOutOfServiceNotification - CRITICAL
CP System Alarms
1. sonusCpSystemFaultyHardDiskNotify - CRITICAL
2. sonusCpSystemReadonlyFileSystemNotify - CRITICAL
Database Alarms
1. sonusDatabaseConfigPolicyDataOutOfSyncNotification - CRITICAL
2. sonusDatabasePolicyDataOutOfSyncNotification - CRITICAL

1. sonusSbxDialogTransparencyMisConfiguredNotification - CRITICAL

1. sonusSbxDnsServerBlacklistedNotification - CRITICAL
2. sonusSbxDnsServerEdnsFailureNotification - CRITICAL
3. sonusSbxDnsServerRecoveredNotification - CRITICAL

1. sonusSbxDspCardOrDeviceFailureNotification - CRITICAL
2. sonusSbxDspCardOrDeviceFailureNotificationClear - CRITICAL
License Alarms
1. sonusCpLicenseBundleExpiredNotification - CRITICAL
2. sonusCpLicenseHostSerialUnavailable - CRITICAL
3. sonusCpLicenseIntegrityViolationNotification - CRITICAL
4. sonusCpLicensePeerSerialMismatch - CRITICAL
5. sonusCpNiceRecLicenseExpireWarningNotification - CRITICAL
6. sonusCpLicenseSerialMismatch - CRITICAL
7. sonusSbxCallRejectsDueToSlbSessionLicenseNotification-CRITICAL
8. sonusSbxFeatureLicenseUnavailable-CRITICAL
Licensing Alarms for SBC SWe Deployments

1. sonusCpLicenseExpireWarningNotification - CRITICAL
2. sonusCpLicenseManagerRegistrationPeriodExpired - CRITICAL
3. sonusSbxCallRejectsDueToSessionLicenseClearNotification - CRITICAL
4. sonusSbxCallRejectsDueToSessionLicenseNotification - CRITICAL
5. sonusSbxLicensedServiceDeniedDueToLicenseLimit - CRITICAL
6. sonusSbxMandatoryLicenseUnavailable - CRITICAL
7. sonusSbxMaximumLicenseCountThresholdExceeded - CRITICAL
8. sonusSbxMinimumLicenseCountThresholdNotReached - CRITICAL
9. sonusCpLicenseManagerUnsanctionedMannerSoon - CRITICAL
Media Port Alarms

1. sonusCpSystemProductCapabalityMismatch - CRITICAL
2. sonusSbxNrsMediaPortDownNoLicenseClearedNotification - CRITICAL
3. sonusSbxNrsMediaPortDownNoLicenseNotification - CRITICAL
4. sonusSbxNrsMediaPortInvalidSfpClearedNotification - CRITICAL
5. sonusSbxNrsMediaPortInvalidSfpNotification - CRITICAL
1. sonusSbxLbsLocalNodeIsLeaderLackOfCommuncationNotification- CRITICAL
2. sonusSbxLbsLocalNodeIsLeaderLackOfCommuncationNotificationV6- CRITICAL
Node Alarms
1. sonusCpNodeBondingDeviceDownNotification - CRITICAL
Platform Alarms
1. sonusCpEventLogDirectoryCreateErrorNotification - CRITICAL
2. sonusCpRedundGroupNoRedundancyNotification - CRITICAL
3. sonusCpRedundGroupSwitchOverNotification - CRITICAL
4. sonusCpSystemApacheFailedNotification - CRITICAL
5. sonusOpenSSLCRNGTestFailedNotification - CRITICAL
6. sonusOpenSSLPairwiseConsistencyTestFailedNotification - CRITICAL
7. sonusSoftwareLoadTestFailedNotification - CRITICAL
8. sonusCpSystemLocalDiskSpaceCriticalNotification - CRITICAL
9. sonusCpSystemLocalDiskSpaceFaultNotification - CRITICAL
10. sonusCpSystemServiceRestartNotification - CRITICAL

1. sonusSbxSscsOutOfServiceNotification - CRITICAL
Major Alarms List
A consolidated list of SBC Core Major alarms is provided below. For complete alarm details, refer to SBC Alarm Details.
ALARM CATEGORY ALARMS

1. sonusSbxCallProcAnswerSupervisionTimeout - MAJOR
CP CDR Server Alarms

1. sonusCpCdrServerNewXferPendingNotification - MAJOR
2. sonusCpCdrServerSwitchoverNotification - MAJOR
3. sonusCpCdrServerTransferFailNotification - MAJOR
CP Event Log Alarms

1. sonusCpEventLogFileSecFilterLevelChngNotification - MAJOR
2. sonusCpEventLogFileDebugLevelInfoNotification - MAJOR
CP Radius Alarms
1. sonusCpRadiusServerFailedNotification - MAJOR
2. sonusCpRadiusServerPacketsFlushedNotification - MAJOR
CP System Alarms
1. sonusCpSystemCEBootActiveNotification - MAJOR
2. sonusCpSystemCEBootDeactiveNotification - MAJOR
3. sonusCpSystemFaultAvalancheControlPacketDroppedNotify - MAJOR
4. sonusCpSystemNPTempFailureNotification - MAJOR
5. sonusCpSystemNPTempNormalNotification - MAJOR
6. sonusCpSystemNPTempWarningNotification - MAJOR
7. sonusCpSystemRsyslogRemoteServerConnectionIssue - MAJOR
8. sonusCpSystemRsyslogRemoteServerConnectionRecovered - MAJOR
9. sonusCpSystemServerDrbdReformatBackupNotify - MAJOR
10. sonusCpSystemServerDrbdReformatCompletedNotify - MAJOR
11. sonusCpSystemServerDrbdReformatErrorNotify - MAJOR
12. sonusCpSystemServerDrbdReformatStartNotify - MAJOR
13. sonusCpSystemServerDrbdReformatSwitchoverNotify - MAJOR
14. sonusCpSystemSoftBootActiveNotification - MAJOR
15. sonusCpSystemSoftBootNotification - MAJOR
Diameter Alarms
1. sonusSbxDiamPeerConnectionDown - MAJOR
2. sonusSbxDiamPeerConnectionUp - MAJOR
1. sonusSbxCcsClusterDownNotification - MAJOR
2. sonusSbxCcsClusterUpNotification - MAJOR
3. sonusSbxDsbcClusterAllSeedNodesUnreachable - MAJOR
4. sonusSbxDsbcClusterFqdnResolutionFailure - MAJOR
5. sonusSbxDsbcClusterFqdnResolutionSuccess - MAJOR
6. sonusSbxDsbcClusterLeaderDiscoveryInProgress - MAJOR
7. sonusSbxDsbcClusterLeaderDiscoveryInProgressV6 - MAJOR
8. sonusSbxDsbcClusterLeaderRetrievalCompleted - MAJOR
9. sonusSbxDsbcClusterLeaderRetrievalCompletedV6 - MAJOR
10. sonusSbxDsbcControlChanCloseNotification - MAJOR
11. sonusSbxDsbcControlChanCloseNotificationV6 - MAJOR
12. sonusSbxDsbcControlChanOpenAttemptNotification - MAJOR
13. sonusSbxDsbcControlChanOpenAttemptNotificationV6 - MAJOR
14. sonusSbxDsbcControlChanOpenNotification - MAJOR
15. sonusSbxDsbcControlChanOpenNotificationV6 - MAJOR
16. sonusSbxDsbcControlChanRetryTimerExpiredNotification - MAJOR
17. sonusSbxDsbcControlChanRetryTimerExpiredNotificationV6 - MAJOR
18. sonusSbxDsbcFaultCallsReleasedClear - MAJOR
19. sonusSbxDsbcFaultCallsReleasedClearV6 - MAJOR
20. sonusSbxDsbcFaultCallsReleased - MAJOR
21. sonusSbxDsbcFaultCallsReleasedV6 - MAJOR
22. sonusSbxDsbcNodeAllocationFailureClear- MAJOR
23. sonusSbxDsbcNodeAllocationFailureClearV6 - MAJOR
24. sonusSbxDsbcNodeAllocationFailure - MAJOR
25. sonusSbxDsbcNodeAllocationFailureV6 - MAJOR
26. sonusSbxDsbcNodeCongestedClear - MAJOR
27. sonusSbxDsbcNodeCongestedClearV6 - MAJOR
28. sonusSbxDsbcNodeCongested - MAJOR
29. sonusSbxDsbcNodeCongestedV6 - MAJOR

1. sonusSbxCallFailureNoDspExceedThresholdNotification - MAJOR
2. sonusSbxDspAvailG711OnSetCrossThresholdNotification - MAJOR
3. sonusSbxDspAvailG711PacketAbateCrossThresholdNotification - MAJOR
5. sonusSbxDspAvailG726AbateCrossThresholdNotification - MAJOR
7. sonusSbxDspAvailG729AbateCrossThresholdNotification - MAJOR
8. sonusSbxDspFpgaVersionCheckFailureNotification - MAJOR
9. sonusSbxGpuCodecThresholdNotificationClear - MAJOR
10. sonusSbxGpuCodecThresholdNotification - MAJOR
11. sonusSbxSingleDspReloadAndCoreDumpNotification - MAJOR
1. sonusSbxDBLActionEndpointInfoNotification - MAJOR
2. sonusSbxDBLActionMajorNotification - MAJOR
3. sonusSbxDBLClearActionEndpointInfoNotification - MAJOR
4. sonusSbxDBLClearActionMajorNotification - MAJOR

1. sonusSbxGwSigChanCloseNotification - MAJOR
2. sonusSbxGwSigChanCloseNotificationV6 - MAJOR
3. sonusSbxGwSigChanOpenNotification - MAJOR
4. sonusSbxGwSigChanOpenNotificationV6 - MAJOR
5. sonusSbxGwSigTrunkGroupOutOfServiceNotification - MAJOR
GETS and WPS Alarms

1. sonusHpcCallNoLicenseNotification - MAJOR
H248 Alarms
1. sonusH248SigPortCloseNotification - MAJOR
2. sonusH248SigPortOpenNotification - MAJOR
3. sonusH248ScNotificationClear - MAJOR
4. sonusH248VMGtermNoRTPRcvdThresholdExceeded - MAJOR
5. sonusH248ClearVMGtermNoRTPRcvdThresholdExceeded - MAJOR
IP Interface Alarms
1. sonusSbxLvmLinkDetectionGroupFailedNotification - MAJOR
2. sonusSbxLvmLinkDetectionGroupRestoredNotification - MAJOR
3. sonusSbxLvmLinkDetectionGroupSwitchoverNotification - MAJOR
4. sonusSbxNrsIpInterfaceAdminDisabledNotification - MAJOR
5. sonusSbxNrsIpInterfaceAdminEnabledNotification - MAJOR
6. sonusSbxNrsIpInterfaceAdminISNotification - MAJOR
7. sonusSbxNrsIpInterfaceAdminOOSNotification - MAJOR
8. sonusSbxNrsIpInterfaceISNotification - MAJOR
9. sonusSbxNrsIpInterfaceLinkMonitorDownNotification - MAJOR
10. sonusSbxNrsIpInterfaceLinkMonitorDownNotificationV6 - MAJOR
11. sonusSbxNrsIpInterfaceLinkMonitorUpNotification - MAJOR
12. sonusSbxNrsIpInterfaceLinkMonitorUpNotificationV6 - MAJOR
13. sonusSbxNrsIpInterfaceOOSNotification - MAJOR
14. sonusSbxNrsLogMgmtIpInterfaceAdminDisabledNotification - MAJOR
15. sonusSbxNrsLogMgmtIpInterfaceAdminEnabledNotification - MAJOR
16. sonusSbxNrsMgmtIpInterfaceAdminDisabledNotification - MAJOR
17. sonusSbxNrsMgmtIpInterfaceAdminEnabledNotification - MAJOR
18. sonusSbxNrsMgmtPortDownNotification - MAJOR
19. sonusSbxNrsPacketPortDownNotification - MAJOR
20. sonusSbxNrsPacketPortUpNotification - MAJOR
JSRC Alarms
1. sonusJsrcServerStateDownNotification - MAJOR
2. sonusJsrcServerStateUpNotification - MAJOR

1. sonusSbxImMediationServerTcpLinkDown - MAJOR
2. sonusSbxImMediationServerTcpLinkUp - MAJOR
3. sonusSbxImPriOperStateChange - MAJOR
4. sonusSbxImSecOperStateChange - MAJOR
5. sonusSbxImMediationServerX2MsgBufferFull - MAJOR
6. sonusSbxImMediationServerX2MsgBufferAvailable - MAJOR
7. sonusLiCryptoFailureNotification - MAJOR
8. sonusLiCryptoSuccessNotification - MAJOR
License Alarms
1. sonusCpLicenseBundleExpireWarningNotification - MAJOR
2. sonusCpLicenseBundleInvalidUsageCount - MAJOR
3. sonusCpLicenseBundleRenewedNotification - MAJOR
4. sonusCpNiceRecLicenseExpireSoonWarningNotification - MAJOR
5. sonusSbxCallRejectsDueToSessionLicenseClearNotification - MAJOR
6. sonusSbxLicensedOodRateLimitClearNotification - MAJOR
7. sonusSbxLicensedOodRateLimitReachedNotification - MAJOR
8. sonusCpLicenseManagerLicenseServersConfigured - MAJOR
9. sonusSipRegThresholdReachedNotification - MAJOR
10. sonusSipRegThresholdClearedNotification - MAJOR

1. sonusCpLicenseExpireSoonWarningNotification - MAJOR
2. sonusCpLicenseManagerCouldNotConnect - MAJOR
3. sonusCpLicenseManagerNoEmsNodeIdConfigured - MAJOR
4. sonusCpLicenseManagerNoLicenseServersConfigured - MAJOR
5. sonusCpLicenseManagerNoLicenseUsageDetected - MAJOR
6. sonusCpLicenseManagerRegistrationFailed - MAJOR
7. sonusInvalidFingerPrintNotification - MAJOR
8. sonusSbxLicensedVdspThresholdReachedNotification - MAJOR
9. sonusSbxServiceLicenseUnavailable - MAJOR

1. sonusSbxNodeMachineCongestionNotification - MAJOR
2. sonusSbxNodeMemoryCongestionNotification - MAJOR

1. sonusSbxMtrmPortUnAvailNotification - MAJOR
1. sonusSbxMediaOverFlowPacketsNotification - MAJOR
Media Port Alarms
2. sonusSbxMediaOverFlowPacketsCleared - MAJOR
3. sonusNrsNifHighWatermarkNotification - MAJOR
4. sonusPacketPortBWusageThresholdExceeded - MAJOR
5. sonusClearPacketPortclearThresholdExceeded - MAJOR

1. sonusSbxLvmPhyPacketPortDownNotification - MAJOR
2. sonusSbxLvmPhyPacketPortUpNotification - MAJOR
3. sonusSbxLvmPrimaryPhyPacketPortActiveNotification - MAJOR
4. sonusSbxLvmSecondaryPhyPacketPortActiveNotification - MAJOR
Monitoring Alarms
1. sonusSbxSipSmMonServerTcpConnFailureNotification - MAJOR
2. sonusSbxSipSmMonServerTcpConnFailureNotificationV6 - MAJOR

1. sonusSbxNetMgmtClientInformReqQueueFlushedNotification - MAJOR
2. sonusSbxNetMgmtClientInformReqQueueFullNotification - MAJOR
3. sonusSbxSipSmDropLargeSipPduOverUdpNotification - MAJOR
4. sonusSbxSipSmDropLargeSipPduOverUdpNotificationV6 - MAJOR
Node Alarms
1. sonusCpNodeBondingDeviceUpNotification - MAJOR
2. sonusCpNodeHaPortDownNewNotification - MAJOR
3. sonusCpNodeHaPortUpNotification - MAJOR
4. sonusCpNodeStandbyDisabled - MAJOR
5. sonusCpNodeStandbyEnabled - MAJOR
6. sonusSbxNodeInServiceNotification - MAJOR
7. sonusSbxNodeOutOfServiceNotification - MAJOR
8. sonusSbxNodePolicerMajorAlarmNotification - MAJOR
1. sonusSbxNodeResEmerCallNoRouteNotification - MAJOR
2. sonusSbxNodeResourcesCallAdmissionEnabledNotification - MAJOR
3. sonusSbxNodeResourcesCallAdmissionSuspendedNotification - MAJOR
4. sonusSbxNodeResourcesFeatureKeyStateChangeNotification - MAJOR
5. sonusSbxNodeResourcesMaxIpCallLimitClearNotification - MAJOR
6. sonusSbxNodeResourcesMaxIpCallLimitSetNotification - MAJOR
7. sonusSbxNodeResourcesMaxSysCallLimitClearNotification - MAJOR
8. sonusSbxNodeResourcesMaxSysCallLimitSetNotification - MAJOR
9. sonusSbxNodeResourcesMaxTcpMediaSessLimitClearNotification - MAJOR
10. sonusSbxNodeResourcesMaxTcpMediaSessLimitSetNotification - MAJOR
11. sonusSbxNodeResourcesMediaPortRangeExhaustionClearedNotfication - MAJOR
12. sonusSbxNodeResourcesMediaPortRangeExhaustionNotification - MAJOR
13. sonusSbxNodeResourcesNoPacketsReceivedNotification - MAJOR
14. sonusSbxNodeResourcesPacketLossThresholdExceededNotification - MAJOR
15. sonusSbxNodeResourcesSysACLLimitNotification - MAJOR
16. sonusSbxNodeResourcesTcpPortRangeExhaustionClearedNotification - MAJOR
17. sonusSbxNodeResourcesTcpPortRangeExhaustionNotification - MAJOR
OAM Node Alarms

1. sonusSbxManagedNodeAbleToReceiveConfigUpdates - MAJOR
2. sonusSbxManagedNodeConfigChangeListApplyFailed - MAJOR
3. sonusSbxManagedNodeConfigChangeListApplySucceeded - MAJOR
4. sonusSbxManagedNodeUnableToReceiveConfigUpdates - MAJOR
Path Check Alarms

1. sonusSbxPathCheckFqdnPeerDownNotification2 - MINOR
2. sonusSbxPathCheckFqdnPeerIpEndpointDownNotification2 - MINOR
3. sonusSbxPathCheckFqdnPeerIpEndpointUpNotification2 - MINOR
4. sonusSbxPathCheckFqdnPeerUpNotification2 - MINOR
5. sonusSbxPathCheckLocalAdminStateDownNotification2 - MAJOR
6. sonusSbxPathCheckLocalAdminStateDownNotification2V6 - MAJOR
7. sonusSbxPathCheckLocalAdminStateUpNotification2 - MAJOR
8. sonusSbxPathCheckLocalAdminStateUpNotification2V6 - MAJOR
9. sonusSbxPathCheckPingStateDownNotification2 - MAJOR
10. sonusSbxPathCheckPingStateDownNotification2V6 - MAJOR
11. sonusSbxPathCheckPingStateUpNotification2 - MAJOR
12. sonusSbxPathCheckPingStateUpNotification2V6 - MAJOR
13. sonusSbxPathCheckRemoteAdminStateDownNotification2 - MAJOR
14. sonusSbxPathCheckRemoteAdminStateDownNotification2V6 - MAJOR
15. sonusSbxPathCheckRemoteAdminStateUpNotification2 - MAJOR
16. sonusSbxPathCheckRemoteAdminStateUpNotification2V6 - MAJOR
Platform Alarms
1. sonusCdbEncryptionKeyRegeneratedNotification - MAJOR
2. sonusCdbEncryptionKeyZeroizedNotification - MAJOR
3. sonusConnexIpSystemCECardInsertedNotification - MAJOR
4. sonusConnexIpSystemCECardRemovedNotification - MAJOR
5. sonusConnexIpSystemCEFanAbsentNotification - MAJOR
6. sonusConnexIpSystemCEFanFailureNotification - MAJOR
7. sonusConnexIpSystemCEFanNormalNotification - MAJOR
8. sonusConnexIpSystemCEFanPresentNotification - MAJOR
9. sonusConnexIpSystemCEMultipleFanAbsentNotification - MAJOR
10. sonusConnexIpSystemCEMultipleFanPresentNotification - MAJOR
11. sonusConnexIpSystemCEPowerSupplyFailureNotification - MAJOR
12. sonusConnexIpSystemCEPowerSupplyNormalNotification - MAJOR
13. sonusConnexIpSystemCEPowerSupplyUnitInsertedNotification - MAJOR
14. sonusConnexIpSystemCEPowerSupplyUnitRemovedNotification - MAJOR
15. sonusConnexIpSystemCESlotDisabledNotification - MAJOR
16. sonusConnexIpSystemCESlotDryupNotification - MAJOR
17. sonusConnexIpSystemCESlotEnabledNotification - MAJOR
18. sonusConnexIpSystemCESlotFailedNotification - MAJOR
19. sonusConnexIpSystemCESlotLockClearNotification - MAJOR
20. sonusConnexIpSystemCESlotLockNotification - MAJOR
21. sonusConnexIpSystemCESlotMismatchClearNotification - MAJOR
22. sonusConnexIpSystemCESlotMismatchNotification - MAJOR
23. sonusCpConfigCommitFailNotification - MAJOR
24. sonusCpConfigCommitSucceedNotification - MAJOR
25. sonusCpConfiguredExceedSystemLimit - MAJOR
26. sonusCpEventLogFileCountNotification - MAJOR
27. sonusCpEventLogFileWriteErrorNotification - MAJOR
28. sonusCpEventLogInfoLevelLoggingDisabledNotfication - MAJOR
29. sonusCpEventLogInfoLevelLoggingReenabledNotfication - MAJOR
30. sonusCpEventLogRolloverFastNotification - MAJOR
31. sonusCpEventMgrAlarmManualClear - MAJOR
32. sonusCpNtpAllServersOutOfSyncNotification - MAJOR
33. sonusCpNtpDownNotification - MAJOR
34. sonusCpRedundGroupFullRedundancyNotification - MAJOR
35. sonusCpSoftwareUpgradeCommittedNotification - MAJOR
36. sonusCpSoftwareUpgradeInitiatedNotification - MAJOR
37. sonusCpSoftwareUpgradeRevertNotification - MAJOR
38. sonusCpSoftwareUpgradeSucceededNotification - MAJOR
39. sonusCpSoftwareUpgradeTerminatedNotification - MAJOR
40. sonusCpSystemBootActiveNotification - MAJOR
41. sonusCpSystemBootNotification - MAJOR
42. sonusCpSystemCEBootNotification - MAJOR
43. sonusCpSystemCEOperationalNotification - MAJOR
44. sonusCpSystemCESoftBootActiveNotification - MAJOR
45. sonusCpSystemCESoftBootNotification - MAJOR
46. sonusCpSystemCETempFailureNotification - MAJOR
47. sonusCpSystemCETempNormalNotification - MAJOR
48. sonusCpSystemCETempWarningNotification - MAJOR
49. sonusCpSystemCoredumpSpaceWarningNotification - MAJOR
50. sonusCpSystemLocalDiskBadVolumeNotification - MAJOR
51. sonusCpSystemLocalDiskHealthErrorClearNotification - MAJOR
52. sonusCpSystemLocalDiskHealthErrorNotification - MAJOR
53. sonusCpSystemLocalDiskLifeAttribErrorClearNotification - MAJOR
54. sonusCpSystemLocalDiskLifeAttribErrorNotification - MAJOR
55. sonusCpSystemLocalDiskMisMatchNotification - MAJOR
56. sonusCpSystemLocalDiskSpaceClearAlarmsNotification - MAJOR
57. sonusCpSystemLocalDiskSpaceOkNotification - MAJOR
58. sonusCpSystemLocalDiskSpaceReadOnlyNotification - MAJOR
59. sonusCpSystemLocalDiskSpaceWarningNotification - MAJOR
60. sonusCpSystemLocalDiskTooManyFilesNotification - MAJOR
61. sonusCpSystemProcessCoredumpGeneratedNotification - MAJOR
62. sonusCpSystemRestoreConfigNotification - MAJOR
63. sonusSbxMediaProfileDspReconfigurationNotificationClear - MAJOR
64. sonusSbxMediaProfileDspReconfigurationNotification - MAJOR
65. sonusSbxPadThresholdNotificationClear - MAJOR
66. sonusSbxPadThresholdNotification - MAJOR
67. sonusSshHostKeyRegeneratedNotification - MAJOR
68. sonusSshHostKeyZeroizedNotification - MAJOR
69. sonusSystemNodeResourceClearCongestionWarningNotification - MAJOR
70. sonusSystemNodeResourceCongestionWarningNotification - MAJOR
71. sonusSystemSecurityEthernetErrorNotification - MAJOR
72. sonusSystemSecurityMediaErrorNotification - MAJOR
73. sonusSystemSecurityReportNotification - MAJOR
74. sonusIPv6DuplicateManualReviewRebootingNotification - MAJOR
75. sonusIPv6DuplicateManualReviewNoRebootNotification - MAJOR
76. sonusSbxLvmPrgLinkFailureToggleNotification - MAJOR
77. sonusSbxLvmPrgLinkFailureToggleClearedNotification - MAJOR
78. sonusSbxLvmPrgSwitchoverToRecoverLinksNotification - MAJOR
1. sonusPolicyServerCallProcessTimeHighThresholdNotification - MAJOR
2. sonusPolicyServerCallProcessTimeLowThresholdNotification - MAJOR
3. sonusPolicyServerCongestionNotification - MAJOR
4. sonusPolicyServerDbConnSuccessNotification - MAJOR
5. sonusPolicyServerDbOperationFailureNotification - MAJOR
6. sonusPolicyServerExternalErrorHighThresholdNotification - MAJOR
7. sonusPolicyServerInternalErrorHighThresholdNotification - MAJOR
8. sonusPolicyServerLwresdCommunicationDownNotification - MAJOR
9. sonusPolicyServerLwresdCommunicationUpNotification - MAJOR
10. sonusPolicyServerNoRouteFoundNotification - MAJOR
11. sonusPolicyServerPipeCommunicationDownNotification - MAJOR
12. sonusPolicyServerPipeCommunicationUpNotification - MAJOR
13. sonusPolicyServerLWRESDENUMServerBlacklistedNotification - MAJOR
14. sonusPolicyServerPipeIOErrorNotification - MAJOR
15. sonusPolicyServerPipeMWIQueueLevelChanged - MAJOR
16. sonusPolicyServerPipeRegistrationFailureNotification - MAJOR
17. sonusPolicyServerPipeRegistrationSuccessNotification - MAJOR
18. sonusPolicyServerRegisterNotification - MAJOR
19. sonusPolicyServerScpCommunicationDownNotification - MAJOR
20. sonusPolicyServerScpCommunicationUpNotification - MAJOR
21. sonusPolicyServerScpTimeoutNotification - MAJOR
22. sonusPolicyServerSqlErrorHighThresholdNotification - MAJOR
23. sonusPolicyServerUnregisterNotification - MAJOR
24. sonusPostgresTransitionFailureNotification - MAJOR

1. sonusSWeNewActiveProfileCommitNotification - MAJOR
Security Alarms
1. sonusSbxFailedCertificateReCheck - MAJOR
2. sonusSystemSecurityAccountDisabledNotification - MAJOR
3. sonusSystemSecurityAccountRemovedNotification - MAJOR
4. sonusSystemSecurityAccountLocked - MAJOR
5. sonusSystemSecurityOsAccountLocked - MAJOR
6. sonusSystemSecurityLargeConsoleSessionLog - MAJOR
7. sonusSystemSecurityNewPrivateHashingKey - MAJOR
8. sonusSbxCertificateExpireSoonWarningNotification - MAJOR
9. sonusSbxLogFileEncryptionSettingsChangedNotification - MAJOR
10. sonusMalformedMessagesDroppedNotification - MAJOR

1. sonusEmergencyMessageRejectNotification - MAJOR
1. sonusSbxPathCheckFqdnPeerDownNotification2 - MINOR
2. sonusSbxPathCheckFqdnPeerIpEndpointDownNotification2 - MINOR
3. sonusSbxPathCheckFqdnPeerIpEndpointUpNotification2 - MINOR
4. sonusSbxPathCheckFqdnPeerUpNotification2 - MINOR
5. sonusSbxSipCallSigPortCloseNotification - MAJOR
6. sonusSbxSipCallSigPortCloseNotificationV6 - MAJOR
7. sonusSbxSipCallSigPortOpenNotification - MAJOR
8. sonusSbxSipCallSigPortOpenNotificationV6 - MAJOR
9. sonusSbxSipRegistrantPortChangeNotification - MAJOR
10. sonusSbxSipTgRegLimitReachedNotification - MAJOR
11. sonusSbxSipTrunkGroupOutOfServiceNotification - MAJOR

1. sonusSbxSscsInServiceNotification - MAJOR
2. sonusSbxSscsRouteFailureNotification - MAJOR
3. sonusSbxSscsRouteFailureWithoutGapNotification2 - MAJOR

1. sonusSbxIceStunMsgValidationFailNotification - MAJOR
2. sonusSbxIceStunMsgValidationFailNotificationV6 - MAJOR
3. sonusSbxIceTimerExpiryNotification - MAJOR
4. sonusSbxIceTimerExpiryNotificationV6 - MAJOR

1. sonusSbxSurrRegAuthenticationClearNotification - MAJOR
2. sonusSbxSurrRegAuthenticationFailedNotification - MAJOR
3. sonusSbxSurrRegRegistrationFailedNotification - MAJOR
4. sonusSbxSurrRegRegistrationFailedNotificationV6 - MAJOR
5. sonusSbxSurrRegRegistrationSuccessNotification - MAJOR
6. sonusSbxSurrRegRegistrationSuccessNotificationV6 - MAJOR
Trunk Group Alarms

1. sonusSbxCallRejectedDueToNonRegCacMaxLimitReachedNotification - MAJOR
2. sonusSbxH323TrunkGroupOutOfServiceNotification - MAJOR
3. sonusSbxIpPeerKpiCriticalThresholdClearedNotification - MAJOR
4. sonusSbxIpPeerKpiCriticalThresholdNotification - MAJOR
5. sonusSbxTgAuthenticationClearNotification - MAJOR
6. sonusSbxTgAuthenticationFailedNotification - MAJOR
7. sonusSbxTrunkGroupKpiCriticalThresholdClearedNotification - MAJOR
8. sonusSbxTrunkGroupKpiCriticalThresholdNotification - MAJOR
9. sonusSbxTrunkGroupKpiMajorThresholdNotification - MAJOR
VNFM Alarms
1. sonusSbxSlbConnectionDownNotificationV6 - MAJOR
2. sonusSbxSlbConnectionUpNotificationV6 - MAJOR
3. sonusSbxSlbConnectionDownNotification- MAJOR
4. sonusSbxSlbConnectionUpNotification - MAJOR
5. sonusSlbSbcsUnreachableNotification- MAJOR
6. sonusSlbSbcConnectionDownNotification- MAJOR
7. sonusSlbSbcConnectionUpNotification- MAJOR
8. sonusSlbSbcRegistrationNotification - MAJOR
9. sonusSbxSlbGlobalUtilizationThresholdReachedNotification - MAJOR
10. sonusSbxSlbGlobalUtilizationThresholdClearNotification - MAJOR
SBC Alarm Details
SBC Core alarms are detailed in this section, to include alarm descriptions, impact to the system, actions to resolve the alarms, event codes and
alarm clearing behavior.

Database Alarms
Diameter Alarms
GETS and WPS Alarms
H248 Alarms
IP Interface Alarms
JSRC Alarms
License Alarms
Media Port Alarms
Monitoring Alarms
Node Alarms
OAM Node Alarms
Path Check Alarms
Platform Alarms
Resource Alarms
Security Alarms
Trunk Group Alarms
VNFM Alarms
GPU Alarms
Info
Refer to for a consolidated listing of SBC Critical and Major alarms.
This section contains the following SIP Accounting Services alarms.
sonusSbxAccountingIntermediateRecordNotification - INFORMATIONAL
sonusSbxCallAccountingInServiceNotification - MINOR
sonusSbxCallAccountingOutOfServiceNotification - CRITICAL
sonusSbxAccountingIntermediateRecordNotification -
INFORMATIONAL
Type: INFORMATIONAL
Obje 1.3.6.1.4.1.2879.2.10.1.1.6.0.3
ct ID
Desc This alarm is generated when an intermediate accounting record is generated.

ription
Repe None
tition
Even
t sonusAcctGcid— GCID associated with the call which generated the trap. Corresponds to INTERMEDIATE accounting record,
Codes field 65 (Global Call ID).
sonusAcctOrigTrunkgroupType—This value represents the originating trunk type as specified by the user. This field is
associated with the corresponding field of the Trunk Group screen on the SBC. It corresponds to the INTERMEDIATE
accounting record, field 135 (Originating Trunk Type).
sonusAcctEgressCep—Ingress Circuit End Point. If ingress is PSTN, then the CEP string contains the following: <Shelf>:
<Slot>:<Port>:<Ds0>:<Cic>:<LPC>:<RPC> If ingress is IP, then the CEP string contains the following:
<Local IP Address>:<Port>/<Remote IP Address>:<Port> Corresponds to INTERMEDIATE accounting record, fields 32 &
33.
sonusAcctCallingPartyNumber—Calling Party Number associated with the call which generated the trap. Corresponds to
INTERMEDIATE accounting record, field 17 (Calling Number).
Insta sonusAcctCalledPartyNumber— Called Party Number associated with the call which generated the trap. Corresponds to
nce INTERMEDIATE accounting record, field 18 (Called Number)
Fields
Action None
Impa None
ct
Clear Manual
ing
sonusSbxCallAccountingInServiceNotification - MINOR
Type: MINOR
O 1.3.6.1.4.1.2879.2.10.1.1.6.0.1
bj
ec
t
ID
De This alarm is generated when a change is made to the Accounting Configuration for the Node, and the resultant configuration state of
sc accounting for the node is that it is "enabled/in-service".
rip
tion
Re None
pe
titi
on
Ev sonusAcctGenerationMode—Configures the accounting generation mode for the node. Values include:
en
t origination(1)
Co destination(2)
des allcalls(3)
none(4)
sonusAcctLogDestination—The accounting log destination is no longer configurable through this MIB object. This field is replaced by
sonusLogInterfaceAdmnLogDestination in V6.2. Values include:
nfs(1)
streaming(2)
sonusAcctIntAcctState—Configures whether Intermediate Accounting is Enabled or Disabled for the Node. Values include:
disabled(1) <Default>
enabled(2)
sonusAcctIntAcctInterval—Configures the Intermediate Accounting Interval in seconds (range = 5 to 86400). Note: this object is only
applicable when "sonusAcctIntAcctMode" is set to "interval(1)." Default value is "60."
sonusAcctIntAcctMode—Configures the intermediate record generation mode for the node. In INTERVAL(1) mode, intermediate
records are generated a periodic intervals following call establishment. This interval is defined by "sonusAcctIntAcctInterval." In
TELCORDIA(2) mode, intermediate records are generated once per day for calls whose duration exceeds 24 hours. The scheduled
generated time is defined by "sonusAcctTelcordiaGenTime." Values include:
interval(1) <Default>
telcordia(2)
For example, 23:59:59:9 GMT is represented as 0x173B3B09. This object is applicable when "sonusAcctlntAcctMode" is set to telcordia
(2).
sonusAcctIntLongDurGenTime—Octet string that identifies the GMT time to generate Telcordia Long Duration accounting records. At
the scheduled time an intermediate accounting record will be generated for all calls whose duration exceeds 24 hours. Duration is
measured from the Service Established time to the current time.
Octet contents range:
1. Hour (Possible values: 0 to 23)

2. Minute (Possible values: 0 to 59)
3. Seconds (Possible values: 0 to 60)
4. Deci-seconds (Possible values: 0 to 9)
In None
st
an
ce
Fi
el
ds
Ac None
tion
Im None
pa
ct
Cl Manual
ea
ring
sonusSbxCallAccountingOutOfServiceNotification -
CRITICAL
Type: CRITICAL
Object ID 1.3.6.1.4.1.2879.2.10.1.1.6.0.2
Description This alarm is generated when Accounting Records are no longer being generated on the Node.
Possible causes:
A change to the accounting configuration.

Errors in the logging mechanism, such as file logging errors.
Repetition None
Event
Codes sonusAlarmNodeID
sonusAlarmLevel
sonusAlarmSequenceId
sonusAlarmTime
sonusAlarmDescription
sonusAcctOutOfServiceReason
Instance None
Fields
Action Examine the SYS event logs on the Node to obtain further information about the event logging failure when the reason specified for
accounting out-of-service is an event logging error.
Impact No Call Detail Records (CDRs) are generated
Clearing Automatic, sonusSbxCallAccountingInServiceNotification
This section contains call processing-related alarms.

sonusCpCdrServerNewXferPendingNotification - MAJOR
sonusCpCdrServerPendingQueueEmptiedNotification - MINOR
sonusCpCdrServerSwitchoverNotification - MAJOR
sonusCpCdrServerTransferFailNotification - MAJOR
sonusCpCdrServerTransferSucceededNotification - INFORMATIONAL
CP Config Alarms
sonusCpConfigCommitFailNotification - MAJOR
sonusCpConfigCommitSucceedNotification - MAJOR
sonusCpConfiguredExceedSystemLimit - MAJOR
CP Event Log Alarms

sonusCpEventLogAdminStateDisableNotification - MINOR
sonusCpEventLogAdminStateEnableNotification - MINOR
sonusCpEventLogDirectoryCreateErrorNotification - CRITICAL
sonusCpEventLogFileClosedNotification - MINOR
sonusCpEventLogFileCountChngNotification - INFORMATIONAL
sonusCpEventLogFileCountClearedNotification - INFORMATIONAL
sonusCpEventLogFileCountNotification - MAJOR
sonusCpEventLogFileCreatedNotification - INFORMATIONAL
sonusCpEventLogFileDebugLevelInfoClearNotification - MINOR
sonusCpEventLogFileDebugLevelInfoNotification - MAJOR
sonusCpEventLogFileDeletedNotification - INFORMATIONAL
sonusCpEventLogFileFilterLevelChngNotification - INFORMATIONAL
sonusCpEventLogFileMaxEventMemSizeChngNotification - INFORMATIONAL
sonusCpEventLogFileMsgQueueChngNotification - INFORMATIONAL
sonusCpEventLogFileRenamedNotification - INFORMATIONAL
sonusCpEventLogFileRestartNotification - MINOR
sonusCpEventLogFileSecFilterLevelChngNotification - MAJOR
sonusCpEventLogFileShutdownNotification - MINOR
sonusCpEventLogFileSizeChngNotification - INFORMATIONAL
sonusCpEventLogFileSkipped - INFORMATIONAL
sonusCpEventLogFileStateNotification - INFORMATIONAL
sonusCpEventLogFileWriteErrorNotification - MAJOR
sonusCpEventLogInfoLevelLoggingDisabledNotfication - MAJOR
sonusCpEventLogInfoLevelLoggingReenabledNotfication - MAJOR
sonusCpEventLogRolloverFastNotification - MAJOR
sonusCpEventLogRolloverScheduledNotification - INFORMATIONAL
sonusCpEventLogRolloverStoppedNotification - INFORMATIONAL
sonusCpEventLogSaveToChngNotification - INFORMATIONAL
sonusCpEventMgrAlarmAckStateUpdate - INFORMATIONAL
sonusCpEventMgrAlarmCommentUpdate - INFORMATIONAL
sonusCpEventMgrAlarmManualClear - MAJOR
CP NTP Alarms
sonusCpNtpAllServersOutOfSyncNotification - MAJOR
sonusCpNtpDownNotification - MAJOR
sonusCpNtpServerInServiceNotification - INFORMATIONAL
sonusCpNtpServerInSyncNotification - INFORMATIONAL
sonusCpNtpServerOutOfServiceNotification - MINOR
sonusCpNtpServerOutOfSyncNotification - MINOR
sonusCpNtpServerReachableNotification - MINOR
sonusCpNtpUpNotification - INFORMATIONAL
CP Radius Alarms
sonusCpRadiusServerFailedNotification - MAJOR
sonusCpRadiusServerPacketsFlushedNotification - MAJOR
CP Redundancy Group Alarms

sonusCpRedundGroupFullRedundancyNotification - MAJOR
sonusCpRedundGroupNoRedundancyNotification - CRITICAL
sonusCpRedundGroupSwitchOverNotification - CRITICAL
CP Software Upgrade Alarms

sonusCpSoftwareUpgradeCommittedNotification - MAJOR
sonusCpSoftwareUpgradeInitiatedNotification - MAJOR
sonusCpSoftwareUpgradeRevertNotification - MAJOR
sonusCpSoftwareUpgradeSucceededNotification - MAJOR
sonusCpSoftwareUpgradeTerminatedNotification - MAJOR
CP System Alarms
sonusCpSystemApacheFailedNotification - CRITICAL
sonusCpSystemBootActiveNotification - MAJOR
sonusCpSystemBootNotification - MAJOR
sonusCpSystemCEBootActiveNotification - MAJOR
sonusCpSystemCEBootDeactiveNotification - MAJOR
sonusCpSystemCEBootNotification - MAJOR
sonusCpSystemCEOperationalNotification - MAJOR
sonusCpSystemCESoftBootActiveNotification - MAJOR
sonusCpSystemCESoftBootNotification - MAJOR
sonusCpSystemCETempFailureNotification - MAJOR
sonusCpSystemCETempNormalNotification - MAJOR
sonusCpSystemCETempWarningNotification - MAJOR
sonusCpSystemCoredumpSpaceWarningNotification - MAJOR
sonusCpSystemFaultAvalancheControlPacketDroppedNotify - MAJOR
sonusCpSystemFaultyHardDiskNotify - CRITICAL
sonusCpSystemLocalDiskBadVolumeNotification - MAJOR
sonusCpSystemLocalDiskHealthErrorClearNotification - MAJOR
sonusCpSystemLocalDiskHealthErrorNotification - MAJOR
sonusCpSystemLocalDiskLifeAttribErrorClearNotification - MAJOR
sonusCpSystemLocalDiskLifeAttribErrorNotification - MAJOR
sonusCpSystemLocalDiskMisMatchNotification - MAJOR
sonusCpSystemLocalDiskSpaceClearAlarmsNotification - MAJOR
sonusCpSystemLocalDiskSpaceCriticalNotification - CRITICAL
sonusCpSystemLocalDiskSpaceFaultNotification - CRITICAL
sonusCpSystemLocalDiskSpaceOkNotification - MAJOR
sonusCpSystemLocalDiskSpaceReadOnlyNotification - MAJOR
sonusCpSystemLocalDiskSpaceWarningNotification - MAJOR
sonusCpSystemLocalDiskTooManyFilesNotification - MAJOR
sonusCpSystemLocalDiskWritableNotification - MINOR
sonusCpSystemNotMacAddressOwnerNotification - INFORMATIONAL
sonusCpSystemNPTempFailureNotification - MAJOR
sonusCpSystemNPTempNormalNotification - MAJOR
sonusCpSystemNPTempWarningNotification - MAJOR
sonusCpSystemProcessCoredumpGeneratedNotification - MAJOR
sonusCpSystemProductCapabalityMismatch - CRITICAL
sonusCpSystemReadonlyFileSystemNotify - CRITICAL
sonusCpSystemRestoreConfigNotification - MAJOR
sonusCpSystemServerDrbdReformatBackupNotify - MAJOR
sonusCpSystemServerDrbdReformatCompletedNotify - MAJOR
sonusCpSystemServerDrbdReformatErrorNotify - MAJOR
sonusCpSystemServerDrbdReformatStartNotify - MAJOR
sonusCpSystemServerDrbdReformatSwitchoverNotify - MAJOR
sonusCpSystemServiceRestartNotification - CRITICAL
sonusCpSystemSoftBootActiveNotification - MAJOR
sonusCpSystemSoftBootNotification - MAJOR
CP Timer Alarms
sonusSbxCallProcAnswerSupervisionTimeout - MAJOR
sonusSbxCallProcLongDurationCallTimeout - MINOR
This section contains the following Call Processor CDR Server alarms.
sonusCpCdrServerPendingQueueEmptiedNotification - MINOR
sonusCpCdrServerTransferSucceededNotification - INFORMATIONAL
Type: MAJOR
Object 1.3.6.1.4.1.2879.2.8.1.2.1.9.0.3
ID
Descript This trap indicates that a CDR file transfer is added to the pending queue when the accounting file is closed due to a rollover
ion period, or when the maximum configured file size (bufferSize) is reached.
This queue is usually small unless the previous CDR files were not transferred, or the transfer is slow due to network issues. In
such instances, the queue grows until the previously queued files are transferred.
Repetiti Yes. The trap is generated each time a file is added to the queue.
on
Event
sonusAlarmLevel
sonusAlarmTime
Instance
Fields sonusCpCdrServerType
sonusCpCdrServerIpAddress
Action Check the CDR server and make sure it is functioning correctly to avoid delays in file transfers.
Impact CDR files are not available for the mediation server to process until the transfer is completed.
Clearing Manual
sonusCpCdrServerPendingQueueEmptiedNotification -
MINOR
Type: MINOR
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.9.0.4
Description The trap notifies that the CDR server all the pending transfers are completed.
Repetition None
Event Codes
sonusCpCdrServerType
Instance Fields None
Action None
Impact None
Clearing Manual
Type: MAJOR
Object 1.3.6.1.4.1.2879.2.8.1.2.1.9.0.5
ID
Descript This trap is generated when the specified CDR server is not reachable, and the SBC starts sending CDRs to an alternate/secondary
ion server. This notification is flow-controlled, and occurs once every ten seconds.
Repetiti None
on
Event
sonusAlarmLevel
sonusAlarmTime
sonusCpCdrServerType
Instance None
Fields
Action Investigate to determine why the CDR server is no longer reachable, and rectify.
Impact None
Clearing Manual
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.9.0.1
Description The alarm indicates a CDR file transfer failed for a particular instance. The SBC continues to retry the transfer until the file is
successfully transferred.
Repetition Yes. The alarm is generated each time a transfer fails.
Event
sonusAlarmLevel
sonusAlarmTime
Instance
Fields sonusCpCdrServerType
Action Check the CDR server and make sure it is functioning correctly.
Impact The specified CDR file transfer timed out (exceeded the configured transferTimeout value)
Clearing Manual
sonusCpCdrServerTransferSucceededNotification -
INFORMATIONAL
Type: INFORMATIONAL
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.9.0.6
Description This alarm indicates that the CDR transfer succeeded. Clears the alarm sonusCpCdrServerTransferFailNotification.
Repetition This notification is flow controlled and does not occur more often than once every ten seconds.
Event Codes sonusAlarmNodeID

sonusAlarmLevel
sonusAlarmTime
Instance Fields sonusCpCdrServerType

Action None required.
Impact No impact.
Clearing Automatic; sonusCpCdrServerTransferFailNotification
CP Config Alarms
This section contains the following Call Processor configuration alarms.
Type: MAJOR
Object 1.3.6.1.4.1.2879.2.8.1.2.1.5.0.27
ID
Descript This trap indicates a configuration commit failed. A successful configuration commit indicates that configuration changes made to the
ion SBC functionalities via the CLI commands are successfully applied in the SBC.
Repetiti None
on
Event sonusCpSystemAdminName
Codes sonusCpSystemServerName
Instance None
Fields
Action Examine the CLI commands and reapply the CLI commands with correct parameters.
Impact Changes in configuration made to the SBC functions do not take effect.
Clearing Manual
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.5.0.26
Description This trap indicates that a configuration commit has succeeded.
Repetition None
Event Codes sonusCpSystemAdminName

sonusCpSystemServerName
Action None
Impact None
Clearing Manual
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.8.0.8
Description The configured number of licenses for sessions exceeds the system limit (64000). This trap is applicable for only Hardware
platforms as the session limit is fixed for hardware platforms.
Repetition None
Event sonusSessConfigLicenses
Codes sonusSessSystemLimit
Instance None
Fields
Action Ensure configured number of licenses for sessions does not exceed the system limit.
Impact Calls exceeding the session license limit are rejected.
Clearing Manual
CP Event Log Alarms

This section contains the following Call Processor Event Log alarms.
sonusCpEventLogDirectoryCreateErrorNotification - CRITICAL
sonusCpEventLogFileCountChngNotification - INFORMATIONAL
sonusCpEventLogFileCountClearedNotification - INFORMATIONAL
sonusCpEventLogFileDebugLevelInfoClearNotification - MINOR
sonusCpEventLogFileFilterLevelChngNotification - INFORMATIONAL
sonusCpEventLogFileMaxEventMemSizeChngNotification - INFORMATIONAL
sonusCpEventLogFileMsgQueueChngNotification - INFORMATIONAL
sonusCpEventLogFileRenamedNotification - INFORMATIONAL
sonusCpEventLogFileSecFilterLevelChngNotification - MAJOR
sonusCpEventLogFileSizeChngNotification - INFORMATIONAL
sonusCpEventLogInfoLevelLoggingDisabledNotfication - MAJOR
sonusCpEventLogInfoLevelLoggingReenabledNotfication - MAJOR
sonusCpEventLogRolloverScheduledNotification - INFORMATIONAL
sonusCpEventLogRolloverStoppedNotification - INFORMATIONAL
sonusCpEventLogSaveToChngNotification - INFORMATIONAL
Type: MINOR
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.4.0.24
Description This alarm indicates that the security or audit logging is disabled.
Repetition None
Event Codes sonusCpEventLogType - The type of the event log being modified
system(1)
debug(2)
trace(3)
acct(4)
security(5)
audit(6)
packet(7)
Action None required; informational only
Impact Logging stops for the specified Event Code.
Clearing Automatic; sonusCpEventLogAdminStateEnableNotification
Type: MINOR
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.4.0.23
Description This alarm indicates that the security or audit logging is enabled.
Repetition None
Event Codes sonusCpEventLogType - The type of the event log being modified
Action None; informational only
Impact None
Clearing Automatic
sonusCpEventLogDirectoryCreateErrorNotification -
CRITICAL
Type: CRITICAL
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.4.0.13
Description This trap indicates that the inability of the system to create a directory for event logging.
Repetition None
Event Codes sonusCpEvLogDirName

sonusCpEvLogErrorCode
sonusCpEventLogType
Action Contact Sonus Technical Support.
Impact Logging for the reported log type is not available.
Clearing Manual
Type: MINOR
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.4.0.4
Description This trap indicates the name of the event file which has been closed.
Repetition None
Event Codes sonusCpEventLogType

sonusEventLogTypeStatusCurrentFile
Action None required; informational only.
Impact None
Clearing Manual
sonusCpEventLogFileCountChngNotification -
INFORMATIONAL
Type: INFORMATIONAL
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.4.0.7
Description This trap indicates the number of Event Log files maintained for this event type changed.
Repetition None
Event Codes sonusEventLogTypeAdminFileCount

sonusCpEventLogType
Impact None
Clearing Manual
sonusCpEventLogFileCountClearedNotification -
INFORMATIONAL
Type: INFORMATIONAL
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.4.0.17
Description This alarm indicates that the number of event log files has dropped below the either the 100% or 75% threshold.
Repetition None
Event Codes sonusCpEvLogFilePercentage

sonusCpEvLogCurFileCount
sonusEventLogTypeAdminFileCount
sonusEvLogTypeName
Action None
Impact Logging rollover will not overwrite existing files.
Clearing Manual
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.4.0.6
Description This alarm indicates that the number of event log files is approaching the configured maximum.
Repetition None
Event Codes sonusEvLogTypeName

sonusCpEvLogFilePercentage
sonusCpEvLogCurFileCount
sonusEventLogTypeAdminFileCount
Action If it is important to archiving operations, relocate files that are approaching the configured maximum to a separate server.
Impact Logging rollover to the first file of this log type if 100% is reached.
Clearing Automatic, sonusCpEventLogFileCountClearedNotification
Type: INFORMATIONAL
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.4.0.2
Description This trap indicates the name of the event file created for logging.
Repetition None

Impact None
Clearing Manual
sonusCpEventLogFileDebugLevelInfoClearNotification -
MINOR
Type: MINOR
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.4.0.31
Description This alarm is generated when the debug event log filter level is no longer set to INFO and clears sonusCpEventLogFileDebugL
evelInfoNotification
Repetition None
Event sonusAlarmNodeID
Codes sonusAlarmLevel
sonusAlarmTime
Instance None
Fields
Action None
Impact None
Clearing Manual
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.4.0.30
Description This alarm is generated when the debug event log filter level is set to INFO.
Repetition This alarm is triggered when the filter level for debug event log is set to INFO, and continues every five minutes until it is
cleared.

sonusAlarmLevel
sonusAlarmTime
Instance None
Fields
Action Change the filter level of the debug event log to something other than INFO
Impact A higher level of event logging can cause unexpected behavior and service affecting issues on the SBC.
Clearing Automatic; sonusCpEventLogFileDebugLevelInfoClearNotification
Type: INFORMATIONAL
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.4.0.19
Description This trap indicates that an accounting file was deleted because the maximum file count is reached.
Repetition None
Event Codes sonusEventLogTypeStatusCurrentFile

sonusCpEventLogType
Action None
Impact None
Clearing Manual
sonusCpEventLogFileFilterLevelChngNotification -
INFORMATIONAL
Type: INFORMATIONAL
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.4.0.12
Description This trap indicates that the level of event logging for this event type changed.
Repetition None
Event Codes sonusEventLogTypeAdminFilterLevel

sonusCpEventLogType
Impact None
Clearing Manual
sonusCpEventLogFileMaxEventMemSizeChngNotification -
INFORMATIONAL
Type: INFORMATIONAL
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.4.0.11
Description This trap indicates that the maximum size of the memory event log buffer changed.
Repetition None
Event Codes sonusEventLogTypeAdminMaxEventMemorySize

sonusCpEventLogType
Impact None
Clearing Manual
sonusCpEventLogFileMsgQueueChngNotification -
INFORMATIONAL
Type: INFORMATIONAL
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.4.0.9
Description This trap indicates that the number event log message entries to the buffer changed.
Repetition None
Event Codes sonusEventLogTypeAdminMessageQueueSize

sonusCpEventLogType
Impact None
Clearing Manual
sonusCpEventLogFileRenamedNotification -
INFORMATIONAL
Type: INFORMATIONAL
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.4.0.21
Description This trap indicates that an accounting file was renamed to remove the OPEN file extension.
Repetition None
Event Codes sonusCpEventLogType – Log type (always accounting)

sonusEventLogTypeStatusCurrentFile – File name with OPEN extension
sonusEventLogRenameToFile – File name without OPEN extension
Action None
Impact None
Clearing Manual
Type: MINOR
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.4.0.3
Description This alarm indicates that file event logging has been automatically restarted.
Repetition None
Impact None
Clearing Manual. Clearing alarm for sonusCpEventLogFileShutdownNotification
sonusCpEventLogFileSecFilterLevelChngNotification -
MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.4.0.22
Description This alarm indicates the event logging filter level changed for this event.
Repetition None
Event Codes
sonusCpEventLogType – The type of the event log modified.
sonusEventLogTypeAdminFilterLevel – Events with this severity, or greater, are logged.
Action Manual
Impact None
Clearing Manual; cleared by user
Type: MINOR
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.4.0.5
Description This alarm indicates that a shutdown of file event logging has occurred.
Repetition None
Event Codes sonusCpEvLogShutdownReason

sonusCpEvLogAdminState
sonusCpEventLogType
Action Do the following:

Check Event Logging permissions
Restore SBC communication to the node.
Check status of SBC Core systems for issues affecting ability of the node to write event logs.
Impact Varies from "loss of logging" to "no impact" (where files are administratively closed).
Clearing Manual
sonusCpEventLogFileSizeChngNotification -
INFORMATIONAL
Type: INFORMATIONAL
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.4.0.8
Description This trap indicates that the maximum size of a single event log file has changed.
Repetition None
Event Codes sonusEventLogTypeAdminFileSize

sonusCpEventLogType
Impact None
Clearing Manual
Type: INFORMATIONAL
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.4.0.18
Description This trap indicates the name of the event file which has been skipped because of file errors.
Repetition None
Event Codes sonusEventLogTypeStatusCurrentFile

sonusCpEventLogType
Action None
Impact None
Clearing Manual
Type: INFORMATIONAL
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.4.0.1
Description This trap indicates the current state of event file logging.
Repetition None
Event Codes sonusCpEvLogAdminState

sonusCpEventLogType
Impact None
Clearing Manual
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.4.0.25
Description This alarm indicates the name of the event file which could not write an event.
Repetition None

sonusAlarmLevel
sonusAlarmTime
Action None required; Determine if disk is failing or full
Impact Loss of logging
Clearing Manual
sonusCpEventLogInfoLevelLoggingDisabledNotfication -
MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.4.0.26
Description This alarm indicates that the info level logging is disabled because of system congestion.
Repetition None

sonusAlarmLevel
sonusAlarmTime
Action To re-enable logging, the following command must be executed:
request oam eventLog infoLevelLoggingEnable clearInfoLevelLoggingDisabled
If info level logging is re-enabled, the system becomes more congested and there is a degradation of system performance.
Impact None
Clearing Automatic; sonusCpEventLogInfoLevelLoggingReenabledNotfication
sonusCpEventLogInfoLevelLoggingReenabledNotfication -
MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.4.0.27
Description This alarm indicates that info level logging is re-enabled.
Repetition None

sonusAlarmLevel
sonusAlarmTime
Action None required, informational only
Impact None
Clearing Manual
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.4.0.16
Description This trap indicates that event log rollover is occurring frequently.
Repetition None
Event Codes sonusEvLogTypeName
Action Investigate DBG or SYS file to determine what is causing this condition, and rectify.
Impact None
Clearing Manual
sonusCpEventLogRolloverScheduledNotification -
INFORMATIONAL
Type: INFORMATIONAL
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.4.0.14
Description This trap indicates that event log for this log type is scheduled to roll over.
Repetition None
Action None required
Impact None
Clearing Manual
sonusCpEventLogRolloverStoppedNotification -
INFORMATIONAL
Type: INFORMATIONAL
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.4.0.15
Description This trap indicates that event log rollover stopped for this log type.
Repetition None
Impact None
Clearing Manual
sonusCpEventLogSaveToChngNotification -
INFORMATIONAL
Type: INFORMATIONAL
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.4.0.10
Description This trap indicates that the location changed where events are saved.
Repetition None

sonusEventLogTypeAdminSaveTo
Instance Fields
Impact None
Clearing Manual
Type: INFORMATIONAL
Object 1.3.6.1.4.1.2879.2.8.1.2.1.4.0.28
ID
Descript The event code sonusAlarmNodeID is updated with the "acknowledgeState" field (possible values are "acknowledge" and
ion "unAcknowledge"). The "ackowledgeState" reflects the current operator state of this trap.
Repetiti Yes
on
sonusAlarmTime
sonusAlarmMgrId
sonusAlarmMgrAckState
Instance sonusAlarmMgrId
Fields sonusAlarmMgrAckState
Action None
Impact None
Clearing Manual
Type: INFORMATIONAL
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.4.0.29
Description The event code sonusAlarmNodeID "comment" field is updated by an operator.
Repetition Yes

sonusAlarmLevel
sonusAlarmTime
sonusAlarmMgrId
sonusAlarmMgrComment
Instance Fields sonusAlarmMgrId

sonusAlarmMgrComment
Action None
Impact None
Clearing Manual
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.4.0.20
Description This trap indicates that an alarm was manually cleared by an operator.
Repetition None
Event Codes sonusAlarmMgrId
Action None
Impact The Alarm indicator (LED state) may prematurely reset.
Clearing Manual
CP NTP Alarms
This section contains the following Call Processor NTP alarms.
Type: MAJOR
Object 1.3.6.1.4.1.2879.2.8.1.2.1.1.0.5
ID
Descript This alarm indicates that all Network Timing Protocol Servers are Out of Sync.
ion
Repetiti None
on
Event sonusCpSystemServerName
Codes
Instance None
Fields
Action Investigate cause for this out-of-sync condition. A probable cause is that NTP protocol (communication between NTP servers and
node) was interrupted.
To reference NTP Server CLI commands syntax, parameters and examples, see "NTP Services Management" section in SBC Core
CLI Reference Guide.
Impact Call processing will continue. Timestamps in log files and call accounting records will drift from the actual time on NTP server. If the
drift becomes great enough, there may be slight discrepancies in billing records.
Clearing Manual
Type: MAJOR
Obj 1.3.6.1.4.1.2879.2.8.1.2.1.1.0.4
ect
ID
Des This alarm indicates that the Network Timing Protocol is down.
crip
tion
Rep None
etiti
on
Eve sonusCpSystemServerName
nt sonusCpNtpDownReason
Co sonusCpNtpDownReason
des
Inst None
anc
e
Fiel
ds
Acti Take action based upon Reason code:

on noNtpServerConfigured (1) - Create at least one NTP client object with an IP address of a known NTP server.
allNtpServersOutOfSync (2) - If all NTP entries suddenly transition from to OUTOFSYNC, do the following, as applicable:
View NTP SERVER ADMIN screen to verify the NTP clients are properly configured.
Check for connectivity by pinging the IP address of all configured NTP servers.
If you do not ping successfully, investigate possible causes: Network outage, disconnected cable, NTP servers are down.
Check DEBUG and SYSTEM logs for NTP messages which may indicate invalid NTP packets received.
If the above condition is not present and no error messages exist in the DEBUG and SYSTEM logs, a "glitch" in the network may have
occurred, or NTP packets were discarded for some reason. Allow a reasonable amount of time to pass (depending upon how long the
clients have been out of sync) for NTP clients to sync back up to NTP servers. If unsure, contact Sonus TAC for guidance.
Imp The impact is based upon the sonusNtpDownReasonCode:

act noNtpServerConfigured(1)
No NTP client objects were created. If fault is present from boot-up, call admission is suspended - no calls are allowed since the NTP start
time is incorrect.
allNtpServersOutOfSync(2) If one or more NTP servers were up and in sync prior to receiving this alarm, the node timing for this particular
node may drift away from the NTP network timing at a rate based upon the accuracy of the internal clock.
During this fault condition, an NTP client may simply be synced up with its configured server and slowly drifting back toward the correct
NTP time.
Cle Automatic; sonusCpNtpUpNotification

aring
Type: INFORMATIONAL
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.1.0.1
Description This alarm indicates that a Network Timing Protocol Server is in service.
Repetition None
Event Codes sonusCpSystemServerName

sonusCpNtpIpAddress
Action None
Impact None
Clearing Manual
Type: INFORMATIONAL
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.1.0.7
Description This alarm indicates that a Network Timing Protocol Server is in Sync.
Repetition None

sonusCpNtpIpAddress
Impact No impact unless this is the first NTP server to come into service. If this is the case, the system will now have an NTP source.
Clearing Manual
Type: MINOR
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.1.0.2
Description This alarm indicates that a Network Timing Protocol Server is out of service.
Repetition None

sonusCpNtpIpAddress
sonusCpNtpServerOutOfServiceReason
Action None
Impact None
Clearing Automatic, sonusCpNtpServerInServiceNotification
Type: MINOR
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.1.0.6
Description This alarm indicates that a Network Timing Protocol Server is out of Sync.
Repetition None

sonusCpNtpIpAddress
Impact None
Clearing Automatic, sonusCpNtpServerInSyncNotification
Type: MINOR
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.1.0.8
Description This trap indicates that a Network Timing Protocol Server is Reachable.
Repetition None

sonusCpNtpIpAddress
Action None
Impact None
Clearing Manual
Type: INFORMATIONAL
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.1.0.3
Description This alarm indicates that the Network Timing Protocol Server is Up.
Repetition None
Action None
Impact None
Clearing Manual
CP Radius Alarms
This section contains the following Call Processor Radius alarms.
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.7.0.1
Description This trap indicates that a radius accounting server has been marked as failed.
Repetition None
Event Codes sonusCpRadiusServerName
Action None
Impact None
Clearing Manual
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.7.0.2
Description This trap indicates that radius packets are flushed because a radius server is not available.
Repetition None
Event Codes sonusCpRadiusFlushedPackets

sonusCpRadiusFlushedPacketsFile
Action None
Impact None
Clearing Manual
CP Redundancy Group Alarms
This section contains the following Call Processor Redundancy Group alarms.
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.2.0.3
Description This alarm indicates that the specified redundancy group has full redundancy protection.
Repetition None
Event Codes sonusCpRedundancyServicesGroupName
Action None required, informational only.
Impact None
Clearing Manual; sonusCpRedundGroupSwitchOverNotification
Type: CRITICAL
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.2.0.2
Description This alarm indicates that the specified redundancy group has no redundancy protection.
Repetition None
Event Codes sonusCpRedundancyServicesGroupName
Action None
Impact There is no redundancy protection for the particular redundancy group.
Clearing Automatic; sonusCpRedundGroupFullRedundancyNotification
Type: CRITICAL
Object 1.3.6.1.4.1.2879.2.8.1.2.1.2.0.1
ID
Descri This alarm indicates a server module redundancy switchover has occurred. The standby server module has become active. The
ption previous active server module, and group information are included. For 1+1 the redundancy model, there is no group name.
Repetit None
ion
Codes sonusCpRedundPrevActiveServerName
sonusCpRedundancyServicesGroupName
Instan None
ce
Fields
Action None
Impact Loss of redundancy occurs for the particular redundancy group. Some transient calls may be lost as a result of switchover, but no
lasting (normally) impact to overall system operation occurs.
Clearing Automatic; sonusCpRedundGroupFullRedundancyNotification
CP Software Upgrade Alarms
This section contains the following Call Processor Software Upgrade alarms.
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.3.0.6
Description This trap indicates that a Live Software Upgrade is starting.
Repetition None
Event Codes sonusSystemSoftwareUpgradeOldRelease

sonusSystemSoftwareUpgradeNewRelease
Action None
Impact None
Clearing Manual
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.3.0.1
Description This alarm indicates that a software upgrade has been initiated.
Repetition None
Action None
Impact none
Clearing Manual
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.3.0.4
Description This trap indicates that a Live Software Upgrade reverted to the previous release.
Repetition None
Event Codes None
Impact None
Clearing Manual
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.3.0.3
Description This alarm indicates that a software upgrade has succeeded for the specified reason.
Repetition None
Event Codes sonusSystemSoftwareUpgradeStatusReason
Instance None
Fields
Impact None
Clearing Internal alarm that clears sonusCpSoftwareUpgradeInitiatedNotification and sonusCpSoftwareUpgradeTerminatedNotification

alarms.
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.3.0.2
Description This alarm indicates that a software upgrade has terminated for the specified reason.
Repetition None
Event Codes sonusSystemSoftwareUpgradeStatusReason
Action Resolve problem and retry the software upgrade
Impact Software upgrade was unsuccessful
Clearing Manual
CP System Alarms
This section contains the following Call Proccessor System alarms.
sonusCpSystemCoredumpSpaceWarningNotification - MAJOR
sonusCpSystemFaultAvalancheControlPacketDroppedNotify - MAJOR
sonusCpSystemLocalDiskHealthErrorClearNotification - MAJOR
sonusCpSystemLocalDiskLifeAttribErrorClearNotification - MAJOR
sonusCpSystemLocalDiskSpaceClearAlarmsNotification - MAJOR
sonusCpSystemLocalDiskSpaceCriticalNotification - CRITICAL
sonusCpSystemLocalDiskSpaceReadOnlyNotification - MAJOR
sonusCpSystemNotMacAddressOwnerNotification - INFORMATIONAL
sonusCpSystemProcessCoredumpGeneratedNotification - MAJOR
sonusCpSystemServerDrbdReformatCompletedNotify - MAJOR
sonusCpSystemServerDrbdReformatSwitchoverNotify - MAJOR
Type: CRITICAL
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.5.0.29
Description This alarm indicates that the Apache service failed to start.
Repetition None

sonusAlarmLevel
sonusAlarmTime
Action Verify installation, configuration and network health.
Impact EMA Platform Mode may inaccessible.
Clearing Manual
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.5.0.2
Description This alarm indicates that the node is active after a reboot.
Repetition None
Action None
Impact None
Clearing Manual
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.5.0.1
Description This alarm indicates that the node boot is requested.
Repetition None
Action None Required
Impact Node will restart
Clearing Manual
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.5.0.20
Description This alarm indicates that the CE/server is active after a reboot but not completely ready or functional.
Repetition None
Event Codes
sonusCpSystemAdminName
Action None
Impact None
Clearing Manual
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.5.0.56
Description This alarm indicates that the CE/server is deactivating.
Repetition None
Event Codes
sonusCpSystemAdminName Name of the system
sonusCpSystemServerName - The unique identifier assigned to this card or server
Action None
Impact None
Clearing Automatic: sonusCpSystemCEBootActiveNotification,

sonusCpSystemCESoftBootActiveNotification
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.5.0.19
Description This alarm indicates that a CE/server boot was requested.
Repetition None

Impact The CE will restart.
Clearing Manual
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.5.0.18
Description This trap indicates a server is operational and is ready to take call load.
Repetition None

Action None
Impact None
Clearing Manual
Type: MAJOR
Object 1.3.6.1.4.1.2879.2.8.1.2.1.5.0.22
ID
Descri This alarm indicates that the CE/server is active after a soft reboot. A node soft boot is requested. Soft boot is requested by issuing a
ption 'softReset' on system or server. softReset is when the application is restarted on the system and not the complete server OS.
Repeti None
tion
Event sonusCpSystemAdminName
Instan None
ce
Fields
Action None
Impact None
Cleari Manual
ng
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.5.0.21
Description This alarm indicates a soft boot on the server occurred.
A soft boot restarts the application, but not the complete OS.
Repetition None

Action None
Impact The applications on the server restart.
Clearing Manual
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.5.0.23
Description This alarm indicates that the CE/server temperature is above normal. The threshold value to generate this temperature failure
alarm is 70 degrees centigrade.
Repetition None
sonusAlarmTime
sonusCpSystemServerTemperatureSensorId
sonusCpSystemServerTemperature
Instance sonusCpSystemAdminName
Fields sonusCpSystemServerName
Action Check CP System CE/server temperature and fan status.
Impact Server shuts down if the temperature reaches critical level.
Clearing Automatic; sonusCpSystemCETempNormalNotification
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.5.0.24
Description This alarm indicates the CE/server temperature is normal. The threshold value to generate this alarm is 60 degrees centigrade.
Repetition None

sonusAlarmLevel
sonusAlarmTime
Instance Fields sonusCpSystemAdminName

Impact None
Clearing Automatic; sonusCpSystemCETempWarningNotification
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.5.0.25
Description This alarm indicates the server temperature is approaching a critical level. The threshold value to generate this alarm is 65
degrees centigrade.
Repetition None

sonusAlarmLevel
sonusAlarmTime
Action Check CP System CE/server temperature and fan status.
Impact Server shuts down if the temperature reaches critical level.
Clearing Automatic; sonusCpSystemCETempNormalNotification
sonusCpSystemCoredumpSpaceWarningNotification -
MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.5.0.37
Description This trap indicates a system is running low on core dump space.
Repetition None

sonusCpSystemCoredumpSpacePct
Action Remove coredump files from the server to increase space for any future core dumps.
Impact If the free disk space is not increased, the future core dumps may not get saved.
Clearing Manual
sonusCpSystemFaultAvalancheControlPacketDroppedNotify
- MAJOR
Type: MAJOR
Object 1.3.6.1.4.1.2879.2.8.1.2.1.17.0.1
ID
Descripti This trap indicates that the first packet is dropped due to matching entries in blocking entries of Fault Avalanche Detection and
on Control Feature.
Repetition None
Event
sonusAlarmLevel
Instance
Fields sonusAlarmTime
sonusFacKeyElementName
sonusFacKeyValueName
sonusCalledParty
Action Verify/Correct specific endpoints originating the calls to avoid Fault avalanche until the solution is provided. Override this option by
adding entries to system nonBlockingEntries or by deleting the fault records
Impact Calls are rejected as crash was observed with these key value pair,and crash count threshold is exceeded.
The calls with this key value pair keep rejecting till it crashes again or it timeouts or crash count threshold comes below configured
threshold for this key element.
Clearing Manual
Type: CRITICAL
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.5.0.75
Description This trap indicates that the hard disk is faulty due to intermittent failures.
Repetition None
Event Codes
sonusAlarmNodeID
sonusAlarmLevel
sonusAlarmTime
Instance Fields
Action Replace the hard disk.
Impact The system may experience intermittent faults/failures.
Clearing Manual
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.5.0.6
Description This trap indicates that a bad volume is detected on the hard drive.
Repetition None

sonusCpSystemHardDiskNumber
Action Replace the hard disk as soon as possible.
Impact The hard disk may be operating at reduced capacity.
Clearing Manual
sonusCpSystemLocalDiskHealthErrorClearNotification -
MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.5.0.52
Descripti This alarm indicates that the system cleared the life remaining threshold alarm from Self-Monitoring, Analysis and Reporting
on Technology (SMART) which is built into many hard drives.
Repetition None
Event sonusCpSystemAdminName - Specifies the name of the system

Codes sonusCpSystemServerName - Specifies the unique identifier assigned to this card or server
sonusCpSystemHardDiskName - Specifies the name of a disk device on the system.
sonusCpSystemLifeAvailAttrib - Specifies the value representing the percentage of disk life remaining reported by Self-Monitoring,
Analysis and Reporting Technology (SMART) or N/A if not supported.
Instance None
Fields
Action Run diagnostics/replace the drive if needed.
Impact System is running on a possibly failing disk.
Clearing Manual
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.5.0.51
Descripti This alarm indicates that the system received an error from Self-Monitoring, Analysis and Reporting Technology (SMART) which is
on built into many hard drives.
Repetition None
Event sonusCpSystemAdminName - Specifies the name of the system.

Codes sonusCpSystemServerName - Specifies the unique identifier assigned to this card or server.
sonusCpSystemHardDiskError - Specifies the error string reported by Self-Monitoring, Analysis and Reporting Technology (SMART).
Instance None
Fields
Action Run diagnostics/replace the drive, if needed.
Clearing Automatic, sonusCpSystemLocalDiskLifeAttribErrorClearNotification
sonusCpSystemLocalDiskLifeAttribErrorClearNotification -
MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.5.0.54
Descripti This alarm indicates the system cleared life remaining threshold alarm from Self-Monitoring, Analysis and Reporting Technology
on (SMART) which is built into many hard drives.
Repetition None

Instance None
Fields
Action Run diagnostics/replace the drive, if needed.
Clearing Manual
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.5.0.53
Descripti This alarm indicates that the system received a life remaining threshold exceeded event from Self-Monitoring, Analysis and
on Reporting Technology (SMART) which is built into many hard drives.
Repetition None

sonusCpSystemHardDiskError - Specifies the error string reported by Self-Monitoring, Analysis and Reporting Technology (SMART).
Instance None
Fields
Action Run diagnostics/replace the drive if needed.
Clearing Automatic, sonusCpSystemLocalDiskLifeAttribErrorClearNotification
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.5.0.7
Description This trap indicates that an incompatible hard disk is inserted on a server.
Repetition None

Action Remove the hard drive and insert a compatible hard drive.
Impact Use of an incompatible hard drive prevents hard drive redundancy.
Clearing Manual
sonusCpSystemLocalDiskSpaceClearAlarmsNotification -
MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.5.0.80
Description This alarm clears all the previous disk space usage alarms before issuing fresh ones.
Repetition None

sonusAlarmLevel
sonusAlarmTime
sonusCpSystemDiskPartition
sonusCpSystemDiskSpaceUsedPct

Impact None
Clearing Automatic
sonusCpSystemLocalDiskSpaceCriticalNotification -
CRITICAL
Type: CRITICAL
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.5.0.78
Description This alarm is generated when the disk usage is greater than 90%.
Repetition None

sonusAlarmLevel
sonusAlarmTime

Action Free disk space.
Impact Indicates the disk usage has exceeded 90%.
Note: If the disk exceeds 95% capacity, the SBC application automatically restarts.
Clearing Automatic; sonusCpSystemLocalDiskSpaceClearAlarmsNotification and sonusCpSystemLocalDiskSpaceOkNotification
Type: CRITICAL
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.5.0.79
Description This alarm is generated when the disk usage is greater than 95%; the application automatically shuts down.
Repetition None

sonusAlarmLevel
sonusAlarmTime

Action Free up disk space, and then manually restart the application.
Impact The application automatically shuts down.
Clearing Automatic; sonusCpSystemLocalDiskSpaceClearAlarmsNotification and sonusCpSystemLocalDiskSpaceOkNotification
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.5.0.8
Description This alarm indicates that space on the hard disk is within the limits of normal operation (70% of the total disk space).
Repetition None

Action None
Impact None
Clearing Manual
sonusCpSystemLocalDiskSpaceReadOnlyNotification -
MAJOR
Type: MAJOR
Object iD 1.3.6.1.4.1.2879.2.8.1.2.1.5.0.9
Description This trap indicates that free space on the specified hard disk is low. The disk is now operating in read-only mode.
Repetition None

Action Free up disk space.
Impact No additional data is written to the disk.
Clearing Manual
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.5.0.10
Description This alarm indicates the SBC hard disk space has reached 75% capacity.
Repetition None

sonusAlarmLevel
sonusAlarmTime

Action Take immediate action to free up disk space.
Impact If the disk exceeds 95% capacity, the SBC application automatically restarts.
Clearing Manual
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.5.0.11
Description This alarm indicates that there are too many files on the hard disk (20% of the total number of files allowed).
Repetition None

Action Free up disk space.
Impact No additional data is written to the disk if the total file count reaches the maximum allowed count.
Clearing Manual
Type: MINOR
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.5.0.13
Description This trap indicates that local disk is now writable.
Repetition None

Action None
Impact None
Clearing Manual
sonusCpSystemNotMacAddressOwnerNotification -
INFORMATIONAL
Type: INFORMATIONAL
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.5.0.47
Description This trap indicates that the system is running with a set of MAC addresses that does not belong to this system. This is possible if
a server is replaced.
Repetition None
Event Codes sonusCpSelfBaseMacAddress

sonusCpPeerBaseMacAddress
sonusCpActiveBaseMacAddress
Instance None
Fields
Action None
Impact None
Clearing Manual
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.5.0.31
Description This trap indicates that the CE/server NP temperature is higher than normal. It is generated when the temperature is greater than
or equal to 90oC.
Repetition None

sonusAlarmLevel
sonusAlarmTime
Action Check NP temperature and Fan status
Impact Server will shutdown if the NP temperature reaches critical level.
Clearing Automatic; sonusCpSystemNPTempNormalNotification
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.5.0.32
Description This alarm indicates that the CE/server NP temperature is normal. It is generated when the temperature goes below 80oC. It
clears the alarms;
sonusCpSystemNPTempFailureNotification
sonusCpSystemNPTempWarningNotification
Repetition None

sonusAlarmLevel
sonusAlarmTime
Action None
Impact NP is running at normal temperature.
Clearing Manual
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.5.0.33
Description This alarm indicates that the CE/server NP temperature is reaching critical level. It is generated when the temperature is greater
than or equal to 85oC.
Repetition None

sonusAlarmLevel
sonusAlarmTime
Instance sonusCpSystemServerName
Fields sonusCpSystemAdminName
Action Check NP temperature and Fan status
Impact Server will shutdown if the NP temperature reaches critical level.
Clearing Automatic; sonusCpSystemNPTempNormalNotification
sonusCpSystemProcessCoredumpGeneratedNotification -
MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.5.0.36
Description This alarm indicates that a coredump is generated for a process running on the indicated server.
Repetition None

sonusCpSystemCoredumpFile
Action Extract coredump from server and remove it on server to make space for any future coredumps.
Impact Application on the indicated server will be restarted.
Clearing Manual
Type: CRITICAL
Object iD 1.3.6.1.4.1.2879.2.8.1.2.1.5.0.49
Description This is a generic alarm used for any sort of mismatch between the servers of a HA pair.
Repetition None

sonusAlarmLevel
sonusAlarmTime
sonusCpProductCapabilityName
sonusCpProductCapabilityValue
sonusCpProductPeerCapabilityValue
Instance Fields sonusCpSystemServerName

sonusCpProductCapabilityName
sonusCpProductCapabilityValue
sonusCpProductPeerCapabilityValue
Action Check the capability that is mismatching and correct.
Impact Depending on the type of capability, standby server may not come up or may operate in reduced capacity.
Clearing Manual
Type: CRITICAL
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.5.0.74
Description This trap indicates that the file system has gone into an unrecoverable read-only state – no disk writes will occur.
Repetition None
Event Codes
sonusAlarmNodeID
sonusAlarmLevel
sonusAlarmTime
Instance Fields
Action Replace the hard disk.
Impact No disk writes will occur.
Clearing Manual
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.5.0.46
Description This trap indicates that the configuration restoration from the specified config file is in progress.
Repetition None

sonusCpSystemConfigFileName
Action None
Impact Configuration is restored from the specified file, and applications on the node restart.
Clearing Manual
This alarm is not currently supported.
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.5.0.71
Description This alarm indicates that the DRBD process is backing up configuration and accounting files in preparation for a DRBD partition
reformat.
Repetition None

sonusAlarmLevel
sonusAlarmTime
Fields
Action None
Impact Preparing for a forced switchover.
Clearing Automatic; sonusCpSystemServerDrbdReformatCompletedNotification
sonusCpSystemServerDrbdReformatCompletedNotify -
MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.5.0.72
Description This alarm indicates DRBD partition format has completed. A full disk sync will start.
Repetition None

sonusAlarmLevel
sonusAlarmTime
Action None
Impact Full DRBD sync is issued.
Clearing Automatic
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.5.0.70
Description This alarm indicates that the DRBD process encountered an error during reconfiguration.
Repetition None

sonusAlarmLevel
sonusAlarmTime
Action Correct the error or wait for the SBC to retry.
Impact None
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.5.0.68
Description This alarm indicates that the DRBD partition is being resized and reformatted to match the peer partition.
Repetition None

sonusAlarmLevel
sonusAlarmTime
Action None
Impact DRBD full sync is issued.
sonusCpSystemServerDrbdReformatSwitchoverNotify -
MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.5.0.69
Description This alarm indicates that the active server has requested the standby to become active, allowing the current active to reconfigure
its DRBD partition.
Repetition None

sonusAlarmLevel
sonusAlarmTime
Fields
Action None
Impact Switchover
Type: CRITICAL
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.5.0.85
Description This alarm indicates the reason for the service restarting. The service restart is required for:
Unknown reason
System restart
System software reset
Switchover
Process abnormal termination
Software upgrade or revert
Management port down
Repetition None

sonusAlarmLevel
sonusAlarmTime
sonusCpSystemApplicationRestartReason

sonusCpSystemApplicationRestartReason
Action Take appropriate action depending on the reason.
Impact Need to understand/analyze reason for restart.
Clearing Manual
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.5.0.4
Description This alarm indicates that the node is active after a soft reboot.
Repetition None
Action None
Impact None
Clearing Manual
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.5.0.3
Description This alarm indicates that the node soft boot is requested.
Repetition None
Action None
Impact Applications on the node will restart.
Clearing Manual
CP Timer Alarms
This section contains the following Call Processor timer-related alarms.
Type: MAJOR
Object 1.3.6.1.4.1.2879.2.10.1.1.7.0.1
ID
Descri The answer supervision timer has expired, indicating that answer message has not been received from the called party. This alarm is
ption used to inform maintenance personnel of the situation so they can decide whether executive action is required to tear the call down.
Repeti None
tion
Event
Codes sonusIngressTgName—Name of ingress Trunk Group.
sonusIngressCep—Ingress circuit end point information (PSTN or IP formatted).
sonusEgressTgName—Name of egress Trunk Group.
sonusEgressCep—Egress circuit end point information (PSTN or IP formatted).
sonusCalledNumber—Called party number.
sonusCallingNumber—Calling party number.
Instan None
ce
Fields
Action None
Impact None
Cleari Manual
ng
Type: MINOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.7.0.2
Description This trap is used to inform that the long duration call timer has expired. The call has been active for the configured timeout period,
and the appropriate action has been taken.
Repetition None
Event
Codes sonusTgName—The name of the Trunk Group.
sonusCepCircuit end point information (PSTN or IP formatted).
sonusStaticCallGcid—The call identifier for a call to be deleted.
sonusCalledNumber—The directory number of the called party.
sonusCallingNumber—The directory number of the calling party.
sonusLdcStatus—Status of the LDC call:
Disconnected—Call is to be released.
Active—Call is to remain active.
Instance None
Fields
Action None
Impact None
Clearing Manual
Database Alarms
This section contains the following Database alarms.
sonusDatabaseConfigPolicyDataInSyncNotification - INFORMATIONAL
sonusDatabaseConfigPolicyDataInSyncNotification - INFORMATIONAL
sonusDatabaseConfigPolicyDataOutOfSyncNotification - CRITICAL
sonusDatabasePolicyDataInSyncNotification - INFORMATIONAL
sonusDatabasePolicyDataOutOfSyncNotification - CRITICAL
sonusDatabaseConfigPolicyDataInSyncNotification -
INFORMATIONAL
Type: INFORMATIONAL
Object ID 1.3.6.1.4.1.2879.2.10.1.1.15.0.2
Description This clearing alarm is triggered once the PostgreSQL (configuration) and CDB (policy) databases are back in sync on the
active SBC.
Repetition None
Event Codes sonusSbxSystemName

sonusSbxServerName
sonusSbxRedundencyRole
Instance None
Fields
Action None
Impact None
Clearing Automatic, sonusDatabaseConfigPolicyDataOutOfSyncNotification
sonusDatabaseConfigPolicyDataOutOfSyncNotification -
CRITICAL
Type: CRITICAL
Object 1.3.6.1.4.1.2879.2.10.1.1.15.0.1
ID
Descript This alarm is generated when the PostgreSQL (configuration) and CDB (policy) databases are out of sync on the active SBC.
ion Manual action is required to clear this. See the Action field below for guidance.
Repetiti None
on
Event sonusSbxSystemName
Codes sonusSbxServerName
sonusSbxRedundencyRole
Instance None
Fields
Action Reload the databases from a known good backup.
Impact The configuration and policy databases are out of sync on the active SBC. The system may not operate as expected.
Clearing Automatic, sonusDatabaseConfigPolicyDataInSyncNotification
sonusDatabasePolicyDataInSyncNotification -
INFORMATIONAL
Type: INFORMATIONAL
Object ID 1.3.6.1.4.1.2879.2.10.1.1.15.0.4
Description This alarm indicates that the policy databases on active and standby are in sync.
Repetition None

sonusSbxServerName
sonusSbxPeerServerName
Action None
Impact None
Clearing Manual
sonusDatabasePolicyDataOutOfSyncNotification - CRITICAL
Type: CRITICAL
Object ID 1.3.6.1.4.1.2879.2.10.1.1.15.0.3
Description This alarm indicates that the policy databases on active and standby are out of sync and manual action is required.
Repetition None

sonusSbxServerName
sonusSbxPeerServerName
Action Investigate the reason and then correct the problem.
Impact Policy databases on active and standby are out of sync and the system may not operate normally.
Clearing Automatic, sonusDatabasePolicyDataInSyncNotification
This section contains the Dialog Transparency Alarm sonusSbxDialogTransparencyMisConfiguredNotification - CRITICAL.
sonusSbxDialogTransparencyMisConfiguredNotification -
CRITICAL
Type: CRITICAL
Object ID 1.3.6.1.4.1.2879.2.10.1.1.1.0.52
Description This alarm is generated when Dialog Transparency parameter is enabled on one zone (either ingress or egress) and
disabled on the other.
Repetition None

sonusAlarmLevel
sonusAlarmTime
sonusZoneName
Instance None
Fields
Action Ensure that the Dialog Transparency parameter is enabled on both ingress and egress zones.
Impact All calls and messages are rejected as dialog transparency is not enabled on both ingress and egress zones.
Clearing Manual
Diameter Alarms
This section contains the following Diameter slarms.
sonusSbxDiamPeerConnectionDown - MAJOR
sonusSbxDiamPeerConnectionUp - MAJOR
sonusSbxDiamPeerConnectionDown - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.22.0.3
Description This alarm or SNMP trap is generated when the connection to a Diameter Peer is detected as lost or broken.
Repetition None

sonusAlarmLevel
sonusAlarmTime
sonusDiamPeerName
sonusDiamPeerIpAddress
Instance Fields sonusDiamPeerName

Action Make sure the Diameter peer is up and running.
Impact Diameter messages are not sent.
Clearing Automatic; sonusSbxDiamPeerConnectionUp
sonusSbxDiamPeerConnectionUp - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.22.0.4
Description This alarm or SNMP trap is generated when the connection to a Diameter Peer is restored.
Repetition None

sonusAlarmLevel
sonusAlarmTime
sonusDiamPeerName
Instance Fields sonusDiamPeerName

Action None
Impact Diameter messages are sent.
Clearing Automatic
sonusSbxCcsClusterDownNotification - MAJOR
sonusSbxCcsClusterUpNotification - MAJOR
sonusSbxDsbcClusterAllSeedNodesUnreachable - MAJOR
sonusSbxDsbcClusterFqdnResolutionFailure - MAJOR
sonusSbxDsbcClusterFqdnResolutionSuccess - MAJOR
sonusSbxDsbcClusterLeaderDiscoveryInProgress - MAJOR
sonusSbxDsbcClusterLeaderDiscoveryInProgressV6 - MAJOR
sonusSbxDsbcClusterLeaderRetrievalCompleted - MAJOR
sonusSbxDsbcClusterLeaderRetrievalCompletedV6 - MAJOR
sonusSbxDsbcControlChanCloseNotification - MAJOR
sonusSbxDsbcControlChanCloseNotificationV6 - MAJOR
sonusSbxDsbcControlChanOpenAttemptNotification - MAJOR
sonusSbxDsbcControlChanOpenAttemptNotificationV6 - MAJOR
sonusSbxDsbcControlChanOpenNotification - MAJOR
sonusSbxDsbcControlChanOpenNotificationV6 - MAJOR
sonusSbxDsbcControlChanRetryTimerExpiredNotification - MAJOR
sonusSbxDsbcControlChanRetryTimerExpiredNotificationV6 - MAJOR
sonusSbxDsbcFaultCallsReleasedClear - MAJOR
sonusSbxDsbcFaultCallsReleasedClearV6 - MAJOR
sonusSbxDsbcFaultCallsReleased - MAJOR
sonusSbxDsbcFaultCallsReleasedV6 - MAJOR
sonusSbxDsbcNodeAllocationFailureClear- MAJOR
sonusSbxDsbcNodeAllocationFailureClearV6 - MAJOR
sonusSbxDsbcNodeAllocationFailure - MAJOR
sonusSbxDsbcNodeAllocationFailureV6 - MAJOR
sonusSbxDsbcNodeCongestedClear - MAJOR
sonusSbxDsbcNodeCongestedClearV6 - MAJOR
sonusSbxDsbcNodeCongested - MAJOR
sonusSbxDsbcNodeCongestedV6 - MAJOR
sonusSbxCcsClusterDownNotification - MAJOR
Type: MAJOR
Object 1.3.6.1.4.1.2879.2.10.1.1.27.0.1
ID
Descrip The alarm indicates the cluster is down and the SBC is unable to communicate and discover other nodes in the cluster. Any SBC
tion functionality that make use of this information does not function until communication is restored.
Repetiti None
on
Event
sonusAlarmLevel
Instanc
e Fields sonusAlarmTime
sonusNrsCeName
Action Determine the reason for communications failure with other nodes and correct it.
Impact Any services that rely on cluster communications are not available.
Clearing Automatic; sonusSbxCcsClusterUpNotification
sonusSbxCcsClusterUpNotification - MAJOR
Type: MAJOR
Object 1.3.6.1.4.1.2879.2.10.1.1.27.0.2
ID
Descri The alarm indicates that the SBC is able to discover other nodes in the same VNF cluster and communicate with them using the
ption Membership and Broadcast Service (MBS) subsystem. Functionalities of the SBC that make use of this information function as
expected.
Repeti None
tion
Event
sonusAlarmLevel
Instan
ce sonusAlarmTime
Fields sonusAlarmDescription
sonusNrsCeName
Action None
Impact Services that rely on cluster communications are available
Cleari Manual
ng
sonusSbxDsbcClusterAllSeedNodesUnreachable - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.25.0.11
Description This alarm indicates that all seed nodes for this cluster FQDN are unreachable.
Repetition Repeats until at least one configured seed node on the DNS for configured cluster FQDN is reachable.

sonusAlarmLevel
sonusAlarmTime
sonusDsbcClusterFqdn
sonusDsbcClusterType
Instance Fields sonusDsbcClusterFqdn

Action Calls requiring this cluster’s resources are rejected.
Impact The cluster is not usable for hosting calls.
Clearing Automatic;
sonusSbxDsbcClusterLeaderRetrievalCompleted (IPv4 cluster address type)

sonusSbxDsbcClusterLeaderRetrievalCompletedV6 (IPv6 cluster address type)
sonusSbxDsbcClusterFqdnResolutionFailure - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.25.0.9
Description This alarm indicates that all FQDN resolution attempts failed for this cluster.
Repetition Repeats until configured cluster FQDN is successfully resolved for at least one seed node configured at the DNS server.

sonusAlarmLevel
sonusAlarmTime

Action Calls requiring this cluster’s resources are rejected.
Impact The cluster is not usable for hosting calls.
Clearing Automatic; sonusSbxDsbcClusterFqdnResolutionSuccess
sonusSbxDsbcClusterFqdnResolutionSuccess - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.25.0.10
Description This alarm indicates that FQDN resolution succeeded for this cluster.
Repetition N/A

sonusAlarmLevel
sonusAlarmTime

Action N/A
Impact N/A
Clearing Manual
sonusSbxDsbcClusterLeaderDiscoveryInProgress - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.25.0.12
Description This alarm indicates that the specified seed node for this cluster is reached, and leader discovery is in progress.
Repetition Repeats until the cluster leader node discovery is successful.

sonusAlarmLevel
sonusAlarmTime
sonusDsbcRemoteDsbcAddr

Action Call resource requests are buffered until cluster leader node retrieval is successful.
Impact Calls will fail if cluster leader node discovery does not occur in a timely fashion (typically within one second).
Clearing Automatic; sonusSbxDsbcClusterLeaderRetrievalCompleted
sonusSbxDsbcClusterLeaderDiscoveryInProgressV6 -
MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.25.0.13
Description This alarm indicates the specified seed node for this cluster is reached, and leader discovery is in progress (IPv6).
Repetition Repeats until cluster leader node discovery is successful.

sonusAlarmLevel
sonusAlarmTime
sonusDsbcRemoteDsbc6Addr

Action Call resource requests are buffered until the cluster leader node retrieval is successful.
Impact Calls will fail if cluster leader node discovery does not occur in a timely fashion (typically within one second).
Clearing Automatic; sonusSbxDsbcClusterLeaderRetrievalCompletedV6
sonusSbxDsbcClusterLeaderRetrievalCompleted - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.25.0.14
Description This alarm indicates that the specified seed node for this cluster is reached, and leader retrieval completed successfully.
Repetition N/A

sonusAlarmLevel
sonusAlarmTime

Action N/A
Impact N/A
Clearing Manual
sonusSbxDsbcClusterLeaderRetrievalCompletedV6 - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.25.0.15
Description This alarm indicates that the specified seed node for this cluster is reached, and leader retrieval completed successfully (IPv6).
Repetition N/A

sonusAlarmLevel
sonusAlarmTime

Action N/A
Impact N/A
Clearing Manual
sonusSbxDsbcControlChanCloseNotification - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.25.0.2
Description This alarm indicates that a Control Channel Link to a Remote D-SBC is closed.
Repetition This alarm occurs each time the D-SBC control channel is closed. The data includes the remote IP address and port.

sonusAlarmLevel
sonusAlarmTime
sonusDsbcCloseReasonCode: Reason for the closure of the Control Channel Link
administratorInitiatedClose(1)
closeRequestReceivedFromRemote(2)
remoteNotResponding(3)
internalError(4)
configError(5)
recvCallSigReqFromUnknownGw(6)
socketErrNetworkDown(7)
socketErrNetworkUnreachable(8)
socketErrNetworkReset(9)
socketErrSoftwareConnectionAbort(10)
socketErrConnectionResetByPeer(11)
socketErrNoBufferSpaceAvail(12)
socketErrAlreadyConnected(13)
socketErrNotConnected(14)
socketErrCantSendAfterShutdown(15)
socketErrTooManyReferences(16)
socketErrConnectionTimedOut(17)
socketErrUnknown(18)
recvDuplicateLinkOpenReq(19)
socketErrExceptionEvent(20)
linkXmtCongestion(21)
openNackReceivedFromRemote(22)
idleTimeOut(23)
Instance Fields sonusDsbcRemoteDsbcAddr

sonusDsbcCloseReasonCode
Action Check connectivity for any link issues.
Impact This condituion may impact calls if the Control Channel link is not established.
Clearing Manual
sonusSbxDsbcControlChanCloseNotificationV6 - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.25.0.8
Description This alarm indicates that the specified IPv6 Control Channel Link to a remote D-SBC node has closed.
Repetition Occurs when the D-SBC control channel link open request is sent. Alarm data includes the remote IP and port.

sonusAlarmLevel
sonusAlarmTime
internalError(4)
configError(5)
idleTimeOut(23)
Instance Fields sonusDsbcRemoteDsbc6Addr

Impact This condition may impact calls if the control channel link does not re-establish.
Clearing Manual
sonusSbxDsbcControlChanOpenAttemptNotification -
MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.25.0.3
Description This alarm indicates that a request to open a Control Channel IPv4 link was sent to a remote D-SBC.

sonusAlarmLevel
sonusAlarmTime
Action No action needed
Impact No adverse impact
Clearing Manual
sonusSbxDsbcControlChanOpenAttemptNotificationV6 -
MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.25.0.6
Description This alarm indicates that a request to open a Call Signaling IPv6 link was sent to a remote D-SBC.

sonusAlarmLevel
sonusAlarmTime
Clearing Manual
sonusSbxDsbcControlChanOpenNotification - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.25.0.1
Description This alarm indicates that the specified Control Channel IPv4 link to a remote D-SBC successfully opened.
Repetition Occurs when a D-SBC control channel open ACK is sent or received. The alarm data includes the remote IP and port.

sonusAlarmLevel
sonusAlarmTime
Clearing Manual
sonusSbxDsbcControlChanOpenNotificationV6 - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.25.0.5
Description This alarm indicates that a Call Signaling IPv6 link to a remote D-SBC is successfully opened.
Repetition Occurs when D-SBC control channel open ACK is sent or received. The alarm data includes the remote IP and port.

sonusAlarmLevel
sonusAlarmTime
Clearing Manual
sonusSbxDsbcControlChanRetryTimerExpiredNotification -
MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.25.0.4
Description This alarm indicates that attempts to recover a Control Channel Link to a remote D-SBC is failed.
Repetition Occurs when D-SBC control channel link retry timer expires. Data included remote IP and port.

sonusAlarmLevel
sonusAlarmTime
Impact Calls may be impacted if the control channel link cannot be established.
Clearing Manual
sonusSbxDsbcControlChanRetryTimerExpiredNotification
sonusSbxDsbcControlChanRetryTimerExpiredNotificationV6
- MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.25.0.7
Description This alarm indicates that attempts to recover a Call Signaling IPV6 Link to a Remote D-SBC have failed.
Repetition Occurs when D-SBC control channel link retry timer expires. Data included remote IP and port.

sonusAlarmLevel
sonusAlarmTime

Impact Calls may be impacted if the control channel link cannot be established.
Clearing Manual
sonusSbxDsbcFaultCallsReleasedClear - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.25.0.17
Description This alarm clears the D-SBC network fault call drop trap.
Repetition N/A

sonusAlarmLevel
sonusAlarmTime
sonusDsbcCallsReleasedReasonCode
Instance Fields sonusDsbcCallsReleasedReasonCode

sonusDsbcCallsReleasedCount
Action N/A
Impact N/A
Clearing Manual
sonusSbxDsbcFaultCallsReleasedClearV6 - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.25.0.19
Description This alarmclears the D-SBC network fault call drop trap.
Repetition N/A

sonusAlarmLevel
sonusAlarmTime

Action N/A
Impact N/A
Clearing Manual
sonusSbxDsbcFaultCallsReleased - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.25.0.16
Description This alarm indicates that a D-SBC network fault has resulted in calls being dropped.
Repetition Singular alarm resulting in the release of the indicated number of calls at the specified remote node.

sonusAlarmLevel
sonusAlarmTime

Action Calls dropped.
Impact Existing calls dropped, service impact may be ongoing until network fault condition is remedied.
Clearing Automatic; sonusSbxDsbcFaultCallsReleasedClear
sonusSbxDsbcFaultCallsReleasedV6 - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.25.0.18
Description This alarm indicates that a D-SBC network fault has resulted in calls being dropped.
Repetition Singular alarm resulting in the release of the indicated number of calls at the specified remote node.

sonusAlarmLevel
sonusAlarmTime

Action Investigate D-SBC network fault condition. Contact Ribbon Global Product Support (GPS) if required.
Impact Existing calls dropped, service impact may be ongoing until network fault condition is remedied.
Clearing Automatic; sonusSbxDsbcFaultCallsReleasedClearV6
sonusSbxDsbcNodeAllocationFailureClear- MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.25.0.25
Description This alarm confirms the M-SBC node allocation failure is cleared.
Repetition None
Event Codes
sonusAlarmNodeID
sonusAlarmLevel
sonusAlarmTime
sonusDsbcAllocFailuresCount
sonusDsbcRemoteDsbcAdd
Instance Fields sonusDsbcAllocFailuresCount, sonusDsbcRemoteDsbcAdd
Action None
Impact The node allocation failure is cleared.
Clearing Manual
sonusSbxDsbcNodeAllocationFailureClearV6 - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.25.0.27
Description This alarm indicates that the M-SBC node allocation failure is cleared (IPv6 network).
Repetition None
Event Codes sonusAlarmNodeID,
sonusAlarmLevel,
sonusAlarmSequenceId,
sonusAlarmTime,
sonusAlarmDescription,
sonusDsbcAllocFailuresCount,
sonusDsbcRemoteDsbc6Add
Action None
Impact Calls are no longer rejected.
Clearing Manual
sonusSbxDsbcNodeAllocationFailure - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.25.0.24
Description This alarm indicates M-SBC node allocation failure(s) occurred.
Repetition The alarm repeats until the M-SBC is able to allocate the resources successfuly.
Event Codes
sonusAlarmNodeID
sonusAlarmLevel
sonusAlarmTime
sonusDsbcRemoteDsbcAdd
Action Calls sent to the M-SBC fail.
Impact The M-SBC node rejects calls.
Clearing Automatic; sonusSbxDsbcNodeAllocationFailureClear
sonusSbxDsbcNodeAllocationFailureV6 - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.25.0.26
Description This alarm indicates that an M-SBC node allocation failure occurred (IPv6 network).
Repetition This alarm repeats until the M-SBC is able to allocate the resources successfully.
sonusAlarmLevel
sonusAlarmTime
Action Calls offered to the M-SBC fail.
Impact The M-SBC node rejects calls.
Clearing Automatic; sonusSbxDsbcNodeAllocationFailureClear
sonusSbxDsbcNodeCongestedClear - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.25.0.21
Description This alarm indicates that the D-SBC node congestion condition has cleared.
Repetition None

sonusAlarmLevel
sonusAlarmTime
Action None
Impact Restores full call load to the previously congested node.
Clearing Manual
sonusSbxDsbcNodeCongestedClearV6 - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.25.0.23
Description This alarm confirms the D-SBC node congestion condition cleared (IPv6 network).
Repetition None

sonusAlarmLevel
sonusAlarmTime
Action None
Impact Restores full call load to the previously congested node.
Clearing Manual
sonusSbxDsbcNodeCongested - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.25.0.20
Description This alarm indicates that the D-SBC node reported congestion failure.
Repetition A single alarm is reported, and will remain until the remote node congestion condition clears.

sonusAlarmLevel
sonusAlarmTime
Action The call load to congested node is reduced.
Impact The call load to non-congested nodes is increased.
Clearing Automatic; sonusSbxDsbcNodeCongestedClear
sonusSbxDsbcNodeCongestedV6 - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.25.0.22
Description This alarm indicates that a D-SBC node reported a congestion failure (IPv6 networks).
Repetition A single alarm is reported, and will remain until the remote node congestion condition clears.

sonusAlarmLevel
sonusAlarmTime
Action Call load to congested node is reduced.
Impact Call load to non-congested nodes increases.
Clearing Automatic; sonusSbxDsbcNodeCongestedClearV6
This section contains the following Domain Name Server (DNS) alarms.
sonusSbxDnsServerBlacklistedNotification - CRITICAL
sonusSbxDnsServerEdnsFailureNotification - CRITICAL
sonusSbxDnsServerRecoveredNotification - CRITICAL
sonusSbxRcodeErrorClearNotification - MINOR
sonusSbxRcodeErrorClearNotificationV6 - MINOR
sonusSbxRcodeErrorOnDnsQuery - MINOR
sonusSbxRcodeErrorOnDnsQueryV6 - MINOR
sonusSbxDnsServerBlacklistedNotification - CRITICAL
Type: CRITICAL
Object ID 1.3.6.1.4.1.2879.2.10.1.1.23.0.1
Description This alarms is raised when DNS server consistently fails to send a response to SBC DNS request. DNS Server is moved to
Blacklisted state.
Repetition Yes

sonusAlarmLevel
sonusAlarmTime
sonusDnsServerIp
sonusDnsServerPortNum
sonusDnsServerTransport
Instance sonusDnsServerIp
Fields sonusDnsServerPortNum
Action Bypass DNS server for further DNS queries until it is no longer blacklisted.
Impact DNS server is blacklisted and not available for use.
Clearing Automatic; sonusSbxDnsServerRecoveredNotification
sonusSbxDnsServerEdnsFailureNotification - CRITICAL
Type: CRITICAL
Object ID 1.3.6.1.4.1.2879.2.10.1.1.24.0.1
Descripti This alarm is triggered when the SBC receives one of the following errors against a EDNS query from the DNS server:
on
NOT_IMPLEMENTED
FORMAT_ERR
SERVER_FAILURE
Repetition No
Event
sonusAlarmLevel
sonusAlarmTime
sonusDnsServerIp
Instance sonusDnsServerIp
Fields
Action Do one of the following to avoid receiving this alarm:
Bypass the DNS server to prevent further eDNS queries.

Set the DNS Group flag, dnsFallback, to “disabled” to send an EDNS request towards the DNS server irrespective of any DNS
failure response. For configuration details, refer to DNS Group - CLI.
Impact The DNS Server is barred for future eDNS queries.
Clearing Manual
sonusSbxDnsServerRecoveredNotification - CRITICAL
Type: CRITICAL
Object ID 1.3.6.1.4.1.2879.2.10.1.1.23.0.2
Description This alarms is raised when SBC has recovered from blacklisted state.
Repetition Yes

sonusAlarmLevel
sonusAlarmTime
sonusDnsServerIpAddress
sonusDnsServerPortNum
Action Resume using DNS server for DNS queries.
Impact DNS server is removed from blacklisted state.
Clearing Automatic; sonusSbxDnsServerBlacklistedNotification
sonusSbxRcodeErrorClearNotification - MINOR
Type: MINOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.23.0.4
Description The DNS Server RCODE monitor interval errors are cleared.
Repetition No
Event Codes
sonusAlarmNodeID
sonusAlarmLevel
Instance Fields
sonusAlarmTime
sonusDnsIpAddr
Action None
Impact None
Clearing Automatic; sonusSbxRcodeErrorOnDnsQuery
sonusSbxRcodeErrorClearNotificationV6 - MINOR
Type: MINOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.23.0.6
Description The DNS Server IPv6 RCODE monitor interval errors are cleared.
Repetition No
Event Codes
sonusAlarmNodeID
sonusAlarmLevel
Instance Fields
sonusAlarmTime
sonusDnsIpAddr
Action None
Impact None
Clearing Automatic; sonusSbxRcodeErrorOnDnsQueryV6
sonusSbxRcodeErrorOnDnsQuery - MINOR
Type: MINOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.23.0.3
Description The DNS Server has encountered an RCODE error.
Repetition No
Event Codes
sonusAlarmNodeID
sonusAlarmLevel
Instance Fields
sonusAlarmTime
sonusDnsServerZoneId
sonusDnsIpAddr
sonusDomainName
sonusRecordType
sonusRcodeError
sonusDnsServerType
Action Fix the DNS Server for the RCODE error for the FQDN and record type listed.
Impact None
Clearing Automatic; sonusSbxRcodeErrorClearNotification
sonusSbxRcodeErrorOnDnsQueryV6 - MINOR
Type: MINOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.23.0.5
Description The DNS IPv6 server has encountered an RCODE error.
Repetition No
Event Codes
sonusAlarmNodeID
sonusAlarmLevel
Instance Fields
sonusAlarmTime
sonusDnsServerZoneId
sonusDnsIpAddr
sonusDomainName
sonusRecordType
sonusRcodeError
sonusDnsServerType
Action Fix the DNS Server for the RCODE error for the FQDN and record type listed.
Impact None
Clearing Automatic; sonusSbxRcodeErrorClearNotificationV6
This section contains the following DSP Availability alarms.
sonusSbxCallFailureNoDspExceedThresholdNotification - MAJOR
sonusSbxDspAvailG711OnSetCrossThresholdNotification - MAJOR
sonusSbxDspAvailG711PacketAbateCrossThresholdNotification - MAJOR
sonusSbxDspAvailG726AbateCrossThresholdNotification - MAJOR
sonusSbxDspAvailG729AbateCrossThresholdNotification - MAJOR
sonusSbxDspCardOrDeviceFailureNotificationClear - CRITICAL
sonusSbxDspCardOrDeviceFailureNotification - CRITICAL
sonusSbxDspFpgaVersionCheckFailureNotification - MAJOR
sonusSbxGpuCodecThresholdNotificationClear - MAJOR
sonusSbxGpuCodecThresholdNotification - MAJOR
sonusSbxSingleDspReloadAndCoreDumpNotification - MAJOR
sonusSbxCallFailureNoDspExceedThresholdNotification -
MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.4.0.11
Description This trap indicates the configured call failure threshold value was exceeded due to lack of DSP resources.
Repetition None
Event Codes
sonusAlarmNodeID
sonusAlarmLevel
sonusAlarmTime
Instance sonusNumCallFailureNoDspExceedThreshold – The number of times a call fails due to lack of DSP resources since the last
Fields alarm notification.
Action Add DSP resources.
Impact The calls fail.
Clearing Manual
sonusSbxDspAvailG711OnSetCrossThresholdNotification -
MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.4.0.14
Description Indicates the system DSP availability descended below the G711 Packet DSP threshold level (crossed below the
threshold).
Repetition None
Event Codes
sonusAlarmNodeID
sonusAlarmLevel
sonusAlarmTime
Instance sonusNumDspAvailabilityG711PacketCrossThreshold
Fields
Action Ensure G711 Packet DSP availability.
Impact Calls may fail.
Clearing Automatic; sonusSbxDspAvailG711PacketAbateCrossThresholdNotification
sonusSbxDspAvailG711PacketAbateCrossThresholdNotification - M
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.4.0.17
Description Indicates the system DSP availability rose above the G711 Packet DSP threshold level (crossed above the threshold). This
trap clears the
sonusSbxDspAvailG711OnSetCrossThresholdNotification trap.
Repetition None
Event Codes
sonusAlarmNodeID
sonusAlarmLevel
sonusAlarmTime
Instance sonusSbxDspAvailG711PacketAbateCrossThresholdNotification
Fields
Action None
Impact System DSP resources are now available as required.
Clearing Automatic; sonusSbxDspAvailG711OnSetCrossThresholdNotification
MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.4.0.13
Description Indicates that the system DSP availability descended below the G726 Packet DSP threshold level (crossed below the
threshold).
Repetition None
Event Codes
sonusAlarmNodeID
sonusAlarmLevel
sonusAlarmTime
Instance sonusNumDspAvailabilityG726CrossThreshold
Fields
Clearing Automatic; sonusSbxDspAvailG726AbateCrossThresholdNotification
sonusSbxDspAvailG726AbateCrossThresholdNotification -
MAJOR
Type: MAJOR
Object 1.3.6.1.4.1.2879.2.10.1.1.4.0.16
ID
Descript Indicates the system DSP availability rose above the G711 Packet DSP threshold level (crossed above the threshold). This alarm
ion clears the sonusSbxDspAvailG726OnSetCrossThresholdNotification alarm.
Repetiti None
on
Event
sonusAlarmLevel
sonusAlarmTime
Instance sonusSbxDspAvailG726AbateCrossThresholdNotification
Fields
Action None
Impact The DSP resource is now available.
MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.4.0.12
Description Indicates the system DSP availability descended below the G729 Packet DSP threshold level (crossed below the
threshold).
Repetition None
Event Codes
sonusAlarmNodeID
sonusAlarmLevel
sonusAlarmTime
Instance sonusNumDspAvailabilityG729CrossThreshold
Fields
Clearing Automatic; sonusSbxDspAvailG729AbateCrossThresholdNotification
sonusSbxDspAvailG729AbateCrossThresholdNotification -
MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.4.0.15
Description Indicates that the system DSP availability rose above the G729 Packet DSP threshold level (crossed above the threshold).
This alarm clears the sonusSbxDspAvailG729OnSetCrossThresholdNotification.
Repetition None
Event Codes
sonusAlarmNodeID
sonusAlarmLevel
sonusAlarmTime
Instance Fields sonusSbxDspAvailG729AbateCrossThresholdNotification
Action None
Impact The DSP resource is now available.
sonusSbxDspCardOrDeviceFailureNotificationClear -
CRITICAL
Note
Currently, the SBC does not support this alarm.
Type: CRITICAL
Object ID 1.3.6.1.4.1.2879.2.10.1.1.4.0.50
Description This alarm indicates that a DSP device or card failure is cleared.
Repetition None

sonusAlarmLevel
sonusAlarmTime
Action None
Impact None
Clearing Manual
sonusSbxDspCardOrDeviceFailureNotification - CRITICAL
Type: CRITICAL
Object ID 1.3.6.1.4.1.2879.2.10.1.1.4.0.49
Description This trap identifies and indicates a fatal DSP device or card failure.
Repetition None

sonusAlarmLevel
sonusAlarmTime
Action The SBC restarts.
Impact The SBC restarts and switches over to a standby SBC if an HA configuration is available.
Clearing Manual
sonusSbxDspFpgaVersionCheckFailureNotification - MAJOR
This alarm is supported only on SBC 5110, SBC 5210 and SBC 7000.
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.4.0.43
Description This trap is generated when the FPGA version on the DSP card is less than the minimum required. (Min FPGA Version for
DSP2x: 0x14 and for DSP-LC 0x16).
Repetition None
sonusAlarmTime
Instance None
Fields
Action Upgrade FPGA on the DSP card to the required version. Refer to MOP to Upgrade SBC 7000 DSP-LC FPGA, for details.
Impact The DSP card is disabled.
Clearing Manual
sonusSbxGpuCodecThresholdNotificationClear - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.4.0.52
Description This alarm indicates that the compression DSP resource usage for GPU-supported codec dropped below the threshold
limit.
Repetition None
Event Codes
sonusAlarmNodeID
sonusAlarmLevel
Instance
sonusThresholdCrossingCodec
Action None
Impact None
Clearing None
Note
This alarm is no longer asserted.
sonusSbxGpuCodecThresholdNotification - MAJOR
Type: MAJOR
Object 1.3.6.1.4.1.2879.2.10.1.1.4.0.51
ID
Descri This alarm indicates that the compression DSP resource usage for certain GPU-supported codecs crossed the threshold value. The
ption default Universal Compression threshold value is 90% by default. To modify the threshold, refer to DSP PAD Resources - CLI.
Repeti None
tion
Event
sonusAlarmLevel
Instan
ce sonusAlarmTime
sonusThresholdCrossingCodec
Action Increase, if possible, compression DSP resources for the corresponding GPU-supported codec.
Impact May impact new transcoded calls on the GPU.
Cleari Automatic; sonusSbxGpuCodecThresholdNotificationClear

ng
Note
This alarm is no longer asserted.
sonusSbxSingleDspReloadAndCoreDumpNotification -
MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.4.0.38
Description This trap indicates that a DSP core-dump was collected after a single DSP failure and subsequent successful reload.
Repetition None
Event Codes None
Instance None
Fields
Action None
Impact The SBC successfully reloaded a failed DSP, restored active channels (if any) and collected a core dump in the background of
the DSP failure event.
Clearing Manual
This section contains the following Dynamic Blacklist alarms.
sonusSbxDBLActionEndpointInfoNotification - MAJOR
sonusSbxDBLActionMajorNotification - MAJOR
sonusSbxDBLClearActionEndpointInfoNotification - MAJOR
sonusSbxDBLClearActionMajorNotification - MAJOR
sonusSbxDBLEnhActionClearNotification - MINOR
sonusSbxDBLEnhActionSetNotification - MINOR
sonusSbxDBLActionEndpointInfoNotification - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.9.0.8
Description This alarm indicates that action has been taken on the endpoint due to
the DBL enforcement.
Repetition None

sonusAlarmLevel
sonusAlarmTime
sonusDBLAddressContextName
sonusDBLEndPointInfo
sonusDBLAction
sonusDBLDuration
sonusDBLCriteria
sonusDBLProfileRuleInfo
Instance Fields sonusDBLAddressContextName

sonusDBLAction
sonusDBLDuration
sonusDBLCriteria
Action N/A
Impact Endpoint is blacklisted or request are rejected.
Clearing Automatic; sonusSbxDBLClearActionEndpointInfoNotification
sonusSbxDBLActionMajorNotification - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.9.0.4
Description This trap indicates one or more DBL entries exist in the system.
Repetition None
Event Codes sonusDBLAddressContextName – AddressContext name.
Action None
Impact None
Clearing Automatic, sonusSbxDBLClearActionMajorNotification
sonusSbxDBLClearActionEndpointInfoNotification - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.9.0.9
Description The alarm notifies the user that the DBL enforcement action on the endpoint is now cleared.
Repetition None

sonusAlarmLevel
sonusAlarmTime
sonusDBLAction
sonusDBLDuration
sonusDBLCriteria

sonusDBLAction
sonusDBLDuration
sonusDBLCriteria
Action Clears the trap sonusSbxDBLActionEndpointInfoNotification.
Impact Endpoint is now released from DBL enforcement.
Clearing Manual
sonusSbxDBLClearActionMajorNotification - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.9.0.5
Description This trap indicates there are no longer any DBL entries in the system.
Repetition None
Event Codes
sonusAlarmNodeID
sonusAlarmLevel
sonusAlarmTime
Action None
Impact None
Clearing Automatic; sonusSbxDBLActionMajorNotification
sonusSbxDBLEnhActionClearNotification - MINOR
Type: MINOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.9.0.7
Description This alarm is raised when the SBC recovers an endpoint from the enhanced DBL action.
Repetition N/A

sonusAlarmLevel
sonusAlarmTime
sonusDBLAction
sonusDBLDuration
sonusDBLCriteria

sonusDBLAction
sonusDBLDuration
sonusDBLCriteria
Action Clears the trap sonusSbxDBLEnhActionSetNotification.
Impact Endpoint is released from the enhanced DBL enforcement.
Clearing Manual
sonusSbxDBLEnhActionSetNotification - MINOR
Type: MINOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.9.0.6
Description This alarm is raised when the SBC takes an action on the endpoint based on the enhanced DBL enforcement.
Repetition N/A

sonusAlarmLevel
sonusAlarmTime
sonusDBLAction
sonusDBLDuration
sonusDBLCriteria

sonusDBLAction
sonusDBLDuration
sonusDBLCriteria
Action Remove the endpoint entry from the respective action manually or wait till the effective period for action expires.
Impact Endpoint is blacklisted or requests are rejected.
Clearing Automatic; sonusSbxDBLEnhActionClearNotification
This section contains the following Gateway Signaling alarms.
sonusSbxGwSigChanCloseNotification - MAJOR
sonusSbxGwSigChanCloseNotificationV6 - MAJOR
sonusSbxGwSigChanOpenAttemptNotification - MINOR
sonusSbxGwSigChanOpenAttemptNotificationV6 - MINOR
sonusSbxGwSigChanOpenNotification - MAJOR
sonusSbxGwSigChanOpenNotificationV6 - MAJOR
sonusSbxGwSigChanRetryTimerExpiredNotification - MINOR
sonusSbxGwSigChanRetryTimerExpiredNotificationV6 - MINOR
sonusSbxGwSigTrunkGroupOutOfServiceNotification - MAJOR
sonusSbxGwTrunkGroupInServiceNotification - MINOR
sonusSbxGwSigChanCloseNotification - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.13.0.2
Description This alarm indicates that a Call Signaling Link to a Remote Gateway has closed.
Repetition None
Event Codes
sonusGwRemoteGwAddr
sonusGwCloseReasonCode - Reason for close of Call Signaling Link:
internalError(4)
configError(5)
idleTimeOut(23)
Action None
Impact None
Clearing Automatic, sonusSbxGwSigChanOpenNotification
sonusSbxGwSigChanCloseNotificationV6 - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.13.0.10
Description This alarm indicates that a Call Signaling Link to a Remote Gateway has been closed.
Repetition None
Event Codes sonusGwRemoteGw6Addr-IP address of the remote Gateway.

sonusGwCloseReasonCode-Reason for close of Call Signaling Link:
internalError(4)
configError(5)
idleTimeOut(23)
Action None
Impact None
Clearing Automatic, sonusSbxGwSigChanOpenNotificationV6
sonusSbxGwSigChanOpenAttemptNotification - MINOR
Type: MINOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.13.0.3
Description This trap indicates that a request to Open a Call Signaling Link has been sent to a Remote Gateway.
Repetition None
Event Codes sonusGwRemoteGwAddr
Action None
Impact None
sonusSbxGwSigChanOpenAttemptNotificationV6 - MINOR
Type: MINOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.13.0.8
Description This alarm indicates that a request to Open a Call Signaling Link has been sent to a Remote Gateway.
Repetition None
Event Codes sonusGwRemoteGw6Addr
Action None
Impact None
sonusSbxGwSigChanOpenNotification - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.13.0.1
Description This alarm indicates that a Call Signaling Link to a Remote Gateway has successfully opened.
Repetition None
Action None
Impact None
Clearing Manual
sonusSbxGwSigChanOpenNotificationV6 - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.13.0.7
Description This alarm indicates that a Call Signaling Link to a Remote Gateway has been successfully opened.
Repetition None
Action None
Impact None
Clearing Manual
sonusSbxGwSigChanRetryTimerExpiredNotification - MINOR
Type: MINOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.13.0.4
Description This alarm indicates that attempts to recover a Call Signaling Link to a Remote GW have failed.
Repetition None
Action None
Impact None
sonusSbxGwSigChanRetryTimerExpiredNotificationV6 -
MINOR
Type: MINOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.13.0.9
Description This alarm indicates that attempts to recover a Call Signaling Link to a Remote GW have failed.
Repetition None
Action None
Impact None
sonusSbxGwSigTrunkGroupOutOfServiceNotification -
MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.13.0.6
Description This alarm indicates that the Gateway Trunk Group was taken out of service by maintenance staff.
Repetition None
Event Codes sonusGwSigTgName
Action None
Impact None
Clearing Automatic, sonusSbxGwTrunkGroupInServiceNotification
sonusSbxGwTrunkGroupInServiceNotification - MINOR
Type: MINOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.13.0.5
Description This alarm indicates that the Gateway Trunk Group was put into service by maintenance staff.
Repetition None
Event Codes sonusGwSigTgName
Action None
Impact None
Clearing Manual
GETS and WPS Alarms

This section contains the following GETS and WPS alarms:
sonusHpcCallNoLicenseNotification - MAJOR
sonusHpcLimitHighIngressCallRateNotification - INFORMATIONAL
sonusHpcLimitHighSimultaneousCallsNotification - INFORMATIONAL
sonusHpcCallNoLicenseNotification - MAJOR
Type: MAJOR
Object 1.3.6.1.4.1.2879.2.10.1.1.31.0.1
ID
Descri This alarm indicates that an HPC call is attempted without HPC license. The call proceeds as a normal call and the SBC does not
ption treat it as an HPC call. This alarm warns the operator to purchase an HPC license so that the HPC calls have priority treatment.
Repeti Yes. This alarm repeats any time the SBC attempts an HPC call. There is a minimum of an hour between alarm.
tion
Event
sonusAlarmLevel
sonusAlarmTime
Instan
ce sonusAlarmLevel
Action Purchase an HPC license.
Impact The SBC does not process the attempted HPC calls with priority.
Cleari Manual.
ng
sonusHpcLimitHighIngressCallRateNotification -
INFORMATIONAL
Type: INFORMATIONAL
Object ID 1.3.6.1.4.1.2879.2.10.1.1.30.0.1
Descripti This alarm indicates that the HPC call rate exceeded the HPC ingress call rate limit value on HPC Limit <Peer_Name or
on Peer_IP_Address>, and reports the number of denied attempts.
Repetition Yes. This alarm repeats once for each occurrence.
Event None
Codes
Instance Limit Entry Name

Fields
Action None
Impact The SBC does not complete the reported number of denied HPC attempts.
Clearing Manual
sonusHpcLimitHighSimultaneousCallsNotification -
INFORMATIONAL
Type: INFORMATIONAL
Object ID 1.3.6.1.4.1.2879.2.10.1.1.30.0.2
Descripti This alarm indicates that the HPC calls exceeded the Simultaneous HPC calls limit value on HPC Limit <Peer_Name or
on Peer_IP_Address>, and reports the number of denied attempts.
Repetition Yes. This alarm repeats once for each occurrence.
Event None
Codes
Instance Limit Entry Name

Fields
Action None
Impact The SBC does not complete the reported number of denied HPC attempts.
Clearing Manual
H248 Alarms
Note
Not applicable to the SBC Software Edition (SWe).
This section contains H248 notifications.
Topic include:
sonusH248SigPortCloseNotification - MAJOR
sonusH248SigPortOpenNotification - MAJOR
sonusH248ScFailoverTxNotification - INFORMATIONAL
sonusH248ScFailoverTxStatusNotification - INFORMATIONAL
sonusH248ScHandoffRxNotification - INFORMATIONAL
sonusH248FeatureEnableNotification - INFORMATIONAL
sonusH248ScDisconnectedTxNotification - INFORMATIONAL
sonusH248ScNotificationClear - MAJOR
sonusH248VMGtermNoRTPRcvdThresholdExceeded - MAJOR
sonusH248ClearVMGtermNoRTPRcvdThresholdExceeded - MAJOR
sonusH248SigPortCloseNotification - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.12.0.14
Description This alarm indicates that a call signaling port is closed.
Repetition None
Event Codes
sonusAlarmNodeID
sonusAlarmLevel
Instance Fields
sonusAlarmTime
sonusH248SigPortIpAddress
sonusH248SigPortNum
sonusH248SigScMethod
Action None
Impact None
Clearing Automatic, sonusH248SigPortOpenNotification
sonusH248SigPortOpenNotification - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.12.0.13
Description This alarm indicates that a H248 signaling port is opened.
Repetition None
Event Codes
sonusAlarmNodeID
sonusAlarmLevel
Instance Fields
sonusAlarmTime
sonusH248SigPortIpAddress
sonusH248SigPortNum
Action None
Impact None
Clearing Manual
sonusH248ScFailoverTxNotification - INFORMATIONAL
Type: INFORMATIONAL
Object ID 1.3.6.1.4.1.2879.2.10.1.1.12.0.4
Description This alarm indicates that the Service change Failover is transmitted.
Repetition None
Event Codes
sonusAlarmNodeID
sonusAlarmLevel
Instance Fields
sonusAlarmTime
sonusH248SigRemoteIpAddr
sonusH248SigLocalIpAddr
sonusH248SigMid
Action None
Impact Call failures may happen if the VMG association is not established after failover with secondary MGC.
Clearing Automatic; sonusH248ScNotificationClear
sonusH248ScFailoverTxStatusNotification - INFORMATIONAL
Type: INFORMATIONAL
Object ID 1.3.6.1.4.1.2879.2.10.1.1.12.0.3
Description This trap indicates the service change failover transmitted status.
Repetition None
Event Codes
sonusAlarmNodeID
sonusAlarmLevel
Instance
sonusH248SigMid
sonusH248SigStatus
Action None
Impact Calls may fail if the Virtual Media Gateway (VMG) association is not established after failover with secondary Media Gateway
Controller (MGC).
Clearing Automatic; sonusH248ScNotificationClear
sonusH248ScHandoffRxNotification - INFORMATIONAL
Type: INFORMATIONAL
Object ID 1.3.6.1.4.1.2879.2.10.1.1.12.0.5
Descripti This alarm indicates that the service change handoff is received and is cleared automatically by "sonusH248ScNotificationClear"
on notification after the association is established with the secondary MGC.
Repetition None
Event
sonusAlarmLevel
Instance
sonusH248SigMid
Action None
Impact Calls could fail if the VMG association is not established after handoff with the secondary MGC.
Clearing Automatic; sonusH248ScNotificationClear.
Type: INFORMATIONAL
Object ID 1.3.6.1.4.1.2879.2.10.1.1.12.0.12
Description This alarm indicates the license is enabled to access H.248 features.
Repetition None
Event Codes sonusH248FeatureName
Action None
Impact None
Clearing Manual
sonusH248ScDisconnectedTxNotification - INFORMATIONAL
Type: INFORMATIONAL
Object ID 1.3.6.1.4.1.2879.2.10.1.1.12.0.1
Description This alarm indicates the H.248 service change has disconnected.
Repetition None
Event Codes
sonusAlarmNodeID
sonusAlarmLevel
Instance
sonusH248SigMid
Action None
Impact Whenever a VMG detects inactivity on the MGC-VMG connection, the VMG attempts to re-establish the lost control association
by
sending a ServiceChangeMethod Disconnected. Call Failures may happen until the connection gets re-established properly
Clearing Automatic: sonusH248ScNotificationClear
sonusH248ScNotificationClear - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.12.0.15
Description This alarm generates when the H.248 service connection is reestablished.
Repetition None
Event Codes
sonusAlarmNodeID
sonusAlarmLevel
Instance Fields
sonusAlarmTime
sonusH248SigMid
Action None
Impact None
Clearing Manual
sonusH248VMGtermNoRTPRcvdThresholdExceeded -
MAJOR
Type: MAJOR
Object 1.3.6.1.4.1.2879.2.10.1.1.35.0.1
ID
Descrip The alarm is generated when the maximum threshold for the VMG that specifies the percentage of the total number of terminations
tion that did not receive any RTP or RTCP during their session in the latest reporting interval is exceeded.
Repetiti No
on
Event
sonusAlarmLevel
sonusAlarmTime
sonusH248VmgName
sonusH248TermThreshold
sonusH248NoRtpTerminations
Instanc
e Fields sonusH248VmgName
Action An issue in the network may prevent media traffic from reaching this VMG.
Impact All impacted terminations stopped receiving RTP (media), which means the end-users that this traffic is directed to do not receive
audio.
Clearing Automatic; sonusH248ClearVMGtermNoRTPRcvdThresholdExceeded
sonusH248ClearVMGtermNoRTPRcvdThresholdExceeded -
MAJOR
Type: MAJOR
Object 1.3.6.1.4.1.2879.2.10.1.1.35.0.2
ID
Descrip The alarm generates when the clear threshold for the VMG that specifies the percentage of the total number of terminations that did
tion not receive any RTP or RTCP during their session in the latest reporting interval is not exceeded.
Repetiti No
on
Event
sonusAlarmLevel
sonusAlarmTime
sonusH248VmgName
sonusH248ClearThreshold
sonusH248NoRtpTerminations
sonusH248MinimumRtpTerminations
sonusH248TotalRtpTerminations
Instanc
e Fields sonusH248VmgName
Action None
Impact All impacted terminations start receiving RTP.
Clearing Manual
The SBC generates an alarm when it detects that an internal micro-service, such as a Service Discovery micro-service, is unresponsive. The
alarm clears when the micro-service becomes operational again.
Service Discovery for Trap Target Destinations and EMS Registration
With regard to Service Discovery for trap target destinations and EMS registration, the SBC generates an alarm,
sonusMicroServiceConnectionFailed, when it detects that its internal Service Discovery micro-service is unresponsive. The alarm clears
with alarm sonusMicroServiceConnectionSucceeded when the micro-service becomes operational again. For more information about
Service Discovery, see Service Discovery for Trap Target Destinations and EMS Registration.
In addition, the SBC generates alarms when a DNS server is blacklisted or recovers from a blacklisted state. For these alarm descriptions,
refer to sonusSbxDnsServerBlacklistedNotification - CRITICAL and sonusSbxDnsServerRecoveredNotification - CRITICAL.
This section contains the following Internal Micro-Services alarms.
sonusMicroServiceConnectionFailed - MINOR
sonusMicroServiceConnectionSucceeded - INFORMATIONAL
sonusMicroServiceConnectionFailed - MINOR
Type: MINOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.33.0.1
Description The SBC connection to the specified internal micro-service is lost.
In the case of Service Discovery, this alarm is reported if the Service Discovery micro-service becomes unresponsive.
Repetition Each time the communication is lost between the SBC and an internal micro-service
Event Codes
sonusAlarmNodeID
sonusAlarmLevel
sonusAlarmTime
sonusMicroServiceName
Instance Fields sonusMicroServiceName
Action Make sure the micro-service is reachable.
Impact The SBC is not able to communicate with the micro-service.
Clearing Automatic, sonusMicroServiceConnectionSucceeded
sonusMicroServiceConnectionSucceeded - INFORMATIONAL
Type: INFORMATIONAL
Object ID 1.3.6.1.4.1.2879.2.10.1.1.33.0.2
Description The SBC connection to the specified micro-service is restored.
In the case of Service Discovery, this alarm is reported when the Service Discovery micro-service is restored.
Repetition None
Event Codes
sonusAlarmNodeID
sonusAlarmLevel
sonusAlarmTime
sonusMicroServiceName
Instance Fields sonusMicroServiceName
Action None
Impact The SBC is able to communicate with the micro-service.
Clearing Automatic, sonusMicroServiceConnectionFailed
IP Interface Alarms
This section contains the following IP Interface alarms.
sonusBfdSessionDelete - MINOR
sonusBfdSessionDown - MINOR
sonusBfdSessionUp - MINOR
sonusSbxLvmLinkDetectionGroupFailedNotification - MAJOR
sonusSbxLvmLinkDetectionGroupRestoredNotification - MAJOR
sonusSbxLvmLinkDetectionGroupSwitchoverNotification - MAJOR
sonusSbxNrsIpInterfaceAdminDisabledNotification - MAJOR
sonusSbxNrsIpInterfaceAdminEnabledNotification - MAJOR
sonusSbxNrsIpInterfaceAdminISNotification - MAJOR
sonusSbxNrsIpInterfaceAdminOOSNotification - MAJOR
sonusSbxNrsIpInterfaceISNotification - MAJOR
sonusSbxNrsIpInterfaceLinkMonitorDownNotification - MAJOR
sonusSbxNrsIpInterfaceLinkMonitorDownNotificationV6 - MAJOR
sonusSbxNrsIpInterfaceLinkMonitorUpNotification - MAJOR
sonusSbxNrsIpInterfaceLinkMonitorUpNotificationV6 - MAJOR
sonusSbxNrsIpInterfaceOOSNotification - MAJOR
sonusSbxNrsLogMgmtIpInterfaceAdminDisabledNotification - MAJOR
sonusSbxNrsLogMgmtIpInterfaceAdminEnabledNotification - MAJOR
sonusSbxNrsMgmtIpInterfaceAdminDisabledNotification - MAJOR
sonusSbxNrsMgmtIpInterfaceAdminEnabledNotification - MAJOR
sonusSbxNrsMgmtPortAdminDisabledNotification - MINOR
sonusSbxNrsMgmtPortAdminEnabledNotification - MINOR
sonusSbxNrsMgmtPortDownNotification - MAJOR
sonusSbxNrsMgmtPortUpNotification - MINOR
sonusSbxNrsPacketPortDownNotification - MAJOR
sonusSbxNrsPacketPortUpNotification - MAJOR
sonusBfdSessionDelete - MINOR
Type: MINOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.34.0.3
Description The BFD session for the specified linkId is deleted by the operator.
Repetition No
Event Codes
sonusAlarmNodeID
sonusAlarmLevel
sonusAlarmTime
sonusBfdLinkId
Instance Fields
sonusBfdLinkId
Action None
Impact None
Clearing Manual
sonusBfdSessionDown - MINOR
Type: MINOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.34.0.1
Description The BFD session for the specified linkId is DOWN.
Repetition No
Event Codes
sonusAlarmNodeID
sonusAlarmLevel
sonusAlarmTime
sonusBfdLinkId
Instance Fields
sonusBfdLinkId
Action None
Impact None
Clearing Automatic; sonusBfdSessionDelete or sonusBfdSessionUp
sonusBfdSessionUp - MINOR
Type: MINOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.34.0.2
Description The BFD session for the specified linkId is UP.
Repetition No
Event Codes
sonusAlarmNodeID
sonusAlarmLevel
sonusAlarmTime
sonusBfdLinkId
Instance Fields
sonusBfdLinkId
Action None
Impact None
Clearing Manual
sonusSbxLvmLinkDetectionGroupFailedNotification - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.21.0.5
Description The alarm indicates the link detection group failed.
Repetition None

sonusAlarmLevel
sonusAlarmTime
sonusNrsCeName
sonusNrsAddressContextName
sonusLvmLinkDetectionGroupName
Instance Fields sonusNrsCeName

Action Examine the health of the links associated with the failed Link DetectionGroup and repair.
Impact The links monitored by this LinkDetectionGroup are failed.
Clearing Automatic; sonusSbxLvmLinkDetectionGroupRestoredNotification
sonusSbxLvmLinkDetectionGroupRestoredNotification -
MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.21.0.6
Description The alarm indicates the link detection group is restored.
Repetition None
Event Codes
sonusAlarmNodeIDE
sonusAlarmLevel
sonusAlarmTime
sonusNrsCeName
Instance Fields
sonusNrsCeName
Action None
Impact None
Clearing Manual
sonusSbxLvmLinkDetectionGroupSwitchoverNotification -
MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.21.0.7
Description This trap indicates the detection group triggered a CE switchover.
Repetition None
Event Codes
sonusAlarmNodeID
sonusAlarmLevel
sonusAlarmTime
sonusNrsCeName
Instance Fields
sonusNrsCeName
Action Examine the health of the links associated with the Link Detection Group that triggered the switchover, and repair.
Impact A CE switchover occurred.
Clearing Manual
sonusSbxNrsIpInterfaceAdminDisabledNotification - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.11.0.3
Description This alarm indicates the IP Interface was administratively disabled.
Repetition None
Event Codes sonusNrsAddressContextName

sonusNrsIpInterfaceGroupName
sonusNrsIpInterfaceName
Action None
Impact Calls cannot be made in the interface. The interface can be configured.
Clearing Automatic, sonusSbxNrsMgmtIpInterfaceAdminEnabledNotification
sonusSbxNrsIpInterfaceAdminEnabledNotification - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.11.0.4
Description This alarm indicates that the IP Interface was administratively enabled.
Repetition None

Action None
Impact The configuration cannot be changed on the interface.
Clearing Automatic, sonusSbxNrsIpInterfaceAdminDisabledNotification
sonusSbxNrsIpInterfaceAdminISNotification - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.11.0.6
Description This alarm indicates that the IP Interface was administratively placed in-service.
Repetition None

Action None
Impact Calls can be made on the interface.
Clearing Manual
sonusSbxNrsIpInterfaceAdminOOSNotification - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.11.0.5
Description This alarm indicates that the IP Interface was administratively placed out of service.
Repetition None

Action None
Impact New calls cannot be made on the interface.
Clearing Automatic, sonusSbxNrsIpInterfaceAdminISNotification
sonusSbxNrsIpInterfaceISNotification - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.11.0.2
Description This alarm indicates the specified IP interface is now in service. This alarm clears sonusSbxNrsIpInterfaceOOSNotification -
MAJOR.
Repetition None

Instance None
Fields
Action None
Impact This interface can carry calls.
Clearing Manual
sonusSbxNrsIpInterfaceLinkMonitorDownNotification -
MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.11.0.17
Description This alarm indicates that the destination IPv4 Interface is down.
Repetition None
Event Codes
sonusNrsIpAddress
Action None
Impact None
Clearing Automatic, sonusSbxNrsIpInterfaceLinkMonitorUpNotification
sonusSbxNrsIpInterfaceLinkMonitorDownNotificationV6 -
MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.11.0.21
Description This alarm indicates that the destination IPv6 Interface is down.
Repetition None

sonusNrsIpAddressV6
Action None
Impact None
Clearing Automatic, sonusSbxNrsIpInterfaceLinkMonitorUpNotificationV6
sonusSbxNrsIpInterfaceLinkMonitorUpNotification - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.11.0.18
Description This alarm indicates that the destination IPv4 Interface is up.
Repetition None
Event Codes
sonusNrsIpAddress
Action None
Impact None
Clearing Manual
sonusSbxNrsIpInterfaceLinkMonitorUpNotificationV6 -
MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.11.0.22
Description This alarm indicates that the destination IPv6 Interface is up.
Repetition None
Event Codes
sonusNrsIpAddressV6
Action None
Impact None
Clearing Manual
sonusSbxNrsIpInterfaceOOSNotification - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.11.0.1
Description The IP interface is out of service.
This alarm can apply to a specific IP address or all IP addresses configured on the specified interface.
Repetition None

Action Determine the cause of the out-of-service condition.
Impact No new calls can use the interface.
Clearing Automatic; sonusSbxNrsIpInterfaceISNotification
sonusSbxNrsLogMgmtIpInterfaceAdminDisabledNotification
- MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.11.0.20
Description This alarm indicates that the Logical Management IP Interface was administratively enabled.
Repetition None
Event Codes sonusNrsIpInterfaceName
Action None
Impact No management traffic will flow on the interface. The interface is not configurable..
Clearing Automatic, sonusSbxNrsLogMgmtIpInterfaceAdminEnabledNotification
sonusSbxNrsLogMgmtIpInterfaceAdminEnabledNotification -
MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.11.0.19
Description This alarm indicates that the Logical Management IP Interface was administratively enabled.
Repetition None
Event Codes sonusNrsIpInterfaceName
Action None
Impact Management traffic will flow on the interface. The interface cannot be configured.
Clearing Manual
sonusSbxNrsMgmtIpInterfaceAdminDisabledNotification -
MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.11.0.8
Description This alarm indicates that the Management IP Interface was administratively disabled.
Repetition None

Action None
Impact No management traffic will flow on the interface. The interface can be configured.
Clearing Automatic, sonusSbxNrsMgmtIpInterfaceAdminEnabledNotification
sonusSbxNrsMgmtIpInterfaceAdminEnabledNotification -
MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.11.0.9
Description This alarm indicates that the Management IP Interface was administratively enabled.
Repetition None

Action None
Impact Management traffic will flow on the interface. The interface cannot be configured.
Clearing Automatic, sonusSbxNrsMgmtIpInterfaceAdminDisabledNotification
sonusSbxNrsMgmtPortAdminDisabledNotification - MINOR
Type: MINOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.11.0.10
Description This alarm indicates that the Management Port was administratively disabled.
Repetition None
Event Codes sonusNrsCeName

sonusNrsPortName
Action None
Impact No management traffic will flow on the port. The port can be configured.
Clearing Automatic, sonusSbxNrsMgmtPortAdminEnabledNotification
sonusSbxNrsMgmtPortAdminEnabledNotification - MINOR
Type: MINOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.11.0.11
Description This alarm indicates that the Management Port was administratively enabled.
Repetition None

sonusNrsPortName
Action None
Impact Management traffic will flow on the port. The port cannot be configured.
Clearing Manual
sonusSbxNrsMgmtPortDownNotification - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.11.0.15
Description This alarm indicates that the Management IP Interface is down.
Repetition None

sonusNrsPortName
Action Determine the cause of the port down and correct it.
Impact No management traffic will flow on the port.
Clearing Automatic, sonusSbxNrsMgmtPortUpNotification
sonusSbxNrsMgmtPortUpNotification - MINOR
Type: MINOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.11.0.16
Description This alarm indicates that the Management IP Interface is up.
Repetition None

sonusAlarmLevel
sonusAlarmTime
sonusNrsCeName
sonusNrsPortName
Action None
Impact Management traffic will flow on the protocol.
Clearing Manual
sonusSbxNrsPacketPortDownNotification - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.11.0.13
Description This alarm indicates that the packet port is down.
Repetition None

sonusNrsPortName
Action Determine the cause of the port going down and correct it.
Impact No new calls can be made on the ports. Media for existing calls is lost.
Clearing Automatic, sonusSbxNrsPacketPortUpNotification
sonusSbxNrsPacketPortUpNotification - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.11.0.14
Description This alarm indicates that the packet port is up.
Repetition None

sonusNrsPortName
Action None
Impact Calls can use the port.
Clearing Manual
JSRC Alarms
This section contains the following Juniper SRC Server alarms:
sonusJsrcServerStateDownNotification - MAJOR
sonusJsrcServerStateUpNotification - MAJOR
sonusJsrcServerStateDownNotification - MAJOR
Type: MAJOR
Objec 1.3.6.1.4.1.2879.2.10.1.1.4.0.27
t ID
Descr This alarm indicates that the JSRC Server is down.

iption
Repet None
ition
Event sonusJSrcServerName - Specifies the name of the server in the jsrcServer remoteServer table.
Codes
Instan None
ce
Fields
Action If system jsrcServer and the srcReconnectPollTimeout is set to 0, the server must be manually disabled and re-enabled to bring the
server back in service, else, an automatic reconnect occurs. In either case, check the connectivity to, and the health of, fields of the
remote server.
Impact If only one remote Server is configured, calls requiring source reservations fails, else, call capacity may be affected.
Cleari Automatic, sonusJsrcServerStateDownNotification

ng
sonusJsrcServerStateUpNotification - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.4.0.26
Description This alarm indicates that the JSRC Server is Up and Running.
Repetition None
Event Codes sonusJSrcServerName - Specifies the name of the server in the jsrcServer remoteServer table.
Action None
Impact None
Clearing Automatic, sonusJsrcServerStateDownNotification
This section describes the following Lawful Intercept alarms.
sonusSbxImMediationServerTcpLinkDown - MAJOR
sonusSbxImMediationServerTcpLinkUp - MAJOR
sonusSbxImPriOperStateChange - MAJOR
sonusSbxImSecOperStateChange - MAJOR
sonusSbxImMediationServerX2MsgBufferFull - MAJOR
sonusSbxImMediationServerX2MsgBufferAvailable - MAJOR
sonusLiCryptoFailureNotification - MAJOR
sonusLiCryptoSuccessNotification - MAJOR
sonusSbxImMediationServerTcpLinkDown - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.18.0.3
Description The alarm indicates the TCP link towards the Mediation Server is down.
Repetition None

sonusAlarmLevel
sonusAlarmTime
sonusImMediationServerName
sonusImMediationServerState
sonusImMediationServerInterceptMediaType
Instance Fields sonusImMediationServerName

Action Ensure the TCP link toward Mediation Server is up and running.
Impact Intercepted media is not sent over TCP.
Clearing Automatic; sonusSbxImMediationServerTcpLinkUp
sonusSbxImMediationServerTcpLinkUp - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.18.0.4
Description TCP link towards Mediation Server is established.
Repetition None

sonusAlarmLevel
sonusAlarmTime
Instance Fields sonusImMediationServerName

Action None
Impact Intercepted Media can be sent towards the mediation server.
Clearing Automatic
sonusSbxImPriOperStateChange - MAJOR
Type: MAJOR
Object 1.3.6.1.4.1.2879.2.10.1.1.18.0.1
ID
Descripti This alarm specifies the primary operational state of the intercept manager.
on
Repetition None
sonusAlarmTime
sonusImStatusPriOperState
Instance sonusImStatusPriOperState
Fields
Action If the primary operational state changes to out of service, SBC switches to secondary call data channel. If the secondary operational
state changes to out of service, SBC switches to primary call data channel.
Impact None
Clearing Manual
sonusSbxImSecOperStateChange - MAJOR
Type: MAJOR
Object 1.3.6.1.4.1.2879.2.10.1.1.18.0.2
ID
Descripti This alarm specifies the secondary operational state of the intercept manager.
on
Repetition None
sonusAlarmTime
Instance sonusImStatusSecOperState
Fields
Impact None
Clearing Manual
sonusSbxImMediationServerX2MsgBufferFull - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.18.0.5
Description This alarm indicates that the mediation server X2 message buffer is full.
Repetition None
Event Codes sonusAlarmNodeID,
sonusAlarmLevel
Instance Fields sonusAlarmTime
Action Ensure that the TCP link is up.
Impact X2 signaling message interception gets discarded.
Clearing NONE; SET Alarm only
sonusSbxImMediationServerX2MsgBufferAvailable - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.18.0.6
Description This alarm indicates that the mediation server X2 message buffer is available.
Repetition None
sonusAlarmLevel
Instance Fields sonusAlarmTime
Action None
Impact X2 Intercepted signaling message is sent towards the mediation server.
Clearing sonusSbxImMediationServerX2MsgBufferFull
sonusLiCryptoFailureNotification - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.4.0.46
Descripti D-SBC deployments: This alarm is raised when the LI data decryption operation fails at the S-SBC or M-SBC node. This trap is not
on raised again for subsequent failures as it is a rate-limited alarm.
Repetition None
sonusAlarmTime
sonusScmInstanceId
sonusDecryptModuleId
Instance sonusScmInstanceId
Fields sonusDecryptModuleId
Action Investigate for possible Man In The Middle (MITM) attack and report the attack to the customer support team.
Impact This impacts lawful interception between S-SBC to M-SBC or PSX to S-SBC
Clearing Automatic; sonusLiCryptoSuccessNotification
sonusLiCryptoSuccessNotification - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.4.0.47
Description D-SBC deployments: This alarm is raised when the LI data decryption returns to successful operation after a failure. This trap
clears the sonusLiCryptoFailureNotification alarm.
Repetition None
sonusAlarmTime
sonusScmInstanceId
sonusDecryptModuleId
Instance sonusScmInstanceId
Fields sonusDecryptModuleId
Action None
Impact None
Clearing Automatic; sonusLiCryptoFailureNotification
License Alarms
This section contains the following License alarms.

sonusCpLicenseBundleExpiredNotification - CRITICAL
sonusCpLicenseBundleExpireWarningNotification - MAJOR
sonusCpLicenseBundleInvalidUsageCount - MAJOR
sonusCpLicenseBundleRenewedNotification - MAJOR
sonusCpLicenseHostSerialUnavailable - CRITICAL
sonusCpLicenseIntegrityViolationNotification - CRITICAL
sonusCpLicensePeerSerialMismatch - CRITICAL
sonusCpLicenseSerialMismatch - CRITICAL
sonusCpNiceRecLicenseExpireSoonWarningNotification - MAJOR
sonusCpNiceRecLicenseExpireWarningNotification - CRITICAL
sonusSbxCallRejectsDueToSlbSessionLicenseNotification - Critical
sonusSbxFeatureLicenseAvailable - INFORMATIONAL
sonusSbxFeatureLicenseUnavailable - CRITICAL
sonusSbxLicensedEvsSessionsThresholdReachedNotification - INFORMATIONAL
sonusSbxLicensedOodRateLimitClearNotification - MAJOR
sonusSbxLicensedOodRateLimitReachedNotification - MAJOR
sonusSbxLicensedSessionsThresholdReachedNotification - INFORMATIONAL
sonusSbxLicensedSlbSessionsThresholdReachedNotification - INFORMATIONAL
sonusSbxPDCSLicenseUnavailableNotification - MINOR
sonusSbxSIPRecLicenseNotAvailable - MINOR
sonusSbxSiprecLicenseUnavailableNotification - MINOR
sonusSipRegThresholdClearedNotification - MAJOR
sonusSipRegThresholdReachedNotification - MAJOR
Note
Some license alarms are specific to a particular license mode and are not triggered unless the SBC is configured to use the
corresponding license mode.
This section describes licensing alarms applicable to SBC SWe when deployed in an N:1 HA or OpenStack cloud environment.
Table of Contents
sonusCpLicenseExpireSoonWarningNotification - MAJOR
sonusCpLicenseExpireWarningNotification - CRITICAL
sonusCpLicenseManagerCouldNotConnect - MAJOR
sonusCpLicenseManagerLicenseServersConfigured - MAJOR
sonusCpLicenseManagerLicenseUsageDetected - INFORMATIONAL
sonusCpLicenseManagerNoEmsNodeIdConfigured - MAJOR
sonusCpLicenseManagerNoLicenseServersConfigured - MAJOR
sonusCpLicenseManagerNoLicenseUsageDetected - MAJOR
sonusCpLicenseManagerRegistrationFailed - MAJOR
sonusCpLicenseManagerRegistrationPeriodExpired - CRITICAL
sonusCpLicenseManagerRegistrationSucceeded - INFORMATIONAL
sonusCpLicenseManagerUnsanctionedMannerSoon - CRITICAL
sonusInvalidFingerPrintNotification - MAJOR
sonusSbxCallRejectsDueToSessionLicenseNotification - CRITICAL
sonusSbxClearMaximumLicenseCountThresholdExceeded - INFORMATIONAL
sonusSbxClearMinimumLicenseCountThresholdNotReached - INFORMATIONAL
sonusSbxLicensedAmrNbSessionsThresholdReachedNotification - INFORMATIONAL
sonusSbxLicensedAmrWbSessionsThresholdReachedNotification - INFORMATIONAL
sonusSbxLicensedEvrcSessionsThresholdReachedNotification - INFORMATIONAL
sonusSbxLicensedServiceDeniedDueToLicenseLimit - CRITICAL
sonusSbxLicensedVdspThresholdReachedNotification - MAJOR
sonusSbxMandatoryLicenseAvailable - INFORMATIONAL
sonusSbxMandatoryLicenseUnavailable - CRITICAL
sonusSbxMaximumLicenseCountThresholdExceeded - CRITICAL
sonusSbxMinimumLicenseCountThresholdNotReached - CRITICAL
sonusSbxServiceLicenseAvailable - INFORMATIONAL
sonusSbxServiceLicenseUnavailable - MAJOR
sonusCpLicenseExpireSoonWarningNotification - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.8.0.15
Description This trap warns the user that the specified local license expires soon. The trap is reported 90, 60, and 30 days from the
expiration date.
Repetition None

sonusAlarmLevel
sonusAlarmTime
sonusCpLicenseFeatureName
Instance sonusCpLicenseFeatureName
Fields
Action Contact Ribbon to purchase new licenses.
Impact Calls requiring this feature may fail when the license expires.
Clearing Manual
This trap is applicable only for local licensing mode.
sonusCpLicenseExpireWarningNotification - CRITICAL
Type: CRITICAL
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.8.0.16
Description This trap warns the user that the specified local license is in immediate danger of expiring. The trap is reported 7 days, 1 day, 8
hours, and 0 hours from the expiration date/time.
Repetition None
sonusAlarmTime
Instance sonusCpLicenseFeatureName
Fields
Action Contact Ribbon to purchase new licenses.
Impact Calls requiring this feature may fail when the license expires.
Clearing Manual
This trap is applicable only for local licensing mode.
sonusCpLicenseManagerCouldNotConnect - MAJOR
Type: MAJOR
Obj 1.3.6.1.4.1.2879.2.8.1.2.1.19.0.3
ect
ID
De This alarm indicates that the connection to the License Manager failed.
scr
ipti
on
Re Repeats for each occurrence.

pet
ition
Ev EVENT_LICENSE_MANAGER_SERVER_CONNECT_ERROR
ent
Co
des
Ins
tan sonusAlarmNodeID
ce sonusAlarmLevel
Fie sonusAlarmSequenceId
lds sonusAlarmTime
sonusServerIpAddress
sonusLicenseManagerGraceDaysLeft
Act Check the IP address in the message and check connectivity to that address.
ion
Im The SBC will not be able to register with the EMS/RAMP.

pa
ct
Note
If the SBC remains disconnected from the managing EMS/RAMP instance for an extended period of time, it will result in the SBC
operating in an unsanctioned manner from a licensing perspective. Reconnect the SBC to the managing EMS/RAMP instance.
Contact Ribbon Global Product Support for more information regarding the need for the SBC to remain in constant contact with the
managing EMS/RAMP instance.
Cle automatic; sonusCpLicenseManagerRegistrationSucceeded

ari
ng
sonusCpLicenseManagerLicenseServersConfigured - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.19.0.2
Description This alarm indicates that license servers configuration information is available.
Repetition Repeats for each occurrence.
Event Codes EVENT_LICENSE_MANAGER_LICENSE_SERVERS_CONFIGURED
Instance Fields
sonusAlarmNodeID
sonusAlarmLevel
sonusAlarmTime
sonusLicenseManagerServerList
Action None needed.
Impact The SBC will be able to register with the EMS/RAMP.
Clearing Manual
sonusCpLicenseManagerLicenseUsageDetected -
INFORMATIONAL
Type: INFORMATIONAL
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.19.0.9
Alarm Name sonusCpLicenseManagerLicenseUsageDetected
Description This trap indicates that License Manager has successfully collected license usage statistics.
Event Codes EVENT_LICENSE_MANAGER_LICENSE_USAGE_DETECTED
sonusAlarmNodeID,
sonusAlarmLevel,
sonusAlarmTime,
sonusServerIpAddress,
sonusLicenseManagerLastCollectionTime
Action None
Impact None
Clearing Manual
sonusCpLicenseManagerNoEmsNodeIdConfigured - MAJOR
Type: MAJOR
Obj 1.3.6.1.4.1.2879.2.8.1.2.1.19.0.7
ect
ID
De This alarm indicates that an EMS/RAMP node ID has not been configured on the SBC.
scr
ipti
on

pet
ition
Ev EVENT_LICENSE_MANAGER_EMS_NODEID_NOT_CONFIGURED
ent
Co
des
Ins
ce sonusAlarmLevel
lds sonusAlarmTime
Act Check if the SBC has successfully registered with the EMS/RAMP and the performance data collection is enabled.
ion

pa
ct
Note
Cle Manual
ari
ng
sonusCpLicenseManagerNoLicenseServersConfigured -
MAJOR
Type: MAJOR
Obj 1.3.6.1.4.1.2879.2.8.1.2.1.19.0.1
ect
ID
De This alarm indicates that no license servers have been configured to communicate with the License Manager and no EMS/RAMP
scr registration information is available.
ipti
on

pet
ition
Ev LICENSE_MANAGER_NO_LICENSE_SERVERS_CONFIGURED
ent
Co
des
Ins
ce sonusAlarmLevel
lds sonusAlarmTime
Act Configure one or more license servers.

ion

pa
ct
Note
Cle automatic; sonusCpLicenseManagerLicenseServersConfigured

ari
ng
sonusCpLicenseManagerNoLicenseUsageDetected - MAJOR
Type: MAJOR
Ob 1.3.6.1.4.1.2879.2.8.1.2.1.19.0.8
jec
t ID
De This alarm indicates that the License Manager has not collected license usage statistics for more than a day.
scr
ipti
on

pet
ition
Ev EVENT_LICENSE_MANAGER_NO_LICENSE_USAGE_DETECTED
ent
Co
des
Ins
ce sonusAlarmLevel
lds sonusAlarmTime
sonusLicenseManagerLastCollectionTime
Act Check the logs on the License Manager and correct the issues listed. This issue is seen if no calls have been made on the system and
ion no on/off licenses are present.
Im If the SBC remains disconnected from the managing EMS/RAMP instance for an extended period of time, it will result in the SBC
pa operating in an unsanctioned manner from a licensing perspective. Reconnect the SBC to the managing EMS/RAMP instance. Contact
ct Ribbon Global Product Support for more information regarding the need for the SBC to remain in constant contact with the managing
EMS/RAMP instance.
Cle automatic; sonusCpLicenseManagerLicenseUsageDetected

ari
ng
sonusCpLicenseManagerRegistrationFailed - MAJOR
Type: MAJOR
Obj 1.3.6.1.4.1.2879.2.8.1.2.1.19.0.4
ect
ID
De This alarm indicates that the License Manager has rejected the registration request.
scr
ipti
on

pet
ition
Ev EVENT_LICENSE_MANAGER_SERVER_REGISTRATION_FAILED
ent
Co
des
Ins
ce sonusAlarmLevel
lds sonusAlarmTime
Act Check the logs on the License Manager and correct the issues listed.
ion

pa
ct
Note

ari
ng
sonusCpLicenseManagerRegistrationPeriodExpired -
CRITICAL
Type: CRITICAL
Obj 1.3.6.1.4.1.2879.2.8.1.2.1.19.0.6
ect
ID
De This alarm indicates that the SBC was unable to register with the License Manager during the grace period.
scr
ipti
on

pet
ition
Ev EVENT_LICENSE_MANAGER_REGISTRATION_PERIOD_EXPIRED
ent
Co
des
Ins
ce sonusAlarmLevel
Fiel sonusAlarmSequenceId
ds sonusAlarmTime
sonusLicenseManagerGracePeriod
Act Check the previous alarms regarding registration failures and take the actions indicated.
ion
Reconnect the SBC to the managing EMS/RAMP instance.
Im The SBC has been disconnected from the managing EMS/RAMP for an extended period, resulting in the SBC operating in an
pact unsanctioned manner from a licensing perspective. Reconnect the SBC to the managing EMS/RAMP instance. Contact Ribbon Global
Product Support for more information regarding the need for the SBC to remain in constant contact with the managing EMS/RAMP
instance.

ari
ng
sonusCpLicenseManagerRegistrationSucceeded -
INFORMATIONAL
Type: INFORMATIONAL
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.19.0.5
Description This alarm indicates that the registration with the License Manager was successful.
Event Codes EVENT_LICENSE_MANAGER_SERVER_REGISTRATION_SUCCEEDED
Instance Fields
sonusAlarmNodeID
sonusAlarmLevel
sonusAlarmTime
Action None
Impact None
Clearing Manual
sonusCpLicenseManagerUnsanctionedMannerSoon -
CRITICAL
Type: CRITICAL
Obj 1.3.6.1.4.1.2879.2.8.1.2.1.19.0.11
ect
ID
De This alarm indicates that the SBC has not successfully registered with the EMS/RAMP for an extended period of time. The SBC will
scr soon operate in an unsanctioned manner from a licensing perspective.
ipti
on
Re The alarm repeats once a day.

pet
ition
Ev
ent sonusAlarmNodeID
Co sonusAlarmLevel
des sonusAlarmSequenceId
sonusAlarmTime
Ins
tan sonusLicenseManagerGracePeriodStart
ce sonusLicenseManagerGraceDaysLeft
Fie sonusLicenseManagerGraceHoursLeft
lds
Act Check the logs on the License Manager and correct the issues listed.
ion
Im If the SBC remains disconnected from the managing EMS/RAMP instance for an extended period, it will result in the SBC operating in
pa an unsanctioned manner from a licensing perspective. Reconnect the SBC to the managing EMS/RAMP instance. Contact
ct Ribbon Global Product Support for more information regarding the need for the SBC to remain in constant contact with the managing
EMS/RAMP instance.
Cle Automatic; sonusCpLicenseManagerRegistrationSucceeded

ari
ng
sonusInvalidFingerPrintNotification - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.8.0.17
Description This trap notifies of an attempt to install a license with an invalid fingerprint.
Repetition None
Event Codes
sonusAlarmNodeID
sonusAlarmLevel
sonusAlarmTime
sonusCpLicenseViolationDescString
Instance Fields
sonusCpLicenseViolationDescString
Action None
Impact None
Clearing Manual
sonusSbxCallRejectsDueToSessionLicenseNotification -
CRITICAL
Type: CRITICAL
Object 1.3.6.1.4.1.2879.2.10.1.1.14.0.1
ID
Descrip This alarm is generated when either pass-through or transcoded sessions fail to set up due to the lack of a valid session license, or if
tion the total number of active sessions has reached the session license limit. As a result, new calls will fail.
Repetiti None
on
sonusAlarmTime
sonusSessLicenseLimit
Instanc sonusSessLicenseLimit
e
Fields
Action Obtain additional session licenses.
Impact Calls exceeding the session license limit are rejected.
Clearing Automatic; sonusSbxCallRejectsDueToSessionLicenseClearNotification
sonusSbxClearMaximumLicenseCountThresholdExceeded -
INFORMATIONAL
Type: INFORMATIONAL
Object ID 1.3.6.1.4.1.2879.2.10.1.1.14.0.9
Description This alarm clears the alarm sonusSbxMinimumLicenseCountThresholdNotReached.
Repetition None

sonusAlarmLevel
sonusAlarmTime
sonusAlarmName
sonusSessionsThreshold
Instance Fields sonusSessionsThreshold

Action None
Impact None
Clearing Manual
sonusSbxClearMinimumLicenseCountThresholdNotReached
- INFORMATIONAL
Type: INFORMATIONAL
Object ID 1.3.6.1.4.1.2879.2.10.1.1.14.0.7
Description This alarm clears the alarm sonusSbxClearMinimumLicenseCountThresholdNotReached.
Repetition None

sonusAlarmLevel
sonusAlarmTime
sonusAlarmName

Action None
Impact None
Clearing Manual
sonusSbxLicensedAmrNbSessionsThresholdReachedNotification -
Note
Type: INFORMATIONAL
Object ID 1.3.6.1.4.1.2879.2.10.1.1.14.0.14
Description This alarm is only applicable when the SBC is using local licenses and configured threshold is reached for AMRNB sessions.
Repetition Once in a day per configured value

sonusAlarmLevel
sonusAlarmTime
sonusActiveSessionCount

Action Purchase additional session licenses.
Impact The sessions usage has reached or exceeded the notification threshold
Clearing Manual
sonusSbxLicensedAmrWbSessionsThresholdReachedNotification
Note
Type: INFORMATIONAL
Object ID 1.3.6.1.4.1.2879.2.10.1.1.14.0.15
Description This alarm is only applicable when the SBC is using local licenses and configured threshold is reached for AMRWB sessions.

sonusAlarmLevel
sonusAlarmTime

Impact The sessions usage has reached or exceeded the notification threshold.
Clearing Manual
sonusSbxLicensedEvrcSessionsThresholdReachedNotification - IN
Type: INFORMATIONAL
Object ID 1.3.6.1.4.1.2879.2.10.1.1.14.0.16
Description This alarm is only applicable when the SBC is using local licenses and configured threshold is reached for EVRC sessions.

sonusAlarmLevel
sonusAlarmTime

Clearing Manual
sonusSbxLicensedServiceDeniedDueToLicenseLimit -
CRITICAL
Type: CRITICAL
Objec 1.3.6.1.4.1.2879.2.10.1.1.14.0.25
t ID
Descr This alarm indicates that for a licensed feature, the session limit is reached. The service is denied for the affected call. This alarm is
iption raised for each licensed feature for which the session limit is reached. However, the rate of the alarmed being triggered is limited to one
alarm per license per minute.
Repet Every minute.

ition
Event
sonusAlarmLevel
sonusAlarmTime
sonusAlarmName
Insta
nce sonusAlarmName
Fields sonusActiveSessionCount
Action Consider if more licenses should be ordered for the affected service.
Impa The specified service license reaches its limit and the SBC denies the associated service for the affected call. The SBC continues to
ct deny any all further requests for the service, till the license is available.
Cleari Manual
ng
sonusSbxLicensedVdspThresholdReachedNotification -
MAJOR
Note
Currently, the SBC does not support this alarm. This alarm is generated only in local licensing mode.
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.14.0.19
Description This trap is only applicable when the SBC is using local licenses and the configured threshold is reached for VDSP sessions.
Repetition Once per day

sonusAlarmLevel
sonusAlarmTime

Clearing Manual
sonusSbxMandatoryLicenseAvailable - INFORMATIONAL
Type: INFORMATIONAL
Object ID 1.3.6.1.4.1.2879.2.10.1.1.14.0.22
Description This alarm indicates that a mandatory license is available, and operations are restored to normal after clearing the alarm.
Repetition Once per acquired license.
Event Codes
sonusAlarmNodeID
sonusAlarmLevel
sonusAlarmTime
sonusAlarmName
Instance Fields sonusAlarmName
Action None
Impact The SBC gets the specified license from the license server, and the functionality dependent on that license is enabled.
Clearing Manual
sonusSbxMandatoryLicenseUnavailable - CRITICAL
Type: CRITICAL
Object ID 1.3.6.1.4.1.2879.2.10.1.1.14.0.21
Descripti This alarm indicates that a mandatory license is not available. The alarm is triggered for each of the unavailable licenses. When the
on alarm is raised, all call admissions are suspended.
Repetition Once per license, and every 1 hour if the required mandatory license not acquired.
Event
sonusAlarmLevel
sonusAlarmTime
sonusAlarmName
Instance sonusAlarmName
Fields
Action
Check each of the the mandatory licenses required for configuring the SBC.
Check whether the mandatory licenses are applied and available at the license server.
Impact The specified mandatory license is unavailable at the license server, or, a mandatory license is required but not specified in the
required license table. As a result, all call admissions are disabled.
Clearing Automatic; sonusSbxMandatoryLicenseAvailable
sonusSbxMaximumLicenseCountThresholdExceeded -
CRITICAL
Type: CRITICAL
Object 1.3.6.1.4.1.2879.2.10.1.1.14.0.8
ID
Descrip This alarm is generated when the SBC license is configured with a maximum threshold (for example, this matches the SBC-RTU
tion maximum license count) that is lower than the current license count returned by the SLS.
Repetiti None
on
sonusAlarmTime
sonusAlarmName
Instanc sonusSessionsThreshold
e Fields sonusSessLicenseLimit
Action
Increase the maximum count for that license.
In case of call fail, increase the maximum count of the license or wait until call count is less then maximum count.
Impact
Call fails, if the current call count is more than the maximum count, which is configured for that license. If the calls are released
and the call count is less than maximum count, calls are allowed till the availability of the license.
If maximum count is reduced than the previously acquired license, licenses are released to the SLS.
Clearing Automatic; sonusSbxClearMaximumLicenseCountThresholdExceeded
sonusSbxMinimumLicenseCountThresholdNotReached -
CRITICAL
Type: CRITICAL
Object ID 1.3.6.1.4.1.2879.2.10.1.1.14.0.6
Descripti This alarm is generated when the SBC license is configured with a minimum threshold (for example, this will match the SBC-RTU
on minimum license count) that cannot be returned by the SLS.
Repetition None
sonusAlarmTime
sonusAlarmName
Instance sonusSessionsThreshold
Fields sonusSessLicenseLimit
Action Check for license availability in SLS server.
Impact None
Clearing Automatic; sonusSbxClearMinimumLicenseCountThresholdNotReached
sonusSbxServiceLicenseAvailable - INFORMATIONAL
Type: INFORMATIONAL
Object ID 1.3.6.1.4.1.2879.2.10.1.1.14.0.24
Description This alarm indicates that a service license has successfully been retrieved.
Repetition Once per acquired license.
Event Codes
sonusAlarmNodeID
sonusAlarmLevel
sonusAlarmTime
Action None
Impact he specified service license is fetched from the license server and the associated service is allowed in the SBC.
Clearing Manual
sonusSbxServiceLicenseUnavailable - MAJOR
Type: MAJOR
Objec 1.3.6.1.4.1.2879.2.10.1.1.14.0.23
t ID
Descr This alarm indicates that a service license required for configuring a service cannot be retrieved from the license server. Due to the
iption unavailability of the required license, licensed functionality is denied by the SBC. This alarm is raised for each instance of unavailable
service license.
Repet Once per license, and once every hour till the required service license not acquired.
ition
Event
sonusAlarmLevel
sonusAlarmTime
sonusAlarmName
Instan sonusAlarmName
ce
Fields
Action Check whether the required licenses are applied at the license server.
Impact The specified service license is unavailable at the license server, and the SBC denies the associated service.
Cleari Automatic; sonusSbxServiceLicenseAvailable

ng
sonusCpLicenseBundleExpiredNotification - CRITICAL
Type: CRITICAL
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.8.0.3
Description This alarm indicates that license bundle (featureName) has expired.
Repetition None

sonusAlarmLevel
sonusAlarmTime
sonusCpLicenseId
Instance Fields sonusCpLicenseId

Action Contact Sonus to obtain an updated license.
Impact Calls may be rejected.
Clearing Manual
Note
When upgrading to 6.0 and later releases, the sonusCpLicenseBundleExpiredNotification CRITICAL alarm is triggered if the POL-BASE
license is installed because the ePSX is no longer supported. To clear this alarm, remove the POL-BASE license bundle from the EMA
GUI. Refer to License Management - Node Locked License Settings for details.
sonusCpLicenseBundleExpireWarningNotification - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.8.0.2
Description This trap indicates that license bundle will expire in 14 days.
Repetition None
Event Codes sonusCpLicenseId

Action None
Impact None
Clearing Manual
sonusCpLicenseBundleInvalidUsageCount - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.8.0.19
Description This alarm indicates that the usage limit for a counted license has an invalid count of 0.
Repetition On system startup

sonusAlarmLevel
sonusAlarmTime
sonusCpLicenseId
Instance Fields sonusCpLicenseId

Action Contact Sonus to generate a new license with the valid usage count.
Impact Not enough licenses may be available
Clearing Manual
sonusCpLicenseBundleRenewedNotification - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.8.0.4
Description This trap indicates that license bundle is renewed.
Repetition None
Event Codes sonusCpLicenseId

Action None
Impact None
Clearing Manual
sonusCpLicenseHostSerialUnavailable - CRITICAL
Type: CRITICAL
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.8.0.5
Description This trap indicates that the host serial number could not be read from the hardware.
Repetition None
Action None
Impact None
Clearing Manual
sonusCpLicenseIntegrityViolationNotification - CRITICAL
Type: CRITICAL
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.8.0.1
Description This alarm indicates any attempted violation of license integrity.
Repetition None
Event Codes sonusCpLicenseViolationDescString

sonusCpLicenseId
Action None
Impact None
Clearing Manual
sonusCpLicensePeerSerialMismatch - CRITICAL
Type: CRITICAL
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.8.0.7
Descripti This trap indicates that the Peer host serial number does not match the serial number recorded in the license.
on
Repetition None
Codes
sonusCpLicenseId
Instance None
Fields
Action Check the Peer's serial number and compare it to what is recorded in the license, and then refer to Node-Locked Licensing for
guidance and/or contact your Ribbon account representative.
Impact The license file is deemed invalid due to serial number mismatch. In HA scenario, the license file must contain both SBC serial
numbers.
Clearing Manual
sonusCpLicenseSerialMismatch - CRITICAL
Type: CRITICAL
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.8.0.6
Descripti This alarm indicates that the host serial number does not match the serial number recorded in the license.
on
Repetition None
Event
sonusCpLicenseId
Instance None
Fields
Action Check the Host serial number and compare it to what is recorded in the license, and then refer to Node-Locked Licensing for
guidance and/or contact your Sonus account representative.
Impact The license file is deemed invalid due to serial number mismatch. The license file must contain the SBC serial number.
In HA scenario, the license file must contain both SBC serial numbers.
Clearing Manual
sonusCpNiceRecLicenseExpireSoonWarningNotification -
MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.8.0.31
Description The SBC generates this trap during the time of SBC-NICEREC license expiry. This trap is applicable only to Legacy modes.
Repetition 90 days, 60 days and 30 days

sonusAlarmLevel
sonusAlarmTime
Instance Fields sonusAlarmLevel

Action Purchase a new license.
Impact Calls are disconnected after the license expiry.
Clearing Manual
sonusCpNiceRecLicenseExpireWarningNotification -
CRITICAL
Type: CRITICAL
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.8.0.32
Description The SBC generates this trap during the time of SBC-NICEREC license expiry. This trap is applicable only to Legacy modes.
Repetition 7 days, 1 day, 8 hours and 0 hour

sonusAlarmLevel
sonusAlarmTime
Instance Fields sonusAlarmLevel

Action A new license is required to purchase.
Impact Calls are disconnected once the trap reports 0 hours left (license expires).
Clearing Manual
sonusSbxCallRejectsDueToSlbSessionLicenseNotification -
Critical
Type: CRITICAL
Objec 1.3.6.1.4.1.2879.2.10.1.1.14.0.29
t ID
Descr This alarm is generated when either pass-through or transcoded sessions fail to establish due to the lack of a valid Session Load
iption Balancer (SLB) session license, or if the total number of active SIB sessions reaches the session license limits. As a result, the SBC is
unable to complete new calls.
Repet None.
ition
Event
sonusAlarmTime
Insta sonusSessLicenseLimit
nce
Fields
Action None
Impa Call failures are explerienced due to SLB sessions license unavailability.
ct
Cleari Manual
ng
sonusSbxFeatureLicenseAvailable - INFORMATIONAL
Type: INFORMATIONAL
Object ID 1.3.6.1.4.1.2879.2.10.1.1.14.0.32
Description This alarm is generated when the feature license becomes available.
Repetition None
Event Codes
sonusAlarmNodeID
sonusAlarmLevel
sonusAlarmTime
Action None
Impact None
Clearing Automatic; sonusSbxFeatureLicenseUnavailable
sonusSbxFeatureLicenseUnavailable - CRITICAL
Type: CRITICAL
Object ID 1.3.6.1.4.1.2879.2.10.1.1.14.0.31
Description This alarm is generated when the mandatory feature license is not available.
Repetition None
Event Codes
sonusAlarmNodeID
sonusAlarmLevel
sonusAlarmTime
Action Obtain additional feature licenses.
Impact Feature functionality fails.
Clearing Automatics; sonusSbxFeatureLicenseAvailable
sonusSbxLicensedEvsSessionsThresholdReachedNotification - INF
Type: Informational
Object ID 1.3.6.1.4.1.2879.2.10.1.1.14.0.28
Description This alarm is only applicable when the SBC uses the local licenses and the configured threshold is reached for EVS sessions.
Repetition None
Event Codes
sonusAlarmLevel
sonusAlarmTime
Instance Fields
Clearing Manual
sonusSbxLicensedOodRateLimitClearNotification - MAJOR
Type: MAJOR
Objec 1.3.6.1.4.1.2879.2.10.1.1.28.0.2
t ID
Descri This alarm notifies that action which had been taken on sonusSbxLicensedOodRateLimitReachedNotification is now cleared.
ption
Repeti None
tion
sonusAlarmTime
sonusAlarmName
sonusActiveOodRate
sonusOodRateLimit
Instan sonusActiveOodRate
ce sonusOodRateLimit
Fields
Action None
Impact No impact.
Cleari Automatic; clears sonusSbxLicensedOodRateLimitReachedNotification when the peak rate goes below 90% of the configured OOD rate
ng license limit (10% less than when the alarm was set). This avoids repeated 'set' and 'clear' alarms when the peak rate is close to the
limit.
The alarm reports the SBC Node ID, time, active oodRate, and ood Rate limit (the Rate associated with the license).
sonusSbxLicensedOodRateLimitReachedNotification -
MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.28.0.1
Description This alarm warns the administrator when the configured OOD rate licensed rate limit is exceeded.
Repetition None

sonusAlarmLevel
sonusAlarmTime
sonusAlarmName
sonusActiveOodRate
sonusOodRateLimit
Instance Fields sonusActiveOodRate

sonusOodRateLimit
Action Lower the incoming OOD message rate to lower than 90% of the configured value.
Impact No impact.
Clearing Automatic, sonusSbxLicensedOodRateLimitClearNotification.
sonusSbxLicensedSessionsThresholdReachedNotification -
INFORMATIONAL
Type: INFORMATIONAL
Object ID 1.3.6.1.4.1.2879.2.10.1.1.14.0.3
Description This alarm indicates the SBC reached or exceeded the license sessions limit.
Repetition None
Event Codes sonusConcurrentCalls - Concurrent calls

sonusSessLicenseLimit - Licensed session limit
sonusSessionsThreshold - Sessions threshold
Impact If the session usage reaches or exceeds the license limit, calls may fail.
Clearing Manual
sonusSbxLicensedSlbSessionsThresholdReachedNotification - INF
Type: INFORMATIONAL
Object Id 1.3.6.1.4.1.2879.2.10.1.1.14.0.30
Description This alarm indicates the licensed SLB sessions notification threshold is reached or exceeded.
Repetition None
Event Codes
sonusAlarmNodeID
sonusAlarmLevel
sonusAlarmTime
Instance Fields
sonusConcurrentCalls
Action Purchase additional SLB session licenses.
Impact The SLB sessions usage has reached or exceeded the notification threshold.
Clearing Manual
sonusSbxPDCSLicenseUnavailableNotification - MINOR
Type: MINOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.1.0.61
Description This alarm indicates that P-DCS-LAES call interception failed due to lack of license(s).
Repetition None

sonusAlarmLevel
sonusAlarmTime
sonusRecCallGCID
sonusRecorderTrunkName
sonusRecordingCallLeg
Instance Fields sonusRecCallGCID

Action Purchase additional SIPREC licenses.
Impact P-DCS-LAES call interception fails.
Clearing Manual
This alarm is supported only in network mode. The network mode is applies only to existing SBC SWe cloud deployments that continue to
use network licensing from a prior release. Do not change your license mode to network. New implementations of network licensing are not
supported.
sonusSbxSIPRecLicenseNotAvailable - MINOR
Type: MINOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.1.0.45
Description This alarm indicates that the license is not available for SIPREC.
Repetition None
Event Codes NRM_SIPREC_LICENSE_NOT_AVAILABLE
Action Install license.
Impact SIPREC feature is not available as the license is not available.
Clearing Manual
sonusSbxSiprecLicenseUnavailableNotification - MINOR
Type: MINOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.1.0.60
Description This alarm indicates that the specified SIPREC recording session failed due to a missing license.
The alarm is reported while another recording session is in progress (concurrent recording sessions are required to generate
this alarm).
The alarm details specify the unused SRS.
Repetition None

sonusAlarmLevel
sonusAlarmTime
sonusRecorderIpAddress
sonusRecorderPortNum
sonusRecCallGCID
Instance sonusRecorderIpAddress
Fields sonusRecorderPortNum
sonusRecCallGCID
Action Purchase additional SIPREC licenses.
Impact SIPREC recordings fails.
Clearing Manual
This alarm is supported only in network mode. The network mode is applies only to existing SBC SWe cloud deployments that continue to
use network licensing from a prior release. Do not change your license mode to network. New implementations of network licensing are not
supported.
Type: MAJOR
O 1.3.6.1.4.1.2879.2.10.1.1.4.0.70
bj
e
ct
ID
D This alarm indicates that SIP Register License threshold is cleared. The threshold limit is 90% of the maximum license count.
e
s Note: The Alarm is cleared when the threshold falls back to 80% of the maximum license count but not if it happens within 5 seconds.
cr For example, if the registration count reaches 90% of the maximum license count and the very next second the count reaches to 80% of
ip the maximum license count (due to a registration expiration), then the alarm is not cleared immediately. After 5 seconds, if the
ti registration count is lesser than 80% of max license count, then the alarm is cleared. This control is implemented to control the flooding
on of alarms in the system.
R None
e
p
et
iti
on
E
v sonusAlarmNodeID
e sonusAlarmLevel
nt sonusAlarmSequenceId
C sonusAlarmTime
o sonusAlarmDescription
d
es
In
st sonusSipRegLicenseClearThreshold
a sonusSipRegLicenseLimit
n
c
e
Fi
el
ds
A None. SIP license threshold is cleared.

ct
ion
I The alarm indicates that SIP Register License Threshold is cleared. REGISTER messages are no longer rejected.
m
p
a
ct
C Automatic; sonusSipRegThresholdReachedNotification
le
ar
ing
Type: MAJOR
O 1.3.6.1.4.1.2879.2.10.1.1.4.0.71
bj
e
ct
ID
D This alarm indicates that the SIP Register License Threshold is reached. The threshold limit is 90% of the maximum license count. If the
e SIP Register License is not applied, and the REGISTER is tried, the alarm sonusSipRegThresholdReachedNotification is raised. It's
s cleared upon receiving the first REGISTER message after applying the license.
cr
ip Note: For NWDL licenses, the maximum license count is equal to the maximum registrations supported by the SBC. For Node-Locked
ti licenses, the maximum license count is equal to the number of licenses configured.
on
R None
e
p
et
iti
on
E
v SIPREG_LICENSE_UPPER_THRESHOLD_REACHED
e sonusAlarmNodeID
nt sonusAlarmLevel
C sonusAlarmSequenceId
o sonusAlarmTime
d sonusAlarmDescription
es
In
st sonusSipRegLicenseSetThreshold
a sonusSipRegLicenseLimit
n
c
e
Fi
el
ds
A The Admin must examine the SIP REGISTER traffic towards the REGISTRAR.
ct
ion
I The alarm indicates that SIP Register License Threshold is reached. After License limit is breached the SIP REGISTRAR may start
m rejecting REGISTER messages.
p
a
ct
C Automatic; sonusSipRegThresholdClearedNotification.
le
ar Note: The alarm is cleared when the threshold falls back to 80% of the maximum license count but not if it happens within 5 seconds.
ing For example, if the registration count reaches 90% of the maximum license count and the very next second the count reaches to 80% of
the maximum license count (due to a registration expiration), then the alarm is not cleared immediately. After 5 seconds, if the
registration count is lesser than 80% of max license count, then the alarm is cleared. This control is implemented to control the flooding
of alarms in the system.
This section contains the following Machine Congestion alarms.
sonusSbxNodeMachineCongestionNotification - MAJOR
sonusSbxNodeMemoryCongestionClearNotification - MINOR
sonusSbxNodeMemoryCongestionNotification - MAJOR
sonusSbxNodeMachineCongestionNotification - MAJOR
Type: MAJOR
Object 1.3.6.1.4.1.2879.2.10.1.1.4.0.28
ID
Descripti This alarm indicates the SBC machine congestion level changes.
on
Repetition None
sonusAlarmTime
sonusOverloadLevel
Instance None
Fields
Impact None
Clearing Manual
sonusSbxNodeMemoryCongestionClearNotification - MINOR
Type: MINOR
Obj 1.3.6.1.4.1.2879.2.10.1.1.4.0.40
ect
ID
Des When system memory utilization falls below the set threshold of approximately 65%, this alarm is raised to clear
crip sonusSbxNodeMemoryCongestionNotification.
tion
NOTE: The memory limit alarms are applicable for HW platforms of the SBC. For SBC SWe, the memory limits are pre-calculated. The
SBC SWe pre-allocates memory for small configuration when the VM memory is less than 18 GB and the large configuration when the VM
memory is 18 GB or greater. It is recommended to use large configuration when memory is 18GB or greater.
For more information, refer to SBC SWe Performance Metrics.
Rep None
etiti
on
Eve
nt 1. sonusCallCount - The number of currently active calls on the system.
Cod
es 2. sonusRegCount - The number of current active registrations on the system.
3. sonusRelayCount - The number of current active relay control blocks on the system.
Inst None
anc
e
Fiel
ds
Acti None
on
Imp Requests to initiate sessions are now accepted.

act
Cle None
aring
sonusSbxNodeMemoryCongestionNotification - MAJOR
Type: MAJOR
Obj 1.3.6.1.4.1.2879.2.10.1.1.4.0.39
ect
ID
Des This alarm indicates the system memory utilization exceeds the set threshold of approximately 70%.
crip
tion NOTE: The memory limit alarms are applicable for HW platforms of the SBC. For SBC SWe, the memory limits are pre-calculated. The
SBC SWe pre-allocates memory for small configuration when the VM memory is less than 18 GB and the large configuration when the VM
memory is 18 GB or greater. It is recommended to use large configuration when memory is 18GB or greater.
For more information, refer to SBC SWe Performance Metrics.
Rep None
etiti
on
Eve
nt 1. sonusCallCount - The number of currently active calls on the system.
Cod
es 2. sonusRegCount - The number of current active registrations on the system.
3. sonusRelayCount - The number of current active relay control blocks on the system.
Inst None
anc
e
Fiel
ds
Acti None
on
Imp No further requests to initiate sessions are accepted. New sessions shall be accepted only after some of the existing sessions terminate
act
Cle Automatic (sonusSbxNodeMemoryCongestionClearNotification). Clearing occurs when system's memory is no longer congested.
aring
This section describes the following Master Trunk Group alarms:
sonusSbxMtrmPortAvailNotification - MINOR
sonusSbxMtrmPortSwitchoverNotification - MINOR
sonusSbxMtrmPortUnAvailNotification - MAJOR
sonusSbxMtrmPortAvailNotification - MINOR
Type: MINOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.19.0.1
Description This alarm indicates that a server connection port is available. It clears the "sonusSbxMtrmPortUnAvailNotification" alarm.
Repetition None
Event Codes sonusMtrmPortIndex- MTRM connection port index.
Action None
Impact None
Clearing Manual
sonusSbxMtrmPortSwitchoverNotification - MINOR
Type: MINOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.19.0.3
Description This alarm indicates that a client connection port switches from primary to secondary.
Repetition None
Event Codes sonusMtrmPortIndex- MTRM connection port index.
Action None
Impact None
Clearing Manual
sonusSbxMtrmPortUnAvailNotification - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.19.0.2
Description This alarm indicates that a server connection port is unavailable.
Repetition None
Event Codes sonusMtrmPortIndex- MTRM connection port index
Action None
Impact MTRM messaging cannot happen through this connection port.
Clearing Automatic, sonusSbxMtrmPortAvailNotification, sonusSbxMtrmPortSwitchoverNotification
Media Port Alarms
This section contains the following Media Port alarms.
sonusSbxMediaOverFlowPacketsCleared - MAJOR
sonusSbxMediaOverFlowPacketsNotification - MAJOR
sonusTrafficProfileActivationNotification - INFORMATIONAL
sonusConfigProfileActivationNotification - INFORMATIONAL
sonusSbxNrsMediaPortDownNoLicenseClearedNotification - CRITICAL
sonusSbxNrsMediaPortDownNoLicenseNotification - CRITICAL
sonusSbxNrsMediaPortInvalidSfpClearedNotification - CRITICAL
sonusSbxNrsMediaPortInvalidSfpNotification - CRITICAL
sonusNrsNifLowWatermarkNotification - MINOR
sonusNrsNifHighWatermarkNotification - MAJOR
sonusPacketPortBWusageThresholdExceeded - MAJOR
sonusClearPacketPortclearThresholdExceeded - MAJOR
sonusSbxMediaOverFlowPacketsCleared - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.4.0.54
Description This trap indicates that there are no more over flow packets or non-confirming packets for calls during X interval defined in
system policing.
Repetition None

sonusAlarmLevel
sonusAlarmTime
Instance None
Fields
Action None
Impact None
Clearing Automatic; sonusSbxMediaOverFlowPacketsNotification
sonusSbxMediaOverFlowPacketsNotification - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.4.0.53
Description This trap indicates that overflow packets or non-Confirming packets is found for one or more calls during X interval defined in the
system policing.
Repetition None
Event Codes
sonusAlarmNodeID
sonusAlarmLevel
sonusAlarmTime
Instance None
Fields
Action Investigate the over-flow packets are dropped or by passed controlled by spikeAction configuration
Packets Discarded count - If present, indicates that the SBC drops packets
OverFlow Packet Count - If present, indicates that the SBC passes/relays non-confirming packets.
To relay/by-pass the non-confirming packets, set the spikeAction to 'alarm' using the command: system > media >
policing > spikeAction
Impact The SBC either drops the packets or passes some non-conforming packets.
Clearing Automatic; sonusSbxMediaOverFlowPacketsCleared
sonusTrafficProfileActivationNotification - INFORMATIONAL
Severity: INFORMATIONAL
Object ID 1.3.6.1.4.1.2879.2.10.1.1.4.0.55
Description This alarm indicates that there was an attempt to activate a traffic profile on a SWe/Cloud instance from the OAM.
Repetition None
Event Codes
sonusAlarmNodeID
sonusAlarmLevel
Instance Fields
sonusAlarmTime
sonusTrafficProfileActivationMsg
sonusTrafficProfileActivationStatus
Action None
Impact If the attempt is successful, the concerned traffic profile is activated.
Clearing Manual
sonusConfigProfileActivationNotification - INFORMATIONAL
Severity: INFORMATIONAL
Object ID 1.3.6.1.4.1.2879.2.10.1.1.4.0.56
Description This alarm indicates that there was an attempt to activate a Config profile on an SBC SWe / Cloud instance from the OAM.
Repetition None
Event Codes
sonusAlarmNodeID
sonusAlarmLevel
Instance Fields
sonusAlarmTime
sonusTrafficProfileActivationMsg
sonusTrafficProfileActivationStatus
Action None
Impact If the attempt is successful, the concerned Config profile is activated.
Clearing Manual
sonusSbxNrsMediaPortDownNoLicenseClearedNotification -
CRITICAL
Type: CRITICAL
Object ID 1.3.6.1.4.1.2879.2.10.1.1.11.0.24
Description The alarm indicates that the media port is no longer down due to unavailability of license..
Repetition None

sonusAlarmLevel
sonusAlarmTime
sonusNrsCeName
sonusNrsPortName

sonusNrsPortName
Action None
Impact The media port is no longer down due to unavailability of license.
Clearing Manual
sonusSbxNrsMediaPortDownNoLicenseNotification -
CRITICAL
Type: CRITICAL
Object ID 1.3.6.1.4.1.2879.2.10.1.1.11.0.23
Description This alarm is raised when the media port is down due to unavailability of license.
Repetition None

sonusAlarmLevel
sonusAlarmTime
sonusNrsCeName
sonusNrsPortName

sonusNrsPortName
Action Add the appropriate media port license.
Impact The port remains down until the license is present.
Clearing Automatic; sonusSbxNrsMediaPortDownNoLicenseClearedNotification
sonusSbxNrsMediaPortInvalidSfpClearedNotification -
CRITICAL
Type: CRITICAL
Object ID 1.3.6.1.4.1.2879.2.10.1.1.11.0.26
Description The alarm indicates an invalid SFP is no longer plugged into the port.
Repetition None

sonusAlarmLevel
sonusAlarmTime
sonusNrsCeName
sonusNrsPortName
sonusNrsInvalidSfpReason

sonusNrsPortName
Action None
Impact None
Clearing Manual
sonusSbxNrsMediaPortInvalidSfpNotification - CRITICAL
Type: CRITICAL
Object ID 1.3.6.1.4.1.2879.2.10.1.1.11.0.25
Description The alarm indicates an invalid SFP is installed in the specified port. SFP failure reasons:
1. Incorrect speed for the port

2. Non-Sonus SFP installed
Execute the packetPortStatus command to check the failure reason.
Repetition None

sonusAlarmLevel
sonusAlarmTime
sonusNrsCeName
sonusNrsPortName

sonusNrsPortName
Action Replace the SFP with a valid SFP for that port.
Impact The port remains down until valid SFP is inserted.
Clearing Automatic; sonusSbxNrsMediaPortInvalidSfpClearedNotification
sonusNrsNifLowWatermarkNotification - MINOR
Type: MINOR (currently not supported on the SBC)
Object ID 1.3.6.1.4.1.2879.2.10.1.1.11.0.28
Description This trap indicates that a NIF's low watermark has been reached the first time since the NIF's high watermark has been
reached.
Repetition None
Event Codes
sonusAlarmNodeID
sonusAlarmLevel
sonusAlarmTime
sonusNifPort
sonusNifIndex
sonusNrsPortName
Instance
Fields sonusNifPort
sonusNifIndex
sonusNrsPortName
Action None
Impact None
Clearing Manual
sonusNrsNifHighWatermarkNotification - MAJOR
Type: MAJOR (currently not supported by the SBC)
Object ID 1.3.6.1.4.1.2879.2.10.1.1.11.0.27
Description This trap indicates that a NIF's high watermark has been reached the first time since the NIF's low watermark has been
reached.
Repetition None
Event Codes
sonusAlarmNodeID
sonusAlarmLevel
sonusAlarmTime
sonusNifPort
sonusNifIndex
sonusNrsPortName
Instance
Fields sonusNifPort
sonusNifIndex
sonusNrsPortName
Action None
Impact None
Clearing Yes
sonusPacketPortBWusageThresholdExceeded - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.36.0.1
Description The Bandwidth Usage exceeds a maximum threshold of 95%..
Repetition No
Event Codes
sonusAlarmNodeID
sonusAlarmLevel
sonusAlarmTime
sonusAlarmPortName
Instance Fields
sonusAlarmPortName
Action An issue in the network may prevent the creation of new call contexts.
Impact BW utilization is reaching the maximum capacity. The SBC may not be able to create new call contexts.
Clearing Automatic; sonusClearPacketPortBWusageThresholdExceeded
sonusClearPacketPortclearThresholdExceeded - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.36.0.2
Description The alarm is generated when the Bandwidth Usage returns with a threshold under 90%.
Repetition No
Event Codes
sonusAlarmNodeID
sonusAlarmLevel
sonusAlarmTime
sonusAlarmPortName
Instance Fields
sonusAlarmPortName
Action None
Impact The BW utilization on the packet port is within the configured threshold.
Clearing Manual

This section contains the following Media Port alarms.
sonusSbxLvmPhyPacketPortDownNotification - MAJOR
sonusSbxLvmPhyPacketPortUpNotification - MAJOR
sonusSbxLvmPrimaryPhyPacketPortActiveNotification - MAJOR
sonusSbxLvmSecondaryPhyPacketPortActiveNotification - MAJOR
Note
Currently, these alarms are applicable only to SBC 7000 and SBC SWe on OpenStack platforms.
sonusSbxLvmPhyPacketPortDownNotification - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.21.0.1
Description The alarm indicates the physical packet port is down.
Repetition None

sonusAlarmLevel
sonusAlarmTime
sonusNrsCeName
sonusNrsPortName
Action Determine the cause of the port going down and correct it.
Impact No new calls can be made on the ports. Media for existing calls is lost.
Clearing Automatic; sonusSbxLvmPhyPacketPortUpNotification
sonusSbxLvmPhyPacketPortUpNotification - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.21.0.2
Description The physical packet port is up.
Repetition None

sonusAlarmLevel
sonusAlarmTime
sonusNrsCeName
sonusNrsPortName
Instance Fields Nones
Action None
Impact Calls can use the port.
Clearing Manual
sonusSbxLvmPrimaryPhyPacketPortActiveNotification -
MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.21.0.3
Description The trap indicates the primary physical packet port is now ACTIVE.
Repetition None
Event Codes
sonusAlarmNodeID
sonusAlarmLevel
sonusAlarmTime
sonusNrsCeName
sonusNrsPortName
sonusLvmPortSwitchReason
Action Investigate link failure (if indicated) on the secondary port.
Impact None
Clearing Manual
sonusSbxLvmSecondaryPhyPacketPortActiveNotification -
MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.21.0.4
Description The trap indicates the secondary physical packet port is made ACTIVE.
Repetition None

sonusAlarmLevel
sonusAlarmTime
sonusNrsCeName
sonusNrsPortName
sonusLvmPortSwitchReason
Action Investigate link failure on primary port if indicated.
Impact None
Clearing Manual
Monitoring Alarms
This section contains the following SIP Monitoring alarms.
sonusSbxSipSmMonServerTcpConnFailureNotification - MAJOR
sonusSbxSipSmMonServerTcpConnFailureNotificationV6 - MAJOR
sonusSbxSipSmMonServerTcpConnFailureNotification -
MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.1.0.62
Description This alarm is raised when a TCP connection to a particular monitoring server is not established after three failed attempts
(IPV4).
Repetition Yes
Event Codes
sonusAlarmNodeID
sonusAlarmLevel
sonusAlarmTime
sonusAlarmDescriptin
sonusMonIpAddress
sonusMonPortNum
Instance
Fields sonusMonIpAddress
sonusMonPortNum
Action Re-establish the TCP connection.
Note
Manually disable or enable the monitoring profile state after taking corrective actions.
Impact The SBC cannot stream SIP PDUs to the monitoring server since the TCP connection is not established.
Clearing Manual
sonusSbxSipSmMonServerTcpConnFailureNotificationV6 -
MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.1.0.63
Description This alarm is raised when the TCP connection to a particular monitoring server is not established after three failed attempts
(IPv6).
Repetition Yes
Event Codes
sonusAlarmNodeID
sonusAlarmLevel
sonusAlarmTime
sonusMonIpAddressV6
sonusMonPortNum
Instance
Fields sonusMonIpAddressV6
sonusMonPortNum
Action Re-establish the TCP connection.
Note
Manually disable or enable the monitoring profile state after taking correction actions.
Impact The SBC cannot stream SIP PDUs to the monitoring server since the TCP connection is not established.
Clearing Manual
This section contains the following Network Management Alarms.
sonusSbxLbsLocalNodeIsLeaderLackOfCommuncationNotification - CRITICAL
sonusSbxLbsLocalNodeIsLeaderLackOfCommuncationNotificationV6 - CRITICAL
sonusSbxNetMgmtClientInformReqQueueFlushedNotification - MAJOR
sonusSbxNetMgmtClientInformReqQueueFullNotification - MAJOR
sonusSbxSipSmDropLargeSipPduOverUdpNotification - MAJOR
sonusSbxSipSmDropLargeSipPduOverUdpNotificationV6 - MAJOR
sonusSbxLbsLocalNodeIsLeaderLackOfCommuncationNotification
Type: CRITICAL
Object ID 1.3.6.1.4.1.2879.2.10.1.1.1.0.70
Description This alarm indicates that the local node elected as leader due to lack of communication with other instances in a cluster.
Repetition None
Event Codes
sonusAlarmNodeID
sonusAlarmLevel
sonusAlarmTime
Instance Fields sonusMsbcIpAddress
Action None
Impact None
Clearing Manual
sonusSbxLbsLocalNodeIsLeaderLackOfCommuncationNotification
Type: CRITICAL
Object ID 1.3.6.1.4.1.2879.2.10.1.1.1.0.71
Description This alarm indicates that the local node elected as leader due to lack of communication with other instances in a cluster for
IPv6
Repetition None
Event Codes
sonusAlarmNodeID
sonusAlarmLevel
sonusAlarmTime
Instance sonusMsbcIpAddressv6
Fields
Action None
Impact None
Clearing Manual
sonusSbxNetMgmtClientInformReqQueueFlushedNotification - MAJ
Type: MAJOR
Ob 1.3.6.1.4.1.2879.2.10.1.1.8.0.1
jec
t
ID
De The trap indicates the specified number of InformRequest PDUs destined to the specified Management Client were flushed from the
sc InformRequest PDU queue because no Response PDUs were received from the Management Client.
rip
tion This situation can occur if the Management Client cannot quickly process and respond to InformRequest PDUs that it receives, or if
communications is lost with the Management Client.
Re None
pe
titi
on
Ev
en sonusNetMgmtClientName
t sonusNetMgmtInformReqDiscards
Co
des
In None
st
an
ce
Fi
el
ds
Ac If this situation occurs occasionally, it is recommended to increase the InformRequest PDU timeout and/or retry values (see
tion sonusNetMgmtClientInformReqRspTimeout and sonusNetMgmtClientInformReqRetries.)
If this situation occurs repeatedly, it is an indication that communication is lost with the Management Client, either because of network
problems, or because the Management Client is no longer operational. It is recommended that this device be configured to send a alarm
PDU, not an InformRequest PDU, for this Notification to all Management Clients, thus bypassing a problematic InformRequest PDU queue
and allowing the situation to be quickly identified and resolved.
Im None
pa
ct
Cl Manual
ea
ring
sonusSbxNetMgmtClientInformReqQueueFullNotification -
MAJOR
Type: MAJOR
Object 1.3.6.1.4.1.2879.2.10.1.1.8.0.2
ID
Descri The trap indicates the specified number of InformRequest PDUs destined to the specified Management Client were discarded because
ption the InformRequest PDU queue is full.
This situation can occur if the Management Client does not quickly process and respond to the received InformRequest PDUs, or if
communication with the Management Client is lost.
Repetit None
ion
Event sonusNetMgmtClientName
Codes sonusNetMgmtInformReqDiscards
Instanc None
e
Fields
Action Take the following actions, as appropriate:
If this situation occurs occasionally, increase the InformRequest PDU queue size (refer to
sonusNetMgmtClientInformReqMaxQueue).
If this situation occurs repeatedly, it is an indication that communications is lost with the Management Client, either because of
network problems, or because the Management Client is no longer operational.
Ribbon recommends to configure this device to send an alarm PDU for this notification (not an InformRequest PDU) to all Management
Clients, thus bypassing a problematic InformRequest PDU queue for quick identification and resolution.
Impact The specified number of InformRequest PDUs destined to the specified Management Client are discarded.
Clearing Manual
sonusSbxSipSmDropLargeSipPduOverUdpNotification -
MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.1.0.68
Description This trap indicates that the SBC drops large PDUs (more than 4,096 bytes) over UDP towards the monitoring server (IPv4).
Repetition None
Event Codes
sonusAlarmNodeID
sonusAlarmLevel
sonusAlarmTime
Instance Fields
sonusMonIpAddress
sonusMonPortNum
Action None
Impact The large PDUs are dropped over UDP.
Clearing Manual
sonusSbxSipSmDropLargeSipPduOverUdpNotificationV6 -
MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.1.0.69
Description This trap indicates that large PDUs (more than 4,096 bytes) are dropped over UDP towards the monitoring server (IPv6).
Repetition None
Event Codes
sonusAlarmNodeID
sonusAlarmLevel
sonusAlarmTime
Instance Fields
sonusMonIpAddress
sonusMonPortNum
Action None
Impact The large PDUs are dropped over UDP.
Clearing Manual
Node Alarms
This section contains the following Node alarms.
sonusCpNodeBondingDeviceDownNotification - CRITICAL
sonusCpNodeBondingDeviceUpNotification - MAJOR
sonusCpNodeHaPortDownNewNotification - MAJOR
sonusCpNodeHaPortUpNotification - MAJOR
sonusCpNodeStandbyDisabled - MAJOR
sonusCpNodeStandbyEnabled - MAJOR
sonusSbxNodeInServiceNotification - MAJOR
sonusSbxNodeOutOfServiceNotification - MAJOR
sonusSbxNodePolicerClearAlarmNotification - MINOR
sonusSbxNodePolicerMajorAlarmNotification - MAJOR
sonusSbxNodePolicerMinorAlarmNotification - MINOR
sonusCpNodeBondingDeviceDownNotification - CRITICAL
Type: CRITICAL
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.5.0.42
Description This alarm indicates that the bonding device is down.
Repetition None
Action Determine the cause of the bonding device down and correct it.
Impact Communication between the active and standby computes elements is lost.
Clearing Automatic, sonusCpNodeBondingDeviceUpNotification
sonusCpNodeBondingDeviceUpNotification - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.5.0.43
Description This alarm indicates that the bonding device is up.
Repetition None
Action None
Impact Communication over the bonding device is normal.
Clearing Automatic
sonusCpNodeHaPortDownNewNotification - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.5.0.44
Description This alarm indicates that a high availability (HA) port is down.
Repetition None
Codes sonusCpSystemPortName
Instance None
Fields
Action Determine the cause of the port down and correct it.
Impact One of the two high availability ports are down. If the other goes down then communication between the active and standby
computes elements are lost.
Clearing Automatic; sonusCpNodeHaPortUpNotification
sonusCpNodeHaPortUpNotification - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.5.0.41
Description This alarm indicates that a high availability port is up.
Repetition None

sonusAlarmNodeID
sonusAlarmLevel
sonusAlarmTime
Instance Fields sonusCpSystemPortName

sonusCpSystemPortName
Action None
Impact Communication over the high availability port is normal.
Clearing Manual
sonusCpNodeStandbyDisabled - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.5.0.38
Description This alarm indicates that the node standby server is disabled.
Repetition None
Impact Node will be running in unprotected mode.
Clearing Automatic; sonusCpNodeStandbyEnabled
sonusCpNodeStandbyEnabled - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.5.0.39
Description This alarm indicates that the node standby server is enabled.
Repetition None
Action None
Impact Node will be running in protected mode.
Clearing Manual
sonusSbxNodeInServiceNotification - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.4.0.48
Description This alarm indicates that the system is in service.
Repetition None
Event Codes None
Instance Fields sonusAlarmNodeID

sonusAlarmLevel
sonusAlarmTime
Action None
Impact Calls to the system are allowed.
Clearing Automatic; sonusSbxNodeOutOfServiceNotificatio
sonusSbxNodeOutOfServiceNotification - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.4.0.44
Description This alarm indicates that the system is out of service.
Repetition None
Event Codes None

sonusAlarmLevel
sonusAlarmTime
Action None
Impact Calls to the system are not allowed.
Clearing Automatic; sonusSbxNodeInServiceNotification
sonusSbxNodePolicerClearAlarmNotification - MINOR
Type: MINOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.9.0.3
Description The alarm indicates that a system policer alarm is cleared.
Repetition None
Event Codes sonusPolicerTypeStr
Action None
Impact None
Clearing Manual
sonusSbxNodePolicerMajorAlarmNotification - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.9.0.2
Description The alarm indicates a system policer major level alarm.
Repetition None

sonusPolicerLevelStr
Action None
Impact None
Clearing Automatic, sonusSbxNodePolicerClearAlarmNotification
sonusSbxNodePolicerMinorAlarmNotification - MINOR
Type: MINOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.9.0.1
Description This alarm indicates a system policer minor level alarm.
Repetition None

sonusPolicerLevelStr
Action None
Impact None
Clearing Manual
This section contains the following Node Resources alarms.
sonusSbxNodeResEmerCallNoRouteNotification - MAJOR
sonusSbxNodeResourceCallTraceActiveNotification - INFORMATIONAL
sonusSbxNodeResourceCallTraceDisabledNotification - INFORMATIONAL
sonusSbxNodeResourceCallTraceResetNotification - INFORMATIONAL
sonusSbxNodeResourceCallTraceSignalingDisabledNotification - INFORMATIONAL
sonusSbxNodeResourceCallTraceSignalingEnabledNotification - INFORMATIONAL
sonusSbxNodeResourcesCallAdmissionEnabledNotification - MAJOR
sonusSbxNodeResourcesCallAdmissionSuspendedNotification - MAJOR
sonusSbxNodeResourcesCallTraceHitGAPNotification - INFORMATIONAL
sonusSbxNodeResourcesCallTraceHitNotification - INFORMATIONAL
sonusSbxNodeResourcesFeatureKeyStateChangeNotification - MAJOR
sonusSbxNodeResourcesMaxIpCallLimitClearNotification - MAJOR
sonusSbxNodeResourcesMaxIpCallLimitSetNotification - MAJOR
sonusSbxNodeResourcesMaxSysCallLimitClearNotification - MAJOR
sonusSbxNodeResourcesMaxSysCallLimitSetNotification - MAJOR
sonusSbxNodeResourcesMaxTcpMediaSessLimitClearNotification - MAJOR
sonusSbxNodeResourcesMaxTcpMediaSessLimitSetNotification - MAJOR
sonusSbxNodeResourcesMediaPortRangeExhaustionClearedNotfication - MAJOR
sonusSbxNodeResourcesMediaPortRangeExhaustionNotification - MAJOR
sonusSbxNodeResourcesNoPacketsReceivedClearNotification - MINOR
sonusSbxNodeResourcesNoPacketsReceivedNotification - MAJOR
sonusSbxNodeResourcesPacketLossThresholdClearNotification - MINOR
sonusSbxNodeResourcesPacketLossThresholdExceededNotification - MAJOR
sonusSbxNodeResourcesSysACLLimitNotification - MAJOR
sonusSbxNodeResourcesTcpPortRangeExhaustionClearedNotification - MAJOR
sonusSbxNodeResourcesTcpPortRangeExhaustionNotification - MAJOR
sonusSbxNodeResEmerCallNoRouteNotification - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.4.0.5
Description This trap indicates that for a given emergency call the SBC is unable to route the call on any of the provided routes. This is a
warning indicator of a failed emergency call.
Repetition None
Event sonusActiveCallIngressPstnTrunk—For calls originating from PSTN (circuit) side, specifies the Trunk Group name to which the
Codes Ingress PSTN channel belongs.
sonusNodeResourceIsupCircuit—Base circuit identity code (CIC) for the circuit.
sonusActiveCallCallingNum—The E.164 number representing the calling party's telephone number.
sonusActiveCallCalledNum—The E.164 number representing the called party's telephone number.
sonusActiveCallOrigCalledNum—If an address translation is performed on the called party number, this entry contains the original,
untranslated number.
Instance None
Fields
Action Investigate why the calls are failing
Impact Emergency calls will not route
Clearing Manual
sonusSbxNodeResourceCallTraceActiveNotification -
INFORMATIONAL
Type: INFORMATIONAL
Object ID 1.3.6.1.4.1.2879.2.10.1.1.4.0.30
Description This alarm indicates that call trace has started.
Repetition None
Event Codes CALLTRACE_ACTIVE 114
Instance None
Fields
Action None
Impact None
Clearing Automatic, sonusSbxNodeResourceCallTraceDisabledNotification,

sonusSbxNodeResourceCallTraceSignalingDisabledNotification
sonusSbxNodeResourceCallTraceDisabledNotification -
INFORMATIONAL
Type: INFORMATIONAL
Object ID 1.3.6.1.4.1.2879.2.10.1.1.4.0.29
Description This alarm indicates that call trace has stopped either due to maxTriggerCount reach or callTraceTimer expiry.
Repetition None
Event Codes CALLTRACE_DISABLED 113
Action None
Impact None
Clearing None
sonusSbxNodeResourceCallTraceResetNotification -
INFORMATIONAL
Type: INFORMATIONAL
Object ID 1.3.6.1.4.1.2879.2.10.1.1.4.0.62
Description This trap is generated when the command "request global callTrace action command start" is issued and there is already an
active call trace filter.
Repetition None
Event Codes
sonusAlarmNodeID
sonusAlarmLevel
sonusAlarmTime
Instance None
Fields
Action None
Impact Clears any previous sonusSbxNodeResourceCallTraceActiveNotification traps.
Clearing Automatic; sonusSbxNodeResourceCallTraceActiveNotification
sonusSbxNodeResourceCallTraceSignalingDisabledNotification - IN
Type: INFORMATIONAL
Object ID 1.3.6.1.4.1.2879.2.10.1.1.4.0.41
Description This trap indicates that the signaling packet capture is disabled/inactive.
Repetition None
Event Codes
sonusAlarmNodeID
sonusAlarmLevel
sonusAlarmTime
sonusCallTraceDisableReason
Instance Fields
sonusCallTraceDisableReason
Action None
Impact None
Clearing Manual
sonusSbxNodeResourceCallTraceSignalingEnabledNotification - IN
Type: INFORMATIONAL
Object ID 1.3.6.1.4.1.2879.2.10.1.1.4.0.42
Description This trap indicates that the signaling packet capture has started.
Repetition None
Event Codes
sonusAlarmNodeID
sonusAlarmLevel
sonusAlarmTime
Action None
Impact None
Clearing Manual
sonusSbxNodeResourcesCallAdmissionEnabledNotification
- MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.4.0.2
Descripti This alarm indicates that call admission into the SBC has been suspended. Information provided by this alarm includes one of the
on following reasons why call admission was previously disabled:
NTP timing not available following system initialization

Transient call cleanup following switchover
Repetition None
Event sonusCallAdmissionChangeReason
Codes
Instance None
Fields
Action Investigate based on the reason for suspension and correct problem.
Impact None
Clearing Manual
sonusSbxNodeResourcesCallAdmissionSuspendedNotification - M
Type: MAJOR
Obj 1.3.6.1.4.1.2879.2.10.1.1.4.0.1
ect
ID
Des This alarm indicates that call admission into the SBC Core server has been suspended. Information provided by this trap includes one of
crip the following reasons why call admission is suspended:
tion
Critical system overload
NTP timing not available following system initialization
Transient call cleanup following a switchover
Rep None
etiti
on
Eve sonusAlarmNodeID
nt sonusAlarmLevel
Cod sonusAlarmSequenceId
es sonusAlarmTime
sonusCallAdmissionChangeReason
Inst sonusCallAdmissionChangeReason
anc
e
Fiel
ds
Acti Investigate based on the reason for the suspension, and correct problem.
on
Imp No calls are admitted to the system or the affected server card while call admission is suspended.
act
For the case where a valid NTP source is not available following system initialization, call admission is suspended until a valid NTP time
reference is obtained. This action is taken to ensure that accounting records may be generated with the correct time of day. For other
cases, call admission is suspended for a short time and the condition does not require any operator action.
For example, during card failover processing, call admission is suspended briefly as the standby card transitions to the active state. Call
admission is resumed as soon as the card has completed the transition and is ready to accept new call arrivals.
Cle Automatic, sonusSbxNodeResourcesCallAdmissionEnabledNotification

aring
sonusSbxNodeResourcesCallTraceHitGAPNotification -
INFORMATIONAL
Type: INFORMATIONAL
Object 1.3.6.1.4.1.2879.2.10.1.1.4.0.4
ID
Descri This trap indicates that the call trace filter has found a match based upon the user's filter criteria. Information provided by this alarm
ption includes the called number, calling number, and original called number for a Generic Access Profile (GAP).
Repetit None
ion
Event sonusCallTraceCalledNumber—The called number being traced.

Codes sonusCallTraceCallingNumber—The calling number being traced.
sonusActiveCallOrigCalledNum—If an address translation has been performed on the called party number, this entry contains the
original, untranslated number.
Instanc None
e
Fields
Action None
Impact None
Clearing Manual
sonusSbxNodeResourcesCallTraceHitNotification -
INFORMATIONAL
Type: INFORMATIONAL
Object ID 1.3.6.1.4.1.2879.2.10.1.1.4.0.3
Descripti This trap indicates that the call trace filter has found a match based upon the user's filter criteria. Information provided by this alarm
on includes the called number, calling number, and original called number.
Repetition None
Event sonusCallTraceCalledNumber—The called number being traced.

Codes sonusCallTraceCallingNumber—The calling number being traced.
Instance None
Fields
Action None
Impact None
Clearing Manual
sonusSbxNodeResourcesFeatureKeyStateChangeNotification - MA
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.4.0.10
Description This trap indicates there is a change in the feature key state for the associated sonusFeatureName resulting from applying or
removing a license key.
Repetition None
Event Codes
sonusFeatureName —Name of the feature
sonusFeatureState —State of the specified feature
Instance None
Fields
Action None
Impact The specified feature is enabled/disabled.
Clearing Manual
sonusSbxNodeResourcesMaxIpCallLimitClearNotification -
MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.4.0.7
Description This alarm indicates that 10 consecutive IP calls have been successfully accepted into the system.
Repetition None
Event Codes None
Action None
Impact None
Clearing Manual
sonusSbxNodeResourcesMaxIpCallLimitSetNotification -
MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.4.0.6
Description This alarm indicates that MAX IP Call Limit has been reached.
Repetition None
Event Codes None
Action None
Impact New incoming IP calls will be rejected. As existing calls terminate, new calls will be accepted.
Clearing Automatic, sonusSbxNodeResourcesMaxIpCallLimitClearNotification
sonusSbxNodeResourcesMaxSysCallLimitClearNotification -
MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.4.0.9
Description This alarm indicates the maximum system call limit cleared.
Repetition None
Event Codes None
Action None
Impact None
Clearing Manual
sonusSbxNodeResourcesMaxSysCallLimitSetNotification -
MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.4.0.8
Description This alarm indicates the maximum system call limit set.
Repetition None
Event Codes None
Action None
Impact New incoming calls will get rejected. As existing calls terminate, new calls will be accepted.
Clearing Automatic, sonusSbxNodeResourcesMaxSysCallLimitClearNotification
sonusSbxNodeResourcesMaxTcpMediaSessLimitClearNotification
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.4.0.32
Description This alarm indicates that the TCP media sessions have dropped below lower threshold.
Repetition None
Event Codes None
Action None
Impact None
Clearing Manual
sonusSbxNodeResourcesMaxTcpMediaSessLimitSetNotification - M
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.4.0.31
Description This alarm indicates that the TCP media sessions reached the maximum media session limit.
Repetition None
Event Codes None
Action None
Impact New incoming TCP media sessions are not accepted. As the existing sessions terminate, new sessions are accepted.
Clearing Automatic, sonusSbxNodeResourcesMaxTcpMediaSessLimitClearNotification
sonusSbxNodeResourcesMediaPortRangeExhaustionClearedNotfic
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.4.0.35
Description The alarm indicates that media port range is no longer exhausted.
Repetition None

sonusAlarmLevel
sonusAlarmTime
sonusTgName
Instance Fields sonusTgName
Action None
Impact The ports are available for new UDP media sessions.
Clearing None
sonusSbxNodeResourcesMediaPortRangeExhaustionNotification -
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.4.0.34
Description The alarm indicates that the Media Port Range has been exhausted.
Repetition None

sonusAlarmLevel
sonusAlarmTime
sonusTgName
Action Configure a larger media port range for the Trunk Group.
Impact New UDP media sessions will fail.
Clearing Automatic; sonusSbxNodeResourcesMediaPortRangeExhaustionClearedNotification
sonusSbxNodeResourcesNoPacketsReceivedClearNotification - MI
Type: MINOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.4.0.21
Description This alarm indicates that the peer has resumed sending RTP or RTCP packets.
Repetition None

sonusAlarmLevel
sonusAlarmTime
sonusNrmaCallGcid
Action None
Impact None
Clearing Automatic, sonusSbxNodeResourcesNoPacketsReceivedNotification
sonusSbxNodeResourcesNoPacketsReceivedNotification -
MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.4.0.20
Description This alarm indicates that no RTP or RTCP packets were received from peer.
Repetition None

sonusAlarmLevel
sonusAlarmTime
sonusNrmaCallGcid
Action Investigate if the peer is still participating in the session.
Impact May impact the media session.
Clearing Automatic, sonusSbxNodeResourcesNoPacketsReceivedClearNotification
sonusSbxNodeResourcesPacketLossThresholdClearNotification - M
Type: MINOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.4.0.19
Description This alarm indicates that the RTP packet loss has fallen below the configured threshold level.
Repetition None
Event Codes
sonusAlarmNodeID
sonusAlarmLevel
sonusAlarmTime
sonusNrmaCallGcid
Impact None.
Clearing Automatic, sonusSbxNodeResourcesPacketLossThresholdExceededNotification
sonusSbxNodeResourcesPacketLossThresholdExceededNotificatio
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.4.0.18
Description This alarm indicates that the RTP packet loss has exceeded the configured threshold level.
Repetition None
Event Codes
sonusAlarmNodeID
sonusAlarmLevel
sonusAlarmTime
sonusNrmaCallGcid
Action Investigate the network condition or peer status.
Impact May impact the media or signaling path.
Clearing Automatic, sonusSbxNodeResourcesPacketLossThresholdClearNotification
Note
Refer to RTCP Options for details on configuing packetLossThreshold.
sonusSbxNodeResourcesSysACLLimitNotification - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.4.0.33
Description This alarm is generated when an error is encountered while creating a system ACL for a TCP media session. This error may occur
when the system reaches the maximum ACL limit.
Repetition None
sonusAlarmTime
Instance None
Fields
Action Configure user ACLs through CLI or EMA for TCP media endpoint.
Impact New TCP media sessions are failed unless the user ACLs are configured through CLI or EMA.
Clearing Manual
sonusSbxNodeResourcesTcpPortRangeExhaustionClearedNotifica
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.4.0.37
Description This alarm indicates the TCP port range is no longer exceeded (exhausted).
Repetition None

sonusAlarmLevel
sonusAlarmTime
sonusTgName
Action None
Impact The ports are available for new TCP media sessions.
Clearing Automatic; sonusSbxNodeResourcesTcpPortRangeExhaustionNotification
sonusSbxNodeResourcesTcpPortRangeExhaustionNotification - M
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.4.0.36
Description This alarm indicates that the TCP Port Range is exceeded (exhausted). TCP port range values between 1-65534 are allowed.
Refer to Media - TCP Port Range for details.
Repetition None

sonusAlarmLevel
sonusAlarmTime
sonusTgName
Action Configure a larger TCP port range for the Trunk Group.
Impact New TCP media sessions fail.
Clearing Automatic: sonusSbxNodeResourcesTcpPortRangeExhaustionCleared
trap
OAM Node Alarms

This section contains the following OAM node alarms.
sonusSbxManagedNodeAbleToReceiveConfigUpdates - MAJOR
sonusSbxManagedNodeConfigChangeListApplyFailed - MAJOR
sonusSbxManagedNodeConfigChangeListApplySucceeded - MAJOR
sonusSbxManagedNodeUnableToReceiveConfigUpdates - MAJOR
sonusSbxManagedNodeAbleToReceiveConfigUpdates -
MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.29.0.2
Description Managed node is able to receive config update/revert requests from the OAM node.
Repetition This clearing alarm is raised when a managed node can access configuration changes on the OAM node.
Event Codes EV_MANAGED_NODE_ABLE_TO_RECEIVE_CONFIG_UPDATES
Instance Fields ManagedNodeCeName
Action None
Impact Configuration is in sync - the configuration on the managed node is in sync with the OAM node.
Clearing This clearing alarm clears the alarm sonusSbxManagedNodeUnableToReceiveConfigUpdates
sonusSbxManagedNodeConfigChangeListApplyFailed -
MAJOR
Type: MAJOR
Objec 1.3.6.1.4.1.2879.2.10.1.1.29.0.3
t ID
Descr A managed node fails to apply configuration changes to replay the configuration change list.
iption
Repet This alarm is raised for each occurence when a managed node fails to replay the configuration change list.
ition
Event EV_MANAGED_NODE_CONFIG_CHANGE_LIST_APPLY_FAILED
Codes
Insta ManagedNodeCeName
nce
Fields
Action Determine the reason why managed node failed to replay the config change list. May require reboot of the managed node. Can use
the EMS Restore function to revert to a prior configuration. Refer to Reviewing Configuration Changes and Reverting Configuration
(OAM Mode).
Impact Configuration on the managed node is out of sync with the OAM node.
Cleari Automatic; sonusSbxManagedNodeConfigChangeListApplySucceeded

ng
sonusSbxManagedNodeConfigChangeListApplySucceeded -
MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.29.0.4
Description A managed node successfully applied configuration changes to replay the configuration change list.
Repetition This clearing alarm is raised when a managed node successfully replays the configuration change list.
Event Codes EV_MANAGED_NODE_CONFIG_CHANGE_LIST_APPLY_SUCCEEDED
Instance Fields ManagedNodeCeName
Action None
Impact Configuration on the managed node is in sync with the OAM node.
Clearing Automatic; sonusSbxManagedNodeConfigChangeListApplyFailed
sonusSbxManagedNodeUnableToReceiveConfigUpdates -
MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.29.0.1
Description Managed node is unable to receive config update/revert requests from the OAM node.
Repetition This alarm is raised when a managed node cannot access configuration changes on the OAM node.
Event Codes EV_MANAGED_NODE_UNABLE_TO_RECEIVE_CONFIG_UPDATES
Instance ManagedNodeCeName
Fields
Action Determine the reason why managed node cannot access the config update/revert requests on the OAM node.
Impact Configuration on the managed node may get out of sync with the OAM node if the saveAndActivate command is executed
in this state.
Clearing Cleared by the clearing alarm sonusSbxManagedNodeAbleToReceiveConfigUpdates
Path Check Alarms
This section contains the following Path Check alarms.
sonusSbxPathCheckFqdnPeerDownNotification2 - MINOR
sonusSbxPathCheckFqdnPeerIpEndpointDownNotification2 - MINOR
sonusSbxPathCheckFqdnPeerIpEndpointUpNotification2 - MINOR
sonusSbxPathCheckFqdnPeerIpV6EndpointDownNotification2 - MINOR
sonusSbxPathCheckFqdnPeerIpV6EndpointUpNotification2 - MINOR
sonusSbxPathCheckFqdnPeerUpNotification2 - MINOR
sonusSbxPathCheckLocalAdminStateDownNotification2 - MAJOR
sonusSbxPathCheckLocalAdminStateDownNotification2V6 - MAJOR
sonusSbxPathCheckLocalAdminStateUpNotification2 - MAJOR
sonusSbxPathCheckLocalAdminStateUpNotification2V6 - MAJOR
sonusSbxPathCheckPingStateDownNotification2 - MAJOR
sonusSbxPathCheckPingStateDownNotification2V6 - MAJOR
sonusSbxPathCheckPingStateUpNotification2 - MAJOR
sonusSbxPathCheckPingStateUpNotification2V6 - MAJOR
sonusSbxPathCheckRemoteAdminStateDownNotification2 - MAJOR
sonusSbxPathCheckRemoteAdminStateDownNotification2V6 - MAJOR
sonusSbxPathCheckRemoteAdminStateUpNotification2 - MAJOR
sonusSbxPathCheckRemoteAdminStateUpNotification2V6 - MAJOR
sonusSbxPathCheckFqdnPeerDownNotification2 - MINOR
Type: MINOR
Object Id 1.3.6.1.4.1.2879.2.10.1.1.1.0.90
Description This alarm indicates that the specified SIP peer is unavailable to receive calls.
Repetition None
Event Codes EVENT_PATHCHK_FQDN_PEER_DOWN
Instance Fields
sonusAlarmNodeID
sonusAlarmLevel
sonusAlarmTime
sonusPingPeerFqdn
sonusPingPeerPortNum
sonusPingPeerZoneId
sonusPingPeerZoneName
sonusPingPeerName
Action Ensure that the SIP peer is available to receive SIP calls and is reachable.
Impact The specified endpoint are bypassed when routing SIP calls.
Clearing Manual
sonusSbxPathCheckFqdnPeerIpEndpointDownNotification2 -
MINOR
Type: MINOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.1.0.92
Description This alarm indicates that the specified IPv4 end-point belonging to the SIP Peer is unavailable to receive calls.
Repetition None
Event Codes EVENT_PATHCHK_FQDN_PEER_IP_ENDPOINT_DOWN
Instance Fields
sonusAlarmNodeID
sonusAlarmLevel
sonusAlarmTime
sonusPingPeerIpAddress
sonusPingPeerFqdn
sonusPingPeerZoneId
sonusPingPeerName
Action Ensure that the IP end-point is available to receive SIP calls and is reachable.
Impact The specified IP end-point will be bypassed while routing SIP calls.
Clearing Manual
sonusSbxPathCheckFqdnPeerIpEndpointUpNotification2 -
MINOR
Type: MINOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.1.0.91
Description This alarm indicates that the specified IPv4 end-point belonging to the SIP Peer is available to receive calls.
Repetition None
Event Codes EVENT_PATHCHK_FQDN_PEER_IP_ENDPOINT_UP
Instance Fields
sonusAlarmNodeID
sonusAlarmLevel
sonusAlarmTime
sonusPingPeerFqdn
sonusPingPeerZoneId
sonusPingPeerName
Action None
Impact The specified IP end-point is no longer bypassed while routing SIP calls.
Clearing Automatic; sonusSbxPathCheckFqdnPeerIpEndpointDownNotification2
sonusSbxPathCheckFqdnPeerIpV6EndpointDownNotification2 - MI
Type: MINOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.1.0.94
Description This alarm indicates that the specified IPv6 end-point belonging to the SIP Peer is unavailable to receive calls.
Repetition None
Event Codes EVENT_PATHCHK_FQDN_PEER_IPV6_ENDPOINT_DOWN
Instance Fields
sonusAlarmNodeID
sonusAlarmLevel
sonusAlarmTime
sonusPingPeerIpAddressV6
sonusPingPeerFqdn
sonusPingPeerZoneId
sonusPingPeerName
Action Ensure that the IP end-point is available to receive SIP calls and is reachable.
Impact The specified IP end-point is bypassed while routing SIP calls.
Clearing Manual
sonusSbxPathCheckFqdnPeerIpV6EndpointUpNotification2 -
MINOR
Type: MINOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.1.0.93
Description This alarm indicates that the specified IPv6 end-point belonging to the SIP Peer is available to receive calls.
Repetition None
Event Codes EVENT_PATHCHK_FQDN_PEER_IPV6_ENDPOINT_UP
Instance Fields
sonusAlarmNodeID
sonusAlarmLevel
sonusAlarmTime
sonusPingPeerFqdn
sonusPingPeerZoneId
sonusPingPeerName
Action None
Impact The specified IP end-point is no longer bypassed when routing SIP calls.
Clearing Automatic; sonusSbxPathCheckFqdnPeerIpV6EndpointDownNotification2
sonusSbxPathCheckFqdnPeerUpNotification2 - MINOR
Type: MINOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.1.0.89
Description This alarm indicates that the specified SIP peer is available to receive calls.
Repetition None
Event Codes EVENT_PATHCHK_FQDN_PEER_UP
Instance Fields
sonusAlarmNodeID
sonusAlarmLevel
sonusAlarmTime
sonusPingPeerFqdn
sonusPingPeerZoneId
sonusPingPeerName
Action None
Impact The specified SIP peer will no longer be bypassed while routing SIP calls.
Clearing Automatic; sonusSbxPathCheckFqdnPeerDownNotification2
sonusSbxPathCheckLocalAdminStateDownNotification2 -
MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.1.0.82
Description This alarm indicates that the peer's local administrative state is down (IPv4).
Repetition None
Event Codes EVENT_PATHCHK_LOCAL_ADMIN_STATE_DOWN
Instance Fields
sonusAlarmNodeID
sonusAlarmLevel
sonusAlarmTime
sonusPingPeerZoneId
sonusPingPeerName
Action None
Impact None
Clearing Manual
sonusSbxPathCheckLocalAdminStateDownNotification2V6 -
MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.1.0.84
Description This alarm indicates that the peer's local admin state is down (IPv6).
Repetition None
Event Codes EVENT_PATHCHK_LOCAL_ADMIN_STATE_DOWN_V6
Instance Fields
sonusAlarmNodeID
sonusAlarmLevel
sonusAlarmTime
sonusPingPeerZoneId
sonusPingPeerName
Action None
Impact None
Clearing Manual
sonusSbxPathCheckLocalAdminStateUpNotification2 -
MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.1.0.81
Description This alarm indicates the SBC PATHCHK ping state is up for a particular peer's local admin.
Repetition None
Event Codes EVENT_PATHCHK_LOCAL_ADMIN_STATE_UP
Instance Fields
sonusAlarmNodeID
sonusAlarmLevel
sonusAlarmTime
sonusPingPeerZoneId
sonusPingPeerName
Action None
Impact None
Clearing Automatic; sonusSbxPathCheckLocalAdminStateDownNotification2
sonusSbxPathCheckLocalAdminStateUpNotification2V6 -
MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.1.0.83
Description This alarm indicates the SBC PATHCHK ping state is up for a particular peer's IPv6 local admin.
Repetition None
Event Codes EVENT_PATHCHK_LOCAL_ADMIN_STATE_UP_V6
Instance Fields
sonusAlarmNodeID
sonusAlarmLevel
sonusAlarmTime
sonusPingPeerZoneId
sonusPingPeerName
Action None
Impact None
Clearing Automatic; sonusSbxPathCheckLocalAdminStateDownNotification2V6
sonusSbxPathCheckPingStateDownNotification2 - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.1.0.78
Description This alarm indicates that ping (Options ping and ICMP ping) is disabled for the specified IP Peer.
Repetition None
Event Codes EVENT_PATHCHK_PING_STATE_DOWN
Instance Fields
sonusAlarmNodeID
sonusAlarmLevel
sonusAlarmTime
sonusPingPeerZoneId
sonusPingPeerName
Action None
Impact None
Clearing Manual
sonusSbxPathCheckPingStateDownNotification2V6 - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.1.0.86
Description This alarm indicates that ping (Option ping and ICMP ping) is disabled for the IP Peer at the specified IPv6 address.
Repetition None
Event Codes EVENT_PATHCHK_PING_STATE_DOWN_V6
Instance Fields
sonusAlarmNodeID
sonusAlarmLevel
sonusAlarmTime
sonusPingPeerZoneId
sonusPingPeerName
Action None
Impact None
Clearing Manual
sonusSbxPathCheckPingStateUpNotification2 - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.1.0.77
Description This alarm indicates that the ping (Options ping and ICMP ping) is enabled for the specified IP Peer.
Repetition None
Event Codes EVENT_PATHCHK_PING_STATE_UP
Instance Fields
sonusAlarmNodeID
sonusAlarmLevel
sonusAlarmTime
sonusPingPeerZoneId
sonusPingPeerName
Action None
Impact None
Clearing Automatic; sonusSbxPathCheckPingStateDownNotification2
sonusSbxPathCheckPingStateUpNotification2V6 - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.1.0.85
Description This alarm indicates that the ping (Options ping and ICMP ping) is enabled for the IP Peer at the specified IPv6 address.
Repetition None
Event Codes EVENT_PATHCHK_PING_STATE_UP_V6
Instance Fields
sonusAlarmNodeID
sonusAlarmLevel
sonusAlarmTime
sonusPingPeerZoneId
sonusPingPeerName
Action None
Impact None
Clearing Automatic; sonusSbxPathCheckPingStateDownNotification2V6
sonusSbxPathCheckRemoteAdminStateDownNotification2 -
MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.1.0.80
Description This alarm indicates the peer's remote admin state is down.
Repetition None
Event Codes EVENT_PATHCHK_REMOTE_ADMIN_STATE_DOWN
Instance Fields
sonusAlarmNodeID
sonusAlarmLevel
sonusAlarmTime
sonusPingPeerZoneId
sonusPingPeerName
Action None
Impact The peer’s admin state is unreachable.
Clearing Manual
sonusSbxPathCheckRemoteAdminStateDownNotification2V6
- MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.1.0.88
Description This alarm indicates that the peer's IPv6 remote admin state is down.
Repetition None
Event Codes EVENT_PATHCHK_REMOTE_ADMIN_STATE_DOWN_V6
Instance Fields
sonusAlarmNodeID
sonusAlarmLevel
sonusAlarmTime
sonusPingPeerZoneId
sonusPingPeerName
Action None
Impact IPv6 peer is unreachable.
Clearing Manual
sonusSbxPathCheckRemoteAdminStateUpNotification2 -
MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.1.0.79
Description This alarm indicates that the peer's remote Admin State is up.
Repetition None
Event Codes EVENT_PATHCHK_REMOTE_ADMIN_STATE_UP
Instance Fields
sonusAlarmNodeID
sonusAlarmLevel
sonusAlarmTime
sonusPingPeerZoneId
sonusPingPeerName
Action None
Impact The peer’s admin state is reachable.
Clearing Automatic; sonusSbxPathCheckRemoteAdminStateDownNotification2
sonusSbxPathCheckRemoteAdminStateUpNotification2V6 -
MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.1.0.87
Description This alarm indicates that the peer's IPv6 remote admin state is up.
Repetition None
Event Codes EVENT_PATHCHK_REMOTE_ADMIN_STATE_UP_V6
Instance Fields
sonusAlarmNodeID
sonusAlarmLevel
sonusAlarmTime
sonusPingPeerZoneId
sonusPingPeerName
Action None
Impact The IPv6 peer’s admin state is reachable.
Clearing Automatic; sonusSbxPathCheckRemoteAdminStateDownNotification2V6
Platform Alarms
This section contains the following Platform alarms.
sonusCdbEncryptionKeyRegeneratedNotification - MAJOR
sonusCdbEncryptionKeyZeroizedNotification - MAJOR
sonusConnexIpSystemCECardInsertedNotification - MAJOR
sonusConnexIpSystemCECardRemovedNotification - MAJOR
sonusConnexIpSystemCEFanAbsentNotification - MAJOR
sonusConnexIpSystemCEFanFailureNotification - MAJOR
sonusConnexIpSystemCEFanNormalNotification - MAJOR
sonusConnexIpSystemCEFanPresentNotification - MAJOR
sonusConnexIpSystemCEMultipleFanAbsentNotification - MAJOR
sonusConnexIpSystemCEMultipleFanPresentNotification - MAJOR
sonusConnexIpSystemCEPowerSupplyFailureNotification - MAJOR
sonusConnexIpSystemCEPowerSupplyNormalNotification - MAJOR
sonusConnexIpSystemCEPowerSupplyUnitInsertedNotification - MAJOR
sonusConnexIpSystemCEPowerSupplyUnitRemovedNotification - MAJOR
sonusConnexIpSystemCESlotDisabledNotification - MAJOR
sonusConnexIpSystemCESlotDryupNotification - MAJOR
sonusConnexIpSystemCESlotEnabledNotification - MAJOR
sonusConnexIpSystemCESlotFailedNotification - MAJOR
sonusConnexIpSystemCESlotLockClearNotification - MAJOR
sonusConnexIpSystemCESlotLockNotification - MAJOR
sonusConnexIpSystemCESlotMismatchClearNotification - MAJOR
sonusConnexIpSystemCESlotMismatchNotification - MAJOR
sonusIPv6DuplicateManualReviewNoRebootNotification - MAJOR
sonusIPv6DuplicateManualReviewRebootingNotification - MAJOR
sonusOpenSSLCRNGTestFailedNotification - CRITICAL
sonusOpenSSLPairwiseConsistencyTestFailedNotification - CRITICAL
sonusSbxLvmPrgLinkFailureToggleClearedNotification - MAJOR
sonusSbxLvmPrgLinkFailureToggleNotification - MAJOR
sonusSbxLvmPrgSwitchoverToRecoverLinksNotification - MAJOR
sonusSbxMediaProfileDspReconfigurationNotificationClear - MAJOR
sonusSbxMediaProfileDspReconfigurationNotification - MAJOR
sonusSbxPadThresholdNotificationClear - MAJOR
sonusSbxPadThresholdNotification - MAJOR
sonusSoftwareLoadTestFailedNotification - CRITICAL
sonusSshHostKeyRegeneratedNotification - MAJOR
sonusSshHostKeyZeroizedNotification - MAJOR
sonusSystemNodeResourceClearCongestionWarningNotification - MAJOR
sonusSystemNodeResourceCongestionWarningNotification - MAJOR
sonusSystemSecurityEthernetClearNotification - INFORMATIONAL
sonusSystemSecurityEthernetErrorNotification - MAJOR
sonusSystemSecurityMediaErrClearNotification - INFORMATIONAL
sonusSystemSecurityMediaErrorNotification - MAJOR
sonusSystemSecurityReportNotification - MAJOR
sonusCdbEncryptionKeyRegeneratedNotification - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.11.0.4
Description This trap indicates that the CDB encryption keys are regenerated.
Repetition None

sonusAlarmLevel
sonusAlarmTime
Action None
Impact None
Clearing Manual
sonusCdbEncryptionKeyZeroizedNotification - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.11.0.3
Description This trap indicates that the CDB encryption keys are zeroized.
Repetition None
Event Codes 334

sonusAlarmLevel
sonusAlarmTime
Action None
Impact None
Clearing Manual
sonusConnexIpSystemCECardInsertedNotification - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.8.1.4.1.1.0.11
Description This alarm indicates that the card is inserted into a specified slot on the server.
Repetition None
Event Codes sonusConnexIpSystemServerName

sonusConnexIpSlotNum
sonusConnexIpCardType
sonusConnexIpCardAdminState
Action None
Impact If the Admin state is enabled, the capacity of the server will increase.
Clearing Manual
sonusConnexIpSystemCECardRemovedNotification - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.8.1.4.1.1.0.12
Description This alarm indicates that the DSP card is removed from the specified slot on the server.
Repetition None

sonusConnexIpCardAdminState
Action None
Impact The capacity of server decreases.
Clearing Automatic, cleared by sonusConnexIpSystemCECardInsertedNotification
sonusConnexIpSystemCEFanAbsentNotification - MAJOR
Note
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.8.1.4.1.1.0.7
Description This alarm indicates that a fan of the server is removed (absent).
Repetition None
Event Codes sonusConnexIpSystemAdminName

sonusConnexIpSystemServerName
sonusConnexIpSystemFanId
Action None
Impact None
Clearing Automatic, sonusConnexIpSystemCEFanPresentNotification
sonusConnexIpSystemCEFanFailureNotification - MAJOR
Note
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.8.1.4.1.1.0.6
Description This trap indicates that the specified chassis fan failed.
Repetition None

sonusConnexIpSystemFanSpeed
Action Replace the failed fan
Impact System may overheat
Clearing Manual
sonusConnexIpSystemCEFanNormalNotification - MAJOR
Note
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.8.1.4.1.1.0.5
Description This trap indicates that the specified chassis fan is operating normally.
Repetition None

sonusConnexIpSystemFanSpeed
Action None
Impact None
Clearing Manual
sonusConnexIpSystemCEFanPresentNotification - MAJOR
Note
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.8.1.4.1.1.0.8
Description This alarm indicates the specified chassis fan was inserted.
Repetition None

Action None
Impact None
Clearing Manual
sonusConnexIpSystemCEMultipleFanAbsentNotification -
MAJOR
Note
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.8.1.4.1.1.0.9
Description This alarm indicates that two or more chassis fans are removed (absent).
Repetition None

Action None
Impact None
Clearing Automatic, sonusConnexIpSystemCEMultipleFanPresentNotification
sonusConnexIpSystemCEMultipleFanPresentNotification -
MAJOR
Note
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.8.1.4.1.1.0.10
Description This alarm indicates that at least two chassis fans are present.
Repetition None

Action None
Impact None
Clearing Manual
sonusConnexIpSystemCEPowerSupplyFailureNotification -
MAJOR
Note
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.8.1.4.1.1.0.1
Description This alarm indicates the specified chassis power supply failed.
Repetition None

sonusConnexIpSystemPowerSupplyId
Instance None
Fields
Action Replace the power supply or source of power.
Refer to the respective hardware installation guide for power supply replacement procedures.
Installing SBC 5400 Hardware

Installing SBC 7000 Hardware
Impact The server is running without power supply redundancy. If the second power supply fails during this time, the server will go
down.
Clearing Automatic, sonusConnexIpSystemCEPowerSupplyNormalNotification
sonusConnexIpSystemCEPowerSupplyNormalNotification -
MAJOR
Note
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.8.1.4.1.1.0.2
Description This alarm indicates that the power supply of the server is normal.
Repetition None

sonusAlarmLevel
sonusAlarmTime
sonusConnexIpSystemAdminName
Action None
Impact The server will run with protected power supply.
Clearing Automatic; sonusConnexIpSystemCEPowerSupplyFailureNotification
sonusConnexIpSystemCEPowerSupplyUnitInsertedNotification - M
Note
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.8.1.4.1.1.0.4
Description This alarm indicates that a server power supply was inserted.
Repetition None

Action None
Impact None
Clearing Manual
sonusConnexIpSystemCEPowerSupplyUnitRemovedNotification - M
Note
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.8.1.4.1.1.0.3
Description This alarm indicates the specified chassis power supply was removed.
Repetition None

Action Replace the power supply unit.
Impact The server is running without power supply redundancy.
Clearing Automatic, sonusConnexIpSystemCEPowerSupplyUnitInsertedNotification
sonusConnexIpSystemCESlotDisabledNotification - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.8.1.4.1.1.0.14
Description This alarm indicates that a specified DSP card slot on the server is disabled.
Repetition None

sonusConnexIpCleanupType
sonusConnexIpDryupTime
Instance None
Fields
Action None
Impact The capacity of the server decreases. Check the status screen; if dryup is complete, the card in the specified slot can be
removed safely.
Clearing Automatic; sonusConnexIpSystemCESlotEnabledNotification
sonusConnexIpSystemCESlotDryupNotification - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.8.1.4.1.1.0.15
Description This trap indicates that the specified slot on the server is transitioning to dry-up mode.
Repetition None

sonusAlarmLevel
sonusAlarmTime
Action Check logs and resolve problem for this slot.
Impact The slot is transitioning to dry-up mode.
Clearing Manual
sonusConnexIpSystemCESlotEnabledNotification - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.8.1.4.1.1.0.13
Description This alarm indicates that a specified slot on the server is enabled.
Repetition None

Action None
Impact If the card is present in the slot, capacity of the server increases.
Clearing Manual
sonusConnexIpSystemCESlotFailedNotification - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.8.1.4.1.1.0.20
Description This trap is generated when the specified slot load/boot fails at least three times consecutively.
Repetition None

sonusAlarmLevel
sonusAlarmTime
Action Take the following actions:
1. Disable the card in this slot.

2. Replace the card.
3. Active the card to enable it.
Impact This specified slot fails to boot.
Clearing Manual
sonusConnexIpSystemCESlotLockClearNotification - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.8.1.4.1.1.0.19
Description This alarm indicates that the lockout on the specified slot has cleared.
Repetition None

sonusAlarmLevel
sonusAlarmTime
Action No action required from user.
Impact Slot lockout is cleared.
Clearing Manual
sonusConnexIpSystemCESlotLockNotification - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.8.1.4.1.1.0.18
Descripti This alarm indicates the specified slot is locked due to a mismatch with the peer server. Because of this, the system admin dspMism
on atchAction parameter is set to "preserveRedundancy".
Repetition None
sonusAlarmTime
Instance None
Fields
Action To use this slot, match the DSP card configuration with the peer server.
Impact The slot is locked due to a mismatch with the peer server.
Clearing Automatic; sonusConnexIpSystemCESlotLockClearNotification
sonusConnexIpSystemCESlotMismatchClearNotification -
MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.8.1.4.1.1.0.17
Description This alarm indicates that the mismatch with the peer on the specified slot is cleared.
Repetition None

sonusAlarmLevel
sonusAlarmTime
Action No action required.
Impact The slot mismatch with the peer is cleared.
Clearing Manual
sonusConnexIpSystemCESlotMismatchNotification - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.8.1.4.1.1.0.16
Description This alarm indicates that the specified ConnexIP slot is mismatched with the peer server.
Repetition None

sonusAlarmLevel
sonusAlarmTime
Action Match the slot configuration with the peer server.
Impact A slot mismatch occurred with the peer server.
Clearing Automatic; sonusConnexIpSystemCESlotMismatchClearNotification
sonusIPv6DuplicateManualReviewNoRebootNotification -
MAJOR
Type: MAJOR
Objec 1.3.6.1.4.1.2879.2.8.1.2.1.18.0.1
t ID
Descr After bringing down the HA port on the active node, the standby role is set to active. On the new active node, some IPV6 pkt ports
iption contain the error 'tentative dadfailed' . When 'tentative dadfailed' is detected on some ports, check the configurations/logs and take
action accordingly.
This alarm is triggered only when some IPV6 pkt ports contain the error 'tentative dadfailed'.
Repet This alarm is triggered when some IPV6 pkt ports contain the error 'tentative dadfailed'.
ition
Event
sonusAlarmLevel
sonusAlarmTime
Insta sonusDuplicateIpv6Address
nce
Fields
Action Verify/correct specific configurations. Otherwise, reboot the node.
Impa Calls are rejected as duplicate address is detected.

ct
Cleari Alarm clears automatically after node reboots.

ng
sonusIPv6DuplicateManualReviewRebootingNotification -
MAJOR
Type: MAJOR
Object 1.3.6.1.4.1.2879.2.8.1.2.1.18.0.2
ID
Descri After bringing down the HA port on the active node, the standby role is set to active. On the new active node, all IPV6 pkt ports
ption contain the error 'tentative dadfailed'. When 'tentative dadfailed' is detected on all ports, the node is rebooted.
Repetit This trap is triggered when all IPV6 pkt ports contain the error 'tentative dadfailed'.
ion
Event
sonusAlarmLevel
sonusAlarmTime
Instanc None
e
Fields
Action Node is rebooting. No manual action is required.
Impact Calls are rejected as duplicate address is detected.
Clearing The trap clears automatically after the node reboots.
sonusOpenSSLCRNGTestFailedNotification - CRITICAL
Type: CRITICAL
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.11.0.5
Description This trap indicates that the OpenSSL Continuous Random Number Generator Test has failed.
Repetition None

sonusAlarmLevel
sonusAlarmTime
sonusFipsNotificationDetails
Action Reboot is required to restore SBC, ssh, apache (EMA/PM) services.
Impact SBC, SSH, Apache (EMA/PM) services are stopped.
Clearing Manual
sonusOpenSSLPairwiseConsistencyTestFailedNotification -
CRITICAL
Type: CRITICAL
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.11.0.6
Description This trap indicates that the OpenSSL Pairwise Consistency Test has failed.
Repetition None

sonusAlarmLevel
sonusAlarmTime
Action Reboot is required to restore SBC, SSH, Apache (EMA/PM) services.
Impact SBC, SSH, Apache (EMA/PM) services are stopped.
Clearing Manual
sonusSbxLvmPrgLinkFailureToggleClearedNotification -
MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.21.0.9
Description Port Redundancy Group cleared link failure toggling.
Repetition Occurs when Port Redundancy Group clears link failure toggling.
Event Codes
sonusAlarmNodeID
sonusAlarmLevel
sonusAlarmTime
sonusNrsCeName
sonusLvmPortRedundancyGroupName
Instance Fields
sonusNrsCeName
Action None
Impact None
Clearing Manual
sonusSbxLvmPrgLinkFailureToggleNotification - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.21.0.8
Description Port Redundancy Group detected link failure toggling.
Repetition Occurs when Port Redundancy Group detects link failure toggling.
Event
sonusAlarmLevel
sonusAlarmTime
sonusNrsCeName
Instance
Fields sonusNrsCeName
Action Examine the health of the failed links and repair them.
Impact Automatic port switchovers to re-establish failed links stop.
Clearing automatic; sonusSbxLvmPrgLinkFailureToggleClearedNotification
Note: In certain instances, you must clear this alarm manually; for example, after node switchover (if the links do not recover
before toggleRecoverTimer expiry).
sonusSbxLvmPrgSwitchoverToRecoverLinksNotification -
MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.21.0.10
Description Indicates a node switchover is initiating as the system is unable to recover from port toggling.
Repetition None
Event Codes
sonusAlarmNodeID
sonusAlarmLevel
sonusAlarmTime
Instance None
Fields
Action Node switchover is initiated. After the switchover, examine the health of the failed links of the current standby node, and fix
them.
To check the current status of the links, use the following CLI commands:
show table addressContext <ACName> linkDetectionGroup
show table addressContext <ACName> linkDetectionGroup <LDGName> linkMonitorStatus
show table system ethernetPort portMonitorStatus
Refer to the CLI pages Link Detection Group - CLI and Show Table System, for more details.
Impact Node switchover to the standby server occurs.
Clearing Manual
sonusSbxMediaProfileDspReconfigurationNotificationClear -
MAJOR
Note:
Media profile configuration applies only to SBCs deployed on the SBC 5400/7000 platforms and not to SBC SWe deployments.
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.4.0.25
Description This alarm indicates that the mediaProfile and DSP reconfiguration are complete.
Repetition None
Event Codes None
Action None
Impact None
Clearing Manual
sonusSbxMediaProfileDspReconfigurationNotification -
MAJOR
Note:
Media profile configuration applies only to SBCs deployed on the SBC 5400/7000 platforms and not to SBC SWe deployments.
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.4.0.24
Description This alarm indicates that the mediaProfile config has been modified and DSP re-configuration is initiated and in progress.
Repetition None
Event Codes None
Action None
Impact Existing DSP resources may be placed in extended dryup state before reconfiguration completes.
Clearing Automatic, sonusSbxMediaProfileDspReconfigurationNotificationClear
sonusSbxPadThresholdNotificationClear - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.4.0.23
Description This alarm indicates that the compression DSP resource usage has dropped below the configured threshold value. The default
threshold value is 90%.
Repetition None.
Event Codes
sonusAlarmNodeID
sonusAlarmLevel
sonusAlarmTime
Instance None.
Fields
Action None. It clears the alarm sonusSbxPadThresholdNotification - MAJOR.
Impact None. New transcoded calls are no longer impacted as the DSP resource usage is now within the threshold value.
Clearing Manual.
sonusSbxPadThresholdNotification - MAJOR
Type: MAJOR
Object iD 1.3.6.1.4.1.2879.2.10.1.1.4.0.22
Description This alarm indicates that the compression DSP resource usage has crossed the configured threshold value.
The default threshold value is 90%.
Repetition None
Event Codes None
Action Increase compression DSP resources, if possible.
Impact May impact new transcoded calls.
Clearing Automatic; sonusSbxPadThresholdNotificationClear
sonusSoftwareLoadTestFailedNotification - CRITICAL
Type: CRITICAL
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.11.0.7
Description This alarm indicates that the Package Integrity Test has failed.
Repetition None

sonusAlarmLevel
sonusAlarmTime
Action Download the Ribbon-signed package for upgrade or installation.
Impact Installation or upgrade is aborted.
Clearing Manual
sonusSshHostKeyRegeneratedNotification - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.11.0.2
Description This trap indicates that the SSH host keys are regenerated.
Repetition None
Event Codes
sonusAlarmNodeID
sonusAlarmLevel
sonusAlarmTime
Action None
Impact None
Clearing Manual
sonusSshHostKeyZeroizedNotification - MAJOR
Type: MAJOR
Object iD 1.3.6.1.4.1.2879.2.8.1.2.1.11.0.1
Description This trap indicates that the SSH host keys are zeroed.
Repetition None

sonusAlarmLevel
sonusAlarmTime
Action None
Impact None
Clearing Manual
sonusSystemNodeResourceClearCongestionWarningNotification -
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.5.0.50
Description This alarm indicates that the system has fallen below the memory threshold.
Repetition None

sonusAlarmLevel
sonusAlarmTime
sonusNodeOverloadType
sonusNodeOverloadLevel
sonusNodeOverloadThresholdCurrent
sonusNodeOverloadThresholdConfigured
Instance Fields sonusNodeOverloadType

Action None
Impact None
Clearing Manual
For SBC SWe, this trap is also generated when system is coming out of CPU congestion.
sonusSystemNodeResourceCongestionWarningNotification -
MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.5.0.48
Description This alarm indicates that the system is running out of memory and will soon reboot.
Repetition None

sonusAlarmLevel
sonusAlarmTime
sonusNodeOverloadType
Instance Fields sonusNodeOverloadType

Action Check call/registration load and possible resource leakage.
Impact Calls may get rejected.
Clearing Automatic; sonusSystemNodeResourceClearCongestionWarningNotification
For SBC SWe, this alarm is also generated when there is a CPU congestion. Calls may get rejected during congestion in order to maintain
system stability.
Note
If the node overload type mentioned in the alarm is "mem" then, the SBC application restarts only when the memory threshold of 90% is
breached. If the node overload type is "XRM" in the alarm, then the SBC does not restart.
sonusSystemSecurityEthernetClearNotification -
INFORMATIONAL
Type: INFORMATIONAL
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.12.0.2
Description This alarm indicates that the CRC error rate has gone below the configurable "clearThreshold" level for the specified Ethernet
port.
Repetition None
Event Codes sonusEthErrorType
sonusEthInterfaceType
Instance None
Fields
Action None
Impact None
Clearing Automatic; sonusSystemSecurityEthernetErrorNotification
sonusSystemSecurityEthernetErrorNotification - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.12.0.3
Description This alarm indicates CRC error rate exceeds the configurable "setThreshold" for the specified Ethernet port.
Repetition None.
Event Codes sonusEthErrorType
sonusEthInterfaceType
Instance Fields None.
Action Examine the proper functioning of the network interface element that reports an error.
Impact Communication integrity of the network interface maybe compromised or becomes unreliable.
Clearing Automatic; sonusSystemSecurityEthernetClearNotification
sonusSystemSecurityMediaErrClearNotification -
INFORMATIONAL
Type: INFORMATIONAL
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.12.0.4
Description This alarm indicates the Media Error rate has gone below the configurable "clearThreshold" level for this system
Repetition None
Event Codes sonusMediaErrType
Action None
Impact None
Clearing Automatic; sonusSystemSecurityMediaErrorNotification
sonusSystemSecurityMediaErrorNotification - MAJOR
Type: MAJOR
Object iD 1.3.6.1.4.1.2879.2.8.1.2.1.12.0.5
Description This alarm indicates processor Media Error rate has exceeded the configurable "setThreshold" for this system.
Repetition None
Event sonusMediaErrType
Codes
Instance None
Fields
Action If the problem persists, examine the IP Sec Decrypt Offenders policer list for potential issues. Refer to, Policers - IP Sec Decrypt
Offenders List for more information.
Impact Communication integrity of the media stream maybe compromised or becomes unreliable.
Clearing Automatic; sonusSystemSecurityMediaErrClearNotification
sonusSystemSecurityReportNotification - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.12.0.1
Description This trap is triggered upon the detection of a major system security event.
Repetition
Event Codes
sonusAlarmNodeID
sonusAlarmLevel
sonusAlarmTime
sonusSystemSecurityNotificationDetails
Instance Fields sonusSystemSecurityNotificationDetails
Action Verify system security based on information provided in the trap notification details.
Impact Possible compromise of system security.
Clearing Manual
This section contains the following Policy Server alarms.
sonusPipeTMControlModifiedNotification - INFORMATIONAL
sonusPipeTMControlProvisionedNotification - INFORMATIONAL
sonusPipeTMControlRemovedNotification - INFORMATIONAL
sonusPolicyServerADServerSyncFailedNotification - INFORMATIONAL
sonusPolicyServerADServerSyncSuccessNotification - INFORMATIONAL
sonusPolicyServerCallProcessTimeHighThresholdNotification - MAJOR
sonusPolicyServerCallProcessTimeLowThresholdNotification - MAJOR
sonusPolicyServerCongestionNotification - MAJOR
sonusPolicyServerDbConnSuccessNotification - MAJOR
sonusPolicyServerDbOperationFailureNotification - MAJOR
sonusPolicyServerExternalErrorHighThresholdNotification - MAJOR
sonusPolicyServerExternalErrorLowThresholdNotification - INFORMATIONAL
sonusPolicyServerInternalErrorHighThresholdNotification - MAJOR
sonusPolicyServerInternalErrorLowThresholdNotification - INFORMATIONAL
sonusPolicyServerLwresdCommunicationDownNotification - MAJOR
sonusPolicyServerLwresdCommunicationUpNotification - MAJOR
sonusPolicyServerLWRESDDNSServerBlacklistedNotification - INFORMATIONAL
sonusPolicyServerLWRESDDNSServerRecoveredNotification - INFORMATIONAL
sonusPolicyServerLWRESDENUMServerBlacklistedNotification - MAJOR
sonusPolicyServerLWRESDENUMServerRecoveredNotification - MINOR
sonusPolicyServerNoRouteFoundNotification - MAJOR
sonusPolicyServerPipeCommunicationDownNotification - MAJOR
sonusPolicyServerPipeCommunicationUpNotification - MAJOR
sonusPolicyServerPipeIOErrorNotification - MAJOR
sonusPolicyServerPipeMWIQueueLevelChanged - MAJOR
sonusPolicyServerPipeRegistrationFailureNotification - MAJOR
sonusPolicyServerPipeRegistrationSuccessNotification - MAJOR
sonusPolicyServerRegisterNotification - MAJOR
sonusPolicyServerScpCommunicationDownNotification - MAJOR
sonusPolicyServerScpCommunicationUpNotification - MAJOR
sonusPolicyServerScpTimeoutNotification - MAJOR
sonusPolicyServerSqlErrorHighThresholdNotification - MAJOR
sonusPolicyServerTMControlAppliedNotification - INFORMATIONAL
sonusPolicyServerUnregisterNotification - MAJOR
sonusPostgresTransitionFailureNotification - MAJOR
sonusPipeTMControlModifiedNotification - INFORMATIONAL
Type: INFORMATIONAL
Object ID 1.3.6.1.4.1.2879.2.10.1.2.1.1.0.28
Description This trap indicates a traffic control is modified.
Repetition None
Event Codes
sonusPolicyServerTMElementType
sonusPolicyServerTMIdentifier1
sonusPolicyServerTMProvControlType
sonusPolicyServerTMAddressNature
Action None
Impact None
Clearing Manual
sonusPipeTMControlProvisionedNotification -
INFORMATIONAL
Type: INFORMATIONAL
Object ID 1.3.6.1.4.1.2879.2.10.1.2.1.1.0.26
Description This trap indicates the specified traffic control is provisioned.
Repetition None
Event Codes
Action None
Impact None
Clearing Manual
sonusPipeTMControlRemovedNotification - INFORMATIONAL
Type: INFORMATIONAL
Object ID 1.3.6.1.4.1.2879.2.10.1.2.1.1.0.27
Description This trap indicates the specified traffic control is removed.
Repetition None
Event Codes
Action None
Impact None
Clearing Manual
sonusPolicyServerADServerSyncFailedNotification -
INFORMATIONAL
Type: INFORMATIONAL
Object ID 1.3.6.1.4.1.2879.2.10.1.2.1.1.0.33
Description This alarm generates when the domain controller data synchronization fails.
Repetition Yes
Event Codes
sonusAlarmNodeID
sonusAlarmLevel
sonusAlarmTime
Instance Fields sonusPolicyServerADServerSyncFailed
Action LDAP Server sync failed.
Impact Latest changes will not synchronization with the database cache.
Clearing Automatic; sonusPolicyServerADServerSyncSuccessNotification
sonusPolicyServerADServerSyncSuccessNotification -
INFORMATIONAL
Type: INFORMATIONAL
Object ID 1.3.6.1.4.1.2879.2.10.1.2.1.1.0.34
Description This alarm is generated when the LDAP domain controller data synchronization is successful.
Repetition Yes
Event Codes
sonusAlarmNodeID
sonusAlarmLevel
sonusAlarmTime
Instance Fields sonusPolicyServerADServerSyncSuccess
Action LDAP Server sync success.
Impact The latest changes will synchronize with the database cache.
Clearing Automatic; sonusPolicyServerADServerSyncFailedNotification
sonusPolicyServerCallProcessTimeHighThresholdNotification - MA
Type: MAJOR
Object 1.3.6.1.4.1.2879.2.10.1.2.1.1.0.6
ID
Descrip This trap is generated when the PSX average call processing time for the last 50 calls exceeds the high threshold (100 msecs).
tion
Possible failure reasons:
PSX CPU overload

PSX database fragmentation
Repetiti Repeats each time that the call processing time exceeds the high watermark; and continues to repeat after the alarm is cleared by
on sonusPolicyServerCallProcessTimeLowThresholdNotification as long as the high watermark is exceeded.
Event None
Codes
Instanc None
e
Fields
Action Perform the following:
1. Check to see if a process is loading down the CPU.

2. Log onto PSX and type the following to execute the database diagnostic program:
DbDiag.ksh S
If database cleanup is needed, contact Ribbon Support for assistance.
For help with viewing counters and logs, refer to PSX Documentation.
Impact Long call setup times and potential call failures.
Clearing Automatic; sonusPolicyServerCallProcessTimeLowThresholdNotification
sonusPolicyServerCallProcessTimeLowThresholdNotification - MA
Type: MAJOR
Object 1.3.6.1.4.1.2879.2.10.1.2.1.1.0.7
ID
Descri This trap is generated when the average call processing time for the last 50 calls falls below the low threshold (70 msecs) following a
ption high threshold notification.
Repeti Repeats each time that the call processing time goes below the low watermark; and will continue to repeat after the alarm is cleared by
tion sonusPolicyServerCallProcessTimeHighThresholdNotification as long as the call processing time is below the watermark.
Event None
Codes
Instan None
ce
Fields
Action None
Impact None
Cleari Automatic; clears in two minutes

ng
sonusPolicyServerCongestionNotification - MAJOR
Note
The SBC does not support this trap.
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.2.1.1.0.11
Description This trap is generated when the congestion control level changes within the 30-seconds interval. The notification indicates the
current congestion control level (0, 1, 2, or 3).
Repetition None
Event sonusPolicyServerCongestionLevel
Codes
Instance None
Fields
Action Investigate congestion level and ensure that the load is balanced across all SBCs.
Impact Call processing delays may occur when the congestion control level is high.
Clearing Manual
sonusPolicyServerDbConnSuccessNotification - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.2.1.1.0.12
Description The PES process establishes a connection to the SBC Core DB.
Repetition None
Event Codes None
Action None
Impact None
Clearing Manual
sonusPolicyServerDbOperationFailureNotification - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.2.1.1.0.1
Description A database operation is failed.
Repetition None
Event Codes sonusPolicyServerDbOperationFailureReason
Instance None
Fields
Action Check the failure reason to take corrective action.
Impact The impact to the system may vary for each alarm occurrence and depends on the failure reason, which is received in the alarm
message.
Clearing Manual
sonusPolicyServerExternalErrorHighThresholdNotification -
MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.2.1.1.0.23
Descripti The alarm indicates the PSX External communication failure has exceeded the configured threshold. The default value is “50”, and is
on configurable from the PSX. For details, refer to PSX Documentation.
Repetition None
Event None
Codes
Instance None
Fields
Action Determine cause of failure and rectify.
Impact Calls are failing due to this External Communication failure error. PES will not shut down the socket for this error.
Clearing Automatic; sonusPolicyServerExternalErrorLowThresholdNotification
sonusPolicyServerExternalErrorLowThresholdNotification -
INFORMATIONAL
Type: INFORMATIONAL
Object ID 1.3.6.1.4.1.2879.2.10.1.2.1.1.0.25
Description The alarm indicates the SBC Core excessive External communication failure cleared.
Repetition None
Event Codes None
Action None
Impact None
Clearing Automatic, sonusPolicyServerExternalErrorHighThresholdNotification
sonusPolicyServerInternalErrorHighThresholdNotification -
MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.2.1.1.0.22
Descripti The alarm indicates the PSX Internal communication failure has exceeded the configured threshold. The default value is “50”, and is
on configurable from the PSX. For details, refer to PSX Documentation.
Repetition None
Event None
Codes
Instance None
Fields
Action Examine the call logs for cause of failure and rectify.
Impact Calls are failing due to this internal error.
Clearing Automatic; sonusPolicyServerInternalErrorLowThresholdNotification
sonusPolicyServerInternalErrorLowThresholdNotification -
INFORMATIONAL
Type: INFORMATIONAL
Object ID 1.3.6.1.4.1.2879.2.10.1.2.1.1.0.24
Description SBC Core excessive External communication failure crossed configured threshold.
Repetition None
Event Codes None
Action Determine cause of failure and rectify.
Impact Calls are failing due to this External Communication failure error.
PES will not shutdown the socket for this error.
Clearing Internal error that clears the sonusPolicyServerInternalErrorHighThresholdNotification alarm.
sonusPolicyServerLwresdCommunicationDownNotification -
MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.2.1.1.0.20
Description The alarm indicates the communication to LWRESD is down.
Repetition None
Event Codes None
Action Investigate the /var/log/daemon.log file to determine the cause of failure.
Impact DNS and ENUM queries will fail forcing calls to use standard routing.
Clearing Automatic; sonusPolicyServerLwresdCommunicationUpNotification
sonusPolicyServerLwresdCommunicationUpNotification -
MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.2.1.1.0.19
Description The alarm indicates the communication to LWRESD is UP.
Repetition None
Event Codes None
Impact None
Clearing Automatic, sonusPolicyServerLwresdCommunicationDownNotification
sonusPolicyServerLWRESDDNSServerBlacklistedNotification - INF
Type: INFORMATIONAL
Object ID 1.3.6.1.4.1.2879.2.10.1.2.1.1.0.29
Description The alarm indicates the ENUM server is blacklisted and the server is not available.
Repetition Yes
Event Codes
sonusAlarmNodeID
sonusAlarmLevel
sonusAlarmTime
sonusPolicyServerLWRESDBlacklisted
Instance Fields sonusPolicyServerLWRESDBlacklisted
Action ENUM Server is blacklisted and not available.
Impact None
Clearing Automatic; sonusPolicyServerLWRESDENUMServerRecoveredNotification
sonusPolicyServerLWRESDDNSServerRecoveredNotification
- INFORMATIONAL
Type: INFORMATIONAL
Object ID 1.3.6.1.4.1.2879.2.10.1.2.1.1.0.30
Description The alarm indicates the ENUM server is whiteListed, the HighWaterMark timer has expired (for HighWaterMark timer expiry).
The ENUM server is whiteListed and Server is reachable and up (for other reasons).
Repetition Yes
Event Codes
sonusAlarmNodeID
sonusAlarmLevel
sonusAlarmTime
sonusPolicyServerLWRESDWhitelisted
Instance Fields sonusPolicyServerLWRESDWhitelisted
Action ENUM Server is whitelisted and not available.
Impact None
Clearing Manual
The alarm indicates the
sonusPolicyServerLWRESDENUMServerBlacklistedNotification - M
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.2.1.1.0.31
Description This alarm indicates that the ENUM Server is blacklisted.
Repetition Yes
Event Codes
sonusAlarmNodeID,
sonusAlarmLevel,
sonusAlarmTime,
sonusPolicyServerLWRESDBlacklisted
Instance Fields sonusPolicyServerLWRESDBlacklisted
Action The ENUM Server is blacklisted and not available.
Impact None
Clearing Automatic; sonusPolicyServerLWRESDENUMServerRecoveredNotification
sonusPolicyServerLWRESDENUMServerRecoveredNotification - MI
Type: MINOR
Object ID 1.3.6.1.4.1.2879.2.10.1.2.1.1.0.32
Description This alarm is reported when the ENUM server is WhiteListed, and the HighWaterMark timer expired (for HighWaterMark timer
expiry).
The server is reachable and up (for the reasons indicated).
Repetition None
Event Codes
sonusAlarmNodeID
sonusAlarmLevel
sonusAlarmTime
sonusPolicyServerLWRESDWhitelisted
Instance sonusPolicyServerLWRESDWhitelisted
Fields
Impact The ENUM server is available.
Clearing Automatic; sonusPolicyServerLWRESDENUMServerBlacklistedNotification
sonusPolicyServerNoRouteFoundNotification - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.2.1.1.0.9
Description This trap is generated when a PES request is unable to find or provide a route for the call.
Repetition Yes. Repeats after the “Number Of No Routes Found” counter exceeds “No Found Routes Threshold” value configured in the
process configuration.
Event Codes None
Instance None
Fields
Action Verify that a route exists for the failed call via SBC Core database (provisioning). For provisioning information, refer to PSX
Documentation.
Impact The call may fail.
Clearing Manual
sonusPolicyServerPipeCommunicationDownNotification -
MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.2.1.1.0.13
Description The alarm indicates the PES process is not able to establish connection with the master PIPE process.
Repetition None
Event Codes sonusPolicyServerPipeErrorCode
Action Investigate the error_code field to determine the cause of failure.
Impact The PES process cannot send updates (for example, MWI) to PIPE process.
Clearing Automatic, sonusPolicyServerPipeCommunicationUpNotification
sonusPolicyServerPipeCommunicationUpNotification -
MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.2.1.1.0.17
Description The alarm indicates 'pes' process establishes connection with master 'pipe' process.
Repetition None
Event Codes None
Action None
Impact None
Clearing Manual
sonusPolicyServerPipeIOErrorNotification - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.2.1.1.0.15
Description The PES process is not able to send/receive an update to PIPE process.
Repetition Yes. Repeats each time a failure to update the database for MWI occurs.
Action Investigate the error_code field to determine cause of failure.
Impact An update operation failed and the associated update record is lost.
Clearing Manual
sonusPolicyServerPipeMWIQueueLevelChanged - MAJOR
Type: MAJOR
Objec 1.3.6.1.4.1.2879.2.10.1.2.1.1.0.16
t ID
Descr This trap indicates that the MWI queue level changed. If the incoming message rate is much higher than the consumption rate (database
iption update), the queue builds up and crosses levels. Once the “Critical” level is reached, incoming messages are floored (no longer put in
the queue).
Repet None
ition
Event sonusPolicyServerPipeMwiQueueLevel
Codes
Instan None
ce
Fields
Action Check to see if the network is slow, which may contribute to this fault. Also, check the database for any errors.
Impact Once the "Critical" level is reached, incoming messages are floored (no longer put in the queue).
Cleari Manual
ng
sonusPolicyServerPipeRegistrationFailureNotification -
MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.2.1.1.0.14
Description The alarm indicates the PES process is not able to register with master PIPE process.
Repetition None
Action Investigate the error_code field to determine cause of failure
Impact PES cannot send updates (for example, MWI) to PIPE process.
Clearing Automatic, sonusPolicyServerPipeRegistrationSuccessNotification
sonusPolicyServerPipeRegistrationSuccessNotification -
MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.2.1.1.0.18
Description The alarm indicates the PES process successfully registered with master PIPE process.
Repetition None
Event Codes None
Action None
Impact None
Clearing Automatic, sonusPolicyServerPipeRegistrationFailureNotification
sonusPolicyServerRegisterNotification - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.2.1.1.0.2
Description This alarm is generated when the SBC registers to a local PSX server.
Repetition None

sonusAlarmLevel
sonusAlarmTime
sonusPolicyServerClientName
sonusPolicyServerRegisterReason
Instance Fields sonusPolicyServerClientName

sonusPolicyServerRegisterReason
Action Refer to register reason in this alarm to see if any action is necessary.
Impact Once registered, the SBC can place calls.
Clearing Manual
This alarm is not generated when registering to an external PSX.
sonusPolicyServerScpCommunicationDownNotification -
MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.2.1.1.0.5
Description This alarm indicates the communication to SCP is down.
Repetition None
Event Codes None
Action Investigate to determine cause of failure, and reestablish the PES interface.
Impact The SBC may not perform SCP-related operations.
Clearing Manual
sonusPolicyServerScpCommunicationUpNotification -
MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.2.1.1.0.4
Description The alarm indicates communication to SCP is UP.
Repetition None
Event Codes None
Impact None
Clearing Automatic, sonusPolicyServerScpCommunicationDownNotification
sonusPolicyServerScpTimeoutNotification - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.2.1.1.0.8
Description This trap is generated when SCP query time-out rate exceeds 10% in the PES (SCP query timeout rate is calculated in every
100 calls).
Repetition Repeats after every 100 calls if SCP time-out is equal to or greater than 10%.
Event Codes None
Instance None
Fields
Action Investigate excessive time-out rate and check failure reason for corrective action.
For help with viewing counters and logs, refer to PSX Documentation.
Impact May induce call failures or excessive call retries due to SCP query retries.
Clearing Manual
sonusPolicyServerSqlErrorHighThresholdNotification -
MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.2.1.1.0.21
Description PES communication ports are closed due to excessive failures.
Repetition None
Event Codes None
Action Most probable cause is a database failure (hard disk or PostgreSQL

failure).
Identify and fix failure condition, and then restart the SBC.
Impact The Policy server is closed to all communication.
Clearing Manual
sonusPolicyServerTMControlAppliedNotification -
INFORMATIONAL
Type: INFORMATIONAL
Object ID 1.3.6.1.4.1.2879.2.10.1.2.1.1.0.10
Description This trap indicates a traffic control is applied.
Repetition None
Event Codes
sonusPolicyServerTMAppliedControlTyp
e
Action None
Impact None
Clearing Manual
sonusPolicyServerUnregisterNotification - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.2.1.1.0.3
Description This alarm indicates an unregistered operation. Checkk the unregistered reason for insight into this issue.
Repetition None
Event Codes sonusPolicyServerClientName

sonusPolicyServerUnregisterReason
Action Investigate the cause for the failure based on the sonusPolicyServerUnregisterReason field.
Impact SBC must re-register before resuming call processing.
Clearing Automatic, sonusPolicyServerRegisterNotification
Type: Major
Object ID .1.3.6.1.4.1.2879.2.8.1.2.1.5.0.89
Description The Policy Database(Postgres) transition fails during a switchover.
Repetition None
Event Codes None
Instance Fields sonusAlarmNodeID,

sonusAlarmLevel,
sonusAlarmTime,
Action None
Impact Replication slot creation is skipped due to Policy Database(Postgres) transition failure.
Clearing Manual
This section contains the following Registration Event alarm.
sonusSbxSubscriptionToRegEventPackageFailedNotification - MINOR
sonusSbxSubscriptionToRegEventPackageFailedNotification
- MINOR
Type: MINOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.1.0.53
Description This trap indicates that a subscription to REG-EVENT package failed.
Repetition The alarm repeats for each occurrence of a failed subscription.

sonusAlarmLevel
sonusAlarmTime
sonusSubscriptionId
Instance Fields sonusSubscriptionId
Impact No impact to the system.
Clearing Manual
Resource Alarms
This section contains the following Resource alarm.
sonusSbxResourceThresholdReachedNotification - INFORMATIONAL
sonusSbxResourceThresholdReachedNotification -
INFORMATIONAL
Type: INFORMATIONAL
Object ID 1.3.6.1.4.1.2879.2.10.1.1.16.0.1
Description This alarm indicates that the configured bandwidthLimitThreshold/callLimitThreshold is reached for the CAC.
Repetition None
Event Codes
sonusAlarmNodeID
sonusAlarmLevel
sonusAlarmTime
sonusResource
sonusEntityType
sonusEntityName
sonusSharedCacLimitPoolProfileId
sonusResourceUsage
sonusResourceLimit
sonusResourceThreshold
Instance Fields
sonusResource
sonusEntityType
sonusEntityName
sonusSharedCacLimitPoolProfileId
sonusResourceUsage
sonusResourceLimit
sonusResourceThreshold
Action None
Impact None
Clearing Clear manually using the CLI command:
request alarms clear current alarmId <alarmId>
Refer to Alarms - CLI, for more details.
sonusSWeNewActiveProfileCommitNotification - MAJOR
sonusSWeNewActiveProfileCommitNotification - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.15.0.1
Description This trap is generated when a new traffic profile is activated, which triggers system reboot to complete profile activation.
Repetition N/A

sonusAlarmLevel
sonusAlarmTime

Action None
Impact HA pair/Standalone system(s) are rebooted to activate the newly applied traffic profile.
Clearing Manual
Security Alarms
This section describes the following Online Certificate Status Protocol (OCSP) and certificate alarms:
sonusCpSystemRsyslogRemoteServerConnectionIssue - MAJOR
sonusCpSystemRsyslogRemoteServerConnectionRecovered - MAJOR
sonusInvalidOcspResponseReceived - MINOR
sonusMalformedMessagesDroppedNotification - MAJOR
sonusNoValidOcspResponseReceived - MINOR
sonusOcspConnectionFailed - MINOR
sonusOcspExceptionResponse - MINOR
sonusOcspResponseUnknown - MINOR
sonusSbxCertificateExpireSoonWarningNotification - MAJOR
sonusSbxFailedCertificateReCheck - MAJOR
sonusSbxLogFileEncryptionSettingsChangedNotification - MAJOR
sonusSystemSecurityAccountAutoReEnabled - MINOR
sonusSystemSecurityAccountConfigChange - MINOR
sonusSystemSecurityAccountCreatedNotification - MINOR
sonusSystemSecurityAccountDisabledNotification - MAJOR
sonusSystemSecurityAccountLocked - MAJOR
sonusSystemSecurityAccountManuallyDeletedNotification - MINOR
sonusSystemSecurityAccountNewGroupNotification - MINOR
sonusSystemSecurityAccountReEnabled - MINOR
sonusSystemSecurityAccountRemovedNotification - MAJOR
sonusSystemSecurityAccountSshKeyChange - MINOR
sonusSystemSecurityLargeConsoleSessionLog - MAJOR
sonusSystemSecurityNewPrivateHashingKey - MAJOR
sonusSystemSecurityOsAccountAutoReEnabled - MINOR
sonusSystemSecurityOsAccountLocked - MAJOR
sonusSystemSecurityOsAccountReEnabled - MINOR
sonusCpSystemRsyslogRemoteServerConnectionIssue -
MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.5.0.87
Description This alarm indicates the SBC failed to establish a TCP connection with Rsyslog server.
Repetition Five minutes

sonusAlarmLevel
sonusAlarmTime
Instance Fields sonusServerIpAddress
Action Check the rsyslog service status on the remote server and if the SBC can communicate to the remote server.
Impact Event messages are not written to the remote server.
Clearing Automatic; sonusCpSystemRsyslogRemoteServerConnectionRecovered
sonusCpSystemRsyslogRemoteServerConnectionRecovered
- MAJOR
Note
The SBC may continually trigger this alarm if it loses connection to the syslog server and is configured to push Account logs to a remote
syslog server while no account logs are getting generated. This is required in order to preserve the integrity of the accounting logs. The
SBC will stop triggering this alarm once calls occur. Alternatively, you can stop the alarms by disabling and enabling the typeAdmin acct
sysLog state.
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.5.0.88
Description This alarm indicates the connection to the remote Rsyslog server is established/re-established.
Note: The SBC does not generate traps for UDP connections.
Repetition None

sonusAlarmLevel
sonusAlarmTime
Instance Fields sonusServerIpAddress
Action None
Impact Event messages are written to the remote server.
Clearing Manual
sonusInvalidOcspResponseReceived - MINOR
Type: MINOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.20.0.2
Description This trap indicates an invalid OCSP response received from responder.
Repetition None
Event Codes SEC_OCSP_INVALID_RESPONSE
Instance Fields Responder URL
Action Ensure that the OCSP Responder is properly configured and operational.
Impact TLS OCSP checking cannot be performed.
Clearing Manual or Automatic
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.4.0.63
Description The alarm indicates that malformed messages are dropped.
Repetition The alarm is raised when the Malformed message timer expires. The timer starts when a malformed message is identified and the
expiry value is 10 seconds.
No alarm is raised for malformed messages during the ten second interval.
Event
Codes EVENT_SIPCM_MALFORMED_MESSAGES_DROPPED
Instance
Fields sonusMalformedMessagesDropped,
sonusMalformedMessagesSourceIpAddr
Action No clearing/resolution is required for the informational alarm.
As a preventive action the system admin can block the IP addresses received in the source IP address list.
Impact The alarm indicates that malformed Messages are detected and dropped. This could imply a DoS attack depending on the count
of messages received.
Clearing None
sonusNoValidOcspResponseReceived - MINOR
Type: MINOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.20.0.3
Description This trap indicates that there no valid OCSP response is received from responder.
Repetition None
Event Codes SEC_OCSP_NO_VALID_RESPONSE
Action Ensure that the OCSP Responder is properly configured and operational.
Impact Inability to perform TLS OCSP checking.
sonusOcspConnectionFailed - MINOR
Type: MINOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.20.0.1
Description This trap indicates that the TCP connection to OCSP Responder cannot be established.
Repetition None
Event Codes SEC_OCSP_ CONNECTION_FAILED
Action Ensure that the OCSP Responder is reachable by ping or wget.
Impact TLS OCSP checking cannot be performed.
Clearing None
sonusOcspExceptionResponse - MINOR
Type: MINOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.20.0.5
Description The trap indicates the valid OCSP response was received with certificate status unknown.
Repetition None
Event Codes SEC_OCSP_EXCEPTION_ RESPONSE
Instance Fields Responder URL; Exception Status (malformedRequest(1), internalError(2), tryLater(3), sigRequired(5), unauthorized(6))
Action Ensure that the certificate is good for checking its status via the configured/AIA OCSP URL.
Impact TLS OCSP certificate status is unknown.
sonusOcspResponseUnknown - MINOR
Type: MINOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.20.0.4
Description This trap indicates a valid OCSP response is received from the responder with an unknown certificate status.
Repetition None
Event Codes SEC_OCSP_VALID_ UNKNOWN_RESPONSE
Action Make sure the certificate is good for checking its status via the configured/AIA OCSP URL.
Impact TLS OCSP certificate status is unknown.
sonusSbxCertificateExpireSoonWarningNotification - MAJOR
Type: MAJOR
Object 1.3.6.1.4.1.2879.2.8.1.2.1.12.0.21
ID
Descri This alarm indicates that the certificate mentioned will expire in the specified number of days.
ption
Based on the configuration, set system security certExpiryCheck expiryWarningThreshold 30
expirationPeriodicWarning 3 certReCheckRate 24, the following actions are performed on a daily basis:
1. Get the expiry time of the certificate.

2. Get the current time.
3. Determine the number of days difference.
a. If the difference in days is equal to threshold (for example, 30) then generate alarm. Otherwise,
b. If the difference is less than the threshold then if it is a multiplier of the periodic warning rate (for example, 3 that is 27
days, 24 days) then generate alarm. Otherwise,
c. Generate info level log – for example, 'certificate <certname>remote is <X> days away from expiration'. That is, the alarm
is triggered when either 30 days is remaining, or on multiple of 3 days. For example, 27 days left, 24 days left, 21 days left.
Note: Once the certificate is past its expiry date, the alarm is generated on a daily basis until it is replaced or disabled.
Repeti Yes. See the description above for details.

tion
Event
sonusAlarmLevel
sonusAlarmTime
sonusSecurityCertName
sonusSecurityCertExpiryDaysLeft
Instan
ce sonusSecurityCertName
Fields sonusSecurityCertExpiryDaysLeft
Action Replace the certificate to avoid call processing impact. If the certificate is no longer required, disable it to stop the alarm from being
generated.
Impact May impact call processing if the certificate is required to create secure connections.
Cleari Manual
ng
sonusSbxFailedCertificateReCheck - MAJOR
Type: MAJOR
Object 1.3.6.1.4.1.2879.2.10.1.1.1.0.36
ID
Descripti This trap indicates that the certificate re-check during TLS session failed. Failed check due to either certificate expiration, trust anchor
on invalidity or when the certificate has been revoked, if OSCP is enabled.
Repetition None
Event ENUM_sonusEventLevel_major
Codes
Instance None
Fields
Action None, this is just a warning
Impact Log and SEC module terminates the TLS session.
Clearing Automatic
sonusSbxLogFileEncryptionSettingsChangedNotification -
MAJOR
Type: Major
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.12.0.22
Description This trap indicates that the log file encryption settings have changed.
Repetition No
Event Codes
sonusAlarmNodeID
sonusAlarmLevel
sonusAlarmTime
sonusEvLogTypeName
sonusEvLogEncryptionChangeType
Instance Fields
sonusEvLogTypeName
sonusEvLogEncryptionChangeType
Action Check the Audit logs to ensure that this change was made by an authorized party.
Impact Log file encryption has been turned off, or the encryption key has changed.
Clearing Manual
sonusSystemSecurityAccountAutoReEnabled - MINOR
Type: MINOR
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.12.0.19
Description This alarm indicates that an account previously disabled due to a user exceeding the number of password attempts was
automatically re-enabled.
Repetition N/A
Event Codes
sonusAlarmNodeID
sonusAlarmLevel
Instance
sonusUserName
Action None
Impact None. This alarm clears the sonusSystemSecurityAccountLocked alarm when the type is set to auto-unlock
Clearing Automatic; sonusSystemSecurityAccountLocked
sonusSystemSecurityAccountConfigChange - MINOR
Type: MINOR
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.12.0.14
Description This trap is generated when the specified user account settings changed.
Repetition N/A
Event Codes
sonusAlarmNodeID
sonusAlarmLevel
sonusAlarmTime
sonusUserName
sonusConfigChange
Instance Fields
sonusUserName
sonusConfigChange
Action None
Impact The user configuration settings are changed.
Clearing Manual
sonusSystemSecurityAccountCreatedNotification - MINOR
Type: MINOR
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.12.0.8
Description This trap is generated when an account is created.
Repetition N/A

sonusAlarmLevel
sonusAlarmTime
sonusUserName
Instance Fields sonusUserName
Action None
Impact None
Clearing Manual
sonusSystemSecurityAccountDisabledNotification - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.12.0.6
Description This trap indicates that an account is automatically disabled after the configured account aging period is reached.
Repetition None

sonusAlarmLevel
sonusAlarmTime
sonusUserName
Action If the account is active, enable it; otherwise remove it.
Impact User account is disabled and can no longer access the system.
Clearing Manual
sonusSystemSecurityAccountLocked - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.12.0.15
Description This alarm is generated when an account is locked after a potential brute force attack.
Repetition N/A

sonusAlarmLevel
sonusAlarmTime
sonusUserName
sonusUnlockType

sonusUnlockType
Action Wait until the account is automatically unlocked, or is manually enabled, before attempting to access the account again.
Impact The account is not accessible until unlocked.
Clearing Automatic; sonusSystemSecurityAccountAutoReEnabled
Note
The account lockout status and number of failed login attempts are preserved even after the server is rebooted. The 'linuxadmin' account is
locked like other OS accounts, but only for 10 seconds, and will then unlock automatically.
sonusSystemSecurityAccountManuallyDeletedNotification -
MINOR
Type: MINOR
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.12.0.9
Description This alarm is generated when an account is manually deleted.
Repetition N/A

sonusAlarmLevel
sonusAlarmTime
sonusUserName
Action None
Impact The account is no longer accessible.
Clearing Manual
sonusSystemSecurityAccountNewGroupNotification - MINOR
Type: MINOR
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.12.0.10
Description This trap is generated when a user is assigned to a group.
Repetition N/A

sonusAlarmLevel
sonusAlarmTime
sonusUserName
sonusGroupName

sonusGroupName
Action None
Impact A user is assigned to a group.
Clearing Manual
sonusSystemSecurityAccountReEnabled - MINOR
Type: MINOR
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.12.0.11
Description This trap is generated when an account is re-enabled.
Repetition N/A

sonusAlarmLevel
sonusAlarmTime
sonusUserName
Action None
Impact The account is accessible.
Clearing Manual
sonusSystemSecurityAccountRemovedNotification - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.12.0.7
Description This trap indicates that an account is automatically removed as it is not used during the account removal period.
Repetition None

sonusAlarmLevel
sonusAlarmTime
sonusUserName
Action If the account is still needed, recreate it.
Impact The affected account is removed. The user of the account may no longer access the system.
Clearing Manual
sonusSystemSecurityAccountSshKeyChange - MINOR
Type: MINOR
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.12.0.13
Description This trap is generated when SSH keys are added or removed for a particular user, or for all users.
Repetition N/A

sonusAlarmLevel
sonusAlarmTime
sonusUserName
Action None
Impact An SSH key is added, removed or restored to an account.
Clearing Manual
sonusSystemSecurityLargeConsoleSessionLog - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.12.0.17
Description This trap indicates that a Console Session Log file has reached at least 1 GB in size.
Repetition None

sonusAlarmLevel
sonusAlarmTime
sonusFileName
sonusUserName
sonusProcessId
Instance Fields sonusFileName

sonusUserName
sonusProcessId
Action Review user activity for anything suspicious.
Impact None
Clearing Manual
sonusSystemSecurityNewPrivateHashingKey - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.12.0.18
Description This trap indicates that a new key is being used to hash the event log files.
Repetition None

sonusAlarmLevel
sonusAlarmTime
sonusFileName
sonusKeyName
Instance Fields sonusFileName

sonusKeyName
Action None
Impact Event Logs will now be hashed using this new key
Clearing Manual
sonusSystemSecurityOsAccountAutoReEnabled - MINOR
Type: MINOR
Objec 1.3.6.1.4.1.2879.2.8.1.2.1.12.0.20
t ID
Descr This alarm indicates that an OS account has been auto re-enabled after being disabled due to bad passwords.
iption
Repet N/A
ition
Insta sonusAlarmTime
nce
sonusUserName
sonusSystemServerName
Action None
Impact An OS user account that was locked temporarily because a wrong password was entered too many times is now unlocked again, as the
correct password was entered. This alarm clears sonusSystemSecurityOsAccountLocked when the type is auto-unlock and the
ServerName matches.
Cleari Automatic; sonusSystemSecurityOsAccountLocked

ng
sonusSystemSecurityOsAccountLocked - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.12.0.16
Description This trap is generated when an OS account is locked after a potential brute force attack.
Repetition N/A

sonusAlarmLevel
sonusAlarmTime
sonusUserName
sonusUnlockType

sonusUnlockType
Action Wait until the OS account is automatically unlocked, or is manually enabled, before attempting to access the account.
Impact The OS account is not accessible until unlocked.
Clearing Automatic; sonusSystemSecurityOsAccountAutoReEnabled
Note
Account lockout status and number of failed login attempts are preserved even after the server is rebooted. The 'linuxadmin' account is
locked like other OS accounts, but only for about 10 seconds, and will then unlock automatically.
sonusSystemSecurityOsAccountReEnabled - MINOR
Type: MINOR
Object ID 1.3.6.1.4.1.2879.2.8.1.2.1.12.0.12
Description This trap is generated when an OS account is re-enabled.
Repetition N/A

sonusAlarmLevel
sonusAlarmTime
sonusUserName
Action None
Impact The OS account is accessible.
Clearing Manual

This section contains following SIP Recording alarm:
sonusSbxSipRecSrsSelectionFailedNotification - MINOR
sonusSbxSipRecSrsSelectionFailedNotification - MINOR
Type: MINOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.1.0.59
Description This alarm is generated to indicate the failure to initiate SIPREC recording due to any of the following reasons:
Failure to select SIP Recording Server.

When original CS call is SRTP and the SIPREC is triggered through CLI.
When DTLS-SRTP call is supported.
When SBC offers SRTP towards SRS and the SRS answers with either invalid crypto or with RTP.
Repetition None

sonusAlarmLevel
sonusAlarmTime
sonusRecCallGCID
sonusRecNumStreamsConfigured
sonusRecInitFailureReason
Instance Fields sonusRecCallGCID

sonusRecNumStreamsConfigured
sonusRecInitFailureReason
Action None
Impact The SIPREC recording initiation failed.
Clearing Manual
This section contains the following SIP Resource Priority Header alarm.
sonusEmergencyMessageRejectNotification - MAJOR
sonusEmergencyMessageRejectNotification - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.1.0.54
Description This alarm indicates an Emergency Out-of-Dialog Request is rejected.
Repetition Yes
Event Codes
sonusEmergencyMessageRejected – The type of the message rejected
sonusRPHNamespace – The RPH name space in the ingress message
sonusRPHPriority – The RPH name space priority in the ingress message
Action Verify SBC CAC Resources are available.
Impact All emergency messages are rejected.
Clearing Manual
This section describes the following SIP Signaling alarms.
sonusSbxArsEndPointBlacklistedNotification2 - MINOR
sonusSbxArsEndPointBlacklistedNotification2V6 - MINOR
sonusSbxArsEndPointRecoveredNotification2 - MINOR
sonusSbxArsEndPointRecoveredNotification2V6 - MINOR
sonusSbxArsEndPointsRecoveredNotification2 - MINOR
sonusSbxDropSipMessageFromUnknownSourceNotification - INFORMATIONAL
sonusSbxLocalSurvivabilityModeActiveNotification - MINOR
sonusSbxLocalSurvivabilityModeActiveNotificationV6 - MINOR
sonusSbxLocalSurvivabilityModeClearNotification - MINOR
sonusSbxLocalSurvivabilityModeClearNotificationV6 - MINOR
sonusSbxSipCallSigPortCloseNotification - MAJOR
sonusSbxSipCallSigPortCloseNotificationV6 - MAJOR
sonusSbxSipCallSigPortOpenNotification - MAJOR
sonusSbxSipCallSigPortOpenNotificationV6 - MAJOR
sonusSbxSipMultipleContactsPerAorSigPortExhaustedNotification - MINOR
sonusSbxSipRecRecordingFailedNotification - MINOR
sonusSbxSipRecRecordingFailedNotificationV6 - MINOR
sonusSbxSipRegistrantPortChangeNotification - MAJOR
sonusSbxSipSignalingPortRangeRegistrationFailedNotification - MINOR
sonusSbxSipSignallingRecordingRejectedServerUnavailable - MINOR
sonusSbxSipSignallingRecordingRejectedServerUnavailableV6 - MINOR
sonusSbxSipTgRegLimitReachedNotification - MAJOR
sonusSbxSipTrunkGroupInServiceNotification - MINOR
sonusSbxSipTrunkGroupOutOfServiceNotification - MAJOR
sonusSbxSuppressNonRouteInviteResponseNotification - MINOR
sonusSbxSipSignalingPortRangeRcbCleanpOnCrlfFailure - MINOR
sonusSbxArsEndPointBlacklistedNotification2 - MINOR
Type: MINOR
Object 1.3.6.1.4.1.2879.2.10.1.1.1.0.72
ID
Descrip This trap indicates that the IPv4 SIP endpoint with the specified IP address, port and signaling zone was blacklisted because it
tion met the blacklisting criteria defined in the SIP ARS profile assigned to the egress trunk group.
Refer to SIP ARS Profile - CLI for details on the triggering criteria.
Repetiti None
on
Event EVENT_ARS_ENDPOINT_BLACKLISTED
Codes
Instanc
e Fields sonusAlarmNodeID
sonusAlarmLevel
sonusAlarmTime
sonusSipArsStatEndpointIpAddress
sonusSipArsStatEndpointIpPortNum
sonusSipArsStatSigZoneId
sonusSipArsStatSigPortNum
sonusSipArsStatEndpointOwnerId
sonusSipArsStatSigZoneName
Action Ensure SIP peer is available to take SIP calls and is reachable.
Impact The specified endpoint is unreachable and is bypassed when routing SIP calls.
Clearing Manual
sonusSbxArsEndPointBlacklistedNotification2V6 - MINOR
Type: MINOR
Object 1.3.6.1.4.1.2879.2.10.1.1.1.0.75
ID
Descrip This trap indicates that the IPv6 SIP endpoint with the specified IP address, port and signaling zone was blacklisted because it
tion met the blacklisting criteria defined in the SIP ARS profile assigned to the egress trunk group.
For details on the triggering criteria, refer to SIP ARS Profile - CLI.
Repetiti None
on
Event EVENT_ARS_ENDPOINT_BLACKLISTED_V6
Codes
Instanc
sonusAlarmLevel
sonusAlarmTime
sonusSipArsStatEndpointIpAddressV6
Action Ensure SIP peer is available to take SIP calls and is reachable.
Impact The specified endpoint is unreachable and is bypassed while routing SIP calls.
Clearing Manual
sonusSbxArsEndPointRecoveredNotification2 - MINOR
Type: MINOR
Object 1.3.6.1.4.1.2879.2.10.1.1.1.0.73
ID
Descrip This trap indicates that the IPv4 SIP endpoint with the specified IP address, port and signaling zone is no longer blacklisted
tion because it met the recovery criteria defined in SIP ARS profile assigned to the egress trunk group.
Refer to SIP ARS Profile - CLI for details on the recovery criteria.
Repetiti None
on
Event EVENT_ARS_ENDPOINT_RECOVERED
Codes
Instanc
sonusAlarmLevel
sonusAlarmTime
Action None
Impact The specified endpoint is now reachable and is no longer bypassed when routing SIP calls.
Clearing Manual
sonusSbxArsEndPointRecoveredNotification2V6 - MINOR
Type: MINOR
Object 1.3.6.1.4.1.2879.2.10.1.1.1.0.76
ID
Descrip This trap indicates that the IPv6 SIP endpoint with the specified IP address, port and signaling zone is no longer blacklisted
tion because it met the recovery criteria defined in SIP ARS profile assigned to the egress trunk group.
Repetiti None
on
Event EVENT_ARS_ENDPOINT_RECOVERED_V6
Codes
Instanc
sonusAlarmLevel
sonusAlarmTime
Action None
Impact The specified endpoint is now reachable and is no longer bypassed when routing SIP calls.
Clearing Manual
sonusSbxArsEndPointsRecoveredNotification2 - MINOR
Type: MINOR
Object 1.3.6.1.4.1.2879.2.10.1.1.1.0.74
ID
Descrip This trap indicates that all SIP endpoints with the specified IP address, port and signaling zone are no longer blacklisted because
tion they met the recovery criteria defined in SIP ARS profile assigned to the egress trunk group.
Repetiti None
on
Event EVENT_ARS_ENDPOINTS_RECOVERED
Codes
Instanc
sonusAlarmLevel
sonusAlarmTime
sonusSipArsEndpointRecoveryAll
Action None
Impact The endpoints are now reachable and not bypassed when routing SIP calls.
Clearing Manual
sonusSbxDropSipMessageFromUnknownSourceNotification
- INFORMATIONAL
Type: INFORMATIONAL
Object ID 1.3.6.1.4.1.2879.2.10.1.1.1.0.49
Description This trap is generated when when a SIP message is dropped due to "Known Peer FQDN" check.
Repetition None

sonusAlarmLevel
sonusAlarmTime
sonusDropSipMsgFromUnknowSrcAddress
sonusDropSipMsgFromUnknowSrcMsgType
Action None
Impact None
Clearing None
sonusSbxLocalSurvivabilityModeActiveNotification - MINOR
Type: MINOR
Object 1.3.6.1.4.1.2879.2.10.1.1.1.0.64
ID
Descripti This alarm indicates that local survivability mode is active for a SIP server of the specified IPv4 address, port, Signaling zone. The
on alarm clears when the application server connectivity or overload is restored.
Repetition None
Event
sonusAlarmLevel
sonusAlarmSequenceID
Instance
Action Restore connectivity to Application Server, or eliminate the AS overload conditions. Ensure the SIP peer is available to take SIP calls
and is reachable.
Impact The specified end-point is bypassed and calls are routed locally.
Clearing Automatic; sonusSbxLocalSurvivabilityModeClearNotification
sonusSbxLocalSurvivabilityModeActiveNotificationV6 -
MINOR
Type: MINOR
Object 1.3.6.1.4.1.2879.2.10.1.1.1.0.65
ID
Descripti This alarm indicates that local survivability mode is active for a SIP server of the specified IPv6 address, port, signaling zone. This
on alarm clears when the application server connectivity or overload is restored.
Repetition None
Event
sonusAlarmLevel
Instance
Action Restore connectivity to Application Server, or eliminate the AS overload conditions. Ensure the SIP peer is available to take SIP calls
and is reachable.
Impact The specified end-point is bypassed and calls are routed locally.
Clearing Automatic, sonusSbxLocalSurvivabilityModeClearNotificationV6
sonusSbxLocalSurvivabilityModeClearNotification - MINOR
Type: MINOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.1.0.66
Description This alarm indicates that local survivability mode is cleared for a SIP server of the specified IPv4 address, port, signaling zone.
Repetition None
Event Codes
sonusAlarmNodeID
sonusAlarmLevel
Instance Fields
sonusAlarmTime
Action None
Impact The specified end-point is no longer bypassed for routing calls
Clearing Automatic; sonusSbxLocalSurvivabilityModeActiveNotification
sonusSbxLocalSurvivabilityModeClearNotificationV6 - MINOR
Type: MINOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.1.0.67
Description This alarm indicates that local survivability mode is cleared for a SIP server of the specified IPv6 address, port, and signaling
zone.
Repetition None
Event Codes
sonusAlarmNodeID
sonusAlarmLevel
Instance
Action None
Impact The specified end-point is no longer bypassed for routing calls.
Clearing Automatic, sonusSbxLocalSurvivabilityModeActiveNotification
sonusSbxSipCallSigPortCloseNotification - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.1.0.2
Description This alarm indicates that a call signaling port is closed (IPv4).
Repetition None
Event Codes sonusSipSigPortIpAddress—IP address of the Sip Signaling Port - mandatory

parameter.
sonusSipSigPortNum—UDP port number of SIP Signaling Port (default is 5060).
sonusSipSigProto—The name of the signaling transport protocol.
Action None
Impact None
Clearing Automatic, sonusSbxSipCallSigPortOpenNotification
sonusSbxSipCallSigPortCloseNotificationV6 - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.1.0.26
Description This alarm indicates that a call signaling port is closed (IPv6).
Repetition None
Event Codes sonusSipSigPortIpAddressV6—IP address of the Sip Signaling Port - mandatory

parameter.
Action None
Impact None
Clearing Automatic, sonusSbxSipCallSigPortOpenNotificationV6
sonusSbxSipCallSigPortOpenNotification - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.1.0.1
Description This alarm indicates that a call signaling port is opened (IPv4).
Repetition None
Event Codes
sonusSipSigPortIpAddress—IP address of the Sip Signaling Port - mandatory parameter.
Action None
Impact None
Clearing Manual
sonusSbxSipCallSigPortOpenNotificationV6 - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.1.0.21
Description This alarm indicates that a call signaling port is opened (IPv6).
Repetition None
Event Codes sonusSipSigPortIpAddressV6-IP address of the Sip Signaling Port - mandatory

parameter.
sonusSipSigPortNum-UDP port number of SIP Signaling Port (default is 5060).
Action None
Impact None
Clearing Manual
sonusSbxSipMultipleContactsPerAorSigPortExhaustedNotification
Type: MINOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.1.0.16
Description This trap indicates that an Address of Record (AOR) registering from multiple contact addresses is reusing a signaling port towards
the registrar. This trap is generated once per zone.
Repetition None
Event sonusSipAorSigZoneId
Codes
Instance None
Fields
Action Ensure enough signaling ports are allocated in the Zone.
Impact Calls are not routed towards the AOR registered prior to this registration unless the registrar supports reg-info parameter.
Clearing Manual
sonusSbxSipRecRecordingFailedNotification - MINOR
Type: MINOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.1.0.41
Description This alarm indicates that the recording request is rejected due to the unavailability of the recording server (IPv4).
Repetition None
Event Codes SIPSG_RECORDING_FAILED
Instance Fields
sonusRecorderIpAddress – The IPv4 address of the unavailable recorder
sonusRecorderPortNum – The port of the unavailable recorder
sonusRecCallGCID – The GCID of the call being recorded
sonusRecorderTrunkName – The trunk group name where the recorder is configured
sonusRecordingCallLeg – The leg, ingress or egress, being recorded
Action None
Impact Recording failed for the specified IPv4 recorder
Clearing Manual
sonusSbxSipRecRecordingFailedNotificationV6 - MINOR
Type: MINOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.1.0.42
Description This alarm indicates that the recording request is rejected due to unavailability of the recording server (IPv6).
Repetition None
Event Codes SIPSG_RECORDING_FAILED_V6
Instance Fields
Action None
Impact Recording failed for the IPv6 recorder
Clearing Manual
sonusSbxSipRegistrantPortChangeNotification - MAJOR
Type: MAJOR
Object 1.3.6.1.4.1.2879.2.10.1.1.1.0.5
ID
Descrip This trap indicates that at least one SIP registrant has a source port number that changed over two or more consecutive REGISTER
tion refreshes, possibly indicating that the registrant was unreachable from the SBC for a time.
The NAT between the SIP endpoint (IAD) and the SBC is closing its pinhole before the IAD sends a REGISTER refresh to the SBC.
Repetiti None
on
Event None
Codes
Instanc None
e Fields
Action Check Registration refresh timing between IAD and SBC together with the NAT pinhole timing.
Impact At least one SIP Registrant has a port number that keeps changing.
Clearing Manual
sonusSbxSipSignalingPortRangeRegistrationFailedNotification - M
Type: MINOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.1.0.50
Description This trap indicates that registration is rejected due to the unavailability of the ports.
Repetition Repeats every time the registration fails due to unavailability of the ports
Event Codes SIPSG_PORT_RANGE_REGISTRATION_FAILED
Instance Fields sonusAddressContextName, sonusZoneName, sonusTrunkgroupName
Action Increase the range of configured ports within the media port range under system level or IP Trunk Group, if configured,
Impact Registration failed. Any further registrations on this SIP Trunk Group does not succeed.
Clearing Manual
sonusSbxSipSignallingRecordingRejectedServerUnavailable
- MINOR
Type: MINOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.1.0.43
Description This alarm indicates that recording request is rejected due to unavailability of the recording server (IPv4).
Repetition None
Event Codes SIPSG_RECORDING_SERVER_UNAVAILABLE
Instance Fields
sonusRecorderIpAddress – The IPv4 of the unavailable recorder
sonusRecorderTrunkName – The trunk group name where recorder is configured
Action None
Impact The recording fails if it does not resume on the second server (if available).
Clearing Manual
sonusSbxSipSignallingRecordingRejectedServerUnavailableV6 - M
Type: MINOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.1.0.44
Description This alarm indicates that the recording request is rejected due to unavailability of the recording server (IPv6).
Repetition None
Event Codes SIPSG_RECORDING_SERVER_UNAVAILABLE_V6
Instance Fields
sonusRecorderPortNum – The port of unavailable recorder
Action None
Impact The recording fails if it does not resume on the second recording server (if available).
Clearing Manual
sonusSbxSipTgRegLimitReachedNotification - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.1.0.9
Description This trap indicates that the specified trunk group's configured maximum registration limit is reached due to one of the following
conditions:
Number of registrations received on the ingress leg exceeds the configured limit
Number of implicit/child registrations received on the ingress leg exceeds the configured limit
Repetition None

sonusAlarmLevel
sonusAlarmTime
sonusSipTgName
Instance sonusSipTgName
Fields
Action None
Impact None
Clearing Manual
Note
The maximum number of registrations allowed is user-configurable.
sonusSbxSipTrunkGroupInServiceNotification - MINOR
Type: MINOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.1.0.3
Description This alarm indicates that the SIP Trunk Group was put into service by maintenance staff.
Repetition None
Event Codes sonusSipTgName—The name of the SIP Trunk Group.
Action None
Impact Calls to the indicated SIP Trunk Group are allowed.
Clearing Manual
sonusSbxSipTrunkGroupOutOfServiceNotification - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.1.0.4
Description This alarm indicates that the SIP Trunk Group was taken out of service by maintenance staff.
Repetition None
Event Codes sonusSipTgName—The name of the SIP Trunk Group.
Action None
Impact Calls to the indicated SIP Trunk Group are not allowed. New calls may be impacted/rejected.
Clearing Automatic, sonusSbxSipTrunkGroupInServiceNotification
sonusSbxSuppressNonRouteInviteResponseNotification -
MINOR
Type: MINOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.1.0.46
Description The alarm indicates that the non-routed incoming invite was silently dropped.
Repetition None

sonusAlarmLevel
sonusAlarmTime
sonusNonRouteInviteRequestUri
sonusNonRouteInviteSourceIpAddress
sonusNonRouteInviteSourceIpPortNum
Action None
Impact None
Clearing Manual
sonusSbxSipSignalingPortRangeRcbCleanpOnCrlfFailure -
MINOR
Type: MINOR
Object 1.3.6.1.4.1.2879.2.10.1.1.1.0.95
ID
Descri This alarm is only used in conjunction with a deployment that has a unique TLS connection to the registrar for each user. The alarm
ption is generated on a per user basis, when the registrar fails to respond to a CRLF ping from the SBC, or if there is an SBC switchover.
Repeti Generated on a per user basis. The instance fields identify the unique user.
tion
Event
sonusAlarmLevel
sonusAlarmTime
Instan
ce sonusFromHeader
Fields sonusAuthUserName
sonusSipInstanceId
sonusTrunkGroupName
Action The SBC may have switched over, or the registrar may not be working correctly. Check and resolve the issue.
Impact The SBC removes the registration details of the user. You must register with the SBC/registrar again before making or receiving
calls.
Cleari Manual
ng
This section contains the following Softswitch Client Services (SSCS) alarms.
sonusSbxSscsInServiceNotification - MAJOR
sonusSbxSscsOutOfServiceNotification - CRITICAL
sonusSbxSscsRejectIndNotification - MINOR
sonusSbxSscsRouteFailureNotification - MAJOR
sonusSbxSscsRouteFailureWithoutGapNotification2 - MAJOR
sonusSbxSscsTransErrorNotification - MINOR
sonusSbxSscsInServiceNotification - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.3.0.6
Description The alarm indicates that the softswitch is now in service. A state and a reason for the notification are provided.
Repetition Yes
Event Codes
sonusAlarmNodeID
sonusAlarmLevel
sonusAlarmTime
sonusPscsPolicyServerName
sonusPscsOperState
sonusPscsInServiceReason
Instance Fields sonusPscsPolicyServerName
Action None
Impact None
Clearing Manual
sonusSbxSscsOutOfServiceNotification - CRITICAL
Type: CRITICAL
Object ID 1.3.6.1.4.1.2879.2.10.1.1.3.0.5
Descripti Indicates a softswitch is now out of service. A reason for the notification is included in the alarm.
on
Repetition Yes
Event
sonusAlarmLevel
sonusAlarmTime
sonusPscsOperState
sonusPscsInServiceReason
Instance sonusPscsPolicyServerName
Fields
Action Investigate the fault, and take action based upon operational states below:
configured(1) – Determine the reason for the administrative change.

connectionLoss(2) – Check connectivity to and status of PSX by accomplishing Action steps of alarm
"sonusSoftswitchDownNotification" located in PSX Alarm Troubleshooting Guide.
noConnection(3) – No action required; An automatic retry will occur.
nodeNameChange(4) – No action required; An automatic retry will occur.
incompatibleVersion(5) – Check software versions running on SBC and PSX to ensure SBC software is equal to or no more
than two versions older than PSX software version.
PSX – Login to PSX and display EMS PSX Manager GUI. The top left corner of the window displays the PSX GUI and
server software versions.
SBC – Login to SBC EMA GUI. The current software version displays on EMA screen at the top.
Refer to the PSX Provisioning Guide for help with verifying PSX IP address and port settings.
Impact Loss of communication with the specified PSX.
Clearing Automatic, sonusSbxSscsInServiceNotification
sonusSbxSscsRejectIndNotification - MINOR
Type: MINOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.3.0.4
Description This trap indicates a reject indication was received from the PSX.
Repetition None
Event Codes
sonusPscsPolicyServerName—The name of this Softswitch.
sonusPscsRejectIndReason—The reason why a "reject ind" is received:
notRegistered(1)
unknownGateway(2)
errorAVPContent(3)
errorMsgContent(4)
maxClientAccount(5)
miscRegFailure(6)
Action None
Impact None
Clearing Manual
sonusSbxSscsRouteFailureNotification - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.3.0.2
Description This trap indicates a route look up has failed. The SBC did not return any route for a call.
Repetition None
Event Codes
sonusPscsRouteFailureReason—The reason why a route look up has failed:
routeNotFound(1) –No routes provisioned on SBC for call; badly formatted, mis-dialed, or unexpected number.
noServiceConfigured(2) – Configuration error.
databaseError(3) – SBC database may be corrupt.
sonusPscsCalledNumber—Destination number.
sonusPscsCallingNumber—Originating number.
sonusPscsCarrierCode—Carrier code.
sonusPscsGapNumber—Gap number. Valid only in the case of LNP number translation.
Action None
Impact Call failed
Clearing Manual
sonusSbxSscsRouteFailureWithoutGapNotification2 - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.3.0.7
Description This alarm indicates that a route look without GAP (Generic Address Parameter) failed.
Repetition None

sonusAlarmLevel
sonusAlarmTime
sonusPscsRouteFailureReason
sonusPscsCalledNumber
sonusPscsCallingNumber
sonusPscsCarrierCode
Action None
Impact Call may fail
Clearing Manual
sonusSbxSscsTransErrorNotification - MINOR
Type: MINOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.3.0.3
Description This trap indicates the specified softswitch encountered a transactional error.
Repetition None
Event Codes
sonusPscsTranErrorReason—The reason why a transaction has failed:
noSoftswitchAvailable(1)
transactionTimeout(2)
invalidParameters(3)
receiveError(4)
transmitError(5)
encodeApiError(6)
decodeApiError(7)
noMatchingReplyCbFound(8)
Action None
Impact None
Clearing Manual
This section contains the following WRTC alarms.
sonusSbxIceStunMsgValidationFailNotification - MAJOR
sonusSbxIceStunMsgValidationFailNotificationV6 - MAJOR
sonusSbxIceTimerExpiryNotification - MAJOR
sonusSbxIceTimerExpiryNotificationV6 - MAJOR
sonusSbxIceStunMsgValidationFailNotification - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.1.0.51
Description This trap indicates that authentication validation failed for a STUN message for that call leg (local IP address type is IPv6).
Repetition None
Event Codes
sonusAlarmNodeID
sonusAlarmLevel
sonusAlarmTime
sonusSipIceGcid
sonusSipIceRemoteIpAddress
sonusSipIceRemotePort
sonusSipIceLocalIpAddress
sonusSipIceLocalPort
sonusSipIceFailReason
Instance Fields
sonusSipIceGcid
sonusSipIceRemoteIpAddress
sonusSipIceRemotePort
sonusSipIceFailReason
Action Check with the operator at the remote end point regarding the sending of invalid messages.
Impact The invalid STUN message is not processed, and failure to authenticate may indicate that spoofed packets are received.
Clearing Manual
sonusSbxIceStunMsgValidationFailNotificationV6 - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.1.0.56
Description This trap indicates that validation failed for the first STUN message for that call leg (local IP address type is IPv6).
Repetition None
Event Codes
sonusAlarmNodeID
sonusAlarmLevel
sonusAlarmTime
sonusSipIceGcid
sonusSipIceRemoteIpV6Address
sonusSipIceLocalIpV6Address
sonusSipIceFailReason(string)
Instance Fields
sonusSipIceGcid
sonusSipIceRemoteIpV6Address
Action Check with the operator at the remote end point regarding the sending of invalid messages.
Impact The invalid STUN message is not processed, and failure to authenticate may indicate that spoofed packets are received.
Clearing Manual
sonusSbxIceTimerExpiryNotification - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.1.0.55
Description This trap indicates that the STUN check timer is expired, and the call is disconnected when using local IPv4 address.
Repetition None

sonusAlarmLevel
sonusAlarmTime
sonusSipIceGcid
Instance Fields sonusSipIceGcid

Action Check why the remote end is not able to complete STUN/ICE signaling correctly.
Impact The call disconnects once the STUN check timer expires.
Clearing Manual
sonusSbxIceTimerExpiryNotificationV6 - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.1.0.57
Description This trap indicates that the STUN check timer expired, and the call is disconnected when using a local IPv6 address.
Repetition None

sonusAlarmLevel
sonusAlarmTime
sonusSipIceGcid
Instance Fields sonusSipIceGcid

Action Check why the remote end is not able to complete STUN/ICE signaling correctly.
Impact The call disconnects once the STUN check timer expires.
Clearing Manual

This section describes the tone and announcement alarm.
Table of Contents
sonusSbxToneAnnouncementFailedNotification - MINOR
sonusSbxToneAnnouncementFailedNotification - MINOR
Type: MINOR
Object 1.3.6.1.4.1.2879.2.10.1.1.4.0.45
ID
Descrip This alarm is raised when the SBC is configured to play the specified tone using announcement-based files, and the matching tone
tion announcement files are not present in the system path (/var/log/sonus/sbx/announcements/).
Repetiti N/A
on
sonusAlarmTime
sonusNrmaToneType
sonusNrmaCodecType
sonusNrmaCodecAttr
Instanc sonusNrmaToneType
e Fields sonusNrmaCodecType
sonusNrmaCodecAttr
Action The user must create and add the respective tone and announcement file. To create a Tone and Announcement file, see section Tone
As Announcement Profile.
Impact The specified tone does not play
Clearing Manual
This section contains the following Surrogate Registration alarms.
sonusSbxSurrRegAuthenticationClearNotification - MAJOR
sonusSbxSurrRegAuthenticationFailedNotification - MAJOR
sonusSbxSurrRegRegistrationFailedNotification - MAJOR
sonusSbxSurrRegRegistrationFailedNotificationV6 - MAJOR
sonusSbxSurrRegRegistrationSuccessNotification - MAJOR
sonusSbxSurrRegRegistrationSuccessNotificationV6 - MAJOR
sonusSbxSurrRegAuthenticationClearNotification - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.1.0.38
Description This alarm is used to clear sonusSbxSurrRegAuthenticationFailedNotification. This is raised when surrogate registration is
disabled.
Repetition None
Event Codes SURRREG_AUTHENTICATION_CLEAR
Instance sonusAlarmNodeID
Fields sonusAlarmLevel
sonusAlarmTime
sonusSurrRegPeerName
sonusSurrRegUserPart
sonusSurrRegPeerIpAddress
sonusSurrRegPeerPortNum
sonusSurrRegPeerZoneId
Action None
Impact None
Clearing N/A
sonusSbxSurrRegAuthenticationFailedNotification - MAJOR
Type: MAJOR
Object 1.3.6.1.4.1.2879.2.10.1.1.1.0.37
ID
Descri This alarm is raised when Authentication fails due to credentials mismatch between the SBC and AS.
ption
Repeti None
tion
Event
sonusAlarmLevel
sonusAlarmTime
sonusSurrRegMethodName
sonusSurrRegPeerName
Instan None
ce
Fields
Action If this alarm occurs repeatedly, operator intervention is required to check if the password is correctly set at the SBC and AS.
Impact If the mismatch happens during a call, then the call is cleared. If this happens during registration, surrogate registration is deleted and
the retry timer is restarted.
Cleari Automatic (sonusSbxSurrRegAuthenticationClearNotification), This clearing alarm is raised when surrogate registration is disabled. The
ng corrective action should be to check username/password so that it is similar to what is configured at application server.
sonusSbxSurrRegRegistrationFailedNotification - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.1.0.18
Description This alarm indicates that the surrogate registration for the AOR failed
Repetition None
Event Codes
sonusAlarmNodeID
sonusAlarmLevel
sonusAlarmTime
Action None
Impact None
Clearing Automatic, sonusSbxSurrRegRegistrationSuccessNotification
sonusSbxSurrRegRegistrationFailedNotificationV6 - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.1.0.30
Description This alarm indicates that the surrogate registration failed for an IPv6 peer.
Repetition None
Event Codes
sonusSurrRegPeerIpAddress – Specifies the IPv6 address of the peer.
sonusSurrRegPeerPortNum – Specifies the port number of the peer.
sonusSurrRegPeerZoneId – Specifies the ZoneId of the peer.
sonusSurrRegString – Specifies the string indicates peer is up.
Action None
Impact None
Clearing Automatic, sonusSbxSurrRegRegistrationSuccessNotificationV6
sonusSbxSurrRegRegistrationSuccessNotification - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.1.0.17
Description This alarm indicates that the surrogate registration for the AOR succeeded.
Repetition None
Event Codes
sonusAlarmNodeID
sonusAlarmLevel
sonusAlarmTime
Action None
Impact None
Clearing Manual
sonusSbxSurrRegRegistrationSuccessNotificationV6 -
MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.1.0.29
Description This alarm is generated under one of the following conditions:
When a surrogate registration failure with an IPv6 peer has cleared.

Disabling surrogate registration, once the registration is failed.
Note that the peer is not successfully registered after disabling surrogate registration.
Repetition None
Event Codes
sonusSurrRegPeerIpAddress – Specifies the IPv6 address of the peer.
sonusSurrRegPeerPortNum – Specifies the port number of the peer.
sonusSurrRegPeerZoneId – Specifies the ZoneId of the peer.
sonusSurrRegString – Specifies the string indicates peer is up.
Action None
Impact None
Clearing Manual
Trunk Group Alarms
This section contains the following Trunk Group alarms.
sonusSbxCallRejectedDueToNonRegCacMaxLimitReachedNotification - MAJOR
sonusSbxH323TrunkGroupInServiceNotification - MINOR
sonusSbxH323TrunkGroupOutOfServiceNotification - MAJOR
sonusSbxIpPeerKpiCriticalThresholdClearedNotification - MAJOR
sonusSbxIpPeerKpiCriticalThresholdNotification - MAJOR
sonusSbxTgAuthenticationClearNotification - MAJOR
sonusSbxTgAuthenticationFailedNotification - MAJOR
sonusSbxTrunkGroupAutomaticControlActive3 - INFORMATIONAL
sonusSbxTrunkGroupKpiClearedThresholdNotification - MINOR
sonusSbxTrunkGroupKpiCriticalThresholdClearedNotification - MAJOR
sonusSbxTrunkGroupKpiCriticalThresholdNotification - MAJOR
sonusSbxTrunkGroupKpiMajorThresholdNotification - MAJOR
sonusSbxTrunkGroupManualControlActive3 - INFORMATIONAL
sonusSbxTrunkGroupOutOfResourcesNotification2 - MINOR
sonusSbxTrunkGroupTrafficControlConfChanged2 - INFORMATIONAL
sonusSbxCallRejectedDueToNonRegCacMaxLimitReachedNotificat
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.26.0.1
Description This alarms is raised when the SBC rejects the call as the SBC cannot install CAC from the unregistered endpoints.
Repetition yes

sonusAlarmLevel
sonusAlarmTime
sonusSrcIp
Instance Fields sonusSrcIp
Action The SBC does not install CAC when the maximum CAC count is reached.
Impact Call is rejected.
Clearing Manual
sonusSbxH323TrunkGroupInServiceNotification - MINOR
Type: MINOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.2.0.1
Description This alarm indicates that the H.323 Trunk Group was put into service by maintenance staff.
Repetition None
Event Codes sonusH323TrunkGrpName—Name of the H.323 Trunk Group.
Action None
Impact Calls to the indicated H.323 Trunk Group resume.
Clearing Manual
sonusSbxH323TrunkGroupOutOfServiceNotification - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.2.0.2
Description This alarm indicates that the H.323 Trunk Group was taken out of service by maintenance staff.
Repetition None
Event Codes sonusH323TrunkGrpName—Name of the H.323 Trunk Group.
Action None
Impact None considering this is a planned event.
Clearing Automatic, sonusSbxH323TrunkGroupInServiceNotification
sonusSbxIpPeerKpiCriticalThresholdClearedNotification -
MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.17.0.2
Description This alarm indicates that critical QOS KPI condition in the IP PEER has cleared.
Repetition None
Event Codes sonusPeerName – Specifies the IP PEER name.

sonusZoneName – Specifies the Zone name.
sonusKpi – Specifies the KPI (Key Performance Index) name.
sonusCurrentKpiValue – Specifies the current KPI value.
Action None
Impact Call acceptance resumed.
Clearing Manual
sonusSbxIpPeerKpiCriticalThresholdNotification - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.17.0.1
Description This alarm indicates the IP peer has been put to temporary OOS and is not chosen for Routing.
Repetition None
Event Codes sonusPeerName – Specifies the IP PEER name.

Action None
Impact Call acceptance stopped.
Clearing Automatic, sonusSbxIpPeerKpiCriticalThresholdClearedNotification
sonusSbxTgAuthenticationClearNotification - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.1.0.47
Descripti This alarm occurs when a subsequent call on the same Trunk Group as the previously-attempted call is successful. For example, a
on 200 OK is received in response to a message (INVITE and so on).
Repetition None
Event SIPSG_TG_AUTHENTICATION_SUCCESS
Codes
Instance sonusTgTrunkGroupName
Fields
Action None
Impact None
Clearing Automatic; sonusSbxTgAuthenticationFailedNotification
sonusSbxTgAuthenticationFailedNotification - MAJOR
Type: MAJOR
Object 1.3.6.1.4.1.2879.2.10.1.1.1.0.48
ID
Descript This alarm is raised when the IPTG authentication fails for any message with credentials on the Trunk Group.
ion
Repetiti None
on
Event SIPSG_TG_AUTHENTICATION_FAILED
Codes
Instanc sonusTgTrunkGroupName
e Fields
Action Check the authentication credentials (authUserName and authPassword) on the Trunk Group and re-configure, if not correct.
Impact This alarm indicates the IPTG authentication failure for the Trunk Group. It can prevent calls from completing, if the end point
challenges the requests and SBC generates incorrect authentication information in messages.
Clearing Automatic; sonusSbxTgAuthenticationClearNotification. This alarm clears when the message with credentials is accepted on the
Trunk Group.
sonusSbxTrunkGroupAutomaticControlActive3 -
INFORMATIONAL
Type: INFORMATIONAL
Object ID 1.3.6.1.4.1.2879.2.10.1.1.5.0.14
Description This trap indicates that an automatic traffic control was active within the last 30 seconds. The sonusTrunkGroupAutomaticControl
parameter indicates what automatic control was active.
The trap is generated under the following conditions:
At least one automatic traffic control was applied to a call within the last 30 seconds.
A route is skipped due to remote gateway congestion. Trap details identify the IP Trunk Group which contains the congested
gateway.
Repetition None
Event
sonusTrunkGroupAutoCon—This object is a bit mask that indicates what automatic Trunk Group controls were active in the last
30 seconds:
acc(0)
str(1)
silc(2)
dre(3)
pod(4) {applicable to IP Trunk Groups only}
gwAcc(5) {applicable to IP Trunk Groups only}
callPolicing(6)
regPolicing(7)
sonusTgAdditionalData
Instance
Fields sonusAlarmNodeID
sonusAlarmLevel
sonusAlarmTime
sonusTgName
sonusTrunkGroupAutoCon3
Action Investigate to determine if it is appropriate to have automatic controls.
Impact None
Clearing Manual
sonusSbxTrunkGroupKpiClearedThresholdNotification -
MINOR
Type: MINOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.5.0.5
Description This alarm indicates that bad QOS KPI condition in the Trunk Group cleared. Refer to SIP Trunk Advanced - QOE to define
signaling and media QOE KPIs in the SBC.
Repetition None
Event sonusTgName – Specifies the Trunk Group name.

Codes sonusAddressContextName – Specifies the address context name.
Instance None
Fields
Action None
Impact Call reduction settings are removed.
Clearing Manual
sonusSbxTrunkGroupKpiCriticalThresholdClearedNotification - MA
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.5.0.8
Description This alarm indicates that critical QOS KPI condition in the Trunk Group was cleared. Refer to SIP Trunk Advanced - QOE to define
signaling and media QOE KPIs in the SBC.
Repetition None

Codes sonusAddressContextName – Specifies the name of the Address Context.
Instance None
Fields
Action None
Impact Call acceptance resumed.
Clearing Manual
sonusSbxTrunkGroupKpiCriticalThresholdNotification -
MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.5.0.7
Description This alarm indicates that critical QOS KPI condition in the Trunk Group. Refer to SIP Trunk Advanced - QOE to define signaling
and media QOE KPIs in the SBC.
Repetition None

Instance None
Fields
Action None
Impact Call acceptance stopped.
Clearing Automatic, sonusSbxTrunkGroupKpiCriticalThresholdClearedNotification
sonusSbxTrunkGroupKpiMajorThresholdNotification -
MAJOR
Type: MINOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.5.0.6
Description This alarm indicates a major Quality of Service (QOS) KPI condition in the Trunk Group. Refer to SIP Trunk Advanced - QOE to
define signaling and media QOE KPIs in the SBC.
Repetition None

Instance None
Fields
Action None
Impact Call reduction settings are applied.
Clearing Automatic, sonusSbxTrunkGroupKpiClearedThresholdNotification
sonusSbxTrunkGroupManualControlActive3 -
INFORMATIONAL
Type: INFORMATIONAL
Object ID 1.3.6.1.4.1.2879.2.10.1.1.5.0.13
Description This alarm indicates that a Manual traffic control was active within the last 30 seconds. The sonusTrunkGroupManualControl
parameter indicates what manual control was active.
Repetition None
Event
sonusTrunkGroupManCon—This object is a bit mask that indicates what Manual Trunk Group controls were active in the last
30 seconds:
skip(0)
cant(1)
canf(2)
irr(3)
sirr(4)
orr(5)
sorr(6)
Instance
Fields sonusAlarmNodeID
sonusAlarmLevel
sonusAlarmTime
sonusTgName
sonusTrunkGroupManCon3
Action If warranted, investigate to determine why this manual control is active.
Impact None
Clearing Manual
sonusSbxTrunkGroupOutOfResourcesNotification2 - MINOR
Type: MINOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.5.0.12
Description This trap indicates that the specified trunk group has run out of resources in shared CAC pool.
Repetition None
Event Codes sonusTgName – The name of the Trunk Group

caclLimitType – The type of CAC limit that became exhausted
Action None
Impact Calls may not route; new calls may get rejected.
Clearing Manual
sonusSbxTrunkGroupTrafficControlConfChanged2 -
INFORMATIONAL
Type: INFORMATIONAL
Object ID 1.3.6.1.4.1.2879.2.10.1.1.5.0.9
Description This trap indicates that a traffic control configuration object in the Trunk Group table has changed. The sonusTrunkGroupTCObject
parameter indicates what object or objects changed.
Repetition None
Event
sonusTrunkGroupTCObject—This object is a bit mask that indicates what traffic control object in the Trunk Group table has
changed:
sonusTgTCInboundReserved(1)
sonusTgTCCirResvState(2)
sonusTgTCPriorityCallReserve(3)
sonusTgTCIncomingCallReserve(4)
sonusTgTCOutgoingCallReserve(5)
sonusTgTCSilcState(6)
sonusTgTCSilcMC1Percent(7)
sonusTgTCSilcMC2Percent(8)
Instance sonusAlarmNodeID
Fields sonusAlarmLevel
sonusAlarmTime
sonusTgName
sonusTrunkGroupTCObject
Action Investigate to determine if the new behavior is appropriate.
Impact Traffic controls operate according to the new configuration.
Clearing Manual
VNFM Alarms
This section contains the following Virtual Network Function Manager (VNFM) alarms.
sonusSbxSlbConnectionDownNotification - MAJOR
sonusSbxSlbConnectionDownNotificationV6 - MAJOR
sonusSbxSlbConnectionUpNotification - MAJOR
sonusSbxSlbConnectionUpNotificationV6 - MAJOR
sonusSbcSlbConnectionNotEstablishedNotification - MAJOR
sonusSbcSlbConnectionEstablishedNotification - MAJOR
sonusSlbSbcConnectionDownNotification - MAJOR
sonusSlbSbcConnectionUpNotification - MAJOR
sonusSlbSbcRegistrationNotification - MAJOR
sonusSlbSbcsUnreachableNotification - MAJOR
sonusVnfmConnectionFailed - MINOR
sonusVnfmConnectionSucceeded - INFORMATIONAL
sonusSbxSlbGlobalUtilizationThresholdReachedNotification - MAJOR
sonusSbxSlbGlobalUtilizationThresholdClearNotification - MAJOR
The VNFM interoperates with the SBC SWe only.
sonusSbxSlbConnectionDownNotification - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.32.0.6
Description This alarm is raised when the SBC's control channel connection with the Session-Aware Load Balancer (SLB) has gone down
(IPv4).
Repetition None
Event Codes
sonusAlarmNodeID
sonusAlarmLevel
Instance
sonusSlbIpAddress
Action Investigate the cause of the control channel connection failure, and rectify to reestablish communication.
Impact The SBC is not able to communicate with an SLB and process messages.
Clearing Manual
sonusSbxSlbConnectionDownNotificationV6 - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.32.0.8
Description This alarm is raised when the SBC's control channel connection with the Session-Aware Load Balancer (SLB) has gone down
(IPv6).
Repetition None.
Event Codes
sonusAlarmNodeID
sonusAlarmLevel
Instance
sonusSlbIpv6Address
Action Investigate the cause of the control channel connection failure, and rectify to re-establish communication.
Impact The SBC is not able to communicate with the SLB and process messages.
Clearing Manual
sonusSbxSlbConnectionUpNotification - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.32.0.5
Description The SBC has successfully connected and registered with the Session-Aware Load Balancer (SLB).
Repetition None.
Event Codes
sonusAlarmNodeID
sonusAlarmLevel
Instance Fields
sonusAlarmTime
sonusSipSigPortNum
Action None
Impact SBC has successfully connected to and registered with the SLB.
Clearing Manual
sonusSbxSlbConnectionUpNotificationV6 - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.32.0.7
Description The SBC has successfully connected and registered with the SLB.
Repetition None.
Event Codes
sonusAlarmNodeID
sonusAlarmLevel
Instance Fields
sonusAlarmTime
sonusSlbIpv6Address
Action None
Impact The SBC has successfully connected to and registered with the SLB
Clearing Manual
sonusSbcSlbConnectionNotEstablishedNotification - MAJOR
Severity: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.32.0.11
Description The alarm indicates the connection between the SBC and SLB is not established.
Repetition None
Event Codes
sonusAlarmNodeID
sonusAlarmLevel
Instance
sonusSlbName
sonusSlbIpAddress
Action Investigate the cause of the connection failure.
Impact The SLB and SBCs do not communicate. The calls fail.
Clearing Automatic; sonusSbcSlbConnectionEstablishedNotification
The alarm is cleared automatically by the clearing alarm when the connection between the SBC and SLB is established
again.
sonusSbcSlbConnectionEstablishedNotification - MAJOR
Severity: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.32.0.10
Description The alarm indicates the connection between the SBC and SLB is established.
Repetition None
Event Codes
sonusAlarmNodeID
sonusAlarmLevel
Instance Fields
sonusAlarmTime
sonusSlbName
sonusSlbIpAddress
Action None
Impact The SLB is now communicating with an SBC.
Clearing Automatic
sonusSlbSbcConnectionDownNotification - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.32.0.3
Description The control channel connection between the SLB and a registered SBC is down.
Repetition None.
Event Codes
sonusAlarmNodeID
sonusAlarmLevel
Instance Fields
sonusAlarmTime
sonusVnfId
sonusVnfcInstanceId
Action Investigate and fix the cause of the control channel connection failure.
Impact The SLB is not able to communicate with an SBC.
Clearing Manual
sonusSlbSbcConnectionUpNotification - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.32.0.2
Description The control channel connection between the SLB and a registered SBC is up.
Repetition None.
Event Codes
sonusAlarmNodeID
sonusAlarmLevel
Instance Fields
sonusAlarmTime
sonusVnfId
sonusVnfcInstanceId
Action None
Impact The SLB is now able to communicate with an SBC.
Clearing Manual
sonusSlbSbcRegistrationNotification - MAJOR
Type: MAJOR
Object ID .1.3.6.1.4.1.2879.2.10.1.1.32
Description An SBC has registered with the Session-Aware Load Balancer (SLB)
Repetition None.
Event Codes
sonusAlarmNodeID
sonusAlarmLevel
Instance Fields
sonusAlarmTime
sonusVnfId
sonusVnfcInstanceId
Action None
Impact An SBC has successfully registered with the SLB, no action is required.
Clearing Manual
sonusSlbSbcsUnreachableNotification - MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.32.0.4
Description The Session-Aware Load Balancer (SLB) is unable to forward a SIP message because all registered SBCs that could process
that message are unreachable.
Repetition None.
Event
sonusAlarmLevel
Instance
sonusSipSigPortNum
Action Investigate the reason the SBCs are not reachable by the SLB and rectify.
Impact The SLB is not able to forward SIP messages to the SLBs.
Clearing Manual
sonusVnfmConnectionFailed - MINOR
Type: MINOR
Object 1.3.6.1.4.1.2879.2.10.1.1.20.0.6
ID
Descript The alarm indicates SBC connection to VNFM cannot be established. Triggered if the SBC fails to successfully register with
ion VNFM upon startup or subsequently if the heartbeat between SBC and VNFM is missed.
Repetiti Each time the heartbeat is lost between the SBC and VNFM.
on
sonusAlarmTime
sonusVnfmUrlName
Instanc sonusVnfmUrlName
e Fields
Action Make sure VNFM is reachable.
Impact Availability of VNFM connection is lost.
Clearing Automatic; sonusVnfmConnectionSucceeded
sonusVnfmConnectionSucceeded - INFORMATIONAL
Type: INFORMATIONAL
Object ID 1.3.6.1.4.1.2879.2.10.1.1.20.0.7
Description The alarm indicates the SBC connection to VNFM is recovered.
Repetition None

sonusAlarmLevel
sonusAlarmTime
sonusVnfmUrlName
Instance Fields sonusVnfmUrlName
Action None
Impact Availability of VNFM connection is restored.
Clearing Manual
sonusSbxSlbGlobalUtilizationThresholdReachedNotification
- MAJOR
Type: MAJOR
Object 1.3.6.1.4.1.2879.2.10.1.1.32.0.13
ID
Descrip This alarm indicates the Global Utilization threshold for the SLB has reached or exceeded the configured threshold. To configure
tion the Global Utilization, refer to SIP Aware Front End Load Balancer (SLB) - CLI on the SBC.
Repetiti Yes
on
Event
sonusAlarmLevel
sonusAlarmTime
Instanc
e Fields sonusCurrentGlobalUtilization
sonusGlobalUtilizationLimit
Action Add more SBC nodes, or wait until the Global Utilization goes below the threshold.
Impact The Global Utilization has reached or exceeded the notification threshold.
Clearing Automatic; sonusSbxSlbGlobalUtilizationThresholdClearNotification
The alarm is cleared automatically by the clearing alarm when the Global Utilization goes below the threshold limit.
sonusSbxSlbGlobalUtilizationThresholdClearNotification -
MAJOR
Type: MAJOR
Object ID 1.3.6.1.4.1.2879.2.10.1.1.32.0.14
Descripti This alarm indicates the Global Utilization threshold has cleared.
on
Repetition Yes
Event
sonusAlarmLevel
sonusAlarmTime
Instance
Fields sonusCurrentGlobalUtilization
sonusGlobalUtilizationLimit
Action None
Impact Clears the alarm sonusSbxSlbGlobalUtilizationThresholdReachedNotification when the Global Utilization of the SLB goes below
the threshold limit.
Clearing The alarm is cleared when the Global Utilization reduces to < 90% of the configured threshold. For configuring the threshold,
refer to SIP Aware Front End Load Balancer (SLB) - CLI on the SBC
GPU Alarms
This section contains the following GPU alarms:
sonusGpuDeviceBootFailureNotification
sonusGpuDeviceBootFailureNotification
Type: CRITICAL
Object ID 1.3.6.1.4.1.2879.2.10.1.1.4.0.64
Description This alarm indicates that the GPU card failed sanity test execution during system start-up (system boot). The alarm indicates a
GPU hardware issue.
The event message displays the faulted GPU device's serial number and Peripheral Component Interconnect (PCI) slot ID.
Repetition Each provisioned GPU device executes the GPU sanity test. Each GPU produces its own alarm if it fails the sanity test.
Event Codes None.
Instance sonusAlarmNodeID,
Fields sonusAlarmLevel,
sonusAlarmTime,
Action Replace the faulted GPU device.
Impact When this error occurs, the corresponding MRFP node goes out of service.
Clearing Manual.
New and Deprecated Alarms
In this section:
New Alarms
New alarms in the SBC 11.01.00R000 release
Deprecated Alarms
Obsoleted Alarms
New Alarms
The following alarms are added in the SBC 11.01.00R000 release:
Under License Alarms:

The following alarms are added in the SBC 11.00.00R000 release:
Under Policy Server Alarms:
Under Licensing Alarms for SBC SWe Deployments
sonusCpLicenseManagerUnsanctionedMannerSoon - CRITICAL
Under Node Resources Alarms:
Deprecated Alarms
The following alarms are deprecated in the SBC 11.00.00R000 release:
sonusCpLicenseManagerCallProcessingWillStopSoon
sonusSbxCallRejectsDueToSessionLicenseClearNotification - CRITICAL
sonusSbxCallRejectsDueToSessionLicenseClearNotification - MAJOR
Deprecated Alarms in 09.02.00R000 Release

sonusSbxSlbGlobalLossRatioThresholdReachedNotification
sonusSbxSlbGlobalLossRatioThresholdClearNotification

sonusSbxArsEndPointBlacklistedNotification
sonusSbxArsEndPointBlacklistedNotificationV6
sonusSbxArsEndPointRecoveredNotification
sonusSbxArsEndPointRecoveredNotificationV6
sonusSbxArsEndPointsRecoveredNotification
sonusSbxPathCheckPingStateUpNotification
sonusSbxPathCheckPingStateUpNotificationV6
sonusSbxPathCheckPingStateDownNotification
sonusSbxPathCheckPingStateDownNotificationV6
sonusSbxPathCheckRemoteAdminStateUpNotification
sonusSbxPathCheckRemoteAdminStateUpNotificationV6
sonusSbxPathCheckRemoteAdminStateDownNotification
sonusSbxPathCheckRemoteAdminStateDownNotificationV6
sonusSbxPathCheckLocalAdminStateUpNotification
sonusSbxPathCheckLocalAdminStateUpNotificationV6
sonusSbxPathCheckLocalAdminStateDownNotification
sonusSbxPathCheckLocalAdminStateDownNotificationV6
sonusSbxPathCheckFqdnPeerUpNotification
sonusSbxPathCheckFqdnPeerDownNotification
sonusSbxPathCheckFqdnPeerIpEndpointUpNotification
sonusSbxPathCheckFqdnPeerIpEndpointDownNotification
sonusSbxPathCheckFqdnPeerIpV6EndpointUpNotification
sonusSbxPathCheckFqdnPeerIpV6EndpointDownNotification

sonusCpNifRbrEmptyErrorRateClearedNotification
sonusCpNifRbrEmptyErrorRateExceededNotification
sonusCpNifRbrPrefetchEmptyErrorRateExceededNotification

sonusSbxLicensedMrfSessionsThresholdReachedNotification
sonusSbxLicensedSrtpSessionsThresholdReachedNotification
sonusSbxLicensedVideoSessionsThresholdReachedNotification
sonusSbxLicensedSipRecThresholdReachedNotification
sonusSbxLicensedNiceRecThresholdReachedNotification
Virtual Machine Alarms

sonusCpVmAppDownNotification
sonusCpVmAppUpNotification
sonusCpVmInvalidLicenseNotification
sonusCpVmMatchLicenseNotification
sonusCpVmSyncCompletedNotification
sonusCpVmSyncInprogressNotification
sonusCpVmUpgradeInitiatedNotification
sonusCpVmUpgradeRevertNotification
sonusCpVmUpgradeSucceededNotification
sonusCpVmUpgradeTerminatedNotification

sonusCpLicenseGraceExpired
sonusCpLicenseGraceExpiring
sonusCpLicenseAcquireFailed
sonusCpLicenseAcquireSucceeded
sonusCpLicenseGraceModeCleared
sonusCpLicenseReleased
sonusCpLicenseServerNameResolutionError
sonusCpLicenseServerReachable
sonusCpLicenseServerUnReachable
sonusCpLicenseGraceMode
sonusCpLicenseFingerprintMismatch

sonusSbxDsbcNodeAllocationFailure
sonusSbxDsbcNodeAllocationFailureClear
sonusSbxDsbcNodeAllocationFailureV6
sonusSbxDsbcNodeAllocationFailureClearV6
sonusSbxLicensedOodRateLimitClearNotification
sonusSbxLicensedOodRateLimitReachedNotification

sonusCpNifWredDroppedPacketsRateExceededNotification
sonusCpNifWredDroppedPacketsRateClearedNotification
sonusCpNifMailBoxNotification
sonusCpNifNackPacketReadErrorNotification
sonusCpNifNackPrefetchErrorNotification
sonusCpNifPacketSizeErrorNotification
sonusCpNifPacketPointerErrorNotification
sonusCpNifParityErrorNotification
sonusCpNifPartitionErrorNotification
sonusCpNifByteEnableBusErrorNotification
sonusCpNifPageViolationErrorNotification
sonusCpNifDataControlFifoErrorNotification
sonusCpNifRcrShadowParityErrorNotification
sonusCpNifPrefetchParityErrorNotification
sonusCpNifRbrFullErrorNotification
sonusCpNifRbrLogicalPageErrorNotification
sonusCpNifRbrTimeoutNotification
sonusCpNifRcrAckErrorNotification
sonusCpNifRcrInconsistencyErrorNotification
sonusCpNifRcrRingFullErrorNotification
sonusCpNifResponseCountErrorNotification

sonusCpSystemLocalDiskAvailableNotification
sonusCpSystemLocalDiskUnavailableNotification
sonusCpSystemLocalDiskSyncStartNotification
sonusCpSystemLocalDiskSyncCompleteNotification
sonusCpSystemAllHardDisksFailedNotification
sonusCpSystemLocalRaidArrayDegradedNotification
sonusSbxLicensedEncryptSessionsThresholdReachedNotification

sonusSWeNewTrafficProfileCommitNotfication
sonusSbxServiceDeniedDueToUnavailableLicenseNotification

sonusCpLicenseFailsafeGraceMode
sonusCpLicenseFailsafeGraceModeCleared
sonusCpLicenseFailsafeGraceExpiring
sonusCpLicenseFailsafeGraceExpired

sonusCpLicenseRefreshFailure
sonusCpLicenseServerError
sonusCpLicenseServerErrorCleared
sonusSbxCallRejectsDueToNotAbleToAcquireAdvancedERELicense
sonusSbxAcquiredAdvancedERELicenseNotification

sonusSbxNrsIpInterfaceAdminDeletedNotification
sonusSbxNrsMgmtPortIpInterfaceDeletedNotification
sonusCpSystemServerDrbdReformatCompletedNotification
sonusCpSystemServerDrbdReformatStartNotification
sonusCpSystemServerDrbdReformatSwitchoverNotification
sonusCpSystemServerDrbdReformatErrorNotification
sonusCpSystemServerDrbdReformatBackupNotification
sonusEmergencyMessageRejectedNotification

sonusCpSoftwareUpgradeCommitRequiredNotification
sonusCpSystemServiceRestartedNotification
sonusSbxSelCdrConfUpdateNotification
sonusSbxSelCdrConfigReqRspTimeoutNotification
sonusH248ScDisconnectedTxNotification
sonusH248ScHandoffTxNotification
sonusH248ScFailoverTxStatusNotification
sonusH248ScFailoverTxNotification
sonusH248ScHandoffRxNotification
sonusH248ScRestartRxNotification
sonusH248ScVerNotSupportedNotification
sonusH248ScVerNegotiatedNotification
sonusH248FeatureLicenseExpiryNotification
sonusH248FeatureLicenseLimitNotification
sonusH248FeatureDisabledNotification
sonusH248FeatureEnableNotification
sonusH248SigPortOpenNotification
sonusH248SigPortCloseNotification

sonusCpSystemCEDisabledNotification
sonusCpSystemCEEnabledNotification

sonusSbxDiamConnectionToRfAccountingServerGoesDown
sonusSbxDiamConnectionToRfAccountingServerGoesUp

sonusCpSoftwareUpgradeCommitRequiredNotification

There is no deprecated alarm for this release.

sonusCpSystemCEDisabledNotification
sonusCpSystemCEEnabledNotification

Obsoleted Alarms
Obsoleted Alarms in 07.00.00R000 Release
sonusCpSystemLocalDiskSyncStartNotification
sonusCpSystemLocalDiskSyncCompleteNotification
sonusCpSystemAllHardDisksFailedNotification
sonusCpSystemLocalRaidArrayDegradedNotification
SBC Core Troubleshooting Guide
Table of Contents
Basic Debugging
Debugging OOS Reasons for GR-HA Port Connections with ARP-Based Monitoring
Debugging SBC SWe in Public Cloud
Debug General SBC SWe Public Cloud
Debug SBC SWe in AWS
Debug SBC SWe in Azure
Debug SBC SWe in GCP
Recovering SSH Key Access in Public Cloud and Updating User Data
Debugging SBC SWe Virtual and in Private Cloud

Cloud Diagnostic Tool User Guide
For Troubleshooting Only - How to Enable ssh Access

SBC Troubleshooting Tools
Troubleshooting SBC Using Debug Event Logs
Using SBC Packet Collector for Core Dump Analysis
Using Test Calls and IP Trunk Group Blocking
Using the SSReq Tool
Using SSReq
SSReq User Interface
Status Display
Viewing a Response
Response Field Descriptions
SSReq Troubleshooting
Basic Debugging
In this section:
Viewing Logs
EMA GUI
Call Trace and Wireshark Traces
Cloud SBC Log Header
D-SBC Debugging
Call-Related Trace Logging
Downloading Existing CLI Configuration from GUI
Viewing Logs
After you implement your configuration, you will want to test it out. The SBC Core provides tools that allow you to monitor SIP messaging, look at
logs, look at statistics, and billing records.
Logs may be viewed from either user interface:
EMA GUI
From the EMA GUI:
1. Navigate to the Administration tab

2. View logs and set up a Call Trace to view SIP messages
Call Trace and Wireshark Traces

The Call Trace function allows you to get the SIP message trace and RTP packets for a very specific call. This is helpful when you are testing a
particular call scenario. You can trace on called number, calling number, trunk group, IP Peer.
The SIP messaging (and SBC-specific logs related to the call) are stored in a text file ending in ".TRC".
In addition to the .TRC file, the SIP signaling and RTP traffic can also be captured in a ".PKT" file. To view the ".PKT" file, you download it to your
PC, and then open it with Wireshark interface (referred to as "TShark" in EMA Troubleshooting tab). You can see what trace filters are set up
using "show configuration global callTrace" command.
Below is an example usage for call trace "toBLUECARRIER" that traces all calls to and from trunk group BLUECARRIER:
admin@SBC01a> show configuration global callTrace callFilter toBLUECARRIER {

state enabled;
level level1;
key trunkGroup;
match {
trunkGroup BLUECARRIER;
}
mediaPacketCapture enable;
}
Since a large amount of data is captured for each call, it is advisable to:
Only capture media if you need it

Disable your call trace filter after making your test call
See Troubleshooting Tools - TShark for additional details of using TShark from the EMA.
Cloud SBC Log Header

In Cloud instances of the SBC, the Virtual Network Function Component ID (VNFC-ID) uniquely identifies an instance in an OpenStack setup.
The VNFC-ID is added to the SBC log headers, which helps to identify the instance from where the logs are retrieved. The VNFC-ID is added to
the system, debug, trace, security, audit, and memory logs so that these log files associate to a specific instance.
The VNFC-ID is in a separate line below the existing SBC log header. The following is an example of an SBC log header without the SBC cloud
instance:
Ribbon Communications00000000FF600000570000000000000128V06.02.01A002
0000000000000000000000000000ACT2018010802013300000000000000
The following is an example of an SBC log header with the SBC cloud instance:
Ribbon Communications00000000FF600000570000000000000128V06.02.01A002
0000000000000000000000000000ACT2018010802013300000000000000
Cloud Instance, release.we.621x-isbc-a-1
D-SBC Debugging
Call-Related Trace Logging
Calls in the Distributed SBC (D-SBC) have call segments that reside in various elements, such as Signaling SBC (S-SBC), Media SBC (M-SBC),
and Transcoding SBC (T-SBC). This feature simplifies the debug process of correlating trace lines from separate log files that span multiple
SBCs.
The Virtual Network Function Component ID (VNFC-ID) and Global Call ID (GCID) pair are added to a header in the SBC DBG and TRC log files
to facilitate trace line correlation. VNFC-ID is the networkwide unique identifier for a node and GCID is the nodewide unique identifier for a call.
The VNFC-ID and GCID pair in an SBC form a unique identifier for a call in the network. In the DBG and TRC log files, call-related trace lines for
the Node Resource Manager Agent (NRMA) and the Distributed FE (DFE) are tagged with the VNFC-ID and GCID pair in the D-SBC log header.
The D-SBC log header in S-SBC contains the local VNFC-ID and GCID pair.
Note
This is applicable only for OpenStack Cloud platform and does not support other platforms like KVM, VMWare, and so on.
The following are some of the examples:
If required, this pair is the tagging key for the same call in the M-SBC and T-SBC.
DBG: ... Info .NRMA: [SSBC:VNFCID-ABC,0x8] NrmaContinueAllocResCmd: gcid=0x1 legGcid…

TRC: ... Info .NRMA:CALL:FILTER=trunkgroup [SSBC:VNFCID-ABC,0x4] Allocate Rpy: gcid=0x4 legGcid=0x4 legId=1 noAudio=0 rt…
The D-SBC log header in M-SBC and T-SBC contains the remote S-SBC VNFC-ID and GCID pair and the local M-SBC VNFC-ID and GCID pair.
See the following examples:
The trace line is tagged to the S-SBC VNFC-ID and GCID pair of the call.
DBG: ... Info .NRMA: [SSBC:VNFCID-ABC,0x8] [MSBC:VNFCID-XYZ,0x1] NrmaSendGroupResActivation: Ac…

TRC: ... Info .NRMA:CALL:FILTER=trunkgroup [SSBC:VNFCID-ABC,0x4] [MSBC:VNFCID-XYZ,0x1]
NrmaProcessAllocResCmdRemoteEpRes: gcid=0x4 sGcid=0x4...
The I-SBC will not include the D-SBC log header.
Downloading Existing CLI Configuration from GUI

To save a text file containing the CLI commands used to configure your system, refer to System Administration - Configuration Template Import
(EMA).
Debugging OOS Reasons for GR-HA Port Connections with
ARP-Based Monitoring
This topic describes how to interpret the SBC Core highAvailabilityPort status for GR-HA port connections supporting ARP-based monitoring, in
case additional actions are required.
The following highAvailabilityPort OOS reasons are described in this section:
A status of "noSignal" if there is an outage between the CE and its local switch
A status of "noRemoteSignal" if the outage is beyond the local switch.
Activated Network Connect Mode

admin@EMERALD> show table system haConfig
SERVER LEADER
NAME ELECTION BOND MONITORING
------------------------------------
GARNET enhanced network-connect
EMERALD enhanced network-connect
Scenarios
Loss of connection between the server HA port and the local switch
The OOS Reason is "noSignal"

The other end of the same port shows the OOS Reason as "noRemoteResponse"
Examples:
Disconnected HA port eth0 from Active SBC (EMERALD)
admin@EMERALD> show table system highAvailabilityPort status

NEGOTIATED
CE NAME PORT NAME MAC ADDRESS IP ADDRESS SPEED OOS REASON
-----------------------------------------------------------------------------------------
GARNET haPort1 00:10:6b:03:da:a3 169.254.88.3 speed10Gbps noRemoteResponse
GARNET haPort2 00:10:6b:03:da:a3 169.254.88.4 speed10Gbps na
GARNET bondingDevice0 00:10:6b:03:da:a3 169.254.88.1 unknown na
EMERALD haPort1 00:10:6b:03:db:39 169.254.99.3 unknown noSignal
EMERALD haPort2 00:10:6b:03:db:39 169.254.99.4 speed10Gbps na
EMERALD bondingDevice0 00:10:6b:03:db:39 169.254.99.1 unknown na
Disconnected HA port eth0 connection from switch which is near to standby SBC (GARNET)
admin@EMERALD> show table system highAvailabilityPort status

NEGOTIATED
-----------------------------------------------------------------------------------------
GARNET haPort1 00:10:6b:03:da:a3 169.254.88.3 unknown noSignal
EMERALD haPort1 00:10:6b:03:db:39 169.254.99.3 speed10Gbps noRemoteResponse
A disconnection between switches

The OOS Reason is "noRemoteResponse"
Example:
admin@GARNET> show table system highAvailabilityPort status
NEGOTIATED
-----------------------------------------------------------------------------------------
Both issues are faced

Physical disconnection to server HA port and in between switches, Initially it shows one server with "noSignal" and other with
"noRemoteResponse" as OOS Reason. Once physical disconnection rectified, OOS Reason shows both port as
"noRemoteResponse".
Examples:
Disconnected eth0 from far end switch

NEGOTIATED
-----------------------------------------------------------------------------------------
[ok][2022-02-11 11:54:43]
Disconnected HA port eth0 from active (GARNET) SBC

NEGOTIATED
-----------------------------------------------------------------------------------------
GARNET haPort1 00:10:6b:03:da:a3 169.254.88.3 unknown noSignal
[ok][2022-02-11 11:57:01]
Connected HA port eth0 of active (GARNET) ha port

NEGOTIATED
-----------------------------------------------------------------------------------------
[ok][2022-02-11 11:59:34]
Connected back eth0 far end switch

NEGOTIATED OOS
CE NAME PORT NAME MAC ADDRESS IP ADDRESS SPEED REASON
-------------------------------------------------------------------------------
[ok][2022-02-11 12:01:01]
Debugging SBC SWe in Public Cloud
In this section:

Recovering SSH Key Access in Public Cloud and Updating User Data
This section describes some common issues found with SBC SWe in Public Cloud environments, and the action needed to verify or troubleshoot
the issues.
The SBC Application did not come up on both the active and standby nodes after
reverting to a pre-11.0 release.
Use the following procedure to recover the SBC SWe HA on public cloud after reverting to a pre-11.0 release if the SBC application does not
come up on both the active and standby nodes.
Note
This procedure is only applicable if the system is upgraded from a pre-11.0 release to this release using the following method:
Bring up the SBC HA application with a pre-11.0 release on public cloud (For example, AWS).
Upgrade both the active and standby SBC to this release using the recommended upgrade method.
Step Action
1
1. Revert the SBC application to pre-11.0 release.
2. Once complete, check to see if application is coming up fine on both active and standby nodes.
3. If the SBC application is stuck and unable to receive the assigned role, stop the SBC application on both active and standby
nodes using the
command sbxstop.
2 If present, remove the following file/directories from both the active and standby SBC:
rm -rf /home/cnxipmadmin/peerDynamicHANewComps
rm -rf /opt/sonus/sbx/openclovis/var
3
1. Start the SBC application on both the active and standby nodes using the ‘sbxstart’ command.
2. Check to make sure that the application starts up on both nodes.
Note
If you are using the RAF for upgrade/revert, perform the steps 1.3 to 3.1 within 30 minutes after running the revert operation.
This ensures that the RAF can detect the correct state of VNF and mark the operation as complete.
The sbcDiagnostic tool specifies "cloud-init.service failed with the result 'exit-code'", and
my SBC application is not coming up
Ribbon's cloudinit modules use information retrieved from the Public Cloud provider. Occasionally, the provider fails to return, or only partially
returns, the information. When this occurs, the modules cannot obtain all of the information needed by the SBC.
Step Action
1 Reboot the instance through the cloud provider.
2 Follow other Debugging information if the problem persists:

3 Contact Ribbon Global Support if the issue persists.
Topics:
Multiple HFE setups are reusing pkt0 subnet

Error message in AWSSwitcover.log
SBC/HFE doesn't work in ABC region
SBC/HFE doesn't come up when I use templates that worked in a previous release (AMI)
Public IP (EIP) on UAC and/or UAS making calls to public port of SBC
Some packets are not going through HFE, and the rest of the packets follow HFE for public calls
The HFE fails to route traffic to the SBC
The instance fails to come up with no SSH access
I have AWS infrastructure questions
What do I do if I experience issues related to downloading and executing the HFE.sh
The SBC is not able to contact AWS service(s)
The IP addresses assigned to the interface names are incorrect on the HFE and calls are not working
This section covers some common issues found in the SBC SWe in AWS setup, and the actions necessary for verification and troubleshooting.
Multiple HFE setups are reusing pkt0 subnet

Important
Please make note of this commonly-experienced issue.
Each HFE+SBC triplet must use a different pkt0 subnet. If you used the same subnet for multiple HFE+SBC triplets, then all SBCs will send
packets to the HFE that was created last. This limitation is due to AWS networking architecture.
Action:
1. There is no recovery path from here!

a. Delete all HFE+ SBC triplets except the one created last.
2. You can redirect all non-AWS (Internet-bound) traffic to some instance/port by modifying AWS subnet routing table. This routing table
modification effects entire subnet(not port).
Warning
Do not re-use the pkt0 subnet to create multiple SBC and HFE instances, create /3, or similar, small subnets for each SBC HFE triplet
you need.
Error message in AWSSwitcover.log

Common problems are either the SecurityGroups config. doesn't allow outgoing traffic to the AWS API GW, or the EIP is not attached in eth0
(mgt) on the SBC and HFE.
Action:
1. Make sure that AWS API GW is accessible from default routes.

2. Occassionally, the SBC fails to join an HA pair because it populates incorrect UserData metaVariabel table in confd.
a. In order to create an HA pair, ensure the secondary IPs are assigned on pkt0 and pkt1 ports of either the assigned active or
standby.
b. If an instance fails to see the IPs attached on either of these two instances, the SBC fails to join cluster.
i. Check the LCA and cloud-init logs:
/var/log/cloud-init.log
/var/log/sonus/lca/lca.log
3.
3. If SIPs on pkt0 and pkt1 are assigned, or the port assignment occurs after the instance is created, LCA may show SIPs logs missing on
both the active and standby.
a. Make sure all of the required resources are created by the script/tools provided by Ribbon.
(Any local modification may result into a race condition which prevents the SBC from booting up)
SBC/HFE doesn't work in ABC region

Most of the problems reported are due to incorrectly configuring the IAM policy/role, or assiging incorrect name/permission of the S3 bucket for
storing the HFE.sh script.
Action:
1. Check the IAM role and policy are correct for your release.
2. Make sure that the S3 bucket name given in HFE user data is correct, and that the IAM role attached with an HFE instance can
download a script from the S3 bucket.
Note
HFE and SBC IAM roles/permissions are not identical.
SBC/HFE doesn't come up when I use templates that worked in a previous release (AMI)
Old HFE.sh scripts and templates may not work as expected with a new build. You must treat AMI, templates and HFE.sh scripts as one logical
release (build), and use them together.
Action:
1. Make sure you use the correct templates and HFE.sh script release versions with each new release (these templates and scripts are
bundled in a build's orca/rel directory).
Public IP (EIP) on UAC and/or UAS making calls to public port of SBC
Action:
1. Make sure that the signaling and all media ports that are negotiated are public IPs.
2. If any private IPs exist in the signaling configuration, you must correct this because it will not work with HFE.
Some packets are not going through HFE, and the rest of the packets follow HFE for
public calls
This is due to an incorrect configuration on the SBC. Outgoing packets are either using private IPs, or are not sent out via pkt0.
The HFE can drop packets only if
a user restarts networking on it manually, or changes the default route on it, or if

the HFE routes are modified.
Action:
1. Verify the SBC configuration is correct.

2. Do not debug the HFE node that is dropping selective packets as the first debug step. The HFE does not process the information -
whatever it receives from the SBC (on eth2) goes out via eth0.
3. Don't modify the default route. The default route serves all peers without copying peer configuration from the SBC to the HFE.
An HFE networking service restart will cause a change in the default route on the HFE. Thus, the HFE will stop forwarding
packets to public UAC/end-points. DO NOT restart the networking service on the HFE. If you want to do a network restart, re-
run the HFE.sh script with a "setup" command line argument.
The HFE fails to route traffic to the SBC

Possible causes:
Incorrect HFE.sh script
Incorrect version used
New AWS Linux shows 'ip route' in a different format
Check the output of the commands run by HFE.sh on HFE instance
Ribbon doesn't maintain the HFE AMI (only the configuration script for HFE). The latest AWS Linux AMI ID is selected while launching
HFE from the AWS template. Any change in 'ip addr' or 'ip route' commands may require changes in the HFE.sh script to configure
HFE properly.
The instance fails to come up with no SSH access

Action:
1. Try to ssh on the HA port. If this also fails, continue to the next step.
2. Detach the root disk of the instance and attach it to any other Linux instance (which has lvm2 tools installed) in AWS EC2.
NOTE: The following commands assume that the disk is attached as xvdf in Linux machine. Disk can be detached/attached only when
an instance is in stopped state.
a. Attach the volume (disk).
a. Once the disk is attached, mount the disk using the commands:
vgchange –ay
mount /dev/debian/root /mnt
# The root of SWe instance is available at /mnt
The following SBC SWe logs are available:
OpenClovis logs: /mnt/var/log/sonus/sbx/openclovis

Tailf logs: /mnt/var/log/sonus/sbx/tailf
SYS/DBG logs: /mnt/var/log/sonus/evlog
Core dump: /mnt/var/log/sonus/sbx/coredump
Utility scripts: /mnt/opt/sonus/sbx/scripts
b. Unmount the disk from the GUI using the following commands:
umount /mnt/var/log/sonus/
umount /mnt
vgchange –an
c. Detach the volume (disk).
I have AWS infrastructure questions

Question Answer
1. Can we host EIP on any of AWS service 1. No, there is no such AWS service as of now.
instead of HFE? 2. No, it is designed to give internet access to private instances, we can't initiate calls
2. How about AWS NAT service? from public UAC using this service
A competitor showed us the use of sub-second Most probably it is service continuity (using DNS), and all new requests are going to
switchover. Is this possible? some other SBC.
Check what happened to the existing calls during their fail-over demo.
Can we have HA across multiple AZs? No. For call continuity we rely on IP address movement, AWS doesn't allow us to move
IPs across AZs. This is infrastructure limitation.
Can we use AWS MAC spoofing? No. AWS drops all such packets silently.
Can we use GARP ? No use of sending GARP, AWS doesn't give access to virtual L2 switch. All the provided
networking is L3
What do I need to know about Security Groups? Do not block outgoing traffic because AWS API communication is required by the SBC
HA and HFE.
Caution
Do not open your Security Groups too wide to allow all traffic from
Internet.
Always use PEM-based authentication (ssh/login).
Can I change MetaData ? We can't change MetaData, only UserData can be modified
What is the purpose of the HFE IPs
The HFE Primary IP handles primary IP traffic, and is also used to:
upgrade and configure the SBC, and

download the HFE.sh script
The HFE Secondary IP handles all SIP EIPs to support call flows.
Note
All secondary IP traffic is directed to the SBC.
What do I do if I experience issues related to downloading and executing the HFE.sh

Action:
1. First, enter the below command in HFE to check if the HFE.sh script is downloaded from S3.
aws s3 cp s3://aws-quickstart/quickstart-ribbon-sbc/scripts/HFE.sh ${HFE_FILE}
If the script is downloaded, but HFE.sh is failing to run, go to the next step.
2. Verify the path is correct in HFE logs.
[root@ip-172-31-10-30 log]# bash /var/lib/cloud/instances/i-0d4ab8238b5935f85/user-data.txt

download: s3://aws-quickstart/quickstart-ribbon-sbc/scripts/HFE.sh to ../../home/ec2-user/HFE/HFE.sh
2019-08-29 09:32:11 Copied HFE script from S3 bucket.
REMOTE_SSH_MACHINE_IP=
/var/lib/cloud/instances/i-0d4ab8238b5935f85/user-data.txt: line 18: !timestamp: command not found
[root@ip-172-31-10-30 log]# bash /var/lib/cloud/instances/i-0d4ab8238b5935f85/user-data.txt

download: s3://aws-quickstart/quickstart-ribbon-sbc/scripts/HFE.sh to ../../home/ec2-user/HFE/HFE.sh
2019-08-29 09:33:20 Copied HFE script from S3 bucket.
REMOTE_SSH_MACHINE_IP=
[root@ip-172-31-10-30 log]# ls /var/lib/cloud/instances/
i-0d4ab8238b5935f85
[root@ip-172-31-10-30 log]#
The SBC is not able to contact AWS service(s)

The SBC contacts AWS service(s) in the following cases:
Get peer's data – This is done for cloud-init and LCA

Switchover in HA setup
Getting HFE's data in HFE-based HA setup
The HFE collects SBC's data
SBC services use AWS API(s) to send data to cloud-watch, e.g. interval-stats, trc-anonymization, cloud-watch-service, SNMP logs, act-
anonymization etc.
Metering API service used by post-paid metering SBC product in order to bill customers for actual usage of calls
Action:
If the SBC fails to contact AWS API(s), check the following:
1. Check DNS resolution – You must have AWS provide a DNS configured in VPC, and this must be the first one configured in the SBC.
a. If you have a custom DNS configured in the SBC, you must ensure your DNS has the latest IPs of all AWS services.
b. If your DNS returns the wrong IP, all API communications will fail. Check tshark output to debug it further.
Example:
tshark -i mgt0 | grep -i dns
Capturing on 'mgt0'
129 98 6.584463 172.31.10.137 -> 172.31.10.54 DNS 87 Standard query 0xe264 A ec2.us-
east-1.amazonaws.com
99 6.584471 172.31.10.137 -> 172.31.10.54 DNS 87 Standard query 0x829b AAAA ec2.us-east-
1.amazonaws.com
100 6.588009 172.31.10.54 -> 172.31.10.137 DNS 165 Standard query response 0xe264 A
13.249.37.5 A 99.86.226.181
101 6.588020 172.31.10.54 -> 172.31.10.137 DNS 144 Standard query response 0x829b
In this example, the SBC is not using the AWS-provided DNS. Someone configured the SBC to use the DNS on
172.31.10.54, and this DNS returns the wrong IP for AWS services (A 13.249.37.5 A 99.86.226.181)
The AWS-provided DNS is x.x.x.2, e.g. 172.31.0.2.
c. Solution: Either remove the DNS configured on the SBC, or obtain the correct set of IPs configured on your DNS - 172.31.10.54.
2. IAM role – Make sure IAM role attached to the SBC has the correct set of permissions for the services you are debugging.
3. Security Group Rules – Make sure your SG rules don't block any outgoing traffic. It should be 0.0.0.0/0 to allow all traffic.
4. ACLs in AWS – Make sure AWS ACLs don't block any traffic.
5. ACLs in SBC – Check if ACLs on the SBC are blocking traffic going towards the IP returned by the DNS. If there is no DNS reply, check
that ACLs are opened for port 53 (UDP and TCP).
6. AWS subnet routing table
a. Make sure the interface which is picked up by the SBC to send API traffic is in a subnet which can send traffic to the AWS API
server (check the SBC routes for the IP returned by the DNS)
b. Check AWS subnet and routing table entries.
7. EIP on SBC
a. Check which interface is used for sending out traffic to AWS API server (check DNS IP and the SBC route table). This interface
should use EIP or NATGW.
b. Altenatively, configure a VPC-end-point in your setup.
NOTE: A VPC-end-point doesn't provide all services – if you require a metering service, you must configure either NATGW or
EIP.
If you are using a VPC-end-point, make sure its IP is routed via mgt0 in the SBC.
VPC-end-points will work only if its IP is in mgt0 subnet or any subnet other than HA0, pkt0 and pkt1 (e.g. 10.54.10.x, 10.54.80.x).
The following configuration will not work:
SBC:
1. mgt0 - 10.54.10.x
2. HA0 - 10.54.20.x
3. pkt0 - 10.54.30.x
4. pkt1 - 10.54.40.x
VPC-end-point IP - 10.54.30.10
The DNS will return IP 10.54.30.10 for AWS services, and the SBC's attempt to send out traffic via pkt0 will fail.
The IP addresses assigned to the interface names are incorrect on the HFE and calls are
not working
Perform the following procedure if the calls are not forwarded to the SBC through the HFE, and running the ip addr command indicates that the
IP addresses are assigned to an interface name.
1. Run the ip addr command to identify the interface names that are swapped.
2. Note the link/Ether address associated with the IP address. The following example represents Eth1 and Eth2 are swapped:
[ec2-user@ip-10-1-5-214 ~]$ ip addr

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9001 qdisc mq state UP group default qlen 1000
link/ether 02:a4:b2:be:17:22 brd ff:ff:ff:ff:ff:ff
inet 10.1.5.214/24 brd 10.1.5.255 scope global dynamic eth0
valid_lft 3540sec preferred_lft 3540sec
inet 10.1.5.58/24 brd 10.1.5.255 scope global secondary eth0
inet6 fe80::a4:b2ff:febe:1722/64 scope link
link/ether 02:e2:8b:5e:96:1c brd ff:ff:ff:ff:ff:ff
inet6 fe80::e2:8bff:fe5e:961c/64 scope link
link/ether 02:31:53:a2:88:d6 brd ff:ff:ff:ff:ff:ff
inet6 fe80::31:53ff:fea2:88d6/64 scope link
3. Run the following command to update the associated ifcfg file with the correct Ether address for each incorrect interface:
sudo sed -i 's/^HWADDR=.*/HWADDR=<ether address>/' /etc/sysconfig/network-scripts/ifcfg-eth<interface

number>
Example:
sudo sed -i 's/^HWADDR=.*/HWADDR=02:31:53:a2:88:d6/' /etc/sysconfig/network-scripts/ifcfg-eth1

sudo sed -i 's/^HWADDR=.*/HWADDR=02:e2:8b:5e:96:1c/' /etc/sysconfig/network-scripts/ifcfg-eth2
4. Remove the persistent udev rules: sudo rm -f /etc/udev/rules.d/70-persistent-net.rules

5. Reboot the instance: sudo reboot
6. Run the ip addr command to verify the interfaces are correct.
[ec2-user@ip-10-1-5-214 ~]$ ip addr

link/ether 02:a4:b2:be:17:22 brd ff:ff:ff:ff:ff:ff
inet 10.1.5.58/24 brd 10.1.5.255 scope global secondary eth0
inet6 fe80::a4:b2ff:febe:1722/64 scope link
link/ether 02:31:53:a2:88:d6 brd ff:ff:ff:ff:ff:ff
inet6 fe80::31:53ff:fea2:88d6/64 scope link
link/ether 02:e2:8b:5e:96:1c brd ff:ff:ff:ff:ff:ff
inet6 fe80::e2:8bff:fe5e:961c/64 scope link
In this section:
Every time I start the SBC instance, it stops after a few minutes
The HFE.log continually gets the error message "Connection error ongoing - No connection to SBC PKT ports from HFE"
Calls are failing to reach the SBC from the HFE node
I am unable to log on to my HFE node via the mgmt interface
Instance does not get Accelerated NICs
I am unable to update apt or install using apt on the HFE
My HFE script fails with 'Failed to Set Route'
My HFE script fails with 'Authorization still failing after 15 minutes'
This section covers common issues found in the SBC SWe in Azure setup, and the actions necessary for verification and/or troubleshooting.
Every time I start the SBC instance, it stops after a few minutes
This results from submitting invalid user-data being. Submit only valid JSON to the SBC. For more information on valid JSON, refer to SBC
Userdata topic.
Action Steps:
To verify whether the problem occurs due to invalid JSON, perform the following steps:
1. In the portal, go to Virtual machines.

2. Select instance.
3. Go to Support + troubleshooting > Serial Console.
4. Start the instance.
5. Search the log for the following message:
Invalid JSON format in UserData - Shutting Down
The HFE.log continually gets the error message "Connection error ongoing - No
connection to SBC PKT ports from HFE"
If the message "Connection error ongoing - No connection to SBC PKT ports from HFE" is continually written to HFE.log, it indicates that the HFE
node cannot connect to the SBCs.
Action Steps:
Perform the following verification steps:
1. Using the CLI, verify the PKT0 and PKT1 is configured correctly. For more information on this process, refer to Configuring PKT Ports topic
.
2. Verify the IPs listed in the HFE_conf.log are the ones attached to the SBC:
a. Go to /opt/HFE/log/.
b. Find the logs that specify the IPs for the SBC ; the logs are in the form:
<SBC instance name> - IP for <pkt0 | pkt1> is <IP>
c. Find the Alias IPs for the SBC:
i. Go to Virtual machines.
ii. Click on the SBC instance.
iii. Go to Settings > Networking.
iv. Go to the PKT0 interface.
v. Click on the network interface.
vi. Go to Settings > IP configurations.
vii. Verify the secondary IP matches.
viii.
viii. Repeat for the PKT1 interface.
3. Check the Security groups are correct:
a. Go to Network security groups.

b. Select the security group.
c. Go to Inbound security rules.
d. Verify the end point IPs are allowed.
4. Check the routes are correct:
a. Go to Route tables.
b. Select the route table.
c. Click on Routes and verify the routes point to the eth2 IP on the HFE node.
d. Click on Subnets and verify the the route table is associated with both subnets
Calls are failing to reach the SBC from the HFE node
Action Steps:
1. Verify there are no error logs in the HFE.log.
2. Verify the end point of the traffic is allowed access through the VPC firewalls. For more information, refer to Create Network Security
Group topic
I am unable to log on to my HFE node via the mgmt interface

This indicates that either there is a configuration issue, or the firewall rules are not been updated correctly.
Action Steps:
1. Verify the IP you are trying to SSH from is allowed through the network security group. For more information, refer to Create Network
Security Group topic
2. .
3. Verify that the IP you are trying to SSH from is present correctly in the HFE node user-data. Update the appropriate line containing
"REMOTE_SSH_MACHINE_IP":
/bin/echo "REMOTE_SSH_MACHINE_IP=\"10.27.178.4\"" >> $NAT_VAR
For more information, refer to Custom Data Example topic.

4. The HFE script may fail before creating the routes. In such cases:
a. Attempt to SSH in to the NIC0 on the HFE node.
b. Check the logs for errors in this directory /opt/HFE/log/. For more information, refer to HFE Node Logging topic.
Instance does not get Accelerated NICs

Even without the accelerated NICs, sometimes the SWe instance starts but does not guarantee performance.
Actions Steps:
1. Execute the following command to confirm the availability of the Mellanox NICs.
> lspci | grep Mellanox
The sample output given below indicates presence of Mellanox NICs.
83df:00:02.0 Ethernet controller: Mellanox Technologies MT27710 Family [ConnectX-4 Lx Virtual Function]
(rev 80)
9332:00:02.0 Ethernet controller: Mellanox Technologies MT27710 Family [ConnectX-4 Lx Virtual Function]
(rev 80)
2. In such situations, de-allocate the instance and start again.

If commands such as sudo apt update causes an error such as "connection timed out", you must add a manual route on the HFE node.
Caution
The following action steps will interrupt calls
Actions Steps:
1. Get the management interface gateway IP:

a. Open /opt/HFE/log/HFE_conf.log.
b. Search the log for the line which specifies the eth1.
Example for HFE 2.1: 2020-11-02 11:45:47 ETH1_GW 10.2.0.1
2. Add the route to make traffic go through management interface:
sudo ip route add 0.0.0.0/0 via <Gateway IP> dev <management interface name> metric 10
Example:
ip route add 0.0.0.0/0 via 10.2.0.1 dev eth1 metric 10
3. Run the apt command:
sudo apt update
4. Remove the route you just added:
sudo ip route delete 0.0.0.0/0 via <Gateway IP> dev <management interface name> metric 10
Example:
ip route delete 0.0.0.0/0 via 10.2.0.1 dev eth1 metric 10
My HFE script fails with 'Failed to Set Route'

This issue is generally caused by Linux failing to configure the network interfaces before the HFE_AZ.sh script is run.
Action Steps:
1. Verify if any of the network interfaces (eth0, eth1, eth2) have a state of 'DOWN', using 'ip addr'.
An example of a good instance is:
rbbn@SBC-Terraform:~$ ip a
link/ether 00:0d:3a:11:e1:ac brd ff:ff:ff:ff:ff:ff
inet 10.2.1.4/24 brd 10.2.1.255 scope global eth0
inet6 fe80::20d:3aff:fe11:e1ac/64 scope link
link/ether 00:0d:3a:11:eb:7c brd ff:ff:ff:ff:ff:ff
inet6 fe80::20d:3aff:fe11:eb7c/64 scope link
link/ether 00:0d:3a:11:e2:5c brd ff:ff:ff:ff:ff:ff
inet6 fe80::20d:3aff:fe11:e25c/64 scope link
5: enP1s1: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master eth0 state UP group default
qlen 1000
link/ether 00:0d:3a:11:e1:ac brd ff:ff:ff:ff:ff:ff
6: enP3s3: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master eth2 state UP group default
qlen 1000
link/ether 00:0d:3a:11:e2:5c brd ff:ff:ff:ff:ff:ff
rbbn@SBC-Terraform:~$
2. If any of the states for eth0, eth1 or eth2 are DOWN, then follow these steps to fix:
a. Reboot the instance and re-verify (will generally fix the issue).
b. If issue is not fixed, then perform either of the following steps:
i. Destroy and re-orchestrate the whole HFE setup.
ii. Use Azure's Redeploy option to redeploy the VM:
1. In the Azure portal, go to the VM.
2. In the panel, scroll down and select Redeploy + reapply (under Support + TroubleShooting)
3. Select the Redeploy button.
My HFE script fails with 'Authorization still failing after 15 minutes'

This issue is caused by either the User Assigned Managed Identity does not have the correct roles, or by Linux not configuring the network
interfaces properly on the HFE.
1. Verify the Identity is attached to the VM:

a. Go to Virtual machines.
b. Click on the HFE instance.
c. Go to Settings > Identity.
d. Select User assigned.
e. Verify the Identity is listed.
2. Verify the role attached to the identity is correct (requires Azure CLI):
a. Get the principalId for the Identity:
a.
az identity show --name <identityName> --resource-group <resourceGroupName> --subscription

<subscriptionId>
b. Get the roleDefinitionName:
az role assignment list --assignee <principalId> --subscription <subscriptionId>
c. Get the role definition, and verify action contains the correct permissions (refer to Create Role topic):
az role definition list --name <roleDefinitionName> --subscription <subscriptionId>
3. If the previous steps are correct, follow instructions in the topic My HFE script fails with 'Failed to Set Route'
In this section:
When I try to SSH in to the SBC as linuxadmin, I receive "Permission denied (publickey)"
The HFE.log is continually getting the error message "Connection error ongoing - No connection to SBC PKT ports from HFE"
Every time I start my SBC instance, the instance stops itself after a few minutes.
Calls are failing to reach the SBC.
One of my instances sent a broadcast message saying: "SplitBrain: Going for REBOOT to resolve id collision!!!"
I am unable to log in to my HFE via the mgmt interface
I have correctly configured the SBC PKT ports, but I am still getting "Connection error ongoing - No connection to SBC PKT ports
from HFE in the HFE.log"
My private endpoint is in a different subnet to the HFE interface and I am not receiving traffic
My new SBC HA with HFE setup is not accessible because the metaVariable table data is incomplete
This section describes some common issues found in SBC GCP instances, and the action needed to verify or troubleshoot the issues.
When I try to SSH in to the SBC as linuxadmin, I receive "Permission denied (publickey)"
It implies that there are errors in the public key provided, or you are using a different public key that the one provided.
Action:
1. Check that the supplied linuxadmin key is correct:

a. Go to Compute Engine > VM Instances.
b. Click on the instance.
c. Click on the SSH key.
d. Verify the public key matches the result running ssh-keygen -y -f <<key file>>.
e. Verify the format is ssh-rsa ... linuxadmin.
2. Verify that 'Block project-wide SSH keys' is selected:
a. Go to Compute Engine > VM Instances.
b. Click on the instance.
c. Check 'SSH keys' for the checkbox.
3. Verify that there are no 'SSH Keys' in the global Metadata.
a. Go to Compute Engine > Metadata.
b. If there are any SSH keys, remove them.
4. When you find the issue:
a. If it is an error in the key supplied, update the key and reboot the instance.
b. If it is an error with global Metadata keys, all SBC instances recreate all SBC instances and restart all the HFE node to fetch the
latest SBC information.
The HFE.log is continually getting the error message "Connection error ongoing - No
connection to SBC PKT ports from HFE"
If this log is continually written to the HFE.log, it implies that the HFE node cannot connect to the SBCs.
Action:
1. Ensure that PKT0 and PKT1 are configured correctly through the CLI. Refer to the section "CLI Configuration for Configuring PKT Ports"
of the page Instantiating SBC SWe in GCP.
2. Ensure that the IPs listed in the HFE_conf.log are the ones attached to the SBC:
a.
2.
a. Go to /opt/HFE/log/.
b. Find the logs which specify the IPs for the SBC; they are of the form: <<SBC instance name>> - IP for <<pkt0
/pkt1>> is <<IP>>.
c. Find the Alias IPs for the SBC:
i. Go to Compute Engine > VM Instances.
ii. Click on the instance.
iii. In the Network interfaces table, observe the nic2 and nic3 and ensure that the IPs in the Alias IP ranges match.
3. Check the VPC routes and firewalls are correct:

a. Go to VPC network > VPC networks.
b. Click on the VPC for PKT0.
c. Click on Firewall rules and verify firewall rules exist that, as described in the section "Google Firewall Rules" of the page Config
ure HFE Nodes in GCP.
d. Click on Routes and verify the routes exist, as described in the section "Google Network Routes" of the page Configure HFE
Nodes in GCP.
e. Repeat for PKT1.
Every time I start my SBC instance, the instance stops itself after a few minutes.
This is the result of the invalid user-data. Enter only valid json. Refer to the section "User Data Format" of the page Instantiating SBC SWe in GCP.
Action:
1. Go to Compute > VM instances.

2. Click on the instance.
3. Go to Custom metadata.
4. Click on user-data.
5. Copy the user-data into a file a verify that it is valid JSON. For example:
a. Linux utility jq: jq . user-data.txt
b. Python: python -m json.tool user-data.txt
c. If valid, the user data is printed out; else, an error is displayed.
Calls are failing to reach the SBC.

Action:
1. Ensure that there are no error logs in the HFE.log. Refer to the section "HFE Node Logging" of the page Configure HFE Nodes in GCP.
2. Ensure that the end point of the traffic is allowed access through the VPC firewalls. Refer to the section "Google Firewall Rules" of the
page Configure HFE Nodes in GCP.
One of my instances sent a broadcast message saying: "SplitBrain: Going for REBOOT to
resolve id collision!!!"
This is the result of starting both the instances simultaneously, and trying to communicate with the same ID. This is an expected behavior. The
system reboots and comes up as Standby.
I am unable to log in to my HFE via the mgmt interface
It implies that either there is a configuration issue, or the firewall rules are not updated correctly.
Action:
1. Ensure the IP from which you send SSH requests is allowed through the VPC firewall. Refer to the section "Create Firewall Rules" of the
page Configure VPC Networks.
2. Ensure the IP from which you send SSH requests is in the HFE node user-data correctly. Refer to the section "User Data Example" of
the page Configure HFE Nodes in GCP.
a. Ensure that the updated line is similar to the following:
/bin/echo "REMOTE_SSH_MACHINE_IP=\"10.27.178.4\"" >> $NAT_VAR
3. The HFE script may fail before creating the routes. In that case:
a. Attempt to SSH in to NIC0 on the HFE node.
b. Check the logs for errors in the directory /opt/HFE/log/. Refer to the section "HFE Node Logging" of the page Configure HFE
Nodes in GCP.
I have correctly configured the SBC PKT ports, but I am still getting "Connection error
ongoing - No connection to SBC PKT ports from HFE in the HFE.log"
The possible reason is that the SBC PKT interface is unable to find the HFE interface.
Action:
1. Login to the active SBC.

2. Run tshark on the port:
tshark -i pkt0/pkt1
3. Look for ARP error messages, such as:
0.999962 42:01:0a:00:41:e8 -> Broadcast ARP 42 Who has 10.0.65.231? Tell 10.0.65.232
4. Perform a switchover through the CLI:
request system admin <system_name> switchover
5. Verify HFE connects to the new active SBC.

6. If unresolved, repeat steps 4 and 5.
My private endpoint is in a different subnet to the HFE interface and I am not receiving
traffic
Perform additional steps to allow traffic to reach the HFE, if it is a different subnet.
Action:
1. Allow traffic between the subnets:

a. Peer the two VPCs together. Refer to https://cloud.google.com/vpc/docs/using-vpc-peering for details.
1.
a.
Ensure to peer both the VPCs.
b. Add necessary Firewall rules to allow traffic between the peered subnet. Refer to https://cloud.google.com/vpc/docs/using-
firewalls for details.
2. If the HFE instance is 2.0, add the route to the subnet on the HFE instance:
a. Get the gateway IP address of the subnet where the private endpoint is located:
i. Go to VPC network.
ii. Select VPC networks.
iii. Select the HFE private subnet from the table. The Gateway IP address is located under Gateway heading.
b. Update the HFE startup-script:
i. Go to Compute Engine.
ii. Select the HFE instance.
iii. Select EDIT.
iv. Go to Custom metadata.
v. In the penultimate line of the startup script add the following command:
ip route add <endpoint CIDR> via <gateway ip> dev <ens5/eth1>
See the following startup script excerpt for example:
/bin/echo "Configured using HFE script - $HFE_FILE" >> $LOG_FILE

/bin/echo $(timestamp) " ========================= Done
==========================================" >> $LOG_FILE
ip route add 10.27.27.0/24 via 10.27.3.1 dev ens5
nohup $HFE_FILE setup > /dev/null 2>&1 &
Note
For ubuntu, the interface name is ens5. For any other, it is eth1.
c. Reboot the HFE instance.
My new SBC HA with HFE setup is not accessible because the metaVariable table data is
incomplete
When deploying an HA setup in a public cloud environment, each node must be able to query all other associated instances (peer SBC or HFE
node) to obtain information about the other nodes. If there is a delay in creating any instance within the setup, the other nodes are unable to
collect complete information and data is missing from the metaVariable table in the configuration database. The SBC application cannot start if
cloud-init fails and the database is populated incorrectly.
To correct this issue, reboot both SBC instances from the console to ensure SSH works on the instances, and to allow the nodes to gather all of
the required information.
Recovering SSH Key Access in Public Cloud and Updating
User Data
In this section:

I need to update my SBC User Data
I have lost access to the admin SSH Key
I have lost access to the linuxadmin SSH Key or need to regenerate

In Azure, the SBC's user data is initially populated by the VMs customData, which does not support being updated. Azure introduced a userData
configuration option for the VMs which does support being updated. To update the userData, perform the following method on a Linux machine
using the Azure CLI:
Note
You must perform the following procedure on both the SBCs in an HA-SBC setup.
1. Create a file that contains complete user data through any of the following methods:
a. Create from scratch using the procedures mentioned in the following documents:
i. Standalone: Instantiate Standalone SBC on Azure
ii. SBC HA-HFE: Instantiate SBC HA with HFE on Azure
b. Copy the existing user data from the Azure SBC:
1. Perform SSH into linuxadmin: ssh -i <sshKeyFile> -p2024 linuxadmin@<MgmtIpAddress>.
2. Use sbcDiagnostic to collect the userData.json file: sbcDiagnostic 1.
3. Use SCP with linuxadmin to copy the file locally: scp -i <sshKeyFile> -P2024
linuxadmin@<MgmtIpAddress>:/home/linuxadmin/sbc_diag_logs/userData.json.
4. Use a text editor to change the required values.
2. Log on to the Azure CLI using the following command:
az login
3. Run the following command to update the userData configuration:
az rest -m patch --headers "Content-Type=application/json" -u "https://management.azure.com

//subscriptions/<SUBSCRIPTION_ID>/resourceGroups/<RESOURCE_GROUP_NAME>/providers/Microsoft.Compute
/virtualMachines/<VM_NAME>?api-version=2021-03-01" --body "{ \"properties\" : { \"userData\" :
\"$(base64 -w0 <USER_DATA_JSON_FILE_NAME>)\" }}"
4. Reboot the SBC.
If you have lost access to the admin SSH key and have not configured alternative SSH keys through the SBX application, see "I need to update
my SBC User Data" above and update the AdminSshKey value with the new SSH public Key.

The SBC does not support the Azure Reset Password approach to update the SSH key. If you have lost access to the linuxadmin SSH key
and do not have a configured alternative SSH key through the SBC application, see I need to update my SBC User Data and update
LinuxadminSshKey value with the new SSH public Key. If linuxadmin SSH key was not updated before, you need to add the LinuxadminSshKey
key to the user data. Enter the following command to add the new value under AdminSshKey.
"AdminSshKey": "ssh-rsa XXXXXX",

"LinuxadminSshKey": "ssh-rsa YYYYYY",

Note
Perform the following procedure to update the User Data for the SBC in the GCP console:
1. Navigate to Compute Engine VM Instances.

2. Select Instance
3. Click Edit
4. Navigate to Metadata
5. Update the Value box for Key user-data
6. Click Save
7. Reboot the SBC

If you have lost access to the Admin SSH key and have not configured alternative SSH keys through the SBC application, see "I need to update
my SBC User Data" above and update AdminSshKey value with the new SSH public Key.

Perform the following procedure to update the linuxadmin SSH key:
1. Navigate to Compute Engine VM Instances.

2. Click Edit.
3. Navigate to SSH keys.
4. Replace the public key with the new public key. Ensure the linuxadmin is still present at the end.
Example: ssh-rsa AAAA linuxadmin.
5. Click SAVE.
6. Reboot the SBC.

Note
Perform the following procedure to update the SBC User Data:
1. Navigate to EC2 Instances
2.
2. Select Instance
3. Stop the instance:
a. Navigate to Instance state Stop instance
4. Edit the user data:
a. Navigate to Actions Instance settings Edit user data
b. Update the user data.
c. Click Save.
5. Start the instance:
a. Navigate to Instance state Start instance

If you have lost access to the Admin SSH key and have not configured alternative SSH keys through the SBC application, see "I need to update
my SBC User Data" above and update AdminSshKey value with the new SSH public Key.
Debugging SBC SWe Virtual and in Private Cloud

In this section:
Troubleshooting at VM Level
Troubleshooting at ESXi Host Level
Collecting Diagnostic information at VMware ESXi Hypervisor
Troubleshooting During Switchover
Typical VMware ESXi Virtual Environment
Top-Level Troubleshooting Flow
After switchover, if Calls/Registrations do not work, then check the GARP settings at the router. Generally, by default, in routers such
Juniper SRX, this setting is disabled. For details, see the link:
http://kb.juniper.net/InfoCenter/index?page=content&id=KB24349
Troubleshooting at VM Level
Troubleshoot SBC SWe inside VM using available CLI commands, DBG/SYS logs and call trace filter rules for both signaling and media traffic.
Troubleshooting at ESXi Host Level

Please refer to VMware documentation for troubleshooting guidance. For VMware ESXi troubleshooting, please refer to vsphere-esxi-vcenter-
server-51-troubleshooting-guide.pdf.
Collecting Diagnostic information at VMware ESXi Hypervisor

Use "vm-support" command to create a .tgz archive file of the ESXi logs, command results, and configuration information at the ESXi.
Accomplish the following steps:
1. Login to ESXi host shell using ESXi Management IP address.

2. Ensure “ssh” is enabled on ESXi host (use vSphere to enable it if not already enabled).
3. Enter the following command to view a list of vm-support command options:
vm-support -h
Send the bundled file to Ribbon for further debugging.
Reference:
http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&docTypeID=DT_KB_1_1&externalId=1010705
Troubleshooting During Switchover
As a part of the SBC switch-over process, the SBC moves the IP (Floating IP) to a a different NIC. The SBC then reconfigures the NICs
appropriately and broadcasts a GARP reply to inform neighboring devices about the change in the MAC address for the floating IP.Devices that
receive the ARP packet then update their ARP tables with the new MAC address.
When the system experiences RTP issues after failovers, it is probably due to the fact that newly active interfaces are not discovered on the
switch.
The link provides the recommended settings:
http://kb.juniper.net/InfoCenter/index?page=content&id=KB24349
Cloud Diagnostic Tool User Guide
Contents: Related articles:
Overview
Supported diagnostics
Prerequisites
CLI Examples
help
showCpuInfo
showMemoryInfo
showStorageInfo
showPlatformInfo
showNetworkInfo
checkDiskPerformance
showFullSystemInfo
startNetworkServer
startNetworkTest
startMessageSizeTest
quit/exit
Overview
The Cloud Diagnostic tool, also known as cloud_diags.py script, facilitates debugging of Ribbon cloud devices. You can use this tool as a test
agent on all Ribbon cloud instances as well as in production cloud environments where users only have access to the VM hosting
the Ribbon instance.
Note
The Cloud Diagnostic tool is currently supported on the SBC, PSX and EMS SWe platforms.
Supported diagnostics
System information
CPU information
Platform information
Storage information
Memory information
Basic disk IOPS
Network interfaces information
Check if Metadata supported
Check if Config-drive supported
Check if DHCP used
Check if SBC SR-IOV supported
Network connectivity and performance testing
Packet load throughput measurements on specified interfaces (mgtx, pktx) for different packet sizes (TCP/UDP)
Request/response round trip measurements (latency) with time stamps
Prerequisites
Create an IP Access Control List (ACL) rules (only for SBC) that is used to allow access to incoming IP packets. A separate ACL rule is required
for each protocol type. The ACL rule allows a packet on a specific IP address/port and can be configured to have an “fillRate” and “bucketSize”
set to “Unlimited”. For additional information, refer to Working with Access Control Lists.
An example of a user generated ACL rule on SBC CLI:
set addressContext default ipAccessControlList rule <rule_name> protocol tcp destinationIpAddress

<destination_ip> destinationAddressPrefixLength <dest_prefix_len> destinationPort any precedence <precedence_no>
set addressContext default ipAccessControlList rule <rule_name> bucketSize unlimited fillRate unlimited
set addressContext default ipAccessControlList rule <rule_name> state enabled
commit
Limitations: Even with the ACL rule configured to Unlimited; the rule is limited by the Operator Aggregate Policer. The total amount of bandwidth
allowed on the device is as follows:
Hard coded to 20,000 packets/second

Based on a calculation of 1500 bytes/packet. Expect to get up to 1500 bytes * 8 bytes/bit * 20000 pkts = 240Mbit/second
CLI Examples
Note
The outputs displayed in this section may differ based on the actual system configurations and various other requirements. You may
consider the outputs as an example.
The Cloud Diagnostic tool consists of following commands, each of these commands accomplishes one or more feature described in the feature
overview section.
To run on an SBC system, ssh to the SBC Linux shell as linuxadmin user. The script is in /home/linuxadmin/cloud_diags/cloud_diags.py
directory.
To run on a PSX or an EMS system, ssh to the system Linux shell as root user. The script is in /root/cloud_diags/cloud_diags.py
directory.
Note
Within the tool, command names are case-sensitive and required to be entered as shown. Tab completion is supported for command
names.
help
This command provides information about the available commands or specific information about a command.
command syntax: help [command_name]
Optional parameter(s): command_name
Example:
1. To view the list of available commands:
(Enter command or ?) : ?
Supported commands (type help <command_name>):

==============================================
EOF showCpuInfo showStorageInfo
checkDiskPerformance showFullSystemInfo startMessageSizeTest
exit showMemoryInfo startNetworkServer
help showNetworkInfo startNetworkTest
quit showPlatformInfo
2. To view details of a specific command: Command syntax: help command_name
(Enter command or ?) : help startNetworkTest
Start the Network Test on the Client

Command Syntax:
startNetworkTest -p tcp --si <remote_server_ip> [--sp <remote_server_port_no>] --li <local_ip>
[--lp <local_port_no>] [-r <msg_rate_per_sec>] [-m <message_size>] [-c <run_count>]
startNetworkTest -p udp --si <remote_server_ip> [--sp <remote_server_port_no>] [-r
<msg_rate_per_sec>] [-m <message_size>] [-c <run_count>]
Mandatory Parameters:
-p <protocol_type>
--si <remote_server_ip>
--li <local_client_ip> (only required for TCP)
Optional parameters:
--sp <remote_server_port_no> (default TCP=40000, UDP=5061)
--lp <local_client_port_no> (default TCP=20000, UDP=5061)
-r <msg_rate_per_sec> (default = 1000)
-m <msg_size> (default = 500)
-c <run_count> (default = 1)
-f (output test result to file named <applicationType>_<hostname>_performanceResult_YYYYMMDD-
HHMMSS.txt)
Example:
startNetworkTest -p tcp --si 10.1.10.1 --sp 40000 --li 10.20.2.20 --lp 20000 -r 1000 -m 500 -c 1
-f
startNetworkTest -p udp --si 10.1.10.1 --sp 5061 -r 10000 -m 250 -c 5 -f
Note: Please ensure destination network server is running before running this test.
showCpuInfo
Displays information on the CPU model, CPU virtualization, and number of cores available for the application.
Help information: Displays information on vCPU's, including clock speed, sockets, cores, and threads.
(Enter command or ?) : showCpuInfo
System CPU info :

CPU Model = Intel(R) Xeon(R) CPU E5-2690 v3 @ 2.60GHz (2596.958 MHz)
Number of CPU's = 4 ( 4 Sockets * 1 Cores * 1 Threads)
CPU Virtualization = VT-x
showMemoryInfo
Displays information of total memory, used memory and available memory on the system.
Help information: Displays information on system memory including available and free memory.
(Enter command or ?) : showMemoryInfo
System memory info :

Total Memory = 9.79 GB, Free = 5.21 GB, Buffers = 0.00 GB, Cached = 0.62 GB
Actual Free = 5.84 GB (Free+Buffers+Cached)
showStorageInfo
Displays information on the total storage, used storage and available capacity of the storage device on the system.
Help information: Displays information on system storage/disks including used and free space.
(Enter command or ?) : showStorageInfo
System storage info :

Filesystem Type Size Used Avail Use% Mounted on
/dev/mapper/debian-root ext3 78G 8.9G 66G 12% /
/dev/vda1 ext4 184M 34M 142M 20% /boot
/dev/mapper/debian-root ext3 78G 8.9G 66G 12% /tmp
showPlatformInfo
Displays Linux platform information.
Help information: Displays information on platform, includes node name, app type, Linux platform info, architecture, DHCP use, SRIOV, config-
drive and metadata info.
(Enter command or ?) : showPlatformInfo
System platform info :

Node name = vsbc1
Application type = SBC, Package name = sbc-V06.01.00-A013
Platform Info = Linux-3.2.84-x86_64-with-debian-8, Architecture = ('64bit', 'ELF')
DHCP = DHCP used
SR-IOV support = Not Supported
Config Drive = /dev/disk/by-label/config-2
Checking for Metadata .....
Metadata - Not available
showNetworkInfo
Displays information on network interfaces on the system.
Help information: Displays information on network interfaces including configured IP addresses.
(Enter command or ?) : showNetworkInfo
System network interfaces info :

pkt0 Link encap:Ethernet HWaddr fa:16:3e:bb:b8:be
inet6 addr: fe80::f816:3eff:febb:b8be/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
ha0 Link encap:Ethernet HWaddr fa:16:3e:9a:b6:82

inet addr:192.168.2.94 Bcast:192.168.2.255 Mask:255.255.255.0
inet6 addr: fe80::f816:3eff:fe9a:b682/64 Scope:Link
pkt1 Link encap:Ethernet HWaddr fa:16:3e:11:82:6c

inet6 addr: fe80::f816:3eff:fe11:826c/64 Scope:Link
mgt0 Link encap:Ethernet HWaddr fa:16:3e:a5:0c:22

inet6 addr: fe80::f816:3eff:fea5:c22/64 Scope:Link
Displays information collected from basic disk IO performance tests.
Help information:
Performs basic check of the disk IO performance by reading and writing 10K data records 1,000 times from/to disk.
Displays time and speed in MB/sec taken to read/write data.
(Enter command or ?) : checkDiskPerformance
Basic disk IO performance (may take a few secs to complete) :

Performing write test - Writing 10K data records 1,000 times to disk :
1000+0 records in
1000+0 records out
10240000 bytes (10 MB) copied, 0.608691 s, 16.8 MB/s
Performing read test - Copying 10K data records 1,000 times from disk to null stream:
1000+0 records in
1000+0 records out
10240000 bytes (10 MB) copied, 0.0260588 s, 393 MB/s
showFullSystemInfo
Displays full system information.
Command syntax: showFullSystemInfo [-f]
Optional Parameter(s): -f
If the optional -f flag is specified, output from the command is written to a file named ApplicationName_HostName_fullsysinfo_YYYY
MMDD-HHMMSS.txt
Example:
For SBC - SBC_vsbc_fullsysinfo_20170322-121008.txt

For EMS - EMS_vems_fullsysinfo_20170322-121008.txt
For PSX - PSX_vpsx_fullsysinfo_20170322-121008.txt
Where YYYYMMDD-HHMMSS is the date/time of the file created.
Note - In command syntax -f flag mentioned inside bracket to indicate its an optional parameter, actual command do not require use
of brackets
Help information: Displays comprehensive system information including platform, CPU, memory, storage, network interfaces and
checks disk IOPs.
Displays output of each of the following commands:
showPlatformInfo
showCpuInfo
showMemoryInfo
showStorageInfo
showNetworkInfo
(Enter command or ?) : showFullSystemInfo
Full System Info, collected on - Thu Jun 1 03:07:33 2017

Node name = vsbc1
Platform Info = Linux-3.2.84-x86_64-with-debian-7.11, Architecture = ('64bit', 'ELF')
DHCP = DHCP used
System CPU info :








1000+0 records in
1000+0 records out
1000+0 records in
1000+0 records out
(Enter command or ?) : showFullSystemInfo -f
Full System Info, collected on - Thu Jun 1 03:08:33 2017

Node name = vsbc1
Platform Info = Linux-3.2.84-x86_64-with-debian-7.11, Architecture = ('64bit', 'ELF')
DHCP = DHCP used
System CPU info :







1000+0 records in
1000+0 records out
1000+0 records in
1000+0 records out
10240000 bytes (10 MB) copied, 0.0376839 s, 272 MB/s
Test output also written to file - SBC_vsbc1_fullsysinfo_20170601-030833.txt
startNetworkServer
This command runs test server with parameters. The user is required to select the protocol type, IP address and optional port for the test. The
server acts as a listener for that protocol type; receives and forwards messages from/to the Client.
To start the server from the diagnostics tool menu, execute below command:
startNetworkServer -p <protocol_type> --li <servers_local_ip> [--lp <servers_local_port_no>]
Mandatory Parameters
Parameter Description / Usage Example
-p Specify the Protocol Type of test server. TCP/UDP
Values:
TCP
UDP
--li Specify the Local Server IP (IPv4 or IPv6) address. IPV4 and Protocol - startNetwrokServer -p tcp --li 1.1.1.1
IPV6 and Protocol - startNetwrokServer -p udp --li 2001:0DB8:

AC10:FE01::
Optional Parameters
Parameter Description / Usage Example
--lp Specify the Local Server Port Number. IP (IPV4 or IPV6), Protocol, and Port - startNetwrokServer -p
tcp --li 1.1.1.1 --lp 5061
Values:
TCP: 1024 – 65535. Default TCP - 40000

UDP: 5060 or 5061. Default UDP - 5061
If the user does not specify a Port Number, a default port

number is assigned.
This diagnostics tool is running as TCP Server to receive on IP = fd00:10:6b50:42c0::1c1 port = 40000
Waiting ...
Enter Ctrl-c to exit server mode and return to command prompt
Note
When the diagnostics tool runs as a server, it listens to the port specified in --lp (or default port), and responds to any incoming packet
from the client. The standard output connected to the server displays the message "Waiting ...", without displaying any further
information. To exit the server mode and return to the command prompt, press the Ctrl+C key combination.
startNetworkTest
This command runs client side performance test. The Client side is responsible for running the test and sending packets to the server. Server
should be running when the client test is started.
To start the client test from the diagnostics tool menu, execute below command:
startNetworkTest -p <protocol_type> --si <remote_server_ip> [--sp <remote_server_port_no>] --li <local_ip> [--

lp <local_port_no>] [-r <msg_rate_per_sec>] [-m <message_size>] [-c <run_count>]
Parameter Description / Usage Length Example

/Range
-p Specify the Protocol Type of test server N/A TCP/UDP
Values:
TCP
UDP
--si Specify the Remote Server IP (IPv4 or IPv6) address. N/A IP4: 1.1.1.1
IPV6: 2001:0DB8:AC10:FE01::
--li Specify the Local Server IP (IPv4 or IPv6) address. Mandatory for TCP N/A IP4: 1.1.1.1
and not applicable for UDP. IPV6: 2001:0DB8:AC10:FE01::
Optional Parameters
Parameter Description / Usage Length Example/Default Value

/Range
--sp Specify the Remote Server Port Number. TCP: 1024 TCP - 40000
- 65535
If the user does not specify a Port Number, a default port number is UDP - 5061
assigned. UDP: 5060
or 5061
--lp Specify the Local Client Port Number. This parameter is not applicable for TCP: 1024 TCP - 20000
UDP protocol. - 65535
-r Specify Message Rate Per Second. 1- 10000 1000
-m Specify Message Size. 100-10000 500
-c Specify Run Count (the number of time the test is to be run). 1-100 1
-f Specify whether test result is written to a file. If, -f flag is specified, the N/A Application Name_Host Name_performanceResult
result is displayed and exported to a text file. _YYYYMMDD-HHMMSS.txt
Naming convention of a text file: SBC_vsbc1_performanceResult_20170601-

101112.txt
SBC - Specifies the application name.
vsbc - Specifies the host name. EMS_vems1_performanceResult_20170601-
YYYYMMDD-HHMMSS - Specifies the date/time of file is 101112.txt
created.
PSX_vpsx1_performanceResult_20170601-
101112.txt
StartNetwork command output with TCP protocol
startNetworkTest -p tcp --si fd00:10:6b50:43a0::dd --li fd00:10:6b50:43a0::d8 -r 10000 -m 500

Performance Measurement for TCP
User Input(s) |
Server Address | fd00:10:6b50:43a0::dd 40000
Local Address | fd00:10:6b50:43a0::d8 20000
Protocol Type | TCP
Port Type | MGMT
Number of Messages| 10000
Message Size | 500
Performance Test Results
Fastest | 0.000619
Slowest | 0.017394
Bucket 1 (Range 0.000619 - 0.003974)| 4467
Bucket 2 (Range 0.003974 - 0.007329)| 3796
Bucket 3 (Range 0.007329 - 0.010684)| 1308
Bucket 4 (Range 0.010684 - 0.014039)| 228
Bucket 5 (Range 0.014039 - 0.017394)| 201
Total Time | 0.373096
Packets Lost | 0
Example Usage – TCP
Note
Scenarios below are for illustration purpose only.
Scenario Command
User has All Parameters (without file store startNetwrokTest -p tcp --si 1.1.1.1 --sp 40000 --li 2.2.2.2 --lp 20000 -r 2000 -m 1000 -c
command) 2
User has All Parameters (with file store command) startNetwrokTest -p tcp --si 1.1.1.1 --sp 40000 --li 2.2.2.2 --lp 20000 -r 2000 -m 1000 -c
2 -f
User has only
IPv 4 and Protocol startNetwrokTest -p tcp --si 1.1.1.1 --li 2.2.2.2
IPv 6 and Protocol startNetwrokTest -p tcp --si 2001:0DB8:AC10:FE01:: --li 2001::0DB8:AC10
IP, Protocol and Server Port startNetwrokTest -p tcp --si 1.1.1.1 --sp 40000 --li 2.2.2.2
IP, Protocol and local Port startNetwrokTest -p tcp --si 1.1.1.1 --li 2.2.2.2 --lp 20000
IP, Protocol and Port startNetwrokTest -p tcp --si 1.1.1.1 --sp 40000 --li 2.2.2.2 --lp 20000
StartNetwork command output with UDP protocol
startNetworkTest -p udp --si fd00:10:6b50:43a0::dd -r 1000 -m 500
Performance Measurement for UDP

User Input(s) |
Server Address | fd00:10:6b50:43a0::dd 5061
Local Address | Not Applicable
Protocol Type | UDP
Port Type | MGMT
Number of Messages| 1000
Message Size | 500
Performance Test Results
Fastest | 0.000488
Slowest | 0.007309
Bucket 1 (Range 0.000488 - 0.001852)| 545
Bucket 2 (Range 0.001852 - 0.003216)| 146
Bucket 3 (Range 0.003216 - 0.004580)| 158
Bucket 4 (Range 0.004580 - 0.005944)| 124
Bucket 5 (Range 0.005944 - 0.007309)| 27
Total Time | 1.067999
Packets Lost | 0
Example Usage – UDP
Scenario Command
User has All Parameters (without file store command) startNetwrokTest -p udp --si 1.1.1.1 --sp 5061 -r 2000 -m 1000 -c 2
User has All Parameters (with file store command) startNetwrokTest -p udp --si 1.1.1.1 --sp 5061 -r 2000 -m 1000 -c 2 -f
User has only
IPv 4 and Protocol startNetwrokTest -p udp --si 1.1.1.1
IPv 6 and Protocol startNetwrokTest -p udp --si 2001:0DB8:AC10:FE01::
IP, Protocol and Server Port startNetwrokTest -p udp --si 1.1.1.1 --sp 5061
startMessageSizeTest
This command runs client side message size test. The Client side is responsible for running the test and sending packets to the server.
To start the message size test from the diagnostics tool menu, execute below command:
startMessageSizeTest -p <protocol_type> --si <remote_server_ip> [--sp <remote_server_port_no>]
Parameter Description / Usage Length Example/Default

/Range Value
-p Specify the Protocol Type of test server, only UDP is allowed. N/A UDP
--si Specify the Remote Server IP (IPv4 or IPv6) address. Note: IP type must match in both server and N/A IP4: 1.1.1.1
message size test client to be successful. IPV6: 2001:0DB8:
AC10:FE01::
Optional Parameters
Parameter Description / Usage Length Example/Default

/Range Value
--sp Specify the Remote Server Port Number. 5060 or 5061

5061
If the user does not specify a Port Number, a default port number is assigned.
Example Usage – UDP
Scenario Command
User has All Parameters startMessageSizeTest -p udp --si 1.1.1.1 --sp 5061
User has
IPv 4 and Protocol startMessageSizeTest -p udp --si 1.1.1.1
IPv 6 and Protocol startMessageSizeTest -p udp --si 2001:0DB8:AC10:FE01::
Note
Ensure server is active before running client message size test to be successful.
quit/exit
Each of the command allows user to exit from the command mode of tool.
Command syntax: quit / exit
Example: Exit from tool command prompt and return to Linux terminal command prompt.
(Enter command or ?) : ?
Supported commands (type help <command_name>):

==============================================
EOF showCpuInfo showStorageInfo
checkDiskPerformance showFullSystemInfo startMessageSizeTest
exit showMemoryInfo startNetworkServer
help showNetworkInfo startNetworkTest
quit showPlatformInfo
For Troubleshooting Only - How to Enable ssh Access
Ribbon strongly recommends that you enable Secure Shell (ssh) access only for linuxadmin, and for troubleshooting only, ideally
restricted to key-based authentication and not passwords, and then disabled again.
Enable ssh
Perform the following steps to enable ssh access.
Step Action
1 Log on through BMC as user linuxadmin.
BMC
2 Change to user root:
su root
3 Enter the following command and then press Enter:
enableSsh
4 At the prompt, enter y and then press Enter.
Steps 2, 3, and 4
Disable ssh
Perform the following steps to disable ssh access.
Step Action
1 Log on through BMC as user linuxadmin
BMC
2 Change to user root:
su root
3 Enter the following command and then press Enter:
disableSsh
4 At the prompt, enter y and then press Enter.
SBC Troubleshooting Tools

In this section:
Platform Troubleshooting
How to Check Alarms
How to Check Peer-to-Peer Communication
How to Perform Call Traces
How to Verify Peer-to-Peer Connectivity
How to View and Download Event Logs
Hardware Troubleshooting
How to Locate SBC Chassis
How to Check LED Status
How to View System Status and Statistics
How to Perform a System Dump
SBC troubleshooting tools are primarily divided into two categories:
The SBC Core provides several tools to aid in troubleshooting the SBC platform, such as monitoring various system processes and statistics,
viewing and interpreting alarms, running diagnostics, and performing call trace simulations. This section provides a guide to the location of these
various tools in the SBC Core product documentation.
How to Check Alarms

How to Check Alarms

Navigate the following pages to view, edit, clear, and interpret SBC alarms:
EMA
Alarms - Current Alarms

Alarms - Cleared Alarms
SBC Core Alarms Guide
CLI
View Alarm Details
% show status/table alarms currentStatus
% show status/table alarms historyStatus
Show Status Alarms

Show Table Alarms
Show Status OAM
Show Table OAM
Clear Alarms
> request alarms clear
Request Alarms - CLI

The SIP Options Ping feature is used to verify peer-to-peer connectivity.
EMA
Call Trace Logs and Monitors - Options Ping - Cmds
CLI
> request addressContext <addressContext name> cmds optionsPing
Request Address Context - CLI

EMA
Call Trace and Packet Capture - Call Trace
CLI
Configuration: Call Trace - CLI

Executing: Request Global - CLI
How to Verify Peer-to-Peer Connectivity

Refer to the following page for insight in using SIP OPTIONS and ICMP Ping:
Path Check Support

Path Check Profile - CLI
SIP ARS Profile - CLI
Service Profiles - Path Check Profile (EMA)
Service Profiles - SIP ARS Profile (EMA)

Refer to the following pages for detailed information about viewing event logs and the configuration options.
EMA
Event Log - Filter Admin

Event Log - Filter Status
OAM - Event Log - Platform Audit Logs
Event Log - Sub System Admin
Event Log - Type Admin
Event Log - Type Status
CLI
Event Log - CLI

Request OAM - CLI
Refer to Log Management to download event logs from the EMA.
The SBC provides different hardware troubleshooting tools to aid in troubleshooting the SBC hardware by reviewing, diagnosing, and identifying
operational or technical problems. This section provides a guide to the location of these various tools in the SBC product documentation.


The Blink Locator LED helps you to locate the SBC chassis in the rack. It also specifies the Locator LED is turned ON or OFF to locate the SBC.
EMA
Troubleshooting Tools - Blink Locator LED

EMA
Hardware Status - LED Status
CLI
% show status system ledStatus
Show Status System
Physical Inspection
Front panel LED descriptions are located on following pages:
SBC 5400 Hardware Platform Specifications
SBC 7000 Hardware Platform Specifications

EMA
Dashboard - CAC Offenders Status

Sessions - Call Count Status
Sessions - Call Detail Status
Sessions - Call Summary Status
Hardware Status - CPU Util Current Statistics
Troubleshooting Tools - Hard Disk Status
Announcements - Memory Usage
Troubleshooting Tools - Monitor Endpoint Status
Troubleshooting Tools - Monitor Target Status
System Status And Statistics - Software Upgrade Status
Zone Specific - Sonus SIP Sig Peer Ovld Status Entry
System Status and Statistics - System Congestion Status
System Status And Statistics - System Congestion Interval Statistics
Dashboard - System Statistics
Dashboard - System Status
CLI
Show Status Address Context

Show Table Address Context
Show Status Alarms
Show Table Alarms
Show Status Global
Show Table Global
Show Status OAM
Show Table OAM
Show Table Profiles
Show Status System
Show Table System

EMA
Troubleshooting Tools - Coredump List

Troubleshooting Tools - Coredump Summary
Troubleshooting Tools - System Dump
CLI
> request system serverAdmin <server_name> forceCoreDump
Request System - CLI
Troubleshooting SBC Using Debug Event Logs

Event Log - CLI

Debug Event Log Overview
Traps - CLI
Troubleshooting the SBC using Debug Event Logs
OAM - Traps - Admin
Event Log - Type Admin
sonusCpEventLogFileDebugLevelInfoNotification -
MAJOR
sonusCpEventLogFileDebugLevelInfoClearNotification -
MINOR

The SBC records the maximum number of Debug Event logs, which can potentially cause memory to become congested resulting in unexpected
or undesirable SBC performance.
If using INFO filter level is needed for troubleshooting, the SBC triggers the alarm sonusCpEventLogFileDebugLevelInfoNotification any time the
Debug Event Log filter level is set to INFO as a reminder of potential memory congestion due to the accumulation of a large number of Debug
Event logs in memory. The alarm includes a warning message to set the filter level to MAJOR. The alarm is enabled or disabled using both CLI
and EMA
When the filter level is set to INFO, the following events occur:
The SBC generates the alarm sonusCpEventLogFileDebugLevelInfoNotification every five minutes.

The SBC generates a warning message Debug Event Log filter level is set to INFO. Set to MAJOR if finished
troubleshooting on the last modified Debug Event Log file.
Once the troubleshooting is completed, set the filter level to MAJOR. The alarms are cleared when the filter level is set to MAJOR.
When the filter level is changed, the clear alarm sonusCpEventLogFileDebugLevelInfoClearNotification is triggered and a message D
ebug Event Log filter level is no longer set to INFO is displayed in the log file.
Troubleshooting the SBC using Debug Event Logs

To troubleshoot the SBC and to avoid running out of hard drive space:
1. Check if the sonusCpEventLogFileDebugLevelInfoNotification alarm is enabled. By default, this alarm is enabled.
show table oam traps admin sonusCpEventLogFileDebugLevelInfoNotification state
state enabled;
If it is disabled, enable the sonusCpEventLogFileDebugLevelInfoNotification alarm by executing the following command:
% set oam traps admin sonusCpEventLogFileDebugLevelInfoNotification state enabled
% commit
2. Set the filter level of the .DBG files to INFO.
% set oam eventLog typeAdmin debug filterLevel info
% commit
3. To inspect the debug log files, navigate to the /var/log/sonus/evlog directory. Check for the files with the .DBG extension.
4. Check whether the alarm is triggered (optional):
a. Open the .DBG file with the latest timestamp. List of MAJOR events followed by the list of INFO events are seen. The last Major
event has the following description:
Debug Event Log filter level is set to INFO. Set to MAJOR if finished troubleshooting.
A sample of a .DBG file is shown below:
098 10232017 073429.339677:1.01.00.00336.MAJOR .CHM: *ChmSetNorthboundIface: confd reload start

099 10232017 073429.732518:1.01.00.00337.MAJOR .CHM: *ChmSetNorthboundIface: confd reload finish
104 10232017 073709.116682:1.01.00.00338.MAJOR .NRM: *Call Admission Updated: NTP Server is
Available
136 10232017 073713.059768:1.01.00.00339.MAJOR .PRSNP: *PrsNpCoreStatusProc: NP NTP time
initialized secsH 3717747433 secsL 256045703
132 10232017 144508.294726:1.01.00.00340.MAJOR .NRS: LIFGROUP: Successfully added lifGroupId 3
and name IPIG1 to the lifGroupList
143 10252017 050651.346691:1.01.00.00341.MAJOR .EVLOG: Debug Event Log filter level is set to
Info. Set to MAJOR if finished troubleshooting.
111 10252017 050651.377036:1.01.00.00342.Info .SM: *SystemManager_i::icmMsgHdlr(): Received
message: 0x3c25
112 10252017 050651.377136:1.01.00.00343.Info .SM: *In SystemManager_i::
procConfdGetNextReqMsg(), 1167850545
121 10252017 050651.377188:1.01.00.00344.Info .SM: *In HwModuleComputeElement::
fillServerStatus()ActualNaem WFDSBC01b
091 10252017 050651.377303:1.01.00.00345.Info .SM: *In System_i::fillPeerServerStatus()
099 10252017 050651.377351:1.01.00.00346.Info .SM: *In System_i::fillPeerServerStatus() Unknown
105 10252017 050651.378502:1.01.00.00347.Info .CPX: *CpxGetNextReqFromCache: Entry not found in
cache
136 10252017 050656.271754:1.01.00.00348.Info .SCPA: .SCPA: (10492|139950200698624) Putting
idle timer message on timer task's queue
b. To view the details of the alarm, execute the following command as SBC administrator:
show table alarms currentStatus
ALARM CLEAR
ID TYPE TIMESTAMP INITIAL TIMESTAMP COUNT DESC
---------------------------------------------------------------------------------------------------
--------------------------------------------------------
32026 AUTOMATIC 2017-10-23T11:34:05-00:00 2017-10-23T11:34:05-00:00 1 Packet port pkt2 on
CE WFDSBC01b slot 0 with ifIndex 11 is DOWN
32027 AUTOMATIC 2017-10-23T11:34:05-00:00 2017-10-23T11:34:05-00:00 1 Packet port pkt3 on
CE WFDSBC01b slot 0 with ifIndex 12 is DOWN
32131 MANUAL 2017-10-25T10:26:03-00:00 2017-10-24T10:26:04-00:00 3 SystemSecurity
Intrusion Detection: AIDE cronjob detected file modifications
32227 AUTOMATIC 2017-10-25T10:28:55-00:00 2017-10-25T09:06:51-00:00 18 Debug Event Log
filter level is set to INFO. Set to MAJOR if finished troubleshooting
Set the debug level to MAJOR by executing the following command:
% set oam eventLog typeAdmin debug filterLevel major
% commit
Once the filter level is changed to MAJOR, the following message is displayed in log file:
Debug Event Log filter level is no longer set to INFO
Using SBC Packet Collector for Core Dump Analysis
In this section:
Introduction
Configuration Parameters
Defaults
Software Upgrade
Reporting Tool
Introduction
Core dumps that occur in the field are often the result of a new call flow. However, when these core dumps occur, it is difficult to quickly confirm
which new call flow caused the crash as there is no stored information relating to the sent and received network packets that comprise the call.
A facility is added to the SBC to enable memory based storage of recently sent and received SIP packets. In order to constrain the amount of
system memory used, by default, only the data for recent calls are stored. This data is captured in the SCM process.
Whether or not to save packets for stable calls or completed calls is specified in the configuration parameters.
In the event that a crash occurs, a tool is provided to extract this saved packet data from the core dump, and to provide the full contents of each
packet of the SIP call flow for each call that was present on the system when the crash occurred.
Configuration Parameters
global saveRecentCallFlowsInMemory
Parameter Length Default Description M

/Range /O
saveCallFlows N/A false Enables the storage of recent sent and received SIP packets in the SCM process. O
Note 1: If this value is toggled from true to false, all stored calls are purged.
Note 2: When the SBC is installed, saveCallFlows is changed to true.
maxMemoryUsage 512 - 512 This parameter allows the specification of a maximum amount of memory to be consumed O
10485760 for packet storage.
(kilobytes)
Note 1: When the SBC is installed, maxMemoryUsage is set to 5% of the available
memory on the target SBC.
storeDataForStableC N/A false If set to true, data is saved for stable calls and calls in setup up to the amount of memory O
alls specified in the MaxMemoryUsage parameter.
Note: If this value is toggled from true to false, already stored stable calls are purged.
storeDataForStableC N/A false If set to true, data is saved for completed calls, stable calls and calls in setup up to the O
ompletedCalls amount of memory specified in the MaxMemoryUsage parameter.
Note: If this value is toggled from true to false, already stored completed calls are purged.
Note: if storeDataForStableCalls is set to false then no completed calls are stored,

as the calls are purged when they transition to the stable state.
1. On the SBC main screen, navigate to All Global saveRecentCallFlowsInMemory.
saveRecentCallFlowsInMemory
Defaults
Whether the feature is turned on by default depends on the personality type and the platform.
When the feature is turned on by default, the maxMemoryUsage is set to 5% of the available memory.
Defaults
Personality Hardware Platforms SWE Cloud
ISBC Enabled Not available in the CLI Yes
SSBC Enabled Not available in the CLI Yes
MSBC Not available in the CLI Not available in the CLI Not available in the CLI
Software Upgrade
When upgrading to the 7.2.1 release, the defaults for saveCallFlowsInMemory are set to the same as a fresh install.
Reporting Tool
Note
Only core files generated from the ScmProcess contain call data.
Note
To run the reporting tool, you need to copy ScmProcess.dbg to /opt/sonus/sbx/bin for SBC 8.x and later versions.
When the reporting tool is run without switches, it will print a summary of each call, such as the following:
Call Flows Summary:

Gcid 16777221: Call time: 02/04/2019 11:38:37 EST
When the reporting tool is run with the -g <GCID> switch, the reporting tool will print out the complete PDUs for the call.
The following is an example:

Packet 1: IN
INVITE sip:[email protected]:5060 SIP/2.0
Via: SIP/2.0/UDP 10.2.0.169:5060;branch=z9hG4bK-9406-1-0
From: <sip:[email protected]:5060>;tag=9406SIPpTag001
To: sut <sip:[email protected]:5060>
Call-ID: [email protected]
CSeq: 1 INVITE
Supported: timer
Session-Expires: 120
Allow: OPTIONS, CANCEL, ACK, BYE, INFO
Proxy-Authorization: Digest username=\"<username>\",realm=\"example.com\",nonce=\"923749873894\",opaque=\"\",
uri=\"sip:[email protected]\",response=\"9273498349838974\",algorithm=MD5
Accept: application/sdp
Contact: sip:[email protected]:5060
Route: <sip:[email protected]:5060>;lr
P-Asserted-Identity: \"Sample\" <sip:
user0user1user2user3user4user5user6user7user8user9user0user1user2user3user4user5user6user7user8user9user0user1us
[email protected]>,\"9876543210\" <tel:9876543212;cpc=payphone>
Diversion: <sip:[email protected]:5060>;reason=\"sdfff-sdf\";counter=1;privacy=off, <sip:[email protected]>;
counter=1;privacy=off
P-Charging-Vector: icid-value=0fa92f5c-0000-1000-8000-0003bae278c0;icid-generated-at=10.32.200.42
Remote-Party-ID: \"<example>\" <sip:[email protected]:5060>;id-context=plain;privacy=off
P-K-Cfo: <tel: +19786418260 >;p=\"y\";r=\"msnr\";ap=n;ad=+19786148888
Content-Type: application/sdp
The full help for the utility is shown below:
usage: printSavedCallFlows.py [-h] [-a] [-e EXECUTABLE] [-g GCID] [-l LAST]
[-n NUMBER] [-o OUTPUT] [-p PID] [-s STARTTIME]
[-t ENDTIME] [-v] [-x] [-y] [-z]
[corefile]
Read saved call flows from a core dump
positional arguments:
corefile The corefile to be analyzed
optional arguments:
-h, --help show this help message and exit
-a, --all Print all call flows
-e EXECUTABLE, --executable EXECUTABLE
The executable associated with the corefile
default:/opt/sonus/sbx/bin/ScmProcess
-g GCID, --gcid GCID Print the call flow for the gcid (global call id)
default: print a summary of all call flows
-l LAST, --last LAST print the last n callflows
-n NUMBER, --number NUMBER
Only print the first n packets from each call flow
-o OUTPUT, --output OUTPUT
output file for results
-p PID, --pid PID Print call flows with a time greater than this value
-s STARTTIME, --starttime STARTTIME
Print call flows with a time greater than this value
-t ENDTIME, --endtime ENDTIME
print call flows with a time less than this value
-v, --verbose Enable verbose mode
-x, --headersOnly Only print packet headers
-y, --summary Only print only gcid, timestamp for each call flow
-z, --state Print the state for each call flow
Using Test Calls and IP Trunk Group Blocking
IP Trunk Group Blocking and Test Call Support

Overview
SIP Trunk Group - Block Direction - CLI
Test Calls
Test Call Number Profile - CLI
Identifying a Test Call
Test Call Number Profile - Test Call Number
Configuring Block Direction of the SBC
Services - Test Call Number Profile
Overview
The blocking function restricts the SBC from sending a SIP request (outside an existing dialog) from its own network to the opposite network, but
does not restrict receiving a SIP request (outside an existing dialog) from the opposite network to its own network.
When implementing a function that sends a test call, the network can send a test call to the opposite network even if blocking is enabled. The
SBC allows all test calls even if blocking is enabled on trunk groups.
When the Trunk Group is blocked in... Then the SBC does not allow out-of-dialog SIP requests that are...
Incoming Inbound to the Trunk Group
Outgoing Outbound to the Trunk Group
Bothways Inbound or Outbound to the Trunk Group
Test Calls
When blockingMode is enabled in a particular sipTrunkGroup, the SBC blocks all the normal calls in either one or both the directions based
on the blocking mode enabled except the test calls. The Sip Trunk Group blocking functionality does not impact the SBC test call processing. The
test call functionality is required for the maintenance blocking between interconnected operator's networks.
To configure a Test Call Number Profile, refer to the section Test Call Number Profile - CLI.
Identifying a Test Call

The test calls received at the SBC carries calling party category indication as Test Call. The test call functionality is required for maintenance
blocking between interconnected operator's networks. When the calling party's category is applied to indicate that the call is "test call," a cpc
parameter with the value test is inserted in the P-Asserted-Identity header field of the initial INVITE request. When SBC sees cpc=test in the
PAI header field, the call will be treated as test call.
Example:
P-Asserted-Identity: <sip:[email protected];cpc=test >
P-Asserted-Identity: <sip:user1;[email protected];user=phone>
The SBC identifies the call as test call by examining the cpc parameter received in the P-Asserted-Identity header field. Additionally, the SBC
compares the received called number against the pre-configured test call numbers in the Test Call Number Profile and selects the PSX (either to
send normal PSX or test PSX) for further routing. The SBC routes the test call based on the PSX response.
Configuring Block Direction of the SBC

To set the blocking direction under SIP Trunk Group, enter the following command:
% set addressContext <addressContext name> zone <zone name> sipTrunkGroup <SIPTG name> blockDirection <bothways
| incoming | none | outgoing>
Using the SSReq Tool
Note
Beginning with release 10.1, the Java version in the SBC is upgraded to 11.0. After upgrading the SBC to this release, the SSReq
application will not operate because the Java 11 environment in the client system/desktop does not include "javaws", which is required
to run SSReq on the client system.
Contents
Using SSReq
Download Request Fields
Policy Mid Call Action Fields
Policy Request Fields
Trigger Request Fields
Status Display
Viewing a Response
The SSReq tool is used to verify the provisioning and features of the SBC Core systems by simulating requests (policy, trigger, download,
DIAMETER, etc.). SSReq provides the ability to specify all of the parameters in the request and displays the response received from the PSX
and the call trace. The requests and responses can be saved in files for future use.
The SBC handles simulated calls from SSReq in the same manner as any live call sent from any client in a live Ribbon network, such as from a
GSX, a SIP server, etc. The policy response includes the same information provided to any client. Triggers are used to request a service from the
PSX, such as an Authcode validation service or toll-free number translation service, allowing for the emulation of two-stage calls. Download
requests are used to retrieve the script data from the SBC.
Supported Clients
EMA
EMS
GSX
H.323 gateway
H.323 gatekeeper
SIP server
Model
SSReq is a client/server software solution. The client is a Java-based, graphical user interface applet bundled with the EMA GUI and resides on
the Ribbon Insight server. The server software is bundled with the SBC, and is automatically installed on each SBC in your network.
SSReq Client/Server Software
Using SSReq
Note

Prerequisite 1
Prerequisite 2
Status Display
Summary
Viewing a Response
Steps
This section details SSReq operating procedures.
Prerequisite 1
Make sure you have provisioned the PSX for any functionality that you want to test using SSReq.
Prerequisite 2
Use Java 8 or above in your system to work with the enhanced SSREQ GUI in EMA 6.0 onward. To avoid any problem related to
execution of Java programs in your system, add your SBC IP Address to the list of trusted sites in the Java Control Panel.
To launch SSREQ application from SBC EMA, TLSv1.2 should be enabled in the Java Control Panel settings.
Execute the following steps to enable TLSv1.2:
1. On your computer, navigate to Start > Windows System > Control Panel. The Control Panel window is displayed.
Windows Control Panel Window
2. Click Java or Java (32-bit). The Java Control Panel is displayed.
Java Control Panel window
3.
3. Click Advanced tab. The options for Advanced tab are displayed.
4. Select Use TLS 1.2 under Advanced Security Settings.
Java Control Panel - TLSv1.2
5. Click Apply to save your settings. TLSv1.2 is now enabled.

6. Close the window.
Summary
The following is a summary of the steps for using SSReq. These steps are explained in detail in the following pages.
1. Launch SSReq.
2. Create a request.
3. Configure the server attributes (if changes required).
4. Save the request (optional, if you want to save the request without the response).
5. Submit the request.
6. View the status to confirm successful operation.
7. View the response.
8. View the call trace.
9.
9. Save the request (optional, if you want to save the request with the response).
SSReq saves files in XML format. XML files saved with a previous release of SSReq (version 6.0 or 5.1) can be opened in the current release
using File > Open menu option.
Steps
The SSReq applet and server are automatically installed and enabled during the SBC software installation or update process.
Follow these steps to create and send a request.
1. Login to EMA, and navigate to Troubleshoot > Policy Analysis - SSREQ, and from Policy Analysis window click Launch SSREQ.
GUI example
Create the request using the default file (recommended):
To create a Request using a previously saved file:
1. Select File | Open from the menu bar.

2. Enter the path/file name in the File name box or use the Browse window to locate the file and click Open.
a. Select File | New from the menu bar. The request fields are populated with default values.
b. Modify the request fields as required.
If a field does not have a Present check box, then it is mandatory and must be populated. For optional fields, select the Present
box to have the field sent in the request.
The following policy request fields are mandatory and must be populated with values or have an option selected:
Gateway
Source Trunk Group
Called Number (this is not mandatory for all scenarios. If it is mandatory and left blank, you will be prompted.
For policy request field descriptions, refer to Policy Request Fields.

c. If you want to send one or more trigger requests following the policy request, select the
first trigger request from the navigation panel.

d. Populate the trigger request fields in the details panel as required.
For trigger request field descriptions, refer to Trigger Request Fields.
e.
e. Repeat steps a. through c. for each trigger request desired, up to 5.
2. Configure the server attributes (if required).
Configure Server Attributes
The server attributes must be configured before you can run a simulated policy request. If they have been previously configured and the
target PSX is the same, you do not need to reconfigure them.
a. Select Configure | Server from the menu bar. The Configure Server Attributes dialog box appears.
Enter values in the fields as required. The fields are defined below.
Configure Server Attributes Values
Field Description
PSX The PSX hostname or IP address of which to test the configuration. If the hostname is not resolved to the
Hostname IP address, use the IP address instead or add an entry to the hosts file under the System32\Drivers\etc
or IP directory.
Address
NOTE: An IPv4 address or an IPv6 address can be used.
Port Number The port number at which the SSReq server is listening for the SSReq request. The default port is 3090
for UDP or 3091 for TCP.
Timeout (sec Number of seconds that the SSReq client will wait for a response from the specified server. The default is
onds) 5 seconds.
Transport The transport protocol used to communicate with SSReq Server, either UDP or TCP can be used. The
default is UDP.
b. Click the Accept button to accept the settings.
3.
3. Save the request (Optional, if you want to save the request without the response).
4. Submit the request.
Click Submit to send the request to the SBC.
5. View the status to confirm successful operation. Refer to Status Display.
6. View the response. Refer to Viewing a Response.
7. View the call trace.
The call trace panel displays call trace information for the specific simulated call. Call tracing is enabled by default. You can disable it in
the CallTrace field of the policy request. Each time a new call trace is received, the old trace is overwritten.
Call Trace information from the panel is saved in the same file as the policy request and response using the File, Save or Save As
menu. You can copy and paste the contents of the call trace pane into another application (such as a word processing application) to
create a log file for future reference, share the file, to find keywords, and for troubleshooting. Call trace information is not saved with the
policy request and response information.
8. Save the SSReq file (Optional).
If you modified an existing file or created a new one, you may save it using the Save or Save As menu option. If you modify the default
file and want to save it, you must save it using a different name. Ribbon recommends that you save the request for future reference. The
server configuration is saved as well. If you save the file after the policy response has been received, the response is saved in the same
file.
SSReq saves files in XML format. XML files saved with a previous release of SSReq (version 6.0 or 5.1) can be opened in the current release
using File > Open menu.
Note

Main Window
Menu Bar
File Menu
Configure Menu
Version Menu
Status Display
Navigation Panel
Detail Panel
Present Check Box
Button Panel
CallTrace Panel
Status Display Panel
Main Window
The SSREQ main window is shown below.
Fields with grayed out labels in the Detail Panel are not used in this release.
SSReq Main Window
Menu Bar
File Menu
New—Click New to load the default.xml file which contains sample values.
Open—Click Open to open the Open dialog box where you specify the file you want to load.
Save—Click Save to save the latest changes to the current file. If the default.xml file is the current file, the Save As dialog box opens
automatically to prevent you from overwriting the original file.
Save As—Click Save As to open the Save As dialog box where you name or rename the current file to be saved.
Set Default Directory—You can set a default directory for storing saved SSREQ data files (*.xml). When you click Save to save a file, or
Open to open a saved file, the default directory is accessed.
Properties—Click Properties to open a dialog box where you can specify a description for a file you want to save. When the file is
opened at a later date, the description may be helpful in understanding the purpose of the file.
Configure Menu
Server—Select Server to open the Configure Server Attributes dialog box which contains fields to specify the receiving PSX for
requests. The Server configuration is saved when the SSReq file is saved.
Configure Server Attributes Dialog
Version Menu
The version menu displays the SSReq GUI version number.
Navigation Panel
The navigation panel contains folders for the policy request and response, trigger requests and responses, download requests and responses,
and policy mid-call actions and responses.
Detail Panel
When you select an option from the navigation panel, the corresponding screens appear in the detail panel. For requests, this is where you input
the desired information to send in the request. For responses, this is where the response data appears.
Present Check Box

If a field has a Present check box, it is an optional field. You must check the Present check box to have the field included in the request.
Present checkbox
Button Panel
The Button panel includes three buttons:
Submit—Clicking the Submit button sends the current simulated request to the specified PSX.
Clear—Clicking the Clear button clears the request fields.
Clear Status Display—Clicking the Clear Status Display button clears the status display panel.
CallTrace Panel
The call trace panel displays call trace information for the specific simulated call. Call tracing is enabled by default. Each time a new, successful
call trace is received, the old contents are overwritten.
Status Display Panel

The status display panel shows the status of actions such as:
Opening an *.xml file

Submitting a request
Connecting to a server.
For details, refer to Status Display.
To simulate a download request using SSREQ, do the following:
1. Select "Script" from the DownloadRequest folder in the navigation panel.
2. In the "Script Name" field, enter the name of the script to download.
3. Click Submit.

Policy Mid Call Actions are part of PSX call processing for the Gateway Mobile Switching Center (GMSC) solution. The PSX generates Policy Mid
Call Actions during late call forwarding scenarios in mobile and AIN networks. For more information on the GMSC solution, see the PSX Product
Description document located at PSX Documentation.
When call redirection occurs due to a late call forwarding event (such as a no-answer condition in which a call is then forwarded to the subscriber's
voice mail), the Terminating VMSC (Visited Mobile Switching Center) sends the new redirection data (which includes the Forward To Number) to the
PSX. The PSX in turn sends the new redirection data to the SBC in a Mid Call Action. The SBC adds the new redirection data to the currently stored
data and passes the new data to the PSX in the subsequent policy request to route the call to the Forward To Number.
Policy Mid Call Actions are also used in PSX support for third-party application servers via XML- over-TCP, which involves the PSX SPAS (Sonus
PSX/Application Server) service.
If the simulated call involves Policy Mid Call Actions, check Present for PolicyMidCall in SSReq. SSReq will wait for the Policy Mid Call. If SSReq
receives the Policy Mid Call, SSReq displays it in the Policy Mid Call section and sends the subsequent Policy Request.
To simulate a Policy Mid Call Action using SSREQ, do the following:
1. From the Navigation Panel, click PolicyMidCall
2. Select the Present check box
If the call for which you have set up the corresponding policy request involves a Policy Mid Call Action, the response data will include sections for
Policy Mid Call Data and Policy Mid Call Info.
Policy Request Fields List

The following figure shows the expanded policy request menu in the navigation panel. For a list of all the fields with definitions, see table Policy
Request Field Descriptions.
Expanded Policy Request Menu
Policy Request Field Descriptions
The following table lists the policy request fields with a description of each field.
Policy Request Field Descriptions
Field Description
BASIC FIELDS:
Gateway The gateway associated with the simulated call's policy request. Gateway choices include:
(Mandator
y) GSX: used to simulate a circuit switched call.
SIP: used to simulate the second dip of a SIP (Session Initiation Protocol) call.
H.323: used to simulate the second dip of an H.323 call.
The gateway you choose does not need to physically exist. However, it must be listed in the Gateway table on the PSX to which you
are sending the simulated policy request.
CalledNu The number being called.

mber
CallingNu The number from which the call originates.

mber
CarrierCo The carrier code of the carrier from which the call is being routed. When ISUP signaling is used, the Carrier Code field is populated
de from the Carrier Information Parameter (CIP).
SrcTrunk The trunk group from which the call was received on the ingress trunk group.
Group
(Mandator
y)
ADVANCED FIELDS:
Additional The number of additional categories.

Categorie
sCount
Additional The additional category of the incoming call.

Category
BillingNu The billing number for the call. In ISUP terminology, this is referred to as the charge number.
mber
CalledUri The called URI for the call.
Includes information such as business group ID and line privileges for the calling business group.
CallingBu
sinessGro
up
CallingBu The calling business location.

sinessLoc
ation
CalledDire The called directory number for the call.

ctoryNum
ber
CalledINN The called intelligent network number for the call.

umber
CallingUri The calling URI for the call.
CallTrace Use this field to enable or disable call tracing. If call tracing is enabled, you must provide the Global Call ID. Call tracing is enabled
by default.
CarrierSel The carrier code selection method for the call. The data for this field is derived from the carrier selection parameter in ISUP signaling.
ection
Category Similar to OLIP (Originating Line Information Parameter).
CauseOfN The cause of no ID, which can be Invalid, Reserved, User Requested, Interactive with Other Service, or Coin Phone.
oId
ChosenCa The chosen carrier information for the call.

rrierInfo
Contractor This is a Japan-specific ISUP parameter which includes the telephone number for billing.
Number
Correlatio The correlation identifier.

n ID
CountryC In the CAS (Channel Associated Signaling) protocol, the country code is transmitted as a separate field. When a country code is
ode present and the signaling protocol is CAS, the country code is passed to the PSX in the Country Code field.
DestTG To simulate a SIP call received using global number format, specify the valid destination trunk groups that the PSX client would
provide to the PSX in the policy request from the SIP DTG parameter. The PSX skips most call processing, fetches routes, and
performs digit manipulation to convert SIP global numbers to numbers compatible with ISUP signaling, and then populates the route
attributes in the policy response.
Dialed The (unchanged) number that was dialed.

Number
DPC Info The customer-specific Destination Point Code details, including national ID, country ID, gateway ID, member status, and codes.
DstTGAttri The direction and bearer capability of the destination trunk group.
butes
ForwardC The ISUP signaling forward call indicator data. The PSX client populates this information from the ISUP Forward Call Indicator
allIndicato parameter.
rs
GenericAd This field maps to SS7 IAM Generic Address parameter to store information such as original redirecting number and redirecting
dress number.
GenericDi Generic digits used for Switch ID/Trunkgroup ID-based routing.

gits
GenericN The PSX client sends this generic name parameter in signaling message.
ame
GenericN Feature Group D delivery.

umber
HLC The Higher Layer Compatibility parameter value received in signaling for ISDN/ISUP interworking.
JTIParam Customer-specific parameters.

eters
Jurisdictio The jurisdiction information parameter. This parameter stores the NPA/ NXX assigned to the trunk or extracted from the calling party
nInfo number.
LIRoutingI Used to specify Lawful Intercept Routing details.
nfo
LLC The Lower Layer Compatibility parameter value received in signaling for ISDN/ISUP interworking.
LocationN The geographic position of the calling party. The format is country-specific, but is likely to be some longitude/latitude numeric
umber encoding.
MessageT The SIP message type for the call, which can be INVITE, NOTIFY, REGISTER, or SUBSCRIBE.
ype
Message The MWI state for a subscriber with MWI services (either MESSAGE_WAITING or NO_MESSAGE).
WaitingInd
icatorStat
e
Request
MoreRout Check this box to request the return of more than 10 routes.
esPolicyR
equest
NatureOf This is used to specify the following information for the call:
Connection
Continuity Check Indicator
Echo Control Device Indicator
Satellite Indicator
NetworkD The Partition ID and Network ID that is expected in the ingress IAM. The PSX uses the received NetworkData to map in the
ata database to the routing partition to which the carrier's customer belongs, used for routing international calls to and from the carrier's
customer network.
NFCI This parameter, National Forward Call Indicator, contains zoning indicator, charge indicator, and IN call indicator fields.
NonStand Non Standard Parameter represents any user- or network-specific ISUP parameter that is not in the standard protocol definition.
ardParam
eter
OriginalRe The original called number. Signifies information sent in a forward direction when a call is redirected more than once and identifies
directingN the original called party.
umber
Originatin This is a Japan-specific ISUP parameter. It includes the originating carrier code of the incoming call.
gCarrierInfo
Originatin The originating charge area for the call.

g
ChargeAr
ea
Originatin The SIP server or H.323 gateway from which the call originated.
gGateway
Info
Originatin The originating line type. This field is populated by the PSX client from the Originating Line Information Parameter in ISUP signaling.
gLineInfo
Originatin The ingress trunk group on the gateway that is the actual originator of the call or the name of the originating trunk group on the SIP
gTrunkGr server.
oup
PolicyIndi Specifies whether to download script data in the policy response. With GSX script caching, the PSX does not automatically send
cators script data in policy responses.
PortabilityI Specifies whether or not number portability information is included in the request (NP Status), and whether the Query on Release
nfo (QoR) is in the ingress message or the local exchange must perform the lookup (NPI Flags). This is for INAP use only.
Presentati This field includes the presentation number for the call.
onNumber
PriorityCal Indicates whether the subscriber is a priority caller.

lInfo
PublicPre Indicates the number type and number for a public presence directory number, if present.
senceDire
ctoryNum
ber
RedirectF This field includes the redirect forward information for the call.
orwardInfo
rmation
Redirectin Specifies a redirecting business group for the call.

gBusiness
Group
Redirectin Use to specify the number used instead of the called number to redirect the call. Signifies the information sent in the forward
gNumber direction indicating the number from which the call was last redirected.
Redirectio Provides the reason for redirecting the call.

nInfo
Redirectio This field includes the redirection capability parameter for the call.
nCapability
Redirectio Used to specify information sent in the backward direction indicating the number towards which the call must be rerouted or which
nNumber has been forwarded.
ScpCarrie The SCP carrier code; same as the carrier code in the basic request.
rCode
ScfID Specifies the Service Control Function identifier.
SipApplica For SIP call routing, specifies the IP address and port number of the SIP interface on which the call was received.
tionReceiv
eAddress
SipFromDi For SIP call routing, specified the From header display name.
splayName
SipFromH For SIP call routing, specifies the contents of the From header.
eader
SipPaiSip For SIP call routing, specifies the SIP P-Asserted-Identity SIP display name.
DisplayNa
me
SipPaiSip For SIP call routing, specifies the SIP P-Asserted-Identity SIP URI.
Uri
SipPaiTel For SIP call routing, specifies the SIP P-Asserted-Identity Tel display name.
DisplayNa
me
SIP P- This field contains the SIP P-Charging-Vector parameter for the call.
ChargingV
ector
TimeStam The time at which the simulated call was placed.

p
(Mandator
y)
TransitCar The transit carrier information to use for the call.

rierInfo
TransitNet The transit network selection detail.

workSelec
tion
Translated Number of translations on a per-route basis.

Number
Universal Contains a universally unique call identifier (ID) comprised of the node ID (a number identifying the switch), a boot count (the
CallData number of reboots on the switch), and a Call ID. This parameter is encoded as a string containing a hexadecimal representation of
the data and is used as the Session ID between the PSX and MAP Server.
Imposes different levels of outgoing call restrictions. Not used in this release.
UserContr
olledOutg
oingCallR
estriction
UserServi Specifies the User Service Information parameter value received in signaling for ISDN/ISUP interworking.
ceInfo
XCorellati A customer-specific parameter for a call involving the PSX SPAS service.
onID
VisitorMA Specifies the Visitor MA (Message Area) parameter value, which is a customer-specific Japan ISUP extension parameter for routing
calls in a mobile network.
ZZCode This is used in CAS signaling.
The table below describes the fields available in a trigger request:
Trigger Request Field Descriptions
Field Description
Present If checked, this trigger request will be sent to the SBC.
If the trigger response is successful the next trigger request is processed (if it's Present check box is selected). If the Present check
box is not checked, subsequent trigger requests will not be sent to the SBC.
Routes If checked, specifies that routes are required for this trigger request.
Required
Notification If checked, EDP notification operation will be performed, otherwise the EDP request operation will be performed.
Mid Call If checked, specifies that this is a mid call trigger request.
Trigger
Operation Operation Type of the operation requested.
Authcode The Authcode Group ID.

Group
Variables Identifies the variables and their type to be used in this trigger request.
Result Expected result of the trigger request.
Gateway Identifies the name, family, port number, and IP address of the gateway associated with the simulated call's policy request.
Profile
Triggering Specifies the triggering number and related attributes.

Number
Called Specifies the called directory number.

Directory
Number
Call Specifies the call information report.

Informatio
n Report
Carrier Specifies the carrier code.

Code
Correlation Specifies the correlation ID.

Id
Scp Specifies the SCP carrier code; this is the same as the basic carrier code.
Carrier
Code
Specifies the chosen carrier information.
Chosen
Carrier
Info
HLC Specifies the Higher Layer Compatibility parameter value received in signaling for ISDN/ISUP interworking.
Jurisdictio Specifies the jurisdiction information parameter. Stores the NPA/NXX assigned to the trunk or extracted from the calling party
n number.
Information
LLC Specifies the Lower Layer Compatibility parameter value received in signaling for ISDN/ISUP interworking.
Nature of This is used to specify the following information for the call:
Connection
Satellite Indicator
Originating This is a Japan-specific ISUP parameter. It includes the originating carrier code of the incoming call.
Carrier
Information
Originating Specifies the originating carrier of the call.

Carrier
Information
Portability Specifies whether or not number portability information is included in the request (NP Status), and whether the Query on Release
Info (QoR) is in the ingress message or the local exchange must perform the lookup (NPI Flags). This is for INAP use only.
Presentati Specifies the presentation number.

on Number
Called IN Specifies the called IN number.

Number
Dialed Specifies the original dialed number.

Number
Redirect Specifies the redirect forward information.

Forward
Information
Redirectio Specifies the redirection capability.

n
Capability
Scf ID Specifies the SCF (Service Control Function) identifier.
P- Specifies the P-Charging-Vector.

Charging
Vector
Source Specifies the source trunk group for the call.

Trunkgroup
Transit Specifies the transit carrier information for the call.

Carrier
Info
Trunkgrou Specifies the trunk group attributes.

p
Attributes
UniversalC Contains a universally unique call identifier (ID) comprised of the node ID (a number identifying the switch), a boot count (the
allData number of reboots on the switch), and a Call ID. This parameter is encoded as a string containing a hexadecimal representation of
the data.
Status Display
When a policy request is submitted, the status is reported in the status display panel at the bottom of the screen. See "Main Window" section on page
SSReq User Interface for the location of the status display panel.
Successful Request
A successful request is indicated by the following lines in the status display panel:
SSREQ Client sent Request Sent Register Request to PSX Registration for <gateway> succeeded
Received port <port no.> for sending requests
Sent Policy Request to PSX
SSREQ Client received Policy Response Script returned <script name> Routes returned <no. of routes>
SSREQ Client received Call Trace
Sent Trigger Request to PSX
SSREQ Client received Trigger Response <trigger response no.> Script returned <script name>
Routes returned <no. of routes> SSREQ Client received Call Trace
Sent Download Request to PSX
Script returned <script name> Sent Unregister Request to PSX
The script and routes returned information also appears if there is no script or if there are no routes configured. The information indicates 0.
The routes folder under policy/trigger response appears when the number of routes returned is more than zero. The routes are indexed by trunk
group and gateway. By expanding the routes folder, per-route fields can be viewed.
Unsuccessful Request
A request that does not result in a response will be indicated by one of the following lines in the status display:
Error: SSREQ Server not responding

Error: Unknown PSX Hostname or IP Address <hostname/IP Address> Error: Unable to connect to TCP socket at <server>:
<port>
Error: Unable to read message from TCP socket connected to
<server>:<port>
Error: Unable to send message over UDP to <server>:<port> Error: Registration for <gateway> failed
Error: Registration attempt from unknown gateway <gateway> Error: Failed decoding the Request
Error: SSREQ Server and Client version incompatible - Server: <X> Client: <Y>
Error: Invalid Port Number - <port number> Error: Invalid Timeout - <timeout>
For details on these status messages, refer to SSReq Troubleshooting page.
Viewing a Response
After successfully submitting a request, you can view the response data in the details panel. The fields in the response are view-only and cannot be
edited.
This procedure assumes you have just sent a request or you have opened a saved response.
To view a response, do the following:
1. Click on either the Policy, Trigger, Download, or MidCallPolicy Response folder. The corresponding fields appear in the detail panel
populated with the response data. You can scroll through the fields or select a specific field from the list in the navigation panel.
2. To view a specific field, select the desired field from the navigation panel. The corresponding field appears in the details panel with the text in
bold.
Example:
The figure below shows the Routes directory expanded to show the list of the 10 returned routes. The Routes field also appears at the top of the
details panel. To view the response details for a particular route, click on the route in the navigation panel.
Response Screen
For definitions of each field in the response, see Response Field Descriptions page.

In this section:
Response Fields
Routes Directory Field Descriptions
Policy Mid Call Action Response Fields
Mid Call Info Fields
Response Fields
The following table defines the response fields returned for policy and trigger requests.
Response Fields
Response Description
Routes The number of routes returned.
AIN Flags Optional parameters returned in Send-to-Resource message.
AmaBafModu Automatic Message Accounting modules in Telcordia AMA format.

le
AmaSlpId Identifies a service or a unique subset of service functionality.
BillingData This is the billing information for this call. Includes information such as carrier origin, cluster ID, trunk ID, and so on.
BillingIndicat Billing indicators are used to pass billing information to the SBC client so it can add the information to the accounting record.
ors
BusinessGro This is the business group billing information for the call.
upBillingInfo
CalledBusine Returns information such as business group ID and line privileges for the called business group.
ssGroup
CallInfo Conveys information that the trigger response belongs to the new leg of the call.
CallInformati This is the call information request for the call.

onRequest
CallingBusine Returns information such as business group ID and line privileges for the calling business group.
ssGroup
CallingNumb Returns the charge area for the calling number.

erChargeArea
CallType The type of call, such as National, International, etc.
ConvertOlec Signal to GSX to convert the OLEC carrier code.

CarrierCode
DPCInfo Destination Point Code Information parameter, based on called party number and gateway name.
JTIParameters Specifies customer-specific identification parameters.
CountryCode In the CAS (Channel Associated Signaling) protocol, the country code is transmitted as a separate field. When a country
code is present and the signaling protocol is CAS, the country code is passed to the SBC in the Country Code field.
ForwardCallI This specifies how the carrier code was specified for the call. The data for this field is derived from the carrier selection
ndicators parameter in ISUP signaling.
GenericName The SBC client should send the generic name parameter in the signaling.
IngressIPPar Returns ingress IP signaling parameters and header extensions.

ameters
IngressMedia The SBC Tone and Announcement Profile used in the call.
Profile
IngressPara Attributes associated with the ingress trunk group, such as the ATP Supported attribute.
meterFlags
IngressSwitch The switch on which the call came in.
IngressTrunk The trunk group on which the call came in.

Group
Lata This specifies the local access and transport area of the carrier.
LICriteriaInfo Displays the Lawful Intercept criteria sent back by the SBC.
MidCallData Data containing redirection information related to Policy Mid Call Actions. For calls in GSM networks, the SBC may send
Policy Mid Call Actions to its clients during late call forwarding scenarios in which call redirections occur. For details, see the
section "Policy Mid Call Action Fields" on page 1-20.
MoreRoutesI Specifies more routes availability information.

nfo
NetworkData On a per-route basis, includes information specifying whether to generate, propagate, or suppress the Partition ID and
Network ID in the egress IAM.
OriginalRedir The call type of the original redirecting number.

ectingNumbe
rCallType
OriginatingGa The SIP server or H.323 gateway from which the call originated.
tewayInfo
OverlapDialing Includes values provisioned on the SBC for overlap dialing, such as the minimum digits for routing a call, the minimum digits
for a valid phone number, and the maximum digits for a valid phone number.
OwnCarrierIn This is a specific ISUP parameter. It includes the originating carrier code of the incoming call.
fo
PacketProfile Indicates the settings in the Packet Service Profile used.
PartialCli The partial CLI is passed down to the SBC client whenever the SBC does not receive a calling number in the policy request.
PortabilityInfo Indicates whether or not number portability information is included in the response (NP Status), and whether the Query on
Release (QoR) is received in the ingress message or the local exchange must perform the lookup (NPI Flags). This is for
INAP use only.
Provider The partition ID of the carrier or service provider.
SBCCongesti The current SBC CPU congestion level, including the allowed calls per total calls for the level.
on
RedirectBack The redirect backward information for the call.

wardInformati
on
RedirectionIn Provides the reason for the redirecting the call.

fo
RouteTable The routing label.
ScpCarrierCo The carrier code returned by the SCP, if available.

de
Script The script returned for execution on the SBC client.
SrcCarrierTy Describes how a carrier was chosen for routing the call.
pe
SrcTGConfig Information about the source trunk group.

uration
TranslationS The translation source number for the call.

ourceNumber
Variables In the policy response, the runtime variables will be populated here.
XCorrelationID A customer-specific parameter for a call involving the SBC SPAS service
VisitorMA The Visitor MA (Message Area) parameter, which is a customer- specific Japan ISUP extension parameter for routing calls in
a mobile network.

The following table defines the response fields in a Routes directory.
Field Description
BillingNumber This specifies the billing number for the call. In ISUP terminology, this is referred to as the charge number.
CalledDirectory The directory number being called.

Number
CalledNumber The number being called.
CalledNumberC This field contains the charge area for the called number.
hargeArea
CalledUri This field contains the called URI.
CallIndicators This specifies the charge band information.
CallingNumber The number from which the call originates.
CallingUri This field contains the calling URI for the call.
CarrierCode The carrier code of the carrier from which the call is being routed. When ISUP signaling is used, the Carrier Code field is
populated from the Carrier Information Parameter (CIP).
CarrierSelection This specifies how the carrier code was specified for the call. The data for this field is derived from the carrier selection
parameter in ISUP signaling.
CarrierType Describes how a carrier was chosen for routing the call.
ContractorNumb This is a Japan-specific ISUP parameter. This parameter includes the telephone number for billing.
er
DestSigAttributes Indicates the peer address, packet profile, and IP parameters for the egress leg of a call on an IP trunk group.
DstTGAttributes Indicates the direction and bearer capability of the destination trunk group.
EgressCarrierInfo This is a specific ISUP parameter. It includes the destination carrier code of the outgoing call.
EgressMediaPro The SBC Tone and Announcement Profile selected for the route.
file
EgressParamet Attributes associated with the egress trunk group, such as the ATP Supported attribute.
erFlags
EgressSwitch The egress switch on which the call went out.
EgressTrunkGro The egress trunk group on which the call went out.
up
GatewayAddress The family, port number, and IP address of the gateway associated with the simulated call's policy request.
GatewayName Name of the gateway associated with the simulated call's policy request.
GenericAddress These fields map to SS7 IAM Generic Address parameters to store information such as original redirecting number and
redirecting number.
GenericDigits Used for Switch ID/Trunkgroup ID-based routing.
GenericNumber Used to specify Feature Group D delivery.
IPParameters Returns ingress IP signaling parameters and header extensions.
JTIParameters Contains customer-specific parameters.
JurisdictionInfo Specifies the jurisdiction information parameter. Stores the NPA/ NXX assigned to the trunk or extracted from the calling
party number.
LocalRingBackT This indicates the settings used in the local ring back tone profile.
one
LocationNumber Used to indicate the geographic position of the calling party. The format is country specific, but is likely to be some
longitude/latitude numeric encoding.
NatureOfConne This is used to specify the following information for the call:
ction
Satellite Indicator
NonStandardPa Represents any user or network specific ISUP parameter which is not in the standard protocol definition.
rameterStr
OriginatingLineI This specifies the originating line type. This field is populated by the SBC client from the Originating Line Information
nfo Parameter in ISUP signaling.
OriginalRedirecti This is used to specify the original called number. Signifies information sent in a forward direction when a call is redirected
ngNumber more than once and identifies the original called party.
OutpulseDigits The outpulse digits from an SCP.
PacketProfile Indicates the settings used in the Packet Service Profile.
PartialCLI The partial CLI is passed down to the SBC client whenever the SBC does not receive a calling number in the policy
request.
PresentationNu The presentation number for the call.

mber
RedirectForward The redirect forward information for the call.

Information
RedirectionCap The redirection capability for the call.

ability
RedirectionNum Used to specify information sent in the backward direction indicating the number towards which the call must be rerouted
ber or which has been forwarded.
RedirectingNum Use to specify the number used instead of the called number to redirect the call. Signifies the information sent in the
ber forward direction indicating the number from which the call was last redirected.
RouteType Identifies the type of route, for example H.323 gateway.
SipFromDisplay This field contains the SIP From header display name.
Name
SipFromHeader This field contains the contents of the SIP From header.
SipToHeader Identifies the SIP To header, which specifies the desired "logical" recipient of the request, or the address-of-record of the
user or resource that is the target of this request.
SipPaiSipDispla The SIP P-Asserted-Identity SIP display name.

yName
SipPaiSipUri The SIP P-Asserted-Identity SIP URI.
SIP The SIP P-Asserted-Identity Tel display name.

PaiTelDisplayNa
me
TrafficControl Used to specify the type of traffic control applied and congestion level.
TransitNetworkS This specifies the transit network selection.

election
Translated Number of translations on a per-route basis.
TrunkGroup The trunk group from which the call was received on the ingress trunk group.
ZoneIndex This specifies a unique number in which SIP servers and H.323 gateways can reside and retain unique IP addresses.
ZZCode This is used in CAS signaling.
Policy Mid Call Action Response Fields

The following table describes the Mid Call Action fields.
Mid Call Action Fields
Field Description
Present When checked, indicates the presence of Mid Call Data.
Redirection Count Number of redirections encountered by the SBC.
Mid Call Info Count Number of elements in the Mid Call Info array.
Billing Info Billing data for the call.
Context Contains the redirection data the SBC will use to populate the
Billing
Information when the subsequent policy request is populated.
Mid Call Info See the Table 4 for details.

The following table describes the Mid Call Info fields.
Field Description
Present When checked, indicates the presence of Mid Call Info.
Msg Op Information indicating the type of redirection, which can be IS-41 or GSM.
Action Information indicating how the SBC client should process the Mid Call. For example, drop the egress leg and send a new
policy request.
Digits Contains the redirected to number.
Carrier Contains the new Carrier Code.
Redirection Info Contains the redirection reason.
Redirecting Contains the redirecting number, which is the number that is forwarding the call.
Number
The following table contains information on error messages and common problems encountered with SSReq.
Common Problems and Error Messages Generated by SSReq
Error Message Description/Resolution
Error: SSREQ Server <server>: Problem:

<port> not responding The client could not communicate with the SSReq server.
Error: Unknown PSX Hostname or Resolution:

IP Address <hostname/IP
Address> Ensure the host name and port number in the Configure Server Attributes dialog box is correct. If the
name is correct, try using the IP address of the specified server instead of the host name in the PSX
Error: Unable to connect to TCP Hostname or IP Address text box.
socket at <server>:<port> Verify that the SSReq server is running. If it is, try increasing the timeout value specified in the
Configure Server Attributes dialog box.
Error: Unable to read message
from TCP socket connected to Verify that the combination of the Port and TCP/ UDP is correct. That is, verify that the port number
<server>:<port> corresponding to TCP is used when you select TCP; or verify that the port number corresponding to
UDP is used when you select UDP.
Error: Unable to send message Eliminate any network issues.
over UDP to <server>:<port>
Error: Registration for <gateway> Problem:

failed The gateway could not be registered with the PSX. Resolutions
Error: Registration attempt from Resolution:

unknown gateway <gateway>
Check for a spelling error in the gateway name you specified.
Make sure the gateway is provisioned on the designated PSX.
Error: Failed decoding the Request Problem:

The request from the SSReq client could not be decoded by the server because the XML format is incorrect.
Resolution:
Probably due to a network or transmission error, the server did not receive the complete packet, or the
generated or edited request is not valid XML.
Error: SSREQ Server and Client Problem:

version incompatible - Server: You are not using the same version of the SSReq server and client. <X> and <Y> indicate the respective
<X> Client: <Y> version numbers.
Resolution:
Use the same version of SSReq client and server.
Error: Invalid Port Number - <port Problem:

number> The port number is either invalid or unspecified.
Resolution:
Check the port number in the Configure Server Attributes dialog box.
Error: Invalid Timeout - <timeout> Problem:

The timeout is either invalid or unspecified.
Resolution:
Check the timeout in the Configure Server Attributes dialog box.

550-08889 05.01 SBC Core 11.01.00R000 Alarms and Troubleshooting

Uploaded by

Copyright:

Available Formats

550-08889 05.01 SBC Core 11.01.00R000 Alarms and Troubleshooting

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

550-08889 05.01 SBC Core 11.01.00R000 Alarms and Troubleshooting

Uploaded by

Copyright:

Available Formats

SBC Core

Alarms and Troubleshooting Guide

Disclaimer and Restrictions

Compliance with Applicable Laws and Export Control Laws

SBC Alarm Details

New and Deprecated Alarms

Overview Alarm Field Definitions

You can configure up to 32 trap targets on the SBC.

The SBC displays alarms according to the following categories:

% show table alarms currentStatus

Current alarms (displayed in CLI mode)

To display the Current alarms using EMA,

> show table alarms historyStatus

The output is displayed similar to the figure below:

History alarms output.

Current Alarms - All > Alarms > Current Status

SNMP Trap Definition

To configure trapTarget using CLI: How to Configure SNMP Trap Targets

To view the the related alarms, type the command:

show table alarms currentStatus

To view trap configuration details, refer to

CLI: SNMP - CLI

Category SBC Core Traps

Call Processor sonusCpCdrServerNewXferPendingNotification

Policy Server sonusPolicyServerCallProcessTimeHighThresholdNotification

System Security sonusSystemSecurityAccountConfigChange

Alarm Field Definitions

Severity Mapping Rules

Registering/Configuring Insight SNMP Network Management Station for SBC

You can configure up to 32 trap targets on the SBC.

The following command is executed in CLI to configure the SNMP traps:

Registering/Configuring Insight SNMP Network Management Station for SBC

1. Log into the InsightTM Web-based Element Management System.

Register SBC EMS

SBC EMS Registration

Creating a View in EMA

2. Select the Views tab.

1. Select Real-Time tab from the Fault Manager window.

1. Select the trap to be cleared.

Select alarm to clear

Generic SNMP Trap Support

Generic SNMP Trap Conditions

Action Identify the offending source.

Impact Results in a temporary loss of trapping capability.

ifOperStatus—The current operational state of the interface:

Imp Network connectivity is lost for the interface specified.

Cle Automatic; linkUp

ifOperStatus—The current operational state of the interface:

Act None required.

Imp Network connectivity is restored for the interface specified.

Cle Automatic; clears in 2 minutes.

Critical Alarms List

All alarm types can be manually cleared.

Viewing the Current Alarms

2. Click Edit Alarm to edit the selected alarm.

3. Select the Cleared radio button.

For more information, refer to Dashboard - Alarms.

Viewing the Cleared Alarms

For more information on cleared alarms, refer to Dashboard - Alarms.