sensewindow2003

TivoliProvisioningManagerforOSDeploymentVersion7.
1.
1.
11TroubleshootingandsupportguideTivoliProvisioningManagerforOSDeploymentVersion7.
1.
1.
11TroubleshootingandsupportguideiiTivoliProvisioningManagerforOSDeployment:TroubleshootingandsupportguideContentsTroubleshootingandsupport1Troubleshootingaproblem1Searchingknowledgebases3Gettingafix4ContactingIBMSupport4Errormessages5Systemprofileerrormessages5OSdeploymenterrormessages5ExportingthelogfilesinCommonBaseEvent(CBE)format7Problemsandlimitations8ISACompatibility.
8WindowsServiceTroubleshootingforOSdeploymentserver8Limitations9Problemswiththekernel-freeinBIOSmode.
.
11Problemswiththekernel-freeinUEFImode.
.
11ProblemswiththeOSdeploymentserverandthewebinterfaceextension12ProblemsprovisioningWindowsoperatingsystems.
15ProblemsprovisioningLinuxandUNIXoperatingsystems20ProblemsprovisioningVMWareESXoperatingsystems.
30Problemsafteradeployment30Problemswhileredeployingaprofileonthesametarget31Problemswithamultiserverarchitecture.
.
.
35Problemswithbooting,network,andfiletransfers38Problemswiththedatabaseandthedatabasegateway43KnownlimitationsapplicabletothecurrentreleaseoftheToolkit45Miscellaneousproblems46Conventions54Notices55CopyrightIBMCorp.
2012iiiivTivoliProvisioningManagerforOSDeployment:TroubleshootingandsupportguideTroubleshootingandsupportTohelpyouunderstand,isolate,andresolveproblemswithyourIBMsoftware,thetroubleshootingandsupportinformationcontainsinstructionsforusingtheproblem-determinationresourcesthatareprovidedwithyourIBMproducts.
Toresolveaproblemonyourown,youcanfindouthowtoidentifythesourceofaproblem,howtogatherdiagnosticinformation,wheretogetfixes,andwhichknowledgebasestosearch.
IfyouneedtocontactIBMSupport,youcanfindoutwhatdiagnosticinformationtheservicetechniciansneedtohelpyouaddressaproblem.
TroubleshootingaproblemTroubleshootingisasystematicapproachtosolvingaproblem.
Thegoaloftroubleshootingistodeterminewhysomethingdoesnotworkasexpectedandexplainhowtoresolvetheproblem.
Thefirststepinthetroubleshootingprocessistodescribetheproblemcompletely.
ProblemdescriptionshelpyouandtheIBMSupportpersonknowwheretostarttofindthecauseoftheproblem.
Thisstepincludesaskingyourselfbasicquestions:vWhatarethesymptomsoftheproblemvWheredoestheproblemoccurvWhendoestheproblemoccurvUnderwhichconditionsdoestheproblemoccurvCantheproblembereproducedTheanswerstothesequestionstypicallyleadtoagooddescriptionoftheproblem,andthatisthebestwaytostartdownthepathofproblemresolution.
WhatarethesymptomsoftheproblemWhenstartingtodescribeaproblem,themostobviousquestionis"Whatistheproblem"Thismightseemlikeastraightforwardquestion;however,youcanbreakitdownintoseveralmore-focusedquestionsthatcreateamoredescriptivepictureoftheproblem.
Thesequestionscaninclude:vWho,orwhat,isreportingtheproblemvWhataretheerrorcodesandmessagesvHowdoesthesystemfailForexample,isitaloop,hang,performancedegradation,orincorrectresultvWhatisthebusinessimpactoftheproblemWheredoestheproblemoccurDeterminingwheretheproblemoriginatesisnotalwayseasy,butitisoneofthemostimportantstepsinresolvingaproblem.
Manylayersoftechnologycanexistbetweenthereportingandfailingcomponents.
Networks,disks,anddriversareonlyafewofthecomponentstoconsiderwhenyouareinvestigatingproblems.
Thefollowingquestionshelpyoutofocusonwheretheproblemoccurstoisolatetheproblemlayer:CopyrightIBMCorp.
20121vIstheproblemspecifictooneplatformoroperatingsystem,orisitcommonacrossmultipleplatformsoroperatingsystemsvIsthecurrentenvironmentandconfigurationsupportedRememberthatifonelayerreportstheproblem,theproblemdoesnotnecessarilyoriginateinthatlayer.
Partofidentifyingwhereaproblemoriginatesisunderstandingtheenvironmentinwhichitexists.
Takesometimetocompletelydescribetheproblemenvironment,includingtheoperatingsystemandversion,allcorrespondingsoftwareandversions,andhardwareinformation.
Confirmthatyouarerunningwithinanenvironmentthatisasupportedconfiguration;manyproblemscanbetracedbacktoincompatiblelevelsofsoftwarethatarenotintendedtoruntogetherorhavenotbeenfullytestedtogether.
WhendoestheproblemoccurDevelopadetailedtimelineofeventsleadinguptoafailure,especiallyforthosecasesthatareone-timeoccurrences.
Youcanmosteasilydothisbyworkingbackward:Startatthetimeanerrorwasreported(aspreciselyaspossible,evendowntothemillisecond),andworkbackwardusingtheavailablelogsandinformation.
Typically,youneedtolookonlyasfarasthefirstsuspiciouseventthatyoufindinadiagnosticlog;however,thisisnotalwayseasytodoandtakespractice.
Knowingwhentostoplookingisespeciallydifficultwhenmultiplelayersoftechnologyareinvolved,andwheneachhasitsowndiagnosticinformation.
Todevelopadetailedtimelineofevents,answerthesequestions:vDoestheproblemhappenonlyatacertaintimeofdayornightvHowoftendoestheproblemhappenvWhatsequenceofeventsleadsuptothetimethattheproblemisreportedvDoestheproblemhappenafteranenvironmentchange,suchasupgradingorinstallingsoftwareorhardwareRespondingtoquestionslikethishelpstoprovideyouwithaframeofreferenceinwhichtoinvestigatetheproblem.
UnderwhichconditionsdoestheproblemoccurKnowingwhichsystemsandapplicationsarerunningatthetimethataproblemoccursisanimportantpartoftroubleshooting.
Thesequestionsaboutyourenvironmentcanhelpyoutoidentifytherootcauseoftheproblem:vDoestheproblemalwaysoccurwhenthesametaskisbeingperformedvDoesacertainsequenceofeventsneedtooccurfortheproblemtosurfacevDoanyotherapplicationsfailatthesametimeAnsweringthesetypesofquestionscanhelpyouexplaintheenvironmentinwhichtheproblemoccursandcorrelateanydependencies.
Rememberthatjustbecausemultipleproblemsmighthaveoccurredaroundthesametime,theproblemsarenotnecessarilyrelated.
CantheproblembereproducedFromatroubleshootingstandpoint,theidealproblemisonethatcanbereproduced.
Typically,problemsthatcanbereproducedhavealargersetoftoolsorproceduresatyourdisposaltohelpyouinvestigate.
Consequently,problemsthatyoucanreproduceareofteneasiertodebugandsolve.
However,problems2TivoliProvisioningManagerforOSDeployment:Troubleshootingandsupportguidethatyoucanreproducecanhaveadisadvantage:Iftheproblemisofsignificantbusinessimpact,youdonotwantittorecur.
Ifpossible,re-createtheprobleminatestordevelopmentenvironment,whichtypicallyoffersyoumoreflexibilityandcontrolduringyourinvestigation.
vCantheproblemberecreatedonatestsystemvAremultipleusersorapplicationsencounteringthesametypeofproblemvCantheproblemberecreatedbyrunningasinglecommand,asetofcommands,oraparticularapplication,orastand-aloneapplicationSearchingknowledgebasesYoucanoftenfindsolutionstoproblemsbysearchingIBMknowledgebases.
Learnhowtooptimizeyourresultsbyusingavailableresources,supporttools,andsearchmethodsandhowtoreceiveautomaticupdates.
AvailabletechnicalresourcesInadditiontothisinformationcenter,thefollowingtechnicalresourcesareavailabletohelpyouanswerquestionsandresolveproblems:vTivoliProvisioningManagerforOSDeploymentSupportWebsitevTivoliRedbooksDomainvTivolisupportcommunities(forumsandnewsgroups)SearchingwithsupporttoolsThefollowingtoolsareavailabletohelpyousearchIBMknowledgebases:vIBMSupportAssistant(ISA)isafreesoftwareserviceabilityworkbenchthathelpsyouresolvequestionsandproblemswithIBMsoftwareproducts.
InstructionsfordownloadingandinstallingtheISAcanbefoundontheISAWebsite:www.
ibm.
com/software/support/isa/vIBMSoftwareSupportToolbarisabrowserplug-inthatprovidesyouwithamechanismtoeasilysearchIBMsupportsites.
Youcandownloadthetoolbarat:www.
ibm.
com/software/support/toolbar/.
SearchtipsThefollowingresourcesdescribehowtooptimizeyoursearchresults:vSearchingtheIBMSupportWebsitevUsingtheGooglesearchenginevSearchtheinformationcenterformoreinformationabouterrormessagesthatyouencounterwhileusingtheproduct.
ReceivingautomaticupdatesYoucanreceiveautomaticupdatesinthefollowingways:vMysupport.
Toreceiveweeklye-mailnotificationsregardingfixesandothersupportnews,followthesesteps:1.
GototheIBMSoftwareSupportWebsiteatwww.
ibm.
com/software/support/.
2.
ClickMysupportintheupper-rightcornerofthepageunderPersonalizedsupport.
Troubleshootingandsupport33.
IfyouhavealreadyregisteredforMysupport,signinandskiptothenextstep.
Ifyouhavenotregistered,clickRegisternow.
Completetheregistrationformusingyoure-mailaddressasyourIBMIDandclickSubmit.
4.
ClickEditprofile.
5.
ClickAddproductsandchooseaproductcategory;forexample,Software.
Asecondlistisdisplayed.
6.
Inthesecondlist,selectaproductsegment;forexample,Data&InformationManagement.
Athirdlistisdisplayed.
7.
Inthethirdlist,selectaproductsubsegment,forexample,Databases.
Alistofapplicableproductsisdisplayed.
8.
Selecttheproductsforwhichyouwanttoreceiveupdates.
9.
ClickAddproducts.
10.
Afterselectingallproductsthatareofinteresttoyou,clickSubscribetoemailontheEditprofiletab.
11.
SelectPleasesendthesedocumentsbyweeklyemail.
12.
Updateyoure-mailaddressasneeded.
13.
IntheDocumentslist,selecttheproductcategory;forexample,Software.
14.
Selectthetypesofdocumentsforwhichyouwanttoreceiveinformation.
15.
ClickUpdate.
vRSSfeeds.
ForinformationaboutRSS,includingstepsforgettingstartedandalistofRSS-enabledIBMWebpages,visitwww.
ibm.
com/software/support/rss/GettingafixAproductfixmightbeavailabletoresolveyourproblem.
Youcangetfixesbyfollowingthesesteps:1.
Obtainthetoolsrequiredtogetthefix.
2.
Determinewhichfixyouneed.
3.
Downloadthefix.
Openthedownloaddocumentandfollowthelinkinthe"Downloadpackage"section.
4.
Applythefix.
Followtheinstructionsinthe"InstallationInstructions"sectionofthedownloaddocument.
ContactingIBMSupportIBMSupportprovidesassistancewithproductdefects.
BeforecontactingIBMSupport,yourcompanymusthaveanactiveIBMsoftwaremaintenancecontract,andyoumustbeauthorizedtosubmitproblemstoIBM.
CompletethefollowingstepstocontactIBMSupportwithaproblem:1.
Definetheproblem,gatherbackgroundinformation,anddeterminetheseverityoftheproblem.
2.
Gatherdiagnosticinformation.
3.
SubmityourproblemtoIBMSupportinoneofthefollowingways:vUsingIBMSupportAssistant(ISA)vOnline:ClicktheReportproblemstabontheIBMSoftwareSupportsite:http://www.
ibm.
com/software/support/probsub.
html4TivoliProvisioningManagerforOSDeployment:TroubleshootingandsupportguideIftheproblemyousubmitisforasoftwaredefectorformissingorinaccuratedocumentation,IBMSupportcreatesanAuthorizedProgramAnalysisReport(APAR).
TheAPARdescribestheproblemindetail.
Wheneverpossible,IBMSoftwareIBMSupportprovidesaworkaroundthatyoucanimplementuntiltheAPARisresolvedandafixisdelivered.
IBMpublishesresolvedAPARsontheIBMSupportWebsitedaily,sothatotheruserswhoexperiencethesameproblemcanbenefitfromthesameresolution.
ErrormessagesSystemprofileerrormessagesErrormessagesthatcanoccurwhentryingtocreateortoupdateasystemprofile.
SysprepisnotinstalledThismessagewillappearwhenyouarecreatingaWindowssystemprofileforcloning.
Beforecreatingasystemprofile,youneedtoruntheSyspreptool.
Unknown/UnsupportedOSThiswarningmessageoccurswhencreatingasystemprofileforcloning.
Theoperatingsysteminstalledcannotberecognizedorisnotsupported.
ThecurrentversionofTivoliProvisioningManagerforOSDeploymentsupportstheoperatingsystemslistedintheTivoliProvisioningManagerforOSDeploymentInstallationGuide.
ProfilesaretoooldTheOSdeploymentserverisnotabletoupdateWindowsVista/2008/7/201264-bitunattendedsetupprofilescreatedwithversion7.
1.
1.
1andloweroftheproductifthecorrespondingWinPE264-bitramdisksoftwaremoduleisnotpresentontheserver.
Inthiscasetheiconoftheprofileischangedto,thewarningmessageProfilesaretooold.
isissued,andtheprofilecannotbedeployedanymore.
Tosolvethisissue:1.
Createanewsystemprofile.
2.
Copytheconfigurationsfromtheoldsystemprofiletothenewsystemprofile.
3.
Deletetheoldsystemprofile.
OSdeploymenterrormessagesErrormessagesthatcanoccuronatargetduringadeploymentaredisplayedinaredpanel,inthecenterofthescreen,andareloggedtotheODBCdatabase.
SoftwareProfileandSoftwareItemtablesmustusethesameODBCsourceThismessageshouldneverappearwithastandardOSconfiguration.
ItwillappearifyousplittheSoftwareItemandSystemProfiletablesintotwodifferentODBCsources.
Invaliddestinationfolderforsoftwarecopy/systemsnapshotThedestinationfolderthatyouspecifiedduringthesoftwaremodulecreationdoesnotexist.
UnexpectedendofdeploymentjobOneoftherequiredtasksfailedduringthedeployment.
Youarenotauthorizedtousethismachine(off-line)Thismessageappearswhentheprocessofauthenticationfails.
Thecausemightbethatthenetworkisdown.
Troubleshootingandsupport5ThereisnoknownOSconfigurationforthistargetYouarerunningwithoutbeingconnectedtothenetworkandthedatabaseentryforthetargettodeploydoesnotcontainavalidOSconfiguration.
ThisOSconfigurationwasnotintended.
.
.
ThedeploymentschemehasthesettingNevereditparameters.
Thetargetisnotthesamemodelasthesystemprofiledeployed.
NoentryfoundintheBOMforthistargetThereisnoentryintheBillofMaterialtable(notargetdefinition)matchingthetargetcomputerMACaddress,UUID,andserialnumberandthedeploymentsettingshavebeensettodisablemanualeditionoftheBillofMaterial.
Nosystempartitionhasbeendefined.
.
.
Thiserrorshouldneveroccurunlessyouhavetamperedwiththedefinitionofasystemprofile.
Itresultsfromasystemprofiledefinitionthathasnobootablepartition(OSPartiszerointhedatabase).
InvalidSoftwareIteminthedatabaseThiserrorshouldneveroccur,unlessyouhavetamperedwiththedefinitionofsoftwareitems.
Itresultsfromaanunknownsoftwaremoduletype.
Cannotprocess.
.
.
softwareitemsinpasszeroAfloppy-diskorpartitionsoftwaremoduleisscheduledforuseinpasszero,conflictingwiththeSysprepprocess.
Toavoidthiserror,eitherschedulethesesoftwareitemswithnegativepassnumbers(beforeSysprep)orwithpositivepassnumbers(afterSysprep).
Cannotprocess.
.
.
softwareitemsbeforepasszeroAsoftwaremodulethatinvolveswritingtotheoperatingsystempartitionisusedbeforepasszero,whentheoperatingsystempartitionisformatted.
Toavoidthiserror,alwaysschedulethesesoftwareitemswithapositiveorzeropassnumber.
RequiredfilehasnotbeenenumeratedThisAutoCD-specificerrormessageshouldneveroccur.
ACD-sethasnotbeengeneratedcorrectly,probablybecauseofanerroroftheprogram.
Ifthemessageoccurs,sendareporttoyourreseller,withacopyoftheCD-set.
Thereisnotenoughspaceinpartition.
.
.
todownloadtheimagesAsystemprofilepartitioningschemeisnotcompatiblewithTivoliProvisioningManagerforOSDeployment.
Theharddiskpartitionschememustbecreatedsothatthesumoftheunpartitioneddiskspaceandofthefreespaceinthelastpartitionislargeenoughtostoreallcompressedpartitionandsoftwareimages.
SystemsetuphasnotbeenproperlycompletedThiserrorresultsfromapreviousseriouserrorintheSysprepprocess,thathaspreventedthemini-setuptocomplete(oreventostart).
Connectionrefused.
.
.
insql.
rbcTheTCPtoODBCgatewayservicethatshouldberunningontheOSdeploymentserverisnotacceptingconnections.
Thisserviceistypicallyautomaticallystartedwhentheprovisioningserverserviceisstarted.
Check(usingtheservicemanager)thattheTCPtoODBCGatewayserviceisinstalledandrunningonthecomputerhostingtheprovisioningserver.
6TivoliProvisioningManagerforOSDeployment:TroubleshootingandsupportguideNetworknotinitializedThiserrorresultsfromanabruptlystoppeddeployment,followedbyahard-diskbootthattriestorestartthedeployment.
However,becausethecomputerhasnotbeenstartedonthenetwork,thisisnotpossible.
Torestartthedeployment,rebootthecomputeronnetworkboot.
ThiscomputerhasbeeninterruptedduringadeploymentThismessageappears(onablackbackground)whenyourebootontheharddiskafterastoppeddeployment(typicallybecauseofanerrorortotheuserpressingCancel).
Thedeploymentwasnotcompleted,andmustberestartedbecausetheoperatingsystemisnotfullyinstalled.
PartitionsdonotfitonthisharddiskThesystemprofiletobedeployedonthistargetisbiggerthanthesizeofitsharddisk.
Alternately,aprotectedpartitiononyourdiskmightnothaveenoughspaceonthediskforthecurrentprofile.
Fatalerror,Noharddiskdetected!
Thismessageappearsifyoutrytodeployatargetwithoutharddisk.
CannotaccessinstallationmediaThismessagemightappearduringthedeploymentofaSLES10profileonaPowerPCtarget.
Itindicatesthattheswitchdidnotreestablishthelinktothenetworkcardinatimelyway.
SelectOKorRetrytoresumethedeployment.
ExportingthelogfilesinCommonBaseEvent(CBE)formatSymptomsIncaseyouwanttoexportthelogfilesinCommonBaseEvent(CBE)formatandanalyzethemusingPDtools,usethefollowingprocedure.
ResolvingtheproblemExportthelogfilesusingthefollowingcommand:rbagentrad-exportlogsdestination=destination[mode=mode[compress]][activityid=activityid]where:destinationIsthepathwherethecommonbaseeventmustbestored.
modeThefollowingmodesareavailable:vmode1:Allthelogsareplacedindestination.
(log|trc).
xmlmode.
vmode2:Allthelogsareplacedinthedestinationdirectory(onlyonefileforalltasks).
vmode3:Allthelogsareplacedinthedestinationdirectory(onefileforeachtask).
vmode4:Allthelogsareplacedinthedestinationdirectoryinrawformat.
compressIstheoptiontocompresstheresultingfile,onlyavailableifyouchoosemode4.
activityidIstheoptiontoexportonlytheactivitywiththespecifiedid.
Note:Themodes1,2,and3exportthelogfilesinCBEformat.
Troubleshootingandsupport7ProblemsandlimitationsThissectionprovidestroubleshootingguidanceandinformationaboutproductlimitationsforoperatingsystemdeployment.
ISACompatibilityFromversion5.
1.
1onwards,TivoliProvisioningManagerforOSdeploymentiscompatiblewithIBMSupportAssistant(ISA).
ISAcanhelpyoucollectlogsneededfortroubleshooting.
TocollectlogfileswiththeISA,youneedtohaveISAandtheTivoliProvisioningManagerforOSdeploymentplugininstalledontheprovisioningserver.
FormoreinformationaboutISAandtodownloadit,visithttp://www.
ibm.
com/software/support/isa/.
Duringthedatacollectionprocess,ISAasksyoufortheTivoliProvisioningManagerforOSdeploymentinstallationpathtoknowwherethelogfilesarelocated.
Thecollectedlogfilesarethencompressedintoajarfile.
ThepathandnameofthecompressedfilearegivenbyISAattheendoftheprocess.
OnWindows,itislocatedatC:/ProgramFiles/ISAandESA/IBMSupportAssistant/space/logs/.
ThefilenamestartswithisaCollector_SS3HLM.
WindowsServiceTroubleshootingforOSdeploymentserverIfyourOSdeploymentserverdoesnotworkcorrectly,oryoususpectthatsomethingiswrong,youhaveseveraloptionstocollectdebugginginformationfromtheOSdeploymentserver:vIftheserviceworksandtheserverisreachable,usethewebinterfaceandclickServerstatus/installationcheck.
Ifyoucanreadthesummary,theOSdeploymentserverisrunningandyoucancheckhereforpossibleerrors.
vIfyourserviceworksbutyouwantmoredebugginginformation,youcanalsochecktheServerlogfileswherealllogtypesaredisplayed.
ThelogverbositylevelcanbeincreasedifnecessaryusingServerparameters/Configuration.
vIfthewebinterfacecannotcontacttheOSdeploymentserver,checkthattheTivoliProvisioningManagerforOSDeploymentserviceandprocessesarerunning:–Windows:Usetheservicemanager–Linux/FreeBSD/OSX:typepsaux|greprembo–Solaris:typeps-elf|greprembovChecktheWindowsEventViewer.
TheOSdeploymentserverlogsunrecoverableerrorsmessagesintoeventmanager.
vIftheservicedoesnotstart,runrembo.
exefromthecommand-linewiththefollowingoptions:rembo-d-v4.
ThiswillruntheOSdeploymentserverasaconsoleapplication,withalldebuggingoutputredirectedtoyourcommandwindow.
Youcanincreasethedebuglevel(the-vparameter)to6formaximumdetail.
See"OSdeploymentservercommand-lineoptions"onpage9formoreoncommandlinearguments.
IfTivoliProvisioningManagerforOSDeploymentcomplainsaboutanerrorintheconfiguration,reinstallafreshcopyofTivoliProvisioningManagerforOSDeployment.
Iftheerrormessageisrelatedtoyournetworkconfiguration,trytofixyournetworkconfigurationandruntheserveragain.
Inparticular,youmustchangetheInterfacesglobalparameterifyourcomputerhasmorethanonenetworkinterface.
8TivoliProvisioningManagerforOSDeployment:TroubleshootingandsupportguideIfitstilldoesnotwork,contactyourIBMSoftwareSupportrepresentative.
OSdeploymentservercommand-lineoptionsrembo[-d][-vloglevel][-cconfigfile][-certrembokey]v-dprintsdebuginfotothestandardoutput,doesnotrunasdaemon(donotdetach)v-vsetstheverbositylevel(default:2)v-cspecifiestheconfigfilename(thedefaultisrembo.
conf)Theverbositylevelsaredefinedas:v0:nooutputv1:logerrormessagesonlyv2:logerrorandwarningmessagesv3:logerror,warningandinfomessagesv4:sameas3,butalsolognoticemessagesv5:sameas4,withdebugoutputv6:sameas5,withnetworktraceLimitationsAlistofknownlimitationsandproblems.
TivoliProvisioningManagerforOSDeploymentlimitationsNote:Refertotheproductreleasenotesormostrecentreadmefileprovidedwitheachfixpackforthemostup-to-dateinformationrelatedtoproblemsorlimitations.
vWhenperformingdirectdownloadsofgeneratedISOorCABfiles,thedownloadmightnotworkcorrectlywithInternetExplorer9installedonaWindows2008hostworkstation.
ThesamedownloadswillworkwithInternetExplorer9installedonaWindows7hostworkstation.
vWhendeployingasystemprofileagainstaSonymodel,thelastdigitoftheserialnumberisnotreportedintheTargetMonitor.
Theserialnumbergetstruncatedto15characters.
vTheBootonOSfunctiondoesnotchoosetheoperatingsystemtorunbutonlybootsfromthediskandisnotabletounderstandifyoudeployedamulti-bootsystem.
vThedeploymentonKVMguestsisnotsupportedusingthe"Virtio"disk.
Youmustchangethedevicetypeto"IDEDisk"byremovingthe"Virtio"device.
vOnsomeRAIDcontrollers,theautomaticRAIDconfigurationmightfail.
Inthesecases,usethecustomconfigurations.
vForworkstationswithanamountofmemoryslotsbiggerthanfour,thesizeofthememoryreportedontheinventorytabofthetargetdetailsmightbeinaccurate.
vVMWareESX3.
5u5profilesmightcausenetworkissuesonHPDL585G2hardware.
vThenetworkmightnotbeconfiguredproperlyonHPDL580G7hardwareafterasuccessfulWindows2003deploymentevenifthenetworkdriverisboundtotheprofile.
vSuSELinuxEnterpriseServer(SLES)11SP1operatingsystemdeploymentsarenotsupportedonHPDL580G7workstations.
v32-bitprofilesarenotsupportedonIBMx3850x5servers.
Troubleshootingandsupport9vRedHatEnterpriseLinux(RHEL)5.
532-bitoperatingsystemisnotsupportedonIBMx3850x5servers.
Thisoperatingsystemissupportedonlyonx3850Aservers.
vForsoftwaremodulesinpre-partitioningandpre-OSphasesthefollowingapplies:–ThecurrentWebinterfaceenablesyoutoaddarebootwithinthe"Softwareapplicationorder"popupdialog,evenifitdoesnotmakesensetoaddarebootbetweenthesesoftwarestagesbecause,afterareboot,thedeploymentstateislostinbothcases.
–Pre-partitioningsoftwareisappliedintotheRAM.
Thedeploymentstateislostafterthereboot.
–Forpre-OSsoftwarethereiscurrentlynocacheandthedeploymentstateisalsolostafterthereboot.
vTocreateoneofthefollowingsystemprofiles,youmustusethebrowseronaLinuxworkstationwiththewebinterfaceextensioninstalled:–SLES10SP332-bit–SLES10SP364-bit–SLES10SP432-bit–SLES10SP464-bitvAfterthetargetisbootedontheOSdeploymentserver,ifthetargethastwoNICcards,theinventorydetailsforthattargetonlyshowoneentryforoneNICcard.
vIntheoperatingsystemdeployment,LVMisnotsupported,ifitspansmultipledisks.
vSoftwaresnapshotsaredeprecated.
TheyarenotsupportedonLinux,andyoucanonlyrestorepreviouslycreatedsoftwaresnapshotsonWindows.
vForWindowscloning,becauseofSyspreplimitations,itisnotpossibletochangetheadministratorpasswordduringthedeploymentifthesystemprofilecontainsanon-emptyadministratorpassword.
vForWindowsgoldenmasterimage,becauseofSyspreplimitations,itisnotpossibletochangetheadministratorpasswordduringthedeploymentifthesystemprofilecontainsanon-emptyadministratorpassword.
ThislimitationonlyappliesifyourunSysprepyourselfmanually.
vtargetsonlysupportsincrementalimagesontheprimaryOSpartition.
Ifyouwanttoinstallsoftwareonasecondarypartition,youmustusesoftwareupdatepackageswithanunattendedsetupcommandline.
vtargetssupportsonlyupto3primarypartitions.
Ifyouhavemorethan3primarypartitions,transformtheextraonesintoextendedorlogicalpartitions.
vThefollowingoptionsarenotavailablewhendeployingWindows2000ontargets:–AdvancedIPsettings–JoinaWindowsdomainonsite–Adddomainusertolocaladmingroup–Forceusertoputanewadminpassword–CreatelocalaccountforuservVMwareESXi5.
0and5.
1donotsupportBootOnOSandGreenbannerendaction.
Theywilldefaulttootherendaction.
GreenbannerperformsashutdownandBootOnOSperformsareboot.
vWhenperformingDirectMigrationorwhilecapturingaprofileorvirtualimage,theMicrosoftSystemReservedpartitioniscapturedbutitisempty.
10TivoliProvisioningManagerforOSDeployment:TroubleshootingandsupportguideDatabase-relatedlimitationsThehardwareinventoryrecordsuptofourmemoryslotsonly.
Problemswiththekernel-freeinBIOSmodeInventorylimitationinkernel-freemodeSymptomsCD-DVDinformationisnotcapturedintheinventorydetailswhenthetargetbootsinkernel-freemode.
ResolvingtheproblemNoworkaroundiscurrentlyavailabletosolvethisissue.
BootonOSonIBMx3850failsinkernel-freemodeSymptomsYouperformadeploymentonanIBMx3850hardwareinkernel-freemode.
Thedeploymentissuccessfulanditdisplaysthegreenbanner.
ButafterclickingBootonOS,thetargetdoesnotbootontheoperatingsystem,itbootsonthenetwork,againinkernel-freemode.
ResolvingtheproblemToperformtheBootonOSonanIBMx3850workstation,itisnecessarytoupdateitsBIOSwiththelatestversion1.
32.
Bootfailsonsometargetswhendeployinginkernel-freemodeSymptomsWhendeployingonmultipletargets(morethan20)inkernel-freemode,sometargetsmightnotbeabletobootduringthedeployment.
Thefollowingmessageisdisplayedonthetargetforseveralminutes:Bootfailed:pressakeytoretry,orwaitforreset.
.
.
.
ResolvingtheproblemAsaworkaround,specifythenetworkbeforetheharddiskinthebootlist.
Afterthereboot,thetaskisabletobeautomaticallyrecoveredandnomanualstepsareneeded.
Problemswiththekernel-freeinUEFImodeIncompleteinventoryinUEFImodeonIBMHS22SymptomsWhenyouPXEbootinUEFImodeonIBMHS22,thePCIIOprotocolisnotinitializedandtheinventoryisincomplete.
ResolvingtheproblemToperformthePXEbootinUEFImode,itisnecessarytoupdatetheBIOSwiththeversionP9E155Borlater.
SomeUEFItargetsfailtoPXEbootSymptomsWhilePXEbootingUEFItargets,youcanencounterproblemsiftheUEFIfirmwareversionisoutofdate.
ResolvingtheproblemTroubleshootingandsupport11WiththecurrentUEFIfirmwareversion,someUEFItargetsdonotprocesscorrectlyDHCPoption43,theyrequireoption66and67tobeset.
FormoreinformationchecktheDHCPserverconfigurationsectionintheInstallationGuide.
ProblemswiththeOSdeploymentserverandthewebinterfaceextensionManytaskssuddenlyfailWhenmanytasksaresuddenlyfailing,thereisasimplecheckthatyoucaneasilyperformtocheckthestateofyourOSdeploymentserver.
SymptomsManyofthetasksyoutrytoperformfailwithoutapparentreason.
CausesSomeoftheservicesordaemonsoftheOSdeploymentserverarenotproperlystarted.
DiagnosingtheproblemGotoServer>OSdeployment>TargetMonitor.
.
Youshouldhaveatleastthefollowingtwoentries:unknownThisentryreferstotheOSdeploymentserveritself.
IPoftheOSdeploymentserverThisIPaddressispresentwhentheWebinterfaceextensionisrunningontheOSdeploymentserver.
Oneoftheseentries,orboth,doesnotappearintheTargetMonitoranymore.
ResolvingtheproblemvIfunknownhasdisappeared,restarttheOSdeploymentserver.
vIftheIPaddressoftheOSdeploymentserverhasdisappeared,makesurethewebinterfaceextensionisinstalledontheOSdeploymentserverandrestartit.
Afterthesesteps,bothunknownandtheIPaddressoftheOSdeploymentservershouldbepresentandyourOSdeploymentservershouldworkagain.
FailuresincreatingordeployingaprofileorsoftwaremoduleWhenyoucannotcreateordeployprofilesorsoftwaremodules,OSdeploymentservermighthaveafulltemporarydirectory.
SymptomsYoucannotcreateordeployprofilesorsoftwaremodules.
CausesOSdeploymentservermighthaveafulltemporarydirectory.
ResolvingtheproblemCleanupthetemporarydirectoryinsidetheOSdeploymentserverinstallationdirectoryonaregularbasis.
ThetemporarydirectoryisTPMfOSD_INST_PATH\temp.
OSdeploymentserverstopsrespondingTheOSdeploymentservermightstoprespondingiftoomanyportsarealreadyinuseanditdoesnothaveanyleftforcommunication.
12TivoliProvisioningManagerforOSDeployment:TroubleshootingandsupportguideSymptomsUnderWindows,theOSdeploymentserverstopsrespondingwithoutanyapparentcause.
CausesThismightbeduetothelimitednumberofportandsocketsavailablebydefaultonWindowsoperatingsystems.
UseoftheJavaAPImightcausetoreachthislimit.
ResolvingtheproblemYoucantrytosolvethisproblembyallowingTCPtoassignhigherportnumbersthanthedefault5000andprovidingasmallerwaitingtime,inseconds,beforeTCPcanreleaseaclosedconnection.
Todoso:1.
StoptheOSdeploymentserver2.
Editthefollowingregistrykeysandprovidethevaluessuggested"HKLM/system/CurrentControlSet/Services/TcpIp/Parameters/MaxUserPort"=65534"HKLM/system/CurrentControlSet/Services/TcpIp/Parameters/TCPTimedWaitDelay"=303.
RestartyouOSdeploymentserver.
CorruptedcharacterdisplayonAIXduringsetupSymptomsThecharactersdisplayedduringproductsetuponAIXarecorrupted.
Messagesareunreadable.
CausesYourlocaleisnotUTF-8compliant.
EnvironmentvYouroperatingsystemisAIX.
vYourlocaleisnotUTF-8compliant.
DiagnosingtheproblemYouareinstallingTivoliProvisioningManagerforOSdeploymentonanAIXcomputerusing.
/setup.
Themessagesdisplayedby.
/setupcontaincorruptedcharacterswhichrenderthecontentofthemessagesunreadable.
ThelanguageyouareusingtoinstalltheproducthasseverallocalesandtheoneyoucurrentlyusingisnotUTF-8compliant.
ResolvingtheproblemTherearetwopossibleworkarounds:vChangethecharacterencodingofyourterminalsessiontoUTF-8andrunsetupagain.
vChangeyoursessionsparameterstoanUTF-8compliantlanguageencodingandrunsetupagain.
ServerandwebinterfaceextensionTheOSdeploymentserverandthewebinterfaceextensioncannotstartproperlyonaLinuxtargetwhichhasitslocalesettoTurkish.
SymptomsTheOSdeploymentserverorthewebinterfaceextensionfailstostartonLinuxtargetswhenthelocaleissettoTurkish.
Anerrorwiththefollowingtextmightappear:Troubleshootingandsupport13Unknownerror(ERROR:columnnotfound:@@id)CausesTivoliProvisioningManagerforOSDeploymentcannotworkinaTurkishlocale.
EnvironmentTheOSdeploymentserverorthewebinterfaceextensionisinstalledonatargetrunningLinuxinaTurkishlocale.
ResolvingtheproblemSetthelocaletosomethingelsethanTurkish,forexampleUSEnglish.
TasksappearwitherroneousdatesandtimesinthewebinterfaceProblemdescriptionWhenusinganApacheDerbydatabasewithanOSdeploymentserverinstalledonLinux,tasksmayappearwitherroneousdatesandtimesinthewebinterface.
ProblemresolutionvSettheTZvariable.
Todoso1.
Usethetzselecttooltohelpyoufindyourappropriatetimezone.
2.
SettheTZenvironmentvariabletotheappropriatevalue.
3.
ExporttheTZvariableintheApacheDerbyenvironment.
Exampleforsteps2and3inSwitzerland:TZ='Europe/Zurich';exportTZvModifyyourApacheDerbystartupscript,ifyouhaveone.
Includethe-Duser.
timezonecommandlineoptionlineinyourscript.
Forexample,ifyouwanttouseUTC,type-Duser.
timezone=UTC.
ThewebinterfaceextensionisnotdetectedSometimes,thewebinterfaceextensionisnotcorrectlydetectedonUNIXandLinuxOSdeploymentservers.
SymptomsThewebinterfaceextensioniscorrectlyinstalledandisrunning,butitisnotdetectedbytheOSdeploymentserver.
Arediconforthewebinterfaceextensionisdisplayed.
CausesTheOSdeploymentserverisnotlisteningtothecorrectinterfaceandcannotthereforedetectthewebinterfaceextension.
Resolvingtheproblem1.
Openrbagent.
logandfindthelastoccurrenceConnectxx.
xx.
xx.
xx->yy.
yy.
yy.
yywherexx.
xx.
xx.
xxandyy.
yy.
yy.
yyarebothIPaddressesoftheOSdeploymentserver.
2.
Takenoteoftheyy.
yy.
yy.
yy.
3.
Edit/etc/hosts.
4.
Moveoraddthelinewiththeyy.
yy.
yy.
yybeforethelinewiththelocalhostinterface(127.
0.
0.
1).
5.
RestarttheOSdeploymentserverdaemon.
14TivoliProvisioningManagerforOSDeployment:TroubleshootingandsupportguideNow,theOSdeploymentservercanresolvethehostnameproperlyanddetectthewebinterfaceextension.
ProblemsprovisioningWindowsoperatingsystemsDeployingWindowsfailsduetomissingstoragedriverSymptomsWhenyoudeployWindowsoperatingsystem,anincorrectbuilt-inmassstoragedriverisusedbytheoperatingsystem,andabluescreendisplayswhenbootingontheoperatingsystem.
CausesIntheoperatingsystemisincludedanincorrectdriverthatmatchesthestoragedevice.
Evenifyoubindthecorrectsoftwaremoduledriver,theincorrectdriveristaken.
ResolvingtheproblemTosuccessfullydeployWindows,performthesesteps:1.
Locatethestpwndxxxx.
1fileundertheTPMfOSD_DATA_DIR/global/partitiondirectory.
Thisistheimagefileoftheoperatingsystemyouaredeploying.
2.
Renameitintostpwndxxxx.
wim.
3.
MountitusingWindowsAutomatedInstallationKit(WAIK).
4.
RemovethedriverusingWAIK.
5.
Unmountthestpwndxxxx.
wimfileandrenameitbackintostpwndxxxx.
1.
Alternatively,modifytheimagebeforecreatingthesystemprofile.
Windows2003deploymentfailureontargetwithtwoharddisksDuringWindow2003deployment,WinPEbootsfromadiskdifferentthantheoneusedbyPrebootExecutionEnvironment(PXE).
SymptomsUnattendeddeploymentofWindows2003failswiththefollowingerror:RemboMBRdetected,andnopartitionismarkedwiththebootableflagResolvingtheproblemFromBIOSonthetargetmachinechangethebootorderoftheharddiskstohavethesamebootorderforWinPEandPXE.
Windows2000/2003/2008/XP/Vista/7reportsthatithasdiscoveredanewdeviceSymptomsInsomecases,Windows2000/2003/2008/XP/Vista/7mightreportthedetectionofanewdeviceandaskforarebootafterrestoringanimageusingTivoliProvisioningManagerforOSDeployment,eveniftheimagewasmadeonthesamehardware.
ResolvingtheproblemTherearetwocausesofaWindowsredetectionofhardware:vRestoringanimageontheexactsamekindofhardwarebutonanothercomputer.
Somecomponents(includingtheharddiskdrive)includeauniqueserialnumber.
ThisisnotvisiblewhendeployinganimageinSysprepbecauseSysprephandlestheredetectionsilently,butthiscanaffectarestorationifSysprepmini-setuphadnotbeenusedduringthecreationoftheimage.
Troubleshootingandsupport15vAchangeinthepartitionsize.
Windows2000/2003/2008/XP/Vista/7storesinformationregardingtheoperatingsystempartitionlayoutintheregistry,andmightneedarebootifthepartitionhaschanged.
ThisistypicallynotvisiblewhendeployinganimageinSysprepbecauseSysprephandlestheredetectionsilently,butitcanaffectaplainrestoration.
Insomecases,itcanaffectatypicaldeployment,iftheoperatingsystempartitiongoestotheendofthedisk,becauseTivoliProvisioningManagerforOSDeploymentneedstoresizeittemporarilytostoreitsimagefilesduringthedeployment.
Theworkaroundistohaveanotherpartitionaftertheoperatingsystempartition,sothattheoperatingsystempartitionitselfisnotresizedduringthedeployment.
AccessingtargetdevicesduringdeploymentSymptomsDuringdeploymentonanIBMsystemx3350thefollowingmessageisdisplayed:Pleaseinsertdiskintodrive.
ResolvingtheproblemVerifythatallyourdevicescanbeaccessed.
WinPEdoesnothavethedrivertohandletheNICSymptomsWindowsPreinstallationEnvironment(WinPE)startsonthetargetanddoesnothavethedrivertohandletheNIC.
ResolvingtheproblemEnsurethatyouinstallthedriver,whichisWinPEcertified,forhandlingtheNIC.
Createthesoftwaremodule,relatedtotheWinPEdriver,forthetarget.
Fromthedrivergrid,bindthedrivertothesoftwaremodule.
Formoredetails,seeBindingdriverstoaWinPEdeploymentengine.
WindowsVista/2008/7/2012askforaproductkeyduringdeploymentProblemdescriptionInsomecircumstances,WindowsVista/2008/7/2012askforaproductkeyduringdeploymentofacloningorcloningWIMsystemprofilecreatedwithSysprepinauditmode.
ThisproblemoccursonlyifvYouaredeployingacloningorcloningWIMsystemprofileofWindowsVista/2008/7/2012.
vTheprofilewascreatedwithSysprepinauditmode.
vYoudonothaveaVolumeLicensingversionofWindowsVista/2008/7/2012.
ProblemresolutionThisisknownbehaviorofbothWindowsVista/2008/7/2012operatingsystems.
IftheproductkeywasprovidedintheOSconfiguration,youcanleavethefieldemptyandclicktocontinue.
WindowsVista/2008/7/2012promptsyouforanAdministratorusernameduringdeploymentProblemdescription16TivoliProvisioningManagerforOSDeployment:TroubleshootingandsupportguideWindowsVista/2008/7/2012promptsyouforanAdministratorusernameduringdeployment.
ProblemresolutionIfWindowsVista/2008/7/2012promptsyouforanAdministratorusername,itisbecauseWindowsVista/2008/7/2012requiresanewlocalaccountwhenstartingforthefirsttime.
IfyouwanttoavoidbeingpromptedforanAdministratorusername,provideitintheOSconfiguration.
DriveletterincorrectlysetWhendeployingavirtualimageormigratingaWindowsoperatingsystem,theWdriveisassignedanewdriveletter.
SymptomsOnWindowsoperatingsystem,oneofyourdrivesissettoletterW.
Afterdirectmigrationorthedeploymentofavirtualimage,thisdriveisrandomlyassignedanotherletteronthereceivingtarget.
Allotherdriveskeeptheiroriginalletter.
CausesDriveletterWisnotavailableonWindowsoperatingsystemsinstalledbytheproduct.
DomainnameserverisnotsetafteraWindowsXP64-bitdeploymentSymptomsDomainnameserver(DNS)informationisnotcorrectafterthedeploymentofaWindowsXP64-bitplatform.
CausesOnWindowsXP64-bitplatforms,ifyoucreateaprofile,modifythetargetsettingswithadvancednetworksettingsandcompletethefollowingfields:IPaddress,gateway,DNSserverandDNSdomain.
Afterthedeploymentallsettingsarecorrectlyset,exceptfortheDNSdomain.
DeployingWindowsonLinuxpartitionsfailsYourWindowssystemprofiledeploymentfails.
SymptomsYourdeploymentofaWindowssystemprofilecontainingLinuxpartitions(forexample,LinuxswapandEXT2)fails.
TheerrormessageindicatesCommand[diskpart/sX:\windows\TEMP\4ECCC1F83AC358F3_1\partscript.
txt]failedwithexitcode5.
CausesSinceversion7.
1.
1,theproductleveragesWinPEforWindowsoperatingsysteminstallation.
WinPEdoesnotrecognizeLinuxpartitions.
Thiscausesthedeploymenttofail.
ResolvingtheproblemTheonlysolutionistoeditthesystemprofiletoremovetheLinuxpartitions.
Troubleshootingandsupport17DeployingWindowsonLinuxpartitionsfailsYourWindowssystemprofiledeploymentfails.
SymptomsYourdeploymentofaWindowssystemprofilecontainingLinuxpartitions(forexample,LinuxswapandEXT2)fails.
TheerrormessageindicatesCommand[diskpart/sX:\windows\TEMP\4ECCC1F83AC358F3_1\partscript.
txt]failedwithexitcode5.
CausesSinceversion7.
1.
1,theproductleveragesWinPEforWindowsoperatingsysteminstallation.
WinPEdoesnotrecognizeLinuxpartitions.
Thiscausesthedeploymenttofail.
ResolvingtheproblemTheonlysolutionistoeditthesystemprofiletoremovetheLinuxpartitions.
Windowsdeploymentfailswithastoperror7BonabluescreenYourWindowsdeploymentfailswithastoperror7Bonabluescreenbecauseofamissingdiskdriver.
SymptomsYourWindowsdeploymentfailswithastoperror7Bonabluescreen,asshowninFigure1.
CausesAdiskdriverismissingfromyoursystemprofile.
ResolvingtheproblemFigure1.
Stoperror7Binabluescreen18TivoliProvisioningManagerforOSDeployment:TroubleshootingandsupportguideYoumustfigureoutwhichdriverismissing,bindittothesystemprofile,anddeploythesystemprofileagain.
Todiscoverwhichdriverismissing:1.
GotoServer>OSdeployment>Systemprofiles>Profiledetails.
2.
ScrolldowntotheDrivershandlingsection.
3.
Ifyouareusingtheregularsoftwarerules,clickSwitchtodriverspecificbindingsmode.
4.
ClickEditprofile'sdriverbindings.
5.
Usethegridtolocatemissingmassstoragedevicedriversandtobindsuitabledrivers.
6.
Startyourdeploymentagain.
TimeoutlimitcanbereachedduringOSProbeofWindowsOSThetimeoutlimitcanbereachedduringOSProbeofWindowsOSwithslownetworksorslowmachines.
SymptomsWhenWinPEisdownloadedontargetsfromserver,itcantakealongtimefortheimagetobetransferredonthenetwork.
Ifthetransferisveryslow,sometaskslikeOSprobe(detectionofOStocapture)couldhitatimeouterrorsincedefaulttimeoutforthistaskis10minutes.
ResolvingtheproblemTospeedupthetransferofWinPEimagefromservertotargets,thefollowingparametersmustbecustomizedforWinPEtaskcreation:vTftpBlockSizevTftpWindowSizeTocustomizetheseparameters,gotothetableSettings,lookfortherecordwhereType="WPECREAT"andgetthevaluecorrespondingtothefieldIniFile,forexample,radset-sttngsfrRTPSPEC9.
ini.
EdittheINIfile,locatedinthe/global/schemesbychangingthevalueassignedtotheTftpBlockSizeandTftpWindowSize,asshowninthefollowingexample:[Task]type="WPECREAT"[Settings]StartEnv="*"TftpBlockSize="1432"TftpWindowSize="4"ScratchSpace="32"ItisnotnecessarytorestarttheserverortheWebInterfaceextension,youcanjustrecreateWinPEengines.
WinPEscratch-spaceisinsufficientThetimeoutlimitcanbereachedduringOSProbeofWindowsOSwithslownetworksorslowmachines.
SymptomsWhilerunningthecommandstartnet.
cmdintheWinPEenvironment,thefollowingmessagecouldappear:Thereisnotenoughspaceonthedisk.
Afterthismessageisdisplayed,arebootcouldbeperformed.
ItisverylikelythatWinPEscratch-spaceisinsufficient.
ScratchspacesettingrepresentstheamountofwritableTroubleshootingandsupport19spaceavailableontheWindowsPEsystemvolumewhenbootedinRAMdiskmode.
Bydefault,WindowsPEallocates32MBofmemorytoallocatetotheWindowsPEworkspace,validvaluesare32,64,128,256,and512.
TheWinPEscratchspacemightprovideinsufficientspacetocopyalltherequireddriverssoftwaremodulesonthespecifictargetmodel.
TousetheWinPEdriverinjectionbytheBindingGridforaspecifictargetmodeltoinjectasetofsoftwaremodulesrequiresanamountofspacegreaterthen32Mb.
TheWinPEinvolvedmustbecreatedwithanappropriatequantityofscratchspace.
YoucanfindexamplesaboutWinPEscratchspaceathttp://technet.
microsoft.
com/en-us/library/dd799244%28v=ws.
10%29.
aspxandhttp://technet.
microsoft.
com/en-us/library/hh824936.
aspxResolvingtheproblemTocustomizescratch-space,gotothetableSettings,lookfortherecordwhereType="WPECREAT"andgetthevaluecorrespondingtothefieldIniFile,forexample,radset-sttngsfrRTPSPEC9.
ini.
EdittheINIfile,locatedinthe/global/schemesbychangingthevalueassignedtotheScratchSpace,asshowninthefollowingexample::[Task]type="WPECREAT"[Settings]StartEnv="*"TftpBlockSize="1432"TftpWindowSize="4"ScratchSpace="32"ItisnotnecessarytorestarttheserverortheWebInterfaceextension,youcanjustrecreateWinPEengines.
ProblemsprovisioningLinuxandUNIXoperatingsystemsRPMpackagesaremissingfromtheprofileSymptomsARedHatEnterpriseLinuxdeploymentmightfailduetomissingRPMpackages.
Thismighthappenbecausea"PRUNE"phaseisperformed,whencreatingtheLinuxsystemprofile,toreducetheprofilesizebyexcludingunnecessaryRPMpackages.
Theselectionbytheuserofdifferentcombinationsofsoftwaregroupswhencreatingtheprofilemightcausethe"PRUNE"processtodiscardsomeneededRPMpackages.
ResolvingtheproblemTosolvethisissue,createontheOSdeploymentserveranemptyfilenamed:RH_PROFILE_INCLUDE_ALL_RPMundertheBasedirectoryforOSdeploymentserverfiles/globaldirectory;thenrecreatethesystemprofile.
DeployingLinuxonIBMT410laptopfailsSymptomsWhenyouperformHTTPdeploymentsofLinuxoperatingsystemonIBMT410laptop,thedeploymentfails.
CausesLinuxHTTPdeployments,onIBMT410laptop,usingstaticIPaddressfailsbecausetheNICwakesupslowly,afterkickstartreconfiguresit,andtheinstallerstartsbeforetheNICiscompletelyready.
20TivoliProvisioningManagerforOSDeployment:TroubleshootingandsupportguideResolvingtheproblemTosolvethisissue,settheTCP/IPsettingtoDynamicIP(DHCP).
InstallingLinuxonatargetwithmultipleNICfailsSymptomsWhenyouinstallLinuxonaworkstationwithmultipleNIC,thedeploymentmightfailbecausethetargetcannotconnecttotheserver.
CausesIfyoudonotswitchtoAdvancedIPnetworksettings,onlythefirstNICwillbeconfigured.
ThedeploymentfailsifthetargettriestoconnecttotheserverwithadifferentNIC.
ResolvingtheproblemTosolvethisissue,switchtoAdvancedIPnetworksettingswheninstallingtheLinuxoperatingsystemonaworkstationwithmultipleNIC,byselectingTargetDetails>Commonnetworkinginfo>SwitchtoAdvancedIPsettingmode.
IssueonLinuxtargetwithmultipleNICSymptomsOnaLinuxworkstationwithmultiplenetworkcards,ifthenetworkcardconnectedtotheOSdeploymentserverisnotthefirstoneasdescribedin"InstallingLinuxonatargetwithmultipleNICfails,"theunattendedLinuxinstallationloopsbooting.
ResolvingtheproblemTosolvethisissue,selectTargetMonitor>TargetDetails>AdvancednetworksettingofthenetworkcardconnectedtotheOSdeploymentserver,andspecifythecorrectConnectionnameforthatnetworkcard.
ItisthelogicalnamethattheLinuxoperatingsystemassignstothenetworkdevice,suchaseth3oreth5.
AddinganewpartitiontoRHELunattendedsystemprofilefailsSymptomsWhenyouinstallanunattendedRedHatEnterpriseLinux(RHEL)systemprofile,ifthesystemprofilehasnomountpointprovidedforapartition,duringtheHTTPdeployment,thefollowingerrorisdisplayed:Thefollowingerrorwasfoundwhileparsingthekickstartconfigurationfile.
Thefollowingproblemoccurredonline8ofthekickstartfile:themountpoint"none"isnotvalid.
ResolvingtheproblemTosolvethisissue,alwaysprovideamountpointforpartitionsinthesystemprofilepartitionlayoutorusenon-HTTPdeployments.
DeployingVMWareESX/LinuxfailsSymptomsWhenyoudeployLinuxorVMWareESXoperatingsystems,thedeploymentmightfailandthefollowingerroroccurs:UnabletobootLinuxwiththerequestedparametersbecausetheLinuxkernelorinitialramdiskcannotbefound.
CausesThedefaultdevicemappingisnotworking.
ResolvingtheproblemTroubleshootingandsupport21Tosolvethisissue,manuallyinstallLinuxorVMWareESXusingtheCD/DVDontheworkstationtoidentifythedevicesusedandtousethecorrectdevicenameintheprofile.
DeployingLinuxinkernelmodefailsSymptomsWhenyoudeployLinuxusingthestandardinstallation(HTTPmode,kernelmode),duringthedeploymentthefollowingerroroccurs:UnabletobootLinuxwiththerequestedparametersCausesTheissueiscausedbythefactthatthe/bootdirectoryisonanext4filesystem.
ResolvingtheproblemTosuccessfullydeployLinuxusingthe/bootdirectoryonanext4filesystem,performthedeploymentinkernel-freemode.
GraphicsManagerisnotcorrectlyconfiguredafterdeployingSLES11.
1SymptomsWheninstallingSuSELinuxEnterpriseServer(SLES)11.
1onanhyper-vguestwithagraphicaldisplaymanager(gnome,kdm),theinstallationendssuccessfullybutyoumightexperiencesomeproblemswhenloadingtheGUIpanel,afterthedeploymentiscompleted.
CausesResolvingtheproblemTosolvethisissue,chooseoneofthefollowingoptions:vUsethefollowingcustomautoinst.
xmlfile:;;16gdmtruetrue971603043RYI109-B5RYI1280x1024(SXGA)gnomevUsethefollowingcustomautoinst.
xmlfile:;;1280x1024(SXGA)vRunfromtheterminalthefollowingcommand:sax2-ra;/usr/sbin/rcmxdmrestart22TivoliProvisioningManagerforOSDeployment:TroubleshootingandsupportguidetoreconfiguretheGUI.
fdiskutilityfailsduringdeploymentSymptomsWhenyouperformadeploymenttask,thefdiskutilitymightfail.
CausesTheissueisverylikelyrelatedtotheRAIDdiskpartitioning.
ResolvingtheproblemTosolvethisissue,youhaveoneofthefollowingoptions:vPerformadiskblankingandthenrunagainthedeployment.
vLogintoLinuxdeploymentengineandrunthefollowingcommand:ddif=/dev/zeroof=/dev/cciss/c0d0count=1Rebootthesystemandtryagainthedeployment.
DeploymentofSLESusingKernelFreemethodandhttptechniquemightfailSymptomsWhendeployingtheSuSELinuxEnterpriseServer(SLES)operatingsystem,usingtheKernelFreemethodandtheHTTPtechnique,thedeploymentmightfailanddisplaythefollowingerrormessage:Unabletofindinstallationsource.
.
.
.
.
CausesTheclientisunabletoaccesstheOSdeploymentserverduetoamissingnetworkdriver.
ResolvingtheproblemEnsurethatyouhavethedriverforyournetworkcardcopiedontoaCD-ROMoraUSBdrive.
Whenthescreendisplaystheerror,pressENTER.
TheninserttheCD-ROMortheUSBpen.
FromtheredscreenclickOK->Kernelmodules->AdddriverupdateandselecttheUSBpenortheCD-ROM.
Youshouldreceiveaconfirmationthatthedriverupdatewassuccessful.
AttheerrorscreenpressF9>toaccessthecommandwindowandconfigurethenetworkcardwithyournetworkspecificparameters,forexample:ifconfigeth0inet192.
168.
1.
1broadcast192.
168.
1.
255netmask255.
255.
255.
0upVerifyiftheconfigurationwassuccessfulbypingingtheOSdeploymentserver.
ReturntotheWebinterfacedialogwheretheerrorpoppedupbypressingor.
PressENTERtostartthemanualinstallation.
SelectStartInstallationorSystem.
Specifytheinstallationoptionssuchastypeofinstallation"network",technique"http",andprovideeitherthestaticorthedynamicIPaddress.
Youcannowproceedwiththeinstallation.
IssuewhendeployingLinuxprofileonKVMguestSymptomsWhendeployingaLinuxprofileonaKVMguest,thedeploymentmightfailanddisplaythefollowingerrormessage:autoinst.
xmlcannotbefoundTroubleshootingandsupport23ResolvingtheproblemEnsurethatthediskmappingoftheprofilehasnoothermappingscheckedexceptfor/dev/hda.
SLESdeploymentonPowerPCswitchestointeractiveASuSELinuxEnterpriseServerdeploymentonaPowerPCwithmultiplenetworkcardsswitchestointeractiveinstallationwhenitisnotregisteredwithitsfirstnetworkcardintheOSdeploymentserver.
SymptomsYouaredeployingaSuSELinuxEnterpriseServersystemprofileonaPowerPCtargetwithmorethanonenetworkcard.
Thedeploymentstarts,searchesforaDHCPaddressforitsfirstnetworkcardanddoesnotfindit.
ThemessageSendingDHCPrequestforisdisplayed,whereisthenameofthefirstnetworkcardofthetarget.
Thetargetswitchestointeractiveinstallation.
CausesYouhaveregisteredyoutargetwithanetworkcardwhichisnotthefirst.
Resolvingtheproblem1.
GotoOSDeployment>Profiles>Profiledetails>OSconfigurationdetails.
2.
SelectUnix.
3.
ClickEdittoedittheFixedUNIX-specificprop.
.
4.
UpdatethefieldNetbootdevicetoreflectthenetworkcardwhichwasusedwhenregisteringthetargetintheOSdeploymentserver.
5.
Onceyourconfigurationisupdatedwiththeappropriatenetworkcard,youcanstartthedeploymentagain.
FirmwareerrorduringLinuxdeploymentonPowerPCSuSELinuxEnterpriseServer(SLES)10deploymentfailsonPowerPC,afterthefilesarecopiedonthetargetandthetargetisrestarted.
Theinstallationprocesscannotcontinuebecauseafirmwareexceptioniscaught.
SymptomsWhendeployingaSLES10onPowerPC,thedeploymentstartscorrectly.
TheYASTinstallerinstallsfilesonthetargetandcorrectlyrestartsthetargettocontinuetheinstallationprocesswithtargetconfiguration.
However,whenthetargetrestartsoncemore,theinstallationprocessstopsbecauseafirmwareexceptioniscaught.
Thetargethangs.
Whenusingthesamemediatoinstallthetargetmanually,theinstallationproceedssmoothly.
CausesThisseemstohappenonlyonoldfirmware.
ResolvingtheproblemUpdatethefirmwareofthetargetandtrydeployingagain.
LinuxdeploymentofunattendedsetupimagefailswithspaceerrorSymptomsWhendeployingaLinuxprofile,thedeploymentfailswiththemessageNospaceleftondevice.
24TivoliProvisioningManagerforOSDeployment:TroubleshootingandsupportguideResolvingtheproblemToworkaroundthis,increasethesizeoftheswappartitionontheharddiskdriveofyourtargetcomputer.
LVMpartitionsarenotsupportedwithRedHat4.
8unattendedsetupAftersuccessfuldeploymentofaRedHat4.
8unattendedsetupsystemprofilewithanLVMpartitioninwhichKickstartneedstowritedata,startingontheoperatingsystemfails.
SymptomsYouhavecreatedaRedHat4.
8unattendedsetupsystemprofilewithLVMpartitions.
Youhavesuccessfullydeployedtheprofile,butyouarenotabletostarttheoperatingsystem.
CausesKickstartofRedHat4.
8isnotabletowriteonLVMpartitions.
ResolvingtheproblemDonotuseLVMpartitionsinyourRedHat4.
8unattendedsetupsystemprofile.
SLESsetupfromUSBcannotaccessinstallationmediaSymptomsAproblemoccurswhendeployingtheSLESsetupprofilefromUSB.
IfyoucreateaSLES11x64setupprofilewithadditionalpackageselection(duringthesetupcreationwizard)anddeploytheprofilefromUSBdrive(offline),thedeploymentstopstwiceandrequiresuserinteractiontoproceed.
Then,ifyouskipthemissingpackages,thedeploymentcompletessuccessfully.
ResolvingtheproblemAsaworkaroundcreateanddeployaSLES11x64setupprofilewithoutanyadditionalpackageandaddanyrequiredsoftwarewithTivoliProvisioningManagerforOSDeploymentsoftwaremodules.
UserinteractionrequiredwhendeployingSLES10onPowerPCDependingonyournetworkenvironment,deployingSuSELinuxEnterpriseServer10onPowerPCmightrequireuserinteraction.
SymptomsWhendeployingaSuSELinuxEnterpriseServer10systemprofileonaPowerPCtarget,thedeploymentmightstopwithabluescreenandthefollowingmessage:CannotaccessinstallationmediaSuSELinuxEnterpriseServerSP2.
CheckthattheserverisaccessibleEnvironmentThisisanenvironmentalissue.
Insomecases,thenetworkswitchdoesnotreestablishthelinkwiththenetworkcardinatimelyfashionandatimeoutoccurs.
ResolvingtheproblemForanimmediatesolution,selectOKorRetry.
Foralongtermsolution,configureyourswitchesormodifyyournetworkinfrastructuretoavoidlongdelayswhenswitchesmustreestablishlinkstonetworkcards.
Troubleshootingandsupport25PowerPCdoesnotrebootonharddiskattheendofadeploymentSymptomsAtthefinalrebootofaPowerPCdeployment,thetargetsometimesrebootseitherintheSMSmenuorintheOpenFirmwarepromptinsteadofontheharddisk.
CausesTheoriginoftheproblemseemstoresideintheversionofthefirmwareandintheoperatingsystemwhichwaspreviouslydeployedonthetarget.
ResolvingtheproblemvIfthetargetbootsintotheSMSmenuattheendofthedeployment:1.
SelectBootoptions2.
SelectBootdevice3.
SelectHarddriveandyourtargetwillbootontheharddiskdrive.
vIfthetargetbootsintotheOpenFirmwarepromptattheendofthedeployment,runbootdiskandyourtargetwillbootontheharddiskdrive.
IncompletelogsforSolarisunattendedsetupsystemprofilesOnSolaris,someofthelogginginformationappearsonthetargetratherthaninthelogfilesoftheOSdeploymentserver.
SymptomsWhencreatingaSolarisunattendedsetupsystemprofileordeployingit,theactivitylogsseemincomplete.
CausesThislogginginformationcannotbebothcapturedforinclusioninthelogfilesoftheOSdeploymentserveranddisplayedonthetarget.
Adesignchoicewasmadetodisplaytheinformationaboutthetarget.
MissingRPMfilesThereisnoverificationofRPMdependencieswhenRPMpackagesareaddedthroughautoyast.
xml.
SymptomsWhendeployingaLinuxsystemprofileinwhichyouhaveaddedyourownRPMpackagesthroughautoyast.
xml,yougetanerrorindicatingthatsomeRPMfilesaremissing.
CausesTheproductdoesnotresolveRPMdependenciesandyouhavenotincludedallthenecessaryRPMpackagesinyoursystemprofile.
ResolvingtheproblemTherearetwooptionstosolvethisproblem.
Youneedtoperformonlyone.
vEditthecontentofLinuxinstallationmediatobuildacustomLinuxdistribution.
vAfteryouhavecreatedyousystemprofile,edititandaddthemissingRPMpackages.
1.
GotoServer>OSdeployment>SystemProfiles.
26TivoliProvisioningManagerforOSDeployment:Troubleshootingandsupportguide2.
Double-clickonasystemprofiletoopentheProfiledetailspage.
3.
Double-clickonanOSconfigurationtoopentheOSconfigurationdetailspage.
4.
SelectDiskstoviewthepartitionlayout.
5.
ClickBrowseimageofprimarypartitiontoobtainaccesstothefiles.
6.
Inthecontextualmenu,selectUploadfileandindicatethefilelocation.
Note:Fileuploadislimitedto16MB.
7.
Repeatstep4foreachRPMpackageyouwanttoadd.
LinuxdeploymentdoesnotendonaBladeWhiledeployingaLinuxsystemprofileonaBlade,Linuxdeploymentengineloadinggoesonindefinitelywhenthetargetisnotconnectedtoaremoteconsole.
SymptomsvYouaredeployingaLinuxsystemprofileonaBlade.
vThetargetisnotconnectedtoaremoteconsole.
vThedeploymentdoesnotprogressanymorewhenLinuxdeploymentengineisbeingloaded.
Thedeploymentissuccessfulwhenaremoteconsoleisconnectedtothetarget.
Resolvingtheproblem1.
GotoServer>OSdeployment>TargetMonitor.
Double-clickonatargettoviewitsdetails.
2.
ScrolltotheBootSettingssectionandclickEdit.
3.
SelectDisableUSBandclickSave.
4.
Startyourdeploymentagain.
ThekeyboardlayoutcannotbechangedduringofflinedeploymentYouaredeployingaLinuxoperatingsystemfromadeploymentmediaandyoucannotchangethekeyboardlayouttoentertargetvalues.
SymptomsYouaredeployingaLinuxoperatingsystemfromadeploymentmedia.
YourtargethasbootedintoLinuxdeploymentengineandyouarerequiredtoentersometargetinformation.
Thekeysyoupressonthetargetkeyboarddonotcorrespondtowhatisshownonthedisplay,becauseofadifferentkeyboardlayout.
Yourattempttochangethekeyboardlayoutfails.
ResolvingtheproblemDuetoLinuxdeploymentenginelimitations,youcannotchangethekeyboardlayoutonthetargetwhileyouaredeployingaLinuxoperatingsystemfromadeploymentmedia.
UsetheUSEnglishkeyboardlayouttoentertherequiredvalues.
DeploymentofaSLESsystemprofilewithmorethantwologicalpartitionsfailsYourdeploymentofaSLES10SP2oraSLES11systemprofilewithmorethantwologicalpartitionsfails.
SymptomsTroubleshootingandsupport27YourSLES10SP2orSLES11systemprofilecontainsmorethantwologicalpartitions.
Whileyouaredeployingyoursystemprofile,youencounteroneoftheseissues:vThedeploymentstallsduringpartitioncreationvTheYaSTinstallerstopswiththemessageErrorduringconfigurationofthepartition.
PlstryagainCausesThecauseislocatedintheYaSTinstallerwhichcannothandlemorethantwologicalpartitionsfromthepartitionlayoutinformationgeneratedbytheOSdeploymentserver.
ResolvingtheproblemForSLES11,afixprovidedbyNOVELLwasvalidated.
YoushouldrequestfromyourSLESvendoradriverupdate.
ThereferenceisBugzilla#620212(SUSE11).
ForSLES10SP2,thereisnoworkaroundbecauseNOVELLdoesnotprovidefixesforthisversionanymore.
AccessingtargetdevicesduringdeploymentSymptomsDuringdeploymentonanIBMsystemx3350thefollowingmessageisdisplayed:Pleaseinsertdiskintodrive.
ResolvingtheproblemVerifythatallyourdevicescanbeaccessed.
SLESdeploymentfailsonHPworkstationsOnHPworkstations,SLESdeploymenthangswhenstartingtheLinuxinstaller.
SymptomsYouaretryingtodeployaSLESsystemprofileonanHPBladeHPBL460cG6orHPDL580G7.
ThedeploymentfailswhenstartingtheLinuxinstaller.
ResolvingtheproblemToworkaroundthisissue,youcanenablethekernel-freemodeonthetarget.
Formoredetailsaboutthekernel-freemode,seeTypesofPXEnetworkboot.
Note:Ifyouworkwithamultipleserverarchitecture,youmustbeawarethatthe\TPMfOSFiles\tftpfolderisnotreplicatedfromparenttochildservers.
Therefore,ifataskistriggeredontheparentserverbutthetargetbootsonthechild,youmustuseanexternalreplicationmechanismtoensurethattheparentandchildversionsofthisfolderaresynchronized.
LinuxunattendedsetupdeploymentfailsWhiletryingtodeployaLinuxunattendedsystemprofile,whenstartingtheLinuxkernel,thetargethangs.
Ablackscreenissometimesdisplayed.
SymptomsThetargethangsinthemiddleoftheLinuxdeploymentengine-basedunattendedsetupdeployment,whentryingtostarttheLinuxkernel.
Itmayshowablackscreen.
Note:HTTPdeploymentisdisabled.
28TivoliProvisioningManagerforOSDeployment:TroubleshootingandsupportguideCausesSomelowlevelhardwareincompatibilitiesonrecentBIOSesmaycausethepre-bootenginetohangwhenloadingtheLinuxkernelduringanunattendedsetupLinuxdeployments.
ResolvingtheproblemToworkaroundthisissue,youcanrelyontheSyslinuxnativeLinuxloader:1.
DownloadtheSyslinuxopensourcetoolavailableontheweb.
2.
OntheOSdeploymentserverusedtocreatethenetworkbootmedia,andontheOSdeploymentserverusedfordeployment,youneedtocopysomeSyslinuxfilesintothe/global/updatesfolder,forexampleC:\TPMfOSFiles\global\updatesonaWindowsoperatingsystem.
a.
FromSyslinux3.
63,copythefilesextlinuxfromtheextlinuxfolder,andmbr.
binfromthembrfolder,into\global\updates\extlinuxontheserver.
b.
FromSyslinux4.
02orabove,copythefilesisolinux.
binfromthecorefolder,andlua.
c32fromthecom32/lua/srcfolder,into\global\updates\isolinuxontheserver.
3.
RestartyourOSdeploymentservers.
4.
Createanewdeploymentscheme,oruseadeploymentscheme,whereDownloadfileswithanetworkshareorLinuxHTTPwhenapplicableissettoNo.
5.
GenerateanetworkbootCD.
a.
GotoServer>OSdeployment>Deploymentschemes.
b.
ClickGenerateMedia.
c.
SelectGenerateanetworkbootCD/DVDIsolinuxbasedandclickNext.
Note:Thisoptionisavailableonlywhentheappropriatecontenthasbeencopiedinto/global/updates.
d.
FollowtheremaininginstructionsofthewizardtogenerateyourISOnetworkbootCD/DVD.
6.
Onthetarget,bootfromtheCD/DVD.
7.
Attheisolinuxprompt,typeLinuxDEtostartLinuxdeploymentenginefromthenetworkbootCD/DVD.
8.
Whenthegreenbannerisdisplayed,tobootfromtheharddriveonwhichLinuxhasbeeninstalled,clickRebootonthetarget.
ErrorduringLinux64-bitdeploymentormigrationwhenrunningmkinitrdWhendeployingormigratingaLinux64-bitoperatingsystem,youmayencounteranerrorwhenrunningthemkinitrdscript.
Thiserrorsometimesresultsinafaileddeploymentormigration.
SymptomsYouaredeployingaLinux64-bitoperatingsystem.
Youseethefollowingerrormessageinthelogs,althoughthedeploymentcontinues:mkinitrdfailed,youmayexperienceproblemduringdeployment!
CausesTroubleshootingandsupport29Linuxdeploymentenginehadgenerateda32-bitmkinitrd,thatsometimescausesproblemsfor64-bitdeploymentandmigration.
UEFItargetsfailtoPXEbootonVMWarevirtualmachineswithLinuxoperatingsystemVMWarevirtualmachineswithLinuxguestoperatingsystemneede1000NetworkCardInterface(NIC)forUEFItoPXEboot.
SymptomsWhentheproductserverisrunningonaVMWarevirtualmachinewithLinuxguestoperatingsystem,theUEFItargetsfailstoPXEboot.
ResolvingtheproblemMakesuretheNetworkCardInterface(NIC)typeontheproductserverise1000.
ProblemsprovisioningVMWareESXoperatingsystemsDeployingVMWareESX/LinuxfailsSymptomsWhenyoudeployLinuxorVMWareESXoperatingsystems,thedeploymentmightfailandthefollowingerroroccurs:UnabletobootLinuxwiththerequestedparametersbecausetheLinuxkernelorinitialramdiskcannotbefound.
CausesThedefaultdevicemappingisnotworking.
ResolvingtheproblemTosolvethisissue,manuallyinstallLinuxorVMWareESXusingtheCD/DVDontheworkstationtoidentifythedevicesusedandtousethecorrectdevicenameintheprofile.
HS20hangswhenVMWareESX3.
5isbeingdeployedYoucannotdeployaVMWareESX3.
5onanHS20targetwithoutinteraction.
SymptomsYouaredeployingaVMWareESX3.
5systemprofileonanHS20target.
Thedeploymenthangswhenarebootisneeded.
CausesThisissueisspecifictotheHS20whichcannotberebootedbytheESXinstaller.
ResolvingtheproblemIfyoureboottheHS20targetmanually,thedeploymentresumesandendssuccessfully.
ProblemsafteradeploymentBootingatargetwithtwodisksafterasuccessfuldeploymentfailsAfterasuccessfuldeployment,youcannotbootyourtargetwhichcontainstwoharddisks.
Symptoms30TivoliProvisioningManagerforOSDeployment:TroubleshootingandsupportguideYoursystemprofilecontainsonlyonedisk,butthetargetonwhichyouaredeployingitcontainstwodisks.
Thedeploymentissuccessful.
However,youarenotabletostarttheoperatingsystemonyourtarget.
CausesYouaretryingtobootononediskwhiletheoperatingsystemwasinstalledontheotherdisk.
ResolvingtheproblemYoucantrytochangethebootorderofthetargettoputtheseconddiskfirst.
BootonOSfailsafterasuccessfuldeploymentAfterasuccessfuldeploymentofasystemprofile,clickingBootonOSdoesnotstarttheoperatingsystemonthetarget.
SymptomsYouhavecreatedasystemprofile.
Youhaveperformedasuccessfuldeploymentofthissystemprofile.
Whenthegreenbannerisdisplayed,youclickonBootonOStostarttheoperatingsystem.
Thereisanerrorandtheoperatingsystemdoesnotstart.
ResolvingtheproblemAfterthesuccessfuldeployment,donotclickBootonOS.
ClickRebootinstead.
RAIDdeploymenttaskfailsSymptomsWhenyouperformaRAIDdeploymenttaskusingtheRAIDcommand,theconsoledisplaysthattheRAIDconfigurationcommandexitswithanerror.
ResolvingtheproblemIftheRAIDhardwareconfigurationfails,checktheactivity.
logand.
trcfilesfordetailederrormessagesandadvancedtroubleshooting.
Forexample,ifyoureceivethefollowingerrormessage:ERROR:(2829)CannotcreateArray,DiskSelectionError:Drive"1I:1:3"isnotvaliditmeansthatyouselectedawrongdiskinthehardwareconfiguration.
ProblemswhileredeployingaprofileonthesametargetDeployingonaWindowstargetwhilekeepingtheexistingpartitionSymptomsWhenyoutrytodeployagainjustonepartitionofasystemprofilethathasapartitionlayoutwithtwopartitions,forexample,CandD,usingsimpledeploymentbysettingonlytheoptionMustbedeployedtonoforthepartitionthatyoudonotwanttodeploy,forexample,deployagainCwhileleavingDuntouched,thedeploymentfailswiththefollowingerror:ImpossibletopartitiontheharddiskTroubleshootingandsupport31ResolvingtheproblemTosolvethisissue,followthesesteps:1.
Makesurethefollowingprerequisitesaremet:vInthepartitionlayout,100%ofthediskmustbeassigned.
Inthisexample,therearetwopartitions,oneoccupying85%ofthediskspaceandtheotheroccupying15%.
vThesecondpartitionmustnotbecompletelyfulltoallowtheshrinkingoperation.
2.
Createasoftwaremodulepre-OS(withastageequalto1,beforeusingtheharddisk)toshrinkthepartitionthatyoudonotwanttodeployagain.
Hereisasampleofascriptforthistypeofsoftwaremodule:REMprocessingdisk0partition2shrinkingselectdisk=0selectpartition=2shrinkDESIRED=2048MINIMUM=102432TivoliProvisioningManagerforOSDeployment:Troubleshootingandsupportguide3.
Beforeperformingtheseconddeployment,makesurethatyouhavechangedthemustbedeployedoptionofD:partitiontonoandthenselectthesoftwaremoduledefinedinthepreviousstep.
WhenpartitionsCandDareprimary,youhaveanalternativesolution:fromthefirstdeployment,thescenarioworksonlyifinthediskatleast1or2GBofunpartitionedspaceisleftonthedisk.
RedeployingpartitionDwiththeBitLockerfeatureenabledThistopicdescribeshowredeploypartitionDwhentheBitLockerfeatureisenabled.
Inthefirstpartofthisprocedure(steps1to3)youcreateasystemprofiletobeusedindeploymentsandredeployments.
Inthesecondpartoftheprocedure(steps4to5)youperformtheredeployment.
TheprerequisiteforthisprocedureistodecryptpartitionsCandD.
TocreateasystemprofiletobeusedfordeploymentandredeploymentwiththeBitLockerfeatureenabled,performthefollowingsteps:1.
DeployaWindows7Enterprisewithapartitionlayoutthathastwopartitions,forexampleCandD,whereDisnotprimary,andtheoptionMustbedeployedissettoyesforbothCandD,asshowninthefollowingfigure:Figure2.
SoftwareModuleDetailsTroubleshootingandsupport332.
Aftersuccessfuldeployment,loginintoWindowsandfollowtheproceduretoenabletheBitLockerfeature.
Formoreinformation,seehttp://www.
howtogeek.
com/howto/6229/how-to-use-bitlocker-on-drives-without-tpm/.
TheBitLockersetupisdividedintotwoparts:a.
PrepareyourdriveforBitLockerb.
EncryptthedriveToprepareyourdrive,asystemandhiddenpartitionof300MBiscreatedbetweenCandD.
Thispartitionisleftdecryptedandisusedtobootthetarget.
Afterthereboot,youcanencryptbothpartitionsCandD.
Atthisstage,skiptheencryptionpart.
Toproceedwithnextsteps,bothCandDpartitionsmustbedecrypted.
3.
Createanewsystemprofilebycloningthetarget.
Launchthecommandsysprepbeforecreatingtheprofile.
Aftercloning,youseethepartitionlayoutoftheclonedprofileasshowninthefollowingfigure:ThehiddenpartitionisnowpresentbetweenCandD.
Usethiscloneforadeploymentofanewtarget,asthebaseimage,orforaredeploymentonatargetpreviouslyinstalledwiththesameimage,savingpartitionD.
34TivoliProvisioningManagerforOSDeployment:Troubleshootingandsupportguide4.
CreatesomefilesonpartitionD,toverifythataftertheredeploymenttheystillexistonthepartition.
5.
DecryptbothpartitionsCandD(iftheywereencrypted).
6.
ModifytheclonedprofilebychangingthesettingoftheoptionMustbedeployedofthepartitionDtono.
7.
Createapre-OSsoftwaremodule(withastageequalto1,beforeusingthepartition)toshrinkthepartitionthatyoudonotwanttodeployagain.
Thisisascriptsampleforthistypeofsoftwaremodule:REMprocessingdisk0partition3shrinkingselectdisk=0selectpartition=3shrinkDESIRED=2048MINIMUM=10248.
Makesurethatyouselectthesoftwaremodulespecifiedinstep7,beforeperformingtheseconddeployment.
ThisseconddeploymentreinstallspartitionCinthesamestatewhenitwascloned,andleavesuntouchedpartitionD.
ProblemswithamultiserverarchitectureErrorsinthevm.
trclogwhenreplicatingwithflaghinAutoSyncTherecanbeerrormessageswhenreplicatingforthefirsttimeaserverwiththeflaghinAutoSync.
SymptomsvYouareworkinginamultiservermultipledatabaseenvironment.
vYouuseaconfig.
csvfiletoreplicateyourservers.
Troubleshootingandsupport35vYouhavesetflaghinAutoSync.
vErrormessagesappearinvm.
trclog.
vTheerrormessagesalloccurinsideRADRefreshHosts.
Example:[2009/11/1820:12:08]ErrorraisedbyRADGetMasterBomIdsinconsole.
rbc,line2047[VM:3250][2009/11/1820:12:08]Notanarray[2009/11/1820:12:08](calledfromRADRefreshHosts(console.
rbc:2837))[2009/11/1820:12:08](calledfromRADKeepAlive(console.
rbc:3797))[2009/11/1820:12:08](calledfromRADInstaller(console.
rbc:8188))[2009/11/1820:12:08](calledfromRunPackageInstallers(server.
rbc:19980))[2009/11/1820:12:08](calledfrom--toplevel--(server.
rbc:21505))[2009/11/1820:12:09]ErrorraisedbyRADRefreshHostsinconsole.
rbc,line2863[VM:3250][2009/11/1820:12:09]Notanarray[2009/11/1820:12:09](calledfromRADKeepAlive(console.
rbc:3797))[2009/11/1820:12:09](calledfromRADInstaller(console.
rbc:8188))[2009/11/1820:12:09](calledfromRunPackageInstallers(server.
rbc:19980))[2009/11/1820:12:09](calledfrom--toplevel--(server.
rbc:21505))[2009/11/1820:12:14]Faultyquery(dbdb.
rbc:2049):INSERTINTO"BOMUpd"("DeplCount","Description","SN","UUID","MAC","Model","Platform","LogicalName","HostName","EnableIPv6","IPSettings","IP","MgntIF","NetMask","Gateway","DNSServer1","DNSServer2","DNSServer3","DNSDomain","DNSOrder","WINSServer1","WINSServer2","BitsPerPel","Xresolution","Yresolution","Vrefresh","IdentScope","ScopeName","OrgUnit","JoinDomUser","JoinDomPass","ProductKey","AdministratorName","NameService","NameServer","LDAPProfile","KerberosRealm","KAdminServer","KDCServer1","KDCServer2","KDCServer3","TimeServer","TermInfo","SystemID","DeplSet","GroupID","DeployGroupID","UserID","EnsembleID","Status","StatusDate","IdentDate","MonitorLocation","MonitorLayout","RemboServer","RemboOptions","RemboLockout","PXEBootMode","RedirectSrv","RedirectSrvAlt","MgnParam","SrvHostID","Hypervisor","InstanceID")VALUES(0,NULL,'40160191D8B460',NULL,'00:14:5E:54:9E:F2',NULL,NULL,NULL,NULL,'0',NULL,'9.
167.
62.
167',NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,'Srv5E549EF2-0',0,NULL,'3174709/1206:38:34','3174709/1206:38:34','Default',NULL,'9.
167.
62.
167',0,0,0,NULL,NULL,NULL,0,0,NULL)[2009/11/1820:12:15]ErrorraisedbyDbRbcExecindbdb.
rbc,line4174[:0][2009/11/1820:12:15]Unknownerror(ProbleminaSQLquery,checklogsfordetails[USRMSG]ERROR1(22007):DB2SQLError:SQLCODE=-180,SQLSTATE=22007,SQLERRMC=null,DRIVER=3.
53.
70[dbdb.
rbc:2049][I18NMSG]ProbleminaSQLquery,checklogsfordetails)[2009/11/1820:12:15](calledfromDbCreateRecord(dbdb.
rbc:2090))[2009/11/1820:12:15](calledfromRADForwardEvents(console.
rbc:2361))[2009/11/1820:12:15](calledfromRADRefreshHosts(console.
rbc:3136))[2009/11/1820:12:15](calledfromRADKeepAlive(console.
rbc:3797))[2009/11/1820:12:15](calledfromRADInstaller(console.
rbc:8188))[2009/11/1820:12:15](calledfromRunPackageInstallers(server.
rbc:19980))[2009/11/1820:12:15](calledfrom--toplevel--(server.
rbc:21505))ResolvingtheproblemTheseerrormessagesdonotcompromiseserverfunctionalityandcanbeignored.
Errorsinthefile.
trclogwhenreplicatingSymptomsWhenperformingareplicationthroughsync.
pak,afailureoccursandthefollowingerrormessageiswritteninfile.
trc:InsufficientsystemresourcesexistResolvingtheproblemTosolvethisissue,applytothechildservertheproceduresdescribedinthefollowingMicrosofttechnote:36TivoliProvisioningManagerforOSDeployment:Troubleshootingandsupportguidehttp://support.
microsoft.
com/kb/312362ErrorsintheNBPlogafterswitchingparentandchildserverrolesReversingtherolesofaparentandachildserverinasingledatabasearchitecturecreateserrorsintheNBPlog.
SymptomsYouhavereversedtherolesofaparentserverandachildserverinamultiserversingledatabasearchitecture,usingthelinksprovidedinthewebinterface.
ThereareerrorsintheNBPlogsofboththenewparentserverandthenewchildserverafterthisprocess.
Theerroronthenewparentserverissimilarto[9.
167.
62.
244]Nosessionfoundwithidentifier1.
Resettingconnection.
Theerrorsinthenewchildserveraresimilarto[TCPWRITE.
9.
167.
62.
246.
69bc]Nomatchingconnection[9.
167.
62.
246]ErrorduringTCPWRITE(69bc)[TCPCLOSE.
9.
167.
62.
246.
69bc]Nomatchingconnection[9.
167.
62.
246]ErrorduringTCPCLOSE(69bc)ResolvingtheproblemYoucansafelyignoretheseerrorsintheNBPlogs.
Errorsinthevm.
trclogwhenchangingserverrolefromstandalonetochildErrormessagescanbeloggedtothetracefilewhenrestartingtheserverafteraserverhaschangedrolefromstandalonetochild.
SymptomsvYouareworkinginamultiservermultipledatabaseenvironment.
vYouuseaconfig.
csvfiletochangetheroleofaserverfromstandalonetochild.
vYoucopytheconfig.
csvfiletotheRADdirectory.
vYourestarttheserver.
vUnexpectederrormessagesappearinvm.
trclog.
Sampleerrormessage:[2010/02/1915:30:20]ErrorraisedbyDbRbcExecindbdb.
rbc,line4178[:0][2010/02/1915:30:20]Unknownerror(ProbleminaSQLquery,checklogsfordetails[USRMSG]ERROR1(22007):DB2SQLError:SQLCODE=-180,SQLSTATE=22007,SQLERRMC=null,DRIVER=3.
53.
70[dbdb.
rbc:2051][I18NMSG]ProbleminaSQLquery,checklogsfordetails)[2010/02/1915:30:20](calledfromDbCreateRecord(dbdb.
rbc:2092))[2010/02/1915:30:20](calledfromRADForwardEvents(console.
rbc:2426))[2010/02/1915:30:20](calledfromRADRefreshHosts(console.
rbc:3201))[2010/02/1915:30:20](calledfromRADKeepAlive(console.
rbc:3862))[2010/02/1915:30:20](calledfromRADInstaller(console.
rbc:8542))[2010/02/1915:30:20](calledfromRunPackageInstallers(server.
rbc:19999))[2010/02/1915:30:20](calledfrom--toplevel--(server.
rbc:21524))ResolvingtheproblemTheseerrormessagesdonotcompromiseserverfunctionalityandcanbeignored.
Troubleshootingandsupport37Problemswithbooting,network,andfiletransfersUnknownMACaddressduringbootonPXESymptomsWhenyoubootanHyper-VtargetwithtwoNICconfigured,forthesecondaryNICtheMACaddressissetto"UnknownNIC".
CausesWhenbootingonPXEatargetandcheckingitsnetworkcard,onlythenetworkcardusedtobootonPXEwilldisplaytheMACaddress.
ResolvingtheproblemThereisnocurrentworkaroundtosolvethisissue.
HangonsplashscreenSymptomsTheOSdeploymentservermightbehangingonsplashscreenwhenbootingonatarget.
ResolvingtheproblemThisissuecanbeduetoamissingdefaultgatewayinformationamongtheoptionstobesetfortheDHCPserver(option3).
AlsoverifythatanyfirewalldoesnotblockthetraffictotheOSdeploymentserver,UDPport4012.
PXEbootromnotdetectedSymptomsDuringthebootprocess,thereisnomessageaboutthePXEbootrom,andthecomputerbootsnormally(onthefloppy,harddiskorCD).
ResolvingtheproblemCheckthatyournetworkcardiscorrectlyinstalled,andthataPXEbootromisinstalledonthenetworkcard.
Toverifythatthenetworkworks,runWindowsorLinux,andconfiguretheoperatingsystemsothatyouareabletopingothercomputers(oryouareabletoseeothercomputersinthenetworkneighborhood).
Oncertainnetworkcards,thePXEbootromisnotbeactivatedbydefault.
ReadtheproductdocumentationtofindthekeycombinationtopresstoenterthePXEsetupmenuatboottime.
OnIntelEPRO100,thekeycombinationisCtrl-S,orShift-Shift(pressbothShiftkeys).
Thesekeysmustbepressedduringthebootprocess,whenthecomputerispoweredon.
Somecardsdonothaveaconfigurationmenu.
EnteryourBIOSsetupduringboottime(DEL,orF2keyonmostsystems),andconfiguretheBIOSbootprocesssothatthenetworkcardisthefirstentryinthebootlist.
InsomeBIOS,thereisanoptiontoenablebootonnetwork.
OnotherBIOS,youmustmanuallysettheLAN(alsocalledNET,orOther)asthefirstdeviceofthebootorder.
Ifallofthesestepsfail,trytoobtainaflashmemoryupgradefromyournetworkcardvendor,andflashthenetworkcardromwiththenewestupgrade.
Iftheflashprocessfails,thereisachancethatnobootromisinstalledonyournetworkcard.
IfyouarestillnotseeingthePXEmessages,askforsupportfromyournetworkcardmanufacturer.
Alternatively,youcancreateanetworkbootmediatoenableyourtargettoconnecttoyourOSdeploymentserver.
38TivoliProvisioningManagerforOSDeployment:TroubleshootingandsupportguideThebootromdisplaysDHCP.
.
.
andtimesoutSymptomsThefollowingmessageisdisplayed:Thebootromdoesnotreceiveenoughinformationtoproceedfurther.
EithertheDHCPserverortheOSdeploymentserverisnotcorrectlyconfigured.
ResolvingtheproblemCheckthatyourDHCPserveriscorrectlyconfiguredasexplainedinDHCPserverOSconfiguration.
Inparticular,checkthatoption60issettoPXEClientifyouarerunningtheDHCPserverandthePXEserveronthesametargetonly.
IftheDHCPserverandtheOSdeploymentserverareonthesametarget,trytostopbothservers,andrestartthetwoserversinthefollowingorder:DHCPserverfirst,thentheOSdeploymentserver.
IftheOSdeploymentserverisstartedfirst,itmightreservetheDHCPport,thuspreventingtheDHCPservertostart.
CheckyourDHCPconfiguration:runWindowsorLinuxonyourremote-boottarget,andconfigurethenetworktousedynamicconfigurationinsteadoffixedIPaddress.
Ifthisworks(runwinipcfgoripconfigonaWindowscomputer,ifconfigonaLinuxcomputer),thentheDHCPserveriscorrectlyconfiguredforthistarget.
Otherwise,checkyourDHCPserverOSconfiguration,sothattheremote-boottargetisassignedanIPaddress,anetmaskandadefaultgateway.
Ifyourserveriscorrectlyconfigured(includingoption60),andthetargetstilldisplaysDHCP.
.
.
followedbyanerror,checkyourOSdeploymentserverOSconfiguration.
StoptheOSdeploymentserver,thenrunrembo.
exe-d-v6,andstarttheremote-boottarget.
Whenstarting,theserverdisplaysalinesayingwhetheritisactingasaDHCPProxyoraBINLProxy.
IftheDHCPserverandtheOSdeploymentserverareonthesametarget,theOSdeploymentserveractsasaBINLproxy.
Iftheyareondifferenthosts,theserveractsasaDHCPproxy.
IftheserverdisplaysamessagesayingitactsasaBINLproxy,butthetwoserversarenotonthesametarget,itmeansthatthereisaDHCPserverinstalledonthecomputerwhereyouhaveinstalledTivoliProvisioningManagerforOSDeployment.
Whenatargetstarts,andDHCPiscorrectlyconfigured,theOSdeploymentserver(indebugmode)displaysValiddiscoveryfrom.
.
.
followedbytarget.
.
.
foundingroup.
.
.
.
Iftheserverdisplaysthefirstline,butdisplaystarget.
.
.
notfoundinanygroupinsteadofthesecondline,itmeansthatyourconfigurationfiledoesnotcontainadefaultgroup,andthattheremote-boottargetisnotdeclaredinanygroup(thetargetmustbedeclaredwithitshardwareaddress,notitsIPaddress).
IftheserverdoesnotdisplaythemessageValiddiscoveryrequestfrom.
.
.
,thenoption60ontheDHCPserverisnotcorrectlyset,ortheOSdeploymentserverandtheDHCPserverarenotonthesamesubnet.
IfyouhaveinstalledTivoliProvisioningManagerforOSDeploymentonamulti-homedtarget(acomputerwithmorethanonenetworkcard,orwithadialupadapter),usetheInterfacesoptiontospecifywhichnetworkinterfacetouse.
Ifitstilldoesnotwork,sendareporttoyourIBMSoftwareSupportrepresentativewiththefollowinginformation:vAllthefilesfromthelogsdirectoryoftheOSdeploymentservervTheOSconfigurationinformationforyourDHCPservervTheOSconfigurationinformationforyourOSdeploymentserverTroubleshootingandsupport39vAmemorydumpofthenetworktrafficbetweentheserversandtheremote-boottarget(usetheMSNetworkMonitoronWindowsNT/2000)ThebootromdisplaysMTFTP.
.
.
,andanerrormessageSymptomsThefollowingerrormessageisdisplayed:ThebootromwasunabletoreceivetheTivoliProvisioningManagerforOSDeploymentbootstrapfromtheserver.
ResolvingtheproblemIfthedelaybetweentheMTFTP.
.
messageandtheerrormessageisshort,andthemessageexplainsthatafilewasnotfound,thenthetargetyouhaveinstalledTivoliProvisioningManagerforOSDeploymentonalreadyrunsaTFTPserver(andthisTFTPserveranswersrequestfortheOSdeploymentserver).
IfyouareusingWindows2000/2008/XP/Vistaontheserver,checkthelistofservices,anddisableservicesrelatedtoTFTPorBootprotocols(includingIntelLCMandMicrosoftPXE,).
IfthedelaybetweentheMTFTP.
.
messageandtheerrormessageislong,themulticastTFTPdatagramssentbytheprovisioningserverarenotbeingreceivedbytheremote-boottarget.
IfyouhaveinstalledTivoliProvisioningManagerforOSDeploymentonamulti-homedcomputer,usetheInterfacesparametertospecifywhichnetworkinterfacetouseformulticastpackets.
Ifitstilldoesnotwork,sendareporttoyourIBMSoftwareSupportrepresentativewiththefollowinginformation:vAllthefilesfromthelogsdirectoryoftheprovisioningservervTheOSconfigurationinformationforyourDHCPservervTheOSconfigurationinformationforyourOSdeploymentservervAmemorydumpofthenetworktrafficbetweentheserversandtheremote-boottarget(usetheMSNetworkMonitoronWindows2000/2008/XP/Vista)OccasionalMTFTPtimeout(onmultihomedserver)SymptomsWhenaservernetworkconnectionislostandthenrecovered,thetargetsreportanMTFTPtimeoutafterreceivingtheirDHCPlease.
ResolvingtheproblemThisisbecauseWindows2000automaticallyclosesallsocketswhenanetworkconnectionislost.
Aworkaroundistorestarttheprovisioningserverafterthenetworkisupagain.
Along-termfixistodisabletheWindows2000mediasensingonthenetworkcard,ontheserver.
MoreinformationaboutthistopiccanbefoundinMicrosoftknowledgebase,underthetitleHowtoDisableMediaSenseforTCP/IPinWindows2000.
SubnetnotallowingmulticastInsomecases,asubnetincorrectlyrefusesmulticastconnections.
SymptomsWhileyouhaveselectedmutlicast,packetsaresentinunicastinagivensubnet.
Causes40TivoliProvisioningManagerforOSDeployment:TroubleshootingandsupportguideItispossiblethatthefirstmulticastprobesentbytheOSdeploymentserverfailedandthataredetectionisneededfortheOSdeploymentservertoascertainthatmulticastispossibleonthissubnet.
ResolvingtheproblemIfyoubelievethatyoursubnetshouldbeabletousemulticast,youcantrytoredetectthesubnetsettings.
1.
GotoServer>OSdeployment>TargetMonitor.
2.
Selecttheproblematicsubnet.
3.
ClickForceredetectionofsubnetsettingsThemulticastoptionisnotrespectedduringdeploymentWhiledeployingasystemprofilewithamulticastoptioninthedeploymentscheme,thedeploymentisperformedusingunicast.
SymptomsWhiletryingtodeployasystemprofilewithadeploymentschemewhichrequesttheuseofmulticastfiletransfer,thedeploymentsucceedsbutunicastwasusedinsteadofmulticast.
ResolvingtheproblemMulticastisavailableonlyifallthecriteriawhichfollowarerespected.
vthetargetshaveanIntelx86orx86-64architecturevmulticastisselectedinthedeploymentschemevthesubnetsupportsmulticasttrafficvmulticastisnotdisabledinthebootoptionsofthetargetvthetargetisnotaVMWare3.
xguest.
Makesureallthecriteriaaremetbeforetryingtousemulticast.
DeploymentfailsonsomeBroadcomnetworkadaptersOnsomeBroadcomnetworkadapters,afirmwaredefectpreventssuccessfuldeploymentorredeployment.
SymptomsDeploymentorredeploymentfailsduringnetworktransfersonsometargetswitheitheroneofthefollowingBroadcomchips:vBCM5700vBCM5701vBCM5702vBCM5703vBCM5704TheseBroadcomchipscanbepotentiallyincludedinthefollowingIBMservers,amongotherIBMandnon-IBMservers:vHS20vLS20vx335vx355vx3655CausesTroubleshootingandsupport41ThisisafirmwaredefectwhichcannotbefixedinTivoliProvisioningManagerforOSDeployment.
DiagnosingtheproblemOnthetarget,youseeamessagestartingwithBROKENFIRMWAREDETECTEDFORYOURNETWORKADAPTER.
ResolvingtheproblemThisissuecanonlybefixedbyanupdateofyourfirmwarewiththecorrectPXElevel.
Table1indicateswhichPXElevelmustbeupdatedandtheminimalPXEleveltobereached.
Table1.
PXElevelsProblematicPXElevelCorrectPXElevel9.
0.
x9.
0.
13orabove10.
0.
x10.
4.
10orabove10.
4.
x10.
4.
10orabove11.
0.
x11.
4.
0oraboveContactyourhardwaresupporttoobtainanewfirmwareversionwiththerequiredPXElevel.
ThedeploymentdoesnotstartonatargetwithmultiplenetworkinterfacecardsYouhavemanuallyregisteredatargetwithmultiplenetworkcards,providingtheMACaddresstoregister.
Younowwanttodeploythetarget,butthedeploymentneverstarts.
SymptomsvYouhaveatargetwithmorethanonenetworkinterfacecard.
EachcardhasitsownMACaddress,forexample,AA:AA:AA:AA:AA:AAandBB:BB:BB:BB:BB:BB.
vYourOSdeploymentserverworksinclosedmode.
vYouhaveregisteredyourtargetusingthefirstMACaddress,forexampleAA:AA:AA:AA:AA:AA.
vOnthewebinterface,youselectthetargetandselectDeploynowtostartadeployment.
vThedeploymentdoesnotstartonthetargetwithMACaddressAA:AA:AA:AA:AA:AA.
vHowever,aseparateentryisaddedintheTargetMonitor,withtheIPaddresscorrespondingtothesecondMACaddress(BB:BB:BB:BB:BB:BB).
YounowhavetwoentriesforthesametargetintheTargetMonitor.
CausesTheMACaddressyouusedtoregisterthetarget(AA.
AA:AA:AA:AA:AA)isnottheonefromwhichthetargetbootsbydefault.
ResolvingtheproblemTherearetwooptionstosolvethisissue:vUsetheUUID,serialnumber,orIPaddresstomanuallyregisteryourtarget.
vIfyoumustusetheMACaddresstoregisteryourtarget,makesurethattheMACaddressthatyouprovideistheonethetargetbootsfrombydefault.
42TivoliProvisioningManagerforOSDeployment:TroubleshootingandsupportguideProblemswiththedatabaseandthedatabasegatewayODBCDataSourceAdministratorreportsanerrorwhenmanuallyremovingorconfiguringasystemDSNonWindows64-bitoperatingsystemsSymptomsWhenyouinstallTivoliProvisioningManagerforOSDeploymentwiththeinstalleronaWindows64-bitoperatingsystem,theinstallercreatesasystemDSNcalledAutoDeploywithaMicrosoftAccessDriver.
ThissystemDSNcannotberemovedorconfiguredusingtheODBCDataSourceAdministrator.
Whentryingtodoso,yougetthefollowingerrormessage:ThesetuproutinesfortheMicrosoftAccessDriver(*mdb)ODBCdrivercouldnotbefound.
Reinstallthedriver.
ResolvingtheproblemThesystemDSNisremovedautomaticallywhenyouuninstallTivoliProvisioningManagerforOSDeployment.
ToremoveorconfigurethesystemDSNmanually,youmustdosodirectlyintheregistrywiththeregistryeditor.
Toopentheregistryeditor:1.
Openacommandprompt2.
TyperegeditandpressEnter.
ThekeyandvaluetoremoveorconfigurearevThenameanddriverofthesource,locatedatMyComputer/HKEY_LOCAL_MACHINE/SOFTWARE/ODBC/ODBC.
INI/ODBCDataSources/ThereisanentrywithAutoDeployintheNamecolumnandMicrosoftAccessDriver(*.
mdb)intheDatacolumnvThesourceparameters,locatedatMyComputer/HKEY_LOCAL_MACHINE/SOFTWARE/ODBC/ODBC.
INI/AutoDeployDatabaseconnectivitywithApacheDerbyonaUNIXserverProblemdescriptionYoueitherwanttocheckyourdatabaseconnectivitybeforeinstallingyourprovisioningserveroryouencounterdatabaseconnectivityerrorsinthevm.
logfileofyourprovisioningserver.
YouworkwithApacheDerbyandaUNIXcomputer.
ProblemresolutionTochecktheconnectivityofyourprovisioningserverinstalledonUNIXwithanApacheDerbydatabase1.
dbgw.
jarisaJavaimplementationoftheTCP-to-ODBCgateway,usingJDBCinsteadofODBCfordatabaseaccess.
Youhavetwoalternativestostartthedatabasegateway.
va.
Startthedatabasegatewaybycopyingthederbyclient.
jarfileintothedirectorywheredbgw.
jarislocated.
Thedbgw.
jarfileispartoftheTivoliProvisioningManagerforOSdeploymentinstallationfiles,andshouldhavebeenextractedinto/usr/local/tpmfos.
b.
Runthefollowingcommand:java-cpdbgw.
jar:derbyclient.
jar\-Djdbc.
drivers=org.
apache.
derby.
jdbc.
ClientDrivercom.
rembo.
dbgw.
DbgwTroubleshootingandsupport43vAlternatively,ifyoudonotwanttocopythederbyclient.
jarfile,youcanstarttheJavadatabasegatewaywiththefollowingcommand:java-cpdbgw.
jar:$DERBY_HOME/lib/derbyclient.
jar\-Djdbc.
drivers=org.
apache.
derby.
jdbc.
ClientDrivercom.
rembo.
dbgw.
Dbgw-d2.
Inanotherterminal,verifythedatabaseconnectivityusing:telnetlocalhost2020usederby://127.
0.
0.
1:1527/tpmfosddb,root,3.
Stopthedbgwprocess.
Ifyoudonotstopit,youwillencountererrorswhenrunningthesetuporwhenrestartingyourprovisioningserver.
VerifyingdatabaseconnectivityProblemdescriptionIfyoususpectthereareconnectivityproblemsbetweentheOSdeploymentserverandthedatabase,performthefollowingcheckstoisolatetheproblem.
ProblemresolutionToverifytheconnectivityofthedatabasegateway,thedatabase,andtheOSdeploymentserver,performthefollowingchecks:1.
Verifythedatabasegateway.
Thedatabasegateway,usedbytheserver,runsaprocessnameddbgwonthecomputerrunningtheOSdeploymentserver.
StoptheOSdeploymentserverandattempttocontactthedatabasegatewayusingthefollowingtelnetcommand:telnetlocalhost2020Ifyousuccessfullyrunasessionthenthedatabasegatewayisfunctioningcorrectly.
Thefollowingbannerisdisplayed:-->"HELLO[127.
0.
0.
1]-RemboTCP-to-ODBCgateway/$Revision:#2$"Note:ThedbgwserviceisprovidedineachTPMserver,butintheintegratedenvironmentthechildserverinstalledbyTPMdoesnotusethisservice.
2.
Verifytheconnectionbetweenthedatabaseandthedatabasegateway.
Contactthedatabaseusingthecommand"use",wherethevalueofdependsonthewaytheserverhasbeenconfigured.
vOnWindows:thisstringcouldbethenamegiveninthe"ODBCadministrator".
vOnLinuxorWindows:thisstringcouldbewhatevertheDBneeds.
Forexample,submitthefollowingcommandforadefaultinstallationoftheOSdeploymentserverandDB2databasesoftwareonaLinuxmachine:usedb2://127.
0.
0.
1:50000/tpmfosd,db2inst1,Iftheconnectionissuccessful,thenyouareinaclassicalSQLevaluatorandthefollowingcommandsaretransmittedtothedatabase,evaluated,andtheresultsaredisplayedinthesamewindow:infoselect*fromBOMselect*fromServerswhereServerIdentWhentheconnectionstringisnot"AutoDeploy",youcanfindtheconnectionstringinthefollowingfile:net://global/rad/radb.
ini.
Usetheparametersinthe[Settings]sectiontosubmitthecommandasfollows:44TivoliProvisioningManagerforOSDeployment:Troubleshootingandsupportguideuse,,Ifyoucansuccessfullyverifybothofthesestepsthenthedatabaseisworkingproperly.
JavaexceptionthrownbydbgwprocessSymptomsOnz/Linuxplatforms,afteryouinstallTivoliProvisioningManagerforOSDeployment,thefollowingexceptionisthrownbythedbgwprocess:Exception:Communicationslinkfailureduetounderlyingexception:**BEGINNESTEDEXCEPTION**java.
io.
EOFExceptionSTACKTRACE:java.
io.
EOFExceptionatcom.
mysql.
jdbc.
MysqlIO.
readFully(MysqlIO.
java:1934)atcom.
mysql.
jdbc.
MysqlIO.
reuseAndReadPacket(MysqlIO.
java:2380)atcom.
mysql.
jdbc.
MysqlIO.
checkErrorPacket(MysqlIO.
java:2909)CausesTheproblemseemstobecausedbythedatabaseenginewhichtakeslongtimetostart.
ResolvingtheproblemTheproductrecoverycodeworksaroundtheissuewithoutanysideeffect.
ErrorinTargetMonitorpagewhenusingUserAuthenticationinODBCSymptomsAfteryouinstalltheMicrosoftSQLServerdatabase,ifyoustartODBCconfigusingUserAuthentication,youmighthaveanerroropeningtheTivoliProvisioningManagerforOSDeploymentinterface.
ResolvingtheproblemEnsurethatthecredentialsyouusetologontotheTivoliProvisioningManagerforOSDeploymentinterfaceandtoaccesstheOSdeploymentserverdatabasearethesameasthoseusedfortheSQLserverconnection.
KnownlimitationsapplicabletothecurrentreleaseoftheToolkitThefollowinglimitationsareapplicabletothecurrentreleaseoftheToolkit:vTherbagentprocessrunningofflineonoperatingsystemexitsifnopendingtaskisfoundandnobindingsforabindingmenuareavailable.
vIntheofflinemenuforkernel-freetargets,ifataskisselectedhavingoneactionwithprepare_nextaction=true,theactionisperformedbutnottrackedintothedatabase.
vAtargetremainsinidlestatewhilepollingtheserverforascheduledtask.
Thetargetrunsthetaskwhentheadministratorhasscheduledit.
vTargetUIcustomizationislimitedinrebranding.
Forexample,duetothenewarchitecture,whenatargetPXEbootsandtherearenopendingtask,theproductskinisshownandcannotbechangedfornow(customskinisnotavailableinkernelfreeandrembokernel).
Troubleshootingandsupport45vWhenthebaseflowcustomizationplug-inimplementsthetargetmachineredirection,ifthetargetdoesthePXEbootontheserverusingthekernelmode,itwillberedirectedonthesecondaryserverinthesamekernelmodeandtheservermustbeaccordinglyconfigured.
IfthetargetdoesthePXEbootinkernel-freemode,itwillbootineitherkernel-freeorkernelmodeonthesecondaryserverdependingonthecurrentserverconfiguration.
OnLinuxFAT32mustbecreatedwithahiddenparameterforToolkitofflineflowsProblemdescriptionOnLinux,ifthecachepartitionisusedtostoreRemboKernelasloader,thepartitionmustbeformattedusingthe-h(hidden-sectors)flag.
ProblemresolutionYoumustretrievetheoffsetforthecachepartitionbyusingthefollowingfdisk-ulcommand:pc-000C29C47389:#fdisk-ulDisk/dev/sda:21.
5GB,21474836480bytes255heads,63sectors/track,2610cylinders,total41943040sectorsUnits=sectorsof1*512=512bytesDiskidentifier:0x00051d14DeviceBootStartEndBlocksIDSystem/dev/sda120482080767103936082Linuxswap/SolarisPartition1doesnotendoncylinderboundary.
DeviceBootStartEndBlocksIDSystem/dev/sda22080768311295951609683LinuxPartition2doesnotendoncylinderboundary.
DeviceBootStartEndBlocksIDSystem/dev/sda33112960294195191315328083Linux/dev/sda4294195204187340762269445Extended/dev/sda529421568381747194376576bW95FAT32Assumingthat/dev/sda5isthepartitioncreatedtobethecache,thenitsStartsectoris29421568.
Thisvaluemustbegivenasinputasfollowspc-000C29C47389:#mkfs.
vfat-h29421568/dev/sda5Miscellaneousproblemsrbagentsync-srvradgetcommandfailsduetotimeoutSymptoms46TivoliProvisioningManagerforOSDeployment:TroubleshootingandsupportguidePerformingtherbagentsync-srvradgetcommand,anerrorsimilartothefollowingmightoccur:StoppingWebextensionCommanderror:Timeout,RPC:unabletoconnectErrorraisedbyExternalRPCcallinibm_utils.
rbc,line356[:0]Timeout(RPC:unabletoconnect)RbAgentcommandsync-srvradgethasfailed.
whenyouexportabigamountofdata.
CausesTheHTTPanswertimeoutoftheagentduringthecommandssenttotheserverisfourminutes.
Dependingfromtheamountofdatatoexporttothe.
radfile,fourminutesmightnotbeenoughfortheservertocompletetheexportandsendtheHTTPanswertotheagent,sotheHTTPtimeouterrorontheagentmightoccurforbigamountofdata.
Forexample10GBormore.
ResolvingtheproblemYoucanincreasethetimeoutvaluebysettinganenvironmentvariablenamedRBAGT_HTTP_TIMEOUTinthecommandshellwheretherbagentsync-srvradgetcommandislaunched.
Thismakestheagentmodifythedefaultvaluewiththistime(inseconds).
Thevaluedependsfromthedatatoexport.
Forexample,avalueof1200canbereasonablefor20minutes.
AgentbehaviorwhentheRebootonFatalErroroptionisspecifiedSymptomsWhenthetargetoperatesinkernel-freemodeandthefollowingconditionsaremet:vWinPeismissingthenetworkdriversvTheRebootonFatalErroroptionisselectedwhentheagentisrebootedvTheAutomaticDriverBindingmodeisspecifiedforWinPetheproductautomaticallyattemptstobindthedrivers.
ResolvingtheproblemAnewoptionwasaddedtotherad-makewpecommandasfollows:rad-makewpe[update=EngineItemID][drivermode=auto|none]Ifthedrivermodeisnotspecified,thedefaultvalue(none)isused.
DeployingonKVM6.
1hypervisorfailsSymptomsThedeploymentonaKVM6.
1hypervisormightfailwhentheNICmodelis"HypervisorDefault".
ThedeploymentworkswhentheNICdevicemodelis"E1000".
DuringthedeploymenttheKVMguestMACaddresschangesfromXX:XX:XX:XX:XX:XXto00:00:00:XX:XX:XX.
ResolvingtheproblemTosolvethisissue,aDHCPconfigurationisrequired.
Softwaremodulewizarddoesnotresolve.
lnkfilescontainedinfolderSymptomsWhencreatinganewsoftwaremodule,thewizardasksyoutospecifythefoldercontainingtherequiredfiles.
Thecontrolisthenpassedtotherbagent,whichTroubleshootingandsupport47createstherequestedsoftwaremodule.
Ifthefoldercontainssomelinkfiles,havingthe.
lnkextension,theywillnotberesolvedbytherbagent.
ResolvingtheproblemNoworkaroundiscurrentlyavailableforthisissue.
HowtousehotRAIDdisksonHPserversSymptomsTocorrectlyuseRAIDdisksonHPservers,youmustenterthecorrectsyntaxfor"PhysicalDrives".
Toknowthesyntaxtouseforthe"Physicaldrives"fieldofaRAIDhardwareconfiguration,firstlaunchaRAIDcapture.
TolaunchtheRAIDcapture:1.
Right-clickthetarget.
2.
SelectAdditionalfeatures>Capturehardwareparameters>RAIDcapture3.
Fromthecapturetrace,selectServerhistory>Tasks>Capturehardwareparameters4.
Expandthesection.
5.
Right-clickthespecifictargetentry.
6.
SelectShowtracefile.
7.
ClickFulllog.
Theraidcapt.
rbcoutputisdisplayedbetween:vstartofdatainraidcapt.
iniandvendofdatainraidcapt.
iniHereyoufindtheinformationaboutexistingphysicaldrivesandthesyntaxtoapplyforaRAIDconfiguration:ex:Drive=1I:1:1,1I:1:2,1I:1:3,1I:1:4,2I:1:5,2I:1:6,2I:1:7,2I:1:8Forexample,tocreateanarraywiththreedisks,thesyntaxisasfollows:"Physicaldisks"-->1I:1:1,1I:1:2,1I:1:3ResolvingtheproblemTocorrectlyuseRAIDhotsparedisksonHPservers,youmustentertheinformationaboutwhicharraythehotsparedrivebelongsto,byspecifyingtheletterofthearrayatthebeginningofeveryhotsparedriveinthelist.
Forexample,ifyouwanttoaddthedisk3asahotspareofthefirstarray(A)definedasfollows:Physicaldrives:"1I:1.
1,1I:1:2"thecorrectsyntaxisthefollowing:Hot-sparedrives:"A:1I:3.
1"Passwordmustbechangedinrembo.
conftologinonSolarisSymptomsWhenyouinstallTivoliProvisioningManagerforImagesorTivoliProvisioningManagerforOSDeploymentonaSolarisplatform,afterasuccessfulinstallation,youcannotlogontotheUI.
CausesThecredentialsprovidedduringtheinstallationprocessarenotvalid.
48TivoliProvisioningManagerforOSDeployment:TroubleshootingandsupportguideResolvingtheproblemTosolvethisissue,performthefollowingsteps:1.
Encryptthedesiredpasswordusingamd5alghoritm.
2.
ReplacethevalueforNetpasswordintherembo.
conffilelocatedintheinstallationdirectorywiththeencryptedstring:ex:NetPassword"674861BB588C7D56702E52ED86E7E56C"3.
ReplacethevalueforREMBO_PWDinthetpmfosdvarsfilelocatedinthe/etcdirectorywiththeencryptedstring:ex:REMBO_PWD="674861BB588C7D56702E52ED86E7E56C"4.
Fromtheinstallationdirectory,manuallyrestarttheOSDeploymentserverbyrunningthecommand:.
/rembo-d-v4-c.
/rembo.
conf5.
Fromtheinstall_dir/scripts/solarisdirectory,restarttherbagentbyrunningthecommand:.
/3_rbagent.
shstartHPProLiantDL585G2requiresBIOSupdatesSymptomsTosuccessfullyperformRAIDdeploymentsandhardwarecapturetasks,theHPProLiantDL585G2hardwarerequiressomeBIOSupdates.
ResolvingtheproblemToresolvethisissue,performthefollowingstepsontheHPDL585G2Proliantserver:1.
BoottheserverandgototheBIOSsettings.
2.
SelecttheAdvancedOptions.
3.
SelecttheLinuxx86_64HPETOptionanddisableit.
4.
SaveandclosetheBIOSsettings.
MinimumBIOSversionrequiredonsomeHPlaptopsSymptomsTosuccessfullydeployinkernelmodeonthefollowingHPsystems:vHPEliteBook8470pNotebookPCvHPEliteBook8470wMobileWorkstationvHPEliteBook8570pNotebookPCvHPEliteBookFolio9470mNotebookPCvHPProBook6470bNotebookPCvHPProBook6570bNotebookPCaminimumBIOSversionisrequired.
ResolvingtheproblemToresolvethisissue,theBIOSupdateVersionF.
40(releasedinFebruary2013),oranylaterversion,mustbeappliedinadvance.
IncorrectfontsonthetargetscreenNamesappearingcorrectlyintheOSdeploymentservercannotbeproperlyviewedonthescreenofthetarget.
SymptomsUnderscores_appearonthescreenofthetargetinsteadoftheexpectednamewhichdisplayscorrectlyontheOSdeploymentserver.
Troubleshootingandsupport49|||||||||||||CausesThecorrectfontsarenotloadedtothetargetbecausethelanguageoftheOSdeploymentserverdoesnotusethesefonts.
Theproblematiccharactersareshownasunderscores_.
ResolvingtheproblemUsenameswithfontsthatarecompatiblewiththelanguageoftheOSdeploymentserver.
BIOSistooslowtobootfromUSBdisksSymptomsTheUSBdriveisnotrecognizedasabootdevicebytheBIOSduringitsfirstbootsequence,andthetargetdoesnotbootfromtheUSBdevice.
CausesTargetcomputersmightbetooslowbeforeidentifyingaUSBdrive,andtheUSBdriveisnottakenintoaccountinthebootsequence.
Thisproblemonlyoccursifthetargetwascompletelyshutdownbeforestartingthedeployment.
ResolvingtheproblemIfthediskisnotrecognized,youarerequiredtoperformawarmrebootofthetargetcomputer(ctrl+alt+del).
LimitedpartitionremovaltaskisnotprocessedbyatargetbootedfromUSBSymptomsRemovingthelimitedpartitiononatargetcomputerbootedfromUSBfails.
CausesIfyouselectatargetbootedfromUSBandperformthefollowingactions:1.
SelectAdditionalfeaturesinthecontextualmenu.
2.
SelectDestroyharddiskcontentintheadditionalfeaturewizard.
3.
SelectLimitedPartitionremovalasDisposalmethod.
4.
Followtheremaininginstructionsfromthewizard.
Thetaskiscreatedandisalsovisibleonthetaskpage,butitdoesnotstart.
ResolvingtheproblemWhenbootingfromthenetwork,thetaskisstartedandendssuccessfully.
TroubleshootingJavaAPIIfyouareexperiencingproblems,trylookinginthefollowingplacesforerrors:JavaAPIexceptionsManyproblemsarereportedwithanexceptionattheJavaAPIlevel.
Forexample,improperuseoftheAPIorproblemscontactingtheprovisioningserver.
ExceptionstatusinRBActivityTargetWhenthereisaproblemwithatask,itisreportedinthestatusfieldwiththemethodgetError().
TasktracesTracesarestoredontheprovisioningserver.
Bydefault,thefilepathisc:\tpmfosfiles\global\hosttasks.
The.
inifilescontainparametersforthetaskandforeachtarget.
Thelogfilescontainacopyoftheconsoleofthetarget.
ThetargetareidentifiedbytheirBOMID,anidentifierused50TivoliProvisioningManagerforOSDeployment:Troubleshootingandsupportguideinternallybytheproduct.
IfyouknowonlytheIPaddress,MACaddressorserialnumber(SN)ofthetarget,youhavetosearchforitinall.
inifilesoftargetactivities.
Thenyoucanretrievethecorrespondinglogfile.
AccessingthesetracesfromtheWebinterfaceismoreconvenient.
ServertracesServertracesarestoredontheprovisioningserver.
Bydefault,theyarelocatedinthefilepath,c:\tpmfosfiles\logs.
Thedefaultdetaillevelis3,whichcanberaisedto4withoutimpactingtheperformance,orevento5,butthisslowsdowntheserver.
TheeasiestwaytochangethisdebuglevelisintheWebinterface,orwithRBServerConfig.
setGlobalDebugLevel().
TochangethedebuglevelusingtheWebinterfaceclickonServerparameters,thenclickConfigurationandundertheheadingBaseparametersthereisaGlobaldebuglevelwhichcanbeedited.
Iftheparameterispresentintheconfig.
csvfile,thevaluechangesnexttimetheserverreloadsitsOSconfiguration,forexample,whenitisrestarted.
Thereferenceforconfig.
csvisathttp://www-1.
ibm.
com/support/docview.
wssuid=swg21247013.
ThesetracescanalsobeaccessedfromtheWebinterface.
WebInterfaceExtensiontracesThesetracesarelocatedbydefaultinfilepath,c:\programfiles\commonfiles\ibmtivoli\rbagent.
log.
Errorsoccurringwhenthetargetofataskisrbagentcanbefoundthere.
DatabasetracesTracingisdisabledbydefaultfortheproductDatabaseGateway(=dbgw.
exe=remboodbcservice).
Itcanbeveryusefultoturnthesetracesonbecausealldatabaserequestsperformedbytheprovisioningserverandalltasktargetspassusingthisprocess.
TracingoftheSQLqueriesisonlyenablediftheprocessisrunfromthecommandlinewith"dbgw-d-v4-f".
TracingoftheSQLqueriesandresultsareenablediftheverbosityparameteris5insteadof4.
Bothslowdownsignificantlytheoverallperformanceoftheserver.
Thesamecommandlineparameterscanbeusedtoruntheremboodbcservicewithtraces:fromWindowsservicemanageruserinterfacetostarttheservicemanuallywithStartparameters="-d-v4-f".
TheJDBCversionofthedatabasegateway(com.
rembo.
dbgw.
Dbgw)tracesqueriesandresultswhenstartedwithoption"-d".
DatabasecontentcheckTheeasywaytoinspectdatabasecontentsisbyopeningthefilec:\programfiles\ibm\tpmfosd\autodeploy.
mdbwithMicrosoftAccess.
IfMicrosoftAccessisnotinstalledonyourprovisioningserverandyoucannotreachthefilefromanothercomputer,youcanstilllookatdatabasecontentsdirectlyontheprovisioningserverwithasimple"telnetlocalhost2020".
Port2020istheTCPportusedtocommunicatewithourdatabasegateway.
Thisisdocumentedinhttp://www.
rembo.
com/rbo/docs/SQLOpenEx.
html.
AnupdateddescriptionofalltablesandcolumnsintheproductSQLdatabasecanbedownloadeddirectlyfromtheserverusingtheURLhttp://:8080/virtual/AutoDeployDistrib.
iniServerOSconfigurationThemainOSconfigurationfilesarerembo.
conf,config.
csvandradb.
ini.
OfflinedeploymentfailsonvirtualmachinesDeploymentfailsonavirtualmachinewhenitisstartedfromanOSdeploymentCD/DVD.
Troubleshootingandsupport51SymptomsYouareusinganOSdeploymentCD/DVDtodeployavirtualmachine.
Thedeploymentfails.
CausesThebootorderofyourvirtualmachineliststheCDdrivebeforetheharddisk.
ResolvingtheproblemChangethebootorderonyourvirtualmachinetoensurethattheCDdriveisaftertheharddisk.
UploadinglogstoaUSBkeydoesnotworkWhileperformingadeploymentfromadeploymentmedia,youcannotuploadthedeploymentlogstoaUSBkeySymptomsYouaredeployingasystemprofilefromadeploymentmedia.
YouwanttouploadthedeploymentlogstoaUSBkey,butitdoesnotwork.
ResolvingtheproblemIfyouneedtosendthelogstothesupportteam,usetheshowtracefeature,scrolldownandtakepictureswithadigitalcameraofthelogs.
Sendthepicturestothesupportteam.
CustomizingthetimeoutdurationwhilecloningfromareferenceWindowsimagefileSymptomsYouarecreatinganewsystemprofilestartingfromaWIMfile.
Inthelast"ProfileWizard"youareaskedtowaitforthetasktobecomplete.
Bydefault,thetimeoutis600seconds.
Ifthetimeneededtocompletethetaskexceedsthislimit,youreceivethefollowingerrormessage:Figure3.
ProfileWizard52TivoliProvisioningManagerforOSDeployment:TroubleshootingandsupportguideResolvingtheproblemTosolvethisissue,customizethetimeoutduration.
Todothis,performthefollowingactions:1.
Inthedatabase,gotothetableSettings,lookfortherecordwhereType="IFPROBE"andgetthevaluecorrespondingtothefield"IniFile",forexample,radset-prbngnst0B1AS9RI.
ini.
2.
Editthe.
INIfile,locatedintheBasedirectory/global/schemesbychangingthevalueassignedtothetimeout,asshowninthefollowingexample:[Task]type="IFPROBE"[Settings]StartEnv="AGENT"timeout="600"Thelinetimeout="600"mightnotbepresent,forexample,inthecaseofanupgrade.
Inthiscase,youcanspecifyatimeoutvalueafterthelineStartEnv="AGENT".
Thevalueisexpressedinseconds.
Forafreshinstallation,instead,theINIfileisupdated.
ItisnotnecessarytorestarttheserverortheWebInterfaceextension,youcanjustrestartthetask.
CustomizingthetimeoutdurationwhilecloningfromareferencemachineSymptomsYouarecreatinganewsystemprofilestartingfromareferencemachine.
Inthelast"ProfileWizard"youareaskedtowaitforthetasktobecomplete.
Bydefault,thetimeoutis600seconds.
Ifthetimeneededtocompletethetaskexceedsthislimit,youreceivethefollowingerrormessage:ResolvingtheproblemFigure4.
ProfileWizardTroubleshootingandsupport53Tosolvethisissue,customizethetimeoutduration.
Todothis,performthefollowingsteps:1.
Inthedatabase,gotothetableSettings,lookfortherecordwhereType="OSPROBE"andgetthevaluecorrespondingtothefield"IniFile",forexample,radset-dtctprtn0V47XQD6.
ini.
2.
Editthe.
INIfile,locatedintheBasedirectoryforOSDfiles/global/schemesbychangingthevalueassignedtothetimeout,asshowninthefollowingexample:[Task]type="OSPROBE"[Settings]timeout="600"Thelinetimeout="600"mightnotbepresent,forexample,inthecaseofanupgrade.
Inthiscase,youcanaddtheSettingssectionwiththetimeoutfieldtospecifyyourpreferredvalue,whichisexpressedinseconds.
Forafreshinstallation,instead,theINIfileisupdated.
ItisnotnecessarytorestarttheserverortheWebInterfaceextension,youcanjustrestartthetask.
TheuserinterfaceforBIOSandUEFIisnotlocalizedProblemdescriptionTheuserinterfacepresentonthetargetscreenforbothBIOSandUEFIswitcherisnottranslatedintonationallanguages,itisdisplayedonlyinEnglish.
DeploymentfailsonPowerEdgeR720whenconfiguredtobootwithSDcardSymptomsWhenthemachinePowerEdgeR720isconfiguredtobootwithainternalSDcard,thedeploymentonthatmachinefails.
ResolvingtheproblemTosolvethisissue,removetheinternalSDcardortodisabletheinternalSDportviaBIOS.
Formoreinformation,seehttp://www.
dell.
com/downloads/global/products/pedge/en/poweredge-idsdm-whitepaper-en.
pdf.
ConventionsCuegraphicindicateinformationthatispertinentonlyforspecificoperatingsystems.
WindowsSpecifictoallsupportedMicrosoftWindowsoperatingsystems.
Windows7SpecifictoWindows7operatingsystem.
2008SpecifictoWindowsServer2008operatingsystem.
VistaSpecifictoWindowsVistaoperatingsystem.
54TivoliProvisioningManagerforOSDeployment:Troubleshootingandsupportguide2003SpecifictoWindowsServer2003operatingsystem.
XPSpecifictoWindowsXPoperatingsystem.
2000SpecifictoWindows2000operatingsystem.
UNIXSpecifictoallsupportedUNIX-likeoperatingsystems.
LinuxSpecifictoLinuxoperatingsystems.
RedHatSpecifictoRedHatoperatingsystem.
SUSESpecifictoSuSEoperatingsystem.
AIXSpecifictoAIXoperatingsystem.
HPUXSpecifictoHP-UXoperatingsystem.
SolarisSpecifictoSolarisoperatingsystem.
NoticesIBMmaynotoffertheproducts,services,orfeaturesdiscussedinthisdocumentinothercountries.
ConsultyourlocalIBMrepresentativeforinformationontheproductsandservicescurrentlyavailableinyourarea.
AnyreferencetoanIBMproduct,program,orserviceisnotintendedtostateorimplythatonlythatIBMproduct,program,orservicemaybeused.
Anyfunctionallyequivalentproduct,program,orservicethatdoesnotinfringeanyIBMintellectualpropertyrightmaybeusedinstead.
However,itistheuser'sresponsibilitytoevaluateandverifytheoperationofanynon-IBMproduct,program,orservice.
IBMmayhavepatentsorpendingpatentapplicationscoveringsubjectmatterdescribedinthisdocument.
Thefurnishingofthisdocumentdoesnotgrantyouanylicensetothesepatents.
Youcansendlicenseinquiries,inwriting,to:IBMCorporation2Z4A/10111400BurnetRoadAustin,TX78758U.
S.
A.
Forlicenseinquiriesregardingdouble-byte(DBCS)information,contacttheIBMIntellectualPropertyDepartmentinyourcountryorsendinquiries,inwriting,to:IBMWorldTradeAsiaCorporationLicensing2-31Roppongi3-chome,Minato-kuTokyo106,JapanTroubleshootingandsupport55ThefollowingparagraphdoesnotapplytotheUnitedKingdomoranyothercountrywheresuchprovisionsareinconsistentwithlocallawINTERNATIONALBUSINESSMACHINESCORPORATIONPROVIDESTHISPUBLICATION"ASIS"WITHOUTWARRANTYOFANYKIND,EITHEREXPRESSORIMPLIED,INCLUDING,BUTNOTLIMITEDTO,THEIMPLIEDWARRANTIESOFNON-INFRINGEMENT,MERCHANTABILITYORFITNESSFORAPARTICULARPURPOSE.
Somestatesdonotallowdisclaimerofexpressorimpliedwarrantiesincertaintransactions,therefore,thisstatementmaynotapplytoyou.
Thisinformationcouldincludetechnicalinaccuraciesortypographicalerrors.
Changesareperiodicallymadetotheinformationherein;thesechangeswillbeincorporatedinneweditionsofthepublication.
IBMmaymakeimprovementsand/orchangesintheproduct(s)and/ortheprogram(s)describedinthispublicationatanytimewithoutnotice.
Anyreferencesinthisinformationtonon-IBMWebsitesareprovidedforconvenienceonlyanddonotinanymannerserveasanendorsementofthoseWebsites.
ThematerialsatthoseWebsitesarenotpartofthematerialsforthisIBMproductanduseofthoseWebsitesisatyourownrisk.
IBMmayuseordistributeanyoftheinformationyousupplyinanywayitbelievesappropriatewithoutincurringanyobligationtoyou.
Licenseesofthisprogramwhowishtohaveinformationaboutitforthepurposeofenabling:(i)theexchangeofinformationbetweenindependentlycreatedprogramsandotherprograms(includingthisone)and(ii)themutualuseoftheinformationwhichhasbeenexchanged,shouldcontact:IBMCanadaLtd.
OfficeoftheLabDirector8200WardenAvenueMarkham,OntarioL6G1C7CanadaSuchinformationmaybeavailable,subjecttoappropriatetermsandconditions,includinginsomecases,paymentofafee.
ThelicensedprogramdescribedinthisdocumentandalllicensedmaterialavailableforitareprovidedbyIBMundertermsoftheIBMCustomerAgreement,IBMInternationalProgramLicenseAgreementoranyequivalentagreementbetweenus.
Informationconcerningnon-IBMproductswasobtainedfromthesuppliersofthoseproducts,theirpublishedannouncementsorotherpubliclyavailablesources.
IBMhasnottestedthoseproductsandcannotconfirmtheaccuracyofperformance,compatibilityoranyotherclaimsrelatedtonon-IBMproducts.
Questionsonthecapabilitiesofnon-IBMproductsshouldbeaddressedtothesuppliersofthoseproducts.
Thisinformationcontainsexamplesofdataandreportsusedindailybusinessoperations.
Toillustratethemascompletelyaspossible,theexamplesincludethenamesofindividuals,companies,brands,andproducts.
Allofthesenamesarefictitiousandanysimilaritytothenamesandaddressesusedbyanactualbusinessenterpriseisentirelycoincidental.
COPYRIGHTLICENSE:56TivoliProvisioningManagerforOSDeployment:TroubleshootingandsupportguideThisinformationmaycontainsampleapplicationprograms,insourcelanguage,whichillustrateprogrammingtechniquesonvariousoperatingplatforms.
Youmaycopy,modify,anddistributethesesampleprogramsinanyformwithoutpaymenttoIBMforthepurposesofdeveloping,using,marketing,ordistributingapplicationprogramsconformingtotheapplicationprogramminginterfacefortheoperatingplatformforwhichthesampleprogramsarewritten.
Theseexampleshavenotbeenthoroughlytestedunderallconditions.
IBM,therefore,cannotguaranteeorimplyreliability,serviceability,orfunctionoftheseprograms.
Eachcopyoranyportionofthesesampleprogramsoranyderivativeworkmustincludeacopyrightnoticeasfollows:(C)(yourcompanyname)(year).
PortionsofthiscodearederivedfromIBMCorp.
SamplePrograms.
(C)CopyrightIBMCorp.
_entertheyearoryears_.
Allrightsreserved.
TrademarksIBM,theIBMlogo,andibm.
comaretrademarksorregisteredtrademarksofInternationalBusinessMachinesCorporationintheUnitedStates,othercountries,orboth.
IftheseandotherIBMtrademarkedtermsaremarkedontheirfirstoccurrenceinthisinformationwithatrademarksymbol(or),thesesymbolsindicateU.
S.
registeredorcommonlawtrademarksownedbyIBMatthetimethisinformationwaspublished.
Suchtrademarksmayalsoberegisteredorcommonlawtrademarksinothercountries.
AcurrentlistofIBMtrademarksisavailableontheWebatCopyrightandtrademarkinformationatwww.
ibm.
com/legal/copytrade.
shtmlAdobeiseitheraregisteredtrademarkortrademarkofAdobeSystemsIncorporatedintheUnitedStates,othercountries,orboth.
IntelandPentiumaretrademarksorregisteredtrademarksofIntelCorporationoritssubsidiariesintheUnitedStates,and/orothercountries.
JavaandallJava-basedtrademarksandlogosaretrademarksorregisteredtrademarksofOracleand/oritsaffiliates.
LinuxisatrademarkofLinusTorvaldsintheUnitedStates,othercountries,orboth.
Microsoft,Windows,andWindowsNTaretrademarksofMicrosoftCorporationintheUnitedStates,othercountries,orboth.
UNIXisaregisteredtrademarkofTheOpenGroupintheUnitedStatesandothercountries.
OtherproductandservicenamesmaybetrademarksofIBMorothercompanies.
CopyrightsCopyrightIBMCorporation2012.
Allrightsreserved.
U.
S.
GovernmentUsersRestrictedRights-Use,duplicationordisclosurerestrictedbyGSAADPScheduleContractwithIBMCorp.
Troubleshootingandsupport57IBMwebsitepagesmaycontainotherproprietarynoticesandcopyrightinformationwhichshouldbeobserved.
Portionsofthird-partysoftwareincludedinthisIBMproductisusedwithpermissionandiscoveredunderthefollowingcopyrightattributionstatements:vCopyright(c)1998-2005,TheOpenSSLProject.
Allrightsreserved.
vCopyright(c)1995-2005Jean-loupGaillyandMarkAdler,theZLIBdatacompressionlibrary.
vCopyright1994-2006,TheFreeBSDProject.
Allrightsreserved.
TheMD5Message-DigestAlgorithmwasdevelopedbyRonRivest.
ThepublicdomainClanguageimplementationusedinthisprogramwaswrittenbyColinPlumbin1993.
Permissiontouse,copy,modify,anddistributethissoftwareanditsdocumentationforanypurposeandwithoutfeeisherebygranted,withoutanyconditionsorrestrictions.
Thissoftwareisprovided"asis"withoutexpressorimpliedwarranty.
PortionsincludecryptographicsoftwarewrittenbyEricYoung().
ThisproductbecauseincludesoftwarewrittenbyTimHudson().
NoticesfortianocoreEDKIIUDK2010Copyright2004,IntelCorporationAllrightsreserved.
Redistributionanduseinsourceandbinaryforms,withorwithoutmodification,arepermittedprovidedthatthefollowingconditionsaremet:vRedistributionsofsourcecodemustretaintheabovecopyrightnotice,thislistofconditionsandthefollowingdisclaimer.
vRedistributionsinbinaryformmustreproducetheabovecopyrightnotice,thislistofconditionsandthefollowingdisclaimerinthedocumentationand/orothermaterialsprovidedwiththedistribution.
vNeitherthenameoftheIntelCorporationnorthenamesofitscontributorsmaybeusedtoendorseorpromoteproductsderivedfromthissoftwarewithoutspecificpriorwrittenpermission.
THISSOFTWAREISPROVIDEDBYTHECOPYRIGHTHOLDERSANDCONTRIBUTORS"ASIS"ANDANYEXPRESSORIMPLIEDWARRANTIES,INCLUDING,BUTNOTLIMITEDTO,THEIMPLIEDWARRANTIESOFMERCHANTABILITYANDFITNESSFORAPARTICULARPURPOSEAREDISCLAIMED.
INNOEVENTSHALLTHECOPYRIGHTOWNERORCONTRIBUTORSBELIABLEFORANYDIRECT,INDIRECT,INCIDENTAL,SPECIAL,EXEMPLARY,ORCONSEQUENTIALDAMAGES(INCLUDING,BUTNOTLIMITEDTO,PROCUREMENTOFSUBSTITUTEGOODSORSERVICES;LOSSOFUSE,DATA,ORPROFITS;ORBUSINESSINTERRUPTION)HOWEVERCAUSEDANDONANYTHEORYOFLIABILITY,WHETHERINCONTRACT,STRICTLIABILITY,ORTORT(INCLUDINGNEGLIGENCEOROTHERWISE)ARISINGINANYWAYOUTOFTHEUSEOFTHISSOFTWARE,EVENIFADVISEDOFTHEPOSSIBILITYOFSUCHDAMAGE.
58TivoliProvisioningManagerforOSDeployment:TroubleshootingandsupportguidePrintedinUSA