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

WCDMA RAN, Rel.
RU40,
Operating Documentation,
Issue 06
Configuring SS7 Signaling
Transport over IP for IPARNC
DN0628311
Issue 04C
Approval Date 2013-09-22
ConfiguringSS7SignalingTransportoverIPforIPA-RNC
Theinformationinthisdocumentissubjecttochangewithoutnoticeanddescribesonlytheproduct
defined in the introduction of this documentation. This documentation is intended for the use of
NokiaSolutionsandNetworkscustomersonlyforthepurposesoftheagreementunderwhichthe
documentissubmitted,andnopartofitmaybeused,reproduced,modifiedortransmittedinany
formormeanswithoutthepriorwrittenpermissionofNokiaSolutionsandNetworks.Thedocumentationhasbeenpreparedtobeusedbyprofessionalandproperlytrainedpersonnel,andthecustomerassumesfullresponsibilitywhenusingit.NokiaSolutionsandNetworkswelcomescustomer
commentsaspartoftheprocessofcontinuousdevelopmentandimprovementofthedocumentation.
The information or statements given in this documentation concerning the suitability, capacity, or
performanceofthementionedhardwareorsoftwareproductsaregiven"asis"andallliabilityarisinginconnectionwithsuchhardwareorsoftwareproductsshallbedefinedconclusivelyandfinally
in a separate agreement between Nokia Solutions and Networks and the customer. However,
NokiaSolutionsandNetworkshasmadeallreasonableeffortstoensurethattheinstructionscontained in the document are adequate and free of material errors and omissions. Nokia Solutions
and Networks will, if deemed necessary by Nokia Solutions and Networks, explain issues which
maynotbecoveredbythedocument.
NokiaSolutionsandNetworkswillcorrecterrorsinthisdocumentationassoonaspossible.INNO
EVENT WILL Nokia Solutions and Networks BE LIABLE FOR ERRORS IN THIS DOCUMENTATION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT,INCIDENTALORCONSEQUENTIALORANYLOSSES,SUCHASBUTNOTLIMITEDTO
LOSSOFPROFIT,REVENUE,BUSINESSINTERRUPTION,BUSINESSOPPORTUNITYORDATA,THATMAYARISEFROMTHEUSEOFTHISDOCUMENTORTHEINFORMATIONINIT.
Thisdocumentationandtheproductitdescribesareconsideredprotectedbycopyrightsandother
intellectualpropertyrightsaccordingtotheapplicablelaws.
NSN is a trademark of Nokia Solutions and Networks. Nokia is a registered trademark of Nokia
Corporation.Otherproductnamesmentionedinthisdocumentmaybetrademarksoftheirrespectiveowners,andtheyarementionedforidentificationpurposesonly.
CopyrightNokiaSolutionsandNetworks2013.Allrightsreserved
Important Notice on Product Safety

Thisproductmaypresentsafetyrisksduetolaser,electricity,heat,andothersourcesof
danger.
Only trained and qualified personnel may install, operate, maintain or otherwise handle
this product and only after having carefully read the safety information applicable to this
product.
ThesafetyinformationisprovidedintheSafetyInformationsectionintheLegal,Safety
andEnvironmentalInformationpartofthisdocumentordocumentationset.
NokiaSolutionsandNetworksiscontinuallystrivingtoreducetheadverseenvironmentaleffectsof
itsproductsandservices.Wewouldliketoencourageyouasourcustomersanduserstojoinusin
working towards a cleaner, safer environment. Please recycle product packaging and follow the
recommendationsforpoweruseandproperdisposalofourproductsandtheircomponents.
IfyoushouldhavequestionsregardingourEnvironmentalPolicyoranyoftheenvironmentalservicesweoffer,pleasecontactusatNokiaSolutionsandNetworksforanyadditionalinformation.
DN0628311
Issue:04C
Table of Contents
Thisdocumenthas51pages
Summaryofchanges..................................................................... 6
Issue:04C
1
1.1
1.1.1
1.1.2
1.2
1.3
1.4
1.5
SignalingtransportoverIP(M3UA)............................................... 7
Association.....................................................................................7
SCTPmulti-homing........................................................................ 8
SCTPstream..................................................................................9
Associationset............................................................................. 10
SGP-ASPcommunication.......................................................... 12
IPSP-IPSPcommunication.......................................................... 13
SignalingoverIPstatistics........................................................... 14
2
2.1
2.1.1
2.2
2.2.1
2.3
2.4
2.5
UseofM3UAstack...................................................................... 16
SGP-ASPcommunication............................................................ 16
ExampleofM3UAusage............................................................. 17
IPSP-IPSPcommunication.......................................................... 18
UseofIPSP-IPSPexampleattheM3UA.....................................19
Routingkeyandroutingcontext...................................................19
SignalingPointManagementCluster...........................................20
MessagestructureofM3UA.........................................................22
BasicstructuresofSS7signalingoverIPnetwork.......................24
Planningsiteconfigurationforsignaling.......................................26
PlanningM3UAnetwork...............................................................31
CreatingM3UAconfiguration....................................................... 33
7
7.1
7.2
ModifyingSIGTRANparameters..................................................37
ModifyingassociationsetlevelparametersofM3UA.................. 37
ModifyingSCTPassociationlevelparameters.............................40
DeletingIPsignalinglinks............................................................ 45
9
9.1
9.2
9.3
9.4
SignalingtransportoverIPtroubleshooting................................. 46
IPsignalinglinkactivationfails.....................................................46
SCTPassociationfails................................................................. 47
PathofSCTPassociationfails.....................................................48
Listofdebuggingcommandsinafailurecase............................. 51
DN0628311
List of Figures
Figure1
SCTPretransmission............................................................................8
Figure2
Symmetricnetworklayout.................................................................... 9
Figure3
Asymmetricnetworklayout...................................................................9
Figure4
ExampleofanIPtypeSS7signalinglink........................................... 10
Figure5
Associationset....................................................................................11
Figure6
AnexampleofSGP-ASPcommunication.......................................... 13
Figure7
AnexampleofabasicIPSP-IPSPconfigurationwithapointtopoint
connectioninsidetheIPnetwork........................................................13
Figure8
AnexampleofSGP-ASPcommunication.......................................... 16
Figure9
AnexampleofaSignalingGatewaybetweentwonetworkelementsin
differentprotocols............................................................................... 18
Figure10
AnexampleofcombinedSignalingGatewayandIPSP-IPSP........... 19
Figure11
AnexampleofSignalingPointManagementCluster......................... 21
Figure12
MessagestructureofM3UA............................................................... 23
Figure13
BasicexampleofanetworkthatusesIP............................................24
Figure14
ExampleofpointtopointIPconnection............................................. 24
Figure15
ExampleofsignalinglinksrelatedtoSPMC.......................................32
DN0628311
Issue:04C
List of Tables
Table1
Issue:04C
Summaryofsuggestedparametersets..............................................42
DN0628311
Summaryofchanges
ConfiguringSS7SignalingTransportoverIPforIPARNC
Summary of changes
Changesbetweendocumentissuesarecumulative.Therefore,thelatestdocument
issuecontainsallchangesmadetopreviousissues.
Pleasenotethattheissuenumberingsystem,safetyinformation,andproductnaming
practicearechanging.Formoreinformation,seeGuide to WCDMA RAN Operating
Documentation.
Changes between Issues 04B (2013-09-13, RU40) and 04C (2013-1122, RU40)
AddedoneDSCPfieldinSCTPparameters,followingchaptersareupdatedforthe
feature:
Planningsiteconfigurationforsignaling
ModifyingSCTPassociationlevelparameters
Changes between Issues 04A (2013-07-25, RU40) and 04B (2013-0913, 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.
DN0628311
Issue:04C
SignalingtransportoverIP(M3UA)
1 Signaling transport over IP (M3UA)

TheinformationinthisdocumentrelatestoDX200andIPA2800-basedproducts.
SignalingtransportoverIP(SIGTRAN)containsseveraluseradaptationlayers,oneof
whichisdescribedhere:theM3UA(MTP3UserAdaptationLayer).
M3UAisaprotocolforsupportingthetransportofanySS7MTP3-Usersignaling(for
example,ISUPandSCCPmessages)overIPusingtheservicesoftheStreamControl
TransmissionProtocol(SCTP).Also,provisionismadeforprotocolelementsthatenable
aseamlessoperationoftheMTP3-UserpeersintheSS7andIPdomains.
M3UAprotocolistobeusedinIP-basedIuandIurinterfacesofRNC,whereSignaling
ConnectionControlPart(SCCP)isrequired.SS7signalingcanalsobereceivedover
ATMinterfaceusingtheSS7MessageTransferPart(MTP)toprovidetransport.
1.1 Association
AnSCTPassociationisarelationshipbetweentwocommunicatingpeers.Applicationof
anSCTPisestablishingandmaintaininganassociation.ConfigurationofanSCTP
associationisdoneintheapplicationlevel.Ifbothcommunicatingpeersarebasedon
oursystem,theSCTPassociationhasbeenestablishedbetweentwosignalingunitsby
clientpeer.TheSCTPassociationusesthefollowingaddressparameters:sourceport
number,listofsourceIPaddresses,destinationportnumber,andlistofdestinationIP
addresses.Ifoneofthoseaddressparametersisdifferent,itmeansthatanew
associationshouldbeestablished.Anassociationcanhaveseverallogicalpaths(source
anddestinationIPaddresspair);thatkindofconnectioniscalledamulti-homed
connection.SCTPcanuseamulti-homedconnectionbutaTCPdoesnotknowthatkind
ofarchitecture.Forthisreason,anSCTPassociationismuchmorefaulttolerantthana
TCPconnection.
Fortheabovementionedsignalingadaptationstoworkassolidlyastheirexamples
(Q.921andQ.704),SCTPhasbeenusedinimplementationasthedatalinklayer.SCTP
offerssimilarcertificationcapacitiesascanbeexpectedwhenusingatraditionalTDM
connection.TomeetthetraditionalqualityrequirementswhenusingSCTP,the
retransmissionparametersofSCTPmustbeadjustedsothatthecriteriawillbemetalso
whenusingtheIP-net.WhenreadjustingSCTPretransmissionparametersyouneedto
takeintoaccountthemethodofimplementationoftheIP-net(eitherLANorWAN)as
wellasthequalityofserviceitprovides.Themostcrucialcriteriaoftheseisthetransit
timedelay.
TheClientpeerestablishesanassociation.ThesystemsupportstwodestinationIP
addresses;primarydestinationIPaddressandsecondarydestinationIPaddress.During
theassociationestablishingphasetheClientnormallysendsanSCTPinitializemessage
totheprimarydestinationIPaddress.IftheprimarydestinationIPaddressdoesnot
respond,theClienttriestoestablishanassociationtothesecondarydestinationIP
address.Whenthenetworkfailureintheprimarynetworkisover,thesystemchanges
theconfigurationsothatsignalingtrafficisrunningovertheprimarynetworkandthe
secondarynetworkisrunninginbackupmode.
Issue:04C
DN0628311
1.1.1 SCTP multi-homing

IntheIPterminology,ahostiscalledmulti-homedifitcanbeaddressedbymultipleIP
addresses.TomakefulluseoftheSCTPmulti-homing,thehostalsoneedstosupport
multiplenetworkinterfaces,eachofwhichhastobeconfiguredtoworkinadifferentsubnetwork.TheSCTPmulti-homingisusedonlyforrecoveringfromnetworkfailures.Itis
notused,forexample,forloadbalancing.TheSCTPimplementationsupportstwopaths
foreachassociation.Normallydataissentviatheprimarypath.Ifanetworkfailure
occursintheprimarynetwork,SCTPresendsunacknowledgeddataviathesecondary
pathautomatically.Theapplicationcannotseewhichpathisusedandsendingofdatais
alsonotaffectedintheapplicationlevel.Inthiscase,theSCTPstacktakescareofall
thedetails.
TheSCTPassociationworksnormallysothatdataisrunningviatheprimarypathand
SCTPheartbeatisrunningviathesecondarypath.Ifsomethingunexpectedhappensin
theprimarypath,theSCTPusuallyhasanalternativepathavailable.TheSCTP
monitorsaconditionofthesecondarypathallthetimebyusingaheartbeatmessage.
TheprocessoftheSCTPretransmissionisshowninFigure1:SCTPretransmission,
whichisachievedwiththefollowingparameters:
Retransmissiontime-out,RTO.min300ms
RTO.max500ms
Path.max.retrans2
Assoc.max.retrans4
ForinstructionsonconfiguringtheSCTPparametersandthedescirptionsonthe
retransmissiontimer,seeModifyingSCTPassociationlevelparameters.
Figure 1
SCTPretransmission
EndPoint A
EndPointB
PrimaryPath
300ms
300ms
500ms
500ms
SecondaryPath
PrimaryPath
Primarypath
Unavailable
SecondaryPath
Abort
Inthisprocess,theSCTPendpointAsendsdatafirstviatheprimarypathandstartsthe
retransmissiontimeroftheprimarypath.IfitdoesnotreceivetheSACKmessagefrom
theotherendbeforetheretransmissiontimerexpires,itresendsthedataviathe
secondarypathandstartstheretransmissiontimerofthesecondarypath.Ifthe
transmissioninthesecondarypathisalsounacknowledged,theendpointAstartsthe
secondroundofdataresendingviaprimarypathandsecondarypathwiththe
recalculatedretransmissiontimers.Ifthetransmissionsinboththeprimarypathand
secondarypatharestillunacknowledged,theendpointAdropsthedataandclosesthe
SCTPassociationbysendinganABORTmessagetotheotherend.
DN0628311
Issue:04C
TherearetwotypesofSCTPmulti-homing.
Figure 2
Symmetricnetworklayout
HOST A
HOST B
ThefirsttypeissymmetricSCTPmulti-homingwherebothpeershavetwoormore
externalEthernetinterfacesavailableandconnectionismadebetweenthem.Each
signalingunitcontainstwoEthernetInterfacesinthenetworkelement.SCTPcanuse
bothinterfacesinsuchawaythatoneisworkingasaprimaryandtheotheroneasa
secondarypath.SCTPensuresthatnomessagescangetlostincaseofpathfailure.
EachEthernetportshouldbelongtoadifferentsubnetworkofthesignalingunit,
otherwisemulti-homedconnectionsdonotworkasexpected.
Figure 3
Asymmetricnetworklayout
HOST A
HOST B
Thesecondtypeisasymmetricmulti-homingwhereaconfigurationalsohastwo
separatepathsbutHostAhasonlyoneEthernetportinuse.IftheonlyEthernetportof
HostAorthegatewayrouterwhereitisconnectedfails,thenmulti-homingdoesnot
help.IfHostAisassignedtoasecondnetwork,thentheresiliencyofthenetworkcanbe
improved.ThisadditionaladdressofHostAshouldbetakenintoaccountinthenetwork
configurationoftheroutersaswell.Asaresultofthismodification,incaseofanykindof
networkfailure,multi-hominghelpstoavoidassociationloss.
1.1.2 SCTP stream

SCTPprovidesmultiplestreamfunctionwithinanSCTPassociation.SCTPuses
streamingformessageordering.Eachindependentlyorderedmessagesequenceis
calledastream.Streamisunidirectional,whichmeansthatthenumberofoutbound
streamsandthenumberofinboundstreamscanbedifferent.Thenumberofdata
streamscanvaryfromonetothousands.Themainpurposeofthestreamistoavoidso
calledheadoflineblockingsituation,especiallywhenonlyoneSCTPassociationisin
usebetweennetworkelements.Alternatively,thiscanbeavoidedbyusingmultiple
associations.TheusednumberofoutboundstreamsdependsonSCTPapplications
becauseanapplicationshouldtageachofitsoutboundmessageswithastream
Issue:04C
DN0628311
identifier.Outboundstreamnumber0mightbeusedforaspecialpurpose.Forexample,
M3UAuseradaptationrequiresthatonlyamanagementmessageisallowedtousea
stream0andthereforethefirstdatastreamis1.
InM3UAimplementationitispossibletousemultiplestreamsfordatamessages.
Managementmessagesarealwayssenttostream0.Itispossibletoconfigurewithan
associationsetparameterwhetherthedatastreamis0or1.Itisrecommendedtouse
multipledatastreams;inthatcasethefirstdatastreamisalways1.Numberofstreams
foreachassociationis16intheM3UA,exceptwhentheremoteendsupportsfewer
streamsthanlocalendwantstouse.Inthatcasethesystemisusingalowernumberof
streamsautomatically.
1.2 Association set

Inadistributedarchitectureseveralcomputerunitscandothesamekindoftasks,so
thatsystemresourcescanbeusedmoreefficiently.M3UAhasbeenplannedtoworkin
suchasystem.
SCTPassociationisapoint-to-pointconnectionbetweentwoendpoints(seeFigure4:
ExampleofanIPtypeSS7signalinglink).Inoursystem,anIPendpointisasignaling
unit.Anetworkelementmaycontaintensofsignalingunits.Ifmoresignalingcapacityis
neededbetweentwonetworkelements,signalingcapacitycanbeincreasedbyadding
moreSCTPassociationstotheassociationset.Inthiscase,itisassumedthateach
SCTPassociationiscreatedtoadifferentsignalingunit.Byusingmultiplesignalingunits
inoneassociationset(oneassociationpersignalingunit),yousharetheloadamong
morethanonecomputerunitandatthesametimemakethesignalingconnection
redundant.Onesignalingunitcanbeconnectedtomultipleassociationsetsifthe
networkelementalsoneedstocommunicatewithotherpeers.
Figure 4
ExampleofanIPtypeSS7signalinglink
MGW(server)
Association
RNC(client)
ICSU0
ICSU1
ISU0
IP network
ICSU2
ISU1
ISU2
ICSU3
ISU3
Association
set/SS7
signaling
link
DN0641567
Additionally,whenthereisamultipleassociationsetbetweentwonetworkelements,itis
recommendedthatthesignalingunitisonlyconnectedtooneassociationset.For
example,ifsupportofmultipleSS7networksisrequiredinthenetworkplanning,then
morethanoneassociationsetbetweentwonetworkelementsmustbecreated.Insome
10
DN0628311
Issue:04C
casesitmightbenecessarytocreatemultipleassociations,whichareconnectedtothe
samesignalingunitintheassociationset.Thisisnotrecommendedbutitispossibleif
thenetworkcannotbeplannedinanyotherway.
OntheM3UA,eachIPsignalinglinkisassociatedwithanassociationsetconsistingof
upto32SCTPassociations.However,fororderedmessages,forwhichtheSLSisused
forloadsharing,trafficissharedtoamaximumof16firstactivatedSCTPassociations.
Upto32activeassociationscanbeusedforacasewhereunorderedmessagesare
used.UnorderedmessagemodeispossibleonlywithaninterfacewhereSCCPprotocol
class0hasbeenused.Thestateofasignalinglinkfollowsthestateoftheassociation
set;whenatleastoneSCTPassociationisactiveinsidetheassociationset,the
signalinglinkisactive.
Figure 5
Associationset
Signalingrouteset
Signalinglinkset
Signalinglink
Associationset
Association
Association
Association
TheloadsharingmethodoftheM3UAdependsonsignalingtraffic.Ifsignalingtraffic
requiresanordereddelivery,theSLSvalueisusedforloadsharing.Thismeansthatall
signalingmessageswiththesameSLSaredeliveredviathesameassociationinsidethe
associationset.Incaseofanassociationfailure,itisnecessarytoupdatetherouting
tableoftheassociationset.Whentheassociationfailureisover,thecontentofthe
associationsetroutingtablehastobeexactlythesameasitwasbeforethefailure.
AssociationsetisaNSNspecificconceptthatisrelatedtothedistributed
architecture.TheassociationsetconceptisonlyusedinM3UAconnections.
Eachassociationinsideanassociationsetcanbeinthefollowingstates:
DOWN-BY-USER
Issue:04C
Thisistheinitialstateofanassociationjustaftercreation
withtheOYAcommand.Itcanalsorefertoa'deactivated
bytheuser'stateafterthelatestsystemrestart.The
deactivation/activationisdonewiththeOYScommand.
DN0628311
11
SCTP-DOWN
Thisisthestateofanassociationafterthesystemrestart.
MTPmanagementhasnotyetactivatedtheM3UAlinkthat
correspondstotheassociation,andtheM3UAlinkmaybe
inUA-ADstate(activationdenied).
UP-PROCEEDING
ThisstatemeansthatthenegotiationoftheSCTP
associationisongoing.Theremaybesomeprobleminthe
IPconnectionsothattheSCTPassociationdoesnot
activate.ChecktheIPconnectionwithpingcommandQRX.
ASP-DOWN
ThisstatemeansthattheassociationisupattheSCTP
levelbutdownattheM3UAlevel,thatis,ASP
managementmessageexchangeisongoing.ASPUP(at
theserver)orASPUPACK(attheclient)hasnotbeen
receivedyet,andtheM3UAlinkisnotactive.
ASP-INACTIVE
ThisstatemeansthattheassociationisupattheSCTP
levelbutinactiveattheM3UAlevel,thatis,ASP
managementmessageexchangeisongoing.ASPAC(at
theserver)orASPACACK(attheclient)hasnotbeen
receivedyet,andtheM3UAlinkisnotactive.
ASP-ACTIVE
Thisstatemeansthattheassociationisupatboththe
SCTPandtheM3UAlevel.TheM3UAlinkisactive.
1.3 SGP - ASP communication

signalingGatewayprocessisasignalingagentthatsendsandreceivestelecom
signalingtrafficattheedgeofIPnetwork.SignalingGatewayisasignalingconverter
whereTDMorATMbasedsignalingconnectionisterminated.
Applicationserverisavirtualdatabaseorcallcontrolelement,whichcanserveaspecific
routingkey.Asmentionedearlier,DPCisusedasaroutingkeyatthesolution.
AccordingtoRFC2719,FrameworkArchitectureforsignalingtransport,SGP-ASP
communicationisbasedonIPnetworkastransportationmedium.ASP-SGPconceptis
describedinFigure6:AnexampleofSGP-ASPcommunication.
12
DN0628311
Issue:04C
Figure 6
AnexampleofSGP-ASPcommunication
SEP/STP
ASP
CAP/MAP/...
CAP/MAP/...
TCAP
BICC/ISUP
BSSAP
TCAP
SCCP
BICC/ISUP
BSSAP
SCCP
MTP3
M3UA
MTP2
SCTP
MTP1
IPv4/IPv6
SG
MTP3
M3UA
MTP2
SCTP
MTP1
IPv4/IPv6
Figure6:AnexampleofSGP-ASPcommunicationdescribestheASP-SGPconnection
incaseofM3UA.
1.4 IPSP-IPSP communication

IncaseofIPSP-IPSPcommunication,theservicesofaSignalingGatewaynodearenot
needed,sincebothpeersexistintheIPdomain.AgroupofIPSPsformanApplication
serveratbothendsofthesignalingconnection.ThemessageexchangeinanIPSPIPSPconnectionissingle-endedbydefault,whereonlyoneendpointsendsASP
managementmessages.Theotherpossibilityisthedual-endedmode,whereboth
endpointssendASPmanagementmessages.
Figure 7
AnexampleofabasicIPSP-IPSPconfigurationwithapointtopoint
connectioninsidetheIPnetwork
Applications
Applications
Adaptation
Layers
Adaptation
Layers
SCTP
SCTP
IP
IP
IPSP-IPSP
Issue:04C
DN0628311
13
1.5 Signaling over IP statistics

Inthesignalingunitlevel,theSIGTRANtrafficcanbemonitoredfromtheSCTPstack
counters.TheSCTPstatisticscountersofferanoverallnumberofSCTPtrafficinthe
signalingunit.ThesecounterscontaintrafficfromallSCTPuseradaptations,and
thereforearenotsousefulifoneisinterestedonlyinthetrafficofaspecificSCTPuser
adaptation.TheSCTPstatisticscounterscanbeexaminedusingQRS.
M3UAAssociationSetMeasurement(295H/661)canbeusedtomonitorM3UAtraffic.It
givesinformationontrafficthroughputandqualityofM3UAconnections.The
measurementmeasuresM3UAtrafficfromM3UAlayerandSCTPlayer.
M3UAlayercountersshowthepayloadofSCTPconnection.Fromthecountersofthe
SCTPlayer,youcanretracethetrafficoftheSCTPlayerusedbyM3UAassociation.
TheSCTPlayercountersgiveyoumoreaccurateinformationontherealloadrequired
forsendingM3UAtrafficthroughSCTPbyincludingthenumberofretransmittedSCTP
packetsandSCTPheader.
Unavailabilitycounterscanbeusedformonitoring,forexampleiftheassociationisin
ASP-INACTIVEstate.
ThemeasurementisconfiguredbyusingcommonstatisticsinterfaceT2MMLcommand
groupcommands.
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,theM3UAtrafficcanbemonitoredby
usingtheMTP3levelmatrixmeasurements.TheMTP3matrixmeasurementisbasedon
usinganOPC,DPC,andSImatrix.Thematrixdefinesaconnectionwhosetrafficwillbe
measured.Thismeasurementshowsanamountofspecificsignalingtrafficbetweentwo
signalingpoints.ServiceIndicator(SI)definesconcernedsignalingtrafficandOPCand
DPCparametersshowwhichonesofthesignalingpointsbelongtoameasurement.The
MTP3matrixmeasurementcanbeconfiguredbyusingOIMMLcommandgroup
commands.
Issue:04C
DN0628311
15
UseofM3UAstack
2 Use of M3UA stack

ThissectiondescribestheuseoftheM3UAstack.
2.1 SGP-ASP communication

Thesignalinggatewayprocess-applicationserverprocess(SGP-ASP)communication
isneededwhencommunicatingbetweentheMTP-3peersinSS7andIPdomains.To
enablethecommunication,aseamlessinterworkingfunctionisneededintheSGatthe
M3UAlayerfortheMTP3-UserpeersintheSS7andIPdomains.IntheSGP-ASP
communicationtherelatedconceptsareAS,ASP,SG,andSGP.
Figure 8
AnexampleofSGP-ASPcommunication
AS
SG
ASP
SGP
ASP
SGP
ASP
AgroupofASPsconnectedtoasignalinggatewayprocess(SGP)andservingaspecific
routingkeyiscalledanapplicationserver(AS).WhentheSGProutesthemessage,it
selectsanASbycomparingtheinformationinthemessagewithaprovisionedRouting
Key(DPC+NI).AfterthatanactiveASPinsidethatASisselected.Thewaytheselection
isdonedependsonthetraffichandlingmodeused.Whenthetraffichandlingmodeis
load-share,anactiveASPisselectedfromthelistofactiveASPs:ifthetraffichandling
modeisover-ride,thereisonlyoneactiveASPonthelistatthetime.
EachASPinsideanAScanbeconnectedtoseveralSGPs.AgroupofSGPsforman
SG.WhenroutingthemessageatASP,theSGisfirstselectedbasedoninformationin
themessage,forexample,DPC+NA,andanSGPisselectedinsidethatSG.TheSGPs
insideanSGallhavethesameavailabilityviewoftheSS7network.
EachASPcanbelongtomorethanoneAS,eachASservingitsownroutingkey.When
theASP(inthiscase)wantstoindicatetoanSGPthatitisactiveforhandlingspecific
routingkeytraffic,itneedstousetheroutingcontextvaluetoindicatetotheSGPwhich
routingkeytraffictheASPwantsactivelyhandle.Therearetwopossibilitiestodetermine
16
DN0628311
Issue:04C
UseofM3UAstack
routingcontextvalue:eitherstaticconfiguredordynamicroutingkeyregistration.
Dynamicroutingkeyregistrationprocedureisusedbydefault.Usingroutingkey
registrationisnotmandatediftheotherpeerdoesnotsupportthisoptionalfeature.
IncommunicationbetweenNSNnetworkelements,theASandSGconceptsare
mappedtonetworkelements,forexample,AS=MSS,SG=MGW.Furthermore,the
signalingunitsinthosenetworkelementsaremappedtoASPsinsidetheMSSand
SGPsinsidetheMGW.
WhenasignalingmessagearrivestothesignalinggatewayfromanSS7link,theM3UA
routingfunctionfirstdeterminestheassociationsetbasedoncomparingtheinformation
inthemessagewithaprovisionedRoutingKey(DPC+NI).Insidetheassociationsetan
associationisselected,basedontheSLSvalue,andthesignalingmessageisforwarded
tothesignalingunitwheretheassociationexists.WithIETFconcepts,intheNSN
routingfunctiontheSGP(thesignalingunit)andtheASP(association)fromthatSGP
areselectedatoncebasedontheroutingkey,thatis,DPC+NIandtheSLSvalue.When
thereisaNSNnetworkelementatthepeer,itisrecommendedthatthereisonlyone
associationinonesignalingunitinsideoneassociationset.SeealsoAssociationset.
InastrictIETFsense,theASconceptappliesineachSGPseparately.Theassociation
setconcept,however,isvalidforthewholenetworkelementcollectingallASPs
connectedtoeachSGP(signalingunit).
IntheNSNimplementation,eachassociationcancarryonlythesignalingtrafficrelated
tooneroutingkey.Thatiswhyitisnotnecessarytoconfigurearoutingcontext.The
staticconfigurationoftheroutingcontextisnecessaryanditmightbeneededinsome
compatibilitycases.
However,iftheregistrationparameterisusedinsidetheassociationset,therouting
contextgetsitsvalueduringroutingkeyregistration.Thatvalueissavedtoaworkfilefor
possiblefurtheruseinASPTMmessages.
2.1.1 Example of M3UA usage

SignalingmessagesfromthePSTNareaddressedtotheservernetworkelement.A
signalingroutegoesviathesignalinggateway,whereaprotocolchangefromSS7to
SIGTRANisdone.SignalingmessagesfromtheserveraredestinedtotheSCCPinthe
PSTNnetworkelement.Asignalingroutegoesviathesignalinggateway,wherea
protocolchangefromSIGTRANtoSS7isdone.TheremaybeSTPpointsintheSS7
pathbetweentheSGandthedestinationPSTNnetworkelement.
Issue:04C
DN0628311
17
UseofM3UAstack
Figure 9
PSTN
AnexampleofaSignalingGatewaybetweentwonetworkelementsin
differentprotocols
Signalinggateway
Server
MAP
MAP
TC
TC
SCCP
SCCP
MTP
MTP
M3UA
M3UA
SCTP
SCTP
IP
IP
WhentheSG-ASPcommunicationisused,signalingmessagesfromthePSTNare
destinedtotheserverwithSPCaddressing.Asignalingroutegoesviathesignaling
gateway,wheretheprotocolchangesfromSS7toSIGTRAN.Thisissimilartothe
previousexample,wherethemessagedoesnotgototheSCCPlevelinthesignaling
gateway.
SignalingmessagesfromtheserveraredestinedtothesignalinggatewaywithSPC
addressing.Asignalingroutegoesviathesignalinggateway,wheretheprotocol
changesfromSIGTRANtoSS7.Thisissimilartothepreviousexample,wherethe
messagedoesnotgototheSCCPlevelinthesignalinggateway.
2.2 IPSP-IPSP communication

TheIPSP-IPSP(IPserverprocess)communicationandtheASP-SGPcommunication
arenotdifferentexceptforthefactthatthesignalinggatewayfunctionalityisnotneeded
ateitherendpoint.Theconfiguration,association,andtheIPSPactivationarethesame.
TheIPSP-IPSPhastwokindsoffunctionalmodes.IfthedualendedmodeoftheIPSPIPSPconfigurationisused,the'ASPMESSAGESINIPSP'andthe'ASPMESSAGES'
parametersshouldhavethevalue'Y'atbothendpointsofthesignalinglink.Insingle
endedmode,onlythe'ASPMESSAGES'parametershouldhavethevalue'Y'atboth
endpoints.Ifbothparametershavethevalue'N',theapplicationsserverprocessstate
maintenancemessages(ASPSM)andapplicationserverprocesstrafficmaintenance
messages(ASPTM)arenotexchangedatall.
TheIPSP-IPSPconnectioncanbeusedpoint-to-pointbetweentheM3UAusers.For
example,whentheSignalingGatewayisabletodotheGTtranslationorwhenthereis
anSCCPrelayintheIPnetwork,thefollowingconnectionisIPSP-IPSP.
18
DN0628311
Issue:04C
UseofM3UAstack
2.2.1 Use of IPSP-IPSP example at the M3UA

Figure 10
PSTN
AnexampleofcombinedSignalingGatewayandIPSP-IPSP
Signalinggateway
Server
MAP
MAP
TC
TC
SCCP
MTP
SCCP
SCCP
MTP
M3UA
M3UA
SCTP
SCTP
IP
IP
IPSP-IPSP
orSGP-ASP
InFigure10:AnexampleofcombinedSignalingGatewayandIPSP-IPSP,boththe
IPSP-IPSPandtheSGP-ASPcommunicationispossible.
WhentheIPSP-IPSPcommunicationisused,signalingmessagesfromthepublic
switchedtelephonenetwork(PSTN)aredestinedtothesignalinggatewaywithGT
addressing.TheGTTinthesignalingconnectioncontrolpart(SCCP)ofthesignaling
gatewaygivesasaresulttheSCCPpeerlocatedintheIPnetwork.Thesignaling
messagesfromtheserveraredestinedtothesignalinggatewaywithglobaltitle(GT)
addressing.Theglobaltitletranslation(GTT)intheSCCPofthesignalinggatewaygives
asaresulttheSCCPpeerlocatedintheSS7network.Inthiscase,theconnection
betweenthesignalinggatewayandtheserverisanIPSP-IPSPconnection.
2.3 Routing key and routing context

ThedistributionoftheSS7messagesbetweentheSGPandtheApplicationServersis
determinedbytheroutingkeysandtheirassociatedroutingcontexts.
Routingkeyisapartofthemessageheader.TheInternetEngineeringTaskForce
(IETF)standardforM3UAdeterminesagroupofSS7parametersthatcanbeusedas
anidentifierforanAS.TheseparameterscanbeDPC(DestinationPointCode),NA
(NetworkAppearance),SI(ServiceIndicator),OPClist(OriginatingPointCode),or
certainvaluedomainsofthenumberspaceofCIC(CircuitIdentificationCode).The
parameterDPCisobligatorybecauseitistheSPCaddressusedbytheAS.Eitherone
orseveraloftheseparametersasanidentifierforanAScanbeusedasaroutingkey.
Issue:04C
DN0628311
19
UseofM3UAstack
TheDPCandnetworkappearancetogetherformtheonlyroutingkeythatissupported.
Botharealsomandatoryparametersintheroutingkey.Thenetworkappearancemaps
toanetworkindicator.Thenetworkappearanceparameterisincludedintheassociation
setparameters.Theotherparameters:SI,SSN,orCICarenotincludedintherouting
keybecauseitisexpectedthatthenetworkelementoperatingasanAScanhandlethe
messagedistributingfunctionitself.ThisespeciallyappliestotheSGPwhenthepeeris
aNSNnetworkelement.
Routingcontextisavaluethatuniquelyidentifiesaroutingkey.Theroutingcontext
parameterisa4-bytevalue(integer)whichisassociatedtothatroutingkeyina1-to-1
relationship.Therefore,theroutingcontextcanbeviewedasanindexintoasending
node'sMessageDistributionTable,containingtheroutingkeyentries.Anapplication
serverprocessmaybeconfiguredtoprocesssignalingtrafficrelatedtomorethanone
ApplicationServer,overasingleSCTPAssociation.InASPActiveandASPInactive
managementmessages,thesignalingtraffictobestartedorstoppedisselectedbythe
routingcontextparameter.AtanASP,theroutingcontextparameteruniquelyidentifies
therangeofsignalingtrafficassociatedwitheachApplicationServerthattheASPis
configuredtoreceive.
Youcanconfigureroutingcontextvalueseitherbyusingaconfigurationmanagement
interface,orbyusingspecificproceduresofroutingkeymanagement.Incaseofstatic
configuration,youcanconfigurethevalueoftheroutingcontextmanually.Dynamic
RoutingKeyregistrationisusedbydefault,butifyouwanttohaveastaticconfiguration
forsomereason(forexample,insurecompatibilitywithothervendors'products),referto
OY - SCTP Configuration HandlingMMLcommandmanual.
2.4 Signaling Point Management Cluster

SignalingPointManagementCluster(SPMC)isanexampleofaconfigurationwheretwo
networkelementsshareaSignalingPointCode(SPC).TheSPMCisanentitywhich
consistsoftheSGandApplicationNode,butisvisibletoothernetworkelementsonly
withonesignalingpointidentity,thatoftheApplicationNode.MTPlevel2connections
andotherMTPfunctionalitiesofanSPMCareintheSignalingGateway,whiletheUser
PartfunctionalityoftheclusterisintheApplicationNode.WhentheMTPoftheSignaling
GatewayreceivesaUserPartmessagedestinedtothemanagementcluster,itforwards
themessagetotheApplicationNode.
Asignalingpointmanagementclusterisapplicablewhenasignalingpointbecomesan
ApplicationNodeasitisconnectedtoaSignalingGateway,andthereforestrippedofits
MTPlevel2connectionstoothernetworkelements.Thenothernetworkelementsneed
noconfigurationchanges,astheyseenothingfromthemanagementcluster,butthe
sameoldsignalingpointcode.
AsignalingpointmanagementclustermayalsobeneededwiththeMSSSysteminIUor
Ainterface,becausesomeradionetworkcontrollerimplementationsonlysupport
associatedsignalingmode.However,itisnotmandatorytousethemanagementcluster
whenmigratingintoMSSSystemarchitecture.NSNrecommendsthatwiththeMSS
System,thequasi-associatedsignalingmodeisused,thatis,MGWisusedasanSTP,
whichmakesitpossibletodesignaasignalingnetworkwithmoreredundancy.
20
DN0628311
Issue:04C
Figure 11
UseofM3UAstack
AnexampleofSignalingPointManagementCluster
DPC=123,NI=8
TMSC
TDM
SG
M3UA
ASP
WhentherearetwoMGWintheSPMC,thetwoMGWsprotecteachotherandtheSS7
signalingisredundanteitherby
quasi-associatedsignaling,havingbothMGWsasSignalingTransferPoints(STP)
fortheMSCServer,or
associatedsignaling,havingSignalingPointManagementCluster(SPMC)overone
MSCServerandtwoMGWs.
TheSPMCenablestheinterworkinginamultivendorenvironmentwhentheotherend
(forexample,aBSC)doesnotsupportquasi-associatedsignaling.TheMSSSystemis
seenasonepointcodewhichdoesnotsetrequirementsforothernetworks(PLMNor
PSTN).
TheSPMCisapplicabletosignalingapplicationsthatarenotterminatedintheMGW,
suchasISUP,BSSAP,andRANAP.ThesignalingtrafficthatisterminatedintheMGW,
suchasAccessLinkControlApplicationProtocol(ALCAP)orsignalingnetwork
managementmessages(SNM),needsspecialconsiderationasthepeernetwork
elementsconnectedtotheprotectedMGWpairmaysendsignalingtrafficrandomlyto
eitheroneoftheMGWs.MGWsupportstheforwardingofthesignalingnetwork
managementmessagesoftheMTPsignalinglinkincasetheyarereceivedbyanMGW
thatdoesnotmanagetherelatedsignalingobjects.Adedicatedsignalingpointcode,
thatis,asignalinglinksetfortheALCAP,independentofRANAP,isneededtoterminate
ALCAPintheMGW.
IncaseasignalinglinkbetweentheMSSandtheMGWislost,thestateofthesignaling
linksbetweentheMGWandthePSTN/PLMN/BSC/RNCis'outofservice',butthe
signalinglinksviatheotherMGWareavailable.Incasesignalinglinksbetweenthe
MGWandthePSTN/PLMN/BSC/RNCarelost,thestateofthesignalinglinkbetween
theMSCServerandtheMGWis'outofservice',butthesignalinglinkviatheother
MGWisavailable.
AclusterformedbytwoMGWsandoneMSCServerisconfiguredsimilarlytoacluster
definedintheearlierreleasesbut,inadditiontothat,thereisasignalinglink(for
example,SIGTRAN)betweenthetwoMGWs.Thepurposeofthatadditionalsignaling
linkistoenabletheMTP3signalingmanagementfunctions(signalingtraffic,linkand
routemanagement)inaclusterwhichcontainstwoMGWs.Theconnectedpointsof
initiation(POI),thatis,BSC,RNC,orPSTN/PLMN,considertheclusterasonesignaling
Issue:04C
DN0628311
21
UseofM3UAstack
entityandtheSNMstheysendcanbereceivedbyeitheroneoftheMGWs.Thatiswhy
theMGWsmayneedtoforwardsomeSNMstotheotherMGWwhichhasthesignaling
linksconcerned.
2.5 Message structure of M3UA

ThebasicoverheadonSIGTRANcontainsthefollowingmessageheaders:IP,SCTP,
andM3UA.
22
ThesizeoftheIPheaderdependsonwhatversionoftheIPstackisused,IPv4or
IPv6.ThelengthoftheIPv4headercanvarybetween20and60bytes.20bytesis
thelengthofthebasicIPaddressinIPv4.Theremaining40bytesisthelengthofthe
optionfield.OptionsarenotcommonlyusedontheIPv4.ThelengthoftheIPv6
headeris40bytes+optionsfields.Usuallysomeoptionfieldsareincludedinthe
messagewhenitisusingIPv6.
TheSCTPheadershouldcontainaCommonheader,aChunkdescription,anda
Payloadidentifier.ThelengthoftheCommonheaderis12bytes.Thelengthofthe
ChunkDescriptionis4bytes.ThelengthofthePayloadidentifieris12bytes.The
totalSCTPheadersizeis28bytes.
ThesizeoftheCommonMessageheaderoftheM3UAis8bytes.TheCommon
messageheaderexistsineveryM3UAmessage.Themainpartofthebitrateis
generatedfromthepayloaddatamessages.Therefore,anexampledescribesonly
thestructureofthepayloaddata.TheoptionalNetworkAppearanceparameteris
usedinM3UA.Itssizeis8bytes.TheRoutinglabeloftheMTP3messageis
encodedinseparatefields.TheOPCandDPCfieldsareboth4byteslongandthe
restoftheroutinglabelparameterslikeSI,NI,MessagePriority,andSLSare
encodedinonedword(4bytes).ThetotallengthoftheM3UAmessageheaderis24
bytesinthePayloadDatamessage.
DN0628311
Issue:04C
Figure 12
UseofM3UAstack
MessagestructureofM3UA
31
Header
length
Ver.
Typeofservice
Totallength
Identification
Timetolive
FragmentOffset
Flags
Protocol
Checksum
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

Reserved
Version
MessageClass
Message Type
Messagelength
Tag=210
Length
OriginatingPointCode
DestinationPointCode
SI
NI
MP
SLS
protocol dataoftheM3UA users (VariableLength)
Issue:04C
DN0628311
23
BasicstructuresofSS7signalingoverIPnetwork
3 Basic structures of SS7 signaling over IP

network
WhenIPtransportisusedinthesignalingnetwork,thesignaling end point(SEP)
networkelementisusuallyintheIPnetwork.TheSEPnetworkelementcanbeany
networkelementwheresignalingistransportedviatheIPnetwork(suchasRNCorMSC
Server).
Figure 13
BasicexampleofanetworkthatusesIP
SG
RNC
MSS
IP
SG
InFigure13:BasicexampleofanetworkthatusesIP,therearetwoSignalingGateways
(SGs).Ifoneofthemisunavailable,theotheronecanbeusedasabackup.
WhenanIPconnectionoverATMisused,thesignalingunitmusthaveapointtopointIP
overATMconnectionwiththenetworkelementwhichitisconnectedto.
Figure 14
IPSP
ExampleofpointtopointIPconnection
IP
IPSP
IPSP
IPServerPoint
WhenanIPconnectionoverEthernetisused,thenetworkelementmusthaveanIP
networkinterfaceunitwithEthernetports.TheIPnetworkinterfaceunitisusedasanIP
gateway.Insidethenetworkelement,internalIPoverATMconnectionisused.
IntheIPnetwork,M3UAsignalingisimplementedaspoint-to-pointsignaling.TheM3UA
specificationdoesnotdescribetheM3UAlevelSTPfunctionality;however,theSTP
functionalityisimplementedintheDX200andIPA2800-basednetworkelements
accordingtotheITU-T Q704 recommendations.
24
DN0628311
Issue:04C
BasicstructuresofSS7signalingoverIPnetwork
SS7messageroutingcanalsobebasedonanSCCPGT(GlobalTitle)address.Ifthe
GTisusedforrouting,therecanalsobeanSCCP-levelSTPinsidetheIPnetwork.The
SGroutesmessagestotheSTPpoint,whichisanASfromtheSG'spointofview.Inthat
node,theSCCPfindsoutthenextsignalingpointwherethemessagehastobesent.
ThemessageisthenpassedontothenextsignalingpointthroughIPSP-IPSPtype
M3UAconnection.
Issue:04C
DN0628311
25
4 Planning site configuration for signaling

ThissectiondescribeshowtoplanthesiteconfigurationforsignalingwithIPsolutions:
IPoverATM(IPoA)andIPoverEthernet(IPoE).TheIPoAinterfacesareconfiguredfor
NPS1unitsandtheIPoEinterfacesforNPGE(P)units.
WerecommendthatthesameDiffServisusedforallSCTPassociationsinthe
associationsetintheM3UA.ThesettingsoftheDiffServcodeusedforM3UAsignaling
arecommontoallthoseapplicationswhosetrafficgoesviathesameSCTPassociation.
Themaximumdelaythatisallowedbetweenthenetworkelementsisnotspecified.See
Q706ITU-Trecommendationforreference.AnapplicationoftheM3UAsetsreallimits.
TheM3UAdoesnotcontainforexamplesignalinglinkswitchoverwithinasignalinglink
set,andthereforeitcannotachievethesameservicelevelasMTP3inmessage
transport.PacketlossmayhappenintheM3UAasonMTPlevel3.
InIPoEcases,theLANinfrastructure,suchasthepoint-to-pointcapacityoftheLAN,
shouldbeknownwhenplanningthesiteconfiguration.ModifiableSCTPparametersare
necessaryfortheassociationstofunctionaccordingtotheQ706ITU-Trecommendation.
YoucanplantheredundancyeitherbyusingSCTPmulti-homingorbyusing2N
redundantNPGEPunits.Redundancyofassociationscanbehandledonseverallevels:
onthenetworkelementlevel:IfsignalingunitsareconfiguredwithlogicalIP
addresses(whichishighlyrecommended),itispossibletodoasignalingunit
switchoverproceduresothatthecurrentM3UAconfigurationisrecovered.
ontheunitlevel.
Before you start

IfIPoAsolutionisused,configureATMresourcesforit.SeeCreating ATM resources in
RNC.
InadditiontotheMMLbasedconfigurationtheIPoAinterfacecanbeconfigured
viatheIPplaninterfacefromtheNetAct.TheIPplansupportcoversthebasic
supportfortheMMLcommandsQMF,QRNandQKCanddoesnotcontainthe
OSPFconfiguration.Forfurtherdetails,refertodocument
WCDMA RAN Mass Operations.
Takethefollowingpointsintoconsiderationwhenplanningsiteconfigurationfor
signaling:
1. UselogicalIPaddresses.
ThisenablesmakingaunitswitchoversothatIPaddressesremainthesame.
2. UselogicalstaticIProutes.
ThishelpstomakeastaticIProuteconfigurationandensurethataftertheunit
switchover,signalingconnectionworksasbeforetheunitswitchover.
SCTPmulti-homingconfigurationisrequiredtoconfiguretwoIPsubnetworkstoeachsignalingunit.Forthisreason,thenumberofIProutes
increasesrapidlyineachpeer.GoodIPaddressingandgoodIPnetwork
designarekeyissuestoavoidsuchasituation.
3. Usemulti-homedconnectionsforsignalingoverIP,ifpossible.
26
DN0628311
Issue:04C
Inthiscase,IFGE0andIFGE1(forIPoE)orAA0andAA1(forIPoA)shouldbelong
todifferentsub-networks.Thiskindofconfigurationensuresthattheprimarypathis
separatedfromthesecondarypath.
4. Point-to-pointmessagetravellingtimeshouldbeexplored.
Ifthefailuredetectiontimehasbeenplanned,itisimportanttoreduceittothesame
levelasthatoftheSS7networkbytuningtheSCTPparameters.
Steps for planning the site configuration for IP over ATM interfaces
ThisproceduredescribeshowtoconfigureIPoAinterfacesonNPS1units.
1. PlantheIPoAinterfacesforSCTPmulti-homing.
AA0andAA1shouldbelongtodifferentsub-networks.SCTPmulti-homingenables
betterredundancyandthereforeitistherecommendedredundancymodefor
signaling.Werecommendthatyouuseasymmetricconfigurationinthecaseof
SCTPmulti-homing.FormoreinformationonSCTPconfigurations,seeSCTPmultihoming.
2. TunetheSCTPparameters.
BytuningtheSCTPparameters,afailuredetectiontimeofassociationcanbe
reducedtothesamelevelasthatoftheSS7networkrequired.Formoreinformation
onSCTPparameters,seeModifyingSCTPassociationlevelparameters.
3. PlanIPaddressesmanagementandconfiguration.
UselogicalIPaddresses.
Forfurtherinformation,seeConfiguring IP Connections for RNC.
Inthefollowingexample,twoIPoAinterfacesarecreatedtothesameICSU.
Inthisway,SCTPmulti-homingwithtwodifferentIPnetworkscanbe
supported.
Example:Creating two IP over ATM interfaces to the same ICSU
a) ConfiguretwoIPoAinterfaces(AA0andAA1)overtheVCLtpcreatedduring
configuringATMresources.(QMF)
Signalingunitmustbeinanactivestate(thatis,inWO-EXstate)before
configuration.
ZQMF:ICSU,0,L:AA0:2,20,30:1,IPOAM;
ZQMF:ICSU,0,L:AA1:2,20,31:1,IPOAM;
b) AssignIPaddressestobothATMinterfacesconfiguredinthepreviousstep.
(QRN)
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)
Whenthedestinationaddress(OYA)associatedwithsignalingpointis
justthedestinationaddress(QRN)ofIPoAconnection,itisunnecessary
tocreatestaticroutes.
ZQKC:ICSU,0:10.2.3.0,:1.2.3.1:LOG:;
ZQKC:ICSU,0:20.2.3.0,:2.2.3.1:LOG:;
Issue:04C
DN0628311
27
Steps for planning the site configuration for IP over Ethernet

