HP MC /ServicesGuaid A11.16版本安装手册2

jeffreyli

A.系统级别的MC配置
A-1: 指定群集节点和生成群集配置模版文件并改动模版文件
# cmquerycl –v –C /etc/cmcluster/cmclconf.ascii –n  hp1–n hp2
注意:有时候系统的CLUSTER里面主机不止两个，要在-n跟上各个主机的名字.
两个主机版本不同，密码不同有时候会有问题
生成文件后,用vi改动,粽色表示需要人工干预的参数
#vi /etc/cmcluster/cmclconf.ascii
脚本
# *************************************************************************************
# ********* HIGH AVAILABILITY CLUSTER CONFIGURATION FILE         #
# ***** For complete details about cluster parameters and how to           #
# ***** set them, consult the Serviceguard manual.                       #
# ************************************************************************************ #

# Enter a name for this cluster.  This name will be used to identify the
# cluster when viewing or manipulating it.

CLUSTER_NAME            cluster1  (集群名字)


# Cluster Lock Parameters
# The cluster lock is used as a tie-breaker for situations
# in which a running cluster fails, and then two equal-sized
# sub-clusters are both trying to form a new cluster.  The
# cluster lock may be configured using only one of the
# following alternatives on a cluster:
#          the LVM lock disk
#          the quorom server
#
#
# Consider the following when configuring a cluster.
# For a two-node cluster, you must use a cluster lock.  For
# a cluster of three or four nodes, a cluster lock is strongly
# recommended.  For a cluster of more than four nodes, a
# cluster lock is recommended.  If you decide to configure
# a lock for a cluster of more than four nodes, it must be
# a quorum server.

# Lock Disk Parameters.  Use the FIRST_CLUSTER_LOCK_VG and
# FIRST_CLUSTER_LOCK_PV parameters to define a lock disk.
# The FIRST_CLUSTER_LOCK_VG is the LVM volume group that
# holds the cluster lock. This volume group should not be
# used by any other cluster as a cluster lock device.

# Quorum Server Parameters. Use the QS_HOST, QS_POLLING_INTERVAL,
# and QS_TIMEOUT_EXTENSION parameters to define a quorum server.
# The QS_HOST is the host name or IP address of the system
# that is running the quorum server process.  The
# QS_POLLING_INTERVAL (microseconds) is the interval at which
# Serviceguard checks to make sure the quorum server is running.
# The optional QS_TIMEOUT_EXTENSION (microseconds) is used to increase
# the time interval after which the quorum server is marked DOWN.
#
# The default quorum server timeout is calculated from the
# Serviceguard cluster parameters, including NODE_TIMEOUT and
# HEARTBEAT_INTERVAL.  If you are experiencing quorum server
# timeouts, you can adjust these parameters, or you can include
# the QS_TIMEOUT_EXTENSION parameter.
#
# The value of QS_TIMEOUT_EXTENSION will directly effect the amount
# of time it takes for cluster reformation in the event of failure.
# For example, if QS_TIMEOUT_EXTENSION is set to 10 seconds, the cluster
# reformation will take 10 seconds longer than if the QS_TIMEOUT_EXTENSION
# was set to 0. This delay applies even if there is no delay in
# contacting the Quorum Server.  The recommended value for
# QS_TIMEOUT_EXTENSION is 0, which is used as the default
# and the maximum supported value is 30000000 (5 minutes).
#
# For example, to configure a quorum server running on node
# "qshost" with 120 seconds for the QS_POLLING_INTERVAL and to
# add 2 seconds to the system assigned value for the quorum server
# timeout, enter:
#
# QS_HOST qshost
# QS_POLLING_INTERVAL 120000000
# QS_TIMEOUT_EXTENSION 2000000

FIRST_CLUSTER_LOCK_VG           /dev/vglock（锁盘VG）


