fail over test

8/3/2019 Fail Over Test

1/379

# Question Res onse

M1Is this an Infrastructure or an Application Change?

Application

M2

Is this change subject to a Change Management Approved agreement - i.e. CAMRequest - which specifies that a cut down version or non standard version of the

RFC Tem late can be used

No

M3

Is Business outage required? No

M3a If a Business outa e what is the outa e duration? 3 hoursM3b If a Business outa e is it scheduled outside normal Business workin eriods? YesM4 Is the chan e window art of a WCC eriod? NoM5 Is this chan e window art of a Ke Event i.e. Stabilit Period Turnaround ? No

I1Is this a Shared Infrastructure Change? No

M6 What Se ments/Functions does this chan e im act Functions

M7a Risk & Im act clarification 1 NoM7b Risk & Im act clarification 2M7c Risk & Im act clarification 3 No

A1

Is there a change to the Access Controls setup of the system? No

A2

Is there a change to the Data Classification within the application? No

A3 Are an external links or FireWall chan es included in this chan e? NoM8 Does this chan e amend the Su ort Model in an wa ? NoM9 Does this chan e include a Version U rade? NoM10 Does this Chan e relate to a Ma or Pro ect? No

M11Does this change include any Decommissioning activities No

# Question Res onse

Mp1 Are Business Communications re uired to su ort this chan e?Yes

Mp2 Are Technical Communications re uired to su ort this chan e?

Yes

Mp3

Have all teams who need to be involved in, or aware of the change been engaged

with?Yes

Mp4 What environment is this chan e bein made in Production

Mp5

Does this change follow a pre-defined Test Plan that has been formally reviewed

and a roved and is ublishedNo

N

This Worksheet MUST be completed for all changes - your responses will provide g

review

If some detail is missing or not all results are sh

General Guidelines and

RFC Reference: CRQ000000049324


2/379


3/379

Guidelines

1. Testing Tables

2. Engagement Meetings

3. Communications

4. External Resources and Engineers

Is testing complete at the time of attaching this RFC Templa

Test Case

1. This implementation would be only on production systems,

to make sure the availablity of cluster, in case of any major

incident or failure of some service

Is testing complete at the time of attaching this RFC Templa

System Testing


4/379

Meeting Title/Purpose

List External Resource / Engineer

Provide det

Provide details of Communicati

Provide details of External


5/379


6/379


7/379


8/379


9/379


10/379


11/379


12/379


13/379


14/379

NO Testing completion Date

enter date whether

completed or not

Tester Pre-Change Test Stat Comment

NO Testing completion Date

enter date whether

completed or not

Tester Pre-Change Test Stat Comment

environment(s) testing performed in >

This tab must list all activities that need to be completed in preparation for the

final implementation to ensure that all possible Risk Mitigation is in place

our change ticket will not pass validation & you will not gain approval for this

change

-Testing plan

-Pre-Testing Log

Detail test plans, testers and test results - if referring to other documents these

must be accessible by all reviewers of the RFC, with the location of the document

provided below - if attached to the RFC state which Work Info Record they areIt is the responsibility of the Change Assignee to ensure all impacted parties are

engaged with in preparation for the change activity. Details of these engagements

Ensure these are considered as part of the Prior Preparation and Planning

activities and are clearly documented in Tab 7 Communications Plan

If it is necessary to secure any external resource for the change activity details

must be provided - typically this will be an engineer. In the context of Rig, Tanker

or similar changes where transportation etc is critical, therefore timing for

external resources has a significant implication on the success/failure of the


15/379

Attendees Attendee Role & Org

Comment (was

objective met?)

yes

Justification for using

external

resource/engineer

na a e can e

booked to meet

planned

implementation

window? To be booked by?

ils of Engagement Meetings

ns activities - Go to Tab 7 Communications Plan

Resources and/or Engineers to be booked


16/379


17/379


18/379


19/379


20/379


21/379


22/379


23/379


24/379


25/379


26/379


27/379


28/379


29/379


30/379


31/379


32/379


33/379


34/379


35/379


36/379


37/379


38/379


39/379


40/379


41/379


42/379


43/379


44/379


45/379


46/379


47/379


48/379


49/379


50/379


51/379


52/379


53/379


54/379


55/379


56/379


57/379


58/379


59/379


60/379


61/379


62/379


63/379


64/379


65/379


66/379


67/379


68/379


69/379


70/379


71/379


72/379


73/379


74/379


75/379


76/379


77/379


78/379


79/379


80/379


81/379


82/379


83/379


84/379


85/379


86/379


87/379


88/379


89/379


90/379


91/379


92/379


93/379


94/379


95/379


96/379


97/379


98/379


99/379


100/379


101/379


102/379


103/379


104/379


105/379


106/379


107/379


108/379


109/379


110/379


111/379


112/379


113/379


114/379


115/379


116/379


117/379


118/379


119/379


120/379


121/379


122/379


123/379


124/379


125/379


126/379


127/379


128/379


129/379


130/379


131/379


132/379


133/379


134/379


135/379


136/379


137/379


138/379


139/379


140/379


141/379


142/379


143/379


144/379


145/379


146/379


147/379


148/379


149/379


150/379


151/379


152/379


153/379


154/379


155/379


156/379


157/379


158/379


159/379


160/379


161/379


162/379


163/379


164/379


165/379


166/379


167/379


168/379


169/379


170/379


171/379


172/379


173/379


174/379


175/379


176/379


177/379


178/379


179/379


180/379


181/379


182/379


183/379


184/379


185/379


186/379


187/379


188/379


189/379


190/379


191/379


192/379


193/379


194/379


195/379


196/379


197/379


198/379


199/379


200/379


201/379


202/379


203/379


204/379


205/379


206/379


207/379


208/379


209/379


210/379


211/379


212/379


213/379


214/379


215/379


216/379


217/379


218/379


219/379


220/379


221/379


222/379


223/379


224/379


225/379


226/379


227/379


228/379


229/379


230/379


231/379


232/379


233/379


234/379


235/379


236/379


237/379


238/379


239/379


240/379


241/379


242/379


243/379


244/379


245/379


246/379


247/379


248/379


249/379


250/379


251/379


252/379


253/379


254/379


255/379


256/379


257/379


258/379


259/379


260/379


261/379


262/379


263/379


264/379


265/379


266/379


267/379


268/379


269/379


270/379


271/379


272/379


273/379


274/379


275/379


276/379


277/379


278/379


279/379


280/379


281/379


282/379


283/379


284/379


285/379


286/379


287/379


288/379


289/379


290/379


291/379


292/379


293/379


294/379


295/379


296/379


297/379


298/379


299/379


300/379


301/379

Guidelines

Pre-implementation check

Make sure that, are able to login to OS level and cluster level

Pre-requisites1. Get the confirmation from the unix team before

implementation, that every thing fine to implement

Check-

If some detail is missing or not all results are showing,

If Pre-implementation r

Pre-implemen

-Pre-im

-Pre


302/379


303/379


304/379


305/379


306/379


307/379


308/379


309/379


310/379


311/379

Checked by

Verified By

Point Go\No Go decission

our change ticket will not pass validation & you will not gain approval for this

change

Comments

eceives a no go do not proceed further

This tab must list all non-intrusive checks that must be performed before the

Implementation activity is started - i.e.

a) Confirm any testing that was not finished when the RFC template was finalisedhas been successfully completed

b) Confirm all hardware, CDs, cables, external resources etc are in place and

working

c) Confirm site access is available

d) Check that the RFC is fully approved and scheduled

e) Check that all pre-Implementation Comms have been issued and no

outstanding concerns have been raised

f For com lex chan es check all teams are available and read

tation checks & Pre-requisites

plementation checks/steps

Comments

-requisites checks/steps

Praveen Pothula

Srinivas kalluri


312/379


313/379


314/379


315/379


316/379


317/379


318/379


319/379


320/379


321/379


322/379


323/379


324/379


325/379


326/379


327/379


328/379


329/379


330/379


331/379


332/379

Guidelines

Description

Check tabs 2 and 3 have been completed

Description

Stop the batch jobs using Btctrns1 report

Logon to CI Os level

Login to Verital cluster in operating system level

Bring the system online to other node

Check, whether all the services are shifted or not

Login to the Sap system and check,able to login SAP or not through the gui

Switch back to the original node

Execute the btctrns2

TIME ZONE

If above


333/379

System outage details

Description

For Trouble Shooting Ongoing Support will be pro

If above receives a no go do n

Implement

If above receives a no go


334/379


335/379

10-Dec-11 8:30 AM IST 11:30 AM IST3 hours praveen

pothula

Date Start Time End Time Duration

[Minutes]

Owner Contacts

See contact

list

ONGOING SUPPORT

heck-Point Go\No Go decision

ided during change window, please dial into the Telecom Bridge in order to arrange proble

heck-Point Go\No Go decision

t proceed further and invoke Backout plan detailed on Tab 5

tion tests & Post Implementation results

do not proceed further and request further information


336/379

Comment Telecom

Bridge

Comment Telecom

Bridge

lan 1st step

ange

a result in GMT bein

eir tasks.

vide details including the

vided in this tab

e RFC Change Window

e provided or

es, once per server>

t gain approval


337/379

Comment Telecom

Bridge

solving.


338/379

Start Time

Date Start Time

Logon to CI Os level10-Dec-11 12:30 PM IST

Login to Verital cluster in operating system level10-Dec-11

1:00 PM IST

Bring back the system to original node

10-Dec-11

3:00 PM IST

Date Start

Time

End Time

Implementation

time

This plan needs to document the timing at which the Remediation Plan should be invok

The plan also needs to include who can authorise the implementation of the remediatio

Remediation Tasks (Describe type and tasks involved, break down into logical steps useReference any external documentation already completed.

Include any system dependencies etc.

If external resources required add check points by their tasks.


339/379


340/379

Post App Remediation

Testing Testing Point

End Time Duration

[Minutes]

Owner Contacts Comment

1:00 PM IST :30 MinPraveen

Pothula

3:00 PM IST 2 hours Praveen

Pothula

3:30 PM IST :30 Min

Praveen

Pothula

Duration

Minutes

Owner Contacts Comment Telecom

Brid e

d i.e. at what stage is the Change implementation considered unsuccessful.

plan.

1 row per step)


