Thanks Robert! I also had suspected hostname at first since I guess that is
used in logic to figure out whether provisioned control node configuration is
for self. Everything looked good to me and json output I attached confirms it.
In any case, I had to do reinstall of some of the contrail packages and this
problem has disappeared. I am not sure what fixed it. I definitely didn't fix
any control node configuration.
Will keep an eye on this.
Also, as soon as "no config for self" error went away, vrouter agent was able
to establish XMPP connection to control node. So all is good now.
Thanks,Rathi
On Tuesday, June 6, 2017 10:47 PM, "Van Leeuwen, Robert"
<rovanleeu...@ebay.com> wrote:
#yiv2677697258 #yiv2677697258 -- _filtered #yiv2677697258 {panose-1:2 4 5 3 5
4 6 3 2 4;} _filtered #yiv2677697258 {panose-1:2 0 5 3 0 0 0 2 0
4;}#yiv2677697258 #yiv2677697258 p.yiv2677697258MsoNormal, #yiv2677697258
li.yiv2677697258MsoNormal, #yiv2677697258 div.yiv2677697258MsoNormal
{margin:0in;margin-bottom:.0001pt;font-size:12.0pt;}#yiv2677697258 a:link,
#yiv2677697258 span.yiv2677697258MsoHyperlink
{color:#0563C1;text-decoration:underline;}#yiv2677697258 a:visited,
#yiv2677697258 span.yiv2677697258MsoHyperlinkFollowed
{color:#954F72;text-decoration:underline;}#yiv2677697258
span.yiv2677697258EmailStyle17
{font-family:Calibri;color:windowtext;}#yiv2677697258 span.yiv2677697258msoIns
{text-decoration:underline;color:teal;}#yiv2677697258
.yiv2677697258MsoChpDefault {font-size:10.0pt;} _filtered #yiv2677697258
{margin:1.0in 1.0in 1.0in 1.0in;}#yiv2677697258 div.yiv2677697258WordSection1
{}#yiv2677697258 > 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
