t Dm Based High Speed Signalling Links

Slide titleIn CAPITALS

50 pt

Slide subtitle 32 pt

TDM based High Speed Signalling Links

Top right corner for field-mark, customer or partner logotypes. See Best practice for example.

Slide title 40 pt


Text 24 pt

Bullets level 2-520 pt

CBC-07:002068 Uen Rev A Ericsson Internal TDM based High Speed Signalling Links 2007-09-302

Agenda

Concept Pre-requirements for HSL BSC configuration MGW configuration Migration Procedure Problems & reference TRs References


Slide title 40 pt


Text 24 pt



Agenda

ConceptConcept Pre-requirements for HSL BSC configuration MGW configuration Migration Procedure Problems & reference TRs References


Slide title 40 pt


Text 24 pt



TDM based High Speed Signaling Links (FAJ1210166/1)

HSL uses a whole 2 Mbit/s channel as a signalling linkuses a whole 2 Mbit/s channel as a signalling link.

On A-interface, HSL increases the maximum capacity to 16x2 increases the maximum capacity to 16x2 Mbit/sMbit/s, makes it e.g. possible to connect high-capacity BSCs, which do not yet support Signalling over IP

The TDM-based High-Speed Signaling Links are based on a protocol stack consisting of MTP3, MTP2 and MTP1.

– A whole E1 (or an E1 on an STM-1) is used as the MTP1-layerA whole E1 (or an E1 on an STM-1) is used as the MTP1-layer.– ITU-T, ETSI and Chinese standards are supported for the MTP3

and MTP2 layers.


Slide title 40 pt


Text 24 pt



TDM based High Speed Signaling Links (FAJ1210166/1)

The MTP2 (Message Transfer Part) standards supported are:– ITU-T Q.703 (07/96) - SS7 Signaling Data Link, Annex A– Specification of 2 Mbit/s High Speed Signalling Link (V1.0) China

Mobile 2000.5

The MTP3 (Message Transfer Part) standards supported are:– ITU-T Q.701 (88, 03/93) - Functional Description of MTP– ITU-T Q.704 (88, 03/93, 07/96) - Signaling Network Functions and

Messages– ITU-T Q.707 (88) - Testing and Maintenance– ETS 300 008 - Integrated Services Digital Network; CCITT

Signaling System No 7, Message Transfer Part to Support International Interconnection, ETSI


Slide title 40 pt


Text 24 pt



Agenda

Concept Pre-requirements for HSLPre-requirements for HSL BSC configuration MGW configuration Migration Procedure Problems & reference TRs References


Slide title 40 pt


Text 24 pt



Pre-requirements in BSC

2 additional RPP boards are needed


Slide title 40 pt


Text 24 pt



Pre-requirements in MGW

Hardware: – new ET-C41/2 (ROJ 119 2257/2) board needed.

Software: – M-MGw R4 CNP R4.2.2.0 and onward is required.

License: – License key file containing TDM-based HSL should be

ordered and updated to the node before HSL definition / migration.


Slide title 40 pt


Text 24 pt



Agenda

Concept Pre-requirements for HSL BSC configurationBSC configuration MGW configuration Migration Procedure Problems & reference TRs References


Slide title 40 pt


Text 24 pt



BSC configuration

1. Define 2 new RPP’s and EM’s for HSL

2. Define ST and SNT allocation

3. Define the 2 semi-permanent connection to be used for SL towards MSC

4. Activate the SL’s

5. Check the MTP3 routing for associated mode signaling

bsc_integration.txt (3 KB)


Slide title 40 pt


Text 24 pt



Concept Pre-requirements for HSL BSC configurationBSC configuration MGW configurationMGW configuration Migration ProcedureMigration Procedure Problems & reference TRs References


Slide title 40 pt


Text 24 pt



ECHO "======>> Creating Mtp2Hsl" CREATE ( parent "ManagedElement=1,TransportNetwork=1" identity Mtp2Hsl moType Mtp2Hsl exception none nrOfAttributes 1 userLabel String "Mtp2Hsl" ) ----------------------------------------------------------------------------------------------------------------------------- ECHO "======>> Creating Mtp2HslProfileItu" CREATE ( parent "ManagedElement=1,TransportNetwork=1,Mtp2Hsl=Mtp2Hsl" identity 1 moType Mtp2HslProfileItu exception none nrOfAttributes 4 de Integer 11 te Integer 793 ue Integer 198 userLabel String "Mtp2HslProfileItu_1" ) -----------------------------------------------------------------------------------------------------------------------------

ECHO "======>> Creating Mtp2HslTpItu" CREATE ( parent "ManagedElement=1,TransportNetwork=1,Mtp2Hsl=Mtp2Hsl" identity Mtp2HslTpItu_625101 moType Mtp2HslTpItu exception none nrOfAttributes 4 mtp2HslProfileItuRef Reference

"ManagedElement=1,TransportNetwork=1,Mtp2Hsl=Mtp2Hsl,Mtp2HslProfileItu=1" physicalPort Reference

"ManagedElement=1,Equipment=1,Subrack=6,Slot=25,PlugInUnit=1,ExchangeTerminal=1,Os155SpiTtp=6251,Vc4Ttp=1,Vc12Ttp=1,E1Ttp=1"

sequenceNumberingType Integer 1 userLabel String "Mtp2HslTpItu_625101" )

Select E1 link, remove existing configuration on the E1.If the E1 is used for Traffic, the corresponding MO(TdmTermGrp, Ds0Bundle). If the E1 is used for signalling, the corresponding MO (Mtp3bSlxxx, Mtp2Tpxxx, Ds0Bundle) should be removed

MGW configuration


Slide title 40 pt


Text 24 pt



MGW configuration

TransportNetwork

Mtp3bSpxxx

Mtp3bSls

Mtp3bSlxxx

Mtp3bSrs

Mtp2HslTpxxx

Mtp3bSr

All the configuration is same as before.

But Mtp3bSls for HSL and LSL should be separated

So the Mtp3bSr should be separated and their priority cannot be the same.


Slide title 40 pt


Text 24 pt



Concept Pre-requirements for HSL BSC integration MGW integration Migration ProcedureMigration Procedure Problems & reference TRs References


Slide title 40 pt


Text 24 pt



Migration procedure

SW upgrade HW replacement License key update Configuration procedure


Slide title 40 pt


Text 24 pt



SW upgrade

Upgrade MGW to CNP R4.2.2.0 and onwardCNP R4.2.2.0 and onward following <<upgrade guide>> for each package


Slide title 40 pt


Text 24 pt



HW replacement

In BSC: 2 additional RPP boards are needed


Slide title 40 pt


Text 24 pt



HW replacement

MGW:

New ET-C41/2 board replacing For GMP V3.0 any ET-C41 board can be replaced.

For GMP V2.x the two ET-MC41 boards in the ATM extension subrack will be replaced, the ET-C41/2 will be positioned in the two most left slots (slot 21&22) and the Dummy boards to the right (slot 23&24).


Slide title 40 pt


Text 24 pt



HW replacementfor GMP v3.0

Board Replacing Procedure if MSP1+1 used

– Check which board is the standby board. Lock the standby board. The ongoing calls and signaling links on the MSPG are not affected.

– Follow OPI “Replacing an Exchange Terminal Board” to replace the board with new ET-C41/2. The ongoing calls and signaling links on the MSPG are not affected.

– Check that the standby board and MSPG are working normal.

– Soft lock the active board.

– After some specified time the board is locked. The remaining calls on the MSPG are dropped. The signaling links on the MSPG will be down and up. MSPG active board switched to the new ET-C41/2 board.

– Follow OPI “Replacing an Exchange Terminal Board” to replace the board with new ET-C41/2. The ongoing calls and signaling links on the MSPG are not affected.

– Check that the new board and MSPG are working normal.


Slide title 40 pt


Text 24 pt



HW replacementfor GMP v3.0

Board Replacing Procedure if NO MSP1+1 used

– Follow OPI “Replacing an Exchange Terminal Board”


Slide title 40 pt


Text 24 pt



HW replacementfor GMP v2.x

Follow “GMP V2.x Node Expansion Procedure, M-MGw R4” section 5.5 ‘HSL Expansion Procedure for ATM Subrack’

This expansion case includes traffic impact for the boards involved in the expansion.

Prerequisites for installation and configuration of the HSL in the ATM subrack: All the network configurations have been deleted/moved from the ETMC41 boards in the ATM subrack slots 21 and 23.


Slide title 40 pt


Text 24 pt




Procedure: Execute CALL Script:

EXP-HSL_EXP_CALL_01_Conf Remove the ET-MC41 boards found in slots 21 and 23 in the ATM subrack. Insert ET-C41/2 boards into slots 21 and 22 in the ATM subrack. Insert dummy boards into slot 23, and slot 24. Check that the hardware is installed according to “HW Configuration for GMP V2.1” Activate Plug&Play: Execute CALL Script:

EXP-HSL_EXP_CALL_02_PnP_On Wait until all new boards come up in locked state: In Element Manager Equipment view, wait until the

