|Skip Navigation Links|
|Exit Print View|
|System Administration Guide: IP Services Oracle Solaris 11 Express 11/10|
Network software installation occurs along with the installation of the operating system software. At that time, certain IP configuration parameters must be stored in appropriate files so that they can be read at boot time.
The network configuration process involves creating or editing the network configuration files. How configuration information is made available to a system's kernel is conditional. The availability depends on whether these files are stored locally (local files mode) or acquired from the network configuration server (network client mode).
The IP address of each network interface on every system.
The host names of each system on the network. You can type the host name in a local file or a name service database.
The NIS, LDAP, or DNS domain name in which the system resides, if applicable.
The default router addresses. You supply this information if you have a simple network topology with only one router attached to each network. You also supply this information if your routers do not run routing protocols such as the Router Discovery Server Protocol (RDISC) or the Router Information Protocol (RIP). For more information on default routers, refer to Packet Forwarding and Routing on IPv4 Networks See Table 4-1 for a list of routing protocols supported in Oracle Solaris.
Subnet mask (required only for networks with subnets).
If the Oracle Solaris installation program detects more than one interface on the system, you can optionally configure the additional interfaces during installation. For complete instructions, see Getting Started With Oracle Solaris 11 Express.
This chapter contains information on creating and editing local configuration files. See System Administration Guide: Naming and Directory Services (DNS, NIS, and LDAP) for information on working with name service databases.
Use this procedure for configuring TCP/IP on a host that runs in local files mode.
For steps for manually configuring interfaces in Oracle Solaris, refer to How to Configure an IP Interface in System Administration Guide: Network Interfaces and Network Virtualization.
When you specify the host name of a system during Oracle Solaris installation, that host name is entered into the /etc/nodename file. Make sure that the node name entry is the correct host name for the system.
The Oracle Solaris installation program creates entries for the primary network interface, loopback address, and, if applicable, any additional interfaces that were configured during installation.
For example, suppose host tenere was part of the domain deserts.worldwide.com. Therefore, you would type deserts.worldwide.com in /etc/defaultdomain. See /etc/defaultdomain File for more information.
See /etc/defaultrouter File for information about this file.
Additional routing options are available, as discussed in How to Configure Hosts for Network Client Mode. You can apply these options to a local files mode configuration.
If the host gets its IP address from a DHCP server, you do not have to specify the network mask.
If you have set up a NIS server on the same network as this client, you can add netmask information into the appropriate database on the server.
For all other conditions, do the following:
Use the following format:
For example, for the Class C network number 192.168.83, you would type:
For CIDR addresses, convert the network prefix into the equivalent dotted decimal representation. Network prefixes and their dotted decimal equivalents can be found in Table 1-3. For example, use the following to express the CIDR network prefix 192.168.3.0/22.
netmasks: files nis
Information for setting up installation servers and boot servers is found in Getting Started With Oracle Solaris 11 Express.
# mkdir /tftpboot
This command configures the system as a TFTP, bootparams, and RARP server.
# ln -s /tftpboot/. /tftpboot/tftpboot
Check that the entry reads as follows:
tftp dgram udp6 wait root /usr/sbin/in.tftpd in.tftpd -s /tftpboot
This line prevents in.tftpd from retrieving any file other than the files that are located in /tftpboot.
Add the host names and IP addresses for every client on the network.
Create entries for every host on the network that runs in network client mode.
See bootparams Database. Use the wildcard entry or create an entry for every host that runs in network client mode.
# svcs network/tftp/udp6
You should receive output resembling the following:
STATE STIME FMRI online 18:22:21 svc:/network/tftp/udp6:default
The in.tftpd daemon is managed by the Service Management Facility. Administrative actions on in.tftpd, such as enabling, disabling, or restarting, can be performed using the svcadm command. Responsibility for initiating and restarting this service is delegated to inetd. Use the inetadm command to make configuration changes and to view configuration information for in.tftpd. You can query the service's status by using the svcs command. For an overview of the Service Management Facility, refer to Chapter 11, Managing Services (Overview), in System Administration Guide: Basic Administration.
Network clients receive their configuration information from network configuration servers. Therefore, before you configure a host as a network client you must ensure that at least one network configuration server is set up for the network.
Do the following procedure on each host to be configured in network client mode.
# cat /etc/inet/hosts # Internet host table # 127.0.0.1 localhost
For more information, see Loopback Address. The file should not contain the IP address and host name for the local host (primary network interface).
If such a file exists, delete it.
This procedure explains how to modify the IPv4 address, host name, and other network parameters on a previously installed system. Use the procedure for modifying the IP address of a server or networked standalone system. The procedure does not apply to network clients or appliances. The steps create a configuration that persists across reboots.
Note - The instructions apply specifically to changing the IPv4 address of the primary network interface. To add another interface to the system, refer to How to Configure an IP Interface in System Administration Guide: Network Interfaces and Network Virtualization.
In almost all cases, the following steps use traditional IPv4 dotted decimal notation to specify the IPv4 address and subnet mask. Alternatively, you can use CIDR notation to specify the IPv4 address in all the applicable files in this procedure. For an introduction to CIDR notation, see IPv4 Addresses in CIDR Format.
# svccfg -s svc:/system/identity:node setprop config/nodename = astring: hostname
# reboot -- -r
Example 4-1 Changing the IP Address and Host Name
This example shows how to change a host's name, IP address of the primary network interface, and subnet mask. The IP address for the primary network interface bge0 changes from 10.0.0.14 to 192.168.34.100.
# ipadm show-addr ADDROBJ TYPE STATE ADDR lo0/v4 static ok 127.0.0.1/8 bge0/v4 static ok 10.0.0.14/24 # ipadm create-addr -T static -a 192.168.34.100/24 bge0/v4new # svccfg -s svc:/system/identity:node setprop config/nodename = astring: mynewhostname # ipadm show-addr ADDROBJ TYPE STATE ADDR lo0/v4 static ok 127.0.0.1/8 bge0/v4new static ok 192.168.34.100/24 # hostname mynewhostname
To change the IP address of an interface other than the primary network interface, refer to System Administration Guide: Basic Administration and How to Configure an IP Interface in System Administration Guide: Network Interfaces and Network Virtualization.