11-30-2015
Hi all,
thanks for the helps, we found the problem.
The point is that we have a server which is connected to another device ( a battery with RS232) and, therefore that battery send a message to V440 to power-off, but not to power on.
So, wen the system power off all the instalation, we think the battery send a "Init 0" to the server, and after some minutes the server is powered off / plug out.
After that, we plug in the server and it power on automatically, and of course it boots with command
setenv auto-boot? true
But when we format the server we did a shutdown and power-off with console and, looks like that in that way the system does not power on automatically.....
Thanks anyway for the help
10 More Discussions You Might Find Interesting
1. Solaris
Hi Friends,
My solaris box V440 got stucked. I couldn't accessit from the remote console. Finally i restarted the box.
Can you tell me what are the ways we can find out the issues
and what are the logs we can check other than /var/log/messages.
Thanks
Jinu (1 Reply)
Discussion started by: Jinu
1 Replies
2. SCO
After System power get failed
File system is not getting mounted in read- write mode (1 Reply)
Discussion started by: gtkpmbpl
1 Replies
3. Solaris
Hello,
I've a very weird problem with one of the machines. When I try to boot off a working DVD that I used to install another system with it spits out the following message:
Sun Fire V440, No Keyboard
Copyright 2007 Sun Microsystems, Inc. All rights reserved.
OpenBoot 4.22.33, 8192 MB... (14 Replies)
Discussion started by: stoci
14 Replies
4. AIX
Can u please help me in knowing the details of the servers needed,
FIBRE CABLES, HA softwares, VIO Softwares and other details.
I googled through out and couldnt get a clear idea of it. Please help me (6 Replies)
Discussion started by: Sounddappan
6 Replies
5. Solaris
Hi:
I bougth an used Sun Fire v440, and It have a firmware password. When I turn on the server, it ask for firmware password. (I don 't know what is the correct password). I can access to SC, but when I want to access to OBP, Firmware Password appears again. I remove the battery for two hours,... (1 Reply)
Discussion started by: mguazzardo
1 Replies
6. Solaris
Got a T2000 which has got the 2.5" SAS drives. Want to be able, if I can, to connect to USB caddy and connect to a V440.
Anyone ever tried this? To be honest, having problems even finding a SAS-USB caddy. (0 Replies)
Discussion started by: psychocandy
0 Replies
7. Solaris
Hi,
I have Sun Solaris V440, every two days or so, the system crashes and it's at OK prompt. After that I do the FSCK and clear all the bad sectors. Then system stays up for close to 48 hours. Then it crashes again. I checked the logs and I don't see anything under /var/adm/messages file.
... (1 Reply)
Discussion started by: samnyc
1 Replies
8. Solaris
Hi,
I have a SUN Fire V440 server running Solaris 8. One of the 4 disks do not appear when issued the format command. The "ready to remove" LED is not on either.
Metastat command warns that this disk "Needs maintenace". Can I just shutdown and power off the machine and then insert an... (5 Replies)
Discussion started by: Echo68
5 Replies
9. AIX
Folks,
Again a very silly question :D Could someone tell me, how to determine the power family(540, 520, 575, 595 etc) just by looking into the model # info from prtconf/lsconf o/p of the lpar?
I dont want run a search on any search engine to find out the power family or hit IBM website to... (3 Replies)
Discussion started by: thisissouvik
3 Replies
10. AIX
Hello Forum,
I am very newbie with AIX.
We have 2 AIX 9111-285 servers. The OS version is 5.3.
After the power outage, they did not come up.
I try to unplug the power cable and re-connect after 1 minutes but do not help.
Both display the same reference code 110000AC on the front panel... (6 Replies)
Discussion started by: lilyn
6 Replies
CLONE(8) NUT Manual CLONE(8)
NAME
clone - UPS driver clone
NOTE
This man page only documents the specific features of the clone driver. For information about the core driver, see nutupsdrv(8).
DESCRIPTION
This driver, which sits on top of another driver socket, allows users to group clients to a particular outlet of a device and deal with
this output as if it was a normal UPS.
EXTRA ARGUMENTS
This driver supports the following settings:
load.off=command
Recommended. Set the command on the "real" UPS driver that will be used to switch off the outlet. You need both load.off and load.on in
order to power cycle the outlet. Otherwise, shutting down the clients powered by an outlet is a one way street (see IMPORTANT).
load.on=command
Recommended. Set the command on the "real" UPS driver that will be used to switch on the outlet. You need both load.off and load.on in
order to power cycle the outlet. Otherwise, shutting down the clients powered by an outlet is a one way street (see IMPORTANT).
load.status=value
Recommended. Set the variable on the "real" UPS driver that will be used to indicate the outlet status (i.e. on/off). If not specified,
the clone driver will attempt to keep track of the outlet status, but this is less reliable.
offdelay=num
Set the timer (in seconds) before the outlet is turned off after the shutdown condition (OB LB) for this outlet is met or a command to
shutdown was issued. Defaults to 120 seconds.
ondelay=num
Set the timer (in seconds) for the outlet to switch on in case the power returns after the oulet has been switched off. Defaults to 30
seconds.
mincharge=value
Set the remaining battery level when the clone UPS switches to LB (percent).
minruntime=value
Set the remaining battery runtime when the clone UPS switches to LB (seconds).
IMPLEMENTATION
The port specification in the ups.conf(5) reference the driver socket that the "real" UPS driver is using. For example:
[realups]
driver = usbhid-ups
port = auto
[clone-outlet-1]
driver = clone
port = usbhid-ups-realups
load.on = outlet.1.load.on
load.off = outlet.1.load.off
load.status = outlet.1.status
[...]
IMPORTANT
Unlike a real UPS, you should not configure a upsmon master for this driver. When a upsmon master sees the OB LB flags and tells the upsd
server it is OK to initiate the shutdown sequence, the server will latch the FSD status and it will not be possible to restart the systems
connected without restarting the upsd server.
This will be a problem if the power returns after the clone UPS initiated the shutdown sequence on it's outlet, but returns before the real
UPS begins shutting down. The solution is in the clone driver, that will insert the FSD flag if needed without the help of a upsmon master.
CAVEATS
The clone UPS will follow the status on the real UPS driver. You can only make the clone UPS shutdown earlier than the real UPS driver, not
later. If the real UPS driver initiates a shutdown, the clone UPS driver will immediately follow.
Be aware that the commands to shutdown/restart an outlet on the real UPS drivers are not affected, so if you tell the real UPS driver to
shutdown the outlet of the clone UPS driver, your clients will lose power without warning.
AUTHOR
Arjen de Korte <adkorte-guest@alioth.debian.org>
SEE ALSO
upscmd(1), upsrw(1), ups.conf(5), nutupsdrv(8)
Internet Resources:
The NUT (Network UPS Tools) home page: http://www.networkupstools.org/
Network UPS Tools 05/21/2012 CLONE(8)