HP Ilo 4 User Guide

							Thefollowinginformationisdisplayed:
•FirmwareName—Thenameofthefirmware.
Thefirmwaretypeslistedonthispagevarybasedontheservermodelandconfiguration.
Formostservers,theHPProLiantSystemROMandtheiLOfirmwarearelisted.Otherpossible
firmwareoptionsincludethePowerManagementController,ServerPlatformServices,HP
SmartArray,IntelligentProvisioning,IntelligentPlatformAbstractionData(Gen9serversonly),
HPSmartStorageBattery(Gen9serversonly),andnetworkingadapters.
NOTE:Toviewfirmwareinformationforharddrives,navigatetotheSystem
Information→Storagepage.
•FirmwareVersion—Theversionofthefirmware.
UsingtheiLOEventLog
TheiLOEventLogprovidesarecordofsignificanteventsdetectedbyiLO.
Loggedeventsincludemajorservereventssuchasaserverpoweroutageoraserverreset,and
iLOeventssuchasunauthorizedloginattempts.Otherloggedeventsincludesuccessfulor
unsuccessfulbrowserandRemoteConsolelogins,virtualpowerandpower-cycleevents,clearing
thelog,andsomeconfigurationchanges,suchascreatingordeletingauserandregisteringfor
remotesupport.
iLOprovidessecurepasswordencryption,trackingallloginattemptsandmaintainingarecordof
allloginfailures.TheAuthenticationFailureLoggingsettingallowsyoutoconfigureloggingcriteria
forfailedauthentications.TheEventLogcapturestheclientnameforeachloggedentrytoimprove
auditingcapabilitiesinDHCPenvironments,andrecordstheaccountname,computername,and
IPaddress.
EarlierversionsoftheiLOfirmwaremightnotsupporteventsloggedbylaterversionsofiLO
firmware.Ifanunsupportedfirmwareversionlogsanevent,theeventislistedasUNKNOWN EVENT
TYPE.Youcancleartheeventlogtoeliminatetheseentries,orupdatethefirmwaretothelatest
supportedversion.
ViewingtheiLOEventLog
ToviewtheiLOEventLog,navigatetotheInformation→iLOEventLogpage.
UsingtheiLOEventLog171 
						

							Thelogdisplaysthefollowinginformation:
•id—TheeventIDnumber.Eventsarenumberedintheorderinwhichtheyaregenerated.
Bydefault,theiLOEventLogissortedbytheID,withthemostrecenteventatthetop.
•Severity—Theimportanceofthedetectedevent.
Possiblevaluesfollow:
◦Critical—Theeventindicatesaservicelossorimminentserviceloss.Immediateattention
isneeded.
◦Caution—Theeventissignificantbutdoesnotindicateperformancedegradation.
◦Informational—Theeventprovidesbackgroundinformation.
•Class—Thecomponentorsubsystemthatidentifiedtheloggedevent.
•LastUpdate—Thedateandtimewhenthelatesteventofthistypeoccurred.Thisvalueisbased
onthedateandtimestoredbytheiLOfirmware.
TheiLOdateandtimecanbesynchronizedthroughthefollowing:
◦SystemROM(duringPOSTonly)
◦InsightManagementAgents(intheOS)
◦NTPserver(configurediniLO)
◦OnboardAdministrator(serverbladesonly)
theiLOfirmwaredidnotrecognizethedateandtimewhenaneventwasupdated,[NOT
SET]isdisplayed.
•InitialUpdate—Thedateandtimewhenthefirsteventofthistypeoccurred.Thisvalueisbased
onthedateandtimestoredbytheiLOfirmware.
IftheiLOfirmwaredidnotrecognizethedateandtimewhentheeventwasfirstcreated,
[NOT SET]isdisplayed.
•Count—Thenumberoftimesthiseventhasoccurred(ifsupported).
Ingeneral,importanteventsgenerateaneventlogentryeachtimetheyoccur.Theyarenot
consolidatedintooneeventlogentry.
172UsingiLO 
						

							Whenlessimportanteventsarerepeated,theyareconsolidatedintooneeventlogentry,and
theCountandLastUpdatevaluesareupdated.Eacheventtypehasaspecifictimeinterval
thatdetermineswhetherrepeatedeventsareconsolidatedoraneweventislogged.
•Description—Thedescriptionidentifiesthecomponentanddetailedcharacteristicsofthe
recordedevent.
IftheiLOfirmwareisrolledbacktoanearlierversion,thedescriptionUNKNOWN EVENT
TYPEmightbedisplayedforeventsrecordedbythenewerfirmware.Youcanresolvethis
issuebyupdatingthefirmwaretothelatestsupportedversion,orbyclearingtheeventlog.
SavingtheiLOEventLog
TosavetheiLOEventLogasaCSVfile:
1.ClicktheViewCSVbutton.
TheiLOEventLogisdisplayedinaformatthatyoucancopyandpasteintoatexteditor.
2.CopythetextdisplayedintheiLOEventLogCSVwindow,andsaveitinatexteditorasa
*.csvfile.
3.ClickExittoclosethewindow.
ClearingtheiLOEventLog
UserswiththeConfigureiLOSettingsprivilegecancleartheiLOEventLogofallpreviouslylogged
information.
TocleartheiLOEventLog:
1.ClickClearEventLog.
Thefollowingmessageappears:
Are you sure you want to clear the iLO Event Log?
2.ClickOK.
Thefollowingeventisrecorded:
Event log cleared by .
UsingtheiLOEventLog173 
						

							UsingtheIntegratedManagementLog
TheIntegratedManagementLogprovidesarecordofhistoricaleventsthathaveoccurredonthe
server.EventsaregeneratedbythesystemROMandbyservicessuchastheiLOhealthdriver.
Loggedeventsincludeallserver-specificeventsrecordedbythesystemhealthdriver,including
operatingsysteminformationandROM-basedPOSTcodes.
EntriesintheIMLcanhelpyoudiagnoseissuesoridentifypotentialissues.Preventativeaction
mighthelptoavoiddisruptionofservice.
iLOmanagestheIML,whichyoucanaccessthroughasupportedbrowser,evenwhentheserver
isoff.Theabilitytoviewthelogwhentheserverisoffcanbehelpfulwhentroubleshootingremote
hostserverissues.
ExamplesofthetypesofinformationrecordedintheIMLfollow:
•Faninserted
•Fanremoved
•Fanfailure
•Fandegraded
•Fanrepaired
•Fanredundancylost
•Fansredundant
•Powersupplyinserted
•Powersupplyremoved
•Powersupplyfailure
•Powersuppliesredundancylost
•Powersuppliesredundant
•Temperatureoverthreshold
•Temperaturenormal
•Automaticshutdownstarted
•Automaticshutdowncanceled
•Drivefailure
ViewingtheIML
ToviewtheIML,navigatetotheInformation→IntegratedManagementLogpage.
174UsingiLO 
						

							TheIMLdisplaysthefollowinginformation:
•ThiscolumnincludesacheckboxnexttoeacheventwithCriticalorCautionstatus.Usethis
checkboxtoselectaneventtomarkasrepaired.
Formoreinformationaboutmarkingeventsasrepaired,see“Markingalogentryasrepaired”
(page176).
•id—TheeventIDnumber.Eventsarenumberedintheorderinwhichtheyaregenerated.
Bydefault,theIMLissortedbytheID,withthemostrecenteventatthetop.Afactoryreset
willresetthecounter.
•Severity—Theimportanceofthedetectedevent.
Possiblevaluesfollow:
◦Critical—Theeventindicatesaservicelossoranimminentserviceloss.Immediateattention
isneeded.
◦Caution—Theeventissignificantbutdoesnotindicateperformancedegradation.
◦Informational—Theeventprovidesbackgroundinformation.
◦Repaired—Aneventhasundergonecorrectiveaction.
•Class—Identifiesthecomponentorsubsystemthatidentifiedtheloggedevent.
•LastUpdate—Thedateandtimewhenthelatesteventofthistypeoccurred.Thisvalueisbased
onthedateandtimestoredbytheiLOfirmware.
TheiLOdateandtimecanbesynchronizedthroughthefollowing:
◦SystemROM(duringPOSTonly)
◦InsightManagementAgents(intheOS)
◦NTPserver(configurediniLO)
◦OnboardAdministrator(serverbladesonly)
IfiLOdidnotrecognizethedateandtimewhenaneventwasupdated,[NOT SET]is
displayed.
•InitialUpdate—Thedateandtimewhenthefirsteventofthistypeoccurred.Thisvalueisbased
onthedateandtimestoredbytheiLOfirmware.
IfiLOdidnotrecognizethedateandtimewhentheeventwasfirstcreated,[NOT SET]is
displayed.
UsingtheIntegratedManagementLog175 
						

							•Count—Thenumberoftimesthiseventhasoccurred(ifsupported).
Ingeneral,seriouseventsgenerateaneventlogentryeachtimetheyoccur.Theyarenot
consolidatedintooneeventlogentry.
Whenlessimportanteventsarerepeated,theyareconsolidatedintooneeventlogentry,and
theCountandLastUpdatevaluesareupdated.Eacheventtypehasaspecifictimeinterval
thatdetermineswhetherrepeatedeventsareconsolidatedoraneweventislogged.
•Description—Thedescriptionidentifiesthecomponentanddetailedcharacteristicsofthe
recordedevent.
IftheiLOfirmwareisrolledback,thedescriptionUNKNOWN EVENT TYPEmightbedisplayed
foreventsrecordedbythenewerfirmware.Youcanresolvethisissuebyupdatingthefirmware
tothelatestsupportedversion,orbyclearingthelog.
Markingalogentryasrepaired
UsethisfeaturetochangethestatusofanIMLlogentryfromCriticalorCautiontoRepaired.You
musthavetheConfigureiLOSettingsprivilegetousethisfeature.
WhenaCriticalorCautioneventisreportedintheIMLlog:
1.Investigateandrepairtheissue.
2.NavigatetotheInformation→IntegratedManagementLogpage.
3.Selectthelogentry.
ToselectanIMLentry,clickthecheckboxnexttotheentryinthefirstcolumnoftheIMLtable.
IfacheckboxisnotdisplayednexttoanIMLentry,thatentrycannotbemarkedasrepaired.
4.ClickMarkasRepaired.
TheiLOwebinterfacerefreshes,andtheselectedlogentrystatuschangestoRepaired.
AddingamaintenancenotetotheIML
Usethemaintenancenotefeaturetocreatealogentrythatlogsinformationaboutmaintenance
activitiessuchascomponentupgrades,systembackups,periodicsystemmaintenance,orsoftware
installations.YoumusthavetheConfigureiLOSettingsprivilegetousethisfeature.
1.NavigatetotheInformation→IntegratedManagementLogpage.
2.ClickAddMaintenanceNote.
TheEnterMaintenanceNotewindowopens.
3.Enterthetextthatyouwanttoaddasalogentry,andthenclickOK.
Youcanenterupto227bytesoftext.Youcannotsubmitamaintenancenotewithoutentering
sometext.
AnInformationallogentrywiththeclassMaintenanceisaddedtotheIML.
SavingtheIML
TosavetheIMLasaCSVfile:
176UsingiLO 
						

							1.ClicktheViewCSVbutton.
TheIMLisdisplayedinaformatthatyoucancopyandpasteintoatexteditor.
2.CopythetextdisplayedintheCSVOutputwindow,andsaveitinatexteditorasa*.csv
file.
3.ClickExittoclosethewindow.
ClearingtheIML
TocleartheIMLofallpreviouslyloggedinformation:
1.ClickClearIML.
Thefollowingmessageappears:
Are you sure you want to clear the Integrated Management Log?
2.ToconfirmthatyouwanttocleartheIML,clickOK.
Thefollowingeventisrecorded:
IML Cleared by .
YoucanalsocleartheIMLfromtheserverHPSystemManagementHomepage.
UsingtheHPActiveHealthSystem
TheHPActiveHealthSystemmonitorsandrecordschangesintheserverhardwareandsystem
configuration.Itassistsindiagnosingproblemsanddeliveringrapidresolutionwhensystemfailures
occur.HPActiveHealthSystemdoesnotcollectinformationaboutyouroperations,finances,
customers,employees,partners,ordatacenter(forexample,IPaddresses,hostnames,usernames,
andpasswords).
BydownloadingandsendingActiveHealthSystemdatatoHP,youagreetohaveHPusethedata
foranalysis,technicalresolution,andqualityimprovements.Thedatathatiscollectedismanaged
accordingtotheHPPrivacyStatement,availableathttp://www.hp.com/go/privacy.
Examplesofdatathatiscollectedfollow:
•Servermodel
•Serialnumber
•Processormodelandspeed
•Storagecapacityandspeed
•Memorycapacityandspeed
•Firmware/BIOS
NOTE:TheHPActiveHealthSystemdoesnotparseorchangeoperatingsystemdatafrom
third-partyerroreventlogactivities(forexample,contentcreatedorpassedthroughtheoperating
system).
WhentheActiveHealthSystemLogisfull,newdataoverwritestheoldestdatainthelog.
YoucandownloadtheActiveHealthSystemLogmanuallyandsendittoHP.Todownloadthe
log,useiLO,IntelligentProvisioning,curl,ortheActiveHealthSystemdownloadCLItool.For
moreinformation,seethefollowing:
•“DownloadingtheActiveHealthSystemLogforadaterange”(page178)
•“ExtractingtheActiveHealthSystemlogbyusingcurl”(page179)
•HPIntelligentProvisioningUserGuideforHPProLiantGen8Servers
•HPIntelligentProvisioningUserGuideforHPProLiantGen9Servers
UsingtheHPActiveHealthSystem177 
						

							•HPProLiantGen8TroubleshootingGuide,VolumeI:Troubleshooting
•HPProLiantGen9TroubleshootingGuide,VolumeI:Troubleshooting
AnyusercandownloadtheActiveHealthSystemLog.TheConfigureiLOSettingsprivilegeis
requiredtomodifytheActiveHealthSystemsettingsortoclearthelog.
DownloadingtheActiveHealthSystemLogforadaterange
UsethefollowingproceduretodownloadtheActiveHealthSystemLogforadaterange.
1.NavigatetotheInformation→ActiveHealthSystemLogpage.
2.Entertherangeofdaystoincludeinthelog.
Thedefaultsettingistoincludeloginformationforthelast7days.ClickResetrangetodefault
valuestoresetthedates.
a.ClicktheFrombox.
Acalendarisdisplayed.
b.Selecttherangestartdateonthecalendar.
c.ClicktheTobox.
Acalendarisdisplayed.
d.Selecttherangeenddateonthecalendar.
3.Optional:Enterthecontactinformationtoincludeinthedownloadedfile.
•HPSupportCaseNumber
•ContactName
•PhoneNumber
178UsingiLO 
						

							•E-mail
•CompanyName
ThecontactinformationyouprovidewillbetreatedinaccordancewiththeHPDataPrivacy
Policy,availableathttp://www.hp.com/go/privacy.Thisinformationisnotwrittentothelog
datastoredontheserver.
4.ClickDownload.
5.Savethefile.
ThedefaultfilenameisHP__.ahs.
6.IfyouhaveanopencasewithHPSupport,youcanemailthelogfileto
[email protected].
Usethefollowingconventionfortheemailsubject:CASE:.
NOTE:Filesthatarelargerthan15MBmustbecompressedanduploadedtoanFTPsite.
Ifneeded,contactHPSupportforFTPsiteinformation.
DownloadingtheentireActiveHealthSystemLog
UsethefollowingproceduretodownloadtheentireActiveHealthSystemLog.
ItmighttakealongtimetodownloadtheentireActiveHealthSystemLog.Ifyoumustuploadthe
ActiveHealthSystemLogforatechnicalissue,HPrecommendsdownloadingthelogforthespecific
rangeofdatesinwhichtheproblemoccurred.Forinstructions,see“DownloadingtheActiveHealth
SystemLogforadaterange”(page178).
1.NavigatetotheInformation→ActiveHealthSystemLogpage.
2.ClickShowAdvancedSettings.
3.Optional:Enterthecontactinformationtoincludeinthedownloadedfile.
•HPSupportCaseNumber
•ContactName
•PhoneNumber
•E-mail
•CompanyName
ThecontactinformationthatyouprovidewillbetreatedinaccordancewiththeHPData
PrivacyPolicy,availableathttp://www.hp.com/go/privacy.Thisinformationisnotwritten
tothelogdatastoredontheserver.
4.ClickDownloadEntireLog.
5.Savethefile.
6.IfyouhaveanopencasewithHPSupport,youcanemailthelogfileto
[email protected].
Usethefollowingconventionfortheemailsubject:CASE:.
NOTE:Filesthatarelargerthan15MBmustbecompressedanduploadedtoanFTPsite.
Ifneeded,contactHPSupportforFTPsiteinformation.
ExtractingtheActiveHealthSystemlogbyusingcurl
iLO41.30andlatersupportsextractingtheActiveHealthSystemlogwiththecurlcommand
linetool.
Youcandownloadcurlfromthefollowingwebsite:http://curl.haxx.se/.
TodownloadtheActiveHealthSystemlogbyusingcurl:
UsingtheHPActiveHealthSystem179 
						

							1.Installcurl.
2.Openacommandwindow.
3.EnterthefollowingcommandtodownloadtheActiveHealthSystemlogforarangeofdates:
curl "https:///ahsdata/ahs.ahs?from=&to=
" -k -v -u : -o .ahs
Where:
•istheiLOIPaddress.
•from=&to=representsthestartandenddateofthe
rangeofdatestoincludeinthelog.Enterdatesintheformatyear-month-day,for
example,2013-07-29forJuly29,2013.
•–kspecifiesthatHTTPSwarningswillbeignored.
•–vspecifiesverboseoutput.
•-u :specifiesyouriLOuseraccountcredentials.
•–o specifiestheoutputfilenameandpath.
NOTE:Todownloadtheentirelog,omitthefromandtoparametersandusethefollowing
command:curl "https:///ahsdata/ahs.ahs" -k -v -u
: -o .ahs
Thefileissavedtothepathyouspecified.
4.Closethecommandwindow.
ClearingtheActiveHealthSystemLog
Ifthelogfileiscorrupted,orifyouwanttoclearandrestartlogging,usethefollowingprocedure
tocleartheActiveHealthSystemLog.YoumusthavetheConfigureiLOSettingsprivilegetoperform
thisprocedure.
1.NavigatetotheInformation→ActiveHealthSystemLogpage.
2.ClickShowAdvancedSettings.
3.ScrolltotheClearLogsection,andthenclicktheClearbutton.
Thefollowingmessageappears:
Are you sure that you want to clear the entire Active Health System
log? This action cannot be undone.
4.ClickOK.
iLOnotifiesyouthatthelogisbeingcleared.
5.ResetiLO.
Forinstructions,see“UsingiLOdiagnostics”(page180).
ResettingiLOafterclearingtheActiveHealthSystemLogisrequiredbecausesomeActive
HealthSystemdataisrecordedtothelogonlyduringiLOstartup.Performingthisstepensures
thatacompletesetofdataisavailableinthelog.
6.Reboottheserver.
RebootingtheserverafterclearingtheActiveHealthSystemLogisrequiredbecausesome
information,suchastheoperatingsystemnameandversion,isloggedatserverstartup.
Performingthisstepensuresthatacompletesetofdataisavailableinthelog.
UsingiLOdiagnostics
TheDiagnosticspagedisplaysiLOself-testresultsandallowsyoutoresetiLO,generateanNMI
tothesystem,orconfigureredundantROM.
180UsingiLO