When attempting to update from 6100-07-07 to 6100-08-02 results in build date errors for the following filesets.

• devices.pciex.df1020e214103c04.rte
• devices.pciex.df1020e214103c04.diag
• devices.pciex.df1020e214100f04.rte
• devices.pciex.df1020e214100f04.diag

Solution:

To resolve this issue, download the fix for APAR IV42218, and include the images into the same directory as the 6100-08-02 Service Pack prior to updating.

This issue only occurs when updating from the 6100-07-07 Service Pack.

How many virtual processors are active in my AIX LPARs?

Solution:

You can use kdb command and the sub-command vpm:

As you see, the number of active virtual processors is 4.

# echo vpm | kdb
 START END <name>
0000000000001000 0000000004090000 start+000FD8
F00000002FF47600 F00000002FFDF9C0 __ublock+000000
000000002FF22FF4 000000002FF22FF8 environ+000000
000000002FF22FF8 000000002FF22FFC errno+000000
F1000F0A00000000 F1000F0A10000000 pvproc+000000
F1000F0A10000000 F1000F0A18000000 pvthread+000000
read vscsi_scsi_ptrs OK, ptr = 0x0
(0)> vpm
VPM Tunables
vpm_interval............... 000003E8 schedp.vpm_fold_threshold.. 00000031
vpm_fold_limit............. 00000008 vpm_unfold_limit........... 00000002
vpm_be_threshold........... 0000000A

VPM Data
.........................vpm_mgmt :01
........................vpm_flags :01 USE_BEST_ENERGY
....................vpm_prev_time :1368736952449027431 ns
.....................vpm_interval :1001004500 ns
....................vpm_prev_intr :20125205922335 ns
.........................vpm_intr :11899421 ns

VPM Core Buckets
INDX ID TYPE SR CORE LAST ACTI HEAD UTIL STATE
 0 0 SRAD 1 1 1 0 0 51844765

VPM Core State
 POS CORE NEXT PRIO BEST C STATE
 0 0 NONE 0 0 0 GP ACTIVE

VPM Sleep Data.
........................vsd_state :03
..............vsd_sleep_specifier :00000002
................vsd_sleep_latency :0000000000000000 sec 00989680 nsec
....................vsd_min_sleep :0000000000000000 sec 1DCD6500 nsec
....................vsd_prod_lock :@F100010021622400
....................vsd_prod_head :0000000000000000

VSD Thread State.
 CPU VP_STATE SLEEP_STATE PROD_TIME: SECS NSECS CEDE_LAT

0 ACTIVE AWAKE 0000000000000000 00000000 00
 1 ACTIVE AWAKE 0000000000000000 00000000 00
 2 ACTIVE AWAKE 0000000000000000 00000000 00
 3 ACTIVE AWAKE 0000000000000000 00000000 00

(0)>

PDF download:

WebSphere Application Server – Being the Back-Up Administrator

This is really convenient for AIX system administrators.

To be able to use the FLRT scripting capabilities, you need to install wget or other HTTP retrieval program on the AIX servers.

Sample scripts:

#/bin/ksh 
# Sample script using wget to gather product versions and query FLRT. 
# This current sample script provides commands for gathering MTM, 
# AIX version, and System Firmware. 
# 
# The rest of the product queries are samples which are commented out, 
# and have sample values hardcoded, to show sample output. 
# 
# Please provide additional samples through the feedback button at: 
# http://www14.software.ibm.com/webapp/set2/sas/f/flrt/scripting.html 

################################################################################ 
getHost() { 
 HOSTNAME=""; 
 if [[ "$1" = "localhost" ]] 
 then 
 HOSTNAME=`hostname` 
 else 
 HOSTNAME=`ssh $1 'hostname'` 
 fi 
} 

################################################################################ 
getMTM() { 
 # Determine the System Model 
 if [[ "$1" = "localhost" ]] 
 then 
 MTMVALUE=`prtconf | grep "System Model" | cut -f 2 -d ,` 
 else 
 MTMVALUE=`ssh $1 'prtconf | grep "System Model" | cut -f 2 -d ,'` 
 fi 
} 

################################################################################ 
getMHZ() { 
 # MHZ - processor speed. 
 if [[ "$1" = "localhost" ]] 
 then 
 MHZVALUE=`prtconf | grep "Processor Clock Speed" | cut -f4 -d " "` 
 else 
 MHZVALUE=`ssh $1 'prtconf | grep "Processor Clock Speed" | cut -f4 -d " "'` 
 fi 
} 

################################################################################ 
getAIX() { 
 # AIX service pack level. 
 if [[ "$1" = "localhost" ]] 
 then 
 AIXv=`oslevel -s` 
 else 
 AIXv=`ssh $1 'oslevel -s 2>/dev/null'` 
 fi 
 if [[ -z "$AIXv" ]] 
 then 
 AIXVALUE="" 
 else 
 AIXVALUE=$AIXv 
 fi 
} 

################################################################################ 
getFW() { 
 # System firmware (booted) version 
 if [[ "$1" = "localhost" ]] 
 then 
 SFIRMWAREVALUE=`lsmcode -r system | cut -f1 -d " " | cut -f2 -d":"` 
 else 
 SFIRMWAREVALUE=`ssh $1 'lsmcode -r system | cut -f1 -d " " | cut -f2 -d":"'` 
 fi 
} 

################################################################################ 
getVIOS() { 
 if [[ "$1" = "localhost" ]] 
 then 
 VIOSv=`ioslevel 2>/dev/null` 
 else 
 VIOSv=`ssh -o PasswordAuthentication=no padmin@$1 'ioscli ioslevel'|cut -f1 -d'-'` > /dev/null 2>&1 
 fi 
 if [[ -z "$VIOSv" ]] 
 then 
 VIOSVALUE="" 
 else 
 VIOSVALUE=$VIOSv 
 fi 
} 

################################################################################ 
getHACMP() { 
 #HACMP version 
 if [[ "$1" = "localhost" ]] 
 then 
 HACMPv=`lslpp -L cluster.es.server.rte 2>/dev/null | grep cluster.es.server.rte | cut -f3 -d":"` 
 else 
 HACMPv=`ssh $1 'lslpp -L cluster.es.server.rte 2>/dev/null | grep cluster.es.server.rte | cut -f3 -d":"'` 
 #BRAD - hardcode 
 HACMPv=5.3 
 fi 
 if [[ -z "$HACMPv" ]] 
 then 
 HACMPVALUE="" 
 else 
 HACMPVALUE=$HACMPv 
 fi 
} 

################################################################################ 
getGPFS() { 
 #GPFS version 
 if [[ "$1" = "localhost" ]] 
 then 
 GPFSv=`lslpp -Lc gpfs.base 2>/dev/null | grep gpfs.base | cut -f3 -d":"` 
 else 
 GPFSv=`ssh $1 'lslpp -Lc gpfs.base 2>/dev/null | grep gpfs.base | cut -f3 -d":"'` 
 fi 
 if [[ -z "$GPFSv" ]] 
 then 
 GPFSVALUE="" 
 else 
 GPFSVALUE=$GPFSv 
 fi 
} 

################################################################################ 
getCSM() { 
 if [[ "$1" = "localhost" ]] 
 then 
 CSMv=`lslpp -Lc csm.client 2>/dev/null | grep csm.client | cut -f3 -d":"` 
 else 
 CSMv=`ssh $1 'lslpp -Lc csm.client 2>/dev/null | grep csm.client | cut -f3 -d":"'` 
 fi 
 if [[ -z "$CSMv" ]] 
 then 
 CSMVALUE="" 
 else 
 CSMVALUE=$CSMv 
 fi 
} 

################################################################################ 
getHMC() { 
 # HMC version requires a call to the HMC box. Using ssh is one way to do this. 
 # This requires setup of ssh which is not discussed here. 
 if [[ -z "$HMC_USER" ]] 
 then 
 HMCVALUE="" 
 else 
 HMC_OUTPUT=`ssh -l $HMC_USER $HMC_HOST lshmc -V > hmc.out` 
 HMC_VERSION=`grep -i version hmc.out | grep -v base_version| cut -f 3 -d " "` 
 HMC_RELEASE=`grep -i release hmc.out | cut -f 3 -d " "` 
 HMCVALUE=$HMC_VERSION.$HMC_RELEASE 
 fi 
} 

################################################################################ 
processAIX() { 
 # Parse AIX results 
 AIXVer=`grep ^aix getflrt.rpt|cut -f2 -d' '` 
 if [[ -z $AIXVer ]] 
 then 
 #no AIX results returned 
 AIXVer=none 
 else 
 AIXRes=`grep ^aix getflrt.rpt|cut -f3- -d' '` 
 if [[ $AIXRes == "ok" ]] 
 then 
 echo " AIX Version installed: $AIXVer - OK" 
 else 
 echo "** AIX Version installed: $AIXVer - Lower than recommended" 
 AIXRec=`grep "The current recommended SP level for this AIX TL is" getflrt.rpt` 
 echo \\t$AIXRec 
 fi 
 echo 
 fi 
} 

################################################################################ 
processFW() { 
 # Parse System Firmware results 
 FWVer=`grep ^fw getflrt.rpt|cut -f2 -d' '` 
 if [[ -z $FWVer ]] 
 then 
 #no firmware results returned 
 FWVer=none 
 else 
 FWRes=`grep ^fw getflrt.rpt|cut -f3 -d' '` 
 FWRec=`grep ^fw getflrt.rpt|cut -f4 -d' '` 
 if [[ $FWRes == "ok" ]] 
 then 
 echo " System Firmware version: $FWVer - OK" 
 else 
 echo "** System Firmware version: $FWVer - Upgrade recommended" 
 echo \\tRecommended version: $FWRec 
 fi 
 echo 
 fi 
} 

################################################################################ 
processVIOS() { 
 # Parse VIOS results 
 VIVer=`grep ^vios getflrt.rpt|cut -f2 -d' '` 
 if [[ -z $VIVer ]] 
 then 
 #no vios results returned 
 VIVer=none 
 else 
 VIRes=`grep ^vios getflrt.rpt|cut -f3 -d' '` 
 VIRec=`grep ^vios getflrt.rpt|cut -f4 -d' '` 
 if [[ $VIRes == "ok" ]] 
 then 
 echo " VIOS version: $VIVer - OK" 
 else 
 echo "** VIOS version: $VIVer - Upgrade recommended" 
 echo \\tRecommended version: $VIRec 
 fi 
 echo 
 fi 
} 

################################################################################ 
processHACMP() { 
 # Parse HACMP results 
 HAVer=`grep ^hacmp getflrt.rpt|cut -f2 -d' '` 
 if [[ -z $HAVer ]] 
 then 
 #no hacmp results returned 
 HAVer=none 
 else 
 HARes=`grep ^hacmp getflrt.rpt|cut -f3 -d' '` 
 HARec=`grep ^hacmp getflrt.rpt|cut -f4 -d' '` 
 if [[ $HARes == "ok" ]] 
 then 
 echo " HACMP version: $HAVer - OK" 
 else 
 echo "** HACMP version: $HAVer - Unsupported" 
 HAMessage=`grep ^hacmp getflrt.rpt` 
 echo \\tMessage: $HAMessage 
 fi 
 echo 
 fi 
} 

################################################################################ 
processGPFS() { 
 # Parse GPFS results 
 GPFSVer=`grep ^gpfs getflrt.rpt|cut -f2 -d' '` 
 if [[ -z $GPFSVer ]] 
 then 
 #no GPFS results returned 
 GPFSVer=none 
 else 
 GPFSRes=`grep ^gpfs getflrt.rpt|cut -f3 -d' '` 
 GPFSRec=`grep ^gpfs getflrt.rpt|cut -f4 -d' '` 
 if [[ $GPFSRes == "ok" ]] 
 then 
 echo " GPFS version: $GPFSVer - OK" 
 else 
 echo "** GPFS version: $GPFSVer - Upgrade recommended" 
 echo \\tRecommended version: $GPFSRec 
 fi 
 echo 
 fi 
} 

################################################################################ 
processCSM() { 
 # Parse CSM results 
 CSVer=`grep ^csm getflrt.rpt|cut -f2 -d' '` 
 if [[ -z $CSVer ]] 
 then 
 #no CSM results returned 
 CSVer=none 
 else 
 CSRes=`grep ^csm getflrt.rpt|cut -f3 -d' '` 
 CSRec=`grep ^csm getflrt.rpt|cut -f4 -d' '` 
 if [[ $CSRes == "ok" ]] 
 then 
 echo " Cluster Systems Management version: $CSVer - OK" 
 else 
 echo "** Cluster Systems Management version: $CSVer - Upgrade recommended" 
 echo \\tRecommended version: $CSRec 
 fi 
 echo 
 fi 
} 

################################################################################ 
processHMC() { 
 # Parse HMC results 
 HMVer=`grep ^hmc getflrt.rpt|cut -f2 -d' '` 
 if [[ -z $HMVer ]] 
 then 
 #no hmc results returned 
 HMVer=none 
 else 
 HMRes=`grep ^hmc getflrt.rpt|cut -f3 -d' '` 
 HMRec=`grep ^hmc getflrt.rpt|cut -f4 -d' '` 
 if [[ $HMRes == "ok" ]] 
 then 
 echo " HMC version: $HMVer - OK" 
 else 
 echo "** HMC version: $HMVer - Upgrade recommended" 
 echo \\tRecommended version: $HMRec 
 fi 
 echo 
 fi 
} 

################################################################################ 
################################################################################ 
# MAIN 
################################################################################ 
################################################################################ 

FLRTURL="http://www14.software.ibm.com/webapp/set2/flrt" 

HMC_USER=hscroot 
HMC_HOST=9.3.108.4 

WGET=`which wget` 

if [[ -z $WGET ]] 
then 
 echo "wget not found, quitting" 
 exit 1 
fi 

TR=/usr/bin/tr 
format="text" 
hostlist="" 
ts=`date +"%d %h %Y %r"` 
name="FLRT Report $ts" 
typeset -i system_number 
system_number=0 

############################################################ 
# process arguments 
############################################################ 
while [ $# -gt 0 ] 
do 
 case "$1" in 
 -f) #format 
 shift 
 format=$1 
 ;; 
 *) #host name 
 hostlist="$hostlist $1" 
 ;; 
 esac 
 shift 
done 

if [[ $hostlist = "" ]]; then 
 hostlist="localhost" 
fi 

if [[ $format != "html" ]] && [[ $format != "btext" ]] && [[ $format != "text" ]]; then 
 echo "Error: format must be html, text, or btext" 
 exit 1 
fi 

# need temporary files to hold inventory info 
TMP=/tmp/tmp_inventory_`date +%s`_$$ 
TMPF="/tmp/testQuery$$" 

trap '/bin/rm -f $TMP $TMPF' 0 
trap "exit 2" 1 2 3 13 15 

echo "reportname=$name" > $TMP 

# gather information for inventory file 

first_host="true" 
for host in `echo $hostlist` 
do 
 #check for special vios handling 
 isvios=`echo $host|cut -f1 -d':'` 
 if [[ "$isvios" = "vios" ]]; then # vios processing 
 realhost=`echo $host|cut -f2 -d':'` 
 host=$realhost 
 getVIOS $host 
 AIXVALUE="" 
 else 
 getAIX $host 
 VIOSVALUE="" 
 fi 
 getHost $host 
 #getAIX $host 
 if [[ -z $AIXVALUE && -z $VIOSVALUE ]] 
 then 
 # Non-AIX systems aren't going to support most of the commands we'll be using 
 echo $HOSTNAME does not appear to be an AIX or VIOS partition, cannot continue processing this partition 
 continue; 
 else 
 let system_number+=1 
 # gather data for host 
 #getMHZ $host 
 #getHMC $host 
 #getVIOS $host 
 #getHACMP $host 
 getGPFS $host 
 #getCSM $host 
 # data collected, write to inventory file 
 if [[ $first_host = "true" ]]; then 
 getMTM $host 
 getFW $host 
 first_host="false" 
 echo mtm=$MTMVALUE >> $TMP 
 echo fw=$SFIRMWAREVALUE >> $TMP 
 fi 
 echo p$system_number.parnm=$HOSTNAME >> $TMP 
 echo p$system_number.os=aix >> $TMP 
 if [[ $AIXVALUE != "" ]]; then 
 echo p$system_number.aix=$AIXVALUE >> $TMP 
 fi 
 if [[ $HACMPVALUE != "" ]]; then 
 echo p$system_number.hacmp=$HACMPVALUE >> $TMP 
 fi 
 if [[ $CSMVALUE != "" ]]; then 
 echo p$system_number.csm=$CSMVALUE >> $TMP 
 fi 
 if [[ $VIOSVALUE != "" ]]; then 
 echo p$system_number.vios=$VIOSVALUE >> $TMP 
 fi 
 if [[ $GPFSVALUE != "" ]]; then 
 echo p$system_number.gpfs=$GPFSVALUE >> $TMP 
 fi 

 #$WGET "$FLRTURL/query?format=text&$MHZVALUE$$$HMCVALUE$$$GPFSVALUE$$CSMHAVALUE" -o getflrt.stdout -O getflrt.rpt 
 #process results 
 #processAIX 
 #processFW 
 #processGPFS 
 #processHACMP 
 #processVIOS 
 #processCSM 
 fi 
