For Avaya Aura® System Manager (SMGR) to administer, configure, and maintain a Session Manager (SM), the SM must first be added to the SMGR inventory. This process is known as adding a "Managed Element." This step establishes the secure management and trust relationship between SMGR and the SM instance, enabling SMGR to push configurations, monitor health status, and perform other essential lifecycle management tasks. Without this initial step, SMGR is unaware of the SM's existence and cannot manage it within the SIP domain.

A. Add Session Manager as an Instance.

This is a subsequent step. An "Instance" is created under a Session Manager group after the server has been added as a Managed Element to the System Manager inventory.

B. Check the Enable box on the Session Manager Entity page.

Enabling an entity is an action performed on an already configured element. The fundamental step of making it manageable must occur first.

C. Add Session Manager as a Serviceability Agent.

This configures the Secure Access Link (SAL) Gateway for remote alarming and support access by Avaya services, which is distinct from core administration by System Manager.

1. Avaya Aura® System Manager Documentation: Administering Avaya Aura® System Manager, Release 10.1 (October 2022), Page 389, Section: "Adding a Session Manager managed element". The document states, "Use this procedure to add a Session Manager managed element to the System Manager inventory. You must add Session Manager as a managed element before you can administer Session Manager from System Manager."

2. Avaya Aura® Session Manager Documentation: Deploying Avaya Aura® Session Manager, Release 10.1 (October 2022), Page 101, Section: "Adding Session Manager to System Manager inventory". This section outlines the procedure, which begins with navigating to "Elements > Session Manager > Managed Elements" in the System Manager web interface to add the new Session Manager. This confirms it is a foundational deployment step.