From: Kenneth Wygand (KWygand@customonline.com)
Date: Thu Sep 25 2003 - 13:42:05 GMT-3
FYI - CRC and FCS errors can also be caused by EMI interference or cable
lengths that exceed specifications.
Kenneth E. Wygand
Systems Engineer, Project Services
CISSP #37102, CCNP, CCDP, MCP 2000, CNA 5.1, Network+, A+
Custom Computer Specialists, Inc.
"It's not just about ending up where you want to be, it's about making
the most of the trip there."
-Anonymous
-----Original Message-----
From: Barney Gaumer [mailto:bagaumer@yahoo.com]
Sent: Thursday, September 25, 2003 12:21 PM
To: Barney Gaumer; Ralph Simmons; ccielab@groupstudy.com
Subject: Re: gig ethernet/ collision debate
I should also mention, if the host is acting up like I
mentioned in my previous post then you will also most
likely see runts and fcs errors too.
BG
--- Barney Gaumer <bagaumer@yahoo.com> wrote:
> If the Gig card in the host that is attached to the
> switchport is malfunctioning or has the ability to
> go
> half duplex (and is) then you would see your
> collision
> counter incrementing up.
>
> But if both sides are FDX and no problems then
> collisions should not occure.
>
> Cheers,
> Barney
> --- Ralph Simmons <ciscoag2000@yahoo.com> wrote:
> > so is there any way that you would get collisions
> > then on a gig link other then faulty equipment
> then?
> > My buddy says he has seen it before and I saw
> it
> > is not possible. What could of caused a
> interface
> > to show collisions or did he just not know what he
> > was looking at?
> >
> > Barney Gaumer <bagaumer@yahoo.com> wrote:Since
> > Duplex is not a settable option (at least on
> > 6509 platform) you should not see collisions on
> > either
> > fiber or copper since it is Full Duplex by
> default.
> >
> > Again, 6509 is the only platform I have looked at
> > this
> > on, if other platforms can change Speed/Duplex on
> > Gig
> > someone else will half to speak to that. I think
> Gig
> > is inherently FDX though.
> >
> > 6509-a (enable) sh port 3/7
> > Port Name Status Vlan
> > Duplex Speed Type
> > ----- -------------------- ---------- ----------
> > ------ ----- ------------
> > 3/7 notconnect 1
> > full 1000 1000BaseSX
> >
> >
> > 6509-a (enable) set port speed 3/7 1000
> > Feature not supported on Module 3.
> > 6509-a (enable) set port dup 3/7 full
> > Feature not supported on Port 3/7.
> > 6509-a (enable)
> >
> >
> > 6509-a (enable) sh port 9/1
> > Port Name Status Vlan
> > Duplex Speed Type
> > ----- -------------------- ---------- ----------
> > ------ ----- ------------
> > 9/1 notconnect 1
> > full 1000 1000BaseT
> >
> >
> > 6509-a (enable) set port speed 9/1 1000
> > Feature not supported on Module 9.
> > 6509-a (enable) set port dup 9/1 full
> > Feature not supported on Port 9/1.
> > 6509-a (enable)
> > --- Ralph Simmons wrote:
> > > Hoping one of you guys can settle a debate i am
> > with
> > > a coworker and win me a free lunch from him.
> > >
> > > We were debating about wheter of not you can get
> > > collisions on gig ethernet. Is the collision
> > > detection removed from gig ethernet? If not
> under
> > > what circumstances could you get collisions? Any
> > > documentation of cisco.com would be great to
> prove
> > > it.
> > >
> > > Thanks,
> > >
> > >
> > > ---------------------------------
> > > Do you Yahoo!?
> > > The New Yahoo! Shopping - with improved product
> > > search
> > >
> > > ***Get your CCIE and a FREE vacation:
> > > Shop.GroupStudy.com***
> > >
> >
>
This archive was generated by hypermail 2.1.4 : Wed Oct 01 2003 - 07:24:37 GMT-3