08-16-2006
Reboot the lpar (shutdown -Fr) and you might find it mysteriously appears. Had the same problem with a CD drive!
10 More Discussions You Might Find Interesting
1. AIX
Hi - can anybody tell me what the default behaviour is for cfgmgr when it allocates hdisk numbers to newly discovered disks in the ODM ? I want to add a disk from our FAStT700 SAN disk array and import it on our p-series (AIX 5.2). Problem is we import and export Flashcopy devices fror scripted... (5 Replies)
Discussion started by: fosteria
5 Replies
2. AIX
Hi All,
I remember my old senior mentor in AIX that cfgmgr should not be terminated on your console. Because if it's terminated in the middle, the odm might get corrupted.
Is that true for AIX 5.x?
Regards,
itik (1 Reply)
Discussion started by: itik
1 Replies
3. AIX
Hi all,
I have a System i server with a couple of AIX LPARs.
One of the LPARs owns a dual-channel scsi adapter to which I connect a tape library (IBM TS3100) and a DVD Drive.
I had some problems to get the Tape Library detected but finally I got it:
rmt0 Available 03-08-01-4,0 IBM 3580... (1 Reply)
Discussion started by: wendelalexis
1 Replies
4. AIX
OS: AIX 6.1
The host has a dual port NIC installed and when I went to run `cfgmgr -v` to configure it I got an error showing device packages are missing from the install:
`cfgmgr -v` on 10.15.xx.xxx
cfgmgr: 0514-621 WARNING: The following device packages are required for device support but... (3 Replies)
Discussion started by: b1f30
3 Replies
5. AIX
Hi
When I run cfgmgr -v in my aix box I get the below error :
cfgmgr: 0514-621 WARNING: The following device packages are required for
device support but are not currently installed.
devices.loopback
My oslevel is 6100-06-02-1044
Please assist.
Please use and tags when... (3 Replies)
Discussion started by: samsungsamsung
3 Replies
6. AIX
Hi all,
I have the following configuration
2 ds3524 storage disk systems located over 2 locations
2 P720 server located over 2 locations
DS3524 are connected to san switch.
Each vio server has 1 fc adapter attached to a san switch.
per p720 server 2 virtual io servers. Vio 1 has 1 lun... (2 Replies)
Discussion started by: markiemark
2 Replies
7. AIX
Dear all
i have a sun SL500 tape library attached to my AIX box while issue the command cfgmgr i have the below issue
test>cfgmgr
cfgmgr: 0514-621 WARNING: The following device packages are required for
device support but are not currently installed.
devices.fcp.changer
please... (3 Replies)
Discussion started by: thecobra151
3 Replies
8. AIX
Hi,
From the man page, cfgmgr configures devices and optionally installs device software by running the programs specified in the Configuration Rules object class and it is not dependent on platform .
Are there any fundamental differences impacting the speed of cfgmgr on a stand-alone and... (5 Replies)
Discussion started by: Sachin1987
5 Replies
9. AIX
There can be configurations in IBM Server wherein a
standalone partition is created on some supported IBM Server
Or
A VIOS - VIOC LPARs created.
Now in both cases they are lpars. But if I want to differentiate b/w a standalone LPAR vs an VIOC LPAR how can I do..?
On a... (2 Replies)
Discussion started by: Manish00712
2 Replies
10. Post Here to Contact Site Administrators and Moderators
Hi,
My AIX server able to detect the LUN's which is mapped from IBM v7k storage, And i allocated one more LUN from HP storage but it's appear two hdisk instead of one and it's showing incorrect LUN ID.
SDDPCM driver already installed on this server.
During cfgmgr, Im getting this message :... (1 Reply)
Discussion started by: xinuadmin
1 Replies
LEARN ABOUT OSF1
cfgmgr_set_status
cfgmgr_set_status(9r) cfgmgr_set_status(9r)
NAME
cfgmgr_set_status - General: Reports failure to the cfgmgr framework
SYNOPSIS
int cfgmgr_set_status(
char *driver_name );
ARGUMENTS
Specifies the name of the device driver for which you want to report an associated failure. This name is a string that matches the string
you specified for the entry_name item in the /etc/sysconfigtab database. Typically, third-party driver writers specify the driver name
(followed by a colon) in the sysconfigtab file fragment, which gets appended to the /etc/sysconfigtab database during the driver product
installation.
DESCRIPTION
The cfgmgr_set_status routine reports to the cfgmgr framework that a failure has occurred during static configuration. If the specified
device driver is in the static configuration state, it does not know that the configuration operation is complete until all register call-
back requests (routines) have successfully completed. Therefore, a device driver calls cfgmgr_set_status to report a possible failure dur-
ing static configuration to the cfgmgr framework.
Specifically, cfgmgr_set_status performs the following failure operations: Adjusts the state of the specified device driver Unconfigures
the specified device driver from the cfgmgr framework
The cfgmgr_set_status routine calls the device driver's configure routine at its CFG_OP_UNCONFIGURE entry point as part of these failure
operations. The code associated with the CFG_OP_UNCONFIGURE entry point is responsible for determining how to deallocate any allocated
resources during these failure operations.
The cfgmgr_set_status routine does not notify the operator of a configuration failure. Part of the code associated with the CFG_OP_UNCON-
FIGURE entry point could include an error logging operation to record the fact that a failure has occurred. The reason for doing this is
that the cfgmgr framework's task is to accomplish the unconfigure operation of a statically configured device driver.
You call the cfgmgr_set_status routine in the device driver's callback routine when the static configuration operation fails. You register
a callback routine by calling the register_callback routine.
RETURN VALUES
Upon successful completion, cfgmgr_set_status returns the value ESUCCESS. This success value indicates that cfgmgr_set_status adjusted the
state of the device driver and caused the cfgmgr framework to unconfigure the driver. Otherwise, cfgmgr_set_status returns one of the fol-
lowing error constants defined in /usr/sys/include/sys/sysconfig.h and /usr/sys/include/sys/errno.h: The device driver that you specified
in the driver_name argument does not exist. In this case, cfgmgr_set_status cannot adjust the state and unconfigure the device driver. The
device driver that you specified in the driver_name argument was not statically configured. The device driver that you specified in the
driver_name argument is not in the static configuration state.
EXAMPLES
See Writing Device Drivers: Tutorial for a code example of the cfgmgr_set_status interface.
SEE ALSO
Routines: cfgmgr_get_state(9r), register_callback(9r)
cfgmgr_set_status(9r)