08-31-2015
The GSP shows, correctly, that slot 1 is "Normal" because the power supply has been replaced. Resetting the GSP with that command did nothing for the status in cstm which shows "component failed" (which it should not be).
7 More Discussions You Might Find Interesting
1. HP-UX
Hi,
Newbie here......I am an new guy on HP-Ux... may i ask all the the guru's and who has eperienced here to enlightened me on how to use the CSTM command.
My goal is to view the current HW installed on the Server.
Thanks in advance. (1 Reply)
Discussion started by: renobal
1 Replies
2. Red Hat
Hello guys:
I'm a beginner in this exciting world of open spource and linux. I'm working as a support engineer and a customer send back to me a sysreport from his system running redhat 4. the customer has a power supply failed in his server and to see it and justify the replacement I required a... (0 Replies)
Discussion started by: amani
0 Replies
3. HP-UX
Hi,
I know this has been discussed a number of time but i could not get the exact answer. So need help again.
Issue:
The two command for same file system shows different size.
du -sk shows toatl size is 12780685 KB while df -k 45289229 used allocated Kb
/oxt/mantran/bin $ du -sk... (8 Replies)
Discussion started by: malaya_17
8 Replies
4. Solaris
Hi Gurus
I am in a strange situation.
I have a SUN sparc server . The server was having an IP say X..... (this IP X is now being used by another server)..... I have just installed fresh solaris 9 OS on the same server and given new IP say Y.
I also configured probe based IPMP with ce0 and... (2 Replies)
Discussion started by: ningy
2 Replies
5. HP-UX
Hello,
On a HP-UX 10.20 server I've executed something similar to this command:
# echo 'selall;info;wait;infolog;view;done' | /usr/sbin/cstm
But it returns sometype of "argument list too long" error.
I suppose there is a way to fix it by using xargs but I can't figure it out.
Any... (7 Replies)
Discussion started by: asanchez
7 Replies
6. AIX
Hi,
As in Management Modules of IBM it is possible to find out wheather out of dual powersupply , if one goes down.
is it possible to find out in HMC to find out if one power supply goes down of P Series server? if server is remotely
HOw to find out if one power supply of server is down?... (1 Reply)
Discussion started by: manoj.solaris
1 Replies
7. Shell Programming and Scripting
I am using a script like this
source=$1
if ;
then
echo "got it"
else
echo "lost it"
fi
But the script is giving th error like
script.ksh: ==: unknown test operator
Can i know , is the syntax iam using is correct or suggest me a good way.
... (3 Replies)
Discussion started by: nani1984
3 Replies
power(9E) Driver Entry Points power(9E)
NAME
power - power a device attached to the system
SYNOPSIS
#include <sys/ddi.h>
#include <sys/sunddi.h>
int prefixpower(dev_info_t *dip, int component, int level);
INTERFACE LEVEL
Solaris DDI specific (Solaris DDI). This entry point is required. If the driver writer does not supply this entry point, the value NULL
must be used in the cb_ops(9S) structure instead.
PARAMETERS
dip Pointer to the device's dev_info structure.
component Component of the driver to be managed.
level Desired component power level.
DESCRIPTION
The power(9E) function is the device-specific Power Management entry point. This function is called when the system wants the driver to set
the power level of component to level.
The level argument is the driver-defined power level to which the component needs to be set. Except for power level 0, which is inter-
preted by the framework to mean "powered off," the interpretation of level is entirely up to the driver.
The component argument is the component of the device to be power-managed. The interpretation of component is entirely up to the driver.
When a requested power transition would cause the device to lose state, the driver must save the state of the device in memory. When a
requested power transition requires state to be restored, the driver must restore that state.
If a requested power transition for one component requires another component to change power state before it can be completed, the driver
must call pm_raise_power(9F) to get the other component changed, and the power(9E) entry point must support being re-entered.
If the system requests an inappropriate power transition for the device (for example, a request to power down a device which has just
become busy), then the power level should not be changed and power should return DDI_FAILURE.
RETURN VALUES
The power() function returns:
DDI_SUCCESS Successfully set the power to the requested level.
DDI_FAILURE Failed to set the power to the requested level.
CONTEXT
The power() function is called from user or kernel context only.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Interface stability |Evolving |
+-----------------------------+-----------------------------+
SEE ALSO
attach(9E), detach(9E), pm_busy_component(9F), pm_idle_component(9F), pm_raise_power(9F), cb_ops(9S)
Writing Device Drivers
Using Power Management
SunOS 5.10 12 Dec 2003 power(9E)