interfaces
ThisproceduredescribeshowtoconfigureIPoEinterfacesonNPGE(P)units.Ifthe
systemistobeusedforthefirsttime,createtheIPconfigurationsbeforecreatingSCTP
associations.AfteryoucreatealogicalIPaddressinasignalingunit,theunitstatusis
automaticallychangedfromSP-EXtoWO-EX.
OneNPGEPunitpairsupports2NredundantEthernetports.TheusedEthernet
portshavethesamelogicalIPaddressbutonlyoneofthemisinactivestate.
ThisisdifferentfromtheSCTPmulti-homingconfiguration,wherebothEthernet
portsusedhavetheirownIPaddressesfromdifferentIPsubnetworks,sothat
bothEthernetinterfacesareactivesimultaneously.
TheM3UAimplementationsupportstheDSCPfeature.Theapplicationreadsa
parameterfromthefile(S3BARA)thattellstheDiffServcodepointusedforsignaling,
suchasRANAP,RNSAP.TheparameterisdefinedinSCTPparameterset,anditwillbe
commontoallsignalingapplicationswhichareusingthesameparametersetinthe
networkelement.
1. a)PlantheredundancyusingSCTPmulti-homing.
Ethernetport0andEthernetport1shouldbelongtodifferentsubnetworks.Theycan
betwodifferentEthernetportsofoneNPGE(P)unit,ortwoNPGE(P)units.The
recommendedoptionistousetwoNPGE(P)units.IfoneNPGE(P)unitisused,two
internalIPoAinterfacesareneededbetweenthesignalingunitandtheNPGE(P)
unit.Otherwise,oneinternalIPoAinterfaceforeachNPGE(P)isneeded.
SCTPmulti-homingenablesbetterredundancyandthereforeitistherecommended
redundancymodeforsignaling.Werecommendthatyouuseasymmetric
configurationinthecaseofSCTPmulti-homing.FormoreinformationonSCTP
configurations,seeSCTPmulti-homing.
OR
b)Plantheredundancyusing2NredundantNPGEP.
2NredundantNPGEPunitsbringredundancytoallEthernettrafficandcanbeused
togetherwithSCTPmulti-homing.However,using2NredundantNPGEPunitsis
moreimportantwhenSCTPmulti-homingcannotbeused.
WhenconfiguringalogicalIPaddress,twoEthernetportswiththesamenameofthe
NPGEPpairgetthesamelogicalIPaddress.IftheEthernetport(forexample,
IFGE0)oftheworkingunitfails,theEthernetportofthespareunitcantakethe
responsibilityforthefailedone,andtheSCTPassociationscancontinueworking
normally.
2. TunetheSCTPparameters.
BytuningtheSCTPparameters,afailuredetectiontimeofassociationcouldbe
reducedtothesamelevelasthatoftheSS7networkrequired.Formoreinformation
onSCTPparameters,seeModifyingSCTPassociationlevelparameters
3. PlanIPaddressesmanagementandconfiguration.
LogicalIPaddressesshouldbeusedifpossible.
IPaddressesareneededfortheEthernetportsofNPGE(P)andfortheinternalIPoA
interfacesoftheselectedsignalingunitandtheNPGE(P).TheIPaddressforthe
internalIPoAinterfaceofNPGE(P)isusedasagatewayaddress.Theinterfacetype
oftheinternalIPoAhastobeNUMBERED.
4. CreatestaticIProutes(QKC).
UselogicalIProuteconfiguration.
ConfigurationsareneededbothinthesignalingunitandintheNPGE(P).
28
DN0628311
Issue:04C
5. ConfiguretheLAN.
ConfigurethelowerlevelLAN.
Formoreinformation,seeConfiguring IP Connections for RNC.
6. ConfigureDSCPvalueforRANAPsignalingorRNSAPsignaling.
ConfiguretheIPinterfaceQoSforIuControlPlanetraffic(RANAP)orIurControl
Planetraffic(RNSAP).
Example:Configuring symmetric SCTP multi-homing
ThefollowingexampleshowshowtoconfigureICSU-0toconnecttoSGSNwithmultihomingIPoEinterface,goingthroughNPGEP-0andNPGEP-2.
TheIPaddressesforICSU-0are10.20.1.1and10.20.2.1.Theyareusedlaterasthe
SCTPprimarysourceIPaddressandthesecondarysourceIPaddress.
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,createthefollowingtwoIPoA
interfaceswiththecommandZQMC:
AA5 <-> IFAI5 of NPGEP-0
AA6 <-> IFAI6 of NPGEP-2
ZQMC: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;
Issue:04C
DN0628311
29
Example:Configuring DSCP value for RANAP signaling or RNSAP signaling

ThefollowingexampleistoconfiguretheDSCPvalue30intheSCTPparameterset
whichisusedbytheRANAP/RNSAPsignaling.
1. ConfigureDSCPvalueforRANAPsignalingorRNSAPsignaling.
ZOYT:<param-set-name>:DSCP=30;
2. CheckDSCPvalueforRANAPsignalingorRNSAPsignaling.
ZOYO:NAME=<param-set-name>;
30
DN0628311
Issue:04C
PlanningM3UAnetwork
5 Planning M3UA network

Before you start
CheckthattheassociationsetandSCTPassociationparametersyouplantouseare
compatiblewiththeotherend.Formoreinformation,refertosectionsModifying
associationsetlevelparametersofM3UAandModifyingSCTPassociationlevel
parameters.
ForinformationaboutM3UAlinks,see
WCDMA RAN: Access Network (RNC and Transport)
Steps
1. Plantheredundancyofconnections.
SpreadM3UAassociationstoasmanysignalingunitsaspossible,consideringthe
numberofunitsinbothendsoftheassociationset.Rememberthat4-bitSignaling
LinkSelection(SLS)isusedforloadsharingbetweenassociations,andthatthe
numberofassociationsinanassociationsetshouldbe2,4,8,or16;otherwise,the
loadineachassociationisnotevenandtheunitloadwillnotbeeveneither.Ifan
associationsetcontainsmorethanoneSCTPassociation,eachassociationcantake
careoftheothers'trafficifsomeofthemfail.
TherecommendednumberofSGsistwo.Formoreinformation,refertosectionMTP
levelsignalingnetworkintheConfiguring Signaling Connections in ATM Network
(RNC)document.
2. Planwhatkindofaconnectionisused.
YoushoulddeterminewhetheryouareusinganASP-SGPoranIPSP-IPSP
connection.Formoreinformation,refertoUseofM3UAstack.
3. PlanifSignalingPointManagementClusterisusedornot.
SPMCcanbeusedifforsomereasonitisnotpossibletogiveseparateSPC
addressestotheSGandthenetworkelementfunctioningasanASP.SPMC
configurationcanalsobeusedwhendifferentM3UAconfigurationsneedtobeused
together.SPMCisaspecialconfiguration,throughwhichitisnotpossibletodirect
trafficdestinedtoanotherDPC(STPtraffic),butitiscapableofreceivingand
handlingthesignalingtrafficdestinedtotheSPMC.
Figure15:ExampleofsignalinglinksrelatedtoSPMCshowsanexampleofthe
signalinglinksrelatedtoSPMC.
Issue:04C
DN0628311
31
PlanningM3UAnetwork
Figure 15
ExampleofsignalinglinksrelatedtoSPMC
MSC
Server
M3UA
association
MGW
LinkSLC=0
M3UA
association
Signalinglink
LinkSLC=8
SP A
RNC/BSC/PSTN
Onelinkset
LinkSLC=7
MGW
LinkSLC=F
SPC A
Inthisconfigurationexample,thenormalSPMCiscreatedfirst,byconnectingthe
signalingpointcodesofSPAandMSS.Afterthat,theredundantSPMCiscreated
usingsignalinglinkconnections0-7betweenSPAandMGWAand8-FbetweenSP
AandMGWB.
4. Planthesignalingroutesetparameterscarefully.
ThebasicruleisthatwithsignalingroutesetbetweenMSSandMGWtheIETF
signalingrouteparametersetisusedincaseofanM3UAconnection.Allsignaling
routesetswhichareavailableviaMGWshallbeconfiguredsothatausedsignaling
routeparametersetisbasedonsomeoftheMTP3standards.Thatkindof
parametersetsareforexampleITU-TandANSIparametersets.This
recommendationshouldbefollowedalsowithsignalingroutesetswhichareleading
totheBSCorRNCviaMGW.
SignalingrouteparametersetforA-interface(parameterset1listedbyNNI
MMLcommand)shallbeusedonlywhensignalingroutesetleadsdirectlyto
anadjacentsignalingpoint.
5. PlantheSCCPlevelsignalingnetwork.Proceedwithplanningaccordingtosection
SCCPlevelsignalingnetworkintheConfiguring Signaling Connections in ATM
Network (RNC)document.
32
DN0628311
Issue:04C
CreatingM3UAconfiguration
6 Creating M3UA configuration

Purpose
RNCsupportsIP-basedIuandIurSS7signalingstack.SS7overIPsignalinglinkset
canbeconfiguredintheRNCusingeitherIPoA(IPoverATM)orIPoverEthernet.
Before you start

IfIPoverATMsolutionisused,dothefollowingfirstbeforeperformingthisprocedure:
ConfigureATMresources.Forinstructions,seeCreatingATMresourcesinRNC.
ForinformationonplanningsiteconfigurationforIPoverATM,seePlanningsite
configurationforsignaling.
ConfiguretheIP-basedsignalingtransportoverATMconnectionforRNCcontrol
plane.Forinstructions,seeConfiguringsignalingtransportoverIPoverATMfor
controlplane.
IfIPoverEthernetsolutionisused,dothefollowingfirstbeforeperformingthis
procedure:
CreatetheLANconfiguration.Formoreinformation,seePlanningsiteconfiguration
forsignaling.
ConfiguretheIP-basedsignalingtransportoverEthernetforRNCcontrolplane.For
instructions,seeConfiguringsignalingtransportoverIPoverEthernetforcontrol
plane.
YoushouldalwaysusethelogicalIPaddressoftheunitandlogicalstaticroute
configurationwhenpossible.Otherwise,theremaybeproblemsafterunit
switchover.
Steps
1. Createownsignalingpoint,ifasignalingpointdoesnotexist.(NRP)
ZNRP:<signaling network>,<signaling point code>,<signaling
point name>,<own signaling point handling>:<ss7
standard>:<number of spc subfields>:<spc subfield lengths>;
2. Createanassociationset.(OYC)
OYC:<association set name>:<role>: [SCTP USER | M3UA def];
Remembertocheckiftheassociationsetparametersarecorrect.Formore
information,refertosectionModifying association set level parameters of M3UA.
3. Addassociationstotheassociationset.(OYA)
OYA:<association set name>:<unit type>,<unit index>:<parameter
set name>: [prio | NORMAL def];
Bydefault,thenumberofstreamintheM3UAassociationis16.Itshouldbe
notedthatiftheotherpeercannotsupportasmanyinboundstreamsasthe
clienthasassignedanoutboundstream,thenSCTPprotocolestablishesan
associationbyusinglowervalueofnumberofstream.Thisshouldbetaken
intoaccountwhenconsideringtheresourcesoftheclient.
4. ConfiguretransportaddressesofSCTPassociation.(OYP)
Issue:04C
DN0628311
33
OYP: <SCTP user>: <association set name>, <association

index>:<source address 1>, [source address 2], [source port]:
<primary destination address>, [netmask/prefix], [secondary
destination address], [netmask/prefix], [destination port];
Inthisphase,definethesourceanddestinationportnumbersandsourceand
destinationIPaddressesfortheSCTPassociation.
OntheserversideifdifferentsourceIPaddressesareconfiguredfortwoserver
associationsresidinginthesamesignalingunit,youneedtoconfiguredifferent
sourceportsforthoseassociations.Payattentionthattherecannotbebothsinglehomedandmulti-homedassociationsconfiguredwiththesameportnumberinthe
samesignalingunitontheserverside.Forexample,sourceIPaddress10.20.1.1
withportnumber2905isconfiguredforasingle-homedassociationinoneserver
end,andsourceIPaddresses10.20.1.1and10.20.2.1withthesameportnumber
2905areconfiguredforamulti-homedassociationinthesamesignalingunitofthe
sameserverend,thenthefirstassociationcannotworkproperly.
ZOYNisnolongerusedinSCTPcreationfromRN4.0.Whetherunitspecific
sourceIPaddressexistornot,itdoesnotaffectsystemfunctionality.
5. SetandmodifySCTPassociationsetparametervalues.(OYM)
OYM: <association set name>: (NAME = <new association set
name> | ROLE = <association set role> | VERSION = <M3UA
specification version> | TRAFFIC = <traffic mode type> | ASP =
<ASP messages> | REG = <registration request> | SSNM = <SSNM
messages broadcasts to all ASPs> | NETWORK = <network
appearance> | IPSP = <sending of ASP messages in IPSP
connection> | ROUTING = <routing context> | FIRST = <first
data stream number> | PARAMSET = <parameter set> | TACK =
<acknowledgement timer for ASPSM and ASPTM> | HB = <M3UA hb
interval>);
6. Checktheassociations.(OYI)
OYI:[ [NAME=<association set name> | NBR=<association set
number>...] | <all> def]: [A | H | H def];
VerifythattheassociationswerecreatedcorrectlyandthattheyhavecorrectIP
addressesbyusingtheOYIcommand.
7. CreateIPtypeSS7signalinglinkandlinkset.(NSP)
NSP:<signaling network>, <signaling point code>, <signaling
link set name>: <signaling link number>: <association set
name>;
Inthisstep,createasignalinglinksettodestinationpoint.Anetworkindicatorvalue
andsignalingpointcodeaddressofdestinationpointaredefinedexplicitlywherethe
associationsetisconnected.
8. CreatetheSS7signalingrouteset.(NRC)
NRC:<signaling network>, <signaling point code>, <signaling
point name>, [<parameter set number> | 0 def], [<load sharing
status> | D def ], [<restriction status> | N def ]:
( [<signaling transfer point network> | <signaling network>
def ], [<signaling transfer point code> | <signaling point
code> def ], [<signaling transfer point name> | <signaling
point name> def ], <signaling route priority> )... ;
9. (Option)ActivatetheSCTPassociationsoftheassociationset.(OYS)
Thisstepisoptional.ItallowsnoeffectontheM3UAsignalinginteractionwhenyou
activatetheSCTPassociations.
34
DN0628311
Issue:04C
OYS:<SCTP user>:<SCTP association name>:<state>;

10. Activatethesignalingnetworkconfiguration.
Theactivationprocedureisthesameaswhenyoucreateanon-IPconnection.
WhenyouactivateanSS7signalinglink,thesystemautomaticallyattemptsto
activatealltheassociationsbelongingtotheassociationset.TheSS7signalinglink
isactiveifatleastoneassociationbelongingtoitsassociationsetisactive.To
interrogatethestatesoftheassociations,usetheOYIcommand.Formore
information,seeActivatingMTPconfigurationinConfiguring Signaling Connections
in ATM Network (RNC).
Further information
Example:CreatingIPconfigurationbetweenRNC(client)andMSS(server).
ThisisonlyoneexampleofM3UAusage.Theconfigurationexamplecanbe
appliedtoallenvironmentswhereM3UAisplannedtobeused.
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.
Issue:04C
DN0628311
35
Creating M3UA configuration between RNC and MSS for Iu-CS

interface
1. 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,<signaling link set point code>,<signaling link set
name>,<signaling link number>,:TOMSS10;
7. CreatetheSS7signalingroutesetwiththeNRCcommand.
ZNRC:NA0:<signaling point code>,<signaling route set name>:;
8. ActivatetheSCTPassociations.
ZOYS:M3UA:TOMSS10,0:ACT;
ZOYS:M3UA:TOMSS10,1:ACT;
9. Activatethesignalinglinks.
ZNLA:<signaling link number>;
ZNLC:<signaling link number>, ACT;
10. Activatethesignalingroutesets.
ZNVA:NA0,<signaling point code>:,;
ZNVC:NA0,<signaling point code>:,:ACT;
ForMSSconfiguration,refertoappropriateMSSdocumentation.
36
DN0628311
Issue:04C
ModifyingSIGTRANparameters
7 Modifying SIGTRAN parameters

ThissectiondescribeshowtomodifySIGTRANparameters.
7.1 Modifying association set level parameters of

M3UA
Association set level parameters
NAME
ASSOCIATIONSETNAME
Symbolicnameoftheassociationset.
ROLE
ASSOCIATIONSETROLE
Theroleoftheassociationset(SERVER/CLIENT).Ifthe
roleoftheassociationsetisClient,thentheownpeer
initializesallSCTPassociationsofthatassociationset.
ThisparameteralsocontrolsM3UAmanagement.Ifthe
roleisClient,theexchangestartsASPstate
managementproceduresandtheotherpeeronlysendsan
acknowledgementmessageinbothASPandIPSPcases.
VERSION
M3UASPECIFICATIONVERSION
UsedversionoftheM3UAspecification.Ifotherpeers
supportadifferentversionoftheM3UA,thentheversion
parametershouldbechangedtothesameversionasthat
oftheremotepeer.ThedefaultisM3UAversion1.0
(RFC).
Supportedversionsareasfollows:
5...M3UASPECIFICATIONVERSION05(DRAFT)
16...M3UASPECIFICATIONVERSION1.0(RFC)
Bydefault,Version1.0isused.Normally,thereisnoneedtomodifythis
parameterexceptinveryspecialcases.
TRAFFIC
TRAFFICMODE
Trafficmodeoftheassociationset.Twotypesoftraffic
modesaresupported:over-rideandloadsharing(default).
Thisparametercontrolshowtrafficisroutedbetween
SCTPassociationsintotheassociationset.
ASP
Issue:04C
ASPMESSAGES
DN0628311
37
TheparametercontrolsifASPmanagementmessages
(ASPTMandASPSM)areusedornotintheassociation
set.Bydefault,ASPmanagementmessagesareinuse
whentheversion1.0oftheM3UAisused.
TACK
ACKNOWLEDGEMENTTIMERFORASPSMAND
ASPTM
TheparameterdefinesthetimeM3UAwaitsforresponse
tothesentASPSMandASPTMmessage(forinstance,
ASPUPACKforthesentASPUP,orASPACACKforthe
sentASPAC)beforeresendingthemessage.
HB
M3UAHB.INTERVAL
TheparameterdefineshowlongtimeM3UAwaitsuntilit
sendsthenextM3UABEATafterreceivingBEATACKto
thepreviousBEAT.Value0meansthattheM3UAdoesnot
sendM3UAheartbeat.NotethatM3UAalwayssends
BEATACKasaresponsetoBEAT,independentofthis
parametervalue.
REG
REGISTRATIONREQUEST
Theparametercontrolsifdynamicroutingkeyregistration
isinuseornot.Bydefault,dynamicroutingkey
registrationisused.However,ifdynamicroutingkey
registrationisnotanoptioninthereceivingparty'sM3UA,
thisproceduremaybedenied.
SSNM
SSNMMESSAGESNEEDTOBEBROADCASTEDTO
ALLASPS
TheparametercontrolsthebroadcastoftheSSNM
messages.ThebroadcastoftheSSNMmessagestoall
activeASPsarenotusednormally.
Iftheremotepeer'simplementationdoesnotsupport
centralzedASPmanagementintheAS,theremaybea
needtobroadcasttheSSNMmessagestoeachactive
ASPs.ThisfeaturecanbeusedwithLoadsharingmode
only.
NETWORK
NETWORKAPPEARANCE
Networkappearancewhichisusedintheassociationset
inquestion.Thisisanoptionalparameter,andtherefore
notnecessarilysupportedinallM3UAimplementations.If
notsupported,NetworkAppearancecanberemovedfrom
SSNMmessageswiththeNNMcommand(Parameter
GroupD,parameterUSE_OF_M3UA_NW_APP).From
Datamessage,NetworkAppearancecanberemovedso
thatitsvalueismodifiedasamaximumone.
0-4294967294RangeofNetworkAppearanceparameter
value
38
DN0628311
Issue:04C
4294967295NetworkAppearanceisnotusedindata
message
IPSP
SENDINGOFASPMESSAGESINIPSPCONNECTION
TheparametercontrolsthesendingofASPmanagement
messagesintheIPSPmode.Whenthisparameterisset
on,theserveralsostartstheASPTMandASPSM
managementsequences.Inotherwords,thesystemworks
inasocalleddoubleendedIPSP-IPSPmode.
ROUTING
ROUTINGCONTEXT
TheparameteristhedefinedvalueoftheRoutingContext.
ThevalueoftheRoutingContextcanbeconfiguredonly
whentheregistrationrequestparameterisinactive.This
parameterneedstobemodifiedonlyincaseofstatic
configurationoriftheremotepeerdoesnotsupport
RoutingContextparameter.RoutingContextparameter
cangetthefollowingvalues:
0-4294967294RangeofRoutingContextparameter
value
4294967295RoutingContextisnotsupported
FIRST
FIRSTDATASTREAMNUMBER
Theparameterisdefinedasthenumberofthefirstdata
stream.Normally,thefirstdatastreamnumberis1.When
M3UAversion1.0isused,thefirstdatastreammustbe1.
Thefirstdatastreamnumberhastobemodifiedonlyif
remotepeersupportsanearlierM3UAdraftspecification.
Eachassociationsethasitsownparameters.Inmanycases,itisnotnecessaryto
changetheparameters.However,youmayneedtochangetheparametersiftheremote
peersupportsadifferentversionoftheM3UAspecificationortheremotepeerdoesnot
supportalltheoptionalM3UAfunctionalities.
TheassociationsetlevelparameterscanbemodifiedbyusingtheOYMcommand.Allof
thoseparametersarerelatedtotheM3UA.
Theaboveparameterscanbemodifiedonlywhentheassociationsetis
deactivated.Theassociationsetcanbedeactivatedbydeactivatingasignaling
linkwhichisusingthatassociationset.
Before you start

Steps
1. Checkwhethertheparametershavesuitablevalues.(OYI)
TheassociationsetparameterscanbeinterrogatedwiththeOYIcommand.
2. Ifyouneedtomodifytheparametervalues,deactivatethecorrespondingM3UAlink.
(NLC)
Issue:04C
DN0628311
39
TheNLIcommandshowsthelinkthatcorrespondstotheassociationset.TheNLC
commandbringsallassociationsofthesetdown.
3. Changetheparametervalues.(OYM)
Findoutthereasonwhyandwhichparametersneedtobechanged.Youcanchange
theparametervalueswiththeOYMcommand.
4. ActivatethecorrespondingM3UAlink.(NLC)
7.2 Modifying SCTP association level parameters

TheSCTPassociationlevelparametersarethefollowing.Theseparameterscontrolhow
theSCTPassociationisworking.
RTO.min
Thisparameterdefinestheminimumvalueof
retransmissiontime-out.
IfthemessageaverageRound-TripTime(RTT)isless
than70ms,thepredefinedparameterset(SS7)canbe
used.ThedefaultvalueoftheRTO.minparameteris150
msintheSS7parameterset.
t
RTO.max
WerecommendthatyouconfiguretheRTO.min
valueatleasttwicetheRTTvaluetoavoid
unnecessarymessageretransmissions.
Thisparameterdefinesthemaximumvalueof
retransmissiontime-out.TheSCTPincreasestheretransmissiontimesupervisionexponentiallyaftereach
retransmissionattempt.
ThedefaultvalueoftheRTO.maxparameteris200msin
thepredefinedSS7parameterset.
EachSCTPpathmaintainsitsownretransmissiontimer.Theretransmissiontimeris
determinedwithRTO.minvalue,RTO.maxvalue,andcalculatedRTOvalue.Ifthe
calculatedRTOvalueislessthantheRTO.minvalue,theRTO.minvalueischosenas
theretransmissiontimer.IfthecalculatedRTOvalueisgreaterthantheRTO.minvalue
andlessthantheRTO.maxvalue,thecalculatedRTOvalueischosenasthe
retransmissiontimer.IfthecalculatedRTOvalueisgreaterthantheRTO.maxvalue,the
RTO.maxvalueischosenastheretransmissiontimer.
Inaddition,theSCTPincreasestheretransmissiontimerexponentiallyaftereach
retransmissionattemptforeachpath.Thatis,theSCTPdoublestheretransmission
timerafterthepreviousretransmissionattempt.Ifthedoubledretransmissiontimeris
greaterthantheRTO.maxvalue,theRTO.maxvalueischosenastheretransmission
timer.Otherwise,thedoubledretransmissiontimerischosenastheretransmissiontimer.
RTO.initial
40
ThisparameterisusedasdefaultRTOvaluewhenan
SCTPpathisjustestablished.Onceanacknowledgement
packetisreceivedthroughthispath,theRTOvalueis
calculated.
DN0628311
Issue:04C
SACK period
Thisparameterindicatesamaximumdelaywhich
messagereceivershallwaitforanotherdatachunkuntilit
shallsendSACKmessageforanacknowledgementofa
receiveddatamessage.
ThedefaultvalueoftheSACKperiodis200ms.The
SACKperiodcanneverbemorethan500ms.
HB.Interval
Thisparameteristhebasicvalueoftheheartbeatinterval.
Theheartbeatintervalinreallifeisthesumofthefollowing
parameters:HB.intervalvalue,RTO.min,andthevalueof
smallrandomjitter.UsedHB.intervalvalueandthevalue
ofRTO.mincomefromtheparameterset,butthevalueof
jittercanvarybetweennetworksandnetworkelements.
Whentheparametervalueis0,theSCTPheartbeatisoff.
Path.Max.Retrans
Thisparameterdefinesthemaximumnumberof
unacknowledgedtransmissions(includingheartbeats)per
path.Whenthethresholdvalueisreached,thepathis
markedinactive.
Association.Max.Retran
s
Thisparameterdefinesthemaximumnumberof
unacknowledgedtransmissions(includingheartbeats)per
association.Whenthethresholdvalueisreached,the
associationismarkedaborted.
CHECKSUM
ThisparametercontrolswhichChecksummethodisused
inanassociation.
TheAdler-32ortheCRC32cmethodcanbeused,butthe
CRC32cchecksumisrecommended.CRC32cisusedby
default.
BUNDLING
Thisparametercontrolsiftheuserapplicationallowsor
doesnotallowmorethanonechunkwithintheSCTP
packet.Bundlingisusedbydefaultinthesystem.
EachusermessageoccupiesitsownDATAchunkif
bundlingisnotallowed.
DSCP
Evenifthebundlingoptionisnotseton,theSCTP
stackmightsendtheSCTPcontrolmessageand
datamessagewithinonedatagram.Retransmitted
messagesarealsoallowedtobesentwithinone
datagramevenifthebundlingoptionisnotseton.
ThisparameterdefinesthevalueofDiffServCodePointin
SCTPlevel.
Thevaluerangeisfrom0to63.
Issue:04C
DN0628311
41
AllpredefinedparametersetshavedefaultDSCP
value34inanewinstalledRNC.Butduringupgrade,
theoriginalparameterDSCP_FOR_SIGNALINGin
PRFILEwillbesettoallpredefinedparametersets
asdefaultDSCPvalue.
TheSCTPparametersshouldbeuniformatbothendsoftheSCTPassociation.The
systemincludestwopre-packagedSCTPparametergroups.Thefirstonecontainsthe
IETFcompliantparameters,andthesecondonecontainsapre-tunedparameterto
ensurethattheMTPperformancerequirementsofanSS7networkaremet.TheGeneral
andSatelliteparametergroupscontainsuggestedparameters.Table1:Summaryof
suggestedparametersetssummarizesthedifferencesbetweenpredefinedparameter
sets.
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
Assoc.Max.Retrans
10
CheckSum
CRC32
CRC32
CRC32
CRC32
Bundling
Yes
Yes
Yes
Yes
DSCP
34
34
34
34
Thepre-packagedparameterscannotbemodifiedwiththeOYTcommand.
TheIETFparametersetofferstheRFC2960compliantparametersfortheSCTPstack.
Thisparametersetisnotfeasiblefortelecomsignalingpurposes.Itismorefeasiblewith
dataorientedapplicationslikeWebbrowsers.
TheSS7parametersetofferspre-tunedparametersforconnectionsimilartoMTP3.This
parametersetisdesignedtomeethighperformancerequirementsoftheMSSSystem.It
canbeusedwithaconnectionbetweenNSNMSSandMGW.UsingSS7parameterset
isarequirementfortheWANenvironment.Forthisreason,thisparametersetisnotthe
bestchoiceinallcaseswhereatraditionalTDM-basedconnectionisreplacedwitha
signalingoverIPsystem.Itshouldberememberedthatthisparametersetshallbeused
inbothpeers.
42
DN0628311
Issue:04C
TheGeneralparametersetisdesignedforacasewhereNSNsystemisusedwitha
thirdpartysystem.
TheSatelliteparametersetisdesignedtotakeintoaccountadelaycausedbya
satellite.
Itshouldberememberedthatthepre-definedparametersetsareonlyoneexampleof
possiblecombinationsoftheSCTPparameters.Aparametersethelpstostartsignaling
transportoveranIPconfiguration.
ThevaluesofthePath.Max.RetransandAssociation.Max.Retransparameters
canbeconfiguredindependently,butcarelessconfigurationcanleadan
associationtothestatewhereallthedestinationaddressesofthepeerare
unreachable(socalleddormantstate),butthepeerstaysinareachablestate.
Toavoidthissituation,youshouldavoidsettingthevalueofthe
Association.Max.Retransparameterhigherthanthetotalsumofthevaluesof
Path.Max.Retransforallthedestinationaddressesofthepeer.
WhenthecapacityoftheLANiswell-knownandabetterperformanceof
recoveryisrequired,youcantunehowtheSCTPassociationshouldworkby
usingtheSCTPassociationlevelparameters.
TomodifytheSCTPassociationlevelparameters,followthestepsbelow.
Modifying SCTP association level parameters
Sincethevaluesofpredefinedparametersetscannotbemodified,createanew
parametersetifyouneedtouseuser-definedparametervalues.
1. Createanewparametersetbycopyinganexistingparameterset.(OYE)
Forexample,createthenewparametersetofTEST1bycopyingthepredefined
parametersetofIETF.
OYE:TEST1:IETF:;
2. Checkthevaluesoftheparameters.(OYO)
CurrentparametervaluescanbeinterrogatedwiththeOYOcommand.
3. Changethevaluesoftheparameters.(OYT)
Accordingtoyourrequirements,changethecurrentvaluesoftheparameterset
TEST1withthecommandOYT.
4. DeactivatethecorrespondingM3UAlink.(NLC)
TheNLIcommandshowsthelinkthatcorrespondstotheassociationset.TheNLC
commandbringsallassociationsofthesetdown.
5. Changetheparametersetofassociationset.(OYM)
SCTPparametersetofM3UAassociationsetcanbechangedwiththeOYM
command.
6. ActivatethecorrespondingM3UAlink.(NLC)
Issue:04C
DN0628311
43
ItisalsopossibletomodifySCTPparametersthatarealreadyinanactive
association.YoucanmodifytheparameterswiththeOYTcommand.Butin
ordertobringtheparameterchangeintoeffect,youneedtotakeoneofthe
followingactions:
DeactivatetheM3UAlinkwiththeNLCcommandandthenactivatethe
M3UAlinkagainwiththeNLCcommand.
DeactivateonebyoneeachSCTPassociationoftheassociationsetwith
theMMLcommandOYS,andactivateitagainwithOYScommand.Each
associationshouldbereactivated,butitisnotnecessarytodoitatthe
sametime.
ThedeactivationoftheM3UAlink(ZNLC:...:INA;)orSCTPassociation
(ZOYS:...:DOWN;)doesn'tcausetheclosingofthelisteningsocket(command
QRScanshowthelisteningIPaddressandport).Thelisteningsocketshouldbe
closedwhenthelastserverassociationwiththesamesourceportisremoved
withcommandOYR,orwhencommandOYPisgivenandtheoldsourceportof
thisassociationisnotusedbyotherserverassociationsinthesamesignaling
unit.
44
DN0628311
Issue:04C
DeletingIPsignalinglinks
8 Deleting IP signaling links

Purpose
ThissectiondescribeshowtodeleteM3UAsignalinglinks.
Before you start
RemovefirsttheSCCPandMTP3levels.Formoreinformation,seeRemovinganMTP
signalingpointinConfiguring Signaling Connections in ATM Network (RNC).
Delete the signaling link set. (NSD)

DeletethesignalinglinksetwiththeNSDcommand.
Remove the unused association set. (OYD)

OYD:<association set name>;
Issue:04C
DN0628311
45
SignalingtransportoverIPtroubleshooting
9 Signaling transport over IP troubleshooting

