Cisco BroadWorks

Network Function Manager Fault and Alarm

Interface Specification
Notification
The BroadSoft BroadWorks has been renamed to Cisco BroadWorks. Beginning in September 2018, you
will begin to see the Cisco name and company logo, along with the new product name on the software,
documentation, and packaging. During this transition process, you may see both BroadSoft and Cisco
brands and former product names. These products meet the same high standards and quality that both
BroadSoft and Cisco are known for in the industry.

Copyright Notice
Copyright© 2020 Cisco Systems, Inc. All rights reserved.

Trademarks
Any product names mentioned in this document may be trademarks or registered trademarks of Cisco or
their respective companies and are hereby acknowledged.

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 2
Document Revision History

Release Reason for Change Date Author

2017.11_1.010 Created document with 2017.11_1.010 build. November 10, 2017 Yves Racine

2017.11_1.010 Verified content and published document. November 10, 2017 Margot Hovey-Ritter

2018.12_1.120 Updated content for Release 2018.12_1.120 December 18, 2018 Yves Racine
build.

2018.12_1.120 Validated content and published document. December 20, 2018 Margot Hovey-Ritter

2019.03_1.170 Completed rebranding for Cisco. March 21, 2019 Yves Racine

2019.03_1.170 Validated changes and published document. March 25, 2019 Margot Hovey-Ritter

2019.05_1.280 Updated content for Release 2019.05_1.280 May 30, 2019 Yves Racine
build.

2019.05_1.280 Validated changes and published document. May 30, 2019 Margot Hovey-Ritter

2020.04_1.200 Updated content for Release 2020.04_1.200 April 20, 2020 Yves Racine
build.

2020.04_1.200 Validated changes and published document. April 22, 2020 Margot Hovey-Ritter

2020.05_1.250 Updated content with Release 2020.05_1.250 May 27, 2020 Yves Racine
build.

2020.05_1.250 Validated changes and published document. May 27, 2020 Margot Hovey-Ritter

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 3
Table of Contents

Document Revision History.............................................................................................................3

1 History of Changes to the Cisco BroadWorks Fault MIBs......................................................11
1.1 Changes from Release 2020.04_1.200 to Release 2020.05_1.250.......................................................... 11
1.1.1 Added Faults........................................................................................................................................ 11
1.1.2 Moved Faults........................................................................................................................................11
1.1.3 Deprecated or Obsoleted Faults..........................................................................................................11
1.1.4 Removed Faults................................................................................................................................... 11
1.2 Changes from Release 2020.01_1.160 to Release 2020.04_1.200.......................................................... 11
1.2.1 Added Faults........................................................................................................................................ 11
1.2.2 Moved Faults........................................................................................................................................12
1.2.3 Deprecated or Obsoleted Faults..........................................................................................................12
1.2.4 Removed Faults................................................................................................................................... 12
1.3 Changes from Release 2019.12_1.050 to Release 2020.01_1.160.......................................................... 12
1.3.1 Added Faults........................................................................................................................................ 12
1.3.2 Moved Faults........................................................................................................................................12
1.3.3 Deprecated or Obsoleted Faults..........................................................................................................12
1.3.4 Removed Faults................................................................................................................................... 12
1.4 Changes from Release 2019.09_1.180 to Release 2019.12_1.050.......................................................... 12
1.4.1 Added Faults........................................................................................................................................ 13
1.4.2 Moved Faults........................................................................................................................................13
1.4.3 Deprecated or Obsoleted Faults..........................................................................................................13
1.4.4 Removed Faults................................................................................................................................... 13
1.5 Changes from Release 2019.08_1.230 to Release 2019.09_1.180.......................................................... 13
1.5.1 Added Faults........................................................................................................................................ 13
1.5.2 Moved Faults........................................................................................................................................13
1.5.3 Deprecated or Obsoleted Faults..........................................................................................................13
1.5.4 Removed Faults................................................................................................................................... 13
1.6 Changes from Release 2019.06_1.310 to Release 2019.08_1.230.......................................................... 13
1.6.1 Added Faults........................................................................................................................................ 14
1.6.2 Moved Faults........................................................................................................................................14
1.6.3 Deprecated or Obsoleted Faults..........................................................................................................14
1.6.4 Removed Faults................................................................................................................................... 14
1.7 Changes from Release 2019.05_1.280 to Release 2019.06_1.310.......................................................... 14
1.7.1 Added Faults........................................................................................................................................ 14
1.7.2 Moved Faults........................................................................................................................................14
1.7.3 Deprecated or Obsoleted Faults..........................................................................................................14
1.7.4 Removed Faults................................................................................................................................... 14
1.8 Changes from Release 2019.04_1.230 to Release 2019.05_1.280.......................................................... 14
1.8.1 Added Faults........................................................................................................................................ 15
1.8.2 Moved Faults........................................................................................................................................15
1.8.3 Deprecated or Obsoleted Faults..........................................................................................................15
1.8.4 Removed Faults................................................................................................................................... 15
1.9 Changes from Release 2019.03_1.170 to Release 2019.04_1.230.......................................................... 15
1.9.1 Added Faults........................................................................................................................................ 15
1.9.2 Moved Faults........................................................................................................................................15
1.9.3 Deprecated or Obsoleted Faults..........................................................................................................15
1.9.4 Removed Faults................................................................................................................................... 15
1.10 Changes from Release 2019.01_1.283 to Release 2019.03_1.170........................................................ 16
1.10.1 Added Faults...................................................................................................................................... 16
1.10.2 Moved Faults......................................................................................................................................16
1.10.3 Deprecated or Obsoleted Faults........................................................................................................16
1.10.4 Removed Faults................................................................................................................................. 16
1.11 Changes from Release 2018.12_1.120 to Release 2019.01_1.283........................................................ 16

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 4
 1.11.1 Added Faults...................................................................................................................................... 16
1.11.2 Moved Faults......................................................................................................................................16
1.11.3 Deprecated or Obsoleted Faults........................................................................................................16
1.11.4 Removed Faults................................................................................................................................. 16
1.12 Changes from Release 2018.05_1.230 to Release 2018.12_1.120........................................................ 17
1.12.1 Added Faults...................................................................................................................................... 17
1.12.2 Moved Faults......................................................................................................................................17
1.12.3 Deprecated or Obsoleted Faults........................................................................................................17
1.12.4 Removed Faults................................................................................................................................. 17
1.13 Changes from Release 2018.02_1.250 to Release 2018.05_1.230........................................................ 17
1.13.1 Added Faults...................................................................................................................................... 17
1.13.2 Moved Faults......................................................................................................................................17
1.13.3 Deprecated or Obsoleted Faults........................................................................................................18
1.13.4 Removed Faults................................................................................................................................. 18
1.14 Changes from Release 2017.12_1.010 to Release 2018.02_1.250........................................................ 18
1.14.1 Added Faults...................................................................................................................................... 18
1.14.2 Moved Faults......................................................................................................................................18
1.14.3 Deprecated or Obsoleted Faults........................................................................................................18
1.14.4 Removed Faults................................................................................................................................. 18
1.15 Changes from Release 2017.11_1.010 to Release 2017.12_1.010........................................................ 18
1.15.1 Added Faults...................................................................................................................................... 18
1.15.2 Moved Faults......................................................................................................................................18
1.15.3 Deprecated or Obsoleted Faults........................................................................................................19
1.15.4 Removed Faults................................................................................................................................. 19
1.16 Changes from Release 22.0 to Release 2017.11_1.010.........................................................................19
1.16.1 Added Faults...................................................................................................................................... 19
1.16.2 Moved Faults......................................................................................................................................19
1.16.3 Deprecated or Obsoleted Faults........................................................................................................19
1.16.4 Removed Faults................................................................................................................................. 19
1.17 Changes from Release 21.0 to Release 22.0......................................................................................... 19
1.17.1 Added Faults...................................................................................................................................... 20
1.17.2 Moved Faults......................................................................................................................................22
1.17.3 Deprecated or Obsoleted Faults........................................................................................................22
1.17.4 Removed Faults................................................................................................................................. 22
1.18 Server Introduction in Release 21.0........................................................................................................ 22
2 Introduction.................................................................................................................................. 23
3 SNMP Agent Configuration........................................................................................................ 24
3.1 SNMP Agent Configuration........................................................................................................................ 24
3.2 Configuration SNMP V2c Access List....................................................................................................... 24
3.3 SNMP Trap Managers............................................................................................................................... 25
3.4 SNMP v3 Access Control.......................................................................................................................... 25
3.5 SNMP v3 Users......................................................................................................................................... 27
3.6 Reporting.................................................................................................................................................... 27
4 Cisco BroadWorks Faults.......................................................................................................... 28
4.1 Fault Template........................................................................................................................................... 28
4.2 Notifications and Alarms............................................................................................................................ 28
4.3 Alarm Correlation....................................................................................................................................... 29
4.3.1 Example............................................................................................................................................... 30
4.3.2 High Availability SNMP Alarms............................................................................................................31
4.3.3 Notifications Parameterization............................................................................................................. 35
5 External Subagents Integration................................................................................................. 37
5.1 High-level Description................................................................................................................................ 37
5.2 Integrated Third-Party Subagents.............................................................................................................. 37
6 Fault Thresholding and Suppression........................................................................................38

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 5
 6.1 Trap Lists................................................................................................................................................... 38
6.2 Trap Filters................................................................................................................................................. 39
6.3 Filtering Considerations..............................................................................................................................41
6.4 Filtered Faults Notification......................................................................................................................... 42
6.5 Provisioning Fault Filters............................................................................................................................42
6.5.1 SNMP Provisioning.............................................................................................................................. 42
6.5.2 CLI Provisioning................................................................................................................................... 42
7 Organization of Cisco BroadWorks MIB Files......................................................................... 44
7.1 MIB files for the Network Function Manager............................................................................................. 44
8 Cisco BroadWorks MIB Files..................................................................................................... 45
8.1 BroadworksConfigurationFault MIB............................................................................................................45
8.1.1 SNMP Traps For Component: processmonitor................................................................................... 45
8.1.2 SNMP Traps For Component: configd................................................................................................ 46
8.2 BroadworksFault MIB................................................................................................................................. 47
8.2.1 SNMP Traps For Component: unspecified..........................................................................................48
8.2.2 SNMP Traps For Component: processmonitor................................................................................... 50
8.2.3 SNMP Traps For Component: database............................................................................................. 56
8.2.4 SNMP Traps For Component: sip....................................................................................................... 59
8.2.5 SNMP Traps For Component: mgcp................................................................................................... 63
8.2.6 SNMP Traps For Component: smtp.................................................................................................... 63
8.2.7 SNMP Traps For Component: filesystem............................................................................................ 64
8.2.8 SNMP Traps For Component: callp.................................................................................................... 65
8.2.9 SNMP Traps For Component: nssynch...............................................................................................68
8.2.10 SNMP Traps For Component: smap................................................................................................. 69
8.2.11 SNMP Traps For Component: accounting.........................................................................................70
8.2.12 SNMP Traps For Component: licensing............................................................................................ 70
8.2.13 SNMP Traps For Component: pmReporting..................................................................................... 72
8.2.14 SNMP Traps For Component: smdi.................................................................................................. 72
8.2.15 SNMP Traps For Component: cpeDeviceManagement.....................................................................74
8.2.16 SNMP Traps For Component: networkDeviceManagement..............................................................75
8.2.17 SNMP Traps For Component: cap.................................................................................................... 75
8.2.18 SNMP Traps For Component: ociReporting......................................................................................75
8.2.19 SNMP Traps For Component: bcct................................................................................................... 76
8.2.20 SNMP Traps For Component: taskMonitor....................................................................................... 77
8.2.21 SNMP Traps For Component: logging.............................................................................................. 78
8.2.22 SNMP Traps For Component: dns.................................................................................................... 79
8.2.23 SNMP Traps For Component: snmpAgent........................................................................................80
8.2.24 SNMP Traps For Component: xsp.................................................................................................... 80
8.2.25 SNMP Traps For Component: ps...................................................................................................... 81
8.2.26 SNMP Traps For Component: softwareManager.............................................................................. 81
8.2.27 SNMP Traps For Component: security..............................................................................................82
8.2.28 SNMP Traps For Component: webcontainer.....................................................................................84
8.2.29 SNMP Traps For Component: sccp.................................................................................................. 85
8.2.30 SNMP Traps For Component: jvmProcess....................................................................................... 85
8.2.31 SNMP Traps For Component: time................................................................................................... 87
8.2.32 SNMP Traps For Component: webrtc............................................................................................... 87
8.2.33 SNMP Traps For Component: sipLocation........................................................................................87
8.2.34 SNMP Traps For Component: threshold........................................................................................... 87
8.2.35 SNMP Traps For Component: nps.................................................................................................... 88
8.2.36 SNMP Traps For Component: hazelcastClient..................................................................................89
8.3 BW-FileTransferFault MIB..........................................................................................................................89
8.3.1 SNMP Traps For Component: fileRepos............................................................................................. 89
8.4 BW-LicenseControllerFault MIB................................................................................................................. 90
8.4.1 SNMP Traps For Component: processmonitor................................................................................... 90
8.4.2 SNMP Traps For Component: licenseController................................................................................. 92

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 6
 8.5 BW-LicenseManagerFault MIB...................................................................................................................94
8.5.1 SNMP Traps For Component: processmonitor................................................................................... 94
8.5.2 SNMP Traps For Component: licensing.............................................................................................. 96
8.6 BW-MDBManagementFault MIB................................................................................................................ 98
8.6.1 SNMP Traps For Component: processmonitor................................................................................... 98
8.6.2 SNMP Traps For Component: database........................................................................................... 100
8.7 BW-NetworkMonitoringFault MIB............................................................................................................. 101
8.7.1 SNMP Traps For Component: processmonitor..................................................................................101
8.7.2 SNMP Traps For Component: networkMonitoring.............................................................................104
8.8 BW-NodeControllerFault MIB................................................................................................................... 105
8.8.1 SNMP Traps For Component: processmonitor..................................................................................105
8.8.2 SNMP Traps For Component: nodeController...................................................................................107
8.9 BW-NodeLifecycleManagerFault MIB...................................................................................................... 108
8.9.1 SNMP Traps For Component: processmonitor..................................................................................109
8.10 BW-SoftwareManagementFault MIB...................................................................................................... 111
8.10.1 SNMP Traps For Component: processmonitor................................................................................111
8.10.2 SNMP Traps For Component: softwareManagement......................................................................113
8.11 BW-WebContainerFault MIB.................................................................................................................. 115
8.11.1 SNMP Traps For Component: webcontainer...................................................................................115
Appendix A: 9 Additional Information........................................................................................119
9.1 Fault Parameters......................................................................................................................................119
Appendix B: 10 bwSystemHealthReport Alarm Problem Text.................................................155

Acronyms and Abbreviations......................................................................................................160

Index............................................................................................................................................... 162

References..................................................................................................................................... 165
References to Feature Description Documents............................................................................................. 165

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 7
List of Figures

Figure 1: Views................................................................................................................................................. 26
Figure 2: Visual Representation of Notification during Lifetime of Monitored Device....................................... 29
Figure 3: Visual Representation of Alarm during Lifetime of Monitored Device............................................... 29
Figure 4: Visual Representation of Multiple Instances of Same Alarm being Raised.......................................29
Figure 5: Visual Representation of Alarm Instance being Set to Off................................................................30
Figure 6: Component Failure............................................................................................................................ 32
Figure 7: Agent Failure..................................................................................................................................... 33
Figure 8: Agent Failure with Component Queuing Mechanism........................................................................33
Figure 9: Clearing Alarm from Manager........................................................................................................... 34

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 8
List of Tables

Table 1: Added Faults for Release 2020.05_1.250..........................................................................................11

Table 2: Deprecated or Obsoleted Faults for Release 2020.05_1.250............................................................ 11
Table 3: Added Faults for Release 2020.04_1.200..........................................................................................11
Table 4: Added Faults for Release 2019.05_1.280..........................................................................................15
Table 5: Added Faults for Release 2019.03_1.170..........................................................................................16
Table 6: Added Faults for Release 2018.12_1.120..........................................................................................17
Table 7: Deprecated or Obsoleted Faults for Release 2018.12_1.120............................................................ 17
Table 8: Removed Faults for Release 2017.11_1.010.....................................................................................19
Table 9: Added Faults for Release 22.0.......................................................................................................... 20
Table 10: Deprecated or Obsoleted Faults for Release 22.0...........................................................................22
Table 11: Fault Report Fields........................................................................................................................... 28
Table 12: Traplist Files..................................................................................................................................... 38
Table 13: Trap Filter Files................................................................................................................................ 39
Table 14: MIB Files and OID Value Ranges for the Network Function Manager............................................. 44
Table 15: SNMP Traps For BroadworksConfigurationFault:processmonitor.................................................... 45
Table 16: SNMP Traps For BroadworksConfigurationFault:configd................................................................. 46
Table 17: SNMP Traps For BroadworksFault:unspecified................................................................................48
Table 18: SNMP Traps For BroadworksFault:processmonitor......................................................................... 50
Table 19: SNMP Traps For BroadworksFault:database................................................................................... 56
Table 20: SNMP Traps For BroadworksFault:sip............................................................................................. 59
Table 21: SNMP Traps For BroadworksFault:smtp..........................................................................................63
Table 22: SNMP Traps For BroadworksFault:filesystem..................................................................................64
Table 23: SNMP Traps For BroadworksFault:callp.......................................................................................... 65
Table 24: SNMP Traps For BroadworksFault:nssynch.................................................................................... 68
Table 25: SNMP Traps For BroadworksFault:smap.........................................................................................69
Table 26: SNMP Traps For BroadworksFault:accounting................................................................................ 70
Table 27: SNMP Traps For BroadworksFault:licensing....................................................................................70
Table 28: SNMP Traps For BroadworksFault:pmReporting............................................................................. 72
Table 29: SNMP Traps For BroadworksFault:smdi.......................................................................................... 72
Table 30: SNMP Traps For BroadworksFault:cpeDeviceManagement............................................................ 74
Table 31: SNMP Traps For BroadworksFault:networkDeviceManagement......................................................75
Table 32: SNMP Traps For BroadworksFault:ociReporting..............................................................................76
Table 33: SNMP Traps For BroadworksFault:bcct........................................................................................... 76
Table 34: SNMP Traps For BroadworksFault:taskMonitor............................................................................... 78
Table 35: SNMP Traps For BroadworksFault:logging...................................................................................... 79
Table 36: SNMP Traps For BroadworksFault:dns............................................................................................79
Table 37: SNMP Traps For BroadworksFault:snmpAgent................................................................................80
Table 38: SNMP Traps For BroadworksFault:xsp............................................................................................ 80

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 9
 Table 39: SNMP Traps For BroadworksFault:ps..............................................................................................81
Table 40: SNMP Traps For BroadworksFault:softwareManager...................................................................... 82
Table 41: SNMP Traps For BroadworksFault:security..................................................................................... 82
Table 42: SNMP Traps For BroadworksFault:webcontainer............................................................................ 84
Table 43: SNMP Traps For BroadworksFault:jvmProcess............................................................................... 85
Table 44: SNMP Traps For BroadworksFault:time...........................................................................................87
Table 45: SNMP Traps For BroadworksFault:threshold................................................................................... 87
Table 46: SNMP Traps For BroadworksFault:nps............................................................................................88
Table 47: SNMP Traps For BroadworksFault:hazelcastClient......................................................................... 89
Table 48: SNMP Traps For BW-FileTransferFault:fileRepos............................................................................89
Table 49: SNMP Traps For BW-LicenseControllerFault:processmonitor..........................................................90
Table 50: SNMP Traps For BW-LicenseControllerFault:licenseController....................................................... 92
Table 51: SNMP Traps For BW-LicenseManagerFault:processmonitor........................................................... 95
Table 52: SNMP Traps For BW-LicenseManagerFault:licensing..................................................................... 96
Table 53: SNMP Traps For BW-MDBManagementFault:processmonitor.........................................................98
Table 54: SNMP Traps For BW-MDBManagementFault:database................................................................ 100
Table 55: SNMP Traps For BW-NetworkMonitoringFault:processmonitor......................................................101
Table 56: SNMP Traps For BW-NetworkMonitoringFault:networkMonitoring.................................................104
Table 57: SNMP Traps For BW-NodeControllerFault:processmonitor........................................................... 105
Table 58: SNMP Traps For BW-NodeControllerFault:nodeController............................................................ 107
Table 59: SNMP Traps For BW-NodeLifecycleManagerFault:processmonitor............................................... 109
Table 60: SNMP Traps For BW-SoftwareManagementFault:processmonitor................................................ 112
Table 61: SNMP Traps For BW-SoftwareManagementFault:softwareManagement.......................................114
Table 62: SNMP Traps For BW-WebContainerFault:webcontainer................................................................116
Table 63: Fault Parameters............................................................................................................................ 119

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 10
1 History of Changes to the Cisco BroadWorks Fault MIBs

This section provides the list of changes to the Cisco BroadWorks MIBs between releases.

1.1 Changes from Release 2020.04_1.200 to Release 2020.05_1.250

This section provides the changes to Cisco BroadWorks MIBs between Release 2020.05_1.250 and
Release 2020.04_1.200, the previous major release of Cisco BroadWorks. Note that it also includes
information related to service packs from the previous major release.

1.1.1 Added Faults

List of faults added for Release 2020.05_1.250.
Table 1: Added Faults for Release 2020.05_1.250
Fault Name Mib Feature Also Available

bwOCICServerUnreachable BroadworksFault.mib PR-62549 None

bwOCIPServerUnreachable BroadworksFault.mib PR-62549 None

1.1.2 Moved Faults

List of faults moved between MIBs for Release 2020.05_1.250.
No faults were moved in this release.

1.1.3 Deprecated or Obsoleted Faults

List of faults deprecated or obsoleted for Release 2020.05_1.250. Faults are either deprecated or
obsoleted. The Status column indicates the status of the fault.
Table 2: Deprecated or Obsoleted Faults for Release 2020.05_1.250
Fault Name Mib Status

bwApplicationServerProvUnreachable BroadworksFault.mib Before: current

After: obsolete

1.1.4 Removed Faults

List of faults removed for Release 2020.05_1.250.
No faults were removed in this release.

1.2 Changes from Release 2020.01_1.160 to Release 2020.04_1.200

This section provides the changes to Cisco BroadWorks MIBs between Release 2020.04_1.200 and
Release 2020.01_1.160, the previous major release of Cisco BroadWorks. Note that it also includes
information related to service packs from the previous major release.

1.2.1 Added Faults

List of faults added for Release 2020.04_1.200.
Table 3: Added Faults for Release 2020.04_1.200
Fault Name Mib Feature Also Available

bwApplicationServerProvUnreachable BroadworksFault.mib PR-63437 None

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 11
 Fault Name Mib Feature Also Available

bwOSMisconfiguration BroadworksFault.mib PR-63831 None

bwProtocolRegistrationFailure BroadworksFault.mib PR-63437 None

1.2.2 Moved Faults

List of faults moved between MIBs for Release 2020.04_1.200.
No faults were moved in this release.

1.2.3 Deprecated or Obsoleted Faults

List of faults deprecated or obsoleted for Release 2020.04_1.200. Faults are either deprecated or
obsoleted. The Status column indicates the status of the fault.
No faults were deprecated or obsoleted in this release.

1.2.4 Removed Faults

List of faults removed for Release 2020.04_1.200.
No faults were removed in this release.

1.3 Changes from Release 2019.12_1.050 to Release 2020.01_1.160

This section provides the changes to Cisco BroadWorks MIBs between Release 2020.01_1.160 and
Release 2019.12_1.050, the previous major release of Cisco BroadWorks. Note that it also includes
information related to service packs from the previous major release.

1.3.1 Added Faults

List of faults added for Release 2020.01_1.160.
No faults were added in this release.

1.3.2 Moved Faults

List of faults moved between MIBs for Release 2020.01_1.160.
No faults were moved in this release.

1.3.3 Deprecated or Obsoleted Faults

List of faults deprecated or obsoleted for Release 2020.01_1.160. Faults are either deprecated or
obsoleted. The Status column indicates the status of the fault.
No faults were deprecated or obsoleted in this release.

1.3.4 Removed Faults

List of faults removed for Release 2020.01_1.160.
No faults were removed in this release.

1.4 Changes from Release 2019.09_1.180 to Release 2019.12_1.050

This section provides the changes to Cisco BroadWorks MIBs between Release 2019.12_1.050 and
Release 2019.09_1.180, the previous major release of Cisco BroadWorks. Note that it also includes
information related to service packs from the previous major release.

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 12
1.4.1 Added Faults
List of faults added for Release 2019.12_1.050.
No faults were added in this release.

1.4.2 Moved Faults

List of faults moved between MIBs for Release 2019.12_1.050.
No faults were moved in this release.

1.4.3 Deprecated or Obsoleted Faults

List of faults deprecated or obsoleted for Release 2019.12_1.050. Faults are either deprecated or
obsoleted. The Status column indicates the status of the fault.
No faults were deprecated or obsoleted in this release.

1.4.4 Removed Faults

List of faults removed for Release 2019.12_1.050.
No faults were removed in this release.

1.5 Changes from Release 2019.08_1.230 to Release 2019.09_1.180

This section provides the changes to Cisco BroadWorks MIBs between Release 2019.09_1.180 and
Release 2019.08_1.230, the previous major release of Cisco BroadWorks. Note that it also includes
information related to service packs from the previous major release.

1.5.1 Added Faults

List of faults added for Release 2019.09_1.180.
No faults were added in this release.

1.5.2 Moved Faults

List of faults moved between MIBs for Release 2019.09_1.180.
No faults were moved in this release.

1.5.3 Deprecated or Obsoleted Faults

List of faults deprecated or obsoleted for Release 2019.09_1.180. Faults are either deprecated or
obsoleted. The Status column indicates the status of the fault.
No faults were deprecated or obsoleted in this release.

1.5.4 Removed Faults

List of faults removed for Release 2019.09_1.180.
No faults were removed in this release.

1.6 Changes from Release 2019.06_1.310 to Release 2019.08_1.230

This section provides the changes to Cisco BroadWorks MIBs between Release 2019.08_1.230 and
Release 2019.06_1.310, the previous major release of Cisco BroadWorks. Note that it also includes
information related to service packs from the previous major release.

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 13
1.6.1 Added Faults
List of faults added for Release 2019.08_1.230.
No faults were added in this release.

1.6.2 Moved Faults

List of faults moved between MIBs for Release 2019.08_1.230.
No faults were moved in this release.

1.6.3 Deprecated or Obsoleted Faults

List of faults deprecated or obsoleted for Release 2019.08_1.230. Faults are either deprecated or
obsoleted. The Status column indicates the status of the fault.
No faults were deprecated or obsoleted in this release.

1.6.4 Removed Faults

List of faults removed for Release 2019.08_1.230.
No faults were removed in this release.

1.7 Changes from Release 2019.05_1.280 to Release 2019.06_1.310

This section provides the changes to Cisco BroadWorks MIBs between Release 2019.06_1.310 and
Release 2019.05_1.280, the previous major release of Cisco BroadWorks. Note that it also includes
information related to service packs from the previous major release.

1.7.1 Added Faults

List of faults added for Release 2019.06_1.310.
No faults were added in this release.

1.7.2 Moved Faults

List of faults moved between MIBs for Release 2019.06_1.310.
No faults were moved in this release.

1.7.3 Deprecated or Obsoleted Faults

List of faults deprecated or obsoleted for Release 2019.06_1.310. Faults are either deprecated or
obsoleted. The Status column indicates the status of the fault.
No faults were deprecated or obsoleted in this release.

1.7.4 Removed Faults

List of faults removed for Release 2019.06_1.310.
No faults were removed in this release.

1.8 Changes from Release 2019.04_1.230 to Release 2019.05_1.280

This section provides the changes to Cisco BroadWorks MIBs between Release 2019.05_1.280 and
Release 2019.04_1.230, the previous major release of Cisco BroadWorks. Note that it also includes
information related to service packs from the previous major release.

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 14
1.8.1 Added Faults
List of faults added for Release 2019.05_1.280.
Table 4: Added Faults for Release 2019.05_1.280
Fault Name Mib Feature Also Available

bwCentralizedDatabasePoolFailure BroadworksFault.mib PR-61058 None

1.8.2 Moved Faults

List of faults moved between MIBs for Release 2019.05_1.280.
No faults were moved in this release.

1.8.3 Deprecated or Obsoleted Faults

List of faults deprecated or obsoleted for Release 2019.05_1.280. Faults are either deprecated or
obsoleted. The Status column indicates the status of the fault.
No faults were deprecated or obsoleted in this release.

1.8.4 Removed Faults

List of faults removed for Release 2019.05_1.280.
No faults were removed in this release.

1.9 Changes from Release 2019.03_1.170 to Release 2019.04_1.230

This section provides the changes to Cisco BroadWorks MIBs between Release 2019.04_1.230 and
Release 2019.03_1.170, the previous major release of Cisco BroadWorks. Note that it also includes
information related to service packs from the previous major release.

1.9.1 Added Faults

List of faults added for Release 2019.04_1.230.
No faults were added in this release.

1.9.2 Moved Faults

List of faults moved between MIBs for Release 2019.04_1.230.
No faults were moved in this release.

1.9.3 Deprecated or Obsoleted Faults

List of faults deprecated or obsoleted for Release 2019.04_1.230. Faults are either deprecated or
obsoleted. The Status column indicates the status of the fault.
No faults were deprecated or obsoleted in this release.

1.9.4 Removed Faults

List of faults removed for Release 2019.04_1.230.
No faults were removed in this release.

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 15
1.10 Changes from Release 2019.01_1.283 to Release 2019.03_1.170
This section provides the changes to Cisco BroadWorks MIBs between Release 2019.03_1.170 and
Release 2019.01_1.283, the previous major release of Cisco BroadWorks. Note that it also includes
information related to service packs from the previous major release.

1.10.1 Added Faults

List of faults added for Release 2019.03_1.170.
Table 5: Added Faults for Release 2019.03_1.170
Fault Name Mib Feature Also Available

bwMariaDBNonPrimaryClusterNode BW-MDBManagementFault.mib PR-59778 None

1.10.2 Moved Faults

List of faults moved between MIBs for Release 2019.03_1.170.
No faults were moved in this release.

1.10.3 Deprecated or Obsoleted Faults

List of faults deprecated or obsoleted for Release 2019.03_1.170. Faults are either deprecated or
obsoleted. The Status column indicates the status of the fault.
No faults were deprecated or obsoleted in this release.

1.10.4 Removed Faults

List of faults removed for Release 2019.03_1.170.
No faults were removed in this release.

1.11 Changes from Release 2018.12_1.120 to Release 2019.01_1.283

This section provides the changes to Cisco BroadWorks MIBs between Release 2019.01_1.283 and
Release 2018.12_1.120, the previous major release of Cisco BroadWorks. Note that it also includes
information related to service packs from the previous major release.

1.11.1 Added Faults

List of faults added for Release 2019.01_1.283.
No faults were added in this release.

1.11.2 Moved Faults

List of faults moved between MIBs for Release 2019.01_1.283.
No faults were moved in this release.

1.11.3 Deprecated or Obsoleted Faults

