# VLAN Topology for Commvault Flex Open

This topology allows multiple tagged VLANs to connect to the appliance using the data protection interface. This allows connection to multiple non-routable networks used to avoid sending backup traffic through a router or firewall.

Use this procedure to deploy the Commvault Flex Open software using the 11.40.38 Flex ISO or higher version.

This topology, requires 1 - 10 GbE port for data protection which will connect to multiple tagged VLANs to transfer data to and from the clients being protected and connect to the CommServe server. This will include connections to:

- 2 or more VLAN IDs

- 2 or more IP addresses based on the number of VLANs

One of the vLANs must remain routable to connect to the CommServe server.

Note

VLAN topology connects multiple VLANs directly to the Commvault Flex Open nodes over a single physical connection. This is typically used to connect directly to different networks to avoid traversing routers or firewalls that can become a bottleneck, or to connect to isolated networks. This setup does not provide network redundancy and hence should be combined with the bonded VLAN configurations.

## Network Requirements

In this topology, the number of IP addresses required depends on the number of VLANs. For example, if you have 3 VLANs, 10, 20 and 30, you will require 3 IP addresses as follows:

- 1 - 10 GbE data protection port connected to the VLAN IP addresses for each of the VLANs used for data protection.

  Out of the available VLANs, one network should be routable and the other network(s) can be non-routable. The routable network will be used for CommServe server registration, in addition to data protection operations. All non-routable VLANs will be used exclusively for data protection operations.

- The storage pool network is optional during Commvault Flex Open installation. Storage pool IP addresses on different nodes can be configured on different subnets. This provides greater flexibility in network design for Commvault Flex Open deployments. There are no hard validation checks or installation failures if storage pool IPs are on different subnets.

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

| Node
--- | ---
Data Protection Fully Qualified Domain Name* |
Data Protection vLAN Address* |
Data Protection Netmask* |
Data Protection Gateway* |
Data Protection DNS 1* |
Data Protection DNS 2 |
Data Protection DNS 3 |
Data Protection NIC Port 1 Card 1 MAC Address |
Storage Pool IP Address* |
Storage Pool Netmask* |
Storage Pool NIC Port 2 Card 1 MAC Address |

* Required fields The following information is required for the vLANs. (The following section is provided with examples for illustrative purposes. Replace them with the appropriate IP addresses in your environment.)

vLAN1 |
vLAN1 Description | Infrastructure
vLAN1 ID | 10
vLAN1 Address | 172.16.10.101
vLAN1 Netmask | 255.255.255.0
vLAN2 |
vLAN2 Description | Marketing
vLAN2 ID | 20
vLAN2 Address | 172.16.20.101
vLAN2 Netmask | 255.255.255.0
vLAN3 |
vLAN3 Description | Sales
vLAN3 ID | 30
vLAN3 Address | 172.16.30.101
vLAN3 Netmask | 255.255.255.0

Note

Depending on the number of vLANs in your environment, add rows to include the information for all the vLANs.

×

Loading...