6.6. Creating the fence.ccs File

You can configure each node in a GFS cluster for a variety of fencing devices. To configure fencing for a node, you need to perform the following tasks:

• Create the fence.ccs file — Define the fencing devices available in the cluster (described in this section).

• Create the nodes.ccs file — Define which fencing method (or methods) each node should use (refer to Section 6.7 Creating the nodes.ccs File).

Creating the fence.ccs file consists of defining each fencing device you are going to use. You can define the following types of fencing devices in the fence.ccs file:

• APC MasterSwitch

• WTI NPS (Network Power Switch)

• Brocade FC (Fibre Channel) switch

• McData FC switch

• Vixel FC switch

• GNBD

• HP RILOE card

• xCAT

• Egenera BladeFrame system

• Manual

The fence.ccs file is used in conjunction with the nodes.ccs file to configure fencing in a cluster. The nodes.ccs file specifies fencing devices that are defined in the fence.ccs file. The fence.ccs file can define any combination of fencing devices.

If a node has dual power supplies, you must define a fencing device for each power supply. Similarly, if a node has multiple paths to FC storage, you must define a fencing device for each path to FC storage.

For more information about fencing, refer to Chapter 10 Using the Fencing System.

To create the fence.ccs file, follow these steps:

1. Create a file named fence.ccs. Use a file format according to the fencing method as follows. Refer to Table 6-2 for syntax description.

   • APC MasterSwitch — Refer to Figure 6-2.

   • WTI NPS (Network Power Switch) — Refer to Figure 6-3.

   • Brocade FC (Fibre Channel) switch — Refer to Figure 6-4.

   • McData FC (Fibre Channel) switch — Refer to Figure 6-5.

   • Vixel FC switch — Refer to Figure 6-6.

   • GNBD — For GNBD without GNBD multipath, refer to Figure 6-7. For GNBD with GNBD multipath, refer to Figure 6-8.

   • HP RILOE card — Refer to Figure 6-9.

   • xCAT — Refer to Figure 6-10.

   • Egenera BladeFrame system — Refer to Figure 6-11.

   • Manual — Refer to Figure 6-12.

2. Type parameters in the file according to the fencing device (or devices) needed:

   1. For each APC MasterSwitch fencing device, specify the following parameters: DeviceName, the fencing agent (agent =) as fence_apc, IPAddress, LoginName, and LoginPassword. Refer to Example 6-2 for a fence.ccs file that specifies an APC MasterSwitch fencing device.

   2. For each WTI NPS fencing device, specify the following parameters: DeviceName, the fencing agent (agent =) as fence_wti, IPAddress, and LoginPassword. Refer to Example 6-3 for a fence.ccs file that specifies a WTI NPS fencing device.

   3. For each Brocade FC-switch fencing device, specify the following parameters: DeviceName, the fencing agent (agent =) as fence_brocade, IPAddress, LoginName, and LoginPassword. Refer to Example 6-4 for a fence.ccs file that specifies a Brocade FC-switch fencing device.

   4. For each McData FC-switch fencing device, specify the following parameters: DeviceName, the fencing agent (agent =) as fence_mcdata, IPAddress, LoginName, and LoginPassword. Refer to Example 6-5 for a fence.ccs file that specifies a McData FC-switch fencing device.

   5. For each Vixel FC-switch fencing device, specify the following parameters: DeviceName, the fencing agent (agent =) as fence_vixel, IPAddress, and LoginPassword. Refer to Example 6-6 for a fence.ccs file that specifies a Vixel FC-switch fencing device.

   6. For each GNBD fencing device, specify the following parameters: DeviceName, the fencing agent (agent =) as fence_gnbd, and ServerName.

      For GNBD multipath, include an option = "multipath" line after the ServerName line. In addition, for GNBD multipath, you can add two optional lines: retrys = "Number" and wait_time = "Seconds".

      	Note
      	Do not use fence_gnbd to fence GNBD server nodes.

      For descriptions of those parameters refer to Table 6-2. Refer to Example 6-7 for a fence.ccs file that specifies a GNBD fencing device for a configuration that does not employ GNBD multipath. Refer to Example 6-8 for a fence.ccs file that specifies a GNBD fencing device for a configuration that does employ GNBD multipath.

   7. For each HP-RILOE-card fencing device, specify the following parameters: DeviceName, the fencing agent (agent =) as fence_rib, HostName, LoginName, and LoginPassword. Refer to Example 6-9 for a fence.ccs file that specifies an HP-RILOE-card fencing device.

   8. For each xCAT fencing device, specify the following parameters: DeviceName, the fencing agent (agent =) as fence_xcat, and RpowerBinaryPath. Refer to Example 6-10 for a fence.ccs file that specifies an xCAT fencing device.

   9. For each Egenera BladeFrame fencing device, specify the following parameters: DeviceName, the fencing agent (agent =) as fence_egenera, and CserverName. Refer to Example 6-11 for a fence.ccs file that specifies an Egenera BladeFrame fencing device.

   10. For each manual fencing device, specify DeviceName and the fencing agent (agent =) as fence_manual. Refer to Example 6-12 for a fence.ccs file that specifies a manual fencing device.

3. Save the file.

