Optical Systems Design OSD2524, User Manual

Page: 368 / 402

OPTICAL SYSTEMS DESIGN
DOC ID: 10120001
OSD2524 OPERATOR MANUAL
PAGE 368
LLDP NEIGHBOURS EEE INFORMATION
Monitor
→
LLDP
→
EEE
By using EEE power savings can be achieved at the expense of traffic latency. This latency
occurs due to that the circuits EEE turn off to save power, need time to boot up before sending
traffic over the link. This time is called "wakeup time". To achieve minimal latency, devices
can use LLDP to exchange information about their respective tx and rx "wakeup time ", as a
way to agree upon the minimum wakeup time they need.
This page provides an overview of EEE information exchanged by LLDP.
LLDP NEIGHBORS EEE INFORMATION
The displayed table contains a row for each interface.
If the interface does not supports EEE, then it displays as "EEE not supported for this
interface".
If EEE is not enabled on particular interface, then it displays as "EEE not enabled for this
interface".
If the link partner doesn't supports EEE, then it displays as "Link partner is not EEE capable.
The columns hold the following information:
Local Interface
The interface at which LLDP frames are received or transmitted.
Tx Tw
The link partner's maximum time that transmit path can hold-off sending data after deassertion of LPI.
Rx Tw
The link partner's time that receiver would like the transmitter to hold-off to allow time for the receiver to
wake from sleep.
Fallback Receive Tw
The link partner's fallback receive Tw.
A receiving link partner may inform the transmitter of an alternate desired Tw_sys_tx. Since a receiving
link partner is likely to have discrete levels for savings, this provides the transmitter with additional
information that it may use for a more efficient allocation. Systems that do not implement this option
default the value to be the same as that of the Receive Tw_sys_tx.