Blade Cluster

R14.1 Operation & ConfigurationCustomized Course

Mohammad BahgatMohammad BahgatDecember-2011

PREFACE

Blade Cluster R14.1 Operation & Configuration

Mohammad Bahgat

2

AGENDA

1. What is Blade Cluster

2. Blade Cluster Architecture2. Blade Cluster Architecture

3. Blade Cluster Concepts

4. Traffic Cases4. Traffic Cases

5. Signaling from Blade Cluster Point of View

6. Blade Cluster Configuration Quick View6. Blade Cluster Configuration Quick View


Mohammad Bahgat

3

AGENDA








Mohammad Bahgat

4

What is Blade ClusterPreface


Mohammad Bahgat

5

What is Blade ClusterBlade History

A blade server is a stripped down server computer with a modular design optimized to minimize the use of physical space and energy. Whereas a standard rack-mount server minimize the use of physical space and energy. Whereas a standard rack-mount server can function with (at least) a power cord and network cable, blade servers have many components removed to save spaceDevelopers first placed complete microcomputers on cards and packaged them in Developers first placed complete microcomputers on cards and packaged them in standard 19-inch racks in the 1970s The first commercialized blade server architecture was invented by Christopher Hippand David Kirkeby was assigned to Houston-based RLX Technologies that shipped its first commercial blade server in 2001 and was acquired by Hewlett Packard (HP) in 2005first commercial blade server in 2001 and was acquired by Hewlett Packard (HP) in 2005 The name blade server appeared when a card included the processor, memory, I/O and non-volatile program storage. This allowed manufacturers to package a complete server, with its operating system and applications, on a single card / board / blade. These server, with its operating system and applications, on a single card / board / blade. These blades could then operate independently within a common chassis, doing the work of multiple separate server boxes more efficiently


Mohammad Bahgat

6

What is Blade ClusterBlade Cluster Definition

The MSC-S Blade Cluster, the future-proof server part of Ericssons Mobile Soft- The MSC-S Blade Cluster, the future-proof server part of Ericssons Mobile Soft-

switch solution, provides very high capacity, effortless scalability, and outstanding

system availability. It also means lower OPEX per subscriber, and sets the stage for

business-efficient network solutionsbusiness-efficient network solutions

3 Blades in MSC R14.1 Compared to MSC R13.2 have a capacity of 43% gain


Mohammad Bahgat

7

What is Blade ClusterBlade Cluster Benefits

Ultra High CapacityUp to 11 Million subscribersUp to 11 Million subscribers

Outstanding Node AvailabilityZero down time on node level; and enabling SW upgrade of single blade without traffic Zero down time on node level; and enabling SW upgrade of single blade without traffic disturbance

Easy ScalabilityBlades could be added & removed without updating the configuration of neither radio nor Blades could be added & removed without updating the configuration of neither radio nor core network

A future proof solutionMSC-S Blade Cluster is enabling SIP interworking (IMS)

Dump Cloning on MSC BladesData across blades are the same, this allows for manual cloning a dump from blade to another


Mohammad Bahgat

8

Data across blades are the same, this allows for manual cloning a dump from blade to another

What is Blade ClusterBlade Cluster Benefits


Mohammad Bahgat

9

AGENDA








Mohammad Bahgat

10

Blade Cluster ArchitectureBlade Cluster Components


Mohammad Bahgat

11


MSC Blades: Provide MSC/VLR/SSF & GMSC application functions.MSC Blades: Provide MSC/VLR/SSF & GMSC application functions.Subscribers are distributed among the available MSC-Blades. The blades maintainsubscriber registrations and control the mobile radio access. MSC-Blades arelogically connected to other network nodes (MGW, MSC, HLR, FNR, SCP, RNC,logically connected to other network nodes (MGW, MSC, HLR, FNR, SCP, RNC,BSC). Inter-Blade communication is done via Ethernet.

SPXes : To hide the internal structure of the Blade Cluster. Also provides SPXes : To hide the internal structure of the Blade Cluster. Also providessignaling support functions (Routing, Load-sharing and interworking of differentprotocols) , it also acts as an entry point for incoming traffic & exit point for outgoingtraffic

APG: 2 APG43s are provided [1 for charging&1 for APGs functionality I/OFunctions & Statistics]


Mohammad Bahgat

12


Integrated Site (IS): A solution for building compact IP based sites, its components Integrated Site (IS): A solution for building compact IP based sites, its componentsused for implementing intra MSC-BC connectivity and provide IP connectivity toexternal nodes, MSC-BC doesnt use AXE dedicated hardware for IP, it composed of:

vMXB: Main IS Switch, control shelf => SCP-RP

v EXB: Used to connect Attached System Like SPX => DLEBv EXB: Used to connect Attached System Like SPX => DLEB

v IPLB: Used to route IP signaling as a physical interface to IP network

v SIS: Site Infrastructure Support general I/O system for IS, also acts as O&Mv SIS: Site Infrastructure Support general I/O system for IS, also acts as O&Mfor IS & boot functions (You cant add a new board unless its up)


Mohammad Bahgat

13

Blade Cluster ArchitectureBlade Cluster Connectivity


Mohammad Bahgat

14

Blade Cluster ArchitectureBlade Cluster System Cabinets Whole System


Mohammad Bahgat

15

Blade Cluster ArchitectureBlade Cluster System Boards

SPX SPXvAPZqAPZ 212 55 used in MSC-S R13.1 BC onlyqAPZ 212 60 & APG43qAPZ 212 60 & APG43q SCB-RP Support & Connection Board RP (Ethernet Switching, Power,RP Bus, Shelf Manager)qGARP Generic Application Resource Processor (For NTP)qGARP Generic Application Resource Processor (For NTP)

vAPTqALI ATM Link Interfaceq ET155 Exchange Terminal 155 Mbit/s for TDM interfaceq STEB Signaling Terminal Enhanced Boardq STEB Signaling Terminal Enhanced BoardqXDB Switch Distributed Board acting as Group Switchq IRB Incoming Reference Board for incoming synchronization referenceqCGB Clock Generation Board for stable clocks


Mohammad Bahgat

16

qCGB Clock Generation Board for stable clocks


I/OI/OvAPG43

BladesvAPZ 214 03 GEP2 Generic Ericsson ProcessorvAPZ 214 03 GEP2 Generic Ericsson Processor

ISvMXB-BS Main Switch Blade System (Ethernet switching, Power, ShelfManager, IPMB); it contains two boardsManager, IPMB); it contains two boardsq SCXB Main Switch Board, 2 SCXB boards required for each IS subrack,it provides 1 GE connectivity to all slot positions, in IS-1; 2 CMCB boardsfound while no need for them in IS-2, SCXB with CMCB provides 10 GEqCMCB Optional extension board to provide 10 GE connectivity toqCMCB Optional extension board to provide 10 GE connectivity toBackplane


Mohammad Bahgat

17


ISISv IPLB-BS IP Line Board, IPLB blade system provides signaling trafficconnectivity and routing, it acts as the host interface for load-balancerfunctionality, IPLB behaves as an IP Host or IP forwarding engine, BC systemfunctionality, IPLB behaves as an IP Host or IP forwarding engine, BC systemrequires one IPLB pair blades, one port of IPLB used for 1 GE connectivity to LAN

