XL Axiata

Method of Procedure (MOP)

MOP – Integration New Link C-SBRKO-01 <> C-BJAHY-01

Device : Juniper MX960, M320

Location : C-SBRKO-01, C-BJAHY-01

PT. Lintas Teknologi Indonesia

th
Menara MTH 16 Floor
Jl. MT Haryono Kav. 23
Jakarta 12820 - Indonesia
Telp. +62 21 8378 0000
Fax. +62 21 8378 0001
http://www.lt-indonesia.com
2014
Deployment Plan

Table of Content

1. INTRODUCTION ....................................................................................................... 3
2. PERSON IN CONTACTS (PIC) ...................................................................................... 3
3. SCHEDULE ................................................................................................................ 3
4. IP AND PORT ALLOCATION ....................................................................................... 3
5. IMPLEMENTATION PROCEDURE ............................................................................... 4
6. FALLBACK PLAN ..................................................................................................... 10
MOP CONDITION ........................................................................................................... 12
SIGN-OFF FOR APPROVAL............................................................................................... 12

Appendix 1 Expected Results and Test Case .............................................................. 13

Method of Procedure (MOP)
Deployment Plan

Version History:

Version Author Date Reason for Change

Number
1.0 Arie Satria N 1.10.2014 Initial Draft
Method of Procedure (MOP)
 1. INTRODUCTION
Deployment Plan

This documentation describes the procedures to integration the new 10Ge link between C-
SBRKO-01 and C-BJAHY-01.

2. PERSON IN CONTACTS (PIC)

Person in contacts (PIC)

PT Lintas Teknologi Indonesia :
Hendri Sugilar
Rynal
Fajri Nurbadri P.
Arie Satria Nugraha
Eri Nugraha

3. SCHEDULE

The MPLS network setup will be done on live network and it is expected to no outage. It
is proposed to be scheduled on TBD

4. IP AND PORT ALLOCATION

Allocation port and IP design below :

112.215.109.93/30 C-SBRKO-01 xe-2/0/0

112.215.109.94/30 C-BJAHY-01 ge-5/0/0
Method of Procedure (MOP)

3
 5. IMPLEMENTATION PROCEDURE
Deployment Plan

NO DESCRIPTION COMMAND CONFIGURATION ACTION STATUS

VERIFICATION
1. General system status The purpose of this OK
section is to collect NOK
data about the router
hardware
configuration and
environment.
a Active alarm show chassis alarm
b Save the system hardware show chassis hardware
configuration for future
reference

c Voltage and temperatures show chassis environment

d Status of individual components show chassis fpc detail
2. Routing Engine and Storage The purpose of this OK
media section is to check if NOK
the routing engine
and its storage media
are all working
properly
a Routing engine status show chassis routing-engine
b Storage media on each routing show system storage
engine

3. Software Junos The purpose of this OK

section is to collect NOK
data about the router
software.
a Version show version

4
(MOP)
 NO DESCRIPTION COMMAND CONFIGURATION ACTION STATUS
show version invoke-on all-routing-engine
Deployment Plan

b Running process show system process

c Detail show system software detail
d Log show log messages |no-more
4. Capture existing configuration show configuration | no-more C-SBRKO-01 OK
and status for documentation show interfaces terse | no-more C-BJAHY-01 NOK
purpose and fallback (if needed) show interfaces extensive | no-more
show system process extensive | no-more Estimation time : 5
show bgp summary | no-more minutes
show bgp neighbor | no-more
show mpls interface | no-more
show ldp interface | no-more
show rsvp interface | no-more
show isis adjacency | no-more
show isis interface | no-more
show mpls lsp | no-more
show mpls lsp extensive | no-more
show rsvp neighbor | no-more
show rsvp neighbor detail | no-more
show rsvp session | no-more
show rsvp session detail | no-more
show ldp neighbor | no-more
show ldp neighbor extensive | no-more
show ldp session | no-more
show ldp session extensive | no-more
show route table inet.3 | no-more
show route summary | no-more
show chassis alarm | no-more

5
(MOP)
 NO DESCRIPTION COMMAND CONFIGURATION ACTION STATUS
5. Backup Current show configuration | save yyymmdd.routers-name C-SBRKO-01 OK
Deployment Plan

Configuration C-BJAHY-01 NOK

Estimation time : 1
minute
PREPARATION FOR IP AND INTERFACE CONFIGURATION
6. Configure interfaces PTP on C-SBRKO-01 : C-SBRKO-01 OK
interface xe-2/0/0 in C-SBRKO- configure private C-BJAHY-01 NOK
01 and ge-5/0/0 in C-BJAHY-01 *copy and paste command below*
then verify delete interfaces xe-2/0/0 Estimation time : 5
set interfaces xe-2/0/0 description BB_GSM_10GE_to_C-BJAHY-01_ge-5/0/0 minutes
set interfaces xe-2/0/0 mtu 4500
set interfaces xe-2/0/0 unit 0 family inet address 112.215.109.93/30

show | compare
commit check
commit synchronize and-quit

C-BJAHY-01 :
configure private
*copy and paste command below*
delete interfaces ge-5/0/0
set interfaces ge-5/0/0 description BB_GSM_10GE_to_C-SBRKO-01_xe-2/0/0
set interfaces ge-5/0/0 mtu 4500
set interfaces ge-5/0/0 unit 0 family inet address 112.215.109.94/30

show | compare
commit check

6
(MOP)
 NO DESCRIPTION COMMAND CONFIGURATION ACTION STATUS
commit synchronize and-quit
Deployment Plan

verify :
ping 112.215.109.93 rapid count 100 size 4500 bypass-routing

note :
only goes to next step if test ping is normal

7. Inject protocol to new link C-SBRKO-01 : C-SBRKO-01 OK

interface and verify configure private C-BJAHY-01 NOK
*copy and paste command below*
set interfaces xe-2/0/0 unit 0 family iso Estimation times : 5
set interfaces xe-2/0/0 unit 0 family mpls maximum-labels 5 minutes

set protocols rsvp interface xe-2/0/0.0

set protocols mpls interface xe-2/0/0.0
set protocols isis interface xe-2/0/0.0 point-to-point
set protocols isis interface xe-2/0/0.0 bfd-liveness-detection minimum-interval 500
set protocols isis interface xe-2/0/0.0 bfd-liveness-detection multiplier 3
set protocols isis interface xe-2/0/0.0 level 1 disable

show | compare
commit check
commit synchronize and-quit

C-BJAHY-01 :
configure private

7
(MOP)
 NO DESCRIPTION COMMAND CONFIGURATION ACTION STATUS
*copy and paste command below*
Deployment Plan

set interfaces ge-5/0/0 unit 0 family iso

set interfaces ge-5/0/0 unit 0 family mpls maximum-labels 5

set protocols rsvp interface ge-5/0/0.0

set protocols mpls interface ge-5/0/0.0
set protocols isis interface ge-5/0/0.0 point-to-point
set protocols isis interface ge-5/0/0.0 bfd-liveness-detection minimum-interval 500
set protocols isis interface ge-5/0/0.0 bfd-liveness-detection multiplier 3
set protocols isis interface ge-5/0/0.0 level 1 disable

show | compare
commit check
commit synchronize and-quit

verify :
show isis adjacency | no-more
show isis interface | no-more
show mpls interface | no-more
show ldp interface | no-more
show rsvp interface | no-more
show mpls lsp | no-more
show mpls lsp extensive | no-more
show rsvp neighbor | no-more

note :
make sure all protocol is normal and traffic goes through xe-2/0/0 in C-SBRKO-01 and ge-
5/0/0 C-BJAHY-01

8
(MOP)
 NO DESCRIPTION COMMAND CONFIGURATION ACTION STATUS
8. Monitor traffic for 24 hours Waiting for report from performance team (24 Hours) C-SBRKO-01 OK
Deployment Plan

C-BJAHY-01 NOK

