RE: [10GBASE-T] Technical feasibility: AutoNegotiation
Interesting that you'd ask this, because it was a question I had a
meeting or two ago. In most cases, the PHYs can determine the link
length via a simple electronic ping. As for the grade of the cable,
extrapolation could be performed during the training sequence as the
number of taps would have a correlation to the quality of the cable and
the data rate or distance supported. A lot of these methods are in use
today for 1000BASE-T, but they are implementation strategies, not based
on what is in 802.3.
From: DOVE,DANIEL J (HP-Roseville,ex1) [mailto:firstname.lastname@example.org]
Sent: Monday, August 04, 2003 3:49 PM
Subject: RE: [10GBASE-T] Technical feasibility: AutoNegotiation
Perhaps someone can give me a quick pointer on how we are going to
the issue of <100m cable plants that meet ISO 11801 specs not being able
For example, I have a building full of CAT5e and CAT6 cables. The cables
were installed to specification. Now, all I see are patch panels and
jacks. I don't have a record of which cable is how long, or what its
electrical specs are.
The current Auto-Negotiation protocol supports HCD resolution which
that the link, if configured to 10GBASE-T, will resolve to that speed if
both ends of the link support it. However, if the cable (85m of CAT6)
not, the link will bounce up and down as it negotiates to speed, then
to link. Maybe even worse is the link that actually comes up, but
unreliably due to thermal variation causing changes in parametric values
suffers excessive BER or drops link occasionally.
What is the fix?
Do I test the wire in advance of using 10GBASE-T?
Do we fix the Auto-Negotiation protocol to automatically drop speed if
SNR gets too low to guarantee the BER?
If these have already been addressed, please feel free to just send the
to the presentation.
HP ProCurve Networking