vfe egypt workshop

Vodafone BEP Workshop

Divine Ofori Amankwah

Slide title minimum 32 pt

(32 pt makes 2 rows)

Text and bullet level 1minimum 24 pt

Bullets level 2-5minimum 20 pt

›!"# $%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~¡¢£¤¥¦§¨©ª«¬®¯°±²³´¶·¸¹º»¼½ÀÁÂÃÄÅÆÇÈËÌÍÎÏÐÑÒÓÔÕÖ×ØÙÚÛÜÝÞßàáâãäåæçèéêëìíîïðñòóôõö÷øùúûüýþÿĀāĂăąĆćĊċČĎďĐđĒĖėĘęĚěĞğĠġĢģĪīĮįİıĶķĹĺĻļĽľŁłŃńŅņŇňŌŐőŒœŔŕŖŗŘřŚśŞşŠšŢţŤťŪūŮůŰűŲųŴŵŶŷŸŹźŻżŽžƒ ˆˇ˘˙˚˛˜˝ẀẁẃẄẅȘșỲỳ–—‘’‚“”„†‡•…‰‹›⁄€™−≤≥fifl

Do not add objects or text in the footer area

Ericsson Vodafone Egypt BEP Workshop 2010-01-152

CONTENT SLIDE part one

purpose of dxx 8600 node introduction

features of dxx 8600 node implemented

hardware module description

network scenarios

Summary








Purpose of dxx 8600 in the strategic backhaul network

› To alleviate network capacity limitations on leased line and microwave backhaul infrastructure using a packet network – IP/MPLS.

› Achieve over-subscription at the end of deployment.








Traffic / data forwarding › Two fundamental Network Paradigms in the industry–Connectionless› IP, Ethernet, …

–Connection Oriented› Frame Relay, ATM, Circuit-Switched Voice,…› and MPLS

› Industry has lived with these 2 models for >20 years– Traditionally dealt with in an “overlay” fashion








Backhaul carrier transport evolution>MPLS (Multi-Protocol Label Switching) has emerged as the preferred technology for building Multi-service IP-based networks>Internet Engineering Task Force (IETF), ITU-T, and MPLS & Frame Relay Alliance (MFA) all cooperating on standards to enable MPLS-based convergence>MPLS has the ability to support converged services

>MPLS provides an circuit-like architecture >Majority of the operators are in the process or planning to upgrade their IP network to an IP/MPLS backbone>Hundreds (perhaps thousands) of network operators have MPLS running in the core of their network








What is mpls ?

With MPLS, reliable connection-oriented

services are brought to connectionless IP network

> Future proof platform for operators

> Migration from the legacy platforms such as FR, ATM,

Ethernet and leased lines

> QoS and Traffic Engineering

> Guaranteed QoS with packet prioritization

> Bandwidth reservations and bandwidth releases in links

> Fast rerouting possibilities

> Supports L2 and L3 VPNs with additional label stack








Advantages of MPLS

› Faster & Simple Packet Forwarding Paradigm– Hierarchical label swapping/switching using one or more 32-bit labels

prepended to packets– Decreased packet processing complexity compared to traditional IP

routing› Traffic Engineering and QoS Capabilities

– Explicit route specifications, as opposed to IP’s hop by hop routing– Fast Reroute during link failures; < 50 ms convergence– LSPs (Label Switched Paths) with circuit-like characteristics

› Virtual Private Networks – IP VPNs (IETF BGP/MPLS VPNs)– VPLS VPNs (Multi-point layer 2 Ethernet VPNs)








Multi Protocol Label SwitchingLabel based classification and forwarding capable of transporting protocols other than IP> Components:

>Signaling protocols: Label Distribution>MPLS enabled routers

>Ingress PE (LER): classification map to LSP>Transit P (LSR): Label Swapping>Egress PE (LER): Forward native packet

>IGP: Distribution of reachability information

> Evolution not revolution>MPLS control plane relies on underlying IP network








