Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

This section describes how to install and configure your Swarm CSN on a dedicated node.

...

Prompt

Description

Is this the Primary CSN (yes/no)? [yes]: 

This prompt enables you to specify whether or not the CSN is a primary or secondary CSN. For a review of primary and secondary CSN, see "Primary vs. Secondary" . Make sure that only one primary CSN is configured on the internal network to prevent IP address conflicts as well as conflicts with both DHCP and Swarm netboot configuration. The primary server must be configured prior to configuration of a secondary. DHCP is not started on the secondary CSN.

Is this a single or dual network CSN (single/dual)? [dual] 

Enter whether the CSN should be configured in a 'single' configuration with both the CSN and the storage nodes directly addressable on a single network or in a 'dual' configuration with the storage nodes isolated on an internal network. For a review of dual and single-network configurations, see "Networking" .

Half of the NIC ports on this system will be bonded and assigned to the external network. The following questions configure the external network: 

The following message then displays if you are setting up a Primary CSN.

Enter the CSN IP address []. 

Enter an available IP address on the public network. This is the address you use to access the CSN console and that external clients use to access resources on the internal network (such as the Swarm cluster through the SCSP Proxy). The CSN's IP Address must be within the x.y.z.1 - x.y.z.16 range for the configured subnet. 

Enter the cluster IP address. This IP address will remain with the Primary CSN in the event of a CSN failover []: 

Enter another publicly accessible CSN IP address. (The term cluster here refers to a cluster of CSNs; that is, one primary CSN and one secondary CSN.) 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 IPv4 format and must not already be in use by another host on the network.

Enter the subnet mask [255.255.255.0]: 

Enter the subnet mask for the preceding IP addresses. The default is 255.255.255.0. 

Enter the gateway IP address []: 

Enter the IP address of the default gateway for the preceding IP addresses.

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) []: 

Enter an IP address in your internal network to create an address space for Swarm nodes, third-party servers like DHCP, and other services. Enter the IP address in one of the following formats, depending on your needs:

  • Large network (Class B - more than 128 nodes): Format like 192.168.0.0, 10.10.0.0, or 172.20.0.0

  • Small network (Class C - 128 or fewer nodes): Format like 192.160.100.0, 10.10.100.0, or 172.20.100.0, where the 100 in the third octet limits the number of available IP Addresses in the specified rang

The interface is divided between the CSN(s), privileged applications on the internal network and the Swarm 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. Prompts similar to the following display:

Configuring external/internal ports. This may take some time.
Checking ... eth0 ...eth1 ...eth2 ...eth3 ...
Eth Device | MAC | Public? | Bond
eth0 | 00:0c:29:e2:e6:65 | Y | bond1
eth1 | 00:0c:29:e2:e6:6f | Y | bond1
eth2 | 00:0c:29:e2:e6:79 | N | bond0
eth3 | 00:0c:29:e2:e6:83 | N | bond0
=============================================
Disconnected NICs =
Recommended ethernet device assignment
Internal NICs = eth2 eth3
External NICs = eth0 eth1
Input the list of External NICs.

The preceding shows how CSN suggests you allocate the available NICs by assigning them to internal and external CSN interfaces. The recommendation is based on how the NICs are currently cabled. All NICs that are currently connected to the network display. Any NICs that are not connected to the network display as Disconnected NICs. After you connect them to the network (or if you later need to change NIC assignments), you can assign them to internal or external CSN interfaces. See "Modifying CSN Network Configuration" .

Note: If you answer no to the last configuration prompt asking if the entered values are correct, the interface table displayed on subsequent runs through the configuration prompts will show the values you previously selected for external and internal NICs NOT newly detected values based on any cabling changes.

external nics [space-separated-list]: 

Displays the list of NICs the CSN has determined are for its external interface based upon responses from the external gateway. You can optionally change the list if you want to override the CSN's detection. If the NIC distribution is not as expected and you need to recable the NICs, best practice is to abort the initial configuration script, correct the cabling and then rerun initial configuration using /opt/caringo/csn/bin/firstcsnboot.

Note: If the configured external gateway has ICMP turned off so that it does not respond to ping requests, the CSN will not be able to automatically detect how the NICs are cabled. You will need to manually assign the NICs to either the external or internal interface using the blank prompts.

internal nics [space-separated-list]: 

Displays the list of NICs that CSN has determined are for its internal interface based on lack of response from the external gateway. You can optionally change the list if you want to override the CSN's detection. If the NIC distribution is not as expected and you need to recable the NICs, best practice is to abort the initial configuration script, correct the cabling and then rerun initial configuration using /opt/caringo/csn/bin/firstcsnboot.

Enter a list of IP addresses (separated by spaces) for external name servers [8.8.8.8 8.8.4.4]:

Enter a space-separated list of DNS server IP addresses for the external interface. The default values specify public DNS servers.

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]:

Enter a space-separated list of Network Time Protocol (NTP) server IP addresses or fully qualified host names for the external interface. The default values specify public DNS names from the NTP pool project .

Enter a unique storage cluster name. This name cannot be changed once assigned. A fully qualified domain name is recommended []:

Enter a unique name to identify the Swarm cluster. This value must be unique among all clusters you manage; otherwise, disaster recovery will be problematic. (If the contents of more than one cluster with the same name are written to a single disaster recovery cluster, it will be very difficult to recover the contents later.) DataCore strongly recommends you use a fully qualified IANA domain name (for example, csn.example.com). The name you enter displays as the name of the storage cluster on the CSN Console as well as in metadata for all objects written to the local cluster. The CSN also uses this name to detect all the nodes participating in the cluster.

Enter the multicast group that should be used to uniquely identify the storage cluster on the network. Different storage clusters on the same network must have unique multicast addresses or the nodes will merge into a single cluster (224.0.10.100):

Enter a multicast group address for the storage cluster. Each cluster on the same network must have a unique multicast group address. It must be a Class D IP address in the range 224.0.0.0 - 239.255.255.255.

Are these values correct (yes/no)?

This last step allows you to review the values entered for all prompts before submitting them. Entering yes enables the initial configuration process to proceed with network and service configuration, resulting in a fully functional CSN. Entering no to the final initial configuration prompt restarts the initial configuration script at the first prompt, with the previously entered values populated. Values other than yes or no (case sensitive) are not supported.

Note: After you complete the installation, but before CSN reboots, Fail messages might display. These messages are harmless and can be ignored.

...

The following characters are accepted: letters, numbers, and characters available by pressing Shift on the number keys (!, @, #, and so on).

...

Note

Swarm scans for license updates every 15 minutes; therefore, it may be 15 minutes before a newly published license is registered in a running storage cluster.

Booting Swarm Nodes

Info

Swarm 10 and higher

Swarm 10 introduced two pairs of passwords to manage in the Swarm cluster.cfg file, in the [security] and [snmp] sections. Be sure to set these before booting the nodes. See Defining Swarm Admins, Swarm Users, and Swarm Passwords.

  1. Remove the “snmp” user from the administrators line.

  2. Remove security.operators.

  3. Add snmp.rwCommunity and snmp.roCommunity.

Be aware that the CSN bundle install script may insert deprecated settings that were required for Swarm 9, so always verify these particular settings before booting the nodes.

...