Avaya Aura Messaging [AAM] 6.3: “Cluster topology mismatch has been detected” Alarm – Event Code 47

Doc ID    SOLN245763
Version:    5.0
Status:    Published
Published date:    17 May 2022
Created Date:    26 Feb 2014
Author:   
Steven Daniel
 

Details

 

Alarm Description – This alarm condition indicates that a cluster topology mismatch has been detected with the Avaya Aura Messaging application server.3
 
Alarm Details
 
Alarm Type
Alarm Name
Event Code
Alarm Severity
Alarm String
SNMP INADS
MANGO047
47
Major
MANGO047:0:X:X:X:MANGO:47:MAJ::"Cluster topology mismatch has been detected"

 

Problem Clarification

This alarm will be generated when application servers in a cluster cannot communicate with other clustered members thus causing voicemail retrieval issues

Cause

Causes for this alarm may include:

  • Cluster configuration issue
  • Topology configuration issue

 

Solution

To resolve this alarm please follow/execute the steps outlined below:

 

  1. Verify the cluster configuration on all application servers
  2. Verify the topology on the storage server
  3. Perform ping test on all AAM servers to validate network connectivity

If all matches & operational, the alarm can be manually cleared by a Backbone engineer - Please contact Avaya for assistance.

 

 

Additional Relevant Phrases

MANGO:47:MAJ alarm

Avaya -- Proprietary. Use pursuant to the terms of your signed agreement or Avaya policy