- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- Server Management - Remote Server Management
- >
- RE:Problem in issuing ILO commands in DL320G5s ser...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-07-2011 01:16 AM
тАО02-07-2011 01:16 AM
We are using some DL320G5 servers.
Problem is: When we are issuing the ILO command "stop system1" through "dante client" the system "fails to shut down".
The "start system1" for poweron is working though.
The servers are responding properly when we are operating through the GUI.
Please help if anyone is having the same problem and has got any solution.
Thanks in advance.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-07-2011 06:49 AM
тАО02-07-2011 06:49 AM
Re: RE:Problem in issuing ILO commands in DL320G5s server
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-07-2011 06:59 AM
тАО02-07-2011 06:59 AM
Re: RE:Problem in issuing ILO commands in DL320G5s server
Thanks for your suggestion. But I am using Ubuntu Lucid as my Operating System. Over it I have a "dante client" installed for creating socks connection to the iLO server. I am not using Windows OS. I am sorry for not mentioning these details earlier.
I am facing this problem with DL320G5 servers only.
Badly stuck!! Need more suggestions.
Thanks for all your responses in advance.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-07-2011 04:29 PM
тАО02-07-2011 04:29 PM
Re: RE:Problem in issuing ILO commands in DL320G5s server
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-07-2011 10:06 PM
тАО02-07-2011 10:06 PM
Re: RE:Problem in issuing ILO commands in DL320G5s server
I am using "press and hold" from GUI.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-08-2011 05:18 AM
тАО02-08-2011 05:18 AM
SolutionAs always, make sure you running the latest system ROM and iLO firmware.
When you issue the stop /system1 what is returned from iLO? You should see something like:
hpilo-> stop /system1
status=0
status_command=COMMAND COMPLETE
power-off signal sent to host server
The command "stop /system1" sends a gracefull shutdown command to an ACPI aware OS. Would be the same as doing a momentary press in the iLO GUI
I have a DL380 G5 Runing SLES11, depending on what state the system is in, the command reacts as follows:
anytime the OS is not "up" = system turns off
OS running at GUI login prompt (init 5) = popup asking if system should shutdown, restart, or hibernate
OS running no GUI (init 3) = system powers off gracefully
As a last resort you can issue this command which is the same as the GUI "press and hold"
stop /system1 -f
"Press and hold" is just like yanking the power cord; not the best option as you can corrupt the filesystem.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-08-2011 06:47 AM
тАО02-08-2011 06:47 AM
Re: RE:Problem in issuing ILO commands in DL320G5s server
I was missing out on the fact that by issuing "stop system1" only I was actually doing "momentary press", whereas the need was powering the server off.
Thanks again.
Problem Solved! :)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-08-2011 07:21 AM
тАО02-08-2011 07:21 AM
Re: RE:Problem in issuing ILO commands in DL320G5s server
The nodes I want to poweroff is in init 3.
But here through CLI if I issue only "stop system1" exactly the message is shown as posted by Jimmy. But unfortunately due to some unknown reason the system doesn't poweroff. Even I tried some multiple times it did not poweroff.
So, currently I am using the "stop system1 -f" only to power off. As pointed out by Jimmy it may corrupt the filesystem, but for our scenario it won't matter much since we are doing fresh OS installations.
For time being the problem solved. A huge releif, but I do mention the system running without gui is not powering off gracefully.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-08-2011 07:29 AM
тАО02-08-2011 07:29 AM
Re: RE:Problem in issuing ILO commands in DL320G5s server
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-08-2011 07:39 AM
тАО02-08-2011 07:39 AM
Re: RE:Problem in issuing ILO commands in DL320G5s server
Some more details, I am testing with some old kernels (2.6.18.x) and some not so old (2.6.32.x) due to specific reasons.