VCS X7.1 Licensing Question (Master and Non-Master Peers)

[john-guy]

Could you please let me know what statement below is correct for VCS Clustering (or possibly both are incorrect?).

Is Example 1 or 2 correct with regards to the License Keys. (The keys are examples)

VCS – Master (Example 1)

• H.323-SIP Internetworking Gateway License 123456
  
• Device Provisioning License 111222333
  
• Non-traversal Calls 555666777
  
• Traversal Calls 999888111
  

VCS – Non-Master Peer (Example 1)

• H.323-SIP Internetworking Gateway License 123456
  
• Device Provisioning License 111222333
  
• Non-traversal Calls 555666777
  
• Traversal Calls 999888111
  

VCS – Master (Example 2)

• H.323-SIP Internetworking Gateway License 123456
  
• Device Provisioning License 111222333
  
• Non-traversal Calls 555666777
  
• Traversal Calls 999888111
  

VCS – Master (Example 2)

• H.323-SIP Internetworking Gateway License 999999999
  
• Device Provisioning License 888888888
  
• Non-traversal Calls 777777777
  
• Traversal Calls 666666666
  

[Martin Koch]

Hello John,

its example two!

The keys itself are always dependend on the VCS and its serial number, so other VCS, other option key!

What is ment here is that the same type of keys are used.

Like in your example the device provisioning.

Other examples would be findme, enhanced collaboration, dual interface option, ... they have to exist

on all vcs in the cluster.

If such a key is only present on one and you would like to use this feature you need to purchase/add the feature

on the ones in the cluster which lack them or remove them from all if the feature is not needed.

On older VCS releases you also had to have the same amount of call licenses (they are Traversal, local (non-traversal), turn) on both VCS. Like if you had 10 on the first one, it was required to have 10 on the other one

as well, now it could be 10 vs. 0

[Tomonori Taniguchi]

Martin already explain well on this.

To be clear, you may cluster VCSs even some of VCS(s) has different amount of “non-traversal”, “traversal” or/and “TURN” call licenses.

As cluster VCS should provide same functionality to all registered Endpoint cross cluster peer, all VCS within same cluster must have same “functional” option key, such as SIP-H323 Interworking GW, Device Provisioning, etc.

[john-guy]

Thank you all for the clarification.  Is it true that a Master-VCS can temporarily transfer its licenses to a second VCS-Peer for a period of one month.  For example, my Master VCS fails where all the licenses are dynamically reassigned the the secondary VCS controller?  If this is true what configuration is required to set this up?

[Tomonori Taniguchi]

From X7.0 release, call licenses are shared across the entire VCS cluster and this automatically happen once cluster configuration activated.

Traversal and non-traversal call license option keys are still installed on each individual peer and are subject to per-peer limits, but the licenses are available to all peers in the cluster.

If a Cisco VCS peer loses its connection to the cluster, the shareable licenses installed on that peer will remain available to the rest of the cluster peers for “two weeks” from the time the cluster lost contact with the peer.

Please note, call licenses are shared across the entire VCS cluster, but there is maximum traversal and non-traversal call number that individual VCS can handle which can be exceed even there is still available free call license.

[john-guy]

The following licenses (if used) are required and must be on all VCS controllers in a cluster.

1. Cisco Telepresence FindMe
   
2. Cisco Telepresence Multiway
   
3. Device Provisioning
   
4. Microsoft OCS 2007 Enhanced Option
   
5. Advanced Account Security
   

Call Licenses such as Traversal and Non-Traversal licenses don't need to be the same across the cluster.