New 7.0 Feature: Virtual Appliance – Service Provider Edition (SPE)

IVE 7.0, Virtual Appliance

Right along with the DTE version of the virtual appliances lies the Service Provider Edition (SPE).  The major differences between the two include…

  • Licensing: Unlike the DTE version, each SPE can increase its licensing, provided it gets its licenses from the required license server.  And because the SPE is targeted at service providers (and to major accounts that operate in a similar fashion for various business units), the minimum license offered is 2500 concurrent users, which can then be spread out across as many virtual appliances as you like.
  • Installation Scripts: Inside the download package there are scripts included to help service providers bulk configure virtual appliances.
  • Support: The SPE is actually supported by JTAC.  But  before you get too excited, note that you have to be an existing SPE customer, meaning you have the required minimum number of licenses as well as a license server that is under a support contract. 
3 Comments

3 Comments

  1. Chris  •  Aug 26, 2010 @5:45 am

    Hi Kevin,

    Currently using a SAVA SPE on ESX, it is clear that this product is supported on ESX infrastructure but i couldn’t find any statement on the support of the SAVA on ESXi infrastructure. I would think that there is not a problem as such, but would like a confirmation that we will not encounter any obstacles running our SAVA on ESXi.
    Would you be in a position to state that the Juniper SAVA is fully compatible on ESXi?

    Thanks for your blog
    Chris

  2. KevinPeterson  •  Aug 26, 2010 @8:18 pm

    There is no doubt that it will run on ESXi. But…at least right now all we can sign up to support is VSphere 4.X/ESX4.0, as the QA commitement just to fully qualify that release is burdensome enough and we can’t afford to dilute that supportability.

    Of course, that might not even be a concern to you or others, as virtualization — almost by definition — is designed to give you the flexibility to in various virtualized configurations without having to worry nearly as much about the a potential support black hole. So, at lease in pilot and smaller scale deployments, I would not see a big risk to anyone running this particular configuration. In fact, I readily welcome the endeavor and the wish anyone going this route the best of luck. Please just keep in mind that the official support line is that we can only support things to the hypervisor itself and our reference architecture is currently running VSphere 4.0/ESX4.0.

    Bottom line: If you want the best possible support experience from Juniper, stick as close as you can to the reference architecture (what Juniper QA runs). With any other configurations, just run them within your own comfort level and beg me for held whenever you need to. :-)

    I’m sure any open questions on ESXi will likely be answered by others here as well.

  3. Chris  •  Aug 31, 2010 @4:17 am

    Kevin,
    Thanks for your prompt reply.

Leave a Reply

Allowed tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

Get Adobe Flash playerPlugin by wpburn.com wordpress themes