IBM Aspera Shares

https://www.ibm.com/docs/en/aspera-shares
Admin
IBM Aspera Shares is a solution that enables fast, secure, and reliable sharing and collaboration of...
Tokens:229,686
Snippets:1,943
Trust Score:10
Update:10 months ago
Show doc for...
Tokens:
Raw
### Run Shares Setup Script

Source: https://www.ibm.com/docs/en/aspera-shares/1.10_topic=shares-installing-1101

Executes the Shares installation script located in the setup directory. This script performs essential setup operations after the package installation.

```bash
/opt/aspera/shares/u/setup/bin/install
```

--------------------------------

### Start Shares Background Jobs

Source: https://www.ibm.com/docs/en/aspera-shares/1.10_topic=shares-installing-1101

Starts the background job processing for Shares. This script ensures that asynchronous tasks are handled efficiently.

```bash
bash /opt/aspera/shares/u/shares/delayed_jobs.sh start
```

--------------------------------

### Install Aspera Shares Package

Source: https://www.ibm.com/docs/en/aspera-shares/1.10_topic=shares-installing-110

Installs the Aspera Shares package using RPM. Requires root privileges. Replaces existing versions.

```shell
# rpm -Uvh aspera-shares-version.rpm
```

--------------------------------

### Install and Configure IBM Aspera Shares with Console on Same Host (Linux)

Source: https://www.ibm.com/docs/en/aspera-shares/1.9_topic=appendix-installing-hosting-shares-console-same-host

This procedure outlines the steps to install IBM Aspera Shares on the same host as IBM Aspera Console on a Linux system. It requires downloading specific products, installing Shares without immediately running the script, configuring the MySQL connection in 'my.cnf.setup', running the Shares installer, disabling Apache, creating an Nginx symlink, and restarting Nginx.

```bash
# /opt/aspera/shares/u/setup/bin/install
```

```bash
# asctl apache:stop
# asctl apache:disable
```

```bash
# ln -s ../locations-available/console /opt/aspera/shares/etc/nginx/locations-enabled/
```

--------------------------------

### Install Aspera Entitlement Server RPM

Source: https://www.ibm.com/docs/en/aspera-shares/1.10_topic=installation-installing-configuring-ha-environment

Installs the Aspera Entitlement Server package using the rpm command. This is a foundational step for setting up Aspera services.

```shell
# rpm –Uvh aspera-entsrv-version.rpm
```

--------------------------------

### Login to MySQL as Root

Source: https://www.ibm.com/docs/en/aspera-shares/1.10_topic=installation-installing-configuring-ha-environment

Example command to log in to the MySQL server as the root user. It requires specifying the username ('-u'), host ('-h'), and password ('-p'). Note that there is no space between '-p' and the password.

```shell
# /opt/aspera/shares/bin/mysql –uroot –hlocalhost –ppassword
```

--------------------------------

### Verify MySQL Data Directory Permissions

Source: https://www.ibm.com/docs/en/aspera-shares/1.10_topic=installation-installing-configuring-ha-environment

Checks the permissions and symbolic link for the MySQL data directory after migration.

```bash
# ls -lah /opt/aspera/shares/var
drwxr-xr-x  7 root    root  4096  Dec 19  10:01  log
lrwxrwxrwx  1 nobody  root    11  Dec 19  15:14  mysql -> /mysql_data
drwx-----   5 nobody  root  4096  Dec 19  15:12  mysql_bak
...
```

--------------------------------

### ACM Sanity Check with acmctl

Source: https://www.ibm.com/docs/en/aspera-shares/1.10_topic=installation-installing-configuring-ha-environment

This command performs a sanity check on the ACM installation to verify basic prerequisites. It checks symbolic links, crontab entries, service statuses, and SELinux mode.

```bash
# /opt/aspera/acm/bin/acmctl –s
```

--------------------------------

### Test MySQL Login with Aspera User

Source: https://www.ibm.com/docs/en/aspera-shares/1.10_topic=installation-installing-configuring-ha-environment

