Overview
This article describes the tools available to analyze the communication traces.
Tracing Application Traffic
The HUB includes a flexible and configurable trace framework that supports the tracing of communication between:
- The HUB and applications.
- The HUB and the SMSC.
- The RTRs.
Tracing should only be performed by trained and trusted personnel, as it is an expert-level function that includes visible traffic communication.
Tracing will impact system performance.
The tracing framework consists of:
- Trace filters (created in the MGR) that allow for the conditional collection of trace data.
- The trace receiver (
tp_trace_receiver
): a command-line tool that receives trace data and writes it to a PCAP file. - The
tp_filter
: a command-line tool that shows the current trace filter configuration.
You can configure up to 10 trace filters, with 100 conditions each.
The trace filter configuration determines the tracepoints:
- The HUB outside application interface (to ESME).
- The HUB inside application interface (to SMSC).
- The HUB/RTR MXP communication.
Note: When the character set conversion function is used, trace data may be pre-character conversion or post-character conversion, depending on the specified tracepoint.
For more information about the trace receiver and its configuration file, refer to the Tools Operator Manual.
Recommended Tracing Method
Tracing should be initiated from a single point (such as the MGR), and then go on with all HUB and RTR nodes. Trace data can then be collected centrally and viewed in a tool such as Wireshark.
The recommended method to collect and analyze trace information from application traffic is:
- Run
snoop
on the HUB and collect the relevant data in a trace file. - Download the trace file on a PC workstation.
- Analyze the snoop trace using Wireshark.
This method minimizes the impact on the HUB's performance.
Presentation of Trace Data in Wireshark
The HUB trace framework rebuilds an Ethernet frame by adding TCP, IP, and Ethernet headers to the message. These headers contain CRC and sequence numbers, which are not used by the HUB. Therefore, Wireshark may display some warnings alongside the trace data. You can disable these warnings by going to Edit > Preferences and change the following protocol settings:
- IP: Disable the Validate the checksum setting (if possible).
- TCP (used to trace application/SMSC data): Disable the Validate the TCP checksum and Analyze the TCP sequence numbers settings (if possible).
- SCTP (used to trace MXP data): Apply the setting Checksum Type: None.
Trace Filter Configuration
This section describes how to configure trace filters in the MGR.
Creating Trace Filters
To create a trace filter:
- In the left navigation bar, select Tracing > Trace Filter. The Trace Filters tab appears.
- Click Add New. A new Trace Filters tab appears.
- Enter a unique name for the trace filter in the Name box (maximum 31 characters).
- Optionally, enter a description of the trace filter in the Description box.
- Add the IP address of the server into the Server IP box. The traces from this filter will be sent to the IP address of the server.
- Add the UDP port into the Server Port box. The traces from this filter will be sent to the UDP port of the server.
- Click Save. The MGR creates the filter and closes the tab.
- Configure conditions for the trace filter.
- After you have created all desired conditions, activate the trace filter.
Configuring Trace Filter Conditions
You can configure many conditions for each trace filter. To configure a trace condition:
- In the left navigation bar, select Tracing > Trace Filter. The Trace Filters tab appears.
- Click the trace filter to which you want to add a condition. The trace filter opens in a separate Trace Filters tab.
- Click Add New in the lower right corner of the Trace Filters tab. The Trace Filter Conditions tab will appear.
- Select a trace filter from the Trace Filter list.
- Select a trace condition that needs to be satisfied for the trace filter to match from the Condition list:
- Application: A list of applications appears. Select the desired application.
- Short Number: A box appears. Enter the desired short number of the application (sessions that receive a valid UCP60 with this short number as OAdC will be sent to the trace receiver).
- IP Address: A box appears. Enter the desired source IPv4/IPv6 address of the application (all sessions that have packets sent to and received from this IP will be sent to the trace receiver). The IP Address value can be IPv4 or IPv6 address.
- Unauthenticated sessions: An outside session has not yet been authenticated.
- All MXP Traffic: MXP is a NewNet proprietary protocol used for communication between the HUB, RTR, and AMS. With this condition, traffic can be traced between the HUB and RTR. This condition is only useful in case the NewNet Technical Assistance Centre (TAC) requested to use this option.
- Click Save.
The MGR will create the trace filter condition and close the tab.
Note: You must activate trace filters for them to begin collecting data, but it is not necessary to activate trace filter conditions (they are always active).