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.
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
This User Gave Thanks to MichaelFelt For This Post:
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)
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)
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)
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)
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)
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)
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)
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
LEARN ABOUT MINIX
pmconfig
pmconfig(1M) System Administration Commands pmconfig(1M)NAME
pmconfig - Configure the Power Management system
SYNOPSIS
/usr/sbin/pmconfig [-r]
DESCRIPTION
The pmconfig utility sets the Power Management and suspend-resume configuration. User has permission to change Power Management configu-
ration using pmconfig only if he is allowed to do so according to PMCHANGEPERM keyword of /etc/default/power. User has permission to change
the suspend-resume configuration using pmconfig only if he is allowed to do so according to the CPRCHANGEPERM keyword of
/etc/default/power. See FILES section below for a description of the PMCHANGEPERM and CPRCHANGEPERM keywords of /etc/default/power.
Based on user permissions, pmconfig first resets the Power Management and/or suspend-resume state back to its default and then reads
the new Power Management and/or suspend-resume configuration from /etc/power.conf and issues the commands to activiate the new configu-
ration. The pmconfig utility is run at system boot. This utility can also be run from the command line after manual changes have been made
to the /etc/power.conf file. For editing changes made to the /etc/power.conf file to take effect, users must run pmconfig.
The preferred interface for changing Power Management and suspend-resume configuration is dtpower(1M).
OPTIONS
The following options are supported:
-r Reset Power Management and suspend-resume state to default and exit. User must have both Power Management and suspend-resume
configuration permission for this option.
EXIT STATUS
The following exit values are returned:
0 Upon successful completion
>0 An error occurred
FILES
/etc/power.conf System Power Management configuration file
/etc/default/power File that controls permissions for system's Power Management and suspend-resume features. The PMCHANGEPERM key-
board controls the Power Management configuration permissions, while the CPRCHANGEPERM keyword controls the sus-
pend-resume configuration permissions.
Allowed values are:
all Any user can change the configuration.
- No one except super-user can change the configuration.
<user1, user2,...> A user in this user list or a super-user can change the configuration. The user list is a space and/or comma (,)
separated list. You must enclose the list in < and > characters.
console-owner A user who owns the system console device node or a super-user can change the configuration.
The default values are PMCHANGEPERM=console-owner and CPRCHANGEPERM=console-owner.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWpmu |
+-----------------------------+-----------------------------+
|Interface stability |Unstable |
+-----------------------------+-----------------------------+
SEE ALSO svcs(1), powerd(1M), power.conf(4), svcadm(1M), attributes(5), smf(5), cpr(7), pm(7D)
Using Power Management
NOTES
The pmconfig service is managed by the service management facility, smf(5), under the service identifier:
svc:/system/power:default
Administrative actions on this service, such as enabling, disabling, or requesting restart, can be performed using svcadm(1M). The ser-
vice's status can be queried using the svcs(1) command.
DIAGNOSTICS
If the program cannot open the configuration file, it prints an error message to standard error. If the program encounters a syntax error
in the configuration file, it prints an error message and the line number of the error in the configuration file. It then skips the rest
of the information on that line and processes the next line. Any configuration information already processed on the line containing the
error is used. If user does not have permission to change Power Management and/or suspend-resume configuration, and configuration file has
entries for which user doesn't have permission, it process the entries for which user has permissions and prints error on rest.
SunOS 5.10 12 Aug 2004 pmconfig(1M)