SmartLog displays wrong Rule Numbers

[Daniel_Hainich]

Hi,

iam running on R80.20 with Take 188 and Smartconsole 992000088.

In SmartLog i see logs with same src/dst/svc - but smartlog shows different rule-numbers.

The Rule 552.47 is inside sublayer. 

when i open details for connection with wrong rule-number, and click on rule-link, dashboard jumps to correct rule 552.47

is it only an display-bug in smartlog?

[Dror_Aharony]

yea, it looks like only a display issue.

but I'd like to make sure, when you press the link on the left card of 8.552 you're actually moved to 'right' rule of 552.47 (as on the right card)?

the actions are completely different on both cards on the left & right, so something doesn't make sense to me.

what are the 'wrong' rules: 8.552 & 2.47, are they completely irrelevant?

thought they show accept, but on card they show drop & send actions.

can you send pics of all relevant rules & full log-cards?

[Daniel_Hainich]

please provide mail-address

[G_W_Albrecht]

You can send a private post to Dror_Aharony in Messages !

[Nipaporn_Subwil]

I also found an issue like this. My gateway and management are running with R80.40 with HF_T67. 

Do we have any solution for fix this issue ?

[G_W_Albrecht]

Hmmmm - R80.40 JT is currently 87 or GA 83 together with SmartConsole package Build 414

[Mikael]

This seems to be an issue with R81 as well.

I have an issue where traffic is accepted (as expected) but the log and "Matched Rules" are completely broken...

The links seems to work though...

[Dmitriy_Tiper]

We recently upgraded R80.10 to R81 and have run into exactly the same issue - wrong rule number in SmartView Log; however, clicking on it opens policy on the right policy rule.

Googling returns this topic only on the issue.

[Arskaz]

Using R80.30, with quite new JHF. This bug still exists. When opening the log entry, the Session tab shows the right log number.

[Dmitriy_Tiper]

Things are back to normal after R81 JHF 36 installed on SMSs. Now logs show Access policy rules # matched (before it was Application and URL filtering layer rules #)