Wnew Systemmirror 71x

2011
IBM Power Systems Technical University

October 10-14 | Fontainebleau Miami Beach | Miami, FL
IBM
What’s New in PowerHA SystemMirror for AIX v7.1.x
Shawn Bodily
Certified Consulting IT Specialist
sbodily@us.ibm.com
© Copyright IBM Corporation 2011

Materials may not be reproduced in whole or in part without the prior written permission of IBM. 5.3
Release Overview
• Offering has new product ID.

Standard Edition has “base” function plus Smart Assists (5765-H39)
Enterprise Edition - 7.1.2 (5765-H37)
• Migration options – from 5.4.1,5.5, or 6.1

Static (offline)
Snapshot
Rolling migration
• AIX Requisites - 7.1 (expecting 5 years support life)

PHA - 7.1.1
AIX 6.1 TL 7 SP2
AIX 7.1 TL 1 SP2
RSCT 3.1.2.0 – works with both versions of AIX
PHA - 7.1.2
AIX 6.1 TL 8 SP1
AIX 7.1 TL 2 SP1 (Hyperswap also requires IV27586)
RSCT 3.1.4.0 – works with both versions of AIX
2
© Copyright IBM Corporation 2011 2
PowerHA SystemMirror Version Summary
Version Availability End of Support
V5.1 July, 2003 Sep, 2006
V5.2 July, 2004 Sep, 2007
V5.3 July, 2005 Sep, 2008
V5.4.1 Nov, 2007 Sep, 2011

V5.5 Nov 2008 Apr, 2012
V6.1 Oct 2009 Sep, 2014*
V7.1 Sep 2010 Sep 2015
Green – supported; Red – no longer supported

•: Proposed (estimated) dates
Typical End of Marketing (EOM): 2 years after GA
Typical End of Support (EOS): 3 years after GA
Extended support: 3 years after EOS

New features – Standard Edition
• Usability enhancements
– SMIT menu changes*
– User Defined resource types*
– Additional service IP distribution policies to include source IP
– New resource group management enhancement*
– Adaptive Failover capability*
– Systems Director plug-in
– Private Networks
– Network tunables
– New application startup option *
– IPV6 support
– Site Support
• RAS improvements
– Utilizes CAA
– Repository Resiliency
– Backup Repository Disks
– Rootvg system event* Blue=7.1.0
– Federated Security Support * Red=7.1.1
– JFS2 Mount Guard Green=7.1.2
* Topics are covered in detail in backup charts
New features – Standard Edition Continued
• Administrative additions
– New cluster command line, clmgr.
– New distributed cluster clcmd command
– Physical volume rename *
– Display disk UUID*
– DARE progress indicator*
• Additional Smart Assists*

– SAP
– SAP LiveCache Hot Standby Fast Fallover with SVC and DS8k
– FileNet
– Tivoli Storage Manager
Blue=7.1.0
– Lotus Domino Server Red=7.1.1
– MaxDB
– MQSeries
* Topics are covered in detail in backup charts

New features – Enterprise Edition (7.1.2)
Simpler to deploy and easier to manage multi-site configurations with IBM Systems
Director, intuitive interfaces, multi-site install wizard
Stretched Cluster; Cluster wide AIX commands, kernel based event management
single repository multicast communications
Linked Clustering; cluster wide AIX commands, kernel based event management,
linked clusters with unicast communications & dual repositories
HyperSwap for continuously available storage in two-site topologies
Cluster Split/Merge: technology for managing split-site policy scenarios
GA Date: Nov 9 2012

Cluster Aware AIX - differences
• New communications daemon (clcomd)

– Utilizes /etc/cluster/rhosts
– Uses port# 16191 (/etc/services)
• Uses multicast for heartbeating

– Requires infrastructure to allow forwarding multicast packets (port 4096)
• Initial release did not have deadman switch

– CAA update used by 7.1.1 re-introduced deadman switch
– Use clctrl command to alter setting
• Default setting is “a” to assert
• Optional setting “e” to log event only.

Cluster Aware AIX - Requirements
• Repository disk
– Required disk shared between all nodes in the cluster
• SAN/HBA Heartbeat (optional)

– Requires 4GB or 8GB FC adapters Support
• vSCSI and NPIV support added in next gen VIOS (2.2.0.11-FP24SP01 )
– Key is it must have tme attribute
• Additional details http://www-01.ibm.com/support/docview.wss?uid=isg1IV03643
Hostname
– CAA defaults to using the hostname as the HA nodename. For this to differ you
must define another communication path when adding cluster node(s)
• Requires specific vg and lv naming to be available

# lsvg -l caavg_private
caavg_private:
LV NAME TYPE LPs PPs PVs LV STATE MOUNT POINT
caalv_private1 boot 1 1 1 closed/syncd N/A
caalv_private2 boot 1 1 1 closed/syncd N/A
caalv_private3 boot 4 4 1 open/syncd N/A
powerha_crlv boot 1 1 1 closed/syncd N/A
Cluster Aware AIX: Topology Management (1 of 2)
PowerHA PowerHA • By default mutli-channel

based Topology management
Topology Cluster Aware • Use of high speed SAN links
Services AIX
for cluster communication
PowerHA 6.1 PowerHA 7.1
• Kernel based health
management
Host 1 Host 2 Host 1 Host 2
Topology Topology Topology Topology

Management Management Management Management
Network Network
SAN SAN
Switch Switch

Cluster Aware AIX: Topology Management (2 of 2)
Host 2 Host 2
Host 3
Host 3
Host 1 Host 1
MULTICAST
Host 4
Host 4

• Multicast based protocol
• Heartbeat Rings: detailed protocol
– Discover and use as many adapters as
– Leader, Successor, Mayor etc possible
– Difficult to add/delete nodes – Use network and SAN as needed
• Requires IP aliases management – Adapt to the environment: delay,
subnet etc
in the subnet
• Kernel based cluster message handling
Default Multi Channel Health Management
• Minimal Setup
• Multiple channels of
communication
– Network
– SAN Host 1 Host 2
– Central Repository
Reliable Heartbeats Reliable
Heartbeats
Messaging Messaging
First line of Defense Network
Second line of Defense SAN
Third line of Defense Cluster Repository

Heartbeats
Triple redundant communication pipe

CAA Requirements
• Specific feature requirements
– AIX 6.1.7/7.1.1 SP2 with HA 7.1.1

• 3rd party repository disk support (EMC/Hitachi)
– AIX 6.1.7/7.1.1 SP3 with HA 7.1.1

• VLAN Tagging
• Repository Resilience
– AIX 6.1.8/7.1.2 SP1 and HA 7.1.2

• IPV6
• Sites

Additional Service IP Distribution Policies
• Three new additional service IP distribution polices

– Anti-Collocation with Source
– Collocation with Source
– Anti-Collocation with Persistent Label and Source
• These new choices are intended to address problems caused by

AIX route striping behavior
– Some clients expect or require that packets coming from the application are
marked with the application’s IP address (sometimes this is required for
firewall configuration)
– Specify the desired source address in the Source IP Label for outgoing
packets field

Using Source Service IP Distribution Policies
boot_ip1 en1 9.16.128.201 - boot_ip1

srv_ip1
srv_ip1 en1 9.16.128.250 - serv_ip1
Firewall rule
allows srv_ip1

Private Networks
• Oracle requires that a network can be reserved to it

– No heart beating or protocol traffic
• PowerHA 6.1 and prior supported this

– PowerHA 7.1.0 did not
• PowerHA 7.1.1 restores ability to declare a network as “private”
• Interfaces restricted from use by CAA

– PowerHA lists local private network interfaces in /etc/cluster/ifrestrict
– Do not restrict the interface that has the host name
• Improved configuration
– Can change network attribute without redefinition, provided cluster is down
– Restriction to be removed in the service stream

HeartBeat Tuning
• New Heartbeat Tuning Parameters

– Grace Period: The amount of time (seconds) the node will wait before marking a
node as DOWN. Accepted values are between 5 and 30 Seconds.
– Failure Cycle: The frequency of the heartbeat. Accepted values are between 1
and 20 seconds
• Settings apply to all networks across the cluster.
• To change these settings from Smitty sysmirror → Custom Cluster

Configuration → Cluster Nodes and Networks → Manage the Cluster →
Cluster Heartbeat Settings
• These settings can be modified from command line using clmgr command
Clmgr modify cluster HEARTBEAT_FREQUENCY= 10000 GRACE_PERIOD=5000
• The settings will take effect only after the next sync

Repository Resilience
• In PowerHA 7.1.0, the node shuts down on when the repository disk fails
– Disk failure or lost connection
• CAA now provides Repository Resiliency

– Node continues running even on repository disk failure, using locally cached
information
– User can provide a new disk on which to rebuild the repository
– No changes allowed while repository is out of service
• On repository failure
– Message posted to hacmp.out
• Repeated on config_too_long pattern
– DARE and sync continue to function, but any CAA topology changes are rejected
• User must recognize repository failure, and allocate a new disk

– SMIT path under Manage the Cluster -> Select a new Repository Disk

Repository Resiliency & Backup
Pick list chooses

shared disks currently
not part of a volume
group per the ODM
You must make sure

the disk has no VGDA
information on it, or it
will fail with a cryptic
error message.
•Resiliency introduced in PHA 7.1.1

– Requires AIX 6.1.7.3 or 7.1.1.3
•Backup introduced in PHA 7.1.2

• Allows up to 124 backup repository disks (does not autoswap, yet)
JFS2 Mount Guard
Preventing Double Mounts

– Mounting a file system on two nodes at once corrupts it
– LVM Active/Passive mode and CAA Storage Framework fencing help,
but can be defeated
AIX Mount Guard

– A second mount without intervening unmount will be rejected
• Mount state maintained on disk, does not require node interaction
– Set by chfs option, resettable by logredo or chfs

• PowerHA always sets if right AIX level, runs logredo
+testsvcip:cl_activate_fs(.770):/test2fs[fs_mount+106] : Tell JFS2 to try to

protect against double mounts
+testsvcip:cl_activate_fs(.770):/test2fs[fs_mount+108] chfs -a mountguard=yes
/test2fs
– Available in all AIX levels required for PowerHA SystemMirror 7.1.1

• bos.rte.filesystems 7.1.1 or 6.1.7
– PowerHA support back ported to

• PowerHA 6.1 (IV06544)
• PowerHA 5.5 (IV10903)
Clmgr – cluster command line
• Director plug-ins needed a consistent interface for SystemMirror.

– Simplify management of clusters from Director
– Reduce maintenance overhead
• Replacement to CLVT
– Current Smart Assists utilize CLVT
• Overcomes previous CLVT limitations

– Limited trace output and logging
– Globalization
– Ease of use

Clmgr – cluster command line
• Supported object classes

• Supported actions – cluster –
file_collection
– add – site –
fallback_timer
– delete – node –
volume_group (incomplete coverage)
– manage – interface –
logical_volume (incomplete coverage)
– modify – network –
file_system (incomplete coverage)
– move – resource_group –
physical_volume (incomplete
– offline – service_ip coverage)
– online – persistent_ip – method (incomplete coverage)

– query – application_controller – report
– recover – application_monitor – snapshot
– sync – dependency – tape
– view

Clcmd – cluster distributed commands
• /usr/sbin/clcmd
• Provided by CAA
• Distributes command to all cluster nodes
– Ease of use
– Reminiscent of dsh from SP2 days
• Example
– clcmd cat /etc/cluster/rhosts
NODE jessica.dfw.ibm.com
-------------------------------
jessica
jordan
-------------------------------
NODE jordan.dfw.ibm.com
-------------------------------
jessica
jordan

PowerHA 7.1.2 Two-Site Solutions
Two Sites Stretched Linked

Cluster Clusters
Inter Site Communication Multicast Unicast
Repository Disk Shared Separate
Cluster Communication  Networks  Networks
 SAN  SAN *
 Disk
Cross Site LVM Mirroring  
Repository Disk HyperSwap  

Multi Site Concurrent RG  NA
with / HyperSwap (active-active)
*
Two-Site Stretched Cluster
PowerHA V7.1 Standard Enterprise
Multi Site Definition  

• Site Service IP
• Site Policies
Stretched Cluster  
Linked Clusters  
HADR with Storage Replication NA 

Management
Two-Site Linked Cluster
HyperSwap NA 
*Future capability
PowerHA 7.1.2 Enterprise Edition HyperSwap
• Multi-Site PowerHA cluster with

continuous storage availability
Application
• Non-disruptive - applications keep PowerHA HyperSwap Cluster
running in the event of a storage

outage
• Storage maintenance without

downtime Metro Mirror
Primary DS8K Secondary DS8K

• Storage migration without
downtime

PowerHA 7.1.2 Linked Cluster Split/Merge Management
• Split-Site Management
– Heartbeat indicates failure
– One of the sites becomes production
x – Site partitioning is avoided
• Merge Management
x – Site partitioning occurred

– One of the sites must become the sync
source for the cluster
* Future capability

PowerHA 7.1.2 Merge/Split Policy Options
Policy Setting Split Merge Comments
Majority Rule   • >N/2 side wins (N= total nodes in the

cluster)
• In case of a tie, side with the smallest node
id wins
Tie Breaker   • Tie break holder side wins
Manual (future)   • Operator interventions enabled for

S.O.D
split/merge processing
• Tie breaker policy

X – A means of determining the winner when
a split-site condition occurs
– Losing side is quieced
SCSI 3 reservation disk
• Tie breaker policy options
– Majority rules (site with largest number of nodes wins)
– SCSI 3 reservation disk (first there wins)
X – Operator intervention (operator decides)
Majority rules
PowerHA SystemMirror 7.1.2 Stretched Clusters
Cross-Site Mirroring Recovery within a Hyper Swap Mirroring

Campus Metropolitan Region Metropolitan Region
Single Data Center Two Data Centers Two Data Centers

Applications remain active Systems remain active Systems remain active
Continuous access to data Multi-site workloads can Continuous access to data

in the event of a storage withstand site and/or in the event of a storage
subsystem outage storage failures subsystem outage
PowerHA-Standard Edition PowerHA Enterprise Edition PowerHA Enterprise Edition
LVM Mirroring GLVM, Metro Mirror, DS8800 and Metro Mirror

SRDF,TrueCopy RPO =0 RTO <1 hr
RPO=0, RTO = 0
RPO=0 & RTO<1 hr Storage RTO..minutes
Repository Disk Standard Edition Enterprise Edition

PowerHA SystemMirror 7.1.2 Linked Clusters
Recovery within a Disaster Recovery at

Cross-Site Mirroring Hyper-Swap Mirroring
Metropolitan Region Extended Distance
Campus Metropolitan Region
Single Data Centers Two Data Centers Single Data Centers Two Data Centers
Applications remain active Systems remain active Applications remain active Rapid Systems Disaster
Recovery with “seconds” of
Continuous access to data Multi-site workloads can Continuous access to data Data Loss
in the event of a storage withstand site and/or in the event of a storage Disaster recovery for out of
subsystem outage storage failures subsystem outage region interruptions
PowerHA-Standard Edition PowerHA Enterprise Edition PowerHA-Entertprise Edition PowerHA Enterprise Edition
LVM Mirroring GLVM, Metro Mirror, GLVM/PPRC/SVC/SRDF/TrueCopy
DS8800 and Metro Mirror
SRDF,TrueCopy RPO secs & RTO <1 hr
RPO=0, RTO ~ 0 RPO=0, RTO ~ 0
RPO=0 & RTO<1 hr
Repository Disk Standard Edition Enterprise Edition

PowerHA SystemMirror 7.1.2 for AIX
PowerHA SystemMirror V7 Standard Enterprise
Edition Edition
AIX IT operations skill base  
AIX Technical skill support base  
 AIX embedded clustering AIX Shared Storage management  
technology AIX Volume manager/Mirroring  

AIX File System  
 AIX Cluster Aware, Kernel AIX SMIT Management Tools  
based event management AIX DLPAR HA/DR management  

IBM Director based GUI  
 PowerHA skills are an AIX Cluster Aware  
extension AIX skills Kernel based event management  

Federated Security  
 WW service and support Stretch cluster (shared repository)  

Cross Site Mirroring  
Triple redundant multi-cast heartbeat 
SAN based communications 
Live Cache SAP hot standby 
Linked clusters (separate repositories) 
HyperSwap 
Multi-Site set up wizard 
Split/Merge management
© Copyright IBM Corporationoptions
2011 
29
IBM Director interface for PowerHA SystemMirror V7
 Included with PowerHA

SystemMirror V7
 Masks complexity
 Central management
 Real-time status
 Smart Assist integration
 Deployment wizards
Demo available at: http://www-03.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/PRS5099

PowerHA 7.1.2 Director Plug-in Enhancements
• Wizards
 Cluster Create Wizard
 Single Site and Multi Site deployment
 Resource Group Creation Wizard
 Custom and Smart Assist based RG
deployment
 SAP liveCache HotStandby solution Wizard
 Federated Security Setup Wizard
 Volume Group Create Wizard
 Support for LVM Mirror Pools
 Replication (Mirror) Group Wizard
 HyperSwap Setup
• Management Enhancements
 Repository Disk/s Management
 Resource Groups management
 Snapshots, networks, log files etc
 Reports Management
 Notifications management
 Event driven callouts
 Capacity upgrade based fallovers
 HyperSwap Management
 File collections
Additional information and Training
IBM PowerHA SystemMirror for AIX v7.1.1 Update Redbook

www.redbooks.ibm.com/redpieces/abstracts/sg248030.html
IBM PowerHA SystemMirror 7.1.2 Enterprise Edition for AIX

http://www.redbooks.ibm.com/Redbooks.nsf/RedpieceAbstracts/sg248106.html
Rolling Migration Demo to PowerHA 7.1 Update Redbook

http://www-03.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/PRS4895
also on my Youtube
Channel under POWERHAguy
Follow me on Twitter:
http://twitter.com/#!/POWERHAguy

BACKUP CHARTS

New features – Enterprise Edition 6.1 SP3
• Hitachi TrueCopy/HUR replication support

– TrueCopy for synchronous replication
– HUR for asynchronous replication
– http://www-03.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/FLASH10720
– Recorded Demo available at:
• http://www.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/PRS4594
• DS8700 Global Mirror support

– Asynchronous replication
– http://www-03.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/FLASH10719
• HP Continuous Access (P9500 announced 09/06/2011 )

– XP12000/XP24000 GA date expected 4Q/2011
• Storwize v7000 (Announced 9/30/2011)
• SVC 6.2 (Announced 9/30/2011)

Note: The Enterprise Edition install media will not be refreshed to include SP3. You must download it
from fixdist and install the appropriate filesets as needed.
New features – Enterprise Edition 6.1 SP7
• XIV replication support

– Synchronous & Asynchronous replication
– PowerHA, AIX & RSCT Requirements
 Cluster.es.genxd 6.1.0.7
 AIX 5.3 TL9 or higher
– RSCT V2.4.12.0 or higher
 AIX 6.1 TL2 SP1 or higher
– RSCT V2.5.4.0 or higher
– IBM XIV Storage

 Firmware Software Bundle 10.2.4 or later
– XCLI version 2.4.4 or later
 Must be installed on all PowerHA nodes
– Access to all XIV storage systems
 Reachable from all PowerHA nodes (via IPv4)
 Valid XCLI user account
Note: The Enterprise Edition install media will not be refreshed to include SP7.
You must download it from fixdist and install the appropriate filesets as needed.
SMIT Menus
smit hacmp (v6.1) New fastpath: smit sysmirror
HACMP for AIX PowerHA SystemMirror
Move cursor to desired item and press Enter. Move cursor to desired item and press Enter.
Initialization and Standard Configuration Cluster Nodes and Networks

Extended Configuration Cluster Applications and Resources
System Management (C-SPOC)

Problem Determination Tools System Management (C-SPOC)
Problem Determination Tools
Can't find what you are looking for ?
Not sure where to start ? Custom Cluster Configuration
Can't find what you are looking for ?
Not sure where to start ?
Fastpath hacmp is still valid

SMIT Menus - Continued Cluster Nodes and Networks
Move cursor to desired item and press Enter.
Initial Cluster Setup (Typical)
smit hacmp (v6.1) Manage the Cluster

Manage Nodes
Manage Networks and Network Interfaces
Initialization and Standard Configuration
Discover Network Interfaces and Disks
Move cursor to desired item and press Enter.
Verify and Synchronize Cluster Configuration
Configuration Assistants
Configure an HACMP Cluster and Nodes
Configure Resources to Make Highly Available
Configure HACMP Resource Groups Cluster Application and Resources
Verify and Synchronize HACMP Cluster Configuration Move cursor to desired item and press Enter.
Manage Cluster Services and Resource Groups
Display HACMP configuration Make Applications Highly Available (User Smart Assists)
HACMP Cluster Test Tool Resources
Resource Groups
Not sure where to start ?
Verify and Synchronize Cluster Configuration

User Defined Resources
• Presently, A user can introduce a new resource type by creating a

Application Server.
– PowerHA requires a start/stop/monitor for that resource
• However, PowerHA follows a strict pre-known order to handles the DISK

resources.
– Volume Groups will be handled first VOLUME GROUP
– Application Servers will be handled at the last.
Acquisition Order
• This approach is not flexible for end users FILE SYSTEM
• What’s new in the next release

– Introducing a concept of ‘User Defined Resource Types’ where, user is allowed to
User Defined
Resource
develop a bundle which includes attributes/verifications/order for PowerHA etc.
– Framework accepts Methods to verify/start/stop/monitor/cleanup/restart the user defined SERVICE IP
resource
– A xml file can be supplied as input which will be having definition for the user defined
resource type APPLICATION
– PowerHA allows to create instances of the user defined resource type and these
instances can be added into RG as resources.

Creating User Defined Resources
• smitty sysmirror->Custom Cluster Configuration->Resources-

>Configure User Defined Resources and Types-Configure Userr Defined
Resource Types->Add a User Defined Resource Type
• Then add the type as a resource • Then add resource into resource group
Setting the Service IP Distribution Policy
• smitty cm_service_ip-> Configure Service IP Labels/Address

Distribution Preference->(choose network)

New Dependencies
• Previously, PowerHA supports only parent-child dependency

among Resource Groups.
– Child RGs starts after all of it’s parents starts
– Child RGs stops before it’s parents stops
• Not sufficient to support complex applications like SAP/FileNet

– FileNet App Server requires to be started only after database, but no need to be stopped if
the DB is down for sometime
• Two new dependencies are introduced in PowerHA 7.1

• STARTAFTER
• STOPAFTER
– Affects how RG started or stopped
– Simplified UI for managing these relations in both SMIT and Director

Dynamic Node Priority new Adaptive Fallover
• Present PowerHA support static/dynamic failover policies

– Static: New failover node will be the next node from the node participation list
– Dynamic Node Priority : allows the failover node to be having certain degree of free
CPU/memory/IO activity
• This is not sufficient in some specific cases like SAP Enqueue replication, where RG for
Enqueue server need to failover where Enqueue Replication is running.
– Introducing a new dynamic failover policy where, it asks user to supply a script which can dictate
the failover behavior.
• The supplied script will be executed on all nodes by PowerHA to know whether the given node
can be used as host for failing over RG
• Since it is a script, no of checks can be performed by user to let PowerHA know whether the
node can be used as a host on a dynamic basis .
• The DNP feature is enhanced to support two more policies.

• The return code of a user-defined script is used in determining the destination
node:
– cl_lowest_nonzero_udscript_rc
– cl_highest_udscript_rc
Director Plug-in
• Replacement for WebSMIT

• A single, centralized view into all PowerHA SystemMirror clusters
– Centralized, secure access point
– Single sign-on capability
• Two highly accessible interfaces:

– Graphical interface
• Maximum, interactive assistance with many tasks
• Instant, and nearly instant help is available for just about everything
• Maximum error checking
• SystemMirror enterprise health summary
– Textual interface
• Maximum speed
• Centralized, cross-cluster scripting
• A common, unified IBM STG interface.

– Learn once, manage many.

Systems Director Plug-in – Getting Started

Wizards – Creating a Cluster
• Only unused
SystemMirror
nodes are
displayed
Yellow background
• Wethis
means value
check forIs
required.
compatible levels
and edition as
selections are
made
• Common storage
can be checked
• All labels checked against SystemMirror naming rulesonly after multiple
selections
• Addresses validated to be well-formed

•• Optionally select, ordisk

Select a repository type,
fora the
persistent
cluster IP
•• Optionally change
The node name, in the default controlling
parentheses, indicatesnode
the disk name is for
that node
• Optional, but a good

idea; completes the
initial configuration
of the cluster.
• Cluster security settings can be adjusted if desired

Systems Director Plug-in – Management View
Navigation Content
Area Area

System Director Plug-in – Summary Panel

Rootvg System Event
• New kernel level monitoring

• Monitors the loss of rootvg
• Defaults response is to log event and reboot causing fallover to occur
• Smitty sysmirror->Custom Cluster Configuration->Events->System Events
Change/Show Event Response
Type or select values in entry fields.

Press Enter AFTER making all desired changes.
[Entry Fields]
* Event Name ROOTVG +
* Response Log event and reboot +
* Active Yes +

Federated Security
 Federated Security for single-point-of-control, cluster-wide security management. The

Federated Security feature integrates support for 3 different components:
– Lightweight Directory Access Protocol (LDAP)
– Role Based Access Control (RBAC)
– Encrypted Files System (EFS)
System requirements
PowerHA SystemMirror Version 7.1.1, or later
IBM LDAP 6.2 (Correct version of Gskit and DB2 packaged with LDAP), or later (Applicable for
server and client both. )
Microsoft Windows Server:
Microsoft Windows Server 2003/R2 Active Directory
Microsoft Windows Server 2008/R2 Active Directory
Services for UNIX (SFU) 3.5, or later, or the Subsystem for UNIX-based Applications (SUA)
(Needed to configure rsh between AIX client and Windows server)
expect.base
Note: Either a cluster will be configured for Active Directory server or IBM TDS server. In either case the
LDAP client will be IBM LDAP. rsh service needs to be configured in case we want the schema copy and
attributes modification for AD to be done by SystemMirror configuration. Refer to SystemMirror Admin
guide for more information.
Configuring application startup mode
• Application controllers started in the background by default
• Add/Change controller menu has a new option for foreground startup
Add Application Controller Scripts

[Entry Fields]
* Application Controller Name []
* Start Script []
* Stop Script []
Application Monitor Name(s) +
Application startup mode [foreground] +
• Foreground start causes cluster event processing to wait for completion of the
application controller start script
• Simplifies design of start scripts
– Allows sequencing of resource groups with dependencies
• Poorly designed scripts may cause hangs (config_too_long)
• Return codes usually not checked, SP1 will cause event error if RC=1
Physical Volume Rename
• A given physical volume may have different names on different nodes

– Almost guaranteed if nodes access a different number of disks
• Only volumes not already part of a volume group can be renamed

– Pick list only gives disks not in a volume group
– Can change all instances byRename
PVIDa Physical Volume
[Entry Fields]
Physical Volume Name hdisk2

Physical Volume Identifier 00f638bc49c50b8a
Physical Volume is Known on these Nodes r3r6m21,r3r6m22
New Physical Volume Name []

Change all Physical Volumes with this PVID? no

Display Disk UUID
• Convenient way to display Storage Framework information on a physical volume

– UUID is “Universal Unique ID”
– Used to identify objects within CAA
• Intended for assistance in low level trace and debug

– User should not normally need to know this information
Disk name: hdisk8
Disk UUID: 4c13e89df353574f 154e795c0bc89f5e
Fence Group UUID: 4cc81c16b64bf65d 51f638bc49c5094c - Fence Group vg00
Disk device major/minor number: 20, 2
Fence height: 0 (Read/Write)
Reserve mode: 1 (Single Path)
Disk Type: 0x01 (Local access only)
Disk State: 0
C-SPOC- Physical Volumes-Show UUID for a Physical Volume

DARE Progress Indicators
• Completion of a configuration change is not apparent
– Users could start up overlapping or contradictory changes
• With PowerHA 7.1.1, user’s terminal remains locked during DARE processing
• Progress indicators displayed
– Show Cluster Manager state, on-going events
• Plan to fine-tune display
– Remove confusing and redundant information
• Plan to back port to PowerHA 6.1 and 5.5
• Example: Cluster Manager Current state: ST_RP_RUNNING
Cluster Manager Current state: ST_RP_RUNNING
Cluster Manager Current state: ST_BARRIER
Cluster Manager Current state: ST_CBARRIER
Cluster Manager Current state: ST_UNSTABLE
Cluster Manager Current state: ST_STABLE
...Completed
Smart Assists Enhancements – Redefining Component usage
• Currently Smart Assist for WAS and Oracle supports different products as
components
• Smart Assist for WAS supports the following components
– IBM HTTP Server
– IBM Tivoli Directory Server
– IBM WebSphere Application Server - classic
– IBM WebSphere Application Server ND – Deployment Manager
• Smart Assist for Oracle supports the following components
– Oracle Database 10g/11g
– Oracle Application Server 10g R1
• Disadvantages
– Grouping support for different products (as components) affecting consumability
– Split the existing Smart Assist for WAS and Smart Assist for Oracle into
• Smart Assist for WebSphere
• Smart Assist for IHS
• Smart Assist for TDS
• Smart Assist for Oracle Database
• Smart Assist for Oracle Application Server