9.1 IP signaling link activation fails
TheprocedureforcheckingIPtypesignalinglinksisdifferentfromcheckingordinary
signalinglinks.FollowtheprocedureifyouhavenotbeenabletoactivatetheIP
signalinglinkyouhavecreated,andthesignalinglinkstaysinthestateUA-INS.
Steps
1. Checkthealarms(AHO).
a.CheckthefollowingalarmswiththeAHOcommand:1273,2069,3156,3159,and
3155.
b.Ifthereareanyalarms,followthealarminstructions.
2. Checkthestatesandparametersoftheassociationsets(OYI).
Formoreinformation,refertoModifyingassociationsetlevelparametersofM3UA.
a.CheckthestatesandparametersoftheassociationsetswiththeOYIcommand.
b.ChecktheSCTPlevelparameters.Checkingisespeciallyimportantincaseof
retransmissionandalsoiftheSCTPassociationgoesdown,butthereisnoLAN
failure.
3. Checkthesignalinglinkparametersetandtestingoflinks(NCI,NSI).
Youneedtocompletethissteponlyifthefarendofthelinkisanother
vendor'sproductoranyofthefollowingNSNproducts:SCP,SMSC,3GSGSN,orFlexiServer.
a.CheckthesignalinglinkparametersetwiththeNCIcommand.The
defaultvalueis0.
b.Changethevalueto7withtheNCLcommand.
c.CheckwiththeNSIcommandifthetestingofthelinksetisdenied.Ifitis
not,denyitwiththeNSTcommand.ThedefaulttestingoftheM3UAlinkset
isdenied.
4. CheckiftheIPaddressesofthelocalsignalingunitarecorrect(QRI/Q6I).
a.CheckiftheIPaddressesofthelocalsignalingunitarecorrecteitherwiththeQRI
(forIPv4)orQ6I(forIPv6)command.
b.ComparetheIPaddressestotheIPaddressesassignedtotheassociationsatthe
farend.
c.CheckinterfacerunningstatuswiththeQRScommand.
ForexampleQRS:<unit name>,<unit index>:INS,<interface name>;
d.CheckpossibleerrorcounterstoIPstackwiththeQRScommand.
ForexampleQRS:<unit>::PRO;
e.CheckpossibleerrorsfromthePOSIXkernellogwiththePKLcommand.
46
DN0628311
Issue:04C
Connectaserviceterminaltothecorrectcomputerunit.Addthe
POMOXIGXserviceterminalextension.Youcanuseforexampletheletter
P:
ZLP:P, POM
ZPKL
5. CheckifsourceIPaddressesoftheassociationarecorrect.
a.CheckthesourceIPaddresseswiththeOYIcommandincaseofM3UA
connectionproblem.
b.CheckthestaticIProuteconfigurationwiththeQKBcommand.
6. Checkifcorrectchecksumisused.
CheckingwhethercorrectchecksumisusedisespeciallyimportantwhentheDX
200-orIPA-basednetworkelementworksasaclientandaservercomesfroma
thirdparty.
CheckthepossibleSCTPbadchecksumcounterswiththeQRScommand.
7. ChecktheavailabilityofthepeerIPaddresswithPING(QRX/Q6X).
UsetheQRXcommandforIPv4ortheQ6XcommandforIPv6.
8. CheckIPoAchannelstatus.
CheckIPoAchannelstatuswiththeQMQcommand.
9. ChecktheLANcables.
ChecktheLANcablesandtheirconnections.
10. ChecktheIPnetworkconfiguration.
ChecktherouterconfigurationandthesitelevelLANswitchconfiguration.Pay
attentiontothefollowingpossiblesourcesoffailure:
MTUsize.Thedefaultvalueis1500bytes.Iftunnelledconnectionisused,tuning
theMTUsizemightbeneeded.
Bandwidthlimitorpacketratelimit.CheckfromcoreIProutersifsome
bandwidthlimitsareset.
CheckIPnetworksettingssuchasspeedandduplexmode(theseparameters
willbethesameinbothendsofthelink.BydefaultbetweenESBandDX200basednetworkelementuseauto-negotiationmode).
CheckSTP/RSTP/MSTPsettinginthelayer2network.
CheckpossiblebottlenecksintheIPbackbone.
Checkthatthesoftwareversionsofroutersandswitchesarecompliant.
11. MonitoringafailedconnectionwithanIPnetworkanalyzer.
GoodmonitoringtoolsareforexampleDPDUMPoranEthernetmonitoringtool.The
latterisfreewaresoftware.
9.2 SCTP association fails

ThisproceduredescribeshowtotroubleshootwhenSCTPassociationfails.
Steps
a.CheckthefollowingalarmswiththeAHOcommand:
Issue:04C
SCTP_association_lost(3159)
DN0628311
47
SCTP_path_failure(3379)
TheSCTPassociationmayalsofailbecauseallpathsfailfortheassociation.For
moreinstructions,seePathofSCTPassociationfails.
2. Checkthestateofassociationandassociationset.
3. CheckthestateofSCTPsockets(QRS).
ForexampleQRS:ICSU,3:ALL;
4. ChecktheSCTPerrorcountersandSCTPstatistics(QRS).
5. CheckthestaticIProuteconfiguration.
CheckthestaticIProuteconfigurationwiththeQKBcommand.
6. ChecktheavailabilityofthepeerIPaddresswithPING(QRX/Q6X).
ChecktherouterconfigurationandthesitelevelLANswitchconfiguration.Formore
information,refertosectionIPsignalinglinkactivationfails.
9.3 Path of SCTP association fails

ThisproceduredescribeshowtotroubleshootwhenpathofSCTPassociationfails.
Steps
a.CheckthefollowingalarmwiththeAHOcommand:SCTP_path_failure(3379).
2. Checkthestateofassociationorassociationset.
3. CheckthestateofSCTPsockets(QRS).
RNCallowsIPaddresschangeandMTUchangeonIPoAinterfacewhiletheIP
addressisstillusedbytheSCTPstack.Thismaycauseaninconsistencybetween
theSCTPandtheIPlayersleadingtoaninactiveSCTPconnection.
Example:
QRS:ICSU,0:ALL;
IfthestateofanIPaddressconfiguredintheSCTPassociationisinactive(ina),
andre-selecting src addrshowsintheLocal AddressfieldoftheSCTP
association,asindicatedintheexamplebelow,thereasonmightbeIPaddresses
configuredintheSCTPassociationhavebeenmodifiedordeleted.
UNIT: ICSU-0
Active Internet connections (including servers)
Proto Recv-Q Send-Q Local Address
Foreign Address
State
tcp
0
0 *.3452
*.*
LISTEN
udp
0
0 127.0.0.1.524
*.*
Active v4/v6 SCTP connections (including servers)
Proto Recv-Q Send-Q Local Address
Foreign Address
State
sctp
0
0 ----ESTABLISHED
48
DN0628311
Issue:04C
Local addr:
act,sec
10.1.1.7.33056
<re-selecting src addr>
ina,prim
Foreign addr:
act,sec
10.1.1.4.2905
10.1.1.2.2905
ina,prim
sctp6
LISTEN
sctp
LISTEN
*.2905
*.*
10.1.1.7.2905
*.*
FollowingistheinstructonforcorrectingIPaddressconfigration:
Forsingle-homedassociations,reconfiguretheIPaddress(QRN)
IfmultihomedassociationswithbothIPaddressesinactive,configurebothIP
addresses(QRN)
IfmultihomedassociationswithonlyoneIPaddressinactive:
a) DeletetheactiveIPconfiguration(QRG)
b) ReconfigureIPaddresses(QRN)
Withmulti-homingconfiguration,oneSCTPassociationconsistsoftwo
preconfiguredpaths:primarypathandsecondarypath.Bydefault,data
trafficgoesthroughtheprimarypath.Whentheprimarypathisunavailable,
thedatatrafficisswitchedtosecondarypathautomatically,andthe
secondarypathstaysassecondaryinsystem.However,iftheSCTP
associationrestartsupandtheprimarypathisstillunavailable,the
secondarypathwillbeidentifiedasprimarytemporarilyinsystem.Later
on,ifthepreconfiguredprimarypathisavailableagain,thedatatrafficwill
beswitchedback,andthepreconfiguredprimarypathresumesitsprimary
state.
4. ChecktheSCTPerrorcountersandSCTPstatistics(QRS).
5. CheckthestaticIProuteconfiguration.
CheckthestaticIProuteconfigurationwiththeQKBcommand.
6. ChecktheavailabilityofthepeerIPaddressviafailedpathwithPING(QRX/Q6X).
Checktherouterconfigurationandthesite-levelLANswitchconfiguration.Make
surethatthereisnoESA/ESB/Ciscomisconfiguration,suchasduplexmismatchor
RSTP/MSTPusedwithoutedgeportsettingstowardsthesignalingunit.Youcan
checktheswitchconfigurationfromtheESA/ESBwiththefollowingcommands:
show ver
show running-config
show interface
show interface statistics
Youcanchecktherouter(Cisco)configurationwiththefollowingcommands:
show ver
show running-config
show interfaces status
Issue:04C
DN0628311
49
show interfaces counters errors

Formoreinformation,refertosectionIPsignalinglinkactivationfails.
9. ChecktheusedSCTPparametersinbothpeers.
a.CheckthevalueoftheSCTPparameterswithOYOcommand.
b.IftheSCTPparametersaredifferentbetweenpeers,thevalueoftheSCTP
parametersshouldbeharmonizedinbothends.
10. ChecktheSCTPconnectionsforspecialimplementations.
Followingaretheinstructionsforcross-connectionsintwospecialimplementations.
a) Thisinstructionisusedforcheckingwhethercross-connectionshappenedwhen
localIP-baseddefaultGW(gateway)isused.Youcanchecktheroutingtypeby
commandQKB.
Forexample,oneSCTPassociationisconfiguredasfollows:
RNC(c) MGW(s) remark
------------------------A
a
Primary
B
b
Secondary
LocalIP-baseddefaultGWisconfiguredforbothsourceIPAandB.
WhenconnectingIPaddressa,AwillbeselectedassourceIPaddress.IfINITACKisnotreceived,BwillbeselectedassourceIPaddress,cross-connections
mighthappenlikefollows:
------------------------B
a
Primary
A
b
Secondary
Recovery procedures
1. SettheassociationDown(OYS)
2. SettheassociationActive(OYS)
3. Checkthestateofassociation(QRS)
Ifthecross-connectionsstilloccurs,restorethetrafficbyfollowingsteps:
1.
2.
3.
4.
5.
SettheassociationDown(OYS)
Deletetherouteforsecondarypath(QKA)
SettheassociationActive(OYS)
Checkthestateofassociation(QRS)
Recreatetherouteforsecondarypath(QKC)
b) Thisinstructionisusedforcheckingwhethercross-connectionshappenedwhen
staticroutingisusedandbothprimarypathandsecondarypathuseloopbackIP.
Forexample,oneSCTPassociationisconfiguredasfollows:
------------------------A
a
Primary
B
b
Secondary
Whencheckingstateofassociation,cross-connectionsmighthappenlike
follows:
50

------------------------B
a
Primary
A
b
Secondary
DN0628311
Issue:04C

------------------------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 case

BeforecontactingNSNfortechnicalsupport,findthefollowinginformationtohelpfind
outtherootcauses:
1.
2.
3.
4.
5.
6.
Issue:04C
IPconfiguration(QRI)
StaticIProuteconfiguration(QKB)
SCTPassociationforM3UA(OYI)
SCTPparameters(OYO)
SCTPerrorcounters(QRSwithALLandPRO)
DBDUMPmonitoringorothermonitoringfromtheESBswitchesifpossible.
DN0628311
51

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

Încărcat de

Informații document

Descriere originală:

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

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

Încărcat de

Drepturi de autor:

Formate disponibile

WCDMA RAN, Rel.

Important Notice on Product Safety

Changes between Issues 04 (2013-04-15, RU40) and 04A (2013-07-25,

1 Signaling transport over IP (M3UA)

1.1.1 SCTP multi-homing

1.1.2 SCTP stream

1.2 Association set

1.3 SGP - ASP communication

1.4 IPSP-IPSP communication

1.5 Signaling over IP statistics

M3UA association set counters:

M3UA association counters:

SCTP counters used by M3UA:

2 Use of M3UA stack

2.1 SGP-ASP communication

2.1.1 Example of M3UA usage

2.2 IPSP-IPSP communication

2.2.1 Use of IPSP-IPSP example at the M3UA

2.3 Routing key and routing context

2.4 Signaling Point Management Cluster

2.5 Message structure of M3UA

Payload Protocol Identifier

protocol dataoftheM3UA users (VariableLength)

3 Basic structures of SS7 signaling over IP

4 Planning site configuration for signaling

Before you start

Steps for planning the site configuration for IP over Ethernet

Example:Configuring DSCP value for RANAP signaling or RNSAP signaling

5 Planning M3UA network

6 Creating M3UA configuration

Before you start

OYP: <SCTP user>: <association set name>, <association

OYS:<SCTP user>:<SCTP association name>:<state>;

Creating M3UA configuration between RNC and MSS for Iu-CS

7 Modifying SIGTRAN parameters

7.1 Modifying association set level parameters of

Before you start

7.2 Modifying SCTP association level parameters

Modifying SCTP association level parameters

8 Deleting IP signaling links

Delete the signaling link set. (NSD)

Remove the unused association set. (OYD)

9 Signaling transport over IP troubleshooting

9.2 SCTP association fails

9.3 Path of SCTP association fails

show interfaces counters errors

RNC(c) MGW(s) remark

RNC(c) MGW(s) remark

9.4 List of debugging commands in a failure case

S-ar putea să vă placă și

protocol dataoftheM3UA users (VariableLength)