> Expert > Commvault HyperScale > HyperScale X > Getting Started > Determining the Network Topology

Bonded Topology With 1 GbE Management Network

This topology combines the bonded topology with a 1 GbE management interface.

This can be used in cases where the data protection network will be on a non-routable backup network, and therefore an additional management interface is required. This topology leverages one of the built-in 1 GbE copper interfaces for management traffic and will require additional cabling.

In this topology, each node requires connections to 3 separate network, as follows:

  • 2 - 10 GbE port for data protection network, which transfers data to and from the clients being protected and connect to the CommServe server.

  • 2 - 10 GbE port for storage pool network, which is a dedicated private network, used for communication and replication between the HyperScale nodes.

  • 1 - 1 GbE port for management network, which is used exclusively for all management related communication, such as connecting to the CommServe server, accessing the DNS server, etc. Management ports cannot be configured with bonding.

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. Combine the bonded topology with a Management network if the HyperScale X Reference Architecture nodes are located in an isolated backup network.

embd_bonded_1GbE_topology_desc (1)

  • 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

In this topology, each node requires the following connections:

  • 2 - 10GbE bonded ports for the data protection network, (or using multiple vLAN networks) which transfers data to and from the clients. This requires a corresponding IP address for the data protection network.

  • 2 - 10GbE bonded ports for the storage pool which is a dedicated private network, used for communication and replication between the HyperScale nodes. This requires a corresponding IP address for the storage pool network.

  • 1 – 1GbE port for the management network, which is connected to a routable network with DNS access. This requires a corresponding IP address for the management network.

Note

Data Protection, storage pool, and management networks MUST be on separate subnets.

The following network names and IP addresses are required for the 1 GbE management topology:

Node 1

Node 2

Node 3

Node n

Data Protection Fully Qualified Domain Name*

Basic Topology (2)

Basic Topology (2)

Basic Topology (2)

Basic Topology (2)

Data Protection IP Address*

Basic Topology (2)

Basic Topology (2)

Basic Topology (2)

Basic Topology (2)

Data Protection Netmask*

Basic Topology (2)

Basic Topology (2)

Basic Topology (2)

Basic Topology (2)

Data Protection Gateway*

Basic Topology (2)

Basic Topology (2)

Basic Topology (2)

Basic Topology (2)

Data Protection DNS 1*

Basic Topology (2)

Basic Topology (2)

Basic Topology (2)

Basic Topology (2)

Data Protection DNS 2

Basic Topology (2)

Basic Topology (2)

Basic Topology (2)

Basic Topology (2)

Data Protection DNS 3

Basic Topology (2)

Basic Topology (2)

Basic Topology (2)

Basic Topology (2)

Storage Pool IP Address*

Basic Topology (2)

Basic Topology (2)

Basic Topology (2)

Basic Topology (2)

Storage Pool Netmask*

Basic Topology (2)

Basic Topology (2)

Basic Topology (2)

Basic Topology (2)

Data Protection NIC Port 1 Card 1 MAC Address

Basic Topology (2)

Basic Topology (2)

Basic Topology (2)

Basic Topology (2)

Data Protection NIC Port 1 Card 2 MAC Address

Basic Topology (2)

Basic Topology (2)

Basic Topology (2)

Basic Topology (2)

Storage Pool NIC Port 2 Card 1 MAC Address

Basic Topology (2)

Basic Topology (2)

Basic Topology (2)

Basic Topology (2)

Storage Pool NIC Port 2 Card 2 MAC Address

Basic Topology (2)

Basic Topology (2)

Basic Topology (2)

Basic Topology (2)

Management IP Address*

Basic Topology (2)

Basic Topology (2)

Basic Topology (2)

Basic Topology (2)

Management Netmask*

Basic Topology (2)

Basic Topology (2)

Basic Topology (2)

Basic Topology (2)

* Required fields Each node should be resolvable to the CommServe server.

Note

If you have more than 3 nodes expand the columns in this table to include all the nodes that you plan to setup.

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...