Logical Interconnects > About active/active and active/standby configurations |  | next

# About active/active and active/standby configurations

When determining which Virtual Connect network configuration to use (active/active or active/standby), consider the type of network traffic the enclosure must support. For example:

- Will there be a high volume of server-to-server traffic (east/west) in the enclosure?

- Is the traffic flow in the enclosure mainly inbound and outbound (north/south)?

By considering network traffic patterns, you can maximize the connected bandwidth or minimize server-to-server traffic leaving the enclosure.

Use an active/standby configuration if network traffic is between systems in the same enclosure (east/west). This configuration minimizes or eliminates any server-to-server communications from leaving the enclosure.

Use an active/active configuration if network traffic is inbound and outbound (north/south) of the enclosure.

## About active/standby configurations

An active/standby configuration is an Ethernet network configuration where servers in the enclosure have two NIC ports connected to the same Virtual Connect network. A single uplink set has uplinks in both interconnects. The uplinks in one interconnect are active; the uplinks in the other interconnect are standby and available in the event of a network or interconnect failure. Communications between servers do not leave the interconnect module. For external communications, all servers in the enclosure use the active uplink, regardless of which NIC is actively passing traffic.

An active/standby configuration:

- Provides predictable bandwidth.

- Does not oversubscribe top-of-rack switch (ToR) bandwidth.

An active/standby configuration has the following requirements:

- A minimum of one Ethernet network and one uplink set for each external VLAN ID you define.

## About active/active configurations

An active/active configuration is an Ethernet network configuration that allows active traffic on the same VLAN on multiple interconnect modules. The NICs on all the servers in the enclosure have their NICs connected to adjacent Virtual Connect modules. All uplinks are active to forward network traffic.

An active/active configuration:

- Provides full use of all uplink ports (no uplink port in standby mode).

- Allows all traffic to egress through the interconnect module connected to the NIC port without crossing the internal stacking link, if stacking is used.

- Doubles the available bandwidth while maintaining redundancy (when combined with Smart Link).

The networks associated with an uplink set must be included in the server profile connection for the interconnect module. For example, if Net_101_A is in uplink set US_A, which has ports from the interconnect module in bay 1, Net_101_A must be associated with the downlink port connected to the interconnect module in bay 1 (for example, LOM1:1-a).

When setting up an active/active configuration in an enclosure, determine if you have a single logical interconnect group or a multiple logical interconnect group per enclosure configuration. For more information, see About multiple logical interconnect groups in an enclosure group.

- In a single logical interconnect group configuration, have at least two Ethernet interconnect modules with stacking links in the enclosure. All interconnects are defined in one logical interconnect in the single logical interconnect group. When you set up the active/active configuration, all networks are available on both interconnects, and subsequently to any server connected to these interconnects through the use of the stacking links. Networks are created in pairs for each VLAN you want to connect.

- In a multiple logical interconnect group configuration, where you define each interconnect in a separate logical interconnect group, and subsequently separate logical interconnects, the interconnects are no longer stacked. Because you can use the same network in both logical interconnect groups, you can create an active/active configuration with twice as many available networks.

### Requirements for an active/active configuration

An active/active configuration requires proper configuration of OS and NIC teaming. An active/active configuration also requires two Virtual Connect modules and resources that meet the following requirements. For an example of an active/active configuration for an enclosure group with a single logical interconnect group, see Sample active/active configuration for single logical interconnect group.

Resource | Requirement | Best practice
--- | --- | ---
Networks | For a single logical interconnect group configuration, create a pair of networks for each VLAN you want to connect. At least one network for the first interconnect module Another network for the second interconnect module using the same VLAN ID and Smart Link selected on both networks. For a multiple logical interconnect group configuration, you can use the same network in both logical interconnect groups. See General if you need assistance with your entries. | For a single logical interconnect group configuration, designate a network name for a paired network using the naming convention `<purpose>`_`<VLAN ID>`_`<side>` where: `<purpose>` could be `dev`, `mgmt`, or `prod`, for example. `<side>` could be `A` or `B`, `1` or `2`, or `right` or `left`.
Uplink Set | For a single logical interconnect group configuration, create a pair of uplink sets to associate the networks with the uplink ports on the interconnect module. One set of networks assigned to the uplink set with uplinks on the first interconnect module The other networks assigned to the uplink set with uplinks on the second interconnect module Uplink ports in each uplink set are restricted to one interconnect For a multiple logical interconnect group configuration, create an uplink set on the first interconnect module and an uplink set on the second interconnect module with the same networks. | For a single logical interconnect group configuration, assign names to uplink sets using the naming convention `<uplink set name>`_`<side>`, where: `<side>` could be `A` or `B`, `1` or `2`, or `right` or `left`.
Network Sets (optional) | One or more pairs of network sets. Each set should include only networks that are intended to be used in the same server profile connection. For example, if Net_101_A is in uplink set US_A, which has ports from the interconnect module in bay 1, Net_101_A must be associated with the downlink port connected to the interconnect module in bay 1 (for example, LOM1:1-a) | For a single logical interconnect group configuration, designate a network set name using the naming convention `<purpose>`_`<side>`, where: `<purpose>` could be `dev`, `mgmt`, or `prod` for example. `<side>` could be `A` or `B`, `1` or `2`, or `right` or `left`.
Server Profiles | The physical ports to which you want to map the network or network sets. Map the profile connections to the downlink ports on the same interconnect module as the uplinks on the uplink set. This ensures that the networks associated with the uplink ports in the uplink set match the networks assigned to the profile connections in the downlink ports. | Do not select Auto for the port. See Connections if you need assistance with your entries.

### Sample active/active configuration for single logical interconnect group

See also

- Logical Interconnects

- Networks

prev | up | next
About firmware associated with a logical interconnect | home | About loop protection

Copyright © 2013, 2016 Hewlett Packard Enterprise Development LP