How to Setup SEA Failover on DUAL VIO servers?

What needs to be done? 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. Note:  SEAs has the same PVID, but will have a different priority value. Control Channel: An additional virtual Ethernet adapter , which belongs to a unique VLAN on the system, is used to create the control channel between the SEAs, it 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 Limitation : 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. Steps : Create the Virtual ethernet adapter with the following option on the VIOS1 . virtual adapter a unique (Port Virtu

How to configure NPIV (N_Port ID Virtualization)

Step By Step NPIV configuration For maximum redundancy for the paths create the instance on dual VIOS. We will consider an scenario having Power6/7 Server, with 2 PCI Dual/Single port 8 GB Fibre Card with VIOS level – 2,2 FP24 installed and VIOS is in shutdown state. First we need to create Virtual fibre channel adapter on each VIOS which we will later on map to physical fibre adapter after logging into VIOS similarly as we do for Ethernet Please Note: - Create the all lpar clients as per requirements and then configure the Virtual fiber adapter on VIOS. Since we are mapping one single physical fiber adapter to different hosts, hence we need to create that many virtual fiber channel adapter. Dynamically virtual fiber channel adapter can be created but don’t forget to add in profile else you lost the config on power-off. 1.       1. Create Virtual fibre channel adapter on both VIOS server .           HMC--> Managed System-->Manage Profile-->Virtual

NIM Basics

Basics Master (NIM master): The one and only one machine in a NIM environment that has permission to run commands remotely on NIM clients. The NIM master holds all the NIM resources. A client can only have one master, and a master can not be a client of any other master. The NIM master must be at an equal or higher level than the client. Client (NIM client): Any standalone machine or lpar in a NIM environment other than the NIM master. Clients use resources that reside on the NIM master to perform various software maintenance, backup ... Resource (NIM resources): This can be a single file or a whole filesystem that is used to provide some sort of information to, or perform an operation on a NIM client. Resources are allocated to NIM clients using NFS and can be allocated to multiple clients at the same time. Resources can be: mksysb, spot, lpp_source, machines... Allocate/Allocation: This process is what allows your NIM client to access resources in NIM. The master uses