• Setting Up a Windows or Mac OS Host to Use LUN storage over FC

    PDF

    Setting Up a Windows or Mac OS Host to Use LUN storage over FC

    Requirements for setting up a host

    These system and network requirements must be met before setting up a host to use Unity storage.

    Before you can set up a host to use Unity storage, the following storage system and network requirements must be met.

    System requirements

    Before configuring hosts to access the storage system, ensure that these requirements are met.

    Complete the following tasks before connecting hosts to the storage system:

    • Install and configure the system using the Initial Configuration wizard.
    • Use Unisphere or the CLI to configure NAS servers or interfaces, or iSCSI or Fibre Channel (FC) LUNs, on the storage system.

    SAN requirements

    For a host to connect to FC LUNs or VMware VMFS and Block VVol datastores on the Unity system, the host must be in a SAN environment with the storage system, and zoned so that the host and the storage system are visible to each other over the SAN. For a multi-pathing environment, each Unity FC LUN for the host must have two paths associated with it. These two paths should be on different switches to ensure high availability.

    Path management SAN requirements

    When implementing a highly-available SAN between a host and the Unity system, keep in mind that:

    • A LUN or VMware VMFS datastore is visible to both SPs.
    • You can configure multiple paths for a LUN. These paths should be associated with separate physical ports on the same SP.
    • Each LUN must present the same LUN ID to all hosts.
    Directly attaching a host to a storage system is supported if the host connects to both SPs and has the required multipath software.

    VSS HW Provider overview

    The VSS HW Provider runs as a Windows service and provides the interface between the Microsoft Volume Shadow Copy Service (VSS) and your storage system. The VSS HW Provider enables VSS requestor applications, such as VSS-enabled backup applications, to make snapshots of iSCSI and FC LUNs.

    Microsoft VSS

    VSS provides the backup framework for Windows Server 2003 R2, Windows Server 2008, and Windows Server 2012 and enables the creation of snapshots (called shadow copies for Microsoft VSS) — point-in-time copies of data. VSS is integrated with front-end applications so they can create and access shadow copies.

    The VSS architecture includes VSS providers. A VSS provider creates and maintains shadow copies and acts as the interface to point-in-time imaging capabilities either on a storage platform (hardware-based provider) or in a host operating system (software-based provider). The Unity VSS HW Provider is a hardware-based provider that works directly with iSCSI and FC LUNs on the Unity iSCSI and FC interfaces and with the VSS service on Windows Server 2003 R2, Windows Server 2008, or Windows Server 2012 hosts to provide consistent shadow copy creation and addressing.

    Because the Unity VSS HW Provider is a hardware-based provider, it reduces the load on the CPU and memory of the host. It is also more efficient in an environment where shadow copies of multiple volumes must be taken simultaneously.

    Refer to the Microsoft documentation for more information about VSS.

    Windows host — Using multi-path management software over FC

    Multi-path management software manages the connections (paths) between the host and the storage system to provide access to the storage if one of the paths fails. The following types of multi-path management software are available for a Windows 2003, Windows Server 2008, or Window Server 2012 connected host :

    • EMC PowerPath software on a Windows 2003, Windows Server 2008, or Windows Server 2012 host. Refer to the Unity Support Matrix on the support website for compatibility and interoperability information.
      PowerPath is not supported for Windows 7.

    Setting up a storage system for multi-path management software

    For a storage system to operate with hosts running multi-path management software, each LUN on the system should be associated with multiple paths.

    For highest availability, use multiple paths. The network interfaces can be on separate subnets.

    Installing PowerPath

    Procedure
    1. You cannot configure your storage system FC connections to present the FC LUNs to both a standalone Windows host and its Windows virtual machines. If you will configure your FC connections to present the FC LUNs directly to a stand-alone Windows host with HBAs, install PowerPath software on the stand-alone host. If you will configure your FC connections to present FC LUNs directly to a Windows virtual machine with HBAs, install PowerPath software on the virtual machine. On the host or virtual machine, download the latest PowerPath version from the PowerPath software downloads section on the EMC Online Support website.
    2. Install PowerPath using a Custom installation as described in the appropriate PowerPath installation and administration guide for the host’s or virtual machine’s operating system.
      This guide is available on EMC Online Support. If the host or virtual machine is running the most recent version and a patch exists for this version, install it, as described in the readme file that accompanies the patch.
    3. When the installation is complete, reboot the host or virtual machine.
    4. When the host or virtual machine is back up, verify that the PowerPath service has started.

    Configuring FC LUNs for the host

    Use Unisphere or the CLI to:
    Procedure
    1. Create FC LUNs for the host.
    2. Add the host to the storage system by accessing the Hosts tab in Unisphere or using the CLI and creating a host.
    3. Provide host access to the FC LUNs. Host access options are: No Access, LUN, Snapshot, LUN and Snapshot.
      On a Mac OS host, Xsan will not log into the FC storage if no vdisk0 is configured on the storage system.

      For information on performing the above Unisphere tasks, refer to the Unisphere online help.

    Windows host — Setting up for FC LUNs

    Install the Unity VSS HW Provider

    It is recommended that you install the VSS HW Provider on the host that will use the iSCSI or FC LUNs with backup applications.

    To install the Unity VSS HW Provider:

    Procedure
    1. Log in to the host using an account with administrator privileges.
    2. Download the software package that you want to install as follows:
      1. Locate the Unity VSS tool on online support.
        You may need to filter by Support Tools.
      2. Choose the correct version for your Windows platform, and select the option to save the software to the host.
    3. In the directory where you saved the software, double-click the Unity VSS provider executable file to start the installation wizard.
    4. Follow the instructions in the wizard to complete the installation of the Unity VSS provider.

    Starting and stopping the Unity VSS HW Provider

    The Unity VSS HW Provider runs as a Windows service and is enabled by default. You can stop and start this service from the Windows Services administrative tool.

    For a multi-path configuration, install the MPIO feature

    If the Windows host will use a multi-path configuration to connect to the LUNs, you should install the MPIO feature. To install MPIO on Windows Server 2008:

    Procedure
    1. Open Server Manager.
    2. In the Server Manager tree, click Features.
    3. In the Features pane, under Features Summary, click Add Features.
    4. In the Add Features Wizard, select Multipath I/O, and click Next.
    5. In the Confirm Installation Selections dialog box, click Install.
    6. When the installation is complete, in the Installation Results dialog box, click Close.
    7. When prompted to restart the computer, click Yes.
      After restarting, the host finalizes the MPIO installation.
    8. Click Close.

    Set registry values

    Incorrectly modifying the Registry can cause serious system-wide problems that can require you to reinstall the system. Use the Windows Registry Editor at your own risk.
    Procedure
    1. On the host, run the Windows Registry Editor (regedit.exe).
    2. Go to HKEY_LOCAL_MACHINE\SYSTEM\.
    3. Right-click CurrentControlSet, and search for the MaxRequestHoldTime key and modify its value from 60 to 600 (decimal) or from 3c to 258 (hexadecimal).
      Verify that the path to the parameter that you found in the CurrentControlSet. If it is not, search for the parameter again. If you make changes to ControlSets other than the top level current set, those changes will not affect the system.
    4. If the host is running PowerPath:
      1. Search for the register keys list in Table 1.
        Verify that the path to the parameter that you found in the CurrentControlSet. If it is not, search for the parameter again. If you make changes to ControlSets other than the top level current set, those changes will not affect the system.
      2. Record the value of each of these registry keys, so you have them in case you need to uninstall PowerPath.
      3. Update each of these registry keys. See Table 1.
        Table 1. Registry keys to update (iSCSI only)
        Registry keys
        Instructions
        LinkDownTime
        Set to 600.
        AsyncLogoutPauseTimeout (new value)
        Add this REG_DWORD key in the same key as LinkDownTime. Set it to 600.
        DelayBetweenReconnect

        PortalRetryCount

        Find the DelayBetweenReconnect value. Set the PortalRetryCount value so that PortalRetryCount*DelayBetweenReconnect=600
        SrbTimeoutDelta (for PowerPath only)
        Set to 100 for PowerPath only.
    5. Quit the Registry Editor.

    Windows host — Connecting to a FC LUN

    Windows hosts connect directly to FC LUNs that they have access to across the SAN. To connect a Windows host to a FC LUN:

    Configuring a Windows Server 2003 host to connect to a FC LUN

    To add FC storage to a Windows Server 2003 host:
    Procedure
    1. Select LUN Management > Manage Server Connections.
    2. Click Add.
    3. In the Add Server window, add the storage system, and optionally specify a description.
    4. Click OK. The storage system appears in the Manage Server Connections window. All the ports that were discovered appear on the Fibre Channel Ports tab.
    5. Optionally, add additional FC ports manually:
      1. Select the Fibre Channel Ports tab.
      2. Click Add.
      3. Specify the WWN of the FC port.
      4. Click OK.
    6. Enable the FC ports for LUN access:
      1. Select the storage system from the server list.
      2. Select the Fibre Channel Ports tab. Select FC ports to enable.
        If the storage system is not configured for multipathing, enabling more than one FC port may cause data corruption.
      3. Click OK.

    Configuring a Windows Server 2008 R2, Windows Server 2012, Windows7, or Windows 8 host to connect to a FC LUN

    To add FC storage to a Windows Server 2008 R2, Windows Server 2012, Windows 7, or Windows 8 host:
    Procedure
    1. Open Storage Manager for SANs. Click Manage Server Connections.
    2. Click Add.
    3. In the Add Server window, add the storage system, and optionally specify a description.
    4. Click OK.The storage system appears in the Manage Server Connections window. All the ports that were discovered appear on the Fibre Channel Ports tab. Optionally, add additional FC ports manually:
      1. Select the Fibre Channel Ports tab.
      2. Click Add.
      3. Specify the WWN of the FC port.
      4. Click OK.
    5. Enable the FC ports for LUN access:
      1. Select the storage system from the server list.
    6. Select the Fibre Channel Ports tab. Select FC ports to enable. If the storage system is not configured for Multipathing, enabling more than one FC port may cause data corruption. Click OK.

    Windows host — Setting up to use iSCSI or FC LUNs

    Register the LUNs as MPIO devices (Windows Server 2008 R2 and Windows Server 2012)

    If you are using Multipath I/O (MPIO) with Windows Server 2008, you must register LUNs as MPIO devices and set up MPIO to discover iSCSI or FC devices:
    Procedure
    1. On the host, start the MPIO Administrative Tool:
      Either Start > Administrative Tools and select MPIO or Start > Run and enter mpiocpl.exe.
    2. Open the MPIO control panel, and click the Discover Multi-Paths tab.
    3. Select the Add support for iSCSI devices check box, and click Add.
    4. When prompted to restart the computer, click Yes.
      When the computer restarts, the MPIO Devices tab lists the additional hardware ID “MSFT2005iSCSIBusType_0x9.” When this hardware ID is listed, all iSCSI bus attached devices will be claimed by the Microsoft DSM.
    5. Restart the host when prompted.

    Set the offset for the LUN to 64 KB

    This task is only required for systems running Hyper-V on Windows Server 2003, or systems that were upgraded from Windows Server 2003 to Windows Server 2008 or later.

    After the initiator logs in to a target, each of the target’s LUNs that the initiator can access appears as an unknown disk in the Windows Disk Management tool.

    To set the offset for the LUN on the host:

    Procedure
    1. Select Run > diskpart.
    2. Select the disk:
                                    select disk n
                                  

      where n is the disk number.

      If you do not know the disk number, enter:

                                    list disk
                                  
    3. On the selected disk, create a primary partition with an offset of 64 KB:
                                    create part pri align=64
                                  

    Configure a volume on the LUN

    The following configuration process initializes the LUN, creates a partition, formats a volume on the partition, and mounts the partition on a drive letter:
    Procedure
    1. On the host, in the Microsoft Disk Management tool, select the LUN.
    2. If the system asks you to initialize the disk, click Yes, but do not choose to make the disk a dynamic disk because the iSCSI interfaces do not support dynamic disks.
      For a given LUN, its drive letter, disk number, and LUN number are independent.
    3. Use a quick format operation (Windows Server 2003 or Windows Server 2008) or the New Simple Volume wizard (Windows 7) to create a volume on the disk with the following properties:
      • NTFS file system
      • 64K location unit size
      Do not format more than one LUN at a time. Otherwise, some of the volumes can become write-protected and cannot be formatted.

      You can change the volume label. Because the disk number of a LUN can change after system restart or after logging in to and out of a target, be sure to change the default volume label (“New Volume”) to a descriptive label.

    4. Assign an available drive letter to the disk.
    5. Close the Disk Management tool.

    Mac OS host — Setting up for FC LUNs

    To set up a Mac OS for FC LUNs, you must perform these tasks:

    1. Installing and configuring Xsan on a Mac OS host
    2. Set up a Mac OS host to use LUNs

    Installing and configuring Xsan on a Mac OS host

    To connect a Mac OS host to FC storage, you must add the host to the SAN as a client.
    Procedure
    1. On the host, select System Preferences > Xsan. Click Enable Xsan.
    2. Install the Xsan software on the host, and update it to the latest version.
    3. Open Xsan Admin and select Computers.
    4. Add the host to the SAN.

    Set up a Mac OS host to use LUNs

    Before the Mac OS host can use a LUN, you must use the Mac OS Disk Utility to:

    1. Format the LUN
    2. Partition the LUN

    Format the LUN

    Procedure
    1. On the host, go to Finder > Application > Utilities.
    2. Double-click Disk Utility.
    3. In the left panel, select the LUN.
    4. Click the Erase tab.
    5. For Volume Format, select the format that you want, and confirm your format choice.
    6. Click Erase and verify the erase procedure, and click Erase again to start the erase process.
      When the erase process is finished, the LUN is ready for you to partition it.

    Partition the LUN

    Procedure
    1. On the host, go to Finder > Application > Utilities.
    2. Double click Disk Utility.
    3. In the left panel, select the LUN.
    4. Click the Partition tab.
    5. Under Volume Scheme, select the number of partitions for the LUN.
      The utility displays equal-sized partitions to fill the available space on the LUN.
    6. For each partition:
      1. Select the partition.
      2. In Name, enter a name for the partition.
      3. Under Format, select the format for the partition.
        The default format - Mac OS Extended (Journaled) - is a good choice for most uses.
      4. In Size, enter the size for the partition.
    7. When you have specified, the name, size, and format for each partition, click Apply.
      The Disk Utility uses the partition information to create volumes that the host can access and use. When the partitioning process is complete, the new volumes are mounted on the desktop and ready to use.

      You are now ready to either migrate data to the LUN or have the host start using the LUN. To migrate data to the LUN, go to Migrating FC or iSCSI Data to the Storage System.