Hi Stefan, We need to go to the vrouter-agent that hosts the FIP and check if it has established xmpp connections to 2 control nodes. If not, then the FIP will be advertised to just 1 CN and the MX will have just 1 path.
http://<agent-ip>:8085/Snh_AgentXmppConnectionStatusReq? -Nischal On Jul 3, 2015, at 9:55 AM, Stefan Andres <[email protected]<mailto:[email protected]>> wrote: On 01/07/15 18:19, Nischal Sheth wrote: Hi Stefan, Can you check how many BGP paths the GW router(s) has to the floating IP in question in steady state? If you are using an MX you can use "show route table xyz.inet.0". There should ideally be 2 paths learnt from 2 control-nodes. Hey Nischal, it seems only only shows 1 path there. How can we debug this further? Regards, Stefan -Nischal On Jul 1, 2015, at 7:48 AM, Stefan Andres <[email protected]<mailto:[email protected]>> wrote: Hi, we have a setup with 3 contrail-control nodes. We've seen that when we hard-power off on of those nodes, there is a 25-45s packet loss to VM's floating IPs. I'd expect the floating IPs not to have any packet loss at all, since the default BPG TTL should be 30s and in this time, the other contrail-process should already have taken over. What's the concept there and how to tweak those settings? Regards, Stefan _______________________________________________ Dev mailing list [email protected]<mailto:[email protected]> http://lists.opencontrail.org/mailman/listinfo/dev_lists.opencontrail.org -- SysEleven GmbH Umspannwerk - Aufgang C Ohlauer Straße 43 10999 Berlin Tel +49 30 233 2012 0 Fax +49 30 616 755 50 http://www.syseleven.de<http://www.syseleven.de/> http://www.facebook.com/SysEleven Firmensitz: Berlin Registergericht: AG Berlin Charlottenburg, HRB 108571 B Geschäftsführer: Marc Korthaus, Thomas Lohner
_______________________________________________ Dev mailing list [email protected] http://lists.opencontrail.org/mailman/listinfo/dev_lists.opencontrail.org
