Professional Documents
Culture Documents
MS1NW) Mop Preventive Maintenance Asr 9K Onsite V.1.1
MS1NW) Mop Preventive Maintenance Asr 9K Onsite V.1.1
PT SISINDOKOM LINTASBUANA
Graha Astel
Jalan Pintu Air Raya No. 2A Lt. 3A
Jakarta Pusat 10710
INDONESIA
http://www.sisindokom.com
To ensure the operating device installed and managed by Telkom One Network Project
running well and to prevent major problem happen in the future, therefore Sisindokom and
PT. Telkom decides that there will be Preventive Maintenance.To fulfill Sisindokom's duty of
contract, which is 2 (two) times Preventive Maintenance on 1 (one) contractual year.
1.1. Audience
The document can be used by Telkom and/or Telkomsel engineering teams who will be
responsible for the operating system deployment.
1.2. Comment
Loopback Status
No. Area PoP Hostname Address Node Current SW Platform
R2.JT2.RR-TSEL.1 119.98.9.153 In Service IOS-XE 16.12.05 ASR1002-X
1 STO Telkom R2.JT2.ASBR-TSEL.1 119.98.9.136 In Service IOS-XR 6.7.3 ASR-9010-DC-V2
Jatinegara
R2.BRN.ASBR-TSEL.1 119.98.9.133 In Service IOS-XR 6.7.3 ASR-9010-DC-V2
R2.CKA.RR-TSEL.2 118.98.9.167 In Service IOS-XE 16.12.05 ASR1002-X
2 STO Telkom R2.CKA.ASBR-TSEL.1 119.98.9.135 In Service IOS-XR 6.7.3 ASR-9006-DC-V2
Cikupa
R2.TBS.ASBR-TSEL.1 119.98.9.134 In Service IOS-XR 6.7.3 ASR-9010-DC-V2
3 TTC Buaran R2.BRN.RR-TSEL.1 119.98.9.137 In Service IOS-XE 16.12.05 ASR1002-X
4 TTC TB R2.TBS.RR-TSEL.2 118.98.9.166 In Service IOS-XE 16.12.05 ASR1002-X
Simatupang
TTC R3.STA.PE-TSEL.1 119.98.9.138 In Service IOS-XR 6.7.3 ASR-9010-DC-V2
5 Soekarno
Hatta R3.STA.PE-TSEL.2 119.98.9.139 In Service IOS-XR 6.7.3 ASR-9010-DC-V2
R3.DG1.PE-TSEL.1 118.98.9.164 In Service IOS-XR 6.7.3 ASR-9010-DC-V2
6 TTC Dago
R3.DG1.PE-TSEL.2 118.98.9.165 In Service IOS-XR 6.7.3 ASR-9010-DC-V2
2. DEVICE LIST
Below is the table consist of all of device which in the Sisindokom SOW, with site
information details and other critical information, such as Software Version, Loopback
Address, and Device Platform
3. EXECUTIVE SUMMARY
ACTIVITY SUMMARY
Activity Name Preventive Maintenance One Network Node
Objective Activity To maintenance One Network node to analyze and
measure possible problem outcome later.
Category Of Work High
Service Impact No
Prerequisite Onsite
IMPACT ANALYSIS
Node Bandwidth Analysis Power Analysis Impact
R2.JT2.ASBR-TSEL.1 Since this node will be Power redundancy failover No impact service
performed with link test will not be performed.
redundancy check, check
the link utilization first
with cacti, if the average
link utilization is below
40%, therefore it's safe to
continue with the test.
R2.CKA.ASBR-TSEL.1 Since this node will be Power redundancy failover No impact service
performed with link test will not be performed
redundancy check, check
the link utilization first
with cacti, if the average
link utilization is below
40%, therefore it's safe to
continue with the test.
R2.BRN.ASBR-TSEL.1 Since this node will be Power redundancy failover No impact service
performed with link test will not be performed
MS1NW – Preventive Maintenance ASR 9k
Below is the global topology One Network of Jawa Barat & Jabo Area :
5. PREVENTIVE MAINTENANCE
2. Commit configuration :
Write memory (IOS/IOS XE) / commit (IOS XR)
Check
EXPECTED
NO ACTION & STEP COMMAND STATUS
OUTPUT
5. Check System Health show proc cpu Check Ensure the CPU and
show proc mem Memory Process is
of the Device show memory summary Below 70%, Report to
show logging the PIC if the process
show environment is Above 70%
Notes :
2. Commit configuration :
Write memory (IOS/IOS XE) / commit (IOS XR)
Check
Window Time
No. Activity Remarks
Duration Start End
No Service
1. pre-activity task 20 min Impact / No
Downtime
No Service
2. physical check 30 min Impact / No
Downtime
No Service
3. system check 20 min Impact / No
Downtime
No Service
system power supply and
4. 30 min Impact / No
grounding system
Downtime
5. RSP Redundancy check 30 min Downtime
No Service
6. Power redundancy check 20 min Impact / No
Downtime
Downtime
7. Link redundancy check 20 min
No Service
6. post-activity task 20 min Impact / No
Downtime
7. FALLBACK PROCEDURE
No fallback procedure
8. REPORTING
Field engineer must report all anomaly findings to Technical Leader and Project Manager.
Those findings will be informed to the end user to be follow up by Sisindokom team which
permission from the Client user.