ESXi Host
- Use
lspci
in the ESXi host to confirm that VFs are configured. For example:lspci | grep Solarflare 0000:81:00.0 Network controller: Solarflare SFC9220 [vmnic4] 0000:81:00.1 Network controller: Solarflare SFC9220 [vmnic5]
and:
lspci | grep "81:00" 0000:81:00.0 Network controller: Solarflare SFC9220 [vmnic4] 0000:81:00.1 Network controller: Solarflare SFC9220 [vmnic5] 0000:81:00.2 Network controller: [PF_0.129.0_VF_0] 0000:81:00.3 Network controller: [PF_0.129.0_VF_1]
and:
lspci | grep _VF_ 0000:81:00.2 Network controller: [PF_0.129.0_VF_0] 0000:81:00.3 Network controller: [PF_0.129.0_VF_1]
- Check network topology (vswitch and port group) for VM connectivity. In the
following example, there are two VMs: vm-ptp and vm-ptp2. Each VM
has its own VF from the physical adapter in the host:
Note: A VF does not use a port-group for sending/receiving traffic. The port-group is used only to apply networking properties such as VLAN ID.
Local Master
Check the /var/lib/sfptpd/topology file:
- The ptp grandmaster will identify the upstream PTP master clock.
- The state is ptp-slave.
- The offsets for GM to adapter and adapter to system are recorded.
==================== state: ptp-slave interface: ens224 (ens224) timestamping: hw ==================== grandmaster 0050:c2ff:fede:95b7/1 | | 9.000 ns | | v phc0(ens224) 000c:29ff:fed2:7455 | | -4.438 ns | | v system
- Check Local Master VM SRIOV adapter configuration:
Freerun VMs
Check /var/lib/sfptpd/topology file:
- The state is freerun
- The adapter clock is identified
- The offset of the guest OS system clock from adapter clock is recorded.
==================== state: freerun ==================== phc0(ens224) 000c:29ff:fed2:7455 | | -2.562 ns | | v system system
- Check VM SRIOV adapter configuration:
Tcpdump
The standard Linux tcpdump
can be used in the Linux guest to confirm that PTP
traffic is being received by the VF:
# tcpdump -i <sfptpd VF interface> dst port 319 or dst port 320
(PTP only uses ports 319 and 320.)