- CheckMates
- :
- Products
- :
- CloudMates Products
- :
- Cloud Network Security
- :
- Discussion
- :
- vSEC license confused
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Are you a member of CheckMates?
×- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
vSEC license confused
Hi guys,
I recently deploy a environment in Azure,to my luck,the environment works fine.
but one thing:
the Azure GWs managed by a SMS located in non-cloud DC.and this SMS also managed 4 AWS gateways,then AWS have a 72-cores license but it just used 64 cores remaining 8 cores in that pool.
And now,I have a 64 seats license for Azure.but when I use "vsec_central_license" in SMS to attach license for Azure gateways,but it seems the SMC attached the 72-cores license to them.
but the AWS gateways also have license now.
Have any ways to modify the license attaching to vSEC gateways?
Thanks!
- Tags:
- licensing
- vsec azure
Leaderboard
Epsum factorial non deposit quid pro quo hic escorol.
User | Count |
---|---|
2 | |
2 | |
1 | |
1 | |
1 |
Thu 09 May 2024 @ 05:00 PM (CEST)
Under the Hood: Automate Azure Virtual WAN security deployments with Terraform