Originally posted by: VirtualGreg
I'm a big fan of fibre channel boot.
The down side is your SAN architecture had better be redundant in nature and rock solid in terms of reliability and change management. If you have a SAN hiccup or single points of failure in your SAN, you're going to have more grief in an outage.
That said, with 72GB disks being the standard these days, what are you going to do with the other 68GB once AIX is loaded on internal disks? 8^)
With most SAN devices you can customize your LUN sizes and right size storage for rootvg disk(s). You can also benefit from hardware RAID with caching - any time you can rid yourself of the over head in running and managing LVM mirroring, you are a step ahead.
If your memory requirements are sized correctly, you won't do much paging I/O. I wouldn't worry about performance of paging space I/O. A disk is a disk, chances are the SAN storage uses drives with similar specs to your internal disk alternatives.
You could consider using a Virtual I/O Server for boot disks, then the VIOS LPAR's dedicated fibre channel paths take your rootvg I/O's down a different path. However, you should consider two VIOS LPARs for production workloads.
Which disk storage device are you planning to use? You should check with the vendor regarding their support and requirements for AIX fibre channel boot.