e-line, e-lan, e-tree on alu routers -indosat oct2011

Ethernet services on ALU routers – from Indosat network audit, Oct 2011

Alcatel-Lucent, Indosat and Datacomm CONFIDENTIAL /15

1 ETHERNET SERVICES ON ALU ROUTERS

The Indosat network has over 16,000 service access points on Alcatel-Lucent (ALU) routers, where customers connect via Ethernet, ATM or TDM. With the growth in Metro Ethernet services, Indosat requested this document to describe how Metro Ethernet Forum (MEF) terms E-Line, E-LAN and E-Tree relate to services configured on the ALU network:

• ELINE = E-Line = VLL (Virtual Leased Line) = point-to-point “wire” o Configured on ALU routers as an Epipe (Ethernet pipe) o Transparent Layer 2 access service: Ethernet frame in, Ethernet frame out

• ELAN = E-LAN = multipoint-to-multipoint LAN = any-to-any Ethernet bridging service o Configured as a VPLS (Virtual Private LAN Service) o VPLS learns MAC addresses and distributes Ethernet frames as on a LAN segment

• ETREE = E-Tree = point-to-multipoint VPN = hub & spoke service o Configured as a VPLS with settings to direct traffic from “root” to “leaves”

Figure 1 – E-Line, E-LAN, E-Tree overview

Some variations on the above terminology:

Service type Traffic flow

“Private” version if access is a whole port

“Virtual Private” version if access is a VLAN

Configure on ALU routers

E-Line Point-to-point EPL Ethernet Private Line

EVPL Ethernet Virtual Private Line E-pipe

E-LAN Multipoint-to-multipoint EP-LAN Ethernet Private LAN

EVP-LAN Ethernet Virtual Private LAN VPLS

E-Tree Point-to-multipoint EP-Tree Ethernet Private Tree

EVP-Tree Ethernet Virtual Private Tree VPLS

Table 1 – E-Line, E-LAN, E-Tree definitions

ALU IP/MPLSnetwork

A B EpipeEpipe = A B ELINE:

A B VPLSVPLS = A B ELAN:

C

VPLS

C

A B VPLSVPLS = B ETREE:

C

VPLS

C

Root Leaf

Leaf

With split horizon, etc.

A



As noted in Table 1 above, an E-Line may be referred to as an EPL if the customer access point is the whole Ethernet port, or an EVPL if there are many customers multiplexed via VLANs onto the same physical port. Both are Epipes in the ALU configuration, and the only difference is in whether the SAP (service access point) is tied to a VLAN number or not. The same is true for VPLS, with ELAN variations “EP-LAN” vs. “EVP-LAN”, and ETREE variations “EP-Tree” vs. “EVP-Tree”.

Note it is also possible to combine an Epipe & VPLS in a backhaul scenario. For example, a VPLS might be configured on a few central nodes, and many remote sites have Epipe spokes into the VPLS.

Examples of these Epipe & VPLS scenarios are shown in the diagram below.

7750

7705

SAP1/1/7

7750

SAP1/1/1

GE port

7705

SAP1/1/7

7750

VPLS 555

SAP1/1/5

Ethernet Ethernet

7750

GE portE-Line = Epipe“EPL” if one port per Epipe,“EVPL” if one VLAN per Epipe

SAP1/2/8:1001/2/8:200

VLAN 100

VLAN 200

SAP1/5/1:100

Epipe 20

Epipe 20

VLAN 100

Epipe 30VLAN 200

SAP1/2/3:200

7450

ALU IP/MPLS network

E-LAN = VPLSE-Tree = VPLS

7450

SAP1/1/2

7750

SAP1/1/4

Ethernet Ethernet

7750VPLS 100

Combination:backhaul via Epipe to VPLS

Epipe 10 Epipe 10

VPLS 100 VPLS 100

Epipe 40 VPLS 555 VPLS 555

Epipe 30

7750

7705

SAP1/1/7

7750

SAP1/1/1

GE port

7705

SAP1/1/7

7750

VPLS 555

SAP1/1/5

Ethernet Ethernet

7750

