Skip to main content
Version: 2.11.0

High Availability (HA) Deployment

Overview​

High Availability (HA) ensures that systems like NetFlow Optimizer remain operational and accessible, minimizing downtime and maximizing reliability. This document provides a general guide on HA deployment strategies, such as active-active and active-passive configurations. It's important to note that the configuration and maintenance of HA systems are the responsibilities of the customer. Our support will focus on the core functionality of NetFlow Optimizer.

Deployment Strategies​

  • Active-Active: All nodes are active and handle traffic simultaneously, enhancing load balancing and availability.
  • Active-Passive: Involves a primary node serving traffic and a secondary standby node that becomes active on primary node failure.

Active-Active Deployment​

Architecture​

In an active-active setup, multiple nodes operate concurrently to manage traffic loads efficiently. This architecture employs load balancers to distribute network traffic and requests evenly across all nodes.

Components:​

  1. Nodes: Multiple instances of NetFlow Optimizer running in parallel.
  2. Load Balancer: Manages the distribution of user requests and network traffic across all active nodes.
  3. Data Synchronization: Ensures all nodes have consistent and up-to-date information.

Benefits:​

  • Enhanced load management with all nodes active.
  • Reduced risk of downtime as traffic can be rerouted to other nodes instantly if one fails.

Customer Responsibilities:​

  • Implementing and managing load balancing solutions.
  • Ensuring data synchronization across nodes.

Active-Passive Deployment​

Architecture​

This simpler HA setup involves a primary node that handles all operations and a secondary node that activates only if the primary fails.

Components:​

  1. Primary Node: Handles all operational traffic.
  2. Secondary Node: Remains idle until needed for failover.
  3. Failover Mechanism: Automatically redirects traffic from the failed primary node to the secondary node using a floating IP, for example.

Benefits:​

  • Simplicity in management with only one active node at a time.
  • Cost-effectiveness by having secondary resources on standby rather than in constant use.

Customer Responsibilities:​

  • Configuring the failover mechanism.
  • Regular testing to ensure seamless activation of the secondary node during primary failures.

Implementation Guidance​

  1. Planning: Assess your requirements and choose between active-active or active-passive based on your specific needs for NetFlow Optimizer.
  2. Configuration: Set up the nodes, load balancers, and data synchronization mechanisms as required.
  3. Testing: Validate the setup by simulating failures and ensuring failover occurs smoothly.
  4. Monitoring and Maintenance: Continuously monitor the system's performance and conduct regular maintenance to prevent failures.

Conclusion​

Implementing HA for NetFlow Optimizer is a proactive step towards ensuring that network data analysis remains uninterrupted. While we provide support for the application itself, the configuration and maintenance of the HA environment rest with you, the customer. By following these guidelines, you can establish a robust HA setup that aligns with your organizational needs and technical capabilities.