Re: [vpp-dev] VPP crashes because of API segment exhaustion

Hello Florin, > > Agreed that it looks like vl_api_clnt_process sleeps, probably because it > hit a queue size of 0, but memclnt_queue_callback or the timeout, albeit > 20s is a lot, should wake it up. It doesn't look like vl_api_clnt_process would have woken up later. Firstly, because

[vpp-dev] VPP crashes because of API segment exhaustion

Hello all, We are experiencing VPP crashes that occur a few days after the startup because of API segment exhaustion. Increasing API segment size to 256MB didn't stop the crashes from occurring. Can you please take a look at the description below and tell us if you have seen similar issues or

Re: [vpp-dev] NAT ED empty users dump #nat #nat44

Ole, OK, nat44_user_dump is not going to return anything in NAT ED. nat44_user_session_dump has required fields ( ip_address and vrf_id) that don't allow you to dump all the sessions. If make those fields optional, that should work. Addition of sort and limit optional fields is a good idea

Re: [vpp-dev] NAT ED empty users dump #nat #nat44

Hello Ole, I'm not sure I get your question right. The use case is being able to see NAT pool utilization and debug NAT sessions. I  think it's not a specific use case. NAT44 ED sessions: thread 0 vpp_main: 3 sessions i2o 10.255.10.100 proto icmp port 1593 fib 0 o2i

Re: [vpp-dev] NAT ED empty users dump #nat #nat44

Klement, I would prefer the existing API working. I expect millions of sessions and it's clear that dumping them all is a blocker but during debug, there are not so many of them. Thanks, Alexander -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online

Re: [vpp-dev] NAT ED empty users dump #nat #nat44

Klement, Basically print statistics and debug info: number of users, what user consumes what number of sessions, what session created for what communication. Thanks, Alexander -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#16334):

Re: [vpp-dev] NAT ED empty users dump #nat #nat44

Hello Klement, I want to list all NAT sessions. In order to do that I used to call VL_API_NAT44_USER_DUMP. After that, I had all users, and I could call VL_API_NAT44_USER_SESSION_DUMP to get sessions for every user. Now VL_API_NAT44_USER_DUMP returns nothing in ED mode and I don't know what

[vpp-dev] NAT ED empty users dump #nat #nat44

Hello, As I understand the "users" concept has been removed from NAT ED and now vl_api_nat44_user_dump_t returns nothing in ED mode. vl_api_nat44_user_session_dump_t returns sessions only if you know the user you are requesting sessions for. But you can't get the user list. Therefore this

Re: [vpp-dev] Events for IP address addition/deletion on an interface #vpp

Hi Ole, > > Where is the IP address configuration coming from? If it's your > application that configures the addresses, shouldn't the control plane > application know that itself? There are several independent instances of the application. If one of them configures the addresses, others

[vpp-dev] Events for IP address addition/deletion on an interface #vpp

Hello, I have an application that is a client to the shared memory API and I would like to know when an IP address has been added or deleted on an interface. I see that there is sw_interface_event that can notify a client about interface admin/link status changes as well as interface deletion.

[vpp-dev] Question about #16465 patch

Hello, I have a question about this path: https://gerrit.fd.io/r/#/c/16465/ There was a comment about used terminology ("dev instance" vs "ID") that I addressed but no further actions after this. Can you clarify what would be needed to get the patch accepted? Thanks, Alexander