HP XP20000/XP24000 HP StorageWorks XP Disk Array Mainframe Host Attachment and - Page 53

FICON and ESCON migration overview, Migrating from ESCON to native FICON, Native ESCON configuration

Get HP XP20000/XP24000 PDF manuals and user guides View all HP XP20000/XP24000 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 53 highlights

"Setting up storage units for zSeries hosts running Linux" on page 51 provides an example of the prerequisite information that must be obtained to run FCP Linux on the zSeries. 1. Choose one of the following methods to add devices: write a script or manually add the device. • To add more than one device to your SCSI configuration, write a small script that includes all the parameters included. This is an optional step. • Alternatively, you can also add SCSI devices to an existing configuration with the add_map command. After using this command, you must manually map the devices in the SCSI stack. 2. To make the devices available permanently, after a reboot, you must create a new initial ramdisk (RAM that is accessed like a disk) that contains the necessary modules and parameter information. First, save the module parameters (see "Setting up a Linux system to use FCP protocol devices on zSeries hosts" on page 52) in the configuration file /etc/zfcp.conf. • Create a new ramdisk with the mk_initrd utility, then run the zipl utility to update the initial program load record to point to the new ramdisk. 3. Enable multipath support using the logical volume manager kernel for Linux z/FCP. • Create physical volumes using the following commands: pvcreate /dev/sda1 pvcreate /dev/sdb1... • Put the physical volumes into a volume group using the following command: vgcreate fcpvg /dev/sda1 /dev/sdb1... • Create as many logical volumes as you need using the following command: lvcreate -size 16G fcpvg • Enable the alternate paths to the physical volumes using the pvpath command: pvpath -path0 --enable y /dev/sda1 pvpath --path1 --enable y /dev/sda1. If both paths are set to a weight of 0, they will load balance. 4. These configurations yield the SCSI device /dev/sda - /dev/sdc, This device is accessible on the first path and the SCSI device /dev/sdd - /dev/sdf accessed on the second path. FICON and ESCON migration overview This section describes the process required to migrate a zSeries between FICON and ESCON adapters and between a FICON bridge to a FICON adapter. NOTE: FICON support consists of hardware enhancements for enterprise servers, host software upgrades, DS8000 LMC, and adapters. The FICON bridge performs the ESCON to FICON conversion. Migrating from ESCON to native FICON Native ESCON configuration The following figure shows an example of a native ESCON configuration. The configuration shows an S/390 or zSeries host that has four ESCON channels attached to the storage unit through two ESCON directors. XP Disk Array Mainframe Host Attachment and Operations Guide 53

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
“
Setting up storage units for zSeries hosts running Linux
”
on page 51 provides an example of the
prerequisite information that must be obtained to run FCP Linux on the zSeries.
1.
Choose one of the following methods to add devices: write a script or manually add the device.
•
To add more than one device to your SCSI configuration, write a small script that includes
all the parameters included. This is an optional step.
•
Alternatively, you can also add SCSI devices to an existing configuration with the
add_map
command. After using this command, you must manually map the devices in the SCSI stack.
2.
To make the devices available permanently, after a reboot, you must create a new initial ramdisk
(RAM that is accessed like a disk) that contains the necessary modules and parameter information.
First, save the module parameters (see
“
Setting up a Linux system to use FCP protocol devices
on zSeries hosts
”
on page 52) in the configuration file
/etc/zfcp.conf
.
•
Create a new ramdisk with the mk_initrd utility, then run the zipl utility to update the initial
program load record to point to the new ramdisk.
3.
Enable multipath support using the logical volume manager kernel for Linux z/FCP.
•
Create physical volumes using the following commands:
pvcreate /dev/sda1 pvcreate
/dev/sdb1...
•
Put the physical volumes into a volume group using the following command:
vgcreate
fcpvg /dev/sda1 /dev/sdb1...
•
Create as many logical volumes as you need using the following command:
lvcreate --
size 16G fcpvg
•
Enable the alternate paths to the physical volumes using the
pvpath
command:
pvpath -
-path0 --enable y /dev/sda1 pvpath --path1 --enable y /dev/sda1.
If
both paths are set to a weight of 0, they will load balance.
4.
These configurations yield the SCSI device
/dev/sda - /dev/sdc
, This device is accessible
on the first path and the SCSI device
/dev/sdd - /dev/sdf
accessed on the second path.
FICON and ESCON migration overview
This section describes the process required to migrate a zSeries between FICON and ESCON adapters
and between a FICON bridge to a FICON adapter.
NOTE:
FICON support consists of hardware enhancements for enterprise servers, host software upgrades,
DS8000 LMC, and adapters. The FICON bridge performs the ESCON to FICON conversion.
Migrating from ESCON to native FICON
Native ESCON configuration
The following figure shows an example of a native ESCON configuration. The configuration shows
an S/390 or zSeries host that has four ESCON channels attached to the storage unit through two
ESCON directors.
XP Disk Array Mainframe Host Attachment and Operations Guide
53