Hi Sylvain, Can you check if the agent has the following config object?
global-vrouter-config:default-global-system-config:default-global-vrouter-config You can use something like: http://10.84.13.30:8085/Snh_ShowIFMapAgentReq?table_name=global-vrouter-config This object has the default encapsulation-priorities, which should be a list that consists of MPLSoUDP, MPLSoGRE and VXLAN. If the agent doesn't get this config object, it uses it's hard-coded default, which is MPLSoUDP. That behavior itself is incorrect (will file a bug), since it should choose from the encaps in the route rather than using a hard-coded value. The bigger issue though would be why the agent didn't get the global-vrouter-config. -Nischal On Apr 29, 2015, at 1:58 AM, Sylvain Afchain <[email protected]> wrote: > Hi All, > > We are facing a weird issue on our lab since fews days. > > The agents use a MPLSoUDP toward the MXs for the public network while the > controller is sending XMPP message saying to use GRE (checked with traces). > It seems that we didn't change anything except playing with the SNAT, thus > with the service chaining. > > We tried to restart the API/Controllers without any success. The fallback > tunnel protocol set in the agent config file is MPLSoUDP so it seems that is > the one that is used by the agents. > > Checking in the instrospec of the agents we see that we have only MPLSoGRE as > supported encap and MPLSoUDP as activated encap. > > We didn't yet restart the agents since we want to know/understand why we are > in such situation ? > > Any help on this will be welcome... to fix...to troubleshoot :) > > Thanks > > Sylvain > > > _______________________________________________ > Dev mailing list > [email protected] > http://lists.opencontrail.org/mailman/listinfo/dev_lists.opencontrail.org _______________________________________________ Dev mailing list [email protected] http://lists.opencontrail.org/mailman/listinfo/dev_lists.opencontrail.org
