ISO8859-1I1 1RN5P .Z1 5 < !F 7h '+j"<0@mN@ >EK 7UW +!   $ !2 " # ($' >%% f&O 'B (7 )I W*/ +. ,' -D (.3 m/= 0, 1< 2' I3( q45 5 6 7 8 9+!:M;T< o={>?@ABC*D+/E[F0vG*HI  } t8  0M/~,,  ' F f  "   Local node cannot access cluster repository disk.Cluster repository disk is down or not reachable.A hardware problem prevents local node from accessing cluster repository disk.The local node was halted to prevent data corruption.Correct hardware problem that caused loss of access to cluster repository disk.Deadman detected heartbeat loss and triggered.Repository disk lost. LAN/SAN communication lost.Heartbeat not detected.The local node was halted to prevent data corruption.Establish connections so that heartbeats can reach the node.Cluster Duplicate Pseudo IP FoundDuplicate Pseudo IP is being configured on Cluster nodeNode Shorthand IDDuplicate Pseudo IP AddressCluster could not generate AHAFS event.Cluster software could not allocate memory.A cluster AHAFS event was lost. If the problem persists then contact appropriate service representative.Asymmetric Topology reconciliation detected inconsistency of Cluster node states. To prevent repository data corruption, CAA cluster will call panic to halt node.Local node cannot contact all nodes that are known to be UP.Node has less contact value than the other nodes in the Cluster.The local node was halted to maintain consistent view of the Cluster Topology.Correct Hardware or Network problem that caused loss of contact.Contact ListRepository disk was not found. Hence CAA is not loaded on local node.Repository:Cluster backup repository disk is down or inaccessible.A hardware problem prevents local node from accessing cluster backup repository disk.Correct hardware problem that caused loss of access to cluster backup repository disk.Backup Repository disk not found.Backup Disk InfoUnknownAutomatic Repository Updated failed.Try manual replacement of cluster repository disk.Primary Disk InfoReplacement Disk InfoAutomatic Repository Updated succeeded.Primary repository disk was replaced.A hardware problem prevented local node from accessing primary repository disk.Primary repository disk was replaced using backup repository disk.Detected the problem with CAA ASymmetric Security keys.Local node cannot read certificates or cannot import public/private keys.The local node can not enable Cluster Security.Correct the certificate and private key files.CAA Asymmetric Keys Verification failedNode is heartbeating solely over disk or FC for more than 15 minutesMulticast seems to be blocked by underlying networkEnable multicasting so that nodes can heartbeat over ethernetNode seems to be experiencing network issuesFix network issues so that cluster can heartbeat over TCP/IP/var filesystem is running low on spaceRSCT could malfunction if /var gets fullIncrease the filesystem size or delete unwanted filesPercent full Percent threshold FFDC failed on some nodes.Nodes not reachable.Collect FFDC manually from following nodes.Nodes:FFDC failed on local node.Request by:FFDC Successful.FFDC request processed by node.FFDC initiated.Refer to Detail section.Reason for failure:A split has been detected.Nodes are not able to exchange heartbeats.Nodes in remote island will be marked down.A merge has been detected.Nodes started exchanging heartbeats after split.Event generated for RSCT to perform merge.CAA disk clean requested.CAA KE unconfigure requested.This attribute controls the timeout interval for coordinated cluster configuration changes per phase per node in seconds. The default value is 60 seconds. A value of zero disables the timeout.This attribute controls the behavior of the node monitor which periodically evaluates the set of activated heart beating sources to determine whether a node is UP or DOWN. This attribute specifies the amount of time in milliseconds that the node monitor must wait after it makes the determination that another node is DOWN before posting it as DOWN. The valid range is 5000-30000 milliseconds. The default value is 10000 milliseconds.This attribute controls the frequency in which the node heartbeats across the various enabled heart beating sources as defined by hb_src_xxx attributes. It determines the number of milliseconds before another node may consider node X to be DOWN if it receives no incoming heartbeats from node X. The valid range is 1000-20000 milliseconds. The default value is 5000 milliseconds.This attribute is applied as a delta to the node timeout for nodes that are in remote sites. That is, the node monitor will wait node_timeout + link_timeout seconds before determining that a remote node is DOWN. Then, it will wait an additional node_down_delay seconds before posting that the remote node is DOWN. The valid range is 1-30 seconds. The default value is 10 seconds.The hb_src_lan, hb_src_san and hb_src_disk attributes together define the set of heart beating sources that must be evaluated by the node monitor for the purposes of declaring a node as DOWN. Values are defined as: -1 Enabled but not used in the calculation 0 Disabled 1-3 Enabled with priority Enabled with priority is a way of prioritizing heartbeat paths themselves. For example, if hb_src_lan=1, hb_src_san=2, and hb_src_disk=3, then heartbeats are sent across LAN until it fails, then SAN until it fails, then disk.This attribute controls the behavior of the deadman timer. The interval associated with this timer is the node_timeout attribute. When the value is set to 'assert', the node will crash when the deadman timer expires. When the value is set to 'event', an AHAFS event is generated.This attribute has values of 'assert' or 'event'. When the value is set to 'assert', the node will crash upon losing access to the cluster repository. When the value is set to 'event', an AHAFS event is generated.This attribute sets the order in which LAN and WAN based network interfaces are used for cluster communications. A value of 0 restricts the interface. Network interfaces with the same priority are used equally. Network interfaces with different priorities are ordered in a failover mode. For example, setting all of the interfaces to a priority of 1 has the effect of all LANs being used for communications. If each network interface has different values (for example en0 is 1, en1 is 2, en2 is 3), then the network interface with the lowest value is used first. Upon this interface failing, all communications are moved to the interface with the next lowest priority value, and so on.This attribute determines the behavior after a site fails or becomes unreachable. If the attribute is set to 'event', Cluster Aware AIX generates an AHAFS Link DOWN event, and it is the responsibility of higher level cluster management software to manage the recovery. At this time 'event' is the only value that is allowed. Other values may be supported in the future.This attribute determines the behavior after a site comes back online after a site failure or becomes reachable again after a site network outage. If the attribute is set to 'event', Cluster Aware AIX generates an AHAFS Link UP event, and it is the responsibility of higher level cluster management software to manage the recovery. If 'auto' is set, Cluster Aware AIX does as much as it can and potentially fails.Cluster configuration timeout interval (seconds)Cluster node down delay interval (milliseconds)Cluster node timeout interval (milliseconds)Cluster link timeout interval (milliseconds)Cluster LAN heartbeat priorityCluster SAN heartbeat priorityCluster disk heartbeat priorityCluster deadman timer modeCluster repository modeCluster network interface priorityCluster site down modeCluster site up mode