We currently have two seperate Mag 2600's which are not in a cluster, is it possible to cluster the two units and not lose any configuration? Presently we manually mirror the configuration each time there is a change.
Once the devices are clustered, can we share our existing licenses in a pool? We currently have 50 per site and would like to combine that as a shared pool, is this possible?
Is there a way to automatically transfer a user who logs into a site which has reached it's license capacity without having the user authenticate twice into the web portal?
After a site has reached it's license capacity, how long does it take for the device to notify the end user the licenses have been consumed?
If we ever decide to lease licenses, how does this feature work?
Solved! Go to Solution.
If you have two boxes - each with an "Add 50" users license - you can cluster them and have a total of 100 available licenses. If you break the cluster then you will again have two boxes with 50 licenses each. Clustering gives you the shared configuration with no need to update individual boxes.
When you have a cluster you essentially have "one" box. An active / passive cluster truely has one box up while an active / active cluster has two boxes with a load balancer pushing users as desired. As it is one virtual box you don't have to worry about licensing until you get to the user who will be over your licensed capacity (in your case 100) That user will receive a license warning message. As will the next "X" users up to a 10% limit of your license capacity. After that any user trying to login will be denied access and receive a license exceeded error message.
Hope this helps.
If you have a cluster with two devices and 50 licenses per unit (total of 100) and one of the devices dies, do you go back to only having 50 available licenses? My concern is that if one dies, and the licenses do not shift to the working device in the cluster, how can I move them off, etc.?
And this is true even in an active/passive cluster? 50 licenses/50 licenses = 100 concurrent users. In case of one node failing you have 10 days to replace the failed node and still fully utilize the 100 (50/50) concurrent user licenses?