topic Re: dst_uo_name does not work in Firewall and Security Management

dst_uo_name does not work

BikeMan — Wed, 14 Dec 2022 08:42:33 GMT

Hi,

I am running MDM R81.10. Clusters are running R80.20 and R80.40. When I search in the logs and filter with dst_uo_name, nothing is displayed.

I have tried to filter on "origin" (I choose a R80.40 cluster) and logs show the involved updatable object in the field "Destination Updatable Object". Then filter (right click on the field) no more logs are displayed.

Any idea ?

Thanks,

Re: dst_uo_name does not work

the_rock — Wed, 14 Dec 2022 10:05:27 GMT

Can you send a screenshot of the filter you did? I can try it in R81.20 lab today.

Re: dst_uo_name does not work

BikeMan — Wed, 14 Dec 2022 10:24:55 GMT

Here are the pics.

Re: dst_uo_name does not work

the_rock — Wed, 14 Dec 2022 10:27:15 GMT

Give me few hours, have appointment to go to soon, but will check when Im back.

Re: dst_uo_name does not work

the_rock — Wed, 14 Dec 2022 10:41:08 GMT

Just checked cloud instance before I have to leave and dont even see that filter available anywhere in smart console. Anyway, will test later in my own lab.

Re: dst_uo_name does not work

PhoneBoy — Wed, 14 Dec 2022 18:59:18 GMT

Not every field you can see in a log card can be “searched” for.
That is very likely one of those fields.
An RFE will need to be raised with your local Check Point office.

Re: dst_uo_name does not work

the_rock — Wed, 14 Dec 2022 19:07:55 GMT

Sorry, been busy day...I tried searching in 3 environments, but no luck ; - (

Re: dst_uo_name does not work

BikeMan — Thu, 15 Dec 2022 07:28:18 GMT

It is supposed to work starting R80.40 (sk172083).

Re: dst_uo_name does not work

PhoneBoy — Thu, 15 Dec 2022 14:52:33 GMT

If it’s not working as described in the SK, then I recommend a TAC case.

Re: dst_uo_name does not work

the_rock — Thu, 15 Dec 2022 15:05:40 GMT

Tested in R81.10 with jumbo 81 and brand new R81.20, no luck on either. Let us know what TAC says if you do end up opening a case.