Pseudo Random Binary Sequence
The Pseudo Random Binary Sequence (PRBS) feature enables data integrity checks between NCS 1014 trunk and client links without generating client traffic.
The PRBS feature must be enabled on both the transmitting and receiving ports to ensure error-free traffic during link bring-up. The transmitting port creates and sends a bit pattern to the peer device. The NCS 1014 device verifies that the correct pattern is received. Additionally, PRBS is supported on the ODU4 controller by the 1.2T card.
You can configure PRBS on a coherentDSP or Ethernet controller of a 1.2T, 2.4T, or 2.4TX cards. PRBS can also be configured on a ODU controller of the 1.2T card. Before enabling PRBS, the secondary admin state of the controllers must be set to maintenance.
PRBS modes
PRBS operates in several modes, each offering unique functionality:
-
Source mode: The NCS 1014 trunk port generates a PRBS signal on the line continuously according to the configured PRBS pattern
-
Sink mode: The NCS 1014 trunk port locks onto the ingress signal according to the configured pattern, analyzes, and reports the errors.
-
Source-Sink mode: The NCS 1014 trunk port acts as both the PRBS transmitter and receiver, meaning it generates a PRBS signal according to the configured pattern, locks onto the ingress signal with the same pattern, and reports the errors.
Configure PRBS on CoherentDSP controller
Use this task to configure PRBS on the trunk port of the coherentDSP controller of a card.
Procedure
|
Step 1 |
Run the controller coherentDSP R/S/I/P command to enter the coherentDSP controller configuration mode. Example:
|
|
Step 2 |
Run the secondary-admin-state { normal | maintenance} command to set the secondary admin state. Example:
|
|
Step 3 |
Run the prbs mode {source | sink | source-sink} pattern {pn31 | pn23 | pn15 | pn7} command to configure the PRBS mode and pattern. Example:
|
|
Step 4 |
Commit the changes. Example:
|
Configure PRBS on ODU controller
You can configure PRBS in these combinations for an ODU controller on a 1.2T card.
The client ports need to have a physical loopback in all the combinations:
-
Near end client and near end trunk ODU4
-
Near end client and far end client ODU4
-
Near end client and far end trunk ODU4
-
Near end trunk and far end trunk ODU4
Procedure
|
Step 1 |
Run the controller odu4 R/S/I/P command to enter the odu4 controller configuration mode. Example:
|
|
Step 2 |
Run the secondary-admin-state { normal | maintenance} command to set the secondary admin state. Example:
|
|
Step 3 |
Run the opu prbs mode {source | sink | source-sink} pattern {pn31 | pn23 | pn15 | pn7} command to configure the PRBS mode and pattern. Example:
|
|
Step 4 |
Commit the changes. Example:
|
Configure PRBS on Ethernet controller
Use this task to configure PRBS on the client ports of an Ethernet controller of the 2.4T and 2.4TX cards.
Procedure
|
Step 1 |
Run the controller {fourHundredGigECtrlr} R/S/I/P command to enter the ethernet controller configuration mode. Example:
|
|
Step 2 |
Run the secondary-admin-state { normal | maintenance} command to set the secondary admin state. Example:
|
|
Step 3 |
Run the opu prbs mode {source | sink | source-sink} pattern {pn31 | pn23 } command to configure the PRBS mode and pattern. Example:
|
|
Step 4 |
Commit the changes. Example:
|


Feedback