Go to main content

Troubleshooting Network Administration Issues in Oracle® Solaris 11.4

Exit Print View

Updated: November 2020

Resources for Monitoring and Detecting Problems on a TCP/IP Network

The following table describes tasks for monitoring and detecting problems on a TCP/IP network. For complete instructions, see Administering TCP/IP Networks, IPMP, and IP Tunnels in Oracle Solaris 11.4.

Table 1  Tasks for Monitoring TCP/IP Networks
Command and/or Description
Task Information
Monitor network traffic for features at the various layers of the Oracle Solaris network protocol stack.
Depending on the feature and at which layer of the network protocol the feature is configured, you can use a variety of observability tools to gather statistics and monitor network traffic usage.
Log the IP addresses of all incoming TCP connections.
Transport layer protocols typically need no intervention to run properly. However, in some circumstances, you might need to log or modify services that run over the transport layer protocols.
Determine whether a remote system is running.
Use the ping command to determine the status of a remote system.
Detect whether a system is dropping packets
Use the –s option of the ping command to determine whether a remote system is running but losing packets.
Display network statistics on a per-protocol basis.
Use the netstat command to display statistics on a per-protocol basis for TCP, Stream Control Transmission Protocol (SCTP), and User Datagram Protocol (UDP) endpoints in table format.
Perform TCP and UDP management.
Use the netcat (or nc) utility to open TCP connections, send UDP packets, listen on arbitrary TCP and UDP ports, perform port scanning.
Trace the actions of the IPv4 routing daemon, including all packet transfers.
If you suspect a malfunction of the routed daemon, you can start a log that traces the daemon's activity. The log includes all packet transfers when you start the routed daemon.
Discover the route to a remote system.
Use the traceroute command to discover the route to a remote system. The output displays the number of hops in the path a packet follows.
Monitor IPv4 and IPv6 packet transfer processes.
Use the snoop command to monitor the state of package (data) transfers.
Analyze network traffic.
Use the TShark command line interface (CLI) or the Wireshark graphical user interface (GUI) to analyze network traffic.
Monitor network traffic on a server.
Use the ipstat and tcpstat commands to monitor network traffic on a server.
Monitor the status of IPMP on your system.
Use the ipmpstat command to gather different types of information about the status of IPMP. You can also use the command to display information about the underlying IP interfaces for each IPMP group, as well as data and test addresses are configured for the group.