Sponsored Content
Operating Systems AIX Automatic Server bootup after power outage? Post 302951354 by MichaelFelt on Wednesday 5th of August 2015 12:27:47 PM
Old 08-05-2015
I hope I have uploaded two files - one titled autostartPolicypng and the other is startpolicy.png

These are screencaptures from the web-based ASMI - Advanced System Management Interface. I do not have an HMC, so I use the web interface. HMC would have a different way to change these.

Approach ASMI as the system firmware IP address as https://IP_addressOrHostname and login.

Now you should see - on the left - an area titled "Power/Restart Control".
The panel entitled "Power On/Off System" has a selection entitled "System firmware start policy". This is (mainly) for a normal startup.

The choice you want to look at is in the left menu as: "Auto Power Restart". Make sure this is enabled.

HOWEVER, if you system is managed by an HMC all partitions get started, more or less in parallel - so the ones that are dependent on a VIOS may not start as expected. When you do not have an HMC - the VIOS - as IVM (integrated Virtualization Manager) has that role and will start client partitions AFTER it has started itself - and so the system returns as much as possible (depending mainly on the integrity/availability of external storage).

Short advice: get on the ASMI web interface and make you adjustments. Or use the HMC to do the same.

Hope this helps!

Michael
Automatic Server bootup after power outage?-autostartpolicypng
Automatic Server bootup after power outage?-startpolicypng
This User Gave Thanks to MichaelFelt For This Post:
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Why not automatic bootup

Evry time I start up my mavhine ,have to type in unix at Boot : Is there a way unix should bootup automatically? Asif (2 Replies)
Discussion started by: asif iqbal
2 Replies

2. Solaris

Booting up problem after power outage

hi guys, i'm new so don't bite too hard. having a problem booting up a V210 running sol9 on after a power outage... an init5 was done but not a init0 before the power cut... so now when booting up it gives the ff: SC Alert: Host System has Reset Probing system devices Probing memory... (2 Replies)
Discussion started by: lungsta
2 Replies

3. AIX

AIX server freezes on bootup

Issue: AIX server freezes on bootup. Server AIX ver 4.3.3.0 When the AIX server reboots it negotiates NIS. During startup of NFS, customer gets one or more of the following error messages: 0513-056 Timeout waiting for command response. If you specified a foreign host, see the /etc/inittab file... (1 Reply)
Discussion started by: srzaman1
1 Replies

4. Solaris

Automatic reboot does not work after power failure

Hi all, I have a server SUN FUJITSU in solaris 10 ; result of uname -a is : SunOS MOBD1 5.10 Generic_118833-03 sun4us sparc FJSV,GPUZC-M I have configured the eeprom to auto-boot as usual and this automatic reboot does not work in case of power failure. I must type "boot" on the prompt "ok"... (5 Replies)
Discussion started by: aribault
5 Replies

5. Linux

Script under rc3.d not being executed on server bootup

Hello all, I have a script callled 'ABCstartup' setup under /etc/rc.d/init.d Softlink 'S91ABCstartup' pointing to above script has been created under /etc/rc.d/rc3.d The script is not being executed when the server restarts. The script runs successfully via manual execution:... (5 Replies)
Discussion started by: hemangjani
5 Replies

6. AIX

Role of sys admin during power outage in Data center

i am new to aix environment and all my servers are @ remote location just curious to know , what issues/tasks we will be facing when there is a power outage in a data centre, i heard outage's will be a challenging task for administrators.. any example of that sort will be a great help (2 Replies)
Discussion started by: rigin
2 Replies

7. Linux

Administrator responsibilities, in case of power outage?

Hi guys, I was wondering if you could share some of your knowledge, in the event of a power outage. Let presume you are on duty and you get a call at midnight because half of your cabinets have no power, air conditioning is down and you deal with a ton of 500 error messages on your boxes. ... (9 Replies)
Discussion started by: TECK
9 Replies

8. Solaris

Any specific time to reboot the sun server to avoid unplanned outage ??

Hi, Would like to know the uptime or specific time limit to reboot the sun microsystem to avoid unplanned outage. Regards,Tarun (9 Replies)
Discussion started by: taruntan
9 Replies

9. Red Hat

Linux Server Outage

We have Linux Server crash on last Friday of 25th It's is running on IBM x3650 hardware. We Have Red Hat Enterprise Linux Server release 5.9 (Tikanga) running on top of it. We were told to do Root Cause Analysis. So, Apart from looking /var/log/messages, Where can we check to get details on... (3 Replies)
Discussion started by: Sunil Koya
3 Replies

10. AIX

System can't boot up after power outage

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
pm_power_has_changed(9F)				   Kernel Functions for Drivers 				  pm_power_has_changed(9F)

NAME
pm_power_has_changed - Notify Power Management framework of autonomous power level change SYNOPSIS
#include <sys/ddi.h> #include <sys/sunddi.h> int pm_power_has_changed(dev_info_t *dip, int component, int level); INTERFACE LEVEL
Solaris DDI specific (Solaris DDI) PARAMETERS
dip Pointer to the device dev_info structure component Number of the component that has changed power level level Power level to which the indicated component has changed DESCRIPTION
The pm_power_has_changed(9) function notifies the Power Management framework that the power level of component of dip has changed to level. Normally power level changes are initiated by the Power Management framework due to device idleness, or through a request to the framework from the driver via pm_raise_power(9F) or pm_lower_power(9F), but some devices may change power levels on their own. For the framework to track the power level of the device under these circumstances, the framework must be notified of autonomous power level changes by a call to pm_power_has_changed(). Because of the asynchronous nature of these events, the Power Management framework might have called power(9E) between the device's autono- mous power level change and the driver calling pm_power_has_changed(), or the framework may be in the process of changing the power level when pm_power_has_changed() is called. To handle these situations correctly, the driver should verify that the device is indeed at the level or set the device to the level if it doesn't support inquirying of power levels, before calling pm_power_has_changed(). In addition, the driver should prevent a power(9E) entry point from running in parallel with pm_power_has_changed(). Note - If this function is called as a result of entry into the driver's attach(9E), detach(9E) or power(9E) entry point, this function must be called from the same thread which entered attach(9E), detach(9E) or power(9E). RETURN VALUES
The pm_power_has_changed() function returns: DDI_SUCCESS The power level of component was successfully updated to level. DDI_FAILURE Invalid component component or power level level. CONTEXT
This function can be called from user or kernel context. This function can also be called from interrupt context, providing that it is not the first Power Management function called by the driver. EXAMPLES
A hypothetical driver might include this code to handle pm_power_has_changed(9): static int xxusb_intr(struct buf *bp) { ... /* * At this point the device has informed us that it has * changed power level on its own. Inform this to framework. * We need to take care of the case when framework has * already called power() entry point and changed power level * before we were able to inform framework of this change. * Handle this by comparing the informed power level with * the actual power level and only doing the call if they * are same. In addition, make sure that power() doesn't get * run in parallel with this code by holding the mutex. */ ASSERT(mutex_owned(&xsp->lock)); if (level_informed == *(xsp->level_reg_addr)) { if (pm_power_has_changed(xsp->dip, XXUSB_COMPONENT, level_informed) != DDI_SUCCESS) { mutex_exit( &xsp->lock); return(DDI_INTR_UNCLAIMED); } } .... } xxdisk_power(dev_info *dip, int comp, int level) { mutex_enter( xsp->lock); ... ... } ATTRIBUTES
See attributes(5) for a description of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Stability level |Evolving | +-----------------------------+-----------------------------+ SEE ALSO
power.conf(4), pm(7D), attach(9E), detach(9E), power(9E), pm_busy_component(9F), pm_idle_component(9F), pm_raise_power(9F), pm_lower_power(9F), pm(9P), pm-components(9P) Writing Device Drivers SunOS 5.10 22 July 2004 pm_power_has_changed(9F)
All times are GMT -4. The time now is 10:15 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy