IBM Support

How to Initiate Login/Logout Operation for virtual Fibre Channel Client Adapters in HMC

Technote (FAQ)


Question

This document describes how to perform a manual N_Port login and logout operation for virtual Fibre Channel Adapters (vFCA) in an AIX client managed by an HMC.

Cause

A login operation may need to be initiated to facilitate SAN Administrators zoning of new virtual WWPNs (vWWPN), including all inactive WWPNs (2nd WWPN in the pair), which are used in Partition Mobility environments.

Answer

Things to keep in mind:

  1. When performing a login operation, all inactive WWPNs will be activated, including the second WWPN in the pair assigned to each virtual Fibre Channel client adapter. When performing a logout operation, all WWPNs not in use will be deactivated.
  2. To successfully log in a virtual Fibre Channel client adapter, the corresponding virtual Fibre Channel server adapter must exist and it must be mapped.
  3. The primary intent of the login operation is to allow the system administrator to allocate, log in and zone WWPNs before the client partition is activated. With best practices, the WWPNs should be logged out after they are zoned on the Storage Area Network (SAN) and before the partition is activated. If a partition is activated with WWPNs still logged in, the WWPNs used for client access are automatically logged out so they can be logged in by the client.
  4. The login operation can also be used to zone the inactive WWPNs in preparation for a partition mobility operation. If the login operation is performed when a partition is already active, only the inactive WWPNs are activated to the "constant login" state similar to physical Fibre Channel adapters. The WWPNs that are already in use by the virtual Fibre Channel client adapters remain in control of the virtual Fibre Channel clients and are not under the control of this command. This means that active client virtual Fibre Channel WWPNs do not achieve a "constant login" state similar to physical Fibre Channel adapters.
  5. The login operation can interfere with partition mobility operations. Best practice is to perform a logout operation for a partition before attempting to migrate the partition to another server. If a mobility operation is attempted with WWPNs still logged in, the firmware will attempt to automatically log out the WWPNs. However, in some cases, the logouts may not complete in time and may therefore cause the mobility operation to fail.

Environment used in the following scenerio:
    - HMC v7r7.9.0
    - VIOS 2.2.4.10 with 8Gb PCI Express Dual Port FC Adapters
    - AIX 7100-02-02-1316 with NPIV V7000 Storage
      Client's sample output


      Where the C# corresponds to the Client Fibre Channel Adapter ID

      Run fcstat command to determine the Active WWPN, i.e.


      Notice the storage is only provisioned thru fscsi0 and fscsi1:

    - IBM SAN Switch 2498-F48 fOS v7.1.0c
      In this example, NPIV traffic for the client's virtual FCA, fcs0 (Active WWPN C0507605E7460046) is bridged by 8-GB NPIV port, fcs0, on VIOS1, which is cabled to port 36 on switch 1.
      Below is a sample output from the switch where we can see the active WWPN logged in:


How to Perform Login/Logout operation using HMC GUI

Login to the HMC GUI as hscroot (or other HMC user with
> In the navigation pane, open Systems Management and click Servers.
> Select the Managed System name (VIRT-9117-MMB-SN10F6B1R, in this case)
> In the work pane, select the NPIV client partition name (virt07-Margarita, in this example)
> Click Tasks > Configuration > Managed Profiles


You will get a screen similar to the one below where the Last Activated profile can be edited ( vSCSI MPIO_boot, in this case, is the client's profile that has the vFCAs for which the login/logout operation is needed):
> Select the profile name
> Click Actions
> Edit


In the next screen:
> Click Virtual Adapters tab
This will show the 3 Client Fibre Channel Adapter IDs (5, 6, & 7 in our example):


> Click Actions
> Advanced
> Login Logout Fibre Channel
    This will display the status for all 6 WWPNs.
    Note: By design, the HMC generates a pair of WWPNs to each virtual fibre channel client adapter at creation time. The first WWPN in the pair is considered the "Active" WWPN which is the one used to zone the storage. The second WWPN, also known as secondary or inactive WWPN, is only used for Partition Mobility.

    0 : Indicates the WWPN status is Logged Out.
    1 : Indicates the WWPN status is Logged In.
    2 : Indicates the WWPN status is Unknown.

    In this example, WWPNs ...0046, ...0048, and ...004e are the Active WWPNs that are already in use (WWPN Status 1) by the virtual Fibre Channel client adapters. Consequently, they remain in control of the virtual Fibre Channel clients and are not under the control of this Login/Logout operation. This means that active client virtual Fibre Channel WWPNs do not achieve a "constant login" state similar to physical Fibre Channel adapters.
    To display the status via HMC CLI, login to the HMC as hscroot and run lsnportlogin:
    hscroot@<hmc_hostname>:~> lssyscfg -r sys -F name       (to list managed system names)
    hscroot@<hmc_hostname>:~> lsnportlogin -m <managed_system_name>  --filter "lpar_names= <NPIV_partition_name> "

> Click Login
    This will cause all inactive WWPNs to be activated (WWPN Status 1) as shown below, including the second WWPN for each pair assigned to each virtual Fibre Channel client adapter to be used for Partition Mobility.



    At this point, all the WWPNs that were previously inactive (...0047, ...0049, and ...004f) are now logged in on the SAN switch ready for the SAN Administrator to create new zone(s), and they will remain in "constant login" state until a Logout operation is performed. Note: By clicking Cancel after a Login operation has been done will just cause the Login Logout Fibre Channel window to be closed, but the inactive or secondary WWPNs will remain Logged-In until the Logout operation is done. It is strongly recommended to perform a Logout operation once the zoning has been created. Failure to do so may cause vfcmap command to fail on the VIOS with " Device...busy." error as a result, if one attempts to unmap the NPIV port from the vfchost adapter while the WWPN Status is Logged-In By vios, as shown below:


    If we take a closer look at virtual fibre channel client adapter ID 5's secondary WWPN (C0507605e7460047) from the switch side, we can see that it is now listed in addition to the primary or active WWPN (C0507605e7460046):


> Click Logout
This will cause all WWPNs not in use (the secondary or inactive WWPNs) to be deactivated:


Related information

chnportlogin HMC command

Document information

More support for: Virtual I/O Server

Software version: 2.2.3, 2.2.4

Operating system(s): AIX, Other

Software edition: Enterprise, Express, Standard

Reference #: T1024487

Modified date: 01 December 2016