SVI-STP SSME
Squire Technologies - Confidential Document
Page
49
of
57
8
Debug
8.1
Description
From version 15.8.0 onwards of the svi-stp process, it is now possible to only print debug for specific
messages which are received by the STP-SSME-XML engine. The debug profile to use is set on the
Linkset element.
The message match is done using the MTPMatch or SCCPMatch elements. Any message which is
matched for debug will be written to a separate PCAP file from the mtp3/m3ua/sua layer and above.
8.2
Debug Levels
To enable the XML debug for specific messages, no debug Task or Discriminator needs to be set in the
SVI-MS GUI.
To print the full XML debug, configure the ssmedebug attribute on the XML resource to be ‘All’. This
will print out more detailed debug which will show each match the STP-SSME-XML engine tries.
To print the summary debug, deselect all options on the ssmdebug attribute on the XML resource.
This will only print out the lines which were matched and selected.
8.3
Debug PCAP Configuration
In the SVI, under Configuration -> Resources -> Debug, the following configuration options are
available.
To enable the PCAP file set STP Pcap Options to Routed.
8.4
XML Configuration
To enable debug for a Linkset element, you use the debug attribute. This then points to a
LinksetProfile for the debug which in turn points to an Ep which contains MTPMatch or SCCPMatch
elements. If any match is found in this EP then the debug will be printed to the log files and the
message written to the pcap as configured in section 8.3.
<Linkset linkset="
LS-ETSI-OPC-8000-DPC-7000
" profile="
MtpRouting0-etsi-opc8000-dpc-7000
"
debug="
etsi-debug
"/>
<LinksetProfile name="
etsi-debug
">
<LsEp entryPoint="
TestDebug
"/>
</LinksetProfile>
<Ep id="
TestDebug
" name="
TestDebug
">
<SCCPMatch id="
TestDebug-1
" cdpn.digits="
9
"/>
</Ep>