a. Select:
Physical & Logical Storage → Logical Volume Manager → Logical Volumes → Add a Logical Volume
b. Enter a volume group name, for example, sapr3vg.
c. Enter a logical volume name, for example, lvsap01.
d. Enter the number of logical partitions (see section Size of a Logical Partition).
e. Press F3 until the Physical & Logical Storage menu appears.
2. Create the file systems.
a. Select:
Physical & Logical Storage → File Systems → Add/Change/Show/Delete File Systems → Journaled File Systems →
Add a Journaled File System on a previously defined Logical Volume
b. Press F4 to get a list of logical volumes.
c. Select one logical volume.
Select the logical volume with the desired size.
Enter mount point as given in the file system list files.
DB2 UDB for UNIX and Windows: /db2/<SAPSDID>
Informix: /informix/<SAPSID>
Oracle: /oracle/<SAPSID>/sapdata1
SAP DB: /sapdb/<SAPSID>/sapdata
Set mount automatically to yes.
d. Press F10 to exit smitty.
Cluster Topology Configuration:
NOTE: Underscore ( _ ) is the only valid special character for HACMP objects names
First character must not be numeric.
From one node, you will execute the following steps
# smit hacmp
Extended Configuration → Extended Topology Configuration → Configure Cluster → Configure Nodes → Configure IP Networks
- Configure Communication Interfaces on these IP networks
- Configure non-IP Networks (serial rs232 or disk heartbeat)
- Define Communication Devices on these non-IP networks
- Configure persistent IP addresses for network(s) with boot or service
- Synchronize configuration. It will also setup persistent IP aliases.
eg.
Configure HACMP Networks
Move cursor to desired item and press Enter.
Add a Network to the HACMP Cluster
Change/Show a Network in the HACMP Cluster
Remove a Network from the HACMP Cluster
+----------------------------------------------------------------------
| Select a Network to Change/Show
|
| Move cursor to desired item and press Enter.
|
| net_ether_01 (10.0.51.0/24 172.16.1.0/24 172.17.1.0/24)
| net_rs232_01
Change/Show an IP-Based Network in the HACMP Cluster
Type or select values in entry fields.
Press Enter AFTER making all desired changes.
[Entry Fields]
* Network Name net_ether_01
New Network Name []
* Network Type [ether] +
* Netmask [255.255.255.0] +
* Enable IP Address Takeover via IP Aliases [Yes] +
IP Address Offset for Heartbeating over IP Aliases []
* Network attribute public +
Change/Show a Serial Network in the HACMP Cluster
Type or select values in entry fields.
Press Enter AFTER making all desired changes.
[Entry Fields]
* Network Name net_rs232_01
New Network Name []
* Network Type [rs232] +
Configure HACMP Communication Interfaces/Devices
Mo+--------------------------------------------------------------------------+
| Select a Communication Interface/Device to Change/Show |
| |
| Move cursor to desired item and press Enter. Use arrow keys to scroll. |
| |
| [TOP] |
| # Node / Network |
| # Interface/Device IP Label/Device Path IP Address |
| |
| |
| # RACNODE1 / net_ether_01 |
| en0 ibmcl01_boot 172.16.1.1 |
| en2 ibmcl01_stby 172.17.1.1 |
| |
| # RACNODE1 / net_rs232_01 |
| tty0 RACNODE1_tty0_01 /dev/tty0 |
| |
| |
| # RACNODE2 / net_ether_01 |
| en0 ibmcl02_boot 172.16.1.1 |
| en2 ibmcl02_stby 172.17.1.1 |
| |
| # RACNODE2 / net_rs232_01 |
| tty0 RACNODE2_tty0_01 /dev/tty0 |
| [BOTTOM] |
1) Nodes prerequisites
Network configuration on EACH node interfaces on their “boot” and “standby” address, each one on a different subnet hostname corresponding to future “persistent” address:
# smit mkhostname
- /etc/hosts must contain all nodes addresses, persistent and application IP aliases.
- /.rhosts should be empty, except for Bull ClusterWatch (corrected in future PTF).
- on each node file /usr/es/sbin/cluster/etc/rhosts must contain all the “boot” addresses of all nodes and all HACMP networks, for example:
clusnod1_boot1
clusnod2_boot1
Check also that the following daemon is running :
# lssrc –g clcomdES
clcomdES clcomdES 13350 active
otherwise start it with startsrsc –s clcomdES
- godm TCP/IP service must be active ( refresh –s inetd on all nodes)
- Volume Groups imported on all nodes, not automatically activable at boot time,
If AIX 5.2, they must be concurrent capable (bos.clvm.enh fileset installed)
Remove Installed Software
Ty+--------------------------------------------------------------------------+
Pr| SOFTWARE name |
| |
| Move cursor to desired item and press Esc+7. |
* | ONE OR MORE items can be selected. |
| Press Enter AFTER making all selections. |
| |
| [MORE...580] |
| rpm.rte |
| > rsct.basic.hacmp |
| > rsct.basic.rte |
| > rsct.compat.basic.hacmp |
| > rsct.compat.basic.rte |
| > rsct.compat.clients.hacmp |
| > rsct.compat.clients.rte |
| > rsct.core.auditrm |
| > rsct.core.errm |
| > rsct.core.fsrm |
| > rsct.core.gui |
| > rsct.core.hostrm |
| > rsct.core.lprm |
| > rsct.core.rmc |
| > rsct.core.sec |
| > rsct.core.sensorrm |
| > rsct.core.sr |
| > rsct.core.utils |
| > rsct.msg.EN_US.core.auditrm |
| > rsct.msg.EN_US.core.errm |
| > rsct.msg.EN_US.core.fsrm |
| > rsct.msg.EN_US.core.gui |
| > rsct.msg.EN_US.core.hostrm |
| > rsct.msg.EN_US.core.lprm |
| > rsct.msg.EN_US.core.rmc |
| > rsct.msg.EN_US.core.sec |
| > rsct.msg.EN_US.core.sensorrm |
| > rsct.msg.EN_US.core.sr |
| > rsct.msg.EN_US.core.utils |
| > rsct.msg.en_US.basic.rte |
| > rsct.msg.en_US.core.auditrm |
| > rsct.msg.en_US.core.errm |
| > rsct.msg.en_US.core.fsrm |
| > rsct.msg.en_US.core.gui |
| > rsct.msg.en_US.core.gui.com |
| > rsct.msg.en_US.core.hostrm |
| > rsct.msg.en_US.core.lprm |
| > rsct.msg.en_US.core.rmc |
| > rsct.msg.en_US.core.rmc.com |
| > rsct.msg.en_US.core.sec |
| > rsct.msg.en_US.core.sensorrm |
| > rsct.msg.en_US.core.sr |
| > rsct.msg.en_US.core.utils |
| > rsct.opt.storagerm
| > cluster.adt.es.client.include |
| > cluster.adt.es.client.samples.clinfo |
| > cluster.adt.es.client.samples.clstat |
| > cluster.adt.es.client.samples.libcl |
| > cluster.adt.es.java.demo.monitor |
| > cluster.doc.en_US.es.html |
| > cluster.doc.en_US.es.pdf |
| > cluster.es.cfs.rte |
| > cluster.es.client.lib
| > cluster.es.client.rte |
| > cluster.es.client.utils |
| > cluster.es.client.wsm |
| > cluster.es.cspoc.cmds |
| > cluster.es.cspoc.dsh |
| > cluster.es.cspoc.rte |
| > cluster.es.plugins.dhcp |
| > cluster.es.plugins.dns |
| > cluster.es.plugins.printserver
| > cluster.es.server.cfgast |
| > cluster.es.server.diag |
| > cluster.es.server.events |
| > cluster.es.server.rte |
| > cluster.es.server.testtool |
| > cluster.es.server.utils |
| > cluster.es.worksheets |
| > cluster.license |
| > cluster.man.en_US.es.data
| > cluster.msg.en_US.cspoc |
| > cluster.msg.en_US.es.client |
| > cluster.msg.en_US.es.server | | | | |
Es+--------------------------------------------------------------------------+
1) Configure Cluster
# smit hacmp
Extended Configuration → Extended Topology Configuration → Configure an HACMP Cluster → Add/Change/Show an HACMP Cluster
Assign a unique Cluster Name (< 32 characters)
2) Configure Nodes
# smit hacmp
Extended Configuration → Extended Topology Configuration → Configure HACMP Nodes → Add a Node to the HACMP Cluster
Give Node Name, each node has a unique name (<32 characters)
Communication Path to Node: Press F4 and select an IP label (e.g.: boot address)
Repeat this step for all nodes.
3) Configure IP Networks
# smit hacmp
Extended Configuration → Extended Topology Configuration → Configure HACMP Networks → Add a Network to the HACMP Cluster
Go to # Pre-defined IP-based Network Types
select network type (e.g.: ether)
check that Netmask is correct
It is mandatory to modify the following field:
* Enable IP Address Takeover via IP Aliases [No]
Repeat this step for all IP networks (interconnect, administration).
Configure Communication Interfaces on these IP networks
# smit hacmp
Extended Configuration → Extended Topology Configuration → Configure HACMP Communication → Interfaces/Devices
Add Communication Interfaces/Devices
Add Pre-defined Communication Interfaces and Devices
Communication Interfaces
Select a previously defined network
give IP Label and Node Name Repeat this step for all “boot and standby” addresses of all IP networks and of all nodes. E.g.: clusnod1_boot, clusnod1_stby, clusnod2_boot, clusnod2_stby
4) Configure non-IP network (serial rs232 or disk heartbeat)
# smit hacmp
Extended Configuration → Extended Topology Configuration → Configure HACMP Networks → Add a Network to the HACMP Cluster
Go to # Pre-defined Serial Device Types
Select rs232 or diskhb
This will create a network with a default name like net_rs232_0<x>
Define Communication Devices on these non-IP networks
# smit hacmp
Extended Configuration → Extended Topology Configuration → Configure HACMP Communication Interfaces/Devices
Add Communication Interfaces/Devices
Add Pre-defined Communication Interfaces and Devices
Communication Devices
Select a Device Network then give:
Device Name: symbolic name eg. clusnod1_tty
Device Path : /dev/tty<x> or /dev/hdiskpower<x> (or /dev/hdisk<x>
disk must belong to an AIX 5.2 enhanced concurrent VG
Node Name : name of one node
Repeat this step to define the Communication Device of the other node(s) …
5) Configure persistent IP addresses for network(s) where an initial “boot” address which will be replaced by a “service” address
# smit hacmp
Extended Configuration → Extended Topology Configuration → Configure HACMP Persistent Node IP Label / Addresses
Add a Persistent Node IP Label / Address
Select a Node and give:
* Network Name [ ] Press F4
* Node IP Label / Address [ ] Should usually correspond to node hostname
or Press F4 to select from /etc/hosts
Repeat this step for the other interface(s) on other node(s) …
6) Synchronize configuration. It will also setup persistent addresses
# smit hacmp
Extended Configuration → Extended Verification and Synchronization
# netstat –i
shows persistent IP addresses on the same interfaces as boot addresses.
Cluster Resources Configuration
From one node, you will execute the following steps:
# smit hacmp
Extended Configuration → Extended Resource Configuration → Configure HACMP Service IP Labels/Addresses (srv address)
Define Application Servers
Define Resource Groups
Configure Resources for each Resource Group
Customization
Synchronize Cluster Resources
Start HACMP on nodes
1) Configure HACMP Service IP Labels/Addresses
# smit hacmp
Extended Configuration → Extended Resource Configuration → HACMP Extended Resources Configuration → Configure HACMP Service IP Labels/Addresses → Add a Service IP Label/Address
Select: Configurable on Multiple Nodes
Select a network name
Give interface service IP label or address (on the same subnet as “boot” address)
You shouldn’t specify an Alternate HW Address to accompany IP Label/Address
because AIX 5L does “gratuitous ARP” update.
Don’t specify an Alternate HW Address for Ethernet Gigabit adapters
Repeat this step for ALL service IP labels.
2) Define Application Servers
# smit hacmp
Extended Configuration → Extended Resource Configuration → HACMP Extended Resources Configuration → Configure HACMP Application Servers → Add an Application Server
Give:
- Server name (symbolic name for the resource)
- Start and Stop scripts full pathnames (must exist on ALL NODES, in non-shared
filesystems).
Repeat this step for ALL Application Servers.
3) Define Resource Groups
# smit hacmp
Extended Configuration → Extended Resource Configuration → HACMP Extended Resource Group Configuration → Add a Resource Group
Select the Resource Group Management Policy: cascading, rotating, concurrent or custom
Give Resource Group Name,
Inter-Site Management Policy (leave default ignore)
Give the list of Participating Node Names: for cascading the order defines the priority.
Repeat this step for all Resource Groups
4) Configure Resources for each Resource Group
# smit hacmp
Extended Configuration → Extended Resource Configuration → HACMP Extended Resource Group Configuration → Change/Show Resources and Attributes for a Resource Group
Select a Resource Group name
Define the resources belonging to the resource group (separated with space):
Inactive Takeover Applied (true if you want first starting node to take all resources)
Cascading Without Fallback Enabled (true to decide when fallback will occur
recommended if HACMP Cluster Services started in /etc/inittab)
Application Servers
Service IP Labels / Addresses (Give ALL Service IP labels separated by space,
in case of several networks)
Volume Groups give the name(s) separated by space
Use forced varyon of volume groups, if necessary (true for AIX mirrored VGs)
Filesystems (empty is All) leave empty
Filesystems Recovery Method leave sequential if nested recursive mount points
otherwise, parallel when many
Filesystems mounted before IP configured (TRUE for NFS (cross)-mount)
Filesystems/Directories to Export (must belong to Volume Groups listed before)
Filesystems/Directories to NFS mount (must belong to previous Export list)
Network for NFS mount
Repeat this step for all Resource Groups
Synchronize Cluster Resources (everytime you change the configuration)
# smit hacmp
Extended Configuration
Extended Verification and Synchronization
which allows to:
* Verify, Synchronize or Both [Both]
Force synchronization if verification fails? [No]
* Verify changes only? [No]
* Logging [Standard / Verbose]
In case of problem, select Verbose Logging and look to log files:
/var/hacmp/clverify/clverify.log or /var/hacmp/clverify/…
Now you can start HACMP on all nodes (several nodes at the same time)
# smit clstart
* Start now, on system restart or both now
Start Cluster Services on these nodes [clusnod1] you can specify several nodes
1. Create Volume Group
Note: the following example is using the disk c0t3d5, the volume group vg01, the logical volume lvtest, and mount point /test
1.1 Identify the disks to be used for LVM and create the missing device files
# insf -eC disk
# ioscan -nfC disk
1.2 Create a LVM data structure on each identified disk
# pvcreate /dev/rdsk/c0t3d5
Note: if the disk was previously used in another VG, use the following command instead:
# pvcreate -f /dev/rdsk/ c0t3d5
1.3 Collect all the physical volumes to form a new volume group
1.3.1 Go to dev directory (/dev)
# cd /dev
1.3.2 Create VG name
# mkdir vg01
1.3.3 Make directory and special file in VG
# mknod /dev/vg01/group c 64 0×010000
Note: the group number (last parameter – 0×010000 ) is in hexadecimal and should be different for each volume group
1.3.4 Create the volume group
# vgcreate -s [pe_size] -e [max_pe] /dev/vg01 /dev/dsk/ c0t3d5
Note: when a volume group is created without define pe_size and max_pe parameter, the maximum physical extents per volume (max_pe) will be set to the max_pe of the largest physical volume (PV). The effect of not setting the max_pe parameter would be that any PV added to the volume group in the future regardless of there size will be limited to the volume groug creation value of max_pe. Therefore, consider increasing the max_pe to accommodate PV’s that may likely be larger than the largest PV used to create the Volume Group. The formula to use to determine the value is:
physical_extent_size * max_pe = size_of_the_disk.
The "df -g" command shows it, but apparently not if you are using Veritas file-system; Veritas says they do not support "df -g"
So, instead, for VxFS on HPUX, use "/usr/sbin/fstyp -v <special>", where "<special>" is the block-special device underlying the file-system.
# /usr/sbin/fstyp -v /dev/vgfc07/asgr07
vxfs
version: 5
f_bsize: 8192
f_frsize: 2048
f_blocks: 262012928
f_bfree: 261972575
f_bavail: 253785933
f_files: 65493168
f_ffree: 65493136
f_favail: 65493136
f_fsid: 1074200577
f_basetype: vxfs
f_namemax: 254
f_magic: a501fcf5
f_featurebits: 0
f_flag: 16
f_fsindex: 9
f_size: 262012928
# df -g
/asgr01 (/dev/vgsata01/asgr01 ) :
8192 file system block size 2048 fragment size
261652480 total blocks 249918266 total free blocks
242108376 allocated free blocks 62522640 total i-nodes
62479564 total free i-nodes 62479564 allocated free i-nodes
1073807361 file system id vxfs file system type
0x10 flags 255 file system name length
/asgr01 file system specific string
/asgr02 (/dev/vgsata02/asgr02 ) :
8192 file system block size 2048 fragment size
261652480 total blocks 19914022 total free blocks
19291718 allocated free blocks 5001472 total i-nodes
4978498 total free i-nodes 4978498 allocated free i-nodes
1073938433 file system id vxfs file system type
0x10 flags 255 file system name length
/asgr02 file system specific string
/asgr03 (/dev/vgsata03/asgr03 ) :
8192 file system block size 2048 fragment size
261652480 total blocks 141523868 total free blocks
137101283 allocated free blocks 35381736 total i-nodes
35380965 total free i-nodes 35380965 allocated free i-nodes
1074003969 file system id vxfs file system type
0x10 flags 255 file system name length
/asgr03 file system specific string
/asgr04 (/dev/vgfc04/asgr04 ) :
8192 file system block size 2048 fragment size
261652480 total blocks 42816731 total free blocks
41478714 allocated free blocks 10724616 total i-nodes
10704175 total free i-nodes 10704175 allocated free i-nodes
1073872897 file system id vxfs file system type
0x10 flags 255 file system name length
/asgr04 file system specific string
/asgr05 (/dev/vgfc05/asgr05 ) :
8192 file system block size 2048 fragment size
261652480 total blocks 16433981 total free blocks
15920441 allocated free blocks 4167456 total i-nodes
4108493 total free i-nodes 4108493 allocated free i-nodes
1074069505 file system id vxfs file system type
0x10 flags 255 file system name length
/asgr05 file system specific string
/home (/dev/vg00/lvol4 ) :
8192 file system block size 8192 fragment size
2621440 total blocks 46553 total free blocks
46203 allocated free blocks 161024 total i-nodes
11632 total free i-nodes 11632 allocated free i-nodes
1073741828 file system id vxfs file system type
0x10 flags 255 file system name length
/home file system specific string
/opt (/dev/vg00/lvol5 ) :
8192 file system block size 8192 fragment size
1048576 total blocks 528936 total free blocks
524811 allocated free blocks 183744 total i-nodes
132218 total free i-nodes 132218 allocated free i-nodes
1073741829 file system id vxfs file system type
0x10 flags 255 file system name length
/opt file system specific string
/tmp (/dev/vg00/lvol6 ) :
8192 file system block size 8192 fragment size
1048576 total blocks 575647 total free blocks
571226 allocated free blocks 154048 total i-nodes
143911 total free i-nodes 143911 allocated free i-nodes
1073741830 file system id vxfs file system type
0x10 flags 255 file system name length
/tmp file system specific string
/usr (/dev/vg00/lvol7 ) :
8192 file system block size 8192 fragment size
1048576 total blocks 724647 total free blocks
718989 allocated free blocks 212064 total i-nodes
181133 total free i-nodes 181133 allocated free i-nodes
1073741831 file system id vxfs file system type
0x10 flags 255 file system name length
/usr file system specific string
/var (/dev/vg00/lvol8 ) :
8192 file system block size 8192 fragment size
1572864 total blocks 1289212 total free blocks
1279187 allocated free blocks 357184 total i-nodes
322290 total free i-nodes 322290 allocated free i-nodes
1073741832 file system id vxfs file system type
0x10 flags 255 file system name length
/var file system specific string
/stand (/dev/vg00/lvol1 ) :
8192 file system block size 8192 fragment size
262144 total blocks 244259 total free blocks
242364 allocated free blocks 61184 total i-nodes
61046 total free i-nodes 61046 allocated free i-nodes
1073741825 file system id vxfs file system type
0 flags 255 file system name length
/stand file system specific string
/ (/dev/vg00/lvol3 ) :
8192 file system block size 8192 fragment size
655360 total blocks 477420 total free blocks
473697 allocated free blocks 129920 total i-nodes
119339 total free i-nodes 119339 allocated free i-nodes
1073741827 file system id vxfs file system type
0x10 flags 255 file system name length
/ file system specific string
Prerequisites
Before you start to set up the necessary file systems , carefully plan their distribution to available disks. Decide whether one or more volume groups (VGs) should be used.
Procedure
1. Enter the command smitty.
2. Select:
Physical & Logical Storage → Logical Volume Manager →
Volume Groups → Add a Volume Group
3. Enter a volume group name, for example, sapr3vg.
Press F4 to get a list of disks, which have not yet been assigned to a volume group.
4. With F7, mark the disks you want to be included in the volume group and press ENTER.
5. Press F10 to exit.
Repeat these steps for each volume group that has to be created.
XML Feeds
Recent comments