Nokia Siemens Networks GSM/EDGE BSS, rel.

RG10(BSS), operating documentation, issue 05

PCU2 Service Terminal Commands
DN0479352 Issue 4-2 Approval Date 28.8.2009

PCU2 Service Terminal Commands

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 DOCUMENTATION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT, 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 Spannung. Einige Teile können auch eine hohe Betriebstemperatur aufweisen. Eine Nichtbeachtung dieser Situation und der Warnungshinweise kann zu Körperverletzungen 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.

2

Id:0900d805806444c9

DN0479352 Issue 4-2

PCU2 Service Terminal Commands

Table of Contents
This document has 196 pages. Summary of changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 1 1.1 1.2 1.3 1.4 1.5 1.6 1.7 2 2.1 2.1.1 2.1.2 2.1.3 2.1.4 2.1.5 2.1.6 2.1.7 2.1.8 2.1.9 2.1.10 2.1.11 2.1.12 2.1.13 2.1.14 2.1.15 2.2 2.2.1 2.2.2 2.2.3 2.2.4 2.2.5 2.2.6 2.2.7 2.2.8 2.3 2.3.1 2.3.2 2.3.3 2.3.4 2.3.5 2.4 2.4.1 Overview of PCU2 service terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . Service terminal in PCU2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Special characteristics of service terminal commands . . . . . . . . . . . . . Service terminal prompt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Service terminal login delays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Service terminal connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Service terminal commands output . . . . . . . . . . . . . . . . . . . . . . . . . . . . Disclaimer and welcome note . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Service terminal commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Service terminal general purpose commands . . . . . . . . . . . . . . . . . . . . exit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . esd (enable system dumps). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . dsd (disable system dumps) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . doe (display operating system error logs) . . . . . . . . . . . . . . . . . . . . . . . dpi (display PCU2 PIU information) . . . . . . . . . . . . . . . . . . . . . . . . . . . . dem (display elapsed milliseconds) . . . . . . . . . . . . . . . . . . . . . . . . . . . . eeqm (enable event queue monitoring) . . . . . . . . . . . . . . . . . . . . . . . . . deqm (disable event queue monitoring). . . . . . . . . . . . . . . . . . . . . . . . . deqs (display event queue statistics) . . . . . . . . . . . . . . . . . . . . . . . . . . . ecm (enable continuous mode) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . dcm (disable continuous mode) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . dbl (display bootup log) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . dai (display application IDs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . daa (display active alarms) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . uad (update authentication data) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Operating system commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . help/? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . date . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . rm. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Service terminal logging to file commands . . . . . . . . . . . . . . . . . . . . . . esl (enable ST logging) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . dsl (disable ST logging) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . dlfi (display logging to a file information) . . . . . . . . . . . . . . . . . . . . . . . . remove (remove logging files) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . > command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Process manipulation commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 10 10 11 12 13 13 14 15 15 15 15 16 16 17 18 18 19 19 21 22 22 28 30 31 31 31 32 32 33 33 33 34 34 35 35 36 36 37 38 40 40

DN0479352 Issue 4-2

Id:0900d805806444c9

3

. . . . . 80 dmml (disable MM data logging) . . . . . 81 netstat . . . . . . . . . . . . .1 2. . . . . . .12. . . . . . . . . . . . . . . . . . . . . .12. .message monitoring. . . . . . . . . . . . . . 95 dtrxtbf (display the TBF information for a particular TRX). . . . . . . . . . .5. . . . . . . . . . . . 90 dtrxrnw (display the radio network configuration for a particular TRX) . . . . . . . . . . . .1 2. 79 emml (enable MM data logging) . . . .9. . . . . . . . . . . . . . . . . . . 71 dfl (disable logging to file) . . . . . . . . . . . . . . . . . . . . . . .2 2. . . . . . . . .7. . . . . . . .5. . . . . . . . . . .5 2. .9. . . . . . . . . . . . . .4 Statistics commands . .7. .2 2. 55 mbbrbb (multiple black box read black box) . . . .5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4 2. . . . . . . . . . . . . . . . . . . . . . 80 IP manipulation commands. . . . . . . and IPC . . . 44 dbp (display buffer statistics per process). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10 2. . . . . . . . . . . .software manipulation . . . . . . . . . . . . . . . . . . . . . . . .5 2. . .2 2. . . . . 102 4 Id:0900d805806444c9 DN0479352 Issue 4-2 . . . . . . . . . . . . . . . . . . . . . . .11. . . . . . . . . . . .7 2. 55 abb (analyze black box) . 72 reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 dbtsrnw (display the radio network configuration for a particular BTS). .9 2. . . . . . . . .6 2. . . . . . . . . . . . . . . 49 dtu (display timer statistics per unit) . . . . . . . . . .5. . . . . . . . 43 dbu (display buffers per unit) . . . . . . . . . . . . . . . 81 ifconfig.1 2.9. . .PCU2 Service Terminal Commands 2. . . . . . . . . . . .3 2. . . . . . . . 77 dimm (display message monitoring configuration) . . . . . . . . . . . . . . . . . . . . . . . . . . .11 2. . . . . . . . . . . . . . .8. . . . . . . . . . . .8 2. . . . .logging . . . . . . . . . .7 2. . . . . . .1 2. . . . . . 69 dlf (display the logger feature) . . . . . .7. . . . .1 2.5 2. . . . . . . . . . . . . .11. . . . . . . . . . . . . . . . . .3 2. 55 Utilities . .5 2. . . . . . . . . .10. . . . . . . . . . . . . . . . . 51 dsco (display statistics for a specific counter). . . . . . . . . . . . . . . . .7. . . . . . . . . . . . . . . . . . . . . . . . . . . 92 dsegrnw (display the radio network configuration for a particular segment) 94 TBF information commands . . . . . . . . . . . . . . . . . . . . . .5. . .6. 83 ping . . . . . . . . . . . . . 95 dsegtbf (display TBF allocation for a particular segment) . . 71 Utilities . .3 2. . . . .10.4 2. . . . . . . .9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 slf (set the logger feature) . . . . . . . . . . .3 2. . . . . . . . . . . . . . . . . . .6 2.12. . . . . . . . . . . . . . .4 2. . . . .5. . . 54 rsco (reset statistics for a specific counter) . . . . . . . . . . . . .8 2. . . . . . . . . . . . . . . . . . . . . . . . . 62 Utilities . . . . . . . 72 ssv (show the software version) . . . 52 rsca (reset statistics counter for specific category) . . .6 2. . . . . . . . . . .3 2. . . . . . . . . . . . . . . . .9. . . . . 100 dtsltbf (display the TBF information specific to identified TSL) . . . .2 2. . . . . 98 dtfitbf (display the TBF information specific to identified TFI) . . . . 73 Utilities . . . .5. . . . . . . . . .7 2. . . . 87 ping6 .10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7. . . . 74 emm (enable message monitoring) . . . . . .9 2. . .3 2. . . . . . . . . . . . . . .12 2. . . . . . . . . . . . . . .3 2. . .8. . . . . . . . . . . . . . . . .2 2. . . . . . . . . . . . . . . . . . . . . . . . .10. . . . . . . . . . . . . . . . . . . . . .5. . . . . . . 78 damm (disable all message monitoring) . . . 74 dmm (disable message monitoring) . .1 2. . . . . . 50 dsca (display statistics counter for specific category) . . . . . . . . manipulation. . .2 2. . . . . . . . .6 2. . . . . . . . . . . . . . . .1 2. . . . . . . .11. . . . .2 2. . . . 70 efl (enable logging to file) . . . . .2 2. . . . . . . . . . . . .4 2. . . . . . . . . . . .9. . . 46 dbs (display buffer statistics of particular size) . . . . . . . . . . . . . . . .5. . . . . . . . . . 64 sll (set the log level) . . . . . . . . . . . . . . . . . 73 ubs (upgrade boot software) . . . . . . . . .8. . . . . . . . . . . . . . . .12. . . . . . .Black Box . . . . 89 Radio network–related commands . . . . . . . . . . . . .1 2. . 47 dtp (display timer statistics per process) . .7. . . . 64 ssl (set the software layer) . . .6. . . . . 68 dld (display the log details) . . .

15 2. . . . . .19 2. .22. 123 dnccrms (display the NCCR data of mobile stations specified) . . . . 116 eupl (enable user plane data logging) . . . 129 ddimsi (display dedicated IMSI) . . .1 2. . . . . . . . . . . . . . . . . .2 2. . . . . . . . . . . . . . .2 2. . . . . . . . . .18. . . . . . .18 2. . .1 dpcutbf (display number of UL and DL TBFs for all active segments in the PCU) . . . . 131 DN0479352 Issue 4-2 Id:0900d805806444c9 5 . . . . . . . . . . . 114 User plane monitoring–related commands . . . . . . . . . . . . . . . . . .13. . . . . . . . .13 2. . . . . . . . . . . 122 NCCR commands . . . . .13. . . . . . . . . . . .14. . . . . . . 123 dnc2ms (display the number of mobile stations in NC2 mode) . . . . . . .19. . . . . . . . . . . . .15. . . . . . . . . .21. 125 dpsinacc (display the neighbour cell SI or PSI messages) . . . . . 121 tcstatus (display list of authenticated IP for telnet connections) . 114 eup (enable user plane monitoring) . .22. . . . . . .14. . . .3 2. . . . . . . . . . . . . .14. . . . . .21. . . .17 2. .3 2. . . . 125 dsinacc (display the SI messages of given segment) . . . . . 111 esm (enable subscriber monitoring). . . . . . . . . . . . . . . . . . . .16 2. . . . .16. . . . . . . . . .3 2. . .14 2. . . . . . .14.6 2. . . . . . 106 dgb (display Gb configuration) . . . . . . . . . . . . . . . . . . . . . . . . . 104 Gb–related commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15. . . . . . . . . . . . 117 dupl (disable user plane data logging) . . . . . . . . . . . . . . . . . . .PCU2 Service Terminal Commands 2. . . . . . . .1 2. . 109 digbm (display Gb monitoring) . . . .20. . . . .13. . . . . . . . . . . . . . . . . .15. . . . . . . . . .23 2. . . .2 2. . . . . . . . . . . 127 dgbipnsei (display the information about certain NSE) . . . . . . . . .1 2. .2 2. . . . . . .14. . 110 dgbl (disable Gb data logging) . . .1 2. . . . . . . .12. . . . . . . . . . . . . . . 128 dgbipnsvc (display the information about certain NSVC). . . . . . . . 118 Frame relay–related commands . . . . . . . . . . . . . . .4 2. . . . . . . . . . . . . . . . . . .13. . . . . . . 118 General category commands.2 2.15. . .20 2. . . . . . . . . . .15. . . . . . . . . . . . . . . . . 118 dfc (display frame relay configuration) . . . . . . . 106 egbm (enable Gb monitoring) . . . . . . . . . . . . . . . . . . . . .3 2. . . . . 113 dsml (disable subscriber monitoring data logging). . . . . . 109 egbl (enable Gb data logging) . . . . . .19. . . . . . . . . . . . . . . . .5 2. . . . . . . . . . . . . . . . . . . . .3 2.18. . . . . . . . . . . . . . . . .1 2. . . . . . . . . 107 dgbm (disable Gb monitoring) . . . . . . . . . .4 2. . . .1 2. . . . . . . . . . . . . . . . . . . .3 2. . . . . . . . . . . . . . . . .1 2. . . . . . . . . . . . . . . . . . . . . . . 120 Telnet server administration commands .22 2. . . . . . . . . 120 etc (enable telnet for specified IP address or for all IPs) . . .18. . . . . . . .1 2. . . . . . . . . . . . . . .20. . . . . . 121 dtc (disable telnet for specified IP address or for all IPs). .13. . . . . . . . . . . . . . . . 116 diup (display user plane monitoring) . . . 120 dpt (display system level trace pending table) . . . . .2 2. . . . . . 123 dnc0ms (display number of mobile stations in NC0 mode) . . . . . . . . . . . . . . . . . . . . . . . 112 dism (display subscriber monitoring) . . . . . . . . . .5 2. . . . . . . . . . . . . . . . . . . . . 126 Gb over IP commands . . . . . . .2 2. . .19. . . . . . . . . . . . . . . . . .21 2. . . . . . . . . 129 didtms (display internal DTM counters) . . . . . . . .1 2. . . . 124 NACC commands . . . . . . . . . . . . . . . . . . . . . 111 Subscriber monitoring–related commands . . . . . . . . 128 DTM commands. . . . . . . . . . 131 Service terminal commands for DSP and PCM allocation information 131 ddspinfo (display DSP information) . . .5 2. . . . . . . . . . . .1 2. . . . . . . . . . .17. . . .21. . . . . . . . . . . . . .2 2. . . . . . . . . . . . . . . . . . . . 125 dnacc (display the NACC related neighbour cell configuration data). . .5 2. . . . . . . .22. . . . . . . . . . . . . . . . . . . . . . . . . . . . 130 ddtmimsi (delete DTM IMSI) . . .3 2. . . . . . . . . . . . . . 113 esml (enable subscriber monitoring data logging) . . .23. . . . .3 2. . . . . . . . . . . . . . 111 dsm (disable subscriber monitoring) . . . .4 2. . . .13. . . .20. . . . . . . . . . 115 dup (disable user plane monitoring). . . . . . 127 dgbipbvc (display the information about certain BVC) . . . . . . . . . . . . .

. . . . . . . 135 ddaptrxinfo (display TRX information for the specified DAP) . . .23. . .23. . . . . 142 Bootup phases and traces . . . . . . . 138 Cell monitoring commands . . . . . .1 2. 134 ddapinfo (display EDAP information) .23. . . .2 2. . . .23. . . . . . .5 2. .24. . . . .26 2.3 2. . . . . . . . . . . . . .23. . . . . . . . . . . . . . . . . . . . . . . . . .25. . . . . .1 2. . . . . . . . . . . . . .23. . . 151 Error code debugging information for abb and doe command output. . . . . . . . . .8 2. . . . . . 152 Error codes interpretation in case 'user_called' is 'false' (value 0) . . . . . . . . . . . . . . . . . . . .25. . . . .25. . . . . . . . . . . . . . .PCU2 Service Terminal Commands 2. . . . . . . . 142 Application IDs for commands . . . . . . . . . . . .7 2. . . 136 dstslinfo (display sub-TSL info for the PCU-PCM line) . . . . . .6 2.25 2. . . . . . . . . . . . .4 2. . . . . . . . . . . . . . . . . . . .3 2. . 139 dcem (display cell monitoring data) . . .27 dpcminfo (display PCU-PCM information) . . . 134 dabmtrxinfo (display the TRX information for the BTS in the specified segment). . . . . . 132 dpcmdapinfo (display PCU-PCM information for the specified EDAP) . . . .24 2. . . . . . . .23. . . . . . . . .25. . . . 154 Error codes interpretation in case 'user_called' is 'true' (value 1) . . . . . . . . . . . . . . . .4 2. . . . . . . . . . . 172 6 Id:0900d805806444c9 DN0479352 Issue 4-2 . . 139 Service terminal command–related information . . . . . . . . . . . . 142 Commands in continuous mode . . . .2 2. 137 dgpinfo (display guard period information per DAP) . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . 10 Error code decoding . . . . . . . . . . . . . . . . . . . . . 153 DN0479352 Issue 4-2 Id:0900d805806444c9 7 .PCU2 Service Terminal Commands List of Figures Figure 1 Figure 2 PCU2 service terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

PCU2 Service Terminal Commands 8 Id:0900d805806444c9 DN0479352 Issue 4-2 .

dnacc. dbtsrnw. additional information on PCU2 boot upgrade instructions has been added. dsegrnw. The following commands have been removed: dsegtbfc. rsca. The examples and execution printouts of the following commands have been updated to include changes due to Downlink Dual Carrier: dtrxrnw. dbtstbfc. The execution printouts of the dai and ssv commands have been updated. and dcem. dsco. and the text about the function of dsinacc has been modified. ddspinfo. and dtrxtbfc. 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 latest document issue contains all changes made to previous issues. dtrxtbf. dtfitbf. dpcutbf. • • • • • • DN0479352 Issue 4-2 Id:0900d80580623ab7 9 . Changes made between issues 4-2 and 4-1 Information on the categories 72 and 79 has been added to subsection dsca (display statistics counter for specific category) in chapter Service terminal commands. and rsco. information on the PQIII controller processor has been added.PCU2 Service Terminal Commands Summary of changes Summary of changes Changes between document issues are cumulative. dsegtbf. and dsinacc. Changes made between issues 4-1 and 4-0 In the Service terminal commands chapter. Segment ID information has been revised in the following commands: dnccrms. Changes made between issues 4-0 and 3-1 In the Overview of PCU2 service terminal chapter. The execution printout of the ps command has been updated to include new processes due to the PCU2-E. Counter information in examples and execution printouts has been revised in the following statistics commands: dsca. dtsltbf. Section Application IDs for commands has been updated. Therefore.

Help on the PCU2 commands can be obtained by typing: • ? <command> • help <command> 10 Id:0900d80580623aba DN0479352 Issue 4-2 . Commands to the DSPs are sent via the controller processor. or via the MML terminal by establishing a remote service terminal session using the appropriate MML command. while the PCU2-E unit uses PQIII instead of PQII. The controller processor of the PCU2-D and PCU2-U units is PQII. The digital signal processors (DSPs) do not have a direct service terminal interface. to maintain backward compatibility. via an Ethernet interface using the Telnet protocol. You can start a service terminal session either on a service terminal physically connected to a computer unit. PQIII is still referred to as PQII in all the service terminal command parameters. It is a specialist tool used in monitoring the system as well as in fault investigations. 1.1 Service terminal in PCU2 In the PCU2. the service terminal functionality is based on operating system embedded (OSE) shell running on a controller processor. However. note that: • • The parameters are separated via a 'space' separator and commands are considered to be complete and interpreted when the Enter key is pressed.Overview of PCU2 service terminal PCU2 Service Terminal Commands 1 Overview of PCU2 service terminal Service terminal is a visual display terminal connected to the PCU2 through a serial or an Ethernet interface. The PCU2 service terminal operating environment is presented in the figure below: BSC OMU Ethernet MML or service terminal session Telnet client BCSU PCU2 RS232 VDU or terminal emulator Figure 1 PCU2 service terminal 1. When using the PCU2 service terminal commands.2 Special characteristics of service terminal commands PCU2 service terminal commands are different from the MML commands. examples. and execution printouts in Service terminal commands.

which indicates that the service terminal is an OSE-based service terminal. the syntax of remove command is remove <filename> This command must be executed as: remove log_file_gb. The parameters are to be interpreted as explained below: Explanation Specifies that the parameter is optional and its value not mandatory to specify.3 Service terminal prompt Service terminal prompt denotes the BCSU and the PCU ID along with the suffix 'OSE'. Detailed help on each command and its syntax can be obtained by typing 'help <command name>'. For example.PCU2 Service Terminal Commands Overview of PCU2 service terminal • • • help The commands are case sensitive. DN0479352 Issue 4-2 Id:0900d80580623aba 11 . For example. For example. as explained in the command description. the syntax of help command is help/? [<command>] This command can be executed as: help ps or help Parameter syntax [<parameter>] {parameter} Specifies that the parameter is conditionally optional and needs to be specified only under a certain condition. 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. The commands are entered using lower case letters. Some of the commands do not require parameters to be passed on to them. This is to enable to distinguish between the Chorus-based and the OSE-based service terminal.log but not remove 1.

the following message is displayed on the terminal. the service terminal prompt will change to indicate this. The prompt will be BCSU/0/PCU/0/OSE/SML> /L /ML /GBL /UPL /SML The service terminal prompt can be a combination of any of the suffixes specified above. The prompt will be BCSU/0/PCU/0/OSE/UPL> If the 'esml' command has been run. the service terminal logging mode has been switched on. the prompt will be BCSU/0/PCU/0/OSE/C/ML> 1. the service terminal subscriber monitoring logging mode has been switched ON. XX is the BSCU index and YY is the PCU index. the service terminal user plane monitoring logging mode has been switched ON. The prompt will be BCSU/0/PCU/0/OSE/C> If the 'esl' command has been run. the service terminal message monitoring logging mode has been switched on. The prompt is BCSU/0/PCU/0/OSE/L> If the 'emml' command has been run. The prompt will be BCSU/0/PCU/0/OSE/ML> If the 'egbl' command has been run. 12 Id:0900d80580623aba DN0479352 Issue 4-2 .4 Service terminal login delays In case there is a delay of less than 60 seconds during the login via Telnet. if you have enabled both the continuous mode and the message monitoring logging mode. Possible suffixes /C Explanation If the continuous mode is enabled.PLEASE WAIT***/ Connection to host lost. The prompt will be BCSU/0/PCU/0/OSE/GBL> If the 'eupl' command has been run.Overview of PCU2 service terminal PCU2 Service Terminal Commands Prompt BCSU/XX/PCU/YY/OSE> Explanation The basic service terminal prompt denotes the BSCU and the PCU index. the service terminal Gb interface monitoring logging mode has been switched on. For example. login: qwe Password: /*** User Authorization Failure ***/ login: qwe Password: /*** User Authorization Failure ***/ login: qwe Password: /*** User Authorization Failure ***/ /***DELAY OF 5 SECONDS APPLIED.

34>***/ Connection to host lost. the following message is displayed on the terminal. C:\> login: asd Password: /*** User Authorization Failure ***/ /***DELAY APPLIED. or via the BSC MML. see Information Security. which displays the date and a timestamp. This enables you to do offline analysis especially in commands related to statistics measurement.PLEASE WAIT UNTIL <15. You need a username and a password for the access.----> Command XXX executed on [dd/mm/yyyy Hr:Min:Sec:Micro-Seconds] <---. The Ethernet interface is supported over IPv4. 1. The sections below highlight how to access the service terminal through the various interfaces available.PCU2 Service Terminal Commands Overview of PCU2 service terminal In case there is a delay of more than 60 seconds during the login via Telnet. The access requires that you have a Telnet client from the source machine.5 Service terminal connectivity The service terminal can be accessed through a serial interface. the header format is: ----------------------------------------------------------. you need to configure a connection in the software to choose the correct COM port.6 Service terminal commands output All the service terminal command execution printouts contain a header. Ethernet interface. You need a username and a password for the access. For more information. 1. when the command ace is executed. Remote session to the PCU on MML terminal For instructions on starting a remote session to the PCU on MML terminal.---------------------------------------------------------- XXX indicates the command name. The printouts are the same for serial sessions. Access through serial interface The service terminal can be accessed locally through the serial interface. the Ethernet connection is disabled. The format of the header is: ----------------------------------------------------------. For example.---------------------------------------------------------- DN0479352 Issue 4-2 Id:0900d80580623aba 13 . IPv6 is not supported in the service terminal interface. see Starting a service terminal session in Service Terminal Essentials.----> Command ace executed on [1/1/2004 0:0:5:260001] <---. As a default. You can enable it with the etc command. If you are using a PC software environment and a third-party software. Access through Ethernet interface The service terminal can be accessed through the Ethernet interface.

MAY CAUSE DAMAGE BCSU-xx. WELCOME TO IMS GW SERVICE TERMINAL DIALOGUE. 2003-09-26 UNAUTHORIZED USAGE 14 Id:0900d80580623aba DN0479352 Issue 4-2 . In the welcome message. the characters 'xx' are the BCSU ID and the character 'x' is the PCU ID. 10:06:10 IMS GW SERVICE TERMINAL IS A SPECIALIST TOOL.Overview of PCU2 service terminal PCU2 Service Terminal Commands 1.7 Disclaimer and welcome note The following disclaimer and welcome notes are displayed when you log into a plug-in unit through the service terminal. PCU-x.

you will not get any traces/logs on the screen.PCU2 Service Terminal Commands Service terminal commands 2 Service terminal commands The service terminal command examples and execution printouts apply to all PCU2 variants.. 2.2 esd (enable system dumps) Function With this command you enable system dumps. Syntax esd Examples 1. when you log into the plugin unit (PIU) through the service terminal. Exit the service terminal session.1. Syntax exit Examples 1.1 exit Function With this command you exit the current session and return to the login prompt. exit Execution printouts BCSU/0/PCU/0/OSE>exit ---------------------------------------------------------------> Command exit executed on [1/1/2004 0:0:43:569039] <--------------------------------------------------------------exiting. 2. DN0479352 Issue 4-2 Id:0900d805806444bc 15 . By default..1. unless otherwise specified. This functionality has been added so that you can do the desired operation and not be disturbed by frequent traces. username: 2. esd Execution printouts BCSU/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.1 Service terminal general purpose commands The commands described below relate to the PCU2 as a complete system. Enable system dumps on the existing service terminal session.

Display the operating system error logs for the DSP processor. These error logs are maintained internally by the service terminal and will not survive in case of a PIU reboot.3 dsd (disable system dumps) Function With this command you disable system dumps. The error logs for the DSP processors are maintained on a global level. Display the operating system error logs for the PQII processor.1. Syntax doe <processor type> Parameter explanations processor type With this parameter you specify the processor type on which the application is residing. the output of the logging and traces messages will not appear on the screen. the value is '1'. see section Error code debugging information for abb and doe command output. Syntax dsd Examples 1. 16 Id:0900d805806444bc DN0479352 Issue 4-2 . dsd Execution printouts BCSU/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. not per DSP. The allowed values are 'pq2' and 'dsp'.4 doe (display operating system error logs) Function With this command you can examine the operating system error logs in the PCU2 system.Service terminal commands PCU2 Service Terminal Commands 2. The last 20 error logs occurred are displayed for user analysis. After you have given this command. To debug the error code. Examples 1.1. Disable system dumps on the existing service terminal session. and otherwise '0'. doe pq2 2. doe dsp Execution printouts The parameters used in the execution printout: User called Specifies if the error was a result of application calling or kernel calling. The full form of this command is display operating system error logs (doe). In case of application calling.

Process name is a string showing the name of the process or block. Line is an integer containing the source code line from which the current system call was issued.c Line : 37 2. Line 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 : 0x00110031 Extra : 0x073aff34 Process Name : errhnd Process ID : 0x00030042 File : xyz. Syntax dpi DN0479352 Issue 4-2 Id:0900d805806444bc 17 . Line is 0 if no line and file information is available. In the current BSC hardware. it always specifies the value '1' for all the parameters. slot.1.c Line : 31 User called : 0x1 Error code : 0x00000001 Extra : 0x00000000 Process Name : errhnd Process ID : 0x00050042 File : xyz. The command displays the cartridge.5 dpi (display PCU2 PIU information) Function With this command you display the hardware-related information. and section of the PIU.PCU2 Service Terminal Commands Service terminal commands Error code Extra Process name Process ID File Specifies the error code used by the user/kernel to indicate which error caused a call to the error handler. Specifies the extra information used in debugging the error code. This field is invalid if the line is 0. It specifies the process name of the application/platform processes. The full form of this command is display PCU2 PIU hardware information (dpi). Line and file information is available only if the PCU2 software was compiled with the debug option. Specifies the process ID. File is a string showing the file name from which the current system call was issued. Line and file information is available only if the PCU2 software was compiled with the debug option.

Service terminal commands PCU2 Service Terminal Commands Examples 1. These statistics may help you in debug- 18 Id:0900d805806444bc DN0479352 Issue 4-2 .7 eeqm (enable event queue monitoring) Function With this command you enable the event queue monitoring and will then be able to execute the command deqs to see the results.1. Syntax dem Examples 1. Display the PCU2 PIU information.1. Display the elapsed milliseconds since the last system restart. dpi Execution printouts BCSU/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. The full form of this command is display elapsed milliseconds (dem). dem Execution printouts BCSU/0/PCU/0/OSE>dem --------------------------------------------> Command dem executed on [1/1/2004 0:5:19:330001] <-------------------------------------------Milliseconds elapsed since system restart [2350100] ========================================================== 2.6 dem (display elapsed milliseconds) Function With this command you display the elapsed milliseconds since the last system restart.

deqs DN0479352 Issue 4-2 Id:0900d805806444bc 19 .1.9 deqs (display event queue statistics) Function With this command you display useful statistics to assist you in debugging process communication-related problems.8 deqm (disable event queue monitoring) Function With this command you disable the event queue monitoring. The full form of this command is enable event queue monitoring (eeqm). Syntax eeqm Examples 1. deqm Execution printouts BCSU/0/PCU/0/OSE>deqm ---------------------------------------------------------------> Command deqm executed on [1/1/2004 0:6:10:520001] <--------------------------------------------------------------Event queue monitoring disabled 2. Syntax deqs Examples 1.1. The full form of this command is display event queue statistics (deqs). Disable the event queue monitoring. Syntax deqm Examples 1.PCU2 Service Terminal Commands Service terminal commands ging the process communication-related problems. Display the event queue statistics. eeqm Execution printouts BCSU/0/PCU/0/OSE>eeqm ---------------------------------------------------------------> Command eeqm executed on [1/1/2004 0:5:35:200001] <--------------------------------------------------------------Event queue monitoring enabled 2. The full form of this command is disable event queue monitoring (deqm). Enable the event queue monitoring.

Service terminal commands PCU2 Service Terminal Commands Execution printouts BCSU/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 20 Id:0900d805806444bc DN0479352 Issue 4-2 .

certain commands you execute will run continuously after every specified number of seconds. Examples 1.10 seconds. Otherwise PCU2's internal service terminal resources may get exhausted. The suggested value is between 3 . Enable the continuous mode with a refresh interval of 6 seconds. You should always disable the continuous mode with the dcm command before closing the service terminal session. You can stop the command execution by executing 'Control-C' characters. 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 the continuous mode is set.PCU2 Service Terminal Commands Service terminal commands 42 0 0 0 0 -------------------------------------------------------------------------------- 2. The service terminal prompt is changed when the continuous mode is set. When this mode is enabled. Syntax ecm <refresh time in seconds> Parameter explanations refresh time in seconds With this parameter you specify the refresh time of the command. the commands are enabled in continuous mode for the PQII processor only.1. The continuous mode can be set individually for each of the connected service terminal sessions with the same or different refresh intervals. Enable the continuous mode with a refresh interval of 3 seconds. ecm 6 Execution printouts BCSU/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 DN0479352 Issue 4-2 Id:0900d805806444bc 21 . ecm 3 2.10 ecm (enable continuous mode) Function With this command you set the service terminal commands to continuous mode.

Syntax dbl 22 Id:0900d805806444bc DN0479352 Issue 4-2 .12 dbl (display bootup log) Function With this command you can examine the bootup logs after a successful restart. Syntax dcm Examples 1.1. See section Commands in continuous mode for a list of the commands that are disabled in the continuous mode when this command is executed. The full form of this command is display the bootup logs (dbl). Disable the continuous mode. which may help you in checking the state of the system. dcm Execution printouts BCSU/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.Service terminal commands PCU2 Service Terminal Commands -------------------------------BCSU/0/PCU/0/OSE> 2.1.11 dcm (disable continuous mode) Function With this command you disable the continuous mode of the service terminal.

Installing FastEthernet Driver. Post Stage II diagnostics completed. RAM based initialization completed OSE Started. address lines and SDRAM memory walkthrough) and watchdog diagnostics completed. Phy add=0x32.. Starting Ethernet and serial Diagnostics POST Stage II Tests. Display the bootup logs. dbl Execution printouts Execution 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.hex has been downloaded in DSP 0 DN0479352 Issue 4-2 Id:0900d805806444bc 23 . IMSGW_CM: Executing the Entry Point function OF CM PCI: Sending Host Intr Starting PIU index=0x6. Bootup Image Started. Broadcast=0x7f Log PIU Index= 0x7 Component Manager(RESTART State) : Received WORKING state from BSC File /ram/bin/dsp/IGWDGDSD. PIU type=0x3d9. Starting Boot Diagnostics POST Stage II Tests. Installing SMCUART Driver.PCU2 Service Terminal Commands Service terminal commands Examples 1. Installing FastEthernet Driver. Post Stage II diagnostics completed.. Diagnostics HDLC Loopback Test Interface 1 result = PASSED. ============================================================ IMSGW Boot image version : '6.33-0' built on Aug 21 2006 Power-On-Self-Tests : SDL BOOTLOADER: Reset Reason HARD RESET SDL BOOTLOADER: Downloading image For Section 0. ============================================================ Welcome to the PQII Boot Loader. Creating WatchDog Clear Process. PQII Data-Cache test result : PASSED Starting Component Manager . Creating WatchDog Clear Process. Installing SMCUART Driver. Initializing PCM MUX Settings Starting Ethernet and Internal PQ2 PCM Diagnostics POST Stage II Tests. SDL BOOTLOADER: Transfering control to image entry point at 0x01e00004 RAM Image Started. Diagnostics Ethernet Interface 1 test result = PASSED.. Diagnostics Ethernet Interface 2 test result = PASSED. Diagnostics Serial Interface test result = PASSED..

hex has been downloaded in DSP 2 File /ram/bin/dsp/IGWDGDSD.hex has been downloaded in DSP 6 File /ram/bin/dsp/IGWDGDSD.hex has been downloaded in DSP 3 File /ram/bin/dsp/IGWDGDSD.hex has been downloaded in DSP 0 DIAGNOSTIC RESULTS OF DSP1 -----------------------------------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 1 DIAGNOSTIC RESULTS OF DSP2 -----------------------------------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 3 24 Id:0900d805806444bc DN0479352 Issue 4-2 .hex has been downloaded in DSP 7 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 1 File /ram/bin/dsp/IGWDGDSD.hex has been downloaded in DSP 5 File /ram/bin/dsp/IGWDGDSD.hex has been downloaded in DSP 2 DIAGNOSTIC RESULTS OF DSP3 -----------------------------------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 4 File /ram/bin/dsp/IGWDGDSD.Service terminal commands PCU2 Service Terminal Commands File /ram/bin/dsp/IGWDGDSD.

hex has been downloaded in DSP 4 DIAGNOSTIC RESULTS OF DSP5 -----------------------------------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 File /ram/bin/dsp/IGWMNDSD.hex has been downloaded in DSP 7 File /ram/bin/dsp/IGWMNDSD.PCU2 Service Terminal Commands Service terminal commands DIAGNOSTIC RESULTS OF DSP4 -----------------------------------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 1 File /ram/bin/dsp/IGWMNDSD.hex has been downloaded in DSP 2 File /ram/bin/dsp/IGWMNDSD.hex has been downloaded in DSP 6 DIAGNOSTIC RESULTS OF DSP7 -----------------------------------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 3 File /ram/bin/dsp/IGWMNDSD.hex has been downloaded in DSP 5 DIAGNOSTIC RESULTS OF DSP6 -----------------------------------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 5 File /ram/bin/dsp/IGWMNDSD.hex has been downloaded in DSP 6 DN0479352 Issue 4-2 Id:0900d805806444bc 25 .hex has been downloaded in DSP 4 File /ram/bin/dsp/IGWMNDSD.

..hex has been downloaded in DSP 1 File /ram/bin/dsp/IGWDGDSE.Mon Feb 9 09:58:17 2009 File /ram/bin/dsp/IGWDGDSE.hex has been downloaded in DSP 2 File /ram/bin/dsp/IGWDGDSE.hex has been downloaded in DSP 3 File /ram/bin/dsp/IGWDGDSE. PASSED.13-0' built on Dec 19 2008 Power-On-Self-Tests : SDL BOOTLOADER: Reset Reason HARD RESET SDL BOOTLOADER: Downloading image For Section 0.. Broadcast=0x7f Log PIU Index= 0x5 Component Manager(RESTART State) : Received WORKING state from BSC IMSGW_CM: Time Received from BSC .hex has been downloaded in DSP 0 File /ram/bin/dsp/IGWDGDSE.. PIU type=0x3e3.hex has been downloaded in DSP 4 File /ram/bin/dsp/IGWDGDSE. Phy add=0x32. SDL BOOTLOADER: Transferring control to image entry point at 0x10000000 Diagnostics HDLC Loopback Test Interface 1 result = RAM based initialization completed OSE Started.hex has been downloaded in DSP 7 BCSU/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.hex has been downloaded in DSP 5 26 Id:0900d805806444bc DN0479352 Issue 4-2 . IMSGW_CM: Executing the Entry Point function OF CM PCI: Sending Host Intr Starting PIU index=0x4.Service terminal commands PCU2 Service Terminal Commands File /ram/bin/dsp/IGWMNDSD. Starting Component Manager . ============================================================ IMSGW Boot image version : '1.

PCU2 Service Terminal Commands Service terminal commands 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 DIAGNOSTIC RESULTS OF DSP1 ---------------------------------------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 3 DN0479352 Issue 4-2 Id:0900d805806444bc 27 .hex has been downloaded in DSP 1 DIAGNOSTIC RESULTS OF DSP2 ---------------------------------------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 2 DIAGNOSTIC RESULTS OF DSP3 ---------------------------------------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 3 File /ram/bin/dsp/IGWMNDSE.hex has been downloaded in DSP 5 File /ram/bin/dsp/IGWMNDSE.hex has been downloaded in DSP 5 BCSU/32/PCU/4/OSE> 2.13 dai (display application IDs) Function With 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). Syntax dai 28 Id:0900d805806444bc DN0479352 Issue 4-2 .hex has been downloaded in DSP 0 File /ram/bin/dsp/IGWMNDSE.hex has been downloaded in DSP 1 File /ram/bin/dsp/IGWMNDSE.hex has been downloaded in DSP 4 File /ram/bin/dsp/IGWMNDSE.hex has been downloaded in DSP 2 File /ram/bin/dsp/IGWMNDSE.1.hex has been downloaded in DSP 4 DIAGNOSTIC RESULTS OF DSP5 ---------------------------------------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.Service terminal commands PCU2 Service Terminal Commands DIAGNOSTIC RESULTS OF DSP4 ---------------------------------------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.

PCU2 Service Terminal Commands Service terminal commands Examples 1. Display the application IDs. dai Execution printouts BCSU/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) 1 Inter Process Communication(IPC) 2 Performance management System(PMS) 3 ******************************************************** Platform Component IDs for PQII ******************************************************** Software Download(SDL) 4 Logger(LOGGER) 5 Alarm Server(ARS) 6 DSP Manager(DSPM) 7 System Monitor(SYSMON) 8 Diagnostics(DIAG) 9 DSP Resource Manager(DSPRM) 10 Service Terminal Agent(STA) 11 ******************************************************** Displaying Application Component IDs for PQII ******************************************************** 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 IBNACC 33 ******************************************************** Displaying Dynamic Application IDs for PQII ******************************************************** DN0479352 Issue 4-2 Id:0900d805806444bc 29 .

14 daa (display active alarms) Function With this command you display the list of alarms currently active in the PCU2.<set sent/unsent>.<reset/not reset>.<set acked/unacked>.Service terminal commands PCU2 Service Terminal Commands Dynamic Application Begin 34 Dynamic Application End 46 ******************************************************** Displaying Application Component IDs for DSP ******************************************************** Quality Control(QC) 4 ULQC 29 DLQC 30 DSPA 6 DSP CPU MON 24 INTER DSPA 25 SERIAL DSPA 26 DSPA LOGGER 28 Data Transfer Task(DTT) 5 ULRLC 31 DLRLC 32 PFD 33 ULSCH 34 DLSCH 35 Inter DSP Communication(COM) 27 BCSU/32/PCU/4/OSE> 2. Display the alarms currently active in the system. daa Execution printouts Output syntax: <s.<reset sent/unsent>.1.<set/not set>.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 raised the obs(hex dump)> <setting family> <setting time(mm/dd/yyyy hr:mi:ss:hundredth of a second> current state: <not set>. Syntax daa Examples 1. The full form of this command is display active alarms (daa).<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) 30 Id:0900d805806444bc DN0479352 Issue 4-2 .

When the service terminal program opens the QWERTY file.1.PCU2 Service Terminal Commands Service terminal commands =================================================== < 1>.<not reset>. the command displays the terminal commands for the standard inputs with their assigned control keys. Syntax uad Examples 1. Syntax keys Examples 1.15 uad (update authentication data) Function With this command you reload the Service Terminal Authentication QWERTY file (QWERTYGX. <3250> <6B> <1> <18> <2F22> <5143> 28/10/2004 18:26:32:59 current state:<set>.<set sent>. it first calculates the checksum of the file data and compares it with the checksum value in the header of the QWERTY file.<not reset>.1 keys Function With this command you display the terminal keys configured in the system. keys DN0479352 Issue 4-2 Id:0900d805806444bc 31 .2 Operating system commands This section contains the commands which apply to the general category of the service terminal. uad Execution printouts ---------------------------------------------------------------> Command uad executed on [1/1/1970 0:3:9:310001] <--------------------------------------------------------------- 2. Display the existing configured keys.<set sent>. Without any parameters.<set acked>. 2. The file data is corrupted if the checksum does not match.<reset not sent>.<reset not acked> <100000> < 2>.2.IMG) from the OMU's disk to the unit's memory when the QWERTY file is corrupted. Reload the QWERTY file.<set acked>.<reset not acked> <42 0> 2.<reset not sent>. <3053> <6B> <1> <1B> <2F22> <5143> 1/1/04 0:0:8:69 current state:<set>.

Service terminal commands

PCU2 Service Terminal Commands

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

2.2.2

help/?
Function With this command you can print the syntax and a short explanation for each specified command. '?' is an alias for help. Syntax help/? [<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
Function With this command you display the date of the system. The date is displayed in the format 'yyyy-Month-dd'. Syntax date Examples 1. Display the current date of the system. date Execution printouts

BCSU/0/PCU/0/OSE>date 2004-January-1

32

Id:0900d805806444bc

DN0479352 Issue 4-2

PCU2 Service Terminal Commands

Service terminal commands

2.2.4

time
Function With this command you print the current time to the standard output. The time is displayed in the format 'hours:minutes:seconds.microseconds'. Syntax time Examples 1. Display the current time of the system. time Execution printouts

BCSU/0/PCU/0/OSE>time 0:41:57.36

2.2.5

ver
Function With this command you print the version of the OSE kernel and SHELL to the standard output. Syntax ver Examples 1. Display the OSE OS version. ver Execution printouts

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

2.2.6

ls
Function With this command you list the specified files or the files and subdirectories in the directory where the command is executed. Two option flags are possible. Syntax ls [<options>][<dirname> ...] Parameter explanations –l This parameter specifies a long listing with information such as access modes, ownership, size, and modification date. –a

DN0479352 Issue 4-2

Id:0900d805806444bc

33

Service terminal commands

PCU2 Service Terminal Commands

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 printouts BCSU/0/PCU/0/OSE>ls Directory '/ram/' dump.dat IGWBTDSD.hex IGWDGDSD.hex IGWMNDSD.hex log_file.txt etc/

2.2.7

cat
Function With 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. Syntax cat [<filename>] Examples 1. Display the contents of an already existing file named 'abc.txt' on the screen. cat abc.txt Execution printouts

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

2.2.8

rm
Function With this command you remove (delete) the specified files. The file(s) must not be open. Syntax rm [f] <filename> ... Examples 1. Remove a file named 'log_file.txt'. rm log_file.txt Execution printouts If any process has opened the file, it gives the following message:

34

Id:0900d805806444bc

DN0479352 Issue 4-2

txt' to '/ram/st_logs.PCU2 Service Terminal Commands Service terminal commands BCSU/0/PCU/0/OSE>rm log_file. In case the logs exceed the maximum file size.txt': Permission denied. Parameter explanations filename The name of the file in which the logs are to be captured. Use this command with care and only when necessary. and no more logging is done.3 Service terminal logging to file commands This section contains the commands which are related to logging to the file facilities provided. the log capture mode is automatically turned off. 2. 2.1 esl (enable ST logging) Function With this command you log the output of all the PCU2 commands (except the OSE commands) to a file. ! Running this command may affect the system performance. Enable service terminal logging to a file named 'st_logs. esl st_logs. You must execute the dsl command before viewing the generated file (through the cat command).txt Could not remove 'log_file. size_in_bytes The maximum size of the file. The full form of this command is enable ST logging (esl).txt' with a maximum size of 5000 bytes.3.log' ---------------------------------------------------------------> Command esl executed on [1/1/2004 0:0:22:370001] <--------------------------------------------------------------******************************************************** Enabled Service Terminal Logging Data to a file Filename: /ram/st_logs. This command can be typically used in scenarios where auditing is required for record purposes. You can use any of the commands provided to log the desired service terminal outputs to a file on the PCU RAM disk system.txt 5000 Execution printouts BCSU/0/PCU/0/OSE/L>esl st_logs.log 5000 filename extension should be “log” changing filename 'st_logs.log Size: 5000 DN0479352 Issue 4-2 Id:0900d805806444bc 35 . Syntax esl <filename> <size_in_bytes> Examples 1.

Service terminal commands PCU2 Service Terminal Commands 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 dlfi (display logging to a file information) Function The full form of this command is display logging to a file information (dlfi).log Size: 5000 ******************************************************** 2. Disable the service terminal logging to a file. 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 36 Id:0900d805806444bc DN0479352 Issue 4-2 . dsl Execution printouts BCSU/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. dlfi Execution printouts If no logging to a file has been enabled. Syntax dsl Examples 1.2 dsl (disable ST logging) Function The full form of this command is disable ST logging (dsl).3. Syntax dlfi Examples 1. Display the existing logging to a file options.3.

log Size: 5000 ******************************************************** ******************************************************** Service Terminal GB Logging to a file mode is ON Filename: /ram/st_gb_logs. Syntax remove <filename> Parameter explanations file identifier This parameter specifies which file is to be removed.3.log for removing all log files with extension '. You must close the files before executing this command by disabling logging to a file for the respective file.4 remove (remove logging files) Function With 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 various options which can be specified are: all_log_files *.log Size: 5000 ******************************************************** ******************************************************** Service Terminal Subscriber Logging to a file mode is ON Filename: /ram/st_sm_logs. 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' for removing all log files with extension '.log' DN0479352 Issue 4-2 Id:0900d805806444bc 37 . The full form of this command is remove logging files (remove).PCU2 Service Terminal Commands Service terminal commands Service Service Service Service Terminal Terminal Terminal Terminal MM Logging GB Logging UP Logging Subscriber to a file mode Not activated to a file mode Not activated to a file mode Not activated Logging to a file mode Not activated If all loggings to a file have been enabled.log Size: 5000 ******************************************************** 2.log Size: 5000 ******************************************************** ******************************************************** Service Terminal UP Logging to a file mode is ON Filename: /ram/st_up_logs.

Service terminal commands PCU2 Service Terminal Commands filename Examples for removing individual files 1.log' from the RAM disk. Remove a file named 'log_gb. Remove all log files with the extension '. Syntax <command> > <filename> Examples 1. the reason for it will be printed out: ---------------------------------------------------------------> Command remove executed on [1/1/2004 0:3:31:510001] <--------------------------------------------------------------File <abc.log 3. Remove all files with the extension '. remove all_log_files Execution printouts A 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. Redirect the output of the 'ps' command to a file 'ps_output.3.txt BCSU/0/PCU/0/OSE> BCSU/0/PCU/0/OSE>cat ps_output.log 2. remove log_gb.log> could not be removed Search permission is denied for a component of the path prefix 2.txt pid name tpr block 00400057 ps p09 main 00010055 st_receiver p09 main 00010054 ose_shell p09 main 00010053 DSPMTI tim main 00010052 ose_login p09 main 00010051 MCC_HDLC_TI tim main 00010050 MCC_HDLC_1 i03 main 0001004f PSW p16 main own status 4 running 0 rcv 5 rcv 0 1 rcv 0 0 0 rcv 38 Id:0900d805806444bc DN0479352 Issue 4-2 .5 > command Function With this command you direct the output of any command to a file.txt'.log' from the RAM disk.txt Execution printouts BCSU/0/PCU/0/OSE>ps > ps_output.log' from the RAM disk. remove *. ps > ps_output.

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

wildcard and pixlist index as follows: • • • • numerical pid (0x10001) name (ose_shell) wildcard (ose*) pixlist index (*(14)) Name. name.4.Service terminal commands PCU2 Service Terminal Commands 0001001c ose_nulldev 0001001b ose_tosv_ti 0001001a ipcom_syslogd 00010019 ipcom_init 00010018 ose_cmd_proxy 00010017 ose_eat_vector 00010015 ose_heapd_cleanup 00010014 CPUMON_BACK_GND 00010013 start_efs 00010012 ose_ramdisk 00010011 ose_extfm 00010010 ose_shelld 0001000f ose_serdd 0001000e ose_confm 0001000d ose_fss 0001000c ose_tosv 0001000b ose_rtc 0001000a ose_heapd 00010008 main 00010009 ose_ticker 00010006 ose_huntd 00010005 ose_huntd 00010004 ose_tickd 00010003 ose_sysd 00010002 idle Total 84 processes BCSU/31/PCU/4/OSE> ph tim p10 p10 p20 i00 p31 bg p09 p09 p09 p09 p09 p09 p09 p02 p03 p10 p16 i00 ph p10 i31 p20 bg main main main main main main main main main main main main main main main main main main main OSE OSE OSE OSE OSE OSE 0 0 0 86 0 0 0 0 0 1 1 0 1 1 0 1 0 1 1 0 0 0 0 80 0 rcv stop ready rcv rcv ready stop ready rcv rcv rcv rcv rcv rcv rcv rcv rcv rcv rcv rcv ready 2. Processes and blocks can be specified by numerical pid. The command lists the specified process or all processes belonging to the specified block.1 ps Function With this command you list the current processes running in the system. With no parameters all processes are listed. 2. Syntax ps [-w] [<pid>] 40 Id:0900d805806444bc DN0479352 Issue 4-2 .4 Process manipulation commands This section contains the commands provided by the OSE real-time operating system (RTOS) to the process manipulation category of the service terminal. wildcard and pixlist index can be mixed.

For example. Specifies the thread priority. ps Execution printouts Output field descriptions: Parameter pid name tpr Explanation Specifies the process ID of the process. List the current processes and their states in the system. Specifies the block to which the process belongs. The process is a phantom process. BCSU/0/PCU/0/OSE>ps pid name 0003000c DSPMTI 00010064 pcu_agnt_cmd_proc 00010063 MCC_HDLC_TI 00010062 MCC_HDLC_1 00010061 DMA1ISR 0001005f srio_sw_int_proc 0001005e IPMR tpr tim p14 tim i03 i30 i06 p16 block pcu2e pcu2e pcu2e pcu2e pcu2e pcu2e pcu2e own 0 0 0 0 0 0 1 status sem rcv DN0479352 Issue 4-2 Id:0900d805806444bc 41 . Specifies the status of the process: running rcv sem delay ready The process is currently running. Specifies the priority.PCU2 Service Terminal Commands Service terminal commands Parameter explanations –w Wide listing. The process is executing a delay system call. The process is a timer interrupt process. interrupt. Specifies the owner of the process. and timer interrupt processes do not have any statuses. P09 specifies priority 9. The phantom . pid Specifies the process ID of the process. The process is waiting on a receive call. Examples 1. The process is ready to be started. Specifies the process name. The process is waiting for a semaphore. bg pxx tim ph block own status The process is a background process. and is waiting for a message.

Service terminal commands PCU2 Service Terminal Commands 0001005d 0001005c 0001005b 0001005a 00010059 00010058 00010057 00010056 00010055 00010054 00010053 00010052 00010051 00010050 0001004f 0001004e 0001004a 00010049 00010048 00010047 00010046 00010045 00010044 00040043 0002000d 00010031 00770067 00010066 00010065 00020060 0001004d 0001004c 0001004b 00010042 00010041 00010040 0001003f 0001003e 0001003d 0001003c 0001003b 0001003a 00010039 00020037 00010038 00010036 00010035 00010034 00010033 00010032 0001002f IBNACC IDRS CPUMON PCU_AGNT PSW RL FR NS BGP PCM PFM MAC PDM ABM DIAGONOSTICS DSPRM SDL SYSMON ARS IPC_MR DSPMRX DSPM PMS-PQII LOGGER efs_file_owner cm_main ps st_receiver st_main my_ose_login st_dmx_dd1 st_dmx_dd0 STA ose_telnetd ose_vfs/pop3 ose_vfs/http ose_vfs/ftp ose_vfs/tftp ose_vfs/ramlog ose_vfs/zip ose_vfs/gzip ose_surfer iptftps_service iptftps ipnetradvd_service ipftps_service ipftps ose_gws ose_lmcmd_daemon CPUMON_BACK_GND ose_dbgserver p16 p16 p10 p15 p16 p16 p16 p16 p16 p16 p16 p16 p16 p15 p16 p20 p18 p16 p16 p16 p05 p16 p16 p16 ph p16 p09 p09 p09 p09 p09 p09 p09 bg p22 p22 p22 p22 p22 p22 p22 p26 p16 p16 p16 p16 p10 bg p24 bg p10 pcu2e pcu2e pcu2e pcu2e pcu2e pcu2e pcu2e pcu2e pcu2e pcu2e pcu2e pcu2e pcu2e pcu2e pcu2e pcu2e pcu2e pcu2e pcu2e pcu2e pcu2e pcu2e pcu2e pcu2e pcu2e pcu2e main main main main main main main main main main main main main main main main main main main main main main main main main 0 0 0 4 0 1 1 1 0 0 0 0 2 0 0 1 0 0 2 1 1 4 0 3 0 29 6 1 7 3 1 1 0 1 0 0 0 0 0 0 0 1 1 1 1 1 1 2 0 0 2 rcv rcv rcv rcv rcv rcv rcv rcv rcv rcv rcv rcv rcv rcv rcv rcv rcv rcv rcv rcv rcv rcv rcv rcv rcv running rcv rcv rcv rcv rcv rcv rcv rcv rcv rcv rcv rcv rcv rcv rcv rcv rcv rcv rcv rcv rcv rcv ready rcv 42 Id:0900d805806444bc DN0479352 Issue 4-2 .

PCU2 Service Terminal Commands

Service terminal commands

0001002e ose_vfs 0001002d ose_dhcp 0001002c ose_resolve 0001002b ose_ucc 0001002a ose_ucc 00010029 ipnetd 00010028 ipcom_syslogd 00010027 ipcom_shared_heap 00010026 ose_inet 00010025 netw_supervisor 00010024 ose_rtl_elf 00010023 ose_program_mgr 00010022 ose_extfm_/ram 00010021 ose_extfm 00010020 ose_boardparam 0001001f ose_ramdisk 0001001e FAM_COMMON_SENDER 0001001d uart1 0001001c ose_serdd_uart1 0001001b ose_confm_/tty 0001001a ose_confm 00010019 ose_serdd 00010018 ose_cmd_proxy 00010017 ose_nulldev 00010016 ose_shelld 00010015 ose_fss 00010014 ose_rtc 00010013 ose_riodb_tx0 00010012 ose_riodb_rx0 00010011 ose_dma0 00010010 ose_devman 0001000f ose_heapd 0001000e ose_memory_mgr 0001000b core_supervisor 00010009 main 0001000a ose_ticker 00010007 ose_monitor 00010006 ose_huntd 00010005 ose_huntd 00010004 ose_tickd 00010003 ose_sysd 00010002 idle Total 100 processes BCSU/0/PCU/0/OSE>

p22 p16 p12 i14 i14 p10 p10 ph p10 p15 p25 p25 p25 p25 p10 p30 ph i08 p14 p14 p14 p14 p20 ph p25 p19 p05 i10 i10 i08 p20 p20 p20 p15 p16 i00 p01 ph p10 i31 p20 bg

main main main main main main main main main main main main main main main main main main main main main main main main main main main main main main main main main main main OSE OSE OSE OSE OSE OSE OSE

0 1 1 0 0 1 1 0 343 5 0 3 5 1 0 1 0 1 0 4 1 1 0 0 1 1 0 0 0 0 3 43 0 26 1 0 4 0 0 0 97 0

stop ready rcv rcv rcv rcv rcv rcv rcv rcv rcv rcv rcv rcv rcv ready rcv rcv rcv rcv rcv rcv rcv rcv rcv rcv rcv rcv rcv rcv ready

2.5

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

DN0479352 Issue 4-2

Id:0900d805806444bc

43

Service terminal commands

PCU2 Service Terminal Commands

2.5.1

dbu (display buffers per unit)
Function With 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). Syntax dbu <processor type>{:<dsp id>} Parameter explanations processor type 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 specified 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 printouts

BCSU/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

44

Id:0900d805806444bc

DN0479352 Issue 4-2

PCU2 Service Terminal Commands

Service terminal commands

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 0 131072 0 1 0.00% 100.00% 131072 0 131072 1150000 1 0 100.00% 100.00% 1150000 1150000 0 1397760 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 Free size 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>

DN0479352 Issue 4-2

Id:0900d805806444bc

45

dbp pq2:1 2. Display the buffers allocated by the application on dsp '1' with application ID '1'.5.Service terminal commands PCU2 Service Terminal Commands 2. see section Application IDs for commands. Display the buffers allocated by the application on pq2 with application ID '1'. Examples 1. The allowable values are 'pq2' and 'dsp' dsp id Specifies the DSP ID. For the application IDs. dbp dsp:1:1 Execution printouts BCSU/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 46 Id:0900d805806444bc DN0479352 Issue 4-2 . application id The application ID should be within the possible range. The parameter needs to be specified only in case the processor type is DSP.2 dbp (display buffer statistics per process) Function With this command you list the buffer statistics per process on a particular processor type. Syntax dbp <processor type>{:<dsp id>}:<application id> Parameter explanations processor type Specifies the processor type on which the application is residing. The values range from 0 to 7. The full form of this command is display buffer statistics per process (dbp).

3 dbs (display buffer statistics of particular size) Function With this command you list the buffer statistics of a particular buffer size on a particular processor. 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 allowable values are 'pq2' and 'dsp' dsp id Specifies the DSP ID. The full form of this command is display buffer statistics of particular size (dbs). The parameter needs to be specified only in case the processor type is DSP.PCU2 Service Terminal Commands Service terminal commands 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. DN0479352 Issue 4-2 Id:0900d805806444bc 47 . Syntax dbs <processor type>{:<dsp id>} <buffer size> Parameter explanations processor type Specifies the processor type on which the application is residing. the next highest size is displayed instead. The values range from 0 to 7.5.

Service terminal commands PCU2 Service Terminal Commands Examples 1. dbs pq2 30 2. Display the buffers allocated by various applications with buffer size 30 on dsp '0'. Display the buffers allocated by various applications with buffer size 30 on pq2. dbs dsp:0 30 Execution printouts BCSU/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 -------------------------------------------------------------------------------- 48 Id:0900d805806444bc DN0479352 Issue 4-2 .

4 dtp (display timer statistics per process) Function With this command you list the timer statistics for a process on a particular processor. For the application IDs. application id The application ID should be within the possible range. see section Application IDs for commands. Examples 1.5. The full form of this command is display timer statistics per process (dtp). The allowable values are 'pq2' and 'dsp' dsp id Specifies the DSP ID. dtp pq2:1 2. Syntax dtp <processor type>{:<dsp id>}:<application id> Parameter explanations processor type Specifies the processor type on which the application is residing. dtp dsp:1:1 Execution printouts BCSU/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] <--------------------------------------------------------------- DN0479352 Issue 4-2 Id:0900d805806444bc 49 . The parameter needs to be specified only in case the processor type is DSP. Display the timers started by the application on pq2 with application ID '1'. The values range from 0 to 7. Display the timer started by the application on dsp '1' with application ID '1'.PCU2 Service Terminal Commands Service terminal commands 2.

on PQII only.Service terminal commands PCU2 Service Terminal Commands Timer statistics for application 1 -------------------------------------------------------------------------------Timer id Timer value(ms) Timer type Time left till next expiry(ms) -------------------------------------------------------------------------------0x2820c2 500 periodic 8 -------------------------------------------------------------------------------- 2. The full form of this command is display timer statistics per unit (dtu).5 dtu (display timer statistics per unit) Function With this command you list the timer statistics per application for all the applications. dtu Execution printouts BCSU/0/PCU/0/OSE>dtu ---------------------------------------------------------------> Command dtu executed on [1/1/2004 0:13:17:530001] <---------------------------------------------------------------------------------------------------------------------------------------------App Timer Timer Timer Time left Total id id value(ms) type till next expiry(ms) timers -------------------------------------------------------------------------------1 70 periodic 46 1 -------------------------------------------------------------------------------5 1000 periodic 284 1 -------------------------------------------------------------------------------7 7 7 7 7 7 7 7 10000 periodic 1250468 1800000 periodic 1250642 1800000 periodic 1250758 1800000 periodic 1250756 1800000 periodic 1250756 1800000 periodic 1250812 1800000 periodic 1250812 1800000 periodic 1250812 8 -------------------------------------------------------------------------------8 0x736e0d8 10000 periodic 1412 1 -------------------------------------------------------------------------------15 0x736e288 5000 periodic 1978 1 -------------------------------------------------------------------------------28 0x736e378 2000 periodic 482 0x736e108 0x736e138 0x736e168 0x736e198 0x736e1c8 0x736e1f8 0x736e228 0x736e258 0x736e078 0x736e3a8 50 Id:0900d805806444bc DN0479352 Issue 4-2 .5. Syntax dtu Examples 1. Display the timers currently started in the PQII processor.

The third dimension parameter Service area is also mandatory for the category 79 Coding Scheme.6 dsca (display statistics counter for specific category) Function With this command you display the values of the statistics counter IDs for a specific category (dsca). For the parameters that need to be specified. second dimension. in case you want to DN0479352 Issue 4-2 Id:0900d805806444bc 51 . This command has a 'first dimension'. a 'second dimension' and a 'third dimension' as conditional parameters.PCU2 Service Terminal Commands Service terminal commands 1 -------------------------------------------------------------------------------- 2. Note that the second dimension parameter Service area is required for the category 72 PCU. For example. Category ID 72 73 74 76 79 90 95 96 97 98 105 110 Statistics category First dimension PCU RLC Blocks per TRX Frame Relay Dynamic Abis Coding Scheme Quality of Service GPRS Cell Reselection GPRS RX Level and Quality Enhanced QoS Gb over IP PS DTM PCU Utilisation BTS ID BTS ID Bearer channel no. If the GPRS Cell Re-selection record is to be displayed for a particular BTS ID and LACCI pair. third dimension These parameters define the additional parameter to be specified.5. counters for all possible records with valid data are displayed. This parameter is dependent on the category ID (see the table above). see the table below. provide the CI in the most significant byte (MSB) and the LAC in the least significant byte (LSB) of the LAC-CI pair. If the dimensions are not passed. first dimension. EDAP ID BTS ID Segment ID BTS ID BTS ID Segment ID NSEI BTS ID Second dimension Service area TRX ID Third dimension Coding scheme QoS class LAC-CI TRX ID TC-THP-PFI ID NSVC ID Service area Coding scheme ARP ID Syntax dsca <category id> {first dimension} {second dimension} {third dimension} Parameter explanations category ID This parameter specifies the category of the counters.

Display the statistics of category id 76 with EDAP ID '1'. dsca 76 Execution printouts BCSU/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 = 1 total_nbr_of_pcm_subtsls_in_edap = 15 average_dl_edap_usage = 16 average_ul_edap_usage = 17 average_edap_usage_den = 18 peak_dl_edap_usage = 19 peak_ul_edap_usage = 20 ul_tbfs_without_edap_res = 21 dl_tbfs_without_edap_res = 22 dl_tbfs_with_inadequate_edap_res = 23 ul_edap_allocation_requests = 24 dl_edap_allocation_requests = 25 ave_edap_ul_allocated_for_rt = 26 ave_edap_dl_allocated_for_rt = 27 ave_edap_ul_usage_for_rt = 28 ave_edap_dl_usage_for_rt = 29 ave_edap_ul_usage_for_nrt = 30 ave_edap_dl_usage_for_nrt = 31 total_nbr_of_pcm_subtsls_in_edap_ul = 32 dynamic_abis_denom_ul = 33 ul_mcs_limited_by_pcu = 34 dl_mcs_limited_by_pcu = 35 2. Examples 1.5.Service terminal commands PCU2 Service Terminal Commands display statistics related to a particular BTS (for category PCU). a 'second dimension' and a 'third dimension' as conditional parameters. 52 Id:0900d805806444bc DN0479352 Issue 4-2 . This command has a 'first dimension'. dsca 76 1 2. then BTS ID needs to be given in the first dimension. Display the statistics of category id 76 for all EDAP IDs with valid data. the counter's value for all configured dimensions is displayed. If the dimensions are not passed.7 dsco (display statistics for a specific counter) Function With this command you display statistics for a specific counter (dsco).

first dimension. For example. if you want to display statistics related to a particular BTS (for category PCU). Display the statistics of counter ID 110002.PCU2 Service Terminal Commands Service terminal commands If the GPRS Cell Re-selection record is to be displayed for a particular BTS ID and LACCI pair. 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 Syntax dsco <counter id> {first dimension} {second dimension} {third dimension} Parameter explanations counter ID This parameter defines the counter ID. third dimension These parameters define the additional parameter to be specified. second dimension. Examples 1. provide the CI in the MSB and the LAC in the LSB of the LAC-CI pair. For the counter IDs. This parameter is dependent on the category of the specified counter ID. then BTS ID needs to be given in the first dimension. dsco 110002 Execution printouts BCSU/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 DN0479352 Issue 4-2 Id:0900d805806444bc 53 .

76 the statistics of all categories. if you want to reset counters related to a particular BTS (for category PCU).8 rsca (reset statistics counter for specific category) Function With this command you reset the values of statistics counter IDs for a specific category (rsca).5. Examples 1. first dimension. Reset rsca 2. For the parameters that need to be specified. third dimension These parameters define the additional parameter to be specified. all the dimensions are reset. Reset rsca the statistics of category id 76 with EDAP ID '1'. This parameter is dependent on the category ID (see the table above). Category ID 72 73 74 76 79 90 95 96 97 98 105 110 Statistics category PCU RLC Blocks per TRX Frame Relay Dynamic Abis Coding Scheme Quality of Service GPRS Cell Reselection GPRS RX Level and Quality Enhanced QoS Gb over IP PS DTM PCU Utilisation First dimension BTS ID BTS ID Bearer channel no EDAP ID BTS ID Segment ID BTS ID BTS ID Segment ID NSEI BTS ID Second dimension Service area TRX ID Third dimension Coding scheme QoS class LAC-CI TRX ID TC-THP-PFI ID NSVC ID Service area Coding scheme ARP ID Syntax rsca [<category id>] {first dimension} {second dimension} {third dimension} Parameter explanations category ID This parameter specifies the category of the counters. then BTS ID needs to be given in the first dimension. see the table below. second dimension. For example. a 'second dimension' and a 'third dimension' as conditional parameters. all the categories for all their respective dimensions are reset. Reset rsca 3. 54 Id:0900d805806444bc DN0479352 Issue 4-2 . If the dimensions are not passed. 76 1 the statistics of category id 76 for all EDAP IDs.Service terminal commands PCU2 Service Terminal Commands 2. If the category ID is not passed. This command has a 'first dimension'.

PCU2 Service Terminal Commands Service terminal commands Execution printouts BCSU/0/PCU/0/OSE>rsca 76 1 ---------------------------------------------------------------> Command rsca executed on [11/7/20080:7:53:180001] <--------------------------------------------------------------- 2.Black Box abb (analyze black box) Function With this command you dump the black box contents on to the service terminal screen. Syntax rsco <counter id> {first dimension} {second dimension} {third dimension} Parameter explanations counter ID This parameter defines the counter ID. Syntax abb <processor type> DN0479352 Issue 4-2 Id:0900d805806444bc 55 . all the dimensions are reset. third dimension These parameters define the additional parameter to be specified. second dimension. Reset statistics of counter ID 110002.6.6 2. rsco 110002 Execution printouts BCSU/30/PCU/4/OSE>rsco 110002 ---------------------------------------------------------------> Command rsco executed on [11/7/2008 13:16:3:22612] <--------------------------------------------------------------- 2.1 Utilities . see section Error code debugging information for abb and doe command output. Examples 1.9 rsco (reset statistics for a specific counter) Function With this command you reset statistics for a specific counter (rsco). a 'second dimension' and a 'third dimension' as conditional parameters. first dimension. If the dimensions are not passed. To debug the error code. if you want to reset counters related to a particular BTS (for category PCU). For example. This parameter is dependent on the category of the specified counter ID.5. This command has a 'first dimension'. then BTS ID needs to be given in the first dimension.

and Normal Shutdown.7 specify the crashed DSP Number. Specifies the process ID.OS_ZOOMBIE 4096 .OS_BLOCK 2048 . abb pq2 Execution printouts Output field description: Parameter name Cause code Reboot reason Description Specifies the cause code used by the kernel to indicate which error caused a call to the error handler.OS_TI_PROC 512 . Contains the process type. The only allowable value is 'pq2'. Legal values are: 0 .OS_PHANTOM 1024 . Analyse the black box for 'pq2'. This field specifies the process name of the application/platform processes.Service terminal commands PCU2 Service Terminal Commands Parameter explanations processor type This parameter specifies the processor type on which the application is residing. Specifies the processor ID on which the black box formation has occurred. 8 specifies that the crash has happened on the PQII processor. Process name is a string (in the strings array) showing the name of the process or block. This value is reset in case of a healthy reboot. Examples 1. Typical examples are SSF Initialisation Failure. 0 . Process startup Failure. You can use the status field to determine which the case is. The number of PCU2 processes initially started successfully by the component manager.OS_ILLEGAL Fast semaphore Specifies the current value of the fast semaphore attached to the process.OS_PRI_PROC 64 . Contains the various reboot/failure reasons because of which the card would be reset.OS_BG_PROC 128 .OS_INT_PROC 256 . The number of times the system has been restarted. The value is negative if the process is waiting at the semaphore or if the process does not have a fast semaphore. Number of retries Number of processes Processor ID Process name Process ID Process type 56 Id:0900d805806444bc DN0479352 Issue 4-2 .

OS_STOPPED . Process priority User Signal count Specifies the new priority. The second 'product name' specifies the OSE process name. not when traversing the signal queue itself. File is a string (in the strings array) showing the file name from which the current system call was issued. 64 . DN0479352 Issue 4-2 Id:0900d805806444bc 57 .OS_INTERCEPTED .OS_REMOTE . two. Registers that cannot be determined at a certain point are excluded from the list. All values are in upper case hex format.OS_RECEIVE .31. Line number Filename Cpu register Optional fields (only displayed if the required information can be extracted during the system failure): Product Name Product Name File name Sub Code Specifies the product name which triggered the kernel error handler.PCU2 Service Terminal Commands Service terminal commands Parameter name Process status Description Contains the process status. Line and file information is available only if the PCU2 platform was compiled with the debug option. and it assists the user in locating the exact error cause.OS_FSEMAPHORE . 2 . 16 .The process was stopped. or three bits set. for example: 'TELNET/UDP server'.Waiting for a delay call. Signal count is the number of signals currently in the signal queue of the process. It contains the return address to user code while a system call is in progress.OS_DELAY . 4 . Line is 0 if no line and file information is available. 32 . Other bits are mutually exclusive. This is a bit field with zero. In OSE the allowable range is from 0 . Legal bit masks are: 1 . User is the user number of the process.OS_SEMAPHORE . for example: 'OSE_TELUDPD'. Information on CPU register values is only available for kernel libraries supporting debugging. There may be a pseudo register named 'R'".A breakpoint was reached. for example: 'inetutilerr. 0 is the highest priority. The OS_STOPPED and OS_INTERCEPTED bits can be set independently.h'.Waiting for a remote system call. the process is ready or running. If no bits are set. Line and file information is available if the PCU2 platform was compiled with the debug option.Waiting for one of the receive calls. Specifies the OSE error code filename in which the error code description can be found. This field is invalid if line is 0. The subcode is extracted from error_code. one.Waiting at a semaphore. Registers are separated by a space.Waiting at a fast semaphore. Line is an integer containing the source code line from which the current system call was issued. 8 . A sample string might look like “PC=00001D34 SP=000089AB D1=0000A89”. The names of these are CPU dependent. Cpuregs is a string (in the strings array) showing all known CPU register values. Otherwise the process is suspended for one or more reasons. Note that the 'Signal count' field should only be used for statistics.

Service terminal commands PCU2 Service Terminal Commands 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 :2 Line 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 58 Id:0900d805806444bc DN0479352 Issue 4-2 .

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 :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 :0 Line 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 :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.PCU2 Service Terminal Commands Service terminal commands Line Number Filename CPU Register :617 :ssf_event.c CPU Register :TID=00000244 DN0479352 Issue 4-2 Id:0900d805806444bc 59 .

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.Service terminal commands PCU2 Service Terminal Commands --------------------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 :0 Line Number :617 Filename :ssf_event.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 :0 Line Number :617 Filename :ssf_event.c CPU Register :TID=00000258 --------------------Data for Process:MAC------------Process Id :0x10035 60 Id:0900d805806444bc DN0479352 Issue 4-2 .

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 :0 Line Number :617 Filename :ssf_event.PCU2 Service Terminal Commands Service terminal commands Process Type Process Status Process Priority User Fast Semaphore Signal Count Line Number Filename CPU Register :0 :1 :16 :0 :0 :0 :617 :ssf_event.c CPU Register :TID=00000268 --------------------Data for Process:NS------------Process Id :0x10039 Process Type :0 Process Status :1 Process Priority :16 DN0479352 Issue 4-2 Id:0900d805806444bc 61 .c :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 :0 Line 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=00000278 2.Service terminal commands PCU2 Service Terminal Commands User Fast Semaphore Signal Count Line Number Filename CPU Register :0 :0 :0 :617 :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 :0 Line Number :617 Filename :ssf_event.2 mbbrbb (multiple black box read black box) Function With this command you read the black box from the mbb structure with the processor ID.c :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 :0 Line 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.6. 62 Id:0900d805806444bc DN0479352 Issue 4-2 .

so that the timestamp can be compared in local format. n:<n> This parameter prints the nth most recent black box for pq2 or dsp:<dsp id>.dsp:7. bt:DD:MM:YYYY:HH:MM:SS This parameter prints all the black boxes for the given processor ID. so that the timestamp can be compared in local format.. The information is displayed in sequence. The allowable values are pq2 or dsp:0. Examples 1.. at:DD:MM:YYYY:HH:MM:SS This parameter prints all the black boxes for the given processor ID. the time of creation. mbbrbb dsp:1 -all Execution printouts BCSU/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 DN0479352 Issue 4-2 Id:0900d805806444bc 63 . The input time is in local format. which were created before the time given to command input.PCU2 Service Terminal Commands Service terminal commands Syntax mbbrbb <processor_id> <-snapshot | -all | -n:number | -bt:DD:MM:YYYY:HH:MM:SS | -at:DD:MM:YYYY:HH:MM:SS> Parameter explanations processor_id This parameter specifies the processor type on which the application is residing. such as the processor ID. The input time is in local format. all This parameter prints the recorded black boxes for pq2 or dsp <dsp id> along with the flash header. Print all the black boxes for dsp '1'. snapshot This parameter gives the information stored in the flash header. starting from the most recent black box. and the version name of the build. which were created after the time given to command input.

. dsp id This parameter specifies the DSP ID. see section Application IDs for commands.WARNING LOGS 64 Id:0900d805806444bc DN0479352 Issue 4-2 . 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. For the application IDs.NO LOGS 1 . By executing these commands you can change the log level of various applications.. Syntax sll <processor type>{:<dsp id>}[:<application id>]<log level>: .logging This section contains the commands related to the logging facility provided in the PCU2 system for debugging purposes. (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. application id The application ID should be within the allowable/possible range. This parameter should to be specified only if the processor type is DSP. Parameter explanations processor type This parameter specifies the processor type on which the application is residing.Service terminal commands PCU2 Service Terminal Commands Some Static Function. The allowable values are 'pq2' and 'dsp'. log level This parameter is the new log level to be specified.7.1 sll (set the log level) Function With this command you change the existing log level. 2. 0 .7 Utilities .

PCU2 Service Terminal Commands Service terminal commands 2 . Set the log level of all the applications on pq2 processor to 1. Examples 1. 2 and 3.ERROR LOGS 7 . Set the log level of the application with application ID '2' on dsp '1' processor to 1 and 4.INFO_1 LOGS 3 .DETAIL_1 LOGS 8 . For example. Set the log level of all the applications on dsp '1' processor to 1 and 4. You can set multiple log levels at the same time. any level cannot be specified more than once. the command sll pq2:1 1:2:1 is invalid. the command sll pq2:1 0:1:2:3 is invalid. sll pq2:15 1:2 2. sll dsp:1:2 1:4 3. In addition.CRITICAL LOGS These log levels are mutually exclusive. Set the log level of the application with application ID '15' on pq2 processor to 1 and 2.DETAIL_3 LOGS 10 . sll pq2 1:2:3 4.DETAIL_2 LOGS 9 .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 ------------------------------------------------------------ DN0479352 Issue 4-2 Id:0900d805806444bc 65 . sll dsp:1 1:4 Execution printouts The 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.INFO_2 LOGS 4 . The log level 'No logs' cannot be specified in combination with any other level.INFO_3 LOGS 5 .DETAIL_4 LOGS 11 .INFO_4 LOGS 6 . For example.

Service terminal commands PCU2 Service Terminal Commands ----> Command sll executed on [1/1/2004 0:1:2:720001] <--------------------------------------------------------------Response from DSP [1].Current DL BPN:[9598] [Logging Trace][<DSP ID:0>. and this command can be used to change the filtering criterion regarding the software layer. Syntax ssl <processor type>{:<dsp id>}[:<application id>]<software layer>: . second message The log message for the DSP processor type: [Logging Trace][<DSP ID:0>.2 ssl (set the software layer) Function The full form of this command is set the software layer (ssl). TRX Id: [0]. TSL Id: 1 Current UL BPN:[9476]. 66 Id:0900d805806444bc DN0479352 Issue 4-2 .2 Description The filename from which the log message was generated.5][60069] Current UL BPN:[9475].. The log level and software layer of the application.c][522][33][29/10/2004 20:56:20:190000][6.\pfd_ul.5][60068] UL overflow condition is true for TRX. In the example above. and the software layer is 2 .c 25 17 1/1/2004 0:16:23:180001 7.c][695][33][29/10/2004 20:56:20:190000][6.INFO3 LOG SOFTWARE LEVEL: COMPUTING_PLATFORM Log messages will be generated consecutively by the applications: Log message output description: Parameter name psw. Appropriate logs will be generated according to this filtering criterion.7.c][516][33][29/10/2004 20:56:20:190000][6. EGPRS enabled: [1]. The log message raised by the application. The line number of the file from which the log message was generated.COMPUTING PLATFORM. The date stamp when the log was raised in dd/mm/yyyy format.\pfd_ul. Application [2]: LOG LEVEL: WARNING.DETAIL_1 LOGS.5] [60070]PFD ERROR: No data written by Platform PFD for this TSLTRX Id: 0..ul_overflow_reg:[0xee] [Logging Trace][<DSP ID:0>. The time stamp when the log was raised in hr:min:sec:micro-seconds format.\pfd_ul. the log level is 7 .Current DL BPN:[9598] 2. Application processes can be classified into various categories. The application ID of the application that raised the log.

You can set multiple layers at the same time.APPLICATION. dsp id This parameter specifies the DSP ID. Set the software level of all the applications on pq2 processor to 1.NO LOGS 1 . ssl pq2:17 1:2:3 2. The software layer 'No logs' cannot be specified in combination with any other layer. any layer cannot be specified more than once. 2 and 3. ssl dsp:1 1:4 Execution printouts The execution printout for the PQII processor type: DN0479352 Issue 4-2 Id:0900d805806444bc 67 .KERNEL 2 . ssl dsp:1:1 1:4 3. ssl pq2 1:2:3 4. Set the software level of application with application id as '17' on pq2 processor to 1. Set the software level of application with application id as '1' on dsp '1' processor to 1 and 4.PCU2 Service Terminal Commands Service terminal commands Parameter explanations processor type This parameter specifies the processor type on which the application is residing. see section Application IDs for commands. the command ssl pq2:1 0:1:2:3 is invalid. For example.RECOVERY 5 . For the application IDs.APPLICATION 6 .OTHERS Currently the PCU2 software produces log writings only with software layer 5 . This parameter is to be specified only in case the processor type is DSP. the command ssl pq2:1 1:2:1 is invalid. 2 and 3.COMPUTING PLATFORM 3 . 0 . Examples 1. software layer This is the new software layer to be specified. In addition. For example. These layers are mutually exclusive. application id The application ID should be within the allowable/possible range.SWITCHING PLATFORM 4 . Set the software level of all the applications on dsp '1' processor to 1 and 4. The allowable values are 'pq2' and 'dsp'.

3 slf (set the logger feature) Function With this command you enable/disable the logging facility on the PCU system. Enable the logger feature on pq2. Examples 1. slf pq2 1 2. To enable give value '1' and to disable give value '0'.Service terminal commands PCU2 Service Terminal Commands 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. INFO3 LOG SOFTWARE LEVEL: KERNEL. This parameter is to be specified only in case the processor type is DSP. slf dsp:1 1 68 Id:0900d805806444bc DN0479352 Issue 4-2 . Enable the logger feature on dsp '1'. The full form of this command is set the logger feature (slf). The allowable values are 'pq2' and 'dsp'.COMPUTING_PLATFORM. INFO2 LOG SOFTWARE LEVEL: KERNEL.COMPUTING_PLATFORM. slf pq2 0 3.7. INFO1. Application [1]: LOG LEVEL: WARNING. dsp id This parameter specifies the DSP ID.SWITCHING_PLATFORM 2. Disable the logger feature on pq2. flag This parameter specifies the logging facility to be enabled or disabled.SWITCHING_PLATFORM The execution printout for the DSP processor type: 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]. Syntax slf <processor type>{:<dsp id>} <flag> Parameter explanations processor type This parameter specifies the processor type on which the application is residing.

For the application IDs. slf dsp:1 0 Execution printouts The execution printout for the PQII processor type: BCSU/0/PCU/0/OSE>slf pq2 1 ---------------------------------------------------------------> Command slf executed on [1/1/2004 0:2:20:560001] <--------------------------------------------------------------Logger is [1]. The full form of this command is display the log details (dld).7. application id The application ID should be within the allowable/possible range.PCU2 Service Terminal Commands Service terminal commands 4. dld pq2 4. 0: DISABLED]. This parameter is to be specified only in case the processor type is DSP. The allowable values are 'pq2' and 'dsp'. dld pq2:1 2. Display the log/software level details of all the applications on pq2. dld dsp:1 DN0479352 Issue 4-2 Id:0900d805806444bc 69 . The logger is 1 [1: Enabled. dsp id This parameter specifies the DSP ID. see section Application IDs for commands. 2. Disable the logger feature on dsp '1'. Examples 1. Display the log/software level details of application with application id '1' on dsp '1'. The execution printout for the DSP processor type: BCSU/0/PCU/0/OSE>slf dsp:1 1 ---------------------------------------------------------------> Command slf executed on [1/1/2004 0:2:20:560001] <--------------------------------------------------------------Response from DSP [1]. Syntax dld <processor type>{:<dsp id>} [<application id>] Parameter explanations processor type This parameter specifies the processor type on which the application is residing. Display the log/software level details of all the applications on dsp '1'. dld dsp:1:1 3. Display the log/software level details of application with application id '1' on pq2.4 dld (display the log details) Function This command can be used to examine the existing log level and software levels of the applications.

dlf pq2 70 Id:0900d805806444bc DN0479352 Issue 4-2 . The full form of this command is display the logger feature (dlf). The allowable values are 'pq2' and 'dsp'. Display the current setting of the logger feature on pq2.Service terminal commands PCU2 Service Terminal Commands Execution printouts The execution printout for the PQII processor type: 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 The execution printout for the DSP processor type: 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. Syntax dlf <processor type>{:<dsp id>} Parameter explanations processor type This parameter specifies the processor type on which the application is residing.7. This parameter is to be specified only in case the processor type is DSP. Examples 1. dsp id This parameter specifies the DSP ID.5 dlf (display the logger feature) Function With this command you display the existing set options to enable/disable the logging facility in the PCU system.

By disabling file logging. Syntax dfl Examples 1.6 efl (enable logging to file) Function With this command you enable logging to file from the PCU2. efl Execution printouts BCSU/0/PCU/0/OSE>efl Logging to file enabled.7.. Disable file logging. the PCU2 stops writing the logs to the file /ram/log_file. 2. dlf dsp:1 Execution printouts The execution printout for the PQII processor type: BCSU/0/PCU/0/OSE>dlf pq2 ---------------------------------------------------------------> Command dlf executed on [1/1/2004 0:3:9:310001] <--------------------------------------------------------------Logger is [1] (1->ENABLED. Logger is [1] (1->ENABLED.txt.7.. Syntax efl Examples 1. Enable file logging.PCU2 Service Terminal Commands Service terminal commands 2. dfl DN0479352 Issue 4-2 Id:0900d805806444bc 71 . Display the current setting of the logger feature on dsp '1'.txt. The execution printout for the DSP processor type: BCSU/0/PCU/0/OSE>dlf dsp:0 ---------------------------------------------------------------> Command dlf executed on [1/1/2004 0:3:9:310001] <--------------------------------------------------------------Response from DSP [0]. 0->DISABLED). By enabling file logging. BCSU/0/PCU/0/OSE> 2. 0->DISABLED).7 dfl (disable logging to file) Function With this command you disable logging to file from the PCU2. the PCU2 starts writing the logs to the file /ram/log_file.

BCSU/0/PCU/0/OSE> 2. BCSU/0/PCU/0/OSE> 72 Id:0900d805806444bc DN0479352 Issue 4-2 . including commands to reset the card after copying the new software from the download server or any other machine to the flash. reset dsp:1 Execution printouts The execution printout for the PQII processor type: BCSU/0/PCU/0/OSE>reset pq2 ---------------------------------------------------------------> Command reset executed on [1/1/2004 0:3:9:310001] <--------------------------------------------------------------pq2 Processor reset.Service terminal commands PCU2 Service Terminal Commands Execution printouts BCSU/0/PCU/0/OSE>dfl Logging to file disabled. BCSU/0/PCU/0/OSE> The execution printout for the DSP processor type: BCSU/0/PCU/0/OSE>reset dsp:7 ---------------------------------------------------------------> Command reset executed on [1/1/2004 0:3:9:310001] <--------------------------------------------------------------dsp Processor reset. and to display the existing software versions in the system.... reset pq2 2. 2.software manipulation This section contains the commands for software manipulation. Reset the dsp processor '1'. Reset the pq2 processor. Syntax reset <processor type>:{dsp id} Parameter explanations processor type This parameter specifies the processor type on which the application is residing..1 reset Function With this command you reset the PQII or DSP processor..8 Utilities ..8. This parameter is to be specified only in case the processor type is DSP. The allowable values are 'pq2' and 'dsp'. Examples 1. dsp id This parameter specifies the DSP ID.

ubs Execution printouts BCSU/0/PCU/0/OSE>ubs ---------------------------------------------------------------> Command ubs executed on [1/1/2004 0:7:53:180001] <--------------------------------------------------------------SDL ubs: Current Boot Image Software Version : "IGWBTPQC. You need to restart the PIU to make the new boot software effective. it cannot be executed when the PCU is in the WO (working) state. The full form of this command is upgrade boot software (ubs).8-0 BCSU/30/PCU/4/OSE> 2.elf 2. The command displays the boot and PIU RAM software version.33-0 PQ2 RAM Image Software Version: 9. Display the existing software version.elf 2.3 ubs (upgrade boot software) Function With this command you can transfer the software from the OMU disk to the PCU and program it to the flash memory on PCU2. Upgrade the boot software.8-0 DSP Diagnostics Image Software Version: 9.8-0 DSP Boot Image Software Version: 9. This command must be executed in TE (test) state only.2 ssv (show the software version) Function With this command you show the software version (ssv). Syntax ubs Examples 1. Syntax ssv Examples 1.8. ssv Execution printouts BCSU/30/PCU/4/OSE>ssv ---------------------------------------------------------------> Command ssv executed on [7/7/2008 11:6:32:413206] <--------------------------------------------------------------PQ2 Boot Image Software Version: 56.2P10_DMX" SDL ubs: Downloaded Boot Image Software Version : "IGWBTPQC.8-0 DSP RAM Image Software Version: 9.PCU2 Service Terminal Commands Service terminal commands 2.2P12_DMX" Confirm Boot Software Upgrade (y/n):y INPUT: y DN0479352 Issue 4-2 Id:0900d805806444bc 73 .8.

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. manipulation.. This parameter is to be specified only in case the processor type is DSP. SDL ubs: New Boot file would be applied when PCU is rebooted. If it is specified to src ID. IPC MR. For the application IDs. 74 Id:0900d805806444bc DN0479352 Issue 4-2 .. In other cases. src id This parameter specifies the source application ID from where the message is simulated to have been originated. Syntax emm <processor type>{:<dsp id>}{:<src id>} <processor type>{:<dsp id>}{:<dst id>} <direction_flag> [<msg type>] [<payload offset> <pattern>] Parameter explanations processor type This parameter specifies the card type.1 emm (enable message monitoring) Function With this command you activate message-monitoring with the desired filtering criteria. and IPC This section contains the commands for message monitoring and message manipulation. it specifies the dst processor type. ---------------------------------------------------------If the command is executed in the WO state. it specifies the src processor type. The source or destination cannot be of the logger. 'bsc' and 'dsp'.Service terminal commands PCU2 Service Terminal Commands SDL ubs: Upgrading Boot Software. The allowable values are 'pq2'. see section Application IDs for commands. 2. 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. dsp id This parameter specifies the DSP ID. The full form of this command is enable message monitoring (emm).message monitoring. 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. DSPA or DSPM.9 Utilities .

Enable message monitoring from application 1 at PQII to application 1 on DSP 1 for message type as 12. to monitor at sender. Enable message monitoring from application 1 at DSP 1 to application 2 on PQII for message pattern "01 02 03 04" from location 12.-. Enable message monitoring from application 1 at PQII to application 1 on DSP 1 for message type as 12.0/"/". emm pq2:1 dsp:1:1 2 12 4. msg type This parameter specifies the message type to be sent.-. -. pattern This parameter specifies the pattern to be compared from the offset 'payload offset'.----------05 00 0F 01 B7 05 10 .-.-.----.-. see section Application IDs for commands.----. to monitor at both directions..-...-.----------- DN0479352 Issue 4-2 Id:0900d805806444bc 75 .-.-.-. emm dsp:1:1 pq2:1 0 12 "01 02 03 04" Execution printouts BCSU/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 Monitored at : Receiver Source : DSP:0:5 Destination : PQ2:15 Message ID : 439 Message Header : -------.PCU2 Service Terminal Commands Service terminal commands dst id This parameter specifies the destination application ID to which the message needs to be sent.-.-..-. Enable message monitoring from application 1 at PQII to application 1 on DSP 1 for message type as 12.-. For the application IDs..-0:2:36:218844] -.Monitor message at sender 2 .-.Monitor message at receiver Examples 1..-.-.Monitor message at both directions 1 . to monitor at both directions. .-.-00000000 00 01 00 01 30 22 AF 22 00 00000010 00 02 -------.-..-.-....-. Valid values are: 0 .-. emm pq2:1 dsp:1:1 0 12 2.-. direction_flag This parameter specifies the direction in which the monitoring is to be done. payload offset This parameter specifies the offset from which the comparison is to begin. emm pq2:1 dsp:1:1 1 12 3.-. to monitor at receiver.-.-.-..

Service terminal commands

PCU2 Service Terminal Commands

Message Payload : 00000000 00 00 15 00000010 5B E0 5B 00000020 5B D8 5B 00000030 5B D0 5B 00000040 5B C8 5B 00000050 5B C0 5B 00000060 5B B8 5B 00000070 5B B0 5B 00000080 5B A8 5B 00000090 5B A0 5B 000000A0 5B 98 5B 000000B0 5B 90 5B 000000C0 5B 88 5B 000000D0 5B 80 5B 000000E0 5B 78 5B 000000F0 5B 70 5B 00000100 5B 68 5B 00000110 5B 60 5B 00000120 5B 58 5B 00000130 5B 50 5B 00000140 5B 48 5B 00000150 5B 40 5B 00000160 5B 38 5B 00000170 5B 30 5B 00000180 5B 28 5B 00000190 5B 20 5B 000001A0 5B 18 5B 000001B0 5B 10 5B 000001C0 5B 08 5B 000001D0 5B 00 5A 000001E0 5A F8 5A 000001F0 5A F0 5A 00000200 5A E8 5A 00000210 5A E0 5A 00000220 5A D8 5A 00000230 5A D0 5A 00000240 5A C8 5A 00000250 5A C0 5A 00000260 5A B8 5A 00000270 00 00 00 00000280 00 07 00 00000290 00 00 00 000002A0 00 00 5A 000002B0 5A 90 5A 000002C0 5A 88 5A 000002D0 5A 80 5A 000002E0 5A 78 5A 000002F0 5A 70 5A 00000300 5A 68 5A 00000310 5A 60 5A 00000320 5A 58 5A 00000330 5A 50 5A 00000340 5A 48 5A 00000350 5A 40 5A 00000230 5A D0 5A 00000240 5A C8 5A 00000250 5A C0 5A 00000260 5A B8 5A 00000270 00 00 00 00000280 00 07 00 00000290 00 00 00 000002A0 00 00 5A 000002B0 5A 90 5A 000002C0 5A 88 5A 000002D0 5A 80 5A

-------6A 00 00 DF 5B DE D7 5B D6 CF 5B CE C7 5B C6 BF 5B BE B7 5B B6 AF 5B AE A7 5B A6 9F 5B 9E 97 5B 96 8F 5B 8E 87 5B 86 7F 5B 7E 77 5B 76 6F 5B 6E 67 5B 66 5F 5B 5E 57 5B 56 4F 5B 4E 47 5B 46 3F 5B 3E 37 5B 36 2F 5B 2E 27 5B 26 1F 5B 1E 17 5B 16 0F 5B 0E 07 5B 06 FF 5A FE F7 5A F6 EF 5A EE E7 5A E6 DF 5A DE D7 5A D6 CF 5A CE C7 5A C6 BF 5A BE B7 5A B6 01 B1 FF 08 00 00 00 00 07 97 5A 96 8F 5A 8E 87 5A 86 7F 5A 7E 77 5A 76 6F 5A 6E 67 5A 66 5F 5A 5E 57 5A 56 4F 5A 4E 47 5A 46 3F 5A 3E CF 5A CE C7 5A C6 BF 5A BE B7 5A B6 01 B1 FF 08 00 00 00 00 07 97 5A 96 8F 5A 8E 87 5A 86 7F 5A 7E

-00 5B 5B 5B 5B 5B 5B 5B 5B 5B 5B 5B 5B 5B 5B 5B 5B 5B 5B 5B 5B 5B 5B 5B 5B 5B 5B 5B 5B 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A F0 00 00 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A F0 00 00 5A 5A 5A 5A

-00 DD D5 CD C5 BD B5 AD A5 9D 95 8D 85 7D 75 6D 65 5D 55 4D 45 3D 35 2D 25 1D 15 0D 05 FD F5 ED E5 DD D5 CD C5 BD B5 5F 01 08 95 8D 85 7D 75 6D 65 5D 55 4D 45 3D CD C5 BD B5 5F 01 08 95 8D 85 7D

-5B 5B 5B 5B 5B 5B 5B 5B 5B 5B 5B 5B 5B 5B 5B 5B 5B 5B 5B 5B 5B 5B 5B 5B 5B 5B 5B 5B 5B 5A 5A 5A 5A 5A 5A 5A 5A 5A 00 00 B1 00 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 00 00 B1 00 5A 5A 5A 5A

-E4 DC D4 CC C4 BC B4 AC A4 9C 94 8C 84 7C 74 6C 64 5C 54 4C 44 3C 34 2C 24 1C 14 0C 04 FC F4 EC E4 DC D4 CC C4 BC 00 00 FF 00 94 8C 84 7C 74 6C 64 5C 54 4C 44 3C CC C4 BC 00 00 FF 00 94 8C 84 7C

-5B 5B 5B 5B 5B 5B 5B 5B 5B 5B 5B 5B 5B 5B 5B 5B 5B 5B 5B 5B 5B 5B 5B 5B 5B 5B 5B 5B 5B 5A 5A 5A 5A 5A 5A 5A 5A 5A 00 5A F0 00 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 00 5A F0 00 5A 5A 5A 5A

-E3 DB D3 CB C3 BB B3 AB A3 9B 93 8B 83 7B 73 6B 63 5B 53 4B 43 3B 33 2B 23 1B 13 0B 03 FB F3 EB E3 DB D3 CB C3 BB 00 AB 5F 01 93 8B 83 7B 73 6B 63 5B 53 4B 43 3B CB C3 BB 00 AB 5F 01 93 8B 83 7B

-5B 5B 5B 5B 5B 5B 5B 5B 5B 5B 5B 5B 5B 5B 5B 5B 5B 5B 5B 5B 5B 5B 5B 5B 5B 5B 5B 5B 5B 5A 5A 5A 5A 5A 5A 5A 5A 5A 00 00 00 B1 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 00 00 00 B1 5A 5A 5A 5A

-E2 DA D2 CA C2 BA B2 AA A2 9A 92 8A 82 7A 72 6A 62 5A 52 4A 42 3A 32 2A 22 1A 12 0A 02 FA F2 EA E2 DA D2 CA C2 BA 06 00 00 FF 92 8A 82 7A 72 6A 62 5A 52 4A 42 3A CA C2 BA 06 00 00 FF 92 8A 82 7A

-5B 5B 5B 5B 5B 5B 5B 5B 5B 5B 5B 5B 5B 5B 5B 5B 5B 5B 5B 5B 5B 5B 5B 5B 5B 5B 5B 5B 5B 5A 5A 5A 5A 5A 5A 5A 5A 5A 00 00 5A F0 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 00 00 5A F0 5A 5A 5A 5A

-E1 D9 D1 C9 C1 B9 B1 A9 A1 99 91 89 81 79 71 69 61 59 51 49 41 39 31 29 21 19 11 09 01 F9 F1 E9 E1 D9 D1 C9 C1 B9 08 00 A1 5F 91 89 81 79 71 69 61 59 51 49 41 39 C9 C1 B9 08 00 A1 5F 91 89 81 79

-- -- -- -- -- -- ----- ----------...j....[.[.[.[. [.[.[.[.[.[.[.[. [.[.[.[.[.[.[.[. [.[.[.[.[.[.[.[. [.[.[.[.[.[.[.[. [.[.[.[.[.[.[.[. [.[.[.[.[.[.[.[. [.[.[.[.[.[.[.[. [.[.[.[.[.[.[.[. [.[.[.[.[.[.[.[. [.[.[.[.[.[.[.[. [.[.[.[.[.[.[.[. [.[.[.[.[.[.[.[. [.[.[~[}[|[{[z[y [x[w[v[u[t[s[r[q [p[o[n[m[l[k[j[i [h[g[f[e[d[c[b[a [`[_[^[][\[[[Z[Y [X[W[V[U[T[S[R[Q [P[O[N[M[L[K[J[I [H[G[F[E[D[C[B[A [@[?[>[=[<[;[:[9 [8[7[6[5[4[3[2[1 [0[/[.[-[,[+[*[) [(['[&[%[$[#["[! [ [.[.[.[.[.[.[. [.[.[.[.[.[.[.[. [.[.[.[.[.[.[.[. [.[.[.[.[.[.[.[. [.Z.Z.Z.Z.Z.Z.Z. Z.Z.Z.Z.Z.Z.Z.Z. Z.Z.Z.Z.Z.Z.Z.Z. Z.Z.Z.Z.Z.Z.Z.Z. Z.Z.Z.Z.Z.Z.Z.Z. Z.Z.Z.Z.Z.Z.Z.Z. Z.Z.Z.Z.Z.Z.Z.Z. Z.Z.Z.Z.Z.Z.Z.Z. Z.Z.Z.Z.Z.Z.Z.Z. Z.Z.Z.Z......... ......._..Z..... ..........._..Z. ..............._ ..Z.Z.Z.Z.Z.Z.Z. Z.Z.Z.Z.Z.Z.Z.Z. Z.Z.Z.Z.Z.Z.Z.Z. Z.Z.Z~Z}Z|Z{ZzZy ZxZwZvZuZtZsZrZq ZpZoZnZmZlZkZjZi ZhZgZfZeZdZcZbZa Z`Z_Z^Z]Z\Z[ZZZY ZXZWZVZUZTZSZRZQ ZPZOZNZMZLZKZJZI ZHZGZFZEZDZCZBZA Z@Z?Z>Z=ZZ.Z.Z.Z.Z.Z.Z.Z. Z.Z.Z.Z.Z.Z.Z.Z. Z.Z.Z.Z.Z.Z.Z.Z. Z.Z.Z.Z.Z.Z.Z.Z. Z.Z.Z.Z......... ......._..Z..... ..........._..Z. ..............._ ..Z.Z.Z.Z.Z.Z.Z. Z.Z.Z.Z.Z.Z.Z.Z. Z.Z.Z.Z.Z.Z.Z.Z. Z.Z.Z~Z}Z|Z{ZzZy

76

Id:0900d805806444bc

DN0479352 Issue 4-2

PCU2 Service Terminal Commands

Service terminal commands

000002E0 000002F0 00000300 00000310 00000320 00000330 00000340 00000350 00000360 00000370 00000380 00000390 000003A0 000003B0 000003C0 000003D0 000003E0 000003F0 00000400 00000410 00000420 00000430 00000440 00000450 00000460 00000470 00000480 00000490 000004A0 000004B0 000004C0 000004D0 000004E0 000004F0 00000500 --------

5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 59 59 59 59 59 59 59 59 59 59 59 59 59 59 59 59 59 59 05 --

78 70 68 60 58 50 48 40 38 30 28 20 18 10 08 00 F8 F0 E8 E0 D8 D0 C8 C0 B8 B0 A8 A0 98 90 88 80 78 70 10 --

5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 59 59 59 59 59 59 59 59 59 59 59 59 59 59 59 59 59 59 00 00 --

77 6F 67 5F 57 4F 47 3F 37 2F 27 1F 17 0F 07 FF F7 EF E7 DF D7 CF C7 BF B7 AF A7 9F 97 8F 87 7F 77 01 02 --

5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 59 59 59 59 59 59 59 59 59 59 59 59 59 59 59 59 59 59 00 00 --

76 6E 66 5E 56 4E 46 3E 36 2E 26 1E 16 0E 06 FE F6 EE E6 DE D6 CE C6 BE B6 AE A6 9E 96 8E 86 7E 76 01 00 --

5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 59 59 59 59 59 59 59 59 59 59 59 59 59 59 59 59 59 59 30 15 --

75 6D 65 5D 55 4D 45 3D 35 2D 25 1D 15 0D 05 FD F5 ED E5 DD D5 CD C5 BD B5 AD A5 9D 95 8D 85 7D 75 22 57 --

5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 59 59 59 59 59 59 59 59 59 59 59 59 59 59 59 59 59 00 AF 00 --

74 6C 64 5C 54 4C 44 3C 34 2C 24 1C 14 0C 04 FC F4 EC E4 DC D4 CC C4 BC B4 AC A4 9C 94 8C 84 7C FF 22 FF --

5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 59 59 59 59 59 59 59 59 59 59 59 59 59 59 59 59 59 00 00 00 --

73 6B 63 5B 53 4B 43 3B 33 2B 23 1B 13 0B 03 FB F3 EB E3 DB D3 CB C3 BB B3 AB A3 9B 93 8B 83 7B FF 05 FF --

5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 59 59 59 59 59 59 59 59 59 59 59 59 59 59 59 59 59 00 00 00 --

72 6A 62 5A 52 4A 42 3A 32 2A 22 1A 12 0A 02 FA F2 EA E2 DA D2 CA C2 BA B2 AA A2 9A 92 8A 82 7A FF 0F FF --

5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 59 59 59 59 59 59 59 59 59 59 59 59 59 59 59 59 59 00 01 00 --

71 69 61 59 51 49 41 39 31 29 21 19 11 09 01 F9 F1 E9 E1 D9 D1 C9 C1 B9 B1 A9 A1 99 91 89 81 79 FF B7 FF --

ZxZwZvZuZtZsZrZq ZpZoZnZmZlZkZjZi ZhZgZfZeZdZcZbZa Z`Z_Z^Z]Z\Z[ZZZY ZXZWZVZUZTZSZRZQ ZPZOZNZMZLZKZJZI ZHZGZFZEZDZCZBZA Z@Z?Z>Z=Z<Z;Z:Z9 Z8Z7Z6Z5Z4Z3Z2Z1 Z0Z/Z.Z-Z,Z+Z*Z) Z(Z'ZZ&Z%Z$Z#Z"Z! Z Z.Z.Z.Z.Z.Z.Z. Z.Z.Z.Z.Z.Z.Z.Z. Z.Z.Z.Z.Z.Z.Z.Z. Z.Z.Z.Z.Z.Z.Z.Z. Z.Y.Y.Y.Y.Y.Y.Y. Y.Y.Y.Y.Y.Y.Y.Y. Y.Y.Y.Y.Y.Y.Y.Y. Y.Y.Y.Y.Y.Y.Y.Y. Y.Y.Y.Y.Y.Y.Y.Y. Y.Y.Y.Y.Y.Y.Y.Y. Y.Y.Y.Y.Y.Y.Y.Y. Y.Y.Y.Y.Y.Y.Y.Y. Y.Y.Y.Y.Y.Y.Y.Y. Y.Y.Y.Y.Y.Y.Y.Y. Y.Y.Y.Y.Y.Y.Y.Y. Y.Y.Y.Y.Y.Y.Y.Y. Y.Y.Y.Y.Y.Y.Y.Y. Y.Y.Y.Y.Y.Y.Y.Y. Y.Y.Y.Y.Y.Y.Y.Y. Y.Y.Y.Y.Y.Y.Y.Y. Y.Y.Y~Y}Y|Y{YzYy YxYwYvYu........ Yp....0"."...... .......W........ ----------------

2.9.2

dmm (disable message monitoring)
Function With this command you deactivate the message monitoring with the desired filtering criteria. The full form of this command is disable message monitoring (dmm). Syntax

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

Parameter explanations processor type This parameter specifies the card type. If it is specified to src ID, it specifies the src processor type. In other cases, it specifies the dst processor type. The allowable values are 'pq2', 'bsc' and 'dsp'. dsp id This parameter specifies the DSP ID. This parameter is to be specified only in case the processor type is DSP. src id

DN0479352 Issue 4-2

Id:0900d805806444bc

77

Service terminal commands

PCU2 Service Terminal Commands

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 commands. 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 printouts BCSU/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)
Function The full form of this command is display message monitoring configuration (dimm).

78

Id:0900d805806444bc

DN0479352 Issue 4-2

DN0479352 Issue 4-2 Id:0900d805806444bc 79 . dsp id This parameter specifies the DSP ID. The allowable values are 'pq2' and 'dsp'. damm Execution printouts BCSU/0/PCU/0/OSE>damm ---------------------------------------------------------------> Command damm executed on [1/1/2004 0:0:53:831634] <--------------------------------------------------------------Disabled all message monitoring. dimm pq2 2. "mask_val"] [dir_flag] pq2:* pq2:* [*] [NA][->] 2.4 damm (disable all message monitoring) Function The full form of this command is disable all message monitoring (damm).. Disable all message monitoring. Examples 1.. Display the message monitoring configuration for pq2.9. The values range from 0 to 7. dimm dsp:1 Execution printouts BCSU/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. The parameter needs to be specified only in case the processor type is DSP. Syntax damm Examples 1.PCU2 Service Terminal Commands Service terminal commands Syntax dimm <processor type>{:<dsp id>} Parameter explanations processor type This parameter specifies the processor type on which the application is residing. Display the message monitoring configuration for DSP ID '1'.

5 emml (enable MM data logging) Function With this command you log the output of all the MM messages. Use this command with care and only when necessary.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. 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. Syntax emml <filename> <size_in _bytes> Parameter explanations filename The name of the file in which the logs are to be captured.9. The filename must have the extension '. size_in_bytes The maximum size of the file. ! Running this command may affect the system performance.log' with size of 5000 bytes.log'. Examples 1.6 dmml (disable MM data logging) Function The full form of this command is disable MM data logging (dmml). emml st_mm_logs.9. In case the logs exceed the maximum file size. 80 Id:0900d805806444bc DN0479352 Issue 4-2 . Enable message monitoring logging to a file named 'st_mm_logs. the file is wrapped around.log 5000 Execution printouts BCSU/0/PCU/0/OSE/ML>emml 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.Service terminal commands PCU2 Service Terminal Commands 2.

10 IP manipulation commands This section contains the commands which apply to the IP manipulation category of the service terminal. dmml Execution printouts BCSU/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.PCU2 Service Terminal Commands Service terminal commands Syntax dmml Examples 1. 2. Disable the message monitoring logging to a file.1 ifconfig Function With this command you configure the network interface and/or configure network interface parameters. Syntax ifconfig <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 DN0479352 Issue 4-2 Id:0900d805806444bc 81 . It can also be used to change/display the IP address of the PIU.10. The commands are provided by the IPNET IP stack.

d> Set interface netmask to 'a.d' (inet only). 'inet' or 'inet6'. delete <a> Delete 'a' IPv4 or IPv6 address. dstaddr <a> Set remote address to 'a' (inet and PPP only). Note that the interface must be down first. address The IPv4 or IPv6 address.b.c. mtu <v> Set interface MTU to 'v'. family Address family.c. dhcp Enable dhcp auto configuration (inet only).b. up Bring the interface up.Service terminal commands PCU2 Service Terminal Commands or ifconfig <interface> -dhcp or ifconfig <interface> rtab <value> or ifconfig [<interface> | -a] Parameter explanations –a List all interfaces. netmask <a. 82 Id:0900d805806444bc DN0479352 Issue 4-2 . add <a> Add 'a' IPv4 or IPv6 address. down Bring the interface down. -dhcp Disable dhcp auto configuration (inet only). rtab <v> Set route table index to 'v' (default = 0). value Numeric value depending on the command. detach Detaches the interface. interface Name of the interface.

PCU2 Service Terminal Commands Service terminal commands prefixlen <value> Set interface prefix (mask length) length to 'n'.0.2 netstat Function With this command you query the information about the interfaces on a system.0 broadcast 10.0. Display the configuration of all the interfaces. ifconfig -a Execution printouts BCSU/31/PCU/4/OSE>ifconfig -a lo Link type:Local loopback Queue:None inet 127.8. Syntax netstat [-anh] [-f address_family] [-p protocol] DN0479352 Issue 4-2 Id:0900d805806444bc 83 .255.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.102 mask 255.10.255.0.201.0. The command displays current TCP/IP network connections and protocol statistics.201.1 mask 255. tentative Perform DAD before setting address (inet6 only). Examples 1. 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.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.8.

The following address families are recognized: inet for IP_AF_INET and inet6 for IP_AF_INET6.0.0.0.* Foreign Address 0. -h This parameter displays help for the usage menu. input and output packets and errors.0.0. etc. -p protocol This parameter displays statistics for a protocol.0. collisions and size of output queue.0. the default is 0. The default is to look up symbolic names for the addresses. -n This parameter displays the network addresses as numbers. If the value is not specified. Display the configuration of all the interfaces.* ICMP 23 0 0. -f address_family This parameter limits the statistics or address control block reports to those of the specified address family.0. netstat -a 2. collisions and size of output queue. -v <routetab> This parameter specifies the routing table. Normally the sockets used by server processes are not shown. input and output packets and errors. -l With this parameter.* State 84 Id:0900d805806444bc DN0479352 Issue 4-2 . the routes are not displays where the LLINFO flag is set. Display interface information such as MTU.0. -r This parameter displays the routing tables.* 0. netstat -r 3. You can enter either a well-known name for a protocol or an alias for it.Service terminal commands PCU2 Service Terminal Commands or netstat -r [-n] [-f address_family] Parameter explanations -a This parameter displays the state of all sockets. etc.0. Examples 1. netstat -i Execution printouts The execution printout for example 1 is the following: BCSU/0/PCU/0/OSE>netstat -a INET sockets Prot Fd Rt Local Address ICMP 22 0 0.0. Display the routing table.0. -i This parameter displays the interface information such as MTU.

* ::.49157 0.0.23 10.0.49158 127.0.0.2 10.0.0/8 127.0.0.3.3.3.3.0.1.0.0.0.0.PCU2 Service Terminal Commands Service terminal commands TCP TCP TCP TCP UDP UDP UDP UDP 11 25 27 28 10 19 20 21 0 0 0 0 0 0 0 0 0.0.0.0.1.* 0.5000 0.0.0.0.0.0.0.0.49156 0.0.* 0.0.* 0.0.49157 127.23 127.0.0.* BCSU/0/PCU/0/OSE> Foreign Address ::.20064 ::.* ::1.0.0.* State LISTEN The execution printout for example 2 is the following: BCSU/0/PCU/0/OSE>netstat -r INET route table Destination 0.1.1907 127.0.0.1 224.3.0.0/0 10.0.255 Gateway 10.0.0.0.190.0/24 10.3.0.0.0.0.140.0.0.3.49155 0.0.140 127.255.3.0/4 255.0.* 192.0.0.2 link#2 00:0d:28:22:ff:ff link#1 link#1 link#1 * * Flags UGS UC UHL UH URS UH R HR Use If 20993 ifeth0 12 11 0 0 7436 0 0 ifeth0 ifeth0 lo lo lo * * INET6 route table Destination ::1 FE80::%lo/64 FE80::%ifeth0/64 Gateway link#1 link#1 link#2 Flags UH UC UC Use 4 0 0 If lo lo ifeth0 DN0479352 Issue 4-2 Id:0900d805806444bc 85 .* 0.1.3.* ICMP6 24 0 ::.20065 ICMP6 13 0 ::.255.3.49158 0.0.23 UDP 14 0 ::1.* LISTEN ESTABLISHED ESTABLISHED ESTABLISHED INET6 sockets Prot Fd Rt Local Address TCP 12 0 ::.168.

0.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> 86 Id:0900d805806444bc DN0479352 Issue 4-2 .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 0 ifeth0 1500 10.0/8 127.0.3.0/24 10.3.3.Service terminal commands PCU2 Service Terminal Commands FE80::%ifeth1/64 FE80::1%lo link#3 link#1 UC UH UH UH U U U U U 0 0 0 0 0 0 0 4 4 ifeth1 lo lo lo lo lo lo ifeth0 ifeth FE80::1814:18FF:FE17:1916%ifeth1 link#1 FE80::1814:18FF:FE17:1A15%ifeth0 link#1 FF00::/8 FF01::/16 FF02::%lo/16 FF02::%ifeth0/16 FF02::%ifeth1/16 BCSU/0/PCU/0/OSE> link#1 link#1 link#1 link#2 link#3 The execution printout for example 3 is the following: BCSU/0/PCU/0/OSE>netstat -i Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll Iqdrops Noproto lo 1500 127.0.0.

The program also measures the round trip time to the host. If the value is not specified. No attempts will be made to look up names for the host addresses. DN0479352 Issue 4-2 Id:0900d805806444bc 87 . Syntax ping [-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. -c count This parameter stops after sending count ECHO_RESPONSE packets. the default is 0.10.PCU2 Service Terminal Commands Service terminal commands 2. the default is 1000 ms. -D This parameter sets the DF (do not fragment) flag on each sent ping request. -w This parameter specifies the timeout in milliseconds. ping uses the ICMPv4 protocol's mandatory ECHO_REQUEST datagram to elicit an ECHO_REPLY from a host or a gateway. The default is 56. -n This parameter outputs numeric data only. you can use the specified time-to-live.3 ping Function With this command you test whether another host is reachable or not. which translates into 64 ICMP data bytes when combined with the 8 bytes of the ICMP header data. -r This parameter bypasses the normal routing tables and sends directly to a host on an attached network. giving some indication of how far away that host is. -T ttl With this parameter. -s packetsize This parameter specifies the number of data bytes to be sent. -b This parameter allows the pinging of a broadcast address. -S src_addr This parameter specifies the address to be used as a source address when sending. The program sends ICMPv4 ECHO_REQUEST packets to network hosts and expects a reply from the host in return. -V This parameter specifies the routing table. -t This parameter pings the specified host until stopped. It also displays ttl (time to live) and round trip time.

3.3.3.2 bytes=64 time=1ms ttl=255 Reply from 10.3.2) with 128 bytes of data: Reply from 10.2 bytes=64 time=2ms ttl=255 Reply from 10. ping -s 128 10.3.3.3.3.3.3.3.3.2 ---------------------------------------------------------------> Command ping executed on [30/11/2005 18:53:21:710875] <--------------------------------------------------------------Pinging 10. ping -c 5 10.3.2.2 bytes=128 time=3ms ttl=255 BCSU/0/PCU/0/OSE> The execution printout for example 3 is the following: BCSU/0/PCU/0/OSE>ping -c 5 10.2 (10.3.2 (10.3.3.3.3.3.3.3.3.2 bytes=128 time=2ms ttl=255 Reply from 10.3.3.3.3.3. Send ECHO_REQUEST packets to 10.2 Execution printouts The execution printout for example 1 is the following: BCSU/0/PCU/0/OSE>ping 10.3.2) with 64 bytes of data: Reply from 10.3.2) with 64 bytes of data: Reply from 10.2 3.3.3.3.2 bytes=64 time=2ms ttl=255 BCSU/0/PCU/0/OSE> The execution printout for example 2 is the following: BCSU/0/PCU/0/OSE>ping -s 128 10.2 bytes=64 time=2ms ttl=255 Reply from 10.3.2 bytes=128 time=3ms ttl=255 Reply from 10.3.2 bytes=128 time=3ms ttl=255 Reply from 10.2 bytes=64 time=3ms ttl=255 BCSU/0/PCU/0/OSE> 88 Id:0900d805806444bc DN0479352 Issue 4-2 .3.3.2 with 128 as the packet size.3.3.3.2 ---------------------------------------------------------------> Command ping executed on [30/11/2005 18:53:21:710875] <--------------------------------------------------------------Pinging 10.2 bytes=64 time=3ms ttl=255 Reply from 10.3.2 bytes=64 time=2ms ttl=255 Reply from 10.2 so that the sending is stopped after 5 packets.Service terminal commands PCU2 Service Terminal Commands Examples 1.3.2 2.3.2 (10.3.3.3.3.3.3.3.3.2 bytes=64 time=2ms ttl=255 Reply from 10.2 ---------------------------------------------------------------> Command ping executed on [30/11/2005 18:53:21:710875] <--------------------------------------------------------------Pinging 10. ping 10.3.3.2 bytes=64 time=2ms ttl=255 Reply from 10.3. Send ECHO_REQUEST packets to 10.3. Send ECHO_REQUEST packets to 10.3.3.

the default is 1000 ms. -n This parameter outputs numeric data only. ping6 uses the ICMPv6 protocol's mandatory ICMP6_ECHO_REQUEST datagram to elicit an ICMP6_ECHO_REPLY from a host or a gateway. ping6 -s 128 FF02::1 3. -r This parameter bypasses the normal routing tables and sends directly to a host on an attached network. -V routetab With this parameter you specify the routing table. If the value is not specified the default is 0.. Send ECHO_REQUEST packets to FF02::1 with 128 as the packet size. Examples 1..] host Parameter explanations -c count This parameter stops after sending count ECHO_RESPONSE packets. -t This parameter pings the specified host until stopped.10. ICMP6_ECHO_REQUEST datagrams (“pings”) have an IPv6 header and an ICMPv6 header formatted as documented in RFC2463. Syntax ping6 [-n] [-c count] [-h hoplimit] [-s packetsize] [hop . ping6 -c 5 FF02::1 DN0479352 Issue 4-2 Id:0900d805806444bc 89 . The default is 56.PCU2 Service Terminal Commands Service terminal commands 2. This is accomplished by adding a routing header to the packet. Send ECHO_REQUEST packets to FF02::1. -w timeout This parameter specifies the timeout in milliseconds. No attempts will be made to look up names for host addresses. -h hoplimit With this parameter you set the IPv6 hop limit. The program sends ICMPv6 ECHO_REQUEST packets to network hosts and expects a reply from the host in return. ping6 FF02::1 2. -s packetsize This parameter specifies the number of data bytes to be sent. which translates into 64 ICMP data bytes when combined with the 8 bytes of the ICMP header data. Send ECHO_REQUEST packets to FF02::1 so that the sending is stopped after 5 packets. It is possible to specify additional nodes that the ping request must visit before reaching its final destination.4 ping6 Function With this command you test whether another host is reachable or not.

They are helpful in examining the current network configuration and its related problems.Service terminal commands PCU2 Service Terminal Commands Execution printouts The execution printout for example 1 is the following: 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=255 BCSU/0/PCU/0/OSE> The execution printout for example 2 is the following: 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> The execution printout for example 3 is the following: 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=255 Reply from FE80::1 bytes=64 time=0ms hlim=255 BCSU/0/PCU/0/OSE> 2.11 Radio network–related commands This section contains the commands for radio network configuration display. 90 Id:0900d805806444bc DN0479352 Issue 4-2 .

trx id This parameter specifies the TRX ID.1 dtrxrnw (display the radio network configuration for a particular TRX) Function With this command you display the radio network configuration for a particular TRX (dtrxrnw). dtrxrnw 613 10 Execution printouts The execution printout for example 1 is the following: 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 1900 TX_Power:15 Hopping:NO Territory_Type:EGPRS_CS1_CS4 DSP Id : 0 CONTR_BCSU_ADDR : 16731 E-TRX : NO DLDC TRX : YES Num_of_PSW_TSLs:5 TSL_3:DEDICATED TSL_4:DEDICATED TSL_5:DEDICATED TSL_6:DEDICATED TSL_7:DEDICATED EDAP id : 613 Ext PCM Line of the SMCH : 8137 Ext PCM TSL (64 K) of the SMCH : 14 Ext PCM STSL (16 K) of the SMCH : 0 BTS id of SMCH: 613 TRX id of SMCH: 9 RTSL of SMCH : 7 BCSU/30/PCU/4/OSE> The execution printout for example 2 is the following: DN0479352 Issue 4-2 Id:0900d805806444bc 91 .PCU2 Service Terminal Commands Service terminal commands 2. Display the radio network configuration with BTS ID '613' and TRX ID '10'. Syntax dtrxrnw <bts id> <trx id> Parameter explanations bts id This parameter specifies the BTS ID. Examples 1.11. Display the radio network configuration with BTS ID '613' and TRX ID '9'. dtrxrnw 613 9 2.

Display the radio network configuration for BTS ID '613'.Service terminal commands PCU2 Service Terminal Commands 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 1900 TX_Power:15 Hopping:NO Territory_Type:EGPRS_CS1_CS4 DSP Id : 0 CONTR_BCSU_ADDR : 16731 E-TRX : YES DLDC TRX : NO Num_of_PSW_TSLs:6 TSL_2:EGTCH TSL_3:EGTCH TSL_4:EGTCH TSL_5:EGTCH TSL_6:EGTCH TSL_7:EGTCH EDAP id : 613 Ext PCM Line of the SMCH : 8137 Ext PCM TSL (64 K) of the SMCH : 14 Ext PCM STSL (16 K) of the SMCH : 0 BTS id of SMCH: 613 TRX id of SMCH: 9 RTSL of SMCH : 7 BCSU/30/PCU/4/OSE> 2.2 dbtsrnw (display the radio network configuration for a particular BTS) Function With this command you display the radio network configuration for a particular BTS (dbtsrnw). Syntax dbtsrnw <bts id> Parameter explanations bts id This parameter specifies the BTS ID.11. dbtsrnw 613 Execution printouts BCSU/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:YES Num_Default_TSLs:11 Num_Dedicated_TSLs:11 92 Id:0900d805806444bc DN0479352 Issue 4-2 . Examples 1.

PCU2 Service Terminal Commands Service terminal commands NUM_EGTCH: 0 Actual_Num_of_TSLs_for_PSW:11 BCCH_TRX_BCSU: 16731 INITIAL MCS FOR ACKNOWLEDGED MODE : MCS1 INITIAL MCS FOR UNACKNOWLEDGED MODE : MCS1 DL CODING SCHEME IN ACKNOWLEDGED MODE : CS2 UL CODING SCHEME IN ACKNOWLEDGED MODE : CS2 DL CODING SCHEME IN UNACKNOWLEDGED MODE: CS2 UL CODING SCHEME IN UNACKNOWLEDGED MODE: CS2 Num_TRX:2 Num_E_TRX:0 DLDC Enabled:YES BTS_ID:613 TRX_ID:9 ARFCN:640 Access Tech:GSM 1900 TX_Power:15 Hopping:NO Territory_Type:EGPRS_CS1_CS4 DSP Id : 0 CONTR_BCSU_ADDR : 16731 E-TRX : NO DLDC TRX : YES Num_of_PSW_TSLs:5 TSL_3:DEDICATED TSL_4:DEDICATED TSL_5:DEDICATED TSL_6:DEDICATED TSL_7:DEDICATED EDAP id : 613 Ext PCM Line of the SMCH : 8137 Ext PCM TSL (64 K) of the SMCH : 14 Ext PCM STSL (16 K) of the SMCH : 0 BTS id of SMCH: 613 TRX id of SMCH: 9 RTSL of SMCH : 7 BTS_ID:613 TRX_ID:10 ARFCN:645 Access Tech:GSM 1900 TX_Power:15 Hopping:NO Territory_Type:EGPRS_CS1_CS4 DSP Id : 0 CONTR_BCSU_ADDR : 16731 E-TRX : NO DLDC TRX : YES Num_of_PSW_TSLs:6 TSL_2: DEDICATED TSL_3: DEDICATED TSL_4: DEDICATED TSL_5: DEDICATED TSL_6: DEDICATED TSL_7: DEDICATED EDAP id : 613 Ext PCM Line of the SMCH : 8137 Ext PCM TSL (64 K) of the SMCH : 14 Ext PCM STSL (16 K) of the SMCH : 0 BTS id of SMCH: 613 TRX id of SMCH: 9 RTSL of SMCH : 7 BCSU/30/PCU/4/OSE> DN0479352 Issue 4-2 Id:0900d805806444bc 93 .

Syntax dsegrnw <segment id> Parameter explanations segment id This parameter specifies the segment ID.Service terminal commands PCU2 Service Terminal Commands 2.11. Display the radio network configuration for segment ID '613'. Examples 1.3 dsegrnw (display the radio network configuration for a particular segment) Function With this command you display the radio network configuration for a particular segment (dsegrnw). dsegrnw 613 Execution printouts BCSU/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:16731 Num_GRPS_TSLs:0 Num_EGRPS_TSLs:11 PCCCH_BTS:613 PCCCH_TRX:9 PCCCH_TSL:Not Configured PCCCH_DSP_ID:Not Configured NC Mode : 0 Ext Cell: NO SEG_ID:613 BTS_ID:613 Access_Tech:GSM 1900 Edge_Capable:YES Num_Default_TSLs:11 Num_Dedicated_TSLs:11 NUM_EGTCH: 0 Actual_Num_of_TSLs_for_PSW:11 BCCH_TRX_BCSU: 16731 INITIAL MCS FOR ACKNOWLEDGED MODE : MCS1 INITIAL MCS FOR UNACKNOWLEDGED MODE : MCS1 DL CODING SCHEME IN ACKNOWLEDGED MODE : CS2 UL CODING SCHEME IN ACKNOWLEDGED MODE : CS2 DL CODING SCHEME IN UNACKNOWLEDGED MODE: CS2 UL CODING SCHEME IN UNACKNOWLEDGED MODE: CS2 Num_TRX:2 Num_E_TRX:0 DLDC Enabled:YES BTS_ID:613 TRX_ID:9 ARFCN:640 Access Tech:GSM 1900 TX_Power:15 Hopping:NO Territory_Type:EGPRS_CS1_CS4 DSP Id : 0 CONTR_BCSU_ADDR : 16731 E-TRX : NO DLDC TRX : YES Num_of_PSW_TSLs:5 TSL_3:DEDICATED TSL_4:DEDICATED TSL_5:DEDICATED TSL_6:DEDICATED TSL_7:DEDICATED 94 Id:0900d805806444bc DN0479352 Issue 4-2 .

12.PCU2 Service Terminal Commands Service terminal commands EDAP id : 613 Ext PCM Line of the SMCH : 8137 Ext PCM TSL (64 K) of the SMCH : 14 Ext PCM STSL (16 K) of the SMCH : 0 BTS id of SMCH: 613 TRX id of SMCH: 9 RTSL of SMCH : 7 BTS_ID:613 TRX_ID:10 ARFCN:645 Access Tech:GSM 1900 TX_Power:15 Hopping:NO Territory_Type:EGPRS_CS1_CS4 DSP Id : 0 CONTR_BCSU_ADDR : 16731 E-TRX : NO DLDC TRX : YES Num_of_PSW_TSLs:6 TSL_2: DEDICATED TSL_3: DEDICATED TSL_4: DEDICATED TSL_5: DEDICATED TSL_6: DEDICATED TSL_7: DEDICATED EDAP id : 613 Ext PCM Line of the SMCH : 8137 Ext PCM TSL (64 K) of the SMCH : 14 Ext PCM STSL (16 K) of the SMCH : 0 BTS id of SMCH: 613 TRX id of SMCH: 9 RTSL of SMCH : 7 BCSU/30/PCU/4/OSE> 2.12 2. Examples 1.1 TBF information commands dsegtbf (display TBF allocation for a particular segment) Function With this command you display the TBF allocation for a particular segment (dsegtbf). Display the TBF allocation for segment ID '300'. Syntax dsegtbf <segment id> Parameter explanations segment id This parameter specifies the segment ID. dsegtbf 300 Execution printouts BCSU/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 DN0479352 Issue 4-2 Id:0900d805806444bc 95 .

Service terminal commands PCU2 Service Terminal Commands Num_GPRS_TSLs:0 Num_EGPRS_TSLs:8 PCCCH_BTS:300 PCCCH_TRX:1 PCCCH_TSL:Not Configured PCCCH_DSP_ID:Not Configured NC Mode : 0 Ext Cell: NO SEG_ID:300 BTS_ID:300 Access_Tech:GSM_P Edge_Capable:YES Num_Default_TSLs:23 Num_Dedicated_TSLs:23 NUM_EGTCH: 0 Actual_Num_of_TSLs_for_PSW:8 BCCH_TRX_BCSU: 16735 INITIAL MCS FOR ACKNOWLEDGED MODE IN NORMAL AREA : MCS6 INITIAL MCS FOR UNACKNOWLEDGED MODE IN NORMAL AREA : MCS5 INITIAL MCS FOR ACKNOWLEDGED MODE IN EXTENDED AREA : MCS1 INITIAL MCS FOR UNACKNOWLEDGED MODE IN EXTENDED AREA : MCS1 DL CODING SCHEME UL CODING SCHEME DL CODING SCHEME UL CODING SCHEME DL CODING SCHEME UL CODING SCHEME DL CODING SCHEME UL CODING SCHEME Num_TRX:2 Num_E_TRX:0 DLDC Enabled:YES IN IN IN IN IN IN IN IN ACKNOWLEDGED MODE IN NORMAL AREA: CS3 ACKNOWLEDGED MODE IN NORMAL AREA: CS3 UNACKNOWLEDGED MODE IN NORMAL AREA: CS2 UNACKNOWLEDGED MODE IN NORMAL AREA: CS2 ACKNOWLEDGED MODE IN EXTENDED AREA: CS1 ACKNOWLEDGED MODE IN EXTENDED AREA: CS1 UNACKNOWLEDGED MODE IN EXTENDED AREA: CS1 UNACKNOWLEDGED MODE IN EXTENDED AREA: CS1 BTS_ID:300 TRX_ID:1 ARFCN:1 Access Tech:GSM_P TX_Power:0 Hopping:NO Territory_Type:EGPRS_CS1_CS2 DSP Id : 0 CONTR_BCSU_ADDR : 16735 E-TRX : NO DLDC TRX : YES Num_of_PSW_TSLs:4 TSL_4:DEDICATED TSL_5:DEDICATED TSL_6:DEDICATED TSL_7:DEDICATED EDAP id : 300 Ext PCM Line of the SMCH : 8112 Ext PCM TSL (64 K) of the SMCH : 10 Ext PCM STSL (16 K) of the SMCH : 2 BTS id of SMCH: 300 TRX id of SMCH: 1 RTSL of SMCH : 5 BTS_ID:300 TRX_ID:3 ARFCN:5 Access Tech:GSM_P 96 Id:0900d805806444bc DN0479352 Issue 4-2 .

PCU2 Service Terminal Commands Service terminal commands TX_Power:0 DSP Id : 0 E-TRX : NO DLDC TRX : YES Hopping:NO Territory_Type:EGPRS_CS1_CS2 CONTR_BCSU_ADDR : 16735 Num_of_PSW_TSLs:4 TSL_4:DEDICATED TSL_5:DEDICATED TSL_6:DEDICATED TSL_7:DEDICATED EDAP id : 300 Ext PCM Line of the SMCH : 8112 Ext PCM TSL (64 K) of the SMCH : 10 Ext PCM STSL (16 K) of the SMCH : 2 BTS id of SMCH: 300 TRX id of SMCH: 1 RTSL of SMCH : 5 BTS ID TRX ID DSP ID MULTISLOT CLASS Direction RLC MODE TBF TSL NUM Allocated USF TBF STATE TBF ID TFI Coding Scheme TBF Data rate Direction RLC MODE TBF TSL NUM Allocated TBF STATE TBF ID TFI Coding Scheme TBF Data rate TLLI MS_INDEX IMSI TYPE NC Mode MS TSL_4 TSL_5 : : : : : : : : : : : : : : : : : : : : : : : : : : : : 300 [0x12c] 1 [0x1] 0 33 UPLINK ACK 6 7 127 127 127 127 127 PDM_ULTBF_ACTIVE 8 [0x8] 6 [0x6] MCS9 9.60 KB per sec 3221225480 [0xc0000008] 0x012cc0000008 244051090001003 EGPRS 0 DOWNLINK DOWNLINK 127 5 4 DN0479352 Issue 4-2 Id:0900d805806444bc 97 .99 KB per sec DOWNLINK ACK 4 5 6 7 PDM_DLTBF_ACTIVE 0 [0x0] 0 [0x0] MCS6 10.

trx id This parameter specifies the TRX ID. Syntax dtrxtbf <bts id> <trx id> Parameter explanations bts id This parameter specifies the BTS ID. dtrxtbf 300 3 Execution printouts BCSU/35/PCU/4/OSE> dtrxtbf 300 3 ---------------------------------------------------------------> Command dtrxtbf executed on [22/11/2008 16:19:56:313010] <---- 98 Id:0900d805806444bc DN0479352 Issue 4-2 .Service terminal commands PCU2 Service Terminal Commands TSL_6 TSL_7 PFI PFC ID DL Guranteed Data Rate DL RLC MODE PFC Traffic Class ARP PFI PFC ID UL Guranteed Data Rate UL RLC MODE PFC Traffic Class ARP DLDC ALLOCATION TRX ID 2 TSL NUM Allocated TSL_4 TSL_5 TSL_6 TSL_7 : : : : : : : : : : : : : : : : : : : : : CONCURRENT CONCURRENT 0 26684465 [0x1972c31] 0 ACK BEST_EFFORT ARP3 0 26684464 [0x1972c30] 0 ACK BEST_EFFORT ARP2 YES 3 [0x3] 4 5 6 DOWNLINK DOWNLINK DOWNLINK DOWNLINK 7 BCSU/35/PCU/4/OSE> 2. Examples 1. Display the TBF information for BTS ID '300' and TRX ID '3'.12.2 dtrxtbf (display the TBF information for a particular TRX) Function This command is used to display the TBF information for a particular TRX (dtrxtbf).

67 KB per sec 3221225480 [0xc0000008] 0x012cc0000008 244051090001003 EGPRS 0 DOWNLINK DOWNLINK CONCURRENT 127 6 3 DN0479352 Issue 4-2 Id:0900d805806444bc 99 .09 KB per sec DOWNLINK ACK 4 5 6 7 PDM_DLTBF_ACTIVE 0 [0x0] 21 [0x15] MCS6 10.PCU2 Service Terminal Commands Service terminal commands -----------------------------------------------------------BTS_ID:300 TRX_ID:3 ARFCN:5 Access Tech:GSM_P TX_Power:0 Hopping:NO Territory_Type:EGPRS_CS1_CS2 DSP Id : 0 CONTR_BCSU_ADDR : 16735 E-TRX : NO DLDC TRX : YES Num_of_PSW_TSLs:4 TSL_4:DEDICATED TSL_5:DEDICATED TSL_6:DEDICATED TSL_7:DEDICATED EDAP id : 300 Ext PCM Line of the SMCH : 8112 Ext PCM TSL (64 K) of the SMCH : 10 Ext PCM STSL (16 K) of the SMCH : 2 BTS id of SMCH: 300 TRX id of SMCH: 1 RTSL of SMCH : 5 BTS ID TRX ID DSP ID MULTISLOT CLASS Direction RLC MODE TBF TSL NUM Allocated USF TBF STATE TBF ID TFI Coding Scheme TBF Data rate Direction RLC MODE TBF TSL NUM Allocated TBF STATE TBF ID TFI Coding Scheme TBF Data rate TLLI MS_INDEX IMSI TYPE NC Mode MS TSL_4 TSL_5 TSL_6 : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 300 [0x12c] 1 [0x1] 0 33 UPLINK ACK 6 7 127 127 127 127 127 PDM_ULTBF_ACTIVE 8 [0x8] 11 [0xb] MCS9 10.

trx id This parameter specifies the TRX ID. Display the TBF information for BTS '300'. TSL '7' and TFI '21'.Service terminal commands PCU2 Service Terminal Commands TSL_7 PFI PFC ID DL Guranteed Data Rate DL RLC MODE PFC Traffic Class ARP PFI PFC ID UL Guranteed Data Rate UL RLC MODE PFC Traffic Class ARP DLDC ALLOCATION TRX ID 2 TSL NUM Allocated TSL_4 TSL_5 TSL_6 TSL_7 : : : : : : : : : : : : : : : : : : : : CONCURRENT 0 28388817 [0x1b12dd1] 0 ACK BEST_EFFORT ARP3 0 28388816 [0x1b12dd0] 0 ACK BEST_EFFORT ARP2 YES 3 [0x3] 4 5 6 DOWNLINK DOWNLINK DOWNLINK DOWNLINK 7 BCSU/35/PCU/4/OSE> 2. Syntax dtfitbf <bts id> <trx id> <tsl> <tfi> Parameter explanations bts id This parameter specifies the BTS ID. tsl This parameter specifies the TSL. TRX '3'.3 dtfitbf (display the TBF information specific to identified TFI) Function With this command you display the TBF information specific to identified temporary flow identity (TFI) (dtfitbf).12. tfi This parameter specifies the TFI. dtfitbf 300 3 7 21 100 Id:0900d805806444bc DN0479352 Issue 4-2 . Examples 1.

69 KB per sec 127 127 127 4 1 DN0479352 Issue 4-2 Id:0900d805806444bc 101 .PCU2 Service Terminal Commands Service terminal commands Execution printouts BCSU/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 TRX_ID:3 ARFCN:5 Access Tech:GSM_P TX_Power:0 Hopping:NO Territory_Type:EGPRS_CS1_CS2 DSP Id : 0 CONTR_BCSU_ADDR : 16735 E-TRX : NO DLDC TRX : YES Num_of_PSW_TSLs:4 TSL_4:DEDICATED TSL_5:DEDICATED TSL_6:DEDICATED TSL_7:DEDICATED EDAP id : 300 Ext PCM Line of the SMCH : 8112 Ext PCM TSL (64 K) of the SMCH : 10 Ext PCM STSL (16 K) of the SMCH : 2 BTS id of SMCH: 300 TRX id of SMCH: 1 RTSL of SMCH : 5 BTS ID TRX ID DSP ID MULTISLOT CLASS Direction RLC MODE TBF TSL NUM Allocated USF TBF STATE TBF ID TFI Coding Scheme TBF Data rate Direction RLC MODE TBF TSL NUM Allocated TBF STATE TBF ID TFI Coding Scheme TBF Data rate : : : : : : : : : : : : : : : : : : : : : 300 [0x12c] 1 [0x1] 0 33 UPLINK ACK 6 7 127 127 127 PDM_ULTBF_ACTIVE 8 [0x8] 17 [0x11] MCS9 0.01 KB per sec DOWNLINK ACK 4 5 6 7 PDM_DLTBF_ACTIVE 0 [0x0] 21 [0x15] MCS3 10.

tsl This parameter specifies the TSL. Syntax dtsltbf <bts id> <trx id> <tsl> Parameter explanations bts id This parameter specifies the BTS ID.12.Service terminal commands PCU2 Service Terminal Commands TLLI MS_INDEX IMSI TYPE NC Mode MS TSL_4 TSL_5 TSL_6 TSL_7 PFI PFC ID DL Guranteed Data Rate DL RLC MODE PFC Traffic Class ARP PFI PFC ID UL Guranteed Data Rate UL RLC MODE PFC Traffic Class ARP DLDC ALLOCATION TRX ID 2 TSL NUM Allocated TSL_4 TSL_5 TSL_6 TSL_7 : : : : : : : : : : : : : : : : : : : : : : : : : : : : 3221225480 [0xc0000008] 0x012cc0000008 244051090001003 EGPRS 0 DOWNLINK DOWNLINK CONCURRENT CONCURRENT 0 28388817 [0x1b12dd1] 0 ACK BEST_EFFORT ARP3 0 28388816 [0x1b12dd0] 0 ACK BEST_EFFORT ARP2 YES 3 [0x3] 4 5 6 DOWNLINK DOWNLINK DOWNLINK DOWNLINK 7 BCSU/35/PCU/4/OSE> 2.4 dtsltbf (display the TBF information specific to identified TSL) Function With this command you display the TBF information specific to identified TSL (dtsltbf). trx id This parameter specifies the TRX ID. 102 Id:0900d805806444bc DN0479352 Issue 4-2 .

01 KB per sec DOWNLINK ACK 4 5 6 7 PDM_DLTBF_ACTIVE 127 127 127 6 3 DN0479352 Issue 4-2 Id:0900d805806444bc 103 . Display the information for a TSL with BTS ID '300'. dtsltbf 300 3 7 Execution printouts BCSU/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 TRX_ID:3 ARFCN:5 Access Tech:GSM_P TX_Power:0 Hopping:NO Territory_Type:EGPRS_CS1_CS2 DSP Id : 0 CONTR_BCSU_ADDR : 16735 E-TRX : NO DLDC TRX : YES Num_of_PSW_TSLs:4 TSL_4:DEDICATED TSL_5:DEDICATED TSL_6:DEDICATED TSL_7:DEDICATED EDAP id : 300 Ext PCM Line of the SMCH : 8112 Ext PCM TSL (64 K) of the SMCH : 10 Ext PCM STSL (16 K) of the SMCH : 2 BTS id of SMCH: 300 TRX id of SMCH: 1 RTSL of SMCH : 5 BTS ID TRX ID DSP ID MULTISLOT CLASS Direction RLC MODE TBF TSL NUM Allocated USF TBF STATE TBF ID TFI Coding Scheme TBF Data rate Direction RLC MODE TBF TSL NUM Allocated TBF STATE : : : : : : : : : : : : : : : : : 300 [0x12c] 1 [0x1] 0 33 UPLINK ACK 6 7 127 127 127 PDM_ULTBF_ACTIVE 8 [0x8] 17 [0x11] MCS9 0.PCU2 Service Terminal Commands Service terminal commands Examples 1. TRX ID '3' and TSL ID '7'.

This command also gives information on the number of TRXs in the segment and the DSPs which are handling the TRXs of a segment.Service terminal commands PCU2 Service Terminal Commands TBF ID TFI Coding Scheme TBF Data rate TLLI MS_INDEX IMSI TYPE NC Mode MS TSL_4 TSL_5 TSL_6 TSL_7 PFI PFC ID UL Guranteed Data Rate UL RLC MODE PFC Traffic Class ARP PFI PFC ID DL Guranteed Data Rate DL RLC MODE PFC Traffic Class ARP DLDC ALLOCATION TRX ID 2 TSL NUM Allocated TSL_4 TSL_5 TSL_6 TSL_7 : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 0 [0x0] 20 [0x14] MCS4 10.5 dpcutbf (display number of UL and DL TBFs for all active segments in the PCU) Function With this command you display the number of uplink and downlink TBFs for all active segments in the PCU.12. 104 Id:0900d805806444bc DN0479352 Issue 4-2 . the segment is not included in the printout.69 KB per sec 3221225480 [0xc0000008] 0x012cc0000008 244051090001003 EGPRS 0 DOWNLINK DOWNLINK CONCURRENT CONCURRENT 0 28388816 [0x1b12dd0] 0 ACK BEST_EFFORT ARP2 0 28388817 [0x1b12dd1] 0 ACK BEST_EFFORT ARP3 YES 3 [0x3] 4 5 6 DOWNLINK DOWNLINK DOWNLINK DOWNLINK 7 BCSU/35/PCU/4/OSE> 2. If there are no DLDC TBFs in a segment. You can also choose to display the number of Downlink Dual Carrier (DLDC) TBFs ongoing in each segment.

PCU2 Service Terminal Commands Service terminal commands Syntax dpcutbf [-dldc] Parameter explanations -dldc This parameter displays the number of Downlink Dual Carrier (DLDC) TBFs ongoing in each segment. dpcutbf -dldc Execution printouts The execution printout for example 1 is the following: 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-TBFs 300 2 0 4 4 ---------------------------------------------------------------------TOTAL: 4 4 ---------------------------------------------------------------------**************************END OF TRACE**************************** The execution printout for example 2 is the following: 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-TBFs 300 2 0 4 4 4 ---------------------------------------------------------------------TOTAL: 4 4 4 ---------------------------------------------------------------------**************************END OF TRACE**************************** BCSU/35/PCU/4/OSE> DN0479352 Issue 4-2 Id:0900d805806444bc 105 . Examples 1. dpcutbf 2. Display the TBF and DSP allocation for all segments. Display the TBF and DSP allocation for all segments including ongoing DLDC TBFs.

1 Gb–related commands dgb (display Gb configuration) Function With this command you display Gb configuration (dgb). Syntax dgb Examples 1. dgb Execution printouts BCSU/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::991 Number 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 106 Id:0900d805806444bc DN0479352 Issue 4-2 .Service terminal commands PCU2 Service Terminal Commands 2. Display the Gb configuration.13 2.13.

Examples 1. egbm -u 1 2 5. If the TLLI is not entered. BVCI This parameter specifies the BVCI for which monitoring is to be enabled. Enable Gb interface monitoring for all BVCIs and TLLIs in the form of hex dump. egbm -u 1 DN0479352 Issue 4-2 Id:0900d805806444bc 107 .PCU2 Service Terminal Commands Service terminal commands 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. Enable Gb interface monitoring for BVCI 1 and TLLI 2 in the form of hex dump. egbm -h 1 3.2 egbm (enable Gb monitoring) Function With this command you enable Gb interface monitoring (egbm). egbm -h 4. –u This parameter specifies that the data to be output is in ASCII format (like printf). Enable Gb interface monitoring for BVCI 1 and all TLLIs the form of hex dump. and that BVCI and all TLLIs are monitored. then the first parameter (after -h/u switch) is considered the BVCI. Syntax egbm -[h/u][BVCI] [TLLI] Parameter explanations –h This parameter specifies that the data to be output should be in the form of hex dump. Enable Gb interface monitoring for BVCI 1 and TLLI 2 in the ASCII form. egbm -h 1 2 2. If the BSSGP virtual connection identifier (BVCI) and the temporal logical link identity (TLLI) are not entered. TLLI This parameter specifies the TLLI for which monitoring is to be enabled.13. Enable Gb interface monitoring for BVCI 1 and all TLLIs the ASCII form. then all BVCIs and all TLLIs are monitored.

R_default_MS value : 0 bits/sec.-.-.-.-.-.-...----.-.-.a.. [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 -------.-.-.-. Enable Gb interface monitoring for BVCI 1 and all TLLIs the ASCII form.-.-.-.-.-.-..----.-.-.-.-.----------- 108 Id:0900d805806444bc DN0479352 Issue 4-2 ..-. Bucket Leak Rate : 0 bits/sec Bmax : 0 bits/sec.-.-e BCSU/0/PCU/0/OSE/GBL> Trace for BVCI:101 and TLLI:?][1/1/2004 0:20:32:215005] FLOW-CONTROL-BVC-ACK -.-.-..----.----.Service terminal commands PCU2 Service Terminal Commands 6.-.----------81 61 '.-. 00000010 1C 82 00 00 06 82 00 00 . -------.-.-.-.-..-.-.-.-.-.-.-.-...-. egbm -u Execution printouts BCSU/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.-.-.-.-...-..a -..-.----------[GB Monitoring SGSN --> BSS -------.-.-.-..-.-.-..-.-..-.-.-00000000 27 1E -------.----------00000000 26 1E 81 61 05 82 00 00 03 82 00 00 01 82 00 00 &.-..-.. BVC Measurment : 0 msec..-..-.

Syntax digbm Examples 1.PCU2 Service Terminal Commands Service terminal commands 2. Disable Gb interface monitoring.13.13. The command disables the Gb monitoring for all the BVCIs and TLLIs enabled through the service terminal.4 digbm (display Gb monitoring) Function With this command you display the list of BVCIs and TLLIs for which the Gb monitoring (digbm) is enabled. digbm Execution printouts BCSU/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> DN0479352 Issue 4-2 Id:0900d805806444bc 109 . Syntax dgbm Examples 1.3 dgbm (disable Gb monitoring) Function This command is used to disable Gb interface monitoring (egbm). Display the Gb interface monitoring configuration. dgbm Execution printouts BCSU/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.

Enable Gb data logging to a file named 'st_gb_logs.log'. ! Running this command may affect the system performance.Service terminal commands PCU2 Service Terminal Commands 2. In case the logs exceed the maximum file size. Use this command with care and only when necessary. The full form of this command is enable Gb data logging (egbl).13. Syntax egbl <filename> <size_in_bytes> Parameter explanations filename The name of the file in which the logs are to be captured. size_in_bytes The maximum size of the file.log 5000 Execution printouts BCSU/0/PCU/0/OSE>egbl st_gb_logs. Examples 1. enter the commands dgbm and dgbl. you should enter the following commands in the following order: egbm -[h/u][BVCI] [TLLI] egbl <filename> <size_in_bytes> After you finish logging.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 ********************************************************************** 110 Id:0900d805806444bc DN0479352 Issue 4-2 . To log Gb interface messages into a file. the file is wrapped around. This command can be used when you need to capture the output into a file for offline analysis.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' with a size of 5000 bytes. egbl st_gb_logs.5 egbl (enable Gb data logging) Function With this command you log the output of all the Gb interface messages. The filename must have the extension '.

Syntax dgbl Examples 1.14. Enable subscriber monitoring for IMSI '1'. If another user tries to enable subscriber monitoring for another IMSI.13. the request will be rejected and appropriate message will be printed. Examples 1. Syntax esm <imsi> Parameter explanations imsi This parameter specifies the IMSI to be monitored.PCU2 Service Terminal Commands Service terminal commands 2. The subscriber monitoring can be enabled only for one IMSI at a time in the system. Disable the Gb data logging to a file.14 Subscriber monitoring–related commands This section contains the commands for subscriber monitoring. 2. dgbl Execution printouts BCSU/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.1 esm (enable subscriber monitoring) Function With this command you enable subscriber monitoring (esm).log Size: 5000 ******************************************************** 2. esm 1 Execution printouts BCSU/0/PCU/0/OSE>esm 24405109000004 ---------------------------------------------------------------> Command esm executed on [1/1/2004 0:11:7:870001] <---- DN0479352 Issue 4-2 Id:0900d805806444bc 111 .6 dgbl (disable Gb data logging) Function The full form of this command is disable Gb data logging (dgbl).

* BCSU/0/PCU/0/OSE> 2.* .* .* .* .* Segment id : 0 BTS id : 0 TRX id : 0 Location area id : LAC : 0.* .* .* .* . dsm Execution printouts BCSU/0/PCU/0/OSE>dsm ---------------------------------------------------------------> Command dsm executed on [1/1/2004 0:11:7:870001] <---- 112 Id:0900d805806444bc DN0479352 Issue 4-2 .* .* .* .* .* .14.* MCS change observations: .* .* .* .2 dsm (disable subscriber monitoring) Function With this command you disable subscriber monitoring (dsm).* .* .* .* .* .* .* .* .* .* .* System level trace report for IMSI : 24405109000004 .* Flow control change observations : .* .* .Service terminal commands PCU2 Service Terminal Commands -----------------------------------------------------------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] .* .* .* .* .* .* .* .* .* . 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 : .* .* .* .* .* .* .* .* .* .* TBF release time : Thu Jan 1 00:20:27 2004 TBF release cause : 0 Amount of LLC data using the last MCS : 10080 Number of RLC blocks using the last MCS : 364 Number of mcs changes caused by Abis-bus blockage : 0 .* .* .* .* .* .* .* .* .* .* .* .* .* .* .* .* .* .* .* .* .* .* .* .* .* .* .* . Syntax dsm Examples 1.* .* .* .* .* . Disable subscriber monitoring.* .* .* .* .* .* .* .* .* .* .* .* .* .* .* PFC change observations : .* .

The full form of this command is enable subscriber monitoring data logging (esml). The filename must have an extension '. Syntax esml <filename> <size_in_bytes> Parameter explanations filename The name of the file in which the logs are to be captured. This command can be typically used when you need to capture the output into a file for offline analysis. In case the logs exceed the maximum file size. Syntax dism Examples 1. the log capture mode is automatically turned off. Use this command with care and only when necessary. size_in_bytes The maximum size of the file.log'.14. ! Running this command may affect the system performance.3 dism (display subscriber monitoring) Function With this command you display the IMSI for which the subscriber monitoring (dism) is enabled.14. DN0479352 Issue 4-2 Id:0900d805806444bc 113 . Display the subscriber monitoring configuration.PCU2 Service Terminal Commands Service terminal commands -----------------------------------------------------------subscriber monitioring successfully disabled BCSU/0/PCU/0/OSE> 2. dism Execution printouts BCSU/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.4 esml (enable subscriber monitoring data logging) Function With this command you log the output of all the subscriber monitoring messages. and no more logging is done.

log 5000 Execution printouts BCSU/0/PCU/0/OSE>esml st_sm_logs. esml st_sm_logs. Disable the subscriber monitoring data logging to a file.log' with size of 5000 bytes.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.Service terminal commands PCU2 Service Terminal Commands Examples 1. Syntax dsml Examples 1.log Size: 5000 ******************************************************** 2.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. Enable subscriber monitoring data logging to a file named 'st_sm_logs.14. dsml Execution printouts BCSU/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.15 User plane monitoring–related commands This section contains the commands for user plane monitoring. 114 Id:0900d805806444bc DN0479352 Issue 4-2 .5 dsml (disable subscriber monitoring data logging) Function The full form of this command is disable subscriber monitoring data logging (dsml).

.-.. The trace message. Enable user plane monitoring for IMSI '1'..---------------00000000 00 00 00 00 C0 E5 7F 81 E0 F0 B2 66 03 C2 D4 80 . The line number of the file from which the log message was generated. The time stamp when the log was raised in hr:min:sec:micro-seconds format. If the display had been IMSI:123456.-....-.-.1 eup (enable user plane monitoring) Function With this command you enable user plane monitoring (eup)..-... dtt. Examples 1.-.-.c 66 5 1/1/2004 0:0:26:0 47 DSP:USER Plane Monitoring Test Message 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. the length of the IMSI would have been 6 octets.. meaning that the length is 3 octets.f.-. Direction ->Downlink -------..-.-.PCU2 Service Terminal Commands Service terminal commands 2...-. raised by the application. The filename from which the log message was generated.15. Syntax eup <imsi> Parameter explanations imsi This parameter specifies the IMSI to be monitored. The date stamp when the log was raised in dd/mm/yyyy format.-. Indicates that this is a user plane monitoring trace.-.-. DN0479352 Issue 4-2 Id:0900d805806444bc 115 .-. The application ID of the application which raised the log. eup 1 Execution printouts User plane message output description: Parameter IMSI:013 Description Indicates that this trace has been raised for IMSI of value '013'.-.

-.3 diup (display user plane monitoring) Function With this command you display the IMSI for which the user plane monitoring (diup) is enabled....---------------0C 00 01 02 01 04 03 06 ....... 0D 10 0F 12 11 14 13 16 . Direction ->Uplink -------00000000 00000010 00000020 --------00 05 15 --00 08 18 --00 07 17 --23 0A 1A --A7 09 19 --FD 0C 1C --FC 0B 1B --2C 0E FB --.-..-......-.-.-.-.-.-..-..-..-..#... ..Service terminal commands PCU2 Service Terminal Commands 00000010 D4 D4 D4 D4 D4 D4 D4 D4 D4 D4 D4 D4 D4 D4 FF D4 .-...15.. Syntax dup Examples 1..-.-....-..-.15.---------------- 2.-. 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.. -------. Disable user plane monitoring..-. dup Execution printouts BCSU/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.-....-.-.-.2 dup (disable user plane monitoring) Function With this command you disable user plane monitoring (dup)...-...-. diup Execution printouts BCSU/0/PCU/0/OSE/UPL>diup ---------------------------------------------------------------> Command diup executed on [1/1/2004 0:7:53:180001] <---- 116 Id:0900d805806444bc DN0479352 Issue 4-2 ...-..-.. -.. Display the user plane monitoring configuration...-. Syntax diup Examples 1.......

This command can be typically used in scenarios where you need to capture the output into a file for offline analysis. In case the logs exceed the maximum file size. Examples 1. eupl st_up_logs. The full form of this command is enable user plane data logging (eupl).log 5000 Execution printouts BCSU/0/PCU/0/OSE>eupl st_up_logs. the file is wrapped around. Use this command with care and only when necessary.4 eupl (enable user plane data logging) Function With this command you log the output of all the user plane messages. The filename must have an extension '.15.log'. size_in_bytes The maximum size of the file.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 ********************************************************************** DN0479352 Issue 4-2 Id:0900d805806444bc 117 . Enable user plane data logging to a file named 'st_up_logs.log' with size of 5000 bytes. Syntax eupl <filename> <size_in_bytes> Parameter explanations filename The name of the file in which the logs are to be captured.PCU2 Service Terminal Commands Service terminal commands -----------------------------------------------------------User Plane Monitoring is enabled for IMSI 24405109000004 BCSU/0/PCU/0/OSE/UPL> 2. ! Running this command may affect the system performance.

Examples 1. dfc 2.16 Frame relay–related commands This section contains the commands for frame relay. Display the frame relay configuration for bearer '2. Disable user plane logging to a file.16.5 dupl (disable user plane data logging) Function The full form of this command is disable user plane data logging (dupl). 2. dfc 2 118 Id:0900d805806444bc DN0479352 Issue 4-2 . Syntax dupl Examples 1.log Size: 5000 ******************************************************** 2. Syntax dfc {<bearer_id>} {<dlci>} Parameter explanations bearer_id This parameter specifies the bearer for which the frame relay configuration is to be displayed. dlci This parameter specifies the dlci ID of the bearer for which the frame relay configuration is to be displayed. Display the frame relay configuration for all the bearers.15.1 dfc (display frame relay configuration) Function With this command you display frame relay configuration (dfc).Service terminal commands PCU2 Service Terminal Commands 2. dupl Execution printouts BCSU/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.

dfc 2 17 Execution printouts BCSU/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 ------------------------------------------------------------ DN0479352 Issue 4-2 Id:0900d805806444bc 119 .PCU2 Service Terminal Commands Service terminal commands 3. Display the frame relay configuration for bearer '2 and dlci ID '17.

Syntax dpt Examples 1. 120 Id:0900d805806444bc DN0479352 Issue 4-2 .18 Telnet server administration commands This section describes the service terminal commands used to enable/disable Telnet connectivity. Display the system level trace pending table.17 2. dpt Execution printouts BCSU/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.17.1 General category commands dpt (display system level trace pending table) Function With this command you display system level trace pending table (dpt).Service terminal commands PCU2 Service Terminal Commands ----> 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.

In PCU reset the values revert to default values. Enable Telnet for all IPs. Examples 1.1 etc (enable telnet for specified IP address or for all IPs) Function With this command you enable Telnet for a specified IP address or for all IPs. etc all Execution printouts BCSU/0/PCU/0/OSE>etc 192.18. Enable Telnet for a specified IP address.0.2 dtc (disable telnet for specified IP address or for all IPs) Function With this command you disable Telnet for a specified IP address or for all IPs.PCU2 Service Terminal Commands Service terminal commands 2. Syntax etc <"all"|ipv4_address> Parameter explanations ip address This parameter specifies the IP address for which Telnet services are to be enabled in the PCU2. etc 192. The allowed values are 'all' or any IPv4 address.168.168.18. In PCU reset the values revert to default values. The allowed values are 'all' or any IPv4 address. Syntax dtc <"all"|ipv4_address> Parameter explanations ip address This parameter specifies the IP address for which Telnet services are to be enabled in the PCU2.0.11 2. DN0479352 Issue 4-2 Id:0900d805806444bc 121 .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.

tcstatus Execution printouts BCSU/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 ------------------------------------------------------------ 122 Id:0900d805806444bc DN0479352 Issue 4-2 .0.168. dtc 192.3 tcstatus (display list of authenticated IP for telnet connections) Function With this command you display the list of authenticated IPs for Telnet connections. Disable Telnet for all IPs.0.168. Disable Telnet for a specified IP address. Display list of authenticated IPs for Telnet connections. dtc all Execution printouts BCSU/0/PCU/0/OSE>dtc 192. Syntax tcstatus Examples 1.Service terminal commands PCU2 Service Terminal Commands Examples 1.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.11 2.18.

Display the number of mobile stations in NC0 mode.0.19. Syntax dnc2ms Examples 1.19. Syntax dnc0ms Examples 1.PCU2 Service Terminal Commands Service terminal commands ----> Command tcstatus executed on [1/1/2004 0:33:39:3002] <--------------------------------------------------------------Telnet allowed from only following IP addresses 192.19 2. Display the number of mobile stations in NC2 mode. dnc2ms Execution printouts BCSU/0/PCU/0/OSE>dnc2ms ------------------------------------------------------------ DN0479352 Issue 4-2 Id:0900d805806444bc 123 .168.1 NCCR commands dnc0ms (display number of mobile stations in NC0 mode) Function With this command you display the number of mobile stations in NC0 mode in the system.2 dnc2ms (display the number of mobile stations in NC2 mode) Function With this command you display the number of mobile stations in NC2 mode in the system.11 BCSU/0/PCU/0/OSE> 2. dnc0ms Execution printouts BCSU/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.

segment ID. Display the NCCR data of mobile stations with MS ID '1000'. TLLI. Bitrate per radioblock UL N. Examples 1.3 dnccrms (display the NCCR data of mobile stations specified) Function With this command you display the NCCR data of mobile stations specified by a temporary logical link identity (TLLI). Syntax dnccrms <-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.A. dnccrms -t 4294967040 10 2. or MS ID for which NCCR data of mobile stations will be displayed.A.Service terminal commands PCU2 Service Terminal Commands ----> 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. MS ID This parameter specifies the TLLI. 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/No NO 3G MEASUREMENTS RECEIVED FOR THIS MS 124 Id:0900d805806444bc DN0479352 Issue 4-2 .A. DL N. segment ID. segment ID. Display the NCCR data of mobile stations with TLLI ’4294967040’ and segment ID ’10’. -m for MS ID.A.19. or MS ID. dnccrms -m 1000 Execution printouts BCSU/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. kbit/s DL N.

Examples 1. Syntax dpsinacc <segment ID> Parameter explanations segment ID This parameter specifies the segment ID for which PSI messages will be displayed.20. Display the NACC-related neighbour cell configuration data of segment '69'.PCU2 Service Terminal Commands Service terminal commands ************************* End of Trace ************************* 2.1 NACC commands dnacc (display the NACC related neighbour cell configuration data) Function With this command you display the NACC-related neighbour cell configuration data of a user-given segment.20.20 2. 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. DN0479352 Issue 4-2 Id:0900d805806444bc 125 . Syntax dnacc <segment ID> Parameter explanations segment ID This parameter specifies the segment ID for which the NACC-related neighbour cell configuration data will be displayed.2 dpsinacc (display the neighbour cell SI or PSI messages) Function With this command you display the neighbour cell SI or PSI messages of a given segment.

dsinacc 69 Execution printouts BCSU/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 SI 2Q(1) 0 2b 2b 2b 2b 126 Id:0900d805806444bc DN0479352 Issue 4-2 .3 dsinacc (display the SI messages of given segment) Function With this command you display the SI messages of a given segment stored into the PCU. Display the SI messages of segment '69'. Examples 1. With this data the PCU responds to the PACKET SI STATUS messages sent by MSS. Syntax dsinacc <segment ID> eg: dsinacc 1 Parameter explanations segment ID This parameter specifies the segment ID for which SI messages will be displayed. dpsinacc 69 Execution printouts BCSU/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. Display the PSI messages of segment '69'.20.Service terminal commands PCU2 Service Terminal Commands Examples 1.

PCU2 Service Terminal Commands Service terminal commands 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 SI4 21 SI13 21 BCSU/30/PCU/4/OSE> 1b 8 15 32 f4 51 22 22 c9 2 5 64 40 5 9d 0 0 1c 13 2b 2b 1c 32 f4 51 22 22 40 5 9d 0 0 1 2b 2b 2b 2b 2b 2b 2b 2b 0 0 80 0 f8 8 7c c9 32 a6 14 25 a4 db 2b 2b 2b 2b 2b 2b 2b 0 2. Syntax dgbipbvc <BVCI> Parameter explanations BVCI This parameter specifies the BSSGP virtual connection identifier (BVCI) for which the Gb information will be displayed. Display the information about BVCI '10010'.21.1 Gb over IP commands dgbipbvc (display the information about certain BVC) Function With this command you display the information about a certain BSSGP virtual connection (BVC). dgbipbvc 10010 Execution printouts BCSU/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> DN0479352 Issue 4-2 Id:0900d805806444bc 127 . Examples 1.21 2.

dgbipnsei 10010 10 Execution printouts BCSU/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.Service terminal commands PCU2 Service Terminal Commands 2.21. Syntax dgbipnsvc <NSEI> Parameter explanations NSEI This parameter specifies the NSEI for which Gb information will be displayed. Display the information about NSEI '10'. Examples 1.3 dgbipnsvc (display the information about certain NSVC) Function With this command you display the information about a certain network service virtual connection (NSVC). NSEI This parameter specifies the network service entity identifier (NSEI) for which Gb information will be displayed.2 dgbipnsei (display the information about certain NSE) Function With this command you display the information about a certain network service entity (NSE).21. Display the information about BVCI '10010' and NSEI '10'. Examples 1. Syntax dgbipnsei <BVCI> <NSEI> Parameter explanations BVCI This parameter specifies the BVCI for which Gb information will be displayed. dgbipnsvc 10 128 Id:0900d805806444bc DN0479352 Issue 4-2 .

Display all dedicated IMSI entries.22 DTM commands These commands are used to display and delete information stored in the dedicated dual transfer mode (DTM) IMSI database.1 ddimsi (display dedicated IMSI) Function With this command you display a specified DTM IMSI entry stored in the IMSI table.136 Remote UDP Port::5567 Remote Data Weight::1 Remote Signaling Weight::1 Preconf SGSN IP Endpoint::STATIC BCSU/0/PCU/0/OSE> 2. the IMSI ID needs to be specified. you will be prompted.PCU2 Service Terminal Commands Service terminal commands Execution printouts BCSU/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. Syntax ddimsi <imsi | “all”> Examples 1.3. ddimsi all Execution printouts BCSU/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: DN0479352 Issue 4-2 Id:0900d805806444bc 129 . Before printing all IMSI entries. For commands didtms and ddtmimsi.3. 2.22. The IMSI ID is a 15 digit number. The command can also be used to display the complete DTM IMSI entry table.

The command displays two internal counters: DTM IMSI COORDINATION MESSAGES and DTM IMSI SEARCH OPERATIONS.22.Service terminal commands PCU2 Service Terminal Commands -----------------------------------------------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.2 didtms (display internal DTM counters) Function With this command you display the internal counters for a specified DTM IMSI. Syntax didtms <imsi> 130 Id:0900d805806444bc DN0479352 Issue 4-2 .

PCU2 Service Terminal Commands

Service terminal commands

Examples 1. Display the internal counters for a DTM IMSI. didtms 987651561155865 Execution printouts BCSU/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)
Function With this command you delete a specific DTM IMSI entry stored in the IMSI table. Syntax ddtmimsi <imsi> Examples 1. Delete dedicated IMSI entry. ddtmimsi 987651561155865 Execution printouts

BCSU/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
ddspinfo (display DSP information)
Function With this command you display DSP information.

2.23.1

DN0479352 Issue 4-2

Id:0900d805806444bc

131

Service terminal commands

PCU2 Service Terminal Commands

Syntax ddspinfo <dsp_id> Parameter explanations dsp_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 Execution printouts The execution printout for example 1 is the following: BCSU/0/PCU/0/OSE> ddspinfo ddspinfo DSP DAP1(EDAP1) DAP2(EDAP2) 0 2(0)* 65535(255) 1 2(0)* 65535(255) 2 2(0)* 65535(255) 3 2(0) 65535(255) 4 2(0) 65535(255) 5 2(0) 65535(255) 6 2(0) 65535(255) 7 2(0) 65535(255)

EGPRS 7 0 0 0 0 0 0 0

GPRS 0 0 0 0 0 0 0 0

STATE 1 1 1 1 1 1 1 1

SLAVE(UL/DL) 0/3 0/0 0/0 0/0 0/0 0/0 0/0 0/0

Where DSP state, 0 - DSP_UNKNOWN 1 - DSP_READY 2 - DSP_FAILED Where * denotes DSP is DLDC preferred for this DAP The execution printout for example 2 is the following: BCSU/0/PCU/0/OSE> ddspinfo 2 DSP DAP1(EDAP1) DAP2(EDAP2) 2 2(0)* 65535(255) EGPRS 0 GPRS 0 STATE 1 SLAVE(UL/DL) 0/0

Where DSP state, 0 - DSP_UNKNOWN 1 - DSP_READY 2 - DSP_FAILED Where * denotes DSP is DLDC preferred for this DAP BCSU/0/PCU/0/OSE>

2.23.2

dpcminfo (display PCU-PCM information)
Function With 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.

132

Id:0900d805806444bc

DN0479352 Issue 4-2

PCU2 Service Terminal Commands

Service terminal commands

Syntax dpcminfo <pcm_line_no> Parameter explanations pcm_line_no This parameter specifies the PCM line number for which the information will be displayed. The value range is from 0 to 1. Examples 1. Display the information for PCU-PCM line number 1. dpcminfo 1 Execution printouts
BCSU/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_FAILED BCSU/0/PCU/0/OSE>

DN0479352 Issue 4-2

Id:0900d805806444bc

133

CH_UNKNOWN 1 .CH_RES_MASTER 7 . Examples 1. The value range is from 1 to 470. Display the PCU-PCM information for EDAP '2' dpcmdapinfo 2 Execution printouts BCSU/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. Display the information for EDAP '2' ddapinfo 2 134 Id:0900d805806444bc DN0479352 Issue 4-2 .CH_GPRS 2 .CH_UNDER_TEST 6 . 0 .CH_RESERVED_UL 8 .CH_RES_DL 9 .CH_FAILED BCSU/30/PCU/3/OSE> 2.3 dpcmdapinfo (display PCU-PCM information for the specified EDAP) Function With this command you display the PCU-PCM information for a specified EGPRS dynamic Abis pool (EDAP).CH_EDAP 5 .CH_PCCCH 3 .23. Syntax ddapinfo <dap_id> Parameter explanations dap_id This parameter specifies the EDAP ID for which the information will be displayed. Syntax dpcmdapinfo <dap_id> Parameter explanations dap_id This parameter specifies the EDAP ID for which the PCU-PCM information will be displayed. The value range is from 1 to 470.4 ddapinfo (display EDAP information) Function With this command you display EDAP information.Service terminal commands PCU2 Service Terminal Commands 2. Examples 1.CH_EGPRS_MASTER 4 .23.

Examples 1. Syntax dabmtrxinfo <seg_id> <bts_id> <trx_id> Parameter explanations seg_id This parameter specifies the SEG ID for which the information will be displayed.PCU2 Service Terminal Commands Service terminal commands Execution printouts BCSU/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.23. Display the information for SEG '257' and BTS '257' dabmtrxinfo 257 257 Execution printouts BCSU/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 DN0479352 Issue 4-2 Id:0900d805806444bc 135 . The value range is from 1 to 660.ST_EDAP_FAILED .28-32 3 0 0 1 2 3 4 5 6 7 Where EDAP state: .ST_EDAP_WTF_DSP_ACK . The value range is from 1 to 660. The value range is from 1 to 16.5 dabmtrxinfo (display the TRX information for the BTS in the specified segment) Function With this command you display the TRX information for the BTS in the specified segment. trx_id This parameter specifies the TRX ID for which the information will be displayed.ST_EDAP_IN_CONFLICT 0 2 4 6 1 3 5 7 - ST_EDAP_WTF_EDAP_INFO ST_EDAP_READY ST_EDAP_WTF_RECONF ST_EDAP_FAIL_IN_LOOP_TEST BCSU/30/PCU/3/OSE> 2. bts_id This parameter specifies the BTS ID for which the information will be displayed.ST_EDAP_NOT_DEFINED .

CH_NOT_USED . The value range is from 1 to 470. Syntax ddaptrxinfo <dap_id> Parameter explanations dap_id This parameter specifies the EDAP ID for which the information will be displayed. Examples 1.CH_DSP_CONNECTING . Display the TRX information for EDAP '2'.Service terminal commands PCU2 Service Terminal Commands RTSL 0 1 2 3 4 5 6 7 PCU_PCM 0 0 0 0 0 0 0 TSL 1 1 1 0 0 0 0 subTSL 2 1 0 3 2 1 0 DSP 0 0 0 0 0 0 0 STATE 3 3 3 3 3 3 3 0 2 4 6 8 Where RTSL state: .23.CH_DSP_DISCONNECTING .CH_FAILED 1 3 5 7 - CH_RC0_CONNECTIN CH_CONNECTED CH_RC0_DISCONNECTING CH_REALLOC_RELEASE BCSU/30/PCU/3/OSE> 2.CH_REALLOC_CONNECT .6 ddaptrxinfo (display TRX information for the specified DAP) Function With this command you display the TRX information for the specified DAP. Execution printouts BCSU/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 0 1 2 3 4 5 PCU_PCM 0 0 0 0 0 TSL 1 1 1 0 0 subTSL 2 1 0 3 2 DSP 0 0 0 0 0 STATE 3 3 3 3 3 136 Id:0900d805806444bc DN0479352 Issue 4-2 .

stsl_ix This parameter specifies the sub-timeslot index for which the information will be displayed. tsl_ix This parameter specifies the timeslot index for which the information will be displayed. Examples 1.CH_DSP_CONNECTING .23. The value range is from 0 to 1. Display the information for PCU-PCM line number 0 and timeslot number .CH_NOT_USED .PCU2 Service Terminal Commands Service terminal commands 6 7 0 0 0 0 1 0 0 0 3 3 0 2 4 6 8 Where RTSL state: . The value range is from 0 to 3.CH_REALLOC_CONNECT . dstslinfo 0 0 Execution printouts BCSU/30/PCU/3/OSE>dstslinfo 0 0 ---------------------------------------------------------------> Command dstslinfo executed on [21/12/2005 9:7:18:508951] <--------------------------------------------------------------PCM: 0 subTSL 0 1 2 3 TSL:0 TYPE 3 3 3 0 TRX_ID(PCU_TRX_IX) 1(0) 1(0) 1(0) - RTSL 7 6 5 - Where TSL state: DN0479352 Issue 4-2 Id:0900d805806444bc 137 . Syntax dstslinfo <pcm_line_no> <tsl_ix> <stsl_ix> Parameter explanations pcm_line_no This parameter specifies the PCM line number for which the information will be displayed.7 dstslinfo (display sub-TSL info for the PCU-PCM line) Function With this command you display the sub-timeslot information for the PCU-PCM line.0.CH_FAILED 1 3 5 7 - CH_RC0_CONNECTIN CH_CONNECTED CH_RC0_DISCONNECTING CH_REALLOC_RELEASE BCSU/30/PCU/3/OSE> 2.CH_DSP_DISCONNECTING . The value range is from 0 to 31.

Display Guard Period information for DAP '40'. Display Guard Period information. dgpinfo 2. Syntax dgpinfo <dap_id> Parameter explanations dap_id This parameter specifies the EDAP ID for which the information will be displayed. The value range is from 1 to 470. dgpinfo 40 Execution printouts The execution printout for example 1 is the following: 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 -/-/-/-/- 138 Id:0900d805806444bc DN0479352 Issue 4-2 .Service terminal commands PCU2 Service Terminal Commands 0 2 4 6 8 - CH_UNKNOWN CH_PCCCH CH_EDAP CH_RES_MASTER CH_RES_DL 1 3 5 7 9 - CH_GPRS CH_EGPRS_MASTER CH_UNDER_TEST CH_RESERVED_UL CH_FAILED BCSU/30/PCU/3/OSE> 2. Examples 1.8 dgpinfo (display guard period information per DAP) Function With this command you display the Guard Period information per dynamic Abis pool (DAP).23.

1 Cell monitoring commands dcem (display cell monitoring data) Function With this command you display the information about cell monitoring data.24.PCU2 Service Terminal Commands Service terminal commands 14 -/-/15 -/-/16 -/-/17 -/-/18 -/-/19 -/-/20 -/-/21 -/-/22 -/-/23 -/-/24 -/-/25 -/-/26 -/-/27 -/-/28 -/-/29 -/-/30 -/-/31 -/-/BCSU/30/PCU/3/OSE> -/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/- -/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/- 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 -/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/0/0 -/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/0/0 -/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/0/0 -/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/0/0 The execution printout for example 2 is the following: 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 31 Sub0 0/0 Sub1 0/0 Sub2 0/0 Sub3 0/0 BCSU/30/PCU/3/OSE> 2.24 2. Syntax dcem -g Display dcem -b Display dcem -t Display dcem -i Display <SEG_ID> info of all MS of all TSL of all TRX of all BTS of a particular Segment <BTS_ID> info of all MS of all TSL of all TRX of a particular BTS <TBF_ID> info of a particular TBF ID <SEG_ID> <TLLI> info of a particular TLLI DN0479352 Issue 4-2 Id:0900d805806444bc 139 .

TLLI This parameter specifies the temporary logical link identity (TLLI) for which the cell monitoring data will be displayed.Service terminal commands PCU2 Service Terminal Commands dcem -x Display dcem -s Display dcem -f Display <BTS_ID> <TRX_ID> info of all MS on all TSL of a particular TRX <BTS_ID> <TRX_ID> <TSL> info of all MS on particular TSL of a TRX <BTS_ID> <TRX_ID> <TSL> <TFI> info of a particular TFI on a TSL of a TRX Parameter explanations SEG_ID This parameter specifies the segment ID for which the cell monitoring data will be displayed. BTS_ID This parameter specifies the BTS ID for which the cell monitoring data will be displayed. Display the cell monitoring data for TBF ID =8 dcem -t 8 Execution printouts BCSU/35/PCU/4/OSE>dcem -t 8 ---------------------------------------------------------------> Command dcem executed on [22/11/2008 16:39:50:471007] <--------------------------------------------------------------**************************START OF TRACE**************************** TBF ID: 8 BTS_ID:300 TRX_ID:1 ARFCN:1 Access Tech:GSM_P TX_Power:0 Hopping:NO Territory_Type:EGPRS_CS1_CS2 DSP Id : 0 CONTR_BCSU_ADDR : 16735 E-TRX : NO DLDC TRX : YES Num_of_PSW_TSLs:4 TSL_4:DEDICATED TSL_5:DEDICATED TSL_6:DEDICATED 140 Id:0900d805806444bc DN0479352 Issue 4-2 . TFI This parameter specifies the temporary flow identity (TFI) for which the cell monitoring data will be displayed. Examples 1. TSL This parameter specifies the TSL 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.

PCU2 Service Terminal Commands Service terminal commands TSL_7:DEDICATED EDAP id : 300 Ext PCM Line of the SMCH : 8112 Ext PCM TSL (64 K) of the SMCH : 10 Ext PCM STSL (16 K) of the SMCH : 2 BTS id of SMCH: 300 TRX id of SMCH: 1 RTSL of SMCH : 5 BTS ID TRX ID DSP ID MULTISLOT CLASS Direction RLC MODE TBF TSL NUM Allocated USF TBF STATE TBF ID TFI Coding Scheme TBF Data rate Direction RLC MODE TBF TSL NUM Allocated TBF STATE TBF ID TFI Coding Scheme TBF Data rate TLLI MS_INDEX IMSI TYPE NC Mode MS TSL_4 TSL_5 TSL_6 TSL_7 PFI PFC ID DL Guranteed Data Rate DL RLC MODE PFC Traffic Class ARP PFI PFC ID UL Guranteed Data Rate UL RLC MODE PFC Traffic Class : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 300 [0x12c] 1 [0x1] 0 33 UPLINK ACK 6 7 127 127 127 127 127 127 PDM_ULTBF_NORMAL_REL_IN_PROGRESS 8 [0x8] 10 [0xa] MCS9 10.08 KB per sec DOWNLINK ACK 4 5 6 7 PDM_DLTBF_ACTIVE 0 [0x0] 28 [0x1c] MCS3 10.73 KB per sec 3221225480 [0xc0000008] 0x012cc0000008 244051090001003 EGPRS 0 DOWNLINK DOWNLINK CONCURRENT CONCURRENT 0 34026289 [0x2073331] 0 ACK BEST_EFFORT ARP3 0 34026288 [0x2073330] 0 ACK BEST_EFFORT 5 4 DN0479352 Issue 4-2 Id:0900d805806444bc 141 .

giving you a continuous update on the list of running processes and their status.33-0' built on Aug 21 2006 142 Id:0900d805806444bc DN0479352 Issue 4-2 .25 2.25. The traces that are displayed for PCU2-D/U are: ============================================================ Welcome to the PQII Boot Loader. Running can be invoked by enabling/disabling continuous mode.2 Bootup phases and traces When the service terminal boots up. For example: ecm <refresh time in seconds> After this mode is set. traces are displayed on the serial interface to inform you of what phase is currently in progress in the system. The commands that can be run in continuous mode are: • • • • • • • • • • • dbu dbp dbs dtu dtp dsca dsco daa deqs dsegtbf dtrxtbf 2.1 Service terminal command–related information Commands in continuous mode Some service terminal commands can be run in continuous mode.Service terminal commands PCU2 Service Terminal Commands ARP DLDC ALLOCATION TRX ID 2 TSL NUM Allocated TSL_4 TSL_5 TSL_6 TSL_7 : ARP2 : : : : : : : YES 3 [0x3] 4 5 6 DOWNLINK DOWNLINK DOWNLINK DOWNLINK 7 BCSU/35/PCU/4/OSE> 2. ============================================================ IMSGW Boot image version : '6.25. the commands listed below will run every 'timeperiod' seconds.

..Interface 1 : PASSED Ethernet Diagnostics test result ....Interface 1 : PASSED Starting Component Manager ..... PQII Data-Cache test result : PASSED HDLC Diagnostics test results .. SDL BOOTLOADER: Loading . Size = <0xa341b0> SDL BOOTLOADER: Transfering control to image entry point at 0x01e00004 RAM based initialization completed OSE Started.... IMSGW Platform Version : '11..11-0' built on Feb 04 2009 21:17:03 last line: <-34509834> last file: <FDF16BF5> IMSGW_CM: Executing the Entry Point function OF CM PCI: Sending Host Intr Starting PIU index=0x6.....Interface 2 : PASSED SDL BOOTLOADER: Reset Reason HARD RESET SDL BOOTLOADER: Downloading image For Section 0.. SDL BOOTLOADER: WAITING.. PCI and Component Framework Started Process LOGGER Created Process DSPM Created Process DSPMRX Created Process IPC_MR Created Process ARS Created Process SYSMON Created Process SDL Created Process STA Created Process st_dmx_dd0 Created Process st_dmx_dd1 Created Process DSPRM Created Process DIAGONOSTICS Created Process PCU_AGNT Created Process CPUMON Created Process SERIAL_DSPM Created DN0479352 Issue 4-2 Id:0900d805806444bc 143 ... Phy add=0x32. SDL BOOTLOADER: PQ2 Image Loading Completed... PIU type=0x3d9..PCU2 Service Terminal Commands Service terminal commands Power-On-Self-Tests : Memory Test : PASSED Watchdog Test : PASSED Serial Diagnostics test result : PASSED Ethernet Diagnostics test result . Broadcast=0x7f Log PIU Index= 0x7 IMSGW_CM:System Services..

Service terminal commands PCU2 Service Terminal Commands Process IDRS Created Process IBNACC Created Process IPMR Created IMSGW_CM:Component Manager started Stage 1 Applications Component Manager(RESTART State) : Received WORKING state from BSC Process PMS-PQII Created Process ABM Created Process PDM Created Process MAC Created Process PFM Created Process PCM Created Process BGP Created Process NS Created Process FR Created Process RL Created Process PSW Created IMSGW_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 File /ram/bin/dsp/IGWDGDSD.hex has been downloaded in DSP 7 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 144 Id:0900d805806444bc DN0479352 Issue 4-2 .hex has been downloaded in DSP 5 File /ram/bin/dsp/IGWDGDSD.hex has been downloaded in DSP 6 File /ram/bin/dsp/IGWDGDSD.hex has been downloaded in DSP 2 File /ram/bin/dsp/IGWDGDSD.hex has been downloaded in DSP 0 File /ram/bin/dsp/IGWDGDSD.hex has been downloaded in DSP 1 File /ram/bin/dsp/IGWDGDSD.hex has been downloaded in DSP 3 File /ram/bin/dsp/IGWDGDSD.hex has been downloaded in DSP 4 File /ram/bin/dsp/IGWDGDSD.

hex has been downloaded in DSP 2 DIAGNOSTIC RESULTS OF DSP3 -----------------------------------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 1 DIAGNOSTIC RESULTS OF DSP2 -----------------------------------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.PCU2 Service Terminal Commands Service terminal commands DIAGNOSTIC RESULTS OF DSP1 -----------------------------------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 3 DIAGNOSTIC RESULTS OF DSP4 -----------------------------------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 DN0479352 Issue 4-2 Id:0900d805806444bc 145 .

hex has been downloaded in DSP 5 DIAGNOSTIC RESULTS OF DSP6 -----------------------------------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 2 File /ram/bin/dsp/IGWMNDSD.hex has been downloaded in DSP 7 File /ram/bin/dsp/IGWMNDSD.Service terminal commands PCU2 Service Terminal Commands File /ram/bin/dsp/IGWBTDSD.hex has been downloaded in DSP 3 File /ram/bin/dsp/IGWMNDSD.hex has been downloaded in DSP 0 File /ram/bin/dsp/IGWMNDSD.hex has been downloaded in DSP 4 146 Id:0900d805806444bc DN0479352 Issue 4-2 .hex has been downloaded in DSP 6 DIAGNOSTIC RESULTS OF DSP7 -----------------------------------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 1 File /ram/bin/dsp/IGWMNDSD.hex has been downloaded in DSP 4 DIAGNOSTIC RESULTS OF DSP5 -----------------------------------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.

. HDLC Diagnostics test results ......PCU2 Service Terminal Commands Service terminal commands File /ram/bin/dsp/IGWMNDSD...... SDL BOOTLOADER: Loading . SDL BOOTLOADER: PQ3 Image Loading Completed. SDL Handshake failed.13-0' built on Dec 19 2008 Power-On-Self-Tests : Memory Test : PASSED SDL BOOTLOADER: Reset Reason HARD RESET SDL BOOTLOADER: Downloading image For Section 0.Interface 1 : PASSED DN0479352 Issue 4-2 Id:0900d805806444bc 147 .. ============================================================ IMSGW Boot image version : '1....... SDL BOOTLOADER: WAITING........hex has been downloaded in DSP 6 File /ram/bin/dsp/IGWMNDSD. Size = <0x00B80FB4> SDL BOOTLOADER: Transferring control to image entry point at 0x10000000 RAM based initialization completed OSE Started..hex has been downloaded in DSP 7 The traces that are displayed for PCU2-E are: ============================================================ Welcome to the PQIII Boot Loader.. 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.hex has been downloaded in DSP 5 File /ram/bin/dsp/IGWMNDSD. Type 'bist' within next 10 seconds to transfer control to BIST image..

PIU type=0x3e3.. PCI and Component Framework Started Process LOGGER Created Process DSPM Created Process DSPMRX Created Process IPC_MR Created Process ARS Created Process SYSMON Created Process SDL Created Process STA Created Process st_dmx_dd0 Created Process st_dmx_dd1 Created Process DSPRM Created Process DIAGONOSTICS Created Process PCU_AGNT Created Process CPUMON Created Process IDRS Created Process IBNACC Created Process IPMR Created IMSGW_CM:Component Manager started Stage 1 Applications Component Manager(RESTART State) : Received WORKING state from BSC Process PMS-PQII Created Process ABM Created Process PDM Created Process MAC Created Process PFM Created Process PCM Created Process BGP Created Process NS Created Process FR Created Process RL Created Process PSW Created IMSGW_CM:Component Manager started Stage 2 Applications FR has sent FTN_INIT_REQ_S message to BSC IMSGW_CM: Time Received from BSC .Service terminal commands PCU2 Service Terminal Commands Starting Component Manager . Phy add=0x32.Mon Feb 9 09:58:17 2009 RELAY has sent NSOM_GB_INT_RESTART_IND_S message to BSC 148 Id:0900d805806444bc DN0479352 Issue 4-2 . IMSGW Platform Version : 'R4E-DLDC-01-E0.. Broadcast=0x7f Log PIU Index= 0x5 IMSGW_CM:System Services.1P20' built on Feb 4 2009 21:16:30 last line: <0> last file: <0> IMSGW_CM: Executing the Entry Point function OF CM PCI: pci_wait_host_ack status WAITING_1 PCI: pci_wait_host_ack status WAITING_1 PCI: pci_wait_host_ack status WAITING_1 PCI: pci_wait_host_ack status WAITING_1 PCI: Sending Host Intr Starting PIU index=0x4.

hex has been downloaded in DSP 5 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 3 File /ram/bin/dsp/IGWDGDSE.hex has been downloaded in DSP 1 File /ram/bin/dsp/IGWDGDSE.hex has been downloaded in DSP 4 File /ram/bin/dsp/IGWDGDSE.hex has been downloaded in DSP 0 File /ram/bin/dsp/IGWDGDSE.hex has been downloaded in DSP 1 DIAGNOSTIC RESULTS OF DSP2 ---------------------------------------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 2 File /ram/bin/dsp/IGWDGDSE.hex has been downloaded in DSP 0 DIAGNOSTIC RESULTS OF DSP1 ---------------------------------------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 2 DN0479352 Issue 4-2 Id:0900d805806444bc 149 .PCU2 Service Terminal Commands Service terminal commands File /ram/bin/dsp/IGWDGDSE.

hex has been downloaded in DSP 4 150 Id:0900d805806444bc DN0479352 Issue 4-2 .hex has been downloaded in DSP 3 File /ram/bin/dsp/IGWMNDSE.hex has been downloaded in DSP 2 File /ram/bin/dsp/IGWMNDSE.hex has been downloaded in DSP 5 File /ram/bin/dsp/IGWMNDSE.hex has been downloaded in DSP 1 File /ram/bin/dsp/IGWMNDSE.hex has been downloaded in DSP 3 DIAGNOSTIC RESULTS OF DSP4 ---------------------------------------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.Service terminal commands PCU2 Service Terminal Commands DIAGNOSTIC RESULTS OF DSP3 ---------------------------------------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 4 DIAGNOSTIC RESULTS OF DSP5 ---------------------------------------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 File /ram/bin/dsp/IGWMNDSE.

3 Application name Application IDs for commands Application ID Common applications for PQII and DSP: Component manager IPC Message Router PMS Applications on PQII: Software Download Logger Alarms DSPM System Monitoring Diagnostics DSPRM Service Terminal Agent ABM PDM PSW MAC PFM PCM BGP NS FR RL PCU Agent CPU Monitoring process IDRS IPMR Dynamic application ID begin for PQII Dynamic application ID end for PQII Applications on DSP: QC DTT DSPA 4 5 6 4 5 6 7 8 9 10 11 16 17 18 19 20 21 22 23 24 25 28 29 31 12 34 46 1 2 3 DN0479352 Issue 4-2 Id:0900d805806444bc 151 .25.PCU2 Service Terminal Commands Service terminal commands File /ram/bin/dsp/IGWMNDSE.hex has been downloaded in DSP 5 2.

If the header in the black box displays the kernel cause. Software upgrade done and system rebooted. A process failed to start. 152 Id:0900d805806444bc DN0479352 Issue 4-2 . SSF failed to initialise. Kernel error handler called. it needs to be interpreted by the scheme below.25.4 Error code debugging information for abb and doe command output The reboot reason can have the following values in the black box: Value 0 1 2 3 4 5 6 7 8 Parameter CM_INVALID_REASON CM_SSF_INIT_FAILURE CM_PROCESS_STARTUP_FAIL URE CM_PROCESS_RUNTIME_FAILU RE CM_NORMAL_SHUTDOWN CM_WDOG_TIMER_START_FAIL ED CM_ST_SOFTWARE_UPGRADE CM_BB_NEW_FILE CM_KRN_ERR_HANDL_CALLED Description An invalid or an unknown reason. Black box new file created. A process crashed.Service terminal commands PCU2 Service Terminal Commands Application name ABIS ABIS_RX_0 ABIS_RX_1 ABIS_TX_0 ABIS_TX_1 DSP Interrupt Processes: DSPAISR ABIS_DMA_CH0_DROP_OS_ISR ABIS_DMA_CH1_DROP_OS_ISR ABIS_DMA_CH2_DROP_OS_ISR ABIS_DMA_CH3_DROP_OS_ISR ABIS_TX_OS_ISR_0 ABIS_TX_OS_ISR_1 ABIS_RX_OS_ISR_0 ABIS_RX_OS_ISR_1 DSP_BERR_OS_ISR MCSERIAL Dynamic application ID begin for DSP Dynamic application ID end for DSP Application ID 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 32 2. Watchdog timer starting failed. Normal shutdown initiated by user.

Defined by the constants below. only the kernel error handler is called.. A fatal flag.D16 D31 A main error code. In these cases. If the error handler returns. and interrupts are disabled before the call is made. The following masks are used to extract the various error parameter fields.D0 D30. A non-fatal error is called a warning. Contains the error code. where a memory pool has been exhausted. cleared for a warning. Fatal errors include all situations where kernel data has been damaged. A warning causes the OSE system to shut down. The least significant 8 bits are mostly used to indicate which system call was in progress. Set for a fatal error. or where an illegal parameter has been passed to a system call... An error may be either fatal or non–fatal. In these cases. Warnings include situations where data areas in user space have been damaged. The error handler receives three parameters: Parameter user_called ecode extra Description The value is zero for all system errors. Each error code contains three fields: • • • A 16-bit main error code. Set if a fatal error has occurred.. Many warnings are fatal for all processes in the involved address space. the kernel enters an infinite loop. regardless of any action taken by an error handler. which can be exited only by a hardware reset. A 15-bit subcode. A system error handler may elect to restart the system instead of returning to the kernel. unless an error handler resolves the error situation. Contains various error-dependent information.PCU2 Service Terminal Commands Service terminal commands The format of these error codes is specific to each OSE implementation. since a damaged data area can never be guaranteed not to affect other unprotected memory. Fatal Flag Subcode or Zero if not present Main Error Code D31 Figure 2 D30-D16 Error code decoding D0-D15 The 32-bit error parameter passed to an error handler is organised as follows: D15. the error handler is responsible for restarting the system. A 1-bit fatal flag. If no error handler resolves the situation. A fatal error causes the OSE system to shut down. A subcode or zero if not present. the kernel enters an infinite loop. Parameter ERROR_MASK Description 0x0000ffff DN0479352 Issue 4-2 Id:0900d805806444bc 153 .

Use SUBCODE_MASK to extract this field.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.Service terminal commands PCU2 Service Terminal Commands Parameter SUBCODE_MASK FATAL_MASK Description 0x7fff0000 0x80000000 2. System call name OSE_ADDRESSEE OSE_ALLOC OSE_ASSIGN_LINKHANDLER OSE_ATTACH OSE_ATTACH_SEGMENT OSE_CLEAR_BP OSE_CREATE_BLOCK OSE_CREATE_ERROR_HANDLER OSE_CREATE_POOL OSE_CREATE_PROCESS OSE_CREATE_SEM OSE_CURRENT_PROCESS OSE_DELAY OSE_DETACH OSE_ERROR OSE_FLUSH OSE_FREE_BUF OSE_GET_BID OSE_GET_BID_LIST OSE_GET_CPU OSE_GET_ENV OSE_GET_ENV_LIST OSE_GET_FSEM OSE_GET_MEM OSE_GET_PCB OSE_GET_PID_LIST OSE_GET_PRI OSE_GET_PTYPE Error code (0x010000) (0x020000) (0x030000) (0x040000) (0x050000) (0x060000) (0x070000) (0x080000) (0x090000) (0x0a0000) (0x0b0000) (0x0c0000) (0x0d0000) (0x0e0000) (0x0f0000) (0x100000) (0x110000) (0x120000) (0x130000) (0x140000) (0x150000) (0x160000) (0x170000) (0x180000) (0x190000) (0x1a0000) (0x1b0000) (0x1c0000) 154 Id:0900d805806444bc DN0479352 Issue 4-2 . The field is zero if the current system call is irrelevant.

PCU2 Service Terminal Commands Service terminal commands System call name OSE_GET_SEM OSE_GET_SIGNAL OSE_GET_SYSTIME OSE_GET_TICKS OSE_GET_UID OSE_HUNT OSE_HUNT_FROM OSE_INTERCEPT OSE_KILL_PROC OSE_KILL_SEM OSE_POWER_FAIL OSE_RECEIVE OSE_RECEIVE_FROM OSE_RECEIVE_W_TMO OSE_RESTORE OSE_RESUME OSE_SEND OSE_SENDER OSE_SEND_W_S OSE_SET_BP OSE_SET_ENV OSE_SET_FSEM OSE_SET_MEM OSE_SET_PCB OSE_SET_PRI OSE_SET_SEGMENT OSE_SIGSIZE OSE_SIGNAL_FSEM OSE_SIGNAL_SEM OSE_START OSE_START_OSE OSE_STOP OSE_SYSTEM_TICK OSE_TICK OSE_WAIT_FSEM OSE_WAIT_SEM OSE_WAKE_UP OSE_EXTEND_POOL Error code (0x1d0000) (0x1e0000) (0x1f0000) (0x200000) (0x210000) (0x220000) (0x230000) (0x240000) (0x250000) (0x260000) (0x270000) (0x280000) (0x290000) (0x2a0000) (0x2b0000) (0x2c0000) (0x2d0000) (0x2e0000) (0x2f0000) (0x300000) (0x310000) (0x320000) (0x330000) (0x340000) (0x350000) (0x360000) (0x370000) (0x380000) (0x390000) (0x3a0000) (0x3b0000) (0x3c0000) (0x3d0000) (0x3e0000) (0x3f0000) (0x400000) (0x410000) (0x420000) DN0479352 Issue 4-2 Id:0900d805806444bc 155 .

the error handler is assumed to disable interrupts before calling extend_pool() and restoring the previous interrupt status upon return. Note that the error handler is called in a state where the dispatcher is locked. The extra parameter serves no other purpose. Furthermore. Error code description when 'user_called' is 'False' ( value '0').Service terminal commands PCU2 Service Terminal Commands System call name OSE_RECEIVE_WITH OSE_SET_PRI_FOR OSE_REQUEST_TMO_SIG OSE_REQUEST_TMO OSE_CANCEL_TMO_SIG OSE_CANCEL_TMO OSE_RESTART_TMO OSE_RECEIVE_SPORT OSE_SET_REDIRECTION OSE_GET_STK_POOLID OSE_GET_SIG_POOLID Error code (0x430000) (0x440000) (0x450000) (0x460000) (0x470000) (0x480000) (0x490000) (0x4a0000) (0x4b0000) (0x4c0000) (0x4d0000) Constants are used to find out which error occurred. Use ERROR_MASK to extract this field. 156 Id:0900d805806444bc DN0479352 Issue 4-2 . it is. Ignoring the error causes the current allocation to be retried. however. The error handler is therefore not allowed to perform any operations or system calls that would cause a process switch to be attempted. if the pool serves interrupt or timer processes. An error handler may extend the pool with the extend_pool() system call. This error code can be ignored only if the pool was extended. As a special case. possible to use the signal_fsem() and signal_sem() calls in this situation. The extra parameter contains a pool identifier that can be passed to the extend_pool() system call. Error code name OSE_ENO_KERN_SPACE Value 0x12 Description The kernel pool is out of space.

The extra parameter contains a pool identifier that can be passed to the extend_pool() system call. As a special case. if the pool serves interrupt or timer processes. An error handler may extend the pool with the extend_pool() system call. if the pool serves interrupt or timer processes. however. The error handler is therefore not allowed to perform any operations or system calls that would cause a process switch to be attempted. An error handler may extend the pool with the extend_pool() system call. Ignoring the error causes the current allocation to be retried. possible to use the kill_proc(). signal_fsem() and signal_sem() calls in this situation. Furthermore.PCU2 Service Terminal Commands Service terminal commands Error code name OSE_ENO_USER_SIGSPACE Value 0x20 Description The user signal pool is out of space. The extra parameter serves no other purpose. This error code can be ignored only if the pool was extended. signal_fsem() and signal_sem() calls in this situation. however. The user stack pool is out of space. This error code can be ignored only if the pool was extended. the error handler is assumed to disable interrupts before calling extend_pool() and restoring the previous interrupt status upon return. The extra parameter contains a pool identifier that can be passed to the extend_pool() system call. Note that the error handler is called in a state where the dispatcher is locked. The extra parameter serves no other purpose. it is. Note that the error handler is called in a state where the dispatcher is locked. the error handler is assumed to disable interrupts before calling extend_pool() and restoring the previous interrupt status upon return. Ignoring the error causes the current allocation to be retried. it is. Furthermore. OSE_ENO_USER_STACKSPACE 0x02 DN0479352 Issue 4-2 Id:0900d805806444bc 157 . possible to use the kill_proc(). The error handler is therefore not allowed to perform any operations or system calls that would cause a process switch to be attempted. As a special case.

The create_pool system call was used on a block that contains processes. Too large stack buffer requested. OSE_EBUFFER_TOO_LARGE 0x11 OSE_ESTACK_TOO_LARGE 0x01 OSE_EBLOCK_HAS_PROCESSE S OSE_EILLEGAL_PROCESS_ID 0x22 0x32 158 Id:0900d805806444bc DN0479352 Issue 4-2 . An error handler repeatedly claims that an out-of-space error was handled. This error is fatal when it occurs in an interrupt process. so it is recommended that the system is shut down or restarted by the system error handler. the recover procedure may not be straightforward. Too large signal buffer requested. the error handler is expected to kill the current process. An illegal block or process ID was presented to the kernel. but the kernel cannot find the extended space. The extra parameter contains the offending ID. This code may also indicate a bad process ID in a redirection table.Service terminal commands PCU2 Service Terminal Commands Error code name OSE_EPOOL_EXTENSION_FAIL ED Value 0x21 Description Pool extension failed. create_block() and create_process(). OSE_ENO_USER_SIGSPACE or OSE_ENO_USER_STACKSPACE . The extra parameter contains the size requested. Ignoring this error causes the kernel to allocate the largest buffer available in the pool. Ignoring this error causes the system call to treat the ID as the ID of a killed process. This error is fatal if it occurs when the kernel tries to allocate system pool space as a side effect of system calls. There is no stack of this size or larger in the pool attached to process that called create_process. For errors in the kernel pool. If it is not. The extra parameter contains the initial error code: OSE_ENO_KERN_SPACE. for example. It is impossible to allocate a buffer larger than the largest size available in the pool. The extra parameter contains the size requested. It is possible that the error handler never used the extend_pool() system call.

This error must be handled in a system error handler by killing the current process/program. The extra parameter contains the address of the signal buffer. Restore was attempted on a signal buffer that has already been freed or is otherwise not owned by any process. The extra parameter contains the address of the signal buffer.PCU2 Service Terminal Commands Service terminal commands Error code name OSE_EUSED_NIL_POINTER Value 0x31 Description The caller tried to operate on the NIL pointer. 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. A valid end mark could not be found in the signal buffer presented to the kernel. and attempting to ignore it will only cause the error to be reported again with the fatal flag set. This error may also occur for a wild signal pointer or for a buffer located in a memory segment protected from the caller. The calling process seems to have been writing more data than the size of the buffer allows. The calling process is not the owner of the specified signal buffer. The error cannot be ignored. The buffer has probably already been sent or freed. This error may sometimes also occur for a wild signal pointer. OSE_ENOT_SIG_OWNER 0x5f OSE_ECANNOT_RESTORE 0x57 OSE_ENO_BUFFER_END_MARK 0xa5 DN0479352 Issue 4-2 Id:0900d805806444bc 159 . Such buffers cannot be restored. Ignoring this error causes the illegal system call to be ignored. The extra parameter contains the address of the signal buffer.

Too many signals were attached. An interrupt process was created for a vector that is already allocated to another interrupt process. The system tables allows only a certain number of processes. 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. Ignoring this error causes the system call to return as if it was never called. OSE_ETOO_MANY_ATTACHED 0x24 OSE_ECORRUPTED_KERNEL 0x4a OSE_EVECTOR_IN_USE 0x25 OSE_EILLEGAL_SYSTEMCALL 0x26 160 Id:0900d805806444bc DN0479352 Issue 4-2 . Ignoring this error causes the system call to return as if it was never called. All sizes in a table are zero. The kernel tables were found to be inconsistent. The extra parameter contains an undocumented subcode. but both tables cannot have a count of zero. 2. OSE_ETOO_MANY_PROCESSE S 0x03 Too many processes were created. 4. This error code is used in any of the following illegal cases: 1. pools. Valid counts are 0-8. The count field in the first location is unreasonable. Kernel data was damaged. The extra parameter contains the vector. The system tables allows only a certain number of attached signals. This number was exceeded. The supplied memory fragment does not fit in the address space. or segments. 3. Illegal system call from an interrupt process.Service terminal commands PCU2 Service Terminal Commands Error code name OSE_EUNREASONABLE_SIZES Value 0x23 Description The create_pool system call was exposed to an illegal signal size table or stack size table. The kernel data may have been damaged by a crashed process. The size table is not properly sorted on size. Ignoring this error causes the interrupt process to be removed from the system as if it was never created. The current interrupt or timer process has been using a system call that is only allowed for non interrupt processes. Vector already in use. This number was exceeded.

The priority parameter in the create_process call must match the actual hardware priority at which the interrupt occurs. and attempting to ignore it will only cause the error to be reported again with the fatal flag set. OSE_EBAD_INTLEVEL 0x28 OSE_ERECURSIVE_ERROR 0x29 DN0479352 Issue 4-2 Id:0900d805806444bc 161 . 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. The current interrupt process was invoked with a hardware priority that does not match the priority stated when the interrupt process was created. This error must be handled in a system error handler by killing the current process/program. Illegal wake-up priority for an interrupt process. The extra parameter to the error handler contains the error code supplied in the error system call.PCU2 Service Terminal Commands Service terminal commands Error code name OSE_EINTERSEGMENT_SEND Value 0x27 Description Illegal intersegment send to an interrupt or timer process. The situation was detected in an error system call made by the current process. Ignoring this error causes the process priority to be updated. Signals can be sent to interrupt or timer processes only if the pool associated with the target process is in the same memory segment as the pool associated with the sending process. The error cannot be ignored. The extra parameter to the error handler contains the actual priority encountered. An error was encountered while an error handler was executing.

The extra parameter contains the illegal initial value. An attempt to kill a semaphore that is still in use was made. since a negative semaphore value implies that one or more processes are waiting at the semaphore. A semaphore in another memory segment is unavailable in some memory configurations. This error also occurs when a semaphore that is not available to the calling process is killed. 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 is an illegal situation. Ignoring this error causes the semaphore to be created with an initial value set to zero.Service terminal commands PCU2 Service Terminal Commands Error code name OSE_ERECURSIVE_SYSERROR Value 0x2a Description An error was encountered while an error handler was executing. and attempting to ignore it will only cause the error to be reported again with the fatal flag set. A semaphore cannot be killed when there are processes waiting for it. The situation was detected when an error detected by OSE was about to be reported. Ignoring this error causes the system call to return as if it was never called. The error cannot be ignored. An attempt to kill a static semaphore was made. The extra parameter contains the identity of the first waiting process. An illegal semaphore pointer was presented to the kernel. OSE_EILLEGAL_SEM_VALUE 0x2b OSE_EILLEGAL_SEMAPHORE 0x1f OSE_EKILLED_STATIC_SEMAP HORE 0x1D OSE_EKILLED_SEMAPHORE_IN _USE 0x1E 162 Id:0900d805806444bc DN0479352 Issue 4-2 . Only semaphores created with the create_sem system call can be killed. Ignoring this error causes the system call to return as if it was never called. This error must be handled in a system error handler by killing the current process/program. A semaphore with a negative initial value was found or created.

An attempt was made to detach from a process long after the death of that process. Only one detach call may be issued for each attach call made. The error can sometimes occur as a result of a too small number of attach entries defined in the kernel configuration. This error occurs when processes erroneously use a semaphore located in another memory segment. If you encounter this error for no apparent reason. that is. the caller must be prepared for receiving a subsequent attached signal from the killed process. but processes are still waiting for it. This is illegal. but in a system without memory protection. and the caller failed to notice this for a period long enough for the kernel to discard all attach information for that process. An attempt to detach from an already detached process was made. This error may also occur if detach is called with a bad parameter. An attempt was made to create a process of an invalid type. The kernel cannot understand the difference in all cases.PCU2 Service Terminal Commands Service terminal commands Error code name OSE_EINTERSEGMENT_SEMAP HORE_REF Value 0x2c Description A semaphore in use was implicitly killed. This error must be handled in a system error handler by killing the offending process. Ignoring this error causes detach() to perform no operation. This occurs when all processes in that segment have been killed. This error implies that the attached process has been killed. then try increasing the attach limit in the configuration file. The kernel cannot understand the difference in all cases. This error may also occur if detach is called with a bad parameter. The ID of this process is passed to the error handler in the extra parameter. An attempt was made to detach from a process when the attached signal had already been received. OSE_EDETACHED_TWICE 0x2d OSE_EDETACHED_TOO_LATE 0x2e OSE_EDETACH_AFTER_RECEIV 0x2f E OSE_EBAD_PROCESS_TYPE 0x30 DN0479352 Issue 4-2 Id:0900d805806444bc 163 . Ignoring this error causes the same effect as if detach() was never called. it works up to the point when the memory segment containing the semaphore is reclaimed.

since all static processes are now dead. The field is zero if the ID could not be obtained.c. Analysis indicates 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. A damaged signal buffer was presented to the kernel. Killing a static process is illegal in a system linked to an OSE real-time kernel. The invalid ID was found in the array specifying from which processes signals should be discarded. since the first table entry containing the count and the default process ID is included in the counter. An invalid redirection table was presented to the kernel. The field is zero if the name could not be obtained. The error was reported by the system daemon. The number of entries was zero. This is probably the buffer which was originally damaged. extra[2] = A pointer to the signal buffer that was damaged by the indicated process.Service terminal commands PCU2 Service Terminal Commands Error code name OSE_EILLEGAL_FLUSH_SENDE R Value 0x47 Description An invalid process ID was encountered in the flush system call. 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. Ignoring this error causes the illegal system call to be ignored. A static process was killed. extra[3] = A pointer to the damaged signal buffer that was presented to the kernel by the calling process. which detected the death of the main process in osemain. It is unknown at this time which process was originally killed. This error may also indicate that the first entry of the array contains an invalid array size. It must always be at least one. OSE_EKILLED_STATIC_PROCE SS 0x48 OSE_EILLEGAL_REDIRCOUNT 0x49 OSE_ECORRUPTED_POOL 0xa6 164 Id:0900d805806444bc DN0479352 Issue 4-2 . The field may contain the ID of any process including the current. extra[1] = A pointer to the name of the other process. This is probably only a secondary error indication caused by the extra[2] buffer.

An attempt was made to attach to the current process. Too large interrupt stack buffer requested. The extra parameter to the error handler contains the size of the signal buffer found in the receive queue. 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.PCU2 Service Terminal Commands Service terminal commands Error code name OSE_ESPURIOUS_INTERRUPT Value 0x52 Description An interrupt occurred from an unused interrupt vector. OSE_EATTACHED_TO_CALLER 0x53 OSE_EINTERSEGMENT_COPY_ FAILED 0x54 OSE_EINTSTACK_TOO_LARGE 0x55 DN0479352 Issue 4-2 Id:0900d805806444bc 165 . There may be several possible reasons for this: hardware capable of generating interrupt was erroneously initialised. then a situation may arise where the kernel thinks that the interrupt stack needs to be larger than is actually required by interrupt processes currently in operation. It is illegal to issue an attach call with the ID of the calling process as a parameter. Ignoring this error causes the interrupt stack to be silently truncated to the largest size available. or the system was restarted without issuing a proper hardware reset. If the system is designed such that interrupt processes are frequently created and killed on various interrupt priorities. This error does not necessarily mean that a real problem is present. Planning pools with regard to the largest available buffer size is an important issue in systems where intersegment memory protection is utilised. since the interrupt stack size accumulates worst stack case requirements on each interrupt priority over the system life. The extra parameter contains the accummulated size. The extra parameter to the error handler contains the priority on which the interrupt was encountered. It is nearly always advisable to have all pools support the largest signal size of 64k bytes. or an interrupt process might have been killed without disabling the corresponding hardware. Ignoring this error causes the received signal to be lost. There is no interrupt stack of sufficient size in the system pool.

A superuser system call was used by a non-superuser process. The extra parameter to the error handler contains the process ID of the system daemon. Pool fragments smaller than 1024 bytes are rendered useless. starting only stopped processes. Otherwise the system will crash. the block was found to contain at least one process that was not stopped. For a block ID. Only one process at a time may use it. fragments should be at least several times the size of the largest buffer or stack size. An attempt was made to start a process that is not stopped. Ignoring this error causes the system call to return without creating the pool or installing the pool extension.Service terminal commands PCU2 Service Terminal Commands Error code name OSE_EKILLED_SYSTEM_DAEM ON Value 0x56 Description An attempt was made to kill a system daemon. The extra parameter contains the ID that was passed to the start() call. OSE_EFRAGMENT_TOO_SMALL 0x58 OSE_ECONCURRENT_TICK_CA LL 0x59 OSE_EILLEGAL_USER_CALL 0x5a OSE_EALREADY_STARTED 0x5b 166 Id:0900d805806444bc DN0479352 Issue 4-2 . Using these calls in other processes is illegal. as if the call was never made. An attempt was made to install an unreasonably small pool or pool fragment. This is an arbitrary limit selected because it is believed that fragments this small are always useless. Ignoring this error causes the kill_proc call to return without killing the system daemon. This is a fatal error. The extra parameter to the error handler contains the size of the supplied pool fragment. Tick is a non– reentrant system call. Tick was called concurrently by several processes. The start() system call was invoked with either a process or a block ID. As a general guideline. Some system calls are reserved for use by processes with a user number of zero (the superuser number). Ignoring this error causes the illegal system call to be ignored. Killing a member of the OSE block such as 'ose_sysd' or 'idle' is not allowed. Ignoring the error causes the start() system call to continue.

The extra parameter contains the offending pointer. This was probably caused by a problem related to uninitialised variables. OSE_EILLEGAL_ENVNAME 0x5d OSE_EILLEGAL_POOL 0x5e OSE_EWILD_SIG_POINTER 0x70 OSE_EBAD_PARAMETER 0x71 DN0479352 Issue 4-2 Id:0900d805806444bc 167 . A set_env() or get_env() call was issued with a name parameter set to NULL. Doing this is a design rule violation. or if the linkhandler was stopped or intercepted for more than 10 seconds. possible that the error was caused during debugging instead. Ignoring this error causes the kernel to continue waiting for a response. An invalid parameter was used in a system call. 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. Ignoring this error causes the illegal system call to be ignored. Ignoring this error causes the illegal system call to be ignored. This error code means that one of the parameters to the indicated system call contained an illegal value. An illegal pool ID was presented to the kernel. It is. The operating system checks many of the system call parameters for unreasonable values. An illegal environment variable name was detected. The extra parameter contains the value of the offending parameter. however. The extend_pool() call was issued with a pool_id parameter that refers to an object that is not a pool. The extra parameter contains the process ID of the linkhandler that did not respond. that is the address that should have contained a signal number. Ignoring this error causes the illegal system call to be ignored. Ignoring this error causes the illegal system call to be ignored. This was probably caused by a problem related to uninitialised variables.PCU2 Service Terminal Commands Service terminal commands Error code name OSE_ELINKHANDLER_DEADLO CK Value 0x5c Description A linkhandler deadlock was detected. The operating system was unable to identify the memory pointed to as a signal buffer. An invalid signal pointer was presented to the kernel.

as if the call was never made. Ignoring this error causes the signal to be silently freed. but the mode is set to user mode. Ignoring this error causes the illegal system call to be ignored.Service terminal commands PCU2 Service Terminal Commands Error code name OSE_EFRAGMENT_IN_USE Value 0x72 Description 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. OSE_EILLEGAL_SUPER_MODE 0x73 OSE_ESPURIOUS_SYSTEM_SIG NAL 0x74 OSE_EFRAGMENT_TOO_LARG E 0x75 168 Id:0900d805806444bc DN0479352 Issue 4-2 . The extra parameter contains a pointer to the name of the new block. This error indicates either that the size is unreasonably large. The old pool is probably still in use because it contains signals that are currently owned by a process that is still alive. Ignoring this error causes the system call to return without creating the pool or installing the pool extension. The extra parameter contains the process ID of the sender of the unknown signal. 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 to the error handler contains the size of the supplied pool fragment. An attempt was made to install an unreasonably large pool or pool fragment. Ignoring this error causes the block to be created anyway. The size of the pool fragment presented to the kernel is too large for the fragment to fit in the address space. or that the base of the memory fragment is too close to the end of the address space. An unrecognised signal was received by one of the system daemon processes. Pools do not die until the last signal in the pool has been freed. The extra parameter contains the base of the offending pool space. This error can also be reported if pool space is allocated on the stack of the caller by mistake.

One or more entries in the kernel configuration file has an illegal value. An attempt was made to signal a semaphore or a fast semaphore beyond the maximum value. Ignoring this error causes the priorities to be automatically adjusted. as if the call was never made.PCU2 Service Terminal Commands Service terminal commands Error code name OSE_ESTOP_OVERFLOW Value 0x76 Description An attempt was made to stop a process for an unreasonable number of times. OSE_ESEM_OVERFLOW 0x77 OSE_EBAD_HUNT_PRI 0x78 OSE_EILLEGAL_PRISYSTEMCA LL 0x79 OSE_EILLEGAL_CONFIGURATI ON 0x7a DN0479352 Issue 4-2 Id:0900d805806444bc 169 . Ignoring this error causes the system call to return without executing the stop operation. The current background. The extra parameter to the error handler contains the ID of the process stopped. The ose_huntd process must have a priority higher than the ose_sysd process. This error occurs when the semaphore value wraps from two giga times to two giga times. Illegal kernel configuration. The extra parameter to the error handler contains this value. Ignoring this error causes the system call to return without executing the semaphore operation. Ignoring this error will cause the kernel to adjust the value to the closest legal value. Semaphores can only be signalled a limited number of times before a wait operation is performed. The extra parameter to the error handler contains the address of the semaphore or the process ID to which the fast semaphore belongs. Illegal system call from an interrupt or background process. interrupt or timer process has been using a system call that is only allowed for prioritised processes. as if the call was never made. Bad kernel configuration. The huntd priority is too low. This error occurs when the stop-counter wraps from four giga times to zero.

An attempt has been made to cancel or restart a time-out signal request that was already cancelled. The extra parameter contains the CPU's program counter. Supervisor stack exhausted. system pool size and CPU power permitting. Time-out signal already received.Service terminal commands PCU2 Service Terminal Commands Error code name OSE_ETOO_MANY_TMO_REQU ESTS Value 0x7b Description Too many time-out signal requests. OSE_ETMO_ALREADY_CANCEL LED 0x7c OSE_ETMO_ALREADY_RECEIV ED 0x7d OSE_EUSER_STACK_OVERFLO W 0x101 OSE_ESUPERV_STACK_OVERF LOW 0x102 OSE_EINTERRUPT_STACK_OV ERFLOW 0x103 OSE_EUNKNOWN_BREAKPOIN T 0x104 170 Id:0900d805806444bc DN0479352 Issue 4-2 . An unknown breakpoint was encountered. The error cannot be ignored. User stack exhausted. This is a fatal error. Ignoring this error will cause the system call to return without further action. Stack overwrite in an interrupt stack. The extra parameter to the error handler contains the actual limit. An attempt has been made to cancel or restart a time-out signal request when the signal was already received by the application. Ignoring this error causes the system call to return without further action. The extra parameter to the error handler contains the time-out identity returned by the time-out request. This error can only be caught by the kernel error handler. The extra parameter contains the address to the first byte beyond the stack. This is a fatal error. This error must be handled by killing the current process/program. The error cannot be ignored. The limit is at least 1000 000. This is a fatal error. Too many concurrently running time-out signal requests have been made. The extra parameter contains the address to the first byte beyond the stack. The extra parameter contains the address to the first byte beyond the stack. This error may also indicate that wrong process tried to cancel or restart the time-out. and attempting to ignore it will only cause the error to be reported again with the fatal flag set. Time-out signal already cancelled.

This is a fatal error. The exception offset (or vector offset on some CPUs) is supplied in the subcode field. The kernel configuration needs to contain a known CPU model. Kernel start-up stack exhausted. This error is issued when a start handler has used too much stack space. An undefined function code has been used for a system call. The interrupt controller must not allow an interrupt process to be interrupted by an interrupt process with equal or lower priority. An unexpected exception occurred. This is a fatal error. The extra parameter contains the value configured. The extra parameter contains the function code number. The extra parameter contains the CPU's program counter. The reason for this is probably that interrupts have not been masked properly in the interrupt controller. The extra parameter contains vector number. The extra parameter contains the illegal priority. This is a fatal error.PCU2 Service Terminal Commands Service terminal commands Error code name OSE_EUNKNOWN_INTERRUPT Value 0x105 Description An unknown interrupt was encountered. Interrupt priority error. OSE_EPROCESS_ENDED 0x107 OSE_ESTART_STACK_OVERFL OW 0x108 OSE_EUNRECOGNIZED_CPU 0x109 OSE_EUNDEFINED_SYSCALL_C ODE 0x110 OSE_EUNEXPECTED_EXCEPTI ON 0x111 OSE_EPRIORITY_ERROR 0x112 OSE_EUNEXPECTED_EXCEPTI ON_REGDUMP 0x113 DN0479352 Issue 4-2 Id:0900d805806444bc 171 . An interrupt has occurred with equal or less priority than the currently running interrupt process. Ignoring this error will cause the process to be killed. This is a fatal error. A prioritised or background process ended. The extra parameter contains a pointer to a register dump. The extra parameter contains the process ID. Ignoring this error causes the system call to return with the return value zero. The CPU model is not recognised. An unexpected exception occurred.h. described in cpu. This is a fatal error. This is a fatal error. The extra parameter contains the address to the first byte beyond the stack. The exception offset is supplied in the subcode field.

The caller is therefore not an OSE process but a kernel handler. PLS internal error. extra[3] = The source line number of the calling program if it could be obtained. PLS process unexpectedly killed. 0x500001 0x500002 172 Id:0900d805806444bc DN0479352 Issue 4-2 . The field is zero if the name could not be obtained. The caller is therefore not an OSE process but a kernel handler. 2. Use SUBCODE_MASK to extract this field. otherwise zero. Usually it points into the kernel access library. This is a fatal error. This is a fatal error. A program has called error() or error2() before the kernel start-up was complete. extra[1] = Original extra argument to error2(). No system calls can be used in the error handler. called in the start phase. 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. The extra parameter is a pointer to the received signal. OSE_ESYSCALL_TOO_EARLY 0x115 A kernel system call was used before the kernel was operable. otherwise zero. called in the start phase. A program has used a kernel system call before the kernel start up was complete. No system calls can be used in the error handler.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.Service terminal commands PCU2 Service Terminal Commands Error code name OSE_EEARLY_ERROR Value 0x114 Description An error has been reported before the kernel was operable. extra[2] = A pointer to the file name of the calling program. Error code description for Program Handler Error code name OSE_PRH_PLS_EINVALID_SIGN AL OSE_PRH_PLS_EINTERNAL OSE_PRH_PLS_EPROCESS_KIL LED Value 0x500000 Description PLS received an invalid (unknown) signal. The extra parameter contains the return address of the system call.

PLS could not install a trap handler. Obsolete: PLS could not find MMS. File write failed. The lower 8 bits are the errno code. The lower 8 bits are the errno code. and the extra parameter is a pointer to the name of the directory. Obsolete: file names for load modules cannot be longer than 255 characters. and the extra parameter is a pointer to the name of the file. The extra parameter is a pointer to the duplicate load module identity. Error code description for Archive Server Error code name OSE_PRH_ASF_EINVALID_SIGN AL OSE_PRH_ASF_EOPEN_DIR_FA ILED Value 0x520000 Description ASF received an invalid (unknown) signal. File read failed. 0x520100 OSE_PRH_ASF_EOPEN_FILE_F AILED 0x520200 OSE_PRH_ASF_ECREATE_FILE _FAILED 0x520300 OSE_PRH_ASF_EREAD_FILE_F AILED 0x520400 OSE_PRH_ASF_EUNLINK_FAILE D 0x520500 OSE_PRH_ASF_EWRITE_FILE_F 0x520600 AILED OSE_PRH_ASF_ECLOSE_FILE_ FAILED 0x520700 OSE_PRH_ASF_EPROCESS_KIL LED OSE_PRH_ASF_EDUPLICATE_L M 0x520800 0x520900 OSE_PRH_ASF_ETOO_LONG_FI 0x520A00 LE_NAME DN0479352 Issue 4-2 Id:0900d805806444bc 173 .PCU2 Service Terminal Commands Service terminal commands Error code name OSE_PRH_PLS_ECREATE_PRO CESS OSE_PRH_PLS_ENO_MMS OSE_PRH_PLS_BIOS_INSTALL_ FAILED Value 0x500003 0x500004 0x500005 Description Obsolete: PLS process failed when created. and the extra parameter is a pointer to the name of the file. File close failed. Could not create a file. Could not open a directory. and the extra parameter is a pointer to the name of the file. The lower 8 bits are the errno code. An ASF process unexpectedly killed. The lower 8 bits are the errno code. The lower 8 bits are the errno code. The lower 8 bits are the errno code. and the extra parameter is a pointer to the name of the file. File unlink (remove) failed. The extra parameter is a pointer to the received signal. and the extra parameter is a pointer to the name of the file. Local store contains the same load module ID in several files. 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.

The 32-bit error parameter passed to an error handler is organised as follows: D7.. The extra parameter is a pointer to the last TFTP configuration string.16.D8 D29. Example: "172. A 14-bit wide subcode. A 1-bit wide fatal flag. and the hostdir must end with '/' (unix) or '\' (win32).Service terminal commands PCU2 Service Terminal Commands Error code name OSE_PRH_ASF_EBAD_TFTP_C ONFIGURATION Value 0x520B00 Description A TFTP archive server is used without or with an incorrect host address or host directory. The fatal bit conveys this information.232.. If the error occurs after the kernel has initialised. the port is optional.16.con). Defined by the constants below. Each MMS error code contains five fields: • • • • • An 8-bit wide main error code. cleared for a warning...232./" or "172..D0 D15. during the execution of mMSStartHandler1 or any other START_HANDLER1. If the error occurs during pre-kernel initialisation.. All errors generated by the MMS are application generated (user_called). the user supplied early error handler is called (see EARLY_ERROR_HANDLER in the configuration file mms. Error code description for MMS The error reporting mechanism that the MMS uses depends on when the error occurs. A 1-bit wide supervisor flag. A few of the errors are non-fatal warnings. The TFTP configuration syntax is 'host[:port] hostdir' where the host is IP address of the TFTP server.1:69 . This part is valid only for some main error codes.1 /tftpboot/". in other words.D16 D30 D31 main error code exception code subcode supervisor flag fatal flag The following masks are used to extract the various error parameter fields. Set if the error occurred while in supervisor mode. Parameter name OSE_MMS_EFATAL_MASK OSE_MMS_ESUPERVISOR_MASK OSE_MMS_ESUBCODE_MASK OSE_MMS_EEXCEPTION_CODE_MASK OSE_MMS_EERROR_MASK Description 0x80000000 0x40000000 0x3FFF0000 0x0000FF00 0x000000FF 174 Id:0900d805806444bc DN0479352 Issue 4-2 . Set for a fatal error. An 8-bit wide exception code. the system call err is used instead. cleared otherwise.

See readme files.PCU2 Service Terminal Commands Service terminal commands 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. This is a fatal error. executable areas. This is a fatal error. and the fault is fatal to the system. Therefore. This is a fatal error. Parameter OSE_MMS_SUPERVISOR_MODE OSE_MMS_USER_MODE Description 0x40000000 0x00000000 Error code descriptions for MMS: Error code name OSE_MMS_EMMU_NOT_SUPPO RTED Value 0x00580000 Description The MMS does not recognise the version of the MMU. This is a fatal error. in other words. Illegal configuration. perhaps implementation error for a specific MMU. This is because it will be isolated to the scope of that process. This is a fatal error. The system limits of the number of local domains. Normally the fault is non-fatal to the system if it occurred in user mode. There was no definition of executable memory. if the fault occurred in supervisor mode. or MMS memory areas were exceeded. This is a fatal error. the error handler should shut down the system. An erroneous start-up sequence. This is a fatal error. The memory dedicated as MMS memory is not sufficient. This is a fatal error. This is a fatal error. so it cannot perform any mapping. Shut down the system and decrease the number of items. The definition of executable memory was illegal. the region of memory in which it is executing. There are overlapping definitions in the static configuration. OSE_MMS_ETOO_MANY_DOMA INS 0x00580001 OSE_MMS_ETOO_MANY_EXEC _AREAS OSE_MMS_ETOO_MANY_BANK S OSE_MMS_EOVERLAPPING_DE F OSE_MMS_EEND_OF_MEMORY 0x00580002 0x00580003 0x00580004 0x00580005 OSE_MMS_EILLEGAL_CONFIGU RATION OSE_MMS_ENO_CODEDATA OSE_MMS_EILLEGAL_EXEC_AR EA 0x00580006 0x00580007 0x00580008 OSE_MMS_EILLEGAL_START_S EQ 0x00580009 DN0479352 Issue 4-2 Id:0900d805806444bc 175 . the system cannot be guaranteed to be in a consistent state. This is a fatal error. However.

and a cold start was forced. LOCAL_REGION). The get_spr_value() hook returned an illegal value for a SPR register. The information detected after warm start was corrupted. The type definition of the register file dump is described below. This is a fatal error. 176 Id:0900d805806444bc DN0479352 Issue 4-2 . Illegal access mode of region. This error consists of an error code and a pointer to a dump of the register file content at the time of the exception. An error was encountered when trying to fetch configuration information from BIOS. The field exception code indicates the type of the exception. An unexpected exception occurred. The size is not one of the legal sizes. Note that the error handler will not execute the code beyond an eventual kill_proc command. All regions (GLOBAL_REGION. The extra parameter contains the SPR number. This is a fatal error. This error must be reported to OSE systems. This is a fatal error. and a cold start was forced. or the start address of the page table is not a multiple of the size. and MMS heap (MMS_MEMORY) must be aligned on a page boundary (4 kbyte). The field exception code indicates the type of the exception. Illegal placement of a page table. An internal error that should not occur. The extra parameter in the error handler call is the pointer.Service terminal commands PCU2 Service Terminal Commands Error code name OSE_MMS_EILLEGAL_ALIGNME NT Value 0x0058000A Description Illegal alignment. executable memory (CODE_DATA). OSE_MMS_EILLEGAL_ACCESS_ TYPE 0x0058000B OSE_MMS_EPAGETABLE_ILLEG 0x0058000C AL_CONFIGURATION OSE_MMS_ECORRUPTED_REC OVERY OSE_MMS_ENONPROTECTED_ RECOVERY OSE_MMS_EINTERNAL 0x00580010 0x00580011 0x00580012 OSE_MMS_EBIOS_PARSE_ERR OR OSE_MMS_EILLEGAL_L2_CACH E_CONFIGURATION 0x00580015 0x00580016 OSE_MMS_EUNEXPECTED_EX CEPTION 0x00580013 OSE_MMS_ENESTED_EXCEPTI ON 0x00580014 An exception has occurred while processing another one inside the MMS. The information detected after warm start was in a non-protected state. It is non-recoverable and system-fatal. The execution mode at the time of the fault is always given in exception faults.

the set of functions for this CPU contained the wrong number of functions. The symbol description table is corrupt or in an unknown format. The symbol description table must be compiled with the same structure alignment and padding as the GLH. An invalid link ID for a new connection specified by the PLH. The symbol description table pointer which is stored in environment variable oseSigdescTab is illegal. The symbol description table size is not as expected. OSE_MMS_DETECT_CPU_FAILE 0x00580017 D OSE_MMS_CPUFUNCS_MISMAT 0x00580018 CH OSE_MMS_ILLEGAL_STATIC_R EG 0x00580019 Error code description for General Link Handler Error code name OSE_GLH_EBUFBEG_OFFS_ER ROR OSE_GLH_EUNDEFINED_SIG Value 0x00600000 0x00600001 Description An invalid bufbeg configuration. the signal will be freed. and the GLH will continue operation. The main GLH process was shut down (killed) incorrectly. When probing for CPU functions. The GLH received an unknown signal. This indicates that the version of the mmshal cpu functions does not match the version of the rest of the MMS library. A process internal to the GLH was killed.con'. Never kill any GLH processes. Creating static regions for a segment other than the system segment is not allowed for the current implementation and CPU.PCU2 Service Terminal Commands Service terminal commands Error code name Value Description The armhal package failed to find CPU-specific functions for the current CPU. Verify that your CPU is listed in the file 'mmshal. If the error handler returns ok. It should be a multiple of 4. OSE_GLH_ELINKID_0 OSE_GLH_EINTERNAL_PROC_T ERMINATED OSE_GLH_EGLH_TERMINATED 0x00600002 0x00600003 0x00600004 OSE_GLH_EILLEGAL_SIGDESC TAB_PTR 0x0060000A OSE_GLH_ESIGDESCTAB_COR RUPT OSE_GLH_EWRONG_SIGDESC_ SIZE 0x0060000B 0x0060000 DN0479352 Issue 4-2 Id:0900d805806444bc 177 . The extra parameter is a pointer to the received signal. The proper way to terminate a GLH is to send a GLH_TERMINATE signal to the GLH. The extra parameter contains the segment ID (!= 0) that was used to create the region.

This is a fatal error. It should be a multiple of 4 bytes. The Signal Size received is invalid. Make it larger. and the GPL will continue operation. Invalid number of buffered acks configuration. More than one link handler with the same name detected. Invalid PDR configuration. Make sure that the tables on the sender and receiver side are identical. The extra parameter is a pointer to the received signal. This indicates that the symbol description table generator is not working properly. Invalid transmit time-out configuration. It should be >= 1. Invalid bufbeg offset configuration. The GPL received an unknown signal. The GLH received a converted signal sent from a remote GLH. If the error handler returns ok. It should be <= 28 (the size of sliding window queue 4). The GLH detected an internal error (inconsistency). Invalid maximum sigsize configuration. It should be >= 10 ms. It should be less than or equal to the maximum number of outstanding bytes. Invalid max flush configuration. but the signal number was not found in the symbol description table. It should be >= 1. It is too small. neither PDR process PID nor PDR callback function specified. the signal will be freed. Invalid number of retransmits configuration. The lower 12 bits is the line number in the source file.Service terminal commands PCU2 Service Terminal Commands Error code name OSE_GLH_EDUPLICATE_SIGNA L Value 0x0060000D Description The symbol description table contains two identical symbols. OSE_GLH_ERECEIVE_NO_SIGN AL_FOUND 0x0060000F OSE_GLH_ESIGNAL_SIZE OSE_GLH_EINTERNAL_ERROR 0x00600010 0x80601000 Error code description for General Protocol Link Handler Error code name OSE_GPL_EMAX_SIG_SIZE Value 0x80640000 Description Invalid maximum sigsize configuration. OSE_GPL_EMAX_SIG_SIZE_TO O_SMALL OSE_GPL_EBUFBEG_OFFS_ER ROR OSE_GPL_ENO_OF_RETRANSM ITS OSE_GPL_EMAX_FLUSH OSE_GPL_ETIMEOUT_TRANSMI T OSE_GPL_EPID_PDR_OR_ACTI ON_TRANSMIT OSE_GPL_ENO_OF_BUFFERED _ACK 0x80640001 0x80640002 0x80640003 0x80640004 0x80640005 0x80640007 0x80640008 OSE_GPL_EUNDEFINED_SIG 0x80640009 OSE_GPL_ENAME_IN_USE 0x8064000A 178 Id:0900d805806444bc DN0479352 Issue 4-2 .

The GPL received an invalid signal from a remote link handler. If the application returns from the error handler. sendto() failed. If the error handler returns. lower 8 bits is the errno value. The initialisation signals to the link handler were sent in the wrong order. OSE_GPL_EWRONG_CONFIG_ ORDER 0x80640011 Error code description for UDP Driver for General Protocol Link Handler Error code name Value Description socket() failed. O_NDELAY) failed. The maximum is 4095. lower 8 bits is the errno value. the offending signal will be ignored and freed. and then restarted. lower 8 bits is the errno value. lower 8 bits is the errno value. This is a fatal error.PCU2 Service Terminal Commands Service terminal commands Error code name OSE_GPL_EREM_ADDR_EQU_B ROADC_ADDR OSE_GPL_EPDR_CEASED OSE_GPL_ECORRUPT_GPL_TR ANS_ACK_RECEIVE_SIG OSE_GPL_ECORRUPT_GPL_RE CEIVE_SIG Value 0x8064000B Description A link handler with an invalid address (IP-address:UDP-port) was found. lower 8 bits is the errno value. fcntl(F_SETFL. close() failed. lower 8 bits is the errno value ioctl(SIOCGIFBRDADDR) failed. The extra parameter contains the initialisation signal that triggered this error. OSE_UDPPDR_ESOCKET_FAILE 0x00660000 D OSE_UDPPDR_EIOCTL_GIFADD R_FAILED 0x00660100 OSE_UDPPDR_ECLOSE_FAILED 0x00660200 OSE_UDPPDR_EIOCTL_GIFBRD ADDR_FAILED OSE_UDPPDR_ESENDTO_FAIL ED OSE_UDPPDR_EFCNTL_NDELA Y_FAILED 0x00660300 0x00660400 0x00660500 DN0479352 Issue 4-2 Id:0900d805806444bc 179 . The GPL detected an inconsistency in the sliding window handling. It is safe to return from this error. The GPL detected an inconsistency probably caused by the PDR. 0x8064000C 0x8064000D 0x8064000E OSE_GPL_ETOO_MANY_REM_C 0x8064000F ONNECTIONS Error code description for General Protocol Link Handler Error code name OSE_GPL_EMAX_QUEUE_LENG TH_REACHED Value 0x80640010 Description This error is reported by the SendCongestion Handling mechanism when the user-specified maximum queue length is reached. the connection will be taken down. ioctl(SIOCGIFADDR) failed. Too many simultaneous connections attempted.

SO_SNDBUF) failed. lower 8 bits is the errno value recvfrom() failed. select() failed. lower 8 bits is the errno value. the extra parameter points to the signal. The extra parameter points to the specified BIOS name. lower 8 bits is the errno value. getsockname() failed. lower 8 bits is the errno value. SO_BROADCAST) failed. SO_RCVBUF) failed. SO_REUSEADDR) failed. lower 8 bits is the errno value. The signal will be freed. setsockopt(SOL_SOCKET. lower 8 bits is the errno value. lower 8 bits is the errno value setsockopt(SOL_SOCKET. lower 8 bits is the errno value. biosOpen() failed.Service terminal commands PCU2 Service Terminal Commands Error code name OSE_UDPPDR_ESETSOCKOPT_ REUSEADDR_FAILED OSE_UDPPDR_EBIND_FAILED OSE_UDPPDR_EGETSOCKNAM E_FAILED OSE_UDPPDR_ESETSOCKOPT_ BROADCAST_FAILED OSE_UDPPDR_ESETSOCKOPT_ RCVBUF_FAILED OSE_UDPPDR_ESETSOCKOPT_ SNDBUF_FAILED OSE_UDPPDR_ERECVFROM_F AILED Value 0x00660600 Description setsockopt(SOL_SOCKET. bind() failed. select() failed. lower 8 bits is the errno value setsockopt(SOL_SOCKET. lower 8 bits is the errno value 0x00661000 Error code description for Serial Driver for General Protocol Link Handler Error code name OSE_SERPDR_EUNKNOWN_SI GNAL Value 0x00670000 Description SERPDR received an unwanted signal. This error is not fatal. SO_REUSEPORT) failed. The extra parameter points to the specified BIOS name. OSE_SERPDR_ENO_DRIVER 0x00670100 OSE_SERPDR_ENOT_A_DRIVE R 0x00670200 180 Id:0900d805806444bc DN0479352 Issue 4-2 . and the link handler will continue operation. setsockopt(SOL_SOCKET. BIOS module was not a device driver. no such BIOS module. lower 8 bits is the errno value 0x00660700 0x00660800 0x00660900 0x00660A00 0x00660B00 0x00660C00 Error code description for UDP Driver for General Protocol Link Handler Error code name OSE_UDPPDR_ESELECT_FAILE D OSE_UDPPDR_SIOCGIFFLAGS_ FAILED OSE_UDPPDR_SIOCGIFBRDAD DR_OR_SIOCGIFDSTADDR_FAI LED OSE_UDPPDR_ESETSOCKOPT_ REUSEPORT_FAILED Value 0x00660D00 0x00660E00 0x00660F00 Description select() failed.

The extra parameter points to the specified BIOS name.PCU2 Service Terminal Commands Service terminal commands Error code name OSE_SERPDR_EDDOPEN_FAIL ED OSE_SERPDR_EDDSETCONF_F AILED Value 0x00670300 0x00670400 Description ddOpen() failed. ddStart() failed. The extra parameter points to the specified BIOS name. The packet will be freed. lower 8 bits is the device driver error code. Invalid or unsupported baud rate. lower 8 bits is the errno value. OSE_ETHPDR_EUNKNOWN_SIG 0x00680000 NAL OSE_ETHPDR_ENO_DRIVER 0x00680100 OSE_ETHPDR_ENOT_A_DRIVE R OSE_ETHPDR_EDDOPEN_FAIL ED OSE_ETHPDR_EDDSETCONF_F AILED 0x00680200 0x00680300 0x00680400 DN0479352 Issue 4-2 Id:0900d805806444bc 181 . tcsetattr() failed. tcgetattr() failed. The extra parameter points to the signal. The packet will be freed. lower 8 bits is the device driver error code. ddWrite() failed. read() failed. lower 8 bits is the device driver error code. lower 8 bits is the device driver error code. lower 8 bits is the device driver error code. lower 8 bits is the errno value. ddGetConf() failed. biosOpen() failed. The signal will be freed. and the link handler will continue operation. lower 8 bits is the device driver error code. no such BIOS module. The error will be ignored. and the link handler will continue operation. lower 8 bits is the errno value. lower 8 bits is the errno value. OSE_SERPDR_EDDGETCONF_F 0x00670500 AILED OSE_SERPDR_EDDSTART_FAIL ED OSE_SERPDR_EDDWRITE_FAIL ED 0x00670600 0x00670700 OSE_SERPDR_EOPEN_FAILED OSE_SERPDR_ETCGETATTR_F AILED OSE_SERPDR_ETCSETATTR_F AILED OSE_SERPDR_EWRITE_FAILED 0x00671800 0x00671900 0x00671A00 0x00671B00 OSE_SERPDR_EREAD_FAILED 0x00671C00 OSE_SERPDR_EINVALID_BAUD RATE 0x00671D00 Error code description for Ethernet Driver for General Protocol Link Handler Error code name Value Description ETHPDR received an unwanted signal. This error is not fatal. write() failed. This error is not fatal. ddSetConf() failed. ddOpen() failed. lower 8 bits is the errno value. and the link handler will continue operation. open() failed. This error is not fatal. BIOS module was not a device driver. ddSetConf() failed. lower 8 bits is the device driver error code. and the link handler will continue operation. This error is not fatal.

The packet will be freed. bind() failed. lower 8 bits is the errno value Error code description for Telnet Server Error code name OSE_TELNETD_ESOCKET_FAIL ED OSE_TELNETD_EBIND_FAILED OSE_TELNETD_ELISTEN_FAILE D Value 0x6C0000 0x6C0100 0x6C0200 Description socket() failed. listen() failed. ddWrite() failed. accept() failed. lower 8 bits is the errno value. lower 8 bits is the errno value. and the link handler will continue operation. Error code description for TFTP Server Error code name OSE_TFTPD_ESOCKET_FAILED OSE_TFTPD_EBIND_FAILED OSE_TFTPD_ERECVFROM_FAIL ED OSE_TFTPD_ECONNECT_FAILE D Value 0x00690000 0x00690100 0x00690200 0x00690300 Description socket() failed. OSE_FTPD_EACCEPT_FAILED. listen() failed. lower 8 bits is the errno value. connect() failed. bind() failed. lower 8 bits is the errno value. Error code description for FTP Server Error code OSE_FTPD_ESOCKET_FAILED OSE_FTPD_EBIND_FAILED OSE_FTPD_ELISTEN_FAILED. recvfrom() failed. OSE_FTPD_ESETSOCKOPT_RE USEADDR_FAILED Value 0x006B0000 0x006B0100 0x006B0200 0x006B0300 0x006B0400 Description socket() failed. lower 8 bits is the errno value. lower 8 bits is the device driver error code. This error is not fatal.Service terminal commands PCU2 Service Terminal Commands Error code name OSE_ETHPDR_EDDGETCONF_F AILED OSE_ETHPDR_EDDSTART_FAIL ED OSE_ETHPDR_EDDWRITE_FAIL ED Value 0x00680500 0x00680600 0x00680700 Description ddGetConf() failed. 182 Id:0900d805806444bc DN0479352 Issue 4-2 . lower 8 bits is the errno value. lower 8 bits is the errno value. setsockopt(SO_REUSEADDR) failed. bind() failed. lower 8 bits is the errno value. lower 8 bits is the errno value. lower 8 bits is the device driver error code. lower 8 bits is the device driver error code. lower 8 bits is the errno value. ddStart() failed. lower 8 bits is the errno value.

Call to setsockopt failed. OSE_BOOTP_ESOCKET_FAILED 0x006E0001 OSE_BOOTP_EBIND_FAILED OSE_BOOTP_ESENDTO_FAILE D OSE_BOOTP_ESIGNAL_FAILED 0x006E0002 0x006E0003 0x006E0004 DN0479352 Issue 4-2 Id:0900d805806444bc 183 . setsockopt(SO_OSEOWNER) failed.PCU2 Service Terminal Commands Service terminal commands Error code name OSE_TELNETD_EACCEPT_FAIL ED OSE_TELNETD_ESETSOCKOPT _OSEOWNER_FAILED OSE_TELNETD_ESETSOCKOPT _KEEPALIVE_FAILED OSE_TELNETD_ESETSOCKOPT _OSEASYNC_FAILED OSE_TELNETD_ESETSOCKOPT _OSEEVENT_FAILED OSE_TELNETD_EIOCTL_FIONBI O_FAILED Value 0x6C0300 0x6C0400 Description accept() failed. close() failed. lower 8 bits is the errno value. The extra parameter contains the INET errno. bind() failed. Error code description for Bootp Client Error code name Value Description INET socket() failed. An unknown signal was received. lower 8 bits is the errno value. setsockopt(SO_OSEASYNC) failed. An unexpected error while reading. lower 8 bits is the errno value. lower 8 bits is the errno value. The extra parameter contains the INET errno. lower 8 bits is the errno value. setsockopt(SO_OSEEVENT) failed. INET bind failed. setsockopt(SO_KEEPALIVE) failed. lower 8 bits is the errno value. listen() failed. 0x6C0500 0x6C0600 0x6C0700 0x6C0800 Error code description for OSE System Surfer Error code name OSE_SURFER_SOCKET OSE_SURFER_SETSOCKOPT OSE_SURFER_BIND OSE_SURFERLISTEN OSE_SURFER_NONBLOCK OSE_SURFER_ACCEPT OSE_SURFER_READ OSE_SURFER_CLOSE Value 0x006D1000 0x006D2000 0x006D3000 0x006D4000 0x006D5000 0x006D6000 0x006D7000 0x006D8000 Description socket() failed. lower 8 bits is the errno value. ioctl(FIONBIO) failed. lower 8 bits is the errno value. lower 8 bits is the errno value. accept() failed. sendto failed. The extra parameter contains the INET errno. lower 8 bits is the errno value. A non-blocking call failed. lower 8 bits is the errno value. The extra parameter contains a pointer to signal.

connect() failed. The extra parameter contains the INET errno. The extra parameter contains the INET errno. lower 8 bits is the errno value. No sockets could be created. This is a fatal error. inet_send failed. Could not set subnet mask. The DHCP client received an unknown DHCP message from the server. The extra parameter contains the INET errno.Service terminal commands PCU2 Service Terminal Commands Error code name OSE_BOOTP_ESOCKOPT_FAIL ED Value 0x006E0005 Description Call to setsockopt failed. Failed to create a socket. The extra parameter contains the INET errno. Failed to set socket in async. The process ose_resolve could not be found. mode. Error code description for DHCP Client Error code name OSE_DHCP_EIF_IOCTL OSE_DHCP_EIF_IOCTL_SET_IP OSE_DHCP_EADD_ROUTE Value 0x006F1001 0x006F1002 0x006F1003 Description The ioctl call to get/set information on an IF failed. setsockopt(SO_OSEASYNC) failed. The DHCP client received an unknown OSE signal. INET sendto failed. OSE_DHCP_ESET_SUBNET 0x006F1004 OSE_DHCP_ESOCKET_FAILED OSE_DHCP_ESOCKOPT_FAILE D OSE_DHCP_ESENDTO_FAILED OSE_DHCP_EUNKNOWN_SIGN AL OSE_DHCP_ESIGNAL_FAILED 0x006F1005 0x006F1006 0x006F1007 0x006F1008 0x006F1009 184 Id:0900d805806444bc DN0479352 Issue 4-2 . Error code description for DNS Resolver Error code name OSE_RES_ESOCKET_FAILED OSE_RES_ENO_SOCKET OSE_RES_ESETSOCKOPT_OSE ASYNC_FAILED OSE_RES_EINET_SEND_FAILE D OSE_RES_EUNKNOWN_SIGNAL OSE_RES_ENOT_INITIALIZED OSE_RES_DAEMON_TIME_OUT OSE_RES_ECONNECT_FAILED Value 0x006F0001 0x006F0002 0x006F0003 0x006F0004 0x006F0005 0x006F0006 0x006F0007 0x006F0008 Description INET socket() failed. An unknown signal was received by ose_resolve. The extra parameter contains the INET route status. Could not add route. Resolver has not been initialised. The extra parameter contains the INET errno. The Interface ioctl to set the new IP address failed. The extra parameter contains the INET errno.

An unknown DNS class number. The extra parameter contains the signal.PCU2 Service Terminal Commands Service terminal commands Error code name OSE_DHCP_EBIND_FAILED OSE_DHCP_EMKQUERY OSE_DHCP_EGET_HWADDR OSE_DHCP_EIF_IOCTL_GET_IP OSE_DHCP_EMALLOC Value 0x006F100A 0x006F100B 0x006F100C 0x006F100D 0x006F100E Description bind() failed. getsockname() failed. bind() failed. The extra parameter contains the requested size. The extra parameter contains the requested size. An unexpected error while reading a file. The DHCP client failed to get the HW address for the interface. Error code description for FTP Client Error code name OSE_FTP_ESOCKET_FAILED OSE_FTP_EBIND_FAILED OSE_FTP_EBAD_SOCKET OSE_FTP_EMALLOC Value 0x006F2001 0x006F2002 0x006F2003 0x006F2004 Description Failed to create a socket. OSE_DNS_SRV_DAEMON_TIME _OUT 0x00C2200A DN0479352 Issue 4-2 Id:0900d805806444bc 185 . The extra parameter contains the INET errno. The extra parameter contains the INET errno. The ose_dnsd process could not be found. The Interface ioctl failed to get the IP address. Extra parameter contains the INET errno. An unknown signal was received. The extra parameter contains the INET errno. The extra parameter contains the INET errno. connect() failed. Error code description for DNS Server Error code name OSE_DNS_SRV_ESOCKET OSE_DNS_SRV_ESETSOCKOPT OSE_DNS_SRV_EBIND OSE_DNS_SRV_CONNECT OSE_DNS_SRV_ESEND OSE_DNS_SRV_ECLASS OSE_DNS_SRV_ETYPE OSE_DNS_SRV_EREAD OSE_DNS_SRV_ESIG Value 0x00C22001 0x00C22002 0x00C22003 0x00C22004 0x00C22005 0x00C22006 0x00C22007 0x00C22008 0x00C22009 Description INET socket() failed. setsockopt() failed. Could not allocate memory from the heap. The DHCP client failed to create a valid DHCP message. The extra parameter contains the INET errno. send() failed. An unknown DNS type number. Could not allocate memory from the heap. Failed to bind a socket.

Call to setsockopt failed. lower 8 bits is the errno value. BIOS install failed. The extra parameter contains a pointer to a HeapBufferInfoReply struct. Ignore the error. A non-blocking call failed. The pointer to the signal is stored in the address field of the struct. Heap daemon received an unknown signal. The unknown function code is stored in the status field of the struct.Service terminal commands PCU2 Service Terminal Commands Error code name OSE_DNS_SRV_EOPCODE Value 0x00C2200B Description An unknown opcode received in a DNS message. A BIOS call failed. Server received an unknown BIOS function code. lower 8 bits is the errno value. Function library could not find ose_heapd. Error code description for Heap Manager Error code name OSE_HEAP_EBIOS_INSTALL_FA ILED Value 0x820000 Description Server could not install a trap handler. and the signal will be ignored. bind() failed. close() failed. listen() failed. Error code description for Web Server (WEBS) Error code name WEBSERR_SOCKET WEBSERR_SETSOCKOPT WEBSERR_BIND WEBSERR_LISTEN WEBSERR_NONBLOCK WEBSERR_CLOSE WEBSERR_BIOSINSTALL WEBSERR_BIOSOPEN WEBSERR_BIOSCALL Value 0x00711000 0x00712000 0x00713000 0x00714000 0x00715000 0x00716000 0x00717000 0x00718000 0x00719000 Description socket() failed. The extra parameter contains a pointer to a HeapBufferInfoReply struct. The extra parameter contains a pointer to a HeapBufferInfoReply struct. BIOS open failed. OSE_HEAP_EHUNT_HEAPD_FAI 0x820001 LED OSE_HEAP_EBIOS_OPEN_FAIL ED 0x820002 OSE_HEAP_EUNKNOWN_SIGNA 0x820003 L OSE_HEAP_EUNKNOWN_FCOD E 0x820004 186 Id:0900d805806444bc DN0479352 Issue 4-2 . lower 8 bits is the errno value. Function library could not open a heap BIOS module. lower 8 bits is the errno value. The BIOS error code is stored in the status field of the struct.

Heap extension not available (heap daemon too old). but without file and line information). Start hook 2 heap_init_flib not called. The extra parameter is a pointer to a HeapBufferInfoReply struct with additional information about the buffer. Tried to operate on a buffer that is not owned. req_size is the size required. 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. and act_size is the minimum size required (with the internal overhead. Tried to allocate too large a buffer. Tried to operate on a buffer whose endmark is overwritten. OSE_HEAP_ENO_HEAP_INIT_FL 0x820006 IB OSE_HEAP_EFREED_BUFFER_ OVERWRITTEN 0x820007 OSE_HEAP_ESIZE_TOO_LARGE 0x820100 OSE_HEAP_EPTR_INVALID 0x820101 OSE_HEAP_EBUFFER_FREE 0x820102 OSE_HEAP_EPROCESS_NOT_O WNER 0x820103 OSE_HEAP_EENDMARK_OVER WRITTEN 0x820104 OSE_HEAP_EHEAP_EXHAUSTE D 0x820105 OSE_HEAP_ENO_EXTEND_HEA P 0x820106 DN0479352 Issue 4-2 Id:0900d805806444bc 187 . The extra parameter is a pointer to a HeapBufferInfoReply struct. The extra parameter is a pointer to a HeapBufferInfoReply struct. Extra parameter is a pointer to a HeapBufferInfoReply struct with additional information about the buffer. Tried to free an invalid pointer. The extra parameter is a pointer to a HeapBufferInfoReply struct with additional information about the buffer. Tried to operate on free buffer. The pointer is stored in the address field.PCU2 Service Terminal Commands Service terminal commands Error code name OSE_HEAP_EINIT_HEAP_FAILE D Value 0x820005 Description Failed to initialise the heap. Heap is exhausted and could not be properly extended. The extra parameter is a pointer to a HeapBufferInfoReply struct. but without file and line information) to extend the heap. reply not received from the heap daemon. and act_size is the minimum size required (with the internal overhead. req_size is the size required.

resetTmo() called after reception of a time-out signal. Error code description for Time Out Server Error code name OSE_TOSV_EBIOS_INSTALL_FA ILED OSE_TOSV_EBIOS_OPEN_FAIL ED OSE_TOSV_EBIOS_CALL_FAILE D Value 0x8A0000 Description Server could not install a TOSV module. A BIOS call failed. The extra parameter contains the error code. dcUartError called in serprintf. The extra parameter contains the error code. The extra parameter contains the unknown function code. Time-out server process 'ose_tosv' could not be found. Server received an unknown signal. Trap interface function library could not open a RTC module. The extra parameter contains a pointer to the unknown signal. Device initialisation failed. The extra parameter contains the BIOS error code.Service terminal commands PCU2 Service Terminal Commands Error code description for Board Support Package Error code name OSE_BSP_EBIOSINSTALL_FAIL ED OSE_BSP_EBIOSOPEN_FAILED OSE_BSP_EDEVICE_INIT_FAILE D OSE_BSP_EBIOSCALL_FAILED OSE_BSP_SERPRINTF_EUART Value 0x880000 0x880001 0x880002 0x880003 0x880010 Description BIOS install failed. BIOS open failed. The extra parameter contains a pointer to the unknown signal. Server received an unknown BIOS function code. 0x8A0001 0x8A0002 OSE_TOSV_EUNKNOWN_SIGNA 0x8A0003 L OSE_TOSV_EHUNT_OSE_TOSV _FAILED OSE_TOSV_ERESET_TOO_LAT E 0x8A0004 0x8A0005 Error code description for RealTime Clock Error code name OSE_RTC_EBIOS_INSTALL_FAI LED OSE_RTC_EBIOS_OPEN_FAILE D OSE_RTC_EUNKNOWN_SIGNAL Value 0x8B0000 Description Server could not install a trap handler. 0x8B0001 0x8B0002 OSE_RTC_EUNKNOWN_FCODE 0x8B0003 188 Id:0900d805806444bc DN0479352 Issue 4-2 . BIOS call TOSV returned an error. TOSV function library could not open a TOSV module. Time-out server received an unknown signal.

The extra parameter is not used. Real Time server process 'ose_rtc' could not be found. The extra parameter contains a pointer to the signal. The name server found an internal error. 0x8B0007 Error code description for Name Server Error code name OSENS_NOT_IMPLEMENTED_E RR Value 0x808d0000 Description Tried to use something not currently implemented. This is a fatal error.0.0. OSENS_INTERNAL_ERR OSENS_ILLEGAL_SID_ERR 0x808d0001 0x008d0002 OSENS_TAG_TOO_LONG_ERR 0x008d0003 OSENS_LNH_NAME_TOO_LON G_ERR 0x008d0004 Error code description for PostMortemDump Error code name OSE_PMD_EBIOS_INSTALL_FAI LED Value 0x8E0000 Description The PMD module could not be installed.0. The PMD function library could not open the PMD module. An illegal subscription identifier (sid) was presented to the name server. The extra parameter contains a pointer to an information string. The extra parameter contains the expire time.3. The 254-character limitation was removed in version P1.0. This is a fatal error. It is safe to continue to run after this error. The extra parameter holds the illegal subscription identifier.PCU2 Service Terminal Commands Service terminal commands Error code name OSE_RTC_EASCTIME_INVALID_ TM OSE_RTC_EHUNT_OSE_RTC_F AILED OSE_RTC_EHISTORIC_PERIODI C_ALARM OSE_RTC_EWILD_ALARM_ID Value 0x8B0004 0x8B0005 0x8B0006 Description asctime/asctime_r called with an invalid struct tm parameter. A historic periodic alarm was created. Calling rtc_cancel_alarm() with a wild alarm identifier. This error is no longer valid. The 254-character limitation was removed in version P1. The extra parameter contains the error code returned from biosInstall().3 This error is no longer valid. This is a fatal error. OSE_PMD_EBIOS_OPEN_FAILE D 0x8E0001 DN0479352 Issue 4-2 Id:0900d805806444bc 189 . This is a fatal error.

OSE_PMD_EUNKNOWN_BIOS_ CALL 0x8E0003 OSE_PMD_EKERNEL_UNAVAIL ABLE OSE_PMD_EBAD_PMD_AREA_C ONFIGURATION 0x8E0004 0x8E0005 OSE_PMD_EPMD_CONFIGURAT ION_DENIED 0x8E0006 OSE_PMD_EWORK_AREA_TOO _SMALL 0x8E0007 Error code description for EFS Common Error code name OSE_EFS_EREGISTER_FAILED Value 0x900000 Description Failure to register an EFS object to FSS. An unknown BIOS call was presented to the PMD module. is sufficient. The memory dedicated as PMD work area is not sufficient. This is a fatal error.h for more details about PMD area configuration. This error often occurs as a recursive error. Normally the default and minimum requirement.con. The extra parameter is not used. 64K. The extra parameter contains the offending process identifier. This is a fatal error. See pmd.Service terminal commands PCU2 Service Terminal Commands Error code name OSE_PMD_EBIOS_CALL_FAILE D Value 0x8E0002 Description A BIOS call in the PMD module returned an error. The extra parameter contains the error code returned from the BIOS call.h for more details about PMD area configuration. This is a fatal error. The work area is configured with the item WORK_AREA_SIZE (<size>) in pmd.h for more details about PMD area configuration. This is a fatal error. 190 Id:0900d805806444bc DN0479352 Issue 4-2 . the work area may need to be increased. See pmd. A bad configuration of the PMD area was detected. This is a fatal error. Increasing the current value by doubling it should be enough. but in a system where a large number of pool fragments (more than 50) or programs is used. PMD could not 'attach' to the kernel data structures. See pmd. The extra parameter contains the error code returned from the BIOS call. The extra parameter contains the offending parameter value. A process does not have supervisor mode right to configure the PMD area or its list of memory areas. The extra parameter contains the current work area size. since the dump functions are usually called from within an error handler. This is a fatal error.

Hunt for ose_fss not successful. Environment variable EFS_TMPDIR not set when calling tmpnam() or tmpfile(). but no file descriptor 2 open. Trying to write after read with no intervening fflush/fseek and so forth. This process must be a stopped. Hunt for ose_partman not successful. The extra parameter is the pid of the invalid process. Referencing stderr. The extra parameter is the invalid FILE pointer.PCU2 Service Terminal Commands Service terminal commands Error code name OSE_EFS_EUNKNOWN_SIGNAL Value 0x900001 Description EFS object received an unknown signal. Trying to read after write with no intervening fflush/fseek and so forth. The extra parameter is the relevant FILE pointer. and the signal will be freed and the execution continued. but no file descriptor 0 open. Ignore the error. The extra parameter is the invalid DIR pointer. and the process will continue trying. Ignore the error. Invalid process to receive cloned state. prioritised. but no file descriptor 1 open. or background process. 0x910001 OSE_EFS_FLIB_EINVALID_FILE 0x910002 OSE_EFS_FLIB_EINVALID_DIR 0x910003 OSE_EFS_FLIB_EWRITE_AFTER 0x910004 _READ OSE_EFS_FLIB_EREAD_AFTER _WRITE 0x910005 OSE_EFS_FLIB_ENO_STDIN OSE_EFS_FLIB_ENO_STDOUT OSE_EFS_FLIB_ENO_STDERR OSE_EFS_FLIB_EENV_TMPDIR_ NOT_SET 0x910006 0x910007 0x910008 0x910009 DN0479352 Issue 4-2 Id:0900d805806444bc 191 . An invalid FILE specified. OSE_EFS_EHUNT_FSS_TIMEOU 0x900002 T OSE_EFS_EHUNT_PARTMAN_F AILED 0x900003 Error code description for EFS Function Library Error code name OSE_EFS_FLIB_ESHARE_TOO_ LATE OSE_EFS_FLIB_EINVALID_CLO NE Value 0x910000 Description efs_segment_share() called too late (after any other FLIB call) by process. An invalid DIR specified. Referencing stdout. The address to the corresponding signal structure is in the extra parameter. The extra parameter is the relevant FILE pointer. It must be set on the process or block that calls these functions. Referencing stdin.

OSE_EFS_FLIB_EINVALID_UNG ETC 0x91000B OSE_EFS_FLIB_EINVALID_SHA RE OSE_EFS_FLIB_EFD_NOT_SOC KET OSE_EFS_FLIB_EFD_NOT_FILE 0x91000C 0x91000D 0x91000E OSE_EFS_FLIB_EUNRESOLVED _INET_FUNCTION OSE_EFS_FLIB_EINVALID_PEE KC 0x91000F 0x910010 Error code description for EFS serdd Error code name OSE_EFS_SERDD_ENO_DEVIC E OSE_EFS_SERDD_EUNIT_BUSY OSE_EFS_SERDD_ESETCONF_ FAILED OSE_EFS_SERDD_EUNEXPECT ED_ERROR Value 0x920000 0x920001 0x920002 0x920003 Description serdd could not open the specified device or it was not a serial device. serdd got an unexpected device driver error. The extra parameter is the relevant FILE pointer. Calling ungetc() for a file not in read mode or before any characters have been read. The extra parameter contains the name of the process hunted for. The extra parameter is the file descriptor. Unit could not be configured according to specification. missing INET library when linking. The extra parameter is the invalid descriptor. Unresolved weak reference to INET function. The extra parameter is the relevant FILE pointer. Calling efs_peekc() for a file not in read mode or not buffered. in other words. The extra parameter is the invalid descriptor. Attempted socket operation on nonsocket descriptor. The extra parameter is the invalid bid. Unit could not be opened. Error code description for OSE EFS Shell Error code name OSE_EFS_SHELL_EHUNT_FAIL ED Value 0x930000 Description Hunt failed. An invalid block to be put into shared mode. Attempted file operation on non-file descriptor.Service terminal commands PCU2 Service Terminal Commands Error code name OSE_EFS_FLIB_ECLOSE_FD_IN _USE Value 0x91000A Description Closing a file descriptor that is in use by some other process. 192 Id:0900d805806444bc DN0479352 Issue 4-2 .

The extra parameter contains a pointer to the name that did not resolve. The extra parameter contains the extended error code. In start_efs. The extra parameter contains the extended error code. If the error handler returns. The extra parameter contains the exended error code. start_efs could not mount ram disk (/ram). the ose_dbgserver process will be stopped. 0x940001 OSE_EFS_STARTEFS_EMOUNT _DISK_FAILED OSE_EFS_STARTEFS_EFORMA T_DISK_FAILED OSE_EFS_STARTEFS_ECHDIR_ DISK_FAILED 0x940002 0x940003 0x940004 OSE_EFS_STARTEFS_ERESOL VE_FAILED 0x940005 OSE_EFS_STARTEFS_DEL_KEY _MAPPING_FAILED 0x940006 Error code description for DebugServer for Illuminator Error code name OSE_DBGS_ESOCKET_OPERAT ION Value 0xA00000 Description A socket operation failed.PCU2 Service Terminal Commands Service terminal commands Error code description for EFS startefs. 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. the 16 LSB is the errno value from the failed socket call and the 16 MSB is the line number for the error call. This error may indicate that there is some sort of a configuration error. OSE_DBGS_EFAILED_TO_GET_ IP 0xA00002 DN0479352 Issue 4-2 Id:0900d805806444bc 193 . the call to efs_examine_term or efs_config_term failed. The extra parameter contains the extended error code. The extra parameter contains the extended error code. Failed to get the target's IP address. In the extra parameter. start_efs could not properly open serial terminal (/tty) as stdio. The error is fatal for the ose_dbgserver process. If the error handler returns. start_efs could not resolve a name with the FSS.c Error code name OSE_EFS_STARTEFS_EMOUNT _TTY_FAILED OSE_EFS_STARTEFS_EOPEN_ TTY_FAILED Value 0x940000 Description start_efs could not mount serial terminal (/tty). start_efs could not change the current directory to the ram disk (/ram). start_efs could not format ram disk (/ram). The error is fatal for the ose_dbgserver process. the ose_dbgserver process will be stopped.

OSE_DBGS_EFAILED_TO_CREA TE_SOCKET 0xA00004 OSE_DBGS_ETOO_LONG_IF_N AME 0xA00005 OSE_DBGS_ETOO_LARGE_PAC KET 0xA00006 OSE_DBGS_EIF_ERROR 0xA00007 OSE_DBGS_ELOST_INET 0xA00008 194 Id:0900d805806444bc DN0479352 Issue 4-2 . The extra parameter contains the errno value from the failed socket call. The error is fatal for the ose_dbgserver process. The ose_dbgserver process will use the default interface name. the current client will be disconnected. The extra parameter contains the maximum length that can be used. The error is fatal for the ose_dbgserver process. the ose_dbgserver process will be stopped. The extra parameter contains the packet size for the failing packet. If the error handler returns. If the error handler returns. The error is fatal for the ose_dbgserver process. Failed to create a new socket. the ose_dbgserver process will be stopped. The extra parameter contains the errno value from the failed socket call. The specified interface name is too long. The extra parameter is not used. The error is fatal for the ose_dbgserver process. The error is not fatal. An unexpected interface error from OSE INET. The ose_dbgserver process received a packet on TCP which was larger than the ose_dbgserver could handle. the ose_dbgserver process will be stopped. ose_dbgerver will throw the packet away. the ose_dbgserver process will be stopped. If the error handler returns. If the error handler returns. Lost the connection to the OSE INET. If the error handler returns. The extra parameter contains the interface status received from OSE INET. The error is not fatal.Service terminal commands PCU2 Service Terminal Commands Error code name OSE_DBGS_EFAILED_TO_SET_ NON_BLOCKING Value 0xA00003 Description Failed to set a socket in nonblocking mode.

The error is not fatal. The ose_dbgserver will sleep and retry to connect. The dbserver received an unknown signal. OSE_DBGS_EILLEGAL_LDM_VE RSION 0xA0000A OSE_DBGS_EILLEGAL_LDM_EN DIAN 0xA0000B OSE_DBGS_ELDM_CONNECTIO N_REFUSED 0xA0000C OSE_DBGS_ELDM_ERROR 0xA0000D OSE_DBGS_EINVALID_HUNT_P ATH 0xA0000E OSE_DBGS_EUNKNOWN_SIGN AL 0xA0000F DN0479352 Issue 4-2 Id:0900d805806444bc 195 . for example. The extra parameter contains the interface version number of the LDM. The extra parameter contains a pointer to the faulty environment variable value string. The extra parameter is not used. The extra parameter is not used. This could be because the LDM is already connected to someone or some interface mismatch. The error is fatal for the dbgserver processes. The OSE_LDM_HUNT_PATH environment variable must end with 'ose_ldm/'. Incorrect version of the LDM. The error is fatal for the ose_dbgserver process. The LDM reported an error to the dbgserver process. The extra parameter contains a pointer to the hunt path used (located in the pool or text segment of the ose_dbgserver process). The error is not fatal for the dbgserver. The error is fatal for the dbgserver process. The error is not fatal. You should upgrade your kernel or the ose_dbgserver. The ose_dbgserver process will continue to wait and report the error every 10 seconds until the LDM is found.PCU2 Service Terminal Commands Service terminal commands Error code name OSE_DBGS_ELDM_NOT_FOUN D Value 0xA00009 Description The LDM was not found within the default time-out (10s). The extra parameter contains the signal pointer (in the address space of the dbgserver). The extra parameter contains the error code from the LDM. The LDM uses incorrect endian. Incorrect LDM hunt path configuration. The error is fatal for the ose_dbgserver. Connection refused by the LDM. 'remote_target/ose_ldm/'.

The function library could not open the PTHREAD BIOS module. OSE_PTH_EBIOS_INSTALL_FAIL 0xC10001 ED OSE_PTH_NOPTHREAD 0xC10003 OSE_PTH_EUNKNOWN_FCODE 0xC10004 OSE_PTH_EBIOS_OPEN_FAILE D OSE_PTH_EBIOS_CALL_FAILED 0xC10005 0xC10006 Error code description for OSE NTP/SNTP Error code name Value Description The clock was mixed up. This error must be reported to OSE Systems. OSE_NTP_ERROR_CLOCK_TOO 0x00C30000 _SCREWED_UP OSE_NTP_ERROR_SOCKET_SE TUP_FAILURE 0x00C30001 OSE_NTP_ERROR_NO_NAME_S 0x00C30002 ERVER OSE_NTP_ERROR_SERVICE_N OT_REGISTERED 0x00C30003 196 Id:0900d805806444bc DN0479352 Issue 4-2 . The extra parameter contains the handle used in the call. OSE name server hunt failed. OSE NTP/SNTP failed to set up its socket. The extra parameter contains the unknown function code.Service terminal commands PCU2 Service Terminal Commands Error code description for Pthreads Error code name OSE_PTH_INTERNAL Value 0xC10000 Description An internal error that should not occur. The extra parameter contains the BIOS error code. A BIOS call failed. The OSE NTP/SNTP service was not registered by the OSE name server. You have probably not installed the start hook initPthreads. Could not install the trap handler. pthread function failed because the PID in the extra parameter did not refer to a pthread. The NTP does not try to correct it. The server received an unknown BIOS function code.

Sign up to vote on this title
UsefulNot useful