I finally got to look into this yet.
Peering alert was introduced in OCPM 4.1 for MCC.
Functional spec for 4.1 states to possible conditions
Cluster peer
Check that cluster peer is available: "unavailable" , "available" ,"partial" , "pending"
Cluster Peer Status Monitor
20100 - OK - Cluster Peer status is good. -> Equates to Cluster Peer is "available"
20102 - Critical- Cluster Peer status is bad -> Equates to Cluster Peer is "unavailable" , "available" ,"partial" , "pending"
mva-mcc2-3250-a1_SiteA::security login role> cluster peer show
Peer Cluster Name Cluster Serial Number Availability Authentication
------------------------- --------------------- -------------- --------------
mva-mcc2-3250-b1_SiteB 1-80-000011 Available ok
I filed a burt to address this:
BURT: New bug 955446 [3B] - "Knowledge Text for Cluster Peer Monitor needs explain what a critical state means and how to resolve it."
Knowledge Text for Cluster Peer Monitor needs improvment.
It to explain what a critical state means and how to resolve it.
Right now it is just the generic template:
---------------- Knowledge text --------------------------------------
Summary
The Cluster Peer Monitor monitors the OnCommand event log for events generated by the Cluster Peer State Monitoring Rule and generates corresponding Operations Manager alerts.
Here is info form the functional spec and from the cDOT CLI: