Sponsored Content
Operating Systems AIX Determining how long device has been in defined state Post 302766811 by jwholey on Tuesday 5th of February 2013 12:42:54 PM
Old 02-05-2013
Thanks for the updates... appreciated. One of the SA's who supports my app has advised me that a few network interfaces went into defined state over a year ago. I'm not suggesting something nefarious is going on, I would simply like to know how he determined that.
 

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... (0 Replies)
Discussion started by: mgmk.84
0 Replies

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. (2 Replies)
Discussion started by: manoj.solaris
2 Replies

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. ... (0 Replies)
Discussion started by: Tanmoy
0 Replies

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. (2 Replies)
Discussion started by: snchaudhari2
2 Replies

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... (4 Replies)
Discussion started by: anuragr
4 Replies
pm_trans_check(9F)					   Kernel Functions for Drivers 					pm_trans_check(9F)

NAME
pm_trans_check - Device power cycle advisory check SYNOPSIS
#include <sys/sunddi.h> int pm_trans_check(struct pm_trans_data *datap, time_t *intervalp); INTERFACE LEVEL
Solaris DDI specific (Solaris DDI) PARAMETERS
datap Pointer to a pm_trans_data structure intervalp Pointer to time difference when next power cycle will be advised DESCRIPTION
The pm_trans_check() function checks if a power-cycle is currently advised based on data in the pm_trans_data structure. This function is provided to prevent damage to devices from excess power cycles; drivers for devices that are sensitive to the number of power cycles should call pm_trans_check() from their power(9E) function before powering-off a device. If pm_trans_check() indicates that the device should not be power cycled, the driver should not attempt to power cycle the device and should fail the call to power(9E) entry point. If pm_trans_check() returns that it is not advised to power cycle the device, it attempts to calculate when the next power cycle is advised, based on the supplied parameters. In such case, intervalp returns the time difference (in seconds) from the current time to when the next power cycle is advised. If the time for the next power cycle cannot be determined, intervalp indicates 0. To avoid excessive calls to the power(9E) entry point during a period when power cycling is not advised, the driver should mark the corre- sponding device component busy for the intervalp time period (if interval is not 0). Conveniently, the driver can utilize the fact that calls to pm_busy_component(9F) are stacked. If power cycling is not advised, the driver can call pm_busy_component(9F) and issue a time- out(9F) for the intervalp time. The timeout() handler can issue the corresponding pm_idle_component(9F) call. When the format field of pm_trans_data is set to DC_SCSI_FORMAT, the caller must provide valid data in svc_date[], lifemax, and ncycles. Currently, flag must be set to 0. struct pm_scsi_cycles { int lifemax; /* lifetime max power cycles */ int ncycles; /* number of cycles so far */ char svc_date[DC_SCSI_MFR_LEN]; /* service date YYYYWW */ int flag; /* reserved for future */ }; struct pm_trans_data { int format; /* data format */ union { struct pm_scsi_cycles scsi_cycles; } un; }; RETURN VALUES
1 Power cycle is advised 0 Power cycle is not advised -1 Error due to invalid argument. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Interface Stability |Committed | +-----------------------------+-----------------------------+ SEE ALSO
power.conf(4), attributes(5), power(9E) Writing Device Drivers Using Power Management SunOS 5.11 16 Oct 1999 pm_trans_check(9F)
All times are GMT -4. The time now is 12:58 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy