Rebooting the CN causes traffic loss for existing active streams
Bug #1481932 reported by
Ranjit patro
This bug report is a duplicate of:
Bug #1481606: TSN : High cpu utilization when lot of unknown unicast packets are received.
Edit
Remove
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenContrail |
New
|
Undecided
|
Unassigned |
Bug Description
Upon rebooting the controller, traffic loss is seen for existing traffic streams which are learned and installed in forwarding DB.
I see remote MAC are getting deleted on multiple TORs.
CN and TSN are running latest 2.0-74.
Even after CN is UP after reboot , traffic never recover for most of streams.
ToR Agent shows initializing forever unless i stop all traffic .
When I stop all traffic, TSN state recovers to active.
WHen I start traffic again, though TSN and CN state is fine but traffic doesnt recover (fxpc is seen 100%, will open a separate QFX PR for this)
root@cd- st-lnxserver15: ~# contrail-status vrouter- agent active vrouter- nodemgr active
== Contrail vRouter ==
supervisor-vrouter: active
contrail-
contrail-
== Contrail Control == control- nodemgr active
supervisor-control: active
contrail-control active
contrail-
contrail-dns active
contrail-named active
== Contrail Analytics == analytics: active analytics- api active analytics- nodemgr active query-engine active snmp-collector active
supervisor-
contrail-
contrail-
contrail-collector active
contrail-
contrail-
contrail-topology active
== Contrail Config == config- nodemgr active device- manager active discovery: 0 active svc-monitor active
supervisor-config: active
contrail-api:0 active
contrail-
contrail-
contrail-
contrail-schema active
contrail-
ifmap active
== Contrail Web UI == webui-middlewar e active
supervisor-webui: active
contrail-webui active
contrail-
== Contrail Database == database: active database- nodemgr active
supervisor-
contrail-database active
contrail-
== Contrail Support Services == support- service: active
supervisor-
rabbitmq-server active
root@cd- st-lnxserver15: ~#
root@cd- st-lnxserver16: ~# contrail-status >>>>>>>>>> tor-agent- 1 initializing (ToR:pdt-elit-01 connection down) tor-agent- 2 initializing (ToR:st-pdt-opus02 connection down) tor-agent- 3 active vrouter- agent active vrouter- nodemgr active
== Contrail vRouter ==
supervisor-vrouter: active
contrail-
contrail-
contrail-
contrail-
contrail-
========Run time service failures= ======= ===== core.contrail- vroute. 12194.cd- st-lnxserver16. 1438089702 core.contrail- vroute. 2154.cd- st-lnxserver16. 1438739145 core.contrail- vroute. 7206.cd- st-lnxserver16. 1438770395 core.contrail- vroute. 2150.cd- st-lnxserver16. 1437999440 core.contrail- vroute. 6335.cd- st-lnxserver16. 1438109983 core.contrail- tor-ag. 2151.cd- st-lnxserver16. 1438023139 core.contrail- vroute. 24050.cd- st-lnxserver16. 1438095047 core.contrail- vroute. 18873.cd- st-lnxserver16. 1438755472 core.contrail- vroute. 24639.cd- st-lnxserver16. 1438783974 core.contrail- vrou...
/var/crashes/
/var/crashes/
/var/crashes/
/var/crashes/
/var/crashes/
/var/crashes/
/var/crashes/
/var/crashes/
/var/crashes/
/var/crashes/