LinDX PCUM & ETME/A

Service Terminal
AirScale Cloud BSC 19 FP3 Troubleshooting
Nokia Internals course | RN23930-V-19F3

1 18/07/2019 © Nokia 2019

1 © 2019 Nokia
Copyright and confidentiality
The contents of this document are proprietary and
confidential property of Nokia. This document is provided
subject to confidentiality obligations of the applicable
agreement(s).
This document is intended for use of Nokia customers and
collaborators only for the purpose for which this document
is submitted by Nokia. No part of this document may be
reproduced or made available to the public or to any third
party in any form or means without the prior written
permission of Nokia. This document is to be used by
properly trained professional personnel. Any use of the
contents in this document is limited strictly to the use(s)
specifically created in the applicable agreement(s) under
which the document is submitted. The user of this document
may voluntarily provide suggestions, comments or other
feedback to Nokia in respect of the contents of this
document ("Feedback"). Such Feedback may be used in
Nokia products and related specifications or other
2 © 2019 Nokia
documentation. Accordingly, if the user of this document BE RESPONSIBLE IN ANY EVENT FOR ERRORS IN THIS
gives Nokia feedback on the contents of this document, DOCUMENT or for any loss of data or income or any
Nokia may freely use, disclose, reproduce, license, distribute special, incidental, consequential, indirect or direct damages
and otherwise commercialize the feedback in any Nokia howsoever caused, that might arise from the use of this
product, technology, service, specification or other document or any contents of this document.
documentation.
This document and the product(s) it describes are protected
Nokia operates a policy of ongoing development. Nokia by copyright according to the applicable laws.
reserves the right to make changes and improvements to
any of the products and/or services described in this Nokia is a registered trademark of Nokia Corporation. Other
document or withdraw this document at any time without product and company names mentioned herein may be
prior notice. trademarks or trade names of their
respective owners.
The contents of this document are provided "as is". Except
as required by applicable law, no warranties of any kind,
either express or implied, including, but not limited to, the
implied warranties of merchantability and fitness for a
particular purpose, are made in relation to the accuracy,
reliability or contents of this document. Nokia SHALL NOT
Objectives

• After studying this module the trainee will be able to:

• Practice connecting to LinDX Service Terminal units
• Use important commands in PCUM and ETME/A service terminal
• Inspect packet switched traffic in PCUM
• Practice handling PCUM log files

4 © Nokia 2019 RN23930

 Legend
Service terminal Interfaces in asBSC
Nokia Radio Cloud Infrastructure for Radio (NCIR) Nokia SW

Nokia LinDX SW
Two types VM in AirScaleBSC: Virtual Machines Virtual Machines Orchestrator 3rd party SW
1: DMX unit
2: LinDX unit Controller application Controller application
& platform SW & platform SW NetAct

DMX Linux CAM

• Based on Wind River Titanium server

SW, based on Wind

OpenStack

Radio Cloud Host

• OpenStack services & agents Accelerated HA OpenStack services

River Titanium
• Accelerated vSwitch vSwitch middleware agents
• Telco grade HA middleware HA middleware

• Based on Wind River Linux

• Libvirt + KVM with real-time patches
Hypervisor libvirt QEMU KVM DRBD or Ceph
Linux SW + libraries Linux SW + libraries
kernel kernel
Linux host OS Linux host OS

• Nokia IT servers IT compute node HW IT controller HW

Controller / storage
Compute node node
5 06/03/2023
Confidential
 Introduction to LinDX Service Terminal
• LinDX service terminal is a service terminal session which can be enabled from a Lin DX computer unit for system monitoring as
well as fault investigation
• A LinDX computer unit is functional unit, configured as a Virtual Machine in NCIR with PCUM/ETME/ETMA flavors and running
SW based on Nokia Linux platform SW.
• Local, connect directly to a computer unit through the NCIR suite using the console
Compute node
• Remote, connect from MML session or Service Terminal session of another computer unit Compute node
Compute node
Compute node
REMOTE linDX SERVICE TERMINAL SESSIONS Compute node
MML Connection Compute node
• Commands VM-PCUM VM-ETME VM-ETMA Compute node
Compute node
• ZDDS:<unit>; Remote Service Terminal session Compute node
DX Service Terminal BE (Ositus) Compute-17 (hosting OMU VM) Compute node
Storage node
• ZRS:<MB address>; BF (Ositus) Controller node
MB Addresses:: ETME 0(60), ETME1(61), PCUM 0(80), Data plane switch
Data plane switch
PCUM 1(81)PCUM, ETMA 0(6D), ETMA1(6E) HW mgmt. switch (opt)
Cable management
WORKING STATE OF UNITS
UNIT PHYS STATE INFO
Console Service Terminal Cable management
Cable management
ETME-0 0060 WO-EX -
session (local) only for M-plane switch
ETME-1 0061 SP-EX IDLE
startup monitoring M- plane switch
Controller node
PCUM-0 0080 WO-EX - Storage node
PCUM-1 0081 SP-EX IDLE Compute node
Compute node
ETMA-0 006D WO-EX - NCIR suite session Controller – 0 (floating ip) Compute node
ETMA-1 006E WO-EX - Compute node
Compute node
Compute node
LOCAL LINDX SERVICE TERMINAL SESSION Compute node
NCIR SUITE Compute node
Compute node
Project>Compute>Instances>Console Compute node

6 © 2019 Nokia
LinDX Service Terminal > Local Connectivity to Instances (VMs)
Console Connectivity for NCIR Project Users
NCIR Project users can connect locally to the LinDX Service Terminal Console from the following menu:
Project>Compute>Instances>Console

For startup-monitoring

7 © 2019 Nokia
 LinDX Service Terminal Virtual Machines
VM Distribution in Compute Nodes
• The physical location/configuration of LinDX
Service Terminal VM’s varies in the NCIR as the
VM’s are distributed in different compute nodes
for HW redundancy purposes. MCMU 0 RRMU 0 Compute
OMU node
BCXU #1 PCUM

• AirScale BSC reference deployments are

dimensioned with one extra compute node to MCMU 1 RRMU 1 Compute
BCXU node
ETME #2 ETME
allow hardware maintenance operations without
VNF service impact.
• E.g. RD1_BSC 1100 is defined with 5 compute nodes
ETME Compute
BCXU node
ETMA #3 PCUM

by default.
During Deployment: PCUM Compute
PCUM node #4
ETMA

• ETME’s, PCUM’s, ETMA’s are allocated to compute

nodes dynamically, balancing the resource usage Compute node #5 (Failover)

8 © 2019 Nokia RN23890

 LinDX Service Terminal
AirScale BSC LinDX Virtual Machines
LinDX units AirScale BSC
ZDDS:ETME,0; → 0060-$
OMU-VM
ZDDS:ETME,1; → 0061-$ W6I::;
ZDDS:ETME,2; → 0062-$ 00
INTERNAL CONNECTIVITY OF UNITS
ZDDS:ETMA,0; → 006D-$
ZDDS:ETMA,1; → 006E-$ UNIT STATE EL0 EL1 EMB0 EMB1
MCMU 0-VM MCMU 1-VM
ZDDS:PCUM,0; → 0080-$
---------------------------------------------------- 04 05
OMU WO-EX UP UP UP UP
ZDDS:PCUM,1; → 0081-$ MCMU-0 WO-EX UP UP UP UP
ZDDS:PCUM,2; → 0082-$ MCMU-1 SP-EX UP UP UP UP
ETME-0 WO-EX UP UP UP UP
ZDDS:PCUM,3; → 0083-$ ETME 0-VM 61 ETME 1-VM
ETME-1 SP-EX UP UP UP UP 60
PCUM-0 WO-EX UP UP UP UP
ASBSC asBSC1 PCUM-1 SP-EX UP UP UP UP EMB 1
2019-10-01 11:47:06 BCXU-0 WO-EX UP UP UP UP EMB 0
BCXU-1 WO-EX UP UP UP UP ETMA 0-VM ETMA 1-VM
WORKING STATE OF UNITS BCXU-2 SP-EX UP UP UP UP 6D 6E
UNIT PHYS STATE INFO ETMA-0 WO-EX UP UP UP UP
OMU 0000 WO-EX - ETMA-1 WO-EX UP UP UP UP
MCMU-0 0004 WO-EX - RRMU-0 WO-EX UP UP UP UP
MCMU-1 0005 SP-EX - RRMU-1 SP-EX UP UP UP UP PCUM 0-VM PCUM 1-VM
ETME-0 0060 WO-EX -
80 81
ETME-1 0061 SP-EX IDLE COMMAND EXECUTED
PCUM-0 0080 WO-EX -
PCUM-1 0081 SP-EX IDLE
BCXU-0 0043 WO-EX -
BCXU-1 0044 WO-EX -
BCXU-2 0045 SP-EX IDLE
ETMA-0 006D WO-EX -
ETMA-1 006E WO-EX - EMB IPs are hardcoded in platform software.
RRMU-0 0058 WO-EX -
RRMU-1 0059 SP-EX - EMB0 10.20.0.0/21
EMB-0 WO-EX -
EMB1 10.30.0.0/21
EMB-1 SP-EX -

9 © 2019 Nokia RN23890

Remote LinDX Service Terminal Connectivity in asBSC

Remote Connection from MML

Unit name MB
• MML command to open a remote Service Terminal session on a computer unit as Address
follows
ETME 0 60
ZDDS:<unit>,<index>;
ETME 1 61
• Example:
ETME 2 62
ZDDS:PCUM,0; to open service terminal session on OMU
ETMA 0 6D
Remote Connection from DMX Service Terminal
ETMA 1 6E
• Service Terminal command on DMX units to open remote Service Terminal session on
PCUM 0 80
another computer unit
ZRS:<compt unit physical address> PCUM 1 81

• Example: PCUM 2 82

ZRS:80; to open service terminal session on PCUM 0 (physical address 0080 H) PCUM 3 83

Remote Connections are supported by OSITUS processes BE & BF . (Equivalent to two

maximum remote connections)

10 © 2019 Nokia
Introdoction to LinDX Service Terminal for asBSC
• LinDx Service Terminal is a visual display terminal connected to PCUM via a serial/Ethernet interface
• LinDX is hosted in ETMEs, ETMAs, PCUMs
• Specialist tool used in monitoring of the system as well as in fault investigations and fault analysis
• The operator can start a service terminal session via an Ethernet Interface using the Telnet protocol or via the
MML terminal by establishing a remote service terminal session using the appropriate MML command
• PCUM Service Terminal functionality is based on BASH shell running on the Linux OS
• Cores will not have a direct Service Terminal Interface (Commands to the Simple Executive SW of the PCU will be
sent via the Linux Core)

PCUSIG

BSC MML / DX Service

Terminal
PCUM

Telnet Service
Terminal
AS BSC

11 © 2019 Nokia
 PCU Legacy Hardware vs asBSC PCUM
• PCUM connectivity :
• 550 BCFs per one PCUM VM
AirScale BSC PCUM-VM • 550 Cells per one PCUM VM
• 550 TRXs per one PCUM VM
• PCUM-A = Octeon I (plus) > BOC-A plug in unit for mcBSC • Throughput : 50 + 50 Mbit/s (UL+DL) per one
PCUM VM with all MCS9 calls
• PCUM-B = Octeon II > BMPP2 plug in unit for mcBSC • 1640 Channels (MCS1 RTSL) per one PCUM VM
• PCU2_E = 2 nd generation PCU version E for FlexiBSC • 890 MCS9 RTSLs per one PCUM VM

Parameter / PCU type PCU2-E PCUM-A PCUM-B

Processor family C6482 (Himalaya) OCTEON Plus OCTEON II

#DSPs per PCU / #Abis channels 6 / 172 8 / 128 20 / 128

per DSP
#Abis channels 1024 1024 2560*
#BTS / #BCF objects 384 550 550
#EGPRS cells (#SEG) 256 550 550
#GPRS / #EGPRS TRX 1024 / 720 550 / 550 550 / 550
Gb throughput 8 Mbps 8 Mbps 20 Mbps
12 © 2019 Nokia
PCUM/ETME/ETMA from Octeon to Intel - Differences
Item Octeon in mcBSC Intel in AS-BSC

Cores 32 cores (BMPP2) 14 cores in each socket (NDSC17), max 12 for VNF use, double with
hyperthreading

Endianness Big-endian Little-endian

Timer Dedicated timer module in HW. Timer expiry is unaffected by Timer management is done in SW. Timer works in poll mode. For accurate
current processing load. PTP synchronization in frequency timer processing application-processing loop must be quick to finish
domain is used. processing within the interval between two timeouts. NTP synchronization
in time domain only possible.

Packet HW places an incoming packet into one of eight HW queues Only 2 SW based priority queues are available per process in case of fast
Processing based on packet classification. path process.

Scheduler HW based scheduler. Priority of scheduling events from amongst SW based scheduling based on DPM layer from RCP in case of fast path
available queues is configurable. process and Linux based scheduling in case of slow path process.

Atomic HW guarantees atomic processing per classified flow. No such support.

Processing

Buffer Dedicated HW (FPA) for managing buffers. FPA can manage up Buffer management is done in SW.
to 8 pools of different sizes.

Variables Per core local variable and cvmx shared variable. No such support.

Tagging PIP/IPD HW provides support to classify the IP packet based on No such support.
IP and UDP port and can forwarded the same to preconfigured
core or core group.

CIU Interrupt based timer with the help of CIU HW. No such support.
13 © 2019 Nokia
LinDX in PCUM, ETME and ETMA
• DMX messaging
• MR (Message Router) will use LinDX service (dmxmsg subsystem) for messaging with DX PRBs
• Messaging between PCUM/ETM components will still use the current IPC
• No need to configure ETPSIG and PCUSIG, no GW BCXU
• Global variables -> LinDX provides, no need to ask via messages
• SW loading and boot
• VM image includes only the boot loader (BOLERO)
• The boot loader loads the correct application image from OMU, including Nokia Linux and LinDX
• LinDX starts MR, MR will start other PCUM/ETM components
• Supervision, state management
• LinDX supervises only two application components (Slow path and Fast path) which then supervise other components as
currently
• Alarm system
• Internal alarm component uses LinDX alarm services to send alarms to TSE, no need for internal alarm storage
• Logging -> LinDX logging service is used
• IP stack configuration management -> LinDX makes configuration information available to the application
14 © 2019 Nokia
PCUM/ETME/ETMA Common Platform

PCUM, ETME, ETMA slow path applications PCUM, ETME, ETMA fast path applications

Slow path SSF Fast path SSF

Buffer Mgmt SYSMON Buffer Mgmt SYSMON CM Event
SSF applications
IPC Timer Event IPC Timer PMS

CM DX router ST FWK
Alarm Log Alarm Log Diag

LinDX DPM 6Wind

Utility libraries SW loading EMB post office Unit startup MEM EVM TIM

Recovery Alarms IO MON BB

Unit supervision Program
startup and
IP configuration supervision Event forward Memory files DPDK

Logging User authentication Global variables NTP client

6Wind Nokia Linux

15 © 2019 Nokia
PCUM – Packet Control Unit

• PCUM implements GPRS/EGPRS functionality in the BSC

• RLC/MAC protocol between PCUM and MS via the Abis interface
• Gb interface towards SGSN
• One PCUM controls certain segments, all segments of a BCF are controlled by the same PCUM
• If a segment is spread to two BCFs, those BCFs must be controlled by the same PCUM
• PCUM is synchronized to radio interface
• Initial block alignment procedure when a RTSL is added to the PS territory, or when block alignment is lost (e.g. BTS
or PCUM restart)
• The problem is that CPU clock is drifting -> Solution to keep PCUM synchronized with BTSs is required, 20ms tick
• ToP HW (PTP client) in mcBSC, SW based solution (NTP client) in AirScale BSC
• Direct interface from PCUM to Abis (ETME functionality related to PS is moved to PCUM)
• PCUM IP address is configured to BCF via Abis O&M
• PEP links between ETME and PCUM not needed
• Redundancy: N+1 (as in mcBSC)
• BCF can be moved from one PCUM to another (via existing PSE reallocation MML command)

16 © 2019 Nokia
 PCUM – Logical View
Abis termination Resource management Quality control
moved from ETME
to PCUM RM QC
(ABM, PCM, PSW, (UL QC, DL QC )
PDM, PFM, MAC,
IDRS, IBNACC )

UL RLC data blocks UL Router Gb interface

AI
AIRLC, SCH,
(PFD, RL
AIRLC, SCH,
(PFD,
COM)
BTS Gb
DL RLC data blocks COM) AI RLC, SCH,
(PFD, NSBGB
COM)
(PFD, RLC, SCH,
RTP packets COM) BGBP

Air and Abis interface

RL = Relay, adaptation of O&M

PSW = Packet Switched Radio Resource
Management
PCM = PCCCH Channel Management
ABM = Abis Manager
PDM = Packet Data Manager
IBNACC = Inter BSC/Inter System NW messages for NS and BSSGB layers,
Assisted Cell Change reassembly of UL RLC data blocks to LLC
IDRS = Inactivity Detection and Reporting PDU frames
PFM = Packet Flow Control Module NSBGB = Network Service (NS) layer
AI = Air and Abis interface modules BGBP = BSS GPRS protocol (BSGB)
MAC = Medium Access Control
QC = Quality Control

17 © 2019 Nokia
Connecting to PCUM /ETME/ ETMA
Type of Connections
1. BSC MML / DX Service Terminal
2. Telnet session
• Serial interface via NCIR Console is only for Monitoring the Startup of the VM (Virtual Machine)

BSC MML/ DX
MONITORIN
Service Terminal G
Console NCIR
dmxmsg ETME/A/ Openstack
subsystem PCUM
1
asBSC Telnet

18 © 2019 Nokia
 Type of Connections
LinDX Service Terminal Connectivity via MML or DX Service Terminal

Via MML
- Use ZDDS to enter Service Terminal to a PCUM, ETME or ETMA
- ZDDS:<unit name>,<unit index>; BSC
Example: ZDDS:PCUM,0:;
Via DX Service Terminal OMU
- ZRS:<MB>, BE
- Message Bus addresses in basic modules: DX service MML
terminal
PCUM,0> 80 MCMU ZRS
ZDDS

PCUM,1> 81
PCUM,2> 82 DX service
terminal
PCUM,3> 83 ZRS PCUM/
PCUM,4> 84 ETMx
- Service Terminal Family Process ID’s:
• BE / BF BCXU DX service
terminal
ZRS

19 © Nokia 2019 RN23930

LinDX Service Terminal Introduction

• PCUM Service Terminal functionality is based on BASH shell running on the Linux OS
• No extension to be loaded
• All commands are always usable
• Intended for expert usage:
• The PCUM commands resemble Linux commands. For example, the parameters are separated via a ‘space’
separator and commands are considered to be complete and interpreted when the Enter key is pressed.
• The user can obtain detailed help on each LinDX ST command by using the following command:
st-help <command name>
• PCUM commands are case sensitive. The commands are entered using lower case letters.
• Not all the commands require parameters to be passed to them
• The syntax of help command for bash linux is help/? [<command>]. Example:
help ps or help
• Exiting from the ST: exit

20 © 2019 Nokia RN23890

LinDX Service Terminal Introduction
0080-$ help
GNU bash, version 4.4.12(1)-release (x86_64-pc-linux-gnu)
These shell commands are defined internally. Type `help' to see this list.
help in Linux Bash
Type `help name' to find out more about the function `name'.
Use `info bash' to find out more about the shell in general.
Use `man -k' or `info' to find out more about commands not in this list.

A star (*) next to a name means that the command is disabled.

job_spec [&] history [-c] [-d offset] [n] or hist>

(( expression ))
. filename [arguments]
: kill [-s sigspec | -n signum | -sigs>
[ arg... ]
[[ expression ]]
alias [-p] [name[=value] ... ]
bg [job_spec ...]
bind [-lpsvPSVX] [-m keymap] [-f file>
break [n]
builtin [shell-builtin [arg ...]]
caller [expr]
case WORD in [PATTERN [| PATTERN]...)>
cd [-L|[-P [-e]] [-@]] [dir]
command [-pVv] command [arg ...]
compgen [-abcdefgjksuv] [-o option] [>
complete [-abcdefgjksuv] [-pr] [-DE] >
compopt [-o|+o option] [-DE] [name ..>
continue [n]
coproc [NAME] command [redirections]
declare [-aAfFgilnrtux] [-p] [name[=v>
dirs [-clpv] [+N] [-N]
disown [-h] [-ar] [jobspec ... | pid >
echo [-neE] [arg ...]
enable [-a] [-dnps] [-f filename] [na>
eval [arg ...]
exec [-cl] [-a name] [command [argume>
exit [n]
export [-fn] [name[=value] ...] or ex>
false
fc [-e ename] [-lnr] [first] [last] o>
fg [job_spec]
for NAME [in WORDS ... ] ; do COMMAND>
for (( exp1; exp2; exp3 )); do COMMAN>
function name { COMMANDS ; } or name >
getopts optstring name [arg]
21 © 2019 Nokia hash [-lr] [-pRN23930
pathname] [-dt] [name >
help [-dms] [pattern ...]
if COMMANDS; then COMMANDS; [ elif C>
jobs [-lnprs] [jobspec ...] or jobs >
let arg [arg ...]
local [option] name[=value] ...
logout [n]
mapfile [-d delim] [-n count] [-O or>
popd [-n] [+N | -N]
printf [-v var] format [arguments]
pushd [-n] [+N | -N | dir]
pwd [-LP]
read [-ers] [-a array] [-d delim] [->
readarray [-n count] [-O origin] [-s>
readonly [-aAf] [name[=value] ...] o>
return [n]
select NAME [in WORDS ... ;] do COMM>
set [-abefhkmnptuvxBCHP] [-o option->
shift [n]
shopt [-pqsu] [-o] [optname ...]
source filename [arguments]
suspend [-f]
test [expr]
time [-p] pipeline
times
trap [-lp] [[arg] signal_spec ...]
true
type [-afptP] name [name ...]
typeset [-aAfFgilnrtux] [-p] name[=v>
ulimit [-SHabcdefiklmnpqrstuvxPT] [l>
umask [-p] [-S] [mode]
unalias [-a] name [name ...]
unset [-f] [-v] [-n] [name ...]
until COMMANDS; do COMMANDS; done
variables - Names and meanings of so>
wait [-n] [id ...]
while COMMANDS; do COMMANDS; done
{ COMMANDS ;
LinDX Service Terminal Commands
Legacy PCU inheritance
Some Service terminal commands are inherited from legacy BSC, you can use the below command to get command information

$ st-help note : you can list all the support command

$ st-help <command name> eg: st-help sll

Some useful commands in LinDX units:

ETMA
>dbcfinfo eg: dbcfinfo display bcf informations
>dbscp eg: dbscp display BSC parameters

ETME
>dbcfinfo eg: dbcfinfo display bcf informations
> detpcs eg: detpcs displays CS and CSD call information

PCUM
>dai eg: dai to show application ID and application name
>dsegtbf eg: dsegtbf <seg id> to output the allocated tbf for dedicate Segment.
>dgb eg: dgb all to output gb related information
>sll eg: sll fp:133 1:2:3:4:5:6:11 to set the log level for application 133

22 © 2019 Nokia RN23930

LinDX Service Terminal Commands
• Checking PCU Status
Command
ssv software version
time current time
date current date
dai Display applications
ps / ps –a / ps -A Lists running processes in the system
ifconfig Check the interfaces
• Handling files inside PCU
Command
ls -l Directory listing
df -h Checking file system space
cat Printing out a file
fdisk –l Checking disk space
remove <filename> (remove *.log) Removing a file
mv Move files
mkdir Create directories
23 © 2019 Nokia RN23890
LinDX Service Terminal Commands
Service terminal commands for platform
General purpose commands dai
Commands provided by Linux date, ls, cat, rm, mkdir, mv
Process manipulation commands ps
Statistic commands dbu, dtu, dsca, dsco, rsca, rsco
Logging sll, dld
Software manipulation ssv
IP manipulation ifconfig, route, netstat, arp, ping
Service terminal commands for the application
Radio network related commands dtrxrnw, dbtsrnw, dsegrnw
TBF info commands dsegtbf, dtrxtbf, dtfitbf, dtsltbf, dpcutbf
GB related commands dgb
GB over IP commands dgbipbvc, dgbbvcstatus, dgbipnsei, dgbipnsvc
commands for DSP allocation info ddspinfo, dabmtrxinfo, dcem

24 © 2019 Nokia RN23930

LinDX Service Terminal Commands

ASBSC asBSC1 2019-10-06 14:32:43

Last login: Sun Oct 6 14:08:15 on pts/0
0080-$ route Checking ip routes in PCU
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
1.1.1.0 * 255.255.255.0 U 0 0 0 fpn0
10.2.122.0 * 255.255.255.128 U 0 0 0 el1
10.2.123.0 * 255.255.255.192 U 0 0 0 el5
10.2.123.160 * 255.255.255.224 U 0 0 0 el4
10.20.0.0 * 255.255.248.0 U 0 0 0 emb0
10.20.98.0 * 255.255.255.0 U 0 0 0 el0
10.30.0.0 * 255.255.248.0 U 0 0 0 emb1
0080-$

25 © 2019 Nokia RN23930

 Exercise: Basic handling of LinDX Service Terminal in PCUM
Basic exercise:
Interrogate the software version of PCUM
________________________________________________________________________________________________
Interrogate the directories of PCUM
________________________________________________________________________________________________
Check the disk space of PCUM
________________________________________________________________________________________________
Check the interfaces of the PCUM . What new interfaces can you see compared to mcBSC PCUM?
________________________________________________________________________________________________
Close the Service Terminal session
_________________________________________________________________________________________________

26 © 2019 Nokia
LinDX Service Terminal in PCUM
Execution Example
ASBSC asBSC1 2019-10-06 12:44:02
Last login: Sun Oct 6 12:33:35 on pts/0
0080-$ date
Sun Oct 6 12:44:04 NOKIA-2 2019
Checking PCU date
0080-$ time
Checking PCU time
real 0m0.000s
user 0m0.000s
sys 0m0.000s
0080-$ Checking PCU SW details
0080-$ ssv
------------------------------------------------------------
----> Command ssv executed on [06/10/2019 12:50:03:252078] <----
------------------------------------------------------------

*************************************
* Software Version Details *
*************************************
Common Platform : rev 1014b4ca7ec8f64a5a33b0c99ffc6fe9b1c6631f
PCUM Application : rev fcbbb11fe1dfba28ba27672c780fef7092107f0c
*************************************
0080-$

27 © 2019 Nokia
LinDX Service Terminal in PCUM
Directory Handling Commands
0080-$ ls -l
total 0 Command
0080-$ cd / ls -l List directory
0080-$ ls -l
total 356 ls -la List directory (attributes)
drwxr-xr-x 2 root root 4160 Oct 6 09:20 bin
-rw-r--r-- 1 root root 358 Oct 6 09:22 csagent_temp ls -lrt List directory (time based)
drwxr-xr-x 6 root root 2680 Oct 6 09:21 dev
drwxr-xr-x 17 root root 1200 Oct 6 12:39 etc cd Change directory (current user pcu directory (ie
drwxr-xr-x 2 root root 40 Oct 6 09:20 home user root)
-rwxr-xr-x 1 root root 3140 Oct 6 09:20 init
drwxr-xr-x 4 root root 80 Oct 6 09:20 lib cd / Change directory to PCU root file system
drwxr-xr-x 2 root root 1180 Oct 6 09:20 lib64
lrwxrwxrwx 1 root root 11 Oct 6 09:20 linuxrc -> bin/busybox pwd Tells you which directory you are located in the
drwxr-xr-x 4 root root 80 Oct 6 09:21 mnt service terminal interface
drwxr-xr-x 3 root root 60 Jun 9 2018 opt
dr-xr-xr-x 185 root root 0 Oct 6 09:20 proc
drwx------ 2 root root 60 Oct 6 11:08 root
drwxr-xr-x 3 root root 60 Oct 6 09:20 run
drwxr-xr-x 2 root root 2880 Oct 6 09:20 sbin
-rw-r--r-- 1 root root 355972 Oct 6 09:20 swcatalog
dr-xr-xr-x 12 root root 0 Oct 6 09:20 sys
drwxrwxrwt 3 root root 740 Oct 6 09:39 tmp
drwxr-xr-x 11 root root 220 Oct 6 09:20 usr
drwxr-xr-x 7 root root 140 Oct 6 09:20 var
0080-$ cd
0080-$ pwd
/root
0080-$

28 © 2019 Nokia
LinDx Service Terminal Help and Menu
0080-$ st-help st-help
------------------------------------------------------------
----> Command st-help executed on [06/10/2019 13:53:46:516619] <----
------------------------------------------------------------
-----------------------------------------------------
Detailed help and syntax of any command can be displayed
by typing st-help <command name>
For e.g.: st-help ssv
-----------------------------------------------------

-----------------------------------------------------
Command | Description
-----------------------------------------------------
st-help | Display Help and syntax of Service Terminal Commmands
ssv | Display software version
dai | Display Application ids to name mapping
dbu | Display buffer Statistics
dtu | Display Timer Statistics
sll | Set log level of a particular application
ssl | Set software level of a particular application
dld | Display Log Details of a particular application
olp_set_limit | Manually set OLP limits by changing to 'Manual' Mode
olp_get_limit | Will Display the currently set OLP limits
olp_set_mode | Set OLP's Mode of Operation
olp_get_mode | Get OLP's Current Mode of Operation
olp_set_load | Set Core Load Manually
olp_get_load | Get Current Total Core Load
d20msdbg | displays info about 20ms execution time and channels.
d20msdbg | displays info about 20ms execution time and channels.
d20msdbg | displays info about 20ms execution time and channels.
d20msdbg | displays info about 20ms execution time and channels.
d20msdbg | displays info about 20ms execution time and channels.
dlatepktinfo | displays info about late packet. First Argument should be dsp id.
dpfdpstpinfo | displays info about IP. First Argument should be dsp id.
dpfdpepinfo | displays info about PEP interface. First Argument should be dsp id.
dpfdjitterinfo | displays info about jitter buffer. First Argument should be dsp id.
dpfdtrxinfo | displays info about trx. First Argument should be dsp id.
dpfdglobalinfo | displays info about pfd globals. First Argument should be dsp id.
dpfdstats | displays info about pfd stats. First Argument should be dsp id.
rpfdstats | displays info about pfd stats reset. First Argument should be dsp id.
dpfddebuginfo | displays debug info. First Argument should be dsp id.
dcongestioninfo | displays info about congestion
abm_dsp_status | Show and edit DSP Status

29 © 2019 Nokia RN23890

LinDX Service Terminal in PCUM
RNW Configuration Commands
• Configuration on Segment level
dsegrnw <SEG id> (for ex. dsegrnw 83)
• Configuration on BTS level
dbtsrnw <BTS id> (for ex. dbtsrnw 83)
• Configuration on TRX level
dtrxrnw <BTS id> <TRX id> (for ex. dtrxrnw 83 1)
Syntax help Example
0080-$ st-help dbtsrnw
------------------------------------------------------------
----> Command st-help executed on [06/10/2019 13:25:49:159543]
<----
------------------------------------------------------------
Usage: dbtsrnw <BTS ID>
Display RNW configuration for a particular BTS

0080-$

30 © 2019 Nokia RN23930

 PCUM Service Terminal > Displaying segment RNW
0080-$ dsegrnw 1
------------------------------------------------------------
----> Command dsegrnw executed on [06/10/2019 13:29:59:879382] <----
------------------------------------------------------------
SEG_ID:1 Num_BTS:1 BCCH_BCSU_UNIT:17269
Displaying segment RNW > dsegrnw <seg id>
Num_GPRS_TSLs:0 Num_EGPRS_TSLs:1
PCCCH_BTS:1
PCCCH_TRX:1
PCCCH_TSL:Not Configured
PCCCH_DSP_ID:Not Configured
Ext Cell: NO Segment specific configuration
Super Ext Cell: NO
DLPC Enabled: No
Composite Multi Site Transmission State: Disabled
PEO_BCCH_CHANGE_MARK: 0
RCC (Rf Color Code): 0
SEG_ID:1 BTS_ID:1 Access_Tech:GSM_P Edge_Capable:YES
Is_Congested:NO Congestion_Level:255
ETP_BCF_ID: 1 BCF_IP: 10.31.196.217
Num_Default_TSLs:1 Num_Dedicated_TSLs:0
NUM_EGTCH: 0
NUM_EGTCH in S-TRXs: 0
Actual_Num_of_TSLs_for_PSW:1 BCCH_TRX_BCSU: 17269
PEO_Capable: No
BLOCKED_FOR_CCCH_ALLOC :0
EC-EGPRS TRX'S :0
INITIAL MCS FOR ACKNOWLEDGED MODE IN NORMAL AREA : MCS6
INITIAL MCS FOR UNACKNOWLEDGED MODE IN NORMAL AREA : MCS5
INITIAL MCS FOR ACKNOWLEDGED MODE IN EXTENDED AREA : MCS1 BTS specific configuration
INITIAL MCS FOR UNACKNOWLEDGED MODE IN EXTENDED AREA : MCS1
DL CODING SCHEME IN ACKNOWLEDGED MODE IN NORMAL AREA: CS2
UL CODING SCHEME IN ACKNOWLEDGED MODE IN NORMAL AREA: CS2
DL CODING SCHEME IN UNACKNOWLEDGED MODE IN NORMAL AREA: CS2
UL CODING SCHEME IN UNACKNOWLEDGED MODE IN NORMAL AREA: CS2
DL CODING SCHEME IN ACKNOWLEDGED MODE IN EXTENDED AREA: CS1
UL CODING SCHEME IN ACKNOWLEDGED MODE IN EXTENDED AREA: CS1
DL CODING SCHEME IN UNACKNOWLEDGED MODE IN EXTENDED AREA: CS1
UL CODING SCHEME IN UNACKNOWLEDGED MODE IN EXTENDED AREA: CS1
Num_TRX:1
Num_E_TRX:0
Num_S_TRX:0
DLDC Enabled:NO
BTS_ID:1 TRX_ID:1 EDAP_ID:65535 ARFCN:4 Access Tech:GSM_P
TRX specific configuration
TX_Power:0 Hopping:NO Territory_Type:EGPRS_CS1_CS2
DSP Id : 0 CONTR_BCSU_ADDR : 17269 E-TRX : NO S-TRX : NO
DLDC TRX : No
SSS_ENABLED: NO
Num_of_PSW_TSLs:1
TSL_7:DEFAULT
31 ec_egprs_ma_number:
© Nokia 2019 0 RN23930
 PCUM Service Terminal > Displaying BTS RNW
0080-$ dbtsrnw 1
------------------------------------------------------------
----> Command dbtsrnw executed on [06/10/2019 13:34:17:58698] < ----
------------------------------------------------------------ Displaying BTS RNW > dbtsrnw <bts id>
SEG_ID:1 BTS_ID:1 Access_Tech:GSM_P Edge_Capable:YES
Is_Congested:NO Congestion_Level:255
ETP_BCF_ID: 1 BCF_IP: 10.31.196.217
Num_Default_TSLs:1 Num_Dedicated_TSLs:0
NUM_EGTCH: 0
NUM_EGTCH in S-TRXs: 0
Actual_Num_of_TSLs_for_PSW:1 BCCH_TRX_BCSU: 17269
PEO_Capable: No
BLOCKED_FOR_CCCH_ALLOC :0
EC-EGPRS TRX'S :0
INITIAL MCS FOR ACKNOWLEDGED MODE IN NORMAL AREA : MCS6
INITIAL MCS FOR UNACKNOWLEDGED MODE IN NORMAL AREA : MCS5
INITIAL MCS FOR ACKNOWLEDGED MODE IN EXTENDED AREA : MCS1
INITIAL MCS FOR UNACKNOWLEDGED MODE IN EXTENDED AREA : MCS1
DL CODING SCHEME IN ACKNOWLEDGED MODE IN NORMAL AREA: CS2
UL CODING SCHEME IN ACKNOWLEDGED MODE IN NORMAL AREA: CS2
DL CODING SCHEME IN UNACKNOWLEDGED MODE IN NORMAL AREA: CS2
UL CODING SCHEME IN UNACKNOWLEDGED MODE IN NORMAL AREA: CS2
DL CODING SCHEME IN ACKNOWLEDGED MODE IN EXTENDED AREA: CS1
BTS specific configuration
UL CODING SCHEME IN ACKNOWLEDGED MODE IN EXTENDED AREA: CS1
DL CODING SCHEME IN UNACKNOWLEDGED MODE IN EXTENDED AREA: CS1
UL CODING SCHEME IN UNACKNOWLEDGED MODE IN EXTENDED AREA: CS1
Num_TRX:1
Num_E_TRX:0
Num_S_TRX:0
DLDC Enabled:NO

BTS_ID:1 TRX_ID:1 EDAP_ID:65535 ARFCN:4 Access Tech:GSM_P

TX_Power:0 Hopping:NO Territory_Type:EGPRS_CS1_CS2
DSP Id : 0 CONTR_BCSU_ADDR : 17269 E-TRX : NO S-TRX : NO
DLDC TRX : No
SSS_ENABLED: NO

Num_of_PSW_TSLs:1
TSL_7:DEFAULT

ec_egprs_ma_number: 0

0080-$

32 © Nokia 2019 RN23930

 PCUM Service Terminal > Displaying TRX RNW

Displaying trx RNW > dtrxrnw <bts id> <trx id>

0080-$ dtrxrnw 1 1
------------------------------------------------------------
----> Command dtrxrnw executed on [06/10/2019 13:38:51:238114] <----
------------------------------------------------------------

BTS_ID:1 TRX_ID:1 EDAP_ID:65535 ARFCN:4 Access Tech:GSM_P

TX_Power:0 Hopping:NO Territory_Type:EGPRS_CS1_CS2
DSP Id : 0
DLDC TRX : No
CONTR_BCSU_ADDR : 17269 E-TRX : NO S-TRX : NO
TRX specific configuration
SSS_ENABLED: NO

Num_of_PSW_TSLs:1
TSL_7:DEFAULT

ec_egprs_ma_number: 0

0080-$

33 © Nokia 2019 RN23930

 PCUM Service Terminal > TBF Information
• TBF Info Commands group
- TBF Traffic going through a segment a TRX or a timeslot
• dsegtbf <SEG id> (for ex. dtrxtbf 7)
• dtrxtbf <BTS id> (for ex. dtrxtbf 7 1)
• dtsltbf <BTS id> <TRX id> <TSL id> (for ex. dtrxtbf 7 1 7)
- Traffic going through PCU
• dpcutbf
- Display the TBF information specific to identified TFI)
• dtfitbf <BTS id> <TRX id> <TSLid> <TFI id> (for ex. dtrxtbf 7 1 7 15)

34 © Nokia 2019 RN23930

 PCUM Service Terminal > PCU TBF allocations
Displaying a summary of all TBF’s in the PCU > dpcutbf

0080-$ dpcutbf
------------------------------------------------------------
----> Command dpcutbf executed on [06/10/2019 13:46:12:867505] <----
------------------------------------------------------------
************************************START OF TRACE**************************************
SEG-ID Num-TRX DSP-ID Num-UL-TBFs Num-DL-TBFs
1 1 0 0 0
96 2 1 0 6
97 2 2 0 0
98 2 3 0 7
99 2 4 0 0
100 2 1 0 6
101 2 2 0 0
102 2 3 0 7
103 2 2 0 0
104 2 3 0 7
105 2 0 0 0
106 2 1 0 7
------------------------------------------------------------ Sum of TBFs in the PCU
TOTAL: 0 40
------------------------------------------------------------
****************************END OF TRACE ****************************
0080-$

35 © Nokia 2019 RN23930

 PCUM Service Terminal > TBF Information
BTS ID : 100 [0x64] Displaying TBF PS call RNW > dsegtbf <SEG id>
TRX ID : 6 [0x6]
DSP ID : 0
Direction : UPLINK
RLC MODE TBF : ACK
TSL NUM Allocated : 6
USF : 127 127 127 127 127 127 2 127
TBF STATE : PDM_ULTBF_REALLOC_IN_PROGRESS
TBF ID : 8 [0x8]
TFI : 29 [0x1d]
Direction : DOWNLINK
RLC MODE TBF : ACK
TSL NUM Allocated : 3 4 5 6 7
TBF STATE : PDM_DLTBF_REALLOC_IN_PROGRESS
TBF ID : 0 [0x0]
TFI : 29 [0x1d]
Coding Scheme : MCS9
TBF Data rate : 11.02 KB per sec
TLLI : 3222380709 [0xc011a0a5]
MS_INDEX : 0x0064c011a0a5
IMSI : 520181021511510
TYPE : EGPRS
NC Mode MS : 0
TSL_3 : DOWNLINK
TSL_4 : DOWNLINK
TSL_5 : DOWNLINK
TSL_6 : CONCURRENT
TSL_7 : DOWNLINK
PFI : 0
PFC ID DL : 4065601 [0x3e0941]
Guranteed Data Rate DL : 0
RLC MODE PFC : ACK
Traffic Class : BEST_EFFORT
ARP : ARP2
PFI : 0
PFC ID UL : 4065600 [0x3e0940]
Guranteed Data Rate UL : 0
RLC MODE PFC : ACK
Traffic Class : BEST_EFFORT
ARP : ARP2

36 © Nokia 2019 RN23930

PCUM Service Terminal > Cell Monitoring
Cell Monitoring commands offers Several parameter choices
dcem

• Display info of all MS of all TSL of all TRX of all BTS of a particular Segment
dcem -g <seg_id>
• Display info of all MS of all TSL of all TRX of a particular BTS
dcem -b <bts_id>
• Display info of a particular TBF ID
dcem -t <tbf_id>
• Display info of a particular TLLI
dcem -i <seg_id> <tlli>
• Display info of all MS on all TSL of a particular TRX
dcem -x <bts_id> <trx_id>
• Display info of all MS on particular TSL of a TRX
dcem -s <bts_id> <trx_id> <tsl>
• Display info of a particular TFI on a TSL of a TRX
dcem -f <bts_id> <trx_id> <tsl> <tfi>

37 © Nokia 2019 RN23930

PCUM Service Terminal > Gb interface commands

• Gb configuration + values of Gb timers and counters

dgb
• Gb over IP commands
dgbipbvc <BVCI>
dgbipnsei <BVCI> <NSEI>
dgbipnsvc <NSVCI>

38 © Nokia 2019 RN23930

 PCUM Service Terminal > Gb Configuration
0080-$ dgb all GB Timers and Counters values:
------------------------------------------------------------
----> Command dgb executed on [06/10/2019 14:00:58:515997] <----
Parameter T_TNS_BLOCK :: 300
Parameter T_TNS_RESET :: 300 Displaying GB interface parameters>
dgb all
Parameter T_TNS_TEST :: 500
------------------------------------------------------------ Parameter T_TNS_ALIVE :: 300
************************ Start of Trace ************************ Parameter T_TNS_FLOW :: 100
Bearer Network in use is IP Parameter NS_BLOCK_RETRIES :: 3
Number of NSEI configured::1 Parameter NS_UNBLOCK_RETRIES :: 3
Parameter NS_ALIVE_RETRIES :: 10
BVCs in Use : Parameter NS_RESET_RETRIES :: 255
Parameter T_TGB_BLOCK :: 300
Segment ID::1 BVC ID::10001 POOL ID::NONE
Parameter T_TGB_RESET :: 300
Number of BVCs Configured: 1
Parameter T_TGB_SUSPEND :: 60
Parameter T_TGB_FLOW :: 100
Parameter BVC_BLOCK_RETRIES :: 12
PFC Feature Mode[0]: IMSGW_FALSE Parameter BVC_UNBLOCK_RETRIES :: 12
Parameter BVC_RESET_RETRIES :: 22
Parameter BVC_SUSPEND_RETRIES :: 3
NSEI: 1011 Parameter BSSGP_FLOW_CONTROL_ON_LEVEL :: 75
Parameter BSSGP_FLOW_CONTROL_OFF_LEVEL :: 50
Parameter CELL_BUFFER_SAFETY_FACTOR :: 20
Parameter FC_R_DIF_TRG_LIMIT :: 100
MOCN Support: NO Parameter FC_MS_R_DEF :: 4500
Parameter FC_MS_R_DEF_EGPRS :: 15000
NSVCs information : Parameter FC_MS_R_MIN :: 40
Local Endpoint: IP Address::10.2.123.165 Parameter FC_MS_B_MAX_DEF :: 10000
Parameter FC_MS_B_MAX_DEF_EGPRS :: 25000
UDP Port::50000
Parameter FC_R_TSL :: 1500
Preconfigured NSVC ID::1011 Parameter FC_R_TSL_EGPRS :: 4500
Preconfigured NSVC Remote Endpoint: IP Address::10.88.46.54 Parameter FC_B_MAX_TSL :: 25000
Preconfigured NSVC Remote UDP Port::49999 Parameter FC_B_MAX_TSL_EGPRS :: 25000
Preconfigured NSVC Remote Data Weight::1 Parameter FC_FORG_FACTOR :: 500
Preconfigured NSVC Remote Signalling Weight::1 Parameter T_SNS_PROV :: 3
NSE Capacity Value :: 1 Parameter T_SNS_ADD_RETRIES :: 3
SGSN Prevented :: NO Parameter T_SNS_CONFIG_RETRIES :: 3
Parameter T_SNS_CHANGEWEIGHT_RETRIES :: 3
Auto-Configured NSVCs Info :: Parameter T_SNS_DELETE_RETRIES :: 3
NSVC ID::1012 Parameter T_SNS_SIZE_RETRIES :: 10
Remote Endpoint: IP Address::10.88.46.54 Parameter T_TGB_RAC_UPDATE :: 3
UDP Port::51011 Parameter RAC_UPDATE_RETRIES :: 3
Remote Data Weight::1 Parameter T_TGB_DNLOAD_BSS_PFC :: 300
Remote Signalling Weight::1 Parameter DNLOAD_BSS_PFC_RETRIES :: 3
Number of NS-ALIVE received from SGSN : 0 Parameter T_TGB_MODIFY_BSS_PFC :: 300
Parameter MODIFY_BSS_PFC_RETRIES :: 3
Number of NS-ALIVE-ACK sent to SGSN : 0 Parameter RESUME_RETRIES_INDEX :: 1
Parameter T_TGB_RESUME :: 20
Parameter PS_NULL_NRI_SUPPORT :: 0
Number of NSVCs Configured : 1 Parameter SNS_SIZE_IPEP :: 1
Number of NSVCs Configured Over IPv4 : 1 Parameter UL_PDUS_REROUTE_ACT :: 1
Number of NSVCs Configured Over IPv6 : 0 ************************* End of Trace *************************
0080-$
The Number of PDU's Re-Routed from this NSE = 0

39 © Nokia 2019 RN23930

PCUM Service Terminal > Gb over IP NSVC configuration
Command Syntax for 'dgbipnsvc' Command: Displaying Gb IP interface> dgbipnsvc <nsvci> <nsei>
dgbipnsvc <NSVCI> <"all"|NSEI>
eg: dgbipnsvc 1 all
eg: dgbipnsvc 1 1

0080-$dgbipnsvc 04001 04001

------------------------------------------------------------
----> Command dgbipnsvc executed on [16/6/2019 16:50:40:651922] < ----
------------------------------------------------------------

NSEI: 4001
MOCN Supported:NO OP_ID : NONE

NSVCs information :
Local Endpoint: IP Address::10.31.251.164
UDP Port::54001
Preconfigured NSVC ID::4001
Preconfigured NSVC Remote Endpoint: IP Address::10.88.40.167
Preconfigured NSVC Remote UDP Port::50001
Preconfigured NSVC Remote Data Weight::1
Preconfigured NSVC Remote Signaling Weight::1
0080-$

40 © Nokia 2019 RN23930

PCUM Service Terminal: NCCR and NACC commands
• NCCR Commands group
- How many mobiles in NC2 mode on this PCU?
• dnc2ms
- How many in NC0 mode?
• dnc0ms
- NCCR related MS specific information by TLLI/MS id
• dnccrms –t <TLLI> <SEG id> (for ex. dnccrms –t 3496265481 83)
• TLLI / MS id seen with TBF commands
• NACC Commands group
- Neighbor cell configuration for a segment:
• dnacc
- Serving cell SI or PSI messages
• dsinacc <SEG id> (for ex. dsinacc 83)
- Neighbor cells’ SI or PSI messages
• dpsinacc <SEG id> (for ex. dpsinacc 83)

41 © Nokia 2019 RN23930

asBSC PCUM Cores / DSPs
Service terminal commands for DSP allocation information
Displaying Info on DSP Cores > ddspinfo all
0080-$ ddspinfo all
------------------------------------------------------------
----> Command ddspinfo executed on [06/10/2019 17:35:14:771693] <----
------------------------------------------------------------
DSP-ID SEG-ID

0 1
1
2
3
4
D E G S E E E E E E E E
S G P T D D D D D D D D
P P R A A A A A A A A A
I R S T P P P P P P P P
D S E 0 1 2 3 4 5 6 7

0 1 0 1 ffff/ff ffff/ff ffff/ff ffff/ff ffff/ff ffff/ff ffff/ff ffff/ff

1 0 0 1 ffff/ff ffff/ff ffff/ff ffff/ff ffff/ff ffff/ff ffff/ff ffff/ff
2 0 0 1 ffff/ff ffff/ff ffff/ff ffff/ff ffff/ff ffff/ff ffff/ff ffff/ff
3 0 0 1 ffff/ff ffff/ff ffff/ff ffff/ff ffff/ff ffff/ff ffff/ff ffff/ff
4 0 0 1 ffff/ff ffff/ff ffff/ff ffff/ff ffff/ff ffff/ff ffff/ff ffff/ff

Where DSP state, 0 - DSP_UNKNOWN

1 - DSP_READY
2 - DSP_FAILED
3 - DSP_NOT_USED

DSP Reserved channel count

0 0
1 0
2 0
3 0
4 0
0080-$
42 © 2019 Nokia RN23930
PCUM Architecture – Usage of vCPUs
RELAY BSSGB
ULR Common platform SCH RLC NS

SSF LinDX GB
COM PFD
Linux PCM IBNACC
UL router
(one vCPU) Slow path vCPU – DTT
Management instance PDM PSW
(one vCPU)

SSF IDRS ABM

DPM
PFM
DPM
DPM Linux
(one vCPU)
RRM
AI (5 vCPU)
MAC QC
Slow path vCPU
6Wind - Master instance
(one vCPU) SSF
DPM/DPDK DPM

6Wind vCPU (1 vCPU) Gb/RRM

(2 vCPU)

43 © 2019 Nokia
LinDX Service Terminal Commands

44 2018 RN23890
44 © 2019 Nokia
LinDX Service Terminal System
LinDX makes Linux yet another operating system alternative for DX computer units. Other alternatives include e.g. DMX, Chorus
and OSE

Service terminal for LinDX ( new command from with ASBSC.)

Command line Short description

lnx-dmxmsg-msgmon Message monitoring

lnx-dmxmsg-shell Send and receive messages on command line

lnx-dmxmsg-send
lnx-dmxmsg-recv
lnx-dmxmsg-poll

lnx-log Read system log

lnx-dxerr-code Error code checking

lnx-fu Read system log

lnx-dxfile-cp Copy files from(/to) DMX units

lnx-pubvar Access public variables (like Phys addr)

lnx-swlist Find loaded files/packages

lnx-launcher Handle the programs started by lnx-launcher-d

45 06/03/2023 © Nokia 2014 - File Name - Version - Creator - DocID

Confidential
 LinDX Programs / Commands
Command lnx- Displays LinDX Programs
lnx-blackbox-cli
0080-$ lnx-
lnx-blackbox-cli lnx-fp-pcum lnx-ns-test lnx-cp
lnx-cp lnx-fp-pcum.sh lnx-pubvar lnx-dik lnx-launcher
lnx-dik lnx-fu lnx-rsterm
lnx-dmxmsg-msgmon lnx-fu-log lnx-sp-pcum lnx-dmxmsg-msgmon lnx-lieser
lnx-dmxmsg-poll lnx-ikeconf-d lnx-sp-pcum.sh lnx-log
lnx-dmxmsg-recv lnx-ipconf-test lnx-swlist lnx-dmxmsg-poll
lnx-dmxmsg-send lnx-launcher lnx-swlist-chain lnx-dmxmsg-recv lnx-log-forwarder
lnx-dmxmsg-shell lnx-lieser lnx-sysmon-cli
lnx-dxerr-code lnx-log lnx-util-runtimeout lnx-dmxmsg-send lnx-module-checksum
lnx-dxfile-cp lnx-log-forwarder lnx-vplatfrom-st-cli
lnx-dmxmsg-shell lnx-ns-query
lnx-dxfile-imgtool lnx-module-checksum
lnx-dxfile-mem-file lnx-ns-query lnx-dxerr-code lnx-ns-test
0080-$ lnx-
lnx-dxfile-cp lnx-pubvar
lnx-dxfile-imgtool lnx-rsterm
lnx-dxfile-mem-file lnx-sp-pcum
lnx-fp-pcum lnx-sp-pcum.sh
lnx-fp-pcum.sh lnx-swlist
lnx-fu lnx-swlist-chain
lnx-fu-log lnx-sysmon-cli
lnx-ikecond-d lnx-util-runtimeout
lnx-ipconf-test lnx-vplatfrom-st-cli

46 © 2019 Nokia RN23930

 LinDX Processes
Help for lnx-launcher
lnx-launcher -help Listing a specific lnx program
0080-$ lnx-launcher -help
0080-$ lnx-launcher -l lnx-lalarm-d
Handle the programs started by Launcher
name = lnx-lalarm-d
Usage: lnx-launcher [OPTIONS] cmd = ${LINDX_SUBSYSTEMS_DIR}/lalarm/lnx-
lalarm-d
Options: after = lnx-fu-rcy-d
-L List info of all programs pid = 541
-l program(s) List info of program(s) dmxpid = 143
-k program(s) Kill program(s) critical = 1
-R Restart all programs restartable = N
-r program(s) Restart program(s) starting phase = 0
-h Show this help start timeout = 10
supervision timeout = 20
0080-$ state = running
nice = 0
not_running_in_te = 0

0080-$

47 © 2019 Nokia RN23930

LinDX Processes
Listing all LNX Processes
0080-$ lnx-launcher -L

NAME PID DMXPID C R P STATE lnx-hwapi-rps-enabler 538 0 N 0 finished

lnx-dxdiag-d 2267 A3 0 Y 1 running lnx-sysmon-d 2203 777 1 N 1 running
lnx-dmxmsg-epo-d 483 66B 2 N 0 running lnx-gersup-d 2612 A30 0 Y 3 running
lnx-sysmon-diq-d 2323 626 0 Y 1 running lnx-dxfile-iomana-d 2207 F 0 Y 1 running
lnx-random-writer 2317 AB7 1 N 1 finished lnx-dxfile-rmemfs-d 579 2A0 0 Y 0 running
lnx-swlist-d 2256 205 0 Y 1 running lnx-ethmana-d 2264 3CA 0 Y 1 running
lnx-dxerr-load 2205 0 N 1 finished lnx-dmxrtemu-d 522 0 0 Y 0 running
lnx-rsterm-d-be 578 BE 0 Y 0 running lnx-ikeconf-d 2596 617 0 Y 3 running
lnx-rsterm-d-bf 577 BF 0 Y 0 running lnx-fu-rcy-d 529 A0 2 N 0 running
lnx-lieser-d 537 43B 1 N 0 running lnx-fu-fuzzi-d 523 103 2 N 0 running
lnx-dmxmsg-distmon-d 2204 C1 0 Y 1 running lnx-ipconf-d 2209 43E 0 Y 1 running
lnx-unabom-d 525 A1 0 Y 0 running lnx-lalarm-d 541 143 1 N 0 running
lnx-lrm-d 2349 13B 0 Y 1 running lnx-blackbox-d 2270 978 0 Y 1 running
lnx-sysmon-cpupro-d 2324 FF 0 Y 1 running lnx-setup 340 1 N 0 finished
lnx-sp-pcum 2595 435 1 N 3 running
lnx-fp-pcum 2953 ACE 1 N 3 running ( C = criticality, R = restartable, P = starting phase )
lnx-ns-d 2254 260 0 Y 1 running
lnx-sysmon-lmp-d 2328 47B 0 Y 1 running
lnx-ntpconf-d 2952 B2E 0 Y 3 running 0080-$
lnx-6wind-monitor 1920 AC6 1 N 0 running
lnx-dxfile-loader 580 705 1 N 0 finished
lnx-6wind-starter 543 AC6 1 N 0 finished
lnx-dxfile-femser-d 576 90 0 Y 0 running
lnx-csagent-d 2261 671 0 Y 1 running
lnx-log-sender-d 2251 3BD 0 Y 1 running
lnx-log-syslog-d 339 0 Y 0 running
lnx-log-klog-d 341 0 Y 0 running
lnx-dik-d 2310 72C 0 Y 1 running

48 © 2019 Nokia RN23930

LinDX Processes
Reading the DMXMSG LNX process
0080-$ lnx-launcher -l lnx-dmxmsg-epo-d

name = lnx-dmxmsg-epo-d
cmd = ${LINDX_SUBSYSTEMS_DIR}/dmxmsg/lnx-dmxmsg-epo-d.sh
after = lnx-setup
pid = 483
dmxpid = 66B
critical = 2
restartable = N
starting phase = 0
start timeout = 10
supervision timeout = 10
state = running
nice = 0
not_running_in_te = 0

0080-$

49 © 2019 Nokia RN23930

LinDX Logs
Log Handling Program
0080-$ lnx-log -h Error.
-T TYPE show only log printouts of given type.
Usage: lnx-log [OPTION]... -N Print additional new line between log
printouts.
Log handling program. If no parameters are given, Error -a force ascii form printout.
and Critical -v program prevent log printouts from the program
type of log printouts are printed. -m program remove the prevention from the program.
Log can be cleared, its size can be changed and its -o show prevented programs.
content can be -z SIZE set the size of the log in bytes.
printed with using log printout's index, type or program -h show this help.
name as a filter. -S Show the status of the log.
It is also possible to prevent log printouts from specific
programs. -x test_case Execute a test case for log the service.
1. test log_data function
Options: 2. test log_print function
-n log_name Name of the log. If not given default log 3. print alternatively to logs A and B.
is used 4. print log printouts which size if
-l List own log files. form 1 to count
-c size Create own log. Size defines the log's size 5. write a test message to the log
-C copy_name Copy the content of the log to copy_name 6. write a log printout with size given
named log with -Y parameter
-e empty the log. 7. write a log printout with serial
-r remove the log. number
-s index show one log printout. 8. test log_print_disk function
-p program show log printouts from the program. -y count How many times the test case is repeated
-t TYPE show log printouts of given and more severe -Y size The size of the test log printout
types. -d delay How many log delays once
Type is one of the following: -D interval How long is the delay(us)
C Critical -u thread How many thread to print log
E Error
N Notice 0080-$
T Test
Default value for the type is Critical and

50 © 2019 Nokia RN23930

LinDX Commands
Printing out Logs
0080-$ lnx-log If no parameters are inputed only error
Ind. Type Date Time Program: Log print and critical logs are printed
121 C-000 2019-10-06 09:20:45.48 lnx-log-syslog-d: [daemon.alert] 09:20:45
fp-rte[1522]: Entering module vBSC_plugin_init

122 C-000 2019-10-06 09:20:45.48 lnx-log-syslog-d: [daemon.alert] 09:20:45

fp-rte[1522]: Registering vBSC mainloop

123 C-000 2019-10-06 09:20:45.48 lnx-log-syslog-d: [daemon.alert] 09:20:45

fp-rte[1522]: Registering vBSC UDP handler

124 C-000 2019-10-06 09:20:45.48 lnx-log-syslog-d: [daemon.alert] 09:20:45

fp-rte[1522]: Created send/receive DPDK rings

125 C-000 2019-10-06 09:20:45.48 lnx-log-syslog-d: [daemon.alert] 09:20:45

fp-rte[1522]: vBSC_plugin_init done.

310 C-000 2019-10-06 09:22:00.95 lnx-sp-pcum:

CPF-LOG:[Layer:1][File:cm_main.c][Line:1926][Inst:1][App:1][LogSeqNo:0][LogLevel
:CRITICAL][LogMsg:SP:CRIT , ERR & WARN LOGGING ENABLED
]
311 C-000 2019-10-06 09:22:00.98 lnx-sp-pcum:
CPF-LOG:[Layer:1][File:cm_main.c][Line:791][Inst:1][App:23][LogSeqNo:0][LogLevel
:CRITICAL][LogMsg:Updated:
phy_addr=128,own_unit_addr=28923,own_unit_index=0,own_unit_type=297,own_unit_sta
te=1]

312 C-000 2019-10-06 09:22:01.00 lnx-sp-pcum:

CPF-LOG:[Unit:0x80][Layer:1][File:cm_main.c][Line:791][Inst:1][App:23][LogSeqNo:
1][LogLevel:CRITICAL][LogMsg:Updated:
phy_addr=128,own_unit_addr=28923,own_unit_index=0,own_unit_type=297,own_unit_sta
te=1]

51 © 2019 Nokia RN23930

 LinDX Commands kernel: [ 14.016522] EMB-1 IP address is 0a1e0180
15 N-000 2019-10-06 09:20:37.35 lnx-log-syslog-d: [user.info] 07:20:37
Printing out Test Logs kernel: [ 14.016694] Found unit 0x00
16 N-000 2019-10-06 09:20:37.35 lnx-log-syslog-d: [user.info] 07:20:37
0080-$ lnx-log -t T kernel: [ 14.016695] Found unit 0x04
Ind. Type Date Time Program: Log print 17 N-000 2019-10-06 09:20:37.35 lnx-log-syslog-d: [user.info] 07:20:37
kernel: [
1 N-000 2019-10-06 09:20:28.03 lnx-log-syslog-d: [user.info] 07:20:28 14.016696] Found unit 0x05
kernel: [ 18 N-000
4.703265] x86/PAT: lnx-setup:340 freeing invalid memtype [mem 2019-10-06 09:20:37.35 lnx-log-syslog-d: [user.info] 07:20:37
0x04008000-0x04008fff] kernel: [ 14.016697] Found unit 0x58
19 N-000
2 N-000 2019-10-06 09:20:28.06 lnx-log-syslog-d: [user.info] 07:20:28 2019-10-06 09:20:37.35 lnx-log-syslog-d: [user.info] 07:20:37
kernel: [ kernel: [
4.725888] x86/PAT: lnx-setup:340 freeing invalid memtype [mem 14.016698] Found unit 0x60
0x04008000-0x04008fff] 20 N-000 2019-10-06 09:20:37.35 lnx-log-syslog-d: [user.info] 07:20:37
kernel: [
3 N-000 2019-10-06 09:20:28.06 lnx-log-syslog-d: [user.info] 07:20:28 14.016699] Found unit 0x61
kernel: [ 4.725897] x86/PAT: lnx-setup:340 freeing invalid memtype [mem 2019-10-06 09:20:37.35 lnx-log-syslog-d: [user.info]
21 N-000 07:20:37
0x04008000-0x04008fff] kernel: [ 14.016699] Found unit 0x6D
4 N-000 2019-10-06 09:20:28.10 lnx-log-syslog-d: [user.info] 07:20:282019-10-06 09:20:37.35 lnx-log-syslog-d: [user.info]
22 N-000 07:20:37
kernel: [ kernel: [
4.771290] virtio_net virtio2 emb0: renamed from eth2 14.016700] Found unit 0x6E
5 N-000 2019-10-06 09:20:28.11 lnx-log-syslog-d: [user.info] 07:20:282019-10-06 09:20:37.35 lnx-log-syslog-d: [user.info]
23 N-000 07:20:37
kernel: [ kernel: [
4.779304] virtio_net virtio3 emb1: renamed from eth3 14.016701] Found unit 0x81
6 N-000 2019-10-06 09:20:28.15 lnx-log-syslog-d: [user.info] 07:20:282019-10-06 09:20:37.35 lnx-log-syslog-d: [user.info]
24 N-000 07:20:37
kernel: [ 4.815666] EXT4-fs (vdb): recovery complete kernel: [ 14.016702] SYM reached
7 N-000 2019-10-06 09:20:28.15 lnx-log-syslog-d: [user.info] 07:20:282019-10-06 09:20:37.35 lnx-log-syslog-d: [user.info]
25 N-000 07:20:37
kernel: [ 4.817742] EXT4-fs (vdb): mounted filesystem with kernel:
ordered [data14.016713]
mode. Contacted unit 0x04 on EMB-0 (err_count was 0)
Opts: (null) 26 N-000 2019-10-06 09:20:37.35 lnx-log-syslog-d: [user.info] 07:20:37
8 N-000 2019-10-06 09:20:32.32 lnx-setup: Setup complete kernel: [ 14.016716] Contacted unit 0x05 on EMB-0 (err_count was 0)
27 N-000
9 N-000 2019-10-06 09:20:32.32 lnx-launcher-d: Family 'lnx-setup' exited 2019-10-06 09:20:37.35 lnx-log-syslog-d: [user.info] 07:20:37
normally with status=0 kernel: [ 14.016734] Contacted unit 0x58 on EMB-0 (err_count was 0)
28 N-000
10 N-000 2019-10-06 09:20:37.34 lnx-log-syslog-d: [user.warn] 07:20:37 2019-10-06 09:20:37.35 lnx-log-syslog-d: [user.info] 07:20:37
kernel: [ kernel: [ 14.016738]
14.006790] dmxmsg_core: loading out-of-tree module taints kernel. Contacted unit 0x60 on EMB-0 (err_count was 0)
29 N-000
11 N-000 2019-10-06 09:20:37.35 lnx-log-syslog-d: [user.warn] 07:20:37 2019-10-06 09:20:37.35 lnx-log-syslog-d: [user.info] 07:20:37
kernel: [ 14.016520] EMB-0 hwaddr is fa:16:3e:d2:29:f7 kernel: [ 14.016741] Contacted unit 0x61 on EMB-0 (err_count was 0)
12 N-000 2019-10-06 09:20:37.35 lnx-log-syslog-d: [user.warn] 30 07:20:37
N-000 2019-10-06 09:20:37.35 lnx-log-syslog-d: [user.info] 07:20:37
kernel: [ 14.016521] EMB-1 hwaddr is fa:16:3e:a0:31:d2
13 N-000 2019-10-06 09:20:37.35 lnx-log-syslog-d: [user.warn] 07:20:37
kernel: [ 14.016522] EMB-0 IP address is 0a140180
14 N-000 2019-10-06 09:20:37.35 lnx-log-syslog-d: [user.warn] 07:20:37

52 © 2019 Nokia RN23930

LinDX Commands
LinDX - DMX Functionality (Functional Units)
ASBSC asBSC1 2019-10-06 15:22:58
Last login: Sun Oct 6 15:10:58 on pts/0
0080-$ lnx-fu h
Usage: lnx-fu [-a] [-e] [-f] [-l] [-m] [-r [start]:[stop]] [-s [start]:[stop]]
[-v] [-t [unit]:[start]:[stop]] [-u unit,index | def all]
[-p unit,index] [-d [unit]:[unit]]Options:
-a: Displays shared memory pointers and handles
-e: Displays records of own SCDFLE in same way that ZUSEO st command
in DMX units.
-f: Displays used records from FUNINDE table.
-l: Displays used records from phys/log address conversion table.
-m: Displays used records from MBINDE table.
-r: Displays SCDFLE file dump between start/stop record numbers.
Enter record numbers in hexadesimal format.
-s: Displays SCDFLE file records between start/stop record numbers.
Enter record numbers in hexadesimal format.
-t: Compares SCDFLE file records from given unit between start/stop
record numbers.
Enter record numbers in hexadesimal format.
-v: Displays public variables.
-u: Displays unit info.
-p: Displays parent info.
-h: Displays this message.
-d: Displays typind table of SCDFLE

0080-$

53 © 2019 Nokia RN23930

LinDX Commands
LinDX - DMX Functionality (Functional Units)
0080-$ lnx-fu -u

System time: 2019-10-06 15:26:23.859

System: ASBSC asBSC1(111111) 0080-$ lnx-fu -e
Unit: PCUM-0
Sw packet: SG 9.32-0 3 System time: 2019-10-06 15:27:29.718
System: ASBSC asBSC1(111111)
Working state of units: Unit: PCUM-0
unit phys state info Sw packet: SG 9.32-0 3

OMU-0 0x00 WO-EX 0000: 0002 0000 0000 0000 000000FF 00000000 0000 4002 00 FFFF FFFF 0002 FFFF
EMB-0 WO-EX 0001: 0002 0001 FFFD FFFF FFFFFFFF 00000000 FFFF FFFF 00 FFFF FFFF FFFF FFFF
EMB-1 SP-EX 0002: 0206 0000 0000 0000 000000FF 00000000 FFFF FFFF 00 FFFF FFFF 0003 0003
MCMU-0 0x04 WO-EX 0003: 0206 0001 0025 0000 000000FF 00000000 FFFF FFFF 00 FFFF FFFF 0004 0002
MCMU-1 0x05 SP-EX 0004: 006A 0000 0000 0000 000000FF 00000000 0004 4105 00 FFFF FFFF 0005 0005
RRMU-0 0x58 WO-EX 0005: 006A 0001 0025 0000 000000FF 00000000 0005 4105 00 FFFF FFFF 0006 0004
RRMU-1 0x59 SP-EX 0006: 0148 0000 0000 0000 000000FF 00000000 0058 70DE 00 FFFF FFFF 0007 0007
BCXU-0 0x43 WO-EX 0007: 0148 0001 0025 0000 000000FF 00000000 0059 70DE 00 FFFF FFFF 0008 0006
BCXU-1 0x44 WO-EX 0008: 012B 0000 0000 0000 000000FF 00000000 0043 4377 00 FFFF FFFF 0009 FFFF
BCXU-2 0x45 SP-EX 0009: 012B 0001 0000 0000 000000FF 00000000 0044 4375 00 FFFF FFFF 000A FFFF
ETMA-0 0x6D WO-EX 000A: 012B 0002 0025 0000 000000FF 00000000 0045 4376 00 FFFF FFFF 000C FFFF
ETMA-1 0x6E WO-EX 000B: 012B 0003 FFFF FFFF FFFFFFFF FFFFFFFF FFFF FFFF FF FFFF FFFF FFFF FFFF
ETME-0 0x60 WO-EX 000C: 012C 0000 0000 0000 000000FF 00000000 006D 70EE 00 FFFF FFFF 000D FFFF
ETME-1 0x61 SP-EX 000D: 012C 0001 0000 0000 000000FF 00000000 006E 70EF 00 FFFF FFFF 000E FFFF
PCUM-0 0x80 WO-EX 000E: 0128 0000 0000 0000 000000FF 00000000 0060 70E0 00 FFFF FFFF 000F FFFF
PCUM-1 0x81 SP-EX 000F: 0128 0001 0025 0000 000000FF 00000000 0061 70E1 00 FFFF FFFF 0010 FFFF
0010: 0129 0000 0000 0000 000000FF 00000000 0080 70FB 00 FFFF FFFF 0011 FFFF
0080-$ 0011: 0129 0001 0025 0000 000000FF 00000000 0081 70FC 00 FFFF FFFF FFFF FFFF
END OF DATA

54 © 2019 Nokia RN23930

0080-$
 LinDX Commands
Reading SW Catalogs and Loaded Packets
0080-$ lnx-swlist -h
lnx-swlist: Utility for reading /swcatalog file

Usage: lnx-swlist [OPTIONS]

Options:
-f PATTERN Find files from swcatalog that match PATTERN using regex.
-i Print loaded packet id
-l Print list of loaded PACs LNX715G4.PAC 4.2-0 17/05/05 PLAENVY2.PAC 60.46-0
LNX714G4.PAC 4.16-0 18/05/22 PLAENVY2.PAC 60.46-0
Example: LNX712G4.PAC 4.3-0 18/03/07 PLAENVY2.PAC 60.46-0
lnx-swlist -f msgmon LNX710G4.PAC 4.1-0 17/05/05 PLAENVY2.PAC 60.46-0
LNX70FG4.PAC 4.1-0 17/05/05 PLAENVY2.PAC 60.46-0
0080-$ lnx-swlist -l LNX70EG4.PAC 4.1-0 17/05/05 PLAENVY2.PAC 60.46-0
LN071C09.PAC 18.7-2 18/07/06 PLAENVY2.PAC 60.46-0 LNX70DG4.PAC 4.1-0 17/05/05 PLAENVY2.PAC 60.46-0
LNXAC7G4.PAC 1.17-1 18/09/01 PLAENVY2.PAC 60.46-0 LNX70CG4.PAC 4.3-0 18/06/15 PLAENVY2.PAC 60.46-0
LNXAC6G4.PAC 3.2-3 18/11/20 BXXENVSG.PAC 9.32-0 LNX70BG4.PAC 3.13-0 19/01/11 PLAENVY2.PAC 60.46-0
LNXAC2G4.PAC 1.4-0 17/09/02 PLAENVY2.PAC 60.46-0 LNX70AG4.PAC 9.6-0 17/12/11 PLAENVY2.PAC 60.46-0
LNXABFG4.PAC 2.2-0 17/07/19 PLAENVY2.PAC 60.46-0 LNX709G4.PAC 8.7-0 18/10/11 PLAENVY2.PAC 60.46-0
LNXAB7G4.PAC 2.1-0 17/05/05 PLAENVY2.PAC 60.46-0 LNX708G4.PAC 5.1-0 17/05/05 PLAENVY2.PAC 60.46-0
LNXAB3G4.PAC 3.1-0 17/05/05 PLAENVY2.PAC 60.46-0 LNX707G4.PAC 8.5-0 18/06/27 PLAENVY2.PAC 60.46-0
LNXA9DG4.PAC 1.9-0 18/09/14 PLAENVY2.PAC 60.46-0 LNX706G4.PAC 4.1-0 17/05/05 PLAENVY2.PAC 60.46-0
LNXA8FG4.PAC 2.1-0 17/05/05 PLAENVY2.PAC 60.46-0 LNX705G4.PAC 5.5-0 18/05/17 PLAENVY2.PAC 60.46-0
LNXA86G4.PAC 1.5-0 17/07/24 PLAENVY2.PAC 60.46-0 LNX704G4.PAC 4.1-0 17/05/05 PLAENVY2.PAC 60.46-0
LNX98CG4.PAC 2.1-0 17/05/05 PLAENVY2.PAC 60.46-0 LNX703G4.PAC 4.2-0 17/09/01 PLAENVY2.PAC 60.46-0
LNX988G4.PAC 4.11-0 18/06/11 PLAENVY2.PAC 60.46-0 LNX702G4.PAC 6.12-25 18/05/29 PLAENVY2.PAC 60.46-0
LNX978G4.PAC 4.5-0 18/04/10 PLAENVY2.PAC 60.46-0 LNX701G4.PAC 4.4-0 17/12/22 PLAENVY2.PAC 60.46-0
LNX92CG4.PAC 3.1-0 17/05/05 PLAENVY2.PAC 60.46-0 LNX6FFG4.PAC 7.9-0 18/04/23 PLAENVY2.PAC 60.46-0
LNX921G4.PAC 3.2-0 17/11/30 PLAENVY2.PAC 60.46-0 LNX6F8G4.PAC 4.5-0 17/12/26 PLAENVY2.PAC 60.46-0
LNX90BG4.PAC 4.1-0 17/05/05 PLAENVY2.PAC 60.46-0 LNXAC3G4.PAC 3.4-17 19/01/30 BXXENVSG.PAC 9.32-0
LNX71AG4.PAC 6.2-0 17/11/28 PLAENVY2.PAC 60.46-0 0080-$
LNX718G4.PAC 4.1-0 17/05/05 PLAENVY2.PAC 60.46-0
LNX716G4.PAC 6.3-1 18/02/22 PLAENVY2.PAC 60.46-0

55 © 2019 Nokia RN23930

PCU Log Handling

56 2018 RN23890

56 © 2019 Nokia
 LinDX Applications
Displaying Application Indexes > dai
0080-$ dai
------------------------------------------------------------
----> Command dai executed on [06/10/2019 14:36:58:262196] <- 134 MAC
--- 135 PFM
------------------------------------------------------------ 136 PCM
137 BGP
***************************************** 138 NS
* Application ID Application NAME 140 RL
***************************************** 141 QC
Application running on slow path 146 IDRS
1 SP_CM sp 148 IBNACC
2 DXROUTER 153 RL1
3 PMS-MA 156 RCH
7 ARS 157 DLUD
9 ST 172 ul_router
11 SYSMON 173 DTT
32 MGA 174 PFD
33 DGA 176 DLRLC
177 ULRLC
Application running on fast path 178 DLSCH
fp 179 ULSCH
101 FP_CM
103 PMS-SA 180 COM
104 fpsysmon 254 IPMR
105 FP_ST 0080-$
131 ABM
132 PDM
133 PSW

57 © 2019 Nokia RN23930

LinDX Applications and Log levels
0080-$ st-help dld
------------------------------------------------------------
----> Command st-help executed on [06/10/2019 14:41:21:262065] <----
------------------------------------------------------------
Usage: dld <processor type>{:[<application id>]
where processor type can be "fp" or "sp"
eg: dld sp
eg: dld sp:2

Display Log Details of a particular application

0080-$ dld sp
------------------------------------------------------------
----> Command dld executed on [06/10/2019 14:41:36:542007] <----
------------------------------------------------------------
Application [1]:SP_CM
LOG LEVEL:
WARNING,ERROR,CRITICAL
LOG SOFTWARE LEVEL: Displaying Log Documents (DLD) and their log level settings
APPLICATION,PLATFORM
st-help dld > help for displaying lod documets
Application [2]:DXROUTER
LOG LEVEL: dld sp > Displaying log documents for slowpath services
WARNING,ERROR,CRITICAL
LOG SOFTWARE LEVEL: dld fp > Displaying log documents for fastpath services
APPLICATION,PLATFORM

Application [3]:PMS-MA
LOG LEVEL:
WARNING,ERROR,CRITICAL
LOG SOFTWARE LEVEL:
APPLICATION,PLATFORM

Application [7]:ARS
LOG LEVEL:
WARNING,ERROR,CRITICAL
LOG SOFTWARE LEVEL:
APPLICATION,PLATFORM
58 © 2019 Nokia RN23930
Application log levels
• PCU has logs distributed from 0 to 11 levels, which can be seen by “sll” command.
• Each applications generates logs at 10 different levels
• Each level can be turned on and off at run time
• Warning and Error logs are switched ON by default. Broad classification is as follows:

0 LOG_NULL To Switch off the log

1 LOG_WARNING Warning level logs
2,3,4,5 LOG_INFO Information logs
6 LOG_ERROR Error logs, to be taken for all modules
7,8,9,10 Detail 1,2,3,4 More detailed information is sometimes required over Info logs
11 Critical

59 RN23880-V-19 © Nokia 2019

 PCU Log Handling in LinDX (1)
Setting Log Levels
0080-$ st-help sll
------------------------------------------------------------
----> Command st-help executed on [06/10/2019 17:18:13:552305] <----
------------------------------------------------------------
Usage: sll <processor type>[:<application id>] <log level>:...where processor type can be "fp" or "sp"
and possible values of log level are
1 - WARNING LOGS
2 - INFO1 LOGS
3 - INFO2 LOGS
4 - INFO3 LOGS
5 - INFO4 LOGS Setting Log Level Help
6 - ERROR LOGS -Log levels
7 - DETAIL1 LOGS
8 - DETAIL2 LOGS
9 - DETAIL3 LOGS
10 - DETAIL4 LOGS
11 - CRITICAL LOGS
eg: sll sp 1:2:3
eg: sll sp:15 1:2:3

Set log level of a particular application

Setting Log Level for fast path application
0080-$ 132 PDM (Packet Data Manager)
0080-$ sll fp:132 1:2:3:4:5:6:7:8:9:10:11
------------------------------------------------------------
----> Command sll executed on [06/10/2019 17:15:06:392132] <----
------------------------------------------------------------
LOG LEVELS SET Verifying the setting of logs with command
Use "dld" to verify dld (display log documents)
0080-$ dld fp

60 © 2019 Nokia RN23930

 PCU Log Handling in LinDX (2)
Displaying Log Levels Note: The Logs produced as a result of successful execution of this command will only be seen
0080-$ lnx-log -t T on the Service Terminal sessions that have enabled the display of Logs by executing the ‘lnx-
log -t T’ Command
12895 N-000 2019-10-06 17:18:16.22 lnx-fp-pcum:
CPF-LOG:[Unit:0x80][Layer:0][File:pdm_stats.c][Line:2774][Inst:0][App:132][LogSe
qNo:2630][LogLevel:DETAIL_4][LogMsg:Entering function
pdm_update_counter_avg_busy_channel
]

12896 N-000 2019-10-06 17:18:16.22 lnx-fp-pcum:

CPF-LOG:[Unit:0x80][Layer:0][File:pdm_stats.c][Line:3009][Inst:0][App:132][LogSe
qNo:2631][LogLevel:DETAIL_4][LogMsg:Value of total_tsl_num_dl[0] = 0
total_tsl_num_dl_tbf[0] =0
]

12897 N-000 2019-10-06 17:18:16.22 lnx-fp-pcum:

CPF-LOG:[Unit:0x80][Layer:0][File:pdm_stats.c][Line:3014][Inst:0][App:132][LogSe
qNo:2632][LogLevel:DETAIL_4][LogMsg:Value of cntr_curr_no_dl_tbfs_in_bts[0] = 0
]

12898 N-000 2019-10-06 17:18:16.22 lnx-fp-pcum:

CPF-LOG:[Unit:0x80][Layer:0][File:pdm_timers.c][Line:2653][Inst:0][App:132][LogS
eqNo:2633][LogLevel:DETAIL_4][LogMsg:Exit Function
pdm_handle_upd_statistics_timer_expiry with success
]

12899 N-000 2019-10-06 17:18:16.22 lnx-fp-pcum:

CPF-LOG:[Unit:0x80][Layer:0][File:pdm_main.c][Line:3416][Inst:0][App:132][LogSeq
No:2634][LogLevel:DETAIL_1][LogMsg:PDM Main State Machine Handled Event:128 in
State:1 succesfully
]

61 © 2019 Nokia RN23930

 PCU Log Handling in LinDX (3)
Copying Log Files to the OMU
• Instructions to collect log files from ETME, ETMA, and PCUM Functional Units (FUs) to OMU
0080-$ ls -lah /mnt/disk/log disk using cinder volume.
total 60M • In AirScale BSC, the log files in ETME, ETMA, and PCUM units are written to the mounted
drwxr-xr-x 4 root root 4.0K Oct 4 00:06 . cinder volume /mnt/disk/log in each unit.
drwxr-xr-x 5 root root 4.0K Oct 4 00:07 ..
drwxr-xr-x 2 root root 4.0K Oct 6 09:20 config • The lnx-dxfile-cp command can be used to copy log files from ETME, ETMA, and PCUM
drwxr-xr-x 2 root root 4.0K Oct 4 00:06 cores units to the OMU disk.
-rw------- 1 root root 60M Oct 6 22:27 messages
0080-$

0080-$ lnx-dxfile-cp /mnt/disk/log/messages OMU:W0-/PCUALX/ASBSC1PCU0

• Step example to copy log files from mounted cinder volume of ETME, ETMA, and PCUM
0000-MAS> X:W0-/PCUALX/ units to WDU volume of OMU disk

VOLUME OMU_W1 .DIR

INITIALIZED BY XY 18-03-20 LAST WRITE 19-10-06
DIRECTORY OF /PCUALX/
INITIALIZED BY XY 2019-10-06 22:18:50.16 LAST WRITE 19-10-06

NUM NAME EXT VER SIZE FREE CREATED LAST MOD INI ATTR LOCKED BY
YY-MM-DD YY-MM-DD
0009 ASBSC1PCU0 . :01 0001DCA6 00000000 19-10-06 19-10-06 D A
TOTAL 0001DCA7( INCLUDING FIDS )

LISTED LABELS 00000001

0094BD18H BLOCKS USED OF TOTAL 0C800000H BLOCKS ( 95 % FREE )

0000-MAS>

62 © 2019 Nokia RN23930

 PCU Log Handling in LinDX (3)
Copying Log Files from the OMU to your PC

0000-MAS> X:W0-/PCUALX/

VOLUME OMU_W1 .DIR

INITIALIZED BY XY 18-03-20 LAST WRITE 19-10-06
DIRECTORY OF /PCUALX/
INITIALIZED BY XY 2019-10-06 22:18:50.16 LAST WRITE 19-10-06

NUM NAME EXT VER SIZE FREE CREATED LAST MOD INI ATTR LOCKED BY
YY-MM-DD YY-MM-DD
0009 ASBSC1PCU0 . :01 0001DCA6 00000000 19-10-06 19-10-06 D A
TOTAL 0001DCA7( INCLUDING FIDS )

LISTED LABELS 00000001

0094BD18H BLOCKS USED OF TOTAL 0C800000H BLOCKS ( 95 % FREE )

0000-MAS>

63 © 2019 Nokia RN23930

 PCU Log Handling in LinDX
Procedure RELAY BSSGB
1. Display the applications in your PCU NS
dai GB
2. Set the log levels you want on the application you will monitor
PCM IBNACC
sll fp:132 1:2:3:4:5:6:7:8:9:10:11
3. Verify the log levels you have set in the previous step FastPath PDM PSW
Application#132
dld fp:132 IDRS ABM
4. Display the logs in Service Terminal
PFM
lnx-log –t T
RRM
5. Copy the log files from the PCU to the OMU
lnx-dxfile-cp /mnt/disk/log/messages OMU:W0-/PCUALX/ASBSC1PCU0 MAC QC

6. Extract the log files with FTT to your PC SSF

7. Set back the log levels to as they were on your application (ie warning,error,critical) DPM
sll fp:132 1:6:11 Gb/RRM
(2 vCPU)

64 © 2019 Nokia RN23930

ETME/A Service Terminal

65 2018 RN23890
65 © 2019 Nokia
LinDX commands in ETME /ETMA Service terminal
• Displaying Application in ETME 0: dai
0060-$ dai • Displaying Site Information for BCF 1: dbcfinfo
------------------------------------------------------------ 0060-$ dbcfinfo 1
----> Command dai executed on [06/10/2019 23:09:43:941011] <---- ------------------------------------------------------------
------------------------------------------------------------ ----> Command dbcfinfo executed on [06/10/2019 23:13:13:500976] <----
------------------------------------------------------------
*****************************************
Etp_bcf_id:0
* Application ID Application NAME Bcf_id:1
***************************************** BCF_M-plane_IP:10.31.196.217
Application running on slow path BCF_C/U-plane_IP:10.31.196.217
1 SP_CM Header Compression for UDP/IP:0
2 DXROUTER
Maximum Multiplexing packet size:300
3 PMS-MA Maximum Multiplexing wait time on ETP:2
7 ARS CS UDP MUX Port:c000
9 ST PS UDP MUX Port:c002
11 SYSMON Packet Delay Variation:5000
32 CCH
Total active calls:0
33 RF DL max buf len:0
DL num seg:0
Application running on fast path BCF used DL:0
101 FP_CM BCF used cs UL:0
103 PMS-SA
BCF used PS UL:0
104 fpsysmon MUX buf RTP pkt count:0
105 FP_ST CS UL octets rcvd:858
131 PKTRTR CS DL octets sent:858
132 CPHUL 0060-$
133 CPHDL
0060-$

66 RN23880-V-19 © Nokia 2019

 LinDX commands in ETME /ETMA Service terminal
• Display CS call information : detpcs
0060-$ st-help detpcs
------------------------------------------------------------
----> Command st-help executed on [06/10/2019 23:16:23:1047] <----
------------------------------------------------------------
Usage: detpcs
prints CS calls information

0060-$ detpcs
------------------------------------------------------------
----> Command detpcs executed on [06/10/2019 23:16:27:941188] <----
------------------------------------------------------------

Num CS calls Active :: 0

CCH_STATE :: 1, CCH_STATE_NORMAL
0060-$ detpcs all
------------------------------------------------------------
----> Command detpcs executed on [06/10/2019 23:16:30:461034] <----
------------------------------------------------------------

Total running calls :: 0

0060-$

67 RN23880-V-19 © Nokia 2019

 LinDX commands in ETME /ETMA Service terminal
0060-$ st-help
st-help in ETME
------------------------------------------------------------
----> Command st-help executed on [06/10/2019 23:22:27:361241] <----
------------------------------------------------------------ olp_set_limit | Manually set OLP limits by changing to 'Manual' Mode
----------------------------------------------------- olp_get_limit | Will Display the currently set OLP limits
Detailed help and syntax of any command can be displayed olp_set_mode | Set OLP's Mode of Operation
by typing st-help <command name> olp_get_mode | Get OLP's Current Mode of Operation
For e.g.: st-help ssv olp_set_load | Set Core Load Manually
----------------------------------------------------- olp_get_load | Get Current Total Core Load
dsca | Display Statistics for a specific CAtegory
----------------------------------------------------- dsco | Display Statistics for a specific COunter
Command | Description rsca | Reset Statistics for a specific CAtegory
----------------------------------------------------- rsco | Reset Statistics for a specific COunter
detpcs | prints CS calls information 0060-$
app_debug | prints the Data packets statistics
all_debug_info | prints the statistics info on card
dbcfinfo | displays bcf information
dpdul | Displays Packets Dropped in Uplink
dpddl | Displays Packets Dropped in Downlink
dudul | Displays UDP packets passed in Uplink
duddl | Displays UDP packets passed in Downlink
rf_unit_status | Displays rf and switchover related status
dbscp | Display BSC parameters configured in ETME
st-help | Display Help and syntax of Service Terminal Commmands
ssv | Display software version
dai | Display Application ids to name mapping
dbu | Display buffer Statistics
dtu | Display Timer Statistics
sll | Set log level of a particular application
ssl | Set software level of a particular application
dld | Display Log Details of a particular application

68 RN23880-V-19 © Nokia 2019

 LinDX commands in ETME /ETMA Service terminal
LinDX processes in ETME
0060-$ lnx-launcher -L lnx-dxfile-iomana-d 2150 F 0 Y 1 running
lnx-dxfile-rmemfs-d 579 2A0 0 Y 0 running
NAME PID DMXPID C R P STATE lnx-ethmana-d 2211 3CA 0 Y 1 running
lnx-dxdiag-d 2213 A3 0 Y 1 running lnx-fp-etme 2830 ACE 1 N 3 running
lnx-dmxmsg-epo-d 474 66B 2 N 0 running lnx-dmxrtemu-d 513 0 0 Y 0 running
lnx-sysmon-diq-d 2264 626 0 Y 1 running lnx-ikeconf-d 2509 617 0 Y 3 running
lnx-random-writer 2262 AB7 1 N 1 finished lnx-fu-rcy-d 518 A0 2 N 0 running
lnx-swlist-d 2203 205 0 Y 1 running lnx-fu-fuzzi-d 514 103 2 N 0 running
lnx-dxerr-load 2149 0 N 1 finished lnx-ipconf-d 2151 43E 0 Y 1 running
lnx-rsterm-d-be 578 BE 0 Y 0 running lnx-lalarm-d 542 143 1 N 0 running
lnx-rsterm-d-bf 577 BF 0 Y 0 running lnx-blackbox-d 2215 978 0 Y 1 running
lnx-lieser-d 538 43B 1 N 0 running lnx-setup 337 1 N 0 finished
lnx-dmxmsg-distmon-d 2147 C1 0 Y 1 running
lnx-unabom-d 516 A1 0 Y 0 running ( C = criticality, R = restartable, P = starting phase )
lnx-lrm-d 2290 13B 0 Y 1 running
lnx-sysmon-cpupro-d 2266 FF 0 Y 1 running
lnx-ntpconf-d 2829 B2E 0 Y 3 running 0060-$
lnx-ns-d 2200 260 0 Y 1 running
lnx-sysmon-lmp-d 2270 47B 0 Y 1 running
lnx-6wind-monitor 1916 AC6 1 N 0 running
lnx-dxfile-loader 580 705 1 N 0 finished
lnx-6wind-starter 544 AC6 1 N 0 finished
lnx-dxfile-femser-d 576 90 0 Y 0 running
lnx-csagent-d 2208 671 0 Y 1 running
lnx-log-sender-d 2198 3BD 0 Y 1 running
lnx-log-syslog-d 336 0 Y 0 running
lnx-log-klog-d 338 0 Y 0 running
lnx-dik-d 2259 72C 0 Y 1 running
lnx-hwapi-rps-enabler 539 0 N 0 finished
lnx-sysmon-d 2146 777 1 N 1 running
lnx-sp-etme 2508 9FB 1 N 3 running
lnx-gersup-d 2516 A30 0 Y 3 running
69 RN23880-V-19 © Nokia 2019
 LinDX commands in ETME /ETMA Service terminal
Network Interfaces in ETME
QRI:ETME,0;

ASBSC asBSC1 2019-10-06 23:34:28

INTERROGATING NETWORK INTERFACE DATA

UNIT ADMIN ADDR

INTERFACE STATE MTU ATTR IP ADDRESS
------------ ----- ----- -------- ---------------------------------------------
ETME-0
EL0 UP 1500 PI 10.20.98.10/24
NTP
EL1 UP 1500 P 10.2.122.17/25
MONITORING 0060-$ route
EEP GW: route
EL4 UP 1500 LI 10.0.2.6/24 Kernel IP routing table
EEP Destination Gateway Genmask Flags Metric Ref Use Iface
EL5 UP 1500 L 10.2.123.13/26 1.1.1.0 * 255.255.255.0 U 0 0 0 fpn0
ABIS 10.0.2.0 * 255.255.255.0 U 0 0 0 el4
10.2.122.0 * 255.255.255.128 U 0 0 0 el1
COMMAND EXECUTED 10.2.123.0 * 255.255.255.192 U 0 0 0 el5
10.20.0.0 * 255.255.248.0 U 0 0 0 emb0
10.20.98.0 * 255.255.255.0 U 0 0 0 el0
10.30.0.0 * 255.255.248.0 U 0 0 0 emb1
0060-$

70 RN23880-V-19 © Nokia 2019

 LinDX commands in ETME /ETMA Service terminal
QRI:ETMA,; Network Interfaces in ETMA
ASBSC asBSC1 2019-10-06 23:39:41

INTERROGATING NETWORK INTERFACE DATA

UNIT ADMIN ADDR

INTERFACE STATE MTU ATTR IP ADDRESS
------------ ----- ----- -------- ---------------------------------------------
ETMA-0
006D-$ route
EEP GW > route
EL0 UP 1500 PI 10.20.98.9/24
Kernel IP routing table
NTP Destination Gateway Genmask Flags Metric Ref Use Iface
EL1 UP 1500 P 10.2.122.9/25
1.1.1.0 * 255.255.255.0 U 0 0 0 fpn0
MONITORING 10.0.2.0 * 255.255.255.0 U 0 0 0 el4
EL4 UP 1500 LI 10.0.2.3/24
10.2.122.0 * 255.255.255.128 U 0 0 0 el1
EEP
10.2.123.192 * 255.255.255.240 U 0 0 0 el5
EL5 UP 1500 L 10.2.123.201/28 10.20.0.0 * 255.255.248.0 U 0 0 0 emb0
AOIP
10.20.98.0 * 255.255.255.0 U 0 0 0 el0
10.30.0.0 * 255.255.248.0 U 0 0 0 emb1
ETMA-1
10.31.196.217 10.0.2.6 255.255.255.255 UGH 0 0 0 el4
EL0 UP 1500 PI 10.20.98.14/24
006D-$
NTP
EL1 UP 1500 P 10.2.122.19/25 Destination BCF1 via EEP GW (ETME
EL4 UP 1500 LI
MONITORING
10.0.2.8/24
0)
EEP
EL5 UP 1500 L 10.2.123.203/28
AOIP

COMMAND EXECUTED

71 RN23880-V-19 © Nokia 2019

 LinDX commands in ETME /ETMA Service terminal
Displaying BSC parameters in ETMA > dbscp
006D-$ dbscp
------------------------------------------------------------
----> Command dbscp executed on [06/10/2019 23:45:03:591536] <----
------------------------------------------------------------
********************************
BSC parameters
******************************** OVERLOAD PARAMETERS
aoip_dscp_mapp -----------------------
cs_traff = 34 OLP: Critical Limit :90
csx_traff = 34 OLP: High Limit :80
aoip_vlan_prior_mapp OLP: Low Limit :70
priority_be = 0 OLP: Load Hysteresis :5
priority_af1 = 1 OLP: Time Hysteresis :10
priority_af2 = 3 006D-$
priority_af3 = 4
priority_af4 = 5
priority_ef = 6
aoip_wfq_weights
af4_wfg_weight = 5000
af3_wfg_weight = 5000
af2_wfg_weight = 5000
af1_wfg_weight = 5000
be_wfg_weight = 5000
max_cs_call_len = 180
base_rtp_udp_port = 49152
rtcp_admin_state = 0
packet_delay_var = 5
mca_feature_status = Disable

72 RN23880-V-19 © Nokia 2019

Appendix

73 2018 RN23890

73 © 2019 Nokia
Service terminal Exercises

• Exercise 1.
• Delete one Directory which include subdirectory and files in the Disk
• Exercise 2.
• Get the BSC C-number with Service terminal command. (how many ways to get BSC C-number in BSC ?)
•Exercise 3.
• Set the log level to 1:2:3:4:5:6:11 for Application ID ABM in PCUM.
• Exercise 4.
• How to check the log level setting for special application.

74 © 2019 Nokia
 PCU2 Application Software Architecture (S11.5)
BCSU, MCMU, OMU
8 5 2
Gb INTERFACE
SOFT WARE
PDM ABM BSSGP
RESOURCE
PCM MANAGEMENT PSW 3 Relay
1 SGSN
UL SCH
SOFT WARE
DL SCH
NS
UL QC DL QC PFM FR
6 4
7
AIR & ABIS BTS
SOFT WARE UL PC UL DL RLC
MAC
@DSP
PFD @PQII

75 RN23880-V-19 © Nokia 2019

PQ2 Application Modules 1/4
• PDM: Packet Data Manger
- Controls the entity for data transfer
- Performs the initial coding scheme selection and interpretation of multislot class for allocation of timeslots
- Sub-functionalities :
• Resource management:
- Allocation of air-resources
- BTS selection and admission control
- Interacts with ABM for edap resource reservations
- Interacts with PSW for requirements of additional territory
• TBF Management: Creation and Deletion of TBF
• PFC manager: Creation and admission of PFCs
- Log levels of 1:2:3:4:5:6 are helpful in case of PDM.

76 RN23880-V-19 © Nokia 2019

PQ2 Application Modules 2/4

• ABM: Abis manager:

- Allocates and manages abis resources including slave distribution etc
- Dynamic abis management every scheduling cycle for PFC’s informed by the Scheduler module
- ABIS resource reservation and allocation for streaming PFCs
- Error logs of ABM recommended
• PSW: Packet Switched Radio Resource Manager
- Does territory procedures and informs other modules of upgrade and downgrade requests.
- PSW logs of 1:2:3:4:5:6 shall be taken for cases related to additional territory as well

77 RN23880-V-19 © Nokia 2019

PQ2 Application Modules 3/4
• MAC: Medium Access Control
- Controls the entity of NCCR procedures
- Problems related to cell change shall be captured under all 1:2:3:4:5:6:7:8:9:10:11 levels of MAC logs

• PFM: Packet Flow Control Module

- Manages the BVC, MS and PFC flow control procedures.
- Only for problems related to flow control values bucket size, bucket leak rate etc.
- All PFM logs of 1:2:3:4:5:6:7:8:9:10:11 shall be taken

• PCM: PCCCH Channel Management

- PCM logs of 1:2:3:4:5:6 are required for tbf establishment on PCCCH

78 RN23880-V-19 © Nokia 2019

PQ2 Application Modules 4/4
• BSSGP
- Interacts with PDM and Relay for sending UL blocks to SGSN
- Data blocks are received from Relay and BSSGP sends it over GB in form of
BGP_UL_UNITDATA
- DL data is given to PDM by BSSGP
- Logs of 1:6 levels are preferred.
• NS, FR
- Layers for information and control functionality of Gb interface
- NS and FR error logs shall be taken
• RELAY
- UL RLC functionality of assembly of UL data blocks and transmission to GB through BSSGP
- Logs of 1:2:3:4:5:6 levels shall be set for problems related to UL data transfer

79 RN23880-V-19 © Nokia 2019

DSP Application Modules 1/2
• SCH: Scheduler
- Scheduler module runs scheduling algorithm for UL and DL data.
- Interacts with RLC and ABM to decide on MCS to be used for transmission data
- Divided into two sub-modules –> UL and DL Scheduler
• RLC: Radio Link Control
- Implements ACK and UNACK mode of TBF for sending and receiving rlc data blocks
- Implemented in two sub-modules as DL and UL RLC
• DL RLC:
- Sends the data received from PDM, in DL direction
- Interprets DL_Ack_Nack sent from MS
- Maintains window for DL data
• UL RLC:
- Receives the UL data
- Generates UL_Ack_Nack
- Maintains acked/nacked information of UL data blocks

80 RN23880-V-19 © Nokia 2019

DSP Application Modules 2/2
• PFD: Packet Framer Deframer
- Maintains synch on ABIS
- Assembles UL data received on master and slave channels and sends it to Scheduler
- In downlink direction it distributes the data received from scheduler into master and slave channels over ABIS

• QC: Quality Control

- Maintains counts for bit rate being achieved by PFCs for which data transfer is ongoing
- Informs other modules for appropriate action to be taken, i.e.:
• Downgrade of PFC QOS
• Dropping the PFC
• Triggering the cell change procedure

81 RN23880-V-19 © Nokia 2019

<Document ID: change ID in footer or remove> <Change