Brocade Fibre Channel Networking Community

Expand all | Collapse all

understanding porterrshow

  • 1.  understanding porterrshow

    Posted 04-04-2018 02:31 PM

    Can someone explain to me the TX and RX counters. Or confirm what I THINK is occurring.  I pulled the porterrshow on a switch last week and the TX and RX counters showed....

             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

     93:  613.4m   3.1g   0      0      0      0      0      0      0      0      0      0      0      0      0      0      0      0

     104:    1.1g 587.7m   0      0      0      0      0      0     21      0      0      0      0      0      0      0      0      0

     

    Today they show..

              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

    93:    3.6g   4.2g   0      0      0      0      0      0      0      0      0      0      0      0      0      0      0      0

    104:    4.0g   3.3g   0      0      0      0      0      0     21      0      0      0      0      0      0      0      0      0

     

    Do the TX and RX counters reset to 0 after they hit 999.9m frames?

     

    Thanks.

     


    #BrocadeFibreChannelNetworkingCommunity


  • 2.  Re: understanding porterrshow

    Posted 04-04-2018 11:37 PM

    Hi,

     

    no they don't.

     

    From the Comand Ref:

     

    Counts are reported on frames transmitted by the port (Tx) or on frames received by the port (Rx). The display contains one output line per port. Numeric values exceeding 999 are displayed in units of thousands (k), millions (m), or giga (g) if indicated.

     

    So you had millions and now you are in the giga range.

     

    TL


    #BrocadeFibreChannelNetworkingCommunity


  • 3.  Re: understanding porterrshow

    Posted 04-05-2018 06:21 AM
    The counters will wrap to zero when they will reach the maximum, which is obviously 0xFFFFFFFF for 32 bit counters and 0xFFFFFFFFFFFFFFFF for 64 bit counters.
    #BrocadeFibreChannelNetworkingCommunity


  • 4.  Re: understanding porterrshow

    Posted 04-04-2018 11:37 PM

    Hello,

     

    As you mentioned TX and RX are counting transmitted or received frames by particular port.

    There is only one difference between your ouputs.

     

    In first one you have postfix mega, on second one there is postfix giga.

    No, the the TX and RX counters didnt reset to 0 after they hit 999.9m frames, they simple changed to 1g.

     


    #BrocadeFibreChannelNetworkingCommunity


  • 5.  Re: understanding porterrshow

    Posted 04-05-2018 02:30 PM

    There are 32bit and 64bit counters provided in later FOS levels.

     

    A 32bit counter has a max reading of 4,294,967,296  or 4.2g.  The porterrshow uses the 32bit counter.

    I doubt you will see the tx or rx frame counter every exceed 4.2g before reverting back to zero and re-incrementing.

    If you want the exact count use the command portstatsshow XX (where XX is the port index).

     

    On a very busy port it's quite possible for the porterrshow tx/rx frame counter to wrap after several minutes

    as ever frame in tx/rx count is represents an i/o.

     

     

    Example:  

    Porterrshow  of port index 2

    /fabos/cliexec/porterrshow :
              frames      enc    crc    crc    too    too    bad    enc   disc   link   loss   loss   frjt   fbsy  c3timeout    pcs    uncor
              tx        rx      in    err    g_eof  shrt   long   eof     out   c3    fail    sync   sig                  tx    rx     err    err
      2:    3.2g   1.0g   0      0      0      0      0      0      0      0      0      0      0      0      0      0      0      0      0  

     

    portstatsshow 2
    stat_ftx                3249149040          Frames transmitted  <= 3.2g
    stat_frx                1069238593          Frames received       <=1.0g

     

    A 64bit counter is also available in command output portstats64show.

    64bit counter equates to 18,446,744,073,709,551,616.  Instead of showing such a ridiculously large

    value the portstats64show has an upper and lower register.  The 32 bit upper register value represents

    the number of times the 32-bit lower register wrapped.   Although I believe you can

    view the actual 64bit count by using "portstats64show XX -long" command.

     

    Most of this info is in the FOS command guide under portstatsshow and portstats64show.


    #BrocadeFibreChannelNetworkingCommunity