Filter
Top Products
82 IBM Certification Study Guide AIX HACMP
3.4.1 Creating Shared VGs
The following sections contain information about creating non-concurrent
VGs and VGs for concurrent access.
3.4.1.1 Creating Non-Concurrent VGs
This section covers how to create a shared volume group on the source node
using the SMIT interface. Use the
smit mkvg fastpath to create a shared
volume group. Use the default field values unless your site has other
requirements, or unless you are specifically instructed otherwise here.
Table 13. smit mkvg Options (Non-Concurrent)
3.4.1.2 Creating VGs for Concurrent Access
The procedure used to create a concurrent access volume group varies
depending on which type of device you are using: serial disk subsystem
(7133) or RAID disk subsystem (7135).
Options Description
VOLUME GROUP name The name of the shared volume group should be
unique within the cluster.
Activate volume group
AUTOMATICALLY at system
restart?
Set to no so that the volume group can be
activated as appropriate by the cluster event
scripts.
ACTIVATE volume group after it
is created?
Set to yes
.
Volume Group MAJOR
NUMBER
If you are not using NFS, you can use the default
(which is the next available number in the valid
range). If you are using NFS, you must make sure
to use the same major number on all nodes. Use
the lvlstmajor command on each node to
determine a free major number common to all
nodes.
If you are creating (or plan to create) concurrent volume groups on SSA
devices, be sure to assign unique non-zero node numbers through the
SSAR on each cluster node. If you plan to specify SSA disk fencing in your
concurrent resource group, the node numbers are assigned when you
synchronize resources. If you do not specify SSA disk fencing, assign node
numbers using the following command:
chdev -l ssar -a node_number=x,
where x is the number to assign to that node. You must reboot the system
to effect the change.
Note