UBS-45!41!009 v1.2 AP Alarms and Events

© 2011 Ubiquisys Limited. All rights are reserved; reproduction in whole or in part is prohibited without written consent of the copyright owners.

(07 October 11)

Version 1.2

UBS-45-41-009

Femto Engine ™ AP Alarms and Events for G 3 APs

Femto Engine AP Alarms and Events /22 07 October 11

© 2011 Ubiquisys Limited –Company Confidential

Contents

1 AP DIAGNOSIS .................................................................................................................................................. 3

2 FACTORY RESET PROCEDURE .................................................................................................................. 3

2.1 TIER 1 (AP AT END USER LOCATION) ........................................................................................................... 4 2.1.1 UE Checks ............................................................................................................................................ 8

2.2 TIER 2 (AP AT MNO RETURNS LOCATION) .................................................................................................. 8 2.3 TIER 3 (AP AT SI RETURNS LOCATION) ........................................................................................................ 9

3 FAULT MANAGEMENT ................................................................................................................................. 11

3.1 EVENT MANAGEMENT .................................................................................................................................. 15 3.1.1 AP Events – Cause and Action ....................................................................................................... 16

4 GLOSSARY ...................................................................................................................................................... 21

ANNEX A – CHANGE HISTORY .......................................................................................................................... 22



1 AP Diagnosis

The diagnostic process can be performed through various levels, from customer to field engineer. The LED information supplied to the customer in their User Guide provides LED sequences with recommended basic checks to perform, such as moving the AP, checking cables etc., where other sequences will direct the user to contact Customer Services. At this point tier one and tier two staff should refer to table 1, which provides some more diagnosis scenarios and checks to perform.

Finally, tier three engineers can use the ZoneGate Trace Tool to debug the AP. All levels of AP checks should be performed prior to returning a G3 ZoneGate AP.

2 Factory Reset Procedure

The Factory Reset (FR) procedure is intended to ensure that a ZoneGate AP can be recovered from a bad state without having to return it to the factory. It should then be able to establish a connection with the APMS and download its database and settings and/or the latest software load as normal.

Check on the ZAS that the AP has a profile and that it has the correct network configuration. If valid then tell user to press the reset button for 10 seconds and then release. The AP will now carry out an FR procedure. The LEDs on the AP will show the sequence of the states that the AP goes through. If the AP does not recover to an operational state then there is a problem with the AP and the unit should be returned.

When instructed by the following table, perform the FR process as described above .



2.1 Tier 1 (AP at End User Location)

Tier 1 personnel with ZAS access should make the following initial AP status checks:

• Is the AP authorised?

• Perform a “check recovery” for the AP to check the factory recovery profile is correct

• Is the designated network for the AP correctly configured?

o Check the AP’s factory recovery logs for errors during deployment or recoveries

The following two tables depict the G3 LED sequences for LED profiles 0 and 1 (where profile zero is the default and profile 1 is optional). All tier 1 personnel should check the AP’s LED state against the following cause and actions:

Diagnosis ProcessAP STATUS

No power: Ensure power supply is connected and turned on. If this

still fails return unit.Unknown state or off

This occurs during software initialisation, and so is a transitional

state. Wait for action to complete. If not cleared then call the

Operator.Initialisation - Boot

The AP has started up OK, and is connecting to the core network.

Wait for action to complete. If not cleared then call the Operator.Initialisation -Connecting

The AP has been partially provisioned. Awaiting additional

parameters to be provisioned. Wait for action to complete. If not

cleared then call the Operator.

Initialisation - Not provisionedThe AP has been partially provisioned. Awaiting additional

parameters to be provisioned. Wait for action to complete. If not

cleared then call the Operator.

Initialisation - Listen Mode

In operation and can support callsIn Service. No Active calls (CS/PS),

no voice mail

In operation and can support callsIn Service. Active calls (CS/PS), no

voice mail

Temporary interference. Phones may be too close to the AP.

Contact the Operator if it persists.RF Issue. Local interference

Wait for action to complete. If not cleared then call the Operator.

This could be due to diagnostics, software upgrade or listen mode or

whilst the AP is getting provisioning information.Temporary out of service

F

3

F

LED

F

F

F

S

No physical LAN Connection 1

This is the equivalent to the LEDs on an RJ45 connector. There is

no electrical connection with the residential gateway. User should

check connection with residential gateway.

No connection with routerThe AP has an electrical connection but cannot get an IP address.

This is probably a problem with the residential gateway. 1

No Internet connectionCheck AP connection with ISP/Internet. Is the residential gateway

connected to the Internet ? 2

No SIM card detected 5

The SIM card is either not inserted or it could be the wrong type of

SIM card (i.e. the AP cannot read it). The user should check the SIM

is inserted properly and that it is the one provided.

HNB over Temperature 4The AP is over temperature. Check the AP location and check there

is good air flow.

RF issue - the AP cannot select an

RF profile

The AP is experiencing excessive interference, which means it

cannot provide service. This could be because another AP is located

close by. The user needs to relocate the AP. If still persists then call

the Operator to resolve.



Diagnosis ProcessAP STATUS LED

The AP has been blocked at the core network gateway. This could

be because the SIM is not the correct one or the SIM has been

blocked by the Operator. The user should check the SIM card

inserted is the correct one. If it is contact the Operator.

Cannot create secure connection

The AP has established a connection with the Operator core

network but has not been able to establish a connection with the

ZMS to complete its provisioning process. This may be because the

AP is blacklisted by the ZMS or ZMS has no provisioning information

for the AP.

Provisioning Failure

Internal fault AP has a fault and cannot provide service, contact the Operator

Initialisation - ProvisioningThe AP is waiting for all the parameters to complete its provisioning

process. Wait for action to complete. If not cleared then call

operator.

F

In service but with congestion and

so cannot accept any more calls2 In operation and so cannot accept any more calls

Initialisation - Initial bootWait for a period of up to 20 minutes, if the state does not change

carryout a factory reset procedure

Factory reset 1 (entering)

Factory reset 2 (downloading

recovery image)

Factory reset 3 (upgrading

software)

Factory reset 4 (critical upgrading

software)

Wait for a period of up to 20 minutes, if the state does not change








F

F

F

F

F/S

F/S

OFF

Static

green

Static

red

Flashing green Fast or Slow)

Flashing red (Fast or slow)

LED Legend

Flashing a number of times

(red or green depicted)1-5

Only applicable to IMS mode

Femto+ location verification failure Contact Operator support.6

Backhaul issue. Service-affecting

QOSService is inhibited due to 0 call capacity

Green/

red alt

Table 1 – Profile 0 (default) Tier 1/2 LED Status Cause and Action



Diagnosis ProcessAP STATUS LED

The unit has been blocked at the core network gateway. The SIM

may not the correct one or it has been blocked by the Operator. The

user should check the SIM card inserted is the correct one. If it is, or

no SIM card is required for the unit contact the Operator.

Cannot create secure connection

The unit has established a connection with the Operator core

network but has not been able to establish a connection with the MS

to complete its provisioning process. This may be because the unit

is blacklisted by the MS, or the MS has no provisioning information.

Provisioning Failure

Internal fault Unit has a fault and cannot provide service, contact the Operator

Initialisation - ProvisioningThe unit is waiting for all the parameters to complete its provisioning

process. Wait for action to complete. If not cleared then call the

Operator.

Initialisation - Initial bootWait for a period of up to 20 minutes, if the state does not change


Factory reset 1 (entering)

Factory reset 2 (downloading

recovery image)

Factory reset 3 (upgrading

software)

Factory reset 4 (critical upgrading

software)









F

F

F

F

F/SOFF

Static

green

Static

red

Flashing green, red or orange

(Fast or Slow)

Flashing a number of times

green, red or orange

LED Legend

1-6

1

4

S

Femto+ location verification failure Contact Operator support.6

Green/red alternating

Shaded items do not apply to this

release

When the Network Mode is Iuh, the term:

– Unit represents the HNB

– MS represents the HMS

When the Network Mode is GANC, the term:

– Unit represents the AP

– MS represents the ZMS

Table 2: Profile 1 (optional) Tier 1/2 LED Status Cause and Action



2.1.1 UE Checks

When the AP is indicating normal functionality but the user has an issue, make the following handset checks:

• Is the UE IMSI permitted to register on the AP?

• If CS calls are working but PS fail, confirm the PS data configuration on the UE

• If SMS take longer than 10 seconds to send, check the UE is CS SMS configured not PS SMS

2.2 Tier 2 (AP at MNO Returns Location)

Assuming Tier 2 support has access to the ZAS, then check the status of the AP in the following areas:

• Is the AP authorised?

• Perform a “check recovery” for the AP to ensure the factory recovery profile is correct

• Is the designated network for the AP correctly configured?

• Check the AP’s factory recovery logs for errors during deployment or recoveries

• Power up the AP with a known working, provisioned SIM, DC adaptor, Internet connection

All tier 2 personnel should check the AP’s LED state in tried and tested environments (provisioned SIM, DC adaptor, Internet connection etc.) against the following cause and actions:

• 5 flashing red

o Return the unit

• Solid red

Cannot connect to security gateway

o Check DNS lookup for secure gateway FQDN

• Fast green

AP cannot communicate to the INC but IPSec tunnel has been esta blished

o Check the internal DNS server and resolve INC FQDN

o Check the INC

o Use Wireshark to confirm there is AP to INC communication

• 3 flashing red

o Return the unit

• Solid red

o Return the unit

• Fast green

• Solid red

o Verify provisioning on LBR

• Solid green (normal LED status)

o AP believes it is OK – carry out voice call validation

• Fast green

o Return the unit

• Fast green



Trying to provision or trying to boot or trying to contact ZAS for deployme nt

o Press the reset button for 3 seconds to invoke a factory recovery

o Use Wireshark to validate the recovery server DNS lookup

The final tier 2 screening check is a voice call validation:

• Power up the AP with known working, provisioned SIM, DC adaptor, Internet connection and provisioned (both on the AP and network) UE SIM and UE with engineering software, e.g. Nemo

o Attempt to register a UE on the AP

o Validate the registration with LBR logs

o If no registration is visible, attempt manual network selection on UE (use UE scrambling code lock)

o Validate the location update parameters using Wireshark on LBR and APMS data

o Attempt a voice call to PSTN/Macro network – if this fails at this point it is likely to be a network issue

o If voice call is OK then the AP is NFF

o If the call fails verify there is no global issue and if not, return the unit

2.3 Tier 3 (AP at SI Returns Location)

Follow the guidelines for tier 2 in section 2.2 and additionally use the ZoneGate Trace Tool to debug the AP. Ubiquisys training material can be used for guidance. Some of the more frequent scenarios are detailed below:

Faults on AP Power-up

<state> RF interference <indicator> fast green <cause> proximity of other APs/excessive interference on same frequency <process> set sniff trace high, filter for RF interference

UE Camp on Failures

<state> camp on failure <indicator> camp on failure <cause> UE subscriber list <process> confirm in APMS

<state> camp on failure <indicator> camp on failure <cause> MMC MCC mismatches AP broadcast to SIM <process> confirm on APMS

<state> camp on failure <indicator> camp on failure <cause> UE camps on another AP <process> verify UE status on Web GUI

<state> camp on failure <indicator> camp on failure indicated in Event log <cause> excessive trace <process> Excessive trace – multiple UEs camping – set to minimum



Voice Call Failures

<state> failure to set up <indicator> failure to set up indicated in Event log <cause> excessive trace <process> reduce trace

<state> failure to set up <indicator> failure to set up call - significant event viewable in log <cause> blocked due to Dynamic Downlink monitor mode being active (DLMM session controller) <process> unblock

<state> failure to set up <indicator> Poor HSDPA <cause> lack of power <process> excessive radio uplink reconfiguration, limit uplink to 128k, default 384k

<state> poor throughput <indicator> data rate <cause> simultaneous uplink/downlink reduces flow on both <process> reduce flow

<state> calls drop <indicator> RLC reset, CRC reset EC/IO values in trace <cause> RF signal, radio bearer reconfiguration <process> disregard

CPU Overload

<state> call rejected, shown in event log <indicator> event log insufficient resources <cause> high data, excessive video calls <process> Check PKTC loading

APMS Failure

<state> no authentification <indicator> provisioning error <cause> user name password, AP mismatch <process> check and resolve

<state> connection failure <indicator> connection failure <cause> Script engine timeout <process> Sufficient time to run the event within the engine timeout period required

<state> inform failure <indicator> failure to provision <cause> IPSec tunnel failure after s/w upgrade <process> OAMP – HIGH check events prior such as above or reboot, Wireshark of APMS to AP

traffic



3 Fault Management

The ZoneGate AP monitors for any faults within its system and can report problems to the APMS automatically if there is a problem. The alarms are used by the Operator’s Customer Care representative to help isolate customer reported issues. Also the APMS will have the capability to correlate common alarms across a number of femtocells so common problems can be highlighted quickly. For example, a number of femtocells raise a timing server alarm this may mean that the timing server has failed.

The number of alarm types that a femtocell can raise is restricted to ensure that the APMS is not flooded with excess number of messages.

TR-069 does not support alarms but it does support parameter value change notifications. This means that if a specific parameter value changes then the femtocell will send a notification to the APMS. So to support alarms a group of parameters (of type dateTime) have been created to represent alarms. If the parameter value is zero then the alarm is not active. If the value is not zero then the alarm is active and the time represents when the alarm was raised.

Parameter Description CannotSelectRFProfile The AP is unable to select a valid set of RF parameters because of excessive

interference. This alarm can be cleared by the AP if its RF environment changes or a new set of RF parameters are provided. Severity = Major AP Status = MAJOR FAULT LED Status =RF Issue

SoftwareFault The AP detected a software problem which requires it to re-initialise in order to provide service. Set when the AP detects a major software fault. This alarm is not cleared by the AP. The AP will inform the APMS whenever there is a new failure. Severity = Warning AP Status = Transient and so not shown LED Status = Transient and so not shown

PMReportFailure The AP is unable to upload the PM files. Set when the AP fails to upload a file. Cleared when the AP completes an up load. Severity = Warning AP Status = WARNING LED Status = Not shown

The APMS can correlate alarms across multiple APs to identify network wide issues (e.g. RF interference in a localised area). The APMS can forward these alarms to the OSS. APMS

Server

Inform message (value change)

APMS displays the alarms reported for an AP. This helps diagnose a customer problem.

.

Minimum time between Inform messages to ensure AP MS is not overloaded.

A number of parameters (type dateTime) are identified as alarms. The value of parameter is the time the alarm was raised (if 0 then alarm cleared)

OSSAPMS GUI

FemtocellFemtocell



Parameter Description LocationChanged The AP has detected that it has potentially change location.

Set when the AP detects a location change. Not cleared by the AP. Further changes will be notified to the APMS. Severity = Warning AP Status = WARNING LED Status = Not shown

PoorRFQos The AP has measured that the QoS on the RF uplink and/or downlink have has diminished below a preset threshold. Set when the AP detects poor QOS for a defined period of time. This is cleared by the AP when it has good QoS for a defined period of time. Severity = Minor AP Status = MINOR FAULT LED Status = RF Issue. Local Interference

PoorBackHaulQoS The AP has measured that the QoS on the backhaul connection have has diminished below a preset threshold. Set when the AP detects poor QOS for a defined period of time. This is cleared by the AP when it has good QoS for a defined period of time. Details to be defined. Severity = Minor AP Status = MINOR FAULT LED Status = Not shown

OverTemperature The AP shutdown because of over temperature Set if the AP detects that it is over temperature and so shuts down its RF. Cleared when the AP enters normal operation. Severity = Warning AP Status = WARNING LED Status = Over Temperature

UpgradeFailure The AP could not complete its upgrade successfully. Set if the AP fails to complete the upgrade process. It may send additional failures on retires. Cleared when the AP is upgraded. Severity = Warning AP Status = WARNING LED Status = Not shown

FilesystemFailure The AP secondary file system has failed (escalated to a System Failure if the fault cannot be cleared). Set if the AP secondary file system has failed (escalated to a System Failure if the fault cannot be cleared). Cleared when file system has recovered. Severity = minor AP Status = MINOR FAULT LED Status = Not shown

HotSpotIndication The AP has detected an excessive number of attach rejects which indicates it is in a hotspot. Set if the AP detects that the number of attach rejects exceeds a threshold. Never cleared by the AP. Severity = Minor AP Status = MINOR FAULT LED Status = Not shown

NoNtpServer The AP cannot connect to an NTP server to set its internal date/time clock. If the AP cannot set its date time clock then it will continue to provide basic services. Any services that have an expiry date will be stopped until the AP has set its clock. The AP will only set this alarm if the date/time clock has not been set (i.e. after initialisation). It will not set the alarm if the AP looses connection to the NTP server during operation (i.e. the clock was already set. The alarm will be cleared if the AP gets access to the NTP server and sets its clock. Severity = Warning AP Status = WARNING LED Status = Not shown

InvalidCountry The AP has detected that it has potentially change location into a different country (AP home PLMN MCC has not been detected on any macro cells) Set when the AP detects an invalid country. Further changes will be notified to the APMS. Severity = Warning AP Status = WARNING LED Status = Not shown



Parameter Description GatewayChanged The AP has detected that it has potentially change location as the Home Gateway

MAC address has changed Set when the AP detects a gateway change. Not cleared by the AP. Further changes will be notified to the APMS. Severity = Warning AP Status = WARNING LED Status = Not shown

LossOfAllTimingServer Connectivity

The AP has detected that all the configured timing servers are no longer contactable. If macro coverage is lost this will lead to the NoTimingSource alarm Severity = Warning AP Status = WARNING LED Status = Not shown

NoTimingSource The AP has no macro coverage and there are either no timing servers configured or the LossOfAllTimingServerConnectivity alarm is raised. When in this state the timing within the AP will gradually drift out of spec unless timing of one form is restored. Current frequency accuracy can be queried in Device.X_UBIQUISYS_COM_ZAP.Network.IPTiming.PredictedResolution. If PredictedResolution gets worse than 250ppb then the AP may inhibit service depending on the setting of Device.X_UBIQUISYS_COM_ZAP.Network.IPTiming.PoorResolutionBehaviour Severity = Minor AP Status = MINOR FAULT LED Status = Not shown

EnterpriseLACReuseDetected The ZAP has detected that the LAC assigned to the enterprise is being used by a cell that is not part of the enterprise group Set when the ZAP detects reuse. This is cleared when the ZMS allocates a new LAC to the group that no longer conflicts with any adjacent cells outside the group. Severity = Warning ZAP Status = WARNING LED Status = Not shown

ServiceAffectingBackhaulQoS With only one CS call (voice or video) in progress, the AP has measured that the backhaul QoS parameters for that call have diminished below preset thresholds. As only one CS call is in progress then this implies that all CS services are affected by the condition. Set when the AP detects poor backhaul performance when only one CS call is in progress. This is cleared by the AP when it detects good QoS again or when the call is released. Severity = Minor AP Status = MINOR FAULT LED Status = Not shown

CapacityLimitingBackhaulQoS With 2, 3 or 4 CS call (voice or video) in progress the AP has measured that the backhaul QoS parameters for that call have diminished below preset thresholds. This implies that the Femto AP will limit its CS call capacity, but can still maintain service to an acceptable level. This is cleared by the AP when it detects good QoS again or when all calls are released. Severity = Warning AP Status = WARNING LED Status = Not shown

EnterpriseNoMRTTrafficRxd Enterprise functionality is configured but the AP has not received any MRT traffic on the network, check the network configuration. The alarm will clear as soon as MRT traffic is received. Severity = Warning AP Status = WARNING LED Status = Not shown

Table 3: Device.X_UBIQUISYS_COM_ZAP.AM.CurrentAlarmL ist

The severity level of the alarms is not specified by the ZoneGate AP. In the TR-69 protocol, there is no alarm severity passed through. The interpretation of the alarm severity is left to the APMS. Ubiquisys in this document only recommends severity classification.



To allow the APMS user to view femtocell fault history there is also an alarm history list.

Parameter Description AlarmName The name of the alarm; please refer to Table 3 AlarmDateTime Time the alarm was raised or cleared AlarmActive Type of history entry (TRUE = active alarm, FALSE = inactive alarm)

Table 4: Device.X_UBIQUISYS_COM_ZAP.AM.AlarmHistory

To prevent too many alarm messages flooding the APMS from a large ZoneGate AP network, the APMS can restrict the frequency that the units can send alarm, by default 5 minutes. However, the ZoneGate AP can be configured to also restrict this frequency by defining a minimum time ReportingPeriod between alarms being sent. When the ZoneGate AP does send an alarm message it will contain a summary of the alarm transitions for that period with an upper limit defined by the length of the alarm history, defined on the AP by AlarmHistoryMaxLength. Additionally the APMS can specify that the ZoneGate AP only sends a subset of the alarms. This subset can be changed by the APMS to meet different needs, e.g. a small number of alarms for normal operation and an increasing amount for diagnostics.

Parameter Comment

ReportingPeriod The minimum time between alarms being sent in hours. 0 means an inform will be sent on every change.

Table 5: Device.X_UBIQUISYS_COM_ZAP.AM



3.1 Event Management

The event log list is stored in non-volatile memory and so will be maintained over a power off and initialization, even if the AP (U)SIM is changed.

• Information about call release. Each entry includes the following information:

o Time call is terminated o Reason for call failure if applicable

• Information about software errors detected by the AP. It shall include information that may help identify the reason for the error (this does not include low level debug information such as memory dumps etc).

• Information on when the AP initialises.

• Information on when a new SIM card is inserted. The information specifies the IMSI of the SIM card.

• Information on when AP completes listen mode. The information specifies the values of the new RF parameters (if changed).

The only controlled parameter the Operator can modify is the MaxLength which defines the maximum length of the log list.

Parameter Description MaxLength Max number of events in the event list. EventListNumberOfEntries Number of events in the event list. WriteIndex Index of the oldest entry in the event list

Table 6: Structure of alarm history in Device.X_UBIQUISYS_COM_ZAP.EventLog

Parameter Description EventDescription Description of the event EventDateTime Time and date that the event occurred

Table 7: Structure of alarm history in Device.X_UBIQUISYS_COM_ZAP.EventLog.EventList



3.1.1 AP Events – Cause and Action

The following table provides a list of AP events, their cause and where relevant the corrective action. The following list is not exhaustive:

G3 AP Event Cause Action Abnormal call release, reason code 4 - treloccomplete-expiry

Parameter t_reloc_complete (default value 10000ms) has been exceeded. A core network problem is preventing the relocation signalling from working correctly.

or RF conditions prevent successful UE handover and timers expire.

Report the issue to core network analysts. A local Wireshark trace will display the delta between HO requested and HO command.

or Measurement reports will show CRCI errors on target or cell update on source AP/Macro. The UE may cell update on either source or target depending on whether it lost the source or achieved sync on the target but could not establish radio links. A low RSCP report for the neighbour of < -97dBm, will require the source and target APs to be repositioned (ref UBS 43-41-022 ZoneGate AP Positioning for Enterprise or UBS-43-41-003 ZoneGate AP Parameter Guidelines for R2.9.x. A more typical reading is -70dBm

Abnormal call release, reason code 46 Loss of RF link either because of out of range, interference or congestion. Code 46 will be appended with one of the following: - L1 API Radio Link Failure", - RLC Unrecoverable Error", - Rel resource for dead ZID", - Unexp RRC Cnx Req", - Cell Update(RL Failure)", - Cell Update(RLC Unrecov err)",

This event occurs because the UE has moved out of the coverage area of the AP or has experienced a high level of interference from another UE or cell. If this event is being seen frequently on a particular AP then the customer may need to relocate it to an alternative location where it can provide better service to the UEs.

APMS initial connection failed AP Fail to connect to APMS. Check APMS is operational. Check AP is provisioned on APMS. Check AP username and password correctly configured.

AP service inhibited due to invalid cell status An SC to RRC request to change cell status (up or down) was not successful and that SC has protected the AP by inhibiting operation. I.e. specifically at this time for the following reasons: RRC could not Start Cell, RRC could not stop Cell or Stop request timed out.

Informational, unless AP is not working, in which case this indicates an area of internal failure. If cell parameters have been changed recently, it may indicate that they are now in conflict and should be corrected.

AP service inhibited due to hardware acceleration failure

IPSec acceleration failure. Reboot AP.



G3 AP Event Cause Action AP service inhibited due to invalid SIM status The USIM reader believes that there is no card in

the SIM slot Check the SIM card is the card issued by the Operator and correctly seated.

AP service inhibited due to loss of network Loss of LAN connectivity (cable, DSL reboot etc) or

The closure of the network connection due to updates from the CN.

Check all LAN connections or

None. An example of this event is when the CN sends a Register Update Downlink to the AP, causing the AP to fake a CN loss in order to take down the cell and apply new changes.

AP service inhibited due to periodic RF re-configuration

Periodic RF reconfigurations are attempted during the Least busy hour. This is recorded as shown.

None.

AP service inhibited due to software fault If an application process fails (software or modem) then service will be inhibited.

Service will be inhibited until the cell has been restarted. The AP stops new calls whilst removing others.

AP service inhibited due to unknown reason The initial cause of failure should be reported a few lines up in the eventlog. This only relates to procedures attempting to start while the cell is being taken down (e.g. loss of core network connection).

Check eventlog via APMS. Follow advice for prior failure cause.

AP shutdown due to software failing during start-up

Process failed to start up correctly. AP should recover automatically. If this event is being seen frequently on a particular AP check AP config on APMS.

AP shutdown due to unknown reason Normally a failure due to a crash of the kernel. AP should automatically recover. AP shutdown due to APMS provisioning AP has been rebooted at the request of the AP.

Normally due to config change. None

AP started AP powered on None Call failure due to congestion Too many users attempting call on AP. None. If this event is being seen frequently on a particular AP

consider reducing cell power in the downlink. Call failure due to no CN response Call failure due to the AP receiving no response to

service request message. Verify IMS gateway is fully operational.

Call failure due to service inhibited Only seen if invalid country or gateway changed validation is set to inhibit service and the alarm is active.

Check company policy on invalid country/gateway changed alarms.

Call setup refused due to insufficient processing resources

Processor overload threshold reached. To prevent call failures call redirected to macro.

None. If this event is being seen frequently on a particular AP consider reducing cell power in the downlink.

Chosen DL frequency <XYZ>GHz. Chosen primary scrambling code <XYZ>. Chosen max TX powers: DL <XYZ>dBm, UL <XYZ>dBm

Details the current Radio setting in use by AP. None.

Connection lost to Ethernet The AP has no electrical connection and cannot get an IP address.

This is probably a problem with the residential gateway.

Connection lost to Internet As stated. Check AP connection with ISP/Internet. Is the residential gateway connected to the Internet?



G3 AP Event Cause Action Connection lost to residential gateway The AP has an electrical connection but cannot get

an IP address. This is probably a problem with the residential gateway with no DHCP response to DHCP request.

Can be caused by connecting the power supply to the AP before the RJ45 cable. Power cycle AP (with RJ45 already connected). Check ADSL router is DHCP enabled, check connection with ADSL router.

Connection lost to SEGW/PDG (UE PDP context)

N/A applies to IMS.

Connection lost to APMS Unable to contact APMS after periodic inform timer expiry.

Check APMS operation.

Excessive UL interference UL noise exceeds defined parameters. None. If this event is being seen frequently on a particular AP consider reducing cell power in the downlink.

Gateway MAC address changed to <XYZ> DSL gateway MAC address has change since last power on.

None.

IPSec lockup occurred, AP connection state(unrecoverable)

Unrecoverable failure in the IPSec tunnel to SeGW. AP should automatically recover.

IPT starting FAST IPT, reason is entering new temperature range

Due to AP heating or cooling AP needs to recheck the RF environment.

None.

IPT starting FAST IPT, reason is K value out of date FAST IPT update required. None. IPT starting FAST IPT, reason is rate of temperature change limit exceeded

Internal temperature of AP has altered sufficiently to require a re-sync of the IPT clock.

None.

IPT starting FAST IPT, stored resolution worse than 250ppb

FAST IPT update required due to poor stored resolution.

None.

IPT stopping FAST IPT, run for database defined time

FAST IPT complete. None.

MO CS call failure due to no CN response Call failure due to the AP receiving no response to service request message.

Verify RAN gateway is fully operational.

MO CS call failure due to no CN response (Emergency call)

Call failure due to the AP receiving no response to service request message.


MO SMS failure due to no CN response Call failure due to the AP receiving no response to service request message.

Verify IMS gateway is fully operational.

Poor RF QoS due to AP interference High RSCP level on a reused scrambling code. RF performance has been degraded due to signal strength of neighbouring APs. Two units are located in same room within close proximity.

Suggest moving AP to another location.

Poor RF QoS due to macro interference RF performance has been degraded due to signal strength of neighbouring macro cells. Macro interference too high for an indoor environment. Unit

Suggest moving AP closer to the centre of the building.



G3 AP Event Cause Action located on open window frame or outdoors

Poor RF QoS due to unknown interference1 Wideband Interference or Inability to Decode any 3G Neighbour SIB or AP Neighbours Reporting Macro on Own Carrier

Suggest moving AP closer to the centre of the building. When poor RF QoS alarm is raised frequently on an AP, check the event logs for the root cause of the issue.

PS session failure due to no CN response Call failure due to the AP receiving no response to service request message.


Rolling location update detected, triggering periodic RF re-configuration

Repeated location update request from UEs. AP automatically recovers.

SEGW/PDG (UE CS registration) initial connection failed

IPSec tunnel establishment failure for CS registration or unable to contact SeGW when a UE attempts CS registration.

Verify RAN/IMS gateway is fully operational.

SEGW/PDG (UE PDP context) initial connection failed

PS call setup failure Verify PDG/IMS CN is fully operational, check PDP context address in AP, check UE settings..

SEGW/PDG (UE PS registration) initial connection failed

IPSec tunnel establishment failure for PS registration or unable to contact SeGW when a UE attempts CS registration.

Verify PDG/IMS CN is fully operational

Significant RF change (MRSC new macro on our freq/scr) detected

New macro cell detected by AP, triggering a re-sniff of RF environment.

None.

Significant RF change (new best carrier) detected

New best carrier detected (frequency) by AP, triggering a re-sniff of RF environment.

None.

Significant RF change (new strongest macro) detected

New strongest macro cell detected by AP, triggering a re-sniff of RF environment.

None.

Significant RF change (shared AP code freed) detected

AP power down detected by AP, triggering a re-sniff of RF environment.

None.

Significant RF change (slaving AP vanished) detected

AP used for clocking power down detected by AP, triggering a re-sniff of RF environment.

None.

SMS failure due to no CN response Call failure due to the AP receiving no response to service request message.


MMS failure due to no CN response Call failure due to the AP receiving no response to service request message.


UE registration failure due to congestion Too many users attempting registration on AP. None. If this event is being seen frequently on a particular AP consider reducing cell power in the downlink.

UE registration failure due to no CN response Registration failure due to the AP receiving no response to service request message.


1 Poor RF QoS events and alarms are discussed in more detail in document UBS-43-12-012 Safe Mode and Poor RF QoS



G3 AP Event Cause Action UE registration failure due to no CN response (Combined Attach)

Registration failure due to the AP receiving no response to service request message.


UE registration failure due to no CN response (LU)



UE registration failure due to no CN response (PS Attach)



UE registration failure due to no CN response (RAU)



UE registration failure due to no CN response (RAU, Combined)



UE registration failure due to service inhibited UE attempts to register while the AP is taking the cell out of service due to loss of connection to the CN.

None.

Updated max TX powers: DL <XYZ>dBm, UL <XYZ>dBm

For reference. None

Table 8 – AP Events



4 Glossary

For the purposes of the present document, the following abbreviations apply:

APMS AP Management Server CN Core Network

CS Circuit Switch CTT Customer Trace Tool

DLMM DownLink Monitor Mode

FAP Femtocell Access Point FR Factory Recovery

GW GateWay HSDPA High Speed Downlink Packet Access IMSI International Mobile Subscriber Identity LBR Load Balancing Router

MNO Mobile Network Operator MO Mobile Originated

MS Mobile Station

MTS Manufacturing Test System PS Packet Switch

QoS Quality of Service

RF Radio Frequency RRM Radio Resource Management

SEGW SEcurity GateWay SI Systems Integrator

SMS Short Message Service UE User Equipment UTRAN UMTS Terrestrial Radio Access Network

UMTS Universal Mobile Telecommunication System

ZAP ZoneGate Access Point ZAS ZoneGate Activation Server (formerly ZDS)



Annex A – Change History

Version Authors Date Status Comment

1.0 Simon Hughes 29 March 11 Released Updated from G2 to G3 (LED table), alarm parameters for SME added, event cause 46 expanded, added Glossary and amend reference to ZDS, now ZAS

1.1 Simon Hughes 08 Aug 11 Released LED profile tables updated to include IMS mode and optional profile 1. Amend tier 2 LED displays.

1.2 Simon Hughes 07 Oct 11 Released Added reason code 4, per request

Contact Us

Ubiquisys Ltd, Stella Building, Windmill Hill Business Park, Swindon, SN5 6NX, UK

Email: [email protected] Tel: +44 (0)2071 833400 Web site: www.ubiquisys.com

UBS-45!41!009 v1.2 AP Alarms and Events

Documents

Transcript of UBS-45!41!009 v1.2 AP Alarms and Events