Determining how long device has been in defined state Post: 302766291

Sponsored Content

Operating Systems AIX Determining how long device has been in defined state Post 302766291 by zaxxon on Monday 4th of February 2013 01:44:19 PM

02-04-2013

Registered User

Afaik something like that is not being logged right out of the box. You could check the ODM, if there is any kind of timestamp somewhere associated with the appropriate interface (have no AIX to check at the moment), but I quite doubt that. I also doubt it is written to the Error Report, but you can try out that very easy. Error Report is bound to a buffer size and it`s entries will be overwritten, if too many messages go in there.

If you have Auditing (Accounting and Auditing on AIX 5L) set up you could be lucky to find some traces of any shell input. If not, you could set this up if things like this are in your interesst.

You could also think about to use something to track config changes like SPM.
There was also an AIX native tool, but I do not remember it�s name. Xray was using it - I will drop him a PM, to help me recall it�s name Smilie

If the user had to use sudo to issue the command, you might be lucky with the sudo logs.

If it was done via smitty, check smitty.log.

zaxxon

View Public Profile for zaxxon

Find all posts by zaxxon

5 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Hitting with custom port in CLOSE_WAIT state for long time in solaris 10

Hi, Occasionally I am getting the port state in CLOSE_WAIT for long time in the solaris server. I am not sure is it application problem or not. Because we are using port 9009 for Tomcat process in our web application, some time when I start the application, the port 9009 is in CLOSE_WAIT...

2. AIX

Device Available / Define state

Hi, I would like to know wheather it is possible to make device in availabe state? if for same reason os is not able to make it in available state. and it is in define state.

3. Red Hat

Unable To Activate Ethernet Network Device in RHEL 5.5 - e100 device eth0 does not seem to be presen

Hi All, Could anyone please help to resolve the below problem. I installed RHEL5.5 in my desktop.But when i try to activate the ethernet connection then it gives me the error. I spent 2 days for the above and go through with several suggestion found by googling. But no luck. ...

4. AIX

Open firmware state to running state

Hi Admins, I am having a whole system lpar in open firmware state on HMC. How can I bring it to running state ? Let me know. Thanks.

5. HP-UX

Failed to open tape device /dev/rmt/0mn:Device busy (errno = 16)

Hi, Unable to make tape backup, please help. /opt/ignite/bin/make_tape_recovery -a /dev/rmt/?mn -I -v -m tar -x inc_entire=vg00 * Creating local directories for configuration files and archive. ======= 04/25/16 16:28:08 IST Started /opt/ignite/bin/make_tape_recovery. (Mon...

LEARN ABOUT OSF1

cfgmgr_get_state

cfgmgr_get_state(9r)													      cfgmgr_get_state(9r)

NAME

       cfgmgr_get_state - General: Determines the configuration state

SYNOPSIS

       int cfgmgr_get_state(
	       char *driver_name,
	       int *driver_cfg_state );

ARGUMENTS

       Specifies  the  name  of  the device driver whose configuration state you want to obtain. 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  (fol-
       lowed  by  a  colon)  in  the  sysconfigtab  file fragment, which gets appended to the /etc/sysconfigtab database during the driver product
       installation.  Returns one of the following state value bits to the driver_cfg_state argument:  The  specified  device  driver  is  in  the
       dynamic	configuration  state.  This  means  the  driver was dynamically configured into the kernel.  The specified device driver is in the
       static configuration state. This means the driver was statically configured into the kernel.

DESCRIPTION

       The cfgmgr_get_state routine obtains the configuration state of the specified device driver. The specified device driver is in  either  the
       static configuration state or the dynamic configuration state.

       The  cfgmgr_get_state  routine returns the state value in the driver_cfg_state argument. Driver writers should store this state value in an
       xx_is_dynamic variable or some similarly named variable.

       You typically call the cfgmgr_get_state routine in the CFG_OP_CONFIGURE entry point of the device driver's configure routine.

RETURN VALUES

       Upon successful completion, cfgmgr_get_state returns the value ESUCCESS. This success value indicates that  cfgmgr_get_state  returned  the
       configuration state of the specified device driver in the driver_cfg_state argument. Otherwise, cfgmgr_get_state returns one of the follow-
       ing 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_get_state cannot return the configuration state of the specified device
       driver in the driver_cfg_state argument.  The device driver that you specified in the driver_name argument is not a valid name.

EXAMPLES

       See Writing Device Drivers: Tutorial for a code example of the cfgmgr_get_state interface.

SEE ALSO

       Routines: cfgmgr_set_status(9r)

															      cfgmgr_get_state(9r)