[j-nsp] EX4300 and full-duplex-only

[Jackson, William]

The ex3300 does not have this limitation.


William Jackson

Gibtelecom 
Email: william.jackson at gibtele.com 

-----Original Message-----
From: juniper-nsp [mailto:juniper-nsp-bounces at puck.nether.net] On Behalf Of Frank Sweetser
Sent: 23 September 2015 18:05
To: juniper-nsp at puck.nether.net
Subject: Re: [j-nsp] EX4300 and full-duplex-only

On 09/23/2015 09:47 AM, Phil Mayers wrote:
> If you mean "why it's only duplex limitations", I'm guessing the 
> device is missing the collision-detect/retransmit hardware for cost 
> reasons. 10/half is pretty rare these days and, in theory, they're 
> pitched as a datacentre device (though we have an IBM tape library which is 10/half on it's management port).

When I first saw the details about the EX4300, my initial reaction was that it was built as a low cost 1Gb dongle for QFabric.

> You can force the link up by disabling autoneg, but that comes up 
> duplex-mismatched - 10/full at the EX end, 10/half at the device end.
>
> All very disappointing; we did not think to specify "must comply with 
> IEEE 802.3" in the RFP :o/


Even putting it in wouldn't have helped unless you verified it yourself anyway
- they list 802.3 support on page 19 of the data sheet:

http://www.juniper.net/assets/us/en/local/pdf/datasheets/1000467-en.pdf

That said, does anyone know if the EX3300 switches suffer from this same design decision?

-- 
Frank Sweetser fs at wpi.edu    |  For every problem, there is a solution that
Manager of Network Operations   |  is simple, elegant, and wrong.
Worcester Polytechnic Institute |           - HL Mencken
_______________________________________________
juniper-nsp mailing list juniper-nsp at puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp