Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

VMware Smart Assurance NCM: Checkpoint Firewall getting discovered as Generic device (516024)

Last Updated: 2/22/2021Categories: TroubleshootingTotal Views: 7929Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

Checkpoint firewall discovery in NCM is failing to identify correct driver with below messages in $VOYENCE_HOME/logs/autodisc.log

discoverDriverViaSnmp: 10.x.x.x: (trying Driver #1000:CHECKPOINT)
Executing function "CHECKPOINT::initialize"...
Executing function "CHECKPOINT::discoverDevice"...
DASL: Check Point Discovery
SNMP-GET(.1.3.6.1.2.1.1.1.0)->Linux b118451cckcpf1001 2.6.18-92cp #1 SMP Thu Oct 15 17:02:54 IDT 2015 i686
DASL: SNMP Check Point Discovery
SNMP-GET(.1.3.6.1.4.1.2620.1.1.10.0)->Firewall
SNMP-GET(.1.3.6.1.4.1.2620.1.1.10.0)->Firewall
Executing function "CHECKPOINT::discoverDevice"...done #1.000000e+00 (1)
discoverDriverViaSnmp: Driver #1000, Can't Manage this device

Device is discovered with Generic device class.

Cause

NCM looks for OID 1.3.6.1.4.1.2620.1.1.10.0 contains  FireWall-1 & sysDesc(.1.3.6.1.2.1.1.1.0) should not contain  IP530 to identify device as CheckPoint Firewall.
Here second condition is met, first is not, hence discovery will pick Generic driver.

SNMP-GET(.1.3.6.1.4.1.2620.1.1.10.0)->Firewall
SNMP-GET(.1.3.6.1.2.1.1.1.0)->Linux b118451cckcpf1001 2.6.18-92cp #1 SMP Thu Oct 15 17:02:54 IDT 2015 i686

This device type is not officially supported in NCM as of now. Raise a TASC request for official device support in upcoming NCM DSR releases.

Refer the below links on how to submit TASC request:
https://kb.vmware.com/s/article/334114?lang=en_US

Resolution

Below workaround can be added in DS to discover device with correct device class:

1) Create a directory with name "checkpoint" at $VOYENCE_HOME/custompackage, if it doesn't already exist and copy all files from $VOYENCE_HOME/package/checkpoint to the newly created folder.
2) Open devCP.dasl file at $VOYENCE_HOME/custompackage/checkpoint/ directory, modify below lines

From:
(ProductCode.value == "FireWall-1"))
To:
(ProductCode.value == "FireWall-1" ||  Firewall ))

From:
if (strfind (version, "FireWall-1") != -1) {
To:
if (strfind (version, "FireWall-1") != -1 || strfind (version, "Firewall") != -1) {

Save the file.

3) Restart voyence service with following command:
service voyence restart
4) Discover the device now.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

Related Versions:

VMware Smart Assurance - NCM

Take Our Survey

Support Assistant