> Quick search for "No BGP configuration for self" seems to indicate that it > is not an issue i.e. once BGP peers are configured, state should change. > But it seems like vrouter-agent XMPP connection is closed by the control node > since it thinks that there is no self BGP config.
From what I have seen you must be missing a proper“Control node” object under the BGP routers for the contrail-control node(s) itself. It is not related to a BGP peer “outside of contrail” like an Juniper MX80 or something like that. In the gui add a new BGP object of the type “control node” with the IP of the control node AND the correct name. Note that Ubuntu and Redhat seem to use different names (IIRC with Ubuntu you need to put in the shortname and with Redhat the FQDN) I think you can lookup the expected name by going to the first page of the gui: you should be able to see the expected names for the control nodes in the controller overview. When this is properly setup the “no config for self” should be gone from the contrail-status command on the controllers. Until this message is fixed stuff will not work in my experience. (e.g. you can spawn instances if you use e.g. OpenStack but traffic will not work since it will miss a lot of the configuration on the vrouter) Cheers, Robert van Leeuwen
_______________________________________________ Users mailing list Users@lists.opencontrail.org http://lists.opencontrail.org/mailman/listinfo/users_lists.opencontrail.org
