CSL_Cochin_c

WELCOME
TO
CSL Data Centre – Operational Training
P- Series IBM SERVER
2
CSL Data Centre – Operational Training
12.11.2014

 IBM equipment's Installed at Cochin Shipyard Ltd Data Center
 Introduction to IBM P Series Server.
 Server Specification & Server connectivity
 LPAR, Power VM,
 AIX Operating System
 Server hardware redundancy
 what all things should monitor on daily basis & The usual AIX commands to troubleshoot
issues.
 LPAR create , Power HA
 User logs & Error Logs
 File Systems & Disk Status
 User Administration
 Performance Monitoring
 1st level troubleshooting steps if any issue happens
 Backup & Restore
 Upgrading
AgendaDay-1
Day-2
3
 IBM equipment's Installed at Cochin Shipyard Ltd Data Center
 Introduction to IBM P Series Server.
 Server Specification & Server connectivity
 LPAR, Power VM,
 AIX Operating System
 Server hardware redundancy
 what all things should monitor on daily basis & The usual AIX commands to troubleshoot
issues.
 LPAR create , Power HA
 User logs & Error Logs
 File Systems & Disk Status
 User Administration
 Performance Monitoring
 1st level troubleshooting steps if any issue happens
 Backup & Restore
 Upgrading
12.11.2014
Day-3

 RISC – Reduced Instruction Set Computing (John Cocke 1970’s IBM’s TJ Watson
research center. )
 RS/6000
 POWER – Performance Optimised With Enhanced RISC
 Power 4,4+,5,5+,6,7,8
 Running Server in CSL DC : Power 750
 The Power 750 Express systems utilize the innovative IBM POWER7
processor technology that is designed to deliver unprecedented
performance, scalability, reliability, and manageability for demanding
workloads.
Introduction to IBM p-Series
4
 RISC – Reduced Instruction Set Computing (John Cocke 1970’s IBM’s TJ Watson
research center. )
 RS/6000
 POWER – Performance Optimised With Enhanced RISC
 Power 4,4+,5,5+,6,7,8
 Running Server in CSL DC : Power 750
 The Power 750 Express systems utilize the innovative IBM POWER7
processor technology that is designed to deliver unprecedented
performance, scalability, reliability, and manageability for demanding
workloads.
12.11.2014

 Rack-mount (4U) configuration
 Processors:
 6, 12, 18, and 24-core design with one, two, three, or four 3.3 GHz
processor cards
or 3.3 GHz Processor cards
 8, 16, 24, and 32-core design with one, two, three, or four 3.55
GHz processor cards.
 Up to 512 GB of 1066 MHz ECC (error checking and correcting) memory,
expandable to 128 GB per processor card.
5
 Rack-mount (4U) configuration
 Processors:
processor cards
or 3.3 GHz Processor cards
 8, 16, 24, and 32-core design with one, two, three, or four 3.55
GHz processor cards.
 Up to 512 GB of 1066 MHz ECC (error checking and correcting) memory,
expandable to 128 GB per processor card.
12.11.2014

 8 x 2.5-inch DASD/SSD/Media backplane with an external SAS port
 1 to 8 SFF (Small Form Factor) DASD or solid state drives (mixing
allowed).
 Choice of two Integrated Virtual Ethernet daughter cards:
 Quad-port 1 Gb IVE
 Dual-port 10 Gb IVE
 Two media bays:
 One slim bay for a DVD-RAM (required)
 One half-height bay for an optional tape drive or removable disk
 A maximum of five hot-swap slots:
 Two PCIe x8 slots, short card length (slots 1 and 2)
 One PCIe x8 slot, full card length (slot 3)
 Two PCI-X DDR slots, full card length (slots 4 and 5)
 One GX+ slot (shares same space as PCIe x8 slot 2)
 One GX++ slot (shares same space as PCIe x8 slot 1)
6
 8 x 2.5-inch DASD/SSD/Media backplane with an external SAS port
 1 to 8 SFF (Small Form Factor) DASD or solid state drives (mixing
allowed).
 Choice of two Integrated Virtual Ethernet daughter cards:
 Quad-port 1 Gb IVE
 Dual-port 10 Gb IVE
 Two media bays:
 One slim bay for a DVD-RAM (required)
 One half-height bay for an optional tape drive or removable disk
 A maximum of five hot-swap slots:
 Two PCIe x8 slots, short card length (slots 1 and 2)
 One PCIe x8 slot, full card length (slot 3)
 Two PCI-X DDR slots, full card length (slots 4 and 5)
 One GX+ slot (shares same space as PCIe x8 slot 2)
 One GX++ slot (shares same space as PCIe x8 slot 1)
12.11.2014

 Integrated:
 Service Processor
 Quad-port 10/100/1000 Mb Ethernet
 Energy Scale technology
 Hot-swap and redundant cooling
 Three USB ports; two system ports
 Two HMC ports; two SPCN(System Power Control Network) ports
 Two Power Supplies, 1725 Watt AC, Hot-swap
7
 Integrated:
 Service Processor
 Quad-port 10/100/1000 Mb Ethernet
 Energy Scale technology
 Hot-swap and redundant cooling
 Three USB ports; two system ports
 Two HMC ports; two SPCN(System Power Control Network) ports
 Two Power Supplies, 1725 Watt AC, Hot-swap
12.11.2014

Power 750 Front & Rear View
8
12.11.2014

9
12.11.2014

Server & Storage & SAN Connectivity (Refer to connectivity PDF)
10
12.11.2014

HMC, LPAR, PowerVM, PowerHA & Profile
HMC
 Required to partition any box
 Can use HMC to manage systems
 Provides a console to manage hardware
 Detecting, reporting and storing changes in hardware
 Vterms to partitions
LPAR
AIX logical partition virtual machine technology is released by IBM with AIX as a full
virtualization solution. LPAR differs from other popular alternatives like Xen and
VMware in terms of operation, performance and flexibility.
Logical partition : The allocation of system resources to create logically separate
systems within the same physical footprint
Reasons to Partition :
 Consolidation
 Production and Test on same hardware
 Multiple Operating Systems
 Consolidate Applications on different time zones
11
12.11.2014
HMC
 Required to partition any box
 Can use HMC to manage systems
 Provides a console to manage hardware
 Detecting, reporting and storing changes in hardware
 Vterms to partitions
LPAR
AIX logical partition virtual machine technology is released by IBM with AIX as a full
virtualization solution. LPAR differs from other popular alternatives like Xen and
VMware in terms of operation, performance and flexibility.
Logical partition : The allocation of system resources to create logically separate
systems within the same physical footprint
Reasons to Partition :
 Consolidation
 Production and Test on same hardware
 Multiple Operating Systems
 Consolidate Applications on different time zones

System resources include:
 Processors
 Memory
 System buses
 Disk
 I/O controllers and devices
12
12.11.2014
System resources include:
 Processors
 Memory
 System buses
 Disk
 I/O controllers and devices
System
Model
Processor Type Processor
Version
Number Of
Processors
CPU
Type
Kernel
Type
Memory Server
Qty
IBM,8233-
E8B
PowerPC_POWER7
PV_7_Compat
24
64-
bit
64-bit 368GB 2

Keyword for Virtualization
 PowerVM
 Physical CPU - Virtual CPU (Processor Virtualization) - Logical CPU
 SMT
 Sharing Mode (Capped & Uncapped)
 IBM LPARs with dedicated I/O
 IBM LPARs with Virtual I/O Servers
 Shared Ethernet Adapter (SEA) : Virtualizing Network
 NPIV Virtualization
 DLPAR
 Live Partition Mobility
 Live Application Mobility
 Active Memory Sharing
 Active Memory Expansion
13
12.11.2014
 PowerVM
 Physical CPU - Virtual CPU (Processor Virtualization) - Logical CPU
 SMT
 Sharing Mode (Capped & Uncapped)
 IBM LPARs with dedicated I/O
 IBM LPARs with Virtual I/O Servers
 Shared Ethernet Adapter (SEA) : Virtualizing Network
 NPIV Virtualization
 DLPAR
 Live Partition Mobility
 Live Application Mobility
 Active Memory Sharing
 Active Memory Expansion

PowerVM
PowerVM is a combination of hardware, firmware, and software that provides CPU,
network, and disk virtualization. These are the main virtualization technologies:
 POWER7 hardware
 POWER Hypervisor
 Virtual I/O Server
PowerVM Hypervisor delivers functions that enable capabilities including
dedicated-processor partitions, micro-partitioning, virtual processors, virtual
Ethernet adapters, virtual SCSI adapters, virtual Fiber Channel adapters, and virtual
consoles.
Supports multiple operating environments on a single system. The POWER
Hypervisor is a firmware layer sitting between the hosted operating systems and the
server hardware.
Virtual I/O Server for providing virtualized devices to its client partitions.
14
12.11.2014
PowerVM
PowerVM is a combination of hardware, firmware, and software that provides CPU,
network, and disk virtualization. These are the main virtualization technologies:
 POWER7 hardware
 POWER Hypervisor
 Virtual I/O Server
PowerVM Hypervisor delivers functions that enable capabilities including
dedicated-processor partitions, micro-partitioning, virtual processors, virtual
Ethernet adapters, virtual SCSI adapters, virtual Fiber Channel adapters, and virtual
consoles.
Supports multiple operating environments on a single system. The POWER
Hypervisor is a firmware layer sitting between the hosted operating systems and the
server hardware.
Virtual I/O Server for providing virtualized devices to its client partitions.

