Knowledge Sharing : ISHO PS Problem & Solution

Security Level

ISHO PS Problem & Solution

1. Fail ISHO PS mostly pegged in VS.IRATHO.FailOutPSUTRAN.NoReply or

Others, from DT it's shown as Timer T309 expiry
Check RNC setting T309 in UCONNMODETIMER, make sure has been set to 8
(=8s, maximum) (NPO)

Audit IuPS IPPATH against configuration in respective SGSN and/or

GGSN. In RNC, collect IPPATH with ITFT=IUPS (NPO, BO 3G, BO PS)
Check availability/quality of active IuPS IPPATH in RNC whether any Path
Fault alarm (NPO, BO 3G, BO TX, BO Datacom)
Make sure SGSN setting BYTE58 BIT4=1 (BO PS)
+++ USN/*MEID:8 MENAME:S1301b*/
2014-11-12 09:55:41+07:00
O&M #77
%%LST SOFTPARA: DT=BYTE, PARANUM=58;%%
RETCODE = 0 Operation succeeded
Query Soft Para
--------------Para type = Unsigned Char Type
Para index = 58
Para value = 0x08(8)
(Number of results = 1)

In case degradation triggered by massive MBRD/MBRU change in HLR

profile, tuning of SHIND in UTYPRABBASIC is advisable (found in Inner
CFGMML (execute command EXP INNERCFGMML:; and get the result via FTP RNC in
location /bam/version_b/ftp/export_cfgmml))

(NPO)

In case RNC and BSC belong to different SGSN, make sure SGSN
feature Enhanced Inter-RAU enabled (parameter ENINTERRAU is YES)
in respective SGSN (BO PS). Its always recommended to have RNC and
BSC connected to same SGSN to ensure good ISHO PS.
+++ USN/*MEID:8 MENAME:S1301b*/
2014-11-12 09:55:50+07:00
O&M #79
%%LST SOFTPARA: DT=BYTE_EX, PARANUM=44;%%
RETCODE = 0 Operation succeeded
Query Soft Para
--------------Para type = Extern Unsigned Char Type
2016-06-28

Huawei Proprietary - Restricted Distribution

Page1, Total2

Knowledge Sharing : ISHO PS Problem & Solution

Security Level

Para index = 44
Para value = 0xC0(192)
(Number of results = 1)

2. Fail ISHO PS mostly pegged in IRATHO.FailOutPSUTRAN.CfgUnsupp

Audit UEXT2GCELL and make sure information (LAC, RAC, CID, NCC,
BCC, RATCELLTYPE) align with actual 2G cell setting in respective BSC
(NPO)
3. Fail ISHO PS mostly pegged in IRATHO.FailOutPSUTRAN.PhyChFail
Collect ISHO PS per relation statistic (gcell) and sort based on Total ISHO
PS Fail (VS.IRATHO.AttOutPSUTRAN.GCell VS.IRATHO.SuccOutPSUTRAN.GCell) and perform detail investigation.
To coordinate with BSC owner for 2G analysis. (NPO)
As temporary solution, tuning CIOOFFSET in U2GNCELL for problematic
relation(s) might be taken (NPO)
In case analysis shown bad 2G RF quality as root cause, tuning
TARGETRATHTHD and/or TARGETRATR99PSTHD in
UCELLINTERRATHOCOV or UINTERRATHOCOV is advisable (NPO)
Fine tune of penalty setting (InterRatPhyChFailNum and/or
PenaltyTimeForPhyChFail in UCELLINTERRATHOCOV or
UINTERRATHOCOV) might be tried out (NPO)
4. Fail ISHO PS mostly pegged in VS.IRATHO.FailOutPSUTRAN.Other
Audit 2G LAC & RAC in Gn DNS to make sure all 2G LAC & RAC in

UEXT2GCELL defined (NPO, BO PS)

5. Reset SIGBVC in BSC side can also solve in some cases where the root

cause is Gb connection problem

2016-06-28

Huawei Proprietary - Restricted Distribution

Page2, Total2