After implementation, Avaya Aura® Session Manager (SM) replication status is Not Polling, and both replica nodes are not reachable. The network connectivity has been verified, although Avaya Aura®…

Question

Options

• AAvaya Aura® Session Manager (SM)
• BAvaya Aura® System Manager (SMGR)
• CAvaya Aura® Communication Manager (CM)
• DAvaya Aura® Utility Server (US)

• A
  65% (15)
• B
  22% (5)
• C
  9% (2)
• D
  4% (1)

Explanation

Option A is correct because the evidence systematically eliminates everything else: network connectivity is confirmed working, and SMGR can successfully reach other components - meaning SMGR (B) and the network path are both functional. The fault is isolated to Session Manager itself, since it alone is unreachable and its replication status shows "Not Polling," indicating SM's services or configuration are the problem. B (SMGR) is wrong because SMGR is demonstrably working - it connects to other components without issue. C (CM) is wrong because Communication Manager isn't referenced in the symptom at all; the issue is specifically about SM replication and SMGR-to-SM connectivity. D (Utility Server) is wrong for the same reason - there are no symptoms pointing to the Utility Server.

Memory tip: Use the process-of-elimination rule - "What CAN still reach things? Rule it out." SMGR connects to everything except SM, so SM is the odd one out. When replication says "Not Polling," think of it as SM going silent - the listener (SM) is the problem, not the caller (SMGR).

No community discussion yet for this question.