JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle Solaris SAN Configuration and Multipathing Guide     Oracle Solaris 10 1/13 Information Library
search filter icon
search icon

Document Information


1.  Solaris I/0 Multipathing Overview

2.  Configuring Solaris I/O Multipathing Features

3.  Configuring Fabric-Connected Devices

4.  Configuring Oracle Solaris iSCSI Initiators

5.  Configuring SAS Domains

6.  Configuring IPFC SAN Devices

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

8.  Persistent Binding for Tape Devices

A.  Manual Configuration for Fabric-Connected Devices

Manually Configuring FC Devices

How to Manually Configure a FC Device

Configuring Fabric Device Nodes

Ensuring That LUN Level Information Is Visible

How to Ensure LUN Level Information is Visible

How to Detect Visible Fabric Devices on a System

Configuring Device Nodes Without Multipathing Enabled

How to Manually Configure an FC Device Without Multipathing

How to Configure Multiple FC Devices Without Multipathing

Configuring Device Nodes With Solaris Multipathing Enabled

How to Configure Individual Multipathed FC Devices

How to Configure Multiple Multipathed FC Devices

Unconfiguring Fabric Devices

Unconfiguring a Fabric Device

How to Manually Unconfigure a FC Device

How to Unconfigure All FC Devices on a FC Host Port

How to Unconfigure a Multipathed FC Device

How to Unconfigure One Path to a Multipathed FC Device

How to Unconfigure All Multipathed FC Devices

B.  Supported FC-HBA API

C.  Troubleshooting Multipathing-Related Problems


How to Detect Visible Fabric Devices on a System

This section provides an example of the procedure for detecting fabric devices using FC host ports c0 and c1. This procedure also shows the device configuration information that is displayed with the cfgadm command.

Note - In the following examples, only failover path attachment point IDs (Ap_Ids) are listed. The Ap_Ids displayed on your system depend on your system configuration.

  1. Become superuser.
  2. Display the information about the attachment points on the system.
    # cfgadm -l
    Ap_Id                Type         Receptacle   Occupant     Condition
    c0                 fc-fabric      connected    unconfigured unknown
    c1                 fc-private     connected    configured   unknown

    In this example, c0 represents a fabric-connected host port, and c1 represents a private, loop-connected host port. Use the cfgadm command to manage the device configuration on fabric-connected host ports.

    By default, the device configuration on private, loop-connected host ports is managed by a system running the Oracle Solaris OS.

  3. Display information about the host ports and their attached devices.
    # cfgadm -al
    Ap_Id                Type      Receptacle     Occupant   Condition
    c0                 fc-fabric   connected    unconfigured unknown
    c0::50020f2300006077 disk      connected    unconfigured unknown
    c0::50020f23000063a9 disk      connected    unconfigured unknown
    c0::50020f2300005f24 disk      connected    unconfigured unknown
    c0::50020f2300006107 disk      connected    unconfigured unknown
    c1                 fc-private  connected    configured   unknown
    c1::220203708b69c32b disk      connected    configured   unknown
    c1::220203708ba7d832 disk      connected    configured   unknown
    c1::220203708b8d45f2 disk      connected    configured   unknown
    c1::220203708b9b20b2 disk      connected    configured   unknown

    Note - The cfgadm -l command displays information about FC host ports. You can also use the cfgadm -al command to display information about FC devices. The lines that include a port world wide name (WWN) in the Ap_Id field associated with c0 represent a fabric device. Use the cfgadm configure and unconfigure commands to manage those devices and make them available to systems using the Oracle Solaris OS. The Ap_Id devices with port WWNs under c1 represent private-loop devices that are configured through the c1 host port.