JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle Solaris 11.1 Administration: SAN Configuration and Multipathing     Oracle Solaris 11.1 Information Library
search filter icon
search icon

Document Information


1.  Solaris I/0 Multipathing Overview

2.  Fibre Channel Multipathing Configuration Overview

3.  Configuring Solaris I/O Multipathing Features

4.  Administering Multipathing Devices

5.  Configuring Fabric-Connected Devices

6.  Configuring Solaris iSCSI Initiators

7.  Configuring Virtual Fibre Channel Ports

8.  Configuring FCoE Ports

9.  Configuring SAS Domains

10.  Configuring IPFC SAN Devices

IPFC Considerations

Determining Fibre Channel Adapter Port Instances

How to Determine Port Instances

How to Create an IPFC Instance

Invoking and Configuring IPFC

How to Start a Network Interface Manually

How to Configure the Host for Automatic Network Configuration

11.  Booting the Oracle Solaris OS From Fibre Channel Devices on x86 Based Systems

12.  Persistent Binding for Tape Devices

A.  Manual Configuration for Fabric-Connected Devices

B.  Supported FC-HBA API

C.  Troubleshooting Multipathed Device Problems


Invoking and Configuring IPFC

Immediately upon installation, start IPFC manually with the ipadm command. You can configure the host so that on subsequent reboot, the IPFC network interface starts automatically. This section describes the procedures to start a network interface manually and to configure the host for automatic plumbing upon reboot.

How to Start a Network Interface Manually

Use this procedure when you want to plumb IPFC with specific netmask values and get the IPFC interface up and running.

  1. Become an administrator.
  2. Configure the appropriate network interface.

    Ask your network administrator for an appropriate IP address and netmask information. For example, to enable an IPFC interface associated with fp instance 0 and an IP address of, type:

    # ipadm create-ip fcip0
    # ipadm create-addr -T static -a fcip0/ipv4

    For more information, see ipadm(1M).

  3. Confirm that the network is operational.
    # ipadm show-if

How to Configure the Host for Automatic Network Configuration

A system's hostname is set in the svc:/system/identity:node service. For example, the hostname is sys-A and the IPFC network interface is fcip0.

  1. Become an administrator.
  2. Confirm that the hostname is set.
    # svccfg -s identity:node
    svc:/system/identity:node> listprop config/nodename
    config/nodename  astring  sys-A

    If you need to set the hostname, use syntax similar to the following:

    # svccfg -s identity:node setprop config/nodename = "sys-A"
  3. Make any additional entries to the /etc/inet/hosts file.

    The installation program creates the /etc/inet/hosts file with minimum entries. You must manually make additional entries with a text editor. See the hosts(4) man page for additional information.

    The /etc/inet/hosts file contains the hosts database. This file contains the host names and the primary network interface IP addresses, as well as the IP addresses of other network interfaces attached to the system and of any other network interfaces that the machine must know about.

    The following example shows an etc/inet/host file.      localhost     loghost   neo1     #This is the local host name fcip0 #Interface to network
  4. Confirm that the name service SMF service is configured with files nis for hosts.
    # svccfg
    svc:> select network/nis/client:default
    svc:/network/nis/client:default> select name-service/switch
    svc:/system/name-service/switch> listprop config/host
    config/host astring     "files nis"
    svc:/system/name-service/switch> quit