Sponsored Content
Full Discussion: POWER6 VIO Failover
Operating Systems AIX POWER6 VIO Failover Post 302316207 by filosophizer on Thursday 14th of May 2009 10:57:17 AM
Old 05-14-2009
Thanks for the information. The redbook -- which you posted -- gives few examples... I will try that and post here.

Also, for the Partition Mobility POWER6
check this out


Live Partition Mobility is the next step in the IBMs Power Systems™ virtualization continuum. It can be combined with other virtualization technologies, such as logical partitions, Live Workload Partitions, and the SAN Volume Controller, to provide a fully virtualized computing platform that offers the degree of system and infrastructure flexibility required by today's production data centers.
This IBM® Redbooks® publication discusses how Live Partition Mobility can help technical professionals, enterprise architects, and system administrators:
* Migrate entire running AIX® and Linux® partitions and hosted applications from one physical server to another without disrupting services and loads.
* Meet stringent service-level agreements.
* Rebalance loads across systems quickly, with support for multiple concurrent migrations.
* Use a migration wizard for single partition migrations.
This book can help you understand, plan, prepare, and perform partition migration on IBM Power Systems POWER6™ technology-based servers that are running AIX.

Table of contents

Chapter 1. Overview
Chapter 2. Live Partition Mobility mechanisms
Chapter 3. Requirements and preparation
Chapter 4. Basic partition migration scenario
Chapter 5. Advanced topics
Chapter 6. Migration status
Chapter 7. Integrated Virtualization Manager for Live Partition Mobility
Appendix A. Error codes and logs
 

9 More Discussions You Might Find Interesting

1. AIX

Oracle 10G best practices on Power6 AIX5.3

Can anyone point me to any best practices for partitioning, resource prerequisites, and implementation of Oracle 10G release 2 with RAC on 2 power6 550's running AIX5.3 as a cluster? (1 Reply)
Discussion started by: JodyTek
1 Replies

2. AIX

Power6 Virtual Fibre Channel Adapter

Hello, Searched in all IBM Redbooks and on the internet and couldn't find anything about the new feature of POWER 6 which Virtual Fibre ( Fiber ) channel adapter. It is similar to virtual scsi adapter. In my client partition I created the virtual Fibre Adapter mapped it with the VIO... (1 Reply)
Discussion started by: filosophizer
1 Replies

3. AIX

vio server and vio client

Hi, I want to know wheather partition size for installation of vio client can be specified on vio server example If I am installing vio server on blade with 2*300gb hard disk,after that I want to create 2 vio client (AIX Operating system) wheather I can specify hard disk size while... (1 Reply)
Discussion started by: manoj.solaris
1 Replies

4. AIX

AIX 6.1 Power6 - Sys CPU utilization twice that of User

Hello, We just purchased two new 4-way (one active one failover) 5Ghz Power6 Servers (failover) with 64GB RAM (32GB per node) runing AIX 6.1 with two LPARs per node connected to our SAN with two 4GB HBAs. The PROD LPAR has 2 dedicated CPUs (4 virtual) and the TEST LPAR has 2 dedicated CPUs. ... (3 Replies)
Discussion started by: troym72
3 Replies

5. AIX

HACMP with VIO, service IP failover

Would anyone please kindly help to solve this problem... An LPAR with the below network configuration. ent0 and ent1 are logical lan (virtual ethernet) from VIO SEA. en0 1.2.3.4 <- boot ip 192.168.1.1 <- persistent ip 192.168.1.10 <- service ip en1 11.22.33.44 <- boot ip When I... (6 Replies)
Discussion started by: skeyeung
6 Replies

6. AIX

vio server ethernet to vio client ethernet(concepts confusing)

Hi In the vio server when I do # lsattr -El hdisk*, I get a PVID. The same PVID is also seen when I put the lspv command on the vio client partition. This way Im able to confirm the lun using the PVID. Similarly how does the vio client partition gets the virtual ethernet scsi client adapter... (1 Reply)
Discussion started by: newtoaixos
1 Replies

7. AIX

Power6 vs. Power7 hardware performance

I know I will get blasted for posting here, not know where to post this, however, I have performance question between the 2 platforms. Not knowing the exact processors in each box, but the Power6 Platform clock speed is 4400 (?? at least what was told to me), and the Power7 clock speed is 3500.... (5 Replies)
Discussion started by: mrmurdock
5 Replies

8. AIX

How to get power6 power FRU?

how to get power6 power FRU? the power5 can get by this command: lscfg -vp | grep -p 'AC PS' | grep FRU however, the power6 machine cannot get any info for that command. thanks (1 Reply)
Discussion started by: rainbow_bean
1 Replies

9. AIX

Hard drive compatibility for POWER6 p520

Hi, I have recently inherited an old p520 from work running AIX 6.1, based on the POWER6 CPU. I'm planning to play around with it and use it to learn the system, so this is a purely personal project. The machine is not under a support contract any more. I am looking to replace one of the disks... (11 Replies)
Discussion started by: topcat
11 Replies
SYSTEMD-GPT-AUTO-GENERATOR(8)				    systemd-gpt-auto-generator				     SYSTEMD-GPT-AUTO-GENERATOR(8)

NAME
systemd-gpt-auto-generator - Generator for automatically discovering and mounting root, /home and /srv partitions, as well as discovering and enabling swap partitions, based on GPT partition type GUIDs. SYNOPSIS
/lib/systemd/system-generators/systemd-gpt-auto-generator DESCRIPTION
systemd-gpt-auto-generator is a unit generator that automatically discovers root, /home, /srv and swap partitions and creates mount and swap units for them, based on the partition type GUIDs of GUID partition tables (GPT). It implements the Discoverable Partitions Specification[1]. Note that this generator has no effect on non-GPT systems, or where the directories under the mount points are already non-empty. Also, on systems where the units are explicitly configured (for example, listed in fstab(5)), the units this generator creates are overridden, but additional implicit dependencies might be created. This generator will only look for root partitions on the same physical disk the EFI System Partition (ESP) is located on. It will only look for the other partitions on the same physical disk the root file system is located on. These partitions will not be searched on systems where the root file system is distributed on multiple disks, for example via btrfs RAID. systemd-gpt-auto-generator is useful for centralizing file system configuration in the partition table and making manual configuration in /etc/fstab or suchlike unnecessary. This generator looks for the partitions based on their partition type GUID. The following partition type GUIDs are identified: Table 1. Partition Type GUIDs +-------------------------------------+--------------------------------+--------------------------------------+ |Partition Type GUID | Name | Explanation | +-------------------------------------+--------------------------------+--------------------------------------+ |44479540-f297-41b2-9af7-d131d5f0458a | Root Partition (x86) | On 32-bit x86 systems, the first x86 | | | | root partition on the disk the EFI | | | | ESP is located on is mounted to the | | | | root directory /. | +-------------------------------------+--------------------------------+--------------------------------------+ |4f68bce3-e8cd-4db1-96e7-fbcaf984b709 | Root Partition (x86-64) | On 64-bit x86 systems, the first | | | | x86-64 root partition on the disk | | | | the EFI ESP is located on is mounted | | | | to the root directory /. | +-------------------------------------+--------------------------------+--------------------------------------+ |69dad710-2ce4-4e3c-b16c-21a1d49abed3 | Root Partition (32-bit ARM) | On 32-bit ARM systems, the first ARM | | | | root partition on the disk the EFI | | | | ESP is located on is mounted to the | | | | root directory /. | +-------------------------------------+--------------------------------+--------------------------------------+ |b921b045-1df0-41c3-af44-4c6f280d3fae | Root Partition (64-bit ARM) | On 64-bit ARM systems, the first ARM | | | | root partition on the disk the EFI | | | | ESP is located on is mounted to the | | | | root directory /. | +-------------------------------------+--------------------------------+--------------------------------------+ |993d8d3d-f80e-4225-855a-9daf8ed7ea97 | Root Partition (Itanium/IA-64) | On Itanium systems, the first | | | | Itanium root partition on the disk | | | | the EFI ESP is located on is mounted | | | | to the root directory /. | +-------------------------------------+--------------------------------+--------------------------------------+ |933ac7e1-2eb4-4f13-b844-0e14e2aef915 | Home Partition | The first home partition on the disk | | | | the root partition is located on is | | | | mounted to /home. | +-------------------------------------+--------------------------------+--------------------------------------+ |3b8f8425-20e0-4f3b-907f-1a25a76f98e8 | Server Data Partition | The first server data partition on | | | | the disk the root partition is | | | | located on is mounted to /srv. | +-------------------------------------+--------------------------------+--------------------------------------+ |0657fd6d-a4ab-43c4-84e5-0933c84b4f4f | Swap | All swap partitions located on the | | | | disk the root partition is located | | | | on are enabled. | +-------------------------------------+--------------------------------+--------------------------------------+ |c12a7328-f81f-11d2-ba4b-00a0c93ec93b | EFI System Partition (ESP) | The first ESP located on the disk | | | | the root partition is located on is | | | | mounted to /boot or /efi, see below. | +-------------------------------------+--------------------------------+--------------------------------------+ The /home and /srv partitions may be encrypted in LUKS format. In this case, a device mapper device is set up under the names /dev/mapper/home and /dev/mapper/srv. Note that this might create conflicts if the same partition is listed in /etc/crypttab with a different device mapper device name. Mount and automount units for the EFI System Partition (ESP) are generated on EFI systems. The ESP is mounted to /boot, unless a mount point directory /efi exists, in which case it is mounted there. Since this generator creates an automount unit, the mount will only be activated on-demand, when accessed. On systems where /boot (or /efi if it exists) is an explicitly configured mount (for example, listed in fstab(5)) or where the /boot (or /efi) mount point is non-empty, no mount units are generated. When using this generator in conjunction with btrfs file systems, make sure to set the correct default subvolumes on them, using btrfs subvolume set-default. systemd-gpt-auto-generator implements systemd.generator(7). SEE ALSO
systemd(1), systemd.mount(5), systemd.swap(5), systemd-fstab-generator(8), systemd-cryptsetup@.service(8), cryptsetup(8), fstab(5), btrfs(8) NOTES
1. Discoverable Partitions Specification https://www.freedesktop.org/wiki/Specifications/DiscoverablePartitionsSpec/ systemd 237 SYSTEMD-GPT-AUTO-GENERATOR(8)
All times are GMT -4. The time now is 11:04 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy