Dear Charlie,
Vpp won't touch an interface if it has an associated Linux kernel interface
which is up, and/or has an address configured on it. Manually unbinding the
interface - as you did - makes the Linux kernel interface disappear.
Accidentally whitelisting a host's management ethernet would be a Bad Thing.
"Hmmm... Why can't I ping the box anymore, let alone ssh to it..."
HTH... Dave
From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On
Behalf Of Li, Charlie
Sent: Wednesday, January 3, 2018 2:29 PM
To: vpp-dev@lists.fd.io
Subject: [vpp-dev] VPP does not detect NIC automatically
Hi VPP team,
I am new to VPP and am following the "FDIO Quick Start Guide"
(https://docs.google.com/document/d/1zqYN7qMavgbdkPWIJIrsPXlxNOZ_GhEveHQxpYr3qrg/edit)
to get started.
I am running Ubuntu 16.04 and using the pre-built packages.
According to the document, vpp should detect and take over the Ethernet ports
that are not in use (link down). But on my system, vpp does not detect any
interfaces except the "local0".
# ps -eaf | grep vpp
root991 1 99 Nov28 ?2-06:13:50 /usr/bin/vpp -c
/etc/vpp/startup.conf
root 83025 83014 0 15:34 pts/800:00:00 grep --color=auto vpp
# lspci
...
01:00.0 Ethernet controller: Intel Corporation 82599ES 10-Gigabit SFI/SFP+
Network Connection (rev 01)
01:00.1 Ethernet controller: Intel Corporation 82599ES 10-Gigabit SFI/SFP+
Network Connection (rev 01)
...
# vppctl show int
Name Idx State Counter Count
local00down
Then I add the two interfaces to the whitelist in startup.conf
## Whitelist specific interface by specifying PCI address
dev :01:00.0
dev :01:00.1
And restart vpp, but it still does not detect the interfaces.
As a workaround, I manually bind the interfaces
~/dpdk/usertools/dpdk-devbind.py -b uio_pci_generic :01:00.0
~/dpdk/usertools/dpdk-devbind.py -b uio_pci_generic :01:00.1
And restart vpp; now everything starts to work.
Is this as expected or did I miss something?
Regards,
Charlie Li
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev
