Sponsored Content
Full Discussion: VIOS LPAR Error 0518
Operating Systems AIX VIOS LPAR Error 0518 Post 302746835 by MichaelFelt on Thursday 20th of December 2012 05:06:19 AM
Old 12-20-2012
My guess is that AIX 5.3 DVD image does not support the system you are trying to install AIX 5.3 on. AIX 5.3 can be installed on most Power7, and certainly Power6, Power5, and Power4, etc..

If you have a nim server I would suggest creating nim installation resources from the DVD - first the LPP and then update to latest service pack, and then create the SPOT.

If you do not have a nim server I recommend making one. There is an example on unix.com and one I wrote and published elsewhere (I have been asked not to put up links to my old articles so you will have to search for it IF you want to compare.) Anyway, once you have the nim server: use recommendation above.
This User Gave Thanks to MichaelFelt For This Post:
 

10 More Discussions You Might Find Interesting

1. AIX

Problem mapping LUN disk from VIOS to the LPAR

Hello guys, It would be so nice of you if someone can provide me with these informations. 1) My SAN group assigned 51G of LUN space to the VIO server.I ran cfgdev to discover the newly added LUN. Unfortunately most of the disks that are in VIO server is 51G. How would I know which is the newly... (3 Replies)
Discussion started by: solaix14
3 Replies

2. AIX

DUAL VIOS & Client LPAR hangs at 25b3

I have a DUAL VIO ( IBM Virtual I/O ) setup on p 570. Two Vio server ( VIOS ) and many LPAR clients. VIO ( latest version + service pack + applied the fix ) and AIX 6.1 ML2 When both VIOs are running, and if I turn on a Client LPAR, the LPAR hangs at LED 25b3 for more than 1 hour then it... (2 Replies)
Discussion started by: filosophizer
2 Replies

3. AIX

VIOS to lpar Mapping

Hello, I have created mapping of 2 virtual adapters for Lpars using following command: mkvdev -vdev ipanalyzerlv1 -vadapter vhost11 mkvdev -vdev ipanalyzerlv -vadapter vhost13 The above two commands were succesfull but when I want to map the third virtual device to the same Lpar than... (3 Replies)
Discussion started by: Vit0_Corleone
3 Replies

4. AIX

LPAR freezes after switching of storage (lpar is mirrored)

Hi all, I have the following configuration 2 ds3524 storage disk systems located over 2 locations 2 P720 server located over 2 locations DS3524 are connected to san switch. Each vio server has 1 fc adapter attached to a san switch. per p720 server 2 virtual io servers. Vio 1 has 1 lun... (2 Replies)
Discussion started by: markiemark
2 Replies

5. AIX

What's the difference between VIOS and LPAR?

Hi All, Besides the licenses on VIO and LPAR. What's the main difference with the two? I have installed VIO, my manager told me so, because it's like a free hypervisor but I never installed LPAR before. How do you install it? And if you can give more info on the two, that would be great. ... (5 Replies)
Discussion started by: itik
5 Replies

6. AIX

VIOS IP address - separate vlan for vios servers ?

Hello, Lets say for simplicity that I do not use any vlan config inside my server - one lpar group use hea physical port1, another group hea physical port2. Physical port1 configured as vlan1 on external switch, physical port2 as vlan2. What is the common practice - should I isolate my vios... (0 Replies)
Discussion started by: vilius
0 Replies

7. AIX

List LPAR from VIOS

Hi guys, does anyone know how to get a list of the LPAR running on VIOS? Thanks! (5 Replies)
Discussion started by: cecco16
5 Replies

8. AIX

Moving VIOS, LPAR's, HMC to different subnet

Hi, Just joined to new company with one Power 720 Express (8202-E4C) server and have no much experience with IBM systems. I am trying to move everything I mentioned to different subnet as required by customer contract (currently sitting on same subnet as company lan). Access to this subnet will... (8 Replies)
Discussion started by: spricer
8 Replies

9. AIX

VIOS: Extend virtual disk assigned to running lpar?

Hello, VIOS 2.2.1.4 using IVM. I'm trying to extend a virtual disk assigned to a running lpar so that I can expand the lpar's datavg and grow some filesystems for the user. Storage admin expanded the lun and new size was reflected in VIO right away. I then needed the storage pool to... (2 Replies)
Discussion started by: j_aix
2 Replies

10. UNIX for Advanced & Expert Users

Unable to install client AIX LPAR to vscsi hdisk provided from VIOS

