Troubleshooting Network Administration Issues in Oracle® Solaris 11.2

Exit Print View

Updated: July 2014
 
 

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.2 .

Table 1-1  Tasks for Monitoring TCP/IP Networks
Task
Command and/or Description
Task Information
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 host is running.
Use the ping command to determine the status of a remote host.
Detect whether a host is dropping packets
Use the –s option of the ping command to determine whether a remote host 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 host.
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.
Check packets between an IPv4 server and a client.
Establish a snoop system off a hub that is connected to either a client or a server to check intervening traffic.
Monitor the packet transfer process.
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 network traffic on an IPv6 network.
Use the snoop ip6 command to display just IPv6 packets for a network node.
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.
Control the output of the ping, netstat, and traceroute commands.
Create a file named inet_type that sets the DEFAULT_IP variable in the file that controls the display output of IPv6-related commands.