10-04-2017
Having deleted the device you need to run cfgmgr to probe and discover it again.
This will happen next boot or you can force it with cfgmgr -S
You may also need to delete device ent0
Does that help?
Robin
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
We are trying to Establish Network using Linux.Now we are facing the problem in configring Ethernet.In out network we are giving eth0 in server and activating it at the boot time,so it is activating as it is but when we define the Ethernet of node on server and allowing it to activate at boot time... (5 Replies)
Discussion started by: at_renai2001
5 Replies
2. UNIX for Dummies Questions & Answers
I am using Red Hat 7.1 . I have installed one Server and trying to make network installing workstations on other system of a network. The Ethernet of the server has been mounted and working properly. I am getting problem installing /mounting the Ethernet of the workstations .I have tryed this by... (1 Reply)
Discussion started by: at_renai2001
1 Replies
3. Filesystems, Disks and Memory
First time so excuse my ignorance please.
I may not be accurately describing the issue.
I have inherited a small lab mostly SUN V120s.
We lost power and are trying to recover.
Nope no backups...
The primary issue I have is 1 box is an Oracle Server.
It has 2 36Gb harddrives.
I am able to... (3 Replies)
Discussion started by: murphsr
3 Replies
4. Solaris
Boot device: /pci@8,600000/SUNW,qlc@4/fp@0,0/disk@w500000e0103c3391,0:a File and args:
SunOS Release 5.8 Version Generic_108528-29 64-bit
Copyright 1983-2003 Sun Microsystems, Inc. All rights reserved.
ifconfig: plumb: qfe2: Bad file number
configuring IPv4 interfaces: eri0.
moving addresses... (1 Reply)
Discussion started by: fredginting
1 Replies
5. AIX
Hello everyone
I have a problem with one server, has Aix 5.3 in the errpt has this message
IDENTIFIER TIMESTAMP T C RESOURCE_NAME DESCRIPTION
F3931284 0105133009 I H ent0 ETHERNET NETWORK RECOVERY MODE
EC0BCCD4 0105133009 T H ent0 ETHERNET DOWN
F3931284 ... (4 Replies)
Discussion started by: lo-lp-kl
4 Replies
6. Solaris
I have a new Sun 440 and I am trying to configure it. Non of the Ethernet ports are enabled; when I issue "ifconfig -a" it returns nothing. Is there a way to know the available port name (e.g. ce, bge, etc.) by running a command or so ? (4 Replies)
Discussion started by: StarSol
4 Replies
7. Solaris
my solris box network is unreachable how to solve this
ipaddress assiagning and entry in vi /etc/host
how to solve network is unreachable (2 Replies)
Discussion started by: tirupathi
2 Replies
8. AIX
Hi
In the vio server when I do # lsattr -El hdisk*, I get a PVID. The same PVID is also seen when I put the lspv command on the vio client partition. This way Im able to confirm the lun using the PVID.
Similarly how does the vio client partition gets the virtual ethernet scsi client adapter... (1 Reply)
Discussion started by: newtoaixos
1 Replies
9. UNIX for Advanced & Expert Users
Hi,
I have posted several times regarding my application.
In a nutshell, I have a server application that logs attached instrument data over USB and Ethernet. My restriction here is having two wires or more to plug all instrumentation in - at least one for USB and at least one for ethernet.
... (16 Replies)
Discussion started by: fedora18
16 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)