Sponsored Content
Full Discussion: Power machine 720 SAS disk
Operating Systems AIX Power machine 720 SAS disk Post 303042785 by Phat on Tuesday 7th of January 2020 12:13:39 AM
Old 01-07-2020
Quote:
Originally Posted by rbatte1
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!)
Code:
lspv
lspv -v
lspv -l
lsvpcfg                    # (possibly with a -l flag?)
lsdev -Cc disk             # Bit of a long shot perhaps
lscfg -v|grep -i disk      # Again, a bit of a guess

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
Code:
lsdev -Cc disk | grep -i sas

to figure out the disk size of said disks use
Code:
getconf DISK_SIZE /dev/<hdisk>

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?
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

mount disk on other machine

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)
Discussion started by: sajjan2
5 Replies

2. UNIX for Dummies Questions & Answers

command to know disk controllers in a machine

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)
Discussion started by: reply2priyanka
3 Replies

3. AIX

Maximum Limit of HMC to handle Physical Power Virtualization Physical Machine

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)
Discussion started by: jenish_shah
1 Replies

4. AIX

POWER HA 5.5 & Service IP / disk heart beat

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)
Discussion started by: filosophizer
2 Replies

5. UNIX for Dummies Questions & Answers

find physical disk type : SAS / SATA

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)
Discussion started by: coderd
1 Replies

6. AIX

Power HA 7 repository disk unmirrored?

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)
Discussion started by: funksen
0 Replies

7. UNIX for Dummies Questions & Answers

How to get current power consumption of a machine

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)
Discussion started by: flagman5
6 Replies

8. Red Hat

Udev Rule TAG for identifying a local sas disk, non-scsi, non-fiber, non-iscsi

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)
Discussion started by: mrmurdock
0 Replies

9. AIX

Power Machine password

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)
Discussion started by: Phat
6 Replies

10. AIX

Replaced pdisk not showing up in SAS Disk Array Configuration

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
voldiskadm(8)						      System Manager's Manual						     voldiskadm(8)

NAME
voldiskadm - Menu interface for LSM disk administration SYNOPSIS
/usr/sbin/voldiskadm DESCRIPTION
The voldiskadm script is an interactive tool that presents a menu of possible operations to the user. When an operation is selected, the script guides the user through the necessary steps, and prompts for data needed to complete the operation. The voldiskadm interface is intended mainly for beginning users and for those who prefer a simple method for doing common operations. The interface uses query-based prompts to gather input, with defaults supplied when possible. Context-sensitive help is available at every prompt by typing ?. Also, a list option can be used to get information on available target disks for an operation. For operations that require a device name, one or more names can be specified using a space-separated list. Names in the list can have the form dskn or rdskn (for an entire disk) or dsknp or rdsknp (for a specific disk partition). Disk names relate directly to device names in the /dev/disk and /dev/rdisk directories. The file, /etc/vol/disks.exclude, may be used to exclude disks from use by voldiskadm. Each line of the file specifies the name of a disk to exclude (for example, dsk5). The voldiskadm menu includes the following options: Add or initialize one or more disks This option prompts for one or more disk device addresses. The specified disks can be added to an existing disk group, added to a new disk group, added to a disk group as spares, or initialized but not added to a disk group (reserved for use as replacement disks). After specifying the disks, the user is prompted for a disk group (rootdg by default) and a disk name. If no name is specified, a default disk name is assigned (diskn for disks in the rootdg disk group and diskgroupn for disks in other disk groups). The disks are then checked to ensure that there is no information already on them. If there is, the user is given the option of encapsulating the disks. Encapsulate one or more disks This option prompts for one or more disk addresses. It then calls volencap to encapsulate the specified partitions. Remove a disk This option prompts for a disk, by disk media name. The disk is checked to ensure that no subdisks reside on the disk. If the disk is in use, the operation fails with a recommendation to first move all volumes off the disk. If this disk is the last disk in a disk group, the user is prompted for whether the disk group should be removed from the system, as well. The operation proceeds by calling voldg rmdisk to remove the disk from its disk group. If this is the last disk in its disk group, voldg deport is used, instead, to remove the disk group from use. Remove a disk for replacement This option prompts for a disk, by disk media name. The disk is checked for volumes that would lose all mirrors as a result of the operation. If such volumes exist, they are listed and the user is prompted to ensure that the operation should proceed. The operation proceeds by calling voldg -k rmdisk to dissociate the media record from the physical disk. If some formatted disks are under LSM control but not assigned to a disk group, the user is prompted for whether one of these disks should be used as a replacement. Replace a failed or removed disk This option prompts for a disk media name. The named media record must be dissociated from a disk. If the media record is not in the removed state, unused disks are scanned for matching disk IDs. If a disk with a matching disk ID is found, the user is prompted for whether that disk should be reattached. If a matching disk is not used, the user is prompted for a new disk, by device name. If the named replacement disk has a valid disk header, but is not allocated to a disk group, the user is prompted for whether the disk should be reinitialized. If the named replacement disk is listed as allocated to a disk group or to another host, the user is prompted to ensure that the operation should proceed. If the device is to be initialized, a new disk label is written to the disk to reflect its private and public regions. Given an initialized disk, the operation proceeds by replacing the disk in a disk group with voldg -k adddisk. Mirror volumes on a disk This option prompts for a disk, by disk media name. It then prompts for a destination disk within the same disk group, also by disk media name. Specifying no destination disks indicates that any disk is suitable. The operation proceeds by calling volmirror to mirror the volumes. Mirroring volumes from the boot disk will produce a disk that can be used as an alternate boot disk. This is done by calling the volrootmir command. Move volumes from a disk This option prompts for a disk, by disk media name. It then prompts for a possible list of destination disks, also by disk media name. Specifying no destination disks indicates that any disk is suitable. The operation proceeds by calling volevac to move sub- disks off the disk. Enable access to (import) a disk group This option prompts for a disk, by device address. The operation proceeds by calling voldg import to import the disk group stored on that disk. Disable access to (deport) a disk group This option prompts for a disk group name. The prompt display lists alternate disk groups and the disks (media name and access name) that they contain. The operation proceeds by calling voldg deport. Enable (online) a disk device This option prompts for a disk device. The prompt display allows for a display of disks on the system. The operation only func- tions for disks currently in an offline state. It then proceeds to make the disk accessible. Disable (offline) a disk device This option prompts for a disk device. The prompt display allows for a display of disks on the system. The operation only func- tions for disks currently in an online state but not part of any disk group. It then proceeds to mark the disk as offline such that the Logical Storage Manager makes no further attempt at accessing the disk. Mark a disk as a spare for a disk group This option sets up a disk to be used as a spare device for its disk group. A spare disk can be used to automatically replace a disk that has failed. No space can be used on a disk that is marked as a spare. Turn off the spare flag for a disk This option removes a disk from those that can be used as a spare and returns its space to the general pool of available space. Recover plexes and volumes after replacement This operation performs plex attachment, RAID-5 subdisk recovery, and resynchronize operations for the named volumes, or for volumes residing on the named disks (media name). If no media name or volume operands are specified, the operation applies to all volumes (or to all volumes in the specified disk group). ERRORS
See the voldiskadd(8) reference page for a description of errors related to the initialization operation. FILES
A list of disks to exclude from use by voldiskadm. SEE ALSO
disklabel(8), volintro(8), voldg(8), voldisk(8), voldiskadd(8), voldisksetup(8), volrootmir(8) voldiskadm(8)
All times are GMT -4. The time now is 12:18 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy