It depends quite what you are looking for. Do any of these help (sorry but I no longer have access to AIX so I'm a bit rusty!)
What are the metrics you are looking for? Is it the LPAR view of the assigned disk to the size of the disk that is owned by the hardware as a whole? The LPAR will not see that.
I hope that these suggestions give you something.
Robin
Thank Robin, I would like to check at the physical hardware console, not from LPAR, have not LPAR right now.
--- Post updated at 06:13 AM ---
Quote:
Originally Posted by zxmaus
from the hardware itself, you cannot see the disks - you can only see the controllers, not what is attached to them.
As part of the SMS menu you can see the disks and sizes if you query the controllers - or when you install AIX as you have to select a suitable disks for the installation - with location code.
If you have AIX already installed, run these commands.
to find your SAS disks, run
to figure out the disk size of said disks use
Hi Zxmaus,
I understand now that from physical hardware Power Machine we cannot check the disk and size.
Still have 1 thing to ask, for SAS disk, I see it is part of raid controller. The disk is called pdisk. After configuring raid, it becomes hdisk which AIX can see. The question is, if in the first time, we assign the controller and its disks to LPAR to install AIX. How can we configure the raid before AIX OS can see these disks?
I have two Unix machines on the network and now one of them are running out of disk but i have alot on the other so i like to mount the disk (or a folder) from the one that has disk and mount it on the other that does not.
How do i do that? Is it possible i read the "man mount" but didn't really... (5 Replies)
Hi!!
I am these days working on a project, where I need to know about the disk controllers available in a machine (e.g., 3ware,IBM,etc).
Please, let me know the command by which I can get the information.
thnx,
priyanka (3 Replies)
Hello All,
Can anybody please tell me what is the maximum limit of Physical IBM Power Machine which can be handled by single HMC at a single point of time?
Thanks,
Jenish (1 Reply)
Hello,
I have a quick question regarding POWER HA ( HACMP ) 5.5 ;
I have four ethernet adapters
en0
en1
en2
en3
en0 is configured as BOOT_IP with IP address
all other ethernet adapters are empty en1 / en2 / en3
so when I configure the service IP and start HACMP , the service IP... (2 Replies)
Hi,
Is there an easy way to find the disk-type from the command line or with another api ? sdparm works for SAS but not for SATA, hdparm works for SATA but not SAS.
Thanks (1 Reply)
hi guys,
I don't like the new concept of the power ha 7 cluster with the repository disk and the internal solidb, I really would like to mirror this disk, but the "IBM PowerHA SystemMirror 7.1 for AIX" redbook says, normal lvm operations should not be performed on this disk.
even mirroring the... (0 Replies)
Hi
Is there any native commands or somewhere in the /proc files to get the machine's power consumption? I googled for a while and cannot really find this information
Thanks for your help. (6 Replies)
I need to add a VMware virtual disk to the 99-oracle-asmdevices.rules file but the OS is not assigning a WWID to the disk. It has been fdisk'd and a single partition created.
What TAG inside the file needs to be added? the Program scsi-id does not work for some reason. latest patches... (0 Replies)
Hi,
I have installed the HMC on the VMWare VM. I try to add the power machine (managed system) and asking for a password? So this is the IBM predefined password of Power Machine?
In the VMWare perspective, we can login to ESX host to do some management tasks. But how about the Power machine?... (6 Replies)
OSLevel: 5300-10-02-0943
System Model: IBM,8203-E4A
Power 6
==
Hi!
I replaced a failed pdisk in the raid enclosure as follows,
- rmdev -l 'pdisk18' '-d'
- Replaced it.
- cfgmgr (detected)
- I can see the new drive, with the correct serial #
lscfg -v -l pdisk18
pdisk18... (2 Replies)
Discussion started by: estrar
2 Replies
LEARN ABOUT OSF1
ri
ri(7) Miscellaneous Information Manual ri(7)NAME
ri - I2O RAID disk interface
SYNOPSIS
bus i2o0 at pci2001 slot 4
controller i2o_bs0 at i2o0 slot 18
DESCRIPTION
The ri driver supports 32-bit and 64-bit PCI backplane RAID controllers with Intelligent I/O (I2O) host interface supporting backend SCSI
channels. I2O is an open architecture for developing device drivers that is independent of the operating system, processor platform, and
system I/O bus. The communication model is based on a message-passing protocol reducing the number of driver interfaces needed. A single
driver called an Operating System Module(OSM) is provided to support all Block Storage class devices. Any RAID system that supports the
I2O interface functions with this driver. These devices are designated as ri to distinguish them from ra, re, and rz (SCSI) devices.
The StorageWorks Command Console Utility (SWCC) is supported for online configuration and monitoring of I2O raid devices.
The following rules are used to determine the major and minor numbers that are associated with an ri type disk. A dynamic major number is
used to represent ri block devices, and is assigned during initial configuration. The current major number can be determined using the
following command: # /sbin/devswmgr -getnum i2o_bs The preceding command displays the driver switch reservation list, showing the device
instance and major number for the i2o_bs driver. An alternative method is: # /sbin/sysconfig -q i2o_bs
The highest 14 bits of the 20-bit minor number represents a particular Block Storage device, while lowest six bits of the minor number
specify disk partitions (identified by the letters, a through h) on that device.
The device special file names associated with ri disks are based on conventions that are closely associated with the minor number assigned
to the disk. The standard device names begin with ri for block special files and rri for character (raw) special files. Following the ri
is the unit number and then a letter, a through h, that represents the partition. Throughout this reference page, the question mark (?)
character represents the unit number in the name of the device special file. For example, ri?b could represent ri0b, ri1b, and so on.
A disk can be accessed through either the block special file or the character special file. The block special file accesses the disk using
the file system's normal buffering mechanism. Reads and writes to the block special file can specify any size. This capability avoids the
need to limit data transfers to the size of physical disk records and to calculate offsets within disk records. The file system can break
up large read and write requests into smaller fixed size transfers to the disk.
The character special file provides a raw interface that allows for direct transmission between the disk and the user's read or write buf-
fer. A single read/write operation to the raw interface results in exactly one I/O operation. Consequently, raw I/O may be considerably
more efficient for large transfers.
For systems with ri disks, the first software boot after the system is powered on may take longer than expected. This delay is normal and
is caused by the software spinning up the ri disks.
Disk Support
The ri driver handles all disk drives that can be connected to the I2O RAID controller. To determine which drives are supported for spe-
cific CPU types and hardware configurations, see the hardware installation and configuration information for your I2O system.
I2O RAID Controllers are viewed in all cases as RI type disks. There are some notable differences that should be taken into consideration
when configuring a RAID device: Currently only sector sizes of 512 bytes are supported. Logical Volume sizes are not fixed sizes as com-
pared to other disk devices. The size of the Logical Volume is configurable based on needs. The dynamic nature of Logical Volume sizes is
dealt with by defining RAID devices as DYNAMIC. Only partitions a, b, c, and g are defined. If necessary, the disklabel(8) command can be
run to change and define partitions for RAID devices
Usually, the ri?a partition is used for the root file system and the ri?b partition as a paging area. The ri?c partition can be used for
disk-to-disk copying because it maps the entire disk.
The starting location and length (in 512 byte sectors) of the disk partitions of each drive are shown in the following table. Partition
sizes can be changed by using the disklabel(8) command.
I2O RAID partitions for systems
based on the Alpha AXP architecture
disk start length
ri?a 0 131072 ri?b 131072 262144 ri?c 0 end of media ri?d 0 0 ri?e 0 0 ri?f 0 0
ri?g 393216 end of media ri?h 0 0
FILES
/dev/disk/ri??? /dev/disk/rri???
RELATED INFORMATION RAID(7), SCSI(7), tz(7), rz(7),disklabel(8), MAKEDEV(8), uerf(8) delim off
ri(7)