haii .... i could not esablish BGP(EVPN) connection...""state:down"" is
shown. kindly help...

step1: Creates a new BGPSpeaker instance on each host.::: is working fine
step2:Registers the neighbor for the speakers on each host.---> didnt get


   1.

   (Host A)$ curl -X GET http://localhost:8080/vtep/neighbors |
    python -m json.tool

   ...
   {
       "172.17.0.2": {
           "EvpnNeighbor": {
               "address": "172.17.0.2",
               "remote_as": 65000,
               "state": "up"  # "up" shows the connection established
           }


   2.
   3.
   4.



On Mon, Apr 17, 2017 at 11:25 AM, Tessy Thomas <tessyma...@gmail.com> wrote:

> please find attachment
>
> On Mon, Apr 17, 2017 at 11:24 AM, Tessy Thomas <tessyma...@gmail.com>
> wrote:
>
>> hai..
>>
>> the error is solved,when i run rest_vtep in 2 differnet systems....but
>> now every command works fine...but i have """""state"= down"""""""
>>
>> Please find attachment
>> kindly reply....how to change state down to state up...
>> Thankyou
>>
>> On Thu, Apr 13, 2017 at 10:25 PM, Tessy Thomas <tessyma...@gmail.com>
>> wrote:
>>
>>> ok sir,i will do it in seperate machine,Thankyou for reply
>>>
>>> On Thu, Apr 13, 2017 at 4:48 PM, Yusuke Iwase <iwase.yusu...@gmail.com>
>>> wrote:
>>>
>>>> Hi,
>>>>
>>>> Please confirm again that rest_vtep needs to be executed on the
>>>> separated machine.
>>>>
>>>> It seems that the port Ryu's BGP instance listing on is conflicted.
>>>>
>>>> Thanks,
>>>> Iwase
>>>>
>>>> 2017/04/13 16:49、Tessy Thomas <tessyma...@gmail.com> のメッセージ:
>>>>
>>>> hi..i run it with sudo ..but step2:Registers the neighbor for the
>>>> speakers on each host...is not working for host1 ...i am running both
>>>> controller in same system(without VM) ..please find attachment...
>>>>
>>>> Step1 is working fine.
>>>> Step2 -Registers the neighbor for the speakers- one host is success-in
>>>> other host :core manager is not active error"
>>>> See. image "hostb-2.png"
>>>> Kindly reply
>>>> Thankyou so much
>>>>
>>>>
>>>> On Wed, Apr 12, 2017 at 7:15 PM, Yusuke Iwase <iwase.yusu...@gmail.com>
>>>> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> Well...
>>>>> Please confirm ryu-manager running with "sudo", because BGP needs to
>>>>> listen well-known port 179, which requires root privilege on Linux.
>>>>> I'm sorry it is not clearly described on the document.
>>>>>
>>>>> Thanks,
>>>>> Iwase
>>>>>
>>>>> 2017/04/11 17:20、Tessy Thomas <tessyma...@gmail.com> のメッセージ:
>>>>>
>>>>> hi..
>>>>> i am getting correct response when adding speaker but getting error
>>>>> when adding neighbor it is showing coremanager is not active....please 
>>>>> find
>>>>> attachment
>>>>>
>>>>> thankyou
>>>>>
>>>>> On Tue, Apr 11, 2017 at 12:02 PM, Iwase Yusuke <
>>>>> iwase.yusu...@gmail.com> wrote:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> What did rest_vtep.py response for "1. Creates a new BGPSpeaker
>>>>>> instance on each host."?
>>>>>> Did you get the message as expected?
>>>>>>   http://ryu.readthedocs.io/en/latest/app/rest_vtep.html#ryu.a
>>>>>> pp.rest_vtep.RestVtepController.add_speaker
>>>>>>
>>>>>> Thanks,
>>>>>> Iwase
>>>>>>
>>>>>>
>>>>>> On 2017年04月11日 14:31, Tessy Thomas wrote:
>>>>>> > hi..i run the rest_vtep with 2 systems...
>>>>>> > the BGP speaker is started..but i'm getting error as follows
>>>>>> >
>>>>>> > "error": "500.3 - CoreManager is not active.",
>>>>>> >     "status": 500
>>>>>> >
>>>>>> > kindly reply,,
>>>>>> > thankyou
>>>>>> >
>>>>>> >
>>>>>> > On Tue, Apr 11, 2017 at 10:00 AM, Tessy Thomas <
>>>>>> tessyma...@gmail.com <mailto:tessyma...@gmail.com>> wrote:
>>>>>> >
>>>>>> >     hi .thankyou for the reply....i run both controller in same
>>>>>> machine(in 2 terminal)
>>>>>> >     will do it in 2 vm
>>>>>> >     thankyou
>>>>>> >
>>>>>> >     On Tue, Apr 11, 2017 at 5:42 AM, Iwase Yusuke <
>>>>>> iwase.yusu...@gmail.com <mailto:iwase.yusu...@gmail.com>> wrote:
>>>>>> >
>>>>>> >         Hi,
>>>>>> >
>>>>>> >         First, please let me make your question clear.
>>>>>> >         Are you trying to start ryu1 and ryu2 on the same host(or
>>>>>> the same VM)?
>>>>>> >
>>>>>> >         rest_vtep.py suppose to be executed on the different host
>>>>>> for each other.
>>>>>> >           http://ryu.readthedocs.io/en/
>>>>>> latest/app/rest_vtep.html#environment <http://ryu.readthedocs.io/en/
>>>>>> latest/app/rest_vtep.html#environment>
>>>>>> >           e.g.) On Host A, Ryu1 and s1(OVS) should be executed, and
>>>>>> on Host B,
>>>>>> >             Ryu2 and s2(OVS) should be executed.
>>>>>> >             Also, s1h1 and s1h2 shows VMs or network namespaces
>>>>>> (like container).
>>>>>> >
>>>>>> >         I added some description to the following:
>>>>>> >
>>>>>> >           +----------------------+
>>>>>>  +----------------------+
>>>>>> >           | Host A (172.17.0.1)  |                 | Host B
>>>>>> (172.17.0.2)  |
>>>>>> >           |+--------------------+|
>>>>>>  |+--------------------+|
>>>>>> >           ||   Ryu1             |---- BGP(EVPN) ----|   Ryu2
>>>>>>      ||
>>>>>> >           |+--------------------+|
>>>>>>  |+--------------------+|
>>>>>> >           |        |             |                 |       |
>>>>>>       |
>>>>>> >           |+--------------------+|
>>>>>>  |+--------------------+|
>>>>>> >           ||   s1(OVS):dpid=1   |====== vxlan ======|
>>>>>>  s2(OVS):dpid=1   ||
>>>>>> >           |+--------------------+|
>>>>>>  |+--------------------+|
>>>>>> >           |(s1-eth1)    (s1-eth2)|                 |(s2-eth1)
>>>>>> (s2-eth2)|
>>>>>> >           |   |            |     |                 |   |
>>>>>> |     |
>>>>>> >           |+--------+  +--------+|                 |+--------+
>>>>>> +--------+|
>>>>>> >           || s1h1   |  | s1h2   ||                 || s2h1   |  |
>>>>>> s2h2   ||
>>>>>> >           |+--------+  +--------+|                 |+--------+
>>>>>> +--------+|
>>>>>> >           +----------------------+
>>>>>>  +----------------------+
>>>>>> >
>>>>>> >         Because rest_vtep.py will create BGP instance, which
>>>>>> listening on the
>>>>>> >         well-known port 179, and it is difficult to run it on the
>>>>>> same host
>>>>>> >         (some additional configuration will be required, and
>>>>>> rest_vtep does not
>>>>>> >         support it).
>>>>>> >
>>>>>> >
>>>>>> >         For the error message "No such datapath: 1", please confirm
>>>>>> your OVS
>>>>>> >         instance's datapath-id(=dpid).
>>>>>> >
>>>>>> >         Thanks,
>>>>>> >         Iwase
>>>>>> >
>>>>>> >
>>>>>> >         On 2017年04月10日 23:34, Tessy Thomas wrote:
>>>>>> >         > halo,thankyou so much for reply..attaching the screen
>>>>>> shots of how i run it...i got error message when i run
>>>>>> >         >
>>>>>> >         > "Creates a new BGPSpeaker instance on each host" ...
>>>>>> >         >
>>>>>> >         > where do i went wrong?? Kindly help
>>>>>> >         >
>>>>>> >         > thankyou
>>>>>> >         >
>>>>>> >         >
>>>>>> >         >
>>>>>> >         > Creates a new BGPSpeaker instance on each host.
>>>>>> >         >
>>>>>> >         > On Host A:
>>>>>> >         >
>>>>>> >         > (Host A)$ curl -X POST -d '{
>>>>>> >         >  "dpid": 1,
>>>>>> >         >  "as_number": 65000,
>>>>>> >         >  "router_id": "172.17.0.1"
>>>>>> >         >  }' http://localhost:8080/vtep/speakers <
>>>>>> http://localhost:8080/vtep/speakers> | python -m json.tool
>>>>>> >         >
>>>>>> >         >
>>>>>> >         > On Mon, Apr 10, 2017 at 7:22 AM, Iwase Yusuke <
>>>>>> iwase.yusu...@gmail.com <mailto:iwase.yusu...@gmail.com> <mailto:
>>>>>> iwase.yusu...@gmail.com <mailto:iwase.yusu...@gmail.com>>> wrote:
>>>>>> >         >
>>>>>> >         >     Hi,
>>>>>> >         >
>>>>>> >         >     Thank you for reporting!
>>>>>> >         >
>>>>>> >         >
>>>>>> >         >     On 2017年04月09日 20:31, Tessy Thomas wrote:
>>>>>> >         >     > hi.
>>>>>> >         >     > i followed http://ryu.readthedocs.io/en/l
>>>>>> atest/app/rest_vtep.html <http://ryu.readthedocs.io/en/
>>>>>> latest/app/rest_vtep.html> <http://ryu.readthedocs.io/en/
>>>>>> latest/app/rest_vtep.html <http://ryu.readthedocs.io/en/
>>>>>> latest/app/rest_vtep.html>> .. but i am very new to ryu,..can
>>>>>> someone kindly help me to run it.....
>>>>>> >         >     >
>>>>>> >         >     > cd ryu1
>>>>>> >         >     > ryu-manager ryu/app/rest_vtep.py
>>>>>> >         >     >
>>>>>> >         >     > cd ryu2
>>>>>> >         >     > ryu-manager ryu/app/rest_vtep.py
>>>>>> >         >     >
>>>>>> >         >     >
>>>>>> >         >     > ovs-vsctl add-br s1-ovs
>>>>>> >         >     > ovs-vsctl set-controller s1-ovs tcp:172.17.0.1:6633
>>>>>> <http://172.17.0.1:6633> <http://172.17.0.1:6633> <
>>>>>> http://172.17.0.1:6633>
>>>>>> >         >     >
>>>>>> >         >     > ovs-vsctl add-br s2-ovs
>>>>>> >         >     > ovs-vsctl set-controller s2-ovs tcp:172.17.0.2:6633
>>>>>> <http://172.17.0.2:6633> <http://172.17.0.2:6633> <
>>>>>> http://172.17.0.2:6633>
>>>>>> >         >     >
>>>>>> >         >     > i did these....but i got error """ "error":
>>>>>> "BGPSpeaker could not be found",
>>>>>> >         >     >     "status": 404"""\
>>>>>> >         >
>>>>>> >         >     First, which command returned this message?
>>>>>> >         >     The above message shows Ryu's BGP instance was not
>>>>>> started yet or could not be
>>>>>> >         >     started as expected.
>>>>>> >         >
>>>>>> >         >
>>>>>> >         >     Thanks,
>>>>>> >         >     Iwase
>>>>>> >         >
>>>>>> >         >     >
>>>>>> >         >     >
>>>>>> >         >     > kindly help
>>>>>> >         >     > thankyou
>>>>>> >         >     >
>>>>>> >         >     >
>>>>>> >         >     >
>>>>>> >         >     >
>>>>>> >         >     > ------------------------------
>>>>>> ------------------------------------------------
>>>>>> >         >     > Check out the vibrant tech community on one of the
>>>>>> world's most
>>>>>> >         >     > engaging tech sites, Slashdot.org!
>>>>>> http://sdm.link/slashdot
>>>>>> >         >     >
>>>>>> >         >     >
>>>>>> >         >     >
>>>>>> >         >     > _______________________________________________
>>>>>> >         >     > Ryu-devel mailing list
>>>>>> >         >     > Ryu-devel@lists.sourceforge.net <mailto:
>>>>>> Ryu-devel@lists.sourceforge.net> <mailto:Ryu-devel@lists.source
>>>>>> forge.net <mailto:Ryu-devel@lists.sourceforge.net>>
>>>>>> >         >     > https://lists.sourceforge.net/
>>>>>> lists/listinfo/ryu-devel <https://lists.sourceforge.net
>>>>>> /lists/listinfo/ryu-devel> <https://lists.sourceforge.net
>>>>>> /lists/listinfo/ryu-devel <https://lists.sourceforge.net
>>>>>> /lists/listinfo/ryu-devel>>
>>>>>> >         >     >
>>>>>> >         >
>>>>>> >         >
>>>>>> >
>>>>>> >
>>>>>> >
>>>>>> >
>>>>>> >
>>>>>> > ------------------------------------------------------------
>>>>>> ------------------
>>>>>> > Check out the vibrant tech community on one of the world's most
>>>>>> > engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>>>>> >
>>>>>> >
>>>>>> >
>>>>>> > _______________________________________________
>>>>>> > Ryu-devel mailing list
>>>>>> > Ryu-devel@lists.sourceforge.net
>>>>>> > https://lists.sourceforge.net/lists/listinfo/ryu-devel
>>>>>> >
>>>>>>
>>>>>
>>>>> <aaa.png>
>>>>>
>>>>> <core-manager.png>
>>>>>
>>>>> ------------------------------------------------------------
>>>>> ------------------
>>>>> Check out the vibrant tech community on one of the world's most
>>>>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>>>>
>>>>> _______________________________________________
>>>>> Ryu-devel mailing list
>>>>> Ryu-devel@lists.sourceforge.net
>>>>> https://lists.sourceforge.net/lists/listinfo/ryu-devel
>>>>>
>>>>>
>>>> <ryu-cont-1.png>
>>>>
>>>> <ryu-contr-2.png>
>>>>
>>>> <mininet-topo.png>
>>>>
>>>> <hostb-2.png>
>>>>
>>>>
>>>
>>
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Ryu-devel mailing list
Ryu-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ryu-devel

Reply via email to