> Essential > Storage > Remote Office Appliance > ROBO on Linux > Getting Started > Determining the Network Topology

Bonded Topology for Linux ROBO

Bonded topology is the most common option for Linux ROBO as this provides network level redundancy for each node.

In this topology, the node requires connections to 2 - 10 GbE port for data protection network, which transfers data to and from the clients being protected and connect to the CommServe server.

Use this procedure to deploy the Linux ROBO software using the Linux ROBO ISO 3.2408 or higher version.

Note

Bonded topology is the most used configuration and is recommended for most deployments. The bonding can be configured to provide redundancy using either the Active-Backup bonding or the Link Aggregation Control Protocol (LACP). This can also be used with a multi-switch link aggregation protocol such as Virtual Port Channel (VPC), MLAG, or MC-LAG to provide switch level redundancy.

  • Each pair will be bonded on the node, so it is treated as one logical connection. If a node encounters a cable, SFP, or network card failures, the node remains operational without any user intervention. This can optionally be setup to connect to 2 switches to provide switch level redundancy.

  • Active-Backup and Link Aggregation Control Protocol (LACP) are the supported bonding modes.

    LACP requires the switch(s) to support it as well. When using LACP, each pair of ports should be configured as an active port-channel, and not configured to negotiate the aggregation protocol.

Network Requirements

The following network names and IP addresses are required for a bonded topology:

Node

Data Protection Fully Qualified Domain Name*

Basic Topology (2)

Data Protection IP Address*

Basic Topology (2)

Data Protection Netmask*

Basic Topology (2)

Data Protection Gateway*

Basic Topology (2)

Data Protection DNS 1*

Basic Topology (2)

Data Protection DNS 2

Basic Topology (2)

Data Protection DNS 3

Basic Topology (2)

Data Protection NIC Port 1 Card 1 MAC Address

Basic Topology (2)

Data Protection NIC Port 1 Card 2 MAC Address

Basic Topology (2)

CommServe Requirements

You will require the following information to connect to an existing CommServe server:

CommServe hostname (FQDN)

Fully qualified hostname (FQDN) associated with the existing CommServe server.

Note

TCP Ports 8400 & 443 must be open from the nodes to the CommServe server.

Username

Username associated with the admin user.

Password

Password for the admin user.

Loading...