MPR Delta Training

8/6/2019 MPR Delta Training

1/81

All Rights Reserved Alcatel-Lucent 2006, #####

9500 MPR Delta TrainingRel 1.2 Rel 1.3

ASAP & AUX boards management

Alcatel-Lucent

April, 2010


2/81

All Rights Reserved Alcatel-Lucent 2006

Content

1. ATM networks An introduction.

2. ATM traffic management in 9500MPR.

3. ASAP board provisioning procedure.

4. AUX board Provisioning


3/81


ATM networks

An Introduction

1


4/81


1. ATM networks Introduction

1.1 Introduction

1.2 Frame structure

1.3 Switching in ATM networks

1.4 ATM protocol stack

1.5 ATM Traffic characterization

1.6 QoS parameters

1.7 ATM service categories


5/81


1. ATM networks Introduction

1.1 Introduction1.1 Introduction

1.2 Frame structure




1.6 QoS parameters



6/81


1.1. Introduction

ATM networking architecture is designed with a view to transmit Voice, Video and Data

traffic on the same network. Although these different types of traffic have differenttolerance levels for packet loss and end-to-end delay.

ATM networks are connection-oriented, andpacket-switchednetworks:- Connection-Oriented:As a connection must be established first between circuit ends(call-setup phase), before the exchange of information commences.

- Packet-switched:As the exchanged information is in the form of packets (Referred to asCELLs).

An ATM cell is of fixed length (53Bytes), containing 5 bytes of header and 48 bytes ofpayload.

Switching inside an ATM network is based on the circuit identifier (CI) information,

found in the cell header.

There is neither error control nor flow control between two adjacent ATM nodes.However, ATM cell header is protected in order to avoid forwarding the packet to thewrong destination


7/81


1. ATM networks Introduction1.1 Introduction

1.2 Frame structure1.2 Frame structure




1.6 QoS parameters



8/81


1.2. ATM frame structure

An ATM cell is of fixed length (53 Bytes), containing 5 header bytes and 48payload bytes.

Two slightly different formats for the cell header were adopted, for UNI and NNIcells.

UNI cells (User Network Interface) are the cells exchanged between an ATM end

device and anATM

switch. While NNI ce

lls (Network Network Interface) areexchanged between ATM switches belonging to the same network or two different

networks.


9/81


1.2. ATM frame structure Contd

The structure of an ATM NNI cell is described in the figure below:

Where:

VPI = Virtual Path Identifier.

VCI = Virtual Circuit Identifier.

PTI = Payload Type Indicator.

CLP = Cell Loss Priority

HEC = Header Error Control


10/81



VPI/VCI fields:

An ATM connection is identified by the combined Virtual Path IdentifierVPI and Virtual Circuit IdentifierVCI . Such a connection is referred to asVirtual Channel Connection VCC.

VPI field is 12 bits long in an NNI cell. Therefore, there can be a max of 4096virtual paths in an NNI interface.

VCI field is 16 bits

long, a

llowing a maximum of 65,535 virtua

lcircuits insidethe same virtual path.

The combined VPI and VCI allocated for a connection is known as the ConnectionIdentifier (CI) i.e. CI = {VPI, VCI}


11/81



PTI Field:

Payload Type indicatorField is used to indicate different types of payload;such as user date or OAM.

Its also used to notify that network congestion was experienced.

CLP Field:

Cell Loss PriorityField indicates whether the cell can be discarded whencongestion arises in the network.

HEC field:

Header Error Control is used for error detection and correction for the

header part of the cell only. (Correction is possible only in case of singleerror).

9-bit pattern CRC is used for detection and correction.


12/81



1.2 Frame structure

1.3 Switching in ATM networks1.3 Switching in ATM networks



1.6 QoS parameters



13/81


1.3. Switching in ATM networks A Virtual Channel Connection between end devices consists of a path through a number ofATM

switches.

For each point to point link along the path, the connection is identified by a different VPI/VCI

pair. i.e. VPI/VCI has local significance and is translated to a different VPI/VCI at each switch thecell traverses.

This VPI/VCI translation is performed by an ATM switch, this operation is also known as LabelSwapping.

VP18VP3

Port 1 Port 3

500

500

500500

500


14/81


1.3. Switching in ATM networks contd

The VPI/VCI translation involves a look-up in the switching table, in order for theswitch to determine what is the output port and new VPI/VCI to use beforeforwarding a received cell.

According to the example switching table shown:

An incoming cell at port 1, having VPI = 100 and VCI = 85, is forwarded to port 3,with a new VPI = 231 and a new VCI = 3.

While an incoming cell at the same port, but with VPI/VCI = 33/42, is forwarded toport 5 with new VPI/VCI = 54/95

Input Output

Port # VPI VCI Port # VPI VCI

1 100 85 3 231 3

1 33 42 5 54 95

ATM switching table Simplified example


15/81



1.2 Frame structure


1.4 ATM protocol stack1.4 ATM protocol stack


1.6 QoS parameters



16/81


1.4. ATM protocol stack

The ATM protocol stack consists of the following layers:

Physical Layer.

ATM Layer.

ATM adaptation layer (AAL)

Higher layers permitting various applications

to run on top ofATM, transmitting different traffic types.


17/81


1.4. ATM protocol stack Contd

The Physical Layer:

This layer maps cells to the transmission medium, it performs the followingFunctions:

1. Generation and verification of HEC.

2. Insertion of idle cells in case of no incoming traffic.

3. Timing function; generates timing for Tx cells, and derives timing from Rx cells.

4. Encoding and decoding of the bit stream (Block coding).

The ATMlayer:

Switching in ATM networks is performed by this layer, the most important functionsare:

1. Cell switching.

2. QoS management.

3. Congestion control.


18/81


1.4. ATM protocol stack Contd

The ATMAdaptation Layer:

This Layer converts the traffic generated by higher levellayers to suitable ATMpayload, to be further on delivered to destination by the ATMlayer.

SeveralAALs were defined according to the type of traffic to be sent, most importantis:

1. AAL-1: Used for circuit emulation services (CES), constant bit rate video, andhigh quality constant bit rate audio.

2. AAL-2: suitable for delay sensitive, low bit rate applications.3. AAL-5: The most popular AAL, used for transfer of data traffic.


19/81



1.2 Frame structure



1.5 ATM Traffic characterization1.5 ATM Traffic characterization

1.6 QoS parameters



20/81


1.5. ATM traffic characterization

The traffic submitted by an ATM source can be described by the following parameters:

Peak Cell Rate (PCR):

Is the max amount of traffic submitted by a source to the network (in cells/sec)

Sustained Cell Rate (SCR):

Is the Max average transmission rate of traffic submitted by the source (in cells/sec)

Minimum Cell Rate (MCR):

Is the min cell rate that must be guaranteed by the network for a given source. Maximum Burst Size (MBS):

For bursty sources, the max burst

size is the max number of cells that

can be submitted by the source @ PCR.


21/81



1.2 Frame structure




1.6 QoS parameters1.6 QoS parameters



22/81


1.6. QoS Parameters

Different parameters can be defined to express the QoS level of a connection.

During the call setup phase, values are set for the desired QoS parameters. The network

will accept the connection if it can guarantee these values throughout the whole path.

The standardized QoS parameters are described as follows:

Cell Loss Rate (CLR): Max allowed rate for cellloss. CLR is the most popular QoSparameter, as its easy to quantify.

Jitter: Is a very important QoS parameter in case of real time applications. It is used

to set an upper bound for the inter-arrival gaps between the received cells. Inter-arrival gaps (In case of real-time audio/video), if too large, might cause the play outprocess to pause.

CellTransfer Delay (CTD): Is the time it takes to transfer a cell end-to-end. CTD ismade up of a fixed component (Due to Txn medium propagation delay, switch

processing time, etc), and a variable component due to queuing delays insideswitches (Variable CTD is also refered to as Peak-to-peak cell delay variation).


23/81



1.2 Frame structure




1.6 QoS parameters

1.7 ATM service categories1.7 ATM service categories


24/81


1.7. ATM Service Categories

ATM service categories are classes of services carried over the ATM network.

Each service category is associated with a set of traffic parameters, and a set of QoSparameters.

Cells belonging to different service categories are treated differently inside the switchscheduler.

The service category of a connection is signaled at call setup phase.

Six ATM service categories were standardized by ATM forum: Constant Bit Rate (CBR), Real

time Variable Bit Rate (RT-VBR), Non RealTime Variable Bit Rate (NRT-VBR), UnspecifiedBit Rate (UBR), Available Bit Rate (ABR), and Guaranteed Frame Rate (GFR).

To define a service category during call setup phase, two mandatory pieces of informationmust be supplied:

A description for the traffic parameters (e.g. whats the PCR, the SCR, etc)

A description for the required QoS parameters.

Supplying this info, leads to a settlement of an agreement (a contract) between the network and thesource. To be respected by both parties throughout the transmission period.

Any of the above service categories can be used with any ATMAdaptation Layer (There isno restriction).


25/81


1.7. ATM Service Categories Contd

Constant Bit Rate service (CBR) :

This service is intended for real time applications transmitting at constant bit ratelike circuit emulation services (CES), and constant bit rate audio or video.

Required traffic parameters for contract: PCR and CDVT.

Required QoS parameters: CLR, peak-to-peak cell delay variation, and Max CTD.

Real time Variable Bit Rate service (RT-VBR):

This service is intended for real time applications that transmit at variable bit rate.Like encoded video and encoded voice.

PCR, MBS, CDVT, and SCR are needed to characterize this VBR traffic.

QoS parameters needed: CLR, peak-to-peak cell delay variation, and Max CTD.


26/81



Non RealTime Variable Bit Rate service (NRT-VBR) :

This service is intended for non-real time applications that transmit at variable bitrate.

PCR, MBS, CDVT, and SCR are needed to characterize this VBR traffic.

QoS parameters needed: only CLR (As the transmitting aplication is non-real time,there are no constrains on delay).

Unspecified Bit Rate service (UBR):

This is a BEST EFFORT type of service intended for data transfer application like filetransfer and web browsing.

No traffic descriptors nor QoS parameters required, as (if defined) they can beignored by the network.


27/81



UBR + MDCR (UBR+):

This service is the same as UBR but adding a Minimum Desired Cell Rate that thenetwork commits to transmit.

PCR, and MDCR are required to characterize the traffic.


28/81


ATM ManagementIn 9500 MPR

2


29/81


1. ATM management in 9500MPR2.1 The physical layer (What is IMA?)

2.2 Pseudo wire emulation (What is a PWE3?)

2.3 Policing and Shaping

2.4 Supported service categories


30/81


1. ATM management in 9500MPR2.1 The physical layer (What is IMA?)2.1 The physical layer (What is IMA?)

2.2 Pseudo wire emulation (What is a PWE3?)




31/81


2.1. The Physical Layer (IMA)

ATM cells can be carried over several physical interfaces (e.g SONET, DS3, 100Mbps

multimode fiber, etc

)

9500MPR uses IMA protocol (Inverse Multiplexing ofATM) to interface ATM traffic.

IMA protocol is based on the multiplexing ofATM cells over several physicallinks to form ahigher capacity logicallink.

Multiplexing ofATM cells is performed in a cyclic way (Round Robin).

Physicallinks used are E1 links.

PHY

PHY

PHY

PHY

PHY

PHY

Physical Link #0

Physical Link #1

Physical Link #2

IMA Virtual Link

ATM Cell

Stream fromATM Layer

Original Cell

Stream Passedto ATM Layer

IMA Group IMA GroupATM end device

e.g. NodeB

9500 MPR

ASAP board


32/81


ASAP board

9500MPR

2.1. The Physical Layer (IMA) contd

In 9500 MPR, an IMA interface can support up to 8 E1 links.

ASAP board can manage up to 8 IMA groups.

An IMA E1 link carries around 4490 cells/sec.

Example:

Two ATM end devices are interfaced to 9500MPRASAP board using 2 IMA groups.

IMA group #1 interfacing device A is composed of 3 E1 links.

IMA

group #2 interfacing deviceB is composed of 2 E1

links.

VCVCVCVCVCVCVCVP2x E1VP

VCVCVCVCVCVCVC

VC

VCVC

VC