Tests the ability to log into the MySQL server using the 'aspera' user credentials and the system's IP address.

```bash
# /opt/aspera/shares/bin/mysql –uaspera –hprimary_node_ip_address –ppassword
```

--------------------------------

### OpenSSL Certificate Attribute Prompt Example

Source: https://www.ibm.com/docs/en/aspera-shares/1.10_topic=shares-installing-signed-ssl-certificate-provided-by-authorities

This example demonstrates the interactive prompts from OpenSSL when generating a certificate request. It shows the user input for various X.509 attributes, such as Country Name, State or Province Name, Locality Name, Organization Name, Organizational Unit Name, Common Name, and Email Address. The Common Name is critical for SSL security.

```text
Generating a 1024 bit RSA private key
....................++++++
................++++++
writing new private key to 'my_key_name.key' -----
You are about to be asked to enter information that will be incorporated
into your certificate request.
What you are about to enter is what is called a Distinguished Name or a DN.
There are quite a few fields but you can leave some blank
For some fields there will be a default value,
If you enter '.', the field will be left blank. -----
Country Name (2 letter code) [US]: US
State or Province Name (full name) [Some-State]: CA
Locality Name (eg, city) []: Emeryville
Organization Name (eg, company) [Internet Widgits Pty Ltd]: IBM Aspera
Organizational Unit Name (eg, section) []: ASP
Common Name (i.e., your server's hostname) []: faspex.asperasoft.com
Email Address []: faspex@asperasoft.com

```

--------------------------------

### Create Aspera User and Group

Source: https://www.ibm.com/docs/en/aspera-shares/1.10_topic=installation-installing-configuring-ha-environment

Creates the 'shares' user and group with specific UID and GID, and the 'mysql' user and group. These accounts are required for Aspera Shares operation and must be consistent across all nodes in the HA environment.

```bash
# groupadd -g 777 shares && useradd -c "Aspera Shares" -d /home/shares -g shares -m -s /bin/aspshell -r -u 777 shares
# groupadd -g 778 mysql && useradd -c "Aspera Mysql" -d /home/mysql -g mysql -m -s /bin/false -u 778 mysql
```

--------------------------------

### Configure NFS Mounts in /etc/fstab

Source: https://www.ibm.com/docs/en/aspera-shares/1.10_topic=installation-installing-configuring-ha-environment

Defines how remote file systems (NFS shares) are automatically mounted on system startup. This ensures that shared storage for MySQL data, uploaded files, and ACM files is accessible to all Shares servers.

```bash
10.0.75.10:/export/mysql_data   /mysql_data    nfs4 rw,sync,hard,intr 0 0
10.0.75.10:/export/shares       /shares        nfs4 rw,sync,hard,intr 0 0
10.0.75.10:/export/acm_files    /acm_files     nfs4 rw,sync,hard,intr,noac 0 0
```

--------------------------------

### List Node API Users with Asnodeadmin

Source: https://www.ibm.com/docs/en/aspera-shares/1.10_topic=installation-installing-configuring-ha-environment

Lists all configured Node API users and their associated transfer accounts. This command is used to verify the creation and association of the 'nodeadmin' user.

```shell
# /opt/aspera/bin/asnodeadmin –l
```

--------------------------------

### Run Aspera Shares Upgrade Script (Shell)

Source: https://www.ibm.com/docs/en/aspera-shares/1.10_topic=environment-upgrading-ha

After unpacking the installer, this script must be executed as root to complete the Aspera Shares upgrade. It starts the Shares services, waits for MySQL, and migrates the database and configuration. The script's output indicates the progress of these steps.

```shell
# /opt/aspera/shares/u/setup/bin/upgrade 

  Starting aspera-shares ...
  Started
  Waiting for MySQL server to answer
  mysqld is alive
  Migrating the Shares database ...
  Initializing the Shares database ...
  Clearing background jobs ...
  Migrating the stats collector database ...
  Done
```

--------------------------------

### Configure ACM Symbolic Links and Database Credentials

Source: https://www.ibm.com/docs/en/aspera-shares/1.10_topic=installation-installing-configuring-ha-environment

Sets up symbolic links for ACM configuration files and ensures the database.yml file contains correct node-specific credentials. This integrates ACM with the shared database.

```bash
# ln -s /acm_files/acm /opt/aspera/acm
# cd /opt/aspera/shares/u/shares/config
# mv database.yml database.yml.orig
# ln -s /opt/aspera/acm/config/database.yml database.yml
# cp /opt/aspera/acm/config/database.yml.orig /opt/aspera/acm/config/database.yml
# chown -h nobody.nobody database.yml
```

--------------------------------

### Backup Shares Database with Crontab

Source: https://www.ibm.com/docs/en/aspera-shares/1.10_topic=installation-installing-configuring-ha-environment

This cron job schedules a daily backup of the Shares database using the acmctl -b command. The backup is performed every day at 3:30 AM. Output is redirected to /dev/null.

```bash
# crontab -e
30 3 * * * /opt/aspera/acm/bin/acmctl -b > /dev/null 2>&1
```

--------------------------------

### Start Aspera Node Daemon Service

Source: https://www.ibm.com/docs/en/aspera-shares/1.9_topic=nodes-setting-up-macos-node

Starts the Aspera Node daemon service using launchctl. This command ensures the Aspera services are running on the system.

```bash
# sudo launchctl start com.aspera.asperanoded
```

--------------------------------

### Example acm4shares Crontab Entry

Source: https://www.ibm.com/docs/en/aspera-shares/1.10_topic=installation-installing-configuring-ha-environment

An example of a crontab entry that uses the acm4shares command with a specific IP address (10.0.0.0) and device number (21). Output is discarded.

```bash
# crontab -e
* * * * * /opt/aspera/acm/bin/acm 10.0.0.0 21 /dev/null 2>&1
```

--------------------------------

### Stop Firewall Services

Source: https://www.ibm.com/docs/en/aspera-shares/1.10_topic=installation-installing-configuring-ha-environment

Stops the ip6tables firewall service and disables it from starting on boot. This is a prerequisite for certain network configurations.

```bash
# service ip6tables stop
ip6tables: Flushing firewall rules:        [  OK  ]
ip6tables: Setting chains to policy ACCEPT: filter     [  OK  ]
ip6tables: Unloading modules:  [  OK  ]
# chkconfig iptables off
# chkconfig ip6tables off
```

--------------------------------

### Run IBM Aspera Shares Installer

Source: https://www.ibm.com/docs/en/aspera-shares/1.10_topic=appendix-installing-hosting-shares-console-same-host

This command executes the installation script for IBM Aspera Shares. It is part of the process for installing Shares and Console on the same host. Ensure all prerequisites, including the prior installation of IBM Aspera Console and correct MySQL configuration, are met before running this command.

```bash
# /opt/aspera/shares/u/setup/bin/install
```

--------------------------------

### Stop and Disable Aspera Shares Services

Source: https://www.ibm.com/docs/en/aspera-shares/1.10_topic=installation-installing-configuring-ha-environment

Stops the Aspera Shares service and disables it from starting on boot. This is a preparatory step before managing service files.

```bash
# service aspera-shares stop
# chkconfig aspera-shares off
```

--------------------------------

### Create Working Directory

Source: https://www.ibm.com/docs/en/aspera-shares/1.10_topic=ss-installing-signed-ssl-certificate-provided-by-authorities

Creates a new directory for SSL-related files and navigates into it. This is the first step in preparing the environment for certificate generation.

```batch
> mkdir c:\ssl
> cd c:\ssl
```

--------------------------------

### Get Hostname (Linux)

Source: https://www.ibm.com/docs/en/aspera-shares/1.10_topic=installation-installing-configuring-ha-environment

This command retrieves the hostname of the current system. It is used to verify network settings and ensure each host has a unique, resolvable name, which is crucial for HA environments.

```bash
# hostname
hashares1.mydomain.com
```

--------------------------------

### Create and Verify Node API User for Aspera Shares

Source: https://www.ibm.com/docs/en/aspera-shares/1.9_topic=sutn-setting-up-windows-node

These commands are used to create a Node API user and associate it with a system user for Aspera Shares. The first command adds the user, and the second command lists all users to verify the addition. Ensure you use distinct names for system and transfer users.

```bash
> asnodeadmin -a -u node_api_username -p node_api_passwd -x system_username 
> asnodeadmin -a -u node_user -p XF324cd28 -x xfer_user
```

```bash
> asnodeadmin -l
```

```text
user       system/transfer user                    acls
====================    =======================    ====================
           node_user                  xfer_user                                  
```

--------------------------------

### Disable Local Firewall (Linux)

Source: https://www.ibm.com/docs/en/aspera-shares/1.10_topic=installation-installing-configuring-ha-environment

This command stops the local iptables firewall service and configures it to not start on reboot. This is a prerequisite for setting up HA environments to ensure unrestricted traffic between nodes. It flushes existing rules and sets the policy to ACCEPT.

```bash
# service iptables stop
iptables: Flushing firewall rules:         [  OK  ]
iptables: Setting chains to policy ACCEPT: filter      [  OK  ]
iptables: Unloading modules:   [  OK  ]
```

--------------------------------

### Configure User Data and Docroot with asconfigurator

Source: https://www.ibm.com/docs/en/aspera-shares/1.9_topic=nodes-setting-up-windows-node

Use the `asconfigurator` utility to add a user to the `aspera.conf` file and specify their document root (docroot). The docroot defines the accessible directory for the transfer user. Ensure the path does not contain spaces.

```bash
> asconfigurator -x "set_user_data;user_name,username;absolute,/docroot/path"
```

```bash
> asconfigurator -x "set_user_data;user_name,xfer_user;absolute,/project1"
```

--------------------------------

### Install HST Server Package

Source: https://www.ibm.com/docs/en/aspera-shares/1.10_topic=installation-installing-configuring-ha-environment

Installs the Aspera High Speed Transfer (HST) Server package. This is a prerequisite for configuring servers to function with the Shares Server software in an HA environment.

```bash
# (Installation command for HST Server would go here)
```

--------------------------------

### Install Aspera Shares Package

Source: https://www.ibm.com/docs/en/aspera-shares/1.9_topic=shares-installing

Installs the Aspera Shares package using RPM. This command should be run as root and requires the specific package version. The output shows the progress of the installation.

```shell
[root] # rpm -Uvh aspera-shares-version.rpm
```

--------------------------------

### Create and Verify Node API User for Aspera Shares

Source: https://www.ibm.com/docs/en/aspera-shares/1.9_topic=nodes-setting-up-windows-node

Commands to create a Node API user and associate it with a system user, followed by a command to list all Node API users to verify successful addition. This ensures the transfer user account is correctly set up for authentication.

```bash
> asnodeadmin -a -u node_api_username -p node_api_passwd -x system_username 
> asnodeadmin -a -u node_user -p XF324cd28 -x xfer_user 
> asnodeadmin -l
```

--------------------------------

### OpenSSL Certificate Attribute Prompts

Source: https://www.ibm.com/docs/en/aspera-shares/1.9_topic=shares-installing-signed-ssl-certificate-provided-by-authorities

This is an example of the interactive prompts generated by the OpenSSL command when creating a CSR. It guides the user to enter details like Country Name, State, Locality, Organization, Common Name (server's hostname), and Email Address. The Common Name is critical for SSL protection.

```text
Generating a 1024 bit RSA private key
....................++++++
................++++++
writing new private key to 'my_key_name.key'
-----
You are about to be asked to enter information that will be incorporated
into your certificate request.
What you are about to enter is what is called a Distinguished Name or a DN.
There are quite a few fields but you can leave some blank
For some fields there will be a default value,
If you enter '.', the field will be left blank.
-----
Country Name (2 letter code) [US]: US
State or Province Name (full name) [Some-State]: CA
Locality Name (eg, city) []: Emeryville
Organization Name (eg, company) [Internet Widgits Pty Ltd]: IBM Aspera
Organizational Unit Name (eg, section) []: ASP
Common Name (i.e., your server's hostname) []: faspex.asperasoft.com
Email Address []: faspex@asperasoft.com
```

--------------------------------

### Verify IBM Aspera High-Speed Transfer Server License (Linux)

Source: https://www.ibm.com/docs/en/aspera-shares/1.10_topic=nodes-setting-up-linux-node

This command verifies that the IBM Aspera High-Speed Transfer Server is installed and has a valid license on the transfer server. Shares requires nodes to use a Connect Server license.

```bash
# ascp -A
```

--------------------------------

### Check SELinux Status

Source: https://www.ibm.com/docs/en/aspera-shares/1.10_topic=shares-installing-110

This command checks the current status of SELinux. SELinux must be set to 'permissive' or 'disabled' for installation. If it is 'enforced', refer to the documentation for disabling it.

```bash
# sestatus

```

--------------------------------

### Run Shares Installer (Linux)

Source: https://www.ibm.com/docs/en/aspera-shares/1.10_topic=appendix-installing-hosting-shares-faspex-4-same-host

This command executes the IBM Aspera Shares installer script. It is a crucial step after configuring the MySQL settings, ensuring the Shares application is properly set up on the host.

```bash
# /opt/aspera/shares/u/setup/bin/install

```

--------------------------------

### Exit MySQL Client

Source: https://www.ibm.com/docs/en/aspera-shares/1.10_topic=installation-installing-configuring-ha-environment

Exits the MySQL command-line client session.

```mysql
mysql> quit
```

--------------------------------

### List Aspera Node API Users

Source: https://www.ibm.com/docs/en/aspera-shares/1.9_topic=nodes-setting-up-macos-node

Lists all configured Node API users and their associated system/transfer users. Used to verify successful addition of a user.

```bash
# /Library/Aspera/bin/asnodeadmin -l
```

--------------------------------

### Install Shares RPM Package

Source: https://www.ibm.com/docs/en/aspera-shares/1.10_topic=shares-installing-1101

Installs the IBM Aspera Shares RPM package. Ensure you have the correct package file name. This is the initial step for setting up Shares.

```bash
rpm -Uvh <package>
```

--------------------------------

### Backup IBM Aspera Shares Installation

Source: https://www.ibm.com/docs/en/aspera-shares/1.10_topic=shares-upgrading-from-110-1101

Creates a backup of the current IBM Aspera Shares installation. This command should be executed before starting the upgrade process to ensure data recovery in case of issues. The backup file will be stored in the /tmp directory.

```bash
/opt/aspera/shares/u/setup/bin/backup /tmp
```

--------------------------------

### Verify Aspera Installation (Windows)

Source: https://www.ibm.com/docs/en/aspera-shares/1.10_topic=sutn-setting-up-windows-node

This command verifies that the IBM Aspera High-Speed Transfer Server is installed and licensed on the transfer server. It's a prerequisite for setting up Shares.

```shell
> ascp -A
```

--------------------------------

### Check Aspera Shares Service Status

Source: https://www.ibm.com/docs/en/aspera-shares/1.10_topic=installation-installing-configuring-ha-environment

Checks the current status of the Aspera Shares service to confirm it has been stopped.

```bash
# service aspera-shares status
Checking status of aspera-shares ...
Status is stopped
```

--------------------------------

### Example of Rake Task Destination Directory (Shell)

Source: https://www.ibm.com/docs/en/aspera-shares/1.9_topic=database-backing-up-shares

Provides an example of how to specify a destination directory for a rake task backup. It highlights that the rake task runs as an unprivileged user, requiring the destination directory to be writable by all users. The recommended directory is /tmp.

```bash
# Ensure ensure the destination directory is writable by all users. Aspera recommends using /tmp.
# For example: 
```

--------------------------------

### Restart SSH Service

Source: https://www.ibm.com/docs/en/aspera-shares/1.10_topic=installation-installing-configuring-ha-environment

Restarts the SSH daemon to apply changes made to the sshd_config file, such as enabling public key authentication.

```bash
# service sshd restart
```

--------------------------------

### Example Signed SAML Authentication Request Configuration

Source: https://www.ibm.com/docs/en/aspera-shares/1.10_topic=saml-configuring-signed-authentication-requests

An example of a fully configured saml.yml section for signed SAML authentication requests, including a sample SSL certificate and private key. This demonstrates the expected format for these values.

```yaml
EnableSignedAuthnRequests: true 
AuthnDigestMethod: XMLSecurity::Document::SHA1
AuthnSignatureMethod: XMLSecurity::Document::RSA_SHA256
AuthnCertificate: >
-----BEGIN CERTIFICATE-----
MIICKzCCAZSgAwIBAgIBAzANBgkqhkiG9w0BAQQFADA3MQswCQYDVQQGEwJVUzER
MA8GA1UEChMITmV0c2NhcGUxFTATBgNVBAsTDFN1cHJpeWEncyBDQTAeFw05NzEw
MTgwMTM2MjVaFw05OTEwMTgwMTM2MjVaMEgxCzAJBgNVBAYTAlVTMREwDwYDVQQK
EwhOZXRzY2FwZTENMAsGA1UECxMEUHViczEXMBUGA1UEAxMOU3Vwcml5YSBTaGV0
dHkwgZ8wDQYJKoZIhvcNAQEFBQADgY0AMIGJAoGBAMr6eZiPGfjX3uRJgEjmKiqG
7SdATYazBcABu1AVyd7chRkiQ31FbXFOGD3wNktbf6hRo6EAmM5/R1AskzZ8AW7L
iQZBcrXpc0k4du+2Q6xJu2MPm/8WKuMOnTuvzpo+SGXelmHVChEqooCwfdiZywyZ
NMmrJgaoMa2MS6pUkfQVAgMBAAGjNjA0MBEGCWCGSAGG+EIBAQQEAwIAgDAfBgNV
HSMEGDAWgBTy8gZZkBhHUfWJM1oxeuZc+zYmyTANBgkqhkiG9w0BAQQFAAOBgQBt
I6/z07Z635DfzX4XbAFpjlRl/AYwQzTSYx8GfcNAqCqCwaSDKvsuj/vwbf91o3j3
UkdGYpcd2cYRCgKi4MwqdWyLtpuHAH18hHZ5uvi00mJYw8W2wUOsY0RC/a/IDy84
hW3WWehBUqVK5SY4/zJ4oTjx7dwNMdGwbWfpRqjd1A==
-----END CERTIFICATE-----
AuthnPrivateKey: >
-----BEGIN RSA PRIVATE KEY-----
MIICXAIBAAKBgQCVqGpH2S7F0CbEmQBgmbiDiOOGxhVwlG+yY/6OBQoPKcx4Jv2h
vLz7r54ngjaIqnqRNP7ljKjFLp5zhnAu9GsdwXbgLPtrmMSB+MVFHTJvKjQ+eY9p
dWA3NbQusM9uf8dArm+3VrZxNHQbVGXOIAPNHTO08cZHMSqIDQ6OvLma7wIDAQAB
AoGAbxKPzsNh826JV2A253svdnAibeSWBPgl7kBIrR8QWDCtkH9fvqpVmHa+6pO5
5bShQyQSCkxa9f2jnBorKK4+0K412TBM/SG6Zjw+DsZd6VuoZ7P027msTWQrMBxg
Hjgs7FSFtj76HQ0OZxFeZ8BkIYq0w+7VQYAPBWEPSqCRQAECQQDv09M4PyRVWSQM
S8Rmf/jBWmRnY1gPPEOZDOiSWJqIBZUBznvOPOOQSH6B+vee/q5edQA2OIaDgNmn
AurEtUaRAkEAn7/65w+Tewr89mOM0RKMVpFpwNfGYAj3kT1mFEYDq+iNWdcSE6xE
2H0w3YEbDsSayxc36efFnmr//4ljt4iJfwJAa1pOeicJhIracAaaa6dtGl/0AbOe
f3NibugwUxIGWkzlXmGnWbI3yyYoOta0cR9fvjhxV9QFomfTBcdwf40FgQJAH3MG
DBMO77w8DK2QfWBvbGN4NFTGYwWg52D1Bay68E759OPYVTMm4o/S3Oib0Q53gt/x
TAUq7IMYHtCHZwxkNQJBAORwE+6qVIv/ZSP2tHLYf8DGOhEBJtQcVjE7PfUjAbH5
lr++9qUfv0S13gXj5weio5dzgEXwWdX2YSL/asz5DhU=
-----END RSA PRIVATE KEY-----
```

--------------------------------

### Copy MySQL Backup to Shared Volume

Source: https://www.ibm.com/docs/en/aspera-shares/1.10_topic=installation-installing-configuring-ha-environment

Copies the backed-up MySQL data from the previous location to the new shared MySQL data directory.

```bash
# cp -Rp /opt/aspera/shares/var/mysql_bak/* /opt/aspera/shares/var/mysql
```

--------------------------------

### Check SELinux Status

Source: https://www.ibm.com/docs/en/aspera-shares/1.10_topic=installation-installing-configuring-ha-environment

Displays the current status of SELinux. SELinux must be disabled or set to permissive mode for Aspera Shares to function correctly.

```bash
# sestatus
SELinux status: disabled
```

--------------------------------

### Disable iptables and ip6tables Services

Source: https://www.ibm.com/docs/en/aspera-shares/1.9_topic=installation-installing-configuring-ha-environment

This command disables the iptables and ip6tables services from starting automatically on system boot. This ensures the firewall remains inactive.

```bash
# chkconfig iptables off
# chkconfig ip6tables off
```

--------------------------------

### Configure MySQL Credentials for Shares Installation (Linux)

Source: https://www.ibm.com/docs/en/aspera-shares/1.10_topic=appendix-installing-hosting-shares-faspex-4-same-host

This snippet shows how to edit the my.cnf.setup file to provide MySQL credentials used during Faspex installation. This ensures Shares can connect to the existing MySQL instance hosted by Faspex, setting the host to 127.0.0.1 and specifying the correct port.

```text
[client]
user     = mysql_username
password = mysql_password
host     = 127.0.0.1
port     = 4406                

```

--------------------------------

### Determine IP Address

Source: https://www.ibm.com/docs/en/aspera-shares/1.10_topic=installation-installing-configuring-ha-environment

This command lists the network interfaces and their assigned IP addresses. It is used to identify the local IP address required for the acm4shares command.

```bash
# ip addr | grep "inet"
```

--------------------------------

### Run Aspera Shares Admin Command

Source: https://www.ibm.com/docs/en/aspera-shares/1.10_topic=shares-first-log-in-licensing

Executes the Aspera Shares administration command to set up an admin user. Requires specifying the admin username, password, and email address.

```shell
/opt/aspera/shares/u/shares/bin/run rake aspera:admin NAME="admin_username" PASSWORD="password" EMAIL="email_address"
```

--------------------------------

### List Node API Users with asnodeadmin

Source: https://www.ibm.com/docs/en/aspera-shares/1.10_topic=sutn-setting-up-windows-node

This command verifies that the system user has been successfully added to the asnodeadmin list. It displays a list of configured users, their associated system/transfer users, and their access control lists (ACLs).

```bash
> asnodeadmin -l
```

--------------------------------

### Configure SSH Public Key Authentication

Source: https://www.ibm.com/docs/en/aspera-shares/1.10_topic=installation-installing-configuring-ha-environment

Ensures that public key authentication is enabled in the SSH server configuration. This is crucial for secure communication between servers in the HA environment.

```bash
PubkeyAuthentication yes
```

--------------------------------

### Run Aspera Shares Upgrade Script

Source: https://www.ibm.com/docs/en/aspera-shares/1.9_topic=shares-upgrading

Executes the upgrade script for Aspera Shares after the package installation. This script migrates the database, initializes settings, and restarts services.

```shell
# /opt/aspera/shares/u/setup/bin/upgrade
```
Tokens:
Raw