Ashish Kumar Padhy, ITA, ITIS

Objectives
Overview on Power System Hardware
About LPAR & its administration
OS Installation
Disk Administration & AIX Storage
OS Mirroring & Cloning
User Administration
Networking (Bonding/Routes)

Booting Procedure
OS Health Checking
Performance troubleshooting
Patching Procedure
Mksysb backup
HACMP Cluster Basics
Overview on NIMS Servers
VIO Concepts
2
Power Hardware Variant

IBM Power BLADE SERVERS includes ps704,

ps703, ps702, ps701, ps700. All in simple to
manage highly efficient way.

IBM Power EXPRESS SERVERS includes p710,

ps720, ps730, ps740, ps750. Available as tower
and rack standalone server with 4-32 cores
provides high computing performance.

IBM Power ENTERPRISE SERVERS includes

p750, p760, ps770, ps780, ps795. Provides upto
256 cores and upto 8TB memory.

3
IBM Power LINUX SERVERS includes 7R1,
7R2.Servers are designed to go head-to-head
with x86 server on cost delivering greater
performance, higher utilization and superior
availability.

IBM Power HPC SERVERS includes p755, p775

offers extreme performance for analytic and
big data workloads.

4
IBM Power Based on RISC Technology

Reduce Instruction Set Computing (RISC) based on processors

Implement the most used instruction in hardware.
Execute multiple instructions in one cycle
Provide synergy between hardware and software

Time To Execute Number of Clock cycles per Time taken for

a program = instructions X instruction X a clock cycle

IBM developed in 1970s RISC architecture with hardware RS/600.

Later enhanced the standard RISC technology by introducing the
newer Performance Optimized With Enhanced RISC (POWER).

5
Power System Hardware Architecture

Processor Ram Disk 1GNIC 10GNIC Fccard SAScard

6
About LPAR & Its Administration

A logical partition (LPAR) is the division of a computer's processor ,

memory and storage into multiple sets of resources so that each set
of resources can be operated independently with its own operating
system instance and application’s.
Interconnected POWER 750 Express Server

LPAR 1 LPAR 2

7
The number of logical partitions that can be created depends on the system's processor
model and resources available.

LPARs can have resources allocated based on the needs of the workload rather than the
amount contained in a physical building block.

On the IBM System p server implementation of LPARs, you can dynamically add and
remove resources (CPUs, memory, and I/O slots) to and from a partition while the
operating system is running.

HARDWARE MANAGEMENT CONSOLE

8
Partition configuration and control Dynamic partitioning for LPARs
Capacity Upgrade on Demand Diagnostics
Operational management Remote HMC control

9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
Login Prompt

30
Important Commands

#lsdev (list the devices available in the system)

#lsdev –Cc adapter (list the adapters available in the system)
#lsdev –Cc disk (list the disk available in the system)
#lsdev –Cc tape (list the tape available in the system)
#lscfg –vpl <device name> (complete information about device)
#lsslot –c pci (complete pci slot information)
#entstat –d <ethernet device name> (ethernet device name)
#prtconf (complete system information)

31
#smitty

32
#smit

33
User Administration
Each user has a unique name, numeric ID, and password
• File ownership is determined by a numeric user ID
• The owner is usually the user who created the file, but
ownership can be transferred by root
• Default users:
– root Superuser
– adm, sys, bin, ... IDs that own system files but cannot be used for login

Importance of user accounts

The security of the system is based on a user being assigned a unique name, user ID (UID)
and password. When the user logs in, the UID is used to validate all requests for file access.

File ownership
When a file is created, the UID associated with the process that created the file is assigned
ownership of the file. Only the owner or root can change the access permissions.

Automatically created user accounts

There are several user accounts automatically created. root, for example, is one. Some
user accounts are not made for login but only to own certain files. adm, sys, and bin.

34
Group
A group is a set of users, all of whom need access to a given set of files.
Every user is a member of at least one group and can be a member of several groups.
Default groups:
– System administrators: system
– Ordinary users: staff

Group hierarchy

35
User hierarchy

To protect important users and groups from members of the security group, AIX has
admin users and admin groups
Only root can add, remove, or change an admin user or admin group
Any user on the system can be defined as an admin user regardless of the group they
are in

Controlling access to the root account

• Restrict access to privileged logins

• root's passwords should be changed on an unannounced
schedule by the system administrator
• Assign different root passwords to different machines
• System administrators should always login as themselves
first and then su to root instead of logging in as root. This
helps provide an audit trail for root usage
• Do not include unsecured directories in root's PATH

36
File/Directory Permission

# ls -ld /usr/bin/passwd /usr/bin/crontab /tmp/

drwxrwxrwt 21 bin bin 8192 Jul 07 18:15 /tmp/
-r-sr-sr-x 1 root cron 43462 Aug 11 2011 /usr/bin/crontab
-r-sr-xr-x 1 root security 41924 Aug 11 2011 /usr/bin/passwd

User & Group Related Command

Create
#useradd –c “comment” –m -g <groupname> -G groupname1, groupname2… -u
<userid> Username

Modify
#usermod [option..] username

Delete
#userdel username (don’t use –r option without home directory back to checks)

User login
#users (current user login info)
#id (current user login info with details)
#finger (login users information with more information)
37
Group

Create
#mkgroup <groupname>

Delete Group
#rmgroup <groupname>

Important Commands
#lsuser –f <username>
#lsuser –f ALL
#lsgroup –f <username>
#lsgroup –f ALL
#chown <owner:groupower> filename/Directory
#chown -R <owner:groupower> filename/Directory
#chmod <perm> filename/Directory
#chmod –R <perm> filename/Directory
#last
#passwd

38
File updated
The useradd command has read and write permissions to the following files.
/etc/passwd
Contains the basic attributes of users.
/etc/security/user
Contains the extended attributes of users.
/etc/security/user.roles
Contains the administrative role attributes of users.
/etc/security/limits
Defines resource quotas and limits for each user.
/etc/security/environ
Contains the environment attributes of users.
/etc/security/audit/config
Contains audit configuration information.
/etc/security/lastlog
Contains the last login attributes of users.
/etc/group
Contains the basic attributes of groups.
/etc/security/group
Contains the extended attributes of groups.

39