Because the GroupWise® 6.5 Monitor currently runs on Windows NT*/2000, rather than NetWare®, you cannot run GroupWise Monitor in a cluster. However, GroupWise Monitor can easily monitor a clustered GroupWise system from a vantage point outside the cluster.
When you first install Monitor, it gathers information about agents to monitor from a domain database (wpdomain.db). This provides the secondary IP address of each agent (the IP address associated with the cluster-enabled volume where the agent's domain or post office resides). When an agent fails over or migrates to a different node, its status in Monitor displays as Not Listening until it is up and running again, at which time its status returns to Normal.
Because Monitor must use secondary IP addresses to monitor the agents in a clustered GroupWise system, the Discover Machine and Discover Network options do not work in a cluster. Secondary IP addresses cannot be obtained by examining the network itself. If you need to add agents to monitor, use the Add Agent option and provide the agent's secondary IP address.
For instructions on setting up GroupWise Monitor, see "Installing GroupWise Monitor" in the GroupWise 6.5 Installation Guide.