134659455 MPR Delta Training

8/10/2019 134659455 MPR Delta Training

http://slidepdf.com/reader/full/134659455-mpr-delta-training 1/81

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

9500 MPR Delta Training

Rel 1.2 Rel 1.3

ASAP & AUX boards management

Alcatel-Lucent

April, 2010



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




ATM networks An Introduction

1




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





1.1 Introduction

1.2 Frame structure




1.6 QoS parameters





1.1. Introduction

ATM networking architecture is designed with a view to transmit Voice, Video and Datatraffic on the same network. Although these different types of traffic have different

tolerance levels for packet loss and end-to-end delay.

ATM networks are connection-oriented , and packet-switched networks:- 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 as

CELLs).

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





1.1 Introduction

1.2 Frame structure




1.6 QoS parameters





1.2. ATM frame structure

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

payload 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 enddevice and an ATM switch. While NNI cells (Network Network Interface) areexchanged between ATM switches belonging to the same network or two differentnetworks.




1.2. ATM frame structure Cont’d

• 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 PriorityHEC = Header Error Control





• VPI/VCI fields:

•

An ATM connection is identified by the combined Virtual Path Identifier“ VPI ” and Virtual Circuit Identifier “ VCI ” . 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, allowing a maximum of 65,535 virtual circuits inside

the same virtual path.

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





• PTI Field:

•

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

• It’s also used to notify that network congestion was experienced.

• CLP Field:

• Cell Loss Priority Field 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.





1.1 Introduction

1.2 Frame structure




1.6 QoS parameters





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

For each point to point link along the path, the connection is identified by a different VPI/VCIpair. i.e. VPI/VCI has local significance and is translated to a different VPI/VCI at each switch the

cell 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




1.3. Switching in ATM networks cont’d

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 before

forwarding 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





1.1 Introduction

1.2 Frame structure




1.6 QoS parameters





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 of ATM, transmitting different traffic types.




1.4. ATM protocol stack Cont’d

The Physical Layer:

This layer maps cells to the transmission medium, it performs the following

Functions:

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 ATM layer:

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

1. Cell switching.

2. QoS management.3. Congestion control.




1.4. ATM protocol stack Cont’d

The ATM Adaptation Layer:

This Layer converts the traffic generated by higher level layers to suitable ATM

payload, to be further on delivered to destination by the ATM layer.

Several AALs 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.





1.1 Introduction

1.2 Frame structure




1.6 QoS parameters





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.





1.1 Introduction

1.2 Frame structure




1.6 QoS parameters





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 cell loss. CLR is the most popular QoSparameter, as it’s easy to quantify.

Jitter: Is a very important QoS parameter in case of real time applications. It is usedto 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.

Cell Transfer 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, switchprocessing time, etc…), and a variable component due to queuing delays insideswitches… (Variable CTD is also refered to as Peak-to-peak cell delay variation).





1.1 Introduction

1.2 Frame structure




1.6 QoS parameters





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 QoS

parameters.

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), Realtime Variable Bit Rate (RT-VBR), Non Real Time Variable Bit Rate (NRT-VBR), Unspecified

Bit 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. what’s 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 ATM Adaptation Layer (There isno restriction).




1.7. ATM Service Categories Cont’d

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.





Non Real Time Variable Bit Rate service (NRT-VBR) :

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

rate.

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 file

transfer and web browsing.

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





UBR + MDCR (UBR+):

This service is the same as UBR but adding a Minimum Desired Cell Rate that the

network commits to transmit.

PCR, and MDCR are required to characterize the traffic.




ATM Management In 9500 MPR

2




1. ATM management in 9500MPR

2.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






2.2 Pseudo wire emulation (What is a PWE3?)






2.1. The Physical Layer (IMA)

ATM cells can be carried over several physical interfaces (e.g SONET, DS3, 100Mbpsmultimode fiber, etc…)

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

IMA protocol is based on the multiplexing of ATM cells over several physical links to form ahigher capacity logical link.

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

Physical links 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




ASAP board

9500MPR

2.1. The Physical Layer (IMA) cont’d

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 9500MPR ASAP board using 2 IMA groups.

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

IMA group #2 interfacing device ‘ B’ 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






2.2 Pseudo Wire Emulation (What is a PWE3?)






2.2. Pseudo Wire Emulation (PWE3)

Pseudo Wire Edge-to-Edge Emulation (PWE3) is a mechanism to carry emulated servicessuch as ATM or TDM over a packet switched network (PSN). Connecting two provider edges

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