List of faults deprecated or obsoleted for Release 2019.01_1.283. Faults are either deprecated or
obsoleted. The Status column indicates the status of the fault.
No faults were deprecated or obsoleted in this release.

1.11.4 Removed Faults

List of faults removed for Release 2019.01_1.283.

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 16
 No faults were removed in this release.

1.12 Changes from Release 2018.05_1.230 to Release 2018.12_1.120

This section provides the changes to Cisco BroadWorks MIBs between Release 2018.12_1.120 and
Release 2018.05_1.230, the previous major release of Cisco BroadWorks. Note that it also includes
information related to service packs from the previous major release.

1.12.1 Added Faults

List of faults added for Release 2018.12_1.120.
Table 6: Added Faults for Release 2018.12_1.120
Fault Name Mib Feature Also Available

bwHazelcastClusterConnectivityUnavailable BroadworksFault.mib BW-18485 R22.0

1.12.2 Moved Faults

List of faults moved between MIBs for Release 2018.12_1.120.
No faults were moved in this release.

1.12.3 Deprecated or Obsoleted Faults

List of faults deprecated or obsoleted for Release 2018.12_1.120. Faults are either deprecated or
obsoleted. The Status column indicates the status of the fault.
Table 7: Deprecated or Obsoleted Faults for Release 2018.12_1.120
Fault Name Mib Status

bwPMconfigdOutOfMemory BroadworksConfigurationFault.mib Before: current

After: obsolete

bwPMlmdOutOfMemory BW-LicenseManagerFault.mib Before: current

After: obsolete

1.12.4 Removed Faults

List of faults removed for Release 2018.12_1.120.
No faults were removed in this release.

1.13 Changes from Release 2018.02_1.250 to Release 2018.05_1.230

This section provides the changes to Cisco BroadWorks MIBs between Release 2018.05_1.230 and
Release 2018.02_1.250, the previous major release of Cisco BroadWorks. Note that it also includes
information related to service packs from the previous major release.

1.13.1 Added Faults

List of faults added for Release 2018.05_1.230.
No faults were added in this release.

1.13.2 Moved Faults

List of faults moved between MIBs for Release 2018.05_1.230.
No faults were moved in this release.

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 17
1.13.3 Deprecated or Obsoleted Faults
List of faults deprecated or obsoleted for Release 2018.05_1.230. Faults are either deprecated or
obsoleted. The Status column indicates the status of the fault.
No faults were deprecated or obsoleted in this release.

1.13.4 Removed Faults

List of faults removed for Release 2018.05_1.230.
No faults were removed in this release.

1.14 Changes from Release 2017.12_1.010 to Release 2018.02_1.250

This section provides the changes to Cisco BroadWorks MIBs between Release 2018.02_1.250 and
Release 2017.12_1.010, the previous major release of Cisco BroadWorks. Note that it also includes
information related to service packs from the previous major release.

1.14.1 Added Faults

List of faults added for Release 2018.02_1.250.
No faults were added in this release.

1.14.2 Moved Faults

List of faults moved between MIBs for Release 2018.02_1.250.
No faults were moved in this release.

1.14.3 Deprecated or Obsoleted Faults

List of faults deprecated or obsoleted for Release 2018.02_1.250. Faults are either deprecated or
obsoleted. The Status column indicates the status of the fault.
No faults were deprecated or obsoleted in this release.

1.14.4 Removed Faults

List of faults removed for Release 2018.02_1.250.
No faults were removed in this release.

1.15 Changes from Release 2017.11_1.010 to Release 2017.12_1.010

This section provides the changes to Cisco BroadWorks MIBs between Release 2017.12_1.010 and
Release 2017.11_1.010, the previous major release of Cisco BroadWorks. Note that it also includes
information related to service packs from the previous major release.

1.15.1 Added Faults

List of faults added for Release 2017.12_1.010.
No faults were added in this release.

1.15.2 Moved Faults

List of faults moved between MIBs for Release 2017.12_1.010.
No faults were moved in this release.

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 18
1.15.3 Deprecated or Obsoleted Faults
List of faults deprecated or obsoleted for Release 2017.12_1.010. Faults are either deprecated or
obsoleted. The Status column indicates the status of the fault.
No faults were deprecated or obsoleted in this release.

1.15.4 Removed Faults

List of faults removed for Release 2017.12_1.010.
No faults were removed in this release.

1.16 Changes from Release 22.0 to Release 2017.11_1.010

This section provides the changes to Cisco BroadWorks MIBs between Release 2017.11_1.010 and
Release 22.0, the previous major release of Cisco BroadWorks. Note that it also includes information
related to service packs from the previous major release.

1.16.1 Added Faults

List of faults added for Release 2017.11_1.010.
No faults were added in this release.

1.16.2 Moved Faults

List of faults moved between MIBs for Release 2017.11_1.010.
No faults were moved in this release.

1.16.3 Deprecated or Obsoleted Faults

List of faults deprecated or obsoleted for Release 2017.11_1.010. Faults are either deprecated or
obsoleted. The Status column indicates the status of the fault.
No faults were deprecated or obsoleted in this release.

1.16.4 Removed Faults

List of faults removed for Release 2017.11_1.010.
Table 8: Removed Faults for Release 2017.11_1.010
Fault Name Mib

bwApplicationServerProvUnreachable BroadworksFault.mib

bwApplicationServerUnreachable BroadworksFault.mib

bwHazelcastClusterConnectivityUnavailable BroadworksFault.mib

bwProtocolRegistrationFailure BroadworksFault.mib

bwMariaDBNonPrimaryClusterNode BW-MDBManagementFault.mib

1.17 Changes from Release 21.0 to Release 22.0

This section provides the changes to Cisco BroadWorks MIBs between Release 22.0 and Release 21.0,
the previous major release of Cisco BroadWorks. Note that it also includes information related to service
packs from the previous major release.

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 19
1.17.1 Added Faults
List of faults added for Release 22.0.
Table 9: Added Faults for Release 22.0
Fault Name Mib Feature Also Available

bwApplicationServerProvUnreachable BroadworksFault.mib PR-63437 None

bwCentralizedDatabaseListenerFailure BroadworksFault.mib PR-52073 None

bwCentralizedDatabaseMaxConnectionsReached BroadworksFault.mib PR-52342 None

bwCentralizedDatabaseNewConnectionFailure BroadworksFault.mib PR-52871 None

bwCouchbaseNodeConnectivityFailure BroadworksFault.mib BW-10066 R22.0

bwExtremeOverload BroadworksFault.mib PR-45925 None

bwHazelcastClusterConnectivityUnavailable BroadworksFault.mib BW-18485 R22.0

bwJVMProcessOutOfMemory BroadworksFault.mib BW-6517 R22.0

bwJVMProcessUnexpectedSoftwareCondition BroadworksFault.mib BW-6517 R22.0

Detected

bwNetworkDatabaseClusterConnectivityFailure BroadworksFault.mib BW-2299 R21.sp2, R22.0

bwNetworkDatabaseNodeConnectivityFailure BroadworksFault.mib BW-2299 R21.sp2, R22.0

bwNetworkDatabaseSchemaFailure BroadworksFault.mib BW-2299 R21.sp2, R22.0

bwNSSyncSuccessDbCommitFailed BroadworksFault.mib BW-6957 None

bwProtocolRegistrationFailure BroadworksFault.mib PR-63437 None

bwPushNotificationServerUnreachable BroadworksFault.mib TIII-58132 None

bwTimeSkewExceeded BroadworksFault.mib BW-2300 R21.sp1, R22.0

bwFileTransferReplicationFailure BW-FileTransferFault.mib BW-7266 R21.sp1, R22.0

bwFileTransferReplicationOffline BW-FileTransferFault.mib BW-7266 R21.sp1, R22.0

bwMariaDBNonPrimaryClusterNode BW-MDBManagementFault.mib PR-59778 None

bwPMMariaDBDeath BW-MDBManagementFault.mib BW-2299 R21.sp2, R22.0

bwPMMariaDBLaunched BW-MDBManagementFault.mib BW-2299 R21.sp2, R22.0

bwPMMariaDBRestarted BW-MDBManagementFault.mib BW-2299 R21.sp2, R22.0

bwPMMariaDBShutDown BW-MDBManagementFault.mib BW-2299 R21.sp2, R22.0

bwPMmdbMonitorDeath BW-MDBManagementFault.mib BW-2299 R21.sp2, R22.0

bwPMmdbMonitorLaunched BW-MDBManagementFault.mib BW-2299 R21.sp2, R22.0

bwPMmdbMonitorRestarted BW-MDBManagementFault.mib BW-2299 R21.sp2, R22.0

bwPMmdbMonitorShutDown BW-MDBManagementFault.mib BW-2299 R21.sp2, R22.0

bwNMControllerInventoryOutOfSynch BW-NetworkMonitoringFault.mib BW-6984 R21.sp1, R22.0

bwNMReplicationPrimaryFailure BW-NetworkMonitoringFault.mib BW-6984 R21.sp1, R22.0

bwNMReplicationStandbyFailure BW-NetworkMonitoringFault.mib BW-6984 R21.sp1, R22.0

bwPMFileReplicationDeath BW-NetworkMonitoringFault.mib BW-6984 R21.sp1, R22.0

bwPMFileReplicationLaunched BW-NetworkMonitoringFault.mib BW-6984 R21.sp1, R22.0

bwPMFileReplicationRestarted BW-NetworkMonitoringFault.mib BW-6984 R21.sp1, R22.0

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 20
 Fault Name Mib Feature Also Available

bwPMFileReplicationShutDown BW-NetworkMonitoringFault.mib BW-6984 R21.sp1, R22.0

bwPMNetworkMonitoringDeath BW-NetworkMonitoringFault.mib BW-6984 R21.sp1, R22.0

bwPMNetworkMonitoringLaunched BW-NetworkMonitoringFault.mib BW-6984 R21.sp1, R22.0

bwPMNetworkMonitoringOutOfMemory BW-NetworkMonitoringFault.mib BW-6984 R21.sp1, R22.0

bwPMNetworkMonitoringRestarted BW-NetworkMonitoringFault.mib BW-6984 R21.sp1, R22.0

bwPMNetworkMonitoringShutDown BW-NetworkMonitoringFault.mib BW-6984 R21.sp1, R22.0

bwPMnginxDeath BW-NodeLifecycleManagerFault 217550 R21.0

.mib

bwPMnginxLaunched BW-NodeLifecycleManagerFault 217550 R21.0

.mib

bwPMnginxRestarted BW-NodeLifecycleManagerFault 217550 R21.0

.mib

bwPMnginxShutDown BW-NodeLifecycleManagerFault 217550 R21.0

.mib

bwPMunicornDeath BW-NodeLifecycleManagerFault 217550 R21.0

.mib

bwPMunicornLaunched BW-NodeLifecycleManagerFault 217550 R21.0

.mib

bwPMunicornRestarted BW-NodeLifecycleManagerFault 217550 R21.0

.mib

bwPMunicornShutDown BW-NodeLifecycleManagerFault 217550 R21.0

.mib

bwPMSoftwareControllerDeath BW-SoftwareManagementFault BW-7266 R21.sp1, R22.0

.mib

bwPMSoftwareControllerLaunched BW-SoftwareManagementFault BW-7266 R21.sp1, R22.0

.mib

bwPMSoftwareControllerOutOfMemory BW-SoftwareManagementFault BW-7266 R21.sp1, R22.0

.mib

bwPMSoftwareControllerRestarted BW-SoftwareManagementFault BW-7266 R21.sp1, R22.0

.mib

bwPMSoftwareControllerShutDown BW-SoftwareManagementFault BW-7266 R21.sp1, R22.0

.mib

bwSoftwareManagementAdditionalPatchMissing BW-SoftwareManagementFault BW-7266 R21.sp1, R22.0

.mib

bwSoftwareManagementDistributionCenter BW-SoftwareManagementFault BW-7266 R21.sp1, R22.0

ConnectivityFailure .mib

bwSoftwareManagementExecutorQueueLatency BW-SoftwareManagementFault BW-7266 R21.sp1, R22.0

Exceeded .mib

bwSoftwareManagementExecutorQueueUsage BW-SoftwareManagementFault BW-7266 R21.sp1, R22.0

Exceeded .mib

bwSoftwareManagementExecutorThreadPoolBusy BW-SoftwareManagementFault BW-7266 R21.sp1, R22.0

Exceeded .mib

bwSoftwareManagementExecutorThreadPool BW-SoftwareManagementFault BW-7266 R21.sp1, R22.0

ProcessingTimeExceeded .mib

bwSoftwareManagementInvalidSignature BW-SoftwareManagementFault BW-2214 R22.0

.mib

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 21
 Fault Name Mib Feature Also Available

bwSoftwareManagementNewCriticalPatch BW-SoftwareManagementFault BW-7266 R21.sp1, R22.0

Released .mib

bwSoftwareManagementNewDeprecatedPatch BW-SoftwareManagementFault BW-7266 R21.sp1, R22.0

.mib

bwSoftwareManagementReReleasedPatch BW-SoftwareManagementFault BW-7266 R21.sp1, R22.0

.mib

bwSoftwareManagementSWManagerInstallation BW-SoftwareManagementFault BW-7266 R21.sp1, R22.0

Failure .mib

1.17.2 Moved Faults

List of faults moved between MIBs for Release 22.0.
No faults were moved in this release.

1.17.3 Deprecated or Obsoleted Faults

List of faults deprecated or obsoleted for Release 22.0. Faults are either deprecated or obsoleted. The
Status column indicates the status of the fault.
Table 10: Deprecated or Obsoleted Faults for Release 22.0
Fault Name Mib Status

bwNonheapMemoryUsageExceeded BroadworksFault.mib Before: current

After: deprecated

1.17.4 Removed Faults

List of faults removed for Release 22.0.
No faults were removed in this release.

1.18 Server Introduction in Release 21.0

Release 21.0 introduces the Network Function Manager.

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 22
2 Introduction

This document describes Cisco BroadWorks Fault Management for all the Cisco BroadWorks servers.
This document describes the:
• Cisco BroadWorks Fault Management components, including the Command Line Interface (CLI) and
Simple Network Management Protocol (SNMP) functionality
• Notifications and alarms generated by Cisco BroadWorks
Cisco BroadWorks supports SNMP v2c and v3. Operators are provided with a set of comprehensive CLI
commands to manage the SNMP trap redirection. Note that Cisco BroadWorks also acts as an SNMP
proxy agent for the Solaris platform agent.

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 23
3 SNMP Agent Configuration

The information provided in this section applies to the SNMP agent for all the Cisco BroadWorks servers.

3.1 SNMP Agent Configuration

The Cisco BroadWorks SNMP interface is configured using the CLI client (bwcli). An operator has access
to the SNMP configuration level at the CLI Interfaces/SNMP level.
CLI/Interface/SNMP> ?
0) AccessList : go to level AccessList
1) Agent : go to level Agent
2) AgentX : go to level AgentX
3) JVMStatsCollector : go to level JVMStatsCollector
4) Logging : go to level Logging
5) NetSNMP : go to level NetSNMP
6) Reporting : go to level Reporting
7) SMAP : go to level SMAP
8) TrapTable : go to level TrapTable
9) V3AccessControl : go to level V3AccessControl
10) V3Users : go to level V3Users

h (help), e (exit), q (quit), r (read), w (write), t (tree),

c (config), cd (cd), a (alias), hi (history), p (pause), re (repeat),
k (keyboardHelp)

CLI/Interface/SNMP> Agent

CLI/Interface/SNMP/Agent> get
port = 8001
encoding = ISO-8859-1
readCommunity = public
writeCommunity = public
trapCommunity = public
trapSourceAddress = 10.9.32.228
disableV2 = false
hostMibII = false

By default, Cisco BroadWorks listens on port 8001 to service SNMP get requests. Compared to other
typical SNMP agents, the Cisco BroadWorks agent cannot listen on port 161. Note that the community
strings apply only for v2c requests.
For a system with multiple network interfaces, the operator can also choose the interface to use to send
SNMP traps. In the example above, 192.168.13.189 appears as the trap source address received at the
Element or Network Management System.

NOTE: At this context, the Logging context is used to configure logging and SMAP is used to configure
internal messaging parameters. For information on the V3AccessControl and V3Users contexts, see the
BroadWorks Network Function Manager Performance Measurement Interface Specification Guide.

3.2 Configuration SNMP V2c Access List

An access list specifies the management systems permitted to retrieve performance measurements. The
management system that sends the query must include, as part of the message, a community name that
acts as a password on the agent systems. Upon each SNMP get request, Cisco BroadWorks verifies the

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 24
 community and the IP address of the request against the community and IP address configured in the
access list. Upon successful validation, the SNMP get request is processed. The access list is configured
through the CLI.
CLI/Interface/SNMP> AccessList

CLI/Interface/SNMP/AccessList> get

192.168.8.181
192.168.8.179
127.0.0.1
192.168.8.43
192.168.13.187
192.168.13.185
192.168.8.251

7 entries found.

3.3 SNMP Trap Managers

A trap-forwarding table specifies the management systems and the corresponding ports faults. The trap
table is configured through the CLI.
AS_CLI/Interface/SNMP/TrapTable
AS_CLI/Interface/SNMP/TrapTable get
IP Address Port Model Use Alarms V3User
==================================================
192.168.8.179 8001 shared true
192.168.8.181 8001 shared true
192.168.8.43 8001 shared true
192.168.13.187 8001 unique true
192.168.13.185 8001 unique true
192.168.8.251 8001 shared true

6 entries found.

Cisco BroadWorks uses the concept of a model to control traps. The model value can either be set to
"unique" or "shared". Details of these include:
• In the "unique" model, each Cisco BroadWorks trap has a unique OID. In this model, the management
system does not have to do additional processing to uniquely identify a trap.

Important: Usage of the "unique" model is recommended.

• In the "shared" model, Cisco BroadWorks traps all use the same notification OID. Following this model,
the management system must parse incoming traps and extract the fault name to uniquely identify
each notification. The "shared" model was originally the only model supported by Cisco BroadWorks
and it has been kept for backward-compatibility. It should only be used if a monitoring system still has
scripts that use this functionality and that cannot be converted to use unique OIDs. As of Release 16.0,
the "shared" model is deprecated. It is still fully supported; however, steps should be taken to convert
monitoring managers relying on this model to the "unique" model.

3.4 SNMP v3 Access Control

SNMP agent configuration provides the ability to enforce the SNMP v3 View-based Access Control Model
(VACM). This access control facility makes it possible to configure different levels of access to the agent
Management Information Base (MIB) for SNMP v3 users. Access control is performed by a group, where

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 25
 the group is a set of one or more users. Access is granted for each group to one of the three predefined
views: all, management, or performance.
• The all view provides access to all MIBs.
• The management view provides access to the managed object’s subtree from the Cisco BroadWorks
maintenance MIB (BroadworksMaintenance.mib).
• The performance view provides access to all other MIBs. Read and write permissions are given on a
per-user basis.
The following figure illustrates the three predefined views.

Figure 1: Views

Both the VACM and the User-based Security Model (USM) MIBs are solely allowed "read-only" access.
Configuration of the settings for v3 access control is performed through the Cisco BroadWorks CLI.
First, define an access control group and then set the level of access for the group. More than one level of
access can be assigned to a group. The following illustrates these steps from the CLI.

CLI/Interface/SNMP/V3AccessControl/Groups> add groupOne

...Done

CLI/Interface/SNMP/V3AccessControl/Groups> get
Name
==========
groupOne

1 entry found.

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 26
 CLI/Interface/SNMP/V3AccessControl/Groups> AccessLevels
CLI/Interface/SNMP/V3AccessControl/Groups/AccessLevels> add groupOne performance
...Done

CLI/Interface/SNMP/V3AccessControl/Groups/AccessLevels> get groupOne

Level
============
performance

1 entry found.

3.5 SNMP v3 Users

SNMP v3 uses a User-based Security Model (USM). Management operations using this security model
make use of a defined set of user identities. For any user with management operations authorized at a
particular SNMP engine, that SNMP engine must have knowledge of that user. An SNMP engine that
wishes to communicate with another SNMP engine must also have knowledge of a user known to that
engine, including knowledge of the applicable attributes of that user.
The Cisco BroadWorks v3 implementation supports three levels of v3 users:
• No Authorization, No Privacy
• Authorization (MD5, SHA, SHA224, SHA256, SHA384, SHA512), No Privacy
• Authorization (MD5, SHA, SHA224, SHA256, SHA384, SHA512), Privacy (DES, AES)
A v3 user can be associated with an access control group. Configuration of the SNMP v3 users is done
through the Cisco BroadWorks CLI.

NOTE: If no access control group is assigned to a v3 user, that user has no access.

3.6 Reporting
The SNMP reporting level allows an operator to automate the generation of an operational measurements
report, which is sent to remote servers. The report (in XML format) contains a header and a value for each
SNMP counter and gauge. The report is sent to remote servers via FTP put commands.
For more information on reporting functionality, see the BroadWorks Network Function Manager
Performance Measurement Interface Specification Guide.

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 27
4 Cisco BroadWorks Faults

This section provides the definitions required to work with the Cisco BroadWorks faults.

4.1 Fault Template

The following table describes the fields in a fault report:
Table 11: Fault Report Fields
Field Description

Identifier A sequentially generated number, which can be used to uniquely identify the fault.

Timestamp The date and time the fault was generated.

System Name The host name of the system running Cisco BroadWorks software.

Severity An indicator of the severity of the fault.

INFORMATIONAL: This does not affect service.
LOW: Losing redundant connectivity, but does not affect service or capacity. For example, the
primary SMTP server is down, but Call Notify services are still provided via secondary SMTP
server (for example, losing one Media Server). (The Media Server is typically deployed in N + 1
fashion).
MEDIUM:Ability to provide connectivity, but affects service-level. For example, losing two out of
four Media Servers impacts the Media Server capacity.
HIGH: Inability to provide connectivity over a particular interface. For example losing connectivity
to all Media Servers or losing connectivity to both SMTP servers.
CRITICAL: No basic calls can be processed without operator intervention.

Component The Cisco BroadWorks server or application reporting the fault.

Subcomponent Software component within the Cisco BroadWorks component reporting the fault.

Problem Type Notification, Alarm, or Software Error

Alarm State Alarm "On" or "Off" (applicable to stateful alarms only).

Problem Text Text indicating the details of the variable. One central file for problem text to support
internationalization.

Problem Resources A list of variables, which bind to the problem text.

Recommended Actions Text Text indicating details of the recommended actions to take.

Recommended Resources A list of variables, which bind with the recommended actions text.
Text

Notification Parameters Each fault defines a number of variable bindings that give additional context to the fault being
variable bindings... sent.

The remaining sections specify faults generated by Cisco BroadWorks. The document is organized by
component followed by subcomponent. Variable bindings for Problem Text parameters are denoted by
%<tagName>%, where <tagname> is the name of the notification parameter that is itself featured as a
variable binding in the SNMP trap. Variable bindings for Recommendation Text parameters are denoted
by %n, where n is an integer representing the argument number. Carriage returns in the Problem Text and
Recommendation Text fields are denoted by <cr>.

4.2 Notifications and Alarms

Cisco BroadWorks defines two types of faults: notifications and alarms. Notifications describe punctual
events that can occur throughout the lifetime of the application. Events such as unauthorized access,

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 28
 security violations, status reports, added/deleted resources, unreachable servers, and software errors can
be the objects of notifications. The system health report is a good example of a notification. A monitored
device sends it periodically to provide a snapshot of its health at a certain moment. The severity of this
notification depends on the health of the monitored device.

Figure 2: Visual Representation of Notification during Lifetime of Monitored Device

Alarms warn that the system is currently in an abnormal state, but that the situation could change (for
better or worse) over time. Alarms are raised at the start of the abnormal state and are cleared upon return
to normal state. They are used to represent events such as connectivity loss, unresponsive software
components, reached threshold limits, and resource exhaustion. Alarms have a state that determines
whether they are On or Off. Alarms are sometimes referred to as Stateful Alarms. An additional state,
Cleared, is used when the alarm is set to Off through manual intervention. Off and Cleared mean the same
thing except that the latter gives an indication that the alarm was set to Off manually.

Figure 3: Visual Representation of Alarm during Lifetime of Monitored Device

4.3 Alarm Correlation

This feature introduces the correlation parameter. Monitoring systems can correlate with the alarm name to
identify different instances of the same alarm when raised numerous times for different reasons.

Figure 4: Visual Representation of Multiple Instances of Same Alarm being Raised

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 29
 In Figure 3 the Application Server tries to connect to two Network Servers; however, it fails. When an
Application Server is unable to connect to a Network Server, the bwNetworkServerUnreachable alarm is
raised. To differentiate between the alarms concerning NS1 and NS2, the monitoring system can now read
the correlation variable which, in addition to the alarm name, correlates and uniquely identifies the alarm
instance.
When the Application Server is finally able to connect to NS1, it sends a new alarm - state = "off" with the
same differentiator variable. This way, the monitoring system knows which bwNetworkServerUnreachable
alarm instance to clear.

Figure 5: Visual Representation of Alarm Instance being Set to Off

The correlation parameter type is a string. This allows it to be generic enough for all alarm types that use it.
For example, in the case of a connectivity problem, the correlation value could be the configured address;
for software failures, the correlation value could be the component name, and so on.
The correlation parameter is defined at the following object identifier (OID):
.iso.org.dod.internet.private.enterprises.broadsoft.broadworks.
common.systemFaults.faultFields.correlationParameter
OID: .1.3.6.1.4.1.6431.1.1.1.1.11

NOTE: Monitoring managers shall always correlate alarms using the alarm OID and the correlation
parameter.

4.3.1 Example
The bwCNAMSoapServerUnreachable notification is sent when an Application Server detects a
connectivity problem with a CNAM (CNAM) SOAP server. In this example, the originating component is the
Application Server and the subcomponent is the SOAP interface. The BroadworksFault.mib file defines the
Application Server as component 0 and the SOAP interface as the subcomponent 47. In this example the
unreachable CNAM SOAP server is at address 192.168.8.13 and the exception message is unknown.
The correlation parameter for this alarm would be a composition of the component, the subcomponent, and
all the problem variables:
0;47;192.168.8.13;unknown

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 30
 The same correlation parameter is calculated when the alarm state is set to Off, allowing managers to clear
the alarm.

4.3.2 High Availability SNMP Alarms

One of the SNMP agent challenges is to provide high availability for SNMP alarms even though they are
transferred over the unreliable User Datagram Protocol (UDP). High availability is achieved by providing
access to active and historical alarms as well as re-sending alarms following an agent failure.

4.3.2.1 List of Alarms

The agent sends SNMP alarms (traps/notifications) to the monitoring systems over the UDP protocol, a
connectionless and unreliable protocol. It is possible that monitoring systems do not receive alarms at all.
For this reason and because the monitoring systems can be restarted, the agent provides a list of currently
active alarms. The agent maintains this table with the information coming from the subcomponents on the
server.
The alarm list is located in the common maintenance MIB:
.iso.org.dod.internet.private.enterprises.broadsoft.broadworks.
common.alarms.bwAlarmsTableOID:
.1.3.6.1.4.1.6431.1.1.2.1

Managers can request alarms to be resent to them. Additionally, it is possible to clear currently active
alarms.
The table contains up to a maximum of 500 (configurable through a Java property) alarms that are
currently raised. The table displays the following alarms fields. All fields are read-only.
• Sequential Identifier (Counter32) - INDEX
• Timestamp (DateAndTime)
• Alarm OID (OID)
• Alarm Name (DisplayString)
• Severity (Integer: Informational (0), low (1), medium (2), high (3), critical (4))
• Correlation Parameter (DisplayString)
Two additional read-write fields are provided to perform actions on selected alarms:
• Clear Alarm (Integer: Clear (1))
• Resend (String)
The Sequential Identifier integer always counts up for each new notification and alarm. It is, therefore, not a
sequential table row count.
In the event that the table limit is reached, no new alarms are generated by the agent. A critical notification,
bwAlarmsTableLimitReached, is sent to notify monitoring managers that the agent is no longer processing
alarms normally.
When the alarm state is set to Off, the originating component is notified that it must clear its alarm. This
results in a new notification being sent to clear the alarm by the originating component.
The Resend field must be set with a valid host and port (format: host:port) for an alarm to be resent. Any
valid combination of host and port can be used, as long as it is a configured manager and it is configured
to support alarms. When set, the corresponding alarm is resent to the monitoring manager defined by the
host and port. All original parameters are kept, including the timestamp. Note that it is possible that the
resending of the alarms reaches the host after a possible clearing of the alarm. The monitoring manager
must handle this scenario by comparing the timestamps and correlation parameters.
At the CLI, the list can also be consulted using the list command at the AlarmsTable level:
$ CLI/Monitoring/Alarms/AlarmsTable> list
Identifier TimeStamp Alarm Name Severity
Correlation Parameter
==================================================================

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 31
 2562 2010-3-23 20:48:50 GMT bwNSSynchUnknownHostnameError Medium
2;16;MTLSOL-27;
1 entry found.

4.3.2.2 Component Failure

A component failure is defined as a component losing its communication with the SNMP agent while the
SNMP agent itself is still alive. Loss of communication is detected by the Cisco BroadWorks Common
Communication Transport (BCCT) framework which actively monitors the connection between the agent
and SNMP agent for disconnections and socket failures. When the communication is re-established with
the SNMP agent through a communication reset or through a restart of the component's process, the
failure is resolved.
When a component failure is detected by the agent, it removes the outstanding alarms sent by this
component from the alarms tables, and sends clearing notifications to the monitoring managers.

Figure 6: Component Failure

Upon resolution of the component failure, the component communicates active alarms to the agent who in
turn sends them out to the managers.
Managers can check this table periodically to ensure they are synchronized and that they have not missed
any alarms.

4.3.2.3 Agent Failure

In the event that the agent fails, it is automatically restarted by the process monitor. Although this situation
is not supposed to occur, a strategy is in place to reduce the failure time while ensuring high availability of
the alarm.
At startup or following a failure, the agent starts with an empty Alarms table. Upon reconnection of the
different server's components with the SNMP agent, the table is repopulated with currently active alarms.
Alarm raises or clears that occurred on the component during the agent failure are also sent to the agent
who in turn sends out alarms to the managers.

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 32
 Figure 7: Agent Failure

In this scenario, if the manager did not detect the agent failure through a ping, it receives the same
notification twice. In this case, the manager should update the initial alarm, which is identifiable with the
correlation parameter. Note that if the component sends a notification indicating that it was just restarted,
the manager could trigger on this notification to clear all the other alarms for this component.

Figure 8: Agent Failure with Component Queuing Mechanism

In the case that a component detects an event noteworthy of an alarm while not connected to the SNMP
agent, it queues the alarm until the connection is re-established.

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 33
4.3.2.4 Cisco BroadWorks Restart
When it starts, a notification is not sent by the agent. Even if there was one, their unreliable nature would
not guarantee that all monitoring managers would receive it. Following a Cisco BroadWorks server restart,
when problems are encountered, the agent generates new notifications. If they share the same correlation
parameter, they might look like updates of past notifications to the monitoring managers.
Monitoring managers should perform periodic lookups (for example, 15 minutes) to ensure they remain
synchronized.

4.3.2.5 Clear Alarm

Managers can clear any alarm in the Alarms table. To clear a specific alarm, the value of the
corresponding alarm clearAlarm column must be set to 1. When the agent receives such a request,
it notifies the originating component. The originating component is responsible to send back,
asynchronously, a message to the agent indicating that the alarm was cleared. The agent then sends an
alarm clear to all monitoring managers. When an alarm is manually cleared, its state should be Cleared.
It is also possible to clear an alarm using the CLI:
$ CLI/Monitoring/Alarms/AlarmsTable> clear 134
...Done

NOTE: Because the agent must request the clear to another component, there is absolutely no guarantee
that a request to clear an alarm results in a Cleared notification to be issued.

Figure 9: Clearing Alarm from Manager

4.3.2.6 Clearing the Alarms

It is possible to clear the alarm list from the agent through a unique SNMP operation. This has the same
effect as clearing every single alarm individually.
The entire alarm list can be reset by setting the integer value 1 on the following OID:
.iso.org.dod.internet.private.enterprises.broadsoft.broadworks.
common.alarms.resetAlarmsTable
OID: .1.3.6.1.4.1.6431.1.1.4.2

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 34
 The clearing of the Alarms table can also provisioned at the CLI:
$ CLI/Monitoring/Alarms/AlarmsTable> clearAll
WARNING: This will clear all currently active alarms. Every configured manager will
receive many notifications.
Please confirm (Yes, Y, No, N): y
...Done

NOTE: Resetting the entire alarm list might trigger as many notifications as there are active alarms. To
prevent the flooding of the monitoring managers, this operation is by default permitted only once every 30
seconds (configurable through the resendAllRequestPeriod property) for all monitoring managers.

4.3.2.7 Resending All Alarms in Alarms Table

In the event that a monitoring manager requires SNMP notifications to be sent to re-synchronize due to
an impossibility of synchronization based on the information contained in the Alarms table, it is possible to
have all the current alarms resent.
The entire alarm list can be resent through SNMP notifications by setting the address
and the port of a configured monitoring manager that uses alarms (format: host:port)
on the following OID:
.iso.org.dod.internet.private.enterprises.broadsoft.broadworks.
common.alarms.resendAlarmsTableOID:
.1.3.6.1.4.1.6431.1.1.4.3

Resending all alarms in the Alarms table can also be done at the CLI:
$ CLI/Monitoring/Alarms> resendAll 192.168.1.14 20001
...Done

NOTE: Resending all alarms of the Alarms table triggers as many notifications as there are active alarms.
To prevent the flooding of the target monitoring manager, this operation is by default permitted only once
every 30 seconds (configurable through the clearAllRequestPeriod property) per monitoring manager.

4.3.2.8 Last Modification Timestamp

Every time the Alarms table is modified, the agent updates a timestamp indicating the time at which the last
modification to the table was made. This timestamp is exposed and can be used by monitoring managers
in their effort to synchronize the table. Every time a monitoring manager wants to synchronize, it should
compare its copy of the last modification timestamp with the one on the server before traversing the Alarms
table. The timestamp is always set when the Cisco BroadWorks SNMP agent restarts, whether or not there
are alarms in the table.
Node Name:
.iso.org.dod.internet.private.enterprises.broadsoft.broadworks.
common.alarms.lastAlarmsTableModificationTimestampOID:
.1.3.6.1.4.1.6431.1.1.4.4

4.3.2.9 Polling
The agent does not notify monitoring systems when it suddenly dies. Monitoring systems should poll the
agent on a regular basis to ensure that it is still alive and that alarms reported earlier are still valid.

4.3.3 Notifications Parameterization

A weakness of the former SNMP agent implementation is the lack of contextualized parameters in
notifications. All notifications are sent with the same parameters and one has to read the Problem Text field
to understand what the root cause of the problem is.

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 35
 This verbose behavior is acceptable for human beings who read complex sentences. However, it makes
information systems parse the Problem Text field to gather the information it requires to deal with the
alarm.
Notification parameters solve this problem. In addition to existing generic parameters, new contextualized
parameters are added to notifications. For example, for connectivity problems, a new parameter
npRemoteAddress is added. Notifications can have as many parameters as required to provide adequate
context to network managers. Each fault definition in the MIBs defines the parameters they carry.
The following example shows how the bwExternalAuthenticationUnknownUser carries the npUserName
and npDomain parameters when it is sent.
bwExternalAuthenticationUnknownUser NOTIFICATION-TYPE
OBJECTS { identifier, timestamp, alarmName, systemName, severity, component,
subcomponent, problemText, recommendedActionsText, npUserName, npDomain}
STATUS current
DESCRIPTION
"..."
::= { systemFaults 3583 }

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 36
5 External Subagents Integration

This section provides a list of SNMP subagents for which Cisco BroadWorks acts as proxy.

5.1 High-level Description

The integration of the SNMP subagents is performed through a master/proxy agent with subagent
architecture.
The Cisco BroadWorks agent acts as a master/proxy agent to the other subagent(s) and provides a single
point of access for managers. The master/proxy agent functionalities are as follows:
• Receives requests from managers
• Forwards requests to appropriate subagent
• Receives responses from subagent
• Forwards responses to managers
• Forwards traps to managers
The Cisco BroadWorks master SNMP agent listens for traps on port 162, thereby allowing any agent that is
sending traps to port 162 to be captured by the master agent and forwarded to the appropriate managers.
This is the case with the TimesTen application, which forwards traps to port 162 even though it is not
defined as a subagent for the Network Server (NS) and the Application Server (AS). Note that TimesTen is
not part of the Media Server (MS).
The authorization list for manager(s) accessing the system is managed through the existing Cisco
BroadWorks SNMP agent access control list.
This feature is designed for network and system operators to monitor hardware and software devices on
which Cisco BroadWorks applications are running and is available for Cisco BroadWorks servers.

5.2 Integrated Third-Party Subagents

Cisco BroadWorks integrates the following subagents:
• Solaris MIB II subagent
• TimesTen subagent (alarms only)

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 37
6 Fault Thresholding and Suppression

Fault suppression and threshold can be viewed as fault filters. This feature provides fault filtering at the
Cisco BroadWorks SNMP agent level. The Cisco BroadWorks servers continue to generate faults. They
send the faults to their SNMP agent (using a proprietary protocol) and the agent processes them. When
the SNMP agent receives a fault, it performs the following tasks:
1) Logs the fault to a local file.
2) Sends the fault to a trap server, which then sends it to all registered trap clients (such as Cisco
BroadWorks CLI sessions).
3) Sends an SNMP trap to the provisioned managers.
This feature only performs fault filtering for tasks one (1) and three (3) above. Therefore, fault filtering has
no impact on trap clients waiting for faults.
The feature only provides a mechanism to filter faults generated by Cisco BroadWorks applications (such
as the Application Server Execution Server, Application Server Provisioning Server, Network Server
Execution Server, Network Server Provisioning Server, and so on) and Cisco BroadWorks process
monitors. In other words, this feature provides filtering for faults defined under the Cisco Object Identifier
(OID).
Fault filtering occurs at the SNMP agent-level (not by cluster).

6.1 Trap Lists

Currently, each Cisco BroadWorks server comes with XML-encoded trap list files which define all the traps
that this server can generate. These files are:
Table 12: Traplist Files
Cisco BroadWorks Server Traplist File Name

Common to all servers /usr/local/broadworks/bw_base/conf/commontraplist.xml /usr/local/broadworks/bw_base/conf/

configdtraplist.xml

Access Mediation Server

Application Server /usr/local/broadworks/bw_base/conf/executiontraplist.xml /usr/local/broadworks/bw_base/conf/

ocstraplist.xml /usr/local/broadworks/bw_base/conf/provisioningtraplist.xml /usr/local/broadworks/
bw_base/web/conf/containertraplist.xml

Call Detail Server /usr/local/broadworks/bw_base/conf/cdstraplist.xml /usr/local/broadworks/bw_base/conf/

webcontainertraplist.xml

Element Management System /usr/local/broadworks/bw_base/conf/emstraplist.xml /usr/local/broadworks/bw_base/

conf/ocstraplist.xml /usr/local/broadworks/bw_base/web/conf/containertraplist.xml Profile
Server /usr/local/broadworks/bw_base/conf/pstraplist.xml /usr/local/broadworks/bw_base/
confwebcontainertraplist.xml

Media Server /usr/local/broadworks/bw_base/conf/mstraplist.xml

Network Server /usr/local/broadworks/bw_base/conf/nsexecutiontraplist.xml /usr/local/broadworks/bw_base/

conf/nsportaltraplist.xml /usr/local/broadworks/bw_base/conf/nsprovisioningtraplist.xml /usr/local/
broadworks/bw_base/conf/webcontainertraplist.xml

Profile Server /usr/local/broadworks/bw_base/conf/pstraplist.xml /usr/local/broadworks/bw_base/

confwebcontainertraplist.xml

Xtended Services Platform /usr/local/broadworks/bw_base/conf/xsptraplist.xml /usr/local/broadworks/bw_base/conf/

ocstraplist.xml /usr/local/broadworks/bw_base/conf/webcontainertraplist.xml /usr/local/
broadworks/bw_base/conf/ucconnecttraplist.xml (NOTE: This file appears once the application is
activated.)

Although trap definitions are in every component's fault MIBs, some information is also defined in the trap
list file. The trap list file hosts the problem text and recommended action text for all traps originating from a

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 38
 Cisco BroadWorks component. This text is defined in a separate file to allow internationalization of these
fields if required.
Traplist entry example:
<trap>
<name>bwTrunkGroupCapacityExceeded</name>
<problemType>0</problemType>
<problemText>The capacity of a trunk group was exceeded.
Service Provider / Enterprise Name: %npServiceProviderId%
Group Name: %npGroupName%
Trunk Group Name: %npTrunkGroupName%</problemText>
<recommendedAction>Increase the Maximum Active Calls Allowed parameter of the
associated trunk group.
Maximum Active Calls Allowed: *
Maximum Outgoing Active Calls Allowed: *
Maximum Incoming Active Calls Allowed: *
Bursting Maximum Active Calls Allowed *
Bursting Maximum Outgoing Active Calls Allowed: *
Bursting Maximum Incoming Active Calls Allowed: *
<recommendedActionParam doc="Maximum Active Calls Allowed parameter" />
<recommendedActionParam doc="Maximum Outgoing Active Calls Allowed parameter" /
>
<recommendedActionParam doc="Maximum Incoming Active Calls Allowed parameter" /
>
<recommendedActionParam doc="Bursting Maximum Active Calls Allowed parameter" /
>
<recommendedActionParam doc="Bursting Maximum Outgoing Active Calls Allowed
parameter" />
<recommendedActionParam doc="Bursting Maximum Incoming Active Calls Allowed
parameter" />
</recommendedAction>
</trap>

Variables in the problem text must be valid notification parameters described in the BroadworksFault.mib
file. Conversely, the wildcard character for the recommended action text is always the asterisk (*). If this
file must be internationalized, only the problemText and recommendedAction must be translated. The
recommendedActionParam is for internal use and does not appear in the trap sent to the monitoring
managers. When internationalizing, the problem text variables ( between percent (%) signs) should not be
modified.

6.2 Trap Filters

Trap filter files are XML-based files. The purpose of this file is different from the trap lists. Rather than
defining trap information, they define fault filters that can be used to throttle or suppress faults sent by the
SNMP agent.
Trap filters are defined in the following files:
Table 13: Trap Filter Files
BroadWorks Server Trap Filter File Name

Access Mediation Server

Application Server /usr/local/broadworks/bw_base/conf/astrapfilter.xml /usr/local/broadworks/bw_base/conf/

ocstrapfilter.xml

Call Detail Server /usr/local/broadworks/bw_base/conf/cdstrapfilter.xml

Element Management System /usr/local/broadworks/bw_base/conf/emstrapfilter.xml /usr/local/broadworks/bw_base/conf/

ocstrapfilter.xml

Media Server /usr/local/broadworks/bw_base/conf/mstrapfilter.xml

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 39
 BroadWorks Server Trap Filter File Name

Network Server /usr/local/broadworks/bw_base/conf/nstrapfilter.xml

Profile Server /usr/local/broadworks/bw_base/conf/pstrapfilter.xml /usr/local/broadworks/bw_base/conf/

ocstrapfilter.xml

Xtended Services Platform /usr/local/broadworks/bw_base/conf/xsptrapfilter.xml /usr/local/broadworks/bw_base/conf/

ocstrapfilter.xml

The trap filter files are preserved during a BroadWorks upgrade so that filters defined by customers can
remain unchanged after an upgrade.
Details on the Document Type Definition (DTD) for trap filter files follow.
<?xml version='1.0' encoding="UTF-8"?>

<!ELEMENT trapFilter (defaultFilter?, filter*)>

<!ELEMENT defaultFilter (active, maxNumTrapsPerTimePeriod, timePeriodInSeconds?,

minSeverity?)>

<!ELEMENT filter (name, active, maxNumTrapsPerTimePeriod, timePeriodInSeconds?,

problemTextVarNum1?, problemTextVarNum2?, problemTextVarNum3?, problemTextVarNum4?,
problemTextVarNum5?)>

