Ip Access Alarms

© ip.access Ltd

COMPANY CONFIDENTIAL CENG0097_XE_Alarm_Specification_SR1.5f.doc1

User Guide

ip.access Ltd CPC1 Capital Park Fulbourn Cambridge CB1 5XE United Kingdom

ip.access ALARM SPECIFICATION FOR THE nanoGSM BSS AT SYSTEM RELEASE 1.5f

CENG0097 Author(s) J Y Bromell 28 July 2004

© ip.access Ltd


The information contained in this document is commercially confidential and must

not be disclosed to third parties without prior consent.

© ip.access Ltd


1 Revision History Version Change Summary Date Author

XA First Draft 12 February 2003 jyb XB Minor updates. This version of CENG0097 was

autogenerated from alarmspec.xml rev 1.41 23 February 2004 jyb

XC Meaning and Action text added for GNAT alarms. This version of CENG0097 was autogenerated from

alarmspec.xml rev Revision: 1.44

1 March 2004 jyb

XD This version of CENG0097 was autogenerated from alarmspec.xml rev Revision: 1.45

3 March 2004 jyb

XE This version of CENG0097 was autogenerated from alarmspec.xml rev Revision: 1.51

1 July 2004 jyb

2 Document Approval

Author: John Bromell Signature: Date:

Approved By: Carl Melbourne Signature: Date:

© ip.access Ltd


3 Table of Contents 1 Revision History ............................................................................................................................. 3 2 Document Approval ....................................................................................................................... 3 3 Table of Contents ........................................................................................................................... 4 4 Introduction .................................................................................................................................... 7

4.1 Overview ................................................................................................................................... 7 4.2 Purpose and Scope .................................................................................................................. 7 4.3 Related Documents .................................................................................................................. 7

5 Alarm Specifications...................................................................................................................... 8 5.1 Software Fatal Error .................................................................................................................. 9 5.2 Software Warning.................................................................................................................... 10 5.3 Supply Voltage High ............................................................................................................... 11 5.4 Supply Voltage Low ................................................................................................................ 12 5.5 Internal Temperature High ...................................................................................................... 13 5.6 Internal Temperature Low....................................................................................................... 14 5.7 Input Current High................................................................................................................... 15 5.8 Input Current Low.................................................................................................................... 17 5.9 Input Power High..................................................................................................................... 18 5.10 Input Power Low.................................................................................................................. 19 5.11 RSL Failure.......................................................................................................................... 20 5.12 DHCP Rebinding ................................................................................................................. 21 5.13 DHCP Lease Expiry ............................................................................................................ 22 5.14 DHCP Renew NACK ........................................................................................................... 23 5.15 DHCP Rebind NACK........................................................................................................... 24 5.16 DHCP Address Declined ..................................................................................................... 25 5.17 NSVC Failure....................................................................................................................... 26 5.18 NSVC Reset Failure ............................................................................................................ 27 5.19 NSVC Unblock Failure ........................................................................................................ 28 5.20 NSVC Block Failure............................................................................................................. 29 5.21 Unknown NSVCI Received ................................................................................................. 30 5.22 Unknown NSEI Received .................................................................................................... 31 5.23 Attribute Value Not Supported............................................................................................. 32 5.24 Object Must Be Locked ....................................................................................................... 33 5.25 PTP BVC Failed .................................................................................................................. 34 5.26 Blocked by peer................................................................................................................... 35 5.27 TRX Boot Failed .................................................................................................................. 36 5.28 Transmitter Power Out of Lock............................................................................................ 37 5.29 Transmitter Phase Lock Loop Failure ................................................................................. 38 5.30 Hardware/Software Incompatibility...................................................................................... 39 5.31 Paging Commands Discarded............................................................................................. 40 5.32 UDP Packets Discarded...................................................................................................... 41 5.33 A-bis Connection Failure ..................................................................................................... 42 5.34 A-bis Connection Rejected.................................................................................................. 43 5.35 Unidentified Message Received.......................................................................................... 44 5.36 Message not expected ........................................................................................................ 45 5.37 Invalid Message Received .................................................................................................. 46 5.38 Unexpected Parameter in Message.................................................................................... 47 5.39 Mandatory Parameter Missing from Message. ................................................................... 48 5.40 Message Received for Invalid Object.................................................................................. 49 5.41 Invalid Parameter in Message............................................................................................. 50 5.42 Failed to Encode Message.................................................................................................. 51 5.43 Invalid Length Field in Message.......................................................................................... 52 5.44 Failed to Encode Encryption Enformation........................................................................... 53 5.45 Internal Message Processing Error ..................................................................................... 54

© ip.access Ltd


5.46 Protocol Handler Failed....................................................................................................... 55 5.47 Failed to Parse Message File.............................................................................................. 56 5.48 List Size Problem in Message............................................................................................. 57 5.49 Message Processing Error (IE format) ................................................................................ 58 5.50 Message Processing Error (IE tag) ..................................................................................... 59 5.51 Reset Procedure Failed....................................................................................................... 60 5.52 Failed to Decode BTS Identity............................................................................................. 61 5.53 Sub-agent Connection Failed.............................................................................................. 62 5.54 Internal Software Error ........................................................................................................ 63 5.55 Failed to Set Attributes ........................................................................................................ 64 5.56 Failed to Change Admin State ............................................................................................ 65 5.57 Failed to Opstart .................................................................................................................. 66 5.58 Failed to Activate Software.................................................................................................. 67 5.59 Failed to Reinitialize ............................................................................................................ 68 5.60 Management Request Failed .............................................................................................. 69 5.61 Failed to Remove BTS ........................................................................................................ 70 5.62 Failed to Remove TRX ........................................................................................................ 71 5.63 Adjacent Cell List Too Long ................................................................................................ 72 5.64 TRX Error Report................................................................................................................. 73 5.65 TRX Error Indication............................................................................................................ 74 5.66 BSC Restarted..................................................................................................................... 75 5.67 Failed to Write to Database................................................................................................. 76 5.68 Encryption Algorithm Not Supported................................................................................... 77 5.69 Management Connection Failed ......................................................................................... 78 5.70 PCM link failure ................................................................................................................... 79 5.71 Frame Relay link failure....................................................................................................... 80 5.72 NSVC failure (Frame Relay side) ........................................................................................ 81 5.73 NSVC failure (UDP side) ..................................................................................................... 82 5.74 Invalid PDU type received ................................................................................................... 83 5.75 Invalid API ID received ........................................................................................................ 84 5.76 Message not expected ........................................................................................................ 85 5.77 IE parse error....................................................................................................................... 86 5.78 Too many params in message............................................................................................ 87 5.79 TLLI does not exist .............................................................................................................. 88 5.80 Signalling BVC not provisioned........................................................................................... 89 5.81 NSEI unknown or not provisioned....................................................................................... 90 5.82 NSEI not operational ........................................................................................................... 91 5.83 BVCI unknown or not provisioned....................................................................................... 92 5.84 BVC blocked........................................................................................................................ 93 5.85 BVCI is invalid ..................................................................................................................... 94 5.86 NS reset in progress............................................................................................................ 95 5.87 BVC-BLOCK failure............................................................................................................. 96 5.88 BVC-UNBLOCK failure........................................................................................................ 97 5.89 BVC-RESET failure ............................................................................................................. 98 5.90 NSVCI unknown or not provisioned .................................................................................... 99 5.91 Socket connection failure .................................................................................................. 100 5.92 Management Connection Failed ....................................................................................... 101 5.93 GNAT core connection lost ............................................................................................... 102 5.94 NSVC Failure..................................................................................................................... 103 5.95 NSVC blocked ................................................................................................................... 104 5.96 Out of memory................................................................................................................... 105 5.97 Software warning............................................................................................................... 106 5.98 Software fatal error ............................................................................................................ 107 5.99 Object is not initialised....................................................................................................... 108 5.100 Config file missing ............................................................................................................. 109 5.101 Invalid config file format..................................................................................................... 110

© ip.access Ltd


5.102 Unable to open log file....................................................................................................... 111 5.103 Unable to write to log file ................................................................................................... 112 5.104 Error in config file............................................................................................................... 113 5.105 Failed to provision object................................................................................................... 114 5.106 Failed to unprovision object............................................................................................... 115 5.107 MTP3 Route failed............................................................................................................. 116 5.108 Management Connection Failed ....................................................................................... 117 5.109 Loss of Signal .................................................................................................................... 118 5.110 Loss of Framing................................................................................................................. 119 5.111 Remote Alarm Indication ................................................................................................... 120 5.112 Alarm Indication Signal...................................................................................................... 121 5.113 CRC errors ........................................................................................................................ 122 5.114 MTP2 Link failed................................................................................................................ 123 5.115 M2UA layer down .............................................................................................................. 124 5.116 SCTP association (connection) failed ............................................................................... 125 5.117 Sigtran stack configuration is invalid ................................................................................. 126 5.118 Database Integrity Check Failed ....................................................................................... 127 5.119 Wrong Attribute Type ........................................................................................................ 128 5.120 Wrong Attribute Type ........................................................................................................ 129 5.121 Invalid Attribute Value ....................................................................................................... 130 5.122 Missing Attribute ................................................................................................................ 131 5.123 Management Connection Failed ....................................................................................... 132

© ip.access Ltd


4 Introduction

4.1 Overview This document details the alarms that can be generated in the ip.access nanoGSM BSS at System Release 1.5f.

4.2 Purpose and Scope This is a customer facing document to assist customer engineers who need to know the details (including, for example, numerical values of probable cause type and value fields) in order to be able to program external management tools to interpret alarms received from nanoGSM equipment.

4.3 Related Documents ALARMSPEC.XML This is the source XML document from which this document was generated

(Revision: 1.51 )

© ip.access Ltd


5 Alarm Specifications Each alarm appears in the document as a separate 2nd level section, as follows

1.1 Software Fatal Error

1.1.1 Alarm Type ProcessingFailure

1.1.2 Alarm Source BTS

1.1.3 Alarm Token IPA_BTS_SW_FATAL_ERROR

1.1.4 Probable Cause Type 0x03

1.1.5 Probable Cause Value 0x0000

1.1.6 Bts Equipment Version 108_029 110_029

1.1.7 Permitted Severities critical

1.1.8 Meaning This alarm means that the nanoBTS software detected an internal error from which the only means of recovery was a reset. The nanoBTS may log the event before resetting, in which case it will attempt to send the alarm after the reset has completed, with an indication that this is a "logged" event (that is, an event that the nanoBTS logged but was not able to send at the time it occurred). If repeated after the reset, this alarm may indicate a configuration problem or a hardware problem. In some cases, there may be multiple, related, instances of this alarm, which when taken together provide a stack trace to help the development engineers diagnose the problem.

