Performing Lin_Tape Self Service

You can perform Lin_Tape Self Service.

Procedure

Obtain the archived source driver lin_tape-3.0.60-rhel7.x86_64 from IBM FIXCENTRAL.
Create a RHEL 7.9 virtual machine (VM) and update the kernel to the same level as the HyperScale X nodes.
Make sure that the kernel-devel is the correct level as the required kernel.

Note

You require a licensed VM with access to RHEL updates.
1. On HyperScale X nodes, execute the following command:
```
uname -r
```
  Note the running kernel that appears in the output.
2. On the VM, execute the following commands:
```
yum install <kernel version from output of uname -r on HyperScale node>
```
```
reboot
```
```
yum install "kernel-devel-uname-r == $(uname -r)" #Reboot node to apply new kernel
```
```
reboot
```
```
yum install rpm-build glibc-devel gcc
```
Move source file from step 1 to a working location on the VM and rebuild the file for the running kernel.

For more information, see Installing the lin_tape device driver.

On the VM, execute the following command:
```
rpmbuild --rebuild lin_tape-1.60.0-1.src.rpm 
```
The output of the command is very large. Near the end, the command output looks like the following example:
```
# rpmbuild --rebuildlin_tape-1.60.0-1.src.rpm |tee lin-install.log Installing lin_tape-1.60.0-1.src.rpm
Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.53402
....
Checking for unpackaged file(s): /usr/lib/rpm/check-files /var/tmp/lin_tape-1.61.0-1-root-root
Wrote: /usr/src/packages/RPMS/x86_64/lin_tape-1.60.0-1.x86_64.rpm
Executing(%clean): /bin/sh -e /var/tmp/rpm-tmp.91513
...
+ exit 0
```
In this output, notice the following line:

Wrote: /usr/src/packages/RPMS/x86_64/lin_tape-1.60.0-1.x86_64.rpm

The file that is named on this line, /usr/src/packages/RPMS/x86_64/lin_tape-1.60.0-1.x86_64.rpm, is the build package.
Move the built RPM from the Wrote path parameter above to the nodes, and then install.

rpm -ivh lin_tape-1.60.0-1.x86_64.rpm
For a new deployment, refer to the Commvault Expert documentation for detection and configuration. For a pre-existing deployment, do the following:

a. Rescan hardware at the operating system level.

b. At the MediaAgent level in CommServe computer, perform Scan Hardware, followed by Detect Devices, and then reset the library to ensure all access paths are updated correctly if they changed upon install of new driver.

For more information, see Commvault Expert documentation.