Abis Over TDM to Abis IP Over E1

Huawei Technologies Co., Ltd. All rights reserved

Product Name

2G Network Swap procedures

Intended User Prepared by Reviewed by Approved by

Wireless BSS Engineer (GSM) Bonisiwe BSS Wireless Engineer Fengsongjie/Jason

Document Version

V1.0

Due Date Date: Date:

15 August 2013

Huawei MTN Project Team

KZN Abis IP over E1 Swap experience Summary And Document

Guide

Hi Guys Please find attached the new chapter to ABIS migration, starting somewhere next week What is going to happen: we are going to use the existing E1 at the switch and site we will cut them from the DXX to OSN (wire Telkom Tie to OSN port on planning page) Telkom E1 stay as if its TDM Changes from original ABISoIP Communication type is PPP/MP not PortIP Transmission Type is IP_over_E1 nor IP_over_FE/GE Destination is OTHER not BSC Specify which Timeslots are used on your script

KZN Swap experience summary and document Guide

Contents 1. Introduction……………………………………………………………………..………………………………………………….…...Error! Bookmark not defined. 1.1 Objective of This Ducument…………………………………………………………………..........................................Error! Bookmark not defined.

2. IP Requirements………………………………………………………...…………………….......................................... 2.1 Hardware Requirements………………………………………………………………………… 2.1.1 FG2a/c……………………………………………………………………………………………………………………………………….. 2.1.2 GOUa/c………………………………………………………………………………………………………………………………………

3. Hardware Planning Installation……………………………………………………………………………………………… 3.1 Hardware Installation on BSC………………………………………………………………………………………………………. 3.2 Hardware Installation on BTS……………………………………………………………………………………………………….

4. Data Planning ………………………………………………..…….................................................. 4.1 IP Planning……………………………………………………………………………………………………………………………………. 4.2 Implementation ……………………………..…………………………………………………………………………………………….

5. Verification……………………………………………………………………………………………………………………………….. 5.1 Verify Physical layer……………………………………………………………………………………………………………………… 5.2 Verify IP layer………………………………………………………………………………………………………………………………. 5.3 Verify the BSS Equipment……………………………………………………………………………………………………………..

6. Team Spirit…………………………………………………………………………………………………………..

1. Introduction The Purpose of this document describes the steps of Migrating a site from Abis over TDM to Abis over E1. Abis is the interface between the BSC and the BTS. The Abis interface has the features of high bandwidth and low cost, and is no longer a factor restricting the BSC capacity.

2. IP Requirements Hardware Requirements

2.1 2.1.1

FG2a/c Item

2.1.2

Specification

Abis

FG2a support TRX

384

Abis

FG2c support TRX

2,048

GOUa/c Item Abis GOUa support TRX

3. Hardware Planning Installation 3.1 Hardware installation on BSC On the BSC side: A

GOUc/FG2c/GOUa/FG2a interface board is configured



Insert FG2x/GOUx cards into BSC to the correct slots



Connect the cable to the correct port.

Specification 384

3.2 Hardware installation on BTS

On the BTS side: A GTMU or GTMUb board is configured. 

No additional hardware required basic on existing TDM BTS.



Connect E1 cable on GTMU for IP over E1.

.

4. Data IP Planning During Abis IP over E1migration we have to collect all data information that we will need from the customer to prepare the Abis IP over E1migration. 4.1 IP Planning Pre Requisite 

Before you can start with the BTS Abis IP over E1migration configuring the following IP information must be available:  BSC has an IP interface card connected to  BSC IP Address and Mask  BSC Gateway (CTN node) IP address  BTS Gateway IP Address (CTN node)  BSC can PING CTN CX???/CX??? node IP on site  BTS ESN from all types of BTS cabinet:

ESN number for a normal BTS3900 Cabinet found in a BBU:

ESN number for BTS3900E

4.2 Implementation (Create New BTS IP site) 

We have to prepare a new IP scripts for all the sites that will be migrated to IP no matter what type of BTS Cabinet as we have different type of BTS3900: (i) BTS3900_GSM (ii) BTS3900A_GSM (iii) BTS3900E_GSM (iv) BTS39000L_GSM



Before you making any changes on the site make sure that you have a backup of the TDM script configurations for each site, you can back up the script from M2000 using CME if it’s a live site.



Steps to export the TDM script using CME:

Open your planned work Area on CME:

Select your planned work area name then click OK:

Once your planned work area is opened go to the site (T0703) you a backup script for, Right click on the site and do as shown below.

Therefore you can save the backup script file on your PC.

ADD_BTS_703 backup from CME.txt

Steps to migrate the live site from TDM to E1: Do the simple troubleshooting:   

Check what is the active alarm before migrating the site, Check the status of all the RFU boards, Check the status of the channels

Listing commands.txt

Then you can run the Abis IPo E1 script: //*****************Deactivate and remove TDM connections************************// DEA BTS: IDTYPE=BYNAME, BTSNAME="703"; RMV BTSCONNECT: IDTYPE=BYNAME, BTSNAME="703", INPN=0, INCN=0, INSRN=0, INSN=6; RMV BTSCONNECT: IDTYPE=BYNAME, BTSNAME="703", INPN=1, INCN=0, INSRN=0, INSN=6; //******************Changing from TDM to Abis IP over E1*************************// SET BTSABISTROP: IDTYPE=BYNAME, BTSNAME="703", DETECTSWITCH=OFF; MOD BTS: IDTYPE=BYNAME, BTSNAME="703", SERVICEMODE=IP, IPPHYTRANSTYPE=IP_OVER_E1; ADD IPLOGICPORT: SRN=1, SN=22, BT=GOUc, LPNTYPE=Leaf, LPN=101, CARRYT=ETHER, PN=1, RSCMNGMODE=SHARE, BWADJ=OFF, CIR=64, FLOWCTRLSWITCH=ON, TRMLOADTHINDEX=3, OPSEPFLAG=OFF; ADD ADJNODE: ANI = 1032, NAME = "703", NODET = ABIS, BTSID = 12; ADD IPRT: SRN=1, SN=22, DSTIP="10.50.72.0", DSTMASK="255.255.255.0", NEXTHOP="10.50.0.94", PRIORITY=HIGH, REMARK="To BTS"; ADD BTSESN: IDTYPE = BYID, BTSID = 12, MAINDEVTAB = "21021127226TBC924925"; SET BTSIP: IDTYPE=BYNAME, BTSNAME="703", BTSCOMTYPE=PPP/MP, BTSIP="10.50.72.113", BSCIP="10.50.248.39", CFGFLAG=IPLGCPORT, SN=22, LPN=101; ADD BTSCONNECT: IDTYPE=BYNAME, BTSNAME="703", INPN=0, INCN=0, INSRN=0, INSN=6, DESTNODE=OTHER; ADD BTSCONNECT: IDTYPE=BYNAME, BTSNAME="703", INPN=1, INCN=0, INSRN=0, INSN=6, DESTNODE=OTHER; ADD BTSMPGRP: IDTYPE=BYNAME, BTSNAME="703", MPGRPN=0, CN=0, SRN=0, SN=6, LOCALIP="10.50.72.113", MASK="255.255.255.252", PEERIP="10.50.72.114", MPSWITCH=ENABLE, AUTHTYPE=NO_V; ADD BTSMPLNK: IDTYPE=BYNAME, BTSNAME="703", MPGRPN=0, PPPLNKN=0, PN=0, CN=0, SRN=0, SN=6, TSBITMAP=TS1-1&TS2-1&TS3-1&TS4-1&TS5-1&TS6-1&TS7-1&TS8-1&TS9-1&TS10-1&TS111&TS12-1&TS13-1&TS14-1&TS15-1&TS16-1&TS17-1&TS18-1&TS19-1&TS20-1&TS21-1&TS22-1&TS231&TS24-1&TS25-1&TS26-1&TS27-1&TS28-1&TS29-1&TS30-1&TS31-1; ADD BTSMPLNK: IDTYPE=BYNAME, BTSNAME="703", MPGRPN=0, PPPLNKN=1, PN=1, CN=0, SRN=0, SN=6, TSBITMAP=TS1-1&TS2-1&TS3-1&TS4-1&TS5-1&TS6-1&TS7-1&TS8-1&TS9-1&TS10-1&TS111&TS12-1&TS13-1&TS14-1&TS15-1&TS16-1&TS17-1&TS18-1&TS19-1&TS20-1&TS21-1&TS22-1&TS231&TS24-1&TS25-1&TS26-1&TS27-1&TS28-1&TS29-1&TS30-1&TS31-1; ADD BTSIPRT: IDTYPE=BYNAME, BTSNAME="703", DSTIP="10.50.248.39", DSTMASK="255.255.255.255", RTTYPE=OUTIF, CN=0, SRN=0, SN=6, ITFType=MP, IFNO=0;

ADD IPPATH: ANI = 1032, PATHID = 1, ITFT = ABIS, PATHT = EF, TXBW =4096, RXBW = 4096, TRMLOADTHINDEX = 3, VLANFLAG = DISABLE, PATHCHK = DISABLED; ADD IPPATH: ANI = 1032, PATHID = 2, ITFT = ABIS, PATHT = AF31, TXBW = 4096, RXBW = 4096, TRMLOADTHINDEX = 3, VLANFLAG = DISABLE, PATHCHK = DISABLED; ADD ADJMAP: ANI = 1032, ITFT = ABIS, TMIGLD = 10, FTI = 1; SET BTSVLAN: IDTYPE = BYID, BTSID = 12, SERVICETYPE = OML, DSCP = 56, VLANSWITCH=NO; SET BTSVLAN: IDTYPE = BYID, BTSID = 12, SERVICETYPE = RSL, DSCP = 56, VLANSWITCH=NO; SET BTSVLAN: IDTYPE = BYID, BTSID = 12, SERVICETYPE = EML, DSCP = 10, VLANSWITCH=NO; SET BTSVLAN: IDTYPE = BYID, BTSID = 12, SERVICETYPE = ESL, DSCP = 56, VLANSWITCH=NO; SET BTSVLAN: IDTYPE = BYID, BTSID = 12, SERVICETYPE = CSVOICE, DSCP = 46, VLANSWITCH=NO; SET BTSVLAN: IDTYPE = BYID, BTSID = 12, SERVICETYPE = CSDATA, DSCP = 46, VLANSWITCH=NO; SET BTSVLAN: IDTYPE = BYID, BTSID = 12, SERVICETYPE = PSHIGHPRI, DSCP = 26, VLANSWITCH=NO; SET BTSVLAN: IDTYPE = BYID, BTSID = 12, SERVICETYPE = PSLOWPRI, DSCP = 26, VLANSWITCH=NO; SET BTSVLAN: IDTYPE = BYID, BTSID = 12, SERVICETYPE = OTHERDATA, DSCP = 56, VLANSWITCH=NO; SET BSCABISPRIMAP: IDTYPE = BYID, BTSID = 12, TRANSTYPE = IP, OMLDSCP = 56, RSLDSCP = 56, EMLDSCP = 10, ESLDSCP = 56, VLANFLAG = DISABLE; ACT BTS: IDTYPE=BYNAME, BTSNAME="703", TRXIDTYPE=BYID;

T0703 Running IP Script.txt

During ACTIVATION Period: The RE should do the hard reset and it should take 5mins to come up if the site is not coming up within 5mins time starts troubleshooting:  PING Gateway IP , if you can’t be able to Ping it  Double check the configures with Tx planning and Optimization  Or double check CTN support.  If everything is 100% correct to all sides  Ask the RE to add the Status IP from the site using BTSM Tool. BTS3900E IP Steps 

The RE must add the Status IP to the site according to the design planning and he need to use the BTSM Tool, and then Query the Status whether he added the correct information.



After the adding the Status IP the RE need to give the BSS Engineer the ESN number and inform him/ her to add the IP Script remotely.

ESN number for BTS3900E

Activation steps: When we activating the site we have to check the followings: 



The site is activated as all the boards’ status showing Normal,

All the Sub-channels status should be working or in normal status:

Simple troubleshooting when the site is fully up:  

We have to troubleshoot the alarms when the site is up and There mustn’t be any active alarms left over unless is a transmission issue.

Avoid too long Downtime 

If the site it’s been down for so long that means the site is not carrying any traffic and the customer will complain. Try by all means to resolve the issue.

5. Verification 5.1 Verify physical layer 

Check the ETH light on BSC IP Abis cards.



Check the E1 light on BTS ETH port.



Check the alarms on BSC WebLMT to see if there is any alarms like “Ethernet link fault”

5.2 Verify IP layer  Ping from BSC device IP to BTS port IP  Check if there is any “Path Fault” alarms (only support when switched on Ping Test) 5.3 Verify the BSS equipment 

Check the FG2x/GOUx cards status on WebLMT to see if is any failures.



Check the BTS status on WebLMT to see if is any failures.



Check the alarms on WebLMT or M2000 to see if there is any alarms like “Board Failure”, “Cell out of service” “PS cell out of service”.

5.4 Verify the BSS service  Make a CS call to verify CS service on the IP site. 

Make a PS call to verify PS service on the IP site.



Monitor the KPI for the IP site.

6. Team Spirit With all the support we get from the entire department team I believe that is why everything happened according to the plan although sometimes we have some difficulties but we manage to put 7x BTS IP over E1 Sites on Air in a short period.