GE portE-Line = Epipe“EPL” if one port per Epipe,“EVPL” if one VLAN per Epipe

SAP1/2/8:1001/2/8:200

VLAN 100

VLAN 200

SAP1/5/1:100

Epipe 20

Epipe 20

VLAN 100

Epipe 30VLAN 200

SAP1/2/3:200

7450

ALU IP/MPLS network

E-LAN = VPLSE-Tree = VPLS

7450

SAP1/1/2

7750

SAP1/1/4

Ethernet Ethernet

7750VPLS 100

Combination:backhaul via Epipe to VPLS

Epipe 10 Epipe 10

VPLS 100 VPLS 100

Epipe 40 VPLS 555 VPLS 555

Epipe 30

Figure 2 – Examples of Epipe and VPLS services

1.1 Configuring Epipes & VPLS on ALU hardware

The Indosat network has 421 ALU routers/switches of 11 chassis types from 5 main families:

ALU node family # nodes 7450 ESS – Ethernet Service Switch 1547750 SR – Service Router 817710 SR – Service Router 97705 SAR – Service Aggregation Router 1027250 SAS – Service Access Switch 75Total 421

Table 2 – Count of ALU routers & switches, as of August 2011



7750 SR-7

7710 SR-c127710 SR-c4 7450 ESS-67450 ESS-1 7450 ESS-7

7750 SR-17705 SAR-8

7450 ESS-12

7750 SR-127250 SAS 7750 SR-7

7710 SR-c127710 SR-c4 7450 ESS-67450 ESS-1 7450 ESS-7

7750 SR-17705 SAR-8

7450 ESS-12

7750 SR-127250 SAS

Figure 3 – Alcatel-Lucent routers & switches in the Indosat network

Some hardware considerations:

• Epipe and VPLS services are not configured on 7250, but 7250 can transport traffic from the network edge to an Epipe or VPLS on 7450/7750/7710/7705.

• VPLS is not currently configured on any 7705’s in the network, because 7705 software did not support VPLS until recently. VPLS was introduced in 7705 release 4.0R3.

• Epipes are configured on 7450/7750/7710/7705, with 60% of them on 7750 • VPLS are configured on 7450/7750/7710, with 65% of them on 7750 • Ethernet access ports in the network may be FE (Fast Ethernet, 10/100 Mbps), GE

(Gigabit Ethernet, 1 Gbps), or 10GE (10 Gbps). There are 1186 Ethernet MDAs (Media Dependant Adapter = line cards) in the network, with the following layouts:

MDA type Layout 7450 7750 7710 7705 Total a8-eth 6 x FE + 2 x GE 109 109 a8-ethv2 6 x FE + 2 x GE 4 4 c8-10/100eth-tx 8 x FE 9 9 m60-10/100eth-tx 60 x FE 13 6 19 c1-1gb-sfp 1 x GE 8 8 m5-1gb-sfp-b 5 x GE 37 3 40 m10-1gb-sfp 10 x GE 8 15 23 m10-1gb-sfp-b 10 x GE 312 116 428 m20-1gb-sfp 20 x GE 1 14 15 m20-1gb-tx 20 x GE 69 9 78 m20-1gb-xp-sfp 20 x GE 4 26 30 m1-10gb 1 x 10GE 6 6 m1-10gb-xfp 1 x 10GE 113 22 135 m1-10gb-xp-xfp 1 x 10GE 2 2 m2-10gb-xfp 2 x 10GE 18 18 m2-10gb-xp-xfp 2 x 10GE 18 244 262 Total 546 507 20 113 1186

Table 3 – Ethernet MDA card inventory



As of August 2011 the Indosat network was at 16 different software levels, though this is moving towards 2 main levels: 7705s at 4.0R2, and 7450/7750/7710 at 8.0R11. (The latest available software as of October 2011 is 7705 4.0R5 and 7450/7770/7710 9.0R5.) Some features are not supported on older software levels (e.g., VPLS is not supported on 7705 R3.0), so always consider the software level when planning to deploy new services. Consult the ALU release notes and other manuals for supported features.

1.1 Transport for Epipes & VPLS

