Go to main content

Configuring and Managing Network Components in Oracle® Solaris 11.3

Exit Print View

Updated: December 2017
 
 

Configuring a System for Local Files Mode

When running in local files mode, a system obtains all TCP/IP configuration information from files that are located in a local directory. In network client mode, the configuration information is provided to all of the systems in the network by a remote network configuration server.

    Typically, the following servers on the network run in local files mode:

  • Network configuration servers

  • NFS servers

  • Name servers that supply NIS, LDAP, or DNS services

  • Mail servers

  • Routers

Since clients can run in either network client mode or local files mode, on any given network, you can have a combination of these modes with which different systems are configured.

How to Configure a System for Local Files Mode

  1. Become an administrator.
  2. Configure the system's IP interfaces with the assigned IP addresses.

    Refer to How to Configure an IPv4 Interface in Configuring and Managing Network Components in Oracle Solaris 11.3.

  3. Verify that the host name was set correctly.
    # hostname

    For more information, see the hostname(1) man page.

  4. Verify that the entries in the /etc/inet/hosts are current.

    Oracle Solaris creates entries for the primary network interface, the loopback address, and any additional interfaces that are configured during the installation, if applicable. If the entries are not current, add the IP addresses and corresponding names for any network interfaces that were added to the system after the installation.

  5. Specify the system's fully qualified domain as a property of the nis/domain SMF service.

    For example, you would specify deserts.example.com as the value for the domainname property of the nis/domain SMF service as follows:

    # domainname domainname

    This step makes the change persistent.

  6. Add the routing information.

    Note -  If you are using DHCP services, you can skip this step.

    For instructions, see Configuring Routing.

  7. Add the netmask information, if applicable.

    Note -  If you are using DHCP services, you can skip this step.
    1. Type the network number and the netmask in the /etc/inet/netmasks file.

      To create entries, use the format network-number netmask. For example, to specify the Class C network number 192.0.2, you would type the following information:

      192.0.2.0    255.255.255.0

      For CIDR addresses, convert the network prefix to the equivalent dotted decimal representation. For example, type the following information to express the CIDR network prefix 192.0.2.0/22.

      192.0.2.0     255.255.252.0
    2. Change the lookup source for the netmask in the name-service/switch property so that only local files are searched, then refresh the name service instance.
      # svccfg -s name-service/switch setprop config/netmask = astring: "files"
      # svccfg -s name-service/switch:default refresh
  8. Reboot the system.