CI in Maintenance when opening a change

[George18]

Hi,

OOB when opening a change for a CI, that CI will be put in maintenance.

Maintenance = no incidents or tasks will be created during that period.

I would like to know in which phase during the change does the CI go into maintenance and in which phase it comes out of maintenance?

Thank you

[Dr Atul G- LNG]

Hi @George18 

SN provided 2 modules here

1. Maintenance Schedule --> Means during this period a change can be deployed.

2. Blackout Schedule --> Means no change allowed in this period.

My video will help you to understand these.

https://youtu.be/XBOuhFtv3-M

[Bjarne Nielsen]

It is not OOTB to put a CI in Maintenance Mode during a Change Request. However if you use Event Management, there is a Maintenance Rule defined, that will put the CI i Mantenance Mode, if it is in an active Change Window.

This means that the logic of "when" is defined by the start and end date of the Change Window - not the phase of the Change Request.

[George18]

Hi Bjarne,

thank you for your response.

Yes, in fact we are using the Event Management module.

Is it the end date of when the change was scheduled to be finished or when the end date of when the change got completed.

e.g: Change scheduled today from 9am to 2pm

Change actually started at 9:30am and was closed at 10:00am.

Will the CI which was affected by in maintenance from 9am-2pm or from 9:30-10am?

Thank you

[Bjarne Nielsen]

Hi George

The CI will actually not change the operational state to "Maintenance", but instead create a record in the table em_impact_maint_ci table. This is then used to decide it alerts should be created, even for CI's not in operational state "Maintenance".
You can play around with this background script in DEV to see if the ci's are counted as being in maintenance window right now:

var impactManager = new SNC.ImpactManager();
var cis = impactManager.getCisInActiveChangeWindow();
gs.log(cis);