I'm unable to see the ENI DBDF from the Virtual Ethernet Application

Question

I am trying out the capabilities of DPDK, and folowing the Virtual Ethernet Application Guide [here](https://github.com/aws/aws-fpga/blob/f2/sdk/apps/virtual-ethernet/doc/Virtual_Ethernet_Application_Guide.md#packetgen-dual-instance-loopback)

I have an aws instance (ubuntu) that I want to use as the packet generator. I have already installed the packet generator and set up the additional Network Interface. However, following the guide (pic 1), when I use lspci (pic 2) there is no device with device id "1d0f:ec20". Please advise on how to solve this, thanks you.

![guide](/media/postImages/original/IMXoszm20nQmmeh1lKIzbz6w)

![lspci](/media/postImages/original/IM0JF9a-WJTZWqxjMJqq_Wlg)

Steven T · Accepted Answer

The virtual ethernet examples were tested on an f2.6xlarge instance for the Virtual Ethernet instance and a m5.2xlarge instance for the packet generator. Both of these instance types support Enhanced Networking. The bot post brings up good questions about verifying the instance type supports ENI and it is actually attached and enabled.

I noticed on some Ubuntu releases, lspci does not output the VendorID and DeviceID of the devices so the grep will not work. On these distributions, running the following will show the attached ENIs.

```
lspci -d 1d0f:ec20
```

re:Post Agent · Answer

Based on the information provided, it appears you're encountering an issue with identifying the Elastic Network Interface (ENI) on your AWS EC2 instance while trying to set up DPDK (Data Plane Development Kit) for a virtual Ethernet application.

The fact that you can't see the expected device ID (1d0f:ec20) in the lspci output suggests that either the ENI is not properly attached to your instance, or the instance type you're using may not support the specific network interface you're looking for.

To troubleshoot this issue:

1. Verify that you have indeed attached an additional network interface to your EC2 instance as mentioned in the guide.

2. Check if your instance type supports Enhanced Networking. Not all instance types support this feature, which is required for certain advanced networking capabilities.

3. Ensure that Enhanced Network Adapter (ENA) is enabled on your instance. ENA is required for advanced networking features on many modern EC2 instance types.

4. If ENA is supported but not enabled, you may need to enable it. This typically involves stopping the instance, enabling the ENA attribute, and then starting the instance again.

5. After confirming ENA is enabled, reboot your instance and check the lspci output again.

6. If you still don't see the expected device, consider checking the EC2 console to verify the status of your network interfaces and ensure they are correctly attached to your instance.

If these steps don't resolve the issue, you may need to consult AWS support or the DPDK community forums for more specific guidance related to your instance type and configuration.  
**Sources**  
[Can Not Enable ENA | AWS re:Post](https://repost.aws/questions/QUm5iVTgLETXKHZN1Um3JG-A/can-not-enable-ena)  
[How to MAP ENI with ETH | AWS re:Post](https://repost.aws/questions/QUHxN1YaNhRSmoi2vm49BzJg/how-to-map-eni-with-eth)

I'm unable to see the ENI DBDF from the Virtual Ethernet Application

Add your answer

Relevant content