FCAT Related Maintenance and Troubleshooting Tasks

The following tasks apply to configurations using the ACSLS Feature Card Availability Toolkit (FCAT) in a dual feature card configuration with ACSLS 8.5.1.

Breaking Trust Between Two Feature Cards

Complete the following steps:

Enter the following command:

fcatServer_clusterizeFeatureCards.sh -d

The following message is displayed:

=============================================================
 
Trust between two feature cards plugged in the same library
form the backbone for ACSLS availability solution on
feature cards as it enables the exchange of data and files between
those two feature cards.
 
ACSLS availability solution for feature card is *not*
possible without trust between the two feature cards.
 
=============================================================
Do you want to break the trust [root : Side-A => Side-B] ? [Y/N] y

At the prompt, enter Y.

The following message is displayed:

root: fcatServer_clusterizeFeatureCards.sh: INFO: A simplex trust [root : Side-A => Side-B] is destroyed.

To ensure that all trusts are removed, run the above command on both Side-A and Side-B feature cards, first as user acsss and then as user root.

Breaking Trust Between the FCAT Client and Feature Cards

Reference the configuration tasks as described in "Configuring the FCAT Environment":

See "Step 7: Remove Existing Trusts Between the FCAT Client and Feature Cards".

Updating Passwords Associated with Feature Cards

Complete the following steps:

Login to the Side-A feature card as user acsss and shut down the feature card:
```
acsss shutdown
```
Repeat the above step for the Side-B feature card.
Remove existing trust between the FCAT Client and feature cards, as described in Using the ACSLS Feature Card Availability Toolkit:

See Step 7: Remove Existing Trusts Between the FCAT Client and Feature Cards.
Remove existing trust between the two feature cards for both user acsss and user root, as described in Breaking Trust Between Two Feature Cards.
Perform your password changes.
Re-create trust between the feature cards, as described in Using the ACSLS Feature Card Availability Toolkit.

See Step 5: Cluster the Feature Cards and Establish Trust.
Re-create trust between the FCAT client and feature cards, as described in Using the ACSLS Feature Card Availability Toolkit:

See Step 8: Configure the FCAT Client to Recognize Both Side-A and Side-B Feature Cards.
Enable ACSLS as user acsss to begin operations:
```
acsss enable
```

Verifying that Trusts are Established Between Feature Cards

Use the fcatClient_featureCardStatus.sh command to verify that trusts are established between the two feature cards installed in the upper two LOC card slots within the same SL4000 library.

If one of the feature cards indicates Unreachable for a given user, then attempt to establish trust again using the fcatServer_clusterizeFeatureCards.sh utility.

If you cannot view both feature cards on the ACSLS Availability Status screen, then verify that you have correctly established trusts in your /root/.ssh/known_hosts file.

Verifying that Database Snapshots are Successfully Replicated

When the FCAT tools are properly configured, the database is automatically replicated between the two feature cards and all four feature storage cards when an ACSLS change results in a database update.

To verify that the backup files and all four feature storage cards are in sync, review the directory /export/backup/ and look for files in the form 2019-05-22_18:13:31.tar. You should see the same set of files for each feature card. Copies are also located on all of the feature storage cards.

Note:

Ensure that the current time for both feature cards is in sync. See Step 2: Sync Time Between Feature Cards and the SL4000.

Troubleshooting Feature Card Tools

All of the fcatClient scripts are certified to run on the OBI Linux release 6.8, 6.10, 7.3, 7.6, 7.8 and 7.9 platforms. Other versions of Unix may require standard porting methods.