The Linux Manuals (man pages) document is an important part of Linux documents. Linux Manuals are organized as several sections. Each section has a group of commands for a specific area in Linux usage, administration or development.
fence_vmware_soap – Fence agent for VMWare over SOAP API Description fence_vmware_soap is an I/O Fencing agent which can be used with the virtual machines managed by VMWare products that have SOAP API v4.1+. Name of virtual machine (-n / port) has to be used in inventory path format (e.g. /datacenter/vm/Discovered virtual machine/myMachine). In the cases…
fence_vmware – Fence agent for VMWare Description fence_vmware is an I/O Fencing agent which can be used with the VMware ESX, VMware ESXi or VMware Server to fence virtual machines. Before you can use this agent, it must be installed VI Perl Toolkit or vmrun command on every node you want to make fencing. VI…
fence_vixel – I/O Fencing agent for Vixel FC switches Synopsis fence_vixel [OPTION]… Description fence_vixel is an I/O Fencing agent which can be used with Vixel FC switches. It logs into a Vixel switch via telnet and removes the specified port from the zone. Removing the zone access from the port disables the port from being…
fence_virtd – Fencing host for virtual machines Description fence_virtd is a host daemon designed to route fencing requests for virtual machines. Fence_virt and fence_xvm talk to fence_virtd, which supports multiple backend plugins, including: – libvirt for single-node operation – Cluster Checkpoints when using Linux-cluster release 3.0.0 or later – libvirt-qpid for multi-node, non-cluster operation For…
fence_virt – Fencing agent for virtual machines using VM Channel fence_xvm – Fencing agent for virtual machines using multicast Description fence_virt and fence_xvm are an I/O Fencing agents which can be used with virtual machines. Fence_xvm is backward compatible with fence_xvmd. Fence_virt and fence_xvm talk to fence_virtd, which supports multiple backend plugins, including: – libvirt…
fence_virsh – Fence agent for virsh Description fence_virsh is an I/O Fencing agent which can be used with the virtual machines managed by libvirt. It logs via ssh to a dom0 and there run virsh command, which does all work. By default, virsh needs root account to do properly work. So you must allow ssh…
fence_tool – a utility for the fenced daemon Synopsis fence_tool [COMMAND] [OPTIONS] Description This utility controls and queries the fenced(8) daemon with the following commands: join join the fence domain. leave leave the fence domain. dump print the fenced internal debug buffer ont stdout. ls display internal fenced state. The leave command will not be…
fence_scsi – Fence agent for SCSI persistent reservation Description fence_scsi is an I/O fencing agent that uses SCSI-3 persistent reservations to control access to shared storage devices. These devices must support SCSI-3 persistent reservations (SPC-3 or greater) as well as the "preempt-and-abort" subcommand. The fence_scsi agent works by having each node in the cluster register…
fence_sanlockd – daemon for fence_sanlock agent Synopsis fence_sanlockd [OPTIONS] Description The fence_sanlockd daemon is used by the fence_sanlock agent. See fence_sanlock(8), for full description. Options -D Enable debugging to stderr and don’t fork. -p path Path to shared storage with sanlock leases. -i host_id Local sanlock host_id (1-128). -w Wait for fence_sanlockd -s to send options (p,i)….
fence_sanlock – fence agent using watchdog and shared storage leases Synopsis fence_sanlock [OPTIONS] Description fence_sanlock uses the watchdog device to reset nodes, in conjunction with three daemons: fence_sanlockd, sanlock, and wdmd. The watchdog device, controlled through /dev/watchdog, is available when a watchdog kernel module is loaded. A module should be loaded for the available hardware….
fence_sanbox2 – Fence agent for QLogic SANBox2 FC switches Description fence_sanbox2 is an I/O Fencing agent which can be used with QLogic SANBox2 FC switches. It logs into a SANBox2 switch via telnet and disables a specified port. Disabling the port which a machine is connected to effectively fences that machine. Lengthy telnet connections to…
fence_rsb – I/O Fencing agent for Fujitsu-Siemens RSB Description fence_rsb is an I/O Fencing agent which can be used with the Fujitsu-Siemens RSB management interface. It logs into device via telnet/ssh and reboots a specified outlet. Lengthy telnet/ssh connections should be avoided while a GFS cluster is running because the connection will block any necessary…
fence_rsa – Fence agent for IBM RSA Description fence_rsa is an I/O Fencing agent which can be used with the IBM RSA II management interface. It logs into an RSA II device via telnet and reboots the associated machine. Lengthy telnet connections to the RSA II device should be avoided while a GFS cluster is…
fence_rhevm – Fence agent for RHEV-M REST API Description fence_rhevm is an I/O Fencing agent which can be used with RHEV-M REST API to fence virtual machines. fence_rhevm accepts options on the command line as well as from stdin. Fenced sends parameters through stdin when it execs the agent. fence_rhevm can be run by itself…
fence_rackswitch – I/O Fencing agent for RackSaver RackSwitch Synopsis fence_rackswitch [OPTION]… Description fence_rackswitch is an I/O Fencing agent which can be used with the RackSaver RackSwitch. It logs into the RackSwitch and boots a specified plug. Using the http interface to the RackSwitch should be avoided while a GFS cluster is running because the connection…
fence_node – a utility to run fence agents Synopsis fence_node [OPTIONS] nodename Description This utility runs a fence agent against nodename. The agent and args are taken from the running cluster configuration based on cluster.conf(5). fence_node is a wrapper around the libfence functions: fence_node() and unfence_node(). These libfence functions use libccs to read the node…
fence_na This is the fence agent for the Node Assassin fence device. Synopsis fence_na -a motoko.alteeve.com -n 2 -l motoko -p secret -o off Description This fence agent takes argument from the command line or from the ‘fenced’ program and interprets them into calls to send to the Node Assassin fence device. It analyzes the…
fence_mpath – Fence agent for multipath persistent reservation Description fence_mpath is an I/O fencing agent that uses SCSI-3 persistent reservations to control access multipath devices. Underlying devices must support SCSI-3 persistent reservations (SPC-3 or greater) as well as the "preempt-and-abort" subcommand. The fence_mpath agent works by having a unique key for each node that has…
fence_mcdata – I/O Fencing agent for McData FC switches Synopsis fence_mcdata [OPTION]… Description fence_mcdata is an I/O Fencing agent which can be used with McData FC switches. It logs into a McData switch via telnet and disables a specified port. Disabling the port which a machine is connected to effectively fences that machine. Lengthy telnet…
fence_lpar – Fence agent for IBM LPAR Description fence_lpar accepts options on the command line as well as from stdin. Fenced sends parameters through stdin when it execs the agent. fence_lpar can be run by itself with command line options. This is useful for testing and for turning outlets on or off from scripts. Parameters…