03-13-2014
Have you assigned the CD device to the LPAR?
If there is not a boot record on any of the disks, you will probably drop to SMS / firmware. Try to explore the disks by following the menus to select a boot device and then get it to list all the devices.
I hope that this helps,
Robin
Liverpool/Blackburn
UK
10 More Discussions You Might Find Interesting
1. AIX
Hello, we are trying to install an HP DAT drive on an IBM AIX RS6000 server. We have attached the SCSI connection and power cylced the unit, but still cannot see the device in smit.
I am only a couple months into AIX, so I am very green! The server we are working on is in a lab environment,... (2 Replies)
Discussion started by: dayinthelife
2 Replies
2. AIX
Whenever I assign/unassign a CDROM ( RAID CTRL ) to Active LPAR from HMC, I have to reboot the LPAR.
How can I do it without rebooting the LPARS.
POWER6 with HMC
LPARS = AIX 6.1
Any info
developerWorks : AIX and UNIX : PowerVM Forum : Moving CD-ROM/DVD-ROM dynamically ...
But... (5 Replies)
Discussion started by: filosophizer
5 Replies
3. AIX
I have 2 LPARs running AIX 5.3. Both are on the same VLAN. One LPAR, which I'll call LPAR2, has a 4mm SCSI tape drive connected to it, while LPAR1 does not have a tape drive connected. I am able to take mksysb backups of LPAR2 to the tape drive since it's directly connected. However, I need to... (2 Replies)
Discussion started by: need2bageek
2 Replies
4. AIX
Hi All,
i would like to know if it's possible to know all the IP Addresses of all LPAR's interfaces from HMC (without connect into LPAR).
And if i can know also the "Application" hostname of LPAR from HMC.
Thanks in advance.
Bye
Mario (2 Replies)
Discussion started by: Zio Bill
2 Replies
5. AIX
Unix Guys
i want to setup a lab in my house for learning, i want to setup and hacmp and a seperate server where i can setup 2 lpars and then cluster those 2 lpars and setup them up for failover
what is the cheapest way to achive this.
my objective is to learn hmc -> managed server via... (7 Replies)
Discussion started by: asyed123
7 Replies
6. AIX
Does anyone know of a command that can be run on the lpar to show the name of the lpars managing HMC?
We have a large environment and records a little old on which HMC manages which lpars....if i could login to an lpar and just issue a command to show me its managing hmc that would be great. (2 Replies)
Discussion started by: Foiled
2 Replies
7. AIX
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
8. AIX
Hi,
For installing aix on power series , do i need to install hmc first?
or i can connect hmc after?
Rgs, (7 Replies)
Discussion started by: prpkrk
7 Replies
9. UNIX for Advanced & Expert Users
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
10. UNIX for Beginners Questions & Answers
We want to integrate powervm by using openstack with hmc.
Now we encounter problem with the console, we can open the terminal within hmc, and I think hmc using tech java applet.
sample applet code like
<applet codebase="https://172.16.28.174/hmc/"... (0 Replies)
Discussion started by: eagle
0 Replies
LEARN ABOUT HPUX
bootconf
bootconf(4) Kernel Interfaces Manual bootconf(4)
NAME
bootconf - boot device configuration table
DESCRIPTION
The file contains the address and disk layout type of the system's boot devices or lif volumes. It is used by the and HP-UX kernel control
scripts (fileset to determine how and where to update the initial boot loader. Normally the kernel's script queries the system's hardware
and creates the file. In rare cases when either the system configuration cannot be automatically determined or additional and/or alternate
boot devices should be automatically updated, the administrator must edit the file manually.
There is one line in the file for each boot device. Each line contains the following blank-separated fields in the order shown:
disk type A flag indicating how the file system(s) on the disk are laid out. The flag must be one of the following:
Indicates that the root disk is in LVM or VERITAS Volume Manager
(VxVM) format. If LVM or VxVM mirrors are used, then each of the "mirrors" must have its own line in the file.
Indicates that the root disk is in the
"whole disk" format with no partitions, but boot and swap space are reserved outside the file system.
device file The absolute path of the device special file that accesses the physical device where the boot area is located. For LVM root
disks, the device special file is the physical volume(s) returned by the command. For "whole disks" this is the device file
that references the entire disk.
Blank lines are permitted. Any line beginning with a is considered to be a comment.
DIAGNOSTICS
The Software Distributor log file contains diagnostic messages under the fileset if the file is incorrect. Most of the messages are self-
explanatory; a few warrant additional explanation:
If there are no other messages about
the file is probably empty. Otherwise, the file is not in the proper format, and the other messages will explain what the problem
is.
The specified device file does not point to a disk where there is a
lif which contains the file
Some character other than
or is in the first field of a line.
As of release 10.0, the boot areas in
must all be on the same type of disk layout.
There are characters after the
device file specification.
EXAMPLES
The boot area is on an LVM root disk:
l /dev/disk/disk7_p2
The boot area is on a whole disk layout:
w /dev/disk/disk7
WARNINGS
All of the boot devices in the file must have the same disk layout.
AUTHOR
was developed by the Hewlett-Packard Company.
FILES
SEE ALSO
mediainit(1), hpux(1M), hpux.efi(1M), mkboot(1M), vgdisplay(1M), lif(4), intro(7).
documentation.
bootconf(4)