OSI Transport StackOSI = Open System InterconnectOSI = Open System Interconnect

Applications• Provides network services to application processes• Provides user authentication• Keywords: HTTP, SMTP, DNS, Telnet, FTP…Data Presentation• Ensure that the data are readable by the receiving system • Provides encryption• Keywords: MPEG, JPEG, ASCII, PGPInterhost Communication• Establish, manage and terminate sessions between applications• Keywords: Operation SystemEnd-to-End Connection• Handles transportation issues between hosts• Ensures data transport reliability• Establish, maintains and terminates virtual circuits• Keywords: TCP, UDP, Segmentation, Packets

Data Delivery• Route data packets• Select best path to deliver data• Provides logical addressing and path selection• Keywords: Router, IP, IPX, ARP, ICMP…

Access to Media• How data is formatted for transmission and how the access to the network is controlled.• It provides error detection• Keywords: Switch, Frame, CSMACD…Binary Transmission• Electrical, mechanical, procedural and functional spec. for activate, maintain and de-activate the physical link• Keywords: Copper, Fibre, Bit, Byte, Hub…

Layer-1: Physical

Layer-2: Data Link

Layer-3: Network

Layer-4: Transport

Layer-5: Session

Layer-6: Presentation

Layer-7: Application








MPLS Pseudowires

MPLS LSP

Pseudowire

AttachmentCircuit PW Granularity

TDM E1, 64 kbps

PPP, HDLC Port

Frame Relay Port, DLCI

ATM VP, VC

Ethernet Port, VLAN

TDM

PPP/HDLC

ATM (IMA)

FR

Ethernet

› Layer 1 or layer 2 traffic mapped to MPLS pseudowires

› Transport for 2G and 3G mobile traffic› Ethernet point-to-point services








Mpls label switched path› A Label Switched Path (LSP) is a uni-directional Virtual Circuit that

carries aggregated flows of traffic› This path is identified by a label, which is swapped as the packet

traverses the network (similar to ATM VPI/VCI or Frame Relay DLCI)› Since IP and Ethernet packets don’t have a field that can be used as a

label, a header must be added to these packets to include a label› LSP’s can be engineered to take explicit routes and be allocated

specific resources








Mpls (Shim) header format>Label

> Fixed-length packet identifier> Link local significance

>Fields> Label (20bits) = Label Value (220 = 1,048,576)> EXP (3bits) = Experimental (usually CoS)> S (1bit) = Bottom of stack “1” or not “0”> TTL (8bits) = Time to live, analogous to IP TTL

TTLLabel (20-bits) EXP S

L2 or L3 Packet (Payload)L2 or L3 Packet (Payload)

32-bits

MPLS Header0x8847SADA








Functions of mpls switches

ATM

Frame Relay

Ethernet

CE CE

ATM

Frame Relay

Ethernet

LER (or PE) Assigns MPLS Labels for packets moving

toward core Removes MPLS labels for packets

moving away from core Provides Adaptation Header (e.g. PW

Label) for E/ATM/FRLSR (or P) Forwards packets based on

Label Swaps labels Does not understand the

contents of the labeled packet

C D

E

F

G

B

LER (PE)

LSR LSR LSR

A

LER (PE)LSR

LSR

Customer NetworkCustomer Network

MPLS Core








Mpls switch functions

ATM

Frame Relay

Ethernet

CE CE

ATM

Frame Relay

Ethernet

CE devices Customer Edge equipment Could be a router, ethernet switch,

ATM or Frame Relay device Does NOT speak MPLS to the PE

C D

E

F

G

B

LER (PE)

LSR LSR LSR

A

LER (PE)LSR

LSR








Routing topology

› MPLS uses existing IP routing protocols–OSPF, IS-IS

› IP routing protocols identify a “shortest path” onto which all packets will be forwarded

› Traffic engineering requires “constraint-based” routing – finding a path that meets a set of specified constraints

› Routing protocols have been extended to support TE–OSPF-TE, ISIS-TE