Physical CPU - Virtual CPU - Logical CPU:
Physical Processors are cores in the machine. Virtual Processors are assigned to an
LPAR manually when LPAR is created. Logical Processors are created automatically
by AIX, depending on the SMT setting.
Simultaneous Multi-Threading (SMT):
SMT is that feature of a Power Processor, when multiple hardware threads can run on
one physical processor at the same time (a processor appears as 2 or 4 logical CPU).
mpstat or topas -L is showing it:
At the column "lpa" the sign "-" will show turned off SMT threads .
15
12.11.2014
Physical CPU - Virtual CPU - Logical CPU:
Physical Processors are cores in the machine. Virtual Processors are assigned to an
LPAR manually when LPAR is created. Logical Processors are created automatically
by AIX, depending on the SMT setting.
Simultaneous Multi-Threading (SMT):
SMT is that feature of a Power Processor, when multiple hardware threads can run on
one physical processor at the same time (a processor appears as 2 or 4 logical CPU).
mpstat or topas -L is showing it:
At the column "lpa" the sign "-" will show turned off SMT threads .

16
12.11.2014

17
12.11.2014

IBM LPARs with dedicated I/O :
The baseline configuration is a traditional AIX deployment with dedicated HBAs and
NICs.
IBM LPARs with Virtual I/O Servers :
With Virtual I/O Servers LPARs can share physical resources. The VIOS provides
virtual SCSI, virtual fiber channel, and virtual networking for sharing. Sharing of
resources between LPARs enables more efficient utilization of physical resources and
facilitates consolidation.
SEA
A SEA can be used to connect a physical Ethernet network to a virtual Ethernet
network. The SEA hosted in the Virtual I/O Server acts as a layer-2 bridge between
the internal and external network.
Command for single VIO server:
$mkvdev -sea <PHYS> -vadapter <VIRT> -default <VIRT> -defaultid <VLAN>
$mkvdev-sea ent0 -vadapterent1 -default ent1 -defaultid1
18
12.11.2014
IBM LPARs with dedicated I/O :
The baseline configuration is a traditional AIX deployment with dedicated HBAs and
NICs.
IBM LPARs with Virtual I/O Servers :
With Virtual I/O Servers LPARs can share physical resources. The VIOS provides
virtual SCSI, virtual fiber channel, and virtual networking for sharing. Sharing of
resources between LPARs enables more efficient utilization of physical resources and
facilitates consolidation.
SEA
A SEA can be used to connect a physical Ethernet network to a virtual Ethernet
network. The SEA hosted in the Virtual I/O Server acts as a layer-2 bridge between
the internal and external network.
Command for single VIO server:
$mkvdev -sea <PHYS> -vadapter <VIRT> -default <VIRT> -defaultid <VLAN>
$mkvdev-sea ent0 -vadapterent1 -default ent1 -defaultid1

SEA in Dual VIO Server Configuration Here control channel is configured through ent2.
SEA ent3 is created using physical adapter ent0 and virtual adapter ent1, & the trunk
priority of VIO server1 is 1 and for VIO server2 is 2
19
12.11.2014

Command for Dual VIO Server where SEA failover is possible through SEA and
control channel:
$mkvdev -sea <PHYS> -vadapter <VIRT> -default <VIRT> -defaultid <VLAN> -attr
ha_mode=auto ctl_chan=<CONT>
$mkvdev -sea ent0 -vadapter ent1 -default ent1 -defaultid 1 -attr ha_mode=auto
ctl_chan=ent2
To assign the IP Address to SEA port:
$mktcpip -hostname vios1_55A -inetaddr 10.10.1.52 –interface en3 -netmask
255.255.255.128 -start
 Adapter ID: Any ID for the Virtual ethernet adapter
 Port Virtual Ethernet: PVID given to this adapter (usually a VLAN ID which is not used
at any other adapter to avoid untagging packets)
 IEE 802.1q: Additional VLAN IDs can be specified here
 Ethernet bridging: This checkbox enables accessing external networks
 Priority: For SEA Failover mode, you can specify which SEA should be the primary (here
it is the secondary SEA)
 The real adapter can be a physical Ethernet adapter, a Link Aggregation or EtherChannel
device, or a Logical Host Ethernet Adapter.
20
12.11.2014
Command for Dual VIO Server where SEA failover is possible through SEA and
control channel:
$mkvdev -sea <PHYS> -vadapter <VIRT> -default <VIRT> -defaultid <VLAN> -attr
ha_mode=auto ctl_chan=<CONT>
$mkvdev -sea ent0 -vadapter ent1 -default ent1 -defaultid 1 -attr ha_mode=auto
ctl_chan=ent2
To assign the IP Address to SEA port:
$mktcpip -hostname vios1_55A -inetaddr 10.10.1.52 –interface en3 -netmask
255.255.255.128 -start
 Adapter ID: Any ID for the Virtual ethernet adapter
 Port Virtual Ethernet: PVID given to this adapter (usually a VLAN ID which is not used
at any other adapter to avoid untagging packets)
 IEE 802.1q: Additional VLAN IDs can be specified here
 Ethernet bridging: This checkbox enables accessing external networks
 Priority: For SEA Failover mode, you can specify which SEA should be the primary (here
it is the secondary SEA)
 The real adapter can be a physical Ethernet adapter, a Link Aggregation or EtherChannel
device, or a Logical Host Ethernet Adapter.

 The virtual Ethernet adapter (trunk adapter in the SEA) must be created with the
following settings:
21
12.11.2014

Network Interface Backup (NIB)
Network Interface Backup (NIB) in the client partition can be used to achieve network
redundancy when using two Virtual I/O Severs. The client partition uses two virtual
Ethernet adapters to create an EtherChannel that consists of one primary adapter and
one backup adapter. The interface is defined on the EtherChannel. If the primary adapter
becomes unavailable, the Network Interface Backup switches to the backup adapter.
22
12.11.2014

NPIV (Virtual Fibre Channel Adapter)
With NPIV, we can configure the managed system so that multiple logical partitions
can access independent physical storage through the same physical fibre channel
adapter. (NPIV means N_Port ID Virtualization. N_Port ID is a storage term, for node
port ID, to identify ports on the nod (FC Adapter) in the SAN area.)
$ lsnports: This command will display the list of fabric to 1 if the virtualization is supported
on the card.
$ vfcmap -vadapter vfchost0 -fcp fcs0 : Used to map fcs0 to vfchost0
$ lsmap –npiv–all: Lists all npiv mappings.
23
12.11.2014
NPIV (Virtual Fibre Channel Adapter)
With NPIV, we can configure the managed system so that multiple logical partitions
can access independent physical storage through the same physical fibre channel
adapter. (NPIV means N_Port ID Virtualization. N_Port ID is a storage term, for node
port ID, to identify ports on the nod (FC Adapter) in the SAN area.)
$ lsnports: This command will display the list of fabric to 1 if the virtualization is supported
on the card.
$ lsmap –npiv–all: Lists all npiv mappings.

NPIV creation and how they are related together:
FCS0: Physical FC Adapter installed on the VIOS
VFCHOST0: Virtual FC (Server) Adapter on VIOS
FCS0 (on client): Virtual FC adapter on VIO client
24
12.11.2014

25
12.11.2014
11

11
26
12.11.2014
2

Storage – SAN Switch - Server
Server(HBA,WWN)
LUN
SAN Switch (Zonning)(WWN,WWN)(Refer to Zonning Screenshot)
LUN
Volume
Disk pool (Storage Pool)
Mdisk, Mdisk,Mdisk (RAID Arrays)
27
12.11.2014
Server(HBA,WWN)
LUN
SAN Switch (Zonning)(WWN,WWN)(Refer to Zonning Screenshot)
LUN
Volume
Disk pool (Storage Pool)
Mdisk, Mdisk,Mdisk (RAID Arrays)

 AIX – Advanced Interactive eXecutive System
 AIX 5L version 5.1, 5.2, 5.3,
 AIX 6L version 6.0, 6.1
 AIX 7.1 (AIX 7.1 : 7100-02-02-1316 ) : Presently Running in CSL DC
oslevel -s
Applies all flags to service packs. The service pack level returned is in the
format 7100-02-02-1316.
where 7100 refers to base level 7.1.0.0; 02 refers to technology level 2; 02
refers to service pack 2;and 1316 refers to the yyww build date in year and
weeks, in this case, the 16th week of the year 2013.
Installation Options
1. New and Complete overwrite
2. Migration
3. Preservation
About AIX
28
 AIX – Advanced Interactive eXecutive System
 AIX 5L version 5.1, 5.2, 5.3,
 AIX 6L version 6.0, 6.1
 AIX 7.1 (AIX 7.1 : 7100-02-02-1316 ) : Presently Running in CSL DC
oslevel -s
Applies all flags to service packs. The service pack level returned is in the
format 7100-02-02-1316.
where 7100 refers to base level 7.1.0.0; 02 refers to technology level 2; 02
refers to service pack 2;and 1316 refers to the yyww build date in year and
weeks, in this case, the 16th week of the year 2013.
Installation Options
1. New and Complete overwrite
2. Migration
3. Preservation
12.11.2014

1. New and Complete Overwrite installation
Generally, the New and Complete Overwrite method is used when you
have a new machine without a prior or useful system installation. In this case, the
hard disk or disks on which you are installing the BOS are empty. This is the only
possible installation method for a new machine. You want to install onto a hard disk
that contains an existing root volume group that you wish to completely overwrite.
For example, this might occur if your root volume group has become corrupted. You
want to reassign your hard disks, that is, to make your rootvg smaller and assign
less disk space to it.
2. Migration installation
Use the migration installation method to upgrade AIX Version 4.2, 4.3,
AIX 5L Version 5.1, or Version 5.2 to AIX 5L Version 5.3 while preserving the
existing root volume group . The installation process determines which optional
software products must be installed. With the exception of /tmp, this method
preserves most file systems, including the root volume group, logical volumes, and
system configuration files.
29
1. New and Complete Overwrite installation
Generally, the New and Complete Overwrite method is used when you
have a new machine without a prior or useful system installation. In this case, the
hard disk or disks on which you are installing the BOS are empty. This is the only
possible installation method for a new machine. You want to install onto a hard disk
that contains an existing root volume group that you wish to completely overwrite.
For example, this might occur if your root volume group has become corrupted. You
want to reassign your hard disks, that is, to make your rootvg smaller and assign
less disk space to it.
2. Migration installation
Use the migration installation method to upgrade AIX Version 4.2, 4.3,
AIX 5L Version 5.1, or Version 5.2 to AIX 5L Version 5.3 while preserving the
existing root volume group . The installation process determines which optional
software products must be installed. With the exception of /tmp, this method
preserves most file systems, including the root volume group, logical volumes, and
system configuration files. 12.11.2014

