IPD WT IW Internal Use

Draft V0.16published Sept.30 of 43

Alcatel-Lucent IPD and WTPG Interworking Solutions Over Ethernet VLLs Internal use only - Copyright ©2009 Alcatel-Lucent. All rights reserved.

Alcatel-Lucent IPD and WTPU Interworking Solutions

Over Ethernet VLLs - Step 1



Table of Contents

1 SCOPE ................................................................................................................................................. 4

2 AUDIENCE ......................................................................................................................................... 4

3 INTRODUCTION............................................................................................................................... 4

4 GENERAL DEPLOYMENT PARAMETERS ................................................................................ 7

4.1 PHYSICAL CONNECTIVITY ............................................................................................................ 7 4.1.1 9500 MPR............................................................................................................................... 7 4.1.2 IPD Products .......................................................................................................................... 7

4.2 ENCAPSULATION.......................................................................................................................... 7 4.2.1 9500 MPR............................................................................................................................... 7 4.2.2 IPD Products ........................................................................................................................ 10

4.3 SCALABILITY .............................................................................................................................. 10 4.3.1 IPD Products ........................................................................................................................ 10

4.4 TRAFFIC MANAGEMENT............................................................................................................. 11 4.4.1 9500 MPR............................................................................................................................. 11 4.4.2 IPD Products ........................................................................................................................ 11

5 SOLUTIONS ..................................................................................................................................... 12

5.1 ATM INTERWORKING................................................................................................................ 13 5.1.1 Description ........................................................................................................................... 13 5.1.2 Physical Connectivity ........................................................................................................... 14 5.1.3 Scalability ............................................................................................................................. 14 5.1.4 Requirements ........................................................................................................................ 14

5.2 TDM INTERWORKING................................................................................................................ 16 5.2.1 Description ........................................................................................................................... 16 5.2.2 Physical Connectivity ........................................................................................................... 17 5.2.3 Scalability ............................................................................................................................. 17 5.2.4 Requirements ........................................................................................................................ 17

5.3 ETHERNET INTERWORKING........................................................................................................ 18 5.3.1 Description ........................................................................................................................... 18 5.3.2 Physical Connectivity ........................................................................................................... 19 5.3.3 Scalability ............................................................................................................................. 19 5.3.4 Requirements ........................................................................................................................ 19

APPENDIX A 7450 MDAS................................................................................................................ 20

APPENDIX B 7750 MDAS................................................................................................................ 21

APPENDIX C GLOSSARY............................................................................................................... 23

APPENDIX D REFERENCES.......................................................................................................... 24

APPENDIX E HISTORY .................................................................................................................. 24

APPENDIX F LAB VALIDATION.................................................................................................. 25

F.1 ATM INTERWORKING SOLUTION ............................................................................................... 25 F.1.1 7750/7450 SETUP ................................................................................................................ 25 F.1.2 Failure Scenarios Validation................................................................................................ 26

F.2 TDM INTERWORKING SOLUTION ............................................................................................... 29 F.2.1 7750/7450 SETUP ................................................................................................................ 29 F.2.2 Failure Scenarios Validation................................................................................................ 30

F.3 ETHERNET INTERWORKING SOLUTION ....................................................................................... 32 F.3.1 7750/7450 SETUP ................................................................................................................ 32 F.3.2 Failure Scenarios Validation................................................................................................ 32



F.4 NETWORK SYNCHRONIZATION MODEL A – MEF8 ACR WITH RF CLOCK DISTRIBUTION ......... 34 F.4.1 MPR Setup ............................................................................................................................ 34 F.4.2 7750/7450 SETUP ................................................................................................................ 34 F.4.3 Tests and Results .................................................................................................................. 35 F.4.4 Clocking Measurements........................................................................................................ 35

F.5 NETWORK SYNCHRONIZATION MODEL B – END TO END MEF8 ACR ....................................... 38 F.5.1 MPR Setup ............................................................................................................................ 38

F.6 MPR 9500, 7705 AND 7750 ATM, ETH AND TDM INTERWORKING SOLUTION ........................ 40 F.6.1 7750/7705 SETUP ................................................................................................................ 40 F.6.2 Validation Scenario .............................................................................................................. 40

F.7 TRANSFER DELAY MEASUREMENT............................................................................................ 42



1 Scope This document defines the interworking solution between 9500 MPR based microwave transport networks and IP/MPLS aggregation networks with the use of Ethernet VLLs (Epipes).

2 Audience This document is intended for product and solution managers, and R&D personnel of WTPG and IPD. It is not intended for general distribution.

3 Introduction This document is applicable to transport networks where the customer is asking:

� to gather traffic from peripheral locations to central locations � to have microwave based access � to have IP/MPLS based aggregation

IP/MPLS MW

Customer

peripheral stations

MW

transport

IP/MPLS

transport

Customer

central locations

IP/MPLS MW

Customer

peripheral stations

MW

transport

IP/MPLS

transport

Customer

central locations

There is a suitable number of hand-off sites between the microwave backhauling and the IP/MPLS fiber backhauling (i.e. between the L2/Static MPLS domain and the dynamic MPLS domain). In the hand-off point(s) a Gigabit Ethernet connection is typically used to connect the microwave equipment with the IP/MPLS equipment. Microwave network topology is typically a daisy-chain layout in the access network (see Figure 1). For the purpose of this solution, the topology of the MW network is not vital to the operation of the interworking function at the hand-off site.



MICROWAVE technology

L2 or Static MPLS

Fiber technology

Dynamic MPLS domain

Hand-offSites

Figure 1: Microwave backhaul hand-off to IP/MPLS aggregation

For ease of reference, the following diagram captures the names used for various parts of the solution topologies:

IPD NetworkMicrowaveNetwork

Controller7750 inthe MTSO

7xxx in thehand-off

GW MPRCell-site MPR

Handoff point

PEPE

The different native services (TDM, ATM/IMA, Ethernet) are mapped in the hand-off point into Ethernet. Two interworking models will be introduced in a phased approach:

• “Interworking model 1” => “Epipes” In the hand-off point the native services will be mapped as:

o ATM => into an MPLS PW o TDM => into a MEF-8 PW o Ethernet => as native Ethernet

The IPD network will then use Epipes to (re-)encapsulate everything into PtP Ethernet connections



o “Interworking model 2” => “Multi-segment PW” In the hand-off point the native services will be mapped as MPLS PW.

The IPD network will then implement PW switching to open Apipes/Cpipes/Epipes

This document focuses on “Interworking model 1” requirements.

IP/MPLSNetwork

MicrowaveNetwork

Customer

central location

Customer

native services

(E1, ATM/IMA/E1, Ethernet)Handoff point

Any service

over Ethernet

Epipes

Interworking model 1 ⇒⇒⇒⇒ Epipes

IP/MPLS

Network

Microwave

Network

Customer

central location

PW switching

Customer

native services (E1, ATM/IMA/E1, Ethernet) Epipes

Apipes

Cpipes

Interworking model 2 ⇒⇒⇒⇒ Multi-segment PW

Handoff pointAny service

over MPLS over Eth



4 General Deployment Parameters

4.1 Physical Connectivity

4.1.1 9500 MPR The MPR is a microwave radio link made of an Indoor Unit (IDU) and an Outdoor Unit (ODU). The IDU is providing different customer interfaces: PDH E1 through the “PDH plug-in”, ATM/IMA/E1 through the “ASAP” board, Ethernet through the “Core” board.

4.1.2 IPD Products

4.1.2.1 7450 ESS The 7450 supports several variants of GigE MDAs with different number of ports. The IOM3/MDA-XP variants also support SyncE. In most cases, GigE links will be at the handoff point, but there is the possibility of using FE. In addition, 10GigE is possible in the uplink. Some applicable MDA types are listed in Appendix A.

4.1.2.2 7705 SAR A likely candidate for handoff sites is the 7705 SAR because of the evolution path for this product to support ATM PW switching (Phase 2). The 7705 supports an 8-port Ethernet Card. Includes 2 GigE SFP ports, 6 10/100 FE RJ45 ports and Synchronous Ethernet. Each port can be used for access or network ports.

