JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Configuring and Administering Oracle Solaris 11.1 Networks     Oracle Solaris 11.1 Information Library
search filter icon
search icon

Document Information

Preface

1.  Planning the Network Deployment

2.  Considerations When Using IPv6 Addresses

3.  Configuring an IPv4 Network

4.  Enabling IPv6 on the Network

5.  Administering a TCP/IP Network

Major TCP/IP Administrative Tasks (Task Map)

Monitoring Network Status With the netstat Command

How to Display Statistics by Protocol

How to Display the Status of Transport Protocols

How to Display Network Interface Status

How to Display the Status of Sockets

How to Display the Status of Transmissions for Packets of a Specific Address Type

How to Display the Status of Known Routes

Probing Remote Hosts With the ping Command

How to Determine if a Remote Host Is Running

How to Determine if a Host Is Dropping Packets

Administering and Logging Network Status Displays

How to Control the Display Output of IP-Related Commands

How to Log Actions of the IPv4 Routing Daemon

How to Trace the Activities of the IPv6 Neighbor Discovery Daemon

Displaying Routing Information With the traceroute Command

How to Find Out the Route to a Remote Host

How to Trace All Routes

Monitoring Packet Transfers With the snoop Command

How to Check Packets From All Interfaces

How to Capture snoop Output Into a File

How to Check Packets Between an IPv4 Server and a Client

How to Monitor IPv6 Network Traffic

Monitoring Packets by Using IP Layer Devices

How to Check Packets on the IP Layer

Examples of Checking Packets

Administering Default Address Selection

How to Administer the IPv6 Address Selection Policy Table

How to Modify the IPv6 Address Selection Table for the Current Session Only

6.  Configuring IP Tunnels

7.  IPv4 Reference

8.  IPv6 Reference

Index

Administering and Logging Network Status Displays

The following tasks show how to check the status of the network by using well-known networking commands.

How to Control the Display Output of IP-Related Commands

You can control the output of the netstat command to display IPv4 information only, or both IPv4 and IPv6 information.

  1. Create the /etc/default/inet_type file.
  2. Add one of the following entries to /etc/default/inet_type, as required for your network:
    • To display IPv4 information only:

      DEFAULT_IP=IP_VERSION4
    • To display both IPv4 and IPv6 information:

      DEFAULT_IP=BOTH

      Or

      DEFAULT_IP=IP_VERSION6

      For more information about the inet_type file, see the inet_type(4) man page.


    Note - The -f flag in the netstat command overrides the values set in the inet_type file.


Example 5-10 Controlling Output to Select IPv4 and IPv6 Information

How to Log Actions of the IPv4 Routing Daemon

If you suspect a malfunction of routed, the IPv4 routing daemon, you can start a log that traces the daemon's activity. The log includes all packet transfers when you start the routed daemon.

Example 5-11 Network Log for the in.routed Daemon

The following example shows the beginning of the log that is created by the procedure How to Log Actions of the IPv4 Routing Daemon.

-- 2003/11/18 16:47:00.000000 --
Tracing actions started
RCVBUF=61440
Add interface lo0  #1   127.0.0.1      -->127.0.0.1/32   
   <UP|LOOPBACK|RUNNING|MULTICAST|IPv4> <PASSIVE> 
Add interface net0 #2   10.10.48.112    -->10.10.48.0/25   
    <UP|BROADCAST|RUNNING|MULTICAST|IPv4> 
turn on RIP
Add    10.0.0.0        -->10.10.48.112      metric=0  net0  <NET_SYN>
Add    10.10.48.85/25  -->10.10.48.112      metric=0  net0  <IF|NOPROP>

How to Trace the Activities of the IPv6 Neighbor Discovery Daemon

If you suspect a malfunction of the IPv6 in.ndpd daemon, you can start a log that traces the daemon's activity. This trace is displayed on the standard output until terminated. This trace includes all packet transfers when you start the in.ndpd daemon.

  1. Start a trace of the in.ndpd daemon.
    # /usr/lib/inet/in.ndpd -t
  2. Terminate the trace as needed by typing Control-C.

Example 5-12 Trace of the in.ndpd Daemon

The following output shows the beginning of a trace of in.ndpd.

# /usr/lib/inet/in.ndpd -t
Nov 18 17:27:28 Sending solicitation to  ff02::2 (16 bytes) on net0
Nov 18 17:27:28         Source LLA: len 6 <08:00:20:b9:4c:54>
Nov 18 17:27:28 Received valid advert from fe80::a00:20ff:fee9:2d27 (88 bytes) on net0
Nov 18 17:27:28         Max hop limit: 0
Nov 18 17:27:28         Managed address configuration: Not set
Nov 18 17:27:28         Other configuration flag: Not set
Nov 18 17:27:28         Router lifetime: 1800
Nov 18 17:27:28         Reachable timer: 0
Nov 18 17:27:28         Reachable retrans timer: 0
Nov 18 17:27:28         Source LLA: len 6 <08:00:20:e9:2d:27>
Nov 18 17:27:28         Prefix: 2001:08db:3c4d:1::/64
Nov 18 17:27:28                 On link flag:Set
Nov 18 17:27:28                 Auto addrconf flag:Set
Nov 18 17:27:28                 Valid time: 2592000
Nov 18 17:27:28                 Preferred time: 604800
Nov 18 17:27:28         Prefix: 2002:0a00:3010:2::/64
Nov 18 17:27:28                 On link flag:Set
Nov 18 17:27:28                 Auto addrconf flag:Set
Nov 18 17:27:28                 Valid time: 2592000
Nov 18 17:27:28                 Preferred time: 604800