Core dump file of dp-ipc55 generated on NSX Edge node
search cancel

Core dump file of dp-ipc55 generated on NSX Edge node

book

Article ID: 374020

calendar_today

Updated On:

Products

VMware NSX

Issue/Introduction

  • An application on an NSX Edge node crashed, resulting in a core dump file of dp-ipc55 being generated.
  • Log lines similar to the below are encountered in /var/log/syslog

Sample logs from /var/log/syslog

NSX 7519 FABRIC [nsx@6876 comp="nsx-edge" subcomp="datapathd" s2comp="phys-port" tname="dp-ipc55" level="INFO"] Set mtu for port 1 : 9000
NSX 7519 FABRIC [nsx@6876 comp="nsx-edge" subcomp="datapathd" s2comp="intel-rte" tname="dp-ipc55" level="INFO"] Reconfiguring port 1 - drv net_i40e
NSX 7519 FABRIC [nsx@6876 comp="nsx-edge" subcomp="datapathd" s2comp="intel-rte" tname="dp-ipc55" level="WARN"] i40e_phy_conf_link(): Failed to get PHY capabilities: -56#012
NSX 7519 FABRIC [nsx@6876 comp="nsx-edge" subcomp="datapathd" s2comp="intel-rte" tname="dp-ipc55" level="WARN"] i40e_dev_sync_phy_type(): Failed to sync phy type: status=-56
NSX 7519 FABRIC [nsx@6876 comp="nsx-edge" subcomp="datapathd" s2comp="intel-rte" tname="dp-ipc55" level="WARN"] Configure failed for port 1, err: Operation not supported
NSX 7519 FABRIC [nsx@6876 comp="nsx-edge" subcomp="datapathd" s2comp="intel-rte" tname="dp-ipc55" level="WARN"] Port 1 setup/configure error: Operation not supported
NSX 7519 FABRIC [nsx@6876 comp="nsx-edge" subcomp="datapathd" s2comp="intel-rte" tname="dp-ipc55" level="WARN"] Failed to init port 1 : Operation not supported
NSX 7519 FABRIC [nsx@6876 comp="nsx-edge" subcomp="datapathd" s2comp="phys-port" tname="dp-ipc55" level="WARN"] Failed to start port 1 for MTU change (mtu: 9000) ret: -95; attempting to roll back config
NSX 7519 FABRIC [nsx@6876 comp="nsx-edge" subcomp="datapathd" s2comp="intel-rte" tname="dp-ipc55" level="INFO"] Reconfiguring port 1 - drv net_i40e
NSX 7519 FABRIC [nsx@6876 comp="nsx-edge" subcomp="datapathd" s2comp="intel-rte" tname="dp-ipc55" level="WARN"] update_link_aq(): Failed to get link info
NSX 7519 FABRIC [nsx@6876 comp="nsx-edge" subcomp="datapathd" s2comp="intel-rte" tname="dp-ipc55" level="INFO"] Device with port_id=1 already stopped
NSX 7519 FABRIC [nsx@6876 comp="nsx-edge" subcomp="datapathd" s2comp="intel-rte" tname="dp-ipc55" level="INFO"] Setting up port 1; driver net_i40e, tx_q: 24 rx_q: 25
NSX 7519 FABRIC [nsx@6876 comp="nsx-edge" subcomp="datapathd" s2comp="intel-rte" tname="dp-ipc55" level="INFO"] Requested RSS on port 1 not subset of capabilities: rss_hf 0x2db4, capa 0x7ef8
NSX 7519 FABRIC [nsx@6876 comp="nsx-edge" subcomp="datapathd" s2comp="intel-rte" tname="dp-ipc55" level="WARN"] i40e_dev_sync_phy_type(): Failed to sync phy type: status=-56
NSX 7519 FABRIC [nsx@6876 comp="nsx-edge" subcomp="datapathd" s2comp="intel-rte" tname="dp-ipc55" level="WARN"] Port1 dev_configure = -95
NSX 7519 FABRIC [nsx@6876 comp="nsx-edge" subcomp="datapathd" s2comp="intel-rte" tname="dp-ipc55" level="WARN"] Configure failed for port 1, err: Operation not supported
NSX 7519 FABRIC [nsx@6876 comp="nsx-edge" subcomp="datapathd" s2comp="intel-rte" tname="dp-ipc55" level="WARN"] Port 1 setup/configure error: Operation not supported
NSX 7519 FABRIC [nsx@6876 comp="nsx-edge" subcomp="datapathd" s2comp="intel-rte" tname="dp-ipc55" level="WARN"] Failed to init port 1 : Operation not supported
NSX 7519 FABRIC [nsx@6876 comp="nsx-edge" subcomp="datapathd" s2comp="intel-rte" tname="dp-ipc55" level="FATAL"] PANIC in phys_port_set_mtu():
NSX 7519 FABRIC [nsx@6876 comp="nsx-edge" subcomp="datapathd" s2comp="intel-rte" tname="dp-ipc55" level="FATAL"] Rollback failed. Bailing out.
datapathd 7519 intel-rte tname="dp-ipc55" [FATAL] PANIC in phys_port_set_mtu():
datapathd 7519 intel-rte tname="dp-ipc55" [FATAL] Rollback failed. Bailing out.
datapathd 7519 intel-rte tname="dp-ipc55" [FATAL] PANIC in phys_port_set_mtu():
datapathd 7519 intel-rte tname="dp-ipc55" [FATAL] Rollback failed. Bailing out.

Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Environment

VMware NSX

Cause

The syslog messages indicate that the physical network interface driver didn't complete some of its functions properly.
It eventually led to PANIC in phys_port_set_mtu() function and the core dump file generated.

Resolution

This is a condition that may occur in a VMware NSX environment.

Contact hardware vendor to check the NIC driver/firmware and hardware.