https://worldofeuc.com logo
Join Slack
Powered by
This message was deleted.
# citrix-netscaler
s
This message was deleted.
b
Ela2 is a purchase discount level
Has nothing to do with the amount of capacity you buy
m
right, I have no idea what any of the numbers mean because a google search just takes me to a page for someone like cdw with no useful info on it
I have no idea how to find out what a 3021934-E2 is
b
Sounds like they gave you an incomplete quote with just SKU numbers and no description
m
yeah, I’m going it over it with them tomorrow
trying to find out if it limits instances as well as bandwidth
b
Looked licensing is either vcpu or bandwidth. Not both
m
so you get unlimited instances up to the amount of bandwidth you buy?
or limited by the minimum rather
b
Correct. So if you buy 20gb that can be 20 1gb instances or 100 200mb or however you want to cut it
m
ok cool, I gues I just need to work out what number we bought, and what edition
b
But keep in mind that some of the vpxs can only go up to so much bandwidth because of number of packet engine cpus. So you aren’t going to use a single 10gb vpx
m
right, we are upgrading our sdx licenses and have a couple of vpx on esx as well
b
Ahhh six licensing is a bit different in that I believe you license the instance itself and it does not use pooled capacity
m
the image at the end shows instance and bandwidth
for pooled
so I’m confused
I haven’t done a lot of sdx or pooled licensing before
b
I guess you can do pooled capacity on SDX. I’ve not done much with SDX. We are doing pooled capacity vCpu licenses for vpx in azure
m
ah ok
p
yes, you can do pooled on any VPX instance whether it is on SDX or VPX installed on prem or cloud, the licenses are installed on the MAS server and managed centrally for all instances. There are two types of pooled licenses, pooled vCPU and Pooled bandwidth but both operate similarly in you carve up that pool in multiple big or little instances based on the sizes you need. All pooled licensing to my knowledge is based on Premium
c
OK, there's a bit of confusion here.
vCPU based licensing effectively removes bandwidth as a restriction. You get a pool of 40 Premium vCPUs for example, and that means you can create as many Premium licensed ADCs as you want by checking out vCPU licenses from the central pool, subject to the minimums and maximums of the VPX platform. vCPU does not work on any of the physical ADC platforms, just VPX/CPX/BLX. If you are a totally virtualized environment and don't have appliances then this is usually the best way to go. License level follows the vCPU pool, you can have Premium/Standard/Advanced vCPU pools.
"Traditional" pooled licensing instead provides a pool of bandwidth and a pool of instances that you can check out and create ADCs from. For example, you may get a starter pool that has 20 instances and 20Gbit of Premium edition throughput. When you license an ADC, you generally check out an instance license and the amount of bandwidth you want to allocate to that instance. Performance scales based on the amount of bandwidth assigned, and the feature set is tied to the bandwidth pool (i.e. you can have Standard/Advanced/Premium bandwidth pools which are independently tracked).
👍 1
"Traditional" pooled licensing can be used in conjunction with zero capacity hardware as well as software. SDX, VPX and CPX platforms check out instance licenses and bandwidth, MPX and BLX platforms just check out bandwidth. You can also convert existing perpetual licenses to "traditional" pooled capacity. If you want to be able to move instances around between hardware/software/cloud then this is the model you'd want.
3 Views
Open in Slack
PreviousNext
Powered by