<!ELEMENT name (#PCDATA)>

<!ELEMENT active (false|true)>
<!ELEMENT maxNumTrapsPerTimePeriod (#PCDATA)>
<!ELEMENT timePeriodInSeconds (#PCDATA)>
<!ELEMENT minSeverity (0|1|2|3|4)>
<!ELEMENT problemTextVarNum1 (#PCDATA)>
<!ELEMENT problemTextVarNum2 (#PCDATA)>
<!ELEMENT problemTextVarNum3 (#PCDATA)>
<!ELEMENT problemTextVarNum4 (#PCDATA)>
<!ELEMENT problemTextVarNum5 (#PCDATA)>

>

Assuming that astrapfilter.xml contains the following trapFilter block:

<trapFilter>
<defaultFilter>
<active>false</active>
<maxNumTrapsPerTimePeriod>10</maxNumTrapsPerTimePeriod>
<timePeriodInSeconds>5</timePeriodInSeconds>
<minSeverity>1</minSeverity>
</defaultFilter>
<filter>
<name>bwSipRegistrationFailure</name>
<active>true</active>
<maxNumTrapsPerTimePeriod>0</maxNumTrapsPerTimePeriod>
</filter>
<filter>
<name>bwSipUnexpectedMessage</name>
<active>true</active>
<maxNumTrapsPerTimePeriod>2</maxNumTrapsPerTimePeriod>
<timePeriodInSeconds>5</timePeriodInSeconds>
</filter>
<filter>
<name>bwNSSynchronizationFailure</name>
<active>true</active>
<maxNumTrapsPerTimePeriod>1</maxNumTrapsPerTimePeriod>
<timePeriodInSeconds>10</timePeriodInSeconds>

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 40
 <problemTextVarNum1>3</problemTextVarNum1>
</filter>
<filter>
<name>bwSMDIOperationFailure</name>
<active>true</active>
<maxNumTrapsPerTimePeriod>10</maxNumTrapsPerTimePeriod>
<timePeriodInSeconds>60</timePeriodInSeconds>
<problemTextVarNum1>2</problemTextVarNum1>
<problemTextVarNum2>3</problemTextVarNum2>
</filter>
</trapFilter>

The Application Server SNMP agent filters faults as follows:

• In general, no more than 10 faults of a type per sliding period of five seconds are sent out over the
SNMP interface, unless fault-specific filters exist for some faults. However, this system default threshold
is inactive, so the SNMP agent simply ignores this threshold definition. Also, if the default fault filter is
activated, only faults with a severity of low (1) or greater are sent out. Informational faults are discarded.
• All bwSipRegistrationFailure faults are filtered out and none are sent over the SNMP interface.
• The SNMP agent only sends a maximum of two bwSipUnexpectedMessage faults per sliding period of
five seconds.
• For a given Network Server address (<problemTextVarNum1>3</problemTextVarNum1>), the SNMP
agent sends a maximum of one bwNSSynchronizationFailure fault per sliding period of ten seconds.
• For a given phone number (<problemTextVarNum1>2</problemTextVarNum1>) and a given failure
reason (<problemTextVarNum2>3</problemTextVarNum2>), the SNMP agent sends a maximum of ten
bwSMDIOperationFailure faults per sliding period of one minute.
The above feature behavior is the same on all types of BroadWorks servers.

6.3 Filtering Considerations

• Cisco does not provide any predefined fault suppression or threshold rules in the various trapfilter files
besides the system default fault threshold (set to "inactive").
• Fault filtering works on a per-node basis and not on a per-cluster basis. This means that if a filter
specifies that fault X should be discarded if the generation rate exceeds five faults per second, no fault
is discarded if each server in a cluster has an actual rate of three faults per second, even though the
aggregated rate for this two-node cluster is actually of six faults per second.
• The data that the SNMP agent uses to filter out faults is not persisted. This means that after the SNMP
agent restarts, filtering is reinitialized using the filters defined in the trapfilter file, and faults are sent out
until the various thresholds are reached once more.
• For a given fault name, it is possible to define more than one filter. In this case, all filters are evaluated
and if at least one does not allow the fault to be sent, then the fault is not sent.
• If maxNumTrapsPerTimePeriod is set to 0 (zero) or a negative integer value, then the fault (matching
the other filter criteria, if some are specified) is suppressed. In such a case, the timePeriodInSeconds
value is ignored.
• If maxNumTrapsPerTimePeriod is a positive integer greater than zero, then the fault (matching the
other filter criteria, if some are specified) has a threshold. In such a case, the timePeriodInSeconds
must contain a positive integer value greater than zero.
• Fault threshold uses the concept of sliding time period. When the agent receives a fault, it checks
how many alarms matching the threshold rule(s) were received in the previous timePeriodInSeconds
seconds. If that number exceeds maxNumTrapsPerTimePeriod, then the alarm is not sent over the
SNMP interface. The agent remembers that this fault was received, for proper filtering when the next
one comes.
• A maximum of five problem text variable filters can be defined per threshold. When the agent compares
the content of problem text variables for filtering purposes, the comparison is not case sensitive.

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 41
 • If a fault filter is provisioned with an invalid fault name (that is, the fault name does not exist in the
system), the filter is accepted but it remains in state invalid.
• If the filtered fault is an alarm, the alarm is still added to the Alarms table.

6.4 Filtered Faults Notification

The fault named bwAlarmsDiscarded is common to all servers. The SNMP agent generates this fault every
15 minutes (15 minutes after SNMP agent restart and every 15 minutes thereafter) if at least one fault
was discarded in the past 15 minutes. If this is the case, the fault gives a list of all the alarms that were
discarded in the past 15 minutes along with the number of times each fault was discarded.
If the data to be included in the alarm gets too big, more than one fault is generated. The threshold is set to
no more than 1024 characters in the list (and count) of faults discarded.

6.5 Provisioning Fault Filters

The SNMP agent stores all fault filters in a trapfilter file, as described in the previous sections. To provision
fault filters, an administrator can:
• Use the SNMP interface to ask the SNMP agent to add, delete, get, and set fault filters.
• Use the Cisco BroadWorks CLI interface to add, delete, get, and set fault filters.
These methods are explained in detail in the following subsections.

6.5.1 SNMP Provisioning

The definition of fault filters and their configuration are part of the BroadworksMaintenance.mib. Therefore,
any network element that has an authorized SNMP connectivity to the server's SNMP agent can configure
fault filters. Fault filters can only be provisioned if the SNMP agent is running.

6.5.2 CLI Provisioning

It is also possible to add, delete, get, and set fault filters using the Cisco BroadWorks CLI. To provision and
configure fault filters using the CLI, the SNMP agent on the server must be running. The following is an
example (on an Application Server) showing how fault filters can be managed using the CLI.
AS_CLI/Monitoring/Alarm/Threshold> get
Index AlarmName MaxNumTrapsPerTimePeriod TimePeriodInSeconds
Var1 Var2 Var3 Var4 Var5 Status
=================================================================
======================================

0 entry found.

AS_CLI/Monitoring/Alarm/Threshold> %% No more than 4 bwNSSynchronizationFailure alarms

per sliding period of 10 seconds.

AS_CLI/Monitoring/Alarm/Threshold> add bwNSSynchronizationFailure 4 10 active

...Done

AS_CLI/Monitoring/Alarm/Threshold> %% Suppress all bwSipRegistrationFailure alarms.

AS_CLI/Monitoring/Alarm/Threshold> add bwSipRegistrationFailure 0 1 active

...Done

AS_CLI/Monitoring/Alarm/Threshold/Default> %% Limit each alarm in system to 100 alarms

of each type per hour.

AS_CLI/Monitoring/Alarm/Threshold/Default> set maxNumTrapsPerTimePeriod 100

timePeriodInSeconds 3600 status active minSeverity low

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 42
 ...Done

AS_CLI/Monitoring/Alarm/Threshold> %% For the same Endpoint ID (problem text variable

position 1) and Device Address (problem text variable position 2), limit the number of
bwMGCPReTransmissionTimeout alarms to 2 per sliding period of 30 seconds.

AS_CLI/Monitoring/Alarm/Threshold> add bwMGCPReTransmissionTimeout 2 30 active

problemTextVariable1 1 problemTextVariable2 2
...Done

AS_CLI/Monitoring/Alarm/Threshold> get
Index AlarmName MaxNumTrapsPerTimePeriod TimePeriodInSeconds
Var1 Var2 Var3 Var4 Var5 Status
===================================================================================
====================================
1 bwNSSynchronizationFailure 4 10

active
2 bwSipRegistrationFailure 0 1

active
4 bwMGCPReTransmissionTimeout 2 30
1 2 active

3 entries found.

AS_CLI/Monitoring/Alarm/Threshold/Default> get
maxNumTrapsPerTimePeriod = 100
timePeriodInSeconds = 3600
status = active
minSeverity = low

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 43
7 Organization of Cisco BroadWorks MIB Files

This section describes the organization of Cisco BroadWorks MIB files by server type. In addition, the
range of notification OIDs currently in use by each MIB file is identified.

NOTE: fault IDs are uniquely defined within Cisco BroadWorks. All faults have the following root OID:
.1.3.6.1.4.1.6431.1.1.1

You can click on the link of each MIB for a description of the MIB.

7.1 MIB files for the Network Function Manager

MIB files for the Network Function Manager.
Table 14: MIB Files and OID Value Ranges for the Network Function Manager.
MIB File Application Notification ID Range

BroadworksConfigurationFault MIB BroadWorks Platform 6101 through 6109

BroadworksFault MIB 2 through 11759

BW-LicenseManagerFault MIB 15801 through 15813

BW-FileTransferFault MIB File Transfer Application 17701 through 17702

BW-LicenseControllerFault MIB License Controller Application 15401 through 15412

BW-MDBManagementFault MIB MDB Management Application 16401 through 16409

BW-NetworkMonitoringFault MIB Network Monitoring Application 16201 through 16212

BW-NodeControllerFault MIB Node Controller Application 15601 through 15610

BW-NodeLifecycleManagerFault MIB Node Lifecycle Manager Application 17301 through 17308

BW-SoftwareManagementFault MIB Software Management Application 17901 through 17916

BW-WebContainerFault MIB Web Container Application 6001 through 6013

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 44
8 Cisco BroadWorks MIB Files

This section describes all Cisco BroadWorks MIBs in alphabetical order.

8.1 BroadworksConfigurationFault MIB

This section presents SNMP traps (notifications and alarms) for the BroadworksConfigurationFault MIB
grouped by component.
The MIB defines the faults for the Configuration subsystem.
Applicable server(s):
Network Function Manager.

8.1.1 SNMP Traps For Component: processmonitor

The table that follows describes the SNMP traps for the processmonitor subcomponent of the
BroadworksConfigurationFault MIB.
Table 15: SNMP Traps For BroadworksConfigurationFault:processmonitor
Alarm Name Attributes Values

bwPMconfigdLaunched Problem Type Notification

OID 6101

Status current

Severity Range informational

Description This notification indicates that the configuration agent has been
started.

Problem Text configd started.

Recommended
Action(s)

Correlation Rules bwPMconfigdLaunched, bwPMconfigdShutDown,

bwPMconfigdRestarted, and bwPMconfigdDeath can be
correlated into a single alarm. These events have to be
considered as a transition of the state machine for the
management of the configd process.

bwPMconfigdShutDown Problem Type Notification

OID 6102

Status current

Severity Range informational

Description This notification indicates that the configuration agent has been
shutdown.

Problem Text configd shutdown.

Recommended
Action(s)

Correlation Rules bwPMconfigdLaunched, bwPMconfigdShutDown,

bwPMconfigdRestarted, and bwPMconfigdDeath can be
correlated into a single alarm. These events have to be
considered as a transition of the state machine for the
management of the configd process.

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 45
 Alarm Name Attributes Values

bwPMconfigdRestarted Problem Type Notification

OID 6103

Status current

Severity Range informational

Description This notification indicates that the configuration agent has been
restarted.

Problem Text configd restarted.

Recommended
Action(s)

Correlation Rules bwPMconfigdLaunched, bwPMconfigdShutDown,

bwPMconfigdRestarted, and bwPMconfigdDeath can be
correlated into a single alarm. These events have to be
considered as a transition of the state machine for the
management of the configd process.

bwPMconfigdDeath Problem Type Notification

OID 6104

Status current

Severity Range critical

Description This notification indicates that the configuration agent as

abnormally terminated.

Problem Text configd terminated.

Recommended Make sure configd gets restarted

Action(s)

Correlation Rules bwPMconfigdLaunched, bwPMconfigdShutDown,

bwPMconfigdRestarted, and bwPMconfigdDeath can be
correlated into a single alarm. These events have to be
considered as a transition of the state machine for the
management of the configd process.

8.1.2 SNMP Traps For Component: configd

The table that follows describes the SNMP traps for the configd subcomponent of the
BroadworksConfigurationFault MIB.
Table 16: SNMP Traps For BroadworksConfigurationFault:configd
Alarm Name Attributes Values

bwConfigurationChanged Problem Type Notification

OID 6105

Status current

Severity Range informational

Description This notification indicates that the configuration agent as loaded

a new configuration version.

Problem Text Configuration version %npConfigVersion% loaded.

Recommended
Action(s)

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 46
 Alarm Name Attributes Values

Correlation Rules

bwConfigurationFailed Problem Type Notification

OID 6106

Status current

Severity Range high

Description This notification indicates that the configuration agent as failed

to loaded a new configuration version.

Problem Text Configuration version %npConfigVersion% failed.

Recommended
Action(s)

Correlation Rules

bwConfigReplicationOffline Problem Type Alarm

OID 6108

Status current

Severity Range high

Description This alarm indicates that the configuration replication is currently

offline.

Problem Text Configuration replication is offline.

Recommended
Action(s)

Correlation Rules

bwConfigReplicationFailed Problem Type Notification

OID 6109

Status current

Severity Range high

Description This notification indicates that the master's configuration could

not be properly replicated.

Problem Text The master's configuration could not be properly replicated.

Recommended
Action(s)

Correlation Rules

8.2 BroadworksFault MIB

This section presents SNMP traps (notifications and alarms) for the BroadworksFault MIB grouped by
component.
This MIB defines management information that is common to all elements in a Broadworks system.
Applicable server(s):
Network Function Manager.

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 47
8.2.1 SNMP Traps For Component: unspecified
The table that follows describes the SNMP traps for the unspecified subcomponent of the BroadworksFault
MIB.
Table 17: SNMP Traps For BroadworksFault:unspecified
Alarm Name Attributes Values

bwGeneralSoftwareError Problem Type Notification

OID 5

Status current

Severity Range medium-high

Description This software error indicates that an unspecified software error

has occurred.

Problem Text Unexpected software error occurred during processing.

Stack Trace:
%npStackTrace%

Recommended Contact BroadSoft Support Engineer.

Action(s)

Correlation Rules

bwServerStateTransition Problem Type Notification

OID 12

Status current

Severity Range informational

Description Reports a BroadWorks server state transition.

Problem Text Server administrative state change.

Old Administrative State: %npOldAdministrativeState%,
New Administrative State: %npNewAdministrativeState%

Recommended
Action(s)

Correlation Rules It is recommended to clear all alarms associated with a network

element whenever there is an NE transition to the enable state,
since the network element, itself, will in this case automatically
clear all internal error conditions.

bwAlarmsDiscarded Problem Type Notification

OID 41

Status current

Severity Range low

Description Provides a complete list of all the alarms that the SNMP
agent discarded in the past 15 minutes either because they
are suppressed or because they exceeded their predefined
threshold criteria.

Problem Text The following alarms were discarded during the 15 minutes
period ending at: %npTimestamp%

%npAlarmList%

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 48
 Alarm Name Attributes Values

Recommended
Action(s)

Correlation Rules

bwApplicationStateTransition Problem Type Notification

OID 52

Status current

Severity Range informational

Description Reports an application's administrative or effective state

transition.

Problem Text Application State Changed

Application Name: %npApplicationName%,
Old Administrative State: %npOldAdministrativeState%,
New Administrative State: %npNewAdministrativeState%,
Old Effective State: %npOldEffectiveState%,
New Effective State: %npNewEffectiveState%

Recommended
Action(s)

Correlation Rules

bwExtremeOverload Problem Type Notification

OID 80

Status current

Severity Range high

Description Queue dropped event because of extreme overload.

Problem Text Queue dropped event because of extreme overload.

Queue name: %npQueueName%
Reason: %npExtremeOverloadReason%

Recommended
Action(s)

Correlation Rules

bwCPEDeviceConfigurationDeviceReset Problem Type Notification

OID 3572

Status current

Severity Range medium

Description An IP phone could not be reset.

Problem Text An IP phone could not be reset.

Device Name: %npDeviceName%
Remote Host: %npRemoteAddress%

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 49
 Alarm Name Attributes Values

Recommended Use one of the following steps to troubleshoot the problem:

Action(s)
1- Check that the phone is on, or
2- Check that the communication to the phone is up.

Correlation Rules

8.2.2 SNMP Traps For Component: processmonitor

The table that follows describes the SNMP traps for the processmonitor subcomponent of the
BroadworksFault MIB.
Table 18: SNMP Traps For BroadworksFault:processmonitor
Alarm Name Attributes Values

bwPMtomcatLaunched Problem Type Notification

OID 6

Status current

Severity Range informational

Description This notification indicates that the Tomcat server has been
started.

Problem Text tomcat started.

Recommended
Action(s)

Correlation Rules bwPMtomcatLaunched, bwPMtomcatShutDown,

bwPMtomcatStarted, and bwPMtomcatDeath can be correlated
into a single notification. These events have to be considered
as a transition of the state machine for the management of the
Tomcat process running on some of the BroadWorks servers.

bwPMtomcatShutDown Problem Type Notification

OID 7

Status current

Severity Range informational

Description This notification indicates that the Tomcat server has been
manually shut down.

Problem Text tomcat shut down.

Recommended
Action(s)

Correlation Rules bwPMtomcatLaunched, bwPMtomcatShutDown,

bwPMtomcatStarted, and bwPMtomcatDeath can be correlated
into a single notification. These events have to be considered
as a transition of the state machine for the management of the
Tomcat process running on some of the BroadWorks servers.

bwPMtomcatRestarted Problem Type Notification

OID 8

Status current

Severity Range informational

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 50
 Alarm Name Attributes Values

Description This notification provides the date and time of the Tomcat server
restart.

Problem Text tomcat restarted.

Recommended Log in BroadWorks.

Action(s)

Correlation Rules bwPMtomcatLaunched, bwPMtomcatShutDown,

bwPMtomcatStarted, and bwPMtomcatDeath can be correlated
into a single notification. These events have to be considered
as a transition of the state machine for the management of the
Tomcat process running on some of the BroadWorks servers.

bwPMtomcatDeath Problem Type Notification

OID 9

Status current

Severity Range critical

Description This notification provides the date and time of the Tomcat server
death.

Problem Text tomcat terminated.

Recommended Make sure tomcat gets restarted

Action(s)

Correlation Rules bwPMtomcatLaunched, bwPMtomcatShutDown,

bwPMtomcatStarted, and bwPMtomcatDeath can be correlated
into a single notification. These events have to be considered
as a transition of the state machine for the management of the
Tomcat process running on some of the BroadWorks servers.

bwSystemHealthReport Problem Type Notification

OID 10

Status current

Severity Range informational-critical

Description System health report. See Appendix B of the BroadWorks

Faults and Alarms Interface Specification for a description of the
bwSystemHealthReport Alarm Problem Text.

Problem Text %npReport%

Recommended
Action(s) *

Correlation Rules The system health should always be at the latest state/severity
reported by a bwSystemHealthReport trap. For example a
critical alarm raised through bwSystemHealthReport could
be cleared automatically in case the next severity received is
informational.

bwDatabaseSyncReport Problem Type Notification

OID 11

Status current

Severity Range informational

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 51
 Alarm Name Attributes Values

Description This notification is generated by the synchcheck_basic.pl

command. It provides a detail reports on database differences.

Problem Text %npReport%

Recommended
Action(s) *

Correlation Rules

bwCPUIdleTimeLimitReached Problem Type Notification

OID 17

Status current

Severity Range informational-critical

Description CPU idle time monitoring.

Problem Text Average CPU idle time is %npCpuIdleTimePercentage

%% where the %npThresholdName% threshold is
%npCurrentThresholdValue%%

Recommended This may be an intermittent issue. Verify by performing the

Action(s) following:
- Monitor real-time server CPU usage using "vmstat 1 10".
- Identify high running process using "top".
- If "sar" is enabled, check historic CPU usage statistics.

If high CPU usage persists, issue the following command and

send the output to BroadSoft support:
$ tech-support

Correlation Rules It is recommended to always keep the highest severity value for
this notification until it is cleared.

bwMemoryLimitReached Problem Type Notification

OID 18

Status current

Severity Range critical

Description This notification is generated by the bwCPUMon script. It

monitors the heap, CPU, and I/O usage for the entire system
and for the Execution Server process (Application Server only).

Problem Text %npReport%

Recommended Issue the following command and send the output to BroadSoft
Action(s) support:
$ tech-support

Correlation Rules It is recommended to always keep the highest severity value for
this notification until it is cleared.

bwPMremotexlaLaunched Problem Type Notification

OID 21

Status current

Severity Range informational

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 52
 Alarm Name Attributes Values

Description This notification indicates that the remote XLA server has been
started.

Problem Text remotexla started.

Recommended
Action(s)

Correlation Rules bwPMremotexlaLaunched, bwPMremotexlaShutDown,

bwPMremotexlaRestarted, and bwPMremotexlaDeath can
be correlated into a single notification. These events have
to be considered as a transition of the state machine for the
management of the remoteXLA process running on some of the
BroadWorks servers.

bwPMremotexlaShutDown Problem Type Notification

OID 22

Status current

Severity Range informational

Description This notification indicates that the remote XLA server has been
manually shut down.

Problem Text remotexla shut down.

Recommended
Action(s)

Correlation Rules bwPMremotexlaLaunched, bwPMremotexlaShutDown,

bwPMremotexlaRestarted, and bwPMremotexlaDeath can
be correlated into a single notification. These events have
to be considered as a transition of the state machine for the
management of the remoteXLA process running on some of the
BroadWorks servers.

bwPMremotexlaRestarted Problem Type Notification

OID 23

Status current

Severity Range informational

Description This notification provides the date and time of the remote XLA
server restart.

Problem Text remotexla restarted.

Recommended Log in BroadWorks.

Action(s)

Correlation Rules bwPMremotexlaLaunched, bwPMremotexlaShutDown,

bwPMremotexlaRestarted, and bwPMremotexlaDeath can
be correlated into a single notification. These events have
to be considered as a transition of the state machine for the
management of the remoteXLA process running on some of the
BroadWorks servers.

bwPMremotexlaDeath Problem Type Notification

OID 24

Status current

Severity Range critical

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 53
 Alarm Name Attributes Values

Description This notification provides the date and time of the remote XLA
server death.

Problem Text remotexla terminated.

Recommended Make sure remotexla gets restarted

Action(s)

Correlation Rules bwPMremotexlaLaunched, bwPMremotexlaShutDown,

bwPMremotexlaRestarted, and bwPMremotexlaDeath can
be correlated into a single notification. These events have
to be considered as a transition of the state machine for the
management of the remoteXLA process running on some of the
BroadWorks servers.

bwPMhttpdLaunched Problem Type Notification

OID 48

Status current

Severity Range informational

Description Apache started.

Problem Text apache started.

Recommended
Action(s)

Correlation Rules

bwPMhttpdShutDown Problem Type Notification

OID 49

Status current

Severity Range informational

Description Apache manually shut down.

Problem Text apache shut down.

Recommended
Action(s)

Correlation Rules

bwPMhttpdRestarted Problem Type Notification

OID 50

Status current

Severity Range informational

Description Apache restarted.

Problem Text apache restarted.

Recommended Log in BroadWorks.

Action(s)

Correlation Rules

bwPMhttpdDeath Problem Type Notification

OID 51

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 54
 Alarm Name Attributes Values

Status current

Severity Range critical

Description Apache process unexpectedly died.

Problem Text apache terminated.

Recommended Make sure apache gets restarted

Action(s)

Correlation Rules

bwMaintenanceTaskFailure Problem Type Notification

OID 65

Status current

Severity Range medium

Description A maintenance task failed to execute.

Problem Text The maintenance task %npTaskName% failed to execute

Recommended
Action(s) *

Correlation Rules

bwSystemBackwardTimeDrift Problem Type Notification

OID 73

Status current

Severity Range high

Description The system time has gone backward, which can result in
software malfunction.

Problem Text The system time has gone backward, which can result in
software malfunction.

Recommended Verify that BroadWorks applications are working as expected, if

Action(s) this is not the case, restart BroadWorks.

Correlation Rules

bwOSMisconfiguration Problem Type Notification

OID 90

Status current

Severity Range high-critical

Description This notification indicates that an OS parameter is not set to

recommended value.

Problem Text Problem detail: %npMessage%

Recommended *
Action(s)

Correlation Rules

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 55
8.2.3 SNMP Traps For Component: database
The table that follows describes the SNMP traps for the database subcomponent of the BroadworksFault
MIB.
Table 19: SNMP Traps For BroadworksFault:database
Alarm Name Attributes Values

bwCentralizedDatabaseConnectivity Problem Type Alarm

Failure
OID 60

Status current

Severity Range high

Description A connectivity failure is detected on the connection to a

centralized database site for a given site.

Problem Text A connectivity failure occurred for Database %npDatabaseName

% on site %npSite%.

Recommended Verify that the Database Server(s) on the problematic sites are
Action(s) running and verify the IP connectivity between the local node to
the Database Server site on the configured port.

Correlation Rules

bwCentralizedDatabaseSchemaFailure Problem Type Alarm

OID 67

Status current

Severity Range high

Description A schema access failure is detected to a centralized database

site for a given schema.

Problem Text A schema access failure occurred for schema

%npSchemaInstanceName% (state =
%npSchemaInstanceState%).

Recommended Make sure the application is connected to a Read/Write

Action(s) Centralized Database site.

Correlation Rules

bwNetworkDatabaseNodeConnectivity Problem Type Alarm

Failure
OID 77

Status current

Severity Range high

Description This notification indicates that the application has no

connectivity to a database node.

Problem Text A connectivity failure is detected on the connection to a Network

Database node:
Database: %npDatabaseName%
Node: %npDatabaseNode%.

Recommended Verify that the Network Database node is running and verify the
Action(s) IP connectivity between the server reporting the fault and the
database node. Verify the database node hostname and port
configuration.

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 56
 Alarm Name Attributes Values

Correlation Rules

bwNetworkDatabaseClusterConnectivity Problem Type Alarm

Failure
OID 78

Status current

Severity Range critical

Description This notification indicates that the application has no

connectivity to all the database nodes.

Problem Text Connectivity lost with all the Network Database nodes for
database %npDatabaseName%
Nodes: %npDatabaseNode%.

Recommended Verify that the Network Database nodes are running and verify
Action(s) the IP connectivity between the server reporting the fault and all
the database nodes. Verify the database nodes hostname and
port configuration.

Correlation Rules

bwNetworkDatabaseSchemaFailure Problem Type Alarm

OID 79

Status current

Severity Range high

Description This notification indicates that a schema instance is not able to

communicate to any node of the Network Database.

Problem Text A schema access failure is detected to Network

Database %npDatabaseName% for schema instance
%npSchemaInstanceName%.

Recommended Verify that the Network Database nodes are running and verify
Action(s) the IP connectivity between the server reporting the fault and
all the database nodes. Verify the database nodes hostname
and port configuration. Verify the schema instance configuration
to make sure it uses the correct database. Verify if the schema
instance is in state OFFLINE in the Network Database.

Correlation Rules

bwCouchbaseNodeConnectivityFailure Problem Type Alarm

OID 81

Status current

Severity Range low, high, critical

Description This notification indicates that the application has no

connectivity to one or more Couchbase nodes.

Problem Text A connectivity failure is detected on the connection to one or

more Couchbase nodes:
Node(s): %npCouchbaseNodes%

Recommended
Action(s)

Correlation Rules

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 57
 Alarm Name Attributes Values

bwCentralizedDatabaseListenerFailure Problem Type Alarm

OID 82

Status current

Severity Range high

Description Cannot connect to Oracle Database Listener.

Problem Text A failure occured connecting to listener at %npAddress%.

Recommended Make sure the listener is working properly on Database site

Action(s)

Correlation Rules

bwCentralizedDatabaseMaxConnections Problem Type Alarm

Reached
OID 83

Status current

Severity Range high

Description Maximum number of borrowable connections has been reached.

Problem Text Maximum number of borrowable connections has been reached

(%npConnectionCount% connections)

Recommended
Action(s)

Correlation Rules

bwCentralizedDatabaseNewConnection Problem Type Alarm

Failure
OID 84

Status current

Severity Range high

Description Unable to create a new database connection.

Problem Text The persistency monitoring framework failed to create a new

database connection on %npSite%

Recommended Make sure all listeners are working and responsive on Database
Action(s) site

Correlation Rules

bwCentralizedDatabasePoolFailure Problem Type Alarm

OID 87

Status current

Severity Range critical

Description Cannot initialize the specified connection pool, reducing the

initPoolSize and restarting the application is required.

Problem Text Cannot initialize the %npConnectionPoolName% connection

pool.

Recommended Reduce the value of the initPoolSize parameter and restart the
Action(s) application to free connections.

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 58
 Alarm Name Attributes Values

Correlation Rules

8.2.4 SNMP Traps For Component: sip

The table that follows describes the SNMP traps for the sip subcomponent of the BroadworksFault MIB.
Table 20: SNMP Traps For BroadworksFault:sip
Alarm Name Attributes Values

bwSipTcpExceededMax Problem Type Notification

OID 31

Status current

Severity Range low

Description SIP TCP connections reclaimed to avoid exceeding the

maximum number of SIP TCP connections.

Problem Text SIP TCP connections reclaimed to avoid exceeding the

maximum number of SIP TCP connections.

Recommended No action is typically required. Adjust the following configuration

Action(s) values as needed: maxNumberTcpSocketsPerSystem,
autoDiscardStaleConnections, and
staleConnectionTimerInMinutes.

Correlation Rules

bwSipTcpExceededMaxPerPeer Problem Type Notification

OID 32

Status current

Severity Range low

Description SIP TCP connections associated with the IP address were

reclaimed to avoid exceeding the maximum number of SIP TCP
connections per peer.

Problem Text SIP TCP connections associated with %npRemoteAddress%

were reclaimed to avoid exceeding the maximum number of SIP
TCP connections per peer.

Recommended No action is typically required. Adjust the

Action(s) following configuration values as needed:
maxNumberTcpSocketsPerPeer, autoDiscardStaleConnections,
and staleConnectionTimerInMinutes.

Correlation Rules

bwSipTcpSocketError Problem Type Notification

OID 33

Status current

Severity Range low

Description SIP TCP connection associated with IP address and port was
released or unable to be established

Problem Text SIP TCP connection associated with %npRemoteAddress% was

released or unable to be established.

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 59
 Alarm Name Attributes Values

Recommended
Action(s)

Correlation Rules

bwSipSocketAlreadyBound Problem Type Notification

OID 71

Status current

Severity Range low

Description The server attempted to bind a socket against a local port that
was already used.

Problem Text Could not bind to %npLocalPort%

Recommended
Action(s)

Correlation Rules

bwSipMessageParsingError Problem Type Notification

OID 3509

Status current

Severity Range low

Description This notification indicates that BroadWorks is unable to parse an

incoming SIP message.

Problem Text Unable to parse SIP message. Error is %npMissingHeader%.

Message:
%npMessage%

Recommended Check SIP message for syntax error

Action(s)

Correlation Rules

bwSipRegistrationFailure Problem Type Notification

OID 3510

Status current

Severity Range low

Description This notification indicates that BroadWorks rejected a

registration attempt from an endpoint due to the Emergency
Zone feature.

Problem Text Emergency Zone rejected SIP Registration. Message:

%npMessage%

Recommended
Action(s)

Correlation Rules

bwSipUnexpectedMessage Problem Type Notification

OID 3511

Status current

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 60
 Alarm Name Attributes Values

Severity Range low

Description This notification indicates that an unexpected SIP message is

received.

Problem Text Unexpected SIP Message received.

Reason:
%npReason%
Response Message:
%npSipResponseMessage%
Request Message:
%npSipRequestMessage%

Recommended
Action(s)

Correlation Rules

bwSipMaxRetriesExceeded Problem Type Notification

OID 3512

Status current

Severity Range low

Description This notification indicates a SIP request was aborted after

maximum number of retries.

Problem Text SIP request %npMethod% aborted after maximum number of

retries.
Call-ID: %npCallId%
Destination address: %npDeviceAddress%:%npRemotePort%

Recommended
Action(s)

Correlation Rules

bwSipRequestTimeOutReceived Problem Type Notification

OID 3513

Status current

Severity Range low

Description This notification indicates that a SIP request timeout message

was received.

Problem Text SIP respond 408 Request Timeout received.

Response Message:
%npSipResponseMessage%
Request Message:
%npSipRequestMessage%
Device Address: %npDeviceAddress%

Recommended
Action(s)

Correlation Rules

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 61
 Alarm Name Attributes Values

bwSipServiceUnavailableReceived Problem Type Notification

OID 3514

Status current

Severity Range low

Description This notification indicates that a SIP service unavailable

message was received.

Problem Text SIP respond 503 Service Unavailable received.

Response Message:
%npSipResponseMessage%
Request Message:
%npSipRequestMessage%
Device Address: %npDeviceAddress%

Recommended
Action(s)

Correlation Rules

bwSipServerTimeOutReceived Problem Type Notification

OID 3515

Status current

Severity Range low

Description This notification indicates that a SIP server timeout message

was received.

Problem Text SIP respond 504 Server Timeout received.

Response Message:
%npSipResponseMessage%
Request Message:
%npSipRequestMessage%
Device Address: %npDeviceAddress%

Recommended
Action(s)

Correlation Rules

bwAclViolation Problem Type Notification

OID 3517

Status current

Severity Range low

Description SIP request received from an unknown device.

Problem Text SIP request %npMethod% received violates access control list.
Call-ID: %npCallId%
%npReason%

Recommended
Action(s)

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 62
 Alarm Name Attributes Values

Correlation Rules

bwSipUnrecognisedDomainName Problem Type Notification

OID 3518

Status current

Severity Range medium

Description The domain name entered in the access device location is

unrecognized or the domain name server is unreachable.

Problem Text The access device:%npHost% is not currently in service

Recommended Check the connectivity/availability of the DNS or verify the

Action(s) domain name used as location.

Correlation Rules

bwSipTcpConnectionFailure Problem Type Notification

OID 3595

Status current

Severity Range low

Description Failure to establish TCP connection.

Problem Text Could not connect to %npRemoteAddress%

Recommended Check the connectivity, availability, and configuration of the

Action(s) device.

Correlation Rules

8.2.5 SNMP Traps For Component: mgcp

The table that follows describes the SNMP traps for the mgcp subcomponent of the BroadworksFault MIB.
There is no visible fault for this component.

8.2.6 SNMP Traps For Component: smtp

The table that follows describes the SNMP traps for the smtp subcomponent of the BroadworksFault MIB.
Table 21: SNMP Traps For BroadworksFault:smtp
Alarm Name Attributes Values

bwSMTPPrimaryServerEmailMessage Problem Type Alarm

DeliveryError
OID 3519

Status current

Severity Range low

Description This notification indicates that the system failed to deliver an e-

mail message via the primary SMTP server.

Problem Text System failed to deliver emails via the primary SMTP server.

Recommended Check the connectivity/availability of the primary SMTP server.

Action(s)

Correlation Rules

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 63
 Alarm Name Attributes Values

bwSMTPConnectivityFailure Problem Type Notification

OID 3520

Status current

Severity Range high

Description This notification indicates that the system has lost the
connection to both SMTP servers.

Problem Text System failed to deliver emails via the primary and the
secondary SMTP servers.

Recommended Check the connectivity/availability of the primary and secondary

Action(s) SMTP servers.

Correlation Rules

8.2.7 SNMP Traps For Component: filesystem

The table that follows describes the SNMP traps for the filesystem subcomponent of the BroadworksFault
MIB.
Table 22: SNMP Traps For BroadworksFault:filesystem
Alarm Name Attributes Values

bwFileServerClusterUnreachable Problem Type Alarm

OID 37

Status current

Severity Range critical

Description The file server cluster is unreachable, causing a file operation to

fail.

Problem Text Could not connect to any server in file server cluster
%npClusterName%.

Recommended Verify that:

Action(s)
- The file server is properly configured in CLI context System/
MediaFileSystem and/or in CLI context System/Device/
FileRepos.
- The DNS is properly configured.
- The failing file server nodes are reachable from the Application
Server, the Media Server and the Xtended Services Platform for
device management.
- The file server is properly configured.

Correlation Rules

bwFileServerNodeUnreachable Problem Type Notification

OID 38

Status current

Severity Range high

Description One node in the file server cluster is not reachable.

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 64
 Alarm Name Attributes Values

Problem Text The file server node %npRemoteAddress% in the file server
cluster %npClusterName% is unreachable.

Recommended Verify that:

Action(s)
- The DNS is properly configured for the failing file server nodes.
- The failing file server nodes are reachable from the Application
Server, the Media Server and/or the Xtended Services Platform
for device management.
- The file server is properly configured on the failing file server
nodes.

Correlation Rules

8.2.8 SNMP Traps For Component: callp

The table that follows describes the SNMP traps for the callp subcomponent of the BroadworksFault MIB.
Table 23: SNMP Traps For BroadworksFault:callp
Alarm Name Attributes Values

bwCongestionManagementNeighbors Problem Type Notification

Inhibited
OID 46

Status current

Severity Range medium

Description The Application Server has identified the main overload source
when it enters into the yellow zone.

Problem Text %npNbInhibitedNeighbors% network element addresses caused

the server to become overloaded: %npInhibitedNeighbors%

Recommended
Action(s)

Correlation Rules

bwAuditAbnormalCallTermination Problem Type Notification

OID 3536

Status current

Severity Range low

Description This notification is sent when an end device does not respond
during an active call or when a call is detected in the system in
an incorrect state. Session audit has terminated the call when
this alarm is sent.

Problem Text Failed audit

User: %npUserUid%
Session Key: %npSessionKey%
Endpoint: %npEndpointId%

Recommended None
Action(s)

Correlation Rules

bwCallPThreadAutoRestart Problem Type Notification

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 65
 Alarm Name Attributes Values

OID 3555

Status current

Severity Range high

Description This notification is sent when the Application Server call

processing watchdog thread has detected a problem with a call
processing thread and has restarted it.

Problem Text Thread automatically restarted by watchdog:

%npThreadName%

Recommended Contact Broadsoft support.

Action(s)

Correlation Rules

bwForcedExitDueToHungThread Problem Type Notification

OID 3556

Status current

Severity Range critical

Description This notification is sent when the Application Server call

processing watchdog thread has detected a problem with a call
processing thread. An attempt was made to restart the thread,
however this has failed. The Application Server processes exits
and is restarted by the process monitor.

Problem Text Application server restarting because of unrecoverable problem

in thread:
%npThreadName%

Recommended Check log file for full Java stack trace and contact Broadsoft
Action(s) support.

Correlation Rules

bwThreadDelayDetected Problem Type Notification

OID 3594

Status current

Severity Range high

Description A thread was delayed.

Problem Text The %npThreadName% thread was delayed for

%npTimeElapsed% milliseconds. A thread dump is available in
the XSOutput log file. Last message processed:
%npMessage%

Recommended Contact Broadsoft support and supply the XSOutput file.

Action(s)

Correlation Rules

bwPhysicalLocationOriginationBlocked Problem Type Notification

OID 3609

Status current

Severity Range informational

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 66
 Alarm Name Attributes Values

Description User origination blocked by the Physical Location service.

Problem Text User origination blocked by the Physical Location service.

User ID: %npUserId%
Call ID: %npCallId%
Dialed Number: %npDialedNumber%
Device Line/Port: %npDeviceLinePort%
Received Physical Location: %npReceivedPhysicalLocation%
Configured Physical Location: %npConfiguredPhysicalLocation
%

Recommended
Action(s)

Correlation Rules

bwCallOverloadZoneTransition Problem Type Alarm

OID 3618

Status current

Severity Range high

Description This trap is generated when the BroadWorks component enters

a new non-call overload control zone.

Problem Text The server has entered a new call processing overload control
zone.
Old Zone: %npOldZone%
New Zone: %npNewZone%

Recommended
Action(s)

Correlation Rules

bwNonCallOverloadZoneTransition Problem Type Alarm

OID 3619

Status current

Severity Range high

Description This trap is generated when the BroadWorks component enters

a new call overload control zone.

Problem Text The server has entered a new non-call processing overload
control zone.
Old Zone: %npOldZone%
New Zone: %npNewZone%

Recommended
Action(s)

Correlation Rules

bwCongestionManagementNeighbor Problem Type Alarm

Overloaded
OID 3635

Status current

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 67
 Alarm Name Attributes Values

Severity Range medium

Description The Server has received a 503 Response with Retry-After from
the neighbor and set the neighbor to Overloaded state.

Problem Text Neighbor: %npRemoteAddress%

Retry-After period: %npPeriod%

Recommended
Action(s)

Correlation Rules

8.2.9 SNMP Traps For Component: nssynch

The table that follows describes the SNMP traps for the nssynch subcomponent of the BroadworksFault
MIB.
Table 24: SNMP Traps For BroadworksFault:nssynch
Alarm Name Attributes Values

bwNSSynchronizationConnectivityFailure Problem Type Notification

OID 3537

Status current

Severity Range high

Description Failure to create data synchronization connection between

Application Server and Network Server.

Problem Text Failure with connectivity between Application Server and

Network Server for synchronization.
%npReason%

Recommended
Action(s) *

Correlation Rules

bwNSLocationConnectivityFailure Problem Type Alarm

OID 3539

Status current

Severity Range high

Description Failure with connectivity between the Application Server and the
Network Server.

Problem Text Failure with connectivity between Application Server and

Network Server for user location.
%npReason%
Failed Transaction:
%npMessage%

Recommended
Action(s) *

Correlation Rules

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 68
 Alarm Name Attributes Values

bwNSLocationFailure Problem Type Notification

OID 3540

Status current

Severity Range medium

Description Data may be out of synch between the Application Server and
the Network Server.

Problem Text Failure with user location transaction between Application

Server and Network Server.
%npReason%
Failed Transaction:
%npMessage%
Network Server IP address:
%npRemoteAddress%

Recommended Check synchronization of data with Network Server used for

Action(s) user location.

Correlation Rules

bwNSSyncSuccessDbCommitFailed Problem Type Notification

OID 11759

Status current

Severity Range medium

Description A provisioning transaction successfully performed a NSSynch

but failed to commit to the database.

Problem Text Out of synch with NS : %npRequestName%

Recommended
Action(s)

Correlation Rules

8.2.10 SNMP Traps For Component: smap

The table that follows describes the SNMP traps for the smap subcomponent of the BroadworksFault MIB.
Table 25: SNMP Traps For BroadworksFault:smap
Alarm Name Attributes Values

bwSMAPConnectionFailure Problem Type Notification

OID 26

Status current

Severity Range medium

Description The SMAP port failed to be opened.

Problem Text Unable to open SMAP port, which will prevent processing of
SNMP requests.

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 69
 Alarm Name Attributes Values

Recommended Stop server. Make sure SMAP port * is available for connection.
Action(s) Restart server. If problem persists, contact BroadSoft Support
Engineer.

Correlation Rules

8.2.11 SNMP Traps For Component: accounting

The table that follows describes the SNMP traps for the accounting subcomponent of the BroadworksFault
MIB.
Table 26: SNMP Traps For BroadworksFault:accounting
Alarm Name Attributes Values

bwLicenseMonitoringFault Problem Type Notification

OID 3665

Status current

Severity Range high

Description Licensing threshold exceeded.

Problem Text bwLicenseMon has detected that some services have exceeded
the following licensing threshold: %npCurrentThresholdValue%

%npReport%

Recommended
Action(s)

Correlation Rules

8.2.12 SNMP Traps For Component: licensing

The table that follows describes the SNMP traps for the licensing subcomponent of the BroadworksFault
MIB.
Table 27: SNMP Traps For BroadworksFault:licensing
Alarm Name Attributes Values

bwLicenseFileNotFound Problem Type Notification

OID 25

Status current

Severity Range critical

Description This notification indicates that the system is unable to locate the
license files.

Problem Text License file not found. %npFilename%

Recommended Install the license file or contact Broadsoft support.

Action(s)

Correlation Rules

bwLicenseFileExpiring Problem Type Notification

OID 44

Status current

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 70
 Alarm Name Attributes Values

Severity Range critical

Description This alarm is generated once a day when the license file
expiration date is less than seven days from the current day.

Problem Text The license file will expire on %npDate%. After that date, the
system will no longer start.

Recommended Please contact BroadSoft to get an updated license file.

Action(s)

Correlation Rules

bwLicenseFileExpired Problem Type Notification

OID 45

Status current

Severity Range critical

Description This alarm is sent once a day, after the license file has expired.

Problem Text The license file expired on %npDate%. The system can no
longer start.

Recommended Please contact BroadSoft to get an updated license file.

Action(s)

Correlation Rules

bwLicenseAuthenticationFailure Problem Type Notification

OID 3541

Status current

Severity Range critical

Description This notification indicates that the authentication of the license

file failed.

Problem Text License file authentication failure.

Recommended Use the correct license file or contact Broadsoft support.

Action(s)

Correlation Rules

bwLicenseHWViolation Problem Type Notification

OID 3543

Status current

Severity Range critical

Description This notification indicates that there is an attempt to run the

application on an unlicensed server.

Problem Text Attempt to run the application on an unlicensed server.

Recommended Please run the application on the designated server or contact

Action(s) BroadSoft to obtain additional licenses.

Correlation Rules

bwLicenseAccntViolation Problem Type Notification

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 71
 Alarm Name Attributes Values

OID 3544

Status current

Severity Range high

Description This notification indicates that the license allocation has

exceeded the limit.

Problem Text License allocation has exceeded the limit for %npLicenseKey
%. Limit is %npLicenseLimit% and current allocation is
%npLicenseAllocation%.

Recommended Please contact BroadSoft to obtain additional licenses.

Action(s)

Correlation Rules

8.2.13 SNMP Traps For Component: pmReporting

The table that follows describes the SNMP traps for the pmReporting subcomponent of the
BroadworksFault MIB.
Table 28: SNMP Traps For BroadworksFault:pmReporting
Alarm Name Attributes Values

bwPMReportingFTPConnectionError Problem Type Alarm

OID 16

Status current

Severity Range informational

Description Periodic measurement report could not be sent to FTP server.

Problem Text Periodic SNMP measurement report could not be sent to FTP
server. Could not connect to %npRemoteAddress%. User ID:
%npUserId%

Recommended Verify the availability of the FTP server. Verify that the FTP
Action(s) domain, user ID and password are correct. The report file was
copied to the /var/broadworks/pm_reports/not_sent directory. It
can be uploaded manually to the FTP server.

Correlation Rules

8.2.14 SNMP Traps For Component: smdi

The table that follows describes the SNMP traps for the smdi subcomponent of the BroadworksFault MIB.
Table 29: SNMP Traps For BroadworksFault:smdi
Alarm Name Attributes Values

bwSMDIsessionRejected Problem Type Notification

OID 3566

Status current

Severity Range low

Description An SMDI session, initiated by an external terminal server, was

rejected.

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 72
 Alarm Name Attributes Values

Problem Text An SMDI session was rejected.

Rejection reason: %npReason%.
Client address: %npClientAddress%.

Recommended 1- Make sure that the server sending the request is configured in
Action(s) the AS access list,
2- Try to increase to maximum number of sessions.

Correlation Rules

bwSMDIInterfaceError Problem Type Notification

OID 3574

Status current

Severity Range low

Description The SMDI interface could not be started on a specific port.

Problem Text The SMDI interface cannot be enabled using listening port
%npLocalPort%. The Application Server will not be able to
receive or send SMDI messages.

Recommended Validate whether:

Action(s)
1- The listening port specified is not already used by another
application in the system.
2- The SMDI component is allowed to use the listening port
specified.
3- Enabling the interface using another port works.

Correlation Rules

bwSMDIConfigurationError Problem Type Notification

OID 3575

Status current

Severity Range low

Description An outgoing SMDI message could not be sent to a SMDI device

for the specified user.

Problem Text The following user could not be mapped to an outgoing SMDI
device:
User ID: %npUserId%
SMDI number: %npSmdiNumber%

Recommended For Outgoing Message Waiting Indicator (MWI), verify that:

Action(s)
1- In Voice Messaging Service, Outgoing MWI is assigned and
turned on for the user,
2- The SMDI route list is properly configured.
For Message Desk (MD), verify that:
1- At least one outgoing SMDI device (terminal server) is
configured for the SMDI Message Desk service.

Correlation Rules

bwSMDIOperationFailure Problem Type Notification

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 73
 Alarm Name Attributes Values

OID 3576

Status current

Severity Range low

Description For the actual description, refer the BroadWorks

FaultManagementGuide as it may contain variable data.

Problem Text The SMDI MWI indicator was not accepted by the destination
PBX or C5 network:
User ID: %npUserId%
SMDI number: %npSmdiNumber%
Reason: %npReason%

Recommended Validate whether:

Action(s)
1- The user should be assigned MWI on SMDI in the voice
messaging service, or
2- The configuration on the PBX and/or class 5 is accurate.

Correlation Rules

bwSMDIRouteExhaustion Problem Type Notification

OID 3577

Status current

Severity Range low

Description An SMDI message could not be sent because of route

exhaustion.

Problem Text The SMDI MWI indicator cannot be sent to any SMDI device:
User ID: %npUserId%
SMDI number: %npSmdiNumber%
Devices: %npDeviceName%

Recommended Validate whether:

Action(s)
1- The SMDI device address and port are valid and reachable,
or
2- The SMDI device configuration is accurate, or
3- The SMDI device is running and correctly communicating with
the PBX and/or class 5.

Correlation Rules

8.2.15 SNMP Traps For Component: cpeDeviceManagement

The table that follows describes the SNMP traps for the cpeDeviceManagement subcomponent of the
BroadworksFault MIB.
Table 30: SNMP Traps For BroadworksFault:cpeDeviceManagement
Alarm Name Attributes Values

bwCPEDeviceProfileLockout Problem Type Notification

OID 66

Status current

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 74
 Alarm Name Attributes Values

Severity Range low

Description Device Profile is locked out because of an authentication failure

per device profile lockout rules.

Problem Text Device is locked out because of authentication failure.

Service Provider / Enterprise ID: %npServiceProviderId%
Group ID: %npGroupId%
Device Profile Name: %npDeviceProfileName%
Lockout Counter: %npLockoutCounter%
Lockout Period (minutes): %npLockoutPeriod%
%npDeviceFileRequestMessage%

Recommended Determine if caused by a rogue device or configuration issue.

Action(s)

Correlation Rules

8.2.16 SNMP Traps For Component: networkDeviceManagement

The table that follows describes the SNMP traps for the networkDeviceManagement subcomponent of the
BroadworksFault MIB.
Table 31: SNMP Traps For BroadworksFault:networkDeviceManagement
Alarm Name Attributes Values

bwNetworkDeviceIsFailed Problem Type Alarm

OID 19

Status current

Severity Range high

Description This alarm is generated whenever a network device that was

previously responding does not respond to an application-level
ping.

Problem Text The following network device is currently unavailable:

%npServerType%
%npRemoteAddress%

Recommended Please verify that the device is operational and that there is
Action(s) connectivity to the device.

Correlation Rules It is recommended to always keep the highest severity value for
this notification until it is cleared.

8.2.17 SNMP Traps For Component: cap

The table that follows describes the SNMP traps for the cap subcomponent of the BroadworksFault MIB.
There is no visible fault for this component.

8.2.18 SNMP Traps For Component: ociReporting

The table that follows describes the SNMP traps for the ociReporting subcomponent of the
BroadworksFault MIB.

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 75
 Table 32: SNMP Traps For BroadworksFault:ociReporting
Alarm Name Attributes Values

bwOciReportingAclViolation Problem Type Notification

OID 3607

Status current

Severity Range low

Description Connection request received from an unknown external system.

Problem Text External system IP address %npRemoteAddress% not in

access control list.

Recommended
Action(s)

Correlation Rules

bwOciReportingConnectionError Problem Type Alarm

OID 3608

Status current

Severity Range low

Description Error detected on connection to an external system.

Problem Text Error detected on connection to external system IP address

%npRemoteAddress%. Connection released.

Recommended
Action(s)

Correlation Rules

bwOciReportingBackLogFileDeleted Problem Type Notification

OID 3615

Status current

Severity Range low

Description The total size of the OCI reporting backlog files exceeded the
system limit (500 MB). The oldest file is deleted.

Problem Text OCI Report backlog file %npFilename% for host %npHost% is
deleted due to the system size limit.

Recommended Reestablish the connection so the backlog files can be

Action(s) processed.

Correlation Rules

8.2.19 SNMP Traps For Component: bcct

The table that follows describes the SNMP traps for the bcct subcomponent of the BroadworksFault MIB.
Table 33: SNMP Traps For BroadworksFault:bcct
Alarm Name Attributes Values

bwCommProtocolInitError Problem Type Notification

OID 28

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 76
 Alarm Name Attributes Values

Status current

Severity Range high

Description Could not bind on TCP port.

Problem Text Application is unable to connect to local port:

- Local Interface: %npLocalInterface%
- Port: %npLocalPort%

Recommended Make sure the listening port is not used by another application
Action(s)

Correlation Rules

bwCommProtocolHostNotAllowed Problem Type Notification

OID 29

Status current

Severity Range low

Description A host that is not allowed for this protocol has attempted to
connect.

Problem Text An unauthorized host for a specific protocol has attempted to

connect to this server:
- Remote Host Address: %npRemoteAddress%
- Local Interface: %npLocalInterface%
- Protocol: %npProtocol%

Recommended In case of a valid host, make sure it is defined in the BCCT

Action(s) Access List for the specified protocol.

Correlation Rules

bwCommProtocolInterfaceNotAllowed Problem Type Notification

OID 30

Status current

Severity Range low

Description Connections for this protocol are not allowed on this interface.

Problem Text A remote server has attempted to connect on an interface that is

not registered for a protocol:
- Remote Host Address: %npRemoteAddress%
- Local Interface: %npLocalInterface%
- Protocol: %npProtocol%

Recommended In case of a valid host, make sure it is defined in the BCCT

Action(s) Access List for the specified protocol.

Correlation Rules

8.2.20 SNMP Traps For Component: taskMonitor

The table that follows describes the SNMP traps for the taskMonitor subcomponent of the BroadworksFault
MIB.

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 77
 Table 34: SNMP Traps For BroadworksFault:taskMonitor
Alarm Name Attributes Values

bwTaskMonitorWarning Problem Type Notification

OID 34

Status current

Severity Range low

Description A task is taking longer than normal.

Problem Text A task is taking too long to complete. The task timeout is
%npTimeLength% ms and it was started %npTimeElapsed% ms
ago. Thread: %npThreadName%. Stack trace:
%npStackTrace%

Recommended Please report to BroadSoft support.

Action(s)

Correlation Rules

bwTaskMonitorHungTask Problem Type Notification

OID 35

Status current

Severity Range high-critical

Description A task is hung.

Problem Text A task is hung. The task timeout is %npTimeLength% ms and it

was started %npTimeElapsed% ms ago.
Thread: %npThreadName%
Stack trace:
%npStackTrace%

Recommended BroadWorks should be restarted as soon as possible. Please

Action(s) report to BroadSoft support.

Correlation Rules

bwTcpSubsystemFatalError Problem Type Notification

OID 36

Status current

Severity Range high

Description TCP subsystem fatal error.

Problem Text TCP subsystem fatal error: shutdown initiated.

%npStackTrace%

Recommended Please report to BroadSoft support.

Action(s)

Correlation Rules

8.2.21 SNMP Traps For Component: logging

The table that follows describes the SNMP traps for the logging subcomponent of the BroadworksFault
MIB.

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 78
 Table 35: SNMP Traps For BroadworksFault:logging
Alarm Name Attributes Values

bwLogQueueSizeLimitReached Problem Type Alarm

OID 42

Status current

Severity Range high

Description The server has started to drop log entries because the logging
queue size limit has been reached.

Problem Text Log queue size reached %npSizeLimit% for the OutputChannels
configured for %npFilename%

Recommended Please verify the availability of the OutputChannels.

Action(s)

Correlation Rules

8.2.22 SNMP Traps For Component: dns

The table that follows describes the SNMP traps for the dns subcomponent of the BroadworksFault MIB.
Table 36: SNMP Traps For BroadworksFault:dns
Alarm Name Attributes Values

bwDnsTimeout Problem Type Notification

OID 63

Status current

Severity Range high

Description A query to the Domain Name System (DNS) server times out.

Problem Text A DNS query timed out.

Recommended
Action(s)

Correlation Rules

bwDnsServerUnreachable Problem Type Notification

OID 3645

Status current

Severity Range low

Description A DNS server was unreachable for a DNS query.

Problem Text DNS server: %npRemoteAddress% is unreachable.

Recommended
Action(s)

Correlation Rules

bwDnsAllServersUnreachable Problem Type Alarm

OID 3646

Status current

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 79
 Alarm Name Attributes Values

Severity Range high

Description All DNS servers are unreachable.

Problem Text All DNS servers are unreachable.

Recommended
Action(s)

Correlation Rules

8.2.23 SNMP Traps For Component: snmpAgent

The table that follows describes the SNMP traps for the snmpAgent subcomponent of the BroadworksFault
MIB.
Table 37: SNMP Traps For BroadworksFault:snmpAgent
Alarm Name Attributes Values

bwAlarmsTableLimitReached Problem Type Notification

OID 47

Status current

Severity Range critical

Description This alarm is raised when the alarms table has reached the
configured maximum number of entries. It warns the manager
that no more alarms will be sent until the problem is fixed.

Problem Text The alarms table has reached its capacity limit of
%npMaximumNbItems%. No more alarms will be sent until
alarms are cleared.

Recommended
Action(s)

Correlation Rules

8.2.24 SNMP Traps For Component: xsp

The table that follows describes the SNMP traps for the xsp subcomponent of the BroadworksFault MIB.
Table 38: SNMP Traps For BroadworksFault:xsp
Alarm Name Attributes Values

bwProtocolRegistrationFailure Problem Type Alarm

OID 89

Status current

Severity Range high

Description Failed to register protocol with Application Server.

Problem Text

Recommended
Action(s)

Correlation Rules

bwOCIPServerUnreachable Problem Type Alarm

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 80
 Alarm Name Attributes Values

OID 91

Status current

Severity Range high

Description Unable to send OCI-P request, server is unreachable.

Problem Text Unable to send OCI-P request to %npAddress%. Server is

unreachable.

Recommended Verify * connectivity

Action(s)

Correlation Rules

bwOCICServerUnreachable Problem Type Alarm

OID 92

Status current

Severity Range high

Description Unable to send OCI-C request, server is unreachable.

Problem Text Unable to send OCI-C request to %npAddress%. Server is

unreachable.

Recommended Verify * connectivity.

Action(s)

Correlation Rules

8.2.25 SNMP Traps For Component: ps

The table that follows describes the SNMP traps for the ps subcomponent of the BroadworksFault MIB.
Table 39: SNMP Traps For BroadworksFault:ps
Alarm Name Attributes Values

bwSCFAPIURLUnreachable Problem Type Alarm

OID 2607

Status current

Severity Range high

Description Connection to SCF API failed due to URL not being reachable.

Problem Text Could not connect to SCF API URL %npRemoteAddress%.

Recommended
Action(s)

Correlation Rules

8.2.26 SNMP Traps For Component: softwareManager

The table that follows describes the SNMP traps for the softwareManager subcomponent of the
BroadworksFault MIB.

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 81
 Table 40: SNMP Traps For BroadworksFault:softwareManager
Alarm Name Attributes Values

bwMemoryAllocationExceeded Problem Type Notification

OID 53

Status current

Severity Range informational

Description Reports a lack of memory when deploying an application..

Problem Text Total application memory usage (%npApplicationMemory% MB)

exceeded system memory capacity (%npSystemMemory% MB).

Recommended Please consider un-deploying some applications.

Action(s)

Correlation Rules

bwMemoryOverAllocation Problem Type Alarm

OID 54

Status current

Severity Range informational

Description The memory allocation for application is overallocated.

Problem Text Memory settings for the containers on the node cannot be
satisfied as configured. This condition is checked by the
software manager on restart and when a new configuration is
deployed on the node.

Recommended The amount of memory configured for the containers exceeds

Action(s) the amount of physical memory.

Correlation Rules

8.2.27 SNMP Traps For Component: security

The table that follows describes the SNMP traps for the security subcomponent of the BroadworksFault
MIB.
Table 41: SNMP Traps For BroadworksFault:security
Alarm Name Attributes Values

bwMaximumFailedLoginAttempts Problem Type Notification

OID 27

Status current

Severity Range low

Description A user has failed to log in the allowed maximum number of

times (consecutive login failures).

Problem Text The number of failed login attempts: %npFailedLoginAttempts%

has exceeded the maximum of %npMaxFailedLoginAttempts%.

Recommended
Action(s)

Correlation Rules

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 82
 Alarm Name Attributes Values

bwMaximumFailedUserLoginAttempts Problem Type Notification

OID 59

Status current

Severity Range low

Description A specific user/administrator has failed to log in the allowed

maximum number of times (consecutive login failures).

Problem Text The user %npUserId% has reached the maximum number
allowed (%npMaxFailedLoginAttempts%) of consecutive failed
attempts, this account login has been disabled.

Recommended
Action(s)

Correlation Rules

bwSecureTlktToolResult Problem Type Notification

OID 64

Status current

Severity Range critical, high, medium, low, or informational

Description This notification returns the result from executing one of the
Security Toolkit tool as a task where the tool is configured to
report a notification.

Problem Text Result for tool %npSecureTlktToolName%

Tool result: %npSecureTlktToolResult%

Recommended
Action(s)

Correlation Rules

bwSecurityRiskDetected Problem Type Notification

OID 68

Status current

Severity Range high

Description A security risk is detected.

Problem Text The Security Monitor maintenance task detects a security risk.

Recommended Please review *.

Action(s)

Correlation Rules

bwKeyManagerCriticalDataMismatch Problem Type Notification

OID 69

Status current

Severity Range high-critical

Description The key manager identified a mismatch between the password

and the keystore entity.

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 83
 Alarm Name Attributes Values

Problem Text Mismatch: the %npMissingComponent% is %npState% for the

%npExistingComponent% that already exists.

Recommended
Action(s)

Correlation Rules

bwChangeDatabaseUserPasswordError Problem Type Notification

OID 70

Status current

Severity Range low

Description An error occurred while changing the password.

Problem Text An error occurred while changing the database password of

%npUserName%. The previous password is still effective.

Recommended Please ensure the database engine is running and retry with a
Action(s) different password.

Correlation Rules

8.2.28 SNMP Traps For Component: webcontainer

The table that follows describes the SNMP traps for the webcontainer subcomponent of the
BroadworksFault MIB.
Table 42: SNMP Traps For BroadworksFault:webcontainer
Alarm Name Attributes Values

bwExecutorQueueUsageExceeded Problem Type Alarm

OID 6005

Status current

Severity Range high

Description The usage ratio of the executor queue (in %) exceeded the
threshold level.

Problem Text The usage ratio of the %npExecutorType% executor exceeded

the threshold level.

Recommended Review server usage for identifying potential bottlenecks.

Action(s)

Correlation Rules

bwExecutorQueueLatencyExceeded Problem Type Alarm

OID 6006

Status current

Severity Range high

Description The executor queue latency exceeded the threshold level.

Problem Text The %npExecutorType% executor queue latency exceeded the

threshold level.

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 84
 Alarm Name Attributes Values

Recommended Review server usage for identifying potential bottlenecks.

Action(s)

Correlation Rules

bwExecutorThreadPoolProcessingTime Problem Type Alarm

Exceeded
OID 6007

Status current

Severity Range high

Description The executor thread pool processing time exceeded the

threshold level.

Problem Text The %npExecutorType% executor thread pool processing time

exceeded the threshold level.

Recommended Review server usage for identifying potential bottlenecks.

Action(s)

Correlation Rules

bwExecutorThreadPoolBusyExceeded Problem Type Alarm

OID 6008

Status current

Severity Range high

Description The executor thread pool busy ratio exceeded the threshold
level.

Problem Text The %npExecutorType% executor thread pool busy ratio

exceeded the threshold level.

Recommended Review server usage for identifying potential bottlenecks.

Action(s)

Correlation Rules

8.2.29 SNMP Traps For Component: sccp

The table that follows describes the SNMP traps for the sccp subcomponent of the BroadworksFault MIB.
There is no visible fault for this component.

8.2.30 SNMP Traps For Component: jvmProcess

The table that follows describes the SNMP traps for the jvmProcess subcomponent of the BroadworksFault
MIB.
Table 43: SNMP Traps For BroadworksFault:jvmProcess
Alarm Name Attributes Values

bwHeapMemoryUsageExceeded Problem Type Alarm

OID 61

Status current

Severity Range high

Description The memory usage ratio after a full garbage collection (in %)
exceeded the threshold level.

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 85
 Alarm Name Attributes Values

Problem Text The memory usage after a full garbage collection reached
%npProcessMemoryUsage% M for %npContainerName%.

Recommended Review server usage for identifying potential memory

Action(s) bottlenecks.

Correlation Rules

bwJVMProcessOutOfMemory Problem Type Alarm

OID 74

Status current

Severity Range critical

Description An out of memory condition was detected by a thread.

Problem Text An out of memory condition has been detected by thread

%npThreadName% for container %npContainerName%.

Recommended Please contact BroadSoft support.

Action(s)

Correlation Rules

bwJVMProcessUnexpectedSoftware Problem Type Alarm

ConditionDetected
OID 75

Status current

Severity Range high

Description An unexpected software condition has been detected by a

thread.

Problem Text An unexpected software condition has been detected by thread

%npThreadName% for container %npContainerName%.
Message: %npErrorMessage%

Recommended Further details can be found in the container's output logs.

Action(s) Please contact BroadSoft support.

Correlation Rules

bwNonheapMemoryUsageExceeded Problem Type Alarm

OID 62

Status deprecated

Severity Range high

Description The non heap memory usage ratio after a full garbage collection
(in %) exceeded the threshold level.

Problem Text The non heap memory usage after a full garbage
collection reached %npProcessMemoryUsage% M for
%npContainerName%.

Recommended Review server usage for identifying potential memory

Action(s) bottlenecks.

Correlation Rules

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 86
8.2.31 SNMP Traps For Component: time
The table that follows describes the SNMP traps for the time subcomponent of the BroadworksFault MIB.
Table 44: SNMP Traps For BroadworksFault:time
Alarm Name Attributes Values

bwTimeSkewExceeded Problem Type Notification

OID 76

Status current

Severity Range medium

Description The time difference between servers exceeds threshold.

Problem Text The time difference with %npRemoteAddress% exceeds the

%npTimeLength% seconds allowed threshold.

Recommended Check the time on the servers. Check that NTP is correctly
Action(s) configured on the servers.

Correlation Rules

8.2.32 SNMP Traps For Component: webrtc

The table that follows describes the SNMP traps for the webrtc subcomponent of the BroadworksFault
MIB.
There is no visible fault for this component.

8.2.33 SNMP Traps For Component: sipLocation

The table that follows describes the SNMP traps for the sipLocation subcomponent of the BroadworksFault
MIB.
There is no visible fault for this component.

8.2.34 SNMP Traps For Component: threshold

The table that follows describes the SNMP traps for the threshold subcomponent of the BroadworksFault
MIB.
Table 45: SNMP Traps For BroadworksFault:threshold
Alarm Name Attributes Values

bwCounterThreshold Problem Type Notification

OID 13

Status current

Severity Range variable

Description Sent when a counter threshold reaches its limit.

Problem Text Counter %npCounterName% has reached or exceeded

a user-defined threshold. The counter's value is
%npCurrentCounterValue% and the threshold was set at
%npCurrentThresholdValue%. The value to reach before the
next notification is now %npNewThresholdValue%. User-defined
description follows.
%npThresholdDescription%

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 87
 Alarm Name Attributes Values

Recommended
Action(s)

Correlation Rules

bwGaugeLowLimitThreshold Problem Type Alarm

OID 14

Status current

Severity Range variable

Description Sent when gauge threshold lowNotify value is reached while

decreasing.

Problem Text Gauge %npGaugeName% has reached a user-defined

low notification threshold. The threshold low value is
%npCurrentThresholdValue% and the value to reach to
clear the alarm is %npClearThresholdValue%. User-defined
description follows.
%npThresholdDescription%

Recommended
Action(s)

Correlation Rules

bwGaugeHighLimitThreshold Problem Type Alarm

OID 15

Status current

Severity Range variable

Description Sent when gauge threshold highNotify value is reached while

increasing.

Problem Text Gauge %npGaugeName% has reached a user-defined

high notification threshold. The threshold high value is
%npCurrentThresholdValue% and the value to reach to
clear the alarm is %npClearThresholdValue%. User-defined
description follows.
%npThresholdDescription%

Recommended
Action(s)

Correlation Rules

8.2.35 SNMP Traps For Component: nps

The table that follows describes the SNMP traps for the nps subcomponent of the BroadworksFault MIB.
Table 46: SNMP Traps For BroadworksFault:nps
Alarm Name Attributes Values

bwPushNotificationServerUnreachable Problem Type Alarm

OID 85

Status current

Severity Range critical

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 88
 Alarm Name Attributes Values

Description Push Notification Server has become unreachable.

Problem Text Push Notification Server %npAddress% has become

unreachable.

Recommended Please verify Push Notification Server connectivity.

Action(s)

Correlation Rules

8.2.36 SNMP Traps For Component: hazelcastClient

The table that follows describes the SNMP traps for the hazelcastClient subcomponent of the
BroadworksFault MIB.
Table 47: SNMP Traps For BroadworksFault:hazelcastClient
Alarm Name Attributes Values

bwHazelcastClusterConnectivity Problem Type Alarm

Unavailable
OID 86

Status current

Severity Range critical

Description The connectivity between Hazelcast client and Hazelcast cluster

is unavailable.

Problem Text Connectivity to %npClusterName% is unavailable.

Recommended Verify connectivity to Hazelcast cluster nodes or availability of

Action(s) Hazelcast cluster nodes.

Correlation Rules

8.3 BW-FileTransferFault MIB

This section presents SNMP traps (notifications and alarms) for the BW-FileTransferFault MIB grouped by
component.
This MIB defines the faults for the BroadWorks FileTransfer Application.
Applicable server(s):
Network Function Manager.

8.3.1 SNMP Traps For Component: fileRepos

The table that follows describes the SNMP traps for the fileRepos subcomponent of the BW-
FileTransferFault MIB.
Table 48: SNMP Traps For BW-FileTransferFault:fileRepos
Alarm Name Attributes Values

bwFileTransferReplicationFailure Problem Type Alarm

OID 17701

Status current

Severity Range high

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 89
 Alarm Name Attributes Values

Description A replication failure occurred.

Problem Text A replication failure occurred on peer : %npHost% for

%npWebAppContextPath%.

Recommended Review the server connectivity.

Action(s)

Correlation Rules

bwFileTransferReplicationOffline Problem Type Alarm

OID 17702

Status current

Severity Range high

Description The replication stopped for one of the Network Function

Manager peer. This was caused by exceeding the replication
queue capacity.

Problem Text The replication for %npWebAppContextPath% on the Network

Function Manager %npHost% has stopped.

Recommended The Network Function Manager Server is out of sync and needs
Action(s) to be restored.

Correlation Rules

8.4 BW-LicenseControllerFault MIB

This section presents SNMP traps (notifications and alarms) for the BW-LicenseControllerFault MIB
grouped by component.
This MIB defines the faults for the BroadWorks license controller Application.
Applicable server(s):
Network Function Manager.

8.4.1 SNMP Traps For Component: processmonitor

The table that follows describes the SNMP traps for the processmonitor subcomponent of the BW-
LicenseControllerFault MIB.
Table 49: SNMP Traps For BW-LicenseControllerFault:processmonitor
Alarm Name Attributes Values

bwPMLicenseControllerLaunched Problem Type Notification

OID 15401

Status current

Severity Range informational

Description This notification indicates that the license controller has been
started.

Problem Text The license controller has started.

Recommended
Action(s)

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 90
 Alarm Name Attributes Values

Correlation Rules bwPMLicenseControllerLaunched,

bwPMLicenseControllerShutDown,
bwPMLicenseControllerRestarted,
bwPMLicenseControllerDeath, and
bwPMLicenseControllerOutOfMemory can be correlated into
a single alarm. These events have to be considered as a
transition of the state machine for the management of the
license controller process

bwPMLicenseControllerShutDown Problem Type Notification

OID 15402

Status current

Severity Range informational

Description This notification indicates that the license controller has been
manually shut down.

Problem Text The license controller has shutdown.

Recommended
Action(s)

Correlation Rules bwPMLicenseControllerLaunched,

bwPMLicenseControllerShutDown,
bwPMLicenseControllerRestarted,
bwPMLicenseControllerDeath, and
bwPMLicenseControllerOutOfMemory can be correlated into
a single alarm. These events have to be considered as a
transition of the state machine for the management of the
license controller process

bwPMLicenseControllerRestarted Problem Type Notification

OID 15403

Status current

Severity Range informational

Description This notification provides the date and time of the license
controller restart.

Problem Text The license controller has restarted.

Recommended
Action(s)

Correlation Rules bwPMLicenseControllerLaunched,

bwPMLicenseControllerShutDown,
bwPMLicenseControllerRestarted,
bwPMLicenseControllerDeath, and
bwPMLicenseControllerOutOfMemory can be correlated into
a single alarm. These events have to be considered as a
transition of the state machine for the management of the
license controller process

bwPMLicenseControllerDeath Problem Type Notification

OID 15404

Status current

Severity Range critical

Description This notification provides the date and time of the license
controller death.

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 91
 Alarm Name Attributes Values

Problem Text The license controller has terminated.

Recommended Ensure license controller is restarted.

Action(s)

Correlation Rules bwPMLicenseControllerLaunched,

bwPMLicenseControllerShutDown,
bwPMLicenseControllerRestarted,
bwPMLicenseControllerDeath, and
bwPMLicenseControllerOutOfMemory can be correlated into
a single alarm. These events have to be considered as a
transition of the state machine for the management of the
license controller process

bwPMLicenseControllerOutOfMemory Problem Type Notification

OID 15405

Status current

Severity Range high

Description This notification provides the date and time when the license
controller application ran out of memory.

Problem Text The license controller ran out of memory.

Recommended Ensure license controller is restarted.

Action(s)

Correlation Rules bwPMLicenseControllerLaunched,

bwPMLicenseControllerShutDown,
bwPMLicenseControllerRestarted,
bwPMLicenseControllerDeath, and
bwPMLicenseControllerOutOfMemory can be correlated into
a single alarm. These events have to be considered as a
transition of the state machine for the management of the
license controller process.

8.4.2 SNMP Traps For Component: licenseController

The table that follows describes the SNMP traps for the licenseController subcomponent of the BW-
LicenseControllerFault MIB.
Table 50: SNMP Traps For BW-LicenseControllerFault:licenseController
Alarm Name Attributes Values

bwLicenseControllerNodeUsing Problem Type Notification

UnauthorizedLicense
OID 15406

Status current

Severity Range high

Description This notification indicates that the specified node is requesting

grant for a license different than the one that has been assigned
to the node.

Problem Text The Node %npNodeName% is requesting license grant for

licenseId %npWrongLicenseId% while it should be using
licenseId %npValidLicenseId%.

Recommended Verify communication between the Network Function Manager

Action(s) and the node. Verify alarms generated by the node.

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 92
 Alarm Name Attributes Values

Correlation Rules

bwLicenseControllerNodeLicenseUpdate Problem Type Notification

Failure
OID 15407

Status current

Severity Range high

Description This notification indicates that the Network Function Manager

failed to send a license update notification to the specified node.

Problem Text The Network Function Manager failed to notify %npNodeName

% of license change.

Recommended Verify communication between the Network Function Manager

Action(s) and the node.

Correlation Rules

bwLicenseControllerNodeUsing Problem Type Notification

UndeployedLicenseInstance
OID 15408

Status current

Severity Range high

Description This notification indicates that the specified node is not using the
deployed license instance.

Problem Text The node %npNodeName% is not using the expected license
%licenseIdInstance%.

Recommended
Action(s)

Correlation Rules

bwLicenseControllerExecutorQueue Problem Type Alarm

UsageExceeded
OID 15409

Status current

Severity Range high

Description This alarm indicates the usage ratio of the executor queue
exceeded the threshold level.

Problem Text The usage ratio of the %npExecutorType% executor exceeded

the threshold level.

Recommended Review the server usage for identifying potential bottlenecks.

Action(s)

Correlation Rules

bwLicenseControllerExecutorQueue Problem Type Alarm

LatencyExceeded
OID 15410

Status current

Severity Range high

Description This alarm indicates that the executor queue latency exceeded
the threshold level.

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 93
 Alarm Name Attributes Values

Problem Text The %npExecutorType% executor queue latency exceeded the

threshold level.

Recommended Review the server usage for identifying potential bottlenecks.

Action(s)

Correlation Rules

bwLicenseControllerExecutorThreadPool Problem Type Alarm

ProcessingTimeExceeded
OID 15411

Status current

Severity Range high

Description The alarm indicates that the executor thread pool processing
time exceeded the threshold level.

Problem Text The %npExecutorType% executor thread pool processing time

exceeded the threshold level.

Recommended Review the server usage for identifying potential bottlenecks.

Action(s)

Correlation Rules

bwLicenseControllerExecutorThreadPool Problem Type Alarm

BusyExceeded
OID 15412

Status current

Severity Range high

Description The alarm indicates that the executor thread pool busy ratio
exceeded the threshold level.

Problem Text The executor thread pool busy ratio exceeded the threshold
level.

Recommended Review the server usage for identifying potential bottlenecks.

Action(s)

Correlation Rules

8.5 BW-LicenseManagerFault MIB

This section presents SNMP traps (notifications and alarms) for the BW-LicenseManagerFault MIB
grouped by component.
This MIB defines the faults for the BroadWorks license manager daemon.
Applicable server(s):
Network Function Manager.

8.5.1 SNMP Traps For Component: processmonitor

The table that follows describes the SNMP traps for the processmonitor subcomponent of the BW-
LicenseManagerFault MIB.

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 94
 Table 51: SNMP Traps For BW-LicenseManagerFault:processmonitor
Alarm Name Attributes Values

bwPMlmdLaunched Problem Type Notification

OID 15801

Status current

Severity Range informational

Description This notification indicates that the license manager daemon has
started.

Problem Text The license manager has started.

Recommended
Action(s)

Correlation Rules bwPMlmdLaunched, bwPMlmdShutDown, bwPMlmdRestarted,

and bwPMlmdDeath can be correlated into a single alarm.
These events have to be considered as a transition of the state
machine for the management of the LicenseController process

bwPMlmdShutDown Problem Type Notification

OID 15802

Status current

Severity Range informational

Description This notification indicates that the license manager daemon has
been manually shut down.

Problem Text The license manager has shutdown.

Recommended
Action(s)

Correlation Rules bwPMlmdLaunched, bwPMlmdShutDown, bwPMlmdRestarted,

and bwPMlmdDeath can be correlated into a single alarm.
These events have to be considered as a transition of the state
machine for the management of the LicenseController process

bwPMlmdRestarted Problem Type Notification

OID 15803

Status current

Severity Range informational

Description This notification provides the date and time of the license
manager daemon restart.

Problem Text The license manager has restarted.

Recommended
Action(s)

Correlation Rules bwPMlmdLaunched, bwPMlmdShutDown, bwPMlmdRestarted,

and bwPMlmdDeath can be correlated into a single alarm.
These events have to be considered as a transition of the state
machine for the management of the LicenseController process

bwPMlmdDeath Problem Type Notification

OID 15804

Status current

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 95
 Alarm Name Attributes Values

Severity Range critical

Description This notification indicates that the license manager daemon has
abnormally terminated.

Problem Text The License has terminated.

Recommended Ensure license manager is restarted.

Action(s)

Correlation Rules bwPMlmdLaunched, bwPMlmdShutDown, bwPMlmdRestarted,

and bwPMlmdDeath can be correlated into a single alarm.
These events have to be considered as a transition of the state
machine for the management of the LicenseController process

8.5.2 SNMP Traps For Component: licensing

The table that follows describes the SNMP traps for the licensing subcomponent of the BW-
LicenseManagerFault MIB.
Table 52: SNMP Traps For BW-LicenseManagerFault:licensing
Alarm Name Attributes Values

bwLicensingNFMCommunicationLoss Problem Type Alarm

OID 15806

Status current

Severity Range high

Description There is a communication loss with the Network Function

Manager.

Problem Text The license manager could not connect to Networks Function
Manager at %npNFMFqdn%.

Recommended Fix the connection between this node and the Network Function
Action(s) Manager.

Correlation Rules

bwLicensingLMCommunicationLoss Problem Type Alarm

OID 15807

Status current

Severity Range high

Description There is a communication loss with the license manager.

Problem Text Unable to connect to the license manager.

Recommended Ensure the license manager daemon is alive on this node.

Action(s)

Correlation Rules

bwLicensingViolation Problem Type Alarm

OID 15808

Status current

Severity Range high

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 96
 Alarm Name Attributes Values

Description There is a license usage violation.

Problem Text This node is not allowed to use the current license,
%npLicenseId%, %npBroadWorksRelease%, %npDate%.

Recommended Please update the node with a valid license.

Action(s)

Correlation Rules

bwLicensingOverAllocation Problem Type Alarm

OID 15809

Status current

Severity Range high

Description An application reports a license over-allocation.

Problem Text An application reports a license over-allocation.

Recommended Please update the license or de-provision the over-allocated

Action(s) application to clear the condition.

Correlation Rules

bwLicensingNFMCommunicationLoss Problem Type Notification

Grace
OID 15810

Status current

Severity Range low to critical

Description There is a communication loss grace period.

Problem Text This node is in licensing communication loss grace period.

%npGraceAction% will be executed in %npHours% hours.

Recommended Fix the connection between this node and the Network Function
Action(s) Manager.

Correlation Rules

bwLicensingLMCommunicationLossGrace Problem Type Notification

OID 15811

Status current

Severity Range low to critical

Description There is a communication loss grace period.

Problem Text This node is in licensing communication loss grace period.

%npGraceAction% will be executed in %npHours% hours.

Recommended Ensure the license manager daemon is alive on the machine.

Action(s)

Correlation Rules

bwLicensingViolationGrace Problem Type Notification

OID 15812

Status current

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 97
 Alarm Name Attributes Values

Severity Range low to high

Description There is a licensing violation grace period.

Problem Text This node is in licensing violation grace period. %npGraceAction

% will be executed in %npHours% hours.

Recommended Update the node with a valid license.

Action(s)

Correlation Rules

bwOverAllocationViolationGrace Problem Type Notification

OID 15813

Status current

Severity Range low to high

Description There is a licensing over-allocation grace period.

Problem Text This node is in licensing over allocation grace period.

%npGraceAction% will be executed in %npHours% hours.

Recommended Update the license or de-provision the node to clear the over-
Action(s) allocation condition.

Correlation Rules

8.6 BW-MDBManagementFault MIB

This section presents SNMP traps (notifications and alarms) for the BW-MDBManagementFault MIB
grouped by component.
This MIB defines the faults for the BroadWorks MDB Management Application.
Applicable server(s):
Network Function Manager.

8.6.1 SNMP Traps For Component: processmonitor

The table that follows describes the SNMP traps for the processmonitor subcomponent of the BW-
MDBManagementFault MIB.
Table 53: SNMP Traps For BW-MDBManagementFault:processmonitor
Alarm Name Attributes Values

bwPMMariaDBLaunched Problem Type Notification

OID 16401

Status current

Severity Range informational

Description This notification indicates that the MariaDB daemon has started.

Problem Text The MariaDB daemon has started.

Recommended
Action(s)

Correlation Rules

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 98
 Alarm Name Attributes Values

bwPMMariaDBShutDown Problem Type Notification

OID 16402

Status current

Severity Range informational

Description This notification indicates that the MariaDB daemon has shut
down.

Problem Text The MariaDB daemon has shut down.

Recommended
Action(s)

Correlation Rules

bwPMMariaDBRestarted Problem Type Notification

OID 16403

Status current

Severity Range informational

Description This notification indicates that the MariaDB daemon has

restarted.

Problem Text The MariaDB daemon has restarted.

Recommended
Action(s)

Correlation Rules

bwPMMariaDBDeath Problem Type Notification

OID 16404

Status current

Severity Range critical

Description This notification indicates that the MariaDB daemon has

abnormally terminated.

Problem Text The MariaDB daemon has terminated.

Recommended Make sure MariaDB daemon gets restarted.

Action(s)

Correlation Rules

bwPMmdbMonitorLaunched Problem Type Notification

OID 16405

Status current

Severity Range informational

Description This notification indicates that the MariaDB monitor application

has started.

Problem Text The MariaDB monitor application has started.

Recommended
Action(s)

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 99
 Alarm Name Attributes Values

Correlation Rules

bwPMmdbMonitorShutDown Problem Type Notification

OID 16406

Status current

Severity Range informational

Description This notification indicates that the MariaDB monitor application

has shut down.

Problem Text The MariaDB monitor application has shut down.

Recommended
Action(s)

Correlation Rules

bwPMmdbMonitorRestarted Problem Type Notification

OID 16407

Status current

Severity Range informational

Description This notification indicates that the MariaDB monitor application

has restarted.

Problem Text The MariaDB monitor application has restarted.

Recommended
Action(s)

Correlation Rules

bwPMmdbMonitorDeath Problem Type Notification

OID 16408

Status current

Severity Range informational

Description This notification indicates that the MariaDB monitor application

has abnormally terminated.

Problem Text The MariaDB monitor application has terminated.

Recommended Make sure MariaDB monitor application gets restarted.

Action(s)

Correlation Rules

8.6.2 SNMP Traps For Component: database

The table that follows describes the SNMP traps for the database subcomponent of the BW-
MDBManagementFault MIB.
Table 54: SNMP Traps For BW-MDBManagementFault:database
Alarm Name Attributes Values

bwMariaDBNonPrimaryClusterNode Problem Type Alarm

OID 16409

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 100
 Alarm Name Attributes Values

Status current

Severity Range critical

Description This alarm indicates that the database node lost communication
with the cluster.

Problem Text Database node lost communication with the cluster.

Recommended Verify that the cluster nodes are running and verify the IP
Action(s) connectivity between the server reporting the fault and its peers.

Correlation Rules

8.7 BW-NetworkMonitoringFault MIB

This section presents SNMP traps (notifications and alarms) for the BW-NetworkMonitoringFault MIB
grouped by component.
This MIB defines the faults for the BroadWorks network monitoring Application.
Applicable server(s):
Network Function Manager.

8.7.1 SNMP Traps For Component: processmonitor

The table that follows describes the SNMP traps for the processmonitor subcomponent of the BW-
NetworkMonitoringFault MIB.
Table 55: SNMP Traps For BW-NetworkMonitoringFault:processmonitor
Alarm Name Attributes Values

bwPMNetworkMonitoringLaunched Problem Type Notification

OID 16201

Status current

Severity Range informational

Description This notification indicates that the network monitoring has been
started.

Problem Text The network monitoring has started.

Recommended
Action(s)

Correlation Rules bwPMNetworkMonitoringLaunched,

bwPMNetworkMonitoringShutDown,
bwPMNetworkMonitoringRestarted,
bwPMNetworkMonitoringDeath, and
bwPMNetworkMonitoringOutOfMemory can be correlated
into a single alarm. These events have to be considered as
a transition of the state machine for the management of the
network monitoring process

bwPMNetworkMonitoringShutDown Problem Type Notification

OID 16202

Status current

Severity Range informational

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 101
 Alarm Name Attributes Values

Description This notification indicates that the network monitoring has been
manually shut down.

Problem Text The network monitoring has shutdown.

Recommended
Action(s)

Correlation Rules bwPMNetworkMonitoringLaunched,

bwPMNetworkMonitoringShutDown,
bwPMNetworkMonitoringRestarted,
bwPMNetworkMonitoringDeath, and
bwPMNetworkMonitoringOutOfMemory can be correlated
into a single alarm. These events have to be considered as
a transition of the state machine for the management of the
network monitoring process

bwPMNetworkMonitoringRestarted Problem Type Notification

OID 16203

Status current

Severity Range informational

Description This notification provides the date and time of the network
monitoring restart.

Problem Text The network monitoring has restarted.

Recommended
Action(s)

Correlation Rules bwPMNetworkMonitoringLaunched,

bwPMNetworkMonitoringShutDown,
bwPMNetworkMonitoringRestarted,
bwPMNetworkMonitoringDeath, and
bwPMNetworkMonitoringOutOfMemory can be correlated
into a single alarm. These events have to be considered as
a transition of the state machine for the management of the
network monitoring process

bwPMNetworkMonitoringDeath Problem Type Notification

OID 16204

Status current

Severity Range critical

Description This notification provides the date and time of the network
monitoring death.

Problem Text The network monitoring has terminated.

Recommended Ensure network monitoring is restarted.

Action(s)

Correlation Rules bwPMNetworkMonitoringLaunched,

bwPMNetworkMonitoringShutDown,
bwPMNetworkMonitoringRestarted,
bwPMNetworkMonitoringDeath, and
bwPMNetworkMonitoringOutOfMemory can be correlated
into a single alarm. These events have to be considered as
a transition of the state machine for the management of the
network monitoring process

bwPMNetworkMonitoringOutOfMemory Problem Type Notification

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 102
 Alarm Name Attributes Values

OID 16205

Status current

Severity Range high

Description This notification provides the date and time when the network
monitoring application ran out of memory.

Problem Text The network monitoring ran out of memory.

Recommended Ensure network monitoring is restarted.

Action(s)

Correlation Rules bwPMNetworkMonitoringLaunched,

bwPMNetworkMonitoringShutDown,
bwPMNetworkMonitoringRestarted,
bwPMNetworkMonitoringDeath, and
bwPMNetworkMonitoringOutOfMemory can be correlated
into a single alarm. These events have to be considered as
a transition of the state machine for the management of the
network monitoring process.

bwPMFileReplicationLaunched Problem Type Notification

OID 16207

Status current

Severity Range informational

Description This notification indicates that the File Replication application

has started.

Problem Text The File Replication application has started.

Recommended
Action(s)

Correlation Rules

bwPMFileReplicationShutDown Problem Type Notification

OID 16208

Status current

Severity Range informational

Description This notification indicates that the File Replication application

has shut down.

Problem Text The File Replication application has shutdown.

Recommended From the CLI, execute the syncInventory command.

Action(s)

Correlation Rules

bwPMFileReplicationRestarted Problem Type Notification

OID 16209

Status current

Severity Range informational

Description This notification indicates that the File Replication application

has restarted.

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 103
 Alarm Name Attributes Values

Problem Text The node inventory is out of synch.

Recommended The File Replication application has restarted

Action(s)

Correlation Rules

bwPMFileReplicationDeath Problem Type Notification

OID 16210

Status current

Severity Range critical

Description This notification indicates that the File Replication application

has abnormally terminated.

Problem Text The File Replication application has terminated.

Recommended Ensure that the file replication is restarted.

Action(s)

Correlation Rules

8.7.2 SNMP Traps For Component: networkMonitoring

The table that follows describes the SNMP traps for the networkMonitoring subcomponent of the BW-
NetworkMonitoringFault MIB.
Table 56: SNMP Traps For BW-NetworkMonitoringFault:networkMonitoring
Alarm Name Attributes Values

bwNMControllerInventoryOutOfSynch Problem Type Alarm

OID 16206

Status current

Severity Range high

Description There is a loss of synchronization, regarding the

NetworkMonitoring inventory.

Problem Text The node inventory is out of synch.

Recommended From the CLI, execute the syncInventory command.

Action(s)

Correlation Rules

bwNMReplicationPrimaryFailure Problem Type Notification

OID 16211

Status current

Severity Range critical

Description The primary NetworkMonitoring application is not responding.

Problem Text The primary NetworkMonitoring application is not responding.

Recommended Resolve the issue which caused the primary primary

Action(s) NetworkMonitoring application to fail and reconfigure the
redundancy.

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 104
 Alarm Name Attributes Values

Correlation Rules

bwNMReplicationStandbyFailure Problem Type Notification

OID 16212

Status current

Severity Range critical

Description The standby NetworkMonitoring application is not responding.

Problem Text The standby NetworkMonitoring application is not responding.

Recommended Resolve the issue which caused the standby NetworkMonitoring

Action(s) application to fail and reconfigure the redundancy.

Correlation Rules

8.8 BW-NodeControllerFault MIB

This section presents SNMP traps (notifications and alarms) for the BW-NodeControllerFault MIB grouped
by component.
This MIB defines the faults for the BroadWorks node controller Application.
Applicable server(s):
Network Function Manager.

8.8.1 SNMP Traps For Component: processmonitor

The table that follows describes the SNMP traps for the processmonitor subcomponent of the BW-
NodeControllerFault MIB.
Table 57: SNMP Traps For BW-NodeControllerFault:processmonitor
Alarm Name Attributes Values

bwPMNodeControllerLaunched Problem Type Notification

OID 15601

Status current

Severity Range informational

Description This notification indicates that the node controller has been
started.

Problem Text The node controller has started.

Recommended
Action(s)

Correlation Rules bwPMNodeControllerLaunched,

bwPMNodeControllerShutDown,
bwPMNodeControllerRestarted, bwPMNodeControllerDeath,
and bwPMNodeControllerOutOfMemory can be correlated into a
single alarm. These events have to be considered as a transition
of the state machine for the management of the node controller
process

bwPMNodeControllerShutDown Problem Type Notification

OID 15602

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 105
 Alarm Name Attributes Values

Status current

Severity Range informational

Description This notification indicates that the node controller has been
manually shut down.

Problem Text The node controller has shutdown.

Recommended
Action(s)

Correlation Rules bwPMNodeControllerLaunched,

bwPMNodeControllerShutDown,
bwPMNodeControllerRestarted, bwPMNodeControllerDeath,
and bwPMNodeControllerOutOfMemory can be correlated into a
single alarm. These events have to be considered as a transition
of the state machine for the management of the node controller
process

bwPMNodeControllerRestarted Problem Type Notification

OID 15603

Status current

Severity Range informational

Description This notification provides the date and time of the node
controller restart.

Problem Text The node controller has restarted.

Recommended
Action(s)

Correlation Rules bwPMNodeControllerLaunched,

bwPMNodeControllerShutDown,
bwPMNodeControllerRestarted, bwPMNodeControllerDeath,
and bwPMNodeControllerOutOfMemory can be correlated into a
single alarm. These events have to be considered as a transition
of the state machine for the management of the node controller
process

bwPMNodeControllerDeath Problem Type Notification

OID 15604

Status current

Severity Range critical

Description This notification provides the date and time of the node
controller death.

Problem Text The node controller has terminated.

Recommended Ensure node controller is restarted.

Action(s)

Correlation Rules bwPMNodeControllerLaunched,

bwPMNodeControllerShutDown,
bwPMNodeControllerRestarted, bwPMNodeControllerDeath,
and bwPMNodeControllerOutOfMemory can be correlated into a
single alarm. These events have to be considered as a transition
of the state machine for the management of the node controller
process

bwPMNodeControllerOutOfMemory Problem Type Notification

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 106
 Alarm Name Attributes Values

OID 15605

Status current

Severity Range high

Description This notification provides the date and time when the node
controller application ran out of memory.

Problem Text The node controller ran out of memory.

Recommended Ensure node controller is restarted.

Action(s)

Correlation Rules bwPMNodeControllerLaunched,

bwPMNodeControllerShutDown,
bwPMNodeControllerRestarted, bwPMNodeControllerDeath,
and bwPMNodeControllerOutOfMemory can be correlated into a
single alarm. These events have to be considered as a transition
of the state machine for the management of the node controller
process.

8.8.2 SNMP Traps For Component: nodeController

The table that follows describes the SNMP traps for the nodeController subcomponent of the BW-
NodeControllerFault MIB.
Table 58: SNMP Traps For BW-NodeControllerFault:nodeController
Alarm Name Attributes Values

bwNodeControllerOperationFailure Problem Type Alarm

OID 15606

Status current

Severity Range high

Description This notification indicates that the node controller has

experienced an error during an operation.

Problem Text Operation %npOperation% unsuccessful.

Caused by:
%npReason%.

Recommended
Action(s)

Correlation Rules

bwNodeControllerExecutorQueueUsage Problem Type Alarm

Exceeded
OID 15607

Status current

Severity Range high

Description This alarm indicates the usage ratio of the executor queue
exceeded the threshold level.

Problem Text The usage ratio of the %npExecutorType% executor exceeded

the threshold level.

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 107
 Alarm Name Attributes Values

Recommended Review the server usage for identifying potential bottlenecks.

Action(s)

Correlation Rules

bwNodeControllerExecutorQueueLatency Problem Type Alarm

Exceeded
OID 15608

Status current

Severity Range high

Description This alarm indicates that the executor queue latency exceeded
the threshold level.

Problem Text The %npExecutorType% executor queue latency exceeded the

threshold level.

Recommended Review the server usage for identifying potential bottlenecks.

Action(s)

Correlation Rules

bwNodeControllerExecutorThreadPool Problem Type Alarm

ProcessingTimeExceeded
OID 15609

Status current

Severity Range high

Description The alarm indicates that the executor thread pool processing
time exceeded the threshold level.

Problem Text The %npExecutorType% executor thread pool processing time

exceeded the threshold level.

Recommended Review the server usage for identifying potential bottlenecks.

Action(s)

Correlation Rules

bwNodeControllerExecutorThreadPool Problem Type Alarm

BusyExceeded
OID 15610

Status current

Severity Range high

Description The alarm indicates that the executor thread pool busy ratio
exceeded the threshold level.

Problem Text The executor thread pool busy ratio exceeded the threshold
level.

Recommended Review the server usage for identifying potential bottlenecks.

Action(s)

Correlation Rules

8.9 BW-NodeLifecycleManagerFault MIB

This section presents SNMP traps (notifications and alarms) for the BW-NodeLifecycleManagerFault MIB
grouped by component.
This MIB defines the faults for the BroadWorks node lifecycle manager Application.

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 108
 Applicable server(s):
Network Function Manager.

8.9.1 SNMP Traps For Component: processmonitor

The table that follows describes the SNMP traps for the processmonitor subcomponent of the BW-
NodeLifecycleManagerFault MIB.
Table 59: SNMP Traps For BW-NodeLifecycleManagerFault:processmonitor
Alarm Name Attributes Values

bwPMnginxLaunched Problem Type Notification

OID 17301

Status current

Severity Range informational

Description This notification indicates that the nginx process has been
started.

Problem Text The nginx process has started.

Recommended
Action(s)

Correlation Rules bwPMnginxLaunched, bwPMnginxShutDown,

bwPMnginxRestarted, and bwPMnginxDeath can be correlated
into a single alarm. These events have to be considered as a
transition of the state machine for the management of the nginx
process

bwPMnginxShutDown Problem Type Notification

OID 17302

Status current

Severity Range informational

Description This notification indicates that the node nginx process has been
manually shut down.

Problem Text The nginx process has shutdown.

Recommended
Action(s)

Correlation Rules bwPMnginxLaunched, bwPMnginxShutDown,

bwPMnginxRestarted, and bwPMnginxDeath can be correlated
into a single alarm. These events have to be considered as a
transition of the state machine for the management of the nginx
process

bwPMnginxRestarted Problem Type Notification

OID 17303

Status current

Severity Range informational

Description This notification provides the date and time of the nginx process
restart.

Problem Text The nginx process has restarted.

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 109
 Alarm Name Attributes Values

Recommended
Action(s)

Correlation Rules bwPMnginxLaunched, bwPMnginxShutDown,

bwPMnginxRestarted, and bwPMnginxDeath can be correlated
into a single alarm. These events have to be considered as a
transition of the state machine for the management of the nginx
process

bwPMnginxDeath Problem Type Notification

OID 17304

Status current

Severity Range critical

Description This notification provides the date and time of the nginx process
death.

Problem Text The nginx process has terminated.

Recommended Ensure nginx process is restarted.

Action(s)

Correlation Rules bwPMnginxLaunched, bwPMnginxShutDown,

bwPMnginxRestarted, and bwPMnginxDeath can be correlated
into a single alarm. These events have to be considered as a
transition of the state machine for the management of the nginx
process

bwPMunicornLaunched Problem Type Notification

OID 17305

Status current

Severity Range informational

Description This notification indicates that the unicorn process has been
started.

Problem Text The unicorn process has started.

Recommended
Action(s)

Correlation Rules bwPMunicornLaunched, bwPMunicornShutDown,

bwPMunicornRestarted, and bwPMunicornDeath can be
correlated into a single alarm. These events have to be
considered as a transition of the state machine for the
management of the unicorn process

bwPMunicornShutDown Problem Type Notification

OID 17306

Status current

Severity Range informational

Description This notification indicates that the node unicorn process has
been manually shut down.

Problem Text The unicorn process has shutdown.

Recommended
Action(s)

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 110
 Alarm Name Attributes Values

Correlation Rules bwPMunicornLaunched, bwPMunicornShutDown,

bwPMunicornRestarted, and bwPMunicornDeath can be
correlated into a single alarm. These events have to be
considered as a transition of the state machine for the
management of the unicorn process

bwPMunicornRestarted Problem Type Notification

OID 17307

Status current

Severity Range informational

Description This notification provides the date and time of the unicorn
process restart.

Problem Text The unicorn process has restarted.

Recommended
Action(s)

Correlation Rules bwPMunicornLaunched, bwPMunicornShutDown,

bwPMunicornRestarted, and bwPMunicornDeath can be
correlated into a single alarm. These events have to be
considered as a transition of the state machine for the
management of the unicorn process

bwPMunicornDeath Problem Type Notification

OID 17308

Status current

Severity Range critical

Description This notification provides the date and time of the unicorn
process death.

Problem Text The unicorn process has terminated.

Recommended Ensure unicorn process is restarted.

Action(s)

Correlation Rules bwPMunicornLaunched, bwPMunicornShutDown,

bwPMunicornRestarted, and bwPMunicornDeath can be
correlated into a single alarm. These events have to be
considered as a transition of the state machine for the
management of the unicorn process

8.10 BW-SoftwareManagementFault MIB

This section presents SNMP traps (notifications and alarms) for the BW-SoftwareManagementFault MIB
grouped by component.
This MIB defines the faults for the BroadWorks Software Management Application.
Applicable server(s):
Network Function Manager.

8.10.1 SNMP Traps For Component: processmonitor

The table that follows describes the SNMP traps for the processmonitor subcomponent of the BW-
SoftwareManagementFault MIB.

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 111
 Table 60: SNMP Traps For BW-SoftwareManagementFault:processmonitor
Alarm Name Attributes Values

bwPMSoftwareControllerLaunched Problem Type Notification

OID 17901

Status current

Severity Range informational

Description This notification indicates that the Software Controller has been
started.

Problem Text The software controller has started.

Recommended
Action(s)

Correlation Rules bwPMSoftwareControllerLaunched,

bwPMSoftwareControllerShutDown,
bwPMSoftwareControllerRestarted,
bwPMSoftwareControllerDeath, and
bwPMSoftwareControllerOutOfMemory can be correlated into a
single alarm. These events have to be considered as a transition
of the state machine for the management of the Software
Controller process

bwPMSoftwareControllerShutDown Problem Type Notification

OID 17902

Status current

Severity Range informational

Description This notification indicates that the Software Controller has been
manually shut down.

Problem Text The software controller has shutdown.

Recommended
Action(s)

Correlation Rules bwPMSoftwareControllerLaunched,

bwPMSoftwareControllerShutDown,
bwPMSoftwareControllerRestarted,
bwPMSoftwareControllerDeath, and
bwPMSoftwareControllerOutOfMemory can be correlated into a
single alarm. These events have to be considered as a transition
of the state machine for the management of the Software
Controller process

bwPMSoftwareControllerRestarted Problem Type Notification

OID 17903

Status current

Severity Range informational

Description This notification provides the date and time of the Software
Controller restart.

Problem Text The software controller has restarted.

Recommended
Action(s)

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 112
 Alarm Name Attributes Values

Correlation Rules bwPMSoftwareControllerLaunched,

bwPMSoftwareControllerShutDown,
bwPMSoftwareControllerRestarted,
bwPMSoftwareControllerDeath, and
bwPMSoftwareControllerOutOfMemory can be correlated into a
single alarm. These events have to be considered as a transition
of the state machine for the management of the Software
Controller process

bwPMSoftwareControllerDeath Problem Type Notification

OID 17904

Status current

Severity Range critical

Description This notification provides the date and time of the Software
Controller death.

Problem Text The software controller has terminated.

Recommended Ensure software controller is restarted.

Action(s)

Correlation Rules bwPMSoftwareControllerLaunched,

bwPMSoftwareControllerShutDown,
bwPMSoftwareControllerRestarted,
bwPMSoftwareControllerDeath, and
bwPMSoftwareControllerOutOfMemory can be correlated into a
single alarm. These events have to be considered as a transition
of the state machine for the management of the Software
Controller process

bwPMSoftwareControllerOutOfMemory Problem Type Notification

OID 17905

Status current

Severity Range high

Description This notification provides the date and time when the Software
Controller application ran out of memory.

Problem Text The software controller ran out of memory.

Recommended Ensure software controller is restarted.

Action(s)

Correlation Rules bwPMSoftwareControllerLaunched,

bwPMSoftwareControllerShutDown,
bwPMSoftwareControllerRestarted,
bwPMSoftwareControllerDeath, and
bwPMSoftwareControllerOutOfMemory can be correlated into a
single alarm. These events have to be considered as a transition
of the state machine for the management of the Software
Controller process.

8.10.2 SNMP Traps For Component: softwareManagement

The table that follows describes the SNMP traps for the softwareManagement subcomponent of the BW-
SoftwareManagementFault MIB.

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 113
 Table 61: SNMP Traps For BW-SoftwareManagementFault:softwareManagement
Alarm Name Attributes Values

bwSoftwareManagementDistribution Problem Type Alarm

CenterConnectivityFailure
OID 17906

Status current

Severity Range high

Description The SoftwareManagement application is not able to connect to

the configured software distribution center.

Problem Text Could not connect to %npNetAddress% on port %npPort%

using %npUserName%.

Recommended Verify that the software distribution center is reachable and

Action(s) validate the configured credentials.

Correlation Rules

bwSoftwareManagementNewCriticalPatch Problem Type Notification

Released
OID 17907

Status current

Severity Range medium

Description A new critical patch is released and missing on certain nodes.

Problem Text A new critical patch %npPatchTitle% is released and must be

applied on the following nodes: %npListOfNodes%.

Recommended
Action(s)

Correlation Rules

bwSoftwareManagementNewDeprecated Problem Type Notification

Patch
OID 17908

Status current

Severity Range medium

Description A deprecated patch is applied on certain nodes.

Problem Text %npPatchTitle% is now deprecated and must be removed from

the following nodes: %npListOfNodes%.

Recommended
Action(s)

Correlation Rules

bwSoftwareManagementReReleased Problem Type Notification

Patch
OID 17909

Status current

Severity Range medium

Description A patch has been rereleased and must be re-applied on certain

nodes.

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 114
 Alarm Name Attributes Values

Problem Text %npPatchTitle% has been rereleased and must be re-applied

on the following nodes: %npListOfNodes%.

Recommended
Action(s)

Correlation Rules

bwSoftwareManagementAdditionalPatch Problem Type Notification

Missing
OID 17910

Status current

Severity Range informational

Description A patch needs an additional patch to completely fix the issue.

Problem Text %npPatchTitle% needs one or more patches to completely fix

the initial issue. Apply the additional patch(es) on the following
nodes: %npListOfNodes%.

Recommended
Action(s)

Correlation Rules

bwSoftwareManagementSWManager Problem Type Notification

InstallationFailure
OID 17911

Status current

Severity Range high

Description An error occurred while upgrading the SWManager.

Problem Text Unable to upgrade the SWManager to %npSWManagerVersion

% on the following nodes: %npListOfNodes%

Recommended
Action(s)

Correlation Rules

8.11 BW-WebContainerFault MIB

This section presents SNMP traps (notifications and alarms) for the BW-WebContainerFault MIB grouped
by component.
This MIB defines the faults for the Web Container application.
Applicable server(s):
Network Function Manager.

8.11.1 SNMP Traps For Component: webcontainer

The table that follows describes the SNMP traps for the webcontainer subcomponent of the BW-
WebContainerFault MIB.

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 115
 Table 62: SNMP Traps For BW-WebContainerFault:webcontainer
Alarm Name Attributes Values

bwWebContainerTransactionGlobalRate Problem Type Notification

LimitExceeded
OID 6001

Status current

Severity Range high

Description Transaction denial due to high transaction rate for a given

webapp.

Problem Text Transaction denied due to high transaction rate for webapp
%npWebAppContext%

Recommended
Action(s)

Correlation Rules

bwWebContainerTransactionUserRate Problem Type Notification

LimitExceeded
OID 6002

Status current

Severity Range high

Description Transaction denial due to high transaction rate for a given

userid.

Problem Text Transaction denied due to high transaction rate for webapp
%npWebAppContext% and userid %npUserId%

Recommended
Action(s)

Correlation Rules

bwWebApplicationCacheDiskFull Problem Type Alarm

OID 6003

Status current

Severity Range low

Description A cache update has failed because the disk is full.

Problem Text The web application "%npWebAppName%" cache is out of

space.

Recommended Clean disk space or reduce the cache size on disk.

Action(s)

Correlation Rules

bwHttpWorkersBusyExceeded Problem Type Alarm

OID 6004

Status current

Severity Range high

Description The ratio of http workerBusy exceeded the threshold level.

Problem Text The ratio of http workerBusy exceeded the threshold level.

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 116
 Alarm Name Attributes Values

Recommended Review server usage for identifying potential bottlenecks.

Action(s)

Correlation Rules

bwWebContainerServerTransactionLimit Problem Type Notification

Exceeded
OID 6009

Status current

Severity Range high

Description The number of incoming requests exceeded the prescribed limit

during the last overload protection period.

Problem Text The number of incoming requests reached

%npReceivedRequestsDuringLastPeriod% for the last
%npProtectionPeriod% %npPeriodUnit%.

Recommended Review incoming traffic to identify potential Denial of Service

Action(s) (DOS) attacks.

Correlation Rules

bwWebContainerWebAppTransaction Problem Type Notification

LimitExceeded
OID 6010

Status current

Severity Range high

Description The number of incoming requests exceeded the prescribed limit

during the last overload protection period.

Problem Text The number of incoming requests for %npWebAppContext%

reached %npReceivedRequestsDuringLastPeriod% for the last
%npProtectionPeriod% %npPeriodUnit%.

Recommended Review incoming traffic to identify potential Denial of Service

Action(s) (DOS) attacks.

Correlation Rules

bwWebContainerUserTransactionLimit Problem Type Notification

Exceeded
OID 6011

Status current

Severity Range high

Description The number of incoming requests exceeded the prescribed limit

during the last overload protection period.

Problem Text The number of incoming requests from

%npWebAppUser% for %npWebAppContext% reached
%npReceivedRequestsDuringLastPeriod% for the last
%npProtectionPeriod% %npPeriodUnit%.

Recommended Review incoming traffic to identify potential Denial of Service

Action(s) (DOS) attacks.

Correlation Rules

bwWebContainerAuthenticationServer Problem Type Alarm

Unreachable
OID 6012

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 117
 Alarm Name Attributes Values

Status current

Severity Range critical

Description The Web Container was unable to connect to the Authentication

Server.

Problem Text The Web Container was unable to connect to the Authentication
Server %npAuthenticationServer%.

Recommended Identify why the WebContainer cannot communicate with the

Action(s) authentication server.

Correlation Rules

bwSslClientAuthWithoutTrust Problem Type Notification

OID 6013

Status current

Severity Range high

Description There is no trust configured on the system but a client

authentication is required on a secure interface.

Problem Text The client authentication is required on the %npProtocol%

secure interface %npName% without any trust configured.

Recommended Configure at least one valid trust anchor.

Action(s)

Correlation Rules

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 118
Appendix A: Additional Information

This section captures additional information related to Cisco BroadWorks Fault and Alarm Management.

9.1 Fault Parameters

This section captures the list of parameters that can are used by the various Cisco BroadWorks faults.
Table 63: Fault Parameters
Parameter Name Attributes Values

OID 1

npAlarmList Description Describes a list of alarms

Type DisplayString

OID 2

npAllowedAttempts Description The number of allowed attempts

Type DisplayString

OID 3

npAnswerTime Description Answer Time

Type DisplayString

OID 4

npBridgeName Description Bridge Name

Type DisplayString

OID 5

npCallAnswered Description Call Answered

Type DisplayString

OID 6

npCallCapacityGroup Description Call Capacity Group

Type DisplayString

OID 7

npCallId Description Call ID

Type DisplayString

OID 8

npCallPersonality Description Call Personality

Type DisplayString

OID 9

npCalledNumber Description Called Number

Type DisplayString

npCalledNumberContext OID 10

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 119
 Parameter Name Attributes Values

Description Called Number Context

Type DisplayString

OID 11

npCaller Description Caller

Type DisplayString

OID 12

npCallingNumber Description Calling Number

Type DisplayString

OID 13

npCallingNumberContext Description Calling Number Context

Type DisplayString

OID 14

npCallingPartyCategory Description Calling Party Category

Type DisplayString

OID 15

npCallingPresentationIndicator Description Calling Presentation Indicator

Type DisplayString

OID 16

npCallsLimit Description Calls Limit

Type DisplayString

OID 17

npCallTreatment Description Call Treatment

Type DisplayString

OID 18

npCallType Description Call Type

Type DisplayString

OID 19

npClientAddress Description Client Address

Type DisplayString

OID 20

npClusterName Description Cluster Name

Type DisplayString

OID 21

npConfiguredAddress Description Configured Address

Type DisplayString

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 120
 Parameter Name Attributes Values

OID 22

npConfiguredPhysicalLocation Description Configured Physical Location

Type DisplayString

OID 23

npCounterName Description Counter Name

Type DisplayString

OID 24

npCountryCode Description Country Code

Type DisplayString

OID 25

npCpuIdleTimePercentage Description CPU Idle Time Percentage

Type DisplayString

OID 26

npCurrentThresholdValue Description Current Threshold Value

Type DisplayString

OID 27

npDate Description Date

Type DisplayString

OID 28

npDepartmentName Description Department Name

Type DisplayString

OID 29

npDestinationUserId Description Destination User ID

Type DisplayString

OID 30

npDeviceAddress Description Device Address

Type DisplayString

OID 31

npDeviceLinePort Description Device Line Port

Type DisplayString

OID 32

npDeviceList Description Device List

Type DisplayString

OID 33
npDeviceName
Description Device Name

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 121
 Parameter Name Attributes Values

Type DisplayString

OID 34

npDeviceType Description Device Type

Type DisplayString

OID 35

npDialedNumber Description Dialed Number

Type DisplayString

OID 36

npDirection Description Direction

Type DisplayString

OID 37

npDomain Description Domain

Type DisplayString

OID 38

npEndpointId Description Endpoint ID

Type DisplayString

OID 39

npExceptionMessage Description Exception Message

Type DisplayString

OID 40

npExpectedVersion Description Expected Version

Type DisplayString

OID 41

npFailedAttempts Description Failed Attempts

Type DisplayString

OID 42

npFailedLoginAttempts Description Failed Login Attempts

Type DisplayString

OID 43

npFeatureName Description Feature Name

Type DisplayString

OID 44

npFilename Description File Name

Type DisplayString

npFilenameAlt OID 45

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 122
 Parameter Name Attributes Values

Description Alternate File Name

Type DisplayString

OID 46

npFirstName Description First Name

Type DisplayString

OID 47

npGaugeName Description Gauge Name

Type DisplayString

OID 48

npGroupId Description Group ID

Type DisplayString

OID 49

npGroupName Description Group Name

Type DisplayString

OID 50

npGroupNumber Description Group Number

Type DisplayString

OID 51

npHost Description Host

Type DisplayString

OID 52

npIndex Description Index

Type DisplayString

OID 53

npInhibitedNeighbors Description Inhibited Neighbours

Type DisplayString

OID 54

npInstanceName Description Instance Name

Type DisplayString

OID 55

npLastIncomingCallTime Description Last Incoming Call Time

Type DisplayString

OID 56

npLastName Description Last Name

Type DisplayString

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 123
 Parameter Name Attributes Values

OID 57

npLicenseAllocation Description License Allocation

Type DisplayString

OID 58

npLicenseKey Description License Key

Type DisplayString

OID 59

npLicenseLimit Description License Limit

Type DisplayString

OID 60

npLocalInterface Description Local Interface

Type DisplayString

OID 61

npLocalPort Description Local Port

Type DisplayString

OID 62

npMailboxId Description Mailbox ID

Type DisplayString

OID 63

npMaxFailedLoginAttempts Description Maximum Failed Login Attempts

Type DisplayString

OID 64

npMessage Description Message

Type DisplayString

OID 65

npMethod Description Method

Type DisplayString

OID 66

npMissingHeader Description Missing Header

Type DisplayString

OID 67

npNbDevicesProcessed Description Number of Devices Processed

Type DisplayString

OID 68
npNbDevicesWithoutMACAddress
Description Number of Devices Without MAC Address

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 124
 Parameter Name Attributes Values

Type DisplayString

OID 69

npNbInhibitedNeighbors Description Number of Inhibited Neighbors

Type DisplayString

OID 70

npNbOfErrors Description Number of Errors

Type DisplayString

OID 71

npNbOfSoapThreads Description Number of SOAP Threads

Type DisplayString

OID 72

npNbTransactions Description Number of Transactions

Type DisplayString

OID 73

npNetworkCallId Description Network Call ID

Type DisplayString

OID 74

npNewAddress Description New Address

Type DisplayString

OID 75

npNewAdministrativeState Description New Administrative State

Type DisplayString

OID 76

npNewDomainName Description New Domain Name

Type DisplayString

OID 77

npNewOperationalState Description New Operational State

Type DisplayString

OID 78

npNewThresholdValue Description New Threshold Value

Type DisplayString

OID 79

npNewZone Description New Zone

Type DisplayString

npNodeId OID 80

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 125
 Parameter Name Attributes Values

Description Node ID

Type DisplayString

OID 81

npOldAdministrativeState Description Old Administrative State

Type DisplayString

OID 82

npOldDomainName Description Old Domain Name

Type DisplayString

OID 83

npOldOperationalState Description Old Operational State

Type DisplayString

OID 84

npOldZone Description Old Zone

Type DisplayString

OID 85

npOperation Description Operation

Type DisplayString

OID 86

npOriginalAddress Description Original Address

Type DisplayString

OID 87

npOriginalCalledNumber Description Original Called Number

Type DisplayString

OID 88

npOriginalCalledNumberContext Description Original Called Number Context

Type DisplayString

OID 89
npOriginalCalledNumberPresentation Description Original Called Number Presentation Indicator
Indicator
Type DisplayString

OID 90

npOriginalCalledReason Description Original Called Reason

Type DisplayString

OID 91

npOriginator Description Originator

Type DisplayString

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 126
 Parameter Name Attributes Values

OID 92

npPeriod Description Period

Type DisplayString

OID 93

npPolicyFeature Description Policy Feature

Type DisplayString

OID 94

npProtocol Description Protocol

Type DisplayString

OID 95

npReason Description Reason

Type DisplayString

OID 96

npRadiusServerList Description Radius Server List

Type DisplayString

OID 97

npReceivedPhysicalLocation Description Received Physical Location

Type DisplayString

OID 98

npReceivedVersion Description Received Version

Type DisplayString

OID 99

npRedirectingNumber Description Redirecting Number

Type DisplayString

OID 100

npRedirectingNumberContext Description Redirecting Number Context

Type DisplayString

OID 101
npRedirectingNumberPresentation Description Redirecting Number Presentation Indicator
Indicator
Type DisplayString

OID 102

npRedirectingReason Description Redirecting Reason

Type DisplayString

OID 103
npRemoteAddress
Description Remote Address

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 127
 Parameter Name Attributes Values

Type DisplayString

OID 104

npRemoteParty Description Remote Party

Type DisplayString

OID 105

npRemotePort Description Remote Port

Type DisplayString

OID 106

npReport Description Report

Type DisplayString

OID 107

npRequest Description Request

Type DisplayString

OID 108

npResolvedAddress Description Resolved Address

Type DisplayString

OID 109

npRoute Description Route

Type DisplayString

OID 110

npServerName Description Server Name

Type DisplayString

OID 111

npServerType Description Server Type

Type DisplayString

OID 112

npServiceProviderId Description Service Provider ID

Type DisplayString

OID 113

npSessionId Description Session ID

Type DisplayString

OID 114

npSessionKey Description Session Key

Type DisplayString

npSipErrorCode OID 115

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 128
 Parameter Name Attributes Values

Description SIP Error Code

Type DisplayString

OID 116

npSipRequestMessage Description SIP Request Message

Type DisplayString

OID 117

npSipResponseMessage Description SIP Response Message

Type DisplayString

OID 118

npSizeLimit Description Size Limit

Type DisplayString

OID 119

npSmdiNumber Description SMDI Number

Type DisplayString

OID 120

npStackTrace Description Stack Trace

Type DisplayString

OID 121

npStartTime Description Start Time

Type DisplayString

OID 122

npSubscriberType Description Subscriber Type

Type DisplayString

OID 123

npTaskName Description Task Name

Type DisplayString

OID 124

npThreadName Description Thread Name

Type DisplayString

OID 125

npThresholdName Description Threshold Name

Type DisplayString

OID 126

npTimeElapsed Description Time Elapsed

Type DisplayString

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 129
 Parameter Name Attributes Values

OID 127

npTimeLength Description Time Length

Type DisplayString

OID 128

npTimestamp Description Timestamp

Type DisplayString

OID 129

npTraceType Description Trace Type

Type DisplayString

OID 130

npTrunkGroupName Description Trunk Group Name

Type DisplayString

OID 131

npUrl Description Uniform Resource Locator

Type DisplayString

OID 132

npUserId Description User ID

Type DisplayString

OID 133

npUserName Description User Name

Type DisplayString

OID 134

npUserNumber Description User Number

Type DisplayString

OID 135

npUserUid Description User UID

Type DisplayString

OID 136

npThresholdDescription Description Threshold Description

Type DisplayString

OID 137

npSubscriberId Description Subscriber ID

Type DisplayString

OID 138
npCommand
Description Command

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 130
 Parameter Name Attributes Values

Type DisplayString

OID 139

npPublicIdentity Description Public Identity

Type DisplayString

OID 140

npDataReference Description Data Reference

Type DisplayString

OID 141

npResultCode Description Result Code

Type DisplayString

OID 142

npResultCodeType Description Result Code Type

Type DisplayString

OID 143

npError Description Error

Type DisplayString

OID 144

npLoginLevel Description Login Level

Type DisplayString

OID 145

npMaximumNbItems Description Maximum Number of Items

Type DisplayString

OID 146

npRequestUriUser Description Requested User URI

Type DisplayString

OID 147

npWebAppContext Description Web Application context path

Type DisplayString

OID 148

npTreatment Description Treatment received for call

Type DisplayString

OID 149

npPrimaryAddress Description Primary Address

Type DisplayString

npSecondaryAddress OID 150

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 131
 Parameter Name Attributes Values

Description Secondary Address

Type DisplayString

OID 151

npServiceProviderName Description Service Provider Name

Type DisplayString

OID 152

npConfigVersion Description Configuration revision number

Type DisplayString

OID 153

npApplicationName Description Name of the application.

Type DisplayString

OID 154

npOldEffectiveState Description Old Effective State

Type DisplayString

OID 155

npNewEffectiveState Description New Administrative State

Type DisplayString

OID 156

npApplicationMemory Description The quantity of memory allocated for the application.

Type DisplayString

OID 157

Description The total amount of memory in the system that is available to

npSystemMemory
allocate for applications.

Type DisplayString

OID 158

npSourceCodec Description Name of original codec.

Type DisplayString

OID 159

npDestinationCodec Description Name of destination codec.

Type DisplayString

OID 160

npMaximumAttempt Description Maximum number of attempt.

Type DisplayString

OID 161
npMacAddress
Description Mac Address

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 132
 Parameter Name Attributes Values

Type DisplayString

OID 162

npMaxNumberOfSessions Description Maximum number of sessions

Type DisplayString

OID 163

npSACGroupId Description The Id of the SAC group

Type DisplayString

OID 164

npFileURL Description The file URL

Type DisplayString

OID 165

npObjectId Description Object Identifier

Type DisplayString

OID 166

npMSCAddr Description network MSC Address

Type DisplayString

OID 167

npRoutePointName Description The name of the route point

Type DisplayString

OID 168

npProfileDescription Description The profile description

Type DisplayString

OID 169

npTransactionLimitPeriod Description The transaction limit period in secs

Type DisplayString

OID 170

npGlobalTransactionLimit Description The configured global transaction limit

Type DisplayString

OID 171

npNetAddress Description The IP/FQDN Address

Type DisplayString

OID 172

Description The name of the scheduled report. This parameter is encoded

npReportName
using the application/x-www-form-urlencoded MIME format.

Type DisplayString

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 133
 Parameter Name Attributes Values

OID 173

npDateTime Description The date and time

Type DisplayString

OID 174

npTimeoutValue Description The timeout value

Type DisplayString

OID 175

npMediaServerAddress Description The address of the Media Server.

Type DisplayString

OID 176

npUserDN Description The DN of the paging group.

Type DisplayString

OID 177

npApplicationServerSetName Description The Application Server set name

Type DisplayString

OID 178

Description A comma-separated list of Hosting NE names that are part of

npApplicationServerSetContent
the set.

Type DisplayString

OID 179

npIdentity Description The main PUI for the profile.

Type DisplayString

OID 180

npAlternate Description The alternate PUI which failed to be linked.

Type DisplayString

OID 181

npDatabaseName Description The database name.

Type DisplayString

OID 182

npSite Description The database site.

Type DisplayString

OID 183

npEnterpriseId Description The enterprise Id.

Type DisplayString

npAddress OID 184

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 134
 Parameter Name Attributes Values

Description The IP address.

Type DisplayString

OID 185

npResourceRecordType Description Resource record type (NAPTR, SRV, A, PTR) in the query.

Type DisplayString

OID 186

npIMRNNumber Description IMRN number

Type DisplayString

OID 187

npSIPCallID Description SIP Call ID

Type DisplayString

OID 188

npFrom Description Caller

Type DisplayString

OID 189

npDatabaseObjectType Description Database Object type.

Type DisplayString

OID 190

npWebAppName Description Web Application Name

Type DisplayString

OID 191

Description The provisioning action requested to BroadCloud. Can be

npBroadCloudRequest
POST, PUT or DELETE

Type DisplayString

OID 192

npBroadCloudUid Description The BroadCloud unique subscriber id.

Type DisplayString

OID 193

npBroadCloudService Description The BroadCloud service for which the request was made.

Type DisplayString

OID 194

npBroadCloudFailureReason Description The reason for the failure.

Type DisplayString

OID 195
npSCCASPSIDNNumber
Description SCC AS PSI DN number.

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 135
 Parameter Name Attributes Values

Type DisplayString

OID 196

npDBSchemaName Description The name of the database schema instance.

Type DisplayString

OID 197

npHttpWorkersBusy Description The ratio of busy workers.

Type DisplayString

OID 198

npExecutorType Description The executor type (ajp, httpnio, cti, ocic, ocip).

Type DisplayString

OID 199

npExecutorQueueUsage Description The ratio of executor queue usage.

Type DisplayString

OID 200

npExecutorQueueLatency Description The ratio of executor queue latency.

Type DisplayString

OID 201

npExecutorDurationUnit Description The measurement unit.

Type DisplayString

OID 202

npExecutorThreadPoolProcessingTime Description The executor thread pool processing time.

Type DisplayString

OID 203
npExecutorThreadPoolProcessing Description The executor thread pool processing time unit.
DurationUnit
Type DisplayString

OID 204

npExecutorThreadPoolBusy Description The executor thread pool busy ratio.

Type DisplayString

OID 205

npProcessMemoryUsage Description The process memory usage.

Type DisplayString

OID 206

Description The number of requests received during the last overload

npReceivedRequestsDuringLastPeriod
protection period.

Type DisplayString

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 136
 Parameter Name Attributes Values

OID 207

npProtectionPeriod Description The duration of the overload protection period.

Type DisplayString

OID 208

Description The unit used for the overload protection period. Its default value
npPeriodUnit
is seconds.

Type DisplayString

OID 209

npWebAppUser Description The user of the web app

Type DisplayString

OID 210

npNEMaintenancePartitionId Description The subscriber's NE maintenance partition

Type DisplayString

OID 211

sccpObjId Description The sccp object id

Type Integer32

OID 212

sccpState Description The sccp state

Type Integer32

OID 213

sccpAffectedSsn Description The sccp affected sub system number

Type Integer32

OID 214

sccpAffectedSsnSp Description The sp of affected sub system number

Type Integer32

OID 215

sccpAffectedSsnSsn Description The affected sub system number

Type Integer32

OID 216

sccpConnectionId Description The sccp connection id

Type Integer32

OID 217

sccpResetReason Description The sccp reset reason

Type DisplayString

sccpOriginator OID 218

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 137
 Parameter Name Attributes Values

Description The sccp originator

Type DisplayString

OID 219

sccpModuleId Description The sccp module id

Type Integer32

OID 220

sccpSubModuleId Description The sccp sub-module id

Type Integer32

OID 221

sccpMtpSap Description The sap id

Type Integer32

OID 222

sccpErrorCode Description The sccp error code

Type Integer32

OID 223

sccpBitMask Description The sccp bit mask

Type Integer32

OID 224

sccpDroppedApiId Description The sccp dropped api id

Type Integer32

OID 225

sccpErrorLevel Description The sccp error level

Type Integer32

OID 226

sccpErrorFlag Description The sccp error flag

Type Integer32

OID 227

sccpPointCode Description The point code

Type Integer32

OID 228

m3uaAsId Description The m3ua AS id

Type Integer32

OID 229

m3uaLocalSpId Description The m3ua local SP id

Type Integer32

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 138
 Parameter Name Attributes Values

OID 230

m3uaRemSpId Description The m3ua remote SP id

Type Integer32

OID 231

m3uaState Description The m3ua state

Type DisplayString

OID 232

m3uaNwSpId Description The m3ua n/w SP id

Type Integer32

OID 233

m3uaAspId Description The m3ua ASP id

Type Integer32

OID 234

m3uaOptIndParams Description The m3ua optional indication paramters

Type Integer32

OID 235

m3uaOptIndParamsBitmap Description The m3ua optional indication paramter's bitmap

Type Integer32

OID 236

m3uaOptIndParamsDownCause Description The m3ua optional indication paramter's down cause

Type Integer32

OID 237

m3uaSgId Description The m3ua SG id

Type Integer32

OID 238

m3uaAssocId Description The association id

Type Integer32

OID 239

m3uaNumInStreams Description The number of input streams

Type Integer32

OID 240

m3uaNumOutStreams Description The number of output streams

Type Integer32

OID 241
m3uaErrSrc
Description The m3ua error source

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 139
 Parameter Name Attributes Values

Type Integer32

OID 242

m3uaEcode Description The m3ua error code

Type Integer32

OID 243

m3uaInfoLength Description The m3ua information length

Type Integer32

OID 244

m3uaPInfoStr Description The m3ua information string

Type OCTET STRING

OID 245

m3uaRegStatus Description The m3ua registration status

Type Integer32

OID 246

m3uaDeregStatus Description The m3ua de-registration status

Type Integer32

OID 247

m3uaNewAs Description The m3ua new AS

Type Integer32

OID 248

m3uaDelAs Description The m3ua deleted AS

Type Integer32

OID 249

ss7pInstanceId Description The ss7p instance id

Type Integer32

OID 250

ss7pStackType Description The ss7p stack type

Type Integer32

OID 251

ss7pEcode Description The ss7p error code

Type Integer32

OID 252

ss7pEntityStatus Description The ss7p entity status

Type DisplayString

ss7pFailureEcode OID 253

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 140
 Parameter Name Attributes Values

Description The ss7p failure error code

Type Integer32

OID 254

ss7pTierId Description The ss7p tier id

Type Integer32

OID 255

ss7pPc Description The ss7p point code

Type Integer32

OID 256

ss7pPcType Description The ss7p point code type

Type Integer32

OID 257

ss7pSpId Description The ss7p SP id

Type Integer32

OID 258

ss7pNi Description The ss7p network indicator

Type Integer32

OID 259

ss7pVariant Description The ss7p variant

Type DisplayString

OID 260

ss7pSapId Description The ss7p sap id

Type Integer32

OID 261

ss7pSsn Description The ss7p sub-system number

Type Integer32

OID 262

ss7pSsId Description The ss7p sub-system id

Type Integer32

OID 263

ss7pNumBitsInstanceId Description The ss7p T2 bits intance id

Type Integer32

OID 264

ss7pFlag Description The ss7p flag

Type DisplayString

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 141
 Parameter Name Attributes Values

OID 265

ss7pEmStatus Description The ss7p EM status

Type DisplayString

OID 266

ss7pEmInfoAddr Description The Em IP address

Type OCTET STRING (SIZE(30))

OID 267

ss7pEmInfoServerPort Description The Em server port

Type Integer32

OID 268

ss7pEmInfoMinClientPort Description The Em minimum client port

Type Integer32

OID 269

ss7pEmInfoMaxClientPort Description The Em maximum client port

Type Integer32

OID 270

ss7pInstanceType Description The ss7p instance type

Type DisplayString

OID 271

ss7pIp Description The ss7p IP address

Type OCTET STRING (SIZE(20))

OID 272

ss7pPort Description The Ss7p port

Type Integer32

OID 273

ss7pIpStr Description The ss7p IP address in string

Type OCTET STRING (SIZE(20))

OID 274

mapInstId Description The map instance id

Type Integer32

OID 275

mapTierLevel Description The map platform tier level

Type Integer32

OID 276
mapErrorCode
Description The map error code

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 142
 Parameter Name Attributes Values

Type Integer32

OID 277

mapInfoLen Description The map information length

Type Integer32

OID 278

mapInfoStr Description The Em information string

Type OCTET STRING

OID 279

mapStatus Description The map status

Type DisplayString

OID 280

mapInstanceType Description The map instance type

Type DisplayString

OID 281

mapVariant Description The map platform variant

Type Integer32

OID 282

mapIp Description The map ip address

Type OCTET STRING (SIZE(30))

OID 283

mapPort Description The map port

Type Integer32

OID 284

mapEmStatus Description The map EM status

Type DisplayString

OID 285

mapEmInfoAddr Description The map EM's IP address

Type OCTET STRING (SIZE(30))

OID 286

mapEmInfoServerPort Description The map EM's server port

Type Integer32

OID 287

mapEmInfoMinClientPort Description The map EM's minimum client port

Type Integer32

mapEmInfoMaxClientPort OID 288

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 143
 Parameter Name Attributes Values

Description The map EM's maximum client port

Type Integer32

OID 289

npSecureTlktToolName Description The name of the Secure Toolkit.

Type DisplayString

OID 290

npSecureTlktToolResult Description The result of the Secure Toolkit.

Type DisplayString

OID 291

npIMRN Description The IP Multimedia Routing Number.

Type DisplayString

OID 292

npDeviceLinePortOrPublicIdentity Description The Device Line/Port or Public Identity.

Type DisplayString

OID 293

npLockoutCounter Description The lockout count since last reset.

Type DisplayString

OID 294

npLockoutPeriod Description The number of minutes or permanent.

Type DisplayString

OID 295

npDeviceProfileName Description The Device Profile Name.

Type DisplayString

OID 296

npDeviceFileRequestMessage Description The Device File Request Message.

Type DisplayString

OID 297

npWebAppContextPath Description The Web Application context path.

Type DisplayString

OID 298

npSS7SubsystemNumber Description The SS7 Subsystem number.

Type DisplayString

OID 299

npAuthenticationServer Description The authentication server.

Type DisplayString

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 144
 Parameter Name Attributes Values

OID 300

npLdapVersion Description The configured LDAP version.

Type DisplayString

OID 301

npSchemaInstanceName Description The schema instance name.

Type DisplayString

OID 302

npSchemaInstanceState Description The schema instance state.

Type DisplayString

OID 303

npMessageCount Description The number of Messages.

Type DisplayString

OID 304

npProfileServer Description The ProfileServer.

Type DisplayString

OID 305

npPercentEventQueueFiles Description The percentage of event queue files in use.

Type DisplayString

OID 306

npMaxNumEventQueueFiles Description The Maximum number of event queue files allowed.

Type DisplayString

OID 307

npOldestEventAge Description The age of oldest event not saved on the Database Server.

Type DisplayString

OID 308

Description The maximum age of an event that can be saved on the

npMaxEventAge
Database Server.

Type DisplayString

OID 309

npLogFile Description The log filename.

Type DisplayString

OID 310

npIS41Operation Description The IS41 operation.

Type DisplayString

npMissingComponent OID 311

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 145
 Parameter Name Attributes Values

Description The missing component.

Type DisplayString

OID 312

npState Description The state id the component.

Type DisplayString

OID 313

npExistingComponent Description The existing component.

Type DisplayString

OID 314

npBridgeParticipantId Description The bridge participant id.

Type DisplayString

OID 315

npRoomId Description The room id.

Type DisplayString

OID 316

npErrorCode Description The error code.

Type DisplayString

OID 317

npErrorMessage Description The error message.

Type DisplayString

OID 318

npPort Description The Port.

Type DisplayString

OID 319

Description The name of the Hypertext Transfer Protocol (HTTP) server or

npName
the Internet Protocol (IP) address for other protocols.

Type DisplayString

OID 320

npRepositoryUri Description The URI of the repository.

Type DisplayString

OID 321

npRemoteAddresses Description The remote addresses.

Type DisplayString

OID 322
npConnectionType
Description The connection type.

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 146
 Parameter Name Attributes Values

Type DisplayString

OID 323

npFileCapacityInBytes Description The capacity of a file in bytes.

Type DisplayString

OID 324

npFileSystemPathList Description The list of paths.

Type DisplayString

OID 325

npDiskUsageInBytes Description The amount of disk space currently in use.

Type DisplayString

OID 326

npValidLicenseId Description The valid license Id.

Type DisplayString

OID 327

npNFMName Description The Network Function Manager name.

Type DisplayString

OID 328

npNodeName Description The node name.

Type DisplayString

OID 329

npLicenseIdInstance Description The details of the licenseId instance.

Type DisplayString

OID 330

Description The Fully Qualified Domain Name (FQDN) of the Network

npNFMFqdn
Function Manager.

Type DisplayString

OID 331

npBroadWorksRelease Description The BroadWorks release.

Type DisplayString

OID 332

npGraceAction Description The action taken on grace period expiration.

Type DisplayString

OID 333

npHours Description The number of hours remaining before taking action.

Type DisplayString

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 147
 Parameter Name Attributes Values

OID 334

npEnterpriseTrunkName Description The name of the enterprise trunk.

Type DisplayString

OID 335

npInvalidLicenseId Description The invalid license Id.

Type DisplayString

OID 336

npCallingParty Description The calling party.

Type DisplayString

OID 337

npLicenseId Description The licenseId.

Type DisplayString

OID 338

npContainerName Description The name of the container.

Type DisplayString

OID 339

npDatabaseNode Description The hostname and port of the database node.

Type DisplayString

OID 340

Description A space separated list of all the hostname and port of the
npDatabaseNodes
database nodes.

Type DisplayString

OID 341

npQueueName Description The name of the queue.

Type DisplayString

OID 342

npExtremeOverloadReason Description The reason for the extreme overload, either expiration or count.

Type DisplayString

OID 343

npApplicationId Description The application ID.

Type DisplayString

OID 344

npChannelId Description The Xsi channel Id.

Type DisplayString

npChannelSetId OID 345

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 148
 Parameter Name Attributes Values

Description The Xsi channel set id.

Type DisplayString

OID 346

npChannelOwner Description The Xsi channel owner.

Type DisplayString

OID 347

npRequestName Description The request name

Type DisplayString

OID 348

npPatchTitle Description The patch title.

Type DisplayString

OID 349

npListOfNodes Description The list of nodes.

Type DisplayString

OID 350

npSWManagerVersion Description The Software Manager version.

Type DisplayString

OID 351

Description The calling asserted identity, including the asserted name and
npCallerAssertedIdentity
number.

Type DisplayString

OID 352

npCallingAssertedNumber Description The calling asserted number.

Type DisplayString

OID 353

npCallingAssertedNumberContext Description The calling asserted number context.

Type DisplayString

OID 354

npCurrentCounterValue Description The current value of the counter.

Type DisplayString

OID 355

npClearThresholdValue Description The value to reach by the gauge to clear the alarm.

Type DisplayString

OID 356
npCouchbaseNodes
Description The List of Couchbase nodes.

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 149
 Parameter Name Attributes Values

Type DisplayString

OID 357

npTableName Description The name of the table that was modified.

Type DisplayString

OID 358

npErrorText Description The error text.

Type DisplayString

OID 359

npConnectionCount Description The number of connections.

Type Integer32

OID 360

npDefaultProfilePUI Description The default user pui.

Type DisplayString

OID 361

npDataCenter Description The name of the data center.

Type DisplayString

OID 362

npResellerId Description The reseller id.

Type DisplayString

OID 363

npTcapObjId Description The tcap object ID.

Type DisplayString

OID 364

npTcapModuleId Description The tcap module ID.

Type DisplayString

OID 365

npSs7pSapId Description The sap ID.

Type DisplayString

OID 366

npTcapErrorCode Description The tcap error code.

Type DisplayString

OID 367

npTcapErrorStr Description The tcap error string.

Type DisplayString

npTcapBitMask OID 368

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 150
 Parameter Name Attributes Values

Description The tcap bit mask.

Type DisplayString

OID 369

npTcapUserId Description The tcap user ID.

Type DisplayString

OID 370

npDialogId Description The dialog ID.

Type DisplayString

OID 371

npDialogState Description The dialog state.

Type DisplayString

OID 372

npTcapTransId Description The transaction ID.

Type DisplayString

OID 373

npTcapTransState Description The transaction state.

Type DisplayString

OID 374

npInvokeId Description The invoke ID.

Type DisplayString

OID 375

npInvokeState Description The invoke state.

Type DisplayString

OID 376

npResellerName Description The reseller name.

Type DisplayString

OID 377

npPercent Description The percent.

Type DisplayString

OID 378

npSourceOrFrom Description The IP address and port of the source or SIP URI of the caller.

Type DisplayString

OID 379

npInterface Description The interface name.

Type DisplayString

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 151
 Parameter Name Attributes Values

OID 380

npThreshold Description The threshold value.

Type DisplayString

OID 381

npTransport Description The transport used to send SIP OPTIONS.

Type DisplayString

OID 382

npQueryDuration Description The query duration time.

Type DisplayString

OID 383

npConfiguredMax Description The threshold time configured.

Type DisplayString

OID 384

Description The discrepancy ratio between the average execution time of a

npDiscrepancyRatio given command for the current run and the Life-Time average
for this same command.

Type DisplayString

OID 385

npCurrentAverage Description The current command average query time for this run.

Type DisplayString

OID 386

Description The current command average query time over the life time of
npLifeTimeAverage
CallP Timing Verifications.

Type DisplayString

OID 387

npBytes Description The number of bytes.

Type DisplayString

OID 388

npLimitType Description The limit type that can be total, incoming or outgoing .

Type DisplayString

OID 389

npConnectionPoolName Description The connection pool name.

Type DisplayString

OID 390

npRemoteHostPort Description The remote address normalized.

Type DisplayString

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 152
 Parameter Name Attributes Values

OID 391

npSipEventMessage Description The SIP event remote address normalized.

Type DisplayString

OID 392

npUserFullJid Description The user full JID.

Type DisplayString

OID 393

Description The number of records in the MUC queue table for the user
npMucQueueRecords
resource in the last 1 minute.

Type DisplayString

OID 394

npMucQueueTable Description The name of the MUC queue table.

Type DisplayString

OID 395

npNbFiles Description Number of Files

Type DisplayString

OID 396

npPartitionUsed Description The percentage of partition used.

Type DisplayString

OID 397

npPartitionUsedLimit Description The percentage limit of partition used.

Type DisplayString

OID 398

npHttpUrl Description The configured URL for the server.

Type DisplayString

OID 399

npBcctConnection Description The BCCT connectiion.

Type DisplayString

OID 400

npBcctProtocol Description The BCCT protocol.

Type DisplayString

OID 401

npDocumentID Description The BCCT protocol.

Type DisplayString

npAdmin OID 402

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 153
 Parameter Name Attributes Values

Description The BCCT protocol.

Type DisplayString

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 154
Appendix B: bwSystemHealthReport Alarm Problem Text

The following table describes the problem text contained in the bwSystemHealthReport.
Problem text Severity Recommended action

The following FileSystems have exceeded the size Try to free up some space on FileSystems that
limit: Critical have exceeded a limit. Consider deleting old logs,
Critical old database backups and/or old software versions
[STOPBW(<STOPBW_THRESHOLD>%) ::
in directories /var/broadworks/logs, /usr/local/
<PARTITION>] Major broadworks and /bw/install. BroadSoft doesn't
[CRITICAL(<CRITICAL_THRESHOLD>%) :: Warning recommend keeping more that three software
<PARTITION>] versions installed on a given server.
[HIGH(<HIGH_THRESHOLD>%) :: <PARTITION>]
[WARNING(<WARNING_THRESHOLD>%) ::
<PARTITION>]

The following sub agents are not started: Minor To start the SNMP sub agent(s): [As root user,
do: /etc/init.d/init.subagentctl start] [As root user,
[MIBIISA sub agent]
do: /etc/init.d/init.es_agent start]
[ESD sub agent]

BroadWorks <server_type> processes in trouble:

[Invalid date in BroadWorks License file.] Minor [Invalid date in BroadWorks License file, please
contact BroadSoft Support.]

[BroadWorks License expired. License expire Minor [BroadWorks License expired, please contact
date:<expired_date>] BroadSoft Support.]

[BroadWorks License expired. License expire Minor [BroadWorks License is expiring, please contact
date:<expired_date>] BroadSoft Support.]

[SNMP Agent not running] Critical [Broadworks needs to be restarted]

[Configuration agent not running] Critical [The Configuration Agent needs to be restarted
(configdctl start)]

[The Software Manager is not running] Critical [The Software Manager needs to be restarted
(startswman.pl)]

[<CONTAINER_NAME> not running] Critical [The <FAULTY_APPLICATION> application needs

to be restarted]

[<CONTAINER_NAME> process monitor not Critical [The <FAULTY_APPLICATION> application needs

running] to be restarted]

[Current DSN permanent size (<PERM_SIZE>M) Major [Contact BroadSoft Support to get the DSN
exceeds the maximum of 128M for a system with resizing procedure]
or with less than 1G in physical memory]

[Current DSN permanent size (<PERM_SIZE>M) Major [Contact BroadSoft Support to get the DSN
exceeds <MINIMUM_RATIO>\% of the memory resizing procedure]
available in the system <MEM_SIZE>M]

[Open Client Server Monitoring not running] Critical [The Web Server needs to be restarted]

[Open Client Server not running] Critical [The Web Server needs to be restarted]

[APACHE Monitoring not running] Critical [The Web Server needs to be restarted]

[APACHE not running] Critical [The Web Server needs to be restarted]

[Flash policy server process monitor not running] Critical [The Web Server needs to be restarted]

[Flash policy server not running] Critical [The Web Server needs to be restarted]

[<PROCESS_NAME> process monitor not Critical [The <SERVER_TYPE> needs to be restarted]

running]

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 155
 Problem text Severity Recommended action

[<PROCESS_NAME> not running] Critical [The <SERVER_TYPE> needs to be restarted]

[License Server process monitor not running] Critical [The Virtualized License Server needs to be
restarted]

[License Server not running] Critical [The Virtualized License Server needs to be
restarted]

[DbManagement not running] Critical [The Database Server needs to be restarted.

Please restart BroadWorks server using restartbw.]

[SSHD not running] Critical [Restart the sshd process (/etc/init.d/sshd start)]

[TIMESTEND not running] Critical [The TimesTen daemon (TIMESTEND) needs

to be restarted. Please refer to the BroadWorks
Maintenance Guide for detailed procedures on how
to restart the process(es) currently not running on
this server, or contact your BroadWorks support
team.]

[*** Internal error in healthmon script *** Major [Contact BroadSoft support.]
<INTERNAL_ERROR_OUTPUT>]

[Could not properly monitor TimesTen permanent Minor Try running “<command>” and see if you get any
and temporary memory area usage. This error is results. If this problem persists, please contact
not fatal and can be caused by an impossibility to BroadSoft support.
obtain a connection to the TimesTen engine.]

[TimesTen permanent memory area is at Critical, Major or Minor [Increase your datastore permanent size area
<PERM_MEM_PERCENT> of total permanent (using the resizeDSN tool]
size. (Currently in use size is at <PERM_IN_USE>.
Allocated size is <ALLOCATED_SIZE>, high water
mark is <HIGH_WATER_MARK> and in use size
is <PERM_IN_USE>]

[TimesTen temporary memory area is at Critical, Major or Minor [Increase your datastore temporary size area
<TEMP_MEM_PERCENT> of total temporary (using the resizeDSN tool)]
size. (Currently in use size is at <TEMP_IN_USE>.
Allocated size is <ALLOCATED_SIZE>, high water
mark is <HIGH_WATER_MARK> and in use size
is <TEMP_IN_USE>]

[TimesTen data store permanent size is Critical [Check the data store permanent size and adjust
different (<PERM_ALLOCATED> compared to it so that all peers have the same permanent size
<CURRENT>) on peers in the cluster.] (using the resizeDSN tool).]

[TimesTen data store temporary size is Critical [Check the data store temporary size and adjust
different (<PERM_ALLOCATED> compared to it so that all peers have the same temporary size
<CURRENT>) on peers in the cluster.] (using the resizeDSN tool).]

[SLAPD not running] Critical [Restart the slapd process (/etc/init.d/ldapctl start)]

[An error occured with the LDAP server Critical [Restart the LDAP server replication by importing
replication.] the database on the secondary from the primary.]

[Cannot connect to the LDAP master server to Critical [Configure LDAP master and slave server with
retrieve replication status.] same replication port.]

[Cannot connect to the LDAP slave server to Critical [Configure LDAP master and slave server with
retrieve replication status.] same replication port.]

[MYSQLD is not running] Critical [The MySQL daemon (MYSQLD) needs to

be restarted. Please refer to the BroadWorks
Maintenance Guide for detailed procedures on how
to restart the process(es) currently not running on
this server, or contact BroadSoft support team.]

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 156
 Problem text Severity Recommended action

[Database integrity failed] Critical [The MySQL database needs to be repaired:

<OUTPUT_MSG>. Please restart BroadWorks
server using restartbw command to repair the
database. If the problem persist, contact BroadSoft
support team.]

[DSN not initialized properly.] Critical [The server must be re-installed. If the problem
persist, contact BroadSoft support team.]

[Application schema not properly installed.] Critical [The server must be re-installed. If the problem
persist, contact BroadSoft support team.]

[Oracle DBS Utilities Error Detected] Critical [The server must be re-installed. If the problem
persist, contact BroadSoft support team.]

[Oracle Grid not running.] Critical [Oracle Grid Infrastructure (High Availability
framework) needs to be restarted]

[Fragmentation detected on <ENTITY>.] Warning [Contact BroadSoft Support]

[Low preallocation level detected on <ENTITY>] Warning [Contact BroadSoft Support]

[<NUM_OF_ERROR> Oracle redo log Major [Contact BroadSoft Support]

checkpointing error(s) detected.]

[Oracle Observer not running] Major [Oracle Observer needs to run on a separate
server (PS) and must be configured to monitor this
DBS.]

[Oracle Database failover detected] Major [Restore the original primary site and perform a
manual switch-over using the DBS observer CLI]

[Oracle redundancy error detected, failure on the Major [Make sure redo apply is enabled by running
primary site will result in data loss.] 'dbsctl redo apply=on' on the standby site. If the
error persists, contact BroadSoft Support.]

[Oracle Database secondary host <HOST_NAME> Warning [Verify <HOST> reacheability or reinstall a new
is not ready.] standby and reconfigure redundancy.]

[Could not found an active primary database Major [Log back as bwadmin on the primary DBS to
instance.] complete redundancy configuration.]

[Could not get reliable peer information.] Major [Please restart BroadWorks server using
restartbw.]

[Oracle Database not running.] Critical [Oracle Database must be restarted.]

[Internal: problem with healthmon script Critical [Contact BroadSoft Support.]

(validate_peers_state method)]

[Error in transmitting commands to a remote peer. Critical [Make sure ssh and replication are correctly
Reported error is: <ERROR>] configured. (If a server has been unreachable for a
long time, its database may be out-of-synch. It can
be re-synchronized with importdb.pl. Please refer
to the BroadWorks Maintenance Guide.]

[Replication: a remote server is in MAINTENANCE Warning [Validate that the peer server is in the right state.]
state. Replication test bypassed.]

[Replication: a remote server <PEER> is not Major [Validate that the peer server <PEER> is
responding or not in RUNNING state. Replication reachable.]
test bypassed.]

[File replication is not running.] Critical [Perform a file replication restart (repctl restart)]

[Cannot connect to the MySQL database to Critical [Contact BroadSoft Support.]

retrieve replication status.]

[An error occured with the database replication.] Critical [Restart the database replication by importing the
database on the secondary from the primary.]

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 157
 Problem text Severity Recommended action

[The following peers' clocks have a delay of Minor [Make sure that the clocks are synchronized.
+/- <DIFFERENCE> seconds with the local If using NTP, ensure that all peers are using
(<LOCAL_HOSTNAME>) clock: <PEER_LIST>] the same server. If using NTP with the same
server, augment the frequency at which the time is
synchronized with the server for each peer.]

[Not all members of the cluster use the same Minor [Make sure that all of this server's peers are
SWManager version.] running the same SWManager version.]

[All members of this cluster are not at the same Major [The output of the checkPeer.pl script returned
patch level.] the following output: <OUTPUT>. All servers in a
cluster must be at the same patch level.]

[Hostname <HOSTNAME> cannot be found in Major [Change the server hostname or change the
redundancy peers (peerctl ls)] redundancy peer hostname (peerctl)]

[Database is locked: no provisioning can occur on Major [Unlock the server using peerctl]
the server]

[Server is NOT unlocked] Major [Unlock the server via the CLI or SNMP.]

[Failure in reading server administrative state from Major [Make sure the Configuration Agent is started
the Configuration Agent] (configdctl status)]

[Unknown server state received from server: Major [Make sure the SNMP Agent is started (snmpdctl
<STATE>] status)]

[The directory for offline CDR file queueing (/ Minor [File Queuing could not be automatically disabled.
var/broadworks/billing/rf/) takes more than 5% Manually disable it at the CLI: AS_CLI/Interface/
of the available space on the partition where it is Accounting/BroadWorksCDRInterface/Diameter/
mounted. File queuing will be disabled.] Offline> set enableFileQueuing false. Manually
re-enable file queuing when the disk full condition
is cleared. Verify that the file queuing retention
time is appropriate for the call rate and the disk
space. Verify that the listed offline charging servers
are up and running. Verify that there is network
connection between the Application Server and the
offline charging servers. Verify that the Diameter
interface is properly configured on the Application
Server.]

[The partition on which the directory for offline CDR Minor [File Queuing could not be automatically disabled.
file queueing (/var/broadworks/billing/rf/) is hosted Manually disable it at the CLI: AS_CLI/Interface/
is <PARTITION_USAGE>% full.] Accounting/BroadWorksCDRInterface/Diameter/
Offline> set enableFileQueuing false. Manually
re-enable file queuing when the disk full condition
is cleared. Verify that the file queuing retention
time is appropriate for the call rate and the disk
space. Verify that the listed offline charging servers
are up and running. Verify that there is network
connection between the Application Server and the
offline charging servers. Verify that the Diameter
interface is properly configured on the Application
Server.]

[Replication is not running for DSN <DSN>. Critical [Replication must be started (repctl start). If
Databases may be out-of-synch.] databases are out-of-synch they must be re-
synchronized first (with the importdb.pl tool).
Please refer to the BroadWorks Maintenance
Guide for detailed procedures.]

[Internal: problem with healthmon script Critical [Contact BroadSoft Support.]

(monitor_redundancy method)]

[Insufficient space to perform backup] Major [Try to free up some space by deleting old logs, old
database backups and/or old software versions.]

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 158
 Problem text Severity Recommended action

[Dangling processes detected: Informational [Over time dangling processes may cause
performance impact on your BroadWorks system.
<PROCESS_HEADER> Those processes were identified and killed
<DANGLING_PROCESSES>] automatically.]

[The swap configured on the system is very Critical (50% of required [You should add more swap space to the system.]
insufficient.] swap detected) or
Major (65% of required
swap detected)

[ The swap configured on the system is Warning (80% of [Consider adding more swap space to the system.]
insufficient. ] required swap detected)
or Informational (90% of
required swap detected)

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 159
Acronyms and Abbreviations

API Application Programming Interface

AS Application Server
BCCT BroadWorks Common Communication Transport
BW BroadWorks
CDR Call Detail Record
CLI Command Line Interface
CNAM Caller ID with NAMe
CPU Central Processing Unit
DB Database
DBS Database Server
DN Directory Number
DNS Domain Name System
DSN Database Store Name
DTD Document Type Definition
FQDN Fully Qualified Domain Name
FTP File Transfer Protocol
HTTP Hypertext Transfer Protocol
IMRN IP Multimedia Routing Number
IN International
IP Internet Protocol
LDAP Lightweight Directory Access Protocol
MAC Media Access Control
MB Megabyte
MIB Management Information Base
MIME Multipurpose Internet Mail Extensions
MS Media Server
MSC Mobile Switching Centre
MWI Message Waiting Indicator or Indication
NAPTR Naming Authority Pointer
NFM Network Function Manager
NMS Network Management System
NS Network Server
NTP Network Time Protocol
OCI Open Client Interface
OID Object Identifier
PBX Private Branch Exchange
PUI Public User Identity

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 160
SCC Service Centralization and Continuity
SCR Selective Call Rejection
SIP Session Initiation Protocol
SMDI Simplified Message Desk Interface
SMTP Simple Mail Transfer Protocol
SNMP Simple Network Management Protocol
SOAP Simple Object Access Protocol
TCP Transmission Control Protocol
UDP User Datagram Protocol
UID Unique Identifier
URI Uniform Resource Identifier
URL Uniform Resource Locator
XML eXtensible Markup Language
Xsi Xtended Services Interface

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 161
Index

A bwFileServerClusterUnreachable 64
bwFileServerNodeUnreachable 64
Access list 24 bwFileTransferReplicationFailure 20, 89
Agent configuration 24 bwFileTransferReplicationOffline 20, 90
Alarm Correlation 29 bwForcedExitDueToHungThread 66
Alarms 28 bwGaugeHighLimitThreshold 88
bwGaugeLowLimitThreshold 88
bwGeneralSoftwareError 48
B bwHazelcastClusterConnectivityUnavailable 17, 19, 20, 89
BroadworksConfigurationFault.mib 45 bwHeapMemoryUsageExceeded 85
BroadworksFault.mib 47 bwHttpWorkersBusyExceeded 116
BW-FileTransferFault.mib 89 bwJVMProcessOutOfMemory 20, 86
BW-LicenseControllerFault.mib 90 bwJVMProcessUnexpectedSoftwareConditionDetected 20,
BW-LicenseManagerFault.mib 94 86
BW-MDBManagementFault.mib 98 bwKeyManagerCriticalDataMismatch 83
BW-NetworkMonitoringFault.mib 101 bwLicenseAccntViolation 71
BW-NodeControllerFault.mib 105 bwLicenseAuthenticationFailure 71
BW-NodeLifecycleManagerFault.mib 108 bwLicenseControllerExecutorQueueLatencyExceeded 93
BW-SoftwareManagementFault.mib 111 bwLicenseControllerExecutorQueueUsageExceeded 93
BW-WebContainerFault.mib 115 bwLicenseControllerExecutorThreadPoolBusyExceeded 94
bwAclViolation 62 bwLicenseControllerExecutorThreadPoolProcessingTimeExceeded
bwAlarmsDiscarded 48 94
bwAlarmsTableLimitReached 80 bwLicenseControllerNodeLicenseUpdateFailure 93
bwApplicationServerProvUnreachable 11, 11, 19, 20 bwLicenseControllerNodeUsingUnauthorizedLicense 92
bwApplicationServerUnreachable 19 bwLicenseControllerNodeUsingUndeployedLicenseInstance
bwApplicationStateTransition 49 93
bwAuditAbnormalCallTermination 65 bwLicenseFileExpired 71
bwCallOverloadZoneTransition 67 bwLicenseFileExpiring 70
bwCallPThreadAutoRestart 65 bwLicenseFileNotFound 70
bwCentralizedDatabaseConnectivityFailure 56 bwLicenseHWViolation 71
bwCentralizedDatabaseListenerFailure 20, 58 bwLicenseMonitoringFault 70
bwCentralizedDatabaseMaxConnectionsReached 20, 58 bwLicensingLMCommunicationLoss 96
bwCentralizedDatabaseNewConnectionFailure 20, 58 bwLicensingLMCommunicationLossGrace 97
bwCentralizedDatabasePoolFailure 15, 58 bwLicensingNFMCommunicationLoss 96
bwCentralizedDatabaseSchemaFailure 56 bwLicensingNFMCommunicationLossGrace 97
bwChangeDatabaseUserPasswordError 84 bwLicensingOverAllocation 97
bwCommProtocolHostNotAllowed 77 bwLicensingViolation 96
bwCommProtocolInitError 76 bwLicensingViolationGrace 97
bwCommProtocolInterfaceNotAllowed 77 bwLogQueueSizeLimitReached 79
bwConfigReplicationFailed 47 bwMaintenanceTaskFailure 55
bwConfigReplicationOffline 47 bwMariaDBNonPrimaryClusterNode 16, 19, 20, 100
bwConfigurationChanged 46 bwMaximumFailedLoginAttempts 82
bwConfigurationFailed 47 bwMaximumFailedUserLoginAttempts 83
bwCongestionManagementNeighborOverloaded 67 bwMemoryAllocationExceeded 82
bwCongestionManagementNeighborsInhibited 65 bwMemoryLimitReached 52
bwCouchbaseNodeConnectivityFailure 20, 57 bwMemoryOverAllocation 82
bwCounterThreshold 87 bwNetworkDatabaseClusterConnectivityFailure 20, 57
bwCPEDeviceConfigurationDeviceReset 49 bwNetworkDatabaseNodeConnectivityFailure 20, 56
bwCPEDeviceProfileLockout 74 bwNetworkDatabaseSchemaFailure 20, 57
bwCPUIdleTimeLimitReached 52 bwNetworkDeviceIsFailed 75
bwDatabaseSyncReport 51 bwNMControllerInventoryOutOfSynch 20, 104
bwDnsAllServersUnreachable 79 bwNMReplicationPrimaryFailure 20, 104
bwDnsServerUnreachable 79 bwNMReplicationStandbyFailure 20, 105
bwDnsTimeout 79 bwNodeControllerExecutorQueueLatencyExceeded 108
bwExecutorQueueLatencyExceeded 84 bwNodeControllerExecutorQueueUsageExceeded 107
bwExecutorQueueUsageExceeded 84 bwNodeControllerExecutorThreadPoolBusyExceeded 108
bwExecutorThreadPoolBusyExceeded 85 bwNodeControllerExecutorThreadPoolProcessingTimeExceeded
bwExecutorThreadPoolProcessingTimeExceeded 85 108
bwExtremeOverload 20, 49 bwNodeControllerOperationFailure 107

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 162
bwNonCallOverloadZoneTransition 67 bwPMremotexlaShutDown 53
bwNonheapMemoryUsageExceeded 22, 86 bwPMReportingFTPConnectionError 72
bwNSLocationConnectivityFailure 68 bwPMSoftwareControllerDeath 21, 113
bwNSLocationFailure 69 bwPMSoftwareControllerLaunched 21, 112
bwNSSynchronizationConnectivityFailure 68 bwPMSoftwareControllerOutOfMemory 21, 113
bwNSSyncSuccessDbCommitFailed 20, 69 bwPMSoftwareControllerRestarted 21, 112
bwOCICServerUnreachable 11, 81 bwPMSoftwareControllerShutDown 21, 112
bwOCIPServerUnreachable 11, 80 bwPMtomcatDeath 51
bwOciReportingAclViolation 76 bwPMtomcatLaunched 50
bwOciReportingBackLogFileDeleted 76 bwPMtomcatRestarted 50
bwOciReportingConnectionError 76 bwPMtomcatShutDown 50
bwOSMisconfiguration 12, 55 bwPMunicornDeath 21, 111
bwOverAllocationViolationGrace 98 bwPMunicornLaunched 21, 110
bwPhysicalLocationOriginationBlocked 66 bwPMunicornRestarted 21, 111
bwPMconfigdDeath 46 bwPMunicornShutDown 21, 110
bwPMconfigdLaunched 45 bwProtocolRegistrationFailure 12, 19, 20, 80
bwPMconfigdOutOfMemory 17 bwPushNotificationServerUnreachable 20, 88
bwPMconfigdRestarted 46 bwSCFAPIURLUnreachable 81
bwPMconfigdShutDown 45 bwSecureTlktToolResult 83
bwPMFileReplicationDeath 20, 104 bwSecurityRiskDetected 83
bwPMFileReplicationLaunched 20, 103 bwServerStateTransition 48
bwPMFileReplicationRestarted 20, 103 bwSipMaxRetriesExceeded 61
bwPMFileReplicationShutDown 21, 103 bwSipMessageParsingError 60
bwPMhttpdDeath 54 bwSipRegistrationFailure 60
bwPMhttpdLaunched 54 bwSipRequestTimeOutReceived 61
bwPMhttpdRestarted 54 bwSipServerTimeOutReceived 62
bwPMhttpdShutDown 54 bwSipServiceUnavailableReceived 62
bwPMLicenseControllerDeath 91 bwSipSocketAlreadyBound 60
bwPMLicenseControllerLaunched 90 bwSipTcpConnectionFailure 63
bwPMLicenseControllerOutOfMemory 92 bwSipTcpExceededMax 59
bwPMLicenseControllerRestarted 91 bwSipTcpExceededMaxPerPeer 59
bwPMLicenseControllerShutDown 91 bwSipTcpSocketError 59
bwPMlmdDeath 95 bwSipUnexpectedMessage 60
bwPMlmdLaunched 95 bwSipUnrecognisedDomainName 63
bwPMlmdOutOfMemory 17 bwSMAPConnectionFailure 69
bwPMlmdRestarted 95 bwSMDIConfigurationError 73
bwPMlmdShutDown 95 bwSMDIInterfaceError 73
bwPMMariaDBDeath 20, 99 bwSMDIOperationFailure 73
bwPMMariaDBLaunched 20, 98 bwSMDIRouteExhaustion 74
bwPMMariaDBRestarted 20, 99 bwSMDIsessionRejected 72
bwPMMariaDBShutDown 20, 99 bwSMTPConnectivityFailure 64
bwPMmdbMonitorDeath 20, 100 bwSMTPPrimaryServerEmailMessageDeliveryError 63
bwPMmdbMonitorLaunched 20, 99 bwSoftwareManagementAdditionalPatchMissing 21, 115
bwPMmdbMonitorRestarted 20, 100 bwSoftwareManagementDistributionCenterConnectivityFailure
bwPMmdbMonitorShutDown 20, 100 21, 114
bwPMNetworkMonitoringDeath 21, 102 bwSoftwareManagementExecutorQueueLatencyExceeded
bwPMNetworkMonitoringLaunched 21, 101 21
bwPMNetworkMonitoringOutOfMemory 21, 102 bwSoftwareManagementExecutorQueueUsageExceeded
bwPMNetworkMonitoringRestarted 21, 102 21
bwPMNetworkMonitoringShutDown 21, 101 bwSoftwareManagementExecutorThreadPoolBusyExceeded
bwPMnginxDeath 21, 110 21
bwPMnginxLaunched 21, 109 bwSoftwareManagementExecutorThreadPoolProcessingTimeExceeded
bwPMnginxRestarted 21, 109 21
bwPMnginxShutDown 21, 109 bwSoftwareManagementInvalidSignature 21
bwPMNodeControllerDeath 106 bwSoftwareManagementNewCriticalPatchReleased 22, 114
bwPMNodeControllerLaunched 105 bwSoftwareManagementNewDeprecatedPatch 22, 114
bwPMNodeControllerOutOfMemory 106 bwSoftwareManagementReReleasedPatch 22, 114
bwPMNodeControllerRestarted 106 bwSoftwareManagementSWManagerInstallationFailure 22,
bwPMNodeControllerShutDown 105 115
bwPMremotexlaDeath 53 bwSslClientAuthWithoutTrust 118
bwPMremotexlaLaunched 52 bwSystemBackwardTimeDrift 55
bwPMremotexlaRestarted 53 bwSystemHealthReport 51

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 163
bwTaskMonitorHungTask 78 N
bwTaskMonitorWarning 78
bwTcpSubsystemFatalError 78 Notifications 28
bwThreadDelayDetected 66
bwTimeSkewExceeded 20, 87
bwWebApplicationCacheDiskFull 116
O
bwWebContainerAuthenticationServerUnreachable 117 OID
bwWebContainerServerTransactionLimitExceeded 117 Shared 25
bwWebContainerTransactionGlobalRateLimitExceeded 116 Unique 25
bwWebContainerTransactionUserRateLimitExceeded 116
bwWebContainerUserTransactionLimitExceeded 117
bwWebContainerWebAppTransactionLimitExceeded 117 P
Provisioning filters 42
C
Configuration 24 R
Reporting 27
E
External subagents S
Integration 37, 37
SNMP
Access list 24
F Agent 24, 24
Agent configuration 25
Fault Security model 27
Alarms 28, 29 Trap manager 25
Definitions 28 v2c 24, 25
Fault IDs 44 v3 users 27
Filters 42
MIB files 44
Notification 42 T
Notifications 28
Template 28
Suppression 38
Threshold filtering 39, 41, 42
Template 28
Trap
Thresholding
Lists 38
Filtering considerations 41
Manager 25
Trap filters 39
Trap lists 38

I
Integration 37
Introduction 23

M
MIB
BroadworksConfigurationFault.mib 45
BroadworksFault.mib 47
BW-FileTransferFault.mib 89
BW-LicenseControllerFault.mib 90
BW-LicenseManagerFault.mib 94
BW-MDBManagementFault.mib 98
BW-NetworkMonitoringFault.mib 101
BW-NodeControllerFault.mib 105
BW-NodeLifecycleManagerFault.mib 108
BW-SoftwareManagementFault.mib 111
BW-WebContainerFault.mib 115
Files 44
MIBs 45

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 164
References

[1] Cisco Systems, Inc. 2020. Cisco BroadWorks Network Function Manager Performance
Measurement Interface Specification.
Available from Cisco at https://xchange.broadsoft.com.

References to Feature Description Documents

[FR 18485] Cisco Systems, Inc. 2020. Hazelcast Connectivity Alarm Feature Description, Release 24.0.
Available from Cisco at https://xchange.broadsoft.com.
[FR 217550] Cisco Systems, Inc. 2020. Node License Management Feature Description, Release 21.0.
Available from Cisco at https://xchange.broadsoft.com/node/475423.
[FR 2214] Cisco Systems, Inc. 2017. Downloadable Software Signing Feature Description, Release 22.0.
Available from Cisco at https://xchange.broadsoft.com/node/490790.
[FR 2299] Cisco Systems, Inc. 2017. Network Database Server Feature Description, Release 22.0.
Available from Cisco at https://xchange.broadsoft.com/node/481987.
[FR 2300] Cisco Systems, Inc. 2017. Generic Database Change Notification Feature Description, Release
22.0.
Available from Cisco at https://xchange.broadsoft.com/node/490553.
[FR 6517] Cisco Systems, Inc. 2017. Java Heap Monitoring Feature Description, Release 22.0.
Available from Cisco at https://xchange.broadsoft.com/node/490523.
[FR 6984] Cisco Systems, Inc. 2020. NFM Open NMS-SNMP Enhancements Feature Description, Release
22.0.
Available from Cisco at https://xchange.broadsoft.com.
[FR 7266] Cisco Systems, Inc. 2018. NFM Patch Management, Release 22.0.
Available from Cisco at https://xchange.broadsoft.com/node/1031014.
[FR 10066] Cisco Systems, Inc. 2017. Enhanced Call Log DB Switch from Database Server Feature
Description, Release 22.0.
Available from Cisco at https://xchange.broadsoft.com/node/491649.

CISCO BROADWORKS NETWORK FUNCTION MANAGER FAULT AND ALARM INTERFACE SPECIFICATION 05-BD6101-00
©2020 CISCO SYSTEMS, INC. PAGE 165