Specifications

www.ibm.com/support/techdocs 32

Summary of Best Practices for Storage Area Networks

In addition, a completed record should contain a complete list detailing how the changes

were made. This can be as simple as copying a checklist out of the Standard Operating

Procedures, checking off each step as it is completed, and pasting the completed list

into the record. The total information on implementation should allow the change to be

backed out later if needed.

For every common change, there should be a documented standard operating

procedure (SOP) implementing the change. This procedure should contain sufficient

detail that any administrator familiar with the systems and devices involved could make

the change, and end up with a functionally equivalent configuration. These procedures

enable the rapid training of new personnel, reduce errors in configuration changes,

increase change consistency, and make documentation simpler and more accurate.

This procedure can be integrated in with the checklist templates that will appear in the

change ticket.

The SOP should never incorporate a detailed “cookbook” method. Optimal SOPs do

not have to be extremely detailed step-by-step instructions written so any computer

literate person can follow them. Instead, they should concentrate on the things unique

to the SAN environment. For instance, the SOP for storage allocation (either for a new

or existing server) need not include instructions on which buttons in the GUI to push or

step-by-step listing of specific commands. Rather, the SOP should include information

on how to decide on which storage system to be used and additional information to fulfill

the request. The primary assumption of the SOP is the administrator is expected to

know the basic steps for allocation (create a volume, define a host definition, map the

volume to the host.

If the standard operating procedures are well-developed, and change requests are well-

documented, an effective change management system will eliminate the need for

multiple approval levels for common requests and thereby allow for better time

utilization of administrators for unique requests.

To bring it all together, the following is an example of a SOP and change record. This

example is for the addition of a new server to the switch configuration and allocating the

new server with some SVC-based storage. It assumes that a previous request

(following its own procedures) for physically cabling the server has already been

completed.

Author’s Note: This example is provided with the sort of detail that is required. It has

not been given a “test drive”, and is probably missing vital information for your business

purposes. Actually developing a complete set of change procedures and