vEXB5 Extension Switch Board (Ethernet switch with external interfaces forvEXB5 Extension Switch Board (Ethernet switch with external interfaces forconnecting non-IS equipment to IS infrastructure), used for AXE attached systemconnectivity, in other words; External LAN attachment blade system is used forextending the IS LAN connectivity to various externally attached LAN devices,providing these with well-defined, standards compliant data link layerproviding these with well-defined, standards compliant data link layerconnectivity, 2 boards included in IS-1


Mohammad Bahgat

18


ISISv SIS Site Infrastructure Support Board (OAM for IS), one SIS pair mandatoryper IS domain; there is one active SIS blade and one stand-by. The SIS bladesystem provides services like: Integrated Site Management (ISM), Faultsystem provides services like: Integrated Site Management (ISM), Faultmanagement, Interface for Locally Connected Terminal etc.


Mohammad Bahgat

19

Blade Cluster ArchitectureBlade Cluster System Cabinets - Cabinet 1


Mohammad Bahgat

20

Blade Cluster ArchitectureBlade Cluster System Cabinets - Cabinet 2


Mohammad Bahgat

21

Blade Cluster ArchitectureBlade Cluster System Terminologies


Mohammad Bahgat

22



Mohammad Bahgat

23



Mohammad Bahgat

24

Blade Cluster ArchitectureBlade Cluster Resiliency

Board Types Resiliency

SPX 2 * (1+1) Protection

MSC-Blades N+1 Protection

APG43 1+1 Protection (OAM & STS)

APG43 1+1 Protection (Charging)APG43 1+1 Protection (Charging)

IS 1+1 Protection


Mohammad Bahgat

25

AGENDA








Mohammad Bahgat

26

Blade Cluster ArchitectureBlade Cluster Concepts

Signaling ProXy Signaling ProXyA 1+1 protected AXE CP with RP equipment. It will hide cluster from externalnetwork & convert and route signaling traffic (ATM, TDM and IP based signaling)received from external network nodes to the appropriate blades. Acting as SGWreceived from external network nodes to the appropriate blades. Acting as SGWwhile Blades use IP only

Primary Blade Primary BladeOne from two MSC blades that can handle a certain mobile subscriber. One of theMSC blades is automatically selected as Primary MSC blade for each mobilesubscriber by the mobile subscriber distribution function. The Primary MSC bladeexecutes traffic for a mobile subscriber unless it experiences a transient failure orexecutes traffic for a mobile subscriber unless it experiences a transient failure ortraffic isolation


Mohammad Bahgat

27


Buddy BladeBuddy BladeOne from two MSC blades that can handle a certain mobile subscriber. One of theMSC blades is automatically selected as Buddy MSC blade for each mobilesubscriber by the mobile subscriber distribution function. The Buddy MSC blade is tosubscriber by the mobile subscriber distribution function. The Buddy MSC blade is tohandle new traffic for a subscriber during traffic isolation or a transient failure of thePrimary MSC blade of the same subscriber

Once the Buddy MSC blade has taken the control of a subscriber, it handles thissubscriber until the next location update is received or until it becomes unable toexecute traffic due to traffic isolation or due to a transient failure. At the occurrence ofone of these events, the Primary MSC blade will start to handle the subscriber again,one of these events, the Primary MSC blade will start to handle the subscriber again,unless the Primary MSC blade is not able to execute traffic


Mohammad Bahgat

28


Active bladeActive bladeThe Blade that is handling traffic of a certain mobile subscriber at a certain time. It is alogical role that is automatically assigned to a blade for each mobile subscriber by thedistribution function. Active blade of a subscriber is either the Primary or the Buddydistribution function. Active blade of a subscriber is either the Primary or the Buddyblade of that subscriber. The selection whether Primary or Buddy blade is the activeblade can change in the course of time and depends on the ability of the two blades toexecute traffic. There can be only one active blade per subscriber at the same timeexecute traffic. There can be only one active blade per subscriber at the same time

Passive bladeFrom the two blades that can execute traffic for a mobile subscriber (Primary andBuddy blade), a blade that is not the active blade is passive blade. By default a bladeBuddy blade), a blade that is not the active blade is passive blade. By default a bladebecomes a passive blade for all mobile subscribers that are already registered on thatblade during traffic isolation or a transient failure. Both ,Primary and Buddy bladecan be a passive blade at the same time


Mohammad Bahgat

29

can be a passive blade at the same time


VLR data replicationVLR data replicationThis is a function that makes the subscriber data of a mobile subscriber available inthe VLRs of the Primary and of Buddy blade. It achieves a consistency of the VLRdata between the two MSC blades. The master database in this case is the HLRdata between the two MSC blades. The master database in this case is the HLR

Permanent failureA permanent failure of a blade is a failure that cant be corrected by automaticA permanent failure of a blade is a failure that cant be corrected by automaticrecovery actions. A permanent failure of a blade always leads to clusterreconfiguration

Transient failure Transient failureA transient failure of a blade is a temporary situation. During this situation the bladeis not able to execute traffic due to automatic recovery actions


Mohammad Bahgat

30


Cluster HandlerCluster Handler

A new APZ platform function, which provides information about the blades in thecluster in a consistent manner. I.e. before the application is notified (on each blade)cluster in a consistent manner. I.e. before the application is notified (on each blade)about the available blades, the platform will perform checks concerning the bladeavailability and the communication paths. If the cluster handler detects changes inthe cluster (transient or permanent changes), it will notify the application notification.the cluster (transient or permanent changes), it will notify the application notification.It also offers functionality to traffic isolate a blade and to initiate capacity changes.The latter one can be triggered either by the operator or due to permanent failures


Mohammad Bahgat

31


Load-Vector Load-VectorA logical representation of the cluster configuration and the load distribution withinthe MSC Server Blade Cluster. It contains the information which blades areconfigured to handle traffic and how the load is distributed over the MSC blades. Theconfigured to handle traffic and how the load is distributed over the MSC blades. Theinformation of the load vectors is stored on all blades and it is used by the distributionfunction to determine the Primary and the Buddy blades of a mobile subscriber.Different load vectors are used for this task. The load vectors are calculated based onDifferent load vectors are used for this task. The load vectors are calculated based onthe information in the consistent cluster view

Cluster ReconfigurationThe automatic process of redistributing the registered mobile subscribers between theThe automatic process of redistributing the registered mobile subscribers between the

blades according to a new cluster configuration. It is always preceded by thecalculation of new load vectors. A cluster reconfiguration is initiated due to a clusterextension, a cluster reduction or a permanent failure of a blade


Mohammad Bahgat

32

extension, a cluster reduction or a permanent failure of a blade

Blade Cluster ArchitectureBlade Cluster Key Mechanisms


Mohammad Bahgat

33


Distribution & ReplicationDistribution & Replication


Mohammad Bahgat

34




Mohammad Bahgat

35




Mohammad Bahgat

36




Mohammad Bahgat

37




Mohammad Bahgat

38




Mohammad Bahgat

39


Cluster Circuit Sharing (CCS)Cluster Circuit Sharing (CCS)


Mohammad Bahgat

40




Mohammad Bahgat

41




Mohammad Bahgat

42


Cluster Circuit Sharing (CCS)Cluster Circuit Sharing (CCS)qCOASE


Mohammad Bahgat

43


Cluster Circuit Sharing (CCS)Cluster Circuit Sharing (CCS)qAge Rank

Assigned by Cluster Handler indicating the age of CP joining the quorum, thelongest time CP alive in quorum has the smallest Age Rank and is the CPlongest time CP alive in quorum has the smallest Age Rank and is the CPTraffic Leader that will further assigns the Master Role


Mohammad Bahgat

44


Cluster Circuit Sharing (CCS)Cluster Circuit Sharing (CCS)qAge Rank

Assigned by Cluster Handler indicating the age of CP joining the quorum, thelongest time CP alive in quorum has the smallest Age Rank and is the CPlongest time CP alive in quorum has the smallest Age Rank and is the CPTraffic Leader that will further assigns the Master Role


Mohammad Bahgat

45


Cluster Circuit Sharing (CCS)Cluster Circuit Sharing (CCS)q Traffic Leader & Route Master Role


Mohammad Bahgat

46




Mohammad Bahgat

47




Mohammad Bahgat

48




Mohammad Bahgat

49

Blade Cluster ArchitectureIP on CP Migration

Virtual Interfaces (VIFs)

oVirtual Interface is a logical representation of an interface that is used to sendor receive data for the connected network

oVIF connected to a VLAN

oIP addresses & routing tables can only be configured on VIFsoIP addresses & routing tables can only be configured on VIFs


Mohammad Bahgat

50


Virtual Interfaces (VIFs)oTypes of VIFsoTypes of VIFs

Dual Sided CP (SPXes) "Multi-Homing"

Supports two physical Ethernet interfaces (EthA, EthB); each interfaceconnected to a number representing VLAN to be used for this VIF "EthA-10connected to EthA & uses VLAN-10"connected to EthA & uses VLAN-10"

Both VIF that defined on two Ethernet interfaces called VIF-Pair, specificfunctions applied to VIF-Pair like "Router Supervision"


Mohammad Bahgat

51



Router Supervision Function available only for dual sided CP

