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

Question

Options

• AAdd SM as an Instance.
• BAdd SM as a Serviceability Agent.
• CAdd SM as a Managed Element.
• DCheck the Enable box on the SM Entity page.

• A
  6% (2)
• B
  3% (1)
• C
  91% (31)

Explanation

Adding Session Manager as a Managed Element (C) is the required step because Avaya System Manager uses the Managed Element framework to discover, register, and administer network components - without this registration, System Manager has no administrative relationship with the SM and cannot push configurations, certificates, or monitor its health within the SIP Domain.

Why the distractors are wrong:

• A (Instance): "Instance" refers to adding an application instance within a cluster or profile, not the top-level administrative onboarding of SM.
• B (Serviceability Agent): Serviceability Agents are used for SNMP-based monitoring/alarming, not for enabling full administration and maintenance of SM in a SIP Domain.
• D (Enable box on SM Entity page): The Entity page defines SM as a SIP entity for routing purposes - that alone does not grant System Manager the administrative control needed to manage it.

Memory tip: Think "Managed Element = Managed by System Manager." If System Manager is going to manage something end-to-end (administer, maintain, update), that something must first be declared a Managed Element - it's the handshake that brings SM under central control.

No community discussion yet for this question.