Understanding Half-Duplex Links on Satellite Devices in a Junos Fusion Enterprise
This topic describes half-duplex links on satellite devices in a Junos Fusion Enterprise.
This topic covers:
Half-Duplex Links on Satellite Devices Overview
Half-duplex communication is supported on all built-in network copper ports on EX2300, EX3400, and EX4300 satellite devices in a Junos Fusion Enterprise (JFE). Half-duplex is bidirectional communication, but signals can flow in only one direction at a time. Full-duplex communication means that both ends of the communication can send and receive signals at the same time.
The built-in network copper ports are configured by default as full-duplex 1-gigabit links with autonegotiation. If the link partner is set to autonegotiate the link, then the link is autonegotiated to full duplex or half-duplex. If the link is not set to autonegotiation, then the satellite-device link defaults to half-duplex unless the interface is explicitly configured for full duplex.
On EX2300, EX3400, and EX4300 satellite devices, the link mode is handled as follows:
If the link partner is operating in half-duplex, the satellite device interface goes to half-duplex.
If the link partner is not capable of autonegotiation, the satellite device interface goes to half duplex.
If the link partner is capable of autonegotiation and is operating in full duplex, the satellite device interface also works in full duplex.
Understanding Configuration of Full-Duplex Link Mode on a Satellite Device and Verification of Half-Duplex Mode
Like all features in a Junos Fusion Enterprise, link modes are configured and verified from the aggregation devices.
To explicitly configure full duplex:
[edit] user@aggregation-device# set interfaces interface-name link-mode full-duplex
To verify a half-duplex setting:
user@aggregation-device> show interfaces interface-name extensive