DN0628311-Configuring SS7 Signaling Transport Over IP for IPA-RNC

WCDMA RAN, Rel. RU40,Operating Documentation,Issue 06

Configuring SS7 SignalingTransport over IP for IPA-RNC DN0628311Issue 04CApproval Date 2013-09-22

Theinformationinthisdocumentissubjecttochangewithoutnoticeanddescribesonlytheproductdefined in the introduction of this documentation. This documentation is intended for the use ofNokiaSolutionsandNetworkscustomersonlyforthepurposesoftheagreementunderwhichthedocumentissubmitted,andnopartofitmaybeused,reproduced,modifiedortransmittedinanyformormeanswithoutthepriorwrittenpermissionofNokiaSolutionsandNetworks.Thedocumen-tationhasbeenpreparedtobeusedbyprofessionalandproperlytrainedpersonnel,andthecus-tomerassumesfullresponsibilitywhenusingit.NokiaSolutionsandNetworkswelcomescustomercommentsaspartoftheprocessofcontinuousdevelopmentandimprovementofthedocumenta-tion.

The informationor statementsgiven in thisdocumentationconcerning thesuitability, capacity, orperformanceofthementionedhardwareorsoftwareproductsaregiven"asis"andallliabilityaris-inginconnectionwithsuchhardwareorsoftwareproductsshallbedefinedconclusivelyandfinallyin a separate agreement between Nokia Solutions and Networks and the customer. However,NokiaSolutionsandNetworkshasmadeallreasonableeffortstoensurethattheinstructionscon-tained in thedocumentareadequateand freeofmaterialerrorsandomissions.NokiaSolutionsandNetworkswill, if deemednecessarybyNokiaSolutionsandNetworks, explain issueswhichmaynotbecoveredbythedocument.

NokiaSolutionsandNetworkswillcorrecterrorsinthisdocumentationassoonaspossible.INNOEVENTWILLNokiaSolutionsandNetworksBELIABLEFORERRORS INTHISDOCUMENTA-TIONORFORANYDAMAGES, INCLUDINGBUTNOTLIMITEDTOSPECIAL,DIRECT, INDI-RECT,INCIDENTALORCONSEQUENTIALORANYLOSSES,SUCHASBUTNOTLIMITEDTOLOSSOFPROFIT,REVENUE,BUSINESSINTERRUPTION,BUSINESSOPPORTUNITYORDA-TA,THATMAYARISEFROMTHEUSEOFTHISDOCUMENTORTHEINFORMATIONINIT.

Thisdocumentationandtheproductitdescribesareconsideredprotectedbycopyrightsandotherintellectualpropertyrightsaccordingtotheapplicablelaws.

NSN is a trademark ofNokiaSolutions andNetworks.Nokia is a registered trademark ofNokiaCorporation.Otherproductnamesmentionedinthisdocumentmaybetrademarksoftheirrespec-tiveowners,andtheyarementionedforidentificationpurposesonly.

CopyrightNokiaSolutionsandNetworks2013.Allrightsreserved

f Important Notice on Product Safety Thisproductmaypresentsafetyrisksduetolaser,electricity,heat,andothersourcesof

danger.

Only trained and qualified personnelmay install, operate,maintain or otherwise handlethisproductandonlyafterhavingcarefully read thesafety informationapplicable to thisproduct.

Thesafety information isprovided in theSafety Informationsection in theLegal,SafetyandEnvironmentalInformationpartofthisdocumentordocumentationset.

NokiaSolutionsandNetworksiscontinuallystrivingtoreducetheadverseenvironmentaleffectsofitsproductsandservices.Wewouldliketoencourageyouasourcustomersanduserstojoinusinworking towards a cleaner, safer environment. Please recycle product packaging and follow therecommendationsforpoweruseandproperdisposalofourproductsandtheircomponents.

IfyoushouldhavequestionsregardingourEnvironmentalPolicyoranyoftheenvironmentalser-vicesweoffer,pleasecontactusatNokiaSolutionsandNetworksforanyadditionalinformation.

ConfiguringSS7SignalingTransportoverIPforIPA-RNC

2 DN0628311 Issue:04C

Table of ContentsThisdocumenthas51pages

Summaryofchanges..................................................................... 6

1 SignalingtransportoverIP(M3UA)............................................... 71.1 Association.....................................................................................71.1.1 SCTPmulti-homing........................................................................ 81.1.2 SCTPstream..................................................................................91.2 Associationset............................................................................. 101.3 SGP-ASPcommunication.......................................................... 121.4 IPSP-IPSPcommunication.......................................................... 131.5 SignalingoverIPstatistics........................................................... 14 2 UseofM3UAstack...................................................................... 162.1 SGP-ASPcommunication............................................................ 162.1.1 ExampleofM3UAusage............................................................. 172.2 IPSP-IPSPcommunication.......................................................... 182.2.1 UseofIPSP-IPSPexampleattheM3UA.....................................192.3 Routingkeyandroutingcontext...................................................192.4 SignalingPointManagementCluster...........................................202.5 MessagestructureofM3UA.........................................................22 3 BasicstructuresofSS7signalingoverIPnetwork.......................24 4 Planningsiteconfigurationforsignaling.......................................26 5 PlanningM3UAnetwork...............................................................31 6 CreatingM3UAconfiguration....................................................... 33 7 ModifyingSIGTRANparameters..................................................377.1 ModifyingassociationsetlevelparametersofM3UA.................. 377.2 ModifyingSCTPassociationlevelparameters.............................40 8 DeletingIPsignalinglinks............................................................ 45 9 SignalingtransportoverIPtroubleshooting................................. 469.1 IPsignalinglinkactivationfails.....................................................469.2 SCTPassociationfails................................................................. 479.3 PathofSCTPassociationfails.....................................................489.4 Listofdebuggingcommandsinafailurecase............................. 51


Issue:04C DN0628311 3

List of FiguresFigure1 SCTPretransmission............................................................................8Figure2 Symmetricnetworklayout.................................................................... 9Figure3 Asymmetricnetworklayout...................................................................9Figure4 ExampleofanIPtypeSS7signalinglink........................................... 10Figure5 Associationset....................................................................................11Figure6 AnexampleofSGP-ASPcommunication.......................................... 13Figure7 AnexampleofabasicIPSP-IPSPconfigurationwithapointtopoint

connectioninsidetheIPnetwork........................................................13Figure8 AnexampleofSGP-ASPcommunication.......................................... 16Figure9 AnexampleofaSignalingGatewaybetweentwonetworkelementsin

differentprotocols............................................................................... 18Figure10 AnexampleofcombinedSignalingGatewayandIPSP-IPSP........... 19Figure11 AnexampleofSignalingPointManagementCluster......................... 21Figure12 MessagestructureofM3UA............................................................... 23Figure13 BasicexampleofanetworkthatusesIP............................................24Figure14 ExampleofpointtopointIPconnection............................................. 24Figure15 ExampleofsignalinglinksrelatedtoSPMC.......................................32


4 DN0628311 Issue:04C

List of TablesTable1 Summaryofsuggestedparametersets..............................................42


Issue:04C DN0628311 5

Summary of changesChangesbetweendocumentissuesarecumulative.Therefore,thelatestdocumentissuecontainsallchangesmadetopreviousissues.

Pleasenotethattheissuenumberingsystem,safetyinformation,andproductnamingpracticearechanging.Formoreinformation,seeGuide to WCDMA RAN OperatingDocumentation.

Changes between Issues 04B (2013-09-13, RU40) and 04C (2013-11-22, RU40)AddedoneDSCPfieldinSCTPparameters,followingchaptersareupdatedforthefeature:

Planningsiteconfigurationforsignaling ModifyingSCTPassociationlevelparameters

Changes between Issues 04A (2013-07-25, RU40) and 04B (2013-09-13, RU40)Path of SCTP association fails (9.3)

Addaspecialimplementationfortroubleshooting.

Changes between Issues 04 (2013-04-15, RU40) and 04A (2013-07-25,RU40)Path of SCTP association fails (9.3)

Addaspecialimplementationfortroubleshooting.

Summaryofchanges ConfiguringSS7SignalingTransportoverIPforIPA-RNC

6 DN0628311 Issue:04C

1 Signaling transport over IP (M3UA)TheinformationinthisdocumentrelatestoDX200andIPA2800-basedproducts.

SignalingtransportoverIP(SIGTRAN)containsseveraluseradaptationlayers,oneofwhichisdescribedhere:theM3UA(MTP3UserAdaptationLayer).

M3UAisaprotocolforsupportingthetransportofanySS7MTP3-Usersignaling(forexample,ISUPandSCCPmessages)overIPusingtheservicesoftheStreamControlTransmissionProtocol(SCTP).Also,provisionismadeforprotocolelementsthatenableaseamlessoperationoftheMTP3-UserpeersintheSS7andIPdomains.

M3UAprotocolistobeusedinIP-basedIuandIurinterfacesofRNC,whereSignalingConnectionControlPart(SCCP)isrequired.SS7signalingcanalsobereceivedoverATMinterfaceusingtheSS7MessageTransferPart(MTP)toprovidetransport.

1.1 AssociationAnSCTPassociationisarelationshipbetweentwocommunicatingpeers.ApplicationofanSCTPisestablishingandmaintaininganassociation.ConfigurationofanSCTPassociationisdoneintheapplicationlevel.Ifbothcommunicatingpeersarebasedonoursystem,theSCTPassociationhasbeenestablishedbetweentwosignalingunitsbyclientpeer.TheSCTPassociationusesthefollowingaddressparameters:sourceportnumber,listofsourceIPaddresses,destinationportnumber,andlistofdestinationIPaddresses.Ifoneofthoseaddressparametersisdifferent,itmeansthatanewassociationshouldbeestablished.Anassociationcanhaveseverallogicalpaths(sourceanddestinationIPaddresspair);thatkindofconnectioniscalledamulti-homedconnection.SCTPcanuseamulti-homedconnectionbutaTCPdoesnotknowthatkindofarchitecture.Forthisreason,anSCTPassociationismuchmorefaulttolerantthanaTCPconnection.

Fortheabovementionedsignalingadaptationstoworkassolidlyastheirexamples(Q.921andQ.704),SCTPhasbeenusedinimplementationasthedatalinklayer.SCTPofferssimilarcertificationcapacitiesascanbeexpectedwhenusingatraditionalTDMconnection.TomeetthetraditionalqualityrequirementswhenusingSCTP,theretransmissionparametersofSCTPmustbeadjustedsothatthecriteriawillbemetalsowhenusingtheIP-net.WhenreadjustingSCTPretransmissionparametersyouneedtotakeintoaccountthemethodofimplementationoftheIP-net(eitherLANorWAN)aswellasthequalityofserviceitprovides.Themostcrucialcriteriaoftheseisthetransittimedelay.

TheClientpeerestablishesanassociation.ThesystemsupportstwodestinationIPaddresses;primarydestinationIPaddressandsecondarydestinationIPaddress.DuringtheassociationestablishingphasetheClientnormallysendsanSCTPinitializemessagetotheprimarydestinationIPaddress.IftheprimarydestinationIPaddressdoesnotrespond,theClienttriestoestablishanassociationtothesecondarydestinationIPaddress.Whenthenetworkfailureintheprimarynetworkisover,thesystemchangestheconfigurationsothatsignalingtrafficisrunningovertheprimarynetworkandthesecondarynetworkisrunninginbackupmode.


SignalingtransportoverIP(M3UA)

Issue:04C DN0628311 7

1.1.1 SCTP multi-homingIntheIPterminology,ahostiscalledmulti-homedifitcanbeaddressedbymultipleIPaddresses.TomakefulluseoftheSCTPmulti-homing,thehostalsoneedstosupportmultiplenetworkinterfaces,eachofwhichhastobeconfiguredtoworkinadifferentsub-network.TheSCTPmulti-homingisusedonlyforrecoveringfromnetworkfailures.Itisnotused,forexample,forloadbalancing.TheSCTPimplementationsupportstwopathsforeachassociation.Normallydataissentviatheprimarypath.Ifanetworkfailureoccursintheprimarynetwork,SCTPresendsunacknowledgeddataviathesecondarypathautomatically.Theapplicationcannotseewhichpathisusedandsendingofdataisalsonotaffectedintheapplicationlevel.Inthiscase,theSCTPstacktakescareofallthedetails.

TheSCTPassociationworksnormallysothatdataisrunningviatheprimarypathandSCTPheartbeatisrunningviathesecondarypath.Ifsomethingunexpectedhappensintheprimarypath,theSCTPusuallyhasanalternativepathavailable.TheSCTPmonitorsaconditionofthesecondarypathallthetimebyusingaheartbeatmessage.

TheprocessoftheSCTPretransmissionisshowninFigure1:SCTPretransmission,whichisachievedwiththefollowingparameters:

