[TIP] Migration to POWER8


 
Thread Tools Search this Thread
Operating Systems AIX [TIP] Migration to POWER8
# 1  
Old 07-10-2014
[TIP] Migration to POWER8

Read "Migration to POWER8" article to get prepared for migration to POWER8:

Moderator's Comments:
Mod Comment link removed, advertisement

Last edited by zaxxon; 07-11-2014 at 03:40 AM..
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. Solaris

Tip: Ldom migration

Prerequisite: • S7-2L Server Hardware Console Access • Solaris 11.3 OS and LDOM Packages (Ex: 3.4) • Setup IPS Repositories Solaris 11 comes with Oracle VM server pre-installed if older version is there remove the old and install latest Oracle VM... (1 Reply)
Discussion started by: mahendra170
1 Replies

2. AIX

IBM Power Linux Cluster Fence device on Power8 Platform

wasn't quite sure which forum to post in. What typical fence device to configure for a Power Linux PaceMaker Cluster running on the Power8 Platform (S822 Model of hardware), or what should be ordered with the S822 for use as a Fence Device? (5 Replies)
Discussion started by: mrmurdock
5 Replies

3. AIX

Power8 S812L:HMC issue and ...

Hi, I just bought POWER 8 ESERVER S812L from Ebay. There is no AIX on it. I am trying to install RedHat on this box But it does not recognize the hard drive and Ethernet card. I am very newbie with IBM ... please help or hints me please ... 1. can't access to HMC ports, thought it's... (21 Replies)
Discussion started by: lilyn
21 Replies

4. AIX

AIX - FC Switch migration, SAN Migration question!

I'm New to AIX / VIOS We're doing a FC switch cutover on an ibm device, connected via SAN. How do I tell if one path to my remote disk is lost? (aix lvm) How do I tell when my link is down on my HBA port? Appreciate your help, very much! (4 Replies)
Discussion started by: BG_JrAdmin
4 Replies

5. AIX

StorWize v3700 and Power8 (S822) AIX, configuration best practice for LUNs?

Hello, We have an Power8 System (S822) and a IBM StorWize v3700 SAN. The OS is AIX 7.1. With this hardware from what I read I need to download/install special SDDPCM drivers, so I did (SDDPCM VERSION 2.6.6.0 (devices.sddpcm.71.rte). I carved my volumes in the StorWize and presented to... (3 Replies)
Discussion started by: c3rb3rus
3 Replies

6. AIX

New IBM Power8 (S822) and StorWiz V3700 SAN, best practices for production setup/config?

Hello, Got a IBM Power8 box (S822) that I am configuring for replacement of our existing IBM machine. Wanted to touch base with the expert community here to ensure I don't miss anything critical in my setup/config of AIX. Did a fresh AIX 7.1 install on the internal scsi hdisk, mirror'ed... (3 Replies)
Discussion started by: c3rb3rus
3 Replies

7. Shell Programming and Scripting

Regexp tip

Hello, I'm just starting working on it. I'd like to get a tip For istance if I have a file like: a b c d e f .... and I wanna get: 1a & 2b & 3c 0d & 8e & 4f ..... I would like to use sed and come up with a regular expression that works.... (3 Replies)
Discussion started by: Dedalus
3 Replies

8. Solaris

Solaris; tip

plz explain TIP in solaris in detail. (11 Replies)
Discussion started by: karman0931
11 Replies

9. Shell Programming and Scripting

Little bit of a help or just a tip

I am about to do a script that change the COST so i dont need to change each cost. The output looks like this. "OL_ID OL_LINK_COST ----------- ------------ 51 10 52 10 53 10 54 10 55 ... (3 Replies)
Discussion started by: maskot
3 Replies

10. Solaris

tip into 280R

I need to use tip from machine A serial port to machine B serial port. Can someone point me to an example of the correct cable to use? Thanks. (1 Reply)
Discussion started by: dangral
1 Replies
Login or Register to Ask a Question
vzmigrate(8)							    Containers							      vzmigrate(8)

NAME
vzmigrate - migrate a container between two OpenVZ servers SYNOPSIS
vzmigrate [-r|--remove-area yes|no] [--ssh=ssh_options] [--rsync=rsync_options] [--keep-dst] [--online] [-v] destination_address CTID DESCRIPTION
This utility is used to migrate a container from one (source) Hardware Node (HN) to another (destination) HN. The utility can migrate either stopped or running container. For a stopped container, simple CT private area transfer is performed (rsync(1) is used for file transfer). For running containers, migration may be offline (default) or online. This program uses ssh as a transport layer. You will need to put ssh public key to destination node and be able to connect to node without entering password. OPTIONS
-r, --remove-area yes | no Whether to remove a container area on source HN for the successfully migrated container. Default is yes. --ssh=options Additional options that will be passed to ssh while establishing connection to destination HN. --rsync=options Additional options that will be passed to rsync(8). You may add options like -z to enable data compression if you are migrating over a slow link. --keep-dst Do not clean synced destination container private area in case of some error. It makes sense to use this option on big container migration to avoid syncing container private area again in case some error (on container stop for example) occurs during first migration attempt. --online Perform online (zero-downtime) migration: during the migration the container hangs for a while and after the migration it continues working as though nothing has happened. -v Verbose mode. Causes vzmigrate to print debugging messages about its progress. Multiple -v options increase the verbosity. The maximum is 3. EXAMPLES
Migration of CT 101 to 192.168.1.130 with downtime: vzmigrate 192.168.1.130 101 Online migration of CT 102 to 192.168.1.130: vzmigrate --online 192.168.1.130 102 EXIT STATUS
0 EXIT_OK Command completed successfully. 1 EXIT_USAGE Bad command line options. 2 EXIT_VE_STOPPED Container is stopped. 4 EXIT_CONNECT Can't connect to destination (source) HN. 6 EXIT_COPY Container private area copying/moving failed. 7 EXIT_VE_START Can't start or restore destination CT. 8 EXIT_VE_STOP Can't stop or checkpoint source CT. 9 EXIT_EXISTS Container already exists on destination HN. 10 EXIT_NOTEXIST Container does not exists on source HN. 12 EXIT_IP_INUSE You attempt to migrate CT which IP address(es) are already in use on the destination node. 13 EXIT_QUOTA Operation with CT quota failed. SEE ALSO
rsync(1). COPYRIGHT
Copyright (C) 2001-2010, Parallels, Inc. Licensed under GNU GPL. OpenVZ 28 Jun 2011 vzmigrate(8)