When a user connects via SSH switch starts dropping packets and generates kernel messages:
The issue came in as not being able to ssh into the switch, they only have console access. The cust can ping the mgmt0 IP but when they ssh to it, they get no prompt and they start dropping pings. You can see where the ssh daemon wigs out below.
This is 5K-b which is the secondary peer. The config on this 5K matches the other one.
Cisco’s output interpreter doesn’t show anything.
2012 Mar 1 22:12:20 AMEDWRAIRNX5K02 Mar 1 22:12:20 %KERN-3-SYSTEM_MSG: igb: eth0: igb_clean_tx_irq: Detected Tx Unit Hang - kernel
2012 Mar 1 22:12:22 AMEDWRAIRNX5K02 Mar 1 22:12:22 %KERN-3-SYSTEM_MSG: igb: eth0: igb_clean_tx_irq: Detected Tx Unit Hang - kernel
2012 Mar 1 22:12:24 AMEDWRAIRNX5K02 Mar 1 22:12:24 %KERN-3-SYSTEM_MSG: igb: eth0: igb_clean_tx_irq: Detected Tx Unit Hang - kernel
2012 Mar 1 22:12:26 AMEDWRAIRNX5K02 Mar 1 22:12:26 %KERN-3-SYSTEM_MSG: igb: eth0: igb_clean_tx_irq: Detected Tx Unit Hang - kernel
2012 Mar 1 22:12:29 AMEDWRAIRNX5K02 %IM-5-IM_INTF_STATE: mgmt0 is DOWN in vdc 1
2012 Mar 1 22:12:32 AMEDWRAIRNX5K02 %IM-5-IM_INTF_STATE: mgmt0 is UP in vdc 1
…
2012 May 15 14:22:57 AMEDWRAIRNX5K02 May 15 14:22:57 %KERN-3-SYSTEM_MSG: igb: eth0: igb_clean_tx_irq: Detected Tx Unit Hang - kernel
2012 May 15 14:22:59 AMEDWRAIRNX5K02 May 15 14:22:59 %KERN-3-SYSTEM_MSG: igb: eth0: igb_clean_tx_irq: Detected Tx Unit Hang - kernel
2012 May 15 14:23:01 AMEDWRAIRNX5K02 May 15 14:23:01 %KERN-3-SYSTEM_MSG: igb: eth0: igb_clean_tx_irq: Detected Tx Unit Hang - kernel
2012 May 15 14:23:03 AMEDWRAIRNX5K02 May 15 14:23:03 %KERN-3-SYSTEM_MSG: igb: eth0: igb_clean_tx_irq: Detected Tx Unit Hang - kernel
2012 May 15 14:23:05 AMEDWRAIRNX5K02 May 15 14:23:05 %KERN-3-SYSTEM_MSG: igb: eth0: igb_clean_tx_irq: Detected Tx Unit Hang - kernel
2012 May 15 14:23:08 AMEDWRAIRNX5K02 %IM-5-IM_INTF_STATE: mgmt0 is DOWN in vdc 1
2012 May 15 14:23:11 AMEDWRAIRNX5K02 %IM-5-IM_INTF_STATE: mgmt0 is UP in vdc 1
2012 May 15 14:25:05 AMEDWRAIRNX5K02 May 15 14:25:05 %KERN-3-SYSTEM_MSG: igb: eth0: igb_clean_tx_irq: Detected Tx Unit Hang - kernel
2012 May 15 14:25:07 AMEDWRAIRNX5K02 May 15 14:25:07 %KERN-3-SYSTEM_MSG: igb: eth0: igb_clean_tx_irq: Detected Tx Unit Hang - kernel
2012 May 15 14:25:09 AMEDWRAIRNX5K02 May 15 14:25:09 %KERN-3-SYSTEM_MSG: igb: eth0: igb_clean_tx_irq: Detected Tx Unit Hang - kernel
2012 May 15 14:25:11 AMEDWRAIRNX5K02 May 15 14:25:11 %KERN-3-SYSTEM_MSG: igb: eth0: igb_clean_tx_irq: Detected Tx Unit Hang - kernel
2012 May 15 14:25:13 AMEDWRAIRNX5K02 May 15 14:25:13 %KERN-3-SYSTEM_MSG: igb: eth0: igb_clean_tx_irq: Detected Tx Unit Hang - kernel
2012 May 15 14:25:14 AMEDWRAIRNX5K02 %IM-5-IM_INTF_STATE: mgmt0 is DOWN in vdc 1
2012 May 15 14:25:17 AMEDWRAIRNX5K02 %IM-5-IM_INTF_STATE: mgmt0 is UP in vdc 1
2012 May 15 14:27:13 AMEDWRAIRNX5K02 May 15 14:27:13 %KERN-3-SYSTEM_MSG: igb: eth0: igb_clean_tx_irq: Detected Tx Unit Hang - kernel
2012 May 15 14:27:15 AMEDWRAIRNX5K02 May 15 14:27:15 %KERN-3-SYSTEM_MSG: igb: eth0: igb_clean_tx_irq: Detected Tx Unit Hang - kernel
2012 May 15 14:27:17 AMEDWRAIRNX5K02 May 15 14:27:17 %KERN-3-SYSTEM_MSG: igb: eth0: igb_clean_tx_irq: Detected Tx Unit Hang - kernel
2012 May 15 14:27:19 AMEDWRAIRNX5K02 May 15 14:27:19 %KERN-3-SYSTEM_MSG: igb: eth0: igb_clean_tx_irq: Detected Tx Unit Hang - kernel
2012 May 15 14:27:21 AMEDWRAIRNX5K02 May 15 14:27:21 %KERN-3-SYSTEM_MSG: igb: eth0: igb_clean_tx_irq: Detected Tx Unit Hang - kernel
2012 May 15 14:27:23 AMEDWRAIRNX5K02 %IM-5-IM_INTF_STATE: mgmt0 is DOWN in vdc 1
2012 May 15 14:27:26 AMEDWRAIRNX5K02 %IM-5-IM_INTF_STATE: mgmt0 is UP in vdc 1
2012 May 15 14:28:15 AMEDWRAIRNX5K02 %DAEMON-2-SYSTEM_MSG: fatal: Read from socket failed: Connection timed out - sshd[4355]
I want to kill/restart the ssh dameon. Will "no feature ssh" and "feature ssh" restart the cpu process. Or is there another way?
