|Skip Navigation Links|
|Exit Print View|
|Oracle Solaris Administration: Network Interfaces and Network Virtualization Oracle Solaris 11 Information Library|
Note the following differences in the manner the network is configured in this release that distinguishes it from previous Oracle Solaris releases:
Network configuration is managed by a profile. The type of configuration that is operative in a system depends on which network configuration profile is active. See Part I, Network Auto-Magic.
Datalinks on layer 2 of the networking stack are administered by using the dladm command. This command replaces previous ifconfig command options to configure datalink properties. Consequently, the configuration of link aggregations, VLANs, and IP tunnels have also changed. See Chapter 8, Datalink Configuration and Administration, Chapter 12, Administering Link Aggregations, and Chapter 13, Administering VLANs. See also Chapter 6, Configuring IP Tunnels, in Oracle Solaris Administration: IP Services.
Datalink names are no longer bound to their hardware drivers. Thus, datalinks, by default, are assigned generic link names such as net0, net1, and so on. See Network Devices and Datalink Names.
IP interfaces on layer 3 of the networking stack are administered by using the ipadm command. This command replaces previous ifconfig command options to configure IP interfaces. See Chapter 9, Configuring an IP Interface.
IPMP groups are implemented as IP interfaces and are therefore similarly configured with the ipadm command. Additionally, the ipmpstat is introduced that allows you to obtain IPMP-related information and statistics. See Chapter 14, Introducing IPMP and Chapter 15, Administering IPMP.
Virtualization is implemented on the network device level. Thus you can configure VNICs and manage the use of network resources for greater efficiency. See Part III, Network Virtualization and Resource Management.