Hi Raja,
Thanks for the reply,
I'm not able to ping control node IP or any other IP from my board. Also
from outside I'm not able to ping board.
Below is the tcpdump log by pinging from both side,
for both vhost0 and eth0 same logs,
########################################################################################
*tcpdump -i <vhost0 and eth0> -n -v 'icmp[icmptype] = icmp-echoreply or
icmp[icmptype] = icmp-echo'*
192.168.6.171 > 192.168.6.210: ICMP echo request, id 12829, seq 508, length
64
02:10:13.042670 IP (tos 0x0, ttl 63, id 0, offset 0, flags [DF], proto ICMP
(1), length 84, bad cksum abdc (->acdb)!)
192.168.6.171 > 192.168.6.210: ICMP echo request, id 12829, seq 509,
length 64
02:10:14.050699 IP (tos 0x0, ttl 63, id 0, offset 0, flags [DF], proto ICMP
(1), length 84, bad cksum abdc (->acdb)!)
192.168.6.171 > 192.168.6.210: ICMP echo request, id 12829, seq 510,
length 64
02:10:15.058642 IP (tos 0x0, ttl 63, id 0, offset 0, flags [DF], proto ICMP
(1), length 84, bad cksum abdc (->acdb)!)
192.168.6.171 > 192.168.6.210: ICMP echo request, id 12829, seq 511,
length 64
02:10:16.066666 IP (tos 0x0, ttl 63, id 0, offset 0, flags [DF], proto ICMP
(1), length 84, bad cksum abdc (->acdb)!)
192.168.6.171 > 192.168.6.210: ICMP echo request, id 12829, seq 512,
length 64
02:10:17.074662 IP (tos 0x0, ttl 63, id 0, offset 0, flags [DF], proto ICMP
(1), length 84, bad cksum abdc (->acdb)!)
192.168.6.171 > 192.168.6.210: ICMP echo request, id 12829, seq 513,
length 64
02:10:18.082667 IP (tos 0x0, ttl 63, id 0, offset 0, flags [DF], proto ICMP
(1), length 84, bad cksum abdc (->acdb)!)
192.168.6.171 > 192.168.6.210: ICMP echo request, id 12829, seq 514,
length 64
02:10:19.090663 IP (tos 0x0, ttl 63, id 0, offset 0, flags [DF], proto ICMP
(1), length 84, bad cksum abdc (->acdb)!)
192.168.6.171 > 192.168.6.210: ICMP echo request, id 12829, seq 515,
length 64
02:10:20.098685 IP (tos 0x0, ttl 63, id 0, offset 0, flags [DF], proto ICMP
(1), length 84, bad cksum abdc (->acdb)!)
192.168.6.171 > 192.168.6.210: ICMP echo request, id 12829, seq 516,
length 64
02:10:21.106729 IP (tos 0x0, ttl 63, id 0, offset 0, flags [DF], proto ICMP
(1), length 84, bad cksum abdc (->acdb)!)
192.168.6.171 > 192.168.6.210: ICMP echo request, id 12829, seq 517,
length 64
02:10:22.114694 IP (tos 0x0, ttl 63, id 0, offset 0, flags [DF], proto ICMP
(1), length 84, bad cksum abdc (->acdb)!)
192.168.6.171 > 192.168.6.210: ICMP echo request, id 12829, seq 518,
length 64
02:10:23.122708 IP (tos 0x0, ttl 63, id 0, offset 0, flags [DF], proto ICMP
(1), length 84, bad cksum abdc (->acdb)!)
192.168.6.171 > 192.168.6.210: ICMP echo request, id 12829, seq 519,
length 64
02:10:24.130685 IP (tos 0x0, ttl 63, id 0, offset 0, flags [DF], proto ICMP
(1), length 84, bad cksum abdc (->acdb)!)
192.168.6.171 > 192.168.6.210: ICMP echo request, id 12829, seq 520,
length 64
#############################################################################################
Controller Node IP : 192.168.6.171
Compute Bode IP (Board) : 192.168.6.210
Our x86 is trying to make connection at 5269 port (xmpp) with controller
node , whereas the board is trying to make the connection at 5998 port.
Request is coming to both interface but reply is not happening..
What is the solution ?? and how to enable this xmpp server UP ??
Thanks,
--Vignesh
On Wed, Sep 23, 2015 at 12:16 PM, Rajagopalan Sivaramakrishnan <
[email protected]> wrote:
> Hi Vignesh,
> Are you able to ping the control node IP address from your board? If
> not, please use tcpdump to find out where packets are being dropped.
>
> Raja
>
> From: Dev <[email protected]> on behalf of Vigneshwaran
> R <[email protected]>
> Date: Tuesday, September 22, 2015 at 9:51 PM
> To: "[email protected]" <[email protected]>
> Subject: Re: [opencontrail-dev] Dev Digest, Vol 25, Issue 36
>
> Hi All,
>
> We checked all the above stuffs which you said, still we are not able to
> ping to outside world from board. We manually tried to make x86 system to
> act as a compute node by inserting kernel module and running
> contrail-vrouter-agent. Once we done this we are able to ping outside world
> with contrail-vrouter-agent running.
>
> But when we repeat the same steps in our board, pinging was not happening.
>
> While checking the logs, we came to know that problem is with xmpp.
>
> *X86 - Logs *
>
> ##############################################################################
> 2015-09-22 Tue 15:11:45:572.197 IST ubuntu [Thread 139779643537152, Pid
> 18018]: SANDESH: Send FAILED: 1442914905572157 [SYS_INFO]:
> XmppConnectionLog: connection= [ ip_address = 192.168.6.171 state = Idle
> next_state = Active event = Start ] file =
> controller/src/xmpp/xmpp_state_machine.cc line = 1264
>
> #############################################################################
>
> This log we are not getting in our board, ie xmpp connection is not
> getting active.
>
> Also in *x86* this is an additional log where dns-server is assigned with
> ip,
>
> ###############################################################################
> connection_infos= *[ [ [ type = XMPP name = control-node:192.168.6.171
> server_addrs= [ [ (*_iter6) = 192.168.6.171:5269
> <http://192.168.6.171:5269/>, ] ] status = Down description = Idle ], [
> type = XMPP name = dns-server:192.168.6.171 server_addrs= [ [ (*_iter6)
> =192.168.6.171:53 <http://192.168.6.171:53/>, ] ] status = Down
> description = Idle ],*
>
> [ type = Collector name = server_addrs= [ [ (*_iter6) =
> 192.168.6.171:8086, ] ] status = *Initializing description* = Connect :
> EvTcpConnected ], [ type = Discovery name = Collector server_addrs= [ [
> (*_iter6) = 192.168.6.171:5998, ] ] status = *Up description *=
> SubscribeResponse ], [ type = Discovery name = dns-server server_addrs= [
> [ (*_iter6) = 192.168.6.171:5998, ] ] status = *Up description* =
> SubscribeResponse ], [ type = Discovery name = xmpp-server server_addrs=
> [ [ (*_iter6) =192.168.6.171:5998, ] ] status = *Up description* =
> SubscribeResponse ], ] ] description = *XMPP:control-node:192.168.6.171,
> XMPP:dns-server:192.168.6.171, Collector connection down ], ] ] ]*
>
> ################################################################################
>
>
> but in *board *case, we are not getting that.
>
> #################################################################################
> connection_infos= [ [
>
> [ type = Collector name = server_addrs= [ [ (*_iter6) = 0.0.0.0:0, ]
> ] status =* Down description* = Idle : EvStart -> Disconnect ], [ type
> = Discovery name = Collector server_addrs= [ [ (*_iter6) =
> 192.168.6.171:5998, ] ] status = *Down description = *Timeout was reached
> ], [ type = Discovery name = dns-server server_addrs= [ [ (*_iter6) =
> 192.168.6.171:5998, ] ] status = *Down description* = Timeout was
> reached ], [ type = Discovery name = xmpp-server server_addrs= [ [
> (*_iter6) = 192.168.6.171:5998, ] ] status = *Down description* =
> Timeout was reached ], ] ] description = *Collector,
> Discovery:Collector, Discovery:dns-server, Discovery:xmpp-server connection
> down* ], ] ] ]
>
> ##################################################################################
>
> These are the difference between two logs.
>
> Now, how we can make this xmpp enable in board and also dns-server to
> establish communication ??
>
> Kindly help us in this..
>
> Thanks,
> --Vignesh
>
> On Mon, Sep 21, 2015 at 9:30 PM, <[email protected]>
> wrote:
>
>> Send Dev mailing list submissions to
>> [email protected]
>>
>> To subscribe or unsubscribe via the World Wide Web, visit
>>
>> http://lists.opencontrail.org/mailman/listinfo/dev_lists.opencontrail.org
>>
>> or, via email, send a message with subject or body 'help' to
>> [email protected]
>>
>> You can reach the person managing the list at
>> [email protected]
>>
>> When replying, please edit your Subject line so it is more specific
>> than "Re: Contents of Dev digest..."
>>
>>
>> Today's Topics:
>>
>> 1. no ping with contrail-vrouter-agent running (abhishek jain)
>>
>>
>> ----------------------------------------------------------------------
>>
>> Message: 1
>> Date: Mon, 21 Sep 2015 19:38:16 +0530
>> From: abhishek jain <[email protected]>
>> To: [email protected]
>> Subject: [opencontrail-dev] no ping with contrail-vrouter-agent
>> running
>> Message-ID:
>> <
>> ca+9-lvvqprxwqrjr-khaqhk823rdb-wubxn6aeezk20f7ct...@mail.gmail.com>
>> Content-Type: text/plain; charset="utf-8"
>>
>> Hi Team
>>
>>
>> I'm trying to configure powerpc ubuntu as contrail compute node and I'm
>> having following process running on it..
>>
>> ps -ef | grep contrail
>> root 27034 5751 0 08:39 pts/0 00:00:00 /usr/bin/python
>> /usr/bin/supervisord --nodaemon -c /etc/contrail/supervisord_vrouter.conf
>> root 27037 27034 0 08:39 pts/0 00:00:01 python
>> /usr/bin/contrail-nodemgr --nodetype=contrail-vrouter
>> root 27038 27034 52 08:39 pts/0 00:05:22
>> /usr/bin/contrail-vrouter-agent
>> root 27384 4554 0 08:49 ttyS0 00:00:00 grep --color=auto contrail
>>
>> The issue is when I'm running these above process,I'm not able to ping the
>> gw ip i.e 192.168.5.1 with compute node ip being 192.168.6.210 and
>> controller node Ip 192.168.6.171.
>>
>>
>>
>> 09-21 Mon 04:12:08:327.732 CDT t4240-ubuntu1310 [Thread 4115657792, Pid
>> 5420]: VnswInterfaceListenerBase Event ADD_ADDR Interface lo Addr
>> 127.0.0.1 prefixlen 8 Gateway 0.0.0.0 Flags 128 Protocol 0
>> 2015-09-21 Mon 04:12:08:327.791 CDT t4240-ubuntu1310 [Thread 4115657792,
>> Pid 5420]: VnswInterfaceListenerBase Event ADD_ADDR Interface vhost0
>> Addr 192.168.6.210 prefixlen 22 Gateway 0.0.0.0 Flags 128 Protocol 0
>> 2015-09-21 Mon 04:12:08:327.850 CDT t4240-ubuntu1310 [Thread 4115657792,
>> Pid 5420]: VnswInterfaceListenerBase Event ADD_ROUTE Interface vhost0
>> Addr 192.168.4.0 prefixlen 22 Gateway 0.0.0.0 Flags 0 Protocol 2
>> 2015-09-21 Mon 04:12:08:526.918 CDT t4240-ubuntu1310 [Thread 4143969344,
>> Pid 5420]: SANDESH: Send FAILED: 1184912310 Agent [SYS_INFO]: AgentRo
>> uteLog: Added route 192.168.6.171/32 in VRF
>> default-domain:default-project:ip-fabric:__default__ Local
>> controller/src/vnsw/agent/oper/agent_rou
>> te.cc 389
>> 2015-09-21 Mon 04:12:08:527.076 CDT t4240-ubuntu1310 [Thread 4143969344,
>> Pid 5420]: SANDESH: Send FAILED: 1184912465 Agent [SYS_INFO]: AgentRo
>> uteLog: Path add 192.168.6.171/32 in VRF
>> default-domain:default-project:ip-fabric:__default__ Local
>> controller/src/vnsw/agent/oper/agent_route.
>> cc 411
>> 2015-09-21 Mon 04:12:09:205.358 CDT t4240-ubuntu1310 [Thread 4126143552,
>> Pid 5420]: SANDESH: Send FAILED: 1185590716 Agent [SYS_INFO]: AgentRo
>> uteLog: Added route 192.168.5.254/32 in VRF
>> default-domain:default-project:ip-fabric:__default__ Local
>> controller/src/vnsw/agent/oper/agent_rou
>> te.cc 389
>> 2015-09-21 Mon 04:12:09:205.518 CDT t4240-ubuntu1310 [Thread 4126143552,
>> Pid 5420]: SANDESH: Send FAILED: 1185590882 Agent [SYS_INFO]: AgentRo
>> uteLog: Path add 192.168.5.254/32 in VRF
>> default-domain:default-project:ip-fabric:__default__ Local
>> controller/src/vnsw/agent/oper/agent_route.
>> cc 411
>> 2015-09-21 Mon 04:12:14:908.970 CDT t4240-ubuntu1310 [Thread 4124046400,
>> Pid 5420]: SANDESH: Send FAILED: 1191294341 Agent [SYS_INFO]: AgentRo
>> uteLog: Added route 192.168.5.255/32 in VRF
>> default-domain:default-project:ip-fabric:__default__ Local
>> controller/src/vnsw/agent/oper/agent_rou
>> te.cc 389
>> 2015-09-21 Mon 04:12:14:909.138 CDT t4240-ubuntu1310 [Thread 4124046400,
>> Pid 5420]: SANDESH: Send FAILED: 1191294502 Agent [SYS_INFO]: AgentRo
>> uteLog: Path add 192.168.5.255/32 in VRF
>> default-domain:default-project:ip-fabric:__default__ Local
>> controller/src/vnsw/agent/oper/agent_route.
>> cc 411
>> 2015-09-21 Mon 04:12:17:181.376 CDT t4240-ubuntu1310 [Thread 4092589120,
>> Pid 5420]: SANDESH: Send FAILED: 1193566650 NodeStatusUVE: data= [ na
>> me = t4240-ubuntu1310 process_status= [ [ [ module_id =
>> contrail-vrouter-agent instance_id = 0 state = Non-Functional
>> connection_infos= [ [
>> [ type = Collector name = server_addrs= [ [ (*_iter6) = 0.0.0.0:0, ]
>> ]
>> status = Down description = Idle : EvStart -> Disconnect ], [ type
>> = Discovery name = Collector server_addrs= [ [ (*_iter6) =
>> 192.168.6.171:5998, ] ] status = Down description = Timeout was reached
>> ], [ ty
>> pe = Discovery name = dns-server server_addrs= [ [ (*_iter6) =
>> 192.168.6.171:5998, ] ] status = Initializing description = Subscribe ],
>> [ t
>> ype = Discovery name = xmpp-server server_addrs= [ [ (*_iter6) =
>> 192.168.6.171:5998, ] ] status = Initializing description = Subscribe ],
>> ]
>> ] description = Collector, Discovery:Collector, Discovery:dns-server,
>> Discovery:xmpp-server connection down ], ] ] ]
>> 2015-09-21 Mon 04:12:17:181.596 CDT t4240-ubuntu1310 [Thread 4092589120,
>> Pid 5420]: SANDESH: Send FAILED: 1193566950 NodeStatusUVE: data= [ na
>> me = t4240-ubuntu1310 process_status= [ [ [ module_id =
>> contrail-vrouter-agent instance_id = 0 state = Non-Functional
>> connection_infos= [ [
>> [ type = Collector name = server_addrs= [ [ (*_iter6) = 0.0.0.0:0, ]
>> ]
>> status = Down description = Idle : EvStart -> Disconnect ], [ type
>> = Discovery name = Collector server_addrs= [ [ (*_iter6) =
>> 192.168.6.171:5998, ] ] status = Down description = Timeout was reached
>> ], [ ty
>> pe = Discovery name = dns-server server_addrs= [ [ (*_iter6) =
>> 192.168.6.171:5998, ] ] status = Initializing description = Subscribe ],
>> [ t
>> ype = Discovery name = xmpp-server server_addrs= [ [ (*_iter6) =
>> 192.168.6.171:5998, ] ] status = Down description = Timeout was reached
>> ],
>> ] ] description = Collector, Discovery:Collector, Discovery:dns-server,
>> Discovery:xmpp-server connection down ], ] ] ]
>> 2015-09-21 Mon 04:12:17:181.808 CDT t4240-ubuntu1310 [Thread 4092589120,
>> Pid 5420]: SANDESH: Send FAILED: 1193567168 NodeStatusUVE: data= [ na
>> me = t4240-ubuntu1310 process_status= [ [ [ module_id =
>> contrail-vrouter-agent instance_id = 0 state = Non-Functional
>> connection_infos= [ [
>> [ type = Collector name = server_addrs= [ [ (*_iter6) = 0.0.0.0:0, ]
>> ]
>> status = Down description = Idle : EvStart -> Disconnect ], [ type
>> = Discovery name = Collector server_addrs= [ [ (*_iter6) =
>> 192.168.6.171:5998, ] ] status = Down description = Timeout was reached
>> ], [ ty
>> pe = Discovery name = dns-server server_addrs= [ [ (*_iter6) =
>> 192.168.6.171:5998, ] ] status = Down description = Timeout was reached
>> ], [
>> type = Discovery name = xmpp-server server_addrs= [ [ (*_iter6) =
>> 192.168.6.171:5998, ] ] status = Down description = Timeout was reached
>> ],
>> ] ] description = Collector, Discovery:Collector, Discovery:dns-server,
>> Discovery:xmpp-server connection down ], ] ] ]
>>
>>
>> I have configured /etc/contrail/supervisord_vrouter.conf properly with
>> prper details and the tx/rx count of vhost0 is also increasing.
>>
>> Please help me regarding this.
>>
>> Thanks
>> Abhishek Jain
>> -------------- next part --------------
>> An HTML attachment was scrubbed...
>> URL: <
>> http://lists.opencontrail.org/pipermail/dev_lists.opencontrail.org/attachments/20150921/0615ff1c/attachment-0001.html
>> >
>>
>> ------------------------------
>>
>> Subject: Digest Footer
>>
>> _______________________________________________
>> Dev mailing list
>> [email protected]
>> http://lists.opencontrail.org/mailman/listinfo/dev_lists.opencontrail.org
>>
>>
>> ------------------------------
>>
>> End of Dev Digest, Vol 25, Issue 36
>> ***********************************
>>
>
>
_______________________________________________
Dev mailing list
[email protected]
http://lists.opencontrail.org/mailman/listinfo/dev_lists.opencontrail.org