Each VLAN could have one Router Supervision Instance that everyinstance has 2 router supervision IP addresses used to monitor IPconnectivity between interface and supervised gatewayconnectivity between interface and supervised gateway

Router Supervision IP addresses (PingA & PingB) always defined in pairs,one on each interface in a VIF-Pair


Mohammad Bahgat

52



Router Supervision Function available only for dual sided CP

Each VLAN could have one Router Supervision Instance that everyinstance has 2 router supervision IP addresses used to monitor IPconnectivity between interface and supervised gatewayconnectivity between interface and supervised gateway

Router Supervision IP addresses (PingA & PingB) always defined in pairs,one on each interface in a VIF-Pair


Mohammad Bahgat

53



Single Sided CP (Blades) Semi Multi-Homing in a Single-Homed View

Supports two physical Ethernet interfaces, will appear as a single interface(LAG) because of Ethernet Link AGgregationFor single sided VIF called; named VIF "nVIFFor single sided VIF called; named VIF "nVIFVIF is always connected to one Ethernet interfaceOn VIF; operator can define Application IP that belongs to one or moredefined IP subnets


Mohammad Bahgat

54



Single Sided CP (Blades) Semi Multi-Homing in a Single-Homed View

Supports two physical Ethernet interfaces, will appear as a single interface(LAG) because of Ethernet Link AGgregationFor single sided VIF called; named VIF "nVIFFor single sided VIF called; named VIF "nVIFVIF is always connected to one Ethernet interfaceOn VIF; operator can define Application IP that belongs to one or moredefined IP subnets


Mohammad Bahgat

55



For IP stack on CP; a specific Subnet belongs to exactly one VLAN

Link aggregation is a term which describes usage of multiple Ethernetnetwork cables/ports in parallel to increase the link speed beyond thelimits of any one single cable or portlimits of any one single cable or port


Mohammad Bahgat

56


Different Cases Uses IP on CPEthernet

Link Aggregation Group (LAG)


Mohammad Bahgat

57


Different Cases Uses IP on CP


Mohammad Bahgat

58




Mohammad Bahgat

59




Mohammad Bahgat

60




Mohammad Bahgat

61




Mohammad Bahgat

62




Mohammad Bahgat

63

AGENDA








Mohammad Bahgat

64

Traffic CasesLocation Update

1 2 6543

1- A# sends request to SPX for LU


Mohammad Bahgat

65


1 2 6543

2- SPX perform round robin technique to choose randomly a blade blade 2 chosen


Mohammad Bahgat

66

chosen


1 2 6543

3- Load vector calculated for A# based on [IMSI, CP Load, Cluster Area Identifier], primary blade 4 and blade 4 calculate load vector to choose buddy blade, blade 5 chosen


Mohammad Bahgat

67

Identifier], primary blade 4 and blade 4 calculate load vector to choose buddy blade, blade 5 chosen


1 2 6543

4- TID sent back to SPX where SPX forward it to HLR


Mohammad Bahgat

68


1 2 6543

5- HLR sends LU acknowledge back to SPX then back to primary blade


Mohammad Bahgat

69

5- HLR sends LU acknowledge back to SPX then back to primary blade

Traffic CasesMobile Originating Call

1 2 6543

1- A# sends its IMSI, B# and Bearer Capability


Mohammad Bahgat

70


1 2 6543



Mohammad Bahgat

71

chosen


1 2 6543

3- Blade 2 will read load vector from cluster handler and assign primary & buddy blades of last LU of A#


Mohammad Bahgat

72

blades of last LU of A#


1 2 6543

4- SRI sent with TID to HLR


Mohammad Bahgat

73

Traffic CasesMobile Terminating Call

1 2 6543

1- B# sends IAM request to SPX


Mohammad Bahgat

74


1 2 6543



Mohammad Bahgat

75


1 2 6543

3- Blade 3 chosen as the lowest load blade


Mohammad Bahgat

76


1 2 6543

4- SRI with TID sent to HLR


Mohammad Bahgat

77


1 2 6543

5- HLR sends PRN aligned with IMSI of A# back to SPX


Mohammad Bahgat

78


1 2 6543

6- SPX perform round robin technique to choose randomly a blade blade 6


Mohammad Bahgat

79



1 2 6543