3. Preservation installation
Use the preservation installation method when a version of the BOS is
installed on your system, and you want to preserve the user data in the root volume
group. However, this method overwrites the /usr, /tmp, /var, and / (root) file
systems by default, so any user data in these directories is lost. These file systems
are removed and recreated, so any other LPPs or filesets that you installed on the
system will also be lost. System configuration must be done after doing a
preservation installation.
The /etc/preserve.list file contains a list of system files to be copied and saved
during a preservation BOS installation.
30
3. Preservation installation
Use the preservation installation method when a version of the BOS is
installed on your system, and you want to preserve the user data in the root volume
group. However, this method overwrites the /usr, /tmp, /var, and / (root) file
systems by default, so any user data in these directories is lost. These file systems
are removed and recreated, so any other LPPs or filesets that you installed on the
system will also be lost. System configuration must be done after doing a
preservation installation.
The /etc/preserve.list file contains a list of system files to be copied and saved
during a preservation BOS installation.
12.11.2014

ROOTVG – System defined Volume Group where AIX resides.
Logical Volumes are
hd1 /home
hd2 /usr
hd3 /tmp
hd4 /
hd5 BLV
hd6 paging space
hd8 jfslog
hd9var /var
hd10opt /opt
31
12.11.2014
ROOTVG – System defined Volume Group where AIX resides.
Logical Volumes are
hd1 /home
hd2 /usr
hd3 /tmp
hd4 /
hd5 BLV
hd6 paging space
hd8 jfslog
hd9var /var
hd10opt /opt

Alternate disk installation, allows for system installation on a system while it is still up
and running.
Alternate disk installation can be used in one of two ways: Cloning the current
running rootvg to an alternate disk.
Command : smitty alt_clone
AND Installing a mksysb image on another disk.
smitty alt_mksysb
Alternate disk installation
32
12.11.2014
Alternate disk installation, allows for system installation on a system while it is still up
and running.
Alternate disk installation can be used in one of two ways: Cloning the current
running rootvg to an alternate disk.
Command : smitty alt_clone
AND Installing a mksysb image on another disk.
smitty alt_mksysb

Filesets
A fileset is the smallest installable base unit for the AIX 5L operating system.
Eg :- bos.net.nfs.client.
Packages
A package is a group of separately installable filesets that provide a set of related
functions.
Eg :- bos.net
Licensed Program Products
A Licensed Program Product (LPP) is a complete software product including all
packages associated with that licensed program.
Eg :- BOS
Bundles
A bundle is a list of software that can contain filesets, packages, and LPPs that
are suited for a particular use.
lslpp –l / lslpp –l | grep bos.net*
AIX Packaging Terminology
33
12.11.2014
Filesets
A fileset is the smallest installable base unit for the AIX 5L operating system.
Eg :- bos.net.nfs.client.
Packages
A package is a group of separately installable filesets that provide a set of related
functions.
Eg :- bos.net
Licensed Program Products
A Licensed Program Product (LPP) is a complete software product including all
packages associated with that licensed program.
Eg :- BOS
Bundles
A bundle is a list of software that can contain filesets, packages, and LPPs that
are suited for a particular use.
lslpp –l / lslpp –l | grep bos.net*

PTFs
PTF is an acronym for Program Temporary Fix. A PTF is an updated fileset or a new
fileset that fixes a previous system problem. PTFs are installed in the same way as
regular filesets by the use of the installp command.
Command : installp -ac -d /dev/cd0 fileset
APAR
APAR is an acronym for Authorized Program Analysis Report. An APAR is an
emergency fix, or interim fix, to a unique problem on the system.
Commands : instfix –k IY65465 -d /dev/cd0
instfix –ik “IY32232 IY654564”
instfix –I | grep ML
Smitty instfix or smitty update_by_fix,
Smitty show_apar_stat
AIX Packaging Terminology
34
12.11.2014
PTFs
PTF is an acronym for Program Temporary Fix. A PTF is an updated fileset or a new
fileset that fixes a previous system problem. PTFs are installed in the same way as
regular filesets by the use of the installp command.
Command : installp -ac -d /dev/cd0 fileset
APAR
APAR is an acronym for Authorized Program Analysis Report. An APAR is an
emergency fix, or interim fix, to a unique problem on the system.
Commands : instfix –k IY65465 -d /dev/cd0
instfix –ik “IY32232 IY654564”
instfix –I | grep ML
Smitty instfix or smitty update_by_fix,
Smitty show_apar_stat

Software can be installed in one of two states: Applied or Committed.
The applied state places software on the system and retains the previous
version of the software. When an update is in the applied state, the previous version is
stored in the /usr/lpp/PackageName directory, where Package Name could be bos.net
which is a package. This process is useful for deploying or testing new software, where
it may be necessary to go back to the previous version of the software in case of errors.
Command : intstallp –a <PackageName>
The committed state places software on the system and removes all previous
levels of the software from the /usr/lpp/PackageName directory. If committed software
needs to be removed, you cannot go back to the previous version without a complete
reinstall of the previous version of the software. We recommend you to install new
software in the applied state, rather than the committed state, until the new software
has been thoroughly tested .
Command : intstallp –c <PackageName>
Installing software
35
12.11.2014
Software can be installed in one of two states: Applied or Committed.
The applied state places software on the system and retains the previous
version of the software. When an update is in the applied state, the previous version is
stored in the /usr/lpp/PackageName directory, where Package Name could be bos.net
which is a package. This process is useful for deploying or testing new software, where
it may be necessary to go back to the previous version of the software in case of errors.
Command : intstallp –a <PackageName>
The committed state places software on the system and removes all previous
levels of the software from the /usr/lpp/PackageName directory. If committed software
needs to be removed, you cannot go back to the previous version without a complete
reinstall of the previous version of the software. We recommend you to install new
software in the applied state, rather than the committed state, until the new software
has been thoroughly tested .
Command : intstallp –c <PackageName>

Components of LVM.
 Volume Groups,
 Physical volumes,
 Physical Partitions,
 Logical Volumes,
 Logical Partitions.
Logical Volume Manager.
36
12.11.2014

Limitation of LVM.
37
12.11.2014
 mkvg -y testvg -s 4 -f hdisk4
 mkvg -B -y testvg -s 128 -V 101 –f hdisk6
 mkvg -S -y testvg -s 1 -f hdisk3 hdisk4 hdisk5 hdisk6 hdisk7
 mklv -y lv3 -t jfs2 -a im test1vg 10 hdisk5
 crfs -v jfs2 -d /dev/copylv -g testvg -a size=10M -m /fs1
 Extendvg vgname hdisk2
 Mirrorvg vgname

Intra-physical volume allocation policy:
E M C M E
38
12.11.2014
Inner Edge
Inner Middle
Center
Outer Middle (Middle)
Center Edge (Edge)

39
12.11.2014

40
12.11.2014

LPAR Creation
Refer to LPAR Doc ------
41
13.11.2014

Performance Monitoring
vmstat
iostat
topas
netstat
sar
ps
42
13.11.2014
vmstat
iostat
topas
netstat
sar
ps

43
13.11.2014

44
13.11.2014

45
13.11.2014

46
13.11.2014

File System Differences.
47
13.11.2014

 chvg -ay newvg <--- Auto varyon flag
 chvg -L 128 testvg <--- The LTG is the maximum transfer size of an LV and is common to all the LVs in
the VG
 chvg -G testvg <--- To change the format of the volume group from original to scalable.
 chvg -hY testvg <--- Hot Spare yes (one to Many)
 chvg -hy testvg <--- Hot Spare yes (one to one)
 chvg –u <--- unlocking the VG
 extendvg -f testvg hdiskx <--- Increase the VG size
 reducevg -d testvg hdiskx <--- Decrease the VG size
 disk replaced -> cfgmgr <--it will find the new disk (i.e. hdisk1)
 chvg -Qn rootvg <--only if quorum setting has not yet been disabled, because this needs a restart
 mirrorvg -s rootvg <--add mirror for rootvg (-s: synchronization will not be done)
User Administration
48
13.11.2014
 chvg -ay newvg <--- Auto varyon flag
 chvg -L 128 testvg <--- The LTG is the maximum transfer size of an LV and is common to all the LVs in
the VG
 chvg -G testvg <--- To change the format of the volume group from original to scalable.
 chvg -hY testvg <--- Hot Spare yes (one to Many)
 chvg -hy testvg <--- Hot Spare yes (one to one)
 chvg –u <--- unlocking the VG
 extendvg -f testvg hdiskx <--- Increase the VG size
 reducevg -d testvg hdiskx <--- Decrease the VG size
 disk replaced -> cfgmgr <--it will find the new disk (i.e. hdisk1)
 chvg -Qn rootvg <--only if quorum setting has not yet been disabled, because this needs a restart
 mirrorvg -s rootvg <--add mirror for rootvg (-s: synchronization will not be done)

 syncvg -v rootvg <--synchronize the new copy (lsvg rootvg | grep STALE)
 bosboot -a <--we changed the system so create boot image (-a: create complete boot image and device)
(hd5 is mirrorred, no need to do it for each disk. ie. bosboot -ad hdisk0)
 bootlist -m normal hdisk0 hdisk1 <--set normal bootlist
 bootlist -m service hdisk0 hdisk1 <--set bootlist when we want to boot into service mode
 shutdown -Fr <--this is needed if quorum has been disabled
 bootinfo -b <--shows the disk which was used for boot
 mklvcopy -k lv1 3 hdisk7 &
 Snap -gc
49
13.11.2014
 syncvg -v rootvg <--synchronize the new copy (lsvg rootvg | grep STALE)
 bosboot -a <--we changed the system so create boot image (-a: create complete boot image and device)
(hd5 is mirrorred, no need to do it for each disk. ie. bosboot -ad hdisk0)
 bootlist -m normal hdisk0 hdisk1 <--set normal bootlist
 bootlist -m service hdisk0 hdisk1 <--set bootlist when we want to boot into service mode
 shutdown -Fr <--this is needed if quorum has been disabled
 bootinfo -b <--shows the disk which was used for boot
 mklvcopy -k lv1 3 hdisk7 &
 Snap -gc

User Administration for VIO
 license –accept
 oem_setup_env
 backupios
 updateios
updateios –dev /update <--To update the IOS software:
updateios –dev /cd0 -install –accept <-- To installs a new filesets (mainly used for TL updates)
updateios –commit <-- To commit all applied
updateios –reject <-- To rejects all uncommitted updates
 mirrorios
 ioslevel
 shutdown -restart
 lsmap
 Mkvdev
example==> mkvdev -vdevclient1_rootvg -vadapter vhost0 -dev client1_rootvg
50
13.11.2014
 license –accept
 oem_setup_env
 backupios
 updateios
updateios –dev /update <--To update the IOS software:
updateios –dev /cd0 -install –accept <-- To installs a new filesets (mainly used for TL updates)
updateios –commit <-- To commit all applied
updateios –reject <-- To rejects all uncommitted updates
 mirrorios
 ioslevel
 shutdown -restart
 lsmap
 Mkvdev
example==> mkvdev -vdevclient1_rootvg -vadapter vhost0 -dev client1_rootvg

 lsnports
 lsdev –slots
 cfgdev
 vfcmap -vadapter vfchost4 -fcp <--remove mapping
vfcmap -vadapter vfchost4 -fcp fcs2 <--create new mapping
 backupios -file /mnt/backup
backupios -file /mnt/backup -mksysb
 viosbr -backup -file /mnt/vio/vios1_devicebackup <--device mapping configuration backup
 viosbr –restore
 emgr -P <--list installed efix's (by label)
 emgr -r -L <--for each additional efix listed, run to remove
51
13.11.2014
 lsnports
 lsdev –slots
 cfgdev
 vfcmap -vadapter vfchost4 -fcp <--remove mapping
vfcmap -vadapter vfchost4 -fcp fcs2 <--create new mapping
 backupios -file /mnt/backup
backupios -file /mnt/backup -mksysb
 viosbr -backup -file /mnt/vio/vios1_devicebackup <--device mapping configuration backup
 viosbr –restore
 emgr -P <--list installed efix's (by label)
 emgr -r -L <--for each additional efix listed, run to remove

Power HA
CSLECCPRD2 (DB2)
CSLSRMPRD1 (SAP)
CSLEPPRD2 (DB2)
CSLEPSRMPRD1 (DB2)
CSLPIPRD2 (DB2)
CSLECCPRD2 (SAP)
CSLSRMPRD1 (DB2)
CSLEPPRD2 (SAP)
CSLEPSRMPRD1 (SAP)
CSLPIPRD2 (SAP)
Node 1 Node 2
52
13.11.2014
CSLECCPRD2 (DB2)
CSLSRMPRD1 (SAP)
CSLEPPRD2 (DB2)
CSLEPSRMPRD1 (DB2)
CSLPIPRD2 (DB2)
CSLECCPRD2 (SAP)
CSLSRMPRD1 (DB2)
CSLEPPRD2 (SAP)
CSLEPSRMPRD1 (SAP)
CSLPIPRD2 (SAP)
/db2
/usr/SAP
/sapmnt
Cluster Name, Node, RG, Repository Disk
Boot IP
Persistent IP
Service IP

