Specifications

2
Software Architecture
32
InadditiontotheHPIdata,automaticoperationsaresynchronizedwiththepeerHPIservers
tokeepHPIdatabasesinsync.Theseoperationsarecalledbythefollowingfunctionsandare
onlysynchronizedwiththestandbyHPIserverwhentheHPIapplicationmakestherequestto
theactiveHPIserver.
•
saHpiDiscover()–Thisfunctionovercomespotentiallatenciesinthehot‐swapmechanism
andkeepstheresourcepresencetable(RPT)updated.Thisoperationissynchronizedto
thepeerHPIserversoitcanupdateitsRPT.
Note:ThesaHpiDiscover()functionisnotmeanttoperformanyinitializationordiscovery
actionsandshouldnotbeusedforanHPIimplementation.However,thefunctioncanbe
usedindebugsituations(refertoTable 15onpage 126forexamples).
• saHpiEventLogClear()–ThisfunctionclearsthespecifiedHPIeventloginbothactiveand
standbyHPIservers.
• saHpiParmControl()–Thisfunctionsavescustomconfigurationsforresources.The
configurationsaresynchronizedwiththepeerHPIservertoensurelocalHPIconfiguration
filesareupdated.
DuringHPIserverinitialization,thestandbyHPIserversendsarefreshrequesttotheactive
HPIserveroverthesynchronizationmedium.Uponreceptionofthisrequest,theactiveHPI
serversendsanydatathatneedstobesynchronizedtothestandbyHPIserver.Thestandby
HPIserverbecomesfullyinitializedandtheHPIservicebecomesfullyredundantoncethe
refreshsyncwiththeactiveHPIser veriscompleted.
ThedynamicredundancybetweentheactiveandstandbyHPIserversenablethesystem
managertogetaconsistentviewoftheRadisyssystemregardlessoffailovers,andensures
thatasystemmanagementinterfaceisalwaysavailable.