content_image/974496.jpg
Figure 9-9 shows the result after confirming the configuration. 

<img src='content_image/974496.jpg'>

Before configuring a disk as tiebreaker, you can check its current reservation policy by using the AIX command devrsrv , as shown in Example 9-1. 

root@testnode1[/]# devrsrv -c query -l hdisk3 Device Reservation State Information ================================================== Device Name : hdisk3 Device Open On Current Host? : NO ODM Reservation Policy : NO RESERVE Device Reservation State : NO RESERVE 

When cluster services are started, the first time after a tiebreaker disk is configured on a node, the reservation policy of the tiebreaker disk is set to PR_exclusive  with a persistent reserve key, as shown in Example 9-2. 

root@testnode1[/]# devrsrv -c query -l hdisk3 Device Reservation State Information ================================================== Device Name : hdisk3 Device Open On Current Host? : NO ODM Reservation Policy : PR EXCLUSIVE ODM PR Key Value : 8477804151029074886 Device Reservation State : NO RESERVE Registered PR Keys : No Keys Registered PR Capabilities Byte[2] : 0x15 CRH ATP_C PTPL_C PR Capabilities Byte[3] : 0xa1 PTPL_A PR Types Supported : PR_WE_AR PR_EA_RO PR_WE_RO PR_EA PR_WE PR_EA_AR 