PWE3 PSNPWE3

PWE3

CES

CESCES ATM

ATM

ATM

CES

ATM




2.2. Pseudo Wire Emulation (PWE3) cont’d

As 9500 MPR is a packet based equipment, ASAP board performs the Circuit Emulation forincoming ATM cells via MPLS encapsulation to make it suitable for transmission over the

PSN (Via radio port or Ethernet aggregation). Ingress and Egress VPI/VCI translation is performed by ASAP board (If needed) during the

PWE3 creation.

Each ATM PW is identified by a separate VLAN ID.

PSNATM

Core-E

ASAPGbE

PWE3

MD300GbE

GbE on Core-E






2.2 Pseudo Wire Emulation (What is a PWE3?)






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 connection

traffic 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 isrespecting the traffic contract of the connection.

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




2.3. Policing and Shaping cont’d

Egress Shaping:

Before forwarding the ATM cells to the receiving ATM device, ASAP board may apply

traffic 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

couldn’t be shaped due to buffer overflow.




2.4. Supported service categories

9500MPR supports the following service categories:

CBR : Constant Bit Rate service. The Commit Information Rate (CIR) for this service is

equal 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).




ASAP board provisioning3




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








3.4 The E1 Layer

3.5 The IMA Layer

3.6 The ATM Layer

3.7 The PW layer





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.








3.4 The E1 Layer

3.5 The IMA Layer

3.6 The ATM Layer

3.7 The PW layer





3.2. Provisioning phases To provision the ASAP board, one should pass through the following phases:

1. Creating Traffic Descriptors (TD):

Defining traffic contracts that will be associated to each ATM connection.

2. Configuring the E1 Layer:

Choosing the active E1 ports to be used, as well as the timing mode of each link.

3. Configuring the IMA Layer:

In this phase we define how many IMA groups/Interfaces are used, how many links

inside each interface, and which physical E1 ports are associated with each IMAgroup.

4. Configuring the ATM Layer:

Once IMA interfaces are defined, we need to inform the ASAP about the expected

VP’s and VC’s on each interface, as well as the amount of traffic and class of

service expected on each VP and VC (Using the TD’s created in phase 1).

5. Configuring the PWE3 Layer:

In this phase, the PWE3 are created for each VP/VC.

6. PWE3 Cross-connection:

Cross-Connecting the created PWE3’s to an Ethernet port or to a radio link.

It’s also possible to connect PWE3 between radio directions without having local ASAP board (ATM

repeater sites)








3.4 The E1 Layer

3.5 The IMA Layer

3.6 The ATM Layer

3.7 The PW layer





3.3. Creating Traffic Descriptors

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




3.3. Creating Traffic Descriptors Cont’d

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.








3.4 The E1 Layer

3.5 The IMA Layer

3.6 The ATM Layer

3.7 The PW layer





3.4. The E1 Layer

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




3.4. The E1 Layer cont’d

On the ASAP main view, choose the E1 layer tab

h




3.4. The E1 Layer Cont’d

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).








3.4 The E1 Layer

3.5 The IMA Layer

3.6 The ATM Layer

3.7 The PW layer


3 5 Th IMA L




3.5. The IMA Layer

Move on to th e IMA Layer tab, and ass oci ate the 5 E1s (Enabled in E1 Layer) to gro up#01.








3.4 The E1 Layer

3.5 The IMA Layer

3.6 The ATM Layer

3.7 The PW layer




3 6 Th ATM L




3.6. The ATM Layer

The VP Layer co nf igurat ion opens.

Input th e VP ID in the firs t f ield.

Choos e the VP role:

Log ical: If furth er VCs to be created.

NotLo gic al: If no VCs to b e created.

3 6 Th ATM L




3.6. The ATM Layer cont’d

Ass ociate a TD by cl ickin g Brows e

(Choose one of the previously created TD’s

descr ib ing the traf fic f low ing ov er th is VP).

In our examp le, VP 1 is Log ical, ass oci ated to TD 1, wh ile VP 2 is NotLog ical and asso ciated

to a di fferent TD 2..

3 6 Th ATM L




3.6. The ATM Layer cont’d

Once a Logical VP is created, select it

and pr ess Create VC in th e VC Layer

conf igu rat ion Area.

Proceed w ith VC c reat ion, just l ike VP creat ion. Ass ociat ing the appro pr iate traf f ic descr iptors

for each VC. (Must be c reated in advance from the TD conf igurat ion v iew)

In our example, VP1 con tains

VCs 32, 33, and 34.

Traf fic d escr iptors were created

in advance to descr ibe the traf fic

f lowing on these VCs.








3.4 The E1 Layer

3.5 The IMA Layer

3.6 The ATM Layer

3.7 The PW layer


3 7 The PWE3 Layer




3.7. The PWE3 Layer

Move o n to ATMPWLayer, and create PWE3s.

3 7 The PWE3 Layer




3.7. The PWE3 Layer cont’d

In our Examp le, 4 con nectio n exis t on interface#1; namely VPI/VCI 1/32, 1/33, 1/34 and VPI 2.

One PWE3 must be created for each of th ese con nectio ns. Here PWE3 labels are 132, 133,

134 and 20 respectiv ely.

No VPI/VCI translat ion is requir ed. (Note that Egr ess and Ingress VPI/VCI are the same).

The only r emaining step is to cros s-connect these PWE3s to the radio (Or to an Ethernet port

on Co re-E).








3.4 The E1 Layer

3.5 The IMA Layer

3.6 The ATM Layer

3.7 The PW layer


3 8 PWE3 Cross Connection




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



3 8 PWE3 Cross Connection C ’d




3.8. PWE3 Cross-Connection Cont’d

Other PWE3 cross-connect ion types:

The PWE3 cross conn ect ion covered ion our example is an ASAP - Radio cross connect ion.

Three other PW cross -connection typ es are sup ported:

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 (ATM

repeater site)




AUX board Provisioning4




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







4.2.1 Configuring Service Channels.

4.2.2 Configuring H/K alarms.

4 1 Introduction to AUX board





AUX board provid e access for two s ervice channels, Housekeeping Alarms and

EOW.

Four co nnectors c an be found on the front plate of AUX board as descr ibed in the

below f igure:

Each Eng ineering Servic e Channel conn ector (ESC-1 and ESC-2) interface one

Synchro nous 64Kbps RS422/V11 DCE co-direct ional channels for radio transpo rt .

Three radio service channels (Out band) are avai lable for cr oss -connect ion of lo cal

service channels on AUX board.

Housekeeping alarms conn ector suppo rts 6 Input and 7 Output alarms.

EOW vo ice channel is not s uppo rted in th is 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.

4 1 Introduction to AUX board cont’d




4.1 Introduction to AUX board cont’d

Like al l other 9500MPR boards, the main funct ion of an AUX card is to transform the incom ing

Service channels and H/K alarm into a form at suitable for transm ission to the CORE-E board

via the GbE interface on the back p lan.

Data com ing from the AUX board is then pr ocessed and cros s-connected by the CORE-E to

the appropr iate radio p ort .

AUX board is al low ed to be inserted only in slot-8 in an MSS-8 or Slot-4 in an MSS-4 chassis .








4.2.2 Configuring H/K Alarms.

4 2 1 Configuring Service Channels




4.2.1 Configuring Service Channels To access AUX board conf igurat ion view, doub le cl ick on the AUX board in Equipm ent

view.

Service Channels provis ioning is perform ed in two s teps:

1 . Def ine the operat iona l ESC por ts (Enab le / D isable).

2 . Cross-connec t the con f igu red port s to the approp r ia te rad io channel .

4 2 1 Configuring Service Channels Cont’d




4.2.1 Configuring Service Channels Cont d

In result ing AUX board c onf igurat ion v iew, Sett ings tab, conf igure ESC ports as descr ibed

be low:

4 2 1 Configuring Service Channels Cont’d




4.2.1 Configuring Service Channels Cont d

Cross-conn ect the conf igu red ports to the approp r iate radio port as fol lows :

** Possib le TP combinat ions are:

1. Rad io po rt Radio p ort

Where a pass- through con nect ion is

perform ed between different radio direct ion s

2. Rad io port ESC por t

Where a radio service channel is co nnected

to an ESC port on AUX board








4.2.2 Configuring H/K Alarms.

4.2.2 Configuring H/K alarms




4.2.2 Configuring H/K alarms On AUX bo ard prov isioning view, select the External points tab.

Conf igure input alarms as fol low s:

4.2.2 Configuring H/K alarms




4.2.2 Configuring H/K alarms Conf igure Output alarms as fol low s:



End Of TrainingThanks for your attention

WWW.ALCATEL-LUCENT.COM

134659455 MPR Delta Training

Documents

Transcript of 134659455 MPR Delta Training