Specifications

© IBM Copyright, 2012 Version: January 26, 2012
www.ibm.com/support/techdocs 33
Summary of Best Practices for Storage Area Networks
documentation templates is beyond the scope of this white paper. Certainly, the
example “procedure” for choosing an MDisk Group is inadequate for most complex SAN
environments.
The easiest way to develop a Standard Operating Procedure is to integrate it with the
ensuing checklist to implement the operation. The procedural notes that assist the
Storage Administrator in developing the ticket are in italics. Those notes would
obviously not be part of the ticket template, just the SOP document.
The fields that will change for each ticket are delimited by __double underscores__.
Sample Change Record
***** BEGIN RECORD*****
Request: __ABC456__
Purpose: Add new server __XYZ123__ to the SAN and allocate __200GB__ of
space.
Date of Implementation: __04/01/2007__
Implementing Storage Administrator: __ SAN admin’s name __
Server Administrator: __ Server admin’s name __
Impact: None. This is a non-disruptive change.
Risk: Low.
Time estimate: __30 minutes__
Backout Plan: Reverse changes
Implementation Checklist:
1. ___ Verify (via phone or e-mail) that the administrator has
installed all code levels listed on the website
http://www.thecompany.com/storage_code.html
2. ___ Verify that the cabling change request, __CAB927__ has been
completed.
3. ___ For each HBA in the server, update the switch configuration
spreadsheet with the new server.
To decide which ioGroup to Use: These should roughly be evenly
distributed. Consult the storage inventory, which contains a
running total of the number of servers assigned to each I/O group.
To select which Node Ports to Use: If the last digit of the first
WWPN for the host is odd, use ports 1 and 4; if even, 2 and 3.
HBA A: