Unable to SSH to the ESXi host due to a missing uplink.

Products

• VMware vSphere ESXi

Issue/Introduction

The source (A.A.A.A) is unable to SSH into the ESXi host (B.B.B.B) due to the absence of a SYN/ACK response from the host, as observed in the packet capture on the vmk0 uplink.

1    0    0.000000    <DATE_TIME>    A.A.A.A    B.B.B.B    TCP    ##    ##### → 22 [SYN] Seq=# Win=##### Len=0 MSS=#### SACK_PERM TSval=########## TSecr=# WS=### 2    0    1.001159    <DATE_TIME>    A.A.A.A    B.B.B.B    TCP    ##    [TCP Retransmission] ##### → 22 [SYN] Seq=# Win=##### Len=# MSS=#### SACK_PERM TSval=########## TSecr=# WS=### 3    0    2.005993    <DATE_TIME>    A.A.A.A    B.B.B.B    TCP    ##    [TCP Retransmission] ##### → 22 [SYN] Seq=# Win=##### Len=# MSS=#### SACK_PERM TSval=########## TSecr=# WS=### 4    0    4.008367    <DATE_TIME>    A.A.A.A    B.B.B.B    TCP    ##    [TCP Retransmission] ##### → 22 [SYN] Seq=# Win=##### Len=# MSS=#### SACK_PERM TSval=########## TSecr=# WS=### 5    0    8.008007    <DATE_TIME>    A.A.A.A    B.B.B.B    TCP    ##    [TCP Retransmission] ##### → 22 [SYN] Seq=# Win=##### Len=# MSS=#### SACK_PERM TSval=########## TSecr=# WS=###

 

According to the routing table from the output of 'esxcfg-route -l -N defaultTcpipStack' command, the outbound packets destined for the source should be routed via vmk1.

VMkernel Routes: Network          Netmask          Gateway          Interface A.A.A.0       255.255.255.0       A.A.A.1            vmk1 default          0.0.0.0                 B.B.B.1           vmk0

 

However, the output of the 'netdbg vswitch instance list' command reveals that vmk1 does not have an assigned uplink with its status displayed as void.

vSwitch# () Total Ports:#### Available:####   Client                         PortID          DVPortID                             MAC                         Uplink          VID              VNI   vmk1                          #########                                              ##:##:##:##:##:##    void             N/A              N/A

 

Environment

VMware vSphere ESXi

Cause

It is detected in /var/run/log/vmkwarning.log that the missing uplink is caused because of the firmware reset failure.

<DATE_TIME> Wa(###) vmkwarning: cpu##:#######)WARNING: i40en: i40en_InitSharedCode:####: ####:##:##.#: Initial pf_reset failed: I40E_ERR_RESET_FAILED <DATE_TIME> Wa(###) vmkwarning: cpu##:#######)WARNING: i40en: i40en_CheckEmprCount:####: ####:##:##.#: Entering recovery mode due to repeated FW resets. This may take several minutes. Refer to the Intel(R) Ethernet Adapters and Devices User Guide <DATE_TIME> Wa(###) vmkwarning: cpu##:#######)WARNING: i40en: indrv_Attach:####: ####:##:##.#: Failed to init shared code <DATE_TIME> Wa(###) vmkwarning: cpu##:#######)WARNING: i40en: i40en_CheckRecoveryMode:####: ####:##:##.#: Firmware recovery mode detected. Limiting functionality. Refer to the Intel(R) Ethernet Adapters and Devices User Guide for details on firmware re$

Resolution

Contact the hardware vendor to investigate the cause of the firmware reset failure.