# This is the main configuration file for the TrippLite PDU fence device. # # This can support one or more TrippLite PDU fence devices. # # TrippLite SNMP Fence Agent # # Core functions; # # Eric Knific (iggi) # eknific@etshost.com # www.etshost.com / www.ericknific.com / iggi.me # # FenceAgentAPI adaption; # # Digimer; digimer@digimer.ca # http://digimer.ca # # This software is released under the GPL v2. See the LICENSE file in the # configuration directory for a copy of the GPL v2. # # Bugs; # - None known, many expected # # Warnings; # - The TrippLite PDUs are notorious for having delays in state change actions # and state change detection. This makes them sub-optimal as fence devices. # If you use one, expect fence actions to take up to 30 seconds (with an # averaage of about 15 seconds in practice). ############################################################################### # System: # # - Here you setup general values for the fence agent and any/all nodes. # ############################################################################### # This must be set to the number of TrippLite PDU devices you are using. It # must be a positive integer. #system::tl_num = 1 system::tl_num = 1 # Version of the fence_tripplite_snmp fence agent. system::agent_version = 1.0.0 # This is the log file. If unset, no logging will occur. If using '/var/log/', # be sure that this agent is able to create or edit the file. The default is to # write to '/tmp' to prevent accidental failure of the agent due to # misconfiguration. #system::log = /var/log/fence_tripplite_snmp.log system::log = /var/log/fence_tripplite_snmp.log # This is the lock file used to help prevent simultaneous calls to # fence_tripplite_snmp. #system::lock_file = /tmp/fence_tripplite_snmp.lock system::lock_file = /tmp/fence_tripplite_snmp.lock # When a lock file is older than this number of seconds, it is considered stale # and is removed the next time fence_tripplite_snmp is called. If a pending call is # waiting, it will remove the old lock and proceed once the existing lock file # reaches this age. #system::lock_timeout = 300 system::lock_timeout = 300 # This is the authentication information... It is currently a simple plain text # compare, but this will change prior to first release. system::username = admin system::password = secret ############################################################################### # Devices: # # - Here you setup each fence device. There must be a corresponding # # 'node::X::var' for each node where 'X' is between 1 and 'system::tl_num'. # ############################################################################### ### Define values for PDU 1. # The PDU name. This is an abitrary value that you can set however you wish. tl::1::tl_name = pdu1 # This is the IP address and port where I will use to connect to this PDU. # NOTE: THIS MUST MATCH THE VALUE USED IN '/etc/cluster/cluster.conf'! If you # used a resolvable name there, use the same name here. Vice versa for IP # addresses. If this doesn't match the 'ipaddr' argument sent by the 'fenced' # daemon the fence will not work properly! tl::1::ipaddr = pdu1.domain.com tl::1::tcp_port = 161 # This is the number of ports provided by this TrippLite PDU. tl::1::max_nodes = 8 # These are aliases for each TrippLite PDU port. They should match the name or # URI of the node connected to the given port. This is optional but will make # the fenced 'list' argument more accurate and sane. If a port is listed here, # then the 'list' action will return ','. If a port is not # defined, 'list' will return ','. If a port is # set to 'unused', it will be skipped when replying to a 'list'. tl::1::alias::1 = node01.domain.com tl::1::alias::2 = node02.domain.com tl::1::alias::3 = unused tl::1::alias::4 = unused tl::1::alias::5 = unused tl::1::alias::6 = unused tl::1::alias::7 = unused tl::1::alias::8 = unused