HP-UX Containers (SRP) A.03.01 Administrator's Guide
48
preview
Checks whether this system will accept the exchange file for import. If you
specify the preview option, only import validation is performed.
exchange_file
Specifies the existing exchange file name. The srp –export command
creates the exchange file.
The default is srp.exchange.
variable=value
The most commonly used variables for the import operation are as follows:
• iface
The primary network interface name, that is a name without a colon
such as lan0, on which to assign the imported IP address of the
container. Imported IPv4 nework interfaces will be assigned a
secondary interface name, for example lan0:1, if the primary is
already configured in the /etc/rc.config.d/netconf file.
• ip_address, ip_mask, iface, gw_ip_address, and
assign_ip
When the container name is different from the
name in the exchange file, you must provide the network
configuration for the new container.
• runlevel
The default run level for the container’s /etc/inittab file. When
a container is copied with a new name, it is by default configured to
start at run-level 2 which causes the container to start with minimal
services. You should reconfigure the services in the new container,
as needed, and then update the run-level in the container’s
/etc/inittab file to the desired value. If the container is not
imported with a new name, the default value for the run level is3.
• workload containers: allow_sw_mismatch
Set to yes to force an import operation to succeed if the required
products for the container are not present or if there is a software
version mismatch from the source to the target system. The default is
no.
You can use the following notation to assign a value to a variable:
name=value, name='value', or name="value"
6.9.3 Best practices for exporting and importing a container
To simplify the export and import of a container across systems, HP recommends you to keep the
properties of containers atomic by not sharing files and data with other containers unnecessarily. The
following are the best practices for using the srp –export and srp -import commands:
• Maintain consistent OS versions and patch levels across systems
System containers require consistent OS versions and patch levels across the systems where a
container is being cloned. For workload containers, HP-UX Containers have minimal
requirements for OS levels and patches to be synchronized across systems, applications
utilized within the containers may have more specific requirements. By maintaining
consistency across systems, you will not have to manually track application dependencies