Versions Compared

Old Version 1

changes.mady.by.user Ribbon Communications

Saved on

compared with

New Version Current

changes.mady.by.user Ribbon Communications

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Add_workflow_for_techpubs
AUTH1UserResourceIdentifier{userKey=8a00a0c86ca23f8a016cd6ed6fe90013, userName='null'}
JIRAIDAUTHTP-548
REV5UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'}
REV6UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'}
REV3UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'}
REV1UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'}

  1. Choose Network > T1 Diagnostics.
  2. Choose the loopback test you want to run from the Loopback drop-down list and click Submit. Loopback tests are described in T1 Loopback Tests, Alarms, and Counters.

  3. Select the BERT test type from the BERT menu and click Submit.
    The BERT test sends a framed Quasi Random Bit Sequence (QRBS) on the T1 link and monitors the receive path for bit errors. A BERT test is usually run in conjunction with a network loopback at the remote end so that the test pattern sent by the 

    Spacevars
    0product2
    can be compared to the pattern received on the same interface. The
    Spacevars
    0product2
    can send a QRBS 2^15-1 and a QRBS 2^20-1 pattern.

    Note

    The 

    Spacevars
    0product2
    also responds to network-generated, AT&T formatted loop up/down codes. Loopback codes sent from far-end equipment loop the T1 interfaces back toward the network. T1 diagnostic counters are described in T1 Loopback Tests, Alarms, and Counters.


Pagebreak