Retransmissiontime-out,RTO.min300ms RTO.max500ms Path.max.retrans2 Assoc.max.retrans4

ForinstructionsonconfiguringtheSCTPparametersandthedescirptionsontheretransmissiontimer,seeModifyingSCTPassociationlevelparameters.

Figure 1 SCTPretransmission

EndPoint A EndPointB

PrimaryPath

SecondaryPath300ms

300msPrimaryPath

SecondaryPath500ms

500ms

PrimarypathUnavailable

Abort

Inthisprocess,theSCTPendpointAsendsdatafirstviatheprimarypathandstartstheretransmissiontimeroftheprimarypath.IfitdoesnotreceivetheSACKmessagefromtheotherendbeforetheretransmissiontimerexpires,itresendsthedataviathesecondarypathandstartstheretransmissiontimerofthesecondarypath.Ifthetransmissioninthesecondarypathisalsounacknowledged,theendpointAstartsthesecondroundofdataresendingviaprimarypathandsecondarypathwiththerecalculatedretransmissiontimers.Ifthetransmissionsinboththeprimarypathandsecondarypatharestillunacknowledged,theendpointAdropsthedataandclosestheSCTPassociationbysendinganABORTmessagetotheotherend.

SignalingtransportoverIP(M3UA) ConfiguringSS7SignalingTransportoverIPforIPA-RNC

8 DN0628311 Issue:04C

TherearetwotypesofSCTPmulti-homing.

Figure 2 Symmetricnetworklayout

HOST A HOST B

ThefirsttypeissymmetricSCTPmulti-homingwherebothpeershavetwoormoreexternalEthernetinterfacesavailableandconnectionismadebetweenthem.EachsignalingunitcontainstwoEthernetInterfacesinthenetworkelement.SCTPcanusebothinterfacesinsuchawaythatoneisworkingasaprimaryandtheotheroneasasecondarypath.SCTPensuresthatnomessagescangetlostincaseofpathfailure.EachEthernetportshouldbelongtoadifferentsubnetworkofthesignalingunit,otherwisemulti-homedconnectionsdonotworkasexpected.

Figure 3 Asymmetricnetworklayout

HOST A HOST B

Thesecondtypeisasymmetricmulti-homingwhereaconfigurationalsohastwoseparatepathsbutHostAhasonlyoneEthernetportinuse.IftheonlyEthernetportofHostAorthegatewayrouterwhereitisconnectedfails,thenmulti-homingdoesnothelp.IfHostAisassignedtoasecondnetwork,thentheresiliencyofthenetworkcanbeimproved.ThisadditionaladdressofHostAshouldbetakenintoaccountinthenetworkconfigurationoftheroutersaswell.Asaresultofthismodification,incaseofanykindofnetworkfailure,multi-hominghelpstoavoidassociationloss.

1.1.2 SCTP streamSCTPprovidesmultiplestreamfunctionwithinanSCTPassociation.SCTPusesstreamingformessageordering.Eachindependentlyorderedmessagesequenceiscalledastream.Streamisunidirectional,whichmeansthatthenumberofoutboundstreamsandthenumberofinboundstreamscanbedifferent.Thenumberofdatastreamscanvaryfromonetothousands.Themainpurposeofthestreamistoavoidsocalledheadoflineblockingsituation,especiallywhenonlyoneSCTPassociationisinusebetweennetworkelements.Alternatively,thiscanbeavoidedbyusingmultipleassociations.TheusednumberofoutboundstreamsdependsonSCTPapplicationsbecauseanapplicationshouldtageachofitsoutboundmessageswithastream



Issue:04C DN0628311 9

identifier.Outboundstreamnumber0mightbeusedforaspecialpurpose.Forexample,M3UAuseradaptationrequiresthatonlyamanagementmessageisallowedtouseastream0andthereforethefirstdatastreamis1.

InM3UAimplementationitispossibletousemultiplestreamsfordatamessages.Managementmessagesarealwayssenttostream0.Itispossibletoconfigurewithanassociationsetparameterwhetherthedatastreamis0or1.Itisrecommendedtousemultipledatastreams;inthatcasethefirstdatastreamisalways1.Numberofstreamsforeachassociationis16intheM3UA,exceptwhentheremoteendsupportsfewerstreamsthanlocalendwantstouse.Inthatcasethesystemisusingalowernumberofstreamsautomatically.

1.2 Association setInadistributedarchitectureseveralcomputerunitscandothesamekindoftasks,sothatsystemresourcescanbeusedmoreefficiently.M3UAhasbeenplannedtoworkinsuchasystem.

SCTPassociationisapoint-to-pointconnectionbetweentwoendpoints(seeFigure4:ExampleofanIPtypeSS7signalinglink).Inoursystem,anIPendpointisasignalingunit.Anetworkelementmaycontaintensofsignalingunits.Ifmoresignalingcapacityisneededbetweentwonetworkelements,signalingcapacitycanbeincreasedbyaddingmoreSCTPassociationstotheassociationset.Inthiscase,itisassumedthateachSCTPassociationiscreatedtoadifferentsignalingunit.Byusingmultiplesignalingunitsinoneassociationset(oneassociationpersignalingunit),yousharetheloadamongmorethanonecomputerunitandatthesametimemakethesignalingconnectionredundant.Onesignalingunitcanbeconnectedtomultipleassociationsetsifthenetworkelementalsoneedstocommunicatewithotherpeers.

Figure 4 ExampleofanIPtypeSS7signalinglinkMGW(server)

RNC(client)

ICSU0

DN0641567

ICSU1

ICSU2

ICSU3

IP network

Associationset/SS7signaling

link

ISU0

ISU1

ISU2

ISU3

Association

Additionally,whenthereisamultipleassociationsetbetweentwonetworkelements,itisrecommendedthatthesignalingunitisonlyconnectedtooneassociationset.Forexample,ifsupportofmultipleSS7networksisrequiredinthenetworkplanning,thenmorethanoneassociationsetbetweentwonetworkelementsmustbecreated.Insome


10 DN0628311 Issue:04C

casesitmightbenecessarytocreatemultipleassociations,whichareconnectedtothesamesignalingunitintheassociationset.Thisisnotrecommendedbutitispossibleifthenetworkcannotbeplannedinanyotherway.

OntheM3UA,eachIPsignalinglinkisassociatedwithanassociationsetconsistingofupto32SCTPassociations.However,fororderedmessages,forwhichtheSLSisusedforloadsharing,trafficissharedtoamaximumof16firstactivatedSCTPassociations.Upto32activeassociationscanbeusedforacasewhereunorderedmessagesareused.UnorderedmessagemodeispossibleonlywithaninterfacewhereSCCPprotocolclass0hasbeenused.Thestateofasignalinglinkfollowsthestateoftheassociationset;whenatleastoneSCTPassociationisactiveinsidetheassociationset,thesignalinglinkisactive.

Figure 5 Associationset

Signalingrouteset

Signalinglink

Signalinglinkset

Association

Association

Association

Associationset

TheloadsharingmethodoftheM3UAdependsonsignalingtraffic.Ifsignalingtrafficrequiresanordereddelivery,theSLSvalueisusedforloadsharing.ThismeansthatallsignalingmessageswiththesameSLSaredeliveredviathesameassociationinsidetheassociationset.Incaseofanassociationfailure,itisnecessarytoupdatetheroutingtableoftheassociationset.Whentheassociationfailureisover,thecontentoftheassociationsetroutingtablehastobeexactlythesameasitwasbeforethefailure.

t AssociationsetisaNSNspecificconceptthatisrelatedtothedistributedarchitecture.TheassociationsetconceptisonlyusedinM3UAconnections.

Eachassociationinsideanassociationsetcanbeinthefollowingstates:

DOWN-BY-USER ThisistheinitialstateofanassociationjustaftercreationwiththeOYAcommand.Itcanalsorefertoa'deactivatedbytheuser'stateafterthelatestsystemrestart.Thedeactivation/activationisdonewiththeOYScommand.



Issue:04C DN0628311 11

SCTP-DOWN Thisisthestateofanassociationafterthesystemrestart.MTPmanagementhasnotyetactivatedtheM3UAlinkthatcorrespondstotheassociation,andtheM3UAlinkmaybeinUA-ADstate(activationdenied).

UP-PROCEEDING ThisstatemeansthatthenegotiationoftheSCTPassociationisongoing.TheremaybesomeproblemintheIPconnectionsothattheSCTPassociationdoesnotactivate.ChecktheIPconnectionwithpingcommandQRX.

ASP-DOWN ThisstatemeansthattheassociationisupattheSCTPlevelbutdownattheM3UAlevel,thatis,ASPmanagementmessageexchangeisongoing.ASPUP(attheserver)orASPUPACK(attheclient)hasnotbeenreceivedyet,andtheM3UAlinkisnotactive.

ASP-INACTIVE ThisstatemeansthattheassociationisupattheSCTPlevelbutinactiveattheM3UAlevel,thatis,ASPmanagementmessageexchangeisongoing.ASPAC(attheserver)orASPACACK(attheclient)hasnotbeenreceivedyet,andtheM3UAlinkisnotactive.

ASP-ACTIVE ThisstatemeansthattheassociationisupatboththeSCTPandtheM3UAlevel.TheM3UAlinkisactive.

1.3 SGP - ASP communicationsignalingGatewayprocessisasignalingagentthatsendsandreceivestelecomsignalingtrafficattheedgeofIPnetwork.SignalingGatewayisasignalingconverterwhereTDMorATMbasedsignalingconnectionisterminated.

Applicationserverisavirtualdatabaseorcallcontrolelement,whichcanserveaspecificroutingkey.Asmentionedearlier,DPCisusedasaroutingkeyatthesolution.AccordingtoRFC2719,FrameworkArchitectureforsignalingtransport,SGP-ASPcommunicationisbasedonIPnetworkastransportationmedium.ASP-SGPconceptisdescribedinFigure6:AnexampleofSGP-ASPcommunication.


12 DN0628311 Issue:04C

Figure 6 AnexampleofSGP-ASPcommunication

MTP2 SCTP

MTP1 IPv4/IPv6

MTP3 M3UA

CAP/MAP/...

TCAP BSSAP

BICC/ISUP SCCP

M3UA

SCTP

IPv4/IPv6

CAP/MAP/...

TCAP BSSAP

BICC/ISUP SCCP

MTP3

MTP2

MTP1

SG

SEP/STP ASP

Figure6:AnexampleofSGP-ASPcommunicationdescribestheASP-SGPconnectionincaseofM3UA.

1.4 IPSP-IPSP communicationIncaseofIPSP-IPSPcommunication,theservicesofaSignalingGatewaynodearenotneeded,sincebothpeersexistintheIPdomain.AgroupofIPSPsformanApplicationserveratbothendsofthesignalingconnection.ThemessageexchangeinanIPSP-IPSPconnectionissingle-endedbydefault,whereonlyoneendpointsendsASPmanagementmessages.Theotherpossibilityisthedual-endedmode,wherebothendpointssendASPmanagementmessages.

Figure 7 AnexampleofabasicIPSP-IPSPconfigurationwithapointtopointconnectioninsidetheIPnetwork

Applications

AdaptationLayers

SCTP

IP

Applications

AdaptationLayers

SCTP

IP

IPSP-IPSP



Issue:04C DN0628311 13

1.5 Signaling over IP statisticsInthesignalingunitlevel,theSIGTRANtrafficcanbemonitoredfromtheSCTPstackcounters.TheSCTPstatisticscountersofferanoverallnumberofSCTPtrafficinthesignalingunit.ThesecounterscontaintrafficfromallSCTPuseradaptations,andthereforearenotsousefulifoneisinterestedonlyinthetrafficofaspecificSCTPuseradaptation.TheSCTPstatisticscounterscanbeexaminedusingQRS.

M3UAAssociationSetMeasurement(295H/661)canbeusedtomonitorM3UAtraffic.ItgivesinformationontrafficthroughputandqualityofM3UAconnections.ThemeasurementmeasuresM3UAtrafficfromM3UAlayerandSCTPlayer.

M3UAlayercountersshowthepayloadofSCTPconnection.FromthecountersoftheSCTPlayer,youcanretracethetrafficoftheSCTPlayerusedbyM3UAassociation.TheSCTPlayercountersgiveyoumoreaccurateinformationontherealloadrequiredforsendingM3UAtrafficthroughSCTPbyincludingthenumberofretransmittedSCTPpacketsandSCTPheader.

Unavailabilitycounterscanbeusedformonitoring,forexampleiftheassociationisinASP-INACTIVEstate.

ThemeasurementisconfiguredbyusingcommonstatisticsinterfaceT2MMLcommandgroupcommands.

Thefollowingcountersaresupported:

M3UA association set counters:DurationofM3UAassociationsethasbeenunavailable

NumberoftimesM3UAassociationsethasbeenunavailable

M3UA association counters:DurationofM3UAassociationhasbeenunavailable

NumberoftimesM3UAassociationhasbeenunavailable

NumberofreceivedpacketsonM3UAassociation

NumberofsentpacketsonM3UAassociation

NumberofoctetsreceivedonM3UAassociation

NumberofoctetssentonM3UAassociation

SCTP counters used by M3UA:NumberofSCTPpacketsreceived

NumberofSCTPpacketssent

NumberofSCTPoctetsreceived

NumberofSCTPoctetssent

NumberofretransmittedSCTPpackets

NumberofduplicatedTSNreceived


14 DN0628311 Issue:04C

IftheM3UA-specificstatisticsarenotavailable,theM3UAtrafficcanbemonitoredbyusingtheMTP3levelmatrixmeasurements.TheMTP3matrixmeasurementisbasedonusinganOPC,DPC,andSImatrix.Thematrixdefinesaconnectionwhosetrafficwillbemeasured.Thismeasurementshowsanamountofspecificsignalingtrafficbetweentwosignalingpoints.ServiceIndicator(SI)definesconcernedsignalingtrafficandOPCandDPCparametersshowwhichonesofthesignalingpointsbelongtoameasurement.TheMTP3matrixmeasurementcanbeconfiguredbyusingOIMMLcommandgroupcommands.



Issue:04C DN0628311 15

2 Use of M3UA stackThissectiondescribestheuseoftheM3UAstack.

2.1 SGP-ASP communicationThesignalinggatewayprocess-applicationserverprocess(SGP-ASP)communicationisneededwhencommunicatingbetweentheMTP-3peersinSS7andIPdomains.Toenablethecommunication,aseamlessinterworkingfunctionisneededintheSGattheM3UAlayerfortheMTP3-UserpeersintheSS7andIPdomains.IntheSGP-ASPcommunicationtherelatedconceptsareAS,ASP,SG,andSGP.

Figure 8 AnexampleofSGP-ASPcommunication

SG

AS

SGP

SGP

ASP

ASP

ASP

AgroupofASPsconnectedtoasignalinggatewayprocess(SGP)andservingaspecificroutingkeyiscalledanapplicationserver(AS).WhentheSGProutesthemessage,itselectsanASbycomparingtheinformationinthemessagewithaprovisionedRoutingKey(DPC+NI).AfterthatanactiveASPinsidethatASisselected.Thewaytheselectionisdonedependsonthetraffichandlingmodeused.Whenthetraffichandlingmodeisload-share,anactiveASPisselectedfromthelistofactiveASPs:ifthetraffichandlingmodeisover-ride,thereisonlyoneactiveASPonthelistatthetime.

EachASPinsideanAScanbeconnectedtoseveralSGPs.AgroupofSGPsformanSG.WhenroutingthemessageatASP,theSGisfirstselectedbasedoninformationinthemessage,forexample,DPC+NA,andanSGPisselectedinsidethatSG.TheSGPsinsideanSGallhavethesameavailabilityviewoftheSS7network.

EachASPcanbelongtomorethanoneAS,eachASservingitsownroutingkey.WhentheASP(inthiscase)wantstoindicatetoanSGPthatitisactiveforhandlingspecificroutingkeytraffic,itneedstousetheroutingcontextvaluetoindicatetotheSGPwhichroutingkeytraffictheASPwantsactivelyhandle.Therearetwopossibilitiestodetermine

UseofM3UAstack ConfiguringSS7SignalingTransportoverIPforIPA-RNC

16 DN0628311 Issue:04C

routingcontextvalue:eitherstaticconfiguredordynamicroutingkeyregistration.Dynamicroutingkeyregistrationprocedureisusedbydefault.Usingroutingkeyregistrationisnotmandatediftheotherpeerdoesnotsupportthisoptionalfeature.

IncommunicationbetweenNSNnetworkelements,theASandSGconceptsaremappedtonetworkelements,forexample,AS=MSS,SG=MGW.Furthermore,thesignalingunitsinthosenetworkelementsaremappedtoASPsinsidetheMSSandSGPsinsidetheMGW.

WhenasignalingmessagearrivestothesignalinggatewayfromanSS7link,theM3UAroutingfunctionfirstdeterminestheassociationsetbasedoncomparingtheinformationinthemessagewithaprovisionedRoutingKey(DPC+NI).Insidetheassociationsetanassociationisselected,basedontheSLSvalue,andthesignalingmessageisforwardedtothesignalingunitwheretheassociationexists.WithIETFconcepts,intheNSNroutingfunctiontheSGP(thesignalingunit)andtheASP(association)fromthatSGPareselectedatoncebasedontheroutingkey,thatis,DPC+NIandtheSLSvalue.WhenthereisaNSNnetworkelementatthepeer,itisrecommendedthatthereisonlyoneassociationinonesignalingunitinsideoneassociationset.SeealsoAssociationset.

InastrictIETFsense,theASconceptappliesineachSGPseparately.Theassociationsetconcept,however,isvalidforthewholenetworkelementcollectingallASPsconnectedtoeachSGP(signalingunit).

IntheNSNimplementation,eachassociationcancarryonlythesignalingtrafficrelatedtooneroutingkey.Thatiswhyitisnotnecessarytoconfigurearoutingcontext.Thestaticconfigurationoftheroutingcontextisnecessaryanditmightbeneededinsomecompatibilitycases.

However,iftheregistrationparameterisusedinsidetheassociationset,theroutingcontextgetsitsvalueduringroutingkeyregistration.ThatvalueissavedtoaworkfileforpossiblefurtheruseinASPTMmessages.

2.1.1 Example of M3UA usageSignalingmessagesfromthePSTNareaddressedtotheservernetworkelement.Asignalingroutegoesviathesignalinggateway,whereaprotocolchangefromSS7toSIGTRANisdone.SignalingmessagesfromtheserveraredestinedtotheSCCPinthePSTNnetworkelement.Asignalingroutegoesviathesignalinggateway,whereaprotocolchangefromSIGTRANtoSS7isdone.TheremaybeSTPpointsintheSS7pathbetweentheSGandthedestinationPSTNnetworkelement.


UseofM3UAstack

Issue:04C DN0628311 17

Figure 9 AnexampleofaSignalingGatewaybetweentwonetworkelementsindifferentprotocols

PSTN Signalinggateway Server

MAP MAP

MTP

SCCP

TC

MTP

M3UA

SCTP

IP

M3UA

SCTP

IP

TC

SCCP

WhentheSG-ASPcommunicationisused,signalingmessagesfromthePSTNaredestinedtotheserverwithSPCaddressing.Asignalingroutegoesviathesignalinggateway,wheretheprotocolchangesfromSS7toSIGTRAN.Thisissimilartothepreviousexample,wherethemessagedoesnotgototheSCCPlevelinthesignalinggateway.

SignalingmessagesfromtheserveraredestinedtothesignalinggatewaywithSPCaddressing.Asignalingroutegoesviathesignalinggateway,wheretheprotocolchangesfromSIGTRANtoSS7.Thisissimilartothepreviousexample,wherethemessagedoesnotgototheSCCPlevelinthesignalinggateway.

2.2 IPSP-IPSP communicationTheIPSP-IPSP(IPserverprocess)communicationandtheASP-SGPcommunicationarenotdifferentexceptforthefactthatthesignalinggatewayfunctionalityisnotneededateitherendpoint.Theconfiguration,association,andtheIPSPactivationarethesame.TheIPSP-IPSPhastwokindsoffunctionalmodes.IfthedualendedmodeoftheIPSP-IPSPconfigurationisused,the'ASPMESSAGESINIPSP'andthe'ASPMESSAGES'parametersshouldhavethevalue'Y'atbothendpointsofthesignalinglink.Insingleendedmode,onlythe'ASPMESSAGES'parametershouldhavethevalue'Y'atbothendpoints.Ifbothparametershavethevalue'N',theapplicationsserverprocessstatemaintenancemessages(ASPSM)andapplicationserverprocesstrafficmaintenancemessages(ASPTM)arenotexchangedatall.

TheIPSP-IPSPconnectioncanbeusedpoint-to-pointbetweentheM3UAusers.Forexample,whentheSignalingGatewayisabletodotheGTtranslationorwhenthereisanSCCPrelayintheIPnetwork,thefollowingconnectionisIPSP-IPSP.


18 DN0628311 Issue:04C

2.2.1 Use of IPSP-IPSP example at the M3UAFigure 10 AnexampleofcombinedSignalingGatewayandIPSP-IPSP

PSTN Signalinggateway Server

MAP MAP

MTP

SCCP

TC

MTP

M3UA

SCTP

IP

SCCP

IPSP-IPSPorSGP-ASP

M3UA

SCTP

IP

TC

SCCP

InFigure10:AnexampleofcombinedSignalingGatewayandIPSP-IPSP,boththeIPSP-IPSPandtheSGP-ASPcommunicationispossible.

WhentheIPSP-IPSPcommunicationisused,signalingmessagesfromthepublicswitchedtelephonenetwork(PSTN)aredestinedtothesignalinggatewaywithGTaddressing.TheGTTinthesignalingconnectioncontrolpart(SCCP)ofthesignalinggatewaygivesasaresulttheSCCPpeerlocatedintheIPnetwork.Thesignalingmessagesfromtheserveraredestinedtothesignalinggatewaywithglobaltitle(GT)addressing.Theglobaltitletranslation(GTT)intheSCCPofthesignalinggatewaygivesasaresulttheSCCPpeerlocatedintheSS7network.Inthiscase,theconnectionbetweenthesignalinggatewayandtheserverisanIPSP-IPSPconnection.

2.3 Routing key and routing contextThedistributionoftheSS7messagesbetweentheSGPandtheApplicationServersisdeterminedbytheroutingkeysandtheirassociatedroutingcontexts.

Routingkeyisapartofthemessageheader.TheInternetEngineeringTaskForce(IETF)standardforM3UAdeterminesagroupofSS7parametersthatcanbeusedasanidentifierforanAS.TheseparameterscanbeDPC(DestinationPointCode),NA(NetworkAppearance),SI(ServiceIndicator),OPClist(OriginatingPointCode),orcertainvaluedomainsofthenumberspaceofCIC(CircuitIdentificationCode).TheparameterDPCisobligatorybecauseitistheSPCaddressusedbytheAS.EitheroneorseveraloftheseparametersasanidentifierforanAScanbeusedasaroutingkey.


UseofM3UAstack

Issue:04C DN0628311 19

TheDPCandnetworkappearancetogetherformtheonlyroutingkeythatissupported.Botharealsomandatoryparametersintheroutingkey.Thenetworkappearancemapstoanetworkindicator.Thenetworkappearanceparameterisincludedintheassociationsetparameters.Theotherparameters:SI,SSN,orCICarenotincludedintheroutingkeybecauseitisexpectedthatthenetworkelementoperatingasanAScanhandlethemessagedistributingfunctionitself.ThisespeciallyappliestotheSGPwhenthepeerisaNSNnetworkelement.

Routingcontextisavaluethatuniquelyidentifiesaroutingkey.Theroutingcontextparameterisa4-bytevalue(integer)whichisassociatedtothatroutingkeyina1-to-1relationship.Therefore,theroutingcontextcanbeviewedasanindexintoasendingnode'sMessageDistributionTable,containingtheroutingkeyentries.AnapplicationserverprocessmaybeconfiguredtoprocesssignalingtrafficrelatedtomorethanoneApplicationServer,overasingleSCTPAssociation.InASPActiveandASPInactivemanagementmessages,thesignalingtraffictobestartedorstoppedisselectedbytheroutingcontextparameter.AtanASP,theroutingcontextparameteruniquelyidentifiestherangeofsignalingtrafficassociatedwitheachApplicationServerthattheASPisconfiguredtoreceive.

Youcanconfigureroutingcontextvalueseitherbyusingaconfigurationmanagementinterface,orbyusingspecificproceduresofroutingkeymanagement.Incaseofstaticconfiguration,youcanconfigurethevalueoftheroutingcontextmanually.DynamicRoutingKeyregistrationisusedbydefault,butifyouwanttohaveastaticconfigurationforsomereason(forexample,insurecompatibilitywithothervendors'products),refertoOY - SCTP Configuration HandlingMMLcommandmanual.

2.4 Signaling Point Management ClusterSignalingPointManagementCluster(SPMC)isanexampleofaconfigurationwheretwonetworkelementsshareaSignalingPointCode(SPC).TheSPMCisanentitywhichconsistsoftheSGandApplicationNode,butisvisibletoothernetworkelementsonlywithonesignalingpointidentity,thatoftheApplicationNode.MTPlevel2connectionsandotherMTPfunctionalitiesofanSPMCareintheSignalingGateway,whiletheUserPartfunctionalityoftheclusterisintheApplicationNode.WhentheMTPoftheSignalingGatewayreceivesaUserPartmessagedestinedtothemanagementcluster,itforwardsthemessagetotheApplicationNode.

AsignalingpointmanagementclusterisapplicablewhenasignalingpointbecomesanApplicationNodeasitisconnectedtoaSignalingGateway,andthereforestrippedofitsMTPlevel2connectionstoothernetworkelements.Thenothernetworkelementsneednoconfigurationchanges,astheyseenothingfromthemanagementcluster,butthesameoldsignalingpointcode.

AsignalingpointmanagementclustermayalsobeneededwiththeMSSSysteminIUorAinterface,becausesomeradionetworkcontrollerimplementationsonlysupportassociatedsignalingmode.However,itisnotmandatorytousethemanagementclusterwhenmigratingintoMSSSystemarchitecture.NSNrecommendsthatwiththeMSSSystem,thequasi-associatedsignalingmodeisused,thatis,MGWisusedasanSTP,whichmakesitpossibletodesignaasignalingnetworkwithmoreredundancy.


20 DN0628311 Issue:04C

Figure 11 AnexampleofSignalingPointManagementCluster

TMSC

DPC=123,NI=8

TDM SG ASPM3UA

WhentherearetwoMGWintheSPMC,thetwoMGWsprotecteachotherandtheSS7signalingisredundanteitherby

quasi-associatedsignaling,havingbothMGWsasSignalingTransferPoints(STP)fortheMSCServer,or

associatedsignaling,havingSignalingPointManagementCluster(SPMC)overoneMSCServerandtwoMGWs.

TheSPMCenablestheinterworkinginamultivendorenvironmentwhentheotherend(forexample,aBSC)doesnotsupportquasi-associatedsignaling.TheMSSSystemisseenasonepointcodewhichdoesnotsetrequirementsforothernetworks(PLMNorPSTN).

TheSPMCisapplicabletosignalingapplicationsthatarenotterminatedintheMGW,suchasISUP,BSSAP,andRANAP.ThesignalingtrafficthatisterminatedintheMGW,suchasAccessLinkControlApplicationProtocol(ALCAP)orsignalingnetworkmanagementmessages(SNM),needsspecialconsiderationasthepeernetworkelementsconnectedtotheprotectedMGWpairmaysendsignalingtrafficrandomlytoeitheroneoftheMGWs.MGWsupportstheforwardingofthesignalingnetworkmanagementmessagesoftheMTPsignalinglinkincasetheyarereceivedbyanMGWthatdoesnotmanagetherelatedsignalingobjects.Adedicatedsignalingpointcode,thatis,asignalinglinksetfortheALCAP,independentofRANAP,isneededtoterminateALCAPintheMGW.

IncaseasignalinglinkbetweentheMSSandtheMGWislost,thestateofthesignalinglinksbetweentheMGWandthePSTN/PLMN/BSC/RNCis'outofservice',butthesignalinglinksviatheotherMGWareavailable.IncasesignalinglinksbetweentheMGWandthePSTN/PLMN/BSC/RNCarelost,thestateofthesignalinglinkbetweentheMSCServerandtheMGWis'outofservice',butthesignalinglinkviatheotherMGWisavailable.

AclusterformedbytwoMGWsandoneMSCServerisconfiguredsimilarlytoaclusterdefinedintheearlierreleasesbut,inadditiontothat,thereisasignalinglink(forexample,SIGTRAN)betweenthetwoMGWs.ThepurposeofthatadditionalsignalinglinkistoenabletheMTP3signalingmanagementfunctions(signalingtraffic,linkandroutemanagement)inaclusterwhichcontainstwoMGWs.Theconnectedpointsofinitiation(POI),thatis,BSC,RNC,orPSTN/PLMN,considertheclusterasonesignaling


UseofM3UAstack

Issue:04C DN0628311 21

entityandtheSNMstheysendcanbereceivedbyeitheroneoftheMGWs.ThatiswhytheMGWsmayneedtoforwardsomeSNMstotheotherMGWwhichhasthesignalinglinksconcerned.

2.5 Message structure of M3UAThebasicoverheadonSIGTRANcontainsthefollowingmessageheaders:IP,SCTP,andM3UA.

ThesizeoftheIPheaderdependsonwhatversionoftheIPstackisused,IPv4orIPv6.ThelengthoftheIPv4headercanvarybetween20and60bytes.20bytesisthelengthofthebasicIPaddressinIPv4.Theremaining40bytesisthelengthoftheoptionfield.OptionsarenotcommonlyusedontheIPv4.ThelengthoftheIPv6headeris40bytes+optionsfields.UsuallysomeoptionfieldsareincludedinthemessagewhenitisusingIPv6.

TheSCTPheadershouldcontainaCommonheader,aChunkdescription,andaPayloadidentifier.ThelengthoftheCommonheaderis12bytes.ThelengthoftheChunkDescriptionis4bytes.ThelengthofthePayloadidentifieris12bytes.ThetotalSCTPheadersizeis28bytes.

ThesizeoftheCommonMessageheaderoftheM3UAis8bytes.TheCommonmessageheaderexistsineveryM3UAmessage.Themainpartofthebitrateisgeneratedfromthepayloaddatamessages.Therefore,anexampledescribesonlythestructureofthepayloaddata.TheoptionalNetworkAppearanceparameterisusedinM3UA.Itssizeis8bytes.TheRoutinglabeloftheMTP3messageisencodedinseparatefields.TheOPCandDPCfieldsareboth4byteslongandtherestoftheroutinglabelparameterslikeSI,NI,MessagePriority,andSLSareencodedinonedword(4bytes).ThetotallengthoftheM3UAmessageheaderis24bytesinthePayloadDatamessage.


22 DN0628311 Issue:04C

Figure 12 MessagestructureofM3UA0 31

FragmentOffset

TotallengthTypeofserviceHeaderlength

Identification

Timetolive Protocol Checksum

Flags

Ver.

SourceIP address

DestinationIP address

Options (variable length,usually this fieldis notused)

Source PortNumber DestinationPortNumber

Verification Tag

Checksum

Chunk Type ChunkFlags ChunkLength

TSN

StreamIdentifier StreamSequence Number

Payload Protocol Identifier

LengthTag=210

SI NI MP SLS

protocol dataoftheM3UA users (VariableLength)

Messagelength

OriginatingPointCode

DestinationPointCode

Version Reserved MessageClass Message Type


UseofM3UAstack

Issue:04C DN0628311 23

3 Basic structures of SS7 signaling over IPnetworkWhenIPtransportisusedinthesignalingnetwork,thesignaling end point(SEP)networkelementisusuallyintheIPnetwork.TheSEPnetworkelementcanbeanynetworkelementwheresignalingistransportedviatheIPnetwork(suchasRNCorMSCServer).

Figure 13 BasicexampleofanetworkthatusesIP

RNC

SG

SG

MSSIP

InFigure13:BasicexampleofanetworkthatusesIP,therearetwoSignalingGateways(SGs).Ifoneofthemisunavailable,theotheronecanbeusedasabackup.

WhenanIPconnectionoverATMisused,thesignalingunitmusthaveapointtopointIPoverATMconnectionwiththenetworkelementwhichitisconnectedto.

Figure 14 ExampleofpointtopointIPconnection

IPSP IP IPSP

IPSP IPServerPoint

WhenanIPconnectionoverEthernetisused,thenetworkelementmusthaveanIPnetworkinterfaceunitwithEthernetports.TheIPnetworkinterfaceunitisusedasanIPgateway.Insidethenetworkelement,internalIPoverATMconnectionisused.

IntheIPnetwork,M3UAsignalingisimplementedaspoint-to-pointsignaling.TheM3UAspecificationdoesnotdescribetheM3UAlevelSTPfunctionality;however,theSTPfunctionalityisimplementedintheDX200andIPA2800-basednetworkelementsaccordingtotheITU-T Q704 recommendations.

BasicstructuresofSS7signalingoverIPnetwork ConfiguringSS7SignalingTransportoverIPforIPA-RNC

24 DN0628311 Issue:04C

SS7messageroutingcanalsobebasedonanSCCPGT(GlobalTitle)address.IftheGTisusedforrouting,therecanalsobeanSCCP-levelSTPinsidetheIPnetwork.TheSGroutesmessagestotheSTPpoint,whichisanASfromtheSG'spointofview.Inthatnode,theSCCPfindsoutthenextsignalingpointwherethemessagehastobesent.ThemessageisthenpassedontothenextsignalingpointthroughIPSP-IPSPtypeM3UAconnection.


BasicstructuresofSS7signalingoverIPnetwork

Issue:04C DN0628311 25

4 Planning site configuration for signalingThissectiondescribeshowtoplanthesiteconfigurationforsignalingwithIPsolutions:IPoverATM(IPoA)andIPoverEthernet(IPoE).TheIPoAinterfacesareconfiguredforNPS1unitsandtheIPoEinterfacesforNPGE(P)units.

WerecommendthatthesameDiffServisusedforallSCTPassociationsintheassociationsetintheM3UA.ThesettingsoftheDiffServcodeusedforM3UAsignalingarecommontoallthoseapplicationswhosetrafficgoesviathesameSCTPassociation.

Themaximumdelaythatisallowedbetweenthenetworkelementsisnotspecified.SeeQ706ITU-Trecommendationforreference.AnapplicationoftheM3UAsetsreallimits.TheM3UAdoesnotcontainforexamplesignalinglinkswitchoverwithinasignalinglinkset,andthereforeitcannotachievethesameservicelevelasMTP3inmessagetransport.PacketlossmayhappenintheM3UAasonMTPlevel3.

InIPoEcases,theLANinfrastructure,suchasthepoint-to-pointcapacityoftheLAN,shouldbeknownwhenplanningthesiteconfiguration.ModifiableSCTPparametersarenecessaryfortheassociationstofunctionaccordingtotheQ706ITU-Trecommendation.

YoucanplantheredundancyeitherbyusingSCTPmulti-homingorbyusing2NredundantNPGEPunits.Redundancyofassociationscanbehandledonseverallevels:

onthenetworkelementlevel:IfsignalingunitsareconfiguredwithlogicalIPaddresses(whichishighlyrecommended),itispossibletodoasignalingunitswitchoverproceduresothatthecurrentM3UAconfigurationisrecovered.

ontheunitlevel.

Before you startIfIPoAsolutionisused,configureATMresourcesforit.SeeCreating ATM resources inRNC.

g InadditiontotheMMLbasedconfigurationtheIPoAinterfacecanbeconfiguredviatheIPplaninterfacefromtheNetAct.TheIPplansupportcoversthebasicsupportfortheMMLcommandsQMF,QRNandQKCanddoesnotcontaintheOSPFconfiguration.Forfurtherdetails,refertodocumentWCDMA RAN Mass Operations.

Takethefollowingpointsintoconsiderationwhenplanningsiteconfigurationforsignaling:

1. UselogicalIPaddresses.ThisenablesmakingaunitswitchoversothatIPaddressesremainthesame.

2. UselogicalstaticIProutes.ThishelpstomakeastaticIProuteconfigurationandensurethataftertheunitswitchover,signalingconnectionworksasbeforetheunitswitchover.

g SCTPmulti-homingconfigurationisrequiredtoconfiguretwoIPsub-networkstoeachsignalingunit.Forthisreason,thenumberofIProutesincreasesrapidlyineachpeer.GoodIPaddressingandgoodIPnetworkdesignarekeyissuestoavoidsuchasituation.

3. Usemulti-homedconnectionsforsignalingoverIP,ifpossible.

Planningsiteconfigurationforsignaling ConfiguringSS7SignalingTransportoverIPforIPA-RNC

26 DN0628311 Issue:04C

Inthiscase,IFGE0andIFGE1(forIPoE)orAA0andAA1(forIPoA)shouldbelongtodifferentsub-networks.Thiskindofconfigurationensuresthattheprimarypathisseparatedfromthesecondarypath.

4. Point-to-pointmessagetravellingtimeshouldbeexplored.Ifthefailuredetectiontimehasbeenplanned,itisimportanttoreduceittothesamelevelasthatoftheSS7networkbytuningtheSCTPparameters.

Steps for planning the site configuration for IP over ATM interfacesThisproceduredescribeshowtoconfigureIPoAinterfacesonNPS1units.

1. PlantheIPoAinterfacesforSCTPmulti-homing.AA0andAA1shouldbelongtodifferentsub-networks.SCTPmulti-homingenablesbetterredundancyandthereforeitistherecommendedredundancymodeforsignaling.WerecommendthatyouuseasymmetricconfigurationinthecaseofSCTPmulti-homing.FormoreinformationonSCTPconfigurations,seeSCTPmulti-homing.

2. TunetheSCTPparameters.BytuningtheSCTPparameters,afailuredetectiontimeofassociationcanbereducedtothesamelevelasthatoftheSS7networkrequired.FormoreinformationonSCTPparameters,seeModifyingSCTPassociationlevelparameters.

3. PlanIPaddressesmanagementandconfiguration.UselogicalIPaddresses.Forfurtherinformation,seeConfiguring IP Connections for RNC.

t Inthefollowingexample,twoIPoAinterfacesarecreatedtothesameICSU.Inthisway,SCTPmulti-homingwithtwodifferentIPnetworkscanbesupported.

Example:Creating two IP over ATM interfaces to the same ICSU

a) ConfiguretwoIPoAinterfaces(AA0andAA1)overtheVCLtpcreatedduringconfiguringATMresources.(QMF)

g Signalingunitmustbeinanactivestate(thatis,inWO-EXstate)beforeconfiguration.ZQMF:ICSU,0,L:AA0:2,20,30:1,IPOAM;ZQMF:ICSU,0,L:AA1:2,20,31:1,IPOAM;

b) AssignIPaddressestobothATMinterfacesconfiguredinthepreviousstep.(QRN)

g IPaddressesmustbeassignedfromdifferentsubnetwork.ZQRN:ICSU,0:AA0:1.2.3.4:32:1.2.3.1;ZQRN:ICSU,0:AA1:2.2.3.4:32:2.2.3.1;

c) Createstaticroutesifneeded.(QKC)

g Whenthedestinationaddress(OYA)associatedwithsignalingpointisjustthedestinationaddress(QRN)ofIPoAconnection,itisunnecessarytocreatestaticroutes.

ZQKC:ICSU,0:10.2.3.0,:1.2.3.1:LOG:;ZQKC:ICSU,0:20.2.3.0,:2.2.3.1:LOG:;


Planningsiteconfigurationforsignaling

Issue:04C DN0628311 27

Steps for planning the site configuration for IP over EthernetinterfacesThisproceduredescribeshowtoconfigureIPoEinterfacesonNPGE(P)units.Ifthesystemistobeusedforthefirsttime,createtheIPconfigurationsbeforecreatingSCTPassociations.AfteryoucreatealogicalIPaddressinasignalingunit,theunitstatusisautomaticallychangedfromSP-EXtoWO-EX.

t OneNPGEPunitpairsupports2NredundantEthernetports.TheusedEthernetportshavethesamelogicalIPaddressbutonlyoneofthemisinactivestate.ThisisdifferentfromtheSCTPmulti-homingconfiguration,wherebothEthernetportsusedhavetheirownIPaddressesfromdifferentIPsubnetworks,sothatbothEthernetinterfacesareactivesimultaneously.

TheM3UAimplementationsupportstheDSCPfeature.Theapplicationreadsaparameterfromthefile(S3BARA)thattellstheDiffServcodepointusedforsignaling,suchasRANAP,RNSAP.TheparameterisdefinedinSCTPparameterset,anditwillbecommontoallsignalingapplicationswhichareusingthesameparametersetinthenetworkelement.

1. a)PlantheredundancyusingSCTPmulti-homing.Ethernetport0andEthernetport1shouldbelongtodifferentsubnetworks.TheycanbetwodifferentEthernetportsofoneNPGE(P)unit,ortwoNPGE(P)units.TherecommendedoptionistousetwoNPGE(P)units.IfoneNPGE(P)unitisused,twointernalIPoAinterfacesareneededbetweenthesignalingunitandtheNPGE(P)unit.Otherwise,oneinternalIPoAinterfaceforeachNPGE(P)isneeded.SCTPmulti-homingenablesbetterredundancyandthereforeitistherecommendedredundancymodeforsignaling.WerecommendthatyouuseasymmetricconfigurationinthecaseofSCTPmulti-homing.FormoreinformationonSCTPconfigurations,seeSCTPmulti-homing.ORb)Plantheredundancyusing2NredundantNPGEP.2NredundantNPGEPunitsbringredundancytoallEthernettrafficandcanbeusedtogetherwithSCTPmulti-homing.However,using2NredundantNPGEPunitsismoreimportantwhenSCTPmulti-homingcannotbeused.WhenconfiguringalogicalIPaddress,twoEthernetportswiththesamenameoftheNPGEPpairgetthesamelogicalIPaddress.IftheEthernetport(forexample,IFGE0)oftheworkingunitfails,theEthernetportofthespareunitcantaketheresponsibilityforthefailedone,andtheSCTPassociationscancontinueworkingnormally.

2. TunetheSCTPparameters.BytuningtheSCTPparameters,afailuredetectiontimeofassociationcouldbereducedtothesamelevelasthatoftheSS7networkrequired.FormoreinformationonSCTPparameters,seeModifyingSCTPassociationlevelparameters

3. PlanIPaddressesmanagementandconfiguration.LogicalIPaddressesshouldbeusedifpossible.IPaddressesareneededfortheEthernetportsofNPGE(P)andfortheinternalIPoAinterfacesoftheselectedsignalingunitandtheNPGE(P).TheIPaddressfortheinternalIPoAinterfaceofNPGE(P)isusedasagatewayaddress.TheinterfacetypeoftheinternalIPoAhastobeNUMBERED.

4. CreatestaticIProutes(QKC).UselogicalIProuteconfiguration.ConfigurationsareneededbothinthesignalingunitandintheNPGE(P).


28 DN0628311 Issue:04C

5. ConfiguretheLAN.ConfigurethelowerlevelLAN.Formoreinformation,seeConfiguring IP Connections for RNC.

6. ConfigureDSCPvalueforRANAPsignalingorRNSAPsignaling.ConfiguretheIPinterfaceQoSforIuControlPlanetraffic(RANAP)orIurControlPlanetraffic(RNSAP).

Example:Configuring symmetric SCTP multi-homing

ThefollowingexampleshowshowtoconfigureICSU-0toconnecttoSGSNwithmulti-homingIPoEinterface,goingthroughNPGEP-0andNPGEP-2.

TheIPaddressesforICSU-0are10.20.1.1and10.20.2.1.TheyareusedlaterastheSCTPprimarysourceIPaddressandthesecondarysourceIPaddress.

TheIPaddressesforNPGEP-0internalIPoAis10.20.1.2and10.20.2.2forNPGEP-2.

TheIPaddressforNPGEP-0is10.20.3.1and10.20.4.1forNPGEP-2.

Thesub-netaddressesforIu-PSsignalingofSGSNare10.2.5.0/24and10.2.6.0/24.

TheIPaddressesforSGSNare10.2.5.1and10.2.6.1.

TheIPaddressesforsiteroutersare10.20.3.2and10.20.4.2.

1. EnableIPforwardinginNPGE(P),whichisusedforroutingthepackets.ZQRT:NPGEP,0:IPF=YES,;ZQRT:NPGEP,2:IPF=YES,;

2. AssignIPaddressestotheEthernetinterfaces.ZQRN:NPGEP,0:IFGE0:10.20.3.1,L:24;ZQRN:NPGEP,2:IFGE0:10.20.4.1,L:24;

3. CreatethestaticroutesfortheNPGE(P).ZQKC:NPGEP,0:10.2.5.0,24:10.20.3.2;ZQKC:NPGEP,2:10.2.6.0,24:10.20.4.2;

4. CreateinternalIPoAinterfaces.Forexample,createthefollowingtwoIPoAinterfaceswiththecommandZQMC:AA5 IFAI5 of NPGEP-0AA6 IFAI6 of NPGEP-2ZQMC:NPGEP,0,:IFAI5:ICSU,0,:AA5::;ZQMC:NPGEP,2,:IFAI6:ICSU,0,:AA6::;

5. AssignIPaddressestotheinternalIPoAinterfacesforICSUandNPGEP.ZQRN:ICSU,0:AA5,N:10.20.1.1,L::10.20.1.2:;ZQRN:ICSU,0:AA6,N:10.20.2.1,L::10.20.2.2:;ZQRN:NPGEP,0:IFAI5,N:10.20.1.2,L::10.20.1.1;ZQRN:NPGEP,2:IFAI6,N:10.20.2.2,L::10.20.2.1;

6. ConfigurestaticroutesforICSU.ZQKC:ICSU,0:10.20.3.0,24:10.20.1.2:LOG:;ZQKC:ICSU,0:10.20.4.0,24:10.20.2.2:LOG:;ZQKC:ICSU,0:10.2.5.0,24:10.20.1.2:LOG:;ZQKC:ICSU,0:10.2.6.0,24:10.20.2.2:LOG:;

7. VerifytheIPconnectivityfromICSUtoSGSN.ZQRX:ICSU,0:IP=10.20.3.2;ZQRX:ICSU,0:IP=10.20.4.2;ZQRX:ICSU,0:IP=10.2.5.1;ZQRX:ICSU,0:IP=10.2.6.1;


Planningsiteconfigurationforsignaling

Issue:04C DN0628311 29

Example:Configuring DSCP value for RANAP signaling or RNSAP signaling

ThefollowingexampleistoconfiguretheDSCPvalue30intheSCTPparametersetwhichisusedbytheRANAP/RNSAPsignaling.

1. ConfigureDSCPvalueforRANAPsignalingorRNSAPsignaling.ZOYT::DSCP=30;

2. CheckDSCPvalueforRANAPsignalingorRNSAPsignaling.ZOYO:NAME=;


30 DN0628311 Issue:04C

5 Planning M3UA networkBefore you startCheckthattheassociationsetandSCTPassociationparametersyouplantousearecompatiblewiththeotherend.Formoreinformation,refertosectionsModifyingassociationsetlevelparametersofM3UAandModifyingSCTPassociationlevelparameters.

g ForinformationaboutM3UAlinks,seeWCDMA RAN: Access Network (RNC and Transport)

Steps1. Plantheredundancyofconnections.

SpreadM3UAassociationstoasmanysignalingunitsaspossible,consideringthenumberofunitsinbothendsoftheassociationset.Rememberthat4-bitSignalingLinkSelection(SLS)isusedforloadsharingbetweenassociations,andthatthenumberofassociationsinanassociationsetshouldbe2,4,8,or16;otherwise,theloadineachassociationisnotevenandtheunitloadwillnotbeeveneither.IfanassociationsetcontainsmorethanoneSCTPassociation,eachassociationcantakecareoftheothers'trafficifsomeofthemfail.TherecommendednumberofSGsistwo.Formoreinformation,refertosectionMTPlevelsignalingnetworkintheConfiguring Signaling Connections in ATM Network(RNC)document.

2. Planwhatkindofaconnectionisused.YoushoulddeterminewhetheryouareusinganASP-SGPoranIPSP-IPSPconnection.Formoreinformation,refertoUseofM3UAstack.

3. PlanifSignalingPointManagementClusterisusedornot.SPMCcanbeusedifforsomereasonitisnotpossibletogiveseparateSPCaddressestotheSGandthenetworkelementfunctioningasanASP.SPMCconfigurationcanalsobeusedwhendifferentM3UAconfigurationsneedtobeusedtogether.SPMCisaspecialconfiguration,throughwhichitisnotpossibletodirecttrafficdestinedtoanotherDPC(STPtraffic),butitiscapableofreceivingandhandlingthesignalingtrafficdestinedtotheSPMC.Figure15:ExampleofsignalinglinksrelatedtoSPMCshowsanexampleofthesignalinglinksrelatedtoSPMC.


PlanningM3UAnetwork

Issue:04C DN0628311 31

Figure 15 ExampleofsignalinglinksrelatedtoSPMC

SP ARNC/BSC/PSTN

M3UAassociation

M3UAassociation

MSCServer

SignalinglinkMGW

LinkSLC=0 LinkSLC=8LinkSLC=7 LinkSLC=F

Onelinkset

MGW

SPC A

Inthisconfigurationexample,thenormalSPMCiscreatedfirst,byconnectingthesignalingpointcodesofSPAandMSS.Afterthat,theredundantSPMCiscreatedusingsignalinglinkconnections0-7betweenSPAandMGWAand8-FbetweenSPAandMGWB.

4. Planthesignalingroutesetparameterscarefully.ThebasicruleisthatwithsignalingroutesetbetweenMSSandMGWtheIETFsignalingrouteparametersetisusedincaseofanM3UAconnection.AllsignalingroutesetswhichareavailableviaMGWshallbeconfiguredsothatausedsignalingrouteparametersetisbasedonsomeoftheMTP3standards.ThatkindofparametersetsareforexampleITU-TandANSIparametersets.ThisrecommendationshouldbefollowedalsowithsignalingroutesetswhichareleadingtotheBSCorRNCviaMGW.

g SignalingrouteparametersetforA-interface(parameterset1listedbyNNIMMLcommand)shallbeusedonlywhensignalingroutesetleadsdirectlytoanadjacentsignalingpoint.

5. PlantheSCCPlevelsignalingnetwork.ProceedwithplanningaccordingtosectionSCCPlevelsignalingnetworkintheConfiguring Signaling Connections in ATMNetwork (RNC)document.

PlanningM3UAnetwork ConfiguringSS7SignalingTransportoverIPforIPA-RNC

32 DN0628311 Issue:04C

6 Creating M3UA configurationPurposeRNCsupportsIP-basedIuandIurSS7signalingstack.SS7overIPsignalinglinksetcanbeconfiguredintheRNCusingeitherIPoA(IPoverATM)orIPoverEthernet.

Before you startIfIPoverATMsolutionisused,dothefollowingfirstbeforeperformingthisprocedure:

ConfigureATMresources.Forinstructions,seeCreatingATMresourcesinRNC.ForinformationonplanningsiteconfigurationforIPoverATM,seePlanningsiteconfigurationforsignaling.

ConfiguretheIP-basedsignalingtransportoverATMconnectionforRNCcontrolplane.Forinstructions,seeConfiguringsignalingtransportoverIPoverATMforcontrolplane.

IfIPoverEthernetsolutionisused,dothefollowingfirstbeforeperformingthisprocedure:

CreatetheLANconfiguration.Formoreinformation,seePlanningsiteconfigurationforsignaling.

ConfiguretheIP-basedsignalingtransportoverEthernetforRNCcontrolplane.Forinstructions,seeConfiguringsignalingtransportoverIPoverEthernetforcontrolplane.

g YoushouldalwaysusethelogicalIPaddressoftheunitandlogicalstaticrouteconfigurationwhenpossible.Otherwise,theremaybeproblemsafterunitswitchover.

Steps1. Createownsignalingpoint,ifasignalingpointdoesnotexist.(NRP)

ZNRP:,,,:::;

2. Createanassociationset.(OYC)OYC::: [SCTP USER | M3UA def];Remembertocheckiftheassociationsetparametersarecorrect.Formoreinformation,refertosectionModifying association set level parameters of M3UA.

3. Addassociationstotheassociationset.(OYA)OYA::,:: [prio | NORMAL def];

g Bydefault,thenumberofstreamintheM3UAassociationis16.Itshouldbenotedthatiftheotherpeercannotsupportasmanyinboundstreamsastheclienthasassignedanoutboundstream,thenSCTPprotocolestablishesanassociationbyusinglowervalueofnumberofstream.Thisshouldbetakenintoaccountwhenconsideringtheresourcesoftheclient.

4. ConfiguretransportaddressesofSCTPassociation.(OYP)


CreatingM3UAconfiguration

Issue:04C DN0628311 33

OYP: : , :, [source address 2], [source port]:, [netmask/prefix], [secondarydestination address], [netmask/prefix], [destination port];Inthisphase,definethesourceanddestinationportnumbersandsourceanddestinationIPaddressesfortheSCTPassociation.OntheserversideifdifferentsourceIPaddressesareconfiguredfortwoserverassociationsresidinginthesamesignalingunit,youneedtoconfiguredifferentsourceportsforthoseassociations.Payattentionthattherecannotbebothsingle-homedandmulti-homedassociationsconfiguredwiththesameportnumberinthesamesignalingunitontheserverside.Forexample,sourceIPaddress10.20.1.1withportnumber2905isconfiguredforasingle-homedassociationinoneserverend,andsourceIPaddresses10.20.1.1and10.20.2.1withthesameportnumber2905areconfiguredforamulti-homedassociationinthesamesignalingunitofthesameserverend,thenthefirstassociationcannotworkproperly.

g ZOYNisnolongerusedinSCTPcreationfromRN4.0.WhetherunitspecificsourceIPaddressexistornot,itdoesnotaffectsystemfunctionality.

5. SetandmodifySCTPassociationsetparametervalues.(OYM)OYM: : (NAME = | ROLE = | VERSION = | TRAFFIC = | ASP = | REG = | SSNM = | NETWORK = | IPSP = | ROUTING = | FIRST = | PARAMSET = | TACK = | HB = );

6. Checktheassociations.(OYI)OYI:[ [NAME= | NBR=...] | def]: [A | H | H def];VerifythattheassociationswerecreatedcorrectlyandthattheyhavecorrectIPaddressesbyusingtheOYIcommand.

7. CreateIPtypeSS7signalinglinkandlinkset.(NSP)NSP:, , : : ;Inthisstep,createasignalinglinksettodestinationpoint.Anetworkindicatorvalueandsignalingpointcodeaddressofdestinationpointaredefinedexplicitlywheretheassociationsetisconnected.

8. CreatetheSS7signalingrouteset.(NRC)NRC:, , , [ | 0 def], [ | D def ], [ | N def ]:( [ | def ], [ | def ], [ | def ], )... ;

9. (Option)ActivatetheSCTPassociationsoftheassociationset.(OYS)Thisstepisoptional.ItallowsnoeffectontheM3UAsignalinginteractionwhenyouactivatetheSCTPassociations.

CreatingM3UAconfiguration ConfiguringSS7SignalingTransportoverIPforIPA-RNC

34 DN0628311 Issue:04C

OYS:::;10. Activatethesignalingnetworkconfiguration.

Theactivationprocedureisthesameaswhenyoucreateanon-IPconnection.WhenyouactivateanSS7signalinglink,thesystemautomaticallyattemptstoactivatealltheassociationsbelongingtotheassociationset.TheSS7signalinglinkisactiveifatleastoneassociationbelongingtoitsassociationsetisactive.Tointerrogatethestatesoftheassociations,usetheOYIcommand.Formoreinformation,seeActivatingMTPconfigurationinConfiguring Signaling Connectionsin ATM Network (RNC).

Further informationExample:CreatingIPconfigurationbetweenRNC(client)andMSS(server).

g ThisisonlyoneexampleofM3UAusage.TheconfigurationexamplecanbeappliedtoallenvironmentswhereM3UAisplannedtobeused.

TheSIGUunitsoftheMSS(MSS10)areasfollows:

SIGU0

EL0131.228.40.10

EL1131.228.41.10

SIGU1

EL0131.228.40.11

EL1131.228.41.11

TheICSUunitsoftheRNC(RNC400)areasfollows:

ICSU0

AA511132.228.45.4

AA511132.228.46.4

ICSU1

AA511132.228.45.5

AA511132.228.46.5

TheNPGEunitsoftheRNC(RNC400)areasfollows:

NPGE0

IFGE0132.228.45.40

IFGE1132.228.46.40

IFAI0isconnectedwithAA0ofICSU-0




IProutesareconfiguredcorrectly.


CreatingM3UAconfiguration

Issue:04C DN0628311 35

Creating M3UA configuration between RNC and MSS for Iu-CSinterface1. Createownsignalingpoint,ifasignalingpointdoesnotexist.

ZNRP:NA0,400,SP400,STP:STAND=ITU-T:3::;2. CreateanassociationsetcalledTOMSS10.

ZOYC:TOMSS10:C;3. AddtwoassociationstotheassociationsetTOMSS10.

ZOYA:TOMSS10:ICSU,0,:SS7:;ZOYA:TOMSS10:ICSU,1,:SS7:;

4. AddSCTPtransportaddressestotheassociation.ZOYP:M3UA:TOMSS10,0:"132.228.45.4","132.228.46.4":"131.228.40.10",24,"131.228.41.10",24,;ZOYP:M3UA:TOMSS10,1:"132.228.45.5","132.228.46.5":"131.228.40.11",24,"131.228.41.11",24,;

5. VerifytheIPaddressesintheassociationsetTOMSS10.ZOYI:NAME=TOMSS10:A;

6. CreateanSS7signalinglinksettousetheassociationsetTOMSS10.ZNSP:NA0,,,,:TOMSS10;

7. CreatetheSS7signalingroutesetwiththeNRCcommand.ZNRC:NA0:,:;

8. ActivatetheSCTPassociations.ZOYS:M3UA:TOMSS10,0:ACT;ZOYS:M3UA:TOMSS10,1:ACT;

9. Activatethesignalinglinks.ZNLA:;ZNLC:, ACT;

10. Activatethesignalingroutesets.ZNVA:NA0,:,;ZNVC:NA0,:,:ACT;

ForMSSconfiguration,refertoappropriateMSSdocumentation.

CreatingM3UAconfiguration ConfiguringSS7SignalingTransportoverIPforIPA-RNC

36 DN0628311 Issue:04C

7 Modifying SIGTRAN parametersThissectiondescribeshowtomodifySIGTRANparameters.

7.1 Modifying association set level parameters ofM3UAAssociation set level parametersNAME ASSOCIATIONSETNAME

Symbolicnameoftheassociationset.

ROLE ASSOCIATIONSETROLE

Theroleoftheassociationset(SERVER/CLIENT).IftheroleoftheassociationsetisClient,thentheownpeerinitializesallSCTPassociationsofthatassociationset.ThisparameteralsocontrolsM3UAmanagement.IftheroleisClient,theexchangestartsASPstatemanagementproceduresandtheotherpeeronlysendsanacknowledgementmessageinbothASPandIPSPcases.

VERSION M3UASPECIFICATIONVERSION

UsedversionoftheM3UAspecification.IfotherpeerssupportadifferentversionoftheM3UA,thentheversionparametershouldbechangedtothesameversionasthatoftheremotepeer.ThedefaultisM3UAversion1.0(RFC).

Supportedversionsareasfollows:

5...M3UASPECIFICATIONVERSION05(DRAFT)



16...M3UASPECIFICATIONVERSION1.0(RFC)

g Bydefault,Version1.0isused.Normally,thereisnoneedtomodifythisparameterexceptinveryspecialcases.

TRAFFIC TRAFFICMODE

Trafficmodeoftheassociationset.Twotypesoftrafficmodesaresupported:over-rideandloadsharing(default).ThisparametercontrolshowtrafficisroutedbetweenSCTPassociationsintotheassociationset.

ASP ASPMESSAGES


ModifyingSIGTRANparameters

Issue:04C DN0628311 37

TheparametercontrolsifASPmanagementmessages(ASPTMandASPSM)areusedornotintheassociationset.Bydefault,ASPmanagementmessagesareinusewhentheversion1.0oftheM3UAisused.

TACK ACKNOWLEDGEMENTTIMERFORASPSMANDASPTM

TheparameterdefinesthetimeM3UAwaitsforresponsetothesentASPSMandASPTMmessage(forinstance,ASPUPACKforthesentASPUP,orASPACACKforthesentASPAC)beforeresendingthemessage.

HB M3UAHB.INTERVAL

TheparameterdefineshowlongtimeM3UAwaitsuntilitsendsthenextM3UABEATafterreceivingBEATACKtothepreviousBEAT.Value0meansthattheM3UAdoesnotsendM3UAheartbeat.NotethatM3UAalwayssendsBEATACKasaresponsetoBEAT,independentofthisparametervalue.

REG REGISTRATIONREQUEST

Theparametercontrolsifdynamicroutingkeyregistrationisinuseornot.Bydefault,dynamicroutingkeyregistrationisused.However,ifdynamicroutingkeyregistrationisnotanoptioninthereceivingparty'sM3UA,thisproceduremaybedenied.

SSNM SSNMMESSAGESNEEDTOBEBROADCASTEDTOALLASPS

TheparametercontrolsthebroadcastoftheSSNMmessages.ThebroadcastoftheSSNMmessagestoallactiveASPsarenotusednormally.

Iftheremotepeer'simplementationdoesnotsupportcentralzedASPmanagementintheAS,theremaybeaneedtobroadcasttheSSNMmessagestoeachactiveASPs.ThisfeaturecanbeusedwithLoadsharingmodeonly.

NETWORK NETWORKAPPEARANCE

Networkappearancewhichisusedintheassociationsetinquestion.Thisisanoptionalparameter,andthereforenotnecessarilysupportedinallM3UAimplementations.Ifnotsupported,NetworkAppearancecanberemovedfromSSNMmessageswiththeNNMcommand(ParameterGroupD,parameterUSE_OF_M3UA_NW_APP).FromDatamessage,NetworkAppearancecanberemovedsothatitsvalueismodifiedasamaximumone.

0-4294967294RangeofNetworkAppearanceparametervalue

ModifyingSIGTRANparameters ConfiguringSS7SignalingTransportoverIPforIPA-RNC

38 DN0628311 Issue:04C

4294967295NetworkAppearanceisnotusedindatamessage

IPSP SENDINGOFASPMESSAGESINIPSPCONNECTION

TheparametercontrolsthesendingofASPmanagementmessagesintheIPSPmode.Whenthisparameterisseton,theserveralsostartstheASPTMandASPSMmanagementsequences.Inotherwords,thesystemworksinasocalleddoubleendedIPSP-IPSPmode.

ROUTING ROUTINGCONTEXT

TheparameteristhedefinedvalueoftheRoutingContext.ThevalueoftheRoutingContextcanbeconfiguredonlywhentheregistrationrequestparameterisinactive.ThisparameterneedstobemodifiedonlyincaseofstaticconfigurationoriftheremotepeerdoesnotsupportRoutingContextparameter.RoutingContextparametercangetthefollowingvalues:

0-4294967294RangeofRoutingContextparametervalue

4294967295RoutingContextisnotsupported

FIRST FIRSTDATASTREAMNUMBER

Theparameterisdefinedasthenumberofthefirstdatastream.Normally,thefirstdatastreamnumberis1.WhenM3UAversion1.0isused,thefirstdatastreammustbe1.

ThefirstdatastreamnumberhastobemodifiedonlyifremotepeersupportsanearlierM3UAdraftspecification.

Eachassociationsethasitsownparameters.Inmanycases,itisnotnecessarytochangetheparameters.However,youmayneedtochangetheparametersiftheremotepeersupportsadifferentversionoftheM3UAspecificationortheremotepeerdoesnotsupportalltheoptionalM3UAfunctionalities.

TheassociationsetlevelparameterscanbemodifiedbyusingtheOYMcommand.AllofthoseparametersarerelatedtotheM3UA.

g Theaboveparameterscanbemodifiedonlywhentheassociationsetisdeactivated.Theassociationsetcanbedeactivatedbydeactivatingasignalinglinkwhichisusingthatassociationset.

Before you startSteps

1. Checkwhethertheparametershavesuitablevalues.(OYI)TheassociationsetparameterscanbeinterrogatedwiththeOYIcommand.

2. Ifyouneedtomodifytheparametervalues,deactivatethecorrespondingM3UAlink.(NLC)



Issue:04C DN0628311 39

TheNLIcommandshowsthelinkthatcorrespondstotheassociationset.TheNLCcommandbringsallassociationsofthesetdown.

3. Changetheparametervalues.(OYM)Findoutthereasonwhyandwhichparametersneedtobechanged.YoucanchangetheparametervalueswiththeOYMcommand.

4. ActivatethecorrespondingM3UAlink.(NLC)

7.2 Modifying SCTP association level parametersTheSCTPassociationlevelparametersarethefollowing.TheseparameterscontrolhowtheSCTPassociationisworking.

RTO.min Thisparameterdefinestheminimumvalueofretransmissiontime-out.

IfthemessageaverageRound-TripTime(RTT)islessthan70ms,thepredefinedparameterset(SS7)canbeused.ThedefaultvalueoftheRTO.minparameteris150msintheSS7parameterset.

t WerecommendthatyouconfiguretheRTO.minvalueatleasttwicetheRTTvaluetoavoidunnecessarymessageretransmissions.

RTO.max Thisparameterdefinesthemaximumvalueofretransmissiontime-out.TheSCTPincreasesthere-transmissiontimesupervisionexponentiallyaftereachretransmissionattempt.

ThedefaultvalueoftheRTO.maxparameteris200msinthepredefinedSS7parameterset.

EachSCTPpathmaintainsitsownretransmissiontimer.TheretransmissiontimerisdeterminedwithRTO.minvalue,RTO.maxvalue,andcalculatedRTOvalue.IfthecalculatedRTOvalueislessthantheRTO.minvalue,theRTO.minvalueischosenastheretransmissiontimer.IfthecalculatedRTOvalueisgreaterthantheRTO.minvalueandlessthantheRTO.maxvalue,thecalculatedRTOvalueischosenastheretransmissiontimer.IfthecalculatedRTOvalueisgreaterthantheRTO.maxvalue,theRTO.maxvalueischosenastheretransmissiontimer.

Inaddition,theSCTPincreasestheretransmissiontimerexponentiallyaftereachretransmissionattemptforeachpath.Thatis,theSCTPdoublestheretransmissiontimerafterthepreviousretransmissionattempt.IfthedoubledretransmissiontimerisgreaterthantheRTO.maxvalue,theRTO.maxvalueischosenastheretransmissiontimer.Otherwise,thedoubledretransmissiontimerischosenastheretransmissiontimer.

RTO.initial ThisparameterisusedasdefaultRTOvaluewhenanSCTPpathisjustestablished.Onceanacknowledgementpacketisreceivedthroughthispath,theRTOvalueiscalculated.


40 DN0628311 Issue:04C

SACK period ThisparameterindicatesamaximumdelaywhichmessagereceivershallwaitforanotherdatachunkuntilitshallsendSACKmessageforanacknowledgementofareceiveddatamessage.

ThedefaultvalueoftheSACKperiodis200ms.TheSACKperiodcanneverbemorethan500ms.

HB.Interval Thisparameteristhebasicvalueoftheheartbeatinterval.Theheartbeatintervalinreallifeisthesumofthefollowingparameters:HB.intervalvalue,RTO.min,andthevalueofsmallrandomjitter.UsedHB.intervalvalueandthevalueofRTO.mincomefromtheparameterset,butthevalueofjittercanvarybetweennetworksandnetworkelements.Whentheparametervalueis0,theSCTPheartbeatisoff.

Path.Max.Retrans Thisparameterdefinesthemaximumnumberofunacknowledgedtransmissions(includingheartbeats)perpath.Whenthethresholdvalueisreached,thepathismarkedinactive.

Association.Max.Retrans

Thisparameterdefinesthemaximumnumberofunacknowledgedtransmissions(includingheartbeats)perassociation.Whenthethresholdvalueisreached,theassociationismarkedaborted.

CHECKSUM ThisparametercontrolswhichChecksummethodisusedinanassociation.

TheAdler-32ortheCRC32cmethodcanbeused,buttheCRC32cchecksumisrecommended.CRC32cisusedbydefault.

BUNDLING ThisparametercontrolsiftheuserapplicationallowsordoesnotallowmorethanonechunkwithintheSCTPpacket.Bundlingisusedbydefaultinthesystem.

EachusermessageoccupiesitsownDATAchunkifbundlingisnotallowed.

g Evenifthebundlingoptionisnotseton,theSCTPstackmightsendtheSCTPcontrolmessageanddatamessagewithinonedatagram.Retransmittedmessagesarealsoallowedtobesentwithinonedatagramevenifthebundlingoptionisnotseton.

DSCP ThisparameterdefinesthevalueofDiffServCodePointinSCTPlevel.

Thevaluerangeisfrom0to63.



Issue:04C DN0628311 41

g AllpredefinedparametersetshavedefaultDSCPvalue34inanewinstalledRNC.Butduringupgrade,theoriginalparameterDSCP_FOR_SIGNALINGinPRFILEwillbesettoallpredefinedparametersetsasdefaultDSCPvalue.

TheSCTPparametersshouldbeuniformatbothendsoftheSCTPassociation.Thesystemincludestwopre-packagedSCTPparametergroups.ThefirstonecontainstheIETFcompliantparameters,andthesecondonecontainsapre-tunedparametertoensurethattheMTPperformancerequirementsofanSS7networkaremet.TheGeneralandSatelliteparametergroupscontainsuggestedparameters.Table1:Summaryofsuggestedparametersetssummarizesthedifferencesbetweenpredefinedparametersets.

Table 1 Summaryofsuggestedparametersets

IETF

SS7

GENERAL

SATELLITE

RTO.min 1s 150ms 250ms 750ms

RTO.max 60s 200ms 400ms 1.5s

RTO.init 3s 200ms 200ms 1s

HB.interval 30s 1s 1s 2s

SACK.period 200ms 110ms 200ms 200ms

Path.Max.Retrans 5 2 2 2

Assoc.Max.Retrans 10 4 4 4

CheckSum CRC32 CRC32 CRC32 CRC32

Bundling Yes Yes Yes Yes

DSCP 34 34 34 34

g Thepre-packagedparameterscannotbemodifiedwiththeOYTcommand.

TheIETFparametersetofferstheRFC2960compliantparametersfortheSCTPstack.Thisparametersetisnotfeasiblefortelecomsignalingpurposes.ItismorefeasiblewithdataorientedapplicationslikeWebbrowsers.

TheSS7parametersetofferspre-tunedparametersforconnectionsimilartoMTP3.ThisparametersetisdesignedtomeethighperformancerequirementsoftheMSSSystem.ItcanbeusedwithaconnectionbetweenNSNMSSandMGW.UsingSS7parametersetisarequirementfortheWANenvironment.Forthisreason,thisparametersetisnotthebestchoiceinallcaseswhereatraditionalTDM-basedconnectionisreplacedwithasignalingoverIPsystem.Itshouldberememberedthatthisparametersetshallbeusedinbothpeers.


42 DN0628311 Issue:04C

TheGeneralparametersetisdesignedforacasewhereNSNsystemisusedwithathirdpartysystem.

TheSatelliteparametersetisdesignedtotakeintoaccountadelaycausedbyasatellite.

Itshouldberememberedthatthepre-definedparametersetsareonlyoneexampleofpossiblecombinationsoftheSCTPparameters.AparametersethelpstostartsignalingtransportoveranIPconfiguration.

g ThevaluesofthePath.Max.RetransandAssociation.Max.Retransparameterscanbeconfiguredindependently,butcarelessconfigurationcanleadanassociationtothestatewhereallthedestinationaddressesofthepeerareunreachable(socalleddormantstate),butthepeerstaysinareachablestate.Toavoidthissituation,youshouldavoidsettingthevalueoftheAssociation.Max.RetransparameterhigherthanthetotalsumofthevaluesofPath.Max.Retransforallthedestinationaddressesofthepeer.

WhenthecapacityoftheLANiswell-knownandabetterperformanceofrecoveryisrequired,youcantunehowtheSCTPassociationshouldworkbyusingtheSCTPassociationlevelparameters.

TomodifytheSCTPassociationlevelparameters,followthestepsbelow.

Modifying SCTP association level parameters

g Sincethevaluesofpredefinedparametersetscannotbemodified,createanewparametersetifyouneedtouseuser-definedparametervalues.

1. Createanewparametersetbycopyinganexistingparameterset.(OYE)Forexample,createthenewparametersetofTEST1bycopyingthepredefinedparametersetofIETF.OYE:TEST1:IETF:;

2. Checkthevaluesoftheparameters.(OYO)CurrentparametervaluescanbeinterrogatedwiththeOYOcommand.

3. Changethevaluesoftheparameters.(OYT)Accordingtoyourrequirements,changethecurrentvaluesoftheparametersetTEST1withthecommandOYT.

4. DeactivatethecorrespondingM3UAlink.(NLC)TheNLIcommandshowsthelinkthatcorrespondstotheassociationset.TheNLCcommandbringsallassociationsofthesetdown.

5. Changetheparametersetofassociationset.(OYM)SCTPparametersetofM3UAassociationsetcanbechangedwiththeOYMcommand.

6. ActivatethecorrespondingM3UAlink.(NLC)



Issue:04C DN0628311 43

g ItisalsopossibletomodifySCTPparametersthatarealreadyinanactiveassociation.YoucanmodifytheparameterswiththeOYTcommand.Butinordertobringtheparameterchangeintoeffect,youneedtotakeoneofthefollowingactions:

DeactivatetheM3UAlinkwiththeNLCcommandandthenactivatetheM3UAlinkagainwiththeNLCcommand.

DeactivateonebyoneeachSCTPassociationoftheassociationsetwiththeMMLcommandOYS,andactivateitagainwithOYScommand.Eachassociationshouldbereactivated,butitisnotnecessarytodoitatthesametime.

ThedeactivationoftheM3UAlink(ZNLC:...:INA;)orSCTPassociation(ZOYS:...:DOWN;)doesn'tcausetheclosingofthelisteningsocket(commandQRScanshowthelisteningIPaddressandport).ThelisteningsocketshouldbeclosedwhenthelastserverassociationwiththesamesourceportisremovedwithcommandOYR,orwhencommandOYPisgivenandtheoldsourceportofthisassociationisnotusedbyotherserverassociationsinthesamesignalingunit.


44 DN0628311 Issue:04C

8 Deleting IP signaling linksPurpose

ThissectiondescribeshowtodeleteM3UAsignalinglinks.

Before you start

RemovefirsttheSCCPandMTP3levels.Formoreinformation,seeRemovinganMTPsignalingpointinConfiguring Signaling Connections in ATM Network (RNC).

1 Delete the signaling link set. (NSD)DeletethesignalinglinksetwiththeNSDcommand.

2 Remove the unused association set. (OYD)OYD:;


DeletingIPsignalinglinks

Issue:04C DN0628311 45

9 Signaling transport over IP troubleshooting

9.1 IP signaling link activation failsTheprocedureforcheckingIPtypesignalinglinksisdifferentfromcheckingordinarysignalinglinks.FollowtheprocedureifyouhavenotbeenabletoactivatetheIPsignalinglinkyouhavecreated,andthesignalinglinkstaysinthestateUA-INS.

Steps1. Checkthealarms(AHO).

a.CheckthefollowingalarmswiththeAHOcommand:1273,2069,3156,3159,and3155.b.Ifthereareanyalarms,followthealarminstructions.