VCVC

VCVP3x E1VPVC

VCVC

VC

VCVC

VC

Device B

Device A

Max 8980 cells/sec

Max 13440 cells/sec


33/81



22..22 Pseudo Wire Emulation (What is a PWEPseudo Wire Emulation (What is a PWE33?)?)




34/81


2.2. Pseudo Wire Emulation (PWE3)

Pseudo Wire Edge-to-Edge Emulation (PWE3) is a mechanism to carry emulated services

such asATM

orTDM

over a packet switched network (PSN). Connecting two provider edgestogether.

PWE3 is a Layer two VPN between end points over the PSN.

PWE3 PSNPWE3

PWE3

CES

CESCES ATM

ATM

ATM

CES

ATM


35/81


2.2. Pseudo Wire Emulation (PWE3) contd

As 9500 MPR is a packet based equipment, ASAP board performs the Circuit Emulation for

incomingATM

cells via

MPLS encapsu

lation to make it suitab

le for transmission over thePSN (Via radio port or Ethernet aggregation).

Ingress and Egress VPI/VCI translation is performed by ASAP board (If needed) during thePWE3 creation.

Each ATM PW is identified by a separate VLAN ID.

PSNATM

Core-E

ASAPGbE

PWE3

MD300GbE

GbE on Core-E


36/81



2.2 Pseudo Wire Emulation (What is a PWE3?)

2.3 Policing and Shaping2.3 Policing and Shaping



37/81


2.3. Policing and Shaping

Policing and Shaping are QoS components controlling the amount of traffic received andtransmitted on an ATM interface; ensuring the conformity of the traffic to the connectiontraffic contract

Ingress Policing:

Before forwarding the ATM cells to circuit emulation block, ASAP board may performpolicing on the incoming traffic to ensure that the transmitting ATM source is

respecting the traffic contract of the connection.

The resulting traffic (Policed) is used for pseudo wire creation, and aggregation overa radio or Ethernet link.


38/81


2.3. Policing and Shaping contd

Egress Shaping:

Before forwarding the ATM cells to the receiving ATM device, ASAP board may applytraffic shaping to the egress traffic, to ensure that the output traffic from MPR isrespecting the traffic contract of the connection.

Egress Shaping is based on the leaky bucket mechanism. The yellow cells represent shaped traffic, while red cells correspond to traffic that

couldnt be shaped due to buffer overflow.


39/81



2.2 Pseudo Wire Emulation (What is a PWE3?)


22..44 Supported service categoriesSupported service categories


40/81


2.4. Supported service categories

9500MPR supports the following service categories:

CBR : Constant Bit Rate service. The Commit Information Rate (CIR) for this service isequal to the defined PCR of the connection.

UBR : Unspecified Bit Rate service (Best effort). CIR = 0.

UBR+ : UBR with a Minimum Desired Cell Rate (MDCR) (CIR = MDCR).


41/81


ASAP board provisioning

3


42/81


3. ASAP board provisioning

3.1 Introduction to ASAP

3.2 Provisioning phases

3.3 Creating Traffic descriptors

3.4 The E1 Layer

3.5 The IMA Layer

3.6 The ATM Layer

3.7 The PW layer

3.8 PW Cross-Connection


43/81



33..11 Introduction to ASAPIntroduction to ASAP



3.4 The E1 Layer

3.5 The IMA Layer

3.6 The ATM Layer

3.7 The PW layer



44/81


3.1. Introduction to ASAP

ASAP board performs MPLS encapsulation for the incoming

ATM cells producing pseudo wires (PWE3).

The resulting PWE3 are then forwarded to the Main and Spare

Core-E boards to connect them to the aggregation port

(Radio or Ethernet).

During MPLS encapsulation, ASAP board performs

VPI/VCI translation (If needed).

ASAP board accepts only the configured connection

(Predefined VPI and VCI) respecting the traffic contracts.

16 E1 ports are available on the ASAP board

front plate, constituting up to 8 IMA interfaces.


45/81




33..22 Provisioning phasesProvisioning phases


3.4 The E1 Layer

3.5 The IMA Layer

3.6 The ATM Layer

3.7 The PW layer



46/81


