Session Manager Profile Change. 1

[RedTech443]

Is it possible to change a Session Manager profile from 1 to a higher number like 4 or 5? I am running SM 8.1 and can only deploy as Profile 1 for now due to VM resource limits, later down the road I need to increase to profile 4 or 5 to support 12k+ SIP endpoints. I am being told it is possible but cannot find any documentation anywhere on how to do it other then changing the VM resources manually. I am sure I need to edit SM to know it is using the new profile as well.


Local Instance Name: ASM100
Local Management Host: 10.1.30.14
Local Security Module: 10.1.30.15
Local SIP State: Allow New SIP
Local FQDN: LAB-SM.lab.net
Local Netmask: 255.255.255.0
Local Gateway: 10.1.30.1
Local Timezone: America/New_York (EDT, -0400)
Local Date/Time: Mon Apr 13 12:18:58 EDT 2020
Local NTP Servers: 10.99.99.99,time.nist.gov
Local DNS Servers: 10.1.30.1
Local Search List: lab.net
SELinux: Enforcing
Hypervisor: VMware
Profile: SM Profile 1 Max Devices 2,000

No other Session Managers provisioned!

Avaya Aura Session Manager Software Version Inventory

Application Name: Session Manager
Release: 8.1.0.0.810007
Patches:

ID Version Status Summary
--------------------- -------------- --------- --------------------------------
8.1-SSP-005 005 installed Security Service Pack

Call Processing: 8.1.0.0.810007
Management: 8.1.0.0.810007
SM Tools: 8.1.0.0.810007
DRS: 8.1.0.0.810007
CDR: 8.1.0.0.810007
NCS: 7.65.19
Security Module: 8.1.0.0.810001
nginx: 1.14.0
Firewall: 8.1.0.0.810001
WebSphere AS: 9.0.0.6
SAL Agent: 8.1.0.0.7
PostgreSQL: 9.6.1
Cassandra: 3.11.3
VMware Tools: 10.2.5.3619 (build-8068406)
Application Deployment: Virtual Machine
Virtualization Environment: VMware
Current Application Size: SM Profile 1 Max Devices 2,000
OS: Red Hat Linux Release 7.6 (Maipo)

[cust@LAB-SM bin]$

 

[kyle555]

On VMware:

https://downloads.avaya.com/css/P8/documents/101058176

P49

On AVP:

https://downloads.avaya.com/css/P8/documents/101058246

You just click the VM, edit, and "change flexi footprint" is an option.

 

[RedTech443]

As always thanks Kyle.


I did hear this was one of the ways for VMware, however. I tested this in my lab and simply chaning the VM settings does not update the profile in SM, it still reports as profile 1 even though I increased the settings. I was wondering if there was also something that needed to be changed in SM to show / know it is on a new profile settings..

 

[RedTech443]

Update:
I went over the settings again, changed all the requirements for the VM settings to exactly what each profile would need, then powered back on. The profile would then show the correct profile # automatically. Problem solved.