AIX 6.1 WPAR Commands

Most of these commands are only runable by root user for the Global LPAR (Global
Environment).

chwpar Modifies dynamically the configuration options of the WPAR even when it is
running.

clogin Provides a mechanism for the root user to log in or run a command within a
workload partition. The “clogin” command uses a pseudo-terminal allocated on
the Global Environment (see in the mobility part the impact of this) and creates
a login shell running which belongs to the workload partition.

lswpar Prints information about WPARs

mkwpar Specific for System WPAR - Builds the infrastructure and the configuration
file. Then it creates and populates the WPARs file systems. Allocate the
specified resources as well as the WLM information (if any) and eventually
starts it. Specifying whether the workload partitions should be automatically
started on system boot or when /etc/rc.wpars is executed.

startwpar Activates the System WPAR defined with mkwpar

wparexec Specific for Application WPAR – Builds, create specification file and
eventually starts the Application WPAR

rebootwpar Stops and resumes a System Workload Partition. It cannot be run within a
WPAR

rmwpar Deletes the specified Workload Partition from the system as well as its
configuration and its WLM profile

stopwpar Kills the WPAR and deallocate all resources belonging to it. It removes the
Application WPAR

syncwpar Specific to System WPAR - Synchronizes the software installed in the global
shared parts (usually /usr and /opt) with the workload partition's root part

Note: The mkwpar and chwpar can update the global file /etc/wpars:

Note: /etc/rc.wpars: Specific to System WPAR - this script is run at main system boot it
invokes the startwpar command on all workload partitions with the autostart option.
Some commands have different or enhanced behavior in a WPAR environment. The list
includes acctcom, acctctl, df, domainname, hosted, hostname, ifconfig, ioo, ipcrm, ipcs,
mkclass, mount, netstat, nfso, no, projctl, ps , schedo, uname, vmo, wlmstat, wlmtune,
wlmcntrl. This change is described in the AIX 6 documentation.

The simplest way to administrate WPARs using command lines (CLI) is to issue the
command smitty wpar which will provide the interface to these commands.

Server Snapshots: IBM p570 Power 6

The IBM POWER6 processor-based System p570 is a midrange server that aims to deliver outstanding price/performance while providing mainframe-like reliability and availability. This 19-inch rack-mount system, which can handle up to 16 POWER6 cores, is best-suited to database and application serving, as well as server consolidation.
"The first server to use the new POWER6 processor is the System p570," said Jeff Howard, director of System p offering management for IBM (Armonk, N.Y.). "The p570 leverages the chip's many breakthroughs in energy conservation and virtualization technology."

POWER6 Packs a Punch
The modular p570 takes over from its predecessor, the IBM POWER5+ processor-based System p5 570 server. POWER6 processors can run 64-bit applications while concurrently supporting 32-bit applications. They feature simultaneous multithreading, allowing two application threads to be run at the same time.
"At 4.7 GHz, the dual-core POWER6 processor doubles the speed of the previous generation, POWER5, while using the same amount of electricity to run and cool it," said Howard. "This means customers can use the new processor to either increase their performance by 100 percent or cut their power consumption in half."
Dan Olds, principal of Oregon-based Gabriel Consulting Group, believes the p570/POWER6 combo is an impressive one. The new processors come in 3.5 GHz, 4.2 GHz and 4.7 GHz flavors. IBM has effectively doubled the frequency over its predecessor without increasing the number of cores on the chip.

p570 close up

The POWER6 [processor] has two cores, each of which can simultaneously execute two threads, an approach known as simultaneous multithreading (SMT)," said Gordon Haff, an analyst at Illuminata (Nashua, N.H.). "POWER6 processors also have integrated memory controllers in order to improve memory access times and thereby application performance."
He pointed out that changes in the way POWER6 processors connect to each other and to the rest of the system flatten latency differences. There are also new specialized execution units and reliability features. Compute power is able to double largely because POWER6 has more than 790 million transistors compared to 276 million in the POWER5+. The amount of Level 2 Cache has gone up to 8 MB from just under 2 MB.
More to Come
While POWER6 has been released and is functioning currently in data centers, it is not quite a finished article. IBM is introducing more features later this year, such as Live Partition Mobility and Live Partition Migration. Live Partition Mobility, for example, will move a running Logical Partition (LPAR) from one physical server to another. It functions below the level of the operating system, at the hypervisor level; works only with the upcoming AIX 6 (currently in beta), AIX 5.3, and Linux; and the servers must all be on the same network subnet.
Haff said AIX 6 contains several major new features, including role-based access controls, a Trusted installation option and new "Workload Partitions" (WPAR). WPAR are resource groups similar to Solaris Containers or virtual servers that can be migrated from one server to another.
"I think that enhancements to the overall system, particularly the Live Partition Mobility feature, are big news and will provide the most business value to customers," said Olds. "With Live Partition Mobility, IBM users can move active workloads from one physical server to another — with no application interruption, no loss of transactions, and no user impact."
Gaining Ground
With such functions added to the already impressive POWER6, Olds believes the IBM p570 will gain major ground in the marketplace.
"This arguably means the end of planned application downtime and can eliminate perhaps half of overall application downtime, which is a big deal," said Olds. "This is much more sophisticated than VMware's VMotion and is a feature that their competitors will need to address."
Howard of IBM boasted that the POWER6 chip is nearly three times faster than the latest HP Itanium processor that runs much of HP's midrange server line. Thus, it will likely reinforce IBM's lead in the Unix servers market. According to research firm IDC (Framingham, Mass.), the company has a 29.6 percent revenue share in Unix.
"The p570 is the first server to hold all four major benchmark speed records for business and technical performance," said Howard. "In fact, the System p 570 now holds more than 20 benchmark records."
The p570 currently supports AIX 5L (v5.2 or later), the upcoming AIX 6, as well as Linux distributions from Red Hat (RHEL 4 Update 5 or later) and SUSE Linux (v10 SP1 or later).
The starting price for a basic version of the server is $60,000. IBM was reluctant to give out more details of pricing and configurations. Per its Web site, the minimum is a 2-core version operating at 3.5 GHz, so presumably that is what is obtained for this price. Each p570 building block accommodates two processor cards, each of which provides two 64-bit POWER6 processor cores, 8 MB of Level 2 (L2) cache and 32 MB of Level 3 (L3) cache. Each processor card has 12 slots for DDR2 (double data rate 2) ECC memory DIMMs, providing memory capacity of up to 192 GB per building block.


p570 Close Up

Name p 570
Vendor IBM
Platform Power6
Dimensions 4U rackmount; 19" by 32.4" by 6.85"; Weight: 140 lb
Processor Details 2- to 16-core POWER6
Hard Drives Six hot-swappable SAS disk bays per building block provide up to 7.2 TB of internal disk storage, up to four building blocks
Operating Systems Supported by AIX 5L (V5.2 or later) and Linux distributions from Red Hat (RHEL 4 Update 5 or later) and SUSE Linux (V10 SP1 or later) operating systems; AIX6 is in beta
Configuration Options The base configuration starts at $60,000 for a 2-core processor, 3.5 GHz, 64MB L3 cache, 16 GB system memory, and 2 x 73.4GB SAS 15K rpm internal storage. A high-end, system begins at $2 million before IBM discounts. This is a 16-core version running at 4.7 GHz.
GA Now available
Warranty Three years

Changing WPAR properties & starting it in Verbose mode.

====================================================

1 To modify the host name of the workload partition called roy, enter the following command:

chwpar -h roy.com roy
2 To remove a network address from the workload partition called dale, enter the following command:

chwpar -K -N address=219.81.45.65 dale
3 To disable resource controls in the workload partition called wayne while retaining the settings for future use, enter the following command:

chwpar -R active=no wayne
4 To remove the device /dev/foo, exported by default through the devexportsFile, from a workload partition, enter the following command:

chwpar -D globaldev=/dev/foo export=no moore
5 To export the device /dev/bar, permitted by the devexportsFile but not exported, enter the following command:

chwpar -D globaldev=/dev/bar export=yes moore
6 To rename the workload partition from moore to hart, enter the following command:

chwpar -n hart moore
=========================================================



To start WPAR in verbose mode.

tarting workload partition MyTestWpar3.
Mounting all workload partition file systems.
Mounting /wpars/MyTestWpar3
Mounting /wpars/MyTestWpar3/home
Mounting /wpars/MyTestWpar3/opt
Mounting /wpars/MyTestWpar3/proc
Mounting /wpars/MyTestWpar3/tmp
Mounting /wpars/MyTestWpar3/usr
Mounting /wpars/MyTestWpar3/var
Loading workload partition.
$corral_t = {
'name' => 'MyTestWpar3',
'wlm_cpu' => [
undef,
undef,
undef,
undef
],
'path' => '/wpars/MyTestWpar3',
'hostname' => 'MyTestWpar3',
'wlm_procVirtMem' => [
-1,
undef
],
'wlm_mem' => [
undef,
undef,
undef,
undef
],
'key' => 5,
'vips' => [
[
'en0',
'172.29.138.24',
'255.255.192.0',
'172.29.191.255'
]
],
'wlm_rset' => undef,
'opts' => 4,
'id' => 0
};
Exporting workload partition devices.
Starting workload partition subsystem cor_MyTestWpar3.
0513-059 The cor_MyTestWpar3 Subsystem has been started. Subsystem PID is 536778.
Verifying workload partition startup.
Return Status = SUCCESS.
lpar47p682e_pub[/] >
-------------------------------------------------------

To remove WPAR from command line.

par47p682e_pub[/] > rmwpar TestWpar3
rmwpar: Removing file system /wpars/TestWpar3/var.
rmlv: Logical volume fslv15 is removed.
rmwpar: Removing file system /wpars/TestWpar3/usr.
rmwpar: Removing file system /wpars/TestWpar3/tmp.
rmlv: Logical volume fslv14 is removed.
rmwpar: Removing file system /wpars/TestWpar3/proc.
rmwpar: Removing file system /wpars/TestWpar3/opt.
rmwpar: Removing file system /wpars/TestWpar3/home.
rmlv: Logical volume fslv13 is removed.
rmwpar: Removing file system /wpars/TestWpar3.
rmlv: Logical volume fslv12 is removed.


To remove WPAR first we need to stop WPAR in order to remove it.
After removing WPAR all filesystem related to that WPAR gets deleted.

Creating WPAR on command line.

==========================================

1 To create a workload partition called roy, enter the following command:

mkwpar -n roy -N address=192.168.0.51
All values that are not specified are generated or discovered from the global system's settings.
2 To create a workload partition based on an existing specification file, enter the following command:

mkwpar -f /tmp/wpar1.spec
3 To create a modified copy of a specification file with a new IP address, host name, and workload partition name (without creating a workload
partition), enter the following command:

mkwpar -f /tmp/wpar1.spec -N address=219.168.45.132 -h www.flowers.com -n wpar2
-o /tmp/wpar2.spec -w
4 To create a new specification file based on an existing workload partition, enter the following command:

mkwpar -e wpar1 -o /tmp/wpar2.spec -w
5 To recreate a workload partition that was previously removed with the rmwpar -p command, enter the following command:

mkwpar -p wparname

==========================================================
Actual WPAR creation screen shots.

par47p682e_pub[/] > mkwpar -n MyTestWpar2 -N ip= xyz
mkwpar: Creating file systems...
/
/home
/opt

