On this page:
The CSN distribution is available as a collection of RPM packages that are installed with a shell script. The packages and their dependencies must be installed as the 'root' user from an attached monitor and keyboard with at least one NIC connected to the external network using the following steps. Please reference the Upgrade section for additional steps required for upgrading the software:
1. Copy the distributed zip file to your Cluster Services Node and unzip it into the directory of your choice. The following example command would unzip the version of the software which was previously copied to the /tmp/csninstall directory:
$ sudo su -
# cd /tmp/csninstall
# unzip caringo-csn-2.0.0.zip
Note: The full zip name may include additional descriptive labeling related to versions or distribution channel depending on how the CSN software release is delivered.
2. Install the CSN by running the self-extracting script from the directory location where the shell script was unzipped. For instance, continuing the example above from the /tmp/csninstall directory:
# cd caringo-csn-2.0.0
This command will initiate installation of the CSN and its dependent packages. When the installation is complete, the following prompt will display:
Would you like to proceed with CSN network configuration? (yes/no):
Answer 'yes' to proceed with configuring the CSN. If you answer 'no', you may return to the configuration screen at a later time by running the command: /opt/caringo/csn/bin/firstcsnboot.
If you run the configuration at a later time, it must still be from an attached monitor and keyboard.
Primary CSN Configuration
After installing the CSN, you will automatically be prompted to enter some minimal configuration data to configure the server on the overall network. Network settings are central to all CSN services and should be planned with care in advance by an administrator knowledgeable about the environment. The initial configuration process is only required once after the initial installation. Any necessary subsequent updates to the initial configuration parameters can be made from the CSN Console. Several prompts will suggest a default value in brackets that can be accepted by simply pressing Enter.
Is this the Primary CSN (yes/no)? [yes]:
The above prompt allows specification of whether or not the CSN is a primary or secondary CSN. The default value is yes. Administrators should take care to ensure that only a single primary CSN is configured on the internal network to prevent conflicts with both DHCP and Netmail Store netboot configuration. The primary server must be configured prior to configuration of a secondary. DHCP is not started on the secondary CSN.
Half of the NIC ports on this system will be bonded and assigned to the external network. The following questions configure the external network:
Enter the CSN IP address :
The above parameter requires entry of an external IP address for the CSN node. The entered address must be in a valid w.x.y.z format and must not already be in use on the network.
Enter the cluster IP address. This IP address will remain with the Primary CSN in the event of a CSN failover :
The above parameter requires entry of an external IP address for the CSN cluster address. This well-known address remains with the primary CSN in the event of a failover, meaning the cluster can always be reached at this address. The entered address must be in a valid w.x.y.z format and must not already be in use on the network.
Enter the subnet mask [255.255.255.0]:
The above parameter requires entry of the subnet mask for the external network that corresponds with the entered IP address. The default is 255.255.255.0.
Enter the gateway IP address :
The above parameter requires entry of the gateway associated with the entered IP address for the external interface.
Half of the NIC ports on this system will be bonded and assigned to the internal network. The following questions configure the internal network:
Enter the network address, e.g. 192.168.100.0 (small network), 192.168.0.0, 172.20.0.0 (large network) :
The above parameter allows specification of the network interface that should be used for the internal network. Enter an interface in the format of 192.168.100.0 to use a small interface that will support 128 Netmail Store nodes. Enter an interface in the format of 192.168.0.0 or 172.20.0.0 to use a larger network that will support much larger Netmail Store clusters. The entered interface will be divided between the CSN(s) and privileged applications on the internal network and the Netmail Store nodes. The initial configuration process automatically creates multiple alias IP addresses on the internal network for use by various system services and reserves similar IP addresses for a Secondary CSN.
Enter a list of IP addresses (separated by spaces) for external name servers [126.96.36.199 188.8.131.52]:
The above parameter allows specification of one or more DNS servers for the external interface. Entries must be separated by spaces. Publicly available name servers have been defaulted.
Enter a list of IP addresses or server names (separated by a space) for external time servers [0.pool.ntp.org 1.pool.ntp.org 2.pool.ntp.org]:
The above parameter allows specification of one or more NTP servers for the external interface. The defaults are public NTP servers.
Enter a unique storage cluster name. This name cannot be changed once assigned. A fully qualified domain name is recommended :
The above parameter is used to populate the name of the storage cluster on the admin console as well as in stream metadata for all streams written to the local cluster. The CSN also uses this name to detect all the nodes participating in the cluster. For all of these purposes, the name must be unique. An IANA fully qualified domain name is recommended.
Are these values correct (yes/no)?
This last step allows you to review the values entered for all prompts before submitting them. Answering yes will allow the initial configuration process to proceed with network and service configuration, resulting in a fully functional CSN. Answering no to the final initial configuration prompt will restart the initial configuration script at the first prompt, with the previously entered values populated.
At the completion of a successful initial configuration, the CSN will immediately reboot the server to initialize all services. When the node comes back up all network services will be configured and available including SNMP, syslog, DHCP, DNS, NTP, and firewall. Additionally, the CSN Console will be available, the SCSP Proxy will be configured and started and the Content Router Publisher will be configured and started.
Cabling the Internal and External Interfaces
The initial CSN configuration allocates NICs to the public or private interface by splitting assignment of all detected NICs between the two interfaces. Detected NICs are alternated between assignment to the public interface and assignment to the private interface (public, private, public, etc). This allows general support for different types of hardware but complicates network cabling of the NICs to the correct public or private network switch. To assist in correct cabling, the command line 'ethstatus' script reports current NIC allocation and status. The script can be run after the initial configuration is complete by entering the following at a command line as a root user:
The script will output a 'Public Interfaces' section and a 'Private Interfaces' section, including which NICs are assigned to each interface and the current status of that NIC. Online NICs will show a speed, duplex and link status. NICs that are not cabled will show a 'Speed not detected, Duplex not detected, No link' status. To correctly cable the NICs, simply plug a cable for a particular NIC into the internal or external network switch and check the script output to see if the NIC appears online under the correct interface. If it does not, switch the cable to the other network switch and check the script output again. This information will refresh every second with updated information as you plug or unplug cables from the network. When all configured NICs are online and cabled to the correct interface, press Control-C to exit the script.
Secondary CSN Configuration
Once a Primary CSN has been configured on the network, a Secondary CSN may also be configured. The Secondary only requires entry of a single unique external IP address and identification of the internal interface that is already defined on the Primary. The Secondary will then pull much of its network configuration data from the Primary. To facilitate this, a one-time use of the Primary's root password is required as follows:
Additional information about the network will be obtained from the primary CSN
Please enter the primary csn root password :
Please re-enter the primary csn root password :
Taken from the confirmation at the end of the initial configuration script, the Secondary configuration parameters are simply:
External CSN IP address: 192.168.66.11
Internal network interface: 172.20.20.0
Are these values correct (yes/no)?
Configuring Object Storage Cluster Licensing
Subsequent to rebooting after configuration and prior to booting any storage cluster nodes, the Netmail Store license file you received with your purchased capacity must be published via the Netmail Administration Console. The console allows web-based configuration of all CSN services after the initial network configuration. Please refer tofor a full overview of console capabilities.
To access the Netmail Administration Console, open a standard web browser and enter the IP address of the server where you installed Netmail Store. The Netmail Administration Console can be accessed from any workstation with access to this IP address.
To access the console initially for license publication, enter the following address: http://<CSNExternalIP>:8090. You will be required to authenticate prior to being granted access. The username for the console is admin and the default password is caringo. Once authenticated, click the Licensing tab of the Content Storage object to access the licensing interface.
To correctly publish a license, browse to the location of the license file you received with your published capacity using the Upload New License File field in the licensing user interface. Upload the license. Once the file has been updated, the licensing interface will show the company information populated in the license file as well as a last modified date for the license file.
Note: Netmail Store scans for license updates every 15 minutes so it may be up to that long before a newly published license is registered in a running storage cluster.