6 More Discussions You Might Find Interesting
1. AIX
Hello,
I have checked the state of rmc on the HMC as below:
HMC1:~> lssyscfg -r lpar -m Server-xxx -F lpar_id,state,rmc_state,rmc_ipaddr,os_version,dlpar_mem_capable,dlpar_proc_capable,dlpar_io_capable --filter "lpar_ids=4"
4,Running,inactive,10.176.x.x,VIOS 2.2.6.51,0,0,0
HMC1:~> lssyscfg... (2 Replies)
Discussion started by: Phat
2 Replies
2. AIX
Hey All,
I have running dual VIOS on a P9 systems, and just created a new LPAR profile. My objective is to create LPAR Client VFC adapters, and then DLPAR VFC Server adapters on the VIOS.
In the HMC v9 Enhanced GUI, I have DLPAR a VFC adapter to both VIOS, however, you can't specify the... (1 Reply)
Discussion started by: aixkidbee
1 Replies
3. AIX
I cannot find the post with the comment that DLPAR capability was not working with IVM.
The two commands that need to be run are (as root, padmin does not know this command):
VIOS: lsrsrc IBM.MngNode
CLIENTS: lsrsrc IBM.MCP
Examples:
# lsrsrc IBM.MngNode
Resource Persistent Attributes for... (2 Replies)
Discussion started by: MichaelFelt
2 Replies
4. UNIX for Advanced & Expert Users
Can anyone please let know difference between LPAR/DLPAR/WPAR.
and its purpose ??? (3 Replies)
Discussion started by: Pavithran
3 Replies
5. AIX
I am trying to generate a report to track dlpar operation performed on a MS and was wondering if anyone has done this before.
I can get history from HMC using lssvcevents , but this does not give me details as to what quantity was added or removed .
Any thoughts ?
Thanks (3 Replies)
Discussion started by: mk8570
3 Replies
6. AIX
Hello,
This is the foll error wen i try doin DLPAR from my VIO after adding the virtual adpaters on my clients:
HSCL294C DLPAR ADD Virtual I/O resources failed:
com.ibm.hsc.common.exceptions.PIHscClientException: HSCL294C DLPAR ADD Virtual I/O... (0 Replies)
Discussion started by: lildudesaif
0 Replies
TAPSET::SCSI(3stap) TAPSET::SCSI(3stap)
NAME
tapset::scsi - systemtap scsi probe points
DESCRIPTION
This family of probe points is used to probe the SCSI activities. It contains the following probe points:
scsi.ioentry
Fires when SCSI mid layer prepares a SCSI request
Arguments:
disk_major
The major number of the disk
disk_minor
The minor number of the disk
device_state
The current state of the device. The possible values could be:
SDEV_CREATED = 1, /* device created but not added to sysfs
* Only internal commands allowed (for inq) */
SDEV_RUNNING = 2, /* device properly configured
* All commands allowed */
SDEV_CANCEL = 3, /* beginning to delete device
* Only error handler commands allowed */
SDEV_DEL = 4, /* device deleted
* no commands allowed */
SDEV_QUIESCE = 5, /* Device quiescent. No block commands
* will be accepted, only specials (which
* originate in the mid-layer) */
SDEV_OFFLINE = 6, /* Device offlined (by error handling or
* user request */
SDEV_BLOCK = 7, /* Device blocked by scsi lld. No scsi
* commands from user or midlayer should be issued
* to the scsi lld. */
scsi.iodispatching
Fires when the SCSI mid layer dispatches a SCSI command to the low level driver
Arguments:
host_no
The host number
channel
The channel number
lun
The lun number
dev_id
The scsi device id
device_state
The current state of the device.
data_direction
The data_direction specifies whether this command is from/to the device.
The possible values could be:
DMA_BIDIRECTIONAL = 0,
DMA_TO_DEVICE = 1,
DMA_FROM_DEVICE = 2,
DMA_NONE = 3,
request_buffer
The request buffer address
req_bufflen
The request buffer length
scsi.iodone
Fires when a SCSI command is done by low level driver and enqueued into the done queue.
Arguments:
host_no
The host number
channel
The channel number
lun
The lun number
dev_id
The scsi device id
device_state
The current state of the device
data_direction
The data_direction specifies whether this command is from/to the device.
scsi.iocompleted
Fires when SCSI mid layer runs the completion processing for block device I/O requests
Arguments:
host_no
The host number
channel
The channel number
lun
The lun number
dev_id
The scsi device id
device_state
The current state of the device
data_direction
The data_direction specifies whether this command is from/to the device.
goodbytes
The bytes completed.
SEE ALSO
stap(1), stapprobes(3stap)
IBM
TAPSET::SCSI(3stap)