Some Error and Solution
Check: LED: User Action:
File system full ? 553 Access the rootvg. Issue “df –k”.
Check if /tmp, /usr or / are full.
/etc/inittab?
/etc/environment?
553 Access the rootvg. Check /etc/inittab(empty, missing, or
corrupt?). Check /etc/environment.
BLV corrupt ? 551, 555,
557
Access the rootvg. Re-create the BLV:
# bosboot –ad /dev/hdiskx
53
13.11.2014
JFS log corrupt ? 551, 552,
554, 555,
556,557
Access rootvg before mounting the rootvg file systems. Re-
reate the JFS log: # logform /dev/hd8, Run fsck afterwards.
Superblock corrupt? 552, 554,
556
Run fsck against all rootvg file systems, if fsck indicates
errors (not an AIX file system), repair the superblock.
rootvg locked 551 Access rootvg and unlock the rootvg:
# chvg –u rootvg
ODM files missing ? 523 - 534 ODM files are missing or inaccessible. Restore the missing
files from a system backup
Mount of /usr or /var
failed
518 Check /etc/filesystem, Check network (remote mount), file
systems (fsck) and hardware

Total Etherchannel failure and LIMBO state on SEA:
 During dual VIOS install, when second SEA configured on VIOS2, network
connection was lost and received this errpt:
CE9566DF 0719154713 P H ent9 TOTAL ETHERCHANNEL
FAILURE
Limbo state means:
The physical network is not operational or network state is unknown, or the Shared
Ethernet Adapter cannot ping the specified remote host.
On the VIOS LPAR with wrong control channel:
 remove SEA device: rmdev...
 shutdown LPAR and change profile on HMC: control channel virt. adapter to the
correct virtual switch
 start LPAR and create SEA device again.
54
13.11.2014
Total Etherchannel failure and LIMBO state on SEA:
 During dual VIOS install, when second SEA configured on VIOS2, network
connection was lost and received this errpt:
CE9566DF 0719154713 P H ent9 TOTAL ETHERCHANNEL
FAILURE
Limbo state means:
The physical network is not operational or network state is unknown, or the Shared
Ethernet Adapter cannot ping the specified remote host.
On the VIOS LPAR with wrong control channel:
 remove SEA device: rmdev...
 shutdown LPAR and change profile on HMC: control channel virt. adapter to the
correct virtual switch
 start LPAR and create SEA device again.

Checking SEA on VIO server:
 padmin@vios1: / # lsdev -dev ent* | grep Shared
ent8 Available Shared Ethernet Adapter
 padmin@vios1: / # lsdev -dev ent8 -attr | grep adapter
pvid_adapter ent4 Default virtual adapter to use for non-VLAN-tagged packets True
real_adapter ent0 Physical adapter associated with the SEA True
55
13.11.2014
Checking SEA on VIO server:
 padmin@vios1: / # lsdev -dev ent* | grep Shared
ent8 Available Shared Ethernet Adapter
 padmin@vios1: / # lsdev -dev ent8 -attr | grep adapter
pvid_adapter ent4 Default virtual adapter to use for non-VLAN-tagged packets True
real_adapter ent0 Physical adapter associated with the SEA True

Replacement of a physical FC adapter with NPIV
1. identify the adapter
$ lsdev -dev fcs4 -child
name status description
fcnet4 Defined Fibre Channel Network Protocol Device
fscsi4 Available FC SCSI I/O Controller Protocol Device
2. unconfigure the mappings
$ rmdev -dev vfchost0 -ucfg
vfchost0 Defined
3. FC adapters and their child devices must be unconfigured or deleted
$ rmdev -dev fcs4 -recursive -ucfg
fscsi4 Defined
fcnet4 Defined
fcs4 Defined
56
13.11.2014
Replacement of a physical FC adapter with NPIV
1. identify the adapter
$ lsdev -dev fcs4 -child
name status description
fcnet4 Defined Fibre Channel Network Protocol Device
fscsi4 Available FC SCSI I/O Controller Protocol Device
2. unconfigure the mappings
$ rmdev -dev vfchost0 -ucfg
vfchost0 Defined
3. FC adapters and their child devices must be unconfigured or deleted
$ rmdev -dev fcs4 -recursive -ucfg
fscsi4 Defined
fcnet4 Defined
fcs4 Defined

4. Diagmenu
DIAGNOSTIC OPERATING INSTRUCTIONS ->
Task Selection ->
Hot Plug Task ->
PCI Hot Plug Manager ->
Replace/Remove a PCI Hot Plug Adapter.
----------------------------------------------------
Changing WWPN number:
There are 2 methods: changing dynamically (chhwres) or changing in the profile
(chsyscfg). Both of them are similar and both of them done in HMC CLI.
57
13.11.2014
4. Diagmenu
DIAGNOSTIC OPERATING INSTRUCTIONS ->
Task Selection ->
Hot Plug Task ->
PCI Hot Plug Manager ->
Replace/Remove a PCI Hot Plug Adapter.
----------------------------------------------------
Changing WWPN number:
There are 2 methods: changing dynamically (chhwres) or changing in the profile
(chsyscfg). Both of them are similar and both of them done in HMC CLI.

Thank You
Prepared
By
Tikaram Sethi
58
Thank You
Prepared
By
Tikaram Sethi
13.11.2014

CSL_Cochin_c

More Related Content

What's hot (20)

Viewers also liked (17)

Similar to CSL_Cochin_c (20)

CSL_Cochin_c