ProLiant Servers (ML,DL,SL)
1827084 Members
1622 Online
109713 Solutions
New Discussion

Re: ML 350 g5 seems to overheat

 
SOLVED
Go to solution

Re: ML 350 g5 seems to overheat

OK, thanks to all of you for help to solve my trouble; only one last question before closing this thread. I noticed the old server ML 350 g5 has a power reading of 157 W, while the new ML 350 g6 has only 58 W! Anf yet the latter is working more now. Is it normal? Has the power efficiency of ML 350 so dramatically improved from g5 to g6? Or there is something else wrong with my old g5?
gregersenj
Honored Contributor

Re: ML 350 g5 seems to overheat

Well Holger, seems like you got a new server :)

Paolo, I don't know the numbers, but power effincecy is improving, even though performance and workload is increased.

BR
/jag

Accept or Kudo

Re: ML 350 g5 seems to overheat

Just when I thought the problem was over, here it is again and doubled!
Yesterday night both server g5 and g6 went down together!
From the iLO 2 log it results a "Server power removed" preceded by a "iLO 2 network link down" (this is something new and at the same time 22:18, what does it mean?); a few hours before a "SSH login failure from:" on both server from the same IP.

Now the only thing I can guess is a hacker attack. Or have You another explanation?

Following is the Log of the old server (the other is similar, but power removed is just at 22:18)

Informational iLO 2
06/14/2011 07:48 06/14/2011 07:48 1
On-board clock set; was previously [NOT SET].

Informational iLO 2
[NOT SET] [NOT SET] 1
Server power restored.

Caution iLO 2 [NOT SET] [NOT SET] 1
Power restored to iLO 2.

Informational iLO 2
06/13/2011 22:42 06/13/2011 22:42 1
Server power removed.

Caution iLO 2
06/13/2011 22:18 06/13/2011 22:18 1
iLO 2 network link down.

Caution iLO 2
06/13/2011 15:21 06/13/2011 15:21 1
SSH login failure from: 85.172.209.59(DNS name not found).

Re: ML 350 g5 seems to overheat

I withdraw everything!
It was just a power problem in our school! Very simple, no hacker.
The SSH login failure was just a failure after all!!

Beg your pardon for the useless post!
And I think I can really close the thread now.