Reference Guide

Force10 Service Agent | 363
</item>
</content>
</action_list_message>
Excessive CRC-error policy configuration
The following FTSA policy configuration uses the interface-crc match condition to monitor
GigabitEthernet 1/2 for greater than 500 CRC errors. When this condition exists, FTSA triggers the action
list, which captures a partial output of the command
show interfaces gigabitethernet 1/2.
Configuring an FTSA Policy for an Excessive CRC-error Condition
call-home
admin-email [e-mail]
smtp server-address 192.168.1.1
no enable-all
server FTOS
recipient [e-mail]
keyadd Force10DefaultPublicKey
no encrypt
enable
no log-messages
policy crcerror
action-list crcerror
test-list crcerror
policy-test-list crcerror
test-condition interface-crc 1 greater-than number 500
policy-action-list crcerror
no log-only
message-format text
cli-show "show int gig 1/2 | grep CRC" repeat 1 delay 1
System Syslog Messages during an Excessive CRC-error Condition
R6_E300(conf)#do show int gig 1/2 | grep CRC
0 CRC, 0 overrun, 0 discarded
R6_E300(conf)#do show int gig 1/2 | grep CRC
105 CRC, 0 overrun, 105 discarded
R6_E300(conf)#do show int gig 1/2 | grep CRC
183 CRC, 0 overrun, 183 discarded
R6_E300(conf)#do show int gig 1/2 | grep CRC
285 CRC, 0 overrun, 285 discarded
R6_E300(conf)#do show int gig 1/2 | grep CRC
399 CRC, 0 overrun, 399 discarded
R6_E300(conf)#do show int gig 1/2 | grep CRC
501 CRC, 0 overrun, 501 discarded
R6_E300(conf)#02:27:01: %RPM0-P:CP %CALL-HOME-HELPER-3-CALLHOME: Callhome service sent
a message to Force10 at [e-mail]
FTSA Type 5 Message for an Excessive CRC-error Condition
--------------------------------Message Body------------------------------------------
<AgentInfo>
<messagetype>Type - 5</messagetype>
<time>21:10:04.678 UTC Tue Mar 10 2009</time>
<serialnum>0036232 </serialnum>