reply to xdxml12
Re: Network Maintenance Procedures As cramer notes, depends what "network maintenace procedure" refers to, and what kind of "template" you're looking for.
Are you looking for a Standard Operating Procedure, or are you looking more for a "best practices" kind of thing?
Speaking from personal experience, here's my 00000010bits :
- determine the hour(s) that changes / maintenence can occur without negatively impacting users / business.
- determine the kind(s) of maintenence that is occuring -- power, hardware, break/fix, project-related, IMAC, etc.
- draft up guideline(s) when each can occur, and which group(s) need to be involved in reviewing the change
- make a point of setting up regular change meetings to discuss upcoming changes with the interested parties --
can be facilities, business unit(s), users / managers, other IT depts, etc. The whole point is making sure everyone
is aware of WHAT is going on, WHAT will be impacted, and for how long.
- keep a papertrail, paper or otherwise, of change approvals for later review
- DOCUMENT, DOCUMENT, DOCUMENT! I can't stress this enough!
In terms of SOPs for maintenence, your imagination's the limit. In general, any change / maintenence I do
breaks down into the following steps :
a) did I notify someone I am starting the change?
b) did I gather my prechange so that I know what the environment looks like prior to starting, and in case I have to
back out my change I can put it back the way it ways?
c) execute and validate the change -- did it accomplish what I needed to do, and did I only affect what I needed to touch?
d) did I gather my postchange and verify the above?
e) did I notify someone I have completed the change, and whether it was successful or not?