JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Transitioning From Oracle Solaris 10 to Oracle Solaris 11.1     Oracle Solaris 11.1 Information Library
search filter icon
search icon

Document Information

Preface

1.  Transitioning From Oracle Solaris 10 to an Oracle Solaris 11 Release (Overview)

2.  Transitioning to an Oracle Solaris 11 Installation Method

3.  Managing Devices

4.  Managing Storage Features

5.  Managing File Systems

6.  Managing Software and Boot Environments

7.  Managing Network Configuration

Network Configuration Feature Changes

How the Network Is Configured in Oracle Solaris

How the Network Is Configured During an Installation

Network Configuration Commands

Managing Network Configuration in Fixed Mode

Displaying and Configuring Datalinks in Fixed Mode

Configuring IP Interfaces and Addresses in Fixed Mode

Configuring Naming Services in Fixed Mode

resolv.conf Error-Checking Capabilities

Temporarily Resetting SMF Naming Services

Importing Naming Services Configuration

How to Use a Legacy nsswitch.conf File

Configuring LDAP in Fixed Mode

Managing Network Configuration in Reactive Mode

Configuring Naming Services in Reactive Mode

Configuring LDAP in Reactive Mode

Creating Persistent Routes (Fixed and Reactive)

Configuring IPMP in Oracle Solaris 11

Managing Network Configuration From the Desktop

Network Configuration and Administration Commands (Quick Reference)

8.  Managing System Configuration

9.  Managing Security

10.  Managing Oracle Solaris Releases in a Virtual Environment

11.  Managing User Accounts and User Environments

12.  Managing Desktop Features

A.  SPARC Automated Installation Scenario

How the Network Is Configured in Oracle Solaris

Oracle Solaris 11 uses profile-based network configuration, which is comprised of two network configuration modes: fixed (manual) and reactive (automatic). The way you manage network configuration depends on the configuration mode that you are using and the profiles that are currently active on the system. After an installation, two system-defined network configuration profiles (NCPs) are present on the system: DefaultFixed and Automatic. Three system-defined Location profiles are present on the system after an installation: Automatic, NoNet, and DefaultFixed (new in Oracle Solaris 11.1). Additional reactive profiles can be created after an installation.

Both the text and AI installation methods default to fixed network configuration. For fixed network configuration, the dladm and ipadm commands are used. If the Automatic NCP or another reactive NCP is active after the installation, the netcfg and netadm commands are used to manage network configuration. Starting with Oracle Solaris 11.1, you can also use the dladm and ipadm commands to manage a reactive NCP, but the NCP must be currently active on the system.

Note the following additional information about profile-based network configuration:

How the Network Is Configured During an Installation

During an installation, the network is configured, as follows:


Note - Several aspects of network configuration have changed in Oracle Solaris 11, including where certain network configuration information is stored. For example, a system's default route is no longer stored in the /etc/defaultrouter file because this file is deprecated in Oracle Solaris 11. Do not check this file after an installation to determine a system's default route. Instead, use the route -p show command or the netstat -nr command. For more information, see Creating Persistent Routes (Fixed and Reactive).


Example 7-1 Verifying the Active NCP on a System

After an installation, use the netadm list command to determine which NCP is active (online). In the following example, the output of the netadm list command shows that the Automatic NCP is currently active:

$ netadm list
TYPE        PROFILE        STATE
ncp         Automatic      online
ncu:phys    net0           online
ncu:ip      net0           online
ncu:phys    net1           offline
ncu:ip      net1           offline
ncu:phys    net2           offline
ncu:ip      net2           offline
ncu:phys    net3           offline
ncu:ip      net3           offline
loc         Automatic      offline
loc         NoNet          offline
loc         myloc          online
loc         myncp          disabled

In the previous output, a user-defined Location named myloc is also online. This Location defines system-wide network settings for this particular configuration. When using reactive network configuration, exactly one NCP (either the Automatic NCP or another reactive NCP) and one Location must be active on the system at all times.

The output of the netadm list command in the following example shows that the DefaultFixed NCP is active, which means you must configure the network manually by using the dladm and ipadm commands. Note that whenever the DefaultFixed NCP is online, the DefaultFixed Location is also online:

# netadm list
TYPE        PROFILE        STATE
ncp         Automatic      disabled
ncp         DefaultFixed   online
loc         Automatic      offline
loc         NoNet          offline
loc         DefaultFixed   online

Example 7-2 Switching the Default NCP

Switching network configuration modes requires you to enable the appropriate NCP for that configuration mode. The following example shows how to switch from reactive mode to fixed mode by enabling the DefaultFixed NCP:

$ netadm enable -p ncp DefaultFixed

Switch to the Automatic NCP, as follows:

$ netadm enable -p ncp Automatic

The process of switching network configuration modes can take a few minutes. During this time, any messages about various network services that are displayed can be safely ignored.