This section describes the steps needed to configure PowerMax iSCSI using the Unisphere for PowerMax graphical user interface.
Note: Prior to configuring iSCSI using Unisphere for PowerMax, ensure that there is a dedicated network for iSCSI, and that the network and VLAN on the host and switch are set up correctly.
- For high availability and scale, create multiple iSCSI targets—at least one per iSCSI front end port. The following example shows the creation of a single iSCSI target on iSCSI director emulation 1E.
- From Unisphere for PowerMax Dashboard -> System click iSCSI. This will open the iSCSI Dashboard which is the base from which all ISCSI components are configured. On iSCSI Dashboard, the steps required to complete iSCSI configuration on PowerMax are listed for ease of navigation and management.
Figure 2. iSCSI dashboard and actions required for complete configuration
- From the iSCSI Dashboard, click on iSCSI Targets (Unattached) -> Create to open a dialog box to create iSCSI target.
- Select the director that your target will be presented from, the target IQN name (you can choose custom name or have the system automatically generate one), the Network ID, and the TCP port (default port is 3260 for iSCSI) and click OK. Note that the newly created target is in the disabled state. You must enable it while attaching it to an IP interface.
Figure 3. Create iSCSI Target
Step 2: Create IP Interface
To provide flexibility, you will create one or more IP interfaces on a physical port and then later attach them to a target created on the same director board in Step 1.
- From the iSCSI dashboard, click IP Interfaces to open the IP interfaces page and then click Create to open a dialog box to create the IP interface.
- Select iSCSI director, port, desired IP address, subnet prefix, Virtual Local Area Network (VLAN) ID, and Maximum Transaction Unit (MTU). The default MTU is 1500, but we recommend that you to set it to 9000 for better performance of the Microsoft applications database. A Network ID is a PowerMaxOS construct that is used internally by the system to associate an array IP interface with an array iSCSI target and isolate IP interfaces within same subnet. The valid range for a Network ID is from 0 to 511. VLAN ID of 28 is used in the configuration which should match with that on the switch.
Figure 4. Create IP interface
Step 3: Enable Target and attach to IP interface
After a target is created, it is in disabled state by default and shows up in the list of unattached targets.
- To enable the target, click iSCSI Targets unattached, select the target and click Enable.
- To attach the target to an IP interface, select the target and click Attach.
- In the Attach dialog box, select an existing unused IP interface, or create a new one.
Figure 5. Enable Target and attach to IP interface
Step 4: Create a port group of iSCSI targets
- Select Hosts-> Port Groups-> Create to open the Create Port Group dialog box.
- Enter a port group name, select the iSCSI radio button and select the newly created target from the list. As shown in the list of ports, several storage virtual ports that are internally mapped to a physical iSCSI port are available for selection.
- From the drop-down menu in the bottom right (Add to job list menu), select Run Now.
Figure 6. Create iSCSI port group
Step 5: Create an Initiator Group of host iSCSI IQN
Use the database server iSCSI initiator IQN to configure an iSCSI host initiator in Unisphere. The database server iSCSI initiators are not visible in Unisphere without logging into targets, so the easiest method to create an initiator group is to manually enter the database server IQN.
- Select Hosts-> Hosts-> Create->Create Host to open the Create Host dialog box.
- Enter a name, select the iSCSI radio button and manually add the database server IQN by clicking on the + symbol on the right side, followed by OK. From the drop-down in right bottom, select Run Now.
Figure 7. Create Host
Note: On Linux servers it is easy to identify the initiator’s IQN by looking at the contents of the file /etc/iscsi/initiatorname.iscsi for each of the node in cluster.
Step 6: Create a storage groups for Oracle
A storage group (SG) is a way to group devices together so they can be managed as a single entity. An SG can be stand-alone or in a parent-child relationship. A parent SG contains one or more child SGs. In this way, storage management operations on the stand-alone (or child) SG apply only to that SG, and operations on the parent apply to all its child SGs as a unit. In this example grid_sg contains the Oracle +GRID ASM disk group devices (Oracle GI), fra_sg contains the Oracle +FRA ASM disk group devices (archive logs), and db_sg is a parent SG, containing data_sg and redo_sg—Oracle +DATA ASM disk group devices (data files) and Oracle +REDO ASM disk group devices (redo logs).
To create the storage groups for the database, select the Create button in the Storage Group section in Unisphere. The storage group creation wizard allows the creation of just the storage group, which is done by executing the job after the first screen, creation of a storage group and placing it in a masking view, which is done by completing all the steps in the wizard.
Figure 8. Storage Groups for Oracle
Step 7: Create masking views
PowerMax devices are made visible to hosts through masking views. To create a masking view, you need a storage group (SG), a port group (PG) and an initiator group (IG). The SG contains the devices you want to make visible. For iSCSI, the PG contains virtual iSCSI ports, where each port is associated with a target. The IG contains the iSCSI IQN of the database servers to which devices needs to be presented to. Each server that requires access to devices in a storage system needs to be part of a masking view in that storage system. Once the masking view is created, the devices in the SG are visible across the storage ports in the PG to the all the database servers with initiators in the IG.
- Go to the masking view menu (Hosts -> Masking Views->Create Masking View) and create the masking views using IG and PG created for iSCSI in the steps above.
- Create three masking views for three Oracle SGs: db_sg, fra_sg, and grid_sg.
Figure 9. Masking View creation