We are looking at running MPIO for it's redundancy and load balancing benefits. Does anyone know what pieces of software or modules are needed on the VIO server to get load balancing to work. Remember we are using EMC's DMX3500 storage system. We no longer want to use Powerpath. :rolleyes: ... (2 Replies)
Hi All,
The path requires me to go Single User mode. On single user mode, the patch still won't continue:
dhcpagent supports a new keyword in /etc/default/dhcpagent.
Please merge the existing /etc/default/dhcpagent with the
patched version of /etc/default/dhcpagent shipped with this... (2 Replies)
Hi folks,
does anybody have a link to a documentation how to implement native MPIO on AIX? We are using EMC PowerPath and Datacore SanSymphony/Cambex for this so far and I wasn't able to find a good description on that topic. All I know so far is that mkpath, chpath and lspath are used to... (3 Replies)
Hello All,
After creating lpp_source/spot from AIX 5.3TL6-07 DVD on the NIM(AIX6.1), I went online and download the fix pack for reaching TL8-04. (it was less than 200Mgegs total)
then I did define a newer lpp_source530TL8-04 via a copy from the older lpp_source530TL6-07 (I diduse a command... (2 Replies)
On a particular LPAR, I was running AIX 5.3 TL 3. On Monday I did an update of the LPAR to 5.3 TL 9 SP2. The install was smooth, but then I ran into a problem.
The MPIO driver does not work with LSI's StoreAge (SVM4). I did some looking, and looks like
5.3 TL3 = IBM.MPIO 5.3.0.30
5.3... (0 Replies)
Hi,
we have a vew boxes using MPIO and they are connected to some virtualization software managing some disk subsystems, offering volumes to the AIX boxes.
Sometimes when a cable has been plugged out for a test or when a real problem occurs, using lspath to show the state of the paths shows... (8 Replies)
Hello,
we are planning to deploy some of our databases on AIX/LPAR based servers (we didn't bought it yet ...). IBM's engineers says that if we want to boot them from SAN the hardware array has to be compatible with MPIO but they don't want to deliver any document with list of arrays supported... (5 Replies)
This is getting very confusing for me, and appreciate if someone can help.
Platform: Power VM ( Virtual I/O Server)
ioslevel 2.1.3.10-FP23
# oslevel -s
6100-05-00-0000
Storage: IBM DS4300
Two HBAs - Dual Port Fibre Adapter Channels
Each card has two ports , so a total of 4 ports going... (3 Replies)
Hello,
I have some concerns over the disk management of my AIX system.
For example server1
/ > lspv
hdisk0 00fa6d1288c820aa rootvg active
hdisk1 00fa6d1288c8213c vg_2 active
hdisk2 00c1cc14d6de272b ... (6 Replies)
Hello,
I have encountered the issue on my AIX 6.1. As you can see below, the hdisk1 & hdisk8 are not recognized by the system
/ > lspv
hdisk0 00fa6d1288c820aa rootvg active
hdisk1 00fa6d1288c8213c None
hdisk2 ... (9 Replies)
Discussion started by: Phat
9 Replies
LEARN ABOUT ULTRIX
kits
kits(1) General Commands Manual kits(1)Name
kits - generate setld format distribution kits
Syntax
/usr/sys/dist/kits key-file input-path output-path [ subset... ]
Description
The command produces subset images, inventories, and control files for an installation using the command. You need to know the key file
which describes the product to be built, a hierarchy from which the component files to be kitted are to be taken, and a destination direc-
tory into which the kit information is to be placed.
The command produces a subset image and a .image file in the output-path directory for each subset. In the instctrl subdirectory of output-
path, produces an inventory file and a control file. Any subset control program for the subset is transferred to output-path/instctrl. An
instctrl directory is created if none existed.
Arguments
key-file The path name of the manufacturing key file which describes the product to be kitted. Unless optional subset arguments are
specified, all subsets listed in the descriptor section of the key-file are kitted.
input-path The path name which specifies the top of a hierarchy of files. This hierarchy contains the files which are to be kitted into
subsets.
output-path The name of the directory to be used to store the subset image and data files produced by the command.
subset... The names of individual subsets can be specified by optionally listing them on the command line. If they are specified, only
those subsets will be kitted. The program assumes that all other subsets for the product have been kitted and that their
images are in the directory specified by output-path. The key file specified must contain descriptors for each of the
optional named subsets.
Restrictions
Any subset control programs to be provided with the kit must be located in a directory scps in the working directory where the program is
invoked. If no subset control program is found for a subset, an empty one is created.
Examples
The following example shows the command used to produce a kit using key file ULT400.k in the current directory to package files from the
hierarchy /var/kits/input and place the results in /var/kits/output.
kits ULT400.k /var/kits/input /var/kits/output
The next example shows the same usage, but specifies that only the ULTACCT400 subset is to be created.
kits ULT400.k /var/kits/input /var/kits/output ULTACCT400
Diagnostics
kits: key-file not found
The program was unable to find the key-file specified on the command line.
kits: input-path not found
The program was unable to find the specified input-path.
kits: output-path not found
The program was unable to find the specified output-path.
kits: cannot create instctrl directory.
The program cannot create an instctrl directory under output-path. Check that the user has write permission to output-path.
kits: key-file format error
One of the NAME, CODE, VERS, MI or ROOT values in the specified key-file is either missing or has a null value.
Inventory file pathname not found
The master inventory file pathname specified in the MI entry of the key-file cannot be found. Verify that the pathname is accessible from
the current directory.
Generating media creation information...failed.
There are no records in the master inventory file for a subset which is being kitted. Check the master inventory file for correctness of
content and format.
No such subset in key-file subset subset
A subset name specified on the command line does not have a descriptor line in the key-file. Check the spelling of the subset name on the
command line. Check the contents of the key-file.
compression failed. status = status
The compression option was specified in the key-file and an attempt to compress a subset failed. This should not happen. Run the program
once more.
Files
temporary files.
log of subset packaging activity
See Alsoinvcutter(1), tarsets(1), stl_comp(5), stl_ctrl(5), stl_image(5), stl_key(5), stl_mi(5), stl_scp(5), setld(8)
Guide to Preparing Software for Distribution on ULTRIX Systems
kits(1)