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


1.  Overview of the Networking Stack

Network Configuration in This Oracle Solaris Release

The Network Stack in Oracle Solaris

Network Devices and Datalink Names

Default Generic Link Names

The Assignment of Generic Names to Datalinks

Customizing How Generic Link Names Are Assigned

Link Names in Upgraded Systems

Replacing Hardware-Based Link Names

Caution About Changing Link Names

Rules for Valid Link 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)

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



Network Devices and Datalink Names

From an administrative perspective, administrators create IP interfaces on top of datalinks. The datalink represents a link object in the second layer of the Open Systems Interconnection (OSI) model. The physical link is directly associated with a device and possesses a device name. The device name is essentially the device instance name, and is composed of the driver name and the device instance number. The instance number can have a value from zero to n, depending on how many NICs use that driver on the system.

For example, consider a Gigabit Ethernet card, which is often used as the primary NIC on both host systems and server systems. Some typical driver names for this NIC are bge and e1000g. When used as the primary NIC, the Gigabit Ethernet interface has a device name such as bge0 or e1000g0. Other driver names are nge, nxge, and so on.

In this Oracle Solaris release, the device instance name continues to depend on the underlying hardware. However, datalinks on top of these devices are not similarly bound and can be given meaningful names. For example, the administrator can assign the datalink on top of device instance e1000g0 the name itops0. In this Oracle Solaris release, datalinks by default are provided with generic names. To display the mapping between the datalinks with their generic names and the corresponding device instances, you use the dladm sho-phys subcommand.

Default Generic Link Names

When you install this Oracle Solaris release on a system for the first time, Oracle Solaris automatically provides generic link names for all the system's physical network devices. This name assignment uses the net# naming convention, where the # is the instance number. This instance number increments for each device, for example, net0, net1, net2, and so on.

Generic or flexible link names provide advantages in network configuration as shown in the following examples:

The Assignment of Generic Names to Datalinks

In Oracle Solaris, generic names are automatically assigned to all the datalinks based on specific criteria. All devices share the same prefix net. However, the instance numbers are assigned based on the following:

Based on the criteria, Ethernet devices on a lower motherboard or ioboard, hostbridge, PCIe rootcomplex, bus, device, and function are ranked ahead of the other devices.

To display the correspondences of link names, devices, and locations, use the dladm show-phys command as follows:

# dladm show-phys -L
net0         e1000g0       MB
net1         e1000g1       MB
net2         e1000g2       MB
net3         e1000g3       MB
net4         ibp0          MB/RISER0/PCIE0/PORT1
net5         ibp1          MB/RISER0/PCIE0/PORT2
net6         eoib2         MB/RISER0/PCIE0/PORT1/cloud-nm2gw-2/1A-ETH-2
net7         eoib4         MB/RISER0/PCIE0/PORT2/cloud-nm2gw-2/1A-ETH-2

Customizing How Generic Link Names Are Assigned

Oracle Solaris uses the prefix net when assigning link names. However, any custom prefix can be used instead, such as eth. If you prefer, you can also disable the automatic assignment of neutral link names.


Caution - You must customize how generic link names are automatically assigned before you install Oracle Solaris. After installation, you cannot customize the default link names without tearing down existing configurations.

To disable automatic link naming, or to customize the prefix of link names, set the following property in the System Configuration manifests that are used by the Automated Install (AI) program.

<service name="network/datalink-management"
   version="1" type="service">
      <instance name="default enabled="true">
         <property_group name='linkname-policy'
               <propval name='phys-prefix' type='astring'

By default, the value for phys-prefix is set to net, as shown in emphasis.

If the value that is provided to phys-prefix is invalid, then that value will be ignored. The datalinks will be named according to their associated hardware drivers, such as bge0, e1000g0, and so on. For rules about valid link names, see Rules for Valid Link Names.

Link Names in Upgraded Systems

In systems where this Oracle Solaris release is freshly installed, datalinks are automatically named net0 through netN-1, where N represents the total number of network devices.

The case is not true if you upgrade from Oracle Solaris 11 Express. On such upgraded systems, the datalinks retain their names prior to the upgrade. These names would either be the default hardware-based names, or customized names that the administrator assigned to the datalinks before the upgrade. Further, on these upgraded systems, new network devices that are subsequently added also retain the default hardware-based names rather than receive neutral names. This behavior for upgraded systems ensures that no neutral names that are assigned by the OS become mixed with other hardware-based names or customize names assigned by the administrator before the upgrade.

In any system with this Oracle Solaris release, both hardware-based names as well as OS-supplied link names can be replaced by other names that you prefer to use. Typically, the default link names that are assigned by the OS suffice for creating the system's network configuration. However, if you select to change link names, note the important considerations discussed in the following sections.

Replacing Hardware-Based Link Names

If your system's links have hardware-based names, rename these links with at least generic names. If you retain the hardware-based names of the links, confusion might arise in later situations where these physical devices are removed or replaced.

For example, you retain the link name bge0 that is associated with the device bge0. All link configurations are performed by referring to the link name. Later, you might replace the NIC bge with the NIC e1000g. To reapply the former device's link configuration to the new NIC e1000g0, you would need to reassign the link name bge0 to e1000g0. The combination of a hardware-based link name bge0 with a different associated NIC e1000g0 can cause confusion. By using names that are not hardware-based, you can better distinguish the links from the associated devices.

Caution About Changing Link Names

While replacing hardware-based link names is recommended, you must still plan carefully before you rename links. Changing the device's link name does not automatically propagate the new name to all existing associated configurations. The following examples illustrate the risks when you change link names:

Thus, as a general rule, do not rename datalinks randomly. When renaming datalinks, ensure that all of the link's associated configurations continue to apply after the link name is changed. Some of the configurations that might be affected by renaming links are as follows:

Rules for Valid Link Names

When you assign link names, observe the following rules:

Note - As an added restriction, you cannot use lo0 as a flexible link name. This name is reserved to identify the IP loopback interface.

The function of the link within your network setup can be a useful reference when you assign link names. For example, netmgt0 can be a link that is dedicated to network management. Upstream2 can be the link that connects to the ISP. As a general rule to avoid confusion, do not assign names of known devices to your links.