Hosts SAN aliases and zones In today’s environment, administrators deal with large networks, the internet, and Cloud  Computing. Use good server naming conventions so that they can quickly identify a server  and determine the following information: Changing a server’s name in IBM FlashSystem 9 100 is as simple as changing any other IBM  FlashSystem 9100 object name. However, changing the name on the operating system of a  server might have implications for application configuration and require a server reboot.  Therefore, you might want to prepare a detailed plan if you decide to rename several servers  in your network. The following example is for server name conventions for  LLAATRFFNN : SAN aliases often need to reflect only the device and port that is associated to it. Including  information about where one particular device port is physically attached on the SAN might  lead to inconsistencies if you make a change or perform maintenance and then forget to  update the alias. Create one alias for each device port WWPN in your SAN, and use these  aliases in your zoning configuration. Consider the following examples: Be mindful of the IBM FlashSystem 9100 port aliases. There are mappings between the  last digits of the port WWPN and the node FC port If your SAN does not support aliases, for example, in heterogeneous fabrics with switches in  some interoperations modes, use WWPNs in your zones. However, remember to update  every zone that uses a WWPN if you ever change it. GLYPH<SM590000> Where it is (to know how to access it). GLYPH<SM590000> What kind it is (to determine the vendor and support group in charge). GLYPH<SM590000> What it does (to engage the proper application support and notify its owner). GLYPH<SM590000> Its importance (to determine the severity if problems occur). GLYPH<SM590000> LL is the location, which might designate a city, data center, building floor, or room. GLYPH<SM590000> AA is a major application, for example, billing, ERP, and Data Warehouse. GLYPH<SM590000> T is the type, for example, UNIX, Windows, and VMware. GLYPH<SM590000> R is the role, for example, Production, Test, Q&A, and Development. GLYPH<SM590000> FF is the function, for example, DB server, application server, web server, and file server. GLYPH<SM590000> NN is numeric. GLYPH<SM590000> AIX_NYBIXTDB02_FC2: Interface fcs2 of AIX server NYBIXTDB02 GLYPH<SM590000> LIN_POKBIXAP01_FC1: Interface fcs1 of Linux Server POKBIXAP01 GLYPH<SM590000> WIN_EXCHSRV01_HBA1: Interface HBA1 of physical Windows server EXCHSRV01 GLYPH<SM590000> ESX_NYVMCLUSTER01_VMHBA2: Interface vmhba2 of ESX server NYVMCLUSTER01 GLYPH<SM590000> IBM_NYFS9100_N1_P1_HOST: Port 1 of Node 1 from FS9100 Cluster NYFS9100 dedicated  for hosts GLYPH<SM590000> IBM_NYFS9100_N1_P5_INTRACLUSTER: Port 5 of Node 1 from FS9100 Cluster NYFS9100  dedicated to intracluster traffic GLYPH<SM590000> IBM_NYFS9100_N1_P7_REPLICATION: Port 7 of Node 1 from FS9100 Cluster NYFS9100  dedicated to replication GLYPH<SM590000> IBM_D88870_75XY131_I0301: DS8870 serial number75XY131, port I0301 GLYPH<SM590000> IBM_TL01_TD06: Tape library 01, tape drive 06 GLYPH<SM590000> EMC_VNX7500_01_SPAP2: EMC VNX7500 hostname VNX7500_01, SP A, port 2 Chapter 9. Maintenance  323