1.1.9 Actions Since the nanoBTS has reset itself, no repair action is required. Please report the occurrence of this alarm to your nanoGSM customer support provider.

the “Alarm name” – this text appears in the “Probable Cause” field in Alarm Manager

the “Alarm Type” – this text appears in the “Type” field in Alarm Manager

the “Alarm Source” is the type of equipment which generates the alarm.

the “Meaning” text describes the likely underlying cause or causes of the alarm condition

the “Action” text describes recommended actions to follow when this alarm is observed

the “Alarm Token” is the symbol by which this alarm is known internally by the nanoGSM software.

the “Probable Cause Type” combined with “Probable Cause Value” uniquely identifies the kind of alarm that has been raised.

the “Bts Equipment Version” identifies the type(s) of nanoBTS hardware on which this alarm can be raised.

the “Permitted Severities” identifies one or more severity levels at which this alarm may be raised.

© ip.access Ltd


5.1 Software Fatal Error



5.1.3 Alarm Token IPA_BTS_SW_FATAL_ERROR





5.1.8 Meaning This alarm means that the nanoBTS software detected an internal error from which the only means of recovery was a reset. The nanoBTS may log the event before resetting, in which case it will attempt to send the alarm after the reset has completed, with an indication that this is a "logged" event (that is, an event that the nanoBTS logged but was not able to send at the time it occurred). If repeated after the reset, this alarm may indicate a configuration problem or a hardware problem. In some cases, there may be multiple, related, instances of this alarm, which when taken together provide a stack trace to help the development engineers diagnose the problem.

5.1.9 Actions Since the nanoBTS has reset itself, no repair action is required. Please report the occurrence of this alarm to your nanoGSM customer support provider.

© ip.access Ltd


5.2 Software Warning



5.2.3 Alarm Token IPA_BTS_SW_WARNING




5.2.7 Permitted Severities warning

5.2.8 Meaning This alarm means that the nanoBTS software detected an error condition, but was able to continue operation. The Additional Text field contains information about the specific error condition detected. If repeated, this alarm may indicate a configuration problem or a hardware problem.

5.2.9 Actions Since the nanoBTS was able to continue operating, no repair action is required. Please report the occurrence of this alarm to your nanoGSM customer support provider.

© ip.access Ltd


5.3 Supply Voltage High

5.3.1 Alarm Type Environmental


5.3.3 Alarm Token IPA_BTS_SUPPLY_OVER_VOLTAGE




5.3.7 Permitted Severities warning cleared

5.3.8 Meaning This alarm means that the nanoBTS has detected that its input supply voltage has exceeded the upper alarm threshold for this measurement. The nanoBTS will clear this alarm when it detects that the input supply voltage has subsequently dropped below this threshold.

5.3.8.1 Possible Causes • The upper alarm threshold is set too low. • The power supply is faulty. • The nanoBTS is faulty.

5.3.9 Actions

5.3.9.1 Steps • Check that the upper alarm threshold for the input supply voltage is not set too low. The 100%

threshold corresponds to the maximum allowable input voltage. • Check the power supply and replace it if necessary. The maximum allowable input voltage at

the BTS, under load, is 57V.

© ip.access Ltd


5.4 Supply Voltage Low



5.4.3 Alarm Token IPA_BTS_SUPPLY_UNDER_VOLTAGE





5.4.8 Meaning This alarm means that the nanoBTS has detected that its input supply voltage has dropped below the lower alarm threshold for this measurement. The nanoBTS will clear this alarm when it detects that the input supply voltage has subsequently risen above this threshold.

5.4.8.1 Possible Causes • The threshold is set too high (0% corresponds to the minimum allowable input voltage). • There is excessive resistance in the Ethernet cabling. • The Ethernet cable is too long. • The power supply unit is faulty. • The nanoBTS is faulty.

5.4.9 Actions

5.4.9.1 Steps • Check that the lower alarm threshold for the input supply voltage is not set too high. • Check the power supply and replace it if necessary. • Check that the Ethernet cable is not too long. The cable should be a maximum of 100m for

power and data reasons, and typical overall dc resistance should be about 10 ohms per conductor. When using an ip.access PSU, the minimum expected input voltage at the BTS, under load, is 40V. Voltage must be measured at the BTS end, under load, to include the effects of cable resistance.

© ip.access Ltd


5.5 Internal Temperature High



5.5.3 Alarm Token IPA_BTS_INTERNAL_OVER_TEMPERATURE





5.5.8 Meaning This alarm means that the nanoBTS has detected that its internal temperature has exceeded the upper alarm threshold for this measurement. The nanoBTS will clear this alarm when it detects that the internal temperature has subsequently dropped below this threshold.

5.5.8.1 Possible Causes • The threshold is set too low. • The ambient temperature is too high. • The nanoBTS is faulty.

5.5.9 Actions

5.5.9.1 Steps • Check that the upper alarm threshold for the internal temperature is not set too low. • Check the physical location in which the nanoBTS is installed to ensure that the ambient air

temperature is not more than 45 degrees C: if it is, either take steps to reduce the ambient temperature or relocate the BTS. The best cooling occurs with the BTS mounted to a wall with its fins unobstructed and vertical, and with its plastic cover removed.

© ip.access Ltd


5.6 Internal Temperature Low



5.6.3 Alarm Token IPA_BTS_INTERNAL_UNDER_TEMPERATURE





5.6.8 Meaning This alarm means that the nanoBTS has detected that its internal temperature has dropped below the lower alarm threshold for this measurement. The nanoBTS will clear this alarm when it detects that the internal temperature has subsequently risen above this threshold.

5.6.8.1 Possible Causes • The threshold is set too high • The ambient temperature is too low. • The nanoBTS is faulty.

5.6.9 Actions

5.6.9.1 Steps • Check that the lower alarm threshold for the internal temperature is not set too high. • Check the physical location in which the nanoBTS is installed to ensure that the ambient air

temperature is not less than -5 degrees C: if it is, either take steps to increase the ambient temperature or relocate the BTS.

© ip.access Ltd


5.7 Input Current High



5.7.3 Alarm Token IPA_BTS_INTERNAL_OVER_CURRENT





5.7.8 Meaning This alarm means that the nanoBTS has detected that its input current has exceeded the upper alarm threshold for this measurement. The input current will rise as the input voltage falls, so this alarm may be accompanied by a Supply Voltage Low alarm. The nanoBTS will clear the Input Current High alarm when it detects that the input current has subsequently dropped below the threshold.

5.7.8.1 Possible Causes • The upper alarm threshold is set too low. • The Ethernet cable is too long, or there is excessive resistance in the cabling for some other

reason, and the input current has increased to compensate for the voltage drop. • The ambient temperature at the BTS is too low, and the OCXO heater is drawing excessive

current. In this case, the Input Current High alarm may be accompanied by an Internal Temperature Low alarm and/or an Input Power High alarm (depending on the relevant threshold settings).

• The power supply unit is faulty. • The nanoBTS is faulty.

5.7.9 Actions

5.7.9.1 Steps • Check that the upper alarm threshold for the input current is not set too low. The 0% threshold

corresponds to the minimum allowable input current, which is 100 mA. The 100% threshold corresponds to the maximum allowable input current, which is 350 mA.

© ip.access Ltd


• Check the physical location in which the nanoBTS is installed to ensure that the ambient air temperature is not less than -5 degrees C: if it is, either take steps to increase the ambient temperature or relocate the BTS.

• Check the power supply (eg. by substituting a known good one) and replace it if necessary. • Check that the Ethernet cable is not too long. The cable should be a maximum of 100m for

power and data reasons, and typical overall dc resistance should be about 10 ohms per conductor. When using an ip.access PSU, the minimum expected input voltage at the BTS, under load, is 40V. Voltage must be measured at the BTS end, under load, to include the effects of cable resistance.

• If none of the previous steps reveals the problem, replace the BTS with a spare unit.

© ip.access Ltd


5.8 Input Current Low



5.8.3 Alarm Token IPA_BTS_INTERNAL_UNDER_CURRENT





5.8.8 Meaning This alarm means that the nanoBTS has detected that its input current has dropped below the lower alarm threshold for this measurement. The nanoBTS will clear this alarm when it detects that the input current has subsequently risen above the threshold.

5.8.8.1 Possible Causes • The lower alarm threshold is set too high. • The power supply unit is faulty. • The nanoBTS is faulty. In the case of a transmitter power amplifier failure, the Input Current

Low alarm would be accompanied by a Transmitter Power Out of Lock alarm.

5.8.9 Actions

5.8.9.1 Steps • Check that the lower alarm threshold for the input current is not set too high. The 0% threshold

corresponds to the minimum allowable input current, which is 100 mA. The 100% threshold corresponds to the maximum allowable input current, which is 350 mA.

• Check the power supply (eg. by substituting a known good one) and replace it if necessary. • If none of the previous steps reveals the problem, replace the BTS with a spare.

© ip.access Ltd


5.9 Input Power High



5.9.3 Alarm Token IPA_BTS_INTERNAL_OVER_POWER





5.9.8 Meaning This alarm means that the nanoBTS has detected that its input power has exceeded the upper alarm threshold for this measurement. The nanoBTS will clear this alarm when it detects that the input power has subsequently dropped below the threshold.

5.9.8.1 Possible Causes • The upper alarm threshold is set too low. • The ambient temperature at the BTS is too low, and the OCXO heater is drawing excessive

current. In this case, the Input Current High alarm may be accompanied by an Internal Temperature Low alarm and/or an Input Current High alarm (depending on the relevant threshold settings).

• The nanoBTS is faulty.

5.9.9 Actions

5.9.9.1 Steps • Check that the upper alarm threshold for the input power is not set too low. The 0% threshold

corresponds to the minimum allowable input power, which is 4 W. The 100% threshold corresponds to the maximum allowable input power, which is 14 W.

• Check the physical location in which the nanoBTS is installed to ensure that the ambient air temperature is not less than -5 degrees C: if it is, either take steps to increase the ambient temperature or relocate the BTS.

• If none of the previous steps reveals the problem, replace the BTS with a spare unit.

© ip.access Ltd


5.10 Input Power Low



5.10.3 Alarm Token IPA_BTS_INTERNAL_UNDER_POWER





5.10.8 Meaning This alarm means that the nanoBTS has detected that its input power has dropped below the lower alarm threshold for this measurement. The nanoBTS will clear this alarm when it detects that the input power has subsequently risen above the threshold. If the input power drops too low, the BTS will stop functioning.

5.10.8.1 Possible Causes • The lower alarm threshold is set too high. • The power supply unit is faulty. • The nanoBTS is faulty. In the case of a transmitter power amplifier failure, the Input Power

Low alarm would be accompanied by a Transmitter Power Out of Lock alarm.

5.10.9 Actions

5.10.9.1 Steps • Check that the lower alarm threshold for the input power is not set too high. The 0% threshold

corresponds to the minimum allowable input power, which is 4 W. The 100% threshold corresponds to the maximum allowable input power, which is 14 W.

• Check the power supply (eg. by substituting a known good one) and replace it if necessary. • If none of the previous steps reveals the problem, replace the BTS with a spare.

© ip.access Ltd


5.11 RSL Failure

5.11.1 Alarm Type Communications


5.11.3 Alarm Token IPA_BTS_RSL_LINK_FAIL




5.11.7 Permitted Severities major cleared

5.11.8 Meaning This alarm will only be seen via the BSC's management interface if the RSL connection has failed but the primary OML connection to the nanoBTS is still alive. This is an unlikely situation, but possible causes include: a mis-configured firewall between the nanoBTS and the BSC; a network fault that happened to affect the RSL but not the OML. The alarm will clear when the network integrity is restored.

5.11.9 Actions Check any firewall configurations and the integrity of the network between the nanoBTS and the BSC.

© ip.access Ltd


5.12 DHCP Rebinding



5.12.3 Alarm Token IPA_BTS_DHCP_REBINDING


5.12.5 Probable Cause Value 0x030B



5.12.8 Meaning The nanoBTS has tried to renew its lease with the DHCP server that last issued it with an IP address, but is getting no reply. This could be due to an intentional change to the network configuration, or it could indicate a DHCP server failure. The alarm will clear if the nanoBTS succeeds in renewing its IP address before its lease actually expires.

5.12.9 Actions If an alternative DHCP server is available and configured to serve the nanoBTS, no action is required. Otherwise, first check that the original DHCP server is still running and configured to serve the nanoBTS: if not, restart it and/or reconfigure it as necessary. If this does not solve the problem, check the integrity of the LAN connection between the nanoBTS and the DHCP server.

© ip.access Ltd


5.13 DHCP Lease Expiry



5.13.3 Alarm Token IPA_BTS_DHCP_LEASE_EXPIRY


5.13.5 Probable Cause Value 0x030C



5.13.8 Meaning The nanoBTS has attempted to renew its lease with a DHCP server, but was not been able to do so before the lease expired. It no longer has a valid IP address, cannot provide service, and will reboot shortly after raising this alarm. Possible causes include: DHCP server has stopped or failed; a fault on the network between the DHCP server and the nanoBTS reporting the alarm.

5.13.9 Actions Check that the DHCP server is still running and is configured to serve the nanoBTS: if not, restart it and or reconfigure it as necessary. If this does not solve the problem, check the integrity of the LAN connection between the nanoBTS and the DHCP server.

© ip.access Ltd


5.14 DHCP Renew NACK



5.14.3 Alarm Token IPA_BTS_DHCP_RENEW_NACK


5.14.5 Probable Cause Value 0x030D



5.14.8 Meaning The nanoBTS has attempted to renew its lease with the DHCP server that leased it its current IP address, but as far as the server is concerned the IP address is no longer valid. The nanoBTS therefore can no longer provide service, and will reboot shortly.

5.14.8.1 Possible Causes • The DHCP server has been reconfigured with a different subnet address from that of the

nanoBTS. • The DHCP server is not behaving in accordance with RFC2131.

5.14.9 Actions If a deliberate change of subnet address has been made, no action is required, as the nanoBTS will reset and acquire a new IP address. Otherwise, check the configuration and operation of the DHCP server.

© ip.access Ltd


5.15 DHCP Rebind NACK



5.15.3 Alarm Token IPA_BTS_DHCP_REBIND_NACK


5.15.5 Probable Cause Value 0x030E



5.15.8 Meaning The nanoBTS has attempted to renew its lease, but had no answer from the DHCP server that issued the lease; it has therefore now broadcast its DHCPREQUEST and a server (possibly the original one) has refused to renew the lease. The nanoBTS therefore no longer has a valid IP address, cannot provide service, and will reboot shortly after raising this alarm.

5.15.8.1 Possible Causes • The original DHCP server has been taken down, has failed, or was temporarily unavailable,

and the currently available DHCP server(s) have been reconfigured with a different subnet address from that of the nanoBTS.

• The DHCP server(s) are not behaving in accordance with RFC2131.

5.15.9 Actions If a deliberate change of subnet address has been made, no action is required, as the nanoBTS will reset and acquire a new IP address. Otherwise, check the configuration and operation of the DHCP server(s).

© ip.access Ltd


5.16 DHCP Address Declined



5.16.3 Alarm Token IPA_BTS_DHCP_ADDR_DECLINED


5.16.5 Probable Cause Value 0x030F



5.16.8 Meaning The nanoBTS has discovered (eg. using ARP) that another device is already using the IP address that a DHCP server has suggested that it use. The nanoBTS cannot continue using that address and will therefore reset and restart the process of acquiring an IP address.

5.16.8.1 Possible Causes • There is more than one DHCP server on the network, and as a result of a race condition,

another device has legitimately been allocated the IP address in question, just before the nanoBTS was given it.

• There is a DHCP configuration problem in the network (eg. the DHCP server(s) have been configured to allocate the same IP address to more than one device.

5.16.9 Actions If this alarm occurs repeatedly, check the DHCP configuration in the network.

© ip.access Ltd


5.17 NSVC Failure



5.17.3 Alarm Token IPA_BTS_GPRS_NSVC_DEAD




5.17.7 Permitted Severities critical cleared

5.17.8 Meaning This alarm means the BTS has detected that one of its NSVCs is no longer responding to messages from the BTS. This may be due to a physical link problem (cabling), a mismatch in configuration between the BTS, FR-IP Converter and SGSN or a hardware problem in one of these items.

5.17.9 Actions

5.17.9.1 Steps • Check for consistency between the following sets of configuration: 1) NSEI and NSVC(s) at

the BTS, 2) BTS, SGSN and FR configuration at the FR-IP Converter (ip_fr_route_table, ip_fr_config, fr_config), 3) NSEI, NSVC(s) and FR configuration at the SGSN. In particular check that the IP addresses, NSVCIs and DLCIs all match. Once the correct configuration is present and assuming the BTS, FR-IP and SGSN are running, the NSVC should automatically recover.

• If the NSVC does not recover after checking configuration then confirm that the physical connections are present. Check for green lights on the T1/E1 sockets of the FR-IP Converter that are connected to the SGSN. If a socket has a red light this most likely indicates a cabling problem. If a socket has an orange light this most likely indicates a T1/E1 configuration problem. Check for a green light on the Ethernet socket of the FR-IP Converter and check the cabling and routing configuration between the FR-IP Converter and the BTS.

• If the problem persists, further investigation using E1/T1/Frame Relay and Ethernet/IP test equipment will be required in order to observe Gb messaging between the BTS, FR-IP Converter and SGSN.

© ip.access Ltd


5.18 NSVC Reset Failure



5.18.3 Alarm Token IPA_BTS_GPRS_NSVC_RESET_FAILED





5.18.8 Meaning This alarm means the BTS has detected that an attempt to reset one of its NSVCs failed because the BTS did not receive a valid response from the SGSN. This may be due to a physical link problem (cabling), a mismatch in configuration between the BTS, FR-IP Converter and SGSN or a hardware problem in one of these items.

5.18.9 Actions





© ip.access Ltd


5.19 NSVC Unblock Failure



5.19.3 Alarm Token IPA_BTS_GPRS_NSVC_UNBLOCK_FAILED





5.19.8 Meaning This alarm means the BTS has detected that an attempt to unblock one of its NSVCs failed because the BTS did not receive a valid response from the SGSN. This may be due to a physical link problem (cabling), a mismatch in configuration between the BTS, FR-IP Converter and SGSN or a hardware problem in one of these items.

5.19.9 Actions





© ip.access Ltd


5.20 NSVC Block Failure



5.20.3 Alarm Token IPA_BTS_GPRS_NSVC_BLOCK_FAILED




5.20.7 Permitted Severities minor cleared

5.20.8 Meaning This alarm means the BTS has detected that an attempt to block one of its NSVCs failed because the BTS did not receive a valid response from the SGSN. This may be due to a physical link problem (cabling), a mismatch in configuration between the BTS, FR-IP Converter and SGSN or a hardware problem in one of these items.

5.20.9 Actions





© ip.access Ltd


5.21 Unknown NSVCI Received



5.21.3 Alarm Token IPA_BTS_GPRS_BAD_NSVCI





5.21.8 Meaning This alarm means the BTS has received a message containing an unrecognised NSVCI.

5.21.9 Actions


the BTS, 2) BTS, SGSN and FR configuration at the FR-IP Converter (ip_fr_route_table, ip_fr_config, fr_config), 3) NSEI, NSVC(s) and FR configuration at the SGSN. In particular check that the IP addresses, NSVCIs and DLCIs all match. Once the correct configuration is present and assuming the BTS, FR-IP and SGSN are running, the NSVC(s) should automatically recover and the alarm should not re-occur.


© ip.access Ltd


5.22 Unknown NSEI Received



5.22.3 Alarm Token IPA_BTS_GPRS_BAD_NSEI





5.22.8 Meaning This alarm means the BTS has received a message containing an unrecognised NSEI.

5.22.9 Actions


the BTS, 2) BTS, SGSN and FR configuration at the FR-IP Converter (ip_fr_route_table, ip_fr_config, fr_config), 3) NSEI, NSVC(s) and FR configuration at the SGSN. In particular check that the IP addresses, NSVCIs and DLCIs all match. Once the correct configuration is present and assuming the BTS, FR-IP and SGSN are running, the NSVC(s) should automatically recover and the alarm should not re-occur.


© ip.access Ltd


5.23 Attribute Value Not Supported



5.23.3 Alarm Token IPA_BTS_ATTRIBUTE_VALUE_NOT_SUPPORTED_1




5.23.7 Permitted Severities major

5.23.8 Meaning This alarm means that an attempt to change the value of an attribute was denied as the new value is not supported. The new value has not been applied and any previously configured value is still in use. The new value has however been commited to the BSC Database, and must be corrected before the BTS next restarts, or the BTS will not restart until it is fixed.

5.23.9 Actions The value must be changed to a value supported for this attribute.

© ip.access Ltd


5.24 Object Must Be Locked



5.24.3 Alarm Token IPA_BTS_OBJECT_MUST_BE_LOCKED_1





5.24.8 Meaning This alarm means that a procedure could not be performed on a managed object as the object must be locked to perform it. The new value has however been commited to the BSC Database, and will be applied when the BTS next restarts.

5.24.9 Actions The object should be locked and the procedure reattempted.

© ip.access Ltd


5.25 PTP BVC Failed



5.25.3 Alarm Token IPA_BTS_GPRS_PTP_BVC_FAILED


5.25.5 Probable Cause Value 0x031A



5.25.8 Meaning The SGSN has failed to respond to BVC-FLOW-CONTROL messages after a BVC_RESET. If the NS layer is up when this alarm is raised, the only known cause is a software defect in the SGSN. It is also just possible that this alarm could be seen if the Gb link failed after the nanoBTS had sent a BVC-FLOW-CONTROL message, and before the SGSN had responded, but in this case there would also be a "NSVC Failed" alarm, and the GPRS NSVC object would be disabled. When this alarm is set the BTS will periodically test the BVC to see if it is fixed. The alarm will clear after the successul completion of the BVC-RESET, BVC-UNBLOCK and BVC-FLOW-CONTROL procedures.

5.25.9 Actions

5.25.9.1 Steps • Check that the NS layer is still up (GPRS NSVC object enabled. If it is, check that the SGSN

responds correctly to BVC-FLOW-CONTROL messages: if it doesn't, investigate and correct the SGSN software.

• If the Gb link is down (GPRS NSVC object disabled), restore it. • If the Gb link is up and the SGSN is responding correctly to BVC-FLOW-CONTROL

messages, please report the problem to your nanoGSM customer support provider.

© ip.access Ltd


5.26 Blocked by peer



5.26.3 Alarm Token IPA_BTS_GPRS_NSVC_BLOCKED_BY_PEER





5.26.8 Meaning This alarm means that the BTS has received a NS-BLOCK message from the peer Gb entity (SGSN or ip.access GNAT if used). The NSVC is no longer available to provide GPRS service.

5.26.9 Actions

5.26.9.1 Steps • This is most likely to be due to an intentional management operation at the SGSN or GNAT

requiring no action. • Verify correct NSVC configuration at the BTS, GNAT (if present), FRIP (if present) and SGSN. • May be the result of loss of NSVC group between SGSN and GNAT - if so all BTSs will

produce this alarm, and investigation of the Gb link to the SGSN should be made.

© ip.access Ltd


5.27 TRX Boot Failed



5.27.3 Alarm Token IPA_BTS_TRX_BOOT_FAILURE





5.27.8 Meaning This alarm means that one of the processors in the TRX portion of the nanoBTS hardware could not be booted properly. The unit should still be able to carry out management operations (such as software download, for example) that do not involve the TRX hardware.

5.27.9 Actions Please report this alarm to your nanoGSM customer support provider. If this alarm occurs repeatedly, replace the nanoBTS unit with a spare one.

© ip.access Ltd


5.28 Transmitter Power Out of Lock



5.28.3 Alarm Token IPA_BTS_TX_PA_FAILURE





5.28.8 Meaning This alarm means that the nanoBTS's power amplifier is unable to generate the power level required. This could either be because the amplifier has got too hot and cannot provide the required gain, or because a hardware component has failed.

5.28.9 Actions If immediate restoration of service is required, replace the nanoBTS unit with a spare one. Otherwise, clear the alarm, power the unit down, leave it to cool down for at least one hour, then power it up again. If when the transmitter turns on, the same alarm occurs straight away, a hardware fault is indicated, in which case, replace the unit with a spare one and report the problem to your nanoGSM customer support provider. If when the transmitter turns on, the alarm does not recur, it is likely that the unit had previously become too hot: ensure that there is adequate ventilation where the unit is installed, and if the unit's plastic cover is still in place, remove it to aid cooling.

© ip.access Ltd


5.29 Transmitter Phase Lock Loop Failure



5.29.3 Alarm Token IPA_BTS_TX_OPLL_FAILURE





5.29.8 Meaning This alarm means that the unit's phase-lock loop has either failed to acquire, or has lost, lock and cannot reacquire the required frequency, and therefore cannot transmit. This could be due to a temporary external influence, or it could be due to an internal hardware fault.

5.29.9 Actions Reset the nanoBTS. If it starts up and transmits successfully, no further action is required. Otherwise, replace the nanoBTS unit with a spare one, and report the problem to your nanoGSM customer support provider.

© ip.access Ltd


5.30 Hardware/Software Incompatibility



5.30.3 Alarm Token IPA_BTS_HW_SW_COMPATIBILITY_FAIL





5.30.8 Meaning The version of software that is currently running is not compatible with the hardware it is running on. The nanoBTS should not accept downloads of sofware which is incompatible with the hardware version, so possible causes are: incompatible software version installed in the factory; internal fault in nanoBTS.

5.30.9 Actions Please contact your nanoGSM customer support provider.

© ip.access Ltd


5.31 Paging Commands Discarded

5.31.1 Alarm Type QualityOfService


5.31.3 Alarm Token IPA_BTS_PAGING_DISCARD





5.31.8 Meaning The nanoBTS has discarded 08.58 Paging Commands due to resource limitations.

5.31.9 Actions Reduce the paging load on the nanoBTS by adjusting the GSM network configuration in one or more of the following ways: reduce the number of paging repeats; reduce the number of AGCH reserved blocks; change the channel combination to Full BCCH; reduce the size of the location area.

© ip.access Ltd


5.32 UDP Packets Discarded

5.32.1 Alarm Type QualityOfService


5.32.3 Alarm Token IPA_BTS_UDP_OVERFLOW





5.32.8 Meaning The nanoBTS has discarded downlink UDP packets due to resource limitations.

5.32.9 Actions Please report the full details of the alarm, including any information in the Additional Text field, to your nanoGSM customer support provider.

© ip.access Ltd


5.33 A-bis Connection Failure


5.33.2 Alarm Source BSC

5.33.3 Alarm Token IPA_BSC_CONNECTION_FAILED




5.33.7 Meaning The BSC has detected that the connection to the nanoBTS has been lost. This alarm will be raised against both the site manager object and the baseband transceiver objects at about the same time if the cause is disconnection of the nanoBTS from the network, the nanoBTS resetting, or the nanoBTS being powered down. Other causes can result in the alarm being raised on either or both of these managed objects.

5.33.7.1 Possible Causes • Disconnection of the nanoBTS from the network. • The nanoBTS has reset itself or has been reinitialised by management action. • The nanoBTS has been powered down. • In a multi-homed BSC, the nanoBTS-side network interface is faulty. • There is a firewall configuration problem. • There is, or has been, a network fault that is preventing communication on the connection.

5.33.8 Actions

5.33.8.1 Steps • If all nanoBTSs connected to a multi-homed BSC are showing this alarm, check the

connection from the BSC to the nanoBTS subnetwork. • Check the integrity of the network between the nanoBTS and the BSC. • If there is a firewall between the BSC and the nanoBTS, check its configuration.

© ip.access Ltd


5.34 A-bis Connection Rejected



5.34.3 Alarm Token IPA_BSC_CONNECTION_REJECTED




5.34.7 Meaning An unexpected nanoBTS has attempted make an OML or RSL connection to the BSC. The BSC does not recognise the (relevant part of) the nanoBTS's unit id. If the problem is associated with an OML connection, the alarm will be raised against the site manager object and the site id of the unit trying to connect is given in the alarm's additional text field. If the problem is associated with an RSL connection, the alarm will be raised against the baseband transceiver object and the full unit id (site/bts/trx) is given in the alarm's additional text field. In both cases, the IP address of the unit trying to connect is also given.

5.34.7.1 Possible Causes • While adding a nanoBTS to the network, it has been connected before its home BSC has

been configured to accept it. • While adding a nanoBTS to the network, its home BSC has been configured with the wrong

unit id. • A nanoBTS that is being added to the network has the wrong unit id. • A nanoBTS has been given the wrong primary OML IP address, and has therefore tried to

connect to the wrong BSC. • A nanoBTS that has been deleted from its home BSC has been re-connected to the network.

5.34.8 Actions

5.34.8.1 Steps • Check that the source BSC has been configured with all of the correct unit ids for the

nanoBTSs that should be connecting to it. • Check that all nanoBTSs that are configured with the source BSC's IP address as their

primary OML IP address have the correct unit ids. • Check that all nanoBTSs that have an IP route to the source BSC also have the correct

primary OML IP addresses.

© ip.access Ltd


5.35 Unidentified Message Received



5.35.3 Alarm Token IPA_BSC_MSG_UNKNOWN




5.35.7 Meaning The BSC received a message that it could not identify.

5.35.7.1 Possible Causes • There is a mismatch between the two sides of one of the BSC's interfaces (both sides comply

with valid, but different, specifications). • There is a bug in the equipment that sent the message. • There was a transmission error that was not detected or corrected by the communications link.


© ip.access Ltd


5.36 Message not expected



5.36.3 Alarm Token IPA_BSC_MSG_NOT_EXPECTED




5.36.7 Meaning The BSC understood a message that it received, but was not in a state in which it expected to receive it, and so ignored it. Examples: receipt of an ACK for a message that had not been sent; receipt of a SCCP Release Complete message after the connection had been closed.


© ip.access Ltd


5.37 Invalid Message Received



5.37.3 Alarm Token IPA_BSC_MSG_INVALID




5.37.7 Meaning The BSC received a message that it considered did not conform to the relevant interface specification. The BSC will not have acted on this message.


© ip.access Ltd


5.38 Unexpected Parameter in Message



5.38.3 Alarm Token IPA_BSC_MSG_PARAM_UNKNOWN



5.38.6 Permitted Severities minor

5.38.7 Meaning The BSC received a message that it considered did not conform to the relevant interface specification, because it contained an attribute that it either didn't recognise or was not expected in a message of this type. The BSC will have acted on the rest of the message.


© ip.access Ltd


5.39 Mandatory Parameter Missing from Message.



5.39.3 Alarm Token IPA_BSC_MSG_PARAM_MANDATORY_MISSING




5.39.7 Meaning The BSC received a message that it considered did not conform to the relevant interface specification, because a mandatory parameter was missing. The BSC will not have acted on this message.


© ip.access Ltd


5.40 Message Received for Invalid Object



5.40.3 Alarm Token IPA_BSC_MSG_PARAM_MANDATORY_ERROR




5.40.7 Meaning The BSC received a GSM 12.21 message for an object that it could not identify or was incorrect for the operation being performed. The BSC will not have acted on this message.


© ip.access Ltd


5.41 Invalid Parameter in Message



5.41.3 Alarm Token IPA_BSC_MSG_PARAM_INVALID




5.41.7 Meaning The BSC received a message that it considered did not conform to the relevant interface specification because it contained an information element with invalid contents (for example, nonsensical encryption information). The BSC may not have acted on the message.


© ip.access Ltd


5.42 Failed to Encode Message



5.42.3 Alarm Token IPA_BSC_MSG_PARAM_ERROR




5.42.7 Meaning The BSC has encountered an error when encoding a message (for example, an invalid combination of information elements or values).


© ip.access Ltd


5.43 Invalid Length Field in Message



5.43.3 Alarm Token IPA_BSC_MSG_LENGTH_ERROR




5.43.7 Meaning The BSC received a message that it considered did not conform to the relevant interface specification because either the message length field or an information element length field was invalid. The BSC may not have acted on the message.


© ip.access Ltd


5.44 Failed to Encode Encryption Enformation



5.44.3 Alarm Token IPA_BSC_MSG_ENCODING_ERROR




5.44.7 Meaning The BSC has encountered an error when encoding a message due to an invalid combination of information elements or values related to encryption information.


© ip.access Ltd


5.45 Internal Message Processing Error



5.45.3 Alarm Token IPA_BSC_MSG_ILLEGAL_ACCESS_ERROR




5.45.7 Meaning An internal software error occurred while the BSC was processing a received message. The processing may have partially completed or the message may have been discarded.


© ip.access Ltd


5.46 Protocol Handler Failed



5.46.3 Alarm Token IPA_BSC_MSG_UNRECOVERABLE_ERROR




5.46.7 Meaning An internal software error occurred which prevented the BSC from processing a message. The message will have been discarded. It is unlikely that the BSC will be able to handle any further messages belonging to the same protocol. If this alarm occurs at all it is likely that many alarms of this type may be seen in rapid succession.

5.46.8 Actions Restart the BSC, and report the problem to your nanoGSM customer support provider.

© ip.access Ltd


5.47 Failed to Parse Message File



5.47.3 Alarm Token IPA_BSC_MSG_XML_PARSE_ERROR




5.47.7 Meaning The BSC could not parse one of the XML files that defines protocol messages. This could be due to a file being missing or corrupted.

5.47.8 Actions Reinstall the BSC.

© ip.access Ltd


5.48 List Size Problem in Message



5.48.3 Alarm Token IPA_BSC_MSG_INDEX_ERROR




5.48.7 Meaning The BSC received a message that it considered did not conform to the relevant interface specification, because an information element containing a list of values contained the wrong number of values. The BSC will have acted on the values that it was able to access.


© ip.access Ltd


5.49 Message Processing Error (IE format)



5.49.3 Alarm Token IPA_BSC_MSG_IE_FORMAT_ERROR




5.49.7 Meaning An internal software error occurred while the BSC was encoding or decoding a message. The processing may have partially completed or the message may have been discarded.


© ip.access Ltd


5.50 Message Processing Error (IE tag)



5.50.3 Alarm Token IPA_BSC_MSG_IE_TAG_ERROR




5.50.7 Meaning An internal software error occurred while the BSC was encoding or decoding a message. The processing may have partially completed or the message may have been discarded.


© ip.access Ltd


5.51 Reset Procedure Failed



5.51.3 Alarm Token IPA_BSC_RESET_PROCEDURE_FAILED_1




5.51.7 Meaning The MSC did not respond to the BSC's 08.08 RESET message, even after repeated attempts.

5.51.7.1 Possible Causes • A fault at the MSC. • A-interface communications failure.

5.51.8 Actions

5.51.8.1 Steps • Check that the MSC is running properly and correct any problem found. • Check A-interface communications links and correct any problem found.

© ip.access Ltd


5.52 Failed to Decode BTS Identity



5.52.3 Alarm Token IPA_BSC_INVALID_UNIT_ID_1




5.52.7 Meaning The BSC could not decode an Identity message from a nanoBTS.

5.52.7.1 Possible Causes • Software error in the BSC or in the nanoBTS.


© ip.access Ltd


5.53 Sub-agent Connection Failed



5.53.3 Alarm Token IPA_BSC_SUBAGENT_CONNECTION_FAILED




5.53.7 Meaning The BSC has lost its connection to the management sub-agent for the managed object raising the alarm. Since the sub-agent process runs on the BSC's Main CPU card, this is almost certainly due to the sub-agent process having terminated abnormally. The sub-agent process should restart automatically, and when the connection is re-established, the alarm will be cleared.

5.53.8 Actions Report this alarm to your nanoGSM customer support provider, including relevant log files. If this alarm occurs continuously, investigate the log files for further information.

© ip.access Ltd


5.54 Internal Software Error



5.54.3 Alarm Token IPA_BSC_INT_SW




5.54.7 Meaning The BSC has detected an internal software error.


© ip.access Ltd


5.55 Failed to Set Attributes



5.55.3 Alarm Token IPA_BSC_SET_ATTRIBUTES_FAILURE




5.55.7 Meaning The BSC attempted to set attribute values on a nanoBTS but could not do so.

5.55.7.1 Possible Causes • Incorrect configuration. • A-bis interface communications problem. • An internal software error in either the BSC or the nanoBTS.


© ip.access Ltd


5.56 Failed to Change Admin State



5.56.3 Alarm Token IPA_BSC_CHANGE_ADMIN_STATE_FAILURE




5.56.7 Meaning The BSC attempted to change the administrative state of a managed object on a nanoBTS but could not do so.

5.56.7.1 Possible Causes • A-bis interface communications problem. • An internal software error in either the BSC or the nanoBTS.


© ip.access Ltd


5.57 Failed to Opstart



5.57.3 Alarm Token IPA_BSC_OPSTART_FAILURE




5.57.7 Meaning The BSC attempted to OPSTART a managed object on a nanoBTS but could not do so.

5.57.7.1 Possible Causes • Incorrect configuration. • A-bis interface communications problem. • An internal software error in either the BSC or the nanoBTS.


© ip.access Ltd


5.58 Failed to Activate Software



5.58.3 Alarm Token IPA_BSC_ACTIVATE_SW_FAILURE




5.58.7 Meaning The BSC attempted to software activate a managed object on a nanoBTS but could not do so.



© ip.access Ltd


5.59 Failed to Reinitialize



5.59.3 Alarm Token IPA_BSC_REINITIALIZE_FAILURE




5.59.7 Meaning The BSC attempted to reinitialise a managed object on a nanoBTS but could not do so.



© ip.access Ltd


5.60 Management Request Failed



5.60.3 Alarm Token IPA_BSC_MGNT_REQUEST_FAILURE




5.60.7 Meaning The BSC has sent a 12.21 management request for which either no response has been received or a response has been received indicating that the request cannot be carried out.


© ip.access Ltd


5.61 Failed to Remove BTS



5.61.3 Alarm Token IPA_BSC_REMOVE_BTS_FAILURE




5.61.7 Meaning A user has attempted to deprovision a nanoBTS from a BSC, and the BSC has failed to close the connections to the nanoBTS.

5.61.7.1 Possible Causes • A software error in the BSC.

5.61.8 Actions Try again, and if the problem recurs, report it to your nanoGSM customer support provider.

© ip.access Ltd


5.62 Failed to Remove TRX



5.62.3 Alarm Token IPA_BSC_REMOVE_TRX_FAILURE




5.62.7 Meaning A user has attempted to deprovision a nanoBTS from a BSC, and the BSC has failed to close the connections to the nanoBTS.

5.62.8 Actions Try again, and if the problem recurs, report it to your nanoGSM customer support provider.

© ip.access Ltd


5.63 Adjacent Cell List Too Long



5.63.3 Alarm Token IPA_BSC_CONFIG_INCONSISTENT




5.63.7 Meaning The BSC needs to send SYSTEM INFORMATION 2 or 5 to a nanoBTS and there are too many ARFCNs defined for the adjacent cell for reselection list or the adjacent cell for handover list.

5.63.7.1 Possible Causes • User error. • Software error in the BSC.

5.63.8 Actions Remove one or more ARFCNs from the relevant adjacent cell list.

© ip.access Ltd


5.64 TRX Error Report



5.64.3 Alarm Token IPA_BSC_TRX_ERROR_REPORT




5.64.7 Meaning The BSC has received an 08.58 ERROR REPORT message, with a cause value other than encryption algorithm not implemented. The cause value reported by the nanoBTS is included in the alarm's Additional Text field.

5.64.7.1 Possible Causes • See 3GPP TS 08.58 V8.6.0, section 9.3.26.

5.64.8 Actions Dependent on cause value.

© ip.access Ltd


5.65 TRX Error Indication



5.65.3 Alarm Token IPA_BSC_TRX_ERROR_INDICATION




5.65.7 Meaning The BSC has received an 08.58 ERROR INDICATION message, which indicates that the nanoBTS has detected an error on a radio link layer connection to a mobile station. The RLM Cause value reported by the nanoBTS is included in the alarm's Additional Text field.

5.65.7.1 Possible Causes • See 3GPP TS 08.58 V8.6.0, section 9.3.22.

5.65.8 Actions Dependent on cause value.

© ip.access Ltd


5.66 BSC Restarted



5.66.3 Alarm Token IPA_BSC_RESTARTED




5.66.7 Meaning The BSC has just restarted. The alarm's additional text field gives the reason for the reset, which will be one of the following: "BSC starting for the first time"; "Manual BSC reset"; "Internal BSC reset"; "Unknown BSC reset". Each of these is described below.

5.66.7.1 Possible Causes • If the additional text is "BSC starting for the first time", the alarm identifies a brand new

installation starting for the first time. • If the additional text is "Manual BSC reset", the alarm means that the BSC was

stopped/started normally using the config-bsc tool. • If the additional text is "Internal BSC reset", the alarm means that the BSC explicitly aborted

due to an internal fault discovered by the BSC runtime (for example, an assertion violation or thread heartbeat timeout).

• If the additional text is "Unknown BSC reset", the alarm means that the BSC aborted due to some event not known by the BSC runtime. For example the BSC might have core-dumped and/or was explicity terminated by receipt of a terminating signal (e.g SIGSEGV).

5.66.8 Actions If this was an Internal BSC reset or an Unknown BSC reset, please report it to your nanoGSM customer support provider, including relevant error and trace files from the BSC. If this alarm is received continuously, investigate the error log files on the BSC platform for further information.

© ip.access Ltd


5.67 Failed to Write to Database

5.67.1 Alarm Type Equipment


5.67.3 Alarm Token IPA_BSC_DB_ACCESS




5.67.7 Meaning The BSC has attempted to write details of an alarm or state change event into its database and could not do so.

5.67.7.1 Possible Causes • The BSC's database daemon has crashed and could not be restarted. • The disk or partition used for the BSC's database is full.

5.67.8 Actions

5.67.8.1 Steps • Check that the BSC's MySQL daemon is running properly. If not, attempt to restart it. • Check that the BSC's MySQL daemon is running properly.

© ip.access Ltd


5.68 Encryption Algorithm Not Supported

5.68.1 Alarm Type Equipment


5.68.3 Alarm Token IPA_BSC_REQUESTED_ENCRYPT_ALG_NOT_SUPPORTED




5.68.7 Meaning The BSC has received an 08.58 ERROR REPORT message, with a Cause value meaning "encryption algorithm not implemented".

5.68.7.1 Possible Causes • The MSC has been configured incorrectly for this cell. • The wrong software has been installed on the nanoBTS.

5.68.8 Actions Determine whether or not this cell is required to support the encryption algorithm requested. If so, upgrade the nanoBTS software (availability permitting) with a version that supports it. If not, change the MSC configuration so that it does not request it for this cell.

© ip.access Ltd


5.69 Management Connection Failed


5.69.2 Alarm Source FRIP

5.69.3 Alarm Token IPA_FRIP_LOSS_OF_COMMUNICATIONS




5.69.7 Meaning This alarm is generated by the FRIP management agent if it has lost communication with the FRIP. The alarm will clear when the FRIP management agent re-establishes comms with the FRIP.

5.69.7.1 Possible Causes • The FRIP application has stopped.

5.69.8 Actions Check the the FRIP application is still running using the command ps -ax | grep FRIP.

© ip.access Ltd


5.70 PCM link failure



5.70.3 Alarm Token IPA_FRIP_PCM_LINK_FAILURE




5.70.7 Meaning This alarm is generated by the FRIP if a PCM link goes down. The alarm will clear when the PCM link recovers.

5.70.7.1 Possible Causes • The PCM link is not connected. • The PCM link cabling is incorrectly wired. • The PCM link type (T1/E1) does not match the other end of the link. • The line coding does not match the other end of the link. • The framing does not match the other end of the link. • Both ends of the link are configured as timing slave. • For T1 links, the linedrive may be incorrect.

5.70.8 Actions

5.70.8.1 Steps • Check the PCM link is connected. • Check the green link light on the FRIP. If this is not showing then check the cabling between

the FRIP and the SGSN. • Check the configuration at both ends of the link. Link type, line coding, and framing should all

match. • Check the timing configuration. Confirm that both ends are not timing slaves. Ideally one end

of the link should generate timing and the other end of the link should recover timing. • For T1 links check that the linedrive is set to a value corresponding to the length of the PCM

link cabling. • If the problem remains, report the problem to your nanoGSM customer support provider.

© ip.access Ltd


5.71 Frame Relay link failure



5.71.3 Alarm Token IPA_FRIP_FR_LINK_FAILURE




5.71.7 Meaning This alarm is generated by the FRIP if a Frame Relay link goes down. The alarm will clear when the Frame Relay link recovers.

5.71.7.1 Possible Causes • The underlying PCM link has failed. • The role (HOST/NETWORK) does not correspond with the opposite value at the other end of

the link. • The timeslots configured for the Frame Relay link do not correspond with the values at the

other end of the link. • The LMI type for the Frame Relay link does not correspond with the LMI type at the other end

of the link.

5.71.8 Actions

5.71.8.1 Steps • If all Frame Relay links running on the same PCM link have failed then check the PCM link as

described in the IPA_FRIP_PCM_LINK_FAILURE alarm. • Check the role configured for the Frame Relay link. Typically the FRIP will be the HOST and

the SGSN will be the NETWORK. • Check the timeslot configuration at both ends of the link. This must match exactly! • Check the LMI type configuration at both ends of the link. The LMI type does not follow

automatically from the PCM link type; an E1 link can have ANSI LMI, similarly a T1 link can have ITU LMI. If the LMI type for the other end of the link cannot be determined, try changing the LMI type at the FRIP to see if this fixes the problem.

• If the problem remains, run the fr_status program. View the Frame Relay link that has failed. Report the problem and the information from the fr_status program to your nanoGSM customer support provider.

© ip.access Ltd


5.72 NSVC failure (Frame Relay side)



5.72.3 Alarm Token IPA_FRIP_NSVC_FR_FAILURE




5.72.7 Meaning This alarm is generated by the FRIP if there are no frames received from the SGSN on this NSVC. The alarm will clear when frames are received from the SGSN.

5.72.7.1 Possible Causes • The underlying Frame Relay link has failed. • DLCI mismatch between the SGSN and the FRIP. • The NS layer using this link is not configured at the SGSN.

5.72.8 Actions

5.72.8.1 Steps • If all NSVCs on this Frame Relay link have failed then check the Frame Relay link as

described in IPA_FRIP_FR_LINK_FAILURE. • Check that the NS layer configuration at the SGSN. Confirm that the NS layer is set up to use

this Frame Relay link. Confirm the DLCI configured at the SGSN corresponds with the DLCI at the FRIP.

• If the problem remains, report the problem to your nanoGSM customer support provider.

© ip.access Ltd


5.73 NSVC failure (UDP side)



5.73.3 Alarm Token IPA_FRIP_NSVC_UDP_FAILURE




5.73.7 Meaning This alarm is generated by the FRIP if there are no frames received from the BTS/GNAT on this NSVC. The alarm will clear when frames are received from the BTS/GNAT.

5.73.7.1 Possible Causes • BTS/GNAT not running. • UDP/IP configuration mismatch between the BTS/GNAT and the FRIP.

5.73.8 Actions

5.73.8.1 Steps • Check that the BTS/GNAT with the IP address corresponding to this NSVC is running. • Confirm that the NSVC remote IP address and port configured at the BTS/GNAT correspond

with the FRIP IP address and port configured for this NSVC. • Confirm that the NSVC local port configured at the BTS/GNAT corresponds with the remote

port configured for this NSVC. • If the problem remains, report the problem to your nanoGSM customer support provider.

© ip.access Ltd


5.74 Invalid PDU type received


5.74.2 Alarm Source GNAT

5.74.3 Alarm Token IPA_GNAT_UNKNOWN_PDU_TYPE




5.74.7 Meaning An NS-UNITDATA message has been received containing an unknown BSSGP message. This is most likely due to packet corruption on the Gb link toward the SGSN or a BTS and may affect GPRS service within the BSS.

5.74.8 Actions

5.74.8.1 Steps • A single instance of this alarm can probably be safely ignored. If the alarm recurs, confirm the

IP network is operating correctly and that the software releases of the BTS, GNAT and SGSN are compatible.

• If GPRS service on a single cell has been affected then it is recommended that the GPRS NSE object of the affected BTS be locked and unlocked.

• If GPRS service on all cells within the BSS has been affected then it is recommended that the GNAT be restarted.

• If the problem recurs, report the problem to your nanoGSM customer support provider.

© ip.access Ltd


5.75 Invalid API ID received



5.75.3 Alarm Token IPA_GNAT_INVALID_API_ID




5.75.7 Meaning A reserved or unknown message has been received at the NS or BSSGP layer within the GNAT. This may affect GPRS service.

5.75.8 Actions

5.75.8.1 Steps • If GPRS service on a single cell has been affected then it is recommended that the GPRS

NSE object of the affected BTS be locked and unlocked. • If GPRS service on all cells within the BSS has been affected then it is recommended that the

GNAT be restarted. • If the problem recurs, report the problem to your nanoGSM customer support provider.

© ip.access Ltd


5.76 Message not expected



5.76.3 Alarm Token IPA_GNAT_MSG_INCOMP_WITH_STATE




5.76.7 Meaning A BSSGP message has been received which is incompatible with the current state of the system.

5.76.8 Actions




© ip.access Ltd


5.77 IE parse error



5.77.3 Alarm Token IPA_GNAT_IE_PARSE_ERROR




5.77.7 Meaning There was a problem parsing an information element in an NS layer message.

5.77.8 Actions




© ip.access Ltd


5.78 Too many params in message



5.78.3 Alarm Token IPA_GNAT_NUM_PARAMS_EXCEEDS_LIMIT




5.78.7 Meaning This alarm has not yet been implemented and should not be seen.


© ip.access Ltd


5.79 TLLI does not exist



5.79.3 Alarm Token IPA_GNAT_TLLI_NOT_KNOWN




5.79.7 Meaning A condition has occured by which the GNAT has received a message for an unknown MS. This may cause temporary loss of service to the user, depending on the conditions causing the alarm.

5.79.8 Actions If the alarm occurs while experiencing specific GPRS service problems or is recurring, report the problem to your nanoGSM customer support provider.

© ip.access Ltd


5.80 Signalling BVC not provisioned



5.80.3 Alarm Token IPA_GNAT_SIG_BVC_NOT_PROV






© ip.access Ltd


5.81 NSEI unknown or not provisioned



5.81.3 Alarm Token IPA_GNAT_NSEI_NOT_KNOWN




5.81.7 Meaning The NSEI sent in the NS UNITDATA to/from the BTS or SGSN is invalid or unprovisioned.

5.81.8 Actions

5.81.8.1 Steps • The primary cause of this error is a misconfiguration between the GNAT and the SGSN.

Confirm the GNAT and SGSN are configured with the same NSEI and restart the GNAT. • If the alarm recurs, report the problem to your nanoGSM customer support provider.

© ip.access Ltd


5.82 NSEI not operational



5.82.3 Alarm Token IPA_GNAT_NSEI_NOT_OPERATIONAL




5.82.7 Meaning An attempt has been made to send a message on an NSEI that is not currently operational.

5.82.8 Actions

5.82.8.1 Steps • If the alarm occurs while experiencing GPRS service problems or is recurring, verify correct

configuration of NSEIs at the GNAT and SGSN. Restart the GNAT. • If you are still experiencing GPRS service problems or the alarm is recurring, report the

problem to your nanoGSM customer support provider.

© ip.access Ltd


5.83 BVCI unknown or not provisioned



5.83.3 Alarm Token IPA_GNAT_BVCI_NOT_KNOWN




5.83.7 Meaning An attempt has been made to send a message on a BVCI that is not currently operational.

5.83.8 Actions If the alarm occurs while experiencing specific GPRS service problems or is recurring, report the problem to your nanoGSM customer support provider.

© ip.access Ltd


5.84 BVC blocked



5.84.3 Alarm Token IPA_GNAT_BVC_BLOCKED




5.84.7 Meaning This alarm indicates the GNAT has blocked a PTP-BVC to the SGSN or a PTP-BVC has been blocked by a BTS. The alarm will clear on the BVC becoming unblocked.

5.84.8 Actions

5.84.8.1 Steps • This is normally due to management intervention e.g. locking objects on a BTS. The alarm

will clear on bringing the affected node back into service. • Confirm that the NSVC(s) between the BTS(s) and the GNAT and between the GNAT and the

SGSN are alive and unblocked. If there is a failure at the NS layer, the problem may be due to incorrect NSVC configuration at the BTS, GNAT and/or SGSN or a failure of the IP network.

• Lock and unlock the GPRS Cell and/or GPRS NSE object on the affected BTS. • If the problem persists, further investigation using E1/T1/Frame Relay and Ethernet/IP test

equipment will be required in order to observe Gb messaging between the BTS, GNAT, FR-IP Converter and SGSN.

© ip.access Ltd


5.85 BVCI is invalid



5.85.3 Alarm Token IPA_GNAT_INVALID_BVCI




5.85.7 Meaning An attempt has been made to block or unblock a Signalling or PTM BVC.

5.85.8 Actions Report the problem to your nanoGSM customer support provider.

© ip.access Ltd


5.86 NS reset in progress



5.86.3 Alarm Token IPA_GNAT_NS_RESET_IN_PROGRESS




5.86.7 Meaning A message has been sent or received on an NSVC by the GNAT during an NS reset procedure.

5.86.8 Actions

5.86.8.1 Steps • If this occurs during management intervention at the GNAT, BTS(s) or SGSN and service is

otherwise unaffected, the alarm can be ignored. • If this occurs during management intervention and GPRS service is affected (beyond that

expected by the management action), confirm correct NSVC configuration at the BTS(s), GNAT, FR-IP Converter and SGSN. Restart the GNAT.

• If the alarm recurs, report the problem to your nanoGSM customer support provider.

© ip.access Ltd


5.87 BVC-BLOCK failure



5.87.3 Alarm Token IPA_GNAT_BVC_BLOCK_FAILURE




5.87.7 Meaning The maximum number of retries of the (PTP) BVC-BLOCK procedure towards the SGSN has been reached without receiving a BVC-BLOCK-ACK. This alarm most likely indicates a problem at the SGSN.

5.87.8 Actions

5.87.8.1 Steps • Check the SGSN NS/BSSGP configuration for this NSE/BSS. If there is a problem, correct it. • If the above step does not resolve the problem, restart the GNAT. • If the problem persists, report the problem to your nanoGSM and/or SGSN customer support

provider.

© ip.access Ltd


5.88 BVC-UNBLOCK failure



5.88.3 Alarm Token IPA_GNAT_BVC_UNBLOCK_FAILURE




5.88.7 Meaning The maximum number of retries of the (PTP) BVC-UNBLOCK procedure towards the SGSN has been reached without receiving a BVC-UNBLOCK-ACK. This alarm most likely indicates a problem at the SGSN.

5.88.8 Actions

5.88.8.1 Steps • Check the SGSN NS/BSSGP configuration for this NSE/BSS. If there is a problem, correct it. • If the above step does not resolve the problem, restart the GNAT. • If the problem persists, report the problem to your nanoGSM and/or SGSN customer support

provider.

© ip.access Ltd


5.89 BVC-RESET failure



5.89.3 Alarm Token IPA_GNAT_BVC_RESET_FAILURE




5.89.7 Meaning The maximum number of retries of the BVC-RESET procedure towards the SGSN or BTS has been reached without receiving a BVC-RESET-ACK. This alarm most likely indicates a problem at the SGSN or BTS or an unexpected state at the GNAT.

5.89.8 Actions

5.89.8.1 Steps • Check the SGSN NS/BSSGP configuration for this NSE/BSS. If there is a problem, correct it

and restart the GNAT if the problem does not resolve itself. • Check the BTS configuration for this BVC (GPRS Cell object). If there is a problem, correct it

and restart the GNAT if the problem does not resolve itself. • If the above steps do not resolve the problem, restart the GNAT. • If the problem persists, report the problem to your nanoGSM and/or SGSN customer support

provider.

© ip.access Ltd


5.90 NSVCI unknown or not provisioned



5.90.3 Alarm Token IPA_GNAT_NSVCI_NOT_KNOWN




5.90.7 Meaning The NSVCI received in a message is invalid or unprovisioned. The primary cause of this error is a misconfiguration between the GNAT and the SGSN.

5.90.8 Actions

5.90.8.1 Steps • Confirm the GNAT and SGSN are configured with the same NSVCI(s). If there is a problem,

correct it and restart the GNAT if the problem does not resolve itself. • If the alarm recurs, report the problem to your nanoGSM customer support provider.

© ip.access Ltd





5.92.3 Alarm Token IPA_GNAT_LOSS_OF_COMMUNICATIONS




5.92.7 Meaning This alarm is generated by the GNAT management agent if it has lost communication with the GNAT. The alarm will clear when the GNAT management agent re-establishes communications with the GNAT.

5.92.8 Actions

5.92.8.1 Steps • If the connection does not recover automatically within a minute, restart the GNAT. • If the alarm persists or recurs, report the problem to your nanoGSM customer support

provider.

© ip.access Ltd


5.93 GNAT core connection lost



5.93.3 Alarm Token IPA_GNAT_LOSS_OF_GNAT_CORE




5.93.7 Meaning This alarm is generated by the GNAT management agent if there has been a loss of communications with the GNAT core application. The alarm will clear when the GNAT re-establishes communications with the core application.

5.93.8 Actions

5.93.8.1 Steps • If the connection does not recover automatically within a minute, restart the GNAT. • If the alarm persists or recurs, report the problem to your nanoGSM customer support

provider.

© ip.access Ltd


5.94 NSVC Failure



5.94.3 Alarm Token IPA_GNAT_NSVC_DEAD




5.94.7 Meaning This alarm means the GNAT has detected the failure of an NSVC. This may be due to a physical link problem (cabling), a mismatch in configuration between the BTS, GNAT, FR-IP Converter and SGSN or a hardware problem in one of these items.

5.94.8 Actions


the BTS, 2) BTS NSEI at the GNAT, 3) SGSN NSEI and NSVC(s) at the GNAT, 4) BTS/GNAT, SGSN and FR configuration at the FR-IP Converter (ip_fr_route_table, ip_fr_config, fr_config), 5) NSEI, NSVC(s) and FR configuration at the SGSN. In particular check that the IP addresses, NSVCIs and DLCIs all match. Once the correct configuration is present and assuming the BTS, GNAT, FR-IP and SGSN are running, the NSVC should automatically recover.

• If the NSVC does not recover after correcting configuration then confirm that the physical connections are present. Check for green lights on the T1/E1 sockets of the FR-IP Converter that are connected to the SGSN. If a socket has a red light this most likely indicates a cabling problem. If a socket has an orange light this most likely indicates a T1/E1 configuration problem. Check for a green light on the Ethernet socket of the BSC/GNAT/FR-IP Converter and check the cabling and routing configuration between the BSC/GNAT/FR-IP Converter and the BTS.

• If the problem persists, further investigation using E1/T1/Frame Relay and Ethernet/IP test equipment will be required in order to observe Gb messaging between the BTS, GNAT, FR-IP Converter and SGSN.

© ip.access Ltd


5.95 NSVC blocked



5.95.3 Alarm Token IPA_GNAT_NSVC_BLOCKED




5.95.7 Meaning This alarm indicates the GNAT has blocked an NSVC or an NSVC has been blocked by a peer entity (BTS or SGSN). The alarm will clear on the NSVC becoming unblocked. The GNAT should not normally block NSVCs towards the SGSN although this may occur during reconfiguration or start up.

5.95.8 Actions

5.95.8.1 Steps • The GNAT will block NSVCs towards the BTSs if the link to the SGSN is down. If BTS NSVCs

are being blocked by the GNAT, confirm correct operation of the SGSN NSVCs. Check for consistency between the following sets of configuration: 1) SGSN NSEI and NSVC(s) at the GNAT, 2) BTS/GNAT, SGSN and FR configuration at the FR-IP Converter (ip_fr_route_table, ip_fr_config, fr_config), 3) NSEI, NSVC(s) and FR configuration at the SGSN. In particular check that the IP addresses, NSVCIs and DLCIs all match. Once the correct configuration is present and assuming the GNAT, FR-IP and SGSN are running, the NSVC should automatically recover.

• If the SGSN has blocked an NSVC, then take action at the SGSN to unblock it. • If the problem persists, further investigation using E1/T1/Frame Relay and Ethernet/IP test

equipment will be required in order to observe Gb messaging between the BTS, GNAT, FR-IP Converter and SGSN.

© ip.access Ltd


5.96 Out of memory



5.96.3 Alarm Token IPA_GNAT_OUT_OF_MEMORY




5.96.7 Meaning The GNAT has been unable to allocate memory for a specific task.

5.96.8 Actions Restart the GNAT and report the problem to your nanoGSM customer support provider.

© ip.access Ltd


5.97 Software warning



5.97.3 Alarm Token IPA_GNAT_SOFTWARE_WARNING




5.97.7 Meaning The GNAT has detected an unexpected condition but should be able to continue operating.

5.97.8 Actions

5.97.8.1 Steps • If there is a problem with GPRS service coinciding with this alarm, restart the GNAT. • If the alarm persists or recurs, report the problem to your nanoGSM customer support

provider.

© ip.access Ltd


5.98 Software fatal error



5.98.3 Alarm Token IPA_GNAT_SOFTWARE_FATAL




5.98.7 Meaning The GNAT has detected an unexpected condition and cannot continue operating.

5.98.8 Actions

5.98.8.1 Steps • Restart the GNAT. • If the alarm persists or recurs, report the problem to your nanoGSM customer support

provider.

© ip.access Ltd


5.99 Object is not initialised



5.99.3 Alarm Token IPA_GNAT_INIT_NOT_DONE




5.99.7 Meaning The GNAT has not been correctly initialised.

5.99.8 Actions Restart the GNAT. If the alarm persists or recurs, report the problem to your nanoGSM customer support provider.

© ip.access Ltd


5.100 Config file missing



5.100.3 Alarm Token IPA_GNAT_OAM_CONFIG_FILE_MISSING




5.100.7 Meaning The GNAT could not find the configuration file specified on the GNAT Management Function command line.

5.100.8 Actions

5.100.8.1 Steps • Confirm the existence of the file : /etc/ipaccess/gnat/gnat_config.xml. If this does not exist,

create it according to the GNAT User Guide. • If the file exists, report the problem to your nanoGSM customer support provider.

© ip.access Ltd


5.102 Unable to open log file



5.102.3 Alarm Token IPA_GNAT_UNABLE_TO_OPEN_LOG_FILE




5.102.7 Meaning There was a problem opening the debug log file. This should not occur in normal operation as logging is disabled by default.

5.102.8 Actions

5.102.8.1 Steps • Confirm the file name and path for the debug file are correct in the XML configuration file or

turn off debugging if not required. Reload the configuration file or restart the GNAT. • If the alarm recurs, report the problem to your nanoGSM customer support provider.

© ip.access Ltd


5.103 Unable to write to log file



5.103.3 Alarm Token IPA_GNAT_UNABLE_TO_WRITE_TO_LOG_FILE




5.103.7 Meaning There was a problem writing to the debug log file. This should not occur in normal operation as logging is disabled by default.

5.103.8 Actions

5.103.8.1 Steps • Confirm the file name and path for the debug file are correct in the XML configuration file or

turn off debugging if not required. Reload the configuration file or restart the GNAT. • Confirm there is sufficient disk space. If the disk is full, free up some disk space, stop

debugging and/or delete the debug file. • If the alarm recurs, report the problem to your nanoGSM customer support provider.

© ip.access Ltd


5.104 Error in config file



5.104.3 Alarm Token IPA_GNAT_CONFIG_FILE_XML_ERROR




5.104.7 Meaning There is an error in the GNAT XML configuration file. See the alarm's additional text field for further information.

5.104.8 Actions Correct the configuration file and instruct the GNAT to reload it.

© ip.access Ltd


5.107 MTP3 Route failed


5.107.2 Alarm Source Gateway

5.107.3 Alarm Token IPA_CCTA_ROUTE_FAILED




5.107.7 Meaning This alarm means that the MTP3 route to the MSC has failed. This is caused by loss of all MTP2 links between the BSC and the MSC. The alarm additional text field indicates which point codes are affected.

5.107.8 Actions

5.107.8.1 Steps • Check that all physical connections between the Media Gateway and the MSC are in place,

and if any cables have become disconnected, plug them in again. • Check that the physical layer LED on the gateway card is lit green. If it is red, the MTP1 layer

has failed - check connections again and that the physical layer configuration matches that of the link (E1/T1, line coding etc).

© ip.access Ltd





5.108.3 Alarm Token IPA_SMGW_LOSS_OF_COMMUNICATION




5.108.7 Meaning This alarm means that the BSC's management agent has lost communication with the equipment or software represented by the managed object that the alarm has been raised on. If the managed object represents the gateway card, possible reasons include: physical disconnection of network between the Gateway card and the Main CPU card; failure of a network interface or network node; complete or partial failure of the Gateway card or the Media Gateway application. If the managed object represents the sigtran stack, the alarm is due to complete or partial failure of the sigtran stack.

5.108.8 Actions For loss of communication with the gateway, check that all physical connections between the Gateway card and the BSC's Main CPU card are in place, and if any cables have become disconnected, plug them in again. If the physical connections are OK, check that the Gateway card is plugged into the rack and powered, the BSC processes are still running, and if necessary restart the BSC. For loss of communication with the sigtran stack, recovery should be automatic: if it isn't, check the sigtran config files.

© ip.access Ltd


5.109 Loss of Signal



5.109.3 Alarm Token IPA_MGW_PCMLINK_LOS




5.109.7 Meaning Loss of Signal alarm on the PCM (E1/T1) link. The physical link has been lost.

5.109.8 Actions Check that all physical connections between the BSC's Gateway card and the MSC are in place, and if any cables have become disconnected, plug them in again. The alarm additional text field describes which physical connection on the gateway card is affected.

© ip.access Ltd


5.110 Loss of Framing



5.110.3 Alarm Token IPA_MGW_PCMLINK_LOF




5.110.7 Meaning Loss of Framing alarm on the PCM (E1/T1) link. The physical link has been lost.


© ip.access Ltd


5.111 Remote Alarm Indication



5.111.3 Alarm Token IPA_MGW_PCMLINK_RAI




5.111.7 Meaning Remote Alarm Indication alarm on the PCM (E1/T1) link. There is a problem at far end of the PCM link.


© ip.access Ltd


5.112 Alarm Indication Signal



5.112.3 Alarm Token IPA_MGW_PCMLINK_AIS




5.112.7 Meaning Alarm Indication Signal on the PCM (E1/T1) link.


© ip.access Ltd


5.113 CRC errors



5.113.3 Alarm Token IPA_MGW_PCMLINK_RIA_CRC




5.113.7 Meaning CRC errors on the PCM (E1/T1) link.


© ip.access Ltd


5.114 MTP2 Link failed



5.114.3 Alarm Token IPA_SGW_MTP2_LINK_FAILED




5.114.7 Meaning This alarm means that a MTP2 link to the MSC has failed. If no other MTP2 links are available, this will also mean loss of the A-Interface. The alarm additional text field indicates the SLC of the affected link.

5.114.8 Actions

5.114.8.1 Steps • Check that all physical connections between the BSC's Gateway card and the MSC are in

place, and if any cables have become disconnected, plug them in again. • Check that the physical layer LED on the Gateway card is lit green. If it is red, the MTP1 layer

has failed - check connections again and that the physical layer configuration matches that of the link (E1/T1, line coding etc).

© ip.access Ltd


5.115 M2UA layer down



5.115.3 Alarm Token IPA_SGW_M2UA_FAILED




5.115.7 Meaning This alarm means that the layer 2 (M2UA) between the sigtran stack and the signalling gateway is down.

5.115.8 Actions

5.115.8.1 Steps • Check that all physical connections between the BSC and the Signalling Gateway card are in

place, and if any cables have become disconnected, plug them in again. • Check that the Signalling Gateway IP Address configuration (using config-bsc tool) matches

that of the signalling gateway card. • Check that at least one signalling link has been provisioned on the Signalling Gateway (using

config-bsc tool).

© ip.access Ltd


5.116 SCTP association (connection) failed



5.116.3 Alarm Token IPA_SGW_SCTP_ASSOCIATION_FAILED




5.116.7 Meaning This alarm means that the SCTP association (connection) to the Signalling Gateway has failed. The alarm additional text field indicates the ip address of the affected signalling gateway.

5.116.8 Actions

5.116.8.1 Steps • Check that all physical connections between the Media Gateway and the BSC are in place,

and if any cables have become disconnected, plug them in again. • Check that the Signalling Gateway IP Address configuration (using config-bsc tool) matches

that of the signalling gateway card.

© ip.access Ltd


5.117 Sigtran stack configuration is invalid



5.117.3 Alarm Token IPA_SGW_INVALID_CONFIGURATION




5.117.7 Meaning This alarm means that the sigtran stack configuration is invalid, almost certainly resulting in the A-interface being unavailable. The sigtran.conf file on the BSC has been corrupted, is missing required entries or contains invalid entries.

5.117.8 Actions Regenerate the sigtran configuration file by using the config-bsc tool and temporarily changing the sigtran configuration (e.g. change a point code and then change it back again). Then restart the BSC in order to load the newly generated configuration file.

© ip.access Ltd


5.118 Database Integrity Check Failed



5.118.3 Alarm Token IPA_BSC_DB_INTEGRITY_FAILED




5.118.7 Meaning The BSC has performed an integrity check on its database and found that one or more tables has not been closed properly, probably because power to the BSC was lost while the BSC was running. The BSC will have paused, awaiting operator intervention, because it cannot operate until this problem has been corrected. The alarm's Additional Text indicates which database table(s) were found not to have been closed properly.

5.118.8 Actions Stop the BSC. Restore the last known good BSC database that was backed up. Restart the BSC and, if necessary, adjust it to the configuration immediately prior to the integrity check failure.

© ip.access Ltd


5.119 Wrong Attribute Type


5.119.2 Alarm Source OMC-R

5.119.3 Alarm Token IPA_OMCR_WRONG_ATTRIBUTE_TYPE




5.119.7 Meaning This alarm means that the BSC has sent the OMC-R an attribute whose type does not match the definition in the Management Information Base (MIB). The OMC-R will not display this invalid data.

5.119.8 Actions Since the OMC-R is able to continue operating, no repair action is required. Please report the occurrence of this alarm to your nanoGSM customer support provider.

© ip.access Ltd


5.120 Wrong Attribute Type



5.120.3 Alarm Token IPA_OMCR_INVALID_ATTRIBUTE_TYPE




5.120.7 Meaning This alarm means that the BSC has sent the OMC-R an attribute whose type does not match the definition in the Management Information Base (MIB). The OMC-R will not display this invalid data.


© ip.access Ltd


5.121 Invalid Attribute Value



5.121.3 Alarm Token IPA_OMCR_INVALID_ATTRIBUTE_VALUE




5.121.7 Meaning This alarm means that the BSC has sent the OMC-R an attribute whose value is does not conform to the defined range or format as specified in the Management Information Base (MIB). The OMC-R will not display this invalid data.


© ip.access Ltd


5.122 Missing Attribute



5.122.3 Alarm Token IPA_OMCR_MISSING_ATTRIBUTE_VALUE




5.122.7 Meaning This alarm means that the BSC has sent the OMC-R an Managed Object, but an Attribute as specified in the Management Information Base (MIB) is missing.


© ip.access Ltd





5.123.3 Alarm Token IPA_OMCR_LOSS_OF_COMMUNICATIONS_TO_BSC




5.123.7 Meaning This alarm means that the OMC-R server has lost communication with the BSC. Possible reasons for this include: physical disconnection of network between the OMC-R server and the BSC; failure of a network interface or network node; complete or partial failure of the BSC itself. If the OMC-R server loses communication with all BSC's, it is likely that there is a physical network problem at, or close to, the OMC-R server. If it loses communication with a set of BSCs that are on a common sub-network, it is likely that there is a physical network problem in that sub-network. If communication with just one BSC is lost, it is likely that there is a problem at, or, close to that particular BSC.

5.123.8 Actions Check that all physical connections between the OMC-R server and the BSC are in place, and if any cables have become disconnected, plug them in again. If the physical connections are OK, check that all BSC processes are still running, and if necessary restart the BSC.

End of Document

Ip Access Alarms

Documents

Transcript of Ip Access Alarms