Hi everybody, I have Power5 server with 4 internal hdisks each of 70Gb. VIOS server was installed via Virtual I/O Server Image Repository on the HMC. HMC release - 7.7.0 VIOS rootvg installed on 2 disk(these disks merged to one storage pool during VIOS install process),and 2 others hdisks... (2 Replies)
Discussion started by: Ravil Khalilov
2 Replies
re-preinstall(1M)					  System Administration Commands					 re-preinstall(1M)

NAME
re-preinstall - installs the JumpStart software on a system SYNOPSIS
cdrom-mnt-pt/Solaris_XX/Tools/Boot/usr/sbin/install.d/re-preinstall [-m Solaris_boot_dir] [-k platform_name] target-slice DESCRIPTION
re-preinstall installs the JumpStart software (preinstall boot image) on a system, so you can power-on the system and have it automatically install the Solaris software (perform a JumpStart installation on the system). When you turn on a re-preinstalled system, the system looks for the JumpStart software on the system's default boot disk. All new SPARC systems have the JumpStart software already preinstalled. The XX in Solaris_XX is the version number of the Solaris release being used. You can use the re-preinstall command in several ways. The most common way is to run re-preinstall on a system to install the JumpStart software on its own default boot disk. This is useful if you want to restore a system to its original factory conditions. (See the first procedure described in EXAMPLES.) You can also run re-preinstall on a system to install JumpStart software on any attached disk (non-boot disk). After you install the Jump- Start software on a disk, you can move the disk to a different system and perform a JumpStart installation on the different system. (See the second procedure described in EXAMPLES.) re-preinstall creates a standard file system on the specified target-slice (usually slice 0), and re-preinstall makes sure there is enough space on the target-slice for the JumpStart software. If sufficient space is not available, re-preinstall fails with the following message: re-preinstall: target-slice too small xx Megabytes required You can use the format(1M) command to create sufficient space on the target-slice for the JumpStart software. OPTIONS
The following options are supported: -k platform_name Platform name of the system that will use the disk with the JumpStart software. The default is the platform name of the system running re-preinstall. (Use the uname(1) command (-i option) to determine a system's platform name.) -m Solaris_boot_dir Absolute path to the Solaris_XX/Tools/Boot subdirectory of a mounted Solaris CD or a Solaris CD copied to disk that re-preinstall uses to install the JumpStart software. The default is root (/), which is where the Solaris CD is mounted in single-user mode. OPERANDS
The following operands are supported: target-slice Device name of the disk slice where the JumpStart software will be installed (usually slice 0), for example, c0t3d0s0. EXAMPLES
Example 1: Installing the JumpStart Software on a System's Own Default Boot Disk The following procedure installs the JumpStart software on a system's own default boot disk: 1. From the ok prompt, boot the system from the Solaris media CD or DVD in single-user mode: ok boot cdrom -s 2. The following command installs the Jumpstart software on the System default boot disk, c0t0d0s0 on a Solaris 9 system: example# /usr/sbin/install.d/re-preinstall c0t0d0s1 3. Reboot the slice: example# reboot disk:b Example 2: Installing the JumpStart Software on a System's Attached (non-boot) Disk The following procedure installs the JumpStart software on a system's attached (non-boot) disk: 1. Mount the Solaris CD or DVD if vold(1M) is not running or CD or DVD is not mounted. 2. Use the format(1M) command to determine the target-slice where JumpStart will be installed. 3. Use the uname(1) command (-i option) to determine the platform name of the system that will use the re-preinstalled disk 4. Run re-preinstall with the -m Solaris_boot_dir option if the Solaris CD or DVD is not mounted on /cdrom. The following command installs the JumpStart software on the system's attached disk for a system with a Sun4u kernel architecture, and it uses the Solaris CD or DVD mounted with vold(1M) on a Solaris 9 system: example# /cdrom/cdrom/s1/usr/bin/install.d/re-preinstall -m /cdrom/cdrom/s1 -k sun4u c0t2d0s0 EXIT STATUS
The following exit values are returned: 0 Successful completion. 1 An error has occurred. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcdrom (Solaris CD, | | |SPARC Platform Edition) | +-----------------------------+-----------------------------+ SEE ALSO
uname(1), eeprom(1M), format(1M), mount(1M), vold(1M), attributes(5) Solaris 10 Installation Guide: Basic Installations SunOS 5.10 9 Apr 2002 re-preinstall(1M)
All times are GMT -4. The time now is 04:37 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy