Smart Plug-in for WebLogic Server Reference Guide

Chapter 1
Metric B081_ClsInMesFailRt
1-67
Metric B081_ClsInMesFailRt
Monitor Template Name WLSSPI_0081
Metric Name Cluster Incoming Message Failure Rate
Metric Type Alarming, Graphing
Description Number of multicast messages per minute from cluster lost by server.
WebLogic 6.0/6.1 or Both Both
Severity: Condition Minor: WLSSPI-0081.1, threshold 1
Collection Interval 5m
Message Group WebLogic
Message Text WLSSPI-0081.1: # of multicast messages from cluster lost by server
(<$VALUE>/min) too high (>=<$THRESHOLD>/min)
Instruction Text The number of multicast messages from the cluster that were lost by the server
has exceeded the threshold value.
Probable cause: This could be caused by the cluster configuration or the
network topology.
Potential impact: Potential loss of critical data.
Suggested action: Because multicast controls critical functions related to
detecting failures and maintaining the cluster-wide JNDI tree, it is important that
neither the cluster configuration nor the basic network topology interfere with
multicast communication. Always consider the following rules when
configuring or planning a WebLogic Server cluster.
For most deployments, limiting clustered servers to a single subnet ensures that
multicast messages are reliably transmitted. In special cases, however, you may
want to distribute a WebLogic Server cluster across subnets in a Wide Area
Network (WAN). This may be desirable to increase redundancy in a clustered
deployment, or to distribute clustered instances over a larger geographical area.