2. Checkthestatesandparametersoftheassociationsets(OYI).Formoreinformation,refertoModifyingassociationsetlevelparametersofM3UA.a.CheckthestatesandparametersoftheassociationsetswiththeOYIcommand.b.ChecktheSCTPlevelparameters.CheckingisespeciallyimportantincaseofretransmissionandalsoiftheSCTPassociationgoesdown,butthereisnoLANfailure.

3. Checkthesignalinglinkparametersetandtestingoflinks(NCI,NSI).

g Youneedtocompletethissteponlyifthefarendofthelinkisanothervendor'sproductoranyofthefollowingNSNproducts:SCP,SMSC,3G-SGSN,orFlexiServer.

a.CheckthesignalinglinkparametersetwiththeNCIcommand.Thedefaultvalueis0.

b.Changethevalueto7withtheNCLcommand.

c.CheckwiththeNSIcommandifthetestingofthelinksetisdenied.Ifitisnot,denyitwiththeNSTcommand.ThedefaulttestingoftheM3UAlinksetisdenied.

4. CheckiftheIPaddressesofthelocalsignalingunitarecorrect(QRI/Q6I).a.CheckiftheIPaddressesofthelocalsignalingunitarecorrecteitherwiththeQRI(forIPv4)orQ6I(forIPv6)command.b.ComparetheIPaddressestotheIPaddressesassignedtotheassociationsatthefarend.c.CheckinterfacerunningstatuswiththeQRScommand.ForexampleQRS:,:INS,;d.CheckpossibleerrorcounterstoIPstackwiththeQRScommand.ForexampleQRS:::PRO;e.CheckpossibleerrorsfromthePOSIXkernellogwiththePKLcommand.

SignalingtransportoverIPtroubleshooting ConfiguringSS7SignalingTransportoverIPforIPA-RNC

46 DN0628311 Issue:04C

g Connectaserviceterminaltothecorrectcomputerunit.AddthePOMOXIGXserviceterminalextension.YoucanuseforexampletheletterP:

ZLP:P, POM

ZPKL

5. CheckifsourceIPaddressesoftheassociationarecorrect.a.CheckthesourceIPaddresseswiththeOYIcommandincaseofM3UAconnectionproblem.b.CheckthestaticIProuteconfigurationwiththeQKBcommand.

6. Checkifcorrectchecksumisused.CheckingwhethercorrectchecksumisusedisespeciallyimportantwhentheDX200-orIPA-basednetworkelementworksasaclientandaservercomesfromathirdparty.CheckthepossibleSCTPbadchecksumcounterswiththeQRScommand.

7. ChecktheavailabilityofthepeerIPaddresswithPING(QRX/Q6X).UsetheQRXcommandforIPv4ortheQ6XcommandforIPv6.

8. CheckIPoAchannelstatus.CheckIPoAchannelstatuswiththeQMQcommand.

9. ChecktheLANcables.ChecktheLANcablesandtheirconnections.

10. ChecktheIPnetworkconfiguration.ChecktherouterconfigurationandthesitelevelLANswitchconfiguration.Payattentiontothefollowingpossiblesourcesoffailure:

MTUsize.Thedefaultvalueis1500bytes.Iftunnelledconnectionisused,tuningtheMTUsizemightbeneeded.

Bandwidthlimitorpacketratelimit.CheckfromcoreIProutersifsomebandwidthlimitsareset.

CheckIPnetworksettingssuchasspeedandduplexmode(theseparameterswillbethesameinbothendsofthelink.BydefaultbetweenESBandDX200-basednetworkelementuseauto-negotiationmode).

CheckSTP/RSTP/MSTPsettinginthelayer2network. CheckpossiblebottlenecksintheIPbackbone. Checkthatthesoftwareversionsofroutersandswitchesarecompliant.

11. MonitoringafailedconnectionwithanIPnetworkanalyzer.GoodmonitoringtoolsareforexampleDPDUMPoranEthernetmonitoringtool.Thelatterisfreewaresoftware.

9.2 SCTP association failsThisproceduredescribeshowtotroubleshootwhenSCTPassociationfails.


a.CheckthefollowingalarmswiththeAHOcommand:

SCTP_association_lost(3159)


SignalingtransportoverIPtroubleshooting

Issue:04C DN0628311 47

SCTP_path_failure(3379)TheSCTPassociationmayalsofailbecauseallpathsfailfortheassociation.Formoreinstructions,seePathofSCTPassociationfails.

b.Ifthereareanyalarms,followthealarminstructions.2. Checkthestateofassociationandassociationset.3. CheckthestateofSCTPsockets(QRS).

ForexampleQRS:ICSU,3:ALL;4. ChecktheSCTPerrorcountersandSCTPstatistics(QRS).5. CheckthestaticIProuteconfiguration.

CheckthestaticIProuteconfigurationwiththeQKBcommand.6. ChecktheavailabilityofthepeerIPaddresswithPING(QRX/Q6X).

UsetheQRXcommandforIPv4ortheQ6XcommandforIPv6.7. ChecktheLANcables.

ChecktheLANcablesandtheirconnections.8. ChecktheIPnetworkconfiguration.

ChecktherouterconfigurationandthesitelevelLANswitchconfiguration.Formoreinformation,refertosectionIPsignalinglinkactivationfails.

9.3 Path of SCTP association failsThisproceduredescribeshowtotroubleshootwhenpathofSCTPassociationfails.


a.CheckthefollowingalarmwiththeAHOcommand:SCTP_path_failure(3379).b.Ifthereareanyalarms,followthealarminstructions.

2. Checkthestateofassociationorassociationset.3. CheckthestateofSCTPsockets(QRS).

RNCallowsIPaddresschangeandMTUchangeonIPoAinterfacewhiletheIPaddressisstillusedbytheSCTPstack.ThismaycauseaninconsistencybetweentheSCTPandtheIPlayersleadingtoaninactiveSCTPconnection.Example:QRS:ICSU,0:ALL;IfthestateofanIPaddressconfiguredintheSCTPassociationisinactive(ina),andre-selecting src addrshowsintheLocal AddressfieldoftheSCTPassociation,asindicatedintheexamplebelow,thereasonmightbeIPaddressesconfiguredintheSCTPassociationhavebeenmodifiedordeleted.UNIT: ICSU-0 Active Internet connections (including servers)Proto Recv-Q Send-Q Local Address Foreign Address Statetcp 0 0 *.3452 *.* LISTENudp 0 0 127.0.0.1.524 *.*

Active v4/v6 SCTP connections (including servers)Proto Recv-Q Send-Q Local Address Foreign Address Statesctp 0 0 --- --- ESTABLISHED


48 DN0628311 Issue:04C

Local addr: 10.1.1.7.33056 act,sec ina,prim Foreign addr: 10.1.1.4.2905 act,sec 10.1.1.2.2905 ina,primsctp6 0 0 *.2905 *.* LISTENsctp 0 0 10.1.1.7.2905 *.* LISTENFollowingistheinstructonforcorrectingIPaddressconfigration:

Forsingle-homedassociations,reconfiguretheIPaddress(QRN) IfmultihomedassociationswithbothIPaddressesinactive,configurebothIP

addresses(QRN) IfmultihomedassociationswithonlyoneIPaddressinactive:

a) DeletetheactiveIPconfiguration(QRG)b) ReconfigureIPaddresses(QRN)

g Withmulti-homingconfiguration,oneSCTPassociationconsistsoftwopreconfiguredpaths:primarypathandsecondarypath.Bydefault,datatrafficgoesthroughtheprimarypath.Whentheprimarypathisunavailable,thedatatrafficisswitchedtosecondarypathautomatically,andthesecondarypathstaysassecondaryinsystem.However,iftheSCTPassociationrestartsupandtheprimarypathisstillunavailable,thesecondarypathwillbeidentifiedasprimarytemporarilyinsystem.Lateron,ifthepreconfiguredprimarypathisavailableagain,thedatatrafficwillbeswitchedback,andthepreconfiguredprimarypathresumesitsprimarystate.

4. ChecktheSCTPerrorcountersandSCTPstatistics(QRS).5. CheckthestaticIProuteconfiguration.

CheckthestaticIProuteconfigurationwiththeQKBcommand.6. ChecktheavailabilityofthepeerIPaddressviafailedpathwithPING(QRX/Q6X).

UsetheQRXcommandforIPv4ortheQ6XcommandforIPv6.7. ChecktheLANcables.

ChecktheLANcablesandtheirconnections.8. ChecktheIPnetworkconfiguration.

Checktherouterconfigurationandthesite-levelLANswitchconfiguration.MakesurethatthereisnoESA/ESB/Ciscomisconfiguration,suchasduplexmismatchorRSTP/MSTPusedwithoutedgeportsettingstowardsthesignalingunit.YoucanchecktheswitchconfigurationfromtheESA/ESBwiththefollowingcommands:show vershow running-configshow interfaceshow interface statisticsYoucanchecktherouter(Cisco)configurationwiththefollowingcommands:show vershow running-configshow interfaces status



Issue:04C DN0628311 49

show interfaces counters errorsFormoreinformation,refertosectionIPsignalinglinkactivationfails.

9. ChecktheusedSCTPparametersinbothpeers.a.CheckthevalueoftheSCTPparameterswithOYOcommand.b.IftheSCTPparametersaredifferentbetweenpeers,thevalueoftheSCTPparametersshouldbeharmonizedinbothends.

10. ChecktheSCTPconnectionsforspecialimplementations.Followingaretheinstructionsforcross-connectionsintwospecialimplementations.

a) Thisinstructionisusedforcheckingwhethercross-connectionshappenedwhenlocalIP-baseddefaultGW(gateway)isused.YoucanchecktheroutingtypebycommandQKB.Forexample,oneSCTPassociationisconfiguredasfollows:RNC(c) MGW(s) remark -------------------------A a Primary B b Secondary LocalIP-baseddefaultGWisconfiguredforbothsourceIPAandB.WhenconnectingIPaddressa,AwillbeselectedassourceIPaddress.IfINIT-ACKisnotreceived,BwillbeselectedassourceIPaddress,cross-connectionsmighthappenlikefollows:RNC(c) MGW(s) remark -------------------------B a Primary A b Secondary Recovery procedures

1. SettheassociationDown(OYS)2. SettheassociationActive(OYS)3. Checkthestateofassociation(QRS)

Ifthecross-connectionsstilloccurs,restorethetrafficbyfollowingsteps:

1. SettheassociationDown(OYS)2. Deletetherouteforsecondarypath(QKA)3. SettheassociationActive(OYS)4. Checkthestateofassociation(QRS)5. Recreatetherouteforsecondarypath(QKC)

b) Thisinstructionisusedforcheckingwhethercross-connectionshappenedwhenstaticroutingisusedandbothprimarypathandsecondarypathuseloopbackIP.Forexample,oneSCTPassociationisconfiguredasfollows:RNC(c) MGW(s) remark -------------------------A a Primary B b Secondary Whencheckingstateofassociation,cross-connectionsmighthappenlikefollows:

RNC(c) MGW(s) remark -------------------------B a Primary A b Secondary


50 DN0628311 Issue:04C

RNC(c) MGW(s) remark -------------------------A a Primary A b Secondary

Recovery procedures

1. SettheassociationDown(OYS)2. SettheassociationActive(OYS)3. Checkthestateofassociation(QRS)

9.4 List of debugging commands in a failure caseBeforecontactingNSNfortechnicalsupport,findthefollowinginformationtohelpfindouttherootcauses:

1. IPconfiguration(QRI)2. StaticIProuteconfiguration(QKB)3. SCTPassociationforM3UA(OYI)4. SCTPparameters(OYO)5. SCTPerrorcounters(QRSwithALLandPRO)6. DBDUMPmonitoringorothermonitoringfromtheESBswitchesifpossible.



Issue:04C DN0628311 51

Configuring SS7 Signaling Transport over IP for IPA-RNCTable of ContentsList of FiguresList of TablesSummary of changes1Signaling transport over IP (M3UA)1.1Association1.1.1SCTP multi-homing1.1.2SCTP stream

1.2Association set1.3SGP - ASP communication1.4IPSP-IPSP communication1.5Signaling over IP statistics

2Use of M3UA stack2.1SGP-ASP communication2.1.1Example of M3UA usage

2.2IPSP-IPSP communication2.2.1Use of IPSP-IPSP example at the M3UA

2.3Routing key and routing context2.4Signaling Point Management Cluster2.5Message structure of M3UA

3Basic structures of SS7 signaling over IP network4Planning site configuration for signaling5Planning M3UA network6Creating M3UA configuration7Modifying SIGTRAN parameters7.1Modifying association set level parameters of M3UA7.2Modifying SCTP association level parameters

8Deleting IP signaling links9Signaling transport over IP troubleshooting9.1IP signaling link activation fails9.2SCTP association fails9.3Path of SCTP association fails9.4List of debugging commands in a failure case

Documents

DN0628311-Configuring SS7 Signaling Transport Over IP for IPA-RNC