Implementation c100229805

1. # AGREED INFRASTRUCTURE IT CHANGE MODEL/TEMPLATE ###
## TEMPLATE NAME: GENERIC IMPLEMENTATION AND BACK-OUT TEMPLATE
## OWNER: TERENCE DONNELLY
## Reviewed Date: 08/11/2017
This is an agreed IT Change Management Template and has been reviewed and
sanctioned by the IT Change Management team for use to improve the efficiencies
of the HPSM system. The questions and answers to them are part of this Change
model and should not require amending
Please enter the latest date and time you require this change to be fully
approved by: 14 november 2017
THIS IS THE IMPLEMENTATION AND BACK-OUT TEMPLATE FOR ALL NORMAL CHANGES
14/11/2017:
Implementation and Scripting
‘Scripting’ refers to any method of packaging together or automating a series of
actions, including such actions as may be initiated from a control panel. Where
such control panel interaction requires granular selection of particular values,
this is ‘manual’ action that should be logged as such.
Q1: Is scripting used in the implementation of this change?
A1: Yes
If YES to A1, answer Q2 & Q3. If NO, go to Q4.
Q2: What testing has been done to ensure the script will provide the required
outcome?
A2: These are standard weblogic start-stop scripts which have been tested many
times in test and production servers
Q3: Please confirm that all variable parameters in the script, such as Queue
Names, Server Ids, DNS values, Library names etc. have been independently
checked and confirmed to be relevant to the target production environment?
A3:Yes, these have been checked
Q4: Is any part of the implementation plan of this change carried out by user
manually entering commands?
A4:Yes

2. If YES to A4, answer Q5 & Q6. If NO, go to END.
Q5: Please provide a summary of manual commands but ensure detail is included in
implementation plan?
A5:Standard Linux commands given below
ls
mv
cp
pwd
cd
vi
rm -rf
Q6: If Manual commands used please describe mitigation to prevent human error?
A6:These commands have been tested on test environment. Also care is taken at
the time of deployment before running any command.
END
If you have answered NO to both Q1 and Q4, this is incompatible. Please reassess
and re-answer all the questions.
IMPLEMENTATION TASKS
********************************************************************************
NOTE: If you have identified that configuration items are being taken
down/rebooted and have NOT used the alarm suppression task, please confirm how
alerting will be suppressed or please confirm if suppression is not required
here:
NOTE: It is the responsibility of the change implementers to advise the CSOC if
the change is likely to overrun the planned change window.
NOTE: It is the responsibility of the change implementers to advise the CSOC if
the change is likely to fail and cause a P1 or P2 fault.
NOTE: In the case of multi-night changes, it is the responsibility of the change
implementers to confirm that the change is in the deployment phase and not
locked. If the change is not in the deployment phase or is locked then do not
proceed with any deployment activity.

3. *******************************************************************************
No 1 Starts at 14/11/2017 22:00
Assignment Group/Implementer : SMARSPLUS will carry out task
CHECK PHASE OF CHANGE TO MAKE SURE THE CHANGE IS IN THE DEPLOYMENT PHASE. IF NOT
IN THE DEPLOYMENT PHASE OR IF THE CHANGE IS LOCKED, DO NOT PROCEED WITH THE
CHANGE
No 1 Ends at 14/11/2017 22:05
No 2 Starts at 14/11/2017 22:06
Assignment Group/Implementer : SMARSPLUS will carry out task : Pre-Deployment
Testing
1. Check if all servers are in Running state
2.Check all the services are in Running state
No 2 Ends at 14/11/2017 22:30
Derby Sanity 14_3S.xlsx
No 3 Starts at 14/11/2017 22:31
Assignment Group/Implementer : SMARSPLUS will carry out task :
Host Details-
IP Address- 10.59.202.22
IP Address- 10.36.54.10
IP Address- 10.36.33.17
IP Address- 10.38.79.17
Step 1: Login to smarts server
Step 2: Goto path /apps/MonitorIT/SAM/smarts/local/rules/icoi-syslog/
Step 3 : take a backup of cisco_hook_syslog.asl
cp cisco_hook_syslog.asl cisco_hook_syslog.asl_withoutBCO

4. Step 4: Restart the service with below command:
sm_service stop P-SMP1-NT-SA-01
sm_service show P-SMP1-NT-SA-01
sm_service start P-SMP1-NT-SA-01
No 3 Ends at 14/11/2017 23:50
No 4 Starts at 14/11/2017 23:51
Assignment Group/Implementer : SMARSPLUS will carry out task : Post Deployment
Testing
1. Check if server are in Running state.
2- Check all the services are in Running state.
#brcontrol
#sm_service show
No 4 Ends at 15/11/2017 03:30.
No 5 Starts at 15/11/2017 03:35
Assignment Group/Implementer : SMARSPLUS GROUP will carry out task : Decision
for Rollback
No 5 Ends at 15/11/2017 04:55