Automating Outage Scheduling and Master Checks

c602 scheduling around outages n.w
1 / 15
Embed
Share

Enhance your outage management with automated scheduling around outages and streamline master checks. Execute failover processes efficiently, run post-failover checks, and close failover changes seamlessly. Ensure system reliability with detailed master proofs and workstation updates.

  • Automation
  • Outage Management
  • Master Checks
  • Failover
  • Scheduling

Uploaded on | 0 Views


Download Presentation

Please find below an Image/Link to download the presentation.

The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author. If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.

You are allowed to download the files provided on this website for personal or commercial use, subject to the condition that they are used lawfully. All files are the property of their respective owners.

The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author.

E N D

Presentation Transcript


  1. C602 Scheduling around outages

  2. Scheduling around outages Outage preparation Master FTA Repeated application scheduled outage

  3. Master Schedule the patching on masters. Roll in failover schedule and final schedule from respective MDM and BMDM. API to create pre-authorized failover change. Run the failover schedule. Post failover checks. API to close failover change. End End automation. (Hands off)

  4. Master Schedule the patching on masters. Roll in failover schedule and final schedule from respective MDM and BMDM. API to create pre-authorized failover change. Run the failover schedule. Post failover checks. API to close failover change. End End automation. (Hands off)

  5. Master

  6. Master

  7. Master Check List: 1. Master check = PASS 2. Unlink check = FAIL 3. Boker status check = PASS 4. WAS status check = PASS 5. Event status check = PASS 7. Master (KSAAN006) Limit Value = 20 8. Master (KSAAN006) fence Value = 0 9. Backup master (OSAAN002) Limit Value = 20 10. Backup master (OSAAN002) fence Value = 70 11. Domain manager 1 (KSAAN007_54111) Limit Value = 10 12. Domain manager 1 (KSAAN007_54111) fence Value = 0

  8. Master 23. Backup domain manager 1 (OSAAN004_54111) Limit Value = 10 24. Backup domain manager 1 (OSAAN004_54111) fence Value = 70 35. Final jobstream check = PASS 36. FINALPOSTREPORTS jobstream check = PASS 37. Mailsendername check = PASS 38. SMTPservername check = PASS

  9. Master Proofs: 1. Master check KSAAN006 1394 *UNIX MASTER 20 0 12/18/18 08:59 I J MDEA MASTERDM 2. Unlink check List of unlinked workstation :- CL-NYNY-DPX002 1394 UNIX FTA 10 0 12/18/18 09:26 I J MD PD_FLOR1 SA-NYNY-NBUM01 1394 UNIX FTA 10 0 12/18/18 09:28 I J MD PD_FLOR1 Mail server for SA-NYNY-NBUM01 ==> L Mail server for CL-NYNY-DPX002 ==> L

  10. Master *************************************************** Last Workstation update logs for Server SA-NYNY-NBUM01 *************************************************** CONMAN |20180809|174615|20180809|134615| PLWKSTN |MODIFY | | iwa94pd| | SA-NYNY-NBUM01|limit cpu=@!SA-NYNY-NBUM01@ 10 noask ******************************************* Workstation logs for Server SA-NYNY-NBUM01 ******************************************* 09:43:34 18.12.2018|BATCHMAN:Workstation SA-NYNY-NBUM01 State is being changed: LINKED=TCP 09:44:52 18.12.2018|MAILMAN:AWSBCV087I Added SA-NYNY-NBUM01 to workstation table, node "S", server " ", link type "1", flags "16400". 09:59:58 18.12.2018|BATCHMAN:Workstation SA-NYNY-NBUM01 State is being changed: UNSETTING: LINKED=TCP

  11. Master 3. Broker status check: OSAAN002_DWB 1394 OTHR BROKER 10 0 12/18/18 09:01 LTI JW MASTERDM 4. WAS status check: Ps ef|grep <server> output 5. Event status check: KSAAN006 1394 *UNIX MASTER 20 0 12/18/18 08:59 I J MDEA MASTERDM

  12. Master 6. Database connection check: Optman ls output 7. MDM / BMDM / DM BDM Limit and fence values check. 8. Final and finalpostreports schedule load check.

  13. FTA API to pull SNOW information Job to compare the server in TWS (Housekeeping job to update active node and hostname) Job to submit Limit 0 and Limit 10 job 15 minutes before outage Auto shut down and auto start in FTA Limit 0 alert suppression Downtime manager API Job to monitor downtime manager expiration Limit 10 job to set back the limit

  14. Application outage Schedules to make changes Jobs to cancel application jobs which falls in outage window Jobs to change start time before outage Jobs to change start time after outage

  15. Whats your take? Your feedback helps to set the course for future ASAP UNIVERSITY training initiatives. How do you rate the value of this Session Code ____? Let us know. Complete the evaluation. How will you use what you learned? Share your insights with users between sessions on the ASAP User Forum at asapuniversity.org. Remember to stay connected to ASAP. Tweet! @ASAPUniversity

Related


More Related Content