HP Ilo 3 User Guide

							Figure122ChooseDiskImageFiledialogbox
8.TypeorselectthepathoftheUSBkey/floppy(/dev/disk)insertedintheclient.
YoucanalsomounttheUSBkey/floppybylabel,asshowninFigure123(page221).
Figure123MountingtheUSBkeybylabel
9.ClickOK.
CapsLockoutofsyncbetweeniLOandJavaIRC
WhenyoulogintotheJavaIRC,theCapsLocksettingmightbeoutofsyncbetweeniLOandthe
JavaIRC.
Solution:SelectKeyboard→CapsLockintheJavaIRCtosynchronizetheCapsLocksettings.
TroubleshootingRemoteConsoleissues221 
						

							NumLockoutofsyncbetweeniLOandSharedRemoteConsole
WhenyoulogintoaSharedRemoteConsolesession,theNumLocksettingmightbeoutofsync
betweeniLOandsomeoftheRemoteConsolesessions.
Solution:SelectKeyboard→NumLockintheRemoteConsoletosynchronizetheNumLocksettings.
KeystrokesrepeatunintentionallyduringRemoteConsolesession
Whenyouareusingthe.NETIRCorJavaIRC,akeystrokemightrepeatunintentionallyduringa
RemoteConsolesession.
Solution1:Identifyandfixproblemsthatmightcausenetworklatency.
Solution2:Adjustthefollowingsettingsontheremotemachine:
•Increasethetypematicdelay—Thissettingcontrolsthedelaybeforeacharacterrepeatswhen
youpressandholdakeyonthekeyboard.
•Decreasethetypematicrate—Thissettingcontrolstherateatwhichacharacterrepeatswhen
youpressandholdakeyonthekeyboard.
NOTE:TheexactnameofthesettingvariesdependingontheOSyouareusing.Formore
informationaboutchangingthetypematicdelayandrate,seeyourOSdocumentation.
Sessionleaderdoesnotreceiveconnectionrequestwhen.NETIRCisinreplaymode
Solution:WhenaRemoteConsolesessionleaderplayscapturedvideodata,the.NETIRCdoes
notdisplaytheDenyorAcceptmessagewhenanotheruserattemptstoaccessorsharethe.NET
IRC.Instead,thenew.NETIRCsessionwaitsandeventuallytimesout.Ifyourequireaccesstothe
.NETIRC,andyourrequesttimesout,contacttheotheruserorusetheRemoteConsoleAcquire
featuretotakecontroloftheIRC.Forinstructions,see“AcquiringtheRemoteConsole”(page118).
KeyboardLEDdoesnotworkcorrectly
TheclientkeyboardLEDdoesnotreflectthetruestateofthekeyboardlockkeys.TheCapsLock,
NumLock,andScrollLockkeysarefullyfunctionalwhenyouareusingthekeyboardoptionsin
theRemoteConsole.
Inactive.NETIRC
TheiLO.NETIRCmightbecomeinactiveordisconnectduringperiodsofhighactivity..NETIRC
activityslowsbeforebecominginactive.Symptomsofanaffected.NETIRCincludethefollowing:
•The.NETIRCdisplayisnotupdated.
•Keyboardandmouseactivityisnotrecorded.
•SharedRemoteConsolerequestsdonotregister.
Althoughyoucanreplayacapturedfileonaninactive.NETIRC,theactivestateofthe.NETIRC
isnotrestored.
ThisissuemightoccurwhenmultipleusersareloggedintoiLO,aVirtualMediasessionisconnected
andisperformingacontinuouscopyoperation,ora.NETIRCsessionisopen.TheVirtualMedia
continuouscopyoperationtakespriorityand,consequently,the.NETIRClosessynchronization.
Eventually,theVirtualMediaconnectionresetsmultipletimesandcausestheUSBmediadrivefor
theOStolosesynchronizationwiththeVirtualMediaclient.
Solution:Reconnecttothe.NETIRCandtheVirtualMedia.Ifpossible,reducethenumberof
simultaneousiLOusersessions.Ifnecessary,resetiLO.(Theserverdoesnotneedtobereset.)
222Troubleshooting 
						

							.NETIRCfailedtoconnecttoserver
iLOmightdisplaythemessageFailed to connect to serverwhenitattemptstoestablish
a.NETIRCsession.
TheiLO.NETIRCclientwaitsaspecifiedamountoftimeforaconnectiontobeestablishedwith
iLO.Iftheclientserverdoesnotreceivearesponseinthisamountoftime,itdisplaysanerror
message.
Possiblecausesforthismessageincludethefollowing:
•Thenetworkresponseisdelayed.
•ASharedRemoteConsolesessionisrequested,butthesessionleaderdelayssendingan
acceptanceordenialmessage.
Solution1:Retrythe.NETIRCconnection.
Solution2:Ifpossible,correctthenetworkdelayandretrythe.NETIRCconnection.
Solution3:IftherequestwasforaSharedRemoteConsolesession,attempttocontactthesession
leaderandretrytherequest.IftheRemoteConsoleAcquirefeatureisenabled,usetheAcquire
featureratherthanrequestingaSharedRemoteConsolesession.Formoreinformation,see
“AcquiringtheRemoteConsole”(page118).
Filenotpresentaftercopyfrom.NETIRCvirtualdrivestoUSBkey
IfausercopiesfilesfromthetargetservertoamountediLOvirtualdrive(USBkeyconnectedto
aclientcomputerrunninganyWindowsOS),thefilesarenotvisibleinWindowsExploreronthe
clientcomputer.
FilechangesontheiLOVirtualMediaUSBkeyareneverseeninWindowsExplorerbytheuser
ontheclientcomputer.
WindowsExplorerkeepsacachedcopyofthefilesontheUSBkey,andtheiLORemoteConsole
doesnotnotifytheWindowsShellwhentheUSBkeyisupdatedwithfilechanges.Thefilechanges
existontheUSBdrive,butiftheuserrefreshestheExplorerwindow,thecachedcopyofthefiles
isflushedbacktotheUSBkey,andtheuserwillneverseethefilechangesinWindowsExplorer.
AnykindoffilechangemadeonamountediLOVirtualMediaUSBkeydrivefromaWindows
clientviatheRemoteConsolecantriggerthisissue.
Solution:
1.InstallaUSBkeydriveonaWindowsclientcomputer.
2.Using.NETIRC,connecttheclientUSBkeytotheiLOVirtualMediadriveonthetargetserver.
3.MakefilechangestotheconnectediLOVirtualMediadrive(copy,delete,andsoon).
4.SafelyunmounttheiLOUSBVirtualMediadriveonthetargetserversothatalldataisupdated
totheVirtualMediadrive.
5.DisconnecttheclientUSBkeybyusingthe.NETIRC.
CAUTION:DonotuseWindowsExplorertorefreshthecontentsoftheUSBkey.
6.SafelyremovetheUSBkeyfromtheclientcomputerbyclickingtheSafelyRemoveHardware
iconintheWindowsnotificationarea.Followtheonscreeninstructions.
7.RemovetheUSBkeyfromtheclientcomputer.
WhenyouconnecttheUSBkeytoanycomputer,thefilechangeswillbevisibleinWindows
Explorer.
.NETIRCtakesalongtimetoverifyapplicationrequirements
Whenyoustartthe.NETIRCfromtheiLOwebinterface,thefollowingdialogbox(Figure124)
appearsandremainsonthescreenforalongtime.
TroubleshootingRemoteConsoleissues223  
						

							Figure124.NETIRClaunchdialogbox
Solution:
1.OpenInternetExplorer.
2.SelectTools→InternetOptions.
TheInternetOptionswindowopens.
3.ClicktheConnectionstab,andthenclicktheLANsettingsbutton.
TheLocalAreaNetwork(LAN)Settingswindowopens.
4.CleartheAutomaticallydetectsettingscheckbox.
5.Optional:Ifneeded,configuretheproxyserversettings.
6.Closeallofthebrowserwindows.
7.Restartthebrowserandstartthe.NETIRC.
.NETIRCfailstostart
Whenyoustartthe.NETIRC,thefollowingerrormessageappears(Figure125).
Figure125.NETIRCcannotbestarted
Solution:CleartheClickOnceapplicationcachebyenteringthefollowingcommandfromthe
WindowsCommandPrompt:rundll32 %windir%\system32\dfshim.dll
CleanOnlineAppCache.
.NETIRCcannotbeshared
Whenyoutrytojoinashared.NETIRCsession,thefollowingerrormessageappears(Figure126.
Figure126.NETIRCfirewallerror
Solution1:Makesurethereisacommunicationroutebetweenthesessionleader.NETIRCclient
andeachshared.NETIRCclient.
Solution2:MakesurethefirewallsettingsonallclientsallowaninboundconnectiontotheRemote
Consoleport(thedefaultportis17990).
224Troubleshooting 
						

							TroubleshootingSSHissues
ThefollowingsectionsdiscusstroubleshootingSSHissues.
InitialPuTTYinputslow
DuringtheinitialconnectiontoiLOthroughaPuTTYclient,inputisacceptedslowlyforapproximately
5seconds.
Solution:Changetheconfigurationoptionsintheclient.CleartheDisableNagle'salgorithmcheck
boxinthelow-levelTCPconnectionoptions.
PuTTYclientunresponsive
WhenyouareusingaPuTTYclientwiththeSharedNetworkPort,thePuTTYsessionmightbecome
unresponsivewhenalargeamountofdataistransferredorwhenyouareusingaVirtualSerial
PortandRemoteConsole.
Solution:ClosethePuTTYclientandrestartthesession.
SSHtextsupportfromtext-basedRemoteConsolesession
SSHaccessfromthetext-basedRemoteConsolesupportsthestandard80x25configurationof
thetextscreen.Thismodeiscompatibleforthetext-basedRemoteConsoleformosttext-mode
interfaces.Extendedtextconfigurationbeyondthe80x25configurationisnotdisplayedcorrectly
whenusingSSH.HPrecommendsconfiguringthetextapplicationin80x25modeorusingthe
graphicalRemoteConsole.
Troubleshootingvideoandmonitorissues
Theclientscreenresolutionmustbegreaterthanthescreenresolutionoftheremoteserver.
Userinterfacedoesnotdisplaycorrectly
OnProLiantserversusingRedHatEL4.0andsomeotherLinuxsystemsandiLO3,thetextonthe
buttonsoftheuserinterfacemightbecutoffalongthebottomofthebutton.Thiserroroccurs
becauseMozillaFirefoxdoesnotdisplaythetextsizethatiLO3specifiesforthebuttons.
Solution:Todisplaythetextcorrectly,selectView>TextSize>Decreaseuntilthetextappears
correctly.
iLOVirtualFloppymediaappletunresponsive
TheiLOVirtualFloppymediaappletcanbecomeunresponsiveifthephysicalfloppydiskette
containsmediaerrors.
Solution:TopreventtheiLOVirtualFloppymediaappletfrombecomingunresponsive,runautility
suchasCHKDSK.EXEtocheckthephysicalfloppydiskmediaforerrors.Ifthephysicalmedia
containserrors,loadthefloppydiskimageontoanewphysicalfloppydiskette.
Troubleshootingtext-basedRemoteConsoleissues
Thefollowingsectionsdiscussitemstobeawareofwhenattemptingtoresolvetext-basedRemote
Consoleissues.
UnabletoviewLinuxinstallerintext-basedRemoteConsole
WheninstallingLinuxfromthetextconsole,theinitialinstallationscreenmightnotappearbecause
thescreenisingraphicsmode.
Solution:Tocorrectthisandproceedwiththeinstallation,dooneofthefollowing:
•FormostversionsofLinux,enterlinux text nofb.
Thecharactersthatyouenterdonotappear.
TroubleshootingSSHissues225 
						

							Afteryouenterthecommand,thescreenchangesfromgraphicsmodetotextmode,displaying
thescreen.
•ForSLES,pressF2andthedownarrowfromthetextconsole.Thetextmodeisselectedand
thescreenappears.
UnabletopassdatathroughSSHterminal
IfyouuseanSSHterminaltoaccessthetextconsole,SSHmightinterceptkeystrokedataandnot
passtheactiontothetext-basedRemoteConsole.Whenthisoccurs,itappearsasifthekeystroke
didnotperformitsfunction.
Solution:DisableanySSHterminalshortcuts.
VSP-drivenselectionduringtheserialtimeoutwindowsendsoutputtoBIOSredirect
insteadofVSP
The/etc/grub.conffileincludesanoptionforaserialtimeoutwindow(terminal
--timeout=10 serial console).Thissettingprovidesawindowoftimetoselectakeystroke
ontheVSPorontheVGAconsole,andthenthemenuisoutputtothecorrespondingdevice.The
BIOSserialredirectinterceptsVSPkeystrokesduringthistimeoutwindow.
Solution:Toworkaroundthisissue,donotpressakeyforaVSP-drivenselectionduringthe
10-secondtimeoutorturnoffBIOSredirectiontotheVSP.
ScrollingandtextappearirregularduringBIOSredirection
DuringBIOSredirection,thescrollingmightnotworkproperly.Whenyouentercommandsin
RBSU,thetextmightoverwriteitselfonthebottomlineoftheterminalwindow.
Solution:TheBIOSexpectsandcontrolsafixed80x24characterwindow.Whenredirectedto
theserialport,theBIOSstillexpectsandcontrolsafixed80x24characterwindow.IftheVSP
clientbeingused(SSH,HyperTerminal,orotherterminalemulator)canresizethewindowtoa
sizeotherthan80x24,scrollingbecomesconfusedandthescreenoutputappearsgarbled.To
avoidthisissue,configuretheterminalemulatorforawindowsizeofexactly80x24.
Troubleshootingmiscellaneousissues
Thefollowingsectionsdiscusstroubleshootingmiscellaneoushardwareorsoftwareissues.
CookiesharingbetweenbrowserinstancesandiLO
iLOusesbrowsersessioncookiestodistinguishbetweenindividuallogins—eachbrowserwindow
appearsasaseparateuserlogin—whilesharingthesameactivesessionwithiLO.Multiplelogins
canconfusethebrowser.ThismayappeartobeaniLOissue,butitistypicalbrowserbehavior.
Severalprocessescancauseabrowsertoopenadditionalwindows.Browserwindowsopened
fromanopenbrowserrepresentdifferentaspectsofthesameprograminmemory.Consequently,
eachbrowserwindowsharespropertieswiththeparent,includingcookies.
Sharedinstances
WheniLOopensanotherbrowserwindow(forexample,theRemoteConsoleorahelpfile),this
windowsharesthesameconnectiontoiLOandthesessioncookie.
TheiLOwebservermakesURLdecisionsbasedoneachrequestreceived.Forexample,ifarequest
doesnothaveaccessrights,itisredirectedtotheloginpage,regardlessoftheoriginalrequest.
Webserver-basedredirection,selectingFile→New→Window,orpressingCtrl+Nopensaduplicate
instanceoftheoriginalbrowser.
226Troubleshooting 
						

							Cookieorder
Duringlogin,theloginpagebuildsabrowsersessioncookiethatlinksthewindowtotheappropriate
sessionintheiLOfirmware.Thefirmwaretracksbrowserloginsasseparatesessionslistedinthe
ActiveSessionssectionoftheiLOOverviewpage.
Forexample,whenUser1logsin,thewebserverbuildstheinitialframesview,withUser1listed
inthetoppane,menuitemsintheleftpane,andpagedatainthelowerrightpane.WhenUser1
clicksfromlinktolink,onlythemenuitemsandpagedataareupdated.
WhileUser1isloggedin,ifUser2,opensabrowserwindowonthesameclientandlogsin,the
secondloginoverwritesthecookiegeneratedintheoriginalUser1session.AssumingthatUser2
isadifferentuseraccount,adifferentcurrentframeisbuilt,andanewsessionisgranted.The
secondsessionappearsintheActiveSessionssectionoftheiLOOverviewpageasUser2.
Thesecondloginhaseffectivelyorphanedthefirstsessionbyoverridingthecookiegenerated
duringtheUser1login.ThisbehavioristhesameasclosingtheUser1browserwithoutclicking
theSignOutbutton.TheUser1orphanedsessionisreclaimedwhenthesessiontimeoutexpires.
Becausethecurrentuserframeisnotrefreshedunlessthebrowserisforcedtorefreshtheentire
page,User1cancontinuenavigatingbyusingthebrowserwindow.However,thebrowserisnow
operatingbyusingtheUser2sessioncookiesettings,eventhoughitmaynotbereadilyapparent.
IfUser1continuestonavigateinthismode(User1andUser2sharingthesameprocessbecause
User2loggedinandresetthesessioncookie),thefollowingcanoccur:
•User1sessionbehavesconsistentlywiththeprivilegesassignedtoUser2.
•User1activitykeepsUser2sessionalive,butUser1sessioncantimeoutunexpectedly.
•Loggingoutofeitherwindowcausesbothsessionstoend.Thenextactivityintheotherwindow
canredirecttheusertotheloginpageasifasessiontimeoutorprematuretimeoutoccurred.
•ClickingSignOutfromthesecondsession(User2)resultsinthefollowingwarningmessage:
Logging out: unknown page to display before redirecting the user to
the login page.
•IfUser2logsoutandthenlogsbackinasUser3,User1assumestheUser3session.
•IfUser1isatlogin,andUser2isloggedin,User1canaltertheURLtoredirecttotheindex
page.ItappearsasifUser1hasaccessediLOwithoutloggingin.
Thesebehaviorscontinueaslongastheduplicatewindowsareopen.Allactivitiesareattributed
tothesameuser,usingthelastsessioncookieset.
Displayingthecurrentsessioncookie
Afterloggingin,youcanforcethebrowsertodisplaythecurrentsessioncookiebyenteringthe
followingintheURLnavigationbar:
javascript:alert(document.cookie)
ThefirstfieldvisibleisthesessionID.IfthesessionIDisthesameamongthedifferentbrowser
windows,thesewindowsaresharingthesameiLOsession.
YoucanforcethebrowsertorefreshandrevealyourtrueidentitybypressingF5,selecting
View→Refresh,orclickingtheRefreshbutton.
Preventingcookie-relatedissues
Topreventtheseissues:
•Startanewbrowserforeachloginbydouble-clickingthebrowsericonorshortcut.
•ClicktheSignOutbuttontoclosetheiLOsessionbeforeyouclosethebrowserwindow.
Troubleshootingmiscellaneousissues227 
						

							UnabletogetSNMPinformationfromHPSIM
Solution:TheagentsrunningonthemanagedserversupplySNMPinformationtoHPSIM.For
agentstopassinformationthroughiLO,iLOdevicedriversmustbeinstalled.Forinstallation
instructions,see“InstallingtheiLOdrivers”(page22).
IfyouhaveinstalledthedriversandagentsforiLO,verifythatiLOandthemanagementPCare
onthesamesubnet.YoucanverifythisquicklybypingingiLOfromthemanagementPC.Consult
yournetworkadministratorforproperroutestoaccesstheiLOnetworkinterface.
UnabletoupgradeiLOfirmware
•Solution1:IfyouattempttoupgradetheiLOfirmwarebyusingtheiLOwebinterface,andit
doesnotrespond,doesnotacceptthefirmwareupgrade,orisstoppedbeforeasuccessful
upgrade,tryreinstallingthefirmwareafteryoucompletethefollowingdiagnosticsteps:
1.AttempttoconnecttoiLOthroughthewebbrowser.Ifyoucannotconnect,thereisa
communicationissue.
2.AttempttopingiLO.Ifyouaresuccessful,thenetworkisworking.
•Solution2:IfanincorrectfileisusedtoflashtheiLOfirmwarebyusingtheiLOwebinterface,
thefollowingerrormessageisdisplayed:
The last firmware update attempt was not successful. Ready for the
next update.
Ifthiserroroccurs,clicktheClearErrorbuttontoresettheflashprocess,andthentrythe
firmwareupdateagainwiththecorrectfirmwarefile.Ifyoudonotcleartheerror,thesame
errormightoccurevenwhenyouusethecorrectfirmwarefile.
•Solution3:IfaconnectionerroroccursafteryouinstallafirmwareupdatebyusingtheiLO
webinterface,clearthebrowsercache.
•Solution4:Tryadifferentfirmwareupdatemethod.Forinformationaboutthemethodsthat
youcanusetoupdatethefirmware,see“Updatingfirmware”(page25).
RecoveringfromafailediLOfirmwareupdate
UsethisproceduretorecoverfromafailediLOfirmwareupdateonLinuxorVMwaresystems.
1.CopytheiLOofflineflashcomponenttoaUSBdrivekey.
2.SettheiLOSecurityOverrideSwitchtodisabled.
3.BoottheUSBdrivekeycontainingtheiLOofflineflashcomponent.
TodownloadtheHPUSBKeyUtilityandforinformationonhowtocreateabootUSBkey,
seetheSPPdocumentationathttp://www.hp.com/go/spp/documentation.
4.Afterthefirstscreendisplays,switchtotextconsolebypressingCtrl+Alt+F1.
5.Switchtothedirectorywheretheflashcomponentisstoredbyenteringthefollowingcommand
atthe#prompt:
cd /mnt/usb/components/
6.RemovetheloadediLOdriverbyenteringthefollowingcommands:
•ESX4.x:/etc/init.d/hp-snmp-agents stop /etc/init.d/hp-ilo stop
•ESX3.x:/etc/init.d/hpasm stop
7.Runthecomponentusingthe--directoption,forexample:
/CP00xxxx.scexe –-direct
8.EnterYattheContinue (Y/N)?prompt.
9.Afterprogrammingissuccessfullycompleted,setthesecurityoverrideswitchtoenabledand
reboottheserver.
228Troubleshooting 
						

							iLOnetworkFailedFlashRecovery
Mostfirmwareupgradesfinishsuccessfully.Intheunlikelyeventofserverpowerlossduringan
iLOfirmwareupgrade,iLOmightberecoverablewhenpowerisrestored.
Whenthecomputerisbooting,thekernelperformsimagevalidationonthemainimage.Ifthe
imageiscorruptedorincomplete,thekernelentersFailedFlashRecovery.FailedFlashRecovery
activatesanFTPserverwithiniLO.TheFTPserverenablesyoutosendanimagetoiLOfor
programming.TheFTPserverdoesnotprovideanyotherservices.
AnetworkclientcanconnecttotheFTPserver.Theusernamefortheconnectionistest,andthe
passwordisflash.TosendafirmwareimagetoiLO,usetheFTPclientPUTcommand.After
receivingtheimage,iLOvalidatestheimage.Iftheimageisacomplete,signed,andvalidfirmware
image,thekernelbeginsprogrammingtheFLASHpartition.
AftertheimageiscompletelyprogrammedintotheFLASHpartition,resetiLObyissuingtheRESET
commandtotheiLOFTPserver.
Example:
F:\ilo3>ftp 192.168.1.2
Connected to 192.168.1.2.
220 FTP Recovery server ready.
User (192.168.1.2:(none)): ftp
331 Password required.
Password:
231 Logged in.
ftp> put iLO3.bin
200 Ok.
150 ready for file
226-Checking file
226-File acceptable
226-Flashing   3% complete
226-Flashing   4% complete
226-Flashing   6% complete
.
.
.
226-Flashing  97% complete
226-Flashing  99% complete
226-Flashing 100% complete
226-Flashing completed
226 Closing file
ftp: 8388608 bytes sent in 1.38Seconds 6100.81 Kbytes/sec.
ftp> quote reset
221 Goodbye (reset).
Connection closed by remote host.
ftp> quit
TestingSSL
Thefollowingtestchecksforthecorrectsecurityprompt.Anonworkingserverwillproceedtoa
Page cannot be displayedmessage.Ifthistestfails,yourdomaincontrollerisnotaccepting
SSLconnectionsandprobablyhasnotbeenissuedacertificate.
1.Openabrowserandnavigatetohttps://:636.
Youcanuseinsteadof,whichaccessestheDNSand
determineswhichdomaincontrollerishandlingrequestsforthedomain.Testmultipledomain
controllerstoverifythatallofthemhavebeenissuedacertificate.
Troubleshootingmiscellaneousissues229 
						

							2.IfSSLisoperatingcorrectlyonthedomaincontroller(acertificatehasbeenissued),youare
promptedwithasecuritymessagethataskswhetheryouwanttoproceedwithaccessingthe
siteorviewtheservercertificate.ClickingYesdoesnotdisplayawebpage,whichisnormal.
Thisprocessisautomatic,butmightrequirerebooting.Toavoidrebooting:
a.OpentheMMC.
b.Addthecertificatessnap-in.
c.Whenprompted,selectComputerAccountforthetypeofcertificatesyouwanttoview.
d.ClickOKtoreturntothecertificatessnap-in.
e.SelectthePersonal→Certificatesfolder.
f.Right-clickthefolderandselectRequestNewCertificate.
g.VerifythattheTypeisdomaincontroller,andclickNextuntilacertificateisissued.
YoucanalsousetheMicrosoftLdp.exetooltoverifySSLconnections.Formoreinformationabout
theLDPtool,seeyourMicrosoftdocumentation.
AnoldcertificatecancauseissueswithSSLonthedomaincontrollerwhenitpointstoapreviously
trustedCAwiththesamename.Thissituationisrarebutmighthappenifacertificateserviceis
addedandremoved,andthenaddedagainonthedomaincontroller.Toremoveoldcertificates
andissueanewone,followtheinstructionsinstep2.
ResettingiLO
Insomecases,itmightbenecessarytoresetiLO;forexample,ifiLOisnotrespondingtothe
browser.
iLOmightresetitselfincertaininstances.Forexample,aninternaliLOwatchdogtimerresetsifthe
firmwaredetectsaniLOissue.Ifafirmwareupgradeiscompletedoranetworksettingischanged,
iLOalsoresets.
ToresetiLO,useoneofthefollowingmethods:
•ClickResetontheInformation→DiagnosticspageintheiLOwebinterface.Formore
information,see“UsingiLOdiagnostics”(page112).
•UsetheCLIorHPONCFG.Forinstructions,seetheHPiLO3ScriptingandCommandLine
Guide.
•TheHPInsightManagementAgents5.40andlaterhavetheabilitytoresetiLO.Selectthe
ResetiLOoptionontheHPManagementAgentpageintheiLOsection.
•ClickApplyontheNetwork→iLODedicatedNetworkPortorSharedNetworkPort→General
pagetomanuallyforcetheiLOmanagementprocessortoreset.IftheApplybuttonisnot
available,changeasetting,changeitback,andthenclickApplytoresetiLOwithoutchanging
theconfiguration.
Ifnoneofthesemethodsisavailableorworkingasexpected,youmustpowerdowntheserver
anddisconnectthepowersuppliescompletely.
ResettingiLOtothefactorydefaultsettingsbyusingiLORBSU
ToresetiLOtothefactorydefaultsettings:
CAUTION:Thisoperationclearsalluserandlicensedata.
1.Optional:Ifyouaccesstheserverremotely,startaniLOremoteconsolesession.
Youcanusethe.NETIRCorJavaIRC.
2.Restartorpowerontheserver.
3.PressF8intheHPProLiantPOSTscreen.
iLORBSUstarts.
230Troubleshooting