ARD-D00742 - Netspan Alarms and Events Reference Guide - SR16.00 - Standard - Rev 10.3

Netspan Alarms and Events Reference
Guide
Part Number: ARD-D00742

System Release: SR16.00
Status: Standard
Revision: 10.3
Published: August 2018
© Copyright by Airspan Networks Ltd., 2018. All rights reserved worldwide.
Legal Notices
The information contained within this document is proprietary, privileged and intended only for the recipient. As such, the
information is subject to all relevant copyright, patent and other laws protecting intellectual property, as well as any specific
agreements protecting Airspan Networks Ltd. rights in the aforesaid information. Neither this document nor the information
contained herein may be published, reproduced, transmitted or disclosed to third parties, in whole or in part, without the
express, prior, written permission of Airspan Networks Ltd. In addition, any use of this document or the information contained
herein for the purposes other than those for which it is disclosed is strictly forbidden.
Airspan Networks Ltd. reserves the right, without prior notice or liability, to make changes in equipment design or specifications.
Information supplied by Airspan Networks Ltd. is believed in good faith to be accurate and reliable, while every care has been
taken in preparing these documents. However, Airspan Networks Ltd. does not make any representations and gives no
warranties of whatever nature in respect of these documents, including without limitation, the accuracy or completeness of any
information, facts and/or opinions contained therein. No responsibility is assumed by Airspan Networks Ltd. for the use of the
documents nor for the rights of third parties which may be effected in any way by the use thereof. The provision of these
documents (and the documents themselves) does not constitute professional advice of any kind. Any representation(s) in these
documents concerning performance of Airspan Networks Ltd. product(s) are for informational purposes only and are not
warranties of future performance, either expressed or implied. Airspan Networks Ltd., its affiliates, directors, employees and
agents shall not be held liable for any damages or losses, of any nature whatsoever, arising from any use of and/or reliance on
the documents.
These documents may contain flaws, omissions or typesetting errors; no warranty is granted nor liability assumed in relation
thereto unless specifically undertaken in Airspan Networks Ltd. sales contract or order confirmation. Information contained
herein is periodically updated and changes will be incorporated into subsequent editions. If you have encountered an error,
please notify Airspan Networks Ltd.
Product performance figures quoted within this document are indicative and for information purposes only.
UK WEEE Registration number: WEEE/AB0207WZ. For more information, see WEEE Information for Airspan Customers
and Recyclers.
Netspan Alarms and Events Reference Guide
Table of Contents
Document Information.............................................................................1
Abstract .................................................................................................................. 1
Revision History ..................................................................................................... 1
Netspan Related Alarm Changes ........................................................................... 7
Netspan Related Event Changes ........................................................................... 8
About This Document ...........................................................................11
Purpose................................................................................................................ 11
Intended Audience ............................................................................................... 11
Document Conventions ........................................................................................ 11
Document Organization ....................................................................................... 12
Related Reading .................................................................................................. 12
Customer Service Help Desk ................................................................ 13
Airspan Encourages Comments .......................................................................... 13
1 Overview ........................................................................................... 14
1.1 Event and Alarm Correlation........................................................................ 14
2 Netspan Alarms.................................................................................16
2.1 Alarm Severity Levels .................................................................................. 16
2.2 Viewing Alarms ............................................................................................ 17
2.3 Refining Alarm Search ................................................................................. 17
2.4 Viewing Alarm Type Description .................................................................. 18
2.5 Viewing Alarm Description ........................................................................... 19
2.6 Acknowledged and Unacknowledged Alarms .............................................. 20
2.7 Deleting an Active Alarm ............................................................................. 20
2.8 Exporting Alarms View into an Excel File .................................................... 21
2.9 Refreshing an Alarms Page ......................................................................... 21
2.10 Alarm Synchronization ................................................................................. 21
2.11 Purging Alarms ............................................................................................ 21
2.12 Alarm Types ................................................................................................ 22
Access Point Connection Fault ............................................................................................... 27
All MME Connectivity Lost (per PLMN) .................................................................................. 27
ARD-D00742 Airspan Commercial and Internal Use i

ASN R6 Comms Loss ............................................................................................................. 28

ASN R6 Standby Comms Loss .............................................................................................. 28
Authorization Failure ............................................................................................................... 28
Auto RSI Config Invalid ........................................................................................................... 29
Auto-Align Failed .................................................................................................................... 29
Auto-Align In-Progress ............................................................................................................ 30
Auto-PCI Allocation Failed ...................................................................................................... 30
Auto-PCI Collision Not Resolved ............................................................................................ 30
Auto-PCI Confusion Not Resolved ......................................................................................... 31
Auto-PCI Policy Violation Not Resolved ................................................................................. 31
Backhaul QoS BW Server Connection ................................................................................... 32
Backhaul QoS Service Affecting ............................................................................................. 32
Backhaul QoS Service Capacity Limiting ............................................................................... 32
Battery Overtemperature (eNodeB) ........................................................................................ 33
Battery Overtemperature (WiFi).............................................................................................. 33
CBSD State Change Failure ................................................................................................... 34
Cell 1 CLPC Disabled ............................................................................................................. 34
Cell 1 Transmission Disabled ................................................................................................. 34
Cell 2 CLPC Disabled ............................................................................................................. 35
Cell 2 Transmission Disabled ................................................................................................. 35
Cell is Not Active ..................................................................................................................... 36
Cell Outage Detected ............................................................................................................. 36
Channel Action Error .............................................................................................................. 37
Channel Out of Service (OOS) ............................................................................................... 37
Channel Provisioning Error ..................................................................................................... 38
CMS Mismatch ....................................................................................................................... 38
CTS eNB Capacity Exceeded................................................................................................. 39
CTS Log Overwritten .............................................................................................................. 39
CTS Logging Stopped ............................................................................................................ 39
CTS PTE Auto Disabled ......................................................................................................... 40
CTS PTE Destination Folder Access Denied ......................................................................... 40
CTS Server Down ................................................................................................................... 41
CTS Time Sync Failed ............................................................................................................ 41
CTS Trace Analysis Failed ..................................................................................................... 42
DHCP T2 Timer Expired ......................................................................................................... 42
ARD-D00742 Airspan Commercial and Internal Use ii

Donor Cell Poor Backhaul Quality .......................................................................................... 43

Enabled Port Down ................................................................................................................. 43
eNodeB is in Holdover ............................................................................................................ 43
eNodeB is in Holdover Expired ............................................................................................... 44
eNodeB PDN Mismatch .......................................................................................................... 44
eSON Server Connection Lost ............................................................................................... 45
ETWS SFTP Session Error .................................................................................................... 45
Ext PPS Not Locked ............................................................................................................... 46
Forced Management Mode Failure ........................................................................................ 46
Frame Synchronized to Internal Clock ................................................................................... 47
GPS Alarms Status Failure ..................................................................................................... 47
GPS File Failure ..................................................................................................................... 48
GPS Lost Comms ................................................................................................................... 48
GPS Lost Satellite Lock .......................................................................................................... 49
GPS Persistency Lost ............................................................................................................. 49
GPS Signal Unacceptable ...................................................................................................... 50
GPS SNR Low ........................................................................................................................ 50
High Antenna Imbalance ........................................................................................................ 51
IKEv2 SA Expired ................................................................................................................... 51
Inventory Error ........................................................................................................................ 52
IP Conflict ............................................................................................................................... 52
IPsec SA Expired .................................................................................................................... 53
iRelay FEM Error .................................................................................................................... 53
Link Down ............................................................................................................................... 54
Low CPU Resources .............................................................................................................. 54
Low Memory Resources ......................................................................................................... 55
Low RRC Resources .............................................................................................................. 55
MBSFN SF Configuration Conflict .......................................................................................... 56
MCE Connectivity Lost ........................................................................................................... 56
Measured BW Less than Minimum ......................................................................................... 57
MME Connectivity Lost ........................................................................................................... 57
MME PLMN Overload Service Interruption ............................................................................ 58
MME PLMN Overload Without Service Interruption ............................................................... 58
Motor Failure ........................................................................................................................... 59
Motor Pending Failure ............................................................................................................ 59
ARD-D00742 Airspan Commercial and Internal Use iii

MSM Failure............................................................................................................................ 60
MSM Port Failure .................................................................................................................... 60
Neighbour Addition Rejected .................................................................................................. 60
NetspanSF Node Config Error ................................................................................................ 61
NetspanSF Server Error ......................................................................................................... 61
NL Sync Clock Source Error ................................................................................................... 62
NL Sync Procedure Error ........................................................................................................ 62
NLM Frequency Scan Warning .............................................................................................. 63
No PTP Master Available ........................................................................................................ 63
Node 10MHz Clock Failure ..................................................................................................... 63
Node Action Error ................................................................................................................... 64
Node Call Trace Server Connection Lost ............................................................................... 64
Node Clock Source Lost ......................................................................................................... 65
Node Clock Source Unavailable ............................................................................................. 65
Node Config Status Changed ................................................................................................. 66
Node Current Unacceptable ................................................................................................... 66
Node Disk Full ........................................................................................................................ 66
Node Encryption Licence Invalid ............................................................................................ 67
Node Feature Licence Expired ............................................................................................... 67
Node Feature Licence Invalid ................................................................................................. 68
Node Feature Not Implemented ............................................................................................. 69
Node Feature Not Licensed .................................................................................................... 69
Node in Holdover .................................................................................................................... 70
Node in Maintenance Mode .................................................................................................... 70
Node Internal Clock ................................................................................................................ 70
Node Invalid Configuration ..................................................................................................... 71
Node Local Access Attempt.................................................................................................... 71
Node Loss of Sync .................................................................................................................. 72
Node Lost Comms .................................................................................................................. 72
Node Out of Service (OOS) .................................................................................................... 73
Node Power Unacceptable ..................................................................................................... 73
Node Provisioning Error .......................................................................................................... 74
Node PTP Degraded Stream .................................................................................................. 74
Node PTP Grand Master Lost ................................................................................................ 75
Node Self Test Failed ............................................................................................................. 75
ARD-D00742 Airspan Commercial and Internal Use iv

Node Shutdown ...................................................................................................................... 76

Node Software Version Status Changed ................................................................................ 76
Node Temperature Unacceptable .......................................................................................... 77
Node Timing Frame Lock Lost................................................................................................ 77
Node Voltage Unacceptable ................................................................................................... 78
NTP Failure ............................................................................................................................. 78
Operator Certificate Expired ................................................................................................... 79
Outdoor Cell is Out of Service ................................................................................................ 79
P1 CDCL Selection Failure ..................................................................................................... 80
P1 PDCL Selection Failure ..................................................................................................... 80
PCI Conflict Not Resolved ...................................................................................................... 81
PCI Update Failure ................................................................................................................. 81
PDCL Selection Failure .......................................................................................................... 82
PLL Lock Lost ......................................................................................................................... 82
PnP Configuration Mismatch .................................................................................................. 83
PnP Location Changed ........................................................................................................... 83
Port Disable Prevention .......................................................................................................... 84
PTP Clock Sync ...................................................................................................................... 84
PTP Hardware Fault ............................................................................................................... 85
QoS Handover Neighbour Does Not Exist ............................................................................. 85
QoS Server Connection Failure .............................................................................................. 86
Remote Connection Lost ........................................................................................................ 86
RF FEM Fault ......................................................................................................................... 86
RF FEM Not Present .............................................................................................................. 87
RF Hardware Fault ................................................................................................................. 87
RF Out of Service (OOS) ........................................................................................................ 88
RF1 Carrier Sense Frequent Interference .............................................................................. 88
RF1 Carrier Sense Interference ............................................................................................. 89
RF1 Configuration Fault .......................................................................................................... 89
RF1 Hardware Fault ............................................................................................................... 90
RF1 Hardware Fault (Warning)............................................................................................... 90
RF1 Temperature Fault .......................................................................................................... 91
RF1 Transmitter Off ................................................................................................................ 91
RF1 VSWR Fault .................................................................................................................... 92
RF2 Carrier Sense Frequent Interference .............................................................................. 92
ARD-D00742 Airspan Commercial and Internal Use v

RF2 Carrier Sense Interference ............................................................................................. 93

RF2 VSWR Fault .................................................................................................................... 96
RF3 VSWR Fault .................................................................................................................... 99
RF4 Configuration Fault ........................................................................................................ 100
RF4 Hardware Fault ............................................................................................................. 100
RF4 Hardware Fault (Warning)............................................................................................. 101
RF4 Temperature Fault ........................................................................................................ 101
RF4 Transmitter Off .............................................................................................................. 102
RF4 VSWR Fault .................................................................................................................. 102
SAS Grant Failure ................................................................................................................. 103
SAS Grant Suspended ......................................................................................................... 103
SAS Heartbeat Failure .......................................................................................................... 104
SAS Registration Failure ...................................................................................................... 104
SAS Registration Suspended ............................................................................................... 104
SAS Server Disconnected .................................................................................................... 105
SAS Spectrum Inquiry Failure .............................................................................................. 105
SBA Misconfiguration ........................................................................................................... 106
Scan In Progress .................................................................................................................. 106
Server CPU Usage High ....................................................................................................... 107
Server Disk Usage High ....................................................................................................... 107
Server Event Queue Size High ............................................................................................. 108
Server Memory Usage High ................................................................................................. 108
Serving Netspan Address Mismatch .................................................................................... 108
Serving Security Gateway Mismatch .................................................................................... 109
S-GW Connectivity Lost ........................................................................................................ 109
ARD-D00742 Airspan Commercial and Internal Use vi

SNMP Authentication Failure................................................................................................ 110

SNMPv3 Fallback ................................................................................................................. 110
Software Activate Failure ...................................................................................................... 110
Software Download Failure................................................................................................... 111
Software Upgrade Fault ........................................................................................................ 111
SS Action Error ..................................................................................................................... 112
SS Provisioning Error ........................................................................................................... 112
SS RSSI ............................................................................................................................. 113
Sync Switch Exceeded ......................................................................................................... 113
System Information Truncation ............................................................................................. 114
Tamper Detect ...................................................................................................................... 114
Tamper Detect and Disabled ................................................................................................ 114
Tilt Threshold Exceeded ....................................................................................................... 115
TWAMP Overloaded ............................................................................................................. 115
Unsupported Clock Source ................................................................................................... 116
VoiceMAX Lost Comms ........................................................................................................ 116
WiFi Board Connectivity ....................................................................................................... 116
WiFi Board Initialization ........................................................................................................ 117
X2 Neighbour Comms Loss .................................................................................................. 117
3 Netspan Events ............................................................................... 119

3.1 Viewing Events .......................................................................................... 119
3.2 Refining Event Search ............................................................................... 119
3.3 Editing Event Details ................................................................................. 120
3.4 Exporting Events View into an Excel File .................................................. 121
3.5 Refreshing an Events Page ....................................................................... 121
3.6 Event Types............................................................................................... 121
Action Error ........................................................................................................................... 127
Active Clock Source Change ................................................................................................ 127
A-GPS File Status Change ................................................................................................... 127
All MME S1-C Comms Status Change (per PLMN) ............................................................. 128
Authorization Failure ............................................................................................................. 128
Authorization Success .......................................................................................................... 129
Auto PCI Range Changed .................................................................................................... 129
Auto RSI Change .................................................................................................................. 129
ARD-D00742 Airspan Commercial and Internal Use vii

Auto RSI Selected Value ...................................................................................................... 130

Auto-Align Request Detected ............................................................................................... 130
Auto-Align Status Changed .................................................................................................. 130
Auto-PCI Allocation ............................................................................................................... 131
Backhaul QoS BW Server Connection Status Change ........................................................ 131
Backhaul Qos Capacity Limiting Status ................................................................................ 131
Backhaul Qos Service Affecting Status ................................................................................ 132
Basic Caps Exchange Failure............................................................................................... 132
Basic Caps Exchange Success ............................................................................................ 132
Battery Overtemperature (eNodeB) ...................................................................................... 133
Battery Overtemperature (WiFi)............................................................................................ 133
BS Active ASN Gateway....................................................................................................... 133
BS ASN R6 Comms Status Change ..................................................................................... 134
BS ASN-GW Mode Change.................................................................................................. 134
BS Failed Actions Cleared .................................................................................................... 134
BS FEM Status Change ........................................................................................................ 135
BS Inventory Added .............................................................................................................. 135
BS MSM Port Status Change ............................................................................................... 135
BS MSM Status Change ....................................................................................................... 136
BS Running Status Change .................................................................................................. 136
Calculate Sector Harmonic Mean Request Detected ........................................................... 136
CBSD State Change ............................................................................................................. 137
Cell 1 Status Change ............................................................................................................ 137
Cell 2 Status Change ............................................................................................................ 137
Cell Active Status Change .................................................................................................... 138
Cell Enabled State Change .................................................................................................. 138
Cell Outage Detected ........................................................................................................... 138
Channel Action Error ............................................................................................................ 139
Channel Failed Actions Cleared ........................................................................................... 139
Channel Provisioning Error ................................................................................................... 139
Channel Reprovision ............................................................................................................ 140
Channel Status Change........................................................................................................ 140
Clock Source Availability Change ......................................................................................... 141
Clock Source Change ........................................................................................................... 141
Clock Source Configuration .................................................................................................. 141
ARD-D00742 Airspan Commercial and Internal Use viii

CMS Status Change ............................................................................................................. 142

Cold Start ............................................................................................................................. 142
Command Failed .................................................................................................................. 142
CTS eNB Capacity Status Change ....................................................................................... 143
CTS Log Overwrite Status Change ...................................................................................... 143
CTS Logging Status Change ................................................................................................ 143
CTS PTE Status Change ...................................................................................................... 144
CTS Server Status Change .................................................................................................. 144
CTS Time Sync Status Change ............................................................................................ 144
CTS Trace Analysis Status Change ..................................................................................... 145
Deregistration ....................................................................................................................... 145
DFS Disruption Detected ...................................................................................................... 145
DFS Mode Change ............................................................................................................... 146
DFS Status Change .............................................................................................................. 146
DHCP T2 Timer Status Change ........................................................................................... 146
Donor Cell Backhaul Quality Changed ................................................................................. 147
Duplicate EMS ...................................................................................................................... 147
EGP Neighbor Loss .............................................................................................................. 147
Emergency Call Reset Delay ................................................................................................ 148
Enabled Port Down ............................................................................................................... 148
eNodeB PDN Status Change ............................................................................................... 148
eSON Server Connection Change ....................................................................................... 149
ETWS File Upload ................................................................................................................ 149
ETWS SFTP Session ........................................................................................................... 149
Ext PPS Stream Status Changed ......................................................................................... 150
Failed Actions Cleared .......................................................................................................... 150
File Upload Change .............................................................................................................. 150
Fine-Scan Request Detected................................................................................................ 151
Force Scan Request Detected ............................................................................................. 151
Forced Management Status Changed .................................................................................. 152
Forced Reset ........................................................................................................................ 152
GPS Alarms Status Change ................................................................................................. 153
GPS Comms Change ........................................................................................................... 153
GPS File Status Change....................................................................................................... 154
GPS Lock Change ................................................................................................................ 154
ARD-D00742 Airspan Commercial and Internal Use ix

GPS Persistency Status Changed ........................................................................................ 155

GPS Reduced Holdover ....................................................................................................... 155
GPS SNR Change ................................................................................................................ 156
Hardware Replaced .............................................................................................................. 156
Hardware Swap .................................................................................................................... 156
ICIC Misconfiguration ........................................................................................................... 157
Ignore ............................................................................................................................. 157
IKEv2 SA Expiry ................................................................................................................... 157
Initial Ranging Failure ........................................................................................................... 158
Initial Ranging Success ........................................................................................................ 158
Inventory Status Change ...................................................................................................... 158
IPsec SA Expiry .................................................................................................................... 159
iRelay Donor Cell Connectivity Status Changed .................................................................. 159
iRelay FEM Status ................................................................................................................ 160
iRelay P1 PDCL Status Changed ......................................................................................... 160
iRelay Scan List Empty in Specific Band Changed .............................................................. 161
iRelay Scan List Empty Status Changed .............................................................................. 161
iRelay Scan List PDCL Status Changed .............................................................................. 161
LAN Device Connection Status Change ............................................................................... 162
LAN Device MAC Address Mismatch ................................................................................... 162
Link Down ............................................................................................................................. 163
Link Up ............................................................................................................................. 163
Lockout ............................................................................................................................. 164
Management IP Info Change ................................................................................................ 164
Management Profile (16e) Change ...................................................................................... 165
Management Service Started ............................................................................................... 165
Management Service Stopped ............................................................................................. 165
MBSFN SF Configuration Conflict ........................................................................................ 166
MCE Connectivity ................................................................................................................. 166
Measured BW Status Change .............................................................................................. 167
MIB Provisioning Change ..................................................................................................... 167
MME PLMN Overload Service Interruption Status Changed ............................................... 167
MME PLMN Overload Without Service Interruption Status Changed .................................. 168
MME S1-C Comms Status Change ...................................................................................... 168
Motor Failure ......................................................................................................................... 168
ARD-D00742 Airspan Commercial and Internal Use x

Neighbour Addition Rejected ................................................................................................ 169

Neighbouring Cell in NRT ..................................................................................................... 169
NetspanSF Node Config Error .............................................................................................. 169
NetspanSF Server Error ....................................................................................................... 170
Network Entry Status Change .............................................................................................. 170
Network Profile (16e) Change .............................................................................................. 170
NL Sync Clock Source Operation Status Change ................................................................ 171
NL Sync Procedure Status Change ...................................................................................... 171
NLM Frequency Scan ........................................................................................................... 171
NMS Licence Change ........................................................................................................... 172
NMS Restart Complete ......................................................................................................... 172
Node 10MHz Clock Status Change ...................................................................................... 173
Node Action Error ................................................................................................................. 173
Node Added .......................................................................................................................... 173
Node Agent Active State Change ......................................................................................... 174
Node Agent ID Change ......................................................................................................... 174
Node Call Trace Status Changed ......................................................................................... 175
Node Clock Source Status Change ...................................................................................... 175
Node Config Status Change ................................................................................................. 175
Node Connection State Change ........................................................................................... 176
Node Current Change ........................................................................................................... 176
Node Deleted ........................................................................................................................ 177
Node Disk Usage Change .................................................................................................... 177
Node Encryption Licence Invalid .......................................................................................... 177
Node Feature Licence Expiring ............................................................................................ 178
Node Feature Licence Invalid ............................................................................................... 178
Node Feature Not Implemented ........................................................................................... 179
Node Feature Not Licensed .................................................................................................. 179
Node GPS Receiver Status Change .................................................................................... 179
Node Internal Clock Status Change ..................................................................................... 180
Node Invalid Configuration Change ...................................................................................... 180
Node LED Status Change .................................................................................................... 181
Node Local Access Attempt.................................................................................................. 181
Node Maintenance Transition ............................................................................................... 181
Node Management Change.................................................................................................. 182
ARD-D00742 Airspan Commercial and Internal Use xi

Node Message Change Failed ............................................................................................. 182

Node Message Change Success ......................................................................................... 183
Node NTP Status Change .................................................................................................... 183
Node Operational Status Change ......................................................................................... 183
Node Operational Status Change (Server Detected) ........................................................... 184
Node Power Change ............................................................................................................ 184
Node Provisioning Error ........................................................................................................ 184
Node PTP Grand Master Status Change ............................................................................. 185
Node PTP Quality Status Change ........................................................................................ 185
Node Redirection Failure ...................................................................................................... 186
Node Redirection Request.................................................................................................... 186
Node Redirection Success ................................................................................................... 186
Node Reprovision ................................................................................................................. 187
Node Resources Status Change .......................................................................................... 187
Node Restarted (Server Detected) ....................................................................................... 188
Node Self Test ...................................................................................................................... 188
Node Shutdown .................................................................................................................... 188
Node Software Version Status Change ................................................................................ 189
Node SS BPKM Fail ............................................................................................................. 189
Node SS Dynamic Service Fail............................................................................................. 190
Node SS RSSI Status Change ............................................................................................. 190
Node Sync Lock Status Change ........................................................................................... 190
Node Synchronization Lock Status Change ......................................................................... 191
Node Temperature Change .................................................................................................. 191
Node Tilt Changed ................................................................................................................ 192
Node Timing Frame Lock ..................................................................................................... 192
Node Voltage Status Change ............................................................................................... 192
Node X2 Neighbour Status Change ..................................................................................... 193
Operator Certificate Expiry ................................................................................................... 193
Outdoor Cell Status Changed ............................................................................................... 194
P1 CDCL Status Changed .................................................................................................... 194
Password Change ................................................................................................................ 194
Password Reset .................................................................................................................... 195
PCI Conflict Status Changed ................................................................................................ 195
PCI Range Configuration ...................................................................................................... 195
ARD-D00742 Airspan Commercial and Internal Use xii

PCI Update Status Change .................................................................................................. 196

PHY Reset ............................................................................................................................ 196
PLL Status Change ............................................................................................................... 196
PnP Complete ....................................................................................................................... 197
PnP Config Added ................................................................................................................ 197
PnP Config Deleted .............................................................................................................. 197
PnP Configuration Mismatch ................................................................................................ 198
PnP Identification .................................................................................................................. 198
PnP Location Changed ......................................................................................................... 199
PnP Node Discovery Failed .................................................................................................. 199
PnP Node Matched Multiple Config ...................................................................................... 200
PnP Node Not Configured .................................................................................................... 200
PnP Node Not Found ............................................................................................................ 200
PnP Node Not Managed ....................................................................................................... 201
PnP State Change ................................................................................................................ 201
PnP Trigger ........................................................................................................................... 202
Port Disable Prevention ........................................................................................................ 202
Port Status Changed ............................................................................................................ 202
Provisioning Error ................................................................................................................. 203
PTP Hardware ...................................................................................................................... 203
PTP Master Availability Changed ......................................................................................... 204
PTP Timing Sync .................................................................................................................. 204
QoS Handover Neighbour Change ....................................................................................... 204
Registration Failure ............................................................................................................... 205
Registration SubOptimal ....................................................................................................... 205
Registration Success ............................................................................................................ 205
Remote Connection Change ................................................................................................ 206
Reprovision ........................................................................................................................... 206
Reset ............................................................................................................................. 207
RF Path Imbalance Detected................................................................................................ 207
RF Status Change ................................................................................................................ 207
RF Status Change (Server Detected) ................................................................................... 208
RF1 Status Change .............................................................................................................. 208
RF1 Status Change (Server Detected) ................................................................................. 209
RF2 Status Change .............................................................................................................. 209
ARD-D00742 Airspan Commercial and Internal Use xiii


RF3 Status Change .............................................................................................................. 211
RF4 Status Change .............................................................................................................. 212
SAS Grant Status ................................................................................................................. 213
SAS Grant Suspension Status.............................................................................................. 214
SAS Heartbeat Status ........................................................................................................... 215
SAS Registration Update ...................................................................................................... 215
SAS Server Connection State Change ................................................................................. 216
SAS Spectrum Inquiry Update .............................................................................................. 216
SBA Configuration Status Changed ..................................................................................... 217
Scan Status........................................................................................................................... 217
Server CPU Usage Change.................................................................................................. 217
Server Disk Usage Change .................................................................................................. 218
Server Event Queue Size Change ....................................................................................... 218
Server Memory Usage Change ............................................................................................ 218
Serving Netspan Address Status Change ............................................................................ 219
Serving Security Gateway Status Change ........................................................................... 219
SF Creation Failure ............................................................................................................... 219
SF Creation Success ............................................................................................................ 220
S-GW S1-U Comms Status Change .................................................................................... 220
SNMP Authentication Failure................................................................................................ 220
SNMPv3 Fallback Status Changed ...................................................................................... 221
Software Activate .................................................................................................................. 221
Software Download ............................................................................................................... 221
Software Upgrade Fault ........................................................................................................ 222
Software Upgrade State Change .......................................................................................... 222
Summary Connection Status ................................................................................................ 223
SW Bank Info Changed ........................................................................................................ 223
Synchronization Source Changed ........................................................................................ 223
System Information Truncation ............................................................................................. 224
Tamper Status Change ......................................................................................................... 224
TFTP Failure ......................................................................................................................... 224
TFTP Success ...................................................................................................................... 225
ARD-D00742 Airspan Commercial and Internal Use xiv

TWAMP Overload Status Changed ...................................................................................... 225

TWAMP Sender Operational Status Change ....................................................................... 225
UE Trace and MDT Status Change ...................................................................................... 226
Unauthorized File Upload Attempted .................................................................................... 226
Unknown ............................................................................................................................. 226
VoiceMAX Comms Change .................................................................................................. 227
Warm Start ............................................................................................................................ 227
WiFi Board Connectivity ....................................................................................................... 227
WiFi Board Initialization ........................................................................................................ 228
Wman-IF Draft 1 Node Trap (SNMPv1) ............................................................................... 228
A Abbreviations .................................................................................. 229
ARD-D00742 Airspan Commercial and Internal Use xv

Figures
Figure 1: Netspan Fault Management Mechanism .............................................................................. 14
Tables
Table 1. Typographic Conventions ....................................................................................................... 11
Table 2. Alarm Severity Levels ............................................................................................................. 16
Table 3. Alarm Search Criteria ............................................................................................................. 17
Table 4. Alarm Type Properties and Descriptions ................................................................................ 18
Table 5. Alarm Properties and Descriptions ......................................................................................... 19
Table 6. Alarm Definition Structure ....................................................................................................... 22
Table 7. Alarms ..................................................................................................................................... 23
Table 8. Event Search Criteria ........................................................................................................... 119
Table 9. Event Properties ................................................................................................................... 120
Table 10. Event Definition Structure ................................................................................................... 121
Table 11. Events ................................................................................................................................. 122
ARD-D00742 Airspan Commercial and Internal Use xvi

Document Information
Abstract
This document serves as a reference for all the alarms and events displayed in Netspan. It defines
activities that aid in managing faults in Netspan.
Revision History
Revision Details Date Summary of Changes
Rev 10.3 July 2018 Alarm Types

Updated Alarm Types
 Updated the following alarm types:
o Server Event Queue Size High: added a
note about the current threshold.
Removed Alarm Types
 Removed the following alarm types:
o A-GPS File Not Received
Event Types
Updated Event Types
 Updated the following event types:
o Server Event Queue Size Change: added
a note about the current threshold.
Rev 10.2 June 2018 Alarm Types

New Alarm Types
 Added the following new alarm types:
o SAS Server Disconnected
o GPS SNR Low
Reason: This alarm type was removed
from Rev 10.1 assuming that it was only
relevant for eNodeBs up to SR14.01
(inclusive). It has been added back in this
revision after confirming that it also applies
to other hardware types.
Removed Alarm Types
 Removed the following WiMAX alarm types:
o DFS Failure
o Node Carrier Frequent Interference
o Node Carrier Interference
o Node Lost GPS Synchronization
o Node OBSAI Link Failure (All)
o Node OBSAI Link Failure (Partial)
o Node RF Transceiver Fault (All)
o Node RF Transceiver Fault (Partial)
o Node RF Transceiver Fault (Warning)
ARD-D00742 Airspan Commercial and Internal Use 1


o SCRT Redundancy Protection Activated
Event Types
New Event Types
 Added the following new event types:
o A-GPS File Status Change
o LAN Device Connection Status Change
o LAN Device MAC Address Mismatch
o SAS Server Connection State Change
Updated Event Types
 PnP Identification: updated the information in
the Event Information field.
Renamed Event Types
 Renamed the following event type:
o Unsupported Clock Source Configuration
as Clock Source Configuration
Removed Event Types
 Removed the following event types because
they apply to WiMAX products only:
o DFS Event
o Node Carrier Sense (deprecated)
o Node Carrier Sense Status Change
o Node OBSAI Link
o Node GPS Synchronization Change
o Node RF Status Change (16d)
o Node RF Transceiver Fault
o SS WiFi AP Reset
Rev 10.1 April 2018 Alarm Types

New Alarm Types
 Added the following new alarm types:
o eNodeB PDN Mismatch
o Serving Netspan Address Mismatch
Updated Alarm Types
 Access Point Connection Fault
o Updated the Recommended Actions
field.
 All MME Connectivity Lost (per PLMN)
o Updated the Description, Applicable
Technology and Recommended Actions
fields.
 Backhaul QoS BW Server Connection
o Updated the Description and Applicable
Technology fields.
 Backhaul QoS Service Affecting
field.
 Backhaul QoS Service Capacity Limiting
field.


 CBSD State Change Failure
o Updated the Description and
Recommended Actions fields.
 Cell is Not Active
Updated the Recommended Actions and
Clearing fields.
 CMS Mismatch
Technology and Recommended Actions
fields.
 eNodeB is in Holdover
o Updated the Severity field.
 eNodeB is in Holdover Expired
o Updated the Description field.
 Measured BW Less than Minimum
 NLM Frequency Scan Warning
field.
 Node Feature Licence Expired
o Removed eNodeB and Relay eNodeB
from the Applicable Technology field.
Reason: This alarm type is not applicable
to eNodeB and Relay eNodeB.
 Node Feature Licence Invalid
 Node Feature Not Licensed
 Server Event Queue Size High
 Serving Security Gateway Mismatch
 SNMP Authentication Failure
o Removed eNodeB, iBridge NLOS, Relay
and Relay eNodeB from the Applicable
Technology field.
to eNodeB, iBridge NLOS, Relay and
Relay eNodeB.
 Sync Switch Exceeded


Removed Alarm Types
 GPS SNR Low
Reason: This alarm has been removed from
this version because it only applies to
eNodeBs up to SR14.01 (inclusive).
Event Types
New Event Types
 Added the following new event types:
o eNodeB PDN Status Change
o Serving Netspan Address Status Change
Updated Event Types
 All MME S1-C Comms Status Change (per
PLMN)
o Updated the Description, Event Trigger
and Event Information fields.
 Backhaul QoS BW Server Connection Status
Change
Hardware Type, Event Trigger and
Event Information fields.
 CBSD State Change
 CMS Status Change
 Cell Active Status Change
 Measured BW Status Change
 NLM Frequency Scan
o Updated the Event Information field.
 Node Feature Licence Expiring
from the Applicable Hardware Type field.
Reason: This event type is not applicable


 Password Change
 Password Reset
 PCI Conflict Status Changed
 Server Event Queue Size Change
Event Information.
 Serving Security Gateway Status Change
Event Information.
o Removed eNodeB, iBridge NLOS, Relay
and Relay eNodeB from the Applicable
Technology field.
to eNodeB, iBridge NLOS, Relay and
Relay eNodeB.
 UE Trace and MDT Status Change
Renamed Event Types
 Renamed the following event types:
o Cell is Not Active as Cell Active Status
Change
o CMS Mismatch as CMS Status Change
o BhQos Bw Server Connection Status
Change as Backhaul QoS BW Server
Connection Status Change
o Measured BW Less than Minimum as
Measured BW Status Change
o Serving Security Gateway Mismatch as
Serving Security Gateway Status
Change
Rev 10.0 March 2018 Table 2. Alarm Severity Levels

Alarm Types
 New Alarms
 All MME Connectivity Lost (per PLMN)
 CBSD State Change Failure
 Cell is Not Active
 eNodeB Is In Holdover
 eNodeB Is In Holdover Expired
 NL Sync Clock Source Error


 NL Sync Procedure Error
 NLM Frequency Scan Warning
 Node Clock Source Unavailable
 Node Disk Full
 PCI Update Failure
 Server Event Queue Size High
 Unsupported Clock Source
Event Types
 New Events
 Active Clock Source Change
 All MME S1-C Comms Status Change (per
PLMN)
 BhQos Bw Server Connection Status
Change
 Cell is not active
 Clock Source Availability Change
 CMS Mismatch
 NL Sync Clock Source Operation Status
Change
 NL Sync Procedure Status Change
 NLM Frequency Scan
 Node Sync Lock Status Change
 PCI Update Status Change
 Server Event Queue Size Change
 Unsupported Clock Source Configuration
Abbreviations

Netspan Related Alarm Changes

Revision Alarm Name Location Summary of
Details Changes
Revision 10.3
SR16.00/ o Server Event Queue Size High Updated alarm types

Alarm Types
Rev 10.3 o A-GPS File Not Received Removed alarm types
Revision 10.2

o SAS Server Disconnected New alarm types
o GPS SNR Low
o DFS Failure
o Node Carrier Frequent Interference
SR16.00/
o Node Carrier Interference Alarm Types
Rev 10.2
o Node Lost GPS Synchronization
o Node OBSAI Link Failure (All)
o Node OBSAI Link Failure (Partial) Removed alarm types
o Node RF Transceiver Fault (All)
o Node RF Transceiver Fault (Partial)
(Warning)
o SCRT Redundancy Protection
Activated
Revision 10.1
o eNodeB PDN Mismatch

New alarm types
o Serving Netspan Address Mismatch
o Access Point Connection Fault

o All MME Connectivity Lost (per
PLMN)
o Backhaul QoS BW Server
Connection
o Backhaul QoS Service Affecting
o Backhaul QoS Service Capacity
SR16.00/Rev Limiting Alarm Types
10.1
o CBSD State Change Failure
Updated alarm types
o Cell is Not Active
o CMS Mismatch
o eNodeB is in Holdover
o eNodeB is in Holdover Expired
o Measured BW Less than Minimum
o NLM Frequency Scan Warning
o Node Feature Licence Expired
o Node Feature Licence Invalid

Revision Alarm Name Location Summary of

Details Changes
o Node Feature Not Licensed
o Server Event Queue Size High
o Serving Security Gateway
Mismatch
o SNMP Authentication Failure
o Sync Switch Exceeded
o GPS SNR Low Removed alarm types
Revision 10.0
o All MME Connectivity Lost (per

PLMN)
Connection
o CBSD State Change Failure
o Cell is Not Active
o eNodeB Is In Holdover
o eNodeB Is In Holdover Expired
o Measured BW Less than Minimum
SR16.00/Rev o NL Sync Clock Source Error Alarm Types New alarm types
10.0
o NL Sync Procedure Error
o NLM Frequency Scan Warning
o Node Clock Source Unavailable
o Node Disk Full
o PCI Update Failure
o Server Event Queue Size High
Mismatch
o Unsupported Clock Source
Netspan Related Event Changes

Revision Event Name Location Summary of
Details Changes
Revision 10.3
SR16.00/
o Server Event Queue Size Change Event Types Updated event types
Rev 10.3
Revision 10.2
o A-GPS File Status Change

o LAN Device Connection Status
Change
SR16.00/ o LAN Device MAC Address New event types
Mismatch Event Types
Rev 10.2
o SAS Server Connection State
Change
o PnP Identification Updated event types


Details Changes

Configuration as Clock Source Renamed event type
Configuration
o DFS Event
o Node Carrier Sense (deprecated)
o Node Carrier Sense Status
Change
o Node OBSAI Link
Removed event types
o Node GPS Synchronization
Change
o Node RF Status Change (16d)
o SS WiFi AP Reset
Revision 10.1
o eNodeB PDN Status Change

o Serving Netspan Address Status New event types
Change
o All MME S1-C Comms Status

Change (per PLMN)
Connection Status Change
o CBSD State Change
o CMS Status Change
o Cell Active Status Change
o Measured BW Status Change
o NLM Frequency Scan
o Node Feature Licence Expiring
o Node Feature Licence Invalid Updated event types
o Node Feature Not Licensed
SR16.00/Rev
10.1 o Password Change Event Types
o Password Reset
o PCI Conflict Status Changed
o Server Event Queue Size Change
o Serving Security Gateway Status
Change
o SNMP Authentication Failure
o UE Trace and MDT Status
Change
o Cell is Not Active as Cell Active

Status Change
o CMS Mismatch as CMS Status
Change
Renamed event types
o BhQos Bw Server Connection
Status Change as Backhaul QoS
BW Server Connection Status
Change


Details Changes
o Measured BW Less than
Minimum as Measured BW Status
Change
Mismatch as Serving Security
Gateway Status Change
Revision 10.0
o Active Clock Source Change

o All MME S1-C Comms Status
Change (per PLMN)
o BhQos Bw Server Connection
Status Change
o CBSD State Change
o Cell is not active
o Clock Source Availability Change
o CMS Mismatch
o Measured BW Less than
Minimum
o NL Sync Clock Source Operation
SR16.00/Rev
Status Change Event Types New event types
10.0
o NL Sync Procedure Status
Change
o NLM Frequency Scan
o Node Sync Lock Status Change
o PCI Update Status Change
o Server Event Queue Size Change
Mismatch
o UE Trace and MDT Status
Change
Configuration

About This Document

Purpose
This guide explains the fault management mechanism implemented in Netspan.
Intended Audience
This guide is intended for the operations and maintenance personnel who need information on the
alarms and events displayed in Netspan.
Document Conventions
This document uses the following typographic conventions.
Table 1. Typographic Conventions
Convention Element
Blue underlined text Cross-reference links.
Bold text Keyboard buttons and GUI elements.
Command Command names or phrases.
Computer output Text displayed by the computer.
Hyperlinks Website and e-mail addresses.
Signifies a hazardous situation—if not avoided—will

Danger cause death or serious injury. Describes how to avoid
it.
Signifies a hazardous situation—if not avoided—can

Warning cause death or serious personal injury. Describes
how to avoid it.
Signifies a hazardous situation—if not avoided—can

Caution void the product warranty, and cause property
damage. Describes how to avoid it.
Important Provides necessary information to explain a task.
Note Provides additional information.
Tip Provides helpful hints.

Document Organization
Chapter Contents
1 Overview Provides an overview of the Netspan alarms.
2 Netspan Alarms Describes different types of Netspan alarms.
3 Netspan Events Describes the different types of Netspan events.
Lists the abbreviations (used in this document) and their

A Abbreviations
expansions.
Related Reading
The following document contains related information:
 SYN-PSD-0027 – Netspan NBIF Product Specification
This document describes the transportation mechanism implemented in Netspan to interface
with the customer OSS through an NBIF.

Customer Service Help Desk

Airspan’s Customer Care Help Desk offers prompt and efficient customer support services.
Note: To avail Airspan’s Customer Care Help Desk support, you must be a registered user and must
have a valid support contract. To register, click here and fill the Registration form.
To create and update issue logs, send e-mails to Customer Care Help Desk. Once you submit your
issue, the system generates a new issue and sends an issue number for your reference. The system
uses this issue number to categorize and store e-mails under the appropriate issue.
To help Customer Care Help Desk identify your issue, include the issue number and your Customer
Care Helpdesk account details in all further communications.
Main Operations Worldwide Headquarters Airspan India

Airspan Communications Ltd. Airspan Networks Inc. Airspan Networks India Pvt Ltd.
Capital Point 777, Yamato Road, Suite 105 Cyber One, 1107/1108,
33 Bath Road Boca Raton, FL 3341-4408, USA S Pranavanandji Marg, Sector - 30,
Slough, Berkshire Tel: +1 561 893 8670 Vashi, Navi Mumbai – 400 703.
SL1 3UF, United Kingdom Tel: +91 22 2087 8003
Tel: +44-1895-467-100
Airspan Encourages Comments

Airspan welcomes any feedback and suggestions that help to improve the quality of the documentation.
Send your feedback to documentfeedback@airspan.com.

1 Overview
This document provides a comprehensive overview of Netspan alarms and events.
A Netspan event is a notification indicating the occurrence of a condition on the Netspan server or any
NEs - for example - Channel Action Error, where the node reports a change in its status per channel.
The following conditions can raise a Netspan event:
 The receipt of the SNMP traps or notifications by Netspan.
 The transmission of any internal Netspan notification to Event Service by any Netspan
component.
 The occurrence of a significant change (for example, rebooting the server or change of an alarm
status).
A Netspan alarm indicates the presence of a fault condition on the Netspan server or any NEs - for
example - Node Lost Comms, which indicates that the EMS server is unable to communicate with the
SNMP agent on the node.
1.1 Event and Alarm Correlation

The alarm raising and clearing processes are always triggered by an associated event.
Note: Not all events raise alarms. Only events notifying fault conditions raise alarms.
Depending on the event severity, Netspan raises an alarm until the subsequent condition is cleared.
Resolving a fault in the network clears the associated alarm, but an event remains until it is expired
from the Netspan event buffer.
Figure 1 illustrates the Netspan fault management mechanism.
Figure 1: Netspan Fault Management Mechanism
The node or NE sends the SNMP trap notifications (for example, Cold Start) to Event Service. Event
Service converts those notifications to Netspan events.

Event Service also performs the background polling of the NE alarm state and raises internal events to
synchronise the alarms. Certain events are forwarded to Alarm Service, which raises or clears alarms
as required.
If the NBIF event and alarm forwarding is configured, the events and alarms are forwarded as SNMP
traps to a high level management system.

2 Netspan Alarms
An alarm is the response to one or more associated events. In Netspan, alarms are raised and cleared
by events.
This chapter discusses the following topics:
 Alarm Severity Levels
 Viewing Alarms
 Refining Alarm Search
 Viewing Alarm Type Description
 Viewing Alarm Description
 Acknowledged and Unacknowledged Alarms
 Deleting an Active Alarm
 Exporting Alarms View into an Excel File
 Refreshing an Alarms Page
 Alarm Synchronization
 Purging Alarms
 Alarm Types
2.1 Alarm Severity Levels

Table 2 defines the severity levels of the Netspan alarms.
Table 2. Alarm Severity Levels
Severity Color Icon Description
Critical Red Indicates a critical condition.
Indicates that there is a high risk of loss of

Major Orange
service.
Indicates that there is a partial risk of loss of

service.
Minor Yellow
Note: Perform corrective actions to avoid a more
severe service-affecting fault.
Signifies the presence of a warning condition.

Warning Cyan Note: Perform corrective actions to avoid a more
severe service-affecting fault.
Normal Green Indicates that the alarm is cleared.
Indicates that the cause of the Alarm cannot be

Indeterminate Magenta determined at this time (or the node is in
maintenance mode).

2.2 Viewing Alarms

Depending on the status, the Netspan alarms are classified into the following types:
 Active alarms
 Historical alarms
Active alarms include all the currently active alarms that are collected from the network and stored in
the Netspan database. To view the active alarms, on the main menu, select Fault Management >
Active Alarms.
You can also find the active alarms on the Historical Alarms page, which also displays the deleted
alarms. To view the historical alarms, on the main menu, select Fault Management > Historical
Alarms.
2.3 Refining Alarm Search

You can apply filters on your Active Alarms page to display a subset of alarms. To refine your search,
go to the Active Alarms page, and then do one of the following:
 Using Filter – Click on the Filter checkbox and select the preferred search criterion listed in
the Filter drop-down box. For more information on the available search criteria, see Table 3.
Table 3. Alarm Search Criteria
Criterion Description
Displays the alarms that match the search terms
Severity
with the specified severity level.
Displays the Cleared alarms that match the

Cleared search terms (if the search term is False it
displays the not Cleared alarms).
Displays the alarm that matches the Alarm ID of

Alarm ID
a specific Alarm ID.
Displays the alarms that match the specified

Alarm Type
Alarm Type.
Displays the alarms that match your specified

Alarm Type ID
Alarm Type ID.

Category
Category.

Source Type
source type.

Source Name
Source Name (Node Name) and condition.

Unique ID
Unique ID of the alarm.

Alarm Info
with specified Source Name.
Displays the Acknowledged alarms that match

Ack the search terms (if the Search Term is false it
displays the Not Acknowledged Alarms).

User
with the specified User.

Displays the Last Acknowledged Alarms based
Last Acknowledged
on a Search Date.

Alarm Count
with the specified Alarm count.
Displays First Raised Alarms based on a Search

First Raised
Date.
Displays the Last Raised Event based on a

Last Raise Event
Search Date.
Last Cleared Displays the alarms that were last cleared.
MAC Address Displays the MAC address of the source node.
 Using Search - Select the preferred search criterion list from the Filter drop-down box and
then click on Search to get the results.
2.4 Viewing Alarm Type Description

Netspan allows you to view details of each alarm and add your own description about the alarms.
To view details of an alarm type:
1. Go to the Alarm Types page.
2. Select the alarm, whose details you want to view.
3. Click the Edit button or double-click the selected alarm.
To add new details about an alarm type:
1. Go to the Alarm Types page.
2. Select the alarm about which you want to add more details.
3. Click the Edit button or double-click the selected alarm. The Edit Alarm Type page appears.
4. Under Descriptions, type the information in the User Description box.
Table 4 lists the details of all the fields that you can find on the Edit Alarm Type page.
Table 4. Alarm Type Properties and Descriptions
Property Description
Name Provides the name of the alarm.
Properties
Severity Specifies the default severity level of the alarm.
Raise Specifies whether the alarm can be raised or not.
Specifies whether this alarm is forwarded by the NBIF

Forward
(if the NBIF alarm forwarding is configured).
Specifies whether alarm synchronization is enabled for

Alarm Sync Enabled
that alarm type.
Specifies the number of hours after which a cleared

Auto Delete Cleared Time
alarm is deleted automatically.
Category Specifies the category of the alarm.

ITU Event Type Specifies the ITU event type of the alarm.
Descriptions
Probable Cause Lists the possible causes that triggered the alarm.
Description Provides the description of the alarm.
Use this field to add your own descriptions, as

User Description
discussed previously.
2.5 Viewing Alarm Description

To view details of an alarm:
1. Go to the Active Alarms or Historical Alarms page.
2. Select the alarm, whose details you want to view.
3. Click the Edit button or double-click the selected alarm.
To add new details about an alarm:
1. Go to the Active Alarms or Historical Alarms page.
2. Select the alarm about which you want to add more details.
3. Click the Edit button or double-click the selected alarm. The Alarm Details page appears.
4. Type the information in the Comments box.
Table 5 lists the details of all the fields that you can find on the Edit Alarm page.
Table 5. Alarm Properties and Descriptions
Alarm Type Specifies the alarm type.
Specifies the name of the managed element for which

Source Name
the alarm is raised.
Specifies the ID of the managed element for which the

Source ID
alarm is raised.
Specifies the ID of the selected alarm.

Alarm ID Note: Netspan generates a unique alarm ID for every
new alarm.
Alarm Properties
Alarm Info Provides information on the selected alarm.
Severity Specifies the current severity level of the alarm.
If selected, it indicates that a specific user is

Acknowledged
investigating that alarm.
Specifies the name of the user who acknowledged the

User Name
alarm (if the alarm is acknowledged).
First Raised Specifies the date on which the alarm was first raised.
Last Raised Specifies the date on which the alarm was last raised.
Specifies the number of times the alarm changed from

Alarm Count
the cleared to raised state.

Specifies the number of events raised for the selected

Number of Raise Events
alarm.
Comments Lists the user-defined comments.
Alarm Type Properties
ITU Event Type Specifies the ITU event type of the alarm.
Probable Cause Lists the possible causes that triggered the alarm.
Description Provides the description of the alarm.
User Description Lists the user descriptions.
Alarm History
Lists the history of the alarm status changes.
2.6 Acknowledged and Unacknowledged Alarms

An acknowledged alarm indicates that a specific user is investigating that alarm. Any users can
acknowledge the alarms.
To acknowledge an alarm:
1. On the main menu, select Fault Management > Active Alarms. The Active Alarms page
appears.
2. Select the alarm that you want to acknowledge.
Note: You can acknowledge multiple alarms simultaneously.
3. Click the Acknowledge button.

An unacknowledged alarm indicates that the user is no longer investigating that alarm. The alarms can
be unacknowledged only by the administrator or by the user who acknowledged the alarm.
To unacknowledge an alarm:
appears.
2. Select the acknowledged alarm that you want to unacknowledge.
3. Click the Unacknowledge button.
2.7 Deleting an Active Alarm

Note: Airspan recommends not to delete an active alarm without identifying the root cause and
resolving the fault. Otherwise, the alarm might recur.
To delete an active alarm, perform the following steps:

appears.
2. Select the alarm that you want to delete.
3. Click the Delete button.
To view the deleted alarms, go to the Historical Alarm page. The Historical Alarm page lists all the
deleted and active alarms.
To view the historical alarms, on the main menu, select Fault Management > Historical Alarms.

2.8 Exporting Alarms View into an Excel File

To export the alarms view into an Excel file containing details of all the alarms, click Export (at the
bottom of the page).
2.9 Refreshing an Alarms Page

To refresh a page, click the Reload or Reload Page button.
Tip: To enable automatic reload, select Auto On (if available on the selected page).
2.10 Alarm Synchronization

Alarm synchronization is automatic if there is a communication loss between Netspan and any node
that it manages. Netspan periodically synchronizes with the node and if it detects any mismatches, it
generates an event for that alarm.
If there is a communication loss between Netspan and an external OSS system over NBIF, then the
OSS should resynchronize its alarm state with the Netspan alarm state.
Once the interface regains connectivity, the OSS system can call any of the following methods to
resynchronize with Netspan over its SOAP/HTTP based NBIF:
 AlarmList - Returns a list of active alarms.
 AlarmListChanged - Returns a list of active alarms that changed since the specified time.
To access these methods in Netspan, go to
http://server_name/ws/webservice_version/FaultManagement.asmx.
Where:
server_name is the name of the Netspan server
webservice_version is the web service version
For more information on the available web service versions, see the Netspan NBIF Product
Specification.
2.11 Purging Alarms

By default, Netspan retains 1000000 alarms and performs automatic database purging when the
database exceeds the specified limit.
Netspan purges alarms based on the following criteria (in the given order):
a. Deletes the oldest historical alarms
b. Deletes the oldest cleared active alarms
Netspan also limits the alarm status changes (Fault Management > Active Alarms or Historical
Alarms > Alarm Details > Alarm History) to 100 x number of alarms with a minimum value of
1000000 and a maximum value of 10000000.

Figure 1: Alarm History
Note: Users cannot configure the number of alarms that Netspan retains.
2.12 Alarm Types

To view the list of the Netspan alarm types, on the main menu, select Fault Management > Alarm
Types.
Table 6 shows how the information on each alarm is structured in this section.
Table 6. Alarm Definition Structure
Provides a brief description of the alarm and its

Description/Probable Cause
possible cause.
Provides information on the applicable technology.

Note: In this document:
Applicable Technology  iBridge LOS refers to iBridge 440.
 iBridge NLOS refers to iBridge 300, 400, and
460.
Specifies the severity level of the alarm.

Severity For more information on alarm severity, see Alarm
Severity Levels.
Category Specifies the category of the alarm.
Specifies the ITU event type of an alarm, which can

be one of the following:
 Other
 Communications Alarm
ITU Event Type
 Quality of Service Alarm
 Processing Error Alarm
 Equipment Alarm
 Environmental Alarm

 Integrity Violation
 Operational Violation
 Physical Violation
 Security Service or Mechanism Violation
 Time Domain Violation
Explains how the system automatically resolves the

Clearing
fault and clears the alarm.
Provides the details of the appropriate corrective

Recommended Actions
actions.
Table 7 provides an alphabetical list of the Netspan alarms.

Table 7. Alarms
 Access Point Connection Fault  Node Invalid Configuration
 All MME Connectivity Lost (per  Node Local Access Attempt

PLMN)
 Node Loss of Sync
 ASN R6 Comms Loss
 Node Lost Comms
 ASN R6 Standby Comms Loss
 Node Out of Service (OOS)
 Authorization Failure
 Node Power Unacceptable
 Auto RSI Config Invalid
 Node Provisioning Error
 Auto-Align Failed
 Node PTP Degraded Stream
 Auto-Align In-Progress
 Node PTP Grand Master Lost
 Auto-PCI Allocation Failed
 Node Self Test Failed
 Auto-PCI Collision Not Resolved
 Node Shutdown
 Auto-PCI Confusion Not Resolved
 Node Software Version Status Changed
 Auto-PCI Policy Violation Not
Resolved  Node Temperature Unacceptable
 Backhaul QoS BW Server  Node Timing Frame Lock Lost

Connection
 Node Voltage Unacceptable
 Backhaul QoS Service Affecting
 NTP Failure
 Backhaul QoS Service Capacity
Limiting  Operator Certificate Expired
 Battery Overtemperature (eNodeB)  Outdoor Cell is Out of Service
 Battery Overtemperature (WiFi)  P1 CDCL Selection Failure
 CBSD State Change Failure  P1 PDCL Selection Failure

 Cell 1 CLPC Disabled  PCI Conflict Not Resolved
 Cell 1 Transmission Disabled  PCI Update Failure
 Cell 2 CLPC Disabled  PDCL Selection Failure
 Cell 2 Transmission Disabled  PLL Lock Lost
 Cell is Not Active  PnP Configuration Mismatch
 Cell Outage Detected  PnP Location Changed
 Channel Action Error  Port Disable Prevention
 Channel Out of Service (OOS)  PTP Clock Sync
 Channel Provisioning Error  PTP Hardware Fault
 CMS Mismatch  QoS Handover Neighbour Does Not

Exist
 CTS eNB Capacity Exceeded
 QoS Server Connection Failure
 CTS Log Overwritten
 Remote Connection Lost
 CTS Logging Stopped
 RF FEM Fault
 CTS PTE Auto Disabled
 RF FEM Not Present
 CTS PTE Destination Folder Access
Denied  RF Hardware Fault
 CTS Server Down  RF Out of Service (OOS)
 CTS Time Sync Failed  RF1 Carrier Sense Frequent

Interference
 CTS Trace Analysis Failed
 RF1 Carrier Sense Interference
 DHCP T2 Timer Expired
 RF1 Configuration Fault
 Donor Cell Poor Backhaul Quality
 RF1 Hardware Fault
 Enabled Port Down
 RF1 Hardware Fault (Warning)
 eNodeB is in Holdover
 RF1 Temperature Fault
 eNodeB is in Holdover Expired
 RF1 Transmitter Off
 eNodeB PDN Mismatch
 RF1 VSWR Fault
 eSON Server Connection Lost
 RF2 Carrier Sense Frequent
 ETWS SFTP Session Error Interference
 Ext PPS Not Locked  RF2 Carrier Sense Interference
 Forced Management Mode Failure  RF2 Configuration Fault

 Frame Synchronised to Internal  RF2 Hardware Fault

Clock
 GPS Alarms Status Failure
 GPS File Failure
 GPS Lost Comms
 RF2 VSWR Fault
 GPS Lost Satellite Lock
 GPS Persistency Lost
 GPS Signal Unacceptable
 GPS SNR Low
 High Antenna Imbalance
 IKEv2 SA Expired
 RF3 VSWR Fault
 Inventory Error
 IP Conflict
 IPsec SA Expired
 iRelay FEM Error
 Link Down
 Low CPU Resources
 RF4 VSWR Fault
 Low Memory Resources
 SAS Grant Failure
 Low RRC Resources
 SAS Grant Suspended
 MBSFN SF Configuration Conflict
 SAS Heartbeat Failure
 MCE Connectivity Lost
 SAS Registration Failure
 SAS Registration Suspended
 MME Connectivity Lost
 SAS Server Disconnected
 MME PLMN Overload Service
Interruption  SAS Spectrum Inquiry Failure
 MME PLMN Overload Without  SBA Misconfiguration

Service Interruption
 Scan In Progress
 Motor Failure
 Server CPU Usage High
 Motor Pending Failure
 Server Disk Usage High
 MSM Failure

 MSM Port Failure  Server Event Queue Size High
 Neighbour Addition Rejected  Server Memory Usage High
 NetspanSF Node Config Error  Serving Netspan Address Mismatch
 NetspanSF Server Error  Serving Security Gateway Mismatch
 NL Sync Clock Source Error  S-GW Connectivity Lost
 NL Sync Procedure Error  SNMP Authentication Failure
 NLM Frequency Scan Warning  SNMPv3 Fallback
 No PTP Master Available  Software Activate Failure
 Node 10Mhz Clock Failure  Software Download Failure
 Node Action Error  Software Upgrade Fault
 Node Call Trace Server Connection  SS Action Error

Lost
 SS Provisioning Error
 Node Clock Source Lost
 SS RSSI
 Node Clock Source Unavailable
 Sync Switched Exceeded
 Node Config Status Changed
 System Information Truncation
 Node Current Unacceptable
 Tamper Detect
 Node Disk Full
 Tamper Detect And Disabled
 Node Encryption Licence Invalid
 Tilt Threshold Exceeded
 Node Feature Licence Expired
 TWAMP Overloaded
 Unsupported Clock Source
 Node Feature Not Implemented
 VoiceMAX Lost Comms
 WiFi Board Connectivity
 Node in Holdover
 WiFi Board Initialization
 Node in Maintenance Mode
 X2 Neighbour Comms Loss
 Node Internal Clock

Access Point Connection Fault
An access point tried to obtain a PDN connection, but

failed for a reason unrelated to RF connectivity. It
Description/Probable Cause indicates that the device is unable to establish
backhaul for a connected access point due to
configuration problems.
Alarm Type ID 634
Applicable Technology Relay
Severity Critical
Category Connected
ITU Event Type Communications Alarm
Clearing Automatic
Do one of the following:

 Initiate a reboot (that is, a Force Reset).
Recommended Actions  Review the APN configuration in the Relay
Profile.
 Access the unit over the management APN
and ping the access device.
All MME Connectivity Lost (per PLMN)
Raised when the eNodeB is unable to communicate

with all configured MMEs for a specific configured
Description/Probable Cause PLMN.
It is caused by the loss of S1 connection with the
MME.
Alarm Type ID 669
Applicable Technology eNodeB
Severity Critical
Category Node
Clearing Automatic
Recommended Actions Check the available MMEs and restart them.

ASN R6 Comms Loss
The BS is unable to communicate with the ASN-GW.

The link between the BS and ASN-GW failed.
Alarm Type ID 519
Applicable Technology WiMAX 16e
Severity Critical
Category BS
Clearing Automatic
Troubleshoot the connectivity between the BS and

Recommended Actions
ASN-GW.
ASN R6 Standby Comms Loss
The BS is unable to communicate with the standby

Description/Probable Cause ASN-GW. The link between the BS and the standby
ASN-GW failed.
Alarm Type ID 542
Severity Warning
Category BS
Clearing Automatic
Troubleshoot the connectivity between the BS and

Recommended Actions
the standby ASN-GW.
Authorization Failure
An SS or iBridge term with invalid credentials is

attempting to gain service on the node.
Alarm Type ID 62
iBridge NLOS,
Applicable Technology
WiMAX 16e
Severity Minor
Category

ITU Event Type Security or Mechanism Violation
Clearing Automatic
Recommended Actions Check the configuration and security certificates.
Auto RSI Config Invalid
An alarm is raised when the RSI list size is changed

to be smaller than the PCI list size.
Alarm Type ID 577
eNodeB,
Relay eNodeB
Severity Warning
Category Node
ITU Event Type Equipment Alarm
Clearing Automatic
Recommended Actions N/A
Auto-Align Failed
The auto-alignment process has not completed

Description/Probable Cause successfully. This occurs when the user has explicitly
requested to abort the auto-alignment process.
Alarm Type ID 596
Applicable Technology iBridge NLOS
Severity Warning
Category Node
This alarm is cleared when the user initiates the next

Clearing
auto-alignment process.
Recommended Actions None

Auto-Align In-Progress
Description/Probable Cause Indicates that the Auto-Align process is in progress.
Alarm Type ID 617
Severity Warning
Category Node
Clearing Automatic
Recommended Actions Not applicable
Auto-PCI Allocation Failed
Description/Probable Cause Automatic allocation of the PCI failed.
Alarm Type ID 565
eNodeB,
Relay eNodeB
Severity Critical
Category Node
ITU Event Type Other
Clearing Automatic
Resolve the cause of the PCI allocation failure.

For more information, go to SON Status on the
Status tab of the Node Management page.
Recommended Actions You might need to do the following:
1. Perform configuration changes to the assigned
SON profile.
2. Reallocate the PCI from the Node Edit page.
Auto-PCI Collision Not Resolved
A PCI collision is detected. There is an NRT change

Description/Probable Cause in which the node has been identified with the same
PCI as one of its first degree neighbor.
Alarm Type ID 622

Severity Critical
Category Node
PCI collision resolved by a new PCI allocation or by

Clearing
colliding neighbor.
Recommended Actions Check the allocated PCI.
Auto-PCI Confusion Not Resolved
Detected PCI confusion or allocation policy violation:

 PCI confusion: The node has the same PCI as
one of its second degree neighbor.
 Allocation policy violation: The selected PCI
does not any longer comply with the configured
allocation policy.
Alarm Type ID 623
Severity Major
Category Node
PCI confusion/allocation policy violation is resolved

Clearing
either by new PCI allocation or by colliding neighbor.
Recommended Actions Check the allocated PCI.
Auto-PCI Policy Violation Not Resolved
Auto-PCI Policy Violation could not be resolved in

current maintenance window.
Alarm Type ID 645
Severity Minor
Category Node
Clearing Automatic
Recommended Actions Check Auto PCI status.

Backhaul QoS BW Server Connection
Indicates the BW server connection failure. A

Description/Probable Cause communication with the BW reservation server or the
initial MBR has failed.
Alarm Type ID 657
Severity Critical
Category Node
Clearing Automatic
Check the reservation server FQDN and IP

Recommended Actions
addresses.
Backhaul QoS Service Affecting
Indicates a major degradation in the number of

acceptable VoLTE calls due to degraded BH QoS.
Alarm Type ID 642
Applicable Technology Relay eNodeB
Severity Critical
Category Node
Clearing Automatic
Perform manual scanning to find a better cell or try

Recommended Actions
shifting the unit (a technician must be involved).
Backhaul QoS Service Capacity Limiting
Indicates a minor degradation in the number of

acceptable VoLTE calls due to degraded BH QoS.
Alarm Type ID 643
Severity Critical
Category Node

Clearing Automatic
Perform manual scanning to find a better cell or try

Recommended Actions
shifting the unit (a technician must be involved).
Battery Overtemperature (eNodeB)
This parameter indicates that eNodeB has been

Description/Probable Cause disabled as the temperature has exceeded the
threshold.
Alarm Type ID 655
Severity Critical
Category Node
ITU Event Type Environment Alarm
Clearing Automatic
Recommended Actions No manual action required.
Battery Overtemperature (WiFi)
This parameter indicates that Wi-Fi has been

Description/Probable Cause disabled as the temperature has exceeded the
threshold.
Alarm Type ID 654
Severity Critical
Category Node
Clearing Automatic
Recommended Actions No manual action required.

CBSD State Change Failure
The probable causes include:

o Failure of CBSD to reach the authorized state
o SAS communication failure
o Expiry of grant
Alarm Type ID 182
Severity Critical
Category BS
Clearing Automatic
Use the CBSD Management page (Configuration

Recommended Actions Management > Node > CBSD Management) to
investigate further about the issue.
Cell 1 CLPC Disabled
Cell 1 CLPC disabled. CLPC will not correct a

Description/Probable Cause correction that is above limitation threshold (too-
large).
Alarm Type ID 666
Severity Minor
Category Cell1
Clearing Auto
Recommended Actions Contact Airspan support.
Cell 1 Transmission Disabled
Cell 1 Transmission disabled. Cell 1 Status Event

raised with OOS bit=’1’ (out of service).
Alarm Type ID 664
Severity Critical

Category Cell1
Clearing Auto
Perform the following steps:

 Check the configuration.
Recommended Actions
 Confirm whether it is a hardware failure.
 If confirmed, replace the hardware.
Cell 2 CLPC Disabled
Cell 2 CLPC disabled. CLPC will not correct a

Description/Probable Cause correction that’s above limitation threshold (too-
large).
Alarm Type ID 667
Severity Minor
Category Cell2
Clearing Auto
Recommended Actions Contact Airspan support.
Cell 2 Transmission Disabled
Cell 2 Transmission disabled. Cell 2 Status Event

raised with OOS bit=’1’ (out of service).
Alarm Type ID 665
Severity Critical
Category Cell2
Clearing Automatic

Recommended Actions
 Confirm whether it is a hardware failure.
 If confirmed, replace the hardware.

Cell is Not Active
This alarm is raised when there is no activity in the

cell during selfHealingNonActivityTimer.
Description/Probable Cause This alarm is triggered when the following occurs:
 Expiry of selfHealingNonActivityTimer expired
 SelfHealing non-activity reboot = False
Alarm Type ID 668
Severity Critical
Category Node
 Reboot the node to manually clear this

alarm.
Clearing
 This alarm is automatically cleared upon the
receipt of a new RRC command.
Recommended Actions Reboot the eNodeB.
Cell Outage Detected
Cell outage detected on a cell in an eNodeB by a

centralized SON system.
Alarm Type ID 597
Applicable Technology Centralized SON server
Severity Critical
Category Node
Cleared when centralized SON system detects that

Clearing
the cell is in service.
Perform the following:

1. Select the State and Control tab, and then
verify that the cell is not manually set to the Out
Recommended Actions
of Service state.
2. Select the Status tab and verify the values
under the RF and Sensor status types.

Channel Action Error
A problem in performing an action on the specified

channel.
Alarm Type ID 110
Applicable Technology WiMAX 16d
Severity Minor
Category BS
ITU Event Type Processing Error Alarm
Clearing Automatic
To rectify, re-provision the specified channel.

To re-provision the specified channel, perform the
following steps:
Recommended Actions 1. Go to the channel management page.
2. Click the State and Control tab.
3. Under Re-provisioning and Actions, click the
Re-provision button.
Channel Out of Service (OOS)
Channel OOS can be a result of the management

configuration, or an underlying hardware or software
issue (in that case, it is accompanied by another
alarm).
Alarm Type ID 557
eNodeB,
Relay eNodeB
Severity Critical
Category Node
Clearing Automatic
Select the State and Control tab, and then verify that
the cell is not manually set to the Out-of-Service
state.
Recommended Actions If this alarm is accompanied by another alarm (for
example, MME Connectivity Lost, RF Transmitter
Off), follow the recommended actions to clear those
alarms.

Channel Provisioning Error
A problem in configuring the per-Channel

configuration on the specified channel.
Alarm Type ID 103
eNodeB,
iBridge NLOS,
Relay eNodeB,
WiMAX 16e/16d
Severity Minor
Category BS
Clearing Automatic
To rectify, re-provision the specified channel.

To re-provision the specified channel, perform the
following steps:
Recommended Actions 1. Go to the channel management page.
CMS Mismatch
This alarm indicates the CMS FQDN and IP address

Description/Probable Cause are missing in option 43 or CMS IP address is given
in the PDN type other than eNBpdntype.
Alarm Type ID 674
Severity Major
Category Node
Clearing Automatic
Reconfigure the CMS FQDN/IP in VSI (in dns-sd or

Recommended Actions
DHCP option 43 record).

CTS eNB Capacity Exceeded
More than 10000 eNodeBs tried to log to a specific

CTS simultaneously.
Alarm Type ID 414
Applicable Technology CTS
Severity Minor
Category CTS
Clearing Manually select OK in the Trace Server UI.
Create another server and assign new eNodeBs to it

Recommended Actions
or remove selected eNodeBs from the CTS.
CTS Log Overwritten
The CTS depleted its log storage space and starts

Description/Probable Cause overwriting old logs in FIFO manner (oldest is deleted
first).
Alarm Type ID 413
Severity Warning
Category CTS
Automatic when the storage space on the CTS goes

Clearing
below the watermark set by the user.
No action required if configured FIFO policy is

Recommended Actions
acceptable.
CTS Logging Stopped
The CTS depleted its log storage space and stops

Description/Probable Cause logging along with the server’s IP address and name,
if configured.
Alarm Type ID 412
Severity Major
Category CTS

Automatic when the storage space on the CTS goes

Clearing
below the watermark set by the user.
Recommended Actions Clear space on the CTS by archiving old logs.
CTS PTE Auto Disabled
Trace Server depleted its log storage space and

Description/Probable Cause disabled PTE with the server’s IP address and name,
if configured.
Alarm Type ID 418
Applicable Technology Call Trace Server
Severity Major
Category CTS
ITU Event Type Operation Violation
Clearing Auto
Clear space on the Call Trace server by archiving old

Recommended Actions
logs and extract files.
CTS PTE Destination Folder Access Denied
PTE destination folder does not exist or has access

Description/Probable Cause issues with the server’s IP address and name, if
configured.
Alarm Type ID 417
Applicable Technology Call Trace Server
Severity Major
Category CTS
ITU Event Type Operation Violation
Clearing Automatic
Create destination folder and provide copy/delete

Recommended Actions
access.

CTS Server Down
This alarm could be raised in one or more of the

following scenarios:
 Trace Log Start messages were not
acknowledged for the configured amount of
attempts.
 Trace Log Start messages were not
Description/Probable Cause acknowledged for the configured amount of
attempts and trace end time has reached.
 Trace Log Keep-Alive messages were not
acknowledged for the configured amount of
attempts.
 Lost communication to the CTS, along with the
server’s IP address and name, if configured.
Alarm Type ID 411
eNodeB,
Relay eNodeB
Severity Major
Category CTS
 Communication regained to the Trace Server

Clearing (from Netspan)
 Trace Log Start acknowledged (from eNodeB)
Verify the following:

1. The IP connectivity to the specified CTS
2. The specified CTS is operational
3. Check communications between the CTS and
the eNodeB.
Recommended Actions
the eNodeB and the IP configuration on the
eNodeB for the CTS.
the eNodeB and the IP configuration on the
eNodeB for the CTS.
CTS Time Sync Failed
Description/Probable Cause The CTS was unable to sync with a time server.
Alarm Type ID 416
Severity Major
Category CTS

Check the communications and the configuration for

Recommended Actions
the NTP server.
CTS Trace Analysis Failed
The CTS was unable to analyze the data received

from the eNodeB (for example, corrupted data).
Alarm Type ID 415
Severity Minor
Category CTS
Check if corruption is for all data from a particular

Recommended Actions eNodeB. In that case, consider rebooting the
eNodeB.
DHCP T2 Timer Expired
Relay eNodeB reports that its cell is out of service.

Description/Probable Cause There is no response for the renewal request from
the DHCP server.
Alarm Type ID 625
Severity Major
Category Node
Clearing Automatic

1. Check DHCP server settings for the eNodeB
Recommended Actions
part of the Relay eNodeB.
2. Reboot the Relay eNodeB.

Donor Cell Poor Backhaul Quality
Indicates that the serving DeNB RF quality has fallen

below the SINR/SE thresholds.
Alarm Type ID 621
Relay,
Relay eNodeB
Severity Major
Category Node
Clearing Automatic
Investigate whether the DeNB Tx power has been

Recommended Actions changed and perhaps schedule a rescan at a suitable
time.
Enabled Port Down
Description/Probable Cause The operational status of an active port is down.
Alarm Type ID 595
eNodeB,
Relay eNodeB
Severity Minor
Category Node
Clearing Automatic

1. Check the port connectivity on both ends of the
Recommended Actions cable.
2. Disconnect and reconnect the cable from the
failed port.
eNodeB is in Holdover
The eNodeB reports that it moved to a Holdover

state.
Alarm Type ID 662

Severity Minor
Category Node
Clearing Automatic
Recommended Actions Check the configured clock sources.
eNodeB is in Holdover Expired
The eNodeB reports that it moved to a Holdover

Description/Probable Cause Expired state. It indicates that the eNodeB has lost
clock sync and holdover timeout has expired.
Alarm Type ID 672
Severity Critical
Category Node
Clearing Automatic
Recommended Actions Check the configured synchronization sources.
eNodeB PDN Mismatch
Indicates a mismatch between the eNodeB and Relay

PDN types.
Description/Probable Cause The backhaul APN for the eNodeB is configured to be
IPv6, when the backhaul APN for the relay UE
management is IPv4.
Alarm Type ID 675
Severity Major
Category Node
Cleared when the Relay management APN is

Clearing changed to IPv6, or when the eNodeB APN is
changed to IPv4.

 Verify that the Relay management APN is

using the expected IP version; if not, initiate
Recommended Actions a cold reset of the node.
 Update the Relay profile configuration so that
the eNodeB access APN is IPv4.
eSON Server Connection Lost
Description/Probable Cause The connection with the eSON server is lost.
Alarm Type ID 579
eNodeB,
Relay eNodeB
Severity Major
Category Node
Clearing Automatic
An eNodeB has lost its connection to the configured

eSON server, and is trying to re-establish
connectivity. If this alarm doesn’t clear automatically,
Recommended Actions verify the following:
1. The IP connectivity to the specified eSON server.
2. The specified eSON server is operational.
ETWS SFTP Session Error
SFTP session did not open or was closed due to an

error.
Alarm Type ID 650
Applicable Technology eNB
Severity Warning
Category Node
Clearing Automatic
Recommended Actions Check the SFTP server availability.

Ext PPS Not Locked
Description/Probable Cause External PPS lost sync.
Alarm Type ID 618
Severity Warning
Category Node
Clearing Automatic
Check the external PPS source to see if there is a

Recommended Actions
clock drift.
Forced Management Mode Failure
iRelay could not establish backhaul connection

(apn2) for backhaul service to RNeNB (MM), but it
managed to connect to the management system
using apn1.
Alarm Type ID 610
Relay,
Relay eNodeB
Severity Major
Category Node
Cleared by the configuration change triggered by the

Clearing
management system.

1. Check the configuration.
Recommended Actions 2. Verify RF parameters of cells reported in the
CDCL.
3. Correct the configuration or adjust the
equipment location.

Frame Synchronized to Internal Clock
System is configured to use the lab mode of the

operation where internal clock is used without
Description/Probable Cause synchronisation to the GPS or PTP. If this mode is
used OTA, there is a risk of interference with other
nodes.
Alarm Type ID 545
iBridge NLOS,
WiMAX 16e
Severity Warning
Category BS
Clearing Automatic
Check the configuration, and change the

Recommended Actions configuration of the clock source to use the GPS or
PTP.
GPS Alarms Status Failure
The GPS module reported an alarm. It indicates the

GPS module startup phases or a failure.
Description/Probable Cause The system clock might not be synchronised to the
GPS, and the RF subsystem might have disabled the
transmitter to prevent interference with other nodes.
Alarm Type ID 214
iBridge NLOS,
WiMAX 16e/16d
Severity Minor
Category GPS
Clearing Automatic

1. Check the GPS module.
Recommended Actions
2. Check the GPS antenna connection (for the
node with the cable connected antenna).

GPS File Failure
The node fails to download the updated A-GPS file or

the A-GPS file has been deleted from the node.
Alarm Type ID 632
Severity Warning
Category Node
When the A-GPS file download is successful, the

Clearing
alarm will be cleared automatically.

1. Check if the A-GPS offline URL is received in
Recommended Actions DHCP options.
2. Check if the A-GPS offline URL is accessible
from APN1 interface.
GPS Lost Comms
The Node or BSDU module lost communication with

the GPS module.
The GPS module might be misconfigured and the
status reporting is not available. The system clock
might lose synchronisation.
The possible cause is the failure of the GPS module.
Alarm Type ID 203
eNodeB,
iBridge NLOS,
Applicable Technology Relay,
Relay eNodeB,
WiMAX 16e/16d
Severity Minor
Category GPS
Clearing Automatic

1. Check connections with the GPS module.
Recommended Actions
2. Reboot the node.
3. If the condition persists, replace the hardware.

GPS Lost Satellite Lock
The Node or BSDU GPS module lost the timing lock

with the satellites.
Description/Probable Cause If the system clock is not synchronised to the GPS,
the RF subsystem disables the transmitter to prevent
interference with other nodes.
Alarm Type ID 204
iBridge NLOS,
Relay,
Relay eNodeB,
WiMAX 16e/16d
Severity Warning
Category GPS
Clearing Automatic

1. Check the GPS module.
Recommended Actions 2. Check the GPS antenna connection (for the
3. Check the GPS antenna sky view.
GPS Persistency Lost
Indicates iRelay was moved to a new location, which

Description/Probable Cause falls outside the configurable radius from the location
where full PnP was performed.
Alarm Type ID 609
Relay,
Relay eNodeB
Severity Major
Category Node
Once the unit is reset to the factory configuration and

Clearing full PnP sequence is rerun, this alarm clears
automatically.
Check the configuration. Inspect the location in the

Recommended Actions field. If the new location is valid, reset the unit to the
factory configuration, and rerun full PnP sequence.

GPS Signal Unacceptable
The GPS receiver on the unit is not able to detect

suitable satellites and is currently unlocked. This can
be the result of bad satellite visibility or a hardware
fault in the GPS cable or antenna.
Alarm Type ID 224
Severity Major
Category GPS
Clearing Automatic
If this condition persists, check the GPS antenna and

Recommended Actions
cabling.
GPS SNR Low
The node reports a GPS receiver alarm. The GPS

module detected a low SNR of the GPS signal.
This alarm is an indication of a poor signal level and it
might lead to a lock loss.
The probable causes include:
Description/Probable Cause  The Node GPS module has a low SNR (that is,
Node GPS Receiver Status reports SNR
Low).
 The GPS antenna is faulty.
 The GPS antenna cable is faulty.
 The sky view is limited or partially obstructed.
Alarm Type ID 213
iBridge (all variants)

Relay eNodeB
Applicable Technology Note: This alarm applies to eNodeBs up to SR14.01
(inclusive) only. eNodeBs post SR14.01 do not
generate this alarm.
Severity Minor
Category GPS
Clearing Automatic

Recommended Actions 1. Check the GPS antenna connection (for the

2. Check the GPS antenna sky view.
High Antenna Imbalance
The signal quality is affected and it might become

impossible to use MIMO Matrix B.
High antenna imbalance might be a result of the
hardware failure or a bad NLOS radio condition.
Alarm Type ID 564
Severity Minor
Category Node
Clearing Automatic
Check the antenna direction (the physical direction

Recommended Actions for the directional antenna and the software selected
direction for the SBA).
IKEv2 SA Expired
The eNodeB is unable to complete the IKEv2

Description/Probable Cause rekeying process with the SeGW. The IKEv2 SA is
about to expire (that is, the traffic will be lost).
Alarm Type ID 590
eNodeB,
Relay eNodeB
Severity Critical
Category Node
Once the eNodeB successfully completes IKE SA

Clearing
rekeying, this alarm clears automatically.
Check the SeGW reachability and connectivity to the

Recommended Actions
eNodeB.

Inventory Error
This alarm can occur due to the following reasons:

 For Relay/Relay eNodeB: If the ranges file is
missing or invalid.
 For Relay/Relay eNodeB and iBridge: If any
Description/Probable Cause of the following is missing:
o Main board inventory MAC address.
o Serial number.
o Equipment product code.
Alarm Type ID 601
iBridge LOS and NLOS,

Relay eNodeB
Severity Critical
Category Node
To clear this alarm, the unit must undergo ATE

Clearing
process.
Contact Airspan Customer Service Help Desk and

Recommended Actions send the unit back to the factory. To resolve this
issue, the unit must undergo the ATE process.
IP Conflict
Description/Probable Cause IP conflict.
Alarm Type ID 633
Applicable Technology All Node Types
Severity Major
Category Node
Clearing Auto
Search for the Node with the duplicate IP address

Recommended Actions and delete or correct the Node with the duplicate IP
Address

IPsec SA Expired
The eNodeB is unable to renew the IPsec SA. The

Description/Probable Cause IPsec SA is about to expire (that is, the traffic will be
lost).
Alarm Type ID 589
eNodeB,
Relay eNodeB
Severity Critical
Category Node
Once the eNodeB successfully completes IPsec SA

Clearing
renewal, this alarm clears automatically.
Check the SeGW reachability and connectivity to the

Recommended Actions
eNodeB.
iRelay FEM Error

 calibrationFault: The ranges file is missing or
invalid.
 calibrationFault: The FEM calibration file or
files are missing or invalid.
 initialisationError: The FEM failed to initialize.
 unSupportedBand: Received an unsupported
band configuration from the application
software. This is highly unlikely to happen.
 freqOutOfRange: Request received to
configure the FEM with frequencies outside the
range of the band. This is highly unlikely to
happen.
Alarm Type ID 598
Relay,
Relay eNodeB
Severity Critical
Category Node
To clear this alarm, the unit must undergo the ATE

Clearing
process.
Contact Airspan Customer Service Help Desk and

Recommended Actions send the unit back to the factory. To resolve this
issue, the unit must undergo the ATE process.

Link Down
One of the network interfaces reported the Link

Down operational state.
The possible causes include:
 One of the network or radio interfaces is not
operational.
 The Ethernet cable is disconnected (for
example, the Ethernet connection with other
hosts connected to the same network is lost) or
the Ethernet interface is faulty.
 Loss of connection to the infrastructure
Description/Probable Cause network.
For iB460:
 IfIndex 2: eth1―external physical Ethernet
port.
 IfIndex 3: eth0―internal physical Ethernet port
(fit on iB460, fit on iB400).
For iRelay:
 IfIndex 2: eth0―physical Ethernet port.
 IfIndex 3: eth1―virtual apn1 port.
Alarm Type ID 11
iBridge LOS,
iBridge NLOS,
Relay eNodeB,
WiMAX 16e/16d
Severity Major
Category AMP
Clearing Automatic

Recommended Actions 1. Inspect the detailed status using the EMS.
2. Check the Ethernet cable.
Low CPU Resources
Description/Probable Cause eNB CPU utilization is above threshold.
Alarm Type ID 635
Applicable Technology LTE
Severity Warning

Category Node
Clearing Automatic
Monitor the unit for any performance changes and if

Recommended Actions any impact is noticeable contact Airspan Technical
Support.
Low Memory Resources
Description/Probable Cause eNB Memory utilization is above threshold.
Alarm Type ID 636
Severity Warning
Category Node
Clearing Automatic
Monitor the unit for any performance changes and if

Recommended Actions any impact is noticeable contact Airspan Technical
Support.
Low RRC Resources
Description/Probable Cause eNB RRC utilization is above threshold.
Alarm Type ID 637
Severity Warning
Category Node
Clearing Automatic
Recommended Actions N/A

MBSFN SF Configuration Conflict
The latest MBMS scheduling information message

contained a conflict between two or more MBSFN SF
Description/Probable Cause configurations; the eNodeB is in the Awareness mode
and will not participate in eMBMS service until the
conflict is cleared.
Alarm Type ID 583
eNodeB,
Relay eNodeB
Severity Major
Category Node
Once the eNodeB receives the M2 MBMS scheduling

information containing no MBSFN SF configuration
Clearing
conflict, eNodeB sends an MBSFN SF Configuration
Conflict Resolved trap).
Recommended Actions Wait till the conflict is resolved.
MCE Connectivity Lost
The M2 interface towards MCE is down and the

eNodeB is in the Awareness mode and will not
participate in eMBMS service until the MCE
connectivity is restored.
Alarm Type ID 582
eNodeB,
Relay eNodeB
Severity Major
Category Node
Once the M2 connectivity is restored, the eNodeB

Clearing
sends an M2 Connectivity Established trap.
Check the MCE status and IP connectivity to the

Recommended Actions
MCE.

Measured BW Less than Minimum
Indicates that the measured QCI-1 BW is less than

Description/Probable Cause the required minimum (that is, the minimum reserved
for calls is not yet attempted).
Alarm Type ID 656
Severity Major
Category Node
Clearing Automatic
The unit triggers a reboot. This will trigger switching

to the best cell in the scanning list. If the failure
Recommended Actions
persists, the radio channel is bad. Try shifting the unit
(a technician must be involved).
MME Connectivity Lost
Loss of the S1AP SCTP connection to a specific

MME.
Raised when the eNodeB is unable to communicate
with the MME (using the MME IP address).
Alarm Type ID 556
eNodeB,
Relay eNodeB
Severity Major
Category Node
Clearing Automatic

Recommended Actions 1. The IP connectivity to the specified MME.
2. The specified MME is operational.

MME PLMN Overload Service Interruption
The MME is overloaded for a PLMN which has no

other serving MMEs.
Alarm Type ID 613
eNodeB,
Relay eNodeB
Severity Major
Category Node
This alarm clears:

 When Overload_response for the relevant
MME receives the value NONE.
 If all GUMMEIs associated with the relevant
Clearing PLMN are deleted from the
Overload_GUMMEI_list (following S1
OVERLOAD STOP).
 If at least one more serving MME is added for
the relevant PLMN.
Recommended Actions Check the corresponding MME capacity.
MME PLMN Overload Without Service Interruption
The MME is overloaded for a PLMN for which there is

at least another serving MME.
Alarm Type ID 614
eNodeB,
Relay eNodeB
Severity Warning
Category Node
This alarm clears:

 When Overload_response for the relevant
MME receives the value NONE.
 If all GUMMEIs associated with the relevant
Clearing PLMN are deleted from the
Overload_GUMMEI_list (following S1
OVERLOAD STOP).
 If all other MMEs serving the relevant PLMN
are deleted.
Recommended Actions Check the corresponding MME capacity.

Motor Failure
Description/Probable Cause The motor on the base station has failed.
Alarm Type ID 581
iBridge NLOS,
Relay
Severity Major
Category Node
Clearing Automatic
Because this alarm is triggered by a hardware failure,

the initial recommendation is to try rebooting the
software on the unit. If the alarm persists, then the
unit should be replaced as soon as possible.
Note: As long as a link is already established, this
Recommended Actions alarm is not service affecting and will not impact the
link. If the alarm was triggered as a result of a
command from Netspan to move the antenna,
meaning that the link was lost when the alarm was
raised, then the alarm does impact the service and
the unit should be replaced immediately.
Motor Pending Failure
A motor slip detected. Raised due to loss of bearing,

Description/Probable Cause mechanical bearing in radome, or impending failure
of the motor.
Alarm Type ID 593
iBridge 460,
Relay
Severity Warning
Category Node
Clearing Automatic
Recommended Actions If the issue persists, replace the unit.

MSM Failure
Air4G cannot communicate with its internal MSM

component.
Alarm Type ID 503
WiMAX
Note: Applies to Air4G only.
Severity Critical
Category SW
Clearing Automatic
Recommended Actions Reboot the node.
MSM Port Failure
Air4G cannot communicate with a daisy-chained slave

BS.
Alarm Type ID 518
WiMAX
Severity Major
Category SW
Clearing Automatic
Disconnect and reconnect the cable from the failed

Recommended Actions
port.
Neighbour Addition Rejected
A neighbor is manually configured through the NMS

when the cell NRT is full.
Alarm Type ID 604
eNodeB,
Relay eNodeB
Severity Warning
Category Node

Clearing Manually
Recommended Actions Delete a neighbor prior to adding the neighbor again.
NetspanSF Node Config Error
NetspanSF has detected an error when generating a

PnP or node configuration for a specific node.
Alarm Type ID 615
Applicable Technology NetspanSF
Severity Critical
Category NetspanSf
Clearing Automatic
Unable to generate a valid EARFCN within

NetspanSF. This may occur if NetspanSF does not
have geographical data corresponding to the GPS
location of the element, lack of DeNodeB ECGI or an
inability to generate a valid EARFCN within the
Recommended Actions configuration rules.
Address the underlying configuration issue and the
PnP configuration should then be generated by
NetspanSF and the PnP sequence should
automatically proceed.
NetspanSF Server Error
Description/Probable Cause NetspanSF has detected a general error.
Alarm Type ID 616
Applicable Technology NetspanSF
Severity Critical
Category NetspanSf
Clearing Automatic
1. The expected software image naming

convention is not aligned between NetspanSF
Recommended Actions
and Netspan. This needs to be corrected at
either end.

2. Netspan-SF detected no GPS location

information available from node. This may mean
that the non-GPS location information was
sufficient if PnP was successful.
Address the underlying configuration issue and the
PnP configuration should then be generated by
NetspanSF and the PnP sequence should
automatically proceed.
NL Sync Clock Source Error
The eNodeB reports an error during the NL Sync

procedure.
This alarm is triggered by the NL Sync Clock Source
Operation Status Change event.
Alarm Type ID 659
Severity Major
Category Node
Clearing Automatic
Recommended Actions Check the status of the NL Sync clock source.
NL Sync Procedure Error
The eNodeB reports an error regarding the operation

of the NL Sync clock source.
This alarm is triggered by the NL Sync Procedure
Status Change event.
Alarm Type ID 658
Severity Warning
Category Node
Clearing Automatic
Recommended Actions Check the status of the NL Sync clock source.

NLM Frequency Scan Warning
The eNodeB reports that the Network Listening

module is not configured with applicable frequencies
Description/Probable Cause for scanning.
This alarm is triggered by the NLM Frequency Scan
event.
Alarm Type ID 660
Severity Warning
Category Node
Clearing Automatic
Recommended Actions Check the configured NL scan frequencies.
No PTP Master Available
Description/Probable Cause None of the configured 1588 Masters is available.
Alarm Type ID 612
eNodeB,
Relay eNodeB
Severity Major
Category Node
Cleared when at least one configured 1588 Master is

Clearing
made available.
Possible causes are reported along with the alarm.

Check the 1588 Master(s), and the transport network
Recommended Actions
towards the 1588 Master for possible connectivity
issues.
Node 10MHz Clock Failure
The node might cease to transmit when in this state

Description/Probable Cause because it lost the 10 MHz signal from the GPS
timing source.
Alarm Type ID 533
Applicable Technology WiMAX 16d

Severity Critical
Category GPS
Clearing Automatic
Reboot the node. If the issue persists, replace the

Recommended Actions
hardware.
Node Action Error
A problem in performing an action on this node. The

node SNMP agent reported an error when action was
invoked from the EMS.
Typically, this alarm that is caused by a potential
software error is used for identifying issues during the
system verification and validation tests.
Alarm Type ID 109
eNodeB,
iBridge NLOS,
Relay eNodeB,
WiMAX 16e/16d
Severity Minor
Category BS
Clearing Automatic
To rectify the issue, re-provision the specified node.

To re-provision the node, perform the following steps:
1. Go to the Node Management page.
Recommended Actions
Node Call Trace Server Connection Lost
Trace Log Start messages were not acknowledged

for the configured amount of attempts.
Alarm Type ID 602
eNodeB,
Relay eNodeB
Severity Warning

Category Node
Automatic when Trace Log Start is acknowledged

Clearing
(from the eNodeB)
1. Check communications between the CTS, the
eNodeB, and the IP configuration on the
Recommended Actions eNodeB for the CTS.
2. Check that the CTS is running needs to be in
the actions.
Node Clock Source Lost
There is no valid synchronization signal (that is, GPS,

Description/Probable Cause 1PPS, 1588, or Network listening) and the system is
in the Holdover or Out-of-Service state.
Alarm Type ID 605
eNodeB,
Relay eNodeB
Severity Major
Category Node
Automatic when the clock source has been re-

Clearing
acquired and the Lock state has been achieved.
Recommended Actions Check the clock source.
Node Clock Source Unavailable
The eNodeB reports that one of its configured and

Description/Probable Cause supported clock sources is unavailable and reports
the details of that clock source.
Alarm Type ID 661
Severity Major
Category Node
Clearing Automatic
Recommended Actions Check the configured clock source.

Node Config Status Changed
The node reports that its configuration status has

changed.
Alarm Type ID 574
eNodeB,
Relay eNodeB
Severity Major
Category Node
Clearing Automatic
The desired configuration cannot be achieved as the

Recommended Actions Air4G OS software version is out of date. Update it
and retry the configuration.
Node Current Unacceptable
The current on a node has either exceeded or

dropped below an alarm threshold.
Alarm Type ID 221
Applicable Technology Not currently implemented by any node.
Severity Major
Category BS
Clearing Automatic
Recommended Actions Not currently implemented.
Node Disk Full
Node disk usage is high (Over 90% of the disk space

is used).
Alarm Type ID 649
Applicable Technology Any
Severity Critical
Category Node

Clearing Auto
Recommended Actions Troubleshoot the Node Disk Usage.
Node Encryption Licence Invalid
The node reports an Invalid Encryption Licence

certificate.
The system falls back to an unencrypted mode of
operation. The privacy and integrity OTA is affected.
Alarm Type ID 211
eNodeB,
iBridge NLOS,
Relay eNodeB,
WiMAX 16e/16d
Severity Critical
Category
Clearing Automatic
To verify the licence information:

1. Select Configuration Management > Node >
Node. The Node List page appears.
2. Double-click the node whose licence
information you want to view.
3. Select the Status tab.
Recommended Actions
4. Select Licence Status in the Status Type box.
If you have an Invalid Encryption Licence, order a
new, valid certificate, and then upload it using
Netspan.
Note: Do not ignore the expiration warnings. Allow
enough time for ordering and installation.
Node Feature Licence Expired
The Feature Licence certificate applied to the node

is expiring or expired.
Description/Probable Cause The system falls back to a mode of operation that
does not require a licence. The performance might be
affected.
Alarm Type ID 538
iBridge NLOS,
WiMAX 16e/16d

Severity Major
Category
Clearing Automatic

Recommended Actions
If the Feature Licence certificate applied to the node
expired or is expiring, order a new, valid licence
certificate, and then upload it using Netspan.
Note: Do not ignore the expiration warnings. Allow
enough time for ordering and installation.
Node Feature Licence Invalid
The node is set up with an Invalid Feature Licence

certificate. It limits the node capabilities.
Description/Probable Cause The system falls back to a mode of operation that
affected.
Alarm Type ID 532
iBridge NLOS,
WiMAX 16e/16d
Severity Critical
Category
Clearing Automatic

Recommended Actions
If you have an invalid Feature Licence, perform the
following steps:
1. Delete the invalid licence.
2. Order a new, valid licence certificate.
3. Upload it using Netspan.

Node Feature Not Implemented
One or more features requested on this node are not

implemented.
The system falls back to a mode of operation that is
implemented. The performance might be affected.
Alarm Type ID 539
iBridge NLOS,
WiMAX 16e/16d
Severity Major
Category
Clearing Automatic
Change the configuration to match the capability of

Recommended Actions
the node.
Node Feature Not Licensed
The NMS licenses available on this server do not

permit the use of the requested features on any node
because they are not licensed.
The system falls back to a mode of operation that
affected.
Alarm Type ID 540
iBridge NLOS,
WiMAX 16e/16d
Severity Major
Category
Clearing Automatic

Recommended Actions
If the requested features are not licensed, order a
new, valid licence certificate for them, and then
upload it using Netspan.

Node in Holdover
The node reports that there is no valid configured

clock source. The node is in the Holdover state.
Alarm Type ID 571
eNodeB,
Relay eNodeB
Severity Major
Category Node
Clearing Automatic
This alarm appears along with the Node PTP Grand

Master Lost alarm. Perform the recommended
Recommended Actions
actions of the relevant alarm to rectify both the
alarms.
Node in Maintenance Mode
The node is currently in the Maintenance mode. This

might be due to a management action.
Alarm Type ID 502
Severity Indeterminate
Category BS
Clearing Automatic
Recommended Actions Check the configuration of the node.
Node Internal Clock
The node reports an internal synchronisation

problem.
Alarm Type ID 573
eNodeB,
Relay eNodeB
Severity Major

Category Node
Clearing Automatic

Recommended Actions
hardware.
Node Invalid Configuration
The node contains invalid configurations as a result

Description/Probable Cause of the validation check failure during PnP.
Note: Netspan raises this alarm.
Alarm Type ID 174
eNodeB,
iBridge NLOS,
Relay,
Relay eNodeB
Severity Critical
Category
Clearing Automatic
Recommended Actions Go to the Edit page and fix the configuration.
Node Local Access Attempt
The node reports that after the unit is operational, a

local access (for example - LAT, Web GUI) was
attempted (even if successful).
 A successful or failed Web GUI attempt.
 A successful or failed SSH attempt.
 A successful or failed serial attempt.
Alarm Type ID 567
eNodeB,
Relay eNodeB
Severity Major
Category Node

When resolved, this alarm does not clear

automatically. To remove the alarm from the Active
Clearing Alarms list, delete it.
For more information on how to delete an active
alarm, see Deleting an Active Alarm.
Check whether the source IP address used for

accessing the node is a trusted one (0.0.0.0 denotes
the serial-port access).
Recommended Actions
If not, consider disabling the Web GUI and SSH
access to the eNodeBs using Netspan (Security
Profile > Management Security Properties).
Node Loss of Sync
The maximum holdover timer in the node expired.

Description/Probable Cause The node does not have a valid sync source and
remains in the OOS state until a valid clock source is
available.
Alarm Type ID 572
eNodeB,
Relay eNodeB
Severity Critical
Category Node
Clearing Automatic
This alarm appears along with the Node PTP Grand

Master Lost alarm. Perform the recommended
Recommended Actions
actions of the relevant alarm to rectify both the
alarms.
Node Lost Comms
The Netspan server is unable to communicate with

the SNMP agent on the node.
This alarm makes the EMS management impractical
(for example—the configuration is suspended, events
and alarms are not logged, or the statistics is not
logged). However, if configured, the node operates
Description/Probable Cause appropriately.
Loss of communication is typically due to a temporary
network condition (for example—problem with the
network connection, or routing and firewall rules).
Note: The node with this alarm will have Comms
failure in the Connection State column of the Node
List.
Alarm Type ID 100
CTS,
eNodeB,

iBridge LOS,
iBridge NLOS,
Relay,
Relay eNodeB,
WiMAX 16e/16d
Severity Major
Category BS
ITU Event Type Quality of Service Alarm
Clearing Automatic
If the issue persists, perform the following steps:

1. Check the network connections between
Netspan and the node.
Recommended Actions
2. Verify whether the throughput and routing of
packets with the IP ports (satisfies the EMS
design requirements).
Node Out of Service (OOS)
The node is out of service. It might be due to a

management action.
Alarm Type ID 501
iBridge NLOS,
WiMAX 16e/16d
Severity Critical
Category BS
Clearing Automatic
Recommended Actions Check the configuration of the node.
Node Power Unacceptable
The power on a node has either exceeded or

Alarm Type ID 220
Applicable Technology Not currently implemented by any node.
Severity Major
Category BS

Clearing Automatic
Recommended Actions Not currently implemented.
Node Provisioning Error
The node SNMP agent or the Netspan server

reported an error (for example—potential software
error, configuration validity, or inconsistency error) on
the provisioning failure.
There is an issue with configuring the per-Node
configuration on the specified node.
Typically, this alarm is used for identifying issues
during the system verification and validation tests.
Alarm Type ID 102
eNodeB,
iBridge LOS,
iBridge NLOS,
Relay,
Relay eNodeB,
WiMAX 16e/16d
Severity Minor
Category BS
Clearing Automatic

Recommended Actions
Node PTP Degraded Stream
PDV in the 1588 PTP stream is too high. This may

cause synchronization issues.
Alarm Type ID 599
eNodeB,
Relay eNodeB
Severity Warning
Category Node

Cleared when PDV in the 1588 PTP stream is

Clearing
normal.
Check the transport network quality. Confirm proper

Recommended Actions
QoS configuration.
Node PTP Grand Master Lost
The node reports that it lost the PTP clock

synchronization and does not have a valid 1588 clock
Description/Probable Cause source.
The Node PTP Grand Master Status event is raised
with the Grand Master Lost status.
Alarm Type ID 570
eNodeB,
Relay eNodeB
Severity Major
Category Node
Clearing Automatic
Recommended Actions Check the connectivity with the PTP GM.
Node Self Test Failed
Description/Probable Cause This alarm is caused by a hardware problem.
Alarm Type ID 566
eNodeB,
Relay eNodeB
Severity Critical
Category Node
Clearing Automatic

Recommended Actions
hardware.

Node Shutdown
Indicates that the node is shut down and out of

service. The node service is temporarily lost until it
restarts automatically.
 The node is manually reset.
 The node is too hot.
 A software error.
Alarm Type ID 201
eNodeB,
iBridge NLOS,
Relay eNodeB,
WiMAX 16e/16d
Severity Critical
Category BS
Clearing Automatic
For overheating:
1. Check the temperature reports.
Recommended Actions 2. Check the installation for causes of
overheating.
3. If it is a software error, contact Airspan
Customer Service Help Desk.
Node Software Version Status Changed
The node reports that its software version status has

changed.
Alarm Type ID 575
eNodeB
Severity Major
Category Node
Clearing Automatic
The desired configuration cannot be achieved as the

Recommended Actions Air4G OS software version is out of date. Update it
and retry the configuration.

Node Temperature Unacceptable
Indicates that the node hardware is close to

overheating or under heating. The node temperature
fell outside the acceptable value threshold.
The Node Temperature event is raised with at least
one sensor out of range.
Though this behavior does not affect the service, it
must be cleared because this might be a warning
before the power shutdown.
Alarm Type ID 202
eNodeB,
iBridge NLOS,
Relay,
Relay eNodeB
Severity Major
Category BS
Clearing Automatic

Recommended Actions
2. Check the installation for causes of
overheating or under heating.
Node Timing Frame Lock Lost
The node lost the timing lock with the external GPS
or PTP timing source.
Description/Probable Cause Because the transmitter is turned off, the node might
cease transmission when in this state. Consequently,
the service will be temporarily lost.
Alarm Type ID 205
iBridge NLOS,
WiMAX 16e
Severity Critical
Category GPS
Clearing Automatic

Recommended Actions For the GPS:
1. Use Netspan to check the GPS status.

2. Check the GPS antenna connection (for the

For the PTP:
1. Check the communication.
2. Check the operation of the PTP master.
Node Voltage Unacceptable
The node indicates that at least one module has a

voltage exceeding the normal operating parameters.
The DC voltage fell outside the acceptable value
threshold.
Alarm Type ID 212
eNodeB,
Relay eNodeB
Severity Major
Category RF
Clearing Automatic

1. Check the voltage.
Recommended Actions
2. Reboot the node.
3. If the issue persists, replace the hardware.
NTP Failure
The NTP Time of Day synchronisation failed and the

node is unable to establish an accurate time for its
clock.
 The node has no NTP server configured.
Description/Probable Cause  The server is not responding.
Note: This failure does not affect a system with
the GPS. However, a system without the GPS
might fail licence certificate validation.
For more information on the system impact, see
the licence related alarms.
Alarm Type ID 541
iBridge NLOS,
Relay,
Relay eNodeB,
WiMAX 16e
Severity Critical

Category
Clearing Automatic

1. Check the communications to the NTP server.
Recommended Actions 2. Use Netspan test facility to verify the NTP
server operation.
3. Configure the backup NTP servers for
redundancy.
Operator Certificate Expired
The eNodeB was unable to update the X.509

operator certificates from the CMS. The eNodeB is
reverting to factory certificates and will restart the
CMPv2 process.
Alarm Type ID 591
eNodeB,
Relay eNodeB
Severity Critical
Category Node
Once the eNodeB successfully obtains the new X.509

Clearing operator certificates from the CMS, this alarm clears
automatically.

1. Check the SeGW reachability and connectivity
Recommended Actions to the eNodeB.
2. Verify and make sure that the operator
certificate is not in the CRL.
Outdoor Cell is Out of Service
The eNodeB turned off its outdoor cell due to poor

channel quality of the Relay part of Relay eNodeB.
Relay eNodeB reports that its outdoor cell is out of
service.
Alarm Type ID 624
Relay eNodeB
Applicable Technology Note: This alarm type applies to Relay eNodeB using
outdoor cells only.
Severity Minor

Category Node
The channel quality (SINR or spectral efficiency) of

Relay needs to be better than the predefined
Clearing
threshold. To clear this alarm, the user must change
the threshold or the channel quality must turn better.
Check the channel quality (SINR or spectral

Recommended Actions
efficiency) of Relay.
P1 CDCL Selection Failure
iRelay failed to establish connection with the first

(highest priority) cell in the CDCL list.
Note: This alarm is raised only if CDCL lock (Netspan
configurable) is set to True.
Alarm Type ID 620
Severity Major
Category Node
The alarm is cleared when the highest priority DeNB

Clearing
has been selected in the CDCL.
P1 PDCL Selection Failure
iRelay failed to establish connection with the first

(highest priority) cell in the PDCL list.
Note: This alarm is raised only if PDCL lock (Netspan
Alarm Type ID 608
Severity Major
Category Node
The alarm is cleared in the following cases:

 iRelay attaches to the highest priority cell
Clearing
configured in the PDCL.
 PDCL configuration change.


Recommended Actions  Verify RF measurements of cells reported in
the CDCL list.
 Correct the configuration or adjust the
equipment location.
PCI Conflict Not Resolved
Auto PCI did not return reboot indication during

maintenance window. eNB reports of Auto PCI
conflict status not resolved during maintenance
window.
Alarm Type ID 641
Severity Critical
Category Node
Clearing Auto
Recommended Actions Check Auto PCI status.
PCI Update Failure
Description/Probable Cause Raised when an ‘on the fly’ PCI change failed.
Alarm Type ID 671
Severity Critical
Category Node
Clearing Automatic
Recommended Actions Reboot the eNodeB.

PDCL Selection Failure
iRelay could not connect to any of the cells

configured in the PDCL.
Note: This alarm is raised only if PDCL lock (Netspan
Alarm Type ID 611
Severity Major
Category Node
The alarm is cleared in the following cases:

 iRelay attaches to a donor cell configured in the
Clearing
PDCL.
 PDCL configuration change.

Recommended Actions  Verify RF measurements of cells reported in
the CDCL.
 Correct the configuration or adjust the
equipment location.
PLL Lock Lost
Indicates that the SDR PLL lost lock to the SDR

VCXO.
It indicates a failure in one of the SDR components
(VCXO).
Alarm Type ID 218
iBridge NLOS,
WiMAX 16e
Severity Critical
Category BS
Clearing Automatic
If the alarm is triggered repeatedly, replace the

Recommended Actions
hardware.

PnP Configuration Mismatch
Netspan received the PnP Identification event from

the node, but PnP is not enabled in Netspan.
Alarm Type ID 569
eNodeB,
Relay eNodeB
Severity Major
Category Node
Clearing Automatic
Check the configuration of PnP in Netspan and on

the node.
Recommended Actions If you want PnP, enable PnP in Netspan; otherwise,
disable PnP in the node through its Web GUI and
configure it statically.
PnP Location Changed
The node reports a change in the PnP location.

Description/Probable Cause A PnP-enabled node changed its location beyond the
configured location radius since its last restart. The
node restart process is halted.
Alarm Type ID 568
eNodeB,
Relay eNodeB
Severity Critical
Category Node
Clearing Automatic
If this is not an expected location change, the node

might be stolen. Netspan is preventing this node from
going active.
Recommended Actions If this is a planned location change, return this node
in Netspan into the PnP database with the updated
coordinates and restart the node to initiate a full PnP
flow.

Port Disable Prevention
The Port Disable command is blocked because this

port is considered as a management port.
Alarm Type ID 594
eNodeB,
Relay eNodeB
Severity Warning
Category Node
Clearing Manual
Recommended Actions Not applicable
PTP Clock Sync
The PTP clock synchronisation with the PTP master

is lost.
If the system is configured for the PTP
synchronisation and the system clock is not
synchronised to the PTP, the RF subsystem disables
the transmitter to prevent interference with other
nodes.
 The result of the PTP clock synchronisation
fault.
 Loss of communication with the IEEE1588 PTP
master.
 The PTP protocol failure.
Alarm Type ID 551
iBridge NLOS,
WiMAX 16e
Severity Critical
Category BS
Clearing Automatic

1. Check the communications to the PTP master.
Recommended Actions
2. Verify the PTP master operation with another
test slave (client).

PTP Hardware Fault
The PTP hardware configuration does not support the

PTP Slave operation.
Description/Probable Cause synchronisation and the system clock is not
synchronised to the PTP, the RF subsystem disables
nodes.
Alarm Type ID 550
iBridge NLOS,
WiMAX 16e
Severity Critical
Category BS
Clearing Automatic

1. Check the hardware inventory log.
Recommended Actions
2. Confirm whether it is a hardware failure.
3. If confirmed, replace the hardware.
QoS Handover Neighbour Does Not Exist
No neighbors with a configured QoS-based Mobility

Description/Probable Cause EARFCN exist at this time. QoS-based handovers will
fail.
Alarm Type ID 592
eNodeB,
Relay eNodeB
Severity Warning
Category Node
Clearing Automatic
Check configured EARFCNs under Netspan Mobility

Profile (that is, in the QoS-Based Measurement
Recommended Actions
Configuration panel) against the actual available
neighbors.

QoS Server Connection Failure
Description/Probable Cause Connection to the TWAMP Server is lost.
Alarm Type ID 644
Applicable Technology eNB
Severity Major
Category Node
Clearing Auto
Troubleshoot the TWAMP Server and verify that the

Recommended Actions
TWAMP server sessions are established.
Remote Connection Lost
The node lost its connection with the node on the

other end of the link.
Alarm Type ID 116
Applicable Technology iBridge LOS
Severity Major
Category BS
Clearing Automatic
You might have to schedule a site visit. For more

Recommended Actions
information, see the iB440 Troubleshooting Guide.
RF FEM Fault
The FEM cannot be configured or is not operational.

Description/Probable Cause The management connectivity with the FEM module
is lost or the FEM status indicates a hardware fault.
Alarm Type ID 543
iBridge NLOS,
Relay,
Relay eNodeB,
WiMAX 16e/16d
Severity Major

Category BS
Clearing Automatic

To re-provision the specified node, perform the
following steps:
Recommended Actions
2. Select the State and Control tab.
4. If the problem persists, replace the unit.
RF FEM Not Present
Description/Probable Cause RF FEM is not detected.
Alarm Type ID 544
iBridge NLOS,
WiMAX 16e/16d
Severity Warning
Category BS
Clearing Automatic

Recommended Actions
hardware.
RF Hardware Fault
Description/Probable Cause The RF status is showing a hardware error.
Alarm Type ID 507
eNodeB,
iBridge NLOS,
Relay eNodeB,
WiMAX 16e/16d
Severity Major
Category RF

Clearing Automatic

1. Check the RF status report.
Recommended Actions
RF Out of Service (OOS)
The RF is currently out of service. It might be due to a

Description/Probable Cause management action.
Note: This alarm is not applicable to AirDensity..
Alarm Type ID 504
iBridge NLOS,
WiMAX 16e/16d
Note: WiMAX (16e) is not recommended for use with
12.x Netspan releases.
Severity Major
Category RF
Clearing Automatic
Recommended Actions Check the configuration of the RF.
RF1 Carrier Sense Frequent Interference
The node detected a high level of interference on

RF1. The interference is persistent and is frequently
detected.
When the interference is detected, it might prevent
Description/Probable Cause the reliable operation of the node. On each
occurrence of the interference, the interference
detection system turns the transmitter off for a
duration of two frames. This might cause the terminal
to lose the link.
Alarm Type ID 536
iBridge NLOS,
WiMAX 16e/16d
Severity Major
Category RF1
Clearing Automatic


Recommended Actions 1. Locate the source of the interference.
2. Change the RF channel.
RF1 Carrier Sense Interference
The carrier sense on RF1 detected at least one

interference event.
to lose the link.
Alarm Type ID 534
iBridge NLOS,
WiMAX 16e/16d
Severity Minor
Category RF1
Clearing Automatic

Recommended Actions 1. Locate the source of interference.
RF1 Configuration Fault
The RF1 status is showing a configuration error.

Description/Probable Cause The RF subsystem is not configured properly. The RF
configuration parameter is invalid or inconsistent with
the hardware capabilities.
Alarm Type ID 510
eNodeB,
iBridge NLOS,
Relay eNodeB,
WiMAX 16e/16d
Severity Major
Category RF1
Clearing Automatic


Recommended Actions 2. Identify the parameter with the invalid or
inconsistent value.
3. Correct the parameter value.
RF1 Hardware Fault
The RF1 status is showing a hardware error. This

error might affect the radio performance, disable the
transmitter, or result in a poor performance.
The following can cause an RF1 hardware fault:
 A frequency or timing synchronisation failure.
 A management action to disable the
transmitter.
Netspan reports the detailed cause.
Alarm Type ID 508
eNodeB,
iBridge NLOS,
Relay eNodeB,
WiMAX 16e/16d
Severity Major
Category RF1
Clearing Automatic

Recommended Actions
RF1 Hardware Fault (Warning)
The RF1 status is showing a hardware warning. It

Description/Probable Cause might affect the radio performance, but the
transmitter remains ON.
Alarm Type ID 546
eNodeB,
iBridge NLOS,
Relay eNodeB,
WiMAX 16e/16d
Severity Warning
Category RF1

Clearing Automatic

1. Check the RF status reports to identify the root
cause.
Recommended Actions
2. Resolve the root cause.
3. If the issue is due to a hardware failure, replace
the unit.
RF1 Temperature Fault
The RF1 status is showing a temperature fault. The

temperature is outside the recommended limits. The
radio performance might be affected, but the unit
remains operational.
Alarm Type ID 514
eNodeB,
iBridge NLOS,
Relay eNodeB,
WiMAX 16e/16d
Severity Major
Category RF1
Clearing Automatic

Recommended Actions 2. Identify source of overheating or under heating.
3. If no external cause is identified, replace the
hardware.
RF1 Transmitter Off
The node reports that the RF1 transmitter is disabled.

The RF1 transmitter is disabled due to a
management request, configuration problem,
Description/Probable Cause licensing issue, or hardware problem.
The fault codes describe the possible reasons (carrier
interference, hardware fault, holdover expired, LFP,
and so on).
Alarm Type ID 516
eNodeB,
Applicable Technology iBridge NLOS,
Relay eNodeB,

WiMAX 16e/16d
Severity Major
Category RF1
Clearing Automatic

Recommended Actions
RF1 VSWR Fault
The RF1 status is showing a hardware error.

Description/Probable Cause The RF1 VSWR is exceeding its configured VSWR
threshold and the RF1 Status event is raised
indicating a VSWR problem.
Alarm Type ID 512
eNodeB,
iBridge NLOS,
Relay eNodeB,
WiMAX 16e/16d
Severity Minor
Category RF1
Automatic only after the manual operation of setting

Clearing
the cell to In Service.
Check the physical connectivity to the antenna. Once

Recommended Actions the issue is identified and fixed, set the cell to
In Service manually from the NMS.
RF2 Carrier Sense Frequent Interference
The node detected a high level of interference on

RF2. The interference is persistent and is frequently
detected.
to lose the link.
Alarm Type ID 537

iBridge NLOS,
WiMAX 16e/16d
Severity Major
Category RF2
Clearing Automatic

Recommended Actions 1. Locate the source of the interference.
RF2 Carrier Sense Interference
The carrier sense on RF2 detected at least one

interference event.
to lose the link.
Alarm Type ID 535
iBridge NLOS,
WiMAX 16e/16d
Severity Minor
Category RF2
Clearing Automatic

Recommended Actions 1. Locate the source of interference.
The RF2 status is showing a configuration error.

This error indicates that the RF subsystem is not
Description/Probable Cause configured properly. The RF configuration parameter
is invalid or inconsistent with the hardware
capabilities.
Alarm Type ID 511
eNodeB,
iBridge NLOS,

Relay eNodeB,
WiMAX 16e/16d
Severity Major
Category RF2
Clearing Automatic

inconsistent value.
RF2 Hardware Fault
The RF2 status is showing a hardware error. This

error might affect the radio performance, disable the
transmitter, or result in a poor performance.
The following can cause an RF1 hardware fault:
 A frequency or timing synchronisation failure.
 A management action to disable the
transmitter.
Netspan reports the detailed cause.
Alarm Type ID 509
eNodeB,
iBridge NLOS,
Relay eNodeB,
WiMAX 16e/16d
Severity Major
Category RF2
Clearing Automatic

Recommended Actions

The RF2 status is showing a hardware warning. It

Description/Probable Cause might affect the radio performance, but the
transmitter remains ON.
Alarm Type ID 547
eNodeB,
iBridge NLOS,
Relay eNodeB,
WiMAX 16e/16d
Severity Warning
Category RF2
Clearing Automatic

cause.
Recommended Actions
the unit.

temperature is outside the recommended limits. This
fault might affect the radio performance, but the unit
remains operational.
Alarm Type ID 515
eNodeB,
iBridge NLOS,
Relay eNodeB,
WiMAX 16e/16d
Severity Major
Category RF2
Clearing Automatic

Recommended Actions 2. Identify the source of overheating or under
heating.
hardware.

RF2 Transmitter Off

The RF2 transmission is turned off due to a
Description/Probable Cause licensing issue, or hardware problem.
The fault codes describe the possible reasons (for
example—carrier interference, hardware fault,
holdover expired, LFP, and so on).
Alarm Type ID 517
eNodeB,
iBridge NLOS,
Relay eNodeB,
WiMAX 16e/16d
Severity Major
Category RF2
Clearing Automatic

Recommended Actions
RF2 VSWR Fault
The RF2 status is showing a hardware error.

Description/Probable Cause The RF2 VSWR is exceeding its configured VSWR
threshold and the RF2 Status event is raised
indicating a VSWR problem.
Alarm Type ID 513
eNodeB,
iBridge NLOS,
Relay eNodeB,
WiMAX 16e/16d
Severity Minor
Category RF2

Clearing


RF3 is experiencing a configuration problem, and the

RF3 status is showing a configuration error.
Alarm Type ID 524
eNodeB,
iBridge NLOS,
Relay eNodeB,
WiMAX 16e/16d
Severity Major
Category RF3
Clearing Automatic

inconsistent value.
RF3 Hardware Fault
RF3 is experiencing a hardware problem, and the

RF3 status is showing a hardware error.
Alarm Type ID 522
eNodeB,
iBridge NLOS,
Relay eNodeB,
WiMAX 16e/16d
Severity Major
Category RF3
Clearing Automatic

Recommended Actions


RF3 status is showing a hardware warning.
Alarm Type ID 548
eNodeB,
iBridge NLOS,
Relay eNodeB,
WiMAX 16e/16d
Severity Warning
Category RF3
Clearing Automatic

cause.
Recommended Actions
the unit.

temperature is outside the recommended limits.
Alarm Type ID 528
eNodeB,
iBridge NLOS,
Relay eNodeB,
WiMAX 16e/16d
Severity Major
Category RF3
Clearing Automatic

heating.
hardware.

RF3 Transmitter Off
The RF3 transmitter is disabled. It might be due to a

Description/Probable Cause management request, configuration problem,
licensing issue, or hardware problem.
Alarm Type ID 530
eNodeB,
iBridge NLOS,
Relay eNodeB,
WiMAX 16e/16d
Severity Major
Category RF3
Clearing Automatic

Recommended Actions
RF3 VSWR Fault
RF3 is experiencing a hardware problem. The RF3

status is showing a hardware error.
Alarm Type ID 526
eNodeB,
iBridge NLOS,
Relay eNodeB,
WiMAX 16e/16d
Severity Minor
Category RF3

Clearing


RF4 is experiencing a configuration problem, and the

RF4 status is showing a configuration error.
Alarm Type ID 525
eNodeB,
iBridge NLOS,
Relay eNodeB,
WiMAX 16e/16d
Severity Major
Category RF4
Clearing Automatic

inconsistent value.
RF4 Hardware Fault

Alarm Type ID 523
eNodeB,
iBridge NLOS,
Relay eNodeB,
WiMAX 16e/16d
Severity Major
Category RF4
Clearing Automatic

Recommended Actions


RF4 status is showing a hardware warning.
Alarm Type ID 549
eNodeB,
iBridge NLOS,
Relay eNodeB,
WiMAX 16e/16d
Severity Warning
Category RF4
Clearing Automatic

cause.
Recommended Actions
the unit.
The RF4 status is showing a temperature fault, and

the temperature is outside the recommended limits.
Alarm Type ID 529
eNodeB,
iBridge NLOS,
Relay eNodeB,
WiMAX 16e/16d
Severity Major
Category RF4
Clearing Automatic

heating.
hardware.

RF4 Transmitter Off

The RF4 transmitter is disabled due to a
licensing issue or hardware problem.
Alarm Type ID 531
eNodeB,
iBridge NLOS,
Relay eNodeB,
WiMAX 16e/16d
Severity Major
Category RF4
Clearing Automatic

Recommended Actions
RF4 VSWR Fault

Alarm Type ID 527
eNodeB,
iBridge NLOS,
Relay eNodeB,
WiMAX 16e/16d
Severity Minor
Category RF4

Clearing


SAS Grant Failure
The eNodeB reports that the Grant procedure has

failed with specific causes:
 Grant Denied, Suggested Parameters.
 Grant Denied.
Description/Probable Cause  Grant Renewal Denied.
 Grant Renewal Failed.
 Grant Terminated, Frequency Reallocation.
 Grant Terminated.
 Grant Expired.
Alarm Type ID 628
Severity Critical
Category Node
Clearing Automatic
Recommended Actions Check the CBRS configuration.
SAS Grant Suspended
The eNodeB reports that the Grant procedure has

been suspended.
Alarm Type ID 630
Severity Critical
Category Node
Clearing Automatic

SAS Heartbeat Failure
The eNodeB reports that the Heartbeat procedure

has failed.
Alarm Type ID 629
Severity Critical
Category Node
Clearing Automatic
SAS Registration Failure
The eNodeB reports that the registration to the SAS

server has failed.
Alarm Type ID 626
Severity Critical
Category Node
Clearing Automatic
SAS Registration Suspended
The eNodeB reports that the registration to the SAS

server was not initiated due to the following reasons:
 Non-CBRS configured frequency.
 SI procedure disabled.
Alarm Type ID 631
Severity Critical
Category Node

Clearing Automatic
Recommended Actions Check the frequency configuration.
SAS Server Disconnected
The causes include:

 Loss of physical communication (that is,
IP not reachable) between Netspan as
CBRS Domain Proxy and the SAS
Description/Probable Cause server
 Issue in the X.509 certificate exchange
for the TLS connection between Netspan
as CBRS Domain Proxy and the SAS
server
Alarm Type ID 186
Severity Major
Category Netspan
Clearing Clears automatically after fixing the underlying issue.
Do the following:
 Verify the IP connectivity between
Netspan as CBRS Domain Proxy to the
SAS server.
 For the X.509 certificate issue:
Recommended Actions
o See the Netspan error event logger.
Or
o Verify the connection using the SAS Test
Connection button (Configuration
Management > SAS Server).
SAS Spectrum Inquiry Failure
The eNodeB reports that the Spectrum Inquiry

procedure failed with specific causes:
 Unsupported parameters (eNodeB).
 Unsupported parameters (SAS).
Alarm Type ID 627
Severity Critical

Category Node
Clearing Automatic
SBA Misconfiguration
The requested SBA configuration was not set

properly, due to the following possible reasons
(described in the alarm status info):
 No response from the SBA.
 The SBA reported configuration is different
from the requested configuration.
Alarm Type ID 600
eNodeB
Applicable Technology Note: Applies to AirHarmony 1100 and AirHarmony
4000 only.
Severity Critical
Category Node
Clearing Automatic

1. Try re-provisioning the SBA configuration.
Recommended Actions 2. Reset the eNodeB.
3. Check the SBA connectivity.
4. Replace the SBA.
Scan In Progress
A trap to indicate that the autonomous scan has

started.
Alarm Type ID 619
Severity Major
Category Node

Clearing The alarm is cleared once the scan has completed.
Server CPU Usage High
The average CPU usage over the sampling period is

high.
Alarm Type ID 171
Applicable Technology Netspan EMS
Severity Warning
Category
Clearing Automatic

1. Monitor and check if the CPU usage is
Recommended Actions persistent.
2. Check if there is any unusual activity on the
server.
Server Disk Usage High
The average disk usage over the sampling period is

high.
Alarm Type ID 173
Severity Warning
Category
Clearing Automatic
Recommended Actions Try to free up some space on the server.

Server Event Queue Size High
Indicates that the server event queue count is higher

than the threshold limit. The system impact for this
Description/Probable Cause alarm is server slowdown.
Note: The current threshold is 12000.
Alarm Type ID 183
Applicable Technology EMS
Severity Critical
Category Netspan
Clearing Automatic
Analyze the events and address the underlying

Recommended Actions
cause.
Server Memory Usage High
The average memory usage over the sampling period

is high.
Alarm Type ID 172
Severity Warning
Category
Clearing Automatic
Check whether there is sufficient physical memory on

Recommended Actions
the server.
Serving Netspan Address Mismatch
The serving IP address for Netspan is IPv6 and the

eNodeB PDN type is IPv4.
Alarm Type ID 676
Severity Major
Category Node

Clears when the Netspan IP address and the eNodeB

Clearing
IP address are of the same PDN type.
Reconfigure either Netspan IP address (in dns-sd or

DHCP option 43) to FQDN (which is generic for
Recommended Actions
IPv4/v6), or eNodeB IP address to match Netspan’s
IP address .
Serving Security Gateway Mismatch
The Serving Security gateway IP address PDN type

is different from the eNodeB PDN type.
Alarm Type ID 673
Severity Major
Category Node
Clearing Automatic
Reconfigure the SeGW IP address and IP address

Recommended Actions
type from Netspan.
S-GW Connectivity Lost
There has been a loss of the S1 connection with the

SGW.
Alarm Type ID 580
eNodeB,
Relay eNodeB
Severity Major
Category Node
Clearing Automatic

Recommended Actions 1. The IP connectivity to the specified SGW.
2. That the specified SGW is operational.

SNMP Authentication Failure
The management of the node is not possible. If the

node is configured, it continues operating as normal.
However, the fault and performance management is
Description/Probable Cause affected.
An SNMP manager is attempting to access the
equipment with invalid credentials.
Alarm Type ID 12
Applicable Technology WiMAX 16e/16d
Severity Minor
Category
Clearing Automatic
Correct the SNMP Read and Write communities

Recommended Actions
(SNMPv2c) or passwords (SNMPv3) in the EMS.
SNMPv3 Fallback
The system determines that it should operate in

Description/Probable Cause SNMPv3 authentication-only mode, but you have set
snmpVerConf to SNMPv3 encrypted.
Alarm Type ID 603
eNodeB,
Relay eNodeB
Severity Warning
Category Node
Clearing Automatic
Load a license or configure snmpVerConf to a

Recommended Actions
different value other than SNMPv3 encrypted.
Software Activate Failure
This alarm indicates that an attempt to activate the

secondary software on the node has failed.
Alarm Type ID 177
Applicable Technology All node types

Severity Warning
Category BS
Clearing Automatic when software activation is successful.
1. Check the management connectivity to the

node
Recommended Actions
2. Check the software was previously successfully
downloaded on the node
Software Download Failure
This alarm indicates that an attempt to download

Description/Probable Cause software from the software server to the node has
failed.
Alarm Type ID 176
Applicable Technology All node types
Severity Warning
Category BS
ITU Event Type Processing Error
Clearing Automatic when software download is successful.
1. Check the management connectivity to the

node
Recommended Actions
2. Check the software image exists on the
software server
Software Upgrade Fault
Indicates that the software upgrade process cannot

Description/Probable Cause proceed with the software image you are trying to
upgrade.
Alarm Type ID 175
eNodeB,
Relay eNodeB
Severity Critical
Category BS
Clearing Automatic

Do one of the following:

1. Download the specified software to upload
Recommended Actions
bootloader.
2. Avoid special bootloader software.
SS Action Error
A problem in performing an action on the specified

Description/Probable Cause SS (on one of the channels that experienced this
issue recently).
Alarm Type ID 111
Severity Minor
Category
Clearing Automatic
To rectify the issue, re-provision the specified SS.

1. Go to the SS Management page.
Recommended Actions
2. Click the State tab.
3. Under Provisioning, click the Re-provision
button.
SS Provisioning Error
A problem in configuring service on the specified SS

Description/Probable Cause (on one of the channels that experienced this issue
recently).
Alarm Type ID 104
Severity Minor
Category
Clearing Automatic
To rectify the issue, re-provision the specified SS.

Recommended Actions
1. Go to the SS Management page.
2. Click the State tab.

3. Under Provisioning, click the Re-provision

button.
SS RSSI
Description/Probable Cause The SS RSSI is below the permitted threshold value.
Alarm Type ID 61
Severity Minor
Category
Clearing Automatic

1. Check the SS antenna.
Recommended Actions 2. Verify the location.
3. Reboot the SS.
4. If the issue persists, replace SS.
Sync Switch Exceeded
If your attempts to switch the synchronization source

Description/Probable Cause (1PPS) between the DeNB and the GPS exceeds the
configured threshold, this alarm is triggered.
Alarm Type ID 638
Severity Minor
Category Node
Clearing Automatic
Move the unit near the window where the GPS is

Recommended Actions
available.

System Information Truncation
System information blocks payload is truncated by

eNodeB due to exceeding maximum SI size (277B).
Alarm Type ID 607
eNodeB,
Relay eNodeB
Severity Major
Category Node
Upon proper broadcast of a SIB which was reported

Clearing
as truncated.
Change SI scheduling to spread across SIB 5, 6, and

Recommended Actions
7, which are the largest SIBs.
Tamper Detect
Description/Probable Cause Device tampering detected.
Alarm Type ID 652
Applicable Technology AU
Severity Minor
Category Node
ITU Event Type Physical Violation
Clearing Manual

Tamper detect need to be reset from Netspan.
Recommended Actions
1. Go to State And Control > Tamper Detection
2. Clear detection flags values
Tamper Detect and Disabled
Device tampering detected and device disabled. The

tampering alarm won’t be cancelled automatically, the
Unit has to be replaced and the alarm deleted
manually.
Alarm Type ID 653
Applicable Technology AU

Severity Critical
Category Node
Clearing Manual

Tamper detect need to be reset from Netspan.
Recommended Actions
1. Go to State And Control > Tamper Detection
2. Clear detection flags values
Tilt Threshold Exceeded
The service might be lost due to a radio link drop. If

the protection is enabled, the transmitter is
automatically disabled and the service will be lost.
This alarm is caused by the exceeded tilt threshold.
The node hardware is tilted due to a hardware failure
or an accident (for example - the lamp post bent).
Alarm Type ID 563
All hardware with the tilt sensor (for example,

AirSynergy3).
To determine if the equipment has inbuilt tilt sensor,
see the relevant product specification.
Severity Warning
Category Node
Clearing Automatic
Check the tilt report status and the hardware

Recommended Actions
installation.
TWAMP Overloaded
Description/Probable Cause TWAMP responders are overloaded.
Alarm Type ID 640
Severity Warning
Category Node

Clearing Auto
Check the TWAMP Sender for any misconfiguration

Recommended Actions in your network. Once the configuration is resolved,
the TWAMP service shall commence automatically.
Unsupported Clock Source
The eNodeB reports that a configured clock source is

unsupported.
Alarm Type ID 663
Severity Major
Category Node
Clearing Automatic
Recommended Actions Disable the unsupported clock source.
VoiceMAX Lost Comms
Description/Probable Cause The node lost its communication with VoiceMAX.
Alarm Type ID 215
Applicable Technology WiMAX 16d/16e
Severity Major
Category CONT
Clearing Automatic
Check the configuration and status of the VoiceMAX

Recommended Actions
server.
WiFi Board Connectivity
The unit is not able to communicate with the Wi-Fi

board.
Alarm Type ID 587
eNodeB
Note: Applies to AirVelocity with Wi-Fi only.

Severity Critical
Category Node
Clearing Automatic
Perform the following steps (in the given order) until

the connectivity is restored:
1. Check the Wi-Fi status from the Wi-Fi NMS and
make sure it is active and has a correct
Recommended Actions software version.
2. Manually reset the Wi-Fi board.
3. Reset the eNodeB.
4. If required, replace the hardware.
WiFi Board Initialization
The unit is not able to initialize communications with

the WiFi board.
Alarm Type ID 586
eNodeB
Note: Applies to AirVelocity with Wi-Fi only.
Severity Critical
Category Node
Clearing Automatic
Perform the following steps (in the given order) until

the connectivity is restored:
1. Check the Wi-Fi status from the Wi-Fi NMS and
make sure it is active and has a correct
Recommended Actions software version.
2. Manually reset the Wi-Fi board.
3. Reset the eNodeB.
4. If required, replace the hardware.
X2 Neighbour Comms Loss
Description/Probable Cause The node lost its X2 connection to the neighbour.
Alarm Type ID 558
eNodeB,
Relay eNodeB
Severity Warning

Category Node
Clearing Automatic

Recommended Actions 1. The IP connectivity to the specified neighbour.
2. The specified neighbour is operating normally.

3 Netspan Events
An event indicates the occurrence of a typical condition (a fault or change in a state) in the network. An
event indicating a fault triggers an alarm.
This chapter discusses the following topics:

 Viewing Events
 Refining Event Search
 Editing Event Details
 Exporting Events View into an Excel File
 Refreshing an Events Page
 Event Types
3.1 Viewing Events

To view the list of the existing events, on the main menu, select Fault Management > Events. The
default layout settings sorts events by date. Therefore, the latest events are displayed first.
Netspan stores events in its database. The Netspan events buffer can store up to a maximum of 1
million events. An event remains until it is expired from the Netspan event buffer.
3.2 Refining Event Search

You can apply filters on your Events page to display a subset of events. To refine your search, go to
the Events page, and then do one of the following:
 Using Filter – Click on the Filter checkbox and select the preferred search criterion listed in
the Filter drop-down box. For more information on the available search criteria, see Table 8.
Table 8. Event Search Criteria
Displays the events that match the Search

Event Type
Terms with a specified Event Type.

Source Type
Terms with a specified Source Type.

Source
Terms with a specified Source.

MAC Address
Terms with a specified MAC Address.

Unique ID Name
Terms with a specified Unique ID Name.

Unique ID
Terms with a specified Unique ID.

Event Info
Terms with a specified Event Info.

Event Status
Terms with a specified Event Status.


Received Time
Terms based on a Date.
 Using Search - Select the preferred search criterion list from the Filter drop-down box and
then click on Search to get the results.
3.3 Editing Event Details

To edit the details of an event:
1. On the main menu, select Fault Management > Event Types. The Event Types page
appears.
2. Select the event, whose details you want to view.
3. Click the Edit button or double-click the selected event.
4. After editing the properties, click OK.
Table 9 lists the details of all the fields that you can find on the Edit Event Type page.
Table 9. Event Properties
Provides the name of the event.

Name
Note: This field is read only.
Specifies the ITU event type of the event, which can

be one of the following:
 Other
 Communications Alarm
 Quality of Service Alarm
 Processing Error Alarm
 Equipment Alarm
ITU Event Type
 Environmental Alarm
 Integrity Violation
 Operational Violation
 Physical Violation
 Security Service or Mechanism Violation
 Time Domain Violation
Note: This field is read only.
Properties
Specifies whether event logging is enabled or

disabled.
Log
Note: For an event type, if you disable event logging,
that event will not appear on the Events page.
Specifies whether event forwarding is enabled or

disabled.
Forward Note: For an event type, if you enable event
forwarding, Netspan forwards that event as an SNMP
trap over the NBIF.

3.4 Exporting Events View into an Excel File

To export the events view into an Excel file containing the loaded items that are displayed on the view,
click Export (at the bottom of the page).
3.5 Refreshing an Events Page

To refresh a page, click the Reload or Reload Page button.
Tip: To enable automatic reload, select Auto On (if available on the selected page).
3.6 Event Types

To view the list of the Netspan event types, on the main menu, select Fault Management > Event
Types.
Table 10 shows how the information on each event is structured in this section.
Table 10. Event Definition Structure
Description Provides a brief description of the event.
Event Type ID Gives the ID of the event type.
Provides information on the applicable hardware type

for the event.
Applicable Hardware Type
Note: This field is the equivalent of Raised By on
Netspan GUI (Fault Management > Event Types).
ITU Event Type Specifies the ITU event type of the event.
Event Trigger Provides information on the possible event triggers.
Event Information Provides information on the event such as status.

Table 11 provides an alphabetical list of the Netspan events.

Table 11. Events
 Action Error  Node Config Status Change
 Active Clock Source Change  Node Connection State Change
 A-GPS File Status Change  Node Current Change
 All MME S1-C Comms Status Change  Node Deleted

(per PLMN)
 Node Disk Usage Change
 Authorization Failure
 Node Encryption Licence Invalid
 Authorization Success
 Node Feature Licence Expiring
 Auto-PCI Range Changed
 Auto RSI Change
 Node Feature Not Implemented
 Auto RSI Selected Value
 Auto-Align Request Detected
 Node GPS Receiver Status Change
 Auto-Align Status Changed
 Node Internal Clock Status Change
 Auto-PCI Allocation
 Node Invalid Configuration Change
Status Change  Node LED Status Change
 Backhaul Qos Capacity Limiting Status  Node Local Access Attempt
 Backhaul Qos Service Affecting Status  Node Maintenance Transition
 Basic Caps Exchange Failure  Node Management Change
 Basic Cap Exchange Success  Node Message Change Failed
 Battery Overtemperature (eNodeB)  Node Message Change Success
 Battery Overtemperature (WiFi)  Node NTP Status Change
 BS Active ASN Gateway  Node Operational Status Change
 BS ASN R6 Comms Status Change  Node Operational Status Change

(Server Detected)
 BS ASN-GW Mode Change
 Node Power Change
 BS Failed Actions Cleared
 Node Provisioning Error
 BS FEM Status Change
 Node PTP Grand Master Status
 BS Inventory Added Change
 BS MSM Port Status Change  Node PTP Quality Status Change

 BS MSM Status Change  Node Redirection Failure
 BS Running Status Change  Node Redirection Request
 Calculate Sector Harmonic Mean  Node Redirection Success

Request Detected
 Node Reprovision
 Node Resource Status Change
 Cell 1 Status Change
 Node Restarted (Server Detected)
 Cell 2 Status Change
 Node Self Test
 Cell Active Status Change
 Node Shutdown
 Cell Enabled State Change
 Node Software Version Status Change
 Cell Outage Detected
 Node SS BPKM Fail
 Channel Action Error
 Node SS Dynamic Service Fail
 Channel Failed Actions Cleared
 Node SS RSSI Status Change
 Channel Provisioning Error
 Node Sync Lock Status Change
 Channel Reprovision
 Node Synchronization Lock Status
 Channel Status Change Change
 Clock Source Availability Change  Node Temperature Change
 Clock Source Change  Node Tilt Changed
 Clock Source Configuration  Node Timing Frame Lock
 CMS Status Change  Node Voltage Status Change
 Cold Start  Node X2 Neighbour Status Change
 Command Failed  Operator Certificate Expiry
 CTS eNB Capacity Status Change  Outdoor Cell Status Changed
 CTS Log Overwrite Status Change  P1 CDCL Status Changed
 CTS Logging Status Change  Password Change
 CTS PTE Status Change  Password Reset
 CTS Server Status Change  PCI Conflict Status Changed
 CTS Time Sync Status Change  PCI Range Configuration
 CTS Trace Analysis Status Change  PCI Update Status Change
 Deregistration  PHY Reset

 DFS Disruption Detected  PLL Status Change
 DFS Mode Change  PnP Complete
 DFS Status Change  PnP Config Added
 DHCP T2 Timer Status Change  PnP Config Deleted
 Donor Cell Backhaul Quality Changed  PnP Configuration Mismatch
 Duplicate EMS  PnP Identification
 EGP Neighbor Loss  PnP Location Changed
 Emergency Call Reset Delay  PnP Node Discovery Failed
 Enabled Port Down  PnP Node Matched Multiple Config
 eNodeB PDN Status Change  PnP Node Not Configured
 eSON Server Connection Change  PnP Node Not Found
 ETWS File Upload  PnP Node Not Managed
 ETWS SFTP Session  PnP State Change
 Ext PPS Stream Status Changed  PnP Trigger
 Failed Actions Cleared  Port Disable Prevention
 File Upload Change  Port Status Changed
 Fine-Scan Request Detected  Provisioning Error
 Force Scan Request Detected  PTP Hardware
 Forced Management Status Changed  PTP Master Availability Changed
 Forced Reset  PTP Timing Sync
 GPS Alarms Status Change  QoS Handover Neighbour Change
 GPS Comms Change  Registration Failure
 GPS File Status Change  Registration SubOptimal
 GPS Lock Change  Registration Success
 GPS Persistency Status Changed  Remote Connection Change
 GPS Reduced Holdover  Reprovision
 GPS SNR Change  Reset
 Hardware Replaced  RF Path Imbalance Detected

 Hardware Swap  RF Status Change
 ICIC Misconfiguration  RF Status Change (Server Detected)
 Ignore  RF1 Status Change
 IKEv2 SA Expiry  RF1 Status Change (Server Detected)
 Initial Ranging Failure  RF2 Status Change
 Initial Ranging Success  RF2 Status Change (Server Detected)
 Inventory Status Change  RF3 Status Change
 IPsec SA Expiry  RF3 Status Change (Server Detected)
 iRelay Donor Cell Connectivity Status  RF4 Status Change

Changed
 RF4 Status Change (Server Detected)
 iRelay FEM Status
 SAS Grant Status
 iRelay P1 PDCL Status Changed
 SAS Grant Suspension Status
 iRelay Scan List Empty in Specific
Band Changed  SAS Heartbeat Status
 iRelay Scan List Empty Status  SAS Registration Update

Changed
 SAS Spectrum Inquiry Update
 iRelay Scan List PDCL Status
Changed  SBA Configuration Status Changed
 Link Down  Scan Status
 Link Up  Server CPU Usage Change
 Lockout  Server Disk Usage Change
 Management IP Info Change  Server Event Queue Size Change
 Management Profile (16e) Change  Server Memory Usage Change
 Management Service Started  Serving Netspan Address Status

Change
 Management Service Stopped
 MBSFN SF Configuration Conflict
 SF Creation Failure
 MCE Connectivity
 SF Creation Success
 Measured BW Status Change
 S-GW S1-U Comms Status Change
 MIB Provisioning Change
 MME PLMN Overload Service
Interruption Status Changed  SNMPv3 Fallback Status Changed

 MME PLMN Overload Without Service  Software Activate

Interruption Status Changed
 Software Download
 MME S1-C Comms Status Change
 Software Upgrade Fault
 Motor Failure
 Software Upgrade State Change
 Neighbour Addition Rejected
 Summary Connection Status
 Neighbouring Cell in NRT
 SW Bank Info Changed
 NetspanSF Node Config Error
 Synchronisation Source Changed
 NetspanSF Server Error
 System Information Truncation
 Network Entry Status Change
 Tamper Status Change
 Network Profile (16e) Change
 TFTP Failure
 NL Sync Clock Source Operation
Status Change  TFTP Success
 NL Sync Procedure Status Change  TWAMP Overload Status Changed
 NLM Frequency Scan  TWAMP Sender Operational Status

Change
 NMS Licence Change
 NMS Restart Complete
 Unauthorized File Upload Attempted
 Node 10MHz Clock Status Change
 Unknown
 Node Action Error
 VoiceMAX Comms Change
 Node Added
 Warm Start
 Node Agent Active State Change
 WiFi Board Connectivity
 Node Agent ID Change
 WiFi Board Initialization
 Node Call Trace Status Changed
 Wman-IF Draft 1 Node Trap (SNMPv1)
 Node Clock Source Status Change

Action Error
Description An action, for example a reboot, was unsuccessful.
Event Type ID 126
eNodeB,
iBridge LOS,
iBridge NLOS,
Relay,
Relay eNodeB,
WiMAX 16e/16d
Event Trigger A user action failed on the equipment.
Event Information States the action that has failed.
Active Clock Source Change
The eNodeB reports a change in its active clock

Description
source.
Event Type ID 664
Applicable Hardware Type eNodeB
The eNodeB changed its active clock source and

Event Trigger
reported the new active clock source.
Check whether a Clock Source Availability Change

Event Information
was reported along with this event.
A-GPS File Status Change
Description Indicates a change in the A-GPS file status.
Event Type ID 677
Applicable Hardware Type Relay eNodeB
This event is raised whenever the A-GPS file status

Event Trigger
(agpsFileStatus) changes.
Additional information about the A-GPS file status

change.
The status of the A-GPS file can be one of the
Event Information
following:
 Valid: When the eNodeB receives an A-GPS
file, it marks agpsFileStatus as Valid.

 Missing: If the eNodeB does not receive the

XTRA file, it marks agpsFileStatus as
Missing.
All MME S1-C Comms Status Change (per PLMN)
The node reports a change in the status of S1-C to

Description MME - per MME per PLMN (using the MME IP
address).
Event Type ID 669
The possible event triggers include:

 The S1AP SCTP connection established to a
Event Trigger specific MME.
 The S1AP SCTP connection to a specific
MME is lost.
Displays the following details:

 MME IP address
Event Information  Communication status – i.e. Active, Initialising
or Inactive.
 Connection status ─ i.e. Connected or Not
Connected
Authorization Failure
An SS or iBridge term with invalid credentials is

Description attempting to gain service on the node. Authorization
fails.
Event Type ID 43
iBridge NLOS,
WiMAX 16e/16d
An SS or iBridge term with invalid credentials

Event Trigger
attempts to gain service on the node.
Provides the channel on which the authorization

Event Information
failure has occurred.

Authorization Success
An SS or iBridge term with valid credentials is

Description attempting to gain service on the node. Authorization
is successful.
Event Type ID 42
iBridge NLOS,
WiMAX 16e/16d
An SS or iBridge term with valid credentials attempts

Event Trigger
to gain service on the node.
Provides the channel on which the authorization has

Event Information
occurred.
Auto PCI Range Changed
Description The range of PCI has been changed.
Event Type ID 595
The change in PCI range while Auto PCI is enabled

Event Trigger
and the current PCI is out of range.
Event Information Displays Auto PCI range changed.
Auto RSI Change
The RSI changed automatically and sends a

Description notification. This constitutes a SON change on the
BS.
Event Type ID 541
eNodeB,
Relay eNodeB
Event Trigger The route sequence index has changed.
Event Information Provides status information on the RSI change.

Auto RSI Selected Value
The eNodeB reports the Auto RSI mode and selected

Description
RSI value.
Event Type ID 596
Event Trigger The eNodeB configuration of the RSI value.
Provides information on the eNodeB Auto RSI Mode

Event Information
and the selected or configured RSI value.
Auto-Align Request Detected
Generated by Netspan due to a user request (button-

Description
click) to perform Auto-Align
Event Type ID 583
Applicable Hardware Type iBridge NLOS
Event Trigger User action (button-click)
Provides information on the detected Auto-Align

Event Information
Request.
Auto-Align Status Changed
Generated by the equipment due to an Auto-Align

Description
status change
Event Type ID 562
Event Trigger A change in the auto align status.
Provides information on the progress on the auto-

alignment process. It indicates when each separate
Event Information
direction is being tested, as the antenna is rotated
through a series of different angles.

Auto-PCI Allocation
The physical cell ID has been changed by SON on

Description
the equipment.
Event Type ID 533
eNodeB,
Relay eNodeB
Event Trigger SON changes the PCI on the equipment.
Provides a current status and further information

Event Information
relating to the PCI allocation.
Backhaul QoS BW Server Connection Status Change
A communication with the BW reservation server has

Description
failed.
Event Type ID 657
No heartbeat response from bw server or initial MBR

Event Trigger
fails
Additional information about the backhaul QoS BW

Event Information
server connection status change.
Backhaul Qos Capacity Limiting Status
Description Backhaul Qos Capacity Limiting Status.
Event Type ID 646
Applicable Hardware Type BS
Number of acceptable VoLTE calls is minor degraded

Event Trigger
due to degraded BH QoS.
“Degraded. Ongoing calls=:” ongoingcalls,

Acceptable calls=:” bhqosAcceptableCalls, “Test
Event Information Result=testResult (i.e. >threshold, Fail), “State=”State
(i.e. periodic or recovery), “Recovered. “State=”State
(i.e. periodic or recovery).

Backhaul Qos Service Affecting Status
Description Backhaul Qos Service Affecting Status.
Event Type ID 645
Number of acceptable VoLTE calls is majorly

Event Trigger
degraded due to degraded BH QoS.
“Degraded. Ongoing calls=:” ongoingcalls,

Acceptable calls=:” bhqosAcceptableCalls, “Test
Event Information Result=testResult (i.e. >threshold, Fail), “State=”State
(i.e. periodic or recovery), “Recovered. “State=”State
(i.e. periodic or recovery).
Basic Caps Exchange Failure
A failure occurs in the capacity exchange element of

Description the registration process between the cell and the
base station.
Event Type ID 41
Applicable Hardware Type WiMAX 16d/16e
There has been a failure in the capacity exchange

Event Trigger element of the registration process between the cell
and the BS.
Provides:
 Status information on the hardware.
Event Information
 The channel on which the failure has taken
place.
Basic Caps Exchange Success
The capacity exchange element of the registration

Description process between the cell and the base station has
been successful.
Event Type ID 40
Applicable Hardware Type WiMAX 16d/16e
A successful capacity exchange element of the

Event Trigger registration process between the cell and the base
station has taken place.

Provides:
 Status information on the hardware.
Event Information
 The channel on which the success has taken
place.
Battery Overtemperature (eNodeB)
This parameter indicates whether the event is raised

Description because the eNB has been disabled (true) or re-
enabled (false).
Event Type ID 654
This event is raised whenever the value of

Event Trigger
batteryOvertempEnb changes.
Event Information True/False.
Battery Overtemperature (WiFi)
This parameter indicates whether the event is raised

Description because the Wi-Fi has been disabled (true) or re-
enabled (false).
Event Type ID 653
This event is raised whenever the value of

Event Trigger
batteryOvertempWifi changes.
Event Information True/False.
BS Active ASN Gateway
Description The active ASN gateway has changed.
Event Type ID 516
Applicable Hardware Type WiMAX 16d / 16e
There has been an automatic change in the active

Event Trigger ASN gateway caused by either the loss or restoration
of the connection to the primary ASN gateway.
Event Information Provides:

 Status information on the active ASN gateway.

 The action that has been performed.
BS ASN R6 Comms Status Change
There has been a change in the R6 communications

Description
status between the BS and the ASN gateway.
Event Type ID 507
WiMAX 16e,
iBridge NLOS
The R6 connection between the BS and the ASN

Event Trigger
gateway has gone either up or down.
Event Information Provides details of the communications status.
BS ASN-GW Mode Change
The operational mode of the ASN gateway has

changed. This is an internal event indicating a
Description
change in the network profile, caused by the ASN
gateway being either used or not.
Event Type ID 140
eNodeB,
iBridge LOS,
Applicable Hardware Type iBridge NLOS,
Relay eNodeB,
WiMAX 16e/16d
Event Trigger The user changes the configuration of the ASN-GW.
Event Information Provides details of the current mode of the ASN GW.
BS Failed Actions Cleared
A user operation to clear the list of failed actions on

Description
the BS.
Event Type ID 128
eNodeB,
iBridge LOS,
iBridge NLOS,
Relay,
Relay eNodeB,
WiMAX 16e/16d

A user performs the operation to clear the failed

Event Trigger
actions.
Provides the name of the user who performed the

Event Information
action.
BS FEM Status Change
There has been a change in the FEM status of the

Description
base station.
Event Type ID 521
iBridge NLOS on Air Synergy,

Relay,
Relay eNodeB,
WiMAX 16e
Event Trigger The FEM status of the base station has changed.
Provides the current FEM status, for example

Event Information
notPresentRequired or notPresentNotRequired.
BS Inventory Added
Netspan has detected an addition to the base station

Description
inventory.
Event Type ID 120
eNodeB,
iBridge LOS,
iBridge NLOS,
Relay,
Relay eNodeB,
WiMAX 16e/16d
Event Trigger An addition is made to the BS inventory.
Event Information N/A
BS MSM Port Status Change
There has been a change in the MSM port status of

Description
the base station.
Event Type ID 506
Applicable Hardware Type WiMAX 16e / 16d

Event Trigger The MSM port status has either gone up or down.
Provides overall MSM port status information, giving

Event Information
the current status.
BS MSM Status Change
There has been a change in the MSM status of the

Description
base station.
Event Type ID 502
Applicable Hardware Type WiMAX 16e
Event Trigger MSM itself has either gone up or down.
Event Information Gives information on the status of the MSM.
BS Running Status Change
There has been a change in the running status of the

Description
base station.
Event Type ID 517
eNodeB,
Relay eNodeB
Event Trigger The running status of the base station is changed.
Provides information on the running status of the

Event Information
base station.
Calculate Sector Harmonic Mean Request Detected

Description
click) to calculate sector harmonic mean.
Event Type ID 582
Provides information on the detected Calculate

Event Information
Sector Harmonic Mean Request.

CBSD State Change
Description Indicates a change in the CBSD state.
Event Type ID 182
Event Trigger Triggered when there is a change in the CBSD state.
Additional information (for example, SAS response,

Event Information
expiry details, and so on) about the state change.
Cell 1 Status Change
Description Cell1 Status Change.
Event Type ID 665
Event Trigger RF-manager trap.
 In-Service (Normal Operation)

 Frequency Out of Range
Event Information
 Duplex Mismatch
 Out of Service
Cell 2 Status Change
Description Cell2 Status Change.
Event Type ID 666
Event Trigger RF-manager trap.
 In-Service (Normal Operation)

 Frequency Out of Range
Event Information
 Duplex Mismatch
 Out of Service

Cell Active Status Change
This event is raised when there is no activity in the

Description
cell during selfHealingNonActivityTimer.
Event Type ID 668
Absence of any activity in the cell during

Event Trigger
selfHealingNonActivityTimer triggers this event.
Event Information Additional information about the cell status change.
Cell Enabled State Change
The eNodeB reports a change in the Admin state of

Description
one of its cells.
Event Type ID 180
Applicable Hardware Type LTE
Manual configuration to Enable or Disable a cell from

Event Trigger
Netspan.
One of the eNodeB’s cells has been manually

Event Information
Enabled/Disabled.
Cell Outage Detected
Cell outage detected on a cell in an eNodeB by a

Description
centralized SON system.
Event Type ID 563
eNodeB,
Relay eNodeB
Centralized SON triggered event when it detects cell

Event Trigger
outage in an eNodeB.
Provides centralized SON system generated

Event Information
information.

Channel Action Error
There has been a problem in performing an action on

Description
the specified channel.
Event Type ID 125
Applicable Hardware Type WiMAX 16d
An error occurs when performing an action on a

Event Trigger
channel.
Event Information Gives details of the channel action that failed.
Channel Failed Actions Cleared
A user operation to clear the list of failed actions on

Description
the channel.
Event Type ID 129
eNodeB,
iBridge LOS,
Relay eNodeB,
WiMAX 16e/16d

Event Trigger
actions.

Event Information
action.
Channel Provisioning Error
A problem has occurred in configuring the per-

Description
channel configuration on the specified channel.
Event Type ID 104
eNodeB,
iBridge LOS,
Relay eNodeB,
WiMAX 16e/16d
Event Trigger A provisioning error occurs on the channel.

The area of the configuration in which an error

occurred is shown, along with the nature of the error,
Event Information for example:
BsSectorCarrierSenseConfigChanged:359:SnmpErro
r= GeneralError
Channel Reprovision
Description The channel has been reprovisioned.
Event Type ID 107
eNodeB,
iBridge LOS,
Relay eNodeB,
WiMAX 16e/16d
Event Trigger An action is taken to reprovision the channel.
Provides details on the type of the reprovision and

Event Information
the reason for it.
Channel Status Change
The node reports a change in its status (for example,

Description
In Service or Out of Service) per channel.
Event Type ID 526
eNodeB,
Relay eNodeB

 Set by the operator
Event Trigger  All RF chains of the channel are in the OOS
 All S1-C connections are down
 Holdover Expired - Loss of Sync
Displays one of the following statuses for the

channel:
Event Information
1. In Service
2. Out of Service

Clock Source Availability Change
The eNodeB reports a change in its active clock

Description
source.
Event Type ID 661
 “<Clock Source>” clock source enters

Event Trigger ‘Stabilizing’/’Standby’/’Active’ status
 “<Clock Source>” clock source becomes ‘N/A’
Event Information Check the clock source.
Clock Source Change
There has been a change in the source of the clock

Description
information.
Event Type ID 522
iBridge on AirSynergy,
Relay,
Relay eNodeB,
WiMAX 16e
Event Trigger The source of the clock information is changed.
States whether the clock source is set to:

1. Internal
Event Information
2. From a received channel
3. From GPS
Clock Source Configuration
The eNodeB reports that a configured clock source is

Description
unsupported.
Event Type ID 663
Event Trigger <Clock Source> clock source is not supported.
Event Information Disable the unsupported clock source.

CMS Status Change
Description Indicates a change in the CMS status.
Event Type ID 674
Event Trigger Triggered when there is a change in the CMS status.
Event Information Additional information from the node.
Cold Start
Description A piece of equipment has started from cold.
Event Type ID 11
eNodeB,
iBridge LOS,
iBridge NLOS,
Relay,
Relay eNodeB,
WiMAX 16e/16d
Event Trigger A piece of equipment is turned on.
Event Information States that the reset has been completed.
Command Failed
One of the debug commands that can be run on the

Description
equipment has failed.
Event Type ID 542
eNodeB,
Relay eNodeB
Event Trigger A debug command fails on the equipment.
Gives further information regarding the failed

Event Information
command.

CTS eNB Capacity Status Change
Indicates a change in the CTS eNodeB capacity

Description
status.
Event Type ID 414
eNodeB,
Relay eNodeB
More than 10000 eNodeBs tried to log to a specific

Event Trigger
CTS simultaneously.
Provides information on whether the capacity of the

Event Information
eNodeB has exceeded or not.
CTS Log Overwrite Status Change
Description Indicates a change in the CTS Log Overwrite status.
Event Type ID 413
eNodeB,
Relay eNodeB
The CTS depleted its log storage space and starts

Event Trigger overwriting old logs in FIFO manner (oldest is deleted
first).
Provides information on whether there is a change in

Event Information
the CTS Log Overwrite status.
CTS Logging Status Change
Description Indicates a change in the CTS Logging status.
Event Type ID 412
eNodeB,
Relay eNodeB
The CTS depleted its log storage space (no FIFO

Event Trigger
storage is defined on the CTS)

Event Information
the CTS Logging status.

CTS PTE Status Change
Description CTS PTE Status Change
Event Type ID 417
Applicable Hardware Type Call Trace Server
ITU Event Type Operational Violation
statusFolderAccessFailed
Event Trigger
statusAutoDisabled
CTS PTE Destination Folder Access Denied. CTS

Event Information
PTE Auto Disabled.
CTS Server Status Change
Description Indicates a change in the CTS Server status.
Event Type ID 411
eNodeB,
Relay eNodeB
Trace Log Start has reached the maximum allowed

Event Trigger
retransmissions (from the eNodeB).
Provides information on whether the CTS server is up

Event Information
or down.
CTS Time Sync Status Change
Description Indicates a change in the CTS Time Sync status.
Event Type ID 416
eNodeB,
Relay eNodeB
Event Trigger The CTS was unable to sync with a time server.

Event Information
the CTS Time Sync status.

CTS Trace Analysis Status Change
Description Indicates a change in the CTS Trace Analysis status.
Event Type ID 415
eNodeB,
Relay eNodeB
The CTS was unable to analyze the data received

Event Trigger
from the eNodeB (for example, corrupted data).
Provides information on whether the trace analysis

Event Information
has failed or not.
Deregistration
A subscriber or iBridge terminal has deregistered

Description
from the BS or iBridge BS it was registered on.
Event Type ID 39
iBridge NLOS,
WiMAX 16e/16d
A subscriber or iBridge terminal deregisters from its

Event Trigger
BS.
Provides details as to the cause of the deregistration,

such as:
 Re-registration attempt
Event Information
 Real time failure
 Deregistered
Also states the channel that has deregistered.
DFS Disruption Detected
Description Indicates frequency interference, causing disruption.
Event Type ID 520
iBridge NLOS,
WiMAX 16e
It has been detected that something else is using the

Event Trigger
same frequency.
States the type of the disruption that has been

Event Information
detected.

DFS Mode Change
Description The operational mode of the DFS has changed.
Event Type ID 519
iBridge NLOS,
WiMAX 16e
A change is made to the operational mode of the

Event Trigger
DFS.
Event Information Provides information on the current mode.
DFS Status Change
Description The status of the DFS has changed.
Event Type ID 518
iBridge NLOS,
WiMAX 16e
Event Trigger There is a change in the status of the DFS.
Gives details of:

 The current DFS status.
 The channel on which the change has taken
Event Information
place.
 The working downlink frequency.
 The working uplink frequency.
DHCP T2 Timer Status Change
The eNodeB reports a change in response when

Description
requesting a renewal from the DHCP server.
Event Type ID 625
DHCP information unavailable for the eNodeB part of

Event Trigger
the Relay eNodeB when sending a renewal request.
Provides information on DHCP timer expiration

Event Information
status.

Donor Cell Backhaul Quality Changed
Indicates whether the DeNB quality is below or above

Description
the defined SINR/SE threshold.
Event Type ID 594
Relay,
Relay eNodeB
Triggered when the DeNB quality falls below the

recommended quality threshold. It is cleared when a
Event Trigger
suitable DeNB with a quality above the recommended
threshold is found.
Can be one of the following:

 Unknown.
Event Information  Below threshold.
 Above threshold.
 Monitoring disabled.
Duplicate EMS
The FT detected that it is connected to two instances

Description of Netspan—one on the wireless and the other on the
wired connection.
Event Type ID 552
Event Trigger The FT has not been configured correctly.
Includes the IP address and type of the wired and

wireless connections. It also provides the status
Event Information which is an enumeration indicating that a trap has
been set. 0 indicates cleared and 1 indicates
detected.
EGP Neighbor Loss
Description A neighboring node is no longer reachable.
Event Type ID 16
eNodeB,
Applicable Hardware Type Relay eNodeB,
WiMAX 16e/16d

Event Trigger An EGP neighbor can no longer be reached.
Event Information Provides details of the node that has been lost.
Emergency Call Reset Delay
A reset of the eNodeB is delayed due to an

Description
emergency call being in progress.
Event Type ID 540
eNodeB,
Relay eNodeB
An eNodeB reset action is delayed due to an active

Event Trigger
emergency call.
Event Information Provides status information on the delay in the reset.
Enabled Port Down
The operational status of an active port is changed to

Description
down.
Event Type ID 560
eNodeB,
Relay eNodeB
The operational status of an active port is changed to

Event Trigger
down.
Event Information Provides port identification and status details.
eNodeB PDN Status Change
Indicates one of the following:

Description  A PDN mismatch detected
 A PDN mismatch cleared
Event Type ID 675
Event Trigger A change in the eNodeB PDN mismatch status.
Additional information on whether an eNodeB PDN

Event Information
mismatch was detected or cleared.

eSON Server Connection Change
Description The connection with the eSON server has been lost.
Event Type ID 543
eNodeB,
Relay eNodeB
Event Trigger The eSON server connection is lost.
Gives status information on the eSON server

Event Information
connection.
ETWS File Upload
Description eNB reports ETWS file upload.
Event Type ID 651
Event Trigger ETWS file upload was not successful.
Event Information ETWS file upload notification.
ETWS SFTP Session
eNB reports a change in SFTP session for ETWS

Description
logs.
Event Type ID 650
 SFTP session was successfully opened

 Opening SFTP session was not successful
Event Trigger
 SFTP session was closed due to an error
 SFTP session was successfully closed
Event Information SFTP Session change.

Ext PPS Stream Status Changed
The eNodeB reports a change to the quality of its

Description
EXT PPS stream status.
Event Type ID 591
Event Trigger Triggered when external PPS is lost.
Provides the following:

Event Information  Lock status
 Holdover reason
Failed Actions Cleared
Description A user operation to clear the list of failed actions.
Event Type ID 130
eNodeB,
iBridge LOS,
iBridge NLOS,
Relay,
Relay eNodeB,
WiMAX 16e/16d

Event Trigger
actions.

Event Information
action.
File Upload Change
The node sends a fileUploadResultTrap trap

Description whenever a transfer status attribute changes to either
success or failure.
Event Type ID 655
Event Trigger The operator launches a Log File Upload.

 logTransferTrapEnable: Boolean controlling

whether log transfer should generate a file
upload trap.
 archiveTransferTrapEnable: Boolean
controlling whether archive transfer should
generate a file upload trap.
 coreTransferTrapEnable: Boolean
controlling whether core file transfer should
generate a file upload trap.
 fileUploadResultTrap: A trap which is raised
when a corresponding file transfer status
attribute changes to success or failure. The
trap has the parameters
fileUploadStatusSource, fileUploadStatus,
Event Information and fileUploadStatusInfo.
 fileUploadStatusSource: An enumeration
which indicates which type of file transfer was
the source of the file upload status attribute
value. This is extensible and initially has the
values none, currentLogs, latestLogArchive,
and latestCoreArchive. It is initialised to none
after application restart/reboot.
 fileUploadStatus: An enumeration which
indicates the status of the last completed file
upload; values are none, success, failure. It is
initialised to none after application
restart/reboot.
 fileUploadStatusInfo: A text string indicating
the most likely reason that the transfer failed.
Fine-Scan Request Detected

Description
click) to perform a fine-scan.
Event Type ID 584
Provides information about the detected Fine-Scan

Event Information
Request.
Force Scan Request Detected

Description
click) to perform a force-scan.
Event Type ID 573

Provides information about the detected Force Scan

Event Information
Request.
Forced Management Status Changed
The equipment entered or left the management

Description
mode.
Event Type ID 585
Applicable Hardware Type Relay
This event is triggered under the following conditions:

 APN2 attachment fails.
 Attached to a non-PDCL donor cell when
PDCL lock is set to True.
Event Trigger  GPS persistency failure.
 The unit moves out of the management
mode.
 The operator explicitly sets the management
mode.
Provides the reason for why the equipment moved

Event Information into the management mode (for example, cell id,
EARFCN, cell quality, and so on).
Forced Reset
A user performs a forced reset. This will occur

Description regardless of the emergency call status on the
eNodeB.
Event Type ID 139
eNodeB,
Relay eNodeB
Event Trigger A user performs a forced reset.
Provides the following information in relation to the

reset:
Event Information
 The channel on which the reset took place.
 The reason for the reset.

GPS Alarms Status Change
The GPS module reported an alarm. It indicates that

Description either the GPS module is in its startup phases, or a
failure.
Event Type ID 214
eNodeB,
iBridge NLOS,
Applicable Hardware Type Relay,
Relay eNodeB,
WiMAX 16e/16d
This event could be triggered by:

 The system clock might not be synchronized
to the GPS.
Event Trigger
 The RF subsystem might have disabled the
transmitter to prevent interference with other
nodes.
The status of the GPS alarm is reported with one (or

a combination of) of the following values:
0x01 = alarmInitWarmUp(0)
0x08 = alarmSnRange(3)
0x10 = alarmNoLock(4)
Event Information
0x18 = alarmSnRange(3) & alarmNoLock(4)
0x30 = alarmNoLock(4) & alarmHoldover(5)
0x48 = alarmSnRange(3) & alarmFreeze(6)
0x81 = alarmInitWarmUp(0) & alarmRefOscFault(7)
0x90 = alarmNoLock(4) & alarmRefOscFault(7)
GPS Comms Change
The node or BSDU reports a change in the

Description
communication status with the GPS module.
Event Type ID 203
eNodeB,
iBridge NLOS,
Relay eNodeB,
WiMAX 16e/16d
The Node or BSDU module lost communication with

the GPS module.
Event Trigger This event could be triggered by:
 The GPS module might be misconfigured and
the status reporting is not available.

 The system clock might lose synchronization.

 The GPS module may have failed.
Gives details of the current status of the

Event Information
communication with the GPS module.
GPS File Status Change
Description The node reports a change in the A-GPS file status.
Event Type ID 631
There has been a change in the A-GPS file status.

Possible states include:
 Valid: The A-GPS file has been successfully
downloaded and the file is valid.
 Expired: The A-GPS file is available in the
Event Trigger unit but the file contents are not valid.
 Missing: The A-GPS file has not been
downloaded or the file has been deleted from
the node.
 Not Applicable: The A-GPS functionality is
disabled or is not supported by the node.
Event Information Provides the A-GPS file status.
GPS Lock Change
The node or BSDU GPS module reports a change in

Description
the GPS lock status.
Event Type ID 204
eNodeB,
iBridge NLOS,
Relay eNodeB,
WiMAX 16e/16d
The Node or BSDU GPS module lost the timing lock

with the satellites.
Event Trigger If the system clock is not synchronized to the GPS,
States whether the status of the GPS lock is Locked

Event Information
or Lost.

GPS Persistency Status Changed
Description Indicates a change in the GPS Persistency status.
Event Type ID 581
Relay,
Relay eNodeB
There has been a change in the GPS Persistency

state. The possible states include:
 DISABLED: The feature is disabled but traps
are still sent.
Event Trigger
 IN: The unit is within the permitted area.
 OUT: The unit is outside the permitted area.
 UNKNOWN: The GPS location of the unit is
unknown.
The text corresponding to each of the states above is

as follows:
 GPS Persistency is currently disabled.
 Basestation is within permitted area. Current
Event Information Radius = * m.
 Basestation is outside permitted area. Current
Radius = * m.
 GPS Persistency Status is unknown.
Note: * indicates a radius value in meters.
GPS Reduced Holdover
The holdover time (the time a unit can operate

Description
without GPS clock lock) has been reduced.
Event Type ID 219
eNodeB,
iBridge NLOS,
Relay eNodeB,
WiMAX 16e/16d
Event Trigger The GPS holdover time is reduced.
Provides details of:

1. The configured insufficient buffer holdover
Event Information time (in minutes).
2. The expiry insufficient buffer holdover time (in
minutes).

GPS SNR Change
Description The node reports a change in the GPS SNR.
Event Type ID 213
eNodeB,
iBridge NLOS,
Relay eNodeB,
WiMAX 16e/16d
This alarm is an indication of a poor signal level and it

might lead to a lock loss.
The probable causes of this event include:
 The Node GPS module has a low SNR (that
Event Trigger is, the Node GPS Receiver Status reports
SNR Low).
 The GPS antenna is faulty.
 The GPS antenna cable is faulty.
 The sky view is limited or partially obstructed.
Event Information Provides the current status of the GPS SNR.
Hardware Replaced
Description Indicates that the hardware has been replaced.
Event Type ID 164
Applicable Hardware Type Netspan EMS
Event Trigger The user performed a hardware swap on Netspan.
Event Information Contains the details of the hardware swap.
Hardware Swap
Description The user has manually performed a hardware swap.
Event Type ID 632
Applicable Hardware Type Applies to all node types.

Performing a manual hardware swap using Netspan

Event Trigger
triggers this event.

Event Information  Old hardware name.
 New hardware name.
ICIC Misconfiguration
eNB reports colliding D-ICIC/SFR/MCIM

Description
configuration.
Event Type ID 647
ITU Event Type Integrity Violation
 SFR Enabled while D-ICIC is enabled.

Event Trigger
 D-ICIC Enabled while SFR is enabled.
 Attempted to enable SFR while D-ICIC is ON

– Request Ignored.
Event Information
 D-ICIC enabled while SFR is ON. SFR has
been disabled.
Ignore
Description For internal use only.
Event Type ID 2
eNodeB,
iBridge LOS,
Relay eNodeB,
WiMAX 16e/16d
Event Trigger N/A
Event Information For internal use only.
IKEv2 SA Expiry

Description rekeying process with the SeGW. The IKEv2 SA is
about to expire (that is, the traffic will be lost).
Event Type ID 554
Applicable Hardware Type eNodeB,

Relay eNodeB

Event Trigger
rekeying process with the SeGW.
All eNodeB traffic using this IPsec tunnel will be lost

Event Information
upon the expiry of the IKEv2 SA.
Initial Ranging Failure
There has been a failure during the initial ranging

Description
element of the sign on process.
Event Type ID 36
Applicable Hardware Type WiMAX 16e/16d
The initial ranging element of the sign on process

Event Trigger
fails.
Provides the StatusInfo as Real time failure,

Event Information
indicating failure, and gives the channel.
Initial Ranging Success
The initial ranging element of the sign on process has

Description
been successful.
Event Type ID 35
The initial ranging element of the sign on process

Event Trigger
succeeds.
Provides the StatusInfo as Ok, indicating success,

Event Information
and gives the channel.
Inventory Status Change
This event happens when a critical inventory item is

Description
missing.
Event Type ID 567
iBridge LOS,
iBridge NLOS,
Relay,
Relay eNodeB


 For Relay/Relay eNodeB: If the ranges file is
missing or invalid.
 For Relay/Relay eNodeB and iBridge: If
Event Trigger any of the following is missing:
o Main board inventory MAC address.
o Serial number.
o Equipment product code.

1. For Relay/Relay eNodeB: Details of the
missing/invalid ranges file.
Event Information 2. For Relay/Relay eNodeB and iBridge:
Details of the missing critical inventory item
(that is, Main board inventory MAC address,
Serial number, or Equipment product code).
IPsec SA Expiry
The eNodeB is unable to renew the IPsec SA. The

Description IPsec SA is about to expire (that is, the traffic will be
lost).
Event Type ID 553
eNodeB,
Relay eNodeB
The eNodeB is unable to renew the IPsec SA with the

Event Trigger
SeGW.
All eNodeB traffic using this IPsec SA will be lost

Event Information
upon the expiry of the tunnel.
iRelay Donor Cell Connectivity Status Changed
The equipment’s connection status with the

Description previously selected donor cell configured in the PDCL
has changed.
Event Type ID 579

 The equipment losses connection to the
previously connected donor cell from the
Event Trigger
PDCL.
 The equipment reconnects back to a donor
cell from the PDCL.

Provides the reason for why the equipment raised

Event Information
this event (along with the cell id of the cell).
iRelay FEM Status
This event indicates an error condition associated

Description
with FEM operation.
Event Type ID 564
Relay,
Relay eNodeB
This event can occur due to the following reasons:

 calibrationFault: The ranges file is missing
or invalid.
 calibrationFault: The FEM calibration file or
files are missing or invalid.
 initialisationError: The FEM failed to
Event Trigger initialize.
 unSupportedBand: Received unsupported
band configuration from the application
software. This is unlikely to happen.
 freqOutOfRange: Request received to
configure the FEM with frequencies outside
the range of the band. This is unlikely to
happen.
The text corresponding to each of the reasons above

is as follows:
1. calibrationFault.
Event Information
2. initialisationError.
3. unSupportedBand.
4. freqOutOfRange.
iRelay P1 PDCL Status Changed
The equipment’s connection status to the highest

Description
priority cell in the PDCL has changed.
Event Type ID 578

 The equipment losses connection to the
highest priority donor cell from the PDCL.
Event Trigger
 The equipment regains connection to the
highest priority donor cell from the PDCL.
 Configuration change.

Provides the reason why the equipment raised this

Event Information
event (along with the cell id of the cell).
iRelay Scan List Empty in Specific Band Changed
The iRelay unit failed to find any donor cell in the

Description
current scanned band.
Event Type ID 580
Relay,
Relay eNodeB
This event is raised when the iRelay unit fails to find

Event Trigger
any donor cell in the current scanned band.
Provides the reason why the equipment raised this

Event Information
event (along with the band number).
iRelay Scan List Empty Status Changed
Indicates whether the equipment was able to find any

Description
donor cell during the band scan process.
Event Type ID 576
Relay,
Relay eNodeB

 No donor cell found during the band scan
Event Trigger
process.
 A donor cell found during the scan.

Event Information
this event.
iRelay Scan List PDCL Status Changed
Indicates whether the equipment was able to connect

Description
to a donor cell from the PDCL.
Event Type ID 577

Event Trigger  No donor cell from the PDCL was found in the
scan list.

 A donor cell from the PDCL was found in the

scan list.
 Configuration change.

Event Information
this event.
LAN Device Connection Status Change
A LAN device is detected as connected or

Description
disconnected to the node’s Ethernet port.
Event Type ID 679
This event is triggered as connected under the

following conditions:
 Ethernet Port Admin is configured as LAN
 Backhaul type is LTE and APN is attached
 LAN Device APN is not null
 LAN Device is physically connected
Event Trigger
This event is triggered as disconnected under the
 Device physically disconnected causing
DHCP request failure
 LAN Device APN is changed
 LAN Device APN is detached
Indicates whether the LAN device connected or

Event Information disconnected, provides the LAN device MAC address
and the node’s hardware id.
LAN Device MAC Address Mismatch
A LAN device is detected as connected or

disconnected to the node’s Ethernet port, but does
Description
not match the configured AV-C device MAC Address
range. Another type of LAN Device is connected.
Event Type ID 680
This event is triggered as connected under the

 The LAN Device Connection Status Changed
Event Trigger event has occurred
 The LAN Device MAC Address does not
match the configured AV-C device MAC
Address range

Indicates that that LAN Device MAC Address does

Event Information match the AV-C range, provides the LAN device MAC
address and the node’s hardware id.
Link Down
One of the network interfaces reported the Link

Description
Down operational state.
Event Type ID 13
iBridge LOS,
iBridge NLOS,
Relay eNodeB,
WiMAX 16e/16d

 One of the network or radio interfaces is not
operational.
 The Ethernet cable is disconnected (for
example, the Ethernet connection with other
hosts connected to the same network is lost)
or the Ethernet interface is faulty.
 Loss of connection to the infrastructure
network.
Event Trigger For iB460:
 IfIndex 2: eth1―external physical Ethernet
port.
 IfIndex 3: eth0―internal physical Ethernet
port (fit on iB460, fit on iB400).
For iRelay:
 IfIndex 2: eth0―physical Ethernet port.
Reports the admin status (AdminStatus, with values

Event Information of up or down) and operational status (OperStatus,
with values of up or down) of the link.
Link Up
One of the network interfaces reported the Link Up

Description
operational state.
Event Type ID 14
iBridge LOS,
iBridge NLOS,
Relay eNodeB,
WiMAX 16e/16d


 A network of radio interface is restored.
Event Trigger  The Ethernet connection is restored.
 A connection is established with the
infrastructure network.
Reports the admin status (AdminStatus, with values

Event Information of up or down) and operational status (OperStatus,
with values of up or down) of the link.
Lockout
Description eNB reports a lockout issue.
Event Type ID 644
 eNB initiated a lockout.

Event Trigger
 eNB is out of a lockout.
Event Information Password reset.
Management IP Info Change
The management IP information on the iBridge

Description
terminal has changed.
Event Type ID 528
iBridge NLOS,
WiMAX 16e
A change is made to the management IP information

Event Trigger
on the iBridge terminal.
Provides the following details of the iBridge terminal

associated with the event:
1. MAC address.
Event Information
2. IP address type.
3. IP address.
4. SNMP port number.

Management Profile (16e) Change
A change is made to the management profile on

Description
WiMAX 16e.
Event Type ID 121
A user makes a change to the management profile on

Event Trigger
WiMAX 16e.
Gives the name of the user who made the change to

Event Information
the management profile.
Management Service Started
One of the network management systems (NMS) has

Description
started.
Event Type ID 102
Applicable Hardware Type Server
Can be triggered by any of the following NMS types

being started:
 AAA Management Service.
 Alarm Service.
 Archive Service.
Event Trigger  Discovery Service.
 Event Service.
 Job Engine Service.
 Provisioning Service.
 Software Manager Service.
 Statistics Service.
States the name of the NMS service that has been

Event Information started (ServiceName) and the current status of that
service (ServiceStatus).
Management Service Stopped
One of the network management systems (NMS) has

Description
stopped.
Event Type ID 101


being stopped:
 Alarm Service.
 Event Service.
States the name of the NMS service that has been

Event Information stopped (ServiceName) and the current status of that
service (ServiceStatus).
MBSFN SF Configuration Conflict

Description contained a conflict between two or more MBSFN SF
configurations.
Event Type ID 547
eNodeB,
Relay eNodeB

Event Trigger contained a conflict between two or more MBSFN SF
configurations.
The eNodeB is in the Awareness mode and will not

Event Information participate in the eMBMS service until the conflict is
cleared.
MCE Connectivity
Description The M2 interface towards the MCE is down.
Event Type ID 546
eNodeB,
Relay eNodeB
Event Trigger The M2 interface towards the MCE is down.
The eNodeB is in the Awareness mode and will not

Event Information participate in the eMBMS service until the MCE
connectivity is restored.

Measured BW Status Change
Description Indicates a change in the measured BW.
Event Type ID 656
Triggered when there is a change in the measured

Event Trigger
BW.
MIB Provisioning Change
There has been a change as to whether subscribers

Description
are provisioned via the MIB.
Event Type ID 155
A user has updated the configuration to change

Event Trigger
whether users are provisioned via the MIB.
Provides details of:

Event Information  The user who made the provisioning change.
 The MIB provisioning now in place.
MME PLMN Overload Service Interruption Status Changed
The MME is overloaded for a PLMN which has no

Description
other serving MMEs.
Event Type ID 587
eNodeB,
Relay eNodeB
Reception of the S1 Overload Start message for a

Event Trigger
PLMN for which there are no other serving MMEs.
MME with IP address <IP> is in overload state for

Event Information
PLMN <PLMN> - service interruption

MME PLMN Overload Without Service Interruption Status Changed
The MME is overloaded for a PLMN for which there is

Description
at least another serving MME.
Event Type ID 588
eNodeB,
Relay eNodeB
Reception of the S1 Overload Start message for a

Event Trigger PLMN for which there is at least another serving
MME.
MME with IP address <IP> is in overload state for

Event Information
PLMN <PLMN>
MME S1-C Comms Status Change
The node reports a change in the status of S1-C to

Description
MME - Per MME (using the MME IP address).
Event Type ID 525
eNodeB,
Relay eNodeB

 The S1AP SCTP connection established to a
Event Trigger specific MME.
 The S1AP SCTP connection to a specific MME
is lost.
Displays:
 MME IP address.
Event Information  Communication status of Active, Initialising or
Inactive.
 Connection status of Connected or Not
Connected.
Motor Failure
The motor in the base station fails, meaning that the

Description
unit can no longer rotate.
Event Type ID 545
iBridge NLOS
Relay

Event Trigger The motor in the base station fails.
Provides details on the nature of the motor failure on

the BS, whether the rotation isn’t happening at all, is
happening but is not stopping, or is getting stuck.
Event Information
Where a motor failure occurs, the transmitters are
disabled and an RF Status Change event is triggered
with an associated alarm.
Neighbour Addition Rejected
A neighbor is manually configured through the NMS

Description
when the cell NRT is full.
Event Type ID 570
eNodeB,
Relay eNodeB
Provisioning of a new NMS neighbor when the cell

Event Trigger
NRT is full.
Event Information NRT is full: Neighbor <eCGI> Addition Rejected
Neighbouring Cell in NRT
Description Neighboring cell in NRT.
Event Type ID 642
1. Neighboring cell has been deleted from NRT

due to PCI change.
Event Trigger
2. An X2 connection has been deleted due to
PCI change.
NRT changed due to an update of the PCI ranges’

Event Information
configuration.
NetspanSF Node Config Error
NetspanSF has detected an error when generating a

Description
PnP or node configuration for a specific node.
Event Type ID 589
Applicable Hardware Type NetspanSF

Unable to generate a valid EARFCN within

NetspanSF. This may occur if NetspanSF does not
have geographical data corresponding to the GPS
Event Trigger
location of the element, lack of DeNodeB ECGI or an
inability to generate a valid EARFCN within the
configuration rules.
Event Information Details of the configuration error.
NetspanSF Server Error
Description NetspanSF has detected a general error.
Event Type ID 590
Applicable Hardware Type NetspanSF
 The expected software image naming

convention is not aligned between NetspanSF
and Netspan.
Event Trigger  Netspan-SF detected no GPS location
information available from node. This may
mean that the non-GPS location information
was sufficient if PnP was successful.
Event Information Details of the error.
Network Entry Status Change
There has been a change in the network entry status

Description
for a subscriber.
Event Type ID 31
Event Trigger The network entry status has changed.
Provides information on:

Event Information  The current network entry status.
 The channel to which the status is applicable.
Network Profile (16e) Change
There has been a change to the network profile

Description
configuration.
Event Type ID 143

A user makes a change to the network profile

Event Trigger
configuration.
Provides the name of the user who made the network

Event Information
profile change.
NL Sync Clock Source Operation Status Change
The eNodeB reports a change in NL Sync clock

Description
source’s operation.
Event Type ID 659
 NL Sync Clock Source Error was received.

Event Trigger
 RbtReq equals False.
NL Sync Procedure Status Change
The eNodeB reports a change in NL Sync procedure

Description
operation.
Event Type ID 658
 NL Sync Clock Source Error <as stated in the

‘status’ field in the received QMI_NL
message> was received.
Event Trigger  No error is stated in the status filed in a
received QMI_NL message.
 No error is stated in the status field in a
received QMI_NL message.
NLM Frequency Scan
The eNodeB reports about Network Listening Module

Description
frequency scan.
Event Type ID 660

 The eNodeB reports that there are NO

applicable frequencies for the Network
Listening Module to scan; hence, the entire
Event Trigger band will be scanned.
 The eNodeB reports that there are applicable
frequencies for the Network Listening Module
to scan.
NMS Licence Change
Description There has been a change in the NMS licence.
Event Type ID 144
Event Trigger A user changes (adds or deletes) NMS licence.
Provides the name of the user who made the NMS

Event Information
licence change.
NMS Restart Complete
A notification that one of the Network Management

Description
Systems (NMS) has successfully restarted.
Event Type ID 123

being restarted:
 Alarm Service.
 Event Service.
Event Information States that the particular NMS has restarted.

Node 10MHz Clock Status Change
The node lost or gained the 10 MHz signal from the

Description
GPS timing source and might cease to transmit.
Event Type ID 511
The system automatically detects that there has been

Event Trigger
a change in the 10MHz clock status on a node.
States whether a 10 MHz clock can be detected or

Event Information
not.
Node Action Error
There was a problem in performing an action on this

node. The node SNMP agent reported an error when
an action was invoked from the EMS.
Description
This event, caused by a potential software error, is
typically used for identifying issues during the system
verification and validation tests.
Event Type ID 124
eNodeB,
iBridge NLOS,
Relay eNodeB,
WiMAX 16e/16d
A problem occurs when performing an action on a

Event Trigger
node.
Displays the failed change which caused the action

Event Information
error.
Node Added
Description A new node has been added.
Event Type ID 109
eNodeB,
iBridge LOS,
iBridge NLOS,
Relay,
Relay eNodeB,
WiMAX 16e/16d

Event Trigger Triggered when a user adds a new node.
Event Information States the user who added the node.
Node Agent Active State Change
A node has changed its air interface type, for

Description
example from iBridge term to iBridge base.
Event Type ID 151
eNodeB,
iBridge LOS,
Relay eNodeB,
WiMAX 16e/16d
There has been a change in the active state of the

Event Trigger node agent, either from “Active” to “Inactive”, or from
“Inactive” to “Active”.
Provides the current ActiveState, whether it is Active

Event Information
or Inactive.
Node Agent ID Change
Description The agent ID of a node has changed.
Event Type ID 156
eNodeB,
iBridge LOS,
iBridge NLOS,
Relay,
Relay eNodeB,
WiMAX 16e/16d
Event Trigger A change is made to the node agent ID.
Event Information States the agent ID of the node.

Node Call Trace Status Changed
The node reports a change in the status of the Call

Description
Trace on one of its cells.
Event Type ID 568
eNodeB,
Relay eNodeB
This event could be triggered by:

 Initialization.
 Trace Log Start has reached the maximum
allowed retransmissions (from the eNodeB).
Event Trigger  Trace Log Start has not been acknowledged
and trace end time is reached (from the
eNodeB).
 Trace Log Keep-Alive has not been
acknowledged.
 Trace Log End has not been acknowledged.
Provides information on whether the Call Trace is

Event Information
active or inactive and any failure reasons.
Node Clock Source Status Change
There has been a change in the synchronization

Description
status of the node.
Event Type ID 571
eNodeB,
Relay eNodeB
The node reports that its synchronization status has

Event Trigger
changed.
The synchronization status can be one of the

following:
1. Initialization.
Event Information
2. Locked.
3. HoldOver.
4. HoldOver expired.
Node Config Status Change
The PTP grand master status of the node has

Description
changed.
Event Type ID 538
Applicable Hardware Type eNodeB,

Relay eNodeB
There has been a change in the PTP grand master

Event Trigger
status.
Event Information Provides details of the current configuration status.
Node Connection State Change
The connection state between Netspan and a node

Description
has changed.
Event Type ID 100
eNodeB,
iBridge LOS,
iBridge NLOS,
Relay,
Relay eNodeB,
WiMAX 16e/16d
There has been a change in the state of the node

Event Trigger
connection.
Provides the current state of the node connection.

This can be one of:
 Online.
Event Information
 NoComms.
 InvalidIpToldMap.
 InvalidWriteCommunity.
Node Current Change
The current on a node has either exceeded or

Description
Event Type ID 221
Applicable Hardware Type N/A
Event Trigger There has been a change in the current on a node.
Event Information Provides status information on the node current.

Node Deleted
Description A node has been deleted.
Event Type ID 110
eNodeB,
iBridge LOS,
iBridge NLOS,
Relay,
Relay eNodeB,
WiMAX 16e/16d
Event Trigger Triggered when a node is deleted.
Event Information States the user who removed the node.
Node Disk Usage Change
Node Disk usage has crossed the threshold. It is

Description based on an average over a period of time which is
configurable in the node.
Event Type ID 649
Event Trigger The Node Disk Usage has crossed the threshold.
Provides details of whether the disk usage is above

Event Information
or below the threshold.
Node Encryption Licence Invalid
An invalid encryption licence certificate is reported by

a node. The system falls back to an unencrypted
Description
mode of operation. The privacy and integrity OTA is
affected.
Event Type ID 211
eNodeB,
iBridge NLOS,
Relay eNodeB,
WiMAX 16e/16d
The node reports an Invalid Encryption Licence

Event Trigger
certificate.

States whether the LicenceCertInvalid property is

Event Information
True or False.
Node Feature Licence Expiring
The Feature Licence certificate applied to the node

is expiring or expired.
Description The system falls back to a mode of operation that
affected.
Event Type ID 512
iBridge NLOS,
WiMAX 16e/16d
The feature licence certificate for the node has less

Event Trigger
than 30 days remaining until it is invalid.
Provides the status information message:

1. Less than 30 days left for feature licence to
Event Information expire.
2. Gives an ExpiryStatusWarning stating the
number of days remaining for the licence.
Node Feature Licence Invalid
The node is set up with an Invalid Feature Licence

certificate. It limits the node capabilities.
Description The system falls back to a mode of operation that
affected.
Event Type ID 510
iBridge NLOS,
WiMAX 16e/16d
The system detects that there is an invalid feature

Event Trigger
licence on a node.
States whether the parameter LicenceCertInvalid is

True or False.
An additional information message is also displayed.
If the certificate is still valid, then the message reads
Event Information
Valid Feature Licence.
If the certificate has expired, then the message reads
Invalid Feature Licence with details of the specific
certificate that has expired.

Node Feature Not Implemented
One or more features requested on this node are not

implemented.
Description
The system falls back to a mode of operation that is
implemented. The performance might be affected.
Event Type ID 513
iBridge NLOS,
WiMAX 16e/16d
The system detects that there is an unimplemented

Event Trigger
feature on a node.
Provides status details of the unimplemented

Event Information
features.
Node Feature Not Licensed
The NMS licenses available on this server do not

permit the use of the requested features on any node
because they are not licensed.
Description
The system falls back to a mode of operation that
does not require a license. The performance might be
affected.
Event Type ID 514
iBridge NLOS,
WiMAX 16e/16d
The system detects that there is an unlicenced

Event Trigger
feature on a node.
States that there are unlicensed features, and then

Event Information provides a list of those features that have been
requested and are unlicensed.
Node GPS Receiver Status Change
Description The node reports a GPS receiver status change.
Event Type ID 224
eNodeB,
Relay eNodeB
Event Trigger The SNR crossed the defined threshold.
Event Information Displays one of the following statuses:

1. GPS Receiver SNR is too low; GPS accuracy

might be degraded.
2. GPS Receiver SNR Normal.
Node Internal Clock Status Change
The node reports a change in its internal clock status

(for example, Frame Lock Lost, PLL Lock Lost, and
Description
so on) describing the hardware faults that lead to the
loss of synchronization.
Event Type ID 222
eNodeB,
Relay eNodeB

 GPS receiver comms lost.
Event Trigger
 PLL Lock Lost.
 Frame Lock Lost (1PPS lock loss).
Displays one of the following statuses:

 GPS receiver internal communication error.
Event Information
 Internal PLL Lock Lost.
 Internal Frame Sync Lost.
Node Invalid Configuration Change

Description
of the validation check failure during PnP.
Event Type ID 174
eNodeB,
iBridge NLOS,
Relay,
Relay eNodeB

Event Trigger
of the validation check failure during PnP.
Event Information Provides information about the validation failure.

Node LED Status Change
The overall permission to light the Status LED has

Description
changed.
Event Type ID 572
iBridge NLOS
Relay eNodeB
The value of asSynBdUnitStatusLedEnabled has

Event Trigger
changed.
Depending on the LED status, one of the following is

displayed:
1. Status LED enabled.
Event Information 2. Status LED disabled.
Note: The Unit Identify function will still be
allowed to light the LED for the defined
duration even in Status LED disabled state.
Node Local Access Attempt
The node reports that after the unit is operational, a

Description local access (for example - LAT, Web GUI) was
attempted (even though it was successful).
Event Type ID 535
eNodeB,
Relay eNodeB

 A successful or failed WebGUI attempt.
Event Trigger
 A successful or failed SSH attempt.
 A successful or failed serial attempt.
Provides the following information in relation to the

local access attempt:
1. Login status.
Event Information
2. Channel on which the access attempt took
place.
3. User name who made the access attempt.
Node Maintenance Transition
This event is generated when a Node transitions to or

Description
from the Maintenance state.
Event Type ID 132

Applicable Hardware Type 16e BS
User configures Node to be in maintenance state or

Event Trigger
configures Node to move from maintenance state.
Whether the Node has moved to or from

Event Information
maintenance state.
Node Management Change
The management mode of the node has been

Description
changed.
Event Type ID 137
eNodeB
iBridge LOS,
iBridge NLOS,
Relay,
Relay eNodeB,
WiMAX 16e/16d
Event Trigger A user changes the management mode of the node.
Provides:
 The current management mode of the node,
Event Information
so Managed or Unmanaged.
 The name of the user who made the change.
Node Message Change Failed
This event is raised when Netspan receives a request

Description for the API ‘RelayEnbError’ and there is a failure in
sending the request to the node.
Event Type ID 184
Event Trigger SOAP Request : RelayENbError.
Event Information SNMP IPAddress, HWID, message.

Node Message Change Success
This event is raised when Netspan receives a request

Description for the API ‘RelayEnbError’ and is successfully able
to send the request to the node
Event Type ID 183
Event Trigger SOAP Request : RelayENbError.
Event Information SNMP IPAddress, HWID, message.
Node NTP Status Change
There has been a change in the network time

Description
protocol status.
Event Type ID 515
Relay,
WiMAX 16e
Event Trigger The status of the NTP changes.
Provides the current status of the NTP. The possible

status messages are:
1. NoError
2. ClockNotSet
Event Information
3. If there is no error, an additional status
message is provided reading Clock set ok. If
the clock is not set, an additional status
message is provided stating NTPDATE has
terminated with an error.
Node Operational Status Change
Description The operational status of the node has changed.
Event Type ID 501
eNodeB,
iBridge NLOS,
Relay eNodeB,
WiMAX 16e/16d

There has been a change in the operational status of

Event Trigger
the node.
Event Information Gives the current operational state of the node.
Node Operational Status Change (Server Detected)
The server has detected that the operational status of

Description
the node has changed.
Event Type ID 133
eNodeB,
iBridge NLOS,
Relay eNodeB,
WiMAX 16e/16d
By polling, the server has detected that the

Event Trigger
operational status of the node has changed.
Provides the current operational status of the node,

Event Information
whether it is InService or OutOfService.
Node Power Change
The power on a node has either exceeded or

Description
Event Type ID 220
Applicable Hardware Type N/A
Event Trigger There has been a change in the power on a node.
Event Information Provides details of the node’s current power status.
Node Provisioning Error
The node SNMP agent or the Netspan server

reported an error (for example - potential software
error, configuration validity, or inconsistency error) on
Description the provisioning failure.
Typically, this alarm is used for identifying issues
during the system verification and validation tests.
Event Type ID 103
eNodeB,
iBridge LOS,

iBridge NLOS,
Relay,
Relay eNodeB,
WiMAX 16e/16d
There is an issue with configuring the per-Node

Event Trigger
configuration on the specified node.
Provides details of the provisioning error. The

software or configuration error is listed as a
FailedChange.
Event Information
There is then further information defining the
SnmpError type, whether it is a GeneralError or
TargetIsUnmanaged.
Node PTP Grand Master Status Change
The node reports a change in its PTP status (and the

Description
relevant IP address of the configured GM).
Event Type ID 537
eNodeB,
Relay eNodeB

 Reliable stream of Sync messages from the
Event Trigger GM.
 No reliable stream of Sync messages from
the GM.

Event Information 1. Grand Master Valid.
2. Grand Master Invalid.
Node PTP Quality Status Change
PDV conditions in the 1588 PTP stream have

Description
changed
Event Type ID 565
eNodeB,
Relay eNodeB
 PDV in the 1588 PTP stream is too high and

may cause synchronization issues.
Event Trigger
 PDV in the 1588 PTP stream is back to
normal.

Check the transport network quality. Confirm proper

Event Information
QoS configuration.
Node Redirection Failure
Description Redirection service failed to configure the Node.
Event Type ID 179
Event Trigger Node offline or incorrect redirection details.
Event Information Details of the Node for which redirection failed.
Node Redirection Request
Description Redirection request forwarded to Netspan SF.
Event Type ID 177
Event Trigger Redirection request received by NMS.
Event Information Details of the Node requesting redirection.
Node Redirection Success
Description Redirection service configured the Node.
Event Type ID 178
Event Trigger Node redirection details configured correctly.
Event Information Details of the Node for which redirection succeeded.

Node Reprovision
Description A node has been reprovisioned.
Event Type ID 106
eNodeB,
iBridge LOS,
iBridge NLOS,
Relay,
Relay eNodeB,
WiMAX 16e/16d
Event Trigger A node has been reprovisioned.
Provides details on the Type of reprovision, whether

it was Automatic or Manual, and the reason for the
reprovision. The reason will be one of the following:
Event Information 1. Software Upgraded.

2. Manual Reprovision.
3. Transition to Managed.
4. Plug and Play.
Node Resources Status Change
Description eNB reports available resources are low.
Event Type ID 635
1. Mean CPU load is above threshold: Bit 1 = 1.

2. Mean Memory Utilization is above threshold:
Event Trigger Bit 2 = 1.
3. Mean number of RRC connections is above
threshold: Bit 3 = 1 or Bit 3 = 1.
1. For CPU trigger: “Low CPU Resources”.

2. For Memory trigger: “Low Memory
Event Information Resources”.
3. For RRC trigger: “Low RRC Resources”,
Including the overloaded Cell ID and PCI.

Node Restarted (Server Detected)
Description Netspan detects that a node has restarted.
Event Type ID 150
eNodeB,
iBridge LOS,
iBridge NLOS,
Relay,
Relay eNodeB,
WiMAX 16e/16d
Event Trigger A node restarts.
Event Information Gives the date and time of the node restart.
Node Self Test
Description There has been a hardware problem at the node.
Event Type ID 534
eNodeB,
Relay eNodeB
Event Trigger Part of the node’s hardware has stopped working.
Provides the status and any other relevant

Event Information
information relating to the self-test.
Node Shutdown
Indicates that the node is shut down and out of

Description service. The node service is temporarily lost until it
restarts automatically.
Event Type ID 201
eNodeB,
iBridge LOS,
iBridge NLOS,
Relay,
Relay eNodeB,
WiMAX 16e/16d


 The node is manually reset.
Event Trigger
 The node is too hot.
 A software error.
Provides a reason code for the shutdown. This will be

one of:
 Manual reset.
 Unrecoverable software error.
 Hot board protection.
Also gives additional information to explain the
shutdown. The possible messages are:
 Management initiated.
Event Information
 RFCP failure.
 SW activation.
 Process malfunction (phy0).
 Process malfunction (rtmacbs).
 Process malfunction (uldatabs).
 RNG initiated reboot.
 <node type>:Critical.
Node Software Version Status Change
There has been a change to the software version

Description
status of a node.
Event Type ID 539
eNodeB,
Relay eNodeB
Event Trigger The software version status on a node is changed.
Provides the current status information of the node’s

Event Information
software version.
Node SS BPKM Fail
Description There has been a failure of the SS BPKM.
Event Type ID 34
Event Trigger The subscriber station BPKM fails.
Names the base station on which there has been a

Event Information
failure.

Node SS Dynamic Service Fail
Nodes are able to get services dynamically, rather

than having them pre-provisioned by Netspan. This
Description
event registers when there has been a failure in the
dynamic service provisioning action.
Event Type ID 32
Event Trigger The dynamic service provisioning fails.
Provides the following information on the dynamic

service failure:
1. The dynamic service type on which the failure
Event Information occurred.
2. A failure reason.
3. The channel on which the failure occurred.
Node SS RSSI Status Change
The RSSI status on a node has changed enough to

Description make it either exceed or drop below an alarm
threshold.
Event Type ID 33
Event Trigger There is a change in the RSSI status on a node.
Gives the current status of the RSSI and the channel

Event Information
on which the status change took place.
Node Sync Lock Status Change
Description The eNodeB reports a change in its Lock status.
Event Type ID 662
 The eNodeB is in the Init State.

 The eNodeB moves to the Lock state.
Event Trigger  The eNodeB moves to the Holdover state.
 The eNodeB moves to the Holdover Expired
state.

Event Information Check the clock source(s).
Node Synchronization Lock Status Change
The node reports a change in its synchronization

Description state, until the Clock Unit implementation is
available, reported either by the GPS or by the PTP.
Event Type ID 223
eNodeB,
Relay eNodeB

 Initializing
Event Trigger  Locked
 Holdover (only for the GPS)
 Holdover Expired - Loss of Sync

1. Initializing
2. Synchronization locked: Normal operation
Event Information 3. All configured clock sources are unavailable:
eNodeB in the holdover state (only for the
GPS)
4. Max holdover time expired: All RF
transmissions are stopped
Node Temperature Change
The node trap reporting the temperature of one or

Description more modules in the node crossed the warning
threshold.
Event Type ID 202
eNodeB,
iBridge NLOS,
Relay,
Relay eNodeB
A specific temperature sensor crossed the defined

Event Trigger
threshold.

1. Low temperature reached.
Event Information
2. Normal temperature.
3. High temperature reached.

Node Tilt Changed
There has been a change in the physical tilt of the

Description
node.
Event Type ID 529
iBridge LOS,
WiMAX 16e
Event Trigger The angle at which the node is tilted is changed.
Gives a tilt status of either:

1. Tilt High.
Event Information 2. Tilt Low.
Provides additional details on the precise angle of the
tilt.
Node Timing Frame Lock

The node lost the timing lock with the external GPS
or PTP timing source.
Description Because the transmitter is turned off, the node might
cease transmission when in this state. Consequently,
the service will be temporarily lost.
Event Type ID 205
iBridge NLOS,
WiMAX 16e
A node loses its timing frame lock with the external

Event Trigger
GPS or PTP timing source.
Gives status information on the current frame lock,

stating whether the node is locked or not locked to a
Event Information
timing source, and also provides information on
whether a clock is detected or not detected.
Node Voltage Status Change
The node reports a change in its module DC voltage

Description
status.
Event Type ID 212
eNodeB,
Relay eNodeB
A specific voltage sensor crossed the defined

Event Trigger
threshold.

Displays one of the following statuses in relation to

the DC voltage:
1. Out of range.
Event Information
2. Nominal.
Provides additional status information detailing
whether the associated alarm is On or Clear.
Node X2 Neighbour Status Change
The node reports a change in its X2 neighbor status

Description (for example - Neighbour ID by the IP, eNodeB ID,
Cell ID, Type).
Event Type ID 527
eNodeB,
Relay eNodeB

 A neighbor removed from the NRT.
Event Trigger
 Loss of connection to a neighbor.
 Establishing connection to a neighbor.

1. Neighbor removed from the NRT.
Event Information 2. Connection to neighbor lost.
3. Connection to neighbor established.
4. Not connected (init).
Operator Certificate Expiry

operator certificates from the CMS. The eNodeB is
Description
reverting to factory certificates and will restart the
CMPv2 process.
Event Type ID 555
eNodeB,
Relay eNodeB

Event Trigger
operator certificates from the CMS.
The eNodeB is reverting to the factory certificates

Event Information
and will restart the CMPv2 process.

Outdoor Cell Status Changed
Description Relay eNodeB’s outdoor cell changed its status.
Event Type ID 624
Relay eNodeB
Applicable Hardware Type Note: This event type applies to Relay eNodeB using
outdoor cells only.
 The outdoor cell of Relay eNodeB turned its

Tx off.
Event Trigger
 The outdoor cell of Relay eNodeB turned its
Tx on.
Relay eNodeB’s outdoor cell changed its status.

Event Information Check the channel quality (SINR or spectral
efficiency) of Relay.
P1 CDCL Status Changed
Failure to connect to the highest priority DeNB in the

Description
PDCL even though it is in the Scan List.
Event Type ID 593
Event Trigger Triggered when a low priority cell is selected.
Event Information Provides information about the P1 CDCL.
Password Change
A password change request was invoked from the

Description
eNodeB CLI or from Netspan.
Event Type ID 636
A request for a password change invoked from the

Event Trigger
eNodeB CLI or from Netspan.
Event Information Additional information about the password change.

Password Reset
A password reset request was sent to the eNodeB

Description
from Netspan over SNMP v3.
Event Type ID 637
A request for a password reset was sent to the

Event Trigger
eNodeB from Netspan over SNMP v3.
Event Information Additional information about the password change.
PCI Conflict Status Changed
The eNodeB detected a PCI conflict, which is or is

Description
not resolved.
Event Type ID 641
The eNodeB resolved or did not resolve a PCI

Event Trigger
conflict.
Additional information about the PCI conflict status

Event Information
change.
PCI Range Configuration
Description PCI range configuration.
Event Type ID 643
eNB receives an X2 SETUP FAILURE message with

‘Cause’ IE set to ‘Message not Compatible with
Receiver State’ and ‘Criticality Diagnostics’ -> ‘IE
Event Trigger Criticality’ IE set to ‘reject’, and ‘Criticality
Diagnostics’ -> ‘IE ID’ IE set to ‘502’, and ‘Criticality
Diagnostics’ -> ‘Type Of Error’ IE set to ‘not
understood’
Event Information Validate PCI range configuration.

PCI Update Status Change
Description There was an on the fly PCI change attempt.
Event Type ID 671
Event Trigger On the fly PCI change attempt.
PCI Update Success: <Cell ID> Old PCI: <old PCI>

New PCI <new PCI>
Event Information
PCI Update Failure: <Cell ID> Old PCI: <old PCI>
New PCI <new PCI>
PHY Reset
A user has requested a PHY reset on the physical

Description
layer of the node.
Event Type ID 531
iBridge LOS,
WiMAX 16e
Event Trigger A user requests a PHY reset.
Specifies the event type that has caused the reset.

This will be one of:
1. Configuration change
2. Dump and reset
3. Other
Event Information
Also gives additional information to explain the reset
event in further detail. This could be:
1. Configuration change
2. RFPM requested ISDU PHY load
3. Tx/Rx out of sync (TxStartRespError)
PLL Status Change
Description There has been a status change with the PLL.
Event Type ID 218
iBridge NLOS,
WiMAX 16e

The PLL status change could indicate:

Event Trigger  SDR PLL lost lock to the SDR VCXO
A failure in one of the SDR components (VCXO).
Event Information Provides details of the current PLL status.
PnP Complete
All the phases of the PnP process have finished and

Description
PnP can be considered complete.
Event Type ID 181
Applicable Hardware Type enodeB, eRelay
Event Trigger PnP process is completed.
Event Information Provides the HID of the node.
PnP Config Added
Description PnP configuration has been added.
Event Type ID 556
eNodeB,
iBridge NLOS,
Relay,
Relay eNodeB
Event Trigger Addition of PnP configuration.
Provides the following details:

 PnP Hardware ID
Event Information  Latitude
 Longitude
 Latitude-longitude radius
PnP Config Deleted
Description PnP configuration has been deleted.
Event Type ID 557
eNodeB,
iBridge NLOS,

Relay,
Relay eNodeB
Event Trigger Deletion of PnP configuration.
Provides the following details:

 PnP Hardware ID
 Longitude
 Latitude-longitude radius
PnP Configuration Mismatch
Netspan received the PnP Identification event from

Description
the node, but PnP is not enabled in Netspan.
Event Type ID 160
eNodeB,
Relay eNodeB
There is a PnP configuration mismatch between

Event Trigger
Netspan and the node.
Presents the following information in relation to the

node that raised the PnP Identification event:
 IP address
Event Information  Hardware ID
 Latitude
 Longitude
 Reboot type
PnP Identification
A plug and play node has started and is requesting

Description
that the PnP process begins.
Event Type ID 532
eNodeB,
Relay eNodeB
A plug and play identification message is received

Event Trigger
from a node.
Provides the following information about the node

Event Information that raised the plug and play identification event:
 IP address

 Hardware ID
 Latitude
 Longitude
 Status of PnP
 Reboot type
 Warm reboot mask
 Product code
 Public IP address
 Netspan version
PnP Location Changed
Description The node reports a change in the PnP location.
Event Type ID 159
eNodeB,
Relay eNodeB
A PnP-enabled node changed its location beyond the

Event Trigger configured location radius since its last restart. The
node restart process is halted.
States the following information in relation to the

node’s new location:
 New latitude
Event Information
 New longitude
 Distance from previously configured radius in
metres
PnP Node Discovery Failed
Description Netspan couldn’t discover the plug and play node.
Event Type ID 162
eNodeB,
Relay eNodeB
Event Trigger Discovery failed on a plug and play node.

node that could not be discovered:
 IP address
Event Information
 Hardware ID
 Latitude
 Longitude

 Reboot type
PnP Node Matched Multiple Config
PnP Identification match multiple PnP Configuration

Description
items.
Event Type ID 633
Applicable Hardware Type Any Node Type
PnP Identification matched more than one PnP

Event Trigger
Configuration.
Event Information Details of the Node sending PnP Identification.
PnP Node Not Configured
The eNodeB part of the Relay eNodeB is starting its

Description
configuration.
Event Type ID 165
Event Trigger Triggered when the eNodeB profiles are not set.

that raised the plug and play not configured event:
 IP address
 Hardware ID
 Longitude
 Status of PnP
 Reboot type
 Warm reboot mask
PnP Node Not Found
A plug and play identification event has been

Description received by Netspan from a node but there is no
matching configuration on the server.
Event Type ID 161
eNodeB,
Relay eNodeB

Netspan cannot find configuration to match a

Event Trigger
received PnP identification event.

node that could not be found:
 IP address
Event Information  Hardware ID
 Latitude
 Longitude
 Reboot type
PnP Node Not Managed
PnP cannot continue because the node is set to the

Description
Unmanaged state.
Event Type ID 166
Applicable Hardware Type Applies to all node types
Received a PnP Site Identification trap from a node

Event Trigger that has been discovered in Netspan. This node is
currently set to the Unmanaged state.
Event Information Provides the IP address and hardware ID of the trap.
PnP State Change
A PnP node goes through a sequence of states when

Description it registers, changes location, etc. Each time it
transitions between states, this event is triggered.
Event Type ID 158
eNodeB,
Relay eNodeB
Event Trigger There is a change in the PnP state of a node.
Gives the current PnP state, providing information on:

1. Discovery.
Event Information 2. Configuration.
3. Software.
4. Completed status.

PnP Trigger
This indicates the initiation of the PnP process when

Description a PnP configuration is created that matches an
unprocessed site identification trap received earlier.
Event Type ID 176
eNodeB,
iBridge NLOS,
Relay,
Relay eNodeB
Creation of a PnP configuration that matches an

Event Trigger unprocessed PnP site identification trap received
earlier.

that raised this event:
1. IP address.
2. Hardware ID.
Event Information 3. Latitude.
4. Longitude.
5. Status of PnP.
6. Reboot type.
7. Warm reboot mask.
Port Disable Prevention
The Port Disable command is blocked because this

Description
port is considered as a management port
Event Type ID 559
eNodeB,
Relay eNodeB
Event Trigger The Port Disable command is blocked.
Port Status Changed
Description The operational status of a port was changed.
Event Type ID 561
eNodeB,
Relay eNodeB

Event Trigger The operational status of a port was changed.
Provisioning Error
There has been a provisioning error when changing

Description
the configuration of the equipment.
Event Type ID 105
eNodeB,
iBridge LOS,
iBridge NLOS,
Relay,
Relay eNodeB,
WiMAX 16e/16d
A provisioning error occurs when changing

Event Trigger
equipment configuration.
Provides details of the specific provisioning change

that failed (FailedChange), the sector in which the
Event Information
error occurred (Sector) and the nature of the SNMP
error (SnmpError).
PTP Hardware
If the system is configured for PTP synchronization

and the system clock is not synchronized to the PTP,
Description
Event Type ID 523
iBridge NLOS,
WiMAX 16e
The PTP hardware configuration does not support the

Event Trigger
PTP Slave operation.
Provides further information on the current PTP

Event Information
hardware profile.

PTP Master Availability Changed
There was a change in the availability of the

Description
configured 1588 Masters.
Event Type ID 586
eNodeB,
Relay eNodeB
 All configured 1588 Masters are unavailable.

Event Trigger  At least one configured 1588 Master is
available.
There was a change in the availability of the

Event Information
configured 1588 Masters.
PTP Timing Sync
The PTP clock synchronization with the PTP master

is lost.
Description synchronization and the system clock is not
synchronized to the PTP, the RF subsystem disables
nodes.
Event Type ID 524
iBridge NLOS,
Relay,
Relay eNodeB,
WiMAX 16e

 The result of the PTP clock synchronization
fault.
Event Trigger
 Loss of communication with the IEEE1588
PTP master.
 The PTP protocol failure.
Provides status information on whether the PTP

timing synchronization is enabled or not Enabled,
Event Information
and additional details on the SyncAlarmCount. This
has a value of 1 if PTP is not enabled.
QoS Handover Neighbour Change
No neighbors with a configured QoS-based Mobility

Description EARFCN exist at this time. QoS-based handovers will
fail.
Event Type ID 558

eNodeB,
Relay eNodeB
A QoS-based handover has been triggered, but no

Event Trigger
neighbor exists for the configured EARFCNs.
QoS-based handovers will not succeed until a

Event Information
suitable neighbor is found.
Registration Failure
There has been a failure during the registration

Description
element of the sign on process.
Event Type ID 38
Event Trigger The registration element of the sign on process fails.
Presents further details of:

Event Information 1. Registration status information.
2. The channel on which the failure took place.
Registration SubOptimal
Description Registration is on a sub-optimal channel.
Event Type ID 138
Registration has taken place on a sub-optimal

Event Trigger
channel.
Identifies the current channel and the preferred

Event Information
channel.
Registration Success
Description The channel registration has been successful.
Event Type ID 37

Event Trigger Registration has been successful.
Gives status information with values of:

1. OK.
Event Information 2. Registered.
Where the value is registered, further details are
provided relating to the Channel that has registered.
Remote Connection Change
There has been a change in the status of the remote

Description connection between the node and the node on the
other end of the link.
Event Type ID 163
Applicable Hardware Type iBridge LOS
The remote connection link has either gone up or

Event Trigger
down.
States whether the remote connection is Up or

Event Information
Down.
Reprovision
Description A piece of equipment has been reprovisioned.
Event Type ID 108
eNodeB,
iBridge LOS,
iBridge NLOS,
Relay,
Relay eNodeB,
WiMAX 16e/16d
Event Trigger The equipment has been reprovisioned.
States the Type of the reprovision. This is either:

1. Automatic.
2. Manual.
Event Information
Provides a Reason for the reprovision, such as:
1. Software upgraded.
2. Manual reprovision.

Reset
Description A user has requested a reset.
Event Type ID 154
eNodeB,
iBridge LOS,
iBridge NLOS,
Relay,
Relay eNodeB,
WiMAX 16e/16d
Event Trigger A user has requests a reset.
Event Information Provides the name of the user who initiated the reset.
RF Path Imbalance Detected
There is an imbalance in the RF path where there is a

Description
stronger signal in one half of the RF than the other.
Event Type ID 530
iBridge LOS,
WiMAX 16e
Event Trigger An imbalance is detected in the RF path.
States whether the RF path imbalance status is

either:
1. Unknown.
Event Information 2. Not balanced.
Where the status is not balanced, gives additional
information on the number of terminals that are
unbalanced.
RF Status Change
Description The status of the RF has changed.
Event Type ID 503
eNodeB,
iBridge NLOS,
Relay eNodeB,
WiMAX 16e

Event Trigger There has been a change in the status of the RF.
Event Information Provides details of the current RF status.
RF Status Change (Server Detected)
Description The server detects a change in the RF status.
Event Type ID 134
iBridge NLOS,
WiMAX 16e
Event Trigger The server detects a change in the RF status.
Event Information Provides details of the current RF status.
RF1 Status Change
The node reports a change in the RF1 status (for

Description example - fault asserted, fault cleared, or a change in
the management configuration).
Event Type ID 504
eNodeB,
iBridge NLOS,
Relay eNodeB,
WiMAX 16e

 In-Service (Normal Operation).
 Frequency Out of Range.
 Duplex Mismatch.
Event Trigger
 Calibration Warning.
 Out of Service.
 Tx Power Out of Range.
 VSWR Threshold Crossed.
The status of the RF is reported with one (or a

combination of) of the following status values:
0x00000000000000000000 = RF alarms set
Event Information 0x00000000000000000002 = Calibration fault
0x00000000000000000008 = Tx Off Configured
0x00000000000000000020 = Tx Off Timing Loss
0x00000000000000000100 = PA Disabled

0x00000000100000000000 = TX power out of range

0x00000002000000000000 = Low forward power
0x00000004000000000000 = 1 PPS invalid
0x00000080000000000000 = Frame unlocked
0x00100000000000000000 = Tx power estimated
0x00800000000000000000 = RF not enabled
RF1 Status Change (Server Detected)
The server detects a change in the RF1 status (for

Event Type ID 135
iBridge NLOS,
WiMAX 16e
Netspan polls a node and detects an RF1 status

Event Trigger
change.

0x00000000000000000000 = RF alarms set
0x00000000000000000002 = Calibration fault
Event Information 0x00000000000000000100 = PA Disabled
0x00000004000000000000 = 1 PPS invalid
0x00000080000000000000 = Frame unlocked
0x00800000000000000000 = RF not enabled
RF2 Status Change

Event Type ID 505
eNodeB,
iBridge NLOS,
Relay eNodeB,
WiMAX 16e

Event Trigger


 Out of Service.

0x00000000000000000000 = RF alarms set
0x00000004000000000000 = 1 PPS invalid
0x00000080000000000000 = Frame unlocked
0x00800000000000000000 = RF not enabled

Event Type ID 136
iBridge NLOS,
WiMAX 16e

Event Trigger
change.

0x00000000000000000000 = RF alarms set
0x00000004000000000000 = 1 PPS invalid
0x00000080000000000000 = Frame unlocked
0x00800000000000000000 = RF not enabled

RF3 Status Change

Event Type ID 508
eNodeB,
iBridge NLOS,
Relay eNodeB,
WiMAX 16e

Event Trigger
 Out of Service.

0x00000000000000000000 = RF alarms set
0x00000004000000000000 = 1 PPS invalid
0x00000080000000000000 = Frame unlocked
0x00800000000000000000 = RF not enabled

Event Type ID 141
iBridge NLOS,
WiMAX 16e

Event Trigger
change.


0x00000000000000000000 = RF alarms set
0x00000004000000000000 = 1 PPS invalid
0x00000080000000000000 = Frame unlocked
0x00800000000000000000 = RF not enabled
RF4 Status Change

Event Type ID 509
eNodeB,
iBridge NLOS,
Relay eNodeB,
WiMAX 16e

Event Trigger
 Out of Service.

0x00000000000000000000 = RF alarms set
0x00000004000000000000 = 1 PPS invalid
0x00000080000000000000 = Frame unlocked
0x00800000000000000000 = RF not enabled


Event Type ID 142
iBridge NLOS,
WiMAX 16e

Event Trigger
change.

0x00000000000000000000 = RF alarms set
0x00000004000000000000 = 1 PPS invalid
0x00000080000000000000 = Frame unlocked
0x00800000000000000000 = RF not enabled
SAS Grant Status
Description The eNodeB reports the Grant procedure status.
Event Type ID 628
 Grant Approved:
Reception of Grant Response with errorCode=0:
“SAS Grant Approved”
 Grant Denied, Suggested Parameters:
Reception of Grant Response with errorCode≠0
with supported operationParam: “SAS Grant
Event Trigger Denied, Suggested Frequency/TX Power:
<operationParam-
>operationalFrequencyRange>/<operationParam-
>peakPower>”
 Grant Denied:
Reception of Grant Response with errorCode≠0
with unsupported / missing operationParam: “SAS
Grant Denied. <errorCode>”

 Grant Renewal Denied:

Reception of Heartbeat Response for a grant
renew message with errorCode = 0 and
grantExpireTime is unchanged: “Grant Renewal
Denied!”
 Grant Renewal Failed:
Reception of Heartbeat Response for a grant
renew message with errorCode ≠ 0: “Grant
Renewal Failed! <errorCode>”
 Grant Renewed:
Reception of the Heartbeat Response message
with errorCode=0 and new grant expiry time:
“Grant Renewed. New grant expires at:
<grantExpireTime>”
 Grant Terminated, Frequency Reallocation:
with errorCode = 500 (TERMINATED_GRANT)
and operationParams IE specifying a new
frequency than the one configured: “Reallocating
Frequency. Grant Terminated”:
 Grant Terminated:
with errorCode = 500 (TERMINATED_GRANT)
and without a new value in operationParams:
“Grant Terminated. Transmission Stopped”
 Grant Expired:
Grant time expiry: “Grant Expired. Transmission
Stopped”
Event Information Provided the SAS Grant status
SAS Grant Suspension Status
The eNodeB reports that the SAS Grant is suspended

Description
or resumed.
Event Type ID 630
 Grant Suspended:
Transmit time expiry or reception of the
Heartbeat Request message with errorCode =
501 (SUSPENDED_GRANT): “Grant
Suspended. Transmission Stopped”
Event Trigger  Grant Resumed - Transmit Expiry Time
Received:
Reception of the Heartbeat Request message
with errorCode = 0 and a new
transmitExpireTime: “New Transmit Expiry
Time Received, Resuming Transmission”
Provides information on whether SAS Grant is

Event Information
suspended or resumed

SAS Heartbeat Status
The eNodeB reports the SAS Heartbeat procedure

Description
status.
Event Type ID 629
 Starting Transmission:
Reception of the first Heartbeat Response
with errorCode=0: “First Heartbeat
Successful. Starting Transmission”
Event Trigger  Heartbeat Procedure Failure:
Heartbeat response not received for
predefined consecutive times: “Heartbeat
Response not received for <hbKeepAlive>
times”
Event Information Provides the SAS Heartbeat procedure status
SAS Registration Update
The eNodeB reports the SAS server registration

Description
status.
Event Type ID 626
 Registration Approved:
Reception of Registration Response with
errorCode=0: “SAS Registration Approved”
 Registration Denied:
Reception of Registration Response with
errorCode≠0: “SAS Registration Failed:
<errorCode>”
Event Trigger
 Deregistration:
Upon sending the Deregistration Request
message: “Deregistered from SAS Server”
 Registration Suspended:
The NMS configured frequency is not with in
the CBRS range and SI procedure is
disabled.
Event Information Provides SAS Registration update

SAS Server Connection State Change
The causes include:

 Change in the physical communication status
(that is, IP not reachable/IP reachable)
between Netspan as CBRS Domain Proxy
Description and the SAS server
 Change in the validity (that is, valid/invalid) of
the X.509 certificate exchange for the TLS
connection between Netspan as CBRS
Domain Proxy and the SAS server
Event Type ID 186
This event is triggered:

 When there is a change in the IP connectivity
between Netspan as CBRS Domain Proxy to
Event Trigger
the SAS server
 When there is a change in the validity of the
X.509 certificate
Provides the reason for the failure of TLS connection

Event Information
with the SAS server.
SAS Spectrum Inquiry Update
The eNodeB reports the Spectrum Inquiry procedure

Description
status.
Event Type ID 627
 Successful Spectrum Inquiry:

Reception of Spectrum Inquiry Response with
errorCode=0 and successful frequency
selection: “SAS Spectrum Inquiry Completed
Successfully. Selected Frequency and
bandwidth: <cbrsDLFreq>Hz, <cbrsBW>MHz”
 Spectrum Inquiry Failure – Unsupported
Parameters (eNodeB):
Event Trigger Reception of Spectrum Inquiry Response with
availableChannel not supported by the
eNodeB: “Spectrum Inquiry Failed, Available
Channels not supported by the eNodeB”
 Spectrum Inquiry Failure – Unsupported
Parameters (SAS):
Reception of Spectrum Inquiry Response with
errorCode≠0: “Spectrum Inquiry Failed,
Requested Spectrum not Supported by SAS”

Event Information Provides Spectrum Inquiry update
SBA Configuration Status Changed
The requested SBA configuration was not set

properly, due to the following possible reasons
(described in the alarm status info):
Description
 The SBA reported configuration is different
from the requested configuration.
Event Type ID 566
AirHarmony 1100,
AirHarmony 4000

Event Trigger  The configuration read from the SBA is
different from the requested configuration.
Event Information Provides the SBA configuration.
Scan Status
Indicates whether a scan has started or completed on

Description
iRelay.
Event Type ID 592
Event Trigger Triggered when a scan has started or completed
Provides details of the scan that has started or

Event Information
completed.
Server CPU Usage Change
The server CPU usage has crossed the threshold. It

is based on an average over a period of time which is
Description
configurable in Netspan (Server > Server Global
Configuration).
Event Type ID 171

Event Trigger The server CPU usage has crossed the threshold.
Provides details of whether the CPU usage is above

Event Information
Server Disk Usage Change
The server disk usage has crossed the threshold. It is

based on an average over a period of time which is
Description
configurable in Netspan (Server > Server Global
Configuration).
Event Type ID 173
Event Trigger The server disk usage has crossed the threshold.
Provides details of whether the disk usage is above

Event Information
Server Event Queue Size Change
Indicates that the server event queue size has

Description changed.
Note: The current threshold is 12000.
Event Type ID 185
Applicable Hardware Type EMS
Triggered when the server event queue size

Event Trigger
changes.
Event Information Additional information about the status change.
Server Memory Usage Change
The server memory usage has crossed the threshold.

It is based on an average over a period of time which
Description
is configurable in Netspan (Server > Server Global
Configuration).
Event Type ID 172
Event Trigger The server memory usage has crossed the threshold.

Provides details of whether the memory usage is

Event Information
above or below the threshold.
Serving Netspan Address Status Change
Indicates one of the following:

 A mismatch between the serving Netspan IP
address and the eNodeB PDN type was
Description detected.
 The mismatch between the serving Netspan
IP address and the eNodeB PDN type was
cleared.
Event Type ID 676
Event Trigger A change in the serving Netspan IP address status.
Additional information on whether the serving

Event Information Netspan IP address mismatch was detected or
cleared.
Serving Security Gateway Status Change
Indicates a change in the Serving Security GW

Description
status.
Event Type ID 673
Triggered when there is a change in the Serving

Event Trigger
Security GW status.
SF Creation Failure
Service flow (SF) creation is an element of the sign

Description on process. This event occurs when that stage of the
process fails.
Event Type ID 47
Event Trigger Service flow creation fails.

Displays status information on the SF creation and

Event Information
the channel on which the action failed.
SF Creation Success
Service flow (SF) creation is an element of the sign

Description on process. This event occurs when that stage of the
process is successful.
Event Type ID 46
Event Trigger Service flow creation succeeds.
Displays status information on the SF creation and

Event Information
the channel on which the action succeeded.
S-GW S1-U Comms Status Change
There has been a change in the communication

Description
status with the SGW.
Event Type ID 544
eNodeB,
Relay eNodeB
The S1 connection with the SGW has either been lost

Event Trigger
or gained.
Displays the IP address of the SGW and the current

Event Information
status.
SNMP Authentication Failure
The management of the node is not possible. If the

node is configured, it continues operating as normal.
Description
However, the fault and performance management is
affected.
Event Type ID 15
An SNMP manager attempts to access the

Event Trigger
equipment with invalid credentials.
Provides details of the SNMP authentication that

Event Information
failed.

SNMPv3 Fallback Status Changed
Description The SNMPv3 fallback mechanism state has changed.
Event Type ID 569
eNodeB,
Relay eNodeB
A change in the state of the SNMPv3 fallback

Event Trigger mechanism (that is, a change from fallback on to
fallback off and vice versa).
Provides information on the existence of the

Event Information
encryption license and SNMPv3 mode of operation.
Software Activate
A sequence of events takes place during the software

Description upgrade process. Software activation is one of these
elements.
Event Type ID 153
eNodeB,
iBridge LOS,
iBridge NLOS,
Relay,
Relay eNodeB,
WiMAX 16e/16d
The software activate element of the software

Event Trigger
upgrade process is triggered.
States whether the software activation is in progress

Event Information
or has completed.
Software Download
A sequence of events takes place during the software

Description upgrade process. Software download is one of these
elements.
Event Type ID 152
eNodeB,
iBridge LOS,
iBridge NLOS,
Relay,
Relay eNodeB,
WiMAX 16e/16d

The software download element of the software

Event Trigger
upgrade process is triggered.
States whether the software download is in progress

Event Information
or has completed.
Software Upgrade Fault
Description Indicates a change in software upgrade state.
Event Type ID 175
eNodeB,
Relay eNodeB
Event Trigger An attempt to upgrade software triggers this event.
Provides information about why the attempt to

Event Information
upgrade software failed.
Software Upgrade State Change
The status of a software upgrade changes depending

on which upgrade events (download, activation, etc.)
Description
have taken place. This event is triggered by a change
in the status of one of these events.
Event Type ID 157
eNodeB,
iBridge LOS,
iBridge NLOS,
Relay,
Relay eNodeB,
WiMAX 16e/16d
Event Trigger There is a change in the state of a software upgrade.
Gives further information relating to the current status

Event Information of the software upgrade, for example whether there is
a download pending.

Summary Connection Status
The overall (summary) status of the currently

Description
connected devices.
Event Type ID 634
There is a change in the status of the connected

Event Trigger
devices.
'none' means no devices are connected, 'fault'

Event Information means one or more devices are in the fault state, and
'normal' means all devices are operating normally.
SW Bank Info Changed
Description Reports the current used bank and version.
Event Type ID 597
Event Trigger Triggered on startup
Provides the following information:

 "Node operating from SW bank %d, using SW
version %s".
Event Information Provides the following information if bank switching
was identified:
 "Node had switched to SW bank %d, using
SW version %s".
Synchronization Source Changed
Description AU-ENB synchronization.
Event Type ID 638
Applicable Hardware Type AU-ENB
Event Trigger Synchronization Source Changes (24h Threshold).
Provides Boolean information of the event

Event Information
(True/False)

System Information Truncation
System information Blocks payload is truncated by

Description
the eNodeB.
Event Type ID 575
eNodeB,
Relay eNodeB
System information blocks payload is truncated by

Event Trigger the eNodeB due to exceeding maximum SI size
(277B).
This event informs which SIBs are truncated

according to the alarm definition. Upon reception of
Event Information
payload of all ‘0’, event information will be ‘All SIBs
are sent properly’.
Tamper Status Change
Description Tamper detection status is changed.
Event Type ID 652
Applicable Hardware Type AirUnity
There is an unauthorized physical manipulation of the

Event Trigger
AU-ENB parts.
Indicates if the tamper detection status is changed;
Event Information
and gives more information as defined in the AU.
TFTP Failure
There has been a failure during the TFTP element of

Description
the sign on process.
Event Type ID 45
Event Trigger TFTP fails during sign on.
Provides further details relating to the current status

Event Information
information, and the channel impacted.

TFTP Success
The TFTP element of the sign on process has been

Description
successful.
Event Type ID 44
Event Trigger TFTP succeeds during sign on.
Provides further details relating to the current status

Event Information
information, and the channel impacted.
TWAMP Overload Status Changed
The eNodeB reports a chance in its TWAMP

Description
Reflector service.
Event Type ID 640
Number of incoming TWAMP packets crossed the

Event Trigger
acceptable threshold.
Provides information about the TWAMP Reflector

Event Information
service and load.
TWAMP Sender Operational Status Change
Description TWAMP sender operational status.
Event Type ID 648
ITU Event Type Integrity Violation
The TWAMP Sender Operational Status has

Event Trigger
changed.
Event Information The new Operational Status of the TWAMP Sender.

UE Trace and MDT Status Change
The eNodeB reports a successful trace activation or

Description
deactivation.
Event Type ID 670
The eNodeB successfully activated or deactivated a

Event Trigger
trace.
Additional information from the node about the trace

Event Information
and MDT status change.
Unauthorized File Upload Attempted
A file upload attempt comes from an IP address that

either isn’t a managed node or is otherwise approved
Description
by Netspan. As a result, the file fails an authorization
check.
Event Type ID 536
There has been an attempt to upload an

Event Trigger
unauthorized file.

file upload attempt:
1. The IP address from where the upload was
Event Information attempted.
2. The name of the file that was uploaded.
3. The size of the file that was uploaded (in kB).
Unknown
An SNMP trap is received that is unsupported in

Description
Netspan.
Event Type ID 1
eNodeB,
iBridge LOS,
Relay eNodeB,
WiMAX 16e/16d
Event Trigger An unknown SNMP trap is received.

Event Information Details are provided of the unsupported SNMP trap.
VoiceMAX Comms Change
There has been a change in the communication

Description
status between the node and VoiceMAX.
Event Type ID 215
eNodeB,
WiMAX 16d/16e
Event Trigger The node loses communication with VoiceMAX.
Displays the current VoiceMAX communication

Event Information
status.
Warm Start
A piece of equipment has started from a reset rather

Description
than a cold start.
Event Type ID 12
iBridge LOS,
WiMAX 16e/16d
Event Trigger A piece of equipment is reset.
Event Information Provides information on the status of the reset.
WiFi Board Connectivity
The eNodeB is not able to communicate with the Wi-

Fi board. If configured to do so, the node shall send
the Wi-Fi Board Connectivity event if there is a
protocol error when communicating with the Wi-Fi
Description
module. Parameters shall include
iFiStatusConnectivityStatus (wifiDown(0), wifiUp(1),
or wifiNone(2)), and
WiFiStatusConnectivityStatusInfo.
Event Type ID 551
Applicable Hardware Type AirVelocity with Wi-Fi
The Wi-Fi board failed to respond to a number of

Event Trigger
consecutive keep-alive messages.

Communications were lost with the WiFi board.

The following are the probable causes:
Event Information 1. Very long WiFi software upgrade duration.
2. Software failure.
3. Hardware failure.
WiFi Board Initialization
The unit is not able to initialize communications with

Description
the Wi-Fi board.
Event Type ID 550
Applicable Hardware Type AirVelocity with Wi-Fi
The Wi-Fi board failed to respond to the initialization

Event Trigger
messages even after resetting several times.
The Wi-Fi board failed to initialize. The following are
the probable causes:
Event Information
1. An incorrect software version.
2. Hardware failure.
Wman-IF Draft 1 Node Trap (SNMPv1)
Description A standard WiMAX trap. For internal use only.
Event Type ID 48
eNodeB,
iBridge LOS,
Relay eNodeB,
WiMAX 16e/16d
Event Trigger N/A
Event Information For internal use only.

A Abbreviations
Term Expansion
A-GPS Assisting-GPS
AAA Authentication, Authorization and Accounting
Ack Acknowledged
AP Application Protocol
APN Access Point Name
ASN Access Service Network
ASN-GW Access Service Network Gateway
ATE Automatic Test Equipment
AV-C AirVelocity Companion
BPKM Baseline Privacy Key Management
BS Base Station
BSDU Bridge Protocol Data Unit
BW Bandwidth
CBRS Citizen Broadband Radio Service
CBSD Citizen Broadband Radio Service
CDCL Candidate Donor Cell List
CLI Command Line Interface
CLPC Closed Loop Power Control
CMP Certificate Management Protocol
CMS Certificate Management System
CRL Certificate Revocation List
CTS Call Trace Server
DC Direct Current
DeNB Donor eNodeB
DFS Dynamic Frequency Selection
DHCP Dynamic Host Configuration Protocol
D-ICIC Dynamic Inter-Cell Interference Coordination
EARFCN E-UTRA Absolute Radio Frequency Channel Number
EGP Exterior Gateway Protocol
eMBMS evolved Multimedia Broadcast/Multicast Service
EMS Element Management System
eNodeB Evolved Node B
eSON EUTRAN Self-organizing network

Term Expansion
ETWS Earthquake and Tsunami Warning Service
FEM Front–End Module
FIFO First In First Out
FQDN Fully Qualified Domain Name
FT Feeder Terminal
GM Grand Master
GPS Global Positioning System
GUI Graphical User Interface
GUMMEI Globally Unique Mobile management Entity Identifier
HTTP Hypertext Transfer Protocol
HWID Hardware ID
IKE Internet Key Exchange
IP Internet Protocol
IPsec Internet Protocol Security
ITU International Telecommunication Union
LAT Local Access Terminal
LFP Low Forward Power
LOS Line-of-Sight
LTE Long Term Evolution
MAC Media Access Control
MBR Master Boot Record
MBSFN Multicast-broadcast single-frequency network
MCE Multi-cell / Multicast Coordination Entity
MDT Minimization of Drive-Tests
MIB Management Information Base
MIMO Multiple-Input and Multiple-Output
MME Mobility Management Entity
MSM Media Switch Module
NBIF Northbound Interface
NE Network Element
NLOS Non-Line-of-Sight
NMS Network Management System
NRT Neighbor Relation Table
NTP Network Time Protocol
OBSAI Open Base Station Architecture Initiative

Term Expansion
OOS Out of Service
OSS Operational Support Systems
OTA Over-the-Air
PCI Physical Cell Identity
PDCL Preferred Donor Cell List
PDN Public Data Network
PDV Packet Delay Variation
PHY Physical Layer
PLL Phase Lock Loop
PLMN Public Land Mobile Network
PnP Plug and Play
PPS Pulse-per second
PTP Precision Time Protocol
QCI Quality of Service Class Identifier
QoS Quality of Service
RF Radio Frequency
RNeNB Relay Node eNodeB
RRC Radio Resource Control
RSI Route Sequence Index
RSSI Received Signal Strength Indicator
SA Security Association
SAS Spectrum Access System
SBA Switched Beam Antenna
SCRT Single Channel Radio Transceiver
SCTP Stream Control Transmission Protocol
SDR Software Defined Radio
SeGW Security Gateway
Choose the appropriate expansion depending on the context:

SF  Service flow
 Subframe
SFR Soft Frequency Reuse
SFTP Secure File Transfer Protocol
SINR Signal-to-Interference-Plus-Noise Ratio
SNMP Simple Network Management Protocol
SNR Signal-to-Noise Ratio
SOAP Simple Object Access Protocol

Term Expansion
SON Self-Organizing Network
SS Subscriber Station
TCE Trace Collection Entity
TFTP Trivial File Transfer Protocol
TWAMP Two-Way Active Measurement Protocol
Tx Transmit
UI User Interface
VCXO Voltage-Controlled Crystal Oscillator
VSWR Voltage Standing Wave Ratio

ARD-D00742 - Netspan Alarms and Events Reference Guide - SR16.00 - Standard - Rev 10.3

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

ARD-D00742 - Netspan Alarms and Events Reference Guide - SR16.00 - Standard - Rev 10.3

Uploaded by

Copyright:

Available Formats

Netspan Alarms and Events Reference

Part Number: ARD-D00742

ARD-D00742 Airspan Commercial and Internal Use i

ASN R6 Comms Loss ............................................................................................................. 28

ARD-D00742 Airspan Commercial and Internal Use ii

Donor Cell Poor Backhaul Quality .......................................................................................... 43

ARD-D00742 Airspan Commercial and Internal Use iii

ARD-D00742 Airspan Commercial and Internal Use iv

Node Shutdown ...................................................................................................................... 76

ARD-D00742 Airspan Commercial and Internal Use v

RF2 Carrier Sense Interference ............................................................................................. 93

ARD-D00742 Airspan Commercial and Internal Use vi

SNMP Authentication Failure................................................................................................ 110

3 Netspan Events ............................................................................... 119

ARD-D00742 Airspan Commercial and Internal Use vii

Auto RSI Selected Value ...................................................................................................... 130

ARD-D00742 Airspan Commercial and Internal Use viii

CMS Status Change ............................................................................................................. 142

ARD-D00742 Airspan Commercial and Internal Use ix

GPS Persistency Status Changed ........................................................................................ 155

ARD-D00742 Airspan Commercial and Internal Use x

Neighbour Addition Rejected ................................................................................................ 169

ARD-D00742 Airspan Commercial and Internal Use xi

Node Message Change Failed ............................................................................................. 182

ARD-D00742 Airspan Commercial and Internal Use xii

PCI Update Status Change .................................................................................................. 196

ARD-D00742 Airspan Commercial and Internal Use xiii

RF2 Status Change (Server Detected) ................................................................................. 210

ARD-D00742 Airspan Commercial and Internal Use xiv

TWAMP Overload Status Changed ...................................................................................... 225

A Abbreviations .................................................................................. 229

ARD-D00742 Airspan Commercial and Internal Use xv

ARD-D00742 Airspan Commercial and Internal Use xvi

Rev 10.3 July 2018 Alarm Types

Rev 10.2 June 2018 Alarm Types

ARD-D00742 Airspan Commercial and Internal Use 1

Revision Details Date Summary of Changes

Rev 10.1 April 2018 Alarm Types

ARD-D00742 Airspan Commercial and Internal Use 2

Revision Details Date Summary of Changes

ARD-D00742 Airspan Commercial and Internal Use 3

Revision Details Date Summary of Changes

ARD-D00742 Airspan Commercial and Internal Use 4

Revision Details Date Summary of Changes

Rev 10.0 March 2018 Table 2. Alarm Severity Levels

ARD-D00742 Airspan Commercial and Internal Use 5

Revision Details Date Summary of Changes

ARD-D00742 Airspan Commercial and Internal Use 6

Netspan Related Alarm Changes

SR16.00/ o Server Event Queue Size High Updated alarm types

o A-GPS File Not Received

o eNodeB PDN Mismatch

o Access Point Connection Fault

ARD-D00742 Airspan Commercial and Internal Use 7

Revision Alarm Name Location Summary of

o GPS SNR Low Removed alarm types

o All MME Connectivity Lost (per

Netspan Related Event Changes

o A-GPS File Status Change

o PnP Identification Updated event types

ARD-D00742 Airspan Commercial and Internal Use 8

Revision Event Name Location Summary of

o Unsupported Clock Source