开始新对话

未解决

Community Manager

 • 

6.3K 消息

465

2020年8月23日 23:00

VxFlex:回切时出现 ESXi NIC 团队连接中断 (000539367)

 

知识库文章:000539367

回切时出现 ESXi NIC 团队连接中断 (000539367)

主要产品:VxFlex 产品系列

 

产品:VxFlex 产品系列、VxFlex OS、VxFlex 就绪节点、VxRack Flex 系列、VxRack Flex-PowerEdge 13G、VxRack Flex-PowerEdge 14G

版本:3

文章类型:中断修复

目标受众:
级别 10 = 公用

上次发布时间:2020 年 3 月 27 日(星期五),7:23:28 GMT

 

总结:

当使用组队 NIC 且重新启动一个交换机时,ESXi SDC 将中断与 SDS/MDM 的连接

 

问题:

场景

当 NIC 上出现链路指示灯时,ESXi 会回切到最近中断的 NIC,并且交换机在几分钟内不会转发数据包。

症状

需要注意的是,交换机中断时不会发生中断,但必须在要重新启动的交换机成功启动时进行。 

ESXi 主机的 vmkernel 日志将显示通用 SDC 断开连接,套接字故障:

2019-09-09T16:16:36.858Z cpu49:66336)WARNING: ScaleIO netCon_IsKaNeeded:3758 :CON 0x4395857ff480 didn't receive message for 30 iterations.  Marking as down

2019-09-09T16:16:36.858Z cpu51:66657)WARNING: ScaleIO netSock_RcvIntrn:1920 :Error: Failed  to receive 128 data PTR 0x4395857ff7fc socket 0x4395857ffd10

2019-09-09T16:16:36.958Z cpu49:66336)WARNING: ScaleIO netCon_IsKaNeeded:3758 :CON 0x439d827f9ac0 didn't receive message for 30 iterations.  Marking as down

2019-09-09T16:16:36.958Z cpu49:66336)WARNING: ScaleIO netCon_IsKaNeeded:3758 :CON 0x439d827f40c0 didn't receive message for 30 iterations.  Marking as down

2019-09-09T16:16:36.958Z cpu49:66336)WARNING: ScaleIO netCon_IsKaNeeded:3758 :CON 0x439d827f6280 didn't receive message for 30 iterations.  Marking as down

2019-09-09T16:16:36.958Z cpu8:66787)WARNING: ScaleIO netSock_RcvIntrn:1920 :Error: Failed  to receive 128 data PTR 0x439d827f9e3c socket 0x439d827fa350

2019-09-09T16:16:36.958Z cpu49:66336)WARNING: ScaleIO netCon_IsKaNeeded:3758 :CON 0x439d827fbc80 didn't receive message for 30 iterations.  Marking as down

2019-09-09T16:16:36.958Z cpu49:66336)WARNING: ScaleIO netCon_IsKaNeeded:3758 :CON 0x439d827f6dc0 didn't receive message for 30 iterations.  Marking as down

2019-09-09T16:16:36.958Z cpu49:66336)WARNING: ScaleIO netCon_IsKaNeeded:3758 :CON 0x439d827fe980 didn't receive message for 30 iterations.  Marking as down

2019-09-09T16:16:36.958Z cpu49:66336)WARNING: ScaleIO netCon_IsKaNeeded:3758 :CON 0x439d827f8f80 didn't receive message for 30 iterations.  Marking as down

2019-09-09T16:16:36.958Z cpu49:66336)WARNING: ScaleIO netCon_IsKaNeeded:3758 :CON 0x439d827fc7c0 didn't receive message for 30 iterations.  Marking as down

2019-09-09T16:16:36.958Z cpu49:66336)WARNING: ScaleIO netCon_IsKaNeeded:3758 :CON 0x439d827ff4c0 didn't receive message for 30 iterations.  Marking as down

2019-09-09T16:16:36.958Z cpu49:66336)WARNING: ScaleIO netCon_IsKaNeeded:3758 :CON 0x439d827f3580 didn't receive message for 30 iterations.  Marking as down

2019-09-09T16:16:36.958Z cpu62:66792)WARNING: ScaleIO netSock_RcvIntrn:1920 :Error: Failed  to receive 128 data PTR 0x439d827f443c socket 0x439d827f4950

2019-09-09T16:16:36.959Z cpu46:66798)WARNING: ScaleIO netSock_RcvIntrn:1920 :Error: Failed  to receive 128 data PTR 0x439d827f65fc socket 0x439d827f6b10

2019-09-09T16:16:36.959Z cpu43:66803)WARNING: ScaleIO netSock_RcvIntrn:1920 :Error: Failed  to receive 128 data PTR 0x439d827fbffc socket 0x439d827fc510

2019-09-09T16:16:36.959Z cpu46:66804)WARNING: ScaleIO netSock_RcvIntrn:1920 :Error: Failed  to receive 128 data PTR 0x439d827f713c socket 0x439d827f7650

2019-09-09T16:16:36.959Z cpu53:66815)WARNING: ScaleIO netSock_RcvIntrn:1920 :Error: Failed  to receive 128 data PTR 0x439d827fecfc socket 0x439d827ff210

2019-09-09T16:16:36.959Z cpu38:66816)WARNING: ScaleIO netSock_RcvIntrn:1920 :Error: Failed  to receive 128 data PTR 0x439d827f92fc socket 0x439d827f9810

2019-09-09T16:16:36.960Z cpu36:66822)WARNING: ScaleIO netSock_RcvIntrn:1920 :Error: Failed  to receive 128 data PTR 0x439d827fcb3c socket 0x439d827fd050

2019-09-09T16:16:36.960Z cpu21:66821)WARNING: ScaleIO netSock_RcvIntrn:1920 :Error: Failed  to receive 128 data PTR 0x439d827ff83c socket 0x439d827ffd50

2019-09-09T16:16:36.961Z cpu17:66791)WARNING: ScaleIO netSock_RcvIntrn:1920 :Error: Failed  to receive 128 data PTR 0x439d827f38fc socket 0x439d827f3e10

 

影响

卷访问中断,DU。  

 

原因:

根本原因

某些型号的 Cisco 交换机可在转发流量前打开其网络端口/ASIC。 

ESXi 的组队功能将链路启动状态视为交换机可随时转发流量,并且在交换机实际开始转发之前不会转发任何内容。

 

 

解决方案:

解决方法

Net.TeamPolicyUpDelay 设置为大于从交换机启动端口至可实际转发流量的持续时间(以毫秒为单位)。 

Configure System Advanced System Settings 下方根据主机找到该设置。

在此客户的环境中,延迟因使用中的交换机而异。  

大多数现代 Cisco 型号在三分钟内就已准备就绪,但它们选择最多 60,000ms(十分钟),以便与较旧交换机兼容。

 

备注:

受影响的版本

不适用 - 非 ScaleIO 问题。 

已解决问题的版本

不适用 - 非 ScaleIO 问题。 

 

主要产品:

VxFlex 产品系列

 

产品:

VxFlex 产品系列、VxFlex OS、VxFlex 就绪节点、VxRack Flex 系列、VxRack Flex-PowerEdge 13G、VxRack Flex-PowerEdge 14G

 

EMC 内部信息:

高价值内容

#IWork4Dell

请您将合适的回复标记为“接受的回答”,并为喜欢的帖子“点赞”。这对我们非常重要!

没有回复!
找不到事件!

Top