Can someone tell me what is this sku for?

[Vladimir]

Can't find it in $CPDIR/conf/cp.macro: 

CPSM-PU001-F-CLM

Specifically the -F-CLM portion.

Thank you,

Vladimir

[AlekseiShelepov]

I think CLM stands for Customer Log Module or Domain Log Server. The licence itself is quite old, I some found info from 2012 - 2014 for it.

And for the whole licence name it should mean:

Security Management for Unlimited Gateways and 1 Blade - CLM

[Vladimir]

Thank you Aleksei Shelepov‌ for looking into it.

I too was able to locate this gem:

As to "-F" I am not sure what it is for, but by looking at the $CPDIR/conf/cp.macro

We see it sometimes appended to the products:

MACRO ::CPFW-ESO-1-mgmt-NGX-F CPFW-ESO-1-IKE3DES-mgmt-NGX
MACRO ::CPVP-VSO-1-mgmt-NGX-F CPVP-VSO-1-IKE3DES-mgmt-NGX

but it does not discriminate between IKE3DES, DES etc.. so I am not sure what it's for.

[G_W_Albrecht]

That are really old licenses, i have found a document from 6.2008 with content from 2003-2007:

CPMP-CLM Customer Log Module
enables real-time log accumulation, tracking and SmartCenter on a dedicated log server for VPN-1 Pro Gateways.
Licensed per number of log servers

In 2011, the Multi-Domain R75v Licensing Primer explained the name changes:

the following table documents the old names and the corresponding new name as relevant for R75

Then the new licenses are listed:

And we find that the -F here stands for upgrading to Multi-Domain Blade licensing:

Q18: What is this Enabler SKU?
- A single ―Enabler‖ SKU is required for every Provider-1 Server
    CPSM-PV1-F
- To receive the ―Enabler― SKU, customers are required to contact Account Services with the following information
   UC account IDs for accounts containing legacy Provider-1 products
   Products that require migration (SKUs + CKs)
   Automatic migration using the ―Self Migration Tool‖ in UserCenter will be added at a later stage

[Vladimir]

Thank you Günther W. Albrecht‌! 

It would've been helpful if CP was to maintain a single reference DB to all of the iterations of the products that could be referenced online.

Regards,

Vladimir

[G_W_Albrecht]

Maybe you are right - but would it really be important ? Your question was about a license enabler 8 years old that had been generated during the change to blade licensing. Only Account Services could tell you exactly its current status as MDM licensing is a science for itself, secret to the uninitiated...

[Vladimir]

I'll give you that it is not often something like this comes up, but what is the harm of having historical SKUs listing?

One less thing for us to spend the time on tracking down the oddball licenses.

[G_W_Albrecht]

I did not mean that there is any harm in that, but i doubt that the work needed would be worth the trouble 😉 CP documentation is already a very broad and complex theme, so when licenses are concerned, it is mostly easier to open a ticket with account services. Especially MDM licensing would not profit much from a database as different licensing models in P-1 history can not be easily compared, find an example here from Multi-Domain R75 Licensing:

[_Val_]

All SKUs, from 4.0 and up, are listed in cp.macro file on any Check Point installation. Some limited explanation is given in the comments in that file as well.