08-30-2004
Dlpar
Hi,
Anybody had a problem trying to rmdev a scsi device and get the following error :
root@:/> rmdev -dlscsi3 -R
Method error (/usr/lib/methods/ucfgncr_scsi):
0514-062 Cannot perform the requested function
because the specified device is busy.
I can't seem to find what is causing it ????
AIX 5.2.
S.
6 More Discussions You Might Find Interesting
1. 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
2. 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
3. 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
4. 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
5. 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
6. 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
LEARN ABOUT FREEBSD
devctl
DEVCTL(8) BSD System Manager's Manual DEVCTL(8)
NAME
devctl -- device control utility
SYNOPSIS
devctl attach device
devctl detach [-f] device
devctl disable [-f] device
devctl enable device
devctl suspend device
devctl resume device
devctl set driver [-f] device driver
DESCRIPTION
The devctl utility adjusts the state of individual devices in the kernel's internal device hierarchy. Each invocation of devctl consists of
a single command followed by command-specific arguments. Each command operates on a single device specified via the device argument. The
device may be specified either as the name of an existing device or as a bus-specific address. More details on supported address formats can
be found in devctl(3).
The following commands are supported:
attach device
Force the kernel to re-probe the device. If a suitable driver is found, it is attached to the device.
detach [-f] device
Detach the device from its current device driver. If the -f flag is specified, the device driver will be detached even if the device
is busy.
disable [-f] device
Disable a device. If the device is currently attached to a device driver, the device driver will be detached from the device, but
the device will retain its current name. If the -f flag is specified, the device driver will be detached even if the device is busy.
enable device
Enable a device. The device will probe and attach if a suitable device driver is found. Note that this can re-enable a device dis-
abled at boot time via a loader tunable.
suspend device
Suspend a device. This may include placing the device in a reduced power state.
resume device
Resume a suspended device to a fully working state.
set driver [-f] device driver
Force the device to use a device driver named driver. If the device is already attached to a device driver and the -f flag is speci-
fied, the device will be detached from its current device driver before it is attached to the new device driver. If the device is
already attached to a device driver and the -f flag is not specified, the device will not be changed.
SEE ALSO
devctl(3), devinfo(8)
HISTORY
The devctl utility first appeared in FreeBSD 11.0.
BSD
February 5, 2015 BSD