Comment 5 for bug 1628044

Are you expecting the Cisco router to initiate the session? To avoid having to run the agent with sudo privileges, we aren't opening a port for accepting connections on the neutron end. If you're expecting you peers to initiate the peering session that could be getting you into trouble. Peers should be set in passive mode, essentially forcing them to wait for neutron to initiate peering. Neutron will initiate the peering session with peers. This seems a little odd, but we didn't want to initially force operators to run the BGP agent with sudo privileges. For Mitaka, we didn't want to deal with the implications of that. To keep it simple, we simply didn't allow Ryu to listen on port 179.

If you put your peers in passive mode and allow neutron to initiate the session, does that solve your problem? We can certainly come back to the issue of listening on port 179 and sudo privileges now that BGP is fairly stable. That may make life easier for users.

If neutron is unable to peer at all, we need to dig in to that. A little more clarification on this point would help.