Identifying HBAs

After an HBA has been installed on a host, run the following command on the host to check whether the HBA is identified by the host.

root@S113:~# cfgadm -al
Ap_Id                          Type         Receptacle   Occupant     Condition
c2                             scsi-sas     connected    configured   unknown
c2::dsk/c2t0d0                 disk         connected    configured   unknown
c2::dsk/c2t1d0                 disk         connected    configured   unknown
c2::dsk/c2t2d0                 disk         connected    configured   unknown
c2::dsk/c2t3d0                 disk         connected    configured   unknown
c2::dsk/c2t4d0                 disk         connected    configured   unknown
c2::dsk/c2t5d0                 disk         connected    configured   unknown
c2::dsk/c2t6d0                 disk         connected    configured   unknown
c3                             fc           connected    unconfigured unknown
c4                             fc           connected    unconfigured unknown
c5                             fc-fabric    connected    configured   unknown
c5::200016212c374217           disk         connected    configured   unknown
c5::200116212c374217           disk         connected    configured   unknown
c5::201016212c374217           disk         connected    configured   unknown
c5::201116212c374217           disk         connected    configured   unknown
c5::2100000e1e1a9b31           unknown      connected    unconfigured unknown
c5::28b0010203040577           disk         connected    configured   unknown
c5::28b1010203040577           disk         connected    configured   unknown
c5::2990010203040577           disk         connected    configured   unknown
c5::2991010203040577           disk         connected    configured   unknown
c6                             fc-fabric    connected    configured   unknown
c6::200016212c374217           disk         connected    configured   unknown
c6::200116212c374217           disk         connected    configured   unknown
c6::201016212c374217           disk         connected    configured   unknown
c6::201116212c374217           disk         connected    configured   unknown
c6::2100000e1e1a9b30           unknown      connected    unconfigured unknown
c6::28b0010203040577           disk         connected    configured   unknown
c6::28b1010203040577           disk         connected    configured   unknown
c6::2990010203040577           disk         connected    configured   unknown
c6::2991010203040577           disk         connected    configured   unknown
usb0/1                         unknown      empty        unconfigured ok
usb0/2                         unknown      empty        unconfigured ok
usb0/3                         unknown      empty        unconfigured ok
usb1/1                         unknown      empty        unconfigured ok
usb1/2                         unknown      empty        unconfigured ok
usb2/1                         unknown      empty        unconfigured ok
usb2/2                         usb-storage  connected    configured   ok
usb2/3                         unknown      empty        unconfigured ok
usb2/4                         usb-hub      connected    configured   ok
usb2/4.1                       unknown      empty        unconfigured ok
usb2/4.2                       unknown      empty        unconfigured ok
usb2/4.3                       unknown      empty        unconfigured ok
usb2/4.4                       unknown      empty        unconfigured ok
usb2/5                         unknown      empty        unconfigured ok
root@S113:~# 

In the command output, two Ap_Ids (c5 and c6) are of the fc-fabric type. This indicates that the host has identified two Fibre Channel ports on the HBAs.

Make sure that Receptacle is connected and Occupant is configured. Otherwise, follow-up operations such as LUN discovery will be affected.

If Receptacle is connected and Occupant is unconfigured, perform the following operations:

• Manually configure the device.

  Run the cfgadm -c configure cx command, in which cx is a variable that is set based on site requirements.

• Forcibly initialize the device.

  Run the luxadm -e port command to query the device that must be forcibly initialized, and then run the luxadm -e forcelip device command to initialize the Fibre Channel link of the port. The following is an example:

  bash-3.2# luxadm -e port

  /devices/pci@1f,700000/pci@0/fibre-channel@2/fp@0,0:devctl         CONNECTED

  /devices/pci@1f,700000/pci@0/fibre-channel@2,1/fp@0,0:devctl       CONNECTED

  bash-3.2# 

  bash-3.2# luxadm -e forcelip /devices/pci@1f,700000/pci@0/fibre-channel@2/fp@0,0:devctl

  bash-3.2# 

  When this command is executed, the HBA port is initialized. All links on the port are interrupted and then reconnected.

• Restart the host.

  If the preceding methods cannot resolve the problem, run the shutdown -y -i6 -g0 command to restart the host.

  Exercise caution when performing this operation, because this affects services on the host.