| Table of Contents | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
| Info |
|---|
ImportantWhen using SCS 1.5.x or later with Swarm 15.3, the process for configuring static IP addresses is greatly simplified. Carefully select the correct set of instructions for your environment. |
...
Assigning Pre-Defined IP Addresses to Storage Nodes
Static In version 1.6, static IP address assignment is enabled by default in 1.6enabled. SCS supports the same automatic assignment of static IP addresses to nodes , but adds the additional ability to manually assign static IP addresses.
New
...
Installations
Follow the normal installation procedures for both SCS and the Swarm Storage bundle for SCS, including a run of scsctl diagnostics config scan_missing at the end.
Initialize DHCP with the desired lower and upper reserved ranges.
scsctl init dhcp --dhcp-reserve-lower {size_of_lower_range} --dhcp-reserve-upper {size_of_upper_range}
Verify the following:
dhcpd.confonly mentions a single pool of IP addressesscsctl storage config show -d "network.useStaticAddresses"should show a value of true. This is required for both automatic as well as and manual assignment of static IP addresses
Assigning
...
Pre-Defined Static IP Addresses
Before assigning static IP addresses, you need to list the storage nodes and record their chassis IDs.
| Info |
|---|
ImportantIf the nodes have not been booted previously, boot the cluster in the dynamic IP assignment mode so the SCS has a record of the storage instances |
...
. Make a list of the instances once the entire cluster is up and running. |
scsctl storage instance list
Once you have made a list of the the storage node chassis and their desired IP assignments, use the following command to set the static IP address for each node.:
scsctl storage config set -d -i {chassis ID} "network.ipV4Address={your.static.address.here}"
| Info |
|---|
RequiredIf the storage cluster was previously using static IP addresses defined in a previous version of SCS (1.5 or earlier), remove the customized node.cfg files for each storage node. Review any other customizations made that do not relate to manual IP address assignment.
|
The final step is to reboot the cluster and confirm that the storage nodes have the desired IP addresses.
scsctl storage instance list
SCS 1.5.1
| Infonote |
|---|
This section ONLY only applies to Swarm 15.3 or later running on SCS 1.5.1. For environments running earlier versions of either, please see SCS 1.4 and Earlier. |
Beginning Static IP address assignment is by default enabled, beginning with SCS 1.5 and Swarm 15.3, static IP address assignment is enabled by default. However, the process to ensure correct behavior differs somewhat based on whether the environment is being upgraded or is a fresh installation.
...
From 1.5 onward, SCS no longer uses a dual-pool system of address allocation. Older versions used a “transient” DHCP pool to assign addresses while nodes are were first booting, with the expectation that the nodes would later acquire an address from the more permanent “storage” pool.
Now, SCS uses a single pool of addresses, bounded by the upper and lower reserved ranges. Once a node begins booting and reports its IP address to SCS, SCS will associate that IP address with the node’s chassis ID and embed the IP address within the node’s node.cfg configuration file. This ensures that the node ends up with the same IP address, regardless of how DHCP responds during the initial boot process on subsequent boots.
Note
If the chassis ID changes (due to a change in NICs on a booting node), then a new IP address may be assigned to the node.
Fresh Installations
Static IP address assignment is enabled The assignment of static IP addresses is by default enabled. To ensure this is the case, follow the normal installation procedures for both SCS and the Swarm Storage bundle for SCS, including a run of scsctl diagnostics config scan_missing at the end and initializing DHCP (scsctl init dhcp ...).
...
Once these have been confirmed, the configuration is complete for static IP address assignments.
...
If the current environment relies on dynamic IP addresses for storage nodes, then no extra steps are required.
Follow the normal upgrade procedures for both SCS and the Swarm Storage bundle for SCS. When upgrading SCS, be sure to run scsctl diagnostics upgrade_check -a to ensure that all SCS-related software components are properly updated, verifying that all steps complete are completed successfully. Once all upgrade steps have been completed, including a run of scsctl diagnostics config scan_missing at the end, re-initialize DHCP (scsctl init dhcp ...) using the same upper and lower reserved ranges as in the current configuration.
...