Hi, Correct, there wasn’t any C3 discard due to timeout. These c3 discards are probably related to “er_other_discard” or “er_unreachable” or “er_unroutable”. See Knowledgebase article; 00037925 : [URL] And the also check the output of the command portstatsshow in the supportshow that should show the other discards.       Regards, Ed Schulte  
Hi all, I got a output below. porterrshow        :          frames      enc    crc    crc    too    too    bad    enc   disc   link   loss   loss   frjt   fbsy  c3timeout    pcs       tx     rx      in    err    g_eof  shrt   long   eof     out   c3    fail    sync   sig                  tx    rx     err  1:  292.6m 596.4m   0      0      0      0      0      0      0     75      0      0      0      0      0      0      0      0    There are 75 disc c3 errors but no c3timeout errors. "A frame can be discarded for a number of reasons; Timeout, destination unreachable, zone discard, or other reasons for discard. Most of the time you will see timeout, which means a frame is longer than E_D_TOV in the buffer." With this output, can I 100% eliminate the timeout from the reasons that causes the disc c3 errors? Thanks in advance.    
Does the porterrshow output (disc c3 errors without c3timeout) mean there 
wasn't I/O timeout at all?