1. Forum
  2. USENET
  3. comp.sys.tandem

  • Utility/Commands to Check CRC Error in NonStop

    From Bry Pas@bryanpascua88@gmail.com to comp.sys.tandem on Fri Mar 31 05:46:28 2023
    From Newsgroup: comp.sys.tandem

    Hello,

    How to check for CRC errors on Ports in NonStop system. Or are there any utility/commands to check for CRC errors?


    --- Synchronet 3.21d-Linux NewsLink 1.2
  • From Gary Hall@gh961170@gmail.com to comp.sys.tandem on Sat Apr 1 02:36:42 2023
    From Newsgroup: comp.sys.tandem

    Hello,

    Depends. Which OS release (D-Series, G-Series, H/J-Series or L-Series) are you running and what communications line hardware/protocol is being used.

    Regards, Gary (CE Engineering)
    --- Synchronet 3.21d-Linux NewsLink 1.2
  • From Bry Pas@bryanpascua88@gmail.com to comp.sys.tandem on Wed Apr 26 05:40:44 2023
    From Newsgroup: comp.sys.tandem

    Hello Gary,

    We are running on J-Series and using G16SE (16-port enclosure).

    Regards,
    Bryan
    --- Synchronet 3.21d-Linux NewsLink 1.2
  • From Gary Hall@google@ce2i.co.uk to comp.sys.tandem on Thu May 4 14:36:41 2023
    From Newsgroup: comp.sys.tandem

    Hello Bryan,

    Use the SCF STATS PIF command to display transmit/receive errors on a G4SA port:

    TACL > SCF > STATS PIF $ZZLAN.G4SA_ADAPTER_NAME.SAC.PIF_NUMBER

    example: STATS PIF $ZZLAN.G10026.0.A

    Use the RESET option to zero down the statistics.

    Regards, Gary (CE Engineering)

    --- Synchronet 3.21d-Linux NewsLink 1.2
  • From Bry Pas@bryanpascua88@gmail.com to comp.sys.tandem on Fri May 5 06:36:11 2023
    From Newsgroup: comp.sys.tandem

    Hello Gary,

    Thanks so much for the Info!

    Regards,

    --- Synchronet 3.21d-Linux NewsLink 1.2