Learn F5 Technologies, Get Answers & Share Community Solutions Join DevCentral

Filter by:
  • Solution
  • Technology
Answers

What hardware comes with 'Better' and 'Best' Viprion software?

Hello all

As far as I know, Viprion's bundles 'Better' and 'Best' come with a bunch of modules each ('Best'='Better'+APM+ASM); anyway I still have some doubts, such as: - If I purchase a Viprion Chassis 2400 in 'Better' mode, with what kind of hardware will it come? How many blades will come with the chassis? - If I purchase a Viprion Chassis 2400 in 'Best' mode, with what kind of hardware will it come? How many blades will come with the chassis? - What happens with the other two models (4480 and 4800)? These are bigger chassis... would they come with more blades?

Please advise

0
Rate this Question

Answers to this Question

placeholder+image
USER ACCEPTED ANSWER & F5 ACCEPTED ANSWER

I believe you get as many blades as you actually buy. The software bundles, are just that. Software. Not hardware...

H

0
placeholder+image
USER ACCEPTED ANSWER & F5 ACCEPTED ANSWER

Hi,

As Hamish said, Better and Best are licence bundles.
So even if you buy one of them, it's not linked to hardware.

With Viprion it's not the chassis itself which runs modules but blades.
So you have to purchase the chassis and then on a blade buy the Best bundle for example.

0
placeholder+image
USER ACCEPTED ANSWER & F5 ACCEPTED ANSWER

Hello again,

So, according to you guys, the total price if I want Viprion chassis 2400 in Best bundle, for example, would consist in the result of adding the following prices: - The price of the 2400 chassis - The price of the blade (or blades) that will come with the chassis - The price of the 'Best' bundle, in this case would be US$ 84995

Now, the question would be: how many modules can a single blade support? There must be a sizing criteria for determining the ammount of blades that are ought to be bought... am I right?

PS: Thanks Hamish and Thomas for your explanation, if you can help me with this other question that would be great!!

0
placeholder+image
USER ACCEPTED ANSWER & F5 ACCEPTED ANSWER

With your blades you'll be able to run every modules at the same time.
A best bundle can be handle by a Big-IP or a blade as soon as it has 8 Gb of RAM.

0
placeholder+image
USER ACCEPTED ANSWER & F5 ACCEPTED ANSWER

Note that various combinations of modules require certain amounts of memory. more modules == more memory required. And some modules can't be provisioned together.

I'd get the biggest badest blades I could afford (2250's please) and as many of them as possible...

The biggest issue we've had is memory on the original 2100 blades. 2250's have 64GB (Versus 16GB on the 2100) and more cores... Mmmm... I could wish for finer grained allocations (e.g. Like VMWare or rolling the KVM's yourself :) ), but not sure I'll ever get that wish.

H

0
placeholder+image
USER ACCEPTED ANSWER & F5 ACCEPTED ANSWER

Thank you guys for your answers!!

I've been doing some research, and got this until now: There are two ways to use Viprion appliance, which are:

  1. Using the chassis with its blades, so I should purchase a bundle for each blade... in this scenario, each blade would work as a single super BIG-IP.

  2. Using VCMP licenses; in this scenario, the VCMP license would work for the whole chassis, and it would work as an Hypervisor, so there would not be a separation among the blades... I could configure a number of virtual machines, which would be provisioned among the blades that are installed the chassis.

What other information is needed? What else shall I have in mind about this whole Viprion matter?? Please advise... and thanks for all your help, guys!!

0
placeholder+image
USER ACCEPTED ANSWER & F5 ACCEPTED ANSWER

Your #1 is news to me; for I thought licences were tied to the chassis for the Viprions, not to individual blades. You pay the same licence fee no matter how many blades there are in the chassis. Will somebody verify this?

0
placeholder+image
USER ACCEPTED ANSWER & F5 ACCEPTED ANSWER

Licences on Viprions are linked to blades not chassis, Marcos is right.
Maybe you "only" knew the second point Marcos talked about.

0
placeholder+image
USER ACCEPTED ANSWER & F5 ACCEPTED ANSWER

Sorry Thomas, but licenses on Viprions are indeed tied to the CHASSIS. Not the Blade. Every blade and every vCMP guest you have gets the same license inherited from the host.

H

0
placeholder+image
USER ACCEPTED ANSWER & F5 ACCEPTED ANSWER

I think I said and understood something wrong...
Hamish you're right in fact, what I wanted to know is on each blade you can have different modules activated.
It's the same for each instance when you use vCMP.

Sorry about that, I'll be more careful on my next posts.

0
placeholder+image
USER ACCEPTED ANSWER & F5 ACCEPTED ANSWER

Hi everybody

Without the intention of generating any kind of confussion, I'll try to clarify what I said, and please need your feedback, in order to knowing if I am right or just talking nonsense :/

  • About item #1, what I meant is that after paying for one bundle, this license can be put in just one blade (if I want to use another blade in the chassis, I should need to get another license for it)... this way, every blade would work as a single BIG-IP... it doesn't mean at all that I can purchase one bundle's license and use it amongst all the blades I have in the chassis... if we want to use all the blades with one single license, we shall get the VCMP license for the chassis and then we will be able to attach this bundle license for the whole chassis, so we would be able to provision all modules among all blades we have in the chassis...

Is this right? sorry for insisting so much but I need to have every scenario about this quite clear...

0
placeholder+image
USER ACCEPTED ANSWER & F5 ACCEPTED ANSWER

When you buy the bundle, it's for ALL the blades in the chassis. You don't (Can't in fact I suspect) buy more than one of the same bundle license for a chassis.

I'm not sure you can run individual blades in a chassis as separate images... [Admittedly I've never tried. We use vCMP]. Although they do run a separate copy of Linux, their own tmm's etc, they inherit everything from the existing blades... Right down to the OS installed (When you put a blade into a chassis with a backlevel OS for example, they'll upgrade automatically to the same version as the existing blades and join the cluster)

H

0
placeholder+image
USER ACCEPTED ANSWER & F5 ACCEPTED ANSWER

I think the primary blade will propagate/sync its conf to all of the rest of the blades, and it is a continuous process.

0
placeholder+image
USER ACCEPTED ANSWER & F5 ACCEPTED ANSWER

if this remains unclear for you then contact your local F5 sales, im sure they can explain it fully to you.

0
placeholder+image
USER ACCEPTED ANSWER & F5 ACCEPTED ANSWER

Ok, everything is much clearer.. thank you everybody for your help!!

0