Instructs the CHARON VM to create a set of virtual FC devices and connect to the virtual system through the virtual KGPSA FC Adapter.

In this mode WWID and UDID values are taken from the storage controller directly. Note that some storage controllers may not support aquiring UDID, in this case this way of mapping cannot be used in case of OpenVMS (Tru64 Unix is Ok)!

Syntax:

where the "Storage controller path ID" parameter is a storage (for example SAN) controller path ID. This ID can be obtained from the "Host Device Check" utility ("Storage Controllers" section).

Once specified, all the disks attached to the storage are automatically mapped as disk units to CHARON VM.

Example:

It is also possible to use wildcards for specifying the ID number:

Example:

In this case CHARON will collect the LUNs from all the matching paths. 

This syntax works disregarding whether Windows MPIO is active or not. If it is active, CHARON VM uses "active" path (because it works through Windows), if Windows MPIO is OFF, CHARON VM selects the first matching path (and warns you in the LOG file).

Note that LUNs obtained by usage of "storage_controller_path_id" parameter is not re-enumerated on reboot, so this mode is possible to use in case of shared disks clusters.

Possible values of the parameter are strings in one of the following forms:

• Physical disk

  • "\\.\PhysicalDrive<X>", where X is 0, 1, … 
    Be careful not to destroy all the information from the disk dedicated to CHARON VM by mistake. 
    These disks must not be formatted by the host OS. 
    In this mode WWID is generated by CHARON and UDID is defined by the index of the "container" parameter. 
    Example:
    

    set FGA container[0]=”\\.\PhysicalDrive1"

    
    

    Note

    In case "\\.\PhysicalDrive<N>" points to some external iSCSI or FC disk note that the disks re-enumeration may appear on CHARON host reboot, for example an external disk originally referenced as "\\.\PhysicalDrive3" may become "\\.\PhysicalDrive1" etc. Especially it is important in shared disks cluster configurations!  So it is stricty recommended to use "Mapping by WWID" / "Mapping iSCSI disks" ways of mapping in these situations (see below). The mapping by using "storage_controller_path_id" (see above) is acceptable as well, since it is not re-enumerating LUNs on each re-boot or CHARON VM restart.

    .

• Physical disk by its WWID

  • "\\.\PhysicalDrive(DevID =XXXX-XXXX-XXXX-XXXX-XXXX-XXXX-XXXX-XXXX)"
    Be careful not to destroy all the information from the disk dedicated to CHARON VM by mistake.
    These disks must not be formatted by the host OS.
    DevID addresses the target physical disk by its WWID (hexadecimal 128-bit identifier assigned to the disk drive by its manufacturer/originator).
    In this mode WWID is generated by CHARON VM and UDID is defined by the index of the "container" parameter.
    Example:

    Div class small set FGA container[100]="\\.\PhysicalDrive(DevID= 6008-05F3-0005-2950-BF8E-0B86-A0C7-0001)"

    
    

    Div
    class pagebreak

    The WWID values can be obtained from "Host Device Check" utility ("All drives" section).

    
    

    Note
    If the "Host Device Check" utility does not display any WWID, this means the target disk does not have one. Use the "\\.\PhysicalDrive<N>" mapping in this case.

    
    

• iSCSI disks

  • "\\.\PhysicalDrive(iSCSITarget = <iSCSI target>, LUN = <LUN number>)"
    iSCSITarget addresses the disk by its iSCSI target name. LUN specifies LUN on connected iSCSI disk.
    In this mode WWID is generated by CHARON VM and UDID is defined by the index of the "container" parameter.
    Example:

    Div class small set FGA container[200]="\\.\PhysicalDrive(iSCSITarget= iqn.2008-04:iSCSI.charon-target-test1, LUN= 1)"

    .

• File representing a physical disk of the HP Alpha system (disk image)
  • [<drive>":\"<path-name>"\"]<file-name>[".vdisk"]

    These files can be created from scratch with "MkDisk" utility. Data and OS disks backups are transferred from the original system via tapes or network and restored into these container files. 

    Mapping may also include the full path (recommended), for example: "C:\My disks\my_boot_disk.vdisk"
    Example:

    set FGA container[401]="my_dka401.vdisk"

    
    

    Warning
    Using compressed folders to store virtual disks and tapes is not supported

    .

This parameter is initially not set, thus creating NO storage elements on the controller..