RFC Overview

Change Ticket ID #
Change Subject Upgrade Firmware Aruba WLC
Change Description Upgrade Firmware Aruba WLC version 8.6.0.6 to 8.10.0.5

Change Initiator Email ID satrio.wicaksono@traveloka.com

(with @traveloka.com)
Change Type Moderate Change
(based on the Change
Announcement Type *Assessment Tool) Yes
Required
Announcement Draft Hi @channel,

We need to inform you that we will have maintenance activity for Network Connectivity on 09
(Jakarta-ID Local Time) on GOP1. During this maintenance activity, You will not be able to

Please, if you have activity on Midpoint during the maintenance period, we are suggest you'r
maintenance or used LAN cable .

Regards,
Service Desk,

List of Impacted Configuration Items / ID-MP-16FL-WLC01 & ID-MP-16FL-WLC02

Services
Business Justification (Impact of NOT This version is got security bug. So it need to upgrade firmware for fixed
Implementing the Change)
Outputs/ Outcomes of the Change Firmware version is updated to 8.10.0.5
Plan Start Date/Time: 12/9/2022 20:00:00
Plan Finish Date/Time: 12/10/2022 5:00:00
RFC Revision Log

Change Management (CM) Roles & Responsibilities

CM Roles Email ID
Change Coordinator it-tubagus.panca@traveloka.com
Change Initiator mfahrul.rozi@traveloka.com
Change Initiator satrio.wicaksono@traveloka.com
Change Implementer it-bimo.prayudha@traveloka.com
Change Implementer it-faisal.ramadhoni@traveloka.com
Change Implementer it-abi.virgiawan@traveloka.com
Change Implementer it-adi.sopian@traveloka.com
Change Implementer it-agung.rahmatullah@traveloka.com
Change Implementer it-michael.apriadi@traveloka.com
Peer Reviewer muhammad.daivan@traveloka.com
Change Tester mfahrul.rozi@traveloka.com
Change Tester satrio.wicaksono@traveloka.com
 RFC Overview

sion 8.6.0.6 to 8.10.0.5

have maintenance activity for Network Connectivity on 09 Aug 2022 20.00 PM - 10 Aug 2022 05.00 AM GMT+7
During this maintenance activity, You will not be able to connect to wireless connection on Midpoint .

oint during the maintenance period, we are suggest you're to change the time work schedule during the

FL-WLC02
it need to upgrade firmware for fixed
0.0.5

nagement (CM) Roles & Responsibilities

Department Remarks
IT Service Delivery
IT Infra
IT Infra
IT Service Delivery
IT Service Delivery
IT Service Delivery
IT Service Delivery
IT Service Delivery
IT Service Delivery
IT Strategy & Service Management
IT Infra
IT Infra
 Planned Start:

Preparation
1.1
1.2
1.3
1.4
1.5
1.6
1.7
Replacement
2.1
2.2
2.3
2.4
2.5
2.6
2.7
2.8
Verification
3.1

Rollback
4.1
4.2
 9/12/22 19:59
Activities
ration
Step by step :
-Step Login
byWEB
step UI
: > Maintenance > Configuration Management > Backup > Flash > Create Backup > Configuration >
- Login WEBArubaOS
Download UI > Maintenance
8.10.0.5 > Configuration Management > Backup > Flash > Create Backup > Configuration >
Conservative Release from Aruba support portal.
Step by step :
-StepLogin
byCLI > show
step : memory
-Step
Login
byCLI > show
step : storage
-Step
Login
byCLI > show
step : image version
- Open CMD on Windows > CD to directory ArubaOS has been downloaded > certutil -hashfile ArubaOS version
acement - Login WEB UI > Maintenance > Upgrade :
-Check Upgrade
and using : Local File
boot partition ID-MP-16FL-WLC01
-Step Image
by file
step name
: : Browse to the file on Windows
Preload Image AP ID-MP-16FL-WLC01
-Step Login
byWEB
step UI
: >ID-MP-16FL-WLC01
Maintenance > Boot Parameter > Boot Partition > Partition 0 > Apply
Reboot system
-Step Login
byWEB
step UI
: >> Maintenance > Access Point > Preload Image > Enable Preload Image > Apply
- Login WEB UI Maintenance > Upgrade :
-- Login WEB UI >: Maintenance
Upgrade > Reboot
Check and using Local File
boot partition ID-MP-16FL-WLC02
-Step
Image file name
by step : : Browse to the file on Windows
Preload Image AP ID-MP-16FL-WLC02
- Login WEB UI > Maintenance > Boot Parameter > Boot Partition > Partition 1 > Apply
Step
Rebootby system
step : ID-MP-16FL-WLC02
-Step
Login
by step UI
WEB : > Maintenance > Access Point > Preload Image > Enable Preload Image > Apply
- Login WEB UI > Maintenance > Reboot
ication
Verify OS & Connectivity

ack
Revert to existing configuration
Test connecion traffic
 Duration
Assignee Start Finish
(dd hh:mm)

PSI 09/12/22 19:59 0d 00:05 09/12/22 20:04

PSI 09/12/22 20:04 0d 00:05 09/12/22 20:09
PSI 09/12/22 20:09 0d 00:10 09/12/22 20:19
PSI 09/12/22 20:19 0d 00:05 09/12/22 20:24
PSI 09/12/22 20:24 0d 00:05 09/12/22 20:29
PSI 09/12/22 20:29 0d 00:06 09/12/22 20:35
PSI 09/12/22 20:30 0d 00:05 09/12/22 20:35

PSI 09/12/22 20:05 0d 00:20 09/12/22 20:25

PSI 09/12/22 20:25 0d 00:05 09/12/22 20:30
PSI 09/12/22 20:30 0d 00:05 09/12/22 20:35
PSI 09/12/22 20:35 0d 00:05 09/12/22 20:40
PSI 09/12/22 20:40 0d 00:30 09/12/22 21:10
PSI 09/12/22 21:10 0d 00:05 09/12/22 21:15
PSI 09/12/22 21:15 0d 00:30 09/12/22 21:45
PSI 09/12/22 21:45 0d 00:10 09/12/22 21:55

PSI 09/12/22 21:54 0d 00:15 09/12/22 22:09

PSI 09/12/22 22:09 0d 00:30 09/12/22 22:39

PSI 09/12/22 22:39 0d 00:15 09/12/22 22:54
Remarks
 CHANGE TY

Change Type Assessment Questionnaire

Category Risk Assessment Question

As a change initiator/owner, you are required to be

1. Change Owner responsibility
familiar with all process documentation.

2. Critical Services How are critical services impacted by this change?

How does this change alter the security model of

BUSINESS IMPACT

3. Security applications or platforms? (e.g. policies, access rights

etc.)

Have all involved or impacted business units, IT

4. Consultation
services, and other stakeholders been consulted?

In case the change fails in the worst possible way,

5. Type of incidents in case of failure what type of incident would business/stakeholders
experience?

6. Workaround Is there a workaround if business functionality is lost?

Is this change occurring during the ITG weekend

7. Maintenance window
Maint. Window?

How many other support teams are needed to deploy

8. Number of touch points this change (including project, platform, services,
business, vendor and support teams)

9. Historical incidents How many High/Critical incidents due to changes in

your technology domain/platform [or application]
RE PROBABILITY

have occurred in the past 12 months?

FAILURE PROBABILITY
What is the size and complexity of a change to
10. Size and complexity
determine the magnitude of impact?

Who has performed testing, conducted an

11. Testing
independent review or examined the test results?

12. Service validation

How will all the involved services be validated for
functionality?
NOTE: Change Owner is responsible for Technical
validation. Functional validation can be performed by
Peer, BSA, Users or QM

What strategy is in place should the change fail post

13. Back out plan
production validation?

Business Impact Score

21
CHANGE TYPE ASSESSMENT TOOL

Your Change Model

Answer Choice (Please choose from drop down) Minor Change

I accept responsibility.

Up/downstream impact on critical services

No security model alteration

Everyone was consulted.

High or critical incident

No known business workaround exists

Outside the window and approved by users

My team and 1–3 other teams

One high/critical incident

Moderate levels of size and complexity; moderate impact

Change coordinator and approver

Full technical and functional validation

Fix forward or back out.

Failure Probability Score

18
Change Model

Moderate Change Major Change

Change Type

Failure
Probability

Moderate Risk High Risk High Risk

Likely

Low Risk Moderate Risk High Risk

Possible

Low Risk Low Risk Moderate Risk

Unlikely

Business
Low Medium High Impact
# Risk Description Likelihood Impact

1 Upgrade firmware fail Possible Low

 Implication on Change implementation Prevention/Mitigation

Upgrade firmware fail and all service running on device will

Revert to existing config
distrubted
ID Test Cases Description
C.1 check firmware version check firmware version
C.2 check connection Ping and Traceroute
Measure of Success Result
version update version update
Reachable Ping Success
 TC # Test Scenario / Test Case Name Preconditions(If any) Steps to execute

<Input the Test <Input Application/Software/System

<Input Test Case/Scenario Name> <Input required steps in this test case scenario>
Case Number/ID> Preconditions (If any)>
 TEST CASE SCENARIO & TEST RESULTS

Expected Result Comment/Remarks Actual Result

<Input the predefined expected result of the

<Input Comment/Remarks (If Any)> <Input the Actual Results>
UAT>
ST RESULTS

Pass/Fail
Tested On Test Defect Description Re-Tested On
(Iteration 1)

<Input the test Defect for failed UAT

<Input the test date> <Input Pass/Fail> <Input the 2nd iteration test date>
on 1st iteration>
 Pass/Fail
Test Defect Description Tested by
(Iteration 2)

<Input the test Defect for failed UAT on

<Input Pass/Fail> <Input UAT Tester Name>
2nd iteration>