Activating an ATM Site

8/13/2019 Activating an ATM Site

http://slidepdf.com/reader/full/activating-an-atm-site 1/35

Work Instruction

ATM SITE ACTIVATION

RANSOG



Prerequisi te:

• Successful completion of this task depends on the following:

• RNC WBTS , cells, neighbors have to be created by DatabuildTeam. In the event any of the above are not ready by the time workbegins, contact :

• [email protected]

• [email protected] • [email protected] ; [email protected];

[email protected];[email protected]; [email protected] ;[email protected] ;[email protected] ;

• Desktop standalone HIT Macro (with correct .INI file for accessing3UK MSCs )

mailto:[email protected]


























Prerequisi te:

• Collect all required information:

• For all TDM sites, TNE`s can be found on

P Drive /TMuk Network.

• Log onto TOOGLE and search for the last

TNE generated :

• <TOOGLE> </TOOGLE>



Prerequisi te:

• Using the number of the TNE, log onto P

Drive using Godiva Explorer from TMUK

Citrix .



Prerequisi te:

• The files are ordered in directories

using the first three digits of the TNE

number, and can be found here :

•

P:\Networks\TXPLAN\DESIGN\UTMS_

ATM_DATA



RNC IuB MML DCN Con f igurat ion

• For the purpose of this procedure, we will be

using the following data:

• -> Site ID : 8776

• -> AA Interface ID : 177

• -> ATM Interface ID: 51

• -> VPI number: 18

• -> RNC IP/AA interface at RNC :10.26.111.161

• -> WBTS IP Subnet : 10.26.111.168 /29



Connect to the RNC using the HIT



Connect to the target RNC:



Termination Point

• First create a termination point (VP) on the target

interface:

• ZLCC:51,VP,18,,VC:::C,,,C1:::150,CPS,::;

• After creating the VP, configure virtual channel VC 32 tobe used for DCN transport:

• ZLCC:51,VC,18,32::U,,,U:U,,,U:::::;

• !Note: While VPIs are unique for any given IF,

VC configuration always stays the same(VC32-DCN VC33-CNBAP VC34-DNBAP

VC45&&VC48-DCH VC49&VC50-HS



• Next step is to configure an external IP over ATM (IPoA) interface on bothOMU boards. This interface serves to connect the OMU boards , which arein redundant mode, to the NIU boards on the RNC.

• ZQMF:OMU,,L:AA177:51,18,32:1,IPOAM:;

• In the above command line, 177 is the AA interface number, 18/32 are thedesignated VP/VC of the NIU interface , 1 is the encapsulation method(LLC/SNAP- always the same) , and IPOAM is the connection purpose(O&M –always the same).

• After creating the AA interface, we need to configure it as a point to point ATM interface, by attaching an IP address and a destination IP address:

• ZQRN:OMU:AA177,N:10.26.111.161,L:32:10.26.111.169:1544:UP:;

• For the above, 10.26.111.161 is the IP defined on the AA interface, while10.26.111.169 is the destination IP address . 1544 is the MTU (always thesame) , followed by the interface state ,UP .

• The last step in configuring the DCN is to configure a static route on theOMU for the IP subnet address assigned to the WBTS , with the AXC IP ofthe WBTS as the gateway point.

• ZQKC:OMU,0&&1:10.26.111.168,29:10.26.111.169:LOG::;



3.4 Config urat ion of COCO on RNC:

• Since the WBTS is build by default on the RNC for ATM transport, it is not

required to do any reconfigurations on it.

• All new ATM sites require however new COCO interfaces to be build.

• There are two ways this can be done, either create a new COCO , or useanother site with similar characteristics as reference.

• In order to successfully create the traffic descriptors for the new COCO, weneed the following information:

• Total number of logical cells that will exist on the site,

• Number of E1s in the sites transmission support,

• Type of physical interface on the RNC side.• Site ID

• NIU Interface ID

• Virtual Path ID



• If a WBTS with the exact same characteristics cant be found to use as

reference, the traffic descriptors have to be modified .

• In the Modify COCO window, go to the VP Termination Points tab:

• The Peak Cell Rate (PCR-egress) represents the maximum defined

bandwidth of the virtual path for the site . To find out the exact number ofE1s for this site, divide the PCR by 4481 (cells per one E1



The RNC interface type can be determined by the VP Max

Bandwidth.

In the given example, the bandwidth is 353207 cells,

which means the interface is SDH STM-1.



• To determine the new traffic descriptors of the COCO interface, use the

“Daily sheet” file, under tab “IUB v1.4”. Input the number of cells and E1

links of the site :



• Using the values in given in the above table, make the necessary

modifications to the COCO interface.

• Change CNBAP values and the Cell Delay Variation Time (CDVT) ( both

egress and ingress ).



• In the ALL2 User plane, modify PCR (ingress and egress) for the

DCHs and HSDPA channels

Also modify VCC Bundle Peak Cell Rate :



Create MSC Data

• To build the MSC data for the 3UK cells, the Global Cell ID is required, and

can be found in the RNC GUI interface.

The list with all MSCs and associated RNCs can be found in Data Sheet excel,

under the RNC Hosting tab.



• The HIT application for connecting to the MSC can be found under

Hutchison:

Connect to the target MSC:



• Build the new SACs with similar parameters to other 3UK cells from thesame WBTS. To find out those parameters , run the command:

• ZEPO:TYPE=SA,NO=<YYYY>; - where YYYY is that GCID

• Creating a new SAC:

• ZEPC:TYPE=SA,NAME=SAC0< XXXX>,NO=<YYYY>:LAC=<ZZ>;

• ZEPF:SANAME=SAC0< XXXX>,TYPE=SA:MGWNBR=MSS:LAC=<ZZ>;

• ZEPR:NAME=SAC0<ZZZZ>,TYPE=SA:RZ=<KKK>;

• ZEPS:TYPE=SA,NO=<YYYY >:U;



Update DNS:

• Open TLUI and select DNS Manager.



• Under the target RNC , select Add Host:

Fill in the WBTS ID using format <WBTSXXXX> , and the WBTS IP.



Build View

• Once the configuration of the site has been altered, the TLUI view needs to

be updated. This operation is done in two steps:

• Topology upload.

• Create RNC views and subviews.

• Topology Upload:

• Open Default view in TLUI:



Write in the command : “NE-RNC-XXX” , where XXX is the RNC ID (the

command is case sensitive).



Create RNC views and subviews:

• Once the topology has been uploaded , rebuild the RNC views.

• Under Default view select and right-click the target RNC icon.



Confirm activating the views:



Load Licenses

• Depending on the site hardware configuration, new licenses may need to be added or deleted.

• Licenses are required for the transmission submodule, system module , radio module , aerialsystem.

• Transmission licenses:

• 1)for Full IP support, no licenses are required.

• 2)for TDM support, we require:• One “IMA (FTM)”

• One “Additional 2 E1, T1, JT1 interface (FTM)” license for each two additional E1 in addition to thefirst one.

• One “UBR+ for IUB User Plane”

• System module licenses:

• For each FSMB 208 “Channel Capacity LK” licenses

• For each FSMD 396 “Channel Capacity LK” licenses

• For each FSME 612 “Channel Capacity LK” licenses

• Radio Module:

• One “Branch Activation LK” license for each active TX port (FRGF and FRGP only).

• One “Multi carrier LK” for each active TX port mapped with a second frequency.

• !Note! Maximum of 2 carriers for each Radio Module. FRGP is the only board with 3 carriersupport

• One “40W Power LK” for each active TX port mapped with a second frequency

• One “60W Power LK” for each active TX port mapped with a third frequency (FRGP only). • Aerial system:

• One “MHA Support LK” for each sector (WHMA, WMHB and WHMC only)

• One “MHA AISG Support LK” for each sector (WHMD only)



Miscellaneous:

One “16 QAM LK” for each site

One “PFRP Scheduler LK” for each site

One “Shared Scheduler LK” for each site

One “RX Signal Level Monitoring” for each site.



After selecting the appropriate license file , choose the site to which it

will be distributed by activating Find target NEs.



Select the target RNC, and confirm by pressing the “+” symbol at the top



• Choose WBTS , scroll down to the designated WBTS ID , select it by

activating the tick box and close the window.



• Type in the number of licenses , select Set and Distribute



Final alarm check :

• Once all the licences have been loaded and the site has been call tested you will

need to do a final alarm check.



• A site with no alarms should look like this:

Activating an ATM Site

Documents

Transcript of Activating an ATM Site