Connectrix Brocade：固件下载在备用 CP 上失败 — 固件下载超时 (0x23)
摘要: FOS 从 v8.2.1c 升级到 v8.2.2d 失败，原因是“Firmware download failed on standby CP - Firmware download timed out. (0x23)
本文适用于
本文不适用于
本文并非针对某种特定的产品。
本文并非包含所有产品版本。
症状
在交换机升级期间观察到 CP 之间的环回通信。
在 CP 上的固件下载期间，两个 CP 都重新启动，并在后端重新获得通信。
通过下面所示的示例增加固件下载命令的超时值不起作用。
在此示例中，它将超时从默认值 30 分钟（1800 秒）增加到 40 分钟（2400 秒）。
在 CP 上的固件下载期间，两个 CP 都重新启动，并在后端重新获得通信。
Apr 6 01:22:42 softupgrade_main:CP1 ### Firmwaredownload command has started ###
Apr 6 01:22:42 softupgrade_main:CP1 IpcInit failed. Firmwaredownloadis already running.
Apr 6 01:22:42 set_status:CP1 Firmwaredownload failed because already another instance of firmwaredownload operation is in progress. Another firmwaredownload is in progress. (0x18)
Apr 6 01:28:06 ipc_send_recv:CP1 err = 35, error_code = 35
Apr 6 01:28:25 set_status:CP1 Firmware download failed on standby CP - Firmware download timed out. (0x23)
Apr 6 01:28:25 state_fwdl_begin:CP1 Firmwaredownload status in state_trans(): Firmware download timed out.
Apr 6 01:28:30 sus_notify:CP1 Firmwaredownload failed. Calling ismic_send_fwdnld_fail.
Apr 6 01:28:31 sus_notify:CP1 Status is SUS_NOTIFY_FWDL_FAILED
Apr 6 01:28:33 ping_standby:CP1 ping_standby(): cmd = /bin/ping -q 127.3.1.1 -c 2 -i 2 1>/dev/null, ret=0x0
Apr 6 01:28:33 ping_standby:CP1 ping_standby failed but htbt ok. Ignore
Apr 6 01:29:22 fwdl_parse_cmd_option:CP1 option=0, index = 1
Apr 6 01:29:54 set_status:CP1 Firmwarecommit has started on the remote CP. Please use firmwaredownloadstatus and firmwareshow to see the firmware status.
Apr 6 01:29:54 set_status:CP1 Please use firmwaredownloadstatus and firmwareshow to see the firmware status.
Apr 6 01:29:54 state_fwdl_begin:CP1 Returning SUS_PEER_FWDL_FAIL
Mar 23 22:37:16 set_status:CP1 Firmware download failed on standby CP - Firmware download timed out. (0x23)
Mar 23 22:37:16 state_fwdl_begin:CP1 Firmwaredownload status in state_trans(): Firmware download timed out.
Mar 23 22:37:21 sus_notify:CP1 Firmwaredownload failed. Calling ismic_send_fwdnld_fail.
Mar 23 22:37:21 sus_notify:CP1 Status is SUS_NOTIFY_FWDL_FAILED
Mar 23 22:37:23 ping_standby:CP1 ping_standby(): cmd = /bin/ping -q 127.3.1.1 -c 2 -i 2 1>/dev/null, ret=0x0
Mar 23 22:37:23 ping_standby:CP1 ping_standby failed but htbt ok. Ignore
Mar 23 22:38:44 set_status:CP1 Firmwarecommit has started on the remote CP. Please use firmwaredownloadstatus and firmwareshow to see the firmware status.
Mar 23 22:38:45 set_status:CP1 Please use firmwaredownloadstatus and firmwareshow to see the firmware status.
Mar 23 22:38:45 state_fwdl_begin:CP1 Returning SUS_PEER_FWDL_FAIL
Apr 6 01:22:42 softupgrade_main:CP1 IpcInit failed. Firmwaredownloadis already running.
Apr 6 01:22:42 set_status:CP1 Firmwaredownload failed because already another instance of firmwaredownload operation is in progress. Another firmwaredownload is in progress. (0x18)
Apr 6 01:28:06 ipc_send_recv:CP1 err = 35, error_code = 35
Apr 6 01:28:25 set_status:CP1 Firmware download failed on standby CP - Firmware download timed out. (0x23)
Apr 6 01:28:25 state_fwdl_begin:CP1 Firmwaredownload status in state_trans(): Firmware download timed out.
Apr 6 01:28:30 sus_notify:CP1 Firmwaredownload failed. Calling ismic_send_fwdnld_fail.
Apr 6 01:28:31 sus_notify:CP1 Status is SUS_NOTIFY_FWDL_FAILED
Apr 6 01:28:33 ping_standby:CP1 ping_standby(): cmd = /bin/ping -q 127.3.1.1 -c 2 -i 2 1>/dev/null, ret=0x0
Apr 6 01:28:33 ping_standby:CP1 ping_standby failed but htbt ok. Ignore
Apr 6 01:29:22 fwdl_parse_cmd_option:CP1 option=0, index = 1
Apr 6 01:29:54 set_status:CP1 Firmwarecommit has started on the remote CP. Please use firmwaredownloadstatus and firmwareshow to see the firmware status.
Apr 6 01:29:54 set_status:CP1 Please use firmwaredownloadstatus and firmwareshow to see the firmware status.
Apr 6 01:29:54 state_fwdl_begin:CP1 Returning SUS_PEER_FWDL_FAIL
Mar 23 22:37:16 set_status:CP1 Firmware download failed on standby CP - Firmware download timed out. (0x23)
Mar 23 22:37:16 state_fwdl_begin:CP1 Firmwaredownload status in state_trans(): Firmware download timed out.
Mar 23 22:37:21 sus_notify:CP1 Firmwaredownload failed. Calling ismic_send_fwdnld_fail.
Mar 23 22:37:21 sus_notify:CP1 Status is SUS_NOTIFY_FWDL_FAILED
Mar 23 22:37:23 ping_standby:CP1 ping_standby(): cmd = /bin/ping -q 127.3.1.1 -c 2 -i 2 1>/dev/null, ret=0x0
Mar 23 22:37:23 ping_standby:CP1 ping_standby failed but htbt ok. Ignore
Mar 23 22:38:44 set_status:CP1 Firmwarecommit has started on the remote CP. Please use firmwaredownloadstatus and firmwareshow to see the firmware status.
Mar 23 22:38:45 set_status:CP1 Please use firmwaredownloadstatus and firmwareshow to see the firmware status.
Mar 23 22:38:45 state_fwdl_begin:CP1 Returning SUS_PEER_FWDL_FAIL
通过下面所示的示例增加固件下载命令的超时值不起作用。
#firmwaredownload -x 2400
在此示例中，它将超时从默认值 30 分钟（1800 秒）增加到 40 分钟（2400 秒）。
原因
CP 之间的环回通信问题
解决方案
使用作为单个 CP 控制器升级的 #firmwaredownload -s 选项升级交换机 CP
- 使用命令 #firmwaredownload -s 将固件下载到备用 CP，并执行 #hafailover 重新启动。
- 在其他 CP 上执行相同的操作。
其他信息
"Firmware download timed out. （0x23）" 不是错误，因为它通常是由于 Brocade 交换机的以太网端口与 SFTP/FTP/SCP 服务器之间的定时问题造成的。
因此，使用 "firmwaredownload -s" 减少了在使用正常 "firmwaredownlaod" 命令时协调从活动 CP 到备用 CP 的文件传输所需的时间（因为命令将首先使用“备用”CP 启动固件升级）。
过去，此类问题已通过检查以太网端口设置、延长超时值或（在这种情况下）客户在每个 CP 上使用 "firmwaredownload -s" 命令来绕过 CP 之间通信所需的额外时间来解决。
由于这些 CP 已在固件下载期间重新启动，因此在下次升级时不应再次出现此问题。
因此，使用 "firmwaredownload -s" 减少了在使用正常 "firmwaredownlaod" 命令时协调从活动 CP 到备用 CP 的文件传输所需的时间（因为命令将首先使用“备用”CP 启动固件升级）。
过去，此类问题已通过检查以太网端口设置、延长超时值或（在这种情况下）客户在每个 CP 上使用 "firmwaredownload -s" 命令来绕过 CP 之间通信所需的额外时间来解决。
由于这些 CP 已在固件下载期间重新启动，因此在下次升级时不应再次出现此问题。
受影响的产品
Brocade文章属性
文章编号: 000185590
文章类型: Solution
上次修改时间: 01 8月 2021
版本: 3
从其他戴尔用户那里查找问题的答案
支持服务
检查您的设备是否在支持服务涵盖的范围内。