What is the reason for the high load on the cisco 7609 router?

Question

Highload

Messages began to appear in the show logging system accompanied by a high load on the cisco processor:
115: 07/29/15 11:53:01 0/0: MAJOR, GOLD, diag_hit_sp_sys_limit[8/1]: sp cpu is busy (81util)! Inband rate tx 903753 rx 1615!
116: 07/29/15 11:53:01 0/0: MAJOR, GOLD, test_synched_fabchan_health[2]: diag_get_fabric_status unknown
117: 07/29/15 11:53:01 0/0: MAJOR, GOLD, diag_hit_sp_sys_limit[2 /1]: sp cpu is busy (81util)! Inband rate tx 903753 rx 1615!
118:07/29/15 11:53:00 0/0: MAJOR, GOLD, fabric_health_hm_test[8/6]:diag_hit_sp_sys_limit!test skipped.
119:07/29/15 11:53:00 0/0: MAJOR, GOLD, diag_hit_sp_sys_limit[8/6]: sp cpu is busy (81util)! Inband rate tx 471096 rx 1348!
120: 07/29/15 11:53:00 0/0: MAJOR, GOLD, test_synced_fabchan_health[1]: diag_get_fabric_status unknown
121: 07/29/15 11:53:00 0/0: MAJOR, GOLD, diag_hit_sp_sys_limit[1 /1]: sp cpu is busy (81util)! Inband rate tx 471096 rx 1348!
122: 07/29/15 11:53:00 0/0: MAJOR, GOLD, test_synched_fabchan_health[7]: diag_get_fabric_status unknown
123: 07/29/15 11:53:00 0/0: MAJOR, GOLD, diag_hit_sp_sys_limit[7 /1]: sp cpu is busy (81util)! Inband rate tx 471096 rx 1348!
124:07/29/15 11:53:00 0/0: MAJOR, GOLD, fabric_health_hm_test[7/10]:diag_hit_sp_sys_limit!test skipped.
125: 07/29/15 11:53:00 0/0: MAJOR, GOLD, diag_hit_sp_sys_limit[7/10]: sp cpu is busy (81util)! Inband rate tx 471096 rx 1348!
126: 07/29/15 11:51:23 2/-1: MAJOR, GOLD, TestErrorCounterMonitor: ID:49 IN:0 PO:255 RE:231 RM:6 DV:10 EG:2 CF:1 TF:42980
127: 07/29/15 11:51:23 2/-1: MAJOR, GOLD, TestErrorCounterMonitor: ID:49 IN:0 PO:255 RE:231 RM:5 DV:10 EG:2 CF:1 TF:34231
I wonder what they mean and what does it show rx-tx in?

Answer 1

Tests fail due to high CPU usage.
rx-tx in packets.
You can also look at sh cpu proc hist
Mirror ports and sniff.
It is better to hire a person who can solve this problem, your tsiska costs more than a novice networker earns in a year.
If the goal is to try to do something (NB! You can break it), then start from here www.cisco.com/c/en/us/support/docs/interfaces-modu... Yes, according to the nexus, but the essence is the same.
*here on iOS www.cisco.com/c/en/us/support/docs/switches/cataly...
The solution to your problem is definitely here: www.cisco.com/c/en/us/support/routers/7609 -router/...