3.7.3. Event Subscription

• PL1_EVENT_LOGGING_CONFIG
• PL1_EVENT_LOGGING_SUBLIST
• PL1_EVENT_LOGGING_RSFEC_THRESH

Understanding Event Subscription

In the context of Layer-1 Event Logging, an Event is defined as a state transition of a certain physical layer condition. For example, a link up to down is considered a different event from a link down changing to up, although both involve the link state. Each event is associated with a timestamp indicating when it occurred.

Important

If there is no state change, no event will be generated. For example, if the link is already down and remains down, no event will be generated until the link state changes again. Thus, only changes result in events being generated, and the Layer-1 Event Logging will only log these state transitions.

Layer-1 Event Logging allows you to subscribe/unsubscribe to multiple events (duplicate subscriptions are allowed), enabling you to monitor various aspects of the physical layer simultaneously.

To subscribe/unsubscribe to an event, you will need to specify the event as follows:

[Event SerDes Index] <Event Type> <Event Condition>

• Event Type: The type of event you want to subscribe to (e.g. link sync state, local fault state). See Layer-1 Event Types & Conditions for a list of supported event types.

• Event Condition: The specific condition or state change that triggers the event. See Layer-1 Event Types & Conditions for a list of supported event conditions.

• Event SerDes Index: The specific SerDes index, if the event is associated with a particular SerDes lane, for which you want to log events. (e.g., for PRBS lock events, you will need to specify the SerDes lane index that you want to monitor). If the event is not SerDes-specific, use 0.