4.1.2.3 7750 SR The 7750 supports several variants of GigE MDAs with different number of ports. The IOM3/MDA-XP variants also support SyncE. The 7750 supports multiple technologies of MDAs, whether it is directly connected to the MW network or is in the MTSO. The relevant MDA types are listed in Appendix B.

4.2 Encapsulation

4.2.1 9500 MPR MPR is accepting the following native services types: E1, ATM/IMA/E1, Ethernet. In the hand-off point the different services are encapsulated as follows:



ATM

Ethernet

VLAN1

MPLS Tunnel1

PW1

ATM PWE3payload

Ethernet

VLANX

Ethernetpayload

Ethernet

VLAN-X

MEF8 Header

TDM MEF8payload

TDM Ethernet

• E1 service o Protocol stack is E1/MEF-8/VLAN/Ethernet. o There is a one-to-one correspondence between o E1 <=> ECID(=PW_label) <=> VLAN_ID. o ACR without RTP is used in conjunction with 7750. Ethernet frames going from MPR to 7x50/7705 have o unique MAC SA equal to the MPR MAC address in the hand-off

point. o MAC DA is configurable per PW

• ATM service o Protocol stack is ATM/PW/MPLS Tunnel/VLAN/Ethernet. o A single and provisionable MPLS Tunnel label is used; in a network

with N hand-off points, there will be N different tunnel labels. Typical values for N are from 1 to 40.

o Each tunnel can carry hundreds of ATM PWs. o Tunnel header in the direction MPR => 7x50: Tunnel_label is

configurable (range:32 to 287, automatically derived by MPR from PW_label and MPR-internal VLAN_ID); Tunnel_exp bits are copied frame-by-frame from PW_exp bits.

o The hashing function that maps ATM PW_label and VLAN_ID to Tunnel label allows to use up to 512 different ATM PW_label and VLAN_ID values into the same tunnel label.

o o Tunnel header in the direction 7x50 => MPR: the info embedded in

the Tunnel tag (label and exp) are not used by the MPR. o With reference to RFC4717: “N-to-1 mode with N=1” is the

encapsulation method; the mapping can be either VC<=>PW or VP<=> PW; the former being the typical behaviour, because of QoS management with NodeBs generating 1 VP with multiple VCs at different ATM service category levels.

o Cell concatenation possible and provisionable (N ATM cells per MPLS packet; 1≤N≤28).



o PW header in the direction MPR => 7x50: the PW label is

provisionable per PW and a unique value is used for both directions; the PW_exp represents CoS derived from original ATM SC.

o PW header in the direction 7x50 => MPR: the PW_label is used by MPR to reconstruct MPR-internal VLAN identifiers; the PW_exp is used to determine MPR-internal CoS info (used in the Core switch).

o A VLAN tag is present, with a single and provisionable VLAN

identifier. o In the direction MPR => 7x50 the VLAN p-bits are copied –frame by

frame- from the PW exp bits; this allows a Carrier Ethernet transport equipment (e.g. the 7450) to use specific Ethernet QoS mechanisms for traffic forwarding (e.g 7450 opening an Epipe with its own PW exp bits, and mapping there the received p bits info)

o In the direction 7x50 => MPR is not using received p bits; the MPR is remarking the VLAN p bits frame by frame in order to declare each frame “green=in-profile”.

Ethernet frames going from MPR to 7x50/7705 have o unique MAC SA equal to the MPR MAC address in the hand-off

point. This behavior has a direct impact on the service configuration in the IP/MPLS aggregation network.

o MAC DA is configurable per PW

• Ethernet service o MPR can be configured for the Eth service either in “bridge mode”

in accordance to 802.1d or in “VLAN mode” in accordance with 802.1q Different cases can be envisaged:

� MPR in “bridge mode” and customer delivering only tagged frames => 7450 can open one tagged Epipe per VLAN.

� MPR in “bridge mode” and customer delivering both tagged and untagged frames => 7450 will open an Epipe in per VLAN and supports null VLAN ID (0) and default service (*) for untagged frames and tagged frames with no explicit service definition. 7705 SAR also supports these service capabilities.

� MPR in “VLAN mode” => both tagged and untagged customer traffic can be accepted by the MPR. Here the MPR will tag customer untagged frames with provisionable VLAN_ID.



o Ethernet frames going from MPR to 7x50/7705: the GW MPR will

not change any field in the L2 Ethernet layer (MAC SA, MAC DA, VLAN if present). This is different from TDM and ATM hand-off behavior.

4.2.2 IPD Products The solutions in this document always make use of Epipe services in the IP/MPLS aggregation network. An Epipe service is a layer 2 point-to-point service where the customer data is encapsulated and transported across a service provider’s IP/MPLS network. An Epipe service is completely transparent to the subscriber’s data and protocols. The 7450 ESS Epipe service does not perform any MAC learning. IPD products encapsulate data based on the port type and service configuration. Ports can be configured either as access or network ports. 7450 Ethernet capable ports can use Null, dot1Q, or QinQ type. Epipe services are initiated against a specific port/VLAN and can be tagged and/or untagged. A service may also be defined for the null VLAN ID “0” on a given physical port. Also, a default service can be used for all tagged/untagged frames with no explicitly defined service. The default SAP is designated by the port ID and “:*”. Please see §5 for more details on encapsulation formats for each solution.

4.3 Scalability

4.3.1 IPD Products Depending on the platform and chassis sizes that are deployed in the IPD segment of the network, the scalability numbers will be different. Network architecture dictates what ultimately becomes a scaling issue. For example, typical limiting parameters on the MTSO 7750s are:

• Network Interfaces

• T-LDP sessions

• BFD sessions

• OSPF adjacencies

• Ports per LAG group

• SR1 IP interfaces For example, prior to release 8.0 of the 7750, up to 240 distributed MW clusters (=handoff points) can be accommodated. As of R8.0, the limit will be close to 1000. Even prior to R8, this is foreseen to be more than sufficient to support MW access aggregation interworking. Scalability of a given solution will be detailed in §5.



4.4 Traffic Management

4.4.1 9500 MPR Within the uW MPR clusters each type of service/traffic is treated accordingly to its nature to guarantee customer expectations on E2E native quality. This is obtained applying various techniques to properly manage the different types of traffic; here below a summary will be given, for a full description pls refer to the 9500MPR Intranet documentation. Ethernet customer traffic is classified and managed according to 802.1p bits or to DSCP bits. ATM customer traffic is classified and managed according to the original ATM CoS (CBR, UBR+, UBR, …). Cell concatenation is optionally used to optimize radio bandwidth usage. TDM customer traffic is recognized and always assigned to the highest priorities scheduler queues to minimize latency.

4.4.2 IPD Products IPD products support the classification of traffic based on ToS fields in the encapsulation (eg. P-bit, DSCP, and EXP). When using Epipes within the IP/MPLS network, the p-bit of ingress traffic is the only means of classifying traffic. In the solutions presented in this document, the assumption is that traffic arriving from the MW cluster is tagged with an appropriate p-bit value to differentiate CoS.



5 Solutions The solutions presented here use the dual-chassis 7750 resiliency model. The single chassis topology is also possible with the removal of unnecessary configuration options. As an example in the following picture is shown –for the ATM case- a 7750 dual chassis arrangement vs. a single chassis one.

IP/MPLS Aggregation

9500 MPR

1 2Epipe

Services

4A

4B

5B 6B

5A 6A

3B

3A

EpipeServices

ApipeServices

EpipeServices

ApipeServices

7B

7A

8

9

RNC

Active PWs

Standby PWs7450770577107750

MPR Chain

77507750 dual chassis

IP/MPLS Aggregation

9500 MPR

1 2Epipe

Services

4A

5A 6A

3A

EpipeServices

ApipeServices

RNC

Active PWs

7450770577107750

MPR Chain

77507750 single chassis

Pls note that E-pipes in the IP/MPLS part for all customer services, including the Eth service, so 1 single cable can be used in the hand-off point (1)<=>(2).



5.1 ATM Interworking

5.1.1 Description The 9500 MPR ASAP card can terminate ATM-IMA links from a WCDMA Node B. The ATM cells are then transported to the GW MPR which performs the encapsulation as described in §4.2. At the hand-off point, the 7xxx initiates an Ethernet VLL service (Epipe) which will be used the transport the ATM payload to the the MTSO. The 7750s in the MTSO must terminate the Epipe and exit the chassis and re-enter to terminate the Apipe frames constructed by the GW MPR. With dual-chassis 7750s in the MTSO, it is possible to configure redundant PW services that are protected end-to-end (see .Figure 2)

T-LDP (dynamic PWs)

IP/MPLS Aggregation

9500 MPR

1 2Epipe

Services

4A

4B

5B 6B

5A 6A

3B

3A

EpipeServices

ApipeServices

EpipeServices

ApipeServices

7B

7A

8

9

Ethernet

VLAN1

MPLS Tunnel1

PW1

ATM PWE3payload

Ethernet

VLAN1 (opt)

MPLS Tunnel1

PW1

ATM PWE3payload

MPLS Tunnel2

PW2

Ethernet

Ethernet

VLAN1

MPLS Tunnel1

PW1

ATM PWE3payload

RNC

Active PWs

Standby PWs APS

External loopback required

Static PWs

7450770577107750

Script file:Provides unique VLAN ID towards 7xxx

MPR Chain

7750

Figure 2: ATM Interworking Solution



5.1.2 Physical Connectivity Hand-off point A single GigE port from the 9500 MPR can be connected to a single 7xxx GigE port at the hand-off point. The 7xxx port must be configured as an access type in order to initiate the Epipe services. 7750 SRs A GigE port is required for the network ingress of the Epipe service. The termination of this service is done on another GigE port (or LAG group of ports) which loopback to the same chassis to network ingress of the static Apipe service. The 7750 supports single or multi-chassis APS connectivity to the RNC. Typically this is an ATM STM1/OC3 concatenated interface, but higher rates are also supported if needed.

5.1.3 Scalability IPD Network With no other services configured on the same network, the 7750 SRs can support up-to a maximum of 992 static MPLS tunnels. Prior to release 8.0 of the 7750, up to 240 distributed MW clusters (=handoff points) can be accommodated (240 is related to the maximum number of 7750 network interfaces – every uW cluster is seen as a “Network adjacency” taking up 1 network IP interface) As of R8.0, the limit will be close to 1000. This is foreseen to be more than sufficient to support MW access aggregation interworking. There may be other important scalability considerations that need to be made. These are often dependent on the backhaul network architecture, and would have to be analyzed on a case-by-case basis.

5.1.4 Requirements

Unless otherwise noted here, the products used in the solution already support the technologies to perform the aggregation functions described in this solution. For example, it is implied that the PE router in the IP/MPLS aggregation network support Epipe services. Features to be implemented:



• Static MPLS Interworking (ATM PWE3) (9500) Available today through config files. Pls see section 4.2.1

• Management support (9500) o Network management and provisioning support for this feature o Available today through a static configuration file.

• Static LSP ARP Fast-Polling Timers (7750) o This enhancement(s) would enhance the recovery time to a few

seconds for � First – Chassis failover � Second – Control processor module switchover

o Without this feature, the max recovery time is approximately 30 seconds.



5.2 TDM Interworking

5.2.1 Description In the hand-off point the protocol stack is a standard MEF-8, with different VLAN identifiers associated to different E1 signals. The number of VLAN_ID per hand-off point has a wide range, with typical values between 10 and 300.

IP/MPLS AggregationEpipeServices

4A

4B

3B

3A

EpipeServices

EpipeServices

7B

7A

8

9

Ethernet

VLAN-X

MEF8 Header

TDM MEF8payload

Ethernet

MEF8 Header

PW1

TDM MEF8payload

MPLS Tunnel

BSC

Active PWs

Standby PWs

OC3/STM1 CES port

T-LDP (dynamic PWs)

Static PWs

T1/E1s

MC-APS

MUX

Ethernet

VLANX

9500 MPR

1 2

MPR Chain

7750

7450770577107750

Figure 3: TDM Interworking Solution



5.2.2 Physical Connectivity Hand-off point A single GigE port from the 9500 MPR can be connected to a single 7xxx GigE port at the hand-off point. The 7xxx port must be configured as an access type in order to initiate the Epipe services. 7750 SRs A minimum of one GigE port and one CES port are required on each 7750 SR. The 7750 can terminate MEF8 over Epipe without having to exit the chassis (as in the ATM case above). The 7750 supports single or multi-chassis APS connectivity to the controller over a channelized OC3/STM1 or OC12/STM4 interface. If the controller requires native TDM links, then a MUX/DEMUX would have to be deployed between the controller and the 7750 SRs.

5.2.3 Scalability IPD Network Consider that –at least theoretically- there is a limit on the number of E1s due to the connection in the BSC/RNC central location between the 7750 and the BSC/RNC. This limit is related to 4 x STM1 output ports of each CES MDA (Circuit Emulation Media Dependent Adapter). Example with SR12: there are 20 available slots for MDAs; assuming that 10 of them are used as CES MDA to terminate MEF-8 services, this is introducing a limit of 10 (MDA) x 4 (STM-1 ports) x 63 (E1per STM-1) = 2520 E1. This is not seen as a real restriction.

5.2.4 Requirements

There are no additional product requirements for supporting this solution.



5.3 Ethernet Interworking

5.3.1 Description Ethernet traffic is natively bridged in the GW MPR. When multiple technologies are being aggregated from the MW network over the IP/MPLS network, it is preferable to use Epipe service from the handoff point to transport the Ethernet frames. This allows all the technologies (TDM, ATM, and Ethernet) to use a single GigE access port on the 7xxx in the hand-off. (NOTE: in future releases it may become possible to have hybrid ports on the 7xxx products. Hybrid ports can support both access and network traffic on a single physical interface)

IP/MPLS Aggregation

9500 MPR

1 2Epipe

Services

4A

4B

3B

3A

7B

7A

8

9

Ethernet

VLANX

Ethernetpayload

Ethernet

PW1

Ethernetpayload

MPLS Tunnel

RNC

Active PWs

Standby PWs

T-LDP (dynamic PWs)

EpipeServices

EpipeServices

MPR Chain

7750

7450770577107750

Figure 4: Ethernet Interworking Solution

(above fig. to be adjusted if E-pipe is the preferred method)



5.3.2 Physical Connectivity Hand-off point A single GigE port from the 9500 MPR can be connected to a single 7xxx GigE port at the hand-off point. The 7xxx port must be configured as an access type in order to initiate the Epipe services. Alternatively, Ethernet bridging overlay can be used in the IP/MPLS domain. This solution requires the configuration of a network port on the 7xxx in the hand-off point.

5.3.3 Scalability There are no additional scalability concerns for this solution.

5.3.4 Requirements

There are no additional product requirements for supporting this solution.



Appendix A 7450 MDAs MDA Name PRODUCT / DESCRIPTION

High Scale Media Dependant Adapter (HS-MDA)

MDA - 7450 ESS 10-PT GIGE HS-MDA

7450 ESS 10-port Gigabit Ethernet High Scale (HS) MDA with on-board queuing. Accepts up to ten (10) SFP GigE-xx Optics Modules. 10/100/1000TX operation supported with GigE TX SFP. (Only support on 3HE00229AB)

MDA - 7450 ESS 1-PT 10GE HS MDA 7450 ESS 1-port 10G Ethernet High Scale (HS) MDA with on-board queuing. Accepts up to one (1) XFP.

Ethernet MDA-XP

MDA - 7450 10-PT GE MDA -XP SFP 7450 ESS 10-Port Gigabit Ethernet MDA-XP. Accepts up to ten (10) SFP GigE-xx Optics Modules, 10/100/1000TX operation with GigE-T SFP

MDA - 7450 20-PT GE MDA-XP SFP 7450 ESS 20-port 1000BASE Ethernet MDA-XP. Accepts up to twenty (20) SFP GigE-xx Optical Modules. (Supported on 3HE00229AB and 3HE03620AA)

MDA - 7450 20-PT 10/100/1000-TX MDA-XP

7450 ESS 20-port 10/100/1000BASE Ethernet MDA-XP with RJ-45 connectors. (Supported on 3HE00229AB and 3HE03620AA)

MDA - 7450 ESS 2-PT 10G MDA-XP - XFP 7450 ESS 2-port 10GBASE Ethernet MDA-XP. Accepts two (2) XFP 10GigE Optics Modules. (Supported on 3HE00229AB and 3HE03620AA)

MDA - 7450 ESS 4-PT 10G MDA-XP - XFP 7450 ESS 4-port 10GBASE Oversubscribed Ethernet MDA-XP. Accepts four (4) XFP 10GigE Optics Modules. (Supported on 3HE00229AB and 3HE03620AA)

MDA - 7450 ESS 1-PT 10G MDA-XP - XFP 7450 ESS 1-Port 10GBASE Ethernet MDA-XP. Accepts One (1) XFP 10GigE Optics Modules. (Supported on 3HE00229AB and 3HE03620AA)

Ethernet MDAs

MDA - 7450 ESS 20-PT GIGE SFP 7450 ESS 20-port Gigabit Ethernet Optical MDA. Accepts up to twenty (20) SFP GigE-xx Optics Modules

MDA - 7450 ESS 1-PT 10GBASE-LW/LR 7450 ESS 1-port 10GBASE-LW/LR Ethernet MDA, WAN/LAN PHY, 1310 nm, Simplex SC Connector

MDA - 7450 ESS 1-PT 10GBASE-EW/ER 7450 ESS 1-port 10GBASE-EW/ER Ethernet MDA, WAN/LAN PHY, 1550 nm, Simplex SC Connector

MDA - 7450 ESS 2-PT 10GBASE XFP 7450 ESS 2-port 10GBASE Ethernet MDA. Accepts up to two (2) XFP 10GigE Optics Modules

MDA - 7450 ESS 1-PT 10GBASE-ZW/ZR 7450 ESS 1-port 10GBASE-ZW/ZR (80 km) Ethernet MDA, WAN/LAN PHY, 1550 nm, Simplex SC Connector

MDA - 7450 ESS 10-PT GIGE-B SFP 7450 ESS 10-port Gigabit Ethernet Optical MDA Rev. B. Accepts up to ten (10) SFP GigE-xx Optics Modules, 10/100/1000TX operation with GigE TX SFP

MDA - 7450 ESS 1-PT 10GBASE XFP 7450 ESS 1-port 10GBASE Ethernet MDA. Accepts one (1) XFP 10GigE Optics Modules

MDA - 7450 ESS 10G+GIGE XFP/SFP 7450 ESS 1-port 10GBASE + 10-port Gigabit Ethernet MDA. Accepts one (1) XFP 10GigE Optics Modules and up to ten (10) SFP GigE-xx Optics Modules, 10/100/1000TX operation with GigE-T SFP



MDA - 7450 ESS 10G TUN ZW/R 1-port 10GBase DWDM Tunable MDA - LC connector. Full C-Band Tunable, supports FEC, EFEC.

Appendix B 7750 MDAs

MDA Name PRODUCT / DESCRIPTION

Integrated Media Modules (IMM's)

IMM - 7750 SR 4-PT 10GE - XFP 7750 SR 4-port 10GE IMM will provide 4 physical ports that accept (4) XFP pluggable optic modules.

IMM - 7750 SR 8-PT 10GE - XFP 7750 SR 8-port 10GE IMM will provide 8 physical ports that accept (8) XFP pluggable optic modules.

IMM - 7750 SR 48-PT GE - SFP 7750 SR 48-port GE IMM will provide 48 physical ports that accept (48) SFP pluggable optic modules.

IMM - 7750 SR 48-PT GE - RJ45 7750 SR 48-port GE IMM will provide 48 physical ports with RJ-45 connectors.

High Scale Media Dependant Adapter (HS-MDA)

MDA - 7750 SR 10-PT GIGE HS-MDA

7750 SR 10-port Gigabit Ethernet High Scale (HS) MDA with on-board queuing. Accepts up to ten (10) SFP GigE-xx Optics Modules. 10/100/1000TX operation supported with GigE-T SFP (Supported on 3HE00020AB and 3HE01473AA)

MDA - 7750 SR 1-PT 10GE HS MDA 7750 SR 1-port 10G Ethernet High Scale (HS) MDA with on-board queuing. Accepts up to one (1) XFP.

Ethernet MDA-XP

MDA - 7750 10-PT GE MDA-XP SFP 7750 SR 10-Port Gigabit Ethernet MDA-XP. Accepts up to ten (10) SFP GigE-xx Optics Modules, 10/100/1000-TX operation with GigE-T SFP

MDA - 7750 20-PT GE MDA-XP - SFP 7750 SR 20-port 1000BASE Ethernet MDA-XP. Accepts up to twenty (20) SFP GigE-xx Optical Modules.

MDA - 7750 20-PT 10/100/1000 RJ45 MDA-XP

7750 SR 20-port 10/100/1000BASE Ethernet MDA-XP with RJ-45 connectors.

MDA - 7750 SR 2-PT 10G MDA-XP - XFP 7750 SR 2-port 10GBASE Ethernet MDA-XP. Accepts two (2) XFP 10GigE Optics Modules.

MDA - 7750 SR 4-PT 10G MDA-XP - XFP 7750 SR 4-port 10GBASE Ethernet MDA-XP. Accepts four (4) XFP 10GigE Optics Modules.

MDA - 7750 SR 1-PT 10G MDA-XP - XFP 7750 SR 1-Port 10GBASE Ethernet MDA-XP. Accepts One (1) XFP 10GigE Optics Modules. (Supported on 3HE00229AB and 3HE03620AA)

Channelized MDAs

MDA - 7750 SR 4-PT CH OC3/STM1 ASAP SFP

4-port Channelized OC-3/STM-1 Any Service Any Port (ASAP) MDA. Supported on IOM2-20G and IOM3-XP. Supports channelization down to DS0 and ATM/FR/PPP encapsulations, accepts four (4) OC-3/STM-1 SFP Optics Modules.

MDA - 7750 SR 1-PT CH OC12/STM4 ASAP SFP

1-port Channelized OC12/STM4 Any Service Any Port (ASAP) MDA. Supported on IOM2-20G and IOM3-XP. Supports channelization down to DS0, accepts one (1) OC-12/STM-4 SFP Optics Modules.

MDA - 77x0 SR 12-PT DS3/E3 ASAP

12-port Channelized DS3/E3 (DS0) Any Service Any Port (ASAP) MDA. Supported on IOM2-20G and IOM3-XP. Supports channelization down to DS0, twenty-four (24) 1.0/2.3 connectors, no cables, accepts up to twenty-four (24) DS3/E3 coax patch cables.



MDA - 77x0 SR 4-PT CH DS3/E3 ASAP

4-Port Channelized DS3/E3 (DS0) Any Service Any Port (ASAP) MDA. Supported on IOM2-20G and IOM3-XP. Supports channelization down to DS0, eight (8) 1.0/2.3 connectors, no cables, accepts up to eight (8) DS3/E3 coax patch cables.

Circuit Emulation MDAs

MDA - 7750 SR 1-PT CH OC3/STM1 CES 1-port Channelized OC-3/STM-1 Circuit Emulation Services (CES) MDA, supports channelization down to DS0, accepts one (1) OC-3/STM-1 SFP Optics Modules (Supported on IOM-2 only 3HE01473AA)

MDA - 7750 SR 4-PT CH OC-3/STM-1 CES

4-Port Channelized OC-3/STM-1 Circuit Emulation Services (CES) MDA, supports channelization down to DS0, accepts four (4) OC-3/STM-1 SFP Optics Modules (Supported on 3HE01473AA - IOM-2 and 3HE03619AA - IOM3-XP)

MDA 7750 SR 1-PORT CH OC-12/STM-4 CES

1-port Channelized OC-12/STM-4 Circuit Emulation Services (CES) MDA, supports channelization down to DS3, accepts up to one (1) OC-12/STM-4 SFP Optics Modules

SONET and ATM MDAs

MDA - 7750 SR 8-PT OC3/STM1 SFP 8-port SONET/SDH OC-3c/STM-1c MDA, accepts up to eight (8) OC-3/STM-1 SFP Optics Modules

MDA - 7750 SR 16-PT OC-3/STM1 SFP 16-port SONET/SDH OC-3c/STM-1c MDA, accepts up to sixteen (16) OC-3/STM-1 SFP Optics Modules

MDA - 7750 SR 16-PT ATM OC3C SFP 16-port ATM OC-3c/STM-1c MDA, accepts up to sixteen (16) OC-3/STM-1 SFP Optics Modules

MDA - 7750 SR 8-PT OC3/12-STM1/4 SFP

8-port SONET/SDH OC-12c/STM-4c MDA, each port can operate as OC-12c/OC-3c or STM-4c/STM-1c, accepts up to eight (8) OC-12/STM-4, OC-3/STM-1 SFP Optics Modules

MDA - 7750 SR 16-PT OC3/12-STM1/4 SFP

16-port SONET/SDH OC-12c/STM-4c MDA, each port can operate as OC-12c/OC-3c or STM-4c/STM-1c, accepts up to sixteen (16) OC-12/STM-4, OC-3/STM-1 SFP Optics Modules

MDA - 7750 SR 4-PT ATM OC3/OC12C SFP

4-port ATM OC-3/12c/STM-1/4c MDA, accepts up to four (4) OC-3/12/STM-1/4 SFP Optics Modules

MDA - 7750 SR 2-PT OC48/STM16 SFP 2-port SONET/SDH OC-48c/STM-16c MDA, accepts up to two (2) OC-48/STM-16 SFP Optics Modules

MDA - 7750 SR 4-PT OC48/STM16 SFP 4-port SONET/SDH OC-48c/STM-16c MDA, accepts up to four (4) OC-48/STM-16 SFP Optics Modules

MDA - 7750 SR OC-192C/STM-64C SR-1 1-port SONET/SDH OC-192c/STM-64c MDA with SR-1 / I-64.1 optics, 1310 nm, Simplex SC Connector

MDA - 7750 SR OC-192C/STM-64C IR-2 1-port SONET/SDH OC-192c/STM-64c MDA with IR-2 / S-64.2 optics, 1550 nm, Simplex SC Connector

MDA - 7750 SR 1-PT OC192/STM64 LR-2 1-port SONET/SDH OC-192c/STM-64c MDA with LR-2 / L-64.2 optics, 1550 nm, Simplex SC Connector

Ethernet MDAs

MDA - 7750 SR 60-PT 10/100TX RJ21 60-port 10/100BASE-T MDA, five (5) mini-RJ21 connectors, no cable, accepts up to five (5) MINI-RJ21 cable assemblies

MDA - 7750 SR 20-PT 100FX SFP 20-port 100BASE-FX MDA, requires optics, accepts up to twenty (20) SFP-100FX-xx Optics Modules

MDA - 7750 SR 1-PT 10GBASE-LW/LR 1-port 10GBASE-LW/LR Ethernet MDA, WAN/LAN PHY, 1310 nm, Simplex SC Connector

MDA - 7750 SR 1-PT 10GBASE-EW/ER 1-port 10GBASE-EW/ER Ethernet MDA, WAN/LAN PHY, 1550 nm, Simplex SC Connector

MDA - 7750 SR 20-PT 10/100/1000 20-Port 10/100/1000BASE-TX MDA

MDA - 7750 SR 2-PT 10GBASE XFP 2-port 10GBASE Ethernet MDA, LAN PHY, requires optics, accepts up to two (2) XFP Optics Module



MDA - 7750 SR 20-PT GIGE SFP 20-port Gigabit Ethernet MDA, requires SFP modules, accepts up to twenty (20) GigE SFP Modules, 10/100/1000TX operation with GigE-T SFP

MDA - 7750 SR 1-PT 10GBASE-ZW/ZR 1-port 10GBASE-ZW/ZR (80 km) Ethernet MDA, WAN/LAN PHY, 1550 nm, Simplex SC Connector

MDA - 7750 SR 1-PT 10GBASE XFP 1-port 10GBASE Ethernet MDA, LAN PHY,requires optics, accepts up to one (1) XFP Optics Module

MDA - 7750 SR 5-PT GIGE-B SFP 5-port Gigabit Ethernet Optical MDA Rev B, requires optics, accepts up to five (5) GigE SFP Optics Modules, 10/100/1000TX operation with GigE-T SFP

MDA - 7750 SR 10-PT GIGE-B SFP 10-port Gigabit Ethernet Optical MDA Rev B, requires optics, accepts up to ten (10) GigE SFP Optics Modules, 10/100/1000TX operation with GigE-T SFP

MDA - 7750 SR 10G+GIGE XFP/SFP

1-port 10GBASE (LAN PHY) + 10-port Gigabit Ethernet MDA, requires optics, accepts accepts one (1) XFP Optics Module and up to ten (10) GigE SFP Optics Modules, 10/100/1000TX operation with GigE-T SFP

MDA - 7750 SR 10G TUN ZW/R 1-port 10GBase DWDM Tunable MDA - LC connector. Full C-Band Tunable, supports FEC, EFEC.

Appendix C Glossary

Apipe ATM VLL

Cpipe Circuit VLL

dot1p Ethernet 802.1p field

DSCP Differentiated Service Code Point

Epipe Ethernet VLL

EXP Experimental bits in the MPLS shim header

FC Forwarding Class

IDU (MPR) InDoor Unit

LDP Label Distribution Protocol

LTE Long-Term Evolution

MPLS Multiprotocol Label Switching

MTSO Mobile Telephone Switching Office

ODU (MPR) OutDoor Unit

PoP Point of Presence

QoS Quality of Service

T-LDP Targeted LDP

ToS Type of Service

UMTS Universal Mobile Transmission System



VLL Virtual Leased Line

VPLS Virtual Private LAN Service

VPRN Virtual Private Routed Network

Appendix D References

Appendix E History

Date Version Name(s) Comments



Appendix F Lab validation

F.1 ATM Interworking Solution This section describes ATM interworking topology used to validate the Alcatel-Lucent 7750 SR with the 9500 MPR ATM services as depicted in Figure 5 . Different topologies are possible for the Mobile Backhaul solution using ATM PW, but we believe this one would be the most complex to achieve since it offer the most amount of protection via PW redundancy, MC-LAG and MC-APS. Testing was performed in the IPD Mobile Solutions Lab, located in Ottawa Canada, during the July of 2009 time period. Note: 7670 ESE ATM Switches are used to emulate the Cell Site and Switching Centre equipment in the following figure.

Working

circuit

Protecting

circuit

‘ ”

10.0.0.2

7750 ‘ SR1”

10.0.0.1

7450 “SR5”

SDP2A

SAP1 Epipe2

SDP2B

PWredundancyendpoint

SDP2A

SAP3A

Epipe2

SAP1A

SDP3B

externaljumper

Apipe 3

-

ICB2A

ICB1A

ICB3B

ICB3A

SDP2A

SAP3A

Epipe2

SAP1A

SDP3B

externaljumper

Apipe 3

ICB2A

ICB1A

ICB3B

ICB3A

9500 MPR

Node F (.99)

Endpoint 2AEndpoint 2AEndpoint

3A

Endpoint 1A

Endpoint 3B

Endpoint 3A

Endpoint 1A

Endpoint 3B

Endpoint 2A

GE

9500 MPR

Node C (.117)

6 X E1

ATM/IMAAdtech

ATM Tester

STM1 ATM

vpi/vpi 5/37

7670 ESE

7670 ESE

STM1 ATM

vpi/vpi 1/37

Aps-10:1/37

lag- 20:1000

LAG-1:1000

1/2/14:105

1/2/19

1/2/11:xxx

2/2/18

sdp 3:3

sdp 4:3

sdp 3:3

sdp 20:6

sdp 20:4

sdp 20:3

sdp 4:3

sdp 20:5

sdp 20:4

sdp 20:3

lag- 10:1000lag- 20:1000

11.0.0.153

11.0.0.150

sdp 20:6

sdp 7:1000

sdp 20:5

sdp 7:1000

Access MC-LAG

LAG 10 activeNetwork

LAG 20

network

LAG 20Access MC-LAG

LAG 10 standby7750 SR2

Inter Chassis links

Aps-10:1/37

Figure 5 Lab Network ATM PW Setup

F.1.1 7750/7450 SETUP For details configuration on IPD equipment see in the Errore. L'origine riferimento non è stata trovata. configuration files section:

• SR1/SR2 o interface "MPR9500" o static-lsp "ATM_Interworking" o Lag10, Lag20



o Apipe 3, Apipe 6 o Epipe 2, Epipe 888

• SR5 o Epipe 2, Epipe 888

Related CLI Commands:

Show lag show lag 10 detail show lag 20 detai show redundancy multi-chassis all show redundancy multi-chassis sync peer 10.0.0.2 detail show redundancy multi-chassis mc-lag peer 10.0.0.2 show redundancy multi-chassis mc-lag peer 10.0.0.2 statistics /tools perform lag force lag-id 10 standby /tools perform lag clear lag-id 10 /tools dump lag lag-id 10 show router ldp bindings service-id 2 show service id 2 endpoint show service id 2 label show service id 2 all show router mpls lsp LSP_SR1_SR5 path loose detail show router mpls bypasss-tunnel show router mpls bypass-tunnel protected-lsp detail show router mpls lsp activepath /oam lsp-ping LSP_SR1_SR5 detail show router arp show aps show aps aps-10 detail /perform dump aps aps-10

F.1.2 Failure Scenarios Validation Test conditions are:

• Network Synchronization as per Model A in section F.4

• Network interfaces on 7750 SR1 and SR2 facing 9500 MPR (i.e. LAG 20:1000 in diagram above) are manually configured to use the same mac addresses. Static arp is provisioned for the mac address of the closest 9500 MPR (Node F in diagram above). This mac address must have the multiclass bit enabled.

• Access interfaces on 7450 SR5 attached to 9500 MPR is a LAG (i.e. Port is configure Ethernet no autonegotiate in the diagram above)

• ATM traffic (MPLS), TDM (MEF8) and ETH traffic were on same physical port to the MPR 9500

• In this solution ATM traffic is carried via A-Pipe terminate on a MC-APS STM1 pair on the 7750 SR1/SR2 and the other side terminate on the MPR9500 E1 IMA ports (6 ports in the IMA group).

o A-Pipe 3: 60 cell/s on VC 1/37 transmitted in bidirectional



o A-Pipe 6: 4095 cells on VC 1/38 transmitted in bidirectional

• Ethernet Pseudowire redundancy and MC-Lag was used for resiliency. RSVP-TE and TLDP was used for signaling in the dynamic portion of the network with OSPF(E-pipes). MPLS static LSP label and static Pseudowire label are used for the A-Pipe data to the 9500 MPR via this Ethernet Pseudowire.

• 1 tunnel only (Static LSP 64 over one Vlan 1000)

The results are:

• “zero errors” for 72 hours on the ATM , TDM and ETH tarffic

• Failure analysis:

Test # Description

Cells lost on VC

1/37 from MPR to SR

Cells lost on VC

1/37 from SR to MPR

Cells lost on VC

1/38 from MPR to SR

Cells lost on VC

1/38 from SR to MPR

PASS or FAIL

1 Fail Active Working APS port: Remove cable on SR1

0 0 14 25 PASS

2 Restore Active Working APS port

1 0 12 82 PASS

3 Fail 1 of 2 LAG Ports: Remove one of two LAG cables on SR1

0 22 2 4 PASS

4 Fail 2 of 2 LAG Ports: Remove the next LAG cable on SR1

1002 1004 68418 68518 PASS*

5 Restore 1 of 2 down LAG ports: Replace one of two LAG cables on SR1

24 24 1618 1622 PASS*

6 Restore 1 of 2 down LAG ports: Replace last LAG cable on SR1

0 14 0 2 PASS

7 Break LSP Path between SR1 and SR5: remove cable between SR1 and SR5 to break the primary path of the LSP

2 1 120 110 PASS

8 Restore LSP path between SR1 and SR5: Replace the cable to restore the primary path of the LSP

0 0 0 0 PASS

9 Fail Active Working APS and LAG on SR1: Remove APS Active Working Cable and both cables of LAG on SR1

1365 1341 93130 94671 PASS*

10 Restore cables removed in above test

1739 1739 118692 118727 PASS*



11 Remove APS Active Working Cable and cable between SR1/SR5 to break the primary path of the LSP

3 2 234 188 PASS

12 Restore cables removed in above test

0 1 10 9 PASS

13 Shutdown ATM SAP (on Apipe 6 on SR1) while active working aps circuit

0 0 100% loss and OAM F5 cells

100% loss PASS

14 Remove ATM SAP shutdown

0 0 0 0 PASS

15 Failure interchassis link: remove cable between SR1 and SR2

0 (Secondary path down on LSP)




PASS

16 Restore interchassis link 0 0 0 0 PASS

17 CPM switchover 1475 1482 101104 100714 PASS*

18 Admin reboot node 1319 1319 90039 90034 PASS*

19 Node Restore 1237 1235 84460 84357 PASS*

20 Power Off node 568 570 38830 38860 PASS*

21 Power On node 1368 1373 93418 93715 PASS*

22 Holdover Test 24H: shutdown Epipe 888 that supply sync for E1port on MPR-C

0 0 0 0 PASS

• *Note: Expected behavior with current release. REF82795 in release 7.0.R6 will improve performance from random 0-30 seconds to 1-2 seconds for static LSP setup.



F.2 TDM Interworking Solution This section describes TDM interworking topology used to validate the Alcatel-Lucent 7750 SR with the 9500 MPR TDM services as depicted in Figure 6: Lab Network TDM PW Setup. Different topologies are possible for the Mobile Backhaul solution using TDM PW, but we believe this one would be the most complex to achieve since it offer the most amount of protection via PW redundancy and MC-APS. Testing was performed in the IPD Mobile Solutions Lab, located in Ottawa Canada, during the August of 2009 time period.

Figure 6: Lab Network TDM PW Setup

F.2.1 7750/7450 SETUP For details configuration on IPD equipment see Aps-11, Aps-12, Epipe 889 in SR1/SR2 and Epipe 889 in SR5 in the Errore. L'origine riferimento non è stata trovata. configuration files section. Related CLI Commands:

show router ldp bindings service-id 889 show service id 889 endpoint show service id 889 label show service id 889 all



show router mpls lsp LSP_SR1_SR5 path SR5 detail show router mpls bypasss-tunnel show router mpls bypass-tunnel protected-lsp detail show router mpls lsp activepath /oam lsp-ping LSP_SR1_SR5 detail show router arp show aps show aps aps-11 detail show aps aps-12 detail /perform dump aps aps-11 /perform dump aps aps-12


• Network Synchronization is achieved by a synch distribution through a TDM E1 signal encapsulated over MEF-8 with ACR (Adaptive Clock Recovery) as per Model B in section F.5.

• Access interfaces on 7450 SR5 facing 9500 MPR is a LAG (i.e. Port is configured with Ethernet autonegotiate disabled in the diagram above)

• ATM traffic (MPLS), ETH and TDM (MEF8) traffic were on same physical port to the MPR 9500

• In this solution TDM traffic is carried via E-Pipe encapsulated over MEF-8 terminate on a MC-APS CES STM1 pair on the 7750 SR1/SR2 and the other side terminate on the MPR9500 E1 TDM ports.

o E-Pipe 889: E1 un-frame CES Channel bidirectionnel

• Traffic is loopback on APS-12.1.1.2.1

• ANT-20 is injecting a Bert pattern

• Ethernet Pseudowire redundancy and MC-APS CES was used for resiliency. RSVP-TE and TLDP was used for signaling in the dynamic portion of the network with OSPF (E-pipes). MPLS static LSP label and static Pseudowire label are used for the A-Pipe data to the 9500 MPR via this Ethernet Pseudowire.

The results are:

• “zero errors” for 72 hours on the TDM, ATM and ETH traffic


Test # Description

ANT-20 APS-Times

Measurement

PASS or FAIL

1 Fail Active Working APS port: Remove cable on SR1

218 ms PASS



2 Restore Active Working APS port

67 ms PASS


35 ms PASS


0 PASS

5 Shutdown TDM SAP (on Epipe 889 on SR1) while active working aps circuit

100% loss (AIS)

PASS

6 Remove TDM SAP shutdown

0 PASS


0 (Secondary path down on

LSP)

PASS

8 Restore interchassis link

0 PASS

9 CPM switchover 0 PASS

10 Admin reboot node 193 PASS*

11 Node Restore 251 PASS*

12 Power Off node 92 PASS*

13 Power On node 187 PASS*

*: Simulated APS had to be replaced with a real node with APS (7710 with 2 CES card)



F.3 Ethernet Interworking Solution This section describes ETH interworking topology used to validate the Alcatel-Lucent 7750 SR with the 9500 MPR ETH services as depicted in Figure 7: Lab Network ETH PW Setup. Testing was performed in the IPD Mobile Solutions Lab, located in Ottawa Canada, during the August of 2009 time period.

F.3.1 7750/7450 SETUP For details configuration on IPD equipment see Epipe 890, Epipe 891 in SR1/SR2 and Epipe 890 in SR5 in the Errore. L'origine riferimento non è stata trovata. configuration files section. Related CLI Commands:

show router ldp bindings service-id 890 show service id 890 label show service id 890 all show router mpls lsp LSP_SR1_SR5 path loose detail show router mpls bypasss-tunnel show router mpls bypass-tunnel protected-lsp detail

SR1”

7450 “SR5”

SDP

SAP Epipe 890

SDP

-

9500 MPR

Node F (.99)

GE

9500 MPR Node C (.117)

Port 2 GE ETH

Lag-1:3002

1/2/14:105

1/2/19

1/2/11:105

2/2/18

sdp 4:890

sdp 4:890

2/2/13:3002

11.0.0.153

11.0.0.150

Inter Chassis links

7750 SR1 10.0.0.1

7750 SR2 10.0.0.2

2/2/12

SAP

Epipe 890

2/2/13

Epipe 891

SAP

SAP

2/2/12:3003

2/2/12:3002

IXIA Vlan3002-Vlan3003

Figure 7: Lab Network ETH PW Setup


• Access interfaces on 7450 SR5 facing 9500 MPR is a LAG (i.e. Port is configure Ethernet no autonegotiate in the diagram above)

• ATM traffic (MPLS), ETH and TDM (MEF8) traffic were on same physical port to the MPR 9500



• In this solution ETH traffic is carried via E-Pipe terminating on 7750 SR1 and the other side terminates on SR5. Ethernet traffic travel over microwave link and is deliver to ETH port on MPR-C.

• E-Pipe 890: IXIA generate 100Mbits/sec of random packets of 64-1500 bytes on Vlan 3002.

• E-Pipe 891: IXIA generate 100Mbits/sec of random packets of 64-1500 bytes on Vlan 3003. The SAP to SAP connection converts Vlan 3003 to Vlan 3002 to be delivered to the ETH port on the MPR9500.

• RSVP-TE and TLDP was used for signaling in the dynamic portion of the network with OSPF (E-pipes). MPLS static LSP label and static Pseudowire label are used for the A-Pipe data to the 9500 MPR via this Ethernet Pseudowire.

The results are:

• “zero errors” for 72 hours on the ETH, ATM and TDM traffic


Test # Description

IXIA packet

lost from 9500��SR1

IXIA packet lost from SR1��9500

PASS or FAIL


464 442 PASS


0 0 PASS

3 Shutdown ETM SAP (on Epipe 890 on SR1)

100% loss 100% loss PASS

4 Remove ETH SAP shutdown

0 0 PASS




PASS

6 Restore interchassis link 0 0 PASS

7 CPM switchover 0 0 PASS



F.4 Network Synchronization Model A – MEF8 ACR with RF Clock Distribution

This section describes one topology used to validate the Alcatel-Lucent 7750 SR with the 9500 MPR MEF8 interworking for synchronization. Different methods are possible for synchronize the 9500 MPR from SR 7750, but we believe this one would be the most complex to achieve since some interop is required. Testing was performed in the IPD Mobile Solutions Lab, located in Ottawa Canada, during the July of 2009 time period.

has loopback line

E1E1/MEF-8/ E- pipeE1 MEF-8

ACR

NEC

RF clock distribution(no impact on radio BW)

NEC

Retiming

ANT-20 # 1

Epipe 888:sap 4/2/1.1.1.1.1Spoke sdp 4:888

CEM MDA:ACR MasterMAC: 00:21:05:87:95:80

Stratum 2 Common Reference Clock

2. 048 Mhtz

7750

Port 3

4/2/1CEM

BITS

CEM 5/2/1

5/2/1.1.1.1

MEF8 MEF8

GE

7450

SR5 SR1

Epipe 888:sap 1/1/1:3000Spoke sdp 4:888

1/2/19GE

Microwavenetwork

9500 9500 MPR-C

E1ATM

Epipe 888

2/2/18

MPR-F138.120.195.99138.120.195.117

Physical loopback on MEF8 TDM Port

Figure 8 Network Synchronization using MEF8

F.4.1 MPR Setup TDM flows are of type TDM2ETH and are MEF8 compliant (256 bytes, packet jitter buffer set to 5 ms). Adaptive clock recovery is configured on 9500 MPR-F and Node timing on 7750 SR flow with RTP disabled. The 9500 MPR-F is configured as Master and Primary Source is E1 Slot#5 Port#1 where TDM2ETH flow terminate. The 9500 MPR-C is configured as Slave and Primary Source is Radio Dir#3 Ch#1. A physical loopback is required on the E1 Port#1 on MPR-F. The mate circuit in SR1 (lower CEM card in Figure 8) must be configure channelized. The connection to the packet network is through a Gigabit Ethernet port of Core board.

F.4.2 7750/7450 SETUP TDM flows are of type MEF8 with RTP disabled (256 bytes, packet jitter buffer set to 5 ms). For details configuration on IPD equipment see Epipe 888 in SR1/SR2 and SR5 in the Errore. L'origine riferimento non è stata trovata. configuration files section. Related CLI Commands:



/show mda 4/2 /configure port 4/2/1 /show service id 888 all /clear port 1/1/1 statistics /clear service statistics id 888 counters /clear service statistics id 888 cem /monitor port 1/1/1 interval 3 repeat 999 rate /monitor service id 888 sap 4/2/1.1.1.1.1 rate repeat 999 interval 11

F.4.3 Tests and Results Test Results

Verify basic MEF-8 Interoperability under normal operating conditions Pass

Verify that the Sync Out Port on the first MPR (MPR-F) meets the ITU-T E1 SEC Network Interface (G.823) mask over a 12 hour time interval.

Pass See Figure 9 for

details

Verify that the Sync Out Port on the second MPR (MPR-C) meets the ITU-T E1 SEC Network Interface (G.823) mask over a 12 hour time interval.


details

Verify that an E1 ATM port on the 9500 MPR meets the ITU-T E1 SEC Network Interface (G.823) mask over a 48 hour time interval with ATM PW traffic (1.75 Mb/sec) as background traffic.


details

Note: We notice (on MPR 95000) the E1 port# XX – Rx and E1 port# XX – TX is in AlarmAIS (with physical loopback) when the far-end (on SR 7750 APS-12) is configure as E1-unframed. To eliminate this problem we configure the E1 to be channelized.

F.4.4 Clocking Measurements

F.4.4.1 E1 Clock Recovery Measurement no microwave hop

To verify that the 9500 MPR adaptive clock recovery performance meets the ITU-T E1 SEC Network Interface (G.823) mask the Sync Out Port on the first 9500 (MPR-F) is fed into an ANT-20. A BITS Stratum 1 source is fed into the 7750 and the CES ports are node-timed. The ANT-20 uses the same Stratum 1 source. The timing is measured over a 12 hour test interval; the resulting MTIE analysis provided in Figure 9 shows that the 9500 MPR successfully meets the traffic mask.



Figure 9 - MTIE Analysis for 9500 MPR Adaptive Clock Recovery

F.4.4.2 E1 Clock Recovery Measurement one microwave hop

To verify that the 9500 MPR adaptive clock recovery performance meets the ITU-T E1 SEC Network Interface (G.823) mask the Sync Out Port on the second 9500 MPR (MPR-C) is fed into an ANT-20. A BITS Stratum 1 source is fed into the 7750 and the CES ports are node-timed. The ANT-20 uses the same Stratum 1 source. The timing is measured over a 12 hour test interval; the resulting MTIE analysis provided in the above Figure 9 shows that the 9500 MPR successfully meets the traffic mask.

F.4.4.3 E1 Clock Recovery Measurement with Background Traffic on ATM port

To verify that the 9500 MPR adaptive clock recovery performance meets the ITU-T E1 SEC Network Interface (G.823) mask on the E1 ATM Port on the second 9500 MPR (MPR-C) is fed into an ANT-20. A BITS Stratum 1 source is fed into the 7750 and the CES ports are node-timed. The ANT-20 uses the same Stratum 1 source. The timing is measured over a 72 hour test interval; the resulting



MTIE analysis provided in the Figure 10 shows that the 9500 MPR successfully meets the traffic mask. The background traffic sent over the microwave link is the following: A-pipe3�60 cells/sec (25.4 Kbits/s over VC 1/37), A-pipe6�4095 cells/sec (1.736 Mbits/sec over VC 1/38), Epipe 888 an E1 un-frame(1 000 packets/sec of 286 bytes), Epipe 889 E1 un-frame (1 000 packets/sec of 286 bytes), E-pipe 890 (15964 packets/sec for 12490171 bytes/sec) for a total of 13350405 bytes/sec 20072 packets/sec or utilization of 10.68% of the GE link.

Figure 10 - MTIE Analysis for 9500 MPR ATM Port with Background Traffic



F.5 Network Synchronization Model B – End to End MEF8 ACR This section describes second topology used to validate the Alcatel-Lucent 7750 SR with the 9500 MPR MEF8 interworking for synchronization as depicted in Figure 11 Network Synchronization using MEF8 all the way. Different topologies are possible for the Mobile Backhaul solution using TDM PW, but we believe this one would be the most complex to achieve since it offer the most amount of protection via PW redundancy and MC-APS. Testing was performed in the IPD Mobile Solutions Lab, located in Ottawa Canada, during the August of 2009 time period.

Figure 11 Network Synchronization using MEF8 all the way

F.5.1 MPR Setup TDM flows are of type TDM2ETH and are MEF8 compliant (256 bytes, packet jitter buffer set to 5 ms). Adaptive clock recovery is configured on 9500 MPR-C and Node timing on 7750 SR flow with RTP disabled. The connection to the packet network is through a Gigabit Ethernet port of Core board.



F.5.4.1 E1 Clock Recovery Measurement with TDM, ATM and ETH Background Traffic on a single port to the MPR9500

To verify that the 9500 MPR adaptive clock recovery performance meets the ITU-T E1 SEC Network Interface (G.823) mask on the E1 TDM Port on the second 9500 MPR (MPR-C) is fed into an ANT-20. A BITS Stratum 1 source is fed into the 7750 and the CES ports are node-timed. The ANT-20 uses the same Stratum 1 source. The timing is measured over a 72 hour test interval; the resulting MTIE analysis provided in the Figure 10 shows that the 9500 MPR successfully meets the traffic mask. The background traffic sent over the microwave link is the following: A-pipe3�60 cells/sec (25.4 Kbits/s over VC 1/37), A-pipe6�4095 cells/sec (1.736 Mbits/sec over VC 1/38), Epipe 888 an E1 un-frame(1 000 packets/sec of 286 bytes), Epipe 889 E1 un-frame (1 000 packets/sec of 286 bytes), E-pipe 890 (15964 packets/sec for 12490171 bytes/sec) for a total of 13350405 bytes/sec 20072 packets/sec or utilization of 10.68% of the GE link.

Figure 12 - MTIE Analysis for 9500 MPR TDM Port with Background Traffic



F.6 MPR 9500, 7705 and 7750 ATM, ETH and TDM Interworking Solution

This section describes the use of SAR 7705 in the topology used to validate the Alcatel-Lucent 7750 SR with the 9500 MPR multi-services as depicted in Figure 13 Lab Network with 7705 for ATM. Refer to Figure 6: Lab Network TDM PW Setup, Figure 7: Lab Network ETH PW Setup and replaced the SR 7450 with a SAR 7705. Testing was performed in the IPD Mobile Solutions Lab, located in Ottawa Canada, during the August of 2009 time period. Note: 7670 ESE ATM Switches are used to emulate the Cell Site and Switching Centre equipment in the following figure.

Figure 13 Lab Network with 7705 ATM PW

F.6.1 7750/7705 SETUP For details configuration on IPD equipment see in the Errore. L'origine riferimento non è stata trovata. configuration files section.

F.6.2 Validation Scenario Test conditions are:

• Network Synchronization as per Model A in section F.4



• Network interfaces on 7750 SR1 and SR2 facing 9500 MPR (i.e. port 20:1000 in diagram above) are manually configured to use the same mac addresses. Static arp is provisioned for the mac address of the closest 9500 MPR (Node F in diagram above). This mac address must have the multiclass bit enabled.

• Access interfaces on 7705 SAR205 attached to 9500 MPR is a port (i.e.LAG not supported on 7705)

• ATM traffic (MPLS), TDM (MEF8) and ETH traffic were on same physical port to the MPR 9500

• In this solution ATM traffic is carried via A-Pipe terminate on a MC-APS STM1 pair on the 7750 SR1/SR2 and the other side terminate on the MPR9500 E1 IMA ports (6 ports in the IMA group).

o A-Pipe 3: 60 cell/s on VC 1/37 transmitted in bidirectional o A-Pipe 6: 4095 cells on VC 1/38 transmitted in bidirectional

• In this solution TDM traffic is carried via E-Pipe encapsulated over MEF-8 terminate on a MC-APS CES STM1 pair on the 7750 SR1/SR2 and the other side terminate on the MPR9500 E1 TDM ports.

o E-Pipe 889: E1 un-frame CES Channel bidirectionnel

• ANT-20 is injecting a Bert pattern

• In this solution ETH traffic is carried via E-Pipe terminating on 7750 SR1 and the other side terminates on SAR205. Ethernet traffic travel over microwave link and is deliver to ETH port on MPR-C.

• E-Pipe 890: IXIA generate 100Mbits/sec of random packets of 64-1500 bytes on Vlan 3002.

• E-Pipe 891: IXIA generate 100Mbits/sec of random packets of 64-1500 bytes on Vlan 3003. The SAP to SAP connection converts Vlan 3003 to Vlan 3002 to be delivered to the ETH port on the MPR9500.

• Ethernet Pseudowire redundancy and MC-Lag was used for resiliency. RSVP-TE and TLDP was used for signaling in the dynamic portion of the network with OSPF(E-pipes). MPLS static LSP label and static Pseudowire label are used for the A-Pipe data to the 9500 MPR via this Ethernet Pseudowire.

• 1 tunnel only (Static LSP 64 over one Vlan 1000)

The results are:

• “zero errors” for 72 hours on the ATM , TDM and ETH traffic



F.7 Transfer Delay Measurement The purpose of this test is to measure Transfer Delay between ATM ports on 9500 MPR and SR port on 7750 using Adtec. Measurements taken are for each VC in both directions. This included 7670 ESE delay.

Figure 14: From 9500 MPRIMA to SR1 ATM Port VC 1/37

Figure 15: From SR1 ATM Port to 9500 MPR IMA VC 1/37



Figure 16: From 9500 MPR IMA to SR1 ATM Port VC 1/38

Figure 17: From SR1 ATM Port to 9500 MPR IMA VC 1/38

IPD WT IW Internal Use

Documents

Transcript of IPD WT IW Internal Use