Group,
An update on that late-collision issue I brought to the list a while back.
Finally got to talk to a tech with my ISP today and we worked through the
circuit.
It seems the half-duplex / full-duplex answer wins the prize.
At first they tried to get me to verify my router's settings and as I have
done many times before, a sh int e0/1 indicated that the interface was not
full-duplex.
But he wanted me to give a command to change it to half-duplex "just to see
what happens".
But I suggested he do it on his end first - "just to see what happens".
In the meanwhile we were monitoring the router interface with sh int and
observing console errors.
The console was constantly spewing out transmit errors - late collision.
The sniffer was seeing significant alignment errors.
Anyway, he "does something" and immediately the console stops scrolling
errors.
amazing..........
So, we're going to stress this circuit a bit before letting them close the
ticket.
It seems they paid more attention when we said we had a sniffer on the line.
thanks for all the responses!
Kevin Wigle
_________________________________
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
