ibm.com/redbooksImplementing an Open IBM SAN Featuring the INRANGE PortfolioJon TateBrian CartwrightSven EichelbaumThomas JahnDiscover the latest addi
viii Implementing an Open IBM SAN5.4 Using SLIC Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3335.4.1 Dr
86 Implementing an Open IBM SANViewing the Communications panelUsing the Communications button, we get the Communications panel, as shown in Figure 2
Chapter 2. IBM TotalStorage Enterprise Storage Server configuration 87Generating a new PE passwordResetting the PE password means actually that you
88 Implementing an Open IBM SANViewing the Licensed Internal Code panelUsing the Licensed Internal Code button we get the “Licensed Internal Code” pa
Chapter 2. IBM TotalStorage Enterprise Storage Server configuration 892.1.3 Configuring the ESSFollowing, we introduce the panels that serve as ent
90 Implementing an Open IBM SANUsing the Copy Services linkUsing the Copy Services button we link to the copy services server.We have to login to gai
Chapter 2. IBM TotalStorage Enterprise Storage Server configuration 91Figure 2-16 ESS Web Copy Services introduction panelUsing the Tools help pag
92 Implementing an Open IBM SANFigure 2-17 Tools help page, Web Copy Services trouble shooting
Chapter 2. IBM TotalStorage Enterprise Storage Server configuration 93Figure 2-18 Tools help page, Web Copy Services trouble shooting, continued2.
94 Implementing an Open IBM SANFigure 2-19 User Administration panelIn our case there are no users configured, other than the default user that we
Chapter 2. IBM TotalStorage Enterprise Storage Server configuration 95Figure 2-20 Modify Users panelThe access levels are:View Viewing the status
© Copyright IBM Corp. 2001 ixPreface“Do everything that is necessary and absolutely nothing that is not.”In this IBM Redbook, we have tried to consoli
96 Implementing an Open IBM SAN2.2 Starting the Open Systems Storage ConfigurationIn the topics that follow, we will guide users through the storage
Chapter 2. IBM TotalStorage Enterprise Storage Server configuration 97In this panel, we get the logical view and the status of the installed and con
98 Implementing an Open IBM SANUsing the ESS interfaces rowBelow the host interface row, we see the row with icons for the ESS installed interface ad
Chapter 2. IBM TotalStorage Enterprise Storage Server configuration 99Figure 2-26 ESS SCSI adapter with two portsFigure 2-27 ESS FC adapter with
100 Implementing an Open IBM SANFigure 2-28 FC host port selectedIn contrast to this, the host SCSI ports have an affinity to the ESS SCSI ports, w
Chapter 2. IBM TotalStorage Enterprise Storage Server configuration 101Figure 2-30 SSA device adapters without any disk group configuredAgain, we
102 Implementing an Open IBM SANFigure 2-31 Disk groups, view all storage modeTo show the state of the disk groups, which contain ESS logical volum
Chapter 2. IBM TotalStorage Enterprise Storage Server configuration 103There are different colors to indicate the state of the disk groups. At the u
104 Implementing an Open IBM SANFigure 2-34 Tabular View, no ESS logical volumes configuredAs expected, the table that contains the detailed descri
Chapter 2. IBM TotalStorage Enterprise Storage Server configuration 105Figure 2-36 Open System Storage panel, no host FC ports definedThe configur
x Implementing an Open IBM SANthe design and implementation of IBM Storage Area Networks across a wide customer base. Brian’s expertise includes SAN
106 Implementing an Open IBM SANFigure 2-37 ESS configuration dependenciesConfiguring disk groups anddefining host FC ports to be ableto add ESS lo
Chapter 2. IBM TotalStorage Enterprise Storage Server configuration 107One step that is independent from the others, is the configuration of the ESS
108 Implementing an Open IBM SAN2.3.1 Performing the disk group configurationPressing the Configure Disk Groups button takes us to the Fixed Block S
Chapter 2. IBM TotalStorage Enterprise Storage Server configuration 109The unformatted size of the disk groups is 254.8 GB. This is equivalent to se
110 Implementing an Open IBM SANFigure 2-40 Disk groups defined for RAID 5Performing the configuration updateTo apply the changes made, we press th
Chapter 2. IBM TotalStorage Enterprise Storage Server configuration 111How time consuming this will be depends on how many disk groups are to be con
112 Implementing an Open IBM SANViewing changes on the Graphical View panelFrom here we can continue with our configuration. To see how the Storage A
Chapter 2. IBM TotalStorage Enterprise Storage Server configuration 113The rectangle representing the disk group is green to show that this is empty
114 Implementing an Open IBM SANDefining two more disk groups for RAID 5We will configure two more disk groups and so we therefore navigate back to t
Chapter 2. IBM TotalStorage Enterprise Storage Server configuration 115Viewing changes on the Graphical View panelDevice adapter pair number four an
Preface xiRichio AikawaJon KruegerEmulex CorporationDave BurchwellJack ConsoliRichard KurzbanMike NaylorINRANGE Technologies CorporationChris BurkeJ
116 Implementing an Open IBM SANFigure 2-48 Status — Graphical View, four disk groups in the process of formattingThis discussion was just intended
Chapter 2. IBM TotalStorage Enterprise Storage Server configuration 1172.4.1 Creating host FC port definitionsFrom the Open System Storage panel, w
118 Implementing an Open IBM SANCreating two host FC port definitionsIn the Host Attributes entry fields, we identify the host FC port that will acce
Chapter 2. IBM TotalStorage Enterprise Storage Server configuration 119Figure 2-52 Host Attributes frame, host interface type selectionThe IP Addr
120 Implementing an Open IBM SANFigure 2-53 Host Systems List, host FC ports definedThis host FC port can belong to the same system, or we can defi
Chapter 2. IBM TotalStorage Enterprise Storage Server configuration 121A window appears which indicates that the configuration update was successful
122 Implementing an Open IBM SANAs we select one of them, we see that there are no ESS logical volumes currently assigned to the host FC ports. Viewi
Chapter 2. IBM TotalStorage Enterprise Storage Server configuration 123Clicking on the host FC port icon also shows that the port would be able to a
124 Implementing an Open IBM SANFigure 2-60 FC port PC1_2 selected for modificationAs we show here, the Fibre-Channel Ports list indicates the curr
Chapter 2. IBM TotalStorage Enterprise Storage Server configuration 125We scroll to and select the adapter tree in bay 1 to limit the host FC port P
xii Implementing an Open IBM SANIBM trademarksThe following terms are trademarks of the International Business Machines Corporation in the United Sta
126 Implementing an Open IBM SANFigure 2-63 Selected host FC port, restricted to one ESS FC portIt shows us also that there are no ESS logical volu
Chapter 2. IBM TotalStorage Enterprise Storage Server configuration 127This takes us to the Add Volumes (1 of 2) panel, as shown in Figure 2-65.Figu
128 Implementing an Open IBM SANSelecting the disk groups for the volume placementBy clicking on a port, we can now see the storage that we can use t
Chapter 2. IBM TotalStorage Enterprise Storage Server configuration 1292.5.2 Adding ESS logical volumes — step twoPressing the Next button, we are
130 Implementing an Open IBM SANSelecting the storage typeTo create RAID 5 volumes, we have to click on the RAID-5 Array row shown in Figure 2-70.Fig
Chapter 2. IBM TotalStorage Enterprise Storage Server configuration 131Instead, we use a volume size of 16.1 GB, which allows us to place 26 of them
132 Implementing an Open IBM SANPlacing the volumes in selected disk groupsNow, as we have defined how many volumes and of what size we want to add,
Chapter 2. IBM TotalStorage Enterprise Storage Server configuration 133Figure 2-75 Add Volumes (2 of 2) panel, ready to perform the configuration
134 Implementing an Open IBM SANAs with every run of a configuration update, there is a progress window, as shown in Figure 2-77.Figure 2-77 Progre
Chapter 2. IBM TotalStorage Enterprise Storage Server configuration 135Viewing changes on the Graphical View panelTo see the updates we have made, w
© Copyright IBM Corp. 2001 1Chapter 1. Implementing Fibre Channel host adapter cardsIn this chapter we describe the steps involved in implementing Fib
136 Implementing an Open IBM SANFigure 2-80 Host FC port and ESS FC port selectedThe Information field now displays information relating to the con
Chapter 2. IBM TotalStorage Enterprise Storage Server configuration 137The items that have changed on the disk group information since our last visi
138 Implementing an Open IBM SANAgain, the Information frame changed the look to represent the general information of the disk group and is still not
Chapter 2. IBM TotalStorage Enterprise Storage Server configuration 139Figure 2-84 FC port PC1_1 with two assigned volumesNow when we select the h
140 Implementing an Open IBM SANViewing changes on the Graphical View panelBack on the Storage Allocation — Graphical View panel we see how the panel
Chapter 2. IBM TotalStorage Enterprise Storage Server configuration 141We select the host PC1_2, and we see that lines now appear connecting the hos
142 Implementing an Open IBM SANFigure 2-87 Displays of all four volume assignmentsWe see all the information about the location and the current as
Chapter 2. IBM TotalStorage Enterprise Storage Server configuration 143For example, we can share volumes between host FC ports. These ports can be i
144 Implementing an Open IBM SANThe Volume Assignments table provides a comprehensive overview of all configured volume associations. We can also sor
Chapter 2. IBM TotalStorage Enterprise Storage Server configuration 145The second case is if the assignments to be selected are adjacent. Of course
2 Implementing an Open IBM SAN1.1 Fibre ChannelFibre Channel transfers information between the sources and the users of the information. This inform
146 Implementing an Open IBM SANPerforming the configuration updateTo apply the changes, we press the Perform Configuration Update button. The progre
Chapter 2. IBM TotalStorage Enterprise Storage Server configuration 147If we press OK, we do not change back to the Open System Storage panel. Inste
148 Implementing an Open IBM SANFigure 2-95 PC1_1 and ESS FC port selectedIn fact there is no volume configured on the ESS which is not assigned to
Chapter 2. IBM TotalStorage Enterprise Storage Server configuration 149Figure 2-96 Disk group containing shared ESS logical volume(s) selectedThe
150 Implementing an Open IBM SANFigure 2-97 Tabular View, two volumes shared, two not sharedConverting volume assignments table in HTML formatTo vi
Chapter 2. IBM TotalStorage Enterprise Storage Server configuration 151Now the content of the table is displayed in HTML format, as shown in Figure
152 Implementing an Open IBM SANRemoving the assignments of one ESS logical volumeFirst as we did in, “Selecting ESS logical volume assignments for m
Chapter 2. IBM TotalStorage Enterprise Storage Server configuration 153Figure 2-103 Warning window two, volumes to be isolated from host FC portsW
154 Implementing an Open IBM SANFigure 2-106 Placeholder for unassigned ESS logical volume selectedViewing changes on the Open System Storage panel
Chapter 2. IBM TotalStorage Enterprise Storage Server configuration 155Viewing changes on the Graphical View panelNow we want to see the changes on
Chapter 1. Implementing Fibre Channel host adapter cards 31.1.2 Fibre Channel node-to-node distancesYou can order and have IBM install a maximum of
156 Implementing an Open IBM SANThe space of the disk groups that contains ESS logical volumes that are assigned to the selected host FC port show up
Chapter 2. IBM TotalStorage Enterprise Storage Server configuration 157Another way to find out about the state of the space in a disk group is to se
158 Implementing an Open IBM SANFigure 2-112 Tabular View, four volume assignments, three volumesHere we see that there is no longer any assignment
Chapter 2. IBM TotalStorage Enterprise Storage Server configuration 159As we already know, the selection of an entity in the Storage Allocation — Gr
160 Implementing an Open IBM SANSelecting the interface port to be configuredThe Configure Host Adapter Ports panel is shown in Figure 2-115.Figure 2
Chapter 2. IBM TotalStorage Enterprise Storage Server configuration 161Figure 2-116 Port selection drop down list, SCSI port selectedThere is no c
162 Implementing an Open IBM SANFigure 2-117 Configure Host Adapter Ports panel, FC port selectedThe port we used is in bay 1, adapter 3, and is po
Chapter 2. IBM TotalStorage Enterprise Storage Server configuration 163There are two Fibre Channel Access Modes to which the ESS can be configured:
164 Implementing an Open IBM SAN Adding new ESS logical volumes to the ESS, the new volumes go to the host FC port that is selected. Assigning ESS
Chapter 2. IBM TotalStorage Enterprise Storage Server configuration 165These actions are host dependent. With respect to the fabric components, if W
4 Implementing an Open IBM SAN1.1.3 LUN affinityFor Fibre Channel attachment, LUNs have an affinity to the host's Fibre Channel adapter through
166 Implementing an Open IBM SANThe Information frame on the Storage Allocation — Graphical View panel reflects the new WWPNs of the ESS we have used
Chapter 2. IBM TotalStorage Enterprise Storage Server configuration 1672.7.3 Configuring host FC ports for FC-SW and FC-ALNow, as we have selected
168 Implementing an Open IBM SANAs we have selected the topology for the selected ESS FC port, we see a small red line directly below the icon of the
Chapter 2. IBM TotalStorage Enterprise Storage Server configuration 169Figure 2-125 ESS FC port for Arbitrated Loop definedResetting changes made
170 Implementing an Open IBM SANPerforming the configuration updateClick on the Perform Configuration Update button. During the process of performing
Chapter 2. IBM TotalStorage Enterprise Storage Server configuration 171For port three in bay one, which is now configured for use with FC Point to P
172 Implementing an Open IBM SANFigure 2-131 Storage allocation now completedWe see that the host FC port PC1_2 is restricted to see the one volume
Chapter 2. IBM TotalStorage Enterprise Storage Server configuration 173IBM Enterprise Storage Server SCSI Command Reference, 2105 Models E10, E20, F
174 Implementing an Open IBM SAN
© Copyright IBM Corp. 2001 175Chapter 3. Implementing the INRANGE FC/9000 Fibre Channel DirectorThe IBM machine type 2042 model number 001, INRANGE FC
Chapter 1. Implementing Fibre Channel host adapter cards 5 Feature code 3023 — This is a short wave laser adapter that includes a 31-m (100-ft) (50
176 Implementing an Open IBM SAN3.1 Introduction to the INRANGE FC/9000 directorIn this chapter we introduce the INRANGE FC/9000 Director and cover
Chapter 3. Implementing the INRANGE FC/9000 Fibre Channel Director 1773.1.1 Product overviewThe FC/9000 Fibre Channel Director is INRANGE’s flagshi
178 Implementing an Open IBM SAN3.1.2 Currently supported zoning methodologiesZoning is one of the key functions provided by SAN switches or directo
Chapter 3. Implementing the INRANGE FC/9000 Fibre Channel Director 179Figure 3-2 shows an example of a director view with IN-VSN Manager.Figure 3-2
180 Implementing an Open IBM SANINRANGE does just that, by supporting these protocols: Open Systems: – Arbitrated Loop• Public loop• Private loop– F
Chapter 3. Implementing the INRANGE FC/9000 Fibre Channel Director 1813.1.6 Supported device attachmentCurrently these Storage products are support
182 Implementing an Open IBM SANIn Figure 3-3 we show our target ITSO environment.Figure 3-3 Initial INRANGE environmentFor management purposes we
Chapter 3. Implementing the INRANGE FC/9000 Fibre Channel Director 1833.2.3 Initial setup of INRANGE FC/9000 IP settingsThe INRANGE Director is del
184 Implementing an Open IBM SANLeaving all IP settings as a private networkFor using the IN-VSN software from this local private network, the suppli
Chapter 3. Implementing the INRANGE FC/9000 Fibre Channel Director 185After attaching our INRANGE setup to IBM’s corporate network, as shown in Figu
6 Implementing an Open IBM SANWhen you have eight paths in the path group, it minimizes the number of missed reconnections. Increasing the number of
186 Implementing an Open IBM SANReferring to Figure 3-6, we see that now only the Management PC can access the directors’s IP ports. Figure 3-6 INR
Chapter 3. Implementing the INRANGE FC/9000 Fibre Channel Director 1873.2.5 Installing the IN-VSN Enterprise Manager softwareThere are a number of
188 Implementing an Open IBM SANRunning the setup procedures of IN-VSN server and client Both the IN-VSN server and client require the following two
Chapter 3. Implementing the INRANGE FC/9000 Fibre Channel Director 189The setup program then checks whether you have the appropriate level of Java i
190 Implementing an Open IBM SANThen you must decide which part of the IN-VSN software should be installed, server and/or client, as shown in Figure
Chapter 3. Implementing the INRANGE FC/9000 Fibre Channel Director 191Before actually starting the installation a list of all installation parts is
192 Implementing an Open IBM SANLeave all components selected in the odbc installation window, as shown in Figure 3-11. Figure 3-11 Running obdc3.2
Chapter 3. Implementing the INRANGE FC/9000 Fibre Channel Director 193We installed the IN-VSN client software on two different workstations in our t
194 Implementing an Open IBM SANOnce the IN-VSN server is up and running, an IN-VSN server window should appear with server running status, as shown
Chapter 3. Implementing the INRANGE FC/9000 Fibre Channel Director 195After starting the client, a login window will appear. Enter user name (defaul
Chapter 1. Implementing Fibre Channel host adapter cards 71.2.6 Attaching an ESS to FICON channelsYou can use the following FICON adapters with the
196 Implementing an Open IBM SANWhen logged into the IN-VSN server as the first client ever used, then all settings are still default values and no s
Chapter 3. Implementing the INRANGE FC/9000 Fibre Channel Director 1973.2.7 Defining users Different user-levels are provided by INRANGE. You can h
198 Implementing an Open IBM SANAdding usersTo enter the user definition screen, click the Users tab as shown in Figure 3-16.Figure 3-16 Adding an
Chapter 3. Implementing the INRANGE FC/9000 Fibre Channel Director 199Click Add to enter the information for a new user as shown in Figure 3-17.Figu
200 Implementing an Open IBM SANIn Figure 3-18 we create a new user called itso_1 with admin rights.Figure 3-18 Adding an IN-VSN user: Creating an
Chapter 3. Implementing the INRANGE FC/9000 Fibre Channel Director 201However, this new user is not saved until you click Save, as shown in Figure 3
202 Implementing an Open IBM SANDeleting usersDeleting users is done using the same panel as we used for adding users. Note that you cannot delete th
Chapter 3. Implementing the INRANGE FC/9000 Fibre Channel Director 203Once you have confirmed this deletion, that particular user is deleted in the
204 Implementing an Open IBM SANTo change a user, first select it in the Users list. Once you have selected a user, you are automatically in change m
Chapter 3. Implementing the INRANGE FC/9000 Fibre Channel Director 2053.2.8 Security considerationsAs a SAN may store a great deal of sensitive and
8 Implementing an Open IBM SANThe FICON architecture prohibits this capability. The reason for the restriction is because the base S/390 and zSeries
206 Implementing an Open IBM SANZoning methodsINRANGE provides both these types of zoning: Hard zoning Name server zoning (often called soft zoning
Chapter 3. Implementing the INRANGE FC/9000 Fibre Channel Director 207When leaving the fabric without any name server zone, the only effective zone
208 Implementing an Open IBM SANWe will first perform a manual backup. Therefore, we use the IN-VSN server window to open the backup menu, as shown i
Chapter 3. Implementing the INRANGE FC/9000 Fibre Channel Director 209The database file created by this manual backup could be used for IN-VSN datab
210 Implementing an Open IBM SANFigure 3-27 AutoBackUp settings: Specifying Filename and backup intervalThe IN-VSN server main window then displays
Chapter 3. Implementing the INRANGE FC/9000 Fibre Channel Director 2113.3.2 Connecting to an INRANGE fabricA fabric is made up of one or multiple I
212 Implementing an Open IBM SANFigure 3-30 IN-VSN: Connecting to a new fabricIt is not necessary that the directors specified with their IP addres
Chapter 3. Implementing the INRANGE FC/9000 Fibre Channel Director 213Figure 3-31 IN-VSN: Initial fabric viewThe default name of this director is
214 Implementing an Open IBM SANTo simplify further usage of this environment, we decided to use the names as shown in Table 3-2. Table 3-2 Directo
Chapter 3. Implementing the INRANGE FC/9000 Fibre Channel Director 215Assigning the directors nameTo assign the directors name we enter the director
Chapter 1. Implementing Fibre Channel host adapter cards 91.3.2 Attachment requirements for the AS/400 or iSeriesThis section lists the requirement
216 Implementing an Open IBM SANAssigning port namesTo assign names to individual FC ports of our director, we click the specific director in the IN-
Chapter 3. Implementing the INRANGE FC/9000 Fibre Channel Director 217Figure 3-35 IN-VSN: Changing port namesWe start with the two ports used for
218 Implementing an Open IBM SANWe have now physically attached all server ports and the two ESS ports. That is why we now have Device information (W
Chapter 3. Implementing the INRANGE FC/9000 Fibre Channel Director 219To set the director clock, just click the specific director in the navigation
220 Implementing an Open IBM SANEnter your desired time settings and apply this by clicking OK as shown in Figure 3-38.Figure 3-38 IN-VSN: Setting
Chapter 3. Implementing the INRANGE FC/9000 Fibre Channel Director 221Enabling loop attachments To make loop node attachment possible, we have to en
222 Implementing an Open IBM SANFigure 3-39 IN-VSN: Port View to enable port specific loop attachmentOnce the Auto Sense field is activated in the
Chapter 3. Implementing the INRANGE FC/9000 Fibre Channel Director 223Figure 3-40 IN-VSN: Confirming the enabling of loop attachmentNow we are abl
224 Implementing an Open IBM SANThis adapter is set to Public Loop as shown in the Topology row. By selecting the Loop Devices tab in the IN-VSN port
Chapter 3. Implementing the INRANGE FC/9000 Fibre Channel Director 225To enable all ports to attach loop devices, select the specific director in th
10 Implementing an Open IBM SANThe following considerations need to be taken into account: You cannot specify a LUN size of 4.190-GB LUN for the SCS
226 Implementing an Open IBM SANWe show a representation of this in Figure 3-45.Figure 3-45 IN-VSN: loop port in name server table as NL_PortPort h
Chapter 3. Implementing the INRANGE FC/9000 Fibre Channel Director 227In our example, we have four loop devices attached to one director port. This
228 Implementing an Open IBM SANTo enable a particular device, use the same menu and click Enable as shown in Figure 3-47.Figure 3-47 IN-VSN: Enabl
Chapter 3. Implementing the INRANGE FC/9000 Fibre Channel Director 229Private loopPrivate loop is the most basic form of Fibre Channel. Private loop
230 Implementing an Open IBM SANUsage of public loop and private loopSince these two loop modes inherit different protocol methods, there are differe
Chapter 3. Implementing the INRANGE FC/9000 Fibre Channel Director 231Usage of private loop portsNormally, private loop ports are not able to talk w
232 Implementing an Open IBM SANThe creation and maintenance of this list is different between private targets and private initiators. Therefore, you
Chapter 3. Implementing the INRANGE FC/9000 Fibre Channel Director 233The translation entries list for private target TL_Ports contains all initiato
234 Implementing an Open IBM SANFigure 3-51 IN-VSN: adding possible targetsIf you want to add device addresses that are currently not attached to t
Chapter 3. Implementing the INRANGE FC/9000 Fibre Channel Director 235Each TL_Port has its own translation entries list, as shown in Figure 3-53.Fig
Chapter 1. Implementing Fibre Channel host adapter cards 111.3.5 Software requirements for the IBM OS/400 operating systemRelease V3R1.0 and later
236 Implementing an Open IBM SANTL_Ports and zoningOnce the translation entries list is created, these TL_Ports can actually talk to other ports in t
Chapter 3. Implementing the INRANGE FC/9000 Fibre Channel Director 237However, since INRANGE is using a Translation Entries List, these LIPs will no
238 Implementing an Open IBM SAN By no means is it possible to have communication over the boundaries of hard zones. This is also true if malfunctio
Chapter 3. Implementing the INRANGE FC/9000 Fibre Channel Director 239Figure 3-54 INRANGE hard zoning: fixed location of port groupsThe two ports
240 Implementing an Open IBM SANBuilding hard zones using port groupsNow we know that a hard zone must consist of port groups. In our example, we hav
Chapter 3. Implementing the INRANGE FC/9000 Fibre Channel Director 241When creating hard zones, all port groups in a particular hard zone must be ad
242 Implementing an Open IBM SAN3.4.3 Understanding INRANGE name server zoningIn contrast to hard zoning, there is no actual physical segmentation o
Chapter 3. Implementing the INRANGE FC/9000 Fibre Channel Director 2433.4.4 Hard zones and name server zones togetherHard zoning can strictly separ
244 Implementing an Open IBM SANThe following rules are enforced with INRANGE directors: Both TL-CFG lists as well as name server zones cannot span
Chapter 3. Implementing the INRANGE FC/9000 Fibre Channel Director 245The scenario illustrated in Figure 3-58 describes a possible layout.Figure 3-5
12 Implementing an Open IBM SANThe RS/6000 and pSeries host system does not support more than one host bus adapter on the loop. The RS/6000 and pSeri
246 Implementing an Open IBM SAN3.4.5 Defining hard zoningIn our example shown in Figure 3-59, we want to separate eight director ports for usage by
Chapter 3. Implementing the INRANGE FC/9000 Fibre Channel Director 247To start our hard zoning setup, we first select the particular director in the
248 Implementing an Open IBM SANFigure 3-61 IN-VSN: Specifying a name for a hard zoneWe have chosen to name the first zone Finance. However, later
Chapter 3. Implementing the INRANGE FC/9000 Fibre Channel Director 249We have selected the two upper leftmost port groups to be part of hard zone Fi
250 Implementing an Open IBM SANAgain we test this layout by clicking the Test button. This time everything looks fine, as illustrated in Figure 3-63
Chapter 3. Implementing the INRANGE FC/9000 Fibre Channel Director 251As illustrated in Figure 3-64, when clicking the Test button now we get a viol
252 Implementing an Open IBM SANTo activate our hard zone layout, we click Apply as illustrated in Figure 3-65.Figure 3-65 IN-VSN: Applying a hard
Chapter 3. Implementing the INRANGE FC/9000 Fibre Channel Director 253All primary FC ports of these servers will be zoned to ESS Bay 1, Port 4, and
254 Implementing an Open IBM SANBy implementing two zones, we limit the access of a particular host FC port to only one ESS FC port. We do this becau
Chapter 3. Implementing the INRANGE FC/9000 Fibre Channel Director 255We shall now explain how our zoning will look logically. As illustrated in Fig
Chapter 1. Implementing Fibre Channel host adapter cards 134. Either you or an IBM SSR checks the LUN limitations for the RS/6000 and pSeries. See T
256 Implementing an Open IBM SANBy implementing such a layout, each server is attached to two zones. Since each zone has a different ESS port as a me
Chapter 3. Implementing the INRANGE FC/9000 Fibre Channel Director 257Leave the Name Server Zone field selected. Click Add to create a new zone. Ent
258 Implementing an Open IBM SANFrom the Ports scroll list, select the ones you want to be a member of that zone as shown in Figure 3-71. Figure 3-71
Chapter 3. Implementing the INRANGE FC/9000 Fibre Channel Director 259After putting all needed ports in the Ports in Zone list, we continue with cli
260 Implementing an Open IBM SANHowever, now we are getting an error message, since our previously chosen zone number of 0 is not valid. This is show
Chapter 3. Implementing the INRANGE FC/9000 Fibre Channel Director 261To make this zone effective, click Save as shown in Figure 3-74.Figure 3-74
262 Implementing an Open IBM SANAfter saving this second zone, the zone list contains both zones with a status of Saved as illustrated in Figure 3-75
Chapter 3. Implementing the INRANGE FC/9000 Fibre Channel Director 263To do this, select the specific director in the navigation tree and then click
264 Implementing an Open IBM SANThe motivation to use cascaded directors is not limited to increased port counts. Cascaded directors can be used to c
Chapter 3. Implementing the INRANGE FC/9000 Fibre Channel Director 265– Each director or switch in a fabric must have a unique switch id.– When havi
14 Implementing an Open IBM SANAfter you install the ibm2105.rte file and all of the 2105 devices are reconfigured, vary on the volume groups and rem
266 Implementing an Open IBM SAN3.6 Monitoring and maintenance of an INRANGE SANThis topic will briefly cover these topics: Communication protocols
Chapter 3. Implementing the INRANGE FC/9000 Fibre Channel Director 267Call home functionalityCall home enables the IN-VSN software to propagate even
268 Implementing an Open IBM SANAll activities are logged and categorized into different types. Following are some examples of these operation types:
Chapter 3. Implementing the INRANGE FC/9000 Fibre Channel Director 2693.6.4 Using the IN-VSN event logThe event log contains all important events t
270 Implementing an Open IBM SAN3.7 ESS configuration guidelinesIn this chapter we have addressed some of more commonly encountered features of the
© Copyright IBM Corp. 2001 271Chapter 4. Implementing the SAN Data GatewayIn this chapter, we describe the steps involved in planning and implementing
272 Implementing an Open IBM SAN4.1 SAN Data GatewayThe IBM Storage Area Network Data Gateway is an essential component of the SAN infrastructure. I
Chapter 4. Implementing the SAN Data Gateway 273 Expand connectivity to storage devices with use of IBM SAN hubs, switches, and directors Perform
274 Implementing an Open IBM SANIf a PC with terminal emulation is used, a 9-pin female to 9-pin female, null modem cable is required and is provided
Chapter 4. Implementing the SAN Data Gateway 2754.2.1 Setting the Ethernet addressOnce restarted, the Ethernet port must be configured and attached
Chapter 1. Implementing Fibre Channel host adapter cards 1514.Remove the compact disc. 15.Shut down the host system. 16.Turn on the host system. 1.4
276 Implementing an Open IBM SANYou cannot telnet to the Gateway and use the service port at the same time. When you telnet to the Gateway, the servi
Chapter 4. Implementing the SAN Data Gateway 277Currently, up to eight different hosts can be attached to each Fibre Channel port. If all six ports
278 Implementing an Open IBM SAN4.3.1 Installing StorWatch SpecialistThe Specialist software is not bundled with the SAN Data Gateway. The Specialis
Chapter 4. Implementing the SAN Data Gateway 279Figure 4-5 StorWatch SAN Data Gateway Specialist serverThe client software can now be launched. If
280 Implementing an Open IBM SAN4.3.2 Using the StorWatch SAN Data Gateway SpecialistOnce you are logged in to the Specialist, you must now connect
Chapter 4. Implementing the SAN Data Gateway 281As we can connect to several SAN Data Gateway systems from one client session, select the particular
282 Implementing an Open IBM SANSCSI channels 1, 2, and 3 and Fibre Channel ports 1 and 4 also have a key on the left-hand side to depict that there
Chapter 4. Implementing the SAN Data Gateway 283You can also select and highlight each SCSI Channel. You will notice that as you do this, the inform
284 Implementing an Open IBM SANInformation pertaining to a particular disk device is shown in Figure 4-11.Figure 4-11 Disk device data
Chapter 4. Implementing the SAN Data Gateway 285You can perform the same drill-down on the Fibre Channel host as we did with the SCSI channel and di
Implementing an Open IBM SAN Featuring the INRANGE Portfolio December 2001International Technical Support OrganizationSG24-6413-00
16 Implementing an Open IBM SANThe ESS also offers the following interim support for Fibre Channel attachment: Feature Code 3019 — With the feature c
286 Implementing an Open IBM SANFigure 4-13 Fibre Channel host dataAs you select and highlight the different ports or devices, there are different
Chapter 4. Implementing the SAN Data Gateway 287Figure 4-15 Advanced SCSI parametersFibre Channel parameters are displayed in a similar fashion. H
288 Implementing an Open IBM SANA detailed description of the SCSI and Fibre Channel settings can be found in the IBM Storage Area Network Data Gatew
Chapter 4. Implementing the SAN Data Gateway 289From this screen, we selected the Windows NT version, and we will save this into a directory for dow
290 Implementing an Open IBM SANThe SAN Data Gateway Specialist will then prompt for the location of the new firmware as shown in Figure 4-20. This i
Chapter 4. Implementing the SAN Data Gateway 291Once the firmware process has been started, the SAN Data Gateway Specialist displays a message as sh
292 Implementing an Open IBM SANAs restarting the SAN Data Gateway is a disruptive process, the Specialist issues a warning as shown below in Figure
Chapter 4. Implementing the SAN Data Gateway 293Once the restart process is completed, the Specialist displays the prompt shown in Figure 4-26 befor
294 Implementing an Open IBM SAN4.4 SCSI devicesThe four SCSI ports on the SAN Data Gateway support Differential Ultra Wide SCSI devices. It will au
Chapter 4. Implementing the SAN Data Gateway 295The SAN Data Gateway must add this extra layer of addressing as the host is no longer directly attac
Chapter 1. Implementing Fibre Channel host adapter cards 171. Insert the Service Pack 3 compact disc into the CD-ROM or CD-R drive. 2. Open the READ
296 Implementing an Open IBM SANWhen this command is issued, you will also be given an option to clear the Virtual Private SAN (VPS) access settings.
Chapter 4. Implementing the SAN Data Gateway 297A check mark will allow access, and as shown in Figure 4-28, you can see that SAN connection 1 has a
298 Implementing an Open IBM SANA dialog box appears requesting the entry of a license key number. For units with serial numbers lower than 1300600 y
Chapter 4. Implementing the SAN Data Gateway 299Once installed, the service runs automatically and does not require further administrator interactio
300 Implementing an Open IBM SANFigure 4-32 Specialist after VPS enabled and host registrationIf no registration software is loaded on the host, or
Chapter 4. Implementing the SAN Data Gateway 301Figure 4-34 SAN Data Gateway with two hostsAdding host and connection informationThe host name and
302 Implementing an Open IBM SANSelect the host to be modified, and the information is transferred to the bottom part of the window where the modific
Chapter 4. Implementing the SAN Data Gateway 303Setting up a Virtual Private SANRemember that the SAN Data Gateway assigns its own LUN numbers, and
304 Implementing an Open IBM SANSCSI to LUN mapPrior to setting the LUN masking, it makes sense to prepare a list that has each LUN and shows which h
Chapter 4. Implementing the SAN Data Gateway 305Setting host access to LUNsTo view and set host access to particular LUNs, access the Virtual Privat
18 Implementing an Open IBM SAN1.6 Compaq host system FC attachmentThis topic describes the host system requirements and provides the procedure toat
306 Implementing an Open IBM SANOnce completed, select Apply Changes and then Close. The host system may now have to be restarted or some other metho
Chapter 4. Implementing the SAN Data Gateway 307SAN connection 1 has access to the LUNs on SCSI channels 2 and 4. VPS will control access to LUNs on
308 Implementing an Open IBM SANFigure 4-40 Fibre Channel port setting for switch attachmentBy default, the setting in the Connection Options box w
Chapter 4. Implementing the SAN Data Gateway 309Switch registrationWith VPS enabled, the switch will register with the database the WWPN of the port
310 Implementing an Open IBM SANFigure 4-42 Switch port loginYou can also check the port on the switch, by accessing the switch configuration from
Chapter 4. Implementing the SAN Data Gateway 311Changing the switch informationFrom the VPS Access Settings window, it is possible to change the unk
312 Implementing an Open IBM SANThe information on the host plymouth, that was attached using port 4, is still kept in the VPS database, but it is no
Chapter 4. Implementing the SAN Data Gateway 313Once changed, as shown in Figure 4-46, the information shown on the main window will reflect the cha
314 Implementing an Open IBM SANBy selecting and highlighting the new NT host, we can see its information, which was automatically sent by the host r
Chapter 4. Implementing the SAN Data Gateway 315Device accessTo have the new NT host access some of the devices, you need to set up the VPS Access p
Chapter 1. Implementing Fibre Channel host adapter cards 191.6.2 Compaq Tru64 UNIX Version 4.0x host systemIn this topic we explain how to install
316 Implementing an Open IBM SANA check mark in the box allows a host access to a LUN, or clear the box if you want to restrict access as described i
Chapter 4. Implementing the SAN Data Gateway 317ESS considerationsAs you configure and allow access from host systems to volumes that are in the ESS
318 Implementing an Open IBM SANSoftware, similar to SDD, is required in the host for it to recognize that it may have two or more paths to the same
Chapter 4. Implementing the SAN Data Gateway 319Another option here is to utilize the zoning and LUN masking capabilities of the SAN Data Gateway. T
320 Implementing an Open IBM SAN
© Copyright IBM Corp. 2001 321Chapter 5. Implementing the Vicom Fibre Channel SLIC RouterThe Vicom Fibre Channel SLIC Router, 7139-111, enables all IB
322 Implementing an Open IBM SAN5.1 SLIC Router featuresThe Instant Copy function can create a separately addressable copy of mirrored data that can
Chapter 5. Implementing the Vicom Fibre Channel SLIC Router 3235.2 Installing the SLIC RouterTo install and establish a SLIC storage system, the Ro
324 Implementing an Open IBM SANLED on the SSA drive will flash and then it will move to the next drive. This test should continue until all drives h
Chapter 5. Implementing the Vicom Fibre Channel SLIC Router 3257. Create general spares.The mode on SW2 is changed to mode 12 to set all drives to b
20 Implementing an Open IBM SANYou do not need to perform any special operations on the Compaq system to view the ESS volumes. Ensure that the host F
326 Implementing an Open IBM SAN5.3 SLIC Manager softwareRather than using the dip switches to configure the features, another option is to use the
Chapter 5. Implementing the Vicom Fibre Channel SLIC Router 327The SLIC Manager has a graphical user interface (GUI) and a command line interface (C
328 Implementing an Open IBM SANEditing the configuration fileWhen the software is loaded, a sample configuration file called 7190.cfg is added in th
Chapter 5. Implementing the Vicom Fibre Channel SLIC Router 329This file can now be edited to be used as the configuration file for your SLIC system
330 Implementing an Open IBM SANConfiguration file informationThe SLIC_name can be any name that you would like to use to identify the Router.Creatin
Chapter 5. Implementing the Vicom Fibre Channel SLIC Router 331Installing the SLIC Manager daemonWith the configuration file edited and a SLIC Zone
332 Implementing an Open IBM SAN5.3.3 Starting the SLIC ManagerTo start the Vicom SLIC Manager software, select Start -> Programs -> Vicom -&g
Chapter 5. Implementing the Vicom Fibre Channel SLIC Router 3335.4 Using SLIC ManagerYou can now look to see that all communications are working pr
334 Implementing an Open IBM SAN5.4.1 Drive propertiesYou can get detailed information on each drive. Select the drive so that it is highlighted and
Chapter 5. Implementing the Vicom Fibre Channel SLIC Router 335Figure 5-11 SLIC Router properties5.4.3 Setting Router to master As you move throu
Chapter 1. Implementing Fibre Channel host adapter cards 21/dev/rrzf128c: character special (8/262466) SCSI #16 2105F20 disk #1029 (SCSI ID #0) (SC
336 Implementing an Open IBM SANClick in the Always Master box so that a check mark appears. Once you click OK, the Router will then be set as the ma
Chapter 5. Implementing the Vicom Fibre Channel SLIC Router 3375.5 Composite driveA composite drive is a large drive that consists of two or more s
338 Implementing an Open IBM SANFrom the Available Drive Pool list, click a desired drive and then click the Add>> button. The drive name will
Chapter 5. Implementing the Vicom Fibre Channel SLIC Router 339When all the desired drives are added, click Next>. The Assigning Properties windo
340 Implementing an Open IBM SANClick the Next> button and a dialog box will appear, as shown in Figure 5-17, to allow you to create another compo
Chapter 5. Implementing the Vicom Fibre Channel SLIC Router 3415.5.2 Composite drive propertiesIf you view the Control Center again, by selecting T
342 Implementing an Open IBM SANSelect the composite drive and then click the Properties button. The Composite Drive Properties dialog box opens, as
Chapter 5. Implementing the Vicom Fibre Channel SLIC Router 3435.6.1 Creating a mirror driveTo create a mirror using physical drives, from the tool
344 Implementing an Open IBM SANBelow each window there is a Capacity window that will display the size of the available drive, or of the mirror driv
Chapter 5. Implementing the Vicom Fibre Channel SLIC Router 345The Assigning Mirror Drive Properties window is shown in Figure 5-22.Figure 5-22 Mi
22 Implementing an Open IBM SANIf there is no disklabel on the disk, type the following command to write the labelto the disk:#disklabel -rw rzh128 s
346 Implementing an Open IBM SAN5.6.2 Mirror drive propertiesIf you go to the Control Center window by selecting Tools -> Control Center, you wil
Chapter 5. Implementing the Vicom Fibre Channel SLIC Router 347If you select and highlight the mirror drive and then click the Properties button, th
348 Implementing an Open IBM SAN5.7.1 Creating an Instant Copy driveTo create an Instant Copy drive, select Tools -> Instant Copy Drive Setup Wiz
Chapter 5. Implementing the Vicom Fibre Channel SLIC Router 349Figure 5-26 Instant Copy Drive PropertiesThe properties that can be changed are the
350 Implementing an Open IBM SANFigure 5-27 Control Center with Instant Copy DriveNotice that in the information provided for the copy drive, there
Chapter 5. Implementing the Vicom Fibre Channel SLIC Router 351Figure 5-28 Add Mirror Member displaySelect and highlight the copy drive from the A
352 Implementing an Open IBM SANClick the OK button, and the Mirror Drive Properties will now reflect the change, as shown in Figure 5-30.Figure 5-30
Chapter 5. Implementing the Vicom Fibre Channel SLIC Router 3535.8.1 Creating a second composite driveTo provide an example of a mirror using only
354 Implementing an Open IBM SANFollow the steps to create a composite drive as described in 5.5, “Composite drive” on page 337. Once created, you ca
Chapter 5. Implementing the Vicom Fibre Channel SLIC Router 3555.8.2 Creating the mirrorThe mirror can now be created by selecting Tools -> Mirr
Chapter 1. Implementing Fibre Channel host adapter cards 231.7 Hewlett Packard 9000 FC host system attachmentThis topic describes the host system r
356 Implementing an Open IBM SAN5.8.3 Viewing mirror drive using composite drivesWith the Mirror Drive Setup Wizard completed, you can now view the
Chapter 5. Implementing the Vicom Fibre Channel SLIC Router 357In the Mirror Drive window, you can see the new mirror drive that was created above a
358 Implementing an Open IBM SANFigure 5-35 Removing a logical driveThe logical drive that was created as an Instant Copy Drive in 5.7.1, “Creating
Chapter 5. Implementing the Vicom Fibre Channel SLIC Router 3595.9.2 Mapping a general spareYou will notice in Figure 5-35 that the general spare d
360 Implementing an Open IBM SANHowever, since each composite drive had its attributes changed as it became a member of the mirror, it will no longer
Chapter 5. Implementing the Vicom Fibre Channel SLIC Router 3615.10 Expanding the SLIC systemThe SLIC storage system can be expanded to add more SS
362 Implementing an Open IBM SANOn the SSA side, there are a few options available. Each Router can have its own SSA loop so that each one can suppor
Chapter 5. Implementing the Vicom Fibre Channel SLIC Router 363Installing additional RoutersWith the existing Router and storage system powered on:1
364 Implementing an Open IBM SAN5.10.3 Adding hostsThe SLIC storage system can be expanded to include more hosts whether they are homogeneous or het
© Copyright IBM Corp. 2001 365Related publicationsThe publications listed in this section are considered particularly suitable for a more detailed dis
24 Implementing an Open IBM SAN4. Either you or an IBM SSR configures the host system for the ESS by using the instructions in your host system publi
366 Implementing an Open IBM SAN366 Implementing an Open IBM SAN IBM Enterprise Storage Server Quick Configuration Guide, SC26-7354 IBM Enterprise
Related publications 367Referenced Web sitesThese Web sites are also relevant as further information sources: www.storage.ibm.com/ibmsan/index.htm
368 Implementing an Open IBM SAN368 Implementing an Open IBM SAN www.vicom.com Vicom Systems www.vixel.com Vixelwww.scsita.orgSCSI Trade Associat
© Copyright IBM Corp. 2001 369Special noticesReferences in this publication to IBM products, programs or services do not imply that IBM intends to mak
370 Implementing an Open IBM SANThe following terms are trademarks of other companies:Tivoli, Manage. Anything. Anywhere.,The Power To Manage., Anyth
© Copyright IBM Corp. 2001 371Glossary8B/10B A data encoding scheme developed byIBM, translating byte-wide data to an encoded10-bit format. Fibre Cha
372 Implementing an Open IBM SANClass-1 A class of service providing dedicatedconnection between two ports with confirmeddelivery or notification of
Glossary 373Enterprise Network A geographically dispersednetwork under the auspices of one organization.Entity In general, a real or existing thing
374 Implementing an Open IBM SANX.271-1996) which defines how the ESCONcommand set protocol is transported using thefibre channel.FC-SW Fibre Channel
Glossary 375data between CPUs and from a CPU to diskarrays and other peripherals.HMMP HyperMedia Management ProtocolHMMS HyperMedia Management Schem
Chapter 1. Implementing Fibre Channel host adapter cards 256. From the Software Selection window, click IBMis_tag. 7. From the Action menu, click Ma
376 Implementing an Open IBM SANLoop Circuit A temporary point-to-point like paththat allows bi-directional communicationsbetween loop-capable ports.
Glossary 377N_Port Login N_Port Login (PLOGI) allows twoN_Ports to establish a session and exchangeidentities and service parameters. It is performe
378 Implementing an Open IBM SANPort Bypass Circuit A circuit used in hubs anddisk enclosures to automatically open or closethe loop to add or remove
Glossary 379SCSI-3 SCSI-3 consists of a set of primarycommands and additional specialized commandsets to meet the needs of specific device types.The
380 Implementing an Open IBM SANhigher value functions including -- reporting ofcapacity, performance, etc. over time (trends),configuration of multi
Glossary 381WAN Wide Area Network - A network whichencompasses inter-connectivity between devicesover a wide geographic area. A wide areanetwork may
382 Implementing an Open IBM SAN
© Copyright IBM Corp. 2001 383IndexNumerics1-way mirror 3422042-001 2702766 adapter 102-way mirror 3423527 3213-way mirror 3427131 3217
384 Implementing an Open IBM SANEEmulex 46Emulex LP8000 32, 42, 47, 53, 56, 58, 65, 67enabling the Ethernet port 275Enabling VPS 297ESCON 5
Index 3852108-G07 271Initialization Method 339initializeBox 274INRANGE defining hard zoning 246INRANGE FC/9000 175INRANGE hard zoning 23
© Copyright International Business Machines Corporation 2001. All rights reserved.Note to U.S Government Users – Documentation related to restricted
26 Implementing an Open IBM SAN3. Extend the volume group to include the c3t0d0 path. When you issue a vgdisplay -v command on the volume group, it l
386 Implementing an Open IBM SANnicknames 122non-RAID 109notification options 85Novell NetWare FC attachment 26NUMA-Q 15OOpen System Storag
Index 387Sun FC attachment 30switch cascading 8Switch registration 309TT_Port 264T_Ports 264Target Hosts 144Technology Pack 17Telnet
388 Implementing an Open IBM SAN
(0.5” spine)0.475”<->0.875”250 <-> 459 pagesImplementing an Open IBM SAN Featuring the INRANGE Portfolio
®SG24-6413-00 ISBN 0738424765INTERNATIONAL TECHNICALSUPPORTORGANIZATIONBUILDING TECHNICALINFORMATION BASED ONPRACTICAL EXPERIENCE IBM Redbooks are dev
Chapter 1. Implementing Fibre Channel host adapter cards 276. From the Advanced Adapter Settings menu, press the Down Arrow to highlight LUNs per ta
28 Implementing an Open IBM SANa. Execution throttle: 240 b. Fast command posting: Enabled c. >4 GB addressing: Disabled for 32 bit systems d. LUN
Chapter 1. Implementing Fibre Channel host adapter cards 291.8.3 Loading the current Fibre Channel adapter driverPerform the following steps to loa
30 Implementing an Open IBM SAN5. Click “Select an additional driver.”6. Press the Insert key.7. Insert a floppy diskette with the QLogic drivers int
Chapter 1. Implementing Fibre Channel host adapter cards 31 Solaris 2.6, Solaris 7, and Solaris 8 require patches to ensure that the host and the E
32 Implementing an Open IBM SAN4. Either you or an IBM SSR configures the host system for the ESS by using the instructions in your host system publi
Chapter 1. Implementing Fibre Channel host adapter cards 336. Replace the computer case by tightening the screws on the case or use the clamp to sec
34 Implementing an Open IBM SAN6. If the file is in the format of filename.tar.Z, type uncompress filename.tar.Z.7. Type tar xvf lpfc-sparc.tar to “u
Chapter 1. Implementing Fibre Channel host adapter cards 3518.Update the parameter list. See Table 1-8 on page 42.19.Restart the host system.1.9.5
© Copyright IBM Corp. 2001 iiiContentsPreface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
36 Implementing an Open IBM SAN11.If you downloaded the driver file from a Sun host system, go to Installing the JNI PCI Fibre Channel adapter driver
Chapter 1. Implementing Fibre Channel host adapter cards 371.9.9 Downloading current JNI SBUS Fibre Channel adapter driverThis section tells you ho
38 Implementing an Open IBM SAN1.9.11 Installing the QLogic QLA2200F adapter cardThis section tells you how to attach an ESS to a host system with t
Chapter 1. Implementing Fibre Channel host adapter cards 39l. Disable database load: Nom. IOCB allocation: 256n. Extended error logging: Disabled (m
40 Implementing an Open IBM SAN2. From the home page, click Driver Download.3. Click Use QLogic Drivers.4. Click Fibre Channel Adapter Drivers and So
Chapter 1. Implementing Fibre Channel host adapter cards 411. Change to the directory by typing: cd /kernel/drv2. Back up the sd.conf file in this s
42 Implementing an Open IBM SANSee Table 1-7 for the recommended configuration settings for the host-bus-adapter for a JNI FC64-1063 and a JNI FCI-10
Chapter 1. Implementing Fibre Channel host adapter cards 43In Table 1-9 we show the recommended configuration file parameters for the host bus adapt
44 Implementing an Open IBM SAN1.9.16 Installing the IBM Subsystem Device DriverThe following instructions explain how to install the IBM Subsystem
Chapter 1. Implementing Fibre Channel host adapter cards 451.9.17 Setting the Sun host system parametersThe following sections contain the procedur
iv Implementing an Open IBM SAN1.6.1 Attachment requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181.6.2 Compaq Tru6
46 Implementing an Open IBM SANmaxphysThis parameter specifies the maximum number of bytes you can transfer for each SCSI transaction. The default va
Chapter 1. Implementing Fibre Channel host adapter cards 47set maxphys=8388608If you are using Veritas volume manager on the ESS LUNs, you must set
48 Implementing an Open IBM SAN3. Either you or an IBM SSR defines the Fiber Channel port configuration if you did not do it during the installation
Chapter 1. Implementing Fibre Channel host adapter cards 49Perform the following steps to install the QLogic QLA2100F adapter card:1. Install the QL
50 Implementing an Open IBM SAN7. From the Advanced Adapter Settings menu, press the Down Arrow to highlight LUNs per target. Press Enter. Set the pa
Chapter 1. Implementing Fibre Channel host adapter cards 5112.Press Esc.13.Save the changes. Highlight Yes.14.Restart the server.1.10.4 Downloading
52 Implementing an Open IBM SAN16.Click OK. 17.Click Close to close the window for WinZip Self-Extractor.1.10.5 Installing the Fibre Channel adapter
Chapter 1. Implementing Fibre Channel host adapter cards 53The host bus adapter uses the time-out parameter to bound its recovery actions and respon
54 Implementing an Open IBM SAN Tar ge t Public initiator Private initiator Target and public initiator Target and private initiatorThe ESS supp
Chapter 1. Implementing Fibre Channel host adapter cards 559. From the File Download window, click the appropriate radio button and proceed as indic
Contents v1.10.9 Installing Emulex LP8000 adapter cards. . . . . . . . . . . . . . . . . . . . . 531.10.10 Downloading the current Fibre Channel a
56 Implementing an Open IBM SAN5. Click Add to create a list of drivers.A window opens that indicates the progress. When the window closes, you shoul
Chapter 1. Implementing Fibre Channel host adapter cards 57Use name server after RSCN Checked (enabled) if fabric attached using soft zoning Not che
58 Implementing an Open IBM SAN1.10.13 Verifying the configurationThe following tells you how to determine whether or not your Windows NT 4.0 host s
Chapter 1. Implementing Fibre Channel host adapter cards 59Either you or an IBM SSR must perform the following tasks to install and configure an ESS
60 Implementing an Open IBM SANPerform the following steps to install the QLogic QLA2100F adapter card:1. Install the QLogic QLA2100F adapter card in
Chapter 1. Implementing Fibre Channel host adapter cards 614. Press Alt+Q to get to the FAST!Util menu.5. From the Configuration Settings menu, sele
62 Implementing an Open IBM SAN10.From the Extended Firmware Settings menu, scroll down to Connection Options to open the Option and Type of Connecti
Chapter 1. Implementing Fibre Channel host adapter cards 6311.Click Save.12.When the download completes, click Open Folder.13.From the A:\ window, d
64 Implementing an Open IBM SAN1.11.7 Configuring for availability and recoverabilityThis section describes how to ensure optimum availability and r
Chapter 1. Implementing Fibre Channel host adapter cards 651.11.9 Installing Emulex LP8000 adapter cardsThis section tells you how to attach an ESS
vi Implementing an Open IBM SAN2.3.1 Performing the disk group configuration . . . . . . . . . . . . . . . . . . . . . 1082.4 Creating and modifyin
66 Implementing an Open IBM SAN8. From the File Download window, click the appropriate radio button and proceed as indicated:– To open this file from
Chapter 1. Implementing Fibre Channel host adapter cards 675. Click Add to create a list of drivers.A window opens that indicates the progress. When
68 Implementing an Open IBM SANUse name server after RSCN Checked (enabled) if fabric attached using soft zoning Not checked (disabled)Lun mapping C
Chapter 1. Implementing Fibre Channel host adapter cards 691.11.13 Verifying the configurationThe following tells you how to determine whether or n
70 Implementing an Open IBM SANIf your host system uses more than one Fibre Channel adapter to connect to your ESS, you must add multiple entries to
Chapter 1. Implementing Fibre Channel host adapter cards 711.12.3 Locating the WWPN for an IBM eServer or IBM NUMA-Q hostTo locate the WWPN for a N
72 Implementing an Open IBM SANProbing timeoutitem adapter WWN Cur.Topo Next Topo[0 ]pga0.0.0.7.1 1000-0000-c922-d469 FABRIC FABRIC[1 ]pgb0.0.0.8.1 2
Chapter 1. Implementing Fibre Channel host adapter cards 73For example, to look for the device path name /dev/td1, type:fcmsutil /dev/td1 where /dev
74 Implementing an Open IBM SAN1.12.9 Locating the WWPN for a Windows NT host systemTo locate the WWPN for a Windows NT host system with a QLogic ad
© Copyright IBM Corp. 2001 75Chapter 2. IBM TotalStorage Enterprise Storage Server configurationOne benefit of a SAN is to implement disk pooling. To
Contents vii3.4.5 Defining hard zoning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2463.4.6 Defining name server zones
76 Implementing an Open IBM SANFor further information on the configuration of the ESS, especially for ESCON and SCSI attachment and the ESS Web Copy
Chapter 2. IBM TotalStorage Enterprise Storage Server configuration 772.1 Introducing the ESS Web InterfaceThe Java based Web interface consists of
78 Implementing an Open IBM SAN2.1.1 Logging on to the ESS SpecialistHere we will detail the steps to log on to the ESS Specialist.Viewing the Intro
Chapter 2. IBM TotalStorage Enterprise Storage Server configuration 79To the left, we see the main button panel, from where we can access the viewin
80 Implementing an Open IBM SANFigure 2-4 New Site Certificate, information windowMore information on the certificate, including the certificate fi
Chapter 2. IBM TotalStorage Enterprise Storage Server configuration 81After closing the Information window, we are asked about our decision to accep
82 Implementing an Open IBM SANFigure 2-7 Site login windowThe session will be valid as long as any browser window is open. Therefore, when the wor
Chapter 2. IBM TotalStorage Enterprise Storage Server configuration 83Viewing the Status — Graphical View panelUsing the Status button, we get to th
84 Implementing an Open IBM SANViewing the Status — Problem Log panelTo get a detailed view on the problems encountered, we use the Problem Log butto
Chapter 2. IBM TotalStorage Enterprise Storage Server configuration 85Viewing the Problem Notification panelUsing the Problem Notification button, w
Komentarze do niniejszej Instrukcji