IP Groups

An IP GroupsGroup aredefines athe corestable componentservice ofaddresses eEKAS,that providingclients a flexible and powerful wayuse to manage service accessibility and high availability across the cluster. Instead of binding services likeaccess SMB, NFS, iSCSI,S3, and iSCSI services. It also determines which gateway nodes may serve those addresses and the order in which they are used during failover.

The cluster monitors the addresses and can move them to another eligible gateway during maintenance or NVMe-oFafter a failure. Shares, exports, buckets, users, and access keys remain unchanged. Existing client connections may need to areconnect.

specific

Before networkyou interfacebegin

• The cluster is configured and all intended gateway nodes are online.
• One or server,more unused static IP Groupsaddresses alloware theseavailable serviceson tothe beclient-facing dynamicallynetwork.
assigned
• Every eligible gateway can access the required VLAN and movedsubnet acrosswith nodesconsistent asMTU, needed.
  routing,

  Eachand firewall configuration.

• The addresses are excluded from DHCP and recorded in IPAM.
• DNS records are prepared if clients use a service name.
• For S3 over HTTPS, a certificate is available that matches the DNS name used by clients.
• For iSCSI multipath, prepare at least two addresses, two eligible gateway nodes, and multipath-capable initiators.

Open IP Group actsManagement

as

a
1. Sign logicalin containerto forthe euroNAS Administration GUI.
2. Open Cluster Management.
3. Select IP Groups.
4. Review the existing groups and their members before making changes.

The overview shows the current serving nodes, gateway order, service addresses, address placement, and assigned services.

Column	Meaning
Name	The permanent administrative name of the IP Group.
Serving nodes	Nodes currently serving one or more addresses from the group.
Gateway order	Primary, secondary, and fallback preference used for placement and failover.
IP addresses	Floating client-facing service addresses.
Address placement	Shows whether addresses remain together or are distributed across gateway nodes.
Members	SMB, NFS, S3, or iSCSI services that currently use the group.

Create an IP Group

1. Select Create IP Group.
2. Enter a unique name containing 3–15 letters or numbers. The name cannot be changed after creation.
3. Enter the service IP addresses separated by commas and verify that they are not already in use.
4. Enable only the nodes that may serve this IP Group. Unselected nodes are excluded.
5. Arrange the enabled nodes as primary, secondary, and additional fallback nodes.
6. Select the required address-placement mode.
7. Review the settings and select Create Group.
8. Return to the overview and confirm that the group has a serving node.

Choose the address-placement mode

Option	When to use it	Requirements
Keep addresses together	All addresses run on one gateway and move together during failover. This provides high availability but does not distribute client connections across nodes.	At least one address; two eligible nodes are recommended for failover.
Distribute addresses across gateway nodes	Each address prefers a different gateway. Use this for multiple S3 or file-service addresses and isfor iSCSI multipath portals.	At least two addresses and two eligible nodes. Publish every intended file or S3 address in DNS and configure multipath on iSCSI initiators.

Note: With one address, the service runs on one gateway. If that gateway fails, the cluster moves the address to the next eligible node.

Edit an existing IP Group

1. Select the IP Group name in the overview.
2. Review the entries in the Members column before changing addresses or gateways.
3. Modify the addresses where permitted for the services in use.
4. Enable or exclude gateway nodes and set their new order.
5. Select Save Settings.
6. Allow the cluster to reconcile placement. Refresh the overview and confirm the serving nodes and address mapping.

Assign an IP Group to an S3 service

During S3 drive creation

1. Create the IP Group before starting the S3 drive wizard.
2. Select the intended IP Group in the S3 service section.
3. Enter the DNS name used toby hostclients.
4. Choose HTTP or provide a specificmatching setcertificate for HTTPS.
5. Complete the wizard and wait until all gateways are ready.
6. Verify DNS resolution and the HTTPS certificate from a client network.

Change the IP Group of services.an Theseexisting groupsS3 aredrive

1. Open Cluster Drive Management.
2. Open the S3 drive properties and select Show S3 Certificate.
3. Select the new IP Group at the top of the dialog.
4. Select Change IP Group and confirm.
5. Keep the dialog open and monitor the progress bar. The system validates the group, adjusts gateway placement, and updates membership and monitoring.
6. Test the endpoint from every required client network.

Certificate material is intentionally excluded from this screenshot.

DNS, TLS, and client configuration

DNS

