Datasheet

2
Juniper Networks Internal and Partner Use Only – Do Not Distribute
High Availability Clustering Capability (No Additional License Required)
Customers have the ability to build clusters without buying any additional licenses.
The clustering method can be explained in two simple steps:
1) Simply place an equal number of user (“-ADD”) licenses on each box.
2) When they are joined together to form a cluster, all of the user licenses add up so that the cluster can now support all of the
licensed users. For example, building a 1,000-user cluster is done by bringing together two boxes with 500 user licenses in each of
the two units.
Clustering features stateful peering and failover across the LAN so in the unlikely event that one unit fails, system configurations (such
as authentication server, authorization groups, and bookmarks), user profile settings (such as user defined bookmarks and cookies), and
user sessions are preserved. Failover is seamless, so there is no interruption to user/enterprise productivity, no need for users to log in
again, and no downtime.
Here are the clustering options for the MAG Series.
1) MAG2600 can be clustered in a pair.
2) MAG4610 can be clustered in a pair.
3) For MAG6610, you can cluster two service modules in a pair (assuming any two service modules are installed in the chassis, either
the MAG-SM160 or MAG-SM360).
4) For MAG6611, you can cluster two service modules in a pair, either using the MAG-SM160 or MAG-SM360. To cluster three or four
service modules will require the MAG-SM360 service modules in the chassis.
Please note that WAN clustering is not supported on the MAG Series. Multisite clustering is supported, however, provided the sites are on
a campus network with LAN-like connectivity.
Clustering Rules with Regards to Licenses
1) When MAG Series gateways are clustered, you can spread the following licenses evenly across all nodes (to prevent disruptions in
service in the event of a node failure):
• ADD (Concurrent user license)
• EES (Enhanced Endpoint Security license)
• RDP (Premier Java RDP license)
• PRM (Patch Remediation license)
• MTG (Secure Meeting license; these new meeting licenses for MAG Series are stackable and inherently more flexible)
• OAC license
2) Single feature licenses that can be shared across all nodes.
• RADIUS license
• IF-MAP license
• SOH license
3) When gateways are clustered, these licenses must be on every node in the cluster (if used).
• MBR (Member license)
• ICE (In Case of Emergency license)
• ACCESS-ICE-25PC (25% burst license)
4) This license cannot be clustered:
• SVR (License server license)
Feature Licenses (Optional)
Feature licenses enable functionality not available with the standard common access licenses alone.
Secure Meeting (Note that this is different than previous Secure Meeting licensing models.)—The Secure Meeting license enables
Secure Meeting functionality for online collaboration on a single MAG Series gateway or cluster, allowing your customers to conduct
secure online meetings using their MAG Series gateway. For the MAG Series, Secure Meeting is licensed through a concurrent user model.
Secure Meeting supports four license options on the MAG Series, and up to 25, 50, 100, or 250 concurrent “meeting” users options are
offered. Please note that the “meeting” user count is separate from the concurrent SSL VPN users count on the MAG Series. Also, there is
a limit to the maximum number of licenses that can be supported on certain MAG Series models.
• A single MAG2600 will support up to 50 concurrent meeting users.
• A single MAG4610 will support up to 100 concurrent meeting users.
• The MAG-SM160 service module (for MAG6610 or MAG6611 chassis) will support up to 100 concurrent meeting users.
• The MAG-SM360 service module (for MAG6610 or MAG6611 chassis) will support up to 250 concurrent meeting users.