cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
3320
Views
5
Helpful
8
Replies

mode border-element license capacity

aalejo
Level 5
Level 5

Hi

 

Does "mode border-element license capacity" enforce maximum numbers of call on CUBE?

 

Thanks

Alex

 

 

 


 

 

 

8 Replies 8

Manish Gogna
Cisco Employee
Cisco Employee

Hi Alex,

This command configures the number of licenses (capacity) to be enabled for the CUBE. As per the CUBE licensing structure it will affect the number of calls supported as well

Two types of Cisco Unified Border Element licenses are available:

  • Pay-as-You-Grow (or session count) license—This type of license covers the right to use the feature as well as the maximum session count allowed. An example is the FL-CUBE-25 license, which allows up to 25 sessions. This license is designed to allow a specific number of sessions (or calls) on a platform. Purchase only as many sessions as are required in your deployment. You can add more licenses later as your needs expand, thus offering pay-as-you-grow benefits. Session licenses are stackable. These licenses are available on select platforms as shown in Table 1 in the section CUBE Licenses, and are available on all software images. Examples include the FL-CUBE-4 and FL-CUBEE-100 licenses.

  • Platform (or flat) license—This type of license covers the right to use the feature up to the maximum session count supported on the chosen platform. An example is the FL-INTVVSRV-2811 license, which allows the maximum number of sessions the Cisco 2811 platform supports. These licenses are available on select platforms as given in Table 1 in the section CUBE Licenses. Examples include the FL-INTVVSRV-2801 and FL-GK-3945 licenses.

HTH

Manish

Hi Manish

 

That's what i believed as well but on a CUBE configured for 250 session , I was able to route 428 SIP calls  (856 SIP call legs).

 

Alex

Hi Alex,

Thanks for bringing this up. I did some more digging into this and found the following info. The licenses are honor-based , ie , we get paper licenses from the licensing team and the number of sessions need to be entered using "mode border-element license capacity" command.

The actual number of sessions depends on the platform and is not dependent on the sessions configured, but it is expected that we obtain the paper licenses  for the number of sessions we intend to use.

You may open a TAC case to get a confirmation as well.

HTH

Manish

Hi Manish

 

Thank you for your quick response and research. It is really difficult to get such quick help this days on the forum. :)

A few comments:

Then , what is the purpose to have a commands that does nothing and not even enforce a value?

 

I understand that currently these licenses are paper only (like CME/SRST) but, as CME, I would expect that they get enforce by command.

 

Our  design opted to not overload a single CUBE and we have multiples CUBE for that purpose. This limitation makes enforcing sessions more difficult, A few workarounds are possible, i know, but not a real session limitation command as I was expecting.

 

Regards

Alex

 

 

 

Hi Alex,

Those are valid points. You may open a TAC case to get clarity on this.

Manish

I have a CUBE(2951) built for SIP trunk connected to an ITSP. We did buy 2951 with a 25 license that came with the CUBE bundle and an additional 25. All I wanted to make sure is whether I have 50 licensed capacity or is it just honorary such that I could carry the maximum 500 sessions allowed for this platform.

Could the experts clarify and help me ? 

Thanks, Saravan

At this point in time the ISRG2 platform CUBE sessions are not enforced, they are based on the honor system.

Being that they are based on the honor system it would be up to you to enforce the amount of sessions in use. You can do this on the dial-peer level if needed with the "max-conn" command.

I'm trying to configure CUBE in my Lab on router 3845, I am unable to get the command 'mode border-element' under 'vocie service voip', IOS on the router is c3845-adventerprisek9_ivs-mz.151-4.M10.bin.