Defining a virtual Ethernet adapter

Edit online

Additional procedures for cluster communications.

During storage area network (SAN) port configuration you must verify that your server interfaces are connected to the SAN fabric ports in the same zone.

To configure the VLAN to establish SAN communication when the storage adapters are virtualized through VIOS, complete the following steps
  1. Enable the target mode enabled (TME) attribute on VIOS Fibre Channel adapters as the padmin, by entering the following commands.
    chdev -dev fcs0 -attr tme=yes -perm 
    shutdown -restart
  2. On the Hardware Management Console (HMC), add a virtual Ethernet adapter to the profile of each PowerHA SystemMirror virtual client node that has a VLAN ID of 3358.
  3. Reactivate the partition by using the new profile. The new profile will boot, and then display a new entX. To display the interface status, enter the command lscluster -i
Notes:
  1. VLAN 3358 must be created on the virtual client LPARs and VIOS servers.
  2. VLAN 3358 is the only value that CAA uses. The VLAN tag of sfw0 must not be changed.
  3. The entX adapter that is associated with VLAN 3358 does not require an enX interface or an IP address.
  4. VLAN 3358 must not be bridged to the Shared Ethernet Adapter (SEA).
  5. When SAN communication is configured properly, the lscluster -m command shows the status of the sfwcom (storage framework communication) interface as up.
  6. The VIOS fcs adapter that serves the repository disk through N_Port ID Virtualization (NPIV) can also be used for SAN communication. However, this configuration represents a single point of failure and therefore, different VIOS fcs adapters must be used for the repository and SAN communication.