In Oracle Solaris 10, you use the ndd command to customize network parameters (tunables) and some driver-specific properties. Although the ndd command is still functional in Oracle Solaris 11, the dladm command is the preferred command for managing these properties.
The driver.conf file is also used in Oracle Solaris 10 to configure some driver-specific properties. In Oracle Solaris 11, you can configure some common driver features by setting dladm properties, as well as certain driver-private features through driver-private properties.
The following three classes of tunables are configurable:
Common generic properties – The majority of these properties have a straightforward mapping to a dladm command equivalent.
While ndd command parameters are queried and set with the –get and –set subcommands, dladm properties are queried and set with the show-linkprop and set-linkprop subcommands. You can also reset dladm properties by using the reset-linkprop subcommand. The following examples illustrate some of the differences between these two commands.
In the following example, the ndd command is used with the –get subcommand to retrieve the link speed of the datalink net0:
# ndd -get /dev/net/net0 link_speed
The following example shows the equivalent dladm command that you would use to retrieve that information from the speed property:
# dladm show-linkprop -p speed net0 LINK PROPERTY PERM VALUE EFFECTIVE DEFAULT POSSIBLE net0 speed r- 0 0 0 --
Another example is how the automatic negotiation of the link speed and duplex setting is enabled. In the following example, the ndd command is used to set the adv_autoneg_cap parameter:
# mdd -set /dev/net/net0 adv_autoneg_cap 1
Note that the ndd command does not configure settings that persist between reboots.
The following example shows how to enable the automatic negotiation of the link speed and duplex setting by using the dladm command to set the adv_autoneg_cap parameter:
# dladm set-linkprop -p adv_autoneg_cap=1
When you use the dladm command, the changes take place immediately and are persistent between system reboots.
Capability related tunables – Many of these properties have an equivalent dladm command option in Oracle Solaris 11. The list of properties is extensive. See the "Ethernet Link Properties" section of the dladm (1M) man page.
You can display these properties by using the dladm command without any options, or you can use the dladm show-ether command. If you do not specify any options with the dladm show-ether command, only the current Ethernet property values for the datalink are displayed. To obtain information beyond what is provided by default, use the –x option, as shown in the following example:
# dladm show-ether -x net1 LINK PTYPE STATE AUTO SPEED-DUPLEX PAUSE net1 current up yes 1G-f both -- capable -- yes 1G-fh,100M-fh,10M-fh both -- adv -- yes 100M-fh,10M-fh both -- peeradv -- yes 100M-f,10M-f both
With the –x option, the command also displays the built-in capabilities of the specified link, as well as the capabilities that are currently advertised between the host and the link partner.
Driver-specific properties – In Oracle Solaris 11, how you configure properties that were previously stored in the driver.conf file depends on the specific driver. The main property that was previously configured in this file is the maximum transmission unit (MTU) property. You manage this property by using the dladm command. See Setting the MTU Property in Configuring and Administering Network Components in Oracle Solaris 11.2 .
For more information about the various properties that you can customize by using the dladm command, see Obtaining Status Information for Datalink Properties in Configuring and Administering Network Components in Oracle Solaris 11.2 .
For information about configuring other private driver properties, refer to the manufacturer's documentation for that driver.