[R4.1-97]- SLO: Fat flow matching SLO rules does not get logged as per rate

Bug #1752258 reported by alok kumar
6
This bug affects 1 person
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:Port/Destination:Port Proto(V)
-----------------------------------------------------------------------------------
    92920<=>125248 11.29.16.3:0 6 (2)
                         125.43.43.4:53
(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)
                         11.29.16.3:0
(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 SessionEndpointObject /var/log/contrail/contrail-vrouter-agent.log*
2018-03-01 Thu 11:30:48:285.096 IST nodec62 [Thread 140719033415424, Pid 2326]: [SYS_INFO]: SessionEndpointObject: session_data= [ [ [ vmi = default-domain:ctest-SecurityLogging-63137257:2838beae-4f7b-4fbf-980d-ff324eaf6e3e vn = default-domain:ctest-SecurityLogging-63137257:ctest-vn-40955256 security_policy_rule = 00000000-0000-0000-0000-000000000001 remote_vn = default-domain:ctest-SecurityLogging-63137257:ctest-vn-47610922 is_client_session = 0 is_si = 0 vrouter_ip = 10.204.217.102 sess_agg_info= [ [ [ local_ip = 125.43.43.4 service_port = 53 protocol = 6 ] [ logged_forward_bytes = 80 logged_forward_pkts = 2 logged_reverse_bytes = 108 logged_reverse_pkts = 2 sessionMap= [ [ [ ip = 11.29.16.3 port = 0 ] [ forward_flow_info= [ logged_bytes = 80 logged_pkts = 2 flow_uuid = 5b48fcdb-67a5-4d99-b25f-faa1084c3a70 tcp_flags = 0 setup_time = 1519884048178630 action = pass sg_rule_uuid = 9e0ddee7-5997-4ac1-8e87-87f615a9db9e nw_ace_uuid = b52837a1-55db-4bea-8e85-60d8e1c205f0 underlay_source_port = 64548 ] reverse_flow_info= [ logged_bytes = 108 logged_pkts = 2 flow_uuid = ca591005-9ba1-4a53-b5a3-4c72ae052381 tcp_flags = 0 setup_time = 1519884048178630 action = pass sg_rule_uuid = 9e0ddee7-5997-4ac1-8e87-87f615a9db9e nw_ace_uuid = b52837a1-55db-4bea-8e85-60d8e1c205f0 underlay_source_port = 52253 ] vm = 884e063e-df71-42a7-b4e6-5dcfcbe9d7dd other_vrouter_ip = 10.204.216.69 underlay_proto = 2 ], ] ] ], ] ] ], ] ]

but when we send the traffic again for the same Fat flow it does not get logged.

Flow with total 4 pkts:
    Index Source:Port/Destination:Port Proto(V)
-----------------------------------------------------------------------------------
    92920<=>125248 11.29.16.3:0 6 (2)
                         125.43.43.4:53
(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)
                         11.29.16.3:0
(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 SessionEndpointObject /var/log/contrail/contrail-vrouter-agent.log*
2018-03-01 Thu 11:30:48:285.096 IST nodec62 [Thread 140719033415424, Pid 2326]: [SYS_INFO]: SessionEndpointObject: session_data= [ [ [ vmi = default-domain:ctest-SecurityLogging-63137257:2838beae-4f7b-4fbf-980d-ff324eaf6e3e vn = default-domain:ctest-SecurityLogging-63137257:ctest-vn-40955256 security_policy_rule = 00000000-0000-0000-0000-000000000001 remote_vn = default-domain:ctest-SecurityLogging-63137257:ctest-vn-47610922 is_client_session = 0 is_si = 0 vrouter_ip = 10.204.217.102 sess_agg_info= [ [ [ local_ip = 125.43.43.4 service_port = 53 protocol = 6 ] [ logged_forward_bytes = 80 logged_forward_pkts = 2 logged_reverse_bytes = 108 logged_reverse_pkts = 2 sessionMap= [ [ [ ip = 11.29.16.3 port = 0 ] [ forward_flow_info= [ logged_bytes = 80 logged_pkts = 2 flow_uuid = 5b48fcdb-67a5-4d99-b25f-faa1084c3a70 tcp_flags = 0 setup_time = 1519884048178630 action = pass sg_rule_uuid = 9e0ddee7-5997-4ac1-8e87-87f615a9db9e nw_ace_uuid = b52837a1-55db-4bea-8e85-60d8e1c205f0 underlay_source_port = 64548 ] reverse_flow_info= [ logged_bytes = 108 logged_pkts = 2 flow_uuid = ca591005-9ba1-4a53-b5a3-4c72ae052381 tcp_flags = 0 setup_time = 1519884048178630 action = pass sg_rule_uuid = 9e0ddee7-5997-4ac1-8e87-87f615a9db9e nw_ace_uuid = b52837a1-55db-4bea-8e85-60d8e1c205f0 underlay_source_port = 52253 ] vm = 884e063e-df71-42a7-b4e6-5dcfcbe9d7dd other_vrouter_ip = 10.204.216.69 underlay_proto = 2 ], ] ] ], ] ] ], ] ]

Note: when SLO rate is 1 then it's logged for each new pkt as expected.

Revision history for this message
alok kumar (kalok) wrote :

marking invalid, test config issue. SLO rate was high so it was not getting logged.

alok kumar (kalok)
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
Revision history for this message
alok kumar (kalok) wrote :

Bug is valid with SLO rate for Fat flow, reopening this bug to look further.
Have updated the bug description accordingly..

description: updated
Jeba Paulaiyan (jebap)
tags: added: releasenote
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.