/proc
/tmp
/usr
/var
Mounting all workload partition file systems.
x ./usr
x ./lib
x ./admin
x ./admin/tmp
x ./audit
x ./dev
x ./etc
x ./etc/check_config.files
x ./etc/consdef
x ./etc/cronlog.conf
x ./etc/csh.cshrc
x ./etc/csh.login
x ./etc/dlpi.conf
x ./etc/dumpdates
x ./etc/environment
x ./etc/ewlm
x ./etc/ewlm/limits
x ./etc/ewlm/trc
x ./etc/ewlm/trc/config_schema.xsd
x ./etc/ewlm/trc/output_schema.xsd
x ./etc/filesystems
x ./etc/group
x ./etc/inittab
x ./etc/magic
x ./etc/motd
x ./etc/nscontrol.conf
x ./etc/objrepos
x ./etc/objrepos/CDiagAtt
x ./etc/objrepos/CDiagAtt.vc
x ./etc/objrepos/CDiagDev
x ./etc/objrepos/Config_Rules
x ./etc/objrepos/CuAt
x ./etc/objrepos/CuAt.vc
x ./etc/objrepos/CuDep
x ./etc/objrepos/CuDv
x ./etc/objrepos/CuDvDr
x ./etc/objrepos/CuPath
x ./etc/objrepos/CuPath.vc
x ./etc/objrepos/CuPathAt
x ./etc/objrepos/CuPathAt.vc
x ./etc/objrepos/CuVPD
x ./etc/objrepos/CuData
x ./etc/objrepos/CuData.vc
x ./etc/objrepos/DAVars
x ./etc/objrepos/FRUB
x ./etc/objrepos/FRUB_SRC
x ./etc/objrepos/FRUs
x ./etc/objrepos/FRUs_src
x ./etc/objrepos/MenuGoal
x ./etc/objrepos/SRCextmeth
x ./etc/objrepos/SRCnotify
x ./etc/objrepos/SRCsubsvr
x ./etc/objrepos/SRCsubsys
x ./etc/objrepos/SWservAt
x ./etc/objrepos/SWservAt.vc
x ./etc/objrepos/TMInput
x ./etc/objrepos/errnotify
x ./etc/objrepos/history
x ./etc/objrepos/history.vc
x ./etc/objrepos/inventory
x ./etc/objrepos/inventory.vc
x ./etc/objrepos/lpp
x ./etc/objrepos/lpp.vc
x ./etc/objrepos/product
x ./etc/objrepos/product.vc
x ./etc/passwd
x ./etc/profile
x ./etc/project
x ./etc/project/projdef
x ./etc/pse.conf
x ./etc/pse_tune.conf
x ./etc/qconfig
x ./etc/rc
x ./etc/rc.C2
x ./etc/rc.CC
x ./etc/rc.dacinet
x ./etc/rc.d
x ./etc/rc.d/init.d
x ./etc/rc.d/rc
x ./etc/rc.d/rc2.d
x ./etc/rc.d/rc3.d
x ./etc/rc.d/rc4.d
x ./etc/rc.d/rc5.d
x ./etc/rc.d/rc6.d
x ./etc/rc.d/rc7.d
x ./etc/rc.d/rc8.d
x ./etc/rc.d/rc9.d
x ./etc/rc.ha_star
x ./etc/rc.powerfail
x ./etc/rc.security.boot
x ./etc/security
x ./etc/security/acl
x ./etc/security/audit
x ./etc/security/audit/bincmds
x ./etc/security/audit/config
x ./etc/security/audit/events
x ./etc/security/audit/objects
x ./etc/security/audit/streamcmds
x ./etc/security/authorizations
x ./etc/security/privcmds
x ./etc/security/privdevs
x ./etc/security/environ
x ./etc/security/group
x ./etc/security/lastlog
x ./etc/security/ldap
x ./etc/security/ldap/2307aixgroup.map
x ./etc/security/ldap/2307aixuser.map
x ./etc/security/ldap/2307group.map
x ./etc/security/ldap/2307user.map
x ./etc/security/ldap/aixgroup.map
x ./etc/security/ldap/aixid.map
x ./etc/security/ldap/aixuser.map
x ./etc/security/ldap/ldap.cfg
x ./etc/security/ldap/ldapid.ldif.template
x ./etc/security/ldap/nisSchema.ldif
x ./etc/security/ldap/proxy.ldif.template
x ./etc/security/ldap/sec.ldif
x ./etc/security/ldap/sectoldif.cfg
x ./etc/security/ldap/sfu20group.map
x ./etc/security/ldap/sfu20user.map
x ./etc/security/ldap/sfu30group.map
x ./etc/security/ldap/sfu30user.map
x ./etc/security/ldap/sfur2group.map
x ./etc/security/ldap/sfur2user.map
x ./etc/security/limits
x ./etc/security/login.cfg
x ./etc/security/passwd
x ./etc/security/portlog
x ./etc/security/priv
x ./etc/security/privfiles
x ./etc/security/.profile
x ./etc/security/pwdalg.cfg
x ./etc/security/roles
x ./etc/security/services
x ./etc/security/smitacl.group
x ./etc/security/smitacl.user
x ./etc/security/sysck.cfg
x ./etc/security/user
x ./etc/security/user.roles
x ./etc/shells
x ./etc/swapspaces
x ./etc/trcfmt.Z
x ./etc/tsh_profile
x ./etc/uucp
x ./etc/uucp/Devices
x ./etc/uucp/Dialers
x ./etc/vfs
x ./etc/vg
x ./etc/xtiso.conf
x ./etc/wlm
x ./etc/wlm/standard
x ./etc/wlm/current
x ./etc/wlm/standard/README
x ./etc/wlm/standard/classes
x ./etc/wlm/standard/limits
x ./etc/wlm/standard/shares
x ./etc/wlm/standard/rules
x ./etc/wlm/template
x ./etc/wlm/template/classes
x ./etc/wlm/template/limits
x ./etc/wlm/template/shares
x ./etc/wlm/template/rules
x ./etc/wlm/template/description
x ./u
x ./lost+found
x ./lpp
x ./mnt
x ./opt
x ./proc
x ./sbin
x ./sbin/comp.kext
x ./sbin/comp.uext
x ./sbin/comp.uext64
x ./sbin/rc.boot
x ./sbin/helpers
x ./sbin/helpers/v3fshelper
x ./sbin/helpers/udfmnthelp
x ./sbin/helpers/jfs2
x ./sbin/helpers/jfs2/backbyinode
x ./sbin/helpers/jfs2/chfs
x ./sbin/helpers/jfs2/chfs64
x ./sbin/helpers/jfs2/crfs
x ./sbin/helpers/jfs2/defragfs
x ./sbin/helpers/jfs2/diskusg
x ./sbin/helpers/jfs2/dumpfs
x ./sbin/helpers/jfs2/ff
x ./sbin/helpers/jfs2/fsck
x ./sbin/helpers/jfs2/fsck64
x ./sbin/helpers/jfs2/fscklog
x ./sbin/helpers/jfs2/fsdb
x ./sbin/helpers/jfs2/fstype
x ./sbin/helpers/jfs2/istat
x ./sbin/helpers/jfs2/logform
x ./sbin/helpers/jfs2/logredo
x ./sbin/helpers/jfs2/logredo64
x ./sbin/helpers/jfs2/lsfs
x ./sbin/helpers/jfs2/mkfs
x ./sbin/helpers/jfs2/mount
x ./sbin/helpers/jfs2/umount
x ./sbin/helpers/jfs2/ncheck
x ./sbin/helpers/jfs2/quotacheck
x ./sbin/helpers/jfs2/rdump
x ./sbin/helpers/jfs2/restbyinode
x ./sbin/helpers/jfs2/rollback
x ./sbin/helpers/jfs2/rrestore
x ./sbin/helpers/jfs2/snapshot
x ./sbin/helpers/jfs2/backsnap
x ./sbin/helpers/jfs2/statfs64
x ./tmp
x ./tmp/lost+found
x ./bin
x ./etc/drivers
x ./etc/methods
x ./etc/microcode
x ./etc/objrepos/DSMOptions
x ./etc/objrepos/DSMOptions.vc
x ./etc/objrepos/DSMenu
x ./etc/objrepos/PDiagRes
x ./etc/objrepos/PDiagRes.vc
x ./etc/objrepos/PDiagTask
x ./etc/objrepos/PDiagTask.vc
x ./etc/objrepos/PDiagAtt
x ./etc/objrepos/PDiagAtt.vc
x ./etc/objrepos/PDiagDev
x ./etc/objrepos/PDiagDev.vc
x ./etc/objrepos/PdAt
x ./etc/objrepos/PdAt.vc
x ./etc/objrepos/PdAtXtd
x ./etc/objrepos/PdAtXtd.vc
x ./etc/objrepos/PdCn
x ./etc/objrepos/PdDv
x ./etc/objrepos/PdDv.vc
x ./etc/objrepos/PdPathAt
x ./etc/objrepos/PdPathAt.vc
x ./etc/methods.cfg
x ./etc/security/mkuser.default
x ./etc/security/mkuser.sys
x ./etc/security/fpm
x ./etc/security/fpm/custom
x ./etc/security/fpm/custom/high
x ./etc/security/fpm/custom/med
x ./etc/security/fpm/custom/default
x ./etc/security/fpm/data
x ./etc/security/fpm/data/high_fpm_list
x ./etc/security/fpm/data/med_fpm_list
x ./etc/security/fpm/data/default_fpm_list.example
x ./etc/security/fpm/data/status_fpm
x ./etc/dtappintegrate
x ./etc/init
x ./var
x ./var/adm
x ./var/adm/cron
x ./var/adm/cron/at.deny
x ./var/adm/cron/cron.deny
x ./var/adm/cron/log
x ./var/adm/cron/queuedefs
x ./var/adm/ras
x ./var/adm/ras/raspertune
x ./var/adm/ras/codepoint.cat
x ./var/adm/ras/platform
x ./var/adm/streams
x ./var/adm/sw
x ./var/adm/sw/tmp
x ./var/adm/sw/tmp/bos.rte.ILS
x ./var/adm/sw/tmp/bos.rte.bind_cmds
x ./var/adm/sw/tmp/bos.rte.console
x ./var/adm/sw/tmp/bos.rte.date
x ./var/adm/sw/tmp/bos.rte.edit
x ./var/adm/sw/tmp/bos.rte.iconv
x ./var/adm/sw/tmp/bos.rte.install
x ./var/adm/sw/tmp/bos.rte.libc
x ./var/adm/sw/tmp/bos.rte.libcfg
x ./var/adm/sw/tmp/bos.rte.libcur
x ./var/adm/sw/tmp/bos.rte.libpthreads
x ./var/adm/sw/tmp/bos.rte.loc
x ./var/adm/sw/tmp/bos.rte.methods
x ./var/adm/sw/tmp/bos.rte.misc_cmds
x ./var/adm/sw/tmp/bos.rte.mlslib
x ./var/adm/sw/tmp/bos.rte.net
x ./var/adm/sw/tmp/bos.rte.odm
x ./var/adm/wtmp
x ./var/locks
x ./etc/locks
x ./var/lost+found
x ./var/msgs
x ./var/news
x ./var/preserve
x ./var/security/fpm
x ./var/security/fpm/log
x ./var/spool
x ./var/spool/cron
x ./var/spool/cron/atjobs
x ./var/spool/cron/crontabs
x ./var/spool/cron/crontabs/adm
x ./var/spool/cron/crontabs/root
x ./var/spool/cron/crontabs/sys
x ./var/spool/lpd
x ./var/spool/lpd/qdir
x ./var/spool/lpd/stat
x ./var/spool/mqueue
x ./var/spool/qdaemon
x ./var/spool/writesrv
x ./var/tmp
x ./etc/pam.conf
x ./etc/security/tsd
x ./etc/security/tsd/tsd.dat
x ./etc/security/certificates
x ./etc/security/certificates/certificate_610
x ./home
x ./home/guest
x ./home/lost+found
syncroot: Processing root part installation status.
syncroot: Synchronizing installp software.
+-----------------------------------------------------------------------------+
Pre-installation Verification...
+-----------------------------------------------------------------------------+
Verifying selections...done
Verifying requisites...done
Results...

SUCCESSES
---------
Filesets listed in this section passed pre-installation verification
and will be installed.

Selected Filesets
-----------------
Java5.sdk 5.0.0.130 # Java SDK 32-bit
Java5_64.sdk 5.0.0.150 # Java SDK 64-bit
Tivoli_Management_Agent.client.rte 3.7.1.0 # Management Framework Endpoin...
X11.Dt.ToolTalk 6.1.0.0 # AIX CDE ToolTalk Support
X11.Dt.bitmaps 6.1.0.0 # AIX CDE Bitmaps
X11.Dt.helpinfo 6.1.0.0 # AIX CDE Help Files and Volumes
X11.Dt.helpmin 6.1.0.0 # AIX CDE Minimum Help Files
X11.Dt.rte 6.1.0.0 # AIX Common Desktop Environme...
X11.apps.xdm 6.1.0.1 # AIXwindows xdm Application
X11.base.rte 6.1.0.1 # AIXwindows Runtime Environment
X11.base.smt 6.1.0.1 # AIXwindows Runtime Shared Me...
X11.help.EN_US.Dt.helpinfo 6.1.0.0 # AIX CDE Help Files and Volum...
X11.loc.DE_DE.Dt.rte 6.1.0.0 # CDE Locale Configuration - G...
X11.loc.ES_ES.Dt.rte 6.1.0.0 # CDE Locale Configuration - S...
X11.loc.FR_FR.Dt.rte 6.1.0.0 # CDE Locale Configuration - F...
X11.loc.IT_IT.Dt.rte 6.1.0.0 # CDE Locale Configuration - I...
X11.loc.JA_JP.Dt.rte 6.1.0.0 # CDE Locale Configuration - J...
X11.loc.Ja_JP.Dt.rte 6.1.0.0 # CDE Locale Configuration - J...
X11.loc.KO_KR.Dt.rte 6.1.0.0 # CDE Locale Configuration - K...
X11.loc.PT_PT.Dt.rte 6.1.0.0 # CDE Locale Configuration - P...
X11.loc.RU_RU.Dt.rte 6.1.0.0 # CDE Locale Configuration - R...
X11.loc.ZH_CN.Dt.rte 6.1.0.0 # CDE Locale Configuration - S...
X11.loc.ZH_HK.Dt.rte 6.1.0.0 # CDE Locale Config - Simplifi...
X11.loc.ZH_SG.Dt.rte 6.1.0.0 # CDE Locale Config - Simplifi...
X11.loc.ZH_TW.Dt.rte 6.1.0.0 # CDE Locale Configuration - T...
X11.loc.Zh_CN.Dt.rte 6.1.0.0 # CDE Locale Configuration - S...
X11.loc.Zh_TW.Dt.rte 6.1.0.0 # CDE Locale Configuration - T...
X11.loc.de_DE.Dt.rte 6.1.0.0 # CDE Locale Configuration - G...
X11.loc.en_US.Dt.rte 6.1.0.0 # CDE Locale Configuration - U...
X11.loc.fr_FR.Dt.rte 6.1.0.0 # CDE Locale Configuration - F...
X11.loc.it_IT.Dt.rte 6.1.0.0 # CDE Locale Configuration - I...
X11.loc.ja_JP.Dt.rte 6.1.0.0 # CDE Locale Configuration - J...
X11.loc.ko_KR.Dt.rte 6.1.0.0 # CDE Locale Configuration - K...
X11.loc.zh_CN.Dt.rte 6.1.0.0 # CDE Locale Configuration - S...
X11.loc.zh_TW.Dt.rte 6.1.0.0 # CDE Locale Configuration - T...
X11.samples.apps.clients 6.1.0.0 # AIXwindows Sample X Consorti...
bos.64bit 6.1.0.1 # Base Operating System 64 bit...
bos.acct 6.1.0.1 # Accounting Services
bos.adt.base 6.1.0.0 # Base Application Development...
bos.adt.insttools 6.1.0.0 # Tool to Create installp Pack...
bos.aixpert.cmds 6.1.0.1 # AIX Security Hardening
bos.cdmount 6.1.0.0 # CD/DVD Automount Facility
bos.compat.links 6.1.0.0 # AIX 3.2 to 4 Compatibility L...
bos.compat.net 6.1.0.0 # AIX 3.2 TCP/IP Compatability...
bos.compat.termcap 6.1.0.0 # AIX 3.2 Termcap Source and L...
bos.diag.com 6.1.0.0 # Common Hardware Diagnostics
bos.diag.rte 6.1.0.0 # Hardware Diagnostics
bos.diag.util 6.1.0.0 # Hardware Diagnostics Utilities
bos.ecc_client.rte 6.1.0.0 # Electronic Customer Care Run...
bos.mh 6.1.0.0 # Mail Handler
bos.mp64 6.1.0.1 # Base Operating System 64-bit...
bos.net.ipsec.keymgt 6.1.0.0 # IP Security Key Management
bos.net.ipsec.rte 6.1.0.0 # IP Security
bos.net.ncs 6.1.0.0 # Network Computing System 1.5.1
bos.net.nfs.client 6.1.0.1 # Network File System Client
bos.net.nis.client 6.1.0.0 # Network Information Service ...
bos.net.snapp 6.1.0.0 # System Networking Analysis a...
bos.net.tcp.client 6.1.0.1 # TCP/IP Client Support
bos.net.tcp.server 6.1.0.0 # TCP/IP Server
bos.net.tcp.smit 6.1.0.0 # TCP/IP SMIT Support
bos.net.uucp 6.1.0.0 # Unix to Unix Copy Program
bos.perf.diag_tool 6.1.0.0 # Performance Diagnostic Tool
bos.perf.libperfstat 6.1.0.0 # Performance Statistics Libra...
bos.perf.perfstat 6.1.0.0 # Performance Statistics Inter...
bos.perf.tools 6.1.0.1 # Base Performance Tools
bos.perf.tune 6.1.0.0 # Performance Tuning Support
bos.pmapi.pmsvcs 6.1.0.0 # Performance Monitor API Kern...
bos.pmapi.tools 6.1.0.0 # Performance Monitor API Tools
bos.rte.archive 6.1.0.1 # Archive Commands
bos.rte.boot 6.1.0.1 # Boot Commands
bos.rte.control 6.1.0.1 # System Control Commands
bos.rte.security 6.1.0.1 # Base Security Function
bos.rte.serv_aid 6.1.0.1 # Error Log Service Aids
bos.suma 6.1.0.0 # Service Update Management As...
bos.sysmgt.loginlic 6.1.0.0 # License Management
bos.sysmgt.nim.client 6.1.0.0 # Network Install Manager - Cl...
bos.sysmgt.quota 6.1.0.0 # Filesystem Quota Commands
bos.sysmgt.serv_aid 6.1.0.1 # Software Error Logging and D...
bos.sysmgt.smit 6.1.0.0 # System Management Interface ...
bos.sysmgt.sysbr 6.1.0.1 # System Backup and BOS Instal...
bos.sysmgt.trace 6.1.0.1 # Software Trace Service Aids
bos.wpars 6.1.0.1 # AIX Workload Partitions
csm.client 1.7.0.0 # Cluster Systems Management C...
csm.core 1.7.0.0 # Cluster Systems Management Core
csm.deploy 1.7.0.0 # Cluster Systems Management D...
csm.diagnostics 1.7.0.0 # Cluster Systems Management P...
csm.dsh 1.7.0.0 # Cluster Systems Management Dsh
devices.artic960.diag 6.1.0.0 # IBM ARTIC960 Adapter Diagnos...
devices.artic960.rte 6.1.0.0 # IBM ARTIC960 Runtime Support
devices.artic960.ucode 6.1.0.0 # IBM ARTIC960 Adapter Software
devices.chrp.IBM.lhca.rte 6.1.0.1 # Infiniband Logical HCA Runti...
devices.chrp.IBM.lhea.rte 6.1.0.0 # Host Ethernet Adapter (HEA) ...
devices.chrp.base.ServiceRM 1.4.0.0 # RSCT Service Resource Manager
devices.chrp.base.diag 6.1.0.1 # RISC CHRP Base System Device...
devices.chrp.base.rte 6.1.0.1 # RISC PC Base System Device S...
devices.chrp.pci.rte 6.1.0.0 # PCI Bus Software (CHRP)
devices.chrp.vdevice.rte 6.1.0.0 # Virtual I/O Bus Support
devices.common.IBM.atm.rte 6.1.0.0 # Common ATM Software
devices.common.IBM.crypt.rte 6.1.0.0 # Cryptographic Common Runtime...
devices.common.IBM.cx.rte 6.1.0.0 # CX Common Adapter Software
devices.common.IBM.ethernet.rte 6.1.0.0 # Common Ethernet Software
devices.common.IBM.fc.hba-api 6.1.0.0 # Common HBA API Library
devices.common.IBM.fc.rte 6.1.0.0 # Common IBM FC Software
devices.common.IBM.hdlc.sdlc 6.1.0.0 # SDLC COMIO Device Driver Emu...
devices.common.IBM.ib.rte 6.1.0.1 # Infiniband Common Runtime En...
devices.common.IBM.ide.rte 6.1.0.0 # Common IDE I/O Controller So...
devices.common.IBM.iscsi.rte 6.1.0.0 # Common iSCSI Files
devices.common.IBM.ktm_std.rte 6.1.0.0 # Common Keyboard, Tablet, and...
devices.common.IBM.mpio.rte 6.1.0.1 # MPIO Disk Path Control Module
devices.common.IBM.scsi.rte 6.1.0.0 # Common SCSI I/O Controller S...
devices.common.IBM.sissas.rte 6.1.0.0 # Common IBM SAS RAID Software
devices.common.IBM.usb.rte 6.1.0.0 # USB System Software
devices.fcp.disk.array.rte 6.1.0.0 # FC SCSI RAIDiant Array Devic...
devices.fcp.disk.rte 6.1.0.1 # FC SCSI CD-ROM, Disk, Read/W...
devices.fcp.tape.rte 6.1.0.0 # FC SCSI Tape Device Software
devices.graphics.com 6.1.0.0 # Graphics Adapter Common Soft...
devices.ide.cdrom.rte 6.1.0.0 # IDE CDROM Device Software
devices.ide.disk.rte 6.1.0.0 # IDE Disk Device Software
devices.isa_sio.chrp.ecp.rte 6.1.0.0 # CHRP IEEE1284 Parallel Port ...
devices.isa_sio.pnpPNP.501.rte 6.1.0.0 # CHRP Serial Adapter Software...
devices.iscsi_sw.rte 6.1.0.0 # iSCSI Software Device Driver
devices.pci.00105000.com 6.1.0.0 # Common SAS Expansion Card De...
devices.pci.02105e51.rte 6.1.0.1 # Native Display Adapter Softw...
devices.pci.13100560.rte 6.1.0.0 # PCI Audio Adapter (13100560)...
devices.pci.14100401.rte 6.1.0.0 # Gigabit Ethernet-SX PCI Adap...
devices.pci.14101403.rte 6.1.0.0 # Gigabit Ethernet-SX Adapter ...
devices.pci.14101b02.rte 6.1.0.0 # GXT6500P Graphics Adapter So...
devices.pci.14101c02.rte 6.1.0.0 # GXT4500P Graphics Adapter So...
devices.pci.14102e00.diag 6.1.0.0 # IBM PCI SCSI RAID Adapter Di...
devices.pci.14102e00.rte 6.1.0.0 # IBM PCI SCSI RAID Adapter De...
devices.pci.14103302.rte 6.1.0.0 # GXT135P Graphics Adapter Sof...
devices.pci.14103e00.rte 6.1.0.0 # IBM PCI Token-Ring Adapter S...
devices.pci.14104e00.rte 6.1.0.0 # PCI ATM Adapter (14104e00) S...
devices.pci.14104f00.rte 6.1.0.0 # PCI ATM Adapter (14104f00) S...
devices.pci.14105000.rte 6.1.0.0 # PCI ATM Adapter (14105000) S...
devices.pci.14105e01.rte 6.1.0.0 # 622Mbps ATM PCI Adapter Soft...
devices.pci.14106602.diag 6.1.0.0 # PCI-X Dual Channel SCSI Adap...
devices.pci.14106602.rte 6.1.0.0 # PCI-X Dual Channel SCSI Adap...
devices.pci.14106802.rte 6.1.0.0 # Gigabit Ethernet-SX PCI-X Ad...
devices.pci.14106902.rte 6.1.0.1 # 10/100/1000 Base-TX PCI-X Ad...
devices.pci.14106e01.rte 6.1.0.0 # GXT4000P Graphics Adapter So...
devices.pci.14107001.rte 6.1.0.0 # GXT6000P Graphics Adapter So...
devices.pci.14107802.diag 6.1.0.0 # PCI-X Dual Channel Ultra320 ...
devices.pci.14107802.rte 6.1.0.0 # PCI-X Dual Channel Ultra320 ...
devices.pci.14107c00.rte 6.1.0.0 # PCI ATM Adapter (14107c00) S...
devices.pci.14108802.rte 6.1.0.0 # 2-Port Gigabit Ethernet-SX P...
devices.pci.14108902.rte 6.1.0.0 # 2-Port 10/100/1000 Base-TX P...
devices.pci.14108c00.rte 6.1.0.0 # ARTIC960Hx 4-Port Selectable...
devices.pci.14109f00.rte 6.1.0.0 # IBM 4758 PCI Cryptographic C...
devices.pci.1410bb02.rte 6.1.0.0 # 10 Gigabit-LR Ethernet PCI-X...
devices.pci.1410d002.com 6.1.0.0 # Common PCI iSCSI TOE Adapter...
devices.pci.1410d002.rte 6.1.0.0 # 1000 Base-TX PCI-X iSCSI TOE...
devices.pci.1410e501.rte 6.1.0.0 # IBM PCI-X Cryptographic Copr...
devices.pci.1410e601.rte 6.1.0.0 # IBM Crypto Accelerator Adapt...
devices.pci.1410ec02.rte 6.1.0.0 # 10 Gigabit Ethernet-LR PCI-X...
devices.pci.1410ff01.rte 6.1.0.0 # 10/100 Mbps Ethernet PCI Ada...
devices.pci.22106474.rte 6.1.0.0 # USB Host Controller (2210647...
devices.pci.23100020.rte 6.1.0.0 # IBM PCI 10/100 Ethernet Adap...
devices.pci.2b102725.rte 6.1.0.0 # GXT145 Graphics Adapter Soft...
devices.pci.33103500.rte 6.1.0.0 # USB Host Controller (3310350...
devices.pci.331121b9.com 6.1.0.0 # IBM PCI 2-Port Multiprotocol...
devices.pci.331121b9.rte 6.1.0.0 # IBM PCI 2-Port Multiprotocol...
devices.pci.4f111100.rte 6.1.0.0 # PCI 8-Port Asynchronous Adap...
devices.pci.4f111b00.rte 6.1.0.0 # PCI 128-Port Asynchronous Ad...
devices.pci.4f11c800.rte 6.1.0.0 # 2-Port Asynchronous EIA-232 ...
devices.pci.77101223.com 6.1.0.0 # PCI FC Adapter (77101223) Co...
devices.pci.77102224.com 6.1.0.1 # PCI-X FC Adapter (77102224) ...
devices.pci.99172704.rte 6.1.0.0 # USB Host Controller (9917270...
devices.pci.ad100501.rte 6.1.0.0 # IDE Adapter Driver for Winbo...
devices.pci.b315445a.rte 6.1.0.0 # PCI 1x/4x Infiniband Device ...
devices.pci.c1110358.rte 6.1.0.0 # USB Host Controller (c111035...
devices.pci.df1000f7.com 6.1.0.1 # Common PCI FC Adapter Device...
devices.pci.df1000f7.diag 6.1.0.0 # PCI FC Adapter Device Diagno...
devices.pci.df1000f7.rte 6.1.0.0 # PCI FC Adapter Device Software
devices.pci.e414a816.rte 6.1.0.0 # Gigabit Ethernet-SX Adapter ...
devices.pciex.b3157862.rte 6.1.0.0 # PCIe-X 4x Infiniband Device ...
devices.sas.rte 6.1.0.0 # Serial Attached SCSI Device ...
devices.scsi.disk.rte 6.1.0.0 # SCSI CD-ROM, Disk, Read/Writ...
devices.scsi.safte.rte 6.1.0.0 # SCSI Accessed Fault-Tolerant...
devices.scsi.ses.rte 6.1.0.0 # SCSI Enclosure Device Software
devices.tty.rte 6.1.0.0 # TTY Device Driver Support So...
devices.usbif.010100.rte 6.1.0.0 # USB Audio Device Driver
devices.usbif.03000008.rte 6.1.0.0 # USB 3D Mouse Client Driver
devices.usbif.030101.rte 6.1.0.0 # USB Keyboard Client Driver
devices.usbif.030102.rte 6.1.0.0 # USB Mouse Client Driver
devices.vdevice.IBM.l-lan.rte 6.1.0.0 # Virtual I/O Ethernet Software
devices.vdevice.IBM.v-scsi.rte 6.1.0.1 # Virtual SCSI Client Support
devices.vdevice.hvterm1.rte 6.1.0.0 # Virtual Terminal Devices
devices.vdevice.vty-server.rte 6.1.0.0 # Virtual Terminal Devices
ibmdebugger 6.0.0.0 # IBM Debugger for AIX
ifor_ls.base.cli 6.1.0.0 # License Use Management Runti...
invscout.com 2.2.0.1 # Inventory Scout Microcode Ca...
invscout.ldb 2.2.0.2 # Inventory Scout Logic Database
invscout.rte 2.2.0.12 # Inventory Scout Runtime
lum.base.cli 5.1.2.0 # License Use Management Runti...
lwi.runtime 6.1.0.0 # Lightweight Infrastructure R...
openssh.base.client 4.3.0.5301 # Open Secure Shell Commands
openssh.base.server 4.3.0.5301 # Open Secure Shell Server
perfagent.tools 6.1.0.0 # Local Performance Analysis &...
printers.rte 6.1.0.0 # Printer Backend
rpm.rte 3.0.5.41 # RPM Package Manager
rsct.core.auditrm 2.5.0.0 # RSCT Audit Log Resource Manager
rsct.core.errm 2.5.0.0 # RSCT Event Response Resource...
rsct.core.fsrm 2.5.0.0 # RSCT File System Resource Ma...
rsct.core.hostrm 2.5.0.0 # RSCT Host Resource Manager
rsct.core.lprm 2.5.0.0 # RSCT Least Privilege Resourc...
rsct.core.rmc 2.5.0.0 # RSCT Resource Monitoring and...
rsct.core.sec 2.5.0.0 # RSCT Security
rsct.core.sensorrm 2.5.0.0 # RSCT Sensor Resource Manager
rsct.core.sr 2.5.0.0 # RSCT Registry
rsct.core.utils 2.5.0.0 # RSCT Utilities
sysmgt.websm.apps 6.1.0.1 # Web-based System Manager App...
sysmgt.websm.framework 6.1.0.0 # Web-based System Manager Cli...
sysmgt.websm.rte 6.1.0.0 # Web-based System Manager Run...
vac.C 9.0.0.0 # IBM XL C Compiler
vac.C 9.0.0.2 # IBM XL C Compiler
vacpp.cmp.core 9.0.0.0 # IBM XL C/C++ Compiler

<< End of Success Section >>

+-----------------------------------------------------------------------------+
BUILDDATE Verification ...
+-----------------------------------------------------------------------------+
Verifying build dates...done
FILESET STATISTICS
------------------
217 Selected to be installed, of which:
217 Passed pre-installation verification
----
217 Total to be installed

+-----------------------------------------------------------------------------+
Installing Software...
+-----------------------------------------------------------------------------+

installp: APPLYING software for:
Java5.sdk 5.0.0.130

Filesets processed: 1 of 217 (Total time: 1 secs).

installp: APPLYING software for:
Java5_64.sdk 5.0.0.150

Filesets processed: 2 of 217 (Total time: 1 secs).

installp: APPLYING software for:
Tivoli_Management_Agent.client.rte 3.7.1.0

Filesets processed: 3 of 217 (Total time: 1 secs).

installp: APPLYING software for:
X11.Dt.bitmaps 6.1.0.0
X11.Dt.helpinfo 6.1.0.0
X11.Dt.helpmin 6.1.0.0

Filesets processed: 6 of 217 (Total time: 1 secs).

installp: APPLYING software for:
X11.base.smt 6.1.0.1

Filesets processed: 7 of 217 (Total time: 1 secs).

installp: APPLYING software for:
X11.help.EN_US.Dt.helpinfo 6.1.0.0

Filesets processed: 8 of 217 (Total time: 1 secs).

installp: APPLYING software for:
bos.acct 6.1.0.1

Filesets processed: 9 of 217 (Total time: 2 secs).

installp: APPLYING software for:
bos.adt.base 6.1.0.0
bos.adt.insttools 6.1.0.0

Filesets processed: 11 of 217 (Total time: 2 secs).

installp: APPLYING software for:
bos.compat.links 6.1.0.0
bos.compat.net 6.1.0.0
bos.compat.termcap 6.1.0.0

/usr/sbin/inetimp: 0822-037 fopen failed on file /etc/services of access mode: r+, errno = 2.
Filesets processed: 14 of 217 (Total time: 2 secs).

installp: APPLYING software for:
bos.diag.util 6.1.0.0

Filesets processed: 15 of 217 (Total time: 2 secs).

installp: APPLYING software for:
bos.mh 6.1.0.0

Filesets processed: 16 of 217 (Total time: 2 secs).

installp: APPLYING software for:
bos.net.nis.client 6.1.0.0
bos.net.snapp 6.1.0.0
bos.net.tcp.smit 6.1.0.0
bos.net.uucp 6.1.0.0

rm: 0653-609 Cannot remove bos.net.snapp.unpre_i.
The file system has read permission only.
rm: 0653-609 Cannot remove bos.net.snapp.unpre_i.
The file system has read permission only.
Filesets processed: 20 of 217 (Total time: 3 secs).

installp: APPLYING software for:
bos.perf.diag_tool 6.1.0.0
bos.perf.libperfstat 6.1.0.0
bos.perf.perfstat 6.1.0.0
bos.perf.tools 6.1.0.1

Filesets processed: 24 of 217 (Total time: 3 secs).

installp: APPLYING software for:
bos.pmapi.pmsvcs 6.1.0.0
bos.pmapi.tools 6.1.0.0

Filesets processed: 26 of 217 (Total time: 4 secs).

installp: APPLYING software for:
bos.rte.archive 6.1.0.1

Filesets processed: 27 of 217 (Total time: 4 secs).

installp: APPLYING software for:
bos.rte.boot 6.1.0.1

Filesets processed: 28 of 217 (Total time: 4 secs).
Note :- Full output had not been showed here.....

+-----------------------------------------------------------------------------+
Summaries:
+-----------------------------------------------------------------------------+