The ALU 7450/7750/7710/7705 service architecture involves several components:

SAP (Service Access Point), representing a port, LAG (bundle of ports) or VLAN, bound to:

Service, such as E-pipe or VPLS, bound to:

SDP (Service Distribution Point) via spoke-sdp or mesh-sdp, bound to:

MPLS or GRE tunnels for transport across the network, over OSPF or static routes

The network has over 10,000 service instances, with 14,000 mesh/spoke-sdp’s and over 16,000 SAPs. These are detailed in the Indosat ALU Network Audit report. A general view of how SAPs, Services and SDPs relate is in Figure 4 below, and an example Epipe is in Figure 5.

Figure 4 – SAP, Service, SDP relationships

7450

SAP1/1/1

7750

SAP1/1/2

GE port GE port

over OSPF or static routes

Epipe 10 Epipe 10spoke-sdp

999:10

SDP 999MPLS LSP“jtl-to-kpi”

spoke-sdp888:10

“kpi-to-jtl”

SDP 888

7450

SAP1/1/1

7750

SAP1/1/2

GE port GE port

over OSPF or static routes


999:10

SDP 999MPLS LSP“jtl-to-kpi”

spoke-sdp888:10

“kpi-to-jtl”

SDP 888

Figure 5 – Example of an Epipe showing SAP, spoke-sdp, MPLS LSP



The details of configuring SDPs, MPLS, OSPF, static routes are not covered in this document. Please see the ALU manuals:

• 7750 SR OS Services Guide

• 7750 SR OS MPLS Guide

• 7750 SR OS Routing Protocols Guide

• 7750 SR OS Router Configuration Guide

Also see the Indosat ALU Network Audit Report for how transport is configured in Indosat.

1.2 Epipes for ELINE

There are 300 Epipes in the Indosat network. These are configured on 7450/7750/7710/7705 nodes, with 60% of them on 7750. Configuring an Epipe requires:

• Choose a globally unique number (service-id) to identify the Epipe: 10 in the example below. Do not re-use this service-id anywhere other than the remote end of the Epipe.

• A customer number: 1 here

• Access ports at each end to make the SAPs: port 1/1/1 to 1/1/2 here. The SAP could also be a VLAN, like 1/1/1:100, or a LAG group.

• An SDP, which represents the tunnel to the remote node in one direction. The SDP may use an MPLS RSVP LSP, LDP, or GRE tunnel for transport. Epipes use spoke-sdp’s, numbered as <sdp-id>:<service-id>. For example, spoke-sdp 999:10 below.

• Description and service-name fields are optional, but a good practice to add them. See Section 1.5 about service-name.

• About half of the Epipes in Indosat also specify a service-mtu (like MTU 1418 bytes), though usually it is better to only configure the MTU on the access port, and then let the Epipe pick it up automatically from there. So the example below does not configure any MTU under the Epipe.

One end of Epipe Other end of Epipe configure service epipe 10 customer 1 create description "Epipe Bali-Jakarta" service-name "epipe-downtown-bali-bank" sap 1/1/1 create exit spoke-sdp 999:10 create exit no shutdown exit

configure service epipe 10 customer 1 create description "Epipe Bali-Jakarta" service-name "epipe-downtown-bali-bank" sap 1/1/2 create exit spoke-sdp 888:10 create exit no shutdown exit

Table 4 – Example of configuring an Epipe

7750

SAP1/1/1

7750

SAP1/1/2

GE port GE port

IP/MPLSnetwork


999:10

SDP 999

spoke-sdp888:10

SDP 888

7750

SAP1/1/1

7750

SAP1/1/2

GE port GE port

IP/MPLSnetwork


999:10

SDP 999

spoke-sdp888:10

SDP 888



Here is an example of a live Epipe in the Indosat network:

7750 PLG-A45-PE1-SR12

SAP10/1/2:42(VLAN 42)

7750 PLG-A45-PE2-SR12

SAP10/1/2:42

(VLAN 42)

GE port GE port

IP/MPLSnetwork


4180:801010042

SDP 4180

spoke-sdp4280:801010042

SDP 4280

epipe 801010042 customer 65011 createdescription "service for OMAL BSC-Palembang"sap 10/1/2:42 createexitspoke-sdp 4180:801010042 createexitno shutdown

exit


exit

7750 PLG-A45-PE1-SR12

SAP10/1/2:42(VLAN 42)

7750 PLG-A45-PE2-SR12

SAP10/1/2:42

(VLAN 42)

GE port GE port

IP/MPLSnetwork


4180:801010042

SDP 4180

spoke-sdp4280:801010042

SDP 4280


exit


exit

On 7750 PLG-A45-PE1-SR12: configure service epipe 801010042 customer 65011 create description "service for OMAL BSC-Palembang" sap 10/1/2:42 create exit spoke-sdp 4180:801010042 create exit no shutdown exit

On 7750 PLG-A45-PE2-SR12: configure service epipe 801010042 customer 65011 create description "service for OMAL BSC-Palembang" sap 10/1/2:42 create exit spoke-sdp 4280:801010042 create exit no shutdown exit

1.2.1 Epipe with QoS

Quality of Service (QoS) can be managed by rate-limiting and prioritizing traffic as it enters the network, and queuing & scheduling it appropriately in the core. There are many options for fine-tuning QoS, as described in the 800-page 7750 QoS Guide, but a common one is to rate-limit the traffic coming into an access port.

If a customer has a physical GE port but is only paying for 300Mbps, for example, setting a sap-ingress QoS profile with “rate 300000” (or 300x1024 = “rate 307200”) under the Epipe will ensure any excess traffic is discarded at the access port, thus saving bandwidth in the network core. Or if the customer was paying for 150Mbps committed rate but was allowed to peak to 200Mbps, the sap-ingress QoS profile could be set with “rate 200000 cir 150000”.

Below is an example of an Epipe with QoS profiles added. Note the QoS profile does not need to be the same at the two ends of an Epipe, though it could be.



One end of Epipe Other end of Epipe configure qos sap-ingress 300 create description "Limit to 300Mbps" queue 1 create rate 300000 exit exit configure service epipe 10 customer 1 create description "Epipe Bali-Jakarta" service-name "epipe-downtown-bali-bank" sap 1/1/1 create ingress qos 300 exit exit spoke-sdp 999:10 create exit no shutdown exit

configure qos sap-ingress 200 create description "Committed 150M, peak 200M" queue 1 create rate 200000 cir 150000 exit exit configure service epipe 10 customer 1 create description "Epipe Bali-Jakarta" service-name "epipe-downtown-bali-bank" sap 1/1/2 create ingress qos 200 exit exit spoke-sdp 888:10 create exit no shutdown exit

Table 5 – Example of configuring an Epipe with a QoS profile

There are 7 Epipes in the network using sap-ingress profiles; for example JKT-KPI-CORE epipe 551.

1.2.2 Redundant Epipe

Normally an Epipe is simply point-to-point between 2 SAPs. It is also possible to configure an Epipe that goes from one SAP to up to 4 alternate destination SAPs. To use Epipe Redundancy, configure the source end with two or more spoke-sdp’s, pointing to different nodes. If the first spoke-sdp is unable to reach its destination SAP, the Epipe will swing over to the 2nd spoke-sdp to reach a different node.

Below is an example of a Redundant Epipe. (Note the term “redundant” here refers to having an alternate destination SAP, not to redundancy along the path. All Epipes that are transported over MPLS/LDP/OSPF will automatically reroute around node/link failures in the end-to-end path, if another route exists.)

At one end of Redundant Epipe: configure service epipe 10 customer 1 create description "Epipe Bali-Jakarta with disaster recovery backup" service-name "epipe-downtown-bali-bank" endpoint "main-and-backup" create standby-signaling-master exit sap 1/1/1 create exit spoke-sdp 555:10 endpoint "main-and-backup" create precedence primary exit spoke-sdp 666:10 endpoint "main-and-backup" create precedence 1 exit no shutdown exit



Epipe at the primary destination node: configure service epipe 10 customer 1 create description "Epipe Bali-Jakarta main site" service-name "epipe-downtown-bali-bank" sap 1/1/2 create exit spoke-sdp 888:10 create exit no shutdown exit

