Hi Venu, Inline.
> On Dec 27, 2020, at 8:17 AM, Venumadhav Josyula <vjosy...@gmail.com> wrote: > > Hi Florin, > > Thanks, that helped. Now I have question, please > vpp# show session verbose proto tcp > [0:1][T] 0.0.0.0:1234->0.0.0.0:0 <http://0.0.0.0:0/> > LISTEN 0 0 > [0:2][T] 172.168.2.60:1234->172.168.1.40:44874 <http://172.168.1.40:44874/> > ESTABLISHED 306296 0 > Thread 0: 2 sessions matched filter > vpp# show session verbose > Connection State > Rx-f Tx-f > [0:0][CT:T] 0.0.0.0:1234->0.0.0.0:0 <http://0.0.0.0:0/> > LISTEN 0 0 > [0:1][T] 0.0.0.0:1234->0.0.0.0:0 <http://0.0.0.0:0/> > LISTEN 0 0 > [0:2][T] 172.168.2.60:1234->172.168.1.40:44874 <http://172.168.1.40:44874/> > ESTABLISHED 306296 0 > Thread 0: active sessions 3 > vpp# > > Question, > i) what is 0.0.0.0 session for ? This is a listener session. The app bound to port 1234 and 0/0 (or INADDR_ANY). > ii) why 2) That’s a cut-through session because the app has requested local scoped connections. See [1] around slide 16. > iii) why not number of session(s) only one ? You have one established session and 2 listeners (local and global scope). Regards, Florin [1] https://wiki.fd.io/images/9/9c/Vpp-hoststack-kc-eu19.pdf <https://wiki.fd.io/images/9/9c/Vpp-hoststack-kc-eu19.pdf> > > Thanks, > Regards, > Venu > > > On Thu, 24 Dec 2020 at 23:29, Florin Coras <fcoras.li...@gmail.com > <mailto:fcoras.li...@gmail.com>> wrote: > Hi Venu, > > That last error "vcl_bapi_init:604: vcl<682:0>: ERROR couldn't connect to > VPP!” pretty much explains everything. VCL is trying to connect over the > binary api to vpp and it can’t find the socket. Make sure that vpp exposes > the binary api’s socket where you want (/var/run as far as I can tell from > lower) by adding "socksvr { socket-name /var/run/vpp-api.sock }" to vpp’s > startup.conf. And then add the same to vcl.conf "api-socket-name > /var/run/vpp-api.sock”. > > If you want to use the session layer’s socket api (not the binary api with > socket transport) add to vpp’s startup.conf "session { use-app-socket-api }” > and to vcl "app-socket-api /var/run/vpp/app_ns_sockets/default”. > > More conf info here [1] and here [2] > > Regards, > Florin > > [1] https://wiki.fd.io/view/VPP/HostStack/VCL > <https://wiki.fd.io/view/VPP/HostStack/VCL>[2] > https://wiki.fd.io/view/VPP/HostStack/SessionLayerArchitecture#Session_Layer_Startup_Configuration > > <https://wiki.fd.io/view/VPP/HostStack/SessionLayerArchitecture#Session_Layer_Startup_Configuration> > >> On Dec 24, 2020, at 4:35 AM, Venumadhav Josyula <vjosy...@gmail.com >> <mailto:vjosy...@gmail.com>> wrote: >> >> Hi >> Setup details :- >> Two dockers created using following commands >> vpp docker >> >> creation :- >> docker run --privileged -it -d -v /var/run:/var/run -v /dev:/dev -v >> /dev/shm:/dev/shm --cap-add=CAP_SYS_ADMIN --cap-add=CAP_NET_ADMIN --name >> vpp-run-c1 vpp-run:1.0 /usr/sbin/init >> >> VPP Libraries installed >> [root@aa7c1125718d vpp-rpm]# rpm -qa | grep vpp >> vpp-lib-21.06-rc0~27_g7b0fa55.x86_64 >> vpp-plugins-21.06-rc0~27_g7b0fa55.x86_64 >> vpp-api-python3-21.06-rc0~27_g7b0fa55.x86_64 >> vpp-debuginfo-21.06-rc0~27_g7b0fa55.x86_64 >> vpp-selinux-policy-21.06-rc0~27_g7b0fa55.x86_64 >> vpp-21.06-rc0~27_g7b0fa55.x86_64 >> vpp-api-lua-21.06-rc0~27_g7b0fa55.x86_64 >> vpp-devel-21.06-rc0~27_g7b0fa55.x86_64 >> [root@aa7c1125718d vpp-rpm]# >> >> startup.conf >> unix { >> nodaemon >> interactive >> log /var/log/vpp/vpp.log >> full-coredump >> cli-listen localhost:5002 >> } >> dpdk { >> dev 0000:00:08.0 >> uio-driver igb_uio >> } >> logging { >> default-syslog-log-level info >> default-log-level info >> } >> session { >> enable >> } >> api-trace { >> on >> } >> vcl.conf >> vcl { >> max-workers 1 >> use-app-socket-api >> } >> >> vcl-server docker >> Creation >> docker run -it -d -v /var/run:/var/run -v /dev/shm:/dev/shm --name >> vcl-server-1 stackpod-img:1.0 >> >> VPP Libraries installed >> [root@8a41dfa6780e vcl-server]# rpm -qa | grep vpp >> vpp-lib-21.06-rc0~27_g7b0fa55.x86_64 >> vpp-selinux-policy-21.06-rc0~27_g7b0fa55.x86_64 >> [root@8a41dfa6780e vcl-server]# >> >> vcl.conf is present but empty. It is present in /etc/vpp/vcl.conf >> >> We are getting following error when starting the vcl_test_server // please >> we are trying to bringup the basic >> [root@8a41dfa6780e vcl-server]# ./vcl_test_server -p tcp 1234 >> vcl_bapi_init:604: vcl<682:0>: ERROR couldn't connect to VPP! >> ERROR when calling vppcom_app_create(): Invalid argument >> >> ERROR: vppcom_app_create() failed (errno = 22)! >> Segmentation fault (core dumped) >> [root@8a41dfa6780e vcl-server]# >> >> >> It would nice, if somebody told us what might be missing or what is the >> additional information required. >> >> Thanks, >> Regards, >> Venu >> >> >> >
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#18433): https://lists.fd.io/g/vpp-dev/message/18433 Mute This Topic: https://lists.fd.io/mt/79200852/21656 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
