Search
Topics
  Create an account Home  ·  Topics  ·  Downloads  ·  Your Account  ·  Submit News  ·  Top 10  
Modules
· Home
· Content
· FAQ
· Feedback
· Forums
· Search
· Statistics
· Surveys
· Top
· Topics
· Web Links
· Your_Account

Current Membership

Latest: SHighett
New Today: 15
New Yesterday: 55
Overall: 148137

People Online:
Visitors: 54
Members: 1
Total: 55 .

Languages
Select Interface Language:


Major ITIL Portals
For general information and resources, ITIL and ITSM World is the most well known for both ITIL and ITIL Books. A shorter snapshot approach can be found at ITIL Zone

Related Resources
Service related resources
Service Level Agreement
Outsourcing

Note: ITIL is a registered trademark of OGC. This portal is totally independent and is in no way related to them. See our Feedback Page for more information.


The Itil Community Forum: Forums

ITIL :: View topic - Server Reboot - An RFC?
 Forum FAQForum FAQ   SearchSearch   UsergroupsUsergroups   ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

Server Reboot - An RFC?
Goto page Previous  1, 2
 
Post new topic   Reply to topic    ITIL Forum Index -> The ITIL Service Desk
View previous topic :: View next topic  
Author Message
UKVIKING
Senior Itiler


Joined: Sep 16, 2006
Posts: 3318
Location: London, UK

PostPosted: Tue Nov 20, 2007 10:01 pm    Post subject: Reply with quote

Ed,

I do see your point about scenario 1. And to be fair I agree with your not liking the answer to the scenarios

The change process like you said should not be a hinderance.

You also have to be practical when you are a change manager

The main reason the RFC was not created was that there was no change process at the time for standard changes like this piece of work. Instead, historically, they used the incident ticket.

All changes had to be approved. The work did not meet the requirement for an emergency change and the only other alternate was the full process which included a 3 day lead time.


The Emergency change request process was being highly abused 30-40%

So I either allowed the change as an Emergency change request or
allowed the standard change (non impacting of course) through the incident process - as there was not a change one at that particular time.
_________________
John Hardesty
ITSM Manager's Certificate (Red Badge)

Change Management is POWER & CONTROL. /....evil laughter
Back to top
View user's profile
scook2003
Newbie
Newbie


Joined: Oct 12, 2007
Posts: 14

PostPosted: Wed Dec 12, 2007 12:48 am    Post subject: Reply with quote

Guys your all talking about servers!


Remeber ITIL is about services. Does the server reboot affect/have an impact on any services? If yes then change management unless its not actually working anyway then I guess incident management would pass to problem management who would re-boot if it was the right thing to do? I would see no need for change management as the service is affected anyway. After this problem management would have a known error but not the root cause which would take further investiugation, if a change is required to fix the root cause then a RFC would be required, urgency dependent on business impact.


If the service is running then the reboot could be carried out in the maint window defined within the SLA therefore no breach in SLA (via change management).
Back to top
View user's profile
Ed
Senior Itiler


Joined: Feb 28, 2006
Posts: 411
Location: Coventry, England

PostPosted: Wed Dec 12, 2007 6:06 pm    Post subject: Reply with quote

Hi scook2003

If you read our posts you will see that both John & I are talking about rebooting servers that form part of a service.

To pick up on part of your post - If a server forms part of a service (whether up or down), it is part of the live environment - therefore it comes under Change Management. It does not matter what state it is in, until it is retired and replaced it is still part of that service. I personally would disembowel anyone that attempted a Change of any kind on one of my live servers, even if that Change is a Change of state, without an RFC in place.

Regards

Ed
Back to top
View user's profile
Mark-OLoughlin
Senior Itiler


Joined: Oct 12, 2007
Posts: 306
Location: Ireland

PostPosted: Wed Dec 12, 2007 7:18 pm    Post subject: Reply with quote

Hi,

"Remeber ITIL is about services". Correct and it also places big importance onthe CMDB which is made up of CI's - which are the very things that need to be rebooted.

Service may not be down but you still need to record the reboot - and use this as analysis to feed into problem management.Why are we continually getting the same problem?

Looking at the changes on this server we are having to reboot it twice a week. - and then the inestiagtion from Problem Management begins.
_________________
Mark O'Loughlin
ITSM / ITIL Consultant
Back to top
View user's profile
scook2003
Newbie
Newbie


Joined: Oct 12, 2007
Posts: 14

PostPosted: Thu Dec 13, 2007 10:07 pm    Post subject: Reply with quote

I see your point, I suppose it would go to change control (whatever) who do look after the final stages of error resolution including impact assesment.

Any high availability business critical servers should have redundancy (i.e. mirroring) so I guess the "high urgency" situation shouldnt occur and therefore standard change control should be ok.

If it has to go through emergency change control then the business should be informed and the SLA of that service discussed with the customer (and availabity management) to include higher availability.
Back to top
View user's profile
Display posts from previous:   
Post new topic   Reply to topic    ITIL Forum Index -> The ITIL Service Desk All times are GMT + 10 Hours
Goto page Previous  1, 2
Page 2 of 2

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum

Powered by phpBB 2.0.8 © 2001 phpBB Group
phpBB port v2.1 based on Tom Nitzschner's phpbb2.0.6 upgraded to phpBB 2.0.4 standalone was developed and tested by:
ArtificialIntel, ChatServ, mikem,
sixonetonoffun and Paul Laudanski (aka Zhen-Xjell).

Version 2.1 by Nuke Cops 2003 http://www.nukecops.com

Forums ©

 

Logos/trademarks property of respective owner. Comments property of poster. Rest 2004 Itil Community for Service Management & Foundation Certification. SV
Site source copyright (c)2003, and is Free Software under the GNU / GPL licence. All Rights Are Reserved.