Installation Summary
--------------------
Name Level Part Event Result
-------------------------------------------------------------------------------
Java5.sdk 5.0.0.130 ROOT APPLY SUCCESS
Java5_64.sdk 5.0.0.150 ROOT APPLY SUCCESS
Tivoli_Management_Agent.cli 3.7.1.0 ROOT APPLY SUCCESS
X11.Dt.bitmaps 6.1.0.0 ROOT APPLY SUCCESS
X11.Dt.helpinfo 6.1.0.0 ROOT APPLY SUCCESS
X11.Dt.helpmin 6.1.0.0 ROOT APPLY SUCCESS
X11.base.smt 6.1.0.1 ROOT APPLY SUCCESS
X11.help.EN_US.Dt.helpinfo 6.1.0.0 ROOT APPLY SUCCESS
bos.acct 6.1.0.1 ROOT APPLY SUCCESS
bos.adt.base 6.1.0.0 ROOT APPLY SUCCESS
bos.adt.insttools 6.1.0.0 ROOT APPLY SUCCESS
bos.compat.links 6.1.0.0 ROOT APPLY SUCCESS
bos.compat.net 6.1.0.0 ROOT APPLY SUCCESS
bos.compat.termcap 6.1.0.0 ROOT APPLY SUCCESS
bos.diag.util 6.1.0.0 ROOT APPLY SUCCESS
bos.mh 6.1.0.0 ROOT APPLY SUCCESS
bos.net.nis.client 6.1.0.0 ROOT APPLY SUCCESS
bos.net.snapp 6.1.0.0 ROOT APPLY SUCCESS
bos.net.tcp.smit 6.1.0.0 ROOT APPLY SUCCESS
bos.net.uucp 6.1.0.0 ROOT APPLY SUCCESS
bos.perf.diag_tool 6.1.0.0 ROOT APPLY SUCCESS
bos.perf.libperfstat 6.1.0.0 ROOT APPLY SUCCESS
bos.perf.perfstat 6.1.0.0 ROOT APPLY SUCCESS
bos.perf.tools 6.1.0.1 ROOT APPLY SUCCESS
bos.pmapi.pmsvcs 6.1.0.0 ROOT APPLY SUCCESS
bos.pmapi.tools 6.1.0.0 ROOT APPLY SUCCESS
bos.rte.archive 6.1.0.1 ROOT APPLY SUCCESS
bos.rte.boot 6.1.0.1 ROOT APPLY SUCCESS
bos.rte.control 6.1.0.1 ROOT APPLY SUCCESS
bos.rte.security 6.1.0.1 ROOT APPLY SUCCESS
bos.rte.serv_aid 6.1.0.1 ROOT APPLY SUCCESS
bos.sysmgt.loginlic 6.1.0.0 ROOT APPLY SUCCESS
bos.sysmgt.quota 6.1.0.0 ROOT APPLY SUCCESS
bos.sysmgt.serv_aid 6.1.0.1 ROOT APPLY SUCCESS
bos.sysmgt.smit 6.1.0.0 ROOT APPLY SUCCESS
bos.sysmgt.sysbr 6.1.0.1 ROOT APPLY SUCCESS
bos.sysmgt.trace 6.1.0.1 ROOT APPLY SUCCESS
bos.wpars 6.1.0.1 ROOT APPLY SUCCESS
csm.deploy 1.7.0.0 ROOT APPLY SUCCESS
csm.diagnostics 1.7.0.0 ROOT APPLY SUCCESS
csm.dsh 1.7.0.0 ROOT APPLY SUCCESS
devices.artic960.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.artic960.ucode 6.1.0.0 ROOT APPLY SUCCESS
devices.chrp.IBM.lhca.rte 6.1.0.1 ROOT APPLY SUCCESS
devices.chrp.IBM.lhea.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.chrp.base.rte 6.1.0.1 ROOT APPLY SUCCESS
devices.chrp.pci.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.chrp.vdevice.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.common.IBM.atm.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.common.IBM.crypt.rt 6.1.0.0 ROOT APPLY SUCCESS
devices.common.IBM.ethernet 6.1.0.0 ROOT APPLY SUCCESS
devices.common.IBM.fc.hba-a 6.1.0.0 ROOT APPLY SUCCESS
devices.common.IBM.fc.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.common.IBM.hdlc.sdl 6.1.0.0 ROOT APPLY SUCCESS
devices.common.IBM.ib.rte 6.1.0.1 ROOT APPLY SUCCESS
devices.common.IBM.ide.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.common.IBM.iscsi.rt 6.1.0.0 ROOT APPLY SUCCESS
devices.common.IBM.ktm_std. 6.1.0.0 ROOT APPLY SUCCESS
devices.common.IBM.mpio.rte 6.1.0.1 ROOT APPLY SUCCESS
devices.common.IBM.scsi.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.common.IBM.sissas.r 6.1.0.0 ROOT APPLY SUCCESS
devices.common.IBM.usb.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.fcp.disk.array.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.fcp.disk.rte 6.1.0.1 ROOT APPLY SUCCESS
devices.fcp.tape.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.graphics.com 6.1.0.0 ROOT APPLY SUCCESS
devices.ide.cdrom.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.ide.disk.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.isa_sio.chrp.ecp.rt 6.1.0.0 ROOT APPLY SUCCESS
devices.isa_sio.pnpPNP.501. 6.1.0.0 ROOT APPLY SUCCESS
devices.iscsi_sw.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.pci.00105000.com 6.1.0.0 ROOT APPLY SUCCESS
devices.pci.02105e51.rte 6.1.0.1 ROOT APPLY SUCCESS
devices.pci.13100560.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.pci.14100401.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.pci.14101403.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.pci.14101b02.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.pci.14101c02.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.pci.14102e00.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.pci.14103302.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.pci.14103e00.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.pci.14104e00.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.pci.14104f00.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.pci.14105000.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.pci.14105e01.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.pci.14106802.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.pci.14106902.rte 6.1.0.1 ROOT APPLY SUCCESS
devices.pci.14106e01.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.pci.14107001.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.pci.14107802.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.pci.14107c00.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.pci.14108802.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.pci.14108902.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.pci.14108c00.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.pci.14109f00.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.pci.1410bb02.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.pci.1410d002.com 6.1.0.0 ROOT APPLY SUCCESS
devices.pci.1410d002.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.pci.1410e501.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.pci.1410e601.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.pci.1410ec02.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.pci.1410ff01.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.pci.22106474.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.pci.23100020.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.pci.2b102725.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.pci.33103500.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.pci.331121b9.com 6.1.0.0 ROOT APPLY SUCCESS
devices.pci.331121b9.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.pci.4f111100.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.pci.4f111b00.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.pci.4f11c800.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.pci.77101223.com 6.1.0.0 ROOT APPLY SUCCESS
devices.pci.77102224.com 6.1.0.1 ROOT APPLY SUCCESS
devices.pci.99172704.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.pci.ad100501.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.pci.b315445a.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.pci.c1110358.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.pci.df1000f7.com 6.1.0.1 ROOT APPLY SUCCESS
devices.pci.df1000f7.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.pci.e414a816.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.pciex.b3157862.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.sas.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.scsi.disk.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.scsi.safte.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.scsi.ses.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.tty.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.usbif.010100.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.usbif.03000008.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.usbif.030101.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.usbif.030102.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.vdevice.IBM.l-lan.r 6.1.0.0 ROOT APPLY SUCCESS
devices.vdevice.IBM.v-scsi. 6.1.0.1 ROOT APPLY SUCCESS
devices.vdevice.hvterm1.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.vdevice.vty-server. 6.1.0.0 ROOT APPLY SUCCESS
ibmdebugger 6.0.0.0 ROOT APPLY FAILED
ibmdebugger 6.0.0.0 ROOT CLEANUP SUCCESS
invscout.com 2.2.0.1 ROOT APPLY SUCCESS
invscout.ldb 2.2.0.2 ROOT APPLY SUCCESS
invscout.rte 2.2.0.12 ROOT APPLY SUCCESS
lwi.runtime 6.1.0.0 ROOT APPLY SUCCESS
openssh.base.client 4.3.0.5301 ROOT APPLY SUCCESS
openssh.base.server 4.3.0.5301 ROOT APPLY SUCCESS
printers.rte 6.1.0.0 ROOT APPLY SUCCESS
sysmgt.websm.apps 6.1.0.1 ROOT APPLY SUCCESS
sysmgt.websm.framework 6.1.0.0 ROOT APPLY SUCCESS
X11.base.rte 6.1.0.1 ROOT APPLY SUCCESS
bos.64bit 6.1.0.1 ROOT APPLY SUCCESS
bos.aixpert.cmds 6.1.0.1 ROOT APPLY SUCCESS
bos.cdmount 6.1.0.0 ROOT APPLY SUCCESS
bos.diag.com 6.1.0.0 ROOT APPLY SUCCESS
bos.diag.rte 6.1.0.0 ROOT APPLY SUCCESS
bos.mp64 6.1.0.1 ROOT APPLY SUCCESS
bos.net.ncs 6.1.0.0 ROOT APPLY SUCCESS
bos.net.tcp.client 6.1.0.1 ROOT APPLY SUCCESS
bos.net.tcp.server 6.1.0.0 ROOT APPLY SUCCESS
bos.perf.tune 6.1.0.0 ROOT APPLY SUCCESS
devices.artic960.diag 6.1.0.0 ROOT APPLY SUCCESS
devices.chrp.base.diag 6.1.0.1 ROOT APPLY SUCCESS
devices.common.IBM.cx.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.pci.14102e00.diag 6.1.0.0 ROOT APPLY SUCCESS
devices.pci.14106602.diag 6.1.0.0 ROOT APPLY SUCCESS
devices.pci.14106602.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.pci.14107802.diag 6.1.0.0 ROOT APPLY SUCCESS
devices.pci.df1000f7.diag 6.1.0.0 ROOT APPLY SUCCESS
perfagent.tools 6.1.0.0 ROOT APPLY SUCCESS
sysmgt.websm.rte 6.1.0.0 ROOT APPLY SUCCESS
vac.C 9.0.0.0 ROOT APPLY SUCCESS
vac.C 9.0.0.2 ROOT APPLY SUCCESS
X11.Dt.ToolTalk 6.1.0.0 ROOT APPLY SUCCESS
X11.Dt.rte 6.1.0.0 ROOT APPLY SUCCESS
X11.apps.xdm 6.1.0.1 ROOT APPLY SUCCESS
X11.loc.DE_DE.Dt.rte 6.1.0.0 ROOT APPLY SUCCESS
X11.loc.ES_ES.Dt.rte 6.1.0.0 ROOT APPLY SUCCESS
X11.loc.FR_FR.Dt.rte 6.1.0.0 ROOT APPLY SUCCESS
X11.loc.IT_IT.Dt.rte 6.1.0.0 ROOT APPLY SUCCESS
X11.loc.JA_JP.Dt.rte 6.1.0.0 ROOT APPLY SUCCESS
X11.loc.Ja_JP.Dt.rte 6.1.0.0 ROOT APPLY SUCCESS
X11.loc.KO_KR.Dt.rte 6.1.0.0 ROOT APPLY SUCCESS
X11.loc.PT_PT.Dt.rte 6.1.0.0 ROOT APPLY SUCCESS
X11.loc.RU_RU.Dt.rte 6.1.0.0 ROOT APPLY SUCCESS
X11.loc.ZH_CN.Dt.rte 6.1.0.0 ROOT APPLY SUCCESS
X11.loc.ZH_HK.Dt.rte 6.1.0.0 ROOT APPLY SUCCESS
X11.loc.ZH_SG.Dt.rte 6.1.0.0 ROOT APPLY SUCCESS
X11.loc.ZH_TW.Dt.rte 6.1.0.0 ROOT APPLY SUCCESS
X11.loc.Zh_CN.Dt.rte 6.1.0.0 ROOT APPLY SUCCESS
X11.loc.Zh_TW.Dt.rte 6.1.0.0 ROOT APPLY SUCCESS
X11.loc.de_DE.Dt.rte 6.1.0.0 ROOT APPLY SUCCESS
X11.loc.en_US.Dt.rte 6.1.0.0 ROOT APPLY SUCCESS
X11.loc.fr_FR.Dt.rte 6.1.0.0 ROOT APPLY SUCCESS
X11.loc.it_IT.Dt.rte 6.1.0.0 ROOT APPLY SUCCESS
X11.loc.ja_JP.Dt.rte 6.1.0.0 ROOT APPLY SUCCESS
X11.loc.ko_KR.Dt.rte 6.1.0.0 ROOT APPLY SUCCESS
X11.loc.zh_CN.Dt.rte 6.1.0.0 ROOT APPLY SUCCESS
X11.loc.zh_TW.Dt.rte 6.1.0.0 ROOT APPLY SUCCESS
X11.samples.apps.clients 6.1.0.0 ROOT APPLY SUCCESS
bos.net.ipsec.rte 6.1.0.0 ROOT APPLY SUCCESS
bos.net.nfs.client 6.1.0.1 ROOT APPLY SUCCESS
bos.sysmgt.nim.client 6.1.0.0 ROOT APPLY SUCCESS
bos.net.ipsec.keymgt 6.1.0.0 ROOT APPLY SUCCESS
ifor_ls.base.cli 6.1.0.0 ROOT APPLY SUCCESS
lum.base.cli 5.1.2.0 ROOT APPLY SUCCESS
rpm.rte 3.0.5.41 ROOT APPLY SUCCESS
rsct.core.utils 2.5.0.0 ROOT APPLY SUCCESS
bos.ecc_client.rte 6.1.0.0 ROOT APPLY SUCCESS
bos.suma 6.1.0.0 ROOT APPLY SUCCESS
csm.core 1.7.0.0 ROOT APPLY SUCCESS
rsct.core.sec 2.5.0.0 ROOT APPLY SUCCESS
rsct.core.sr 2.5.0.0 ROOT APPLY SUCCESS
vacpp.cmp.core 9.0.0.0 ROOT APPLY SUCCESS
csm.client 1.7.0.0 ROOT APPLY SUCCESS
rsct.core.rmc 2.5.0.0 ROOT APPLY SUCCESS
rsct.core.sensorrm 2.5.0.0 ROOT APPLY SUCCESS
devices.chrp.base.ServiceRM 1.4.0.0 ROOT APPLY SUCCESS
rsct.core.auditrm 2.5.0.0 ROOT APPLY SUCCESS
rsct.core.errm 2.5.0.0 ROOT APPLY SUCCESS
rsct.core.fsrm 2.5.0.0 ROOT APPLY SUCCESS
rsct.core.hostrm 2.5.0.0 ROOT APPLY SUCCESS
rsct.core.lprm 2.5.0.0 ROOT APPLY SUCCESS
bos.rte.archive 6.1.0.1 ROOT COMMIT SUCCESS
bos.rte.boot 6.1.0.1 ROOT COMMIT SUCCESS
bos.rte.control 6.1.0.1 ROOT COMMIT SUCCESS
bos.rte.security 6.1.0.1 ROOT COMMIT SUCCESS
bos.rte.serv_aid 6.1.0.1 ROOT COMMIT SUCCESS
vac.C 9.0.0.2 ROOT COMMIT SUCCESS
syncroot: Error synchronizing installp software.
syncroot: Returns Status = FAILURE
Workload partition MyTestWpar4 created successfully.
mkwpar: 0960-390 To start the workload partition, execute the following as root: startwpar [-v] MyTestWpar4
lpar47p682e_pub[/] >



to start WPAR


lpar47p682e_pub[/] > startwpar -v MyTestWpar3
Starting workload partition MyTestWpar3.
Mounting all workload partition file systems.
Mounting /wpars/MyTestWpar3
Mounting /wpars/MyTestWpar3/home
Mounting /wpars/MyTestWpar3/opt
Mounting /wpars/MyTestWpar3/proc
Mounting /wpars/MyTestWpar3/tmp
Mounting /wpars/MyTestWpar3/usr
Mounting /wpars/MyTestWpar3/var
Loading workload partition.
$corral_t = {
'name' => 'MyTestWpar3',
'wlm_cpu' => [
undef,
undef,
undef,
undef
],
'path' => '/wpars/MyTestWpar3',
'hostname' => 'MyTestWpar3',
'wlm_procVirtMem' => [
-1,
undef
],
'wlm_mem' => [
undef,
undef,
undef,
undef
],
'key' => 5,
'vips' => [
[
'en0',
'172.29.138.24',
'255.255.192.0',
'172.29.191.255'
]
],
'wlm_rset' => undef,
'opts' => 4,
'id' => 0
};
Exporting workload partition devices.
Starting workload partition subsystem cor_MyTestWpar3.
0513-059 The cor_MyTestWpar3 Subsystem has been started. Subsystem PID is 536778.
Verifying workload partition startup.
Return Status = SUCCESS.
lpar47p682e_pub[/] >
-------------------------------------------------------
lpar47p682e_pub[/] > syncroot -i
syncroot: Processing root part installation status.
syncroot: Installp root packages are currently synchronized.
syncroot: Root part is currently synchronized.
syncroot: Returns Status = SUCCESS
------------------------------------------------------------

To synchronising all File set from global to WPAR syncroot command needs to executed.

Console login to WPAR

par47p682e_pub[/] > lswpar
Name State Type Hostname Directory
----------------------------------------------------------
MyTestWpar1 A S MyTestWpar1 /wpars/MyTestWpar1
MyTestWpar2 A S MyTestWpar2 /wpars/MyTestWpar2
TestWpar3 A S TestWpar3 /wpars/TestWpar4

lpar47p682e_pub[/] > clogin MyTestWpar4
*******************************************************************************
* *
* *
* Welcome to AIX Version 6.1! *
* *
* *
* Please see the README file in /usr/lpp/bos for information pertinent to *
* this release of the AIX Operating System. *
* *
* *
*******************************************************************************

#

You can also connect to WPAR via ssh. It will have its own user id for authentication.

lsvg, lspv commands wont work as all filesystem alocated to WPAR has been created in AIX 6. global environment.

# df -k
Filesystem 1024-blocks Free %Used Iused %Iused Mounted on
/dev/fslv12 131072 104404 21% 2109 9% /
/dev/fslv13 131072 128640 2% 7 1% /home
/opt 262144 119808 55% 3048 11% /opt
/proc - - - - - /proc
/dev/fslv14 131072 128424 3% 9 1% /tmp
/usr 3538944 158320 96% 91414 69% /usr
/dev/fslv15 131072 116816 11% 372 2% /var



To do changes in above mentioned file system . We need to do in global environment. Not frow WPAR. All system adminstartion task of increasing , decreasing, adding, deleting File system are to be done from AIX global environment.


===============================================

Starting & Stopping WPAR command output

NOTE :- All IP shown in the command has been altered as displaying IP on net is invitation to problem.

To reboot test wpar 2 command is

/usr/bin/stopwpar -r MyTestWpar2 Flag r stands for reboot.


output

Stopping workload partition MyTestWpar2
stopwpar: 0960-261 Waiting up to 600 seconds for workload partition to halt.
Stopping workload partition MyTestWpar2.
Stopping workload partition subsystem cor_MyTestWpar2.
0513-044 The cor_MyTestWpar2 Subsystem was requested to stop.
stopwpar: 0960-261 Waiting up to 600 seconds for workload partition to halt.
Shutting down all workload partition processes.
Unmounting all workload partition file systems.
Starting workload partition MyTestWpar2.
Mounting all workload partition file systems.
Loading workload partition.
Exporting workload partition devices.
Starting workload partition subsystem cor_MyTestWpar2.
0513-059 The cor_MyTestWpar2 Subsystem has been started. Subsystem PID is 696392.
Verifying workload partition startup.


=============================================

To stop WPAR MyTestWpar2


/usr/sbin/stopwpar MyTestWpar2


output

Stopping workload partition MyTestWpar2.
stopwpar: 0960-261 Waiting up to 600 seconds for workload partition to halt.
Stopping workload partition MyTestWpar2.
Stopping workload partition subsystem cor_MyTestWpar2.
0513-044 The cor_MyTestWpar2 Subsystem was requested to stop.
stopwpar: 0960-261 Waiting up to 600 seconds for workload partition to halt.
Shutting down all workload partition processes.
Unmounting all workload partition file systems.



All file systems related to testwpar 2 will be unmounted.

lpar47p682e_pub[/] > df -g
Filesystem GB blocks Free %Used Iused %Iused Mounted on
/dev/hd4 0.12 0.02 87% 8105 63% /
/dev/hd2 3.38 0.15 96% 91414 69% /usr
/dev/hd9var 0.25 0.24 6% 477 1% /var
/dev/hd3 0.25 0.25 1% 53 1% /tmp
/dev/hd1 0.12 0.12 1% 8 1% /home
/dev/hd11admin 0.12 0.12 1% 5 1% /admin
/proc - - - - - /proc
/dev/hd10opt 0.25 0.11 55% 3048 11% /opt
p650:/stage/middleware 73.94 13.38 82% 37383 2% /stage/middleware
192.168.1.12:/userdata/20005533 10.00 9.92 1% 19 1% /home/u0005533
/dev/fslv00 0.12 0.10 21% 2106 9% /wpars/MyTestWpar1
/dev/fslv01 0.12 0.12 2% 5 1% /wpars/MyTestWpar1/home
/dev/fslv02 0.25 0.11 56% 3048 11% /wpars/MyTestWpar1/opt
/proc - - - - - /wpars/MyTestWpar1/proc
/dev/fslv03 0.12 0.12 3% 13 1% /wpars/MyTestWpar1/tmp
/dev/fslv04 3.38 0.14 96% 91483 71% /wpars/MyTestWpar1/usr
/dev/fslv05 0.12 0.11 10% 371 2% /wpars/MyTestWpar1/var
lpar47p682e_pub[/] >


We will not able to ping that TestWpar 172.29.138.23


lpar47p682e_pub[/] > ping 172.29.138.23
PING 172.29.138.23: (172.29.138.23): 56 data bytes


Alias IP 172.29.138.23 will be removed from en0 network adapter....

lpar47p682e_pub[/] > ifconfig -a
en1: flags=1e080863,480
inet 10.153.3.101 netmask 0xffff0000 broadcast 10.153.255.255
tcp_sendspace 262144 tcp_recvspace 262144 rfc1323 1
en0: flags=1e080863,480
inet 172.29.138.149 netmask 0xffffc000 broadcast 172.29.191.255
inet 172.29.138.203 netmask 0xffffc000 broadcast 172.29.191.255
tcp_sendspace 262144 tcp_recvspace 262144 rfc1323 1
lo0: flags=e08084b
inet 127.0.0.1 netmask 0xff000000 broadcast 127.255.255.255
inet6 ::1/0
tcp_sendspace 131072 tcp_recvspace 131072 rfc1323 1
lpar47p682e_pub[/] >

lpar47p682e_pub[/] > lswpar
Name State Type Hostname Directory
----------------------------------------------------------
MyTestWpar1 A S MyTestWpar1 /wpars/MyTestWpar1
MyTestWpar2 D S MyTestWpar2 /wpars/MyTestWpar2 ---- >

D state stands for partition is not activated.
=======================================================================

To start WPAR
To start WPAR TestWpar2

lpar47p682e_pub[/] > startwpar MyTestWpar2
Starting workload partition MyTestWpar2.
Mounting all workload partition file systems.
Loading workload partition.
Exporting workload partition devices.
Starting workload partition subsystem cor_MyTestWpar2.
0513-059 The cor_MyTestWpar2 Subsystem has been started. Subsystem PID is 291026.
Verifying workload partition startup.


Filesystem for testwpar2 is now in mounted state.

lpar47p682e_pub[/] > df -g
Filesystem GB blocks Free %Used Iused %Iused Mounted on
/dev/hd4 0.12 0.02 87% 8105 63% /
/dev/hd2 3.38 0.15 96% 91414 69% /usr
/dev/hd9var 0.25 0.24 6% 477 1% /var
/dev/hd3 0.25 0.25 1% 53 1% /tmp
/dev/hd1 0.12 0.12 1% 8 1% /home
/dev/hd11admin 0.12 0.12 1% 5 1% /admin
/proc - - - - - /proc
/dev/hd10opt 0.25 0.11 55% 3048 11% /opt
p650:/stage/middleware 73.94 13.38 82% 37383 2% /stage/middleware
192.168.1.12:/userdata/20005533 10.00 9.92 1% 19 1% /home/u0005533
/dev/fslv00 0.12 0.10 21% 2106 9% /wpars/MyTestWpar1
/dev/fslv01 0.12 0.12 2% 5 1% /wpars/MyTestWpar1/home
/dev/fslv02 0.25 0.11 56% 3048 11% /wpars/MyTestWpar1/opt
/proc - - - - - /wpars/MyTestWpar1/proc
/dev/fslv03 0.12 0.12 3% 13 1% /wpars/MyTestWpar1/tmp
/dev/fslv04 3.38 0.14 96% 91483 71% /wpars/MyTestWpar1/usr
/dev/fslv05 0.12 0.11 10% 371 2% /wpars/MyTestWpar1/var
/dev/fslv06 0.12 0.10 21% 2107 9% /wpars/MyTestWpar2
/dev/fslv07 0.12 0.12 2% 5 1% /wpars/MyTestWpar2/home
/dev/fslv08 0.25 0.11 56% 3048 11% /wpars/MyTestWpar2/opt
/proc - - - - - /wpars/MyTestWpar2/proc
/dev/fslv09 0.12 0.12 3% 10 1% /wpars/MyTestWpar2/tmp
/dev/fslv10 3.38 0.14 96% 91483 71% /wpars/MyTestWpar2/usr
/dev/fslv11 0.12 0.11 11% 373 2% /wpars/MyTestWpar2/var
lpar47p682e_pub[/] >
=============================================================================


To maintain software for sytem WPAR with Global AIX

syncwpar [ [-a] [-i] | [-F] [-r] ] [-p] [-v] [-X]
{ -A | -f wparNamesFile | wparName }

Flags:
-a = Perform additional installation only.
-i = Only update installp filesets.
-F = Force copy RPM files.
-r = Only update RPM files.
-p = Preview operation. Do not actually perform the synchronization.
-v = Verbose mode.
-X = Expand file system space if possible.
-A = Apply operation to all corrals.
-f = Specifies a file containing a list of workload partitions.



Note : - If system WPAR has /usr private file system for WPAR. Synchronisation will Fail ...
=================================================================

Listing WPAR Command outputs

Server consist of three Test WPAR

To list All WPAR lswpar comamnd is used.

lpar47p682e_pub[/] > lswpar --help
Usage:
Tabular: lswpar [-D | -M | -N] [-a fieldname[,...]]
[-q] [-s state] [-t type] [wparname ...]

Paragraph: lswpar {-G | -L | -R | -S | -T}
[-s state] [-t type] [wparname ...]

Delimited: lswpar {-c | -d delim} [-a fieldname[,...] |
-G | {-D|-M|-N} [-a fieldName[,...]] | -R | -S | -T]
[-q] [-s state] [-t type] [wparname ...]

Flags:
-a = Comma-separated list of field names to print.
-c = Colon delimited output (equivalent to -d:).
-d = Output delimited by specified delimiter.
-D = Print device exports.
-G = Print general information (paragraph format).
-L = Long format.
-M = File systems or file system dependencies.
-N = Print network information.
-q = Suppress output header.
-R = Print resource information (paragraph format).
-S = Print security information (paragraph format).
-s = Only print information about workload partitions in a
given state. Valid states are D (Defined), L (Loaded),
A (Active), F (Frozen), P (Paused), T (Transitional)
and B (Broken).
-T = Print operation information.
-t = Only print information about workload partitions of a given type. Valid
types are S (System), A (Application) and C (Checkpointable).


To have detail inormation of WPAR Use -L flag.

=======================================================================

lpar47p682e_pub[/] > lswpar
Name State Type Hostname Directory
----------------------------------------------------------
MyTestWpar1 A S MyTestWpar1 /wpars/MyTestWpar1
MyTestWpar2 A S MyTestWpar2 /wpars/MyTestWpar2
TestWpar3 A S TestWpar3 /wpars/TestWpar3
lpar47p682e_pub[/] > lswpar TestWpar3


Name State Type Hostname Directory
----------------------------------------------------
TestWpar3 A S TestWpar3 /wpars/TestWpar3


========================================================================

THere are diffrent state of WPAR -- ref Man page

The lswpar command prints information about one or more specified workload partition (or all workload partitions if none are specified) to standard
output.

You can filter all listings according to the following workload partition states using the -s flag:
Defined
The workload partition has been defined by the mkwpar command and is ready for use, but is not active. Start workload partitions in this state
with the startwpar command.
Loaded
The workload partition has been configured in the kernel, but processes have not yet been started. Note: This state is visible only to
programmatic consumers that use the lswpar command to start a workload partition.
Active
The workload partition is running normally.
Frozen
A checkpoint operation is initiated, and the processes of the workload partition are quiesced, awaiting the storing phase. Note: The Frozen
state is only visible when you use the lswpar command to checkpoint a workload partition. The checkpoint or restart function requires additional
software package other than base WPAR.
Paused
A checkpoint or restart operation has been performed, and the workload partition's processes are ready to be resumed or killed. The checkpoint
or restart functionality requires additional software.
Transitional
An administrative operation is in progress. The workload partition is in the process of being created, started, stopped, configured, and so on.
Broken
An administrative operation failed, leaving this workload partition in an unusable state.

You can filter all listings according to the following workload partition types using the -t flag:
Application
This is an application workload partition, running a single process (or a group of processes invoked by that means) without isolated system
services. The process or group of processes inherits its operating environment (file systems, security, devices. and so on) from the environment
where the application workload partition was created.
System
This is a system workload partition, emulating an independent, fully-functional instance of the operating system.

If additional checkpoint or restart software is installed, you can also specify the following type:
Checkpointable

This workload partition is enabled for checkpoint or restart functions. Tip: This is not a mutually exclusive workload partition type.
Checkpointable workload partitions are still either System or Application workload partitions.

=======================================================================
To list detail of MyTestWpar1

====================================================================

lpar47p682e_pub[/] > lswpar -L MyTestWpar1
=================================================================
MyTestWpar1 - Active
=================================================================
GENERAL
Type: S
Owner: root
Hostname: MyTestWpar1
Directory: /wpars/MyTestWpar1
Start/Stop Script:
Auto: yes
Private /usr: yes
Checkpointable: no
Application:

NETWORK
Interface Address Mask/Prefix Broadcast
-----------------------------------------------------------------
en0 172.29.138.203 255.255.192.0 172.29.191.255

FILE SYSTEMS
MountPoint Device Vfs Nodename Options
-----------------------------------------------------------------
/wpars/MyTestWpar1 /dev/fslv00 jfs2
/wpars/MyTestWpar1/home /dev/fslv01 jfs2
/wpars/MyTestWpar1/opt /dev/fslv02 jfs2 rw
/wpars/MyTestWpar1/proc /proc namefs rw
/wpars/MyTestWpar1/tmp /dev/fslv03 jfs2
/wpars/MyTestWpar1/usr /dev/fslv04 jfs2 rw
/wpars/MyTestWpar1/var /dev/fslv05 jfs2

RESOURCE CONTROLS
Active: yes
Resource Set:
CPU Shares: 20
CPU Limits: 0%-100%,100%
Memory Shares: 20
Memory Limits: 0%-100%,100%
Per-Process Virtual Memory Limit: unlimited
Total Processes: unlimited
Total Threads: unlimited

OPERATION
Operation: none
Process ID:
Start Time:

SECURITY SETTINGS
Privileges: PV_AU_,PV_AU_ADD,PV_AU_ADMIN,PV_AU_PROC,PV_AU_READ,
PV_AU_WRITE,PV_AZ_ADMIN,PV_AZ_CHECK,PV_AZ_READ,PV_AZ_ROOT,
PV_DAC_,PV_DAC_GID,PV_DAC_O,PV_DAC_R,PV_DAC_RID,PV_DAC_UID,
PV_DAC_W,PV_DAC_X,PV_DEV_CONFIG,PV_DEV_QUERY,PV_FS_CHOWN,
PV_FS_CHROOT,PV_FS_CNTL,PV_FS_LINKDIR,PV_FS_MKNOD,
PV_FS_MOUNT,PV_FS_QUOTA,PV_KER_ACCT,PV_KER_CONF,PV_KER_DR,
PV_KER_EWLM,PV_KER_EXTCONF,PV_KER_IPC,PV_KER_IPC_O,
PV_KER_IPC_R,PV_KER_IPC_W,PV_KER_LVM,PV_KER_NFS,PV_KER_RAC,
PV_KER_RAS_ERR,PV_KER_REBOOT,PV_NET_PORT,PV_PROC_CKPT,
PV_PROC_CORE,PV_PROC_CRED,PV_PROC_ENV,PV_PROC_PRIO,
PV_PROC_RAC,PV_PROC_RTCLK,PV_PROC_SIG,PV_PROC_TIMER,
PV_PROC_VARS,PV_PROC_PRIV,PV_SU_UID,PV_TCB,PV_TP,PV_TP_SET,
PV_MIC,PV_MIC_CL,PV_LAB_,PV_LAB_CL,PV_LAB_CLTL,PV_LAB_LEF,
PV_LAB_SLDG,PV_LAB_SLDG_STR,PV_LAB_SL_FILE,PV_LAB_SL_PROC,
PV_LAB_SL_SELF,PV_LAB_SLUG,PV_LAB_SLUG_STR,PV_LAB_TL,
PV_MAC_,PV_MAC_CL,PV_MAC_R,PV_MAC_R_CL,PV_MAC_R_STR,
PV_MAC_R_PROC,PV_MAC_W,PV_MAC_W_CL,PV_MAC_W_DN,PV_MAC_W_UP,
PV_MAC_W_PROC,PV_MAC_OVRRD,PV_KER_SECCONFIG,
PV_PROBEVUE_TRC_USER,PV_PROBEVUE_TRC_USER_SELF

DEVICE EXPORTS
Name Type
-----------------------------------------------------------------
/dev/null pseudo
/dev/tty pseudo
/dev/console pseudo
/dev/zero pseudo
/dev/clone pseudo
/dev/sad clone
/dev/xti/tcp clone
/dev/xti/tcp6 clone
/dev/xti/udp clone
/dev/xti/udp6 clone
/dev/xti/unixdg clone
/dev/xti/unixst clone
/dev/error pseudo
/dev/errorctl pseudo
/dev/audit pseudo
/dev/nvram pseudo

=========================================================================

Listing file system of diffrent WPAR in server . THere are three WPAR.

lpar47p682e_pub[/] > df -g
Filesystem GB blocks Free %Used Iused %Iused Mounted on
/dev/hd4 0.12 0.01 91% 8120 68% /
/dev/hd2 3.38 0.15 96% 91414 69% /usr
/dev/hd9var 0.25 0.24 6% 488 1% /var
/dev/hd3 0.25 0.25 1% 55 1% /tmp
/dev/hd1 0.12 0.12 1% 8 1% /home
/dev/hd11admin 0.12 0.12 1% 5 1% /admin
/proc - - - - - /proc
/dev/hd10opt 0.25 0.11 55% 3048 11% /opt
p650:/stage/middleware 73.94 13.38 82% 37383 2% /stage/middleware
192.168.1.12:/userdata/20005533 10.00 9.92 1% 19 1% /home/u0005533
------------------------------------------------------------------------------
WPAR1 Filesystem
/dev/fslv00 0.12 0.10 21% 2107 9% /wpars/MyTestWpar1
/dev/fslv01 0.12 0.12 2% 5 1% /wpars/MyTestWpar1/home
/dev/fslv02 0.25 0.11 56% 3048 11% /wpars/MyTestWpar1/opt
/proc - - - - - /wpars/MyTestWpar1/proc
/dev/fslv03 0.12 0.12 3% 13 1% /wpars/MyTestWpar1/tmp
/dev/fslv04 3.38 0.14 96% 91483 71% /wpars/MyTestWpar1/usr
/dev/fslv05 0.12 0.11 10% 371 2% /wpars/MyTestWpar1/var
/proc - - - - - /wpars/MyTestWpar1/proc
------------------------------------------------------------------------------
WPAR 2 File system
/dev/fslv06 0.12 0.10 21% 2112 9% /wpars/MyTestWpar2
/dev/fslv07 0.12 0.12 2% 5 1% /wpars/MyTestWpar2/home
/dev/fslv08 0.25 0.11 56% 3048 11% /wpars/MyTestWpar2/opt
/proc - - - - - /wpars/MyTestWpar2/proc
/dev/fslv09 0.12 0.12 3% 10 1% /wpars/MyTestWpar2/tmp
/dev/fslv10 3.38 0.14 96% 91483 71% /wpars/MyTestWpar2/usr
/dev/fslv11 0.12 0.11 11% 374 2% /wpars/MyTestWpar2/var
------------------------------------------------------------------------------
WPAR 3 FIle System
/dev/fslv12 0.12 0.10 21% 2103 9% /wpars/MyTestWpar3
/dev/fslv13 0.12 0.12 2% 5 1% /wpars/MyTestWpar3/home
/opt 0.25 0.11 55% 3048 11% /wpars/MyTestWpar3/opt
/proc - - - - - /wpars/MyTestWpar3/proc WPAR 3
/dev/fslv14 0.12 0.12 3% 9 1% /wpars/MyTestWpar3/tmp
/usr 3.38 0.15 96% 91414 69% /wpars/MyTestWpar3/usr
/dev/fslv15 0.12 0.11 11% 370 2% /wpars/MyTestWpar3/var
lpar47p682e_pub[/] >

==========================================================================

Configuration of Etherchannel in AIX

EtherChannel
EtherChannel is a network port aggregation technology that allows several Ethernet adapters to be aggregated together to form a virtual Ethernet adapter. The adapters that belong to an EtherChannel are cabled to the same EtherChannel-enabled network switch, which must be manually configured to identify the ports that belong to the EtherChannel.
The system sees the EtherChannel as any other Ethernet adapter. For this reason, IP is configured over an EtherChannel adapter as over any Ethernet adapter. Furthermore, all the adapters in the EtherChannel are automatically configured with the same hardware (MAC) address, so they are treated by remote systems as if they were one adapter.
EtherChannel's main benefit is that its interface has the aggregated network bandwidth of all its adapters. Traffic is distributed across the adapters in either the standard way (where the adapter over which the packets are sent is chosen depending on the destination address) or on a round-robin basis (where packets are sent evenly across all adapters). If an adapter fails, the packets are automatically sent on the next available adapter in the EtherChannel without disruption to existing user connections. Once the adapter failure has been corrected, the adapter can be used for network traffic once again.
In AIX, users can configure multiple EtherChannels per system, but it is required that all the links in one EtherChannel are attached to a single switch. Because the EtherChannel cannot be spread across two switches, the entire EtherChannel is lost if the switch is unplugged or fails. To solve this problem, a new backup option added in AIX 5.2 keeps the service running when the main EtherChannel fails. The backup and EtherChannel adapters should be attached to different network switches. In the event that all of the adapters in the EtherChannel fail, the IP and MAC addresses will be automatically moved to the backup adapter. When any link in the EtherChannel is restored, the service is moved back to the EtherChannel.
Network Interface Backup, a mode of operation for EtherChannel, protects against a single point of Ethernet network failure. In Network Interface Backup mode, only one adapter at a time is actively used for network traffic. The EtherChannel tests the currently-active adapter and, optionally, the network path to a user-specified node. When a failure is detected, the MAC and IP addresses are moved to the next adapter, which will be used until it fails. Network Interface Backup provides rapid detection and failover with no disruption to user connections. Network Interface Backup was originally implemented as a mode in the EtherChannel SMIT menu. In AIX 5.2, the backup adapter provides the equivalent function, so the mode was eliminated from the SMIT menu. To use network interface backup in AIX 5.2, see Configure Network Interface Backup.
Configuring EtherChannel
The following procedure will help you set up an EtherChannel.
Considerations
You can have anywhere from two to eight Ethernet adapters per EtherChannel.
You can configure multiple EtherChannels on a single system, but remember that each EtherChannel constitutes an additional Ethernet interface. The no command option, ifsize, may need to be increased to include not only the Ethernet interfaces for each adapter, but also any EtherChannels that are configured. The default ifsize is eight.
You can use any supported Ethernet adapter in EtherChannel. However, the Ethernet adapters must be connected to a switch that supports EtherChannel. See the documentation that came with your switch to determine if it supports EtherChannel.
All adapters in the EtherChannel should be configured for the same speed (10 Mbps, for example) and must be configured with the same mode (full duplex, for example).
The adapters that you plan to use for your EtherChannel must not have an IP address configured on it before you start this procedure. Use the ifconfig command to unconfigure your adapters. For example, ifconfig en5 detach would unconfigure adapter en5.
Configure an EtherChannel
With root authority, type smit etherchannel at the command line.
Select Add an EtherChannel from the list and press Enter.
Select the primary Ethernet adapters that you want on your EtherChannel and press Enter. If you are planning to use EtherChannel backup, do not select the adapter that you plan to use for the backup at this point. The EtherChannel backup option was added in AIX 5.2.
Note
The Available Network Adapters displays all Ethernet adapters. If you select an Ethernet adapter that is already being used (has an interface defined), you will get an error message. You first need to detach these interfaces if you want to use them.
Enter the information in the fields according to the following guidelines:
EtherChannel Adapters: You should see all primary adapters that you are using in your EtherChannel. You selected these adapters in the previous step.
Enable Alternate EtherChannel Address: This field is optional. Setting this to yes will enable you to specify a MAC address that you want the EtherChannel to use. If you set this option to no, the EtherChannel will use the MAC address of the first adapter.
Alternate EtherChannel Address: If you set Enable Alternate EtherChannel Address to yes, specify the MAC address that you want to use here. The address you specify must start with 0x and be a 12-digit hexadecimal address.
Enable Gigabit Ethernet Jumbo Frames: This field is optional. In order to use this, your switch must support jumbo frames. This will only work with Standard Ethernet, not IEEE 802.3. Set this to yes if you want to enable it.
Mode: You can choose from the following modes:
Standard: In this mode the EtherChannel uses the destination IP address to choose which adapter it will send the packets out on. The EtherChannel divides the last byte of the packet's destination IP address by the number of adapters in the EtherChannel and uses the remainder (using the "modulus" operator) to identify the outgoing link. For instance, if the destination IP is 10.10.10.1, and there are 2 adapters in the EtherChannel, (1 % 2) = 1, so the second adapter is used (the adapters are numbered starting from 0). The adapters are numbered in the order they are listed in the SMIT menu. For non-IP traffic (such as ARP), the last byte of the destination MAC address is used to do the calculation. This mode will guarantee packets are sent out over the EtherChannel in the order they were given to it, but it may not make full use of the bandwidth. This is the default operation mode.
Round Robin: In this mode the EtherChannel will rotate through the adapters, giving each adapter one packet before repeating. The packets may be sent out in a slightly different order than they were given to the EtherChannel, but it will make the best use of its bandwidth.
Network Interface Backup: This option is available in AIX 5.1 and AIX 4.3.3. In this mode, the channel will activate only one adapter at a time. The intention is that the adapters are plugged into different Ethernet switches, each of which is capable of getting to any other machine on the subnet or network. When a problem is detected either with the direct connection (or optionally through the inability to ping a machine), the EtherChannel will deactivate the current adapter and activate a backup adapter. This mode is the only one that makes use of the Internet Address to Ping, Number of Retries, and Retry Timeout fields.
Network Interface Backup Mode does not exist as an explicit mode in AIX 5.2. To enable Network Interface Backup Mode in AIX 5.2, you must configure one adapter in the main EtherChannel and a backup adapter. For more information, see Configure Network Interface Backup.

