This process monitor watches for the rpcbind service to be running.
A failure indicates that the rpcbind service is down (possibly due to a corrupt network configuration db).
Check the service on the system by running ps -ef | grep rpcbind or by viewing the diagnostic in the Operations Manager Console. If it is down, you can start the service by using the command '/etc/init.d/rpc start' or by clicking the recovery link in the Operations Manager Console. If rpcbind fails to start, other rpc services may need to be started prior. Verify and recover any other rpc alerts.
For root cause analysis, first check the system logfile (/var/adm/messages), and view any related entries at the time of failure. You may also check the system for any process core files. Use '/usr/bin/pstack [corefile]' to print a stack trace which will assist in troubleshooting the cause of failure.