Hi
I'ver always found that you have a 50/50 chance of autonegotiation to work.
However it appears that most vendors are getting it right but you have the
outliers that can't auto negotiate no matter what you do. So unfortunately, you
need to just bite the bullet and hook the port and sometimes the device.
We actually have some systems that can only work at 100HDX but the machine next
to them is going 100FDX.
I would also upgrade to the 5.2 code that may help you to resolve this problem.
Each new release appears to get the auto negotiate a little bit better and more
outliers are starting to work.
Of course, maybe something could be messed up on the card (in the 55xx)? Looks
like everything is sensing 10MB, not 10 or 100...
Does it your station do this in the supervisor 100MB port?
Have you tried a new vlan for a 100mb link? Maybe the negotiate doesn't function
on the vlan as you have mixed media... doubtful but you never know... ;-)
Dmitri Kalintsev wrote:
> Morning good people,
>
> I have a rather strange problem. Here is a brand-new 5505 in the following
> configuration:
>
> System Bootstrap Version: 5.1(1)
> Hardware Version: 1.0 Model: WS-C5505 Serial #: xxx
> Mod Port Model Serial # Versions
> --- ---- ---------- --------- --------------------------------
> 1 0 WS-X5540 xxxxxxxxx Hw : 1.1
> Fw : 5.1(1)
> Fw1: 5.1(1)
> Sw : 5.1(2a)
> 2 24 WS-X5225R xxxxxxxxx Hw : 3.3
> Fw : 4.3(1)
> Sw : 5.1(2a)
> 4 48 WS-X5014 xxxxxxxxx Hw : 1.0
> Fw : 4.2(1)
> Sw : 5.1(2a)
>
> 32M RAM/8M FLASH.
>
> -- config --
> set port enable 2/1-24
> set port level 2/1-24 normal
> set port speed 2/1-24 auto
> set port trap 2/1-24 disable
> set port name 2/1-24
> set port security 2/1-24 disable
> set port broadcast 2/1-24 100%
> set port membership 2/1-24 static
> set port protocol 2/1-24 ip on
> set port protocol 2/1-24 ipx auto
> set port protocol 2/1-24 group auto
> set port negotiation 2/1-24 enable
> set port flowcontrol 2/1-24 send off
> set port flowcontrol 2/1-24 receive on
> set cdp disable 2/1-24
> -- /config --
>
> The problem I have is with 100Mbps negotiation. No, it's not my NIC's, as
> I've tried to connect a Sun Ultra 10 (I hope you won't argue that their
> NIC's *are* good enough), and still cannot get a 100M link up. Sympthoms are
> as follows: (assume that cables *are* fine, as well)
>
> 1. Plugging in a Linux workstation, running DEC 21xxx chipset, it autosenses
> 10/HDX.
>
> 2. Plugging in an uplink crossover to 3com hub - it autosenses 10/HDX.
>
> 3. Plugging in an Intel server (OS == Linux) on-board EtherExpress Pro 100 -
> no link, is I set up "set port speed x/y 10" - link establishes, if I say
> "set port speed x/y 100" - link light just flashes quickly in, flashes out
> for about a second, flashes in quickly again and so on. If I do "sh port
> x/y" it shows "not conn", "conn", "not conn", etc - in other words, it's
> losing a link state all of the time. Setting up duplex manually does not
> help at all.
>
> 4. Plugging in an aforesaid Sun workstation gives exactly the same results
> as in (3). So does i386 workstation running Solaris (NIC == EEPRO 100).
>
> I don't have another Cisco piece of hardware with a 100 mbps capable port
> here to test it out with (unfortunely). ;(
>
> Any ideas?
>
> P.S. Crazy idea, but... all ports (24x100M and 48x10BaseT) are in the same
> VLAN... Should *not* matter, but anyway?
>
> SY,
> --
> (KD1350) CCNA Dmitri E. Kalintsev
> CDPlayer@irc Senior network engineer at NetActive Internet
> dek @ hades.uz phone: +27 (0)11 719-0333 fax: 444-8900
> http://hades.uz UIN:7150410 cell +27 (0)82-336-1033
--
<><><><><><><><><><><><><><><><><><><><><><><><><><><>
"Failure is not an option"
Gene Cranz, Apollo 13 mission
<><><><><><><><><><><><><><><><><><><><><><><><><><><>
Everett Dowd edowd@clark.net
CCIE #2409 http://www.clark.net/pub/edowd
Just bein' virtual =8^) Welcome to the 'net
|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|
This archive was generated by hypermail 2b29 : Sun Aug 04 2002 - 04:12:06 EDT