Installare una specifica lista di filesets

Voglio installare un fileset di una specifica versione , in questo caso rsct.basic.rte:3.1.0.3
ma smitty si ostina a propormi il 3.1.0.4 .

Allora lo inganno creandomi una lista di filesets e passandola come parametro al geninstall ...la installo.

Trovo i pacchetti che mi servono

root@aixbox:/download/AIX/PTF/Aix-61-06-03#installp -L -d . | grep rsct.basic.rte
rsct.basic:rsct.basic.rte:3.1.0.0::I:T:::::N:RSCT Basic Function::::0::
rsct.basic:rsct.basic.rte:3.1.0.1::S:T:::::N:RSCT Basic Function::::0::
rsct.basic:rsct.basic.rte:3.1.0.3::S:T:::::N:RSCT Basic Function::::0::

e li salvo in una lista

root@aixbox:/download/AIX/PTF/Aix-61-06-03#installp -L -d .| awk -F: '{print $2"\t"$3}' > rsct.txt

Il fileset rsct.basic.rte ha come prereq rsct.compat.basic.rte , quindi faccio altrettanto aggiungendo alla lista
il prereq :


root@aixbox:/download/AIX/PTF/Aix-61-06-03#installp -L -d . | grep rsct.compat.clients
rsct.compat.clients:rsct.compat.clients.hacmp:3.1.0.0::I:T:::::N:RSCT Event Management Client Function (HACMP/ES Support)::::0::
rsct.compat.clients:rsct.compat.clients.rte:3.1.0.0::I:C:::::N:RSCT Event Management Client Function::::0::

root@aixbox:/download/AIX/PTF/Aix-61-06-03#installp -L -d . | grep rsct.compat.clients | awk -F: '{print $2"\t"$3}' >> rsct.txt

root@aixbox:/download/AIX/PTF/Aix-61-06-03#cat rsct.txt
rsct.basic.rte  3.1.0.0
rsct.basic.rte  3.1.0.1
rsct.basic.rte  3.1.0.3
rsct.compat.clients.hacmp       3.1.0.0
rsct.compat.clients.rte 3.1.0.0

root@aixbox:/download/AIX/PTF/Aix-61-06-03#geninstall -I "a -cgNqwXY" -Z -d . -f rsct.txt

+-----------------------------------------------------------------------------+
                    Pre-installation Verification...
+-----------------------------------------------------------------------------+
Verifying selections...done
Verifying requisites...done
Results...

WARNINGS
--------
  Problems described in this section are not likely to be the source of any
  immediate or serious failures, but further actions may be necessary or
  desired.

  Already Installed
  -----------------
  The number of selected filesets that are either already installed
  or effectively installed through superseding filesets is 1.  See
  the summaries at the end of this installation for details.

  NOTE:  Base level filesets may be reinstalled using the "Force"
  option (-F flag), or they may be removed, using the deinstall or
  "Remove Software Products" facility (-u flag), and then reinstalled.

  << End of Warning Section >>

Verifying requisites...done
Results...

WARNINGS
--------
  Problems described in this section are not likely to be the source of any
  immediate or serious failures, but further actions may be necessary or
  desired.

  Superseded Fileset Updates
  --------------------------
  Fileset updates listed in this section will not be installed.  Newer
  updates which supersede (replace) these were selected instead (either by
  you or automatically by the installation program).  Make sure that the
  superseding updates listed passed pre-installation verification.

  rsct.basic.rte 3.1.0.1                            (Superseded by 3.1.0.3)

  << End of Warning Section >>

SUCCESSES
---------
  Filesets listed in this section passed pre-installation verification
  and will be installed.

  Selected Filesets
  -----------------
  rsct.basic.rte 3.1.0.0                      # RSCT Basic Function
  rsct.basic.rte 3.1.0.3                      # RSCT Basic Function
  rsct.compat.clients.hacmp 3.1.0.0           # RSCT Event Management Client...


  Requisites
  ----------
  (being installed automatically;  required by filesets listed above)
  rsct.compat.basic.rte 3.1.0.0               # RSCT Event Management Basic ...

  << End of Success Section >>

+-----------------------------------------------------------------------------+
                   BUILDDATE Verification ...
+-----------------------------------------------------------------------------+
Verifying build dates...done
FILESET STATISTICS
------------------
    6  Selected to be installed, of which:
        4  Passed pre-installation verification
        1  Replaced by superseding updates
        1  Already installed (directly or via superseding filesets)
    1  Additional requisites to be automatically installed
  ----
    5  Total to be installed

+-----------------------------------------------------------------------------+
                         Installing Software...
+-----------------------------------------------------------------------------+

installp: APPLYING software for:
        rsct.basic.rte 3.1.0.0


. . . . . << Copyright notice for rsct.basic >> . . . . . . .
 Licensed Materials - Property of IBM

 5765F07AP
   (C) Copyright International Business Machines Corp. 1985, 2010.

 All rights reserved.
 US Government Users Restricted Rights - Use, duplication or disclosure
 restricted by GSA ADP Schedule Contract with IBM Corp.
. . . . . << End of copyright notice for rsct.basic >>. . . .

Filesets processed:  1 of 5  (Total time:  16 secs).

installp: APPLYING software for:
        rsct.basic.rte 3.1.0.3

Filesets processed:  2 of 5  (Total time:  21 secs).

installp: APPLYING software for:

        rsct.compat.clients.hacmp 3.1.0.0


. . . . . << Copyright notice for rsct.compat.clients >> . . . . . . .
 Licensed Materials - Property of IBM

 5765F07AP
   (C) Copyright International Business Machines Corp. 1985, 2010.

 All rights reserved.
 US Government Users Restricted Rights - Use, duplication or disclosure
 restricted by GSA ADP Schedule Contract with IBM Corp.
. . . . . << End of copyright notice for rsct.compat.clients >>. . . .

Filesets processed:  4 of 5  (Total time:  23 secs).

installp: APPLYING software for:
        rsct.compat.basic.rte 3.1.0.0


. . . . . << Copyright notice for rsct.compat.basic >> . . . . . . .
 Licensed Materials - Property of IBM

 5765F07AP
   (C) Copyright International Business Machines Corp. 1985, 2010.

 All rights reserved.
 US Government Users Restricted Rights - Use, duplication or disclosure
 restricted by GSA ADP Schedule Contract with IBM Corp.
. . . . . << End of copyright notice for rsct.compat.basic >>. . . .

Finished processing all filesets.  (Total time:  25 secs).

+-----------------------------------------------------------------------------+
                        Pre-commit Verification...
+-----------------------------------------------------------------------------+
Verifying requisites...done
Results...

SUCCESSES
---------
  Filesets listed in this section passed pre-commit verification
  and will be committed.

  Selected Filesets
  -----------------
  rsct.basic.rte 3.1.0.3                      # RSCT Basic Function

  Requisites
  ----------
  (being committed automatically as requisites of selected filesets)
  bos.rte.console 6.1.6.1                     # Console
  bos.rte.install 6.1.6.3                     # LPP Install Commands
  bos.rte.libc 6.1.6.3                        # libc Library
  bos.rte.net 6.1.5.0                         # Network
  bos.rte.security 6.1.6.3                    # Base Security Function
  bos.rte.serv_aid 6.1.6.3                    # Error Log Service Aids
  rsct.core.errm 3.1.0.2                      # RSCT Event Response Resource...
  rsct.core.fsrm 3.1.0.1                      # RSCT File System Resource Ma...
  rsct.core.hostrm 3.1.0.2                    # RSCT Host Resource Manager
  rsct.core.microsensor 3.1.0.3               # RSCT MicroSensor Resource Ma...
  rsct.core.rmc 3.1.0.3                       # RSCT Resource Monitoring and...
  rsct.core.sec 3.1.0.2                       # RSCT Security
  rsct.core.sensorrm 3.1.0.1                  # RSCT Sensor Resource Manager
  rsct.core.sr 3.1.0.2                        # RSCT Registry
  rsct.core.utils 3.1.0.3                     # RSCT Utilities

  << End of Success Section >>

+-----------------------------------------------------------------------------+
                          Committing Software...
+-----------------------------------------------------------------------------+

installp: COMMITTING software for:
        bos.rte.console 6.1.6.1

Filesets processed:  1 of 16  (Total time:  25 secs).

installp: COMMITTING software for:
        bos.rte.install 6.1.6.3

Filesets processed:  2 of 16  (Total time:  25 secs).

installp: COMMITTING software for:
        bos.rte.libc 6.1.6.3

Filesets processed:  3 of 16  (Total time:  26 secs).

installp: COMMITTING software for:
        bos.rte.serv_aid 6.1.6.3

Filesets processed:  4 of 16  (Total time:  26 secs).

installp: COMMITTING software for:
        bos.rte.net 6.1.5.0

Filesets processed:  5 of 16  (Total time:  26 secs).

installp: COMMITTING software for:
        bos.rte.security 6.1.6.3

Filesets processed:  6 of 16  (Total time:  27 secs).

installp: COMMITTING software for:
        rsct.core.utils 3.1.0.3

Filesets processed:  7 of 16  (Total time:  27 secs).

installp: COMMITTING software for:
        rsct.core.sec 3.1.0.2

Filesets processed:  8 of 16  (Total time:  27 secs).

installp: COMMITTING software for:
        rsct.core.sr 3.1.0.2

Filesets processed:  9 of 16  (Total time:  27 secs).

installp: COMMITTING software for:
        rsct.core.rmc 3.1.0.3

Filesets processed:  10 of 16  (Total time:  28 secs).

installp: COMMITTING software for:
        rsct.basic.rte 3.1.0.3

Filesets processed:  11 of 16  (Total time:  28 secs).

installp: COMMITTING software for:
        rsct.core.errm 3.1.0.2

Filesets processed:  12 of 16  (Total time:  28 secs).

installp: COMMITTING software for:
        rsct.core.fsrm 3.1.0.1

Filesets processed:  13 of 16  (Total time:  28 secs).

installp: COMMITTING software for:
        rsct.core.hostrm 3.1.0.2

Filesets processed:  14 of 16  (Total time:  28 secs).

installp: COMMITTING software for:
        rsct.core.microsensor 3.1.0.3

Filesets processed:  15 of 16  (Total time:  28 secs).

installp: COMMITTING software for:
        rsct.core.sensorrm 3.1.0.1

Finished processing all filesets.  (Total time:  28 secs).

Please wait...

        /usr/sbin/rsct/install/bin/ctposti
****************************************************************
NOTE on HACMP/ES
A PTF has been applied to RSCT daemons. cluster services must be
be recycled in order for the fixes to be activated for HACMP/ES
****************************************************************
0513-071 The ctrmc Subsystem has been added.
0513-059 The ctrmc Subsystem has been started. Subsystem PID is 3407944.
0513-059 The IBM.DRM Subsystem has been started. Subsystem PID is 14942378.
0513-059 The IBM.CSMAgentRM Subsystem has been started. Subsystem PID is 10289284.
0513-059 The IBM.ServiceRM Subsystem has been started. Subsystem PID is 13566080.
done
+-----------------------------------------------------------------------------+
                                Summaries:
+-----------------------------------------------------------------------------+

Pre-installation Failure/Warning Summary
----------------------------------------
Name                      Level           Pre-installation Failure/Warning
-------------------------------------------------------------------------------
rsct.compat.clients.rte   3.1.0.0         Already installed
rsct.basic.rte            3.1.0.1         To be superseded by 3.1.0.3


Installation Summary
--------------------
Name                        Level           Part        Event       Result
-------------------------------------------------------------------------------
rsct.basic.rte              3.1.0.0         USR         APPLY       SUCCESS  
rsct.basic.rte              3.1.0.0         ROOT        APPLY       SUCCESS  
rsct.basic.rte              3.1.0.3         USR         APPLY       SUCCESS  
rsct.basic.rte              3.1.0.3         ROOT        APPLY       SUCCESS  
rsct.compat.clients.hacmp   3.1.0.0         USR         APPLY       SUCCESS  
rsct.compat.basic.rte       3.1.0.0         USR         APPLY       SUCCESS  
rsct.compat.basic.rte       3.1.0.0         ROOT        APPLY       SUCCESS  
bos.rte.console             6.1.6.1         USR         COMMIT      SUCCESS  
bos.rte.console             6.1.6.1         ROOT        COMMIT      SUCCESS  
bos.rte.install             6.1.6.3         USR         COMMIT      SUCCESS  
bos.rte.install             6.1.6.3         ROOT        COMMIT      SUCCESS  
bos.rte.libc                6.1.6.3         USR         COMMIT      SUCCESS  
bos.rte.libc                6.1.6.3         ROOT        COMMIT      SUCCESS  
bos.rte.serv_aid            6.1.6.3         USR         COMMIT      SUCCESS  
bos.rte.serv_aid            6.1.6.3         ROOT        COMMIT      SUCCESS  
bos.rte.net                 6.1.5.0         USR         COMMIT      SUCCESS  
bos.rte.net                 6.1.5.0         ROOT        COMMIT      SUCCESS  
bos.rte.security            6.1.6.3         USR         COMMIT      SUCCESS  
bos.rte.security            6.1.6.3         ROOT        COMMIT      SUCCESS  
rsct.core.utils             3.1.0.3         USR         COMMIT      SUCCESS  
rsct.core.utils             3.1.0.3         ROOT        COMMIT      SUCCESS  
rsct.core.sec               3.1.0.2         USR         COMMIT      SUCCESS  
rsct.core.sec               3.1.0.2         ROOT        COMMIT      SUCCESS  
rsct.core.sr                3.1.0.2         USR         COMMIT      SUCCESS  
rsct.core.sr                3.1.0.2         ROOT        COMMIT      SUCCESS  
rsct.core.rmc               3.1.0.3         USR         COMMIT      SUCCESS  
rsct.core.rmc               3.1.0.3         ROOT        COMMIT      SUCCESS  
rsct.basic.rte              3.1.0.3         USR         COMMIT      SUCCESS  
rsct.basic.rte              3.1.0.3         ROOT        COMMIT      SUCCESS  
rsct.core.errm              3.1.0.2         USR         COMMIT      SUCCESS  
rsct.core.errm              3.1.0.2         ROOT        COMMIT      SUCCESS  
rsct.core.fsrm              3.1.0.1         USR         COMMIT      SUCCESS  
rsct.core.fsrm              3.1.0.1         ROOT        COMMIT      SUCCESS  
rsct.core.hostrm            3.1.0.2         USR         COMMIT      SUCCESS  
rsct.core.hostrm            3.1.0.2         ROOT        COMMIT      SUCCESS  
rsct.core.microsensor       3.1.0.3         USR         COMMIT      SUCCESS  
rsct.core.microsensor       3.1.0.3         ROOT        COMMIT      SUCCESS  
rsct.core.sensorrm          3.1.0.1         USR         COMMIT      SUCCESS  
rsct.core.sensorrm          3.1.0.1         ROOT        COMMIT      SUCCESS  
root@aixbox:/download/AIX/PTF/Aix-61-06-03#oslevel -s
6100-06-03-1048

Aix alt_disk_clone

Di seguito i passi eseguiti per clonare rootvg della lpar LPAR1 in occasione della migrazione da un P6-570 ad un P7-770.
Aggiungo un disco da 50GB (hdisk27) che ospiterà il rootvg della nuova partizione , sulla vecchia si chiamerà altinst_rootvg
al termine dell'operazione.

root@lpar1:/#lspv
hdisk0          00cff683554eac45                    rootvg          active
hdisk1          00cff683554eac7b                    rootvg          active
hdisk4          00cff683e9f9313f                    vgappl30           active
hdisk2          00cff68379f89cc7                    vgappl31           active
hdisk3          00cff68379f89dbe                    vgappl32           active
hdisk5          00cff68379f89e28                    vgappl33           active
hdisk6          00cff68379f89e74                    vgappl34           active
hdisk7          00cff68379f89eb4                    vgappl35           active
hdisk8          00cff68379f89ef9                    vgappl36           active
hdisk9          00cff68379f89f36                    vgappl30           active
hdisk10         00cff68379f89f7a                    vgappl31           active
hdisk11         00cff68379f89fbb                    vgappl32           active
hdisk12         00cff68379f89ffc                    vgappl33           active
hdisk13         00cff68379f8a046                    vgappl34           active
hdisk14         00cff68379f8a08b                    vgappl35           active
hdisk15         00cff68379f8a0d1                    vgappl36           active
hdisk16         00cff6837a2fb38a                    tempvg        active
hdisk17         00cff683ad734158                    tempvg        active
hdisk18         00cff6837b91c30d                    vgappl30           active
hdisk19         00cff683d38e1716                    swapvg          active
hdisk20         00cff6830a99978f                    vgappl30           active
hdisk21         00cff6830a999885                    vgappl31           active
hdisk22         00cff6830a9998f1                    vgappl32           active
hdisk23         00cff6830a999958                    vgappl33           active
hdisk24         00cff6830a9999c5                    vgappl34           active
hdisk25         00cff6830a999a4e                    vgappl35           active
hdisk26         00cff6830a999ace                    vgappl36           active
hdisk27         00cff6830915c025                    None            

Notare che se rootvg è mirrored l'operazione fallirà per mancanza di spazio; rimuovere mirror prima di procedere:

root@lpar1:/#unmirrorvg rootvg hdisk1
0516-1246 rmlvcopy: If hd5 is the boot logical volume, please run 'chpv -c '
        as root user to clear the boot record and avoid a potential boot
        off an old boot image that may reside on the disk from which this
        logical volume is moved/removed.
0516-1804 chvg: The quorum change takes effect immediately.
0516-1144 unmirrorvg: rootvg successfully unmirrored, user should perform
        bosboot of system to reinitialize boot records.  Then, user must modify
        bootlist to just include:  hdisk0.

Verifichiamo lo stato del mirror :

root@lpar1:/#lsvg -p rootvg
rootvg:
PV_NAME           PV STATE          TOTAL PPs   FREE PPs    FREE DISTRIBUTION
hdisk0            active            981         588         08..00..188..196..196
hdisk1            active            981         981         197..196..196..196..196

OK , adesso rimuovo hdisk1 da rootvg :

root@lpar1:/#reducevg rootvg hdisk1
root@lpar1:/#lsvg -p rootvg
rootvg:
PV_NAME           PV STATE          TOTAL PPs   FREE PPs    FREE DISTRIBUTION
hdisk0            active            981         588         08..00..188..196..196

Un altro problema che potrebbe impedire l'operazione è la presenza di LV con nomi di lunghezza superiore a 12 caratteri
visto che la procedura aggiungerà un prefisso al nome originale dei logical volumes.

root@lpar1:/#smitty alt_clone

Type or select values in entry fields.
Press Enter AFTER making all desired changes.

                                                        [Entry Fields]
* Target Disk(s) to install                          [hdisk27]                                                                                                          +
  Phase to execute                                    all                                                                                                               +
  image.data file                                    []                                                                                                                  /
  Exclude list                                       []                                                                                                                  /
  
  Bundle to install                                  []                                                                                                                 +
    -OR-
  Fileset(s) to install                              []
  
  Fix bundle to install                              []
    -OR-
  Fixes to install                                   []
  
  Directory or Device with images                    []
  (required if filesets, bundles or fixes used)
  
  installp Flags
  COMMIT software updates?                            yes                                                                                                               +
  SAVE replaced files?                                no                                                                                                                +
  AUTOMATICALLY install requisite software?           yes                                                                                                               +
  EXTEND file systems if space needed?                yes                                                                                                               +
  OVERWRITE same or newer versions?                   no                                                                                                                +
  VERIFY install and check file sizes?                no                                                                                                                +
  ACCEPT new license agreements?                      yes                                                                                                               +
  
  Customization script                               []                                                                                                                  /
  Set bootlist to boot from this disk
  on next reboot?                                     no                                                                                                                +
  Reboot when complete?                               no                                                                                                                +
  Verbose output?                                     yes                                                                                                               +
  Debug output?                                       no                                                                                                                +

Attenzione a non selezionare la modifica della bootlist e il reboot when complete .

Selezionando l'output verboso vedremo la lista dei files che vengono copiati nel nuovo disco , inutile.

Alla fine avremo :

root@lpar1:/#lspv 
hdisk0          00cff683554eac45                    rootvg          active
hdisk1          00cff683554eac7b                    None            
hdisk4          00cff683e9f9313f                    vgappl30           active
hdisk2          00cff68379f89cc7                    vgappl31           active
hdisk3          00cff68379f89dbe                    vgappl32           active
hdisk5          00cff68379f89e28                    vgappl33           active
hdisk6          00cff68379f89e74                    vgappl34           active
hdisk7          00cff68379f89eb4                    vgappl35           active
hdisk8          00cff68379f89ef9                    vgappl36           active
hdisk9          00cff68379f89f36                    vgappl30           active
hdisk10         00cff68379f89f7a                    vgappl31           active
hdisk11         00cff68379f89fbb                    vgappl32           active
hdisk12         00cff68379f89ffc                    vgappl33           active
hdisk13         00cff68379f8a046                    vgappl34           active
hdisk14         00cff68379f8a08b                    vgappl35           active
hdisk15         00cff68379f8a0d1                    vgappl36           active
hdisk16         00cff6837a2fb38a                    tempvg        active
hdisk17         00cff683ad734158                    tempvg        active
hdisk18         00cff6837b91c30d                    vgappl30           active
hdisk19         00cff683d38e1716                    swapvg          active
hdisk20         00cff6830a99978f                    vgappl30           active
hdisk21         00cff6830a999885                    vgappl31           active
hdisk22         00cff6830a9998f1                    vgappl32           active
hdisk23         00cff6830a999958                    vgappl33           active
hdisk24         00cff6830a9999c5                    vgappl34           active
hdisk25         00cff6830a999a4e                    vgappl35           active
hdisk26         00cff6830a999ace                    vgappl36           active
hdisk27         00cff6830915c025                    altinst_rootvg  

A questo punto abbiamo il nuovo rootvg (altinst_rootvg) , per accedervi dobbiamo usare il comando alt_rootvg_op.
Ad esempio possiamo "svegliare" il vg :

root@lpar1:/#alt_rootvg_op -W -d hdisk27
Waking up altinst_rootvg volume group ...

root@lpar1:/#lsvg -l altinst_rootvg
altinst_rootvg:
LV NAME             TYPE       LPs     PPs     PVs  LV STATE      MOUNT POINT
alt_hd5             boot       1       1       1    closed/syncd  N/A
alt_hd6             paging     16      16      1    closed/syncd  N/A
alt_hd8             jfs2log    1       1       1    open/syncd    N/A
alt_hd4             jfs2       8       8       1    open/syncd    /alt_inst
alt_hd2             jfs2       37      37      1    open/syncd    /alt_inst/usr
alt_hd9var          jfs2       16      16      1    open/syncd    /alt_inst/var
alt_hd3             jfs2       32      32      1    open/syncd    /alt_inst/tmp
alt_hd10opt         jfs2       64      64      1    open/syncd    /alt_inst/opt
alt_hd11admin       jfs2       2       2       1    open/syncd    /alt_inst/admin
alt_dumplv0         sysdump    64      64      1    closed/syncd  N/A
alt_livedump        jfs2       4       4       1    open/syncd    /alt_inst/var/adm/ras/livedump
alt_netbackup       jfs2       64      64      1    open/syncd    /alt_inst/opt/netbackup
alt_ocsinv          jfs2       2       2       1    open/syncd    /alt_inst/opt/ocsinventory
alt_nagios          jfs2       2       2       1    open/syncd    /alt_inst/opt/nagios
alt_logs            jfs2       80      80      1    open/syncd    /alt_inst/logs

e rimetterlo a dormire :

root@lpar1:/#alt_rootvg_op -S
Putting volume group altinst_rootvg to sleep ...
forced unmount of /alt_inst/var/adm/ras/livedump
forced unmount of /alt_inst/var/adm/ras/livedump
forced unmount of /alt_inst/var
forced unmount of /alt_inst/var
forced unmount of /alt_inst/usr
forced unmount of /alt_inst/usr
forced unmount of /alt_inst/tmp
forced unmount of /alt_inst/tmp
forced unmount of /alt_inst/opt/ocsinventory
forced unmount of /alt_inst/opt/ocsinventory
forced unmount of /alt_inst/opt/netbackup
forced unmount of /alt_inst/opt/netbackup
forced unmount of /alt_inst/opt/nagios
forced unmount of /alt_inst/opt/nagios
forced unmount of /alt_inst/opt
forced unmount of /alt_inst/opt
forced unmount of /alt_inst/logs
forced unmount of /alt_inst/logs
forced unmount of /alt_inst/admin
forced unmount of /alt_inst/admin
forced unmount of /alt_inst
forced unmount of /alt_inst
Fixing LV control blocks...
Fixing file system superblocks...

root@lpar1:/#lsvg 
rootvg
altinst_rootvg
vgappl30
vgappl31
vgappl32
vgappl33
vgappl34
vgappl35
vgappl36
stagevg
swapvg

root@lpar1:/#lsvg -l altinst_rootvg
0516-010 : Volume group must be varied on; use varyonvg command.

Ora non rimane che eliminare ogni traccia del vg e del disco dalla lpar per spostarlo sulla nuova.

root@lpar1:/#exportvg altinst_rootvg

root@lpar1:/#rmdev -dl hdisk27
hdisk27 deleted

Linux - Sostituzione LUN gestite da ASM

Situazione attuale:

[root@pobi02 ~]# sanlun lun show
controller(7mode)/ device host lun
vserver(Cmode) lun-pathname filename adapter protocol size mode
---------------------------------------------------------------------------------------------------------
fas3160b /vol/pobi02_data/pobi02_data_lun /dev/sdb host3 FCP 100g 7
fas3160b /vol/pobiX_share/pobiX_share_lun /dev/sdc host3 FCP 10g 7
fas3160b /vol/pobiX_share/pobiX_share_lun2 /dev/sdd host3 FCP 100g 7
fas3160b /vol/pobi02_data/pobi02_data_lun /dev/sde host3 FCP 100g 7
fas3160b /vol/pobiX_share/pobiX_share_lun /dev/sdf host3 FCP 10g 7
fas3160b /vol/pobiX_share/pobiX_share_lun2 /dev/sdg host3 FCP 100g 7
fas3160b /vol/pobi02_data/pobi02_data_lun /dev/sdh host3 FCP 100g 7
fas3160b /vol/pobiX_share/pobiX_share_lun /dev/sdi host3 FCP 10g 7
fas3160b /vol/pobiX_share/pobiX_share_lun2 /dev/sdj host3 FCP 100g 7
fas3160b /vol/pobi02_data/pobi02_data_lun /dev/sdk host3 FCP 100g 7
fas3160b /vol/pobiX_share/pobiX_share_lun /dev/sdl host3 FCP 10g 7
fas3160b /vol/pobiX_share/pobiX_share_lun2 /dev/sdm host3 FCP 100g 7
fas3160b /vol/pobi02_data/pobi02_data_lun /dev/sdn host4 FCP 100g 7
fas3160b /vol/pobiX_share/pobiX_share_lun /dev/sdo host4 FCP 10g 7
fas3160b /vol/pobiX_share/pobiX_share_lun2 /dev/sdp host4 FCP 100g 7
fas3160b /vol/pobi02_data/pobi02_data_lun /dev/sdq host4 FCP 100g 7
fas3160b /vol/pobiX_share/pobiX_share_lun /dev/sdr host4 FCP 10g 7
fas3160b /vol/pobiX_share/pobiX_share_lun2 /dev/sds host4 FCP 100g 7
fas3160b /vol/pobi02_data/pobi02_data_lun /dev/sdt host4 FCP 100g 7
fas3160b /vol/pobiX_share/pobiX_share_lun /dev/sdu host4 FCP 10g 7
fas3160b /vol/pobiX_share/pobiX_share_lun2 /dev/sdv host4 FCP 100g 7
fas3160b /vol/pobi02_data/pobi02_data_lun /dev/sdw host4 FCP 100g 7
fas3160b /vol/pobiX_share/pobiX_share_lun /dev/sdx host4 FCP 10g 7
fas3160b /vol/pobiX_share/pobiX_share_lun2 /dev/sdy host4 FCP 100g 7


Forzo un rescan delle hba , su entrambi i nodi ma un hba alla volta facendo attenzione ad attendere che il link della stessa torni online prima di lanciare il rescan sull'altro path. Posso verificare lo stato utilizzando SCLI :


[root@pobi01 ~]# scli
Scanning QLogic FC HBA(s) and device(s), please wait...
-
SANsurfer FC/CNA HBA CLI

v1.7.3 Build 32

Main Menu

1: General Information
2: HBA Information
3: HBA Parameters
4: Target/LUN List
5: iiDMA Settings
6: Boot Device
7: Utilities
8: Beacon
9: Diagnostics
10: Statistics
11: Virtual
12: FCoE
13: Help
14: Exit


Enter Selection: 4

SANsurfer FC/CNA HBA CLI

v1.7.3 Build 32

Target List Menu

HBA Model QMI8142
1: Port 1: WWPN: 21-00-00-C0-DD-1D-01-B1 Link Down
2: Port 2: WWPN: 21-00-00-C0-DD-1D-01-B3 Link Down
HBA Model QMI2572
3: Port 1: WWPN: 21-00-00-1B-32-9B-8E-4D Loop Down
4: Port 2: WWPN: 21-01-00-1B-32-BB-8E-4D Online
5: All HBAs
6: Return to Previous Menu



In questo caso è in corso il rescan sull' hba 3 , come si vede dallo stato LOOP DOWN.


echo "1" > /sys/class/fc_host/host4/issue_lip

...


echo "1" > /sys/class/fc_host/host3/issue_lip

Al termine della doppia operazione di rescan , otteniamo quanto segue:


[root@pobi01 ~]# sanlun lun show
controller(7mode)/ device host lun
vserver(Cmode) lun-pathname filename adapter protocol size mode
--------------------------------------------------------------------------------------------------------------------
netapp1 /vol/N1_pobiX_share/N1_pobiX_share_data_lun1 /dev/sdaw host3 FCP 100g 7
netapp1 /vol/N1_pobiX_share/N1_pobiX_share_data_lun0 /dev/sdav host3 FCP 10g 7
netapp1 /vol/N1_pobi01_data/N1_pobi01_data_lun0 /dev/sdau host3 FCP 100g 7
netapp1 /vol/N1_pobiX_share/N1_pobiX_share_data_lun1 /dev/sdat host3 FCP 100g 7
netapp1 /vol/N1_pobiX_share/N1_pobiX_share_data_lun0 /dev/sdas host3 FCP 10g 7
netapp1 /vol/N1_pobi01_data/N1_pobi01_data_lun0 /dev/sdar host3 FCP 100g 7
netapp1 /vol/N1_pobiX_share/N1_pobiX_share_data_lun1 /dev/sdaq host3 FCP 100g 7
netapp1 /vol/N1_pobiX_share/N1_pobiX_share_data_lun0 /dev/sdap host3 FCP 10g 7
netapp1 /vol/N1_pobi01_data/N1_pobi01_data_lun0 /dev/sdao host3 FCP 100g 7
netapp1 /vol/N1_pobiX_share/N1_pobiX_share_data_lun1 /dev/sdan host3 FCP 100g 7
netapp1 /vol/N1_pobiX_share/N1_pobiX_share_data_lun0 /dev/sdam host3 FCP 10g 7
netapp1 /vol/N1_pobi01_data/N1_pobi01_data_lun0 /dev/sdal host3 FCP 100g 7
netapp1 /vol/N1_pobiX_share/N1_pobiX_share_data_lun1 /dev/sdak host4 FCP 100g 7
netapp1 /vol/N1_pobi01_data/N1_pobi01_data_lun0 /dev/sdai host4 FCP 100g 7
netapp1 /vol/N1_pobiX_share/N1_pobiX_share_data_lun0 /dev/sdaj host4 FCP 10g 7
netapp1 /vol/N1_pobiX_share/N1_pobiX_share_data_lun1 /dev/sdah host4 FCP 100g 7
netapp1 /vol/N1_pobiX_share/N1_pobiX_share_data_lun0 /dev/sdag host4 FCP 10g 7
netapp1 /vol/N1_pobi01_data/N1_pobi01_data_lun0 /dev/sdaf host4 FCP 100g 7
netapp1 /vol/N1_pobiX_share/N1_pobiX_share_data_lun1 /dev/sdae host4 FCP 100g 7
netapp1 /vol/N1_pobiX_share/N1_pobiX_share_data_lun0 /dev/sdad host4 FCP 10g 7
netapp1 /vol/N1_pobi01_data/N1_pobi01_data_lun0 /dev/sdac host4 FCP 100g 7
netapp1 /vol/N1_pobiX_share/N1_pobiX_share_data_lun1 /dev/sdab host4 FCP 100g 7
netapp1 /vol/N1_pobiX_share/N1_pobiX_share_data_lun0 /dev/sdaa host4 FCP 10g 7
netapp1 /vol/N1_pobi01_data/N1_pobi01_data_lun0 /dev/sdz host4 FCP 100g 7
fas3160b /vol/pobiX_share/pobiX_share_lun2 /dev/sdy host4 FCP 100g 7
fas3160b /vol/pobiX_share/pobiX_share_lun /dev/sdx host4 FCP 10g 7
fas3160b /vol/pobi01_data/pobi01_data_lun /dev/sdw host4 FCP 100g 7
fas3160b /vol/pobiX_share/pobiX_share_lun2 /dev/sdv host3 FCP 100g 7
fas3160b /vol/pobiX_share/pobiX_share_lun2 /dev/sdu host4 FCP 100g 7
fas3160b /vol/pobiX_share/pobiX_share_lun /dev/sdt host3 FCP 10g 7
fas3160b /vol/pobiX_share/pobiX_share_lun /dev/sds host4 FCP 10g 7
fas3160b /vol/pobi01_data/pobi01_data_lun /dev/sdr host3 FCP 100g 7
fas3160b /vol/pobiX_share/pobiX_share_lun2 /dev/sdp host3 FCP 100g 7
fas3160b /vol/pobi01_data/pobi01_data_lun /dev/sdq host4 FCP 100g 7
fas3160b /vol/pobiX_share/pobiX_share_lun /dev/sdo host3 FCP 10g 7
fas3160b /vol/pobi01_data/pobi01_data_lun /dev/sdn host3 FCP 100g 7
fas3160b /vol/pobi01_data/pobi01_data_lun /dev/sdb host3 FCP 100g 7
fas3160b /vol/pobiX_share/pobiX_share_lun /dev/sdc host3 FCP 10g 7
fas3160b /vol/pobiX_share/pobiX_share_lun2 /dev/sdd host3 FCP 100g 7
fas3160b /vol/pobi01_data/pobi01_data_lun /dev/sde host3 FCP 100g 7
fas3160b /vol/pobiX_share/pobiX_share_lun /dev/sdf host3 FCP 10g 7
fas3160b /vol/pobiX_share/pobiX_share_lun2 /dev/sdg host3 FCP 100g 7
fas3160b /vol/pobi01_data/pobi01_data_lun /dev/sdh host4 FCP 100g 7
fas3160b /vol/pobiX_share/pobiX_share_lun /dev/sdi host4 FCP 10g 7
fas3160b /vol/pobiX_share/pobiX_share_lun2 /dev/sdj host4 FCP 100g 7
fas3160b /vol/pobi01_data/pobi01_data_lun /dev/sdk host4 FCP 100g 7
fas3160b /vol/pobiX_share/pobiX_share_lun /dev/sdl host4 FCP 10g 7
fas3160b /vol/pobiX_share/pobiX_share_lun2 /dev/sdm host4 FCP 100g 7

Verifichiamo nuovamente lo stato della HBA , mediante scli:


HBA Model QMI2572
3: Port 1: WWPN: 21-00-00-1B-32-9B-8E-4D Online
4: Port 2: WWPN: 21-01-00-1B-32-BB-8E-4D Online

Adesso la ridondanza del path è nuovamente garantita , perfetto.


- IDENTIFICAZIONE DELLE LUN MEDIANTE WWID

Otteniamo il wwid delle lun utilizzando scsi_id -gus


[root@pobi01 ~]# scsi_id -gus /block/sdau
360a980004176427a302443427a71316f
[root@pobi01 ~]# scsi_id -gus /block/sdav
360a980004176427a302443427a713171
[root@pobi01 ~]# scsi_id -gus /block/sdaw
360a980004176427a302443427a713173

che corrispondono a :


netapp1 /vol/N1_pobi01_data/N1_pobi01_data_lun0 /dev/sdau host3 FCP 100g (DISCO PRIVATO PER FS /u01)
netapp1 /vol/N1_pobiX_share/N1_pobiX_share_data_lun0 /dev/sdav host3 FCP 10g (DISCO ASM PER VOTING DISK)
netapp1 /vol/N1_pobiX_share/N1_pobiX_share_data_lun1 /dev/sdaw host3 FCP 100g (DISCO ASM PER FS ACFS)

Verifichiamo anche sull'altro nodo la coerenza dei wwid:


[root@pobi02 ~]# scsi_id -gus /block/sdau
360a9800041764752752b434151713942
[root@pobi02 ~]# scsi_id -gus /block/sdav
360a980004176427a302443427a713171
[root@pobi02 ~]# scsi_id -gus /block/sdaw
360a980004176427a302443427a713173

