Create a Post
cancel
Showing results for 
Search instead for 
Did you mean: 
BikeMan
Contributor

dst_uo_name does not work

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,

 

0 Kudos
9 Replies
the_rock
MVP Gold
MVP Gold

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

0 Kudos
BikeMan
Contributor

Here are the pics.

0 Kudos
the_rock
MVP Gold
MVP Gold

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

0 Kudos
the_rock
MVP Gold
MVP Gold

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.

0 Kudos
the_rock
MVP Gold
MVP Gold

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

0 Kudos
PhoneBoy
Admin
Admin

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.

0 Kudos
BikeMan
Contributor

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

0 Kudos
PhoneBoy
Admin
Admin

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

0 Kudos
the_rock
MVP Gold
MVP Gold

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.

0 Kudos

Leaderboard

Epsum factorial non deposit quid pro quo hic escorol.

Upcoming Events

    CheckMates Events