Scribd
Upload
102 views3 pages

Cara Cek Problems GB Interface

The document provides guidance on collecting information when encountering problems with the Gb interface between a BSC and SGSN. The key information to collect includes: release levels of the BSC and PCU software; configuration of the Gb interface; monitoring and logs from the PCU; and alarms and monitoring from the BSC. Collecting this technical information simultaneously during an occurrence can help identify and resolve issues with the Gb interface.

Uploaded by

Sloan Ian Ariff
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
102 views3 pages

Cara Cek Problems GB Interface

The document provides guidance on collecting information when encountering problems with the Gb interface between a BSC and SGSN. The key information to collect includes: release levels of the BSC and PCU software; configuration of the Gb interface; monitoring and logs from the PCU; and alarms and monitoring from the BSC. Collecting this technical information simultaneously during an occurrence can help identify and resolve issues with the Gb interface.

Uploaded by

Sloan Ian Ariff
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 3

Reporting problems with Gb interface (PCU1)

When encountering problems that are related to the Gb interface (PCU1), you should collect the
following information:

BSC release and SW level with the command:


ZWQO:CR;

BTS version and SW release


PCU software version GBHTORSX.IMG in use with the MML command:
ZDPY:BCSU,<BCSU_index>:PCU,<PCU_index>:PID,GBH;

the configuration in the Gb interface (FR/IP and NS layers) with the commands of the FU
and FX command groups
Frame Relay: FR bearer channel access rate with the command:
ZFUI;

Frame Relay: committed information rate for NS-VC (BSC/SGSN), NSVC parameters
and attached BTSs of the NSEIs with the commands:
ZFXO:BCSU=0&&<max_BCSU_index>:BTS;

Gb over IP: NS-VL parameters of the used NSEI with the command:
ZFXI:NSEI=<NSEI_index>;

Gb over IP: Attached BTSs of the NSEIs per created PSEIs with the command:
ZFXL:PSEI=0&&99:BTS;

Gb over IP: Network interface data of the BCSUs with the command:
ZQRI:BCSU;

used Routing Area(s) with the command:


ZEBP;

active alarms in BSC with the commands:


ZAHO;
ZEOL;

alarm history from the current day in the BSC with the command:
ZAHP:<date,time>;

Gb interface monitoring with a network analyser taken simultaneously with the PCU logs
when the fault occurs
PCU log writings from the faulty BCSU:
From OMU service terminal (ZDDS;), go to the service terminal of PCU with the
command:
ZRS:3<BCSU_index>,<PCU_terminal_index+1>0BF
or
ZRS:3<BCSU_index>,<PCU_terminal_index+1>0BE
Check the correct PCU terminal index from the Frame Relay configuration printout
ZFUI;.
BEARER BEARER
BEARER CHANNEL EXT TIME
ID
NAME
RATE (KBIT/S) PCM SLOTS UNIT
TERM FUNCT
------ -------- -------------- ---- ------ ------ ---- ----0 SGSN1
128
41
1- 2 BCSU-7
4
0

Gb over IP:
ZFXL:PSEI=<PSEI_index>:ALL;
PACKET SERVICE ENTITY DATA
PSE-01
======
ATTACHED NSE(S) TO PSE:
NSEI
--------------------------------------------02000
ATTACHED PCU(S) TO PSE:
PCU
ID
--00

BCSU
INDEX
----00

PCU
INDEX
----03

ATTACHED BTS(S) TO PSE:


PCU ID-00

BCSU-00

PCU-03

BTS NAME
--------------------------------------------018

PCU service terminal commands:


o
o
o
o

LGLVST GBH 128


LGLVST FRH 128
clog -s -a
exit (Logout from the PCU service terminal)
Additional information:
SGSN manufacturer, SW and CD level

For an overview, see Overview of BSC Problem Reporting.

You might also like