- CheckMates
- :
- Products
- :
- General Topics
- :
- sk167903 cpview - parameter
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Are you a member of CheckMates?
×- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
sk167903 cpview - parameter
Hi,
tried to implement sk167903 to view data in cpview
However, the 'on the fly' parameter are not accepted.
Not sure what I made wrong. Any idea ?
I didn't want to change kernel parameter (reboot required)
[Expert@fw-01:0]# fw ctl set int sim_top_conns_enable 1 -a
PPAK 0: Get before set operation succeeded of sim_top_conns_enable
kiss_params: failed to update VS 0
dmd_mgmt: Get param failed: Unknown parameter sim_top_conns_enable
dmd_worker: Get param failed: Unknown parameter sim_top_conns_enable
[Expert@fw-01:0]# fw ctl set int sim_top_proto_enable 1
Set operation failed: failed to get parameter sim_top_proto_enable
set: Operation failed
Killed
[Expert@fw-01:0]# cpinfo -y FW1
This is Check Point CPinfo Build 914000250 for GAIA
[FW1]
HOTFIX_TEX_ENGINE_R8120_AUTOUPDATE
HOTFIX_INEXT_NANO_EGG_AUTOUPDATE
HOTFIX_R81_20_JUMBO_HF_MAIN Take: 92
HOTFIX_GOT_TPCONF_AUTOUPDATE
HOTFIX_R80_40_MAAS_TUNNEL_AUTOUPDATE
HOTFIX_PUBLIC_CLOUD_CA_BUNDLE_AUTOUPDATE
FW1 build number:
This is Check Point's software
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
It is not a bug but feature. The parameter should work. Please refer to: https://support.checkpoint.com/results/sk/sk180497
Can be confirmed to check after change with: fw ctl get int sim_top_conns_enable -a
If you like this post please give a thumbs up(kudo)! 🙂
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Did you try fw ctl set int sim_top_proto_enable 1 -a
instead of fw ctl set int sim_top_proto_enable 1 ?
As this is VSX - did you use the vsenv <VS ID>
before calling cpview ? https://support.checkpoint.com/results/sk/sk101878
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
no, it is a standard appliance (clusterXL; 7000)
[Expert@fw-01:0]# fw ctl set int sim_top_proto_enable 1 -a
PPAK 0: Get before set operation succeeded of sim_top_proto_enable
kiss_params: failed to update VS 0
dmd_mgmt: Get param failed: Unknown parameter sim_top_proto_enable
dmd_worker: Get param failed: Unknown parameter sim_top_proto_enable
Expert@fw-01:0]# fw ctl set int sim_top_proto_enable ?
kiss_params_user_ctl_set: Argument given is not a number
set: Operation failed
Killed
[Expert@fw-01:0]# fw ctl set int ?
Set operation failed: not enough arguments
set: Operation failed
Killed
[Expert@fw-01:0]# fw ctl set ?
Set operation failed: not enough arguments
set: Operation failed
Regards
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
It is not a bug but feature. The parameter should work. Please refer to: https://support.checkpoint.com/results/sk/sk180497
Can be confirmed to check after change with: fw ctl get int sim_top_conns_enable -a
If you like this post please give a thumbs up(kudo)! 🙂
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Aehm,
you are right.
Still see/get the error message.
But cpview show now the data I was looking for.
Thanks a lot
Regards
