JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle Solaris Administration: Network Interfaces and Network Virtualization     Oracle Solaris 11 Information Library
search filter icon
search icon

Document Information

Preface

1.  Overview of the Networking Stack

Network Configuration in This Oracle Solaris Release

The Network Stack in Oracle Solaris

Network Devices and Datalink Names

Administration of Other Link Types

Part I Network Auto-Magic

2.  Introduction to NWAM

3.  NWAM Configuration and Administration (Overview)

4.  NWAM Profile Configuration (Tasks)

5.  NWAM Profile Administration (Tasks)

Obtaining Information About Profile States

Displaying the Current State of a Profile

Auxiliary State Values

Activating and Deactivating Profiles

Performing a Wireless Scan and Connecting to Available Wireless Networks

Troubleshooting NWAM Network Configuration

Monitoring the Current State of All Network Connections

Troubleshooting Network Interface Configuration Issues

6.  About the NWAM Graphical User Interface

Part II Datalink and Interface Configuration

7.  Using Datalink and Interface Configuration Commands on Profiles

8.  Datalink Configuration and Administration

9.  Configuring an IP Interface

10.  Configuring Wireless Interface Communications on Oracle Solaris

11.  Administering Bridges

12.  Administering Link Aggregations

13.  Administering VLANs

14.  Introducing IPMP

15.  Administering IPMP

16.  Exchanging Network Connectivity Information With LLDP

Part III Network Virtualization and Resource Management

17.  Introducing Network Virtualization and Resource Control (Overview)

18.  Planning for Network Virtualization and Resource Control

19.  Configuring Virtual Networks (Tasks)

20.  Using Link Protection in Virtualized Environments

21.  Managing Network Resources

22.  Monitoring Network Traffic and Resource Usage

Glossary

Index

Troubleshooting NWAM Network Configuration

The information in this section describes how to troubleshoot NWAM network configuration issues.

Monitoring the Current State of All Network Connections

The netadm command can be used with the show-events subcommand to listen for and display events that are being monitored by the NWAM daemon, nwamd. This subcommand provides useful information about events that are related to the configuration process for profiles and configuration objects, as they are configured by NWAM.

The syntax for the netadm show-events command is as follows:

netadm show-events [-v]

In the following example, the nwam show-events command is used with the -v option to display events in verbose mode:

$ netadm show-events -v
EVENT                    DESCRIPTION                                            
LINK_STATE               net0 -> state down                                     
OBJECT_STATE             ncu link:net0 -> state online*, interface/link is down 
OBJECT_STATE             ncu link:net0 -> state offline, interface/link is down 
OBJECT_STATE             ncu interface:net0 -> state online*, conditions for act 
OBJECT_STATE             ncu interface:net0 -> state offline, conditions for act
IF_STATE                 net0 -> state (0) flags 2004801                        
IF_STATE                 net0 -> state (0) flags 2004800                        
IF_STATE                 net0 -> state (0) flags 1004803                        
IF_STATE                 net0 -> state index 4 flags 0x0 address fe80::214:4fff: 
IF_STATE                 net0 -> state (0) flags 1004802                        
IF_STATE                 net0 -> state index 4 flags 0x0 address 129.156.235.229 
IF_STATE                 net0 -> state (0) flags 1004803                        
IF_STATE                 net0 -> state (0) flags 1004802                        
IF_STATE                 net0 -> state (0) flags 1004803                        
IF_STATE                 net0 -> state (0) flags 1004802         

Troubleshooting Network Interface Configuration Issues

The netadm list -x command is useful for determining why a network interface might not be configured correctly. This command displays the various entities that are configured by NWAM, their current state, and the reason why these entities are in that state.

For example, if a cable is unplugged, you can use the netadm list -x command to determine if the link state is offline and why, for example, “link is down.” Similarly, for duplicate address detection, the output of the netadm list -x command reveals that the physical link is online (up), but the IP interface is in a maintenance state. In this instance, the reason that is given is “Duplicate address detected.”

The following is an example of the output of the netadm list -x command:

$ netadm list -x
TYPE        PROFILE        STATE          AUXILIARY STATE
ncp         Automatic      online         active
ncu:phys    net0           offline        interface/link is down
ncu:ip      net0           offline        conditions for activation are unmet
ncu:phys    net1           offline*       need WiFi network selection
ncu:ip      net1           offline        conditions for activation are unmet
ncp         User           disabled       disabled by administrator
loc         Automatic      offline        conditions for activation are unmet
loc         NoNet          online         active
loc         office         offline        conditions for activation are unmet
$

After determining the reason that a link or interface is offline, you can proceed to correct the problem. In the case of a duplicate IP address, you must modify the static IP address that is assigned to the specified interface by using the netcfg command. For instructions, see Setting and Changing Property Values for a Profile. After you commit the changes, run the netadm list -x command again to check that the interface is now configured correctly, and that its state is displayed as online.

Another example of why an interface might not be configured correctly is if no known WLANs are available. In this case, the WiFi link's state would be displayed as offline, and the reason would be “need wifi selection". Or, if a WiFi selection was made, but a key is required, the reason would be “need wifi key".