Session Manager

[wpetilli]

I had moved a current SM to a new SMGR for testing and successfully established trust and now want to move it back to the original SMGR, where the other production SM's are linked to. Before running the initTM command I want to make sure anything I do with this SM doesn't affect the other SM's in the cluster. Do these operate independently until you create entity links? I want to avoid any issue with certificates. Also, re-setting the enrollment password only matters for anything new being linked and not current SM's?

 

[kyle555]

Yes to all of it. Except, they are not independent until links are created. Look at the port matrix, Jgroups on 7800/7801-2-3 is something all core SMs on a SMGR use to keep track of real time state between one another. Like if location "my house" has max bw 1Mbps and I have 10 phones on SM1 in that location using 1Mbps, it's the stuff that lets SM2 know an 11th phone on him can't place a call because it would exceed that 1 Mbps

CLI into a SM and smconsole get jgroupinfo (or jgroupsinfo, can't remember) and you'll see what i mean. Just enrolling in the cluster causes that participation.

Very weird things can happen if 1 SM isn't playing with that nicely. Like 1 and 2 and 3 can all reach other as well as 4, but 4 can't reach 2 or 3. They lose track of things and can act unpredictably.

 

[wpetilli]

Got it -
Hypothetically, what would happen if a cluster of SM's were using the demo certs and a new one was brought in and used non-demo certs?

 

[kyle555]

tls links between them would not work.
Demo certs is only out to the SIP trunks. all mgmt stuff/drs/presumably jgroups is still with the cert the SMGR signed for the SMs