Verifying Link and Transceivers using Pseudo Random Binary Sequence (PRBS) Test
Verifying Link and Transceivers using Pseudo Random Binary Sequence (PRBS) Test
The Pseudo Random Binary Sequence (PRBS) test is a standard feature to verify link quality and transceiver operation. There are two possible diagnostic scenarios:
Bidirectional verification using remote loopback. Test sequence is initiated from the local end. Remote end is configured with the loopback and analysis of the test pattern is performed at local end as well.
Unidirectional. Test sequence is initiated from the local end. Test pattern is analyzed by the remote end.
In the first case, verification is bidirectional and loopback support is required on the remote end.
The following table lists the entity that enables the PRBS test on various MICs:
MIC Type |
PRBS Test Engine |
Remarks |
---|---|---|
JNP10003-LC2103 |
Packet Forwarding Engine (PFE) |
- |
JNP-MIC1 |
Packet Forwarding Engine (PFE) |
- |
JNP-MIC1-MACSEC |
External physical layer (PHY) device |
External physical layer (PHY) device is not capable of passing the PRBS pattern originating from the packet forwarding engine. Hence, the PRBS test is enabled on external physical layer (PHY) device. |
The following table mentions the PRBS test details supported on various interfaces:
Interface Type |
Interface Name |
Interface Lane Characteristics |
Remarks |
---|---|---|---|
10-Gigabit ethernet interface |
“xe” |
The interface is supported with 1 lane of 10Gbps speed |
The PRBS test is executed on each lane supported. Hence,
the |
40-Gigabit ethernet interface |
“et” |
The interface is supported with 4 lanes of 10Gbps speed. |
The PRBS test is executed on each lane supported. Hence,
the |
100-Gigabit ethernet interface |
“et” |
The interface is supported with 4 lanes of 25Gbps speed. |
The PRBS test is executed on each lane supported. Hence,
the |
Guidelines to perform Unidirectional Diagnostics
Enable the transmission of pseudo-random binary sequence pattern on one end of the link (TX), and enable monitoring on the other end (RX).
The PRBS statistics report on the receiving end reflects link quality.
Following are the steps to collect and view the PRBS statistics:
See Also
Guidelines to perform Bidirectional Diagnostics using Remote Loopback
Configure loopback on the remote end of the link. Test pattern generation and analysis is performed on the local end.
The PRBS statistics report on the receiving end reflects link quality.
Following are the steps to collect and view the PRBS statistics:
Interface Card Specific differences
While collecting statistics, the JNP-MIC1-MACSEC and JNP-MIC1 MICs behave differently:
On JNP-MIC1-MACSEC MIC, if RX is not latching to any PRBS signal, then the "state" in the show interfaces interface-name prbs-stats displays as “Disabled" with Error count as 0, where the JNP-MIC1 MIC displays as failed with MAX error count.
For Example: On JNP-MIC1-MACSEC MIC
user@host> test interface et-0/1/10 prbs-test-start pattern-type 31 direction 1 flip 0 user@host> show interfaces et-0/1/10 prbs-stats PRBS Statistics : Enabled Lane 0 : State : Disabled, Error count : 0 Lane 1 : State : Disabled, Error count : 0 Lane 2 : State : Disabled, Error count : 0 Lane 3 : State : Disabled, Error count : 0
For Example: On JNP-MIC1 MIC
user@host> test interface et-0/0/1 prbs-test-start pattern-type 31 direction 1 flip 0 user@host> show interfaces et-0/0/1 prbs-stats PRBS Statistics : Enabled Lane 0 : State : Fail, Error count : 4294967295 Lane 1 : State : Fail, Error count : 4294967295 Lane 2 : State : Fail, Error count : 4294967295 Lane 3 : State : Fail, Error count : 4294967295
If any mismatch is encountered between the pattern-type and flip between TX and RX, the maximum error counts are observed in case of JNP-MIC1 MIC and state “disabled” in case of JNP-MIC1-MACSEC MIC (flip is only supported in JNP-MIC1-MACSEC).
In case of JNP-MIC1 MIC, if TX is interrupted, the RX displays the state as failed with error counts. Even if TX is started again, RX also must to be restarted to work properly. In case of JNP-MIC1-MACSEC MIC, if TX is interrupted, the RX displays the state as "Disabled" with Error Count 0 (point 1) and if TX is started, RX need not be started again.
If TX or RX is started consecutively without stopping the earlier run, then difference in the behavior of JNP-MIC1-MACSEC and JNP-MIC1 MICs are observed.
Decision feedback equalization (DFE) tuning is required on JNP-MIC1 MIC to start a PRBS test. But, on JNP-MIC1-MACSEC MIC, the DFE tuning is not required. If PRBS is started again at TX or RX without stopping the earlier run, there will be errors until DFE tuning is completed again, in JNP-MIC1 MIC. JNP-MIC1-MACSEC MIC does not show this behavior as there is no DFE tuning involved.
You must disable Forward Error Correction (FEC), if loopback is configured in the router with JNP-MIC1 MIC at the remote end.
user@host> show interfaces et-1/1/1 | display set set interfaces et-1/1/1 gigether-options loopback-remote set interfaces et-1/1/1 gigether-options fec none
Clearing the Interface Statistics
The clear interface statistics
command clears only
the error counters and not the status, RX needs to be restarted to
get the right status.
Following are the steps to clear the interface statistics: