Black Box LGB1148A Manual Do Utilizador
724-746-5500 | blackbox.com
Page 102
724-746-5500 | blackbox.com
Chapter 3: Configuration
3.8.5 EEE
By using EEE, power savings can be achieved at the expense of traffic latency. This latency occurs because EEE circuits turn off to
save power, and they 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 section provides an overview of EEE and LLDP interactions.
save power, and they 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 section provides an overview of EEE and LLDP interactions.
Web Interface
To show LLDP EEE neighbors:
1. Click LLDP, then click EEE to show discover EEE devices.
2. Click Refresh for manual update Web screen.
3. Click Auto-refresh for auto-update Web screen.
Figure 3-47 The LLDP Neighbors EEE Information screen.
NOTE: If your network has no devices that enable the EEE function, the table will show “No LLDP EEE information found.”
Parameter Description
• Local Port: The port on which LLDP frames are received or transmitted.
• Tx Tw: The link partner’s maximum time that transmit path can hold off sending data after reassertion 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 allo-
cation. Systems that do not implement this option default the value to be the same as that of the Receive Tw_sys_tx.
cation. Systems that do not implement this option default the value to be the same as that of the Receive Tw_sys_tx.
• Echo Tx Tw: The link partner's Echo Tx Tw value.
The respective echo values shall be defined as the local link partners reflection (echo) of the remote link partners respective
values. When a local link partner receives its echoed values from the remote link partner, it can determine whether or not the
remote link partner has received, registered, and processed its most recent values. For example, if the local link partner receives
echoed parameters that do not match the values in its local MIB, then the local link partner infers that the remote link partners
request was based on stale information.
remote link partner has received, registered, and processed its most recent values. For example, if the local link partner receives
echoed parameters that do not match the values in its local MIB, then the local link partner infers that the remote link partners
request was based on stale information.
• Echo Rx Tw: The link partner's Echo Rx Tw value.
• Resolved Tx Tw: The resolved Tx Tw for this link. Note: NOT the link partner The resolved value that is the actual “tx wakeup
time“ used for this link (based on EEE information exchanged via LLDP).
• Resolved Rx Tw: The resolved Rx Tw for this link. Note: NOT the link partner The resolved value that is the actual “tx wakeup
time“ used for this link (based on EEE information exchanged via LLDP).
• Auto-refresh: Check the auto-refresh box to set the unit to refresh information automatically.
• Icon (refresh), upper right of screen: Click to refresh the LLDP Neighbors information manually.
LGB1108A