4 Monitoring and troubleshooting SDP

This section describes the tools used for monitoring and troubleshooting SDP.

Using sdpnetstat command to check SDP's functioning

Because SDP is a transparent TCP replacement, it is sometimes difficult to know whether SDP is working correctly or not. To verify whether traffic is passing through SDP or TCP, use the sdpnetstat command [-Soption] and monitor the counters that are running.

sdpnetstat -s

This command collects all the SDP statistics that is useful for debugging and troubleshooting. See “Collecting SDP statistics” (page 17) for a sample output of the sdpnetstat -scommand.

sdpnetstat -z

This command zeros all the SDP statistics data.

Monitoring and troubleshooting SDP using sdpnetstat command

The sdpnetstat command is used to verify that SDP is loaded and being used.

sdpnetstat -a

The sdpnetstat -acommand shows all active and passive SDP sockets that use the same format as the traditional netstat program.

When the SDP kernel module is loaded and is being used, the output of the host1$ sdpnetstat -acommand appears as follows:

host1$ sdpnetstat -a

----------------------------------------------------------------------------------------

SDP SOCKETS

-------------------------------------------------------------------------------------------------

Proto Recv-Q Send-Q Local Address

Foreign Address

Inode

State

sdp

0

0

1.1.1.2:40

0.0.0.0:0

0

LISTEN

sdp

0

0

0.0.0.0:0

0.0.0.0:0

0

CLOSED

This example shows two active and passive SDP sockets and contains details about the connections. If the SDP kernel module is not loaded, the output of the command appear as follows:

host1$ sdpnetstat -a

"sdpnetstat: No support for AF_INET_SDP on this is system"

To verify whether the SDP module is loaded or not, the kcmodule command can be used:

# kcmodule sdp

Module State Cause

sdp static best

Debugging the libsdp.so library

SDP provides debug support for both the user space libsdp.so library and the sdp kernel module. Both are useful to understand why a TCP socket was not redirected over SDP, and help to find problems that occurred while implementing SDP.

User space SDP debug is controlled by options in the libsdp.conf file. You can also have a local version of the libsdp.conf file and point to it explicitly using the following command:

host1$ export LIBSDP_CONFIG_FILE=<path>/libsdp.conf

To obtain extensive debug information, modify the libsdp.conf file by changing the min-level variable value, after which the log directive produces maximum debug output (provide the min-level

Using sdpnetstat command to check SDP's functioning

9