For a group with one address, publish that address under the service name. For distributed S3 or file access, publish all intended addresses under the same DNS name. Choose a DNS TTL that supports your recovery objectives.

TLS for S3

The certificate must match the DNS name used by clients. You can add a certificate later to an S3 drive initially configured for HTTP or replace an existing certificate. Verify the complete certificate chain, expiration date, and matching private key before applying it.

iSCSI initiators

Configure every portal address and enable the operating system's supported multipath driver. One optimized path is assigned per LUN; the other paths remain available as standby paths.

Daily monitoring

• Confirm that every IP Group shows the expected serving nodes.
• Compare the address mapping with the selected placement mode.
• Verify that every expected service appears under Members.
• Review cluster health warnings and gateway diagnostics.
• Test the service endpoint, not tiedonly node reachability.
• For S3, monitor certificate expiration and DNS correctness.

Planned maintenance and failover validation

1. Confirm that at least one alternate eligible gateway is healthy.
2. Record the current serving-node and address mapping.
3. Perform the approved maintenance or controlled failover action.
4. Refresh IP Group Management and confirm that the address moved to aan physicaleligible node.
5. Test service access through DNS and every published address.
6. After restoring the node, meaningconfirm theythat canit failrejoins overthe automaticallyeligible set. The address may remain on its current node to avoid another unnecessary interruption.

Troubleshooting

Problem	Checks	Corrective action
The group has no serving node.	Cluster quorum, eligible-node status, VLAN, network interface, address conflicts, and gateway diagnostics.	Restore an eligible node or network path and remove address conflicts.
The address responds but the service does not.	Protocol gateway, port, certificate, service membership, and firewall.	Review cluster diagnostics and correct the protocol or firewall configuration.
Distributed addresses remain on one node.	Placement mode, number of addresses, number of enabled nodes, and current constraints.	Use at least two addresses and two eligible nodes, save again, and allow placement to reconcile.
S3 clients cannot connect after reassignment.	Progress result, DNS, port and protocol, TLS name, and routing to every group address.	Correct DNS, network, or TLS configuration. If the job failed, automatic rollback may have restored the previous group.
The IP Group cannot be deleted.	The Members column and attached SMB, NFS, S3, or iSCSI resources.	Remove or reassign every member before deleting the group.
Client access is intermittent.	Duplicate IP address, asymmetric routing, inconsistent VLAN or MTU settings, and unreachable addresses in DNS.	Correct the network design and test every published address from the client segment.

Delete an IP Group

Deleting a group removes its service addresses from the cluster. Clients lose access if a service or DNS record still depends on those addresses.

1. Identify every member in the overview.
2. Remove the attached services or assign them to another IP Group.
3. Confirm that no DNS record or client still depends on the addresses.
4. Open the group, select Delete Group, and confirm.
5. Verify that the group is absent, its addresses no longer respond, and the remaining services are healthy.
6. Update DNS, IPAM, and operational records.

Commissioning checklist

• Addresses reserved and excluded from DHCP
• VLAN, subnet, MTU, routing, and firewall validated on every eligible node
• Gateway order approved
• Placement mode matches the service design
• DNS records created and tested
• S3 certificate matches the DNS name
• iSCSI multipath configured where applicable
• Service membership visible in casethe ofoverview
a
• Normal hardwareendpoint failuretest orpassed
maintenance
• Controlled event, ensuring service continuityfailover and resilience.
  recovery

  

  test

  Keypassed

Benefits of IP Groups

High Availability: In the event of a node failure, IP Groups are automatically transferred to another healthy node, maintaining uninterrupted access to services.

Service Isolation: Different services can be assigned to separate IP Groups, allowing for clean separation

• Monitoring and betteroperational security.
  documentation

  Simplifiedupdated

Management: Administrators can manage network services centrally and reassign IP Groups without disrupting the entire system.

Scalability: IP Groups make it easy to scale services across the cluster by reassigning or expanding groups without complex reconfiguration.

Use Cases

Assigning a dedicated IP Group for each department or service type (e.g., separate groups for file sharing and backups).

Enabling iSCSI / NVMe-oF multipath access by assigning multiple IP addresses to a single IP Group, allowing initiators to connect through multiple network paths for improved throughput and failover resilience.

Seamlessly migrating services during node failure, maintenance or upgrades.

In eEKAS, IP Groups are designed to enhance the modularity, flexibility, and fault tolerance of your storage infrastructure, forming the backbone of its service availability model.