Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Install MCCS on both nodes
  2. Set group
  3. Add shared disk resource 
  4. Enable shared disk resource and check offline on both nodes
  5. Add SCSI Lock resource (Select new drive letter, not from the one in shared disk resource)
  6. Enable SCSI Lock resource and check Key in resource attribute in MCCS Console
  7. Change PrType 1 to 3 for attribute of SCSI Lock resource. (When SCSI Lock resource is added, make sure that SCSI Lock Disk Letter are disappeared from Windows Explorer of both servers.)
  8. Configure dependency of resources (SCSI Lock resource must go online first)
  9. Test failover from node2 to 1
  10. Test failover from node1 to 2
  11. Customer applications that use the volume setting

 

 

Adding

There are two way to add a resource which one is select this from a group name and another is select this from a resource type.

...

Add the SCSI reservation application resource to a group.
Before configuring the SCSI reservation resource, you must configure the volume in advance by using the SCSI3 supporting storage. 

  1. Select a group → right click → 'Add Resource'. 
    Image Removed
    [Figure] Adding Resource in a group

  2. Select 'ServiceSCSILock' from Resource Type lists and click 'Next' button
    Image Removed
    [Figure] Select Resource Wizard View

  3. Next steps are same as adding in resource type.

Adding in Resource Type

  1. ResourceType → Right Click → Click Add Resource
    Image Removed
    [Figure] Adding Resource in a resource type

    Getting disk information.
    Image Removed
    [Figure] Screen of Getting disk information.
    DriveLetter to be used for SCSILock can be selected.
    Image Removed
    [Figure] Selecting driver letter View
    When there is no disk for SCSI Lock resource, "Disk Not Found" message appears
    Image Removed
    [Figure] Disk Not Found

  2. Enter resource name. If you skip enter resource name, this will be given 'SLock_value' which value is selected driver letter.
    Image Modified
    [Figure] Selecting driver letter ViewSCSI Reservation Resource Added


  3. Click the 'Finish' and SCSI Lock resource is added.
    Image Removed
    [Figure] Adding SCSI Lock resource is completedbutton to add the SCSI reservation resource. 
    You can immediately check the result in the management web console.

Deleting

Select resource type → right click → delete resource.
              Select "Delete Resource". 
              Image Removed
              [Figure] Delete SCSI Lock resource viewThe deleted resource will immediately disappear from the management web console.

Status

The following table explains the status switching of the MCCS resource caused by a user's command and the status.
The command assumes that it is generated by a user.

...

StatusAgent commandDescriptionNote

Online

Disk key is exclusively reserved at an online node.
You cannot register a key at another node. 

Offline

It switches to offline while maintaining the reservation.

 
Monitoring

Check if there is a reservation made on the disk.

 

Offline

1. Disk is reserved but the resource is still offline.
2. The actual offline state where the other node acquired a reservation. 

OnlineRegister a key for a disk reservation and wait for a response from the other node.  
Monitoring

Check if there is a reservation made on the disk.

 

Trouble

It occurs when a reservation is stolen while going online.

OnlineRegister a key for a disk reservation and wait for a response from the other node.  
OfflineIt switches to offline while maintaining the reservation. 

 

 

Attribute

Image Removed

[Figure] SCSI Lock Resource Attribute view

SCSI Lock resource provides the following detailed attributes as well.
Setting are available in "Resource Unique Attribute" in resource's attribute tab.
Each attribute value has the following meanings:

...

Display the unique attribute of SCSI reservation resource.

Attribute

Description

Type

DefaultEditNote
DiskDUID

DUID(Device Unique ID, 16 byte as Hex value) of disk is used as identifier. Specify DUID of reserve disk.
This value is secure when DriveLetter atribute us specified. Try not to insert this value yourself.
DUID information can be checked through scsicmd.cmd command and both nodes need to have the same value.

STRING X 
DriveLetter

Disk to be used for reservation is specified by drive letter.
When register drive letter, DUID of connected disk will automatically obtain in drive letter.

STRING X 
KeyMAC address is used as Reserved-Key. This key is automatically set by agent.STRING   
PreemptWaitCount

Time waiting for permission of other node before reservation
Waiting time is (PreemptWaitCount * MonitorInterval) seconds.

INTEGER2 timesO 
PrType

This attribute decides on how to give the permission of reserve disk access as Persist Type specified in SCSI3-PR spec.
There are 6 types bur MCCS uses 1 (Write Exclusive) or 3 (Exclusive Access).
1 (Write Exclusive) is used when same LUN is used with shared disk, and Disk Letter can be checked in explorer.
3 (Exclusive Access) is used when only Lock_Disk is used.
In this case, SCSI Lock agent LUN is required. 'Mount' state of disk changes to 'un-mount' state.Therefore, Disk Letter will disappear from explorer.

INTEGER

Prtype=1O 

...

Panel

The output of 'scsicmd' command from source node (C29043F13 is MAC Address of NIC from source node.)

Disk DUID(DeviceUniqueID)LetterPRReserved-KeyRegistered-Keys
0 CNononenone
1 DNononenone
200c0ffd796550000f38be34f01000000EYesnonenone
300c0ffd796550000138ce34f01000000FYesC29043F13*C29043F13*
400c0ffd7965500002e8ce34f01000000GYesnonenone

 

The output of 'scsicmd' command from target node (C29043F13 is MAC Address of NIC from source node.)

Disk DUID(DeviceUniqueID)LetterPRReserved-KeyRegistered-Keys
0 CNononenone
1 DNononenone
200c0ffd796550000f38be34f01000000EYesnonenone
300c0ffd796550000138ce34f01000000FYesC29043F13C29043F13
400c0ffd7965500002e8ce34f01000000GYesnonenone

Disk 0 (C:)'s PR is set to "No". So, you can see that the disk does not support SCSI3-PR.  (In general, the "C" drive is the system booting disk and it does not support SCSI.)
Besides, Disk 1 (D:)'s PR is set to "No". You can see that the disk does not support SCSI3-PR.(Internal Disk does not support SCSI3-PR.)
Disk 2 (E:) and Disk 4 (G:)'s SCSI3-PR is set to "Yes". So, it means that the storage used supports SCSI3- PR. Their Reserved-Key and Registered-Keys are set to "none". It means that they are not yet to be registered.
Disk 3 (F:)'s Reserved-Key and Registered-Keys at the source node are set to C29043F13* and C29043F13* and at the target node to C29043F13 and C29043F13. This means that a SCSI reservation agent was used to create the resource.
The (*) marked node with the Reserved-Key and Registered-Keys indicates that a disk is reserved. In addition, only the * marked node with the Reserved-Key value (ex: C29043F13*) can access the disk.