done 

#echo $TMP 
$TR '\n' '&' < ${TMP} > $TMPF 
echo "&format=$format" >> $TMPF 

URL=${FLRTURL}"/query" 
#echo URL $URL 

#$WGET -nv -O out --post-file=${TMPF} ${URL} 
 $WGET -q -O out --post-file=${TMPF} ${URL} 

cat out 

exit

#/bin/ksh 

# Sample script to update preexisting inventory file to FLRT, and 
# display the results 

if [[ $# -eq 0 ]];then 
 print "usage: flrt_inventory.ksh [inventory file]" 
 print " uploads [inventory file] to FLRT, displays results" 
 exit 
fi 

WGET=`which wget` 

if [[ -z $WGET ]] 
then 
 echo "wget not found, quitting" 
 exit 1 
fi 

FLRTURL="http://www14.software.ibm.com/webapp/set2/flrt" 

TR=/usr/bin/tr 
URL=${FLRTURL}"/query" 
format="text" 
TMPF="/tmp/testQuery$$" 

trap '/bin/rm -f $TMP $TMPF' 0 
trap "exit 2" 1 2 3 13 15 

$TR '\n' '&' < ${1} > $TMPF 
echo "&format=$format" >> $TMPF 

$WGET -q -O out --post-file=${TMPF} ${URL} 

cat out

Link:

Sometimes you need to read it from the disk. There are two ways to fulfill this:

1. Using lquerypv command:

# lquerypv -h /dev/hdisk10 80 10
00000080   00C4469D 5E6002A5 00000000 00000000  |..H.^`..........|

2. Using od command:

# od -A n -j 128 -N 8 -x /dev/hdisk10

00c4 469d 5e60 02a5

• N_Port: An N_Port is an end node port on the Fibre Channel fabric. This could be an HBA (Host Bus Adapter) in a server or a target port on a storage array.
• F_Port: An F_Port is a port on a Fibre Channel switch that is connected to an N_Port. So, the port into which a server’s HBA or a storage array’s target port is connected is an F_Port.
• E_Port: An E_Port is a port on a Fibre Channel switch that is connected to another Fibre Channel switch. The connection between two E_Ports forms an Inter-Switch Link (ISL).

There are other types of ports as well—NL_Port, FL_Port, G_Port, TE_Port—but for the purposes of this discussion these three will get us started. With these definitions in mind, I’ll start by discussing N_Port ID Virtualization (NPIV).

N_Port ID Virtualization (NPIV)

Normally, an N_Port would have a single N_Port_ID associated with it; this N_Port_ID is a 24-bit address assigned by the Fibre Channel switch during the FLOGI process. The N_Port_ID is not the same as the World Wide Port Name (WWPN), although there is typically a one-to-one relationship between WWPN and N_Port_ID. Thus, for any given physical N_Port, there would be exactly one WWPN and one N_Port_ID associated with it.

What NPIV does is allow a single physical N_Port to have multiple WWPNs, and therefore multiple N_Port_IDs, associated with it. After the normal FLOGI process, an NPIV-enabled physical N_Port can subsequently issue additional commands to register more WWPNs and receive more N_Port_IDs (one for each WWPN). The Fibre Channel switch must also support NPIV, as the F_Port on the other end of the link would “see” multiple WWPNs and multiple N_Port_IDs coming from the host and must know how to handle this behavior.

Once all the applicable WWPNs have been registered, each of these WWPNs can be used for SAN zoning or LUN presentation. There is no distinction between the physical WWPN and the virtual WWPNs; they all behave in exactly the same fashion and you can use them in exactly the same ways.

So why might this functionality be useful? Consider a virtualized environment, where you would like to be able to present a LUN via Fibre Channel to a specific virtual machine only:

• Without NPIV, it’s not possible because the N_Port on the physical host would have only a single WWPN (and N_Port_ID). Any LUNs would have to be zoned and presented to this single WWPN. Because all VMs would be sharing the same WWPN on the one single physical N_Port, any LUNs zoned to this WWPN would be visible to all VMs on that host because all VMs are using the same physical N_Port, same WWPN, and same N_Port_ID.
• With NPIV, the physical N_Port can register additional WWPNs (and N_Port_IDs). Each VM can have its own WWPN. When you build SAN zones and present LUNs using the VM-specific WWPN, then the LUNs will only be visible to that VM and not to any other VMs.

Virtualization is not the only use case for NPIV, although it is certainly one of the easiest to understand.

<aside>As an aside, it’s interesting to me that VMotion works and is supported with NPIV as long as the RDMs and all associated VMDKs are in the same datastore. Looking at how the physical N_Port has the additional WWPNs and N_Port_IDs associated with it, you’d think that VMotion wouldn’t work. I wonder: does the HBA on the destination ESX/ESXi host have to “re-register” the WWPNs and N_Port_IDs on that physical N_Port as part of the VMotion process?</aside>

Now that I’ve discussed NPIV, I’d like to turn the discussion to N_Port Virtualization (NPV).

N_Port Virtualization

While NPIV is primarily a host-based solution, NPV is primarily a switch-based technology. It is designed to reduce switch management and overhead in larger SAN deployments. Consider that every Fibre Channel switch in a fabric needs a different domain ID, and that the total number of domain IDs in a fabric is limited. In some cases, this limit can be fairly low depending upon the devices attached to the fabric. The problem, though, is that you often need to add Fibre Channel switches in order to scale the size of your fabric. There is therefore an inherent conflict between trying to reduce the overall number of switches in order to keep the domain ID count low while also needing to add switches in order to have a sufficiently high port count. NPV is intended to help address this problem.

NPV introduces a new type of Fibre Channel port, the NP_Port. The NP_Port connects to an F_Port and acts as a proxy for other N_Ports on the NPV-enabled switch. Essentially, the NP_Port “looks” like an NPIV-enabled host to the F_Port on the other end. An NPV-enabled switch will register additional WWPNs (and receive additional N_Port_IDs) via NPIV on behalf of the N_Ports connected to it. The physical N_Ports don’t have any knowledge this is occurring and don’t need any support for it; it’s all handled by the NPV-enabled switch.

Obviously, this means that the upstream Fibre Channel switch must support NPIV, since the NP_Port “looks” and “acts” like an NPIV-enabled host to the upstream F_Port. Additionally, because the NPV-enabled switch now looks like an end host, it no longer needs a domain ID to participate in the Fibre Channel fabric. Using NPV, you can add switches and ports to your fabric without adding domain IDs.

So why is this functionality useful? There is the immediate benefit of being able to scale your Fibre Channel fabric without having to add domain IDs, yes, but in what sorts of environments might this be particularly useful? Consider a blade server environment, like an HP c7000 chassis, where there are Fibre Channel switches in the back of the chassis. By using NPV on these switches, you can add them to your fabric without having to assign a domain ID to each and every one of them.

Here’s another example. Consider an environment where you are mixing different types of Fibre Channel switches and are concerned about interoperability. As long as there is NPIV support, you can enable NPV on one set of switches. The NPV-enabled switches will then act like NPIV-enabled hosts, and you won’t have to worry about connecting E_Ports and creating ISLs between different brands of Fibre Channel switches.

The procedures are in the Hitachi Dynamic Link Manager User Guide. The installation procedure is basically the same as for a standalone AIX server.

You must use the special VIO command oem_setup_env to get into the root shell to uninstall and reinstall Dynamic Link Manager. The recommended procedure is to shut down the client prior to the upgrade.The virtual (mapped) devices must either be removed or put in a defined state.

You must also be aware that the pvid method of identifying the disks is the default with Dynamic LinkManager version 5.6,however, with Dynamic Link Manager version 5.6.1 the option to specify the unique_id method was available. If you are using unique_id, then no changes are required.
However,if you are using the pvid method, then a backup and restore(orreload) is required.If you have dual VIO servers, you can migrate one server at a time,however, care must be taken to ensure the paths areavailable and
there are no path errors in the client. Also, ensure that you are using the unique_id method of identifying the disks. The reserves must be disabled on all the hdisks prior to remapping the devices for the client partitions.

1. Browse to http://www.ibm.com/systems/power/software/aix/linux/toolbox/alpha.html
2. Search for wget
3. Click the RPM link
4. And it downloads the file:  wget-1.9.1-1.aix5.1.ppc.rpm
5. Move this to your repository or home AIX machine on which you can as root install this package. Or you can directly download it using ftp://ftp.software.ibm.com/aix/freeSoftware/aixtoolbox/RPMS/ppc/wget/wget-1.9.1-1.aix5.1.ppc.rpm
6. Run: rpm -Uvh wget-1.9.1-1.aix5.1.ppc.rpm

Now you can use wget to download AIX patches.

Assume your patches are located at ftp://www7b.boulder.ibm.com/aix/fixes/pkgs/kmjuv/

On the AIX server, go into the repository where you want to hold the patches and run wget at background.

# cd /export/nim/patches/IV22602

# wget -b -o /tmp/IV22602_download.log -nd -r --retr-symlinks ftp://www7b.boulder.ibm.com/aix/fixes/pkgs/kmjuv/

-b, --background go to background after startup.

-o, --output-file=FILE log messages to FILE.

-nd, --no-directories don't create directories.

-r, --recursive recursive download.

Check the log file later to make sure the download is completed successfuly.

Please note you will need to make changes on both VIOS and vLPAR.

Link:

Set up IBM Virtual LPAR as a router using static routing

1. Create an AIX LPAR.

2. VIOS Set in   the Virtual Fibre Channel Adapter servers.

3. In the VIOS identify the new vfchost.

4. Create Virtual Fibre Channel Adapter customers

5. Save the new configuration of the VIOS.

6. Map the vfchost to physical cards.

7. Identifying the WWPNs gives the LPAR created.

8. Configure NIM to install AIX one.

9. Start first LPAR.

10. Check status of vfchost logged_in.

11. Create the area in the S / W SAN.

12. Reset LPAR.

13. Define the disks.

14. The installation starts.

Detail Steps:

1. On the HMC create an AIX LPAR as ever.  On LHEA select IVE card, select a free port (which is not used by another LPAR).

HMC

> Systems Management

> Servers

> POWER Server

> Configuration

> Create Logical Partition

> AIX or Linux

> Complete steps Wizard

Note: It is advisable to set in advance the resources that were used to create the LPAR (CPU, memory, cards, etc..).
2. At HMC go to vionodo1h, then Logial Dynamic Partitioning and create a virtual Fibre Channel adapter ( Virtual Fibre Channel Adapter ) with an identifier not used.

HMC

> Vinodo1h

> Dynamic Logial Partitioning

> Virtual Adapter

> Actions

> Create Virtual Adapter

> Fibre Channel Adapter

vionodo1h: ID 4 to 3 nimsuma with customer ID

vionodo2h: ID nimsuma 4 for 4 with customer ID

3. Then run VIOS cfgdev . If you run lsdev before and after, you should see a new device vfchost .

vionod1h :
$ lsdev | grep ^vfc
vfchost0         Available   Virtual FC Server Adapter
vfchost1         Available   Virtual FC Server Adapter
vfchost2         Available   Virtual FC Server Adapter
vfchost3         Available   Virtual FC Server Adapter
vfchost4         Available   Virtual FC Server Adapter
vfchost6         Available   Virtual FC Server Adapter
vfchost7         Available   Virtual FC Server Adapter
vfchost8         Available   Virtual FC Server Adapter
$ cfgdev

$ lsdev | grep ^vfc
vfchost0         Available   Virtual FC Server Adapter
vfchost1         Available   Virtual FC Server Adapter
vfchost2         Available   Virtual FC Server Adapter
vfchost3         Available   Virtual FC Server Adapter
vfchost4         Available   Virtual FC Server Adapter
vfchost5         Available   Virtual FC Server Adapter <–
vfchost6         Available   Virtual FC Server Adapter
vfchost7         Available   Virtual FC Server Adapter
vfchost8         Available   Virtual FC Server Adapter

vionodo2h:
$ lsdev | grep ^vfc
vfchost0         Available   Virtual FC Server Adapter
vfchost1         Available   Virtual FC Server Adapter
vfchost3         Available   Virtual FC Server Adapter
vfchost4         Available   Virtual FC Server Adapter
vfchost6         Available   Virtual FC Server Adapter
vfchost7         Available   Virtual FC Server Adapter
vfchost9         Available   Virtual FC Server Adapter
$ cfgdev

$ lsdev | grep ^vfc
vfchost0         Available   Virtual FC Server Adapter
vfchost1         Available   Virtual FC Server Adapter
vfchost2         Available   Virtual FC Server Adapter <–
vfchost3         Available   Virtual FC Server Adapter
vfchost4         Available   Virtual FC Server Adapter
vfchost6         Available   Virtual FC Server Adapter
vfchost7         Available   Virtual FC Server Adapter
vfchost9         Available   Virtual FC Server Adapter
4. On the profile of the LPAR created in step 1, create a new virtual Fibre Channel adapter and generate one with the identifier and VIOS Part 2. Check which is required for the LPAR start.

HMC

> nimsuma

> Configuration

> Manage Profiles

> Default

> Virtual Adapters

> Actions

> Create Virtual Adapter

> Fiber Channel Adapter

Adapter # 3 Adapter VIO vionodo1h ID 4. 
Adapter # 4, VIO vionodo2h ID adapter 4.

> OK

> Close

5. Save the current profile settings as Default VIO server to keep it restarts if a VIOS.

HMC

> Vionodo1h

> Configuration

> Save Configuration Courrent

> Acceptance 

HMC

> Vionodo2h

> Configuration

> Save Configuration Courrent

> Acceptance

6. VIOS Map out in the command vfcmap , alternating fcs0 and fcs1 .

vionodo1h:

$ Vfcmap-vadapter vfchost5-fcp fcs1 
$ lsmap-NPIV-vadapter vfchost5 
Name Physloc ClntID ClntName ClntOS 
------------------------------ -------------------------------------------- 
vfchost5 U8233.E8B.065864P -V1-C4 3                 

Status: Not_logged_in 
FC name: fcs1 FC loc code: U78A0.001.DNWK388-P1-C1-T2 
Ports logged in: 0 
Flags: 4 <NOT_LOGGED> 
VFC client name: VFC client DRC:

vionodo2h:

$ Vfcmap-vadapter vfchost2-fcp fcs0   
$ lsmap-NPIV-vadapter vfchost2 
Name Physloc ClntID ClntName ClntOS 
------------------------------ -------------------------------------------- 
vfchost2 U8233.E8B.065864P -V2-C4 3                 

Status: Not_logged_in 
FC name: fcs0 FC loc code: U78A0.001.DNWK388-P1-C3-T1 
Ports logged in: 0 
Flags: 4 <NOT_LOGGED> 
VFC client name: VFC client DRC:

7. Goto the WWPNs Storage corresponding to the LPAR created:

HMC

> Select the LAPR the first step

> Configuration

> Manage Profiles

> Choose Default

> Virtual Adapters

> Client Fibre Channel vionodo1h

> Actions

> Properties

> WWPNs: c050760376c40064

7.1 Repeat the same procedure goes for vionodo2h

8. Configure NIM to install AIX one.

# Vi / etc / hosts -> add the name of the LPAR of step 1 and IP available.

10.1.4.253       nimsuma

# Smitty nim

> Perform Nim Administration Tasks

> Manage Machines

> Define a Machine

# smitty nim

> Perform Nim Administration Tasks

> Define a Resource

> spot

# Smitty nim_bosinst

> Select the client we previously defined.

> Select Installation Type: “spot - Install a SPOT copy”

> Select the SPOT to use for the installation    

> Set “ACCEPT new license agreements?” to yes

> Set “Initiate reboot and installation now?” to no

9. Start LPAR in SMS mode and configure the network with the same IP that is in the / etc / hosts on the NIM, in order to start (boot ) from him.

A. Select 2 for setup remote IPL.

B. Select 1 for first ethernet.

C. Select 1 for IPV4.

D. Select 1 for bootp.

E. Select 1 for IP parameters.

1.  client: 10.1.4.253

2.  server: 10.1.4.254

3.  Gateway: 10.1.4.11

4.  Subnet: 255.255.255.0

F. Hit ESC.

10. Execute command on VIOS NPIV-vAdapter lsmap-vfchostX , to see that the state is logged_in.

11. The Storage area should modify now the space for integrating the new LPAR.

In the Fabric

Aliases are created:

nimsuma_hba1

c0:50:76:03:76:c4:00:66

nimsuma_hba2

c0:50:76:03:76:c4:00:64

Zones are created:

v7000nimsumahba1

nimsuma_hba1; stg_v70001; stg_v70002; stg_v70003; stg_v70004

v7000nimsumahba2

nimsuma_hba2; stg_v70001; stg_v70002; stg_v70003; stg_v70004

12. Reset LPAR.

13. At this time “We” visible from the disk enclosure. Storage coach proceeds to perform the necessary definitions in the storage unit.

In V7000

It creates the host:

nimsuma 

c0:50:76:03:76:c4:00:66

c0:50:76:03:76:c4:00:64

Volumes are created:

nimsuma_rootvg

20 GB - NL_SAS

nimsuma_datos

50 GB - NL_SAS

14. Starts installation.

A. Select 1 for boot device.

B. Select 6 for network.

C. Select 1 for bootp.

D. Select 1 for first ethernet.

E. Select 2 for normal boot mode.

F. Select 1 for yes I want to exit tftp should now start up.

G. After around 30,000 packets the console prompt should appear as follows:

Select 1 for English during install.

Notes:

The LPAR created in this example the call nimsuma . To implement NPIV on POWER environment is necessary to use VIO Server, in this case our VIOS called vionodo1h and vionodo2h (redundant). The Storage used was an IBM SW V7000, in which we created two LUNs, one for the installation called nimsuma_rootvg and one for data call nimsuma_datos .

How can I log NPIV WWPN into SAN switch before AIX installation on the VIO LPAR that is using NPIV LUN boot?

Answer:

There are a few methods you can use:

Method 1:

Allocate the NIM lpp_source and SPOT resources to the new LPAR on NIM server.

Start up the new LPAR and boot it from network

When it reaches the installation menu, the WWPNs of virtual adapters will login into SAN switch.

Method 2:

Boot the LPAR, press 8 to get into firmware mode.

> ioinfo

Select 6 for FC Adapter
Then Select the HBA you want, then run the list devices, which will return you login & Devices if any

Note: You can only login one virtual adapter at one time.

Method 3:

chnportlogin and lsnportlogin – Login in Virtual Fibre Channel adapters for NPIV client LPARs

There are two new HMC (V7.7.3.0) commands that can force a client Virtual Fibre Channel adapter to log into a SAN. This should make the life of the AIX and SAN administrator easier, as they will no longer need to install AIX in order for the new VFC adapters to log into the SAN. Although there was an unsupported method* for doing this already (see links below). Nor will the SAN admins need to “blind” zone the WWPNs.

 There was some indication of this in the latest VIOS FP readme:

https://www-304.ibm.com/support/docview.wss?rs=0&uid=isg400000693

• Enabled SAN login from VIOS

And there was this:

IZ95569: ENABLE SAN LOGIN FROM VIOS FOR IMPROVED UABILITY

https://www-304.ibm.com/support/docview.wss?uid=isg1IZ95569

Problem summary

• Customer will be able to instruct the VIOS to login to the SAN
• for a given WWPN on a given virtual adapter to allow the
• customer to see the WWPN in SAN management tools and easing
• the task of configuring new NPIV client
• partitions.

Problem conclusion

• add commands to VIOS manager interface to allow the HMC to
• login, logout and query virtual adapters.

And the manpage of these commands:

chnportlogin:  http://pic.dhe.ibm.com/infocenter/powersys/v3r1m5/index.jsp?topic=/p7edm/chnportlogin.html

lsnportlogin:   http://pic.dhe.ibm.com/infocenter/powersys/v3r1m5/index.jsp?topic=/p7edm/lsnportlogin.html
The new lsnportlogin and chnportlogin commands on the 7.730 HMC provide the ability to utilize the new function in the VIOS. From the Readme:

Added the chnportlogin and lsnportlogin commands.

1.  The chnportlogin command allows you to perform N Port login and logout operations for virtual fibre channel client adapters that are configured in a partition or a partition profile. Use this command to help you in zoning WWPNs on a Storage Area Network (SAN). A login operation activates all inactive WWPNs, including the second WWPN in the pair assigned to each virtual fibre channel client adapter. This feature is particularly useful for Logical Partition Migration. A logout operation deactivates all WWPNs not in use. A successful login of a virtual fibre channel adapter requires that the corresponding virtual fiber channel server adapter must exist and that it must be mapped.

2.  The lsnportlogin command also allows you to list WWPN login status information for virtual fibre channel client adapters configured in partitions or partition profiles.

Here’s an example of using the lsnportlogin command on one of my systems:

hscroot@HMC1:~>  lsnportlogin -m  770-frame-1 –filter “profile_names=normal”

lpar_name=nim1,lpar_id=3,profile_name=normal,slot_num=32,wwpn=c060760405f0000c,wwpn_status=0

lpar_name=nim1,lpar_id=3,profile_name=normal,slot_num=32,wwpn=c060760405f0000d,wwpn_status=0

lpar_name=nim1,lpar_id=3,profile_name=normal,slot_num=33,wwpn=c060760405f0000e,wwpn_status=0

lpar_name=nim1,lpar_id=3,profile_name=normal,slot_num=33,wwpn=c060760405f0000f,wwpn_status=0

lpar_name=nim1,lpar_id=3,profile_name=normal,slot_num=30,wwpn=c060760405f00000,wwpn_status=0

lpar_name=nim1,lpar_id=3,profile_name=normal,slot_num=30,wwpn=c060760405f00001,wwpn_status=0

lpar_name=nim1,lpar_id=3,profile_name=normal,slot_num=31,wwpn=c060760405f00002,wwpn_status=0

lpar_name=nim1,lpar_id=3,profile_name=normal,slot_num=31,wwpn=c060760405f00003,wwpn_status=0

lpar_name=aix01adm,lpar_id=4,profile_name=normal,slot_num=32,wwpn=c060760405f00004,wwpn_status=0

lpar_name=aix01adm,lpar_id=4,profile_name=normal,slot_num=32,wwpn=c060760405f00005,wwpn_status=0

lpar_name=aix01adm,lpar_id=4,profile_name=normal,slot_num=33,wwpn=c060760405f00006,wwpn_status=0

lpar_name=aix01adm,lpar_id=4,profile_name=normal,slot_num=33,wwpn=c060760405f00007,wwpn_status=0

lpar_name=aix01adm,lpar_id=4,profile_name=normal,slot_num=30,wwpn=c060760405f00008,wwpn_status=0

lpar_name=aix01adm,lpar_id=4,profile_name=normal,slot_num=30,wwpn=c060760405f00009,wwpn_status=0

lpar_name=aix01adm,lpar_id=4,profile_name=normal,slot_num=31,wwpn=c060760405f0000a,wwpn_status=0

lpar_name=aix01adm,lpar_id=4,profile_name=normal,slot_num=31,wwpn=c060760405f0000b,wwpn_status=0

Descriptions of selected command attributes:

wwpn_status

The WWPN status.  Possible values are:

0 – WWPN is not activated

1 – WWPN is activated

2 – WWPN status is unknown

I am trying to perform Live Partition Mobility on my LPAR and it fails with HSCLA27C error on my HMC.

Symptom

Cause

Environment

Diagnosing the problem

This document describes how you can copy files to a rootvg filesystem in Service Mode for situations where AIX or the Virtual I/O Server is failing to boot.
Applies to VIOS 2.1 and above.

Cause

Answer

This technote describes how to troubleshoot a hung process or command on PowerVM Virtual I/O Server before resorting to potentially having to force a system dump.

Environment

Diagnosing the problem

Resolving the problem

This technote describes how to capture truss data to further investigate failures of padmin CLI on a Virtual I/O Server partition at the request of VIOS SupportLine.
This applies to VIOS 2.x.

Answer

I am trying to perform Live Partition Mobility on my LPAR and it fails with HSCLA24E error on my HMC.

Symptom

Cause

Environment

Diagnosing the problem

Resolving the problem

What is NPIV?

NPIV is an industry standard technology that provides the capability to assign a
physical Fibre Channel adapter to multiple unique world wide port names
(WWPN). To access physical storage from a SAN, the physical storage is
mapped to logical units (LUNs) and the LUNs are mapped to the ports of physical
Fibre Channel adapters. Then the Virtual I/O Server uses the maps to connect
the LUNs to the virtual Fibre Channel adapter of the virtual I/O client.

Symptom

Environment

Diagnosing the problem

Resolving the problem

1. Make sure you have PuTTY installed on your PC before installing Xming. In your putty config, make sure you enable X11 forwarding in Connection->SSH ->X11.

2. Then on your PC run Xlaunch, and make sure to set your DISPLAY to a higher value, for example “10″ and to check “No Access Control”.

3. Make sure you have X11Forwarding enabled in the sshd config. Your /etc/ssh/sshd_config should contain something like this:

X11DisplayOffset 10
X11Forwarding yes
X11UseLocalhost yes
XAuthLocation /usr/bin/X11/xauth

Restart sshd if you have to make the change to /etc/ssh/sshd_config:
stopsrc -s sshd ; startsrc -ssshd

4. Log in to the UNIX host through PuTTY.

Test, run xclock :

# xclock &

The program xclock should open on your window.

5. Now, how do you get around opening an X window if you have to go through a jumpserver first to get to the correct UNIX server, where you would like to start an X-based program? That’s not too difficult also. After logging in on the UNIX jumpserver, following the procedure described above, issue the following command:

# ssh -X -Y -C otherunixhost

Of course, replace “otherunixhost” with the hostname of the UNIX server you’d like to connect to through your jump server. Then, again, to test, run  ”xclock” to test. It should open on your PC. Now you have X11 forwarding from a UNIX server, to a jumpserver, and back to your PC, in fact double X11 forwarding.