System Release 2.

9
MOTOTRBO™ CAPACITY MAX

System Advisor

APRIL 2018
*MN002730A01*
© 2018 Motorola Solutions, Inc. All rights reserved MN002730A01-AD
MN002730A01-AD
Copyrights

Copyrights
The Motorola Solutions products described in this document may include copyrighted Motorola
Solutions computer programs. Laws in the United States and other countries preserve for Motorola
Solutions certain exclusive rights for copyrighted computer programs. Accordingly, any copyrighted
Motorola Solutions computer programs contained in the Motorola Solutions products described in this
document may not be copied or reproduced in any manner without the express written permission of
Motorola Solutions.
© 2018 Motorola Solutions, Inc. All Rights Reserved
No part of this document may be reproduced, transmitted, stored in a retrieval system, or translated
into any language or computer language, in any form or by any means, without the prior written
permission of Motorola Solutions, Inc.
Furthermore, the purchase of Motorola Solutions products shall not be deemed to grant either directly
or by implication, estoppel or otherwise, any license under the copyrights, patents or patent
applications of Motorola Solutions, except for the normal non-exclusive, royalty-free license to use that
arises by operation of law in the sale of a product.

Disclaimer
Please note that certain features, facilities, and capabilities described in this document may not be
applicable to or licensed for use on a specific system, or may be dependent upon the characteristics of
a specific subscriber unit or configuration of certain parameters. Please refer to your Motorola
Solutions contact for further information.

Trademarks
MOTOROLA, MOTO, MOTOROLA SOLUTIONS, and the Stylized M Logo are trademarks or
registered trademarks of Motorola Trademark Holdings, LLC and are used under license. All other
trademarks are the property of their respective owners.

European Union (EU) Waste of Electrical and Electronic Equipment (WEEE)

directive

The European Union's WEEE directive requires that products sold into EU countries must have
the crossed out trash bin label on the product (or the package in some cases).
As defined by the WEEE directive, this cross-out trash bin label means that customers and end-users
in EU countries should not dispose of electronic and electrical equipment or accessories in household
waste.
Customers or end-users in EU countries should contact their local equipment supplier representative or
service centre for information about the waste collection system in their country.

2
 MN002730A01-AD
Contact Us

Contact Us
Motorola Solutions Support Center
The Solutions Support Center (SSC) is the primary contact for technical support included in your
organization's service agreement with Motorola Solutions.
Service agreement customers should be sure to call the SSC in all situations listed under Customer
Responsibilities in their agreement, such as:
• Before reloading software.
• To confirm troubleshooting results and analysis before taking action.
Your organization received support phone numbers and other contact information appropriate for your
geographic region and service agreement. Use that contact information for the most efficient response.
However, if needed, you can also find general support contact information on the Motorola Solutions
website, by following these steps:
• Enter motorolasolutions.com in your browser
• Ensure that your organization's country or region is displayed on the page. Clicking or tapping the
name of the region provides a way to change it.
• Select "Support" on the motorolasolutions.com page.

Comments
Send questions and comments regarding user documentation to
documentation@motorolasolutions.com.
Provide the following information when reporting a documentation error:
• The document title and part number
• The page number with the error
• A description of the error

3
MN002730A01-AD
Document History

Document History
Version Description Date
MN002730A01-AA Original release of the Capacity Max System Advisor March 2016
manual.
MN002730A01-AB Second release of the Capacity Max System Advisor November 2016
manual. This update includes the following changes:
• Support of 250 RF sites: site objects displayed in
groups in the System and Grid View
• System Advisor redundancy:
- Selection of the active or inactive System Advi-
sor instance on the launch page
- System Advisor activity states displayed in the
System, Grid, and Raw View
• New Grid View icons:
- Site wide call
- System wide call
- System all call
For the updated information, see the following sec-
tions:
• - System Advisor Main Functions on page 27
- System Advisor Redundancy on page 30
- Starting the SA Client on page 69
- Call Monitoring – Grid View on page 89
- Grid View Icons on page 91
- Call Monitoring – Raw View on page 94

MN002730A01-AC Third release of the Capacity Max System Advisor June 2017
manual. This update includes the following changes:
• Addition of the Managed Resources in System
View section.
• Addition of the Grid View Icon:
- Confirmed Group Data Call
• Addition of Alarms and Events in Appendix E.

MN002730A01-AD Fourth release of the Capacity Max System Advisor April 2018
manual. This update includes the following changes:
• Replacement of the System View screenshot
• Policies Description - Audit Trails Cleanup Policy
• Repeaters - Main Repeater Channel Role
• Related Information

4
 MN002730A01-AD
Contents

Contents
Copyrights................................................................................................................... 2
Contact Us................................................................................................................... 3
Document History....................................................................................................... 4
List of Figures............................................................................................................14
List of Tables............................................................................................................. 16
List of Procedures.....................................................................................................17
About the Capacity Max System Advisor............................................................... 21
What is Covered in This Guide?.................................................................................................. 21
Helpful Background Information.................................................................................................. 21
Related Information..................................................................................................................... 21
Chapter 1: SA Description........................................................................................23
1.1 IP-Managed Devices............................................................................................................. 23
1.2 Protocols Supported by SA....................................................................................................23
1.3 Agents....................................................................................................................................24
1.4 Redundancy Management.....................................................................................................25
1.5 Synchronization..................................................................................................................... 25
1.6 Supervision............................................................................................................................ 25
1.7 North Bound Interface............................................................................................................25
1.8 System Advisor Overview......................................................................................................26
1.8.1 System Advisor Main Functions...............................................................................27
1.8.2 System Advisor Redundancy...................................................................................30
1.9 SA Client Overview................................................................................................................30
1.10 Navigation Tree................................................................................................................... 31
1.11 Fault Management Overview...............................................................................................31
1.11.1 Severity Definitions................................................................................................ 32
1.11.2 Event Category Definitions.................................................................................... 32
1.11.3 Unknown Events.................................................................................................... 33
1.11.4 Command Window.................................................................................................33
1.11.5 Alarms Window...................................................................................................... 34
1.11.6 Alarms Summary................................................................................................... 34
1.11.7 Network Events Window........................................................................................ 35
1.11.8 Network Database................................................................................................. 35
1.12 Performance Management Overview.................................................................................. 36
1.13 Discovery Overview............................................................................................................. 36
1.13.1 Devices Discovered by SA.....................................................................................37

5
MN002730A01-AD
Contents

1.13.2 Post-Discovery Synchronization............................................................................ 37

1.14 Events Archive.....................................................................................................................37
Chapter 2: SA Configuration....................................................................................40
2.1 Application Configuration.......................................................................................................40
2.1.1 Configuring System Advisor Properties................................................................... 40
2.1.2 Language and Date Format..................................................................................... 41
2.1.2.1 Changing System Advisor Language Preference...................................... 42
2.1.2.2 Changing System Advisor Date Format.....................................................42
2.1.3 User Preferences Configuration...............................................................................43
2.1.3.1 Setting the Initial View................................................................................43
2.1.3.2 Enabling or Disabling the Login Info Window at the Start-Up.................... 43
2.1.4 Restarting System Advisor.......................................................................................44
2.1.5 Network Database Configuration............................................................................. 45
2.1.5.1 Changing Managed Resource Display Names in Managed Resource
Properties Window............................................................................................ 45
2.1.5.2 Changing Managed Resource Display Name in System View.................. 45
2.1.5.3 Setting Default Names for Managed Resources........................................46
2.1.5.4 Changing Subsystem Names.....................................................................46
2.1.6 Alarm Filters Configuration...................................................................................... 47
2.1.6.1 Adding Alarm Filters...................................................................................48
2.1.6.2 Configuring E-mail Notifications for Alarm Filters.......................................49
2.1.6.3 Modifying Alarm Filters...............................................................................52
2.1.6.4 Alarms Filter by Managed Resource Device Category.............................. 53
2.1.6.5 Modifying Alarm Filter Notifications............................................................53
2.1.6.6 Loading Alarm Filter Files.......................................................................... 53
2.1.6.7 Deleting Alarm Filters.................................................................................54
2.1.6.8 Deleting Alarm Filter Notifications.............................................................. 54
2.1.7 Event Filters Configuration.......................................................................................54
2.1.7.1 Adding Event Filters................................................................................... 55
2.1.7.2 Configuring E-mail Notifications for Event Filters.......................................56
2.1.7.3 Modifying Event Filters...............................................................................59
2.1.7.4 Modifying Event Filter Notifications............................................................ 60
2.1.7.5 Loading Event Filter Files...........................................................................60
2.1.7.6 Deleting Event Filters................................................................................. 60
2.1.7.7 Deleting Event Filter Notifications.............................................................. 61
2.2 Account Management............................................................................................................61
2.3 Inbound and Outbound Communication Credentials Configuration...................................... 62
2.3.1 SNMPv3 Credentials Configuration......................................................................... 62
2.3.1.1 Updating Global SNMPv3 Credentials for the MotoMaster User............... 63

6
 MN002730A01-AD
Contents

2.3.1.2 Updating Global SNMPv3 Inform Credentials............................................64

2.3.1.3 Updating the Network Element SNMPv3 Credentials................................ 64
2.3.1.4 Testing any Device SNMPv3 Configuration............................................... 65
2.3.1.5 Testing SNMPv3 Communication Between Network Elements and SA.... 65
2.3.2 Web Service Credentials Configuration................................................................... 65
2.3.2.1 Changing Global Web Service Credentials for the MotoMaster User........ 66
2.3.2.2 Updating Network Element Web Service Credentials................................66
2.3.2.3 Testing any Device Web Service Configuration.........................................66
2.3.2.4 Testing the Web Service Communication Between Network Elements
and SA.............................................................................................................. 66
2.3.3 Configuring North Bound Interface.......................................................................... 67
2.4 Discovery Job Credentials Configuration...............................................................................67
2.4.1 Configuring Discovery Job Credentials....................................................................67
2.4.2 Disabling Discovery Job Credentials....................................................................... 68
Chapter 3: SA Operation...........................................................................................69
3.1 Starting the SA Client............................................................................................................ 69
3.2 Work Area Overview..............................................................................................................70
3.2.1 Work Area Operations............................................................................................. 70
3.2.1.1 Navigating Through Active Windows......................................................... 70
3.2.1.2 Detaching a Window from the Client..........................................................70
3.2.1.3 Arranging Windows.................................................................................... 70
3.2.2 Work Area Components...........................................................................................70
3.2.3 Broadcasting Messages...........................................................................................71
3.2.4 Table View Operations.............................................................................................72
3.2.4.1 Table Navigation........................................................................................ 72
3.2.4.2 Setting the Page Length.............................................................................72
3.2.4.3 Sorting Table Details..................................................................................72
3.2.4.4 Rearranging and Resizing Table Columns................................................ 73
3.2.5 Custom View Operations......................................................................................... 73
3.2.5.1 Adding Custom Views................................................................................ 74
3.2.5.2 Modifying Custom Views............................................................................74
3.2.5.3 Renaming Custom Views...........................................................................75
3.2.5.4 Moving Custom Views................................................................................75
3.2.5.5 Saving Custom Views................................................................................ 76
3.2.5.6 Deleting Custom Views.............................................................................. 77
3.2.5.7 Exporting Custom Views............................................................................ 77
3.2.5.8 Importing Custom Views............................................................................ 77
3.2.6 Filtering Quick Reference........................................................................................ 78
3.2.6.1 Wildcard Characters for Filtering................................................................78

7
MN002730A01-AD
Contents

3.2.6.2 Examples of Filtering with Wildcard Characters.........................................79

3.3 Active Users Operations........................................................................................................ 79
3.3.1 Viewing the Active SA Clients List........................................................................... 80
3.4 Site Operations...................................................................................................................... 80
3.4.1 Deleting Sites...........................................................................................................81
3.4.2 Deletion Status.........................................................................................................81
3.5 Administration Tools.............................................................................................................. 82
3.5.1 Policies Overview.....................................................................................................82
3.5.1.1 Policies Description....................................................................................82
3.5.1.2 Viewing Policy Details................................................................................ 85
3.5.1.3 Default Policy Parameters..........................................................................86
3.5.2 Viewing Job Status.................................................................................................. 86
3.6 System View.......................................................................................................................... 87
3.7 Call Monitoring Operations.................................................................................................... 89
3.7.1 Call Monitoring – Grid View..................................................................................... 89
3.7.1.1 Viewing Grid Views.................................................................................... 91
3.7.1.2 Grid View Icons.......................................................................................... 91
3.7.2 Call Monitoring – Raw View..................................................................................... 94
3.7.2.1 Viewing Raw Views....................................................................................95
3.8 Fault Management Operations.............................................................................................. 95
3.8.1 Displaying Alarm Details from the Network Database Window............................... 95
3.8.2 Displaying Event Details from the Network Database Window................................95
3.8.3 Managed Resource Properties................................................................................ 96
3.9 Network Events Operations................................................................................................... 97
3.9.1 Event Properties...................................................................................................... 97
3.9.2 Viewing Event Details.............................................................................................. 99
3.9.3 Exporting Events....................................................................................................100
3.9.4 Searching Events...................................................................................................101
3.10 Alarm Operations...............................................................................................................102
3.10.1 Alarm Summary View Operations........................................................................103
3.10.1.1 Displaying Alarm Details from the Tabular View Chart.......................... 103
3.10.1.2 Displaying Alarm Details from the Severity Alone Pie Chart..................104
3.10.1.3 Displaying Alarm Details from the Severity and Category Chart............105
3.10.2 Alarms Window Operations................................................................................. 106
3.10.2.1 Viewing Alarm Details............................................................................ 106
3.10.2.2 Searching Alarms...................................................................................107
3.10.2.3 Viewing Related Events......................................................................... 107
3.10.2.4 Viewing Alarm History and Annotations................................................. 107
3.10.2.5 Deleting Alarms......................................................................................107

8
 MN002730A01-AD
Contents

3.10.3 Adding Annotations to Alarms..............................................................................108

3.10.4 Launching the Alarms View from the Network Database View............................108
3.10.5 Exporting Alarms..................................................................................................108
3.10.6 Displaying Alarms Summary................................................................................109
3.10.7 Alarm Properties.................................................................................................. 109
3.10.8 Audio Notifications for Alarms..............................................................................111
3.10.8.1 Assigning Audio Notifications to Alarms.................................................111
3.10.9 Launching the Alarms View from Custom Alarm Panel....................................... 112
3.10.10 Alarms Ownership..............................................................................................113
3.10.10.1 Assigning Ownership to Alarms from the Alarms Details Window....... 113
3.10.10.2 Assigning or Unassigning Ownership to Alarms from the Main Menu. 113
3.11 Device Management Operations....................................................................................... 114
3.11.1 Managing Resources........................................................................................... 114
3.11.2 Unmanaging Resources...................................................................................... 114
3.11.3 Deleting Network Elements..................................................................................115
3.11.4 Device Commands...............................................................................................116
3.11.4.1 Issuing Commands from the Alarms Window........................................ 116
3.11.4.2 Issuing Commands from the Network Database Window......................117
3.12 Synchronization Operations...............................................................................................117
3.12.1 Synchronizing Managed Resources.................................................................... 117
3.13 Discovery Operations........................................................................................................ 118
3.13.1 Discovering Network Elements............................................................................ 118
3.13.2 Aborting Discovery Jobs...................................................................................... 119
3.13.3 Discovery Status.................................................................................................. 120
3.14 Performance Management Operations..............................................................................121
3.14.1 Viewing Configured Collections for a Device....................................................... 121
3.14.2 Statistic Properties............................................................................................... 121
3.14.3 Data Collection Detailed Properties..................................................................... 122
3.14.4 Statistics Operations............................................................................................ 124
3.14.4.1 Adding Statistics.....................................................................................124
3.14.4.2 Modifying Statistics................................................................................ 124
3.14.4.3 Removing Statistics................................................................................125
3.14.5 Enabling Collections............................................................................................ 125
3.14.6 Disabling Collections............................................................................................125
3.14.7 Searching Configured Collections........................................................................126
3.14.8 Plotting Collected Statistics..................................................................................126
3.14.9 Plotting Current Statistics.....................................................................................127
3.14.10 Zooming in on Plotted Graphs........................................................................... 128
3.14.11 Zooming out on Plotted Graphs......................................................................... 128

9
MN002730A01-AD
Contents

3.14.12 Viewing Performance Status of Managed Resources....................................... 129

3.15 Network Database Operations...........................................................................................129
3.15.1 Viewing Managed Resource Properties...............................................................129
3.15.2 Determining Reliable Communication Capability of a Managed Resource......... 130
3.15.3 Exporting Network Inventory Data....................................................................... 130
3.16 Associated Managed Resources Operations.................................................................... 130
3.16.1 Viewing Associated Managed Resources from the Alarms Window................... 131
3.16.2 Viewing Associated Managed Resources from the Network Database Window. 131
3.17 Unknown Devices.............................................................................................................. 131
3.18 Security Management Operations..................................................................................... 131
3.18.1 Audit Trails Operations........................................................................................ 132
3.18.1.1 Viewing Audit Trails for All Users........................................................... 132
3.18.1.2 Viewing Audit Trails on the SA Client Web Interface............................. 133
3.18.1.3 Viewing Audit Trails for Single Users..................................................... 133
3.18.1.4 Searching Audit Trails............................................................................ 133
3.18.1.5 Exporting Audit Trails............................................................................. 134
3.18.2 Groups Operations...............................................................................................134
3.18.2.1 Adding Groups....................................................................................... 135
3.18.2.2 Assigning Users to Groups.................................................................... 136
3.18.2.3 Unassigning Users from Groups............................................................ 137
3.18.2.4 Deleting Groups..................................................................................... 137
3.18.3 Users Management..............................................................................................137
3.18.3.1 Users Operations................................................................................... 137
3.18.3.2 Changing the User Profile...................................................................... 139
3.18.3.3 Unlocking the User Account...................................................................139
3.18.3.4 Assigning Groups to Users.................................................................... 140
3.18.3.5 Changing the User Password when in the Security Administrator
Group.............................................................................................................. 140
3.18.3.6 Deleting Users........................................................................................140
3.18.4 Operations Management..................................................................................... 141
3.18.4.1 Default Operations................................................................................. 141
3.18.4.2 Operations Assignment..........................................................................147
Chapter 4: SA Maintenance....................................................................................149
4.1 System Advisor Backup and Restore.................................................................................. 149
4.1.1 Logging On to the ESU Client................................................................................150
4.1.2 Backing Up the System Advisor Data on Demand................................................ 150
4.1.3 Scheduling the System Advisor Data Backup........................................................150
4.1.4 Restoring the System Advisor Data....................................................................... 151
4.1.5 Uploading a Backup to ESU.................................................................................. 151

10
 MN002730A01-AD
Contents

4.1.6 SNMPv3 Synchronization...................................................................................... 151

4.2 Retrieving System Advisor Archives and Logs.................................................................... 152
4.3 Trap Overload Overview......................................................................................................152
4.3.1 Cleaning the Trap Buffer Manually........................................................................ 155
4.3.2 Configuring Automatic Cleanup of the Trap Buffer................................................ 155
4.3.3 Managing and Unmanaging Managed Resources From the Trap Buffer.............. 156
4.4 Viewing Archived Events in SA............................................................................................156
Chapter 5: SA Troubleshooting............................................................................. 158
5.1 Client Server Connection is Lost......................................................................................... 158
5.2 Login Errors......................................................................................................................... 158
5.3 Configuring Server Logging................................................................................................. 158
5.4 Configuring Client Logging.................................................................................................. 159
5.5 Command Operation Succeeds but Device Reports a Failure............................................ 160
5.6 Hardware Troubleshooting with SA..................................................................................... 160
5.6.1 Hardware Troubleshooting in Network Database.................................................. 160
5.7 Sluggish Performance Monitoring........................................................................................161
5.8 Performance Management Troubleshooting....................................................................... 161
5.9 Removing Alarms for Deleted Entities................................................................................. 161
5.10 SNMPv3 Communication for MotoMaster Tests................................................................162
5.10.1 Testing the Outbound Communication from SA to any Device............................162
5.10.2 Testing the Outbound Communication from SA to a Discovered Device............ 162
5.10.3 SNMPv3 Inbound Communication Tests............................................................. 163
5.10.4 SNMP Communication Alarms and Events......................................................... 163
Appendix A: Basic Configuration.......................................................................... 165
Appendix B: Configuration Input...........................................................................166
Appendix C: Test E-mail Content.......................................................................... 167
Appendix D: Mail Server Compatibility................................................................. 168
Appendix E: Alarms and events............................................................................ 169
E.1 Manager Generated Events................................................................................................ 169
E.2 MIB-2 Events.......................................................................................................................180
E.3 General RFC Events........................................................................................................... 181
E.4 CM Bridge Alarms and Events Overview............................................................................ 187
E.4.1 CM Bridge Alarms................................................................................................. 187
E.4.2 CM Bridge Events..................................................................................................188
E.5 CMSS Alarms and Events Overview...................................................................................189
E.5.1 CMSS Generic Events...........................................................................................189
E.5.2 CMSS Alarms and Events..................................................................................... 223
E.5.2.1 Processors...............................................................................................223

11
MN002730A01-AD
Contents

E.5.2.2 Power.......................................................................................................223
E.5.2.3 Fan...........................................................................................................224
E.5.2.4 Temperature............................................................................................ 224
E.5.2.5 Storage.................................................................................................... 224
E.5.2.6 Port.......................................................................................................... 224
E.5.2.7 Configuration Issues................................................................................ 225
E.5.2.8 Storage Path............................................................................................225
E.5.2.9 Storage Paths.......................................................................................... 225
E.5.2.10 Virtual machine...................................................................................... 226
E.6 MNIS Alarms and Events Overview.................................................................................... 226
E.6.1 MNIS Alarms......................................................................................................... 226
E.6.2 MNIS Events..........................................................................................................226
E.7 Generic SNMP Node Alarms and Events Overview............................................................227
E.8 Generic SNMP Router Alarms and Events Overview......................................................... 227
E.8.1 Generic SNMP Router Alarms...............................................................................227
E.9 Generic SNMP Switch Alarms and Events Overview..........................................................228
E.9.1 Generic SNMP Switch Alarms...............................................................................228
E.10 HP Switch Alarms and Events Overview...........................................................................228
E.10.1 HP Switch Main Traps......................................................................................... 228
E.10.2 HP Switch Generic Events.................................................................................. 229
E.10.2.1 hpicfFaultFinderTrap..............................................................................229
E.10.2.2 hpicfSensorTrap.................................................................................... 231
E.10.2.3 hpicfSelfTestTrap...................................................................................232
E.10.2.4 hpicfBridgeLoopProtectLoopDetectedNotification................................. 232
E.10.2.5 hpicfConnectionRateFilterNotification....................................................233
E.10.2.6 hpicfIntrusionTrap.................................................................................. 233
E.10.3 HP Switch Alarms................................................................................................234
E.10.4 HP Switch Events................................................................................................ 234
E.10.5 HP Switch Trap Rules......................................................................................... 251
E.11 System Advisor Alarms and Events Overview.................................................................. 261
E.11.1 System Advisor Alarms and Events.................................................................... 261
E.11.1.1 Activity State Events.............................................................................. 261
E.11.1.2 Application............................................................................................. 262
E.11.1.3 DSR Synchronization Object................................................................. 267
E.11.1.4 Broker Server Link................................................................................. 268
E.11.1.5 CM Capacity.......................................................................................... 268
E.11.1.6 Ethernet Card........................................................................................ 269
E.11.1.7 Fan.........................................................................................................271
E.11.1.8 Hard Disk............................................................................................... 272

12
 MN002730A01-AD
Contents

E.11.1.9 Power Supply.........................................................................................273

E.11.2 Application Service Alarms and Events...............................................................274
E.11.2.1 Application Service................................................................................ 274
E.11.2.2 Database Service.................................................................................. 275
E.11.2.3 JVM Service...........................................................................................275
E.11.2.4 Processing Queue................................................................................. 276
E.11.2.5 NCM Service..........................................................................................276
E.11.2.6 Call Monitoring Service..........................................................................277
E.11.2.7 Config Service....................................................................................... 277
E.12 Repeater Alarms and Events Overview............................................................................ 277
E.12.1 Repeater Alarms..................................................................................................278
E.12.2 Repeater Events..................................................................................................285
E.13 Replicator Alarms and Events Overview........................................................................... 286
E.13.1 Replicator Alarms................................................................................................ 286
E.13.2 Replicator Events................................................................................................ 286
E.14 Trunk Controller Alarms and Events Overview................................................................. 286
E.14.1 Trunk Controller Alarms.......................................................................................286
E.14.2 Trunk Controller Events.......................................................................................287

13
MN002730A01-AD
List of Figures

List of Figures
Figure 1: System Advisor – Navigation Tree.......................................................................................... 31
Figure 2: System Advisor – Command Window..................................................................................... 34
Figure 3: Network Events Window......................................................................................................... 35
Figure 4: System Advisor – Network Database Window........................................................................ 36
Figure 5: SA File System – CSV Files List............................................................................................. 38
Figure 6: Events Archive – SA Client Web Interface.............................................................................. 38
Figure 7: Configure System Advisor Properties Window – General Properties Tab.............................. 40
Figure 8: Change Language and Date Format Window......................................................................... 42
Figure 9: User Preferences dialog box................................................................................................... 43
Figure 10: Restart Server Warning.........................................................................................................44
Figure 11: Server Connection Lost Warning Message...........................................................................44
Figure 12: Alert Filters Window.............................................................................................................. 48
Figure 13: Add Action Window – Email Tab........................................................................................... 50
Figure 14: SMTP Configuration Dialog Box............................................................................................51
Figure 15: Event Filters Window.............................................................................................................57
Figure 16: Add Action Window – Email Tab........................................................................................... 58
Figure 17: SMTP Configuration Dialog Box............................................................................................58
Figure 18: Update Credentials Dialog Box............................................................................................. 63
Figure 19: Launch Page......................................................................................................................... 69
Figure 20: Navigation View Panel – Custom View................................................................................. 76
Figure 21: System Administration – SA Client Web Interface................................................................ 80
Figure 22: Client Details – SA Client Web Interface...............................................................................80
Figure 23: Job Status View Window.......................................................................................................81
Figure 24: Policy Details Window........................................................................................................... 85
Figure 25: System View..........................................................................................................................87
Figure 26: Call Monitoring Grid View......................................................................................................90
Figure 27: Call Monitoring – Raw View.................................................................................................. 94
Figure 28: Event Details Window......................................................................................................... 100
Figure 29: Search Dialog Box...............................................................................................................101
Figure 30: Alarms Window................................................................................................................... 102
Figure 31: Alarm Details Window......................................................................................................... 103
Figure 32: Alarm Summary View – Tabular View.................................................................................104
Figure 33: Alarm Summary View – Severity Alone Pie Chart...............................................................105
Figure 34: Alarm Summary View – Graphical View Chart....................................................................106
Figure 35: Alarm Audio Notification Dialog Box....................................................................................112
Figure 36: Alarm Assign Dialog Box.....................................................................................................113

14
 MN002730A01-AD
List of Figures

Figure 37: Job Status View for Deletion Jobs Window.........................................................................115

Figure 38: Discovery Configuration window......................................................................................... 119
Figure 39: Group Adminstration Window..............................................................................................135
Figure 40: Groups Adminstration – Operations Tree Root................................................................... 136
Figure 41: Events Archive – SA Client Web Interface.......................................................................... 157

15
MN002730A01-AD
List of Tables

List of Tables
Table 1: Severity Categories.................................................................................................................. 32
Table 2: Event Category.........................................................................................................................32
Table 3: Filtering Site Trunking Condition Example............................................................................... 79
Table 4: Filtering Transient Illegal Carrier Events Example................................................................... 79
Table 5: Filtering Station alarms on Chosen Sites Example.................................................................. 79
Table 6: Policies Description.................................................................................................................. 82
Table 7: Managed Resource Properties.................................................................................................96
Table 8: Data Collection Detailed Properties........................................................................................122
Table 9: Security Administration...........................................................................................................141
Table 10: System Administration..........................................................................................................141
Table 11: Runtime Administration........................................................................................................ 142
Table 12: Shutdown Web NMS Server.................................................................................................142
Table 13: Terminate Client................................................................................................................... 142
Table 14: Events...................................................................................................................................142
Table 15: Topology...............................................................................................................................142
Table 16: Policy.................................................................................................................................... 143
Table 17: User Administration.............................................................................................................. 143
Table 18: Alerts.................................................................................................................................... 144
Table 19: NBI Configuration................................................................................................................. 145
Table 20: Credentials Configuration..................................................................................................... 145
Table 21: Device Command Configuration...........................................................................................145
Table 22: Device Synchronization........................................................................................................ 145
Table 23: Abort All Discovery Jobs Configuration................................................................................ 146
Table 24: Server Logs Access Configuration....................................................................................... 146
Table 25: Event Archive Access Configuration.................................................................................... 146
Table 26: Performance Archive Access Configuration......................................................................... 146
Table 27: Logging Configuration.......................................................................................................... 146
Table 28: Launch Management Application Configuration...................................................................147
Table 29: View All Login Attempts at Startup Configuration.................................................................147
Table 30: View Associated Managed Resources................................................................................. 147
Table 31: Asset Management Information Configuration..................................................................... 147

16
 MN002730A01-AD
List of Procedures

List of Procedures
Configuring System Advisor Properties .................................................................................................40
Changing System Advisor Language Preference ..................................................................................42
Changing System Advisor Date Format ................................................................................................ 42
Setting the Initial View ........................................................................................................................... 43
Enabling or Disabling the Login Info Window at the Start-Up ................................................................43
Restarting System Advisor .................................................................................................................... 44
Changing Managed Resource Display Names in Managed Resource Properties Window .................. 45
Changing Managed Resource Display Name in System View ..............................................................45
Setting Default Names for Managed Resources ................................................................................... 46
Changing Subsystem Names ................................................................................................................ 46
Adding Alarm Filters .............................................................................................................................. 48
Configuring E-mail Notifications for Alarm Filters .................................................................................. 49
Modifying Alarm Filters .......................................................................................................................... 52
Modifying Alarm Filter Notifications ....................................................................................................... 53
Loading Alarm Filter Files ......................................................................................................................53
Deleting Alarm Filters ............................................................................................................................ 54
Deleting Alarm Filter Notifications ......................................................................................................... 54
Adding Event Filters .............................................................................................................................. 55
Configuring E-mail Notifications for Event Filters .................................................................................. 56
Modifying Event Filters .......................................................................................................................... 59
Modifying Event Filter Notifications ....................................................................................................... 60
Loading Event Filter Files ...................................................................................................................... 60
Deleting Event Filters ............................................................................................................................ 60
Deleting Event Filter Notifications ..........................................................................................................61
Updating Global SNMPv3 Credentials for the MotoMaster User ...........................................................63
Updating Global SNMPv3 Inform Credentials ....................................................................................... 64
Updating the Network Element SNMPv3 Credentials ........................................................................... 64
Testing any Device SNMPv3 Configuration .......................................................................................... 65
Testing SNMPv3 Communication Between Network Elements and SA ................................................65
Changing Global Web Service Credentials for the MotoMaster User ................................................... 66
Updating Network Element Web Service Credentials ........................................................................... 66
Testing any Device Web Service Configuration .................................................................................... 66
Testing the Web Service Communication Between Network Elements and SA ................................... 66
Configuring North Bound Interface ........................................................................................................ 67
Configuring Discovery Job Credentials ................................................................................................. 67
Disabling Discovery Job Credentials ..................................................................................................... 68

17
MN002730A01-AD
List of Procedures

Starting the SA Client ............................................................................................................................ 69

Navigating Through Active Windows .....................................................................................................70
Detaching a Window from the Client ..................................................................................................... 70
Arranging Windows ............................................................................................................................... 70
Broadcasting Messages ........................................................................................................................ 71
Setting the Page Length ........................................................................................................................ 72
Sorting Table Details ............................................................................................................................. 72
Rearranging and Resizing Table Columns ............................................................................................73
Adding Custom Views ........................................................................................................................... 74
Modifying Custom Views ....................................................................................................................... 74
Renaming Custom Views ...................................................................................................................... 75
Moving Custom Views ........................................................................................................................... 75
Saving Custom Views ............................................................................................................................76
Deleting Custom Views ......................................................................................................................... 77
Exporting Custom Views ....................................................................................................................... 77
Importing Custom Views ........................................................................................................................77
Viewing the Active SA Clients List .........................................................................................................80
Deleting Sites ........................................................................................................................................ 81
Viewing Policy Details ........................................................................................................................... 85
Viewing Job Status ................................................................................................................................ 86
Viewing Grid Views ................................................................................................................................91
Viewing Raw Views ............................................................................................................................... 95
Displaying Alarm Details from the Network Database Window ............................................................. 95
Displaying Event Details from the Network Database Window ............................................................. 95
Viewing Event Details ............................................................................................................................99
Exporting Events ................................................................................................................................. 100
Searching Events ................................................................................................................................ 101
Displaying Alarm Details from the Tabular View Chart ........................................................................103
Displaying Alarm Details from the Severity Alone Pie Chart ............................................................... 104
Displaying Alarm Details from the Severity and Category Chart ......................................................... 105
Viewing Alarm Details ..........................................................................................................................106
Searching Alarms ................................................................................................................................ 107
Viewing Related Events .......................................................................................................................107
Viewing Alarm History and Annotations .............................................................................................. 107
Deleting Alarms ................................................................................................................................... 107
Adding Annotations to Alarms ............................................................................................................. 108
Launching the Alarms View from the Network Database View ........................................................... 108
Exporting Alarms ................................................................................................................................. 108
Displaying Alarms Summary ............................................................................................................... 109

18
 MN002730A01-AD
List of Procedures

Assigning Audio Notifications to Alarms .............................................................................................. 111

Launching the Alarms View from Custom Alarm Panel .......................................................................112
Assigning Ownership to Alarms from the Alarms Details Window ...................................................... 113
Assigning or Unassigning Ownership to Alarms from the Main Menu .................................................113
Managing Resources ...........................................................................................................................114
Unmanaging Resources ...................................................................................................................... 114
Deleting Network Elements ................................................................................................................. 115
Issuing Commands from the Alarms Window ......................................................................................116
Issuing Commands from the Network Database Window ................................................................... 117
Synchronizing Managed Resources ....................................................................................................117
Discovering Network Elements ............................................................................................................118
Aborting Discovery Jobs ......................................................................................................................119
Viewing Configured Collections for a Device .......................................................................................121
Adding Statistics .................................................................................................................................. 124
Modifying Statistics ..............................................................................................................................124
Removing Statistics ............................................................................................................................. 125
Enabling Collections ............................................................................................................................ 125
Disabling Collections ........................................................................................................................... 125
Searching Configured Collections ....................................................................................................... 126
Plotting Collected Statistics ................................................................................................................. 126
Plotting Current Statistics .................................................................................................................... 127
Zooming in on Plotted Graphs .............................................................................................................128
Zooming out on Plotted Graphs ...........................................................................................................128
Viewing Performance Status of Managed Resources ......................................................................... 129
Viewing Managed Resource Properties .............................................................................................. 129
Determining Reliable Communication Capability of a Managed Resource ......................................... 130
Exporting Network Inventory Data .......................................................................................................130
Viewing Associated Managed Resources from the Alarms Window ................................................... 131
Viewing Associated Managed Resources from the Network Database Window .................................131
Viewing Audit Trails for All Users ........................................................................................................ 132
Viewing Audit Trails on the SA Client Web Interface ...........................................................................133
Viewing Audit Trails for Single Users .................................................................................................. 133
Searching Audit Trails ......................................................................................................................... 133
Exporting Audit Trails .......................................................................................................................... 134
Adding Groups .....................................................................................................................................135
Assigning Users to Groups ..................................................................................................................136
Unassigning Users from Groups ......................................................................................................... 137
Deleting Groups ...................................................................................................................................137
Adding Users from the SA Client .........................................................................................................138

19
MN002730A01-AD
List of Procedures

Changing the User Profile ................................................................................................................... 139

Unlocking the User Account ................................................................................................................ 139
Assigning Groups to Users ..................................................................................................................140
Changing the User Password when in the Security Administrator Group ........................................... 140
Deleting Users ..................................................................................................................................... 140
Assigning Operations to Users ............................................................................................................ 148
Logging On to the ESU Client ............................................................................................................. 150
Backing Up the System Advisor Data on Demand .............................................................................. 150
Scheduling the System Advisor Data Backup ..................................................................................... 150
Restoring the System Advisor Data .....................................................................................................151
Uploading a Backup to ESU ................................................................................................................ 151
Retrieving System Advisor Archives and Logs ....................................................................................152
Cleaning the Trap Buffer Manually ...................................................................................................... 155
Configuring Automatic Cleanup of the Trap Buffer ..............................................................................155
Managing and Unmanaging Managed Resources From the Trap Buffer ............................................156
Viewing Archived Events in SA ........................................................................................................... 156
Configuring Server Logging .................................................................................................................158
Configuring Client Logging .................................................................................................................. 159
Hardware Troubleshooting in Network Database ................................................................................160
Removing Alarms for Deleted Entities .................................................................................................161
Testing the Outbound Communication from SA to any Device ........................................................... 162
Testing the Outbound Communication from SA to a Discovered Device ............................................ 162

20
 MN002730A01-AD
About the Capacity Max System Advisor

About the Capacity Max System

Advisor
The chapters within this manual describes and presents detailed and referenced information on fault
management, system, and call monitoring solutions for Capacity Max Systems.
This guide contains important information for the configuration of a Capacity Max system and the
subscriber units using System Advisor (SA).
Motorola Solutions recommends for the user to have an in-depth understanding of the network, the IP-
managed devices for the system, and system topologies. The recommended knowledge allows the
user to make full use of this guide.

What is Covered in This Guide?

This guide contains the following chapters:
• SA Description on page 23
• SA Configuration on page 40
• SA Operation on page 69
• SA Maintenance on page 149
• SA Troubleshooting on page 158
• Basic Configuration on page 165
• Configuration Input on page 166
• Test E-mail Content on page 167
• Mail Server Compatibility on page 168
• Alarms and events on page 169

Helpful Background Information

Motorola Solutions offers various courses designed to assist in learning about the system. For
information, go to http://www.motorolasolutions.com/training to view the current course offerings and
technology paths.

Related Information
Motorola Solutions offers various courses designed to assist in learning about the system. For
information, go to http://www.motorolasolutions.com/training to view the current course offerings and
technology paths.

Related Information Purpose

System Advisor Online Help
Standards and Guidelines for Com-
munication Sites (6881089E50)
Provides assistance in the use of the System Advisor
application. It also provides topic-oriented and reference
information.
Provides standards and guidelines that should be fol-
lowed when setting up a communications site. Also
known as R56 manual.

21
MN002730A01-AD
About the Capacity Max System Advisor
Related Information
Capacity Max System Planner
Capacity Max Installation and Con-
figuration Manual
Capacity Max System Operations,
Troubleshooting and Maintenance
Guide
Capacity Max Upgrade Guide
22
Purpose
Provides description of system features and guidelines
on system architecture and planning.
Provides explanation of the entire process of configur-
ing Capacity Max system.
Provides guidelines for better system monitoring and
troubleshooting possible issues.
Provides instruction step by step on upgrading the sys-
tem to the latest release available.
 MN002730A01-AD
SA Description

Chapter 1

SA Description
The System Advisor (SA) is an application that provides fault management, system, and call
monitoring solutions for Capacity Max Systems. The SA helps users in managing their systems by
providing centralized way of viewing the system health, detailed information about the status of the
infrastructure devices, perform simple operations on the devices remotely, and viewing call activities
and channel usage. The System Advisor manages infrastructure devices through several protocols,
including SNMPv1, SNMPv3, ICMP, and web-services.
The System Advisor consists of client and server application. The server application runs on the
Capacity Max System Server (CMSS) which is logically located at the system level (outside of RF
sites).
The client application is a Java Web Start application that can be run on a Windows-based PC that has
access to the CMSS server (radio IP network). Client application requires Oracle Java to be installed
on the PC and a web browser.

Licensing of System Advisor

The basic functionality of the System Advisor is enabled with the Capacity Max System Advisor
license. Optional functionality is enabled through additional license.

1.1
IP-Managed Devices
An IP-managed device is any device that does not support any protocol-based management interface.
When a device is manually discovered without Simple Network Management Protocol (SNMP) agent
running, it will be discovered as an IP-managed device. Therefore, these devices have limited fault
management capabilities in the SA. These devices are discovered as generic nodes and are
supervised using Internet Control Message Protocol (ICMP) requests. The SA still manages and
reports communication link status of these devices.

1.2
Protocols Supported by SA
Devices that are managed by the SA support various protocols.

Simple Network Management Protocol

Simple Network Management Protocol (SNMP) is a set of protocols used for managing complex
networks. It is an application layer protocol that facilitates the exchange of management information
between network devices. It is also a part of the Transmission Simple Network Management Protocol
(SNMP) and a part of the Transmission Control Protocol/Internet Protocol (TCP/IP) suite. SNMP
enables network administrators to manage network performance, find and solve network problems,
and plan for network growth.
SNMP prevents the following threats:
Modification of Information
An unauthorized entity alters messages or values generated by an authorized entity in the system.
Masquerade
An unauthorized entity assumes the identity of an authorized entity.

23
MN002730A01-AD
Chapter 1: SA Description

Message Stream Modification

Malicious reordering, delaying, or replaying of messages that result in the disruption of normal sub-
network service operation. This disruption could bring about unauthorized management operations.
Disclosure
Eavesdropping on the exchanges between SNMPv3 engines.

SNMPv1
SNMPv1 is the original request-response protocol and framework of the Simple Network Management
Protocol. The Network Management System (NMS) issues a request, and the managed devices return
responses. Four protocol operations are used in an SNMPv1 framework:
• GET
• GETNEXT
• SET
• TRAP

SNMPv2
SNMPv2 improves upon the existing SNMPv1 and adds two new protocol operations: GETBULK and
INFORM.

SNMPv3
In comparison to SNMPv2, SNMPv3 offers greater capability to protect your resources against threats.
SNMPv3 supports authentication and encryption, and is specified in its User-Based Security Model
(USM). The View-based Access Control Model (VACM) is an SNMPv3 approach for Management
Information Base (MIB) access control.
Reliable fault information is also a part of SNMPv3. It involves utilizing INFORMs to reliably deliver fault
information to a management entity.
SNMPv3 has three security levels. The following table explains which SNMPv3 security levels require
authentication and privacy passphrases.

AuthProtocol and PrivProtocol and

Security Level
AuthPassphrase PrivPassphrase
NoAuthNoPriv No No
AuthNoPriv Yes No
AuthPriv Yes Yes

Web Service Protocol

Web Service protocols are used to communicate with VMware devices such as CMSS. The protocols
are based on Simple Object Access Protocol (SOAP) and offer authentication and encryption over
SSL.

1.3
Agents
An agent is software that runs within each device.
An agent responds to all protocols supported by the SA and reports all the events of interest to the
management entity.

24
 MN002730A01-AD
Chapter 1: SA Description

1.4
Redundancy Management
Redundancy is the backup mechanism which takes over the function of a device in case the device
fails to provide its core services, for example due to malfunction.
Redundancy management includes the capability of the network element and the management entity
to provide and report such a failover condition.

1.5
Synchronization
The SA performs synchronization automatically, by validating the health of a device with the
information stored in the fault management database.
If the SA finds a discrepancy, it generates an event or an alarm. Synchronization can also be:
• Periodic synchronization triggered by the system clock
• New device discovery
• Rediscovery of an existing device
• User-initiated synchronization
NOTICE: The synchronization process only generates an alarm when it detects that the state of
a device differs from the state currently reported by the SA.

1.6
Supervision
The SA periodically checks its ability to communicate with the devices it manages.
This operation is referred to as supervision and is used to determine the following:
• Whether communication with the device is lost
• For SNMPv3 devices that support reliable communication, whether SA is supposed to initiate
synchronization with the device
If a device does not respond to the supervision query in a timely manner, the SA generates a
Communication Loss event or alarm against the managed device.

1.7
North Bound Interface
North Bound Interface (NBI) describes an interface offered by many Network Management System
(NMS) products, such as the System Advisor (SA).
NBI allows for NMS features, functions, and data to be accessible for Operations Support System
(OSS) and Manager of Managers (MoM). The OSS can use the NBI to retrieve information from NMS.
It uses SNMP which is a standardized protocol. It is also typical for NMS to forward information
automatically to the OSS. An example of such notification is the trap forwarding function available in
most NMS products.
SA supports the capability to send up events to hosts that support data processing by applications
other than Motorola Solutions applications. An example of such a host is the Manager of Managers
(MoM). The customer-processed data is typically viewed as reports by managers who are interested to
see a summary of information from the NMS.
SA supports North Bound Interface (NBI) for sending up notifications to the registered MoMs.
Currently, there are two interfaces that are supported. NBI uses SNMPv3 and the User-Based Security
Model (USM) to provide secure communication between SA and NMS.

25
MN002730A01-AD
Chapter 1: SA Description

NBI services are:

NBI Event Forwarding
The events reported on SA are sent to registered NMS using SNMPv3 traps.
NBI Notification Persistence
SA stores the last 300 events forwarded to enable NMS to quickly retrieve any events it may have
missed.
NBI Event Synchronization
SA provides the means for NMS to query and obtain a set of events from the SA datastore. This
feature is typically used to obtain events missed due to lost traps or when connectivity between SA
and NMS is lost temporarily.
Getting QuickSync events
SA provides the means for NMS to query and obtain a set of events from the SA datastore. This
feature is typically used when the missed trap is within the most recent 300 traps captured in NMS.
NBI Alarm Synchronization
SA provides the means for NMS to query and obtain a set of alarms from the SA datastore. This
feature is typically used to re-synchronize fault information on the NMS after an extended outage.

1.8
System Advisor Overview
System Advisor is a critical fault management application.
SA primary functions are:
• Fault management of devices (SNMP traps or informs)
• Maintaining inventory of managed devices
• Detecting and reporting loss of communication with managed devices (Supervision)
• Ensuring the status reported is current (Synchronization)
• Basic troubleshooting capability
• Ability to manage/un-manage a device or delete a subnet/device
• Device Command Operation (Repeater commands like Enable/Disable/Reset)
• Alarm generation/annotation/ownership assignment/clearing/acknowledgment
• Alarm Summary
• Capability to use a secure protocol (i.e. SNMPv3)
• User access management
• Real-time call monitoring
• Call log archives
SA presents the faults and, in general, the status of the network elements in the following views:
• System View
• Network Database
• Network Events
• Alarms
These views and their operations are explained in detail in Fault Management Operations on page 95
SA user accounts are managed within the application. You can set up system partitions and assign
management responsibility to one or more administrators. The setup and maintenance of accounts are

26
 MN002730A01-AD
Chapter 1: SA Description

explained in SA Configuration on page 40 and Security Management Operations on page 131. SA

also controls critical management operations invoked by operators within the application.
SA provides the capability to manage devices securely (using SNMPv3). SA can detect and report loss
of fault notifications. It can quickly update without constantly polling the devices.
SA North Bound Interface (NBI) supports notifications in the form of SNMPv3 traps to registered
managers and access to management data. The NBI uses SNMPv3 and the User-Based Security
Model (USM) to provide a secure communication between SA and Network Management System
(NMS).

1.8.1
System Advisor Main Functions
The following sections describe the main functions of the System Advisor (SA).

System View
System View provides a hierarchical view of the SA Network Database and groups system level
devices under a System object and the site level devices under Site objects. The Capacity Max system
supports up to 250 RF sites. Therefore, Site objects are also arranged in groups for easy navigation.
Status is propagated upward from each device to provide an “at-a-glance” view of the system health.
You can quickly navigate to other views: Alarms, Event, or Network Database views that show the
additional information for the selected element.

Real-Time Call Monitoring

System Advisor provides two views that show real-time call activities:
Grid View
Shows the list of sites, arranged in groups, with available channels and activity on the channels
(slot usage). You are able to see transmissions happening on the channels, call types, channel
types, and fault state of the channels, which is actually the fault state of the repeater hosting the
channel.
Call View
Shows the list of calls and decoded events as received by SA. Call View shows active, queued, and
finished calls. Associated call events and other events (not related to calls) are also shown. Other
events (not related to calls) are also shown.

North Bound Interface (NBI)

This includes notification of network events and management events to the registered managers:
• The network events are the events originated at the device level or the SA, regarding certain
network behavior.
• The management events are events originated at the System Advisor as a result of management
operations performed on System Advisor (like synchronization, discovery, manage/un-manage a
device and others).
The NBI supports both clear and secure capability of sending the notifications (SNMP Traps) over
SNMPv3 protocol. NBI functionality requires NBI license to be purchased by the customer.

Discovery and Network Database

Discovery is the process of adding an individual device or all the devices in a system into the SA
database. SA supports automatic triggering of discovery process for devices reported by the system,
as well as manual discovery of the device after user provides necessary parameters (like IP address
and SNMP port).

27
MN002730A01-AD
Chapter 1: SA Description

In the SA, the network database view serves as an inventory of the network resources. It maintains the
properties of all the managed resources, including both physical devices (for example, Repeater) and
logical entities (for example, Site, System, Network) discovered by SA.
You can invoke operations on inventory items such as command, manage/un-manage,
synchronization, ping, trace route, and others.

Device Synchronization
Device Synchronization is defined as the basic mechanism that allows SA to determine and refresh the
information about the status of managed devices. The synchronization process performs periodic
SNMP query on each device in “managed” state. Certain users may not want to receive updates about
the state of particular devices. In such cases, the device can be moved by the user to the "un-
managed" state and synchronization process will omit such devices.

Communication Link Management

Communication Link Management is defined as the basic mechanism for the SA to detect
communication loss between the SA and a particular managed device. Whenever a communication
loss is detected, the SA generates a communication loss alarm in the alarm browser. In order for
Communication Link Management to function, the device must be currently managed by SA.

Command Operation
The SA provides command operation for repeater devices. The following commands are supported by
the SA:
Enable, Disable, Reset
Allows you to change the operational state of the repeater.
Read of Repeater Remote Diagnostic counters
Allows you to gather repeater diagnostic information and store it in log file for further analysis. If the
command is successful, the link to the folder with the logs is displayed in the status bar of the
command dialog. Repeater diagnostics data files are saved as repeater_rds.log,
repeater_rds.log.1 and others.
Reset Repeater Remote Diagnostic counters
Allows you to reset the counters to initial value.

Network Events
Network event is the basic unit of management information that represents what has happened to a
particular managed device. Events can convey general information such as discovery of a device or
specific information such as failure of a managed entity and status update of a managed entity. Events
also show the associated entity or component, textual description, and the severity of the occurrence.
Events form a repository of information for all the occurrences in the system. The SA event view
provides a way to look at all events (or a filtered subset of events) that are received (or generated) by
the SA.
You can view the details of each event, export them to .cvs file or define custom view(s) to view a
filtered subset of events. For example, view only critical events that are from a particular device type
and/or from a certain site.
Events relate to an occurrence, such as:
• Initial discovery or rediscovery of an element
• Status update of an element
• Deletion of an element
• Failure in an element

28
 MN002730A01-AD
Chapter 1: SA Description

Alarms
In SA, an alarm results from an event in a managed device that met a pre-determined significant state
change that may require user attention. The SA alarm view provides a way to look at all alarms (or a
filtered subset of alarms). An audible tone can be associated with alarms, based on severity.
Alarms are raised within SA based on notifications from the network element, or by SA to report
failures associated with fault management functions. An alarm becomes active once the SA displays it
in the alarm view, but not cleared yet. Whenever the problem that caused the alarm (of a particular
managed device) to be elevated in SA is resolved, SA clears the alarm. An Alarm Clear Timer policy
can be set (by a user with Admin privileges) to cause cleared alarms to persist in the SA alarm view
anywhere from 15 minutes to 10 hours, in 15 minutes increments.
Alarms can fall into the following general categories:
• Communication alarms
• Equipment alarms
• Quality-of-service alarms
Alarms across a network are commonly related to:
• Resources that have failed
• Connectivity issues
• Devices malfunctioning
• Threat assessment reports
• SNMPv3 or Web Service credentials failure
You can assign an alarm to a user and enter any additional information in a text field. In addition, you
can view the alarm details, export the alarms to .csv file for future analysis and define custom view(s)
to view a filtered subset of alarms.

Fault Event Archives

The SA client application presents the latest 10,000 fault events on its events views. All events with all
defined event properties are additionally saved for later use. Archived events are stored in two ways:
• In the event archive database – Events which can be accessed via web interface that allows
filtering, searching, and exporting to .csv files.
• In the fault event files - The number of events archived in the database is limited, therefore all
events are also saved in the files. Application keeps the files for 31 days - the older files are
automatically removed from the SA server. The files can be accessed and downloaded via the SA
web interface.

Call Event Archives

The SA client application presents the latest 10,000 call related events on the real-time views. All
events are additionally saved in the files for later use and can be accessed and downloaded via the SA
web interface. The files are kept in two formats: binary and text. The application keeps the files for 31
days and the older files are automatically removed from the SA server.

Security Administration
SA provides security administration via Role Based Access Control functionality. Briefly, this implies
that the user accounts in SA application must be created and assigned with specific roles (for example,
groups) for performing a certain set of operations. Users of the SA (dealers or administrators) assigned
into different roles allow System Advisor SA to partition different operations (for example, create new
user/role, manage/un-manage resource, invoke command to a device, perform manual discovery) and
define the permissions that each role/group for a particular application uses.

29
MN002730A01-AD
Chapter 1: SA Description

SA captures all user activities with user activity logs/audit trials.

Email Notification
The Email Notification feature provides a generic notification interface, namely Simple Mail Transfer
Protocol (SMTP) that can be configured and integrated with any standard email/paging solution that a
customer may use.
The SA allows notification configuration based on destination(s) to be sent, occurrence of certain
event/failure, and alarm severity of certain device. Operators are notified via email whenever such
event/failure occurs, so that further diagnostics can be performed immediately.

1.8.2
System Advisor Redundancy
The Capacity Max system supports up to five System Advisor servers. Only two SA instances can be
active at a time.
When more that two System Advisor servers are deployed, the Trunk Controller selects two as active
and the remaining servers are inactive.
If a System Advisor that you are using becomes inactive, for example due to a failure, log on to an
active System Advisor. See Starting the SA Client on page 69.
All System Advisor servers operate independently and user customizations performed on one server
are not applied on other servers (for example, custom views or modifications in users and groups).

Active System Advisors

Active System Advisor servers perform the following functions:
• Log system call activity
• Display real-time system traffic
• Refresh information about managed devices
• Log events and alarms reported by managed devices
Only active System Advisor servers synchronize with managed devices. If an alarm is dropped in the
network, device synchronization determines the alarm state of a device within 10 minutes.

Inactive System Advisors

Inactive System Advisor servers log events and alarms reported by managed devices. Inactive System
Advisors do not receive or display call activity information.
Inactive System Advisors do not synchronize with managed devices, so dropped alarms are lost.
However, you can manually initiate synchronization of a selected device to obtain the current
information from a device.

1.9
SA Client Overview
The SA client application provides an end-user interface for the SA Fault Manager.
The SA client is launched through a web browser which provides starting point and flexibility in
application deployment.
When used for the first time, the application is downloaded from the server onto the local machine
using Java WebStart technology. For subsequent uses, the application is launched from the local
workstation.

30
 MN002730A01-AD
Chapter 1: SA Description

To meet security requirements, the SA Client application uses SSL and SSL over HTTP (HTTPS) for
client-server communication and secure web browser connection. HTTP access is not supported.
To provide seamless access to the SA client, it is recommended to install the SSL certificate for the SA
application first. The certificates are installed from the browser store.

1.10
Navigation Tree
The navigation tree on the left-hand side in the main System Advisor (SA) panel enables you to quickly
select different fault management views.
Selecting nodes in the tree opens the associated view on the right-hand side of the main panel. Nodes
may be added to the tree by creating custom views. Similarly, only the nodes associated with custom
views can be removed from the tree.
Figure 1: System Advisor – Navigation Tree

1.11
Fault Management Overview
Fault management in the SA application includes processing and presentation of events sent by a
network element in the form of a Simple Network Management Protocol (SNMP) trap or inform, or a
Simple Object Access Protocol (SOAP) message.
Failures in the network, network elements, and communication links can interrupt routine activities. In
such situations, SA reports events.

31
MN002730A01-AD
Chapter 1: SA Description

1.11.1
Severity Definitions
Alarms and events are assigned with severity levels, indicated by a severity color and an alarm or
event message. The action required depends on the severity of the alarm.

Table 1: Severity Categories

Severity Value Color

CommFailure 1 (highest severity) Black
Critical 2 Red
Major 3 Orange
Minor 4 Yellow
Warning 5 Cyan
Clear 6 (lowest severity) Green
Info 7 White

NOTICE: When a managed resource is in an unmanaged state, the status (severity) of the
resource is unknown. Only a device in an unmanaged state uses this status. The info severity
level is only used for events, never alarms.

1.11.2
Event Category Definitions
Network elements detect and report to Ssytem Advisor (SA) conditions that have caused or can cause
an interruption in the operation of network elements.
Such conditions can be related to physical failures of a device, for example, fan failure. SA may also
report certain conditions that it detects within the application or on the device. In all cases, SA inspects
the reported condition and categorizes the event as one of the items in the following table.

Table 2: Event Category

Description
Attribute Value Change
Event
Communication Alarm
Equipment Alarm
Informational Event
Condition
An important parameter value has changed.
A communication/synchronization loss or regain is detected.
An equipment or link failed or a previously reported failure is cleared.
A condition that is important, but is not a failure at this time.
NOTICE: Some informational events report conditions that
may cause a failure in the future. These events are nor-
mally reported with a severity higher than Info.

Management Event A condition is detected and reported by SA and is related to a critical

function of SA.
Quality of Service Alarm A service-impacting condition is detected.
Security Violation A credential mismatch condition is detected by SA. Typically associ-
ated with devices that use SNMPv3 to communicate with SA.

32
 MN002730A01-AD
Chapter 1: SA Description

1.11.3
Unknown Events
SA could display an Unknown Event against a discovered device.
SA displays such events with the warning severity and the informational event category when
discovered devices send a notification that is not recognized by SA (SA has no rules to process and
display a received notification type).
The message of this type of event contains:
• The text Unknown Event
• The type SnmpTrap (for SNMP notifications)
• Variable bindings (varbinds) together with received values in the format <varbind>=<value>
NOTICE: SnmpTrap type and varbinds can be presented as:
• text when SA has MIBs to translate the object identifier (OID) to an exact name
• a raw OID if OIDs are from MIB and are not supported by SA

1.11.4
Command Window
You can use the command window to send commands to a selected managed resource, including
repeaters.
The command window provides the list of entities (or device manager resource types) and the
associated commands available for the selected managed resource. If multiple instances of an entity
can exist, a combo box is displayed next to the entity type. The list in the combo box contains all
possible IDs for the entity type. The entities are sorted in alphabetical order.
If the command window is invoked from the Alarms window, the entity associated with the selected
alarm is selected.
If the command window is invoked from the Network Database window, the first entity in the list is
selected.
NOTICE: If the entity has only one instance, no instance ID is displayed.

The status of a command request is displayed in the multi-line status bar at the bottom of the
command window. The managed resource typically responds to a command by changing the state of
one or more entities. These changes are reported to System Advisor (SA) and are displayed in the
Alarms window. To view these alarms, click View Alarms or select Alarms from the navigation tree.
NOTICE: Clicking View Alarms automatically filters the alarms to display only the alarms
associated with the selected managed resource.

33
MN002730A01-AD
Chapter 1: SA Description

Figure 2: System Advisor – Command Window

1.11.5
Alarms Window
You open the Alarms window from the Navigation View by clicking the Alarms node under the Fault
Management node.
In the window, only active alarms of devices are displayed, that is the latest failure or an event clearing
a failure. You can open the detailed view of an alarm by double-clicking an entry in the window. The
Alarm Details window allows the you to perform the following functions:
• Assign/Unassign an alarm
• Annotate an alarm
• View the history of the selected alarm
The default sorting criterion in the Alarms window is the Date/Time column. You can sort the events by
any attribute by clicking the associated column heading. To toggle between ascending and descending
sort orders, click the column again.

1.11.6
Alarms Summary
Alarm summary is used to display the count of the total number of alarms organized by categories
and/or severities.
It is positioned just below the navigation tree in the main window. Each severity is represented in a
single cell or graph, depending on the presentation that is selected. The view is updated automatically
and the counts can be seen at all times, irrespective of the view that is currently open.
The presentation of the alarm summary can be modified by clicking the buttons at the top of the
summary panel. Three different presentations are available:
• Table view
• Bar graph view
• Pie chart view

34
 MN002730A01-AD
Chapter 1: SA Description

1.11.7
Network Events Window
The Network Events window is accessible from the Navigation View by clicking the Network Events
node under the Fault Management node.
The window displays all notifications received or generated by SA. The notifications include various
properties related to events that are raised against devices. You can open the detailed view of an
event by double-clicking an entry in the window. By default, you view 50 events on a single page. You
can customize the number of events displayed on the page. The maximum number of events on a
page is 1,000.
The default sorting criterion in the Network Events window is the Date/Time column. You can sort the
events by any attribute by clicking the associated column heading. To toggle between ascending and
descending sort orders, click the column again.
Figure 3: Network Events Window

1.11.8
Network Database
Network database serves as an inventory view for the resources that are currently present in the
System Advisor (SA) database.
By default, network database displays certain critical properties associated with these resources.
Resources can be physical devices (for example a repeater site controller), networks, or logical entities
(for example a site). The contents are presented in a tabular format with each row corresponding to a
resource. The default page size of this view is 25 entries, but it can be modified to show more or fewer
entries in one page.
Network database displays a status value for each resource. This value is calculated based on the
highest severity of the alarms that are currently outstanding against the resource.
The unknown value indicates that SA does not currently manage the device.

35
MN002730A01-AD
Chapter 1: SA Description

Figure 4: System Advisor – Network Database Window

1.12
Performance Management Overview
SA can collect and plot statistical data.
You can use the data to analyze functions and performance of your system. The data collection for
these statistics is triggered 10 minutes after the server application startup time.

Performance Management Terminology

The following are terms and definitions used within the performance management functions of SA:
Polled Data
The pattern in which data is collected from a device is defined in a variable called Statistics (also
called Polled Data). A statistic is the basic object used for data collection. It contains details such as
the contacted device, the data collected, and the time interval. The Statistics object does not store
the collected data.
Polling
The process of contacting the device and collecting the data for the specified statistics.
Polling Period
The interval in which the device is polled for the statistical data.
Collected Statistics
The statistics collected and stored in the database at the specified polling period.
Current Statistics
The statistics polled instantly from the device. This data is not stored in the database.

1.13
Discovery Overview
Discovery is the process of adding an individual device or all the devices at a system into the System
Advisor (SA) database.
SA supports automatic triggering of discovery process for devices reported by the system. You can
also manually discover a device by providing necessary parameters, like IP address and SNMP port.
Once the devices are discovered, SA reads and stores critical parameters. It also determines the

36
 MN002730A01-AD
Chapter 1: SA Description

current health (status) of the devices and their components. Then, it starts monitoring the connectivity
(supervision) to the devices.
As a result of a device discovery, additional resources are displayed in the SA Network Database
window. These resources are referred to as logical managed resources (LMR). The device itself is a
device managed resource (DMR). LMRs typically represent a set of related services or components
that a device reports on. They can be managed independently due to their physical or logical
relationship. An example of a physical relationship is a separate device connected to the device. A
logical relationship can be an active device in a redundant configuration. For a list of resources
associated with a device, see “Alarms and Events” in the System Advisor Online Help.
You initiate the discovery of a device or a site/network from the Discovery Configuration user interface.
You specify a unique identifier, for example the IP address or Hostname, and start the discovery
process. You can also set SNMPv3 and/or Web Service credentials for a discovery job.
Re-discovering a device is functionally the same as first-time discovery. However, the term is used to
describe the discovery operation performed on a device that is already in the SA database. During a
rediscovery, SA adds the resources of a device that are not present in the SA database. SA also
verifies the current resources of the device. If the verification fails, an alarm is raised against the
resource to indicate that the device does not respond to queries. To remove such alarms, you can
verify the configuration of the device and invoke rediscovery at a later time. If the resource is no longer
active in the system, you can delete it.

1.13.1
Devices Discovered by SA
For a list of devices managed by System Advisor (SA) and the alarms and events connected, see
“Alarms and Events” in the SA Online Help.

1.13.2
Post-Discovery Synchronization
Devices that are discovered successfully are automatically synchronized by the System Advisor (SA)
on a regular basis.
Synchronization is done in the background, but the status is automatically updated and displayed in the
following windows:
• Alarms
• Network Database
• System View
• Grid View
A device sends traps or informs to SA. The SA server application must continuously communicate with
the devices to ensure that status information is up-to-date. Therefore, SA also monitors its connectivity
to the device

1.14
Events Archive
In System Advisor (SA), you can view the latest 10,000 events sent to SA.
In SA, you can view the latest 10,000 events which are sent to SA. Older events are automatically
cleaned up (purged). SA periodically archives received events in two ways: in the SA file system and in
a database.

37
MN002730A01-AD
Chapter 1: SA Description

Archivization in the SA file system

Event archive files contain all event fields that are defined in the event database. The event archive file
format contains one event with all its attributes. The format uses a comma as a delimiter between
event fields within the line (.csv format). SA maintains one event file a day. If event archive files are
older than 31 days, SA cleans them up.
Figure 5: SA File System – CSV Files List

Archivization in a Database
All events that SA receives are automatically forwarded to a separate table. From that table, Fault
Manager can get information about all past events that do not exceed the number of seconds defined
in the ArchiveCleanupPolicy. Through the SA client web interface, you can display archived events or
export them to .csv files based on the provided filtering criteria.
Figure 6: Events Archive – SA Client Web Interface

38
 MN002730A01-AD
Chapter 1: SA Description

Archived Events Properties

Severity
The severity of an event.
Date/Time
The time at which an event is generated in SA. It is displayed in the Date/Time field in the Network
Database window.
Managed Resource
A user-friendly name of a managed object which a particular event corresponds to.
Entity
A user-friendly name of a failure object which a particular event is associated with.
Message
A descriptive text message about an event.
Archive ID
A unique, sequential ID of an archived event. SA assigns it to all archived events.
Event ID
A unique, sequential ID of an event. SA assigns it to all each events.
Category
The category of the event. For example:
• Information event
• Attribute Value Change Event
• Equipment Alarm
• Quality of Service Alarm
• Communication Alarm
• Processing Error Alarm
• Object Creation Event
• Object Deletion Event
• Management Event
• Security Violation
Node
The name of the corresponding network element which a particular event is being generated for.
Failure Object
A failure object responsible for the creation of an event. The internal name is derived by SA.
Source
The managed object which an event corresponds to. Generally, it is the name of a managed object.
Reporting Agent
The IP address of a device (agent) that sends an event.
NE Timestamp
The time at which an event is generated in a device (agent). If the device does not send this
timestamp in the event, there is no value assigned to this attribute.
Identifier
An internal attribute that uniquely identifies a particular event.

39
MN002730A01-AD
Chapter 2: SA Configuration

Chapter 2

SA Configuration
Configuration procedures enable you to configure System Advisor (SA) for your specific network.

2.1
Application Configuration
The following configuration operations can be made to the SA interface:
• System Advisor properties
• Language and date format
• User preferences configuration
• Network Database configuration
• Alarm filters configuration
• Event filters configuration

2.1.1
Configuring System Advisor Properties
Follow the procedure to configure System Advisor (SA) properties.

Procedure:
1 From the menu bar, click Tools → Configure System Advisor Properties.
The Configure System Advisor Properties window appears.
Figure 7: Configure System Advisor Properties Window – General Properties Tab

2 To configure the general properties of the System Advisor, in the General Properties tab,
perform the following actions:

40
 MN002730A01-AD
Chapter 2: SA Configuration

a Make the required changes in the respective configuration fields:

• Network ID
• Server ID
• Base UDP Port
• Call Monitor Application UDP Port
• Primary Trunking Controller IP
• Primary Trunking Controller Port
b Click Update.
In the same window, a message appears prompting a server restart.

3 To configure alternative Trunking Controllers, perform the following actions:

a Click the Alternative Trunking Controllers tab.
b Click Add.
c In the Configure Alternative Trunking Controller window, enter the appropriate values in
the respective fields:
• Trunking Controller IP
• Trunking Controller Port
• Trunking Controller Server ID
d Click OK.
The data for the Trunking Controller is added to the list.

e To add more Trunking Controllers, repeat step 3 b through step 3 d.

f Click Update.
In the same window, a message appears prompting a server restart.

Postrequisites: Restart the server to implement the changes in configurations. For more information,
see Restarting System Advisor on page 44.

2.1.2
Language and Date Format
You can configure the language preference and date format of the System Advisor (SA).
The current language settings and date format are displayed in the Change Language and Date
Format window as shown in the following figure:

41
MN002730A01-AD
Chapter 2: SA Configuration

Figure 8: Change Language and Date Format Window

2.1.2.1
Changing System Advisor Language Preference
System Advisor (SA) supports seven languages, namely English (United States), German, Spanish
(Chile), French, Brazilian Portuguese, Russian, and Simplified Chinese.

Procedure:
1 Select Administration → Change Language and Date Format.
The Change Language and Date Format window appears.

2 In the Change language to: dropdown list, select the preferred language.
3 Click Update.
Postrequisites: Restart the SA server to implement the language change.

2.1.2.2
Changing System Advisor Date Format
The System Advisor supports two types of date formats.

Procedure:
1 Select Administration → Change Language and Date Format.
The Change Language and Date Format window appears.

2 In the Change date format to: dropdown list, select the preferred date format.
3 Click Update.
Postrequisites: Restart the SA server to implement the language change.

42
 MN002730A01-AD
Chapter 2: SA Configuration

2.1.3
User Preferences Configuration
All users can configure the initial SA view and login information. User Preferences Configuration

2.1.3.1
Setting the Initial View
Procedure:
1 Select Administration → User Preferences.
The User Preferences dialog box appears.
Figure 9: User Preferences dialog box

2 In the Initial View on Login drop-down menu, select the view you want to see each time you
log on. The following views are available:
• Alarms
• Network Events
• Network Database
3 Click OK.
Your preference is saved. The User Preferences dialog box displays the currently saved option each
time you open it.

2.1.3.2
Enabling or Disabling the Login Info Window at the Start-Up
Procedure:
1 Select Administration → User Preferences.
The User Preferences dialog box appears.

2 From the Display login info at startup drop-down menu, do one of the following:
• Select Yes to display the window at the start-up
• Select No not to display it.
3 Click OK.
Your preference is saved.

43
MN002730A01-AD
Chapter 2: SA Configuration

2.1.4
Restarting System Advisor
Certain changes in the configuration of the System Advisor (SA) requires restart for the
implementations of changes to take effect. For example, changing language preference.

Procedure:
1 Select Administration → Restart System Advisor Server.
The Restart Server warning dialog box appears.
Figure 10: Restart Server Warning

2 Perform one of the following actions:

• To proceed with restart, click Yes.
• To cancel restart, click No.

If you choose to restart, a broadcast message appears indicating that the SA Server restarts in
60 seconds.
If you choose to cancel restart, skip the following steps.

3 To proceed with restart, click OK in the Broadcast Message window.

At the end of the 60 seconds countdown, the System Advisor — Connection Lost warning
message appears.
Figure 11: Server Connection Lost Warning Message

4 To close and restart the SA, click OK.

The SA Client closes.

44
 MN002730A01-AD
Chapter 2: SA Configuration

Postrequisites: Restart the SA Client to view the implemented changes.

2.1.5
Network Database Configuration
You can configure the network database by changing the display names of managed resources and by
changing the names of subsystems.

2.1.5.1
Changing Managed Resource Display Names in Managed Resource
Properties Window
Follow this procedure to edit managed resource display names in the Managed Resource Properties
window.

Procedure:
1 In the Navigation View panel, click the Network Database node.
2 In the Network Database window, highlight a row, right-click it, and select Managed Resource
Properties.
The Managed Resource Properties window appears.

3 In the Display Name field, type the name of the node you want to see displayed in the Network
Database View and click Modify.
The device displays the updated name in the Managed Resource field.

2.1.5.2
Changing Managed Resource Display Name in System View
Follow this procedure to edit managed resource display names in System View.

Procedure:
1 In the Navigation View panel, click System View.
2 In System View, right-click the managed resource.

A menu dialog appears.

45
MN002730A01-AD
Chapter 2: SA Configuration

3 Click Rename.

The Edit Value window appears.

4 In the Edit Value window, type the new display name for the selected managed resource.
5 Perform one of the following actions:
• To save the new display name of the managed resource, click Save.
• To exit the Edit Value window, click Cancel.
If the new display name is saved, the System View page refreshes and the new display name of the
managed resource is reflected.

2.1.5.3
Setting Default Names for Managed Resources
Procedure:
1 In the Navigation View panel, click System View.
2 In System View, right-click the managed resource.
A menu dialog appears.

3 Click Set Default Name.

The System View page refreshes and the default name of the managed resource is reflected.

2.1.5.4
Changing Subsystem Names
In SA, you can edit subsystem names so that Logical Managed Resources (LMR) and Device
Managed Resources (DMR) are segregated into appropriate groups.

Procedure:
1 In the Navigation View panel, click the Network Database node.
2 In the Network Database window, right-click an item and select Managed Resource
Properties.
3 In the Managed Resource Properties dialog box, click the Relationship tab.
4 Type the new name in the Subsystem Name field and click Modify.
NOTICE: The length of the subsystem name cannot exceed 100 characters. If the
Subsystem Name field is left blank, SA uses the default subsystem name.
The subsystem name is changed.

46
 MN002730A01-AD
Chapter 2: SA Configuration

2.1.6
Alarm Filters Configuration
When an alarm is created, the occurrence of the alarm can be associated with some actions.
SA provides alarm filters to send e-mails to an administrator on occurrence of an alarm. This action is
called a notification. By configuring alarm filters you can filter alarms based on certain match criteria.
With this tool you can also add, modify, or delete filters and filter actions.
When alarms are generated from devices in a network, you can configure SA to send notifications to
users. You can use alarm filters, also referred to as alert filters, to configure SA to automatically initiate
actions for selected alarms.
NOTICE:
The property name, when used for filtering, is case-sensitive and should be used exactly as
specified when typing in the name of the additional property criterion to filter on.
Do not use the following characters in property names:
white space
empty space
> < & $ # ^ - " ' ""
a digit at the beginning of the name
* ! @ ( + ~ { [ | \ ; , . ? / % `
SA supports only the Sending e-mails built-in filter notification. Other notification types that can
be associated with the filter are Suppressing events, Running system command, Sending
custom trap, and Running Custom Code. Even though these notifications are available on the
user interface, Sending e-mails is the only notification type recommended for use during filter
configuration on SA. Do not add/delete or modify other notification types. These notification
schemes require advanced knowledge and privileges and therefore are not recommended for
general use. Contact Motorola Solution Support Center (SSC) for information on the use of
notification schemes other than e-mail notification scheme.

Match Criteria Property Overview

The managed resource and severity criteria determine whether the incoming alarm or event can be
filtered or not. If any field is left blank, it is not considered matching criteria. For the alarm or event filter
to be applied, it must satisfy all the match criteria specified. If even one of the criteria fails, the filter is
not applied. You can use wildcard characters and expressions to specify the match criteria. SA accepts
any match criteria you enter. However, if you want to make sure that your criteria are valid for the
system, enter them into a custom view. Criteria specified for custom views take immediate effect, while
an alarm or event filter only works when new alarms or events of the specified type occur.
Manage/Unmanage
Option that enables you to manage or unmanage SA resources. For example, you can unmanage
resources that are broken so that they do not send many traps to the trap buffer and take a lot of
the trap buffer capacity. After the resources are fixed, you can manage the fixed resources to
enable SA to receive traps from them.
Clean Trap Buffer & Sync
Option that enables you to clear the trap buffer of all traps SA received from a managed resource.
After the trap buffer is cleared, SA schedules synchronization with managed resources whose traps
you removed. As a result, SA receives up-to-date information from the managed resources.

47
MN002730A01-AD
Chapter 2: SA Configuration

2.1.6.1
Adding Alarm Filters
Procedure:
1 In the Navigation View panel, click the Alarms node.
2 From the main menu, select Edit → Alarm Filters.
The Alert Filters window appears.
Figure 12: Alert Filters Window

3 In the Alert Filters window, click Add Filter .

The Actions List pane options become active.

4 In the Filter Name field, specify the name of the filter.

5 In the Match Criteria pane, specify the Managed Resource and Severity criteria.
6 Optional: Configure additional match criteria by clicking Advanced. In the Match Criteria
Properties dialog box, you can configure the following match criteria:
• Message
• Category

48
 MN002730A01-AD
Chapter 2: SA Configuration

• Domain
• Network
• Node
• Failure Object
7 Optional: Configure a filter by using an alarm property that is not displayed on the user interface:
a In the Match Criteria Properties dialog box, click More Properties.
b In the Property Name and Property Value fields, specify filter properties. Click OK.
The value must be the same as the one listed in the Property name for the filtering column.
To modify an existing property, in the Property Name field, enter the same value again and
in the Property Value, enter a new value. To remove a property, in the Property Name field,
enter the same value again and leave the Property Value field blank.
c Close the More Properties dialog box. In the Match Criteria Properties dialog box, click
OK.
8 In the Actions List pane, click Add Action.
9 In the Add Action window, add an action related to the notification.
A filter must have at least one notification associated with it.
10 Finish adding filters and notifications by clicking Apply. Click OK.

2.1.6.2
Configuring E-mail Notifications for Alarm Filters
You configure the e-mail notification to receive e-mails from System Advisor (SA) about incoming
alarms or events that matches your filter criteria. You configure the e-mail notification by adding
specific alarm or event properties to your criteria. Your notification settings and the certificate that you
need for secure communication are backed up during your backup process.
In property names, do not use the following characters:
white space
empty space
> < & $ # ^ - " ' ""
a digit at the beginning of the name
* ! @ ( + ~ { [ | \ ; , . ? / % `

Procedure:
1 In the Navigation View panel, click the Alarms node.
2 From the main menu, select Edit → Alarm Filters.

3 In the Alert Filters window, click Add Filter .

The Actions List pane options become active.

4 In the Actions List pane, click Add Action .

5 In the Add Action window, click the Email tab.

49
MN002730A01-AD
Chapter 2: SA Configuration

Figure 13: Add Action Window – Email Tab

6 In the Notification Name field, enter the name of the e-mail notification. Click Configure.

50
 MN002730A01-AD
Chapter 2: SA Configuration

Figure 14: SMTP Configuration Dialog Box

7 In the SMTP Configuration dialog box, enter the following account details:
a In the Account Name field, enter an SMTP account name.
b In the SMTP Server field, enter a server name.
c In the From Address field, enter a source e-mail address.
d In the To Address field, enter a target e-mail address.
e Click Add. Click OK.
8 Optional: Test the e-mail notification:
a In the Add Action window, from the SMTP Account list, select an SMTP account.

b In the Subject field, click Append Property and select the properties you want to
receive. Click Send Test Email.
In the Message field, a default message is added.

c In the confirmation window, click Yes.

Configuring additional filter match criteria
9 In the Alert Filters window, click Advanced.
10 In the Match Criteria Properties dialog box, configure the match criteria of your choice.
You can configure the following match criteria:
• Message
• Category
• Domain

51
MN002730A01-AD
Chapter 2: SA Configuration

• Network
• Node
• Failure Object
Configuring filter properties that define what information you receive in the e-mail notifications
11 Configure a filter by using an alarm property that is not displayed on the user interface:
a In the Match Criteria Properties dialog box, click More Properties.
b In the Property Name and Property Value fields, specify filter properties. Click OK.
The value must be the same as the one listed in the Property name for the filtering column.
To modify an existing property, in the Property Name field, enter the same value again and
in the Property Value, enter a new value. To remove a property, in the Property Name field,
enter the same value again and leave the Property Value field blank.
c Close the More Properties dialog box. In the Match Criteria Properties dialog box, click
OK.
SA sends a test notification to the specified e-mail address. The test notification does not contain the
properties that you specified in the e-mail notification configuration.

2.1.6.3
Modifying Alarm Filters
Procedure:
1 In the Navigation View panel, click the Alarms node.
2 From the main menu, select Edit → Alarm Filters.
3 In the Alert Filters window, select the alarm filter you want to modify.
4 Optional: In the Filter Name field, modify the filter name.
5 Optional: In the Match Criteria pane, modify the Managed Resource and Severity criteria.
6 Optional: Configure additional match criteria by clicking Advanced.
In the Match Criteria Properties dialog box, you can configure the following match criteria:
• Message
• Category
• Domain
• Network
• Node
• Failure Object
7 Optional: Configure a filter by using an alarm property that is not displayed on the user interface:
a In the Match Criteria Properties dialog box, click More Properties.
b In the Property Name and Property Value fields, specify filter properties. Click OK.
The value must be the same as the one listed in the Property name for the filtering column.
To modify an existing property, in the Property Name field, enter the same value again and
in the Property Value, enter a new value. To remove a property, in the Property Name field,
enter the same value again and leave the Property Value field blank.
c Close the More Properties dialog box. In the Match Criteria Properties dialog box, click
OK.

52
 MN002730A01-AD
Chapter 2: SA Configuration

8 In the Alert Filters window, click Apply. Click OK.

The window closes.

2.1.6.4
Alarms Filter by Managed Resource Device Category
You can filter alarms by the category of managed resource device.
The following table describes the different device categories:

Device Category Category description

RAN Infrastructure for Radio and Network
NM Basic network management components
(FCAPS)
Transport Transport infrastructure
Application Additional components in the system, not relat-
ed directly to its basic capabilities
Core Core equipment and applications in the system
Generic Generic or unknown device

2.1.6.5
Modifying Alarm Filter Notifications
Procedure:
1 In the Navigation View panel, click the Alarms node.
2 From the main menu, select Edit → Alarm Filters.
3 In the Alert Filters window, select the alarm filter you want to modify.

4 In the Actions List pane, click Add Action .

5 In the Add Action window, select the tab corresponding to the notification that you want to
modify.
• Trap
• Email
• Suppress
• Custom
6 From the Filter Action List, select the notification that you want to modify.
7 Edit the notification properties. Click Edit.

2.1.6.6
Loading Alarm Filter Files
Procedure:
1 In the Navigation View panel, click the Alarms node.
2 From the main menu, select Edit → Alarm Filters.
3 In the Alert Filters dialog box, click Load/Save.

53
MN002730A01-AD
Chapter 2: SA Configuration

4 In the Filter Details dialog box, specify the file name and click Load.
Any filters with the same match criteria are replaced with the alarm filters from your load file.

2.1.6.7
Deleting Alarm Filters
Procedure:
1 In the Navigation View panel, click the Alarms node.
2 From the main menu, select Edit → Alarm Filters.

3 In the Alert Filter dialog box, select the alarm filter you want to delete. Click Delete Filter .
4 In the confirmation dialog box, confirm the deletion by clicking Yes.
The alarm filter disappears from the list of alarm filters.

2.1.6.8
Deleting Alarm Filter Notifications
Procedure:
1 In the Navigation View panel, click the Alarms node.
2 From the main menu, select Edit → Alarm Filters.
3 In the Alert Filter dialog box, select the alarm filter whose notification you want to delete.
4 From the Actions List panel, select the notification you want to modify. Click Delete Action

.
5 In the confirmation dialog box, confirm the deletion by clicking Yes.
The notification disappears from the Actions List panel.

2.1.7
Event Filters Configuration
When an event is created, the occurrence of the event can be associated with some actions.
SA provides event filters to send e-mails to an administrator on occurrence of an event. This action is
called a notification. By configuring event filters you can filter events based on certain match criteria.
With this tool you can also add, modify, or delete filters and filter actions.
When events are generated from devices in a network, you can configure SA to send notifications to
users. Use event filters to configure SA to automatically initiate actions for selected events.
NOTICE:
The property name, when used for filtering, is case-sensitive and should be used exactly as
specified when typing in the name of the additional property criterion to filter on.
white space
empty space
> < & $ # ^ - " ' ""
a digit at the beginning of the name
* ! @ ( + ~ { [ | \ ; , . ? / % `
SA supports only the Sending e-mails built-in filter notification. Other notification types that can be
associated with the filter are suppressing events, running system command, sending custom trap, and
running custom code. Even though these notifications are available on the user interface, Sending e-

54
 MN002730A01-AD
Chapter 2: SA Configuration

mails is the only notification type recommended during filter configuration on SA. Do not add/delete or
modify other notification types. These notification schemes require advanced knowledge and privileges
and therefore are not recommended for general use. Contact Motorola Solution Support Center (SSC)
for information on the use of notification schemes other than e-mail notification scheme.
IMPORTANT: By default, SA is configured with a filter named TopoSupress and its associated
action named suppressTopoEvent to suppress some SA internal events. When configuring the
event filter, do not modify or delete the in-built TopoSupress event filter or suppressTopoEvent
action configuration. Modifying or deleting this in-built configuration may lead to incorrect
display of device statuses.

Match Criteria Property Overview

The managed resource and severity criteria determine whether the incoming alarm or event can be
filtered or not. If any field is left blank, it is not considered matching criteria. For the alarm or event filter
to be applied, it must satisfy all the match criteria specified. If even one of the criteria fails, the filter is
not applied. You can use wildcard characters and expressions to specify the match criteria.
SA accepts any match criteria you enter. However, if you want to make sure that your criteria are valid
for the system, enter them into a custom view. Criteria specified for custom views take immediate
effect, while an alarm or event filter only works when new alarms or events of the specified type occur.
Manage/Unmanage
Option that enables you to manage or unmanage SA resources. For example, you can unmanage
resources that are broken so that they do not send many traps to the trap buffer and take a lot of
the trap buffer capacity. After the resources are fixed, you can manage the fixed resources to
enable SA to receive traps from them.
Clean Trap Buffer & Sync
Option that enables you to clear the trap buffer of all traps SA received from a managed resource.
After the trap buffer is cleared, SA schedules synchronization with managed resources whose traps
you removed. As a result, SA receives up-to-date information from the managed resources.

2.1.7.1
Adding Event Filters
Procedure:
1 In the Navigation View panel, select Fault Management → Network Events.
2 From the main menu, select Edit → Event Filters.
The Actions List pane options become active.

3 In the Event Filters window, click Add Filter.

4 In the Filter Name field, specify the name of the filter.
5 In the Match Criteria pane, specify the Managed Resource and Severity criteria.
6 Optional: Configure additional match criteria by clicking Advanced.
In the Match Criteria Properties dialog box, you can configure the following match criteria:
• Message
• Category
• Domain
• Network
• Node
• Failure Object

55
MN002730A01-AD
Chapter 2: SA Configuration

7 Optional: Configure a filter by using an alarm property that is not displayed on the user interface:
a In the Match Criteria Properties dialog box, click More Properties.
b In the Property Name and Property Value fields, specify filter properties. Click OK.
The value must be the same as the one listed in the Property name for the filtering column.
To modify an existing property, in the Property Name field, enter the same value again and
in the Property Value, enter a new value. To remove a property, in the Property Name field,
enter the same value again and leave the Property Value field blank.
c Close the More Properties dialog box. In the Match Criteria Properties dialog box, click
OK.
8 In the Actions List pane, click Add Action.
9 In the Add Action window, add an action related to the notification.
A filter must have at least one notification associated with it.
10 Finish adding filters and notifications by clicking Apply. Click OK.

2.1.7.2
Configuring E-mail Notifications for Event Filters
You configure the e-mail notification to receive e-mails from SA about incoming alarms or events that
matches your filter criteria. You configure the e-mail notification by adding specific alarm or event
properties to your criteria.
In property names, do not use the following characters:
white space
empty space
> < & $ # ^ - " ' ""
a digit at the beginning of the name
* ! @ ( + ~ { [ | \ ; , . ? / % `

Procedure:
1 In the Navigation View panel, click the Network Events node.
2 From the main menu, select Edit → Event Filters.

3 In the Event Filters window, click Add Filter .

The Actions List pane options become active.

56
 MN002730A01-AD
Chapter 2: SA Configuration

Figure 15: Event Filters Window

4 In the Actions List pane, click Add Action .

5 In the Add Action window, click the Email tab.

57
MN002730A01-AD
Chapter 2: SA Configuration

Figure 16: Add Action Window – Email Tab

6 In the Notification Name field, enter the name of the e-mail notification. Click Configure.
Figure 17: SMTP Configuration Dialog Box
7 In the SMTP Configuration dialog box, enter the following account details:
a In the Account Name field, enter an SMTP account name.
b In the SMTP Server field, enter a server name.
c In the From Address field, enter a source e-mail address.
d In the To Address field, enter a target e-mail address.
e Optional: Enable obligatory authentication, select the Authentication Required check box.
Enter your user name and password.
f Click Add. Click OK.
8 Optional: Test the e-mail notification:
a In the Add Action window, from the SMTP Account list, select an SMTP account.

b In the Subject field, click Append Property and select the properties you want to
receive. Click Send Test Email.
In the Message field, a default message is added.

c In the confirmation window, click Yes.

SA sends a test notification to the specified e-mail address. The test notification does not
contain the properties that you specified in the e-mail notification configuration.

Configuring additional filter match criteria

58
 MN002730A01-AD
Chapter 2: SA Configuration

9 In the Alert Filters window, click Advanced.

10 Optional: In the Match Criteria Properties dialog box, configure the match criteria of your
choice.
You can configure the following match criteria:
• Message
• Category
• Domain
• Network
• Node
• Failure Object
Configuring filter properties that define what information you receive in the e-mail notifications
11 Configure a filter by using an alarm property that is not displayed on the user interface:
a In the Match Criteria Properties dialog box, click More Properties.
b In the Property Name and Property Value fields, specify filter properties. Click OK.
The value must be the same as the one listed in the Property name for the filtering column.
To modify an existing property, in the Property Name field, enter the same value again and
in the Property Value, enter a new value. To remove a property, in the Property Name field,
enter the same value again and leave the Property Value field blank.
c Close the More Properties dialog box. In the Match Criteria Properties dialog box, click
OK.

2.1.7.3
Modifying Event Filters
Procedure:
1 In the Navigation View panel, select Fault Management → Network Events.
2 From the main menu, select Edit → Event Filters.
3 In the Event Filters window, select the alarm filter you want to modify.
4 Optional: In the Filter Name field, modify the filter name.
5 Optional: In the Match Criteria pane, modify the Managed Resource and Severity criteria.
6 Optional: Configure additional match criteria by clicking Advanced.
In the Match Criteria Properties dialog box, you can configure the following match criteria:
• Message
• Category
• Domain
• Network
• Node
• Failure Object
7 Optional: Configure a filter by using an alarm property that is not displayed on the user interface:
a In the Match Criteria Properties dialog box, click More Properties.
b In the Property Name and Property Value fields, specify filter properties. Click OK.

59
MN002730A01-AD
Chapter 2: SA Configuration

The value must be the same as the one listed in the Property name for the filtering column.
To modify an existing property, in the Property Name field, enter the same value again and
in the Property Value, enter a new value. To remove a property, in the Property Name field,
enter the same value again and leave the Property Value field blank.
c Close the More Properties dialog box. In the Match Criteria Properties dialog box, click
OK.
8 In the Event Filters window, click Apply. Click OK.
The window closes.

2.1.7.4
Modifying Event Filter Notifications
Procedure:
1 In the Navigation View panel, select Fault Management → Network Events.
2 From the main menu, select Edit → Event Filters.
3 In the Event Filters window, select the alarm filter you want to modify.
4 In the Event Filters window, select the alarm filter you want to modify.

5 In the Actions List pane, click Add Action .

6 In the Add Action window, select the tab corresponding to the notification that you want to
modify.
• Trap
• Email
• Suppress
• Custom
7 From the Filter Action List, select the notification that you want to modify.
8 Edit the notification properties. Click Edit.

2.1.7.5
Loading Event Filter Files
Procedure:
1 In the Navigation View panel, select Fault Management → Network Events.
2 From the main menu, select Edit → Event Filters.
3 In the Event Filters dialog box, click Load/Save.
4 In the Filter Details dialog box, specify the file name and click Load.
Any filters with the same match criteria are replaced with the alarm filters from your load file.

2.1.7.6
Deleting Event Filters
Procedure:
1 In the Navigation View panel, select Fault Management → Network Events.
2 From the main menu, select Edit → Event Filters.

60
 MN002730A01-AD
Chapter 2: SA Configuration

3 In the Alert Filter dialog box, select the alarm filter you want to delete. Click Delete Filter .
4 In the confirmation dialog box, confirm the deletion by clicking Yes.
The event filter disappears from the list of event filters.

2.1.7.7
Deleting Event Filter Notifications
Procedure:
1 In the Navigation View panel, select Fault Management → Network Events.
2 From the main menu, select Edit → Event Filters.
3 In the Event Filter dialog box, select the alarm filter whose notification you want to delete.
4 From the Actions List panel, select the notification you want to modify. Click Delete Action

.
5 In the confirmation dialog box, confirm the deletion by clicking Yes.
The notification disappears from the Actions List panel.

2.2
Account Management
SA accounts are managed by administrators.
The administrators assign privileges to users and groups. In SA, there are pre-configured groups and
user accounts that cannot be deleted.

Account Management Functions

The primary function of the SA administrators is the management of SA users and their privileges.
Privilege assignments are primarily used to enable authentication and authorization services on SA.
The account management function includes the management of the following items:
User
A System Advisor user configured for performing operations on the system.
Group
A logical set of configured users who access common information or perform similar tasks.
Administration settings of a group apply to individual members or users of the group.
Operation
A task or a function allowed in SA.

Pre-Configured Groups
By default, SA is pre-configured with groups that cannot be deleted. If you attempt to delete any of
these groups, an error message appears. The pre-configured groups are:
SuperUser
A user responsible for day-to-day monitoring and administration of the Radio System.
SecurityAdmin
A user responsible for the creation and maintenance of user accounts.
Motorola Solutions Systems Support Center (SSC)
A user responsible for the administration of the Motorola Solution Support Center (SSC) accounts
on the customer system.

61
MN002730A01-AD
Chapter 2: SA Configuration

TechnicianGroup
A user responsible for troubleshooting issues within the Radio System.

Pre-Configured Users
By default, SA is pre-configured with default user accounts that cannot be deleted. If you attempt to
delete any of the default user accounts, an error message appears. The pre-configured default user
accounts are:
root
A user account with the SuperUser role assigned.
admin
A user account with the SecurityAdmin role assigned.
sscadmin
A user account with the Motorola Solutions Systems Support Center (SSC) role assigned.
technician
A user account with the TechnicianGroup role assigned.

2.3
Inbound and Outbound Communication Credentials
Configuration
The configuration of inbound and outbound credentials includes the configuration of Simple Network
Management Protocol version 3 (SNMPv3), WebService, and North Bound Interface (NBI).

2.3.1
SNMPv3 Credentials Configuration
SA supports SNMPv3 communication to the network elements and Network Management System
(NMS).
SNMPv3 credentials that are used for:
• Outbound communication to the devices
• Inbound communication from the devices
• Communication with NMS by using North Bound Interface (NBI)
By default, SA restricts configuration of SNMPv3 credentials for those three types of communication to
the SuperUser and SecurityAdmin groups. The configuration of Motorola Solution Systems Support
Center (SSC) NBI SNMPv3 credentials (MotoNorthMotorola) is restricted to users belonging to the
Motorola Solutions Systems Support Center (SSC) group only.
There are three types of SNMP credentials configuration:
• Global SNMPv3 credentials configuration
• Network element SNMPv3 credentials configuration
• Discovery session SNMPv3 credentials configuration
Network element SNMPv3 credentials can be configured after the network element/device has been
successfully discovered.
NOTICE: If credentials for the discovery job were not configured, network elements are
discovered with Global MotoMaster SNMPv3 credentials.

62
 MN002730A01-AD
Chapter 2: SA Configuration

2.3.1.1
Updating Global SNMPv3 Credentials for the MotoMaster User
Update the global SNMPv3 credentials for communication by modifying the MotoMaster user
credentials. Credentials that you can update for the MotoMaster user are the following security levels:
NoAuthNoPriv
A security level with no authentication and privacy passphrases defined.
AuthNoPriv
A security level with an authentication passphrase defined but with no privacy passphrase.
AuthPriv
A security level with authentication and privacy passphrases defined.

Procedure:
1 From the main menu, select Tools → Configure Global SNMPv3 Credentials.
The

2 In the Configure Global SNMPv3 Credentials dialog box, select MotoMaster. Click Update
Credentials.
The Update Credentials dialog box appears.
Figure 18: Update Credentials Dialog Box

3 In the Update Credentials dialog box, select the security level that you want to update:
• NoAuthNoPriv
• AuthNoPriv
• AuthPriv
4 Modify a security level. Click Update.

63
MN002730A01-AD
Chapter 2: SA Configuration

NOTICE: No passphrase fields are needed with the NoAuthNoPriv security level. Fill the
Authentication Passphrase fields for the AuthNoPriv security level. Fill both the
Authentication Passphrase and the Privacy Passphrase fields for the AuthPriv
security level.

2.3.1.2
Updating Global SNMPv3 Inform Credentials
Update global SNMPv3 credentials for inbound communication by modifying the MotoInformA or
MotoInformB user credentials.

Procedure:
1 Log on to SA as admin, security admin or any user who can change credentials.
2 From the main menu, select Tools → Configure Global SNMPv3 Credentials.
The Configure Global SNMPv3 Credentials window appears, displaying the default
credentials.

3 Select MotoInformA or MotoInformB inform users and click Update credentials.

Update Credentials window appears.

4 Modify the security level information and click Update.

NOTICE: No passphrase fields are needed with the NoAuthNoPriv security level. Fill the
Authentication Passphrase fields for the AuthNoPriv security level. Fill both the
Authentication Passphrase and the Privacy Passphrase fields for the AuthPriv security
level.

2.3.1.3
Updating the Network Element SNMPv3 Credentials
You update the network element SNMPv3 credentials for outbound communication by changing the
MotoMaster credentials for a specific network element. Credentials that you can update for the
MotoMaster user are the following security levels:
NoAuthNoPriv
A security level with no authentication and privacy passphrases defined.
AuthNoPriv
A security level with an authentication passphrase defined but with no privacy passphrase.
AuthPriv
A security level with authentication and privacy passphrases defined.

Procedure:
1 In the Navigation View panel, highlight the Network Database node.
2 In the Network Database window, right-click a network element and select Update SNMPv3
Credentials.
3 In the Update SNMPv3 Credentials dialog box, select MotoMaster. Click Update Credentials.
The Update Credentials dialogue box appears.

4 In the Update Credentials dialog box, select the security level that you want to update.
5 Modify a security level. Click Update.
• For the NoAuthNoPriv security level, make no passphrase updates.
• For the AuthNoPriv security level, update the Authentication Passphrase pane.

64
 MN002730A01-AD
Chapter 2: SA Configuration

• For the AuthPriv security level, update the Authentication Passphrase and Privacy
Passphrase panes.

2.3.1.4
Testing any Device SNMPv3 Configuration
Testing the SNMPv3 configuration of devices involves communication with the MotoMaster user only.
Other SNMPv3 users do not participate in this configuration test.

Procedure:
1 From the main menu, select Tools → Test Any Device SNMPv3 Configuration.
The Test Any Device SNMPv3 Configuration dialog box appears.

2 In the IP Address or Hostname field, enter the IP address of the device you want to test. Click
Start.
The status of the request appears in the status bar.

2.3.1.5
Testing SNMPv3 Communication Between Network Elements and SA
Procedure:
1 In the Navigation View panel, click the Network Database node.
2 In the Network Database view, right-click a managed resource, and select Test SNMPv3
Configuration.
3 In the Test SNMPv3 Configuration dialog box, click Start.
The IP Address and Hostname field is populated automatically.
The status of the request appears in the status bar.

2.3.2
Web Service Credentials Configuration
SA supports communication with Web Service over Simple Object Access Protocol (SOAP). SA is
configured with default Web Service credentials.
Web Service credentials are used for outbound communication to the devices. Neither the SA server
nor the SA client exposes any Web Service, so no configuration for inbound traffic is necessary. By
default, SA restricts configuration of Web Service credentials to the members of the SuperUser and
SecurityAdmin groups.
By using Web Service, the following network elements can be managed through CMSS (using VMware
vSphere Web Services)
Configuring Web Service credentials can be classified into three types:
• Global Web Service credentials configuration
• Network element-specific Web Service credentials configuration
• Web Service credentials for a discovery session
NOTICE: Web Service is also used to communicate to the CMSS server for fault management.

65
MN002730A01-AD
Chapter 2: SA Configuration

2.3.2.1
Changing Global Web Service Credentials for the MotoMaster User
You can change the Web Service credentials for outbound communication, by updating the
MotoMaster user credentials.

Procedure:
1 From the main menu, select Tools → Configure Global Web Service Credentials.
2 In the Configure Global Web Service Credentials dialog box, modify the authentication
passphrase. Click Update.

2.3.2.2
Updating Network Element Web Service Credentials
You can configure the credentials of network element-specific Web Service after the successful
discovery of a network element or device.

Procedure:
1 In the Navigation View panel, click the Network Database node.
2 In the Network Database window, right-click a network element and click Update Web Service
Credentials.
3 In the Update Web Service Credentials dialog box, modify the password. Click Update.

2.3.2.3
Testing any Device Web Service Configuration
Procedure:
1 From the main menu, select Tools → Test Any Device Web Service Configuration.
The Test Any Device Web Service Configuration dialog box appears.

2 In the IP Address or Hostname field, enter the IP address of the device you want to test. Click
Start.
The status of the request appears in the status bar.

2.3.2.4
Testing the Web Service Communication Between Network Elements and
SA
Procedure:
1 In the Navigation View panel, click the Network Database node.
2 In the Network Database view, right-click a managed resource, and select Test Web Service
Configuration.
3 In the Test Web Service Configuration dialog box, click Start.
The IP Address and Hostname fields are populated automatically. The status of the request
appears in the status bar.

66
 MN002730A01-AD
Chapter 2: SA Configuration

2.3.3
Configuring North Bound Interface
System Advisor (SA) supports North Bound Interface (NBI) for sending up notifications to the
registered Manager of Managers (MoM). Currently, there are two interfaces that are supported. NBI
uses SNMPv3 and the User-Based Security Model (USM) to provide secure communication between
SA and Network Management System (NMS). The customer NBI MoM interface is a licensed SA
service that is available only for users with a feature license for the NBI service. The SA supports
configuration of two NBIs.

Procedure:
1 From the main menu, select Tools → Configure North Bound Interface.
2 In the NBI Configuration dialog box, click Register NMS.
3 In the Register NMS dialog box, perform the following actions:
a In the NMS IP Address field, enter the IP address of the NMS to which you want to send the
events.
b In the Port Number field, enter the port number of the NMS to which you want to send the
events.
c From the Operational state list, select Enabled.
NMS can receive events.
d Optional: Verify the NMS IP address by clicking Send test trap.
e Click Register.

2.4
Discovery Job Credentials Configuration
With permissions to configure the MotoMaster credentials and to perform a discovery, you can
configure and disable credentials for a single discovery job.
You can configure Web Service and SNMPv3 discovery job credentials for a discovery job.

2.4.1
Configuring Discovery Job Credentials
When you initiate a discovery job with custom credentials set, the credentials are used to discover new
devices and rediscover existing devices. Existing credentials for discovered devices are overwritten
and rediscovery is performed.
If this rediscovery fails due to a credentials mismatch, additional rediscovery with the proper
credentials set may be needed.
When you start a discovery job with custom credentials, settings in the Update Credentials window
are not set back to their default values as long as the Discovery Configuration window remains open.
This allows you to start multiple discovery jobs with the same customized credentials set.

Procedure:
1 From the main menu, select Tools → Discovery.
2 In the Discovery Configuration window, click Credentials.
3 In the Update Credentials window, perform one of the following actions:

67
MN002730A01-AD
Chapter 2: SA Configuration

If… Then…
If you want to dis- perform the following actions:
cover an SNMPv3 a In the SNMPv3 tab, select the Use the following credentials
device, check box.
b From the Security Level list, select a SNMPv3 security level.
c Enter the respective passphrases. Click OK.

If you want to dis- perform the following actions:

cover a Web Service a In the Web Service tab, select the Use the following creden-
device, tials check box.
b Enter the respective passphrases. Click OK.

If the Use the following credentials check box is selected for either SNMPv3 or Web Service, in the
header of the Discovery Configuration window, a message appears informing you that the
customized credentials apply to devices discovered in earlier and recent discoveries.

2.4.2
Disabling Discovery Job Credentials
After you configure discovery job credentials, you can restore their default values.
Prerequisites: Configure discovery job credentials.

Procedure:
1 From the main menu, select Tools → Discovery..
2 In the Discovery Configuration window, click Credentials.
3 In the Update Credentials window, perform one of the following actions:
• To disable discovery credentials of an SNMPv3 device, in the SNMPv3 tab, clear the Use
the following credentials check box. Click OK.
• To disable discovery credentials of a Web Service device, in the Web Service tab, clear the
Use the following credentials. Click OK.
4 In the Discovery Configuration window, click Close.
Discovery job credentials are restored to their default values.

68
 MN002730A01-AD
SA Operation

Chapter 3

SA Operation
Operation procedures help you work with SA.

3.1
Starting the SA Client
You can access the System Advisor (SA) through a web browser by establishing a connection with the
SA server and launching the SA client.
Prerequisites: System Advisor (SA) requires the latest version of Oracle Java 8 32-bit (at least
1.8.0_66). SA can be launched using Microsoft Internet Explorer (IE 11 or higher), the latest version of
Google Chrome or Mozilla Firefox web browser.

Procedure:
1 Launch the web browser, then enter: https://<IP_OF_SA_SERVER>:9090
The launch page displays a list of the available System Advisor instances and indicates their
activity states. The local instance determined by the IP address that you entered in the web
browser appears on top.
Figure 19: Launch Page

2 Click the Launch Client button for the System Advisor that you want to launch.
• If the Security Warning dialog box appears, select the I accept the risk and want to run
this application check box. Click Run.
• If you are requested to accept the SSL certificate, accept it.
The SA client console appears. A splash screen with a status bar is shown and the SA client user
interface appears.

69
MN002730A01-AD
Chapter 3: SA Operation

3.2
Work Area Overview
Follow procedures in this section to navigate through the SA application and to perform basic SA
operations.

3.2.1
Work Area Operations
This section provides information on basic SA operations.

3.2.1.1
Navigating Through Active Windows
When many windows are open in the display panel, you can easily navigate to the next or the previous
active screen.

Procedure:
Navigate to a window:
• To go back to the previous window, from the File menu, select Back.
• To go to the next window, from the File menu, select Forward.
The window appears.

3.2.1.2
Detaching a Window from the Client
You can detach a window from the display panel of the SA client and view it as a separate window.

Procedure:
In the Window menu, select Detach Current Window.
You restore the window to its default position by closing the detached window.

3.2.1.3
Arranging Windows
Procedure:
Arrange windows horizontally, vertically, or as a cascade of windows:
• To tile all open windows horizontally, from the Window menu, select Tile Windows
Horizontally.
• To tile all open windows vertically, from the Window menu, select Tile Windows Vertically.
• To display a cascade of all open windows, from the Window menu, select Cascade.
Windows are arranged according to your requirements.

3.2.2
Work Area Components
Title Bar
The title bar displays the user logged on and shows the activity state of this System Advisor (SA)
instance.

70
 MN002730A01-AD
Chapter 3: SA Operation

Menu Bar
A rectangular component that is positioned at the top edge of the display area. By clicking the menu
and selecting a particular menu item, the associated function can be performed.
The menu bar differs from screen to screen, based on the functions and on your privileges as a
user. For instance, the Fault Management module has additional menu items, such as Actions and
Custom Views. However, certain menu items, such as File, Edit, Tools, Window, and Help are
common for the entire SA client.
Toolbar
A component that displays a collection of actions, commands, or control functions; useful to display
the frequently used components. It is placed below the menu bar and consists of various tools for
different nodes. A tool tip is provided for each tool, which indicates the operations performed by
them.
To hide the toolbar, perform one of the following steps:
• Click the icon with the tool tip Hide Toolbar.
• From the Window menu, select Show Toolbar.
The toolbar differs from screen to screen, based on the functions of the module. For example, the
Fault Management node provides such toolbar options as Add Custom View or Modify Custom
View. Toolbar options, such as Go Back to Previous, Go Forward to Next, and Help, are
common for the entire SA client.
Navigation View (Navigation Tree)
The tree present on the left-hand side of the SA client displays a set of hierarchical data. The
fundamental object in a tree is called a node, which represents a data item in a given hierarchical
set. The root node is the top node of the hierarchical data. Nodes inside the root nodes are called
child nodes. Nodes that contain no child nodes are called leaf nodes. When you select a particular
node, the corresponding window is displayed on the right-hand side display panel. However for Grid
View under Call Monitoring, there is also an option to open more Grid Views in a Web browser. In
the case of Raw View, clicking the Raw View node always opens the Raw View in a browser.
Alarm Summary View
An overall summary of the alarms that can be viewed. It is based on severity. The Alarm Summary
View panel is located below the Navigation View panel. When you click the count displayed in the
Alarm Summary View panel, the alarms of specific severity are displayed in the corresponding
Alarm panel. This panel is updated automatically. The counts can be seen all the time, regardless
of the functional view.
Status Bar
The status bar is displayed at the bottom of the window. It indicates the status of ongoing
processes.
Display Panel
The display panel is displayed on the right-hand side of the SA client and appears as a window
within the main window. This panel is shown when a tree node is selected. For example, if you
select Fault Management → Network Events in the navigation tree, the Events display panel is
displayed on the right-hand side.

3.2.3
Broadcasting Messages
Procedure:
1 From the main menu, select Tools → Broadcast Message.
2 In the Message field, enter the message you want to broadcast. Click Broadcast.

71
MN002730A01-AD
Chapter 3: SA Operation

3 In the pop-up window with your message, click OK.

The message is delivered to the clients that are connected to the SA server.

3.2.4
Table View Operations
The Table view panel displays details of various application elements, for example alarms and events.
Table view is available on the right-hand side of the SA client for elements in the Fault Management,
Network Database, and Configured Collections nodes.

3.2.4.1
Table Navigation
The table views are available only in the Fault Management, Network Database, and Configured
Collections nodes.
The navigator buttons, First Page, Previous Page, Next Page, and Last Page are located at the top
of each table.
First Page
The first page of the window that displays the data retrieved from the database.
Previous Page
The previously viewed page of the window that displays the data retrieved from the database.
Next Page
The next page of the window frame that displays the data retrieved from the database.
Last Page
The last page of the window that displays the data retrieved from the database.

3.2.4.2
Setting the Page Length
For Navigation View panel elements that belong to the Fault Management and Network Database
nodes, you can set the number of table rows that are displayed. This option is available to all users and
helps you adjust the views to your needs.

Procedure:
In the Page Length drop-down menu, select the number of rows you want to display.
The table displays the desired number of rows.

3.2.4.3
Sorting Table Details
All users can sort the data in a table based on the column type. The details can be viewed either in
ascending or descending order. Arrows indicate the type of sorting order (ascending or descending).
There are two types of sorting:
Server-side sorting
Sorts all data in the SA server and is not restricted to the data available in the SA client.

72
 MN002730A01-AD
Chapter 3: SA Operation

Client-side sorting
Sorts data displayed only in the SA client. For example, if there are 50 alarms in the SA server and
only 25 are displayed on the SA client, the table sorts only the 25.

Procedure:
1 Sort your table details.
• To sort the data, click the column header.
• To sort the data in reverse order, click the same header once again.

NOTICE: When you sort the column header on the client side, hold CTRL.

3.2.4.4
Rearranging and Resizing Table Columns
You can modify table columns according to your preferences. After you modify table columns, your
settings remain unchanged until the SA client is open. When you reopen the SA client, your settings
are lost.

Procedure:
• Rearrange the columns by dragging the column header and moving it to the desired place in the
table.
• Resize the column header by dragging the right edge of a column.
• Optional: Retain the same size of columns, by selecting Custom Views → Save Custom View
State.
IMPORTANT: When you save a custom view, only the column size is saved and the
rearrangement is lost. The custom view is displayed in the default order.

3.2.5
Custom View Operations
In SA, custom views are tailored views that you can create to display a subset of data that satisfies
specific criteria.
You can use custom views, for example, to monitor a specific group of managed resources; instead of
performing search on the resources multiple times, you can define a custom view for them.
You can create custom views in the Network Events, Alarms, Network Database, and Configured
Collection windows. You can create custom views only if your account is privileged to do so. For
information about your user privileges, contact your system administrator.
You can open up to six Network Events custom view windows. When you open another Network
Events custom view window, the Network Events custom view window opened as the first one
closes.
When creating or renaming custom views, note that only alphanumeric characters, spaces and
underscores are allowed.

73
MN002730A01-AD
Chapter 3: SA Operation

3.2.5.1
Adding Custom Views
You can add or create a view by specifying various criteria and providing a name for the view. The
views you create allow you, for example, to quickly monitor only the devices you need.

Procedure:
1 In the Navigation View panel, click one of the following nodes:
• Network Events
• Alarms
• Network Database
• Configured Collection
2 From the main menu, select Custom Views → Add Custom View.
3 In the Show objects with these Properties dialog box, specify the object properties you want
to use to filter the data.
IMPORTANT: Custom view names, that you can modify in the Filter View Name field,
are not case-sensitive. On the same custom view tree level, you cannot add two custom
view names whose names differ only by the size of letters. You can add such custom
view names on different custom view tree levels.
4 Optional: Specify the columns you want to view:
a In the Show objects with these Properties dialog box, click Select Props To View.
The Select Table Columns dialog box appears. The selected fields are the columns that you
see in your table view.

b In the Select Table Columns dialog box, specify the columns you want to view by selecting
or clearing check boxes next the column names. Click OK.
You can also define new columns by clicking Additional table columns.
5 In the Show objects with these Properties dialog box, click Apply Filter.
NOTICE: Within this master view, you can create more views, such as child views M1
and M2. Deleting the master view deletes its child views M1 and M2.
A new node with the custom name you have configured is created on the tree. When you click it, your
custom view is displayed on the display panel.

3.2.5.2
Modifying Custom Views
You can modify a custom view to expand or limit the amount of information it displays. Follow this
procedure to modify custom view properties, not custom view names.

Procedure:
1 In the Navigation View panel, right-click a user-defined custom view under one of the following
nodes:
• Network Events
• Alarms
• Network Database
• Configured Collection

74
 MN002730A01-AD
Chapter 3: SA Operation

2 Select Custom Views → Modify Custom View.

The Show object with these Properties dialog box appears.

3 In the Show object with these Properties dialog box, modify the match criteria you want to use
to filter the data.
4 When you have modified the match criteria, click Apply Filter.

3.2.5.3
Renaming Custom Views
You can rename custom views to make them more meaningful.
NOTICE: Custom view names are not case-sensitive. You cannot add two custom view names
whose names differ only by the size of letters on the same custom view tree level. You can add
such custom view names on different custom view tree levels.

Procedure:
1 In the Navigation View panel, click a user-defined custom view under one of the following
nodes:
• Network Events
• Alarms
• Network Database
• Configured Collection
2 From the main menu, select Custom Views → Rename Custom View.
The custom view name is editable. To quit the custom view name edit field, press ESC.

3 Modify the custom view name. Press ENTER.

The name cannot exceed the limit of 50 characters.

3.2.5.4
Moving Custom Views
Procedure:
1 In the Navigation View panel, expand the Network Events node and click the custom view
node that you want to move.

75
MN002730A01-AD
Chapter 3: SA Operation

Figure 20: Navigation View Panel – Custom View

2 Move the node by using one of the action icons available on the toolbar:

• Move the custom view to the first position by using the Move to the Top icon .

• Move the custom view up by using the Move Up icon .

• Move the custom view down by using the Move Down icon .

• Move the custom view to the last position by using the Move to the Bottom icon .

3.2.5.5
Saving Custom Views
You can configure filter criteria during the configuration of custom views by using the properties. If the
property is not available in the filter configuration user interface, use the mechanism provided to add
more properties to the filter criterion. The name used for the additional property should match,
including case-sensitivity, the name specified in the Property name for filtering column of the table in
Managed Resource Properties.

Procedure:
1 In the custom view, from the Custom Views menu, select Save Custom View State.
2 In the main navigation tree, right-click a custom view under the Network Events, Alarms or
Network Database node and select Custom Views → Save Custom View State.
A message appears in the status bar informing that the custom view has been saved.

76
 MN002730A01-AD
Chapter 3: SA Operation

3.2.5.6
Deleting Custom Views
You can delete single custom views or parent custom views in which other custom views are nested.
When you delete a parent custom view, you also delete all the child custom views that are nested in it.
For example, you create a custom view named Master (parent) and nest in it more custom views
named M1 and M2. When you delete the Master custom view, you also delete the M1 and M2 child
custom views.

Procedure:
1 Open the custom view you want to delete.
2 In the Custom Views menu, select Remove Custom View.
A confirmation dialog box appears.

3 To remove the custom view, click Yes.

The custom view and the tree node are deleted.

3.2.5.7
Exporting Custom Views
You can export your custom views to a .cv file and import them to another client application. Custom
views are structured hierarchically and displayed in the form of a tree. The structure of your exported
custom views depends on which custom views you select.

Procedure:
1 In the Navigation View panel, select one of the following nodes:
• Network Events
• Alarms
• Configured Collection
• Network Database
2 From the main menu, select Custom Views → Export Custom View.
3 In the Export Custom Views dialog box, select check boxes corresponding to custom views
that you want to export. Click OK.
4 In the Save Custom View(s) File dialog box, select a destination folder. Click Save.
A .cv file with custom views is saved in the selected folder. You can use the file to import the custom
views.

3.2.5.8
Importing Custom Views
You can import your custom views from a .cv file. Custom views are structured hierarchically and
displayed in the form of a tree. You can import single custom views or the whole structure of your
exported custom views.

Procedure:
1 In the Navigation View panel, select one of the following nodes:
• Network Events
• Alarms
• Network Database

77
MN002730A01-AD
Chapter 3: SA Operation

• Configured Collection
2 From the main menu, select Custom Views → Import Custom View.
3 In the Open Custom Views File dialog box, select a .cv file with custom views you want to
import. Click Open.
4 In the Import Custom Views dialog box, select check boxes corresponding to custom views
that you want to import. Click OK.
CAUTION: If a custom view of the same name as any of the ones you import exists in
the same hierarchy, name conflict information is displayed in the dialog box in red. If you
continue to import this custom view, the custom view on the client is overwritten.
Selected custom views from the .cv file are imported.

3.2.6
Filtering Quick Reference
Most of the properties listed while adding a custom view are string-based. Some of the properties can
be displayed with a drop-down list. A single value can be selected from the drop-down list. Multiple
values can be typed in by using the operators and expressions available for filtering. When you choose
all, the property is not included.
String-based property values are case-sensitive. For example, the string Router matches the exact
word with capital R only.
Expressions like Status or Severity are also treated as strings. Hence, for a filter of Alarms with critical
severity, specify crit*.
Leave unnecessary fields blank.
Depending on the total number of objects/elements, the complexity of the filter criteria, and the mode of
storage, the time taken for filtering varies. Custom views continue to be updated and navigable for
additions/deletions until the SA client is closed. You can either save your views or remove them.

3.2.6.1
Wildcard Characters for Filtering
You can use wildcard characters to define filtering expressions. Except for <between>“value1”
and “value2”, the expressions that you create by using wildcard characters should include no
spaces between the value and the wildcard characters or operators. For example, the expression abc*
&& *xyz is invalid. A valid definition for this expression is abc*&&*xyz.
* (Asterisk)
It is used to match zero or more characters. The character works only for text strings. Example:
• To view all objects whose names start with test, enter: test*
• To view all objects that end with com, enter:*com
! (Exclamation Mark)
It is used for filtering the search using the NOT operand. The character works only for text strings.
Example:
• To view all objects whose names do not start with test, enter: !test*
• To view all alarms except the ones with the warning severity, enter: !war* (or) !warning
, (comma)
It is used for specifying multiple criteria for the same property. It is the equivalent of the OR
operand. The character works only for text strings. Example: To view objects named nms-server1,
nms-server2, or nms-server3, enter: nms-server1,nms-server2,nms-server3

78
 MN002730A01-AD
Chapter 3: SA Operation

&& (two ampersands)

It is used to match a single value with many patterns. It is the equivalent of the AND operand. The
character works only for text strings. Example: If all the objects with names starting with abc and
ending with xyz are required, enter: abc*&&*xyz
<between>“value1” and “value2”
It is used to get objects with some numeric values within a specific range. Example: If object names
with poll interval value ranging from 300 to 305 is required, enter: <between>300 and 305

3.2.6.2
Examples of Filtering with Wildcard Characters

Table 3: Filtering Site Trunking Condition Example

Filter-site trunking condition due to site control path or core router failure on all Repeater sites.
Temporarily exclude Repeater site 5 which is being upgraded. Filter on the following two fields:

Field Value
identifier isr_site_fault:51.6,isr_site_fault:51.11
source *:Rptr_Site&&!*X.X.X:Rptr_Site
For exact values for <X>, see your System Configuration Plan.

Table 4: Filtering Transient Illegal Carrier Events Example

Filter transient illegal carrier events from channel 5 (High Performance Data (HPD)) and channel 21
(Repeater) at host site 32. Include a special note. Filter on the following three fields:

Field Value
identifier Transient*receiver_fault.1
entity name Channel 5,Channel 21
source *X.X.X:*Site
For exact values for <X>, see your System Configuration Plan.

Table 5: Filtering Station alarms on Chosen Sites Example

View all station (Base Radio) alarms on site1. View all station alarms on site2 except stations 2 and 10.
View all station alarms on site 3. Filter on the following value:

Field Value
source X.X.X.*BaseRadio,X.X.X.*BaseRadio&&!X.X.X.X:*&&!
X.X.X.X:*,X.X.X.*BaseRadio
For exact values for <X>, see your System Configuration Plan.

3.3
Active Users Operations
Administrators can view the list of current active SA clients.
SA responds to the request by displaying the list of current active users who are logged on in the SA
client web interface. You access the system administration panel by selecting Administration →
System Administration from the main menu

79
MN002730A01-AD
Chapter 3: SA Operation

Figure 21: System Administration – SA Client Web Interface

3.3.1
Viewing the Active SA Clients List
Procedure:
1 From the main menu, select Administration → System Administration.
2 In the Monitor/Management pane, click JVM Management.
3 In the SA JVM Management window, select the Client Details tab.
Figure 22: Client Details – SA Client Web Interface

4 Optional: Terminate client sessions by clicking Terminate for a client.

SA displays the list of current active clients.

3.4
Site Operations
The site and its associated devices can be discovered using the Site/Network discovery tab in the
Discovery Configuration user interface.
The Site ID, Agent Port and Netmask are used to determine the list of devices for which discovery is
attempted. Set up the SNMPv3 configuration to match the configuration of the devices at the Site.

80
 MN002730A01-AD
Chapter 3: SA Operation

3.4.1
Deleting Sites
This procedure explains how to remove the site devices and service resources associated with a site
subnet being deleted.

Procedure:
1 In the Network Database window, right-click the Site group managed resource and select
Delete Object and Traces.
2 In the confirmation dialog box, click Yes.
If a site that is still present and active in the system is being deleted, System Advisor (SA) will
discover devices from this site again after some time.
3 In the Deletion Status dialog box, click View Job Status.
A separate job is initiated for each deletion request. The status of the request appears in the
Job Status View window.
4 In the Job Status View window, verify the deletion status.
Figure 23: Job Status View Window

NOTICE: If you delete a single network, the network name appears in the Target column
in the Job Status View window. If you delete multiple networks, Multiple nodes message
appears in the Target column.
If the job status is Success or Completed the device/node and the alarms associated with it are also
deleted. Events are not deleted, because events are part of the history and they are deleted only when
the database is reinitialized.

3.4.2
Deletion Status
Deletion job status is displayed in the Job Status View window.
In progress
The job submission recognized and is in the queue. To determine, whether the job has started
executing and to get information about the progress, view the job log.
Success
The deletion job completed successfully. All devices/nodes scheduled for deletion have been
deleted. The Additional Comments field and detailed information is available in the job log.
Completed
The deletion job completed, but not all devices/nodes scheduled for deletion have been deleted;
during the deletion process, devices/nodes were not present in the database. Detailed information
is available in the job log.

81
MN002730A01-AD
Chapter 3: SA Operation

Failure
The deletion job failed. The job terminated incorrectly, because a deletion failed for one or more
devices/nodes. Detailed information is available in the job log.

3.5
Administration Tools
This section captures information about the Policies and the View Job Status features of SA.
Policies
A set of rules predefined against an activity; for example, a policy can be written for archiving
events and viewing job status.
Viewing job status
The Job Status View provides user feedback and status of jobs initiated.

3.5.1
Policies Overview
Policies are a set of predefined rules.
Policies can be triggered as:
• Non-periodic action (policy can be scheduled for specified date and time)
• Periodic action (server application performs an action at regular intervals, defined in seconds)
SA defines and supports ten predefined policies. All predefined policies are described by custom
parameters

3.5.1.1
Policies Description

Table 6: Policies Description

The following parameters are defined for all predefined policies.

Policy Description Additional Parameters

Archive cleanup (Archi-
veCleanupPolicy)
Audit Trails cleanup
(AuditTrailsCleanupPo-
licy)
A pre-defined policy to periodical- Min Event Storage Size
ly remove from the archive data- Minimum number of events, that
base events that are older than should be retained during clean-
given time. up.
Min Event Storage Period
The time events can exist in the
archive database (in days).
A pre-defined policy to periodical- N/A
ly remove audit trails from the da-
tabase and save them to
the /opt/Motorola/nms/
logs/
archivedAuditTrails/
audit- Trails.csv file. Audit
trails are removed in the following
situations:
• If they are more than a year
old

82

Policy Description
• If their number exceeds
200,000, the most recent
100,000 audit trails are kept,
while the older ones above
this limit are removed.
Cleared Alarm cleanup A pre-defined policy to periodical-
(AlarmCleanupPolicy) ly clean up alarms with the clear
severity. The cleaned alarms are
no longer displayed in the
Alarms window.
MN002730A01-AD
Chapter 3: SA Operation
Additional Parameters
Clear Alarm Cleanup Delay
The time (in seconds) counted
from the last modification of
alarm time. As a result of the
modification, alarms with the
clear severity are listed in the
Alarms window. After the set
time passes, the alarms are re-
moved from the Alarms window
during the next policy execution.
The default time value is one
hour, that is 3600 seconds. The
minimum time value is 15 mi-
nutes, that is 900 seconds. The
maximum time value is 24
hours, that is 86400 seconds.
Period
The time (in seconds) in which
the policy is executed. Period is
always 15 minutes and it starts
when the fault manager server is
enabled.
Example 1: The fault manager
server is enabled at 8.12 a.m.; the
policy execution starts. The clear
alarm cleanup delay is set to one
hour. An alarm is set to the clear
severity at 8.28 a.m. Because peri-
od is set to 15 minutes, policy is
run six times to remove all cleared
alarms. Time of the policy execu-
tion: 8.27, 8.42, 8.57, 9.12, 9.27,
9.42.
At 9.42 a.m. the alarm set to the
clear severity at 8.28 is removed
from the Alarms window.
Example 2: For the same condi-
tions as in example 1, except with
the clear alarm cleanup delay set
to 15 minutes, the alarm set to
clear severity at 8.28 a.m. is re-
moved from the Alarms window at
8.57 a.m.
83
MN002730A01-AD
Chapter 3: SA Operation
Policy Description
Events cleanup (Even- A pre-defined policy to periodical-
tCleanupPolicy) ly remove the oldest current
events when their number ex-
ceeds the configurable maxE-
ventNumber parameter value.
Event archive and A pre-defined policy to periodical-
purge (EventLogging- ly archive events from the SA
Policy) event database to a file on the
SA server application. This policy
also periodically purges the ar-
chived events from the SA event
database.
Export Events to CSV A pre-defined policy to periodical-
File (EventLoggingPoli- ly copy the latest events to
cy) a .csv file and compress
old .csv files to .zip archives.
Export Statistical Data A pre-defined policy to periodical-
to CSV File (StatsDa- ly archive collected statistics from
taExport- Policy) the SA StatsData database to
a .csv file on the SA server ap-
plication. This file is then archived
and stored.
Jobs View Cleanup A pre-defined policy to periodical-
(JobsCleanupPolicy) ly clean up the completed jobs
from the SA Job Status View. All
jobs with End Time older than 24
hours and with status Failure or
Success or Aborted will be delet-
ed from Job View and archived
on SA server for 30 days.
NBI File Purge (NbiFi- A pre-defined policy to periodical-
lePurgePolicy) ly clean up files generated by the
North Bound Interface functionali-
ty during Event Synchronization
or Alarm Synchronization with the
Manager of Managers.
NBI Storage (NbiNotiS- A pre-defined policy to periodical-
toragePurgePolicy) ly clean up database storage
used to keep sent notifications
generated by the North Bound In-
terface (NBI) functionality.
Performance Archive A pre-defined policy to periodical-
Purge (PerfArchivePur- ly purge the archived statistical
gePolicy)
84
Additional Parameters
Event Storage size
Maximum number of events;
when total number of current
events exceeds a given value,
the oldest events are removed.
lastId
The id of the last event in the
previous file (updated after poli-
cy execution).
lastTime
The time (in milliseconds) in
which the last file is created (up-
dated after policy execution).
lastId
The ID of the last event copied
to the file; do not modify this pa-
rameter.
lastTime
The time (ms since EPOCH) of
the last policy execution; do not
modify this parameter.
lastTime
The time of last execution. Be-
fore first execution, it is equal to
server start time.
N/A
File History Time
The maximum age (in seconds)
of the file preventing that proc-
essed file from being deleted by
this policy.
N/A
N/A
 MN002730A01-AD
Chapter 3: SA Operation

Policy Description Additional Parameters

Statistics Data Clean-
up (StatsDataCleanup-
Policy)
Trap Overload Relieve
(TrapStoreOverloa-
dRelievePolicy)
data files from the SA server ap-
plication older than 31 days.
A pre-defined policy to periodical- Delete data after (days)
ly clean up any collected statisti- The frequency of cleanup.
cal data stored on SA. This policy Cleanup Hour
triggers the clean-up of data from An hour of date to execute poli-
the STATSDATA% table in the cy.
database to ensure that the data-
base does not get smothered by
the large amount of data collect-
ed every day. The administrator
decides on the frequency of
cleanup.
A pre-defined policy to periodical- N/A
ly detect trap overload condition
(constant very high load of SNMP
traps to be processed) and clean
up the oldest unprocessed trap
files when overload is detected.

3.5.1.2
Viewing Policy Details
IMPORTANT: Any user changes made in the predefined policy parameters shipped with SA
can seriously damage the SA application.

NOTICE: Do not delete any policies. Time intervals to trigger the predefined policies are
maintained on SA. You can update/execute the policies. Use the Policy user interface to set a
different trigger time. Unless necessary, do not change the trigger time.

Procedure:
1 In the Navigation View panel, click the Policies node.
The Policies window appears.
Figure 24: Policy Details Window

2 Optional: Right-click a policy to perform the following actions:

• Update
• Delete
• Execute

85
MN002730A01-AD
Chapter 3: SA Operation

• Stop
3 Optional: Right-click a policy to perform the following actions:
• Update
• Delete
• Execute
• Stop
In the Policy Item Details dialog box, the policy details appear

3.5.1.3
Default Policy Parameters
Name
The policy display name.
Group Name
The policy group name.
Period
Period for policy execution in seconds
Severity
Switch to enable or disable policy.

3.5.2
Viewing Job Status
You can view the statuses of the jobs initiated by the operator. All jobs listed in the Job Status View
are user-initiated. However, not all user-initiated jobs are maintained in the Job View. Jobs that are
maintained in the Job View are jobs that do not have immediate user feedback. They take longer time
to provide user feedback on the job disposition.

Procedure:
1 In the Navigation View panel, click the Job Status View node.
2 In the Job Status View window, perform the following actions:

If… Then…
If you want to access job logs, select a row and click View Log.
If you want to display job status de- double-click a row.
tails fields, The Job Status Details dialog box appears.

If you want to abort an unfinished dis- select a row and click Abort Job. For more in-
covery job, formation, see .

86
 MN002730A01-AD
Chapter 3: SA Operation

3.6
System View
Accessing the System View is the fastest way to determine the status of a Capacity Max System.
Figure 25: System View

Managed Resources
The System View gives an overall view of all managed devices and their status. The following devices
report alarms directly to the System Advisor (SA) and are visible in the System View:
• System Advisors
• Capacity Max System Servers (CMSS)
• Capacity Max Bridge
• Repeaters
• Routers
• Switches
The following devices do not report the fault status to the System Advisor, but some presence and
configuration information is available:
• MNIS Data Gateways
• MNIS Voice and Radio Command (VRC) Gateways

87
MN002730A01-AD
Chapter 3: SA Operation

• Replicators
• Trunk Controllers
Other types of devices can be discovered manually, but their level of management depends on how
they are recognized by the System Advisor and what management protocols they support.

Names of Managed Resources

During discovery, the System Advisor assigns a default name to the discovered managed resource. If
a repeater is discovered, the repeater alias is read from the device and used as a default repeater
name. If it is RF site, site objects are also named based on the site alias retrieved from the repeater.
Names of all managed resources can be changed in the System View. See Changing Managed
Resource Display Name in System View on page 45.

Tooltip Window
Clicking a node that represents a managed resource shows the tooltip window with details about the
resource, such as the Internet Protocol (IP) address, type, severity status, and device status. The
tooltip window also allows performing basic operations on the resource, such as renaming,
synchronizing, acknowledging alarms, and navigating to different views to analyze the managed
resource in a more detailed way.

Groups
The managed resources are grouped based on their logical location (for example, site) and type (for
example, repeaters) and shown in a hierarchy.
For easy navigation, sites are arranged in groups. Each group contains sites with IDs that belong to a
range of 30 IDs. For example, a site with ID 25 is assigned to the Sites 1 - 30 group, and a site with ID
35 is assigned to the Sites 31 - 60 group, no matter how many sites there are in the system.
You can move a site to a different group by right-clicking the site object and selecting Rename Site
Group Name from the tooltip window. Sites with the same group name are grouped together.
All group sections can be collapsed or expanded, thus allowing customization of the view to your
preference.

Alarms Severity
The severity of alarms and events reported for managed resources navigates from the bottom to the
top. The severity of the children node determines the severity of the parent node. This rule applies to
all nodes in the hierarchy tree. If a site is in a failure state, you can navigate to the failing resource.
See Severity Definitions on page 32.

Activity
Icons indicate the activity states of managed devices. stands for active/enabled, stands for
inactive/disabled. When the activity state of a device changes, System Advisor reports an event.

Repeaters
Besides common information available for all nodes, repeater nodes show additional indicators:
Main Repeater Channel Role
Control
Dedicated - Repeater hosting a dedicated Control Channel.
Shared - Repeater hosting Control Channel that can be switched to Trunking when needed.

88
 MN002730A01-AD
Chapter 3: SA Operation

Trunking
Repeater hosting Trunk Channels.
Data
Repeater hosting Data Revert Channels.
Redundancy Group
If at least one repeater in the redundant group is active and functional, you can detect the repeater
through the visual representation of redundant repeaters.

Gateways
Information about gateways includes a list of connected clients, identified by the client IP, port, and
client type: Voice or Data.

3.7
Call Monitoring Operations
Call monitoring in the System Advisor (SA) provides a view of real-time call and traffic activities within
each site.
In SA, there are two views which can be used to track calls and traffic in the system, the Grid View and
Raw View.

3.7.1
Call Monitoring – Grid View
The Grid View contains lists of sites in the system with counters of active and queued calls on each
site and also the status of each activity.
Sites are displayed in groups. By default, each group contains sites with IDs that belong to a given
range of 30 IDs. For example, a site with ID = 25 belongs to the Sites 1 - 30 group, and a site with ID =
35 is assigned to the Sites 31 - 60 group, no matter how many sites there are in the system. You can
view the sites in a group by expanding the group node.
In the System View, you can move a site to a different group by modifying the group name for the site.
Such changes are reflected in the Grid View.
Each site can be clicked, and the detailed view of the site is displayed on the right. In the detailed view,
you can see control, trunk, and data revert repeaters. Each repeater provides two logical channels over
which voice, control, or data information is transmitted.
When there are calls within the system, calls are represented with icons appearing on logical channel.
Different icons represent different types of calls: group, individual, voice, system, or site-wide. Only
successful calls which have channels assigned are represented. Therefore, it is visible at first sight
how much load there is in the system. Channels that are occupied have icons inside them, and free
channels have empty space inside.
You can search a call in the Grid View by using the source or target ID.

89
MN002730A01-AD
Chapter 3: SA Operation

Figure 26: Call Monitoring Grid View

Site Name
This tab displays the name of the available sites.
Active Calls
Shows the number of active calls in each site.
Queued Calls
Shows the number of calls waiting.
Status
Indicates the status of each site.
The data in each tab can be sorted by clicking the tab.
The Grid View can be filtered to view only certain activities in each site. You can choose whether to
display Voice activities, Data activities, Control Channel activities, a combination of three or any one.

Defining Status of Sites and Calls

Elements on the Grid View are marked by colors representing their state. When any event changes the
state of the repeater, it is immediately visible.
Green
Indicates that the status is Clear.
Blue
Indicates that there is a Warning.
Yellow
Shows that the status is Minor.
Orange
Shows that the status is Major.
Red
Indicates that there is a critical error.

90
 MN002730A01-AD
Chapter 3: SA Operation

Black
Indicates that there is communication failure.
When you open the Grid View for an inactive instance of System Advisor, the view is grayed out and
data related to calls is unavailable. A message appears in the bottom-right corner with a link to the
System Advisor launch page, which you can use to switch to an active SA. If the inactive SA switches
to active state, the Grid View starts normal operation automatically.

3.7.1.1
Viewing Grid Views
The Grid View allows you to monitor real-time call activities.
In the System Advisor (SA) client, you can only open one Grid View. Additionally, you can open
another Grid View window externally in the default web browser.
By opening the Grid View in the System Advisor client, you can view the context menu which includes
the following options:
• View Associated Alarms
• View Associated Events
• View Associated Managed Resources
When you open the Grid View in the web browser, the context menu is not available.
NOTICE: After a system upgrade, at first launch of the System Advisor client, refresh all Grid
View and Raw View windows opened in the web browser. By refreshing the views, you ensure
that the new software version is loaded.

Procedure:
1 In the Navigation View panel, click Call Monitoring → Grid View.
2 Perform one of the following actions
• To open the Grid View in the System Advisor client, click Grid View.
• To open the Grid View in the default web browser window, click Grid View Webpage.

3.7.1.2
Grid View Icons
The following icons on Grid View represent the control channel, the repeater channel states, and
various call activities taking place in each site.

Icon Description
Emergency call

Emergency alarm

91
MN002730A01-AD
Chapter 3: SA Operation

Call alert

Group call

Group broadcast call

Site wide call

System wide call

System all call

Individual FOASCU call

Individual OASCU call

92
 MN002730A01-AD
Chapter 3: SA Operation

Ambient listening

Individual data call

Group data call

Data broadcast call

Phone individual call

Confirmed group data call

Repeater channel is unavailable due to

CWID/BSI transmission.

Repeater channel is unavailable due to inbound

or outbound interference.

A mass random access (registrations/calls) sce-

nario has been detected.

93
MN002730A01-AD
Chapter 3: SA Operation

Control channel

3.7.2
Call Monitoring – Raw View
The Raw View shows raw data (also known as ATIA) which is exactly as it is received from the System
Advisor (SA).
Raw view shows information collected by the SA a few minutes before, depending on the number of
calls and loads in the system. One row in the Raw View corresponds to one piece of information
received from infrastructure: registration, transmission start, session end, or call grant. Raw data is
grouped into calls, so that relevant information can be easily found.
The Raw View contains two components. List of Calls on the left and Detailed Debug View on the right.
Figure 27: Call Monitoring – Raw View

List of calls is used to view calls in three states: ended, active, or queued. In normal system flow, when
a radio requests to make a call, this request appears as queued in calls list. When the Trunking
Controller grants the call, the call changes its state to active. Finally, when the call ends on all involved
devices, it moves to “ended” (historical) state. If the infrastructure rejects the call, it appears as ended
call with appropriate reason. Additionally, there is a column indicating when the call started (for active
or past call) or when it was added to the calls queue (for queued calls). Duration of the call or time of
call waiting in the calls queue is also displayed.

94
 MN002730A01-AD
Chapter 3: SA Operation

In Raw View, you can see details of any call by clicking the call. The packet of this call is highlighted in
the detail view and irrelevant packets are hidden. You can search for information by using the given
source ID.
Traffic logs information shown on the Detailed Debug View are stored for at least one month for
debugging purposes. You can access the traffic logs from the Server Logging menu.

Activity States
Colored entries in the Raw View indicate changes of the System Advisor activity state. A red entry
informs you that the SA instance has become inactive. A green entry indicates that the SA instance
switched to an active state.

3.7.2.1
Viewing Raw Views
The Raw View allows you to monitor real-time call activities.
NOTICE: After a system upgrade, at first launch of the System Advisor client, refresh all Grid
View and Raw View windows opened in the web browser. By refreshing the views, you ensure
that the new software version is loaded.

Procedure:
In the Navigation View panel, click Call Monitoring → Raw View Webpage.

3.8
Fault Management Operations
Fault management in SA includes processing and presentation of events sent by a network element.
Failures in the network, network elements, as well as communication links can interrupt routine
activities. When a failure occurs, events and alarms are reported in SA, based on the criticality of the
occurrence.

3.8.1
Displaying Alarm Details from the Network Database Window
Procedure:
1 In the Network View panel, click the Network Database node.
2 In the Network Database window, highlight a row.
3 From the main menu, select View → Alarms.
The Alarms window appears, displaying the alarms associated with the managed resource you
selected.

3.8.2
Displaying Event Details from the Network Database Window
Procedure:
1 In the Navigation View panel, click the Network Database node.
2 In the Network Database window, highlight a row.
3 From the main menu, select View → Events.
The Network Events window appears, displaying the events associated with the managed resource
you selected.

95
MN002730A01-AD
Chapter 3: SA Operation

3.8.3
Managed Resource Properties
The following table describes various properties of managed resources. The properties are displayed
in the Managed Resource Properties window. The Field Name column captures the name, as shown
in the Managed Resource Properties window. You can also use the table to configure Custom
Views. During the configuration of network database custom views, you can configure filter criteria for
any of the properties. If the name of the property is not available, the custom view user interface
supports defining additional properties. Use the additional property, based on the Property name for
filtering column.

Table 7: Managed Resource Properties

Field Name Description Property Name for Filtering

General Tab
Name Displays the unique Managed name
Resource internal name.
Managed Resource Displays the name of the Man- displayName
aged Resource (this name is
configurable).
Type Displays the device type. type
Class Name Displays the category to which classname1
the device belongs.
Severity Displays the present status of status
the device.
Managed Displays the state of the de- managed
vice (managed or unman-
aged).
Relationships Tab
Parent Resource Displays the resource internal parentKey
name of the parent.
Subsystem Name Displays the subsystem name subSystemName
for the device.
Is Group Displays whether the device is isGroup1
part of a group.
Others Tab
Is Container Displays whether the device is isContainer1
a container object.
Object location — Site Displays the discovery type. N/A
Group Managed Resource Displays the managed re- groupManagedResourceType
Type source type, as specified in
the group.

1These properties are either NOT USED or INTERNAL to System Advisor. The use of these properties
as part of filter criteria for the Network Database view is NOT recommended.

96
 MN002730A01-AD
Chapter 3: SA Operation

3.9
Network Events Operations
A network event is an occurrence within a defined network. It could be a discovery of an element, a
status update of an element, or an element failure. Events form a repository of information for all the
occurrences within the system.
The Network Events window provides a means of looking at all events, or a filtered subset of events
that the system receives. Consolidated lists of events are displayed in the Network Events window.
The event properties that are displayed include:
• Severity
• Managed Resource
• Message
• Entity
• Date/Time
The following properties are not automatically displayed on the Network Events window by default:
Category
Event Type
NE Timestamp
Event time reported by the device
Reporting Agent
Report agent IP address

3.9.1
Event Properties
The following table describes various properties of an event. The Field Name column captures the
name as shown on the Managed Properties window.
During the configuration of network database custom views, you can configure filter criteria on any of
the properties. If the name of the property is not available, the custom view user interface supports
defining an additional property. Use the additional property, based on the Property Name for Filtering
column.
NOTICE: The property name, when used for filtering, is case-sensitive and should be used
exactly as specified when typing in the name of the additional property criterion to filter on.
In property names, do not use the following characters:
white space
empty space
> < & $ # ^ - " ' ""
a digit at the beginning of the name
* ! @ ( + ~ { [ | \ ; , . ? / % `

Field Property Name for

Description
Name Filtering
Event ID The unique ID of an event. This ID is sequential and SA as- id
signs it for each event.
Message Descriptive text message about the event. text
Category Category of the event. For example: category

97
MN002730A01-AD
Chapter 3: SA Operation

Field Property Name for

Description
Name Filtering

• Information Event
• Attribute Value Change Event
• Equipment Alarm
• Communication Alarm
• Processing Error Alarm
• Object Creation Event
• Object Deletion Event
• Management Event
• Security Violation
Domain Domain of the event. Not used by SA. domain
Network The associated network. Not used by SA. network
Node Name of the corresponding network element for which an node
event is being generated.
Failure Failure object which was responsible for the creation of the entity
Object (al- event. The internal name derived by SA.
so named
as Entity
in Event
Filter UI)
Severity Severity of the event. severity
Date/Time The time at which the event was generated on SA. The time time
displayed on the Date/Time field in the Network Events win-
dow.
Source The Managed Object to which the event corresponds. Gen- source
erally, it is the name of the Managed Object.
Help URL A help URL for more detailed information on causes. Not helpURL
used by SA.
Group- The group to which the event belongs. Not used by SA. groupName
Name
Owner- Not used by SA. ownerName
Name
Identifier An internal attribute that uniquely identifies a particular identifier
event. The northbound manager uses it to determine wheth-
er the event is a duplicate, without relying on the event text.
This identifier is different from the Event ID field. Example:
For a site controller power supply malfunction due to fan fail-
ure, the identifier is csc_ps_fault.7.2 where 7 is the
malfunction state number and 2 is the fan failure cause num-
ber. Similarly, for a site controller power supply malfunction
due to excessive battery temperature the identifier is
csc_ps_fault. 6.4..
Entity- User-friendly name of the Failure Object the event is associ- entityDisplayName
Name ated with.

98
 MN002730A01-AD
Chapter 3: SA Operation

Field Property Name for

Description
Name Filtering
NeTimeS- Time at which the event was generated on the device. If the neTimeStamp
tamp device does not send this timestamp in the event, this attrib-
ute has an empty value.
Manage- User-friendly name of the managed object to which the managedResource-
dRe- event corresponds. The user-friendly name for the managed DisplayName
source object name, defined by the Source attribute of the event, for
example chan3.ss2.site60.zone7.
Reporting IP Address of the device (agent) sending the event. reportingAgent
Agent
Event Age Property that is available only in the Event Custom View UI. N/A
(modified This property is not applicable to Event Filters user interface
time) and cannot be used in the filter criteria definition on the
Event Filters UI.
This property specifies the age of the event. Age of an event
denotes the time elapsed since the last modification of the
alarm on SA.
By default, the value specified is Any, whereby events of
any age are displayed.
Other options are: minutes, hours, days, today, and yester-
day.
Example: Age in hrs < 1 displays all the events that are less
than an hour old. After this custom view is created, the
events are dynamically added to the view when they meet
the criteria of being less than one hour old. In this case, the
old events remain in the view. If you require to delete the old
events and want to view only those currently meeting the cri-
teria, set Refresh period in minutes. By default, it is set to
one minute. When you set it, the server application sends
data automatically at the specified time interval.
Device The category in which the managed resource is in. mrDeviceCategory
Category

3.9.2
Viewing Event Details
All events detected by SA are based on the status of the recognized networks. Event details display
the property name and its value.

Procedure:
1 In the Navigation View panel, select Fault Management → Network Events.
2 In the Network Events window, double-click an event to view its details.
The Event Object Details window appears, displaying the details pertaining to the event you selected.

99
MN002730A01-AD
Chapter 3: SA Operation

Figure 28: Event Details Window

3.9.3
Exporting Events
Follow this procedure to export events to a .csv (Comma Separated Value) file and save it to the local
client PC.

Procedure:
1 In the Navigation View panel, select Fault Management → Network Events.
2 In the Network Events window, highlight an event.
3 From the main menu, select Actions → Export Events.
4 In the Save File window, perform the following actions:
a Select the destination directory.

100
 MN002730A01-AD
Chapter 3: SA Operation

b Enter a file name followed by .csv.

c Click Save.
NOTICE: To print the events, open the saved file on the client and use the Print
option in the application you are using.
The .csv file is saved to the local client PC.

3.9.4
Searching Events
The search option is useful when you are looking for a particular event in the list of events. Search
operations are performed in the database and are not restricted only to the events that you see in SA.

Procedure:
1 In the Navigation View panel, select Fault Management → Network Events.
2 From the main menu, select View → Search.
The Search dialog box appears.
Figure 29: Search Dialog Box

3 In the Search dialog box, set your search options:

a From the first drop-down list, select the property you want to base your search on.
b From the second drop-down list, select the condition based on which you want to restrict your
search.
c In the text field, enter the exact information you are looking for.
Step example: If you selected a severity from the first drop-down list, in the text field, specify
the severity value, for example, critical or major.
If you selected date or time-related properties, the Date/Time spin box to set date and time is
available.
4 Define which criteria you want to include in the search:
• To perform a search operation that meets any of the matching criteria that you specify, clear
the Match All of the Above Criteria check box.
• To include all matching criteria in your search operation, select the Match All of the Above
Criteria check box.
5 Specify more criteria by clicking More and repeating Step 3 and Step 4.

101
MN002730A01-AD
Chapter 3: SA Operation

6 Optional: Remove some of the criteria by clicking Fewer.

The last criterion on the list is removed.

7 To begin the search, click Search.

NOTICE: If you want to view all events after performing the search, in the Network
Events window, click Show All.
Events meeting the configured criteria are displayed in the same view.

3.10
Alarm Operations
SA receives an alarm when a device does not function properly.
The agent within the device sends notifications about the device to SA. A notification is uncovered as
an event or alarm, based on the information provided. SA displays alarms in a separate window.
Figure 30: Alarms Window

You can see details of a specific alarm by double-clicking an alarm. A window with alarm details
appears.

102
 MN002730A01-AD
Chapter 3: SA Operation

Figure 31: Alarm Details Window

3.10.1
Alarm Summary View Operations
From the Alarm Summary View panel, you can display alarm details in different ways.

3.10.1.1
Displaying Alarm Details from the Tabular View Chart
You can view Alarm details in a tabular view chart.

Procedure:

1 In the Alarm Summary View panel, click the Severity and Category – Tabular view .
The alarms, based on severity and category, appear in a tabular view.

103
MN002730A01-AD
Chapter 3: SA Operation

Figure 32: Alarm Summary View – Tabular View

2 Click a severity range or a category number.

The Custom Alarm panel appears, displaying the filtered alarms.

3 In the Alarms window, perform one of the following actions:

• To view alarm details for your selection in a new window, in the Alarms window, right-click
an alarm and select Details.
• To view events related to the selected alarm in the Network Events window, in the Alarms
window, rightclick an alarm and select Events.

3.10.1.2
Displaying Alarm Details from the Severity Alone Pie Chart

Procedure:

1 In the Alarm Summary View panel, click Severity Alone .

The alarms, based on their severity, appear in a graphical view, indicating the percentage of
severity against each level.

104
 MN002730A01-AD
Chapter 3: SA Operation

Figure 33: Alarm Summary View – Severity Alone Pie Chart

2 Click a severity level.

The Alarms window appears displaying filtered alarms.

3 In the Alarms window, perform one of the following actions:

• To view alarm details for your selection in a new window, in the Alarms window, right-click
an alarm and select Details.
• To view events related to the selected alarm in the Network Events window, in the Alarms
window, right-click an alarm and select Events.

3.10.1.3
Displaying Alarm Details from the Severity and Category Chart
Procedure:

1 In the Alarm Summary View panel, click Severity and Category - Graphical view .
The alarms, based on severity and category, appear in a graphical view, indicating the number
of alarms for each severity.

105
MN002730A01-AD
Chapter 3: SA Operation

Figure 34: Alarm Summary View – Graphical View Chart

2 Click a severity level.

The Alarms window appears, displaying the filtered alarms.

3 In the Alarms window, perform one of the following actions:

• To view alarm details for your selection in a new window, in the Alarms window, right-click
an alarm and select Details.
• To view events related to the selected alarm in the Network Events window, in the Alarms
window, right-click an alarm and select Events.

3.10.2
Alarms Window Operations
The Alarms window displays all alarms active in the network.

3.10.2.1
Viewing Alarm Details
Alarm details provide information about each of the alarm properties.

Procedure:
1 In the Navigation View panel, select Fault Management → Alarms
2 In the Alarms window, double-click an alarm row.
The Alarm details for <source> window appears, listing alarm properties.

3 Optional: Update the alarm details instantly by clicking Refresh in the Alarm details for
<source> window.

106
 MN002730A01-AD
Chapter 3: SA Operation

3.10.2.2
Searching Alarms
The procedure for searching alarms is the same as the procedure for searching events.

3.10.2.3
Viewing Related Events
Procedure:
1 In the Navigation View panel, select Fault Management → Alarms
2 In the Alarms window, right-click an alarm row and select Events.
The Network Events window appears with the events related only to the selected alarm.

3.10.2.4
Viewing Alarm History and Annotations
The alarm history gives the complete information on alarm status, such as added and updated alarms.
For example, when a critical alarm is generated, in the Alarms window, an alarm status appears.
When the problem is fixed, the alarm severity changes from critical to clear. When viewing alarm
history, you can also see alarm annotations.

Procedure:
1 In the Navigation View panel, select Fault Management → Alarms
2 In the Alarms window, double-click an alarm row.
The Alarm details for <source> window appears, listing alarm properties.

3 In the Alarm details for <source> window, click View history.

The Alarm History window appears, displaying the alarm history that includes 20 last instances
of the alarm, the time at which the alarm occurred, fix time, and severity change.

3.10.2.5
Deleting Alarms
When SA displays alarms for resources that are no longer managed by SA, a privileged operator can
delete the alarms from SA. The event history is not deleted with the alarm.

Procedure:
1 In the Navigation View panel, select Fault Management → Alarms.
2 In the Alarms window, delete alarms:
• To delete one alarm, right right-click an alarm and select Delete.
• To delete multiple alarms, select the alarms you want to delete by holding CTRL and clicking
the alarms. Right-click the selection and select Delete.
3 In the confirmation window, confirm the operation by clicking OK.
This option deletes only the alarm. It does not prevent it from re-appearing when a device
reports an alarm of the same type in the form of a notification or due to synchronization with the
device.
The selected alarm or alarms are deleted and disappear from the Alarms window.

107
MN002730A01-AD
Chapter 3: SA Operation

3.10.3
Adding Annotations to Alarms
You can add an annotation to alarms. An annotation is an extra piece of information that tells you how
to deal with an alarm. Annotations can serve other functions as well. They are visible to other users.

Procedure:
1 In the Navigation View panel, select Fault Management → Alarms.
2 In the Alarms window, double-click an alarm row.
The Alarm details for <source> window appears, listing alarm properties.

3 In the Alarm details for <source> window, in the Annotations field, add information about the
alarm. Click Save.
The annotation can be 4,096 characters long or shorter.
Your annotation is added to the alarm. The annotation is visible to other users. After saving an
annotation, you can still modify it.

3.10.4
Launching the Alarms View from the Network Database View
You can view alarms for a selected device by opening the Alarms view from the Network Database
view.

Procedure:
1 In the Navigation View panel, click the Network Database node.
2 In the Network Database window, select a managed resource and from the main menu, select
View → Alarms.
The Alarms window appears, displaying the alarm (if any) for the device you selected.

3.10.5
Exporting Alarms
Follow this procedure to export alarms to a .csv (Comma Separated Value) file.

Procedure:
1 In the Navigation View panel, click the Alarms node.
2 In the Alarms window, highlight an alarm.
3 From the main menu, select Actions → Export Alarms.
4 In the Save File window, perform the following actions:
a Select a destination directory.
b Enter a file name followed by .csv. Click Save.
NOTICE: To print the alarms, open the saved file on the client and use the Print option in
the application you are using.
The .csv file is saved to the local client PC.

108
 MN002730A01-AD
Chapter 3: SA Operation

3.10.6
Displaying Alarms Summary
Procedure:
1 In the Alarm Summary View panel, perform one of the following actions:

• Click the Severity and Category – Tabular View icon .

• Click the Severity and Category – Graphical View icon .

• Click the Severity alone icon .

Alarms appear in the selected view in the Alarm Summary View panel.

2 Depending on your view, perform one of the following actions:

If… Then…
If you are using the Severity and Category – Tabular click a severity or a category.
View,
If you are using the Severity and Category – Graphical click a severity.
View or Severity alone,
The Alarms window appears, displaying the filtered alarms.

3 In the Alarms window, perform one of the following actions:

• To view alarm details, double-click an alarm.
• To view events related to the selected alarm, right-click an alarm and from the context menu
select View Events.

3.10.7
Alarm Properties
The following table describes various fields of an alarm. The Field Name column captures the name as
shown on the Managed Properties window. During the configuration of alarm custom views, you can
configure filter criteria on any of the properties. If the name of the property is not available, the custom
view user interface supports defining an additional property. Use the additional property, based on the
Property Name for Filtering column.
NOTICE: When used for filtering, property names are case-sensitive and should be used
exactly as specified when typing in the name of the additional property criterion to filter on.
In property names, do not use the following characters:
white space
empty space
> < & $ # ^ - " ' ""
a digit at the beginning of the name
* ! @ ( + ~ { [ | \ ; , . ? / % `

Property Name
Field Name Description
for Filtering
Severity Severity of an alarm. severity

109
MN002730A01-AD
Chapter 3: SA Operation

Property Name
Field Name Description
for Filtering
Previous se- Previous severity of an alarm, that is, the severity of the previousSeverity
verity alarm before it was updated.
Annotations Additional information about an alarm that you can add. Annotations
The length of an annotation cannot exceed 4,096 signs.
Alarm ID The unique ID of an alarm. Since every alarm on System id
Advisor (SA) is generated from a corresponding event,
this ID is the same as the ID of the corresponding event.
Managed Re- User-friendly name of a managed object to which an managedResour-
source event corresponds. It is the user-friendly name for the ceDisplayName
managed object name, defined by the Source attribute of
the event, for example St3 Rptr1.
Reporting IP address of a device (agent) sending an alarm. reportingAgent
Agent
Created The time at which an alarm was created on SA. It is the createTime
time displayed in the Date/Time field in the Alarms win-
dow.
Modified The date and time at which an alarm was last modified. modTime
Reported The date and time at which an alarm was last reported.
Owner/Assign- The name of the owner of the alarm. who
ee
Category Category of an alarm. The value can be one of the fol- category
lowing:
• Equipment Alarm
• Quality of Service Alarm
• Communication Alarm
• Processing Error Alarm
• Security Violation

Ack Status Shows whether the alarm has been acknowledged,

Message Descriptive text message about an alarm. message
Source The name of a managed object to which an alarm corre- source
sponds.
Failure Object Failure object or entity which has the problem indicated entity
by this alarm. The entity and failure object refer to the
same property.
Identifier An internal attribute that uniquely identifies a particular identifier
alarm. The northbound manager uses the Identifier to de-
termine whether the alarm is a duplicate, without relying
on the alarm text. This identifier is different from the
Alarm ID field. Example: For a site controller power sup-
ply malfunction due to fan failure, the identifier is
csc_ps_fault.7.2 where 7 is the malfunction state
number and 2 is the fan failure cause number. Similarly,
for a site controller power supply malfunction due to ex-

110
 MN002730A01-AD
Chapter 3: SA Operation

Property Name
Field Name Description
for Filtering
cessive battery temperature the identifier is
csc_ps_fault.6.4.
Is unverifiable Indicates if the alarm is able to be verified.
Managed Re- The category in which the managed resource is in.
source Device
Category
Alarm Priority Indicated the priority of the alarm. alertPriority

3.10.8
Audio Notifications for Alarms
Audio notification for an alarm associates an audio file with a severity. When an alarm with that severity
is raised, you can hear the associated audio notification. You can also mute audio notifications,
configure the playback time of the audio file, and set the system to play the whole file.
There are six severity levels that can be associated with an audio file. If it is not necessary to audibly
distinguish severities, you can configure the same audio file for all severities.

3.10.8.1
Assigning Audio Notifications to Alarms
Assigning an audio notification to an alarm associates an audio file with a severity. When an alarm with
that severity is raised, you hear the associated audio notification. You can also mute audio
notifications, configure the playback time of the audio file, and set the system to play the whole file.
There are six severity levels that can be associated with an audio file. If it is not necessary to audibly
distinguish severities, you can configure the same audio file for all severities.
Prerequisites: Ensure that the Alarms window that is open is not filtered to exclude the alarm to which
you want to assign an audio notification.

Procedure:
1 In the Navigation View panel, select Fault Management → Alarms.
2 From the main menu, select Actions → Alarms Notifier.
The Alarm Audio Notification dialog box appears.

111
MN002730A01-AD
Chapter 3: SA Operation

Figure 35: Alarm Audio Notification Dialog Box

3 In the Alarm Audio Notification dialog box, make sure the Enable Audio Notification check
box is selected.
The options in the Audio File Details field are enabled.

4 Select a severity to which you want to associate an alarm.

5 Click Browse and select the audio file you want to associate with an alarm.
6 To play the audio file, click Test.
7 Click Apply. Repeat the steps to assign alarms for other severity levels.
NOTICE: You can set the playback time for an alarm by specifying the duration in
seconds. The alarm is not played longer than the duration of the audio file itself.

3.10.9
Launching the Alarms View from Custom Alarm Panel
Procedure:
1 In the Navigation View panel, expand the Alarms node.
The Alarms node expands and a list of custom views appears.

2 From the list of custom views, select a previously created custom view.

112
 MN002730A01-AD
Chapter 3: SA Operation

3.10.10
Alarms Ownership
You can take on the responsibility of owning an alarm and assigning it to an assignee who takes the
alarm forward.
The alarm ownership operation can be invoked from:
• The Alarm details window
• The main menu Actions → Assign/UnAssign
After an alarm is assigned, the System Advisor (SA) stores the data of the user assigned to an alarm
and a timestamp in audit trails.

Batch Assignments
If you select a list of alarms and invoke the Assign/UnAssign operation, all the selected alarms are
assigned the same owner and assignee.

3.10.10.1
Assigning Ownership to Alarms from the Alarms Details Window
Procedure:
1 In the Navigation View panel, select Fault Management → Alarms.
2 In the Alarms window, double-click an alarm row.
The Alarm details for <source> window appears, listing alarm properties.

3 In the Alarm Details window, click Assign.

4 In the AlarmAssignDialog dialog box, type the assigned user name and click OK.
Figure 36: Alarm Assign Dialog Box

5 In the Alarm Details window, click Close.

In the Alarm Details window, the assignment appears in the Owner/Assignee field.

3.10.10.2
Assigning or Unassigning Ownership to Alarms from the Main Menu
Procedure:
1 In the Custom Alarm window, highlight an alarm.
2 From the main menu, select Actions → Assign/Unassign.

113
MN002730A01-AD
Chapter 3: SA Operation

3.11
Device Management Operations
SA uses the discovery process to find devices that are managed in a system.
Whenever a managed resource is discovered (or rediscovered) successfully, SA designates the
management state of that resource as MANAGED.
There are two types of managed resources: device managed resources and logical managed
resources. Logical managed resources are non-physical managed resources, for example, a site.
Device managed resources are physical managed resources, for example, a base radio or a site
controller.
Once a device is marked as MANAGED, SA starts periodic supervision and synchronization. SA also
starts displaying events sent by this device. It raises active alarms against a specific entity within this
device whenever any displayed event requires user attention.
If you have administrative privileges, you can unmanage a managed resource in SA. Once a device is
in an unmanaged state, SA:
• Does not supervise the device.
• Does not synchronize the device.
• Does not diagnose the device.
• Does not perform rediscovery.
• Does not allow any user to view any new events or alarms of any entity from this device.

3.11.1
Managing Resources
Device management provides administrators or Motorola Solutions Systems Support Center (SSC)
administrators with the ability to start managing a previously unmanaged device. Managing an
unmanaged device automatically invokes device rediscovery.
There are two types of resources:
• Device Managed Resources (DMR)
• Logical Managed Resources (LMR)
The only two management states of both DMRs and LMRs are MANAGED and UNMANAGED.

Procedure:
1 In the Navigation View panel, click the Network Database node.
2 In the Network Database window, search for the Device Managed Resource (DMR) you need.
The DMR severity should be Unknown.
3 Right-click the selected DMR and select Manage.
DMR and its Logical Managed Resources (LMRs) become managed. SA starts state synchronization
and traps processing for that device.

3.11.2
Unmanaging Resources
Device unmanagement gives the privileged operator, that is the administrators or Motorola Solutions
Systems Support Center (SSC) administrators, the ability to remove a non-critical device managed
resource from the system.
There are two types of resources:

114
 MN002730A01-AD
Chapter 3: SA Operation

• Device Managed Resources (DMR)

• Logical Managed Resources (LMR)
You can unmanage a resource to remove it if it fails or is at fault. For example, when the managed
resource is interfering with the display of the system health by retaining long-standing high-priority
alarms or generating an excessive number of events.

Procedure:
1 In the Navigation View panel, click the Network Database node.
2 In the Network Database view, search for the Device Managed Resource (DMR) you need.
Every DMR has a defined IP address.
3 Right-click the selected DMR and click UnManage
DMR and its Logical Managed Resources (LMRs) become unmanaged. Their severity changes to
Unknown. SA stops state synchronization and traps processing for that device.

3.11.3
Deleting Network Elements
An operator accesses System Advisor (SA) to request the deletion of a network element or a logical
managed resource. The user assigned to the SuperUser or Motorola Solutions Systems Support
Center (SSC) group has the rights to permanently remove a managed resource from SA.
Administrators or Motorola Solutions Systems Support Center (SSC) administrators are allowed to
request the deletion of both network element and Logical Managed Resources (LMR).

Procedure:
1 In the Navigation View panel, click the Network Database node.
2 In the Network Database view, right-click a manager resource row and select Delete Object
and Traces.
3 In the confirmation dialog box, click Yes.
4 In the Deletion Status dialog box, click View Job Status.
A separate job is initiated for each deletion request. The status of the request appears in the Job
Status View window.

5 In the Job Status View window, verify the deletion status.

Figure 37: Job Status View for Deletion Jobs Window

115
MN002730A01-AD
Chapter 3: SA Operation

NOTICE: If you delete a single network, the network name appears in the Target column
in the Job Status View window. If you delete multiple networks, Multiple nodes message
appears in the Target columns.
If the job status is Success or Completed, the network element or node and the alarms
associated with it are also deleted. Events are not deleted, as events are part of the history and
they are deleted only when the database is reinitialized.

6 If the Warning Discovery in progress dialog box appears, to the view active jobs that are
related to the object being deleted, click Open Job View.
NOTICE: Once a network element is deleted, you cannot restore its alarms.

Job View with the first job highlighted appears.

Postrequisites: If the deleted device is discovered by the system intermediary, the device is created
and managed again. If you do not want to see the status of this device, un-manage the device.

3.11.4
Device Commands
To fault-manage devices and their entities, you can issue commands from SA to a device or a specific
entity of the device.
SA supports, for example, enable, disable, and restart commands. After you issue a command,
command status is displayed on the status bar and SA receives alarms about the device state change.

3.11.4.1
Issuing Commands from the Alarms Window
Procedure:
1 In the Navigation View tree, select the Alarms node.
2 In the Alarms window, select the alarm for which you want to issue a command.
3 In the main menu, select Actions → Issue Command.
4 In the Command dialog box, perform the following actions:
a Select an entity for which you want to issue a command.
b Optional: If a list with entity instances is available, select an entity instance.
c In the Available Commands pane, select a command.
d Click Apply.
When you issue a command for entities that do not support diagnostics, a warning message
appears.

On the multi-line status bar, the system displays one of the following command statuses:
Execution time
Indicates that the command is being processed: Sending command.
Successful command
Indicates that the command status is successful.
Failed command
Indicates that the command status is unsuccessful. A message displays the status as failed and the
reasons of failure.

116
 MN002730A01-AD
Chapter 3: SA Operation

3.11.4.2
Issuing Commands from the Network Database Window
Procedure:
1 In the Navigation View tree, select the Network Database node.
2 In the Network Database window, select the alarm for which you want to issue a command.
3 In the main menu, select Managed-Resource → Issue Command.
4 In the Command dialog box, perform the following actions:
a Select an entity for which you want to issue a command.
b Optional: If a list with entity instances is available, select an entity instance.
c In the Available Commands pane, select a command.
d Click Apply.
When you issue a command for entities that do not support diagnostics, a warning message
appears.

On the multi-line status bar, the system displays one of the following command statuses:
Execution time
Indicates that the command is being processed: Sending command.
Successful command
Indicates that the command status is successful.
Failed command
Indicates that the command status is unsuccessful. A message displays the status as failed and the
reasons of failure.

3.12
Synchronization Operations
In a large network, the network administrators would store all the details of the device in a centralized
database.
Hence, whenever a device gets configured, update the latest configuration changes in the database.
This synchronization allows data integrity by keeping the latest device details intact. Periodic
synchronization on a device, initiates the network element to send all previously unacknowledged
state/cause redundant messages. A user-initiated synchronization or synchronization after discovery
initiates the network element to send all current state/cause redundant messages. You can see the
synchronization state of a device under the Others tab in the Managed Resource Properties of the
device.

3.12.1
Synchronizing Managed Resources
Synchronization is the process in which the status of a device is periodically checked. There can be
situations in which you may not want to wait for the minimum period to view the synchronization
results. Therefore, you can initiate a synchronization request for the device with the manager. The
request interrupts the normal synchronization process and checks the status of a particular device.

Procedure:
1 In the Navigation View panel, click the Network Database node.

117
MN002730A01-AD
Chapter 3: SA Operation

2 In the Network Database click the Network Database node

The managed resource is synchronized. The Synchronization Job Status dialog box with a
synchronization request summary appears. You can view the job status by clicking Job Status View.

3.13
Discovery Operations
Discovery is the process of adding network elements to the Network Database. Discovered network
elements are fault-managed by System Advisor (SA) and generate events and alarms. There are two
ways of discovering network elements.

Discovering Network Elements through the Intermediary

The Intermediary discovers a network element and adds the element to SA for fault management.

Discovering Network Elements Manually

A network element can also be discovered by using the IP Address and Host Name.

3.13.1
Discovering Network Elements
Discovering a single network element, that is one network element at a time, is sometimes referred to
as node discovery. Node discovery operations initiated for a single network element have priority over
the subnet discovery option. Thanks to this priority, operators can discover single network elements
before the subnet discovery is completed.

Procedure:
1 From the main menu, select Tools → Discovery.
The Discovery Configuration window appears.

118
 MN002730A01-AD
Chapter 3: SA Operation

Figure 38: Discovery Configuration window

2 In the Discovery Configuration window, click the Node Discovery tab.

3 In the Node Discovery tab, provide discovery credentials:
a In the IP Address or Hostname field, enter an IP address or hostname of the network
element you want to discover.
b In the Agent Port field, enter an SNMP agent port.
You can leave the default value unchanged as it applies to most of network elements.
c If the device that you want to discover is in a site, select the Site ID check box and provide
the ID of the site that the device is located in.
If the device is not within any site, leave the Site ID check box cleared.
d If you want to discover all devices in a subnet, select the Subnet discovery check box.
For each discovery request, a separate job is initiated. You can view job statuses by clicking View Job
Status. If the discovery is based on the hostname, the Target column in the Job Status View window
shows the hostname with the IP address appended.

3.13.2
Aborting Discovery Jobs
Procedure:
1 In the Navigation View panel, expand the Job Status View node.
2 Select a row with the discovery job you want to abort.
If the selected job type is Discovery and its status is In Progress, the abort job option becomes
active.

119
MN002730A01-AD
Chapter 3: SA Operation

3 Click Abort Job.

4 In the confirmation dialog box, click Yes.
NOTICE: Selected devices awaiting discovery are not discovered. Selected devices
already processed are discovered with appropriate status (discovered, failed, or
unreachable). Job status is set to Aborted if at least one device discovery is aborted
during the operation.

3.13.3
Discovery Status
The status of a discovery job is displayed in the Job Status View window. Status messages include:
In progress
The job submission has been recognized and is in the queue. To determine if the job has started
executing and to get information on the progress, view the job log.
Aborting
An authorized user has chosen to abort an unfinished discovery job. Discovery of devices awaiting
in the queue is being aborted. Discovery of devices for which discovery process was initiated
continues without any interruption. Job log contains details about status of each device (represent
by IP address).
Success
The discovery job has completed successfully. One or more devices may still have not been found
due to communication failures. This information is shown in the Additional Information field and
detailed information is available in the job log.
Completed
The discovery job is complete but no devices defined for the discovery were available. Detailed
information is available in the job log.
Failure
The discovery job has failed. The job has terminated abnormally. The job log provides additional
details and it is necessary for the user to re-submit the job at a later time.
Aborted
An authorized user has aborted the discovery job. At least one device discovery was aborted. The
Additional Information field contains detailed information about the number of discovered, failed,
unreachable, and aborted devices.
After the job is complete, select the job and click View Log. Check the discovery logs for details on IP
addresses that were discovered and IP addresses that are not reachable. Confirm that IP addresses
that are not reachable are indeed not configured in the network. Check the network plan or, by
executing an Internet Control Message Protocol (ICMP), ping on the unreachable IP addresses.
When you choose to abort a discovery job, the status is initially set to Aborting.
• If SA aborts the job, status is set to Aborted.
• If SA initiated discovery of some devices in the selected job, the status is set to Failure or Success.
View the log for more details.
Summary information about the number of discovered, failed, unreachable and aborted jobs can be
found in the Additional Comments column.

120
 MN002730A01-AD
Chapter 3: SA Operation

3.14
Performance Management Operations
Performance management includes all procedures necessary to monitor and collect information on
devices fault managed by SA.
NOTICE: To avoid loss of functionality, only Motorola Solution Support Center (SSC) personnel
should edit values.

3.14.1
Viewing Configured Collections for a Device
The Configured Collection panel displays the list of statistics configured for a data collection. Based
on the defined statistics, System Advisor (SA) collects the data from a device.

Procedure:
1 From the Navigation View panel, select Performance → Configured Collection.
The Configured Collection window appears on the right-hand side of the panel, showing all the
configured statistics for the selected device. The Hosts column lists all the devices on the
network that are configured for data collection.

2 To view the list of statistics for a host, select the host from the Host column in the left panel.
The statistics for the selected host are displayed in the right-hand column.

3 Double-click any statistic to view details for that statistic.

The Data Collection Detailed Properties window appears.

3.14.2
Statistic Properties
Name
A unique name (string) to identify the statistic.
ID
A unique number generated automatically and associated with each statistic.
DNS Name
Host name (device name).
OID
A unique identification number of the device interface.
Community
The community used when sending the SNMP request for collecting the statistic.
Period
The interval at which data is collected for the statistic. For example, the value 300 indicates that
data is collected every 300 seconds.
Active
Specifies whether data collection for the selected device is active or not. The possible values are
true or false. If it is false, data collection is not performed for that device.
Multiple
Specifies the type used to poll columnar value of the tables.
User Name
One of the credentials required for querying SNMPv3 devices.

121
MN002730A01-AD
Chapter 3: SA Operation

SNMP
Simple Network Management Protocol (SNMP) version of the device.
Context Name
One of the credentials required for querying SNMPv3 devices.

3.14.3
Data Collection Detailed Properties

Table 8: Data Collection Detailed Properties

Object Details
Description
Field
Name Specifies the name of the statistic.
For example, if the statistic name is specified as interface_in_octets, then
only devices with that statistic are displayed in the custom view.
Specify multiple statistic names as comma-separated values. For example, in-
terface_in_octets, interface_out_octets.
ID Specifies the ID of a statistic.
DNS Name Specifies the host (node).
Example: If the dnsName is specified as test-machine, then all statistics per-
taining to test-machine are displayed.
oid Specifies the object identifier as reported by the SNMP agent.
period Specifies the polling interval.
Example: If the period is specified as 2, then the statistics that have been sched-
uled for data collection every 2 seconds are displayed.
active Specifies whether a data collection for a selected device is active or not. Possi-
ble values are true or false. If the value is false, data collection is not available
for the device.
save Specifies whether data collection for the selected device is saved or not.
SNMP Version Specifies the SNMP agent version, such as v1, v2, v3 data is collected from.
User Name User name of the user.
Context Name Specifies the name for the custom view you are creating or modifying. If no value
is specified in this field, default values such as Configured Collection0,
Configured Collection1, or Configured Collection2 are created.
agent Specifies the agent name.
For example, if the agent name is specified as Node1agent, then only statistics
from the data that is collected from that agent is displayed.
port Specifies the port number from which the agent is listening for data collection re-
quests.
NOTICE: The default SNMP agent port is 161.

Last Counter Value The time at which the data collection was scheduled for in the previous cy-
cle.Specifies a numeric value. Those statistics (counter type OIDs only) whose
last collected value equals the value specified are displayed.

122
 MN002730A01-AD
Chapter 3: SA Operation

Object Details
Description
Field
lastTime Value The time at which the data collection was scheduled for in the previous cycle.
timeVal The time at which the data collection is scheduled for in the subsequent cycle.
Is Multiple Polled Specifies the type used to poll the column value of the tables.
Data
True: Displays only those statistics which are of type MultiplePolledData.
False: Displays statistics other than MultiplePolledData.
All: Displays all statistics, irrespective of their type (node, interface, multiple).
threshold Specifies whether to display data, based on the thresholds set.
All: Displays all statistics, with and without thresholds.
True: Displays only those statistics which have thresholds associated.
False: Displays only those statistics which do not have thresholds associated.
Policy Name The default PollingObject name.
Save Absolutes A check box to enable or disable the save function.
Log File Specifies a log filename (string), based on the statistics you want to display.
Parent Object Specifies the name of the managed object whose statistics you view.
Threshold List Specifies the name of the thresholds in comma-separated format.
Current Save Count Specifies the current save count (numeric value).
Failure Count Specifies the failure count as a numeric value.
Example: If the failure count is set as 2, all statistics whose failure count is set as
2 are displayed.
protocol Specifies the name of a protocol.
Example:SNMP, TL1.
Poller Name Specifies the name of a poller.
Save Poll Count Specifies the save poll count (numeric value). All statistics with the specified
save poll count are displayed.
groupName Specifies the group.
Failure Threshold Specifies the save failure threshold value (numeric value). All statistics with the
specified failure threshold value are displayed.
Save On Threshold Possible values are true or false. A true value indicates that the collected da-
ta is saved only when it exceeds the threshold.
NOTICE: The default value is false.

timeAvg Possible values are true or false. Calculated for Counter type OIDs. The col-
lected data is an incremental value. At one point, it reaches the final value and
resets to zero. As this reset happens soon and often, it is preferred that a delta
value is derived from two consecutive polls.
NOTICE: The default value is false.

123
MN002730A01-AD
Chapter 3: SA Operation

3.14.4
Statistics Operations
SA allows you to add, remove, and modify a statistic.
However, you can add a statistic only if you are a member of Motorola Solution Support Center (SSC)
personnel.
IMPORTANT: Do not edit any fields in the Statistic Properties user interface. You can only
perform the following actions:
• Enable or disable collection (the Active field of the Statistics Properties Table)
• Modify the collection interval (the Period field of the Statistics Properties Table)

3.14.4.1
Adding Statistics
Procedure:
1 In the main navigation tree, select Performance → Configured Collection.
The Configured Collection window appears on the right-hand side of the panel, displaying all
configured devices.

2 In the main menu, select Edit → Add Statistic or press CTRL + K.

The Object Details dialog box appears.

3 Specify appropriate values in the fields and click Next.

NOTICE: For information on each of the fields, see Statistic Properties on page 121.

4 Optional: Add more properties by performing the following actions:

a In the Object Details dialog box, click Additional Props.
The Polled Data Additional Properties dialog box appears.

b In the Property Name and Value fields, specify the property name and its value respectively.
5 Optional: In the Polled Data Additional Properties dialog box, add a property by clicking More.
6 Optional: In the Polled Data Additional Properties dialog box, remove rows of properties by
clicking Fewer.
7 Optional: In the Polled Data Additional Properties dialog box, remove a property by selecting
the property and clicking Remove.
8 Finish adding a new statistic by clicking OK.
In the Configured Collections panel, the statistic added for the device is displayed.

3.14.4.2
Modifying Statistics
Procedure:
1 From the main navigation tree, select Performance → Configured Collection.
The Configured Collection window appears on the right-hand side of the panel, displaying all
configured devices.

124
 MN002730A01-AD
Chapter 3: SA Operation

2 Select the statistic that you want to modify and select Edit → Modify Statistic.
The Object Details dialog box appears.

3 Make appropriate changes.

4 Click Modify.
Data collection for the selected device is enabled.

3.14.4.3
Removing Statistics
If you want to stop the data collection for a statistic temporarily, do not delete the statistic. Instead, you
can disable (uncheck) the Active property of the statistic, temporarily stopping data collection for the
device. You can check the Active property to enable data collection in the future.

Procedure:
1 From the Navigation View panel, select Performance → Configured Collection.
2 In the Configured Collection window, select the statistic that you want to delete.
3 From the main menu, select Edit → Remove Statistic.
4 In the confirmation dialog box, click Yes.
User properties associated with the statistics are deleted.

3.14.5
Enabling Collections
You can enable the data collection for a particular statistic during runtime.

Procedure:
1 From the main navigation tree, select Performance → Configured Collection.
The Configured Collection window appears on the right-hand side of the panel, displaying all
configured devices.

2 In the Hosts column, select the host that you want to enable.
3 Double-click the row a statistic that you want to enable.
The Object Details window appears.

4 In the Object Details window, select the Active check box.

5 Click Modify.
Data collection for the selected device is enabled.

3.14.6
Disabling Collections
You can disable the data collection for a particular statistic during runtime.

Procedure:
1 From the main navigation tree, select Performance → Configured Collection.
The Configured Collection window appears on the right-hand side of the panel, displaying all
configured devices.

2 From the Hosts column, select the host that you want to disable.

125
MN002730A01-AD
Chapter 3: SA Operation

3 Double-click the row with a statistic that you want to disable.

The Object Details window appears.

4 In the Object Details window, clear the Active check box.

5 Click Modify.
Data collection for the selected device is disabled.

3.14.7
Searching Configured Collections
You can search a configured collection and view the statistics of individual devices. You can search
configured collections by any of the statistics parameters.

Procedure:
1 From the main navigation tree, select Configured Collection.
2 From the menu bar, select View → Search.
The Search window appears.

3 Select a parameter.
Step example: You can select Name, ID, DNS Name, and others.
NOTICE: You can also specify if the selected parameter starts with the name or ends
with the name, and others.
4 Click Search.
The Configured Collection lists the statistics that match your search.

3.14.8
Plotting Collected Statistics
Follow this procedure to view a graph for the collected data within a certain date range. You can view
the collected data (statistics) by using graphs and tables. They help to analyze the statistics gathered
over a long period.

Procedure:
1 From the Navigation View panel, select Performance → Configured Collection.
2 In the Configured Collection window, in the Host column, click the host for which you want to
plot collected statistics.
The hosts are displayed on the right-hand side.

3 Right-click the row for which you want to plot collected statistics and from the main menu, select
Show Collected Statistic.
4 In the Collected Graph Viewer window, change the chart type by clicking a chart icon of your
choice.
You can also view the collected data in the form of a table by selecting Table.

126
 MN002730A01-AD
Chapter 3: SA Operation

NOTICE: By default, the line chart graph type is displayed. You can change the chart
type to any of the following types:
• Line chart
• Bar chart
• Area chart
• Scatter chart
• X-Y chart
• Table
5 In the Date Range Settings area, select a date range. Click Plot Chart.
• To view the graph for the last 24 hours, select the Last 24hrs option button.
• To view the graph for today, select the Today option button.
• To view the graph for data collected over the last seven days, select the Last one week
option button.
• To view a graph for a specific period, select the Custom option button and specify the dates
in the From and To fields.
The custom date range can be displayed for the period of 30 days or less. If you set a custom
date range that is longer than 30 days, no statistics are displayed.
6 Save your plotted graph locally to a .png file by clicking Save.
The graph appears along with a legend. The legend lists object identifiers (OIDs) that are unique
identification numbers of the interface of a managed resource.

3.14.9
Plotting Current Statistics
Plotting current statistics (performance data) helps to view the updated data. In the collected statistics,
only the past data is displayed and it is not updated. The current statistics are instantly collected from
the device and plotted in graphs. On request, System Advisor (SA) queries the devices and collects the
data. You can view the current data (statistics) by using graphs or tables.

Procedure:
1 From the Navigation View panel, select Performance → Configured Collection.
2 In the Configured Collection window, in the Host column, click the host for which you want to
plot current statistics.
The hosts are displayed on the right-hand side.

3 Right-click the row for which you want to plot current statistics and from the main menu, select
Show Current Statistic.
4 Optional: In the CurrentGraphViewer window, change the chart type by clicking a chart icon of
your choice.
You can also view the current data in the form of a table by selecting Table.

127
MN002730A01-AD
Chapter 3: SA Operation

NOTICE: By default, the line chart graph type is displayed. You can change the chart
type to any of the following types:
• Line chart
• Bar chart
• Area chart
• Scatter chart
• X-Y chart
• Table
5 Optional: Define how often data is gathered for the statistics by setting the Polling interval
value.
You can set the Polling interval value to 10 seconds or higher.
Step example: Set the Polling interval value to 30 seconds to gather data for a managed
resource statistics every 30 seconds.
6 Optional: Stop the process of gathering data for statistics by clicking Stop Poller. To start the
process again, click Start Poller.
Current statistics are collected all the time. With the Stop Poller and Start Poller options, you
can stop the process of gathering statistics and gather statistics from a specific period.
7 Optional: Clear your plotted graph by clicking Clear Graph.
Current statistics are collected all the time. With the Clear Graph option, you can clear the
gathered data and start gathering statistics from a specific period.
8 Optional: Save your plotted graph locally to a .png file by clicking Save.
The graph appears along with a legend. The legend lists object identifiers (OIDs) that are unique
identification numbers of the interface of a managed resource.

3.14.10
Zooming in on Plotted Graphs
SAllows you to zoom in on a graph for a better view. You can zoom in on one axis or on both axes of
the graph, that is the Domain Axis and Range Axis.

Procedure:
Right-click the graph and select Zoom In:
• To zoom in on both axes, select Both Axes.
• To zoom in on the domain axis, select Domain Axes.
• To zoom in on the range axis, select Range Axes.
The axis or axes are zoomed in according to your requirements.

3.14.11
Zooming out on Plotted Graphs
SA allows you to zoom out on a graph for a better view. You can zoom out on one axis or on both axes
of the graph, that is the Domain Axis and Range Axis.

Procedure:
Right-click the graph and select Zoom Out:
• To zoom out on both axes, select Both Axes.

128
 MN002730A01-AD
Chapter 3: SA Operation

• To zoom out on the domain axis, select Domain Axes.

• To zoom out on the range axis, select Range Axes.
The axis or axes are zoomed out according to your requirements.

3.14.12
Viewing Performance Status of Managed Resources
You can view the performance status of a managed resource.
The following periods of time are available:
• Today
• Last 7 days
• Last 30 days
• Custom

Procedure:
1 From the main menu, select Administration → System Administration.
2 In the Module Details section, click Performance Status.
3 In the Node Name field, type the details of the device and click View Status.
4 Optional: View the performance status of a device for a period of time:
a In the Period field, select Custom.
The Start Date and End Date text boxes are enabled.

b In the Start Date and End Date text boxes, select the dates and click View Status.
The Performance Status Report screen with the following details appears:
• Statistic name
• Data collection status
• Last collection time
• Next collection time

3.15
Network Database Operations
Network Database serves as an inventory of network resources.
maintains the properties of all the managed resources, including network, physical devices and logical
entities. These managed resources and their properties are listed in a tabular format in the Network
Database View. Each row in the list corresponds to a managed resource.

3.15.1
Viewing Managed Resource Properties
Procedure:
1 In the Navigation View panel, click the Network Database node.
2 In the Network Database window, double-click a managed object.
The Managed Object Properties window appears, displaying the properties of the network you
selected

129
MN002730A01-AD
Chapter 3: SA Operation

3.15.2
Determining Reliable Communication Capability of a Managed
Resource
Some devices managed by SA are capable of Reliable Communication. This means that they are able
to communicate with SA sending informs by using a separate SNMP user, that is MotoInform. Devices
incapable of Reliable Communication use MotoMaster and communicate by sending traps. All users
can verify if managed resources are capable of Reliable Communication.

Procedure:
1 In the Navigation View panel, click the Network Database node.
2 In the Network Database window, double-click a managed resource.
3 In the Managed Resource Properties, perform the following actions:
a Select the Others tab.
b In the Other Properties area, search for the reliableCommCapable property.
If the property value is true, the managed resource is capable of reliable communication.

3.15.3
Exporting Network Inventory Data
Procedure:
1 In the Navigation View panel, click the Network Database node, or any custom network
database node.
2 Select Actions → Export Topology Data.
The Export Topology Data window appears.

3 Specify a file name for your selection and click Save.

The file is saved to the local client PC.

3.16
Associated Managed Resources Operations
To get a better idea of a fault that affects one or multiple devices or their particular components, you
can filter the Network Database view to display only the associated objects, based on the selected
alarms in the Alarms view or managed objects in the Network Database.
When the list of managed resources is narrowed down only to the associated objects, fault tracking
becomes easier.
The following rules define which elements are associated:
• All elements inside a subnet are related to a network element but not the other way round. For
example, when you view associated managed resources for a network element, all devices that are
located in the same network are displayed. However, when you view associated managed
resources for a device, the network is not displayed.
• Generic Nodes, which represent IP managed devices, are associated only to a network they belong
to.
• Device Managed Resources (DMR) are associated to Sites and Network they belong to.
• Logical Managed Resources (LMR) are related to DMRs that they belong to. When you view
associated managed resources for an LMR, the DMR that the LMR belongs to is displayed. When
you view associated managed resources for DMR, all LMRs that belong to this DMR are displayed.

130
 MN002730A01-AD
Chapter 3: SA Operation

• Once a related element is displayed, all associated elements are also displayed.

3.16.1
Viewing Associated Managed Resources from the Alarms Window
Procedure:
1 In the Navigation View panel, click the Alarms node.
2 From the Alarms window, select one or multiple alarms.
NOTICE: If no alarms are available in the Alarms window, open the Network Database
window to see managed resources.
3 Right-click the selection and click Associated Managed Resources.
NOTICE: To sort items by column, hold CTRL and click the column name.

A temporary Network Database custom view containing the associated managed resources appears.

3.16.2
Viewing Associated Managed Resources from the Network
Database Window
Procedure:
1 In the Navigation View panel, click the Network Database node.
2 In the Network Database window, select one or multiple elements.
3 Right-click the selection and select View Associated Managed Resources.
NOTICE: To sort items by column, hold CTRL and click the column name.

In the Network Database window, a temporary custom view containing the associated managed
resources appears.

3.17
Unknown Devices
An unknown device is a device whose device type is unrecognizable, or a device that does not have a
Simple Network Management Protocol (SNMP) agent running.
These devices are discovered as generic nodes.

3.18
Security Management Operations
Security is the assurance of legitimate use, maintenance of confidentiality, data integrity, and ability to
audit the Network Management operations.
It involves identifying the assets, threats, and vulnerabilities of the system. As a result, you can take
protective measures against unintended use of the system. The Security Administration module
enables you to manage security information. Different users can perform different security operations,
depending on their permissions.
This section helps the administrator to create new users, or new groups of users, enabling the
administrator to control the different security levels. New users, or new groups of users are allowed to
see only selected information.

131
MN002730A01-AD
Chapter 3: SA Operation

After logging on, all the operations available to you are based on your group. Therefore, user
administration is a prime function of the administrators.
The following functions can be managed under Security Management:
• Providing group-based authorization where users can be assigned to groups that have configured
levels of authorization, and that provide specific authorizations to them.
• Providing fine-grained access control for specific groups, views, and operations.
• Limiting the access for some users to specific subsets of objects or instances (for example, user
access can be limited to a specific device).
• User activity log, called Audit Trails, containing:
- Operations invoked by the user.
- The name of the user who invoked the operation.
- Data and time of invocation.
- Target device/object on which the operation was invoked.
- The status of the operation.
- The category of invoked operation.

3.18.1
Audit Trails Operations
Audit trails enable you to view the operations performed in SA.
The audit trail identifies all operations that have been performed, displaying also:
• The time
• Whether the audit was successful
• The category
• The audited object
Clear the trails after they have been reviewed.
You can perform the following operations:
• View the audit trail details of all the users or a single user.
• Sort the details by user, operation, time, status, category, and audited object, by clicking the
appropriate column heading.
• Search for audit details, based on the properties.
• Clear the audit trails when you no longer want to manage them.

3.18.1.1
Viewing Audit Trails for All Users
You can view various operations performed by the users, along with the status of whether the
operation was a success or failure. You can view the operation categories such as Fault, Topo,
Provisioning, Configuration, or DEFAULT. For operations that involve adding objects, such as the Add
Node operation, you can also view object details.

Procedure:
1 From the main menu, select Administration → Security Administration.
2 In the Security Administration window, from the main menu select View → Audit Trails.
3 Optional: In the Audit Screen window, sort audit trails:

132
 MN002730A01-AD
Chapter 3: SA Operation

• To sort all audit trails, click a column header.

• To sort only the audit trails that are currently displayed, click a column header while holding
CTRL.
4 Optional: Clear an audit trail by selecting an audit entry and clicking Clear Audit.
• To select a single audit trail, click it.
• To select contiguous audit trails, hold SHIFT and click audit trails.
• To select non-contiguous audit trails, hold CTRL and click audit trails.
5 Optional: To view new records, click Refresh.

3.18.1.2
Viewing Audit Trails on the SA Client Web Interface
Procedure:
1 From the main menu, select Administration → System Administration.
The SA client web interface appears.

2 In the System Administration panel, click the Audit Trails icon.

3.18.1.3
Viewing Audit Trails for Single Users
You can view various operations performed by the users, along with the status of whether the
operation was a success or failure. You can view the operation categories such as Fault, Topo,
Provisioning, Configuration, or DEFAULT. For operations that involve adding objects, such as the Add
Node operation, you can also view object details.

Procedure:
1 From the main menu, select Administration → Security Administration.
2 In the Security Administration window, expand the Users node, right-click a user and select
Audit Trails.
3 Optional: In the Audit Screen window, sort audit trails:
• To sort all audit trails, click a column header.
• To sort only the audit trails that are currently displayed, click a column header while holding
CTRL.
4 Optional: Clear an audit trail by selecting an audit entry and clicking Clear Audit.
• To select a single audit trail, click it.
• To select contiguous audit trails, hold SHIFT and click audit trails.
• To select non-contiguous audit trails, hold CTRL and click audit trails.
• To view new records, click Refresh.

3.18.1.4
Searching Audit Trails
Procedure:
1 From the main menu, select Administration → Security Administration
2 In the Security Administration window, perform one of the following actions:

133
MN002730A01-AD
Chapter 3: SA Operation

• To search audit trails for all users, from the main menu, select View → Audit Trails.
• To search audit trails for a specific user, expand the Users node, right-click a user and select
Audit Trails.
3 In the Auth Audit window, select Edit → Search.
4 In the Search dialog box, perform the following actions:
a Select the property on which the search has to be performed.
b Select the condition from the combo box.
c Specify the value in the text box.
d Click Search.
NOTICE:
After viewing the audit details, you can view all the details again on the same page by
clicking Show All.
To search the Audit Trails more precisely, click More. It allows you to define additional
criteria. To remove additional criteria, click Fewer.

3.18.1.5
Exporting Audit Trails
Procedure:
1 From the main menu, select Administration → Security Administration
2 In the Security Administration window, perform one of the following actions:
• To export audit trails for all users, from the main menu, select View → Audit Trails.
• To export audit trails for a specific user, expand the Users node, right-click a user and select
Audit Trails.
3 In the Auth Audit screen, click Export.
4 In the Export Data to Server dialog box, perform the following actions:
a Define the type of exported data by choosing the appropriate radio button.
b Enter the file name. Click Export.
5 Define the type of exported data by choosing the appropriate radio button.
6 Enter the file name. Click Export.
The file is exported on the server side.

3.18.2
Groups Operations
SA enables you to organize different types of users into groups.
You can classify them by a set of common operations, or provide specific permissions to various
groups. This practice saves time when changing permissions for all users in a specific group. It also
makes it easier to add a new user to an existing group.
A group is a logical collection of users grouped to access common information or perform similar tasks.
Any administration done for the group is reflected in the individual members (or users) of the group.

134
 MN002730A01-AD
Chapter 3: SA Operation

3.18.2.1
Adding Groups
You can add new groups to assign to it permissions that are different from those of an existing group.

Procedure:
1 From the main menu, select Administration → Security Administration
2 In the Security Administration window, from the File menu, select New → Add Group.
The Groups Adminstration window appears.
Figure 39: Group Adminstration Window

3 In the Enter a group name (*) field, enter the name of the group. Click Next.
4 From the Operations Tree Root list, select the permissions you want to allow or disallow for all
users in this group. Click Finish.

135
MN002730A01-AD
Chapter 3: SA Operation

Figure 40: Groups Adminstration – Operations Tree Root

A group is added in the Groups node of the Security tree.

3.18.2.2
Assigning Users to Groups
By assigning users to groups, you can limit access to specific subsets of SA. The groups provide
specific permissions and levels of permissions. For example, user access can be limited to specific
types of devices. The users assigned to the group are displayed in the Members tab.

Procedure:
1 From the main menu, select Administration → Security Administration
2 In the Security Administration window, perform the following actions:
a Expand the Groups node and click the group to which you want to assign users.
b Click the Members tab displayed on the right-hand side.
c Click Setting Users.
3 In the Select Users dialog box, assign one user or many users to a group:

• To assign one user to a group, click the user in All Users and click the Add icon .
• To assign many users to a group, select multiple users by using SHIFT or CTRL.
4 Click OK.
The new group member appears in the Members tab.

136
 MN002730A01-AD
Chapter 3: SA Operation

3.18.2.3
Unassigning Users from Groups
Procedure:
1 From the main menu, select Administration → Security Administration
2 In the Security Administration window, perform the following actions:
a Expand the Groups node and click the group to which you want to assign users.
b Click the Members tab displayed on the right-hand side.
c Click Setting Users.
3 In the Select Users dialog box, in the Selected Users area, click the user you want to unassign

and click Remove .

4 Click OK.
The removed group member disappears from the Members tab.

3.18.2.4
Deleting Groups
Procedure:
1 From the main menu, select Administration → Security Administration
2 In the Security Administration window, expand the Group node, right-click a group you want
to delete and click Delete.
3 Confirm the deletion by clicking Yes.
The group is removed from the database.

3.18.3
Users Management
A user is an individual who logs on to SA.
The user account is configured to perform only a specific set of functions. Before anyone has access to
the SA client, add them as a user to the SA server application database. After a user is created, they
can be given specific permissions, added to groups, and given specific permissions belonging to the
group.

3.18.3.1
Users Operations
You can add a user at any time.
By default, the new user has login permissions only. You provide access to various modules by making
the user a member of pre-configured groups, or by directly assigning permissions to the user.
You can add a new user from the:
• Application Client
• Command Line

137
MN002730A01-AD
Chapter 3: SA Operation

3.18.3.1.1
Adding Users from the SA Client
Procedure:
1 From the main menu, select Administration → Security Administration

2 In the Security Administration window, click Add User .

3 In the User Administration dialog box, enter the user name and password. Click Next.
NOTICE: The password must meet the following criteria:
• must be at least 15 characters long
• cannot exceed 64 characters
• must have the following characteristics:
• at least one lower case alphabet (a-z)
• at least one upper case alphabet (A-Z)
• at least one digit (0-9)
• at least one of the following special characters: ` ! @ # $ % ^ & * ( ) _ - + = [ ] { } ; :
' \" \ | , < . > / ? "
4 In the User Administration window, set the expiration period. Click Next.

If…
If you want the user account to
expire after a specific period,
Then…
perform the following actions:
a Clear the Account never expires check box.
b In the This user account expires in field, enter a
number of days.

If you do not want the user ac- leave the Account never expires check box selected.
count to expire,
5 Optional: Assign the user with an existing group:
a Select the Group-based permissions check box.
b In the Assign groups for the user panel, select the check boxes corresponding to the
groups to which you want to assign the user.
NOTICE: Click the arrow in the panel to display a pop-up window with the permissions
for the group. Based on the permissions, you can assign groups to the user.
6 Create a group to which you want to associate the user:
a In the Enter the new group name field, enter a group name.
b Click Add Group.
The Assign Permissions dialog box appears.

7 To directly assign permissions to the user, perform the following actions:

a Check the Direct assignment check box.
b Click Permissions.
The Assign Permissions dialog box appears.

138
 MN002730A01-AD
Chapter 3: SA Operation

8 When you finish assigning permissions to the user, click Finish.

A new user appears in the Security tree on the left-hand side of the Security Administration window.

3.18.3.2
Changing the User Profile
You can change the profile of a user according to your requirements. For example, you can change a
profile to modify the account expiration date or remove the temporary account lock caused by entering
an invalid password several times in a row.

Procedure:
1 From the main menu, select Administration → Security Administration
2 In the Security Administration window, expand the Users node and click the user whose
profile you want to change.
The Security Administration tabs are displayed on the right-hand side.

3 Click the User Profile tab and select Setting Profile.

The User Profile dialog box appears.

4 To enable or disable the user, clear the No change in status check box and from the drop-
down menu, select enable or disable as appropriate.
5 Change the account and user expiration date as appropriate and click OK.
The Security Administration window displays the Groups and Users nodes on the left-hand side.
Various types of icons displayed under the Users node provide immediate information about the status
of a specific user.

3.18.3.3
Unlocking the User Account
You can unlock a user account that is temporarily locked for one hour due to entering an invalid
password three times in a row.

Procedure:
1 From the main menu, select Administration → Security Administration
2 In the Security Administration window, expand the Users node and click the user whose
account you want to unlock.
The icon represents users with a locked account on the Security tree.
The Security Administration tabs are displayed on the right-hand side.

3 Click the User Profile tab and select Setting Profile.

The User Profile dialog box appears.

4 To unlock the user account, clear the Account locked check box. Click OK.
The account locked check box is active only when a user account is locked.
The Security Administration window displays the Groups and Users nodes on the left-hand side.
Various types of icons displayed under the Users node provide immediate information about the status
of a specific user.

139
MN002730A01-AD
Chapter 3: SA Operation

3.18.3.4
Assigning Groups to Users
You can assign the users that you created to existing groups.

Procedure:
1 From the main menu, select Administration → Security Administration
2 In the Security Administration window, expand the Users node and click the user whose
profile you want to change.
The Security Administration tabs are displayed on the right-hand side.

3 Click the Member Of tab and select Setting Groups.

The Select Groups dialog box appears.

4 Assign one group or many groups to a user:

• To assign one group to a user, click the group in the All Groups list and click the Add icon.
• To assign many groups to a user, select multiple groups by using SHIFT or CTRL.
5 Optional: Unassign a group from a user:
a In the Selected Groups list, click a group.
b Click the Remove icon.
6 Click OK.
The groups assigned to the user are displayed in the Groups for list in the Members Of tab.

3.18.3.5
Changing the User Password when in the Security Administrator Group
A user with the security administrator role or belonging to the security administrator group can change
the passwords for any user at any time.

Procedure:
1 From the main menu, select Administration → Security Administration
2 In the Security Administration window, expand the Users node and click the user whose
password you want to change.
The user details appear on the right-hand side.

3 From the Security Administration window, select Edit → Change Password.

The Change Password dialog box appears.

4 In the password fields, enter the new password. Click OK.

3.18.3.6
Deleting Users
Delete a user when you no longer want the user to have access to the SA.

Procedure:
1 From the main menu, select Administration → Security Administration.
2 In the Security Administration window, expand the Users node, right-click a user you want to
delete, and click Delete.

140
 MN002730A01-AD
Chapter 3: SA Operation

3 Confirm the deletion by clicking Yes.

3.18.4
Operations Management
The operations tree contains a list of operations (also referred to as permissions) that are provided by
default in SA.
The operations are logically arranged in a tree structure with parent and child operations. You can add
new operations when they are needed and delete obsolete operations.

3.18.4.1
Default Operations
The operations tree contains a list of operations that are provided by default in SA. Assigning different
operations to different users is an administrative function.

Administrative Operation
Administrative Operation Services provide information on the operation and the description of
administrative services.

Table 9: Security Administration

Security Administration provides the following security-related operations that can be configured in the
table . You can provide permissions for users only for certain security operations and restrict other
security functions. For instance, you can provide permissions for users to create groups, but restrict
permissions to delete groups.

Operations Description
Group Operations Add Group Disabling this operation pre-
vents the user from adding a
group.
Remove Group Disabling this operation pre-
vents the user from removing
a group.
Set Permission Disabling this operation pre-
vents the user from setting
permissions or operations to
groups.

Table 10: System Administration

Operations Description
System Administration Disabling the System Administration op-
eration prevents the user from accessing
the System Administration page in both
the SA client and SA client web inter-
face..

141
MN002730A01-AD
Chapter 3: SA Operation

Table 11: Runtime Administration

Operations Description
Runtime Administration Disabling the Runtime Administration operation prevents the user
from managing JVM in the SA client web interface.

Table 12: Shutdown Web NMS Server

Operations Description
Shutdown Web NMS Serv- Shutdown Web NMS Server is an operation used internally only by
er the root user. Disabling this operation for the root user may cause
problems with disabling the Server.

Table 13: Terminate Client

Operations Description
Terminate Client Disabling the Terminate Client operation prevents the user from
shutting down connected Clients using System Administration.

Events

Table 14: Events

The Events operations provide permissions to work with event filters, export, and save events to file.

Operations Description
Event Filters Get Event Filters Disabling this operation pre-
vents the user from viewing
the existing event filters in SA.
Set Event Filters Disabling this operation pre-
vents the user from modifying
or adding an event filter.
Export Events Disabling this operation prevents the user from exporting the list
of events.
Save Events To File Disabling this operation prevents the user from saving event fil-
ters to a file.

Topology

Table 15: Topology

The Topology operations provide permissions to work with topology data displayed in the Network
Database view.

Operations Description
Modify Object Disabling this operation prevents the user from alter-
ing Managed Resource properties.
Manage and Unmanage Objects Disabling this operation prevents the user from man-
aging or unmanaging an object or a network element.

142
 MN002730A01-AD
Chapter 3: SA Operation

Operations Description
Discovery Configuration Disabling this operation prevents the user from con-
figuring the discovery process
Export Topology Data Disabling this operation prevents the user from ex-
porting the topology data
Modify Managed Resource Properties Disabling this operation prevents user from modifying
managed resource properties
Delete Object Disabling this operation prevents the user from delet-
ing an object or a network element.
Refresh Node Disabling this operation prevents the user from re-
freshing a node.

Policy

Table 16: Policy

The Policy operations provide permissions to work with policies.

Operation Description
Add Policy Disabling this operation prevents the user from add-
ing a policy.
Delete Policy Disabling this operation prevents the user from delet-
ing an existing policy.
Update Policy Disabling this operation prevents the user from updat-
ing an existing policy.
Execute Policy Disabling this operation prevents the user from exe-
cuting an existing policy.
Stop Policy Disabling this operation prevents the user from stop-
ping an existing policy.

User Administration

Table 17: User Administration

The User Administration operations provide permissions to work with local accounts, users, and
groups.

Operation Description
User Configuration Disabling this operation prevents the user from modi-
fying user configuration in the SA client web interface.
Add Users Disabling this operation prevents the user from add-
ing new users.
Assign User to Group Disabling this operation prevents the user from as-
signing a user to a group.
Remove Users Disabling this operation prevents the user from re-
moving a user.
Remove User from Group Disabling this operation prevents the user from re-
moving a user from a group.

143
MN002730A01-AD
Chapter 3: SA Operation

Operation Description
Change Password Disabling this operation prevents the user from
changing the password of a user.
Get List of Users Disabling this operation prevents the user from view-
ing the list of users added. Applicable only to the SA
client web interface (the link to access the list is disa-
bled).
Set User Permission Disabling this operation prevents the user from setting
operations or permissions for existing users.
Set User Profile Disabling this operation prevents the user from setting
profiles for existing users.
Clear Audit Trails Disabling this operation prevents the user from clear-
ing audit trails in the SA client.
Change Self Password Disabling this operation prevents the user from
changing the password.

Alerts

Table 18: Alerts

The Alerts operations provide permissions to work with alarms displayed in the Alarms view and with
alert filters.

Operations Description
Export Alarms Disabling this operation prevents user from exporting the list of
alerts.
Alert Filters Get Alert Filters Disabling this operation pre-
vents the user from viewing
existing alert filters.
Set Alert Filters Disabling this operation pre-
vents the user from setting
new alert filters.
Alert User Operations Set Alert Annotation Disabling this operation pre-
vents the user from annotating
an alarm.
Get Alert Details Disabling this operation pre-
vents the user from viewing
the details of an alarm.
Get Alert History Disabling this operation pre-
vents the user from viewing
the history of an alarm.
Alert Pickup Disabling this operation pre-
vents the user from picking up
an alarm.
Delete Alerts Disabling this operation pre-
vents the user from deleting
an alarm.

144
 MN002730A01-AD
Chapter 3: SA Operation

Operations Description
Save Alerts To File Disabling this operation pre-
vents the user from saving
alarm filters to a file.
Clear Alerts Disabling this operation pre-
vents the user from clearing
an alarm.

NBI Configuration

Table 19: NBI Configuration

The NBI Configuration operations provide permissions to configure North Bound Interface (NBI).

Operation Description
NMS Configuration Disabling this operation prevents the user from configuring North
Bound Interface (NBI).

Credentials Configuration

Table 20: Credentials Configuration

The Credentials Configuration operations provide permissions to update and test credentials
configuration.

Operation Description
Update Credentials Config- Disabling this operation prevents the user from modifying credentials
uration configuration.
Test Credentials Configu- Disabling this operation prevents the user from testing the creden-
ration tials configuration.

Device Command

Table 21: Device Command Configuration

Operation Description
Device Command Disabling this operation prevents the user from issuing commands to
the device.

Device Synchronization

Table 22: Device Synchronization

The Device Synchronization operation provides permissions to manually synchronize fault managed
devices.

Operation Description
Device Synchronization Disabling this operation prevents the user from performing force syn-
chronization on the device.

145
MN002730A01-AD
Chapter 3: SA Operation

Abort All Discovery Jobs

Table 23: Abort All Discovery Jobs Configuration

The Abort All Discovery Jobs operation provides permissions to abort discovery jobs started by other
users.

Operation Description
Abort All Discovery Jobs Disabling this operation prevents the user from aborting a discovery
job started by a different user. Users can always abort discovery
jobs which they initiated themselves.

Server Logs Access

Table 24: Server Logs Access Configuration

The Server Logs Access operation provides access to server logs.

Operation Description
Server Logs Access Disabling this operation prevents the user from accessing the server
logs by using a web browser. The access is available from Tools →
Server Logs.

Event Archive Access

Table 25: Event Archive Access Configuration

Operation Description
Event Archive Access Disabling this operation prevents the user from accessing the event
archives by using a web browser. The access is available from Ad-
ministration → Security Administration

Performance Archive Access

Table 26: Performance Archive Access Configuration

Operation Description
Performance Archive Ac- Disabling this operation prevents the user from accessing the per-
cess formance archives by using a web browser. The access is available
from Logging → Performance Archive.

Configure Logging

Table 27: Logging Configuration

Operation Description
Configure Logging Disabling this operation prevents the user from configuring the log
information.

146
 MN002730A01-AD
Chapter 3: SA Operation

Launch Management Application

Table 28: Launch Management Application Configuration

The Launch Management Application operation provides access to the launch management
application for fault managed devices.

Operation Description
Launch Management Ap- Disabling this operation prevents the user from accessing the man-
plication agement application.

View All Login Attempts at Startup

Table 29: View All Login Attempts at Startup Configuration

The View All Login Attempts at Startup operation allows you to view logon attempts for all users.

Operation Description
View All Login Attempts at Disabling this operation prevents the user from being able to view
Startup login attempts for other users at startup of the application. You can
view all login attempts by clicking Details in the Last Login Infor-
mation dialog box that opens after starting the SA client.

View Associated Managed Resources

Table 30: View Associated Managed Resources

The View Associated Managed Resources operation allows you to view all associated managed
resources.

Operation Description
View Associated Managed Disabling this operation prevents the user from viewing associated
Resources managed resources by using context menu in SA.

Asset Management Information

Table 31: Asset Management Information Configuration

The Asset Management Information operation provides access to the asset management information
for devices that support this operation, for example PTP, Extreme switches.

Operation Description
Asset Management Infor- Disabling this operation prevents the user from accessing asset
mation management information for devices that support this operation.

3.18.4.2
Operations Assignment
You can assign operations (include or exclude privileges) for a group or for a particular user.
Assigning operations for a group automatically sets the same privileges for the users in that group.

147
MN002730A01-AD
Chapter 3: SA Operation

3.18.4.2.1
Assigning Operations to Users
Procedure:
1 From the main menu, select Administration → Security Administration
2 In the Security Administration window, expand the Users node and click the user to which you
want to assign operations.
3 Click the Permitted Operations for User tab displayed on the right-hand side.
All operations allowed or not allowed for that user are displayed in the Permissions For User
list.

4 Click Set Permissions.

5 In the Assign Permissions window, grant the appropriate permissions:
• To include the permissions you want to grant to the user, select appropriate check boxes so
that a tick symbol is displayed.
• To prevent specific permissions from being granted to the user, select the check box so that
an x symbol is displayed.
NOTICE: Leaving the check box empty for an operation is not an authorized operation.
The check box inherits its immediate parent operation permission.
6 To reset the changes without closing the window, click Reset, to exit without saving, click
Cancel.
7 Click Done.

148
 MN002730A01-AD
SA Maintenance

Chapter 4

SA Maintenance
Maintenance procedures help you back up and secure data on the System Advisor (SA) application.

4.1
System Advisor Backup and Restore
The System Advisor (SA) critical information is backed up by the ESU server and by the SA logging
feature.

ESU Backup and Restore

The Enhanced Software Update (ESU) server is used to back up the SA configuration and database.
The ESU server backs up the following information:
• Managed resource inventory (Network Database) and customizations to this view
• SA groups and users
• SNMPv3 credentials (includes default, device, and NBI information)
• E-mail (paging) and alarm sound file configuration
• E-mail certificate
• Web Service credentials
• License cache
The SA license key is installed during the first system installation. The license key requires neither
backup nor installation.
In the ESU client, you can create two types of backups: on demand and scheduled. The ESU client
also allows you to upload an SA backup that is not currently stored on the ESU server. The SA data
backups can take place without disabling the SA server.
From the ESU client, you can restore the selected backup on the SA and bring the server back to a
previous state. Restoration procedures are performed to recover from any accidental loss of data, or if
the entire server application and its data are lost. SA validates the data being restored for consistency
with the software installed during the restore process. If any discrepancies are detected, an error is
reported.
The ESU server comes from the factory with a predefined Internet Protocol (IP) address and other
network configurations and is enabled by default.
For more information, see the following sections:
• Logging On to the ESU Client on page 150
• Backing Up the System Advisor Data on Demand on page 150
• Scheduling the System Advisor Data Backup on page 150
• Restoring the System Advisor Data on page 151
• Uploading a Backup to ESU on page 151
• SNMPv3 Synchronization on page 151

149
MN002730A01-AD
Chapter 4: SA Maintenance

SA Archives and Logs

The System Advisor creates server, events, performance, and call monitoring logs and stores them as
archive files for specific periods. You can download the log files manually from the SA webpage and
save them in a designated storage location for backup purposes.
For more information, see Retrieving System Advisor Archives and Logs on page 152.

4.1.1
Logging On to the ESU Client
The Enhanced Software Update (ESU) client is a web-based application that you can use to back up
and restore the System Advisor configuration and database.
Prerequisites:
From the system administrator, obtain the following information:
• Internet Protocol (IP) address of the ESU server
• Credentials of the operations user with privileges to use the ESU backup and restore functionality

Procedure:
1 In the web browser address field, enter: https://<ESU_SERVER_IP>/ui
where <ESU_SERVER_IP> is the Internet Protocol (IP) address of the ESU server.
2 On the login page, enter the operations user credentials.

4.1.2
Backing Up the System Advisor Data on Demand
The Enhanced Software Update (ESU) client allows you to back up the System Advisor (SA) data on
demand.
The SA data backups can take place without disabling the SA server.

Procedure:
1 In the ESU client, click the Backup link on the menu on the left side of the application.
2 Click the Run button from the listed applications for the specific one that requires backup.
Status of the operation changes to Started On <<TIME,DATE>>. Once the backup is created,
the status changes to Completed On <<TIME,DATE>>.

3 Optional: To see the details of the backup operation, click the Show link.

4.1.3
Scheduling the System Advisor Data Backup
The Enhanced Software Update (ESU) client allows you to schedule backups of the System Advisor
data.
The SA data backups can take place without disabling the SA server.

Procedure:
1 In the ESU client, click the Scheduled Backup link on the menu, on the left side of the
application.
2 Click New to create a new scheduled backup.
3 The page with parameters for the new scheduled backup is displayed.

150
 MN002730A01-AD
Chapter 4: SA Maintenance

4 After filling all required parameters, click Submit.

The new created scheduled backup is listed in the table, and can be modified or removed.

4.1.4
Restoring the System Advisor Data
By using the Enhanced Software Update (ESU) client, you can restore the backed-up System Advisor
(SA) data.
NOTICE: The ESU disables the SA server before the restore, and automatically enables the
server after the restore.

Procedure:
1 In the ESU client, click the Restore link on the menu, on the left side of the application.
2 From the Backup Name drop-down menu, select the backup file.
3 If the displayed file name is correct, from the listed applications, click Run for the file that has to
be restored.
4 The Status of the operation changes to Started On <<TIME,DATE>>.
5 Once the restoration is complete, the status changes to Completed On <<TIME,DATE>>.
6 Optional: To see details of backup operation., click the Show link.
Postrequisites: Verify if the restored SNMPv3 credentials are up to date. If the SNMPv3 credentials
are old, you must synchronize them. For more information, see SNMPv3 Synchronization on page 151.

4.1.5
Uploading a Backup to ESU
If you want to restore a System Advisor backup that is not currently stored on the Enhanced Software
Update (ESU) server, you can upload the backup file to the ESU and use it in a restore operation. After
uploading the file, you can navigate to the Restore page and use it in a restore operation.

Procedure:
1 In the ESU client, from the menu on the left side of the window, select Upload Files.
2 Select the backup file and click Upload.
The backup file is added to the list of available backups.

4.1.6
SNMPv3 Synchronization
The administrator must synchronize the SNMPv3 credentials after a system restore.
Synchronization is required if the archive used for restoration is older than the last date/time the
SNMPv3 credentials were modified. If the SNMPv3 configuration is not updated after the restore, SA
can be unable to communicate with one or more devices. Verify SNMPv3 credentials for the following
interfaces:
MotoMaster
The SNMPv3 user who uses all communications from SA to the devices.
MotoInformA or MotoInformB
The SNMPv3 user who uses all notifications (SNMP INFORM message) sent from devices to SA.

151
MN002730A01-AD
Chapter 4: SA Maintenance

MotoNorth and MotoNorthMotorola

The SNMPv3 credentials used by the North Bound Interface. Contact the Motorola Solution Support
Center (SSC) after the restoration process is complete. When the SNMPv3 configuration used for
remote monitoring is enabled, they can verify it.

4.2
Retrieving System Advisor Archives and Logs
System Advisor server, events, performance, and call monitoring logs are accessible from the SA
webpage as archive files. You can download the logs manually from the SA webpage to a selected
backup location.
SA does not provide the option to schedule automatic backups of the logs. However, your organization
can implement its own automation solutions.
Prerequisites:
Verify that an SA session is active. If no SA sessions are active, you cannot access the logs.
From your system administrator, obtain user credentials with appropriate privileges to access the
server, events, performance, or call monitoring logs.

Procedure:
1 Log on to the SA client with an account that has permissions to view the server, events,
performance, or call monitoring logs.
You can change accounts by using the Security Administration menu.
2 Select the type of logs that you want to view:
• To view the server logs, from the main menu, select Logging → Server Logs.
• To view the events logs, from the main menu, select Logging → Events Archive.
• To view the performance logs, from the main menu, select Logging → Performance
Archive.
• To view the call monitoring logs, from the main menu, select Logging → Call Monitoring
Archive.
In a browser window, a list of available log files is displayed. Server logs are organized in
folders.

3 Select the appropriate file.

For server logs, you must navigate to the appropriate folder first.
4 Save the file to the selected folder on the client PC or the selected network storage location.
NOTICE: After you save the files to the local client PC, you can move them to external
media for long-term storage.
5 Optional: Save multiple files by repeating step 3 through step 4.

4.3
Trap Overload Overview
In SA, the term trap is used to refer to informs and Web Service notifications. Traps are notifications
sent to SA by resources that SA manages. SA processes all traps it receives. In SA, processing means
converting traps into alarms and events and presenting them in this form in the SA client. SA can
process a finite number of traps at a time. When the number of traps that SA receives exceeds the

152
 MN002730A01-AD
Chapter 4: SA Maintenance

capacity of SA to process them, trap overload occurs, and the excessive traps are queued in the trap
buffer for processing according to their priority.

Overload Buffer States

The trap buffer is a finite space in which SA queues the excessive traps for processing. The trap buffer
has different states that reflect the number of traps that are queued in the trap buffer. The buffer states
are displayed in the overload buffer state bar in the lower right corner of the main SA window.
The following buffer state definitions explain how SA behaves depending on the number of traps
queued for processing in the buffer.
Clear
SA operates normally. SA processes all traps that are queued in the trap buffer. The queued traps
take less than 5% of the trap buffer capacity.
Minor
SA receives more traps than it can process. The queued traps take between 5%–70% of the trap
buffer capacity. When the overload buffer state changes to minor, based on trap statistics that are
available on the SA client web interface, you can verify if the managed resource that sends multiple
traps works correctly, and undertake necessary actions.
Major
SA receives more traps than it can process and cannot process the queued traps for a considerable
amount of time. The queued traps take between 70%–95% of the trap buffer capacity. When the
overload buffer state changes to major, based on trap statistics that are available on the SA client
web interface, you can verify if the managed resource that sends multiple traps works correctly, and
undertake necessary actions, for example unmanage the resource or clear traps sent by the
resource.
Critical
The trap buffer is almost full. The queued traps take up to 95% of the trap buffer capacity. SA
automatically clears the buffer to exit the critical state. Based on the configured cleanup
percentage, the overload buffer state changes to major, minor, or clear.
NOTICE: The hysteresis between the overload buffer states is 3%. As a result, the overload
buffer state changes from, for example, major to minor when traps take 67% of the trap
buffer capacity, though the threshold of the minor state is 70%. The hysteresis prevents
frequent state changes when the capacity of the trap buffer is right between 2 states.

Trap Processing Order

When the overload buffer state is clear, SA processes all traps in the order in which it receives the
traps. When the overload buffer state is minor, major, or critical, SA processes the queued traps
depending on the trap type and managed resource type. SA gives processing priority to:
• All types of traps that change the state of managed resources
The RTU and ZC traps are of the highest processing priority, SC traps are of high processing priority,
and transport managed resource traps are of normal processing priority. When traps are added to the
trap buffer, SA queues them for processing according to their priority.

Automatic Trap Cleanup

When the overload buffer state changes to critical, by default SA clears 20% of traps queued in the
buffer. You can modify the percentage of traps that SA automatically clears when the overload buffer
state changes to critical.
The order in which SA automatically clears the trap buffer depends on the priority of traps:
• Traps of the lowest priority are cleared from the trap buffer as the first ones

153
MN002730A01-AD
Chapter 4: SA Maintenance

• Traps generated by managed resources whose synchronization takes long are cleared from the
trap buffer as the last ones
After SA automatically clears the trap buffer, you are informed about it in a message. In the message,
SA asks you to recognize the fact that the automatic cleanup was performed by clicking OK. The
message also contains information about the number of automatic cleanups performed since your last
cleanup recognition, and about the date of the last cleanup.
This process explains how SA behaves when the trap buffer reaches the critical state.
1 SA initiates the process of removing a percentage of traps queued in the trap buffer.
2 SA identifies the percentage of traps of the lowest priority for removal.
3 SA removes all identified traps and schedules synchronization of the managed resources whose
traps are removed.
4 Managed resources are synchronized and communicate with SA. The amount of time
synchronization takes depends among others on the amount of trap traffic that SA receives, the
number of managed resources scheduled for synchronization. As a result of the synchronization,
SA receives up-to-date information from the managed resources.
5 Details about all traps that SA removes form the trap buffer are collected in the purgeEvents.log
file.

Trap Statistics
Trap statistics are displayed in the SA client web interface. You can open the SA client web interface
by clicking the overload buffer state bar in the lower right corner of the main SA window. Trap statistics
are displayed in the form of charts and tables. The charts provide you with a visual representation of
the trap buffer consumption and trap rate. The tables provide you with details about the trap buffer
consumption and trap rate, and with trap management options.

Trap Buffer Consumption Details

In the Trap Buffer Consumption Details table, you can find information about the current trap buffer
consumption. The table consists of the following elements and options:
Managed Resources
Resources managed by SA whose traps are currently queued in the trap buffer for processing.
Trap Buffer Consumption
Percentage of the current trap buffer capacity that is taken by traps queued in the trap buffer. The
same information is presented graphically in the Trap Buffer Consumption chart.
Number of Traps
Number of traps currently queued in the trap buffer.
Manage/Unmanage
Option that enables you to manage or unmanage SA resources. For example, you can unmanage
resources that are broken so that they do not send many traps to the trap buffer and take a lot of
the trap buffer capacity. After the resources are fixed, you can manage the fixed resources to
enable SA to receive traps from them.
Clean Trap Buffer & Sync
Option that enables you to clear the trap buffer of all traps SA received from a managed resource.
After the trap buffer is cleared, SA schedules synchronization with managed resources whose traps
you removed. As a result, SA receives up-to-date information from the managed resources.
Show on Chart
Option that displays traps belonging to a managed resource on the Trap Rate chart. With this
option, you can display the rate of traps sent to SA per second by one or more managed resources
of your choice. The traps rate value displayed on the chart is the same as the trap rate value
displayed in the Last Minute column.

154
 MN002730A01-AD
Chapter 4: SA Maintenance

4.3.1
Cleaning the Trap Buffer Manually
When the number of traps that SA receives exceeds the capacity of SA to process them, SA queues
the traps in the trap buffer for processing. From the SA client web interface, you can manually clear the
trap buffer, for example, of managed resources that send multiple traps to SA. By manually clearing
the trap buffer, you save the trap buffer space.

Procedure:
1 In the lower right corner of the main SA window, click the overload buffer state bar.
2 In the SA client web interface, go to the Trap Buffer Consumption Details or Trap Rate
Details table and clear traps:
NOTICE: The traps you remove from the trap buffer are not permanently deleted. The
traps are stored in the purgeEvents.log file.
• To clear all traps from the buffer, select the Clear Trap Buffer & Sync check box in the table
heading. Click Apply.
• To clear selected traps from the buffer, in the Clear Trap Buffer & Sync column, select
check boxes for the traps you want to clear. Click Apply.
The traps are deleted from the trap buffer. The deleted traps are collected in the
purgeEvents.log file.

3 Optional: Access the purgeEvents.log file from the SA client by selecting Logging → Server
Logs from the main menu.
SA schedules synchronization with managed resources whose traps you manually removed from the
trap buffer. As a result, SA receives up-to-date information from the managed resources.

4.3.2
Configuring Automatic Cleanup of the Trap Buffer
When the number of traps that SA receives exceeds the capacity of SA to process them, the excessive
traps are queued in the trap buffer for processing. When the overload buffer state changes to critical,
by default SA clears 20% of traps queued in the buffer. You can modify the percentage of traps that SA
automatically clears when the overload buffer state changes to the critical state.

Procedure:
1 In the lower right corner of the main SA window, click the overload buffer state bar.
2 In the SA client web interface, go to the Automatic Trap Buffer Cleanup area.
3 In the Automatically clear field, enter the percentage of traps buffer that SA clears
automatically when the trap buffer reaches the critical state. Click Submit.
When the trap buffer reaches the critical state, SA automatically removes from the trap buffer the
percent of traps you set. SA schedules synchronization with managed resources whose traps it
automatically removed from the trap buffer. As a result, SA receives up-to-date information from the
managed resources. Based on the configured cleanup percentage, the overload buffer state changes
to major, minor, or clear.

155
MN002730A01-AD
Chapter 4: SA Maintenance

4.3.3
Managing and Unmanaging Managed Resources From the Trap
Buffer
When the number of traps that SA receives exceeds the capacity of SA to process them, the excessive
traps are queued in the trap buffer for processing. From the SA client web interface, you can manage
and unmanage managed resources listed in the trap buffer that send many traps to SA.

Procedure:
1 In the lower right corner of the main SA window, click the overload buffer state bar.
2 In the SA client web interface, go to the Trap Buffer Consumption Details or Trap Rate
Details table and manage or unmanage managed resources:
• To unmanage all managed resources, clear the Manage/Unmanage check box in the table
heading. Click Apply.
• To unmanage selected managed resources, in the Clear Trap Buffer & Sync column, clear
check boxes for the managed resources you want to unmanage. Click Apply.
• To manage all managed resources, select the Manage/Unmanage check box in the table
heading. Click Apply.
• To manage selected managed resources, in the Clear Trap Buffer & Sync column, select
check boxes for the managed resources you want to manage. Click Apply.
SA does not receive traps form the unmanaged resources and still receives traps from the managed
resources.

4.4
Viewing Archived Events in SA
You can access the events archive files when a SA session is active. If no SA sessions are active, you
cannot access the events archive files. Only users with appropriate privileges can access event
archives.

Procedure:
1 Log on to the SA client with an account that has permissions to view event archives.
You can change accounts by selecting Administration → Security Administration from the
main menu.
2 From the main menu, select Logging → Event Archive.
3 In the online administration panel, select the Events Archive tab.

156
 MN002730A01-AD
Chapter 4: SA Maintenance

Figure 41: Events Archive – SA Client Web Interface

4 In the Events Archive tab, specify the match criteria by which you want to filter the data. Click
Apply Filters to View Archived Events.
A list of archived events is displayed.

5 Optional: View specific event columns by selecting or clearing appropriate Show Columns
check boxes.
6 Optional: View event details by double-clicking an event.
7 Click Generate CSV.
A .csv file with filtered events is sent to the browser. You can open or save the file. The file
contains all event properties.

157
MN002730A01-AD
Chapter 5: SA Troubleshooting

Chapter 5

SA Troubleshooting
Fault management and troubleshooting information related to SA helps you react quickly in case you
observe any issues.

5.1
Client Server Connection is Lost
SA displays a message when it detects that the connection to the server is lost. The application is
terminated when you click OK. To resolve this issue, restart the SA application.

5.2
Login Errors
A login error occurs as a result of using an incorrect user ID and password. To resolve this issue, the
end user can log on to the application only by specifying an active user ID and an appropriate
authentication password.

5.3
Configuring Server Logging
If you want to access Server Logs, see Retrieving System Advisor Archives and Logs on page 152.
Only Motorola Solution Support Center (SSC) personnel can update or modify settings for the server
log. There are multiple log levels within the server. They are:
• ALL
• DEBUG
• INFO
• WARN
• ERROR
• FATAL
• OFF
A log level can be assigned to a particular application module. For example, if the log level DEBUG is
assigned to DISCOVERY, all logs related to DISCOVERY with a level greater or equal DEBUG are
logged. The relationship between levels is as follows:
• ALL < DEBUG < INFO < WARN < ERROR < FATAL < OFF
where ALL means most of the information will be logged and OFF means none of the logging
information will be published.

Procedure:
1 From the Logging menu, select Server Logging Configuration.
The Server Log Configuration dialog box appears.

2 For a given application module, select an appropriate logging level from the drop-down list.

158
 MN002730A01-AD
Chapter 5: SA Troubleshooting

NOTICE:
The drop-down list appears when you click a cell in the Level column of the table.
Some loggers may have a special meaning and are not manageable through the user
interface. In such cases they remain grayed-out.
3 Click Submit.
The log level change made to one or more modules of the application is updated on the server.
The result of the operation appears at the bottom of the window.

5.4
Configuring Client Logging
Client log files can be created only by the Motorola Solution Support Center (SSC) personnel. Make
sure that it is possible to create them.

Procedure:
1 From the Logging menu, select Client Logging Configuration.
The Client Log Configuration dialog box appears.

2 For the Log State radio button, select Enabled.

NOTICE: The logging state is disabled by default.

The Log File Name and Log Location fields are enabled.

3 In the Log File Name field, type a valid file name.

NOTICE: The valid file name must not contain any of the following symbols:
• < (less than)
• > (greater than)
• : (colon)
• " (double quote)
• / (forward slash)
• \ (backslash)
• | (vertical bar or pipe)
• ? (question mark)
• * (asterisk)
The file name composed of dots only (one or more) is invalid.
4 Click Browse and locate the file in which you want to the save the logs.
In the Log Location text box, the path of the file is displayed.

5 Click Submit.
NOTICE: The status of the operation is displayed at the bottom of the window.

All client logs are logged in the selected text file.

159
MN002730A01-AD
Chapter 5: SA Troubleshooting

5.5
Command Operation Succeeds but Device Reports a Failure
SA displays a message indicating that the command operation succeeded, but an alarm indicating a
hardware failure or similar is reported against the device.
This situation may occur if the hardware or service against which the command was sent is physically
not present or has not been configured. In most cases, it may be necessary to update the configuration
of the device to remove the component that is not present. Once the configuration is updated, it may
also be necessary to invoke the synchronization operation on the impacted device.
NOTICE: The Network Management Servers do not report hardware components. The Generic
Application Server reports hardware components in the form of transient notifications.

5.6
Hardware Troubleshooting with SA
The following devices report hardware problems to System Advisor (SA):
• Repeaters
• System Advisors
• Switches
• Routers
• CMSS servers
To determine the status of these devices, check the severity in the Network Database view or System
View. To view details about the status of the device, check the alarms and events views for these
resources.
The following devices do not report the fault status to SA, but the information of the presence and
configuration of these devices can be found in SA:
• Trunk Controllers
• Voice Gateways
• Data Gateways
SA provides a list of connected clients identified by the client IP, port and client type (Voice or Data).
You can view the connected clients either in the System View or the Managed Resource Properties
window.

5.6.1
Hardware Troubleshooting in Network Database
Procedure:
1 In the Network Database window, select the relevant Generic Application Server and clickView
→ Events.
NOTICE: Hardware events are reported with a Warning severity.

2 To see which applications are affected by the hardware event reported by the Generic
Application Server, open the “Network Database”.

160
 MN002730A01-AD
Chapter 5: SA Troubleshooting

5.7
Sluggish Performance Monitoring
The SA client application may take a few seconds to become active after it is left running overnight.
The same can occur after a few hours of inactivity. This behavior is normal, but if it shows signs of
sluggishness, such as being slow to refresh or clicks taking unusually long to respond, it may indicate
that application is overloaded.
Determine how many sessions are active on the SA client. Make sure that no more than ten sessions
are active. If the number of open sessions exceeds ten, close enough sessions to drop to ten or below.

5.8
Performance Management Troubleshooting
If your graph displays any of the following messages, see the appropriate information in this section.

No data available
Reason: By default, automatic data collection starts 10 minutes after the SA server application is
started and the device is discovered. Also, data collection for a newly added statistic starts only after
10 minutes. The message No data available means that the data is not collected and there is a
delay in the collection process.
NOTICE: For Counter type OIDs, the initial data collected is not stored. When data is collected
for the second time, the difference between the two values is calculated and stored. Therefore,
depending on the polling interval set, the data is collected again. An additional delay in plotting
of data in a graph is possible in the case of Counter type OIDs.

Cannot plot (Data is String Type)

Reason: The collected data from the device is of string type, therefore the graph is not plotted.

Date Range Setting incorrect [From-Date is greater than To-Date]

Reason: The From date and To date that you set in Custom Date Range settings are incorrect. Check
for the date/time values set and click Plot Chart again.

5.9
Removing Alarms for Deleted Entities
When a managed resource is removed from the Radio System, SA can still report alarms against the
resource. Follow this process, if the removal of the resource or entity is permanent or if you want to
remove the alarms.

Procedure:
1 Ensure that the configuration of the device is modified to remove the deleted entity from that
device using the applicable software (CSS, UNC Device Server, and others). This changes the
device settings to reflect the current configuration.
2 In SA, go to the Network Database view and locate the managed resource (device).
3 Synchronize the device status with SA. SA performs a full synchronization on the device with the
deleted entity.
NOTICE: After the synchronization is complete, events from the deleted entity remain,
but are only visible in the Network Events view. Alarms for the deleted entity are also
removed.

161
MN002730A01-AD
Chapter 5: SA Troubleshooting

4 Back up the SA data.

Example:

Postrequisites:

5.10
SNMPv3 Communication for MotoMaster Tests
SA provides a method of testing the current configuration of SNMPv3 connection for a specified IP
address. It provides a status of the connection as well as the reason for failure, if any.

5.10.1
Testing the Outbound Communication from SA to any Device
Procedure:
1 From the main menu select Tools → Test any Device SNMPv3 Configuration.
The Test Any Device SNMPv3 Configuration window appears.

2 Enter the appropriate values and click Start.

NOTICE: The default SNMPv3 credentials are used. For information about how to
configure them, see Updating Global SNMPv3 Credentials for the MotoMaster User on
page 63.
The status of the request is updated in the status bar.

5.10.2
Testing the Outbound Communication from SA to a Discovered
Device
Procedure:
1 From the Network Database window, right-click the managed resource, and select Test
SNMPv3 Configuration.
The Test SNMPv3 Configuration window appears. The IP Address or Hostname field is
automatically populated with the device IP address or hostname.

2 Click Start.
The SNMPv3 credentials set for the device will be used. For information about how to configure
them, see Updating the Network Element SNMPv3 Credentials on page 64.
IMPORTANT: A mechanism for testing ICMP communication with a specific device, to
determine if it is alive (responds to ping) is also available. If the device does not respond
to ping, it will not respond to SNMP communication attempts either.
The status of the request is updated in the status bar.

162
 MN002730A01-AD
Chapter 5: SA Troubleshooting

5.10.3
SNMPv3 Inbound Communication Tests
To test inbound SNMPv3 communication for devices capable of reliable communication, invoke
synchronization.
If Synchronization succeeds and no CommFailure alarm for it is generated, then the inbound
communication is configured properly. Testing inbound communication for devices incapable of
Reliable Communication requires sending a trap from the device to SA.
NOTICE: For detailed procedure on how to send traps from a device consult the specific device
manual.

5.10.4
SNMP Communication Alarms and Events
The connection between devices and System Advisor (SA) is constantly monitored by the Supervision
procedure. If any change in the connection state occurs, it is reported in form of an alarm for
communication entity stating the nature of change as well as the reason for it. Additional events or
alarms may be generated depending on the situation.

CommFailure Alarm on SA
SA displays a communication failure alarm message for one or more managed resources with the
CommFailure severity (see Severity Definitions on page 32). This alarm indicates that SA has lost its
ability to communicate with the device. For IP managed devices, it can occur if the device ceases to
respond to ICMP queries. For devices communicating via SNMPv3, it can occur under any one of the
following conditions:
• Loss of connectivity
• Unstable or noisy link
• SNMPv3 configuration mismatch
• SNMP interface errors
• Device out-of-synchronization with SA (this situation may be related to many conditions)
• Failed Manager Registration on the device
• Device out-of-synchronization with SA (this situation may be related to many conditions)
NOTICE: For event details, see the “Alarms and Events” chapter in the System Advisor Online
Help.

CommFailure Alarm for Legacy Site Controller Managed Resources

SA displays a communication failure message with the CommFailure severity for Site Controller
managed resources if the following situation occurs:
• SA communicates over SNMPv1 with a Site Controller managed resources.
• The Site Controller is not enabled.
• Site Controller managed resources do not work correctly.
SA displays the communication failure message with the CommFailure severity instead of indicating
the real state of the managed resource because of SNMPv1 limitations.
The solution is to enable the Site Controller. Contact Solution Support Center (SSC) to enable the Site
Controller for you.

163
MN002730A01-AD
Chapter 5: SA Troubleshooting

Synchronization Failure: Synchronization Cycles

To test inbound SNMPv3 communication for devices capable of reliable communication, invoke
synchronization. See Synchronizing Managed Resources on page 117. You can also determine if a
device is capable of Reliable Communication. See Determining Reliable Communication Capability of
a Managed Resource on page 130.
If Synchronization succeeds and no CommFailure alarm for it is generated, then the inbound
communication is configured properly. If a CommFailure alarm is generated for Synchronization, refer
to “CommFailure Alarm on SA” paragraph. Testing inbound communication for devices incapable of
Reliable Communication requires sending a trap from the device to SA.
NOTICE: For detailed procedure on how to send traps from a device, consult the specific
device manual.

Synchronization Failure: Misconfiguration of SNMP Credentials

If Synchronization fails due to a credential problem, then the SNMP credentials for the device are most
likely not configured properly. Communication for devices managed by SA is performed by two SNMP
users:
MotoMaster
MotoMaster is used by devices that are incapable of reliable communication.
MotoInform
MotoInform is used by those capable of Reliable Communication.
Depending on the capability of reliable communication of the device, verify that the credentials for the
required SNMP user are set properly. To change them, see Updating Global SNMPv3 Credentials for
the MotoMaster User on page 63 and Updating Global SNMPv3 Inform Credentials on page 64.

Warnings Due to Credentials Mismatch

Whenever SA receives an inform which it is unable to process due to a mismatch in SNMP credentials,
a warning event is generated stating a credential failure.

164
 MN002730A01-AD
Basic Configuration

Appendix A

Basic Configuration
Basic configuration steps include:
• Creating an alarm/event or editing an existing one.
• Creating an E-mail Action or editing/choosing an existing one.
• Optionally testing configuration.
• Saving new configuration.

165
MN002730A01-AD
Appendix B: Configuration Input

Appendix B

Configuration Input
Basic Parameters
• Server address
• E-mail address of the recipient
• E-mail address of the sender
• Message subject
• Message content
To successfully send e-mail messages, valid server address and e-mail address of the recipient are
required.
NOTICE: The mail server must be configured to properly handle the e-mail received. Store the
e-mail in the mailbox if it is locally managed or relay the e-mail to the correct server if the
mailbox is on a different server.
If the user chooses to respond to the e-mail received from SA, the e-mail address of the sender is
used.
NOTICE: SA provides SMTP client functionality only. It is not capable of receiving e-mail. This
field is intended to identify the source of the e-mail notification (for example,
SA@z001SA01.zone1) or redirect the reply to a valid address (for example,
support@motorola.com).
The message subject and content contain details on an event or alarm that has occurred in the system.
The content of these fields can be populated with the content of a particular event or alarm and/or
custom text.

E-mail Account Configuration

In SA, a communication mode and Simple Mail Transfer Protocol (SMTP) port are used globally in all
e-mail actions. SMTP communicates in non-secure mode. The non-secure SMTP communication
mode is the default mode set in SA. The default port value set for non-secure SMTP communication is
25.
NOTICE: By default, the Radio Network Infrastructure (RNI) firewall allows communication on
the SMTP port: 25. If your mail server configuration uses a custom port, before using Digital
Notification, contact the Solution Support Center (SSC) to ensure that this custom port is
unblocked on the RNI firewall.

166
 MN002730A01-AD
Test E-mail Content

Appendix C

Test E-mail Content

The Send Test E-mail functionality available from e-mail action configuration windows is intended to
send test message using the destination and connection parameters specified in the action.
The following parameters are used to send the test e-mail:
• Server address
• To e-mail ID
• From e-mail ID
• Authentication settings: user and password
• Connection parameters: mode and port
The test e-mail content is:
• Subject: “Test E-mail”
• Content:
TIME: <Timestamp>
This is test E-mail
• Example of timestamp: Mon Mar 30 12:08:00 UTC 2009

167
MN002730A01-AD
Appendix D: Mail Server Compatibility

Appendix D

Mail Server Compatibility

Digital notifications in clear mode should be compatible with any mail server that supports Simple Mail
Transfer Protocol (SMTP) implemented according to the RFC 821 standard.
IMPORTANT: Motorola Solutions does not provide the mail server. Provide the mail server and
ensure that the server is configured according to the standards described in this document.

168
 MN002730A01-AD
Appendix E: Alarms and events

Appendix E

Alarms and events

E.1
Manager Generated Events
The Unified Event Manager reports critical information regarding the state of the radio system in the form of events and alarms. In addition to
displaying the information received from devices, the SA may also generate events and alarms when it detects a new condition or a change to an
existing condition that is already reported. In most cases, the SA will report this as an event or alarm against one or more resources that are
currently managed. The following section lists all such events reported.
Use the following table to determine the manager event and alarm details when an event or an alarm is generated.

Event Name Severity Event/Alarm Message Event/Alarm Description Event Catego- Manager
ry Entity
NMAAgentRed Info Redundancy attribute of the managed Redundancy attribute of the managed Attribute-Val- Agent Re-
resource has changed to: resource has changed to: ue-Change dundancy
Event
NMAObjRed Info Redundancy attribute of the entity has Redundancy attribute of the entity has Attribute-Val- -
changed (Possible RedObjState values changed (Possible RedObjState values ue-Change
are 1 = NOT PARTICIPATING, 2 = AC- are 1 = NOT PARTICIPATING, 2 = AC- Event
TIVE, 3 = STANDBY and 4 = TRANSI- TIVE, 3 = STANDBY and 4 = TRANSI-
TIONING) TIONING)
UnknownEventSource Warning Event received from an Unknown IPAd- Event received from an Unknown IPAd- Informational -
dress. dress. Event
UnknownManagedRe- Warning Cannot determine the impacted Man- Cannot determine the impacted Man- Informational -
source aged Resource for the event. aged Resource for the event. Event
UnknownManagedOb- Warning Failure event received with an unknown Failure event received with an unknown Informational -
ject entity. entity. Event
UnknownManagedRe- Warning A Correlation Event could not be gener- A Correlation Event could not be gener- Informational -
sourceForCorrelation ated properly.; UEM cannot determine ated properly. Event
the Managed Resource impacted by the
event.

169
MN002730A01-AD
Appendix E: Alarms and events

Event Name Severity Event/Alarm Message Event/Alarm Description Event Catego- Manager
ry Entity
IncorrectManagedRe- Warning A Correlation Event could not be gener- A Correlation Event could not be gener- Informational -
sourceForCorrelation ated properly.; Incorrect Managed Re- ated properly. Event
source impacted by the event.
SNMPCredential- Info SNMP Credentials have been updated SNMP Credentials have been updated Informational -
Change for for Event
SNMPv3Authentica- Warning Unable to process SNMPv3 INFORM Unable to process SNMPv3 INFORM Security Viola- -
tionFailure request from ; Reason: Authentication/ request from; Reason: Authentication/ tion
Decryption Error. Decryption Error.
DiscDeviceSuccess Info Discovered Device Managed Resource Discovered Device Managed Resource Object-Crea- Discovery
tion Event
DiscDeviceClear Clear Discovering Device Managed Resource Discovering Device Managed Resource Communica- Discovery
- tion Alarm
DiscGenericNode Info Discovered IP Managed Node; Reason: Discovered IP Managed Node; Reason: Object-Crea- Discovery
Device only responded to ICMP queries Device only responded to ICMP queries tion Event
during device discovery. during device discovery.
DiscGenericScada- Info Discovered IP Managed Node; Reason: Discovered IP Managed Node; Reason: Object-Crea- Discovery
Node Missing or invalid RTU configuration. Missing or invalid RTU configuration. tion Event
DiscFailNoManParam Warning Unable to fully discover device; Reason: Unable to fully discover device; Reason: Management Discovery
SNMP request(s) timed out or returned SNMP request(s) timed out or returned Event
the following error the following error
DiscInventoryGeneric- Info Discovered Inventory Generic Node; Discovered Inventory Generic Node; Object-Crea- Discovery
Node Reason: Device protocol is configured to Reason: Device protocol is configured tion Event
TYPE protocol, but only responded to to TYPE protocol, but only responded to
ICMP. ICMP.
DiscInventoryUnreach- Info Discovered Inventory Generic Node; Discovered Inventory Generic Node; Object-Crea- Discovery
ableNode Reason: Device did not respond to Reason: Device did not respond to tion Event
ICMP, but its configuration can be read. ICMP, but its configuration can be read.
DiscFailNoReqParam Critical Discovery failed for the Managed Re- Discovery failed for the Managed Re- Object-Crea- Discovery
source - ; Reason: SNMP request re- source; Reason: SNMP request re- tion Event
turned error during reading turned error during reading
DiscFailAuthEncFail Warning Unable to fully discover device; Reason: Unable to fully discover device; Reason: Security Viola- Discovery
SNMPv3 credential failure. Please verify SNMPv3 credential failure. Please veri- tion

170
 MN002730A01-AD
Appendix E: Alarms and events

Event Name Severity Event/Alarm Message Event/Alarm Description Event Catego- Manager
ry Entity
that the correct SNMPv3 credentials are fy that the correct SNMPv3 credentials
configured. are configured.
DiscFailUnknownSoid Warning Unable to fully discover device; Reason: Unable to fully discover device; Reason: Informational Discovery
The sysObjectID returned by the device The sysObjectID returned by the device Event
is not recognized is not recognized
DiscFailNoDataIvSup- Info Device discovered using default data in- Device discovered using default data in- Informational Discovery
port terface terface Event
DiscCrossDiscDevice Minor Re-discovering device; Reason: Device Re-discovering device; Reason: Device Informational Discovery
responded with different type. New type responded with different type. New type Event
DiscFailDowngrade- Minor Failed to re-discover device; Reason: Failed to re-discover device; Reason: Informational Discovery
Device SNMP query failure(s) during device dis- SNMP query failure(s) during device Event
covery (device responded to ping). discovery (device responded to ping).
NonSnmpDiscFail- Minor Failed to re-discover device; Reason: Failed to re-discover device; Reason: Informational Discovery
DowngradeDevice Device responded only to ping. Device responded only to ping. Event
DiscUpgradeDevice Info Re-discovering IP Managed Node; Rea- Re-discovering IP Managed Node; Rea- Informational Discovery
son: Previously discovered IP Managed son: Previously discovered IP Managed Event
Node is now responding with proper Node is now responding with proper
SNMP messaging. SNMP messaging.
DiscSysIpMismatch Warning Device network interface found but not Device network interface found but not Informational Discovery
managed; Reason: IP is not the man- managed; Reason: IP is not the man- Event
agement interface for the device. Sys- agement interface for the device. Sys-
tem IP tem IP
DiscFailDevUnMan- Warning Failed to re-discover device; Reason: Failed to re-discover device; Reason: Informational Discovery
aged Device is currently unmanaged. Device is currently unmanaged. Event
DiscNeedReDisc Critical Device requires rediscovery; Reason: Device requires rediscovery; Reason: Communica- Discovery
Device discovery did not successfully Device discovery did not successfully tion Alarm
complete due to a device communica- complete due to a device communica-
tion or credential problem. tion or credential problem.
NonSnmpDiscNee- Critical Device requires rediscovery; Reason: Device requires rediscovery; Reason: Communica- Discovery
dReDisc Device discovery did not successfully Device discovery did not successfully tion Alarm
complete due to a device communica- complete due to a device communica-
tion problem. tion problem.

171
MN002730A01-AD
Appendix E: Alarms and events

Event Name Severity Event/Alarm Message Event/Alarm Description Event Catego- Manager
ry Entity
DiscNeedReDiscNoR- Critical Device requires rediscovery; Reason: Device requires rediscovery; Reason: Communica- Discovery
esp Device no longer reporting on the follow- Device no longer reporting on the fol- tion Alarm
ing previously discovered Managed Re- lowing previously discovered Managed
sources Resources
DiscDeviceReDisc- Clear Rediscovering Managed Resource Rediscovering Managed Resource Communica- Discovery
Clear tion Alarm
DiscLMrSuccess Info Discovered Managed Resource Discovered Managed Resource Object-Crea- Discovery
tion Event
SysIPCheckSkipped Info Skipping SysIp check due to CEN dis- Skipping SysIp check due to CEN dis- Informational Discovery
covery for: covery for: Event
DiscLMrFailSnmpErr Minor Unable to discover Managed Resource; Unable to discover Managed Resource; Informational Discovery
Reason: SNMP request for managed re- Reason: SNMP request for managed Event
source returned the following error resource returned the following error
DiscLMrReDiscSuc- Info Rediscovered Managed Resource Rediscovered Managed Resource Object-Crea- Discovery
cess tion Event
DiscLMrReDiscAttrCh- Info Following Attribute Values have Following Attribute Values have Attribute-Val- Discovery
ange changed. changed. ue-Change
Event
DiscFailNoSiteId Warning Unable to discover ID value for; Reason: Unable to discover ID value for; Rea- Informational Discovery
SNMP request for the ID returned the son: SNMP request for the ID returned Event
following error the following error
DiscFailNoInstanceId Major Unable to discover instance identifier for Unable to discover instance identifier for Communica- Discovery
device; Reason: SNMP request for in- device; Reason: SNMP request for in- tion Alarm
stance ID returned the following error stance ID returned the following error
DiscUnknownPtpRFU- Info Device reports that RFU type is ; RFU Device reports that RFU type is; RFU Informational Discovery
Type type will be set to UNKNOWN. type will be set to UNKNOWN. Event
DeleteMrSuccess Info Deleted Managed Resource; Reason: Deleted Managed Resource; Reason: Object-Dele- User Dele-
User requested. User requested. tion Event tion
DeleteMrFail Major Failed Deletion of; Reason: Could not Failed Deletion of; Reason: Could not Management User Dele-
remove the alarms and/or Managed Re- remove the alarms and/or Managed Re- Event tion
source from the data store. source from the data store.

172
 MN002730A01-AD
Appendix E: Alarms and events

Event Name Severity Event/Alarm Message Event/Alarm Description Event Catego- Manager
ry Entity
DeleteMrWarning Major Skipped cascade deletion of Managed Skipped cascade deletion of Managed Management User Dele-
Resource; Reason: Device not Active Resource; Reason: Device not Active Event tion
agent. agent.
MmrDeRegFail Warning Failed to de-register from device ; - Rea- Failed to de-register from device; - Rea- Informational Manage-
son: De-registration request generated son: De-registration request generated Event ment
an error an error
MmrDeRegSuccess Info Manager successfully de-registered Manager successfully de-registered Informational Manage-
from the device from the device Event ment
ChangeMrDispName- Warning Failed display name change; Reason: Failed display name change; Reason: Management Manage-
Fail New display name improperly formatted New display name improperly formatted Event ment
DnsLookupFailure Major Dns could not resolve the following host Dns could not resolve the following host Management Manage-
name / IP address; Reason: Dns service name / IP address; Reason: Dns serv- Event ment
was unavailable or host name / IP ad- ice was unavailable or host name / IP
dress entry could not be found. address entry could not be found.
DiscFailProtocolMis- Major Unable to rediscover device; Reason: Unable to rediscover device; Reason: Management Discovery
match Device responding with different SNMP Device responding with different SNMP Event
protocol version. protocol version.
CommLossTimeout Comm- Fault Manager lost communication to Fault Manager lost communication to Communica- Communi-
Failure the device.; Reason: Timeout on device the device.; Reason: Timeout on device tion Alarm cation
response. response.
CommV3CredFailure Comm- Fault Manager lost communication to Fault Manager lost communication to Communica- Communi-
Failure the device.; Reason: SNMPv3 credential the device.; Reason: SNMPv3 creden- tion Alarm cation
failure. tial failure.
CommV3ProtocolError Comm- Fault Manager lost communication to Fault Manager lost communication to Communica- Communi-
Failure the device.; Reason: SNMP V3 Protocol the device.; Reason: SNMP V3 Protocol tion Alarm cation
Error. Error.
CommUp Clear The Fault Manager has detected that The Fault Manager has detected that Communica- Communi-
the communication to this device is up.; the communication to this device is up.; tion Alarm cation
Reason: The device is responding to re- Reason: The device is responding to re-
quests. quests.
EntityStatusClear Clear Entity has been removed: Entity has been removed: - -
AlarmStatusClear Clear Alarm has been cleared. Previous mes- Alarm has been cleared. Previous mes- - -
sage: sage:

173
MN002730A01-AD
Appendix E: Alarms and events

Event Name Severity Event/Alarm Message Event/Alarm Description Event Catego- Manager
ry Entity
UserRequestedAlarm- Clear Alarm has been cleared by {0}. Previous Alarm has been cleared by {0}. Previ- - -
StatusClear message: {1} ous message: {1}
EntityDeleted Info Entity has been removed: Entity has been removed: Object-Dele- -
tion Event
OutOfSyncStatus Comm- Fault information for this device may be Fault information for this device may be Communica- Synchroni-
Failure out of date.; Reason: there may be out of date.; Reason: there may be tion Alarm zation
missing event information, a loss of missing event information, a loss of
communication, or a failure to synchron- communication, or a failure to synchron-
ize with the device. ize with the device.
SynchronizedStatus Clear Fault manager has synchronized fault Fault manager has synchronized fault Communica- Synchroni-
information with this device. information with this device. tion Alarm zation
SyncCapable Clear Fault manager is capable of synchroniz- Fault manager is capable of synchroniz- Communica- Synchroni-
ing fault information with this device. ing fault information with this device. tion Alarm zation
SyncIncapable Comm- Fault information for this device may be Fault information for this device may be Communica- Synchroni-
Failure out of date.; Reason: there may be out of date.; Reason: there may be tion Alarm zation
missing event information, a loss of missing event information, a loss of
communication, or a failure to synchron- communication, or a failure to synchron-
ize with the device. ize with the device.
NMASyncComplete Clear Fault Manager received Synchronization Fault Manager received Synchroniza- Communica- Synchroni-
Complete notification from the device. tion Complete notification from the de- tion Alarm zation
vice.
DiscUnManRqst Info Managed Resource Unmanaged; Rea- Managed Resource Unmanaged; Rea- Management Manage-
son: User requested son: User requested Event ment
DiscUnManRqstFail Warning Failed to Unmanage Managed Re- Failed to Unmanage Managed Re- Management Manage-
source; Reason: Proxy-ing Device for source; Reason: Proxy-ing Device for Event ment
Managed Resource is not ACTIVE. Managed Resource is not ACTIVE.
DiscManRqst Info Managed Resource is now Managed; Managed Resource is now Managed; Management Manage-
Reason: User requested Reason: User requested Event ment
DiscUnManClearAll Clear Failure cleared by user un-management Failure cleared by user un-management - Manage-
request. request. ment
PortDeletedClear Clear Port status is clear. Reason: Port is no Port status is clear. Reason: Port is no - Manage-
longer reported. longer reported. ment

174
 MN002730A01-AD
Appendix E: Alarms and events

Event Name Severity Event/Alarm Message Event/Alarm Description Event Catego- Manager
ry Entity
FrmwrkInitSuccess Info Fault Management services started suc- Fault Management services started suc- Informational UEM Ap-
cessfully. cessfully. Event plication
ArchivePurgeWriteEr- Major The fault manager has failed to write The fault manager has failed to write Informational UEM Ap-
ror events to the event archive file.; Rea- events to the event archive file.; Rea- Event plication
son: I/O Error son: I/O Error
ArchivePurgeDeleteEr- Major The fault manager has failed to purge The fault manager has failed to purge Informational UEM Ap-
ror events.; Reason: I/O Error events.; Reason: I/O Error Event plication
ArchivePurgeReadEr- Major The fault manager has failed to read The fault manager has failed to read Informational UEM Ap-
ror events to be archived.; Reason: I/O Er- events to be archived.; Reason: I/O Er- Event plication
ror ror
DisplayNameChange Info Following Attribute Values have Following Attribute Values have Attribute-Val- Manage-
changed. changed. ue-Change ment
Event
SubsystemName- Info Following Attribute Values have Following Attribute Values have Management Manage-
Change changed. changed. Event ment
PMArchSizeSoftThre- Warning The Fault Manager statistics archive has The Fault Manager statistics archive Informational Perform-
sholdCrossed grown larger than 750 MB. If it reaches has grown larger than 750 MB. If it Event ance
1 GB, statistical data will be trimmed. reaches 1 GB, statistical data will be
trimmed.
PMArchSizeHardThre- Warning The Fault Manager statistics archive has The Fault Manager statistics archive Informational Perform-
sholdCrossed grown larger than 1 GB. The Fault Man- has grown larger than 1 GB. The Fault Event ance
ager will now trim the archive to below Manager will now trim the archive to be-
750 MB. low 750 MB.
DiscFailUnknownDIV Warning Unable to fully discover device; Reason: Unable to fully discover device; Reason: Informational Discovery
The interface version returned by the The interface version returned by the Event
device is not a supported value device is not a supported value
DiscReDiscoverDiffer- Info Device re-discovered with a different in- Device re-discovered with a different in- Management Discovery
entDIV terface version. Old value was: terface version. Old value was: Event
DiscDeleteDiscovery- Info Device will be deleted and re-discovered Device will be deleted and re-discov- Management Discovery
DifferentDIV with a new interface version. Old value ered with a new interface version. Old Event
was: value was:

175
MN002730A01-AD
Appendix E: Alarms and events

Event Name Severity Event/Alarm Message Event/Alarm Description Event Catego- Manager
ry Entity
DiscDetectLegacyDe- Info Device discovered using default inter- Device discovered using default inter- Management Discovery
vice face version.; Device does not support face version.; Device does not support Event
interface version query. interface version query.
DiscDetectCompatible- Warning Device discovered by using a default in- Device discovered by using a default in- Management Discovery
Device terface version.; Reason: device discov- terface version.; Reason: device discov- Event
ered with the last supported version of ered with the last supported version of
the device interface: the device interface:
DiscDataIvGetFailure Warning Unable to fully discover device; Reason: Unable to fully discover device; Reason: Informational Discovery
Retrieval of device interface version Retrieval of device interface version Event
failed. failed.
UnknownEvent Warning Unknown Event Unknown Event Informational -
Event
DiscNoRedAgntGrp- Warning Fallback redundant group name (based Fallback redundant group name (based Management Discovery
NameParam on first two octets of an IP address) will on first two octets of an IP address) will Event
be calculated for the device; Reason: be calculated for the device; Reason:
Retrieval of mandatory redundant group Retrieval of mandatory redundant group
name parameter failed. name parameter failed.
DiscNoPTPRe- Critical Discovery failed for the device; Reason: Discovery failed for the device; Reason: Object-Crea- Discovery
dAgntGrpNameParam Retrieval of mandatory REDUNDANT Retrieval of mandatory REDUNDANT tion Event
GROUP NAME parameter failed. GROUP NAME parameter failed.
DiscInvalidAttrValue Major Discovery failed due to invalid value of Discovery failed due to invalid value of Informational Discovery
configuration parameter ; Possible val- configuration parameter; Possible val- Event
ues are: ues are:
ManualSynchroniza- Comm- Fault information for this device may be Fault information for this device may be Communica- Synchroni-
tionRequired Failure out of date. Manually synchronize the out of date. Manually synchronize the tion Alarm zation
device; Reason: Internal error. device; Reason: Internal error.
ManagerRegistration- Clear Manager registration on the device was Manager registration on the device was Communica- Manage-
Successful successful. successful. tion Alarm ment
ManagerRegistration- Critical Manager registration on the device Manager registration on the device Communica- Manage-
Failed failed. The device may not be able to failed. The device may not be able to tion Alarm ment
send notifications to the manager. send notifications to the manager.
ManagerRegistration- Warning Manager registration not found on the Manager registration not found on the Communica- Manage-
FailedForIlom device. Perform manual manager regis- device. Perform manual manager regis- tion Alarm ment
tration on the device. tration on the device.

176
 MN002730A01-AD
Appendix E: Alarms and events

Event Name Severity Event/Alarm Message Event/Alarm Description Event Catego- Manager
ry Entity
DeleteAlarm Warning Alarm deleted. severity of deleted alarm Alarm deleted. Severity of deleted alarm Alarm-Deletion Alarm User
was %s. Creation time: %s, last modifi- was %s. Creation time: %s, last modifi- Event Deletion
cation time: %s.; Deletion requested by cation time: %s.; Deletion requested by
%s user. %s user.
VmwareCommProto- Comm- Fault Manager lost communication to Fault Manager lost communication to Communica- Communi-
colError Failure the device.; Reason: Web Service Pro- the device.; Reason: Web Service Pro- tion Alarm cation
tocol Error. tocol Error.
VmwareCommCred- Comm- Fault Manager lost communication to Fault Manager lost communication to Communica- Communi-
Failure Failure the device.; Reason: WebService Cre- the device.; Reason: WebService Cre- tion Alarm cation
dential failure. dential failure.
WebServiceCreden- Info Web Service Credentials have been up- Web Service Credentials have been up- Informational -
tialChange dated dated Event
EventsArchSizeThre- Clear The disk space used by the events ar- The disk space used by the events ar- Informational UEM Ap-
sholdCrossed chive exceeds %s. When the events ar- chive exceeds %s. When the events ar- Event plication
chive reaches its disk space limit, UEM chive reaches its disk space limit, SA
automatically deletes the oldest events. automatically deletes the oldest events.
OverloadModeClear Clear The UEM is displaying fault traffic in real The SA is displaying fault traffic in real Quality-of- Processing
time. ; Exit overload mode. time.; Exit overload mode. Service Alarm
OverloadModeMinor Minor The UEM is not displaying fault traffic in The SA is not displaying fault traffic in Quality-of- Processing
real time. ; Enter overload mode. real time.; Enter overload mode. Service Alarm
OverloadModeMajor Major The UEM buffer is reaching a critical The SA buffer is reaching a critical lev- Quality-of- Processing
level. ; {0}% buffer consumption. el.; {0}% buffer consumption. Service Alarm
OverloadModeCritical Critical The UEM buffer has reached a critical The SA buffer has reached a critical lev- Quality-of- Processing
level. ; {0}% buffer consumption. el.; {0}% buffer consumption. Service Alarm
OverloadPurgedBuffer Warning Fault Management dropped buffer with Fault Management dropped buffer with Informational Processing
notifications from device(s). ; Reason: notifications from device(s).; Reason: Event
Not enough resources to process in- Not enough resources to process in-
coming notifications. coming notifications.
StateApiRejectedE- Warning Fault Management dropped state for {0} Fault Management dropped state for {0} Informational Processing
vent managed resource. ; Reason: Not managed resource. Reason: Not Event
enough resources to process state noti- enough resources to process state noti-
fications. fications.

177
MN002730A01-AD
Appendix E: Alarms and events

Event Name Severity Event/Alarm Message Event/Alarm Description Event Catego- Manager
ry Entity
OverloadSchedule- Warning After the trap buffer reached the critical After the trap buffer reached the critical Informational Processing
Synchronization state, it was cleared of traps received state, it was cleared of traps received Event
from the {0} managed resource. The from the {0} managed resource. The
trap buffer state change took place on trap buffer state change took place on
{1}.; Synchronization of the {0} managed {1}.; Synchronization of the {0} man-
resource is already scheduled by UEM. aged resource is already scheduled by
SA.
OverloadSynchroniza- Warning After the trap buffer reached the critical After the trap buffer reached the critical Informational Processing
tionIsAlreadySched- state, it was cleared of traps received state, it was cleared of traps received Event
uled from the {0} managed resource. The from the {0} managed resource. The
trap buffer state change took place on trap buffer state change took place on
{1}.; Synchronization of the {0} managed {1}.; Synchronization of the {0} man-
resource is already scheduled. This syn- aged resource is already scheduled.
chronization is scheduled by UEM or by This synchronization is scheduled by
application users. SA or by application users.
NotificationProcessing- Major The fault manager has failed to process The fault manager has failed to process Informational Processing
TimeoutError a notification from the {0} device re- a notification from the {0} device re- Event
ceived on {1}.; Reason: Processing ceived on {1}.; Reason: Processing
Timeout Timeout
NotificationProcessin- Major The fault manager has failed to process The fault manager has failed to process Informational Processing
gInterruptedError a notification from the {0} device re- a notification from the {0} device re- Event
ceived on {1}.; Reason: Processing In- ceived on {1}.; Reason: Processing In-
terrupted terrupted
LmrDiscoveryFailed Critical Unable to fully discover device; Reason: Unable to fully discover device; Reason: Informational Discovery
At least one Logical Managed Resource At least one Logical Managed Resource Event
cannot be discovered. cannot be discovered.
NoNbiLicense Info Feature NBI is disabled.; License for this Feature NBI is disabled.; License for Informational UEM Ap-
feature is inactive. Feature inactive for this feature is inactive. Feature inactive Event plication
for
NoCorrelationEngine- Info Feature Correlation Engine is disabled.; Feature Correlation Engine is disabled.; Informational UEM Ap-
License License for this feature is inactive. License for this feature is inactive. Event plication
NoMailLicense Info Feature Email is disabled.; License for Feature Email is disabled.; License for Informational UEM Ap-
this feature is inactive. this feature is inactive. Event plication
ToolkitTrapRuleNot- Warning Trap rule for trap {0} could not be Trap rule for trap {0} could not be Informational -
Found found. ; Reason: the trap was received found.; Reason: the trap was received Event

178
 MN002730A01-AD
Appendix E: Alarms and events

Event Name Severity Event/Alarm Message Event/Alarm Description Event Catego- Manager
ry Entity
with varbind values that do not match with varbind values that do not match
the rules in the DDP. the rules in the DDP.
ToolkitTrapNotifica- Major Unable to process trap {0} for the Toolkit Unable to process trap {0} for the Tool- Informational -
tionProcessingError device. kit device. Event
ToolkitInvalidTrapDa- Warning Received trap {0} contains data not Received trap {0} contains data not Informational -
taFormat compliant with the agent definition. ; compliant with the agent definition.; Event
Reason: One or more varbinds do not Reason: One or more varbinds do not
match the type expected in DDP. match the type expected in DDP.
ToolkitPollingRuleNot- Warning Polling rule could not be found. ; Rea- Polling rule could not be found.; Rea- Informational -
Found son: Synchronization response was re- son: Synchronization response was re- Event
ceived with varbind values that do not ceived with varbind values that do not
match the rules in the DDP. match the rules in the DDP.
ToolkitPollingNotifica- Major Unable to process Toolkit synchroniza- Unable to process Toolkit synchroniza- Informational -
tionProcessingError tion response. tion response. Event
ToolkitInvalidPolling- Warning Received synchronization response Received synchronization response Informational -
DataFormat contains data not compliant with the contains data not compliant with the Event
agent definition. ; Reason: One or more agent definition.; Reason: One or more
varbinds do not match the type expect- varbinds do not match the type expect-
ed in DDP. ed in DDP.
DiscWarnToolkitGe- Warning Unable to get additional property: {0} Unable to get additional property: {0} Informational -
tAdditionalPropertyEr- Event
ror
ToolkitInvalidAdditio- Warning Additional Property {0} has data not ac- Additional Property {0} has data not ac- Informational -
nalPropertyDataFor- cording to agent definition. ; Reason: cording to agent definition.; Reason: Event
mat One or more varbinds have different One or more varbinds have different
type than expected in DDP package. type than expected in DDP package.
ToolkitLicenseViolation Major License Violation. Reason: System con- License Violation. Reason: System con- Equipment UEM Ap-
figuration is greater than licensed limit. figuration is greater than licensed limit. Alarm plication
ToolkitLicenseCompli- Clear License Compliant. Reason: System License Compliant. Reason: System Equipment UEM Ap-
ant configuration is within licensed limits. configuration is within licensed limits. Alarm plication
GmrReclassifyToTsub Warning Group managed resource was assigned Group managed resource was assigned Informational UEM Ap-
to Trunking Subsystem.; Newly discov- to Trunking Subsystem. Event plication
ered device has Trunking Subsystem
configuration.

179
MN002730A01-AD
Appendix E: Alarms and events

Event Name Severity Event/Alarm Message Event/Alarm Description Event Catego- Manager
ry Entity
GmrChangeTsubRe- Warning Group managed resource type was Group managed resource type was Informational UEM Ap-
mote changed from {0} to {1}.; Newly discov- changed from {0} to {1}. Event plication
ered device has different Trunking Sub-
system configuration.
PeriodicalToolkitSigna- Major Fault Manager detected that the signa- Fault Manager detected that the signa- Informational UEM Ap-
tureViolation ture in the DDP is corrupted. The follow- ture in the DDP is corrupted. The follow- Event plication
ing devices will be downgraded: {0} ing devices will be downgraded: {0}
ToolkitSignatureViola- Minor The signed DDP: {0} is corrupted. The The signed DDP: {0} is corrupted. The Object-Crea- Discovery
tion device will be discovered as Generi- device will be discovered as Generi- tion Event
cNode. Contact Motorola Solutions to cNode. Contact Motorola Solutions to
repair the DDP. repair the DDP.

E.2
MIB-2 Events
SA can receive MIB-2 generic SNMP traps from any SNMP-managed device and will display them as Events in the Network Events view.

Event Name Event ID Severity Event/Alarm Message Event Category

Cold Start Trap .1.3.6.1.6.3.1.1.5.1(for SNMPv3 devices)or <enterpri- Major Cold Start.<contents of the SNMP event, if Informational Event
seOID>.1(for SNMPv1 devices) any>
Warm Start .1.3.6.1.6.3.1.1.5.2(for SNMPv3 devices)or <enterpri- Warning Warm Start.<contents of the SNMP event, Informational Event
Trap seOID>.2(for SNMPv1 devices) if any>
Link down trap .1.3.6.1.6.3.1.1.5.3(for SNMPv3 devices)or <enterpri- Major Link Down.ifIndex=<interface index num- Informational Event
seOID>.3(for SNMPv1 devices) ber>,<contents of the SNMP event, if any>
Link up trap .1.3.6.1.6.3.1.1.5.4(for SNMPv3 devices)or <enterpri- Clear Link Up.ifIndex=<interface index num- Informational Event
seOID>.4(for SNMPv1 devices) ber>,<contents of the SNMP event, if any>
Auth Failure .1.3.6.1.6.3.1.1.5.5(for SNMPv3 devices)or <enterpri- Warning Authentication Failure.<contents of the Informational Event
Trap seOID>.5(for SNMPv1 devices) SNMP event, if any>
EgpNeighbor- .1.3.6.1.6.3.1.1.5.6(for SNMPv3 devices)or <enterpri- Major EGP Neighbor Loss.<contents of the Informational Event
Loss seOID>.6(for SNMPv1 devices) SNMP event, if any>

180
 MN002730A01-AD
Appendix E: Alarms and events

E.3
General RFC Events
SA can receive events defined below in general RFC mibs. These events can be sent by different types of devices.

Event Name Event ID Se- Event/Alarm Message Event

verity Category
lldpRemTable- .1.0.8802.1.1.2.0.0.1 Info lldpRemTablesChange. Number of inserts to LLDP Tables = {1 : lldpStats- Informa-
sChange RemTablesInserts : .1.0.8802.1.1.2.1.2.2}, Number of deletions from LLDP tional
Tables = {2 : lldpStatsRemTablesDeletes : .1.0.8802.1.1.2.1.2.3}, Number of Event
insert errors on LLDP Tables = {3 : lldpStatsRemTables-
Drops : .1.0.8802.1.1.2.1.2.4}, Number of insert timeouts on LLDP Tables =
{4 : lldpStatsRemTablesAgeouts : .1.0.8802.1.1.2.1.2.5}
lldpXMedTopolo- .1.0.8802.1.1.2.1.5.4795.0.1 Info lldpXMedTopologyChangeDetected. Type of Encoding = {1 : lldpRemChassi- Informa-
gyChangeDetect- sIdSubtype : .1.0.8802.1.1.2.1.4.1.1.4.*}, Remote Chassis = {2 : lldpRem- tional
ed ChassisId : .1.0.8802.1.1.2.1.4.1.1.5.*}, Device Class = {3 : lldpXMedRemDe- Event
viceClass : .1.0.8802.1.1.2.1.5.4795.1.3.1.1.3.*}
entStateOperEna- .1.3.6.1.2.1.131.0.1 Info entStateOperEnabled. Administrative State = {1 : entStateAd- Informa-
bled min : .1.3.6.1.2.1.131.1.1.1.2.*}, Alarm Status = {2 : entStateA- tional
larm : .1.3.6.1.2.1.131.1.1.1.5.*} Event
entStateOperDisa- .1.3.6.1.2.1.131.0.2 Info entStateOperDisabled. Administrative State = {1 : entStateAd- Informa-
bled min : .1.3.6.1.2.1.131.1.1.1.2.*}, Alarm Status = {2 : entStateA- tional
larm : .1.3.6.1.2.1.131.1.1.1.5.*} Event
ospfv3VirtIfState- .1.3.6.1.2.1.191.0.1 Info ospfv3VirtIfStateChange. Originator of the Notification = {1 : ospfv3Router- Informa-
Change Id : .1.3.6.1.2.1.191.1.1.1}, New state = {2 : ospfv3VirtIf- tional
State : .1.3.6.1.2.1.191.1.8.1.9.*} Event
ospfv3NbrState- .1.3.6.1.2.1.191.0.2 Info ospfv3NbrStateChange. Originator of the Notification = {1 : ospfv3Router- Informa-
Change Id : .1.3.6.1.2.1.191.1.1.1}, New state = {2 : tional
ospfv3NbrState : .1.3.6.1.2.1.191.1.9.1.8.*} Event
ospfv3VirtNbrSta- .1.3.6.1.2.1.191.0.3 Info ospfv3VirtNbrStateChange. Originator of the Notification = {1 : ospfv3Router- Informa-
teChange Id : .1.3.6.1.2.1.191.1.1.1}, New state = {2 : ospfv3VirtNbr- tional
State : .1.3.6.1.2.1.191.1.11.1.8.*} Event
ospfv3IfConfigEr- .1.3.6.1.2.1.191.0.4 Info ospfv3IfConfigError. Originator of the Notification = {1 : ospfv3Router- Informa-
ror Id : .1.3.6.1.2.1.191.1.1.1}, State of the interface = {2 : ospfv3If- tional
State : .1.3.6.1.2.1.191.1.7.1.12.*}, Source IPv6 address = {3 : ospfv3Pack- Event
etSrc : .1.3.6.1.2.1.191.1.14.3}, Type of error = {4 : ospfv3ConfigError-

181
MN002730A01-AD
Appendix E: Alarms and events

Event Name Event ID Se- Event/Alarm Message Event

verity Category
Type : .1.3.6.1.2.1.191.1.14.1}, Type of packet = {5 : ospfv3Packet-
Type : .1.3.6.1.2.1.191.1.14.2}
ospfv3VirtIfConfi- .1.3.6.1.2.1.191.0.5 Info ospfv3VirtIfConfigError. Originator of the Notification = {1 : ospfv3Router- Informa-
gError Id : .1.3.6.1.2.1.191.1.1.1}, State of the interface = {2 : ospfv3VirtIf- tional
State : .1.3.6.1.2.1.191.1.8.1.9.*}, Type of error = {3 : ospfv3ConfigError- Event
Type : .1.3.6.1.2.1.191.1.14.1}, Type of packet = {4 : ospfv3Packet-
Type : .1.3.6.1.2.1.191.1.14.2}
ospfv3IfRxBad- .1.3.6.1.2.1.191.0.6 Info ospfv3IfRxBadPacket. Originator of the Notification = {1 : ospfv3Router- Informa-
Packet Id : .1.3.6.1.2.1.191.1.1.1}, State of the interface = {2 : ospfv3If- tional
State : .1.3.6.1.2.1.191.1.7.1.12.*}, Source IPv6 address = {3 : ospfv3Pack- Event
etSrc : .1.3.6.1.2.1.191.1.14.3}, Type of packet = {4 : ospfv3Packet-
Type : .1.3.6.1.2.1.191.1.14.2}
ospfv3VirtIfRxBad- .1.3.6.1.2.1.191.0.7 Info ospfv3VirtIfRxBadPacket. Originator of the Notification = {1 : ospfv3Router- Informa-
Packet Id : .1.3.6.1.2.1.191.1.1.1}, State of the interface = {2 : ospfv3VirtIf- tional
State : .1.3.6.1.2.1.191.1.8.1.9.*}, Type of packet = {3 : ospfv3Packet- Event
Type : .1.3.6.1.2.1.191.1.14.2}
ospfv3LsdbOver- .1.3.6.1.2.1.191.0.8 Info ospfv3LsdbOverflow. Originator of the Notification = {1 : ospfv3Router- Informa-
flow Id : .1.3.6.1.2.1.191.1.1.1}, Limit on External LSAs = {2 : ospfv3ExtAreaLsd- tional
bLimit : .1.3.6.1.2.1.191.1.1.11} Event
ospfv3LsdbAp- .1.3.6.1.2.1.191.0.9 Info ospfv3LsdbApproachingOverflow. Originator of the Notification = {1 : Informa-
proachingOverflow ospfv3RouterId : .1.3.6.1.2.1.191.1.1.1}, Limit on External LSAs = {2 : tional
ospfv3ExtAreaLsdbLimit : .1.3.6.1.2.1.191.1.1.11} Event
ospfv3IfState- .1.3.6.1.2.1.191.0.10 Info ospfv3IfStateChange. Originator of the Notification = {1 : ospfv3Router- Informa-
Change Id : .1.3.6.1.2.1.191.1.1.1}, New State = {2 : ospfv3If- tional
State : .1.3.6.1.2.1.191.1.7.1.12.*} Event
ospfv3NssaTrans- .1.3.6.1.2.1.191.0.11 Info ospfv3NssaTranslatorStatusChange. Originator of the Notification = {1 : Informa-
latorStatusChange ospfv3RouterId : .1.3.6.1.2.1.191.1.1.1}, NSSA Border Router Translation tional
State = {2 : ospfv3AreaNssaTranslatorState : .1.3.6.1.2.1.191.1.2.1.12.*} Event
ospfv3RestartSta- .1.3.6.1.2.1.191.0.12 Info ospfv3RestartStatusChange. Originator of the Notification = {1 : ospfv3Rou- Informa-
tusChange terId : .1.3.6.1.2.1.191.1.1.1}, New Status = {2 : ospfv3RestartSta- tional
tus : .1.3.6.1.2.1.191.1.1.18}, Restart Interval = {3 : ospfv3RestartInterv- Event
al : .1.3.6.1.2.1.191.1.1.16}, Status = {4 : ospfv3RestartExitRea-
son : .1.3.6.1.2.1.191.1.1.20}

182
 MN002730A01-AD
Appendix E: Alarms and events

Event Name Event ID Se- Event/Alarm Message Event

verity Category
ospfv3NbrRestar- .1.3.6.1.2.1.191.0.13 Info ospfv3NbrRestartHelperStatusChange. Originator of the Notification = {1 : Informa-
tHelperStatu- ospfv3RouterId : .1.3.6.1.2.1.191.1.1.1}, New Status = {2 : ospfv3NbrRestar- tional
sChange tHelperStatus : .1.3.6.1.2.1.191.1.9.1.13.*}, Remaining Time in Restart Inter- Event
val = {3 : ospfv3NbrRestartHelperAge : .1.3.6.1.2.1.191.1.9.1.14.*}, Status =
{4 : ospfv3NbrRestartHelperExitReason : .1.3.6.1.2.1.191.1.9.1.15.*}
ospfv3VirtNbrRes- .1.3.6.1.2.1.191.0.14 Info ospfv3VirtNbrRestartHelperStatusChange. Originator of the Notification = {1 : Informa-
tartHelperStatu- ospfv3RouterId : .1.3.6.1.2.1.191.1.1.1}, New Status = {2 : ospfv3VirtNbrRes- tional
sChange tartHelperStatus : .1.3.6.1.2.1.191.1.11.1.13.*}, Remaining Time in Restart In- Event
terval = {3 : ospfv3VirtNbrRestartHelperAge : .1.3.6.1.2.1.191.1.11.1.14.*},
Status = {4 : ospfv3VirtNbrRestartHelperExitRea-
son : .1.3.6.1.2.1.191.1.11.1.15.*}
ospfVirtIfState- .1.3.6.1.2.1.14.16.2.1 Info ospfVirtIfStateChange. The originator of the trap = {1 : ospfRouter- Informa-
Change Id : .1.3.6.1.2.1.14.1.1}, The Transit Area that the Virtual Link traverses = {2 : tional
ospfVirtIfAreaId : .1.3.6.1.2.1.14.9.1.1}, The Router ID of the virtual neighbor Event
= {3 : ospfVirtIfNeighbor : .1.3.6.1.2.1.14.9.1.2}, The new state = {4 : ospfVir-
tIfState : .1.3.6.1.2.1.14.9.1.7}
ospfNbrState- .1.3.6.1.2.1.14.16.2.2 Info ospfNbrStateChange. The originator of the trap = {1 : ospfRouter- Informa-
Change Id : .1.3.6.1.2.1.14.1.1}, The IP address this neighbor is using in its IP source tional
address = {2 : ospfNbrIpAddr : .1.3.6.1.2.1.14.10.1.1}, The value of ifIndex in Event
the Internet Standard MIB = {3 : ospfNbrAddressLessIn-
dex : .1.3.6.1.2.1.14.10.1.2}, The neighboring router ID in the Autonomous
System = {4 : ospfNbrRtrId : .1.3.6.1.2.1.14.10.1.3}, The new state = {5 :
ospfNbrState : .1.3.6.1.2.1.14.10.1.6}
ospfVirtNbrState- .1.3.6.1.2.1.14.16.2.3 Info ospfVirtNbrStateChange. The originator of the trap = {1 : ospfRouter- Informa-
Change Id : .1.3.6.1.2.1.14.1.1}, The Transit Area Identifier = {2 : ospfVirtNbrAr- tional
ea : .1.3.6.1.2.1.14.11.1.1}, The neighboring router ID in the Autonomous Event
System = {3 : ospfVirtNbrRtrId : .1.3.6.1.2.1.14.11.1.2}, The new state;The
state of the virtual neighbor relationship = {4 : ospfVirtNbr-
State : .1.3.6.1.2.1.14.11.1.5}
ospfIfConfigError .1.3.6.1.2.1.14.16.2.4 Info ospfIfConfigError. The originator of the trap = {1 : ospfRouter- Informa-
Id : .1.3.6.1.2.1.14.1.1}, The IP address of this OSPF interface = {2 : ospfIfI- tional
pAddress : .1.3.6.1.2.1.14.7.1.1}, The value of ifIndex for interfaces having no Event
IP address = {3 : ospfAddressLessIf : .1.3.6.1.2.1.14.7.1.2}, The source IP
address = {4 : ospfPacketSrc : .1.3.6.1.2.1.14.16.1.4}, Config error = {5 : ospf-
ConfigErrorType : .1.3.6.1.2.1.14.16.1.2}, OSPF Packet type = {6 : ospfPack-
etType : .1.3.6.1.2.1.14.16.1.3}

183
MN002730A01-AD
Appendix E: Alarms and events

Event Name Event ID Se- Event/Alarm Message Event

verity Category
ospfVirtIfConfigEr- .1.3.6.1.2.1.14.16.2.5 Info ospfVirtIfConfigError. The originator of the trap = {1 : ospfRouter- Informa-
ror Id : .1.3.6.1.2.1.14.1.1}, The Transit Area that the Virtual Link traverses = {2 : tional
ospfVirtIfAreaId : .1.3.6.1.2.1.14.9.1.1}, The Router ID of the virtual neighbor Event
= {3 : ospfVirtIfNeighbor : .1.3.6.1.2.1.14.9.1.2}, Type of error = {4 : ospfConfi-
gErrorType : .1.3.6.1.2.1.14.16.1.2}
ospfIfAuthFailure .1.3.6.1.2.1.14.16.2.6 Info ospfIfAuthFailure. The originator of the trap = {1 : ospfRouter- Informa-
Id : .1.3.6.1.2.1.14.1.1}, The IP address of this OSPF interface = {2 : ospfIfI- tional
pAddress : .1.3.6.1.2.1.14.7.1.1}, The value of ifIndex for interfaces having no Event
IP address = {3 : ospfAddressLessIf : .1.3.6.1.2.1.14.7.1.2}, The source IP
address = {4 : ospfPacketSrc : .1.3.6.1.2.1.14.16.1.4}, authTypeMismatch or
authFailure = {5 : ospfConfigErrorType : .1.3.6.1.2.1.14.16.1.2}, OSPF packet
types = {6 : ospfPacketType : .1.3.6.1.2.1.14.16.1.3}
ospfVirtIfAuthFai- .1.3.6.1.2.1.14.16.2.7 Info ospfVirtIfAuthFailure. The originator of the trap = {1 : ospfRouter- Informa-
lure Id : .1.3.6.1.2.1.14.1.1}, The Transit Area that the Virtual Link traverses = {2 : tional
ospfVirtIfAreaId : .1.3.6.1.2.1.14.9.1.1}, The Router ID of the virtual neighbor Event
= {3 : ospfVirtIfNeighbor : .1.3.6.1.2.1.14.9.1.2}, authTypeMismatch or auth-
Failure = {4 : ospfConfigErrorType : .1.3.6.1.2.1.14.16.1.2}, OSPF packet
types = {5 : ospfPacketType : .1.3.6.1.2.1.14.16.1.3}
ospfIfRxBadPacket .1.3.6.1.2.1.14.16.2.8 Info ospfIfRxBadPacket. The originator of the trap = {1 : ospfRouter- Informa-
Id : .1.3.6.1.2.1.14.1.1}, The IP address of this OSPF interface = {2 : ospfIfI- tional
pAddress : .1.3.6.1.2.1.14.7.1.1}, The value of ifIndex for interfaces IP ad- Event
dress = {3 : ospfAddressLessIf : .1.3.6.1.2.1.14.7.1.2}, The source IP address
= {4 : ospfPacketSrc : .1.3.6.1.2.1.14.16.1.4}, OSPF packet type = {5 : ospf-
PacketType : .1.3.6.1.2.1.14.16.1.3}
ospfVirtIfRxBad- .1.3.6.1.2.1.14.16.2.9 Info ospfVirtIfRxBadPacket. The originator of the trap = {1 : ospfRouter- Informa-
Packet Id : .1.3.6.1.2.1.14.1.1}, The Transit Area that the Virtual Link traverses = {2 : tional
ospfVirtIfAreaId : .1.3.6.1.2.1.14.9.1.1}, The Router ID of the virtual neighbor Event
= {3 : ospfVirtIfNeighbor : .1.3.6.1.2.1.14.9.1.2}, OSPF packet type = {4 : ospf-
PacketType : .1.3.6.1.2.1.14.16.1.3}
ospfTxRetransmit .1.3.6.1.2.1.14.16.2.10 Info ospfTxRetransmit. The originator of the trap = {1 : ospfRouter- Informa-
Id : .1.3.6.1.2.1.14.1.1}, The IP address of this OSPF interface = {2 : ospfIfI- tional
pAddress : .1.3.6.1.2.1.14.7.1.1}, The value of ifIndex for interfaces IP ad- Event
dress = {3 : ospfAddressLessIf : .1.3.6.1.2.1.14.7.1.2}, Destination = {4 :
ospfNbrRtrId : .1.3.6.1.2.1.14.10.1.3}, OSPF packet type = {5 : ospfPacket-
Type : .1.3.6.1.2.1.14.16.1.3}, The type of the link state advertisement = {6 :
ospfLsdbType : .1.3.6.1.2.1.14.4.1.2}, The Link State ID is an LS Type Specif-

184
 MN002730A01-AD
Appendix E: Alarms and events

Event Name Event ID Se- Event/Alarm Message Event

verity Category
ic field containing either a Router ID or an IP Address = {7 : ospfLsdbL-
sid : .1.3.6.1.2.1.14.4.1.3}, The originating router in the Autonomous System
= {8 : ospfLsdbRouterId : .1.3.6.1.2.1.14.4.1.4}
ospfVirtIfTxRe- .1.3.6.1.2.1.14.16.2.11 Info ospfVirtIfTxRetransmit . The originator of the trap = {1 : ospfRouter- Informa-
transmit Id : .1.3.6.1.2.1.14.1.1}, The Transit Area that the Virtual Link traverses = {2 : tional
ospfVirtIfAreaId : .1.3.6.1.2.1.14.9.1.1}, The Router ID of the virtual neighbor Event
= {3 : ospfVirtIfNeighbor : .1.3.6.1.2.1.14.9.1.2}, OSPF packet type = {4 : ospf-
PacketType : .1.3.6.1.2.1.14.16.1.3}, The type of the link state advertisement
= {5 : ospfLsdbType : .1.3.6.1.2.1.14.4.1.2}, The Link State ID is an LS Type
Specific field containing either a Router ID or an IP Address = {6 : ospfLsdbL-
sid : .1.3.6.1.2.1.14.4.1.3}, The originating router in the Autonomous System
= {7 : ospfLsdbRouterId : .1.3.6.1.2.1.14.4.1.4}
ospfOriginateLsa .1.3.6.1.2.1.14.16.2.12 Info ospfOriginateLsa. The originator of the trap = {1 : ospfRouter- Informa-
Id : .1.3.6.1.2.1.14.1.1}, 0.0.0.0 for AS Externals = {2 : ospfLsdbAr- tional
eaId : .1.3.6.1.2.1.14.4.1.1}, The type of the link state advertisement = {3 : Event
ospfLsdbType : .1.3.6.1.2.1.14.4.1.2}, The Link State ID is an LS Type Specif-
ic field containing either a Router ID or an IP Address = {4 : ospfLsdbL-
sid : .1.3.6.1.2.1.14.4.1.3}, The originating router in the Autonomous System
= {5 : ospfLsdbRouterId : .1.3.6.1.2.1.14.4.1.4}
ospfMaxAgeLsa .1.3.6.1.2.1.14.16.2.13 Info ospfMaxAgeLsa. The originator of the trap = {1 : ospfRouter- Informa-
Id : .1.3.6.1.2.1.14.1.1}, 0.0.0.0 for AS Externals = {2 : ospfLsdbAr- tional
eaId : .1.3.6.1.2.1.14.4.1.1}, The type of the link state advertisement = {3 : Event
ospfLsdbType : .1.3.6.1.2.1.14.4.1.2}, The Link State ID is an LS Type Specif-
ic field containing either a Router ID or an IP Address = {4 : ospfLsdbL-
sid : .1.3.6.1.2.1.14.4.1.3}, The originating router in the Autonomous System
= {5 : ospfLsdbRouterId : .1.3.6.1.2.1.14.4.1.4}
ospfLsdbOverflow .1.3.6.1.2.1.14.16.2.14 Info ospfLsdbOverflow. The originator of the trap = {1 : ospfRouter- Informa-
Id : .1.3.6.1.2.1.14.1.1}, The maximum number of non-default AS-external tional
LSAs entries that can be stored in the link state database = {2 : ospfExtLsd- Event
bLimit : .1.3.6.1.2.1.14.1.11}
ospfLsdbApproa- .1.3.6.1.2.1.14.16.2.15 Info ospfLsdbApproachingOverflow. The originator of the trap = {1 : ospfRouter- Informa-
chingOverflow Id : .1.3.6.1.2.1.14.1.1}, The maximum number of non-default AS-external tional
LSAs entries that can be stored in the link state database = {2 : ospfExtLsd- Event
bLimit : .1.3.6.1.2.1.14.1.11}

185
MN002730A01-AD
Appendix E: Alarms and events

Event Name Event ID Se- Event/Alarm Message Event

verity Category
ospfIfStateChange .1.3.6.1.2.1.14.16.2.16 Info ospfIfStateChange. The originator of the trap = {1 : ospfRouter- Informa-
Id : .1.3.6.1.2.1.14.1.1}, The IP address of this OSPF interface = {2 : ospfIfI- tional
pAddress : .1.3.6.1.2.1.14.7.1.1}, The value of ifIndex for interfaces having no Event
IP address = {3 : ospfAddressLessIf : .1.3.6.1.2.1.14.7.1.2}, The new state =
{4 : ospfIfState : .1.3.6.1.2.1.14.7.1.12}
ospfNssaTransla- .1.3.6.1.2.1.14.16.2.17 Info ospfNssaTranslatorStatusChange. The originator of the trap = {1 : ospfRou- Informa-
torStatusChange terId : .1.3.6.1.2.1.14.1.1}, A 32-bit integer uniquely identifying an area = {2 : tional
ospfAreaId : .1.3.6.1.2.1.14.2.1.1}, The current translation status = {3 : osp- Event
fAreaNssaTranslatorState : .1.3.6.1.2.1.14.2.1.12}
ospfRestartStatu- .1.3.6.1.2.1.14.16.2.18 Info ospfRestartStatusChange. The originator of the trap = {1 : ospfRouter- Informa-
sChange Id : .1.3.6.1.2.1.14.1.1}, Current status of OSPF graceful restart = {2 : osp- tional
fRestartStatus : .1.3.6.1.2.1.14.1.21}, Configured OSPF graceful restart time- Event
out interval = {3 : ospfRestartInterval : .1.3.6.1.2.1.14.1.19}, The outcome of
the last attempt at a graceful restart = {4 : ospfRestartExitRea-
son : .1.3.6.1.2.1.14.1.23}
ospfNbrRestar- .1.3.6.1.2.1.14.16.2.19 Info ospfNbrRestartHelperStatusChange. The originator of the trap = {1 : osp- Informa-
tHelperStatu- fRouterId : .1.3.6.1.2.1.14.1.1}, The IP address this neighbor is using in its IP tional
sChange source address = {2 : ospfNbrIpAddr : .1.3.6.1.2.1.14.10.1.1}, The corre- Event
sponding value of ifIndex in the Internet Standard MIB = {3 : ospfNbrAddres-
sLessIndex : .1.3.6.1.2.1.14.10.1.2}, The neighboring router in the Autono-
mous System = {4 : ospfNbrRtrId : .1.3.6.1.2.1.14.10.1.3}, Indicates whether
the router is acting as a graceful restart helper for the neighbor = {5 : ospfNbr-
RestartHelperStatus : .1.3.6.1.2.1.14.10.1.12}, Remaining time in current
OSPF graceful restart interval = {6 : ospfNbrRestartHelper-
Age : .1.3.6.1.2.1.14.10.1.13}, The outcome of the last attempt at acting as a
graceful restart helper for the neighbor = {7 : ospfNbrRestartHelperExitRea-
son : .1.3.6.1.2.1.14.10.1.14}
ospfVirtNbrRestar- .1.3.6.1.2.1.14.16.2.20 Info ospfVirtNbrRestartHelperStatusChange. The originator of the trap = {1 : osp- Informa-
tHelperStatu- fRouterId : .1.3.6.1.2.1.14.1.1}, The Transit Area Identifier = {2 : ospfVirtN- tional
sChange brArea : .1.3.6.1.2.1.14.11.1.1}, The neighboring router in the Autonomous Event
System = {3 : ospfVirtNbrRtrId : .1.3.6.1.2.1.14.11.1.2}, Indicates whether the
router is acting as a graceful restart helper for the neighbor = {4 : ospfVirtNbr-
RestartHelperStatus : .1.3.6.1.2.1.14.11.1.9}, Remaining time in current
OSPF graceful restart = {5 : ospfVirtNbrRestartHelper-
Age : .1.3.6.1.2.1.14.11.1.10}, The outcome of the last attempt at acting as a
graceful restart helper for the neighbor = {6 : ospfVirtNbrRestartHelperExi-
tReason : .1.3.6.1.2.1.14.11.1.11}

186
 MN002730A01-AD
Appendix E: Alarms and events

Event Name Event ID Se- Event/Alarm Message Event

verity Category
ieee8021Span- .1.3.111.2.802.1.1.3.0.1 Info ieee8021SpanningTreeNewRoot. The sending agent has become the new Informa-
ningTreeNewRoot root of the Spanning Tree. tional
Event
ieee8021Span- .1.3.111.2.802.1.1.3.0.2 Info ieee8021SpanningTreeTopologyChange. Bridge ports transitioned (from the Informa-
ningTreeTopology- Learning state/Forwarding to the Forwarding/Learning state). tional
Change Event
nsNotifyStart .1.3.6.1.4.1.8072.4.0.1 Info nsNotifyStart. Agent has started running. Informa-
tional
Event
nsNotifyShutdown .1.3.6.1.4.1.8072.4.0.2 Info nsNotifyShutdown. Agent is in the process of being shut down. Informa-
tional
Event
nsNotifyRestart .1.3.6.1.4.1.8072.4.0.3 Info nsNotifyRestart. Agent has been restarted. Informa-
tional
Event
entConfigChange .1.3.6.1.2.1.47.2.0.1 Info A configuration change has occurred. Informa-
tional
Event
vrrpv3NewMaster .1.3.6.1.2.1.207.0.1 Info vrrpv3NewMaster. New Master IP Address = {1 : vrrpv3OperationsMasterI- Informa-
pAddr : .1.3.6.1.2.1.207.1.1.1.1.3.*}, Reason of the transition to Master = {2 : tional
vrrpv3StatisticsNewMasterReason : .1.3.6.1.2.1.207.1.2.5.1.2.*} Event
vrrpv3ProtoError .1.3.6.1.2.1.207.0.2 Info vrrpv3ProtoError. Reason of the protocol error = {1 : vrrpv3StatisticsProtoErr- Informa-
Reason : .1.3.6.1.2.1.207.1.2.5.1.6.*} tional
Event

E.4
CM Bridge Alarms and Events Overview
Events and alarms are reported for the CM Bridge as follows:

E.4.1
CM Bridge Alarms
Alarms are reported for the CM Bridge as follows:

187
MN002730A01-AD
Appendix E: Alarms and events

Event Name Severity Event/Alarm Message Event/Alarm Description Event Category Manager Entity
NcmSynchronizedSta- CommFailure Device {0} is not reported by Device {0} is not reported by Communication NCM Synchronized Status
tus the system. the system. Alarm
XrtConnStatus Major XRT connection status. XRT connection has failed. Equipment XRT Connection Status
Alarm
VrcConnStatus Major VRC connection status. VRC connection has failed. Equipment VRC Connection Status
Alarm
PnConnStatus Major PN connection status. PN connection has failed. Equipment PN Connection Status
Alarm
XrtAuthFailure Major XRT authentication failure. XRT authentication failure. Equipment XRT Auth Failure
Alarm
CmbLicenseNotFound Major CMB license not found. CM Bridge license not found. Equipment CMB License Not Found
Alarm
BridgedTalkPathsZero Major Bridged talk paths set to Bridged talk paths set to Equipment Bridged Talk Paths Zero
zero. zero. Alarm
TalkPathsExceeded Major Number of allowed active Number of allowed active Equipment Talk Paths Exceeded
talk paths exceeded. talkpaths exceeded. Alarm
LcpPnConnStatus Major LCP PN connection status. LCP PN connection has Equipment LCP PN Connection Status
failed. Alarm
LcpVrcInstanceConn- Major LCP VRC instance connec- LCP VRC instance connec- Equipment LCP VRC Instance Con-
Status tion status. tion has failed. Alarm nection Status

E.4.2
CM Bridge Events
Events are reported for the CM Bridge as follows:

Event Name Severity Event/Alarm Message Event/Alarm Description Event Category Manager Entity
PropertyChanged Info Property {0} changed from {1} to Property {0} changed from {1} to Informational Event Property Changed
{2}. {2}.
DeviceStatus.Inactive.Dis- Info Current device status: Inactive Current Device Status: Inactive Informational Event Device Status
abled (Disabled). (Disabled).
DeviceStatus.Active.Ena- Info Current device status: Active (En- Current device status: Active (En- Informational Event Device Status
bled abled). abled).

188
 MN002730A01-AD
Appendix E: Alarms and events

Event Name Severity Event/Alarm Message Event/Alarm Description Event Category Manager Entity
DeviceStatus.Inac- Info Current device status: Inactive Current device status: Inactive Informational Event Device Status
tive.Alarm (Alarm). (Alarm).
DeviceStatus.Inac- Info Current device status: Inactive Current device status: Inactive Informational Event Device Status
tive.Locked (Locked). (Locked).
DeviceStatus.Un- Info Current device status: Unknown Current device status: Unknown Informational Event Device Status
known.NotReported (Not Reported). (Not Reported).
DeviceStatus.Unknown Info Current device status: Unknown. Current device status: Unknown. Informational Event Device Status

E.5
CMSS Alarms and Events Overview
Events and alarms are reported for the CMSS as follows:

E.5.1
CMSS Generic Events
The following table shows information on all generic CMSS events that are reported to SA.

Event ID Se- Event/Alarm Message Event/Alarm Description Event

verity Catego-
ry
AccountCreatedEvent Info An account was created on host {host.name} An account was created on host {host.name} Informa-
tional
Event
AccountRemovedEvent Info Account {account} was removed on host Account {account} was removed on host Informa-
{host.name} {host.name} tional
Event
AccountUpdatedEvent Info An account was updated on host {host.name} An account was updated on host {host.name} Informa-
tional
Event
AdminPasswordNotChangedE- Info The default password for the root user on the The default password for the root user on the Informa-
vent host {host.name} has not been changed host {host.name} has not been changed tional
Event

189
MN002730A01-AD
Appendix E: Alarms and events
Event ID
AllVirtualMachinesLicensedEvent Info
CanceledHostOperationEvent
ClusterComplianceCheckedEvent Info
ClusterCreatedEvent
ClusterDestroyedEvent
ClusterOvercommittedEvent
ClusterReconfiguredEvent
ClusterStatusChangedEvent
com.vmware.vc.datastore.Upda-
tedVmFilesEvent
com.vmware.vc.datastore.Upda-
teVmFilesFailedEvent
190
Se- Event/Alarm Message Event/Alarm Description Event
verity Catego-
ry
All running virtual machines are licensed All running virtual machines are licensed Informa-
tional
Event
Info The operation performed on host {host.name} The operation performed on host {host.name} Informa-
in {datacenter.name} was canceled in {datacenter.name} was canceled tional
Event
Checked cluster for compliance Checked cluster for compliance Informa-
tional
Event
Info Created cluster {computeResource.name} in Created cluster {computeResource.name} in Informa-
{datacenter.name} {datacenter.name} tional
Event
Info Removed cluster {computeResource.name} Removed cluster {computeResource.name} Informa-
in datacenter {datacenter.name} in datacenter {datacenter.name} tional
Event
Critical Insufficient capacity in cluster {computeRe- Insufficient capacity in cluster {computeRe- Informa-
source.name} to satisfy resource configura- source.name} to satisfy resource configura- tional
tion in {datacenter.name} tion in {datacenter.name} Event
Info Reconfigured cluster {computeRe- Reconfigured cluster {computeRe- Informa-
source.name} in datacenter {datacen- source.name} in datacenter {datacen- tional
ter.name} ter.name} Event
Info Configuration status on cluster {computeRe- Configuration status on cluster {computeRe- Informa-
source.name} changed from {oldSta- source.name} changed from {oldSta- tional
tus.@enum.ManagedEntity.Status} to {newS- tus.@enum.ManagedEntity.Status} to {newS- Event
tatus.@enum.ManagedEntity.Status} in {da- tatus.@enum.ManagedEntity.Status} in {da-
tacenter.name} tacenter.name}
Info com.vmware.vc.datastore.UpdatedVmFilesE- com.vmware.vc.datastore.UpdatedVmFilesE- Informa-
vent|Updated VM files on datastore vent|Updated VM files on datastore tional
{ds.name} using host {hostName} {ds.name} using host {hostName} Event
Critical com.vmware.vc.datastore.UpdateVmFiles- com.vmware.vc.datastore.UpdateVmFilesFai- Informa-
FailedEvent|Failed to update VM files on da- ledEvent|Failed to update VM files on data- tional
tastore {ds.name} using host {hostName} store {ds.name} using host {hostName} Event

Event ID Se- Event/Alarm Message
verity
com.vmware.vc.datastore.Upda- Info com.vmware.vc.datastore.UpdatingVmFile-
tingVmFilesEvent sEvent|Updating VM files on datastore
{ds.name} using host {hostName}
com.vmware.vc.HA.DasHost- Critical com.vmware.vc.HA.DasHostCompleteDatas-
CompleteDatastoreFailureEvent toreFailureEvent|All shared datastores failed
on the host {hostName} in cluster {comput-
eResource.name} in {datacenter.name}
com.vmware.vc.HA.DasHost- Critical com.vmware.vc.HA.DasHostCompleteNet-
CompleteNetworkFailureEvent workFailureEvent|All VM networks failed on
the host {hostName} in cluster {computeRe-
source.name} in {datacenter.name}
com.vmware.vc.npt.VmAdapter- Info com.vmware.vc.npt.VmAdapterEnteredPass-
EnteredPassthroughEvent throughEvent|Network passthrough is active
on adapter {deviceLabel} of virtual machine
{vm.name} on host {host.name} in {datacen-
ter.name}
com.vmware.vc.npt.VmAdapter- Info com.vmware.vc.npt.VmAdapterExitedPass-
ExitedPassthroughEvent throughEvent|Network passthrough is inac-
tive on adapter {deviceLabel} of virtual ma-
chine {vm.name} on host {host.name} in {da-
tacenter.name}
com.vmware.vc.vcp.TestEndE- Info com.vmware.vc.vcp.TestEndEvent|VM Com-
vent ponent Protection test ends on host
{host.name} in cluster {computeRe-
source.name} in datacenter {datacen-
ter.name}
com.vmware.vc.vcp.TestStartE- Info re.vc.vcp.TestStartEvent|VM Component
vent Protection test starts on host {host.name} in
cluster {computeResource.name} in datacen-
ter {datacenter.name}
com.vmware.vc.vcp.VmDatastor- Critical com.vmware.vc.vcp.VmDatastoreFailedE-
eFailedEvent vent|Virtual machine {vm.name} on host
{host.name} in cluster {computeRe-
MN002730A01-AD
Appendix E: Alarms and events
Event/Alarm Description Event
Catego-
ry
com.vmware.vc.datastore.UpdatingVmFile- Informa-
sEvent|Updating VM files on datastore tional
{ds.name} using host {hostName} Event
com.vmware.vc.HA.DasHostCompleteDatas- Informa-
toreFailureEvent|All shared datastores failed tional
on the host {hostName} in cluster {comput- Event
eResource.name} in {datacenter.name}
com.vmware.vc.HA.DasHostCompleteNet- Informa-
workFailureEvent|All VM networks failed on tional
the host {hostName} in cluster {computeRe- Event
source.name} in {datacenter.name}
com.vmware.vc.npt.VmAdapterEnteredPass- Informa-
throughEvent|Network passthrough is active tional
on adapter {deviceLabel} of virtual machine Event
{vm.name} on host {host.name} in {datacen-
ter.name}
com.vmware.vc.npt.VmAdapterExitedPass- Informa-
throughEvent|Network passthrough is inac- tional
tive on adapter {deviceLabel} of virtual ma- Event
chine {vm.name} on host {host.name} in {da-
tacenter.name}
com.vmware.vc.vcp.TestEndEvent|VM Com- Informa-
ponent Protection test ends on host tional
{host.name} in cluster {computeRe- Event
source.name} in datacenter {datacen-
ter.name}
re.vc.vcp.TestStartEvent|VM Component Informa-
Protection test starts on host {host.name} in tional
cluster {computeResource.name} in datacen- Event
ter {datacenter.name}
com.vmware.vc.vcp.VmDatastoreFailedE- Informa-
vent|Virtual machine {vm.name} on host tional
{host.name} in cluster {computeRe- Event
191
MN002730A01-AD
Appendix E: Alarms and events
Event ID
com.vmware.vc.vcp.VmNetwork- Critical com.vmware.vc.vcp.VmNetworkFailedEvent|
FailedEvent
com.vmware.vc.vmam.VmAp-
pHealthMonitoringStateChange-
dEvent
CustomizationFailed
CustomizationLinuxIdentityFailed Warn- An error occurred while setting up Linux iden- An error occurred while setting up Linux iden- Informa-
CustomizationNetworkSetup-
Failed
CustomizationStartedEvent
CustomizationSucceeded
CustomizationSysprepFailed
192
Se- Event/Alarm Message Event/Alarm Description Event
verity Catego-
ry
source.name} in datacenter {datacen- source.name} in datacenter {datacen-
ter.name} lost access to {datastore} ter.name} lost access to {datastore}
com.vmware.vc.vcp.VmNetworkFailedEvent| Informa-
Virtual machine {vm.name} on host Virtual machine {vm.name} on host tional
{host.name} in cluster {computeRe- {host.name} in cluster {computeRe- Event
source.name} in datacenter {datacen- source.name} in datacenter {datacen-
ter.name} lost access to {network} ter.name} lost access to {network}
Warn- com.vmware.vc.vmam.VmAppHealthMonitor- com.vmware.vc.vmam.VmAppHealthMonitor- Informa-
ing ingStateChangedEvent|Application heartbeat ingStateChangedEvent|Application heartbeat tional
status changed to {status} for {vm.name} on status changed to {status} for {vm.name} on Event
{host.name} in cluster {computeRe- {host.name} in cluster {computeRe-
source.name} in {datacenter.name} source.name} in {datacenter.name}
Warn- Cannot complete customization of VM Cannot complete customization of VM Informa-
ing {vm.name}. See customization log at {logLo- {vm.name}. See customization log at {logLo- tional
cation} on the guest OS for details. cation} on the guest OS for details. Event
ing tity. See log file '{logLocation}' on guest OS tity. See log file '{logLocation}' on guest OS tional
for details. for details. Event
Warn- An error occurred while setting up network An error occurred while setting up network Informa-
ing properties of the guest OS. See the log file properties of the guest OS. See the log file tional
{logLocation} in the guest OS for details. {logLocation} in the guest OS for details. Event
Info Started customization of VM {vm.name}. Started customization of VM {vm.name}. Informa-
Customization log located at {logLocation} in Customization log located at {logLocation} in tional
the guest OS. the guest OS. Event
Info Customization of VM {vm.name} succeeded. Customization of VM {vm.name} succeeded. Informa-
Customization log located at {logLocation} in Customization log located at {logLocation} in tional
the guest OS. the guest OS. Event
Warn- The version of Sysprep {sysprepVersion} pro- The version of Sysprep {sysprepVersion} pro- Informa-
ing vided for customizing VM {vm.name} does vided for customizing VM {vm.name} does tional
not match the version of guest OS {system- not match the version of guest OS {system- Event
Version}. See the log file {logLocation} in the Version}. See the log file {logLocation} in the
guest OS for more information. guest OS for more information.
 MN002730A01-AD
Appendix E: Alarms and events

Event ID Se- Event/Alarm Message Event/Alarm Description Event

CustomizationUnknownFailure
DasAdmissionControlDisabledE- Info
vent
DasAdmissionControlEnabledE-
vent
DasAgentFoundEvent
DasAgentUnavailableEvent
DasClusterIsolatedEvent
DasDisabledEvent
DasEnabledEvent
DasHostFailedEvent
DasHostIsolatedEvent
verity Catego-
ry
Warn- An error occurred while customizing VM An error occurred while customizing VM Informa-
ing {vm.name}. For details reference the log file {vm.name}. For details reference the log file tional
{logLocation} in the guest OS. {logLocation} in the guest OS. Event
HA admission control disabled on cluster HA admission control disabled on cluster Informa-
{computeResource.name} in {datacen- {computeResource.name} in {datacen- tional
ter.name} ter.name} Event
Info HA admission control enabled on cluster HA admission control enabled on cluster Informa-
{computeResource.name} in {datacen- {computeResource.name} in {datacen- tional
ter.name} ter.name} Event
Info Re-established contact with a primary host in Re-established contact with a primary host in Informa-
this HA cluster this HA cluster tional
Event
Critical Unable to contact a primary HA agent in clus- Unable to contact a primary HA agent in clus- Informa-
ter {computeResource.name} in {datacen- ter {computeResource.name} in {datacen- tional
ter.name} ter.name} Event
Critical All hosts in the HA cluster {computeRe- All hosts in the HA cluster {computeRe- Informa-
source.name} in {datacenter.name} were iso- source.name} in {datacenter.name} were iso- tional
lated from the network. Check the network lated from the network. Check the network Event
configuration for proper network redundancy configuration for proper network redundancy
in the management network. in the management network.
Info HA disabled on cluster {computeRe- HA disabled on cluster {computeRe- Informa-
source.name} in {datacenter.name} source.name} in {datacenter.name} tional
Event
Info HA enabled on cluster {computeRe- HA enabled on cluster {computeRe- Informa-
source.name} in {datacenter.name} source.name} in {datacenter.name} tional
Event
Critical A possible host failure has been detected by A possible host failure has been detected by Informa-
HA on {failedHost.name} in cluster {comput- HA on {failedHost.name} in cluster {comput- tional
eResource.name} in {datacenter.name} eResource.name} in {datacenter.name} Event
Warn- Host {isolatedHost.name} has been isolated Host {isolatedHost.name} has been isolated Informa-
ing from cluster {computeResource.name} in {da- from cluster {computeResource.name} in {da- tional
tacenter.name} tacenter.name} Event

193
MN002730A01-AD
Appendix E: Alarms and events

Event ID Se- Event/Alarm Message Event/Alarm Description Event

verity Catego-
ry
DrsDisabledEvent Info Disabled DRS on cluster {computeRe- Disabled DRS on cluster {computeRe- Informa-
source.name} in datacenter {datacen- source.name} in datacenter {datacen- tional
ter.name} ter.name} Event
DrsEnabledEvent Info Enabled DRS on {computeResource.name} Enabled DRS on {computeResource.name} Informa-
with automation level {behavior} in {datacen- with automation level {behavior} in {datacen- tional
ter.name} ter.name} Event
DrsEnteringStandbyModeEvent Info DRS is putting {host.name} into standby DRS is putting {host.name} into standby Informa-
mode mode tional
Event
DrsExitingStandbyModeEvent Info DRS is moving {host.name} out of standby DRS is moving {host.name} out of standby Informa-
mode mode tional
Event
DrsExitStandbyModeFailedEvent Critical DRS cannot move {host.name} out of stand- DRS cannot move {host.name} out of stand- Informa-
by mode by mode tional
Event
DrsInvocationFailedEvent Critical DRS invocation not completed DRS invocation not completed Informa-
tional
Event
DrsRecoveredFromFailureEvent Info DRS has recovered from the failure DRS has recovered from the failure Informa-
tional
Event
DrsResourceConfigureFailedE- Critical Unable to apply DRS resource settings on Unable to apply DRS resource settings on Informa-
vent host {host.name} in {datacenter.name}. {rea- host {host.name} in {datacenter.name}. {rea- tional
son.msg}. This can significantly reduce the son.msg}. This can significantly reduce the Event
effectiveness of DRS. effectiveness of DRS.
DrsResourceConfigureSyncedE- Info Resource configuration specification returns Resource configuration specification returns Informa-
vent to synchronization from previous failure on to synchronization from previous failure on tional
host '{host.name}' in {datacenter.name} host '{host.name}' in {datacenter.name} Event
DrsRuleComplianceEvent Info {vm.name} on {host.name} in {datacen- {vm.name} on {host.name} in {datacen- Informa-
ter.name} is now compliant with DRS VM- ter.name} is now compliant with DRS VM- tional
Host affinity rules Host affinity rules Event

194
 MN002730A01-AD
Appendix E: Alarms and events

Event ID Se- Event/Alarm Message Event/Alarm Description Event

verity Catego-
ry
DrsRuleViolationEvent Info {vm.name} on {host.name} in {datacen- {vm.name} on {host.name} in {datacen- Informa-
ter.name} is violating a DRS VM-Host affinity ter.name} is violating a DRS VM-Host affinity tional
rule rule Event
DrsVmMigratedEvent Info DRS migrated {vm.name} from {source- DRS migrated {vm.name} from {source- Informa-
Host.name} to {host.name} in cluster {com- Host.name} to {host.name} in cluster {com- tional
puteResource.name} in {datacenter.name} puteResource.name} in {datacenter.name} Event
DrsVmPoweredOnEvent Info DRS powered On {vm.name} on {host.name} DRS powered On {vm.name} on {host.name} Informa-
in {datacenter.name} in {datacenter.name} tional
Event
DuplicateIpDetectedEvent Warn- Virtual machine {macAddress} on host Virtual machine {macAddress} on host Informa-
ing {host.name} has a duplicate IP {duplicateIP} {host.name} has a duplicate IP {duplicateIP} tional
Event
DvsHostStatusUpdated Info The host {hostMember.name} changed sta- The host {hostMember.name} changed sta- Informa-
tus on the vNetwork Distributed Switch tus on the vNetwork Distributed Switch tional
{dvs.name} in {datacenter.name} {dvs.name} in {datacenter.name} Event
EnteredMaintenanceModeEvent Info Host {host.name} in {datacenter.name} has Host {host.name} in {datacenter.name} has Informa-
entered maintenance mode entered maintenance mode tional
Event
EnteredStandbyModeEvent Info The host {host.name} is in standby mode The host {host.name} is in standby mode Informa-
tional
Event
EnteringMaintenanceModeEvent Info Host {host.name} in {datacenter.name} has Host {host.name} in {datacenter.name} has Informa-
started to enter maintenance mode started to enter maintenance mode tional
Event
EnteringStandbyModeEvent Info The host {host.name} is entering standby The host {host.name} is entering standby Informa-
mode mode tional
Event
esx.clear.net.connectivity.re- Info esx.clear.net.connectivity.restored|Network esx.clear.net.connectivity.restored|Network Informa-
stored connectivity restored on virtual switch {1}, connectivity restored on virtual switch {1}, tional
portgroups: {2}. Physical NIC {3} is up. portgroups: {2}. Physical NIC {3} is up. Event
esx.clear.net.dvport.connectivi- Info esx.clear.net.dvport.connectivity.restored| esx.clear.net.dvport.connectivity.restored| Informa-
ty.restored Network connectivity restored on DVPorts: Network connectivity restored on DVPorts: tional
{1}. Physical NIC {2} is up. {1}. Physical NIC {2} is up. Event

195
MN002730A01-AD
Appendix E: Alarms and events
Event ID
esx.clear.net.dvport.redundan-
cy.restored
esx.clear.net.redundancy.re-
stored
esx.clear.net.vmnic.linkstate.up
esx.clear.storage.connectivity.re- Info
stored
esx.clear.storage.redundancy.re- Info
stored
esx.problem.apei.bert.memo-
ry.error.corrected
esx.problem.apei.bert.memo-
ry.error.fatal
esx.problem.apei.bert.memo-
ry.error.recoverable
196
Se- Event/Alarm Message Event/Alarm Description Event
verity Catego-
ry
Info esx.clear.net.dvport.redundancy.restored|Up- esx.clear.net.dvport.redundancy.restored|Up- Informa-
link redundancy restored on DVPorts: {1}. link redundancy restored on DVPorts: {1}. tional
Physical NIC {2} is up. Physical NIC {2} is up. Event
Info esx.clear.net.redundancy.restored|Uplink re- esx.clear.net.redundancy.restored|Uplink re- Informa-
dundancy restored on virtual switch {1}, dundancy restored on virtual switch {1}, tional
portgroups: {2}. Physical NIC {3} is up. portgroups: {2}. Physical NIC {3} is up. Event
Info esx.clear.net.vmnic.linkstate.up|Physical NIC esx.clear.net.vmnic.linkstate.up|Physical NIC Informa-
{1} linkstate is up. {1} linkstate is up. tional
Event
esx.clear.storage.connectivity.restored|Con- esx.clear.storage.connectivity.restored|Con- Informa-
nectivity to storage device {1} (Datastores: nectivity to storage device {1} (Datastores: tional
{2}) restored. Path {3} is active again. {2}) restored. Path {3} is active again. Event
esx.clear.storage.redundancy.restored|Path esx.clear.storage.redundancy.restored|Path Informa-
redundancy to storage device {1} (Data- redundancy to storage device {1} (Data- tional
stores: {2}) restored. Path {3} is active again. stores: {2}) restored. Path {3} is active again. Event
Critical esx.problem.apei.bert.memory.error.correct- esx.problem.apei.bert.memory.error.correct- Informa-
ed|A corrected memory error occurred in last ed|A corrected memory error occurred in last tional
boot. The following details were reported. boot. The following details were reported. Event
Physical Addr: {1}, Physical Addr Mask: {2}, Physical Addr: {1}, Physical Addr Mask: {2},
Node: {3}, Card: {4}, Module: {5}, Bank: {6}, Node: {3}, Card: {4}, Module: {5}, Bank: {6},
Device: {7}, Row: {8}, Column: {9} Error type: Device: {7}, Row: {8}, Column: {9} Error type:
{10} {10}
Critical esx.problem.apei.bert.memory.error.fatal|A esx.problem.apei.bert.memory.error.fatal|A Informa-
fatal memory error occurred in the last boot. fatal memory error occurred in the last boot. tional
The following details were reported. Physical The following details were reported. Physical Event
Addr: {1}, Physical Addr Mask: {2}, Node: {3}, Addr: {1}, Physical Addr Mask: {2}, Node: {3},
Card: {4}, Module: {5}, Bank: {6}, Device: {7}, Card: {4}, Module: {5}, Bank: {6}, Device: {7},
Row: {8}, Column: {9} Error type: {10} Row: {8}, Column: {9} Error type: {10}
Critical esx.problem.apei.bert.memory.error.recover- esx.problem.apei.bert.memory.error.recover- Informa-
able|A recoverable memory error occurred in able|A recoverable memory error occurred in tional
last boot. The following details were reported. last boot. The following details were reported. Event
Physical Addr: {1}, Physical Addr Mask: {2}, Physical Addr: {1}, Physical Addr Mask: {2},
Node: {3}, Card: {4}, Module: {5}, Bank: {6}, Node: {3}, Card: {4}, Module: {5}, Bank: {6},

Event ID
esx.problem.apei.bert.pcie.er-
ror.corrected
esx.problem.apei.bert.pcie.er-
ror.fatal
esx.problem.apei.bert.pcie.er-
ror.recoverable
esx.problem.iorm.nonviworkload
esx.problem.net.connectivity.lost Critical esx.problem.net.connectivity.lost|Lost net-
esx.problem.net.dvport.connec-
tivity.lost
MN002730A01-AD
Appendix E: Alarms and events
Se- Event/Alarm Message Event/Alarm Description Event
verity Catego-
ry
Device: {7}, Row: {8}, Column: {9} Error type: Device: {7}, Row: {8}, Column: {9} Error type:
{10} {10}
Critical esx.problem.apei.bert.pcie.error.corrected|A esx.problem.apei.bert.pcie.error.corrected|A Informa-
corrected PCIe error occurred in last boot. corrected PCIe error occurred in last boot. tional
The following details were reported. Port The following details were reported. Port Event
Type: {1}, Device: {2}, Bus #: {3}, Function: Type: {1}, Device: {2}, Bus #: {3}, Function:
{4}, Slot: {5}, Device Vendor: {6}, Version: {7}, {4}, Slot: {5}, Device Vendor: {6}, Version: {7},
Command Register: {8}, Status Register: {9}. Command Register: {8}, Status Register: {9}.
Critical esx.problem.apei.bert.pcie.error.fatal|Plat- esx.problem.apei.bert.pcie.error.fatal|Plat- Informa-
form encounterd a fatal PCIe error in last form encounterd a fatal PCIe error in last tional
boot. The following details were reported. boot. The following details were reported. Event
Port Type: {1}, Device: {2}, Bus #: {3}, Func- Port Type: {1}, Device: {2}, Bus #: {3}, Func-
tion: {4}, Slot: {5}, Device Vendor: {6}, Ver- tion: {4}, Slot: {5}, Device Vendor: {6}, Ver-
sion: {7}, Command Register: {8}, Status sion: {7}, Command Register: {8}, Status
Register: {9}. Register: {9}.
Critical esx.problem.apei.bert.pcie.error.recoverable| esx.problem.apei.bert.pcie.error.recoverable| Informa-
A recoverable PCIe error occurred in last A recoverable PCIe error occurred in last tional
boot. The following details were reported. boot. The following details were reported. Event
Port Type: {1}, Device: {2}, Bus #: {3}, Func- Port Type: {1}, Device: {2}, Bus #: {3}, Func-
tion: {4}, Slot: {5}, Device Vendor: {6}, Ver- tion: {4}, Slot: {5}, Device Vendor: {6}, Ver-
sion: {7}, Command Register: {8}, Status sion: {7}, Command Register: {8}, Status
Register: {9}. Register: {9}.
Warn- esx.problem.iorm.nonviworkload|An external esx.problem.iorm.nonviworkload|An external Informa-
ing I/O activity is detected on datastore {1}, this I/O activity is detected on datastore {1}, this tional
is an unsupported configuration. Consult the is an unsupported configuration. Consult the Event
Resource Management Guide or follow the Resource Management Guide or follow the
Ask VMware link for more information. Ask VMware link for more information.
esx.problem.net.connectivity.lost|Lost net- Informa-
work connectivity on virtual switch {1}. Physi- work connectivity on virtual switch {1}. Physi- tional
cal NIC {2} is down. Affected portgroups:{3}. cal NIC {2} is down. Affected portgroups:{3}. Event
Critical esx.problem.net.dvport.connectivity.lost|Lost esx.problem.net.dvport.connectivity.lost|Lost Informa-
network connectivity on DVPorts: {1}. Physi- network connectivity on DVPorts: {1}. Physi- tional
cal NIC {2} is down. cal NIC {2} is down. Event
197
MN002730A01-AD
Appendix E: Alarms and events
Event ID
esx.problem.net.dvport.redun-
dancy.degraded
esx.problem.net.dvport.redun-
dancy.lost
esx.problem.net.e1000.tso6.not-
supported
esx.problem.net.migrate.bind-
tovmk
esx.problem.net.proxy-
switch.port.unavailable
esx.problem.net.redundancy.de-
graded
esx.problem.net.redundancy.lost Warn- esx.problem.net.redundancy.lost|Lost uplink
ing
198
Se- Event/Alarm Message Event/Alarm Description Event
verity Catego-
ry
Warn- esx.problem.net.dvport.redundancy.degrad- esx.problem.net.dvport.redundancy.degrad- Informa-
ing ed|Uplink redundancy degraded on DVPorts: ed|Uplink redundancy degraded on DVPorts: tional
{1}. Physical NIC {2} is down. {1}. Physical NIC {2} is down. Event
Warn- esx.problem.net.dvport.redundancy.lost|Lost esx.problem.net.dvport.redundancy.lost|Lost Informa-
ing uplink redundancy on DVPorts: {1}. Physical uplink redundancy on DVPorts: {1}. Physical tional
NIC {2} is down. NIC {2} is down. Event
Critical esx.problem.net.e1000.tso6.notsupported| esx.problem.net.e1000.tso6.notsupported| Informa-
Guest-initiated IPv6 TCP Segmentation Off- Guest-initiated IPv6 TCP Segmentation Off- tional
load (TSO) packets ignored. Manually disa- load (TSO) packets ignored. Manually disa- Event
ble TSO inside the guest operating system in ble TSO inside the guest operating system in
virtual machine {1}, or use a different virtual virtual machine {1}, or use a different virtual
adapter. adapter.
Warn- esx.problem.net.migrate.bindtovmk|The ESX esx.problem.net.migrate.bindtovmk|The ESX Informa-
ing advanced configuration option /Migrate/ advanced configuration option /Migrate/ tional
Vmknic is set to an invalid vmknic: {1}. / Vmknic is set to an invalid vmknic: {1}. / Event
Migrate/Vmknic specifies a vmknic that vMo- Migrate/Vmknic specifies a vmknic that vMo-
tion binds to for improved performance. Up- tion binds to for improved performance. Up-
date the configuration option with a valid date the configuration option with a valid
vmknic. Alternatively, if you do not want vMo- vmknic. Alternatively, if you do not want vMo-
tion to bind to a specific vmknic, remove the tion to bind to a specific vmknic, remove the
invalid vmknic and leave the option blank. invalid vmknic and leave the option blank.
Warn- esx.problem.net.proxyswitch.port.unavailable| esx.problem.net.proxyswitch.port.unavailable| Informa-
ing Virtual NIC with hardware address {1} failed Virtual NIC with hardware address {1} failed tional
to connect to distributed virtual port {2} on to connect to distributed virtual port {2} on Event
switch {3}. There are no more ports available switch {3}. There are no more ports available
on the host proxy switch. on the host proxy switch.
Warn- esx.problem.net.redundancy.degraded|Uplink esx.problem.net.redundancy.degraded|Uplink Informa-
ing redundancy degraded on virtual switch {1}. redundancy degraded on virtual switch {1}. tional
Physical NIC {2} is down. Affected Physical NIC {2} is down. Affected Event
portgroups:{3}. portgroups:{3}.
esx.problem.net.redundancy.lost|Lost uplink Informa-
redundancy on virtual switch {1}. Physical redundancy on virtual switch {1}. Physical tional
NIC {2} is down. Affected portgroups:{3}. NIC {2} is down. Affected portgroups:{3}. Event
 MN002730A01-AD
Appendix E: Alarms and events

Event ID Se- Event/Alarm Message Event/Alarm Description Event

esx.problem.net.uplink.mtu.failed Warn- esx.problem.net.uplink.mtu.failed|VMkernel
ing
esx.problem.net.vmknic.ip.dupli-
cate
esx.problem.net.vmnic.link-
state.down
esx.problem.net.vmnic.watch-
dog.reset
esx.problem.scsi.device.limi-
treached
esx.problem.scsi.device.thin-
prov.atquota
esx.problem.scsi.scsipath.limi-
treached
esx.problem.storage.connectivi-
ty.devicepor
esx.problem.storage.connectivi-
ty.lost
verity Catego-
ry
esx.problem.net.uplink.mtu.failed|VMkernel Informa-
failed to set the MTU value {1} on the uplink failed to set the MTU value {1} on the uplink tional
{2}. {2}. Event
Warn- esx.problem.net.vmknic.ip.duplicate|A dupli- esx.problem.net.vmknic.ip.duplicate|A dupli- Informa-
ing cate IP address was detected for {1} on the cate IP address was detected for {1} on the tional
interface {2}. The current owner is {3}. interface {2}. The current owner is {3}. Event
Warn- esx.problem.net.vmnic.linkstate.down|Physi- esx.problem.net.vmnic.linkstate.down|Physi- Informa-
ing cal NIC {1} linkstate is down. cal NIC {1} linkstate is down. tional
Event
Warn- esx.problem.net.vmnic.watchdog.reset|Uplink esx.problem.net.vmnic.watchdog.reset|Uplink Informa-
ing {1} has recovered from a transient failure due {1} has recovered from a transient failure due tional
to watchdog timeout to watchdog timeout Event
Critical esx.problem.scsi.device.limitreached|The esx.problem.scsi.device.limitreached|The Informa-
maximum number of supported devices of {1} maximum number of supported devices of {1} tional
has been reached. A device from plugin {2} has been reached. A device from plugin {2} Event
could not be created. could not be created.
Warn- esx.problem.scsi.device.thinprov.atquota| esx.problem.scsi.device.thinprov.atquota| Informa-
ing Space utilization on thin-provisioned device Space utilization on thin-provisioned device tional
{1} exceeded configured threshold. Affected {1} exceeded configured threshold. Affected Event
datastores (if any): {2}. datastores (if any): {2}.
Critical esx.problem.scsi.scsipath.limitreached|The esx.problem.scsi.scsipath.limitreached|The Informa-
maximum number of supported paths of {1} maximum number of supported paths of {1} tional
has been reached. Path {2} could not be add- has been reached. Path {2} could not be add- Event
ed. ed.
Warn- esx.problem.storage.connectivity.devicepor| esx.problem.storage.connectivity.devicepor| Informa-
ing Frequent PowerOn Reset Unit Attentions are Frequent PowerOn Reset Unit Attentions are tional
occurring on device {1}. This might indicate a occurring on device {1}. This might indicate a Event
storage problem. Affected datastores: {2}1 storage problem. Affected datastores: {2}1
Critical esx.problem.storage.connectivity.lost|Lost esx.problem.storage.connectivity.lost|Lost Informa-
connectivity to storage device {1}. Path {2} is connectivity to storage device {1}. Path {2} is tional
down. Affected datastores: {3}. down. Affected datastores: {3}. Event

199
MN002730A01-AD
Appendix E: Alarms and events

Event ID Se- Event/Alarm Message Event/Alarm Description Event

verity Catego-
ry
esx.problem.storage.connectivi- Warn- esx.problem.storage.connectivity.pathpor| esx.problem.storage.connectivity.pathpor| Informa-
ty.pathpor ing Frequent PowerOn Reset Unit Attentions are Frequent PowerOn Reset Unit Attentions are tional
occurring on path {1}. This might indicate a occurring on path {1}. This might indicate a Event
storage problem. Affected device: {2}. Affect- storage problem. Affected device: {2}. Affect-
ed datastores: {3} ed datastores: {3}
esx.problem.storage.connectivi- Warn- esx.problem.storage.connectivity.pathstate- esx.problem.storage.connectivity.pathstate- Informa-
ty.pathstatechanges ing changes|Frequent path state changes are oc- changes|Frequent path state changes are oc- tional
curring for path {1}. This might indicate a curring for path {1}. This might indicate a Event
storage problem. Affected device: {2}. Affect- storage problem. Affected device: {2}. Affect-
ed datastores: {3} ed datastores: {3}
esx.problem.storage.redundan- Warn- esx.problem.storage.redundancy.degraded| esx.problem.storage.redundancy.degraded| Informa-
cy.degraded ing Path redundancy to storage device {1} de- Path redundancy to storage device {1} de- tional
graded. Path {2} is down. Affected data- graded. Path {2} is down. Affected data- Event
stores: {3}. stores: {3}.
esx.problem.storage.redundan- Warn- esx.problem.storage.redundancy.lost|Lost esx.problem.storage.redundancy.lost|Lost Informa-
cy.lost ing path redundancy to storage device {1}. Path path redundancy to storage device {1}. Path tional
{2} is down. Affected datastores: {3}. {2} is down. Affected datastores: {3}. Event
esx.problem.vmfs.heartbeat.re- Info esx.problem.vmfs.heartbeat.recovered|Suc- esx.problem.vmfs.heartbeat.recovered|Suc- Informa-
covered cessfully restored access to volume {1} ({2}) cessfully restored access to volume {1} ({2}) tional
following connectivity issues. following connectivity issues. Event
esx.problem.vmfs.heart- Info esx.problem.vmfs.heartbeat.timedout|Lost esx.problem.vmfs.heartbeat.timedout|Lost Informa-
beat.timedout access to volume {1} ({2}) due to connectivity access to volume {1} ({2}) due to connectivity tional
issues. Recovery attempt is in progress and issues. Recovery attempt is in progress and Event
outcome will be reported shortly. outcome will be reported shortly.
esx.problem.vmfs.heartbeat.unre- Critical esx.problem.vmfs.heartbeat.unrecoverable| esx.problem.vmfs.heartbeat.unrecoverable| Informa-
coverable Lost connectivity to volume {1} ({2}) and sub- Lost connectivity to volume {1} ({2}) and sub- tional
sequent recovery attempts have failed. sequent recovery attempts have failed. Event
esx.problem.vmfs.journal.create- Warn- esx.problem.vmfs.journal.createfailed|No esx.problem.vmfs.journal.createfailed|No Informa-
failed ing space for journal on volume {1} ({2}). Open- space for journal on volume {1} ({2}). Open- tional
ing volume in read-only metadata mode with ing volume in read-only metadata mode with Event
limited write support. limited write support.
esx.problem.vmfs.lock.corrupton- Critical esx.problem.vmfs.lock.corruptondisk|At least esx.problem.vmfs.lock.corruptondisk|At least Informa-
disk one corrupt on-disk lock was detected on vol- one corrupt on-disk lock was detected on vol- tional
Event

200

Event ID
esx.problem.vmfs.nfs.mount.con- Critical esx.problem.vmfs.nfs.mount.connect.failed| esx.problem.vmfs.nfs.mount.connect.failed| Informa-
nect.failed
esx.problem.vmfs.nfs.mount.lim-
it.exceeded
esx.problem.vmfs.nfs.server.dis-
connect
esx.problem.vmfs.nfs.server.re-
stored
esx.problem.vmfs.resource.cor-
ruptondisk
esx.problem.vmfs.volume.locked Critical esx.problem.vmfs.volume.locked|Volume on
ExitedStandbyModeEvent
ExitingStandbyModeEvent
ExitMaintenanceModeEvent
MN002730A01-AD
Appendix E: Alarms and events
Se- Event/Alarm Message Event/Alarm Description Event
verity Catego-
ry
ume {1} ({2}). Other regions of the volume ume {1} ({2}). Other regions of the volume
might be damaged too. might be damaged too.
Failed to mount to the server {1} mount point Failed to mount to the server {1} mount point tional
{2}. {3} {2}. {3} Event
Critical esx.problem.vmfs.nfs.mount.limit.exceeded| esx.problem.vmfs.nfs.mount.limit.exceeded| Informa-
Failed to mount to the server {1} mount point Failed to mount to the server {1} mount point tional
{2}. {3} {2}. {3} Event
Critical esx.problem.vmfs.nfs.server.disconnect|Lost esx.problem.vmfs.nfs.server.disconnect|Lost Informa-
connection to server {1} mount point {2} connection to server {1} mount point {2} tional
mounted as {3} ({4}). mounted as {3} ({4}). Event
Info esx.problem.vmfs.nfs.server.restored|Re- esx.problem.vmfs.nfs.server.restored|Re- Informa-
stored connection to server {1} mount point stored connection to server {1} mount point tional
{2} mounted as {3} ({4}). {2} mounted as {3} ({4}). Event
Critical esx.problem.vmfs.resource.corruptondisk|At esx.problem.vmfs.resource.corruptondisk|At Informa-
least one corrupt resource metadata region least one corrupt resource metadata region tional
was detected on volume {1} ({2}). Other re- was detected on volume {1} ({2}). Other re- Event
gions of the volume might be damaged too. gions of the volume might be damaged too.
esx.problem.vmfs.volume.locked|Volume on Informa-
device {1} locked, possibly because remote device {1} locked, possibly because remote tional
host {2} encountered an error during a vol- host {2} encountered an error during a vol- Event
ume operation and could not recover. ume operation and could not recover.
Info The host {host.name} is no longer in standby The host {host.name} is no longer in standby Informa-
mode mode tional
Event
Info The host {host.name} is exiting standby The host {host.name} is exiting standby Informa-
mode mode tional
Event
Info Host {host.name} in {datacenter.name} has Host {host.name} in {datacenter.name} has Informa-
exited maintenance mode exited maintenance mode tional
Event
201
MN002730A01-AD
Appendix E: Alarms and events
Event ID
ExitStandbyModeFailedEvent
FailoverLevelRestored
GeneralHostErrorEvent
GeneralHostInfoEvent
GeneralHostWarningEvent
GeneralVmErrorEvent
GeneralVmInfoEvent
GeneralVmWarningEvent
hbr.primary.AppQuiescedDelta-
CompletedEvent
hbr.primary.DeltaAbortedEvent
202
Se- Event/Alarm Message Event/Alarm Description Event
verity Catego-
ry
Critical The host {host.name} could not exit standby The host {host.name} could not exit standby Informa-
mode mode tional
Event
Info Sufficient resources are available to satisfy Sufficient resources are available to satisfy Informa-
HA failover level in cluster {computeRe- HA failover level in cluster {computeRe- tional
source.name} in {datacenter.name} source.name} in {datacenter.name} Event
Critical Error detected on {host.name} in {datacen- Error detected on {host.name} in {datacen- Informa-
ter.name}: {message} ter.name}: {message} tional
Event
Info Issue detected on {host.name} in {datacen- Issue detected on {host.name} in {datacen- Informa-
ter.name}: {message} ter.name}: {message} tional
Event
Warn- Issue detected on {host.name} in {datacen- Issue detected on {host.name} in {datacen- Informa-
ing ter.name}: {message} ter.name}: {message} tional
Event
Critical Error detected for {vm.name} on {host.name} Error detected for {vm.name} on {host.name} Informa-
in {datacenter.name}: {message} in {datacenter.name}: {message} tional
Event
Info Issue detected for {vm.name} on {host.name} Issue detected for {vm.name} on {host.name} Informa-
in {datacenter.name}: {message} in {datacenter.name}: {message} tional
Event
Warn- Issue detected for {vm.name} on {host.name} Issue detected for {vm.name} on {host.name} Informa-
ing in {datacenter.name}: {message} in {datacenter.name}: {message} tional
Event
Info hbr.primary.AppQuiescedDeltaCompletedE- hbr.primary.AppQuiescedDeltaCompletedE- Informa-
vent|Application consistent delta completed vent|Application consistent delta completed tional
for virtual machine {vm.name} on host for virtual machine {vm.name} on host Event
{host.name} in cluster {computeRe- {host.name} in cluster {computeRe-
source.name} in {datacenter.name} ({bytes} source.name} in {datacenter.name} ({bytes}
bytes transferred) bytes transferred)
Warn- hbr.primary.DeltaAbortedEvent|Delta aborted hbr.primary.DeltaAbortedEvent|Delta aborted Informa-
ing for virtual machine {vm.name} on host for virtual machine {vm.name} on host tional
{host.name} in cluster {computeRe- {host.name} in cluster {computeRe- Event
 MN002730A01-AD
Appendix E: Alarms and events

Event ID Se- Event/Alarm Message Event/Alarm Description Event

hbr.primary.DeltaCompletedE-
vent
hbr.primary.FailedToStartDeltaE- Critical hbr.primary.FailedToStartDeltaEvent|Failed
vent
hbr.primary.FailedToStartSyncE- Critical hbr.primary.FailedToStartSyncEvent|Failed to
vent
hbr.primary.FSQuiescedDelta-
CompletedEvent
hbr.primary.InvalidDiskReplica-
tionConfigurationEvent
verity Catego-
ry
source.name} in {datacenter.name}: {rea- source.name} in {datacenter.name}: {rea-
son.@enum.hbr.primary.ReasonForDeltaA- son.@enum.hbr.primary.ReasonForDeltaA-
bort} bort}
Info hbr.primary.DeltaCompletedEvent|Delta com- hbr.primary.DeltaCompletedEvent|Delta com- Informa-
pleted for virtual machine {vm.name} on host pleted for virtual machine {vm.name} on host tional
{host.name} in cluster {computeRe- {host.name} in cluster {computeRe- Event
source.name} in {datacenter.name} ({bytes} source.name} in {datacenter.name} ({bytes}
bytes transferred). bytes transferred).
hbr.primary.FailedToStartDeltaEvent|Failed Informa-
to start delta for virtual machine {vm.name} to start delta for virtual machine {vm.name} tional
on host {host.name} in cluster {computeRe- on host {host.name} in cluster {computeRe- Event
source.name} in {datacenter.name}: {rea- source.name} in {datacenter.name}: {rea-
son.@enum.fault.ReplicationVmFault.Rea- son.@enum.fault.ReplicationVmFault.Rea-
sonForFault} sonForFault}
hbr.primary.FailedToStartSyncEvent|Failed to Informa-
start full sync for virtual machine {vm.name} start full sync for virtual machine {vm.name} tional
on host {host.name} in cluster {computeRe- on host {host.name} in cluster {computeRe- Event
source.name} in {datacenter.name}: {rea- source.name} in {datacenter.name}: {rea-
son.@enum.fault.ReplicationVmFault.Rea- son.@enum.fault.ReplicationVmFault.Rea-
sonForFault} sonForFault}
Warn- hbr.primary.FSQuiescedDeltaCompletedE- hbr.primary.FSQuiescedDeltaCompletedE- Informa-
ing vent|File system consistent delta completed vent|File system consistent delta completed tional
for virtual machine {vm.name} on host for virtual machine {vm.name} on host Event
{host.name} in cluster {computeRe- {host.name} in cluster {computeRe-
source.name} in {datacenter.name} ({bytes} source.name} in {datacenter.name} ({bytes}
bytes transferred) bytes transferred)
Warn- hbr.primary.InvalidDiskReplicationConfigura- hbr.primary.InvalidDiskReplicationConfigura- Informa-
ing tionEvent|Replication configuration is invalid tionEvent|Replication configuration is invalid tional
for virtual machine {vm.name} on host for virtual machine {vm.name} on host Event
{host.name} in cluster {computeRe- {host.name} in cluster {computeRe-
source.name} in {datacenter.name}, disk {dis- source.name} in {datacenter.name}, disk {dis-
kKey}: {reasonForFault.@enum.fault.Replica- kKey}: {reasonForFault.@enum.fault.Replica-
tionDiskConfigFault.ReasonForFault} tionDiskConfigFault.ReasonForFault}

203
MN002730A01-AD
Appendix E: Alarms and events
Event ID Se- Event/Alarm Message
verity
hbr.primary.InvalidVmReplica- Warn- hbr.primary.InvalidVmReplicationConfigura-
tionConfigurationEvent ing tionEvent|Replication configuration is invalid
for virtual machine {vm.name} on host
{host.name} in cluster {computeRe-
source.name} in {datacenter.name}: {reason-
ForFault.@enum.fault.ReplicationVmConfig-
Fault.ReasonForFault}
hbr.primary.NoConnectionToHbr- Warn- hbr.primary.NoConnectionToHbrServerEvent|
ServerEvent ing No connection to replication server for virtual
machine {vm.name} on host {host.name} in
cluster {computeResource.name} in {data-
center.name}: {reason.@enum.hbr.pri-
mary.ReasonForNoServerConnection}
hbr.primary.NoProgressWithHbr- Warn- hbr.primary.NoProgressWithHbrServerEvent|
ServerEvent ing Replication server error for virtual machine
{vm.name} on host {host.name} in cluster
{computeResource.name} in {datacen-
ter.name}: {reason.@enum.hbr.primary.Rea-
sonForNoServerProgress}
hbr.primary.SyncCompletedEvent Info hbr.primary.SyncCompletedEvent|Full sync
completed for virtual machine {vm.name} on
host {host.name} in cluster {computeRe-
source.name} in {datacenter.name} ({bytes}
bytes transferred).
hbr.primary.UnquiescedDelta- Warn- hbr.primary.UnquiescedDeltaCompletedE-
CompletedEvent ing vent|Delta completed for virtual machine
{vm.name} on host {host.name} in cluster
{computeResource.name} in {datacen-
ter.name} ({bytes} bytes transferred).
hbr.primary.VmReplicationConfi- Info hbr.primary.VmReplicationConfiguration-
gurationChangedEvent ChangedEvent|Replication configuration
changed for virtual machine {vm.name} on
host {host.name} in cluster {computeRe-
source.name} in {datacenter.name} ({num-
204
Event/Alarm Description Event
Catego-
ry
hbr.primary.InvalidVmReplicationConfigura- Informa-
tionEvent|Replication configuration is invalid tional
for virtual machine {vm.name} on host Event
{host.name} in cluster {computeRe-
source.name} in {datacenter.name}: {reason-
ForFault.@enum.fault.ReplicationVmConfig-
Fault.ReasonForFault}
hbr.primary.NoConnectionToHbrServerEvent| Informa-
No connection to replication server for virtual tional
machine {vm.name} on host {host.name} in Event
cluster {computeResource.name} in {data-
center.name}: {reason.@enum.hbr.pri-
mary.ReasonForNoServerConnection}
hbr.primary.NoProgressWithHbrServerEvent| Informa-
Replication server error for virtual machine tional
{vm.name} on host {host.name} in cluster Event
{computeResource.name} in {datacen-
ter.name}: {reason.@enum.hbr.primary.Rea-
sonForNoServerProgress}
hbr.primary.SyncCompletedEvent|Full sync Informa-
completed for virtual machine {vm.name} on tional
host {host.name} in cluster {computeRe- Event
source.name} in {datacenter.name} ({bytes}
bytes transferred).
hbr.primary.UnquiescedDeltaCompletedE- Informa-
vent|Delta completed for virtual machine tional
{vm.name} on host {host.name} in cluster Event
{computeResource.name} in {datacen-
ter.name} ({bytes} bytes transferred).
hbr.primary.VmReplicationConfiguration- Informa-
ChangedEvent|Replication configuration tional
changed for virtual machine {vm.name} on Event
host {host.name} in cluster {computeRe-
source.name} in {datacenter.name} ({num-
 MN002730A01-AD
Appendix E: Alarms and events

Event ID Se- Event/Alarm Message Event/Alarm Description Event

verity Catego-
ry
Disks} disks, {rpo} minutes RPO, HBR Server Disks} disks, {rpo} minutes RPO, HBR Server
is {hbrServerAddress}). is {hbrServerAddress}).
HostAddedEvent Info Added host {host.name} to datacenter {data- Added host {host.name} to datacenter {data- Informa-
center.name} center.name} tional
Event
HostAdminDisableEvent Warn- Administrator access to the host {host.name} Administrator access to the host {host.name} Informa-
ing is disabled is disabled tional
Event
HostAdminEnableEvent Warn- Administrator access to the host {host.name} Administrator access to the host {host.name} Informa-
ing has been restored has been restored tional
Event
HostComplianceCheckedEvent Info Host {host.name} checked for compliance. Host {host.name} checked for compliance. Informa-
tional
Event
HostCompliantEvent Info Host {host.name} is in compliance with the Host {host.name} is in compliance with the Informa-
attached profile attached profile tional
Event
HostConfigAppliedEvent Info Host configuration changes applied. Host configuration changes applied. Informa-
tional
Event
HostDasDisabledEvent Info HA agent disabled on {host.name} in cluster HA agent disabled on {host.name} in cluster Informa-
{computeResource.name} in {datacen- {computeResource.name} in {datacen- tional
ter.name} ter.name} Event
HostDasDisablingEvent Info HA is being disabled on {host.name} in clus- HA is being disabled on {host.name} in clus- Informa-
ter {computeResource.name} in datacenter ter {computeResource.name} in datacenter tional
{datacenter.name} {datacenter.name} Event
HostDasEnabledEvent Info HA agent enabled on {host.name} in cluster HA agent enabled on {host.name} in cluster Informa-
{computeResource.name} in {datacen- {computeResource.name} in {datacen- tional
ter.name} ter.name} Event
HostDasEnablingEvent Warn- Enabling HA agent on {host.name} in cluster Enabling HA agent on {host.name} in cluster Informa-
ing {computeResource.name} in {datacen- {computeResource.name} in {datacen- tional
ter.name} ter.name} Event

205
MN002730A01-AD
Appendix E: Alarms and events
Event ID
HostDasErrorEvent
HostDasOkEvent
HostDisconnectedEvent
HostDVPortEvent
HostEnableAdminFailedEvent
HostExtraNetworksEvent
HostGetShortNameFailedEvent
HostInventoryFullEvent
HostInventoryUnreadableEvent
HostIpChangedEvent
206
Se- Event/Alarm Message Event/Alarm Description Event
verity Catego-
ry
Critical HA agent on {host.name} in cluster {comput- HA agent on {host.name} in cluster {comput- Informa-
eResource.name} in {datacenter.name} has eResource.name} in {datacenter.name} has tional
an error {message}: {reason.@enum.HostDa- an error {message}: {reason.@enum.HostDa- Event
sErrorEvent.HostDasErrorReason} sErrorEvent.HostDasErrorReason}
Info HA agent on host {host.name} in cluster HA agent on host {host.name} in cluster Informa-
{computeResource.name} in {datacen- {computeResource.name} in {datacen- tional
ter.name} is configured correctly ter.name} is configured correctly Event
Warn- Disconnected from {host.name} in {datacen- Disconnected from {host.name} in {datacen- Informa-
ing ter.name}. Reason: {reason.@enum.HostDis- ter.name}. Reason: {reason.@enum.HostDis- tional
connectedEvent.ReasonCode} connectedEvent.ReasonCode} Event
Info dvPort connected to host {host.name} in {da- dvPort connected to host {host.name} in {da- Informa-
tacenter.name} changed status tacenter.name} changed status tional
Event
Critical Cannot restore some administrator permis- Cannot restore some administrator permis- Informa-
sions to the host {host.name} sions to the host {host.name} tional
Event
Critical Host {host.name} has the following extra net- Host {host.name} has the following extra net- Informa-
works not used by other hosts for HA com- works not used by other hosts for HA com- tional
munication:{ips}. Consider using HA ad- munication:{ips}. Consider using HA ad- Event
vanced option das.allowNetwork to control vanced option das.allowNetwork to control
network usage network usage
Critical Cannot complete command 'hostname -s' on Cannot complete command 'hostname -s' on Informa-
host {host.name} or returned incorrect name host {host.name} or returned incorrect name tional
format format Event
Warn- Maximum ({capacity}) number of hosts al- Maximum ({capacity}) number of hosts al- Informa-
ing lowed for this edition of vCenter Server has lowed for this edition of vCenter Server has tional
been reached been reached Event
Info The virtual machine inventory file on host The virtual machine inventory file on host Informa-
{host.name} is damaged or unreadable. {host.name} is damaged or unreadable. tional
Event
Info IP address of the host {host.name} changed IP address of the host {host.name} changed Informa-
from {oldIP} to {newIP} from {oldIP} to {newIP} tional
Event

Event ID
HostIpInconsistentEvent
HostIpToShortNameFailedEvent
HostIsolationIpPingFailedEvent
HostMissingNetworksEvent
HostMonitoringStateChangedE-
vent
HostNoAvailableNetworksEvent
HostNoHAEnabledPortGroupsE- Critical Host {host.name} has no port groups enabled Host {host.name} has no port groups enabled Informa-
vent
HostNonCompliantEvent
HostNoRedundantManagement-
NetworkEvent
HostNotInClusterEvent
MN002730A01-AD
Appendix E: Alarms and events
Se- Event/Alarm Message Event/Alarm Description Event
verity Catego-
ry
Warn- Configuration of host IP address is inconsis- Configuration of host IP address is inconsis- Informa-
ing tent on host {host.name}: address resolved to tent on host {host.name}: address resolved to tional
{ipAddress} and {ipAddress2} {ipAddress} and {ipAddress2} Event
Warn- Cannot resolve IP address to short name on Cannot resolve IP address to short name on Informa-
ing host {host.name} host {host.name} tional
Event
Warn- Host {host.name} could not reach isolation Host {host.name} could not reach isolation Informa-
ing address: {isolationIp} address: {isolationIp} tional
Event
Critical Host {host.name} does not have the following Host {host.name} does not have the following Informa-
networks used by other hosts for HA commu- networks used by other hosts for HA commu- tional
nication:{ips}. Consider using HA advanced nication:{ips}. Consider using HA advanced Event
option das.allowNetwork to control network option das.allowNetwork to control network
usage usage
Info Host monitoring state in {computeRe- Host monitoring state in {computeRe- Informa-
source.name} in {datacenter.name} changed source.name} in {datacenter.name} changed tional
to {state} to {state} Event
Critical Host {host.name} currently has no available Host {host.name} currently has no available Informa-
networks for HA Communication. The follow- networks for HA Communication. The follow- tional
ing networks are currently used by HA: {ips} ing networks are currently used by HA: {ips} Event
for HA communication. for HA communication. tional
Event
Warn- Host {host.name} is not in compliance with Host {host.name} is not in compliance with Informa-
ing the attached profile the attached profile tional
Event
Warn- Host {host.name} currently has no manage- Host {host.name} currently has no manage- Informa-
ing ment network redundancy ment network redundancy tional
Event
Critical Host {host.name} is not a cluster member in Host {host.name} is not a cluster member in Informa-
{datacenter.name} {datacenter.name} tional
Event
207
MN002730A01-AD
Appendix E: Alarms and events
Event ID
HostOvercommittedEvent
HostPrimaryAgentNotShortNa-
meEvent
HostProfileAppliedEvent
HostRemovedEvent
HostShortNameInconsistentE-
vent
HostShortNameToIpFailedEvent
HostShutdownEvent
HostStatusChangedEvent
HostSyncFailedEvent
HostUpgradeFailedEvent
208
Se- Event/Alarm Message Event/Alarm Description Event
verity Catego-
ry
Critical Insufficient capacity in host {computeRe- Insufficient capacity in host {computeRe- Informa-
source.name} to satisfy resource configura- source.name} to satisfy resource configura- tional
tion in {datacenter.name} tion in {datacenter.name} Event
Critical Primary agent {primaryAgent} was not speci- Primary agent {primaryAgent} was not speci- Informa-
fied as a short name to host {host.name} fied as a short name to host {host.name} tional
Event
Info Profile is applied on the host {host.name} Profile is applied on the host {host.name} Informa-
tional
Event
Info Removed host {host.name} in {datacen- Removed host {host.name} in {datacen- Informa-
ter.name} ter.name} tional
Event
Warn- Host names {shortName} and {shortName2} Host names {shortName} and {shortName2} Informa-
ing both resolved to the same IP address. Check both resolved to the same IP address. Check tional
the host's network configuration and DNS en- the host's network configuration and DNS en- Event
tries tries
Warn- Cannot resolve short name {shortName} to IP Cannot resolve short name {shortName} to IP Informa-
ing address on host {host.name} address on host {host.name} tional
Event
Info Shut down of {host.name} in {datacen- Shut down of {host.name} in {datacen- Informa-
ter.name}: {reason} ter.name}: {reason} tional
Event
Info Configuration status on host {computeRe- Configuration status on host {computeRe- Informa-
source.name} changed from {oldSta- source.name} changed from {oldSta- tional
tus.@enum.ManagedEntity.Status} to {newS- tus.@enum.ManagedEntity.Status} to {newS- Event
tatus.@enum.ManagedEntity.Status} in {da- tatus.@enum.ManagedEntity.Status} in {da-
tacenter.name} tacenter.name}
Critical Cannot synchronize host {host.name}. {rea- Cannot synchronize host {host.name}. {rea- Informa-
son.msg} son.msg} tional
Event
Critical Cannot install or upgrade vCenter agent Cannot install or upgrade vCenter agent Informa-
service on {host.name} in {datacenter.name} service on {host.name} in {datacenter.name} tional
Event

Event ID
HostUserWorldSwapNotEnable-
dEvent
HostVnicConnectedToCustomi-
zedDVPortEvent
HostWwnChangedEvent
HostWwnConflictEvent
IncorrectHostInformationEvent
InsufficientFailoverResourcesE-
vent
LocalTSMEnabledEvent
MigrationErrorEvent
MigrationHostErrorEvent
MigrationHostWarningEvent
MN002730A01-AD
Appendix E: Alarms and events
Se- Event/Alarm Message Event/Alarm Description Event
verity Catego-
ry
Warn- event.HostUserWorldSwapNotEnabledE- event.HostUserWorldSwapNotEnabledE- Informa-
ing vent.fullFormat vent.fullFormat tional
Event
Info Host {host.name} vNIC {vnic.vnic} was recon- Host {host.name} vNIC {vnic.vnic} was recon- Informa-
figured to use dvPort {vnic.port.portKey} with figured to use dvPort {vnic.port.portKey} with tional
port level configuration, which might be differ- port level configuration, which might be differ- Event
ent from the dvPort group. ent from the dvPort group.
Warn- WWNs are changed for {host.name} WWNs are changed for {host.name} Informa-
ing tional
Event
Critical The WWN ({wwn}) of {host.name} conflicts The WWN ({wwn}) of {host.name} conflicts Informa-
with the currently registered WWN with the currently registered WWN tional
Event
Critical Host {host.name} did not provide the informa- Host {host.name} did not provide the informa- Informa-
tion needed to acquire the correct set of li- tion needed to acquire the correct set of li- tional
censes censes Event
Warn- Insufficient resources to satisfy HA failover Insufficient resources to satisfy HA failover Informa-
ing level on cluster {computeResource.name} in level on cluster {computeResource.name} in tional
{datacenter.name} {datacenter.name} Event
Info The Local Tech Support Mode for the host The Local Tech Support Mode for the host Informa-
{host.name} has been enabled {host.name} has been enabled tional
Event
Critical Unable to migrate {vm.name} from Unable to migrate {vm.name} from Informa-
{host.name} in {datacenter.name}: {fault.msg} {host.name} in {datacenter.name}: {fault.msg} tional
Event
Critical Unable to migrate {vm.name} from Unable to migrate {vm.name} from Informa-
{host.name} to {dstHost.name} in {datacen- {host.name} to {dstHost.name} in {datacen- tional
ter.name}: {fault.msg} ter.name}: {fault.msg} Event
Warn- Migration of {vm.name} from {host.name} to Migration of {vm.name} from {host.name} to Informa-
ing {dstHost.name} in {datacenter.name}: {dstHost.name} in {datacenter.name}: tional
{fault.msg} {fault.msg} Event
209
MN002730A01-AD
Appendix E: Alarms and events

Event ID Se- Event/Alarm Message Event/Alarm Description Event

verity Catego-
ry
MigrationResourceErrorEvent Critical Cannot migrate {vm.name} from {host.name} Cannot migrate {vm.name} from {host.name} Informa-
to {dstHost.name} and resource pool to {dstHost.name} and resource pool tional
{dstPool.name} in {datacenter.name}: {dstPool.name} in {datacenter.name}: Event
{fault.msg} {fault.msg}
MigrationResourceWarningEvent Warn- Migration of {vm.name} from {host.name} to Migration of {vm.name} from {host.name} to Informa-
ing {dstHost.name} and resource pool {dstHost.name} and resource pool tional
{dstPool.name} in {datacenter.name}: {dstPool.name} in {datacenter.name}: Event
{fault.msg} {fault.msg}
MigrationWarningEvent Warn- Migration of {vm.name} from {host.name} in Migration of {vm.name} from {host.name} in Informa-
ing {datacenter.name}: {fault.msg} {datacenter.name}: {fault.msg} tional
Event
NoMaintenanceModeDrsRecom- Info Unable to automatically migrate {vm.name} Unable to automatically migrate {vm.name} Informa-
mendationForVM from {host.name} from {host.name} tional
Event
NotEnoughResourcesToStartV- Info Not enough resources to failover {vm.name} Not enough resources to failover {vm.name} Informa-
mEvent in {computeResource.name} in {datacen- in {computeResource.name} in {datacen- tional
ter.name} ter.name} Event
OutOfSyncDvsHost Warn- The Distributed Virtual Switch configuration The Distributed Virtual Switch configuration Informa-
ing on some hosts differed from that of the vCen- on some hosts differed from that of the vCen- tional
ter Server. ter Server. Event
RemoteTSMEnabledEvent Info Remote Tech Support Mode (SSH) for the Remote Tech Support Mode (SSH) for the Informa-
host {host.name} has been enabled host {host.name} has been enabled tional
Event
ResourcePoolMovedEvent Info Moved resource pool {resourcePool.name} Moved resource pool {resourcePool.name} Informa-
from {oldParent.name} to {newParent.name} from {oldParent.name} to {newParent.name} tional
on {computeResource.name} in {datacen- on {computeResource.name} in {datacen- Event
ter.name} ter.name}
ResourcePoolReconfiguredEvent Critical Updated configuration for {resource- Updated configuration for {resource- Informa-
Pool.name} in compute-resource {computeR- Pool.name} in compute-resource {computeR- tional
esource.name} in {datacenter.name} esource.name} in {datacenter.name} Event
ResourceViolatedEvent Critical Resource usage exceeds configuration for Resource usage exceeds configuration for Informa-
resource pool {resourcePool.name} in com- resource pool {resourcePool.name} in com- tional
Event

210
 MN002730A01-AD
Appendix E: Alarms and events

Event ID Se- Event/Alarm Message Event/Alarm Description Event

verity Catego-
ry
pute-resource {computeResource.name} in pute-resource {computeResource.name} in
{datacenter.name} {datacenter.name}
UnlicensedVirtualMachinesEvent Info There are {unlicensed} unlicensed virtual ma- There are {unlicensed} unlicensed virtual ma- Informa-
chines on host {host} - there are only {availa- chines on host {host} - there are only {availa- tional
ble} licenses available ble} licenses available Event
UnlicensedVirtualMachinesFoun- Info {unlicensed} unlicensed virtual machines {unlicensed} unlicensed virtual machines Informa-
dEvent found on host {host} found on host {host} tional
Event
UpdatedAgentBeingRestartedE- Info The agent on host {host.name} is updated The agent on host {host.name} is updated Informa-
vent and will soon restart and will soon restart tional
Event
VimAccountPasswordChangedE- Info VIM account password was changed on host VIM account password was changed on host Informa-
vent {host.name} {host.name} tional
Event
VmAcquiredMksTicketEvent Info Remote console to {vm.name} on Remote console to {vm.name} on Informa-
{host.name} in {datacenter.name} has been {host.name} in {datacenter.name} has been tional
opened opened Event
VmAcquiredTicketEvent Info A ticket for {vm.name} of type {ticketType} on A ticket for {vm.name} of type {ticketType} on Informa-
{host.name} in {datacenter.name} has been {host.name} in {datacenter.name} has been tional
acquired acquired Event
VmAutoRenameEvent Info Invalid name for {vm.name} on {host.name} Invalid name for {vm.name} on {host.name} Informa-
in {datacenter.name}. Renamed from {old- in {datacenter.name}. Renamed from {old- tional
Name} to {newName} Name} to {newName} Event
VmBeingClonedNoFolderEvent Info Cloning {vm.name} on host {host.name} in Cloning {vm.name} on host {host.name} in Informa-
{datacenter.name} to {destName} on host {datacenter.name} to {destName} on host tional
{destHost.name} {destHost.name} Event
VmBeingCreatedEvent Info Creating {vm.name} on host {host.name} in Creating {vm.name} on host {host.name} in Informa-
{datacenter.name} {datacenter.name} tional
Event
VmBeingDeployedEvent Info Deploying {vm.name} on host {host.name} in Deploying {vm.name} on host {host.name} in Informa-
{datacenter.name} from template {srcTem- {datacenter.name} from template {srcTem- tional
plate.name} plate.name} Event

211
MN002730A01-AD
Appendix E: Alarms and events
Event ID
VmBeingHotMigratedEvent
VmBeingMigratedEvent
VmBeingRelocatedEvent
VmConnectedEvent
VmCreatedEvent
VmDasBeingResetEvent
VmDasBeingResetWithScreen-
shotEvent
VmDasResetFailedEvent
VmDasUpdateErrorEvent
VmDateRolledBackEvent
212
Se- Event/Alarm Message Event/Alarm Description Event
verity Catego-
ry
Info Migrating {vm.name} from {host.name} to Migrating {vm.name} from {host.name} to Informa-
{destHost.name} in {datacenter.name} {destHost.name} in {datacenter.name} tional
Event
Info Relocating {vm.name} from {host.name} to Relocating {vm.name} from {host.name} to Informa-
{destHost.name} in {datacenter.name} {destHost.name} in {datacenter.name} tional
Event
Info Relocating {vm.name} in {datacenter.name} Relocating {vm.name} in {datacenter.name} Informa-
from {host.name} to {destHost.name} from {host.name} to {destHost.name} tional
Event
Info Virtual machine {vm.name} is connected Virtual machine {vm.name} is connected Informa-
tional
Event
Info Created virtual machine {vm.name} on Created virtual machine {vm.name} on Informa-
{host.name} in {datacenter.name} {host.name} in {datacenter.name} tional
Event
Warn- {vm.name} on {host.name} in cluster {com- {vm.name} on {host.name} in cluster {com- Informa-
ing puteResource.name} in {datacenter.name} puteResource.name} in {datacenter.name} tional
reset due to a guest OS error reset due to a guest OS error Event
Warn- {vm.name} on {host.name} in cluster {com- {vm.name} on {host.name} in cluster {com- Informa-
ing puteResource.name} in {datacenter.name} puteResource.name} in {datacenter.name} tional
reset due to a guest OS error. Screenshot is reset due to a guest OS error. Screenshot is Event
saved at {screenshotFilePath}. saved at {screenshotFilePath}.
Critical Cannot reset {vm.name} on {host.name} in Cannot reset {vm.name} on {host.name} in Informa-
cluster {computeResource.name} in {data- cluster {computeResource.name} in {data- tional
center.name} due to a guest OS error center.name} due to a guest OS error Event
Critical Unable to update HA agents given the state Unable to update HA agents given the state Informa-
of {vm.name} of {vm.name} tional
Event
Critical Disconnecting all hosts as the date of virtual Disconnecting all hosts as the date of virtual Informa-
machine {vm.name} has been rolled back machine {vm.name} has been rolled back tional
Event
 MN002730A01-AD
Appendix E: Alarms and events

Event ID Se- Event/Alarm Message Event/Alarm Description Event

verity Catego-
ry
VmDisconnectedEvent Info {vm.name} on host {host.name} in {datacen- {vm.name} on host {host.name} in {datacen- Informa-
ter.name} is disconnected ter.name} is disconnected tional
Event
VmDiscoveredEvent Info Discovered {vm.name} on {host.name} in {da- Discovered {vm.name} on {host.name} in {da- Informa-
tacenter.name} tacenter.name} tional
Event
VmDiskFailedEvent Critical Cannot create virtual disk {disk} Cannot create virtual disk {disk} Informa-
tional
Event
VmDVPortEvent Info dvPort connected to VM {vm.name} on dvPort connected to VM {vm.name} on Informa-
{host.name} in {datacenter.name} changed {host.name} in {datacenter.name} changed tional
status status Event
VmEmigratingEvent Info Migrating {vm.name} off host {host.name} in Migrating {vm.name} off host {host.name} in Informa-
{datacenter.name} {datacenter.name} tional
Event
VmEndRecordingEvent Info End a recording session on {vm.name} End a recording session on {vm.name} Informa-
tional
Event
VmEndReplayingEvent Info End a replay session on {vm.name} End a replay session on {vm.name} Informa-
tional
Event
VmEvent Info This is a catch-all event for various VM This is a catch-all event for various VM Informa-
events (the type of event is listed in the events (the type of event is listed in the tional
event). See VMware's documentation for the event). See VMware's documentation for the Event
list of possible events. list of possible events.
VmFailedMigrateEvent Critical Cannot migrate {vm.name} from {host.name} Cannot migrate {vm.name} from {host.name} Informa-
to {destHost.name} in {datacenter.name} to {destHost.name} in {datacenter.name} tional
Event
VmFailedRelayoutEvent Critical Cannot complete relayout {vm.name} on Cannot complete relayout {vm.name} on Informa-
{host.name} in {datacenter.name}: {rea- {host.name} in {datacenter.name}: {rea- tional
son.msg} son.msg} Event

213
MN002730A01-AD
Appendix E: Alarms and events
Event ID
VmFailedRelayoutOnVmfs2Data- Critical Cannot complete relayout for virtual machine Cannot complete relayout for virtual machine Informa-
storeEvent
VmFailedStartingSecondaryE-
vent
VmFailedToPowerOffEvent
VmFailedToPowerOnEvent
VmFailedToRebootGuestEvent
VmFailedToResetEvent
VmFailedToShutdownGuestE-
vent
VmFailedToStandbyGuestEvent
VmFailedToSuspendEvent
VmFailedUpdatingSecondary-
Config
VmFailoverFailed
214
Se- Event/Alarm Message Event/Alarm Description Event
verity Catego-
ry
{vm.name} which has disks on a VMFS2 vol- {vm.name} which has disks on a VMFS2 vol- tional
ume. ume. Event
Critical vCenter cannot start the Secondary VM vCenter cannot start the Secondary VM Informa-
{vm.name}. Reason: {reason.@enum.VmFai- {vm.name}. Reason: {reason.@enum.VmFai- tional
ledStartingSecondaryEvent.FailureReason} ledStartingSecondaryEvent.FailureReason} Event
Critical Cannot power Off {vm.name} on {host.name} Cannot power Off {vm.name} on {host.name} Informa-
in {datacenter.name}: {reason.msg} in {datacenter.name}: {reason.msg} tional
Event
Critical Cannot power On {vm.name} on {host.name} Cannot power On {vm.name} on {host.name} Informa-
in {datacenter.name}. {reason.msg} in {datacenter.name}. {reason.msg} tional
Event
Critical Cannot reboot the guest OS for {vm.name} Cannot reboot the guest OS for {vm.name} Informa-
on {host.name} in {datacenter.name}. {rea- on {host.name} in {datacenter.name}. {rea- tional
son.msg} son.msg} Event
Critical Cannot suspend {vm.name} on {host.name} Cannot suspend {vm.name} on {host.name} Informa-
in {datacenter.name}: {reason.msg} in {datacenter.name}: {reason.msg} tional
Event
Critical {vm.name} cannot shut down the guest OS {vm.name} cannot shut down the guest OS Informa-
on {host.name} in {datacenter.name}: {rea- on {host.name} in {datacenter.name}: {rea- tional
son.msg} son.msg} Event
Critical {vm.name} cannot standby the guest OS on {vm.name} cannot standby the guest OS on Informa-
{host.name} in {datacenter.name}: {rea- {host.name} in {datacenter.name}: {rea- tional
son.msg} son.msg} Event
Critical Cannot suspend {vm.name} on {host.name} Cannot suspend {vm.name} on {host.name} Informa-
in {datacenter.name}: {reason.msg} in {datacenter.name}: {reason.msg} tional
Event
Critical vCenter cannot update the Secondary VM vCenter cannot update the Secondary VM Informa-
{vm.name} configuration {vm.name} configuration tional
Event
Warn- Failover unsuccessful for {vm.name} on Failover unsuccessful for {vm.name} on Informa-
ing {host.name} in cluster {computeRe- {host.name} in cluster {computeRe- tional
source.name} in {datacenter.name} source.name} in {datacenter.name} Event
 MN002730A01-AD
Appendix E: Alarms and events

Event ID Se- Event/Alarm Message Event/Alarm Description Event

verity Catego-
ry
VmFaultToleranceStateChange- Info Fault Tolerance state on {vm.name} changed Fault Tolerance state on {vm.name} changed Informa-
dEvent from {oldState.@enum.VirtualMachine.Fault- from {oldState.@enum.VirtualMachine.Fault- tional
ToleranceState} to {newState.@enum.Vir- ToleranceState} to {newState.@enum.Vir- Event
tualMachine.FaultToleranceState} tualMachine.FaultToleranceState}
VmFaultToleranceTurnedOffE- Info Fault Tolerance protection has been turned Fault Tolerance protection has been turned Informa-
vent off for {vm.name} off for {vm.name} tional
Event
VmFaultToleranceVmTerminate- Critical The Fault Tolerance VM ({vm.name}) has The Fault Tolerance VM ({vm.name}) has Informa-
dEvent been terminated. {reason.@enum.VmFault- been terminated. {reason.@enum.VmFault- tional
ToleranceVmTerminatedEvent.TerminateR- ToleranceVmTerminatedEvent.TerminateR- Event
eason} eason}
VMFSDatastoreCreatedEvent Info Created VMFS datastore {datastore.name} Created VMFS datastore {datastore.name} Informa-
on {host.name} in {datacenter.name} on {host.name} in {datacenter.name} tional
Event
VmGuestRebootEvent Info Guest OS reboot for {vm.name} on Guest OS reboot for {vm.name} on Informa-
{host.name} in {datacenter.name} {host.name} in {datacenter.name} tional
Event
VmGuestShutdownEvent Info Guest OS shut down for {vm.name} on Guest OS shut down for {vm.name} on Informa-
{host.name} in {datacenter.name} {host.name} in {datacenter.name} tional
Event
VmGuestStandbyEvent Info Guest OS standby for {vm.name} on Guest OS standby for {vm.name} on Informa-
{host.name} in {datacenter.name} {host.name} in {datacenter.name} tional
Event
VmHealthMonitoringStateChan- Info VM monitoring state in {computeRe- VM monitoring state in {computeRe- Informa-
gedEvent source.name} in {datacenter.name} changed source.name} in {datacenter.name} changed tional
to {state} to {state} Event
VmInstanceUuidAssignedEvent Info Assign a new instance UUID ({instanceUuid}) Assign a new instance UUID ({instanceUuid}) Informa-
to {vm.name} to {vm.name} tional
Event
VmInstanceUuidChangedEvent Info The instance UUID of {vm.name} has been The instance UUID of {vm.name} has been Informa-
changed from ({oldInstanceUuid}) to ({newIn- changed from ({oldInstanceUuid}) to ({newIn- tional
stanceUuid}) stanceUuid}) Event

215
MN002730A01-AD
Appendix E: Alarms and events
Event ID
VmInstanceUuidConflictEvent
VmMacAssignedEvent
VmMacChangedEvent
VmMacConflictEvent
VmMaxFTRestartCountReached Warn- Reached maximum Secondary VM (with FT
ing
VmMaxRestartCountReached
VmMessageErrorEvent
VmMessageEvent
VmMessageWarningEvent
VmMigratedEvent
216
Se- Event/Alarm Message Event/Alarm Description Event
verity Catego-
ry
Critical The instance UUID ({instanceUuid}) of The instance UUID ({instanceUuid}) of Informa-
{vm.name} conflicts with the instance UUID {vm.name} conflicts with the instance UUID tional
assigned to {conflictedVm.name} assigned to {conflictedVm.name} Event
Info New MAC address ({mac}) assigned to New MAC address ({mac}) assigned to Informa-
adapter {adapter} for {vm.name} adapter {adapter} for {vm.name} tional
Event
Warn- Changed MAC address from {oldMac} to Changed MAC address from {oldMac} to Informa-
ing {newMac} for adapter {adapter} for {newMac} for adapter {adapter} for tional
{vm.name} {vm.name} Event
Critical The MAC address ({mac}) of {vm.name} con- The MAC address ({mac}) of {vm.name} con- Informa-
flicts with MAC assigned to {conflic- flicts with MAC assigned to {conflic- tional
tedVm.name} tedVm.name} Event
Reached maximum Secondary VM (with FT Informa-
turned On) restart count for {vm.name} on turned On) restart count for {vm.name} on tional
{host.name} in cluster {computeRe- {host.name} in cluster {computeRe- Event
source.name} in {datacenter.name}. source.name} in {datacenter.name}.
Warn- Reached maximum VM restart count for Reached maximum VM restart count for Informa-
ing {vm.name} on {host.name} in cluster {com- {vm.name} on {host.name} in cluster {com- tional
puteResource.name} in {datacenter.name}. puteResource.name} in {datacenter.name}. Event
Critical Error message on {vm.name} on {host.name} Error message on {vm.name} on {host.name} Informa-
in {datacenter.name}: {message} in {datacenter.name}: {message} tional
Event
Info Message on {vm.name} on {host.name} in Message on {vm.name} on {host.name} in Informa-
{datacenter.name}: {message} {datacenter.name}: {message} tional
Event
Warn- Warning message on {vm.name} on Warning message on {vm.name} on Informa-
ing {host.name} in {datacenter.name}: {message} {host.name} in {datacenter.name}: {message} tional
Event
Info Migration of virtual machine {vm.name} from Migration of virtual machine {vm.name} from Informa-
{sourceHost.name} to {host.name} completed {sourceHost.name} to {host.name} completed tional
Event
 MN002730A01-AD
Appendix E: Alarms and events

Event ID Se- Event/Alarm Message Event/Alarm Description Event

verity Catego-
ry
VmNoCompatibleHostForSecon- Warn- No compatible host for the Secondary VM No compatible host for the Secondary VM Informa-
daryEvent ing {vm.name} {vm.name} tional
Event
VmNoNetworkAccessEvent Warn- Not all networks for {vm.name} are accessi- Not all networks for {vm.name} are accessi- Informa-
ing ble by {destHost.name} ble by {destHost.name} tional
Event
VmOrphanedEvent Warn- {vm.name} does not exist on {host.name} in {vm.name} does not exist on {host.name} in Informa-
ing {datacenter.name} {datacenter.name} tional
Event
VmPoweredOffEvent Info {vm.name} on {host.name} in {datacen- {vm.name} on {host.name} in {datacen- Informa-
ter.name} is powered off ter.name} is powered off tional
Event
VmPoweredOnEvent Info {vm.name} on {host.name} in {datacen- {vm.name} on {host.name} in {datacen- Informa-
ter.name} is powered on ter.name} is powered on tional
Event
VmPoweringOnWithCustomi- Info Virtual machine {vm.name} powered On with Virtual machine {vm.name} powered On with Informa-
zedDVPortEvent vNICs connected to dvPorts that have a port vNICs connected to dvPorts that have a port tional
level configuration, which might be different level configuration, which might be different Event
from the dvPort group configuration. from the dvPort group configuration.
VmPowerOffOnIsolationEvent Info {vm.name} was powered Off on the isolated {vm.name} was powered Off on the isolated Informa-
host {isolatedHost.name} in cluster {comput- host {isolatedHost.name} in cluster {comput- tional
eResource.name} in {datacenter.name} eResource.name} in {datacenter.name} Event
VmPrimaryFailoverEvent Critical VM ({vm.name}) failed over to {host.name}. VM ({vm.name}) failed over to {host.name}. Informa-
{reason.@enum.VirtualMachine.NeedSecon- {reason.@enum.VirtualMachine.NeedSecon- tional
daryReason} daryReason} Event
VmReconfiguredEvent Info Reconfigured {vm.name} on {host.name} in Reconfigured {vm.name} on {host.name} in Informa-
{datacenter.name} {datacenter.name} tional
Event
VmRegisteredEvent Info Registered {vm.name} on {host.name} in {da- Registered {vm.name} on {host.name} in {da- Informa-
tacenter.name} tacenter.name} tional
Event

217
MN002730A01-AD
Appendix E: Alarms and events

Event ID Se- Event/Alarm Message Event/Alarm Description Event

verity Catego-
ry
VmRelayoutSuccessfulEvent Info Relayout of {vm.name} on {host.name} in Relayout of {vm.name} on {host.name} in Informa-
{datacenter.name} completed {datacenter.name} completed tional
Event
VmRelayoutUpToDateEvent Info {vm.name} on {host.name} in {datacen- {vm.name} on {host.name} in {datacen- Informa-
ter.name} is in the correct format and relay- ter.name} is in the correct format and relay- tional
out is not necessary out is not necessary Event
VmReloadFromPathEvent Info {vm.name} on {host.name} reloaded from {vm.name} on {host.name} reloaded from Informa-
new configuration {configPath} new configuration {configPath} tional
Event
VmReloadFromPathFailedEvent Critical {vm.name} on {host.name} could not be re- {vm.name} on {host.name} could not be re- Informa-
loaded from {configPath} loaded from {configPath} tional
Event
VmRelocatedEvent Info Completed the relocation of the virtual ma- Completed the relocation of the virtual ma- Informa-
chine chine tional
Event
VmRelocateFailedEvent Critical Cannot relocate virtual machine '{vm.name}' Cannot relocate virtual machine '{vm.name}' Informa-
in {datacenter.name} in {datacenter.name} tional
Event
VmRemoteConsoleConnectedE- Info Remote console connected to {vm.name} on Remote console connected to {vm.name} on Informa-
vent host {host.name} host {host.name} tional
Event
VmRemoteConsoleDisconnecte- Info Remote console disconnected from Remote console disconnected from Informa-
dEvent {vm.name} on host {host.name} {vm.name} on host {host.name} tional
Event
VmRemovedEvent Info Removed {vm.name} on {host.name} from Removed {vm.name} on {host.name} from Informa-
{datacenter.name} {datacenter.name} tional
Event
VmRenamedEvent Warn- Renamed {vm.name} from {oldName} to Renamed {vm.name} from {oldName} to Informa-
ing {newName} in {datacenter.name} {newName} in {datacenter.name} tional
Event
VmResettingEvent Info {vm.name} on {host.name} in {datacen- {vm.name} on {host.name} in {datacen- Informa-
ter.name} is reset ter.name} is reset tional
Event

218
 MN002730A01-AD
Appendix E: Alarms and events

Event ID Se- Event/Alarm Message Event/Alarm Description Event

verity Catego-
ry
VmResourcePoolMovedEvent Info Moved {vm.name} from resource pool {old- Moved {vm.name} from resource pool {old- Informa-
Parent.name} to {newParent.name} in {data- Parent.name} to {newParent.name} in {data- tional
center.name} center.name} Event
VmResourceReallocatedEvent Info Changed resource allocation for {vm.name} Changed resource allocation for {vm.name} Informa-
tional
Event
VmRestartedOnAlternateHostE- Info Virtual machine {vm.name} was restarted on Virtual machine {vm.name} was restarted on Informa-
vent {host.name} since {sourceHost.name} failed {host.name} since {sourceHost.name} failed tional
Event
VmResumingEvent Info {vm.name} on {host.name} in {datacen- {vm.name} on {host.name} in {datacen- Informa-
ter.name} is resumed ter.name} is resumed tional
Event
VmSecondaryAddedEvent Info A Secondary VM has been added for A Secondary VM has been added for Informa-
{vm.name} {vm.name} tional
Event
VmSecondaryDisabledBySyste- Critical vCenter disabled Fault Tolerance on VM vCenter disabled Fault Tolerance on VM Informa-
mEvent '{vm.name}' because the Secondary VM '{vm.name}' because the Secondary VM tional
could not be powered On. could not be powered On. Event
VmSecondaryDisabledEvent Info Disabled Secondary VM for {vm.name} Disabled Secondary VM for {vm.name} Informa-
tional
Event
VmSecondaryEnabledEvent Info Enabled Secondary VM for {vm.name} Enabled Secondary VM for {vm.name} Informa-
tional
Event
VmSecondaryStartedEvent Info Started Secondary VM for {vm.name} Started Secondary VM for {vm.name} Informa-
tional
Event
VmShutdownOnIsolationEvent Info {vm.name} was shut down on the isolated {vm.name} was shut down on the isolated Informa-
host {isolatedHost.name} in cluster {comput- host {isolatedHost.name} in cluster {comput- tional
eResource.name} in {datacenter.name}: eResource.name} in {datacenter.name}: Event
{shutdownResult.@enum.VmShutdownOnI- {shutdownResult.@enum.VmShutdownOnI-
solationEvent.Operation} solationEvent.Operation}

219
MN002730A01-AD
Appendix E: Alarms and events

Event ID Se- Event/Alarm Message Event/Alarm Description Event

verity Catego-
ry
VmStartingEvent Info {vm.name} on host {host.name} in {datacen- {vm.name} on host {host.name} in {datacen- Informa-
ter.name} is starting ter.name} is starting tional
Event
VmStartingSecondaryEvent Info Starting Secondary VM for {vm.name} Starting Secondary VM for {vm.name} Informa-
tional
Event
VmStartRecordingEvent Info Start a recording session on {vm.name} Start a recording session on {vm.name} Informa-
tional
Event
VmStartReplayingEvent Info Start a replay session on {vm.name} Start a replay session on {vm.name} Informa-
tional
Event
VmStaticMacConflictEvent Critical The static MAC address ({mac}) of The static MAC address ({mac}) of Informa-
{vm.name} conflicts with MAC assigned to {vm.name} conflicts with MAC assigned to tional
{conflictedVm.name} {conflictedVm.name} Event
VmStoppingEvent Info {vm.name} on {host.name} in {datacen- {vm.name} on {host.name} in {datacen- Informa-
ter.name} is stopping ter.name} is stopping tional
Event
VmSuspendedEvent Info {vm.name} on {host.name} in {datacen- {vm.name} on {host.name} in {datacen- Informa-
ter.name} is suspended ter.name} is suspended tional
Event
VmSuspendingEvent Info {vm.name} on {host.name} in {datacen- {vm.name} on {host.name} in {datacen- Informa-
ter.name} is being suspended ter.name} is being suspended tional
Event
VmTimedoutStartingSecondaryE- Critical Starting the Secondary VM {vm.name} timed Starting the Secondary VM {vm.name} timed Informa-
vent out within {timeout} ms out within {timeout} ms tional
Event
VmUnsupportedStartingEvent Warn- Unsupported guest OS {guestId} for Unsupported guest OS {guestId} for Informa-
ing {vm.name} on {host.name} in {datacen- {vm.name} on {host.name} in {datacen- tional
ter.name} ter.name} Event
VmUpgradeCompleteEvent Info Virtual hardware upgraded to version {ver- Virtual hardware upgraded to version {ver- Informa-
sion} sion} tional
Event

220
 MN002730A01-AD
Appendix E: Alarms and events

Event ID Se- Event/Alarm Message Event/Alarm Description Event

verity Catego-
ry
VmUpgradeFailedEvent Critical Cannot upgrade virtual hardware Cannot upgrade virtual hardware Informa-
tional
Event
VmUpgradingEvent Info Upgrading virtual hardware on {vm.name} in Upgrading virtual hardware on {vm.name} in Informa-
{datacenter.name} to version {version} {datacenter.name} to version {version} tional
Event
VmUuidAssignedEvent Info Assigned new BIOS UUID ({uuid}) to Assigned new BIOS UUID ({uuid}) to Informa-
{vm.name} on {host.name} in {datacen- {vm.name} on {host.name} in {datacen- tional
ter.name} ter.name} Event
VmUuidChangedEvent Warn- Changed BIOS UUID from {oldUuid} to {new- Changed BIOS UUID from {oldUuid} to {new- Informa-
ing Uuid} for {vm.name} on {host.name} in {data- Uuid} for {vm.name} on {host.name} in {data- tional
center.name} center.name} Event
VmUuidConflictEvent Critical BIOS ID ({uuid}) of {vm.name} conflicts with BIOS ID ({uuid}) of {vm.name} conflicts with Informa-
that of {conflictedVm.name} that of {conflictedVm.name} tional
Event
VmWwnAssignedEvent Info New WWNs assigned to {vm.name} New WWNs assigned to {vm.name} Informa-
tional
Event
VmWwnChangedEvent Warn- WWNs are changed for {vm.name} WWNs are changed for {vm.name} Informa-
ing tional
Event
VmWwnConflictEvent Critical The WWN ({wwn}) of {vm.name} conflicts The WWN ({wwn}) of {vm.name} conflicts Informa-
with the currently registered WWN with the currently registered WWN tional
Event
vprob.net.connectivity.lost Critical vprob.net.connectivity.lost|Lost network con- vprob.net.connectivity.lost|Lost network con- Informa-
nectivity on virtual switch {1}. Physical NIC nectivity on virtual switch {1}. Physical NIC tional
{2} is down. Affected portgroups:{3}. {2} is down. Affected portgroups:{3}. Event
vprob.net.redundancy.degraded Warn- vprob.net.redundancy.degraded|Uplink re- vprob.net.redundancy.degraded|Uplink re- Informa-
ing dundancy degraded on virtual switch {1}. dundancy degraded on virtual switch {1}. tional
Physical NIC {2} is down. {3} uplinks still up. Physical NIC {2} is down. {3} uplinks still up. Event
Affected portgroups:{4}. Affected portgroups:{4}.

221
MN002730A01-AD
Appendix E: Alarms and events
Event ID
vprob.net.redundancy.lost
vprob.storage.connectivity.lost
vprob.storage.redundancy.de-
graded
vprob.storage.redundancy.lost
vprob.vmfs.heartbeat.recovered
vprob.vmfs.heartbeat.timedout
vprob.vmfs.heartbeat.unrecover- Critical vprob.vmfs.heartbeat.unrecoverable|Lost
able
vprob.vmfs.journal.createfailed
vprob.vmfs.lock.corruptondisk
222
Se- Event/Alarm Message Event/Alarm Description Event
verity Catego-
ry
Warn- vprob.net.redundancy.lost|Lost uplink redun- vprob.net.redundancy.lost|Lost uplink redun- Informa-
ing dancy on virtual switch {1}. Physical NIC {2} dancy on virtual switch {1}. Physical NIC {2} tional
is down. Affected portgroups:{3}. is down. Affected portgroups:{3}. Event
Critical vprob.storage.connectivity.lost|Lost connec- vprob.storage.connectivity.lost|Lost connec- Informa-
tivity to storage device {1}. Path {2} is down. tivity to storage device {1}. Path {2} is down. tional
Affected datastores: {3}. Affected datastores: {3}. Event
Warn- vprob.storage.redundancy.degraded|Path re- vprob.storage.redundancy.degraded|Path re- Informa-
ing dundancy to storage device {1} degraded. dundancy to storage device {1} degraded. tional
Path {2} is down. {3} remaining active paths. Path {2} is down. {3} remaining active paths. Event
Affected datastores: {4}. Affected datastores: {4}.
Warn- vprob.storage.redundancy.lost|Lost path re- vprob.storage.redundancy.lost|Lost path re- Informa-
ing dundancy to storage device {1}. Path {2} is dundancy to storage device {1}. Path {2} is tional
down. Affected datastores: {3}. down. Affected datastores: {3}. Event
Info vprob.vmfs.heartbeat.recovered|Successfully vprob.vmfs.heartbeat.recovered|Successfully Informa-
restored access to volume {1} ({2}) following restored access to volume {1} ({2}) following tional
connectivity issues. connectivity issues. Event
Warn- vprob.vmfs.heartbeat.timedout|Lost access to vprob.vmfs.heartbeat.timedout|Lost access to Informa-
ing volume {1} ({2}) due to connectivity issues. volume {1} ({2}) due to connectivity issues. tional
Recovery attempt is in progress and outcome Recovery attempt is in progress and outcome Event
will be reported shortly. will be reported shortly.
vprob.vmfs.heartbeat.unrecoverable|Lost Informa-
connectivity to volume {1} ({2}) and subse- connectivity to volume {1} ({2}) and subse- tional
quent recovery attempts have failed. quent recovery attempts have failed. Event
Warn- vprob.vmfs.journal.createfailed|No space for vprob.vmfs.journal.createfailed|No space for Informa-
ing journal on volume {1} ({2}). Opening volume journal on volume {1} ({2}). Opening volume tional
in read-only metadata mode with limited write in read-only metadata mode with limited write Event
support. support.
Critical vprob.vmfs.lock.corruptondisk|At least one vprob.vmfs.lock.corruptondisk|At least one Informa-
corrupt on-disk lock was detected on volume corrupt on-disk lock was detected on volume tional
{1} ({2}). Other regions of the volume may be {1} ({2}). Other regions of the volume may be Event
damaged too. damaged too.
 MN002730A01-AD
Appendix E: Alarms and events

Event ID Se- Event/Alarm Message Event/Alarm Description Event

verity Catego-
ry
vprob.vmfs.nfs.server.disconnect Critical vprob.vmfs.nfs.server.disconnect|Lost con- vprob.vmfs.nfs.server.disconnect|Lost con- Informa-
nection to server {1} mount point {2} mounted nection to server {1} mount point {2} mounted tional
as {3} ({4}). as {3} ({4}). Event
vprob.vmfs.nfs.server.restored Info vprob.vmfs.nfs.server.restored|Restored con- vprob.vmfs.nfs.server.restored|Restored con- Informa-
nection to server {1} mount point {2} mounted nection to server {1} mount point {2} mounted tional
as {3} ({4}). as {3} ({4}). Event
vprob.vmfs.resource.corrupton- Critical vprob.vmfs.resource.corruptondisk|At least vprob.vmfs.resource.corruptondisk|At least Informa-
disk one corrupt resource metadata region was one corrupt resource metadata region was tional
detected on volume {1} ({2}). Other regions of detected on volume {1} ({2}). Other regions of Event
the volume may be damaged too. the volume may be damaged too.

E.5.2
CMSS Alarms and Events
The following entities are covered:

E.5.2.1
Processors
The following table provides information on all possible events generated against the CMSS, with the managed object name of Processors

Event ID Severity Event/Alarm Message Event/Alarm Description Event Category

processors.1 calculated based on agent Sensors count <# of sensors>. <detail in- Sensors count <# of sensors>. <detail in- Equipment Alarm
input formation about sensors> formation about sensors>

E.5.2.2
Power
The following table provides information on all possible events generated against the CMSS, with the managed object name of Power

Event ID Severity Event/Alarm Message Event/Alarm Description Event Category

power.1 calculated based on agent Sensors count <# of sensors>. <detail in- Sensors count <# of sensors>. <detail infor- Equipment Alarm
input formation about sensors> mation about sensors>

223
MN002730A01-AD
Appendix E: Alarms and events

E.5.2.3
Fan
The following table provides information on all possible events generated against the CMSS, with the managed object name of Fan

Event ID Severity Event/Alarm Message Event/Alarm Description Event Category

fan.1 calculated based on agent Sensors count <# of sensors>. <detail in- Sensors count <# of sensors>. <detail infor- Equipment Alarm
input formation about sensors> mation about sensors>

E.5.2.4
Temperature
The following table provides information on all possible events generated against the CMSS, with the managed object name of Temperature

Event ID Severity Event/Alarm Message Event/Alarm Description Event Category

temperature.1 calculated based on agent Sensors count <# of sensors>. <detail Sensors count <# of sensors>. <detail in- Equipment Alarm
input information about sensors> formation about sensors>

E.5.2.5
Storage
The following table provides information on all possible events generated against the CMSS, with the managed object name of Storage

Event ID Severity Event/Alarm Message Event/Alarm Description Event Category

storage.1 calculated based on agent Sensors count <# of sensors>. <detail in- Sensors count <# of sensors>. <detail infor- Equipment Alarm
input formation about sensors> mation about sensors>

E.5.2.6
Port
The following table provides information on all possible events generated against the CMSS, with the managed object name of Port

Event ID Severity Event/Alarm Message Event/Alarm Description Event Category

port.<portid> Clear Port state is UP Port state is UP Equipment Alarm
port.<portid> Critical Port state is DOWN Port state is DOWN Equipment Alarm

224
 MN002730A01-AD
Appendix E: Alarms and events

E.5.2.7
Configuration Issues
The following table provides information on all possible events generated against the CMSS, with the managed object name of Configuration
Issues

Event ID Severity Event/Alarm Message Event/Alarm Description Event Category

esx.config.is- Clear No configuration issues reported No configuration issues reported Equipment Alarm
sues.clear
esx.config.issues.criti- Critical Configuration issues: <detail information Configuration issues: <detail information about Equipment Alarm
cal about configuration issues> configuration issues>

E.5.2.8
Storage Path
The following table provides information on all possible events generated against the CMSS, with the managed object name of Storage Path

Event ID Severity Event/Alarm Message Event/Alarm Description Event Category

esx.storage.path.up Clear Path <path> to storage device <device.id> is Path <path> to storage device <device.id> is Equipment Alarm
up up
esx.storage.path.down Critical Path <path> to storage device <device.id> is Path <path> to storage device <device.id> is Equipment Alarm
down down

E.5.2.9
Storage Paths
The following table provides information on all possible events generated against the CMSS, with the managed object name of Storage Paths

Event ID Severity Event/Alarm Message Event/Alarm Description Event Cate-

gory
esx.stor- Clear Total number of storage paths is <totalPaths- Total number of storage paths is <totalPaths- Equipment
age.paths.num- Number> Number> Alarm
ber.clear
esx.stor- Major Reported number of storage paths is lower than Reported number of storage paths is lower than Equipment
age.paths.num- expected. Current number of storage paths is expected. Current number of storage paths is Alarm
ber.major <currentPathsNumber> (expexted: <totalPaths- <currentPathsNumber> (expexted: <totalPaths-

225
MN002730A01-AD
Appendix E: Alarms and events

Event ID Severity Event/Alarm Message Event/Alarm Description Event Cate-

gory
Number>). Verify storage adapters configuration Number>). Verify storage adapters configuration
and cables state and cables state

E.5.2.10
Virtual machine
The following table provides information on all possible events generated against the VMware vCenter Server, with the managed object name of
Virtual Machine

Event ID Severity Event/Alarm Message Event/Alarm Description Event Category

VmPoweredOffEvent Critical POWERED OFF - ON HOST <host> POWERED OFF - ON HOST <host> Equipment Alarm
VmPoweredOnEvent Clear POWERED ON - ON HOST <host> POWERED ON - ON HOST <host> Equipment Alarm
VmSuspendedEvent Warning SUSPENDED - ON HOST <host> SUSPENDED - ON HOST <host> Equipment Alarm

E.6
MNIS Alarms and Events Overview
Events and alarms are reported for the MNIS as follows:

E.6.1
MNIS Alarms
Alarms are reported for the MNIS as follows:

Event Name Severity Event/Alarm Message Event/Alarm Description Event Category Manager Entity
NcmSynchronizedSta- CommFailure Device {0} is not reported by Device {0} is not reported by Communication NCM Synchronized Sta-
tus the system. the system. Alarm tus

E.6.2
MNIS Events
Events are reported for the MNIS as follows:

226
 MN002730A01-AD
Appendix E: Alarms and events

Event Name Severity Event/Alarm Message Event/Alarm Description Event Category Manager Entity
PropertyChanged Info Property {0} changed from {1} to Property {0} changed from {1} to Informational Event Property Changed
{2}. {2}.
MnisClientConnected Info Data/Voice client connected. Data/Voice client connected. Informational Event Mnis Client Connect-
ed
MnisClientDisconnected Info Data/Voice client disconnected. Data/Voice client disconnected. Informational Event Mnis Client Discon-
nected
DeviceStatus.Inac- Info Current device status: Inactive Current Device Status: Inactive Informational Event Device Status
tive.Disabled (Disabled). (Disabled).
DeviceStatus.Active.Ena- Info Current device status: Active Current device status: Active Informational Event Device Status
bled (Enabled). (Enabled).
DeviceStatus.Inac- Info Current device status: Inactive Current device status: Inactive Informational Event Device Status
tive.Alarm (Alarm). (Alarm).
DeviceStatus.Inac- Info Current device status: Inactive Current device status: Inactive Informational Event Device Status
tive.Locked (Locked). (Locked).
DeviceStatus.Un- Info Current device status: Unknown Current device status: Unknown Informational Event Device Status
known.NotReported (Not Reported). (Not Reported).
DeviceStatus.Unknown Info Current device status: Unknown. Current device status: Unknown. Informational Event Device Status

E.7
Generic SNMP Node Alarms and Events Overview
No entities are defined for Generic SNMP Node.

E.8
Generic SNMP Router Alarms and Events Overview
Events and alarms are reported for the Generic SNMP Router as follows:

E.8.1
Generic SNMP Router Alarms
There are two SNMP traps that are reported to SA as alarms, rather than events. See Generic SNMP Router Alarms table for more information.

227
MN002730A01-AD
Appendix E: Alarms and events

Event ID Severity Event/Alarm Message Event/Alarm Description Event Category

LinkDown Major Port is DOWN Port is DOWN Equipment Alarm
LinkUp Clear Port is UP Port is UP Equipment Alarm

E.9
Generic SNMP Switch Alarms and Events Overview
Events and alarms are reported for the Generic SNMP Switch as follows:

E.9.1
Generic SNMP Switch Alarms
There are two LAN switch SNMP traps that are reported to SA as alarms, rather than events. See Generic SNMP Switch Alarms table for more
information.

Event ID Severity Event/Alarm Message Event/Alarm Description Event Category

LinkDown Major Port is DOWN Port is DOWN Equipment Alarm
LinkUp Clear Port is UP Port is UP Equipment Alarm

E.10
HP Switch Alarms and Events Overview
This section documents the events sent from all HP hardware, received in HP OpenView, and displayed in the Unified Event Manager alarms
window.

E.10.1
HP Switch Main Traps
Use HP Switch Main Traps to determine the HP switch model that is generating event messages.
NOTICE: The actual event messages (noted by <event message> in the table below) are found in HP Switch.

Event ID Severity Event Message Event Category

.1.3.6.1.4.1.11.2.3.7.11.17.0.2 Info HP Procurve 5308xl Trap - <event message> Informational Event
.1.3.6.1.4.1.11.2.3.7.11.19.0.2 Info HP Procurve 2524 Trap - <event message> Informational Event

228
 MN002730A01-AD
Appendix E: Alarms and events

Event ID Severity Event Message Event Category

.1.3.6.1.4.1.11.2.3.7.11.34.0.2 Info
.1.3.6.1.4.1.11.2.3.7.11.45.0.2 Info
.1.3.6.1.4.1.11.2.3.7.11.29.0.2 Info
.1.3.6.1.4.1.11.2.3.7.11.44.0.2 Info
.1.3.6.1.4.1.11.2.3.7.11.59.0.2 Info
.1.3.6.1.4.1.11.2.3.7.11.58.0.2 Info
.1.3.6.1.4.1.11.2.3.7.11.76.0.2 Info
.1.3.6.1.4.1.11.2.3.7.11.77.0.2 Info
.1.3.6.1.4.1.11.2.3.7.11.122.0.2 Info
.1.3.6.1.4.1.11.2.3.7.11.129.0.2 Info
.1.3.6.1.4.1.11.2.3.7.11.132.0.2 Info
.1.3.6.1.4.1.11.2.3.7.11.181.18.0.2 Info
.1.3.6.1.4.1.11.2.3.7.11.181.19.0.2 Info
HP Procurve 2626A Trap - <event message> Informational Event
HP Procurve 2626B Trap - <event message> Informational Event
HP Procurve 2650A Trap - <event message> Informational Event
HP Procurve 2650B Trap - <event message> Informational Event
HP Procurve 3500 Trap - <event message> Informational Event
HP Procurve 3500 Trap - <event message> Informational Event
HP Procurve 2610-24 Trap - <event message> Informational Event
HP Procurve 2610-48 Trap - <event message> Informational Event
HP Networking 3800 Trap - <event message> Informational Event
HP Networking 2620-24 Trap - <event message> Informational Event
HP Networking 2620-48 Trap - <event message> Informational Event
HPE Networking Switch 2930-24 Trap - <event message> Informational Event
HPE Networking Switch 2930-48 Trap - <event message> Informational Event

E.10.2
HP Switch Generic Events
This section documents the events sent from the HP Switch hardware, received in HP OpenView, and displayed in the Unified Event Manager
alarms window.

E.10.2.1
hpicfFaultFinderTrap
The HP Switch generic event messages appear in the following format, with "Unknown Event" always appearing at the beginning of the message:
Unknown Event - <hpicfFaultFinderTrap> <varbindFirst = varbind value> ... <varbindLast = varbind value>
See hpicfFaultFinderTrap Alarm table for more information on the hpicfFaultFinderTrap event with the associated OID: hpicfFaultFinderTrap
1.3.6.1.4.1.11.2.14.12.1.0.5

229
MN002730A01-AD
Appendix E: Alarms and events

Event Message Contains... Event/Alarm Description Severi-

ty
HP Trap - Fault Finder:Log- This notification is sent whenever the Fault Finder creates an entry in the hpicfFfLogTable. Minor
FaultType = $1 LogAction = Variables:
$2 LogSeverity = $3 InfoURL 1 = "The type of fault which was detected on the physical entity indicated by hpicfFfLogPhysEntity."
= $4 LogPhysEntity = $5
2 = "The action, if any, that was taken by the agent when this fault was detected."
3 = "The severity level of the fault. Port disables is always logged as 'critical'. An agent may need to re-
move faults from the fault log in order to reclaim resources. If so, it must remove lower severity faults be-
fore removing higher severity faults. Faults at the same severity level should be removed from oldest to
newest."
4 = "A URL which a management station can use to access additional information about the fault which
triggered the notification in which this object was sent."
5 = "The entPhysicalIndex of the device port or other physical component on which the fault was detected.
On agents which do not implement the Entity MIB, this will contain the ifIndex of the offending port"

hpicfFaultFinderTrap Variables table contains additional information on all variables that the hpicfFaultFinderTrap could display in the event
message:

Variable Variable Message

LogFaultType 1 = badDriver
2 = badXcvr
3 = badCable
4 = tooLongCable
5 = overBandwidth
6 = bcastStorm
7 = partition
8 = misconfiguredSQE
9 = polarityReversal
10 = networkLoop
11 = lossOfLink
12 = portSecurityViolation
13 = backupLinkTransition
14 = meshingFault
15 = fanFault
16 = rpsFault
17 = stuck10MbFault
18 = lossOfStackMember

230
 MN002730A01-AD
Appendix E: Alarms and events

Variable Variable Message

19 = hotSwapReboot
20 = duplexMismatchHDX
21 = duplexMismatchFDX
22 = flowcntlJumbosFault
23 = portSelftestFailure
24 = xcvrUnidentified
25 = xcvrUnsupported
26 = crfNotify
27 = crfThrottled
28 = crfBlocked
29 = xcvrNotYetSupported
30 = xcvrBRevOnly
31 = xcvrNotSupportedOnPort
32 = phyReadFailure
LogAction 1 = none
2 = warn
3 = warnAndDisable
4 = warnAndSpeedReduce
5 = warnAndSpeedReduceAndDisable
LogSeverity 1 = informational
2 = medium
3 = critical
InfoURL A URL which a management station can use to access additional information about the fault which triggered the notification in
which this object was sent.
LogPhysEntity The entPhysicalIndex of the device port or other physical component on which the fault was detected. On agents which do not
implement the Entity MIB, this will contain the ifIndex of the offending port.

E.10.2.2
hpicfSensorTrap
The HP Switch generic event messages appear in the following format, with "Unknown Event" always appearing at the beginning of the message:
Unknown Event - <hpicfSensorTrap> <varbindFirst = varbind value> ... <varbindLast = varbind value>
See hpicfSensorTrap Alarm table for more information on the hpicfSensorTrap event with the associated OID: hpicfSensorTrap
1.3.6.1.4.1.11.2.14.12.1.0.3

231
MN002730A01-AD
Appendix E: Alarms and events

Event Message Contains... Event/Alarm Description Severity

HP Trap - Sensor:Status = $1 An hpicfSensorTrap indicates that there has been a change of state on one of the sensors in this chas- Minor
Description = $2 sis. The hpicfSensorStatus indicates the new status value for the changed sensor.
Variables:
1 = "Actual status indicated by the sensor."
2 = "A textual description of the sensor."

E.10.2.3
hpicfSelfTestTrap
The HP Switch generic event messages appear in the following format, with "Unknown Event" always appearing at the beginning of the message:
Unknown Event - <hpicfSelfTestTrap> <varbindFirst = varbind value> ... <varbindLast = varbind value>
See hpicfSelfTestTrap Alarm table for more information on the hpicfSelfTestTrap event with the associated OID: hpicfSelfTestTrap
1.3.6.1.4.1.11.2.14.12.1.0.4

Event Message Event/Alarm Description Severity

Contains...
HP Trap - Self Test: An hpicfSelfTestTrap indicates that the agent has detected a non-critical failure. The value of the hpicfSelfTestRe- Minor
ResultTest = $1 sultText object describing the failure is sent in the trap. Note that this trap is sent whenever a new failure is detect-
ed. An agent should throttle the generation of consecutive hpicfSelfTestTraps so that there is at least a five-sec-
ond gap between traps of this type. When traps are throttled, they are dropped, not queued for sending at a future
time.
NOTICE: 'Generating' a trap means sending to all configured recipients.

Variables: helpHPSwitchSelfTestTrap.section.p.2

E.10.2.4
hpicfBridgeLoopProtectLoopDetectedNotification
The HP Switch generic event messages appear in the following format, with "Unknown Event" always appearing at the beginning of the message:
Unknown Event - <hpicfBridgeLoopProtectLoopDetectedNotification> <varbindFirst = varbind value> ... <varbindLast = varbind value>
See hpicfBridgeLoopProtectLoopDetectedNotification Alarm table for more information on the hpicfBridgeLoopProtectLoopDetectedNotification
event with the associated OID: hpicfBridgeLoopProtectLoopDetectedNotification 1.3.6.1.4.1.11.2.14.11.5.1.12.1.5.0.1

232
 MN002730A01-AD
Appendix E: Alarms and events

Event Message Contains... Event/Alarm Description Severity

HP Trap - hpicfBridgeLoopProtectLoop-
DetectedNotification: IfIndex = $1 hpicf-
BridgeLoopProtectPortLoopCount = $2
hpicfBridgeLoopProtectPortReceiverAc-
tion = $3
Variables: Informa-
tional
1 = A unique value for each interface, ranging between 1 and the value of ifNumber. The
value for each interface must remain constant from one re-initialization of the entity's net-
work management system to the next.
2 = When the loop protect feature is enabled on the port this object counts the number of
loops detected on the port. When the feature is disabled on the port the value of this object
is set to 0.
3 = Controls the action taken when a Loop protection packet is received on this port. When
set to 'disableTx' the port that transmitted the packet will be disabled. When set to 'noDisa-
ble' the transmitting port will not be disabled.

E.10.2.5
hpicfConnectionRateFilterNotification
The HP Switch generic event messages appear in the following format, with "Unknown Event" always appearing at the beginning of the message:
Unknown Event - <hpicfConnectionRateFilterNotification> <varbindFirst = varbind value> ... <varbindLast = varbind value>
See hpicfConnectionRateFilterNotification Alarm table for more information on the hpicfConnectionRateFilterNotification event with the associated
OID: hpicfConnectionRateFilterNotification 1.3.6.1.4.1.11.2.14.11.5.1.24.0.1

Event Message Contains... Event/Alarm Description Severity

HP Trap - hpicifConnectionRateFilterVlanId = Variables: Informa-
$1 hpicifConnectionRateFilterInetAddress = 1 = This variable uniquely identifies the vlan on which the host was flagged by the con- tional
$2 hpicifConnectionRateFilterInetAddres- nection rate filter.
sType = $3 hpicifConnectionRateFilterMode =
$4 2 = This variable uniquely identifies the IP address of the host flagged by the connec-
tion rate filter.
3 = This variable uniquely identifies the type of IP address of the host flagged by the
connection rate filter.
4 = This variable identifies the mode applied to the host flagged by the connection rate
filter.

E.10.2.6
hpicfIntrusionTrap
The HP Switch generic event messages appear in the following format, with "Unknown Event" always appearing at the beginning of the message:

233
MN002730A01-AD
Appendix E: Alarms and events

Unknown Event - <hpicfIntrusionTrap> <varbindFirst = varbind value> ... <varbindLast = varbind value>
See hpicfIntrusionTrap Alarm table for more information on the hpicfIntrusionTrap event with the associated OID: hpicfIntrusionTrap
1.3.6.1.4.1.11.2.14.12.4.0.1

Event Message Con- Event/Alarm Description Severi-

tains... ty
HP Trap - IntrusionGroup Variables: Minor
= $1 Port = $2 Address = 1 = "This object identifies the group containing the port on which this intrusion occurred."
$3 Type = $4 Training Vi-
olation = $5 2 = "This object identifies the port within the group on which this intrusion occurred. A port number of zero
indicates that this entry is unused and the values for the other variables in this entry are undefined."
3 = "This object contains the source MAC address of the intruder."
4 = "This object identifies the type of violation that occurred: address, training, or both. The hubIntruderTrai-
ningViolation object indicates additional information, if any, on the type of training violation. This object will be
equal to 'none' if this log entry is unused. Note that the values 'training' and 'both' are only valid for 802.12
ports."
5 = "This object indicates the type of training violation. Note that for 802.3 ports, this object will always be
equal to 'noViolation'. This object will be equal to 'noViolation' if this log entry is unused."

E.10.3
HP Switch Alarms
There are two LAN switch SNMP traps that are reported to SA as alarms, rather than events. See HP Switch Alarms table for more information.

Event ID Severity Event/Alarm Message Event/Alarm Description Event Category

LinkDown Critical Port is DOWN Port is DOWN Equipment Alarm
LinkUp Clear Port is UP Port is UP Equipment Alarm

E.10.4
HP Switch Events
Use HP Switch Events for detailed information on events and alarms generated by the HP Switch. The event message is deciphered as follows:
• The first letter (I, C, M, or W) is the severity of the event:
- I: Info
- C: Clear

234
 MN002730A01-AD
Appendix E: Alarms and events

- M: Major
- W: Warning
• <date time> is the date and time that the event was generated.
• <system name> is the system from which the event was generated. For instance, "chassis:" means that the chassis reported an event to SA.
• The message following the colon (:) is the event text that the LAN switch reports to the SA. Use the event message and the Additional Notes
column in the table to determine what actions to take for the event.
NOTICE: Event messages in the table are applicable to all HP Switch models.

Event Message Event/Alarm Description Additional Notes

I <date time> 802.1x: Authentication I <date time> 802.1x: Authentication <id> is a letter-digit identifier (e.g. A1 F3) where the letter represents
failed for support <id>. failed for support <id>. the port module slot and he digit represents the port on the slot
W <date time> ADDRmgr: Unable W <date time> ADDRmgr: Unable
to learn/age MAC address (s), table to learn/age MAC address (s), table
FULL FULL
C <date time> ADDRmgr: Static ad- C <date time> ADDRmgr: Static ad-
dress missing during address dele- dress missing during address dele-
tion attempt. tion attempt.
I <date time> cdp: CDP enabled I <date time> cdp: CDP enabled cdp: CDP enabled This log event informs the user that CDP has been
enabled on the Switch.
I <date time> cdp: CDP disabled I <date time> cdp: CDP disabled cdp: CDP disabled This log event informs the user that CDP has been
disabled on the Switch.
I <date time> chassis: Slot <id> Re- I <date time> chassis: Slot <id> Re- This message appears whenever a card in a slot is removed from an
moved moved operational switch chassis. The <id> in the format will indicate which
slot from which the card was removed.
I <date time> chassis: Slot <id> In- I <date time> chassis: Slot <id> In- This message appears whenever a card in a slot is inserted into a slot
serted serted in an operational system. The <id> in the format will indicate which slot
into which the card was inserted.
M <date time> chassis: Slot <id> M <date time> chassis: Slot <id> This message appears whenever a slot in a switch chassis fails hots-
Hotswap Failure Hotswap Failure wap. The <id> in the format will indicate the failed slot.
W <date time> chassis: Fan <failure W <date time> chassis: Fan <failure This message will appear when the software notices that a fan has
| OK>: Fan: <fan number> Failures: | OK>: Fan: <fan number> Failures: failed or when a ailed fan is no longer failing. The fan state is indicated
<number of failures> <number of failures> as {failure | OK}. The fan is indicated as fan 1 or fan 2. The number of

235
MN002730A01-AD
Appendix E: Alarms and events
Event Message
W <date time> chassis: Power Sup-
ply <failure | OK>: Supply: <Main |
RPS>, Failures: <number of fail-
ures>
W <date time> chassis: Slot <id> In- W <date time> chassis: Slot <id> In- This message will appear when a module has been inserted that is in-
active: Module/Configuration mis-
match
W <date time> chassis: Slot <id>
Selftest Failure or unsupported
module
W <date time> chassis: Port <id>
Selftest Failure
W <date time> chassis: Invalid
transceiver installed in Port <id>
W <date time> chassis: Boot ROM
Selftest failure!
W <date time> chassis: Lost Com-
munication with Slot <id>
I <date time> chassis: Slot <id>
Downloading
I <date time> chassis: Slot <id>
Download Complete
I <date time> chassis: Slot <id>
Download Failed
236
Event/Alarm Description
W <date time> chassis: Power Sup-
ply <failure | OK>: Supply: <Main |
RPS>, Failures: <number of fail-
ures>
active: Module/Configuration mis-
match
W <date time> chassis: Slot <id>
Selftest Failure or unsupported
module
W <date time> chassis: Port <id>
Selftest Failure
W <date time> chassis: Invalid
transceiver installed in Port <id>
W <date time> chassis: Boot ROM
Selftest failure!
W <date time> chassis: Lost Com-
munication with Slot <id>
I <date time> chassis: Slot <id>
Downloading
I <date time> chassis: Slot <id>
Download Complete
I <date time> chassis: Slot <id>
Download Failed
Additional Notes
times the fan has failed will also be indicated. The fan fail LED will also
be lit.
This message will appear when the software notices hat the RPS is
failing or the RPS is present and the main power supply is failing or
when a failed supply is no longer failing. The supply state will be indi-
cated as {failure | OK}. The supply will be indicated as {Main | RPS}.
The message will also indicate the number of times the supply has
failed. The power fail LED will also be lit.
compatible with the previous module in the indicated slot. The <id> in
the format will indicate the slot.
This message will appear when the indicated slot has failed selftest
completely or when there are no usable ports on the slot. The <id> in
the format will indicate the slot.
This message will appear when the indicated port has failed selftest
and is unusable. <id> is a letter-digit identifier (e.g. A1 F3) where the
letter represents the port module slot and the digit represents the port
on the slot.
This message will appear when the indicated port has an invalid trans-
ceiver installed. <id> is a letter-digit identifier (e.g. A1 F3) where the
letter represents the port module slot and the digit represents the port
on the slot.
This message will appear when the indicated port has an invalid trans-
ceiver installed.
This message will appear when the backplane fails to receive a heart-
beat response from a particular module. The <id> in the format will in-
dicate the slot.
This message will appear when chassis manager begins downloading
a new card. The <id> in the format will indicate the slot.
This message will appear when chassis manager finishes downloading
a new card. The <id> in the format will indicate the slot.
This message will appear if chassis manager fils to download a new
card. The <id> in the format will indicate the slot.

Event Message
I <date time> chassis: Slot <id>
Ready
W <date time> chassis: Unable to
Download to Slot <id>. Please Re-
move Card
W <date time> chassis: Module in
Slot <id> not Supported or may be
Faulty
W <date time> chassis: Backplane
link to slot <id> failed selftest
W <date time> cos: Initialization
failed for protocol priority
W <date time> cos: initialization
failed for Vlan priority
W <date time> cos: initialization
failed for device priority
W <date time> cos: initialization
failed for TOS mode
W <date time> cos: Initialization
failed for DiffServ priority
W <date time> cos: initialization
failed for port priority
C <date time> dhcp: entity enabled
I <date time> dhcp: initialization
failed
W <date time> dhcp: Can't allocate
any msg buffers
I <date time> dhcp: updating IP ad- I <date time> dhcp: updating IP ad- DHCP is updating the ip address, subnet mask and default gateway for
dress and subnet mask
Event/Alarm Description
I <date time> chassis: Slot <id>
Ready
W <date time> chassis: Unable to
Download to Slot <id>. Please Re-
move Card
W <date time> chassis: Module in
Slot <id> not Supported or may be
Faulty
W <date time> chassis: Backplane
link to slot <id> failed selftest
W <date time> cos: Initialization
failed for protocol priority
W <date time> cos: initialization
failed for Vlan priority
W <date time> cos: initialization
failed for device priority
W <date time> cos: initialization
failed for TOS mode
W <date time> cos: Initialization
failed for DiffServ priority
W <date time> cos: initialization
failed for port priority
C <date time> dhcp: entity enabled
I <date time> dhcp: initialization
failed
W <date time> dhcp: Can't allocate
any msg buffers
dress and subnet mask
MN002730A01-AD
Appendix E: Alarms and events
Additional Notes
This message appears whenever a module goes into the state of Avail-
able. The <id> in the format will indicate he slot.
This message appears whenever a module has exceeded the number
of download retries. The <id> in the format will indicate the slot.
This message appears whenever the backplane does not receive a
download request from a module. The <id> in the format will indicate
the slot.
This message appears whenever the backplane does not receive a
download request from a module. The <id> in the format will indicate
the slot.
This log event informs the user that there was an error during CoS initi-
alization for protocol based prioritization.
This log event informs the user that there was an error during CoS initi-
alization for Vlan based prioritization.
This log event informs the user that there was an error during CoS initi-
alization for device based prioritization.
This log event informs the user that there was an error during CoS initi-
alization for TOS based prioritization.
This log event informs the user that there was an error during CoS initi-
alization for Differentiated Services based prioritization.
This log event informs the user that there was an error during CoS initi-
alization for port based prioritization.
DHCP has successfully enabled
DHCP initialization failed
DHCP needed to allocate a message buffer but none were available.
Wait for traffic load to decline then try again. You may also need to re-
configure the switch without SNMP telnet or any other protocols that
are not currently necessary.
a VLAN interface. If this is a lease renewal then the IP configuration is
different than the prior lease configuration.
237
MN002730A01-AD
Appendix E: Alarms and events

Event Message Event/Alarm Description Additional Notes

W <date time> dhcp: subnet in W <date time> dhcp: subnet in The DHCP/BOOTP reply packet specified a subnet that has already
DHCP/BOOTP reply is already be- DHCP/BOOTP reply is already be- been used and thus is invalid.
ing used ing used
W <date time> dhcp: unable to re- W <date time> dhcp: unable to re- A DHCP lease expired and attempts to renew the lease failed.
new an expired DHCP lease new an expired DHCP lease
I <date time> dhcp: relay agent fea- I <date time> dhcp: relay agent fea- The DHCP relay agent feature has been enabled on the switch.
ture enabled ture enabled
I <date time> dhcpr: DHCP relay I <date time> dhcpr: DHCP relay The DHCP relay agent feature has been disabled on the switch.
agent feature disabled agent feature disabled
I <date time> dhcpr: No Resource I <date time> dhcpr: No Resource A remote download request was received from <ip addr or ipx network
for Download Request from <ip addr for Download Request from <ip addr numb>.
or ipx network numb> or ipx network numb>
I <date time> download: download I <date time> download: download A remote download request was received from <ip addr or ipx network
Request Received from <ip addr or Request Received from <ip addr or numb>.
ipx network numb> ipx network numb>
W <date time> download: port <id> W <date time> download: port <id> <id> is a letter-digit identifier (e.g. A1 F3) where the letter represents
- Excessive undersized/giant pack- - Excessive undersized/giant pack- the port module slot and the digit represents the port on the slot.
ets. See help. ets. See help.
W <date time> FFI: port <id> - Ex- W <date time> FFI: port <id> - Ex- <id> is a letter-digit identifier (e.g. A1 F3) where the letter represents
cessive jabbering. See help. cessive jabbering. See help. the port module slot and the digit represents the port on the slot.
W <date time> FFI: port <id> - Ex- W <date time> FFI: port <id> - Ex- <id> is a letter-digit identifier (e.g. A1 F3) where the letter represents
cessive CRC/alignment errors. See cessive CRC/alignment errors. See the port module slot and the digit represents the port on the slot.
help. help.
W <date time> FFI: port <id> - Ex- W <date time> FFI: port <id> - Ex- <id> is a letter-digit identifier (e.g. A1 F3) where the letter represents
cessive late collisions. See help. cessive late collisions. See help. the port module slot and the digit represents the port on the slot.
W <date time> FFI: port <id> - High W <date time> FFI: port <id> - High <id> is a letter-digit identifier (e.g. A1 F3) where the letter represents
collision or drop rate. See help. collision or drop rate. See help. the port module slot and the digit represents the port on the slot.
W <date time> FFI: port <id> - Ex- W <date time> FFI: port <id> - Ex- <id> is a letter-digit identifier (e.g. A1 F3) where the letter represents
cessive Broadcasts. See help. cessive Broadcasts. See help. the port module slot and the digit represents the port on the slot.
I <date time> fault: port <id> - Loss I <date time> fault: port <id> - Loss <id> > is a letter-digit identifier (e.g. A1 F3) where the letter represents
of Link of Link the port module slot and the digit represents the port on the slot.
W <date time> fault: port <id> - Se- W <date time> fault: port <id> - Se- <id> is a letter-digit identifier (e.g. A1 F3) where the letter represents
curity Violation curity Violation the port module slot and the digit represents the port on the slot.

238
 MN002730A01-AD
Appendix E: Alarms and events

Event Message Event/Alarm Description Additional Notes

W <date time> fault: port <id> Disa- W <date time> fault: port <id> Disa- <id> is a letter-digit identifier (e.g. A1 F3) where the letter represents
bled due to speed mismatch. See bled due to speed mismatch. See the port module slot and the digit represents the port on the slot.
help. help.
I <date time> update: Completed I <date time> update: Completed The file transfer was completed successfully.
W <date time> update: Aborted. No W <date time> update: Aborted. No No workspace There is no space left on device, no memory for trans-
workspace left in switch DRAM. workspace left in switch DRAM. fer.
W <date time> update: Aborted. W <date time> update: Aborted. Downloaded a corrupted file.
Downloaded file invalid. Downloaded file invalid.
W <date time> update: with Fatal W <date time> update: with Fatal Problem reading/writing from/to FLASH Memory.
Error. Hardware fault on device, Error. Hardware fault on device,
Corrupt FLASH. Corrupt FLASH.
W <date time> update: Aborted. File W <date time> update: Aborted. File There is no space left on device. No memory for transfer.
too big to fit in FLASH. too big to fit in FLASH.
W <date time> update: Aborted, W <date time> update: Aborted, The transferred file has a missing or incorrect id string or revision.
wrong file wrong file
W <date time> update: Finished, W <date time> update: Finished, The transferred file is identical to current file. No update performed.
identical file, no update performed. identical file, no update performed.
W <date time> update: Disabled W <date time> update: Disabled Switch ran out of memory and is temporarily disabling RMON to free
RMON to retrieve memory for down- RMON to retrieve memory for down- up memory.
load. load.
I <date time> garp: GARP Protocol I <date time> garp: GARP Protocol This log event informs the user that GARP has been enabled on the
enabled enabled Switch.
I <date time< garp: GARP Protocol I <date time< garp: GARP Protocol This log event informs the user that GARP has been disabled on the
disabled disabled Switch.
I <date time> garp: unknown appli- I <date time> garp: unknown appli- This log event informs the user that GARP received a PDU for an ap-
cation <0xXX> PDU received cation <0xXX> PDU received plication that it does not know about
I <date time> gvrp: GVRP Protocol I <date time> gvrp: GVRP Protocol This log event informs the user that GVRP has been enabled on the
enabled enabled Switch.
I <date time> gvrp: GVRP Protocol I <date time> gvrp: GVRP Protocol This log event informs the user that GVRP has been disabled on the
disabled disabled Switch.
W <date time> igmp: Multicast ad- W <date time> igmp: Multicast ad- An IP Multicast address could not be added to the address table be-
dress table is full dress table is full cause the table is full. Wait for the address table to age out an entry
and then re-subscribe to the group.

239
MN002730A01-AD
Appendix E: Alarms and events

Event Message Event/Alarm Description Additional Notes

I <date time> igmp: IGMP feature I <date time> igmp: IGMP feature The IGMP feature has been enabled on the switch or VLAN.
enabled enabled
W <date time> igmp: Querier initiali- W <date time> igmp: Querier initiali- This switch failed IGMP Querier initialization and cannot become Quer-
zation failed zation failed ier. Action: Reset the switch. If the failure persists it may be indicative
of an internal component or firmware failure; call your HP support pro-
vider for assistance.
W <date time> igmp: Port initializa- W <date time> igmp: Port initializa- There was an error during IGMP initialization on port <port_num>. This
tion failed for port <id> tion failed for port <id> port cannot be used for IGMP. Action: Reset the switch. If the failure
persists it may be indicative of an internal component or firmware fail-
ure; call your HP support provider for assistance. <id> is a letter-digit
identifier (e.g. A1 F3) where the letter represents the port module slot
and the digit represents the port on the slot.
I <date time> igmp: IGMP feature I <date time> igmp: IGMP feature The IGMP feature has been disabled for this switch or VLAN.
disabled disabled
I <date time> igmp: Querier Election I <date time> igmp: Querier Election The IGMP Querier Election feature has been disabled via the SNMP
feature disabled feature disabled command "setmib hpSwitchIgmpQuerierState. <vlan#> -i 2" where 2 is
defined as "disable".
I <date time> igmp: Querier Election I <date time> igmp: Querier Election The IGMP Querier Election feature has been disabled via the SNMP
feature enabled feature enabled command "setmib hpSwitchIgmpQuerierState. <vlan#> -i 1" where 1 is
defined as "enable".
C <date time> igmp: entity enabled C <date time> igmp: entity enabled IGMP service has been enabled.
I <date time> igmp: Querier Election I <date time> igmp: Querier Election The switch is currently running the Querier Election process to deter-
in process in process mine which qualified Querier on the network will become Querier for
the network.
I <date time> igmp: This switch has I <date time> igmp: This switch has This switch won the Querier Election and will now act as querier as
been elected as Querier been elected as Querier long as no other qualified Queriers are detected on the network.
I <date time> igmp: This switch was I <date time> igmp: This switch was This switch lost the Querier Election to another Querier device on the
not elected as Querier not elected as Querier network.
I <date time> igmp: Other Querier I <date time> igmp: Other Querier This switch was acting as Querier on the network but detected another
detected detected qualified Querier and yielded Querier function to that device.
I <date time> igmp: This switch is I <date time> igmp: This switch is This switch was acting as Querier on the network but detected another
no longer Querier . no longer Querier . qualified Querier and yielded Querier function to that device

240
 MN002730A01-AD
Appendix E: Alarms and events

Event Message Event/Alarm Description Additional Notes

I <date time> ip: changing IP ad- I <date time> ip: changing IP ad- Note: In all messages the vlan name is only printed if there is more
dress to <ip address> dress to <ip address> than one vlan. "ip: <vlan>: changing IP address to <ip address>" The
IP address for vlan <vlan> was changed to <ip address> by bootp.
W <date time> ip: IP initialization W <date time> ip: IP initialization ip: IP initialization failed for vlan <vlan> This log event informs the user
failed for vlan <vlan> failed for vlan <vlan> that there was an error during IP initialization for the vlan specified.
I <date time> ip: ARP: <ip address> I <date time> ip: ARP: <ip address> ip: <vlan name>: ARP: <ip address> at <mac address> <encapsula-
at <mac address> <encapsulation> at <mac address> <encapsulation> tion> - IP had added a new entry learned through the Address Resolu-
tion Protocol (ARP) to its address translation table. <ip address> is the
host address <mac address> is the physical address and <encapsula-
tion> used (ie ENET SNAP etc).
C <date time> ip: entity enabled C <date time> ip: entity enabled IP service has been enabled.
<date time> ip: Invalid ARP Source: <date time> ip: Invalid ARP Source: ip: <vlan>: Invalid ARP Source: <source ip address> on <target ip ad-
<source ip address> on <target ip <source ip address> on <target ip dress> - Dropping ARP packet because it is from an invalid source ip
address> address> address.
I <date time> ip: Invalid ARP Target: I <date time> ip: Invalid ARP Target: ip: <vlan>: Invalid ARP Target: <target ip address> on <source ip ad-
<target ip address> on <source ip <target ip address> on <source ip dress> - Dropping ARP packet because it specified an invalid target ip
address> address> address.
W <date time> ip: icmp: Unsolicited W <date time> ip: icmp: Unsolicited ip: <vlan>: icmp: Unsolicited Echo Reply from <ip address> - An unso-
Echo Reply from <ip address> Echo Reply from <ip address> licited ICMP reply to a ping was received from <ip address> that was
not sent by the local switch.
I <date time> ip: network enabled I <date time> ip: network enabled ip: <vlan>: network enabled on <ip address> - IP has enabled <ip ad-
on <ip address> on <ip address> dress> on vlan <vlan>
I <date time> ip: network disabled I <date time> ip: network disabled ip: <vlan>: network disabled on <ip address> - IP has disabled <ip ad-
on <ip address> on <ip address> dress> on vlan <vlan>
M <date time> ip: duplicate IP net- M <date time> ip: duplicate IP net- ip: <vlan>: duplicate IP network - Multiple VLANS have been config-
work work ured with the same IP network address.
M <date time> ip: bad ip address M <date time> ip: bad ip address ip: <vlan>: bad ip address <ip address> - The ip address <ip address>
<ip address> <ip address> is invalid.
W <date time> ip: bad mask W <date time> ip: bad mask ip: <vlan>: bad mask <mask>/<ip address> - IP has detected a dis-
<mask>/<ip address> . <mask>/<ip address> . crepancy between an ip address <ip address> and its associated sub-
net mask <mask>. Modify the configuration to correct the discrepancy
I <date time> lacp: Passive Dynam- I <date time> lacp: Passive Dynam- This is the default configuration and will appear only once at boot up as
ic LACP enabled on all ports ic LACP enabled on all ports long as it remains true.

241
MN002730A01-AD
Appendix E: Alarms and events
Event Message
I <date time> lacp: Dynamic LACP
trunk <trunk> is now on-line
I <date time> lacp: trunk <trunk> is
now off-line
I <date time> lacp: No Trunks Avail- I <date time> lacp: No Trunks Avail- No Trunks Available - request for Dynamic trunk denied
able
I <date time> lacp: Port <id> is in
Half Duplex - set to Individual
I <date time> lacp: Port <id> is
blocked - error condition
I <date time> lacp: Port <id> is
blocked - negotiation
I <date time> lacp: Port <id> is
blocked - re-negotiation
I <date time> lacp: Port <id> is
moved from trunk <trunk id> to trunk moved from trunk <trunk id> to trunk the port module slot and the digit represents the port on the slot. <trunk
<trunk id>
I <date time> lacp: Port <id> is
moved to trunk <trunk id>
I <date time> lacp: Port <id> is re-
moved from trunk <trunk id>
I <date time> ldbal: Load Balance
Protocol enabled
I <date time> ldbal: Load Balance
Protocol disabled
I <date time> ldbal: port <id> - es-
tablished
W <date time> ldbal: port <id> - not W <date time> ldbal: port <id> - not This log event informs the user that the LDBAL port enters the not es-
established
242
Event/Alarm Description
I <date time> lacp: Dynamic LACP
trunk <trunk> is now on-line
I <date time> lacp: trunk <trunk> is
now off-line
able
I <date time> lacp: Port <id> is in
Half Duplex - set to Individual
I <date time> lacp: Port <id> is
blocked - error condition
I <date time> lacp: Port <id> is
blocked - negotiation
I <date time> lacp: Port <id> is
blocked - re-negotiation
I <date time> lacp: Port <id> is <id> is a letter-digit identifier (e.g. A1 F3) where the letter represents
<trunk id> id> is the number of the trunk.
I <date time> lacp: Port <id> is
moved to trunk <trunk id>
I <date time> lacp: Port <id> is re-
moved from trunk <trunk id>
I <date time> ldbal: Load Balance
Protocol enabled
I <date time> ldbal: Load Balance
Protocol disabled
I <date time> ldbal: port <id> - es-
tablished
established tablished state. <id> is a letter-digit identifier (e.g. A1 F3) where the let-
Additional Notes
<id> is a letter-digit identifier (e.g. A1 F3) where the letter represents
the port module slot and the digit represents the port on the slot.
<id> is a letter-digit identifier (e.g. A1 F3) where the letter represents
the port module slot and the digit represents the port on the slot.
<id> is a letter-digit identifier (e.g. A1 F3) where the letter represents
the port module slot and the digit represents the port on the slot.
<id> is a letter-digit identifier (e.g. A1 F3) where the letter represents
the port module slot and the digit represents the port on the slot.
<id> is a letter-digit identifier (e.g. A1 F3) where the letter represents
the port module slot and the digit represents the port on the slot. <trunk
id> is the number of the trunk.
<id> is a letter-digit identifier (e.g. A1 F3) where the letter represents
the port module slot and the digit represents the port on the slot. <trunk
id> is the number of the trunk.
This log event informs the user that Load Balance Protocol is enabled
on the Switch.
This log event informs the user that Load Balance Protocol is disabled
on the Switch.
This log event informs the user that the LDBAL port enters the estab-
lished state. <id> is a letter-digit identifier (e.g. A1 F3) where the letter
represents the port module slot and the digit represents the port on the
slot.
 MN002730A01-AD
Appendix E: Alarms and events

Event Message Event/Alarm Description Additional Notes

ter represents the port module slot and the digit represents the port on
the slot.
C <date time> ldbal: port <id> - Rx C <date time> ldbal: port <id> - Rx This log event informs the user that a Type2 Query NAK was received
Type2 Query NAK Type2 Query NAK on a Load-Balance established port. <id> is a letter-digit identifier (e.g.
A1 F3) where the letter represents the port module slot and the digit
represents the port on the slot.
C <date time> ldbal: port <id> - Re- C <date time> ldbal: port <id> - Re- This log event informs the user that a MAC address moved
ceived Update Pkt from <mac addr> ceived Update Pkt from <mac addr>
C <date time> ldbal: Non existent C <date time> ldbal: Non existent This log event informs the user that a MAC address that does not exist
address <mac addr> deleted address <mac addr> deleted in the LdBal tables is being deleted
W <date time> ldbal: port <id>: re- W <date time> ldbal: port <id>: re- This log event informs the user that a port received a mesh packet on
ceived mesh packet on non-mesh ceived mesh packet on non-mesh a non-mesh port.
port port
W <date time> ldbal: Cannot accept W <date time> ldbal: Cannot accept This log event informs the user that the Series 5300 switch is seeing
switch 1600/24xx/4000/8000 into switch 1600/24xx/4000/8000 into the same MAC address on different vlans. If this is the case a Switch
mesh mesh 8000M/4000M/1600M/2400M/2424M will not be allowed into the mesh.
I <date time> mgr: changing time I <date time> mgr: changing time
I <date time> mgr: new time set I <date time> mgr: new time set
I <date time> mgr: SME <CON- I <date time> mgr: SME <CON- A console/telnet session has started (either via console port or telnet)
SOLE/TELNET> Session -<MAN- SOLE/TELNET> Session -<MAN- and the console session has Manager/Operator privileges.
AGER/OPERATOR> Mode estab- AGER/OPERATOR> Mode estab-
lished lished
W <date time> mgr: A remote login W <date time> mgr: A remote login
attempt failed attempt failed
I <date time> mgr: password(s) re- I <date time> mgr: password(s) re-
moved via clear button moved via clear button
W <date time> mgr: password file W <date time> mgr: password file
corrupted - ignoring passwords corrupted - ignoring passwords
I <date time> mgr: Config file updat- I <date time> mgr: Config file updat-
ed to default configuration. ed to default configuration.
I <date time> mgr: Config file con- I <date time> mgr: Config file con-
verted due to OS upgrade. verted due to OS upgrade.

243
MN002730A01-AD
Appendix E: Alarms and events

Event Message Event/Alarm Description Additional Notes

I <date time> mgr: Config file updat- I <date time> mgr: Config file updat-
ed via configuration editor. ed via configuration editor.
I <date time> mgr: Config file updat- I <date time> mgr: Config file updat-
ed from network download. ed from network download.
I <date time> mgr: Config file I <date time> mgr: Config file
erased via testmode clear com- erased via testmode clear com-
mand. mand.
I <date time> mgr: Config file I <date time> mgr: Config file
erased via the NCL delete com- erased via the NCL delete com-
mand. mand.
I <date time> mgr: Config file updat- I <date time> mgr: Config file updat-
ed via Bootp Reply. ed via Bootp Reply.
W <date time> mgr: "No configura- W <date time> mgr: "No configura-
tion summary record" tion summary record"
W <date time> netinet: route entry W <date time> netinet: route entry
creation(s) failed. creation(s) failed.
W <date time> netinet: arp entry W <date time> netinet: arp entry
creation(s) failed. creation(s) failed.
W <date time> netinet: mask for W <date time> netinet: mask for
route allocation(s) failed. route allocation(s) failed.
W <date time> ospf: Router LSA da- W <date time> ospf: Router LSA da- This log event informs the user that we attempted to add a new router
tabase overflow tabase overflow LSA to the link state database when the number of router LSAs in the
database was already at its maximum limit.
W <date time> ospf: Network LSA W <date time> ospf: Network LSA This log event informs the user that we attempted to add a new net-
database overflow database overflow work LSA to the link state database when the number of network LSAs
in the database was already at its maximum limit.
W <date time> ospf: Summary Net W <date time> ospf: Summary Net This log event informs the user that we attempted to add a new net-
LSA database overflow LSA database overflow work summary LSA to the link state database when the number of net-
work summary LSAs in the database was already at its maximum limit.
W <date time> ospf: Summary W <date time> ospf: Summary This log event informs the user that we attempted to add a new ASBR
ASBR LSA database overflow ASBR LSA database overflow Summary LSA to the link state database when the number of ASBR
Summary LSAs in the database was already at its maximum limit.

244
 MN002730A01-AD
Appendix E: Alarms and events

Event Message Event/Alarm Description Additional Notes

W <date time> ospf: AS External W <date time> ospf: AS External This log event informs the user that we attempted to add a new AS ex-
LSA database overflow LSA database overflow ternal LSA to the link state database when the number of AS external
LSAs in the database was already at its maximum limit.
I <date time> pagp: Port <id> is For- I <date time> pagp: Port <id> is For- Port failed PAgP negotiation, putting into Forwarding mode.
warding in Trunk mode warding in Trunk mode
I <date time> pagp: Port <id> is Lis- I <date time> pagp: Port <id> is Lis- Port <id> failed PAgP failed negotiation putting into Blocked mode. for
tening for PAgP Re-negotiation tening for PAgP Re-negotiation re-negotiation.
W <date time> pagp: Network mis- W <date time> pagp: Network mis- PAgP detected a misconfiguration on port <id>. PAgP blocks this port
configuration is detected. Port <id> configuration is detected. Port <id>
is blocked. is blocked.
I <date time> pagp: Port <id> is For- I <date time> pagp: Port <id> is For- pagp: <vlan>: Port <id> is Forwarding after PAgP negotiation success.
warding in FEC mode, nego. suc- warding in FEC mode, nego. suc-
cessful cessful
I <date time> pagp: Port <id> is Lis- I <date time> pagp: Port <id> is Lis- PAgP detects a physical port up indication blocking the port for nego-
tening for PAgP negotiation tening for PAgP negotiation tiation. .
W <date time> pagp: Detected net- W <date time> pagp: Detected net- PAgP detects a misconfiguration But does not have enough informa-
work misconfiguration on port <id> work misconfiguration on port <id> tion to determine which port to block. Leaves port as Forwarding
I <date time> ports: port <id> is now I <date time> ports: port <id> is now ports: port <id> is now on-line Indicates the port changed from an off-
on-line . on-line . line to on-line state. To be on-line the port must be both connected into
the LAN and enabled through configuration. <id> is a letter-digit identi-
fier (e.g. A1 F3) where the letter represents the port module slot (A thru
F) and the digit represents the port on the slot (1 thru 4 for Ethernet
modules and 1 thru 2 for 100VG)
I <date time> ports: port <id> is now I <date time> ports: port <id> is now ports: port <id> is now off-line Indicates the port changed from an on-
off-line off-line line to off-line state. This occurs when the port is physically disconnect-
ed from the LAN disabled through configuration or both. <id> is a let-
ter-digit identifier (e.g. A1 F3) where the letter represents the port mod-
ule slot (A thru F) and the digit represents the port on the slot (1 thru 4
for Ethernet modules and 1 thru 2 for 100VG).
I <date time> ports: trunk <id> is I <date time> ports: trunk <id> is ports: trunk <id> is now active Indicates the port trunk has changed
now active now active from an inactive to active state. This occurs when all ports in the trunk
are off-line and then one port comes on-line. <id> is always "Tr1" since
there can be only one port trunk on the switch.
I <date time> ports: trunk <id> is I <date time> ports: trunk <id> is ports: trunk <id> is now inactive Indicates the port trunk has changed
now inactive now inactive from an active to inactive state. This occurs when the last on-line port

245
MN002730A01-AD
Appendix E: Alarms and events

Event Message Event/Alarm Description Additional Notes

in the trunk goes off-line such that there are now no ports in the trunk
that are on-line. <id> is always "Tr1" since there can be only one port
trunk on the switch.
W <date time> ports: Port initializa- W <date time> ports: Port initializa- This log event informs the user that there was an error during port initi-
tion failed for port <id> tion failed for port <id> alization for the port specified. <id> is the port number.
W <date time> ports: port <id>Carri- W <date time> ports: port <id>Carri- port <id> Carrier Sense Stuck, Resetting Xcvr Indicates the 10/100T
er Sense Stuck, Resetting Xcvr er Sense Stuck, Resetting Xcvr Xcvr's Carrier sense is stuck. <id> is the port with the failing Xcvr (i.e.
A1 A2 ...)
W <date time> ports: port <id> Xcvr W <date time> ports: port <id> Xcvr
Error, Resetting Xcvr Error, Resetting Xcvr
W <date time> ports: resetting port W <date time> ports: resetting port
<id>: remote fault, ieee, parallel de- <id>: remote fault, ieee, parallel de-
tect tect
W <date time> ports: port <id>: Xcvr W <date time> ports: port <id>: Xcvr
not supported in current OS not supported in current OS
M <date time> snmp: Unknown var M <date time> snmp: Unknown var
type type
W <date time> snmp: "public" com- W <date time> snmp: "public" com- snmp: `public' community deleted. Net Mgmt may have problems The
munity deleted. Net Mgmt may have munity deleted. Net Mgmt may have community name "public" is a common name used by many network
problems problems management applications. "public" has been deleted. HP network
management functionality like auto-discovery and traffic management
will not operate. Many other functions will not function unless alterna-
tive community names are explicitly configured on this device and the
network management station.
C <date time> sntp: client enabled C <date time> sntp: client enabled SNTP: client enabled SNTP has been successfully enabled.
I <date time> sntp: timedout waiting I <date time> sntp: timedout waiting SNTP: timedout waiting for broadcast Failed to receive an update from
for broadcast for broadcast a broadcast server
I <date time> sntp: updated time by I <date time> sntp: updated time by Updated system time by given amount
<+/- adjustment in seconds> sec- <+/- adjustment in seconds> sec-
onds onds
I <date time> sntp: all configured I <date time> sntp: all configured SNTP: all configured servers failed unable to receive an SNTP update
servers failed servers failed from any of the configured servers

246
 MN002730A01-AD
Appendix E: Alarms and events

Event Message Event/Alarm Description Additional Notes

I <date time> sntp: preferred broad- I <date time> sntp: preferred broad- SNTP: preferred broadcast server did not send broadcast in time. pre-
cast server did not send broadcast cast server did not send broadcast ferred sntp broadcast server did not send a broadcast in the time allot-
in time. in time. ted.
I <date time> sntp: found new pre- I <date time> sntp: found new pre- SNTP: found new preferred broadcast server at <ip_addr>. sntp client
ferred broadcast server at ferred broadcast server at found a new broadcast server to be used as the preferred broadcast
<ip_addr>. <ip_addr>. server.
I <date time> ssh: SSH server ena- I <date time> ssh: SSH server ena-
bled bled
I <date time> ssh: SSH server disa- I <date time> ssh: SSH server disa-
bled bled
I <date time> stack: Stack Protocol I <date time> stack: Stack Protocol stack: Stack Protocol enabled This log event informs the user that
enabled enabled Stack Protocol is enabled on the Switch.
W <date time> stack: Stack Protocol W <date time> stack: Stack Protocol stack: Stack Protocol disabled This log event informs the user that
disabled disabled Stack Protocol is disabled on the Switch.
I <date time> stp: Spanning Tree I <date time> stp: Spanning Tree stp: Spanning Tree Protocol enabled This log event informs the user
Protocol enabled Protocol enabled that Spanning Tree Protocol is enabled on the Switch.
I <date time> stp: Spanning Tree I <date time> stp: Spanning Tree stp: Spanning Tree Protocol disabled This log event informs the user
Protocol disabled Protocol disabled that Spanning Tree Protocol is disabled on the Switch.
W <date time> stp: STP not enabled W <date time> stp: STP not enabled
- multiple VLANS defined - multiple VLANS defined
I <date time> system: - I <date time> system: -
------------------------------------------------ ------------------------------------------------
I <date time> system: System went I <date time> system: System went
down without saving crash informa- down without saving crash informa-
tion tion
M <date time> system: Boot-up M <date time> system: Boot-up system: Boot-up selftest failed This message appears if the boot up
selftest failed selftest failed selftest resulted in a failure. A slot selftest failure message will also be
logged for each slot that resulted in a failure.
I <date time> system: System Boot- I <date time> system: System Boot- system: System Booted. This message appears at the conclusion of
ed. ed. the boot process.
W <date time> system: system Out W <date time> system: system Out
of <message/packet> buffers; miss of <message/packet> buffers; miss
count: <number missed> count: <number missed>

247
MN002730A01-AD
Appendix E: Alarms and events

Event Message Event/Alarm Description Additional Notes

I <date time> tftp: PUT <object> to I <date time> tftp: PUT <object> to tftp: PUT <object> to <address>, file <filename> TFTP is attempting to
<address>, file <filename> <address>, file <filename> put file <filename> of type <object> (CONFIG CRASH RECORD) to
host <address>.
I <date time> tftp: tftp E GET <local I <date time> tftp: tftp E GET <local tftp: GET <local file> from <address>, file <remote file> TFTP is at-
file> from <address>, file <remote file> from <address>, file <remote tempting to get <local file> which is either a CONFIG OS or CRASH
file> file> RECORD file from host <address> remote file <remote file>.
I <date time> tftp: Enable succeed- I <date time> tftp: Enable succeed- The download TFTP capability has been successfully initialized.
ed ed
I <date time> tftp: WRQ from <ad- I <date time> tftp: WRQ from <ad- tftp: WRQ from <address> for file <filename> TFTP received a write re-
dress> for file <filename> dress> for file <filename> quest from the sender indicated for the file named filename.
I <date time> tftp: RRQ from <ad- I <date time> tftp: RRQ from <ad- tftp: RRQ from <address> for file <filename> TFTP received a read re-
dress> for file <filename> dress> for file <filename> quest from the sender indicated for the file named filename.
I <date time> tftp: Transfer complet- I <date time> tftp: Transfer complet- tftp: transfer complete. TFTP successfully transferred file.
ed ed
W <date time> tftp: RCVD error:<er- W <date time> tftp: RCVD error:<er- tftp: RCVD error:<error>, msg:<errmsg> TFTP received error <error
ror>, msg:<errmsg> ror>, msg:<errmsg> number> with message <errmsg>.
W <date time> tftp: Transfer timed W <date time> tftp: Transfer timed tftp: Transfer timed out TFTP transfer timed out.
out. out.
W <date time> tftp: SENT error:<er- W <date time> tftp: SENT error:<er- tftp: SENT error:<error>, msg:<errmsg> TFTP sent error <error num-
ror>, msg:<errmsg> ror>, msg:<errmsg> ber> with message <errmsg>.
W <date time> tftp: Transfer abort- W <date time> tftp: Transfer abort- tftp: Transfer aborted, wrong file The transferred file has a missing or
ed, wrong file ed, wrong file incorrect id string or revision.
W <date time> tftp: Connection to W <date time> tftp: Connection to tftp: Connection to <address> failed. TFTP connection attempt to <ad-
<address> failed. <address> failed. dress> failed.
W <date time> tftp: Request failed. W <date time> tftp: Request failed. tftp: Request failed. TFTP request failed for some resource reason.
C <date time> tftp: TFTP daemon C <date time> tftp: TFTP daemon The download capability from TFTP daemon enabled.
enabled enabled
W <date time> tftp: TFTP daemon W <date time> tftp: TFTP daemon The download capability from TFTP daemon failed. It is no longer
failed failed available.
W <date time> tftp: Transfer can- W <date time> tftp: Transfer can- There is no space left on device no memory for transfer.
celed. No workspace left on device. celed. No workspace left on device.

248
 MN002730A01-AD
Appendix E: Alarms and events

Event Message Event/Alarm Description Additional Notes

W <date time> tftp: Transfer can- W <date time> tftp: Transfer can- tftp downloaded a corrupt file.
celed. Downloaded file corrupt. celed. Downloaded file corrupt.
W <date time> tftp: Transfer Fatal W <date time> tftp: Transfer Fatal Problem reading/writing from/to FLASH Memory.
Error. Hardware fault on device, Error. Hardware fault on device,
Corrupt FLASH. Corrupt FLASH.
W <date time> tftp: Transfer can- W <date time> tftp: Transfer can- There is no space left on device no memory for transfer.
celed. File too big to fit in FLASH. celed. File too big to fit in FLASH.
I <date time> timep: timep client en- I <date time> timep: timep client en- The timep entity has been enabled.
abled timep: entity enabled abled timep: entity enabled
I <date time> timep: can't reach time I <date time> timep: can't reach time timep: can't reach time server <ip addr> Timep could not reach <ip
server <ip addr> server <ip addr> addr> and thus timed out.
I <date time> timep: client polling I <date time> timep: client polling timep: client polling server at <ip addr> The timep client is polling the
server at <ip addr> server at <ip addr> server at <ip addr> for the timep response.
I <date time> timep: changing time I <date time> timep: changing time timep: changing time The timep client has received a timep response
and is currently updating the new time received.
I <date time> timep: new time set I <date time> timep: new time set timep: new time set The timep client has just reset the time based on
the latest timep response just received.
I <date time> vlan: <vlan _name> I <date time> vlan: <vlan _name> vls: <vlan _name> virtual LAN enabled This log event informs the user
virtual LAN enabled virtual LAN enabled when a virtual LAN comes up. This happens when the first port defined
to be part of that virtual LAN comes up. <vlan_name> is the textual
name of the virtual LAN.
I <date time> vlan: <vlan _name> I <date time> vlan: <vlan _name> vls: <vlan_name> virtual LAN disabled This log event informs the user
virtual LAN disabled virtual LAN disabled when a virtual LAN has gone down. This happens when the last port
defined to be a part of the virtual LAN goes down. <vlan_name> is the
textral name of the virtual LAN.
I <date time> vlan: vlan <vlan_id> I <date time> vlan: vlan <vlan_id> vls: vlan <vlan_id> defined but not active This log event informs the
defined but not active defined but not active user that a vlan has been configured but is being ignored because it
has not been marked active. <vlan_id> is the id number of the virtual
LAN.
W <date time> vlan: port W <date time> vlan: port vls: port <port_num> is member of an invalid vlan <vlan_id> This log
<port_num> is member of an invalid <port_num> is member of an invalid event informs the user that a port has been configured for a vlan that
vlan <vlan_id> vlan <vlan_id> does not exist. <port_num> is the port number. <vlan_id> is the id
number of the virtual LAN.

249
MN002730A01-AD
Appendix E: Alarms and events

Event Message Event/Alarm Description Additional Notes

W <date time> xmodem: Terminal W <date time> xmodem: Terminal
connection broken connection broken
W <date time> xmodem: Failed W <date time> xmodem: Failed
Checksum during Transfer. Checksum during Transfer.
W <date time> xmodem: Transfer W <date time> xmodem: Transfer
terminated by remote terminated by remote
W <date time> xmodem: Cannot W <date time> xmodem: Cannot
open local file, transfer aborted open local file, transfer aborted
W <date time> xmodem: a bad 32 W <date time> xmodem: a bad 32
bit CRC on a data packet. bit CRC on a data packet.
W <date time> xmodem: Transfer W <date time> xmodem: Transfer
canceled. No space left on device. canceled. No space left on device.
W <date time> xmodem: Too many W <date time> xmodem: Too many
bytes before SOF bytes before SOF
W <date time> xmodem: Bad data W <date time> xmodem: Bad data
subpacket from remote subpacket from remote
W <date time> xmodem: Transfer W <date time> xmodem: Transfer
terminated due to timeout terminated due to timeout
W <date time> xmodem: Received W <date time> xmodem: Received
a bad 16 bit CRC on binary header. a bad 16 bit CRC on binary header.
W <date time> xmodem: Received W <date time> xmodem: Received
a bad 32 bit CRC on binary header. a bad 32 bit CRC on binary header.
W <date time> xmodem: Received W <date time> xmodem: Received
a bad 16 bit CRC on hex header. a bad 16 bit CRC on hex header.
W <date time> xmodem: No Ques- W <date time> xmodem: No Ques-
tion Marks tion Marks
W <date time> xmodem: Unable to W <date time> xmodem: Unable to
get remote init parameters get remote init parameters
W <date time> xmodem: Transfer W <date time> xmodem: Transfer
complete complete
W <date time> xmodem: to connect W <date time> xmodem: to connect
to remote to remote

250
 MN002730A01-AD
Appendix E: Alarms and events

Event Message Event/Alarm Description Additional Notes

W <date time> xmodem: config file
cannot be appended, set host for
overwrite
W <date time> xmodem: Unable to
synchronize with remote.
W <date time> xmodem: Transfer
aborted, wrong file.
W <date time> xmodem: Unable to
read header from remote.
W <date time> xmodem: Unable to
read data from remote.
W <date time> xmodem: Filename
too long.
W <date time> xmodem: warning
remote appended data to existing
file.
W <date time> xmodem: Timeout
trying to sync with remote
W <date time> xmodem: Xmodem
transfer aborted.
W <date time> xmodem: Unexpect- W <date time> xmodem: Unexpect-
ed character from remote ed character from remote
W <date time> xmodem: config file
cannot be appended, set host for
overwrite
W <date time> xmodem: Unable to
synchronize with remote.
W <date time> xmodem: Transfer
aborted, wrong file.
W <date time> xmodem: Unable to
read header from remote.
W <date time> xmodem: Unable to
read data from remote.
W <date time> xmodem: Filename
too long.
W <date time> xmodem: warning
remote appended data to existing
file.
W <date time> xmodem: Timeout
trying to sync with remote
W <date time> xmodem: Xmodem
transfer aborted.

E.10.5
HP Switch Trap Rules
Use HP Switch Events for detailed information on HP Switch trap rules.
NOTICE: Event messages in the table are applicable to all HP Switch models.

251
MN002730A01-AD
Appendix E: Alarms and events

Event Name Event ID Se- Event/Alarm Message Event

veri- Catego-
ty ry
HPModelSpecificTrap .1.3.6.1.4.1.11.2.3.7.11.17.0.2 Info HP Procurve 5308xl Trap Informa-
tional
Event
HPModelSpecificTrap .1.3.6.1.4.1.11.2.3.7.11.19.0.2 Info HP Procurve 2524 Trap Informa-
tional
Event
HPModelSpecificTrap .1.3.6.1.4.1.11.2.3.7.11.34.0.2 Info HP Procurve 2626A Trap Informa-
tional
Event
HPModelSpecificTrap .1.3.6.1.4.1.11.2.3.7.11.45.0.2 Info HP Procurve 2626B Trap Informa-
tional
Event
HPModelSpecificTrap .1.3.6.1.4.1.11.2.3.7.11.29.0.2 Info HP Procurve 2650A Trap Informa-
tional
Event
HPModelSpecificTrap .1.3.6.1.4.1.11.2.3.7.11.44.0.2 Info HP Procurve 2650B Trap Informa-
tional
Event
HpSwitch3500yl48G .1.3.6.1.4.1.11.2.3.7.11.59.0.2 Info HP Procurve 3500 Trap Informa-
tional
Event
HpSwitch3500yl24G .1.3.6.1.4.1.11.2.3.7.11.58.0.2 Info HP Procurve 3500 Trap Informa-
tional
Event
HpSwitch2610-24 .1.3.6.1.4.1.11.2.3.7.11.76.0.2 Info HP Procurve 2610-24 Trap Informa-
tional
Event
HpSwitch2610-48 .1.3.6.1.4.1.11.2.3.7.11.77.0.2 Info HP Procurve 2610-48 Trap Informa-
tional
Event
HpSwitch3800-48G .1.3.6.1.4.1.11.2.3.7.11.122.0.2 Info HP Networking 3800 Trap Informa-
tional
Event

252
 MN002730A01-AD
Appendix E: Alarms and events

Event Name Event ID Se- Event/Alarm Message Event

veri- Catego-
ty ry
HpSwitch2620-24 .1.3.6.1.4.1.11.2.3.7.11.129.0.2 Info HP Networking 2620-24 Trap Informa-
tional
Event
HpSwitch2620-48 .1.3.6.1.4.1.11.2.3.7.11.132.0.2 Info HP Networking 2620-48 Trap Informa-
tional
Event
HpSwitchAru- .1.3.6.1.4.1.11.2.3.7.11.181.18.0.2 Info HPE Networking Switch 2930-24 Trap Informa-
ba2930-24 tional
Event
HpSwitchAru- .1.3.6.1.4.1.11.2.3.7.11.181.19.0.2 Info HPE Networking Switch 2930-48 Trap Informa-
ba2930-48 tional
Event
HpSwitchArubaS- .1.3.6.1.4.1.11.2.3.7.8.5.5.0.2 Info HPE Networking Switch 2930 Stacked Trap Informa-
tacked tional
Event
hpicfFaultFinderTrap .1.3.6.1.4.1.11.2.14.12.1.0.5 Info hpicfFaultFinderTrap. Log Fault Type = {1 : hpicfFfLogFault- Informa-
Type : .1.3.6.1.4.1.11.2.14.11.1.7.2.1.4.*}, Log Action = {2 : tional
hpicfFfLogAction : .1.3.6.1.4.1.11.2.14.11.1.7.2.1.5.*}, Log Severi- Event
ty = {3 : hpicfFfLogSeverity : .1.3.6.1.4.1.11.2.14.11.1.7.2.1.6.*},
Fault Info URL = {4 : hpicfFfFaultIn-
foURL : .1.3.6.1.4.1.11.2.14.11.1.7.3}, Log Physical Entity = {5 :
hpicfFfLogPhysEntity : .1.3.6.1.4.1.11.2.14.11.1.7.2.1.3.*}
hpicfSensorTrap .1.3.6.1.4.1.11.2.14.12.1.0.3 Info hpicfSensorTrap. Sensor Status = {1 : hpicfSensorSta- Informa-
tus : .1.3.6.1.4.1.11.2.14.11.1.2.6.1.4.*}, Sensor Descr = {2 : tional
hpicfSensorDescr : .1.3.6.1.4.1.11.2.14.11.1.2.6.1.7.*} Event
hpicfSelfTestTrap .1.3.6.1.4.1.11.2.14.12.1.0.4 Info hpicfSelfTestTrap. Self Test Result Text = {1 : hpicfSelfTestRe- Informa-
sultText : .1.3.6.1.4.1.11.2.14.11.1.4.5.2.*} tional
Event
hpicfBridgeLoopPro- .1.3.6.1.4.1.11.2.14.11.5.1.12.1.5.0.1 Info hpicfBridgeLoopProtectLoopDetectedNotification. Index = {1 : ifIn- Informa-
tectLoopDetectedNoti- dex : .1.3.6.1.2.1.2.2.1.1.*}, BridgeLoop Protect Port LoopCount = tional
fication {2 : hpicfBridgeLoopProtectPortLoop- Event
Count : .1.3.6.1.4.1.11.2.14.11.5.1.12.1.5.2.1.1.4.*}, BridgeLoop
Protect Port Receiver Action = {3 : hpicfBridgeLoopProtectPor-
tReceiverAction : .1.3.6.1.4.1.11.2.14.11.5.1.12.1.5.2.1.1.5.*}

253
MN002730A01-AD
Appendix E: Alarms and events

Event Name Event ID Se- Event/Alarm Message Event

hpicfConnectionRate- .1.3.6.1.4.1.11.2.14.11.5.1.24.0.1
FilterNotification
hpicfIntrusionTrap .1.3.6.1.4.1.11.2.14.12.4.0.1
hpicfUSBPortEnabled .1.3.6.1.4.1.11.2.14.11.5.1.53.0.1
hpicfUSBPortDisabled .1.3.6.1.4.1.11.2.14.11.5.1.53.0.2
hpicfUsrAuthCLIAuth- .1.3.6.1.4.1.11.2.14.11.5.1.19.0.1
Fail
hpicfArpProtectErran- .1.3.6.1.4.1.11.2.14.11.5.1.37.0.1
tReply
veri- Catego-
ty ry
Info hpicfConnectionRateFilterNotification. Connection Rate Filter Vla- Informa-
nId = {1 : hpicifConnectionRateFilterVla- tional
nId : .1.3.6.1.4.1.11.2.14.11.5.1.24.2.1.*}, Connection Rate Filter Event
InetAddress = {2 : hpicifConnectionRateFilterInetAd-
dress : .1.3.6.1.4.1.11.2.14.11.5.1.24.2.2.*}, Connection RateFil-
ter InetAddress Type = {3 : hpicifConnectionRateFilterInetAddres-
sType : .1.3.6.1.4.1.11.2.14.11.5.1.24.2.3.*}, Connection Rate Fil-
ter Mode = {4 : hpicifConnectionRateFilter-
Mode : .1.3.6.1.4.1.11.2.14.11.5.1.24.2.4.*}
Info hpicfIntrusionTrap. Intruder Group = {1 : hubIntru- Informa-
derGroup : .1.3.6.1.4.1.11.2.14.2.10.2.1.2.*}, Intruder Port = {2 : tional
hubIntruderPort : .1.3.6.1.4.1.11.2.14.2.10.2.1.3.*}, Intruder Ad- Event
dress = {3 : hubIntruderAd-
dress : .1.3.6.1.4.1.11.2.14.2.10.2.1.4.*}, Intruder Type = {4 : hu-
bIntruderType : .1.3.6.1.4.1.11.2.14.2.10.2.1.6.*}, Intruder Train-
ing Violation = {5 : hubIntruderTrainingViola-
tion : .1.3.6.1.4.1.11.2.14.2.10.2.1.7.*}
Info HP Procurve 3500 Trap - USB port enabled Informa-
tional
Event
Info HP Procurve 3500 Trap - USB port disabled Informa-
tional
Event
Info hpicfUsrAuthCLIAuthFail. Count of failed attempts = {1 : hpicfUs- Informa-
rAuthCLIFailCnt : .1.3.6.1.4.1.11.2.14.11.5.1.19.1.8}, Interface tional
generating the traps = {2 : hpicfUsrAuthCLIInter- Event
face : .1.3.6.1.4.1.11.2.14.11.5.1.19.1.6}
Info hpicfArpProtectErrantReply. Errant Arp Reply Packet Counter = Informa-
{1 : hpicfArpProtectErrantCnt : .1.3.6.1.4.1.11.2.14.11.5.1.37.1.3}, tional
Errant Arp Reply Packet Source MAC = {2 : hpicfArpProtectEr- Event
rantSrcMac : .1.3.6.1.4.1.11.2.14.11.5.1.37.1.4}, Errant Arp Reply
Packet Source IP Type = {3 : hpicfArpProtectErrantSrcIp-
Type : .1.3.6.1.4.1.11.2.14.11.5.1.37.1.5}, Errant Arp Reply Pack-
et Source IP = {4 : hpicfArpProtectErrantSr-
cIp : .1.3.6.1.4.1.11.2.14.11.5.1.37.1.6}, Errant Arp Reply Packet

254
 MN002730A01-AD
Appendix E: Alarms and events

Event Name Event ID Se- Event/Alarm Message Event

veri- Catego-
ty ry
Destination MAC = {5 : hpicfArpProtectErrantDest-
Mac : .1.3.6.1.4.1.11.2.14.11.5.1.37.1.7}, Errant Arp Reply Packet
Destination IP Type = {6 : hpicfArpProtectErrantDestIp-
Type : .1.3.6.1.4.1.11.2.14.11.5.1.37.1.8}, Errant Arp Reply Pack-
et Destination IP = {7 : hpicfArpProtectErrantDes-
tIp : .1.3.6.1.4.1.11.2.14.11.5.1.37.1.9}
hpicfSwitchAuthSer- .1.3.6.1.4.1.11.2.14.11.5.1.32.0.1 Info hpicfSwitchAuthServerFail. Authorization Server Type = {1 : Informa-
verFail hpicfSwitchAuthServer- tional
Type : .1.3.6.1.4.1.11.2.14.11.5.1.32.1.2.1}, Authorization Server Event
IP Type = {2 : hpicfSwitchAuthServerIP-
Type : .1.3.6.1.4.1.11.2.14.11.5.1.32.1.2.2}, Authorization Server
IP = {3 : hpicfSwitchAuthServer-
IP : .1.3.6.1.4.1.11.2.14.11.5.1.32.1.2.3}
hpicfBridgeVlanLoop- .1.3.6.1.4.1.11.2.14.11.5.1.12.1.5.0.2 Info hpicfBridgeVlanLoopProtectLoopDetectedNotification. Index = Informa-
ProtectLoopDetected- {1 : ifIndex : .1.3.6.1.2.1.2.2.1.1.*}, BridgeLoop Protect Port Loop- tional
Notification Count = {2 : hpicfBridgeLoopProtectPortLoop- Event
Count : .1.3.6.1.4.1.11.2.14.11.5.1.12.1.5.2.1.1.4.*}, BridgeLoop
Protect Port Receiver Action = {3 : hpicfBridgeLoopProtectPor-
tReceiverAction : .1.3.6.1.4.1.11.2.14.11.5.1.12.1.5.2.1.1.5.*},
BridgeLoop Detected Vlan = {4 : hpicfBridgeLoopDetectedV-
lan : .1.3.6.1.4.1.11.2.14.11.5.1.12.1.5.2.1.1.6.*}
hpicfDhcpSnoopErran- .1.3.6.1.4.1.11.2.14.11.5.1.34.0.1 Info hpicfDhcpSnoopErrantReply. DHCP Snooping Notification Coun- Informa-
tReply ter = {1 : hpicfDhcpSnoopNotify- tional
Count : .1.3.6.1.4.1.11.2.14.11.5.1.34.1.3.1}, Errant DHCP Reply Event
Packet MAC = {2 : hpicfDhcpSnoopErrantSrc-
MAC : .1.3.6.1.4.1.11.2.14.11.5.1.34.1.3.2}, Errant DHCP Reply
Packet Source IP Type = {3 : hpicfDhcpSnoopErrantSrcIP-
Type : .1.3.6.1.4.1.11.2.14.11.5.1.34.1.3.3}, Errant DHCP Reply
Packet Source IP = {4 : hpicfDhcpSnoopErrantSr-
cIP : .1.3.6.1.4.1.11.2.14.11.5.1.34.1.3.4}
hpicfInstMonNotifica- .1.3.6.1.4.1.11.2.14.11.5.1.35.1.5 Info hpicfInstMonNotification. Text = {1 : hpicfInstMonNotification- Informa-
tion Text : .1.3.6.1.4.1.11.2.14.11.5.1.35.1.4} tional
Event

255
MN002730A01-AD
Appendix E: Alarms and events

Event Name Event ID Se- Event/Alarm Message Event

veri- Catego-
ty ry
hpicfIpLockOutOfRe- .1.3.6.1.4.1.11.2.14.11.5.1.39.0.1.2 Info hpicfIpLockOutOfResources. Port Index = {1 : hpicfIpLockAddr- Informa-
sources Port : .1.3.6.1.4.1.11.2.14.11.5.1.39.1.2.2.1.1.*}, Permitted MAC = tional
{2 : hpicfIpLockAddrMacAd- Event
dress : .1.3.6.1.4.1.11.2.14.11.5.1.39.1.2.2.1.5.*}, Permitted IP =
{3 : hpicfIpLockAddrIpAd-
dress : .1.3.6.1.4.1.11.2.14.11.5.1.39.1.2.2.1.3.*}, Permitted
VLAN = {4 : hpicfIpLockAddrV-
lan : .1.3.6.1.4.1.11.2.14.11.5.1.39.1.2.2.1.4.*}, Root Cause = {5 :
hpicfIpLockOutOfResource-
Source : .1.3.6.1.4.1.11.2.14.11.5.1.39.0.1.1}
hpicfIpLockErrantNoti- .1.3.6.1.4.1.11.2.14.11.5.1.39.0.1.3 Info hpicfIpLockErrantNotify. Notification Number = {1 : hpicfIpLock- Informa-
fy NotifyCount : .1.3.6.1.4.1.11.2.14.11.5.1.39.0.1.4.1}, Port Index = tional
{2 : hpicfIpLockNotifyPort : .1.3.6.1.4.1.11.2.14.11.5.1.39.0.1.4.2}, Event
Source IP Type = {3 : hpicfIpLockNotifySrcIp-
Type : .1.3.6.1.4.1.11.2.14.11.5.1.39.0.1.4.3}, Source IP = {4 :
hpicfIpLockNotifySrcIpAd-
dress : .1.3.6.1.4.1.11.2.14.11.5.1.39.0.1.4.4}, Destination IP
Type = {5 : hpicfIpLockNotifyDstIp-
Type : .1.3.6.1.4.1.11.2.14.11.5.1.39.0.1.4.5}, Destination IP =
{6 : hpicfIpLockNotifyDstIpAd-
dress : .1.3.6.1.4.1.11.2.14.11.5.1.39.0.1.4.6}, Source MAC = {7 :
hpicfIpLockNotifyMacAd-
dress : .1.3.6.1.4.1.11.2.14.11.5.1.39.0.1.4.7}, Dropped Packets =
{8 : hpicfIpLockNotifyPkt-
Count : .1.3.6.1.4.1.11.2.14.11.5.1.39.0.1.4.8}
hpicfMacNotifyMacAd- .1.3.6.1.4.1.11.2.14.11.5.1.66.0.1 Info hpicfMacNotifyMacAddressTableChange. MAC address table Informa-
dressTableChange change action = {1 : hpicfMacNotifyAc- tional
tion : .1.3.6.1.4.1.11.2.14.11.5.1.66.1.6}, MAC address = {2 : Event
hpicfMacNotifyMacAddress : .1.3.6.1.4.1.11.2.14.11.5.1.66.1.7},
Port Index related with the MAC previously = {3 : hpicfMacNotify-
FromPortId : .1.3.6.1.4.1.11.2.14.11.5.1.66.1.8}, Port Index relat-
ed with the MAC currently = {4 : hpicfMacNotifyToPor-
tId : .1.3.6.1.4.1.11.2.14.11.5.1.66.1.9}, VLAN related with teh
MAC = {5 : hpicfMacNotifyVla-
nId : .1.3.6.1.4.1.11.2.14.11.5.1.66.1.10}

256
 MN002730A01-AD
Appendix E: Alarms and events

Event Name Event ID Se- Event/Alarm Message Event

veri- Catego-
ty ry
hpicfMacNotifyPortMa- .1.3.6.1.4.1.11.2.14.11.5.1.66.0.2 Info hpicfMacNotifyPortMacAddressCount. Port ID for MAC notify = Informa-
cAddressCount {1 : hpicfMacNotifyToPortId : .1.3.6.1.4.1.11.2.14.11.5.1.66.1.9}, tional
VLAN ID for MAC notify = {2 : hpicfMacNotifyVla- Event
nId : .1.3.6.1.4.1.11.2.14.11.5.1.66.1.10}, Number of MAC
learned on port = {3 : hpicfMacNotifyPortLearned-
Count : .1.3.6.1.4.1.11.2.14.11.5.1.66.5.3}, Specifies the exceed-
ed MAC learn address = {4 : hpicfMacNotifyMacAd-
dress : .1.3.6.1.4.1.11.2.14.11.5.1.66.1.7}
hpicfUfdLtDAutoDisa- .1.3.6.1.4.1.11.2.14.11.5.1.74.0.0.3 Info hpicfUfdLtDAutoDisabled. Track ID = {1 : hpicfUfdNotifyTrack- Informa-
bled Id : .1.3.6.1.4.1.11.2.14.11.5.1.74.1.1.2}, List of Ports = {2 : hpic- tional
fUfdLinksToTransition : .1.3.6.1.4.1.11.2.14.11.5.1.74.1.2.1.1.4.*} Event
hpicfUfdLtDAutoEna- .1.3.6.1.4.1.11.2.14.11.5.1.74.0.0.4 Info hpicfUfdLtDAutoEnabled. Track ID = {1 : hpicfUfdNotifyTrack- Informa-
bled Id : .1.3.6.1.4.1.11.2.14.11.5.1.74.1.1.2}, List of Ports = {2 : hpic- tional
fUfdLinksToTransition : .1.3.6.1.4.1.11.2.14.11.5.1.74.1.2.1.1.4.*} Event
hpicfSnmpAuthFail .1.3.6.1.4.1.11.2.14.11.5.1.38.0.1 Info hpicfSnmpAuthFail. Auth Failure Counter = {1 : hpicfSnmpAuth- Informa-
FailCount : .1.3.6.1.4.1.11.2.14.11.5.1.38.1.2.1}, Auth Failure Src tional
IP Type = {2 : hpicfSnmpAuthFailIP- Event
Type : .1.3.6.1.4.1.11.2.14.11.5.1.38.1.2.2}, Auth Failure Src IP =
{3 : hpicfSnmpAuthFailIP : .1.3.6.1.4.1.11.2.14.11.5.1.38.1.2.3}
hpicfSyslogStatu- .1.3.6.1.4.1.11.2.14.14.1.0.1 Info hpicfSyslogStatusChanged. Syslog Application Index = {1 : hpicf- Informa-
sChanged SyslogControlIndex : .1.3.6.1.4.1.11.2.14.14.1.1.1.1.1.*}, Syslog tional
Application User = {2 : hpicfSyslogControl- Event
Descr : .1.3.6.1.4.1.11.2.14.14.1.1.1.1.2.*}, Syslog Receiver IP
Type = {3 : hpicfSyslogControlBindAddr-
Type : .1.3.6.1.4.1.11.2.14.14.1.1.1.1.3.*}, Syslog Receiver IP =
{4 : hpicfSyslogControlBin-
dAddr : .1.3.6.1.4.1.11.2.14.14.1.1.1.1.4.*}, Row Status = {5 :
hpicfSyslogControlRowSta-
tus : .1.3.6.1.4.1.11.2.14.14.1.1.1.1.5.*}, Priority Description = {6 :
hpicfSyslogPriorityDescr : .1.3.6.1.4.1.11.2.14.14.1.1.3.3}, Severi-
ty = {7 : hpicfSyslogPrioritySeveri-
ty : .1.3.6.1.4.1.11.2.14.14.1.1.3.2}, Facility = {8 : hpicfSyslog-
PriorityFacility : .1.3.6.1.4.1.11.2.14.14.1.1.3.1}, System Module =
{9 : hpicfSyslogSystemModule : .1.3.6.1.4.1.11.2.14.14.1.1.3.4},
Operation Status = {10 : hpicfSyslogOperationsSta-
tus : .1.3.6.1.4.1.11.2.14.14.1.1.2.8}

257
MN002730A01-AD
Appendix E: Alarms and events

Event Name Event ID Se- Event/Alarm Message Event

veri- Catego-
ty ry
hpStackPortChange .1.3.6.1.4.1.11.2.14.11.5.1.69.0.1 Info hpStackPortChange. Member Id for Trap = {1 : hpStackMember- Informa-
IdForTrap : .1.3.6.1.4.1.11.2.14.11.5.1.69.1.3.1.13.*}, Port Index tional
for Trap = {2 : hpStackPortIdFor- Event
Trap : .1.3.6.1.4.1.11.2.14.11.5.1.69.1.5.1.6.*}, Port Type for Trap
= {3 : hpStackPortTypeFor-
Trap : .1.3.6.1.4.1.11.2.14.11.5.1.69.1.5.1.7.*}, Port Operating
Status = {4 : hpStackPortOperSta-
tus : .1.3.6.1.4.1.11.2.14.11.5.1.69.1.5.1.3.*}, Port Neighbor = {5 :
hpStackPortNeighbor : .1.3.6.1.4.1.11.2.14.11.5.1.69.1.5.1.4.*}
hpStackCommander- .1.3.6.1.4.1.11.2.14.11.5.1.69.0.2 Info hpStackCommanderChange. Member Id for Trap = {1 : hpStack- Informa-
Change MemberIdForTrap : .1.3.6.1.4.1.11.2.14.11.5.1.69.1.3.1.13.*}, tional
Member State = {2 : hpStackMember- Event
State : .1.3.6.1.4.1.11.2.14.11.5.1.69.1.3.1.9.*}
hpStackMember- .1.3.6.1.4.1.11.2.14.11.5.1.69.0.3 Info hpStackMemberChange. Member Id for Trap = {1 : hpStackMem- Informa-
Change berIdForTrap : .1.3.6.1.4.1.11.2.14.11.5.1.69.1.3.1.13.*}, Member tional
State = {2 : hpStackMember- Event
State : .1.3.6.1.4.1.11.2.14.11.5.1.69.1.3.1.9.*}
hpStackMemberStatu- .1.3.6.1.4.1.11.2.14.11.5.1.69.0.4 Info hpStackMemberStatusChange. Member Id for Trap = {1 : Informa-
sChange hpStackMemberIdFor- tional
Trap : .1.3.6.1.4.1.11.2.14.11.5.1.69.1.3.1.13.*}, Base MAC = {2 : Event
hpSwitchBaseMACAddress : .1.3.6.1.4.1.11.2.14.11.5.1.1.6},
Member State = {3 : hpStackMember-
State : .1.3.6.1.4.1.11.2.14.11.5.1.69.1.3.1.9.*}
hpStackMergeFailed .1.3.6.1.4.1.11.2.14.11.5.1.69.0.5 Info hpStackMergeFailed. Member Id for Trap = {1 : hpStackMember- Informa-
IdForTrap : .1.3.6.1.4.1.11.2.14.11.5.1.69.1.3.1.13.*}, Member tional
State = {2 : hpStackMember- Event
State : .1.3.6.1.4.1.11.2.14.11.5.1.69.1.3.1.9.*}, Stack Id = {3 :
hpStackId : .1.3.6.1.4.1.11.2.14.11.5.1.69.1.1.1}
hpStackMergeSuc- .1.3.6.1.4.1.11.2.14.11.5.1.69.0.6 Info hpStackMergeSuccess. Member Id for Trap = {1 : hpStackMem- Informa-
cess berIdForTrap : .1.3.6.1.4.1.11.2.14.11.5.1.69.1.3.1.13.*}, Member tional
State = {2 : hpStackMember- Event
State : .1.3.6.1.4.1.11.2.14.11.5.1.69.1.3.1.9.*}, Stack Id = {3 :
hpStackId : .1.3.6.1.4.1.11.2.14.11.5.1.69.1.1.1}

258
 MN002730A01-AD
Appendix E: Alarms and events

Event Name Event ID Se- Event/Alarm Message Event

veri- Catego-
ty ry
hpSwitchStartupCon- .1.3.6.1.4.1.11.2.14.11.5.1.7.1.29.1.0.6 Info hpSwitchStartupConfigChange. Startup Config Sequential Num- Informa-
figChange ber = {1 : hpSwitchStartupConfigSeq- tional
Num : .1.3.6.1.4.1.11.2.14.11.5.1.7.1.29.1.9}, Method of Startup Event
Config change = {2 : hpSwitchStartupConfig-
Source : .1.3.6.1.4.1.11.2.14.11.5.1.7.1.29.1.0.1}, Network Agent
Source IP Type = {3 : hpSwitchStartupConfigSourceIPAddr-
Type : .1.3.6.1.4.1.11.2.14.11.5.1.7.1.29.1.0.2}, Network Agent
Source IP = {4 : hpSwitchStartupConfigSourceI-
PAddr : .1.3.6.1.4.1.11.2.14.11.5.1.7.1.29.1.0.3}, CLI User = {5 :
hpSwitchStartupConfigSourceUser-
name : .1.3.6.1.4.1.11.2.14.11.5.1.7.1.29.1.0.4}, Notification
Throttle = {6 : hpSwitchStartupConfigThrot-
tled : .1.3.6.1.4.1.11.2.14.11.5.1.7.1.29.1.0.5}
hpSwitchRunningCon- .1.3.6.1.4.1.11.2.14.11.5.1.7.1.29.1.0.7 Info hpSwitchRunningConfigChange. Running Config Change Num- Informa-
figChange ber = {1 : hpSwitchRunningCfgChgEven- tional
tId : .1.3.6.1.4.1.11.2.14.11.5.1.7.1.29.1.12.6.1.2.*}, Method of Event
Running Config change = {2 : hpSwitchRunningCfgChgEventMe-
thod : .1.3.6.1.4.1.11.2.14.11.5.1.7.1.29.1.12.6.1.3.*}, Network
Agent Source IP Type = {3 : hpSwitchRunningCfgChgEventSour-
ceIPAddrType : .1.3.6.1.4.1.11.2.14.11.5.1.7.1.29.1.12.6.1.4.*},
Network Agent Source IP = {4 : hpSwitchRunningCfgChgEvent-
SourceIPAddr : .1.3.6.1.4.1.11.2.14.11.5.1.7.1.29.1.12.6.1.5.*},
CLI User = {5 : hpSwitchRunningCfgChgEventUser-
name : .1.3.6.1.4.1.11.2.14.11.5.1.7.1.29.1.12.6.1.6.*}, Date and
Time of the Change = {6 : hpSwitchRunningCfgChgEventDa-
teAndTime : .1.3.6.1.4.1.11.2.14.11.5.1.7.1.29.1.12.6.1.7.*}
hpicfRpvstErrantBp- .1.3.6.1.4.1.11.2.14.11.5.1.88.0.11 Info VLAN instance to which BPDU belongs = {1 : hpicfRpvstVlanIn- Informa-
duReceived dex : .1.3.6.1.4.1.11.2.14.11.5.1.88.0.6}, Port ID on which BPDU tional
received = {2 : hpicfRpvstPortNum- Event
ber : .1.3.6.1.4.1.11.2.14.11.5.1.88.0.7}, Total number of errant
BPDU received on the port which belongs to VLAN hpicfRpvstV-
lanId = {3 : hpicfRpvstPortVlanErrantBpduRx-
Count : .1.3.6.1.4.1.11.2.14.11.5.1.88.1.5.1.22}, State of this port
= {4 : hpicfRpvstPortVlan-
State : .1.3.6.1.4.1.11.2.14.11.5.1.88.1.4.1.5}, Designated Bridge
that transmitted this BPDU = {5 : hpicfRpvstPortVlanDesig-
Bridge : .1.3.6.1.4.1.11.2.14.11.5.1.88.1.4.1.6}, Designated port

259
MN002730A01-AD
Appendix E: Alarms and events

Event Name Event ID Se- Event/Alarm Message Event

veri- Catego-
ty ry
of the Bridge that transmitted this BPDU = {6 : hpicfRpvstDe-
signatedPort : .1.3.6.1.4.1.11.2.14.11.5.1.88.0.5}, Source MAC
address of the port sending this Errant trap = {7 : hpicfRpvstEr-
rantBpduSrcMac : .1.3.6.1.4.1.11.2.14.11.5.1.88.0.2}, The identifi-
er of the feature generating Errant BPDU Trap = {8 : hpicfRpv-
stErrantBpduDetector : .1.3.6.1.4.1.11.2.14.11.5.1.88.0.1}
hpicfRpvstNewRoot .1.3.6.1.4.1.11.2.14.11.5.1.88.0.12 Info VLAN instance in which new root is elected = {1 : hpicfRpvstVla- Informa-
nIndex : .1.3.6.1.4.1.11.2.14.11.5.1.88.0.6}, Bridge ID of the new tional
root elected = {2 : hpicfRpvstNewRootBridg- Event
eId : .1.3.6.1.4.1.11.2.14.11.5.1.88.0.3}, Bridge ID of the previous
root = {3 : hpicfRpvstPreviousRootBridg-
eId : .1.3.6.1.4.1.11.2.14.11.5.1.88.0.4}, Time when the root
bridge changed = {4 : hpicfRpvstRootBridgeChangeTimeS-
tamp : .1.3.6.1.4.1.11.2.14.11.5.1.88.0.8}
hpicfRpvstRootGuar- .1.3.6.1.4.1.11.2.14.11.5.1.88.0.13 Info Vlan Instance to which BPDU belongs = {1 : hpicfRpvstVlanIn- Informa-
dInconsistency dex : .1.3.6.1.4.1.11.2.14.11.5.1.88.0.6}, Port ID where root-in- tional
consistency occurred = {2 : hpicfRpvstPortNum- Event
ber : .1.3.6.1.4.1.11.2.14.11.5.1.88.0.7}, The source MAC ad-
dress of the port sending superior BPDU = {3 : hpicfRpvstSuper-
iorBpduSrcMac : .1.3.6.1.4.1.11.2.14.11.5.1.88.0.9}, Port belong-
ing to the Bridge, which transmitted the superior BPDU = {4 :
hpicfRpvstSuperiorBpduSrc-
Port : .1.3.6.1.4.1.11.2.14.11.5.1.88.0.10}
hpicfRpvstLoopGuar- .1.3.6.1.4.1.11.2.14.11.5.1.88.0.14 Info Vlan Instance in which no BPDU received = {1 : hpicfRpvstVla- Informa-
dInconsistency nIndex : .1.3.6.1.4.1.11.2.14.11.5.1.88.0.6}, Port ID where loop- tional
inconsistency occurred = {2 : hpicfRpvstPortNum- Event
ber : .1.3.6.1.4.1.11.2.14.11.5.1.88.0.7}, Designated Bridge this
port was expecting to receive the BPDU = {3 : hpicfRpvstPortV-
lanDesigBridge : .1.3.6.1.4.1.11.2.14.11.5.1.88.1.4.1.6}
hpicfRpvstTopology- .1.3.6.1.4.1.11.2.14.11.5.1.88.0.18 Info hpicfRpvstTopologyChange. Vlan Instance for which topology Informa-
Change change detected = {1 : hpicfRpvstVlanIn- tional
dex : .1.3.6.1.4.1.11.2.14.11.5.1.88.0.6}, Port ID for which topolo- Event
gy change detected = {2 : hpicfRpvstPortNum-
ber : .1.3.6.1.4.1.11.2.14.11.5.1.88.0.7}, Old role of this port be-
fore topology change = {3 : hpicfRpvstOldPor-
tRole : .1.3.6.1.4.1.11.2.14.11.5.1.88.0.15}, New state of this port

260
 MN002730A01-AD
Appendix E: Alarms and events

Event Name Event ID Se- Event/Alarm Message Event

veri- Catego-
ty ry
after topology change = {4 : hpicfRpvstNewPor-
tRole : .1.3.6.1.4.1.11.2.14.11.5.1.88.0.16}, Time at which the
topology change happened for this port = {5 : hpicfRpvstTopo-
ChangeTime : .1.3.6.1.4.1.11.2.14.11.5.1.88.0.17}
hpicfServiceTunnelIf- .1.3.6.1.4.1.11.2.14.11.5.1.100.0.1 Info hpicfServiceTunnelIfUp. Index = {1 : ifIn- Informa-
Up dex : .1.3.6.1.2.1.2.2.1.1.*}, Alias = {2 : ifA- tional
lias : .1.3.6.1.2.1.31.1.1.1.18.*} Event
hpicfServiceTunnelIf- .1.3.6.1.4.1.11.2.14.11.5.1.100.0.2 Info hpicfServiceTunnelIfDown. Index = {1 : ifIn- Informa-
Down dex : .1.3.6.1.2.1.2.2.1.1.*}, Alias = {2 : ifA- tional
lias : .1.3.6.1.2.1.31.1.1.1.18.*}, Service Tunnel down reason = Event
{3 : hpicfServiceTunnelInterfaceDownRea-
son : .1.3.6.1.4.1.11.2.14.11.5.1.100.1.3.1.3.*}
hpicfSmartLinkPort- .1.3.6.1.4.1.11.2.14.11.5.1.96.0.2 Info hpicfSmartLinkPortStateChangeNotification. Group Index = {1 : Informa-
StateChangeNotifica- hpicfSmartLinkNotifyGroupIn- tional
tion dex : .1.3.6.1.4.1.11.2.14.11.5.1.96.0.1}, Master Port State = {2 : Event
hpicfSmartLinkGroupMasterPort-
State : .1.3.6.1.4.1.11.2.14.11.5.1.96.1.4.1.1.*}, Slave Port State
= {3 : hpicfSmartLinkGroupSlavePort-
State : .1.3.6.1.4.1.11.2.14.11.5.1.96.1.4.1.2.*}

E.11
System Advisor Alarms and Events Overview
Events and alarms are reported for the System Advisor and System Advisor subsystems as follows:

E.11.1
System Advisor Alarms and Events
The following entities are covered:

E.11.1.1
Activity State Events
Events are reported for the SA Activity State as follows:

261
MN002730A01-AD
Appendix E: Alarms and events

Event Name Severity Event/Alarm Message Event/Alarm Description Event Category Manager Entity
DeviceStatus * Current device status: Inactive (Dis- System Advisor is inactive. Informational Event Device Status
abled)
DeviceStatus * Current device status: Active (Ena- System Advisor is active. Informational Event Device Status
bled)
DeviceStatus * Current device status: Inactive (Not Local System Advisor is inactive, because it is Informational Event Device Status
Reported) not reported by the system.
DeviceStatus * Current device status: Unknown Activity state of System Advisor is unknown, Informational Event Device Status
(Not Reported) because it is not reported by the system.

E.11.1.2
Application
The following table provides information on all possible events generated against the Application, with the managed object name of
COMMON_APPLICATION_FAULT.

Event ID Severity Event/Alarm Message Event/Alarm Description Event Category

nm_common_application_fault.2.1 Clear ENABLED, NORMAL ENABLED Equipment Alarm
nm_common_application_fault.2.2 Clear ENABLED, USER REQUESTED ENABLED Equipment Alarm
nm_common_application_fault.3.1 Major DISABLED, NORMAL DISABLED Equipment Alarm
nm_common_application_fault.3.2 Major DISABLED, USER REQUESTED DISABLED Equipment Alarm
nm_common_application_fault.4.1 Warning ENABLING, NORMAL ENABLING Equipment Alarm
nm_common_application_fault.4.2 Warning ENABLING, USER REQUESTED ENABLING Equipment Alarm
nm_common_application_fault.5.2 Warning DISABLING, USER REQUESTED DISABLING Equipment Alarm
nm_common_application_fault.5.1 Warning DISABLING, NORMAL DISABLING Equipment Alarm
nm_common_application_fault.6.3 Critical CRITICAL MALFUNCTION, SOFTWARE ERROR CRITICAL MALFUNCTION Equipment Alarm
nm_common_application_fault.6.4 Critical CRITICAL MALFUNCTION, HARDWARE ERROR CRITICAL MALFUNCTION Equipment Alarm
nm_common_application_fault.6.5 Critical CRITICAL MALFUNCTION, COMMUNICATION CRITICAL MALFUNCTION Equipment Alarm
FAILURE
nm_common_application_fault.6.6 Critical CRITICAL MALFUNCTION, NO CONFIGURATION CRITICAL MALFUNCTION Equipment Alarm
nm_common_application_fault.7.3 Major MAJOR MALFUNCTION, SOFTWARE ERROR MAJOR MALFUNCTION Equipment Alarm

262
 MN002730A01-AD
Appendix E: Alarms and events

Event ID Severity Event/Alarm Message Event/Alarm Description Event Category

nm_common_application_fault.7.4 Major MAJOR MALFUNCTION, HARDWARE ERROR MAJOR MALFUNCTION Equipment Alarm
nm_common_application_fault.7.5 Major MAJOR MALFUNCTION, COMMUNICATION FAIL- MAJOR MALFUNCTION Equipment Alarm
URE
nm_common_application_fault.8.3 Minor MINOR MALFUNCTION, SOFTWARE ERROR MINOR MALFUNCTION Equipment Alarm
nm_common_application_fault.8.4 Minor MINOR MALFUNCTION, HARDWARE ERROR MINOR MALFUNCTION Equipment Alarm
nm_common_application_fault.8.5 Minor MINOR MALFUNCTION, COMMUNICATION FAIL- MINOR MALFUNCTION Equipment Alarm
URE
nm_common_application_fault.9.3 Warning WARNING MALFUNCTION, SOFTWARE ERROR WARNING MALFUNCTION Equipment Alarm
nm_common_application_fault.9.4 Warning WARNING MALFUNCTION, HARDWARE ERROR WARNING MALFUNCTION Equipment Alarm
nm_common_application_fault.9.5 Warning WARNING MALFUNCTION, COMMUNICATION WARNING MALFUNCTION Equipment Alarm
FAILURE
nm_common_application_fault.3.3 Major DISABLED, SOFTWARE ERROR DISABLED Equipment Alarm
nm_common_application_fault.10.3 Warning DISABLED STANDBY, SOFTWARE ERROR DISABLED STANDBY Equipment Alarm
nm_common_application_fault.10.2 Clear DISABLED STANDBY, USER REQUESTED DISABLED STANDBY Equipment Alarm
nm_common_application_fault.5.3 Warning DISABLING, SOFTWARE ERROR DISABLING Equipment Alarm

Additional information, if any reported by the device, may be presented at the end of the message.

The following tables lists transient events for the Application

Event ID Severity Event Message Event/Alarm Description

Transient.nm_common_application_fault.1 Critical Unknown Error Unknown Error
Transient.nm_common_application_fault.2 Critical LOW MEMORY DETECTED. Please con- LOW MEMORY DETECTED. Please con-
tact Motorola! tact Motorola!
Transient.nm_common_application_fault.3 Major DNS service not available DNS service not available
Transient.nm_common_application_fault.4 Major DNS lookup failure DNS lookup failure
Transient.nm_common_application_fault.140 Info Connection to EDDI client was abnormally Connection to EDDI client was abnormally
lost. lost.
Transient.nm_common_application_fault.161 Info Scheduled switchover started Scheduled switchover started

263
MN002730A01-AD
Appendix E: Alarms and events

Event ID Severity Event Message Event/Alarm Description

Transient.nm_common_application_fault.162 Clear Scheduled switchover succeeded Scheduled switchover succeeded
Transient.nm_common_application_fault.163 Warning Scheduled switchover cancelled Scheduled switchover cancelled
Transient.nm_common_application_fault.164 Major Scheduled switchover failed Scheduled switchover failed
Transient.nm_common_application_fault.165 Info Scheduled database migration started Scheduled database migration started
Transient.nm_common_application_fault.166 Clear Scheduled database migration succeeded Scheduled database migration succeeded
Transient.nm_common_application_fault.167 Warning Scheduled database migration cancelled Scheduled database migration cancelled
Transient.nm_common_application_fault.168 Major Scheduled database migration failed Scheduled database migration failed
Transient.nm_common_application_fault.171 Clear Standalone database export succeeded Standalone database export succeeded
Transient.nm_common_application_fault.172 Major Standalone database copy failed Standalone database copy failed
Transient.nm_common_application_fault.173 Major Standalone database export failed Standalone database export failed
Transient.nm_common_application_fault.174 Minor Conflicting operations, standalone database Conflicting operations, standalone database
export failed export failed
Transient.nm_common_application_fault.175 Major Standalone database load failed Standalone database load failed
Transient.nm_common_application_fault.182 Info Scheduled Backup Started Scheduled Backup Started
Transient.nm_common_application_fault.183 Clear Scheduled Backup Succeeded Scheduled Backup Succeeded
Transient.nm_common_application_fault.184 Warning Scheduled Backup Interrupted Scheduled Backup Interrupted
Transient.nm_common_application_fault.185 Major Scheduled Backup Failed Scheduled Backup Failed
Transient.nm_common_application_fault.186 Info Manual Backup Started Manual Backup Started
Transient.nm_common_application_fault.187 Clear Manual Backup Succeeded Manual Backup Succeeded
Transient.nm_common_application_fault.188 Warning Manual Backup Interrupted Manual Backup Interrupted
Transient.nm_common_application_fault.189 Major Manual Backup Failed Manual Backup Failed
Transient.nm_common_application_fault.190 Major INITTAB FAILURE INITTAB FAILURE
Transient.nm_common_application_fault.191 Minor Backup incomplete Backup incomplete
Transient.nm_common_application_fault.192 Critical File Error File Error
Transient.nm_common_application_fault.193 Major I/O Error I/O Error
Transient.nm_common_application_fault.194 Warning Unable to complete processing for last inter- Unable to complete processing for last inter-
val val

264
 MN002730A01-AD
Appendix E: Alarms and events

Event ID Severity Event Message Event/Alarm Description

Transient.nm_common_application_fault.195 Warning Maximum job count reached for interval Maximum job count reached for interval
Transient.nm_common_application_fault.196 Warning Trying to create stats file for deleted interval Trying to create stats file for deleted interval
Transient.nm_common_application_fault.197 Critical Operating System Call Error Operating System Call Error
Transient.nm_common_application_fault.198 Critical Database initialization failed Database initialization failed
Transient.nm_common_application_fault.199 Critical Unable to get Zone Information Unable to get Zone Information
Transient.nm_common_application_fault.200 Clear File Error recovered File Error recovered
Transient.nm_common_application_fault.202 Critical Software Error Detected Software Error Detected
Transient.nm_common_application_fault.203 Major Software Error Detected Software Error Detected
Transient.nm_common_application_fault.204 Warning Software Error Detected Software Error Detected
Transient.nm_common_application_fault.205 Warning Software Error Detected Software Error Detected
Transient.nm_common_application_fault.206 Warning Software Error Detected Software Error Detected
Transient.nm_common_application_fault.321 Warning Bar Offline Completed With Warning Bar Offline Completed With Warning
Transient.nm_common_application_fault.331 Warning One or more non-critical services are down. One or more non-critical services are down.
Transient.nm_common_applica- Major DNS Lookup Failed DNS Lookup Failed
tion_fault.1001
Transient.nm_common_applica- Major DNS Unavailable DNS Unavailable
tion_fault.1002
Transient.nm_common_applica- Major Client Authorization Failed Client Authorization Failed
tion_fault.1003
Transient.nm_common_applica- Major PCC Rule Mismatch PCC Rule Mismatch
tion_fault.1004
Transient.nm_common_applica- Major Flow Capacity Reached Flow Capacity Reached
tion_fault.1005
Transient.nm_common_applica- Clear Flow Capacity Reached Clear Flow Capacity Reached Clear
tion_fault.1006
Transient.nm_common_applica- Major CPU Utilization Threshold Exceeded CPU Utilization Threshold Exceeded
tion_fault.1007
Transient.nm_common_applica- Clear CPU Utilization Threshold Exceeded Clear CPU Utilization Threshold Exceeded Clear
tion_fault.1008

265
MN002730A01-AD
Appendix E: Alarms and events

Event ID Severity Event Message Event/Alarm Description

Transient.nm_common_applica- Major Memory Utilization Threshold Exceeded Memory Utilization Threshold Exceeded
tion_fault.1009
Transient.nm_common_applica- Clear Memory Utilization Threshold Exceeded Memory Utilization Threshold Exceeded
tion_fault.1010 Clear Clear
Transient.nm_common_applica- Major Disk Utilization Threshold Exceeded Disk Utilization Threshold Exceeded
tion_fault.1011
Transient.nm_common_applica- Clear Disk Utilization Threshold Exceeded Clear Disk Utilization Threshold Exceeded Clear
tion_fault.1012
Transient.nm_common_applica- Major Network Throughput Threshold Exceeded Network Throughput Threshold Exceeded
tion_fault.1013
Transient.nm_common_applica- Clear Network Throughput Threshold Exceeded Network Throughput Threshold Exceeded
tion_fault.1014 Clear Clear
Transient.nm_common_applica- Clear OSPF Neighbor State Change OSPF Neighbor State Change
tion_fault.1015
Transient.nm_common_applica- Major User Not Provisioned User Not Provisioned
tion_fault.1016
Transient.nm_common_applica- Major IDM Unavailable IDM Unavailable
tion_fault.1017
Transient.nm_common_applica- Clear IDM Unavailable Clear IDM Unavailable Clear
tion_fault.1018
Transient.nm_common_applica- Major Device Activation Threshold Exceeded Device Activation Threshold Exceeded
tion_fault.1019
Transient.nm_common_applica- Clear Device Activation Threshold Exceeded Device Activation Threshold Exceeded
tion_fault.1020 Clear Clear
Transient.nm_common_applica- Warning CDR files have been cleaned due to high CDR files have been cleaned due to high
tion_fault.1201 disk usage. disk usage.
Transient.nm_common_applica- Warning CDR files have been cleaned due to files CDR files have been cleaned due to files not
tion_fault.1202 not being downloaded for too long. being downloaded for too long.

Application Additional Information

The following table provides additional information on the redundancy events displayed against this entity:

266
 MN002730A01-AD
Appendix E: Alarms and events

Event/Alarm Message Severity State Values Cause Values

Redundancy attribute of the entity has changed - {stateText} Info 1-Active This entity does not support causes
2-Standby
3-User Requested Standby

E.11.1.3
DSR Synchronization Object
The following table provides information on all possible events generated against the DSR Synchronization Object, with the managed object name
of DSR_SYNCH_OBJ_FAULT.

Event ID Severity Event/Alarm Message Event/Alarm Descrip- Event Category

tion
nm_dsr_synch_obj_fault.2.1 Clear Data In Sync, Reason: Sync Succeeded Data In Sync Equipment Alarm
nm_dsr_synch_obj_fault.3.3 Major Data Not in Sync, Reason: Redundant Server Application Data Not in Sync Equipment Alarm
version does not match
nm_dsr_synch_obj_fault.3.4 Minor Data Not in Sync, Reason: Redundant Server Application is Data Not in Sync Equipment Alarm
also Active
nm_dsr_synch_obj_fault.3.5 Minor Data Not in Sync, Reason: DSR feature not enabled on the Data Not in Sync Equipment Alarm
Redundant server
nm_dsr_synch_obj_fault.3.6 Minor Data Not in Sync, Reason: Communication Failure with Re- Data Not in Sync Equipment Alarm
dundant Server
nm_dsr_synch_obj_fault.3.7 Minor Data Not in Sync, Reason: Cannot determine Redundant Data Not in Sync Equipment Alarm
Server Status
nm_dsr_synch_obj_fault.3.8 Minor Data Not in Sync, Reason: Secure Key Mismatch Data Not in Sync Equipment Alarm
nm_dsr_synch_obj_fault.3.9 Minor Data Not in Sync, Reason: Skipped sync, previous sync still Data Not in Sync Equipment Alarm
in progress
nm_dsr_synch_obj_fault.3.14 Minor Data Not in Sync, Reason: Could not sync data on the Re- Data Not in Sync Equipment Alarm
dundant server
nm_dsr_synch_obj_fault.3.11 Minor Data Not in Sync, Reason: User cancelled the sync Data Not in Sync Equipment Alarm
nm_dsr_synch_obj_fault.3.12 Major Data Not in Sync, Reason: Software Error Data Not in Sync Equipment Alarm
nm_dsr_synch_obj_fault.3.13 Minor Data Not in Sync, Reason: Synchronization Service Started Data Not in Sync Equipment Alarm

267
MN002730A01-AD
Appendix E: Alarms and events

Event ID Severity Event/Alarm Message Event/Alarm Descrip- Event Category

tion
nm_dsr_synch_obj_fault.1.2 Clear Sync Incapable, Reason: DSR Feature not enabled on this Sync Incapable Equipment Alarm
server
nm_dsr_synch_obj_fault.4.10 Clear Server capable of being synced by Active, Reason: This Server capable of being Equipment Alarm
server is a Standby server synced by Active
nm_dsr_synch_obj_fault.1.15 Minor Sync Incapable, Reason: Sync service is initializing Sync Incapable Equipment Alarm

Additional information, if any reported by the device, may be presented at the end of the message.

This entity does not define any transient faults.

E.11.1.4
Broker Server Link
The following table provides information on all possible events generated against the Broker Server Link, with the managed object name of
BROKER_SERVER_LINK.

Event ID Severity Event/Alarm Message Event/Alarm Description Event Category

nm_broker_server_link.1.501 Clear UP, LINK UP UP, LINK UP Equipment Alarm
nm_broker_server_link.2.503 Critical DOWN, BROKER PRODUCER FAILURE DOWN, BROKER PRODUCER FAILURE Equipment Alarm
nm_broker_server_link.2.505 Critical DOWN, BROKER PRODUCER SERVICE DOWN, BROKER PRODUCER SERVICE Equipment Alarm
DOWN DOWN
nm_broker_server_link.2.507 Critical DOWN, STATS PROCESSING FAILED DOWN, STATS PROCESSING FAILED Equipment Alarm
nm_broker_server_link.2.9998 Critical DOWN, UNKNOWN DOWN, UNKNOWN Equipment Alarm

Additional information, if any reported by the device, may be presented at the end of the message.

This entity does not define any transient faults.

E.11.1.5
CM Capacity
The following table provides information on all possible events generated against the CM Capacity, with the managed object name of
CM_CAPACITY_FAULT.

268
 MN002730A01-AD
Appendix E: Alarms and events

Event ID Severity Event/Alarm Message Event/Alarm Description Event Catego-

ry
nm_cm_capaci- Clear UNKNOWN, AUDIT WAS NOT RUN UNKNOWN, Audit was not run Equipment
ty_fault.1.1 Alarm
nm_cm_capaci- Clear SYSTEM COMPLIANT, SYSTEM CONFIGU- SYSTEM COMPLIANT, System configuration is Equipment
ty_fault.2.2 RATION IS WITHIN EXPECTED LIMITS within expected limits Alarm
nm_cm_capaci- Warning SYSTEM COMPLIANT, SYSTEM CONFIGU- SYSTEM COMPLIANT, System configuration is Equipment
ty_fault.2.3 RATION IS APPROACHING THE LIMIT. CON- approaching the limit. Contact MSI to consider Alarm
TACT MSI TO CONSIDER EXPANSION expansion
nm_cm_capaci- Critical SYSTEM IN VIOLATION, SYSTEM CONFIGU- SYSTEM IN VIOLATION, System configuration Equipment
ty_fault.3.4 RATION HAS EXCEEDED MAXIMUM LIMIT. has exceeded maximum limit. Contact MSI to Alarm
CONTACT MSI TO PLAN EXPANSION plan expansion
nm_cm_capaci- Warning UNKNOWN, AUDIT FAILED TO RUN UNKNOWN, Audit failed to run Equipment
ty_fault.1.5 Alarm

Additional information, if any reported by the device, may be presented at the end of the message.

The following tables lists transient events for the CM Capacity

Event ID Severity Event Message Event/Alarm Description

Transient.nm_cm_capaci- Info THE NUMBER OF MANAGED OBJECTS IS AP- The number of managed objects is approaching the
ty_fault.1 PROACHING THE CAPACITY LIMIT capacity limit

E.11.1.6
Ethernet Card
The following table provides information on all possible events generated against the Ethernet Card, with the managed object name of
SERVER_FRU_ETHERNET_CARD_FAULT.

Event ID Severity Event/Alarm Message Event/Alarm Descrip- Event Category

tion
nm_server_fru_ether- Critical UNKNOWN, NO REASON UNKNOWN Equipment Alarm
net_card_fault.1.1
nm_server_fru_ether- Clear ONLINE, NO PROBLEM ONLINE Equipment Alarm
net_card_fault.2.2

269
MN002730A01-AD
Appendix E: Alarms and events

Event ID Severity Event/Alarm Message Event/Alarm Descrip- Event Category

tion
nm_server_fru_ether- Major OFFLINE, NO PROBLEM OFFLINE Equipment Alarm
net_card_fault.3.2
nm_server_fru_ether- Major OFFLINE, COMPONENT NOT CONFIGURED OFFLINE Equipment Alarm
net_card_fault.3.152
nm_server_fru_ether- Minor INITIALIZATION, NO PROBLEM INITIALIZATION Equipment Alarm
net_card_fault.4.2
nm_server_fru_ether- Minor INITIALIZATION, COMPONENT NOT CONFIGURED INITIALIZATION Equipment Alarm
net_card_fault.4.152
nm_server_fru_ether- Critical FAILURE, A COOLING FAN HAS COMPLETELY FAILURE Equipment Alarm
net_card_fault.5.21 FAILED OR SLOWED DOWN
nm_server_fru_ether- Critical FAILURE, CALL PROCESSING FAILURE FAILURE Equipment Alarm
net_card_fault.5.32
nm_server_fru_ether- Critical FAILURE, INVALID STATE IN CALL PROCESSING FAILURE Equipment Alarm
net_card_fault.5.33
nm_server_fru_ether- Critical FAILURE, ZC INTERNAL COMMUNICATION ERROR FAILURE Equipment Alarm
net_card_fault.5.34
nm_server_fru_ether- Critical FAILURE, POWER SUPPLY FAILURE FAILURE Equipment Alarm
net_card_fault.5.48
nm_server_fru_ether- Critical FAILURE, COULD NOT GET THE STATUS OF POW- FAILURE Equipment Alarm
net_card_fault.5.49 ER SUPPLY
nm_server_fru_ether- Critical FAILURE, PING FAILED ON AT LEAST ONE ETHER- FAILURE Equipment Alarm
net_card_fault.5.66 NET CARD PORT
nm_server_fru_ether- Critical FAILURE, HARD DISK TEST FAILED FAILURE Equipment Alarm
net_card_fault.5.82
nm_server_fru_ether- Critical FAILURE, COMPONENT NOT CONFIGURED FAILURE Equipment Alarm
net_card_fault.5.152

Additional information, if any reported by the device, may be presented at the end of the message.

This entity does not define any transient faults.

270
 MN002730A01-AD
Appendix E: Alarms and events

E.11.1.7
Fan
The following table provides information on all possible events generated against the Fan, with the managed object name of
SERVER_FRU_FAN_FAULT.

Event ID Severity Event/Alarm Message Event/Alarm Descrip- Event Category

tion
nm_server_fru_fan_fault.1.1 Critical UNKNOWN, NO REASON UNKNOWN Equipment Alarm
nm_server_fru_fan_fault.2.2 Clear ONLINE, NO PROBLEM ONLINE Equipment Alarm
nm_server_fru_fan_fault.3.2 Major OFFLINE, NO PROBLEM OFFLINE Equipment Alarm
nm_server_fru_fan_fault.3.152 Major OFFLINE, COMPONENT NOT CONFIGURED OFFLINE Equipment Alarm
nm_server_fru_fan_fault.4.2 Minor INITIALIZATION, NO PROBLEM INITIALIZATION Equipment Alarm
nm_server_fru_fan_fault.4.152 Minor INITIALIZATION, COMPONENT NOT CONFIGURED INITIALIZATION Equipment Alarm
nm_server_fru_fan_fault.5.21 Critical FAILURE, A COOLING FAN HAS COMPLETELY FAILED FAILURE Equipment Alarm
OR SLOWED DOWN
nm_server_fru_fan_fault.5.32 Critical FAILURE, CALL PROCESSING FAILURE FAILURE Equipment Alarm
nm_server_fru_fan_fault.5.33 Critical FAILURE, INVALID STATE IN CALL PROCESSING FAILURE Equipment Alarm
nm_server_fru_fan_fault.5.34 Critical FAILURE, ZC INTERNAL COMMUNICATION ERROR FAILURE Equipment Alarm
nm_server_fru_fan_fault.5.48 Critical FAILURE, POWER SUPPLY FAILURE FAILURE Equipment Alarm
nm_server_fru_fan_fault.5.49 Critical FAILURE, COULD NOT GET THE STATUS OF POWER FAILURE Equipment Alarm
SUPPLY
nm_server_fru_fan_fault.5.66 Critical FAILURE, PING FAILED ON AT LEAST ONE ETHERNET FAILURE Equipment Alarm
CARD PORT
nm_server_fru_fan_fault.5.82 Critical FAILURE, HARD DISK TEST FAILED FAILURE Equipment Alarm
nm_server_fru_fan_fault.5.152 Critical FAILURE, COMPONENT NOT CONFIGURED FAILURE Equipment Alarm

Additional information, if any reported by the device, may be presented at the end of the message.

This entity does not define any transient faults.

271
MN002730A01-AD
Appendix E: Alarms and events

E.11.1.8
Hard Disk
The following table provides information on all possible events generated against the Hard Disk, with the managed object name of
SERVER_FRU_HARDDISK_FAULT.

Event ID Severity Event/Alarm Message Event/Alarm Descrip- Event Category

tion
nm_server_fru_harddisk_fault.1.1 Critical UNKNOWN, NO REASON UNKNOWN Equipment Alarm
nm_server_fru_harddisk_fault.2.2 Clear ONLINE, NO PROBLEM ONLINE Equipment Alarm
nm_server_fru_harddisk_fault.3.2 Major OFFLINE, NO PROBLEM OFFLINE Equipment Alarm
nm_server_fru_hard- Major OFFLINE, COMPONENT NOT CONFIGURED OFFLINE Equipment Alarm
disk_fault.3.152
nm_server_fru_harddisk_fault.4.2 Minor INITIALIZATION, NO PROBLEM INITIALIZATION Equipment Alarm
nm_server_fru_hard- Minor INITIALIZATION, COMPONENT NOT CONFIGURED INITIALIZATION Equipment Alarm
disk_fault.4.152
nm_server_fru_hard- Critical FAILURE, A COOLING FAN HAS COMPLETELY FAILURE Equipment Alarm
disk_fault.5.21 FAILED OR SLOWED DOWN
nm_server_fru_hard- Critical FAILURE, CALL PROCESSING FAILURE FAILURE Equipment Alarm
disk_fault.5.32
nm_server_fru_hard- Critical FAILURE, INVALID STATE IN CALL PROCESSING FAILURE Equipment Alarm
disk_fault.5.33
nm_server_fru_hard- Critical FAILURE, ZC INTERNAL COMMUNICATION ERROR FAILURE Equipment Alarm
disk_fault.5.34
nm_server_fru_hard- Critical FAILURE, POWER SUPPLY FAILURE FAILURE Equipment Alarm
disk_fault.5.48
nm_server_fru_hard- Critical FAILURE, COULD NOT GET THE STATUS OF POWER FAILURE Equipment Alarm
disk_fault.5.49 SUPPLY
nm_server_fru_hard- Critical FAILURE, PING FAILED ON AT LEAST ONE ETHER- FAILURE Equipment Alarm
disk_fault.5.66 NET CARD PORT
nm_server_fru_hard- Critical FAILURE, HARD DISK TEST FAILED FAILURE Equipment Alarm
disk_fault.5.82
nm_server_fru_hard- Critical FAILURE, COMPONENT NOT CONFIGURED FAILURE Equipment Alarm
disk_fault.5.152

272
 MN002730A01-AD
Appendix E: Alarms and events

Additional information, if any reported by the device, may be presented at the end of the message.

This entity does not define any transient faults.

E.11.1.9
Power Supply
The following table provides information on all possible events generated against the Power Supply, with the managed object name of
SERVER_FRU_POWER_SUPPLY_FAULT.

Event ID Severity Event/Alarm Message Event/Alarm Descrip- Event Category

tion
nm_server_fru_power_sup- Critical UNKNOWN, NO REASON UNKNOWN Equipment Alarm
ply_fault.1.1
nm_server_fru_power_sup- Clear ONLINE, NO PROBLEM ONLINE Equipment Alarm
ply_fault.2.2
nm_server_fru_power_sup- Major OFFLINE, NO PROBLEM OFFLINE Equipment Alarm
ply_fault.3.2
nm_server_fru_power_sup- Major OFFLINE, COMPONENT NOT CONFIGURED OFFLINE Equipment Alarm
ply_fault.3.152
nm_server_fru_power_sup- Minor INITIALIZATION, NO PROBLEM INITIALIZATION Equipment Alarm
ply_fault.4.2
nm_server_fru_power_sup- Minor INITIALIZATION, COMPONENT NOT CONFIGURED INITIALIZATION Equipment Alarm
ply_fault.4.152
nm_server_fru_power_sup- Critical FAILURE, A COOLING FAN HAS COMPLETELY FAILURE Equipment Alarm
ply_fault.5.21 FAILED OR SLOWED DOWN
nm_server_fru_power_sup- Critical FAILURE, CALL PROCESSING FAILURE FAILURE Equipment Alarm
ply_fault.5.32
nm_server_fru_power_sup- Critical FAILURE, INVALID STATE IN CALL PROCESSING FAILURE Equipment Alarm
ply_fault.5.33
nm_server_fru_power_sup- Critical FAILURE, ZC INTERNAL COMMUNICATION ERROR FAILURE Equipment Alarm
ply_fault.5.34
nm_server_fru_power_sup- Critical FAILURE, POWER SUPPLY FAILURE FAILURE Equipment Alarm
ply_fault.5.48

273
MN002730A01-AD
Appendix E: Alarms and events

Event ID Severity Event/Alarm Message Event/Alarm Descrip- Event Category

tion
nm_server_fru_power_sup- Critical FAILURE, COULD NOT GET THE STATUS OF POW- FAILURE Equipment Alarm
ply_fault.5.49 ER SUPPLY
nm_server_fru_power_sup- Critical FAILURE, PING FAILED ON AT LEAST ONE ETHER- FAILURE Equipment Alarm
ply_fault.5.66 NET CARD PORT
nm_server_fru_power_sup- Critical FAILURE, HARD DISK TEST FAILED FAILURE Equipment Alarm
ply_fault.5.82
nm_server_fru_power_sup- Critical FAILURE, COMPONENT NOT CONFIGURED FAILURE Equipment Alarm
ply_fault.5.152

Additional information, if any reported by the device, may be presented at the end of the message.
This entity can have multiple instances in following format:Power Supply<entity instance id>, for example:Power Supply1.

This entity does not define any transient faults.

E.11.2
Application Service Alarms and Events
The following entities are covered:

E.11.2.1
Application Service
The following table provides information on all possible events generated against the Application Service, with the managed object name of
APPLICATION_SERVICE_FAULT.

Event ID Severity Event/Alarm Message Event/Alarm Description Event Category

nm_application_service_fault.1.1 Clear Service Starting, Normal Service Starting Equipment Alarm
nm_application_service_fault.2.1 Clear Service Operational, Normal Service Operational Equipment Alarm
nm_application_service_fault.3.2 Critical Service Malfunction, Internal database error Service Malfunction Equipment Alarm
nm_application_service_fault.4.4 Clear Service Disabled, User initiated Service Disabled Equipment Alarm
nm_application_service_fault.3.3 Critical Service Malfunction, Internal database unavailable Service Malfunction Equipment Alarm
nm_application_service_fault.3.5 Critical Service Malfunction, Data link down Service Malfunction Equipment Alarm

274
 MN002730A01-AD
Appendix E: Alarms and events

Additional information, if any reported by the device, may be presented at the end of the message.

This entity does not define any transient faults.

E.11.2.2
Database Service
The following table provides information on all possible events generated against the Database Service, with the managed object name of
DATABASE_SERVICE_FAULT.

Event ID Severity Event/Alarm Message Event/Alarm Description Event Category

nm_database_service_fault.1.1 Clear Service Starting, Normal Service Starting Equipment Alarm
nm_database_service_fault.2.1 Clear Service Operational, Normal Service Operational Equipment Alarm
nm_database_service_fault.3.2 Critical Service Malfunction, Internal database error Service Malfunction Equipment Alarm
nm_database_service_fault.4.4 Clear Service Disabled, User initiated Service Disabled Equipment Alarm
nm_database_service_fault.3.3 Critical Service Malfunction, Internal database unavailable Service Malfunction Equipment Alarm

Additional information, if any reported by the device, may be presented at the end of the message.

This entity does not define any transient faults.

E.11.2.3
JVM Service
The following table provides information on all possible events generated against the JVM Service, with the managed object name of
JVM_SERVICE_FAULT.

Event ID Severity Event/Alarm Message Event/Alarm Description Event Category

nm_jvm_service_fault.1.1 Clear Service Starting, Normal Service Starting Equipment Alarm
nm_jvm_service_fault.2.1 Clear Service Operational, Normal Service Operational Equipment Alarm
nm_jvm_service_fault.4.2 Clear Service Disabled, User initiated Service Disabled Equipment Alarm
nm_jvm_service_fault.3.3 Critical Service Malfunction, JVM Memory Limit Exceeded Service Malfunction Equipment Alarm
nm_jvm_service_fault.3.4 Critical Service Malfunction, JVM Threads Limit Exceeded Service Malfunction Equipment Alarm

275
MN002730A01-AD
Appendix E: Alarms and events

Additional information, if any reported by the device, may be presented at the end of the message.
This entity can have multiple instances in following format:JVM Service<entity instance id>, for example:JVM Service1.

This entity does not define any transient faults.

E.11.2.4
Processing Queue
The following table provides information on all possible events generated against the Processing Queue, with the managed object name of
PROCESSING_QUEUE_FAULT.

Event ID Severity Event/Alarm Message Event/Alarm Description Event Category

nm_processing_queue_fault.1.1 Clear Service Starting, Normal Service Starting Equipment Alarm
nm_processing_queue_fault.2.1 Clear Service Operational, Normal Service Operational Equipment Alarm
nm_processing_queue_fault.4.2 Clear Service Disabled, User initiated Service Disabled Equipment Alarm
nm_processing_queue_fault.3.3 Critical Service Malfunction, Alerts Queue Limit Exceeded Service Malfunction Equipment Alarm
nm_processing_queue_fault.3.4 Critical Service Malfunction, Events Queue Limit Exceeded Service Malfunction Equipment Alarm
nm_processing_queue_fault.3.5 Critical Service Malfunction, Traps Queue Limit Exceeded Service Malfunction Equipment Alarm

Additional information, if any reported by the device, may be presented at the end of the message.
This entity can have multiple instances in following format:Processing Queue<entity instance id>, for example:Processing Queue1.

This entity does not define any transient faults.

E.11.2.5
NCM Service
The following table provides information on all possible events generated against the NCM Service, with the managed object name of
NCM_SERVICE_FAULT.

Event ID Severity Event/Alarm Message Event/Alarm Description Event Category

nm_ncm_service_fault.2.1 Clear Service Operational, Normal Service Operational Equipment Alarm
nm_ncm_service_fault.4.2 Critical Service Disabled, Error Service Disabled Equipment Alarm

276
 MN002730A01-AD
Appendix E: Alarms and events

Additional information, if any reported by the device, may be presented at the end of the message.

This entity does not define any transient faults.

E.11.2.6
Call Monitoring Service
The following table provides information on all possible events generated against the Call Monitoring Service, with the managed object name of
CM_SERVICE_FAULT.

Event ID Severity Event/Alarm Message Event/Alarm Description Event Category

nm_cm_service_fault.2.1 Clear Service Operational, Normal Service Operational Equipment Alarm
nm_cm_service_fault.4.2 Critical Service Disabled, Error Service Disabled Equipment Alarm

Additional information, if any reported by the device, may be presented at the end of the message.

This entity does not define any transient faults.

E.11.2.7
Config Service
The following table provides information on all possible events generated against the Config Service, with the managed object name of
CONFIG_SERVICE_FAULT.

Event ID Severity Event/Alarm Message Event/Alarm Description Event Category

nm_config_service_fault.2.1 Clear Service Operational, Normal Service Operational Equipment Alarm
nm_config_service_fault.4.2 Critical Service Disabled, Error Service Disabled Equipment Alarm

Additional information, if any reported by the device, may be presented at the end of the message.

This entity does not define any transient faults.

E.12
Repeater Alarms and Events Overview
Events and alarms are reported for the Repeater as follows:

277
MN002730A01-AD
Appendix E: Alarms and events

E.12.1
Repeater Alarms
Alarms are reported for the Repeater as follows:

Event Name Severity Event/Alarm Message Event/Alarm Description Event Cate-

TransmitAlarm * Transmit Alarm
ReceiveAlarm * Receive Alarm
TemperatureAlarm * Temperature Alarm
AcPowerAlarm * AC Power Alarm
PaFanAlarm * PA Fan Alarm
PaEepromCorruptionType1 * PA EEPROM Corruption
Type 1
PaEepromCorruptionType2 * PA EEPROM Corruption
Type 2
PaEepromCorruptionType3 * PA EEPROM Corruption
Type 3
ExciterEepromCorruption- * Exciter EEPROM Corrup-
Type1 tion Type 1
ExciterEepromCorruption- * Exciter EEPROM Corrup-
Type2 tion Type 2
gory
The exciter PLL has lost lock. Equipment
Alarm
The receiver Phase Locked Loop (PLL) has lost lock. Equipment
Alarm
The station has exceeded the temperature limit that will allow Equipment
maximum rated output power from the PA. Alarm
The station is not at fault. The AC power source has been in- Equipment
terrupted and the station is operating on DC power. Alarm
The PA fan has failed. Equipment
Alarm
The PA EEPROM has incurred nonrecoverable corruption in Equipment
a semicritical memory location. Note: This alarm is only appli- Alarm
cable to the MTR3000 PA which is important to note in
MTR2000 Upgrades.
The PA EEPROM has incurred recoverable corruption in a Equipment
critical memory location or non-recoverable corruption in a Alarm
noncritical area of memory. Note: This alarm is only applica-
ble to the MTR3000 PA which is important to note in
MTR2000 Upgrades.
The PA EEPROM has incurred nonrecoverable corruption in Equipment
a critical memory location. Note: This alarm is only applicable Alarm
to the MTR3000 PA which is important to note in MTR2000
Upgrades.
The exciter EEPROM has incurred nonrecoverable corruption Equipment
in a semicritical memory location. Alarm
The exciter EEPROM has incurred recoverable corruption in Equipment
a critical memory location or non-recoverable corruption in a Alarm
noncritical area of memory. No action needed. This is infor-
mational only.

278
 MN002730A01-AD
Appendix E: Alarms and events

Event Name Severity Event/Alarm Message Event/Alarm Description Event Cate-

gory
ExciterEepromCorruption- * Exciter EEPROM Corrup- The exciter EEPROM has incurred nonrecoverable corruption Equipment
Type3 tion Type 3 in a critical memory location. Alarm
ReceiverEepromCorruption- * Receiver EEPROM Corrup- The receiver EEPROM has incurred nonrecoverable corrup- Equipment
Type1 tion Type 1 tion in a semicritical memory location. Alarm
ReceiverEepromCorruption- * Receiver EEPROM Corrup- The receiver EEPROM has incurred a recoverable corruption Equipment
Type2 tion Type 2 in critical memory location or non-recoverable corruption in a Alarm
noncritical area of memory. No action needed. This is infor-
mational only.
ReceiverEepromCorruption- * Receiver EEPROM Corrup- The receiver EEPROM has incurred nonrecoverable corrup- Equipment
Type3 tion Type 3 tion in a critical memory location. Alarm
PaHighTemperature * PA high temperature failure PA_OVERHEATING PA high temperature failure. Equipment
Alarm
PaVoltageAlarmHigh * PA Voltage Alarm (High) The station is not at fault. This alarm occurs when the station Equipment
is operating from a DC source with an output voltage that is Alarm
too high to sustain the maximum rated output power from the
PA.
PaVoltageMinorAlarmInter- * PA Voltage Minor Alarm (In- The station is not at fault. This alarm occurs when the station Equipment
mediate termediate) is operating from a DC source with an output voltage that can Alarm
not sustain the maximum rated output power from the PA.
PaVoltageAlarmLow * PA Voltage Alarm (Low) The station is not at fault. This alarm occurs when the station Equipment
is operating from a DC source that has an output voltage Alarm
which is too low to sustain any level of output power from the
PA.
VswrMinorAlarm * VSWR Minor Alarm The Voltage Standing Wave Ratio (VSWR), of the equipment Equipment
the station is coupled to, is between a 3:1 to 5:1. The station Alarm
has rolled power back to protect the PA.
VswrMajorAlarm * VSWR Major Alarm The Voltage Standing Wave Ratio (VSWR), of the equipment Equipment
the station is coupled to, is greater than a 5:1. The station Alarm
has rolled power back to protect the PA.
PowerRollbackAlarm(2dB) * Power Roll-back Alarm The PA output power is between 2dB to 3dB below the set Equipment
(2dB) output power of the station. Alarm
PowerRollbackAlarm(3dB) * Power Roll-back Alarm The PA output power is more than 3dB below the set output Equipment
(3dB) power of the station, but at least one of the following "pri- Alarm

279
MN002730A01-AD
Appendix E: Alarms and events
Event Name
PowerUnleveledAlarm
InteroperabilityBetweenEx-
citerAndPa
IncorrectCarrierFrequency
IncorrectCodeplug-
ForMTR2000Pa
ReferenceUnlock
CirculatorTemperatureAlarm *
OcxoFailure
ExciterDriverAmpAlarm
ExciterFinalAmpAlarm
8vSupplyAlarm
10vSupplyAlarm
RfPowerControlAlarm
280
Severity Event/Alarm Message
* Power Unleveled Alarm
* Interoperability Between Ex- The PA and exciter do not have a compatible frequency
citer and PA
* Incorrect Carrier Frequency At least one personality (analog or digital channel) exists in Equipment
* Incorrect Codeplug for
MTR2000 PA
* Reference Unlock (External "1)External reference is not connected or does not match
Only)
Circulator Temperature
Alarm
* OCXO Failure
* Exciter Driver Amp Alarm
* Exciter Final Amp Alarm
* 8 Volt Supply Alarm
* 10 Volt Supply Alarm
* RF Power Control Alarm
Event/Alarm Description Event Cate-
gory
mary" alarms is also present: Fan Alarm, Temp Alarm, PA
Voltage Minor Alarm, PA Voltage Major Alarm, VSWR Minor
Alarm, or VSWR Major Alarm.
The PA output power is more than 3dB below the set output Equipment
power. Alarm
Equipment
range with each other. Alarm
the codeplug which has a frequency outside of the supported Alarm
electronic bandwidth of the receiver, exciter, or PA.
The MTR3000 codeplug contains an unsupported MTR2000 Equipment
PA. Alarm
Equipment
what is programmed, reference cannot lock to external refer- Alarm
ence 2)May not be fault of station...possibly a fault with the
external reference.".
Mistuned circulator or bad antenna VSWR. Equipment
Alarm
A standard stability reference (1.5ppm) System Clock Module Equipment
(SCM) has been installed into a 800/900MHz station. Note: Alarm
This alarm is only applicable to 800/900 MHz stations.
The current draw of the exciter's driver stage is outside of Equipment
specification. Alarm
The current draw of the exciter's final stage is outside of Equipment
specification. Alarm
The 8 volt backplane linear regulator is delivering a potential Equipment
outside of its specified range. Alarm
The 10 volt backplane linear regulator is delivering a potential Equipment
outside of its specified range. Alarm
The transmitter is delivering power in a dekeyed state or de- Equipment
livering more power in a keyed state than tolerancing allows. Alarm
 MN002730A01-AD
Appendix E: Alarms and events

Event Name Severity Event/Alarm Message Event/Alarm Description Event Cate-

gory
PaGainAlarm * PA Gain Alarm The PA power control loop is near saturation or in saturation. Equipment
Alarm
ExternalCirculatorTempA- * External Circulator Temp A high VSWR is present aft the external double circulator tray Equipment
larm Alarm option. Alarm
PaNvmRevisionIncompati- * PA NVM Revision Incom- The PA hardware is incompatible with the currently loaded Equipment
ble patible firmware version. Alarm
TxNvmRevisionIncompatible * TX NVM Revision Incom- The exciter hardware is incompatible with the currently load- Equipment
patible ed firmware version. Alarm
RxNvmRevisionIncompati- * RX NVM Revision Incom- The receiver hardware is incompatible with the currently load- Equipment
ble patible ed firmware version. Alarm
RasFailure * RAS Failure RAS Failure mode alarm. Equipment
Alarm
ReferenceUnlockInternal- * Reference Unlock - Internal "1) External reference does not match what is programmed, Equipment
Fallback Fall Back reference cannot lock to external reference however the sta- Alarm
tion can run on internal clock 2) May not be the fault of the
station, could be fault with external reference".
ModemModuleIDAlarm * Modem Module ID Alarm EEProm Corrupted...data not valid in terms of hardware ID. Equipment
Alarm
PaModuleIDAlarm * PA Module ID Alarm EEProm Corrupted...data not valid in terms of hardware ID. Equipment
Alarm
PaCommunicationFail * PA Communication Fail Indicative of a hardware failure. Equipment
Alarm
PaProgramFail * PA Program Fail Indicative of a hardware failure. Equipment
Alarm
ChasisModuleIDAlarm * Chassis Module ID Alarm "1) Flex cables may not be inserted correctly 2) EEProm Cor- Equipment
rupted...data not valid in terms of hardware ID.". Alarm
PowerSupplyFanAlarm * Power Supply Fan Alarm The Power Supply fan is failing or has failed. Equipment
Alarm
PowerSupplyModuleIdAlarm * Power Supply Module ID EEProm Corrupted...data not valid in terms of hardware ID. Equipment
Alarm Alarm
BadBattery * Bad Battery Battery charger is unable to charge the battery. Equipment
Alarm

281
MN002730A01-AD
Appendix E: Alarms and events

Event Name Severity Event/Alarm Message Event/Alarm Description Event Cate-

gory
BatteryDisconnected * Battery Disconnected Battery is not connected properly. Equipment
Alarm
PsuCommunicationFail * Power Supply Communica- Indicative of a hardware failure. Equipment
tion Failure Alarm
FrontPanelBoardModuleI- * Front Panel Board Module "1) Flex cables may not be inserted correctly 2) EEProm Cor- Equipment
DAlarm ID Alarm rupted...data not valid in terms of hardware ID.". Alarm
ModemFanAlarm * Modem Fan Alarm The Modem fan is failing or has failed. Equipment
Alarm
UserDefinedAlarm1 * User Defined Alarm 1 User Defined. Equipment
Alarm
UserDefinedAlarm2 * User Defined Alarm 2 User Defined. Equipment
Alarm
UserDefinedAlarm3 * User Defined Alarm 3 User Defined. Equipment
Alarm
UserDefinedAlarm4 * User Defined Alarm 4 User Defined. Equipment
Alarm
UserDefinedAlarm5 * User Defined Alarm 5 User Defined. Equipment
Alarm
UserDefinedAlarm6 * User Defined Alarm 6 User Defined. Equipment
Alarm
IllegalCarrierAlarm * Illegal Carrier Alarm The receiver detected an interfering signal. Equipment
Alarm
PsuProgramFail * Power Supply Program Fail- Indicative of a hardware failure. Equipment
ure Alarm
WirelineBoardModuleIDA- * Wireline Board Module ID "1) Flex cables may not be inserted correctly 2) EEProm Cor- Equipment
larm Alarm rupted...data not valid in terms of hardware ID. 3) Option is Alarm
selected in CPS but not used in the station.".
ExpansionBoardModuleIDA- * Expansion Board Module ID "1) Flex cables may not be inserted correctly 2) EEProm Cor- Equipment
larm Alarm rupted...data not valid in terms of hardware ID. 3) Option is Alarm
selected in CPS but not used in the station.".
PsuHwVer * Power Supply Hardware Incorrect PSU hardware installed. Equipment
Version Incorrect Alarm

282
 MN002730A01-AD
Appendix E: Alarms and events

Event Name Severity Event/Alarm Message Event/Alarm Description Event Cate-

gory
FrontPanelCommFailure * Front Panel Board Commu- Front Panel Board Communications Failure. Equipment
nications Failure Alarm
FrontPanelProgramFail * Front Panel Board Program Front Panel Board Program Fail. Equipment
Fail Alarm
PaHwVer * PA Hardware Version Incor- Incorrect PA hardware installed. Equipment
rect Alarm
FrontPanelHwVer * Front Panel Board Hard- Incorrect Front Panel hardware installed. Equipment
ware Version Incorrect Alarm
WirelessHwVer * Wireline Board Hardware Incorrect Wireline hardware installed. Equipment
Version Incorrect Alarm
ChassisHardwareVersionIn- * Chassis Hardware Version Incorrect Chassis hardware installed. Equipment
correct Incorrect Alarm
IncompatibleDcPowerSup- * Incompatible DC Power Wrong battery type or incorrect DC voltage on supply. Equipment
ply Supply Alarm
TransferringRegistrationRe- * Transferring Registration Indicate that Control Channel is transferring Registration Re- Equipment
cords Records cords to TrunkController Alarm
TemperatureAlarm * Temperature Alarm. Modem Modem temperature is ouside specified limits which would al- Equipment
Temperature={value} low rated power to be generated. Alarm
PaVoltageAlarmHigh * PA Voltage Alarm (High). Voltage to PA FRU is outside of specified range. PA will not Equipment
PA Voltage={value} perform up to specifications. Alarm
PaVoltageAlarmLow * PA Voltage Alarm (Low). PA Voltage to PA FRU is outside of specified range. PA will not Equipment
Voltage={value} perform up to specifications. Alarm
VswrMinorAlarm * VSWR Minor Alarm. The Voltage Standing Wave Ratio (VSWR), of the equipment Equipment
VSWR={value} the station is coupled to, is between a 3:1 to 5:1. The station Alarm
has rolled power back to protect the PA.
VswrMajorAlarm * VSWR Major Alarm. The Voltage Standing Wave Ratio (VSWR), of the equipment Equipment
VSWR={value} the station is coupled to, is greater than a 5:1. The station Alarm
has rolled power back to protect the PA.
PowerRollbackAlarm(2dB) * Power Roll-back Alarm The PA output power is between 2dB to 3dB below the set Equipment
(2dB). Output Power={val- output power of the station, at least one of the following "pri- Alarm
ue} mary" alarms may also present: any Fan Alarm, any Temp

283
MN002730A01-AD
Appendix E: Alarms and events

Event Name Severity Event/Alarm Message Event/Alarm Description Event Cate-

PowerRollbackAlarm(3dB)
PowerUnleveledAlarm
RfPowerControlAlarm
PaGainAlarm
ModemVoltageAlarm
RssiAlarmLow
PaFinalOverCurrent
PaTempAlarm
PowerSupplyOverVoltageA- *
larm
PowerSupplyOverCurrentA- *
larm
PowerSupplyOverTempera- *
tureAlarm
LowBattery
gory
Alarm, PA Voltage Minor Alarm, PA Voltage Major Alarm,
VSWR Minor Alarm, or VSWR Major Alarm.
* Power Roll-back Alarm The PA output power is more than 3dB below the set output Equipment
(3dB). Output Power={val- power of the station, but at least one of the following "pri- Alarm
ue} mary" alarms is also present: any Fan Alarm, any Temp
Alarm, PA Voltage Alarm, or VSWR Alarm.
* Power Unleveled Alarm. The PA output power is more than 3dB below the set output Equipment
Output Power={value} power and no Fan, Temperature, Voltage, or VSWR alarms Alarm
are present.
* RF Power Control Alarm. Transmitter is delivering power in a de-keyed state or deliver- Equipment
Output Power={value} ing more power in a keyed state than tolerancing allows. Alarm
* PA Gain Alarm. Control The transmitter gain is low, which is indicative of a failed or Equipment
Voltage={value} failing amplifer stage. Alarm
* Modem Voltage Alarm. Val- Voltage to modem is outside of specified range. Modem will Equipment
ue={value} not perform up to specifications. Alarm
* RSSI Alarm Low. Val- Receiver Strength Indication is too low...probably hardware Equipment
ue={value} failure. Might be the station but could also be a fault in the an- Alarm
tenna/feed.
* PA Final Over Current. PA . Equipment
Current={value} Alarm
* PA Temp Alarm. PA Tem- PA Final temperature is outside specified limits which would Equipment
perature={value} allow rated power to be generated. Alarm
Power Supply Over Voltage Power Supply is at fault, voltage sensed at the secondary is Equipment
Alarm. PSU Voltage={value} too high. Alarm
Power Supply Over Current Power Supply is at fault, current sensed at the primary is too Equipment
Alarm. DC Current={value} high. Alarm
Power Supply Over Tem- Power Supply temperature is outside specified limits which Equipment
perature Alarm. Power Sup- would allow rated power to be generated. Power supply will Alarm
ply Temperature={value} shut down until temperature returns to a useable level.
* Low Battery. External Bat- Battery is nearing end of usefulness. Equipment
tery Voltage={value} Alarm

284
 MN002730A01-AD
Appendix E: Alarms and events

Event Name Severity Event/Alarm Message Event/Alarm Description Event Cate-

gory
ModemPaAlarm * Modem PA Alarm. Modem Modem PA is failing or failed. Equipment
Current={value} Alarm
NcmSynchronizedStatus Comm- Device {0} is not reported by Device {0} is not reported by the system. Communica-
Failure the system. tion Alarm

E.12.2
Repeater Events
Events are reported for the Repeater as follows:

Event Name Severity Event/Alarm Message Event/Alarm Description Event Category Manager Entity
PropertyChanged Info Property {0} changed from {1} to Property {0} changed from {1} to Informational Event Property Changed
{2}. {2}.
RolesUpdated Info {0} active roles: {1}. Repeater active roles: {1}. Informational Event Roles Updated
NoRoles Info No active roles for {0}. No active roles for {0}. Informational Event Roles Updated
DeviceStatus.Inactive.Disa- Info Current device status: Inactive Current Device Status: Inactive Informational Event Device Status
bled (Disabled). (Disabled).
DeviceStatus.Active.Ena- Info Current device status: Active Current device status: Active (En- Informational Event Device Status
bled (Enabled). abled).
DeviceStatus.Inac- Info Current device status: Inactive Current device status: Inactive Informational Event Device Status
tive.Alarm (Alarm). (Alarm).
DeviceStatus.Inactive.NA Info Current device status: Inactive Current device status: Inactive Informational Event Device Status
(NA). (NA).
DeviceStatus.Inac- Info Current device status: Inactive Current device status: Inactive Informational Event Device Status
tive.Locked (Locked). (Locked).
DeviceStatus.Inac- Info Current device status: Inactive Current device status: Inactive Informational Event Device Status
tive.RPMode (RP Mode). (RP Mode).
DeviceStatus.Unknown.No- Info Current device status: Unknown Current device status: Unknown Informational Event Device Status
tReported (Not Reported). (Not Reported).
DeviceStatus.Unknown Info Current device status: Unknown. Current device status: Unknown. Informational Event Device Status

285
MN002730A01-AD
Appendix E: Alarms and events

E.13
Replicator Alarms and Events Overview
Events and alarms are reported for the Replicator as follows:

E.13.1
Replicator Alarms
Alarms are reported for the Replicator as follows:

Event Name Severity Event/Alarm Message Event/Alarm Description Event Category Manager Entity
NcmSynchronizedSta- CommFailure Device {0} is not reported by Device {0} is not reported by Communication NCM Synchronized Sta-
tus the system. the system. Alarm tus

E.13.2
Replicator Events
Events are reported for the Replicator as follows:

Event Name Severity Event/Alarm Message Event/Alarm Description Event Category Manager Entity
PropertyChanged Info Property {0} changed from {1} to {2}. Property {0} changed from {1} to {2}. Informational Event Property Changed

E.14
Trunk Controller Alarms and Events Overview
Events and alarms are reported for the Trunk Controller as follows:

E.14.1
Trunk Controller Alarms
Alarms are reported for the Trunk Controller as follows:

Event Name Severity Event/Alarm Message Event/Alarm Description Event Category Manager Entity
NcmSynchronizedSta- CommFailure Device {0} is not reported by Device {0} is not reported by Communication NCM Synchronized Sta-
tus the system. the system. Alarm tus

286
 MN002730A01-AD
Appendix E: Alarms and events

E.14.2
Trunk Controller Events
Events are reported for the Trunk Controller as follows:

Event Name Severity Event/Alarm Message Event/Alarm Description Event Category Manager Entity
PropertyChanged Info Property {0} changed from {1} to Property {0} changed from {1} to Informational Event Property Changed
{2}. {2}.
RolesUpdated Info {0} active roles: {1}. Repeater active roles: {1}. Informational Event Roles Updated
NoRoles Info No active roles for {0}. No active roles for {0}. Informational Event Roles Updated
DeviceStatus.Inactive.Dis- Info Current device status: Inactive Current Device Status: Inactive Informational Event Device Status
abled (Disabled). (Disabled).
DeviceStatus.Active.Ena- Info Current device status: Active (En- Current device status: Active (En- Informational Event Device Status
bled abled). abled).
DeviceStatus.Inac- Info Current device status: Inactive Current device status: Inactive Informational Event Device Status
tive.Alarm (Alarm). (Alarm).
DeviceStatus.Inac- Info Current device status: Inactive Current device status: Inactive Informational Event Device Status
tive.Locked (Locked). (Locked).
DeviceStatus.Un- Info Current device status: Unknown Current device status: Unknown Informational Event Device Status
known.NotReported (Not Reported). (Not Reported).
DeviceStatus.Unknown Info Current device status: Unknown. Current device status: Unknown. Informational Event Device Status

287