Upgrade the Host Drivers

Language:

To upgrade the host drivers, follow the procedure which assumes an IPS package.

Locate the host software, which is typically on Oracle's eDelivery website.
Log in to the Oracle Solaris server as a root user.
Copy the drivers into the server.
These packages can go anywhere in the file system (for example, the root, /tmp or /oracle).

Note - If you are using a web repository, download the files to a directory on that server instead of the local hard drive on each individual server.
Untar the TAR ball by using the tar xvzf command in whichever directory contains the file. This procedure assumes that the file was downloaded to the /usr directory.
For example:
```
tar xvzf ORCLovn-5.0.0-SL-sparcv9.tgz
```
When the package is untarred, the host drivers are contained in the ORCLovn directory. The actual file name of the host driver package is system/io/ORCLovn-drv. Use system/io/ORCLovn-drv when specifying the driver package to upgrade.
Set up the publisher by using the pkg set-publisher command and specifying the path to the directory in which the host driver file resides.
For example:
```
pkg set-publisher -p/usr/ORCLovn
```

Upgrade the host drivers by using the pkg update command and specifying the host driver file name.

For example:

pkg update /usr/ORCLovn system/io/ORCLovn-drv

Packages to install: 1
    `            Create boot environment: No
          Create backup boot environment: Yes
                      Services to change: 1

DOWNLOAD                                 PKGS        FILES
XFER (MB) SPEED
      Completed 
1.1/1.1   0 B/s                         1/1          19/19

PHASE                                  ITEMS
Installing new actions                 45/45
Updating package state database         Done
Updating image state                    Done
Creating fast lookup database           Done
Reading search index                    Done
Updating search index                    1/1

Note - This step assumes you are upgrading the host drivers from a local repository. If you are upgrading the host drivers from a web repository, you can specify the URL for the location of the file. For example, http://drivers/system/io/ORCLovn-drv for a server named drivers.

(Optional) Unset the publisher by using the pkg unset-publisher command and specifying the directory location where the host driver file is located.
For example:
```
pkg unset-publisher /usr/ORCLovn
```
Verify that all cabling is complete and correct.
If the physical layer connectivity is not functional, the nodes might not come online correctly after the server is rebooted.
You can reboot the server by using any of the following commands:
- ```
reboot --rv
```
- ```
shutdown -y -g0 -ib
```
Allow the server to completely reboot, then log back in as root.
Verify that the upgraded version of host drivers is installed by issuing the pkg list command while grepping for ORCLovn-drv which is a part of the driver file name.
For example:
```
pkg list|grep ORCLovn-drv
          system/io/ORCLovn-drv (Oracle)
0.5.11-0.175.1.0.0.2.727    i--
```

Confirm that the service is running:

> svcs xsadmd
STATE         STIME     FMRI
online        11:10:35  svc:/application/xsadmd:default

Display all the upgraded software and dependencies are installed by issuing the modinfo command and grepping for xs to find the installed software components.

For example:

modinfo | grep xs
170 7b246000   66f0    285     1 xstn (Xsigo Transport nexus driver v1)
171 7b24e000  1e060      -     1 xstl (Xsigo Transport services v0.2)
174 7b2a0000   f510    286     1 xsvnic (Xsvnic GLDv3 Driver)
181 7b2b0000  309b0    287     1 xsvhba (Xsigo Virtual HBA)

Verify that the attachment points and XSTN nodes are up and running on the Oracle Solaris host:

The host's HCA should be up and connected.
The host's IB fabric should be running.
The InfiniBand port link should be connected to the Oracle Fabric Interconnect. Oracle's Virtual Networking uses the InfiniBand port as a transport medium to the server.
Related IB services should be connected.

The bold text in the following example highlights the HCA and IB functionality that should be verified.

> cfgadm -a
Ap_Id                         Type         Receptacle       Occupant      Condition
c2                            scsi-sas     connected        configured    unknown
c2::dsk/c2t6d0                CD-ROM       connected        configured    unknown
c4                            scsi-sas     connected        configured    unknown
c4::w5000cca03c59d0c9,0       disk-path    connected        configured    unknown
c5                            scsi-sas     connected        unconfigured  unknown
c6                            scsi-sas     connected        configured    unknown     
c6::w5000cca03c59acd9,0       disk-path    connected        configured    unknown
c7                            scsi-sas     connected        unconfigured  unknown
hca:21280001CF8382            IB-HCA       connected        configured    ok
ib                            IB-Fabric    connected        configured    ok
ib::21280001CF8383,0,ipib     IB-PORT      connected        configured    ok
ib::21280001CF8383,ffff,xstn  IB-VPPA      connected        configured    ok
ib::21280001CF8384,0,ipib     IB-PORT      connected        configured    ok
ib::21280001CF8384,ffff,xstn  IB-VPPA      connected        configured    ok
ib::daplt,0                   IB-PSEUDO    connected        configured    ok
ib::eibnx,0                   IB-PSEUDO    connected        configured    ok
ib::iser,0                    IB-PSEUDO    connected        configured    ok
ib::rdsib,0                   IB-PSEUDO    connected        configured    ok
ib::rdsv3,0                   IB-PSEUDO    connected        configured    ok
ib::rpcib,0                   IB-PSEUDO    connected        configured    ok
ib::sol_umad,0                IB-PSEUDO    connected        configured    ok
ib::sol_uverbs,0              IB-PSEUDO    connected        configured    ok
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-hub      connected        configured    ok
usb2/2.1                      unknown      empty            unconfigured  ok
usb2/2.2                      unknown      empty            unconfigured  ok
usb2/2.3                      usb-hub      connected        configured    ok
usb2/2.3.1                    unknown      empty            unconfigured  ok
usb2/2.3.2                    usb-storage  connected        configured    ok
usb2/2.3.3                    unknown      empty            unconfigured  ok
usb2/2.4                      usb-device   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