Configuring the Feature Card and Preparing for ACSLS Installation

Step 1: Connect User Equipment

Connect your user equipment to the library using one of the options described in User Equipment.

If you are using User Equipment Option 1 or have not yet downloaded the ACSLS software bundle onto a flash drive, then proceed with Step 2: Establish a Temporary Connection to the External Network below.
If you are using User Equipment Option 2, ensure that you have downloaded the ACSLS software bundle to your laptop or flash drive. Then proceed with Step 4: Extract the ACSLS Feature Card Scripts.

Step 2: Establish a Temporary Connection to the External Network

To establish the network connection:

If you have not already done so, log in to the feature card as user root.
Gather the following details for your newly initialized feature card. These are defined and assigned by your System Administrator, and will be associated with the feature card in these steps.
- IP address <IP_BOND3>
  
  Note:
  This is the Customer Network Interface IP (i.e. "public") address.
- Netmask <NM>
- Gateway address <IP_GW>
Using vi or your favorite text editor, edit and update the Internet configuration file for port /etc/sysconfig/network-scripts/ifcfg-p4p3 as follows, and then save your updated settings.
Note:
Remember to make a copy of the original file first.
```
DEVICE=p4p3
TYPE=Ethernet
USERCTL=no
NM_CONTROLLED=no
BOOTPROTO=static
IPV6INIT=no
ONBOOT=yes
IPADDR=<IP_BOND3>
NETMASK=<NM>
GATEWAY=<IP_GW>
```

Enable the p4p3 communication port:

ifconfig p4p3 <IP_BOND3> netmask <NM> up; route add default gw <IP_GW> p4p3

Using vi or your favorite text editor, edit and update the /etc/resolv.conf file as follows, and then save your updated settings.
Note:
Remember to make a copy of the original file first.
```
domain <currentDomain>                 	  search <searchDomain> <currentDomain>	  nameserver <dns1_IP>  	nameserver <dns2_IP>   	nameserver <dns3_IP>
```
The <currentDomain> is your site's domain suffix, which may already be included in the file. Otherwise, you must ask your local System Administrator. The second and third nameserver entries are optional depending on whether your site provides multiple nameservers.
Ping the feature card to verify that the IP address is successfully configured. If there is no response then the connection has not been successfully established.
```
ping <IP_BOND3>
```

Step 3: Download the ACSLS Software Bundle

On the feature card, download the latest bundle ACSLS_8.5.1-X.Y_Linux.zip from the Oracle Software Delivery Cloud website.

This step may require the Firefox browser (already installed on the feature card) or another terminal window to allow the download process to be monitored and guided.

Use the Firefox browser on the feature card to download ACSLS software.

From your login shell, enter the command firefox &.
The Firefox browser is displayed on your desktop machine.
Once Firefox launches, configure your local network proxy preferences:
1. Click the open menu icon at the top right of the browser, then select preferences.
2. From the menu in the left-hand frame, select Advanced, then Network, then Connection Settings.
3. From the pop-up menu, select or define the appropriate proxy for your local network environment.
Set the download location for the ACSLS software bundle to /root/Downloads.
1. Click the open menu icon at the top right of the browser, then select preferences.
2. From the menu in the left-hand frame, select General.
3. Under Downloads in the right frame, make sure the Save files to radio button is selected.
4. To the right of the radio button, click Browse and select File System from the left-hand frame.
5. From the right-hand frame, select the root folder, then select Downloads, and click the open button at the bottom of the frame.
The display under Downloads should show the selection, Save files to /root/Downloads.
In the Firefox browser, navigate to the Oracle Software Delivery Cloud. If the Oracle Cloud is not displayed, navigate to the Oracle Software Delivery Cloud at the following URL and follow the steps listed below.
https://edelivery.oracle.com
1. Click Sign In.
2. Enter the user name and password provided by Oracle support.
3. If offered, click Accept on the Export Restrictions screen.
4. Select Download Package from the menu.
5. Type ACSLS in the text box and click Search.
6. Select the resulting product version you desire, and it will be added to your cart.
7. Select Checkout from the upper right to display the Checkout screen.
8. Under Platform/Languages, click the menu and select Linux x86-64. Then click Continue.
9. On the Oracle Terms and Restrictions Screen, review and accept the terms of the licenses by checking the box and clicking Continue.
10. Download your individual packages by clicking on each name.
Once the ACSLS software download is complete, you must perform the following steps to close the temporary connection and to place the system in the correct state for the remaining configuration steps to succeed:
1. Enter the following command to disable the port:
```
ifdown p4p3
```
2. Restore the original /etc/resolv.conf file and remove all copies or backups of it from that directory.
3. Restore the original /etc/sysconfig/network-scripts/ifcfg-p4p3 file, and remove all copies or backups of it from that directory.

Step 4: Extract the ACSLS Feature Card Scripts

To extract the ACSLS software and associated scripts:

Clean up any previous downloads and installs to ensure the latest release is used. To do this, remove any previously downloaded versions of ACSLS 8.5.0 or 8.5.1 from the /tmp directory:
```
cd /tmp
rm -rf ACSLS_8.5.0*
rm -rf ACSLS_8_5_1*
```
Additionally, if the directory /opt/ACSLS exists, remove any previously downloaded versions of ACSLS 8.5.0 or 8.5.1:
```
cd /opt/ACSLS
rm -rf ACSLS_8.5.0*
rm -rf ACSLS_8_5_1*
```
Copy the ACSLS download bundle from your download location of /root/Downloads or from your USB flash drive, into the feature card /tmp directory.
For example, to copy the bundle from the Downloads directory to the /tmp directory:
```
cp /root/Downloads/<ACSLS_bundle_name>.zip /tmp
```
Note:
If you are using a USB flash drive for the download, remove the flash drive from the library once the download is complete.
Once the ACSLS download bundle is in /tmp, unzip the bundle to extract the file fc_config_scripts.zip. This file contains the ACSLS feature card scripts.
```
unzip –x <ACSLS_bundle_name>.zip ACSLS_8.5.1/fc_config_scripts.zip
```
Note:
fc indicates "feature card" and should not be confused with "fibre channel".

Ensure that the file fc_config_scripts.zip has been extracted to the directory /tmp/ACSLS_8.5.1.
```
ls –alt /tmp/ACSLS_8.5.1
```
The file fc_config_scripts.zip should appear in the directory listing for /tmp/ACSLS_8.5.1.
Extract the file featureCard_unzipper.sh from the fc_config_scripts.zip file in the directory /tmp/ACSLS_8.5.1:
```
cd /tmp/ACSLS_8.5.1unzip –x fc_config_scripts.zip featureCard_unzipper.sh
```
The following files should now appear in a directory listing for /tmp/ACSLS_8.5.1:
```
fc_config_scripts.zipfeatureCard_unzipper.sh
```
As user root, execute the featureCard_unzipper.sh utility to automatically transfer the extracted files to their final locations on the ACSLS feature card. This utility also validates that you are installing on a supported SL4000 firmware version of the feature card.
```
./featureCard_unzipper.sh
```
You should see a message similar to the following:
```
The version of SL4000 Firmware hosted on feature card is '1.0.2.X.Y'.ACSLS can be installed on this feature card.
```
After running featureCard_unzipper.sh, verify the presence of the extracted files in the directory /usr/local/bin.
```
ls -alt /usr/local/bin
```
The following files should appear, among others:
```
featureCard_acslsStorageManager.shfeatureCard_bond3.shfeatureCard_hostname.shfeatureCard_resolvconf.sh
```
Verify the presence of the extracted files in the directory /etc/init.d.
```
ls -alt /etc/init.d/
```
The following files should appear:
```
bootCounterFCmountFileSystemsFCstartupCheckFC
```
FC indicates that these services support ACSLS running on the feature card. These services are designed to run in the background.

Step 5: Configure the Feature Card for Bond3 Network Connectivity

Note:

The bond3 network is the default network configuration for ACSLS on the feature card. Optionally, you can customize the network configuration settings to suit your network infrastructure.

To configure the feature card with the bond3 Customer Network Interface as user root:

Go to the repository directory of the feature card configuration scripts.
```
cd /usr/local/bin
```
Use the ifconfig command to verify that the bond3 network does not already exist.
If it exists, then disable the bond3 network interface of the feature card using the following command:
```
./featureCard_bond3.sh –d
```
This disables the ports for the remaining steps, and should not be required on a newly initialized feature card.

Note:
Stop any applications currently running on the feature card.
Enter the following command to establish the ifcfg files for port p4p1, port p4p3, and bond3:
```
./featureCard_bond3 -c <IP_BOND3> <IP_GW> [NM]
```
where:
- IP address <IP_BOND3>
- Gateway address <IP_GW>
- Netmask <NM>
Verify the contents of directory /etc/sysconfig/network-scripts by listing the ifcfg file in the directory:
```
ls -alt /etc/sysconfig/network-scripts
```
Verify that the following files appear:
```
ifcfg-p4p3
ifcfg-p4p1
```
Note:
The file ifcfg-bond3 does not appear, as it is currently disabled.
Verify that configuration entries exist for ports p4p1 and p4p3, and the bond3 network interface on the feature card. This will show both enabled and disabled ports.
```
ifconfig -a
```
The script featureCard_bond3.sh sets up the bond3 external network interface on the feature card which ACSLS will use for its operation. Next, enable the bond3 network interface:
```
./featureCard_bond3.sh -e
```
Verify that the feature card can now be pinged from outside the library or from the Library Controller card.
```
ping <IP_BOND3>
```

Step 6: Configure the Feature Card with DNS Servers and Other Required Settings

To configure the feature card with your DNS servers:

Contact your System Administrator to obtain DNS server IP addresses, a local domain name, and the search list. This information will be used to update /etc/resolv.conf with your new feature card settings.

You must have a minimum of one DNS server IP address. The maximum is three.
The script featureCard_resolvconf.sh sets up the following for the feature card:
- DNS servers, <DNS1_IP> [DNS2_IP] [DNS3_IP]
- Domain name, <DOMAINNAME>
- One or more search domains, <SEARCHDomain1> …[SEARCHDomainN]
The feature card configuration scripts are found in directory /usr/local/bin.
Set up and verify the DNS servers (domain name servers) for the feature card.
```
./featureCard_resolvconf.sh -dns <DNS1_IP> [DNS2_IP] [DNS3_IP]
```
If not satisfied, then revert the change, as follows, before making another change.
```
./featureCard_resolvconf.sh -revert
```
Note that you can only revert the very last change.
Once you are satisfied with the DNS server settings, then set up and verify the Domain Name <domainName> setting for /etc/resolv.conf on the feature card.
```
./featureCard_resolvconf.sh -domain <domainName>
```
If not satisfied, then revert the change, as follows, before making another change.
```
./featureCard_resolvconf.sh -revert
```
Note that you can only revert the very last change.
Once you are satisfied with the Domain Name setting, then set up the Search Domain list, <searchDomain1> … [searchDomainN], for /etc/resolv.conf on the feature card.
```
./featureCard_resolvconf.sh -search <searchDomain1> … [searchDomainN]
```
If not satisfied, then revert the change, as follows, before making another change.
```
./featureCard_resolvconf.sh -revert
```
Note that you can only revert the very last change.
Note:
Once the DNS servers and other required settings are configured, the resolv.conf file will be made immutable to ensure that the settings are not accidentally overwritten. If you need to update this file, use the same procedure as outlined in this section. Otherwise, to make changes to this file you may need to remove and re-enable the immutable attribute of the file: Use the following commands:
```
chattr -i /etc/resolv.conf
<make changes using your favorite editor>
chattr +i /etc/resolv.conf
```
When finished, ensure that you make the file immutable again.

Step 7: Configure the Feature Card Host Name

The script featureCard_hostname.sh changes the default host name of the feature card so that host applications can identify through the host name and communicate with ACSLS running on the feature card.

Assign a new host name to the feature card. This host name should be registered with DNS lookup or LDAP for your organization so that the feature card can be accessed by the ACSLS host applications as proper server.
```
./featureCard_hostname.sh <FC_HOSTNAME>
```
where FC indicates the feature card.

FC_HOSTNAME must be comprised of standard characters:
- a-z
- A-Z
- 0-9
- - (hyphen)
- . (period)
An _ (underscore) and other non-standard characters cannot be used.
After running featureCard_hostname.sh, verify that the /etc/hosts file contains the following.
```
<IP_BOND3>	 <FC_HOSTNAME>
```
Verify that the feature card can now be pinged by <FC_HOSTNAME> from outside the library or from the Library Controller card:
```
ping <FC_HOSTNAME>
```

Step 8: Initialize and Configure the Storage Cards

The factory shipped library storage cards require initialization and configuration to be used in conjunction with the feature card. Configuration is specific to the application that is to be installed on the feature card. Do not use an SDP2 storage card configuration script for the ACSLS application, or vice versa. The configuration scripts are unique to the application and will cause faults if used otherwise.To initialize and configure the storage cards using the Feature Card Kit 1 location:

Ensure that the feature storage cards have been installed by Oracle Support and are running. See Step 5: Insert and Initialize All Feature Storage Cards.
From the feature card, as user root, run the following command to configure the storage for ACSLS on the feature card:
```
cd /usr/local/bin./featureCard_acslsStorageManager.sh
```
As part of this process, RAID storage is mirrored. Watch the output on the screen to see it complete with a success message.
To see more detail during, or after this process, use the following command:
```
cat /proc/mdstat
```
This command displays the configuration definition of the RAID mirror created by the featureCard_acslsStorageManager.sh command.

Step 9: Verify Storage Card Configuration

Once the featureCard_acslsStorageManager.sh script completes, the storage cards are configured. Verify this as follows:

Use df and the specific ls command below to verify file system configuration. Output should appear similar to the following:

# df
Filesystem     1K-blocks     Used Available Use% Mounted on
/dev/sdX3       16382888  6755128   8772516  44% /
tmpfs            8037336       76   8037260   1% /dev/shm
/dev/sdX1         499656    74812    388148  17% /boot
/dev/sdX2       65924860 10267712  52285324  17% /u01
/dev/sdX6       16382888   467952  15059692   4% /var
/dev/sdY1       47929224  1271936  44215920   3% /bkupa
/dev/sdZ1       47929224  1271936  44215920   3% /bkupb
/dev/mdN       191986276  3929464 178297736   3% /export
#
# ls -al /bkupc
lrwxrwxrwx 1 root root 10 Sep 24 20:51 /bkupc -> /u01/bkupc
#

Note:

sdX, sdY, and sdZ, may be sda, sdb, sdc, sdd, or some other name, as determined by Linux. sdX refers to the SSD on the feature card; and /bkupc is also located on the SSD. sdY and sdZ refer to the hard drives on the storage cards.
mdN may be md1 or md2, depending upon whether you have installed the feature card in the Side-A (md1) or Side-B (md2) location within the SL4000 Base Card Cage.

Alternatively you might use lsblk to readily see the partitions and mirrors. For example:

# lsblk
NAME    MAJ:MIN RM   SIZE RO TYPE  MOUNTPOINT
sdX       8:0    0 111.8G  0 disk
  sdX1    8:1    0   512M  0 part  /boot
  sdX2    8:2    0    64G  0 part  /u01
  sdX3    8:3    0    16G  0 part  /
  sdX4    8:4    0     1K  0 part
  sdX5    8:5    0     8G  0 part  [SWAP]
  sdX6    8:6    0    16G  0 part  /var
sdY       8:32   0 558.9G  0 disk
  sdY1    8:33   0  46.6G  0 part  /bkupa
  sdY2    8:34   0 186.3G  0 part
    mdN   9:2    0 186.1G  0 raid1 /export
sdZ       8:48   0 558.9G  0 disk
  sdZ1    8:49   0  46.6G  0 part  /bkupb
  sdZ2    8:50   0 186.3G  0 part
    mdN   9:2    0 186.1G  0 raid1 /export

Note:

In some cases, the featureCard_acslsStorageManager.sh script may need to reconfigure or otherwise perform cleanup, and ask you to reboot. Please reboot as directed. Once the system reboots, open a terminal window and run that script again so it can complete its work. See Step 8: Initialize and Configure the Storage Cards.

The configuration setup leverages the two attached disk drives (/dev/sdY and /dev/sdZ in the example above) to do the following:

Formats both storage cards, each with a single 200GB partition for ACSLS data.
Pairs the two disks into a RAID-1 configuration as device /dev/md1 (or /dev/md2).
Mounts /dev/md1 (or /dev/md2) to /export.
Mounts the RAID device.
Creates two 50GB partitions for assorted backup files, sdY2 and sdZ2, including a copy of ACSLS_8.5.1.X.Y_Linux.zip.
Creates the directories /export/home, /export/backup, /export/PACKAGE, and /opt/ACSLS, if not already present.

Oracle recommends that you label the feature card and the two feature storage cards using an external label. If you remove these components for servicing or other reasons, ensure that you replace them in the locations from which they were removed. Example labels might be:

For Feature Card Kit 1: Feature Card Left –Side-A, Storage Card Left 1, Storage Card Left 2
For Feature Card Kit 2: Feature Card Right –Side-B, Storage Card Right 1, Storage Card Right 2

Step 10: Extract the ACSLS Software Bundle

To extract the ACSLS software:

If you have previously attempted to install ACSLS on the feature card, you may have extraneous files remaining. Ensure that no previously downloaded versions of ACSLS are present.
You may not have directories ACSLS_8.5.0 or ACSLS_8.5.1, depending on whether any previous ACSLS installations were performed on the feature card and not subsequently removed.

To remove previous versions of ACSLS:
```
cd /opt/ACSLS
rm -rf ACSLS_8.5.0*
rm -rf ACSLS_8_5_1*
```
Copy the ACSLS download bundle from the feature card directory of /tmp to the ACSLS installation area. For example, to copy from the location /tmp to /opt/ACSLS:
```
cp /tmp/ACSLS_8.5.1.X.Y.Linux.zip /opt/ACSLS
```
Unzip the ACSLS bundle:
```
unzip ACSLS_8.5.1.X.Y.Linux.zip
```
The ACSLS 8.5.1 files are extracted to the directory /opt/ACSLS/ACSLS_8.5.1.

Verify the presence of the extracted files in the directory /opt/ACSLS/ACSLS_8.5.1.

ls /opt/ACSLS/ACSLS_8.5.1

The following files should appear, amongst others:

ACSLS-8.5.1-X.Y.x86_64.rpm
fc_config_scripts.zip
pkg_install.sh
pkg_uninstall.sh
PostgreSQL-10.5-0-OL6.x86_64.rpm
PostgreSQL-10.5-0-OL7.x86_64.rpm
public-yum-ol6.repo
public-yum-ol7.repo
README.txt
wlUpdate

Once you have confirmed that all files are readily available, you can then remove any copies of the ACSLS_8.5.1-X.Y.Linux.zip from /tmp and /root/Downloads.