CPinfo Utility build for R82.10

[JozkoMrkvicka]

Hi there,

I just noticed that after the upgrade to R82.10, the cpinfo utility build is 914000224.

Such a cpinfo build does NOT exist as per The CPInfo utility article. The latest build of cpinfo utility is 914000259.

Even the download page of cpinfo build 914000259 doesnt have versions R82 nor R82.10 mentioned as affected version:

• VersionR80 (EOS), R80.40 (EOS), R81 (EOS), R81.10, R81.20

Can someone elaborate on that ?

Another related question - Why is cpinfo utility not auto-updated as almost every Check Point utility out there ?

Thank you.

[Vincent_Bacher]

---

@JozkoMrkvicka wrote:

Another related question - Why is cpinfo utility not auto-updated as almost every Check Point utility out there ?

---

This could certainly be done using an auto-updater. The question is whether checking and updating when cpinfo is started might not be sufficient after all.

[Tal_Paz-Fridman]

I've forwarded this post to the relevant R&D owner and will update you once I hear back.

[the_rock]

Wish I had R82.10 lab to check this.

[CaseyB]

I am seeing the same thing on our 3920s, I checked units that were clean installed and upgraded.

[JozkoMrkvicka]

There shouldnt be any action done by end user, as cpinfo is supposed to check if there is newer build automatically installed once per week. If all download consent flags are allowed and device has proxy configured, there is no automatic update at all.

I just tested it by manually running "cpinfo -a" on R82 device where not latest build of cpinfo is installed (all download consent flags are allowed). The command "cpinfo -a" detects I dont have latest cpinfo on the device and updated it to the 259 build. There were some errors printed during the update. Also, I noticed automatic cpinfo is done after newer build is updated (not desired, as I just want to update build of cpinfo, not perform cpinfo at all).

Something is not properly working here...

[the_rock]

Agree 100%

[CaseyB]

Yes, I am agreeing with you that something is not working properly, I am confirming the issue in our environment.

[the_rock]

Lets see whatr @Tal_Paz-Fridman finds out about it.

[Elad_Chomsky · Accepted solution]

Hi @JozkoMrkvicka ,

I’ll take this internally to update the CPinfo utility (SK). Since build numbers differ by version, CPinfo should automatically select/update the appropriate build when it’s triggered. The split was introduced due to new appliance types, which required a separate CPinfo version.

Currently released builds:

• R82 and earlier: 259
• R82.10: 224
• Later than R82.10: 194 (planned / upcoming on the roadmap)

So far we haven’t seen a specific demand for moving CPinfo into AutoUpdater. If you have a concrete customer use case for that, I suggest opening an RFE, and we’ll review it and see whether we can prioritize it on the roadmap.

[the_rock]

Thanks for updating us @Elad_Chomsky 

[JozkoMrkvicka]

Thank you for the update @Elad_Chomsky.

As per the CPinfo utility SK, there should be automatic check of newer version once a week:

Parameter	Description	Important Notes
-a	Forces the update check of the CPInfo utility (by default, it is checked once a week)	Can NOT be used in combination with "-d" Can NOT be used in combination with "-i"

Or does it mean that the CPinfo utility will start to check for newer version only once I try to update it manually using -a parameter ?

[Elad_Chomsky]

There is a mechanism to not check for updates more than once a week. To make it always check, you can use the '-a' flag.

[emmap]

CPInfo checks once a week but only when triggered by you running it. So if you run it once it will check for updates, and if you run it again within a week it will not check. If you don't run it for three months, it will not be updated until you run it again.

It and this behaviour predate the autoupdater stuff so I guess it hasn't been changed as there isn't really the demand to. As it's a utility that's only used occasionally and isn't otherwise relied on for gateway operations it's not critical that it be kept up to date without user interaction.

[JozkoMrkvicka]

Thanks for the explanation.