Networks > Quick Start: Migrate from an active/standby to an active/active configuration |  | next

# Quick Start: Migrate from an active/standby to an active/active configuration

This quick start describes how to migrate from an active/standby configuration to an active/active configuration for an enclosure.

Prerequisites

- Required privileges: Infrastructure administrator or Network administrator for adding networks.

- Required privileges: Infrastructure administrator or Server administrator for changing the server profile configurations.

- Two or more supported Virtual Connect interconnects, as listed in the appropriate support or compatibility matrix on the Hewlett Packard Enterprise Information Library.

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

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

## Migrating from an active/standby to an active/active configuration

For an enclosure group with a single logical interconnect group, when migrating from an active/standby configuration to an active/active configuration, make configuration changes to the following resources:

Resource | Task | Description
--- | --- | ---
Logical Interconnect Groups | Find the uplink set or sets that you want to convert to active/active. Record all networks in the uplink sets. | For more information, see the online help for Logical Interconnect Groups, or the REST API scripting help for logical interconnect groups.
Networks | Rename the networks by adding `<side>` to the network name, as described in Requirements for an active/active configuration (for example, `Dev_100_A`). Create Ethernet networks using the same external VLAN ID for each network renamed in step 3 (for example, `Dev_100_B`). | On the Networks screen: For VLAN ID, use the same external VLAN ID for each network renamed in step 3. Verify that Smart link is selected.
Network Sets | (Optional) Add network sets for the networks created in step 4. | 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. For more information about network sets, see Network Sets, or see the REST API scripting help for networks and network sets.
Logical Interconnect Groups and Logical Interconnects | Determine if all logical interconnects have active and standby uplink ports on the same modules. If the standby uplinks are on the same module, go to step 7. If the standby uplinks are on different modules, force a failover so that all standby uplinks are on the same module. Go to step 7. Edit the active/standby uplink set and delete the standby uplinks. Create a second uplink set for the standby uplinks removed in step 7. Add the networks created in step 4 to the new uplink set. For example, `UplinkSet_B` contains all `Dev_B` networks. Select Actions→Update from group. The active uplinks maintain traffic so there is no downtime. | To determine the port status (active or standby), access the Logical Interconnects screen and review the state of each port in the Uplink Sets view. Hewlett Packard Enterprise recommends deleting the standby uplinks from the original uplink set, and then adding them to the new uplink set. This method prevents connectivity loss. If you change the name of an uplink set on the Logical Interconnect Groups screen, and then select Actions→Update from group on the Logical Interconnects screen, connectivity is interrupted briefly. For more information, see Logical Interconnects, or see the REST API scripting help for logical interconnects and the REST API for the `uplink-sets` resource.
Server Profiles and Server Hardware | Power off the server before you edit the server profile. Edit the server profile to add a connection for the new networks or network sets. Power on the server. | Change every server profile connection associated with the port servicing the original standby uplinks. Assign the new networks or network sets created in steps 4 or 5 to the port. For more information about server profiles, see Server Profiles, or see the REST API scripting help for server profiles.
Logical Interconnect Groups and Logical Interconnects | Edit the logical interconnect group and rename the original uplink set by adding `<side>` to the name, as described in Requirements for an active/active configuration (for example, `UplinkSet_A`). Do not make any changes other than the uplink set name. Select Actions→Update from group. | For more information, see the online help for Logical Interconnects, or the REST API scripting help for logical interconnects and the REST API for the `uplink-sets` resource.

See also

- Networks

prev | up | next
Quick Start: Add an active/active network configuration for single or multiple logical interconnect groups | home | Add a dedicated network for untagged traffic

Copyright © 2013, 2016 Hewlett Packard Enterprise Development LP