following states apply for all new boards: - The PlugInUnit.operationalState is Enabled. - The PlugInUnit.administrativeState is Locked.

Note: It may take up to 15 minutes for the boards to come up after the Plug&Play has been turned on.Important: All the new boards must power-up and have the PlugInUnit Operational state set as “Enabled” and Administrative state set as “Locked” before continuing to the next step. If this is not the case, there is a risk of corrupted configuration in the node.

Unlock the new boards: Execute CALL Script:EXP-HSL_EXP_CALL_03_Unlock_Boards

Check that all the boards are enabled and in unlocked state: The status of PlugInUnit.administrativeState must be Unlocked for the boards.

Create a new CV and set it startable.


Slide title 40 pt


Text 24 pt




Example for HSL Expansion Procedure for ATM Subrack (1)

1. Delete Network Configuration

SLT-MGW34> lst Os155SpiTtp=2231...SLT-MGW34> lst Os155SpiTtp=2211...SLT-MGW34> lko Ds0Bundle=221101/01070918-16:34:44 127.0.0.1 7.0p MGW_NODE_MODEL_R4_2_R11_A01 stopfile=/tmp/2172===================================================================================MOs linked to 809 Equipment=1,Subrack=2,Slot=21,PlugInUnit=1,ExchangeTerminal=1,Os155SpiTtp=2211,Vc4Ttp=1,Vc12Ttp=1,E1Ttp=1,Ds0Bundle=221101/01 (-,E)===================================================================================reservedBy Subrack=2,Slot=21,PlugInUnit=1,ExchangeTerminal=1,Os155SpiTtp=2211,Vc4Ttp=1,Vc12Ttp=1,E1Ttp=1,Ds0Bundle=221101/01 ---> (-,E) Mtp2TpItu=Mtp2TpItu_BSC5_1mtp2ProfileItuId Mtp2TpItu=Mtp2TpItu_BSC5_1 ---> (-,-) Mtp2ProfileItu=1plugInUnitId Mtp2TpItu=Mtp2TpItu_BSC5_1 ---> (U,E) Subrack=1,Slot=8,PlugInUnit=1reservedBy Mtp2TpItu=Mtp2TpItu_BSC5_1 ---> (-,E) Mtp3bSpItu=MGw34_3-1004,Mtp3bSls=BSC5_3-205,Mtp3bSlItu=BSC5_3-205_1mtp3bSrsId Mtp3bSpItu=MGw34_3-1004,Mtp3bSls=BSC5_3-205 ---> (-,E) Mtp3bSpItu=MGw34_3-1004,Mtp3bSrs=BSC5_3-205reservedBy Mtp3bSpItu=MGw34_3-1004,Mtp3bSls=BSC5_3-205 ---> (-,E) Mtp3bSpItu=MGw34_3-1004,Mtp3bSrs=BSC5_3-205,Mtp3bSr=BSC5_3-205===================================================================================

SLT-MGW34> u+ signalling.txtSLT-MGW34> del Mtp3bSlItu=BSC5_3-205_1SLT-MGW34> del Mtp2TpItu=Mtp2TpItu_BSC5_1SLT-MGW34> del Ds0Bundle=221101/01SLT-MGW34> u-070918-16:36:27 127.0.0.1 7.0p MGW_NODE_MODEL_R4_2_R11_A01 stopfile=/tmp/2172To undo, execute command: run /home/etclixi/signalling.mos ($undocommandfile)Note: to convert command files from moshell format to trun/emas format, execute the command: u! <commandfile>


Slide title 40 pt


Text 24 pt





1. Delete Network Configuration (contd)

SLT-MGW34> lko Ds0Bundle=221101/02_31

070918-16:34:35 127.0.0.1 7.0p MGW_NODE_MODEL_R4_2_R11_A01 stopfile=/tmp/2172===================================================================================MOs linked to 808 Equipment=1,Subrack=2,Slot=21,PlugInUnit=1,ExchangeTerminal=1,Os155SpiTtp=2211,Vc4Ttp=1,Vc12Ttp=1,E1Ttp=1,Ds0Bundle=221101/02_31 (-,E)===================================================================================reservedBy Subrack=2,Slot=21,PlugInUnit=1,ExchangeTerminal=1,Os155SpiTtp=2211,Vc4Ttp=1,Vc12Ttp=1,E1Ttp=1,Ds0Bundle=221101/02_31 ---> (U,E) TdmTermGrp=221101/02_31===================================================================================

SLT-MGW34> u+ traffic.txtSLT-MGW34> get TdmTermGrp=221101/02_31SLT-MGW34> bl TdmTermGrp=221101/02_31SLT-MGW34> acc Vmgw=VMGW1 removeTdmTermGrpMosSLT-MGW34> del TdmTermGrp=221101/02_31SLT-MGW34> del Ds0Bundle=221101/02_31SLT-MGW34> u-


Slide title 40 pt


Text 24 pt





1. Delete Network Configuration (contd)

SLT-MGW34> u+ mspg.txtSLT-MGW34> st mspg

070918-16:40:21 127.0.0.1 7.0p MGW_NODE_MODEL_R4_2_R11_A01 stopfile=/tmp/2172===================================================================================Proxy Adm State Op. State MO=================================================================================== 2465 1 (ENABLED) TransportNetwork=1,Mspg=2211_2231 2482 1 (ENABLED) TransportNetwork=1,Mspg=1===================================================================================Total: 2 MOs

SLT-MGW34> del 2465SLT-MGW34> u-

SLT-MGW34> u+ os155.txtSLT-MGW34> del Os155SpiTtp=2211SLT-MGW34> del Os155SpiTtp=2231SLT-MGW34> u-


Slide title 40 pt


Text 24 pt





2. Follow “GMP V2.x Node Expansion Procedure, M-MGw R4” to HSL Expansion

SLT-MGW34> #run EXP-HSL_EXP_CALL_01_Conf

SLT-MGW34> #pull out etmc41 from 012100&012300

SLT-MGW34> #insert etc41 to 012100 and 012200

SLT-MGW34> #run EXP-HSL_EXP_CALL_02_PnP_On

SLT-MGW34> lhsh 012100 viiSLT-MGW34> lhsh 012200 vii

SLT-MGW34> #Unlock 012100 &012200 when they are UP(ENABLED)SLT-MGW34> deb 012100SLT-MGW34> deb 012200SLT-MGW34> lhsh 012100 viiSLT-MGW34> lhsh 012200 vii

SLT-MGW34> cvms MGw34_R4220_HSLboardOK


Slide title 40 pt


Text 24 pt





3. Restore Network Configuration

SLT-MGW34> run os155.mosSLT-MGW34> get Os155SpiTtp=2211SLT-MGW34> get Os155SpiTtp=2221SLT-MGW34> lt allSLT-MGW34> ldeb Os155SpiTtp=2211SLT-MGW34> ldeb Os155SpiTtp=2221SLT-MGW34> run mspg.mosSLT-MGW34> get mspgSLT-MGW34> # addTdmTermGrp to vmgw cannot be logged in undo, so traffic.mos should be modified before use. It can

be done like this: convert traffic.mos to traffic.mo by 'u! trafic.mos', modify traffic.mo by adding addTdmTermGrp & deb them

SLT-MGW34> u! /home/etclixi/traffic.mos

070918-16:38:40 127.0.0.1 7.0p MGW_NODE_MODEL_R4_2_R11_A01 stopfile=/tmp/2172Result saved to: /home/etclixi/traffic.mo ($undotrunfile).

SLT-MGW34> #modify traffic.mo by adding addTdmTermGrp & deb themSLT-MGW34> run traffic.moSLT-MGW34> run signalling.mos

SLT-MGW34> cvms MGw34_R4220_NWconfigRestored


Slide title 40 pt


Text 24 pt



MGW integration- LKF

License Check and Install Check if the feature key for TDM-based High-Speed Signaling Link is

included in the License Key File of the node.

If NOT, follow OPI “Install License Key File” to update the LKF <featureKey id="CXC4010071/3042"> <description>TDM based High Speed Signaling Links ProdNo:FAJ1210166/1</description> <start>2000-01-01</start> <noStop/> </featureKey>


Slide title 40 pt


Text 24 pt



Migration procedure

1. Define HSL function related MO – a) Define Mtp2Hsl, Mtp2HslProfileItu– b) Select E1 link, remove existing configuration on the E1– c) Define Mtp2HslTpItu on the E1


Slide title 40 pt


Text 24 pt



SP

SRS

SR

SR,prio=3

SLS

SLS

HSL

NB SL

SLC-0

SLC-15

SL-0

ET

-C41/2

ET

4-1

MGW

SP

SRS

SR

SLS

HSL

NB SL

SLC-0

SLC-15

SLC-0

BSC

E1

ST

M-1

SR, prio=2

SR, prio=1

1. In MGw, Define HSL function related MO(Mtp2Hsl, Mtp2HslProfileItu, Mtp2HslTpItu ) Note: remove existing configuration on the selected E1 link

2. In BSC, Define new RPP's, EM's and SNT’s

3. Create new signalling link set on MGW

4. Create new signalling route with priority 3

5. Deactivate one NB link from both nodes (assume it’s SLC-0)

6. Remove the NB link from both nodes

7. Create new HSL between both nodes and activate it (SLC-0)

8. Repeat steps 5-7 to add the second HSL (but with SLC-1)

9. Change SR to priority 2 for the route containing the NB links.

10. Change SR to priority 1 for the route containing HSL links

11. Check that the signaling traffic is carried by HSL

12. Remove remaining NB links after confirming HSL works well.

Migration procedure


Slide title 40 pt


Text 24 pt



Migration procedure

DT example

DT.zip (7 KB)


Slide title 40 pt


Text 24 pt



Agenda

Concept Pre-requirements for HSL BSC integration MGW integration Migration ProcedureMigration Procedure Problems & reference TRsProblems & reference TRs References


Slide title 40 pt


Text 24 pt



Problems & reference TRs

HI33733:SP51, IPB devices 100% DependencyLocked Problem Description:

– IPB pool is 100% dependency locked. Trouble shooting:

– Define Nb over IP on R4.1.2.0, there is 25% IPB idle; Upgrade to SP51, it becomes 100% dependencylocked

– Lock/unlock MSB board, restart node doesn’t help– After several discussion with LMF, we find out traffic over IP

is working normally, even if IPB pool is 100% dependency locked

Solution:– Programming fault. Incorrect handle of variable or symbol.

Fixed in CNP R4.2.2.0B.


Slide title 40 pt


Text 24 pt




HI32090 No delete option in EMAS for HSL MOsHI32090 No delete option in EMAS for HSL MOs Problem description:

– Not be able to delete HSL MOs in EMAS, as no delete option in EMAS

Workaround– Use Object Explorer to delete HSL MOs

Solution:– Delivered in CNP 4.2.2.0B


Slide title 40 pt


Text 24 pt




UABtr52905 pmcounters are not written into xml file UABtr52905 pmcounters are not written into xml file though scanner definedthough scanner defined

Problem Description:– Scanner for hsltp is created but no 15min.xml files are

written in pm_data.

Solution:

– Fixed in CNP 4.2.2.0B


Slide title 40 pt


Text 24 pt




HI33526 (UABtr53534) Unlocking Core MP 000200 cause board HI33526 (UABtr53534) Unlocking Core MP 000200 cause board 000300 restart000300 restart

Problem description:– The problem happened at performing test case "HSL behavior when core

MP Replaced". The test instruction requires to do the following steps: - Lock GPB in main subrack slot 2 - Simulate HW failure by using 'reload --'. Run the board in backup

mode - Run the board 000200 back in active with "reload" - Unlock GPB in main subrack slot 2.

– After unlocking 000200, board 000300 auto restarted. The reason is " A program has not been killed within one minute". The HSL link and TDM link was not affected.

Suggested traces:– All the trace groups for Board Manager process need to be enabled with

the command$ te e all Cs_boardmanager_proc $ te save *


Slide title 40 pt


Text 24 pt




HI40141 (UABtr53972) MSPG link switch causes traffic and signalling HI40141 (UABtr53972) MSPG link switch causes traffic and signalling disturbancedisturbance

Problem description:1) when SelectedBoard is 6-25, selectedPort is 6251 - Pull out cable from port 6251, signaling links defined on this mspg could

be(~80%) flash down both for narrowband signaling and HSL, and ongoing call on this mspg is dropped, there is alarm for the corresponding SNT in MSC for the TdmTermGrp raising and ceasing.

- manualMspSwitch from port 6251 to 6261 doesn't cause any problem.

2) when SelectedBoard is 6-25, selectedPort is 6261 - Pull out cable from port 6261, no problem. - manualMspSwitch from port 6261 to 6251 doesn't cause any problem.

3) when no ET4-1 used (mspg defined between 2 MGWs) there's no problem observed when pull out cable.

Note: this problem is found on R4.2.2.0B as well as R4.1.2.0.


Slide title 40 pt


Text 24 pt



Agenda

Concept Pre-requirements for HSL BSC integration MGW integration Migration ProcedureMigration Procedure Problems & reference TRs ReferencesReferences


Slide title 40 pt


Text 24 pt



References

Migration Procedure for LSL to TDM based HSL

Test Description of M-MGw for TDM based HSL

User guide for signaling 10/1553-AXM 101 01/4 Uen N


Slide title 40 pt


Text 24 pt



Date post:	12-Dec-2015
Category:	Documents
Upload:	abhinav-garg
View:	214 times
Download:	0 times

t Dm Based High Speed Signalling Links

Documents