trace

Handling trace functionality.

Format

• -lim N -unit NAME|
• -lim N -unit NAME -signo S [-byte x-X,y-Y..z-Z]|
• -lim N -unit NAME -signam NAME [-byte x-X,y-Y..z-Z]|
• -dir DIRNO |
• -equ x-y-zz-a |
• -bpos x-y-zz [-mask aaaa] |
• -mgw x [-mask aaaa] |
• -modify T -rotate on/off |
• -modify T {-sortin {off|1,2..20}|-sortout {off|1,2..20}}|
• -modify T -info "txt"|
• -modify T -size S |
• -modify T -fcode N [-flim X -funit Y [-fsig Z]]|
• -modify T {-ssigno N|-ssignam NAM } -sunit Y|
• -modify T -sendalarm A|
• -modify T -textlevel N|
• -start 1,2..15 |
• -stop 1,2..15 |
• -print T [-lim N] [-signo S] [-show T] [-from X] [-to Y] [-fromtime time] [-totime time] [-nodecode]|
• -attach T -lim N [-signo S] [-show T][-nodecode]|
• -clear 0,1..15 |
• -display [0,1..15] [-lim N]|
• -remove T

Function

Trace can be initiated in different ways. Trace on the unit, trace on signal sequence, or trace on directory number. To start a trace, the first command shall contain a directory number or a lim and unit number; it may have additional parameters; the printout returned shows the tri number assigned to your trace session. A unit trace is started if only lim and unit parameters are stated.

A sequence trace is started if the message number is added to lim and unit. If a directory number or equ is used, a sequence trace is started for the next call. Tracing on mgw or bpos starts tracing on the hw position (wilma trace). Each signal is printed two times if the equipment position is initiated. On signals to hw, the sw format is printed first, and on signals from hw, the hw format is printed first. If hw is not assigned to signals from hw, only the first format is printed as the signal is not forwarded anywhere.

Note:

• The "trace -print 0" prints the diagnostic history log.
• In most parameters, different notations for input can be used.
• Decadic notation starts with a digit, octal with "0" and hexadecimal values with "0x" "trace -attach X" prints data as signals arrive from the traced object. This can create LOTS of signals in the system, so be careful when selecting targets.
• Attaching or printing when the trace is started on LOGGER should not be done as it will give circular printouts, that is, the printout will start to print the print signals.
• Due to signaling restrictions, trace-attach on all lims is only allowed for the history log. The user should log on to the attached lim if attaching any other trace individually.
• Trace "all" can be cleared, stopped, and restarted by using service codes, such as SC-190 to clear, SC-191 to stop, and SC-192 to restart.

Parameters

• -attach

  The stated tri is prints in "real" time.

  Attach of 0 prints the history log.

  Attach is done on a started trace.

• -bpos

  The HW signaling position to trace on.

  Position entered as mgw-mag-32 group of equ.

  HW signaling to and from boards.

• -byte

  Data in signal requires byte x with value x to start sequence.

  Five possible values can be stated.

• -clear

  The stored messages in the stated tri(s) are removed.

  "all" removes tri 1 to 15.

  "full" removes tri 0 to 15.

• -dir

  Directory number of a subscriber where a signal sequence trace is started.

• -display

  Print trace setup for the stated tri.

• -equ

  Equipment position of a device where a signal sequence trace is started.

  mgw-mag-bpos-ind

• -fcode

  Stop on the trace if this fault is found in a lost signal. Values: 0-45, "all", and "off".

• -flim

  The lim where a lost signal is received to stop a trace. Values: Integer or all.

• -from

  The sequence number in the trace from where the print starts.

• -fromtime

  The Date and Time from where the print starts.

• -fsig

  Stop on the trace if this signal is lost in the stated lim and unit. Values: 1-65535 and "all". The default value is "all".

• -funit

  The unit where a lost signal is received to stop a trace.

• -info

  Free text to inform why a trace is started (70 characters).

• -lim

  Lim the number where the trace is initiated. Unit trace can be made on "all".

• -mask

  Specifies what equipment positions within a 32-group should be included in the trace.

• -mgw

  The hardware signaling position to trace on. Position entered as mgw will trace on internal switch signals to fictive multiple numbers on LSU/DSU.

• -modify

  The stated tri is modified regarding sorting and rotation. "all" modifies tri 1 to 15.

• -nodecode

  Do not print signal data in the decoded (human-readable) form.

• -print

  The stated tri is printed.

  Print of 0 is printing the history log.

  Print can also be done on a started trace.

• -remove

  The stated tri is removed. The value "all" removes the trace individuals 1 to 15 (not number 0).

• -rotate

  States if the trace stops when the buffer is full or overwrites the first entries.

• -sendalarm

  Send alarm when trace hits stop by fault, servicecode or trigsignal. Alarm 1:51 (Trace stopped.) is used to inform the user. yes, no, or empty data. An empty value is considered as “yes”.

• -show

  What type of information is printed out of the signals. Values: full(f), small(s), head(h), compact(c), or a digit(*).

• -signam

  Message name that starts a sequence trace when entering the stated lim and unit.

• -signo

  Message number that starts a sequence trace, when entering in the stated lim and unit.

• -size

  The number of trace messages that can be stored (1 to 100,000). Values over 10,000 displays a warning.

• -sortin

  Signal numbers that shall be stored. The value "off" clears the list.

• -sortout

  Signal numbers that are not stored. The value "off" clears the list.

• -ssignam

  Stop on the trace if this signal name is received in the stated unit.

• -ssigno

  Stop on the trace if this signal number is received in the stated unit. Values: signal number or "off".

• -start

  The stated tri(s) are started. The value "all" starts tri from 1 to 15.

• -stop

  The stated tri(s) are stopped. The value "all" stops the tri from 1 to 15.

• -sunit

  Stops the trace if a stated signal is received in this unit.

• -textlevel

  Indicates what text information types should be collected in the trace.

  Values: all(a)=0xff, basic(b)=0x01, extra(e)=0x03, normal(n)=0x8b, verbose(v)=0x9b, network(wire/w)=0x80 or a digit(*) bit0=basic, bit1=extended, bit2=events, bit3=state, bit4=diagnose, bit5=verbose, bit6=barf, and bit7=network.

  Default is normal(n) = 0x8b

• -to

  The sequence number is traced to where the print continous.

• -totime

  Date and time where the print stops.

• -unit

  Unit name (PU-name) from where the trace starts.

Examples

• DIRECTORY TRACE

  example% trace -dir 2000

• UNIT TRACE

  example% trace -lim 66 -unit CMP

• SEQUENCE TRACE

  example% trace -lim 1 -unit CMP -signo 33

• NETWORK (WIRE) TRACE

  example% trace -lim all -unit SIPLP trace -modify 1 -textlevel network -sortin 0

• START TRACE

  example% trace -start 2

• STOP TRACE

  example% trace -stop 2

• PRINT TRACE

  example% trace -print 2

• PRINT TRACE WITH FROMTIME PARAMETER SPECIFIED

  example% trace -print 2 -fromtime "2013-07-01 12:45:00 (CEST)"

• REMOVE TRACE

  example% trace -remove 2

• Example 1: Problems with scanning of boards
  Trace on DCP.

  MDSH> trace -lim 1 -unit DCP Trace Individual = 1 ready

  MDSH> trace -start 1 Trace Individual = started MDSH>

  //Wait for the scanning to proceed

  MDSH> trace stop 1 Trace Individual = 1 stopped

  MDSH> trace -display 1 Trace ind: 1, State:stopped, Stored: 01, Size per lim: 500 Type: unit-trace, Rotating: off, textlevel: normal Lim no: 1, Unit no: 0029, Unit name: DCP Time mark: 2004-02-04 13:25:43 (MET), by user: mduser

  MDSH>trace -print 1 Trace ind: 1, State: stopped, Stored: 1, Size per lim: 500 Type: unit-trace, Rotating: off, textlevel: normal Lim no: 1, Unit no: 0029, Unit name: DCP Time mark: 2004-02-04 13:25:43 (MET), by user: ebchrg

  <<Sending: 1, 2004-02-04 13:25:21.712700 (MET) Message type 0x01=001 SW_HW Message head type 0x01=001 HARDWARE From 0x001d=00029 DCP LIM 0x01=001 level 0x02=002 B Trace:0x12,0x00,0 Hardware address:0x0000=00000 = 1a-0-00-00 Message 0x1884=06276@(#)(MDL)BORDID v1.0 0x000: 16 MDSH>

• Example 2: What happens in UNIT RMP before an error signal is generated

  MDSH> trace -lim 1 -unit RMP Trace Individual = 1 ready

  MDSH> trace -modify 1 -fcode all -rotate on Trace Individual = 1 modified

  MDSH> trace -start 1 Trace Individual = 1 started MDSH>

  //Wait for error signals to be generated by checking error trace individual.

  MDSH> trace -display 0 Trace ind: 1, State: started, Stored: 1, Size per lim: 500

  MDSH> trace -stop 1 Trace Individual = 1 stopped

  MDSH> trace -print 1 Trace ind: 1, State: stopped, Stored: 500, Size per lim: 500 Type: unit-trace, Rotating: on, Textlevel: normal Lim no: 1, Unit no: 0216, Unit name: RMP Time mark: 2004-02-05 15:25:43 (MET), by user: mduser

  <<Sending: 1, 2004-02-05 14:26:21.312700 (MET) . .

  MDSH>

• Example 3: A user complains that he reaches wrong number

  A simple filter to check basic signals, recording using offhook, onhook, digits, reaching destination and clearing.

  Signals filtered in order to see what is happening, are: OFFHOOK, ONHOOK, ANSWER, CLEAR, ENTBSYMESSTA, ENTCALORGSTA, ENTNOPSTA, KEYDIGREC, RELEASE.

  You can find out the numbers by doing an initial trace and then modify the trace individual later or by use the command message_number.

  Printing in short mode gives a very condensed printout.

  MDSH> trace -dir 302 Number 302 is a directory number Trace Individual = 1 ready
  MDSH> trace -modify 1 -sortin 1,2,1193,1698,2143,2144,2158,3370,3870 Trace Individual = 1 modified
  MDSH> trace -modify 1 -info "Digits are missing user claims" Trace Individual = 1 modified
  MDSH> trace -start 1 Trace Individual = 1 started MDSH>
  //Tell user to dial number on the telephone
  MDSH> trace -stop 1 Trace Individual = 1 stopped
  MDSH> trace -print 1 -show s Trace ind: 1, State: stopped, Stored: 9, Size per lim: 500 Type: directory-trace, Rotating: off, Textlevel: normal Number: 302, Lim: 1, Unit: ELP6, Pointer: 0x027f Sort in: 1 2 1193 1698 2143 2144 2158 3370 3870 Time mark: 2004-02-04 18:29:54 (MET), by user: mduser Info: Digits are missing user claims
  >>Enter: 1, 2004-02-04 18:29:26.666500 (MET)
  To 0x0065=00101 ELP6	LIM 0x01=001 level 0x01=001 A
  Hardware address:0x0070=00112 = 1a-0-32-00
  Message 0x0001=00001 @(#)(MDL) OFFHOOK v1.0
  0x000: 02 7f 00 00	...
  >>Enter: 2, 2004-02-04 18:29:28.419637 (MET)
  From 0x00ae=00174 ADP To 0x0065=00101 ELP6	LIM 0x01=001 level 0x01=001 A LIM 0x01=001 level 0x01=001 A
  Message 0x0d2a=03370 @(#)(MDL) KEYDIGREC v1.0
  0x000: 02 7f 0f 03	...
  >>Enter: 3, 2004-02-04 18:29:29.328788 (MET)
  From 0x00ae=00174 ADP To 0x0065=00101 ELP6	LIM 0x01=001 level 0x01=001 A LIM 0x01=001 level 0x01=001 A
  Message 0x0d2a=03370 @(#)(MDL) KEYDIGREC v1.0
  0x000: 02 7f 0f 03	...

  >>Enter: 4, 2004-02-04 18:29:29.625160 (MET)
  From 0x00ae=00174 ADP To 0x0065=00101 ELP6	LIM 0x01=001 level 0x01=001 A LIM 0x01=001 level 0x01=001 A
  Message 0x0d2a=03370 @(#)(MDL) KEYDIGREC v1.0
  0x000: 02 7f 0f 00	....
  >>Enter: 5, 2004-02-04 18:29:30.268531 (MET)
  From 0x00ce=00206 CMP To 0x0065=00101 ELP6	LIM 0x01=001 level 0x01=001 A LIM 0x01=001 level 0x01=001 A
  Message 0x0860=02144 @(#)(MDL) ENTCALORGSTA v1.0
  0x000: 02 7f 0f 01 00 00 01 01 01 00 ff 00 0f 00 00 00 ...............
  0x010: 00 00 10	....
  >>Enter: 6, 2004-02-04 18:29:41.667896 (MET)
  To 0x0065=00101 ELP6	LIM 0x01=001 level 0x01 =001 A
  Hardware address:0x0070=00112 = 1a-0-32-00
  Message 0x0002=00002 @(#)(MDL) ONHOOK v1.0
  0x000: 02 7f 00 00	....
  >>Enter: 7, 2004-02-04 18:29:41.673528 (MET)
  From 0x0065=00101 ELP6 To 0x00ce=00206 CMP	LIM 0x01=001 level 0x01=001 A LIM 0x01=001 level 0x01=001 A
  Message 0x06a2=01698 @(#)(MDL) CLEAR v1.0
  0x000: 05 0d 02 7f 00 65 01	....
  >>Enter: 8, 2004-02-04 18:29:41.766277 (MET)
  From 0x00ce=00206 CMP To 0x007c=00124 KLP1T	LIM 0x01=001 level 0x01=001 A LIM 0x01=001 level 0x01=001 A
  Message 0x086e=02158 @(#)(MDL) ENTNOPSTA v1.0
  0x000: 00 00 0d 0b ff ff ff 00	....
  >>Enter: 9, 2004-02-04 18:29:41.854513 (MET)
  From 0x00ce=00206 CMP To 0x0065=00101 ELP6	LIM 0x01=001 level 0x01=001 A LIM 0x01=001 level 0x01=001 A
  Message 0x0f1e=03870 @(#)(MDL) RELEASE v1.0
  0x000: 02 7f 0f	...
  MDSH>

• Example 4: What is really happening on the HW in position 1a-0-30

  Set text level filter to omit raw format of signals.

  MDSH> trace -bpos 1a-0-30 Trace Individual = 1 ready
  MDSH> trace -modify 1 -textlevel 0 Trace Individual = 1 modified
  MDSH> trace -start 1 Trace Individual = 1 started
  //Wait for a while to get the information.
  MDSH> trace -stop 1 Trace Individual = 1 stopped
  MDSH> trace -print 1 Trace ind: 1, State: stopped, Stored: 15, Size per lim: 500 Type: bpos-trace, Rotating: off, Textlevel: 0 Bpos: 001a-0-30, mask: 0xffffffff Time mark: 2004-02-04 18:12:13 (MET), by user: mduser
  >>Enter: 1, 2004-02-04 18:11:20.787349 (MET)
  Message type 0x02=002 HW_SW To 0x0065=00101 ELP6	Message head type 0x00=000 SOFTWARE LIM 0x01=001=001 A
  Trace: 0x01,0x00,0 Hardware address: 0x0070=00112 = 1a-0-32-00
  Message 0x0001=00001 @(#)(MDL) OFFHOOK v1.0
  0x000: 02 7f 00 00	....
  <<Sending: 2, 2004-02-04 18:11:20.849010 (MET)
  Message type 0x01=001 SW_HW From 0x0065=00101 ELP6	Message head type 0x01=001 HARDWARE LIM 0x01=001 A
  Trace:0x11,0x00,0 Hardware address: 0x0070=00112 = 1a-0-32-00
  Message 0x1907=06407 @(#)(MDL) PREPLSMESREQ v1.0
  0x000: 98	.
  <<Sending: 3, 2004-02-04 18:11:20.933497 (MET)
  Message type 0x01=001 SW_HW From 0x0065=00101 ELP6	Message head type 0x01=001 HARDWARE LIM 0x01=001 A
  Trace:0x11,0x00,0 Hardware address: 0x0070=00112 = 1a-0-32-00
  Message 0x189f=06303 @(#)(MDL) CODPUPEXN v1.0
  0x000: 87	.

  >>Enter: 4, 2004-02-04 18:11:27.752474 (MET)
  Message type 0x02=002 HW_SW To 0x0065=00101 ELP6	Message head type 0x00=000 SOFTWARE LIM 0x01 = 001 level 0x01=001 A
  Trace:0x01,0x00,0 hardware address:0x0070=00112 = 1a-0-32-00
  Message 0x0006=00006 @(#)(MDL) PREDIG v1.0
  0x000: 02 7f 00 00	....
  >>Enter: 5, 2004-02-04 18:11(MET)
  Message type 0x02=002 HW_SW To 0x0065=00101 ELP6	Message head type 0x00=000 SOFTWARE LIM 0x01 = 001 level 0x01=001 A
  Trace:0x01,0x00,0 hardware address:0x0070=00112 = 1a-0-32-00
  Message 0x0002=00002 @(#)(MDL) ONHOOK v1.0
  0x000: 02 7f 00 00	....
  <<Sending: 6, 2004-02-04 18:11:48.163769(MET)
  Message type 0x01=001 SW_HW From 0x001d=00029 DCP	Message head type 0x01=001 HARDWARE LIM 0x01 = 001 level 0x02=002 B
  Trace:0x11,0x00,0 Hardware address:0x0060=00096 = 1a-0-30-00
  Message 0x1884=06276 @(#)(MDL) BRDID v1.0
  0x000: 16	.
  >>Enter: 7, 2004-02-04 18:11:48.279108(MET)
  Message type 0x02=002 HW_SW To 0x007c=00124 KLP1T	Message head type 0x00=000 SOFTWARE LIM 0x01 = 001 level 0x02 =002 B
  Trace:0x01,0x00,0 Hardware address:0x0060=00096 = 1a-0-30-00
  Message 0x0016=00022 @(#)(MDL) IDENTY v1.0
  0x000: 02 7f 4d cf	..M.
  <<Sending: 8, 2004-02-04 18:11:50.290881(MET)
  Message type 0x01=001 SW_HW From 0x001d=00029 DCP	Message head type 0x01=001 HARDWARE LIM 0x01 = 001 level 0x02=002 B
  Trace:0x11,0x00,0 Hardware address:0x0070=00112 = 1a-0-32-00
  Message 0x1884=06276 @(#)(MDL) BRDID v1.0
  0x000: 16	.
  >>Enter: 9, 2004-02-04 18:11:50.411571(MET)
  Message type 0x02=002 HW_SW To 0x0065=00101 ELP6	Message head type 0x00=000 SOFTWARE LIM 0x01 = 001 level 0x02=002 B
  Trace:0x01,0x00,0 Hardware address:0x0070=00112 = 1a-0-32-00
  Message 0x0016=00022 @(#)(MDL) IDENTY v1.0
  0x000: 02 7f 57 cf	..W.

  <<Sending: 10, 2004-02-04 18:12:04.823306 (MET)
  Message type 0x01=001 SW_HW From 0x001d=00029 DCP	Message head type 0x01=001 HARDWARE LIM 0x01 = 001 level 0x02=002 B
  Trace:0x11,0x00,0 Hardware address:0x0060=00096 = 1a-0-30-00
  Message 0x1884=06276 @(#)(MDL) BRDID v1.0
  0x000: 16	.
  >>Enter: 11, 2004-02-04 18:12:04.941926 (MET)
  Message type 0x02=002 HW_SW To 0x007c=00124 KLP1T	Message head type 0x00=000 SOFTWARE LIM 0x01 = 001 level 0x02 =002 B
  Trace:0x01,0x00,0 Hardware address:0x0060=00096 = 1a-0-30-00
  Message 0x0016=00022 @(#)(MDL) IDENTY v1.0
  0x000: 02 7f 4d cf	..M.
  <<Sending: 12, 2004-02-04 18:12:06.963019 (MET)
  Message type 0x01=001 SW_HW From 0x001d=00029 DCP	Message head type 0x01=001 HARDWARE LIM 0x01 = 001 level 0x02=002 B
  Trace:0x11,0x00,0 Hardware address:0x0070=00112 = 1a-0-32-00
  Message 0x1884=06276 @(#)(MDL) BRDID v1.0
  0x000: 16	.
  >>Enter: 13, 2004-02-04 18:12:07.913270 (MET)
  Message type 0x02=002 HW_SW To 0x0065=00101 ELP6	Message head type 0x00=000 SOFTWARE LIM 0x01 = 001 level 0x02 =002 B
  Trace:0x01,0x00,0 Hardware address:0x0070=00112 = 1a-0-32-00
  Message 0x0016=00022 @(#)(MDL) IDENTY v1.0
  0x000: 02 7f 57 cf	..W.
  <<Sending: 14, 2004-02-04 18:12:09.835451 (MET)
  Message type 0x01=001 SW_HW To 0x0065=00101 ELP6	Message head type 0x01=001 HARDWARE LIM 0x01 = 001 level 0x02=002 B
  Trace:0x11,0x00,0 Hardware address:0x0070=00112 = 1a-0-32-00
  Message 0x18d2=06354 @(#)(MDL) INDSTS v1.0
  0x000: 17	.
  >>Enter: 15, 2004-02-04 18:12:09.954780 (MET)
  Message type 0x02=002 HW_SW To 0x0065=00101 ELP6	Message head type 0x00=000 SOFTWARE LIM 0x01 = 001 level 0x02 =002 B
  Trace:0x01,0x00,0 Hardware address:0x0070=00112 = 1a-0-32-00
  Message 0x0017=00023 @(#)(MDL) ISTAT v1.0
  0x000: 02 7f 00	...
  MDSH>

  Note: It is possible to see signals from all kinds of programs going to and from the bpos 1a-0-30 and 1a-0-32.The board owner send signals to the board and DCP. A possible interference could be spotted here.

• Example 5: START, STOP, AND CLEAR TRACES WITH SERVICE CODES

  Initiated traces in the system can be started, stopped, and cleared by users on advice with several service codes.

  Service codes A190B, A191B, and A192B must be initiated first in the number analysis.

  • To start all traces in the system, enter the service code A192B on a terminal.
  • To stop all traces in the system, enter the service code A191B on a terminal.
  • To clear all traces in the system, enter the service code A190B on a terminal.
  Note: In the above service codes, A stands for *, and B stands for #.