[R4.1-97]- SLO: Fat flow matching SLO rules does not get logged as per rate
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
R4.1 |
New
|
High
|
Pramodh D'Souza | |||
R5.0 |
New
|
High
|
Pramodh D'Souza | |||
Trunk |
New
|
High
|
Pramodh D'Souza |
Bug Description
Fat flows matching the configured SLO rules does not get logged as per SLO rate. it's logged only once if rate is greater than 1. in current case SLO rate is 2.
Fat flow on server node with 2 pkts:
Index Source:
-------
92920<=>125248 11.29.16.3:0 6 (2)
(Gen: 26, K(nh):18, Action:F, Flags:, TCP:, QOS:-1, S(nh):45, Stats:2/80,
SPort 64548, TTL 0, Sinfo 10.204.216.69)
125248<=>92920 125.43.43.4:53 6 (2)
(Gen: 22, K(nh):18, Action:F, Flags:, TCP:, QOS:-1, S(nh):18, Stats:2/108,
SPort 52253, TTL 0, Sinfo 4.0.0.0)
this flow is logged as below:
root@nodec62:~# grep -a SessionEndpoint
2018-03-01 Thu 11:30:48:285.096 IST nodec62 [Thread 140719033415424, Pid 2326]: [SYS_INFO]: SessionEndpoint
but when we send the traffic again for the same Fat flow it does not get logged.
Flow with total 4 pkts:
Index Source:
-------
92920<=>125248 11.29.16.3:0 6 (2)
(Gen: 26, K(nh):18, Action:F, Flags:, TCP:, QOS:-1, S(nh):45, Stats:4/160,
SPort 64548, TTL 0, Sinfo 10.204.216.69)
125248<=>92920 125.43.43.4:53 6 (2)
(Gen: 22, K(nh):18, Action:F, Flags:, TCP:, QOS:-1, S(nh):18, Stats:4/216,
SPort 52253, TTL 0, Sinfo 4.0.0.0)
No new log is seen in log file:
root@nodec62:~# grep -a SessionEndpoint
2018-03-01 Thu 11:30:48:285.096 IST nodec62 [Thread 140719033415424, Pid 2326]: [SYS_INFO]: SessionEndpoint
Note: when SLO rate is 1 then it's logged for each new pkt as expected.
summary: |
- [R4.1-97]- SLO: Fat flow matching SLO rules does not get logged + [R4.1-97]- SLO: Fat flow matching SLO rules does not get logged as per + rate |
tags: | added: releasenote |
marking invalid, test config issue. SLO rate was high so it was not getting logged.