Skip to main content

Network Management

The Network Management module in eEKAS provides a centralized, intuitive interface for configuring
and monitoring all network interfaces and connections across the cluster. In a Ceph-based high-availability
environment, reliable and well-optimized networking is critical for both storage performance and service
continuity. This module ensures administrators can easily define, adjust, and troubleshoot network configurations
without interrupting running services.

In eEKAS, networking is built around IP Groups—logical collections of one or more IP addresses that
can be assigned to specific services such as S3, SMB, NFS, iSCSI, or NVMe-oF. IP Groups are highly flexible:
they can be moved between cluster nodes during planned maintenance or automatically during failover events, ensuring
uninterrupted client connectivity.

Key Capabilities

  • Centralized Interface Management – Configure physical interfaces, bonded interfaces for
    redundancy/performance, and VLAN-tagged interfaces across all nodes from a single screen.
  • VLAN Support – Create and assign VLANs to logically separate traffic (e.g., management, storage
    replication, and client access) without adding more physical NICs. VLANs help segment and prioritize traffic while
    improving security.
  • Multi-Network Support – Isolate storage backend traffic from client-facing traffic to enhance both
    performance and stability.
  • High Availability Integration – IP Groups automatically fail over between nodes in case of node
    failure, keeping client connections active.
  • Real-Time Monitoring – Track link state, bandwidth usage, and traffic statistics for proactive
    troubleshooting.

By combining powerful configuration tools with automated failover logic, eEKAS Network Management ensures that your
cluster maintains stable, high-performance connectivity—supporting both the storage backend and the client-facing
services that rely on it.

Example VLAN Scenario

  • VLAN 10 – Management traffic: cluster administration, monitoring, and control.
  • VLAN 20 – Storage replication traffic: Ceph internal communication between nodes.
  • VLAN 30 – Client access traffic: SMB/NFS/iSCSI/NVMe-oF services.

This layout keeps each traffic type logically isolated, reducing contention and improving both performance and security.

You can extend the model with additional VLANs for S3, backup traffic, or other specialized workloads as needed.

Back to top