Hi Team,
I am facing an issue when I try to set the interface to DHCP Client on
VPP-20.01 with worker thread enabled in the startup.conf.
Environment Used:
1. Vpp 20.01 running on a Ubuntu 16.01 VM.
2. Two CPU cores allocated
cat /proc/cpuinfo | grep processor
processor : 0
processor : 1
[Edited Message Follows]
Hi Team,
I am facing an issue when I try to set the interface to DHCP Client on
VPP-20.01 with worker thread enabled in the startup.conf.
Environment Used:
1. Vpp 20.01 running on a Ubuntu 16.01 VM.
2. Two CPU cores allocated
cat /proc/cpuinfo | grep processor
process
Hi,
This should have been fixed with https://gerrit.fd.io/r/c/vpp/+/27183
It is merged in master and VPP 20.05 (but not 20.01 which is no longer
maintained).
The best should be to upgrade to 20.05.
ben
> -Original Message-
> From: vpp-dev@lists.fd.io On Behalf Of
> ais...@gmail.com
> S
Hi Ben,
This patch seems to be already applied in VPP20.01.
int
dhcp_client_for_us (u32 bi, vlib_buffer_t * b,
ip4_header_t * ip,
udp_header_t * udp, dhcp_header_t * dhcp)
{
dhcp_client_main_t *dcm = &dhcp_client_main;
*vlib_main_t *vm = dcm->vlib_main;*
dhcp_client_t *c;
uword *p;
*f64 now = vlib
Hi Dave,
Thanks, on a VM I am observing the reduction from a couple of
microseconds to 50 microseconds at times
NTP was turned on. After turning it off, I don't see the time reduction.
The output of the command is below
vppctl show clock verbose
Time now 16712.719968, reftime 16712.719967, error
That's within reason given that thread time offsets are not recalculated
immediately, and that (for stability reasons) the clock-rate update algorithm
uses exponential smoothing.
Aside from accounting for the issue in your code, there probably isn't much to
be done about it...
D
-Original
Hi,
We have added sr policies in VPP using VPP C API. We now want to fetch these
policy data similar to what we get in "show sr policies", using VPP C API. How
can we fetch this data using VPP C API so that the segment list indices are
similar to those in "show sr policies" command?
Below is a s
Thanks Dave.
Yes I have taken care of that in my code. I always use the highest
value seen as the ceiling in the logic of my code. If I see a lower
value I use the ceiling else move on and record the new ceiling.
Earlier math counted on an increasing value, so bad things were
happening in my code,
Dave/Steven,
I set the netmask on both sides to 255.255.255.0 and here is how I setup the ip
address on the 2 servers. System-B has ip address set using vppctl and system-A
was setup using ifconfig, as below. The link is up on both enp2s0f1np1 on
System A and bnxt0 on System B. VPP version used
HI Amit,
Here's a patch which I think will fix the problem:
https://gerrit.fd.io/r/c/vpp/+/27563. If you are able to build with the
patch applied and test it, that would be very helpful.
Thanks,
-Matt
On Sun, Jun 14, 2020 at 12:51 AM Amit Mehra wrote:
> Thanks Muthu Raj for the Response.
>
>
Manoj,
Because system B is running VPP, you can’t initiate the ping from system B in
Unix Shell. Kernel does not have that interface and IP address anymore for you
to do the ping. You have to start the ping from vppctl if you want to do the
ping from system B running VPP.
When you do the ping
Steven,
vppctl does not have a ping command I am on version 20.5 (may be I did not
compile this option?) Also not sure how to parse this trace output.
When I ping System B from System A and run the trace on SystemB I get the
following output:
$ sudo vppctl show trace
--- Start
Hi Manoj,
You need to enable ping_plugin.so and then you would be able to see the
ping CLI command
On Mon, 15 Jun, 2020, 10:11 pm Manoj Iyer, wrote:
> Steven,
>
> vppctl does not have a ping command I am on version 20.5 (may be I did not
> compile this option?) Also not sure how to parse this t
Steve,
Oh wow! I enabled the ping plugin, ( it was ping_plugin.so without the 's') and
restarted VPP, and I was able to ping from one machine to the VPP interface of
the other! Thanks a million!
== System A with VPP interface ==
$ sudo vppctl show interface address
bnxt0 (up):
L3 10.1.1.10/24
14 matches
Mail list logo
