Usage is like:
network-stats-collector-3-strombrg> rpc-health localhost Program 100000/portmapper, Proto tcp, Version 2 is OK Program 100000/portmapper, Proto udp, Version 2 is OK Program 100021/nlockmgr, Proto udp, Version 1 is OK Program 100021/nlockmgr, Proto udp, Version 3 is OK Program 100021/nlockmgr, Proto udp, Version 4 is OK Program 100021/nlockmgr, Proto tcp, Version 1 is OK Program 100021/nlockmgr, Proto tcp, Version 3 is OK Program 100021/nlockmgr, Proto tcp, Version 4 is OK Program 100024/status, Proto udp, Version 1 is OK Program 100024/status, Proto tcp, Version 1 is OK Program 100004/ypserv, Proto udp, Version 2 is OK Program 100004/ypserv, Proto udp, Version 1 is OK Program 100004/ypserv, Proto tcp, Version 2 is OK Program 100004/ypserv, Proto tcp, Version 1 is OK Program 100007/ypbind, Proto udp, Version 2 is OK Program 100007/ypbind, Proto udp, Version 1 is OK Program 100007/ypbind, Proto tcp, Version 2 is OK Program 100007/ypbind, Proto tcp, Version 1 is OK Program 391002/sgi_fam, Proto tcp, Version 2 is BAD Program 390113/nsrexecd, Proto tcp, Version 1 is OKI'd guess you can see that all of the registered services on this host are checking out OK, except for sgi_fam. What rpc-health is doing is enumerating all of the services registered on the specified host, and then it does what you can think of as an "RPC ping" for each service, to make sure that it is at least responding to minimal requests.
You can e-mail the author with questions or comments: