Metro-E Network Topology

12/06/2013
SHARING KNOWLEDGE METRO-E

INDOSAT
Bandung, 11 12 Juni 2013
AGENDA (Day 2)
Topology Metro-E Network Indosat
Services Introduction (VLL,VPLS & VPRN)
Topology Services: GboIP, Sigtran, AoIP, Node-B,

etc
O&M Metro-E include Troubleshooting
Sharing Knowledge Metro-E 2013
1
12/06/2013
1. TOPOLOGY: METRO-E
NETWORK INDOSAT
West Java Region Office (WJRO)
AGENDA
Redundancy Network Metro-E
Redundancy Clocking Synchronization
2
12/06/2013
Legend
Bandung (Area 22)
3
12/06/2013
Sukabumi (Area 24)
Purwakarta (Area 30)
4
12/06/2013
Tasikmalaya (Area 31)
Cirebon (Area 32)
5
12/06/2013
Clocking Synchronization &

Design
7x50 and 7705
PE/CN Routers (7x50)

Clocking Synchronization is needed by TDM or ATM
services use to control the speed with which data is
transmitted on the physical connection. There are some
methods to provide clocking synchronization for 7750:
a. External clocking (PRC/MGW/SDH)
b. Sync-E
c. 1588v2 waiting Indosats approval
d. STM-1 port waiting Indosats approval
It is recommended to apply minimum 2 clock source for
redundancy purpose
6
12/06/2013
External Clocking
Standart
Standard wiring for 7750
Cabling :
Cable E1 (without spliter)
Balun connector installed

to clock souce (PRC/SSU)
show system sync-if-timing

===========================================
Reference Input 2
System Interface Timing Operational Info
Admin Status : down
===========================================
Rx Quality Level : unknown
System Status CPM A : Master Locked
Quality Level Override : none
Reference Input Mode : Non-revertive
Qualified For Use : No
Quality Level Selection : Disabled
Not Qualified Due To : disabled
Reference Selected : BITS A
Selected For Use : No
System Quality Level : prc
Not Selected Due To : disabled
Current Frequency Offset (ppm) : +0
Source Port : None
Reference Order : bits ref1 ref2

Reference BITS A
Input Admin Status : up
Reference Mate CPM
Rx Quality Level : prc
Qualified For Use : Yes
Not Selected Due To : on standby
Selected For Use : Yes
Interface Type : E1
Reference Input 1
Framing : PCM31 CRC
Admin Status : down
Line Coding : HDB3
SSM Bit : 8
==============================================
Source Port : None
7
12/06/2013
EN Router (7705)
Clocking Synchronization is needed by TDM or ATM
services use to control the speed with which data is
transmitted on the physical connection. There are some
methods to provide clocking synchronization for 7705:
a. External clocking (PRC/MGW/SDH)
b. Sync-E
c. 1588v2 waiting Indosats approval
d. E1 port waiting Indosats approval
e. ACR (Adaptive Clock Recovery)
It is recommended to apply minimum 2 clock source for
redundancy purpose.
External Clock
Standart
For Sync-E synchronization,
the MDA type must be
Ethv2 type
For distribution of Sync-E

synchronization, the IOM
type must be IOM-1G and
the MDA type must be
Ethv2 type and Sync-E
command must be enabled
at MDA configuration
8
12/06/2013
show system sync-if-timing

========================================
Reference Input 2
System Interface Timing Operational Info
Admin Status : down
========================================
Configured Quality Level : none
System Status CSM A : Master Locked
Reference Input Mode : Non-revertive
Quality Level Selection : Disabled
Reference Order : ref1 ref2 external
Source Port : None
Reference Input 1
Admin Status : up
External Reference Input
Configured Quality Level : none
Admin Status : down
Configured Quality Level : stu
Selected For Use : Yes
Source Port : 1/1/1
Type : 2048Khz-G703
Impedance : 50-Ohm
External Reference Output

Type : 2048Khz-G703
===============================================
Q &A
9
12/06/2013
2. SERVICES INTRODUCTION
Services Overview
Understanding Services
There are two main types of service on the 7x50/7705 :

Internet connectivity
Represented by the Internet Enhanced Service (IES) is a global service
Its purpose is to provide connectivity to the world as defined in the global routing table
VPN services
VPN services (VPWS,VPLS and VPRN) are restricted to private communication
You define the scope of the VPN; what is allowed into the VPN and how the nodes in the
service connect to each oth
10
12/06/2013
Understanding Services
VPN services can be divided into two subsections:

o Layer 2 VPN (implemented through VPWS and VPLS services)
o Layer 3 VPN (implemented through VPRN service)
Type of VPWS:
Epipe
An Ethernet service between two Ethernet SAPs
Fpipe
A Frame Relay service between two Frame-Relay SAPs
Apipe
An ATM service between two ATM SAPs
Cpipe
A TDM service between two TDM SAPs
Network Component Naming Conventions
PE
P
CE P PE
CE = customer edge
CE
PE = provider edge
P = provider router
11
12/06/2013
7x50 Service Configuration Model

In order to provision a service on a 7x50 SR you must configure a:
Service define the type of service that you want
Service Access Point (SAP) a logical entity that serves as the
customer access to the service.
If you want to provision a VPN service (VPRN,VPLS or ePipe) you also

need a way of telling the router which other routers this VPN will
connect to and how. This requires:
Service Distribution Paths (SDP) An SDP defines which other routers a service is
connected to. They also tell the router what sort of tunnel encapsulation the service
will be using MPLS, LDP, or Generic Router Encapsulation (GRE).
Auto-Bind (VPRN only) - This feature is used with MPLS/LDP tunnels, and effectively
auto-provisions the tunnels.
Logical Service Level

Connectivity
Tunnel supporting Martini- SDP binds multiple services to a
Egress and ingress VC label type service encapsulations. tunnel.
provisioned or dynamically Tunnels are unidirectional,
assigned. Uniquely Identifies but are usually paired to
the service to the tunnels far provide a bi-directional
end. service.
SAP is the
customer point of access
PE-A VC VC PE-B
SDP SDP Label
Label
SAP SAP
VC Label
VC Label Demux Service 1
Service 1
Demux
12
12/06/2013
Service Configuration Model

To provision a service on the SR/ESS/SAR you must configure a:
Customer: A customer ID must be associated with the service.The customer is

chosen by the service operator when the customer account is created. Customer-ID 1
is default.
Service define the type of service required (Epipe, Apipe..)
Service Access Point (SAP) a logical entity that serves as the customer access
to the service.
Service Distribution Paths (SDP) An SDP defines which other router(s) a

service is connected to. They also tell the router what sort of tunnel encapsulation the
service will be using: RSVP-TE, Generic Router Encapsulation (GRE) or LDP
Service Components
Service Service Service Service
Access Distribution Distribution Access
Subscribers Points Path Path Points Subscribers
Service 50 Service 50 Customer

Customer SAP
100 SAP 100
Customer 100
Customer 100
SDP 3 Demux
Demux SDP 5
Customer 200 Customer 200
Customer Customer
SAP SAP 200
200 Service 25 Service 25
Service Tunnels
13
12/06/2013
Service Access Point (SAP)

Customer SAP Service 50
100 1/2/3
dot1q
Customer 100
SDP IP/MPLS Network
Customer 200
SAP
Customer
3/2/9
200
dot1q Service 25
SAP Identifiers:
physical Ethernet port or
POS port and channel
encapsulation type
encapsulation identifier (ID)
Service Distribution Path (SDP)
PE-A SDP
Each SDP represents a method for reaching
a Service Edge Router.
SAP Service 1
C
O Encapsulation methods include GRE & MPLS
R
E SDPs are created and then bound to
services
Many services may be bound to a single SDP
SDP VC labels are created when a service is
SAP Service 1 bound to a SDP that has TLDP enabled on it
PE-B
14
12/06/2013
Comparing Flooded Traffic with Spoke-

SDPs, Mesh-SDPs and SAPs
Spoke-SDP
Flooded traffic received on the spoke-SDP is replicated on all
other spoke-SDPs and mesh-SDPs and SAPs within the same
service.
Split horizon assumed.
Mesh-SDP
Flooded traffic received on any mesh-SDP is replicated to
other spoke-SDPs and SAPs but not transmitted on any other
mesh-SDP within the same service.
SAP
Flooded traffic received from a SAP is replicated to other SAPs
and spoke-SDPs and mesh-SDPs within the same service.
SAP Originated Flooded Traffic

The following occurs when flooded traffic is received on a
SAP:
the flooded traffic is replicated on all SAPs and network ports,
including other spoke-SDPs and mesh-SDPs;
the flooded traffic is not replicated on the port it was received
from.
Mesh
SDP
SR-A
SDP
Service G
SDP
Spoke
SAP
SAP
15
12/06/2013
Spoke versus Mesh SDPs

When an SDP is bound to a service, it is bound as either a spoke SDP or a mesh SDP.
The type of SDP governs how flooded traffic is transmitted.
A spoke SDP is treated like the equivalent of a traditional bridge port where flooded
traffic received on the spoke SDP is replicated on all other ports (other spoke and
mesh SDPs or SAPs) and not transmitted on the port it was received.
All mesh SDPs bound to a service are logically treated like a single bridge port for
flooded traffic where flooded traffic received on any mesh SDP on the service is
replicated to other ports (spoke SDPs and SAPs) and not transmitted on any mesh
SDPs.
Mesh Mesh
SDP SDP
SR-A SR-A
SDP SDP
Service G Service G
SDP SDP
SAP SAP
SDP SDP
Spoke Spoke
Services
ePipe Service
16
12/06/2013
ePipe Service
A ePipe service provides a point to point connection between two nodes.

Also referred to as a Virtual Leased Line (VLL) service
From the customers perspective it looks as if a virtual leased
link exists between the two locations.
PE B
The Service provider can apply billing,
ingress/egress shaping and policing ePipe Service
No MAC learning required

PE A PE C
IP / MPLS
Network
PE D
Creating an ePipe Service

Customer Customer
access access
ports SDP PE-B ports
SAP D
Service-id D Service-id
SAP
SDP
PE-A
CORE
Service-id: ePipe
Customer (subscriber) Association
Service Access Point Select node and port
Select Accounting Policy (optional)
Select Ingress/Egress QOS Policies (optional)
Select scheduler policy (optional)
Select Filter policies (optional)
Service Distribution Point Binds an SDP to a service
17
12/06/2013
Configuring Customer and SDP

SR>config>service# customer 5 create
SR>config>service>cust$ contact
description
phone
multi-service
Every service must be associated with a customer
SR>config>service# sdp 2 mpls create
SR>config>service>cust$ description
far-end < <ip-system-target> >
ldp
ePipe Configuration
Creating an ePipe Service:
SR# config>service# epipe 5500 customer 5 create

SR>config>service>epipe$ description epipe service
SR>config>service>epipe$ no shutdown
Applying Ingress and Egress SAP Parameters:
SR>config>service# epipe 5500

SR>config>service>epipe# sap 2/1/3 create
SR>config>service>epipe>sap#exit
18
12/06/2013
ePipe SDP Bindings
Service ID
After you have created an SDP
SR>config>service# epipe 5500

config>service>epipe# spoke-sdp 2:5500 create
config>service>epipe>spoke-sdp$ no shutdown
config>service>epipe>spoke-sdp$ back
config>service>epipe# no shutdown
config>service>epipe# exit all User-assigned
SDP Number
Epipe Show commands

show service sdp
show service sap-using
show service service-using
show service id 500 [ base | all ]
show router mpls interface label-map
show router mpls status
show service id 500 labels
show router ldp bindings
19
12/06/2013
OAM Tools SDP Ping
Verify connectivity to local service SAP

Oam sdp-ping 5
Perform a round-trip SDP ping test
Oam sdp-ping 5 resp-sdp 5
OAM Tools SDP MTU

Oam sdp-mtu 5 size-inc 1510 1520 step 1
20
12/06/2013
OAM Tools Service Ping

Verify the operation of the service
Oam svc-ping 172.0.0.213 service 500
Oam svc-ping 172.0.0.213 service 500 local-sdp remote-sdp
Services
aPipe Service
21
12/06/2013
A-PIPE Overview
A-pipe service provides a bi-directional layer 2 connection of ATM service between
two users/sites through an IP/MPLS network.
A-pipe is supported on any T1/E1 port on 16 p ASAP card when the port is configured
for ATM or IMA
ATM cells received on the ATM SAP are encapsulated into PW packets to be
transported over IP/MPLS outer tunnels.
Targeted LDP signaling is commonly used to setup the PW.
ATM Encapsulation over PSN

PSN Transport Header
Pseudo Wire Header
ATM Service Payload
General format for ATM encapsulation over PSN (RFC 4717)
PSN transport could be GRE or MPLS.

The PSN transport header will include the MPLS Tunnel outer label. In addition to the
transport specific information (Ethernet, ML-PPP)
The PW header identifies a particular ATM service on a tunnel
22
12/06/2013
ATM Encapsulation over PSN

VCC Apipe configured on an E1 ATM port: VCC Apipe configured on an IMA bundle:
configure configure
service apipe 6 customer 1 vc-type atm-vcc
create service apipe 7 customer 1 vc-type atm-vcc create
description Rdmd-3G-6" description "Stl-3G-7"
spoke-sdp 50:6 create spoke-sdp 50:7 create
sap 1/1/3.1:0/32 sap bundle-ima-1/6.1:1/52 exit
exit
no shutdown
no shutdown
Other parameters can also be configured, e.g.

QOS, Accounting policies
A-PIPE Configuration (atm-vpc)

Configure
apipe 702 customer 105 vc-type atm-vpc create
description VPC-Apipe-E1-ATM
sap 1/2/9.1:51 create
exit
spoke-sdp 808:702 create
Slot/MDA/Port.ChGroup:VPI
exit
no shutdown
This Type also can be configured on an IMA bundle.
23
12/06/2013
Apipe Statistics
Statistics can be viewed on:
The port:
show port 1/2/2.1
clear port 1/2/2.1 statistics (to clear port stats)
Or on the service SAP:

show service id 100 sap sap-stats 1/2/1.1
clear service id 100 (to clear the service stats)
47 | 7705 SAR R1.0 System

Hardware | DRAFT V1.0
Services
VPLS Service
24
12/06/2013
Virtual Private LAN Service (VPLS)

VPLS is a class of VPN that allows the connection of
multiple sites in a single bridged domain over a provider
managed IP/MPLS network
PE B
From the customers
perspective it looks as if IP/LSP Full-
VPLS Service
all sites are connected to Mesh
a single switched VLAN

PE A PE C
Service provider
can reuse the
IP/MPLS infrastructure IP / MPLS
to offer multiple services Network
The Service provider can apply billing,

ingress/egress shaping and policing
PE D
Virtual Private LAN Service (VPLS)
PE-A
Service 1
CE
SAP Customer A
PE-B PE-C
CE
Service 1 Service 1
Customer A SAP SAP Customer A
CE
Full Mesh
of IP / MPLS PE-D
Tunnels
Service 1
Customer A SAP
CE
25
12/06/2013
Creating a Customer CLI Example
SR_1>config>service# customer 1000 create
SR_1>config>service>cust$ contact
description
phone
multi-service
Every service must be associated with a customer
Creating a VPLS Service CLI Examples

Creating a Service
SR1>config>service# vpls 500 customer 1000 create
SR1>config>service>vpls$ description New VPLS Service
SR1>config>service>vpls$ no shutdown
Configuring a SAP
SR1>config>service# vpls 500 customer 1000 create
SR1>config>service>vpls# sap 2/1/5:0 create
SR1>config>service>vpls>sap$ no shutdown
Binding a Service to an SDP

SR1>config>service# vpls 500
SR1>config>service>vpls# mesh-sdp 3:500 create
SR1>config>service>vpls> mesh-sdp# no shutdown
26
12/06/2013
Example: Service Show commands

Show service id 500 [all | base] Service, SAP and SDP
= Up
Show service fdb-mac
Services
VPRN Service
27
12/06/2013
Virtual Private Routed Network

MP-IBGP CE B
Route RI-1
Exchange
VPRN is a class of VPN that allows the For all Services RI-2 PE B
connection of multiple sites in a routed
domain over a provider managed IP/MPLS network
RI-1 PE A PE C CE C
From the customers RI-2
perspective it looks as if
all sites are connected to
a routed domain where the CE A IP / MPLS RI-1
provider PEs behave similarly Network RI-2 VPRN Service
Red
to his own routers
Service provider
can reuse the PE D VPRN Service
Green
IP/MPLS infrastructure RI-1
to offer multiple services. RI-2
CE D
Each VPRN appears like an additional
routing instance, routes for a service
between the various PEs are exchanged
using MP-BGP
Customer data is encapsulated using
MPLS or GRE encapsulation
Example: VPRN configuration

Configure global AS number on each router
Configure router autonomous-system 65000
Configure global BGP
Configure router bgp family vpn-ipv4
Configure router bgp local-as 65000
Configure router bgp group Internal
Configure router bgp group Internal peer-as 65000
Configure router bgp group Internal neighbor <neighbor-system-IP>
Configure router bgp group Internal neighbor local-address <local-system-IP>
Configure router bgp no shutdown
Verify the configuration
Show router bgp summary
Show router bgp neighbor
28
12/06/2013
Example: VPRN Configuration

Enable MPLS and LDP on each PE
Configure router mpls no shutdown
Configure router ldp interface-parameters interface toPEXX
Configure router ldp no shutdown
Verify the configuration
Show router ldp interface
Show router ldp bindings
Show router ldp session
Q &A
29
12/06/2013
3. TOPOLOGY: GBoIP, SIGTRAN,

AoIP, & NODE-B
Best Practice
Best Practice
2G NSN
30
12/06/2013
Best Practice Gb Topology
Example Gb Configuration
configure service vpls 500130084 customer 65200 create
description "P2P_GboIP_ext1_H_KEDIRI_01"
split-horizon-group "downstream" create
exit
stp
shutdown
exit
mac-protect
mac 00:00:5e:00:01:0a
exit
service-name "P2P_GboIP_ext1_H_KEDIRI_01"
sap 1/2/6:84 split-horizon-group "downstream" create
restrict-protected-src
exit
mesh-sdp 5019:500130084 create
exit
no shutdown
configure service epipe 500080093 customer 65200 create

description "P2P_GboIP_H_BOJONEGORO_01"
sap 1/6/1:93 create
exit
exit
no shutdown
31
12/06/2013
Example VPRN configuration for Gb Traffic

BSC
configure service vprn 652200 customer 65200 create
description "VPRN ericsson-iups"
snmp-community "community" hash2 version v2c
vrf-import "import-map:652200"
vrf-export "export-map:652200"
autonomous-system 4761
route-distinguisher 124.195.96.252:200
auto-bind ldp
interface "P2P_GboIP_H_BOJONEGORO_01" create
description "P2P_GboIP_H_BOJONEGORO_01"
address 10.243.179.214/30
ip-mtu 1500
sap 2/2/18:94 create
exit
Best Practice Sigtran Topology
32
12/06/2013
Example Sigtran Configuration

description "P2P_CP_ext1_H_KEDIRI_01"
exit
stp
shutdown
exit
mac-protect
mac 00:00:5e:00:01:0a
exit
service-name "P2P_CP_ext1_H_KEDIRI_01"
exit
exit
no shutdown

description "P2P_CP_H_BOJONEGORO_01"
sap 1/5/1:91 create
exit
exit
no shutdown
Example VPRN configuration for Sigtran

Traffic BSC
description "sigtran:ITP"
ecmp 4
auto-bind ldp
interface "P2P_CP_H_BOJONEGORO_01" create
description "P2P_CP_H_BOJONEGORO_01"
address 10.243.179.202/30
ip-mtu 1500
sap 3/2/6:91 create
exit
33
12/06/2013
Best Practice OAM Topology
Example OAM Configuration

description "P2P_OAM_ext1_H_KEDIRI_01"
exit
stp
shutdown
exit
mac-protect
mac 00:00:5e:00:01:0a
exit
service-name "P2P_OAM_ext1_H_KEDIRI_01"
exit
exit
no shutdown
description "P2P_OAM_H_BOJONEGORO_01"
sap 1/5/1:89 create
exit
exit
no shutdown
34
12/06/2013
Example VPRN configuration for OAM

Traffic BSC
description "VPRN alcatel-oss"
auto-bind ldp
interface "P2P_OAM_H_BOJONEGORO_01" create
description "P2P_OAM_H_BOJONEGORO_01"
address 10.243.179.194/30
ip-mtu 1500
sap 3/2/6:89 create
exit
Best Practice AoIP Topology
35
12/06/2013
Example VPLS configuration for AoIP

Configure service vpls 541130000 customer 65003 Configure service epipe 506080089 customer 65554
create create
description "AoIP_H_KEDIRI_01" description "P2P_OAM_H_BOJONEGORO_01"
split-horizon-group "downstream" create sap 1/5/1 create
exit exit
stp spoke-sdp 5250:506080089 create
shutdown exit
exit no shutdown
mac-protect
mac 00:00:5e:00:01:0a
exit
service-name "AoIP_H_KEDIRI_01"
sap 2/1/20 split-horizon-group "downstream"
create
exit
exit
exit
no shutdown
Example VPRN configuration for AoIP BSC

description "VPRN Nokia_3G_Voice"
ecmp 4
auto-bind ldp
interface "loop:1001:ETPA_AoIP_H_BOJONEGORO" create
description "ETPA_AoIP_H_BOJONEGORO"
address 10.243.181.44/28
ip-mtu 1500
vrrp 93
backup 10.243.181.46
priority 110
ping-reply
telnet-reply
ssh-reply
traceroute-reply
exit
sap 3/2/6:1001 create Sharing Knowledge Metro-E 2013
exit
36
12/06/2013
Best Practice
3G Native IP
Best Practice IuB & OAM Topology (NSN)
7750 CN1
IuB VRF 6528888
MDS
SAP with split horizon SAP SAP
VPLS SAP (Main Distribution
Mac-protect enabled SAP
SDP Switch)
Node B
Active
dotiq mesh VPRN
SAP SDP
dotiq
SAP SDP IP/MPLS VRRP VRRP
mesh IuB&OAM Standby
IuB&OAM RNC
NodeB mesh
mesh
TN MDS
7450 at Hub SAP SAP (Main Distribution
SAP SAP
SDP
Switch)
Node B RNC NSN
VPLS VPRN
IuB VRF 6528888

7750 CN2
Note :
7705 can also be used to functioned as 7450 as pictured above.
Assuming 7705 is equipped with TiMOS 4.
Indosat Maintenance Training/2012 Sharing Knowledge Metro-E 2013
37
12/06/2013
Best Practice IuB & OAM Topology (EID)
Indosat Maintenance Training/2012 Sharing Knowledge Metro-E 2013
Example VPLS configuration for IuB

Interface (at Hub Site)
Configure service vpls 72020203 customer 658888 create
description "RNC-02 cluster 03"
sap 2/1/8:203 split-horizon-group "Downstream" create
stp
description "To NodeB 3G_Auri_Cisalak"
shutdown
exit
ingress
mac-protect
scheduler-policy "BW20M"
mac 00:00:5e:00:01:0a
qos 12001
exit
exit
service-name "Iub_RJK02_cluster03_Vlan203"
egress
split-horizon-group "Downstream" create
exit
qos 12001
exit
description "To NodeB 3G_Gandaria, 3G_Auri_cisalak"
exit
ingress
exit
qos 14002
exit
exit
no shutdown
egress
qos 14002
exit
exit
38
12/06/2013
Example VPLS configuration for OAM (at

Hub Site)
description "OAM for RJK02 Cluster 03"
stp
shutdown
exit
mac-protect
mac 00:00:5e:00:01:0a
exit
service-name "OAM_RJK02_Cluster03_Vlan218"
exit
exit
exit
exit
no shutdown
Example VPLS configuration for IuB

Interface (at RNC Site)
description "VPLS NodeB IP RJK 12 Cluster-01"
stp
shutdown
exit
service-name "VPLS NodeB IP RJK 12 Cluster-01"
exit
exit
exit
exit
no shutdown
exit
39
12/06/2013
Example VPLS configuration for OAM (at

RNC Site)
description "OAM_RJK02_Cluster03_VLAN0218"
stp
shutdown
service-name "OAM_RJK02_Cluster03_VLAN0218"
exit
exit
exit
exit
exit
no shutdown
exit
Example VPRN configuration for IuB and

OAM traffic
configure service vprn 6528888 customer 65888 create interface "to_NodeB_Iub_Cluster2" create
description "VPRN IuB (RNC-NodeB)" address 10.253.87.60/26
snmp-community community" hash2 version v2c vrrp 10
vrf-import "import-map:6528888" backup 10.253.87.62
vrf-export "export-map:6528888" priority 110
route-distinguisher 124.195.92.27:8888 ping-reply
auto-bind ldp telnet-reply
interface "to_RNCSMG1_Iub" create ssh-reply
address 10.253.64.101/29 exit
vrrp 10 vpls "VPLS-NodeB_Iub_Cluster2"
backup 10.253.64.102 exit
priority 110 exit
ping-reply static-route 10.253.74.88/29 next-hop
telnet-reply 10.253.69.177
ssh-reply static-route 10.253.77.184/29 next-hop
traceroute-reply 10.253.69.129
exit static-route 10.253.77.192/29 next-hop
vpls "VPLS-RNC_Iub" 10.253.69.130
exit static-route 10.253.77.200/29 next-hop
exit 10.253.69.131
40
12/06/2013
Best Practice IuCS_CP & IuPS_CP & IuR_CP

Topology
Example VPRN configuration for IuCS_CP &

IuPS_CP & IuR_CP Traffic
configure service vprn 6528888 customer 65888 interface "MDS:3/1/2:731_RNCLBG1_IuPS_CP" interface "MDS:3/1/2:735_RNCLBG1_IuR_CP"
create create create
description "sigtran:ITP" description "to-tlan1-2_gi1/5" address 10.253.53.132/29
snmp-community "community" hash2 address 10.253.53.68/29 vrrp 35
version v2c vrrp 31 backup 10.253.53.134
vrf-import "import-map:652003" backup 10.253.53.70 priority 110
vrf-export "export-map:652003" priority 110 policy 3
ecmp 4 policy 3 ping-reply
autonomous-system 4761 ping-reply telnet-reply
route-distinguisher 124.195.96.253:3 telnet-reply ssh-reply
auto-bind ldp ssh-reply traceroute-reply
interface traceroute-reply message-interval milliseconds 300
"MDS:3/1/2:733_RNCLBG1_IuCS_CP" create message-interval milliseconds 300 exit
address 10.253.53.100/29 exit sap 3/1/2:735 create
vrrp 33 sap 3/1/2:731 create ingress
backup 10.253.53.102 ingress qos 100
priority 110 qos 100 exit
policy 3 exit egress
ping-reply egress qos 100
telnet-reply qos 100 exit
ssh-reply exit exit
traceroute-reply exit
message-interval milliseconds 300
exit
ingress
qos 100
exit
egress
qos 100
exit
exit Sharing Knowledge Metro-E 2013
41
12/06/2013
Best Practice IuR_UP & IuCS_UP Topology
Example VPRN configuration for IuR_UP &

IuCS_UP Traffic
configure service vprn 652554 customer 65554 create sap 3/1/2:734 create
description "VPRN Nokia_3G_Voice" ingress
snmp-community "community" hash2 version qos 100
v2c exit
vrf-import "import-map:652554" egress
vrf-export "export-map:652554" qos 100
ecmp 4 exit
autonomous-system 4761 exit
route-distinguisher 124.195.96.253:554 interface "MDS:3/1/2:736_RNCLBG1_IuR_UP" create
auto-bind ldp address 10.253.53.140/29
interface "MDS:3/1/2:734_RNCLBG1_IuCS_UP" vrrp 36
create backup 10.253.53.142
address 10.253.53.108/29 policy 554
vrrp 34 ping-reply
backup 10.253.53.110 telnet-reply
policy 554 ssh-reply
ping-reply traceroute-reply
telnet-reply message-interval milliseconds 300
ssh-reply exit
traceroute-reply sap 3/1/2:736 create
message-interval milliseconds 300 ingress
exit qos 100
exit
egress
qos 100
exit
exit
42
12/06/2013
Best Practice IuPS_UP Topology
Example VPRN configuration for IuPS_UP

Traffic
configure service vprn 652110 customer 65110 sap 3/1/2:732 create
create ingress
qos 100
description "Ericsson-GN" exit
snmp-community "community" hash2 egress
version v2c qos 100
vrf-import "import-map:652110" exit
vrf-export "export-map:652110" exit
ecmp 4
auto-bind ldp
interface
"MDS:3/1/2:732_RNCLBG1_IuPS_UP" create
address 10.253.53.76/29
vrrp 32
backup 10.253.53.78
priority 110
ping-reply
telnet-reply
traceroute-reply
exit
43
12/06/2013
Example configuration for IuB Interface

description "RNC-02 cluster 03"
stp
description "To NodeB 3G_Auri_Cisalak"
shutdown
exit
ingress
mac-protect
mac 00:00:5e:00:01:0a
qos 12001
exit
exit
service-name "Iub_RJK02_cluster03_Vlan203"
egress
split-horizon-group "Downstream" create
exit
qos 12001
exit
description "To NodeB 3G_Gandaria, 3G_Auri_cisalak"
exit
ingress
exit
qos 14002
exit
exit
no shutdown
egress
qos 14002
exit
exit
Best Practice and Topology
3G ATM
44
12/06/2013
Topology NodeB ATM
Ap
ip
e
Topology NodeB ATM
45
12/06/2013
Example Configuration
A:SKA-BHS-EN1-SAR8# configure port bundle-ima- A:SKA-BHS-EN1-SAR8# configure service apipe
1/2.24 313210241
A:SKA-BHS-EN1-SAR8>config>port# info A:SKA-BHS-EN1-SAR8>config>service>apipe# info
---------------------------------------------- ----------------------------------------------
description "NodeB TDM 3G_JAYENGAN" description "Apipe for IuB NodeB ATM
3G_JAYENGAN"
multilink-bundle
sap bundle-ima-1/2.24:1 create
ima
atm
atm
ingress
exit
traffic-desc 904
test-pattern-procedure
exit
exit
exit
exit
ingress
member 1/2/2.2.7.2.1
qos 904
member 1/2/2.2.7.3.1
exit
member 1/2/2.3.1.1.1
exit
member 1/2/2.3.1.2.1
exit
exit
no shutdown
no shutdown
----------------------------------------------
----------------------------------------------
e1 to KLM port
46
12/06/2013
Example Configuration
A:SOL-BHS-PE1-SR7# configure port 4/1/2 A:SOL-BHS-PE1-SR7# configure service apipe 313210241
A:SOL-BHS-PE1-SR7>config>port# info A:SOL-BHS-PE1-SR7>config>service>apipe# info
---------------------------------------------- ----------------------------------------------
description "to RNC solo 1 NP8s1 port 1" description "Apipe for IuB NodeB ATM
3G_JAYENGAN"
sonet-sdh
service-name "JAYENGAN VP-Traffic"
framing sdh
sap 4/1/2:5 create
path
atm
atm
ingress
exit
traffic-desc 904
no shutdown
exit
exit
exit
exit
ingress
no shutdown
qos 904
----------------------------------------------
exit
exit
exit
no shutdown
----------------------------------------------
Q &A
47
12/06/2013
4. OPERATION & MAINTENANCE

METRO-E
Troubleshooting
How to show Layer 1 & Layer 2 alarms

Show log log-id 99 -> all major and minor alarm
Show log log-id 100 -> all major alarm
Example untuk alarm spesific :
What To Check CLI Command

Show alarms of a particular port (ex. port 1/1/1) show log log-id 99 subject 1/1/1
Show alarms related to the chassis show log log-id 99 application chassis
Show alarms of a particular IOM (ex. IOM Slot #1) show log log-id 99 subject Card 1
Show alarms of a SF/CPM (ex. SF/CPM Slot #A) show log log-id 99 subject Card A
Show alarms of a particular MDA (ex. MDA 1/1) show log log-id 99 subject Mda 1/1
48
12/06/2013
Verify cards, MDAs and ports configuration

Chassis configuration & status show chassis
show chassis environment
show chassis power-supply
IOM or SF/CPM configuration & status show card show card <A/B> detail
show card <slot-number> detail
MDA configuration & status show mda show mda detail

port configuration & status show port show port <slot/mda/port>
show port <slot/mda/port[.sonet-sdh-
index]>
show port <port-id> detail
show port <port-id> ppp [detail]
Link Aggregation Group (LAG) show lag <lag-id>
show lag <lag-id> detail
Display logical interfaces associate show port <slot/mda/port> associations
with a port
How to show or clear statistics on a port or

a LAG or a SAP

show statistics of a port show port <slot/mda/port> count
show statistics of a LAG show lag <lag-id> detail statistics
show counters of a SAP show service id <service-id> sap <port-id[:encap-
val]> detail
clear counters of a port clear port < slot/mda/port > statistics
clear counters of a LAG clear lag <lag-id> statistics
clear counters of a SAP clear service statistics sap <port-id[:encap-val]>
counters
49
12/06/2013
How to show or modify the operational

status of a port

To display the administrative status of a port show port <slot/mda/port>
To modify the administrative status of a port config port <slot/mda/port>
[no] shutdown
How to show port status

A:ALA-A# show port 1/6/7
===============================================================================
Ethernet Interface
===============================================================================
Description : to_ALA-A
Interface : 1/6/7 Oper Speed : 1 Gbps
Link-level : Ethernet Config Speed : 1 Gbps
Admin State : up Oper Duplex : full
Oper State : up Config Duplex : full
Physical Link : Yes MTU : 2102
Single Fiber Mode : No
IfIndex : 46366720 Hold time up : 0 seconds
Last State Change : 09/22/2012 22:25:07 Hold time down : 0 seconds
Last Cleared Time : N/A DDM Events : Enabled
Configured Mode : network Encap Type : null

Dot1Q Ethertype : 0x8100
Ing. Pool % Rate : 100 Egr. Pool % Rate : 100
Net. Egr. Queue Pol: default
Net. Scheduler Mode: profile
Auto-negotiate : true MDI/MDX : MDX
Egress Rate : Default Ingress Rate : n/a
50
12/06/2013
How to check port utilization

A:ALA-A# monitor port
- port <port-id> [<port-id>...(up to 5 total)] [interval <seconds>] [repeat
<repeat>] [absolute|rate] [multiclass]
- port <port-id> [<port-id>...(up to 5 total)] atm ...
<port-id> : slot/mda/port[.channel]
bundle-id - bundle-<type>-slot/mda.<bundle-num>
bundle - keyword
type - ima|ppp
bundle-num - [1..32]
aps-id - aps-<group-id>[.channel]
aps - keyword
group-id - [1..8]
<seconds> : [3..60] - default 10
<repeat> : [1..999] - default 10
<absolute|rate> : keywords - default mode delta
<multiclass> : keyword
atm + Monitor ATM statistics

How to check port utilization (contd)

A:ALA-A# monitor port 1/6/7 interval 3 rate
===============================================================================
Monitor statistics for Port 1/6/7
===============================================================================
Input Output
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
At time t = 0 sec (Base Statistics)
-------------------------------------------------------------------------------
Octets 30094116498136 30103155019128
Packets 124993840413 125030716785
Errors 0 0
-------------------------------------------------------------------------------
At time t = 3 sec (Mode: Rate)
-------------------------------------------------------------------------------
Octets 1471488 1471600
Packets 5917 5920
Errors 0 0
Utilization (% of port capacity) 1.27 1.27
-------- output omitted ----------

51
12/06/2013
How to check port utilization (contd)

-------- output omitted ----------
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
Octets 1466070 1465940
Packets 5894 5891
Errors 0 0
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
Octets 1511854 1513339
Packets 6082 6086
Errors 0 0
===============================================================================
How to check multilink-bundle

A:ALA-A# show multilink-bundle
===============================================================================
Bundle Summary
===============================================================================
Bundle Type Admin Oper Port Min Total/
Id State State State Links Active Links
-------------------------------------------------------------------------------
bundle-ima-1/1.2 ima-grp Up Down Down 1 4/0
bundle-ppp-1/2.1 mlppp Up Up Up 1 10/10
bundle-ppp-1/3.2 mlppp Up Up Up 1 6/5
bundle-ima-1/5.1 ima-grp Up Up Up 1 4/4
bundle-ima-1/5.2 ima-grp Up Up Up 1 4/4
-------------------------------------------------------------------------------
Bundles : 5
===============================================================================
52
12/06/2013
How to check multilink-bundle port

utilization
A:ALA-A# monitor port bundle-ima-1/5.1 interval 3 rate
===============================================================================
Monitor statistics for Port bundle-ima-1/5.1
===============================================================================
Input Output
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
At time t = 0 sec (Base Statistics)
-------------------------------------------------------------------------------
Octets 24457908993 77527124714
Packets 461469240 1462775822
Errors 0 0
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
Octets 39962 140644
Packets 754 2650
Errors 0 0
-------- output omitted ----------

How to check multilink-bundle port

utilization
-------- output omitted ----------

-------------------------------------------------------------------------------
Octets 31782 45297
Packets 597 849
Errors 0 0
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
Octets 20741 38125
Packets 395 724
Errors 0 0
===============================================================================
53
12/06/2013
Commands common to any OSPF

troubleshooting
show commands used to check OSPF related configuration
show router ospf area

show router ospf interface
show router ospf neighbor
show router ospf status
show router ospf database
View the OSPF related alarms/logs
show log log-id 99 application ospf
Commands common to any LDP

troubleshooting
show commands used to check LDP related configuration
show log log-id 99 subject LDP
Using Debug to troubleshoot a LDP related problem
SR12# debug router ldp

- Ldp
- no ldp
- [no] interface
+ Enable/disable and configure debugging for an LDP interface
-[no] peer
+ Enable/disable and configure debugging for an LDP peer
54
12/06/2013
Commands common to any LDP

troubleshooting
Using show commands to check LDP information
Command Explanation
show router ldp bindings To display LDP bindings information
show router ldp bindings active To display LDP active bindings.An active binding
must exist for a prefix in order for an LSP to be
active
show router ldp discovery To display LDP discovery information
show router ldp interface To display LDP interface information
show router ldp parameters To display LDP configured and operation
parameters
show router ldp peer To display LDP targeted peer information
show router ldp session To display LDP session information
show router ldp status To display LDP operational information
Commands common to any SDP

troubleshooting
show commands used to check SDP related configuration
show service sdp <sdp-id>
View the SDP related alarms/logs
show log log-id 99 application svcmgr
55
12/06/2013
Commands common to any SDP

troubleshooting
Using Debug to troubleshoot an SDP related problem
SR12# debug service sdp

- no sdp <sdp-id>
- sdp <sdp-id> <sdp-id> : [1..17407]
[no] event-type - Enable/disable a particular debugging event type
Commands common to Layer 2 Service

troubleshooting
show commands used to check Service related configuration
show service id <id> base

show service id <id> sdp <sdp-id>
show service id <id> sap <sap-id>
show service id <id> fdb (VPLS only)
show service id <id> stp (VPLS only)
show service id <id> all
View the Service related alarms/logs
56
12/06/2013
Layer 2 Service Troubleshooting Steps

1. show service id <id> base
2. a. show service id <id> sdp <sdp-id>

b. show service id <id> sap <sap-id>
3. Pay attention flag codes in the outputs of the

commands used in step 2.
Commands common to VPRN Service

troubleshooting
show commands used to check VPRN related configuration
show service id <id> base

show service id <id> sdp <sdp-id>
show service id <id> sap <sap-id>
show service id <id> interface
show service id <id> arp
Show router <service-id> route-table
show router <service-id> interface
show router <service-id> arp
show router <service-id> vrrp instance
Note: All router commands can be used to view the routing information specific to the VPRN.
Use show router <service-id> ? for full a list of available commands.
View the Service related alarms/logs
57
12/06/2013
Q &A
58

Metro-E Network Topology

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Metro-E Network Topology

Uploaded by

Copyright:

Available Formats

12/06/2013

SHARING KNOWLEDGE METRO-E

Topology Metro-E Network Indosat

Services Introduction (VLL,VPLS & VPRN)

Topology Services: GboIP, Sigtran, AoIP, Node-B,

O&M Metro-E include Troubleshooting

Sharing Knowledge Metro-E 2013

Sharing Knowledge Metro-E 2013

Sharing Knowledge Metro-E 2013

Sharing Knowledge Metro-E 2013

Bandung (Area 22)

Sharing Knowledge Metro-E 2013

Sukabumi (Area 24)

Sharing Knowledge Metro-E 2013

Purwakarta (Area 30)

Sharing Knowledge Metro-E 2013

Tasikmalaya (Area 31)

Sharing Knowledge Metro-E 2013

Cirebon (Area 32)

Sharing Knowledge Metro-E 2013

Clocking Synchronization &

Sharing Knowledge Metro-E 2013

PE/CN Routers (7x50)

Sharing Knowledge Metro-E 2013

Cable E1 (without spliter)

Balun connector installed

Sharing Knowledge Metro-E 2013

show system sync-if-timing

Reference Order : bits ref1 ref2

Sharing Knowledge Metro-E 2013

For distribution of Sync-E

Sharing Knowledge Metro-E 2013

show system sync-if-timing

External Reference Output

Sharing Knowledge Metro-E 2013

Sharing Knowledge Metro-E 2013

Sharing Knowledge Metro-E 2013

There are two main types of service on the 7x50/7705 :

Sharing Knowledge Metro-E 2013

VPN services can be divided into two subsections:

Network Component Naming Conventions

Sharing Knowledge Metro-E 2013

7x50 Service Configuration Model

If you want to provision a VPN service (VPRN,VPLS or ePipe) you also

Sharing Knowledge Metro-E 2013

Logical Service Level

Sharing Knowledge Metro-E 2013

Service Configuration Model

Customer: A customer ID must be associated with the service.The customer is

Service define the type of service required (Epipe, Apipe..)

Service Distribution Paths (SDP) An SDP defines which other router(s) a

Sharing Knowledge Metro-E 2013

Service 50 Service 50 Customer

Sharing Knowledge Metro-E 2013

Service Access Point (SAP)

SDP IP/MPLS Network

Sharing Knowledge Metro-E 2013

Service Distribution Path (SDP)

Sharing Knowledge Metro-E 2013

Comparing Flooded Traffic with Spoke-

Sharing Knowledge Metro-E 2013

SAP Originated Flooded Traffic