Basic rules for naming devices in the SAN

The Storage Networking Industry Association (SNIA) defines the storage area network (SAN) as a network whose primary purpose is the transfer of data between computer systems and storage elements. A SAN is a specialized, high-speed network that attaches servers and storage devices.

Use of descriptive naming conventions is one of the most important factors in a successful SAN. Good naming standards will improve problem diagnostics, reduce human error, allow for the creation of detailed documentation and reduce the dependency on individuals.

Port names should be based on the “Rule of one initiator” that is the name of the zone carries information about the initiator and the functional purpose of the zone.

For example: SAPRDDB1_s2p0_DB
where:

SAPRDDB1_s2p0 – alias initiator

DB – conditional functional areas

Functionality can be of the following types:

DB – area for database storage
FS – zone for the file system, such as boot from SAN
Backup – backup area

Mgmt – management zone
ED – zone for extended distance

There may also be other types of zones, but always the name of the zone should be clear of its functionality.

Points to keep in mind while configuring zones:

  • Alias name should be mentioned in such a way that it reflects the path of physical connection (HBA port number) and the functional purpose of the device (the name of the device, application, or operating system). Zones can be created without the usage of Alias names but is strongly recommended to be used and that too with intuitive names.

  • Zone names must be mentioned from the Alias names of devices in zone. In most configurations, it is optimal zoning based on WWPN. Usage names like Zone_1 or qwerty are not permitted.

  • ZoneSet names must be mentioned from the names of zones in set and ZoneSet functionality. There can be several ZoneSets configured but only one configuration of the zones can be active at any given time.

  • Activation of ZoneSet requires an updated copy of the active configuration on all switches in the fabric. Distribution of configuration leads to temporary I/O delays. In small fabrics, it is invisible to users. However, in fabrics with a very large number of devices and switches, activating of ZoneSet should be done during minimal activity of SAN users.

The optimal configuration is the zoning in which each zone has as a member of only one HBA (FCP-initiator) and the port of the disk array or tape Library. This is called the “Rule of one initiator”. In addition, it should not be combined into one zone servers running various operating systems as it can lead to data loss.

Rules for creating titles device ports (Alias names)

Entry level and midrange servers

Use the DNS host name, and then specify the number of the slot where the HBA is installed and the port number. For numbering adapters and ports, the rule from left to right and from top to bottom.

For example: SAPRDDB1_s2p0
where
:
SAPRDDB1 – DNS host name

s2 – the slot number
p0 – the HBA port adapter

High-end servers

Unlike the entry level servers and midrange, high-end servers have IO chassis and hence they should also be indicated in the title:

For example: SAPRDDB1_i0s4p0
where:

SAPRDDB1 – DNS host name

i0 – the IO chassis number
s4 – the slot number

p0 – the HBA port adapter

Entry level and midrange disk arrays

Use the name/model of the array, then the last four characters of the WWN. If several arrays types are present, then the controller number (A or B) and the port number of the controller will also need to be mentioned.

For example: AMS2300_CAE0_A0
where:

AMS2300 – model of the array

CAE0 – the last four characters of WWN
A – the controller number

0 – the port number of controller

In the case of disk arrays such as HP EVA, you can specify only the name of the array which is displayed on the front panel (can be set in the HP Command View EVA)

For example: EVA4400DB_B4
where:

EVA4400DB – the name of the array

B – the controller number
4 – the port number of the controller

High-end disk arrays

Use the name/model of the array, then the array I/O port number.

For example: USP_CL5C
where:

USP – the model of the array

CL5 – the controller number
C – the port number of the controller

Entry level and midrange tape libraries

Use the DNS name of the library and the number of tape drive. For example:

For example: MSL4048_td1
where:

MSL4048 – the library name

td1 – tape drive

High-end tape libraries

Use the DNS name of the library and the number of tape drive, and in some models robot (changer) may be present and should use a separate name in such cases.

For example: ESL_E_td1
where:

ESL_E – library name

td1 – tape drive

For example: ESL_E_chgr
where:

ESL_E – library name

chgr – robot (changer)

 

Written by actsupp-r0cks