fence_devices{ 
   DeviceName { 
      agent = "fence_apc" 
      ipaddr = "IPAddress" 
      login = "LoginName" 
      passwd = "LoginPassword" 
   } 
   DeviceName {
   .
   .
   .
   } 
}

fence_devices{ 
   DeviceName { 
      agent = "fence_wti" 
      ipaddr = " IPAddress" 
      passwd = " LoginPassword" 
   } 
   DeviceName { 
   .
   .
   .
   } 
}

fence_devices{ 
   DeviceName { 
      agent = "fence_brocade" 
      ipaddr = "IPAddress" 
      login = "LoginName"
      passwd = "LoginPassword" 
   } 
   DeviceName { 
   .
   .
   .
   } 
}

fence_devices{ 
   DeviceName { 
      agent = "fence_mcdata" 
      ipaddr = "IPAddress"
      login = "LoginName" 
      passwd = "LoginPassword" 
   } 
   DeviceName { 
   .
   .
   .
   } 
}

fence_devices{ 
   DeviceName { 
      agent = "fence_vixel" 
      ipaddr = "IPAddress" 
      passwd = "LoginPassword" 
   } 
   DeviceName { 
   .
   .
   .
   } 
}

fence_devices{ 
   DeviceName { 
      agent = "fence_gnbd" 
      server = "ServerName"
      .
      .
      .
      server = "ServerName" 
   } 
   DeviceName { 
   .
   .
   .
   } 
}

fence_devices{ 
   DeviceName { 
      agent = "fence_gnbd" 
      server = "ServerName"
      .
      .
      .
      server = "ServerName" 
      option = "multipath"
      retrys = "Number"
      wait_time = "Seconds"
   } 
   DeviceName { 
   .
   .
   .
   } 
}

fence_devices{ 
   DeviceName { 
      agent = "fence_rib" 
      hostname = "HostName"
      login = "LoginName"
      passwd = "LoginPassword"    
   }
   DeviceName { 
   .
   .
   .
   } 
}

fence_devices{ 
   DeviceName { 
      agent = "fence_xcat" 
      rpower = "RpowerBinaryPath"  
   } 
   DeviceName { 
   .
   .
   .
   } 
}

fence_devices{ 
   DeviceName { 
      agent = "fence_egenera" 
      cserver = "CserverName"  
   } 
   DeviceName { 
   .
   .
   .
   } 
}

fence_devices{ 
   DeviceName { 
      agent = "fence_manual" 
   }
   DeviceName { 
   .
   .
   .
   } 
}

fence_devices {  
         apc1 { 
               agent = "fence_apc" 
               ipaddr = "10.0.3.3" 
               login = "apc" 
               passwd = "apc" 
         } 
         apc2 { 
               agent = "fence_apc" 
               ipaddr = "10.0.3.4" 
               login = "apc" 
               passwd = "apc" 
         } 
}

fence_devices {  
         wti1 { 
               agent = "fence_wti" 
               ipaddr = "10.0.3.3" 
               passwd = "password" 
         } 
         wti2 { 
               agent = "fence_wti" 
               ipaddr = "10.0.3.4" 
               passwd = "password" 
         } 
}

fence_devices {  
         silkworm1 { 
               agent = "fence_brocade" 
               ipaddr = "10.0.3.3" 
               login = "admin" 
               passwd = "password" 
         } 
         silkworm2 { 
               agent = "fence_brocade" 
               ipaddr = "10.0.3.4" 
               login = "admin" 
               passwd = "password" 
         } 
}

fence_devices {  
         mdfc1 { 
               agent = "fence_mcdata" 
               ipaddr = "10.0.3.3" 
               login = "admin" 
               passwd = "password" 
         } 
         mdfc2 { 
               agent = "fence_mcdata" 
               ipaddr = "10.0.3.4" 
               login = "admin" 
               passwd = "password" 
         } 
}

fence_devices {  
         vixel1 { 
               agent = "fence_vixel" 
               ipaddr = "10.0.3.3" 
               passwd = "password" 
         } 
         vixel2 { 
               agent = "fence_vixel" 
               ipaddr = "10.0.3.4" 
               passwd = "password" 
         } 
}

fence_devices {  
         gnbd { 
               agent = "fence_gnbd"
               server = "nodea" 
               server = "nodeb" 
          } 
}

fence_devices {  
         gnbdmp { 
               agent = "fence_gnbd"
               server = "nodea" 
               server = "nodeb" 
               option = "multipath"  <-- Additional entry
               retrys = "5"          <-- Number of retries set to 5
               wait_time = "3"       <-- Wait time between retries set to 3
          } 
}  

fence_devices { 
         riloe1 { 
               agent = "fence_rib" 
               ipaddr = "10.0.4.1" 
               login = "admin" 
               passwd = "password" 
         } 
         riloe2 { 
               agent = "fence_rib" 
               ipaddr = "10.0.4.2" 
               login = "admin" 
               passwd = "password" 
         } 
}

fence_devices {  
         xcat { 
               agent = "fence_xcat" 
               rpower = "/opt/xcat/bin/rpower"  
         }  
}

fence_devices {  
         egenera { 
               agent = "fence_egenera" 
               cserver = "c-blade1"  
         }  
}

fence_devices { 
         admin { 
               agent = "fence_manual" 
         } 
}