 |
|
|
NAME
nhprobed - test accessibility of physical
interfaces
SYNOPSIS
/opt/SUNWcgha/sbin/nhprobed [-h] [-u URL]
Each peer node runs a daemon, nhprobed, that periodically
sends a heartbeat in the form of an IP packet. The nhprobed
daemon sends the heartbeats by multicast.
Heartbeats are sent through each of the two physical interfaces of each
peer node. When a heartbeat is detected through a physical interface, it indicates
that the node is reachable and that the physical interface is alive. If a
heartbeat is not detected for a period of time exceeding the detection delay,
the node or one of its physical interfaces is considered to have failed. If
both of the node's physical interfaces fail, the node itself is considered
to have failed. Heartbeats are broadcast at the rate of 3 per 900 milliseconds,
and at least one heartbeat must be detected each 900 milliseconds.
On the master-eligible nodes, the nhprobed daemon
receives a list of nodes from the nhcmmd daemon. The nhprobed daemon monitors the heartbeats of the nodes on the list.
On the master node, the list contains all of the master-ineligible nodes and
the vice-master node. On the vice-master node, the list contains the master
node only.
On the master-eligible nodes, the nhprobed daemon
notifies the nhcmmd daemon when, for any node on its list,
any of the following events occur:
-
One link becomes available, indicating that the node is accessible
through the link.
-
One link becomes unavailable, indicating that the node is
not accessible through the link.
-
The node becomes available, indicating that the first link
to the node becomes available.
-
The node becomes unavailable, indicating that the last available
link to the node becomes unavailable.
The nhprobed daemon uses a kernel module, hbmod, and a kernel driver, hbdrv. The kernel
module and kernel driver manage the send and receive mechanisms of the nhprobed daemon. Because the kernel module and kernel driver operate
in the kernel space, the nhprobed daemon is more robust
against system overload.
Note The probe heartbeat of the Foundation Services 2.1 is incompatible with that
of the Foundation Services 2.1 6/03. All nodes in a cluster must have the same probe installation.
For information about how to install the packages for the nhprobed daemon, the kernel module and kernel driver, see the Netra High Availability Suite Foundation Services 2.1 6/03 Custom Installation Guide.The nhcmmd daemon and nhprobed
daemon communicate through an Internet socket, AF_INET, in connection oriented
mode. The socket port number can be configured in the /etc/services file, using the service name cmm_cgtp_probe.
The nhprobed daemon takes the following options:
- -h
-
Displays help
information.
- -u URL
-
You must specify the URL of the nhfs.conf
file.
For more information, see the nhfs.conf(4) man page.
The following exit values are returned:
-
0
-
Successful
completion.
-
1
-
An
error occurred.
-
URL
-
Common
configuration file. The file that contains configuration and addressing information
for the individual Foundation Services.
The URL for this file could for example be file:///etc/opt/SUNWcgha/nhfs.conf
See attributes(5)
for descriptions of the following attributes:
ATTRIBUTE TYPE | ATTRIBUTE VALUE |
Architecture | SPARC |
Availability | SUNWnhcmb, SUNWnhhb |
Interface Stability | Evolving |
MT-Level | MT-Safe |
Cancel-Safety | Deferred-Cancel-Safe
Asynchronous-Cancel-Unsafe |
Intro(3CMM), nhcmmd(1M),
and nhfs.conf(4)
Netra HAS FS 2.1 | Go To Top | Last Changed September 2004 |
Company Info
|
Contact
|
Copyright 2004 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
|