When observing the Session Manager dashboard, you notice that one entity is marked as down. Which two troubleshooting tools can be used to investigate the problem? (Choose two.)

Question

Options

• AList trace station on Avaya Aura® Communication Manager
• Bstatapp on the Command Line Interface of Avaya Aura® Session Manager
• CtraceSM on the Command Line Interface of Avaya Aura® Session Manager
• Dthe replication page in Avaya Aura® System Manager
• EAvaya Aura® Session Manager Entity Link Connection Status page in Avaya Aura® System

• A
  6% (3)
• B
  2% (1)
• C
  80% (39)
• D
  12% (6)

Explanation

traceSM (C) is a CLI diagnostic tool built specifically for Session Manager that captures SIP signaling and entity link status in real time, making it ideal for pinpointing why an entity is down. The Entity Link Connection Status page (E) in System Manager provides a direct visual view of SIP entity link states, showing whether connections are active, failed, or unreachable - exactly what you need when an entity shows as down on the dashboard.

Why the distractors are wrong:

• A (List trace station on Communication Manager): This traces station/endpoint activity on CM, not Session Manager entity links - wrong tool, wrong layer.
• B (statapp on Session Manager CLI): statapp monitors application process health (JVM, memory, etc.), not SIP entity connectivity.
• D (Replication page in System Manager): The replication page checks data synchronization between System Manager and Session Manager, not entity link or SIP connectivity status.

Memory tip: Think "Check the CLI with traceSM, and Examine Entity Links in the GUI." Both tools target the SIP connection between Session Manager and the entity - one from the command line, one from the web dashboard. If a question asks about an entity being down, focus on SIP-layer tools, not replication or station tracing.

No community discussion yet for this question.