SA Enhancements – Discovery mechanism and Manual configuration
• Until PowerHA 6.1, to get a list of smart assists, the framework runs all the
discovery scripts and returns which list which user can work
– This has been changed such that, we list the installed smart assists first and run the discovery script
of the only chosen smart assist from the list
• Manual Configuration
– Until PowerHA 6.1, A Smart Assist will automatically discover application and it’s resources and
allows you to configure them under PowerHA.
– However, If the discovery script fails, user have no option to proceed further
– Starting from PowerHA 710, user has another option where he/she can supply the application
details in a XML file (a template XML is supplied)
– smitty clsa -> <smart assist name> ->manual configuration

Smart Assists Enhancements – List of all Smart Assists
SystemMirror 7.1.0 SystemMirror 7.1.1

Summary
What has changed

– Cluster monitoring
• CAA instead of topsvcs
– Multicast vs heartbeat rings, no dependence on boot addresses for heartbeat
– Graphical user interface

• ISD Plug-in instead of WebSMIT
– Introduction of robust CLI for PowerHA configuration, control and status

• clmgr is an updated version of clvt
• Leveraged by ISD Plug-in

Summary
What has not changed

– Cluster manager event processing
• The same event scripts and event flows for resource control
• Pre-/post-event configuration and processing
– Resource and resource group configuration

• Same constructs configured in HACMP ODM
– Resource groups, service addresses, application start/stop, application monitoring
– Synchronization of HACMP ODM to all nodes (PHA cluster configuration

NOT central)

Wnew Systemmirror 71x

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Wnew Systemmirror 71x

Uploaded by

Copyright:

Available Formats

2011

IBM Power Systems Technical University

What’s New in PowerHA SystemMirror for AIX v7.1.x

© Copyright IBM Corporation 2011

• Offering has new product ID.

• Migration options – from 5.4.1,5.5, or 6.1

• AIX Requisites - 7.1 (expecting 5 years support life)

Version Availability End of Support

V5.1 July, 2003 Sep, 2006

V5.2 July, 2004 Sep, 2007

V5.3 July, 2005 Sep, 2008

V5.4.1 Nov, 2007 Sep, 2011

Green – supported; Red – no longer supported

© Copyright IBM Corporation 2011 3

• Additional Smart Assists*

© Copyright IBM Corporation 2011 5

HyperSwap for continuously available storage in two-site topologies

Cluster Split/Merge: technology for managing split-site policy scenarios

GA Date: Nov 9 2012

© Copyright IBM Corporation 2011 6

• New communications daemon (clcomd)

• Uses multicast for heartbeating

• Initial release did not have deadman switch

© Copyright IBM Corporation 2011 7

• SAN/HBA Heartbeat (optional)

• Requires specific vg and lv naming to be available

PowerHA PowerHA • By default mutli-channel

Topology Topology Topology Topology

PowerHA 6.1 PowerHA 7.1

© Copyright IBM Corporation 2011 9

PowerHA 6.1 PowerHA 7.1

First line of Defense Network

Second line of Defense SAN

Third line of Defense Cluster Repository

Triple redundant communication pipe

© Copyright IBM Corporation 2011 11

• Specific feature requirements

– AIX 6.1.7/7.1.1 SP2 with HA 7.1.1

– AIX 6.1.7/7.1.1 SP3 with HA 7.1.1

– AIX 6.1.8/7.1.2 SP1 and HA 7.1.2

© Copyright IBM Corporation 2011 12

• Three new additional service IP distribution polices

• These new choices are intended to address problems caused by

© Copyright IBM Corporation 2011 13

boot_ip1 en1 9.16.128.201 - boot_ip1

© Copyright IBM Corporation 2011 14

• Oracle requires that a network can be reserved to it

• PowerHA 6.1 and prior supported this

• PowerHA 7.1.1 restores ability to declare a network as “private”

• Interfaces restricted from use by CAA

© Copyright IBM Corporation 2011 15

• New Heartbeat Tuning Parameters

• Settings apply to all networks across the cluster.

• To change these settings from Smitty sysmirror → Custom Cluster

© Copyright IBM Corporation 2011 16

• CAA now provides Repository Resiliency

• User must recognize repository failure, and allocate a new disk

© Copyright IBM Corporation 2011 17

Pick list chooses

You must make sure

•Resiliency introduced in PHA 7.1.1

•Backup introduced in PHA 7.1.2

Preventing Double Mounts

AIX Mount Guard