Backup Adapter: This field is optional. Enter the adapter that you want to use as your EtherChannel backup. EtherChannel backup is available in AIX 5.2.
Internet Address to Ping: This field is optional and is only available if you are running Network Interface Backup mode. The EtherChannel will ping the IP address that you specify here. If the EtherChannel is unable to ping this address for the Number of Retries times in Retry Timeout intervals, the EtherChannel will switch adapters.
Number of Retries: Enter the number of ping response failures that are allowed before the EtherChannel switches adapters. The default is three. This field is optional and valid only if you have set an Internet Address to Ping.
Retry Timeout: Enter the number of seconds between the times when the EtherChannel will ping the Internet Address to Ping. The default is one second. This field is optional and valid only is you have set an Internet Address to Ping.
Press Enter after changing the desired fields to create the EtherChannel.
Configure IP over the newly created EtherChannel device by typing smit chinet at the command line.
Select your new EtherChannel interface from the list.
Fill in all the required fields and press Enter.
Configure Network Interface Backup
Network Interface Backup protects against a single point of network failure by providing failure detection and failover with no disruption to user connections. When operating in this mode, only one adapter is active at any given time. If the active adapter fails, the next adapter in the EtherChannel will be used for all traffic. When operating in Network Interface Backup mode, it is not necessary to connect to an EtherChannel-enabled switch.
The Network Interface Backup setup is most effective when the adapters are connected to different network switches, as this provides greater redundancy than connecting all adapters to one switch. When connecting to different switches, make sure there is a connection between the switches. This provides failover capabilities from one adapter to another by ensuring that there is always a route to the currently-active adapter.
In releases previous to AIX 5.2, Network Interface Backup mode was implemented as an explicit mode of operation in the EtherChannel SMIT menu. In AIX 5.2, however, the backup adapter functionality provides the equivalent behavior, so the mode was eliminated from the SMIT menu.
AIX 5.2 additionally provides priority, meaning that the adapter configured in the primary EtherChannel will be used over the backup adapter. As long as the primary adapter is functional, it will be used. This contrasts from the behavior of Network Interface Backup mode, where the backup adapter was used until it also failed, regardless of whether the primary adapter had already recovered.
While operating in Interface Backup Mode, it is also possible to configure the EtherChannel to detect link failure and network unreachability. To do this, specify the IP address of a remote host where connectivity should always be present. The EtherChannel will periodically ping this host to determine whether there is still a network path to it. If a specified number of ping attempts go unanswered, the EtherChannel will fail over to the next backup adapter in the hope that there is a network path to the remote host through the next adapter. In this setup, not only should every adapter be connected to a different switch, but each switch should also have a different route to the host that is pinged.
This ping feature is only available in Network Interface Backup mode. However, in AIX 5.2, if the ping feature is enabled and a failover due to ping failure has occurred, the EtherChannel will not fail back to the primary adapter. The backup adapter will be the active channel as long as it is working because there is no way to know when the route to the pinged host will become reachable from the primary adapter. If a failure is detected while the backup adapter is active (that is, if either the ping attempts fail from the backup adapter or if the backup adapter itself fails), the EtherChannel will then failover to the primary adapter. If the failover occurred because the primary adapter failed, the EtherChannel will then come back to the primary adapter as soon it has come back up.
To configure Network Interface Backup in AIX 5.2, see Configure Network Interface Backup in AIX 5.2. To configure Network Interface Backup in previous versions of AIX, see Configure Network Interface Backup in previous AIX versions
Configure Network Interface Backup in AIX 5.2
With root authority, type smit etherchannel on the command line.
Select Add an EtherChannel from the list and press Enter.
Select the primary Ethernet adapter and press Enter. This is the adapter that will be used until it fails.
Note
The Available Network Adapters displays all Ethernet adapters. If you select an Ethernet adapter that is already being used, you will get an error message and will need to detach this interface before you can use it. See the ifconfig command for information on how to detach an interface.
Enter the information in the fields according to the following guidelines:
EtherChannel Adapters: You should see the primary adapter you selected in the previous step.
Enable Alternate EtherChannel Address: This field is optional. Setting this to yes will enable you to specify a MAC address that you want the EtherChannel to use. If you set this option to no, the EtherChannel will use the MAC address of the primary adapter.
Alternate EtherChannel Address: If you set Enable Alternate EtherChannel Address to yes, specify the MAC address that you want to use here. The address you specify must start with 0x and be a 12-digit hexadecimal address.
Enable Gigabit Ethernet Jumbo Frames: This field is optional. In order to use this, your switch must support jumbo frames. This will only work with Standard Ethernet, not IEEE 802.3. Set this to yes if you want to use it.
Mode: It is irrelevant which mode of operation you select because there is only one adapter in the main EtherChannel. All packets will be sent over that adapter until it fails. There is no netif_backup mode because that mode can be emulated using a backup adapter.
Backup Adapter: Enter the adapter that you want to be your backup adapter. After a failover, this adapter will be used until the primary adapter recovers. It is recommended to use the preferred adapter as the primary adapter.
Internet Address to Ping: The field is optional. The EtherChannel will ping the IP address that you specify here. If the EtherChannel is unable to ping this address for Number of Retries time in Retry Timeout intervals, the EtherChannel will switch adapters.
Number of Retries: Enter the number of ping response failures that are allowed before the EtherChannel switches adapters. The default is three. This field is optional and valid only if you have set an Internet Address to Ping.
Retry Timeout: Enter the number of seconds between the times when the EtherChannel will ping the Internet Address to Ping. The default is one second. This field is optional and valid only if you have set an Internet Address to Ping.
Press Enter after changing the desired fields to create the EtherChannel.
Configure IP over the new interface by typing smit chinet at the command line.
Select your new EtherChannel interface from the list.
Fill in all the required fields and press Enter.
Configure Network Interface Backup in previous AIX versions
With root authority, type smit etherchannel on the command line.
Select Add an Etherchannel and press Enter.
Select the adapters that you want to include in the EtherChannel, both primary and secondary.
Note
The Available Network Adapters displays all Ethernet adapters. If you select an Ethernet adapter that is already being used, you will get an error message. You first need to detach that interface by using the ifconfig command.
Enter the information in the fields according to the following guidelines:
Etherchannel adapters: You should see the adapters that you selected in the previous step.
Enable ALTERNATE ETHERCHANNEL address: This field is optional. Setting this to yes will enable you to specify a MAC address that you want the EtherChannel to use. If you set this option to no, the EtherChannel will use the MAC address of the first adapter specified.
ALTERNATE ETHERCHANNEL address: If you set Enable ALTERNATE ETHERCHANNEL address to yes, specify the MAC address that you want the EtherChannel to use here. The address you specify must start with 0x and be a 12-digit hexadecimal value.
Mode: Select netif_backup.
Enable GIGABIT ETHERNET JUMBO frames: This field is optional. In order to use this, your switch must support jumbo frames. This will only work on Standard Ethernet, not IEEE 802.3. Set this to yes if you want to enable it.
Internet Address to Ping: This field is optional. The EtherChannel will ping the IP address you specify here. If the EtherChannel is unable to ping this address for Number of Retries times in Retry Timeout intervals, the EtherChannel will switch adapters.
Number of Retries: Enter the number of ping response failures that are allowed before the EtherChannel switches adapters. The default is three. This field is optional and valid only if you set an Internet Address to Ping.
Retry Timeout: Enter the number of seconds between the times when the EtherChannel will ping the Internet Address to Ping. The default is one second. This field is optional and valid only if you have set and Internet Address to Ping.
Press Enter after changing the desired fields to create the EtherChannel.
Configure IP over the new interface by typing smit chinet at the command line.
Select your new EtherChannel interface from the list.
Fill in all required fields and press Enter.
Managing an EtherChannel
This section will tell you how to perform the following tasks:
List EtherChannels
Change the Alternate Address
Add, remove, or change adapters in an EtherChannel
Remove an EtherChannel
Configure or remove a backup adapter on an existing EtherChannel
List EtherChannels
On the command line, type smit etherchannel.
Select List All EtherChannels and press Enter.
Change the Alternate Address
This enables you to specify a MAC address for your EtherChannel.
Detach the EtherChannel by typing ifconfig interface detach, where interface is your EtherChannel's interface.
On the command line, type smit etherchannel.
Select Change / Show Characteristics of an EtherChannel and press Enter.
If you have multiple EtherChannels, select the EtherChannel for which you want to create an alternate address.
Change the value in Enable Alternate EtherChannel Address to yes.
Enter the alternate address in the Alternate EtherChannel Address field. The address must start with 0x and be a 12-digit hexadecimal address.
Press Enter to complete the process.
Add, remove, or change adapters in an EtherChannel
Detach the EtherChannel by typing ifconfig interface detach, where interface is your EtherChannel's interface.
On the command line type, smit etherchannel.
Select Change / Show Characteristics of an EtherChannel and press Enter.
Select the EtherChannel that you want to modify.
Select the primary adapters that you want in your EtherChannel and press Enter. If you are using EtherChannel backup, do not select that adapter here.
Fill in the necessary fields and press Enter.
Remove an EtherChannel
Detach the EtherChannel by typing ifconfig interface detach, where interface is your EtherChannel's interface.
On the command line type smit etherchannel.
Select Remove an EtherChannel and press Enter.
Select the EtherChannel that you want to remove and press Enter.
Configure or remove a backup adapter on an existing EtherChannel
The following procedure configures or removes a backup adapter on an EtherChannel. This option is available only in AIX 5.2.
Detach the EtherChannel by typing ifconfig interface detach, where interface is your EtherChannel's interface.
On the command line, type smit etherchannel.
Select Change / Show Characteristics of an EtherChannel.
Select the EtherChannel that you are adding or modifying the backup adapter on.
Enter the adapter that you want to use as your backup adapter in the Backup Adapter field, or select NONE if you wish to stop using the backup adapter.
Troubleshooting EtherChannel
If you are having trouble with your EtherChannel, you can use tcpdump and iptrace to troubleshoot the EtherChannel. The trace hook id for the transmission packets is 2FA and for other events is 2FB. You cannot trace receive packets on the EtherChannel as a whole, but you can trace each adapter's receive trace hooks.
You can also use the entstat command to get the aggregate statistics of all the adapters in the EtherChannel. For example, entstat ent7 will display the aggregate statistics of ent7. Adding the -d flag will also display the statistics of each adapter individually. For example, typing entstat -d ent7 will show you the aggregate statistics of the EtherChannel as well as the statistics of each individual adapter in the EtherChannel.
Note
In the General Statistics section, the number shown in Adapter Reset Count is the number of failovers. In EtherChannel backup, coming back to the main EtherChannel from the backup adapter is not counted as a failover. Only failing over from the main channel to the backup is counted.
In the Number of Adapters field, the backup adapter is counted in the number displayed.
If you notice that the failover time when you are using network interface backup mode or EtherChannel backup is much greater than five seconds, you should verify that your switch is not running the Spanning Tree Protocol (STP). When the switch detects a change in its mapping of switch port to MAC address, it runs the spanning tree algorithm to see if there are any loops in the network, and this may take some time. Network Interface Backup and EtherChannel backup may cause a change in the port to MAC address mapping, so disabling the algorithm should make the failover faster.
Also, note that switch ports have a forwarding delay counter that determines how soon after it is initialized each port should begin forwarding or sending packets. For this reason, when the main channel is re-enabled, you may notice that there is a delay of a few seconds before the connection is re-established, whereas the failover to the backup adapter is much faster. You might want to check the forwarding delay counter configured in your switch and make it as small as possible so that coming back to the main channel occurs as fast as possible.
Specifically, for the EtherChannel backup function to work correctly, the forwarding delay counter must not be more than 10 seconds, or coming back to the main EtherChannel might not work correctly. Setting the forwarding delay counter to the lowest value allowed by the switch is recommended.
If you find that adapter failures are not triggering failovers (in other words, if an adapter that is down is still being used by an EtherChannel to send packets), you might want to check to see if your adapter card needs to have link polling enabled to detect link failure. Some adapters cannot automatically detect their link status (whether they are up or down). To detect said condition, these adapters must enable a link polling mechanism, whereby a timer is started that periodically verifies the status of the link. This link polling is disabled by default because it decreases performance. For EtherChannel to work correctly with these adapters, however, the link polling mechanism must be enabled on each adapter before the EtherChannel is created.
Adapters that have a link polling mechanism have an ODM attribute called poll_link, which must be set to yes for the link polling to be enabled. Before creating the EtherChannel, use the following command on every adapter to be included in the channel: chdev -l ent? -a poll_link=yes
Likewise, for the jumbo frames option to work properly, aside from enabling the use_jumbo_frame attribute on the EtherChannel, you must also enable jumbo frames on each adapter before creating the EtherChannel using the following command: chdev -l ent? -a jumbo_frames=yes
Note
In AIX 5.2, this is done automatically when the use_jumbo_frame attribute is set on the EtherChannel.
Remote dump is not supported over an EtherChannel.