RadiSys ATCA-4616 Specifikace stáhnout pdf (Strana 27)

Software Architecture

Peer communication loss causes failover

IfcommunicationbetweenthepeerShMCsbreaksdown,thefirstoftheprevious

communicationmechanisms(ShMC‐to‐ShMCoverIPMB)fails.ThestandbyShelfManager

attemptstopingitspeerovertheLANinterfacetoconfirmitsfullhighavailability(HA)state.

Ifthisfails,thiscausesthestandbyShelfManagertoeffectafailover,assumetheactiverole,

andsendoutaneventnotifyingalleventreceiversofthefailover.Thiscanhappenifthe

activeShelfManagerwashot‐swappedfromtheshelfimproperlyorifthelocalIPMBonthe

activeShelfManagerhardwarefailed,causingittode‐linkitselffromIPMB‐0.

Watchdog expiration causes failover

IftheoperatingenvironmentthattheShMSisrunningonfails,theIPMIwatchdoginthe

ShMCexpires,causingittoresetthemodulehostingtheShMSsothatitrebootstoagood

state.IfthishappensintheactiveShelfManager,afailovertothestandbyShelfManager

occursandthepreviouslyactiveShelfManagerassumesthestandbyroleafteritreboots.

However,ifthishappensinthestandbyShelfManager,thennofailoverisrequired,buta

payloadresettoagoodworkingstandbymodestillhappens.

Peer communication loss causes failover, non-redundancy

IfthepeerShMSsarenotabletomaintaincommunicationovertheLANinterface,they

attempttosynchronizeovertheIPMB.Ifthatfailsaswell,thestandbyShMSassumesthe

activerole.ThisprotectsagainstanunlikelyconditionwheretheactiveShMShasan

unrecoverablefailure,butkeepsrunninginanon‐functionalstate.Withcommunicationover

theLANinterfacelost,theShelfManagersarenolongerconsideredredundant,andtheShelf

Managerredundancysensoronpage 28issuesanalarm.

Watchdog expiration causes reboot of non-redundant SCM

IfnostandbyShelfManagerispresentandthecommunicationbetweentheactiveShMSand

ShMCbreaksdown,theShMCwatchdogstillexpires,causingasoftwarerebootoftheSCM.In

thiscase,theShelfManagerstillrebootstoagoodworkingstateandreassumestheactive

role.Therebootresults

indowntime,becausethereisnoShMStomonitorandrespondto

eventsfromshelfcomponentswhiletheShelfManagerpayloadisrebooting.

Initiating a failover manually

Youcanmanuallyinitiateafailoverby:

•Usingtheplatform‐managementCLI.

•UsingHPI‐Controlnumber0x1010inresource0x02.RefertotheShelfManagerfailover

controlsectionoftheSAFMappingSpecificationformoreinformation.

• Tog gling(openingandthenclosing)thebottomejectorlatchoftheactiveSCM.

•Poweringofforpower

cyclingtheactiveSCMusingHPIwiththe

saHpiResourcePowerStateSet()function.

•ExtractingtheactiveSCMeithermanuallyorusingHPIwiththe

saHpiHotSwapActionRequest()function.

1 2 ... 22 23 24 25 26 27 28 29 30 31 32 ... 145 146

Žádné komentáře

RadiSys ATCA-4616 Specifikace Strana 27