7- Load vector calculated for A# based on [IMSI, CP Load, Cluster Area Identifier], primary blade 5 and blade 5 calculate load vector to choose buddy


Mohammad Bahgat

80



1 2 6543

8- Blade 5 sends PRN acknowledgement assigned with MSRN and HLR sends back to SPX SRI acknowledgement that will finally back to blade 3


Mohammad Bahgat

81

to SPX SRI acknowledgement that will finally back to blade 3


1 2 6543

9- Blade 3 routes to blade 5 for mobile terminating MTE


Mohammad Bahgat

82

Traffic CasesHand Over

Serving BC Drift BC1 2 65431 2 6543

Serving BC Drift BC

1- A# sends request to SPX for HO


Mohammad Bahgat

83



Serving BC Drift BC

2- SPX of Serving BC sends HO request to SPX of Drift BC


Mohammad Bahgat

84



Serving BC Drift BC



Mohammad Bahgat

85

chosen



Serving BC Drift BC

4- SPX will choose lowest load blade, blade 5 chosen


Mohammad Bahgat

86



Serving BC Drift BC

5- Load vector calculated for A# based on [IMSI, CP Load, Cluster Area Identifier], primary blade 6 and blade 6 calculate load vector to choose buddy


Mohammad Bahgat

87


AGENDA








Mohammad Bahgat

88

Signaling from Blade Cluster Point of View Introduction

SPXes main functions are: SPXes main functions are:q SPXes will choose the leader blade by Round-Robin method

qHide cluster from external NEsqHide cluster from external NEs

q Provide external signaling interfaces

qAs long as blades using IP only; SPX will act as an SGW for TDM/ATM

q SPXes will act as STPs for quasi-associate signaling mode

q For SCCP based signaling; it will need a protocol conversion to be directed toblades that understand IP; this is known by SUA protocol


Mohammad Bahgat

89

Signaling from Blade Cluster Point of View Protocols

SUA will be supported for MSC-BC internal connections (Between SPXes and SUA will be supported for MSC-BC internal connections (Between SPXes andBlades & between Blades themselves)

Blades external interfaces based on SCCP,GCP over SCTP setup directly toBlades external interfaces based on SCCP,GCP over SCTP setup directly toMGWbypassing SPXes

This is also applied for SIP & SIP-I protocols to target nodes in IMS network via This is also applied for SIP & SIP-I protocols to target nodes in IMS network viaIPLB blades

M3UA based signaling could possibly be also setup over direct paths to the bladesbut its not recommended because of increased configurations neededbut its not recommended because of increased configurations needed


Mohammad Bahgat

90



Mohammad Bahgat

91



Mohammad Bahgat

92

Signaling from Blade Cluster Point of View Addressing & Routing

Connections of NEs that are not aware of MSC-BC as a distributed multi-hostedConnections of NEs that are not aware of MSC-BC as a distributed multi-hostedsystem [MGWs], MSC-BC appears as one single MSC-Server node Common clusterSPC/GT

NEs that are non-cluster-aware [RANAP RNC, BSSAP BSC, MAP/TCAPHLR], are all signaling peers that uses SCCP as a base signaling protocol; henceconnections are proxied that SPX pair performs a cluster internal load balancingconnections are proxied that SPX pair performs a cluster internal load balancingwithout letting blades being visible to the outside


Mohammad Bahgat

93


Connections of NEs that are not aware of MSC-BC as a distributed multi-hostedConnections of NEs that are not aware of MSC-BC as a distributed multi-hostedsystem [MGWs], MSC-BC appears as one single MSC-Server node Common clusterSPC/GT

NEs that are non-cluster-aware [RANAP RNC, BSSAP BSC, MAP/TCAPHLR], are all signaling peers that uses SCCP as a base signaling protocol; henceconnections are proxied that SPX pair performs a cluster internal load balancingconnections are proxied that SPX pair performs a cluster internal load balancingwithout letting blades being visible to the outside


Mohammad Bahgat

94


4 types of addresses could be distinguished; 4 types of addresses could be distinguished;

qGlobal Title for cluster [One common GT for all blades]qCluster SPC [One DPC for all blades, HPC on SPXes] for SCCP basedqCluster SPC [One DPC for all blades, HPC on SPXes] for SCCP basedsignaling RANAP, BSSAP & MAP/TCAPq Individual SPCs per SPX, one SPC common for all blades, for GCP,ISUP/BICCISUP/BICCq Extra SPC for associated signaling mode On SPX and Blades as well [Non-Ericsson BSC]


Mohammad Bahgat

95


4 types of addresses could be distinguished; 4 types of addresses could be distinguished;

qGlobal Title for cluster [One common GT for all blades]qCluster SPC [One DPC for all blades, HPC on SPXes] for SCCP basedqCluster SPC [One DPC for all blades, HPC on SPXes] for SCCP basedsignaling RANAP, BSSAP & MAP/TCAPq Individual SPCs per SPX, one SPC common for all blades, for GCP,ISUP/BICCISUP/BICCq Extra SPC for associated signaling mode On SPX and Blades as well [Non-Ericsson BSC]


Mohammad Bahgat

96


Hosted Point Code: SPXes seen as MTP STPs from external NE point of viewHosted Point Code: SPXes seen as MTP STPs from external NE point of viewHosted Point Code is an SCCP level in SPX where SPX will recognize HPC anddistribute the messages to one of blades after protocol conversion by Round-RobinBlades respond directly to SPX and allocate Destination local Reference NumbersBlades respond directly to SPX and allocate Destination local Reference NumbersDRN for SCCP signaling RANAP/BSSAP or Transaction IDs TID for MAPdialogues signalingAfter connection/dialogue initially established; SPX will use DRN/TID for routingAfter connection/dialogue initially established; SPX will use DRN/TID for routingto the right bladeWhere does GTT performed?q Performed by SPX for outbound traffic sent by local SCCP applications onSPX but not for outbound traffic of bladesSPX but not for outbound traffic of bladesqWhile performed by SPX for inbound traffic as an intermediate or far-endSPC, maybe also performed at the blades if necessitates


Mohammad Bahgat

97



Mohammad Bahgat

98



Mohammad Bahgat

99



Mohammad Bahgat

100



Mohammad Bahgat

101

Signaling from Blade Cluster Point of View Signaling Scenarios

SIGTRAN to SIGTRAN SIGTRAN to SIGTRAN


Mohammad Bahgat

102


SS7 to SIGTRAN [QUASI-ASSOCIATE MODE] SS7 to SIGTRAN [QUASI-ASSOCIATE MODE]


Mohammad Bahgat

103


SS7 to SIGTRAN [ASSOCIATE MODE] SS7 to SIGTRAN [ASSOCIATE MODE]


Mohammad Bahgat

104


Internal Connections Internal Connections


Mohammad Bahgat

105

Signaling from Blade Cluster Point of View SUA

SUA Concepts SUA ConceptsqApplication Server (AS): Logical entity serving specific RK, contains one ormore of ASPs that actively processing traffic. AS uses SUA for communicatingSCTP/IP infrastructure as a transport layer. You can consider one AS equivalentSCTP/IP infrastructure as a transport layer. You can consider one AS equivalentto one BCqApplication Server Process (ASP): Element of distributed IP based signalingnode, provisioned to receive certain ranges of signaling trafficnode, provisioned to receive certain ranges of signaling trafficq Signaling Gateway (SG): Element that terminates SS7 and transport SCCP orMTP3 messages over IP to an IP SEP (Blade), SG could be modeled as one SGPthat is located at the border between SS7 and IP networkq Signaling Gateway Process (SGP): A Process instance of an SG, its functionq Signaling Gateway Process (SGP): A Process instance of an SG, its functioncomprises SS7 & SUA stack, one SGP exists in SG where all remote processes areconnected; SGP & SG is 1:1. You can consider one SGP equivalent to one SPX


Mohammad Bahgat

106


SUA Concepts SUA ConceptsqApplication Server (AS): Logical entity serving specific RK, contains one ormore of ASPs that actively processing traffic. AS uses SUA for communicatingSCTP/IP infrastructure as a transport layer. You can consider one AS equivalentSCTP/IP infrastructure as a transport layer. You can consider one AS equivalentto one BCqApplication Server Process (ASP): Element of distributed IP based signalingnode, provisioned to receive certain ranges of signaling trafficnode, provisioned to receive certain ranges of signaling trafficq Signaling Gateway (SG): Element that terminates SS7 and transport SCCP orMTP3 messages over IP to an IP SEP (Blade), SG could be modeled as one SGPthat is located at the border between SS7 and IP networkq Signaling Gateway Process (SGP): A Process instance of an SG, its functionq Signaling Gateway Process (SGP): A Process instance of an SG, its functioncomprises SS7 & SUA stack, one SGP exists in SG where all remote processes areconnected; SGP & SG is 1:1. You can consider one SGP equivalent to one SPX


Mohammad Bahgat

107


SUA Concepts SUA Conceptsq Signaling Process (SP): Process instance that uses SUA to communicate withother SPs in SUA network, each SP owns an SCTP End Point used for TX&RXSUA messages, in SUA; SP could be ASP or SGP or IP Server Process (IPSP)SUA messages, in SUA; SP could be ASP or SGP or IP Server Process (IPSP)qRouting Context & Routing Key (RC & RK): Uniquely identifies Routing Key(RK) where it describes a set of SS7 parameters and parameter ranges that definerange of signaling traffic configured to be handled by particular ASrange of signaling traffic configured to be handled by particular ASq SCTP Modes:

oClient-Server Modeo Peer-to-Peer Mode

Peer-to-Server Modeo Peer-to-Server Mode


Mohammad Bahgat

108


SUA Concepts SUA ConceptsqVisualization of SUA Concepts; SUA allows ASPs to be part of several ASs


Mohammad Bahgat

109

Signaling from Blade Cluster Point of View SIP Interworking & IMS


Mohammad Bahgat

110



Mohammad Bahgat

111



Mohammad Bahgat

112

AGENDA








Mohammad Bahgat

113

Blade Cluster Configuration Quick ViewIntroduction (SCTP Connections)

SCTP associations are setup both internally between BC components and towards SCTP associations are setup both internally between BC components and towardsexternal NEs in the IP domain SCTP associations and SUA connections are setup automatically between blades,connections to SPXes need to be configured manuallyconnections to SPXes need to be configured manually Separate SCTP associations are needed for each user (M3UA, SUA & GCP)Blades need associations to both SPXes and SPXes need the correspondingassociations to all bladesassociations to all blades

MSC Blades:q SUA toward both SPXesqM3UA toward both SPXesqM3UA toward both SPXesqDirect GCP toward all MGWs using GCP on SCTP


Mohammad Bahgat

114

Blade Cluster Configuration Quick ViewIntroduction (SCTP Connections)

SCTP associations are setup both internally between BC components and towards SCTP associations are setup both internally between BC components and towardsexternal NEs in the IP domain SCTP associations and SUA connections are setup automatically between blades,connections to SPXes need to be configured manuallyconnections to SPXes need to be configured manually Separate SCTP associations are needed for each user (M3UA, SUA & GCP)Blades need associations to both SPXes and SPXes need the correspondingassociations to all bladesassociations to all blades

MSC Blades:q SUA toward both SPXesqM3UA toward both SPXesqM3UA toward both SPXesqDirect GCP toward all MGWs using GCP on SCTP


Mohammad Bahgat

115

Blade Cluster Configuration Quick ViewConfiguration Example

Network Example DiagramNetwork Example Diagram

Configuration


Mohammad Bahgat

116



Configuration


Mohammad Bahgat

117




Mohammad Bahgat

118

Blade Cluster Configuration Quick ViewUseful Commands

NELS Network Element Data, ListNELS Network Element Data, ListCPLS CP Identification, ListCPGLS CP Group, ListHWCLS Hardware Configuration, ListCQRHLLSCQRHLLS Quorum Log, ListCQMSP:CP=ALL,DETAILS; Cluster Handler, Quorum Membership Data, PrintODBIP Cluster Object Data, Blade Information, PrintMGSBP # Registered Subscribers on MSC-S Blade, PrintMGSBP # Registered Subscribers on MSC-S Blade, PrintPLCLP Processor Load, Cluster Processor Load Survey, PrintCPLS l CP Identification, Hardware related info, List


Mohammad Bahgat

119

In Summer


Mohammad Bahgat

120

Documents

Blade Cluster