# Definition of nodes in the cluster.
# Repeat node definitions as necessary for additional nodes.
# NODE_NAME is the specified nodename in the cluster.
# It must match the hostname and both cannot contain full domain name.
# Each NETWORK_INTERFACE, if configured with IPv4 address,
# must have ONLY one IPv4 address entry with it which could
# be either HEARTBEAT_IP or STATIONARY_IP.
# Each NETWORK_INTERFACE, if configured with IPv6 address(es)
# can have multiple IPv6 address entries(up to a maximum of 2,
# only one IPv6 address entry belonging to site-local scope
# and only one belonging to global scope) which must be all
# STATIONARY_IP. They cannot be HEARTBEAT_IP.


NODE_NAME               hp1 （1号机名字）
  NETWORK_INTERFACE   lan0  （心跳网卡）
    HEARTBEAT_IP        192.168.0.1（心跳IP地址，请注意，请改成HEARTBEAT_IP）
  NETWORK_INTERFACE   lan2   （业务网卡）
    HEARTBEAT_IP        10.157.166.1（1号机业务用IP地址）
  NETWORK_INTERFACE   lan3（不需要配置）
  FIRST_CLUSTER_LOCK_PV /dev/dsk/c8t0d0 （LOCK VG 物理地址）
# List of serial device file names
# For example:
# SERIAL_DEVICE_FILE    /dev/tty0p0

# Warning: There are no standby network interfaces for lan0.
# Possible standby Network Interfaces for lan2: lan3.

NODE_NAME              hp1 （2号机名字）
  NETWORK_INTERFACE  lan0  （心跳网卡）  
    HEARTBEAT_IP        192.168.0.2  （心跳IP地址，请注意，请改成HEARTBEAT_IP）
  NETWORK_INTERFACE   lan2   （业务网卡）
    HEARTBEAT_IP        10.157.166.2 （1号机业务用IP地址）
  NETWORK_INTERFACE   lan3（不需要配置）
  FIRST_CLUSTER_LOCK_PV /dev/dsk/c8t0d0  （LOCK VG 物理地址）
#注意:物理路径要符合,不要把vgdb和vglock两个vg的物理地址混淆
# List of serial device file names
# For example:
# SERIAL_DEVICE_FILE    /dev/tty0p0

# Warning: There are no standby network interfaces for lan0.
# Possible standby Network Interfaces for lan2: lan3.


# Cluster Timing Parameters (microseconds).

# The NODE_TIMEOUT parameter defaults to 2000000 (2 seconds).
# This default setting yields the fastest cluster reformations.
# However, the use of the default value increases the potential
# for spurious reformations due to momentary system hangs or
# network load spikes.
# For a significant portion of installations, a setting of
# 5000000 to 8000000 (5 to 8 seconds) is more appropriate.
# The maximum value recommended for NODE_TIMEOUT is 30000000
# (30 seconds).

HEARTBEAT_INTERVAL              1000000
NODE_TIMEOUT                     2000000
#注意:节点轮询时间和超时设置,一般不动,毫秒为单位

# Configuration/Reconfiguration Timing Parameters (microseconds).

AUTO_START_TIMEOUT      600000000
NETWORK_POLLING_INTERVAL        2000000
#注意:网络启动时间,失败时候的顺序,一般不动, 毫秒为单位
# Network Monitor Configuration Parameters.
# The NETWORK_FAILURE_DETECTION parameter determines how LAN card failures are d
etected.
# If set to INONLY_OR_INOUT, a LAN card will be considered down when its inbound
# message count stops increasing or when both inbound and outbound
# message counts stop increasing.
# If set to INOUT, both the inbound and outbound message counts must
# stop increasing before the card is considered down.
NETWORK_FAILURE_DETECTION               INOUT

# Package Configuration Parameters.
# Enter the maximum number of packages which will be configured in the cluster.
# You can not add packages beyond this limit.
# This parameter is required.
MAX_CONFIGURED_PACKAGES         3
注意:MC里面需要预留几个程序包,有的环境是2个,3个,多个程序包多会耗费一定的内存
  如果程序包只预留了一个,以后要加程序包,这个参数不可逆,所以要重新做MC生成模版
# Access Control Policy Parameters.
#
# Three entries set the access control policy for the cluster:
# First line must be USER_NAME, second USER_HOST, and third USER_ROLE.
# Enter a value after each.
#
# 1. USER_NAME can either be ANY_USER, or a maximum of
#    8 login names from the /etc/passwd file on user host.
# 2. USER_HOST is where the user can issue Serviceguard commands.
#    If using Serviceguard Manager, it is the COM server.
#    Choose one of these three values: ANY_SERVICEGUARD_NODE, or
#    (any) CLUSTER_MEMBER_NODE, or a specific node. For node,
#    use the official hostname from domain name server, and not
#    an IP addresses or fully qualified name.
# 3. USER_ROLE must be one of these three values:
#    * MONITOR: read-only capabilities for the cluster and packages
#    * PACKAGE_ADMIN: MONITOR, plus administrative commands for packages
#      in the cluster
#    * FULL_ADMIN: MONITOR and PACKAGE_ADMIN plus the administrative
#      commands for the cluster.
#
# Access control policy does not set a role for configuration
# capability. To configure, a user must log on to one of the
# cluster's nodes as root (UID=0). Access control
# policy cannot limit root users' access.
#
# MONITOR and FULL_ADMIN can only be set in the cluster configuration file,
# and they apply to the entire cluster. PACKAGE_ADMIN can be set in the
# cluster or a package configuration file. If set in the cluster
# configuration file, PACKAGE_ADMIN applies to all configured packages.
# If set in a package configuration file, PACKAGE_ADMIN applies to that
# package only.
#
# Conflicting or redundant policies will cause an error while applying
# the configuration, and stop the process. The maximum number of access
# policies that can be configured in the cluster is 200.
#
# Example: to configure a role for user john from node noir to
# administer a cluster and all its packages, enter:
# USER_NAME  john
# USER_HOST  noir
# USER_ROLE  FULL_ADMIN


# List of cluster aware LVM Volume Groups. These volume groups will
# be used by package applications via the vgchange -a e command.
# Neither CVM or VxVM Disk Groups should be used here.
# For example:
# VOLUME_GROUP          /dev/vgdatabase
# VOLUME_GROUP          /dev/vg02

VOLUME_GROUP            /dev/vglock    与集群有关的VG请全部列出
VOLUME_GROUP            /dev/vgdata1
VOLUME_GROUP            /dev/vgdata2

1-2: 验证群集配置
  # cmcheckconf –k –v –C /etc/cmcluster/cmclconf.ascii
如果没有报错信息，显示完成信息，即表示通过。有的时候有一些有关CDROM的小警告,但是只要系统建议你可以做下一步,只要提示是complete就OK
1-3:在节点间分发配置文件
  # vgchange –a y /dev/vglock
（在HP1号机上激活VGLOCK，请检查一下HP2号机上VG的激活情况）。
请不要激活所有与数据VG相关的VG 只激活VGLOCK
因为分发是正式的要发二进制的控制文件,一定要提前激活vglock的属性,否则以后MC启动有小问题
  # cmapplyconf –k –v –C /etc/cmcluster/cmclconf.ascii
注意：设置自动启动参数
编辑文件/etc/rc.config.d/cmcluster，将参数AUTOSTART_CMCLD设为1，则在系统自举时自动启动CLUSTER。我们一般不自动启动群集，请将其设置为0，或者跳过这一步}
#vgchange –a n /dev/vglock

运行 群集
Cmruncl –v
查看群集
Cmviewcl –v


本文来自ChinaUnix博客，如果查看原文请点：http://blog.chinaunix.net/u/4925/showart_393779.html