Tag: Networking, Networking / Home

Networking

NAVIGATION
CATEGORIES
REFERRENCE
LINKS
Home » Networking

  • Negotiation problem with Catalyst 2950 and Cisco 2821

    2 answers - 1084 bytes - related search similar search Add To My Delicious Add To My Stumble Upon Add To My Google Mark Add To My Facebook Add To My Digg Add To My Reddit

    You have already identified it as a duplex mismatch. Have you tried to
    hardcode the duplex and speed on both sides?
    12/3/05, Ted Mittelstaedt <tedm (AT) toybox (DOT) placo.comwrote:
    --
    Hi All,
    I hae a stock 2821 router with 2 gig E ports on the inside,
    and 2 load-balanced t1's going to the Internet, running NAT.
    IS version is 12.4.5
    I have several 2950's don't know what version of firmware
    (probably old).
    I plug the 2821 into the 2950s and set the 2821 and 2950 to
    autonegotiate speed and duplex.
    The 2821 negotiates to 10 base T half duplex. Users
    report problems with intermittent disconnects and slowness
    when surfing the web, etc.
    I go to Goodwill, no less, and purchase a 10 year old 8
    port dumb hub, 10BaseT only. Not a switch. Cost is $7.99
    I insert this hub between the 2821 and the Catalyst 2950.
    Problems of disconnects and slowness go away.
    Speculation, anyone?
    Ted
    cisco-nsp mailing list cisco-nsp (AT) puck (DOT) nether.net
    archive at

  • No.1 | | 1326 bytes | |

    3/12/2005 6:28 p.m., Wojtek Zlobicki wrote:
    You have already identified it as a duplex mismatch. Have you tried to
    hardcode the duplex and speed on both sides?

    12/3/05, Ted Mittelstaedt <tedm (AT) toybox (DOT) placo.comwrote:
    >>
    >Hi All,
    >>
    >I hae a stock 2821 router with 2 gig E ports on the inside,
    >and 2 load-balanced t1's going to the Internet, running NAT.
    >IS version is 12.4.5

    Thing is, it's all cisco gear, and current generation at that, so he shouldn't
    *need* to force it. I mean, it's 2005 and autonegotiation has been around for
    years and years so it should be foolproof. Although there are problems with
    some kit (not specific to cisco) when one end is hard coded and the other isn't,
    that's more a function of the way autonegotiation works and isn't relevant in
    this case.

    I have seen the problem Ted is referring to with 2800x and 2950 switches, and
    the only way we could get around it was to upgrade IS on the switch to
    something more recent.

    This bug might also be worth watching:

    reuben

    cisco-nsp mailing list cisco-nsp (AT) puck (DOT) nether.net

    archive at

  • No.2 | | 981 bytes | |

    Multiply this failure to document by the number of 2950 and
    2821's that Cisco has sold and that are undoubtedly coupled together
    and you can see that failing to document this in the 2821 docs wastes
    enormous man-years of time for people.

    As someone else suggested, I also think that the problem lies with the
    2950. I have 2800 series routers connected to 2950s with newer IS
    releases and don't have a problem with autonegotiation.

    a side note, yesterday I was sitting in on a WebEx training session
    for some expensive agent-less troubleshooting software and at one
    point the sales engineer doing the session suggested that you should
    always hard-set your ethernet settings. I didn't say anything because
    I was a simply a guest sitting in on the session. I really wanted to
    reach through my computer and slap him.

    John

    cisco-nsp mailing list cisco-nsp (AT) puck (DOT) nether.net

    archive at

Re: Negotiation problem with Catalyst 2950 and Cisco 2821


max 4000 letters.
Your nickname that display:
In order to stop the spam: 7 + 7 =
QUESTION ON "Networking"

EMSDN.COM