This article will show you how to execute PowerHA daily management.
1.Display PowerHA Version
- [root@dbserv1 /]#/usr/es/sbin/cluster/cspoc/cli_on_cluster -S /usr/es/sbin/cluster/utilities/halevel -s
- dbserv1: 6.1.0 SP8
- dbserv2: 6.1.0 SP8
2.Dsiplay cluster services:
- [root@dbserv1 /]#/usr/es/sbin/cluster/utilities/clshowsrv -v
- Status of the RSCT subsystems used by HACMP:
- Subsystem Group PID Status
- topsvcs topsvcs 5832938 active
- grpsvcs grpsvcs 5636250 active
- grpglsm grpsvcs inoperative
- emsvcs emsvcs 6619156 active
- emaixos emsvcs inoperative
- ctrmc rsct 5177506 active
- Status of the HACMP subsystems:
- Subsystem Group PID Status
- clcomdES clcomdES 5505228 active
- clstrmgrES cluster 6553808 active
- Status of the optional HACMP subsystems:
- Subsystem Group PID Status
- clinfoES cluster 5767368 active
3.Display Resource Group Status:
- [root@dbserv2 /]#/usr/es/sbin/cluster/utilities/clRGinfo -m
- ---------------------------------------------------------------------------------------------------------------------
- Group Name State Application state Node
- ---------------------------------------------------------------------------------------------------------------------
- oradb ONLINE dbserv1
- example ONLINE MONITORED
4.Display Topology Configuration:
- [root@dbserv1 /]#/usr/es/sbin/cluster/utilities/cltopinfo
- Cluster Name: hatest
- Cluster Connection Authentication Mode: Standard
- Cluster Message Authentication Mode: None
- Cluster Message Encryption: None
- Use Persistent Labels for Communication: Yes
- There are 2 node(s) and 3 network(s) defined
- NODE dbserv1:
- Network net_diskhb_01
- diskhb_01 /dev/hdisk5
- Network net_ether_02
- dbserv2-serv 172.16.255.17
- dbserv1-serv 172.16.255.15
- dbserv1 172.16.255.11
- Network net_ether_03
- dbserv1-stby 192.168.0.11
- NODE dbserv2:
- Network net_diskhb_01
- diskhb_02 /dev/hdisk5
- Network net_ether_02
- dbserv2-serv 172.16.255.17
- dbserv1-serv 172.16.255.15
- dbserv2 172.16.255.13
- Network net_ether_03
- dbserv2-stby 192.168.0.13
- Resource Group oradb
- Startup Policy Online On First Available Node
- Fallover Policy Fallover To Next Priority Node In The List
- Fallback Policy Never Fallback
- Participating Nodes dbserv1 dbserv2
- Service IP Label dbserv1-serv
- Service IP Label dbserv2-serv
- Total Heartbeats Missed: 0
- Cluster Topology Start Time: 05/30/2012 14:31:17
5.Show Resource Information
- [root@dbserv1 /]#/usr/es/sbin/cluster/utilities/clshowres
- Resource Group Name oradb
- Participating Node Name(s) dbserv1 dbserv2
- Startup Policy Online On First Available Node
- Fallover Policy Fallover To Next Priority Node In The List
- Fallback Policy Never Fallback
- Site Relationship ignore
- Dynamic Node Priority
- Service IP Label dbserv1-serv dbserv2-serv
- Filesystems ALL
- Filesystems Consistency Check fsck
- Filesystems Recovery Method sequential
- Filesystems/Directories to be exported (NFSv2/NFSv3)
- Filesystems/Directories to be exported (NFSv4)
- Filesystems to be NFS mounted
- Network For NFS Mount
- Filesystem/Directory for NFSv4 Stable Storage
- Volume Groups oradata
- Concurrent Volume Groups
- Use forced varyon for volume groups, if necessary false
- Disks
- GMVG Replicated Resources
- GMD Replicated Resources
- PPRC Replicated Resources
- SVC PPRC Replicated Resources
- EMC SRDFReplicated Resources
- TRUECOPY Replicated Resources
- GENXD Replicated Resources
- Connections Services
- Fast Connect Services
- Shared Tape Resources
- Application Servers example
- Highly Available Communication Links
- Primary Workload Manager Class
- Secondary Workload Manager Class
- Delayed Fallback Timer
- Miscellaneous Data
- Automatically Import Volume Groups false
- Inactive Takeover
- SSA Disk Fencing false
- Filesystems mounted before IP configured false
- WPAR Name
- Run Time Parameters:
- Node Name dbserv1
- Debug Level high
- Format for hacmp.out Standard
- Node Name dbserv2
- Debug Level high
- Format for hacmp.out Standard
6.View Current State:
- [root@dbserv1 /]#/usr/es/sbin/cluster/utilities/cldump
- Obtaining information via SNMP from Node: dbserv1...
- _____________________________________________________________________________
- Cluster Name: hatest
- Cluster State: UP
- Cluster Substate: STABLE
- _____________________________________________________________________________
- Node Name: dbserv1 State: UP
- Network Name: net_diskhb_01 State: UP
- Address: Label: diskhb_01 State: UP
- Network Name: net_ether_02 State: UP
- Address: 172.16.255.11 Label: dbserv1 State: UP
- Address: 172.16.255.15 Label: dbserv1-serv State: UP
- Address: 172.16.255.17 Label: dbserv2-serv State: UP
- Network Name: net_ether_03 State: UP
- Address: 192.168.0.11 Label: dbserv1-stby State: UP
- Node Name: dbserv2 State: UP
- Network Name: net_diskhb_01 State: UP
- Address: Label: diskhb_02 State: UP
- Network Name: net_ether_02 State: UP
- Address: 172.16.255.13 Label: dbserv2 State: UP
- Network Name: net_ether_03 State: UP
- Address: 192.168.0.13 Label: dbserv2-stby State: UP
- Cluster Name: hatest
- Resource Group Name: oradb
- Startup Policy: Online On First Available Node
- Fallover Policy: Fallover To Next Priority Node In The List
- Fallback Policy: Never Fallback
- Site Policy: ignore
- Node Group State
- ---------------------------- ---------------
- dbserv1 ONLINE
- dbserv2 OFFLINE
7.Switch Resource Group to another node:
- [root@dbserv1 /]#/usr/es/sbin/cluster/utilities/clRGmove -s false -m -i -g oradb -n dbserv2
- Attempting to move resource group oradb to node dbserv2.
- Waiting for the cluster to process the resource group movement request....
- Waiting for the cluster to stabilize............
- Resource group movement successful.
- Resource group oradb is online on node dbserv2.
- Cluster Name: hatest
- Resource Group Name: oradb
- Node State
- ---------------------------- ---------------
- dbserv1 OFFLINE
- dbserv2 ONLINE
8.HACMP Cluster Status Monitor:
- [root@dbserv2 cluster]#/usr/es/sbin/cluster/clstat
- clstat - HACMP Cluster Status Monitor
- -------------------------------------
- Cluster: hatest (1078875880)
- Wed May 30 14:56:14 CST 2012
- State: UP Nodes: 2
- SubState: STABLE
- Node: dbserv1 State: UP
- Interface: dbserv1 (1) Address: 172.16.255.11
- State: UP
- Interface: dbserv1-stby (2) Address: 192.168.0.11
- State: UP
- Interface: diskhb_01 (0) Address: 0.0.0.0
- State: UP
- Node: dbserv2 State: UP
- Interface: dbserv2 (1) Address: 172.16.255.13
- State: UP
- Interface: dbserv2-stby (2) Address: 192.168.0.13
- State: UP
- Interface: diskhb_02 (0) Address: 0.0.0.0
- State: UP
9.Show Network information:
- [root@dbserv2 /]#netstat -i
- Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll
- en0 1500 link#2 0.9.6b.2e.c3.3c 258065 0 183578 0 0
- en0 1500 172.16.255 dbserv2.xzxj.edu 258065 0 183578 0 0
- en0 1500 172.16.255 dbserv1-serv 258065 0 183578 0 0
- en0 1500 172.16.255 dbserv2-serv 258065 0 183578 0 0
- en1 1500 link#3 0.9.6b.be.c6.c4 30577 0 38142 12630 0
- en1 1500 192.168.0 dbserv2-stby 30577 0 38142 12630 0
- en1 1500 192.168.2 dbserv2-pers 30577 0 38142 12630 0
- lo0 16896 link#1 250460 0 250460 0 0
- lo0 16896 127 localhost 250460 0 250460 0 0
- lo0 16896 localhost 250460 0 250460 0 0
- [root@dbserv1 /]#netstat -i
- Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll
- en0 1500 link#2 0.14.5e.c.ce.42 129690 0 71388 0 0
- en0 1500 172.16.255 dbserv1.xzxj.edu 129690 0 71388 0 0
- en1 1500 link#3 0.14.5e.c.b7.65 6523 0 4566 3 0
- en1 1500 192.168.0 dbserv1-stby 6523 0 4566 3 0
- en1 1500 192.168.2 dbserv1-pers 6523 0 4566 3 0
- lo0 16896 link#1 29256 0 29256 0 0
- lo0 16896 127 localhost 29256 0 29256 0 0
- lo0 16896 localhost 29256 0 29256 0 0
10.Make Resource Group online or offline:
- [root@dbserv2 /]#/usr/es/sbin/cluster/utilities/clRGmove -g oradb -n dbserv2 -d
- Attempting to bring group oradb offline on node dbserv2.
- Waiting for the cluster to process the resource group movement request....
- Waiting for the cluster to stabilize........
- Resource group movement successful.
- Resource group oradb is offline on node dbserv2.
- [root@dbserv2 /]#/usr/es/sbin/cluster/utilities/clRGmove -g oradb -n dbserv1 -u
- Attempting to bring group oradb online on node dbserv1.
- Waiting for the cluster to process the resource group movement request....
- Waiting for the cluster to stabilize.......
- Resource group movement successful.
- Resource group oradb is online on node dbserv1.