Epipe at the secondary destination node (same as above except for SAP): configure service epipe 10 customer 1 create description "Epipe Bali-Jakarta backup site" service-name "epipe-downtown-bali-bank" sap 1/1/5 create exit spoke-sdp 888:10 create exit no shutdown exit

There are 5 Epipes in the Indosat network that have multiple endpoints like this: epipe 5607, 652158, 652159, 801010402, 801010409.

1.3 VPLS for ELAN

Virtual Private LAN Service (VPLS, also known as E-LAN, EP-LAN, EVP-LAN) is a Layer 2 multipoint-to-multipoint Ethernet Bridging service. Endpoints connected to a VPLS see each other as if they were on the same LAN. Each VPLS maintains its own forwarding database so traffic from one VPLS is isolated from others.

There are about 2200 VPLS services in the Indosat network, with 5400 endpoints. These are configured on 7450/7750/7710 nodes, with 65% of them on 7750. Configuring a VPLS requires:

• Choose a globally unique number (service-id) to identify the VPLS: 100 in the example below. Do not re-use this service-id anywhere other than instances of the same VPLS.

• A customer number: 1 here

• SAP access points into the VPLS: port 1/1/2 and 1/1/4 here. The SAP could also be a VLAN, like 1/1/2:100, or a LAG group.

• An SDP, which represents the tunnel to the remote node in one direction. The SDP may use an MPLS RSVP LSP, LDP, or GRE tunnel for transport. VPLS can use spoke-sdp’s or mesh-sdp’s, numbered as <sdp-id>:<service-id>. For example, mesh-sdp 111:100 below. The difference between mesh and spoke SDPs is:

o Mesh SDP – Flooded traffic that is received on the mesh SDP is transmitted to all spoke SDPs and SAPs to which it is connected. Flooded traffic is not transmitted to any other mesh SDPs or back toward the port from which it was received.

o Spoke SDP – Flooded traffic that is received on the spoke SDP is transmitted to all spoke and mesh SDPs as well as SAPs to which it is connected. Flooded traffic is not transmitted back toward the port from which it was received.



• Spanning Tree Protocol (STP) is turned on by default (“no shutdown”), to prevent loops in scenarios where the end-customer may connect Ethernet switches in a loop. If the overhead of STP is not needed, it can be shutdown. In Indosat, 98% of the VPLS instances have STP shutdown, and 2% (109 VPLSs) have stp enabled.

• Split Horizon is an option that can be configured via “split-horizon-group” so that certain access points in the same VPLS cannot see each other. In Indosat, 3% of VPLS services have Split Horizon set under one or more of their spoke-sdp’s or SAPs. See more on split horizon in the ETREE Section 1.4.

• Description and service-name fields are optional, but a good practice to add them. See Section 1.5 about service-name.

• 87% of the VPLSs in Indosat also specify a service-mtu (like MTU 1600 bytes), though often it is better to only configure the MTU on access ports, and then let the VPLS pick it up automatically from there. The example below does not configure any MTU under the VPLS.

Example VPLS for ELAN:

7450 node 1

SAP1/1/2

7750 node 3

SAP1/1/4

Ethernet Ethernet

7750 node 2

VPLS 100

VPLS 100 VPLS 100mesh-sdp333:100

222:100

mesh-sdp111:100

222:100

7450 node 1

SAP1/1/2

7750 node 3

SAP1/1/4

Ethernet Ethernet

7750 node 2

VPLS 100

VPLS 100 VPLS 100mesh-sdp333:100

222:100

mesh-sdp111:100

222:100

Figure 6 – VPLS example

On Node 1: configure service vpls 100 customer 1 create description "VPLS for Jakarta Bank" service-name "vpls-jakarta-bank" stp no shutdown exit sap 1/1/2 create description "GE port at head office" exit mesh-sdp 333:100 create description "Mesh to node 3" exit mesh-sdp 222:100 create description "Mesh to node 2" exit no shutdown exit

On Node 3: configure service vpls 100 customer 1 create description "VPLS for Jakarta Bank" service-name "vpls-jakarta-bank" stp no shutdown exit



sap 1/1/4 create description "FE port at branch office on Main Street" exit mesh-sdp 111:100 create description "Mesh to node 1" exit mesh-sdp 222:100 create description "Mesh to node 2" exit no shutdown exit A VPLS can reside on 3 nodes as in the above example, or just on 1 node, or on many more. In the Indosat network, VPLS 55564 appears on 19 nodes. VPLS 72020202 appears on 10 nodes that are meshed together with a total of 56 mesh-sdp’s.

Same as described in the Epipes with QoS Section 1.2.1, it is possible to add a QoS profile to the SAPs and/or the mesh/spoke-sdp’s under a VPLS, for example to rate-limit the traffic entering the network or prioritize one access port above another via Forwarding Classes. In the Indosat network, 24% of VPLS SAPs have a sap-ingress QoS profile. It is recommended to consider an overall scheme for QoS in the network.

There are many options for configuring a VPLS on ALU routers; see the 7750 SR OS Services Guide for more details.

1.4 VPLS for ETREE

E-Tree is a point-to-multipoint (hub & spoke) service. This is configured on the ALU routers as a VPLS, similar to the ELAN case above, except with settings to direct traffic from “root” to “leaves”. Typically an ETREE has one or more roots and many leaf nodes. The example below shows a video distribution ETREE with two roots supplying the video to many homes. This could be configured with VPLS at all sites, or with Epipe spokes into a central VPLS.

Video server

Video server

VPLS 555 VPLS 555

LeafLeafLeaf

RootRoot

VPLS 555

Video server

Video server

LeafLeafLeaf

RootRoot

VPLS 555

Epipe 50Epipe 40 Epipe 60

spoke-sdp’s

= split horizon on VPLS SAPs,so no leaf-to-leaf communication

= split horizon on VPLS spoke-sdp’s,so no leaf-to-leaf communication

Video server

Video server

VPLS 555 VPLS 555

LeafLeafLeaf

RootRoot

VPLS 555

Video server

Video server

LeafLeafLeaf

RootRoot

VPLS 555

Epipe 50Epipe 40 Epipe 60

spoke-sdp’s

= split horizon on VPLS SAPs,so no leaf-to-leaf communication

= split horizon on VPLS spoke-sdp’s,so no leaf-to-leaf communication

Figure 7 – ETREE examples with VPLS, or VPLS+Epipe spokes



Unlike an ELAN service where all SAPs can reach each other, the above ETREE must be set so the homes cannot communicate with each other. This is achieved by Split Horizon. SAPs or spoke-sdp’s on a VPLS that are in the same split-horizon-group are restricted from seeing each other, though they can communicate with the roots and vice versa. Considering the right side of the diagram above, with Epipe spokes into a central VPLS, below is a sample config showing the split horizon group. On the top right node with VPLS: configure service vpls 555 customer 1 create description "VPLS ETREE for Jakarta Bank" service-name "vpls-jakarta-bank2" split-horizon-group "homes" create exit stp no shutdown exit sap 1/1/2 create description "GE port to video server 1" exit sap 1/1/3 create description "GE port to video server 2" exit spoke-sdp 222:40 split-horizon-group "homes" create description "Spoke to Epipe 40” exit spoke-sdp 333:50 split-horizon-group "homes" create description "Spoke to Epipe 50” exit spoke-sdp 444:60 split-horizon-group "homes" create description "Spoke to Epipe 60” exit no shutdown exit

On the node with Epipe 40: configure service epipe 40 customer 1 create description "Epipe spoke to the video head-end VPLS" sap 10/1/2 create exit spoke-sdp 111:40 create exit no shutdown exit In the above example, split horizon restricts the traffic flow to a hub & spoke topology, but otherwise the MAC learning and bridging behavior is similar to a regular VPLS. In some ETREE applications it is desired to turn off MAC learning altogether, so that every frame that comes from the root is broadcast to all the leaves. This can be achieved by configuring the option: configure service vpls disable-learning There are many ways to configure distribution trees depending on the application. For example, multicast features for a broadcast TV scenario are shown in the diagram below, from the 7750 SR OS Triple Play Guide. Please refer to this guide for more details.



VPLS 5557750

7450

7750

BSA = Broadband Service AggregatorBSR = Broadband Service Router

VPLS 5557750

7450

7750

BSA = Broadband Service AggregatorBSR = Broadband Service Router

Figure 8 – Distributed Multicasting in ALU Triple-Play architecture

In the Indosat network, there are 12 VPLSs that have Epipe spokes into them. All of them have the Epipes on 7705, because 7705 did not support VPLS until release 4.0, so the Epipes were used instead to reach the VPLS on 7750. The option “disable-learning” is not used on any VPLSs in the network. Below is an example of an ETREE in Indosat. The spokes here are all in the same Split Horizon group, so the switches A, B, C, D are unable to reach each other. But if the head-end switch “E” broadcasts an ARP, it learn the destination MAC address, and then unicasts to A, B, C, or D from now on.

BLI-GSB-CN1-SR12

Epipe 500270294

BLI-TBK-EN1-SAR8

SAP

BLI-GSB-CN2-SR12

SAP

Ethernet

Ethernet

mesh-sdp

Epipe 501270294

SAP

EthernetVPLS

504270294

VPLS504270294

Epipe 503270294

Epipe 502270294

spoke-sdp’s

**

**

* = split-horizon-group “en”

A

B

C

D

E

F

BLI-GSB-CN1-SR12

Epipe 500270294

BLI-TBK-EN1-SAR8

SAP

BLI-GSB-CN2-SR12

SAP

Ethernet

Ethernet

mesh-sdp

Epipe 501270294

SAP

EthernetVPLS

504270294

VPLS504270294

Epipe 503270294

Epipe 502270294

spoke-sdp’s

**

**


BLI-GSB-CN1-SR12

Epipe 500270294

BLI-TBK-EN1-SAR8

SAP

BLI-GSB-CN2-SR12

SAP

Ethernet

Ethernet

mesh-sdp

Epipe 501270294

SAP

EthernetVPLS

504270294

VPLS504270294

Epipe 503270294

Epipe 502270294

spoke-sdp’s

**

**


A

B

C

D

E

F

Figure 9 – E-Tree example in the Indosat network



On 7750 BLI-GSB-CN1-SR12: configure service vpls 504270294 customer 65200 create split-horizon-group "en" create exit stp shutdown exit sap 1/1/10:294 create exit mesh-sdp 4734:504270294 create ## mesh from VPLS to VPLS, spokes go to Epipes exit spoke-sdp 4766:500270294 split-horizon-group "en" create exit spoke-sdp 4766:501270294 split-horizon-group "en" create exit mac-move no shutdown exit no shutdown exit On 7750 BLI-GSB-CN2-SR12: configure service vpls 504270294 customer 65200 create split-horizon-group "en" create exit stp shutdown exit sap 4/1/7:294 create exit mesh-sdp 3447:504270294 create exit spoke-sdp 5066:502270294 split-horizon-group "en" create exit spoke-sdp 5066:503270294 split-horizon-group "en" create exit mac-move no shutdown exit no shutdown exit On 7705 BLI-TBK-EN1-SAR8: configure service epipe 500270294 customer 65200 create sap 1/5/3:294 create exit spoke-sdp 5147:500270294 create exit no shutdown exit epipe 501270294 customer 65200 create sap 1/5/4:294 create exit spoke-sdp 5147:501270294 create exit no shutdown exit epipe 502270294 customer 65200 create sap 1/6/3:294 create exit spoke-sdp 5134:502270294 create exit no shutdown exit epipe 503270294 customer 65200 create sap 1/6/4:294 create exit



spoke-sdp 5134:503270294 create exit no shutdown exit

Please see the 7750 SR OS Triple Play Guide and the 7750 SR OS Services Guide for more details.

1.5 Service-name

This section is a best practice for configuring new Epipes & VPLS, copied from the Indosat ALU Network Audit Report.

When configuring new services, it is useful to include a service-name. It is not required to have a service-name, but it is useful for troubleshooting because it appears in the command “show service service-using”, right beside whether the service is up or down. For example:

> show service service-using =============================================================================== Services =============================================================================== ServiceId Type Adm Opr CustomerId Service Name ------------------------------------------------------------------------------- 1302 VPLS Up Up 312 VPRN Bank Syariah Bukopin 1781 VPLS Up Up 166 VPLS-Bank_Permata_ATM_Wireless 1818 VPLS Up Up 465 VPLS_Zurich_Semarang_1M_64176 652554 VPRN Up Down 65554 VPRN-Nokia-3G-Voice 55100333 Epipe Up Up 65003 Sigtran_Jombang1 ===============================================================================

Service-name can also be used during configuration in place of the service-id. Instead of typing “configure service 652554”, one can type “configure service VPRN-Nokia-3G-Voice”. (A service-id number is still required when the service is first configured.) Services can also be viewed this way in SAM if desired.

For the 5% of services that currently have a service-name, many follow a convention of starting with the service type like “VPLS” or “VPRN”, but then after that it is sometimes a dash (-), underscore (_) or space. It is not required that service-names follow a convention, but if desired, here are some guidelines to consider:

• service-name can be up to 64 characters, but only the first 35 characters appear in the “show service service-using” command

• the first character must not be a digit “0” to “9”

• avoid using spaces, because they require the name to be typed with quotes

• if planning to have the name begin with the service type, pick a convention like VPLS-, VPRN-, Epipe-, Apipe-, Cpipe-, IES-

• some networks use all lower-case letters because it’s easier to type, like “vpls-bank-permata”. Others use mixed case because it may look better when displayed in SAM, like “VPLS-Bank_Permata”. Either way is OK, but it is a good idea to pick one or the other.

• service-name should be unique. That is, do not re-use the same service-name for service-id 1302 and 1781. Doing so will not break the service, but it may be confusing on SAM network management.

• service-name is not currently supported on 7705

It is recommended that Indosat pick a convention for adding names for new services in future.



1.6 Scalability

As noted in the Indosat ALU Network Audit report, none of the services are exceeding ALU scalability guidelines. Aside from physical capacity limits like slot space and port count (“6 MDAs per 7705 SAR-8 node”), and hard limits that are enforced by the CLI (“8 ports per LAG group”), many scaling numbers vary depending on the software level, chassis type, IOM type and combination of features. As such, they are not published in a comprehensive list.

A few key scaling limits are listed here for reference, applying to 7705 release 4.0 and 7450/7750/7710 release 8.0.

• 64000 SAPs per 7450/7750/7710 node. Max in Indosat: 1460

• 2048 SAPs per 7705. Max in Indosat: 65

• 512 SDPs per 7705. Max in Indosat: 68

• 2048 spoke-sdp’s per 7705. Max in Indosat: 93

• 48000 VLLs (Epipe/Apipe/Cpipe) per 7750/7450 (7/12 slot). Max in Indosat: 948

• 8000 VPLS per 7750/7450 (7/12 slot). Max in Indosat: 1155 on JKT-KPI-CORE

• 16 VPLS per 7705 SAR-8. Max in Indosat: 0 (VPLS on 7705 introduced in 4.0)

• 16000 LSPs per 7750/7450 (7/12 slot) in LER role. Max in Indosat: 32

• 2048 LSPs per 7705 in LER role. Max in Indosat: 0 (most 7705s using static routes)

For more details please see the ALU manuals:

• 7750 Basic System Config Guide

• 7750 SR OS System Basics Guide

• 7750 SR OS Interfaces Guide

• 7750 SR OS Services Guide

• 7750 SR OS Router Configuration Guide

• 7750 SR OS Routing Protocols Guide

• 7750 SR OS MPLS Guide

• 7750 SR OS QoS Guide

• 7750 SR OS Triple Play Guide

• 7750 SR OS System Management Guide

• and the equivalents on 7705, 7450, 7710

e-line, e-lan, e-tree on alu routers -indosat oct2011

Documents

ethernet port

multipoint lan

ethernet frames

epipe vpls scenarios

metro ethernet services

alu network

epipe spokes

alu ipmpls networkelan