PCU2 Service Terminal Commands

Nokia Siemens Networks GSM/EDGE BSS, rel. RG10(BSS), operating documentation, issue 05

PCU2 Service Terminal Commands

DN0479352

Issue 4-2Approval Date 28.8.2009

2 DN0479352Issue 4-2


Id:0900d805806444c9

The information in this document is subject to change without notice and describes only the product defined in the introduction of this documentation. This documentation is intended for the use of Nokia Siemens Networks customers only for the purposes of the agreement under which the document is submitted, and no part of it may be used, reproduced, modified or transmitted in any form or means without the prior written permission of Nokia Siemens Networks. The documentation has been prepared to be used by professional and properly trained personnel, and the customer assumes full responsibility when using it. Nokia Siemens Networks welcomes customer comments as part of the process of continuous development and improvement of the documentation.

The information or statements given in this documentation concerning the suitability, capacity, or performance of the mentioned hardware or software products are given "as is" and all liability arising in connection with such hardware or software products shall be defined conclusively and finally in a separate agreement between Nokia Siemens Networks and the customer. However, Nokia Siemens Networks has made all reasonable efforts to ensure that the instructions contained in the document are adequate and free of material errors and omissions. Nokia Siemens Networks will, if deemed necessary by Nokia Siemens Networks, explain issues which may not be covered by the document.

Nokia Siemens Networks will correct errors in this documentation as soon as possible. IN NO EVENT WILL Nokia Siemens Networks BE LIABLE FOR ERRORS IN THIS DOCUMENTA-TION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDI-RECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY OR DATA,THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATION IN IT.

This documentation and the product it describes are considered protected by copyrights and other intellectual property rights according to the applicable laws.

The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark of Nokia Corporation. Siemens is a registered trademark of Siemens AG.

Other product names mentioned in this document may be trademarks of their respective owners, and they are mentioned for identification purposes only.

Copyright © Nokia Siemens Networks 2010. All rights reserved

f Important Notice on Product Safety Elevated voltages are inevitably present at specific points in this electrical equipment. Some of the parts may also have elevated operating temperatures.

Non-observance of these conditions and the safety instructions can result in personal injury or in property damage.

Therefore, only trained and qualified personnel may install and maintain the system.

The system complies with the standard EN 60950 / IEC 60950. All equipment connected has to comply with the applicable safety standards.

The same text in German:

Wichtiger Hinweis zur Produktsicherheit

In elektrischen Anlagen stehen zwangsläufig bestimmte Teile der Geräte unter Span-nung. Einige Teile können auch eine hohe Betriebstemperatur aufweisen.

Eine Nichtbeachtung dieser Situation und der Warnungshinweise kann zu Körperverlet-zungen und Sachschäden führen.

Deshalb wird vorausgesetzt, dass nur geschultes und qualifiziertes Personal die Anlagen installiert und wartet.

Das System entspricht den Anforderungen der EN 60950 / IEC 60950. Angeschlossene Geräte müssen die zutreffenden Sicherheitsbestimmungen erfüllen.

DN0479352Issue 4-2

3


Id:0900d805806444c9

Table of ContentsThis document has 196 pages.

Summary of changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

1 Overview of PCU2 service terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101.1 Service terminal in PCU2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101.2 Special characteristics of service terminal commands . . . . . . . . . . . . . 101.3 Service terminal prompt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111.4 Service terminal login delays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121.5 Service terminal connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131.6 Service terminal commands output . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131.7 Disclaimer and welcome note . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

2 Service terminal commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152.1 Service terminal general purpose commands . . . . . . . . . . . . . . . . . . . . 152.1.1 exit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152.1.2 esd (enable system dumps). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152.1.3 dsd (disable system dumps) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162.1.4 doe (display operating system error logs) . . . . . . . . . . . . . . . . . . . . . . . 162.1.5 dpi (display PCU2 PIU information) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172.1.6 dem (display elapsed milliseconds) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182.1.7 eeqm (enable event queue monitoring) . . . . . . . . . . . . . . . . . . . . . . . . . 182.1.8 deqm (disable event queue monitoring). . . . . . . . . . . . . . . . . . . . . . . . . 192.1.9 deqs (display event queue statistics) . . . . . . . . . . . . . . . . . . . . . . . . . . . 192.1.10 ecm (enable continuous mode) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212.1.11 dcm (disable continuous mode) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222.1.12 dbl (display bootup log) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222.1.13 dai (display application IDs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282.1.14 daa (display active alarms) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302.1.15 uad (update authentication data) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312.2 Operating system commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312.2.1 keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312.2.2 help/? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322.2.3 date . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322.2.4 time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332.2.5 ver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332.2.6 ls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332.2.7 cat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342.2.8 rm. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342.3 Service terminal logging to file commands . . . . . . . . . . . . . . . . . . . . . . 352.3.1 esl (enable ST logging) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352.3.2 dsl (disable ST logging) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362.3.3 dlfi (display logging to a file information) . . . . . . . . . . . . . . . . . . . . . . . . 362.3.4 remove (remove logging files) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372.3.5 > command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382.4 Process manipulation commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402.4.1 ps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

4 DN0479352Issue 4-2


Id:0900d805806444c9

2.5 Statistics commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432.5.1 dbu (display buffers per unit) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442.5.2 dbp (display buffer statistics per process). . . . . . . . . . . . . . . . . . . . . . . . 462.5.3 dbs (display buffer statistics of particular size) . . . . . . . . . . . . . . . . . . . . 472.5.4 dtp (display timer statistics per process) . . . . . . . . . . . . . . . . . . . . . . . . . 492.5.5 dtu (display timer statistics per unit) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 502.5.6 dsca (display statistics counter for specific category) . . . . . . . . . . . . . . . 512.5.7 dsco (display statistics for a specific counter). . . . . . . . . . . . . . . . . . . . . 522.5.8 rsca (reset statistics counter for specific category) . . . . . . . . . . . . . . . . . 542.5.9 rsco (reset statistics for a specific counter) . . . . . . . . . . . . . . . . . . . . . . . 552.6 Utilities - Black Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 552.6.1 abb (analyze black box) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 552.6.2 mbbrbb (multiple black box read black box) . . . . . . . . . . . . . . . . . . . . . . 622.7 Utilities - logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 642.7.1 sll (set the log level) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 642.7.2 ssl (set the software layer) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 662.7.3 slf (set the logger feature) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 682.7.4 dld (display the log details) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 692.7.5 dlf (display the logger feature) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 702.7.6 efl (enable logging to file) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 712.7.7 dfl (disable logging to file) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 712.8 Utilities - software manipulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 722.8.1 reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 722.8.2 ssv (show the software version) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 732.8.3 ubs (upgrade boot software) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 732.9 Utilities - message monitoring, manipulation, and IPC . . . . . . . . . . . . . . 742.9.1 emm (enable message monitoring) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 742.9.2 dmm (disable message monitoring) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 772.9.3 dimm (display message monitoring configuration) . . . . . . . . . . . . . . . . . 782.9.4 damm (disable all message monitoring) . . . . . . . . . . . . . . . . . . . . . . . . . 792.9.5 emml (enable MM data logging) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 802.9.6 dmml (disable MM data logging) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 802.10 IP manipulation commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 812.10.1 ifconfig. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 812.10.2 netstat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 832.10.3 ping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 872.10.4 ping6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 892.11 Radio network–related commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 902.11.1 dtrxrnw (display the radio network configuration for a particular TRX) . . 912.11.2 dbtsrnw (display the radio network configuration for a particular BTS). . 922.11.3 dsegrnw (display the radio network configuration for a particular segment)

942.12 TBF information commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 952.12.1 dsegtbf (display TBF allocation for a particular segment) . . . . . . . . . . . . 952.12.2 dtrxtbf (display the TBF information for a particular TRX). . . . . . . . . . . . 982.12.3 dtfitbf (display the TBF information specific to identified TFI) . . . . . . . . 1002.12.4 dtsltbf (display the TBF information specific to identified TSL) . . . . . . . 102

DN0479352Issue 4-2

5


Id:0900d805806444c9

2.12.5 dpcutbf (display number of UL and DL TBFs for all active segments in the PCU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

2.13 Gb–related commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1062.13.1 dgb (display Gb configuration) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1062.13.2 egbm (enable Gb monitoring) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1072.13.3 dgbm (disable Gb monitoring) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1092.13.4 digbm (display Gb monitoring) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1092.13.5 egbl (enable Gb data logging) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1102.13.6 dgbl (disable Gb data logging) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1112.14 Subscriber monitoring–related commands . . . . . . . . . . . . . . . . . . . . . 1112.14.1 esm (enable subscriber monitoring). . . . . . . . . . . . . . . . . . . . . . . . . . . 1112.14.2 dsm (disable subscriber monitoring) . . . . . . . . . . . . . . . . . . . . . . . . . . 1122.14.3 dism (display subscriber monitoring) . . . . . . . . . . . . . . . . . . . . . . . . . . 1132.14.4 esml (enable subscriber monitoring data logging) . . . . . . . . . . . . . . . . 1132.14.5 dsml (disable subscriber monitoring data logging). . . . . . . . . . . . . . . . 1142.15 User plane monitoring–related commands . . . . . . . . . . . . . . . . . . . . . 1142.15.1 eup (enable user plane monitoring) . . . . . . . . . . . . . . . . . . . . . . . . . . . 1152.15.2 dup (disable user plane monitoring). . . . . . . . . . . . . . . . . . . . . . . . . . . 1162.15.3 diup (display user plane monitoring) . . . . . . . . . . . . . . . . . . . . . . . . . . 1162.15.4 eupl (enable user plane data logging) . . . . . . . . . . . . . . . . . . . . . . . . . 1172.15.5 dupl (disable user plane data logging) . . . . . . . . . . . . . . . . . . . . . . . . . 1182.16 Frame relay–related commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1182.16.1 dfc (display frame relay configuration) . . . . . . . . . . . . . . . . . . . . . . . . . 1182.17 General category commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1202.17.1 dpt (display system level trace pending table) . . . . . . . . . . . . . . . . . . . 1202.18 Telnet server administration commands . . . . . . . . . . . . . . . . . . . . . . . 1202.18.1 etc (enable telnet for specified IP address or for all IPs) . . . . . . . . . . . 1212.18.2 dtc (disable telnet for specified IP address or for all IPs). . . . . . . . . . . 1212.18.3 tcstatus (display list of authenticated IP for telnet connections) . . . . . 1222.19 NCCR commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1232.19.1 dnc0ms (display number of mobile stations in NC0 mode) . . . . . . . . . 1232.19.2 dnc2ms (display the number of mobile stations in NC2 mode) . . . . . . 1232.19.3 dnccrms (display the NCCR data of mobile stations specified) . . . . . . 1242.20 NACC commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1252.20.1 dnacc (display the NACC related neighbour cell configuration data). . 1252.20.2 dpsinacc (display the neighbour cell SI or PSI messages) . . . . . . . . . 1252.20.3 dsinacc (display the SI messages of given segment) . . . . . . . . . . . . . 1262.21 Gb over IP commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1272.21.1 dgbipbvc (display the information about certain BVC) . . . . . . . . . . . . . 1272.21.2 dgbipnsei (display the information about certain NSE) . . . . . . . . . . . . 1282.21.3 dgbipnsvc (display the information about certain NSVC). . . . . . . . . . . 1282.22 DTM commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1292.22.1 ddimsi (display dedicated IMSI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1292.22.2 didtms (display internal DTM counters) . . . . . . . . . . . . . . . . . . . . . . . . 1302.22.3 ddtmimsi (delete DTM IMSI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1312.23 Service terminal commands for DSP and PCM allocation information 1312.23.1 ddspinfo (display DSP information) . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

6 DN0479352Issue 4-2


Id:0900d805806444c9

2.23.2 dpcminfo (display PCU-PCM information) . . . . . . . . . . . . . . . . . . . . . . 1322.23.3 dpcmdapinfo (display PCU-PCM information for the specified EDAP) . 1342.23.4 ddapinfo (display EDAP information) . . . . . . . . . . . . . . . . . . . . . . . . . . 1342.23.5 dabmtrxinfo (display the TRX information for the BTS in the specified seg-

ment). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1352.23.6 ddaptrxinfo (display TRX information for the specified DAP) . . . . . . . . 1362.23.7 dstslinfo (display sub-TSL info for the PCU-PCM line) . . . . . . . . . . . . . 1372.23.8 dgpinfo (display guard period information per DAP) . . . . . . . . . . . . . . . 1382.24 Cell monitoring commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1392.24.1 dcem (display cell monitoring data) . . . . . . . . . . . . . . . . . . . . . . . . . . . 1392.25 Service terminal command–related information . . . . . . . . . . . . . . . . . . 1422.25.1 Commands in continuous mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1422.25.2 Bootup phases and traces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1422.25.3 Application IDs for commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1512.25.4 Error code debugging information for abb and doe command output. . 1522.26 Error codes interpretation in case 'user_called' is 'false' (value 0) . . . . 1542.27 Error codes interpretation in case 'user_called' is 'true' (value 1) . . . . . 172

DN0479352Issue 4-2

7


Id:0900d805806444c9

List of FiguresFigure 1 PCU2 service terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Figure 2 Error code decoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

8 DN0479352Issue 4-2


Id:0900d805806444c9

DN0479352Issue 4-2

9

PCU2 Service Terminal Commands Summary of changes

Id:0900d80580623ab7

Summary of changesChanges between document issues are cumulative. Therefore, the latest document issue contains all changes made to previous issues.

Changes made between issues 4-2 and 4-1Information on the categories 72 and 79 has been added to subsection dsca (display statistics counter for specific category) in chapter Service terminal commands.

Changes made between issues 4-1 and 4-0In the Service terminal commands chapter, additional information on PCU2 boot upgrade instructions has been added.

Changes made between issues 4-0 and 3-1In the Overview of PCU2 service terminal chapter, information on the PQIII controller processor has been added.

In the Service terminal commands chapter:

• It has been specified that the examples and execution printouts apply to all PCU2 variants, unless otherwise specified.

• The examples and execution printouts of the following commands have been updated to include changes due to Downlink Dual Carrier: dtrxrnw, dbtsrnw, dsegrnw, dsegtbf, dtrxtbf, dtfitbf, dtsltbf, dpcutbf, ddspinfo, and dcem.

• The execution printout of the ps command has been updated to include new pro-cesses due to the PCU2-E.

• The execution printouts of the dai and ssv commands have been updated. • Counter information in examples and execution printouts has been revised in the fol-

lowing statistics commands: dsca, dsco, rsca, and rsco. • Segment ID information has been revised in the following commands: dnccrms,

dnacc, and dsinacc, and the text about the function of dsinacc has been modified. • The following commands have been removed: dsegtbfc, dbtstbfc, and dtrxtbfc. • Section Application IDs for commands has been updated.

10 DN0479352Issue 4-2


Id:0900d80580623aba

Overview of PCU2 service terminal

1 Overview of PCU2 service terminalService terminal is a visual display terminal connected to the PCU2 through a serial or an Ethernet interface. It is a specialist tool used in monitoring the system as well as in fault investigations. You can start a service terminal session either on a service terminal physically connected to a computer unit, via an Ethernet interface using the Telnet pro-tocol, or via the MML terminal by establishing a remote service terminal session using the appropriate MML command.

1.1 Service terminal in PCU2In the PCU2, the service terminal functionality is based on operating system embedded (OSE) shell running on a controller processor. The digital signal processors (DSPs) do not have a direct service terminal interface. Commands to the DSPs are sent via the controller processor.

The controller processor of the PCU2-D and PCU2-U units is PQII, while the PCU2-E unit uses PQIII instead of PQII. However, to maintain backward compatibility, PQIII is still referred to as PQII in all the service terminal command parameters, examples, and execution printouts in Service terminal commands.

The PCU2 service terminal operating environment is presented in the figure below:

Figure 1 PCU2 service terminal

1.2 Special characteristics of service terminal commandsPCU2 service terminal commands are different from the MML commands. When using the PCU2 service terminal commands, note that:

• The parameters are separated via a 'space' separator and commands are consid-ered to be complete and interpreted when the Enter key is pressed.

• Help on the PCU2 commands can be obtained by typing: • ? <command> • help <command>

BSC

RS232

Ethernet

Telnet clientMML or serviceterminal session

PCU2

OMU

BCSU

VDU orterminal emulator

DN0479352Issue 4-2

11

PCU2 Service Terminal Commands Overview of PCU2 service terminal

Id:0900d80580623aba

• help • The commands are case sensitive. The commands are entered using lower case

letters. • Some of the commands do not require parameters to be passed on to them.

Detailed help on each command and its syntax can be obtained by typing 'help <command name>'. The parameters are to be interpreted as explained below:

1.3 Service terminal promptService terminal prompt denotes the BCSU and the PCU ID along with the suffix 'OSE', which indicates that the service terminal is an OSE-based service terminal. This is to enable to distinguish between the Chorus-based and the OSE-based service terminal.

Parameter syntax Explanation

[<parameter>] Specifies that the parameter is optional and its value not mandatory to specify.

For example, the syntax of help command is

help/? [<command>]

This command can be executed as:

help ps

or

help

{parameter} Specifies that the parameter is conditionally optional and needs to be specified only under a certain condi-tion, as explained in the command description.

For example, the syntax of dbu command is

dbu <processor type>{:<dsp id>}

This command can be executed as:

dbu pq2

or

dbu dsp:1

but not

dbu dsp

<parameter> Specifies that the parameter is mandatory and its value must be specified.

For example, the syntax of

remove

command is

remove <filename>

This command must be executed as:

remove log_file_gb.log

but not

remove

12 DN0479352Issue 4-2


Id:0900d80580623aba


The service terminal prompt can be a combination of any of the suffixes specified above. For example, if you have enabled both the continuous mode and the message monitor-ing logging mode, the prompt will be BCSU/0/PCU/0/OSE/C/ML>

1.4 Service terminal login delaysIn case there is a delay of less than 60 seconds during the login via Telnet, the following message is displayed on the terminal.

login: qwe Password: /*** User Authorization Failure ***/ login: qwe Password: /*** User Authorization Failure ***/ login: qwe Password: /*** User Authorization Failure ***/ /***DELAY OF 5 SECONDS APPLIED.PLEASE WAIT***/ Connection to host lost.

Prompt Explanation

BCSU/XX/PCU/YY/OSE> The basic service terminal prompt denotes the BSCU and the PCU index. XX is the BSCU index and YY is the PCU index.

Possible suffixes Explanation

/C If the continuous mode is enabled, the service terminal prompt will change to indicate this. The prompt will be BCSU/0/PCU/0/OSE/C>

/L If the 'esl' command has been run, the service terminal logging mode has been switched on. The prompt is BCSU/0/PCU/0/OSE/L>

/ML If the 'emml' command has been run, the service terminal message monitoring logging mode has been switched on. The prompt will be BCSU/0/PCU/0/OSE/ML>

/GBL If the 'egbl' command has been run, the service terminal Gb interface monitoring logging mode has been switched on. The prompt will be BCSU/0/PCU/0/OSE/GBL>

/UPL If the 'eupl' command has been run, the service terminal user plane monitoring logging mode has been switched ON. The prompt will be BCSU/0/PCU/0/OSE/UPL>

/SML If the 'esml' command has been run, the service terminal subscriber monitoring logging mode has been switched ON. The prompt will be BCSU/0/PCU/0/OSE/SML>

DN0479352Issue 4-2

13

PCU2 Service Terminal Commands Overview of PCU2 service terminal

Id:0900d80580623aba

In case there is a delay of more than 60 seconds during the login via Telnet, the following message is displayed on the terminal.

C:\> login: asd Password: /*** User Authorization Failure ***//***DELAY APPLIED.PLEASE WAIT UNTIL <15.34>***/ Connection to host lost.

The printouts are the same for serial sessions.

For more information, see Information Security.

1.5 Service terminal connectivityThe service terminal can be accessed through a serial interface, Ethernet interface, or via the BSC MML. The sections below highlight how to access the service terminal through the various interfaces available.

Access through serial interfaceThe service terminal can be accessed locally through the serial interface. You need a username and a password for the access. If you are using a PC software environment and a third-party software, you need to configure a connection in the software to choose the correct COM port.

Access through Ethernet interfaceThe service terminal can be accessed through the Ethernet interface. You need a username and a password for the access. The access requires that you have a Telnet client from the source machine. The Ethernet interface is supported over IPv4. IPv6 is not supported in the service terminal interface.

As a default, the Ethernet connection is disabled. You can enable it with the etc command.

Remote session to the PCU on MML terminalFor instructions on starting a remote session to the PCU on MML terminal, see Starting a service terminal session in Service Terminal Essentials.

1.6 Service terminal commands outputAll the service terminal command execution printouts contain a header, which displays the date and a timestamp. This enables you to do offline analysis especially in commands related to statistics measurement. The format of the header is:

----------------------------------------------------------- ---->Command XXX executed on [dd/mm/yyyy Hr:Min:Sec:Micro-Seconds] <---- -----------------------------------------------------------

XXX indicates the command name. For example, when the command ace is executed, the header format is:

----------------------------------------------------------- ---->Command ace executed on [1/1/2004 0:0:5:260001] <---- -----------------------------------------------------------

14 DN0479352Issue 4-2


Id:0900d80580623aba


1.7 Disclaimer and welcome noteThe following disclaimer and welcome notes are displayed when you log into a plug-in unit through the service terminal.

In the welcome message, the characters 'xx' are the BCSU ID and the character 'x' is the PCU ID.

WELCOME TO IMS GW SERVICE TERMINAL DIALOGUE, BCSU-xx, PCU-x, 2003-09-26 10:06:10

IMS GW SERVICE TERMINAL IS A SPECIALIST TOOL. UNAUTHORIZED USAGEMAY CAUSE DAMAGE

DN0479352Issue 4-2

15

PCU2 Service Terminal Commands Service terminal commands

Id:0900d805806444bc

2 Service terminal commandsThe service terminal command examples and execution printouts apply to all PCU2 vari-ants, unless otherwise specified.

2.1 Service terminal general purpose commandsThe commands described below relate to the PCU2 as a complete system.

2.1.1 exit

FunctionWith this command you exit the current session and return to the login prompt.

Syntaxexit

Examples

1. Exit the service terminal session.exit

Execution printoutsBCSU/0/PCU/0/OSE>exit ----------------------------------------------------------------> Command exit executed on [1/1/2004 0:0:43:569039] <---- ------------------------------------------------------------exiting... username:

2.1.2 esd (enable system dumps)

FunctionWith this command you enable system dumps. By default, when you log into the plug-in unit (PIU) through the service terminal, you will not get any traces/logs on the screen. This functionality has been added so that you can do the desired operation and not be disturbed by frequent traces.

Syntaxesd

Examples

1. Enable system dumps on the existing service terminal session.esd

Execution printoutsBCSU/0/PCU/0/OSE>esd ----------------------------------------------------------------> Command esd executed on [1/1/2004 0:2:27:410001] <---- ------------------------------------------------------------Flag for Service Terminal application id [30] is changed to ENABLE SYSTEM DUMP.

16 DN0479352Issue 4-2


Id:0900d805806444bc

Service terminal commands

2.1.3 dsd (disable system dumps)

FunctionWith this command you disable system dumps. After you have given this command, the output of the logging and traces messages will not appear on the screen.

Syntaxdsd

Examples

1. Disable system dumps on the existing service terminal session.dsd

Execution printoutsBCSU/0/PCU/0/OSE>dsd ----------------------------------------------------------------> Command dsd executed on [1/1/2004 0:2:57:80001] <---- ------------------------------------------------------------esd Disabled for Service Terminal with APP ID:30

2.1.4 doe (display operating system error logs)

FunctionWith this command you can examine the operating system error logs in the PCU2 system. The full form of this command is display operating system error logs (doe). These error logs are maintained internally by the service terminal and will not survive in case of a PIU reboot. The last 20 error logs occurred are displayed for user analysis.

The error logs for the DSP processors are maintained on a global level, not per DSP.

To debug the error code, see section Error code debugging information for abb and doe command output.

Syntaxdoe <processor type>

Parameter explanationsprocessor type

With this parameter you specify the processor type on which the application is residing. The allowed values are 'pq2' and 'dsp'.

Examples

1. Display the operating system error logs for the PQII processor.doe pq2

2. Display the operating system error logs for the DSP processor.doe dsp

Execution printoutsThe parameters used in the execution printout:

User called Specifies if the error was a result of application calling or kernel calling. In case of application calling, the value is '1', and otherwise '0'.

DN0479352Issue 4-2

17


Id:0900d805806444bc

Error code Specifies the error code used by the user/kernel to indicate which error caused a call to the error handler.

Extra Specifies the extra information used in debugging the error code.

Process name Process name is a string showing the name of the process or block. It specifies the process name of the application/platform processes.

Process ID Specifies the process ID.

File File is a string showing the file name from which the current system call was issued. This field is invalid if the line is 0. Line and file information is available only if the PCU2 software was compiled with the debug option.

Line Line is an integer containing the source code line from which the current system call was issued. Line is 0 if no line and file information is avail-able. Line and file information is available only if the PCU2 software was compiled with the debug option.

BCSU/0/PCU/0/OSE>doe pq2 ----------------------------------------------------------------> Command doe executed on [1/1/2004 0:3:35:190001] <---- ------------------------------------------------------------PQ2 OS error logs ================= User called : 0x0 Error code : 0x00110031Extra : 0x073aff34 Process Name : errhnd Process ID : 0x00030042 File : xyz.cLine : 31

User called : 0x1 Error code : 0x00000001 Extra : 0x00000000 Process Name : errhnd Process ID : 0x00050042 File : xyz.c Line : 37

2.1.5 dpi (display PCU2 PIU information)

FunctionWith this command you display the hardware-related information. The full form of this command is display PCU2 PIU hardware information (dpi). The command displays the cartridge, slot, and section of the PIU. In the current BSC hardware, it always specifies the value '1' for all the parameters.

Syntaxdpi

18 DN0479352Issue 4-2


Id:0900d805806444bc


Examples

1. Display the PCU2 PIU information.dpi

Execution printoutsBCSU/0/PCU/0/OSE>dpi ----------------------------------------------------------------> Command dpi executed on [1/1/2004 0:1:20:821567] <---- ------------------------------------------------------------========================================== PCU plug-in unit information ==========================================Slot ID : 6 Section ID : 1 Boot Image Software Version : PLTF2.15P3 ========================================== Dumping Card Identification register ========================================== Variant : 0x0 Interchangeability : 0x0 Unit Type : 0x3f8

2.1.6 dem (display elapsed milliseconds)

FunctionWith this command you display the elapsed milliseconds since the last system restart. The full form of this command is display elapsed milliseconds (dem).

Syntaxdem

Examples

1. Display the elapsed milliseconds since the last system restart.dem

Execution printoutsBCSU/0/PCU/0/OSE>dem ----------------------------------------- ----> Command dem executed on [1/1/2004 0:5:19:330001] <---- -----------------------------------------Milliseconds elapsed since system restart [2350100] ==========================================================

2.1.7 eeqm (enable event queue monitoring)

FunctionWith this command you enable the event queue monitoring and will then be able to execute the command deqs to see the results. These statistics may help you in debug-

DN0479352Issue 4-2

19


Id:0900d805806444bc

ging the process communication-related problems. The full form of this command is enable event queue monitoring (eeqm).

Syntaxeeqm

Examples

1. Enable the event queue monitoring.eeqm

Execution printoutsBCSU/0/PCU/0/OSE>eeqm ----------------------------------------------------------------> Command eeqm executed on [1/1/2004 0:5:35:200001] <---- ------------------------------------------------------------ Event queue monitoring enabled

2.1.8 deqm (disable event queue monitoring)

FunctionWith this command you disable the event queue monitoring. The full form of this command is disable event queue monitoring (deqm).

Syntaxdeqm

Examples

1. Disable the event queue monitoring.deqm

Execution printoutsBCSU/0/PCU/0/OSE>deqm ----------------------------------------------------------------> Command deqm executed on [1/1/2004 0:6:10:520001] <---- ------------------------------------------------------------Event queue monitoring disabled

2.1.9 deqs (display event queue statistics)

FunctionWith this command you display useful statistics to assist you in debugging process com-munication-related problems. The full form of this command is display event queue sta-tistics (deqs).

Syntaxdeqs

Examples

1. Display the event queue statistics.deqs

20 DN0479352Issue 4-2


Id:0900d805806444bc


Execution printoutsBCSU/0/PCU/0/OSE>deqs ----------------------------------------------------------------> Command deqs executed on [1/1/2004 0:6:22:630001] <---- ------------------------------------------------------------ Event queue statistics -------------------------------------------------------------------------------- App id Current queue Minimum queue Maximum queue Average queue size size size size -------------------------------------------------------------------------------- 1 0 0 0 0 2 0 0 0 0 3 0 0 0 0 4 0 0 0 0 5 0 0 0 0 6 0 0 0 0 7 0 0 0 0 8 0 0 0 0 9 0 0 0 0 10 0 0 0 0 11 0 0 0 0 12 0 0 0 0 13 0 0 0 0 14 0 0 0 0 15 0 0 0 0 16 0 0 0 0 17 0 0 0 0 18 0 0 0 0 19 0 0 0 0 20 0 0 0 0 21 0 0 0 0 22 0 0 0 0 23 0 0 0 0 24 0 0 0 0 25 0 0 0 0 26 0 0 0 0 27 0 0 0 0 28 0 0 0 0 29 0 0 0 0 30 0 0 0 0 31 0 0 0 0 32 0 0 0 0 33 0 0 0 0 34 0 0 0 0 35 0 0 0 0 36 0 0 0 0 37 0 0 0 0 38 0 0 0 0 39 0 0 0 0 40 0 0 0 0 41 0 0 0 0

DN0479352Issue 4-2

21


Id:0900d805806444bc

42 0 0 0 0 --------------------------------------------------------------------------------

2.1.10 ecm (enable continuous mode)

FunctionWith this command you set the service terminal commands to continuous mode. When the continuous mode is set, certain commands you execute will run continuously after every specified number of seconds. You can stop the command execution by executing 'Control-C' characters. The service terminal prompt is changed when the continuous mode is set. See section Commands in continuous mode for a list of the commands that are enabled in the continuous mode when this command is executed. When this mode is enabled, the commands are enabled in continuous mode for the PQII processor only. The continuous mode can be set individually for each of the connected service terminal sessions with the same or different refresh intervals.

You should always disable the continuous mode with the dcm command before closing the service terminal session. Otherwise PCU2's internal service terminal resources may get exhausted.

Syntaxecm <refresh time in seconds>

Parameter explanationsrefresh time in seconds

With this parameter you specify the refresh time of the command. The suggested value is between 3 - 10 seconds.

Examples

1. Enable the continuous mode with a refresh interval of 3 seconds.ecm 3

2. Enable the continuous mode with a refresh interval of 6 seconds.ecm 6

Execution printoutsBCSU/0/PCU/0/OSE>ecm 3 ----------------------------------------------------------------> Command ecm executed on [1/1/2004 0:0:6:289001] <---- ------------------------------------------------------------Refresh time configured '3' seconds Enabling Continous mode for the following commands -------------------------------- dbu (for pq2 only) dbp (for pq2 only) dbs (for pq2 only) dtu dtp (for pq2 only) dsca dsco daa deqs

22 DN0479352Issue 4-2


Id:0900d805806444bc


--------------------------------BCSU/0/PCU/0/OSE>

2.1.11 dcm (disable continuous mode)

FunctionWith this command you disable the continuous mode of the service terminal. See section Commands in continuous mode for a list of the commands that are disabled in the continuous mode when this command is executed.

Syntaxdcm

Examples

1. Disable the continuous mode.dcm

Execution printoutsBCSU/0/PCU/0/OSE/C>dcm ----------------------------------------------------------------> Command dcm executed on [1/1/2004 0:2:1:604001] <---- ------------------------------------------------------------Disabling Continous mode for the following commands --------------------------------dbu (for pq2 only) dbp (for pq2 only) dbs (for pq2 only) dtu dtp (for pq2 only) dsca dsco daa deqs -------------------------------- BCSU/0/PCU/0/OSE/C>

2.1.12 dbl (display bootup log)

FunctionWith this command you can examine the bootup logs after a successful restart, which may help you in checking the state of the system. The full form of this command is display the bootup logs (dbl).

Syntaxdbl

DN0479352Issue 4-2

23


Id:0900d805806444bc

Examples

1. Display the bootup logs.dbl

Execution printoutsExecution printout for PCU2-D/U:

BCSU/32/PCU/6/OSE>dbl----------------------------------------------------------------> Command dbl executed on [9/2/2009 11:2:32:576770] <----------------------------------------------------------------Post Stage I Memory (data lines, address lines and SDRAM memory walkthrough) and watchdog diagnostics completed.

Bootup Image Started.Creating WatchDog Clear Process.Installing SMCUART Driver.Installing FastEthernet Driver.Starting Boot Diagnostics POST Stage II Tests.Starting Ethernet and serial Diagnostics POST Stage II Tests.Diagnostics Ethernet Interface 1 test result = PASSED.Diagnostics Ethernet Interface 2 test result = PASSED.Diagnostics Serial Interface test result = PASSED.Post Stage II diagnostics completed.

============================================================Welcome to the PQII Boot Loader.============================================================

IMSGW Boot image version : '6.33-0' built on Aug 21 2006

Power-On-Self-Tests :

SDL BOOTLOADER: Reset Reason HARD RESETSDL BOOTLOADER: Downloading image For Section 0...SDL BOOTLOADER: Transfering control to image entry point at 0x01e00004

RAM Image Started.Creating WatchDog Clear Process.Installing SMCUART Driver.Installing FastEthernet Driver.Initializing PCM MUX Settings Starting Ethernet and Internal PQ2 PCM Diagnostics POST Stage II Tests.Diagnostics HDLC Loopback Test Interface 1 result = PASSED.Post Stage II diagnostics completed.

RAM based initialization completed

OSE Started.

PQII Data-Cache test result : PASSED

Starting Component Manager ...

IMSGW_CM: Executing the Entry Point function OF CMPCI: Sending Host Intr StartingPIU index=0x6, PIU type=0x3d9, Phy add=0x32, Broadcast=0x7f Log PIU Index= 0x7

Component Manager(RESTART State) : Received WORKING state from BSC

File /ram/bin/dsp/IGWDGDSD.hex has been downloaded in DSP 0

24 DN0479352Issue 4-2


Id:0900d805806444bc









DIAGNOSTIC RESULTS OF DSP0 ------------------------------------DSP CORE TEST : PASSED DSP MEMORY TEST : PASSED DSP TIMER0 TEST : PASSED DSP TIMER1 TEST : PASSED DSP DMA TEST : PASSED DSP McBSP0 TEST : PASSED DSP McBSP1 TEST : PASSED Abis PCM external loopback : PASSED

File /ram/bin/dsp/IGWBTDSD.hex has been downloaded in DSP 0







DN0479352Issue 4-2

25


Id:0900d805806444bc









File /ram/bin/dsp/IGWMNDSD.hex has been downloaded in DSP 0







26 DN0479352Issue 4-2


Id:0900d805806444bc


File /ram/bin/dsp/IGWMNDSD.hex has been downloaded in DSP 7BCSU/32/PCU/4/OSE>

Execution printout for PCU2-E:

BCSU/32/PCU/4/OSE>dbl----------------------------------------------------------------> Command dbl executed on [9/2/2009 10:58:55:776885] <----------------------------------------------------------------

============================================================Welcome to the PQIII Boot Loader.============================================================

IMSGW Boot image version : '1.13-0' built on Dec 19 2008


SDL BOOTLOADER: Reset Reason HARD RESETSDL BOOTLOADER: Downloading image For Section 0...SDL BOOTLOADER: Transferring control to image entry point at 0x10000000

Diagnostics HDLC Loopback Test Interface 1 result = PASSED.


OSE Started.


IMSGW_CM: Executing the Entry Point function OF CMPCI: Sending Host Intr StartingPIU index=0x4, PIU type=0x3e3, Phy add=0x32, Broadcast=0x7f Log PIU Index= 0x5

Component Manager(RESTART State) : Received WORKING state from BSC IMSGW_CM: Time Received from BSC - Mon Feb 9 09:58:17 2009

File /ram/bin/dsp/IGWDGDSE.hex has been downloaded in DSP 0






DN0479352Issue 4-2

27


Id:0900d805806444bc

DIAGNOSTIC RESULTS OF DSP0 ----------------------------------------DSP CORE TEST : PASSED DSP MEMORY TEST : PASSED DSP TIMER0 TEST : PASSED DSP TIMER1 TEST : PASSED DSP DMA TEST : PASSED DSP McBSP0 TEST : PASSED DSP McBSP1 TEST : PASSED DSP SRIO TEST : PASSED

File /ram/bin/dsp/IGWBTDSE.hex has been downloaded in DSP 0







28 DN0479352Issue 4-2


Id:0900d805806444bc






File /ram/bin/dsp/IGWMNDSE.hex has been downloaded in DSP 0





File /ram/bin/dsp/IGWMNDSE.hex has been downloaded in DSP 5BCSU/32/PCU/4/OSE>

2.1.13 dai (display application IDs)

FunctionWith this command you display the list of the application IDs on PQII and DSP, which helps you in giving correct application IDs in the service terminal commands. The full form of this command is display application IDs (dai).

Syntaxdai

DN0479352Issue 4-2

29


Id:0900d805806444bc

Examples

1. Display the application IDs.dai

Execution printoutsBCSU/32/PCU/4/OSE>dai----------------------------------------------------------------> Command dai executed on [26/1/2009 12:43:25:896686] <----------------------------------------------------------------

********************************************************Application Name Application ID********************************************************Component IDs for Common Applications to PQII and DSP********************************************************Component manager(CM) 1Inter Process Communication(IPC) 2Performance management System(PMS) 3******************************************************** Platform Component IDs for PQII********************************************************Software Download(SDL) 4Logger(LOGGER) 5Alarm Server(ARS) 6DSP Manager(DSPM) 7System Monitor(SYSMON) 8Diagnostics(DIAG) 9DSP Resource Manager(DSPRM) 10Service Terminal Agent(STA) 11********************************************************Displaying Application Component IDs for PQII********************************************************ABM 16PDM 17PSW 18MAC 19PFM 20PCM 21BGP 22NS 23FR 24RL 25PCU Agent 28CPU Monitoring process 29IDRS 31IPMR 12IBNACC 33********************************************************Displaying Dynamic Application IDs for PQII********************************************************

30 DN0479352Issue 4-2


Id:0900d805806444bc


Dynamic Application Begin 34Dynamic Application End 46********************************************************Displaying Application Component IDs for DSP********************************************************Quality Control(QC) 4 ULQC 29 DLQC 30DSPA 6DSP CPU MON 24INTER DSPA 25SERIAL DSPA 26DSPA LOGGER 28Data Transfer Task(DTT) 5 ULRLC 31 DLRLC 32 PFD 33 ULSCH 34 DLSCH 35Inter DSP Communication(COM) 27

BCSU/32/PCU/4/OSE>

2.1.14 daa (display active alarms)

FunctionWith this command you display the list of alarms currently active in the PCU2. The full form of this command is display active alarms (daa).

Syntaxdaa

Examples

1. Display the alarms currently active in the system.daa

Execution printoutsOutput syntax:

<s.no> <alarm id(in hex)> <bcsu> <object_index = index_of_host_bcsu_computer> <app_id that raised the obs> <card_id (from IPC hdr) that raisedthe obs(hex dump)> <setting family> <setting time(mm/dd/yyyyhr:mi:ss:hundredth of a second> current state: <not set>,<set/not set>,<reset/not reset>,<set sent/unsent>,<reset sent/unsent>,<setacked/unacked>,<reset acked/unacked> <additional information bytes (as a byte dump)>

Execution printout:BCSU/31/PCU/4/OSE>daa ----------------------------------------------------------------> Command daa executed on [1/1/2004 0:0:8:280001] <---- ------------------------------------------------------------ Current Observations in this card (All parameters displayed in hex in this display)

DN0479352Issue 4-2

31


Id:0900d805806444bc

=================================================== < 1>. <3053> <6B> <1> <1B> <2F22> <5143> 1/1/04 0:0:8:69 current state:<set>,<not reset>,<set sent>,<reset not sent>,<set acked>,<reset not acked> <100000>

< 2>. <3250> <6B> <1> <18> <2F22> <5143> 28/10/2004 18:26:32:59 current state:<set>,<not reset>,<set sent>,<reset not sent>,<set acked>,<reset not acked> <42 0>

2.1.15 uad (update authentication data)

FunctionWith this command you reload the Service Terminal Authentication QWERTY file (QWERTYGX.IMG) from the OMU's disk to the unit's memory when the QWERTY file is corrupted. When the service terminal program opens the QWERTY file, it first calculates the checksum of the file data and compares it with the checksum value in the header of the QWERTY file. The file data is corrupted if the checksum does not match.

Syntaxuad

Examples

1. Reload the QWERTY file.uad

Execution printouts------------------------------------------------------------ ----> Command uad executed on [1/1/1970 0:3:9:310001] <---- ------------------------------------------------------------

2.2 Operating system commandsThis section contains the commands which apply to the general category of the service terminal.

2.2.1 keys

FunctionWith this command you display the terminal keys configured in the system. Without any parameters, the command displays the terminal commands for the standard inputs with their assigned control keys.

Syntaxkeys

Examples

1. Display the existing configured keys.keys

32 DN0479352Issue 4-2


Id:0900d805806444bc


Execution printoutsBCSU/0/PCU/0/OSE>keys eol = ^M eof = ^X eraseleft = ^H eraseright = ^D cutword = ^W cutline = Û reprint = ^L intr = ^C susp = ^Z start = ^Q stop = ^S discard = Ô verbatim = ^V status = ^G curleft = ^B curright = ^F curbegin = Â curend = Ê search = ^R prevline = ^P nextline = ^N cuteol = ^K paste = ^Y

2.2.2 help/?

FunctionWith this command you can print the syntax and a short explanation for each specified command. '?' is an alias for help.

Syntaxhelp/? [<command>] [-i]

Examples

1. Display help and listing of all the commands available in the system.help

2. Display help on a command named 'ps'.help ps

3. Display help on a command named 'ps'.? ps

4. Enter the interactive help mode.help —i

2.2.3 date

FunctionWith this command you display the date of the system. The date is displayed in the format 'yyyy-Month-dd'.

Syntaxdate

Examples

1. Display the current date of the system.date

Execution printoutsBCSU/0/PCU/0/OSE>date 2004-January-1

DN0479352Issue 4-2

33


Id:0900d805806444bc

2.2.4 time

FunctionWith this command you print the current time to the standard output. The time is dis-played in the format 'hours:minutes:seconds.microseconds'.

Syntaxtime

Examples

1. Display the current time of the system.time

Execution printoutsBCSU/0/PCU/0/OSE>time 0:41:57.36

2.2.5 ver

FunctionWith this command you print the version of the OSE kernel and SHELL to the standard output.

Syntaxver

Examples

1. Display the OSE OS version.ver

Execution printoutsBCSU/0/PCU/0/OSE>ver OSE/OSE4.5.1 OSE Delta PowerPC/OSE4.5

2.2.6 ls

FunctionWith this command you list the specified files or the files and subdirectories in the direc-tory where the command is executed. Two option flags are possible.

Syntaxls [<options>][<dirname> ...]

Parameter explanations–l

This parameter specifies a long listing with information such as access modes, owner-ship, size, and modification date.

–a

34 DN0479352Issue 4-2


Id:0900d805806444bc


This parameter includes files starting with a '.' in the listing.

Examples

1. Display the listing of files and subdirectories in the current directory.ls

2. Display the long listing of files and subdirectories in the current directory.ls —l

Execution printoutsBCSU/0/PCU/0/OSE>ls Directory '/ram/' dump.dat IGWBTDSD.hex IGWDGDSD.hexIGWMNDSD.hex log_file.txt etc/

2.2.7 cat

FunctionWith this command you concatenate files. It reads each <filename> in a sequence and outputs the file's data on the standard output. Without filename, it reads from the standard input. You can exit the standard input read mode by pressing Ctrl-x.

Syntaxcat [<filename>]

Examples

1. Display the contents of an already existing file named 'abc.txt' on the screen.cat abc.txt

Execution printoutsBCSU/0/PCU/0/OSE>cat abc.txt /* This is a sample text file called abc.txt */

2.2.8 rm

FunctionWith this command you remove (delete) the specified files. The file(s) must not be open.

Syntaxrm [f] <filename> ...

Examples

1. Remove a file named 'log_file.txt'.rm log_file.txt

Execution printoutsIf any process has opened the file, it gives the following message:

DN0479352Issue 4-2

35


Id:0900d805806444bc

BCSU/0/PCU/0/OSE>rm log_file.txt Could not remove 'log_file.txt': Permission denied.

2.3 Service terminal logging to file commandsThis section contains the commands which are related to logging to the file facilities pro-vided. You can use any of the commands provided to log the desired service terminal outputs to a file on the PCU RAM disk system.

2.3.1 esl (enable ST logging)

FunctionWith this command you log the output of all the PCU2 commands (except the OSE com-mands) to a file. The full form of this command is enable ST logging (esl). This command can be typically used in scenarios where auditing is required for record purposes.

You must execute the dsl command before viewing the generated file (through the cat command).

Parameter explanationsfilename

The name of the file in which the logs are to be captured.

size_in_bytes

The maximum size of the file. In case the logs exceed the maximum file size, the log capture mode is automatically turned off, and no more logging is done.

Syntaxesl <filename> <size_in_bytes>

Examples

1. Enable service terminal logging to a file named 'st_logs.txt' with a maximum size of 5000 bytes.esl st_logs.txt 5000

Execution printoutsBCSU/0/PCU/0/OSE/L>esl st_logs.log 5000 filename extension should be “log” changing filename 'st_logs.txt' to '/ram/st_logs.log'------------------------------------------------------------ ----> Command esl executed on [1/1/2004 0:0:22:370001] <---- ------------------------------------------------------------

******************************************************** Enabled Service Terminal Logging Data to a file Filename: /ram/st_logs.log Size: 5000

!

Running this command may affect the system performance. Use this command with care and only when necessary.

36 DN0479352Issue 4-2


Id:0900d805806444bc


Please note that after the file exceeds Size: 5000 bytes No Data will be logged to the file The User will be intimated and Logging to the File Shall automatically be switched off ********************************************************************** Enabling this command may affect the performance of the System **********************************************************************

2.3.2 dsl (disable ST logging)

FunctionThe full form of this command is disable ST logging (dsl).

Syntaxdsl

Examples

1. Disable the service terminal logging to a file.dsl

Execution printoutsBCSU/0/PCU/0/OSE/L>dsl ----------------------------------------------------------------> Command dsl executed on [1/1/2004 0:1:2:870001] <---- ------------------------------------------------------------

******************************************************** Disabled Service Terminal Logging Data to a file Filename: /ram/st_logs.log Size: 5000 ********************************************************

2.3.3 dlfi (display logging to a file information)

FunctionThe full form of this command is display logging to a file information (dlfi).

Syntaxdlfi

Examples

1. Display the existing logging to a file options.dlfi

Execution printoutsIf no logging to a file has been enabled, the output will be:

BCSU/0/PCU/0/OSE>dlfi ----------------------------------------------------------------> Command dlfi executed on [1/1/2004 0:3:2:322001] <---- ------------------------------------------------------------ Service Terminal Logging to a file mode Not activated

DN0479352Issue 4-2

37


Id:0900d805806444bc

Service Terminal MM Logging to a file mode Not activated Service Terminal GB Logging to a file mode Not activated Service Terminal UP Logging to a file mode Not activated Service Terminal Subscriber Logging to a file mode Not activated

If all loggings to a file have been enabled, the output is:

BCSU/0/PCU/0/OSE>dlfi ----------------------------------------------------------------> Command dlfi executed on [1/1/2004 0:5:38:606001] <---- ------------------------------------------------------------Service Terminal Logging to a file mode Not activated

********************************************************Service Terminal MM Logging to a file mode is ON Filename: /ram/st_mm_logs.log Size: 5000 ********************************************************

******************************************************** Service Terminal GB Logging to a file mode is ON Filename: /ram/st_gb_logs.log Size: 5000 ********************************************************

********************************************************Service Terminal UP Logging to a file mode is ON Filename: /ram/st_up_logs.log Size: 5000 ********************************************************

******************************************************** Service Terminal Subscriber Logging to a file mode is ON Filename: /ram/st_sm_logs.log Size: 5000 ********************************************************

2.3.4 remove (remove logging files)

FunctionWith this command you remove/delete the various log files which you have created to log GB/MM/UP/SM or service terminal outputs to a file. The full form of this command is remove logging files (remove).

You must close the files before executing this command by disabling logging to a file for the respective file.

Syntaxremove <filename>

Parameter explanationsfile identifier

This parameter specifies which file is to be removed. The various options which can be specified are:

all_log_files for removing all log files with extension '.log'

*.log for removing all log files with extension '.log'

38 DN0479352Issue 4-2


Id:0900d805806444bc


filename for removing individual files

Examples

1. Remove a file named 'log_gb.log' from the RAM disk.remove log_gb.log

2. Remove all files with the extension '.log' from the RAM disk.remove *.log

3. Remove all log files with the extension '.log' from the RAM disk.remove all_log_files

Execution printoutsA successfull case:

BCSU/0/PCU/0/OSE>remove all_log_files ----------------------------------------------------------------> Command remove executed on [1/1/2004 0:0:11:920001] <---- ------------------------------------------------------------All LOG File Removed

In case of a failure, the reason for it will be printed out:

------------------------------------------------------------ ----> Command remove executed on [1/1/2004 0:3:31:510001] <---- ------------------------------------------------------------File <abc.log> could not be removed Search permission is denied for a component of the path prefix

2.3.5 > command

FunctionWith this command you direct the output of any command to a file.

Syntax<command> > <filename>

Examples

1. Redirect the output of the 'ps' command to a file 'ps_output.txt'.ps > ps_output.txt

Execution printoutsBCSU/0/PCU/0/OSE>ps > ps_output.txt BCSU/0/PCU/0/OSE> BCSU/0/PCU/0/OSE>cat ps_output.txt pid name tpr block own status00400057 ps p09 main 4 running 00010055 st_receiver p09 main 0 rcv 00010054 ose_shell p09 main 5 rcv 00010053 DSPMTI tim main 0 - 00010052 ose_login p09 main 1 rcv 00010051 MCC_HDLC_TI tim main 0 - 00010050 MCC_HDLC_1 i03 main 0 - 0001004f PSW p16 main 0 rcv

DN0479352Issue 4-2

39


Id:0900d805806444bc

0001004e RL p16 main 0 rcv 0001004d FR p16 main 0 rcv 0001004c NS p16 main 0 rcv 0001004b BGP p16 main 0 rcv 0001004a PCM p16 main 0 rcv 00010049 PFM p16 main 0 rcv 00010048 MAC p16 main 0 rcv 00010047 PDM p16 main 1 rcv 00060016 ABM p25 main 0 rcv 00010046 MiiMdint2 i05 main 0 - 00010045 MiiMdint1 i05 main 0 - 00010044 DSPMISR7 i03 main 0 - 00010043 DSPMISR6 i03 main 0 -00010042 DSPMISR5 i03 main 0 - 00010041 DSPMISR4 i03 main 0 - 00010040 DSPMISR3 i03 main 0 - 0001003f DSPMISR2 i03 main 0 -0001003e DSPMISR1 i03 main 0 - 0001003d MCC_HDLC_2 i03 main 0 - 0001003c DSPMISR0 i03 main 0 - 0001003b pcu_agnt_cmd_proc p14 main 0 sem0001003a IDRS p16 main 0 rcv 00010039 SERIAL_DSPM p16 main 0 ready 00010038 CPUMON p10 main 0 rcv 00010037 PCU_AGNT p15 main 0 rcv 00010036 DIAGONOSTICS p16 main 0 rcv 00010035 DSPRM p20 main 0 rcv 00010034 st_dmx_dd1 p09 main 1 rcv 00010033 st_dmx_dd0 p09 main 1 rcv 00010032 STA p09 main 2 rcv 00010031 SDL p18 main 0 rcv 00010030 SYSMON p16 main 0 rcv 0001002f ARS p16 main 2 rcv 0001002e IPC_MR p16 main 0 rcv 0001002d DSPM p16 main 0 rcv 0001002c PMS-PQII p16 main 0 rcv 0001002b LOGGER p16 main 2 rcv 0001002a pci_delivery_proc tim main 0 - 00010029 ipnet_radvd p10 main 1 rcv00020028 cm_main p16 main 27 stop ready 00010027 ipnet_inputd p10 main 0 sem 00010026 ipnet_tickd p10 main 0 delay 00010025 ose_inet p10 main 0 rcv 00010024 FastEthernet i03 main 0 - 00010023 ose_extfm_/ram p09 main 3 rcv 00010022 SMCUART i03 main 1 - 00010021 FastEthernet i03 main 0 - 00010020 ose_serdd_SMCUART p09 main 8 rcv 0001001f ipcom_tickd p01 main 0 delay 0001001e ose_confm_/tty p09 main 2 rcv 0001001d ipcom_telnetd p10 main 0 rcv

40 DN0479352Issue 4-2


Id:0900d805806444bc


0001001c ose_nulldev ph main 0 - 0001001b ose_tosv_ti tim main 0 - 0001001a ipcom_syslogd p10 main 0 rcv 00010019 ipcom_init p10 main 86 stop ready 00010018 ose_cmd_proxy p20 main 0 rcv 00010017 ose_eat_vector i00 main 0 - 00010015 ose_heapd_cleanup p31 main 0 rcv 00010014 CPUMON_BACK_GND bg main 0 ready 00010013 start_efs p09 main 0 stop ready 00010012 ose_ramdisk p09 main 1 rcv 00010011 ose_extfm p09 main 1 rcv 00010010 ose_shelld p09 main 0 rcv 0001000f ose_serdd p09 main 1 rcv 0001000e ose_confm p09 main 1 rcv 0001000d ose_fss p09 main 0 rcv 0001000c ose_tosv p02 main 1 rcv 0001000b ose_rtc p03 main 0 rcv 0001000a ose_heapd p10 main 1 rcv 00010008 main p16 main 1 rcv 00010009 ose_ticker i00 OSE 0 - 00010006 ose_huntd ph OSE 0 - 00010005 ose_huntd p10 OSE 0 rcv 00010004 ose_tickd i31 OSE 0 - 00010003 ose_sysd p20 OSE 80 rcv 00010002 idle bg OSE 0 readyTotal 84 processes BCSU/31/PCU/4/OSE>

2.4 Process manipulation commandsThis section contains the commands provided by the OSE real-time operating system (RTOS) to the process manipulation category of the service terminal.

2.4.1 ps

FunctionWith this command you list the current processes running in the system. The command lists the specified process or all processes belonging to the specified block. With no parameters all processes are listed. Processes and blocks can be specified by numeri-cal pid, name, wildcard and pixlist index as follows:

• numerical pid (0x10001) • name (ose_shell) • wildcard (ose*) • pixlist index (*(14))

Name, wildcard and pixlist index can be mixed.

Syntaxps [-w] [<pid>]

DN0479352Issue 4-2

41


Id:0900d805806444bc

Parameter explanations–w

Wide listing.

pid

Specifies the process ID of the process.

Examples

1. List the current processes and their states in the system.ps

Execution printoutsOutput field descriptions:

BCSU/0/PCU/0/OSE>ps pid name tpr block own status0003000c DSPMTI tim pcu2e 0 -00010064 pcu_agnt_cmd_proc p14 pcu2e 0 sem00010063 MCC_HDLC_TI tim pcu2e 0 -00010062 MCC_HDLC_1 i03 pcu2e 0 -00010061 DMA1ISR i30 pcu2e 0 -0001005f srio_sw_int_proc i06 pcu2e 0 -0001005e IPMR p16 pcu2e 1 rcv

Parameter Explanation

pid Specifies the process ID of the process.

name Specifies the process name.

tpr Specifies the thread priority.

bg The process is a background process.

pxx Specifies the priority. For example, P09 specifies priority 9.

tim The process is a timer interrupt process.

ph The process is a phantom process.

block Specifies the block to which the process belongs.

own Specifies the owner of the process.

status Specifies the status of the process:

running The process is currently running.

rcv The process is waiting on a receive call, and is waiting for a message.

sem The process is waiting for a sema-phore.

delay The process is executing a delay system call.

ready The process is ready to be started.

The phantom , interrupt, and timer interrupt processes do not have any statuses.

42 DN0479352Issue 4-2


Id:0900d805806444bc


0001005d IBNACC p16 pcu2e 0 rcv0001005c IDRS p16 pcu2e 0 rcv0001005b CPUMON p10 pcu2e 0 rcv0001005a PCU_AGNT p15 pcu2e 4 rcv00010059 PSW p16 pcu2e 0 rcv00010058 RL p16 pcu2e 1 rcv00010057 FR p16 pcu2e 1 rcv00010056 NS p16 pcu2e 1 rcv00010055 BGP p16 pcu2e 0 rcv00010054 PCM p16 pcu2e 0 rcv00010053 PFM p16 pcu2e 0 rcv00010052 MAC p16 pcu2e 0 rcv00010051 PDM p16 pcu2e 2 rcv00010050 ABM p15 pcu2e 0 rcv0001004f DIAGONOSTICS p16 pcu2e 0 rcv0001004e DSPRM p20 pcu2e 1 rcv0001004a SDL p18 pcu2e 0 rcv00010049 SYSMON p16 pcu2e 0 rcv00010048 ARS p16 pcu2e 2 rcv00010047 IPC_MR p16 pcu2e 1 rcv00010046 DSPMRX p05 pcu2e 1 rcv00010045 DSPM p16 pcu2e 4 rcv00010044 PMS-PQII p16 pcu2e 0 rcv00040043 LOGGER p16 pcu2e 3 rcv0002000d efs_file_owner ph pcu2e 0 -00010031 cm_main p16 pcu2e 29 rcv00770067 ps p09 main 6 running00010066 st_receiver p09 main 1 rcv00010065 st_main p09 main 7 rcv00020060 my_ose_login p09 main 3 rcv0001004d st_dmx_dd1 p09 main 1 rcv0001004c st_dmx_dd0 p09 main 1 rcv0001004b STA p09 main 0 rcv00010042 ose_telnetd bg main 1 rcv00010041 ose_vfs/pop3 p22 main 0 rcv00010040 ose_vfs/http p22 main 0 rcv0001003f ose_vfs/ftp p22 main 0 rcv0001003e ose_vfs/tftp p22 main 0 rcv0001003d ose_vfs/ramlog p22 main 0 rcv0001003c ose_vfs/zip p22 main 0 rcv0001003b ose_vfs/gzip p22 main 0 rcv0001003a ose_surfer p26 main 1 rcv00010039 iptftps_service p16 main 1 rcv00020037 iptftps p16 main 1 rcv00010038 ipnetradvd_service p16 main 1 rcv00010036 ipftps_service p16 main 1 rcv00010035 ipftps p10 main 1 rcv00010034 ose_gws bg main 2 rcv00010033 ose_lmcmd_daemon p24 main 0 rcv00010032 CPUMON_BACK_GND bg main 0 ready0001002f ose_dbgserver p10 main 2 rcv

DN0479352Issue 4-2

43


Id:0900d805806444bc

0001002e ose_vfs p22 main 0 stop ready0001002d ose_dhcp p16 main 1 rcv0001002c ose_resolve p12 main 1 rcv0001002b ose_ucc i14 main 0 -0001002a ose_ucc i14 main 0 -00010029 ipnetd p10 main 1 rcv00010028 ipcom_syslogd p10 main 1 rcv00010027 ipcom_shared_heap ph main 0 -00010026 ose_inet p10 main 343 rcv00010025 netw_supervisor p15 main 5 rcv00010024 ose_rtl_elf p25 main 0 rcv00010023 ose_program_mgr p25 main 3 rcv00010022 ose_extfm_/ram p25 main 5 rcv00010021 ose_extfm p25 main 1 rcv00010020 ose_boardparam p10 main 0 rcv0001001f ose_ramdisk p30 main 1 rcv0001001e FAM_COMMON_SENDER ph main 0 -0001001d uart1 i08 main 1 -0001001c ose_serdd_uart1 p14 main 0 rcv0001001b ose_confm_/tty p14 main 4 ready0001001a ose_confm p14 main 1 rcv00010019 ose_serdd p14 main 1 rcv00010018 ose_cmd_proxy p20 main 0 rcv00010017 ose_nulldev ph main 0 -00010016 ose_shelld p25 main 1 rcv00010015 ose_fss p19 main 1 rcv00010014 ose_rtc p05 main 0 rcv00010013 ose_riodb_tx0 i10 main 0 -00010012 ose_riodb_rx0 i10 main 0 -00010011 ose_dma0 i08 main 0 -00010010 ose_devman p20 main 3 rcv0001000f ose_heapd p20 main 43 rcv0001000e ose_memory_mgr p20 main 0 rcv0001000b core_supervisor p15 main 26 rcv00010009 main p16 main 1 rcv0001000a ose_ticker i00 OSE 0 -00010007 ose_monitor p01 OSE 4 rcv00010006 ose_huntd ph OSE 0 -00010005 ose_huntd p10 OSE 0 rcv00010004 ose_tickd i31 OSE 0 -00010003 ose_sysd p20 OSE 97 rcv00010002 idle bg OSE 0 readyTotal 100 processesBCSU/0/PCU/0/OSE>

2.5 Statistics commandsThis section contains the commands used to display the various statistics being col-lected in the PCU systems. The operator for certain analyses (for example, performance degradation and measurements) may use these commands.

44 DN0479352Issue 4-2


Id:0900d805806444bc


2.5.1 dbu (display buffers per unit)

FunctionWith this command you display the buffer statistics for the whole PIU on a per processor basis. The full form of this command is display buffers per unit (dbu).

Syntaxdbu <processor type>{:<dsp id>}


Specifies the processor type on which the application is residing. The allowable values are 'pq2' and 'dsp'.

dsp id

Specifies the DSP ID. The values range from 0 to 7. The parameter needs to be speci-fied only in case the processor type is DSP.

Examples

1. Display the buffers currently allocated in the pq2 processor.dbu pq2

2. Display the buffers currently allocated in the dsp processor '1'.dbu dsp:1

3. Display the buffers currently allocated in the dsp processor '2'.dbu dsp:2

Execution printoutsBCSU/31/PCU/4/OSE>dbu pq2 ----------------------------------------------------------------> Command dbu executed on [8/6/2005 12:54:53:855543] <---- ------------------------------------------------------------

--------------------------------------------------------------------------------Buffer Busy Free Current Max Total Used Free size buffers buffers usage usage bytes bytes bytes -------------------------------------------------------------------------------- 8 13 11 54.16% 100.00% 192 104 88 12 128 43 74.85% 76.02% 2052 1536 516 16 50 1047 4.55% 5.28% 17552 800 16752 20 38 73 34.23% 36.93% 2220 760 1460 22 1 4099 0.02% 0.04% 90200 22 90178 32 28 42970 0.06% 0.16% 1375936 896 1375040 56 4 8102 0.04% 0.08% 453936 224 453712 64 3 4610 0.06% 0.34% 295232 192 295040 70 0 4097 0.00% 0.07% 286790 0 286790 76 2 1003 0.19% 1.09% 76380 152 76228 80 0 350000 0.00% 0.00% 34281600 0 28000000 88 1 2047 0.04% 0.14% 180224 88 180136 116 3 5 37.50% 100.00% 928 348 580 256 12 2 85.71% 100.00% 3584 3072 512 810 9 0 100.00% 100.00% 7290 7290 0

DN0479352Issue 4-2

45


Id:0900d805806444bc

1048 94 4014 2.28% 2.62% 4305184 98512 4206672 1600 8 325 2.40% 3.00% 532800 12800 520000 2000 1152 1848 38.40% 39.20% 6000000 2304000 3696000 4680 2 0 100.00% 100.00% 9360 9360 0 10000 1 0 100.00% 100.00% 10000 10000 0 16384 4 252 1.56% 4.68% 4194304 65536 4128768 31000 0 20 0.00% 5.00% 620000 0 620000 36864 0 2 0.00% 0.00% 73728 0 73728 69136 1 7 12.50% 12.50% 553088 69136 483952 72000 1 2 33.33% 33.33% 216000 72000 144000 96000 1 0 100.00% 100.00% 96000 96000 0131072 0 1 0.00% 100.00% 131072 0 1310721150000 1 0 100.00% 100.00% 1150000 1150000 01397760 0 4 0.00% 25.00% 5591040 0 5591040 2000 0 5000 0.00% 0.34% 10000000 0 10000000 --------------------------------------------------------------------------------Total 6.07% 8.86% 64275092 3902828 60372264-------------------------------------------------------------------------------- BCSU/31/PCU/4/OSE> BCSU/31/PCU/4/OSE>dbu dsp:0 ----------------------------------------------------------------> Command dbu executed on [8/6/2005 12:57:46:495044] <---- ------------------------------------------------------------ --------------------------------------------------------------------------------Buffer Busy Free Current Max Total Used Freesize buffers buffers usage usage bytes bytes bytes-------------------------------------------------------------------------------- 16 6 442 1.33% 4.68% 7168 96 7072 36 8 2702 0.29% 26.78% 97560 288 97272 64 0 128 0.00% 100.00% 8192 0 8192 84 0 224 0.00% 31.69% 18816 0 18816 100 5 10 33.33% 80.00% 1500 500 1000 160 4 712 0.55% 3.35% 114560 640 113920 200 0 1024 0.00% 0.09% 204800 0 204800 500 2 8 20.00% 100.00% 5000 1000 4000 1600 1 1169 0.08% 16.75% 1872000 1600 1870400 2056 6 34 15.00% 15.00% 82240 12336 69904 8228 0 33 0.00% 18.18% 271524 0 271524 21216 1 31 3.12% 18.75% 678912 21216 657696 28788 0 6 0.00% 0.00% 172728 0 172728 30000 0 4 0.00% 0.00% 120000 0 120000 45960 0 1 0.00% 0.00% 45960 0 45960 58228 0 2 0.00% 0.00% 116456 0 116456 140 0 150 0.00% 0.00% 21000 0 21000 --------------------------------------------------------------------------------Total 0.98% 14.41% 3838416 37676 3800740-------------------------------------------------------------------------------- BCSU/31/PCU/4/OSE>

46 DN0479352Issue 4-2


Id:0900d805806444bc


2.5.2 dbp (display buffer statistics per process)

FunctionWith this command you list the buffer statistics per process on a particular processor type. The full form of this command is display buffer statistics per process (dbp).

Syntaxdbp <processor type>{:<dsp id>}:<application id>


Specifies the processor type on which the application is residing. The allowable values are 'pq2' and 'dsp'

dsp id


application id

The application ID should be within the possible range. For the application IDs, see section Application IDs for commands.

Examples

1. Display the buffers allocated by the application on pq2 with application ID '1'.dbp pq2:1

2. Display the buffers allocated by the application on dsp '1' with application ID '1'.dbp dsp:1:1

Execution printoutsBCSU/0/PCU/0/OSE>dbp pq2:1 ----------------------------------------------------------------> Command dbp executed on [1/1/2004 0:12:15:740001] <---- ------------------------------------------------------------ Buffer statistics for application 1 -------------------------------------------------------------------------------- Buffer size Buffer address Allocation time(in millisecs) -------------------------------------------------------------------------------- 20 0x7b0fd3c 12552 20 0x7b0fd60 12582 20 0x7b0fd84 12608 20 0x7b0fda8 12636 20 0x7b0fdcc 12660 20 0x7b0fdf0 12688 20 0x7b0fe14 12712 20 0x7b0fe38 12736 20 0x7b0fe5c 12768 20 0x7b0fe80 12802 20 0x7b0fea4 12828 20 0x7b0fec8 12862 20 0x7b0feec 2677784 20 0x7b0ff10 12910 20 0x7b0ff34 12934 20 0x7b0ff58 12960 20 0x7b0ff7c 12984 20 0x7b0ffa0 13008 20 0x7b0ffc4 13030 20 0x7b0ffe8 13054

DN0479352Issue 4-2

47


Id:0900d805806444bc

20 0x7b1000c 13076 20 0x7b10030 13102 20 0x7b10054 13132 20 0x7b10078 13158 20 0x7b1009c 13192 32 0x7361258 14520 810 0x7b124ca 14520 -------------------------------------------------------------------------------- Total memory usage 1342 Peak memory usage 1342 Minimum memory usage 20 -------------------------------------------------------------------------------- BCSU/0/PCU/0/OSE>dbp dsp:1:1 ----------------------------------------------------------------> Command dbp executed on [1/1/2004 0:12:15:740001] <---- ------------------------------------------------------------ Buffer statistics for application 1 -------------------------------------------------------------------------------- Buffer size Buffer address Allocation time(in millisecs) -------------------------------------------------------------------------------- 36 0x2820ba 0 1600 0x2b0000 0 -------------------------------------------------------------------------------- Total memory usage 1636 Peak memory usage 1636 Minimum memory usage 1600 --------------------------------------------------------------------------------

2.5.3 dbs (display buffer statistics of particular size)

FunctionWith this command you list the buffer statistics of a particular buffer size on a particular processor. The full form of this command is display buffer statistics of particular size (dbs).

Syntaxdbs <processor type>{:<dsp id>} <buffer size>



dsp id


buffer size

This parameter specifies the buffer size of which the statistics are to be printed. If there is no buffer with the specified size, the next highest size is displayed instead.

48 DN0479352Issue 4-2


Id:0900d805806444bc


Examples

1. Display the buffers allocated by various applications with buffer size 30 on pq2.dbs pq2 30

2. Display the buffers allocated by various applications with buffer size 30 on dsp '0'.dbs dsp:0 30

Execution printoutsBCSU/0/PCU/0/OSE>dbs pq2 30 ----------------------------------------------------------------> Command dbs executed on [1/1/2004 0:12:38:970001] <---- ------------------------------------------------------------ Buffer statistics for size 32 -------------------------------------------------------------------------------- Owner's appid Buffer address Allocation time(in millisecs) -------------------------------------------------------------------------------- 3 0x736e038 31338 5 0x736e068 32006 8 0x736e0c8 32140 7 0x736e0f8 51192 7 0x736e128 51366 7 0x736e158 51482 7 0x736e188 51482 7 0x736e1b8 51482 7 0x736e1e8 51538 7 0x736e218 51538 7 0x736e248 51538 15 0x736e278 32706 2 0x736e2a8 33088 27 0x736e2d8 33184 27 0x736e308 33184 27 0x736e338 33184 28 0x736e368 33212 1 0x736e398 33332 --------------------------------------------------------------------------------Total buffers allocated 18 -------------------------------------------------------------------------------- BCSU/0/PCU/0/OSE>dbs dsp:0 30 ----------------------------------------------------------------> Command dbs executed on [1/1/2004 0:12:38:970001] <---- ------------------------------------------------------------ Buffer statistics for size 36 -------------------------------------------------------------------------------- Owner's appid Buffer address Allocation time(in millisecs) -------------------------------------------------------------------------------- 24 0x2820a0 0 1 0x2820ba 0 5 0x2820d4 0 28 0x2820ee 2 --------------------------------------------------------------------------------

DN0479352Issue 4-2

49


Id:0900d805806444bc

2.5.4 dtp (display timer statistics per process)

FunctionWith this command you list the timer statistics for a process on a particular processor. The full form of this command is display timer statistics per process (dtp).

Syntaxdtp <processor type>{:<dsp id>}:<application id>



dsp id


application id

The application ID should be within the possible range. For the application IDs, see section Application IDs for commands.

Examples

1. Display the timers started by the application on pq2 with application ID '1'.dtp pq2:1

2. Display the timer started by the application on dsp '1' with application ID '1'.dtp dsp:1:1

Execution printoutsBCSU/0/PCU/0/OSE>dtp pq2:1 ----------------------------------------------------------------> Command dtp executed on [1/1/2004 0:0:24:288001] <---- ------------------------------------------------------------ Timer statistics for application 1 -------------------------------------------------------------------------------- Timer id Timer value(ms) Timer type Time left till next expiry(ms)-------------------------------------------------------------------------------- 0x736e3a8 70 periodic 30 -------------------------------------------------------------------------------- Total timers 1 -------------------------------------------------------------------------------- BCSU/0/PCU/0/OSE>dtp dsp:1:1 ----------------------------------------------------------------> Command dtp executed on [1/1/2004 0:0:24:288001] <---- ------------------------------------------------------------

50 DN0479352Issue 4-2


Id:0900d805806444bc


Timer statistics for application 1 -------------------------------------------------------------------------------- Timer id Timer value(ms) Timer type Time left till next expiry(ms)-------------------------------------------------------------------------------- 0x2820c2 500 periodic 8 --------------------------------------------------------------------------------

2.5.5 dtu (display timer statistics per unit)

FunctionWith this command you list the timer statistics per application for all the applications, on PQII only. The full form of this command is display timer statistics per unit (dtu).

Syntaxdtu

Examples

1. Display the timers currently started in the PQII processor.dtu

Execution printoutsBCSU/0/PCU/0/OSE>dtu ----------------------------------------------------------------> Command dtu executed on [1/1/2004 0:13:17:530001] <---- -------------------------------------------------------------------------------------------------------------------------------------------- App Timer Timer Timer Time left Totalid id value(ms) type till next expiry(ms) timers-------------------------------------------------------------------------------- 1 0x736e3a8 70 periodic 46 1 -------------------------------------------------------------------------------- 5 0x736e078 1000 periodic 284 1 -------------------------------------------------------------------------------- 7 0x736e108 10000 periodic 1250468 7 0x736e138 1800000 periodic 1250642 7 0x736e168 1800000 periodic 1250758 7 0x736e198 1800000 periodic 1250756 7 0x736e1c8 1800000 periodic 1250756 7 0x736e1f8 1800000 periodic 1250812 7 0x736e228 1800000 periodic 1250812 7 0x736e258 1800000 periodic 1250812 8 --------------------------------------------------------------------------------8 0x736e0d8 10000 periodic 1412 1 --------------------------------------------------------------------------------15 0x736e288 5000 periodic 1978 1 --------------------------------------------------------------------------------28 0x736e378 2000 periodic 482

DN0479352Issue 4-2

51


Id:0900d805806444bc

1 --------------------------------------------------------------------------------

2.5.6 dsca (display statistics counter for specific category)

FunctionWith this command you display the values of the statistics counter IDs for a specific category (dsca). This command has a 'first dimension', a 'second dimension' and a 'third dimension' as conditional parameters. For the parameters that need to be specified, see the table below. If the dimensions are not passed, counters for all possible records with valid data are displayed.

Note that the second dimension parameter Service area is required for the category 72 PCU. The third dimension parameter Service area is also mandatory for the category 79 Coding Scheme.

If the GPRS Cell Re-selection record is to be displayed for a particular BTS ID and LAC-CI pair, provide the CI in the most significant byte (MSB) and the LAC in the least signif-icant byte (LSB) of the LAC-CI pair.

Syntaxdsca <category id> {first dimension} {second dimension} {thirddimension}

Parameter explanationscategory ID

This parameter specifies the category of the counters.

first dimension, second dimension, third dimension

These parameters define the additional parameter to be specified. This parameter is dependent on the category ID (see the table above). For example, in case you want to

Category ID Statistics category First dimension Second dimension Third dimension

72 PCU BTS ID Service area

73 RLC Blocks per TRX

BTS ID TRX ID

74 Frame Relay Bearer channel no.

76 Dynamic Abis EDAP ID

79 Coding Scheme BTS ID Coding scheme Service area

90 Quality of Service Segment ID QoS class

95 GPRS Cell Re-selection

BTS ID LAC-CI

96 GPRS RX Level and Quality

BTS ID TRX ID Coding scheme

97 Enhanced QoS Segment ID TC-THP-PFI ID ARP ID

98 Gb over IP NSEI NSVC ID

105 PS DTM BTS ID

110 PCU Utilisation

52 DN0479352Issue 4-2


Id:0900d805806444bc


display statistics related to a particular BTS (for category PCU), then BTS ID needs to be given in the first dimension.

Examples

1. Display the statistics of category id 76 with EDAP ID '1'.dsca 76 1

2. Display the statistics of category id 76 for all EDAP IDs with valid data.dsca 76

Execution printoutsBCSU/0/PCU/0/OSE>dsca 76 1----------------------------------------------------------------> Command dsca executed on [11/7/20080:35:0:708963] <----------------------------------------------------------------

------------------------------------------------------------------->Statistics displayed at time [11/7/20080:35:0:710251]<-------------------------------------------------------------------

EDAP-ID = 1total_nbr_of_pcm_subtsls_in_edap = 15average_dl_edap_usage = 16average_ul_edap_usage = 17average_edap_usage_den = 18peak_dl_edap_usage = 19peak_ul_edap_usage = 20ul_tbfs_without_edap_res = 21dl_tbfs_without_edap_res = 22dl_tbfs_with_inadequate_edap_res = 23ul_edap_allocation_requests = 24dl_edap_allocation_requests = 25ave_edap_ul_allocated_for_rt = 26ave_edap_dl_allocated_for_rt = 27ave_edap_ul_usage_for_rt = 28ave_edap_dl_usage_for_rt = 29ave_edap_ul_usage_for_nrt = 30ave_edap_dl_usage_for_nrt = 31total_nbr_of_pcm_subtsls_in_edap_ul = 32dynamic_abis_denom_ul = 33ul_mcs_limited_by_pcu = 34dl_mcs_limited_by_pcu = 35

2.5.7 dsco (display statistics for a specific counter)

FunctionWith this command you display statistics for a specific counter (dsco). This command has a 'first dimension', a 'second dimension' and a 'third dimension' as conditional parameters. If the dimensions are not passed, the counter's value for all configured dimensions is displayed.

DN0479352Issue 4-2

53


Id:0900d805806444bc

If the GPRS Cell Re-selection record is to be displayed for a particular BTS ID and LAC-CI pair, provide the CI in the MSB and the LAC in the LSB of the LAC-CI pair.

For the counter IDs, see the following measurements:

• 72 Packet Control Unit Measurement • 73 RLC Blocks per TRX Measurement • 74 Frame Relay Measurement • 76 Dynamic Abis Measurement • 79 Coding Scheme Measurement • 90 Quality of Service Measurement • 95 GPRS Cell Re-selection Measurement • 96 GPRS RX Level and Quality Measurement • 97 Enhanced Quality of Service Measurement • 98 Gb Over IP Measurement • 105 PS DTM Measurement • 110 PCU Utilisation Measurement

Syntaxdsco <counter id> {first dimension} {second dimension} {thirddimension}

Parameter explanationscounter ID

This parameter defines the counter ID.


These parameters define the additional parameter to be specified. This parameter is dependent on the category of the specified counter ID. For example, if you want to display statistics related to a particular BTS (for category PCU), then BTS ID needs to be given in the first dimension.

Examples

1. Display the statistics of counter ID 110002.dsco 110002

Execution printoutsBCSU/30/PCU/4/OSE>dsco 110002----------------------------------------------------------------> Command dsco executed on [11/7/2008 13:12:36:334241] <----------------------------------------------------------------

------------------------------------------------------------------->Statistics displayed at time [11/7/2008 13:12:36:536866]<-------------------------------------------------------------------

Counter-id:110002 PCU_ID :0 value:122

54 DN0479352Issue 4-2


Id:0900d805806444bc


2.5.8 rsca (reset statistics counter for specific category)

FunctionWith this command you reset the values of statistics counter IDs for a specific category (rsca). This command has a 'first dimension', a 'second dimension' and a 'third dimen-sion' as conditional parameters. For the parameters that need to be specified, see the table below. If the dimensions are not passed, all the dimensions are reset. If the category ID is not passed, all the categories for all their respective dimensions are reset.

Syntaxrsca [<category id>] {first dimension} {second dimension} {thirddimension}

Parameter explanationscategory ID

This parameter specifies the category of the counters.


These parameters define the additional parameter to be specified. This parameter is dependent on the category ID (see the table above). For example, if you want to reset counters related to a particular BTS (for category PCU), then BTS ID needs to be given in the first dimension.

Examples

1. Reset the statistics of category id 76 with EDAP ID '1'.rsca 76 1

2. Reset the statistics of category id 76 for all EDAP IDs.rsca 76

3. Reset the statistics of all categories.rsca

Category ID Statistics category First dimension Second dimension Third dimension

72 PCU BTS ID Service area

73 RLC Blocks per TRX

BTS ID TRX ID

74 Frame Relay Bearer channel no

76 Dynamic Abis EDAP ID

79 Coding Scheme BTS ID Coding scheme Service area

90 Quality of Service Segment ID QoS class

95 GPRS Cell Re-selection

BTS ID LAC-CI

96 GPRS RX Level and Quality

BTS ID TRX ID Coding scheme

97 Enhanced QoS Segment ID TC-THP-PFI ID ARP ID

98 Gb over IP NSEI NSVC ID

105 PS DTM BTS ID

110 PCU Utilisation

DN0479352Issue 4-2

55


Id:0900d805806444bc

Execution printoutsBCSU/0/PCU/0/OSE>rsca 76 1----------------------------------------------------------------> Command rsca executed on [11/7/20080:7:53:180001] <----------------------------------------------------------------

2.5.9 rsco (reset statistics for a specific counter)

FunctionWith this command you reset statistics for a specific counter (rsco). This command has a 'first dimension', a 'second dimension' and a 'third dimension' as conditional parame-ters. If the dimensions are not passed, all the dimensions are reset.

Syntaxrsco <counter id> {first dimension} {second dimension} {thirddimension}

Parameter explanationscounter ID

This parameter defines the counter ID.


These parameters define the additional parameter to be specified. This parameter is dependent on the category of the specified counter ID. For example, if you want to reset counters related to a particular BTS (for category PCU), then BTS ID needs to be given in the first dimension.

Examples

1. Reset statistics of counter ID 110002.rsco 110002

Execution printoutsBCSU/30/PCU/4/OSE>rsco 110002----------------------------------------------------------------> Command rsco executed on [11/7/2008 13:16:3:22612] <----------------------------------------------------------------

2.6 Utilities - Black Box

2.6.1 abb (analyze black box)

FunctionWith this command you dump the black box contents on to the service terminal screen.

To debug the error code, see section Error code debugging information for abb and doe command output.

Syntaxabb <processor type>

56 DN0479352Issue 4-2


Id:0900d805806444bc



This parameter specifies the processor type on which the application is residing. The only allowable value is 'pq2'.

Examples

1. Analyse the black box for 'pq2'.abb pq2

Execution printoutsOutput field description:

Parameter name Description

Cause code Specifies the cause code used by the kernel to indicate which error caused a call to the error handler.

Reboot reason Contains the various reboot/failure reasons because of which the card would be reset. Typical examples are SSF Initialisa-tion Failure, Process startup Failure, and Normal Shutdown.

Number of retries The number of times the system has been restarted. This value is reset in case of a healthy reboot.

Number of processes The number of PCU2 processes initially started successfully by the component manager.

Processor ID Specifies the processor ID on which the black box formation has occurred. 0 - 7 specify the crashed DSP Number. 8 spec-ifies that the crash has happened on the PQII processor.

Process name Process name is a string (in the strings array) showing the name of the process or block. This field specifies the process name of the application/platform processes.

Process ID Specifies the process ID.

Process type Contains the process type. Legal values are:

0 - OS_PRI_PROC

64 - OS_BG_PROC

128 - OS_INT_PROC

256 - OS_TI_PROC

512 - OS_PHANTOM

1024 - OS_BLOCK

2048 - OS_ZOOMBIE

4096 - OS_ILLEGAL

Fast semaphore Specifies the current value of the fast semaphore attached to the process. The value is negative if the process is waiting at the semaphore or if the process does not have a fast sema-phore. You can use the status field to determine which the case is.

DN0479352Issue 4-2

57


Id:0900d805806444bc

Process status Contains the process status. This is a bit field with zero, one, two, or three bits set. If no bits are set, the process is ready or running. Otherwise the process is suspended for one or more reasons. The OS_STOPPED and OS_INTERCEPTED bits can be set independently. Other bits are mutually exclusive. Legal bit masks are:

1 - OS_RECEIVE - Waiting for one of the receive calls.

2 - OS_DELAY - Waiting for a delay call.

4 - OS_SEMAPHORE - Waiting at a semaphore.

8 - OS_FSEMAPHORE - Waiting at a fast semaphore.

16 - OS_REMOTE - Waiting for a remote system call.

32 - OS_STOPPED - The process was stopped.

64 - OS_INTERCEPTED - A breakpoint was reached.

Process priority Specifies the new priority. In OSE the allowable range is from 0 - 31. 0 is the highest priority.

User User is the user number of the process.

Signal count Signal count is the number of signals currently in the signal queue of the process. Note that the 'Signal count' field should only be used for statistics, not when traversing the signal queue itself.

Line number Line is an integer containing the source code line from which the current system call was issued. Line is 0 if no line and file information is available. Line and file information is available only if the PCU2 platform was compiled with the debug option.

Filename File is a string (in the strings array) showing the file name from which the current system call was issued. This field is invalid if line is 0. Line and file information is available if the PCU2 platform was compiled with the debug option.

Cpu register Cpuregs is a string (in the strings array) showing all known CPU register values. The names of these are CPU dependent. A sample string might look like “PC=00001D34 SP=000089AB D1=0000A89”. Registers are separated by a space. All values are in upper case hex format. Registers that cannot be deter-mined at a certain point are excluded from the list. There may be a pseudo register named 'R'". It contains the return address to user code while a system call is in progress. Information on CPU register values is only available for kernel libraries sup-porting debugging.

Optional fields (only displayed if the required information can be extracted during the system failure):

Product Name Specifies the product name which triggered the kernel error handler, for example: 'TELNET/UDP server'.

Product Name The second 'product name' specifies the OSE process name, for example: 'OSE_TELUDPD'.

File name Specifies the OSE error code filename in which the error code description can be found, for example: 'inetutilerr.h'.

Sub Code The subcode is extracted from error_code, and it assists the user in locating the exact error cause.


58 DN0479352Issue 4-2


Id:0900d805806444bc


BCSU/0/PCU/0/OSE>abb pq2 ----------------------------------------------------------------> Command abb executed on [1/1/1970 0:0:11:550001] <---- ------------------------------------------------------------------------------------------------------------------------ Displaying Black Box Data ------------------------------------------------------------Cause Code :0 Reboot Reason : Process Run Time Failure Number of retries :1 Number of processes :20 Processor Id (8 PQII) :8

--------------------Data for Crashed Process-------------Process Name :ABM Process Id :0x10033 Process Type :2048 Fast Semaphore :-1

--------------------Data for Process:LOGGER------------- Process Id :0x10029 Process Type :0 Process Status :0 Process Priority :16 User :0 Fast Semaphore :0 Signal Count :2Line Number :617 Filename :ssf_event.c CPU Register :TID=0000022C

--------------------Data for Process:PMS-PQII-------------Process Id :0x1002a Process Type :0 Process Status :1 Process Priority :16 User :0 Fast Semaphore :0 Signal Count :0 Line Number :617 Filename :ssf_event.c CPU Register :TID=00000230

--------------------Data for Process:DSPM------------- Process Id :0x1002b Process Type :0 Process Status :1 Process Priority :16 User :0 Fast Semaphore :0 Signal Count :0

DN0479352Issue 4-2

59


Id:0900d805806444bc

Line Number :617 Filename :ssf_event.c CPU Register :TID=00000234

--------------------Data for Process:IPC_MR-------------Process Id :0x1002c Process Type :0 Process Status :1 Process Priority :16 User :0 Fast Semaphore :0 Signal Count :0 Line Number :617 Filename :ssf_event.c CPU Register :TID=00000238

--------------------Data for Process:ARS------------- Process Id :0x1002d Process Type :0 Process Status :1 Process Priority :16 User :0 Fast Semaphore :0 Signal Count :0Line Number :617 Filename :ssf_event.c CPU Register :TID=0000023C

--------------------Data for Process:SYSMON-------------Process Id :0x1002e Process Type :0 Process Status :1 Process Priority :16 User :0 Fast Semaphore :0 Signal Count :0 Line Number :617 Filename :ssf_event.c CPU Register :TID=00000240

--------------------Data for Process:SDL------------- Process Id :0x1002f Process Type :0 Process Status :1 Process Priority :16 User :0 Fast Semaphore :0 Signal Count :0Line Number :617 Filename :ssf_event.c CPU Register :TID=00000244

60 DN0479352Issue 4-2


Id:0900d805806444bc


--------------------Data for Process:STA-------------Process Id :0x10030 Process Type :0 Process Status :1 Process Priority :16 User :0 Fast Semaphore :0 Signal Count :0 Line Number :617 Filename :ssf_event.c CPU Register :TID=00000248

--------------------Data for Process:DSPRM------------- Process Id :0x10031 Process Type :0 Process Status :1 Process Priority :16 User :0 Fast Semaphore :0 Signal Count :0Line Number :617 Filename :ssf_event.c CPU Register :TID=0000024C

--------------------Data for Process:DIAGONOSTICS-------------Process Id :0x10032 Process Type :0 Process Status :2 Process Priority :16 User :0 Fast Semaphore :0 Signal Count :0 Line Number :717 Filename :diag_main.c CPU Register :TID=00000250

--------------------Data for Process:PDM------------- Process Id :0x10034 Process Type :0 Process Status :1 Process Priority :16 User :0 Fast Semaphore :0 Signal Count :0Line Number :617 Filename :ssf_event.c CPU Register :TID=00000258

--------------------Data for Process:MAC-------------Process Id :0x10035

DN0479352Issue 4-2

61


Id:0900d805806444bc

Process Type :0 Process Status :1 Process Priority :16 User :0 Fast Semaphore :0 Signal Count :0 Line Number :617 Filename :ssf_event.c CPU Register :TID=0000025C

--------------------Data for Process:PFM------------- Process Id :0x10036 Process Type :0 Process Status :1 Process Priority :16 User :0 Fast Semaphore :0 Signal Count :0Line Number :617 Filename :ssf_event.c CPU Register :TID=00000260

--------------------Data for Process:PCM-------------Process Id :0x10037 Process Type :0 Process Status :1 Process Priority :16 User :0 Fast Semaphore :0 Signal Count :0 Line Number :617 Filename :ssf_event.c CPU Register :TID=00000264

--------------------Data for Process:BGP------------- Process Id :0x10038 Process Type :0 Process Status :1 Process Priority :16 User :0 Fast Semaphore :0 Signal Count :0Line Number :617 Filename :ssf_event.c CPU Register :TID=00000268

--------------------Data for Process:NS-------------Process Id :0x10039 Process Type :0 Process Status :1 Process Priority :16

62 DN0479352Issue 4-2


Id:0900d805806444bc


User :0 Fast Semaphore :0 Signal Count :0 Line Number :617 Filename :ssf_event.c CPU Register :TID=0000026C

--------------------Data for Process:FR------------- Process Id :0x1003a Process Type :0 Process Status :1 Process Priority :16 User :0 Fast Semaphore :0 Signal Count :0Line Number :617 Filename :ssf_event.c CPU Register :TID=00000270

--------------------Data for Process:RL-------------Process Id :0x1003b Process Type :0 Process Status :1 Process Priority :16 User :0 Fast Semaphore :0 Signal Count :0 Line Number :617 Filename :ssf_event.c CPU Register :TID=00000274

--------------------Data for Process:PSW------------- Process Id :0x1003c Process Type :0 Process Status :1 Process Priority :16 User :0 Fast Semaphore :0 Signal Count :0Line Number :617 Filename :ssf_event.c CPU Register :TID=00000278

2.6.2 mbbrbb (multiple black box read black box)

FunctionWith this command you read the black box from the mbb structure with the processor ID.

DN0479352Issue 4-2

63


Id:0900d805806444bc

Syntaxmbbrbb <processor_id> <-snapshot | -all | -n:number | -bt:DD:MM:YYYY:HH:MM:SS| -at:DD:MM:YYYY:HH:MM:SS>

Parameter explanationsprocessor_id

This parameter specifies the processor type on which the application is residing. The allowable values are pq2 or dsp:0...dsp:7.

snapshot

This parameter gives the information stored in the flash header, such as the processor ID, the time of creation, and the version name of the build. The information is displayed in sequence, starting from the most recent black box.

all

This parameter prints the recorded black boxes for pq2 or dsp <dsp id> along with the flash header.

n:<n>

This parameter prints the nth most recent black box for pq2 or dsp:<dsp id>.

bt:DD:MM:YYYY:HH:MM:SS

This parameter prints all the black boxes for the given processor ID, which were created before the time given to command input. The input time is in local format, so that the timestamp can be compared in local format.

at:DD:MM:YYYY:HH:MM:SS

This parameter prints all the black boxes for the given processor ID, which were created after the time given to command input. The input time is in local format, so that the time-stamp can be compared in local format.

Examples

1. Print all the black boxes for dsp '1'.mbbrbb dsp:1 -all

Execution printoutsBCSU/0/PCU/0/OSE>mbbrbb dsp:1 -all ----------------------------------------------------------------> Command mbbrbb executed on [30/11/2005 18:53:21:710875] <---- ------------------------------------------------------------ Printing for dsp : 1

========================================================================= Processor id: 1 Valid/Invalid : 1 Build software version: No Version Info Blackbox created on Thu Jan 1 00:05:20 1970

(42e18:42e8b) _error_handler

(3db20:3dc48) _delay

64 DN0479352Issue 4-2


Id:0900d805806444bc


Some Static Function.

(3dc74:3dc8b) _odo_panic (3d6fc:3d706) _odo_spurious_int

(c08c38:c08c3f) _cm_process_wmem_da ========================================================================= No more valid blackbox exists for dsp : 1 Printing DSP blackboxes done!BCSU/0/PCU/0/OSE>

2.7 Utilities - loggingThis section contains the commands related to the logging facility provided in the PCU2 system for debugging purposes. By executing these commands you can change the log level of various applications.

2.7.1 sll (set the log level)

FunctionWith this command you change the existing log level. The full form of this command is set the log level (sll).

The logs produced as a result of successful execution of this command will only be seen on the service terminal sessions that have enabled the display of logs by executing the 'esd' command.

Syntaxsll <processor type>{:<dsp id>}[:<application id>]<loglevel>: ...


This parameter specifies the processor type on which the application is residing. The allowable values are 'pq2' and 'dsp'.

dsp id

This parameter specifies the DSP ID. This parameter should to be specified only if the processor type is DSP.

application id

The application ID should be within the allowable/possible range. For the application IDs, see section Application IDs for commands.

log level

This parameter is the new log level to be specified.

0 - NO LOGS

1 - WARNING LOGS

DN0479352Issue 4-2

65


Id:0900d805806444bc

2 - INFO_1 LOGS

3 - INFO_2 LOGS

4 - INFO_3 LOGS

5 - INFO_4 LOGS

6 - ERROR LOGS

7 - DETAIL_1 LOGS

8 - DETAIL_2 LOGS

9 - DETAIL_3 LOGS

10 - DETAIL_4 LOGS

11 - CRITICAL LOGS

These log levels are mutually exclusive. You can set multiple log levels at the same time. The log level 'No logs' cannot be specified in combination with any other level. For example, the command

sll pq2:1 0:1:2:3

is invalid. In addition, any level cannot be specified more than once. For example, the command

sll pq2:1 1:2:1

is invalid.

Examples

1. Set the log level of the application with application ID '15' on pq2 processor to 1 and 2.sll pq2:15 1:2

2. Set the log level of the application with application ID '2' on dsp '1' processor to 1 and 4.sll dsp:1:2 1:4

3. Set the log level of all the applications on pq2 processor to 1, 2 and 3.sll pq2 1:2:3

4. Set the log level of all the applications on dsp '1' processor to 1 and 4.sll dsp:1 1:4

Execution printoutsThe execution printout for the PQII processor type:

BCSU/32/PCU/4/OSE>sll pq2:15 1:2 ----------------------------------------------------------------> Command sll executed on [1/1/2004 0:1:2:720001] <---- ------------------------------------------------------------Application [15]: LOG LEVEL: WARNING,INFO1 LOG SOFTWARE LEVEL: COMPUTING_PLATFORM

The execution printout for the DSP processor type:

BCSU/32/PCU/4/OSE>sll dsp:1:2 1:4 ------------------------------------------------------------

66 DN0479352Issue 4-2


Id:0900d805806444bc


----> Command sll executed on [1/1/2004 0:1:2:720001] <---- ------------------------------------------------------------Response from DSP [1]. Application [2]: LOG LEVEL: WARNING,INFO3 LOG SOFTWARE LEVEL: COMPUTING_PLATFORM

Log messages will be generated consecutively by the applications:

Log message output description:

The log message for the DSP processor type:[Logging Trace][<DSP ID:0>.\pfd_ul.c][516][33][29/10/2004 20:56:20:190000][6,5][60068] UL overflow condition is true for TRX. TRX Id: [0], EGPRS enabled: [1],ul_overflow_reg:[0xee] [Logging Trace][<DSP ID:0>.\pfd_ul.c][522][33][29/10/2004 20:56:20:190000][6,5][60069]

Current UL BPN:[9475],Current DL BPN:[9598][Logging Trace][<DSP ID:0>.\pfd_ul.c][695][33][29/10/2004 20:56:20:190000][6,5][60070]PFD ERROR: No data written by Platform PFD for this TSLTRX Id: 0, TSL Id: 1Current UL BPN:[9476],Current DL BPN:[9598]

2.7.2 ssl (set the software layer)

FunctionThe full form of this command is set the software layer (ssl). Application processes can be classified into various categories, and this command can be used to change the fil-tering criterion regarding the software layer. Appropriate logs will be generated accord-ing to this filtering criterion.

Syntaxssl <processor type>{:<dsp id>}[:<application id>]<softwarelayer>: ...


psw.c The filename from which the log message was gener-ated.

25 The line number of the file from which the log message was generated.

17 The application ID of the application that raised the log.

1/1/2004 The date stamp when the log was raised in dd/mm/yyyy format.

0:16:23:180001 The time stamp when the log was raised in hr:min:sec:micro-seconds format.

7,2 The log level and software layer of the application. In the example above, the log level is 7 - DETAIL_1 LOGS, and the software layer is 2 - COMPUTING PLATFORM.

second message The log message raised by the application.

DN0479352Issue 4-2

67


Id:0900d805806444bc



dsp id

This parameter specifies the DSP ID. This parameter is to be specified only in case the processor type is DSP.

application id


software layer

This is the new software layer to be specified.

0 - NO LOGS

1 - KERNEL

2 - COMPUTING PLATFORM

3 - SWITCHING PLATFORM

4 - RECOVERY

5 - APPLICATION

6 - OTHERS

Currently the PCU2 software produces log writings only with software layer 5 - APPLI-CATION.

These layers are mutually exclusive. You can set multiple layers at the same time. The software layer 'No logs' cannot be specified in combination with any other layer. For example, the command

ssl pq2:1 0:1:2:3

is invalid. In addition, any layer cannot be specified more than once. For example, the command

ssl pq2:1 1:2:1

is invalid.

Examples

1. Set the software level of application with application id as '17' on pq2 processor to 1, 2 and 3.ssl pq2:17 1:2:3

2. Set the software level of application with application id as '1' on dsp '1' processor to 1 and 4.ssl dsp:1:1 1:4

3. Set the software level of all the applications on pq2 processor to 1, 2 and 3.ssl pq2 1:2:3

4. Set the software level of all the applications on dsp '1' processor to 1 and 4.ssl dsp:1 1:4


68 DN0479352Issue 4-2


Id:0900d805806444bc


BCSU/0/PCU/0/OSE>ssl pq2:17 1:2:3 ----------------------------------------------------------------> Command ssl executed on [1/1/2004 0:1:49:590001] <---- ------------------------------------------------------------Application [17]: LOG LEVEL: WARNING, INFO1, INFO2 LOG SOFTWARE LEVEL: KERNEL,COMPUTING_PLATFORM,SWITCHING_PLATFORM


BCSU/0/PCU/0/OSE>ssl dsp:1:1 1:4 ----------------------------------------------------------------> Command ssl executed on [1/1/2004 0:1:49:590001] <---- ------------------------------------------------------------Response from DSP [1]. Application [1]: LOG LEVEL: WARNING, INFO3 LOG SOFTWARE LEVEL: KERNEL,COMPUTING_PLATFORM,SWITCHING_PLATFORM

2.7.3 slf (set the logger feature)

FunctionWith this command you enable/disable the logging facility on the PCU system. The full form of this command is set the logger feature (slf).

Syntaxslf <processor type>{:<dsp id>} <flag>



dsp id


flag

This parameter specifies the logging facility to be enabled or disabled. To enable give value '1' and to disable give value '0'.

Examples

1. Enable the logger feature on pq2.slf pq2 1

2. Disable the logger feature on pq2.slf pq2 0

3. Enable the logger feature on dsp '1'.slf dsp:1 1

DN0479352Issue 4-2

69


Id:0900d805806444bc

4. Disable the logger feature on dsp '1'.slf dsp:1 0


BCSU/0/PCU/0/OSE>slf pq2 1 ----------------------------------------------------------------> Command slf executed on [1/1/2004 0:2:20:560001] <---- ------------------------------------------------------------Logger is [1].


BCSU/0/PCU/0/OSE>slf dsp:1 1 ----------------------------------------------------------------> Command slf executed on [1/1/2004 0:2:20:560001] <---- ------------------------------------------------------------Response from DSP [1]. The logger is 1 [1: Enabled, 0: DISABLED].

2.7.4 dld (display the log details)

FunctionThis command can be used to examine the existing log level and software levels of the applications. The full form of this command is display the log details (dld).

Syntaxdld <processor type>{:<dsp id>} [<application id>]



dsp id


application id


Examples

1. Display the log/software level details of application with application id '1' on pq2.dld pq2:1

2. Display the log/software level details of application with application id '1' on dsp '1'.dld dsp:1:1

3. Display the log/software level details of all the applications on pq2.dld pq2

4. Display the log/software level details of all the applications on dsp '1'.dld dsp:1

70 DN0479352Issue 4-2


Id:0900d805806444bc



BCSU/0/PCU/0/OSE>dld pq2:1 ----------------------------------------------------------------> Command dld executed on [1/1/2004 0:2:44:520001] <---- ------------------------------------------------------------Application [1]: LOG LEVEL: LOG_WARNING LOG_INFO_1 LOG_ERROR LOG_DETAIL_1 LOG SOFTWARE LEVEL: LOG_COMPUTING_PLATFORM


BCSU/0/PCU/0/OSE>dld dsp:0:5 ----------------------------------------------------------------> Command dld executed on [1/1/2004 0:2:44:520001] <---- ------------------------------------------------------------Response from DSP [0]. Application [5]: LOG LEVEL: ERROR LOG SOFTWARE LEVEL:APPLICATION

2.7.5 dlf (display the logger feature)

FunctionWith this command you display the existing set options to enable/disable the logging facility in the PCU system. The full form of this command is display the logger feature (dlf).

Syntaxdlf <processor type>{:<dsp id>}



dsp id


Examples

1. Display the current setting of the logger feature on pq2.dlf pq2

DN0479352Issue 4-2

71


Id:0900d805806444bc

2. Display the current setting of the logger feature on dsp '1'.dlf dsp:1


BCSU/0/PCU/0/OSE>dlf pq2 ----------------------------------------------------------------> Command dlf executed on [1/1/2004 0:3:9:310001] <---- ------------------------------------------------------------Logger is [1] (1->ENABLED, 0->DISABLED).


BCSU/0/PCU/0/OSE>dlf dsp:0 ----------------------------------------------------------------> Command dlf executed on [1/1/2004 0:3:9:310001] <---- ------------------------------------------------------------Response from DSP [0]. Logger is [1] (1->ENABLED, 0->DISABLED).

2.7.6 efl (enable logging to file)

FunctionWith this command you enable logging to file from the PCU2. By enabling file logging, the PCU2 starts writing the logs to the file /ram/log_file.txt.

Syntaxefl

Examples

1. Enable file logging.efl

Execution printoutsBCSU/0/PCU/0/OSE>efl Logging to file enabled... BCSU/0/PCU/0/OSE>

2.7.7 dfl (disable logging to file)

FunctionWith this command you disable logging to file from the PCU2. By disabling file logging, the PCU2 stops writing the logs to the file /ram/log_file.txt.

Syntaxdfl

Examples

1. Disable file logging.dfl

72 DN0479352Issue 4-2


Id:0900d805806444bc


Execution printoutsBCSU/0/PCU/0/OSE>dfl Logging to file disabled... BCSU/0/PCU/0/OSE>

2.8 Utilities - software manipulationThis section contains the commands for software manipulation, including commands to reset the card after copying the new software from the download server or any other machine to the flash, and to display the existing software versions in the system.

2.8.1 reset

FunctionWith this command you reset the PQII or DSP processor.

Syntaxreset <processor type>:{dsp id}



dsp id


Examples

1. Reset the pq2 processor.reset pq2

2. Reset the dsp processor '1'.reset dsp:1


BCSU/0/PCU/0/OSE>reset pq2 ----------------------------------------------------------------> Command reset executed on [1/1/2004 0:3:9:310001] <---- ------------------------------------------------------------pq2 Processor reset...BCSU/0/PCU/0/OSE>


BCSU/0/PCU/0/OSE>reset dsp:7 ----------------------------------------------------------------> Command reset executed on [1/1/2004 0:3:9:310001] <---- ------------------------------------------------------------dsp Processor reset...BCSU/0/PCU/0/OSE>

DN0479352Issue 4-2

73


Id:0900d805806444bc

2.8.2 ssv (show the software version)

FunctionWith this command you show the software version (ssv). The command displays the boot and PIU RAM software version.

Syntaxssv

Examples

1. Display the existing software version.ssv

Execution printoutsBCSU/30/PCU/4/OSE>ssv----------------------------------------------------------------> Command ssv executed on [7/7/2008 11:6:32:413206] <----------------------------------------------------------------PQ2 Boot Image Software Version: 56.33-0PQ2 RAM Image Software Version: 9.8-0DSP RAM Image Software Version: 9.8-0DSP Diagnostics Image Software Version: 9.8-0DSP Boot Image Software Version: 9.8-0BCSU/30/PCU/4/OSE>

2.8.3 ubs (upgrade boot software)

FunctionWith this command you can transfer the software from the OMU disk to the PCU and program it to the flash memory on PCU2. The full form of this command is upgrade boot software (ubs). You need to restart the PIU to make the new boot software effective.

This command must be executed in TE (test) state only, it cannot be executed when the PCU is in the WO (working) state.

Syntaxubs

Examples

1. Upgrade the boot software.ubs

Execution printoutsBCSU/0/PCU/0/OSE>ubs ----------------------------------------------------------------> Command ubs executed on [1/1/2004 0:7:53:180001] <---- ------------------------------------------------------------SDL ubs: Current Boot Image Software Version : "IGWBTPQC.elf 2.2P10_DMX"SDL ubs: Downloaded Boot Image Software Version : "IGWBTPQC.elf 2.2P12_DMX"Confirm Boot Software Upgrade (y/n):y INPUT: y

74 DN0479352Issue 4-2


Id:0900d805806444bc


SDL ubs: Upgrading Boot Software... SDL ubs: Writing data size 0x53f00 to address 0xffe10000 SDL ubs: Writing data size 0x1784 to address 0xfff00000 SDL ubs: Writing data size 0x260 to address 0xffe63f00 SDL ubs: Boot Software has been upgraded. SDL ubs: New Boot file would be applied when PCU is rebooted. ----------------------------------------------------------

If the command is executed in the WO state, the output is as follows:

BCSU/31/PCU/4/OSE>ubs ----------------------------------------------------------------> Command ubs executed on [17/3/2004 3:19:48:404135] <---- ------------------------------------------------------------Incorrect PCU State: ubs cannot be executed in WO state Command Ignored BCSU/31/PCU/4/OSE>

2.9 Utilities - message monitoring, manipulation, and IPCThis section contains the commands for message monitoring and message manipula-tion.

2.9.1 emm (enable message monitoring)

FunctionWith this command you activate message-monitoring with the desired filtering criteria. The full form of this command is enable message monitoring (emm).

The traces produced as a result of successful execution of this command will only be seen on the service terminal sessions that have enabled the display of these traces by executing the 'esd' command.

The source or destination cannot be of the logger, IPC MR, DSPA or DSPM.

Syntaxemm <processor type>{:<dsp id>}{:<src id>} <processor type>{:<dsp id>}{:<dst id>} <direction_flag> [<msg type>] [<payload offset> <pattern>]


This parameter specifies the card type. If it is specified to src ID, it specifies the src pro-cessor type. In other cases, it specifies the dst processor type. The allowable values are 'pq2', 'bsc' and 'dsp'.

dsp id


src id

This parameter specifies the source application ID from where the message is simulated to have been originated. For the application IDs, see section Application IDs for com-mands.

DN0479352Issue 4-2

75


Id:0900d805806444bc

dst id

This parameter specifies the destination application ID to which the message needs to be sent. For the application IDs, see section Application IDs for commands.

msg type

This parameter specifies the message type to be sent.

payload offset

This parameter specifies the offset from which the comparison is to begin.

pattern

This parameter specifies the pattern to be compared from the offset 'payload offset'.

direction_flag

This parameter specifies the direction in which the monitoring is to be done. Valid values are:

0 - Monitor message at both directions

1 - Monitor message at sender

2 - Monitor message at receiver

Examples

1. Enable message monitoring from application 1 at PQII to application 1 on DSP 1 for message type as 12, to monitor at both directions.emm pq2:1 dsp:1:1 0 12

2. Enable message monitoring from application 1 at PQII to application 1 on DSP 1 for message type as 12, to monitor at sender.emm pq2:1 dsp:1:1 1 12

3. Enable message monitoring from application 1 at PQII to application 1 on DSP 1 for message type as 12, to monitor at receiver.emm pq2:1 dsp:1:1 2 12

4. Enable message monitoring from application 1 at DSP 1 to application 2 on PQII for message pattern "01 02 03 04" from location 12, to monitor at both directions.emm dsp:1:1 pq2:1 0 12 "01 02 03 04"

Execution printoutsBCSU/32/PCU/4/OSE>emm pq2:1 dsp:1:1 0 12 ----------------------------------------------------------------> Command emm executed on [1/1/2004 0:5:38:690001] <---- ------------------------------------------------------------ MM Enable on PQII and DSP[1] successful

Log messages will be generated consecutively by the applications:[Message Monitoring Trace][1/1/2004 0:2:36:218844] Monitored at : Receiver Source : DSP:0:5 Destination : PQ2:15 Message ID : 439 Message Header : -------- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- ----- ----------- 00000000 00 01 00 01 30 22 AF 22 00 05 00 0F 01 B7 05 10 ....0/"/"........ 00000010 00 02 .. -------- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- ----- -----------

76 DN0479352Issue 4-2


Id:0900d805806444bc


Message Payload : -------- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- ----- ----------- 00000000 00 00 15 6A 00 00 00 00 5B E4 5B E3 5B E2 5B E1 ...j....[.[.[.[. 00000010 5B E0 5B DF 5B DE 5B DD 5B DC 5B DB 5B DA 5B D9 [.[.[.[.[.[.[.[. 00000020 5B D8 5B D7 5B D6 5B D5 5B D4 5B D3 5B D2 5B D1 [.[.[.[.[.[.[.[. 00000030 5B D0 5B CF 5B CE 5B CD 5B CC 5B CB 5B CA 5B C9 [.[.[.[.[.[.[.[. 00000040 5B C8 5B C7 5B C6 5B C5 5B C4 5B C3 5B C2 5B C1 [.[.[.[.[.[.[.[. 00000050 5B C0 5B BF 5B BE 5B BD 5B BC 5B BB 5B BA 5B B9 [.[.[.[.[.[.[.[. 00000060 5B B8 5B B7 5B B6 5B B5 5B B4 5B B3 5B B2 5B B1 [.[.[.[.[.[.[.[. 00000070 5B B0 5B AF 5B AE 5B AD 5B AC 5B AB 5B AA 5B A9 [.[.[.[.[.[.[.[. 00000080 5B A8 5B A7 5B A6 5B A5 5B A4 5B A3 5B A2 5B A1 [.[.[.[.[.[.[.[. 00000090 5B A0 5B 9F 5B 9E 5B 9D 5B 9C 5B 9B 5B 9A 5B 99 [.[.[.[.[.[.[.[. 000000A0 5B 98 5B 97 5B 96 5B 95 5B 94 5B 93 5B 92 5B 91 [.[.[.[.[.[.[.[. 000000B0 5B 90 5B 8F 5B 8E 5B 8D 5B 8C 5B 8B 5B 8A 5B 89 [.[.[.[.[.[.[.[. 000000C0 5B 88 5B 87 5B 86 5B 85 5B 84 5B 83 5B 82 5B 81 [.[.[.[.[.[.[.[. 000000D0 5B 80 5B 7F 5B 7E 5B 7D 5B 7C 5B 7B 5B 7A 5B 79 [.[.[~[}[|[{[z[y 000000E0 5B 78 5B 77 5B 76 5B 75 5B 74 5B 73 5B 72 5B 71 [x[w[v[u[t[s[r[q 000000F0 5B 70 5B 6F 5B 6E 5B 6D 5B 6C 5B 6B 5B 6A 5B 69 [p[o[n[m[l[k[j[i 00000100 5B 68 5B 67 5B 66 5B 65 5B 64 5B 63 5B 62 5B 61 [h[g[f[e[d[c[b[a 00000110 5B 60 5B 5F 5B 5E 5B 5D 5B 5C 5B 5B 5B 5A 5B 59 [`[_[^[][\[[[Z[Y 00000120 5B 58 5B 57 5B 56 5B 55 5B 54 5B 53 5B 52 5B 51 [X[W[V[U[T[S[R[Q 00000130 5B 50 5B 4F 5B 4E 5B 4D 5B 4C 5B 4B 5B 4A 5B 49 [P[O[N[M[L[K[J[I 00000140 5B 48 5B 47 5B 46 5B 45 5B 44 5B 43 5B 42 5B 41 [H[G[F[E[D[C[B[A 00000150 5B 40 5B 3F 5B 3E 5B 3D 5B 3C 5B 3B 5B 3A 5B 39 [@[?[>[=[<[;[:[9 00000160 5B 38 5B 37 5B 36 5B 35 5B 34 5B 33 5B 32 5B 31 [8[7[6[5[4[3[2[1 00000170 5B 30 5B 2F 5B 2E 5B 2D 5B 2C 5B 2B 5B 2A 5B 29 [0[/[.[-[,[+[*[) 00000180 5B 28 5B 27 5B 26 5B 25 5B 24 5B 23 5B 22 5B 21 [(['[&[%[$[#["[! 00000190 5B 20 5B 1F 5B 1E 5B 1D 5B 1C 5B 1B 5B 1A 5B 19 [ [.[.[.[.[.[.[. 000001A0 5B 18 5B 17 5B 16 5B 15 5B 14 5B 13 5B 12 5B 11 [.[.[.[.[.[.[.[. 000001B0 5B 10 5B 0F 5B 0E 5B 0D 5B 0C 5B 0B 5B 0A 5B 09 [.[.[.[.[.[.[.[. 000001C0 5B 08 5B 07 5B 06 5B 05 5B 04 5B 03 5B 02 5B 01 [.[.[.[.[.[.[.[. 000001D0 5B 00 5A FF 5A FE 5A FD 5A FC 5A FB 5A FA 5A F9 [.Z.Z.Z.Z.Z.Z.Z. 000001E0 5A F8 5A F7 5A F6 5A F5 5A F4 5A F3 5A F2 5A F1 Z.Z.Z.Z.Z.Z.Z.Z. 000001F0 5A F0 5A EF 5A EE 5A ED 5A EC 5A EB 5A EA 5A E9 Z.Z.Z.Z.Z.Z.Z.Z. 00000200 5A E8 5A E7 5A E6 5A E5 5A E4 5A E3 5A E2 5A E1 Z.Z.Z.Z.Z.Z.Z.Z. 00000210 5A E0 5A DF 5A DE 5A DD 5A DC 5A DB 5A DA 5A D9 Z.Z.Z.Z.Z.Z.Z.Z. 00000220 5A D8 5A D7 5A D6 5A D5 5A D4 5A D3 5A D2 5A D1 Z.Z.Z.Z.Z.Z.Z.Z. 00000230 5A D0 5A CF 5A CE 5A CD 5A CC 5A CB 5A CA 5A C9 Z.Z.Z.Z.Z.Z.Z.Z. 00000240 5A C8 5A C7 5A C6 5A C5 5A C4 5A C3 5A C2 5A C1 Z.Z.Z.Z.Z.Z.Z.Z. 00000250 5A C0 5A BF 5A BE 5A BD 5A BC 5A BB 5A BA 5A B9 Z.Z.Z.Z.Z.Z.Z.Z. 00000260 5A B8 5A B7 5A B6 5A B5 00 00 00 00 00 06 00 08 Z.Z.Z.Z......... 00000270 00 00 00 01 B1 FF F0 5F 00 00 5A AB 00 00 00 00 ......._..Z..... 00000280 00 07 00 08 00 00 00 01 B1 FF F0 5F 00 00 5A A1 ..........._..Z. 00000290 00 00 00 00 00 07 00 08 00 00 00 01 B1 FF F0 5F ..............._ 000002A0 00 00 5A 97 5A 96 5A 95 5A 94 5A 93 5A 92 5A 91 ..Z.Z.Z.Z.Z.Z.Z. 000002B0 5A 90 5A 8F 5A 8E 5A 8D 5A 8C 5A 8B 5A 8A 5A 89 Z.Z.Z.Z.Z.Z.Z.Z. 000002C0 5A 88 5A 87 5A 86 5A 85 5A 84 5A 83 5A 82 5A 81 Z.Z.Z.Z.Z.Z.Z.Z. 000002D0 5A 80 5A 7F 5A 7E 5A 7D 5A 7C 5A 7B 5A 7A 5A 79 Z.Z.Z~Z}Z|Z{ZzZy 000002E0 5A 78 5A 77 5A 76 5A 75 5A 74 5A 73 5A 72 5A 71 ZxZwZvZuZtZsZrZq 000002F0 5A 70 5A 6F 5A 6E 5A 6D 5A 6C 5A 6B 5A 6A 5A 69 ZpZoZnZmZlZkZjZi 00000300 5A 68 5A 67 5A 66 5A 65 5A 64 5A 63 5A 62 5A 61 ZhZgZfZeZdZcZbZa 00000310 5A 60 5A 5F 5A 5E 5A 5D 5A 5C 5A 5B 5A 5A 5A 59 Z`Z_Z^Z]Z\Z[ZZZY 00000320 5A 58 5A 57 5A 56 5A 55 5A 54 5A 53 5A 52 5A 51 ZXZWZVZUZTZSZRZQ 00000330 5A 50 5A 4F 5A 4E 5A 4D 5A 4C 5A 4B 5A 4A 5A 49 ZPZOZNZMZLZKZJZI 00000340 5A 48 5A 47 5A 46 5A 45 5A 44 5A 43 5A 42 5A 41 ZHZGZFZEZDZCZBZA 00000350 5A 40 5A 3F 5A 3E 5A 3D 5A 3C 5A 3B 5A 3A 5A 39 Z@Z?Z>Z=ZZ.Z.Z.Z.Z.Z.Z.Z. 00000230 5A D0 5A CF 5A CE 5A CD 5A CC 5A CB 5A CA 5A C9 Z.Z.Z.Z.Z.Z.Z.Z. 00000240 5A C8 5A C7 5A C6 5A C5 5A C4 5A C3 5A C2 5A C1 Z.Z.Z.Z.Z.Z.Z.Z. 00000250 5A C0 5A BF 5A BE 5A BD 5A BC 5A BB 5A BA 5A B9 Z.Z.Z.Z.Z.Z.Z.Z. 00000260 5A B8 5A B7 5A B6 5A B5 00 00 00 00 00 06 00 08 Z.Z.Z.Z......... 00000270 00 00 00 01 B1 FF F0 5F 00 00 5A AB 00 00 00 00 ......._..Z..... 00000280 00 07 00 08 00 00 00 01 B1 FF F0 5F 00 00 5A A1 ..........._..Z. 00000290 00 00 00 00 00 07 00 08 00 00 00 01 B1 FF F0 5F ..............._ 000002A0 00 00 5A 97 5A 96 5A 95 5A 94 5A 93 5A 92 5A 91 ..Z.Z.Z.Z.Z.Z.Z. 000002B0 5A 90 5A 8F 5A 8E 5A 8D 5A 8C 5A 8B 5A 8A 5A 89 Z.Z.Z.Z.Z.Z.Z.Z. 000002C0 5A 88 5A 87 5A 86 5A 85 5A 84 5A 83 5A 82 5A 81 Z.Z.Z.Z.Z.Z.Z.Z. 000002D0 5A 80 5A 7F 5A 7E 5A 7D 5A 7C 5A 7B 5A 7A 5A 79 Z.Z.Z~Z}Z|Z{ZzZy

DN0479352Issue 4-2

77


Id:0900d805806444bc

000002E0 5A 78 5A 77 5A 76 5A 75 5A 74 5A 73 5A 72 5A 71 ZxZwZvZuZtZsZrZq 000002F0 5A 70 5A 6F 5A 6E 5A 6D 5A 6C 5A 6B 5A 6A 5A 69 ZpZoZnZmZlZkZjZi 00000300 5A 68 5A 67 5A 66 5A 65 5A 64 5A 63 5A 62 5A 61 ZhZgZfZeZdZcZbZa 00000310 5A 60 5A 5F 5A 5E 5A 5D 5A 5C 5A 5B 5A 5A 5A 59 Z`Z_Z^Z]Z\Z[ZZZY 00000320 5A 58 5A 57 5A 56 5A 55 5A 54 5A 53 5A 52 5A 51 ZXZWZVZUZTZSZRZQ 00000330 5A 50 5A 4F 5A 4E 5A 4D 5A 4C 5A 4B 5A 4A 5A 49 ZPZOZNZMZLZKZJZI 00000340 5A 48 5A 47 5A 46 5A 45 5A 44 5A 43 5A 42 5A 41 ZHZGZFZEZDZCZBZA 00000350 5A 40 5A 3F 5A 3E 5A 3D 5A 3C 5A 3B 5A 3A 5A 39 Z@Z?Z>Z=Z<Z;Z:Z9 00000360 5A 38 5A 37 5A 36 5A 35 5A 34 5A 33 5A 32 5A 31 Z8Z7Z6Z5Z4Z3Z2Z1 00000370 5A 30 5A 2F 5A 2E 5A 2D 5A 2C 5A 2B 5A 2A 5A 29 Z0Z/Z.Z-Z,Z+Z*Z) 00000380 5A 28 5A 27 5A 26 5A 25 5A 24 5A 23 5A 22 5A 21 Z(Z'ZZ&Z%Z$Z#Z"Z! 00000390 5A 20 5A 1F 5A 1E 5A 1D 5A 1C 5A 1B 5A 1A 5A 19 Z Z.Z.Z.Z.Z.Z.Z. 000003A0 5A 18 5A 17 5A 16 5A 15 5A 14 5A 13 5A 12 5A 11 Z.Z.Z.Z.Z.Z.Z.Z. 000003B0 5A 10 5A 0F 5A 0E 5A 0D 5A 0C 5A 0B 5A 0A 5A 09 Z.Z.Z.Z.Z.Z.Z.Z. 000003C0 5A 08 5A 07 5A 06 5A 05 5A 04 5A 03 5A 02 5A 01 Z.Z.Z.Z.Z.Z.Z.Z. 000003D0 5A 00 59 FF 59 FE 59 FD 59 FC 59 FB 59 FA 59 F9 Z.Y.Y.Y.Y.Y.Y.Y. 000003E0 59 F8 59 F7 59 F6 59 F5 59 F4 59 F3 59 F2 59 F1 Y.Y.Y.Y.Y.Y.Y.Y. 000003F0 59 F0 59 EF 59 EE 59 ED 59 EC 59 EB 59 EA 59 E9 Y.Y.Y.Y.Y.Y.Y.Y. 00000400 59 E8 59 E7 59 E6 59 E5 59 E4 59 E3 59 E2 59 E1 Y.Y.Y.Y.Y.Y.Y.Y. 00000410 59 E0 59 DF 59 DE 59 DD 59 DC 59 DB 59 DA 59 D9 Y.Y.Y.Y.Y.Y.Y.Y. 00000420 59 D8 59 D7 59 D6 59 D5 59 D4 59 D3 59 D2 59 D1 Y.Y.Y.Y.Y.Y.Y.Y. 00000430 59 D0 59 CF 59 CE 59 CD 59 CC 59 CB 59 CA 59 C9 Y.Y.Y.Y.Y.Y.Y.Y. 00000440 59 C8 59 C7 59 C6 59 C5 59 C4 59 C3 59 C2 59 C1 Y.Y.Y.Y.Y.Y.Y.Y. 00000450 59 C0 59 BF 59 BE 59 BD 59 BC 59 BB 59 BA 59 B9 Y.Y.Y.Y.Y.Y.Y.Y. 00000460 59 B8 59 B7 59 B6 59 B5 59 B4 59 B3 59 B2 59 B1 Y.Y.Y.Y.Y.Y.Y.Y. 00000470 59 B0 59 AF 59 AE 59 AD 59 AC 59 AB 59 AA 59 A9 Y.Y.Y.Y.Y.Y.Y.Y. 00000480 59 A8 59 A7 59 A6 59 A5 59 A4 59 A3 59 A2 59 A1 Y.Y.Y.Y.Y.Y.Y.Y. 00000490 59 A0 59 9F 59 9E 59 9D 59 9C 59 9B 59 9A 59 99 Y.Y.Y.Y.Y.Y.Y.Y. 000004A0 59 98 59 97 59 96 59 95 59 94 59 93 59 92 59 91 Y.Y.Y.Y.Y.Y.Y.Y. 000004B0 59 90 59 8F 59 8E 59 8D 59 8C 59 8B 59 8A 59 89 Y.Y.Y.Y.Y.Y.Y.Y. 000004C0 59 88 59 87 59 86 59 85 59 84 59 83 59 82 59 81 Y.Y.Y.Y.Y.Y.Y.Y. 000004D0 59 80 59 7F 59 7E 59 7D 59 7C 59 7B 59 7A 59 79 Y.Y.Y~Y}Y|Y{YzYy 000004E0 59 78 59 77 59 76 59 75 00 FF 00 FF 00 FF 00 FF YxYwYvYu........ 000004F0 59 70 00 01 00 01 30 22 AF 22 00 05 00 0F 01 B7 Yp....0"."...... 00000500 05 10 00 02 00 00 15 57 00 FF 00 FF 00 FF 00 FF .......W........ -------- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- ----------------

2.9.2 dmm (disable message monitoring)

FunctionWith this command you deactivate the message monitoring with the desired filtering cri-teria. The full form of this command is disable message monitoring (dmm).

Syntaxdmm <processor type>{:<dsp id>}{:<src id>} <processor type>{:<dsp id>}{:<dst id>} <direction_flag> [<msg type>] [<payload offset> <pattern>]


This parameter specifies the card type. If it is specified to src ID, it specifies the src pro-cessor type. In other cases, it specifies the dst processor type. The allowable values are 'pq2', 'bsc' and 'dsp'.

dsp id


src id

78 DN0479352Issue 4-2


Id:0900d805806444bc


This parameter specifies the source application ID from where the message is simulated to have been originated. For the application IDs, see section Application IDs for com-mands.

dst id

This parameter specifies the destination application ID to which the message needs to be sent. For the application IDs, see section Application IDs for commands.

msg type

This parameter specifies the message type to be sent.

payload offset

This paramete specifies the offset from which the comparison is to begin.

pattern

This parameter specifies the pattern to be compared from the offset 'payload offset'.

direction_flag

This parameter specifies the direction in which the monitoring is to be done. Valid values are:

0 - Monitor message at both directions

1 - Monitor message at sender

2 - Monitor message at receiver

Examples

1. Disable message monitoring from application 1 at PQII to application 1 on DSP 1 for message type as 12, to monitor at both directions.dmm pq2:1 dsp:1:1 0 12

2. Disable message monitoring from application 1 at PQII to application 1 on DSP 1 for message type as 12, to monitor at sender.dmm pq2:1 dsp:1:1 1 12

3. Disable message monitoring from application 1 at PQII to application 1 on DSP 1 for message type as 12, to monitor at receiver.dmm pq2:1 dsp:1:1 2 12

4. Disable message monitoring from application 1 at DSP 1 to application 2 on PQII for message pattern "01 02 03 04" from location 12, to monitor at receiver.dmm dsp:1:1 pq2:1 2 12 "01 02 03 04"

Execution printoutsBCSU/32/PCU/4/OSE>dmm pq2:1 dsp:1:1 0 12 ----------------------------------------------------------------> Command dmm executed on [1/1/2004 0:6:15:210001] <---- ------------------------------------------------------------MM Disable on PQII and DSP[1] successful

No log messages will be generated by the applications.

2.9.3 dimm (display message monitoring configuration)

FunctionThe full form of this command is display message monitoring configuration (dimm).

DN0479352Issue 4-2

79


Id:0900d805806444bc

Syntaxdimm <processor type>{:<dsp id>}



dsp id

This parameter specifies the DSP ID. The values range from 0 to 7. The parameter needs to be specified only in case the processor type is DSP.

Examples

1. Display the message monitoring configuration for pq2.dimm pq2

2. Display the message monitoring configuration for DSP ID '1'.dimm dsp:1

Execution printoutsBCSU/0/PCU/0/OSE>dimm pq2 ----------------------------------------------------------------> Command dimm executed on [1/1/2004 0:0:33:69001] <---- --------------------------------------------------------------------------------------------------------------- card_type:<dsp_id:>src_app_id card_type:<dsp_id>:dst_app_id [msg_type] [offset, "mask_val"] [dir_flag]

pq2:* pq2:* [*] [NA][->]

2.9.4 damm (disable all message monitoring)

FunctionThe full form of this command is disable all message monitoring (damm).

Syntaxdamm

Examples

1. Disable all message monitoring.damm

Execution printoutsBCSU/0/PCU/0/OSE>damm ----------------------------------------------------------------> Command damm executed on [1/1/2004 0:0:53:831634] <---- ------------------------------------------------------------Disabled all message monitoring...

80 DN0479352Issue 4-2


Id:0900d805806444bc


2.9.5 emml (enable MM data logging)

FunctionWith this command you log the output of all the MM messages. The full form of this command is enable MM data logging (emml). This command can be typically used when you need to capture the output into a file for offline analysis.

Syntaxemml <filename> <size_in _bytes>


The name of the file in which the logs are to be captured. The filename must have the extension '.log'.

size_in_bytes

The maximum size of the file. In case the logs exceed the maximum file size, the file is wrapped around.

Examples

1. Enable message monitoring logging to a file named 'st_mm_logs.log' with size of 5000 bytes.emml st_mm_logs.log 5000

Execution printoutsBCSU/0/PCU/0/OSE/ML>emml st_mm_logs.log 5000 ----------------------------------------------------------------> Command emml executed on [1/1/2004 0:10:51:930001] <---- ------------------------------------------------------------ ******************************************************** Enabled MM Service Terminal Logging to a file Filename: /ram/st_mm_logs.log Size: 5000 Please note that every time the file exceeds Size: 5000 bytes file will be wrapped around ********************************************************************** Enabling this command may affect the performance of the System **********************************************************************

2.9.6 dmml (disable MM data logging)

FunctionThe full form of this command is disable MM data logging (dmml).

!


DN0479352Issue 4-2

81


Id:0900d805806444bc

Syntaxdmml

Examples

1. Disable the message monitoring logging to a file.dmml

Execution printoutsBCSU/0/PCU/0/OSE>dmml ----------------------------------------------------------------> Command dmml executed on [1/1/2004 0:11:13:260001] <---- ------------------------------------------------------------ ******************************************************** Disabled Service Terminal MM Logging to a file Filename: /ram/st_mm_logs.log Size: 5000 ********************************************************

2.10 IP manipulation commandsThis section contains the commands which apply to the IP manipulation category of the service terminal. The commands are provided by the IPNET IP stack.

2.10.1 ifconfig

FunctionWith this command you configure the network interface and/or configure network inter-face parameters. It can also be used to change/display the IP address of the PIU.

Syntaxifconfig <interface> <family> add <address> [optional parameters]

or

ifconfig <interface> <family> delete <address>

or

ifconfig <interface> <family> dstaddr <address>

or

ifconfig <interface> mtu <value>

or

ifconfig <interface> up

or

ifconfig <interface> down

or

ifconfig <interface> detach

or

ifconfig <interface> dhcp

82 DN0479352Issue 4-2


Id:0900d805806444bc


or

ifconfig <interface> -dhcp

or

ifconfig <interface> rtab <value>

or

ifconfig [<interface> | -a]

Parameter explanations–a

List all interfaces.

add <a>

Add 'a' IPv4 or IPv6 address.

delete <a>

Delete 'a' IPv4 or IPv6 address.

dstaddr <a>

Set remote address to 'a' (inet and PPP only).

mtu <v>

Set interface MTU to 'v'.

up

Bring the interface up.

down

Bring the interface down.

detach

Detaches the interface. Note that the interface must be down first.

rtab <v>

Set route table index to 'v' (default = 0).

dhcp

Enable dhcp auto configuration (inet only).

-dhcp

Disable dhcp auto configuration (inet only).

address

The IPv4 or IPv6 address.

family

Address family. 'inet' or 'inet6'.

interface

Name of the interface.

value

Numeric value depending on the command.

netmask <a.b.c.d>

Set interface netmask to 'a.b.c.d' (inet only).

DN0479352Issue 4-2

83


Id:0900d805806444bc

prefixlen <value>

Set interface prefix (mask length) length to 'n'.

tentative

Perform DAD before setting address (inet6 only).

Examples

1. Display the configuration of all the interfaces.ifconfig -a

Execution printoutsBCSU/31/PCU/4/OSE>ifconfig -a lo Link type:Local loopback Queue:None inet 127.0.0.1 mask 255.0.0.0 inet6 unicast fe80::1%lo prefixlen 64 inet6 unicast ::1 prefixlen 128 inet6 multicast ff02::1%lo prefixlen 16 inet6 multicast ff01::1 prefixlen 16 UP RUNNING LOOPBACK MULTICAST mtu:1500 metric:1 rtab:0 RX packets:16 mcast:4 errors:0 dropped:3 TX packets:8 mcast:0 errors:0 collisions:0 unsupported proto:0 RX bytes:1088 TX bytes:544

ifeth0 Link type:Ethernet HWaddr 00:40:43:e2:3e:8e Queue:FIFO inet 10.8.201.102 mask 255.255.255.0 broadcast 10.8.201.255 inet6 unicast fe80::240:43ff:fee2:3e8e%ifeth0 prefixlen 64 inet6 multicast ff02::1%ifeth0 prefixlen 16 inet6 multicast ff02::1:ffe2:3e8e%ifeth0 prefixlen 16 UP RUNNING SIMPLEX BROADCAST MULTICAST mtu:1500 metric:1 rtab:0 RX packets:41 mcast:25 errors:0 dropped:0 TX packets:3 mcast:2 errors:0 collisions:0 unsupported proto:0 RX bytes:3710 TX bytes:206

ifeth1 Link type:Ethernet HWaddr 00:40:43:e2:3e:8f Queue:FIFO inet6 unicast fe80::240:43ff:fee2:3e8f%ifeth1 prefixlen 64 inet6 multicast ff02::1%ifeth1 prefixlen 16 inet6 multicast ff02::1:ffe2:3e8f%ifeth1 prefixlen 16 UP RUNNING SIMPLEX BROADCAST MULTICAST mtu:1500 metric:1 rtab:0 RX packets:0 mcast:0 errors:0 dropped:0 TX packets:2 mcast:2 errors:0 collisions:0 unsupported proto:0 RX bytes:0 TX bytes:164

BCSU/31/PCU/4/OSE>

2.10.2 netstat

FunctionWith this command you query the information about the interfaces on a system. The command displays current TCP/IP network connections and protocol statistics. The command can also be used to display the routing tables. The netstat program displays and modifies the Internet-to-Ethernet address translation tables used by the address resolution protocol.

Syntaxnetstat [-anh] [-f address_family] [-p protocol]

84 DN0479352Issue 4-2


Id:0900d805806444bc


or

netstat -r [-n] [-f address_family]

Parameter explanations-a

This parameter displays the state of all sockets. Normally the sockets used by server processes are not shown.

-n

This parameter displays the network addresses as numbers. The default is to look up symbolic names for the addresses.

-i

This parameter displays the interface information such as MTU, input and output packets and errors, collisions and size of output queue, etc.

-h

This parameter displays help for the usage menu.

-f address_family

This parameter limits the statistics or address control block reports to those of the spec-ified address family. The following address families are recognized: inet for IP_AF_INET and inet6 for IP_AF_INET6.

-p protocol

This parameter displays statistics for a protocol. You can enter either a well-known name for a protocol or an alias for it.

-r

This parameter displays the routing tables.

-v <routetab>

This parameter specifies the routing table. If the value is not specified, the default is 0.

-l

With this parameter, the routes are not displays where the LLINFO flag is set.

Examples

1. Display the configuration of all the interfaces.netstat -a

2. Display the routing table.netstat -r

3. Display interface information such as MTU, input and output packets and errors, col-lisions and size of output queue, etc.netstat -i

Execution printoutsThe execution printout for example 1 is the following:

BCSU/0/PCU/0/OSE>netstat -a INET sockets Prot Fd Rt Local Address Foreign Address State ICMP 22 0 0.0.0.0.* 0.0.0.0.* ICMP 23 0 0.0.0.0.* 0.0.0.0.*

DN0479352Issue 4-2

85


Id:0900d805806444bc

TCP 11 0 0.0.0.0.23 0.0.0.0.* LISTEN

TCP 25 0 10.3.3.140.23 192.168.0.190.1907 ESTABLISHEDTCP 27 0 127.0.0.1.49158 127.0.0.1.49157 ESTABLISHEDTCP 28 0 127.0.0.1.49157 127.0.0.1.49158 ESTABLISHED UDP 10 0 0.0.0.0.* 0.0.0.0.* UDP 19 0 0.0.0.0.49155 0.0.0.0.* UDP 20 0 0.0.0.0.49156 0.0.0.0.* UDP 21 0 0.0.0.0.5000 0.0.0.0.*

INET6 sockets Prot Fd Rt Local Address Foreign Address State TCP 12 0 ::.23 ::.* LISTEN UDP 14 0 ::1.20065 ::1.20064 ICMP6 13 0 ::.* ::.* ICMP6 24 0 ::.* ::.*

BCSU/0/PCU/0/OSE>

The execution printout for example 2 is the following:

BCSU/0/PCU/0/OSE>netstat -r INET route table Destination Gateway Flags Use If

0.0.0.0/0 10.3.3.2 UGS 20993 ifeth0

10.3.3.0/24 link#2 UC 12 ifeth0

10.3.3.2 00:0d:28:22:ff:ff UHL 11 ifeth0

10.3.3.140 link#1 UH 0 lo

127.0.0.0/8 link#1 URS 0 lo

127.0.0.1 link#1 UH 7436 lo

224.0.0.0/4 * R 0 *

255.255.255.255 * HR 0 *

INET6 route tableDestination Gateway Flags Use If

::1 link#1 UH 4 lo

FE80::%lo/64 link#1 UC 0 lo

FE80::%ifeth0/64 link#2 UC 0 ifeth0

86 DN0479352Issue 4-2


Id:0900d805806444bc


FE80::%ifeth1/64 link#3 UC 0 ifeth1 FE80::1%lo link#1 UH 0 lo FE80::1814:18FF:FE17:1916%ifeth1 link#1 UH 0 lo FE80::1814:18FF:FE17:1A15%ifeth0 link#1 UH 0 lo FF00::/8 link#1 U 0 lo FF01::/16 link#1 U 0 lo FF02::%lo/16 link#1 U 0 lo FF02::%ifeth0/16 link#2 U 4 ifeth0 FF02::%ifeth1/16 link#3 U 4 ifeth BCSU/0/PCU/0/OSE>


BCSU/0/PCU/0/OSE>netstat -i Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll Iqdrops Noproto lo 1500 127.0.0.0/8 127.0.0.1 24262 0 12131 0 0 3 0 lo 1500 FF02::/16 FF02::1 24262 0 12131 0 0 3 0 lo 1500 FE80::/64 FE80::1 24262 0 12131 0 0 3 0 lo 1500 ::1/128 ::1 24262 0 12131 0 0 3 0 lo 1500 FF01::/16 FF01::1 24262 0 12131 0 0 3 0 lo 1500 FF02::/16 FF02::1 24262 0 12131 0 0 3 0 lo 1500 FE80::/64 FE80::1 24262 0 12131 0 0 3 0 lo 1500 ::1/128 ::1 24262 0 12131 0 0 3 0 lo 1500 FF01::/16 FF01::1 24262 0 12131 0 0 3 0ifeth0 1500 10.3.3.0/24 10.3.3.140 265704 0 86206 0 0 49 0 ifeth0 1500 FF02::/16 FF02::1 265704 0 86206 0 0 49 0 ifeth0 1500 FF02::/16 FF02::1:FF17:1A15 265704 0 86206 0 0 49 0 ifeth0 1500 FE80::/64 FE80::1814:18FF:FE17:1A15 265704 0 86206 0 0 49 0 ifeth0 1500 FF02::/16 FF02::1 265704 0 86206 0 0 49 0 ifeth0 1500 FF02::/16 FF02::1:FF17:1A15 265704 0 86206 0 0 49 0 ifeth0 1500 FE80::/64 FE80::1814:18FF:FE17:1A15 265704 0 86206 0 0 49 0 ifeth1 1500 FF02::/16 FF02::1 117 0 2 0 0 0 0 ifeth1 1500 FF02::/16 FF02::1:FF17:1916 117 0 2 0 0 0 0 ifeth1 1500 FE80::/64 FE80::1814:18FF:FE17:1916 117 0 2 0 0 0 0 ifeth1 1500 FF02::/16 FF02::1 117 0 2 0 0 0 0 ifeth1 1500 FF02::/16 FF02::1:FF17:1916 117 0 2 0 0 0 0 ifeth1 1500 FE80::/64 FE80::1814:18FF:FE17:1916 117 0 2 0 0 0 0 BCSU/0/PCU/0/OSE>

DN0479352Issue 4-2

87


Id:0900d805806444bc

2.10.3 ping

FunctionWith this command you test whether another host is reachable or not. The program sends ICMPv4 ECHO_REQUEST packets to network hosts and expects a reply from the host in return. ping uses the ICMPv4 protocol's mandatory ECHO_REQUEST datagram to elicit an ECHO_REPLY from a host or a gateway. The program also measures the round trip time to the host, giving some indication of how far away that host is. It also displays ttl (time to live) and round trip time.

Syntaxping [-nbAD] [-c count] [-T ttl] [-s packetsize] [-V routetab] [-w ms] host

Parameter explanations-A

This parameter adds a router alert option to each sent ping request.

-b

This parameter allows the pinging of a broadcast address.

-c count

This parameter stops after sending count ECHO_RESPONSE packets.

-D

This parameter sets the DF (do not fragment) flag on each sent ping request.

-n

This parameter outputs numeric data only. No attempts will be made to look up names for the host addresses.

-r

This parameter bypasses the normal routing tables and sends directly to a host on an attached network.

-s packetsize

This parameter specifies the number of data bytes to be sent. The default is 56, which translates into 64 ICMP data bytes when combined with the 8 bytes of the ICMP header data.

-S src_addr

This parameter specifies the address to be used as a source address when sending.

-T ttl

With this parameter, you can use the specified time-to-live.

-t

This parameter pings the specified host until stopped.

-V

This parameter specifies the routing table. If the value is not specified, the default is 0.

-w

This parameter specifies the timeout in milliseconds, the default is 1000 ms.

88 DN0479352Issue 4-2


Id:0900d805806444bc


Examples

1. Send ECHO_REQUEST packets to 10.3.3.2.ping 10.3.3.2

2. Send ECHO_REQUEST packets to 10.3.3.2 with 128 as the packet size.ping -s 128 10.3.3.2

3. Send ECHO_REQUEST packets to 10.3.3.2 so that the sending is stopped after 5 packets.ping -c 5 10.3.3.2


BCSU/0/PCU/0/OSE>ping 10.3.3.2 ----------------------------------------------------------------> Command ping executed on [30/11/2005 18:53:21:710875] <---- ------------------------------------------------------------ Pinging 10.3.3.2 (10.3.3.2) with 64 bytes of data: Reply from 10.3.3.2 bytes=64 time=2ms ttl=255 Reply from 10.3.3.2 bytes=64 time=1ms ttl=255 Reply from 10.3.3.2 bytes=64 time=2ms ttl=255 Reply from 10.3.3.2 bytes=64 time=2ms ttl=255BCSU/0/PCU/0/OSE>


BCSU/0/PCU/0/OSE>ping -s 128 10.3.3.2 ----------------------------------------------------------------> Command ping executed on [30/11/2005 18:53:21:710875] <---- ------------------------------------------------------------ Pinging 10.3.3.2 (10.3.3.2) with 128 bytes of data: Reply from 10.3.3.2 bytes=128 time=2ms ttl=255 Reply from 10.3.3.2 bytes=128 time=3ms ttl=255 Reply from 10.3.3.2 bytes=128 time=3ms ttl=255 Reply from 10.3.3.2 bytes=128 time=3ms ttl=255 BCSU/0/PCU/0/OSE>


BCSU/0/PCU/0/OSE>ping -c 5 10.3.3.2 ----------------------------------------------------------------> Command ping executed on [30/11/2005 18:53:21:710875] <---- ------------------------------------------------------------ Pinging 10.3.3.2 (10.3.3.2) with 64 bytes of data: Reply from 10.3.3.2 bytes=64 time=3ms ttl=255 Reply from 10.3.3.2 bytes=64 time=2ms ttl=255 Reply from 10.3.3.2 bytes=64 time=2ms ttl=255 Reply from 10.3.3.2 bytes=64 time=2ms ttl=255Reply from 10.3.3.2 bytes=64 time=3ms ttl=255 BCSU/0/PCU/0/OSE>

DN0479352Issue 4-2

89


Id:0900d805806444bc

2.10.4 ping6

FunctionWith this command you test whether another host is reachable or not. The program sends ICMPv6 ECHO_REQUEST packets to network hosts and expects a reply from the host in return. ping6 uses the ICMPv6 protocol's mandatory ICMP6_ECHO_REQUEST datagram to elicit an ICMP6_ECHO_REPLY from a host or a gateway. ICMP6_ECHO_REQUEST datagrams (“pings”) have an IPv6 header and an ICMPv6 header formatted as documented in RFC2463. It is possible to specify addi-tional nodes that the ping request must visit before reaching its final destination. This is accomplished by adding a routing header to the packet.

Syntaxping6 [-n] [-c count] [-h hoplimit] [-s packetsize] [hop ...] host

Parameter explanations-c count

This parameter stops after sending count ECHO_RESPONSE packets.

-h hoplimit

With this parameter you set the IPv6 hop limit.-n

This parameter outputs numeric data only. No attempts will be made to look up names for host addresses.

-r

This parameter bypasses the normal routing tables and sends directly to a host on an attached network.

-s packetsize

This parameter specifies the number of data bytes to be sent. The default is 56, which translates into 64 ICMP data bytes when combined with the 8 bytes of the ICMP header data.

-t

This parameter pings the specified host until stopped.

-V routetab

With this parameter you specify the routing table. If the value is not specified the default is 0.

-w timeout

This parameter specifies the timeout in milliseconds, the default is 1000 ms.

Examples

1. Send ECHO_REQUEST packets to FF02::1.ping6 FF02::1

2. Send ECHO_REQUEST packets to FF02::1 with 128 as the packet size.ping6 -s 128 FF02::1

3. Send ECHO_REQUEST packets to FF02::1 so that the sending is stopped after 5 packets.ping6 -c 5 FF02::1

90 DN0479352Issue 4-2


Id:0900d805806444bc



BCSU/0/PCU/0/OSE>ping6 FF02::1 ----------------------------------------------------------------> Command ping6 executed on [30/11/2005 18:53:21:710875] <---- ------------------------------------------------------------ Pinging FF02::1 (FF02::1) with 64 bytes of data: Reply from FE80::1 bytes=64 time=0ms hlim=255 Reply from FE80::1 bytes=64 time=0ms hlim=255 Reply from FE80::1 bytes=64 time=0ms hlim=255 Reply from FE80::1 bytes=64 time=0ms hlim=255BCSU/0/PCU/0/OSE>


BCSU/0/PCU/0/OSE>ping6 -s 128 FF02::1 ----------------------------------------------------------------> Command ping6 executed on [30/11/2005 18:53:21:710875] <---- ------------------------------------------------------------ Pinging FF02::1 (FF02::1) with 128 bytes of data: Reply from FE80::1 bytes=128 time=0ms hlim=255 Reply from FE80::1 bytes=128 time=0ms hlim=255 Reply from FE80::1 bytes=128 time=0ms hlim=255 Reply from FE80::1 bytes=128 time=0ms hlim=255 BCSU/0/PCU/0/OSE>


BCSU/0/PCU/0/OSE>ping6 -c 5 FF02::1 ----------------------------------------------------------------> Command ping6 executed on [30/11/2005 18:53:21:710875] <---- ------------------------------------------------------------ Pinging FF02::1 (FF02::1) with 64 bytes of data: Reply from FE80::1 bytes=64 time=0ms hlim=255 Reply from FE80::1 bytes=64 time=0ms hlim=255 Reply from FE80::1 bytes=64 time=0ms hlim=255 Reply from FE80::1 bytes=64 time=0ms hlim=255Reply from FE80::1 bytes=64 time=0ms hlim=255 BCSU/0/PCU/0/OSE>

2.11 Radio network–related commandsThis section contains the commands for radio network configuration display. They are helpful in examining the current network configuration and its related problems.

DN0479352Issue 4-2

91


Id:0900d805806444bc

2.11.1 dtrxrnw (display the radio network configuration for a particular TRX)

FunctionWith this command you display the radio network configuration for a particular TRX (dtrxrnw).

Syntaxdtrxrnw <bts id> <trx id>

Parameter explanationsbts id

This parameter specifies the BTS ID.

trx id

This parameter specifies the TRX ID.

Examples

1. Display the radio network configuration with BTS ID '613' and TRX ID '9'.dtrxrnw 613 9

2. Display the radio network configuration with BTS ID '613' and TRX ID '10'.dtrxrnw 613 10


BCSU/31/PCU/3/OSE>dtrxrnw 613 9----------------------------------------------------------------> Command dtrxrnw executed on [16/4/2007 15:15:50:624533] <----------------------------------------------------------------BTS_ID:613 TRX_ID:9 ARFCN:640 Access Tech:GSM 1900TX_Power:15 Hopping:NO Territory_Type:EGPRS_CS1_CS4DSP Id : 0 CONTR_BCSU_ADDR : 16731E-TRX : NODLDC TRX : YES

Num_of_PSW_TSLs:5 TSL_3:DEDICATED TSL_4:DEDICATED TSL_5:DEDICATED TSL_6:DEDICATED TSL_7:DEDICATEDEDAP id : 613Ext PCM Line of the SMCH : 8137Ext PCM TSL (64 K) of the SMCH : 14Ext PCM STSL (16 K) of the SMCH : 0BTS id of SMCH: 613TRX id of SMCH: 9RTSL of SMCH : 7BCSU/30/PCU/4/OSE>


92 DN0479352Issue 4-2


Id:0900d805806444bc


BCSU/31/PCU/3/OSE>dtrxrnw 613 10----------------------------------------------------------------> Command dtrxrnw executed on [16/4/2007 15:15:54:24550] <----------------------------------------------------------------BTS_ID:613 TRX_ID:10 ARFCN:645 Access Tech:GSM 1900TX_Power:15 Hopping:NO Territory_Type:EGPRS_CS1_CS4DSP Id : 0 CONTR_BCSU_ADDR : 16731E-TRX : YESDLDC TRX : NO

Num_of_PSW_TSLs:6 TSL_2:EGTCH TSL_3:EGTCH TSL_4:EGTCH TSL_5:EGTCH TSL_6:EGTCH TSL_7:EGTCHEDAP id : 613Ext PCM Line of the SMCH : 8137Ext PCM TSL (64 K) of the SMCH : 14Ext PCM STSL (16 K) of the SMCH : 0BTS id of SMCH: 613TRX id of SMCH: 9RTSL of SMCH : 7BCSU/30/PCU/4/OSE>

2.11.2 dbtsrnw (display the radio network configuration for a particular BTS)

FunctionWith this command you display the radio network configuration for a particular BTS (dbtsrnw).

Syntaxdbtsrnw <bts id>



Examples

1. Display the radio network configuration for BTS ID '613'.dbtsrnw 613

Execution printoutsBCSU/31/PCU/3/OSE>dbtsrnw 613----------------------------------------------------------------> Command dbtsrnw executed on [16/4/2007 15:15:40:544451] <----------------------------------------------------------------SEG_ID:613 BTS_ID:613 Access_Tech:GSM 1900 Edge_Capable:YESNum_Default_TSLs:11 Num_Dedicated_TSLs:11

DN0479352Issue 4-2

93


Id:0900d805806444bc

NUM_EGTCH: 0 Actual_Num_of_TSLs_for_PSW:11 BCCH_TRX_BCSU: 16731INITIAL MCS FOR ACKNOWLEDGED MODE : MCS1INITIAL MCS FOR UNACKNOWLEDGED MODE : MCS1DL CODING SCHEME IN ACKNOWLEDGED MODE : CS2UL CODING SCHEME IN ACKNOWLEDGED MODE : CS2DL CODING SCHEME IN UNACKNOWLEDGED MODE: CS2UL CODING SCHEME IN UNACKNOWLEDGED MODE: CS2Num_TRX:2Num_E_TRX:0DLDC Enabled:YES

BTS_ID:613 TRX_ID:9 ARFCN:640 Access Tech:GSM 1900TX_Power:15 Hopping:NO Territory_Type:EGPRS_CS1_CS4DSP Id : 0 CONTR_BCSU_ADDR : 16731E-TRX : NODLDC TRX : YES

Num_of_PSW_TSLs:5 TSL_3:DEDICATED TSL_4:DEDICATED TSL_5:DEDICATED TSL_6:DEDICATED TSL_7:DEDICATEDEDAP id : 613Ext PCM Line of the SMCH : 8137Ext PCM TSL (64 K) of the SMCH : 14Ext PCM STSL (16 K) of the SMCH : 0BTS id of SMCH: 613TRX id of SMCH: 9RTSL of SMCH : 7BTS_ID:613 TRX_ID:10 ARFCN:645 Access Tech:GSM 1900TX_Power:15 Hopping:NO Territory_Type:EGPRS_CS1_CS4DSP Id : 0 CONTR_BCSU_ADDR : 16731E-TRX : NODLDC TRX : YES

Num_of_PSW_TSLs:6 TSL_2: DEDICATED TSL_3: DEDICATED TSL_4: DEDICATED TSL_5: DEDICATED TSL_6: DEDICATED TSL_7: DEDICATEDEDAP id : 613Ext PCM Line of the SMCH : 8137Ext PCM TSL (64 K) of the SMCH : 14Ext PCM STSL (16 K) of the SMCH : 0BTS id of SMCH: 613TRX id of SMCH: 9RTSL of SMCH : 7BCSU/30/PCU/4/OSE>

94 DN0479352Issue 4-2


Id:0900d805806444bc


2.11.3 dsegrnw (display the radio network configuration for a particular segment)

FunctionWith this command you display the radio network configuration for a particular segment (dsegrnw).

Syntaxdsegrnw <segment id>

Parameter explanationssegment id

This parameter specifies the segment ID.

Examples

1. Display the radio network configuration for segment ID '613'.dsegrnw 613

Execution printoutsBCSU/31/PCU/3/OSE>dsegrnw 613----------------------------------------------------------------> Command dsegrnw executed on [16/4/2007 15:14:32:46523] <----------------------------------------------------------------SEG_ID:613 Num_BTS:1 BCCH_BCSU_UNIT:16731Num_GRPS_TSLs:0 Num_EGRPS_TSLs:11PCCCH_BTS:613PCCCH_TRX:9PCCCH_TSL:Not ConfiguredPCCCH_DSP_ID:Not ConfiguredNC Mode : 0Ext Cell: NOSEG_ID:613 BTS_ID:613 Access_Tech:GSM 1900 Edge_Capable:YESNum_Default_TSLs:11 Num_Dedicated_TSLs:11 NUM_EGTCH: 0 Actual_Num_of_TSLs_for_PSW:11 BCCH_TRX_BCSU: 16731INITIAL MCS FOR ACKNOWLEDGED MODE : MCS1INITIAL MCS FOR UNACKNOWLEDGED MODE : MCS1DL CODING SCHEME IN ACKNOWLEDGED MODE : CS2UL CODING SCHEME IN ACKNOWLEDGED MODE : CS2DL CODING SCHEME IN UNACKNOWLEDGED MODE: CS2UL CODING SCHEME IN UNACKNOWLEDGED MODE: CS2Num_TRX:2Num_E_TRX:0DLDC Enabled:YES

BTS_ID:613 TRX_ID:9 ARFCN:640 Access Tech:GSM 1900TX_Power:15 Hopping:NO Territory_Type:EGPRS_CS1_CS4DSP Id : 0 CONTR_BCSU_ADDR : 16731E-TRX : NODLDC TRX : YES

Num_of_PSW_TSLs:5 TSL_3:DEDICATED TSL_4:DEDICATED TSL_5:DEDICATED TSL_6:DEDICATED TSL_7:DEDICATED

DN0479352Issue 4-2

95


Id:0900d805806444bc

EDAP id : 613Ext PCM Line of the SMCH : 8137Ext PCM TSL (64 K) of the SMCH : 14Ext PCM STSL (16 K) of the SMCH : 0BTS id of SMCH: 613TRX id of SMCH: 9RTSL of SMCH : 7BTS_ID:613 TRX_ID:10 ARFCN:645 Access Tech:GSM 1900TX_Power:15 Hopping:NO Territory_Type:EGPRS_CS1_CS4DSP Id : 0 CONTR_BCSU_ADDR : 16731E-TRX : NODLDC TRX : YESNum_of_PSW_TSLs:6 TSL_2: DEDICATED TSL_3: DEDICATED TSL_4: DEDICATED TSL_5: DEDICATED TSL_6: DEDICATED TSL_7: DEDICATEDEDAP id : 613Ext PCM Line of the SMCH : 8137Ext PCM TSL (64 K) of the SMCH : 14Ext PCM STSL (16 K) of the SMCH : 0BTS id of SMCH: 613TRX id of SMCH: 9RTSL of SMCH : 7BCSU/30/PCU/4/OSE>

2.12 TBF information commands

2.12.1 dsegtbf (display TBF allocation for a particular segment)

FunctionWith this command you display the TBF allocation for a particular segment (dsegtbf).

Syntaxdsegtbf <segment id>

Parameter explanationssegment id

This parameter specifies the segment ID.

Examples

1. Display the TBF allocation for segment ID '300'.dsegtbf 300

Execution printoutsBCSU/35/PCU/4/OSE>dsegtbf 300----------------------------------------------------------------> Command dsegtbf executed on [22/11/2008 16:4:24:598356] <----------------------------------------------------------------

SEG_ID:300 Num_BTS:1 BCCH_BCSU_UNIT:16735

96 DN0479352Issue 4-2


Id:0900d805806444bc


Num_GPRS_TSLs:0 Num_EGPRS_TSLs:8PCCCH_BTS:300PCCCH_TRX:1PCCCH_TSL:Not ConfiguredPCCCH_DSP_ID:Not ConfiguredNC Mode : 0Ext Cell: NO

SEG_ID:300 BTS_ID:300 Access_Tech:GSM_P Edge_Capable:YESNum_Default_TSLs:23 Num_Dedicated_TSLs:23NUM_EGTCH: 0 Actual_Num_of_TSLs_for_PSW:8 BCCH_TRX_BCSU: 16735INITIAL MCS FOR ACKNOWLEDGED MODE IN NORMAL AREA : MCS6INITIAL MCS FOR UNACKNOWLEDGED MODE IN NORMAL AREA : MCS5

INITIAL MCS FOR ACKNOWLEDGED MODE IN EXTENDED AREA : MCS1INITIAL MCS FOR UNACKNOWLEDGED MODE IN EXTENDED AREA : MCS1

DL CODING SCHEME IN ACKNOWLEDGED MODE IN NORMAL AREA: CS3UL CODING SCHEME IN ACKNOWLEDGED MODE IN NORMAL AREA: CS3DL CODING SCHEME IN UNACKNOWLEDGED MODE IN NORMAL AREA: CS2UL CODING SCHEME IN UNACKNOWLEDGED MODE IN NORMAL AREA: CS2DL CODING SCHEME IN ACKNOWLEDGED MODE IN EXTENDED AREA: CS1UL CODING SCHEME IN ACKNOWLEDGED MODE IN EXTENDED AREA: CS1DL CODING SCHEME IN UNACKNOWLEDGED MODE IN EXTENDED AREA: CS1UL CODING SCHEME IN UNACKNOWLEDGED MODE IN EXTENDED AREA: CS1Num_TRX:2Num_E_TRX:0DLDC Enabled:YES

BTS_ID:300 TRX_ID:1 ARFCN:1 Access Tech:GSM_PTX_Power:0 Hopping:NO Territory_Type:EGPRS_CS1_CS2DSP Id : 0 CONTR_BCSU_ADDR : 16735E-TRX : NODLDC TRX : YES

Num_of_PSW_TSLs:4 TSL_4:DEDICATED TSL_5:DEDICATED TSL_6:DEDICATED TSL_7:DEDICATEDEDAP id : 300Ext PCM Line of the SMCH : 8112Ext PCM TSL (64 K) of the SMCH : 10Ext PCM STSL (16 K) of the SMCH : 2BTS id of SMCH: 300TRX id of SMCH: 1RTSL of SMCH : 5

BTS_ID:300 TRX_ID:3 ARFCN:5 Access Tech:GSM_P

DN0479352Issue 4-2

97


Id:0900d805806444bc

TX_Power:0 Hopping:NO Territory_Type:EGPRS_CS1_CS2DSP Id : 0 CONTR_BCSU_ADDR : 16735E-TRX : NODLDC TRX : YES


BTS ID : 300 [0x12c] TRX ID : 1 [0x1] DSP ID : 0 MULTISLOT CLASS : 33 Direction : UPLINK RLC MODE TBF : ACK TSL NUM Allocated : 6 7 USF : 127 127 127 127 127 127 5 4 TBF STATE : PDM_ULTBF_ACTIVE TBF ID : 8 [0x8] TFI : 6 [0x6] Coding Scheme : MCS9 TBF Data rate : 9.99 KB per sec Direction : DOWNLINK RLC MODE TBF : ACK TSL NUM Allocated : 4 5 6 7 TBF STATE : PDM_DLTBF_ACTIVE TBF ID : 0 [0x0] TFI : 0 [0x0] Coding Scheme : MCS6 TBF Data rate : 10.60 KB per sec TLLI : 3221225480 [0xc0000008] MS_INDEX : 0x012cc0000008 IMSI : 244051090001003 TYPE : EGPRS NC Mode MS : 0 TSL_4 : DOWNLINK TSL_5 : DOWNLINK

98 DN0479352Issue 4-2


Id:0900d805806444bc


TSL_6 : CONCURRENT TSL_7 : CONCURRENT PFI : 0 PFC ID DL : 26684465 [0x1972c31] Guranteed Data Rate DL : 0 RLC MODE PFC : ACK Traffic Class : BEST_EFFORT ARP : ARP3 PFI : 0 PFC ID UL : 26684464 [0x1972c30] Guranteed Data Rate UL : 0 RLC MODE PFC : ACK Traffic Class : BEST_EFFORT ARP : ARP2

DLDC ALLOCATION : YES TRX ID 2 : 3 [0x3] TSL NUM Allocated : 4 5 6 7 TSL_4 : DOWNLINK TSL_5 : DOWNLINK TSL_6 : DOWNLINK TSL_7 : DOWNLINK

BCSU/35/PCU/4/OSE>

2.12.2 dtrxtbf (display the TBF information for a particular TRX)

FunctionThis command is used to display the TBF information for a particular TRX (dtrxtbf).

Syntaxdtrxtbf <bts id> <trx id>



trx id


Examples

1. Display the TBF information for BTS ID '300' and TRX ID '3'.dtrxtbf 300 3

Execution printoutsBCSU/35/PCU/4/OSE> dtrxtbf 300 3----------------------------------------------------------------> Command dtrxtbf executed on [22/11/2008 16:19:56:313010] <----

DN0479352Issue 4-2

99


Id:0900d805806444bc

------------------------------------------------------------



BTS ID : 300 [0x12c] TRX ID : 1 [0x1] DSP ID : 0 MULTISLOT CLASS : 33 Direction : UPLINK RLC MODE TBF : ACK TSL NUM Allocated : 6 7 USF : 127 127 127 127 127 127 6 3 TBF STATE : PDM_ULTBF_ACTIVE TBF ID : 8 [0x8] TFI : 11 [0xb] Coding Scheme : MCS9 TBF Data rate : 10.09 KB per sec Direction : DOWNLINK RLC MODE TBF : ACK TSL NUM Allocated : 4 5 6 7 TBF STATE : PDM_DLTBF_ACTIVE TBF ID : 0 [0x0] TFI : 21 [0x15] Coding Scheme : MCS6 TBF Data rate : 10.67 KB per sec TLLI : 3221225480 [0xc0000008] MS_INDEX : 0x012cc0000008 IMSI : 244051090001003 TYPE : EGPRS NC Mode MS : 0 TSL_4 : DOWNLINK TSL_5 : DOWNLINK TSL_6 : CONCURRENT

100 DN0479352Issue 4-2


Id:0900d805806444bc


TSL_7 : CONCURRENT PFI : 0 PFC ID DL : 28388817 [0x1b12dd1] Guranteed Data Rate DL : 0 RLC MODE PFC : ACK Traffic Class : BEST_EFFORT ARP : ARP3 PFI : 0 PFC ID UL : 28388816 [0x1b12dd0] Guranteed Data Rate UL : 0 RLC MODE PFC : ACK Traffic Class : BEST_EFFORT ARP : ARP2


BCSU/35/PCU/4/OSE>

2.12.3 dtfitbf (display the TBF information specific to identified TFI)

FunctionWith this command you display the TBF information specific to identified temporary flow identity (TFI) (dtfitbf).

Syntaxdtfitbf <bts id> <trx id> <tsl> <tfi>



trx id


tsl

This parameter specifies the TSL.

tfi

This parameter specifies the TFI.

Examples

1. Display the TBF information for BTS '300', TRX '3', TSL '7' and TFI '21'.dtfitbf 300 3 7 21

DN0479352Issue 4-2

101


Id:0900d805806444bc

Execution printoutsBCSU/35/PCU/4/OSE>dtfitbf 300 3 7 21----------------------------------------------------------------> Command dtfitbf executed on [22/11/2008 16:22:58:990670] <----------------------------------------------------------------

**************************START OF TRACE****************************BTS_ID: 300 TRX_ID: 3 TSL: 7 TFI: 21



BTS ID : 300 [0x12c] TRX ID : 1 [0x1] DSP ID : 0 MULTISLOT CLASS : 33 Direction : UPLINK RLC MODE TBF : ACK TSL NUM Allocated : 6 7 USF : 127 127 127 127 127 127 4 1 TBF STATE : PDM_ULTBF_ACTIVE TBF ID : 8 [0x8] TFI : 17 [0x11] Coding Scheme : MCS9 TBF Data rate : 0.01 KB per sec Direction : DOWNLINK RLC MODE TBF : ACK TSL NUM Allocated : 4 5 6 7 TBF STATE : PDM_DLTBF_ACTIVE TBF ID : 0 [0x0] TFI : 21 [0x15] Coding Scheme : MCS3 TBF Data rate : 10.69 KB per sec

102 DN0479352Issue 4-2


Id:0900d805806444bc


TLLI : 3221225480 [0xc0000008] MS_INDEX : 0x012cc0000008 IMSI : 244051090001003 TYPE : EGPRS NC Mode MS : 0 TSL_4 : DOWNLINK TSL_5 : DOWNLINK TSL_6 : CONCURRENT TSL_7 : CONCURRENT PFI : 0 PFC ID DL : 28388817 [0x1b12dd1] Guranteed Data Rate DL : 0 RLC MODE PFC : ACK Traffic Class : BEST_EFFORT ARP : ARP3 PFI : 0 PFC ID UL : 28388816 [0x1b12dd0] Guranteed Data Rate UL : 0 RLC MODE PFC : ACK Traffic Class : BEST_EFFORT ARP : ARP2


BCSU/35/PCU/4/OSE>

2.12.4 dtsltbf (display the TBF information specific to identified TSL)

FunctionWith this command you display the TBF information specific to identified TSL (dtsltbf).

Syntaxdtsltbf <bts id> <trx id> <tsl>



trx id


tsl

This parameter specifies the TSL.

DN0479352Issue 4-2

103


Id:0900d805806444bc

Examples

1. Display the information for a TSL with BTS ID '300', TRX ID '3' and TSL ID '7'.dtsltbf 300 3 7

Execution printoutsBCSU/35/PCU/4/OSE>dtsltbf 300 3 7 ----------------------------------------------------------------> Command dtsltbf executed on [22/11/2008 16:25:31:577175] <----------------------------------------------------------------

**************************START OF TRACE****************************BTS_ID: 300 TRX_ID: 3 TSL: 7



BTS ID : 300 [0x12c] TRX ID : 1 [0x1] DSP ID : 0 MULTISLOT CLASS : 33 Direction : UPLINK RLC MODE TBF : ACK TSL NUM Allocated : 6 7 USF : 127 127 127 127 127 127 6 3 TBF STATE : PDM_ULTBF_ACTIVE TBF ID : 8 [0x8] TFI : 17 [0x11] Coding Scheme : MCS9 TBF Data rate : 0.01 KB per sec Direction : DOWNLINK RLC MODE TBF : ACK TSL NUM Allocated : 4 5 6 7 TBF STATE : PDM_DLTBF_ACTIVE

104 DN0479352Issue 4-2


Id:0900d805806444bc


TBF ID : 0 [0x0] TFI : 20 [0x14] Coding Scheme : MCS4 TBF Data rate : 10.69 KB per sec TLLI : 3221225480 [0xc0000008] MS_INDEX : 0x012cc0000008 IMSI : 244051090001003 TYPE : EGPRS NC Mode MS : 0 TSL_4 : DOWNLINK TSL_5 : DOWNLINK TSL_6 : CONCURRENT TSL_7 : CONCURRENT PFI : 0 PFC ID UL : 28388816 [0x1b12dd0] Guranteed Data Rate UL : 0 RLC MODE PFC : ACK Traffic Class : BEST_EFFORT ARP : ARP2 PFI : 0 PFC ID DL : 28388817 [0x1b12dd1] Guranteed Data Rate DL : 0 RLC MODE PFC : ACK Traffic Class : BEST_EFFORT ARP : ARP3


BCSU/35/PCU/4/OSE>

2.12.5 dpcutbf (display number of UL and DL TBFs for all active segments in the PCU)

FunctionWith this command you display the number of uplink and downlink TBFs for all active segments in the PCU. This command also gives information on the number of TRXs in the segment and the DSPs which are handling the TRXs of a segment.

You can also choose to display the number of Downlink Dual Carrier (DLDC) TBFs ongoing in each segment. If there are no DLDC TBFs in a segment, the segment is not included in the printout.

DN0479352Issue 4-2

105


Id:0900d805806444bc

Syntaxdpcutbf [-dldc]

Parameter explanations-dldc

This parameter displays the number of Downlink Dual Carrier (DLDC) TBFs ongoing in each segment.

Examples

1. Display the TBF and DSP allocation for all segments.dpcutbf

2. Display the TBF and DSP allocation for all segments including ongoing DLDC TBFs.dpcutbf -dldc


BCSU/35/PCU/4/OSE>dpcutbf----------------------------------------------------------------> Command dpcutbf executed on [22/11/2008 16:26:42:534962] <----------------------------------------------------------------

**************************START OF TRACE****************************SEG-ID Num-TRX DSP-ID Num-UL-TBFs Num-DL-TBFs300 2 0 4 4---------------------------------------------------------------------- TOTAL: 4 4----------------------------------------------------------------------**************************END OF TRACE****************************


BCSU/35/PCU/4/OSE>dpcutbf -dldc----------------------------------------------------------------> Command dpcutbf executed on [22/11/2008 16:26:49:165095] <----------------------------------------------------------------

**************************START OF TRACE****************************SEG-ID Num-TRX DSP-ID Num-UL-TBFs Num-DL-TBFs Num-DLDC-TBFs300 2 0 4 4 4---------------------------------------------------------------------- TOTAL: 4 4 4----------------------------------------------------------------------**************************END OF TRACE****************************BCSU/35/PCU/4/OSE>

106 DN0479352Issue 4-2


Id:0900d805806444bc


2.13 Gb–related commands

2.13.1 dgb (display Gb configuration)

FunctionWith this command you display Gb configuration (dgb).

Syntaxdgb

Examples

1. Display the Gb configuration.dgb

Execution printoutsBCSU/31/PCU/4/OSE>dgb ----------------------------------------------------------------> Command dgb executed on [8/6/2005 17:29:45:591698] <---- ------------------------------------------------------------************************ Start of Trace ************************ Bearer Network in use is Frame Relay BVCs in Use : Segment ID::88 BVC ID::10088 Segment ID::99 BVC ID::10099 Number of BVCs Configured : 2 NSEI value configured::4095 NSVCs information : NSVC ID::4095 DLCI Value::991Number of NSVCs Configured : 1 GB Timers and Counters values: Parameter T_TNS_BLOCK :: 300 Parameter T_TNS_RESET :: 300 Parameter T_TNS_TEST :: 500 Parameter T_TNS_ALIVE :: 300 Parameter T_TNS_FLOW :: 100 Parameter NS_BLOCK_RETRIES :: 3 Parameter NS_UNBLOCK_RETRIES :: 3 Parameter NS_ALIVE_RETRIES :: 10 Parameter NS_RESET_RETRIES :: 255 Parameter T_TGB_BLOCK :: 300 Parameter T_TGB_RESET :: 300 Parameter T_TGB_SUSPEND :: 300 Parameter T_TGB_FLOW :: 100 Parameter BVC_BLOCK_RETRIES :: 3 Parameter BVC_UNBLOCK_RETRIES :: 3 Parameter BVC_RESET_RETRIES :: 3 Parameter BVC_SUSPEND_RETRIES :: 3 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 Parameter FC_MS_R_DEF :: 3000 Parameter FC_MS_R_DEF_EGPRS :: 4500 Parameter FC_MS_R_MIN :: 40 Parameter FC_MS_B_MAX_DEF :: 7500 Parameter FC_MS_B_MAX_DEF_EGPRS :: 12500 Parameter FC_R_TSL :: 1500 Parameter FC_R_TSL_EGPRS :: 4500 Parameter FC_B_MAX_TSL :: 25000 Parameter FC_B_MAX_TSL_EGPRS :: 25000 Parameter FC_FORG_FACTOR :: 500

DN0479352Issue 4-2

107


Id:0900d805806444bc

Parameter T_SNS_PROV :: 3 Parameter T_SNS_ADD_RETRIES :: 3 Parameter T_SNS_CONFIG_RETRIES :: 3 Parameter T_SNS_CHANGEWEIGHT_RETRIES :: 3 Parameter T_SNS_DELETE_RETRIES :: 3 Parameter T_SNS_SIZE_RETRIES :: 10 Parameter T_TGB_RAC_UPDATE :: 3 Parameter RAC_UPDATE_RETRIES :: 3 Parameter T_TGB_DNLOAD_BSS_PFC :: 300 Parameter DNLOAD_BSS_PFC_RETRIES :: 3 Parameter T_TGB_MODIFY_BSS_PFC :: 300 Parameter MODIFY_BSS_PFC_RETRIES :: 3 Parameter RESUME_RETRIES_INDEX :: 3 Parameter T_TGB_RESUME :: 65535 ************************* End of Trace ************************* BCSU/31/PCU/4/OSE>

2.13.2 egbm (enable Gb monitoring)

FunctionWith this command you enable Gb interface monitoring (egbm). If the BSSGP virtual connection identifier (BVCI) and the temporal logical link identity (TLLI) are not entered, then all BVCIs and all TLLIs are monitored. If the TLLI is not entered, then the first parameter (after -h/u switch) is considered the BVCI, and that BVCI and all TLLIs are monitored.

Syntaxegbm -[h/u][BVCI] [TLLI]

Parameter explanations–h

This parameter specifies that the data to be output should be in the form of hex dump.

–u

This parameter specifies that the data to be output is in ASCII format (like printf).

BVCI

This parameter specifies the BVCI for which monitoring is to be enabled.

TLLI

This parameter specifies the TLLI for which monitoring is to be enabled.

Examples

1. Enable Gb interface monitoring for BVCI 1 and TLLI 2 in the form of hex dump.egbm -h 1 2

2. Enable Gb interface monitoring for BVCI 1 and all TLLIs the form of hex dump.egbm -h 1

3. Enable Gb interface monitoring for all BVCIs and TLLIs in the form of hex dump.egbm -h

4. Enable Gb interface monitoring for BVCI 1 and TLLI 2 in the ASCII form.egbm -u 1 2

5. Enable Gb interface monitoring for BVCI 1 and all TLLIs the ASCII form.egbm -u 1

108 DN0479352Issue 4-2


Id:0900d805806444bc


6. Enable Gb interface monitoring for BVCI 1 and all TLLIs the ASCII form.egbm -u

Execution printoutsBCSU/0/PCU/0/OSE/GBL>egbm -u 101 ----------------------------------------------------------------> Command egbm executed on [1/1/2004 0:10:6:720001] <---- ------------------------------------------------------------GB Monitoring enabled for:- BVCIs:101 TLLIs:All Configured TLLIs

The following messages will be generated by the applications:GB Monitoring Trace for BVCI:101 and TLLI:?][1/1/2004 0:8:33:24001]BSS --> SGSN FLOW-CONTROL-BVC Tag: 28 BVC Bucket Size : 0 bits/sec. Bucket Leak Rate : 0 bits/sec Bmax : 0 bits/sec. R_default_MS value : 0 bits/sec. BVC Measurment : 0 msec.[GB Monitoring Trace for BVCI:101 and TLLI:?][1/1/2004 0:8:33:24015] SGSN --> BSS FLOW-CONTROL-BVC-ACK Tag: 28

In hex dump:

BCSU/0/PCU/0/OSE/GBL>egbm -h 101 ----------------------------------------------------------------> Command egbm executed on [1/1/2004 0:20:24:825001] <---- ------------------------------------------------------------ GB Monitoring enabled for:- BVCIs:101 TLLIs:All Configured TLLIs BCSU/0/PCU/0/OSE/GBL>

BCSU/0/PCU/0/OSE/GBL> [GB Monitoring Trace for BVCI:101 and TLLI:?][1/1/2004 0:20:32:215001] BSS --> SGSN FLOW-CONTROL-BVC -------- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- ----- ----------- 00000000 26 1E 81 61 05 82 00 00 03 82 00 00 01 82 00 00 &..a............ 00000010 1C 82 00 00 06 82 00 00 ........ -------- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- ----- -----------

[GB Monitoring Trace for BVCI:101 and TLLI:?][1/1/2004 0:20:32:215005] SGSN --> BSS FLOW-CONTROL-BVC-ACK -------- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- ----- ----------- 00000000 27 1E 81 61 '..a -------- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- ----- -----------

e

BCSU/0/PCU/0/OSE/GBL>

DN0479352Issue 4-2

109


Id:0900d805806444bc

2.13.3 dgbm (disable Gb monitoring)

FunctionThis command is used to disable Gb interface monitoring (egbm). The command disables the Gb monitoring for all the BVCIs and TLLIs enabled through the service ter-minal.

Syntaxdgbm

Examples

1. Disable Gb interface monitoring.dgbm

Execution printoutsBCSU/0/PCU/0/OSE/GBL>dgbm ----------------------------------------------------------------> Command dgbm executed on [1/1/2004 0:10:48:560001] <---- ------------------------------------------------------------GB Monitoring Disabled for:- BVCIs:101 TLLIs:All Configured TLLIs BCSU/0/PCU/0/OSE/GBL>

2.13.4 digbm (display Gb monitoring)

FunctionWith this command you display the list of BVCIs and TLLIs for which the Gb monitoring (digbm) is enabled.

Syntaxdigbm

Examples

1. Display the Gb interface monitoring configuration.digbm

Execution printoutsBCSU/0/PCU/0/OSE/GBL>digbm ----------------------------------------------------------------> Command digbm executed on [1/1/2004 0:0:22:70001] <---- ------------------------------------------------------------GB Monitoring Configuration Display GB Monitoring switched ON from Service Terminal ID(s):31 GB Monitoring enabled for:- BVCIs:101 TLLIs:All Configured TLLIs Normal printing flag ON Print header flag OFF BCSU/0/PCU/0/OSE/GBL>

110 DN0479352Issue 4-2


Id:0900d805806444bc


2.13.5 egbl (enable Gb data logging)

FunctionWith this command you log the output of all the Gb interface messages. The full form of this command is enable Gb data logging (egbl). This command can be used when you need to capture the output into a file for offline analysis.

To log Gb interface messages into a file, you should enter the following commands in the following order:

egbm -[h/u][BVCI] [TLLI]

egbl <filename> <size_in_bytes>

After you finish logging, enter the commands dgbm and dgbl.

Syntaxegbl <filename> <size_in_bytes>


The name of the file in which the logs are to be captured. The filename must have the extension '.log'.

size_in_bytes


Examples

1. Enable Gb data logging to a file named 'st_gb_logs.log' with a size of 5000 bytes.egbl st_gb_logs.log 5000

Execution printoutsBCSU/0/PCU/0/OSE>egbl st_gb_logs.log 5000 ----------------------------------------------------------------> Command egbl executed on [1/1/2004 0:10:8:10001] <---- ------------------------------------------------------------******************************************************** Enabled GB Service Terminal Logging to a file Filename: /ram/st_gb_logs.log Size: 5000 Please note that every time the file exceeds Size: 5000 file will be wrapped around ********************************************************************** Enabling this command may affect the performance of the System **********************************************************************

!


DN0479352Issue 4-2

111


Id:0900d805806444bc

2.13.6 dgbl (disable Gb data logging)

FunctionThe full form of this command is disable Gb data logging (dgbl).

Syntaxdgbl

Examples

1. Disable the Gb data logging to a file.dgbl

Execution printoutsBCSU/0/PCU/0/OSE/GBL>dgbl ----------------------------------------------------------------> Command dgbl executed on [1/1/2004 0:10:27:950001] <---- ------------------------------------------------------------ ******************************************************** Disabled Service Terminal GB Logging to a file Filename: /ram/st_gb_logs.log Size: 5000 ********************************************************

2.14 Subscriber monitoring–related commandsThis section contains the commands for subscriber monitoring.

2.14.1 esm (enable subscriber monitoring)

FunctionWith this command you enable subscriber monitoring (esm). The subscriber monitoring can be enabled only for one IMSI at a time in the system. If another user tries to enable subscriber monitoring for another IMSI, the request will be rejected and appropriate message will be printed.

Syntaxesm <imsi>

Parameter explanationsimsi

This parameter specifies the IMSI to be monitored.

Examples

1. Enable subscriber monitoring for IMSI '1'.esm 1

Execution printoutsBCSU/0/PCU/0/OSE>esm 24405109000004 ----------------------------------------------------------------> Command esm executed on [1/1/2004 0:11:7:870001] <----

112 DN0479352Issue 4-2


Id:0900d805806444bc


------------------------------------------------------------subscriber monitioring enabled for IMSI : 24405109000004

Subscriber monitoring messages will be generated by the applications:

BCSU/0/PCU/0/OSE> [Subscriber Monitoring Trace][1/1/2004 0:20:27:258002]- * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * System level trace report for IMSI : 24405109000004 - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * Segment id : 0 BTS id : 0 TRX id : 0 Location area id : LAC : 0, CI : 0 Routing area id : 0 TBF direction : DOWNLINK TBF allocation time : QOS priority class : 0 Initial number of TCHs : 0 Initial MCS : 0 TBF reallocation observations : - * - * - * - * - * - * - * - * - * - * - Flow control change observations : - * - * - * - * - * - * - * - * - * - * - MCS change observations: - * - * - * - * - * - * - * - * - * - * - PFC change observations : - * - * - * - * - * - * - * - * - * - * - TBF release time : Thu Jan 1 00:20:27 2004 TBF release cause : 0 Amount of LLC data using the last MCS : 10080Number of RLC blocks using the last MCS : 364 Number of mcs changes caused by Abis-bus blockage : 0 - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * BCSU/0/PCU/0/OSE>

2.14.2 dsm (disable subscriber monitoring)

FunctionWith this command you disable subscriber monitoring (dsm).

Syntaxdsm

Examples

1. Disable subscriber monitoring.dsm

Execution printoutsBCSU/0/PCU/0/OSE>dsm ----------------------------------------------------------------> Command dsm executed on [1/1/2004 0:11:7:870001] <----

DN0479352Issue 4-2

113


Id:0900d805806444bc

------------------------------------------------------------subscriber monitioring successfully disabled BCSU/0/PCU/0/OSE>

2.14.3 dism (display subscriber monitoring)

FunctionWith this command you display the IMSI for which the subscriber monitoring (dism) is enabled.

Syntaxdism

Examples

1. Display the subscriber monitoring configuration.dism

Execution printoutsBCSU/0/PCU/0/OSE>dism ----------------------------------------------------------------> Command dism executed on [1/1/2004 0:11:7:870001] <---- ------------------------------------------------------------Currently monitored IMSI : 24405109000004 BCSU/0/PCU/0/OSE>

2.14.4 esml (enable subscriber monitoring data logging)

FunctionWith this command you log the output of all the subscriber monitoring messages. The full form of this command is enable subscriber monitoring data logging (esml). This command can be typically used when you need to capture the output into a file for offline analysis.

Syntaxesml <filename> <size_in_bytes>


The name of the file in which the logs are to be captured. The filename must have an extension '.log'.

size_in_bytes

The maximum size of the file. In case the logs exceed the maximum file size, the log capture mode is automatically turned off, and no more logging is done.

!


114 DN0479352Issue 4-2


Id:0900d805806444bc


Examples

1. Enable subscriber monitoring data logging to a file named 'st_sm_logs.log' with size of 5000 bytes.esml st_sm_logs.log 5000

Execution printoutsBCSU/0/PCU/0/OSE>esml st_sm_logs.log 5000 ----------------------------------------------------------------> Command esml executed on [1/1/2004 0:0:28:965001] <---- ------------------------------------------------------------ ******************************************************** Enabled SM Service Terminal Logging to a file Filename: /ram/st_sm_logs.log Size: 5000 Please note that every time the file exceeds Size: 5000 bytes file will be wrapped around **********************************************************************Enabling this command may affect the performance of the System **********************************************************************

2.14.5 dsml (disable subscriber monitoring data logging)

FunctionThe full form of this command is disable subscriber monitoring data logging (dsml).

Syntaxdsml

Examples

1. Disable the subscriber monitoring data logging to a file.dsml

Execution printoutsBCSU/0/PCU/0/OSE/SML>dsml ----------------------------------------------------------------> Command dsml executed on [1/1/2004 0:0:52:309001] <---- ------------------------------------------------------------ ******************************************************** Disabled Service Terminal Subscriber Logging to a file Filename: /ram/st_sm_logs.log Size: 5000 ********************************************************

2.15 User plane monitoring–related commandsThis section contains the commands for user plane monitoring.

DN0479352Issue 4-2

115


Id:0900d805806444bc

2.15.1 eup (enable user plane monitoring)

FunctionWith this command you enable user plane monitoring (eup).

Syntaxeup <imsi>

Parameter explanationsimsi

This parameter specifies the IMSI to be monitored.

Examples

1. Enable user plane monitoring for IMSI '1'.eup 1

Execution printoutsUser plane message output description:

BCSU/0/PCU/0/OSE/UPL>eup 24405109000004 ----------------------------------------------------------------> Command eup executed on [1/1/2004 0:7:53:180001] <---- ------------------------------------------------------------UserPlane monitoring Enabled for IMSI: 24405109000004 BCSU/0/PCU/0/OSE/UPL>

User plane traces messages will be generated by the applications:

[UserPlane Monitoring Trace for IMSI:24405109000004 ][1/1/2004 0:15:44:0]User Plane Monitoring : Application -> DLPFD, Direction ->Downlink

-------- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- ---------------- 00000000 00 00 00 00 C0 E5 7F 81 E0 F0 B2 66 03 C2 D4 80 ...........f....

Parameter Description

IMSI:013 Indicates that this trace has been raised for IMSI of value '013', meaning that the length is 3 octets. If the display had been IMSI:123456, the length of the IMSI would have been 6 octets.

dtt.c The filename from which the log message was gener-ated.

66 The line number of the file from which the log message was generated.

5 The application ID of the application which raised the log.

1/1/2004 The date stamp when the log was raised in dd/mm/yyyy format.

0:0:26:0 The time stamp when the log was raised in hr:min:sec:micro-seconds format.

47 Indicates that this is a user plane monitoring trace.

DSP:USER Plane Monitoring Test Message The trace message, raised by the application.

116 DN0479352Issue 4-2


Id:0900d805806444bc


00000010 D4 D4 D4 D4 D4 D4 D4 D4 D4 D4 D4 D4 D4 D4 FF D4 ................ 00000020 FF FF FF FF FF FF FF FF ........ -------- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- ----------------

[UserPlane Monitoring Trace for IMSI:24405109000004 ][1/1/2004 0:15:47:0] User Plane Monitoring : Application -> ULPFD, Direction ->Uplink

-------- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- ---------------- 00000000 00 00 00 23 A7 FD FC 2C 0C 00 01 02 01 04 03 06 ...#...,........ 00000010 05 08 07 0A 09 0C 0B 0E 0D 10 0F 12 11 14 13 16 ................ 00000020 15 18 17 1A 19 1C 1B FB ........ -------- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- ----------------

2.15.2 dup (disable user plane monitoring)

FunctionWith this command you disable user plane monitoring (dup).

Syntaxdup

Examples

1. Disable user plane monitoring.dup

Execution printoutsBCSU/0/PCU/0/OSE/UPL>dup ----------------------------------------------------------------> Command dup executed on [1/1/2004 0:7:53:180001] <---- ------------------------------------------------------------MS is not active User Plane Monitoring is disabled BCSU/0/PCU/0/OSE/UPL>

2.15.3 diup (display user plane monitoring)

FunctionWith this command you display the IMSI for which the user plane monitoring (diup) is enabled.

Syntaxdiup

Examples

1. Display the user plane monitoring configuration.diup

Execution printoutsBCSU/0/PCU/0/OSE/UPL>diup ----------------------------------------------------------------> Command diup executed on [1/1/2004 0:7:53:180001] <----

DN0479352Issue 4-2

117


Id:0900d805806444bc

------------------------------------------------------------User Plane Monitoring is enabled for IMSI 24405109000004 BCSU/0/PCU/0/OSE/UPL>

2.15.4 eupl (enable user plane data logging)

FunctionWith this command you log the output of all the user plane messages. The full form of this command is enable user plane data logging (eupl). This command can be typically used in scenarios where you need to capture the output into a file for offline analysis.

Syntaxeupl <filename> <size_in_bytes>


The name of the file in which the logs are to be captured. The filename must have an extension '.log'.

size_in_bytes


Examples

1. Enable user plane data logging to a file named 'st_up_logs.log' with size of 5000 bytes.eupl st_up_logs.log 5000

Execution printoutsBCSU/0/PCU/0/OSE>eupl st_up_logs.log 5000 ----------------------------------------------------------------> Command eupl executed on [1/1/2004 0:11:48:430001] <---- ------------------------------------------------------------ ******************************************************** Enabled UP Service Terminal Logging to a file Filename: /ram/st_up_logs.log Size: 5000 Please note that every time the file exceeds Size: 5000 bytes file will be wrapped around **********************************************************************Enabling this command may affect the performance of the System **********************************************************************

!


118 DN0479352Issue 4-2


Id:0900d805806444bc


2.15.5 dupl (disable user plane data logging)

FunctionThe full form of this command is disable user plane data logging (dupl).

Syntaxdupl

Examples

1. Disable user plane logging to a file.dupl

Execution printoutsBCSU/0/PCU/0/OSE/UPL>dupl ----------------------------------------------------------------> Command dupl executed on [1/1/2004 0:12:7:100001] <---- ------------------------------------------------------------ ******************************************************** Disabled Service Terminal UP Logging to a file Filename: /ram/st_up_logs.log Size: 5000 ********************************************************

2.16 Frame relay–related commandsThis section contains the commands for frame relay.

2.16.1 dfc (display frame relay configuration)

FunctionWith this command you display frame relay configuration (dfc).

Syntaxdfc {<bearer_id>} {<dlci>}

Parameter explanationsbearer_id

This parameter specifies the bearer for which the frame relay configuration is to be dis-played.

dlci

This parameter specifies the dlci ID of the bearer for which the frame relay configuration is to be displayed.

Examples

1. Display the frame relay configuration for all the bearers.dfc

2. Display the frame relay configuration for bearer '2.dfc 2

DN0479352Issue 4-2

119


Id:0900d805806444bc

3. Display the frame relay configuration for bearer '2 and dlci ID '17.dfc 2 17

Execution printoutsBCSU/0/PCU/0/OSE>dfc ----------------------------------------------------------------> Command dfc executed on [1/1/2004 0:5:20:478330] <---- ------------------------------------------------------------ Bearer Data for Link Id: 0 Link Type = 0 Liv Selector = 2 First TSL = 0 Link Rate = 15 N391 Threshold = 6 N392 Threshold = 3 N393 Threshold = 4 T391 Timer = 10 Protocol State = IDLE Operational Status = LINK UP PVC Data for Link Id: 0

DLCI = 16 PVC STATUS = PVC UP

Bearer Data for Link Id: 2 Link Type = 0 Liv Selector = 2 First TSL = 15 Link Rate = 15 N391 Threshold = 6 N392 Threshold = 3 N393 Threshold = 4 T391 Timer = 10 Protocol State = IDLE Operational Status = LINK UP PVC Data for Link Id: 2 DLCI = 17 PVC STATUS = PVC UP

BCSU/0/PCU/0/OSE>dfc 2 ----------------------------------------------------------------> Command dfc executed on [1/1/2004 0:5:25:321528] <---- ------------------------------------------------------------ Bearer Data for Link Id: 2 Link Type = 0 Liv Selector = 2 First TSL = 15 Link Rate = 15 N391 Threshold = 6 N392 Threshold = 3 N393 Threshold = 4 T391 Timer = 10 Protocol State = IDLE Operational Status = LINK UP PVC Data for Link Id: 2 DLCI = 17 PVC STATUS = PVC UP BCSU/0/PCU/0/OSE>dfc 2 17 ------------------------------------------------------------

120 DN0479352Issue 4-2


Id:0900d805806444bc


----> Command dfc executed on [1/1/2004 0:5:28:941518] <---- ------------------------------------------------------------ Bearer Data for Link Id: 2 Link Type = 0 Liv Selector = 2 First TSL = 15 Link Rate = 15 N391 Threshold = 6 N392 Threshold = 3 N393 Threshold = 4 T391 Timer = 10 Protocol State = IDLE Operational Status = LINK UP PVC Data for Link Id: 2 DLCI = 17 PVC STATUS = PVC UP BCSU/0/PCU/0/OSE>

2.17 General category commands

2.17.1 dpt (display system level trace pending table)

FunctionWith this command you display system level trace pending table (dpt).

Syntaxdpt

Examples

1. Display the system level trace pending table.dpt

Execution printoutsBCSU/0/PCU/0/OSE>dpt ----------------------------------------------------------------> Command dpt executed on [1/1/2004 0:12:29:540001] <---- ------------------------------------------------------------System level trace pending table contents --------------------------------------------------------------------------------------------------

IMSI Trace reference State --------------------------------------------------------------------------------------------------

24405109000004 ----- PENDING --------------------------------------------------------------------------------------------------

BCSU/0/PCU/0/OSE>

2.18 Telnet server administration commandsThis section describes the service terminal commands used to enable/disable Telnet connectivity.

DN0479352Issue 4-2

121


Id:0900d805806444bc

2.18.1 etc (enable telnet for specified IP address or for all IPs)

FunctionWith this command you enable Telnet for a specified IP address or for all IPs.

Syntaxetc <"all"|ipv4_address>

Parameter explanationsip address

This parameter specifies the IP address for which Telnet services are to be enabled in the PCU2. The allowed values are 'all' or any IPv4 address.

In PCU reset the values revert to default values.

Examples

1. Enable Telnet for a specified IP address.etc 192.168.0.11

2. Enable Telnet for all IPs.etc all

Execution printoutsBCSU/0/PCU/0/OSE>etc 192.168.0.11 ----------------------------------------------------------------> Command etc executed on [1/1/2004 0:21:42:106002] <---- ------------------------------------------------------------BCSU/0/PCU/0/OSE>

BCSU/0/PCU/0/OSE>etc all ----------------------------------------------------------------> Command etc executed on [1/1/2004 0:20:8:684001] <---- ------------------------------------------------------------ All blocked telnet IP lists would be deleted Are you sure (y/n) : y BCSU/0/PCU/0/OSE>

2.18.2 dtc (disable telnet for specified IP address or for all IPs)

FunctionWith this command you disable Telnet for a specified IP address or for all IPs.

Syntaxdtc <"all"|ipv4_address>

Parameter explanationsip address

This parameter specifies the IP address for which Telnet services are to be enabled in the PCU2. The allowed values are 'all' or any IPv4 address.

In PCU reset the values revert to default values.

122 DN0479352Issue 4-2


Id:0900d805806444bc


Examples

1. Disable Telnet for a specified IP address. dtc 192.168.0.11

2. Disable Telnet for all IPs.dtc all

Execution printoutsBCSU/0/PCU/0/OSE>dtc 192.168.0.11 ----------------------------------------------------------------> Command etc executed on [1/1/2004 0:28:49:110001] <---- ------------------------------------------------------------BCSU/0/PCU/0/OSE>

BCSU/0/PCU/0/OSE>dtc all ----------------------------------------------------------------> Command etc executed on [1/1/2004 0:29:7:425001] <---- ------------------------------------------------------------ All allowed telnet IP lists would be deleted Are you sure (y/n) : y BCSU/0/PCU/0/OSE>

2.18.3 tcstatus (display list of authenticated IP for telnet connections)

FunctionWith this command you display the list of authenticated IPs for Telnet connections.

Syntaxtcstatus

Examples

1. Display list of authenticated IPs for Telnet connections.tcstatus

Execution printoutsBCSU/0/PCU/0/OSE>tcstatus ----------------------------------------------------------------> Command tcstatus executed on [1/1/2004 0:31:55:421001] <---- ------------------------------------------------------------Telnet allowed from all IP addresses

BCSU/0/PCU/0/OSE> BCSU/0/PCU/0/OSE>tcstatus ----------------------------------------------------------------> Command tcstatus executed on [1/1/2004 0:32:18:3002] <---- ------------------------------------------------------------Telnet blocked from all IP addresses

BCSU/0/PCU/0/OSE> BCSU/0/PCU/0/OSE>tcstatus ------------------------------------------------------------

DN0479352Issue 4-2

123


Id:0900d805806444bc

----> Command tcstatus executed on [1/1/2004 0:33:39:3002] <---- ------------------------------------------------------------Telnet allowed from only following IP addresses

192.168.0.11

BCSU/0/PCU/0/OSE>

2.19 NCCR commands

2.19.1 dnc0ms (display number of mobile stations in NC0 mode)

FunctionWith this command you display the number of mobile stations in NC0 mode in the system.

Syntaxdnc0ms

Examples

1. Display the number of mobile stations in NC0 mode.dnc0ms

Execution printoutsBCSU/0/PCU/0/OSE>dnc0ms ----------------------------------------------------------------> Command dnc0ms executed on [1/1/2004 0:1:10:251001] <---- ------------------------------------------------------------************************ Start of Trace ************************ NC0 Transfer mode MS : 0 NC0 Idle mode MS : 9 ************************* End of Trace *************************

2.19.2 dnc2ms (display the number of mobile stations in NC2 mode)

FunctionWith this command you display the number of mobile stations in NC2 mode in the system.

Syntaxdnc2ms

Examples

1. Display the number of mobile stations in NC2 mode.dnc2ms

Execution printoutsBCSU/0/PCU/0/OSE>dnc2ms ------------------------------------------------------------

124 DN0479352Issue 4-2


Id:0900d805806444bc


----> Command dnc2ms executed on [1/1/2004 0:10:22:65001] <- ------------------------------------------------------------************************ Start of Trace ************************ NC2 Idle mode MS : 0 NC2 Transfer mode MS : 1 ************************* End of Trace *************************

2.19.3 dnccrms (display the NCCR data of mobile stations specified)

FunctionWith this command you display the NCCR data of mobile stations specified by a tempo-rary logical link identity (TLLI), segment ID, or MS ID.

Syntaxdnccrms <-t> <TLLI> <segment ID> dnccrms <-m> <MS ID>

Parameter explanations-t or -m

This parameter specifies the parameter type: -t for TLLI and segment ID, -m for MS ID.

TLLI, segment ID, MS ID

This parameter specifies the TLLI, segment ID, or MS ID for which NCCR data of mobile stations will be displayed.

Examples

1. Display the NCCR data of mobile stations with TLLI ’4294967040’ and segment ID ’10’.dnccrms -t 4294967040 10

2. Display the NCCR data of mobile stations with MS ID '1000'.dnccrms -m 1000

Execution printoutsBCSU/0/PCU/0/OSE>dnccrms -t 4294967040 10 ----------------------------------------------------------------> Command dnccrms executed on [1/1/2004 0:4:46:946001] <---- ------------------------------------------------------------************************ Start of Trace ************************ TLLI : 0xffffff00 Segment_id : 10 Serving Cell Data : BTS ID : 2 Serving Cell LAC : 0 Serving Cell CI : 0 TRX Id : 2 BLER UL N.A. DL N.A. Bitrate per radioblock UL N.A. kbit/s DL N.A. kbit/s Serving Cell RXLEV : 5 GSM neighbour cell data : ID LAC CI RX level 12 63 0 3

WCDMA neighbour cell data : RNC ID CI CPICH Ec/NoNO 3G MEASUREMENTS RECEIVED FOR THIS MS

DN0479352Issue 4-2

125


Id:0900d805806444bc

************************* End of Trace *************************

2.20 NACC commands

2.20.1 dnacc (display the NACC related neighbour cell configuration data)

FunctionWith this command you display the NACC-related neighbour cell configuration data of a user-given segment.

Syntaxdnacc <segment ID>

Parameter explanationssegment ID

This parameter specifies the segment ID for which the NACC-related neighbour cell configuration data will be displayed.

Examples

1. Display the NACC-related neighbour cell configuration data of segment '69'.dnacc 69

Execution printouts BCSU/30/PCU/4/OSE>dnacc 69 ----------------------------------------------------------------> Command dnacc executed on [9/6/2005 12:49:35:196927] <---- ------------------------------------------------------------************************ Start of Trace ************************ ADJACENT CELLS OF SEGMENT 69 SEG_ID LAC CI ARFCN BSIC 72 8738 2072 124 0 ************************* End of Trace *************************BCSU/30/PCU/4/OSE>

2.20.2 dpsinacc (display the neighbour cell SI or PSI messages)

FunctionWith this command you display the neighbour cell SI or PSI messages of a given segment.

Syntaxdpsinacc <segment ID>


This parameter specifies the segment ID for which PSI messages will be displayed.

126 DN0479352Issue 4-2


Id:0900d805806444bc


Examples

1. Display the PSI messages of segment '69'.dpsinacc 69

Execution printoutsBCSU/30/PCU/4/OSE>dpsinacc 69 ----------------------------------------------------------------> Command dpsinacc executed on [9/6/2005 12:51:18:524904] <---- ------------------------------------------------------------************************ Start of Trace ************************ SI/PSI MESSAGES OF SEGMENT 69 TYPE (INST) LENGTH MESSAGE DATA SI1 21 19 8f 1d 8 0 0 0 0 0 0 0 0 0 0 0 0 0 9d 0 0 2b SI3 21 1b 8 15 32 f4 51 22 22 c9 2 5 64 40 5 9d 0 0 1c 13 2b 2b SI13 21 0 80 0 f8 8 7c c9 32 a6 14 25 a4 db 2b 2b 2b 2b 2b 2b 2b 0 ************************* End of Trace *************************BCSU/30/PCU/4/OSE>

2.20.3 dsinacc (display the SI messages of given segment)

FunctionWith this command you display the SI messages of a given segment stored into the PCU. With this data the PCU responds to the PACKET SI STATUS messages sent by MSS.

Syntaxdsinacc <segment ID> eg: dsinacc 1


This parameter specifies the segment ID for which SI messages will be displayed.

Examples

1. Display the SI messages of segment '69'.dsinacc 69

Execution printoutsBCSU/30/PCU/4/OSE>dsinacc 69 ----------------------------------------------------------------> Command dsinacc executed on [9/6/2005 12:52:56:782996] <---- ------------------------------------------------------------************************ Start of Trace ************************ SI/PSI MESSAGES OF SEGMENT 69 TYPE (INST) LENGTH MESSAGE DATA SI1 21 19 8f 1d 8 0 0 0 0 0 0 0 0 0 0 0 0 0 9d 0 0 2b SI2 21 1a 9f 1d 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 9d 0 0 SI2B 0 SI 2T(0) 17 3 38 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 SI 2T(1) 0 SI 2T(2) 0 SI 2T(3) 0 SI 2T(4) 0 SI 2T(5) 0 SI 2T(6) 0 SI 2T(7) 0 SI 2Q(0) 21 7 c0 1c 8 4c 14 fa 18 3f b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b SI 2Q(1) 0

DN0479352Issue 4-2

127


Id:0900d805806444bc

SI 2Q(2) 0 SI 2Q(3) 0 SI 2Q(4) 0 SI 2Q(5) 0 SI 2Q(6) 0 SI 2Q(7) 0 SI 2Q(8) 0 SI 2Q(9) 0 SI 2Q(10) 0 SI 2Q(11) 0 SI 2Q(12) 0 SI 2Q(13) 0 SI 2Q(14) 0 SI 2Q(15) 0 SI3 21 1b 8 15 32 f4 51 22 22 c9 2 5 64 40 5 9d 0 0 1c 13 2b 2b SI4 21 1c 32 f4 51 22 22 40 5 9d 0 0 1 2b 2b 2b 2b 2b 2b 2b 2b 0 SI13 21 0 80 0 f8 8 7c c9 32 a6 14 25 a4 db 2b 2b 2b 2b 2b 2b 2b 0 BCSU/30/PCU/4/OSE>

2.21 Gb over IP commands

2.21.1 dgbipbvc (display the information about certain BVC)

FunctionWith this command you display the information about a certain BSSGP virtual connec-tion (BVC).

Syntaxdgbipbvc <BVCI>

Parameter explanationsBVCI

This parameter specifies the BSSGP virtual connection identifier (BVCI) for which the Gb information will be displayed.

Examples

1. Display the information about BVCI '10010'.dgbipbvc 10010

Execution printoutsBCSU/0/PCU/0/OSE> dgbipbvc 10010 ----------------------------------------------------------------> Command dgbipbvc executed on [1/1/2004 0:19:2:919001] <---- ------------------------------------------------------------ Segment ID::10 BVC ID::10010 NSEI::10 BVC State::WORKING

BCSU/0/PCU/0/OSE>

128 DN0479352Issue 4-2


Id:0900d805806444bc


2.21.2 dgbipnsei (display the information about certain NSE)

FunctionWith this command you display the information about a certain network service entity (NSE).

Syntaxdgbipnsei <BVCI> <NSEI>

Parameter explanationsBVCI

This parameter specifies the BVCI for which Gb information will be displayed.

NSEI

This parameter specifies the network service entity identifier (NSEI) for which Gb infor-mation will be displayed.

Examples

1. Display the information about BVCI '10010' and NSEI '10'.dgbipnsei 10010 10

Execution printoutsBCSU/0/PCU/0/OSE> dgbipnsei 10010 10 ----------------------------------------------------------------> Command dgbipnsei executed on [1/1/2004 0:22:16:109001] <---- ------------------------------------------------------------Segment ID::10 BVC ID::10010 NSEI::10 BVC State::WORKING

BCSU/0/PCU/0/OSE>

2.21.3 dgbipnsvc (display the information about certain NSVC)

FunctionWith this command you display the information about a certain network service virtual connection (NSVC).

Syntaxdgbipnsvc <NSEI>

Parameter explanationsNSEI

This parameter specifies the NSEI for which Gb information will be displayed.

Examples

1. Display the information about NSEI '10'.dgbipnsvc 10

DN0479352Issue 4-2

129


Id:0900d805806444bc

Execution printoutsBCSU/0/PCU/0/OSE> dgbipnsvc 10 ----------------------------------------------------------------> Command dgbipnsvc executed on [1/1/2004 0:28:32:284001] <---- ------------------------------------------------------------NSVC ID::10 NSEI::10 NSVC State::WORKING Local UDP Port::5566 Remote Address Type::IP Remote Address IP version::IPv4 Remote IP Address::10.3.3.136 Remote UDP Port::5567 Remote Data Weight::1 Remote Signaling Weight::1 Preconf SGSN IP Endpoint::STATIC

BCSU/0/PCU/0/OSE>

2.22 DTM commandsThese commands are used to display and delete information stored in the dedicated dual transfer mode (DTM) IMSI database. For commands didtms and ddtmimsi, the IMSI ID needs to be specified. The IMSI ID is a 15 digit number.

2.22.1 ddimsi (display dedicated IMSI)

FunctionWith this command you display a specified DTM IMSI entry stored in the IMSI table. The command can also be used to display the complete DTM IMSI entry table. Before printing all IMSI entries, you will be prompted.

Syntaxddimsi <imsi | “all”>

Examples

1. Display all dedicated IMSI entries.ddimsi all

Execution printoutsBCSU/31/PCU/3/OSE>ddimsi all ----------------------------------------------------------------> Command ddimsi executed on [30/11/2005 17:33:29:826875] <---- ------------------------------------------------------------ All Dedicated IMSI Enteries will be Printed Are you sure (y/n) : y

---------------------------------------------------- Number of IMSI Enteries = [0x1] Displaying Contents of ALL IMSI Enteries Starts:

130 DN0479352Issue 4-2


Id:0900d805806444bc


------------------------------------------------ Dedicated IMSI Entry Table : ------------------------------------------------ Dedicated IMSI Entry Table Ptr [0x7521648] : IMSI ID : 987651561155865 Dedicated IMSI Ctx Ptr [0x7ce6db8] : Dedicated TLLI Ctx Ptr [0x0] : DTM MS Ctx Ptr [0x0] :

------------------------------------------------ Dedicated IMSI Context Fields Table Starts : ------------------------------------------------ ABIPRB address : [0x455b] Alloc Req Rxd : [NO] ReAlloc Req Rxd : [NO] NO DTM CS TSL Available NO OLD DTM CS TSL Available Dedicated IMSI Call Context Fields : FLAGS : MO Ongoing = [IMSGW_FALSE] MT Ongoing = [IMSGW_FALSE] DTM Release Cause = [IMSGW_PDM_DTM_RELEASE_CAUSE_NOT_RELEVANT] DX/PCU Initiated Release = [NO_DTM_RELEASE_INITATED] DTM IMSI Cause = [IMSGW_PDM_DTM_IMSI_ENTRY_IND] DTM IMSI Exit Indication Rxd = [IMSGW_FALSE] DTM IMSI Abort Indication Rxd = [IMSGW_FALSE] DTM CS Release Request Rxd = [IMSGW_FALSE] DTM Connect Back to PS Usage = [IMSGW_FALSE] DTM Establishment Cause = [DTM_ESTAB_CAUSE_INVALID] DTM Release Ongoing = [IMSGW_FALSE] ------------------------------------------------Dedicated IMSI Context Fields Table Ends : ------------------------------------------------No DTM MS TLLI Context Exists : DTM MS TLLI Context Field Ends: ------------------------------------------------Number of Dedicated IMSI Entries Printed [0x1] Displayed ALL IMSI Enteries SUCCESSFULLY ------------------------------------------------ ----------------------------------------------------All Dedicated IMSI Enteries Printed BCSU/31/PCU/3/OSE>

2.22.2 didtms (display internal DTM counters)

FunctionWith this command you display the internal counters for a specified DTM IMSI. The command displays two internal counters: DTM IMSI COORDINATION MESSAGES and DTM IMSI SEARCH OPERATIONS.

Syntaxdidtms <imsi>

DN0479352Issue 4-2

131


Id:0900d805806444bc

Examples

1. Display the internal counters for a DTM IMSI.didtms 987651561155865

Execution printoutsBCSU/31/PCU/3/OSE>didtms 987651561155865 ----------------------------------------------------------------> Command didtms executed on [30/11/2005 17:35:25:754975] <---- ---------------------------------------------------------------------------------------------------------------- DISPLAYING INTERNAL COUNTERS OF DTM Total Number of IMSI Coordination Messages: 0 Total Number of IMSI Search Op: 116 ---------------------------------------------------- DTM Internal Counters Displayed BCSU/31/PCU/3/OSE>

2.22.3 ddtmimsi (delete DTM IMSI)

FunctionWith this command you delete a specific DTM IMSI entry stored in the IMSI table.

Syntaxddtmimsi <imsi>

Examples

1. Delete dedicated IMSI entry.ddtmimsi 987651561155865

Execution printoutsBCSU/31/PCU/3/OSE>ddtmimsi 987651561155865 ----------------------------------------------------------------> Command ddtmimsi executed on [30/11/2005 18:54:23:490892] <---- ---------------------------------------------------------------------------------------------------------------- ----------------------------------------------------DTM Dedicated IMSI Entry Deleted BCSU/31/PCU/3/OSE>

2.23 Service terminal commands for DSP and PCM allocation information

2.23.1 ddspinfo (display DSP information)

FunctionWith this command you display DSP information.

132 DN0479352Issue 4-2


Id:0900d805806444bc


Syntaxddspinfo <dsp_id>

Parameter explanationsdsp_id

This parameter specifies the DSP ID for which the information will be displayed. The value range is from 0 to 7.

Examples

1. Display DSP information.ddspinfo

2. Display the information for DSP '2'ddspinfo 2


BCSU/0/PCU/0/OSE> ddspinfo ddspinfo DSP DAP1(EDAP1) DAP2(EDAP2) EGPRS GPRS STATE SLAVE(UL/DL) 0 2(0)* 65535(255) 7 0 1 0/3 1 2(0)* 65535(255) 0 0 1 0/0 2 2(0)* 65535(255) 0 0 1 0/0 3 2(0) 65535(255) 0 0 1 0/0 4 2(0) 65535(255) 0 0 1 0/0 5 2(0) 65535(255) 0 0 1 0/0 6 2(0) 65535(255) 0 0 1 0/0 7 2(0) 65535(255) 0 0 1 0/0

Where DSP state, 0 - DSP_UNKNOWN 1 - DSP_READY 2 - DSP_FAILEDWhere * denotes DSP is DLDC preferred for this DAP


BCSU/0/PCU/0/OSE> ddspinfo 2 DSP DAP1(EDAP1) DAP2(EDAP2) EGPRS GPRS STATE SLAVE(UL/DL) 2 2(0)* 65535(255) 0 0 1 0/0

Where DSP state, 0 - DSP_UNKNOWN 1 - DSP_READY 2 - DSP_FAILED Where * denotes DSP is DLDC preferred for this DAPBCSU/0/PCU/0/OSE>

2.23.2 dpcminfo (display PCU-PCM information)

FunctionWith this command you display PCU-PCM information. If the PCU-PCM line number is not specified, the information for all configured PCU-PCM lines will be displayed.

DN0479352Issue 4-2

133


Id:0900d805806444bc

Syntaxdpcminfo <pcm_line_no>

Parameter explanationspcm_line_no

This parameter specifies the PCM line number for which the information will be dis-played. The value range is from 0 to 1.

Examples

1. Display the information for PCU-PCM line number 1.dpcminfo 1

Execution printoutsBCSU/0/PCU/0/OSE> BCSU/30/PCU/3/OSE>dpcminfo 1 ----------------------------------------------------------------> Command dpcminfo executed on [30/11/2005 18:53:21:710875] <---- ------------------------------------------------------------ PCU_PCM 1 TSL 0123 DAP/DSP 0 0000 255/15 1 0000 255/15 2 0000 255/15 3 0000 255/15 4 0000 255/15 5 0000 255/15 6 0000 255/15 7 0000 255/15 8 0000 255/15 9 0000 255/15 10 0000 255/15 11 0000 255/15 12 0000 255/15 13 0000 255/15 14 0000 255/15 15 0000 255/15 16 0000 255/15 17 0000 255/15 18 0000 255/15 19 0000 255/15 20 0000 255/15 21 0000 255/15 22 0000 255/15 23 0000 255/15 24 0000 255/15 25 0000 255/15 26 0000 255/15 27 0000 255/15 28 8444 0/0 29 4444 0/15 30 4444 0/15 31 4444 0/15

Where TSL state, 0 - CH_UNKNOWN 1 - CH_GPRS 2 - CH_PCCCH 3 - CH_EGPRS_MASTER 4 - CH_EDAP 5 - CH_UNDER_TEST 6 - CH_RES_MASTER 7 - CH_RESERVED_UL 8 - CH_RES_DL 9 - CH_FAILEDBCSU/0/PCU/0/OSE>

134 DN0479352Issue 4-2


Id:0900d805806444bc


2.23.3 dpcmdapinfo (display PCU-PCM information for the specified EDAP)

FunctionWith this command you display the PCU-PCM information for a specified EGPRS dynamic Abis pool (EDAP).

Syntaxdpcmdapinfo <dap_id>

Parameter explanationsdap_id

This parameter specifies the EDAP ID for which the PCU-PCM information will be dis-played. The value range is from 1 to 470.

Examples

1. Display the PCU-PCM information for EDAP '2'dpcmdapinfo 2

Execution printoutsBCSU/30/PCU/3/OSE>dpcmdapinfo 2 ----------------------------------------------------------------> Command dpcmdapinfo executed on [30/11/2005 18:53:21:710875] <---------------------------------------------------------------- PCU_PCM 1 TSL 0123 EDAP/DSP 28 8444 0/0 29 4444 0/15 30 4444 0/15 31 4444 0/15

Where TSL state, 0 - CH_UNKNOWN 1 - CH_GPRS 2 - CH_PCCCH 3 - CH_EGPRS_MASTER 4 - CH_EDAP 5 - CH_UNDER_TEST 6 - CH_RES_MASTER 7 - CH_RESERVED_UL 8 - CH_RES_DL 9 - CH_FAILED BCSU/30/PCU/3/OSE>

2.23.4 ddapinfo (display EDAP information)

FunctionWith this command you display EDAP information.

Syntaxddapinfo <dap_id>


This parameter specifies the EDAP ID for which the information will be displayed. The value range is from 1 to 470.

Examples

1. Display the information for EDAP '2'ddapinfo 2

DN0479352Issue 4-2

135


Id:0900d805806444bc

Execution printoutsBCSU/30/PCU/3/OSE>ddapinfo 2 ----------------------------------------------------------------> Command ddapinfo executed on [30/11/2005 18:53:21:710875] <---- ------------------------------------------------------------DAP ET_PCM PCU_PCM STATE EDAP_IX DSP(s) 2 17-21 1,28-32 3 0 0 1 2 3 4 5 6 7

Where EDAP state: 0 - ST_EDAP_NOT_DEFINED 1 - ST_EDAP_WTF_EDAP_INFO 2 - ST_EDAP_WTF_DSP_ACK 3 - ST_EDAP_READY 4 - ST_EDAP_FAILED 5 - ST_EDAP_WTF_RECONF 6 - ST_EDAP_IN_CONFLICT 7 - ST_EDAP_FAIL_IN_LOOP_TEST

BCSU/30/PCU/3/OSE>

2.23.5 dabmtrxinfo (display the TRX information for the BTS in the speci-fied segment)

FunctionWith this command you display the TRX information for the BTS in the specified segment.

Syntaxdabmtrxinfo <seg_id> <bts_id> <trx_id>

Parameter explanationsseg_id

This parameter specifies the SEG ID for which the information will be displayed. The value range is from 1 to 660.

bts_id

This parameter specifies the BTS ID for which the information will be displayed. The value range is from 1 to 660.

trx_id

This parameter specifies the TRX ID for which the information will be displayed. The value range is from 1 to 16.

Examples

1. Display the information for SEG '257' and BTS '257'dabmtrxinfo 257 257

Execution printoutsBCSU/30/PCU/3/OSE>dabmtrxinfo 257 257 ----------------------------------------------------------------> Command dabmtrxinfo executed on [30/11/2005 18:53:21:710875] <---------------------------------------------------------------- SEG 257 BTS 257 TRX 7 EDGE-TRX=NO DAP=2 PCU_TRX_ID=0

136 DN0479352Issue 4-2


Id:0900d805806444bc


RTSL PCU_PCM TSL subTSL DSP STATE 0 - - - - - 1 0 1 2 0 3 2 0 1 1 0 3 3 0 1 0 0 3 4 0 0 3 0 3 5 0 0 2 0 3 6 0 0 1 0 3 7 0 0 0 0 3

Where RTSL state:0 - CH_NOT_USED 1 - CH_RC0_CONNECTIN 2 - CH_DSP_CONNECTING 3 - CH_CONNECTED 4 - CH_DSP_DISCONNECTING 5 - CH_RC0_DISCONNECTING 6 - CH_REALLOC_CONNECT 7 - CH_REALLOC_RELEASE 8 - CH_FAILED

BCSU/30/PCU/3/OSE>

2.23.6 ddaptrxinfo (display TRX information for the specified DAP)

FunctionWith this command you display the TRX information for the specified DAP.

Syntaxddaptrxinfo <dap_id>



Examples

1. Display the TRX information for EDAP '2'.

Execution printoutsBCSU/30/PCU/3/OSE>ddaptrxinfo 2 ----------------------------------------------------------------> Command ddaptrxinfo executed on [30/11/2005 18:53:21:710875] <---------------------------------------------------------------- SEG 257 BTS 257 TRX 7 EDGE-TRX=NO DAP=2 PCU_TRX_ID=0

RTSL PCU_PCM TSL subTSL DSP STATE 0 - - - - - 1 0 1 2 0 3 2 0 1 1 0 3 3 0 1 0 0 3 4 0 0 3 0 3 5 0 0 2 0 3

DN0479352Issue 4-2

137


Id:0900d805806444bc

6 0 0 1 0 3 7 0 0 0 0 3

Where RTSL state:0 - CH_NOT_USED 1 - CH_RC0_CONNECTIN 2 - CH_DSP_CONNECTING 3 - CH_CONNECTED 4 - CH_DSP_DISCONNECTING 5 - CH_RC0_DISCONNECTING 6 - CH_REALLOC_CONNECT 7 - CH_REALLOC_RELEASE 8 - CH_FAILED

BCSU/30/PCU/3/OSE>

2.23.7 dstslinfo (display sub-TSL info for the PCU-PCM line)

FunctionWith this command you display the sub-timeslot information for the PCU-PCM line.

Syntaxdstslinfo <pcm_line_no> <tsl_ix> <stsl_ix>

Parameter explanationspcm_line_no

This parameter specifies the PCM line number for which the information will be dis-played. The value range is from 0 to 1.

tsl_ix

This parameter specifies the timeslot index for which the information will be displayed. The value range is from 0 to 31.

stsl_ix

This parameter specifies the sub-timeslot index for which the information will be dis-played. The value range is from 0 to 3.

Examples

1. Display the information for PCU-PCM line number 0 and timeslot number .0.dstslinfo 0 0

Execution printoutsBCSU/30/PCU/3/OSE>dstslinfo 0 0 ----------------------------------------------------------------> Command dstslinfo executed on [21/12/2005 9:7:18:508951] <---- ------------------------------------------------------------ PCM: 0 TSL:0 subTSL TYPE TRX_ID(PCU_TRX_IX) RTSL 0 3 1(0) 7 1 3 1(0) 6 2 3 1(0) 5 3 0 - -

Where TSL state:

138 DN0479352Issue 4-2


Id:0900d805806444bc


0 - CH_UNKNOWN 1 - CH_GPRS 2 - CH_PCCCH 3 - CH_EGPRS_MASTER 4 - CH_EDAP 5 - CH_UNDER_TEST 6 - CH_RES_MASTER 7 - CH_RESERVED_UL 8 - CH_RES_DL 9 - CH_FAILED BCSU/30/PCU/3/OSE>

2.23.8 dgpinfo (display guard period information per DAP)

FunctionWith this command you display the Guard Period information per dynamic Abis pool (DAP).

Syntaxdgpinfo <dap_id>



Examples

1. Display Guard Period information.dgpinfo

2. Display Guard Period information for DAP '40'.dgpinfo 40


BCSU/30/PCU/3/OSE>dgpinfo ----------------------------------------------------------------> Command dgpinfo executed on [21/12/2005 9:13:12:612893] <---- ------------------------------------------------------------ PCU_PCM 0 (DL GP/UL GP) PCU_PCM 1 (DL GP/UL GP) TSL Sub0 Sub1 Sub2 Sub3 TSL Sub0 Sub1 Sub2 Sub3 0 -/- -/- -/- -/- 0 -/- -/- -/- -/- 1 -/- -/- -/- -/- 1 -/- -/- -/- -/- 2 -/- -/- -/- -/- 2 -/- -/- -/- -/- 3 -/- -/- -/- -/- 3 -/- -/- -/- -/- 4 -/- -/- -/- -/- 4 -/- -/- -/- -/- 5 -/- -/- -/- -/- 5 -/- -/- -/- -/- 6 -/- -/- -/- -/- 6 -/- -/- -/- -/- 7 -/- -/- -/- -/- 7 -/- -/- -/- -/- 8 -/- -/- -/- -/- 8 -/- -/- -/- -/- 9 -/- -/- -/- -/- 9 -/- -/- -/- -/- 10 -/- -/- -/- -/- 10 -/- -/- -/- -/- 11 -/- -/- -/- -/- 11 -/- -/- -/- -/- 12 -/- -/- -/- -/- 12 -/- -/- -/- -/- 13 -/- -/- -/- -/- 13 -/- -/- -/- -/-

DN0479352Issue 4-2

139


Id:0900d805806444bc

14 -/- -/- -/- -/- 14 -/- -/- -/- -/- 15 -/- -/- -/- -/- 15 -/- -/- -/- -/- 16 -/- -/- -/- -/- 16 -/- -/- -/- -/- 17 -/- -/- -/- -/- 17 -/- -/- -/- -/- 18 -/- -/- -/- -/- 18 -/- -/- -/- -/- 19 -/- -/- -/- -/- 19 -/- -/- -/- -/- 20 -/- -/- -/- -/- 20 -/- -/- -/- -/- 21 -/- -/- -/- -/- 21 -/- -/- -/- -/- 22 -/- -/- -/- -/- 22 -/- -/- -/- -/- 23 -/- -/- -/- -/- 23 -/- -/- -/- -/- 24 -/- -/- -/- -/- 24 -/- -/- -/- -/- 25 -/- -/- -/- -/- 25 -/- -/- -/- -/- 26 -/- -/- -/- -/- 26 -/- -/- -/- -/- 27 -/- -/- -/- -/- 27 -/- -/- -/- -/- 28 -/- -/- -/- -/- 28 -/- -/- -/- -/- 29 -/- -/- -/- -/- 29 -/- -/- -/- -/- 30 -/- -/- -/- -/- 30 -/- -/- -/- -/- 31 -/- -/- -/- -/- 31 0/0 0/0 0/0 0/0BCSU/30/PCU/3/OSE>


BCSU/30/PCU/3/OSE>dgpinfo 40 ----------------------------------------------------------------> Command dgpinfo executed on [21/12/2005 9:15:19:198901] <---- ------------------------------------------------------------ PCU_PCM 1 (DL GP/ UL GP) DAP 40 EDAP 0

TSL Sub0 Sub1 Sub2 Sub3 31 0/0 0/0 0/0 0/0

BCSU/30/PCU/3/OSE>

2.24 Cell monitoring commands

2.24.1 dcem (display cell monitoring data)

FunctionWith this command you display the information about cell monitoring data.

Syntaxdcem -g <SEG_ID> Display info of all MS of all TSL of all TRX of all BTS of a particular Segment dcem -b <BTS_ID> Display info of all MS of all TSL of all TRX of a particular BTS dcem -t <TBF_ID> Display info of a particular TBF ID dcem -i <SEG_ID> <TLLI> Display info of a particular TLLI

140 DN0479352Issue 4-2


Id:0900d805806444bc


dcem -x <BTS_ID> <TRX_ID> Display info of all MS on all TSL of a particular TRX dcem -s <BTS_ID> <TRX_ID> <TSL> Display info of all MS on particular TSL of a TRX dcem -f <BTS_ID> <TRX_ID> <TSL> <TFI> Display info of a particular TFI on a TSL of a TRX

Parameter explanationsSEG_ID

This parameter specifies the segment ID for which the cell monitoring data will be dis-played.

BTS_ID

This parameter specifies the BTS ID for which the cell monitoring data will be displayed.

TRX_ID

This parameter specifies the TRX ID for which the cell monitoring data will be displayed.

TLLI

This parameter specifies the temporary logical link identity (TLLI) for which the cell mon-itoring data will be displayed.

TSL

This parameter specifies the TSL for which the cell monitoring data will be displayed.

TFI

This parameter specifies the temporary flow identity (TFI) for which the cell monitoring data will be displayed.

Examples

1. Display the cell monitoring data for TBF ID =8dcem -t 8

Execution printoutsBCSU/35/PCU/4/OSE>dcem -t 8----------------------------------------------------------------> Command dcem executed on [22/11/2008 16:39:50:471007] <----------------------------------------------------------------

**************************START OF TRACE**************************** TBF ID: 8


Num_of_PSW_TSLs:4 TSL_4:DEDICATED TSL_5:DEDICATED TSL_6:DEDICATED

DN0479352Issue 4-2

141


Id:0900d805806444bc

TSL_7:DEDICATEDEDAP id : 300Ext PCM Line of the SMCH : 8112Ext PCM TSL (64 K) of the SMCH : 10Ext PCM STSL (16 K) of the SMCH : 2BTS id of SMCH: 300TRX id of SMCH: 1RTSL of SMCH : 5

BTS ID : 300 [0x12c] TRX ID : 1 [0x1] DSP ID : 0 MULTISLOT CLASS : 33 Direction : UPLINK RLC MODE TBF : ACK TSL NUM Allocated : 6 7 USF : 127 127 127 127 127 127 5 4 TBF STATE : PDM_ULTBF_NORMAL_REL_IN_PROGRESS TBF ID : 8 [0x8] TFI : 10 [0xa] Coding Scheme : MCS9 TBF Data rate : 10.08 KB per sec Direction : DOWNLINK RLC MODE TBF : ACK TSL NUM Allocated : 4 5 6 7 TBF STATE : PDM_DLTBF_ACTIVE TBF ID : 0 [0x0] TFI : 28 [0x1c] Coding Scheme : MCS3 TBF Data rate : 10.73 KB per sec TLLI : 3221225480 [0xc0000008] MS_INDEX : 0x012cc0000008 IMSI : 244051090001003 TYPE : EGPRS NC Mode MS : 0 TSL_4 : DOWNLINK TSL_5 : DOWNLINK TSL_6 : CONCURRENT TSL_7 : CONCURRENT PFI : 0 PFC ID DL : 34026289 [0x2073331] Guranteed Data Rate DL : 0 RLC MODE PFC : ACK Traffic Class : BEST_EFFORT ARP : ARP3 PFI : 0 PFC ID UL : 34026288 [0x2073330] Guranteed Data Rate UL : 0 RLC MODE PFC : ACK Traffic Class : BEST_EFFORT

142 DN0479352Issue 4-2


Id:0900d805806444bc


ARP : ARP2


BCSU/35/PCU/4/OSE>

2.25 Service terminal command–related information

2.25.1 Commands in continuous modeSome service terminal commands can be run in continuous mode. Running can be invoked by enabling/disabling continuous mode. For example:

ecm <refresh time in seconds>

After this mode is set, the commands listed below will run every 'timeperiod' seconds, giving you a continuous update on the list of running processes and their status.

The commands that can be run in continuous mode are:

• dbu • dbp • dbs • dtu • dtp • dsca • dsco • daa • deqs • dsegtbf • dtrxtbf

2.25.2 Bootup phases and tracesWhen the service terminal boots up, traces are displayed on the serial interface to inform you of what phase is currently in progress in the system.

The traces that are displayed for PCU2-D/U are:

============================================================Welcome to the PQII Boot Loader.============================================================

IMSGW Boot image version : '6.33-0' built on Aug 21 2006

DN0479352Issue 4-2

143


Id:0900d805806444bc


Memory Test : PASSED

Watchdog Test : PASSED

Serial Diagnostics test result : PASSED

Ethernet Diagnostics test result - Interface 1 : PASSED

Ethernet Diagnostics test result - Interface 2 : PASSEDSDL BOOTLOADER: Reset Reason HARD RESETSDL BOOTLOADER: Downloading image For Section 0...SDL BOOTLOADER: WAITING...SDL BOOTLOADER: Loading .....................SDL BOOTLOADER: PQ2 Image Loading Completed. Size = <0xa341b0>SDL BOOTLOADER: Transfering control to image entry point at 0x01e00004


OSE Started.

PQII Data-Cache test result : PASSEDHDLC Diagnostics test results - Interface 1 : PASSED


IMSGW Platform Version : '11.11-0' built on Feb 04 2009 21:17:03last line: <-34509834>last file: <FDF16BF5>IMSGW_CM: Executing the Entry Point function OF CMPCI: Sending Host Intr StartingPIU index=0x6, PIU type=0x3d9, Phy add=0x32, Broadcast=0x7f Log PIU Index= 0x7IMSGW_CM:System Services, PCI and Component Framework Started Process LOGGER CreatedProcess DSPM CreatedProcess DSPMRX CreatedProcess IPC_MR CreatedProcess ARS CreatedProcess SYSMON CreatedProcess SDL CreatedProcess STA CreatedProcess st_dmx_dd0 CreatedProcess st_dmx_dd1 CreatedProcess DSPRM CreatedProcess DIAGONOSTICS CreatedProcess PCU_AGNT CreatedProcess CPUMON CreatedProcess SERIAL_DSPM Created

144 DN0479352Issue 4-2


Id:0900d805806444bc


Process IDRS CreatedProcess IBNACC CreatedProcess IPMR CreatedIMSGW_CM:Component Manager started Stage 1 Applications

Component Manager(RESTART State) : Received WORKING state from BSC Process PMS-PQII CreatedProcess ABM CreatedProcess PDM CreatedProcess MAC CreatedProcess PFM CreatedProcess PCM CreatedProcess BGP CreatedProcess NS CreatedProcess FR CreatedProcess RL CreatedProcess PSW CreatedIMSGW_CM:Component Manager started Stage 2 Applications

FR has sent FTN_INIT_REQ_S message to BSC

RELAY has sent NSOM_GB_INT_RESTART_IND_S message to BSC











DN0479352Issue 4-2

145


Id:0900d805806444bc








146 DN0479352Issue 4-2


Id:0900d805806444bc














DN0479352Issue 4-2

147


Id:0900d805806444bc




The traces that are displayed for PCU2-E are:

============================================================Welcome to the PQIII Boot Loader.============================================================

IMSGW Boot image version : '1.13-0' built on Dec 19 2008


Memory Test : PASSED

SDL BOOTLOADER: Reset Reason HARD RESETSDL BOOTLOADER: Downloading image For Section 0...SDL BOOTLOADER: WAITING...

SDL Handshake failed.Type 'bist' within next 10 seconds to transfer control to BIST image.

10 seconds remaining 9 seconds remaining 8 seconds remaining 7 seconds remaining 6 seconds remaining 5 seconds remaining 4 seconds remaining 3 seconds remaining 2 seconds remaining 1 seconds remaining 0 seconds remaining

Booting continued.SDL BOOTLOADER: Initial Response from PILOAD Recvd...SDL BOOTLOADER: Loading ........................SDL BOOTLOADER: PQ3 Image Loading Completed. Size = <0x00B80FB4>SDL BOOTLOADER: Transferring control to image entry point at 0x10000000


OSE Started.

HDLC Diagnostics test results - Interface 1 : PASSED

148 DN0479352Issue 4-2


Id:0900d805806444bc



IMSGW Platform Version : 'R4E-DLDC-01-E0.1P20' built on Feb 4 2009 21:16:30last line: <0>last file: <0>IMSGW_CM: Executing the Entry Point function OF CMPCI: pci_wait_host_ack status WAITING_1PCI: pci_wait_host_ack status WAITING_1PCI: pci_wait_host_ack status WAITING_1PCI: pci_wait_host_ack status WAITING_1PCI: Sending Host Intr StartingPIU index=0x4, PIU type=0x3e3, Phy add=0x32, Broadcast=0x7f Log PIU Index= 0x5IMSGW_CM:System Services, PCI and Component Framework Started Process LOGGER CreatedProcess DSPM CreatedProcess DSPMRX CreatedProcess IPC_MR CreatedProcess ARS CreatedProcess SYSMON CreatedProcess SDL CreatedProcess STA CreatedProcess st_dmx_dd0 CreatedProcess st_dmx_dd1 CreatedProcess DSPRM CreatedProcess DIAGONOSTICS CreatedProcess PCU_AGNT CreatedProcess CPUMON CreatedProcess IDRS CreatedProcess IBNACC CreatedProcess IPMR CreatedIMSGW_CM:Component Manager started Stage 1 Applications

Component Manager(RESTART State) : Received WORKING state from BSC Process PMS-PQII CreatedProcess ABM CreatedProcess PDM CreatedProcess MAC CreatedProcess PFM CreatedProcess PCM CreatedProcess BGP CreatedProcess NS CreatedProcess FR CreatedProcess RL CreatedProcess PSW CreatedIMSGW_CM:Component Manager started Stage 2 Applications

FR has sent FTN_INIT_REQ_S message to BSCIMSGW_CM: Time Received from BSC - Mon Feb 9 09:58:17 2009

RELAY has sent NSOM_GB_INT_RESTART_IND_S message to BSC

DN0479352Issue 4-2

149


Id:0900d805806444bc













150 DN0479352Issue 4-2


Id:0900d805806444bc













DN0479352Issue 4-2

151


Id:0900d805806444bc


2.25.3 Application IDs for commands

Application name Application ID

Common applications for PQII and DSP:

Component manager 1

IPC Message Router 2

PMS 3

Applications on PQII:

Software Download 4

Logger 5

Alarms 6

DSPM 7

System Monitoring 8

Diagnostics 9

DSPRM 10

Service Terminal Agent 11

ABM 16

PDM 17

PSW 18

MAC 19

PFM 20

PCM 21

BGP 22

NS 23

FR 24

RL 25

PCU Agent 28

CPU Monitoring process 29

IDRS 31

IPMR 12

Dynamic application ID begin for PQII 34

Dynamic application ID end for PQII 46

Applications on DSP:

QC 4

DTT 5

DSPA 6

152 DN0479352Issue 4-2


Id:0900d805806444bc


2.25.4 Error code debugging information for abb and doe command outputThe reboot reason can have the following values in the black box:

If the header in the black box displays the kernel cause, it needs to be interpreted by the scheme below.

ABIS 7

ABIS_RX_0 8

ABIS_RX_1 9

ABIS_TX_0 10

ABIS_TX_1 11

DSP Interrupt Processes:

DSPAISR 12

ABIS_DMA_CH0_DROP_OS_ISR 13




ABIS_TX_OS_ISR_0 17

ABIS_TX_OS_ISR_1 18

ABIS_RX_OS_ISR_0 19

ABIS_RX_OS_ISR_1 20

DSP_BERR_OS_ISR 21

MCSERIAL 22

Dynamic application ID begin for DSP 23

Dynamic application ID end for DSP 32

Application name Application ID

Value Parameter Description

0 CM_INVALID_REASON An invalid or an unknown reason.

1 CM_SSF_INIT_FAILURE SSF failed to initialise.

2 CM_PROCESS_STARTUP_FAILURE

A process failed to start.

3 CM_PROCESS_RUNTIME_FAILURE

A process crashed.

4 CM_NORMAL_SHUTDOWN Normal shutdown initiated by user.

5 CM_WDOG_TIMER_START_FAILED

Watchdog timer starting failed.

6 CM_ST_SOFTWARE_UPGRADE Software upgrade done and system rebooted.

7 CM_BB_NEW_FILE Black box new file created.

8 CM_KRN_ERR_HANDL_CALLED Kernel error handler called.

DN0479352Issue 4-2

153


Id:0900d805806444bc

The format of these error codes is specific to each OSE implementation. The error handler receives three parameters:

An error may be either fatal or non–fatal.

A fatal error causes the OSE system to shut down, regardless of any action taken by an error handler. Fatal errors include all situations where kernel data has been damaged. In these cases, only the kernel error handler is called, and interrupts are disabled before the call is made. In these cases, the error handler is responsible for restarting the system. If the error handler returns, the kernel enters an infinite loop, which can be exited only by a hardware reset.

A non-fatal error is called a warning. A warning causes the OSE system to shut down, unless an error handler resolves the error situation. If no error handler resolves the sit-uation, the kernel enters an infinite loop. A system error handler may elect to restart the system instead of returning to the kernel. Warnings include situations where data areas in user space have been damaged, where a memory pool has been exhausted, or where an illegal parameter has been passed to a system call. Many warnings are fatal for all processes in the involved address space, since a damaged data area can never be guaranteed not to affect other unprotected memory.

Each error code contains three fields:

• A 16-bit main error code. Defined by the constants below. • A 15-bit subcode. The least significant 8 bits are mostly used to indicate which

system call was in progress. • A 1-bit fatal flag. Set for a fatal error, cleared for a warning.

Figure 2 Error code decoding

The 32-bit error parameter passed to an error handler is organised as follows:

The following masks are used to extract the various error parameter fields.


user_called The value is zero for all system errors.

ecode Contains the error code.

extra Contains various error-dependent information.

D31 D30-D16 D0-D15

FatalFlag

Subcode or Zeroif not present

Main ErrorCode

D15...D0 A main error code.

D30...D16 A subcode or zero if not present.

D31 A fatal flag. Set if a fatal error has occurred.


ERROR_MASK 0x0000ffff

154 DN0479352Issue 4-2


Id:0900d805806444bc


2.26 Error codes interpretation in case 'user_called' is 'false' (value 0)Constants are used to find out which system call was in progress when an error was encountered. Use SUBCODE_MASK to extract this field. The field is zero if the current system call is irrelevant.

SUBCODE_MASK 0x7fff0000

FATAL_MASK 0x80000000


System call name Error code

OSE_ADDRESSEE (0x010000)

OSE_ALLOC (0x020000)

OSE_ASSIGN_LINKHANDLER (0x030000)

OSE_ATTACH (0x040000)

OSE_ATTACH_SEGMENT (0x050000)

OSE_CLEAR_BP (0x060000)

OSE_CREATE_BLOCK (0x070000)

OSE_CREATE_ERROR_HANDLER (0x080000)

OSE_CREATE_POOL (0x090000)

OSE_CREATE_PROCESS (0x0a0000)

OSE_CREATE_SEM (0x0b0000)

OSE_CURRENT_PROCESS (0x0c0000)

OSE_DELAY (0x0d0000)

OSE_DETACH (0x0e0000)

OSE_ERROR (0x0f0000)

OSE_FLUSH (0x100000)

OSE_FREE_BUF (0x110000)

OSE_GET_BID (0x120000)

OSE_GET_BID_LIST (0x130000)

OSE_GET_CPU (0x140000)

OSE_GET_ENV (0x150000)

OSE_GET_ENV_LIST (0x160000)

OSE_GET_FSEM (0x170000)

OSE_GET_MEM (0x180000)

OSE_GET_PCB (0x190000)

OSE_GET_PID_LIST (0x1a0000)

OSE_GET_PRI (0x1b0000)

OSE_GET_PTYPE (0x1c0000)

DN0479352Issue 4-2

155


Id:0900d805806444bc

OSE_GET_SEM (0x1d0000)

OSE_GET_SIGNAL (0x1e0000)

OSE_GET_SYSTIME (0x1f0000)

OSE_GET_TICKS (0x200000)

OSE_GET_UID (0x210000)

OSE_HUNT (0x220000)

OSE_HUNT_FROM (0x230000)

OSE_INTERCEPT (0x240000)

OSE_KILL_PROC (0x250000)

OSE_KILL_SEM (0x260000)

OSE_POWER_FAIL (0x270000)

OSE_RECEIVE (0x280000)

OSE_RECEIVE_FROM (0x290000)

OSE_RECEIVE_W_TMO (0x2a0000)

OSE_RESTORE (0x2b0000)

OSE_RESUME (0x2c0000)

OSE_SEND (0x2d0000)

OSE_SENDER (0x2e0000)

OSE_SEND_W_S (0x2f0000)

OSE_SET_BP (0x300000)

OSE_SET_ENV (0x310000)

OSE_SET_FSEM (0x320000)

OSE_SET_MEM (0x330000)

OSE_SET_PCB (0x340000)

OSE_SET_PRI (0x350000)

OSE_SET_SEGMENT (0x360000)

OSE_SIGSIZE (0x370000)

OSE_SIGNAL_FSEM (0x380000)

OSE_SIGNAL_SEM (0x390000)

OSE_START (0x3a0000)

OSE_START_OSE (0x3b0000)

OSE_STOP (0x3c0000)

OSE_SYSTEM_TICK (0x3d0000)

OSE_TICK (0x3e0000)

OSE_WAIT_FSEM (0x3f0000)

OSE_WAIT_SEM (0x400000)

OSE_WAKE_UP (0x410000)

OSE_EXTEND_POOL (0x420000)


156 DN0479352Issue 4-2


Id:0900d805806444bc


Constants are used to find out which error occurred. Use ERROR_MASK to extract this field.

Error code description when 'user_called' is 'False' ( value '0').

OSE_RECEIVE_WITH (0x430000)

OSE_SET_PRI_FOR (0x440000)

OSE_REQUEST_TMO_SIG (0x450000)

OSE_REQUEST_TMO (0x460000)

OSE_CANCEL_TMO_SIG (0x470000)

OSE_CANCEL_TMO (0x480000)

OSE_RESTART_TMO (0x490000)

OSE_RECEIVE_SPORT (0x4a0000)

OSE_SET_REDIRECTION (0x4b0000)

OSE_GET_STK_POOLID (0x4c0000)

OSE_GET_SIG_POOLID (0x4d0000)


Error code name Value Description

OSE_ENO_KERN_SPACE 0x12 The kernel pool is out of space. An error handler may extend the pool with the extend_pool() system call. The extra parameter contains a pool identifier that can be passed to the extend_pool() system call. The extra parameter serves no other purpose. This error code can be ignored only if the pool was extended. Ignoring the error causes the current allocation to be retried. Note that the error handler is called in a state where the dispatcher is locked. The error handler is there-fore not allowed to perform any operations or system calls that would cause a process switch to be attempted. As a special case, it is, however, possible to use the signal_fsem() and signal_sem() calls in this situation. Furthermore, if the pool serves interrupt or timer processes, the error handler is assumed to disable interrupts before calling extend_pool() and restoring the previous interrupt status upon return.

DN0479352Issue 4-2

157


Id:0900d805806444bc

OSE_ENO_USER_SIGSPACE 0x20 The user signal pool is out of space. An error handler may extend the pool with the extend_pool() system call. The extra parameter contains a pool identifier that can be passed to the extend_pool() system call. The extra parameter serves no other purpose. This error code can be ignored only if the pool was extended. Ignoring the error causes the current allocation to be retried. Note that the error handler is called in a state where the dispatcher is locked. The error handler is there-fore not allowed to perform any operations or system calls that would cause a process switch to be attempted. As a special case, it is, however, possible to use the kill_proc(), signal_fsem() and signal_sem() calls in this situation. Furthermore, if the pool serves interrupt or timer processes, the error handler is assumed to disable interrupts before calling extend_pool() and restoring the previous interrupt status upon return.

OSE_ENO_USER_STACKSPACE 0x02 The user stack pool is out of space. An error handler may extend the pool with the extend_pool() system call. The extra parameter contains a pool identifier that can be passed to the extend_pool() system call. The extra parameter serves no other purpose. This error code can be ignored only if the pool was extended. Ignoring the error causes the current allocation to be retried. Note that the error handler is called in a state where the dispatcher is locked. The error handler is there-fore not allowed to perform any operations or system calls that would cause a process switch to be attempted. As a special case, it is, however, possible to use the kill_proc(), signal_fsem() and signal_sem() calls in this situation. Furthermore, if the pool serves interrupt or timer processes, the error handler is assumed to disable interrupts before calling extend_pool() and restoring the previous interrupt status upon return.


158 DN0479352Issue 4-2


Id:0900d805806444bc


OSE_EPOOL_EXTENSION_FAILED

0x21 Pool extension failed. An error handler repeatedly claims that an out-of-space error was handled, but the kernel cannot find the extended space. It is possible that the error handler never used the extend_pool() system call. The extra parameter contains the initial error code: OSE_ENO_KERN_SPACE, OSE_ENO_USER_SIGSPACE or OSE_ENO_USER_STACKSPACE. This error is fatal when it occurs in an interrupt process. If it is not, the error handler is expected to kill the current process. For errors in the kernel pool, the recover procedure may not be straightforward, so it is recommended that the system is shut down or restarted by the system error handler.

OSE_EBUFFER_TOO_LARGE 0x11 Too large signal buffer requested. It is impossible to allocate a buffer larger than the largest size avail-able in the pool. The extra parame-ter contains the size requested. Ignoring this error causes the kernel to allocate the largest buffer avail-able in the pool. This error is fatal if it occurs when the kernel tries to allocate system pool space as a side effect of system calls, for example, create_block() and create_process().

OSE_ESTACK_TOO_LARGE 0x01 Too large stack buffer requested. There is no stack of this size or larger in the pool attached to process that called create_process. The extra parameter contains the size requested.

OSE_EBLOCK_HAS_PROCESSES

0x22 The create_pool system call was used on a block that contains pro-cesses.

OSE_EILLEGAL_PROCESS_ID 0x32 An illegal block or process ID was presented to the kernel. This code may also indicate a bad process ID in a redirection table. The extra parameter contains the offending ID. Ignoring this error causes the system call to treat the ID as the ID of a killed process.


DN0479352Issue 4-2

159


Id:0900d805806444bc

OSE_EUSED_NIL_POINTER 0x31 The caller tried to operate on the NIL pointer. The buffer has probably already been sent or freed. The extra parameter contains the address of the signal pointer that points to NIL. Ignoring this error causes the illegal system call to be ignored.

OSE_ENOT_SIG_OWNER 0x5f The calling process is not the owner of the specified signal buffer. This error may sometimes also occur for a wild signal pointer. The extra parameter contains the address of the signal buffer. Ignoring this error causes the illegal system call to be ignored.

OSE_ECANNOT_RESTORE 0x57 Restore was attempted on a signal buffer that has already been freed or is otherwise not owned by any process. Such buffers cannot be restored. This error may also occur for a wild signal pointer or for a buffer located in a memory segment protected from the caller. The extra parameter contains the address of the signal buffer.

OSE_ENO_BUFFER_END_MARK 0xa5 A valid end mark could not be found in the signal buffer presented to the kernel. The calling process seems to have been writing more data than the size of the buffer allows. The extra parameter contains the address of the signal buffer. This error must be handled in a system error handler by killing the current process/program. The error cannot be ignored, and attempting to ignore it will only cause the error to be reported again with the fatal flag set.


160 DN0479352Issue 4-2


Id:0900d805806444bc


OSE_EUNREASONABLE_SIZES 0x23 The create_pool system call was exposed to an illegal signal size table or stack size table. This error code is used in any of the following illegal cases:

1. The count field in the first location is unreasonable. Valid counts are 0-8, but both tables cannot have a count of zero.

2. The supplied memory fragment does not fit in the address space.

3. The size table is not properly sorted on size.

4. All sizes in a table are zero.

Ignoring this error causes the system call to return as if it was never called.

OSE_ETOO_MANY_PROCESSES

0x03 Too many processes were created. The system tables allows only a certain number of processes. This number was exceeded. As the process table is used to store any object that is represented by a PROCESS ID, this error may also be reported when creating new blocks, pools, or segments. Ignoring this error causes the system call to return as if it was never called.

OSE_ETOO_MANY_ATTACHED 0x24 Too many signals were attached. The system tables allows only a certain number of attached signals. This number was exceeded.

OSE_ECORRUPTED_KERNEL 0x4a Kernel data was damaged. The kernel tables were found to be inconsistent. The kernel data may have been damaged by a crashed process. The extra parameter contains an undocumented subcode.

OSE_EVECTOR_IN_USE 0x25 Vector already in use. An interrupt process was created for a vector that is already allocated to another interrupt process. The extra param-eter contains the vector. Ignoring this error causes the interrupt process to be removed from the system as if it was never created.

OSE_EILLEGAL_SYSTEMCALL 0x26 Illegal system call from an interrupt process. The current interrupt or timer process has been using a system call that is only allowed for non interrupt processes.


DN0479352Issue 4-2

161


Id:0900d805806444bc

OSE_EINTERSEGMENT_SEND 0x27 Illegal intersegment send to an interrupt or timer process. Signals can be sent to interrupt or timer pro-cesses only if the pool associated with the target process is in the same memory segment as the pool associated with the sending process. This restriction is present because an interrupt process cannot handle the page fault that might occur when a reference to the senders memory segment is made at the time of the receive call in the interrupt process.

OSE_EBAD_INTLEVEL 0x28 Illegal wake-up priority for an inter-rupt process. The current interrupt process was invoked with a hardware priority that does not match the priority stated when the interrupt process was created. The priority parameter in the create_process call must match the actual hardware priority at which the interrupt occurs. The extra parameter to the error handler contains the actual priority encoun-tered. Ignoring this error causes the process priority to be updated.

OSE_ERECURSIVE_ERROR 0x29 An error was encountered while an error handler was executing. The situation was detected in an error system call made by the current process. The extra parameter to the error handler contains the error code supplied in the error system call. This error must be handled in a system error handler by killing the current process/program. The error cannot be ignored, and attempting to ignore it will only cause the error to be reported again with the fatal flag set.


162 DN0479352Issue 4-2


Id:0900d805806444bc


OSE_ERECURSIVE_SYSERROR 0x2a An error was encountered while an error handler was executing. The situation was detected when an error detected by OSE was about to be reported. The extra parameter to the error handler contains the error code that was about to be reported by OSE when the recursive error call was detected. This error must be handled in a system error handler by killing the current pro-cess/program. The error cannot be ignored, and attempting to ignore it will only cause the error to be reported again with the fatal flag set.

OSE_EILLEGAL_SEM_VALUE 0x2b A semaphore with a negative initial value was found or created. This is an illegal situation, since a negative semaphore value implies that one or more processes are waiting at the semaphore. The extra parame-ter contains the illegal initial value. Ignoring this error causes the semaphore to be created with an initial value set to zero.

OSE_EILLEGAL_SEMAPHORE 0x1f An illegal semaphore pointer was presented to the kernel. This error also occurs when a semaphore that is not available to the calling process is killed. A semaphore in another memory segment is unavailable in some memory con-figurations. Ignoring this error causes the system call to return as if it was never called.

OSE_EKILLED_STATIC_SEMAPHORE

0x1D An attempt to kill a static sema-phore was made. Only semaphores created with the create_sem system call can be killed.

OSE_EKILLED_SEMAPHORE_IN_USE

0x1E An attempt to kill a semaphore that is still in use was made. A sema-phore cannot be killed when there are processes waiting for it. The extra parameter contains the identity of the first waiting process. Ignoring this error causes the system call to return as if it was never called.


DN0479352Issue 4-2

163


Id:0900d805806444bc

OSE_EINTERSEGMENT_SEMAPHORE_REF

0x2c A semaphore in use was implicitly killed, but processes are still waiting for it. This error occurs when pro-cesses erroneously use a sema-phore located in another memory segment. This is illegal, but in a system without memory protection, it works up to the point when the memory segment containing the semaphore is reclaimed. This occurs when all processes in that segment have been killed. This error must be handled in a system error handler by killing the offending process. The ID of this process is passed to the error handler in the extra parameter.

OSE_EDETACHED_TWICE 0x2d An attempt to detach from an already detached process was made. Only one detach call may be issued for each attach call made. This error may also occur if detach is called with a bad parameter. The kernel cannot understand the differ-ence in all cases. Ignoring this error causes detach() to perform no oper-ation.

OSE_EDETACHED_TOO_LATE 0x2e An attempt was made to detach from a process long after the death of that process. This error implies that the attached process has been killed, and the caller failed to notice this for a period long enough for the kernel to discard all attach informa-tion for that process. The error can sometimes occur as a result of a too small number of attach entries defined in the kernel configuration. If you encounter this error for no apparent reason, then try increas-ing the attach limit in the configura-tion file. This error may also occur if detach is called with a bad parame-ter. The kernel cannot understand the difference in all cases. Ignoring this error causes the same effect as if detach() was never called, that is, the caller must be prepared for receiving a subsequent attached signal from the killed process.

OSE_EDETACH_AFTER_RECEIVE

0x2f An attempt was made to detach from a process when the attached signal had already been received.

OSE_EBAD_PROCESS_TYPE 0x30 An attempt was made to create a process of an invalid type.


164 DN0479352Issue 4-2


Id:0900d805806444bc


OSE_EILLEGAL_FLUSH_SENDER

0x47 An invalid process ID was encoun-tered in the flush system call. The invalid ID was found in the array specifying from which processes signals should be discarded. This error may also indicate that the first entry of the array contains an invalid array size.

OSE_EKILLED_STATIC_PROCESS

0x48 A static process was killed. Killing a static process is illegal in a system linked to an OSE real-time kernel. The error was reported by the system daemon, which detected the death of the main process in osemain.c. It is unknown at this time which process was originally killed, since all static processes are now dead.

OSE_EILLEGAL_REDIRCOUNT 0x49 An invalid redirection table was pre-sented to the kernel. The number of entries was zero. It must always be at least one, since the first table entry containing the count and the default process ID is included in the counter. Ignoring this error causes the illegal system call to be ignored.

OSE_ECORRUPTED_POOL 0xa6 A damaged signal buffer was pre-sented to the kernel. Analysis indi-cates that the problem was caused by some other buffer in which a process has been writing more data than the size of the buffer allows. The extra parameter contains a pointer to a structure with four 32 bit entries and the following layout:

extra[0] = The process ID of the other process that may have caused the problem. The field may contain the ID of any process including the current. The field is zero if the ID could not be obtained.

extra[1] = A pointer to the name of the other process. The field is zero if the name could not be obtained.

extra[2] = A pointer to the signal buffer that was damaged by the indicated process. This is probably the buffer which was originally damaged.

extra[3] = A pointer to the damaged signal buffer that was presented to the kernel by the calling process. This is probably only a secondary error indication caused by the extra[2] buffer.


DN0479352Issue 4-2

165


Id:0900d805806444bc

OSE_ESPURIOUS_INTERRUPT 0x52 An interrupt occurred from an unused interrupt vector. There may be several possible reasons for this: hardware capable of generating interrupt was erroneously initia-lised, or the system was restarted without issuing a proper hardware reset, or an interrupt process might have been killed without disabling the corresponding hardware. The extra parameter to the error handler contains the priority on which the interrupt was encountered.

OSE_EATTACHED_TO_CALLER 0x53 An attempt was made to attach to the current process. It is illegal to issue an attach call with the ID of the calling process as a parameter.

OSE_EINTERSEGMENT_COPY_FAILED

0x54 The current receive(from/w_tmo) system call failed because the pool attached to the calling process does not support the size of the signal received. Planning pools with regard to the largest available buffer size is an important issue in systems where intersegment memory protection is utilised. It is nearly always advisable to have all pools support the largest signal size of 64k bytes. The extra parameter to the error handler contains the size of the signal buffer found in the receive queue. Ignoring this error causes the received signal to be lost.

OSE_EINTSTACK_TOO_LARGE 0x55 Too large interrupt stack buffer requested. There is no interrupt stack of sufficient size in the system pool. The extra parameter contains the accummulated size. This error does not necessarily mean that a real problem is present, since the interrupt stack size accumulates worst stack case requirements on each interrupt priority over the system life. If the system is designed such that interrupt pro-cesses are frequently created and killed on various interrupt priorities, then a situation may arise where the kernel thinks that the interrupt stack needs to be larger than is actually required by interrupt pro-cesses currently in operation. Ignoring this error causes the inter-rupt stack to be silently truncated to the largest size available.


166 DN0479352Issue 4-2


Id:0900d805806444bc


OSE_EKILLED_SYSTEM_DAEMON

0x56 An attempt was made to kill a system daemon. Killing a member of the OSE block such as 'ose_sysd' or 'idle' is not allowed. The extra parameter to the error handler contains the process ID of the system daemon. Ignoring this error causes the kill_proc call to return without killing the system daemon.

OSE_EFRAGMENT_TOO_SMALL 0x58 An attempt was made to install an unreasonably small pool or pool fragment. Pool fragments smaller than 1024 bytes are rendered useless. This is an arbitrary limit selected because it is believed that fragments this small are always useless. As a general guideline, fragments should be at least several times the size of the largest buffer or stack size. The extra parameter to the error handler contains the size of the supplied pool fragment. Ignoring this error causes the system call to return without creating the pool or install-ing the pool extension, as if the call was never made.

OSE_ECONCURRENT_TICK_CALL

0x59 Tick was called concurrently by several processes. Tick is a non–reentrant system call. Only one process at a time may use it. Other-wise the system will crash. This is a fatal error.

OSE_EILLEGAL_USER_CALL 0x5a A superuser system call was used by a non-superuser process. Some system calls are reserved for use by processes with a user number of zero (the superuser number). Using these calls in other processes is illegal. Ignoring this error causes the illegal system call to be ignored.

OSE_EALREADY_STARTED 0x5b An attempt was made to start a process that is not stopped. The start() system call was invoked with either a process or a block ID. For a block ID, the block was found to contain at least one process that was not stopped. The extra param-eter contains the ID that was passed to the start() call. Ignoring the error causes the start() system call to continue, starting only stopped processes.


DN0479352Issue 4-2

167


Id:0900d805806444bc

OSE_ELINKHANDLER_DEADLOCK

0x5c A linkhandler deadlock was detected. This error was probably caused by a linkhandler process issuing a hunt() system call or another system call that can cause a remote system call request. Doing this is a design rule violation. It is, however, possible that the error was caused during debugging instead, or if the linkhandler was stopped or intercepted for more than 10 seconds. The extra param-eter contains the process ID of the linkhandler that did not respond. Ignoring this error causes the kernel to continue waiting for a response.

OSE_EILLEGAL_ENVNAME 0x5d An illegal environment variable name was detected. A set_env() or get_env() call was issued with a name parameter set to NULL. This was probably caused by a problem related to uninitialised variables. Ignoring this error causes the illegal system call to be ignored.

OSE_EILLEGAL_POOL 0x5e An illegal pool ID was presented to the kernel. The extend_pool() call was issued with a pool_id parame-ter that refers to an object that is not a pool. This was probably caused by a problem related to uninitialised variables. Ignoring this error causes the illegal system call to be ignored.

OSE_EWILD_SIG_POINTER 0x70 An invalid signal pointer was pre-sented to the kernel. The operating system was unable to identify the memory pointed to as a signal buffer. The extra parameter contains the offending pointer, that is the address that should have contained a signal number. Ignoring this error causes the illegal system call to be ignored.

OSE_EBAD_PARAMETER 0x71 An invalid parameter was used in a system call. The operating system checks many of the system call parameters for unreasonable values. This error code means that one of the parameters to the indi-cated system call contained an illegal value. The extra parameter contains the value of the offending parameter. Ignoring this error causes the illegal system call to be ignored.


168 DN0479352Issue 4-2


Id:0900d805806444bc


OSE_EFRAGMENT_IN_USE 0x72 An attempt was made to create a pool with a memory area that is already used in another pool. This error commonly occurs when a block is killed and recreated. The old pool is probably still in use because it contains signals that are currently owned by a process that is still alive. Pools do not die until the last signal in the pool has been freed. This error can also be reported if pool space is allocated on the stack of the caller by mistake. The extra parameter contains the base of the offending pool space. Ignoring this error causes the illegal system call to be ignored.

OSE_EILLEGAL_SUPER_MODE 0x73 An illegal attempt was made to create a supervisor mode block. Supervisor mode blocks can only be created by a superuser process executing in supervisor mode. The extra parameter contains a pointer to the name of the new block. Ignoring this error causes the block to be created anyway, but the mode is set to user mode.

OSE_ESPURIOUS_SYSTEM_SIGNAL

0x74 An unrecognised signal was received by one of the system daemon processes. The extra parameter contains the process ID of the sender of the unknown signal. Ignoring this error causes the signal to be silently freed.

OSE_EFRAGMENT_TOO_LARGE

0x75 An attempt was made to install an unreasonably large pool or pool fragment. The size of the pool fragment presented to the kernel is too large for the fragment to fit in the address space. This error indicates either that the size is unreasonably large, or that the base of the memory fragment is too close to the end of the address space. The extra parameter to the error handler contains the size of the supplied pool fragment. Ignoring this error causes the system call to return without creating the pool or install-ing the pool extension, as if the call was never made.


DN0479352Issue 4-2

169


Id:0900d805806444bc

OSE_ESTOP_OVERFLOW 0x76 An attempt was made to stop a process for an unreasonable number of times. This error occurs when the stop-counter wraps from four giga times to zero. The extra parameter to the error handler contains the ID of the process stopped. Ignoring this error causes the system call to return without executing the stop operation, as if the call was never made.

OSE_ESEM_OVERFLOW 0x77 An attempt was made to signal a semaphore or a fast semaphore beyond the maximum value. Sema-phores can only be signalled a limited number of times before a wait operation is performed. This error occurs when the semaphore value wraps from two giga times to two giga times. The extra parame-ter to the error handler contains the address of the semaphore or the process ID to which the fast sema-phore belongs. Ignoring this error causes the system call to return without executing the semaphore operation, as if the call was never made.

OSE_EBAD_HUNT_PRI 0x78 Bad kernel configuration. The huntd priority is too low. The ose_huntd process must have a priority higher than the ose_sysd process. Ignoring this error causes the prior-ities to be automatically adjusted.

OSE_EILLEGAL_PRISYSTEMCALL

0x79 Illegal system call from an interrupt or background process. The current background, interrupt or timer process has been using a system call that is only allowed for prior-itised processes.

OSE_EILLEGAL_CONFIGURATION

0x7a Illegal kernel configuration. One or more entries in the kernel configu-ration file has an illegal value. The extra parameter to the error handler contains this value. Ignoring this error will cause the kernel to adjust the value to the closest legal value.


170 DN0479352Issue 4-2


Id:0900d805806444bc


OSE_ETOO_MANY_TMO_REQUESTS

0x7b Too many time-out signal requests. Too many concurrently running time-out signal requests have been made. The limit is at least 1000 000, system pool size and CPU power permitting. The extra parameter to the error handler contains the actual limit. This error can only be caught by the kernel error handler. The error cannot be ignored.

OSE_ETMO_ALREADY_CANCELLED

0x7c Time-out signal already cancelled. An attempt has been made to cancel or restart a time-out signal request that was already cancelled. Ignoring this error causes the system call to return without further action.

OSE_ETMO_ALREADY_RECEIVED

0x7d Time-out signal already received. An attempt has been made to cancel or restart a time-out signal request when the signal was already received by the application. This error may also indicate that wrong process tried to cancel or restart the time-out. The extra parameter to the error handler contains the time-out identity returned by the time-out request. Ignoring this error will cause the system call to return without further action.

OSE_EUSER_STACK_OVERFLOW

0x101 User stack exhausted. The extra parameter contains the address to the first byte beyond the stack. This error must be handled by killing the current process/program. The error cannot be ignored, and attempting to ignore it will only cause the error to be reported again with the fatal flag set.

OSE_ESUPERV_STACK_OVERFLOW

0x102 Supervisor stack exhausted. The extra parameter contains the address to the first byte beyond the stack. This is a fatal error.

OSE_EINTERRUPT_STACK_OVERFLOW

0x103 Stack overwrite in an interrupt stack. The extra parameter contains the address to the first byte beyond the stack. This is a fatal error.

OSE_EUNKNOWN_BREAKPOINT

0x104 An unknown breakpoint was encountered. The extra parameter contains the CPU's program counter. This is a fatal error.


DN0479352Issue 4-2

171


Id:0900d805806444bc

OSE_EUNKNOWN_INTERRUPT 0x105 An unknown interrupt was encoun-tered. The extra parameter contains vector number. This is a fatal error.

OSE_EPROCESS_ENDED 0x107 A prioritised or background process ended. The extra parameter contains the process ID. Ignoring this error will cause the process to be killed.

OSE_ESTART_STACK_OVERFLOW

0x108 Kernel start-up stack exhausted. This error is issued when a start handler has used too much stack space. The extra parameter contains the address to the first byte beyond the stack. This is a fatal error.

OSE_EUNRECOGNIZED_CPU 0x109 The CPU model is not recognised. The kernel configuration needs to contain a known CPU model. The extra parameter contains the value configured. This is a fatal error.

OSE_EUNDEFINED_SYSCALL_CODE

0x110 An undefined function code has been used for a system call. The extra parameter contains the function code number. Ignoring this error causes the system call to return with the return value zero.

OSE_EUNEXPECTED_EXCEPTION

0x111 An unexpected exception occurred. The exception offset (or vector offset on some CPUs) is supplied in the subcode field. The extra param-eter contains the CPU's program counter. This is a fatal error.

OSE_EPRIORITY_ERROR 0x112 Interrupt priority error. An interrupt has occurred with equal or less priority than the currently running interrupt process. The reason for this is probably that interrupts have not been masked properly in the interrupt controller. The interrupt controller must not allow an inter-rupt process to be interrupted by an interrupt process with equal or lower priority. The extra parameter contains the illegal priority. This is a fatal error.

OSE_EUNEXPECTED_EXCEPTION_REGDUMP

0x113 An unexpected exception occurred. The exception offset is supplied in the subcode field. The extra param-eter contains a pointer to a register dump, described in cpu.h. This is a fatal error.


172 DN0479352Issue 4-2


Id:0900d805806444bc


2.27 Error codes interpretation in case 'user_called' is 'true' (value 1)Constants are used to obtain which module caused the kernel error handler to be invoked. Use SUBCODE_MASK to extract this field.

Error code description for Program Handler

OSE_EEARLY_ERROR 0x114 An error has been reported before the kernel was operable. A program has called error() or error2() before the kernel start-up was complete. The caller is therefore not an OSE process but a kernel handler, called in the start phase. This is a fatal error. No system calls can be used in the error handler. The extra parameter contains a pointer to a structure with four 32 bit entries and the following layout:

extra[0] = Original error code given in the error() or error2() system call.

extra[1] = Original extra argument to error2(), otherwise zero.

extra[2] = A pointer to the file name of the calling program. The field is zero if the name could not be obtained.

extra[3] = The source line number of the calling program if it could be obtained, otherwise zero.

OSE_ESYSCALL_TOO_EARLY 0x115 A kernel system call was used before the kernel was operable. A program has used a kernel system call before the kernel start up was complete. The caller is therefore not an OSE process but a kernel handler, called in the start phase. This is a fatal error. No system calls can be used in the error handler. The extra parameter contains the return address of the system call. Usually it points into the kernel access library.



OSE_PRH_PLS_EINVALID_SIGNAL

0x500000 PLS received an invalid (unknown) signal. The extra parameter is a pointer to the received signal.

OSE_PRH_PLS_EINTERNAL 0x500001 PLS internal error.

OSE_PRH_PLS_EPROCESS_KILLED

0x500002 PLS process unexpectedly killed.

DN0479352Issue 4-2

173


Id:0900d805806444bc

Error code description for Archive Server

OSE_PRH_PLS_ECREATE_PROCESS

0x500003 Obsolete: PLS process failed when created.

OSE_PRH_PLS_ENO_MMS 0x500004 Obsolete: PLS could not find MMS.

OSE_PRH_PLS_BIOS_INSTALL_FAILED

0x500005 PLS could not install a trap handler.



OSE_PRH_ASF_EINVALID_SIGNAL

0x520000 ASF received an invalid (unknown) signal. The extra parameter is a pointer to the received signal.

OSE_PRH_ASF_EOPEN_DIR_FAILED

0x520100 Could not open a directory. The lower 8 bits are the errno code, and the extra parameter is a pointer to the name of the directory.

OSE_PRH_ASF_EOPEN_FILE_FAILED

0x520200 Could not open a file. The lower 8 bits are the errno code, and the extra parameter is a pointer to the name of the file.

OSE_PRH_ASF_ECREATE_FILE_FAILED

0x520300 Could not create a file. The lower 8 bits are the errno code, and the extra parameter is a pointer to the name of the file.

OSE_PRH_ASF_EREAD_FILE_FAILED

0x520400 File read failed. The lower 8 bits are the errno code, and the extra parameter is a pointer to the name of the file.

OSE_PRH_ASF_EUNLINK_FAILED

0x520500 File unlink (remove) failed. The lower 8 bits are the errno code, and the extra parameter is a pointer to the name of the file.

OSE_PRH_ASF_EWRITE_FILE_FAILED

0x520600 File write failed. The lower 8 bits are the errno code, and the extra parameter is a pointer to the name of the file.

OSE_PRH_ASF_ECLOSE_FILE_FAILED

0x520700 File close failed. The lower 8 bits are the errno code, and the extra parameter is a pointer to the name of the file.

OSE_PRH_ASF_EPROCESS_KILLED

0x520800 An ASF process unexpectedly killed.

OSE_PRH_ASF_EDUPLICATE_LM

0x520900 Local store contains the same load module ID in several files. The extra parameter is a pointer to the dupli-cate load module identity.

OSE_PRH_ASF_ETOO_LONG_FILE_NAME

0x520A00 Obsolete: file names for load modules cannot be longer than 255 characters.

174 DN0479352Issue 4-2


Id:0900d805806444bc


Error code description for MMSThe error reporting mechanism that the MMS uses depends on when the error occurs.

If the error occurs during pre-kernel initialisation, in other words, during the execution of mMSStartHandler1 or any other START_HANDLER1, the user supplied early error handler is called (see EARLY_ERROR_HANDLER in the configuration file mms.con).

If the error occurs after the kernel has initialised, the system call err is used instead. All errors generated by the MMS are application generated (user_called). A few of the errors are non-fatal warnings. The fatal bit conveys this information.

Each MMS error code contains five fields:

• An 8-bit wide main error code. Defined by the constants below. • An 8-bit wide exception code. This part is valid only for some main error codes. • A 14-bit wide subcode. • A 1-bit wide supervisor flag. Set if the error occurred while in supervisor mode,

cleared otherwise. • A 1-bit wide fatal flag. Set for a fatal error, cleared for a warning.

The 32-bit error parameter passed to an error handler is organised as follows:

The following masks are used to extract the various error parameter fields.

OSE_PRH_ASF_EBAD_TFTP_CONFIGURATION

0x520B00 A TFTP archive server is used without or with an incorrect host address or host directory. The extra parameter is a pointer to the last TFTP configuration string. The TFTP configuration syntax is 'host[:port] hostdir' where the host is IP address of the TFTP server, the port is optional, and the hostdir must end with '/' (unix) or '\' (win32). Example: "172.16.232.1:69 ./" or "172.16.232.1 /tftpboot/".


D7...D0 main error code

D15...D8 exception code

D29...D16 subcode

D30 supervisor flag

D31 fatal flag


OSE_MMS_EFATAL_MASK 0x80000000

OSE_MMS_ESUPERVISOR_MASK 0x40000000

OSE_MMS_ESUBCODE_MASK 0x3FFF0000

OSE_MMS_EEXCEPTION_CODE_MASK 0x0000FF00

OSE_MMS_EERROR_MASK 0x000000FF

DN0479352Issue 4-2

175


Id:0900d805806444bc

Supervisory bit:

This bit (bit 30) is set in case of an exception error code to indicate that the processor was in supervisor mode when the fault occurred. Normally the fault is non-fatal to the system if it occurred in user mode. This is because it will be isolated to the scope of that process, in other words, the region of memory in which it is executing. However, if the fault occurred in supervisor mode, the system cannot be guaranteed to be in a consis-tent state, and the fault is fatal to the system. Therefore, the error handler should shut down the system.

Error code descriptions for MMS:


OSE_MMS_SUPERVISOR_MODE 0x40000000

OSE_MMS_USER_MODE 0x00000000


OSE_MMS_EMMU_NOT_SUPPORTED

0x00580000 The MMS does not recognise the version of the MMU, so it cannot perform any mapping. This is a fatal error.

OSE_MMS_ETOO_MANY_DOMAINS

0x00580001 The system limits of the number of local domains, executable areas, or MMS memory areas were exceeded. Shut down the system and decrease the number of items. This is a fatal error.

OSE_MMS_ETOO_MANY_EXEC_AREAS

0x00580002 This is a fatal error.

OSE_MMS_ETOO_MANY_BANKS

0x00580003 This is a fatal error.

OSE_MMS_EOVERLAPPING_DEF

0x00580004 There are overlapping definitions in the static configuration. This is a fatal error.

OSE_MMS_EEND_OF_MEMORY 0x00580005 The memory dedicated as MMS memory is not sufficient. This is a fatal error.

OSE_MMS_EILLEGAL_CONFIGURATION

0x00580006 Illegal configuration. See readme files. This is a fatal error.

OSE_MMS_ENO_CODEDATA 0x00580007 There was no definition of execut-able memory. This is a fatal error.

OSE_MMS_EILLEGAL_EXEC_AREA

0x00580008 The definition of executable memory was illegal, perhaps imple-mentation error for a specific MMU. This is a fatal error.

OSE_MMS_EILLEGAL_START_SEQ

0x00580009 An erroneous start-up sequence. This is a fatal error.

176 DN0479352Issue 4-2


Id:0900d805806444bc


OSE_MMS_EILLEGAL_ALIGNMENT

0x0058000A Illegal alignment. All regions (GLOBAL_REGION, LOCAL_REGION), executable memory (CODE_DATA), and MMS heap (MMS_MEMORY) must be aligned on a page boundary (4 kbyte). This is a fatal error.

OSE_MMS_EILLEGAL_ACCESS_TYPE

0x0058000B Illegal access mode of region. This is a fatal error.

OSE_MMS_EPAGETABLE_ILLEGAL_CONFIGURATION

0x0058000C Illegal placement of a page table. The size is not one of the legal sizes, or the start address of the page table is not a multiple of the size. This is a fatal error.

OSE_MMS_ECORRUPTED_RECOVERY

0x00580010 The information detected after warm start was corrupted, and a cold start was forced.

OSE_MMS_ENONPROTECTED_RECOVERY

0x00580011 The information detected after warm start was in a non-protected state, and a cold start was forced.

OSE_MMS_EINTERNAL 0x00580012 An internal error that should not occur. This error must be reported to OSE systems.

OSE_MMS_EBIOS_PARSE_ERROR

0x00580015 An error was encountered when trying to fetch configuration infor-mation from BIOS.

OSE_MMS_EILLEGAL_L2_CACHE_CONFIGURATION

0x00580016 The get_spr_value() hook returned an illegal value for a SPR register. The extra parameter contains the SPR number.

OSE_MMS_EUNEXPECTED_EXCEPTION

0x00580013 An unexpected exception occurred. The field exception code indicates the type of the exception. This error consists of an error code and a pointer to a dump of the register file content at the time of the exception. The extra parameter in the error handler call is the pointer. The type definition of the register file dump is described below. The execution mode at the time of the fault is always given in exception faults.

Note that the error handler will not execute the code beyond an eventual kill_proc command.

OSE_MMS_ENESTED_EXCEPTION

0x00580014 An exception has occurred while processing another one inside the MMS. The field exception code indi-cates the type of the exception. It is non-recoverable and system-fatal.


DN0479352Issue 4-2

177


Id:0900d805806444bc

Error code description for General Link Handler

OSE_MMS_DETECT_CPU_FAILED

0x00580017 The armhal package failed to find CPU-specific functions for the current CPU. Verify that your CPU is listed in the file 'mmshal.con'.

OSE_MMS_CPUFUNCS_MISMATCH

0x00580018 When probing for CPU functions, the set of functions for this CPU contained the wrong number of functions. This indicates that the version of the mmshal cpu functions does not match the version of the rest of the MMS library.

OSE_MMS_ILLEGAL_STATIC_REG

0x00580019 Creating static regions for a segment other than the system segment is not allowed for the current implementation and CPU. The extra parameter contains the segment ID (!= 0) that was used to create the region.



OSE_GLH_EBUFBEG_OFFS_ERROR

0x00600000 An invalid bufbeg configuration. It should be a multiple of 4.

OSE_GLH_EUNDEFINED_SIG 0x00600001 The GLH received an unknown signal. The extra parameter is a pointer to the received signal. If the error handler returns ok, the signal will be freed, and the GLH will continue operation.

OSE_GLH_ELINKID_0 0x00600002 An invalid link ID for a new connec-tion specified by the PLH.

OSE_GLH_EINTERNAL_PROC_TERMINATED

0x00600003 A process internal to the GLH was killed. Never kill any GLH pro-cesses.

OSE_GLH_EGLH_TERMINATED 0x00600004 The main GLH process was shut down (killed) incorrectly. The proper way to terminate a GLH is to send a GLH_TERMINATE signal to the GLH.

OSE_GLH_EILLEGAL_SIGDESCTAB_PTR

0x0060000A The symbol description table pointer which is stored in environ-ment variable oseSigdescTab is illegal.

OSE_GLH_ESIGDESCTAB_CORRUPT

0x0060000B The symbol description table is corrupt or in an unknown format.

OSE_GLH_EWRONG_SIGDESC_SIZE

0x0060000 The symbol description table size is not as expected. The symbol description table must be compiled with the same structure alignment and padding as the GLH.

178 DN0479352Issue 4-2


Id:0900d805806444bc


Error code description for General Protocol Link Handler

OSE_GLH_EDUPLICATE_SIGNAL

0x0060000D The symbol description table contains two identical symbols. This indicates that the symbol description table generator is not working properly.

OSE_GLH_ERECEIVE_NO_SIGNAL_FOUND

0x0060000F The GLH received a converted signal sent from a remote GLH, but the signal number was not found in the symbol description table. Make sure that the tables on the sender and receiver side are identical.

OSE_GLH_ESIGNAL_SIZE 0x00600010 The Signal Size received is invalid.

OSE_GLH_EINTERNAL_ERROR 0x80601000 The GLH detected an internal error (inconsistency). The lower 12 bits is the line number in the source file. This is a fatal error.



OSE_GPL_EMAX_SIG_SIZE 0x80640000 Invalid maximum sigsize configura-tion. It should be less than or equal to the maximum number of out-standing bytes.

OSE_GPL_EMAX_SIG_SIZE_TOO_SMALL

0x80640001 Invalid maximum sigsize configura-tion. It is too small. Make it larger.

OSE_GPL_EBUFBEG_OFFS_ERROR

0x80640002 Invalid bufbeg offset configuration. It should be a multiple of 4 bytes.

OSE_GPL_ENO_OF_RETRANSMITS

0x80640003 Invalid number of retransmits con-figuration. It should be >= 1.

OSE_GPL_EMAX_FLUSH 0x80640004 Invalid max flush configuration. It should be >= 1.

OSE_GPL_ETIMEOUT_TRANSMIT

0x80640005 Invalid transmit time-out configura-tion. It should be >= 10 ms.

OSE_GPL_EPID_PDR_OR_ACTION_TRANSMIT

0x80640007 Invalid PDR configuration, neither PDR process PID nor PDR call-back function specified.

OSE_GPL_ENO_OF_BUFFERED_ACK

0x80640008 Invalid number of buffered acks configuration. It should be <= 28 (the size of sliding window queue - 4).

OSE_GPL_EUNDEFINED_SIG 0x80640009 The GPL received an unknown signal. The extra parameter is a pointer to the received signal. If the error handler returns ok, the signal will be freed, and the GPL will continue operation.

OSE_GPL_ENAME_IN_USE 0x8064000A More than one link handler with the same name detected.

DN0479352Issue 4-2

179


Id:0900d805806444bc

Error code description for General Protocol Link Handler

Error code description for UDP Driver for General Protocol Link Handler

OSE_GPL_EREM_ADDR_EQU_BROADC_ADDR

0x8064000B A link handler with an invalid address (IP-address:UDP-port) was found. This is a fatal error.

OSE_GPL_EPDR_CEASED 0x8064000C The GPL detected an inconsistency probably caused by the PDR.

OSE_GPL_ECORRUPT_GPL_TRANS_ACK_RECEIVE_SIG

0x8064000D The GPL detected an inconsistency in the sliding window handling.

OSE_GPL_ECORRUPT_GPL_RECEIVE_SIG

0x8064000E The GPL received an invalid signal from a remote link handler.

OSE_GPL_ETOO_MANY_REM_CONNECTIONS

0x8064000F Too many simultaneous connec-tions attempted. The maximum is 4095.



OSE_GPL_EMAX_QUEUE_LENGTH_REACHED

0x80640010 This error is reported by the Send-Congestion Handling mechanism when the user-specified maximum queue length is reached. It is safe to return from this error. If the error handler returns, the connection will be taken down, and then restarted.

OSE_GPL_EWRONG_CONFIG_ORDER

0x80640011 The initialisation signals to the link handler were sent in the wrong order. The extra parameter contains the initialisation signal that triggered this error. If the applica-tion returns from the error handler, the offending signal will be ignored and freed.


OSE_UDPPDR_ESOCKET_FAILED

0x00660000 socket() failed, lower 8 bits is the errno value.

OSE_UDPPDR_EIOCTL_GIFADDR_FAILED

0x00660100 ioctl(SIOCGIFADDR) failed, lower 8 bits is the errno value.

OSE_UDPPDR_ECLOSE_FAILED 0x00660200 close() failed, lower 8 bits is the errno value

OSE_UDPPDR_EIOCTL_GIFBRDADDR_FAILED

0x00660300 ioctl(SIOCGIFBRDADDR) failed, lower 8 bits is the errno value.

OSE_UDPPDR_ESENDTO_FAILED

0x00660400 sendto() failed, lower 8 bits is the errno value.

OSE_UDPPDR_EFCNTL_NDELAY_FAILED

0x00660500 fcntl(F_SETFL, O_NDELAY) failed, lower 8 bits is the errno value.

180 DN0479352Issue 4-2


Id:0900d805806444bc


Error code description for UDP Driver for General Protocol Link Handler

Error code description for Serial Driver for General Protocol Link Handler

OSE_UDPPDR_ESETSOCKOPT_REUSEADDR_FAILED

0x00660600 setsockopt(SOL_SOCKET, SO_REUSEADDR) failed, lower 8 bits is the errno value.

OSE_UDPPDR_EBIND_FAILED 0x00660700 bind() failed, lower 8 bits is the errno value.

OSE_UDPPDR_EGETSOCKNAME_FAILED

0x00660800 getsockname() failed, lower 8 bits is the errno value.

OSE_UDPPDR_ESETSOCKOPT_BROADCAST_FAILED

0x00660900 setsockopt(SOL_SOCKET, SO_BROADCAST) failed, lower 8 bits is the errno value.

OSE_UDPPDR_ESETSOCKOPT_RCVBUF_FAILED

0x00660A00 setsockopt(SOL_SOCKET, SO_RCVBUF) failed, lower 8 bits is the errno value

OSE_UDPPDR_ESETSOCKOPT_SNDBUF_FAILED

0x00660B00 setsockopt(SOL_SOCKET, SO_SNDBUF) failed, lower 8 bits is the errno value

OSE_UDPPDR_ERECVFROM_FAILED

0x00660C00 recvfrom() failed, lower 8 bits is the errno value



OSE_UDPPDR_ESELECT_FAILED

0x00660D00 select() failed, lower 8 bits is the errno value.

OSE_UDPPDR_SIOCGIFFLAGS_FAILED

0x00660E00 select() failed, lower 8 bits is the errno value.

OSE_UDPPDR_SIOCGIFBRDADDR_OR_SIOCGIFDSTADDR_FAILED

0x00660F00 select() failed, lower 8 bits is the errno value

OSE_UDPPDR_ESETSOCKOPT_REUSEPORT_FAILED

0x00661000 setsockopt(SOL_SOCKET, SO_REUSEPORT) failed, lower 8 bits is the errno value


OSE_SERPDR_EUNKNOWN_SIGNAL

0x00670000 SERPDR received an unwanted signal, the extra parameter points to the signal. This error is not fatal. The signal will be freed, and the link handler will continue operation.

OSE_SERPDR_ENO_DRIVER 0x00670100 biosOpen() failed, no such BIOS module. The extra parameter points to the specified BIOS name.

OSE_SERPDR_ENOT_A_DRIVER

0x00670200 BIOS module was not a device driver. The extra parameter points to the specified BIOS name.

DN0479352Issue 4-2

181


Id:0900d805806444bc

Error code description for Ethernet Driver for General Protocol Link Handler

OSE_SERPDR_EDDOPEN_FAILED

0x00670300 ddOpen() failed, lower 8 bits is the device driver error code.

OSE_SERPDR_EDDSETCONF_FAILED

0x00670400 ddSetConf() failed, lower 8 bits is the device driver error code.

OSE_SERPDR_EDDGETCONF_FAILED

0x00670500 ddGetConf() failed, lower 8 bits is the device driver error code.

OSE_SERPDR_EDDSTART_FAILED

0x00670600 ddStart() failed, lower 8 bits is the device driver error code.

OSE_SERPDR_EDDWRITE_FAILED

0x00670700 ddWrite() failed, lower 8 bits is the device driver error code. This error is not fatal. The packet will be freed, and the link handler will continue operation.

OSE_SERPDR_EOPEN_FAILED 0x00671800 open() failed, lower 8 bits is the errno value.

OSE_SERPDR_ETCGETATTR_FAILED

0x00671900 tcgetattr() failed, lower 8 bits is the errno value.

OSE_SERPDR_ETCSETATTR_FAILED

0x00671A00 tcsetattr() failed, lower 8 bits is the errno value.

OSE_SERPDR_EWRITE_FAILED 0x00671B00 write() failed, lower 8 bits is the errno value. This error is not fatal. The packet will be freed, and the link handler will continue operation.

OSE_SERPDR_EREAD_FAILED 0x00671C00 read() failed, lower 8 bits is the errno value. This error is not fatal. The error will be ignored, and the link handler will continue operation.

OSE_SERPDR_EINVALID_BAUDRATE

0x00671D00 Invalid or unsupported baud rate.



OSE_ETHPDR_EUNKNOWN_SIGNAL

0x00680000 ETHPDR received an unwanted signal. The extra parameter points to the signal. This error is not fatal. The signal will be freed, and the link handler will continue operation.

OSE_ETHPDR_ENO_DRIVER 0x00680100 biosOpen() failed, no such BIOS module. The extra parameter points to the specified BIOS name.

OSE_ETHPDR_ENOT_A_DRIVER

0x00680200 BIOS module was not a device driver. The extra parameter points to the specified BIOS name.

OSE_ETHPDR_EDDOPEN_FAILED

0x00680300 ddOpen() failed, lower 8 bits is the device driver error code.

OSE_ETHPDR_EDDSETCONF_FAILED

0x00680400 ddSetConf() failed, lower 8 bits is the device driver error code.

182 DN0479352Issue 4-2


Id:0900d805806444bc


Error code description for TFTP Server

Error code description for FTP Server

Error code description for Telnet Server

OSE_ETHPDR_EDDGETCONF_FAILED

0x00680500 ddGetConf() failed, lower 8 bits is the device driver error code.

OSE_ETHPDR_EDDSTART_FAILED

0x00680600 ddStart() failed, lower 8 bits is the device driver error code.

OSE_ETHPDR_EDDWRITE_FAILED

0x00680700 ddWrite() failed, lower 8 bits is the device driver error code. This error is not fatal. The packet will be freed, and the link handler will continue operation.



OSE_TFTPD_ESOCKET_FAILED 0x00690000 socket() failed, lower 8 bits is the errno value.

OSE_TFTPD_EBIND_FAILED 0x00690100 bind() failed, lower 8 bits is the errno value.

OSE_TFTPD_ERECVFROM_FAILED

0x00690200 recvfrom() failed, lower 8 bits is the errno value.

OSE_TFTPD_ECONNECT_FAILED

0x00690300 connect() failed, lower 8 bits is the errno value.

Error code Value Description

OSE_FTPD_ESOCKET_FAILED 0x006B0000 socket() failed, lower 8 bits is the errno value.

OSE_FTPD_EBIND_FAILED 0x006B0100 bind() failed, lower 8 bits is the errno value.

OSE_FTPD_ELISTEN_FAILED. 0x006B0200 listen() failed, lower 8 bits is the errno value.

OSE_FTPD_EACCEPT_FAILED. 0x006B0300 accept() failed, lower 8 bits is the errno value.

OSE_FTPD_ESETSOCKOPT_REUSEADDR_FAILED

0x006B0400 setsockopt(SO_REUSEADDR) failed, lower 8 bits is the errno value


OSE_TELNETD_ESOCKET_FAILED

0x6C0000 socket() failed, lower 8 bits is the errno value.

OSE_TELNETD_EBIND_FAILED 0x6C0100 bind() failed, lower 8 bits is the errno value.

OSE_TELNETD_ELISTEN_FAILED

0x6C0200 listen() failed, lower 8 bits is the errno value.

DN0479352Issue 4-2

183


Id:0900d805806444bc

Error code description for OSE System Surfer

Error code description for Bootp Client

OSE_TELNETD_EACCEPT_FAILED

0x6C0300 accept() failed, lower 8 bits is the errno value.

OSE_TELNETD_ESETSOCKOPT_OSEOWNER_FAILED

0x6C0400 setsockopt(SO_OSEOWNER) failed, lower 8 bits is the errno value.

OSE_TELNETD_ESETSOCKOPT_KEEPALIVE_FAILED

0x6C0500 setsockopt(SO_KEEPALIVE) failed, lower 8 bits is the errno value.

OSE_TELNETD_ESETSOCKOPT_OSEASYNC_FAILED

0x6C0600 setsockopt(SO_OSEASYNC) failed, lower 8 bits is the errno value.

OSE_TELNETD_ESETSOCKOPT_OSEEVENT_FAILED

0x6C0700 setsockopt(SO_OSEEVENT) failed, lower 8 bits is the errno value.

OSE_TELNETD_EIOCTL_FIONBIO_FAILED

0x6C0800 ioctl(FIONBIO) failed, lower 8 bits is the errno value.



OSE_SURFER_SOCKET 0x006D1000 socket() failed, lower 8 bits is the errno value.

OSE_SURFER_SETSOCKOPT 0x006D2000 Call to setsockopt failed.

OSE_SURFER_BIND 0x006D3000 bind() failed, lower 8 bits is the errno value.

OSE_SURFERLISTEN 0x006D4000 listen() failed, lower 8 bits is the errno value.

OSE_SURFER_NONBLOCK 0x006D5000 A non-blocking call failed.

OSE_SURFER_ACCEPT 0x006D6000 accept() failed, lower 8 bits is the errno value.

OSE_SURFER_READ 0x006D7000 An unexpected error while reading.

OSE_SURFER_CLOSE 0x006D8000 close() failed, lower 8 bits is the errno value.


OSE_BOOTP_ESOCKET_FAILED 0x006E0001 INET socket() failed. The extra parameter contains the INET errno.

OSE_BOOTP_EBIND_FAILED 0x006E0002 INET bind failed. The extra param-eter contains the INET errno.

OSE_BOOTP_ESENDTO_FAILED

0x006E0003 sendto failed. The extra parameter contains the INET errno.

OSE_BOOTP_ESIGNAL_FAILED 0x006E0004 An unknown signal was received. The extra parameter contains a pointer to signal.

184 DN0479352Issue 4-2


Id:0900d805806444bc


Error code description for DNS Resolver

Error code description for DHCP Client

OSE_BOOTP_ESOCKOPT_FAILED

0x006E0005 Call to setsockopt failed. The extra parameter contains the INET errno.



OSE_RES_ESOCKET_FAILED 0x006F0001 INET socket() failed. The extra parameter contains the INET errno.

OSE_RES_ENO_SOCKET 0x006F0002 No sockets could be created. This is a fatal error.

OSE_RES_ESETSOCKOPT_OSEASYNC_FAILED

0x006F0003 setsockopt(SO_OSEASYNC) failed.

OSE_RES_EINET_SEND_FAILED

0x006F0004 inet_send failed. The extra parame-ter contains the INET errno.

OSE_RES_EUNKNOWN_SIGNAL 0x006F0005 An unknown signal was received by ose_resolve.

OSE_RES_ENOT_INITIALIZED 0x006F0006 Resolver has not been initialised.

OSE_RES_DAEMON_TIME_OUT 0x006F0007 The process ose_resolve could not be found.

OSE_RES_ECONNECT_FAILED 0x006F0008 connect() failed, lower 8 bits is the errno value.


OSE_DHCP_EIF_IOCTL 0x006F1001 The ioctl call to get/set information on an IF failed.

OSE_DHCP_EIF_IOCTL_SET_IP 0x006F1002 The Interface ioctl to set the new IP address failed.

OSE_DHCP_EADD_ROUTE 0x006F1003 Could not add route. The extra parameter contains the INET route status.

OSE_DHCP_ESET_SUBNET 0x006F1004 Could not set subnet mask. The extra parameter contains the INET errno.

OSE_DHCP_ESOCKET_FAILED 0x006F1005 Failed to create a socket.

OSE_DHCP_ESOCKOPT_FAILED

0x006F1006 Failed to set socket in async. mode. The extra parameter contains the INET errno.

OSE_DHCP_ESENDTO_FAILED 0x006F1007 INET sendto failed. The extra parameter contains the INET errno.

OSE_DHCP_EUNKNOWN_SIGNAL

0x006F1008 The DHCP client received an unknown DHCP message from the server.

OSE_DHCP_ESIGNAL_FAILED 0x006F1009 The DHCP client received an unknown OSE signal.

DN0479352Issue 4-2

185


Id:0900d805806444bc

Error code description for FTP Client

Error code description for DNS Server

OSE_DHCP_EBIND_FAILED 0x006F100A bind() failed. Extra parameter contains the INET errno.

OSE_DHCP_EMKQUERY 0x006F100B The DHCP client failed to create a valid DHCP message.

OSE_DHCP_EGET_HWADDR 0x006F100C The DHCP client failed to get the HW address for the interface.

OSE_DHCP_EIF_IOCTL_GET_IP 0x006F100D The Interface ioctl failed to get the IP address.

OSE_DHCP_EMALLOC 0x006F100E Could not allocate memory from the heap. The extra parameter contains the requested size.



OSE_FTP_ESOCKET_FAILED 0x006F2001 Failed to create a socket.

OSE_FTP_EBIND_FAILED 0x006F2002 bind() failed. The extra parameter contains the INET errno.

OSE_FTP_EBAD_SOCKET 0x006F2003 getsockname() failed. The extra parameter contains the INET errno.

OSE_FTP_EMALLOC 0x006F2004 Could not allocate memory from the heap. The extra parameter contains the requested size.


OSE_DNS_SRV_ESOCKET 0x00C22001 INET socket() failed. The extra parameter contains the INET errno.

OSE_DNS_SRV_ESETSOCKOPT 0x00C22002 setsockopt() failed.

OSE_DNS_SRV_EBIND 0x00C22003 Failed to bind a socket.

OSE_DNS_SRV_CONNECT 0x00C22004 connect() failed. The extra parame-ter contains the INET errno.

OSE_DNS_SRV_ESEND 0x00C22005 send() failed. The extra parameter contains the INET errno.

OSE_DNS_SRV_ECLASS 0x00C22006 An unknown DNS class number.

OSE_DNS_SRV_ETYPE 0x00C22007 An unknown DNS type number.

OSE_DNS_SRV_EREAD 0x00C22008 An unexpected error while reading a file.

OSE_DNS_SRV_ESIG 0x00C22009 An unknown signal was received. The extra parameter contains the signal.

OSE_DNS_SRV_DAEMON_TIME_OUT

0x00C2200A The ose_dnsd process could not be found.

186 DN0479352Issue 4-2


Id:0900d805806444bc


Error code description for Web Server (WEBS)

Error code description for Heap Manager

OSE_DNS_SRV_EOPCODE 0x00C2200B An unknown opcode received in a DNS message.



WEBSERR_SOCKET 0x00711000 socket() failed, lower 8 bits is the errno value.

WEBSERR_SETSOCKOPT 0x00712000 Call to setsockopt failed.

WEBSERR_BIND 0x00713000 bind() failed, lower 8 bits is the errno value.

WEBSERR_LISTEN 0x00714000 listen() failed, lower 8 bits is the errno value.

WEBSERR_NONBLOCK 0x00715000 A non-blocking call failed.

WEBSERR_CLOSE 0x00716000 close() failed, lower 8 bits is the errno value.

WEBSERR_BIOSINSTALL 0x00717000 BIOS install failed.

WEBSERR_BIOSOPEN 0x00718000 BIOS open failed.

WEBSERR_BIOSCALL 0x00719000 A BIOS call failed.


OSE_HEAP_EBIOS_INSTALL_FAILED

0x820000 Server could not install a trap handler. The extra parameter contains a pointer to a HeapBuffer-InfoReply struct. The BIOS error code is stored in the status field of the struct.

OSE_HEAP_EHUNT_HEAPD_FAILED

0x820001 Function library could not find ose_heapd.

OSE_HEAP_EBIOS_OPEN_FAILED

0x820002 Function library could not open a heap BIOS module.

OSE_HEAP_EUNKNOWN_SIGNAL

0x820003 Heap daemon received an unknown signal. The extra parame-ter contains a pointer to a Heap-BufferInfoReply struct. The pointer to the signal is stored in the address field of the struct. Ignore the error, and the signal will be ignored.

OSE_HEAP_EUNKNOWN_FCODE

0x820004 Server received an unknown BIOS function code. The extra parameter contains a pointer to a HeapBuffer-InfoReply struct. The unknown function code is stored in the status field of the struct.

DN0479352Issue 4-2

187


Id:0900d805806444bc

OSE_HEAP_EINIT_HEAP_FAILED

0x820005 Failed to initialise the heap, reply not received from the heap daemon.

OSE_HEAP_ENO_HEAP_INIT_FLIB

0x820006 Start hook 2 heap_init_flib not called.

OSE_HEAP_EFREED_BUFFER_OVERWRITTEN

0x820007 A free buffer has been overwritten by the user. The extra parameter is a pointer to a HeapBufferInfoReply struct with additional information about the buffer.

OSE_HEAP_ESIZE_TOO_LARGE 0x820100 Tried to allocate too large a buffer. The extra parameter is a pointer to a HeapBufferInfoReply struct. req_size is the size required, and act_size is the minimum size required (with the internal over-head, but without file and line infor-mation).

OSE_HEAP_EPTR_INVALID 0x820101 Tried to free an invalid pointer. The extra parameter is a pointer to a HeapBufferInfoReply struct. The pointer is stored in the address field.

OSE_HEAP_EBUFFER_FREE 0x820102 Tried to operate on free buffer. The extra parameter is a pointer to a HeapBufferInfoReply struct with additional information about the buffer.

OSE_HEAP_EPROCESS_NOT_OWNER

0x820103 Tried to operate on a buffer that is not owned. The extra parameter is a pointer to a HeapBufferInfoReply struct with additional information about the buffer.

OSE_HEAP_EENDMARK_OVERWRITTEN

0x820104 Tried to operate on a buffer whose endmark is overwritten. Extra parameter is a pointer to a Heap-BufferInfoReply struct with addi-tional information about the buffer.

OSE_HEAP_EHEAP_EXHAUSTED

0x820105 Heap is exhausted and could not be properly extended. The extra parameter is a pointer to a Heap-BufferInfoReply struct. req_size is the size required, and act_size is the minimum size required (with the internal overhead, but without file and line information) to extend the heap.

OSE_HEAP_ENO_EXTEND_HEAP

0x820106 Heap extension not available (heap daemon too old).


188 DN0479352Issue 4-2


Id:0900d805806444bc


Error code description for Board Support Package

Error code description for Time Out Server

Error code description for RealTime Clock


OSE_BSP_EBIOSINSTALL_FAILED

0x880000 BIOS install failed.

OSE_BSP_EBIOSOPEN_FAILED 0x880001 BIOS open failed.

OSE_BSP_EDEVICE_INIT_FAILED

0x880002 Device initialisation failed.

OSE_BSP_EBIOSCALL_FAILED 0x880003 A BIOS call failed.

OSE_BSP_SERPRINTF_EUART 0x880010 dcUartError called in serprintf.


OSE_TOSV_EBIOS_INSTALL_FAILED

0x8A0000 Server could not install a TOSV module. The extra parameter contains the error code.

OSE_TOSV_EBIOS_OPEN_FAILED

0x8A0001 TOSV function library could not open a TOSV module.

OSE_TOSV_EBIOS_CALL_FAILED

0x8A0002 BIOS call TOSV returned an error. The extra parameter contains the error code.

OSE_TOSV_EUNKNOWN_SIGNAL

0x8A0003 Time-out server received an unknown signal. The extra parame-ter contains a pointer to the unknown signal.

OSE_TOSV_EHUNT_OSE_TOSV_FAILED

0x8A0004 Time-out server process 'ose_tosv' could not be found.

OSE_TOSV_ERESET_TOO_LATE

0x8A0005 resetTmo() called after reception of a time-out signal.


OSE_RTC_EBIOS_INSTALL_FAILED

0x8B0000 Server could not install a trap handler. The extra parameter contains the BIOS error code.

OSE_RTC_EBIOS_OPEN_FAILED

0x8B0001 Trap interface function library could not open a RTC module.

OSE_RTC_EUNKNOWN_SIGNAL 0x8B0002 Server received an unknown signal. The extra parameter contains a pointer to the unknown signal.

OSE_RTC_EUNKNOWN_FCODE 0x8B0003 Server received an unknown BIOS function code. The extra parameter contains the unknown function code.

DN0479352Issue 4-2

189


Id:0900d805806444bc

Error code description for Name Server

Error code description for PostMortemDump

OSE_RTC_EASCTIME_INVALID_TM

0x8B0004 asctime/asctime_r called with an invalid struct tm parameter.

OSE_RTC_EHUNT_OSE_RTC_FAILED

0x8B0005 Real Time server process 'ose_rtc' could not be found.

OSE_RTC_EHISTORIC_PERIODIC_ALARM

0x8B0006 A historic periodic alarm was created. The extra parameter contains the expire time.

OSE_RTC_EWILD_ALARM_ID 0x8B0007 Calling rtc_cancel_alarm() with a wild alarm identifier. The extra parameter contains a pointer to the signal.



OSENS_NOT_IMPLEMENTED_ERR

0x808d0000 Tried to use something not currently implemented. The extra parameter contains a pointer to an information string. This is a fatal error.

OSENS_INTERNAL_ERR 0x808d0001 The name server found an internal error. This is a fatal error.

OSENS_ILLEGAL_SID_ERR 0x008d0002 An illegal subscription identifier (sid) was presented to the name server. The extra parameter holds the illegal subscription identifier. It is safe to continue to run after this error.

OSENS_TAG_TOO_LONG_ERR 0x008d0003 This error is no longer valid. The 254-character limitation was removed in version P1.0.0.3

OSENS_LNH_NAME_TOO_LONG_ERR

0x008d0004 This error is no longer valid. The 254-character limitation was removed in version P1.0.0.3.


OSE_PMD_EBIOS_INSTALL_FAILED

0x8E0000 The PMD module could not be installed. This is a fatal error. The extra parameter contains the error code returned from biosInstall().

OSE_PMD_EBIOS_OPEN_FAILED

0x8E0001 The PMD function library could not open the PMD module. This is a fatal error. The extra parameter is not used.

190 DN0479352Issue 4-2


Id:0900d805806444bc


Error code description for EFS Common

OSE_PMD_EBIOS_CALL_FAILED

0x8E0002 A BIOS call in the PMD module returned an error. This is a fatal error. The extra parameter contains the error code returned from the BIOS call.

OSE_PMD_EUNKNOWN_BIOS_CALL

0x8E0003 An unknown BIOS call was pre-sented to the PMD module. This is a fatal error. The extra parameter contains the error code returned from the BIOS call.

OSE_PMD_EKERNEL_UNAVAILABLE

0x8E0004 PMD could not 'attach' to the kernel data structures. This is a fatal error. The extra parameter is not used.

OSE_PMD_EBAD_PMD_AREA_CONFIGURATION

0x8E0005 A bad configuration of the PMD area was detected. This is a fatal error. The extra parameter contains the offending parameter value. See pmd.h for more details about PMD area configuration.

OSE_PMD_EPMD_CONFIGURATION_DENIED

0x8E0006 A process does not have supervisor mode right to configure the PMD area or its list of memory areas. This is a fatal error. The extra parameter contains the offending process identifier. See pmd.h for more details about PMD area con-figuration.

OSE_PMD_EWORK_AREA_TOO_SMALL

0x8E0007 The memory dedicated as PMD work area is not sufficient. The work area is configured with the item WORK_AREA_SIZE (<size>) in pmd.con. Normally the default and minimum requirement, 64K, is suffi-cient, but in a system where a large number of pool fragments (more than 50) or programs is used, the work area may need to be increased. Increasing the current value by doubling it should be enough. This error often occurs as a recursive error, since the dump functions are usually called from within an error handler. This is a fatal error. The extra parameter contains the current work area size. See pmd.h for more details about PMD area configuration.



OSE_EFS_EREGISTER_FAILED 0x900000 Failure to register an EFS object to FSS.

DN0479352Issue 4-2

191


Id:0900d805806444bc

Error code description for EFS Function Library

OSE_EFS_EUNKNOWN_SIGNAL 0x900001 EFS object received an unknown signal. The address to the corre-sponding signal structure is in the extra parameter. Ignore the error, and the signal will be freed and the execution continued.

OSE_EFS_EHUNT_FSS_TIMEOUT

0x900002 Hunt for ose_fss not successful. Ignore the error, and the process will continue trying.

OSE_EFS_EHUNT_PARTMAN_FAILED

0x900003 Hunt for ose_partman not success-ful.



OSE_EFS_FLIB_ESHARE_TOO_LATE

0x910000 efs_segment_share() called too late (after any other FLIB call) by process.

OSE_EFS_FLIB_EINVALID_CLONE

0x910001 Invalid process to receive cloned state. The extra parameter is the pid of the invalid process. This process must be a stopped, prior-itised, or background process.

OSE_EFS_FLIB_EINVALID_FILE 0x910002 An invalid FILE specified. The extra parameter is the invalid FILE pointer.

OSE_EFS_FLIB_EINVALID_DIR 0x910003 An invalid DIR specified. The extra parameter is the invalid DIR pointer.

OSE_EFS_FLIB_EWRITE_AFTER_READ

0x910004 Trying to write after read with no intervening fflush/fseek and so forth. The extra parameter is the relevant FILE pointer.

OSE_EFS_FLIB_EREAD_AFTER_WRITE

0x910005 Trying to read after write with no intervening fflush/fseek and so forth. The extra parameter is the relevant FILE pointer.

OSE_EFS_FLIB_ENO_STDIN 0x910006 Referencing stdin, but no file descriptor 0 open.

OSE_EFS_FLIB_ENO_STDOUT 0x910007 Referencing stdout, but no file descriptor 1 open.

OSE_EFS_FLIB_ENO_STDERR 0x910008 Referencing stderr, but no file descriptor 2 open.

OSE_EFS_FLIB_EENV_TMPDIR_NOT_SET

0x910009 Environment variable EFS_TMPDIR not set when calling tmpnam() or tmpfile(). It must be set on the process or block that calls these functions.

192 DN0479352Issue 4-2


Id:0900d805806444bc


Error code description for EFS serdd

Error code description for OSE EFS Shell

OSE_EFS_FLIB_ECLOSE_FD_IN_USE

0x91000A Closing a file descriptor that is in use by some other process. The extra parameter is the file descrip-tor.

OSE_EFS_FLIB_EINVALID_UNGETC

0x91000B Calling ungetc() for a file not in read mode or before any characters have been read. The extra parame-ter is the relevant FILE pointer.

OSE_EFS_FLIB_EINVALID_SHARE

0x91000C An invalid block to be put into shared mode. The extra parameter is the invalid bid.

OSE_EFS_FLIB_EFD_NOT_SOCKET

0x91000D Attempted socket operation on non-socket descriptor. The extra param-eter is the invalid descriptor.

OSE_EFS_FLIB_EFD_NOT_FILE 0x91000E Attempted file operation on non-file descriptor. The extra parameter is the invalid descriptor.

OSE_EFS_FLIB_EUNRESOLVED_INET_FUNCTION

0x91000F Unresolved weak reference to INET function, in other words, missing INET library when linking.

OSE_EFS_FLIB_EINVALID_PEEKC

0x910010 Calling efs_peekc() for a file not in read mode or not buffered. The extra parameter is the relevant FILE pointer.



OSE_EFS_SERDD_ENO_DEVICE

0x920000 serdd could not open the specified device or it was not a serial device.

OSE_EFS_SERDD_EUNIT_BUSY 0x920001 Unit could not be opened.

OSE_EFS_SERDD_ESETCONF_FAILED

0x920002 Unit could not be configured according to specification.

OSE_EFS_SERDD_EUNEXPECTED_ERROR

0x920003 serdd got an unexpected device driver error.


OSE_EFS_SHELL_EHUNT_FAILED

0x930000 Hunt failed. The extra parameter contains the name of the process hunted for.

DN0479352Issue 4-2

193


Id:0900d805806444bc

Error code description for EFS startefs.c

Error code description for DebugServer for Illuminator


OSE_EFS_STARTEFS_EMOUNT_TTY_FAILED

0x940000 start_efs could not mount serial terminal (/tty). The extra parameter contains the extended error code.

OSE_EFS_STARTEFS_EOPEN_TTY_FAILED

0x940001 start_efs could not properly open serial terminal (/tty) as stdio. The extra parameter contains the extended error code.

OSE_EFS_STARTEFS_EMOUNT_DISK_FAILED

0x940002 start_efs could not mount ram disk (/ram). The extra parameter contains the extended error code.

OSE_EFS_STARTEFS_EFORMAT_DISK_FAILED

0x940003 start_efs could not format ram disk (/ram). The extra parameter contains the exended error code.

OSE_EFS_STARTEFS_ECHDIR_DISK_FAILED

0x940004 start_efs could not change the current directory to the ram disk (/ram). The extra parameter contains the extended error code.

OSE_EFS_STARTEFS_ERESOLVE_FAILED

0x940005 start_efs could not resolve a name with the FSS. The extra parameter contains a pointer to the name that did not resolve.

OSE_EFS_STARTEFS_DEL_KEY_MAPPING_FAILED

0x940006 In start_efs, the call to efs_examine_term or efs_config_term failed.


OSE_DBGS_ESOCKET_OPERATION

0xA00000 A socket operation failed. The error is fatal for the ose_dbgserver process. In the extra parameter, the 16 LSB is the errno value from the failed socket call and the 16 MSB is the line number for the error call. If the error handler returns, the ose_dbgserver process will be stopped.

OSE_DBGS_EFAILED_TO_GET_IP

0xA00002 Failed to get the target's IP address. The error is fatal for the ose_dbgserver process. The extra parameter: the extra field contains the errno value. This error is reported when the ose_dbgserver process fails to obtain the target's IP address from INET. This error may indicate that there is some sort of a configuration error. If the error handler returns, the ose_dbgserver process will be stopped.

194 DN0479352Issue 4-2


Id:0900d805806444bc


OSE_DBGS_EFAILED_TO_SET_NON_BLOCKING

0xA00003 Failed to set a socket in non-blocking mode. The error is fatal for the ose_dbgserver process. The extra parameter contains the errno value from the failed socket call. If the error handler returns, the ose_dbgserver process will be stopped.

OSE_DBGS_EFAILED_TO_CREATE_SOCKET

0xA00004 Failed to create a new socket. The error is fatal for the ose_dbgserver process. The extra parameter contains the errno value from the failed socket call. If the error handler returns, the ose_dbgserver process will be stopped.

OSE_DBGS_ETOO_LONG_IF_NAME

0xA00005 The specified interface name is too long. The error is not fatal. The ose_dbgserver process will use the default interface name. The extra parameter contains the maximum length that can be used.

OSE_DBGS_ETOO_LARGE_PACKET

0xA00006 The ose_dbgserver process received a packet on TCP which was larger than the ose_dbgserver could handle. The error is not fatal. ose_dbgerver will throw the packet away. The extra parameter contains the packet size for the failing packet. If the error handler returns, the current client will be dis-connected.

OSE_DBGS_EIF_ERROR 0xA00007 An unexpected interface error from OSE INET. The error is fatal for the ose_dbgserver process. The extra parameter contains the interface status received from OSE INET. If the error handler returns, the ose_dbgserver process will be stopped.

OSE_DBGS_ELOST_INET 0xA00008 Lost the connection to the OSE INET. The error is fatal for the ose_dbgserver process. The extra parameter is not used. If the error handler returns, the ose_dbgserver process will be stopped.


DN0479352Issue 4-2

195


Id:0900d805806444bc

OSE_DBGS_ELDM_NOT_FOUND

0xA00009 The LDM was not found within the default time-out (10s). The error is not fatal. The ose_dbgserver process will continue to wait and report the error every 10 seconds until the LDM is found. The extra parameter contains a pointer to the hunt path used (located in the pool or text segment of the ose_dbgserver process).

OSE_DBGS_EILLEGAL_LDM_VERSION

0xA0000A Incorrect version of the LDM. The error is fatal for the ose_dbgserver process. The extra parameter contains the interface version number of the LDM. You should upgrade your kernel or the ose_dbgserver.

OSE_DBGS_EILLEGAL_LDM_ENDIAN

0xA0000B The LDM uses incorrect endian. The error is fatal for the ose_dbgserver. The extra parame-ter is not used.

OSE_DBGS_ELDM_CONNECTION_REFUSED

0xA0000C Connection refused by the LDM. This could be because the LDM is already connected to someone or some interface mismatch. The error is not fatal. The ose_dbgserver will sleep and retry to connect. The extra parameter is not used.

OSE_DBGS_ELDM_ERROR 0xA0000D The LDM reported an error to the dbgserver process. The error is fatal for the dbgserver processes. The extra parameter contains the error code from the LDM.

OSE_DBGS_EINVALID_HUNT_PATH

0xA0000E Incorrect LDM hunt path configura-tion. The OSE_LDM_HUNT_PATH environment variable must end with 'ose_ldm/', for example, 'remote_target/ose_ldm/'. The error is fatal for the dbgserver process. The extra parameter contains a pointer to the faulty environment variable value string.

OSE_DBGS_EUNKNOWN_SIGNAL

0xA0000F The dbserver received an unknown signal. The error is not fatal for the dbgserver. The extra parameter contains the signal pointer (in the address space of the dbgserver).


196 DN0479352Issue 4-2


Id:0900d805806444bc


Error code description for Pthreads

Error code description for OSE NTP/SNTP


OSE_PTH_INTERNAL 0xC10000 An internal error that should not occur. This error must be reported to OSE Systems.

OSE_PTH_EBIOS_INSTALL_FAILED

0xC10001 Could not install the trap handler. The extra parameter contains the BIOS error code.

OSE_PTH_NOPTHREAD 0xC10003 pthread function failed because the PID in the extra parameter did not refer to a pthread.

OSE_PTH_EUNKNOWN_FCODE 0xC10004 The server received an unknown BIOS function code. The extra parameter contains the unknown function code.

OSE_PTH_EBIOS_OPEN_FAILED

0xC10005 The function library could not open the PTHREAD BIOS module.

OSE_PTH_EBIOS_CALL_FAILED 0xC10006 A BIOS call failed. You have probably not installed the start hook initPthreads. The extra parameter contains the handle used in the call.


OSE_NTP_ERROR_CLOCK_TOO_SCREWED_UP

0x00C30000 The clock was mixed up. The NTP does not try to correct it.

OSE_NTP_ERROR_SOCKET_SETUP_FAILURE

0x00C30001 OSE NTP/SNTP failed to set up its socket.

OSE_NTP_ERROR_NO_NAME_SERVER

0x00C30002 OSE name server hunt failed.

OSE_NTP_ERROR_SERVICE_NOT_REGISTERED

0x00C30003 The OSE NTP/SNTP service was not registered by the OSE name server.

PCU2 Service Terminal Commands

Documents

Transcript of PCU2 Service Terminal Commands