03-31-2008
The boot list is stored in the firmware, the firmware is just like the bios on a PC.
The process is just the same, you must tell the firmware where to look for the boot device.
In AIX you can use the bootlist command to display or update the bootlist in the system firmware.
You are correct, if the battery dies there may be a problem booting.
Just like going in to the bios on a pc to correct a boot list after the battery died, on an AIX machine you can use SMS to correct the boot list.
Typically most people have the rootvg on local, internal, disks and any datavg's on SAN disks. This way if the SAN fails, the machine is still bootable, even if it cannot do any work because the SAN is offline.
You will probably also find the internal disks are slightly faster than SAN disks, this is useful for fast access to the operating system files and paging space.
Without a lot more information about your system and SAN configuration and testing of your specific setup there is no way to tell which would be best for you.
If you only have a small amount of space on the internal disks or one fiber card I'd leave things as they are, but check to see if the system can boot from the SAN disks, just so you know what you'll need to do to recover the system if the internal boot disk fails.
10 More Discussions You Might Find Interesting
1. AIX
Hello everyone
I got several aix boxes with aix 5.3
I got a ibm san ds4500
My question is
How can I do a match between my disks on aix and the san?
I try to do a match with the LUN but for example. In my san I got several 1 LUN and on one of my aix box I got this
If I type lscfg... (4 Replies)
Discussion started by: lo-lp-kl
4 Replies
2. AIX
We are considering a DR strategy of booting AIX 5.3 and 5.3 logical partitions from EMC Symmetrix SAN disks, so that we can replicate via SRDF to a recovery site. Has anyone tried configuring AIX 5.x systems to boot from SAN disk? If so, can you provide any information on the pros and cons of... (6 Replies)
Discussion started by: jjgarrot
6 Replies
3. Solaris
hi all,
have a solaris 9 OS and a SAN disk which used to work fine is not getting picked up by my machine. can anyone point out things to check in order to troubleshoot this ??
thanks in advance. (3 Replies)
Discussion started by: cesarNZ
3 Replies
4. Filesystems, Disks and Memory
Scenario:
I've got 2 M5000's connected to a 9985 SAN storage array. I have configured the SAN disks with stmsboot, format and newfs. I can access the same SAN space from both systems. I have created files from both systems on the SAN space.
Question:
Why can't I see the file created... (3 Replies)
Discussion started by: bluescreen
3 Replies
5. UNIX for Dummies Questions & Answers
Hi all,
My main function is as a DBA. Another person manages the server and the SAN.
I just want to know if I should be worried about high disk I/O or is it irrelevant as the I/O "load balancing" will be "taken care" of by the SAN?
For example, I have hdisk1-5 and I can see that there are... (2 Replies)
Discussion started by: newbie_01
2 Replies
6. Solaris
Hi,
I have a production solaris 10 SPARC system (portal). Yesterday legato/Networker gave an I/O Error on one of the files on its SAN mounted disk.
I went to that particular file on the system, did an ls and it showed the file. However, ls -l did not work and it said IO error.
... (6 Replies)
Discussion started by: Mack1982
6 Replies
7. AIX
Hello Folks,
I have directly connected my IBM Pseries AIX machine to SAN Storage
I have a dual port Fibre Channel Adapter
Connected both fiber ports to SAN Box IBM DS4500 Controller A & Controller B
Using IBM DS storage manager client 10 -- created one logical disk and assigned to a... (18 Replies)
Discussion started by: filosophizer
18 Replies
8. AIX
Hello All,
Our servers having emc clarion for the data disks. Is that possible to see those san disks raid level from AIX ?
Am having AIX 6.1 and EMC clarion 5.5.
Regards,
Gowtham.G (3 Replies)
Discussion started by: gowthamakanthan
3 Replies
9. AIX
Hi guys, :)
I'm a studient in IT field (AIX)
I'm trying to map a LUN from a SAN (DS3400) to an AIX server (5300-04-00)
I know there is no MPIO on this version of AIX, and i see double my LUN from the SAN
root@localhost # lscfg | grep hdisk
+ hdisk7 ... (13 Replies)
Discussion started by: Tharsan
13 Replies
10. UNIX for Beginners Questions & Answers
I am in the market looking to purchase a new E950 server and I am trying to decide between using local SSD drives or SSD based SAN. The application that will be running on this server is read-intensive so I am looking for the most optimal configuration to support this application. There are no... (2 Replies)
Discussion started by: ikx
2 Replies
LEARN ABOUT HPUX
vxdestroy_lvmroot
vxdestroy_lvmroot(1M) vxdestroy_lvmroot(1M)
NAME
vxdestroy_lvmroot - remove LVM root disk and associated LVM volume group
SYNOPSIS
vxdestroy_lvmroot [-v] [-b] lvm_root_disk
DESCRIPTION
The vxdestroy_lvmroot command tears down and removes the LVM volume group associated with the specified physical disk. This is done by
removing the volumes in the volume group and then removing the volume group.
OPTIONS
-b Invokes the setboot command to change the primary boot disk to the VxVM root disk from which the system was booted (if the pri-
mary boot disk is not already set to this disk). The alternate boot device remains unchanged. If the -v option is also speci-
fied, the settings of the primary and alternate boot devices are displayed.
-v Outputs verbose messages including a timestamp that indicates major operations being performed.
ARGUMENTS
lvm_root_disk
Specifies the device name of the LVM root disk that is to be destroyed, along with its entire volume group.
EXAMPLES
This example shows the vxdestroy_lvmroot command invoked in its simpliest form:
/etc/vx/bin/vxdestroy_lvmroot c5t1d0
# /etc/vx/bin/vxdestroy_lvmroot -v -b c3t0d0
Are you sure about destroying c3t0d0 (imported on VG /dev/vg02) ? YES
vxdestroy_lvmroot 06:02: Tearing down /dev/vg02 on device c3t0d0
vxdestroy_lvmroot 06:02:
Unmounting and removing any volumes associated with /dev/vg02
vxdestroy_lvmroot 06:02: removing logical volume /dev/vg02/lvol1
vxdestroy_lvmroot 06:02: removing logical volume /dev/vg02/lvol2
vxdestroy_lvmroot 06:02: removing logical volume /dev/vg02/lvol3
vxdestroy_lvmroot 06:02: removing logical volume /dev/vg02/lvol4
vxdestroy_lvmroot 06:02: removing logical volume /dev/vg02/lvol5
vxdestroy_lvmroot 06:02: removing logical volume /dev/vg02/lvol6
vxdestroy_lvmroot 06:02: removing logical volume /dev/vg02/lvol7
vxdestroy_lvmroot 06:02: removing logical volume /dev/vg02/lvol8
vxdestroy_lvmroot 06:02: Removing Volume Group /dev/vg02
vxdestroy_lvmroot 06:02: Removing device files in /dev/vg02
vxdestroy_lvmroot 06:02: Removing LVM Physical Volume c3t0d0
vxdestroy_lvmroot 06:02: Removing LVM Physical Volume c1t1d3
vxdestroy_lvmroot 06:02: Removing LVM Physical Volume c1t1d4
vxdestroy_lvmroot 06:02: Removing LVM Physical Volume c1t1d5
vxdestroy_lvmroot 06:03: Current setboot values:
vxdestroy_lvmroot 06:03: Primary: 0/0/6/0/0.0.0
vxdestroy_lvmroot 06:03: Alternate: 0/0/1/0/0.1.0
vxdestroy_lvmroot 06:03:
Making disk c0t1d0 (0/0/1/0/0.1.0) the primary boot disk
vxdestroy_lvmroot 06:03:
Removal of device c3t0d0, volume group /dev/vg02 was successful
SEE ALSO
cpio(1), dd(1), fsck(1M), setboot(1M) vxbootsetup(1M) vxcp_lvmroot(1M) vxres_lvmroot(1M)
VxVM 5.0.31.1 24 Mar 2008 vxdestroy_lvmroot(1M)