219
1. 8 7 7. 8 7 7. 2 2 6 9 BLACKBOX.COM
NEED HELP?
LE AVE THE TECH TO US
LIVE 24/7
TECHNICAL
SUPPORT
1.8 7 7. 8 7 7. 2 26 9
CHAPTER 4: MONITOR
4.11.3 EEE
By using EEE, power savings can be achieved at the expense of traffic latency. This latency occurs because the circuits EEE turn off
to save power and 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.
WEB INTERFACE
To show LLDP EEE neighbors:
1. Click Monitor, LLDP, then click EEE to show discovered EEE devices.
2. Click Refresh to manually update the web screen.
3. Click Auto-refresh to automatically update the web screen.
FIGURE 4-51. LLDP NEIGHBORS EEE INFORMATION SCREEN
NOTE: If your network does not have any devices that enable the EEE function, then 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 the transmit path can hold off sending data after reassertion of LPI.
Rx Tw: The link partner’s time that the 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.
Echo Tx Tw: The link partner’s Echo Tx Tw value.
The respective echo values will be defined as the local link partner’s reflection (echo) of the remote link partner’s 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 partner‘s 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: This is NOT the link partner.
To Next Page
Loading...
