microsoft powerpoint - 6-ohd906241 singlesdb maintenance and

Course Name

Confidential Information of Huawei.

No Spreading Without Permission 1

www.huawei.com

Copyright © 2011 Huawei Technologies Co., Ltd. All rights reserved.

SingleSDB Maintenance and Troubleshooting (GU HLR9820)


Objectives

� Upon completion of this course, you will be able to:

� Collect fault information on GU HLR9820;

� Locate service faults on GU HLR9820 and troubleshoot the

faults (including hardware faults, signaling faults, tele-

service faults, and supplementary service faults).

Page1

Course Name




Contents

1. Common GU Service Faults and Error Codes

2. Typical GU Service Faults Case

Page2


Contents



Page3

Course Name




Contents


1.1 Registration Faults

1.2 Calling Faults

1.3 SMS Faults

Page4


Common Error Codes Of Registration Fault

� Update Location Faults in CS Domain

Page5

Course Name




Common Error Code – roamingNotAllowed

� Fault Symptom

� The MS cannot be registered on the network.

� Information in the message tracing window indicates that the error

code ROAMING_NOT_ALLOWED is contained in the location update

message.

� Possible Causes

� The subscriber is in a region where roaming is not allowed.

� The subscriber has subscribed to the CAMEL services.

� The subscriber has subscribed to a certain service that is not supported

by the VLR currently serving the subscriber in the area.

Page6


Common Error Code – roamingNotAllowed

� Troubleshooting Steps

� 1. In the message tracing window, identify the peer NE that currently serves the subscriber

by checking the OPEN REQ message.

� 2. Run the LST HLRRR command to check whether the HLR imposes roaming restriction on

the VLR.

� 3. Run the LST RSZI command to check whether the subscriber has subscribed to the

regional roaming restriction services. If yes, run the LST RRTPL command to check the

regional roaming template.

� 4. Run the LST VLRTYP command to check the type of the VLR that currently serves the

subscriber.

� 5. Run the LST VSRR to check whether the subscriber has subscribed to the VLR roaming

restriction service. If yes, run the LST VSLIST command to check how the VLR is defined the

VLR roaming restriction template.

� 6. Check whether the subscriber has subscribed to the CAMEL services. If yes, check the

CAMEL template of the subscriber.

� 7. Run the LST DYNSUB command to check whether the parameter RRDTU is set to TRUE. If

yes, the roaming restriction is caused because the VLR does not support a certain service.

Page7

Course Name




Common Error Code in Voice Call Service Faults

Page8

Copyright © 2011 Huawei Technologies Co., Ltd. All rights reserved. Page9

MAP version

Common Error Code – DataMissing (1)


� 1. Open the SRI REQ message explanation file and check whether the MSISDN exists.

The corresponding cell is shown in the following figure (Yes = go to step 2. No = SRI

request message does not contain the calling number. This is not a fault of the HLR.):

� 2. Further check the message explanation file, and check whether the MAP version of

the request message is V3. The check method is as follows: Open the session part in

the message tracing, and find the ACN cell, as shown in the following figure (Yes = go

to step 3. No = go to step 4):

Course Name




Common Error Code – DataMissing (2)� Troubleshooting steps

� 3. Further check the message explanation file, and check whether the SRI request contains

the GT address of the MSC serving the calling party. The corresponding cell is shown in the

following figure (Yes = go to step 4. No = the SRI with MAP version of 3 does not contain

the calling GT address):

� 4. On the PGW Web LMT, run the LST MAPCONF command and check whether the queried

information contains "SRI-FIR = TRUE". (Yes = go to step 5. No = go to step 6)

� 5. Further check the message explanation file, and check whether the SRI request contains

the cells "Forwarding Reason" and "Basic Service Group" (Yes = go to step 6. No = OR

(Optimal Routing). The forwarding request does not contain the forwarding reason or basic

service group. This is not a fault of the HLR):

� 6. Contact Huawei technical support engineers for help.


Common Error Code – absentSubscriber

� Fault Symptom

� The subscriber cannot be called, and the announcement indicates that the subscriber has powered off or no

announcement is played.

� Possible Causes

� The subscriber has powered off.

� The location message is deleted, for example, by sending the Cancel message.


� 1. Create a message tracing task, and double-click the SRI RSP ERR message. The error code is displayed as

follows:

� 2. On the PGW Web LMT, run the LST DYNSUB command to check whether the VLR or MSC number in

subscriber dynamic data is empty. If yes, run the LST LOG command to query logs of the subscriber on the

PGW, and check whether the logs indicates that the SND CANCEL command is executed.

� 3. Run the LST DYNSUB command to query the value of MsPurgedForNonGprs. If it is set to TRUE, the

subscriber is purged. When the MS is powered off by the subscriber for some time, the VLR deletes data of

the subscriber and sends the PURGE MS message to the HLR.

Page11

Course Name




Common Error Code – callBarred� Fault Symptom

� The subscriber cannot be called, and the announcement indicates that incoming calls of the subscriber are restricted or services

of the subscriber are suspended.

� Possible Causes

� Services of the subscriber are suspended because the subscriber is delinquent or has applied for service suspension.

� The subscriber has subscribed to the BAIC service.

� The subscriber has subscribed to the CUG service. In this case, the subscriber cannot be called by non-members of the group.


� 1. Create a message tracing task, and double-click the SRI RSP ERR message. The error code is displayed as follows:

� 2. Run the LST SUB command to query whether the LOCK service and the SABLOCK service are provided for the subscriber.

� 3. Run the LST ODBDAT command to check the setting of the ODBIC service. If the parameter ODBIC is set to BICROAM, run the

LST DYNSUB to check the value of VLR Number Type and determine whether the subscriber is roaming internationally. Then, run

the LST CBAR command to check whether the subscriber has subscribed to the BAIC service.

� 4. Run the LST CUG command to query whether the subscriber has subscribed to the CUG service. If yes, determine how the

intra- or inter-CUG group calls are restricted, and whether the calling and called subscribers are CUG group members.

Page12


Common Error Code in the SMS Faults

Page13

Course Name




Common Error Code – UnknownSubscriber (1)

� Troubleshooting steps

� 1. On the PGW Web LMT, run the LST SUB command to check whether the MSISDN in

the SEND-ROUTING-INFO-FOR-SM request message is subscribed.

Yes = go to step 2

No = the number is not subscribed. It is not a fault.

� 2. On the PGW Web LMT, run the LST ISDN command to check the properties of the

MSISDN in the SEND-ROUTING-INFO-FOR-SM request message.

INDICATOR = MASTER indicates that the MSISDN is a master number. In this case, go to

step 5.

INDICATOR = AUXILIARY indicates that the MSISDN is an auxiliary number. In this case, go

to step 3.

� 3. On the PGW Web LMT, run the LST ALS command to check whether the MSISDN

subscriber registers the ALS service (ALS = PROV).

Yes = go to step 4

No = the auxiliary number of non-ALS service cannot receive short messages. It is not a

fault.

Page14


Common Error Code –UnknownSubscriber (2)� Troubleshooting steps

� On the PGW Web LMT, run the LST ALS command to check whether the MSISDN is

the LINE2NUM number of the ALS service. For example, the result is displayed as

shown in the following figure. Check whether the MSISDN is consistent with the

LINE2NUM value.

Yes = go to step 5

No = the auxiliary number of non-ALS service cannot receive short messages. It is not a

fault.

� Contact Huawei technical support engineers for help.

Page15

Course Name




Contents



Page16


Contents


2.1 Subscriber Authentication Fails

2.2 Subscribers Fail to Connect to the GPRS Network

2.3 The GPRS Network Speed Is Low or the GPRS Service Cannot

Be Used

2.4 A Subscriber Fails to Receive Calls

2.5 VPN Group Members Cannot Call or Be Called by Each Other

Using Short Numbers

2.6 A Subscriber Fails to Register the Call Forwarding Service

2.7 The HLR Does Not Deliver the CRBT Service Code

2.8 The USSD Service Cannot Be Used

2.9 Traffic Measurement Indicators Are Poor After Cutover

Page17

Course Name




1. Subscriber Authentication Fails

� Fault Symptom

� During the running of the system, a large number of subscribers fails to be

authenticated. As a result, the location update fails and the MS cannot be registered

on the network.

� Possible Causes

� The GT data is incorrectly configured on the FE side. As a result, messages cannot be

sent to or by the HLR.

� The subscriber is not defined in the HLR.

� Authentication parameters are incorrectly configured.

� Troubleshooting Steps:

� 1. Create a message tracing task, and check whether location update messages can be

received by the HLR or sent to the MSC or VLR. If messages cannot be sent or received,

the cause of the fault is that data on the FE side is incorrectly configured. Modify the

data configuration based on the number segment of the subscriber contained in the

message.

Page18


1. Subscriber Authentication Fails (Cont.)

� 2. If information in the message tracing window indicates that the

subscriber is not defined, data of the subscriber is lost, or the data

value is unexpected, run the LST SUB to query the status of the

subscriber.

� 3. If information in the message tracing window indicates that the HLR

has returned the authentication vectors in triplets or quintets, but a

report is received indicating that the authentication has failed, the

cause of the fault is that the authentication parameters configured on

the MS are different from those configured on the HLR.

� In this case, run the LST KI command to query subscriber

authentication parameters.

� For USIM card authentication failure, run the LST MAPSERV

command to query authentication parameters.

Page19

Course Name




2. Subscribers Fail to Connect to the GPRS Network� Fault Symptom

� The location update of the subscriber fails when the subscriber roams to

another region.

� Possible Causes

� The HLR GT translation is incorrectly configured on the visited SGSN.

� The subscriber has subscribed to the roaming restriction services or the

lock service.

� The HLR global data is customized.


� 1. Create a message tracing task for the subscriber, and view messages in

the location update procedure. If the ISD message is not responded, check

whether the HLR GT translation is incorrectly configured on the local SGSN.

If yes, check whether the HLR GT translation is incorrectly configured on

the visited SGSN.

Page20


2. Subscribers Fail to Connect to the GPRS Network (Cont.)

� 2. On the PGW Web LMT, run the LST DYNSUB command to check subscriber dynamic

data for parameters that may be set to restrict the roaming of the subscriber, namely,

SgsnAreaRoamingRestrict, RoamingRestrictInSgsnDueToUnsupportedFeature, and

ODBarredForUnsupportedCamelForGprs.

� 3. On the PGW Web LMT, check the subscription data of the subscriber and global

data configuration. The following data needs to be checked:

� The roaming restriction state (by running the LST HLRRR command)

� The regional roaming service (by running the LST RSZI command)

� The SGSN type (by running the LST SGSNTYP command)

� The VLR/SGSN roaming restrictions (by running the LST VSRR command)

� The alternative processing mode for unsupported services (by running the LST

NONSUPHND command)

� The ODB service subscription state (by running the LST ODBDAT command)

� The GPRS lock service subscription state (by running the LST LCK command)

� The GPRS subscription state (by running the LST GPRS command)

Page21

Course Name




3. The GPRS Network Speed Is Low or the GPRS Service Cannot Be Used� Fault Symptom

� GPRS The GPRS network speed is low, or the GPRS service cannot be

used.

� Possible Causes

� The GPRS location update fails.

� The QoS parameters are set incorrectly.

� The parameter 2G/3G Qos mapping is set to TRUE, causing change of

the QoS parameter distributed by the HLR.


� 1. The GPRS location update failure leads to the unavailability of the

GPRS service. Create a message tracing task for the subscriber to

check whether the GPRS-attach is normal.

Page22


3. The GPRS Network Speed Is Low or the GPRS Service Cannot Be Used (Cont.)

� 2. Run the LST GPRS command to check the configuration of QoS

parameters. If the QoS parameters are not compatible with the live

GPRS network parameters, the GPRS service quality of the

subscriber is compromised.

� 3. If the parameter 2G/3G Qos mapping is set to TRUE and the

SGSN supports the enhanced QoS, the HLR converts 3G QoS

parameters into 2G QoS parameters for distribution. Therefore,

you are advised to set 2G/3G Qos mapping to FALSE. For details on

how the HLR performs data conversion, see the attachment.

Page23

Course Name




4. A Subscriber Fails to Receive Calls

� Fault Symptom

� The subscriber can originate calls, but cannot receive calls.

� Possible Cause

� The subscriber is not authorized to receive calls.

� The CAMEL criteria causes the subscriber calls to be locked, or data exception occurs in the

CAMEL service center.

� The value of the parameter Default call process is incorrectly configured.


� 1. Run the LST LCK, LST CBAR, and LST ODBDAT commands to check whether the subscriber

is authorized to receive calls.

� 2. Run the LST CSI command to query the O-CSI and T-CSI templates of the subscriber, and

then run the LST TCSITPL and LST OCSITPL commands to query template data. Check

whether the parameter ReturnBAIC is correctly configured.

� 3. Run the LST SUB command to check whether the parameter Default call process is set to

TS11.

Page24


5. VPN Group Members Cannot Call or Be Called by Each Other Using Short Numbers

� Fault Symptom

� When a VPN group member dials the short number of another VPN group member,

calls cannot be connected and the announcement indicates that the number does not

exist.

� Possible Causes

� The CAMEL template of the subscriber is incorrectly configured.

� Functional data in the CAMEL services is incorrectly configured.


� 1. On the PGW Web LMT, run the LST OCSI or LST TCSI commands to query data in

the CAMEL template of the subscriber.

� 2. Create a message tracing task for the subscriber, and then make the subscriber

restart the MS. View the location update message, and check whether the O-CSI or T-

CSI of the subscriber is inserted into the VLR.

� 3. Run the LST MAPCONF command to check whether the parameter CSIRESTRICTION

is set to TRUE, and then run the LST CSIR to check the CSI restriction list.

Page25

Course Name




6. A Subscriber Fails to Register the Call Forwarding Service � Symptom

� The subscriber cannot register the forwarded-to number.

� Possible Causes

� The call forwarding data is set incorrectly.

� The subscriber has no call forwarding authority.

� The subscriber has no registration authority.

� Fault locating

� 1. Check whether the call forwarding data is set correctly.

� Check the forwarded-to number analysis table (LST CALLEDNA), IMSI area code

table (LST IMSIAR), forwarded-to number prohibition table (LST FRFWDNO),

blacklist and white list (SET BWFTN), and domestic area code table (LST DAREA).

The call forwarding area restriction may cause the call forwarding registration to

fail. Run the LST MAPSERV command to check the settings of call forwarding

area restriction and number structure restriction.


6. A Subscriber Fails to Register the Call Forwarding Service (Cont.)

� 2. Check whether the subscriber has call forwarding authority.

� If the lock is enabled or the CB and ODB services have conflicts, the

call forwarding registration fails. The OFA is also a method to

restrict the call forwarding. Run the LST CFALL command to check

whether the subscriber has the OFA template restriction, and then

run the LST OFATPL command to check whether the forwarded-to

number registered by the subscriber is in the restriction list.

� 3. Check whether the subscriber has call forwarding

registration authority.

� Run the MOD ODBRCF command to set the call forwarding

registration authority of the subscriber.

Course Name




7. The HLR Does Not Deliver the CRBT Service Code

� Symptom

� The subscribers of China Mobile cannot trigger the Colorful Ring Back Tone

(CRBT) service. The message tracing shows that the HLR does not deliver

the CRBT service code.

� Possible Causes

� The service registration is faulty.

� The CRBT service settings are incorrect.


� 1. Check whether the subscriber registers the CRBT service.

� Run the LST SS command to confirm that the plmn-specificSS registered by the

subscriber is the CRBT service code of the current network (plmn-specificSS-1 is

corresponding to 241, and plmn-specificSS-F is corresponding to 255).

� Generally, the plmn-specificSS is used as the CRBT service code on the current

networks. You can also run the MOD RBT command to register the CRBT service

for the subscriber.


7. The HLR Does Not Deliver the CRBT Service Code (Cont.)

� 2. Check the CRBT service scheme on the HLR.

� 3. The HLR supports multiple CRBT schemes. When the CRBT service of the subscriber

cannot be triggered, firstly check the CRBT scheme on the current network, and then check

the data configuration of the HLR. The parameters related to the CRBT in the LST MAPSERV

command are as follows:

� ISD: The service code set by this parameter is delivered only in the subscriber data insertion flow.

Generally, the calling party CRBT uses this scheme.

� SRI_MSRN: The service code set by this parameter is delivered only when the roaming number is

returned.

� SRI_MSRNCF: The service code set by this parameter is delivered when the roaming number is returned

or when the forwarded-to number is returned, but the CRBT must be activated (run the LST DYNSUB

command to query the activation state).

� PLMNSPECSSENE: This parameter is only meaningful for plmn-specificSS-E. In the entire network scheme,

it triggers the CRBT service only when the roaming number is returned. When it is set to GMSC, the

CRBT is triggered for each SRI response.

� CRBT_PLMNSS: The service code set by this parameter is delivered when the roaming number is

returned. Different from SRI_MSRN, this parameter requires that the private cell to be contained in the

SRI message.

� 4. For the transition network scheme, you need to run the LST SELIST command to check

the supporting capability of the GMSC serving the calling party and the CRBT call continuity

platform for selection. If the connecting GMSC is not configured, the CRBT triggering may

fail.

Course Name




8. The USSD Service Cannot Be Used� Fault Symptom

� When the subscriber sends the USSD service code *124*5978301100#, the message

Supplementary Service Error is sent to the MS.

� Possible Causes

� The system does not support the USSD service.

� The USSD service code is not configured.

� The subscriber is not authorized to operate the USSD service on the MS.

� The customization of the CAMEL service has caused the fault.


� 1. In the MML Command - GU-HLR-FE window, run the DSP LICENSE command to

check whether USSD Function is 1. On the PGW Web LMT, run the LST MAPCONF

command to check whether USSDSUPP is set to TRUE.

Page30


8. The USSD Service Cannot Be Used (Cont.)

� 2. Run the LST USSDDAT and LST UCSITPL commands to check the

USSD service code configured on the HLR.

� 3. Run the LST SUB command to check whether the subscriber has

subscribed to the CB or ODBSS services. On the PGW Web LMT,

run the LST MAPSERV and LST SS commands to check the value of

USSD_BAR and the supplementary services provided for the

subscriber, and then check whether the value of plmn-specificSS-X

is PROV.

� 4. The value of AllowLocationUpdateWithODBBAOC set during the

O-CSI service customization makes the HLR delivers the ODBSS

service during location update procedure. As a result, the

subscriber cannot use the USSD services.

Page31

Course Name




9. Traffic Measurement Indicators Are Poor After Cutover

� Fault Symptom

� During the system monitoring period after the cutover is complete, the performance

measurement result shows that a large number of call losses are generated.

� ALM-1005 Board CPU Overload, ALM-12001 Node Heartbeat Timed Out, or ALM-

3228 Signaling Point Congested may be generated on the alarm console.

� Possible Cause

� The GT routing data of subscribers migrated to the new site is not configured on the

FE.

� Global MAP service data is not configured.

� The system has started flow control.


� Create a message tracing task for the C and D interfaces. If a U_ABORT message is

traced, an timeout error has occurred in the service. Check data configuration on the

FE of the HLR.

Page32


9. Traffic Measurement Indicators Are Poor After Cutover (Cont.)

� Check the HLR global data configuration.

� In the MML Command - GU-HLR-FE window, run the LST OFI

command to check the setting of the parameter HLRGT. On the

PGW Web LMT, run the LST INTEROFF command to query the

setting of the parameter HLRSN.

� Determine whether subscribers whose calls are lost are defined

in the same HLR. If yes, determine whether the HLR cutover or

upgrade is in process. If no such operations are being

performed, check the signaling data configuration on the HLR

for communication between the HLR and other NEs.

� Check the alarms and determine whether the system has

started flow control.

Page33

Course Name




Summary

� In this course we discuss about Common GU Service

Faults, Error Codes and Typical GU Service Faults Case.

Page34


Appendix - Common Operation for GU Service Management

� Handling Incorrect GT Configuration Problem

� Query the Static and Dynamic Data of Subscribers

� Checking Data Consistency

� Checking the CLIP Service

� Checking the CLIR Service

� Checking the Call Barring Service

� Checking the Roaming Restriction information

� The service problem is often caused by the incorrect configuration

of the service. Checking the service configuration is a useful

method in the trouble shooting.

Page35

Course Name




Handling Incorrect GT Configuration Problem� Symptom

� All the CCU modules on the SCCP, TCAP, and MAP layers are displayed

in red on the service panel of the GU-HLR-FE when you check the

service panel

� Possible Causes

� The GT configuration of the peer NEs such as the STP and MSC is

incorrectly configured on the HLR.

� Emergency handling

� Run the LST SCCPGT command to check whether the GTs of the HLR

and the peer NE are correct. If not, change the GTs to correct ones.

� Run the TST SCCPGT command to check the GT configuration is

correct.

� Synchronize the data from the OMU to the FEU. Page36


Query the Static and Dynamic Data of Subscribers

� Scenario

� When the service faults (such as call forwarding faults) occur, the called subscriber cannot

be connected. To locate the faults of a single subscriber, such as faults related to the GPRS

service, service subscription, and provisioning system commands, you need to check the

static information of the subscriber.

Page37

Course Name




Checking Data Consistency

� Scenario

� This method is used to handle call service failure and service provisioning

failure caused by inconsistency of subscriber data between the master and

slave DRUs/DSUs/DRU clusters/DSU clusters.

Page38


Checking the CLIP Service

� Scenario

� The Calling Line Identification Presentation (CLIP) service is a supplementary service

for the called mobile subscribers. When a mobile subscriber receives a call, the

network displays the number of the calling party to the called party. For example, if

mobile subscriber A registers the service, when subscriber B calls A, the MS of

subscriber A rings and displays the number of subscriber B on the screen.

� Run the following command to check the CLIP service of a subscriber:

LST CLIP: ISDN=" ";

The result is displayed as follows:

%%LST CLIP: ISDN="8615558905407";%%

SUCCESS0001: operation successful

IMSI = 460017705400007

ISDN = 8615558905407

STATUS = PROV----PROV indicates that the CLIP service is provided.

OVERRIDE = FALSE

Course Name




Checking the CLIR Service

� Application Scenario

� The Calling Line Identification Restriction (CLIR) service is a supplementary service for

the calling mobile subscribers. When a mobile subscriber makes a call, the network

does not display the number of the calling party to the called party. For example, if

subscriber A registers the CLIR service, when subscriber A calls subscriber B, if

subscriber B is connected successfully, the MS of subscriber B rings but does not

display the number of subscriber A.

� Run the following command to check the CLIR service of a subscriber: LST CLIR:

ISDN=" ";

� The result is displayed as follows:

%%LST CLIR: ISDN="8615558905407";%%


IMSI = 460017705400007

ISDN = 8615558905407

STATUS = NOTPROV---- NOTPROV indicate s that the CLIR service is not

provided.


Checking the Call Barring Service

� Application Scenario

� This operation is used to query the following information of the call barring service: control

right information, call barring service type, applied basic service group, and the registration

and activation information of different call barring services. For example, you can run the

command to query whether a subscriber has the authority to make an outgoing

international call. Note that the operation is effective only when the service state is ACT

(that is, the activated state).

� Run the following command to check the call barring service of a subscriber:

� LST CBAR: ISDN=" ", BSG=ALL;

� The result is displayed as follows:

%%LST CBAR: ISDN="8615558905407";%%


IMSI = 460017705400007

ISDN = 8615558905407

CBCOU = OPERATOR

BAOC (Bar all outgoing calls.)

ALL BS = PROV Indicates that all outgoing calls can be barred, but the

setting is not activated yet

Course Name




Checking the Roaming Restriction information� Application Scenario

� If a subscriber complaints that he/she cannot make a call, you can run the following

command to query the roaming restriction of the subscriber: LST VSRR: ISDN=" ",

TPLTYPE=VLR;

� The query result is displayed as follows:

%%LST VSRR: ISDN="8615558905407", TPLTYPE=VLR;%%


IMSI = 460017705400007

ISDN = 8615558905407

VLRTPLID = 3--------------------It is the roaming restriction information of

the subscriber. In this example, value 3 means that roaming in the country is

permitted, value 2 means that roaming in the province is permitted, and value 1

means that the subscriber can make local calls only. The VLRTPLID parameter must be

defined through the ADD VSLIST command.

Thank youwww.huawei.com

microsoft powerpoint - 6-ohd906241 singlesdb maintenance and

Documents

huawei technologies

common gu service faults

supplementary service

teleservice faults

hardware faults

certain service

fault information

lst rrtpl command