Sponsored Content
Full Discussion: rebooting HMC
Operating Systems AIX rebooting HMC Post 302622385 by johnf on Thursday 12th of April 2012 05:44:26 AM
Old 04-12-2012
Quote:
Originally Posted by manoj.solaris
Hi,

I would like to know wheather rebooting HMC will impact on Management Systems or Lpar inside it is showing?

or I have to shutdown LPAR then only reboot HMC.
Rebooting the HMC does not have any affect on the running systems. The only consequence of such an action is if an LPAR / frame were to go defective whilst the HMC is coming back. Also the listing of the systems will not change when the HMC comes back unless system discovery has been set to run on reboot.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

soft rebooting

When I do a hard reboot, the system recognizes both the ttya and the ttyb, but when I do a hard reboot, it only doesn't recognize the ttyb. Is there a way I can fix this??? Thanks!:confused: (5 Replies)
Discussion started by: nattie_h
5 Replies

2. UNIX for Advanced & Expert Users

Problems when rebooting the system

Hi ! I am working on a server. We have ABAQUS installed on it. I added a compiler to .env file and added usr/local...../IMSL/... to the path. Then i restarted the computer and I get this error: when I am doing interactive option (Red hat Lunix OS) Start service local Yes/no/Continue? no... (1 Reply)
Discussion started by: dsmv
1 Replies

3. UNIX for Dummies Questions & Answers

Server rebooting frequently

O/P of the uname -a Server Server 4.0 3.0 3516 Pentium IV(TM)-ISA/PCI Server is getting rebooted frequetly... I don't know what is the problem in server ... Any help why the server is getting rebooted frequetly. Can i check what is the problem like in log files (5 Replies)
Discussion started by: srikanthus2002
5 Replies

4. Solaris

rebooting resetting loop

while installing unix solaris I found that one of the CD's is corupted so I bring another copy of solaris CD's and type reboot instead of 'reboot cdrom' then the server goes in infinite loop of rebooting resetting??I tried to use ctrl+break but didnt work....how can I break this loop....plz help?? (4 Replies)
Discussion started by: mm00123
4 Replies

5. Shell Programming and Scripting

Not able to 'su' to other user when rebooting the server

Hi All, I have created one script with starting letter 'S' (Example: Start) and stored in the path "/etc/rc.d/". This script was called automatically when we reboot the server. In this script i am using 'su' command to switch other user but it is not working, it giving some error. su... (2 Replies)
Discussion started by: Selva_Kumar
2 Replies

6. Linux

Rebooting Mounted servers

Hi All, We have two servers DSERV1(red hat 8.0) and DSERV2(scounix 3.2) where DSERV1 is the NFS server and DSERV2 is the NFS client. We want to reboot these servers and wanted to know the steps(precautions) we have to follow in order to do this. After reboot should we do anything specific to... (2 Replies)
Discussion started by: jisha
2 Replies

7. AIX

hmc not rebooting

Anyone faced this? I rebooted the HMC through command line after patch installation (hmcshutdown -t now -r) The strange thing happened was the hmc never rebooted, I was not able to connect it through graphical view or through ssh, but the session through which i issued the command was still... (4 Replies)
Discussion started by: balaji_prk
4 Replies

8. Solaris

error while rebooting box

I got following while whenver i reboot my box WARNING: add_spec: No major number for hpfc WARNING: add_spec: No major number for hpfc Error: Unable to init open counts. Kernel struct change? and hpfc is related to agilent fiber channel driver .. i do not know why it requires as i 've... (1 Reply)
Discussion started by: fugitive
1 Replies

9. Red Hat

Server rebooting unexpectedly

hi, I have been working on Solaris am very new to linux. My concern is as it goes....our server is getting rebooted automatically and I am not able to understand anything from the var log messages. Could anybody help me out in troubleshooting the issue. 2.6.18-128.el5 #1 x86_64 GNU/Linux is... (1 Reply)
Discussion started by: EmbedUX
1 Replies

10. What is on Your Mind?

Rebooting a career

Apologies if this is not the correct place to post this. I used to have a job supporting several custom applications that ran on Unix platforms. I used shell scripting, sed, awk, and SQL, but all on a pretty basic level. I also performed non-technical tasks like helping with project management,... (4 Replies)
Discussion started by: intranslation
4 Replies
SYSTEMD-HALT.SERVICE(8) 				       systemd-halt.service					   SYSTEMD-HALT.SERVICE(8)

NAME
systemd-halt.service, systemd-poweroff.service, systemd-reboot.service, systemd-kexec.service, systemd-shutdown - System shutdown logic SYNOPSIS
systemd-halt.service systemd-poweroff.service systemd-reboot.service systemd-kexec.service /lib/systemd/systemd-shutdown /lib/systemd/system-shutdown/ DESCRIPTION
systemd-halt.service is a system service that is pulled in by halt.target and is responsible for the actual system halt. Similarly, systemd-poweroff.service is pulled in by poweroff.target, systemd-reboot.service by reboot.target and systemd-kexec.service by kexec.target to execute the respective actions. When these services are run, they ensure that PID 1 is replaced by the /lib/systemd/systemd-shutdown tool which is then responsible for the actual shutdown. Before shutting down, this binary will try to unmount all remaining file systems, disable all remaining swap devices, detach all remaining storage devices and kill all remaining processes. It is necessary to have this code in a separate binary because otherwise rebooting after an upgrade might be broken -- the running PID 1 could still depend on libraries which are not available any more, thus keeping the file system busy, which then cannot be re-mounted read-only. Immediately before executing the actual system halt/poweroff/reboot/kexec systemd-shutdown will run all executables in /lib/systemd/system-shutdown/ and pass one arguments to them: either "halt", "poweroff", "reboot" or "kexec", depending on the chosen action. All executables in this directory are executed in parallel, and execution of the action is not continued before all executables finished. Note that systemd-halt.service (and the related units) should never be executed directly. Instead, trigger system shutdown with a command such as "systemctl halt" or suchlike. SEE ALSO
systemd(1), systemctl(1), systemd.special(7), reboot(2), systemd-suspend.service(8) systemd 237 SYSTEMD-HALT.SERVICE(8)
All times are GMT -4. The time now is 02:36 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy