vios installios

Under Construction

LPAR-Tool > User Guide > The vios Command

Available: from 1.9.2

Using the “vios installios” command, a virtual I/O server can be installed via an HMC:

 vios [-h <hmc>] [-m <ms>] [-p <profile>] installios [-C] [-N] [-v] <vios> [<ip> [<netmask> [<gateway> [<path>]]]] <attribute> ...
   -C : cache label name and installation image for later use
   -N : do not configure the network on the client after installation

The installation is not interactive! Therefore, all necessary information for the installation must be specified on the command line in the form of attributes.

At least the following information must be provided:

- IP address for the virtual I/O server
- Netmask to be used
- Default Gateway
- Installation Source

This information can be specified directly as command line arguments in the order listed above, or alternatively in the form of attributes. The following attributes are supported:

addr              - the IP address or hostname of the VIOS
netmask           - the netmask of the VIOS (required)
gateway           - the default gateway for the VIOS (required)
path              - the path to an installation image (required)
bosisnt_pvid      - the PVID of the LUN to use for installation
interface         - the interface to use on the HMC for the installation
mac_addr          - the MAC address of the VIOS interface
nfs_options       - the mount option to use for NFS (e.g. vers=4)
dest_dir          - directory where to copy the source, default is /extra filesystem
label             - label name to use instead of 'default1'
language          - language the license agreement will be displayed
speed             - the speed wo configure the client's network interface
                    10, 100 (default), 1000, auto
duplex            - the duplex setting to configure the client network interface
                    half, full (default), auto
vlan_tag          - the VLAN tag id to use for the client network interface
vlan_priority     - the VLAN tag priority to use
bootp_retry_count - maximum number of BOOTP retries (0-9)
tftp_retry_count  - maximum number of TFTP retries (0-9)

The following calls are equivalent:

$ vios installios vio1 10.255.255.59 255.255.255.0 10.255.255.1 VIOS_4.1.0.0
$ vios installios vio1 10.255.255.59 255.255.255.0 10.255.255.1 path=VIOS_4.1.0.0
$ vios installios vio1 10.255.255.59 255.255.255.0 gateway=10.255.255.1 path=VIOS_4.1.0.0
$ vios installios vio1 10.255.255.59 netmask=255.255.255.0 gateway=10.255.255.1 path=VIOS_4.1.0.0
$ vios installios vio1 addr=10.255.255.59 netmask=255.255.255.0 gateway=10.255.255.1 path=VIOS_4.1.0.0

Als Installations Quelle kann entweder ein Installations Image (ISO) oder ein Fullback (NIM Ressource) angegeben werden.

The installation images available for a virtual I/O server can be displayed with “vios lsviosimg” or “hmc lsviosimg“. It is sufficient to enter the name of the image as the path. In dual-HMC configurations, both HMCs are automatically searched for the specified image and the corresponding HMC is selected.

Using “vios lsviosbk” or “hmc lsviosbk”, the available backups can be shown. Here too, it is sufficient to specify the name.

However, an absolute path can also be specified for an image or backup to be used. If a backup is available on an NFS server, server:/absolute/path can also be specified as the path. The specified share must be accessible for the HMC!

Below are some examples for a virtual I/O server named “vio1“, with IP address 10.255.255.59, netmask 255.255.255.0 and gateway 10.255.255.57.

Example 1: The Virtual I/O Server should be installed with the installation image VIOS_4.1.0.0. The image is already available on one of the HMCs:

$ vios installios vio1 10.255.255.59 255.255.255.0 10.255.255.57 VIOS_4.1.0.0
Logging session output to /tmp/installios.415053.log.

Retrieving information for available network adapters
This will take several minutes...

Example 2: The fullback nim_resources.tar of the virtual I/O server vio1 should be installed on it (restore). The fullback is stored on one of the HMCs:

$ vios installios vio1 10.255.255.59 255.255.255.0 10.255.255.57 nim_resources.tar
Logging session output to /tmp/installios.418403.log.

Retrieving information for available network adapters
This will take several minutes...

Example 3: The fullback nim_resources.tar stored on the NFS server aixnim (10.255.255.57) in the directory /export/vios/vio1 is to be installed on the virtual I/O server vio1. The directory /export/vios/vios1 is exported for the HMC(s):

$ vios installios vio1 10.255.255.59 255.255.255.0 10.255.255.57 10.255.255.57:/export/test/nim_resources.tar
Logging session output to /tmp/installios.421750.log.

Retrieving information for available network adapters
This will take several minutes...