Skip Navigation Links | |
Exit Print View | |
Transitioning From Oracle Solaris 10 to Oracle Solaris 11.1 Oracle Solaris 11.1 Information Library |
1. Transitioning From Oracle Solaris 10 to an Oracle Solaris 11 Release (Overview)
2. Transitioning to an Oracle Solaris 11 Installation Method
6. Managing Software and Boot Environments
7. Managing Network Configuration
Network Configuration Feature Changes
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
10. Managing Oracle Solaris Releases in a Virtual Environment
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:
Profile types and network configuration – The two main profile types are the network configuration profile (NCP) and the Location profile. An NCP specifies the configuration of network datalinks and IP interfaces and addresses. The Location profile manages system-wide network configuration, for example naming services and IPfilter settings. Exactly one NCP and one Location profile must be active on the system at all times. If the DefaultFixed NCP is active, the system-defined DefaultFixed Location profile is also active. If any other reactive NCP is active, the Location that is activated is determined by rules and criteria that are specified in each of the reactive Locations. For information about other network profile types, see Network Profiles and Types in Connecting Systems Using Reactive Network Configuration in Oracle Solaris 11.1.
Using the Automatic NCP – The Automatic NCP is a system-defined profile that manages datalink and IP configuration, based on the current network environment. This NCP is automatically updated whenever your network environment changes, for example, when network devices are added or removed from the system. You cannot delete the Automatic NCP. You can modify this NCP by using the dladm and ipadm commands, but any modifications should be made with care.
Rather than directly modifying the Automatic NCP, the preferred method is to clone this NCP, and then apply your changes to the copy. Because the system does not change the configuration for any user-defined NCPs, including copies of the Automatic NCP, any changes that you make are preserved. See Example 7-8.
How system-defined Locations work – These profiles include the Automatic, NoNet, and DefaultFixed Locations. The DefaultFixed Location (new in Oracle Solaris 11.1) tracks changes that are made to naming services, etc. For example, the system updates the DefaultFixed Location to preserve changes that are made to any relevant SMF services (while the Location is active). When the DefaultFixed NCP is active on the system, so is the DefaultFixed Location. System-defined Location profiles can be modified by using the netcfg command, but only after these profiles have been activated on a system for the first time. For more information, see Chapter 1, Reactive Network Configuration (Overview), in Connecting Systems Using Reactive Network Configuration in Oracle Solaris 11.1.
During an installation, the network is configured, as follows:
For a GUI installation, the Automatic NCP is activated, and the network is automatically configured, based on current network conditions.
For a text installation, you must choose Automatic, Manual, or None.
If you choose Automatic, the Automatic NCP is activated, and the network is automatically configured upon reboot.
If you choose Manual, the DefaultFixed NCP is activated, and you are presented with a series of installation screens that enable you to manually configure network settings.
If you choose None, the DefaultFixed NCP is activated, but you do not provide network parameters during the installation. Thus, after a reboot, no network interface is plumbed or configured. Only the loopback IPv4 and IPv6 interfaces (lo0) are activated. You can create persistet network configuration by using dladm and ipadm after the installation. See Managing Network Configuration in Fixed Mode.
For an installation with AI, the network is configured according to the profile that you set up before the installation. If you did not specify any network settings prior to installing Oracle Solaris, the interactive sysconfig tool runs during the installation, enabling you to set network parameters for the system. See Installing Oracle Solaris by Using AI.
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.