2018 War smoke--cisco 6800IA inexplicably restarted!

The last few times in the user site troubleshooting have found Cisco 6800IA inexplicably restarted, view log messages as follows (this is the log that is crawled today):

Jan 11:27:22:%SATMGR-SW1-5-FABRIC_PORT_DOWN:SDP down on Interface Te1/3/8, connected to FEX 101, uplink (reason:s DP Timeout)
Jan 11:27:22:%satmgr-sw1-5-fex_module_offline:fex 101, MODULE 1 OFFLINE (Reason:all fabric links down)
Jan 11:27:22:%SATMGR-SW1-5-FABRIC_PORT_DOWN:SDP down on Interface TE1/3/7, connected to FEX 101, uplink Wuyi (reason:s DP Timeout)
Jan 11:27:22:%oir-sw1-6-insrem:switch 101 physical Slot 1-module Type Line_card removed
Jan 03:27:28.115:SW1:%ha_em-6-log:mandatory.go_fabriclinkstatus.tcl:gold EEM tcl Policy for Testfexfabriclinkstatus
Jan 11:27:28:%const_diag-sw1-6-rsl_link_down:rsl LINK on Module 3 Port 7-8 are down
Jan 11:32:06:%SATMGR-SW1-5-FABRIC_PORT_UP:SDP up in interface Te1/3/8, connected to FEX 101, uplink 52
Jan 11:32:09:%satmgr-sw1-5-online:fex 101 ONLINE
Jan 11:32:09:%satmgr-sw1-5-fex_module_online:fex 101, MODULE 1 ONLINE
Jan 11:32:09:%oir-sw1-6-insrem:switch 101 physical Slot 1-module Type Line_card inserted
Jan 11:32:06.554:%link-3-updown:interface port-channel1, changed state-to-up (FEX-101)
Jan 11:32:07:%lineproto-5-updown:line protocol on Interface Port-channel1, changed state-to-up (FEX-101)
Jan 11:32:12:%SATMGR-SW1-5-FABRIC_PORT_UP:SDP up in interface TE1/3/7, connected to FEX 101, uplink 51
Jan 11:32:24:%diag-sw1-6-run_minimum:fex 101 Module 1:running Minimal Diagnostics ...
Jan 11:32:24:%diag-sw1-6-diag_ok:fex 101 Module 1:passed Online Diagnostics
Jan 11:32:25:%oir-sw1-6-sp_inscard:card inserted in switch_number = 101, physical slot 1,interfaces is now online

Check the 6807XL and 6800IA connection ports, cables, found everything normal, check the core configuration, also did not find any special case.

Check the iOS version, found that the version of the device is relatively old, from the device online to now has not been upgraded, is it a software bug? When you decide to upgrade your system! The upgrade steps are not explained here!

After the upgrade has been completed until this morning, 6800IA is working properly, did not restart, however, this noon and restarted again, the hell!

Before asked excessively Niang, but the degree Niang did not give any useful clue. There is no way to go to the official website to take a chance, did not expect to really let the Blind cat met dead rats ... Here is a section of the official website!

C6800/ia:fex crash when a host port configured as SPAN destination
CSCuo88038
Description
Symptom:
In Catalyst 6800/ia setup, when a host port was configured as SPAN destination, it may cause crash/reset the FEX.

Logs reported:
%SATMGR-SW1-5-FABRIC_PORT_DOWN:SDP down in interface, connected to FEX, uplink (Reason:link down)
Satmgr-sw1-3-err_dual_active_detect_incapable:channel Group is no longer dual-active detection capable

Conditions:
Issue is seen only after configuring the host port as SPAN Destination Port

Workaround:
Move the SPAN destination to the parent/controller switch.

The above paragraph basically means: If you do port mirroring, the port on the 6800IA for the destination port, it will cause a 6800IA restart.

Not to mention, we've done a monitor session on 6800IA before these reboots. There are 10,000 small animals running through the heart.

Here, it is not done after the monitor session will be restarted, today is done after a clutch, after a period of time to restart.

Before a colleague at the scene also did a clutch operation, and then 6800IA restarted, colleagues said: "I will not catch the bag to restart it?" I said: It is not so Jin Gui, not ... Come on, now finally know is caught bag caused! 6800IA What do you want me to say about you?

View documents further

The document says the affected iOS version and the version of the bug has been fixed, but be aware that the iOS version mentioned here is not for the sup6t engine. sup6t What iOS is affected, and which versions have been repaired temporarily not found! The tragedy is that what I'm using here is the sup6t version ...

Although I haven't found the right version for the time being, I know where the problem is.

2018 War smoke--cisco 6800IA inexplicably restarted!