General IAUG Discussion Forum

 View Only
  • 1.  Changing SMGR VM Profile

    Posted 10-05-2020 12:44 PM
    Hi,
    Greetings,

    We are having SMGR 7.1 Appliance Model running on VMWare.
    Recently we started facing issues due to low VM specs (storage and memory) and Avaya has recommended us to migrate from Profile 1 to Profile 2 of same version or Upgrade to SMGR 8.x which is by default on Profile 2.

    We are using SMGR as internal CA and to manage a complete SIP environment of 2000 plus users. Considering this I am skeptical for this activity.
    if anyone has done such migration please share your experience or point to a good document which can be used as a starting point

    ------------------------------
    Arslan Ali
    UC Consultant
    Vodafone
    ------------------------------


  • 2.  RE: Changing SMGR VM Profile

    Posted 05-25-2021 02:02 PM
    Edited by Sam Osheroff 05-25-2021 02:02 PM
    I know not of an official process for changing the SMGR VM profile.   VM memory can be increased very easily.  However, additional disk space beyond the size included in the VM image is only allocated to the various partitions on first-boot of a new SMGR instance, though maybe there's a script that Avaya can provide or run for you to resize the partitions.

    If you're not finding anything useful in the deployment guides for SMGR (I didn't), I'd following a process like this:

    1. Run the SMGR backup to an SFTP/SCP server.
    2. Take note of the existing:
        1. Version (run "swversion" from the CLI) - you'll need to build a new server exactly the same
        2. hostname
        3. host domain
        4. VFQDN (cat /etc/hosts on one of your SMs and look for a line ending in AsmSysMgr1)
        5. IP address/mask/gateway
    3. Shut down the existing SMGR
    4. Deploy a new VM using the correct SMGR template.  Ensure you increase the VMs CPU, memory and disk size before you power it up.
    5. Power it up, open the console and run the base configuration script, using the values above.
    6. Apply all patches to get the new SMGR VM to the exact same version as the old one.
    7. Restore the backup taken earlier via the SMGR web interface (only the default admin login is available until you restore).

    These steps are off the top of my head.  If something goes wrong during the restore, you can power off the new VM and power up the old one.  I definitely invite others to revise/improve my suggested process.

    Another, better documented, option is to change the footprint/profile as part of an upgrade to 8.1.x.   Upgrading from 7.x to 8.x is basically what I outlined above except there is a migration tool that upgrades the database and applies a service pack to the 8.1 base install at the same.  So the last few steps (apply service pack, restore backup) get combined into one step using the migration tool (separate download).   The downside to this method is you should be prepared to upgrade all your SM/BSMs as well, within a short time.  The older SM/BSMs will run on the upgraded SMGR but that's not a long-term advisable configuration.

    ------------------------------
    Sam Osheroff
    UC Engineer
    University of Washington
    ------------------------------