Vif Addresses; Supported Network Configurations (Templates); Gateway Considerations; Ip Address Range - HP StoreOnce B6000 Series Planning And Preparation Manual

VIF addresses

The VIF addresses are key to ensuring continued performance and availability in the event of
failover and are assigned as part of the network configuration process.
There are two instances of VIF addresses: the Management Console VIF and Data Path VIFs.
The B6000 Management Console uses the Management VIF address to access the Backup
System from the customer's network for all manageability tasks. Because this Management
VIF address is dynamic on the system, it can be active on the master node and passive on the
other nodes, but should the master node fail for any reason the Virtual Management Console
simply moves to another node and can still be accessed using the same VIF address.
The VIF Data Path address is associated to a service set, which is the set of services (VTL, NAS,
replication and so on), available for a node. Should the physical port fail, data will
automatically be processed by the service set associated with the failover port using the VIF
Data Path address. No change is needed to the VIF address of the service set, allowing hosts
and the B6000 Backup System to function correctly. Each couplet has two nodes and, therefore,
two service sets, which means that each couplet has two Data Path VIFs.
IMPORTANT:
access the B6000 Management Console (the management VIF), and to configure VTL and NAS
backup targets and replication configurations (the data path VIFs). You will not know what these
addresses are until the HP service engineer has configured the network for you. The HP service
engineer will leave you with a record of these addresses after installation and you can also use
the CLI (command line interface) to display them.

Supported network configurations (templates)

Network ports are bonded to ensure high availability. (But there is no network bonding between
1Gb and 10Gb ports.)
The optimum configuration is to use the 10GbE nodes for NAS data and replication traffic, and
the 1GbE ports for the B6000 Management Console. However, this requires two sub-nets and
may not be available to all users.
Four network configurations are supported and configured using one of the supplied network
templates, illustrated on the following pages. You must decide which template you intend to use
prior to installation. Two of the templates support customer sites with two sub-nets and allow you
to route data traffic on one network and management on the second.

Gateway considerations

Currently, only one gateway is supported. If you are using Template 1 or Template 4, which support
two sub-nets, you must be very clear which network you intend to use for remote access. The
gateway must be in the same sub-net as this network.
For example, users with a 10GbE and a 1GbE network, who wish to use the 10GbE network for
remote access to data, would need to ensure that the gateway is in the same sub-net as the 10GbE
data network for cases such as replication data from remote or other sites. This would restrict access
to the Management Console to other stations on the local 1GbE sub-net, which could be useful if
you require high security access to the management functions.

IP address range

The total number of IP addresses that you require depends upon the template that you select (and
its implementation of physical ports and VIF addresses), and the number of couplets that you have
installed. In the following examples you will find the recommended number of IP addresses. For a
more detailed explanation of VIF addresses and how IP addresses are assigned across couplets,
see Understanding VIF addresses (page
The VIF addresses are the IP addresses that you, the customer, need to know to
10).
Supported network configurations (templates) 1 1