PM Overhead

In this user interface, you can set path monitoring (PM) overhead bytes and relevant parameters.

Navigation Path

In the NE Explorer, select a board and choose Configuration > OTN Overhead Management > PM Overhead from the Function Tree.

Buttons

Button	Description
Display in Text Format	Enables the text format display of overhead bytes.
Display in Hexadecimal	Enables the hexadecimal display of overhead bytes.

Shortcut Menu

Select an object from the object list, right-click the field of its TTI to Be Sent or TTI to Be Received parameter, and choose Copy All From Received or Manual Input from the shortcut menu.

Shortcut Menu	Description
Copy All From Received	Copies the overhead bytes to be received to improve work efficiency.
Manual Input	Displays the Overhead Byte dialog box to enter overhead bytes in it. NOTE: When setting overhead bytes in text mode, use only ASCII characters.

Parameters

Field	Value	Description
Object	Equipment that supports the master and slave shelf management: NE name-shelf ID(shelf name)-slot number-board name-port number(port name)(-monitoring level) Equipment that does not support the master and slave shelf management: NE name-slot number-board name-port number(port name)(-monitoring level) NOTE: For details about the differences between the standard and compatibility modes, see the Impacts of the Standard Mode on the U2000 Web LCT in Channel Model (OTU, Line or PID Board).	Displays the object that the PM overhead monitors.
TIM Mode	Only SAPI, Only DAPI, SAPI&DAPI, No Detection Default: No Detection	Sets the mode of detecting trail trace identifier mismatch. Only SAPI: Only the source tag of the TTI is detected. When the source tag of the TTI to be Received is inconsistent with that of the TTI Received, an alarm is reported. Only DAPI: Only the sink tag of the TTI is detected. When the sink tag of the TTI to be Received is inconsistent with that of the TTI Received, an alarm is reported. SAPI&DAPI: Both the source tag and sink tag of the TTI are detected at the same time. When the source tag or sink tag of the TTI to be Received is inconsistent with that of the TTI Received, an alarm is reported.
TTI to Be Sent	For example: a-b-e	The TTI to Be Sent parameter is used to set the trail trace identifier (TTI) that should be sent of the OTN path monitoring overhead layer. NOTE: Right-click the field of the TTI to be Sent or TTI to be Received parameter and choose Copy All From Received from the shortcut menu to copy the overhead bytes to be sent or received. This will improve the work efficiency.
TTI to Be Received	For example: a-b-e	The TTI to Be Received parameter is used to define the TTI to be received at the receive end. The trail trace identifier (TTI) is a string of 64 characters, including 15 characters used as the source access point identifier, 15 characters used as the sink access point identifier, two characters of 0s, and 32 characters that are defined by carriers.
TTI Received	For example: a-b-e	Displays the TTI received by the port. According to the TIM Mode attributes, the system checks the consistency between the TTI to be Received and the TTI Received to determine whether to report an alarm. NOTE: The value of TTI Received must be the same as the value of TTI to be Received. Otherwise, an ODUk_PM_TIM alarm is reported.
LCK Insertion	Enabled, Disabled Default: Disabled	Sets whether to turn on the LCK insertion function. When the function is Enabled, an LCK signal is inserted to the downstream for locking the signal of the user access point. This function is often used by carriers for a test.
Threshold-Crossing Threshold	1.0E-3, 1.0E-4, 1.0E-5 Default: 1.0E-3	Sets the threshold-crossing threshold for BIP8 bit errors. A threshold crossing occurs if the signal bit error rate reaches this value.
Degrade Threshold	1.0E-5, 1.0E-6, 1.0E-7, 1.0E-8, 1.0E-9 Default: 1.0E-6	Sets the degrade threshold for BIP8 bit errors. A signal degrade occurs if the signal bit error rate reaches this value. The Degrade Threshold should be smaller than the Threshold-Crossing Threshold.