HP MC ServicesGuaid A11.16版本安裝手冊(cè).doc

HP MC /ServicesGuaid A11.16版本安裝手冊(cè)文檔版本 v1.4作者：*HP的MC軟件是一個(gè)使用的比較廣泛的CLUSTER成熟版本，以LICENSE核算，IBM的最高，下來(lái)就是HP的MC，但是下來(lái)的SUN的CLUSTER數(shù)量只相當(dāng)于HP的七分之一。做雙機(jī)熱備的時(shí)候需要提前準(zhǔn)備：準(zhǔn)備工作A-1：編輯/.rhosts ,MC/ServiceGuard將使用/.rhosts 文件驗(yàn)證2機(jī)之間的信任關(guān)系。A-1-1命令 vi /.rhosts （oracle 用戶需在安裝oracle后 加入）示列：hp1 roothp2 root驗(yàn)證雙方關(guān)系是否成立在HP1號(hào)機(jī)上 rlogin hp2A-1-2 分發(fā) /.rhosts到所有群集結(jié)點(diǎn)rcp /.rhosts hp2:/.rhostsA-2 在所有節(jié)點(diǎn)上編輯 /etc/nsswitch.conf 文件，確保有下面一行.A-2-1命令 vi /etc/nsswitch.confhosts: files NOTFOUND=continue dnsA-2-2分發(fā) /etc/nsswitch.conf 到所有群集節(jié)點(diǎn)rcp /etc/nsswitch.conf hp2 /etc/nsswitch.confA-3在所有節(jié)點(diǎn)上編輯 /etc/hosts 文件，解析所有節(jié)點(diǎn)的IP和name.A-3-1命令 vi /etc/hosts注意：在安騰的操作系統(tǒng)，要非常規(guī)范的寫hosts文件，（主機(jī)的IP地址,主機(jī)名）10001 hp110002 hp2 （注意：本處建議不要將心跳地址、浮動(dòng)IP地址寫入）2：在HP主機(jī)上安裝MC的步驟首先，必須根據(jù)HP對(duì)所安裝的軟件提供的License(CustomerIdentifier)在上申請(qǐng)?jiān)撥浖腃odeword。然后，將光盤(光盤的驅(qū)動(dòng)是/dev/dsk/c3t2d0)放入驅(qū)動(dòng)器中，MOUNT以后，在超級(jí)用戶提示符下執(zhí)行#swinstalls/dev/dsk/c3t2d0(如果未建立CD-ROM文件系統(tǒng)則 mkdir /cdromIoscan funCdiskIssf -e找到對(duì)應(yīng)硬件路徑Mount /dev/dsk/c3t2d0 /cdrom (假設(shè)當(dāng)前為c3t2d0)用ls 命令查看CDROM里面的文件cd cdromls進(jìn)入交互式界面后，先加Codeword，才能在列表見(jiàn)到需安裝的軟件。最后，按其提示完成該軟件的安裝。需要注意，兩臺(tái)機(jī)器需要不同的密碼。（MC的補(bǔ)丁請(qǐng)根據(jù)機(jī)型及HP-UX OS的版本進(jìn)行選擇）3：網(wǎng)絡(luò)準(zhǔn)備 關(guān)于網(wǎng)絡(luò)的準(zhǔn)備，一定要仔細(xì)，有圖紙，IP規(guī)劃，對(duì)應(yīng)的機(jī)器主板結(jié)構(gòu)示意圖，如果網(wǎng)絡(luò)有蹊蹺，最好不要做MC。IP的網(wǎng)段要隔絕好，不要出現(xiàn)局域網(wǎng)有重名的IP地址。推薦使用HP的三大底層法寶命令#lanscan看主機(jī)的底層物理狀況，是否UP,（注意這個(gè)命令無(wú)法看到IP層）#netstatin看IP地址綁定是否正確#nslookuphp1看自己可不可以解析自己在配置機(jī)上的操作1、 在HP1（配置機(jī)）創(chuàng)建卷組、縮盤2、強(qiáng)調(diào)：做這個(gè)前要先復(fù)制/etc/lvmtab文件，cp/etc/lvmtab/etc/lvmtab.old在HP2（非配置機(jī)）上一樣先備份 lvmtab fstab請(qǐng)注意：在存儲(chǔ)上的共享卷組是不需要加入到fstab。如果ORALCE建立在數(shù)據(jù)庫(kù)服務(wù)器上的，其/oracle . /backup(如果有)應(yīng)該在fstab。A：在主機(jī)hp1上創(chuàng)建卷組vgdata 和vglock# mkdir /dev/vglock# mkdir /dev/vgdata1# mkdir /dev/vgdata2# ls -l /dev/*/group ( 查看group文件 確定使用0x010000中的X數(shù)值)#mknod /dev/vglock/group c640x0A0000#mknod /dev/vgdata/group c640x0B0000#mknod /dev/vgdata/group c640x0C00002、格式化硬盤：#pvcreate /dev/rdsk/c5t0d0 創(chuàng)建VG #vgcreate /dev/vglock /dev/dsk/c5t0d0 #vgcreate e 65534 s 16 /dev/vgdata /dev/dsk/c5t0d1#vgcreate e 65534 s 16 /dev/vgdata2 /dev/dsk/c5t1d13、在主機(jī)hnyb01上執(zhí)行，創(chuàng)建邏輯卷。(如數(shù)據(jù)庫(kù)建立在裸設(shè)備則不需要)#對(duì)于VGLOCK卷組來(lái)說(shuō)，我們一般不建議在VGLOCK 鎖盤上劃分卷組#lvcreateL300000noradata1 s 16/dev/vgdata1（劃分名字問(wèn)oradata1大小為300000MB，屬于VGDATA1的卷）#lvcreateL300000noradata2 s 16/dev/vgdata2（劃分名字問(wèn)oradata2,大小為300000MB，屬于VGDATA2的卷）4、創(chuàng)建文件系統(tǒng) (如數(shù)據(jù)庫(kù)建立在裸設(shè)備則不需要)#newfsFvxfs o largefiles /dev/vgdata1/roradata(如果系統(tǒng)有超過(guò)2GB的文件 需要加-o的參數(shù)，一般用于裝ORACLE數(shù)據(jù)的卷 才加本參數(shù))請(qǐng)注意 newfs命令一般用于RAW設(shè)備，請(qǐng)?jiān)谇懊婕觬#newfsFvxfs/dev/vgdata2/roralog15、掛載文件系統(tǒng)到目錄(如數(shù)據(jù)庫(kù)建立在裸設(shè)備則不需要)# cd/#mkdir /oradata#mkdir /oralog1# mount /dev/vgdata1/oradata /oradata# mount /dev/vgdata2/oralog1 /oralog1自動(dòng)MOUNT 文件目錄# vi /etc/fstab 加入磁陣上所劃的卷# mount a 掛起所有/etc/fstab 下的所有卷# mount v 顯示所有的已經(jīng)mount上的設(shè)備（或者用bdf查看）6、關(guān)閉vg屬性（請(qǐng)關(guān)閉所有除開與VG00相關(guān)的卷組）在hp1上去激活卷組：# umount /oradata# umount /oralog1# vgchange -a n /dev/vglock# vgchange -a n /dev/vgdata1# vgchange -a n /dev/vgdata27、將主機(jī)hp1號(hào)的vg信息導(dǎo)出#vgexportpsm/tmp/vgdata.map /dev/vgdata1#vgexportpsm/tmp/vglock.map /dev/vgdata2#vgexportpsm/tmp/vglock.map /dev/vglock8、在HP1（配置機(jī)）上將VG信息文件復(fù)制到HP2（非配置機(jī)）上在hp1號(hào)機(jī)將文件復(fù)制到hp2上：#rcp/tmp/vgdata1.map hnyb01:/tmp/vgdata1.map#rcp/tmp/vglock.map hnyb01:/tmp/vglock.map#rcp/tmp/vgdata2.map hnyb01:/tmp/vgdata2.map在非配置機(jī)上的操作9、在HP2（非配置機(jī)）建立文件目錄在主機(jī)hp2上創(chuàng)建group文件# mkdir /dev/vglock# mkdir /dev/vgdata1# mkdir /dev/vgdata2# ls /dev/*/group ( 查看group文件 確定使用0x0F0000中的X數(shù)值)#mknod/dev/vglock/groupc640x010000#mknod/dev/vgdata1/group c640x020000#mknod/dev/vgdata2/group c640x020000這兩個(gè)命令使用的0x0A0000，0x0B0000一定要和主機(jī)hny01要嚴(yán)格符合，否則會(huì)有錯(cuò)誤。10、在HP2（非配置機(jī)）上將VG信息導(dǎo)入將映射文件導(dǎo)入卷組數(shù)據(jù)，在HP2上輸入：#vgimports -vm/tmp/vgdata1.map /dev/vgdata1#vgimportsv -m/tmp/vglock.map /dev/vglock#vgimports -vm/tmp/vgdata2.map /dev/vgdata2注意：hp2上的cXtYdz可能會(huì)和hp1上的不同，檢查一下，確保整個(gè)集群中physical volume names是正確的。例如：#vgimports v -m /tmp/vgdata.map /dev/vgdata /dev/dsk/c1t2d0 (假設(shè)vgdata在磁陣上對(duì)應(yīng)的PV名c1t2d0）請(qǐng)注意：本處可能也不需要本步11、在HP2（非配置機(jī)）上將VG激活（請(qǐng)不要激活除開鎖磁盤以外的數(shù)據(jù)VG）# vgchange -a y /dev/vglock12、在HP2（非配置機(jī)）上建立mount點(diǎn)、文件系統(tǒng)等創(chuàng)建mount目錄點(diǎn)# mkdir /oradata# mkdir /oralog1Mount文件系統(tǒng)以檢查正確性# mount /dev/vgdata1/oradata /oradata # mount /dev/vgdata2/oralog1 /oralog1# mount a 掛起所有/etc/fstab 下的所有卷# mount v 顯示所有的已經(jīng)mount上的設(shè)備（或者用bdf查看）13、備份VG信息（可選擇不要）# vgcfgbackup /dev/vgdata1# vgcfgbackup /dev/vglock# vgcfgbackup /dev/vgdata214、UMOUNT文件系統(tǒng)# umount /oradata# umount /oralog1=下面紅色標(biāo)記的不是太安全=15、改變VG的控制屬性（鎖磁盤不加了）#chmod 777 /dev/vgdata1#chmod 777 /dev/vgdata217、改變卷組的控制屬性（數(shù)據(jù)lv）chmod 660 /dev/vgdata1/roradatachmod 660 /dev/vgdata2/roralog1可以參見(jiàn)實(shí)際系統(tǒng)：18、改變卷組的用戶使用者（一般在ORACLE安裝完畢后使用，目前不用）chown oracle:oracle /dev/vgdata1/roradatachown oracle:oracle /dev/vgdata2/roralog119、對(duì)卷組屬性的更改編輯/etc/lvmrc文件，保證在系統(tǒng)啟動(dòng)時(shí)不自動(dòng)激活與CLUSTER有關(guān)的卷組（將AUTO_VG_ACTIVATE置為0，并確認(rèn)root卷組包含在custom_vg_activation函數(shù)內(nèi)。實(shí)際上，Vg00自動(dòng)處于激活狀態(tài)），這些卷組將在應(yīng)用包的control.sh腳本中激活。實(shí)際上只需要更改AUTO_VG_ACTIVATE=020、在HP1上去激活所有卷組（請(qǐng)關(guān)閉所有除開VG00以外的VG）# vgchange -a n /dev/vglock# vgchange -a n /dev/vgdata1# vgchange -a n /dev/vgdata2到這里，我們所有的準(zhǔn)備工作已經(jīng)做完了；開始正式配置MC。請(qǐng)保證2套機(jī)器上的VGDATA VGLOCK都處于非激活狀態(tài)。A.系統(tǒng)級(jí)別的MC配置A-1:指定群集節(jié)點(diǎn)和生成群集配置模版文件并改動(dòng)模版文件#cmqueryclvC/etc/cmcluster/cmclconf.asciinhp1nhp2注意:有時(shí)候系統(tǒng)的CLUSTER里面主機(jī)不止兩個(gè)，要在-n跟上各個(gè)主機(jī)的名字.兩個(gè)主機(jī)版本不同，密碼不同有時(shí)候會(huì)有問(wèn)題生成文件后,用vi改動(dòng),粽色表示需要人工干預(yù)的參數(shù)#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 2000000FIRST_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號(hào)機(jī)名字） NETWORK_INTERFACE lan0 （心跳網(wǎng)卡） HEARTBEAT_IP （心跳IP地址，請(qǐng)注意，請(qǐng)改成HEARTBEAT_IP） NETWORK_INTERFACE lan2 （業(yè)務(wù)網(wǎng)卡） HEARTBEAT_IP （1號(hào)機(jī)業(yè)務(wù)用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 hp2 （2號(hào)機(jī)名字） NETWORK_INTERFACE lan0 （心跳網(wǎng)卡） HEARTBEAT_IP （心跳IP地址，請(qǐng)注意，請(qǐng)改成HEARTBEAT_IP） NETWORK_INTERFACE lan2 （業(yè)務(wù)網(wǎng)卡） HEARTBEAT_IP （1號(hào)機(jī)業(yè)務(wù)用IP地址） NETWORK_INTERFACE lan3（不需要配置） FIRST_CLUSTER_LOCK_PV /dev/dsk/c8t0d0 （LOCK VG 物理地址）#注意:物理路徑要符合,不要把vgdb和vglock兩個(gè)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 1000000NODE_TIMEOUT 2000000#注意:節(jié)點(diǎn)輪詢時(shí)間和超時(shí)設(shè)置,一般不動(dòng),毫秒為單位# Configuration/Reconfiguration Timing Parameters (microseconds).AUTO_START_TIMEOUT 600000000NETWORK_POLLING_INTERVAL 2000000#注意:網(wǎng)絡(luò)啟動(dòng)時(shí)間,失敗時(shí)候的順序,一般不動(dòng),毫秒為單位# Network Monitor Configuration Parameters.# The NETWORK_FAILURE_DETECTION parameter determines how LAN card failures are detected.# 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里面需要預(yù)留幾個(gè)程序包,有的環(huán)境是2個(gè),3個(gè),多個(gè)程序包多會(huì)耗費(fèi)一定的內(nèi)存如果程序包只預(yù)留了一個(gè),以后要加程序包,這個(gè)參數(shù)不可逆,所以要重新做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# clusters 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/vg02VOLUME_GROUP /dev/vglock 與集群有關(guān)的VG請(qǐng)全部列出VOLUME_GROUP /dev/vgdata1VOLUME_GROUP /dev/vgdata21-2:驗(yàn)正群集配置#cmcheckconfkvC/etc/cmcluster/cmclconf.ascii如果沒(méi)有報(bào)錯(cuò)信息，顯示完成信息，即表示通過(guò)。有的時(shí)候有一些有關(guān)CDROM的小警告,但是只要系統(tǒng)建議你可以做下一步,只要提示是complete就OK1-3:在節(jié)點(diǎn)間分發(fā)配置文件#vgchangeay/dev/vglock（在HP1號(hào)機(jī)上激活VGLOCK，請(qǐng)檢查一下HP2號(hào)機(jī)上VG的激活情況）。請(qǐng)不要激活所有與數(shù)據(jù)VG相關(guān)的VG 只激活VGLOCK因?yàn)榉职l(fā)是正式的要發(fā)二進(jìn)制的控制文件,一定要提前激活vglock的屬性,否則以后MC啟動(dòng)有小問(wèn)題#cmapplyconfkvC/etc/cmcluster/cmclconf.ascii注意：設(shè)置自動(dòng)啟動(dòng)參數(shù)編輯文件/etc/rc.config.d/cmcluster，將參數(shù)AUTOSTART_CMCLD設(shè)為1，則在系統(tǒng)自舉時(shí)自動(dòng)啟動(dòng)CLUSTER。我們一般不自動(dòng)啟動(dòng)群集，請(qǐng)將其設(shè)置為0，或者跳過(guò)這一步#vgchange a n /dev/vglock運(yùn)行 群集Cmruncl v查看群集Cmviewcl v B、應(yīng)用級(jí)別的ORACLE程序包配置B-1:創(chuàng)建程序包配置模板,編輯這些模板文件，以指定程序包名稱、按優(yōu)先級(jí)排序的節(jié)點(diǎn)列表、控制腳本的位置以及各個(gè)程序包的故障切換參數(shù)。#mkdir/dev/cmcluster/pkg1#cmmakepkgp/etc/cmcluster/pkg1/pkg1.conf#vi/etc/cmcluser/pkg1/pkg1.conf腳本# * *# * HIGH AVAILABILITY PACKAGE CONFIGURATION FILE (template)# * *# * Note: This file MUST be edited before it can be used. # * For complete details about package parameters and how to set them, *# * consult the Serviceguard Extension for RAC manuals.# *# Enter a name for this package. This name will be used to identify the# package when viewing or manipulating it. It must be different from# the other configured package names.PACKAGE_NAME pkg1 （程序包的名字）# Enter the package type for this package. PACKAGE_TYPE indicates# whether this package is to run as a FAILOVER or SYSTEM_MULTI_NODE# package.# FAILOVER package runs on one node at a time and if a failure# occurs it can switch to an alternate node.# SYSTEM_MULTI_NODE# package runs on multiple nodes at the same time.# It can not be started and halted on individual nodes.# Both NODE_FAIL_FAST_ENABLED and AUTO_RUN must be set# to YES for this type of package. All SERVICES must# have SERVICE_FAIL_FAST_ENABLED set to YES.# NOTE: Packages which have a PACKAGE_TYPE of SYSTEM_MULTI_NODE are# not failover packages and should only be used for applications# provided by Hewlett-Packard.# Since SYSTEM_MULTI_NODE packages run on multiple nodes at# one time, following parameters are ignored:# FAILOVER_POLICY# FAILBACK_POLICY# Since an IP address can not be assigned to more than node at a# time, relocatable IP addresses can not be assigned in the# package control script for multiple node packages. If# volume groups are assigned to multiple node packages they must# activated in a shared mode and data integrity is left to the# application. Shared access requires a shared volume manager.# Examples : PACKAGE_TYPE FAILOVER (default)# PACKAGE_TYPE SYSTEM_MULTI_NODE#PACKAGE_TYPE FAILOVER（默認(rèn)數(shù)值，不需更改）# Enter the failover policy for this package. This policy will be used# to selec