Networks > Quick Start: Add an active/active network configuration |  | next

# Quick Start: Add an active/active network configuration

This quick start describes the process to add an active/active configuration for an enclosure.

### Prerequisites

- Minimum required session ID privileges: Infrastructure administrator or Network administrator to add the network.

- Minimum required session ID privileges: Infrastructure administrator or Server administrator to change the server profile configurations.

- Two or more fully supported Virtual Connect interconnect modules as listed in the HPE OneView Support Matrix.

- The enclosures and server blades are already added to the appliance.

- Follow recommended naming conventions described in Requirements for an active/active configuration.

## Adding an active/active network configuration for single or multiple logical interconnect groups

For each Virtual Connect interconnect module you want to set up as an active/active configuration in the appliance, make configuration changes to the following resources:

Resource | Task | Description
--- | --- | ---
Networks | Add networks. For an enclosure group with a single logical interconnect group: Add a pair of Ethernet networks for each VLAN you want to connect: one network for the first interconnect module and one network for the second interconnect module using the same VLAN ID. For example, create `Dev101_A` and `Dev101_B` for VLAN ID 101. For a multiple logical interconnect group configuration: Add an Ethernet network to be used in both logical interconnect groups. | For the `name` attributes, assign names to the networks following Requirements for an active/active configuration For the `vlanId` attribute, enter the same ID for the pair of networks. Set the `smartLink` attribute to `true`.
Logical Interconnect Groups and Logical Interconnects | Create uplink sets. For an enclosure group with a single logical interconnect group: Create a pair of uplink sets to associate the networks with the uplink ports on the interconnect module. Assign one set of networks to the uplink set that has ports on the first interconnect module. Assign the other networks to the uplink set that has ports on the second interconnect module. For example, uplink port X5 is defined in both sets: `UplinkSet_A` for bay 1 and `UplinkSet_B` for bay 2. `Dev101_A` is assigned to `UplinkSet_A`, and `Dev101_B` is assigned to `UplinkSet_B`. For a multiple logical interconnect group configuration: Create an uplink set on the first logical interconnect group and an uplink set on the second logical interconnect group with the same networks. | You can either add the networks to existing uplink sets or create new uplink sets for the networks. Uplinks in each uplink set must be restricted to a single interconnect. Duplicate VLAN IDs are not allowed in the same uplink set. For more information, see About logical interconnects and About logical interconnect groups.
Network Sets | (Optional) Add one or more pairs of network sets. Each set should include only the networks that will be used on the same server profile connection. For example, create network set `DevSet_A` for your development `Dev_A` networks, and create `DevSet_B` for your development `Dev_B` networks. | Adding a network to a network set does not require that you take resources offline. You do not need to update server profiles that have connections to the network set. Duplicate VLAN IDs are not allowed in a network set. Each network set should have multiple networks. For more information, see About network sets
Server Profiles and Server Hardware | Power off the server before you edit the server profile. Edit the server profile to add two connections. Assign one port for the networks or network sets on one module, and assign a different port for the networks or network sets on the other module. Make sure the networks associated with the uplink ports in the uplink set match the networks assigned to the profile connections in the downlink ports. For example, `Connection1` is LOM1:1-a for `DevSet_A`, and `Connection2` is LOM1:1-b for `DevSet_B`. Power on the server. | When adding a connection to the server profile, select the physical port connected to the module with the uplink set containing the networks configured for that connection. Do not select Auto. For more information, see About server profiles.

prev | up | next
Update a connection template | home | Quick Start: Migrate from an active/standby to an active/active network configuration

Copyright © 2013-2016 Hewlett Packard Enterprise Development LP