73.30. How to trace the internal events for debugging purposes
Prev Chapter 73. HowTo - Management Next

73.30. How to trace the internal events for debugging purposes

Enter into the Abilis control-program with a Terminal Emulator with file transfer support (e.g. Windows HyperTerminal, Zoc, etc), and type the following commands.

d pstackIdentify the internal port number associated to the resource for which you want to activate the trace. (e.g. suppose the Eth-1 resource).
trace act po:24 data:1600Activate the trace function.
trace startStart saving the events.
trace stopStop tracing the events.
trace get zDownload the trace from Abilis.
[Warning]Warning

Verify parameters settings of the internal events trace using the command trace param. If a trace is running the following message is shown:

[14:04:34] ABILIS_CPX:trace act po:19,18 data:1600

TRACE RUNNING

The trace continues to be active on ports shown by trace param command and not on those specified by trace act command.

[14:04:50] ABILIS_CPX:trace param

        Configured Value       Active Value           Description
------------------------------------------------------------------------------
PO:     024,019                024,019                Ports to be traced
SIZE:   8192 (Kbytes)          8192 (Kbytes)          Tracer buffer size
DATA:   1600 (bytes)           1600 (bytes)           Max. event buffer size
CMD:    STD                    STD                    Command(s) to be traced
LSN:    ALL                    ALL                    SD/RV lsn to be traced
TYPE:   ALL                    ALL                    SD/RV type to be traced
STATE:  -                      RUNNING                Current Tracer state
TSAVE:  NO                     NO                     Automatic trace saving
EVENTS: -                      49929                  Number of events
SNDRCV: -                      24943                  Number of send & receive
LENGTH: -                      8191 (Kbytes)          Current trace length

Stop the trace and set it inactive:

[14:13:42] ABILIS_CPX:trace stop

COMMAND EXECUTED 

[14:15:14] LUIGI_DEMURO:trace inact

COMMAND EXECUTED

Configure the trace and follow the steps of the how to:

[14:17:40] ABILIS_CPX:trace act po:24,18 data:1600

COMMAND EXECUTED 

[14:17:48] ABILIS_CPX:trace param                 

        Configured Value       Active Value           Description
------------------------------------------------------------------------------
PO:     024,019                024,018                Ports to be traced
SIZE:   8192 (Kbytes)          8192 (Kbytes)          Tracer buffer size
DATA:   1600 (bytes)           1600 (bytes)           Max. event buffer size
CMD:    STD                    STD                    Command(s) to be traced
LSN:    ALL                    ALL                    SD/RV lsn to be traced
TYPE:   ALL                    ALL                    SD/RV type to be traced
STATE:  -                      ACTIVE/READY           Current Tracer state
TSAVE:  NO                     NO                     Automatic trace saving
EVENTS: -                      0                      Number of events
SNDRCV: -                      0                      Number of send & receive
LENGTH: -                      0 (Kbytes)             Current trace length

For example, if you use Zoc program:

Abilis CPX traces are saved in a proprietary format “cpx”. Follow these instructions to convert them in other formats (PCAP, I4B, etc).

73.30.1. How to trace only the SIP signaling traffic

Enter into the Abilis control-program with a Terminal Emulator with file transfer support (e.g. Windows HyperTerminal, Zoc, etc), and type the following commands.

d pstack res:udpIdentify the internal port number associated to the resource UDP for which you want to activate the trace.
d d udp locport:5060Identify the Lsn to be traced.
trace act po:11 lsn:0013 data:1600Activate the trace function.
trace startStart saving the events.
trace stopStop tracing the events.
trace get zDownload the trace from Abilis.

Example:

[10:44:37] ABILIS_CPX:d pstack res:udp

+------------+---------------+------------------------------------------------+
|  Resource  |    Act/Run    | Port(s)                                        |
+------------+---------------+------------------------------------------------+
| Udp        | Act/Run       | 11(Udp)                                        |
+------------+---------------+------------------------------------------------+

[10:48:11] ABILIS_CPX:d d udp locport:5060

RES:Udp -----------------------------------------------------------------------
       User_Datagram_Protocol                                                  
       ------------------------------------------------------------------------
       ID    Lsn           LocPort     Resource
       ------------------------------------------------------------------------
       18    0013 (   19)  5060        CtiSip
[Warning]Warning

Verify parameters settings of the internal events trace using the command trace param. If a trace is running the following message is shown:

[14:04:34] ABILIS_CPX:trace act po:11 lsn:0013 data:1600

TRACE RUNNING

The trace continues to be active on ports shown by trace param command and not on those specified by trace act command.

[14:04:50] ABILIS_CPX:trace param

        Configured Value       Active Value           Description
------------------------------------------------------------------------------
PO:     024,019                024,019                Ports to be traced
SIZE:   8192 (Kbytes)          8192 (Kbytes)          Tracer buffer size
DATA:   1600 (bytes)           1600 (bytes)           Max. event buffer size
CMD:    STD                    STD                    Command(s) to be traced
LSN:    ALL                    ALL                    SD/RV lsn to be traced
TYPE:   ALL                    ALL                    SD/RV type to be traced
STATE:  -                      RUNNING                Current Tracer state
TSAVE:  NO                     NO                     Automatic trace saving
EVENTS: -                      49929                  Number of events
SNDRCV: -                      24943                  Number of send & receive
LENGTH: -                      8191 (Kbytes)          Current trace length

Stop the trace and set it inactive:

[14:13:42] ABILIS_CPX:trace stop

COMMAND EXECUTED 

[14:15:14] LUIGI_DEMURO:trace inact

COMMAND EXECUTED

Configure the trace and follow the steps of the how to:

[14:17:40] ABILIS_CPX:trace act po:11 lsn:0013 data:1600

COMMAND EXECUTED 

[10:59:48] ABILIS_CPX:trace start

COMMAND EXECUTED
WARNING: THE AUTOMATIC TRACE SAVING IS ACTIVE

[10:59:52] ABILIS_CPX:trace param

        Configured Value       Active Value           Description
-------------------------------------------------------------------------------
PO:     011                    011                    Ports to be traced
SIZE:   8192 (Kibyte)          3651 (Kibyte)          Tracer buffer size
DATA:   200  (bytes)           1600 (bytes)           Max. event buffer size
CMD:    STD                    STD                    Command(s) to be traced
LSN:    0018                   0013                   SD/RV lsn to be traced
TYPE:   ALL                    ALL                    SD/RV type to be traced
STATE:  -                      RUNNING                Current Tracer state
tact:   YES                    YES                    Trace activation at boot
TSAVE:  YES                    YES                    Automatic trace saving
EVENTS: -                      43                     Number of events
SNDRCV: -                      21                     Number of send & receive
LENGTH: -                      17 (Kibyte)            Current trace length

[11:01:03] ABILIS_CPX:trace stop

COMMAND EXECUTED

Download the trace from Abilis. For example, if you use Zoc program:

Abilis CPX traces are saved in a proprietary format “cpx”. Follow these instructions to convert them in other formats (PCAP, I4B, etc).

73.30.2. How to convert Abilis CPX traces

Go to http://support.abilis.net/downloads/cpx2k/download.html and click the System and tools link of the firmware Release that you want to use; in the following page, download download a “Trace Converter” program (trcmgrw.exe).

For example, the “GUI CPX trace converter” (trcmgrw.exe) converts Abilis CPX traces into:

  • “TAB separated”: is a general purpose format usable to import data into Libreoffice or Openoffice or Excel spreadsheets.

  • PCAP: is used by Wireshark/Tcpdump for Ethernet/PPP/RawIP representation.

  • I4B: it's a format for ISDN layer 1 representation and it can be loaded by Wireshark.

  • VN: Visual Network format; it's used for PPP traces with DTE/DCE direction indication and can be loaded by Wireshark.

For example, if you want to convert the trace in PCAP format, follow these instructions.

  1. Double click the trcmgrw.exe file: the following window will appear.

  2. In the To PCAP tab, select the in the Source file name field the trace that must be converted and in the Target file name field the name of the new trace.

  3. Click the OK button: in the next window selects the port traced and the format.

    [Tip]Tip

    If the traced port is associated with the resource UDP (e.g. Section 73.30.1, “How to trace only the SIP signaling traffic”), then is needed to select the format "Internal-UDP".

  4. Click the OK button: the result of the conversion is shown.

  5. Click the OK button to close the window and then the Exit button to close the program.

For example, if you want to convert the trace in I4B format, follow these instructions.

  1. Double click the trcmgrw.exe file: the following window will appear.

  2. In the To I4B tab, select the in the Source file name field the trace that must be converted and in the Target file name field the name of the new trace.

  3. Select the port and the format, and click the OK button.

    [Tip]Tip

    The selected port 10031 it's for CTIP:31. (Selected port =100+CTIP Number)

  4. Click the OK button: the result of the conversion is shown.

  5. Click the OK button to close the window and then the Exit button to close the program.

Prev Up Next
73.29. How to configure Abilis as a SYSLOG client Home 73.31. How to prevent brute force attacks