- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
Sep 17 2025
Sep 16 2025
Sep 15 2025
@a.kudientsov could you confirm and close the task?
@a.kudientsov could you confirm and close the task?
@hedrok could you re-check and mark as solved if all work as expected?
The lease still cannot be cleared T7823
vyos@r14:~$ show dhcp server leases IP Address MAC address State Lease start Lease expiration Remaining Pool Hostname Origin ------------ ----------------- ------- ------------------------- ------------------------- ----------- ------ ---------- -------- 100.64.2.10 52:54:00:96:17:74 active 2025-09-15 10:47:13+00:00 2025-09-16 10:47:13+00:00 23:57:02 LANv42 r15 local 100.64.2.11 52:54:00:09:0b:01 active 2025-09-15 10:47:28+00:00 2025-09-16 10:47:28+00:00 23:57:17 LANv42 r15 local vyos@r14:~$ vyos@r14:~$ vyos@r14:~$ clear dhcp-server lease 100.64.2.10 Failed to clear lease for "100.64.2.10" vyos@r14:~$ vyos@r14:~$ clear dhcp-server lease 100.64.2.11 Failed to clear lease for "100.64.2.11" vyos@r14:~$ vyos@r14:~$ vyos@r14:~$ show dhcp server leases IP Address MAC address State Lease start Lease expiration Remaining Pool Hostname Origin ------------ ----------------- ------- ------------------------- ------------------------- ----------- ------ ---------- -------- 100.64.2.10 52:54:00:96:17:74 active 2025-09-15 10:47:13+00:00 2025-09-16 10:47:13+00:00 23:56:52 LANv42 r15 local 100.64.2.11 52:54:00:09:0b:01 active 2025-09-15 10:47:28+00:00 2025-09-16 10:47:28+00:00 23:57:07 LANv42 r15 local vyos@r14:~$
DHCP-server starts 2 processes when only the VRF is configured T7822
One process with under VRF context and another without VRF, but the file is the same. Looks like a bug.
Check:
Sep 11 2025
Sep 10 2025
Sep 6 2025
Do you see logs while doing sudo journalctl -f ?
We do not handle/process the /var/log/vpp.log at least by our scripts/configs.
Sep 5 2025
Sep 4 2025
At least 2 CPUs should be for the system processes (Not VPP)
So the error looks handled correctly if you have 8 cores and are trying to use 7 cores.
So, max-number-cores - 2, you can use for VPP even if you isolate 7.
Needs the correction of the error message to be clearer.
It's already disallowed. Vpp is not started with proper error message
Thread(s) per core: 2 Core(s) per socket: 2 Socket(s): 1
The calculation is okay for me: 1 socket, 2 cores. Threads or virtual cores will do more harm than good to performance. Should we disallow starting VPP on such instances?
Sep 3 2025
Sep 1 2025
Looks like a feature
What about option priority?
set container name c1 priority 1 set container name c2 priority 2
Aug 30 2025
@marvin, I think you can claim it