Aix 7.2 | PowerVM | Hdlm | Gpfs | Storwize v7000 | Grid Control | Rac | AMS2100 | Vmware

Update SDDPCM in aix from 6.1 to 7.2

2017-02-21T13:39:00.000-03:00

Update SDDPCM

GPFS Native RAID for 100,000-Disk Petascale Systems

2016-11-21T17:24:00.001-03:00

Mike Griese: IBM Tivoli Storage Productivity Center 5.1 - Day 1

2016-11-11T13:47:00.001-03:00

2016-09-08T08:21:00.002-03:00

A new behaviour when creating fully allocated volumes on SVC/Storwize V7.5 and later by Andrew Martin

IBM Real-time Compression and Storwize V7000 and SVC demo

2016-09-06T14:29:00.001-03:00

Storage Efficiency with IBM Easy Tier

2016-09-06T14:00:00.001-03:00

IBM Storwize V7000 Inroduction to FlashCopy HD

2016-09-06T13:50:00.001-03:00

IBM Storwize V7000 Storage Virtualization Terminology Overview HD

2016-09-06T13:40:00.001-03:00

Algoritmos de reclamación de memoria en Vmware

2016-05-24T07:20:00.001-03:00

http://blogs.virtualmaestro.in/2016/05/vmware-memory-reclamation-memory.html?m=1

How to eliminate multibos manually

2015-12-29T09:59:00.002-03:00

Identify the boot disk
bootinfo -b
bootinfo -v
lspv -l <Boot Disk>

1) mv /etc/multibos /tmp
2) cp /etc/inittab /etc/inittab.backup
3) rmitab mbverify
4) rmfs -r /bos_inst
5) rmfs -r /bos_inst/usr
6) rmfs -r /bos_inst/var
7) rmfs -r /bos_inst/opt
8) rmlv -f bos_hd5
9) chpv -c < Boot Disk>
If i don't have hd5 in boot disk i need to create the lv with this command
mklv -y hd5 -t boot -a e rootvg 1 <Boot Disk>
10) bosboot -ad /dev/hdisk21 -l hd5
11) cp /etc/filesystems /etc/filesystems.backup
12) Edit /etc/filesystem and remove "mb= " lines
13) Check that multibos is Ok, with multibos -Xsp

Como restaurar el servicio de apache en el Storage v7000 si la consola deja de atendernos

2015-12-28T08:38:00.000-03:00

Los pasos a seguir son los siguientes, primero identificar los nodos
sainfo lsservicenodes

De aca podemos identificar los <panel names>

Después vemos el estado de los nodos y nos fijamos en la variable config para ver el nodo activo

sainfo lsservicestatus <panel name> | grep config

Finalmente reinicio el tomcat

satask restartservice -service tomcat < panel name>

Listo.

AIX: alt_disk_install

2015-12-14T09:41:00.001-03:00

jueves, 8 de enero de 2009

AIX: alt_disk_install

En este post quiero presentar una familia de comandos de IBM AIX (AIX4.3, AIX5L, AIX6) que me permite trabajar con gran tranquilidad incluso en aquellas operaciones más "arriesgadas" con el rootvg o actualizando masivamente AIX porque permite volver atrás cuando todo lo demás ha fallado.

Se trata del comando alt_disk_install y familia, y es el complemento perfecto al backup con mksysb.

Respaldo de un sistema IBM AIX
Empezaré con un ejemplo sencillo en el que vamos a crear una copia exacta del rootvg que incluye todos los ficheros personalizados, usuarios, configuraciones hardware, etc.. del sistema clonado:

# alt_disk_install -B -C hdisk2
+-------------------------------------------------------------------=---+
ATTENTION: calling new module /usr/sbin/alt_disk_copy. Please see thealt_disk_copy man pageand documentation for more details.
Executing command: {/usr/sbin/alt_disk_copy -O -B -d "hdisk2"}
+-------------------------------------------------------------------=---+
Calling mkszfile to create new /image.data file.
Checking disk sizes.
Creating cloned rootvg volume group and associated logical volumes.
Creating logical volume alt_hd5
Creating logical volume alt_hd6
Creating logical volume alt_hd8
Creating logical volume alt_hd4
Creating logical volume alt_hd2
Creating logical volume alt_hd9var
Creating logical volume alt_hd3
Creating logical volume alt_hd1
Creating logical volume alt_hd10opt
Creating logical volume alt_lg_dumplv
Creating /alt_inst/ file system.
Creating /alt_inst/home file system.
Creating /alt_inst/opt file system.
Creating /alt_inst/tmp file system.
Creating /alt_inst/usr file system.
Creating /alt_inst/var file system.
Generating a list of filesfor backup and restore into the alternate file system...
Backing-up the rootvg files and restoring them to thealternate file system...
Modifying ODM on cloned disk.
Building boot image on cloned disk.
Resetting all device attributes.
NOTE: The first boot from altinst_rootvg will prompt to define the newsystem console.
[...]
Esta operación, en un sistema POWER5 con carga al 60% el tiempo, no baja de 30 minutos. Al finalizar con "lspv" veremos:

# lspv
hdisk0 00c4b08edd400579 rootvg active
hdisk1 none none
hdisk2 00c4b08e0e0397d7 altinst_rootvg
El disco hdisk2 es en estos momentos totalmente bootable, lo que quiere decir que en caso de catástrofe solo tenemos que entrar en el SMS e indicar éste disco como de BOOT.
Posteriormente se pueden aplicar actualizaciones (ver cómo obtener actualizaciones eficientemente) con otro comando de la familia:

# alt_rootvg_op -C -b update_all -l /repos/aix53-ml5-03
Installing optional filesets or updates into alt_inst_rootvg...
install_all_updates: Initializing system parameters.
install_all_updates: Log file is /var/adm/ras/install_all_updates.log
install_all_updates: Checking for updated install utilities on media.
install_all_updates: Updating install utilities to latest level on media.
+------------------------------------------------------------------+
Pre-installation Verification
...

+------------------------------------------------------------------+
Verifying selections...done
Verifying requisites...done
Results...

Otros formulaciones similares:

# alt_disk_copy -P'all' -d hdisk2 -b update_all -l /repos/aix53-ml5-03
# alt_disk_install -C -B -f /tmp/lista-apar.txt -l /repos/aix-apars hdisk2

Instalación de AIX desde un CLON
Visto todo lo anterior si si añadimos "-O" al comando tendremos un AIX idéntico al de nuestro servidor pero sin personalización de hardware y dispositivos (casi "limpio"). Los ficheros de configuración habituales del /etc y los usuarios si que se conservan, de manera que hay que tener esa precaución. El comando queda así:

# alt_disk_install -O -B -C hdisk2

Si el disco hdisk2 es un disco externo, podemos asignarlo a otro servidor con la posibilidad de ponerse a explotar la copia en tiempo record. Sumando ésto con la virtualización tendremos un servidor funcionando en pocas horas tan operativo y actualizado como el que escojamos para clonar.

2015-11-19T09:50:00.000-03:00

How to configure a VIOS Media Repository/

Virtual Media Library (ex. AIX Install/Restore)

Source: IBM web site

Technote (FAQ)

Question

What's the procedure to install an AIX base ISO to an AIX parition using a VIOS media repository?

What's the procedure to create/use/remove a virtual media repository?

Can a mksysb ISO be restored through the virtual media repository?

Cause

This document provides a step by step command line procedure for using a virtual media repository or

Virtual Media Library (VML) to install/restore an AIX partition.

This applies to VIOS version 2.2.x.

Answer

PART I. REQUIREMENTS BEFORE PROCEEDING

PART II. PERFORMING NEW AIX INSTALL WITH VML

PART III. PERFORMING MKSYSB RESTORE WITH MKSYSB ISO AND VML

PART I. REQUIREMENTS BEFORE PROCEEDING :

Please ensure the following requirements are met before proceeding:

A.) There should be an existing pair of virtual scsi adapters paired between the VIO server (vhost)

and the VIO client (vscsi). Since the client may not have an OS, the adapter pairing can be verified through the

partition properties/profile on the HMC or IVM.

B.) A basic understanding of managing VIO virtual optical devices.

C.) A basic understanding of the AIX Installation Menu and how to install AIX.

PART II. PERFORMING NEW AIX INSTALL WITH VML:

Step 1: Obtain AIX base ISO image from ESS and store on the VIO server.

AIX base ISO images can be obtained by contacting Entitled Software Support (ESS) at 1-800-879-2755

option 2, option 2. The representatives should be able to verify entitlement and guide customers on how to

download the ISO image.

After the AIX ISO image had been downloaded, the image can be stored in the /home/padmin directory

of the VIO server.

$ ls -al /home/padmin/AIX_iso

total 8687952

drwxr-xr-x 2 padmin staff 256 Apr 13 17:07 .

drwxr-x--- 9 padmin system 4096 Apr 13 17:10 ..

-rw-r--r-- 1 root staff 4448223232 Apr 13 17:08 AIX_6.1_Base_Operating_System_TL_6100-07-00_DVD_1

_of_2_102011.iso

Step 2: Create/Modify the media repository

A.) Creating the repository in rootvg:

$ mkrep -sp rootvg -size 6G

Virtual Media Repository Created

Repository created within "VMLibrary" logical volume

B.) Creating the repository in a new VG:

$ mkvg -vg <new volume group name> hdisk#

$ mkrep -sp <repository name> -size 6G

C.) Increasing the size of the media repository:

$ lsrep

Size(mb) Free(mb) Parent Pool Parent Size Parent Free

6118 6118 rootvg 139776 26624

$ chrep -size 4G ==> Adds an additional 4GB to the repository

$ lsrep

Size(mb) Free(mb) Parent Pool Parent Size Parent Free

10198 10198 rootvg 139776 22528

NOTE: Increasing the size is currently the only option, to reduce the size of the repository it will need to be

removed and recreated.

Step 3: Create the virtual media disk

$ mkvopt -name <new media disk name> -file <ISO filename> -ro

Example:

$ mkvopt -name base_61_TL7 -file /home/padmin/AIX_iso/AIX_6.1_Base_Operating_System_TL_

6100-07-00_DVD_1_of_2_102011.iso -ro

NOTE: This command may take a few minutes to complete.

Step 4: Verify the virtual media disk is part of the repository

$ lsrep

Size(mb) Free(mb) Parent Pool Parent Size Parent Free

10198 5955 rootvg 139776 22528

Name File Size Optical Access

base_61_TL7 4243 None ro

Step 5: Create the file backed optical device and map it to a vhost:

~ Shown without the vtopt device ~

$ lsmap -vadapter vhost0

SVSA Physloc Client Partition ID

--------------- -------------------------------------------- ------------------

vhost0 U9117.MMA.10708D0-V1-C11 0x00000002

VTD L1_rootvg

Status Available

LUN 0x8100000000000000

Backing device lpar1_lv

Physloc

Mirrored N/A

Create the vtopt device.

$ mkvdev -fbo -vadapter vhost0

vtopt0 Available

~ Shown with the vtopt device ~

$ lsmap -vadapter vhost0

SVSA Physloc Client Partition ID

--------------- -------------------------------------------- ------------------

vhost0 U9117.MMA.10708D0-V1-C11 0x00000002

VTD L1_rootvg

Status Available

LUN 0x8100000000000000

Backing device lpar1_lv

Physloc

Mirrored N/A

VTD vtopt0

Status Available

LUN 0x8200000000000000

Backing device

Physloc

Mirrored N/A

NOTE: Additional vtopt devices can be created and mapped to other vhosts. Consequently, each vtopt device

will appear as a cd-rom device on the VIO client(s).

Step 6: Load the virtual media disk on the vtopt device:

$ lsrep

Size(mb) Free(mb) Parent Pool Parent Size Parent Free

10198 5955 rootvg 139776 22528

Name File Size Optical Access

base_61_TL7 4243 None ro

$ loadopt -vtd vtopt0 -disk base_61_TL7

$ lsrep

Size(mb) Free(mb) Parent Pool Parent Size Parent Free

10198 5955 rootvg 139776 22528

Name File Size Optical Access

base_61_TL7 4243 vtopt0 ro

Verify that the vtopt# backing device is the virtual media disk location .

$lsmap -vadapter vhost0

...

VTD vtopt0

Status Available

LUN 0x8200000000000000

Backing device /var/vio/VMLibrary/base_61_TL7

Physloc

Mirrored N/A

Step 7: Boot the client partition from the virtual optical device:

A.) Activate the AIX Partition to the SMS Menu

B.) Select the virtual optical device (CD-ROM)

-------------------------------------------------------------------------------

Main Menu

1. Select Language

2. Setup Remote IPL (Initial Program Load)

3. Change SCSI Settings

4. Select Console

5. Select Boot Options <<<

Multiboot

1. Select Install/Boot Device <<<

2. Configure Boot Device Order

3. Multiboot Startup <OFF>

Select Device Type

1. Diskette

2. Tape

3. CD/DVD

4. IDE

5. Hard Drive

6. Network

7. List all Devices <<<

Select Device

Device Current Device

Number Position Name

1. - Interpartition Logical LAN

( loc=U9117.MMA.10708D0-V2-C3-T1 )

2. - SCSI CD-ROM

( loc=U9117.MMA.10708D0-V2-C2-T1-L8200000000000000 ) <<<

NOTE: The location code lun ID L8200000000000000 should match the LUN ID of the vtopt mapped to

the vhost:

$lsmap -vadapter vhost0

...

VTD vtopt0

Status Available

LUN 0x8200000000000000

Backing device /var/vio/VMLibrary/base_61_TL7

Physloc

Mirrored N/A

SCSI CD-ROM

( loc=U9117.MMA.10708D0-V2-C2-T1-L8200000000000000 )

1. Information

2. Normal Mode Boot <<<

3. Service Mode Boot

Are you sure you want to exit System Management Services?

1. Yes <<<

2. No

Upon exiting SMS, the AIX partition will boot up from the virtual optical device to the AIX Installation

Menus.

Step 8: Install the AIX operating system.

Step 9: Unloading the virtual media disk:

$ unloadopt -vtd vtopt0

Step 10: Removing the VM Library

A.) Unmap the vtopt# VTDs from the vhost(s)

$ rmvdev -vtd <VTDname>

B.) Remove the virtual media disk(s) from the Virtual Media Repository:

$ rmvopt -name <name of virtual optical disk>

C.) Remove the repository:

$ rmrep [-f]

PART III: PERFORMING MKSYSB RESTORE WITH MKSYSB ISO AND VML :

Step 1: Check the remaining space of the repository and the size of the mksysb ISO file:

$ lsrep

Size(mb) Free(mb) Parent Pool Parent Size Parent Free

10198 5955 rootvg 139776 22528

Name File Size Optical Access

base_61_TL7 4243 None ro

# ls -al

total 38609016

drwxr-xr-x 3 root system 4096 Apr 25 19:02 .

drwxr-x--- 9 padmin system 4096 Apr 25 21:59 ..

-rw-r----- 1 padmin staff 4448223232 Apr 02 15:59 AIX_6.1_Base_Operating_System_TL_6100-07-00_DVD_1

_of_2_102011.iso

-rw-r----- 1 padmin staff 4032843776 Apr 09 22:12 Virtual_IO_Server_V2.2.1_DVD_1_of_2_102011.iso

-rw-r--r-- 1 root system 3120545792 Apr 25 19:01 cd_image_6357164

drwxr-xr-x 2 root system 256 Apr 12 10:16 lost+found

-rw-r--r-- 1 root staff 2542 Apr 02 12:08 mybackup.tar.gz

-rw-r--r-- 1 root staff 183 Apr 02 12:12 mybackup_DEPLOYED

-rw-r--r-- 1 root staff 102 Apr 02 12:12 mybackup_NONDEPLOYED

-rw-r--r-- 1 root staff 1476 Apr 02 12:12 mybackup_VALID

-rw-r----- 1 root system 8163543040 Apr 13 11:48 nim_resources.tar

Step 2: Create the virtual media disk out of the mksysb ISO and add to the repository

$ mkvopt -name lpar1_sysb -file /home/padmin/mount/cd_image_6357164 -ro

Step 3: Verify the new virtual media disk in the repository:

$ lsrep

Size(mb) Free(mb) Parent Pool Parent Size Parent Free

10198 2979 rootvg 139776 22528

Name File Size Optical Access

base_61_TL7 4243 None ro

lpar1_sysb 2976 None ro

Step 4: As it was done in Part II Step 6, load the new mksysb virtual media disk to the available virtual

optical device mapped to the vhost:

$ lsmap -vadapter vhost0

SVSA Physloc Client Partition ID

--------------- -------------------------------------------- ------------------

vhost0 U9117.MMA.10708D0-V1-C11 0x00000002

VTD L1_rootvg

Status Available

LUN 0x8100000000000000

Backing device lpar1_lv

Physloc

Mirrored N/A

VTD vtopt0

Status Available

LUN 0x8200000000000000

Backing device <== Available to add backing device

Physloc

Mirrored N/A

Load the virtual media disk:

$ loadopt -vtd vtopt0 -disk lpar1_sysb

Verify that the virtual media disk is assigned as the backing device:

$ lsmap -vadapter vhost0

SVSA Physloc Client Partition ID

--------------- -------------------------------------------- ------------------

vhost0 U9117.MMA.10708D0-V1-C11 0x00000002

VTD L1_rootvg

Status Available

LUN 0x8100000000000000

Backing device lpar1_lv

Physloc

Mirrored N/A

VTD vtopt0

Status Available

LUN 0x8200000000000000

Backing device /var/vio/VMLibrary/lpar1_sysb

Physloc

Mirrored N/A

Follow Step 6 and Step 7 to boot the client LPAR and restore from the virtual media disk.

Step 5: Restoring a mksysb with multiple volumes

Locate the directory with your multiple ISO images.

NOTE: Ensure that the volume order (vol1,vol2, etc.) are identifiable to reduce the probability of corrupting the

restore.

$ ls -al /home/padmin/mount/*lpar2*

total 6139912

drwxr-xr-x 2 root system 256 Apr 26 07:21 .

drwxr-xr-x 5 root system 4096 Apr 25 22:28 ..

-rw-r--r-- 1 root system 674078720 Apr 26 00:24 cd_image_3014874.vol1

-rw-r--r-- 1 root system 676304896 Apr 26 02:20 cd_image_3014874.vol2

-rw-r--r-- 1 root system 676304896 Apr 26 04:10 cd_image_3014874.vol3

-rw-r--r-- 1 root system 676304896 Apr 26 05:56 cd_image_3014874.vol4

-rw-r--r-- 1 root system 440211456 Apr 26 07:21 cd_image_3014874.vol5

(Total Sum of ISO file sizes = 3143204864 or 3.143 G)

Ensure that the repository has enough space:

$ lsrep

Size(mb) Free(mb) Parent Pool Parent Size Parent Free

10198 2979 rootvg 139776 22528

Name File Size Optical Access

base_61_TL7 4243 None ro

lpar1_sysb 2976 vtopt0 ro

The repository needs more space. Increase the size of the repository.

$ chrep -size 2G

Check the space available.

$ lsrep

Size(mb) Free(mb) Parent Pool Parent Size Parent Free

12238 5019 rootvg 139776 20480

Name File Size Optical Access

base_61_TL7 4243 None ro

lpar1_sysb 2976 vtopt0 ro

Now, create the virtual media disks out of each volume.

Volume1

$ mkvopt -name lpar2_sysb_vol1 -file /home/padmin/mount/vioc_lpar2_backup/cd_image_3014874.vol1

Volume2

$ mkvopt -name lpar2_sysb_vol2 -file /home/padmin/mount/vioc_lpar2_backup/cd_image_3014874.vol2

Volume3

$ mkvopt -name lpar2_sysb_vol3 -file /home/padmin/mount/vioc_lpar2_backup/cd_image_3014874.vol3

Volum4

$ mkvopt -name lpar2_sysb_vol4 -file /home/padmin/mount/vioc_lpar2_backup/cd_image_3014874.vol4

Volume5

$ mkvopt -name lpar2_sysb_vol5 -file /home/padmin/mount/vioc_lpar2_backup/cd_image_3014874.vol5

Verify that all of the volumes have been made into a virtual disk:

$ lsrep

Size(mb) Free(mb) Parent Pool Parent Size Parent Free

12239 2022 rootvg 139776 20480

Name File Size Optical Access

base_61_TL7 4243 None ro

lpar1_sysb 2976 vtopt0 ro

lpar2_sysb_vol1 643 None rw

lpar2_sysb_vol2 645 None rw

lpar2_sysb_vol3 645 None rw

lpar2_sysb_vol4 645 None rw

lpar2_sysb_vol5 420 None rw

Check that a vtopt has been mapped to the appropriate vhost serving the client and that the backing

device is available:

$ lsmap -vadapter vhost1

SVSA Physloc Client Partition ID

--------------- -------------------------------------------- ------------------

vhost1 U9117.MMA.10708D0-V1-C12 0x00000003

VTD L2_rootvg

Status Available

LUN 0x8100000000000000

Backing device lpar2_lv

Physloc

Mirrored N/A

VTD vtopt1

Status Available

LUN 0x8200000000000000

Backing device <== Available for a virtual media disk from repository

Physloc

Mirrored N/A

Load volume 1 of the virtual media disks to the virtual optical device:

$ loadopt -vtd vtopt1 -disk lpar2_sysb_vol1

Verify it's been assigned as the backing device:

$ lsmap -vadapter vhost1

...

VTD vtopt1

Status Available

LUN 0x8200000000000000

Backing device /var/vio/VMLibrary/lpar2_sysb_vol1

Physloc

Mirrored N/A

Boot the client from the virtual optical device and begin the install with virtual media disk volume 1

(Follow Part II Steps 7 and 8)

When prompted for volume 2 (and every additional volume) "Please remove volume 1, insert volume 2,

and press the ENTER key.", on the VIOS we'll need to unload the current volume and load the next volume:

Example:

$ unloadopt -vtd vtopt1

$ set -o vi

$ loadopt -vtd vtopt1 -disk lpar2_sysb_vol2

Back on the client getting installed, strike ENTER/RETURN to begin reading from the second volume and

continue the install.

Continue the process of unloading and loading the virtual media disk volumes in order as the client asks for

them until the restore has completed.

NIM Server Configuration - Part 5

2015-11-12T16:41:00.001-03:00

NIM Server Configuration - Part 4

2015-11-12T16:18:00.001-03:00

NIM Server Configuration - Part 3

2015-11-12T15:48:00.001-03:00

NIM Server Configuration - Part 2

2015-11-12T15:38:00.003-03:00

NIM Server Configuration - Part 1

2015-11-12T15:38:00.001-03:00

The Complete Oracle Blog: Oracle 10g RAC On Linux Using VMware Server

2015-06-04T20:12:00.001-03:00

The Complete Oracle Blog: Oracle 10g RAC On Linux Using VMware Server: Introduction Download Software VMware Server Installation Virtual Machine Setup Guest Operating System Installation Oracle Installat...

What's new in SAN Health Diagnostics Capture 4.0

2015-01-20T08:15:00.002-03:00

Document with details of SAN Health News

IBM Systems Magazine - ASO Can Quickly Boost Performance for Free | AIX | IBM Systems Magazine | System p, System p5, Power System | ASO, Active System Optimizer, POWER7, performance

2015-01-06T15:58:00.001-03:00

IBM Systems Magazine - ASO Can Quickly Boost Performance for Free | AIX | IBM Systems Magazine | System p, System p5, Power System | ASO, Active System Optimizer, POWER7, performance

VIOS tips largesend and large_receive

2014-12-22T15:00:00.003-03:00

VIOS Largesend and Large_receive

IBM Systems Magazine - Tuning AIX Network Performance | AIX | IBM Systems Magazine

2014-12-17T16:48:00.001-03:00

IBM Systems Magazine - Tuning AIX Network Performance | AIX | IBM Systems Magazine

Virtual I/O Server Advisor

2014-12-17T15:11:00.002-03:00

Virtual I/O Server Advisor

Overview

The VIOS advisor is an application that runs within the customer's VIOS for a user specified amount of time (hours), which polls and collects key performance metrics before analyzing results and providing a health check report and proposes changes to the environment or areas to investigate further.

The goal of the VIOS advisor is not to provide another monitoring tool, but instead have an expert system view performance metrics already available to the customer and make assessments and recommendations based on the expertise and experience available within the IBM systems performance group.

Setup

Download vios_advisor.zip from the link provided in download section

Unzip vios_advisor.zip on a workstation that has a web browser.

ftp vios_advisor onto the VIOS you wish to monitor. (place in any directory)

chmod +x vios_advisor to give the application execution priviliges.

Steps to run VIOS Advisor

The application "vios_advisor" takes only one paramter, which is the duration of the the monitoring period, in minutes.
For example,to monitor the VIOS for 30 minutes run:

vios_advisor 30

Usage Statement:

Usage: vios_advisor
duration_in_minutes:
Recommended monitoring time = >= 30 min
Minimum monitoring time = 5 min (only recommended for settings verification)
Maximum monitoring time = 1440 min (24 hours)
-v : Version

Results

The vios_advisor application is silent (does not produce any output to screen) and upon termination, will generate an xml file in the current running directory labeled:

vios_advisor.xml

Copy over the vios_advisor.xml file to the workstation where the zip file: vios_advisor.zip was extracted, and place the file in the vios_advisor folder.
Open the vios_advisor.xml file with the web-browser of your choice to see the report.

https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/Power%20Systems/page/VIOS%20Advisor

NFS between AIX 6.1 like server and Windows 2008R2 like client

2014-12-04T08:44:00.004-03:00

Ver nota