Ovviamente il primo disco è diverso , quindi lo è anche il wwid (!) . I rimanenti coincidono essendo le shared lun.

Modifico il file multipath.conf su entrambi i nodi , salvandone copia e lo edito aggiungendo le sezioni relative ai nuovi dischi :


cp multipath.conf multipath.conf.20130508.old

multipath {
wwid 360a980004176427a302443427a713171
alias asm_vote_0
path_grouping_policy group_by_prio
path_checker readsector0
path_selector "round-robin 0"
failback immediate
polling_interval 10
no_path_retry 2
mode 0660
uid 290
gid 290
}
multipath {
wwid 360a980004176427a302443427a713173
alias asm_acfs_0
path_grouping_policy group_by_prio
path_checker readsector0
path_selector "round-robin 0"
failback immediate
polling_interval 10
no_path_retry 2
mode 0660
uid 290
gid 290
}

Salviamo e riavviamo il servizio multipathd su entrambi i nodi


[root@pobi01 etc]# service multipathd restart
Stopping multipathd daemon: [ OK ]
Starting multipathd daemon: [ OK ]


E verifichiamo i nomi assegnati dal device mapper ai dischi che ci interessano.


[root@pobi01 etc]# multipath -l
mpath1 (360a980004176427a302443427a71316f) dm-16 NETAPP,LUN
[size=100G][features=1 queue_if_no_path][hwhandler=0][rw]
...
...
asm_acfs_0 (360a980004176427a302443427a713173) dm-18 NETAPP,LUN
[size=100G][features=1 queue_if_no_path][hwhandler=0][rw]
...
...
asm_vote_0 (360a980004176427a302443427a713171) dm-17 NETAPP,LUN
[size=10G][features=1 queue_if_no_path][hwhandler=0][rw]
...
...

- SOSTITUZIONE DEL DISCO PRIVATO CHE OSPITA IL FS /u01

Iniziamo sostituendo il disco fuori dal controllo di ASM , ovvero il disco che ospita il fs /u01 ; nel nostro caso il device interessato è mpath1.


[root@pobi01 etc]# pvcreate /dev/mapper/mpath1
Physical volume "/dev/mapper/mpath1" successfully created


Verifichiamo le caratteristiche del vg che contiene il disco da sostituire ,cioè vg_obi :


[root@pobi01 etc]# vgdisplay --verbose vg_obi
Using volume group(s) on command line
Finding volume group "vg_obi"
--- Volume group ---
VG Name vg_obi
System ID
Format lvm2
Metadata Areas 1
Metadata Sequence No 2
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 1
Open LV 1
Max PV 0
Cur PV 1
Act PV 1
VG Size 100.00 GB
PE Size 4.00 MB
Total PE 25599
Alloc PE / Size 25344 / 99.00 GB
Free PE / Size 255 / 1020.00 MB
VG UUID pZ01Vb-54j0-MAAc-7cef-n9xI-oa36-LCaLsh

--- Logical volume ---
LV Name /dev/vg_obi/lv_u01
VG Name vg_obi
LV UUID HI5rYX-2fwS-1uq9-7c2c-rPkZ-33yU-MyQoRX
LV Write Access read/write
LV Status available
# open 1
LV Size 99.00 GB
Current LE 25344
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:15

--- Physical volumes ---
PV Name /dev/mpath/360a98000486e64376334696c6f487550
PV UUID cmhntD-hM2t-MezU-4ELc-exV5-omhR-hRW3px
PV Status allocatable
Total PE / Free PE 25599 / 255

e notiamo che contiene un solo pv il cui wwid corrisponde con



mpath0 (360a98000486e64376334696c6f487550) dm-12 NETAPP,LUN
[size=100G][features=1 queue_if_no_path][hwhandler=0][rw]

quindi aggiungiamo il nuovo pv al vg


[root@pobi01 etc]# vgextend vg_obi /dev/mapper/mpath1
Volume group "vg_obi" successfully extended

ed eseguo PVMOVE per migrare il contenuto del vecchio pv nel nuovo:


[root@pobi01 etc]# pvmove /dev/mpath/360a98000486e64376334696c6f487550 /dev/mpath/mpath1
/dev/mpath/360a98000486e64376334696c6f487550: Moved: 0.1%
/dev/mpath/360a98000486e64376334696c6f487550: Moved: 1.8%
/dev/mpath/360a98000486e64376334696c6f487550: Moved: 3.6%
...
...
/dev/mpath/360a98000486e64376334696c6f487550: Moved: 98.3%
/dev/mpath/360a98000486e64376334696c6f487550: Moved: 99.6%
/dev/mpath/360a98000486e64376334696c6f487550: Moved: 100.0%
[root@pobi01 etc]#

Verifichiamo che il vecchio PV non abbia PE usati


--- Physical volumes ---
PV Name /dev/mpath/360a98000486e64376334696c6f487550
PV UUID cmhntD-hM2t-MezU-4ELc-exV5-omhR-hRW3px
PV Status allocatable
Total PE / Free PE 25599 / 25599

PV Name /dev/mpath/mpath1
PV UUID fgUfVg-8iAD-fmlO-9D6J-j5XP-APB6-S48H0R
PV Status allocatable
Total PE / Free PE 25599 / 255


e procediamo con la reducevg


[root@pobi01 etc]# vgreduce vg_obi /dev/mpath/360a98000486e64376334696c6f487550
Removed "/dev/mpath/360a98000486e64376334696c6f487550" from volume group "vg_obi"


SOSTITUZIONE DISCHI ACFS

verifichiamo le presenza dei block device sotto /dev/mapper

[root@pobi02 mapper]# ls -la
total 0
drwxr-xr-x 2 root root 440 May 9 08:45 .
drwxr-xr-x 15 root root 5720 May 9 08:45 ..
brw-rw---- 1 root disk 253, 18 May 8 15:49 asm_acfs_0
brw-rw---- 1 grid asmadmin 253, 14 Apr 24 14:54 asm_acfs_1
brw-rw---- 1 root disk 253, 17 May 8 15:49 asm_vote_0
brw-rw---- 1 grid asmadmin 253, 13 May 9 08:45 asm_vote_1 ...


Modifichamo l'ownership dei nuovi device

[root@pobi02 mapper]# chown grid.asmadmin /dev/mapper/asm_acfs_0
[root@pobi02 mapper]# chown grid.asmadmin /dev/mapper/asm_vote_0
[root@pobi02 mapper]# ls -la
total 0
drwxr-xr-x 2 root root 440 May 9 08:45 .
drwxr-xr-x 15 root root 5720 May 9 08:45 ..
brw-rw---- 1 grid asmadmin 253, 18 May 8 15:49 asm_acfs_0
brw-rw---- 1 grid asmadmin 253, 14 Apr 24 14:54 asm_acfs_1
brw-rw---- 1 grid asmadmin 253, 17 May 8 15:49 asm_vote_0
brw-rw---- 1 grid asmadmin 253, 13 May 9 08:48 asm_vote_1


E' tutto pronto per configurare i nuovi dischi ed aggiungere nei dg

Verifico la lista di xauth [root@pobi01 etc]# xauth list pobi01/unix:11 MIT-MAGIC-COOKIE-1 4a0344ce5352618d2c37575c4710dcec

divento utente grid

[root@pobi01 etc]# su - grid
[grid@pobi01 ~]$ export DISPLAY=localhost:11.0
[grid@pobi01 ~]$ xauth add pobi01/unix:11 MIT-MAGIC-COOKIE-1 4a0344ce5352618d2c37575c4710dcec

lancio ASMCA per configurare i dg

[grid@pobi01 ~]$ asmca


AsmSostDsk1.png


Seleziono il VOTEDG e con tasto destro mi si apre un menu; seleziono Add disks


AsmSostDsk2.png


Seleziono il disco da aggiungere


AsmSostDsk3.png


Aggiunta completata


AsmSostDsk5.png


Seleziono il ACFSDG e con tasto destro mi si apre un menu; seleziono Add disks


AsmSostDsk6.png


AsmSostDsk7.png


Aggiunta completata , i disk groups devono ribilanciarsi con i nuovi dischi. Quando siamo certi che non vi sono attività di rebalance in corso , procediamo con la drop dei vecchi dischi dai dg . Posso verificare il progresso dell'attività di rebalancing con le seguenti istruzioni sql:


[grid@pobi02 ~]$ export ORACLE_SID=+ASM2
[grid@pobi02 ~]$ sqlplus / as sysasm

SQL*Plus: Release 11.2.0.3.0 Production on Thu May 9 09:10:54 2013

Copyright (c) 1982, 2011, Oracle. All rights reserved.


Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Real Application Clusters and Automatic Storage Management options

SQL> select * from gv$asm_operation;

INST_ID GROUP_NUMBER OPERA STAT POWER ACTUAL SOFAR EST_WORK EST_RATE EST_MINUTES ERROR_CODE
---------- ------------ ----- ---- ---------- ---------- ---------- ---------- ---------- ----------- --------------------------------------------
2 1 REBAL WAIT 1
1 1 REBAL RUN 1 1 48045 50726 9027 0



SQL> r
1 select * from gv$asm_operation
2*

no rows selected

SQL> quit
Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Real Application Clusters and Automatic Storage Management options



Ora procedo con la drop dei vecchi dischi , seleziono VOTEDG con il tasto destro e scelgo Drop disks


AsmSostDsk8.png


Seleziono il disco da rimuovere dal dg


AsmSostDsk9.png


Rimozione completata , ripetiamo l'operazione con l'altro DG .


AsmSostDsk10.png

AsmSostDsk11.png


Rimozione completata




Per completare l'attività è necessario :

eliminare le voci dei vecchi dischi dal file multipath.conf ;

eliminare il pv vecchio per rimuovere I metadati lvm dal disco: [root@pobi01 etc]# pvs

PV VG Fmt Attr PSize PFree
/dev/mpath/360a98000486e64376334696c6f487550 lvm2 a- 100.00G 100.00G
/dev/mpath/mpath1 vg_obi lvm2 a- 100.00G 1020.00M
/dev/sda2 vg_root lvm2 a- 135.78G 79.53G



[root@pobi01 etc]# pvremove /dev/mpath/360a98000486e64376334696c6f487550

Labels on physical volume "/dev/mpath/360a98000486e64376334696c6f487550" successfully wiped

e rimuovere Il multipathed device: [root@pobi01 etc]# multipath -f mpath0

rimuovere i singoli device, ad esempio ne ottengo la lista e costruisco un ciclo:


for x in b c d e f g h i j k l m n o p q r s t u v w x y
do
echo 1 > /sys/block/sd$x/device/delete
done

infine riavviare il servizio multipathd.

SEA Failover definition in dual vios setup

Scenario , ambiente dual vios su cui vogliamo costruire una shared ethernet adapter con failover e vlan multiple.
Su entrambi I vios definire due virtual adapters su cui verranno configurate le vlan necessarie , in questo caso la 1 per la rete di produzione e la 606 per la management . E' necessario attivare il 802.1q per poter assegnare vlan multiple all'adapter. Sul primo vios della coppia assegnamo anche trunk priority uguale a 1 .


 


 Sul secondo vio replichiamo la stessa configurazione con però trunk priority uguale a 2.


 


 A questo punto configuriamo I due virtual adapter che costituiranno il control channel per il failover della SEA . In questo caso utilizziamo un vlanid non usato , ad es . 999 , senza settare 802.1q e il
bridging.


 


Definiamo infine la SEA :

mkvdev -sea ent2 -vadapter ent3 -default ent3 -defaultid 1 -attr ha_mode=auto ctl_chan=ent4
ent5 Available
en5
et5

 dove ent2 è la fisica , nel nostro caso un etherchannel costruito su due fisiche;
 ent3 è il vadapter che conosce le vlan di prod e mgmt ;
 defaultid = il vlanid di default ; ctl_chan = il vadapter sulla vlan 999 ;

 Configuriamo l'ip address sulla sea oppure aggiungiamo un ulteriore vadapter per rimanere indipendenti dalla SEA e non perdere connettività in caso di manutenzione. 

mkvdev -vlan ent5 -tagid 606
 ent6 Available
en6
et6

 e assegnamo l'ip address al nuovo adapter

 mktcpip -hostname viosXX1 -inetaddr XX.XX.XX.XX -interface en5 -netmask 255.255.255.0 -gateway XX.XX.XX.XX mktcpip -hostname viosXX2 -inetaddr XX.XX.XX.XX -interface en5 -netmask 255.255.255.0 -gateway XX.XX.XX.XX