341/379


342/379

Change

End

Telecom

Bridge2. Ensure your Remediation plan

addresses all of the possibilities

identified above.3. Provide steps in detail for

implementing the plan.4. Estimate t e ina reme iation point

- the lastest time that a Remediation

plan can be started and service stilled

returned to the users within the

Change Window.implemenation of the Remediation6. What tests will be carried out to

ensure the remediation has been

successful?


343/379

Guidelines

Description1. Perform the sanity checks

Post

If some detail is missing or not all re

validation & you w

Post


344/379


345/379


346/379


347/379


348/379


349/379


350/379


351/379


352/379


353/379

Owner Post Implementation Status Comment

Praveen Pothula

Implementation Steps

ults are showing, your change ticket will not pass

ill not gain approval for this change

Implementation Steps

This tab must list all the post-testing (note included as part of the

Implementation/Remediation checks/tests) or steps to be performed after

implementing in production include application and infrastructure (whereapplicable), with results, and should include links to the necessary documents that

show how this post testing or steps will be done and expected results.

After every change remember to update the CMDB, if required, as appropriate for

the activities carried out durin the chan e - other exam les rovided delete if


354/379


355/379


356/379


357/379


358/379


359/379


360/379


361/379


362/379


363/379


364/379


365/379


366/379


367/379


368/379


369/379


370/379


371/379


372/379


373/379


374/379

Guidelines

Date Time Owner

1-Dec-11 11:00:00 AM ISTPraveen

Pothula

Date Time Owner

9-Dec-11 1:00 AM ISTSrinivas

kalluri

9-Dec-11 1:00 AM ISTSrinivas

kalluri

Date Time Owner

Imple

Description

Infor unix team on this activity and

ask their support for this activity

Pre-Impl

Inform functional team about the

activity

Description

Description

If some detail is missing or not all results are showing, your chang

This tab must list the communications plan steps in deep

include any links to the necessary documents that will facil

process.

Reference any external documentation already completedInclude any system or tasks dependencies etc. If external

The plan should explain what activities will be undertaken

Who is going to manage the communications

Who will be communicated to, why and when

What communications have already been completed as

Key communication milestones (planning, before, during

Any dependencies.

Prior Preparati

Inform security team for the

required access


375/379

Date Time Owner

Post Impl

Description


376/379

Comms

To

Security

team

Comms

To

FI team

and

Securiety

team

Unix team

Comms

To

entation Stage

Summary of Communications

mentation StageSummary of Communications


ticket will not pass validation & you will not gain approval for this change

etail, use one row for each step,

litate or be used in the communications

.resources required add check points by their tasks.

to deliver the communications including:

part of the preparation of the change

and post implementation)

on and Planning Stage


377/379

Comms

To

ementation Stage



378/379

Is a Conference Bridge Available? As Needed Start Time: Add Details in End Time:

Bridge Telecom 281-892-7000Participant

Passcode:5705755

Role First Name Last Name Organization Work Phone Mobile Phone

Change Owner Praveen Pothula +91 9663014555

Change Assignee Bhupesh Chimanlal IBM Basis 080-41956186 +91 9740205513

Backup Change Assignee Praveen Pothula IBM Basis 080-41956186 09663014555

Change Implementer Syed Ahmed IBM Basis 080-41956186

Backup Change Implementer Lingaraj Nadagoudar IBM Basis 080-41956186 09972311330

Change Coordinator Bhupesh Chimanlal IBM Basis 080-41956186 +91 97402 05513

Backup Change Coordinator ronald IBM Basis 080-41956186

Conference Bridge Owner kishore IBM Basis +1 630-836-5582

Infrastructure Contacts

Production Basis Llead Bhupesh Chimanlal IBM Basis +91 80 4195 6186 +91 97402 05513

Unix Team Support Dilip Janbhale Unix Team 91-9881476390 91-9881476390

Application Contacts

PR9 App Mgr Oswin Fernando BS&S +44 (0) 2031 078341

Business / Other Contacts

RRO App Mgr Oswin Frenando B&SS +44 (0) 2031 078341

PR9 App Mgr Oswin Fernando BS&S +44 (0) 2031 078341

Infrastructure & Cutover Manager

RRO App Mgr

PRO App Mgr

Infrastructure & Cutover Manager

Remediation (Backout) Plan Key Decision Makers - if fully documented above it is acceptable to just

Go/No Go Key Decision Makers - if fully documented above it is acceptable to just include t

If some detail is missing or not all results are showing, your change ticket will not pass validation

Contact and Telecom details will be required for all MAJOR changes. For normal changes contact and tele

Contact and Telecom details

CommunicationsIf Business and/or Technical Communications are planned these should be documented in Section

Please list any contacts required as part of the change implementation and remediation

CH1 O5 - Contact list

Created on 5/3/2012 9:49 PM


379/379

V1.8 Dave Ray

V1.9

Kay

Thomas

Version

Number

Author Approver(s)

fail over test

Documents