Routing Over Ericsson Mini-Link

Routing Over Ericsson Mini-Link

Presented by : Eng Ahmed Mohammed Nabieh Supervised by : Eng Amr Abdelkreem

Agenda

• Introduction

• TN Units

• Connecting to the Mini-link

• Traffic Routing

Introduction

• Ericsson Mini link IDUs can be categorized into two main categories :

1)Compaq Node (CN) 2) Traffic Node (TN)

Compaq Node (CN)

Compaq Node (CN)

• Pros

1)low cost 2)small size • Cons

1)small capacity up to 8 E1s only

2) Not modular ,in case of HW failure the whole IDU should be replaced

3)support 1+0 Configuration only • Best suitable for end point sites.

Traffic Node (TN)

• TN can be categorized based on their Access module

magazine (AMM) to 20P and 6P where p refer to the number of Units that can be fitted inside the AMM.

• Unlike the CN the TN operation is based on Units(Modules) where every unit do a certain function and all of them are connected through the backplane of the AMM .

Traffic Node (TN)

• We use TN 6P-C and TN 20P-B at Mobinil

Traffic Node (TN-6P)

• Pros

1)Average cost

2)Reasonable Size 3)Modular 4)SW Cross connection availability • Cons

1)Support up to 5 sites only

Traffic Node (TN-20P)

• Pros

1)High Capacity up to 19 sites 2)Modular

3)Cross connection availability • Cons

1)High Cost 2)Large Size • Best suitable for Nodal sites & BSCs.

TN Units

• Access Module Magazine(AMM)

• Network Processing unit (NPU)

• Power Filtering Units (PFU)

• Fan Unit (FAU)

• Line Termination unit (LTU)

TN Units

• TN units can be categorized based on their Size to

Full Width Module

Access Module Magazine

• Connect all the units together through its Backplane. • Backplane has two buses

Traffic Bus which carries the normal traffic between the MMUs and LTU for example and Control Bus used by the NPU to

Network Processing Unit(NPU)

• Holds the TN configuration on Non volatile Memory.

• Control the TN operation through the control BUS in the backplane

• O&M interface for local Maintenance

• E1 & T1 Interfaces up to 4E1s for HW unit and 8E1S FOR FW unit.

• DCN and management interfaces. • Mandatory Unit.

Power Filtering Unit (PFU)

Power Filtering Unit (PFU)

• Can operate over +24 v or -48 v.

• SC protection and DC ripples Smoothing.

• Can be used with another one for redundancy (Protection). • Mandatory Unit.

Fan Unit (FAU)

FAU1 Used in 20p AMM

FAU2 Used in 6p AMM

Air In Air out

Fan Unit (FAU)

• Direct the air flow throughout the AMM

• FAU1 is not inserted in the 20 p AMM ,it is installed above the AMM hence it has a power socket and alarm socket to be

connected to the AMM PFU .

• Consists of 3 blowers for redundancy against equipment failure.

• power can be supplied from two different two PFU redundancy against power supply failure.

Line Termination unit (LTU)

PDH LTU _{SDH LTU}

LTU 155 e LTU 155 e/0

Line Termination unit (LTU)

• Can be either FW or HW depending on the AMM i.e. FW is usually used in the 20p AMM while the HW is usually used in the 6p AMM.

• Optional Unit

• Usually installed in slot 13 or 17 in the 20p AMM ,Slot 6 in the 6p AMM.

Magazine Modem Unit (MMU)

MMU2D

Magazine Modem Unit (MMU)

• Modulate the signal from the Base band to IF Band and vice versa.

• Supply DC power to the RAU (ODU)

• Determine the Link Modulation scheme and Bandwidth.

• Both MMU2H & 2D support modulation up to 128 QAM ,they also support adaptive modulation(Lowering the modulation scheme to became more robust against fading)

• Only MMU2H supports XPIC . • Mandatory Unit.

Connecting to the Mini-Link

• We can connect to Ericsson MW IDU [6P & TNP] using either a USB cable or an Ethernet cable.

• in case of CN-210 we can connect using Ethernet cable only .

• Each IDU has its own IP ,so the IP used in the below example is just for illustration purpose.

• You must assign the Laptop IP within the range of the network of the IDU to be able to connect properly to it.

Example on Configuring the laptop TCP/IP

If the IDU TCP/IP Configuration is as shown :

IP :10.159.106.121

Subnet : 255.255.255.248

Configure the NIC as shown

IP : 10.159.106.122

Subnet : 255.255.255.248 DGW: 10.159.106.121

Identifying the right port

• CN-210

Identifying the right port

• TN-20P

• We connect through the NPU located in slot 11.

TR7/LAN Interface O&M USB Interface

Identifying the right port

• TN-6P

• We connect through the NPU located in slot 7.

TR2/LAN Interface

Starting the SW

• Open Ericsson Mini-Link SW and choose IP from show NE as . • Username : control_user

• Password : ericsson

Traffic Routing

• Hub sites have usually been built by connecting individual microwave Radio Terminals with cables through Digital

Distribution Frames (DDF) and external cross connection to equipment.

• MINI-LINK TN provides a traffic routing function that

facilitates the handling of traffic aggregation. This function enables interconnection of all traffic connections going

through the NE. This means that an aggregation site can be realized using one AMM housing several Radio Terminals with all the cross-connections done in the backplane.

Traffic

Routing

• Interface (LTU and NPU) E1s on Ericsson Mini-Link are identified by a Number then a letter.

• Letters are A,B,C & D. • Numbers from 1 to 8 .

• If we combine them together we can have up to 32 E1.

1 2 3 4 5 6 …. 30 31 32

Traffic

Routing

• In SW cross connection: all the plug in cards are defined according to the Node /Slot/E1 port.

• Example the 3rd _{E1 on the NPU of TN-20P will be written as}

1/11/1C another example of 6th _{E1 of the NPU of TN-6P will}

be written as 1/7/2B. Node

E1

Traffic Routing

• Right click on the site name and choose Configure -> Traffic Routing

Choose the MMU card in interface 1

then choose E1 1/11/6

Traffic Routing

• Example if a new site to be routed from the BSC and we need to connect 1A on the LTU located in slot 12 to the 6th _{E1 of the}

MMU located in slot 10.

Choose the LTU card in interface 2

then choose E1 1/12/1A

Press the arrow button to create

the cross connection

Traffic Routing

• Naming the cross connection

Click on Traffic routing overview

Traffic Routing

• Naming the cross connection

Left click on the E1 name

Link Performance Measurements

• Every 15 minutes the Link record the values of the below 1)BB (Background block) : blocks of data RX by the link

2)BBE : # of blocks that contain errors and can not be corrected 3)BBER : # of BBE / interval(Day or 15 minutes)

4)ES( Error Seconds) : # of seconds of incorrect(corrupted) data 5)ESR(Error second rate) : # of ES / interval(Day or 15 minutes)

6)SES (Severe error seconds) : 10 seconds or more of incorrect data 7)SESR : # of SESR / interval(Day or 15 minutes)

8)Unavailable Seconds : more than 30 % of the data sent per this second has error i.e. data discarded by the link

Link Performance Measurements

• Every 15 minutes the Link records the values of the below 1)BB (Background block) : blocks of data RX by the link 2)BBE : # of blocks that contain errors and can not be

corrected

3)BBER : # of BBE / interval(Day or 15 minutes)

Link Performance Measurements

4)ES( Error Seconds) : # of seconds of incorrect(corrupted) data

5)ESR(Error second rate) : # of ES / interval(Day or 15 minutes).

6)SES (Severe error seconds) : 10 seconds or more of incorrect data.

7)SESR : # of SESR / interval(Day or 15 minutes)

8)Unavailable Seconds : more than 30 % of the data sent per this second has error i.e. data discarded by the link

LPF OVER CN

• Right click on Radio and choose performance to check the LPF for the near end over the current and previous 15 minutes

and current and last day.

LPF OVER CN

• Click on continuous to check the LPF for Near and Far ends since the startup of the link

LPF OVER CN

• Click on RF to check the current RSL for the near end and over the last 7 days and since startup.

LPF OVER CN

• Click on Adaptive modulation to check the modulation

scheme used by link over the current and previous 15 minutes /day

LPF OVER TN

LPF OVER TN

the last 7 days and since startup.