Mpls signalling› Manual configuration (no signaling)

– As per ATM / FR PVCs› LDP = Label Distribution Protocol

– Simple signaling protocol– Good for basic connectivity and soft QoS services

› RSVP-TE = Resource reSerVation Protocol with Traffic Engineering extensions– Sophisticated signaling protocol– Enables resource allocation in each switch an LSP traverses

› BGP = Border Gateway Protocol– Extended to carry label information – eg RFC 2547 VPNs (4364), VPLS-

BGP








label switched paths

31

48

PE PE

IP/MPLS Core

3rd GatheringSmouha

P

P

P

P

LSP

57P

P

P

IPIP

IP

IPIP








Label Operations

› “Push” at ingress to MPLS network– Ingress PE applies label to non-MPLS packet

› “Swap” at each switch point in the network– P routers forward packets based on incoming label– P routers swap in label for out label (similar to ATM and FR)

› “Pop” at the egress to the MPLS network– Egress PE strips off the MPLS label to deliver native packet to the

customer network








label switched paths

31

48

PE PE

IP/MPLS Core

3rd GatheringSmouha

P

P

P

P

57P

P

P

IPIP

IP

IPIP

Swap

Swap

PopPush








over-subscription› Utilisation• Efficient use of backhaul resource – circuit versus packet transport

› Overbooking (0% - 1000%)• Interface connection & Admission control with overbooking- shaping to

smoothen out peaks and troughs to reduce congestion for optimal network perfomance.• Essential for low priority and bursty data control• Administrative bandwidth greater than physically possible• 0% is nominal bandwidth








Features of dxx 8600 node8660 8630 8620 8607 8605

Configuration 24 IFMs 8 IFMs 2 IFMs2 x GE/FE3 Modules

2 x GE16 x E1/T1

2 x FE

Forwarding capcity 42 Gbps 14 Gbps 3.5 Gbps 300 Mbps 300 Mbps

Power protection Yes Yes Yes Dual Input Dual Input

Control protection Yes Yes No No No

Forwarding (switch protection) Yes Yes No No No

Link protection Yes Yes Yes Dual UplinkDual

Uplink

Height 14U 5U 2U 1U 1U

Width 19” 19” 19” 19” 19”

DC power -48 V -48 V -48 V Yes-48 V, +24

V

AC power No No Yes Yes Yes

MPLS PW Yes Yes Yes Yes Yes

IP routing Yes Yes Yes Yes Yes

MPLS signalling (LDP, RSVP-TE)

Yes Yes Yes Yes Yes

Packet synchronization Yes Yes Yes Yes Yes

Availability Now Now Now Q4/2008 Now








Tellabs 8630 Access Switch

› Positioned to hub sites› Flexible capacity from 3.5G…14G

– Distributed switching to line cards (max. 4)

› Flexible equipping with a mixture of interfaces– Support for full redundancy (power

and control)– Two modules per line card

› IP routing and L2 switching› Size 5U x 19” x 300 mm








Tellabs 8660 Edge Switch

› Positioned to RNC and large hub sites› Flexible capacity from 3.5G…42G

– Distributed switching to line cards (max.12)

› Flexible equipping with a mixture of interfaces– Support for full redundancy (power and

control)– Any two modules per line card

› IP routing and L2 switching› Size 14U x 19” x 280 mm








Tellabs 8630/8660Distributed Switching

› Switching function distributed to line cards– Each card brings 3.5 Gbps switching capacity– Backplane supports 10 Gbps links

› Benefits of distributed switching– Low entry cost– More space for line cards– No single point of failure

CDCPower and control

No dedicatedswitch cards – each card has

3,5 Gbps switching

PowerControl

SwitchingLine cards

Line cardswith switching

3.5 Gbpsper cardn…12 cards








Tellabs 8630/8660Control and DC Power Feed Card

› Control and DC Power Feed Card = CDC› Two variants available CDC1-A and CDC1-B (to be used in sync with

IFC variant)› Main functionalities

– DC power feed– Control board (MPLS and IP routing protocols)– S3 timing module (SEC, Stratum 3, SMC)

› Can be 1+1 protected (slot 1 optional)› Physical interfaces

– Ethernet 10/100 Mbit/s and RS-232 asynch serial interface for management

– Station clock input/output 75/120 ohms– External alarm interface (8 inputs/4+2 outputs)

› Size: 40 x 380 x 295 mm (WxHxD)








Tellabs 8630/8660Management Interfaces in CDC

› The CDC card provides two management interfaces– 10/100Base-TX Ethernet interface is used when› Tellabs 8660 is a first hop NE from the operator LAN› Outband management is used

–RS-232 asynchronous serial interface› Local CLI configuration using terminal program








Tellabs 8630/8660CDC Management Fast Ethernet Protection

› MFE protection is automatically on if the CDCs are duplicated

› MFE interfaces in the active and passive CDCs share the same IP address but the MAC address is unique

› Passive MFE receives the same information as active one but drops it in both directions

› Active MFE can reside in the passive CDC








Tellabs 8630/8660Interface Module Concentrator Card

› Line card (LC) consists of one base card (Interface Module Concentrator = IFC) and 1..2 Interface Modules (IFMs)

› IFC has two variants: IFC1-A and IFC1-B– IFC1-A: Fully scaleable IFC with 450k IPv4

entries– IFC1-B: PWE3 optimized IFC with 256k IPv4

entries› Tellabs 8600 universal baseboard

for interface modules– Can be equipped with two

interface modules of various types › Free placement of Line cards into LC slots (any LC

slot number can be used)› SDH/SONET and Ethernet interfaces on different

IFCs can protect each other








Hardware module description› Services

– Ethernet, ATM, FR, PPP/HDLC, and TDM pseudowires

– IP VPN (RFC 2547bis)

› Connectivity– IP routing, MPLS switching– Ethernet port or VLAN switching– ATM VP and VC switching– FR port or DLCI switching– TDM port or timeslot cross

connection

› QoS functionality– DiffServ based QoS– ATM based QoS– MPLS-TE, DS-TE– CAC for ATM and DiffServ

› Resilience– Full element protections– MSP/APS and Ethernet Link

Protection for link level– MPLS-level fast protections








Tellabs 8600 Carrier Class Features

Redundant DC power and control plane

Distributed switchingNo single point of failure

Non-service affecting software downloads

Passive backplane

Hot-swappable cardsand SFPs

Multiple traffic protection alternatives TDM-like

synchronization architecture

Inbuilt test generators and analyzers

Full IP routing and MPLS signalling support








Interface Modules and Baseboard

› Common baseboard, interchangeable modules› Multiple protocol encapsulations› Multiple forwarding layers (TDM, L2, MPLS, IP) simultaneously› Single chip forwarding ASIC: cost effectiveness and reliability

InterfaceModule

Baseboard (IFC)

InterfaceModule

Ethernet

TDM

ATM

FR

PPP/HDLC

POS

BackplaneInterface

ForwardingASIC








Interface Module (IFM)

Interface Type Ports per IF Module

Ports per System

8660 8630 8620

chE1/chT1 (n x 64k) Multiservice (high density) 24 576 192 48

E3/DS3 Multiservice 6 144 48 12

chSTM-1/chOC-3 (down to n x 64k) Multiservice 1 24 8 2

chSTM-1/chOC-3 (down to n x 64k) Multiservice 4 96 32 8

STM-1/OC-3 ATM 4 96 32 8

STM-1/OC-3 POS 8 192 64 16

STM-4/OC-12 POS 4 96 32 4

STM-16/OC-48 POS 1 12 4 -

10/100M Ethernet 8 192 64 16

100M Ethernet (optical) 8 192 64 16

2+6 10/100/1000M Ethernet Combo 2+6 48+144 16+48 4+12

Gigabit Ethernet 2 48 16 4

Gigabit Ethernet (high density) 8 192 64 16








Tellabs 8660/8630Modularity = Flexible Configuration

IFM- various types- density depends on type

IFC- one card for all modules

SFP transceiverfor optics (1..8)also electrical plugs

› Same base board (IFC) can be used for any Interface Module (IFM)› Two IFMs can be equipped into one Line card› IFMs fit into any Tellabs 86x0 element› Number of SFP transceivers can be chosen based on need








Tellabs 8630/8660Hot Swapping

› Hot swapping = the system does not require powering the system down prior changing IFCs

› The CDC and IFC cards, fan modules and optics (SFPs)in the Tellabs 8660 are hot-swappable

› Card and module parameters from the IFCs are stored to the CDC–When an IFC card is replaced, the original parameters are automatically

copied to the new card

› The CDCs copy data between each other while operating– In case the CDC goes down or embedded software is upgraded,

graceful restart is used until the secondary CDC has updated the routes from the network








Tellabs 8600 FunctionalityMultiservice Transport

MPLS LSP

Pseudowire

AttachmentCircuit PW Granularity

TDM n x 64k or 2/1.5 M

PPP, HDLC Port

Frame Relay Port, DLCI

ATM VP, VC, AAL5

Ethernet Port, VLAN

TDM

PPP/HDLC

ATM (IMA)

FR

Ethernet

› Layer 1 or layer 2 traffic mapped to MPLS pseudowires (over MPLS or IP tunnels)

› Transport for 2G and 3G traffic› IP routing

IP VPN

MPLS LSP

ATM/PPP/FR/Ethernet Native L2

IP over

Optionally

Flexible protocol support in SW configurable multiservice interfaces

IP Tunnel








Tellabs 8600 ApplicationsSwitching

MPLS LSP

Switched Connection

Switching Granularity

TDM Port or n x 64k

Frame Relay DLCI

ATM VP, VC

Ethernet VLAN

TDM

ATM (IMA)

FR

Ethernet

› Transport for 2G and 3G traffic

TDM

ATM (IMA)

FR

Ethernet

Transport of native layer 1 and 2 protocols








Switching versus routing› Routing

– Packets contain an explicit destination address– Routers forward packets toward the destination– Each packet is forwarded as a separate event. The same process must occur for each packet

on each node. Caveat: Most routers today have express forwarding as default and look up is not repeated if packet N+1 has the same header contents as packet n. N+1 is simple sent on the same path as n.

– No setup process needed, just a routing protocol to build the routing table– The lookup in the routing table is based on the best-match – there could be multiple matches

› Label switching– Incorporates a locally significant identifier called a “label”– Each hop inspects the label and makes a forwarding decision based on its value– Label values are “swapped” as the packet is switched– Labels must be exchanged between nodes prior to data flow (there must be a setup process)– The lookup in the forwarding table is based on exact match – there is only one “right” answer








Network scenarios

› Haram hub connection.› Nasr City hub connection.› Imbeba hub connection.








Hub and switch connections

• One POS leased line protected ring from TE MSP 1+1.

• Two POS lease line line from TE with L3 RSVP – TE protection.

• Multi link point to point protection ML-PPP Microwave STM-1 or E1.








Access Transmission – Futurewith 3G RAN IP evolution

STM-16

E1 TrafficSTM-1 Traffic

STM-1 Ch.

STM-1 Unch

TE SDH Network

DXX 8630

DXX 8630

DXX 8630

DXX8660

GbE

Unch STM-1 (ETMF4) +GbE (ETMFX)

boards replacing ETMC41

Add Ethernet board (ETMFX) + SW in 3G

RBS








Leased line Protection

RSVP1:1 over two hops with ELP








featuresRSVP 1:1 with ELP– Explanation

Tunnel configured over the two hops with primary path as the working path (i.e. Microwave link #1 and worker - GE link) and secondary path as the protection path (i.e. Microwave link #2 and worker GE link)

– Advantages ELP configuration on the GE link between 8101 and 8102








Questions

Operation and maintenance – trouble shooting

Part two

Divine Ofori Amankwah








Content slide part two node installation, autodiscovery and upgrading traffic carrying nodes –

IFM’S & IFC’S. Node configuration and performance monitoring with snmp. Trunk creation. Establishing ldp and rsvp sessions with isis. Interface parameterization. Site building with pwe for 2g and 3g. Implementation of protection schemes. Alarm monitoring. Summary








Management network








node installation, autodiscovery and upgrading traffic carrying nodes – IFM’S & IFC’S

node installation out band management› Physical installation with complete hw inventory.› Host name› Assign management ethernet interface – mfe› Enable BMP protocol server› Create and assign loop back interface








Command line interface








autodiscovery

•Use only on newly installed nodes to align hardware resources on node with database.

• if hardware changes are made on node already carrying traffic autodiscovery must not be used.

• manually populate changes to db from node editor.








Node configuration and performance monitoring with snmp

Node configuration using LLD› Loop back ip address› Router id and protocol› Mpls / ip / pdh interface parameters.› Mpls global parameters› Synchronisation parameters› Real time clock








SNMP agent configuration








Mpls interface parameters








Trunk creation - physical








Ip / mpls link to trunk - logical








Establishing ldp and rsvp sessions with isis

› Show ldp session› Show rsvp session› Show run | bl gex/x/x› Show run | bl sox/x/x› Show ldp pwe3› Show ldp <pwe3 name>› Show ldp fo <pwe3 name>








Interface parameterization

› Satop parameters.› CeSPSN parameters.› ATM parameters.› IMA groups








Site building with pwe for 2g and 3g








overview








Atm deployment








Structure








Atm time slot creation








ATM Interface parameters








Vp interface creation








VC interface creation








Maximum allocations








Atm Ima gROUP








Ima sTRUCTURE








CREATING IMA








IMA Cell rates








Tdm deployment








Satop tdm interface








cesopsn tdm interface








Hub and switch on same node 7102








Implementation of protection schemes

› Network element level protection.› Graceful restart functionality.› Network level protection.








Network element level protection

› Equipment redundancy








Cdc protection status








Cdc switchover

>Show protection unit cdc

>Protection manual-switchover unit cdc slot <passive>








Cdc mfe protection








Separate control and data plane








Graceful restart functionality› Control plane protection








GR extension supports many protocols








Network scenario of GR








Graceful restart in BGP› Prevents restart in neighbour router from shutting down

session.› Ensures hitless traffic situations in restart.› Prevents route flapping and continuous BGP computing.› Allows buffer time for neighbour to recover – restarting

router routes are marked as stale.› If hit router restarts with GR time stale routes are restored

otherwise traffic is routed to new routes and stale routes deleted.








Network level protection








MSP / APS configuration 1








MSP / APS configuration 2








RSVP-TE Protection 1








RSVP-TE Protection 2








Ethernet link protection group› Two Ethernet interfaces with same IP and MAC addresses active and

passive.› Works with existing Ethernet standards.› Switchover – non revertive, takes less than 200ms, triggered by

manual event or network fault.








Alarm monitoring

› Node alarms.› Network alarms.› network fault monitoring› Fault reporting, filtering and classification








Introduction to fault management








Node alarms








Network alarms

1. Fault report

2. Defining a network fault report.








Fault server function








Polling and notification








Fault types and status

› General problem type (GPT)› Specific problem type (SPT)Status› Maintenance – pma, dma, mei› Severity – critical, major, minor, warning› Service status – service or non-service








Fault types and status








Fault report creation








Fault filtering› General filter› Node specific filter








Fault reclassification› The status of a maintenance or service fault can be

changed.








Nms component monitoring








summary

› MPLS› Label Switched Paths› Utilisation› Evolution to packet ip / mpls backhaul transport

vfe egypt workshop

Documents