headless mode enabled still no communication between 2 networks

[krypto]

Setup:

One Contrail controller,2 compute nodes and one Openstack controller-Liberty

Version:
contrail-version
Package Version Build-ID | Repo | Package Name
-------------------------------------- ------------------------------ ----------------------------------
contrail-lib 3.1.0.0-25 25
contrail-nodemgr 3.1.0.0-25 25
contrail-nova-vif 3.1.0.0-25 25
contrail-openstack-vrouter 3.1.0.0-25 25
contrail-setup 3.1.0.0-25 25
contrail-utils 3.1.0.0-25 25
contrail-vrouter-agent 3.1.0.0-25 25
contrail-vrouter-common 3.1.0.0-25 25
contrail-vrouter-dkms 3.1.0.0-25 25
contrail-vrouter-dpdk 3.1.0.0-25 25
contrail-vrouter-init 3.1.0.0-25 25
contrail-vrouter-utils 3.1.0.0-25 25

Compute:

 cat /etc/contrail/contrail-vrouter-agent.conf|grep headless
headless_mode=True

 contrail-status
== Contrail vRouter ==
supervisor-vrouter: active
contrail-vrouter-agent active (Collector, Discovery:Collector, Discovery:dns-server, Discovery:xmpp-server connection down)
contrail-vrouter-nodemgr initializing (Collector, Discovery:Collector[Subscribe - Connection Error] connection down)

with XMPP down vms in same compute node are not able to communicate when in two different subnets ,but vms in same subnet are working.

isn't it supposed to keep route information ,and generate flow when vms in 2 subnets try to communicate.

flow -l
Flow table(size 80609280, entries 629760)

Entries: Created 1531 Added 1541 Processed 1531 Used Overflow entries 0
(Created Flows/CPU: 1531)(oflows 0)

Action:F=Forward, D=Drop N=NAT(S=SNAT, D=DNAT, Ps=SPAT, Pd=DPAT, L=Link Local Port)
 Other:K(nh)=Key_Nexthop, S(nh)=RPF_Nexthop
 Flags:E=Evicted, Ec=Evict Candidate, N=New Flow, M=Modified Dm=Delete Marked
TCP(r=reverse):S=SYN, F=FIN, R=RST, C=HalfClose, E=Established, D=Dead

    Index Source:Port/Destination:Port Proto(V)
-----------------------------------------------------------------------------------

PS: XMPP failure is simulated by blocking incoming packets from controller.