Configuring the network parameters from the vSphere console

Last Updated : Jun 10, 2026 |

Before you begin

  • Deploy the System Manager virtual machine OVA.

  • Start the System Manager virtual machine.

    If the Power on after deployment check box is clear during deployment, you must manually start the virtual machine.

  • To reach the System Manager command-line interface, start vSphere Web Client and click the Console tab or the icon.

About this task

When first started, System Manager virtual machine collects the network parameters. Enter the network parameters at the system prompt when first started.

Procedure

  1. At the prompt, enter the management network parameters, public network parameters, virtual FQDN parameters, SMGR CLI User parameters, and SNMPv3 parameters of the System Manager virtual machine.

    For information about the configuration and network parameters, see VM Deployment field descriptions.

  2. To schedule the remote backup during the System Manager installation, in Schedule SMGR Backup, type the backup definition parameters for the System Manager virtual machine.

    For information, see Backup Definition parameters.

    If you do not schedule a System Manager backup every 7 days, System Manager generates an alarm.

  3. At the Data Encryption prompt, perform one of the following:

    • To enable data encryption, type 1.

    • To disable data encryption, type 2.

  4. At the Enhanced Access Security Gateway (EASG) prompt, read the following messages, and do one of the following:

    Enable: (Recommended)

    By enabling Avaya Logins you are granting Avaya access to your system.
This is necessary to maximize the performance and value of your Avaya support entitlements, allowing Avaya to resolve product issues in a timely manner.
In addition to enabling the Avaya Logins, this product should be registered with Avaya and technically onboarded for remote connectivity and alarming. Please see the Avaya support site (support.avaya.com/registration) for additional information for registering products and establishing remote access and alarming.

    Disable:

    By disabling Avaya Logins you are preventing Avaya access to your system. 
This is not recommended, as it impacts Avaya’s ability to provide support for the product. Unless the customer is well versed in managing the product themselves, Avaya Logins should not be disabled.

    • Select 1 to enable EASG.

    • Select 2 to disable EASG.

    Avaya recommends that you enable EASG.

    You can also enable EASG after deploying or upgrading the application using the command: EASGManage --enableEASG.

  5. To confirm the network parameters, type Y.

    System Manager starts the configuration of the network parameters.

    From the time you power on the system, the deployment process takes about 30–40 minutes to complete. Do not reboot the system until the configuration is complete. You can monitor the post deployment configuration from the /var/log/Avaya/PostDeployLogs/post_install_sp.log file. Once the configuration is complete, the log file displays the following message: SMGR Post installation configuration is completed

Next Steps

To verify that the System Manager installation is complete and the system is ready for patch deployment, do one of the following:

  • On the web browser, type https://<Fully Qualified Domain Name>/SMGR, and ensure that the system displays the System Manager Log on page.

    The system displays the message: Installation of latest System Manager patch is mandatory.

  • On the Command Line Interface, log on to the System Manager console, and verify that the system does not display the message: Maintenance: SMGR Post installation configuration is In-Progress.

    It should only display the message: Installation of latest System Manager patch is mandatory.