SEA Failover Procedure on Dual VIO

 

 How do I setup SEA failover on DUAL VIO servers (VIOS)?  --- is a FAQ

This document provides concepts of SEA (Shared Ethernet Adapter) and the procedure to configure SEA Failover

 

Shared Ethernet Adapter

Shared Ethernet Adapter can be used to connect a physical network to a virtual Ethernet network. It provides the ability for several client partitions to share one physical adapter. SEA can only be configured on the Virtual I/O server (VIOS) and requires the POWER Hypervisor and Advanced POWER Virtualization feature. The SEA, hosted on the Virtual I/O server, acts as a Layer-2 bridge between the internal and external network.

 

Restrictions with Configuring SEA Failover

• It can only be hosted on the VIOS and not on the client partition.
• The VIOS running Integrated Virtualization Manager (IVM) cannot implement SEA Failover because only one single VIOS can be configured on the P5/P6 with IVM.
• SEA Failover was introduced with Fixpack 7 (Virtual I/O server version 1.2), so both Virtual I/O Servers need to be at this minimum level.

Requirements for Configuring SEA Failover

• One SEA on one VIOS acts as the primary (active) adapter and the second SEA on the second VIOS acts as a backup (standby) adapter.
• Each SEA must have at least one virtual Ethernet adapter with the “Access external network” flag (previously known as “trunk” flag) checked. This enables the SEA to provide bridging functionality between the two VIO servers.
• This adapter on both the SEAs has the same PVID, but will have a different priority value.
• A SEA in ha_mode (Failover mode) might have more than one trunk adapters, in which case all should have the same priority value.
• The priority value defines which of the two SEAs will be the primary and which will be the backup. The lower the priority value, the higher the priority, e.g. an adapter with priority 1 will have the highest priority.
• An additional virtual Ethernet adapter , which belongs to a unique VLAN on the system, is used to create the control channel between the SEAs, and must be specified in each SEA when configured in ha_mode.
• The purpose of this control channel is to communicate between the two SEA adapters to determine when a fail over should take place.

NOTE: If the SEA Failover will be using etherchannel as the physical device, configure the switch ports for etherchannel PRIOR to configuring the etherchannel device on the VIO server. Failure to follow this sequence may result in a network storm.

 

PROCEDURE:

1. Create a virtual adapter to be used in the SEA adapter on VIOS1. EX: (ent2).

To configure a virtual Ethernet adapter via Dynamic Logical Partition (DLPAR) for a running logical partition using HMC V7R3, follow these steps:

 

Note: a DLPAR operation requires the partition to be on the network.

1. In the navigation panel, open Systems Management, open Servers, and click on the managed system on which the logical partition is located.
 
2. In the contents panel, select the VIOS on which you want to configure the virtual Ethernet adapter, click on the Tasks button -> choose Dynamic Logical Partitioning -> Virtual Adapters.
 
3. Click Actions -> Create -> Ethernet Adapter.
 
4. Enter the slot number for the virtual Ethernet adapter into Adapter ID.
 
5. Enter the Port Virtual LAN ID (PVID) for the virtual Ethernet adapter into VLAN ID. The PVID allows the virtual Ethernet adapter to communicate with other virtual Ethernet adapters that have the same PVID.
Note: Give the virtual adapter a unique VLAN ID (PVID): "1"
 
6. Select IEEE 802.1 compatible adapter if you want to configure the virtual Ethernet adapter to communicate over multiple virtual LANs. If you leave this option unchecked and you want this partition to connect to multiple virtual networks, then you must create multiple virtual adapters by creating additional virtual LAN IDs.
 
7. Check the box "access external network".
 
8. Give the virtual adapter a low trunk priority. EX: "1"
 
9. Click OK.
 
NOTE !!
After you have finished, access any existing partition profiles for the logical partition and add the same virtual ethernet adapters to those partitions profiles. The dynamic virtual ethernet adapter will be lost if you shut down the logical partition and activate that logical partition using a partition profile that does not have the new virtual ethernet adapter in it.

2. Create another virtual adapter to be used as a Control Channel on VIOS1. EX: (ent3)

a. Give this new virtual adapter another unique VLAN ID (PVID) EX: "99"
b. Do NOT check the box "access external network".
c. Shutdown, Activate VIOS1 or run cfgdev from VIOS command line if created with DLPAR.

3. Create SEA on VIO server 1 with failover attribute:

$ mkvdev -sea ent0 -vadapter ent2 -default ent2 -defaultid 1 -attr ha_mode=auto ctl_chan=ent3
 
Note: The defaultid value of the SEA should be the Port VLAN ID (PVID) of the default trunk adapter, in case there are more than one trunk adapters configured in the SEA.

4. (OPTIONAL) Assign an ip address to SEA on VIOS1:

 

$ mktcpip -hostname vio1 -interface en4 -inetaddr 9.3.5.136 -netmask 255.255.255.0 -gateway 9.3.5.41 -nsrvaddr 9.3.4.2 -nsrvdomain itsc.austin.ibm.com -start

5. Create a virtual adapter to be used in the SEA adapter on VIOS2. EX: (ent2)

a. Give the virtual adapter the same VLAN ID (PVID) as VIOS1. EX: "1" .
b. Check the box "access external network".
c. Give the virtual adapter a higher trunk priority. EX: "2"

6. Create another virtual adapter to be used as a Control Channel on VIOS2. EX: (ent3):

a. Give this new virtual adapter the same unique VLAN ID (PVID) as the control channel on VIOS1. EX: "99"
b. Do NOT check the box "access external network".
c. Shutdown, Activate VIOS2 or run cfgdev from VIOS command line if created with DLPAR.

7. Create SEA on VIOS2 with failover attribute:

$ mkvdev -sea ent0 -vadapter ent2 -default ent2 -defaultid 1 -attr ha_mode=auto ctl_chan=ent3

8. (OPTIONAL) Assign an ip address to SEA on VIOS2:

$ mktcpip -hostname vio2 -interface en4 -inetaddr 9.3.5.137 -netmask 255.255.255.0 -gateway 9.3.5.41 -nsrvaddr 9.3.4.2 -nsrvdomain itsc.austin.ibm.com -start