[openstack-dev] [neutron] FW: [Ryu-devel] [IMPORTANT]: Query regarding BGP Speaker and BGP Peer States.
Gal Sagie
gal.sagie at gmail.com
Mon Aug 17 14:22:37 UTC 2015
Maybe its best to also send this to the Ryu mailing list
On Mon, Aug 17, 2015 at 4:31 PM, Vikram Choudhary <
vikram.choudhary at huawei.com> wrote:
> Widening audience!
>
>
>
> *From:* Vikram Choudhary [mailto:vikram.choudhary at huawei.com]
> *Sent:* 17 August 2015 18:05
> *To:* ryu-devel at lists.sourceforge.net
> *Cc:* Tidwell, Ryan; Vikram Choudhary; Jaume Devesa; Numan Siddique;
> Kalyankumar Asangi; Baldwin, Carl (OpenStack Neutron)
> *Subject:* [Ryu-devel] [IMPORTANT]: Query regarding BGP Speaker and BGP
> Peer States.
>
>
>
> Hi All,
>
>
>
> We have used Ryu’s BGP speaker functionality for one of the neutron
> projects (https://review.openstack.org/#/c/207635/) and want to know BGP
> Speaker and Peer states for display purpose/s.
>
>
>
> With reference to this we have following question’s.
>
>
>
> è Does Ryu’s BGP Speaker functionality expose any API to query BGP
> Speaker and BGP Peer state?
>
> BGP_FSM_IDLE = 'Idle'
>
> BGP_FSM_CONNECT = 'Connect'
>
> BGP_FSM_ACTIVE = 'Active'
>
> BGP_FSM_OPEN_SENT = 'OpenSent'
>
> BGP_FSM_OPEN_CONFIRM = 'OpenConfirm'
>
> BGP_FSM_ESTABLISHED = 'Established'
>
>
>
> è If not then what will be the easiest way of getting this information?
>
> o From the code, we could find “self.state” saves BGP Speaker state.
> Can we use it directly?
>
> o How to get Peer’s state information.
>
>
>
> Any help would be appreciated.
>
>
>
> Thanks
>
> Vikram
>
>
>
>
>
>
>
>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
--
Best Regards ,
The G.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150817/6b38a298/attachment.html>
More information about the OpenStack-dev
mailing list