47/81





33..33 Creating Traffic descriptorsCreating Traffic descriptors

3.4 The E1 Layer

3.5 The IMA Layer

3.6 The ATM Layer

3.7 The PW layer



48/81


3.3. Creating Traffic Descriptors

To open the traffic descriptors view, go Configuration Traffic descriptors.


49/81


3.3. Creating Traffic Descriptors contd


50/81


3.3. Creating Traffic Descriptors Contd

Example: an ATM interface is carrying the following connections:

VPI/VCI = 1/32, CBR source, PCR = 4000C/S, CDVT = 1000uS.VPI/VCI = 1/33, UBR+ source, PCR = 7000C/S, MDCR = 2000C/S, CDVT = 1000uS.

VPI/VCI = 1/34, UBR source, PCR = 9000C/S.

VPI = 2, CBR source, PCR = 151C/S.

Note that VP 1 contains VCI 32, 33 and 34. The amount of guaranteed traffic inside this VP =

sum of guaranteed traffic inside VCs (4000 + 2000).

VP 1 can be considered as a UBR+ pipe with MDCR 6000C/S and PCR = 20000C/S.

A traffic contract is created for VP1, VC32, VC33, VC34 and VP2 as follows.


51/81






33..44 The EThe E11 LayerLayer

3.5 The IMA Layer

3.6 The ATM Layer

3.7 The PW layer



52/81


3.4. The E1 Layer

To start provisioning layers, double click on the ASAP board to open the ASAP main view:


53/81


3.4. The E1 Layer contd

On the ASAP main view, choose the E1 layer tab


54/81


3.4. The E1 Layer Contd

Back to our Example: The max amount of traffic submitted to this interface (According to the

last example) is 20000 cells. With each E1 IMA link carrying around 4000 C/S, this interface

must have 5 E1 links.

On E1 Layer, five E1 ports are enabled, and timing mode is determined depending on the

location of the interface (e.g node timed @ NodeB side, and Loop timed @ RNC side).


55/81






3.4 The E1 Layer

3.5 The IMA Layer3.5 The IMA Layer

3.6 The ATM Layer

3.7 The PW layer



56/81


3.5. The IMA Layer

Move on to the IMA Layer tab, and associate the 5 E1s (Enabled in E1 Layer) to group#01.


57/81






3.4 The E1 Layer

3.5 The IMA Layer

3.6 The ATM Layer3.6 The ATM Layer

3.7 The PW layer



58/81


3.6. The ATM Layer

Move on to the ATMLayer tab, and create required VPs.


59/81


3.6. The ATM Layer

The VP Layer configuration opens.

Input the VP ID in the first field.

Choose the VP role:

Logical: If further VCs to be created.

NotLogical: If no VCs to be created.


60/81


3.6. The ATM Layer contd

Associate a TD by clickingBrowse

(Choose one of the previously createdT

Dsdescribing the traffic flowing over this VP).

In our example, VP 1 is Logical, associated to TD 1, while VP 2 is NotLogical and associated

to a differentTD 2..


61/81


3.6. The ATM Layer contd

Once a Logical VP is created, select it

and press Create VC in the VC Layerconfiguration Area.

Proceed with VC creation, just like VP creation. Associating the appropriate traffic descriptors

for each VC. (Must be created in advance from the TD configuration view)

In our example, VP1 contains

VCs 32, 33, and 34.

Traffic descriptors were created

in advance to describe the traffic

flowing on these VCs.


62/81






3.4 The E1 Layer

3.5 The IMA Layer

3.6 The ATM Layer

33..77 The PW layerThe PW layer



63/81


3.7. The PWE3 Layer

Move on to ATMPWLayer, and create PWE3s.


64/81


3.7. The PWE3 Layer contd

In our Example, 4 connection exist on interface#1; namely VPI/VCI 1/32, 1/33, 1/34 and VPI 2.

One PWE3 must be created for each of these connections. Here PWE3 labels are 132, 133,

134 and 20 respectively.

No VPI/VCI translation is required. (Note that Egress and Ingress VPI/VCI are the same).

The only remaining step is to cross-connect these PWE3s to the radio (Or to an Ethernet port

on Core-E).


65/81






3.4 The E1 Layer

3.5 The IMA Layer

3.6 The ATM Layer

3.7 The PW layer

33..88 PW CrossPW Cross--ConnectionConnection


66/81


3.8. PWE3 Cross-Connection From Cross-connection view, cross-connect PWE3 from ASAP to Radio or Ethernet port


67/81


3.8. PWE3 cross connection contd A new window will open to complete the cross-connection operation.


68/81


3.8. PWE3 Cross-Connection Contd Other PWE3 cross-connection types:

The PWE3 cross connection covered ion our example is an ASAP - Radio cross connection.

Three other PW cross-connection types are supported:

1. ASAP Ethernet:

To connect the Pseudo Wire to an Ethernet port on Core-E for service aggregation

2. Radio Ethernet:

To connect PWE3 coming from radio to an Ethernet port on Core-E board.

3. Radio Radio:

To connect PWE3 between different radio directions, without the need of a local ASAP board (ATMrepeater site)


69/81


AUX board Provisioning

4


70/81


4. AUX Board Provisioning

4.1 Introduction to AUX board

4.2 Provisioning Procedure

4.2.1 Configuring Service Channels

4.2.2 Configuring H/K Alarms


71/81



44..11 Introduction to AUX boardIntroduction to AUX board


4.2.1 Configuring Service Channels.

4.2.2 Configuring H/K alarms.


72/81



AUXboard provide access for two service channels, HousekeepingAlarms and

EOW. Four connectors can be found on the front plate ofAUXboard as described in the

below figure:

Each EngineeringService Channel connector (ESC-1 and ESC-2) interface one

Synchronous 64Kbps RS422/V11 DCE co-directional channels for radio transport.

Three radio service channels (Out band) are available for cross-connection of local

service channels on AUXboard.

Housekeeping alarms connector supports 6 Input and 7Output alarms.

EOW voice channel is not supported in this release.

Status LED:

Off = Card not powered or notconfigured.

Green Blinking = SW download/bootingor Flash card alignment in progress.

Green = In service.

Red = Card fail.

Red blinking = Card mismatch.


73/81


4.1 Introduction to AUX board contd Like all other 9500MPR boards, the main function of an AUXcard is to transform the incoming

Service channels and H/K alarm into a format suitable for transmission to the CORE-E board

via the GbE interface on the back plan. Data coming from the AUXboard is then processed and cross-connected by the CORE-E to

the appropriate radio port.

AUXboard is allowed to be inserted only in slot-8 in an MSS-8 orSlot-4 in an MSS-4 chassis.


74/81




44..22 Provisioning ProcedureProvisioning Procedure

44..22..11 Configuring Service ChannelsConfiguring Service Channels

4.2.2 Configuring H/K Alarms.


75/81


4.2.1 Configuring Service Channels To access AUXboard configuration view, double click on the AUXboard in Equipment

view.

Service Channels provisioning is performed in two steps:

1. Define the operational ESC ports (Enable / Disable).

2. Cross-connect the configured ports to the appropriate radio channel.


76/81


4.2.1 Configuring Service Channels Contd In resultingAUXboard configuration view, Settings tab, configure ESC ports as described

below:


77/81


4.2.1 Configuring Service Channels Contd Cross-connect the configured ports to the appropriate radio port as follows:

** Possible TP combinations are:

1. Radio port Radio port

Where a pass-through connection is

performed between different radio directions

2. Radio port ESC port

Where a radio service channel is connected

to an ES

C port onAUX

board


78/81





4.2.1 Configuring Service Channels

44..22..22 Configuring H/KAlarms.Configuring H/KAlarms.

f l


79/81


4.2.2 Configuring H/K alarms On AUXboard provisioning view, select the External points tab.

Configure input alarms as follows:

4 2 2 C fi i H/K l


80/81


4.2.2 Configuring H/K alarms Configure Output alarms as follows:


81/81

End Of TrainingThanks for your attention

WWW.ALCATEL-LUCENT.COM

Date post:	07-Apr-2018
Category:	Documents
Upload:	iqbal-rashid-khan
View:	225 times
Download:	0 times

MPR Delta Training

Documents