fail over test
TRANSCRIPT
-
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
-
8/3/2019 Fail Over Test
2/379
-
8/3/2019 Fail Over Test
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
-
8/3/2019 Fail Over Test
4/379
Meeting Title/Purpose
List External Resource / Engineer
Provide det
Provide details of Communicati
Provide details of External
-
8/3/2019 Fail Over Test
5/379
-
8/3/2019 Fail Over Test
6/379
-
8/3/2019 Fail Over Test
7/379
-
8/3/2019 Fail Over Test
8/379
-
8/3/2019 Fail Over Test
9/379
-
8/3/2019 Fail Over Test
10/379
-
8/3/2019 Fail Over Test
11/379
-
8/3/2019 Fail Over Test
12/379
-
8/3/2019 Fail Over Test
13/379
-
8/3/2019 Fail Over Test
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
-
8/3/2019 Fail Over Test
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
-
8/3/2019 Fail Over Test
16/379
-
8/3/2019 Fail Over Test
17/379
-
8/3/2019 Fail Over Test
18/379
-
8/3/2019 Fail Over Test
19/379
-
8/3/2019 Fail Over Test
20/379
-
8/3/2019 Fail Over Test
21/379
-
8/3/2019 Fail Over Test
22/379
-
8/3/2019 Fail Over Test
23/379
-
8/3/2019 Fail Over Test
24/379
-
8/3/2019 Fail Over Test
25/379
-
8/3/2019 Fail Over Test
26/379
-
8/3/2019 Fail Over Test
27/379
-
8/3/2019 Fail Over Test
28/379
-
8/3/2019 Fail Over Test
29/379
-
8/3/2019 Fail Over Test
30/379
-
8/3/2019 Fail Over Test
31/379
-
8/3/2019 Fail Over Test
32/379
-
8/3/2019 Fail Over Test
33/379
-
8/3/2019 Fail Over Test
34/379
-
8/3/2019 Fail Over Test
35/379
-
8/3/2019 Fail Over Test
36/379
-
8/3/2019 Fail Over Test
37/379
-
8/3/2019 Fail Over Test
38/379
-
8/3/2019 Fail Over Test
39/379
-
8/3/2019 Fail Over Test
40/379
-
8/3/2019 Fail Over Test
41/379
-
8/3/2019 Fail Over Test
42/379
-
8/3/2019 Fail Over Test
43/379
-
8/3/2019 Fail Over Test
44/379
-
8/3/2019 Fail Over Test
45/379
-
8/3/2019 Fail Over Test
46/379
-
8/3/2019 Fail Over Test
47/379
-
8/3/2019 Fail Over Test
48/379
-
8/3/2019 Fail Over Test
49/379
-
8/3/2019 Fail Over Test
50/379
-
8/3/2019 Fail Over Test
51/379
-
8/3/2019 Fail Over Test
52/379
-
8/3/2019 Fail Over Test
53/379
-
8/3/2019 Fail Over Test
54/379
-
8/3/2019 Fail Over Test
55/379
-
8/3/2019 Fail Over Test
56/379
-
8/3/2019 Fail Over Test
57/379
-
8/3/2019 Fail Over Test
58/379
-
8/3/2019 Fail Over Test
59/379
-
8/3/2019 Fail Over Test
60/379
-
8/3/2019 Fail Over Test
61/379
-
8/3/2019 Fail Over Test
62/379
-
8/3/2019 Fail Over Test
63/379
-
8/3/2019 Fail Over Test
64/379
-
8/3/2019 Fail Over Test
65/379
-
8/3/2019 Fail Over Test
66/379
-
8/3/2019 Fail Over Test
67/379
-
8/3/2019 Fail Over Test
68/379
-
8/3/2019 Fail Over Test
69/379
-
8/3/2019 Fail Over Test
70/379
-
8/3/2019 Fail Over Test
71/379
-
8/3/2019 Fail Over Test
72/379
-
8/3/2019 Fail Over Test
73/379
-
8/3/2019 Fail Over Test
74/379
-
8/3/2019 Fail Over Test
75/379
-
8/3/2019 Fail Over Test
76/379
-
8/3/2019 Fail Over Test
77/379
-
8/3/2019 Fail Over Test
78/379
-
8/3/2019 Fail Over Test
79/379
-
8/3/2019 Fail Over Test
80/379
-
8/3/2019 Fail Over Test
81/379
-
8/3/2019 Fail Over Test
82/379
-
8/3/2019 Fail Over Test
83/379
-
8/3/2019 Fail Over Test
84/379
-
8/3/2019 Fail Over Test
85/379
-
8/3/2019 Fail Over Test
86/379
-
8/3/2019 Fail Over Test
87/379
-
8/3/2019 Fail Over Test
88/379
-
8/3/2019 Fail Over Test
89/379
-
8/3/2019 Fail Over Test
90/379
-
8/3/2019 Fail Over Test
91/379
-
8/3/2019 Fail Over Test
92/379
-
8/3/2019 Fail Over Test
93/379
-
8/3/2019 Fail Over Test
94/379
-
8/3/2019 Fail Over Test
95/379
-
8/3/2019 Fail Over Test
96/379
-
8/3/2019 Fail Over Test
97/379
-
8/3/2019 Fail Over Test
98/379
-
8/3/2019 Fail Over Test
99/379
-
8/3/2019 Fail Over Test
100/379
-
8/3/2019 Fail Over Test
101/379
-
8/3/2019 Fail Over Test
102/379
-
8/3/2019 Fail Over Test
103/379
-
8/3/2019 Fail Over Test
104/379
-
8/3/2019 Fail Over Test
105/379
-
8/3/2019 Fail Over Test
106/379
-
8/3/2019 Fail Over Test
107/379
-
8/3/2019 Fail Over Test
108/379
-
8/3/2019 Fail Over Test
109/379
-
8/3/2019 Fail Over Test
110/379
-
8/3/2019 Fail Over Test
111/379
-
8/3/2019 Fail Over Test
112/379
-
8/3/2019 Fail Over Test
113/379
-
8/3/2019 Fail Over Test
114/379
-
8/3/2019 Fail Over Test
115/379
-
8/3/2019 Fail Over Test
116/379
-
8/3/2019 Fail Over Test
117/379
-
8/3/2019 Fail Over Test
118/379
-
8/3/2019 Fail Over Test
119/379
-
8/3/2019 Fail Over Test
120/379
-
8/3/2019 Fail Over Test
121/379
-
8/3/2019 Fail Over Test
122/379
-
8/3/2019 Fail Over Test
123/379
-
8/3/2019 Fail Over Test
124/379
-
8/3/2019 Fail Over Test
125/379
-
8/3/2019 Fail Over Test
126/379
-
8/3/2019 Fail Over Test
127/379
-
8/3/2019 Fail Over Test
128/379
-
8/3/2019 Fail Over Test
129/379
-
8/3/2019 Fail Over Test
130/379
-
8/3/2019 Fail Over Test
131/379
-
8/3/2019 Fail Over Test
132/379
-
8/3/2019 Fail Over Test
133/379
-
8/3/2019 Fail Over Test
134/379
-
8/3/2019 Fail Over Test
135/379
-
8/3/2019 Fail Over Test
136/379
-
8/3/2019 Fail Over Test
137/379
-
8/3/2019 Fail Over Test
138/379
-
8/3/2019 Fail Over Test
139/379
-
8/3/2019 Fail Over Test
140/379
-
8/3/2019 Fail Over Test
141/379
-
8/3/2019 Fail Over Test
142/379
-
8/3/2019 Fail Over Test
143/379
-
8/3/2019 Fail Over Test
144/379
-
8/3/2019 Fail Over Test
145/379
-
8/3/2019 Fail Over Test
146/379
-
8/3/2019 Fail Over Test
147/379
-
8/3/2019 Fail Over Test
148/379
-
8/3/2019 Fail Over Test
149/379
-
8/3/2019 Fail Over Test
150/379
-
8/3/2019 Fail Over Test
151/379
-
8/3/2019 Fail Over Test
152/379
-
8/3/2019 Fail Over Test
153/379
-
8/3/2019 Fail Over Test
154/379
-
8/3/2019 Fail Over Test
155/379
-
8/3/2019 Fail Over Test
156/379
-
8/3/2019 Fail Over Test
157/379
-
8/3/2019 Fail Over Test
158/379
-
8/3/2019 Fail Over Test
159/379
-
8/3/2019 Fail Over Test
160/379
-
8/3/2019 Fail Over Test
161/379
-
8/3/2019 Fail Over Test
162/379
-
8/3/2019 Fail Over Test
163/379
-
8/3/2019 Fail Over Test
164/379
-
8/3/2019 Fail Over Test
165/379
-
8/3/2019 Fail Over Test
166/379
-
8/3/2019 Fail Over Test
167/379
-
8/3/2019 Fail Over Test
168/379
-
8/3/2019 Fail Over Test
169/379
-
8/3/2019 Fail Over Test
170/379
-
8/3/2019 Fail Over Test
171/379
-
8/3/2019 Fail Over Test
172/379
-
8/3/2019 Fail Over Test
173/379
-
8/3/2019 Fail Over Test
174/379
-
8/3/2019 Fail Over Test
175/379
-
8/3/2019 Fail Over Test
176/379
-
8/3/2019 Fail Over Test
177/379
-
8/3/2019 Fail Over Test
178/379
-
8/3/2019 Fail Over Test
179/379
-
8/3/2019 Fail Over Test
180/379
-
8/3/2019 Fail Over Test
181/379
-
8/3/2019 Fail Over Test
182/379
-
8/3/2019 Fail Over Test
183/379
-
8/3/2019 Fail Over Test
184/379
-
8/3/2019 Fail Over Test
185/379
-
8/3/2019 Fail Over Test
186/379
-
8/3/2019 Fail Over Test
187/379
-
8/3/2019 Fail Over Test
188/379
-
8/3/2019 Fail Over Test
189/379
-
8/3/2019 Fail Over Test
190/379
-
8/3/2019 Fail Over Test
191/379
-
8/3/2019 Fail Over Test
192/379
-
8/3/2019 Fail Over Test
193/379
-
8/3/2019 Fail Over Test
194/379
-
8/3/2019 Fail Over Test
195/379
-
8/3/2019 Fail Over Test
196/379
-
8/3/2019 Fail Over Test
197/379
-
8/3/2019 Fail Over Test
198/379
-
8/3/2019 Fail Over Test
199/379
-
8/3/2019 Fail Over Test
200/379
-
8/3/2019 Fail Over Test
201/379
-
8/3/2019 Fail Over Test
202/379
-
8/3/2019 Fail Over Test
203/379
-
8/3/2019 Fail Over Test
204/379
-
8/3/2019 Fail Over Test
205/379
-
8/3/2019 Fail Over Test
206/379
-
8/3/2019 Fail Over Test
207/379
-
8/3/2019 Fail Over Test
208/379
-
8/3/2019 Fail Over Test
209/379
-
8/3/2019 Fail Over Test
210/379
-
8/3/2019 Fail Over Test
211/379
-
8/3/2019 Fail Over Test
212/379
-
8/3/2019 Fail Over Test
213/379
-
8/3/2019 Fail Over Test
214/379
-
8/3/2019 Fail Over Test
215/379
-
8/3/2019 Fail Over Test
216/379
-
8/3/2019 Fail Over Test
217/379
-
8/3/2019 Fail Over Test
218/379
-
8/3/2019 Fail Over Test
219/379
-
8/3/2019 Fail Over Test
220/379
-
8/3/2019 Fail Over Test
221/379
-
8/3/2019 Fail Over Test
222/379
-
8/3/2019 Fail Over Test
223/379
-
8/3/2019 Fail Over Test
224/379
-
8/3/2019 Fail Over Test
225/379
-
8/3/2019 Fail Over Test
226/379
-
8/3/2019 Fail Over Test
227/379
-
8/3/2019 Fail Over Test
228/379
-
8/3/2019 Fail Over Test
229/379
-
8/3/2019 Fail Over Test
230/379
-
8/3/2019 Fail Over Test
231/379
-
8/3/2019 Fail Over Test
232/379
-
8/3/2019 Fail Over Test
233/379
-
8/3/2019 Fail Over Test
234/379
-
8/3/2019 Fail Over Test
235/379
-
8/3/2019 Fail Over Test
236/379
-
8/3/2019 Fail Over Test
237/379
-
8/3/2019 Fail Over Test
238/379
-
8/3/2019 Fail Over Test
239/379
-
8/3/2019 Fail Over Test
240/379
-
8/3/2019 Fail Over Test
241/379
-
8/3/2019 Fail Over Test
242/379
-
8/3/2019 Fail Over Test
243/379
-
8/3/2019 Fail Over Test
244/379
-
8/3/2019 Fail Over Test
245/379
-
8/3/2019 Fail Over Test
246/379
-
8/3/2019 Fail Over Test
247/379
-
8/3/2019 Fail Over Test
248/379
-
8/3/2019 Fail Over Test
249/379
-
8/3/2019 Fail Over Test
250/379
-
8/3/2019 Fail Over Test
251/379
-
8/3/2019 Fail Over Test
252/379
-
8/3/2019 Fail Over Test
253/379
-
8/3/2019 Fail Over Test
254/379
-
8/3/2019 Fail Over Test
255/379
-
8/3/2019 Fail Over Test
256/379
-
8/3/2019 Fail Over Test
257/379
-
8/3/2019 Fail Over Test
258/379
-
8/3/2019 Fail Over Test
259/379
-
8/3/2019 Fail Over Test
260/379
-
8/3/2019 Fail Over Test
261/379
-
8/3/2019 Fail Over Test
262/379
-
8/3/2019 Fail Over Test
263/379
-
8/3/2019 Fail Over Test
264/379
-
8/3/2019 Fail Over Test
265/379
-
8/3/2019 Fail Over Test
266/379
-
8/3/2019 Fail Over Test
267/379
-
8/3/2019 Fail Over Test
268/379
-
8/3/2019 Fail Over Test
269/379
-
8/3/2019 Fail Over Test
270/379
-
8/3/2019 Fail Over Test
271/379
-
8/3/2019 Fail Over Test
272/379
-
8/3/2019 Fail Over Test
273/379
-
8/3/2019 Fail Over Test
274/379
-
8/3/2019 Fail Over Test
275/379
-
8/3/2019 Fail Over Test
276/379
-
8/3/2019 Fail Over Test
277/379
-
8/3/2019 Fail Over Test
278/379
-
8/3/2019 Fail Over Test
279/379
-
8/3/2019 Fail Over Test
280/379
-
8/3/2019 Fail Over Test
281/379
-
8/3/2019 Fail Over Test
282/379
-
8/3/2019 Fail Over Test
283/379
-
8/3/2019 Fail Over Test
284/379
-
8/3/2019 Fail Over Test
285/379
-
8/3/2019 Fail Over Test
286/379
-
8/3/2019 Fail Over Test
287/379
-
8/3/2019 Fail Over Test
288/379
-
8/3/2019 Fail Over Test
289/379
-
8/3/2019 Fail Over Test
290/379
-
8/3/2019 Fail Over Test
291/379
-
8/3/2019 Fail Over Test
292/379
-
8/3/2019 Fail Over Test
293/379
-
8/3/2019 Fail Over Test
294/379
-
8/3/2019 Fail Over Test
295/379
-
8/3/2019 Fail Over Test
296/379
-
8/3/2019 Fail Over Test
297/379
-
8/3/2019 Fail Over Test
298/379
-
8/3/2019 Fail Over Test
299/379
-
8/3/2019 Fail Over Test
300/379
-
8/3/2019 Fail Over Test
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
-
8/3/2019 Fail Over Test
302/379
-
8/3/2019 Fail Over Test
303/379
-
8/3/2019 Fail Over Test
304/379
-
8/3/2019 Fail Over Test
305/379
-
8/3/2019 Fail Over Test
306/379
-
8/3/2019 Fail Over Test
307/379
-
8/3/2019 Fail Over Test
308/379
-
8/3/2019 Fail Over Test
309/379
-
8/3/2019 Fail Over Test
310/379
-
8/3/2019 Fail Over Test
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
-
8/3/2019 Fail Over Test
312/379
-
8/3/2019 Fail Over Test
313/379
-
8/3/2019 Fail Over Test
314/379
-
8/3/2019 Fail Over Test
315/379
-
8/3/2019 Fail Over Test
316/379
-
8/3/2019 Fail Over Test
317/379
-
8/3/2019 Fail Over Test
318/379
-
8/3/2019 Fail Over Test
319/379
-
8/3/2019 Fail Over Test
320/379
-
8/3/2019 Fail Over Test
321/379
-
8/3/2019 Fail Over Test
322/379
-
8/3/2019 Fail Over Test
323/379
-
8/3/2019 Fail Over Test
324/379
-
8/3/2019 Fail Over Test
325/379
-
8/3/2019 Fail Over Test
326/379
-
8/3/2019 Fail Over Test
327/379
-
8/3/2019 Fail Over Test
328/379
-
8/3/2019 Fail Over Test
329/379
-
8/3/2019 Fail Over Test
330/379
-
8/3/2019 Fail Over Test
331/379
-
8/3/2019 Fail Over Test
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
-
8/3/2019 Fail Over Test
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
-
8/3/2019 Fail Over Test
334/379
-
8/3/2019 Fail Over Test
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
-
8/3/2019 Fail Over Test
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
-
8/3/2019 Fail Over Test
337/379
Comment Telecom
Bridge
solving.
-
8/3/2019 Fail Over Test
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.
-
8/3/2019 Fail Over Test
339/379
-
8/3/2019 Fail Over Test
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)
-
8/3/2019 Fail Over Test
341/379
-
8/3/2019 Fail Over Test
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?
-
8/3/2019 Fail Over Test
343/379
Guidelines
Description1. Perform the sanity checks
Post
If some detail is missing or not all re
validation & you w
Post
-
8/3/2019 Fail Over Test
344/379
-
8/3/2019 Fail Over Test
345/379
-
8/3/2019 Fail Over Test
346/379
-
8/3/2019 Fail Over Test
347/379
-
8/3/2019 Fail Over Test
348/379
-
8/3/2019 Fail Over Test
349/379
-
8/3/2019 Fail Over Test
350/379
-
8/3/2019 Fail Over Test
351/379
-
8/3/2019 Fail Over Test
352/379
-
8/3/2019 Fail Over Test
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
-
8/3/2019 Fail Over Test
354/379
-
8/3/2019 Fail Over Test
355/379
-
8/3/2019 Fail Over Test
356/379
-
8/3/2019 Fail Over Test
357/379
-
8/3/2019 Fail Over Test
358/379
-
8/3/2019 Fail Over Test
359/379
-
8/3/2019 Fail Over Test
360/379
-
8/3/2019 Fail Over Test
361/379
-
8/3/2019 Fail Over Test
362/379
-
8/3/2019 Fail Over Test
363/379
-
8/3/2019 Fail Over Test
364/379
-
8/3/2019 Fail Over Test
365/379
-
8/3/2019 Fail Over Test
366/379
-
8/3/2019 Fail Over Test
367/379
-
8/3/2019 Fail Over Test
368/379
-
8/3/2019 Fail Over Test
369/379
-
8/3/2019 Fail Over Test
370/379
-
8/3/2019 Fail Over Test
371/379
-
8/3/2019 Fail Over Test
372/379
-
8/3/2019 Fail Over Test
373/379
-
8/3/2019 Fail Over Test
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
-
8/3/2019 Fail Over Test
375/379
Date Time Owner
Post Impl
Description
-
8/3/2019 Fail Over Test
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
Summary 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
-
8/3/2019 Fail Over Test
377/379
Comms
To
ementation Stage
Summary of Communications
-
8/3/2019 Fail Over Test
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
-
8/3/2019 Fail Over Test
379/379
V1.8 Dave Ray
V1.9
Kay
Thomas
Version
Number
Author Approver(s)