Sponsored Content
Operating Systems AIX Upgrading PowerHA from 7.1.0 to 7.1.3 Post 302961200 by MichaelFelt on Wednesday 25th of November 2015 07:10:18 AM
Old 11-25-2015
I have not much with PowerHA/SystemMirror - very first versions such as 7.1.0 to 7.1.1 and later - HOWEVER - I do recall there is a fundamental change in the way CAA (cluster aware AIX) is implemented that made it impossible to update 7.1.0 to 7.1.1, The only path was remove, and start again. I have heard that has been softened a bit - but I prefer clean and tend to not use migration/upgrade paths in general.

A basic feature in PowerHA has been the ability to stop the cluster while leaving the application running. Will this (leaving applications "unmanaged by PowerHA", but operational minimize your downtime sufficiently?

PowerHA/SystemMirror from 7.1.0 to 7.1.3 - what else are you updating? Won't those updates require some maint. time as well? Why not combine them? imho it is not fair to put a requirement for downtime for maint solely on the OS and/or middleware. Applications need maint. as well. The 'business' should know/understand that - and sign off for the impact of unexpected downtime that could have been prevented if maint had been timely. (Or do you wait for your engine to lock up before going to the garage for an oil change?).
 

10 More Discussions You Might Find Interesting

1. AIX

strange route issue in powerha 5.4?

hi all we upgraded hacmp(powerha) from 5.2 to 5.4 recently . during the failover testing, we found a strange network issue. after standby node took service ip address (172.15.100.8) online at standby NIC, we were able to log in the standby node by telnet 172.15.100.8 which stays at... (1 Reply)
Discussion started by: rs6000er
1 Replies

2. AIX

PowerHA - assistant can't find network

I've configured multiple clusters using PowerHA 5.5, but never using the 'Two-node cluster configuration assistant'. I removed all the clusters, clean setup, and gave the assistant a try. I've filled in all the necessary options: Communication Path to Takeover Node Application Server ... (11 Replies)
Discussion started by: Koen87
11 Replies

3. AIX

PowerHA, same subnet for persistent and service ip

I am new in AIX and please forgive my poor english. I know that AIX allow same subnet IPs for different interfaces, which result in multipath routing / route striping. My question is, is there any best practice for the persistent and service IP with same subnet to stay on same interface, or... (5 Replies)
Discussion started by: skeyeung
5 Replies

4. AIX

PowerHA Disk on VIO Server

Hello AIX GURU's Can anybody tell me the steps to crate shared VG (enhanced concurent) for my Lpars from VIO server? my questions are: 1. Should I crate Enhanced Concurent VG in VIO and map it using virtual Scsi to Lpar? or 2. Can I just create virtual SCSI in VIO and map to Lpar and... (1 Reply)
Discussion started by: Vit0_Corleone
1 Replies

5. AIX

PowerHA with 3rd node for communication

Looking to find PowerHA with 3rd node used for communication (voting node) only. Does anyone use such configuration with IBM products? (2 Replies)
Discussion started by: gogogo
2 Replies

6. AIX

PowerHA HACMP on VIOS servers

Few questions regarding Power HA ( previously known as HACMP) and VIOS POWERVM IVM ( IBM Virtualization I/O Server ) Is it possible to create HACMP cluster between two VIOS servers Physical Machine_1 VIOS_SERVER_1 LPAR_1 SHARED_DISK_XX VIOS_SERVER_2 Physical Machine_2 LPAR_2... (6 Replies)
Discussion started by: filosophizer
6 Replies

7. AIX

Powerha on AIX 6.1.9

hello ive installed powerha 7.1.3 on two servers aix 6.1.9 6100-09-03-1415 work with dmx4 EMC storgae. after sync cluster ( terminate with OK ) ive see that the repository disk upper only in one machine : hdiskpower60 00c7f6b59fc60d9d caavg_private active... (1 Reply)
Discussion started by: ariec
1 Replies

8. AIX

VXVM in POWERHA 6.1

I have created a VxVM disk group in AIX7.1. I have tried to added this VxVM disk group in powerHA 6.1. But in cluster VxVM DGs are not listing. Is there any other procedure to add vxvm diskgroup to hacmp. Please share me steps for adding vxvm diskgroup to hacmp. (6 Replies)
Discussion started by: sunnybee
6 Replies

9. AIX

PowerHA; Import flash copy of VG?

Hey guys, wondering if this is possible to accomplish. PowerHA SystemMirror7.1 active/passive cluster. Restored a clustered system in test and upgraded to the latest version of PowerHA. Things are working great. However in the interest of time during cut over to the new system, I was hoping to... (4 Replies)
Discussion started by: j_aix
4 Replies

10. AIX

PowerHa 7.1 Migration check failed

Hello Guys, I was trying to upgrade the PowerHA from 6.1.0.9 to 7.1.3 in prod cluster. Have snapshot migration and run climgcheck. 1. Run climgcheck on node1(kul1pqcmur01) and it success 2. Upgrade the cluster sw 3. Run climgcheck on node2(kul1pqcmur02) and it failed with below errors ... (6 Replies)
Discussion started by: novaothers
6 Replies
Dpkg::BuildFlags(3)						   libdpkg-perl 					       Dpkg::BuildFlags(3)

NAME
Dpkg::BuildFlags - query build flags DESCRIPTION
The Dpkg::BuildFlags object is used by dpkg-buildflags and can be used to query the same information. FUNCTIONS
my $bf = Dpkg::BuildFlags->new() Create a new Dpkg::BuildFlags object. It will be initialized based on the value of several configuration files and environment variables. $bf->load_vendor_defaults() Reset the flags stored to the default set provided by the vendor. $bf->load_system_config() Update flags from the system configuration. $bf->load_user_config() Update flags from the user configuration. $bf->load_environment_config() Update flags based on user directives stored in the environment. See dpkg-buildflags(1) for details. $bf->load_maintainer_config() Update flags based on maintainer directives stored in the environment. See dpkg-buildflags(1) for details. $bf->load_config() Call successively load_system_config(), load_user_config(), load_environment_config() and load_maintainer_config() to update the default build flags defined by the vendor. $bf->set($flag, $value, $source, $maint) Update the build flag $flag with value $value and record its origin as $source (if defined). Record it as maintainer modified if $maint is defined and true. $bf->set_feature($area, $feature, $enabled) Update the boolean state of whether a specific feature within a known feature area has been enabled. The only currently known feature area is "hardening". $bf->strip($flag, $value, $source, $maint) Update the build flag $flag by stripping the flags listed in $value and record its origin as $source (if defined). Record it as maintainer modified if $maint is defined and true. $bf->append($flag, $value, $source, $maint) Append the options listed in $value to the current value of the flag $flag. Record its origin as $source (if defined). Record it as maintainer modified if $maint is defined and true. $bf->prepend($flag, $value, $source, $maint) Prepend the options listed in $value to the current value of the flag $flag. Record its origin as $source (if defined). Record it as maintainer modified if $maint is defined and true. $bf->update_from_conffile($file, $source) Update the current build flags based on the configuration directives contained in $file. See dpkg-buildflags(1) for the format of the directives. $source is the origin recorded for any build flag set or modified. $bf->get($flag) Return the value associated to the flag. It might be undef if the flag doesn't exist. $bf->get_feature_areas() Return the feature areas (i.e. the area values has_features will return true for). $bf->get_features($area) Return, for the given area, a hash with keys as feature names, and values as booleans indicating whether the feature is enabled or not. $bf->get_origin($flag) Return the origin associated to the flag. It might be undef if the flag doesn't exist. $bf->is_maintainer_modified($flag) Return true if the flag is modified by the maintainer. $bf->has_features($area) Returns true if the given area of features is known, and false otherwise. The only currently recognized area is "hardening". $bf->has($option) Returns a boolean indicating whether the flags exists in the object. my @flags = $bf->list() Returns the list of flags stored in the object. CHANGES
Version 1.01 New method: $bf->prepend() very similar to append(). Implement support of the prepend operation everywhere. New method: $bf->load_maintainer_config() that update the build flags based on the package maintainer directives. Version 1.02 New methods: $bf->get_features(), $bf->has_features(), $bf->set_feature(). Version 1.03 New method: $bf->get_feature_areas() to list possible values for $bf->get_features. New method $bf->is_maintainer_modified() and new optional parameter to $bf->set(), $bf->append(), $bf->prepend(), $bf->strip(). AUTHOR
Raphael Hertzog <hertzog@debian.org> 1.16.15 2014-06-05 Dpkg::BuildFlags(3)
All times are GMT -4. The time now is 09:37 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy