losesrebootsystemnow什么意思

AdministeringAvayaAuraSystemPlatformRelease1.
1.
1April20102010AvayaInc.
AllRightsReserved.
NoticesWhilereasonableeffortsweremadetoensurethattheinformationinthisdocumentwascompleteandaccurateatthetimeofprinting,AvayaInc.
canassumenoliabilityforanyerrors.
Changesandcorrectionstotheinformationinthisdocumentmightbeincorporatedinfuturereleases.
DocumentationdisclaimerAvayaInc.
isnotresponsibleforanymodifications,additions,ordeletionstotheoriginalpublishedversionofthisdocumentationunlesssuchmodifications,additions,ordeletionswereperformedbyAvaya.
Customerand/orEndUseragreetoindemnifyandholdharmlessAvaya,Avaya'sagents,servantsandemployeesagainstallclaims,lawsuits,demandsandjudgmentsarisingoutof,orinconnectionwith,subsequentmodifications,additionsordeletionstothisdocumentationtotheextentmadebytheCustomerorEndUser.
LinkdisclaimerAvayaInc.
isnotresponsibleforthecontentsorreliabilityofanylinkedWebsitesreferencedelsewherewithinthisdocumentation,andAvayadoesnotnecessarilyendorsetheproducts,services,orinformationdescribedorofferedwithinthem.
Wecannotguaranteethattheselinkswillworkallthetimeandwehavenocontrolovertheavailabilityofthelinkedpages.
WarrantyAvayaInc.
providesalimitedwarrantyonthisproduct.
Refertoyoursalesagreementtoestablishthetermsofthelimitedwarranty.
Inaddition,Avaya'sstandardwarrantylanguage,aswellasinformationregardingsupportforthisproduct,whileunderwarranty,isavailablethroughtheAvayaSupportWebsite:http://www.
avaya.
com/supportLicensesUSEORINSTALLATIONOFTHEPRODUCTINDICATESTHEENDUSER'SACCEPTANCEOFTHETERMSSETFORTHHEREINANDTHEGENERALLICENSETERMSAVAILABLEONTHEAVAYAWEBSITEhttp://www.
avaya.
com/support/LicenseInfo/("GENERALLICENSETERMS").
IFYOUDONOTWISHTOBEBOUNDBYTHESETERMS,YOUMUSTRETURNTHEPRODUCT(S)TOTHEPOINTOFPURCHASEWITHINTEN(10)DAYSOFDELIVERYFORAREFUNDORCREDIT.
AvayagrantsEndUseralicensewithinthescopeofthelicensetypesdescribedbelow.
Theapplicablenumberoflicensesandunitsofcapacityforwhichthelicenseisgrantedwillbeone(1),unlessadifferentnumberoflicensesorunitsofcapacityisspecifiedintheDocumentationorothermaterialsavailabletoEndUser.
"DesignatedProcessor"meansasinglestand-alonecomputingdevice.
"Server"meansaDesignatedProcessorthathostsasoftwareapplicationtobeaccessedbymultipleusers.
"Software"meansthecomputerprogramsinobjectcode,originallylicensedbyAvayaandultimatelyutilizedbyEndUser,whetherasstand-aloneProductsorpre-installedonHardware.
"Hardware"meansthestandardhardwareProducts,originallysoldbyAvayaandultimatelyutilizedbyEndUser.
LicensetypesDesignatedSystem(s)License(DS).
EndUsermayinstallanduseeachcopyoftheSoftwareononlyoneDesignatedProcessor,unlessadifferentnumberofDesignatedProcessorsisindicatedintheDocumentationorothermaterialsavailabletoEndUser.
AvayamayrequiretheDesignatedProcessor(s)tobeidentifiedbytype,serialnumber,featurekey,locationorotherspecificdesignation,ortobeprovidedbyEndUsertoAvayathroughelectronicmeansestablishedbyAvayaspecificallyforthispurpose.
ConcurrentUserLicense(CU).
EndUsermayinstallandusetheSoftwareonmultipleDesignatedProcessorsoroneormoreServers,solongasonlythelicensednumberofUnitsareaccessingandusingtheSoftwareatanygiventime.
A"Unit"meanstheunitonwhichAvaya,atitssolediscretion,basesthepricingofitslicensesandcanbe,withoutlimitation,anagent,portoruser,ane-mailorvoicemailaccountinthenameofapersonorcorporatefunction(e.
g.
,webmasterorhelpdesk),oradirectoryentryintheadministrativedatabaseutilizedbytheProductthatpermitsoneusertointerfacewiththeSoftware.
Unitsmaybelinkedtoaspecific,identifiedServer.
DatabaseLicense(DL).
CustomermayinstallanduseeachcopyoftheSoftwareononeServeroronmultipleServersprovidedthateachoftheServersonwhichtheSoftwareisinstalledcommunicatewithnomorethanasingleinstanceofthesamedatabase.
CPULicense(CP).
EndUsermayinstallanduseeachcopyoftheSoftwareonanumberofServersuptothenumberindicatedbyAvayaprovidedthattheperformancecapacityoftheServer(s)doesnotexceedtheperformancecapacityspecifiedfortheSoftware.
EndUsermaynotre-installoroperatetheSoftwareonServer(s)withalargerperformancecapacitywithoutAvaya'spriorconsentandpaymentofanupgradefee.
NamedUserLicense(NU).
Customermay:(i)installandusetheSoftwareonasingleDesignatedProcessororServerperauthorizedNamedUser(definedbelow);or(ii)installandusetheSoftwareonaServersolongasonlyauthorizedNamedUsersaccessandusetheSoftware.
"NamedUser,"meansauserordevicethathasbeenexpresslyauthorizedbyAvayatoaccessandusetheSoftware.
AtAvaya'ssolediscretion,a"NamedUser"maybe,withoutlimitation,designatedbyname,corporatefunction(e.
g.
,webmasterorhelpdesk),ane-mailorvoicemailaccountinthenameofapersonorcorporatefunction,oradirectoryentryintheadministrativedatabaseutilizedbytheProductthatpermitsoneusertointerfacewiththeProduct.
ShrinkwrapLicense(SR).
WithrespecttoSoftwarethatcontainselementsprovidedbythirdpartysuppliers,EndUsermayinstallandusetheSoftwareinaccordancewiththetermsandconditionsoftheapplicablelicenseagreements,suchas"shrinkwrap"or"clickwrap"licenseaccompanyingorapplicabletotheSoftware("ShrinkwrapLicense").
ThetextoftheShrinkwrapLicensewillbeavailablefromAvayauponEndUser'srequest(see"Third-partyComponents"formoreinformation).
CopyrightExceptwhereexpresslystatedotherwise,theProductisprotectedbycopyrightandotherlawsrespectingproprietaryrights.
Unauthorizedreproduction,transfer,andorusecanbeacriminal,aswellasacivil,offenseundertheapplicablelaw.
Third-partycomponentsCertainsoftwareprogramsorportionsthereofincludedintheProductmaycontainsoftwaredistributedunderthirdpartyagreements("ThirdPartyComponents"),whichmaycontaintermsthatexpandorlimitrightstousecertainportionsoftheProduct("ThirdPartyTerms").
InformationidentifyingThirdPartyComponentsandtheThirdPartyTermsthatapplytothemisavailableontheAvayaSupportWebsite:http://www.
avaya.
com/support/ThirdPartyLicense/Preventingtollfraud"Tollfraud"istheunauthorizeduseofyourtelecommunicationssystembyanunauthorizedparty(forexample,apersonwhoisnotacorporateemployee,agent,subcontractor,orisnotworkingonyourcompany'sbehalf).
Beawarethattherecanbeariskoftollfraudassociatedwithyoursystemandthat,iftollfraudoccurs,itcanresultinsubstantialadditionalchargesforyourtelecommunicationsservices.
AvayafraudinterventionIfyoususpectthatyouarebeingvictimizedbytollfraudandyouneedtechnicalassistanceorsupport,callTechnicalServiceCenterTollFraudInterventionHotlineat+1-800-643-2353fortheUnitedStatesandCanada.
Foradditionalsupporttelephonenumbers,seetheAvayaSupportWebsite:http://www.
avaya.
com/support/2AdministeringAvayaAuraSystemPlatformApril2010SuspectedsecurityvulnerabilitieswithAvayaProductsshouldbereportedtoAvayabysendingmailto:securityalerts@avaya.
com.
TrademarksAvayaandAvayaAuraareregisteredtrademarksofAvaya.
Allnon-Avayatrademarksarethepropertyoftheirrespectiveowners.
PuTTYiscopyright1997-2009SimonTatham.
DownloadingdocumentsForthemostcurrentversionsofdocumentation,seetheAvayaSupportWebsite:http://www.
avaya.
com/supportContactAvayaSupportAvayaInc.
providesatelephonenumberforyoutousetoreportproblemsortoaskquestionsaboutyourproduct.
Thesupporttelephonenumberis1-800-242-2121intheUnitedStates.
Foradditionalsupporttelephonenumbers,seetheAvayaWebsite:http://www.
avaya.
com/supportAdministeringAvayaAuraSystemPlatformApril201034AdministeringAvayaAuraSystemPlatformApril2010ContentsChapter1:AdministeringSystemPlatform.
9Administrationoverview.
9SystemPlatformManagementConsoleoverview.
9AccessingSystemPlatformManagementConsole.
10AccessingSystemPlatformthroughservicesport.
12VirtualMachineManagement.
12VirtualMachineManagementfielddescriptions.
13VirtualMachineManagementbuttondescriptions.
14Viewingdetailsofavirtualmachine.
14Rebootingavirtualmachine.
15Shuttingdownavirtualmachine.
15VirtualMachineConfigurationParametersfielddescriptions.
16VirtualMachineConfigurationParametersbuttondescriptions.
18Solutiontemplate.
18Servermanagement.
19ServerManagementoverview.
19PatchManagement.
19Logviewer.
26Dateandtimeconfiguration.
28Loggingconfiguration.
33Systemconfiguration.
36Networkconfiguration.
38Staticrouteconfiguration.
41Ethernetconfiguration.
44Alarmconfiguration.
45ManagingCertificates.
47Licensemanagement.
49SALgatewaymanagement.
50SystemPlatformFailover.
51Performancestatistics.
57EjectCDorDVD.
59FileManager.
60BackingupSystemPlatform.
60RestoringSystemPlatform.
64ShutdownorreboottheSystemPlatformserver.
66UserAdministration.
73UserAdministrationoverview.
73Localmanagement.
73EnterpriseLDAP.
79ChangeSystemPlatformpassword.
82Chapter2:Troubleshooting.
83DVDdoesnotmount.
83Troubleshootingsteps.
83VirtualmachinehasnoconnectivityoutsideafterassigningdedicatedNICsupport.
83Troubleshootingsteps-throughSystemDomain(Dom-0)83Troubleshootingsteps-throughSystemPlatformManagementConsole.
84Generalissueswiththesystemandwantstocontactsupport.
84AdministeringAvayaAuraSystemPlatformApril20105Troubleshootingsteps.
84IssueswhenconfiguringSystemPlatformHighAvailabilityFailover.
85Cannotestablishcommunicationthroughcrossovernetworkinterface.
85LocalIPaddressprovided.
85CannotestablishSSLcommunication.
86Standbyfirst-bootsequenceisnotyetfinished.
86Clusternodesarenotequal.
86Atemplateisinstalledonremotenode.
87NICsarenotactiveonbothsides.
87CannotestablishHAnetworkinterface.
88IssueswhenstartingSystemPlatformHighAvailabilityFailover.
88Differentplatformversionsagainstclusternodes.
88Atemplateisinstalledonremotenode.
88ResourcesarenotstartedonanynodeandcannotaccessSystemPlatformManagementConsole89CannotaccessSystemPlatformManagementConsoleafterStartFailover.
89Activeserverfails.
90Dataswitchfails.
90Heartbeatlinkfails.
91HighAvailabilityFailoverdoesnotwork.
91StartLDAPserviceonSystemDomain(Dom-0)91Troubleshootingsteps.
92SystemPlatformManagementConsolenotaccessible.
92Troubleshootingsteps.
92Re-enablingfailedstandbynodetoHighAvailabilityFailover.
92Troubleshootingsteps.
93Re-enablingfailedpreferrednodetoHighAvailabilityFailover.
93Troubleshootingsteps.
93TroubleshootingvirtualmachinewithdedicatedNICmayfailafterSystemPlatformupgrade.
94Troubleshootingsteps.
94AppendixA:HowSystemPlatformHighAvailabilityFailoverworks.
95AppendixB:AdministeringSALonSystemPlatform.
101SALGatewayconfiguration.
101LaunchingSALGatewayUI.
101ConfiguringSALGateway.
102ConfiguringSALEnterprise.
103ConfiguringRemoteAccessServer.
104ConfiguringNMS.
105Managingservicecontrol.
105Applyingconfigurationchanges.
106Configuringamanagedelement.
106Productsandmodels.
107MakingSALGatewaycommunicatewithSALEnterprise.
109AppendixC:Hardwarefaultdetectionandalarming.
113Hardwarefaultdetectionandalarming.
113Faulttypes.
114ForS8510.
114ForS8800.
116Generalsoftwarefaults.
1176AdministeringAvayaAuraSystemPlatformApril2010Lifecyclemanagerfaults.
119Performancefaults.
119HighAvailabilityfaults.
121PriortoSP1.
1.
1.
7.
2.
121SP1.
1.
1.
7.
2andlater.
123Index.
125AdministeringAvayaAuraSystemPlatformApril201078AdministeringAvayaAuraSystemPlatformApril2010Chapter1:AdministeringSystemPlatformAdministrationoverviewAfterinstallingAvayaAuraSystemPlatformandsolutiontemplates,youcanperformadministrativeactivitiesforSystemPlatformandsolutiontemplatesbyaccessingtheSystemPlatformManagementConsole.
Someoftheactivitiesthatyoucanperforminclude:ViewingtheloginformationMonitoringthehealthofthesystemUpdatingandmanagingpatchesManagingusersandpasswordsRebootingorshuttingdowntheserverYouradministrativeoperationsforSystemPlatformcanaffecttheperformanceofthesolutiontemplatesrunningonSystemPlatform.
Forexample,ifyourebootorshutdowntheSystemPlatformserver,thesystemalsorebootsorshutsdownthesolutionstemplatesrunningonSystemPlatform.
However,somesolutiontemplateshavetheirindependentadministrativeproceduresthatyoucanperformbyaccessingtherespectivesolutiontemplate.
Important:SystemPlatformdoesnottagQualityofService(QOS)bitsforanypackets(knownasLayer2802.
1ptagging).
However,SystemPlatformsupportstaggingofpacketsforQOSattheLayer2switch.
SystemPlatformManagementConsoleoverviewTheSystemPlatformWebinterfaceiscalledSystemPlatformManagementConsole.
AfterinstallingSystemPlatform,youcanlogontotheSystemPlatformManagementConsoletoviewdetailsofSystemPlatformvirtualmachines(namely,SystemDomain(Dom-0)andConsoleDomain)andinstalltherequiredsolutiontemplates,suchasMidsizeBusinessTemplateandperformvariousadministrativeactivitiesbyaccessingoptionsfromthenavigationpane.
AdministeringAvayaAuraSystemPlatformApril20109Thesystemdisplaystheadministrativeoptionsunderthreecategoriesasfollows:VirtualMachineManagementComponentsofSystemPlatformandofthesolutiontemplatesinstalledontheSystemPlatformserverareknownasvirtualmachines.
YoucanviewdetailsandmanagethevariousvirtualmachinesbyusingtheoptionsdisplayedunderVirtualMachineManagement.
ServerManagementYoucanperformvariousadministrativeactivitiesfortheSystemPlatformserversuchasconfiguringvarioussettingsfortheserver,viewinglogfiles,upgradingtoalatestreleaseofthesoftware,andbackingupandrestoringcurrentversionofthesoftwarebyusingtheoptionsdisplayedunderServerManagement.
UserAdministrationYoucanviewexistinguserprofilesforSystemPlatformServer,createnewuserprofiles,editexistinguserprofiles,andchangeexistingpasswordsbyusingtheoptionsdisplayedunderUserAdministration.
Note:TheSystemDomain(Dom-0),ConsoleDomainandcomponentsofthesolutiontemplatesrunningontheSystemPlatformareknownasvirtualmachines.
TheSystemDomain(Dom0)runsthevirtualizationengineandhasnodirectmanagementaccess.
ConsoleDomain(cdomorudom)providesmanagementaccesstothesystemthroughSystemPlatformManagementConsole.
AccessingSystemPlatformManagementConsoleYoucanviewtheSystemPlatforminformationbyaccessingtheSystemPlatformManagementConsolefromaWebbrowseronyourlaptoporanothercomputerconnectedtothesamenetworkastheSystemPlatformserver.
1.
OnaWebbrowser,typethefollowingURL:https://ipaddress/webconsole,whereipaddressistheIPaddressfortheConsoleDomainthatyouconfigureduringtheSystemPlatforminstallation.
Note:Thisisasecuresite.
Ifyougetacertificateerror,thenfollowtheinstructionsinyourbrowsertoinstallavalidcertificateonyourcomputer.
2.
EnteravalidUserID.
Important:Thestandardlogin/passwordsareroot/root01,admin/admin01,andcust/cust01.
Therootandadminloginshaveadvancedadministratorcapabilities,AdministeringSystemPlatform10AdministeringAvayaAuraSystemPlatformApril2010whilethecustloginhasnormaladministratorcapabilities.
Therootloginisnotallowedforgenerallogin.
Avayarecommendsthatyouchangethesedefaultpasswordsafteryourfirstlogin.
Passwordsmustbeatleastsixcharacterslong.
Avayarecommendsusingonlyalphanumericcharacters.
ThecraftloginusesASGfeature.
Ifyouareusingcraftlogin,youmusthavetheASGtoolonyourdesktoptogeneratearesponsebasedontherequestgeneratedbytheloginpage.
3.
ClickContinue.
4.
EnteravalidPassword.
5.
ClickLogOn.
ThesystemdisplaystheLicenseTermspagewhenyouloginforthefirsttime.
6.
ClickIAccepttoaccepttheenduserlicenseagreement.
ThesystemdisplaystheVirtualMachineListpageintheSystemPlatformManagementConsole.
Thevariousadministrativeoptionsarelocatedintheleftnavigationmenu.
AccessingSystemPlatformManagementConsoleAdministeringAvayaAuraSystemPlatformApril201011AccessingSystemPlatformthroughservicesportYoumustenableIPforwardingonSystemDomain(Dom-0)toaccessSystemPlatformthroughservicesport.
YoucansetIPforwardingstatusasenabledordisabledduringSystemPlatforminstallation.
Ifyousetthestatusasdisabledduringinstallation,andwanttochangethestatuslater,performthefollowingsteps:1.
ToenableIPforwarding:a.
LogontoSystemDomain(Dom-0)asadmin.
b.
Inthecommandline,typeip_forwardingenableandpressEnter.
2.
Forsecurityreasons,youshouldalwaysdisableIPforwardingafterfinishingyourtask.
PerformthefollowingtaskstodisableIPforwarding:a.
LogontoSystemDomain(Dom-0)asadmin.
b.
Inthecommandline,typeip_forwardingdisableandpressEnter.
VirtualMachineManagementTheSystemDomain(Dom-0)andConsoleDomaincomponentsofSystemPlatformandthecomponentsofvarioustemplatesinstalledontheSystemPlatformserverarecalledvirtualmachines.
Youcanviewdetailsandmanagethevirtualmachinesavailableinthesystem,includingrebootingorshuttingdownavirtualmachine.
TheVirtualMachineListpagedisplaysAdministeringSystemPlatform12AdministeringAvayaAuraSystemPlatformApril2010alistofallthevirtualmachinescurrentlyrunninginthesystem.
Whenyouclickonarespectivevirtualmachinename,thesystemdisplaysallthedetailsofthevirtualmachine,forexample,MACaddress,IPaddress,OperatingSystemandsoon.
AccesstheVirtualMachineListpageeitherbyclickingHomeorbyclickingVirtualMachineManagement>Manage.
ThesystemdisplaystheVirtualMachineListpagewhenyoulogontotheSystemPlatformManagementConsoleforthefirsttime.
VirtualMachineManagementfielddescriptionsNameDescriptionNameNameofthevirtualmachinesrunningonSystemPlatform.
VersionVersionnumberoftherespectivevirtualmachine.
IPAddressIPaddressofthevirtualmachine.
MaximumMemoryThisisadisplayonlyfield.
ThevalueissetbyAvaya,andcannotbeconfiguredbytheusers.
Theamountofphysicalmemoryfromthetotalservermemorythevirutalmachinehasallocatedinthetemplatefile.
MaximumVirtualCPUsThisisadisplayonlyfield.
CPUallocationforthevirtualmachinefromthetemplatefile.
CPUTimeTheamountofCPUtimethevirtualmachinehashadsincebootandisnotthesameasuptime.
StateCurrentstatusofthevirtualmachine.
Possiblevaluesareasfollows:RunningVirtualmachineisrunningnormally.
StartingVirtualmachineiscurrentlybootingandshouldenterarunningstatewhencomplete.
StoppingVirtualmachineisintheprocessofbeingshutdownandshouldenterstoppedstatewhencomplete.
StoppedVirtualmachinehasbeenshutdown.
RebootingVirtualmachineisintheprocessofarebootandshouldreturntorunningwhencomplete.
NoStateThevirtualmachineisnotrunningortheapplicationwatchdogisnotbeingused.
VirtualMachineManagementAdministeringAvayaAuraSystemPlatformApril201013NameDescriptionApplicationStateCurrentstatusoftheapplication(respectivevirtualmachine).
Possiblevaluesareasfollows:StartingApplicationiscurrentlybootingandshouldenterarunningstatewhencomplete.
RunningApplicationisrunningnormally.
StoppedApplicationhasbeenshutdown.
StoppingApplicationisintheprocessofbeingshutdownandshouldenterstoppedstatewhencomplete.
PartialSomeelementsoftheapplicationarerunning,butnotallelements.
TimeoutApplicationhasmissedaheartbeat,signifyingaproblemandmayresultintheConsoleDomainrebootingthevirtualmachinetocleartheproblem.
ErrorApplication'ssanitymechanismprovidedsomekindoferrormessage.
UnknownApplication'ssanitymechanismfailed.
VirtualMachineManagementbuttondescriptionsNameDescriptionRefreshRefreshestheliststhevirtualmachines.
Viewingdetailsofavirtualmachine1.
ClickVirtualMachineManagement>Manage.
Thesystemdisplaysalistofvirtualmachinecurrentlyrunningontheserver.
AdministeringSystemPlatform14AdministeringAvayaAuraSystemPlatformApril20102.
OntheVirtualMachineListpage,clickthevirtualmachineforwhichyouwanttoseethedetails.
TheVirtualMachineConfigurationParameterspagedisplaystheconfigurationdetailsforthevirtualmachine.
Rebootingavirtualmachine1.
ClickVirtualMachineManagement>Manage.
2.
OntheVirtualMachineListpage,clickthevirtualmachinewhichyouwanttoreboot.
3.
OntheVirtualMachineConfigurationParameterspage,clickReboot.
Shuttingdownavirtualmachine1.
ClickVirtualMachineManagement>Manage.
2.
Ifyouwanttostopavirtualmachine,thenclicktheentrycorrespondingtothevirtualmachineontheVirtualMachineListpage.
OntheVirtualMachineConfigurationParameterspage,clickStop.
VirtualMachineManagementAdministeringAvayaAuraSystemPlatformApril201015Note:TheConsoleDomaincanonlyberestartedandnotstopped.
IftheConsoleDomainisstopped,administrationofthesystemwillnolongerbepossible.
3.
Ifyouwanttoshutdowntheserver,dooneofthefollowingsteps:OntheVirtualMachineListpage,clickDomain-0.
OntheVirtualMachineConfigurationParameterspage,clickShutdownServer.
ClickServerManagement>ServerReboot/Shutdown.
OntheServerReboot/Shutdownpage,clickShutdownServer.
VirtualMachineConfigurationParametersfielddescriptionsNameDescriptionNameNameofthevirtualmachinesrunningonSystemPlatform.
MACAddressMachineaddressofthevirtualmachine.
IPAddressIPaddressofthevirtualmachine.
OSTypeOperatingsystemofthevirtualmachine,forexample,LinuxorWindows.
StateCurrentstatusofthevirtualmachine.
Possiblevaluesareasfollows:RunningVirtualmachineisrunningnormally.
StartingVirtualmachineiscurrentlybootingandshouldenterarunningstatewhencomplete.
StoppingVirtualmachineisintheprocessofbeingshutdownandshouldenterstoppedstatewhencomplete.
StoppedVirtualmachinehasbeenshutdown.
RebootingVirtualmachineisintheprocessofarebootandshouldreturntorunningwhencomplete.
NoStateThevirtualmachineisnotrunningortheapplicationwatchdogisnotbeingused.
AdministeringSystemPlatform16AdministeringAvayaAuraSystemPlatformApril2010NameDescriptionApplicationStateStateofvirtualmachineascommunicatedbythewatchdog.
Avirtualmachinemayincludeanapplicationwatchdog.
ThiswatchdogcommunicatesapplicationhealthbacktotheConsoleDomain.
Currentstatusoftheapplication(respectivevirtualmachine).
Possiblevaluesareasfollows:StartingVirtualmachineiscurrentlybootingandshouldenterarunningstatewhencomplete.
RunningVirtualmachineisrunningnormally.
StoppedVirtualmachinehasbeenshutdown.
StoppingVirtualmachineisintheprocessofbeingshutdownandshouldenterstoppedstatewhencomplete.
PartialSomeelementsoftheVirtualmachinearerunning,butnotallelements.
TimeoutVirtualmachinehasmissedaheartbeat,signifyingaproblemandmayresultintheConsoleDomainrebootingthevirtualmachinetocleartheproblem.
ErrorVirtualmachine'ssanitymechanismprovidedsomekindoferrormessage.
UnknownVirtualmachine'ssanitymechanismfailed.
UsedMemoryTheamountofmemorycurrentlyusedbythevirtualmachine.
MaximumMemoryThisisadisplayonlyfield.
Theamountofphysicalmemoryfromthetotalservermemorythevirtualmachinehasallocatedinthetemplatefile.
CPUTimeTheamountofCPUtimethevirtualmachinehashadsincebootandisnotthesameasuptime.
VirtualCPUsThemaximumnumberofvirtualCPUsusedbytherespectivevirtualmachine.
DomainUUIDUniqueIDofthevirtualmachine.
AutoStartStatusofautostartofavirtualmachine:ifthevirtualmachinestartsautomaticallyafterashutdownoperation.
AvailablestatusareTrue(ifautostartisset),andFalse(ifautostartisnotset).
VirtualMachineManagementAdministeringAvayaAuraSystemPlatformApril201017NameDescriptionNote:Thisvalueshouldbechangedonlyfortroubleshootingpurposes.
VirtualMachineConfigurationParametersbuttondescriptionsButtonDescriptionRebootRebootstherespectivevirtualmachine.
InthecaseofSystemDomain(Dom-0),thisrebootoperationisthesameastherebootoperationavailableintheleftnavigationpane.
WhenyoureboottheSystemPlatformserverusingtherebootoptionintheleftnavigationpane,thesystemshutsdowntheSystemPlatformserverandallthevirtualmachinesrunningonit.
Important:WhenyourebootSystemDomain(Dom-0),thesystemrebootstheSystemPlatformserverandallthevirtualmachinesrunningonit,causingpotentialservicedisruption.
WhenyourebootConsoleDomain,thesystemlosesconnectionwiththeSystemPlatformManagementConsole.
YoucanloginagainafterConsoleDomainfinishestherebootoperation.
ShutdownServerAppearsonlyifDomain-0isselectedandshutsdowntheserverandallthevirtualmachinesrunningonit.
SolutiontemplateAfterinstallingSystemPlatformyoucaninstallvarioussolutionstemplatestorunonSystemPlatform.
ThesetemplatescanbeMidsizeBusinessTemplate,ModularMessagingandsoon.
AfterinstallingthetemplatesonSystemPlatform,youcanmanagethetemplatesfromtheSystemPlatformManagementConsole.
SeeInstallingasolutiontemplatesectioninInstallingandConfiguringAvayaAuraSystemPlatformformoreinformation.
AdministeringSystemPlatform18AdministeringAvayaAuraSystemPlatformApril2010ServermanagementServerManagementoverviewYoucanperformvariousadministrativeactivitiesfortheSystemPlatformserversuchasconfiguringvarioussettingsfortheserver,viewinglogfiles,upgradingtoalatestreleaseofthesoftware,andbackingupandrestoringcurrentversionofthesoftwarebyusingtheoptionsdisplayedunderServerManagement.
PatchManagementSearchlocalandremotepatchUsetheSearchLocalandRemotePatchpagetosearchfortheavailablepatchesinthefollowingmedialocations.
Thesemediastorethevariouspatchessothatyoucandownload,upload,orinstallthemlateronSystemPlatform:HTTPSPServerSPCD/DVDSPUSBDiskLocalFileSystemVisittheAvayasupportsite(http://support.
avaya.
com)andrefertothelatestReleaseNotestofindoutthelatestpatches,andaccesstheregularupdatesandpatchesforSystemPlatformandthevarioustemplatesprovidedbyAvaya.
YoucanalsoinstallordownloadthepatchesfromtheAvayaProductLicensingandDeliverySystem(PLDS)Website(http://avaya.
plds.
com).
Downloadingpatches1.
ClickServerManagement>PatchManagement.
2.
ClickDownload/Upload.
ServermanagementAdministeringAvayaAuraSystemPlatformApril2010193.
OntheSearchLocalandRemotePatchpage,choosealocationtosearchforapatchfromthefollowingoptions:HTTPSPServerSPCD/DVDSPUSBDiskLocalFileSystem4.
IfyouselectedHTTPorSPServer,specifythePatchURL.
5.
IfyouselectedHTTP,clickConfigureProxytocreateaproxyserverusingthespecifiedURL.
RefertoSystemconfigurationonpage36.
6.
IfyouselectedLocalFileSystem,clickBrowsertolocatetheservicepackfileonyourcomputerandthenupload.
7.
ClickSearchtosearchfortherequiredpatch.
8.
ChoosethepatchandclickSelect.
InstallingpatchesImportant:IfyouplantoinstallapatchonaHighAvailabilitysystem,seeInstallingSystemPlatformpatchesonHighAvailabilitysystemsonpage21fordetailsbeforeyouinstallthepatch.
AdministeringSystemPlatform20AdministeringAvayaAuraSystemPlatformApril20101.
ClickServerManagement>PatchManagement.
2.
ClickManage.
ThePatchListpagedisplaysthelistofpatchesandthecurrentstatusofthepatches.
3.
OnthePatchListpageclickonapatchIDtoseethedetails.
4.
OnthePatchDetailpage,clickInstall.
Relatedtopics:InstallingSystemPlatformpatchesonHighAvailabilitysystemsonpage21InstallingSystemPlatformpatchesonHighAvailabilitysystemsUnlesstheReleaseNotesforthepatchstateotherwise,ifthepatchincludesaSystemDomain(Dom-0)patch,youmustinstallthepatchonboththeactiveandstandbynodes.
YoumuststopHighAvailabilitybeforeinstallingsuchpatchandtheninstallthepatchonboththeprimaryandsecondarynode.
Note:IfyouinstallthepatchbeforestoppingHighAvailability,youmustremovethepatch,stopHighAvailability,andthenreinstallthepatch.
Otherwise,youwillnotbeabletoinstallthepatchonthestandbynode.
Thestandbynodewillinaccuratelyreportthatthepatchisalreadyinstalledandpreventyoufrominstallingit.
1.
LogintoSystemPlatformManagementConsole.
2.
ClickServerManagement>Failover.
ServermanagementAdministeringAvayaAuraSystemPlatformApril2010213.
ClickStopFailoverModeandconfirmthewarningthatisdisplayed.
SystemPlatformManagementConsoleredirectstotheRebootpageandafterafewminutesredirectstotheLoginpage.
4.
LogintoSystemPlatformManagementConsoleoftheactivenodeagainandinstallthepatch.
5.
LogintoSystemPlatformManagementConsoleofthestandbynodeandinstallthepatch.
6.
OnSystemPlatformManagementConsoleoftheactivenode,clickServerManagement>Failover.
7.
ClickStartFailoverModeandconfirmthewarningthatisdisplayed.
SystemPlatformManagementConsoleredirectstotheRebootpageandafterafewminutesredirectstotheLoginpage.
Relatedtopics:Installingpatchesonpage20RemovingpatchesUnlesstheReleaseNotesforthepatchstateotherwise,ifthepatchincludesaSystemDomain(Dom-0)patch,youmustremovethepatchfromboththeactiveandstandbynodes.
YoumuststopHighAvailabilitybeforeremovingsuchpatchandthenremovethepatchonboththeprimaryandsecondarynode.
Note:IfyouremovedthepatchbeforestoppingHighAvailability,youmustinstallthepatchagain,stopHighAvailability,andthenremovethepatchfrombothmachines.
Otherwise,youwillnotbeabletoremovethepatchfromthestandbynode.
Thestandbynodewillinaccuratelyreportthatthepatchisalreadyremovedandpreventyoufromremovingit.
1.
ClickServerManagement>PatchManagement.
2.
ClickManage.
ThePatchListpagedisplaysthelistofpatchesandthecurrentstatusofthepatches.
3.
OnthePatchListpageclickonapatchthatyouwanttoremove.
AdministeringSystemPlatform22AdministeringAvayaAuraSystemPlatformApril20104.
OnthePatchDetailpage,clickDeactivate.
5.
ClickRemove.
Note:Youcancleanuptheharddiskofyoursystembyremovingapatchinstallationfilethatisnotinstalled.
Todoso,inthelaststep,clickRemovePatchFile.
SearchLocalandRemotePatchfielddescriptionsNameDescriptionSupportedPatchFileExtensionsThepatchyouareinstallingshouldmatchtheextensionsinthislist.
Forexample,*.
tar.
gz,*.
tar.
bz,*.
gz,*.
bz,*.
zip,*.
tar,*.
jar,*.
rpm,*.
patch.
ChooseMediaDisplaystheavailablelocationoptionsforsearchingapatch.
Theavailableoptionsareasfollows:HTTPFilesarelocatedinadifferentserver.
YoumustspecifythePatchURLfortheserver.
SPServerFilesarelocatedinthevsp-templatefilesystemintheSystemPlatformserver.
YoumustspecifythePatchURLfortheserver.
ServermanagementAdministeringAvayaAuraSystemPlatformApril201023NameDescriptionTip:WhenyouwanttomovefilesfromyourlaptoptotheSystemPlatformServer,youmayencountersomeerrors,asSystemDomain(Dom–0)andConsoleDomainsupportonlySCP,butmostlaptopsdonotcomewithSCPsupport.
YoucandownloadthefollowingtwoprogramstoenableSCP(SearchontheInternetaboutthedetailedprocedurestodownloadthem):Pscp.
exeWinSCPSPCD/DVDFilesarelocatedinaSystemPlatformCDorDVD.
SPUSBDiskFilesarelocatedinaUSBflashdrive.
LocalFileSystemFilesarelocatedinalocalcomputer.
PatchURLActiveonlywhenyouselectHTTPorSPServerasthemedialocation.
URLoftheserverwherethepatchfilesarelocated.
SearchLocalandRemotePatchbuttondescriptionsButtonDescriptionSearchSearchesfortheavailablepatchesinthemedialocationyouspecify.
ConfigureProxyActiveonlywhenyouselectHTTPasthemedialocationoption.
OpenstheSystemConfigurationpageandletsyouconfigureaproxybasedonyourspecifications.
Ifthepatchesarelocatedinadifferentserver(forexample,HTTP),youmayberequiredtoconfigureaproxydependingonyournetwork.
UploadUploadsapatchfilewhenLocalFileSystemisselected.
DownloadDownloadsapatchfile.
PatchlistThePatchListpagedisplaysthepatchesontheSystemPlatformserverforinstallingorremoving.
Usethispagetoviewthedetailsofpatchfilebyclickingonthefilename.
ServerManagementfielddescriptionsNameDescriptionSystemPlatformListsthepatchesavailableforSystemPlatformunderthisheading.
AdministeringSystemPlatform24AdministeringAvayaAuraSystemPlatformApril2010NameDescriptionSolutionTemplateListsthepatchesavailablefortherespectivesolutiontemplatesunderrespectivesolutiontemplateheadings.
PatchIDFilenameofapatch.
DescriptionInformationofapatch,forexample,ifthepatchisavailableforSystemPlatformthedescriptionisshownasSPpatch.
StatusShowsthestatusofapatch.
PossiblevaluesofStatusareInstalled,NotInstalled,Active,andNotActivated.
CauseRebootShowsifinstallingthepatchcausestherespectivevirtualmachinetoreboot.
PatchdetailThePatchDetailpageprovidesinformationforapatch.
TheinformationincludespatchIDorpatchfilename,theversion,thevirtualmachinetowhichthepatchbelongs,andthestatus.
PatchDetailfielddescriptionsNameDescriptionIDFilenameofthepatchfile.
VersionVersionofthepatchfile.
ProductIDNameofthevirtualmachine.
DescriptionVirtualmachinenameforwhichthepatchisapplicable.
DetailVirtualmachinenameforwhichthepatchisapplicable.
Forexample,ConsoleDomain(cdompatch).
DependencyShowsifthepatchfilehasanydependencyonanyotherfile.
ApplicableforShowsthesoftwareloadforwhichthepatchisapplicable.
WillrebootwhenShowstheaction(ifany)thatcausestheselectedpatchtorestartthevirtualmachinewhenthepatchisapplied.
RestartthisconsolewhenShowstheaction(ifany)thatcausestheselectedpatchtorestarttheSystemPlatformManagementConsole.
DisablesanitywhenShowsatwhatstagethesanityissettodisable.
StatusShowsifthepatchisavailableforinstallingoralreadyinstalled.
PatchFileShowstheURLforthepatchfile.
PatchDetailbuttondescriptionsButtonDescriptionRefreshRefreshesthePatchDetailspage.
ServermanagementAdministeringAvayaAuraSystemPlatformApril201025ButtonDescriptionPatchListOpensthePatchListpage,thatdisplaysthelistofpatches.
InstallInstallstherespectivepatch.
RemoveRemovestherespectivepatch.
RemovePatchFileRemovestherespectivepatchfile.
LogviewerUsetheLogVieweroptiontoviewvariouslogmessagessentbythesystemtothelogfiles,afterspecifyingthemessagecategoryandtheseveritylevelofthelogs.
Viewinglogfiles1.
ClickServerManagement>LogViewer.
2.
OntheLogViewerpage,dooneofthefollowingtoviewlogfiles:Selectamessageareaandaloglevelareafromthelistofoptions.
Entertexttofindalog.
AdministeringSystemPlatform26AdministeringAvayaAuraSystemPlatformApril20103.
ClickSearch.
LogViewerfielddescriptionsFieldNamesDescriptionsMessagesProvidesthreetypesoflogmessages,namelySystemLogs,EventLogs,andAuditLogssenttologfilesbythesystem.
TheSystemLogsarelogmessagesgeneratedbytheSystemPlatformoperatingsystem(syslog).
TheEventLogsarelogmessagesgeneratedbytheSystemPlatformsoftware.
TheselogsarerelatedtoprocessesandcommandsthathaverunonSystemPlatform.
TheAuditLogsarehistoryofcommandsthatusershaverunontheHistoryofcommandsthatusershaverunontheplatform.
LogLevelsThevariousloglevelsindicatetheseveritylevelofthelogsforeachcategoryoflogmessages.
FindLetsyousearchforparticularlogmessagesorloglevels.
SearchSearchesforthelogmessagesbasedonyourselectionofmessagecategoryandloglevels.
ServermanagementAdministeringAvayaAuraSystemPlatformApril201027DateandtimeconfigurationTheDate/TimeConfigurationpagedisplaysthecurrentsettings,currenttime,currenttimezone,statusofntpdandsoon.
YoucanmodifythedateandtimeintheSystemPlatformserver,afterthedateandtimewassetduringtheSystemPlatforminstallation.
Youcanalsoturnonntpdandchangethecurrenttimezone.
ConfiguringdateandtimeConfiguringthedateandtimeareoptionalandyoucanskipthesesteps.
However,youmustsetupthecorrecttimezoneforSystemPlatform.
1.
ClickServerManagement>Date/TimeConfiguration.
ThesystemdisplaystheDate/TimeConfigurationpagewithdefaultconfigurationsettings.
2.
SpecifyatimeserverandclickAddtoaddthetimeservertotheconfigurationfile.
3.
ClickPingtocheckwhetherthespecifiedtimeserver,thatis,thespecifiedhost,isreachableacrossthenetwork.
4.
ClickStartntpdtosynchronizetheSystemPlatformtimewiththeNTP(NetworkTimeProtocol)server.
AdministeringSystemPlatform28AdministeringAvayaAuraSystemPlatformApril2010Ifyouwanttostopthesynchronization,clickthesamebutton,whichthesystemnowdisplaysasStopntpd.
5.
SelectatimezoneandclickSetTimeZonetosetthetimezoneinSystemPlatform.
ThesystemsetstheselectedtimezoneontheSystemPlatformvirtualmachines(SystemDomain(Dom-0)andConsoleDomain).
Thesystemalsoupdatesthetimezoneontheothervirtualmachines.
6.
ClickQueryStatetochecktheNTP(NetworkTimeProtocol)status.
ThesystemdisplaysthestatusoftheNTPdaemononpage31ontheSystemPlatform.
ConfiguringdateandtimeusingcalendaroptionConfiguringthedateandtimeareoptionalandyoucanskipthesesteps.
However,youmustsetupthecorrecttimezoneforSystemPlatform.
1.
ClickServerManagement>Date/TimeConfiguration.
ThesystemdisplaystheDate/TimeConfigurationpagewithdefaultconfigurationsettings.
2.
ClickthecalendariconlocatednexttotheSetDateandTimebutton.
ServermanagementAdministeringAvayaAuraSystemPlatformApril201029ThesystemdisplaystheSetDateandTimepage.
3.
Selectadateinthecalendartochangethedefaultdateandsettherequireddate.
4.
Dothefollowingtosetthetime:a.
Clickthetimefieldatthebottomofthecalendar.
Thesystemdisplaysapop-upscreenshowingtimeinformation.
b.
Usetheupanddownarrowkeysbesidethehourtochangethehour,andupanddownarrowsbesidetheminutesfieldtosettheminutes.
c.
ClickOKtoacceptyourtimechanges.
5.
ClickApplytosaveyourchanges.
6.
ClickSetDateandTime.
Thesystemdisplaysawarningmessagestatingthatthisactionwillcauseafullsystemreboot.
AdministeringSystemPlatform30AdministeringAvayaAuraSystemPlatformApril20107.
ClickOKtoacceptthemessageandsettheupdateddateandtimeinthesystem.
NTPdaemonTheNTPdaemonreadsitsconfigurationfromafilenamedntp.
conf.
Thentp.
conffilecontainsatleastoneormorelinesstartingwiththekeywordserver.
Eachofthoselinesspecifyonereferencetimesource,thatis,timeserver,whichcanbeeitheranothercomputeronthenetwork,oraclockconnectedtothelocalcomputer.
ReferencetimesourcesarespecifiedusingIPaddresses,orhostnameswhichcanberesolvedbyanameserver.
NTPusesthepseudoIPaddress127.
127.
1.
0toaccessitsownsystemclock,alsoknownasthelocalclock.
YoumustnotmixthisIPaddresswith127.
0.
0.
1,whichistheIPaddressofthelocalhost,thatisthecomputer'sloopbackinterface.
Thelocalclockwillbeusedasafallbackresourceifnoothertimesourceisavailable.
Thatiswhythesystemdoesnotallowyoutoremovethelocalclock.
Removingatimeserver1.
ClickServerManagement>Date/TimeConfiguration.
ThesystemdisplaystheServerManagementpagewithdefaultconfigurationsettings.
ServermanagementAdministeringAvayaAuraSystemPlatformApril2010312.
SelectatimeserverfromthelistofaddedserversandclickRemoveTimeServertoremovetheselectedtimeserver.
Note:Thechangeswillbeeffectiveonrestartingntp.
DateTimeConfigurationfielddescriptionsNameDescriptionDate/TimeConfigurationShowsthelocaltimeandtheUTCtime.
Alsoshowsthestatusofntpd,ifitisstartedorstopped.
SetDateandTimeLetsyoueditthedateandtimesetduringSystemPlatforminstallation.
ManageTimeServersLetsyoupingatimeserverandseeitsstatusandmanagetheexistingtimeservers.
AdministeringSystemPlatform32AdministeringAvayaAuraSystemPlatformApril2010Date/TimeConfigurationbuttondescriptionsButtonDescriptionStartntpdStartsntpdtosynchronizeSystemPlatformtimewithNTP(NetworkTimeProtocol)server.
Ifntpdisstarted,thesystemnowshowsthebuttonasStopntpd.
Youcanstopntpdbyusingthisbutton.
SetDateandTimeEditsthedateandtimesetwhileinstallingSystemPlatformandsetsthenewdateandtime.
Thebuttonwillnotbeenabledifntpdisrunning.
SetTimeZoneEditsthetimezonethatyousetduringSystemPlatforminstallation.
SystemPlatformupdatesthetimezoneonSystemDomain(Domain-0),ConsoleDomain,andthevirtualmachinesrunningonSystemPlatform.
PingCheckswhetherthespecifiedtimeserver,thatis,thespecifiedhost,isreachableacrossthenetwork.
AddAddsatimeservertotheEPW(ElectronicPre-installationWorksheet)filebasedonyourspecifications.
RemoveTimeServerRemovestheselectedtimeserver.
QueryStateChecktheNTP(NetworkTimeProtocol)status.
LoggingconfigurationTheLoggingConfigurationoptionletsyouconfiguretheloglevels(whatthelogshouldcontain)forthelogswrittenbythesystemtothelogfiles.
Thedifferentloglevelsindicatetheseverityofthelogsthatthesystemwritestothelogfiles,thatis,whetheryouwanttowriteINFOorhighseveritylogs,forexample,ERROR,FATAL,andsoon.
SeeLoggingConfigurationfielddescriptionsonpage36formoreinformation.
Caution:Changethedefaultvaluesonlyfortroubleshootingpurposes.
IfyouchangetheloggerleveltoFINE,thesystemwritesmanylogfiles.
Therearechancesofpotentialperformanceissueswhenusingthislogginglevel.
So,AvayarecommendsyoutoswitchtoFINEonlytodebugaseriousissue.
ServermanagementAdministeringAvayaAuraSystemPlatformApril201033Configuringloglevelsandretentionparameters1.
ClickServerManagement>LoggingConfiguration.
AdministeringSystemPlatform34AdministeringAvayaAuraSystemPlatformApril20102.
Editthedefaultvalues,ifrequired.
3.
ClickSavetosavethesettings.
ServermanagementAdministeringAvayaAuraSystemPlatformApril201035LoggingConfigurationfielddescriptionsNameDescriptionSPLoggerSPLoggerisusedfortheSystemPlatformManagementConsolelogswhicharegeneratedbytheSystemPlatformcodebase(forexample,com.
avaya.
vsp).
3rdPartyLoggerThirdPartyLoggeristherootloggerwhichcanincludelogsfromother3rd-partycomponentsincludedintheSystemPlatformManagementConsole(forexample,com.
*orcom.
apache.
*).
vsp-all.
logContainsallthelogsgeneratedbySystemPlatformManagementConsole,irrespectiveofwhethertheyhaveeventcodesinit.
vsp-event.
logContainsalltheeventlogsgeneratedbySystemPlatformManagementConsole.
Thelogsinsp-eventareavailableinAvayacommonloggingformat.
vsp-rsyslog.
logContainssyslogmessages.
MaxBackupsMaximumnumberofbackupsorrotationstokeepforthespecifiedfile.
MaxFileSizeMaximumfilesize(forexample,forafilevsp-all.
log,oncemaxfilesizeisreacheditwillberotated/renamedtovsp-all.
log.
1SystemconfigurationUsetheSystemConfigurationpagetoconfigureproxysettings,changethecurrentkeyboardlayout,enableordisablestatisticscollection.
SeeConfiguringSystemPlatformsystemconfigurationparametersonpage36formoreinformation.
ConfiguringSystemPlatformsystemconfigurationparameters1.
ClickServerManagement>SystemConfiguration.
2.
FillinthefieldsontheSystemConfigurationpagetoconfiguretheSystemPlatformparameters.
SeeSystemconfigurationfielddescriptionsonpage37.
AdministeringSystemPlatform36AdministeringAvayaAuraSystemPlatformApril2010SystemconfigurationfielddescriptionsNameDescriptionProxyStatusSpecifieswhetheranhttpproxyshouldbeusedtoaccesstheInternet,forexample,wheninstallingtemplates,upgradingpatches,orupgradingplatform.
ProxyAddressTheaddressfortheproxyserver.
ProxyPortTheportaddressfortheproxyserver.
KeyboardLayoutDeterminesthespecifiedkeyboardlayoutforthekeyboardattachedtotheSystemPlatformserver.
CMalarmidSpecifiesalarmIDforCommunicationManager.
audixalarmidSpecifiesalarmIDforCommunicationManagerMessaging.
aesalarmidSpecifiesalarmIDforAES.
sesalarmidSpecifiesalarmIDforSES.
StatisticsCollectionIfyoudisablethisoption,thesystemstopscollectingthestatisticsdata.
ServermanagementAdministeringAvayaAuraSystemPlatformApril201037NameDescriptionNote:Ifyoustopcollectingstatistics,thesystem-generatedalarmswillbedisabledautomatically.
NetworkconfigurationNote:ThisoperationisnotsupportedwhilethesystemrunninginHighAvailabilityFailoverMode.
Toproceedtoinstall,youwillhavetostoptheHighAvailabilityFailoverMode.
RefertoSwitchbetweensimplexandhighavailabilityfailovermodesonpage54fordetails.
AfterconfiguringthenetworksettingsduringSystemPlatforminstallation,youcanviewandmodifythesesettingsfromtheNetworkConfigurationoptioninSystemPlatformManagementConsole.
WhenyoulogontotheSystemPlatformManagementConsoleafterinstallingSystemPlatform,theNetworkConfigurationpagedisplaysthesettingsthatyouconfiguredduringtheinstallation.
Whenyouinstallatemplate,theNetworkConfigurationpagedisplaysadditionalfieldsbasedontheresourcesrequestedduringtemplateinstallation,suchasbridges,dedicatedNICs,orIPconfigurationforeachoftheguestdomainscreatedforthetemplate.
ConfiguringandeditingSystemPlatformnetworksettings1.
ClickServerManagement>NetworkConfiguration.
2.
OntheNetworkConfigurationpageentervaluestoconfigurethenetworksettings.
AdministeringSystemPlatform38AdministeringAvayaAuraSystemPlatformApril2010ServermanagementAdministeringAvayaAuraSystemPlatformApril2010393.
ClickSave.
Important:AvayarecommendsyoutochangealltheIPaddresses(whereverrequired)inasingleinstancetominimizetheservicedisruption.
SystemPlatformcreatesaninternal,privatebridgethatallowsvirtualmachinestocommunicatewitheachother.
ThisprivatebridgedoesnothaveanyconnectiontoyourLAN.
Duringinstallation,SystemPlatformrunsanalgorithmtofindasetofIPaddressesthatdonotconflictwiththeaddressesconfiguredontheSystemDomainNetworkConfigurationscreen.
However,itisstillpossiblethattheaddressesselectedconflictwithotheraddressesinyournetwork.
SincethisprivatebridgeisnotconnectedtoyourLAN,thisaddressconflictcouldresultinthefailureofSystemPlatformoraninstalledtemplatetoroutepacketscorrectly.
AftertheSystemPlatforminstallation,checktheNetworkConfigurationpagetoseeiftheIPaddressesontheprivatebridgeconflictwithaddressesinthecorporatenetwork,andifthereisaconflict,changetheIPaddressesonthispage.
Keepinmindthatthetemplateyouinstallmaytakeadditionaladdressesontheprivatebridge.
TherangeofaddressesstartwithSystemDomain's(Dom-0)interfaceon"avprivate".
NetworkConfigurationfielddescriptionsNameDescriptionDefaultGatewayThedefaultgateway.
PrimaryDNSTheprimaryDNSserveraddress.
SecondaryDNSThesecondaryDNSserveraddress.
DomainSearchListThesearchlist,whichisnormallydeterminedfromthelocaldomainname.
Bydefault,itcontainsonlythelocaldomainname.
Thismaybechangedbylistingthedesireddomainsearchpathfollowingthesearchkeywordwithspacesortabsseparatingthenames.
UdomhostnameThehostnameoftheConsoleDomain.
Dom0hostnameThehostnameoftheSystemDomain(Dom-0).
PhysicalNetworkInterfaceThephysicalnetworkinterfacedetailsforeth0andeth1(andeth2incaseofHighAvailabilityFailoverisenabled).
DomainDedicatedNICApplicationswithhighnetworkortimesensitivetrafficmaybeallocatedadedicatednic.
Thismeansthevirtualmachineconnectsdirectlytoaphysicalethernetportandmayrequireaseparatecableconnectiontothecustomernetwork.
Seerespectivetemplateinstallationtopicsformoreinformation.
BridgeThebridgedetailsforthefollowing:AdministeringSystemPlatform40AdministeringAvayaAuraSystemPlatformApril2010NameDescriptionavprivateThisiscalledaprivatebridgebecauseitdoesnotuseanyEthernetinterface,soisstrictlyinternaltotheserver.
TheSystemPlatforminstallerattemptstoassignIPaddressesthatarenotinuse.
avpublicThisbridgeenslavestheEthernetdeviceassociatedwiththedefaultroute,whichisusuallyeth0,butcanvarybasedonthetypeoftheserver.
ThisbridgegenerallyprovidesaccesstotheLANforSystemPlatformelements(SystemDomain(Dom-0)andConsoleDomain)andforanyguestdomainsthatarecreatedwheninstallingatemplate.
TheIPaddressesspecifiedduringSystemPlatforminstallationareassignedtotheinterfacesthatSystemDomain(Dom-0)andConsoleDomainhaveonthisbridge.
templatebridgeThesebridgesarecreatedduringthetemplateinstallationandarespecifictothevirtualmachinesinstalled.
DomainNetworkInterfaceThedomainnetworkinterfacedetailsforSystemDomain(Dom-0)orConsoleDomainthataregroupedbydomainbasedonyourselection.
GlobalTemplateNetworkConfigurationThesetofIPaddressesandhostnamesoftheapplicationshostedonSystemPlatform.
Alsoincludesthegatewayaddressandnetworkmask.
StaticrouteconfigurationUsetheStaticRouteConfigurationpagetoaddstaticroutestoSystemDomain(Dom-0),viewdetailsofexistingstaticroutes,andeditordeleteexistingsetofstaticroutes.
ServermanagementAdministeringAvayaAuraSystemPlatformApril201041Addingastaticroute1.
ClickServerManagement>StaticRouteConfiguration.
2.
OntheStaticRouteConfigurationpage,selecttherequiredinterface.
3.
Enterthenetworkaddress.
4.
Enterthenetworkmaskaddress.
5.
Enterthegatewayaddress.
6.
ClickAddRouteaddthestaticroutewiththepresentsettings.
AdministeringSystemPlatform42AdministeringAvayaAuraSystemPlatformApril2010Deletingastaticroute1.
ClickServerManagement>StaticRouteConfiguration.
2.
ClickDeleteagainstacorrespondingstaticrouteonthepage.
Editingastaticroute1.
ClickServerManagement>StaticRouteConfiguration.
2.
CleartheAuto-NegotiationcheckboxagainstanEthernetinterfacetochange.
3.
SelectthenewEthernetconfigurationfromthedrop-downlists.
4.
ClickApplytosavethesettings.
ServermanagementAdministeringAvayaAuraSystemPlatformApril201043StaticrouteconfigurationfielddescriptionsFieldNamesDescriptionsInterfaceThebridgethroughwhichtherouteisenabled.
NetworkAddressThedestinationnetworkforwhichthestaticrouteisconfigured.
NetworkMaskThenetworkmaskforthedestinationnetworkforwhichthestaticrouteisconfigured.
GatewayThegatewayortherouterthroughwhichtheroutefunctions.
EthernetconfigurationUsetheEthernetConfigurationpageforconfiguringthesettingsofanEthernetdeviceandmodifyingtheexistingsettings.
Editingethernetconfiguration1.
ClickServerManagement>EthernetConfiguration.
TheEthernetConfigurationpagedisplaysthevaluesforalltheethernetinterfacesoftheserver,forexample,eth0,eth1,eth2,andsoon.
2.
Editthedefaultvaluesforethoandeth1.
3.
ClickSavetosaveyoursettings.
EthernetconfigurationfielddescriptionsNameDescriptionSpeedYoucansetthespeedinMB,ifAuto-Negotiationisdisabled.
Thedropdownmenushowsthesupporteddevicespeeds.
PortListstheavailabledeviceports,ifAuto-Negotiationisdisabled.
Auto-NegotiationSpecifiesifspeedautonegotiationisenabled.
Bydefaultitisenabled,butmightcausesomeproblemswithsomenetworkdevices.
Insuchcasesyoucandisablethisoption.
AdministeringSystemPlatform44AdministeringAvayaAuraSystemPlatformApril2010EthernetConfigurationbuttondescriptionsButtonDescriptionApplySavesandappliesthesettingsfortheEthernetdevice.
RefreshRefreshestheEthernetConfigurationpage.
AlarmconfigurationUsetheAlarmConfigurationoptiontoconfigurealarmsgeneratedfromthedatacollectedbythePerformanceStatisticsfeature.
Configuringalarms1.
ClickServerManagement>AlarmConfiguration.
2.
OntheAlarmConfigurationpage,editthedefaultvalues,ifrequired.
Youcanedittheparametersforthefollowingalarms:HighCPUDiskUsage(LogicalVolume)Disk(VolumeGroup)DiskreadsDiskwritesLoadAverageNetworkI/OreceivedNetworkI/OTransmitWebconsoleheapWebconsoleopenfilesWebconsolepermgenSALAgentheapSALAgentpermgenServermanagementAdministeringAvayaAuraSystemPlatformApril2010453.
SelecttheEnabledoptiontoenableanalarm.
4.
EntertheLimitValueforanalarm.
Thisisthethresholdvalue.
5.
Specifythenumberofconsecutivesamplesthatmustexceedthethresholdvaluebeforethesystemgeneratesanalarm.
6.
SpecifytheSuppressionPeriodforanalarmafterthesystemgeneratesthepreviousalarm.
7.
ClickSavetosavethesettings.
AlarmconfigurationfielddescriptionsFieldNamesDescriptionsAlarmNameofthealarm.
Thealarmsareasfollows:HighCPUAverageCPUUsageofVMDiskUsage(LogicalVolume)Percentageoflogicalvolumeused(/,/template-env,/dev/shm,/vspdata,vsp-template)Disk(VolumeGroup)Percentageofvolumegroupused(VolGroup00)DiskreadsDiskreadrate(sda)AdministeringSystemPlatform46AdministeringAvayaAuraSystemPlatformApril2010FieldNamesDescriptionsDiskWritesDiskwriterate(sda)LoadAverageLoadaverageoneachvirtualmachineNetworkI/OreceivedNetworkreceiverateforallguests(excludingdedicatedNICs)NetworkI/OTransmitNetworkreceiverateforallguests(excludingdedicatedNICs)WebconsoleheapPercentageofwebconsole(tomcat)heapmemoryinuseWebconsoleopenfilesNumberoffiledescriptorswebconsolehasopenWebconsolepermgenPercentageofwebconsole(tomcat)permgenheapusedSALAgentheapSALAgentpermgenPercentageofSALheapmemoryinuseSALAgentpermgenPercentageofSALpermgenheapusedDomain-0Memory(Committed_AS)MemoryforSystemDomain(Dom-0)udomMemory(Committed_AS)MemoryforConsoleDomainLimitValuesThethresholdvalueabovewhichthevalueispotentiallyinanalarmingstate.
ForTheperiodforwhichthevaluemustbeabovethethresholdbeforegeneratinganalarm.
SuppressionPeriodTheperiodforwhichthesamealarmisnotrepeatedaftersendingthealarmforthefirsttime.
EnableEnablestheselectedalarm.
ManagingCertificatesCertificatemanagementThecertificatemanagementfeatureallowsauserwiththerightadministrativeprivilegestoreplacethedefaultSystemPlatformManagementConsolecertificateandprivatekey.
ItalsoServermanagementAdministeringAvayaAuraSystemPlatformApril201047allowstheusertouploadandreplacetheenterpriseLDAPcertificate,iftheoptionoftransportlayersecurity(TLS)wasenabledintheEnterpriseLDAPpage.
TheusercanreplacethedefaultSystemPlatformManagementConsolecertificateandprivatekeybyselectinganewcertificatefileandanewprivatekeyonthelocalmachineanduploadingthem.
ThedefaultSystemPlatformManagementConsolecertificateisgeneratedduringSystemPlatforminstallationwiththeCNvaluesameastheConsoleDomainhostname.
Duringplatformupgrade,thecertificateisfirstbackedupandthenrestoredaftertheupgradecompletes.
Similarly,theusercanuploadandreplacetheenterpriseLDAPcertificatebyselectingnewcertificatefileonthelocalmachine,anduploadingit.
TheCertificateManagementpageshowsthefollowingdataforthecurrentSystemPlatformManagementConsoleandEnterpriseLDAPcertificate:TypeVersionExpirydateIssuerHerearethethingstonoterelatingtoacertificate:Theonlyacceptableextensionofanewcertificatefileis.
crt.
Theonlyacceptableextensionofanewprivatekeyfileis.
key.
TheoptiontouploadthekeyisonlyfortheSystemPlatformManagementConsolecertificate.
Anuploadedcertificateisvalidifitsstartdateisnotafterthecurrentdateanditsenddateisnotbeforethecurrentdate.
Anuploadedprivatekeyisvalidifitmatchestheuploadedcertificate.
Relatedtopics:EnterpriseLDAPfielddescriptionsonpage80SelectingSystemPlatformcertificate1.
ClickServerManagement>CertificateManagement.
2.
ClickSelectNewCertificateintheSystemPlatformCertificatearea.
AdministeringSystemPlatform48AdministeringAvayaAuraSystemPlatformApril2010SelectingenterpriseLDAPcertificateThistaskisenabledonlyifTLSwasclickedintheEnterpriseLDAPpage.
1.
ClickServerManagement>CertificateManagement.
2.
ClickSelectNewCertificateintheEnterpriseLDAPCertificatearea.
CertificateManagementfielddescriptionsUsetheCertificateManagementpagetoreceivenewcertificateforSystemPlatformManagementConsoleorEnterpriseLDAP.
InthecaseofSystemPlatformManagementConsole,youalsogettheprivatekey.
FielddescriptionsNameDescriptionTypeIsthetypeofthecertificateissued.
VersionIstheversionnumberofthecertificate.
ExpiryDateIstheexpirydateofthecertificate.
IssuerIstheissuingagencyofthecertificate.
ButtondescriptionsNameDescriptionSelectNewCertificateSelectsnewSystemPlatformManagementConsolecertificateandprivatekeyorEnterpriseLDAPcertificatedependingontheareawherethebuttonislocated.
LicensemanagementUsetheLicenseManagementoptiontolaunchtheWebLMLicenseManagerpageandmanagetheexistingSystemPlatformlicenses.
ServermanagementAdministeringAvayaAuraSystemPlatformApril201049Managinglicenses1.
ClickServerManagement>LicenseManagementtomanagelicensesforthesolution.
2.
ClickLaunchWebLMLicenseManagertolaunchtheWebLMLicenseManagerpage.
3.
OntheWebLMLicenseManagerpage,followtheinstructionstomanagelicenses.
FormoreinformationonmanaginglicensesthroughAvayaWebLM,seeWebLMAdministrationGuide4.
5availableintheAvayaSupportSite:http://www.
avaya.
com/support.
SALgatewaymanagementSALstandsforsecureaccesslink.
SALprovidesremoteaccessandalarmingforserviceabilityoftemplatesonSystemPlatformtoAvayaservicetechniciansand/orAvayaBusinessPartners.
YoucanmodifythealarmsettingsbyloggingintotheSALgatewayapplication.
SeeAdministeringSALonAvayaAuraSystemPlatformfordetailsonadministeringtheSALgatewayforSystemPlatform.
ManagingSALsettings1.
ClickServerManagement>SALGatewayManagement.
2.
OntheSALGatewayManagementpage,clickontheLaunchSALGatewayManagementPortallink.
3.
OntheSALGatewaypage,enteryourConsoleDomainusernameandpasswordtologin.
4.
Editthesettingsasrequired,andthenclickSave.
AdministeringSystemPlatform50AdministeringAvayaAuraSystemPlatformApril2010SALGatewayManagementbuttondescriptionsButtonDescriptionLaunchSALGatewayManagementPortalOpenstheSALGatewayManagementportalinadifferentwebbrowser.
Youmustprovideavalidcertificatedetailstoaccesstheportal.
SystemPlatformFailoverSystemPlatformHighAvailabilityFailoveroverviewTheSystemPlatformHighAvailabilityFailoverisanoptionalfeature.
Thisfeatureoffersthefollowingcapabilities:NodescoresSystemPlatformHighAvailabilityFailoverusesnodescoretocomputetheabilityofeverymachinetoruntheresourcesanddecideonwhichnoderesourcesshouldberunningforeachparticularsituation.
Inthecasethereisnoissuewiththesystemandresourcescouldberunningonanynode,bothmachineshavethesamescore.
ThusSystemPlatformusesatermof"preferrednode"–machinethatissupposedtoruntheresourcesinthecasethereisnoissuewiththesystem.
Thispreferrednodehasasmallscorebenefit.
Soifbothmachinesarebootedupatthesametime,thisnodewillrunresources.
Noauto-failbackSystemPlatformHighAvailabilityFailoverdoesnotuseafeaturecalledauto-failbackthatmigratesresourcesbacktothepreferrednodeincaseitreappearsagainandresourcesarecurrentlyrunningonthestandbynode.
Thisisbecausethereisaserviceimpacttoswitchingserversandifbothserversarehealthythenrunningonthepreferrednodeoffersnoincreasedbenefit.
Iftheuserwantstomigrateresourcesbacktothepreferrednodeafterafailoveroraswitchover,theusercandosousingtheManualSwitchoveroptioninFailovermenuduringthebestsuitabletime.
Note:Remotereboot(alsocalledSTONITH)isdisabledbydefaultandnotsupportedinthecurrentversionofSystemPlatformHighAvailability.
RemoterebootshouldnotbeconfiguredwhenusingHighAvailability.
Expectedfailover/switchovertimesSystemPlatformHighAvailabilityFailoveruses30secondsasatimeoutintervaloflostpingrepliesuponwhichstandbynodewilldeclareactivenodeasdead(althoughitcanbenotaccessible,notrunningorblocked).
Whenthatperiodexpires,thestandbynodeexecutesaServermanagementAdministeringAvayaAuraSystemPlatformApril201051takeover(thatis,startsresources).
NotethatSystemPlatformdoesnotprovideanywebinterfacetomodifythisinterval.
Incaseofmanualswitchoverorincasethereissomestateofthesystemthatinitiatespreemptivefailover,thetotaltimebetweenstartofthecommandandtimewhenallresourcesarerunningonthestandbynodeincludesgracefulshutdownofallresourcesandstartofalltheresources:stopofresources-upto5minutesstartofresources-upto5minutesresultinglongestswitchovertime-upto10minutesIncaseoffailoverduetototalfailureoftheactivenode,thetotaltimebetweenthestartoftheoutageandtimewhenallresourcesarerunningonthestandbynodeincludesdetectionintervaltimeoutandstartofalltheresources:detectactivenodefailure-30secondsstartofresources-upto5minutesresultinglongestswitchovertime-upto5.
5minutesNote:Switchovertimewillvarydependingonhardwareinuseandthespecifictemplateinstalledonthesystem.
Templateswithmorevirtualmachineswilltakeslightlylongertoswitchoverduetomultiplevirtualmachinesbootingsimultaneously.
SeeHowSystemPlatformHighAvailabilityFailoverworksformoreinformation.
PrerequisitesTheprerequisitesforconfiguringSystemPlatformHighAvailabilityFailoverareasfollows:Twoserverswithexactlythesameconfiguration.
HardwaresupportedbySystemPlatform.
TheserversmusthaveaspareGigabitnetworkinterfacetobeusedasacrossoverconnectiondedicatedexclusivelytoHighAvailabilityFailoverservices(heartbeathealthchecksandDRBD(DistributedReplicatedBlockDevice)syncpropagation)Boththeserversmustbeinthesamesubnet.
Boththeserversincloseproximity,approximately10meters.
ThesameversionofSystemPlatforminstalledonboththeactiveandstandbynodes.
Boththeserversmustbeconnectedwithagigabit-crossovercableontheportsdetectedaseth2onoperatingsystem.
Ifyouwanttoinstallatemplateonapreferrednode,youmustdoitbeforestartingHA.
Thestandbyservercannothavelessmemory,numberofprocessors,andtotalorfreediskspacethantheprimaryserver.
AdministeringSystemPlatform52AdministeringAvayaAuraSystemPlatformApril2010Thestandbyservercannothaveinstalledtemplate.
Ifpresent,thefailoverconfigurationwillfailwithanerror.
IfyouareusingthebundledSystemPlatforminstallation(withsolutiontemplate),disabletemplateinstallationonthestandbyserver.
DefaultnetworkgatewayistheSystemPlatformHighAvailabilityFailoverheartbeat'spingtargetanditisnotaconfigurableparameter.
EnsurethatyournetworkgatewayrepliestoICMPrequestscomingfromtheSystemPlatformnodes.
Heartbeatsetspayloadwithnode-identifyingdataandchecksthatthedatainrepliedpacketpayloadiscorrect.
ThesizeoftheseICMPpingpacketsisintherangeof132-256Bytes.
Ifyouapplyfirewallrulesagainstthepingservice(atthegateway),specificallypacketsizerestriction,youmustallowforpacketsizesupto256bytes.
ConfiguringSystemPlatformHighAvailabilityFailover1.
LogontoSystemPlatformManagementConsoleontheactiveserverasanadvancedadministrator.
2.
ClickServerManagement>FailovertodisplaytheFailoverpage.
TheFailoverpagedisplaysthecurrentstatusoffailover.
3.
Completethefieldsonthepage.
SeeConfigureFailoverfielddescriptionsonpage54formoreinformation.
4.
ClickCreatetoconfigurefailover.
5.
ClickStartFailoveronlyafterthesystemcompletesthefailovercreationoperation.
TheStartFailoveroperationblocksalltheconnectionstotheSystemPlatformManagementConsoleandthesystemredirectsyoutoapagethatinformsyouabouttherestartofConsoleDomain.
WhentheSystemPlatformManagementConsoleisaccessibleagain,thesystemredirectsyoutotheloginpageautomatically.
Youmustloginagainatthisstage.
6.
LogontoSystemPlatformManagementConsole7.
ClickServerManagement>Failover.
ServermanagementAdministeringAvayaAuraSystemPlatformApril201053YoucancheckthestatusofthefailovercomponentsintheFailoverpageandensurethatDRDB(DistributedReplicatedBlockDevice)issynchronizingtheharddisksofthetwoservers.
Tip:Duringthedisksynchronizationprocess,youcanincreaseordecreasethespeedofthesyncwithasliderbarprovidedontheconsole.
Thedefaultvalueofthisrateis30MB.
Ifyousetthevaluetoohigh,itmayaffecttheperformanceofthevirtualmachinesrunningontheactiveserver.
ConfigureFailoverfielddescriptionsNameDescriptionRemotecdomIPaddressThesecondaryConsoleDomainIPaddress.
RemotecdomusernameUsernameforConsoleDomain.
RemotecdompasswordThepasswordforConsoleDomain.
PrimarynetworkinterfaceTherequiredEthernetNIC.
CrossovernetworkinterfaceTherequiredEthernetNIC.
AutomaticswitchingfromtheactiveservertothestandbyserverWhentheSystemPlatformserverencountersmissingheartbeatchecks,thestandbySystemPlatformserverbecomestheactiveSystemPlatformserver.
Thesystemshutsdowntheoriginalactiveserver,andrebootsallthevirtualapplicationsonthisnewactiveserver.
Thesystemperformsthefollowing:Detectsproblemsoftheactive(primary)nodebymissingheartbeatchecksduringaspecifiedperiodoftime.
Assignsthesecondarynodeasanewprimarynode.
SetstheDistributedReplicatedBlockDevice(DRBD)devicesasprimaryonthenewactivenode.
Bootsthevirtualmachinesonthenewactivenode.
SwitchbetweensimplexandhighavailabilityfailovermodesSwitchingtohighavailabilityfailovermodeSystemPlatformcanbeextendedfromsimplexmodetohighavailabilityfailovermodeduringsysteminstallationoranytimelater.
OnceyouhaveinstalledanewmachinewithSystemPlatformofthesameversionwithoutatemplateandthemachinehasatleastthesame(orAdministeringSystemPlatform54AdministeringAvayaAuraSystemPlatformApril2010better)configurationsuchasthenumberofprocessorsanddiskspace,youarereadytoproceed.
SwitchingtosimplexmodeTherearetwovariantstoswitchingfromhighavailabilityfailovermode:Stoppinghighavailabilityfailovermode:Ifyouwanttostopthehighavailabilityfailoverandswitchtothesimplexmode,youcandosoassoonasthereisnodisksynchronizationinprogressorthediscsynchronizationisnotpaused.
Thestoppageofhighavailabilityfailovercouldleadtocorruptionofthefilesystemofthestandbyconsoledomain,iftheconditionjustmentionedisnotsatisfied.
Removingfailoverconfiguration:Ifyouwanttoremovethefailoverconfigurationpermanently,youwillusethisvariant.
SwitchingtosimplexmodefortemplateconfigurationSystemPlatformdoesnotsupporttemplateinstall,upgradeordeleteoperationswhileitrunsinthehighavailabilityfailovermode.
Youwillseeawarningmessageontemplatepagesandnotbeabletoexecuteanyoftheseoperations.
Toproceedwithtemplateinstall,upgradeordelete,youhavetostopthehighavailabilityfailovermodefirst.
SwitchingtohighavailabilitymodeaftertemplateconfigurationOnceyouhavefinishedwithtemplateoperation,youcanstartthehighavailabilityfailovermodefromtheFailoverpage.
SwitchingtohighavailabilityfailovermodePrerequisitesThesystemisconfiguredwithhighavailabilityfailover.
RefertoConfiguringSystemPlatformHighAvailabilityFailoveronpage53.
1.
ClickServerManagement>Failover.
2.
ClickStartFailover.
SystemPlatformManagementConsolewillredirecttotherebootpage.
Afteracoupleofminutes,SystemPlatformManagementConsolewillredirecttotheloginpage.
3.
LogintotheSystemPlatformManagementConsole.
4.
ClickServerManagement>Failoverandcheckthediscsynchronizationprogress.
Thisoperationwillsynchronizealltherequiredconfigurationsettingsfrompreferrednodetothestandbynodesothatitwillbereadyfortakeoverofresourceswhenrequired.
Pleasenotethatthisoperationwillrestartconsoledomainandalltemplatevirtualmachines.
ServermanagementAdministeringAvayaAuraSystemPlatformApril201055Stoppinghighavailabilityfailovermode1.
ClickServerManagement>Failover.
2.
ClickStopFailover.
SystemPlatformManagementConsolewillredirecttorebootpage.
Afteracoupleofminutes,SystemPlatformManagementConsoleshouldredirectintotheloginpage.
3.
LogintoSystemPlatformManagementConsole.
4.
ClickServerManagement>Failoverandcheckthestatusofthehighavailabilityfailover.
Nowthesystemisnotpropagatingchangesfromthepreferrednodetothestandbynode.
Howeverthehighavailabilityfailovermodeisstillconfiguredsothatyoucanstartitanytimelater.
Thetemplateonthestandbynodeisremovedduringthisoperation.
YoucannowaccessstandbySystemPlatformManagementConsoleusingitsIPaddress(thatwasprovidedduringtheconfigurationofhighavailabilityfailover).
Pleasenotethatthisoperationwillrestarttheconsoledomainandalltemplatevirtualmachines.
Youcancompletelyremovethenodefromthehighavailabilityfailover.
RefertoRemovingfailoverconfigurationonpage56onhowtoproceed.
Removingfailoverconfiguration1.
ClickServerManagement>Failover.
2.
ClickRemoveFailover.
Note:Thisoperationleavesthestandbyconsoledomainininconsistentstateandthisnodecannotbeagainusedtoconfigurehighavailabilityfailoverwithoutreinstallingit.
SwitchingtosimplexmodefortemplateconfigurationNote:Ifyoustopthehighavailabilityfailovermode,SystemPlatformremovesthetemplate(ifinstalled)fromthestandbynode.
EverytemplateoperationcanonlybeexecutedontheAdministeringSystemPlatform56AdministeringAvayaAuraSystemPlatformApril2010preferrednode.
Youshouldnottrytoinstallatemplateonthestandbynodeasthispreventsstartingthehighavailabilityfailovermodeafterwards.
1.
ClickServerManagement>Failover.
2.
ClickStopFailover.
SystemPlatformManagementConsolewillredirecttorebootpage.
Afteracoupleofminutes,SystemPlatformManagementConsoleshouldredirecttotheloginpage.
3.
LogintoSystemPlatformManagementConsole.
4.
ClickTemplateInstall/Upgradeandproceedwithtemplateoperation.
NextstepsStartthehighavailabilityfailovermodefromtheFailoverpage.
RefertoSwitchingtohighavailabilityfailovermodeaftertemplateconfigurationonpage57fordetails.
SwitchingtohighavailabilityfailovermodeaftertemplateconfigurationRefertoSwitchingtohighavailabilityfailovermodeonpage55fordetailsonhowtoproceed.
PerformancestatisticsUsethePerformanceStatisticsoptiontoviewthestatusofthehealthandusageofthesystem.
ThePerformanceStatisticspageletsyouviewtheperformancestatisticsSystemPlatformandthehostedvirtualmachines.
ViewingperformancestatisticsThePerformanceStatisticspageprovidesyouastatusofthehealthandusageofthesystem.
UsethispagetoviewtheSystemPlatformperformancestatisticsandthehostedvirtualmachines.
1.
ClickServerManagement>PerformanceStatistics.
ServermanagementAdministeringAvayaAuraSystemPlatformApril2010572.
OntheServerManagementpage,clicktheAllStatisticscheckboxtogenerateagraphforallrecordedstatistics.
3.
CleartheAllStatisticscheckbox,andselectthetypeofgraphfromtheTypedropdownmenu.
ThenselecttherequireddomainfromthelistintheDomainsbox.
4.
Specifythedateandtimefortheperiodyouwanttoviewthereportsfrom.
5.
ClickGeneratetogeneratetheperformancegraphforthesystem.
Generatingagraph1.
ClickServerManagement>PerformanceStatistics.
2.
OnthePerformanceStatisticspage,selecttherequireddetails.
3.
ClickGenerate.
Exportingcollecteddata1.
ClickServerManagement>PerformanceStatistics.
2.
OnthePerformanceStatisticspage,selecttherequireddetailsandgenerateagraph.
AdministeringSystemPlatform58AdministeringAvayaAuraSystemPlatformApril20103.
ClickDownloadCSVFileforthedatayouwanttodownload.
4.
ClickSaveandspecifythelocationtodownloadthedata.
PerformancestatisticsfielddescriptionsFieldNamesDescriptionsAllStatisticsIfyouselectthisoption,thesystemdisplaysagraphforalltherecordedstatistics.
TypeAppearsonlyiftheAllStatisticscheckboxiscleared.
Letsyouspecifythetypeofstatisticsyouwanttodisplayfromalistofoptions.
DomainsAppearsonlyiftheAllStatisticscheckboxiscleared.
Letsyouselectthevirtualmachinesforwhichyouwanttogeneratethestatistics,forexample,SystemDomain(Dom-0)andConsoleDomain.
DateandTimeLetsyouspecifythedateandtimeforgeneratingperformancestatisticsfromthreeoptionsasfollows:PredefinedValues:Letsyouspecifytherangeofdays.
Last:Letsyouspecifythedayortime.
Between:Letsyouspecifythedaterange.
GenerateGeneratestheperformancestatisticsofthesystembasedonyourspecifications.
EjectCDorDVDTheCDorDVDusedforinstallingSystemPlatformandvirtualmachinesejectsautomaticallyaftersuccessfullycompletingtheinstallationoranupgrade.
However,ifthereisanyproblemduringinstallationorupgrade,theCDorDVDremainslockedinthedrive.
YoucanusetheEjectCD/DVDoptiontoforceopenthedriveandtakeouttheCDorDVD.
ThedataintheCDorDVDreceivesnodamagebecauseofforceopeningthedrive.
EjectingtheCDorDVD1.
ClickServerManagement>EjectCD/DVD.
2.
ClickEjectontheEjectCD/DVDpagetoejecttheCDorDVD.
ServermanagementAdministeringAvayaAuraSystemPlatformApril201059FileManagerSystemPlatformstoresthesolutiontemplatefilesandplatformupgradeimagesinadirectoryinthesystem.
TheFileManageroptionenablesyoutocleanuptheolderversionsofthesolutiontemplatefilesandplatformupgradeimages.
However,youcannotdeletethefilesforthecurrentlyinstalledsolutiontemplates.
Deletingafolder1.
ClickServerManagement>FileManager.
2.
Selectthefolderfilethatyouwanttodelete.
3.
ClickDelete.
BackingupSystemPlatformSystemPlatformbackupYoucanbackupconfigurationinformationforSystemPlatformandthesolutiontemplate(allvirtualmachines).
Setsofdataarebackedupandcombinedintoalargerbackuparchive.
Backupsetsarerelateddataitemsthatneedtobebackedup.
Whenyouperformabackup,thesystemexecutesallthebackupsets.
Allthebackupsetsmustsucceedtoproduceabackuparchive.
Ifanyofthebackupsetsfail,thenthesystemremovesthebackuparchive.
Theamountofdatabackedupisdependentonthespecificsolutiontemplate.
Thesystemstoresthebackupdatainthe/vspdata/backupdirectoryinConsoleDomain.
Thisisadefaultlocation.
Duringanupgrade,thesystemdoesnotupgradethe/vspdatafolder,sothatyoucanrestorethedata,ifrequired.
YoucanchangethislocationandbackuptheSystemPlatformbackuparchivestoadifferentdirectoryinSystemPlatformorinanexternalserver.
Youcanalsosendthebackupdatatoanexternale-mailaddressifthefilesizeisnotlargerthan10MB.
Ifabackupfails,thesystemautomaticallyredirectsyoutotheBackuppageafterloginanddisplaysthefollowingmessage:LastBackupFailed.
Thesystemcontinuestodisplaythemessageuntilabackupissuccessful.
Note:Itisnottheaimofthebackupfeaturetoprovideamechanismtore-enableafailedHighAvailabilitynodebacktoHighAvailabilityconfiguration.
FollowtheinstructionsgiveninthisAdministeringSystemPlatform60AdministeringAvayaAuraSystemPlatformApril2010documentonhowtore-enablefailedHighAvailabilitynodebacktoHighAvailabilityconfiguration.
RestoringusingSystemPlatformManagementConsoleabackuparchiveproducedwithHighAvailabilityactiveresultsinafailure.
Toworkaroundthisissue,takebackupwithHighAvailabilitydisabled.
Backingupdata1.
ClickServerManagement>Backup/Restore.
2.
ClickBackup.
3.
OntheBackuppage,selecttheBackupNowoptiontostartthebackupoperationimmediately.
Important:Thebackupfilesizecanreach3GB.
Ensurethatyouhavethatmuchoffreespaceonthelocationyouarekeepingyourbackuparchive.
4.
Specifywheretosendthebackupfilesfromthefollowingbackupmethodoptions.
LocalSFTPEmailYoucanspecifyaremotedestinationtowhichthearchivewillbesentbychangingthebackupmethod.
SeeTransferringtheBackupArchivestoaremotedestinationonpage63formoreinformation.
5.
ClickBackupNow.
ServermanagementAdministeringAvayaAuraSystemPlatformApril201061Schedulingabackup1.
ClickServerManagement>Backup/Restore.
2.
ClickBackup.
3.
OntheBackuppage,selecttheScheduleBackupoptiontoschedulethebackupoperationlater.
4.
Specifythefollowing:FrequencyStartTimeArchiveskeptonserver.
BackupMethodYoucanspecifyaremotedestinationtowhichthearchivewillbesentbychangingthebackupmethod.
SeeTransferringtheBackupArchivestoaremotedestinationonpage63formoreinformation.
5.
ClickScheduleBackup.
AdministeringSystemPlatform62AdministeringAvayaAuraSystemPlatformApril2010BackupfielddescriptionsFieldNamesDescriptionsBackupMethodLetsyouspecifyalocationtosendthebackupfilesfromthefollowingoptions:LocalThefilesarestoredonSystemPlatformunder/vspdata/backup/archivedirectory.
SFTPAcopyofthefileisstoredinthedesignatedSFTPhostserver.
IntheSFTPbox,enterthefollowinginformation:Hostname,directory,username,andpassword.
EmailAcopyofthebackuparchiveissentbyane-mailtoarecipient.
Inthee-mailbox,enterthee-mailaddressandtheserveraddressoftherecipient.
BackupNowLaunchesthebackupoperation.
ScheduleBackupfielddescriptionsFieldNamesDescriptionsDailyYoucanschedulesthebackupstorundaily.
WeeklyYoucanselectthedayoftheweektorunbackups.
MonthlyYoucanspecifyadayinthemonthtorunbackups.
StartTimeThestarttimeforthebackup.
ArchiveskeptontheserverThenumberofbackuparchivestostoreonSystemPlatform.
Thedefaultis10.
BackupMethodYoucanspecifyalocationtosendthebackupfilesfromtheavailableoptions.
ScheduleBackupYoucanusethisoptiontoschedulethebackupprocess.
CancelScheduleYoucanusethisoptiontocancelanexistingbackupschedule.
TransferringtheBackupArchivestoaremotedestinationYoucansendthebackuparchivetoamailaddressortoaremoteserverbySFTPwithusingtheBackupMethodoption.
ServermanagementAdministeringAvayaAuraSystemPlatformApril2010631.
Tosendthearchivebyemail:a.
SelecttheEmailoptionastheBackupMethod.
b.
SpecifytheEmailAddressandtheMailServer.
2.
TosendthearchivetoaremoteserverbySFTP:a.
SelectSFTPoptionastheBackupMethod.
b.
SpecifytheSFTPHostname(orIPAddress),Directorytowhichthearchivewillbesentandtheusernameandpasswordtologintheserver.
Viewingbackuphistory1.
ClickServerManagement>Backup/Restore.
2.
ClickBackup.
3.
OntheBackuppage,selecttheBackupHistoryoption.
Thesystemdisplaysthelast10backupsexecutedwiththeirdatesandthestatus.
RestoringSystemPlatformRestoringbackedupconfigurationinformationUsethisproceduretorestorebackedupconfigurationinformationforSystemPlatformandtheSolutionTemplate(allvirtualmachines).
Note:TherestoreoperationdoesnotrestoretheHighAvailabilityconfigurationfromthebackupfile.
Itisnottheaimoftherestorefeaturetore-enablethefailedHighAvailabilitynodebacktoHighAvailabilityconfiguration.
Followtheinstructionsgiveninthisdocumentonhowtore-enablethefailedHighAvailabilitynodebacktoHighAvailabilityconfiguration.
AvayarecommendsrestoringbackupbeforeconfiguringandstartingtheHighAvailabilitymode.
1.
ClickServerManagement>Backup/Restore.
2.
ClickRestore.
AdministeringSystemPlatform64AdministeringAvayaAuraSystemPlatformApril2010TheRestorepagedisplaysalistofpreviouslybackeduparchivesontheSystemPlatformsystem.
3.
Selectanarchivefilefromthelist,andthenclickRestoretorestorefromtheselectedarchive.
RestoringanarchiverequirestheSystemPlatformManagementConsoletorestart,soyoumustloginagainwhentherestoreoperationiscompleted.
RestorefielddescriptionsFieldNamesDescriptionsRestoreArchiveListsthelocationsfromwhereyoucanselecttorestorethebackedupdata.
Alsodisplaysdetailsofthearchiveddataincludingthefilenameandcreationdate.
LocalThelistofarchivelocatedintheSPServer(Defaultlocation).
SFTPRestorearchivelocatedinaremoteserver.
Youmustspecifythefollowing:SFTPHostnameHostnameorIPaddressoftheremoteserverSFTPDirectoryPathwherethearchiveislocatedontheremoteserver.
SFTPUsernameUsernamefortheremoteserver.
SFTPPasswordPasswordfortheremoteserverSearchButtontosearchthelistofarchivespresentinthespecifieddirectoryoftheremoteserver.
ClearSearchResultButtontoclearthelistofarchivesfoundonaremoteserverafteraSFTPsearch.
UploadRestorearchivelocatedinyourcomputer.
RestoreHistoryDisplaystherestorehistoryforlasttenrestores.
Ifanerroroccurredduringthelastrestore,thesystemdirectsyoutothispageafterloginandcontinuestodisplayanerrormessagetillasuccessfulrestoreaction.
ServermanagementAdministeringAvayaAuraSystemPlatformApril201065Viewingrestorehistory1.
ClickServerManagement>Backup/Restore.
2.
ClickRestore.
3.
OntheRestorepage,selecttheRestoreHistoryoption.
Thesystemdisplaysthelast10restoreoperationexecutedwiththeirdatesandthestatus.
ShutdownorreboottheSystemPlatformserverUsetheServerReboot/ShutdownoptiontorebootorshutdowntheSystemPlatformserver.
WhenyourebootorshutdowntheSystemPlatformserver,thesystemrebootsorshutsdownallthevirtualmachinesrunningonSystemPlatform,causingpotentialservicedisruption.
Note:IfyouhaveenabledSystemPlatformHighAvailabilityandyouhavetoshutdownorrebootthesystem,checkthesectionShutdownthesystemrunninginHighAvailabilitymodefordetails.
Relatedtopics:ShutdownthesystemrunninginHighAvailabilitymodeonpage69RebootingtheSystemPlatformServer1.
ClickServerManagement>ServerReboot/Shutdown.
Note:OnlyanAdvancedAdministratorusercanreboottheserver.
2.
OntheServerReboot/Shutdownpage,clickReboot.
AdministeringSystemPlatform66AdministeringAvayaAuraSystemPlatformApril2010ShuttingdowntheSystemPlatformServer1.
ClickServerManagement>ServerReboot/Shutdown.
Note:OnlyanAdvancedAdministratorusercanshutdowntheserver.
2.
OntheServerReboot/Shutdownpage,clickShutdownServer,ServerRebootShutdownfielddescriptionsNameDescriptionNameNameoftheapplicationbeingshutdown.
ThisisalwaysSystemDomain(Domain-0).
MACAddressMachineaddressofthevirtualmachine.
IPAddressIPaddressoftheSystemPlatformserver.
OSTypeOperatingsystemoftheSystemPlatformserver,forexample,Linux.
StateCurrentstatusofthevirtualmachine.
Possiblevaluesareasfollows:RunningVirtualmachineisrunningnormally.
StartingVirtualmachineiscurrentlybootingandshouldenterarunningstatewhencomplete.
StoppingVirtualmachineisintheprocessofbeingshutdownandshouldenterstoppedstatewhencomplete.
StoppedVirtualmachinehasbeenshutdown.
RebootingVirtualmachineisintheprocessofarebootandshouldreturntorunningwhencomplete.
NoStateThevirtualmachineisnotrunningortheapplicationwatchdogisnotbeingused.
ServermanagementAdministeringAvayaAuraSystemPlatformApril201067NameDescriptionApplicationStateCurrentstatusoftheapplication(respectivevirtualmachine).
Possiblevaluesareasfollows:StartingApplicationiscurrentlybootingandshouldenterarunningstatewhencomplete.
RunningApplicationisrunningnormally.
StoppedApplicationhasbeenshutdown.
StoppingApplicationisintheprocessofbeingshutdownandshouldenterstoppedstatewhencomplete.
PartialSomeelementsoftheapplicationarerunning,butnotallelements.
TimeoutApplicationhasmissedaheartbeat,signifyingaproblemandmayresultintheConsoleDomainrebootingthevirtualmachinetocleartheproblem.
ErrorApplication'ssanitymechanismprovidedsomekindoferrormessage.
UnknownApplication'ssanitymechanismfailed.
UsedMemoryTheamountofmemorycurrentlyusedbythevirtualmachine.
MaximumMemoryThisisadisplayonlyfield.
Theamountofphysicalmemoryfromthetotalservermemorythevirtualmachinehasallocatedinthetemplatefile.
CPUTimeTheamountofCPUtimethevirtualmachinehashadsincebootandisnotthesameasuptime.
VirtualCPUsThemaximumnumberofvirtualCPUsthatcanrunonSystemPlatformserver.
DomainUUIDUniqueIDofthevirtualmachine.
AutoStartStatusofautostart-showsiftheSystemPlatformserverstartsautomaticallyafterashutdownoperation.
AvailablestatusareTrue(ifautostartisset),andFalse(ifautostartisnotset).
AdministeringSystemPlatform68AdministeringAvayaAuraSystemPlatformApril2010ServerReboot/ShutdownbuttondescriptionsButtonDescriptionRebootRebootstheSystemPlatformserverandallthevirtualmachinesrunningonit.
ShutdownServerShutsdowntheSystemPlatformserverandallthevirtualmachinesrunningonit.
ShutdownthesystemrunninginHighAvailabilitymodeYoucanshutdownthesystemrunninginHighAvailabilitymodebyoneofthefollowingmethods:StoppingHighAvailabilityandshuttingdownbothofnodesseparatelyShuttingdownbothnodesusingCLIShuttingdownactiveserverfollowedbystandbyserverusingSystemPlatformManagementConsoleStoppingHighAvailabilityandshuttingdownbothserversseparatelyThisisthepreferredmethodofpreparingthesystemforshutdowntoensurethatthesystemissplitintotwoindependentservers.
Thereisnochanceofdatalossandthetimingoftheoperationsisnotthatcriticalasusingothermethods.
Usethismethodunlessthereisrealneedtoshutdownthesystemveryfast.
1.
LogintoSystemPlatformManagementConsole.
2.
Checkthatthesystemisreadytobeshutdowncorrectly.
SeeCheckingcorrectsystemstateusingSystemPlatformManagementConsoleonpage70.
3.
StopHighAvailability.
SeeStoppinghighavailabilityfailovermode.
4.
LogintoSystemPlatformManagementConsoleonthestandbyserver.
5.
ShutdownthestandbyserverusingSystemPlatformManagementConsole.
SeeShuttingdownaserverusingSystemPlatformManagementConsoleonpage70.
ServermanagementAdministeringAvayaAuraSystemPlatformApril2010696.
LogintoSystemPlatformManagementConsoleonactiveserver.
7.
ShutdowntheactiveserverusingSystemPlatformManagementConsole.
SeeShuttingdownaserverusingSystemPlatformManagementConsoleonpage70.
CheckingcorrectsystemstateusingSystemPlatformManagementConsoleUsetheFailoverpagetoidentifythepossibleissueofthesystem.
1.
LogintoSystemPlatformManagementConsoleasadmin.
2.
ClickServerManagement>Failover.
3.
CheckthattheManualSwitchoverbuttonisenabledtoclick.
Note:IftheManualSwitchoverbuttonisnotenabledtoclick,checkthedetailedtableontheFailoverpagetoidentifytheissuethatispreventingmanualswitchoverandfixit.
Important:Donotproceedtoshutdownwithoutfixingtheissue.
ShuttingdownaserverusingSystemPlatformManagementConsole1.
LogintoSystemPlatformManagementConsoleasadmin.
2.
ClickServerManagement>ServerReboot/Shutdown.
3.
ClickShutdownServer.
4.
Inthewarningthatappearstoconfirmshutdown,clickOK.
TheShutdownpageappears.
ShuttingdownbothserversusingCLI1.
LogintocurrentlyactiveSystemPlatformManagementConsoleasadmin2.
Checkthatthesystemisreadytoshutdowncorrectly.
SeeCheckingsystemisincorrectstateusingCLIonpage71.
AdministeringSystemPlatform70AdministeringAvayaAuraSystemPlatformApril20103.
StoptheCRMonthestandbynodebytypingvsphastop-standby-crm4.
StoptheCRMontheactivenodebytypingsudoserviceheartbeatstop5.
LogintoSystemPlatformManagementConsoleonthestandbyserverasadmin.
6.
Typesu7.
Typeshutdownnow8.
LogintoSystemPlatformManagementConsoleontheactiveserverasadmin.
9.
Typesu10.
TypeshutdownnowCheckingsystemisincorrectstateusingCLIUsetheSystemPlatformHighAvailabilitystatuscommandtoidentifythepossibleissueofthesystem.
1.
LogintothecurrentlyactiveSystemPlatformManagementConsoleasadmin.
2.
Ensurethatthesystemyouarecurrentlyloggedinisactivebytyping:vsphastatus|grep'Activenode'Theoutputmayappearasshownnext:Activenode:Local3.
Typevsphastatus-sTheoutputmayappearasshownnext:$vsphastatus-sStatusofHighAvailabilityontheVSPSummary-------Systemstatus:StartedLocalCRMrunning:YesRemoteCRMrunning:YesRemotepubliclink:upRemotecrossoverlink:up4.
Intheoutputofstep3,checkthatbothlocalandremoteCRMprocessesarerunning.
Herearethelinesyoumustcheck:LocalCRMrunning:YesServermanagementAdministeringAvayaAuraSystemPlatformApril201071RemoteCRMrunning:Yes5.
Intheoutputofstep3,checkthatbothremotenetworkinterfacesareup.
Herearethelinesyoumustcheck:Remotepubliclink:upRemotecrossoverlink:up6.
EnsurethatallDRBDresourcesareconnectedandfullysynchronizedbytypingvsphastatusTheoutputmayappearasshownnext:DRBDDiskSyncing0:Domain00ConnectedPrimary/SecondaryUpToDate/UpToDateC1:udom0ConnectedPrimary/SecondaryUpToDate/UpToDateC2:udom1ConnectedPrimary/SecondaryUpToDate/UpToDateC3:udom2ConnectedPrimary/SecondaryUpToDate/UpToDateCImportant:Donotproceedtoshutdownwithoutfixingtheissue.
ShuttingdownbothserversusingSystemPlatformManagementConsoleItispossibletoshutdownaserverusingSystemPlatformManagementConsole.
However,iftheserverisrunninginHighAvailability,youcanonlyshutdownthecurrentlyactiveserver.
UsethisproceduretoshutdowntheHighAvailabilitysystem.
1.
Ontheactiveserver,logintoSystemPlatformManagementConsoleasadmin.
2.
Checkthatthesystemisreadytobeshutdowncorrectly.
SeeCheckingcorrectsystemstateusingSystemPlatformManagementConsoleonpage70.
3.
Shutdowntheactiveserver.
SeeShuttingdownaserverusingSystemPlatformManagementConsoleonpage70.
4.
Waituntilthestandbyservertakesover.
Note:Ensurethatthestandbyserverhastakenoversuccessfully,bycheckingtheavailabilityofSystemPlatformManagementConsoleonthestandbyserver.
Forthat,usetheURLofSystemPlatformManagementConsoleregularly.
AdministeringSystemPlatform72AdministeringAvayaAuraSystemPlatformApril20105.
Onthestandbyserver,logintoSystemPlatformManagementConsoleasadmin.
6.
Shutdownthestandbyserver.
SeeShuttingdownaserverusingSystemPlatformManagementConsoleonpage70.
UserAdministrationUserAdministrationoverviewYoucanviewexistinguserprofilesforSystemPlatformServer,createnewuserprofiles,editexistinguserprofiles,andchangeexistingpasswordsbyusingtheoptionsdisplayedunderUserAdministration.
LocalmanagementBydefault,SystemPlatformcomeswithalocalLDAPserverwhichisanOpenLDAPDirectoryServerinstalledinSystemDomain.
ASystemPlatformuserhasoneofthefollowingtworolesthataredefinedinthelocalLDAPserver:AdministratorAdvancedAdministratorSystemPlatforminstallationcreatestwousers,namely,adminandcustinthelocalLDAPserver.
TheseuserscanlogintoSystemPlatformManagementConsole.
TheycanalsousethecommandlinelogintologintoSystemDomainandConsoleDomain.
TheadminuserhastheroleofAdvancedAdministratorandthecustuserhastheroleofAdministrator.
YoucancreatenewSystemPlatformusersinthelocalLDAPserverbyusingtheLocalManagementoptionintheUserAdministrationmenu.
YoucanaccesstheLocalManagementoptiononlywithanAdvancedAdministratorroleandcanperformthefollowingfunctions:ViewingexistingusersCreatingnewusersModifyingexistingusersChangingpasswordsforexistingusersUserAdministrationAdministeringAvayaAuraSystemPlatformApril201073DeletingexistingusersChangingLDAPManagerpasswordAuserwithAdministratorrolecanonlychangeownpassword.
AccessrestrictionsforAdministratorroleAuserwithAdvancedAdministratorrolehasnoaccessrestrictionswhenusingSystemPlatformManagementConsole.
However,auserwithAdministratorrolehasaccessrestrictionsinusingSystemPlatformManagementConsole.
Thefollowingtablesummarizesthoseaccessrestrictions:MenuOptionWebpagecontrolAccessrestrictionVirtualMachineManagementSolutionTemplateDeniedManageGrantedManageDomain-0linkDeniedclickingtheRebootandShutdownbuttonsManagecdomlinkDeniedclickingtheRebootbuttonManageVMlinksDeniedclickingtheReboot,Start,andStopbuttonsViewInstall/UpgradeLogDeniedServerManagementPatchManagement>Download/UploadDeniedPlatformUpgradeDeniedLogViewerGrantedDate/TimeConfigurationGrantedLogginConfigurationDeniedSystemConfigurationGrantedNetworkConfigurationGrantedStaticRouteConfigurationGrantedEthernetConfigurationGrantedAlarmConfigurationGrantedCertificateManagementGrantedLicenseManagementGrantedAdministeringSystemPlatform74AdministeringAvayaAuraSystemPlatformApril2010MenuOptionWebpagecontrolAccessrestrictionSALGatewayManagementGrantedFailoverDeniedfortheConfigure,Delete,Start,Stop,Switchover,UpdateSyncSpeed,Pause/UnpauseSyncbuttons.
PerformanceStatisticsGrantedEjectCD/DVDGrantedFileManagerGrantedBackup/Restore>BackupGrantedBackup/Restore>RestoreDeniedServerReboot/ShutdownDeniedUserAdministrationLocalManagementDeniedChangeLDAPPasswordDeniedEnterpriseLDAPDeniedChangePasswordDeniedAuthenticationFileDeniedNote:AusercreatedusingtheUserAdministrationmenuinSystemPlatformManagementConsoleisstoredinthelocalLDAPserverandwillnotappearinthe/etc/shadowfile.
UserAdministrationAdministeringAvayaAuraSystemPlatformApril201075Creatingusers1.
ClickUserAdministration>LocalManagement.
TheLocalManagementpageappears:2.
OntheLocalManagementpage,clickCreateUser.
TheLocalManagementpagechangestoacceptthedetailsofnewuser:3.
IntheUserIdfield,enterauniqueuserID.
4.
IntheUserPasswordfield,enterapassword.
5.
IntheConfirmPassword,enterthesamepassword.
6.
IntheUserRolefield,clicktheuserroleyouwanttoassigntotheuser.
7.
ClickSaveUsertothecreatetheuserwiththedetailsyouhavespecified.
AdministeringSystemPlatform76AdministeringAvayaAuraSystemPlatformApril2010Editingusers1.
ClickUserAdministration>LocalManagement.
2.
OntheLocalManagementpage,clickthecheckboxagainsttheuserwhosedetailsyouwanttoedit.
3.
ClickEditUser.
TheLocalManagementpagechangestoenableeditingthedetailsofnewuser:4.
IntheNewPasswordfield,enternewpassword.
5.
IntheConfirmPassword,enterthesamepassword.
6.
IntheUserRolefield,clicktheuserroleyouwanttoassigntotheuser.
7.
ClickSavetosavetheediteduserdetails.
UserAdministrationAdministeringAvayaAuraSystemPlatformApril201077Note:ThecustandadminuserIDsarenon-editable.
Deletingusers1.
ClickUserAdministration>LocalManagement.
2.
OntheLocalManagementpage,clickthecheckboxagainsttheuserwhosedetailsyouwanttodelete:3.
ClickDeleteUser.
4.
Inthedialogboxthatappearstoconfirmdeletingtheuser,clickOK.
Note:ThecustandadminuserIDscannotbedeleted.
AdministeringSystemPlatform78AdministeringAvayaAuraSystemPlatformApril2010LocalManagementfielddescriptionsNameDescriptionUserIdUsernameforauser.
UserPasswordPasswordforarespectiveuser.
UserRoleRoleofauser.
Providesinformationwhetherauserhastherightsofanadministratororadvancedadministrator.
YoucanchangetheuserrolesbyusingtheEditUseroption.
LocalManagementbuttondescriptionsButtonDescriptionCreateUserOpenstheCreateUserpageandletsyoucreateauserprofile.
SaveUserSavestheuserprofileandcreatestheuserwiththesespecifications.
EditUserOpenstheEditUserpageandletsyoueditanexistinguserprofile.
DeleteUserActiveonlywhenyouselectanexistinguserfromtheLocalManagementpage.
Deletestheselecteduser.
EnterpriseLDAPUsetheEnterpriseLDAPpagetoconfigureandenableenterpriseLDAPauthenticationthroughtheSystemPlatformManagementConsolesothatthesystemwillauthenticateloginswithanexternalLDAPserver.
UsethispagetoconfigureenterpriseLDAPserverparameters,sothattheenterpriseuserscanusetheenterpriseloginsandpasswordstologontotheSystemPlatformManagementConsole.
Note:OnlyauserundertheAdvancedAdministratorrolecanaccesstheEnterpriseLDAPoption.
ConfiguringauthenticationagainstanenterpriseLDAPUsethisproceduretoenableandconfigureauthenticationofSystemPlatformusersagainstyourenterpriseLDAP.
UserAdministrationAdministeringAvayaAuraSystemPlatformApril2010791.
ClickUserAdministration>EnterpriseLDAP.
2.
SelectEnableEnterpriseLDAP.
3.
Entertheappropriateinformation.
4.
ClickSaveConfiguration.
5.
IftheTLScheckboxwasselected,clickUploadCertificatetoreplacetheexistingenterpriseLDAPcertificate.
6.
ClickTestConnectiontocheckthatyouareabletoconnecttotheEnterpriseLDAPserver.
Note:IfyouselectedtheTLScheckboxandcouldsuccessfullyconnecttotheenterpriseLDAPserver,itmeansthatyoucouldsuccessfullyuploadtheenterpriseLDAPcertificate.
EnterpriseLDAPfielddescriptionsUsetheEnterpriseLDAPpagetoenableandconfigureauthenticationofSystemPlatformusersagainstyourenterpriseLDAP.
NameDescriptionEnableEnterpriseLDAPThischeckboxenablesexternalLDAPauthentication.
Ifyousavethepagewithoutselectingthischeckbox,thesystemsavestheconfigurationwithoutactivatingtheenterpriseLDAPauthentication.
TLSThischeckboxenablestouseTransportLayerSecurity(TLS).
LDAPServerIstheHostnameorIPaddressoftheLDAPserver.
UserAttributeIstheLDAPattributefortheuser.
Thisisusuallycnoruid.
PortIstheportnumberfortheLDAPconnection.
ForTLS-basedLDAPconnection,thedefaultportnumberis636.
Fornon-TLS-basedLDAPconnection,thedefaultportnumberis389.
BaseDNIsthedistinguishednameofthepathwheretheusersearchwillbeexecuted.
ThisisusedforconnectionauthenticationtotheLDAPserver.
Forexample,cn=admin,ou=sv,dc=avaya,dc=com.
ThisparameterisusedtologintotheLDAPserver.
UserDNIsthedistinguishednameoftheLDAPuser.
UserPasswordIsthepasswordoftheLDAPuser.
AdministeringSystemPlatform80AdministeringAvayaAuraSystemPlatformApril2010NameDescriptionAttributeMapSpecifiesLDAPfiltersfortheadvancedadministratorandadministratorroles.
AsimplefiltercanbememberOf=admin_Group.
Acomplexfiltercancontainmultiplecriteriasuchas:(&(memberOf=vsp-craft)(userstatus=ACTIVE)).
AdvancedAdministratorFilterSpecifiestheLDAPfilteronausertocheckiftheuserhasSystemPlatformadvancedadministratorrole.
Forexample,theLDAPfilter(&(memberOf=vsp-craft)(userstatus=ACTIVE))willfiltertheactiveuserswhoarethemembersofvsp-craft.
AdministratorFilterSpecifiestheLDAPfilteronausertocheckiftheuserhasSystemPlatformadministratorrole.
Forexample,theLDAPfilter(&(memberOf=vsp-admin)(userstatus=ACTIVE))willfiltertheactiveuserswhoarethemembersofvsp-admin.
ChangeLDAPpasswordUsetheChangeLDAPPasswordpageforchangingtheSystemPlatformLDAPpassword.
TheLDAPpasswordisassociatedwiththeSystemPlatformLDAP,whichprovidestheLDAPauthentication.
Thus,theLDAPpasswordisdifferentfromtheSystemPlatformuserpasswordthatletsyouaccesstheSystemPlatformManagementConsole.
Note:Passwordsmustbeatleastsixcharacterslong.
Avayarecommendsusingonlyalphanumericcharacters.
ChangingLDAPpasswordYoucanchangetheLDAPpasswordsetduringtheSystemPlatforminstallation.
1.
ClickUserAdministration>ChangeLDAPPassword.
2.
Enterthenewpassword.
3.
Confirmthenewpassword.
4.
ClickSavetosavethenewpassword.
UserAdministrationAdministeringAvayaAuraSystemPlatformApril201081ChangeSystemPlatformpasswordTheChangePasswordoptionisavailableonlyforlocalusers.
EnterpriseLDAPuserscannotchangetheirpasswordsfromSystemPlatformManagementConsole.
.
UsetheChangePasswordpagetochangetheuserpasswordthatletsyouaccesstheSystemPlatformManagementConsole.
Note:Passwordsmustbeatleastsixcharacterslong.
Avayarecommendsusingonlyalphanumericcharacters.
ChangingSystemPlatformuserpasswords1.
ClickUserAdministration>ChangePassword.
2.
FillupthefollowingfieldsontheChangePasswordpage.
OldPasswordNewPasswordConfirmPassword3.
ClickChangePasswordtochangethecurrentpassword.
AdministeringSystemPlatform82AdministeringAvayaAuraSystemPlatformApril2010Chapter2:TroubleshootingDVDdoesnotmountTheDVDdoesnotmountautomatically.
Troubleshootingsteps1.
LogontoConsoleDomainasadmin.
2.
Typesu-3.
Entertherootpassword.
4.
Runthefollowingcommands:>sshdom0.
vsp/opt/avaya/vsp/template/scripts/udomAttachCd>mount/dev/xvde/cdrom/VirtualmachinehasnoconnectivityoutsideafterassigningdedicatedNICsupportTroubleshootingsteps-throughSystemDomain(Dom-0)1.
CheckifthepciIDentryisinthe/etc/rc.
localand/etc/modprobe.
conf.
2.
CheckifthepciIDisbindedproperlyto/sys/bus/pci/drivers/pciback/.
AdministeringAvayaAuraSystemPlatformApril2010833.
Checkiftheeth0onvirtualmachineisavailableandIPAddressisassigned(type:ifconfig-a).
4.
CheckiftheMacAddressthatisassignedtovirtualmachineeth0isaphysicalMacAddress(type:ifconfig-a).
5.
Alsocheckiftherearenoerrormessagesdisplayedwhenyoutypemodinfobnx2(wherebnx2isadrivername).
Troubleshootingsteps-throughSystemPlatformManagementConsole1.
ChecktheEthernetcableisconnectedonthecorrectEthernetport(forexample:eth3).
2.
ShutdownvirtualmachineandrestartitfromSystemPlatformManagementConsole.
GeneralissueswiththesystemandwantstocontactsupportTroubleshootingstepsSystemPlatformprovidesscriptsthatgatheralltherequiredconfigurationfiles,logfiles,andsystemstatuscommands,andcollectthemintoazipfile.
IfthisscriptisexecutedfromconsoledomainSSHsession,italsogathersthisinformationfromDomain-0(ifHighAvailabilityFailoverisnotconfigured)orfrombothDomain-0s(ifHighAvailabilityFailoverisconfigured).
1.
Tocreatesuchzipfileexecutegetlogscommandfromconsoledomain.
Troubleshooting84AdministeringAvayaAuraSystemPlatformApril2010Itwillcreatevsp_logs__.
zipcompressedfileinthecurrentdirectory.
2.
Ifconsoledomainisnotaccessible,executegetlogscommandonDomain-0(ifHighAvailabilityFailoverisnotconfigured)oronbothDomain-0s(ifHighAvailabilityFailoverisconfigured).
ResultThisfilecanbethenusedtoyoursupporttechnician.
IssueswhenconfiguringSystemPlatformHighAvailabilityFailoverCannotestablishcommunicationthroughcrossovernetworkinterfaceTroubleshootingstepsEnsurethatthecrossovercableisproperlyconnectedtoeth2interfaceonbothmachines.
LocalIPaddressprovidedTroubleshootingstepsEnsurethatyouspecifyremoteconsoledomainIPaddresswhenconfiguringtheSystemPlatformHighAvailabilityFailover.
IssueswhenconfiguringSystemPlatformHighAvailabilityFailoverAdministeringAvayaAuraSystemPlatformApril201085CannotestablishSSLcommunicationTroubleshootingstepsYouhaveprovidedIPaddressremoteconsoledomainIPaddressthatwasalreadypartofSystemPlatformHighAvailabilityFailoverbutwaslaterremovedasastandbynode.
Note:SuchconsoledomaincannotbecomeamemberofSystemPlatformHighAvailabilityFailover.
ReinstallthestandbymachinewiththeSystemPlatformandretrytheConfigureFailovermethod.
Standbyfirst-bootsequenceisnotyetfinishedTroubleshootingstepsYouhaveprovidedIPaddressofremoteconsoledomainwhichinitialstart-upprocedurewasnotyetcompleted.
Provideenoughtimetocompletethisstart-upprocessandtryconfiguringtheSystemPlatformHighAvailabilityFailoveragainlater.
Note:Themachinecantakeupto5minutesuntilthisprocessisfinishedfromthemomentyoucanloginintoSystemDomain(Dom-0).
ClusternodesarenotequalTroubleshooting86AdministeringAvayaAuraSystemPlatformApril2010TroubleshootingstepsYouattemptedtosetupSystemPlatformHighAvailabilityFailoveraddingtheweakermachinethenthepreferredonetothesystem.
Eitheruseanothermachinethathasthesameorbetterconfigurationparametersorswapthemachinessothattheweakeronebecomespreferrednode.
Note:Thestandbyservercannothavelessmemory,numberofprocessors,totalorfreediskspacethenprimaryserver.
AtemplateisinstalledonremotenodeTroubleshootingstepsThereisatemplate(SolutionTemplate)installedonthestandbynode.
Note:SystemPlatformforbidstosetupSystemPlatformHighAvailabilityFailoverwhenthereisatemplateinstalledonthestandbynode.
EitherdeleteSolutionTemplatefromthestandbynodeorreinstallitwithSystemPlatformandretryconfigurationoftheSystemPlatformHighAvailabilityFailover.
NICsarenotactiveonbothsidesTroubleshootingstepsEitherpublicandcrossovernetworkinterfaceisnotavailableononeofthenodes.
Bothpublicandcrossovernetworkinterfacesmustbeavailableandproperlyworkingonbothnodes.
IssueswhenconfiguringSystemPlatformHighAvailabilityFailoverAdministeringAvayaAuraSystemPlatformApril201087Ensureyouhaveenoughnetworkinterfacesonthesystem.
CannotestablishHAnetworkinterfaceTroubleshootingstepsCrossovernetworkinterfacecannotbesetupononeofthenodes.
Crossovernetworkinterfacemustbeavailableproperlyworkingonbothnodes.
Ensurethatthisnetworkinterfaceisnotenslavedtothenetworkbridgeonthesystem.
IssueswhenstartingSystemPlatformHighAvailabilityFailoverDifferentplatformversionsagainstclusternodesTroubleshootingstepsVersionsofSystemPlatformarenotequalonbothclusternodes.
SystemschecksiftheSystemPlatformversionsareequalonbothclusternodesandforbidstostartSystemPlatformHighAvailabilityFailoveriftheyarenot.
BothmachinesmustbeinstalledwiththesameSystemPlatformversion.
Ifyouinstallapatchpleaseensureitisinstalledonbothmachines.
AtemplateisinstalledonremotenodeTroubleshooting88AdministeringAvayaAuraSystemPlatformApril2010TroubleshootingstepsThereisatemplate(SolutionTemplate)installedonthestandbynode.
SystemPlatformforbidstostartSystemPlatformHighAvailabilityFailoverwhenthereisatemplateinstalledonthestandbynode.
DeleteSolutionTemplatefromthestandbynode.
ResourcesarenotstartedonanynodeandcannotaccessSystemPlatformManagementConsoleTroubleshootingstepsSystemPlatformHighAvailabilityFailoverusesdefaultnetworkgatewayasapingtarget.
Itisusedtocheckmachine'sabilitytocommunicatetonetworkandcomputecomputer'sscoretorunresources.
Ifthegatewayisnotreplyingtothosepingrequests,SystemPlatformHighAvailabilityFailoverisnotabletoassignanynodeasactivenode,becausetheirscoreisequalandasaresultnoresourcesareactivatedonanynode.
CheckthatyourdefaultnetworkgatewayisabletoreceiveandreplytoICMPechorequestsfrombothSystemPlatformnodes.
IftherearefirewallrulesfilteringtheICMPrequestsbypacketsize,ensurethatpacketsizesupto256bytesareallowedbytheserules.
SeethePrerequisitessectioninInstallingandConfiguringAvayaAuraSystemPlatformformoreinformation.
CannotaccessSystemPlatformManagementConsoleafterStartFailoverIssueswhenstartingSystemPlatformHighAvailabilityFailoverAdministeringAvayaAuraSystemPlatformApril201089Troubleshootingsteps1.
Check/var/log/vsp/vspha.
loglogfilefordetails.
2.
Execute#getlogscommandonpreferrednode.
3.
Providetheresultingvsp_logs__.
zipcompressedfiletoyoursupporttechnician.
ActiveserverfailsTroubleshootingstepsDisconnectthemainnetworkcableonlyfromtheactiveserver.
ResultThestandbyserverbecomeactive.
Note:Ensurethatthecrossoverconnectionisworkingfinebeforethetest.
DataswitchfailsTroubleshootingsteps1.
Disconnectthemainnetworkcablefrombothactiveandstandbyserver.
2.
Reconnectthecablesafterfewminutes.
ResultPreviousactiveserverremainsasactive.
Troubleshooting90AdministeringAvayaAuraSystemPlatformApril2010Note:Ensurethatthecrossoverconnectionisworkingfinebeforethetest.
HeartbeatlinkfailsTroubleshootingsteps1.
Disconnectcrossovercablebetweenthetwoservers.
2.
Reconnectthecrossovercableafterfewminutes.
ResultActiveserverremainsasactive.
Activeserverwillresyncthedatatostandbyserver.
Note:Thecrossoverconnectioninterruptionshouldnotinitiateanyfailoveraction.
HighAvailabilityFailoverdoesnotworkTroubleshootingsteps1.
RemovetheSAMPboardfromtheS8510serverbeforeinstallingSystemPlatform.
2.
EnsurethattheDualNICcardisconnectedtotheeth2port.
StartLDAPserviceonSystemDomain(Dom-0)StartLDAPserviceonSystemDomain(Dom-0)AdministeringAvayaAuraSystemPlatformApril201091TroubleshootingstepsIfthesystemcrashedorwasresetforanyotherreason,theLDAPcanpreventtostartonnextbootupsequence.
InthatcaseallusersthatarestoredinLDAPdatabasewillnotbeabletologin.
LogintothesystemconsoleasuserthatisnotusingLDAPcredentialsandexecutefollowingcommands:#su–#cd/var/lib/ldap#slapd_db_recover–v#serviceldaprestartSystemPlatformManagementConsolenotaccessibleTroubleshootingsteps1.
Checktheinternetconnection.
2.
EnsurethattheWebaddressiscorrect.
3.
Checkproxysettingsinyourbrowser.
Re-enablingfailedstandbynodetoHighAvailabilityFailoverTroubleshooting92AdministeringAvayaAuraSystemPlatformApril2010TroubleshootingstepsNote:Thisprocedureisservice-disruptiveandyoumustplanyouractivitiesaccordingly.
Inthiscasealltheservicesarestillrunningonthepreferrednode.
Tore-enablestandbynodeafteritwasreinstalledwithSystemPlatformofthesameversionascurrentlyactivenode,performthefollowingsteps:1.
LogontoactivenodewebconsoleasadminuserandnavigatetoServerManagement>Failover.
2.
Executethe"StopFailoverMode"operationfromtheactivenodewebconsole.
3.
Afterthewebconsoleisaccessibleagain,logontoactivenodewebconsoleasadminuserandnavigatetoServerManagement>Failover.
4.
Executethe"RemoveFailover"operation.
5.
Executethe"ConfigureFailover"operationwithnewlyreinstalledstandbynode.
6.
Executethe"StartFailoverMode"fromtheactivenodewebconsole.
Re-enablingfailedpreferrednodetoHighAvailabilityFailoverTroubleshootingstepsInthiscasealltheservicesarerunningonthestandbynode.
However,theresolutioncoulddifferinthefollowingcases:completelynewmachineistobere-enabledintotheHAsystem,orpreviouspreferredmachinewithnewprimarynetworkcard(thecardwitheth0andeth1NICs)istobere-enabledIfyouplantore-enableintoHAsystemthemachinethatfitstoanyoftheaboveconditions,theprocessisexactlythesameasre-enablingthefailedstandbynode.
PleaserefertotheRe-enablingfailedstandbynodetoHighAvailabilityFailoversectionformoreinformation.
Re-enablingfailedpreferrednodetoHighAvailabilityFailoverAdministeringAvayaAuraSystemPlatformApril201093Tore-enablepreviouslyusedpreferrednodewiththesameprimarynetworkcard,someadditionalstepsthatarenotavailableonthewebconsolearerequired.
PleasecontactAvayasupporttoassistyouwithresolvingofthisstate.
Important:DonottrytoreinstallthisfailednodewithSystemPlatformonthesamenetworkascurrentlyactivenode.
Suchinstallationwouldfail.
Ifyoualreadyreinstalledthemachine,itwillhavetobereinstalledagainwithassistanceofAvayasupport.
TroubleshootingvirtualmachinewithdedicatedNICmayfailafterSystemPlatformupgradeTroubleshootingstepsDedicatedNICsettingsarelostuponthenextserverrebootoncethe/etc/rc.
localsymboliclinkischangedtoafile.
ThevirtualmachineusingthededicatedNICwillfailtoboot.
1.
LogintoSystemPlatformManagementConsoleasadmin2.
Typesu3.
Typell/etc/rc.
localThesystemdisplaysthefollowinginformation:/etc/rc.
local->rc.
d/rc.
local4.
Incasethesymboliclinkdoesn'texist,performthefollowingsteps:a.
Movethe/etc/rc.
localfileto/etc/rc.
d/rc.
localbytypingthecommandmv-f/etc/rc.
local/etc/rc.
d/rc.
localb.
Createasymboliclinktothefile/etc/rc.
d/rc.
localbytypingthecommandln-s/etc/rc.
d/rc.
local/etc/rc.
localc.
ReboottheservereitherfromSystemPlatformManagementConsoleorthecommandline.
Troubleshooting94AdministeringAvayaAuraSystemPlatformApril2010AppendixA:HowSystemPlatformHighAvailabilityFailoverworksPingtargetsSystemPlatformHighAvailabilityFailoverusesanodescoringtodecidewhichnoderesourcesshouldrunineachparticularsituation.
Everynodeusesthefollowing3pingtargets:1.
Defaultnetworkgatewayasapublicpingtarget.
2.
eth0networkinterfaceofthepeer.
3.
eth2networkinterfaceofthepeer.
Everysuccessfulpingresultgivesamachinethesamescoreamountforeverypingtarget.
Therefore,ifbothmachinescanreachallthe3pingtargets,theybothhavethesamescoreandresourcesrunonthepreferrednode.
Thefollowingimagedepictstheoverviewofthemachineswiththeir3pingtargets:Asaconsequenceofpingtargets,oneofthefollowingthingsmayhappen:AdministeringAvayaAuraSystemPlatformApril2010951.
Ifthecrossoverlinkisinterruptedonanynode,noactionwillresultbecausebothmachineshavethesamescore.
2.
Ifthepubliclinkisinterruptedonthestandbynode,noactionwillresultbecausetheactivenodestillhasthefullscorewhilethestandbynodehaslost2pingsources.
3.
Ifthepubliclinkisinterruptedontheactivenode,heartbeatwillinitiatefailoverbecauseactivenodehaslost2pingsourceswhilethestandbyhasthefullscore.
Note:Thedefaultgatewayisthepingtargetanditisnotaconfigurableparameter.
EnsurethatyourgatewayrepliestoICMPpingswhichhavepayloadslargerthatthedefaultsandcomefromtheSystemPlatformnodes.
DRBDinitialdatasynchronizationSystemPlatformHighAvailabilityFailoverusestheDistributedReplicatedBlockDevice(DRBD)componenttopropagateonlinechangesthataremadeontheactivenode.
EachLogicalVolumethatispropagatedbyDRBDusesseparateDRBDresource.
ListoftheseDRBDresourcesandtheirstatescanbecheckedontheSystemPlatformFailoverpage.
However,beforetheinitialsynchronizationoftheDRBDresourcesiscompleted,thestandbynodedoesnothavethereliabledatathatcouldbeusedtostartthevirtualmachines.
Thetimeintervalduringinitialdatablocksynchronizationiscalledinitialdatasynchronization.
Thefollowingimagedepictstheinitialdatasynchronizationfromtheactivenodetothestandbynode:HowSystemPlatformHighAvailabilityFailoverworks96AdministeringAvayaAuraSystemPlatformApril2010Note:Duringtheinitialsynchronization,theonlinechangesarealsopropagated.
Itisessentialtoprovideenoughnetworkthroughputforthesuccessfulcompletionoftheonlinechanges.
ThustheSystemPlatformsetstheDRBDinitialsynchronizationrateto30MB/s.
YoucanmodifythisvaluefromtheFailoverpageincasesystemisnotoverloaded.
DRBDonlinepropagationofdatachangesSystemPlatformHighAvailabilityFailoverusestheDistributedReplicatedBlockDevicecomponenttopropagateonlinechangesthataremadeontheactivenode.
Itusesitsprotocol"C"whichensuresthatwritingtothelocalharddiskisonlyconfirmedwhenthesamewriteisacknowledgedontheremotenode.
Thisensuresthatthemachinesarekeptinconsistentstatetoenablethestandbynodetotakeoverwhenrequired.
Thefollowingimagedepictsthedatapropagationfromactivenodetothestandbynode:Intheeventoffailoverorswitchoverwhenthenoderolesarechanged(thatis,theactivenodebecomesthestandbynodeandviceversa),thepropagationdirectionswapstoensurethatthechangesontheactivenodearepropagatedtothecurrentstandbynode.
Thefollowingimagedepictsdatapropagationafterafailover/switchover:AdministeringAvayaAuraSystemPlatformApril201097DatachangesduringdisconnectionIncaseofthereplicationlinkinterruption,DRBDusesitsownmetadatatokeepthehistoryofmodifieddatablockssincetheconnectionbreakup.
Laterwhentheconnectionisreestablished,themissingdatablocksaresynchronizedonthestandbynodeinparallelwiththeonlinechangespropagation.
ThefollowingimagedepictsthedatachangeshistorymarkedintheDRBDmetadataduringthepropagationlinkdisconnection:HowSystemPlatformHighAvailabilityFailoverworks98AdministeringAvayaAuraSystemPlatformApril2010AutomaticSplit-BrainresolutionIncasethereisnocommunicationpathbetweenthenodes,ClusterResourceManagercanactivateresourcesonbothnodesatthesametime.
ThissituationiscalledSplit-Brain.
Afterbothnodesappearonthenetworkagain,thedatachangesthatoccurredonthenodesmustbediscardedononeofthem.
SystemPlatformHighAvailabilityFailoverusesaDRBDfeaturetorecognizewhichnodebecameactiveasthelastone.
Thisnodeisrebootedimmediatelyanditsdatachangesarediscarded.
Aftersuccessfulreboot,itwillsynchronizethechangesthatoccurredonthesurvivalnodesincethedisconnectionbeforesplit-brain.
AdministeringAvayaAuraSystemPlatformApril201099HowSystemPlatformHighAvailabilityFailoverworks100AdministeringAvayaAuraSystemPlatformApril2010AppendixB:AdministeringSALonSystemPlatformSALGatewayconfigurationTheSAL(SecureAccessLink)GatewayincludesaWeb-basedGatewayuserinterfacethatprovidesstatusinformation,logginginformation,andconfigurationinterfaces.
Usetheproceduresinthissectiontoconfigurethegatewayandotherdevicesforalarmingandremoteaccess.
ThedevicesincludeSystemPlatform'sSystemDomain(dom0),ConsoleDomain(cdom),andotherproductvirtualmachines(CommunicationManager,CommunicationManagerMessaging,SIPEnablementServices,ApplicationEnablementServices,UtilityServerandMediaServices)inSystemPlatform.
Relatedtopics:LaunchingSALGatewayUIonpage101ConfiguringSALGatewayonpage102ConfiguringSALEnterpriseonpage103ConfiguringRemoteAccessServeronpage104ConfiguringNMSonpage105Managingservicecontrolonpage105Applyingconfigurationchangesonpage106Configuringamanagedelementonpage106Productsandmodelsonpage107LaunchingSALGatewayUITheSAL(SecureAccessLink)GatewayincludesaWeb-basedGatewayuserinterfacethatprovidesstatusinformation,logginginformation,andconfigurationinterfaces.
Usetheproceduresinthissectiontoconfigurethegatewayandotherdevicesforalarmingandremoteaccess.
ThedevicesincludeSystemPlatform'sSystemDomain(dom0),ConsoleDomain(cdom),andotherproductvirtualmachines(CommunicationManager,CommunicationManagerMessaging,SIPEnablementServices,ApplicationEnablementServices,UtilityServerandMediaServices)inSystemPlatform.
AdministeringAvayaAuraSystemPlatformApril20101011.
GotoAvayaAuraSystemPlatform'sWebconsoleandlogon.
2.
GotoServerManagement>SALGatewayManagement.
3.
OntheSALGatewayManagementpage,clickLaunchSALGatewayManagementPortaltolaunchtheSALGatewayUI(userinterface).
4.
OntheSALGatewaypage,logontotheSALGatewayusingthesamelogincredentialsthatyouusedfortheSystemPlatformWebconsole.
5.
OntheGatewayhomepagenavigationpane,clickAdministration.
ThesystemdisplaysthefollowingoptionsunderAdministration:GatewayConfigurationLDAPProxySALEnterpriseRemoteAccessPolicyServerNMSServiceControlApplyConfigurationChangesConfiguringSALGateway1.
OntheGatewayhomepage,clickAdministration>GatewayConfiguration.
2.
OntheGatewayConfigurationpage,clickEdit.
ThesystemdisplaystheGatewayConfiguration(edit)panel.
3.
IntheGatewayHostnamefield,enteradistinguishinghostnamefortheSALGateway.
4.
IntheGatewayIPAddressfield,entertheIPaddressoftheSALGateway.
5.
IntheSolutionElementIDfield,entertheSolutionElementIDthatuniquelyidentifiestheSALGateway.
ThesystemusestheSALGatewaySolutionElementIDtoregistertheSALGatewaywiththeSecureAccessConcentratorRemoteServer.
6.
IntheGatewayAlarmIDfield,entertheAlarmIDoftheSALGateway.
AdministeringSALonSystemPlatform102AdministeringAvayaAuraSystemPlatformApril2010ThesystemusesthevalueintheGatewayAlarmIDfieldtouniquelyidentifythesourceofGatewayalarmsintheSecureAccessConcentratorCoreServer.
7.
ClickApply.
Thesystemchangestheconfigurationandtheconfigurationchangestakeeffectimmediately.
8.
ClickUndoEdittoundothechanges.
ThesystemreturnstotheconfigurationbeforeyouclickedtheEditbutton.
SeetheSecureAccessLink1.
5GatewayImplementationGuideformoreinformation.
ConfiguringSALEnterprise1.
OntheGatewayhomepage,clickAdministration>SALEnterprise.
ThesystemdisplaystheSALEnterprisepage.
2.
InthePrimaryEnterprisefield,entertheIPAddressorhostnameoftheprimarySALEnterprise.
3.
InthePortfield,enterthePortnumberoftheprimarySALEnterprise.
4.
IntheSecondaryEnterprisefield,entertheIPAddressorthehostnameofthesecondarySALEnterprise.
5.
InthePortfield,enterthePortnumberofthesecondarySALenterprise.
6.
ClickApply.
Thesystemdisplaysthefollowingbuttonsinthepage:Edit:tochangetheconfiguration.
Apply:toapplythechangesmadetotheconfiguration.
Test:torunthediagnostictestsforconnectivity.
Important:YoumustrestarttheSALGatewayfortheconfigurationtotakeeffect.
TillyourestarttheSALGateway,thesystemdoesnotconnecttothenewSALEnterprise.
WhenyourestarttheSALGateway,thesystemmightmisssomeSNMPtraps.
7.
(Optional)IfyouwanttousetheAvayaproductionenterpriseserver,performthefollowingtasks:a.
InthePrimaryEnterprisefield,enteralarming.
esp.
avaya.
com.
SALGatewayconfigurationAdministeringAvayaAuraSystemPlatformApril2010103b.
InthePortfield,enter8002.
c.
UsetheAvayaproxywhenconnectingfromAvayainternalnetwork.
SeetheSecureAccessLink1.
5GatewayImplementationGuideformoreinformation.
ConfiguringRemoteAccessServer1.
OntheGatewayhomepage,clickAdministration>RemoteAccess.
ThesystemdisplaystheRemoteAccesspage2.
InthePrimaryEnterprisefield,entertheIPAddressorhostnameoftheprimaryRemoteAccessServer.
3.
InthePortfield,entertheportnumberoftheprimaryRemoteAccessServer.
4.
(Optional)IntheSecondaryEnterprisefield,entertheIPAddressorHostnameofthesecondaryRemoteAccessServer.
5.
(Optional)InthePortfield,entertheportnumberofthesecondaryRemoteAccessServer6.
ClickApply.
Thesystemdisplaysthefollowingbuttonsinthepage:Edit:tochangetheconfiguration.
Apply:toapplythechangesmadetotheconfiguration.
Test:torunthediagnostictestsforconnectivity.
Important:YoumustrestarttheSALGatewayfortheconfigurationtotakeeffect.
UntilyourestarttheSALGateway,thesystemdoesnotconnecttothenewSecureAccessConcentratorRemoteServers.
WhenyourestarttheSALGateway,thesystemterminatesallactiveconnections.
SeetheSecureAccessLink1.
5GatewayImplementationGuideformoreinformation.
AdministeringSALonSystemPlatform104AdministeringAvayaAuraSystemPlatformApril2010ConfiguringNMS1.
OntheGatewayhomepage,clickAdministration>NMS.
ThesystemdisplaystheNetworkManagementSystemspage.
2.
IntheNMSHostName/IPAddressfield,entertheIPAddressorhostnameoftheNMSserver.
3.
IntheTrapportfield,entertheportoftheNMSserver.
4.
IntheCommunityfield,enterthecommunitystringoftheNMSserver.
EnterpublicastheCommunity,asSALagentssupportonlypublicascommunityatpresent.
5.
ClickApply.
6.
(Optional)UsetheAddbuttontoaddmultipleNMS(s).
SeetheSecureAccessLink1.
5GatewayImplementationGuideformoreinformation.
ManagingservicecontrolUsethisproceduretoviewthestatusofaservice,stopaservice,ortestaservicethattheSALGatewaymanages.
1.
OntheGatewayhomepage,clickAdministration>ServiceControl.
ThesystemdisplaystheGatewayServiceControlpage.
Thepageliststhefollowingservices:Inventory(disabledinthecurrentrelease)AlarmingRemoteAccessTheGatewayServiceControlpagealsodisplaysthestatusofeachserviceas:StoppedRunningSALGatewayconfigurationAdministeringAvayaAuraSystemPlatformApril2010105SeetheSecureAccessLink1.
5GatewayImplementationGuideformoreinformation.
2.
ClickStoptostopaservice.
3.
ClickTesttotestaservice.
Applyingconfigurationchanges1.
OntheGatewayhomepage,clickAdministration>ApplyConfiguration.
ThesystemdisplaystheApplyConfigurationChangespage.
2.
ClicktheApplybuttonnexttoConfigurationChanges.
SeetheSecureAccessLink1.
5GatewayImplementationGuideformoreinformation.
WhenyouclickApply,thesystemrestartstheSALGatewayandupdatestheGatewaywiththenewvaluesyouconfigured.
Configuringamanagedelement1.
OntheGatewayhomepage,clickAdministration>ManagedElement.
ThesystemdisplaystheManagedElementpage.
2.
ClickAddnew.
3.
IntheHostNamefield,enterahostnameforthemanageddevice.
4.
IntheIPAddressfield,entertheIPaddressofthemanageddevice.
5.
SelecttheNIUcheckboxifyouwanttouseaNetworkInterfaceUnitportforremoteaccessandselectavaluefromthelistbox.
Therangeofvaluesallowedisonethroughnine.
SomeoldermanageddevicescanonlybereachedonanetworkthoughanNIUinterface.
TheNIUemulatesamodemtoconvertamanageddevicefrommodemsupporttonetworkaccessibility.
TomakearemoteconnectiontotheNIU-supporteddevices,youmustknowwhichNIUportnumbertoconnectto.
6.
IntheSolutionElementIDfield,entertheSolutionElementIDofthedevice.
AdministeringSALonSystemPlatform106AdministeringAvayaAuraSystemPlatformApril20107.
IntheProductIDfield,entertheProductIDorAlarmID.
8.
IntheModelfield,enterthemodelthatisapplicableforthemanageddevice.
9.
(Optional)SelecttheProvideRemoteAccesstothisdevicecheckbox,ifyouwanttoallowremoteconnectivitytothemanageddevice.
10.
(Optional)SelecttheTransportalarmsfromthisdevicecheckbox,ifyouwantalarmsfromthisdevicetobesenttotheSecureAccessConcentratorCoreServer.
11.
(Optional)SelecttheCollectInventoryforthisdevicecheckbox,ifyouwantaninventoryscheduleatthemanageddevicelevel.
ThisselectionmanagesInventoryCollectionandsendstheinventorytoAvaya.
TheselectionalsodecidestheInventoryCollectionScheduleinterval.
Thisfeatureisnotsupportedyet.
12.
ClickAdd.
13.
ClickApplytoapplythechanges.
14.
ClickEdittochangetheconfiguration.
15.
ClickDeletetodeletetheconfigurations.
Important:AfteryouselectApplyorDelete,youmustrestarttheSALGatewayservicesfortheconfigurationtotakeeffect.
ProductsandmodelsThissectionpresentstherelationshipbetweentheproductdevicesmanagedbytheSALGatewayandthemodelsthemanageddevicesmustuse.
Arewesupposedtochangetheproductnames/modelnamesfromVSPtoSystemPlatformPleaseverifyalltheproductnamesanddomainnames.
ProductsModelsSystemPlatformSystemDomain(Dom0)VSP_1.
0SystemPlatformConsoleDomain(cdomandudom)VSPU_1.
0SALGatewaySAL_Gateway_1.
0CommunicationManagerCM_Media_server_1.
0CommunicationManagerMessagingCM_Media_server_1.
0(temporarysolution)ApplicationEnablementServicesAES_1.
0SALGatewayconfigurationAdministeringAvayaAuraSystemPlatformApril2010107ProductsModelsSIPEnablementServicesSIP_Server_1.
0UtilityServerVUS_1.
0MediaServicesCobar_1.
0Youcancreateacheatsheetasfollows:SystemPlatformdomainIPAddressSEIDProductIDModelsNotesSystemDomain(Dom0)10.
0.
0.
66(076)934-20007000135491VSP_1.
0ConsoleDomain(cdomandudom)10.
0.
0.
67(076)934-20015023427441VSPU_1.
0Dom1-CommunicationManager10.
0.
0.
71(076)934-20021000237197CM_Media_server_1.
0Dom-CommunicationManagerMessaging10.
0.
0.
72(076)934-20032000041897CM_Media_server_1.
0UseCommunicationManagermodelasatemporarysolutionDom2-SIPEnablementServices10.
0.
0.
73(076)934-20041000237198SIP_Server_1.
0Dom3-ApplicationEnablementServices10.
0.
0.
74(076)934-20054000006620AES_1.
0Dom4-UtilityServer10.
0.
0.
75(076)934-2006VUS_1.
0Dom5-MediaServices10.
0.
0.
76(076)934-2007Cobar_1.
0Note:ThereisnoalarmmechanisminUtilityServerandMediaServices.
YouarenotrequiredtoenablealarmingforthemanagedelementsusedbyUtilityServerandMediaServices.
SystemDomain(Dom0)(VSP)doesnothavealarmingenabled,butCdom(VSPU)hasalarmingenabled.
SystemDomain(Dom0)sendsallsyslog(systemlogs)toCdom(ConsoleAdministeringSALonSystemPlatform108AdministeringAvayaAuraSystemPlatformApril2010Domain)andCdomtriggersalarmsonbehalfofSystemDomain(Dom0).
ButSystemDomain(Dom0)hasitsownAlarmID(ProductID).
InSystemPlatformHA(HighAvailability)mode,yourequiretwodifferentsolutionelementIDs(SEID)forSystemDomain(Dom0):oneisforactiveSystemDomain(Dom0)andtheotherisforstandbySystemDomain(Dom0).
YoumustadministerbothSEIDsthroughtheSALGatewayUI(userinterface).
MakingSALGatewaycommunicatewithSALEnterpriseUsethisproceduretomakeSAL1.
5GatewayinSystemPlatformcommunicatewiththeSALEnterpriseinSessionManager.
UseStep1throughStep8toexporttheSelf-SignedCertificateofSessionManager.
Ifyoualreadyknowhowtoexportacertificate,orifSessionManagerisusingacertificatedsignedbytrustedagencies,forexampleVerisign,gotoStep9.
Note:Thisprocedureusesptest9vm2.
platform.
avaya.
comforSessionManagerandptest9vm1.
platform.
avaya.
comforConsoleDomain(cdomandudom)inSystemPlatform,whereSAL1.
5Gatewayislocated.
1.
OnaWebbrowser,typethefollowingURL:https://ptest9vm2.
platform.
avaya.
com/2.
OntheHTTPStatus404page,double-clickthelockicon(SSLSecured)locatedatthebottom.
MakingSALGatewaycommunicatewithSALEnterpriseAdministeringAvayaAuraSystemPlatformApril20101093.
OntheCertificatepage,clickDetails.
4.
ClickCopytoFile.
5.
OntheCertificateExportWizardpage,clickNext.
6.
CheckthattheDERencodedbinaryX.
509(.
CER)optionisselectedbydefault,thenclickNext.
7.
OntheSaveAspage,selectalocationtosavethecertificateandclickSave.
8.
OntheCertificateExportWizardpage,clickFinish.
ThesystemsavestheSelf-SignedCertificatenamedptest9vm2.
platform.
avaya.
com.
cerinyourspecifiedlocation.
9.
OpenanSSHsessiontoptest9vm2.
platform.
avaya.
com.
10.
Typevi/opt/Avaya/Mgmt/3.
0.
5/SpiritEnterprise/config/DataTransportConfig.
xml11.
Makeanoteofthevalueinboldletterstobeusedinlatersteps:12.
OnaWebbrowser,typethefollowingURL:https://ptest9vm1.
platform.
avaya.
com:7443/salgatewayandlogontoSAL1.
5Gateway.
AdministeringSALonSystemPlatform110AdministeringAvayaAuraSystemPlatformApril201013.
MakeanoteofthegatewayconfigurationdetailsfromtheGatewayConfigurationpage.
14.
AddSALGatewayasamanageddeviceusingthedetailsfromtheGatewayConfigurationpage.
SeeConfiguringamanagedelementtopicformoreinformation.
15.
OntheManagedElementConfigurationpage,checktheTransportalarmsfromthisdeviceoption.
DonotrestarttheSALandAxedaagents.
16.
EdittheSALEnterpriseasfollows:a.
OntheSALEnterprisepage,makesurethatthePrimaryEnterpriseandSecondaryEnterprisefieldscontainptest9vm2.
platform.
avaya.
com.
b.
ClicktheTestbuttontochecktheconnection.
c.
ClickApply.
DonotrestarttheSALandAxedaagents.
17.
OpenanSSHsessiontoptest9vm1.
platform.
avaya.
com.
18.
LocatethefileSPIRITAgent_1_0_DataTransportConfig_xxxxxxxx_xxxxxx_xxx.
xmlwiththemostrecenttimestampinthefilename.
19.
Changethefollowingentry:Enterprise-productiontoEnterprise-ptest9vm2.
platform.
avaya.
com20.
LocatethefileSPIRITAgent_1_0_SpiritComponentConfig_xxxxxxxx_xxxxxx_xxx.
xmlwiththemostrecenttimestampinthefilename.
21.
ReplacealltheoccurrencesofEnterprise-productiontoEnterprise-ltest9vm2.
platform.
avaya.
com.
IfSessionManagerusesacertificatethatissignedbyatrustedagency,thenyoucandirectlygotoStep25(restartingSpiritandAxeda).
IfSessionManagerusesaSelf-SignedCertificateandyouhavefollowedStep1throughStep8earlier,thencontinuewiththefollowingsteps.
22.
CopytheSelf-SignedCertificateptest9vm2.
platform.
avaya.
com.
ceryoucreatedearlierto/opt/avaya/SAL/gateway/SpiritAgent/security.
23.
TypethefollowingcommandtoimportthecertificatetoSpiritAgent'struststore:cd/opt/avaya/SAL/gateway/SSL/keytool–import–aliasptest9vm2.
platform.
avaya.
com–keystorespirit-trust.
jks–fileMakingSALGatewaycommunicatewithSALEnterpriseAdministeringAvayaAuraSystemPlatformApril2010111/opt/avaya/SAL/gateway/SpiritAgent/security/ptest9vm2.
platform.
avaya.
com.
cer24.
Enteravaya123whenthesystempromptsyouforpassword.
25.
TypethefollowingcommandstorestarttheSpiritandAxedaAgents:servicespiritAgentrestartserviceaxedaAgentrestart26.
OnaWebbrowser,typethefollowingURL:https://ptest9vm1.
platform.
avaya.
com:7443/andlogontoSAL1.
5Gateway.
27.
GotoAdministration>ServiceControl.
28.
ClicktheTestbutton.
ThesystemdisplaystheTestalarmsentmessage.
29.
OnaWebbrowser,typethefollowingURL:https://ptest9vm2.
platform.
avaya.
com/SMGRandlogontoSessionManager.
30.
GotoAlarms.
Thesystemdisplaysthefollowing:AdministeringSALonSystemPlatform112AdministeringAvayaAuraSystemPlatformApril2010AppendixC:HardwarefaultdetectionandalarmingHardwarefaultdetectionandalarmingSystemPlatformusesacombinationofIPMI(IntelligentPlatformManagementInterface)andRAIDtoolstomonitorserverhardwarehealth.
SystemPlatformperiodicallyusesIPMItoquerysensordata,andgeneratesanalarmforeachsensorthatisincriticalrange.
Thesetofsensorsvariesbyservertype.
SystemPlatformalsomonitorschassisstatus.
Ifanalarmisgenerated,thetextprovidedinthealarmprovidesadescriptionofthesensorfoundtobeincriticalrangeorofthechassisfault.
Thefollowingtableillustratestypicalalarmtextsthataregeneratedforsensorandchassis-typealarms.
AlarmtypeAlarmtextSensorDetectednon-okcomponentinSensorDataRepository(SDR):component=,id=,type=,sensorreading=,status=isuniquebyservertype(refertoinformationonmonitoredsensorsforeachservertype).
Example:Detectednon-okcomponentinSensorDataRepository(SDR):component=Planar3.
3V(0x16),id=7.
1(SystemBoard),type=Voltage,sensorreading=3.
294(+/-0)Volts,status=LowerCriticalChassisDetectedchassisstatusfault=,state=islistedunder"Monitoredchassisstatus"foreachservertype.
Example:Detectedchassisstatusfault=Cooling/FanFault,state=trueForasensoralarmtype,theinformationprovidedinthealarmstringisessentiallythesameinformationprovidedbyIPMI.
Usingtheexampleabove,ipmitoolcandisplayfulldetailasshownbelow:[root@mesaverde1log]#ipmitoolsensorget"Planar3.
3V"Locatingsensorrecord.
.
.
SensorID:Planar3.
3V(0x16)EntityID:7.
1SensorType(Analog):VoltageSensorReading:3.
294(+/-0)VoltsStatus:LowerCriticalLowerNon-Recoverable:naLowerCritical:3.
294LowerNon-Critical:naUpperNon-Critical:naAdministeringAvayaAuraSystemPlatformApril2010113UpperCritical:3.
564UpperNon-Recoverable:naAssertionEvents:lcr-AssertionsEnabled:lcr-ucr+DeassertionsEnabled:lcr-ucr+ThesensorIDinthisexampleipmitoolcommand("Planar3.
3V"fromtheexampleinthetableabove)isthecomponentinthealarmstring.
RAIDtoolsconstantlymonitorRAIDhealthandalarmwhenaproblemisdetected.
TheRAIDmonitoringtoolsdifferbyservertype.
Therefore,server-specificalarmsaredescribedseparately.
FaulttypesIPMIcandetecttwogeneralizedfaulttypes,namely,sensor-relatedandchassisstatus-relatedfaultsforvariousservertypes.
ThissectionpresentsinformationonthefaulttypesforS8510andS8800servers.
Pleasenotethattheinformationprovidedhereshouldnotbeconsideredexhaustiveastheserverhardwareandsensorsmayvaryovertime.
Further,afirmwareupdatemayalsochangethelistofmonitoredsensor-relatedfaults.
Pleasecheckyourvendor'sdocumentationtounderstandtheimplementationofmonitoredsensor-relatedfaults.
ForS8510Themonitoredsensor-relatedfaultsforS8510serverareasfollows:Temp(processor1,processor2,powersupply1,powersupply2)AmbientTempFANMODxxRPM(wherexxis1A,1B,2A,2B,etc.
)Current1,2(sensorforeachpowersupply)Voltage1,2(sensorforeachpowersupply)SystemLevelThemonitoredchassis-relatedfaultsforS8510serverareasfollows:PowerOverloadMainPowerFaultPowerControlFaultHardwarefaultdetectionandalarming114AdministeringAvayaAuraSystemPlatformApril2010DriveFaultCooling/FanFaultTheRAIDalarmsforS8510serverareassummarizedbelow:MessageNoteStorageServiceEventID:2048DevicefailedStorageServiceEventID:2049PhysicaldiskremovedStorageServiceEventID:2056Virtualdiskfailed/VirtualdiskconsistencycheckfailedStorageServiceEventID:2057VirtualdiskdegradedStorageServiceEventID:2076Virtualdiskfailed/VirtualdiskconsistencycheckfailedStorageServiceEventID:2080PhysicaldiskInitializationorrebuildfailStorageServiceEventID:2083PhysicaldiskInitializationorrebuildfailStorageServiceEventID:2102TemperatureexceededthemaximumfailurethresholdStorageServiceEventID:2103TemperaturedroppedbelowtheminimumfailurethresholdStorageServiceEventID:2163HDDrebuildcompletedwitherror(s)StorageServiceEventID:2169ControllerbatteryneedstobereplacedStorageServiceEventID:2268StorageManagementhaslostcommunicationwiththecontrollerStorageServiceEventID:2270PhysicaldiskInitializationorrebuildfailStorageServiceEventID:2272PatrolReadfoundanuncorrectablemediaerrorStorageServiceEventID:2273AblockonthephysicaldiskhasbeenpuncturedbythecontrollerStorageServiceEventID:2282HotspareSMARTpollingfailedStorageServiceEventID:2289Multi-bitECCerroroncontrollerDIMMFaulttypesAdministeringAvayaAuraSystemPlatformApril2010115MessageNoteStorageServiceEventID:2299BadPHYorphysicalconnectionStorageServiceEventID:2307Badblocktableisfull.
UnabletologblockStorageServiceEventID:2320SinglebitECCerror.
TheDIMMiscriticallydegradedStorageServiceEventID:2321ControllerDIMMiscriticallydegradedStorageServiceEventID:2340Thebackgroundinitialization(BGI)completedwithuncorrectableerrorsStorageServiceEventID:2347RebuildfailedduetoerrorsonthesourceortargetphysicaldiskStorageServiceEventID:2348RebuildfailedduetoerrorsonthesourceortargetphysicaldiskStorageServiceEventID:2349AbaddiskblockcouldnotbereassignedduringawriteoperationStorageServiceEventID:2350UnrecoverablediskmediaerrorduringtherebuildorrecoveryRefertotheSystemsHardwareOwner'smanualfoundathttp://support.
dell.
com/support/edocs/systems/pe1950/ortotheMessageReferenceGuideathttp://support.
dell.
com/support/edocs/software/svradmin/5.
3/index.
htmformoreinformationontroubleshootingandfaultresolution.
ForS8800Themonitoredsensor-relatedfaultsforS8800serverareasfollows:AmbientTempAltitudeAvgPowerPlanar3.
3VPlanar5VPlanar12VPlanarVBATFanxxTach(wherexxis1A,1B,2A,2B,andsoon)Hardwarefaultdetectionandalarming116AdministeringAvayaAuraSystemPlatformApril2010Themonitoredchassis-relatedfaultsforS8800serverareasfollows:PowerOverloadMainPowerFaultPowerControlFaultDriveFaultCooling/FanFaultTheRAIDalarmsforS8800serverareassummarizedbelow:MessageNoteDriveSlotsensorDrive[0–9]DrivePresentedDeassertedThismessageindicatesthatadrivehasbeenremoved.
Noalarmmessageisgeneratedwhenthedriveisinserted.
DriveSlotsensorDrive[0–9]DrivePredictiveFailureAssertedApredictivefailurewasdetected.
Thedrivewilllikelyneedtobereplaced.
DriveSlotsensorDrive[0–9]InCriticalArrayAssertedAcriticalfailurewasdetected.
Thedrivewilllikelyneedtobereplaced.
DriveSlotsensorDrive[0–9]InFailedArrayAssertedThedevicehasfailed.
Thedrivewilllikelyneedtobereplaced.
DriveSlotsensorDrive[0–9]InRebuildAbortAssertedTherebuildhasfailed.
RefertotheProblemDeterminationandServiceGuideatftp://ftp.
software.
ibm.
com/systems/support/system_x_pdf/59y6780.
pdfformoreinformationontroubleshootingandfaultresolution.
GeneralsoftwarefaultsAlarmtextProblem/ActionVSPWebConsolecannotstartduetolibvirt_jnicannotbefound.
Checktheexistenceof/usr/local/lib/libvirt_jni.
sooncdom;ifitisasymbolic,ensureitpointstoavalidsharedlib.
GeneralsoftwarefaultsAdministeringAvayaAuraSystemPlatformApril2010117AlarmtextProblem/ActionVSPWebConsolecannotstartduetomissingconfigurationfile(vsp.
properties).
Checktheexistenceof/opt/avaya/vsp/tomcat/lib/vsp.
propertiesoncdom.
VSPWebconsoleencounteredproblemwhilestarting,restartingorstoppingofNTPService.
CheckthelogsofthesystembyenablingFINEinthe/opt/avaya/vsp/tomcat/webapps/webconsole/WEB-INF/classes/log4j.
xmlfileoncdom,orcheckthattheNTPserviceexists.
VSPWebconsoleencounteredproblemrunning/opt/avaya/vsp/bin/vsp_rsyslog_rotate.
shCheckexistenceof/etc/logrotate.
d/vsp_rsyslogandpermissions(shouldbe644andownedbyroot/root)oncdom.
VSPWebconsoleencounteredproblemwithlog4j.
xmlfile.
Checktheexistenceof/opt/avaya/vsp/tomcat/webapps/webconsole/WEB-INF/classes/log4j.
xmloncdom.
CDomWebconsoletomcatdied.
Checktomcatlogfilesin/opt/avaya/vsp/tomcat/logs/catalina.
outoncdom.
VSPBackupfailed.
Checkthedetailsin/vspdata/backup/backup.
loglogfile.
BackuparchivecouldnotbesentonserverVerifythatSFTPisenabledontheserver.
LogintotheSystemPlatformManagementConsole.
ClickServerManagement>Backup/Restore.
ClickBackup.
SelectSFTPfromtheBackupMethodlist.
VerifythattheSFTPDirectoryandSFTPUsernamearevalidon.
Re-entertheSFTPPassword.
Checkthedetailsin/var/log/vsp/vsp-all.
log.
BackuparchivecouldnotbesentonmailVerifythatisavalidemailaddressthatiscurrentlyabletoacceptemail.
Checkthedetailsin/var/log/vsp/vsp-all.
log.
Restoreofarchivefilefailed.
Checkthedetailsin/vspdata/backup/backup.
loglogfile.
Inthe"Alarmtext"and"Problem/Action"columns:isthenameofabackuparchivefile.
isthenameorIPaddressofaserverwhereSFTPisenabledsothatabackuparchivefilecanbesenttotheserver.
isavalidemailaddress.
Hardwarefaultdetectionandalarming118AdministeringAvayaAuraSystemPlatformApril2010LifecyclemanagerfaultsSystemPlatformhasalifecyclemanagerthatmonitorsthehealthofanyvirtualmachinesthatwereinstalledaspartofaproducttemplate.
Anapplicationinthevirtualmachineisexpectedtoprovideaperiodicheartbeat.
Ifthisheartbeatismissedforanumberofperiods,thelifecyclemanagerwillrebootthevirtualmachine.
Ifthelifecyclemanagerdoesnotseeheartbeatsafterarebootforanumberofconsecutivereboots,thelifecyclemanagermayshutdownthevirtualmachine.
Eachproducttemplatedefinesitsowncontractforthefrequencyoftheheartbeat(howoftentoexpecttheheartbeat),thenumberofconsecutivemissedheartbeatsbeforerebooting,andthenumberofconsecutiverebootsbeforeshuttingdown.
AlarmtextProblem/ActionVSPVirtualsystemsanityheartbeatfailureCheckthevirtualsystemlogtoseewhysanityheartbeatfailed.
VSPVirtualsystemrebootastheresultofsanityheartbeatfailuresCheckthevirtualsystemlogtoseewhysanityheartbeatfailed.
VSPVirtualsystemsanityrebootfailed.
Checkthedetailsin/var/log/vsp/vsp-all.
logoncdom.
VSPVirtualsystemshutdownastheresultofsanityheartbeatfailuresCheckthevirtualsystemlogtoseewhysanityheartbeatfailed.
Inthe"Alarmtext"column,isthevirtualmachine'snameasitappearsintheSystemPlatformManagementConsoleundertheVirtualMachineManagementpage.
PerformancefaultsAlarmtextProblem/ActionVSPHighCPUUsagedetectedforCheckThismayrequiretroubleshootingwithinthevirtualmachine.
VSPHighWebconsoleheapusageCheckWebconsoleisOK.
VSPHighNetworkI/O(Tx)fromforCheckThismayrequiretroubleshootingwithinthevirtualmachine.
VSPHighNetworkI/O(Rx)fromforCheckLifecyclemanagerfaultsAdministeringAvayaAuraSystemPlatformApril2010119AlarmtextProblem/ActionThismayrequiretroubleshootingwithinthevirtualmachine.
VSPHighLoadAverageCheckThismayrequiretroubleshootingwithinthevirtualmachine.
VSPLowlogicalvolumefreespaceFreesomespaceonlogicalvolumeThismayrequiretroubleshootingwithinthevirtualmachine.
VSPLowvolumegroupfreespace(VolGroup00)FreesomespaceonvolumegroupVolGroup00indom0.
Thismayrequiretroubleshootingwithinthevirtualmachine.
VSPHighdiskreadrateondisk(sda)Fromdom0,checkthedevicesda.
VSPHighdiskwriterateondisk(sda)Fromdom0,checkthedevicesda.
VSPHighWebconsolepermgenusageLogintotheSystemPlatformManagementConsole.
ClickVirtualMachineManagement>Manage.
Clickthecdomlink.
ClickReboot.
Note:IfunabletologintoSystemPlatformManagementConsole,usethexmrebootcommandwhileloggedintodom0.
VSPHighWebconsoleopenfilesLogintotheSystemPlatformManagementConsole.
ClickVirtualMachineManagement>Manage.
Clickthecdomlink.
ClickReboot.
Note:IfunabletologintoSystemPlatformManagementConsole,usethexmrebootcommandwhileloggedintodom0.
VSPHighSALAgentheapusageLogintotheSystemPlatformManagementConsole.
ClickVirtualMachineManagement>Manage.
Clickthecdomlink.
ClickReboot.
Note:IfunabletologintoSystemPlatformManagementConsole,usethexmrebootcommandwhileloggedintodom0.
VSPHighSALAgentpermgenusageLogintotheSystemPlatformManagementConsole.
ClickVirtualMachineManagement>Manage.
Hardwarefaultdetectionandalarming120AdministeringAvayaAuraSystemPlatformApril2010AlarmtextProblem/ActionClickthecdomlink.
ClickReboot.
Note:IfunabletologintoSystemPlatformManagementConsole,usethexmrebootcommandwhileloggedintodom0.
HighMemoryUsageinDomain-0CheckMemoryUsageinDomain-0.
HighMemoryUsageincdomCheckMemoryUsageincdom.
Inthe"Alarmtext"and"Problem/Action"columns:isthenameofthevirtualmachineasitappearsintheSystemPlatformManagementConsoleundertheVirtualMachineManagementpage.
isthenameofalogicalvolumeusedasavirtualdiskwithinavirtualmachine.
HighAvailabilityfaultsPriortoSP1.
1.
1.
7.
2AlarmtextProblem/ActionVSPWebconsoleencounteredproblemwhilechangingfullresyncspeed.
Checkthedetailsin/var/log/vsp/vspha.
loglogfile.
VSPWebconsoleencounteredproblemwhilepausingfullresynchronisation.
Checkthedetailsin/var/log/vsp/vspha.
loglogfile.
VSPWebconsoleencounteredproblemwhileresumingfullresynchronisation.
Checkthedetailsin/var/log/vsp/vspha.
loglogfile.
VSPWebconsoleencounteredproblemwhilecreatingfailoverconfiguration.
Checkthedetailsin/var/log/vsp/vspha.
loglogfile.
VSPWebconsoleencounteredproblemwhileremovingfailoverconfigurationCheckthedetailsin/var/log/vsp/vspha.
loglogfile.
VSPWebconsoleencounteredproblemwhileswitchingoverthemachines.
Checkthedetailsin/var/log/vsp/vspha.
loglogfile.
HighAvailabilityfaultsAdministeringAvayaAuraSystemPlatformApril2010121AlarmtextProblem/ActionVSPWebconsoleencounteredproblemwhilestartingfailover.
Checkthedetailsin/var/log/vsp/vspha.
loglogfile.
VSPWebconsoleencounteredproblemwhilestoppingfailover.
Checkthedetailsin/var/log/vsp/vspha.
loglogfile.
VSPWebconsoleencounteredproblemwhilesavingipmiparameters.
Checkthedetailsin/var/log/vsp/vspha.
loglogfile.
VSPWebconsoleencounteredproblemwhiledeletingipmiparameters.
Checkthedetailsin/var/log/vsp/vspha.
loglogfile.
VSPWebconsoleencounteredproblemwhileretrievingstatusoffailover.
Checkthedetailsin/var/log/vsp/vspha.
loglogfileindom0.
VSPWebconsoleencounteredproblemwhilesynchronisingservicestosecondarynode.
Checkthedetailsin/var/log/vsp/vspha.
loglogfileindom0.
VSPWebconsoleencounteredproblemwhileremovingtemplatevirtualmachinesfromfailover.
Checkthedetailsin/var/log/vsp/vspha.
loglogfileindom0.
VSPWebconsoleencounteredproblemwhileaddingtemplatevirtualmachinesintofailover.
Checkthedetailsin/var/log/vsp/vspha.
loglogfileindom0.
VSPWebconsoleencounteredproblemwhileupgradingconsolevirtualmachine.
Checkthedetailsin/var/log/vsp/vspha.
loglogfileindom0.
Notabletoreadmachinehardwarestate;errorexecutingIPMIcommand:Checkthedetailsin/var/log/vsp/vspha.
loglogfileindom0.
Migratingresourcestoothernode;acriticalconditionhasexistedforlongerthanxxminutesSeekappropriateserviceforthecriticalcondition.
Failedmigratingresourcestoothernode:Check/var/log/vsp/vspha.
logand/var/log/vsp/ha-logforpossiblecauses.
Inthe"Alarmtext"column,isthefullyqualifieddomainname.
Hardwarefaultdetectionandalarming122AdministeringAvayaAuraSystemPlatformApril2010SP1.
1.
1.
7.
2andlaterAlarmtextProblem/ActionVSPWebconsoleencounteredproblemwhileretrievingstatusoffailover.
Checkthedetailsin/var/log/vsp/vspha.
loglogfileindom0.
VSPWebconsoleencounteredproblemwhilesynchronisingservicestosecondarynode.
Checkthedetailsin/var/log/vsp/vspha.
loglogfileindom0.
VSPWebconsoleencounteredproblemwhileremovingtemplatevirtualmachinesfromfailover.
Checkthedetailsin/var/log/vsp/vspha.
loglogfileindom0.
VSPWebconsoleencounteredproblemwhileaddingtemplatevirtualmachinesintofailover.
Checkthedetailsin/var/log/vsp/vspha.
loglogfileindom0.
VSPWebconsoleencounteredproblemwhileupgradingconsolevirtualmachine.
Checkthedetailsin/var/log/vsp/vspha.
loglogfileindom0.
Notabletoreadmachinehardwarestate;errorexecutingIPMIcommand:(raisedon)Checkthedetailsin/var/log/vsp/vspha.
loglogfileindom0.
Migratingresourcestoothernode;acriticalconditionhasexistedforlongerthanxxminutes(raisedon)SeekappropriateserviceforthecriticalconditionFailedmigratingresourcestoothernode:(raisedon)See/var/log/vsp/vspha.
logand/var/log/vsp/ha-logforpossiblecausesStartHAfailed:(raisedon)See/var/log/vsp/vspha.
logand/var/log/vsp/ha-logforpossiblecausesStopHAfailed:(raisedon)See/var/log/vsp/vspha.
logand/var/log/vsp/ha-logforpossiblecausesHAFailoverfailed:(raisedon)See/var/log/vsp/vspha.
logand/var/log/vsp/ha-logforpossiblecausesCrossoverconnectionbetweenthemachinesisbroken(raisedon)CheckthecrossovernetworkconnectionbetweenthemachinesFailoveroccurred,activatingthisnode(raisedon)Checkthe/var/log/vsp/ha-logand/var/log/messagesforthecauseoffailoverHighAvailabilityfaultsAdministeringAvayaAuraSystemPlatformApril2010123AlarmtextProblem/ActionFailoverhasfailedbecausedirectoryforenvironmentISOimagedoesnotexist(raisedon)Ensurethatthedirectoryexistsindom0andisaccessibleInthe"Alarmtext"column:istheshorthostname(notthefullyqualifieddomainname).
isamoredetailederrorstring.
isaLinux-styledirectoryname.
Hardwarefaultdetectionandalarming124AdministeringAvayaAuraSystemPlatformApril2010IndexAaccessingsystemplatforminformation10accessingsystemplatformthroughservicesport.
.
.
.
.
.
12addingstaticroute42administeringsystemplatform9adminsteringusers73alarmconfiguration45,46alarms50ApplicationEnablementServices107auditlogs26BbackingupusingSystemPlatformManagementConsole.
.
.
.
.
61backingupusingSystemPlatformManagementConsole62backupabout60backuphistory64,66backupmethod63backupnowlocations59,63backupsystemplatform59,63backupSystemPlatform63Ccalendar29certificatemanagement47CertificateManagementpagefielddescriptions49changeLDAPpassword81changepassword82changingSystemPlatformuserpasswords82checkingcorrectsystemstateusingSystemPlatformManagementConsole.
.
.
.
.
70checkingsystemisincorrectstateusingCLI71CommunicationManager107CommunicationManagerMessaging107configurationrestoringforSystemPlatform64configurationchangesapply106ConfigureFailoverfielddescriptions54configuringamanagedelement106configuringalarms45configuringandeditingsystemplatformnetworksettings38configuringdateandtime28,29,31configuringenterpriseLDAP79configuringloglevels34configuringSALEnterprise103configuringSALgateway102configuringSystemPlatformhighavailabilityfailover.
.
.
.
53configuringsystemplatformnetworksettings36configuringSystemPlatformnetworksettings38configuringsystemplatformsystemconfigurationparameters36createusers73,76Ddateandtimeconfiguration28dateandtimeconfigurationbuttondescriptions33dateandtimeconfigurationfielddescriptions32deleteusers73,78deletingafolder60deletingatemplatefile60deletingstaticroute43disablingIPforwarding12downloadingagraph58Eeditusers73,77editingethernetconfiguration44editingstaticroute43ejectCD59ejectDVD59ejectingtheCDorDVD59email63enablingIPforwarding12enterpriseLDAP79configuringinSystemPlatform79EnterpriseLDAPpagefielddescriptions80ethernetconfiguration44ethernetconfigurationbuttondescriptions45eventlogs26AdministeringAvayaAuraSystemPlatformApril2010125Ffaultdetectionandalarminghardwarefault113faulttypes114,116forS8510114forS8800116filemanager60Ggeneralsoftwarefaults117generatingagraph58Hhighavailabilityfailoverhowitworks51removingconfiguration56switchingfromsimplexmode55switchingfromsimplexmodeaftertemplateconfiguration57switchingtosimplexmodefortemplateconfiguration57highavailabilityfailovermodestopping56highavailabilityfaultspriortoSP1.
1.
1.
7.
2121SP1.
1.
1.
7.
2andlater123howhighavailabilityfailoverworks95Iinstallingpatches20LlaunchingSALGateway101LDAPpassword81legalnotices2licensemanagement49localandremotepatchsearching19localandremotepatchbuttondescriptions24localandremotepatchfielddescriptions23localmanagement73localmanagementbuttondescriptions79localmanagementfielddescriptions79loglevels26,33logviewer26,27loggingconfiguration33loggingconfigurationfielddescriptions36Mmanagesystemplatformusers76–78manageddevice107managinglicenses50managingSALsettings50managingservers19managingservicecontrol105managingvirtualmachines14,15MediaServices107Models107Nnetworkconfiguration38networkconfigurationfielddescriptions40networkmanagementsystemconfiguring105NMS105notices,legal2NTP28,31ntpd28,31Ppatchdetail25patchdetailfielddescriptions25patchdetailbuttondescriptions25patchlist24patchesinstallingonSystemPlatformHighAvailabilitysystems21performancestatistics57,58prerequisitesforconfiguringSystemPlatformHighAvailabilityFailover52productdevicemanagedbySALGateway107Rre-enablingfailedpreferrednodetoHA93Re-enablingfailedstandbynodetoHA93rebootingavirtualmachine15rebootingtheSystemPlatformServer66remoteaccess50remoteaccessserverconfiguring104removingatimeserver31removingpatches22126AdministeringAvayaAuraSystemPlatformApril2010restore65restoringSystemPlatformconfigurationinformation.
.
.
.
64retentionparameters34SSAL1.
5Gateway109SALEnterprise109SALGateway107SALGatewayconfiguration101SALgatewaymanagement50SALgatewaymanagementbuttondescriptions51scheduleabackup63schedulingabackup62selectingenterpriseLDAPcertificate49selectingSystemPlatformcertificate48Self-SignedCertificate109servermanagement19servermanagementfielddescriptions24serverrebootandshutdown66serverrebootandshutdownbuttondescriptions.
.
.
.
.
.
.
.
69serverrebootshutdownfielddescriptions67SessionManager109SFTP63SGMR109shuttingdownaserverusingSystemPlatformManagementConsole70shuttingdownavirtualmachine15shuttingdownbothserversusingSystemPlatformManagementConsole.
.
.
.
.
72shuttingdownbothserversseparately69shuttingdownbothserversusingCLI70shuttingdowntheSystemPlatformserver67shuttingdownthesystemrunninginHighAvailabilitymode69SIPEnablementServices107softwarefaultdetectionandalarminglifecyclemanagerfaults119performancefaults119solutiontemplate18staticroute41staticrouteconfiguration44stoppingHighAvailability69switchbetweensimplexandhighavailabilityfailovermodes54synchronizewithtimeserver28,31systemconfiguration36systemconfigurationfielddescriptions37systemlogs26SystemPlatform107,109SystemPlatformmanagementconsole10SystemPlatformManagementConsole9Ttroubleshootingatemplateisinstalledonremotenode87,88activeserverfails90cannotaccessSystemPlatformManagementConsoleafterStartFailover89cannotestablishcommunicationthroughcrossovernetworkinterface85cannotestablishHAnetworkinterface88cannotestablishSSLcommunication86clusternodesarenotequal86dataswitchfails90differentplatformversionsagainstclusternodes.
.
.
.
88DVDdoesnotmount83generalissueswiththesystemandwantstocontactsupport84heartbeatlinkfails91highavailabilityfailoverdoesnotwork91localIPaddressprovided85NICsarenotactiveonbothsides87re-enablingfailedpreferrednodetoHA93Re-enablingfailedstandbynodetoHA92resourcesarenotstartedonanynodeandcannotaccessSystemPlatformManagementConsole.
89standbyfirst-bootsequenceisnotyetfinished.
.
.
.
86StartLDAPserviceonSystemDomain(Dom-0).
.
.
.
91SystemPlatformManagementConsolenotaccessible92virtualmachinehasnoconnectivity83virtualmachinewithdedicatedNICmayfailafterSystemPlatformupgrade94Uuploadinganddownloadingpatches19UserAdministration73UtilityServer107Vviewinglogfiles26,27viewingperformancestatistics57viewingvirtualmachinedetails14virtualmachineconfigurationparametersbuttondescriptions18AdministeringAvayaAuraSystemPlatformApril2010127virtualmachineconfigurationparametersfielddescriptions16virtualmachinemanagement12virtualmachinemanagementbuttondescriptions.
.
.
.
.
.
14virtualmachinemanagementfielddescriptions13VSP107WWebLM50WebLMLicenseManager49128AdministeringAvayaAuraSystemPlatformApril2010