Monitoring
9. Verify the status after show configuration | no-more C-SBRKO-01 OK
migration show interfaces terse | no-more C-BJAHY-01 NOK
show interfaces extensive | no-more
show system process extensive | no-more Estimation times : 5
show bgp summary | no-more minutes
show bgp neighbor | no-more
show mpls interface | no-more
show ldp interface | no-more
show rsvp interface | no-more
show isis adjacency | no-more
show isis interface | no-more
show mpls lsp | no-more
show mpls lsp extensive | no-more
show rsvp neighbor | no-more
show rsvp neighbor detail | no-more
show rsvp session | no-more
show rsvp session detail | no-more
show ldp neighbor | no-more
show ldp neighbor extensive | no-more
show ldp session | no-more
show ldp session extensive | no-more
show route table inet.3 | no-more
show route summary | no-more
show chassis alarm | no-more

9
(MOP)
 6. FALLBACK PLAN
FALLBACK PLAN REMARKS STATUS
Deployment Plan

load override yyyymmdd.NAME C-SBRKO-01 OK

Reload original config and commit C-BJAHY-01 NO
10.
commit
Estimation times : 1 minute
11. Capture all status same with show configuration | no-more C-SBRKO-01 OK
original show interfaces terse | no-more C-BJAHY-01 NOK
show interfaces extensive | no-more
show system process extensive | no-more Estimation time : 5 minutes
show bgp summary | no-more
show bgp neighbor | no-more
show mpls interface | no-more
show ldp interface | no-more
show rsvp interface | no-more
show isis adjacency | no-more
show isis interface | no-more
show mpls lsp | no-more
show mpls lsp extensive | no-more
show rsvp neighbor | no-more
show rsvp neighbor detail | no-more
show rsvp session | no-more
show rsvp session detail | no-more
show ldp neighbor | no-more
show ldp neighbor extensive | no-more
show ldp session | no-more
show ldp session extensive | no-more
show route table inet.3 | no-more
show route summary | no-more

10
(MOP)
 show chassis alarm | no-more
Deployment Plan

11
(MOP)
 MOP CONDITION
Deployment Plan

This MoP will be done by Lintas Teknologi Indonesia Team and has to be supervised by
authorized PT. XL Axiata Team, and the schedule shall be proposed in advance to PT. XL
Axiata.

Upon the completion of the works, Lintas Teknologi Indonesia installation team shall
inform to PT. XL Axiata that the procedures has been completed. XL Axiata should then
verify that the change has not resulted in any network outage.

SIGN-OFF FOR APPROVAL

We declare that the MOP for the abovementioned activity as defined in this document is
executed to the full satisfaction of the customer.
The following representatives from the respective organizations involved in this project are
satisfied that this document captures the full requirement for this service.

PT. XL AXIATA PT. LINTAS TEKNOLOGI INDONESIA

Method of Procedure (MOP)

___________________________ ___________________________

12
 Appendix 1 Expected Results and Test Case
Deployment Plan

No. Command Expected Result Remarks

1. show system processes extensive > show system processes extensive Normally we should see
last pid: 51088; load averages: 0.07, 0.06, 0.01 up 1333+01:52:42 18:11:22 idle processing is above
109 processes: 4 running, 87 sleeping, 1 zombie, 17 waiting 90%

Mem: 109M Active, 93M Inact, 60M Wired, 126M Cache, 69M Buf, 1109M Free
Swap: 2048M Total, 2048M Free

PID USERNAME THR PRI NICE SIZE RES STATE TIME WCPU COMMAND
11 root 1 171 52 0K 12K RUN ??? 94.92% idle
4271 root 1 96 0 22276K 8720K select 809.9H 1.81% chassisd
4353 root 1 4 0 22220K 20068K kqread 53.4H 0.00% rpd
----------------------------------truncated--------------------------------------------
2. show isis interface > show isis interface We should see L1/L2
IS-IS interface database: metric that red highlighted
Interface L CirID Level 1 DR Level 2 DR L1/L2 Metric is exactly same if we are
ae0.0 2 0x1 Disabled Point to Point 3/3 not configuring static
as1.0 2 0x1 Disabled Point to Point 32/32 metric on the IGP
fe-2/3/1.0 2 0x2 Disabled C-BJAHY-01.02 100/100
ge-4/0/0.0 2 0x1 Disabled Point to Point 10/10
----------------------------------truncated--------------------------------------------
2. show bgp summary > show bgp summary We should see
OR Groups: XX Peers: XX Down peers: 0 established bgp
show bgp summary instance xx Peer AS InPkt OutPkt OutQ Flaps Last Up/Dwn sessions with number
State|#Active/Received/Damped... of bgp sessions as
Ip-Peers AS-NUMBER 113936 97210 0 9 4w3d11h Establ expected

13
(MOP)
 XX.inet.0: XX/XX/XX
----------------------------------------truncated---------------------------------------
Deployment Plan

3 show mpls lsp > show mpls lsp We should see all LSP
Ingress LSP: 55 sessions RSVP sessions that
To From State Rt P ActivePath LSPname established or not on
112.215.48.128 202.152.247.230 Up 0 * 3G-PE-LMLPB-02-PE-LMNTR- router that executed
01 this command included
112.215.48.129 202.152.247.230 Up 0 * 3G-PE-LMLPB-02-PE-LMNTR- total session ingress ,
02 transit and egress .
----------------------------------------truncated--------------------------------------- Make sure that all LSP
Egress LSP: 71 sessions RSVP is in up condition
202.152.247.230 202.152.246.62 Up 0 1 SE 3 - 3G-PE-JBPDA-01-to-PE- if we execute this
LMLPB-02 command
202.152.247.230 202.152.247.72 Up 0 1 SE 3 - 3G_PE-JBPDA-01C_to_PE-
LMLPB-02
----------------------------------------truncated---------------------------------------
Transit LSP: 20 sessions
To From State Rt Style Labelin Labelout LSPname
112.215.48.131 202.152.247.229 Up 0 1 SE 676679 744776 Bypass-
>121.52.24.253->112.215.67.2
112.215.48.144 202.152.247.229 Up 0 1 SE 363592 593570 Bypass-
>121.52.24.253->121.52.114.94
----------------------------------------truncated---------------------------------------

4 Show ldp neighbor > show ldp neighbor We should see that all
Address Interface Label space ID Hold time ldp neighbor that
202.152.246.10 lo0.0 202.152.246.10:0 42 established and from
202.152.247.16 lo0.0 202.152.247.16:0 77 which interfaces is
----------------------------------------truncated--------------------------------------- discovered ( targeted
LDP will be established

14
(MOP)
 from lo0 ) . Make sure
Label space ID is show
Deployment Plan

lo0 ldp neighbour

prefixes IP
5 show ldp session > show ldp session We should see that all
Address State Connection Hold time address LDP session is
112.215.48.128 Operational Open 23 established or not .
112.215.48.129 Operational Open 22 Make sure that when
----------------------------------------truncated--------------------------------------- executed this command
state LDP session is in
operational and
connection is in open
state .
6 show route table inet.3 specific- > show route table inet.3 202.152.247.237 We should see route
prefixes prefixes lo0 remote
inet.3: 2397 destinations, 2967 routes (517 active, 0 holddown, 2397 hidden) router on route table
Restart Complete inet.3 if LSP RSVP or
+ = Active Route, - = Last Active, * = Both LDP session is already
up for those specific
202.152.247.237/32 *[RSVP/7] 2d 07:57:13, metric 85 remote router .
via as1.0, label-switched-path 3G-PE-LMLPB-02-PE-PLPBM-02-a Make sure that when
> via as1.0, label-switched-path 3G-PE-LMLPB-02-PE-PLPBM-02-b executed this command
to 121.52.24.21 via xe-2/0/0.0, label-switched-path 3G-PE-LMLPB-02-PE- route table inet.3 is
PLPBM-02-a available after
----------------------------------------truncated--------------------------------------- previously check that
[LDP/9] 20:43:30, metric 85 RSVP / LDP session is
via as1.0, label-switched-path 3G-PE-LMLPB-02-PE-PLPBM-02-a up
> via as1.0, label-switched-path 3G-PE-LMLPB-02-PE-PLPBM-02-b
to 121.52.24.21 via xe-2/0/0.0, label-switched-path 3G-PE-LMLPB-02-PE-
PLPBM-02-a

15
(MOP)
 ----------------------------------------truncated---------------------------------------
Deployment Plan

16
(MOP)