Which step must be performed to enable an Avaya Aura® Session Manager (SM) to be administered and maintained in a SIP Domain?

Question

Options

• AAdd Session Manager as an Instance.
• BCheck the Enable box on the Session Manager Entity page.
• CAdd Session Manager as a Serviceability Agent.
• DAdd Session Manager as a Managed Element.

• A
  4% (1)
• B
  7% (2)
• C
  7% (2)
• D
  81% (22)

Explanation

Adding Session Manager as a Managed Element (D) is the required step because Avaya System Manager must recognize SM as a managed element before it can administer, configure, or maintain it within a SIP Domain - this registration establishes the management relationship between System Manager and Session Manager.

• A is wrong - "Instance" refers to adding Session Manager as an SM instance (defining its runtime role), which is a separate configuration step that comes after establishing it as a managed element.
• B is wrong - The "Enable" checkbox activates an already-configured entity; it cannot work until the management relationship is first established.
• C is wrong - A Serviceability Agent is used for alarm reporting and diagnostics, not for enabling full administration and maintenance capabilities.

Memory tip: Think of "Managed Element" as the front door - you must register SM with System Manager as something it manages before you can do anything else with it. No door = no access.

No community discussion yet for this question.