router log errors

Discussion in 'Cisco' started by Tester, Jan 20, 2004.

  1. Tester

    Tester Guest

    Hi there,
    Can someone tell me what these errors in the Cisco 1605 router mean? Should
    I do anything? Router is connected to a T1 line.

    Jan 19 19:36:38: %QUICC_ETHER-5-LATECOLL: Unit 0, late collision error

    Jan 19 20:52:57: %SYS-2-MALLOCFAIL: Memory allocation of 126 bytes failed
    from 0
    x20C0AAA, pool Processor, alignment 0
    -Process= "IP Input", ipl= 0, pid= 9
    -Traceback= 20BF7A2 20C087A 20C0AB2 21D2E4E 20D1226 2007D78 20A2BE2 217C484
    2173
    3A6 2173AA2 2172E3A 2172F78 217309C
    Thanks, Calin
     
    Tester, Jan 20, 2004
    #1
    1. Advertisements

  2. :Can someone tell me what these errors in the Cisco 1605 router mean? Should
    :I do anything? Router is connected to a T1 line.

    :Jan 19 19:36:38: %QUICC_ETHER-5-LATECOLL: Unit 0, late collision error

    Not good. You have a bad transceiver or your topology exceeds specs
    (e.g., too many hops.)


    :Jan 19 20:52:57: %SYS-2-MALLOCFAIL: Memory allocation of 126 bytes failed

    Have you done the Nachi Worm Mitigation? If not, then you might find
    that you need to.
     
    Walter Roberson, Jan 21, 2004
    #2
    1. Advertisements

  3. Tester

    Hansang Bae Guest

    :Jan 19 19:36:38: %QUICC_ETHER-5-LATECOLL: Unit 0, late collision error


    Or more likely these days...a duplex mismatch.

    --

    hsb

    "Somehow I imagined this experience would be more rewarding" Calvin
    *************** USE ROT13 TO SEE MY EMAIL ADDRESS ****************
    ********************************************************************
    Due to the volume of email that I receive, I may not not be able to
    reply to emails sent to my account. Please post a followup instead.
    ********************************************************************
     
    Hansang Bae, Jan 21, 2004
    #3
  4. Tester

    Hansang Bae Guest

    Sure,..the HD side listens during IFG, transmits, makes it past the min
    size frame...only to be trumped by the FD side who has no such
    contstraints.


    --

    hsb

    "Somehow I imagined this experience would be more rewarding" Calvin
    *************** USE ROT13 TO SEE MY EMAIL ADDRESS ****************
    ********************************************************************
    Due to the volume of email that I receive, I may not not be able to
    reply to emails sent to my account. Please post a followup instead.
    ********************************************************************
     
    Hansang Bae, Jan 22, 2004
    #4
  5. Tester

    Ivan Ostres Guest

    That would be possible just with really small frames...
     
    Ivan Ostres, Jan 22, 2004
    #5
  6. Tester

    mikester Guest

    We see late collisions all the time with duplex mismatches. (Sun
    hardware connecting to FE ports on 6509s)
     
    mikester, Jan 22, 2004
    #6
  7. Tester

    Ivan Ostres Guest

    Frames with length 64 are perfectly normal...
     
    Ivan Ostres, Jan 22, 2004
    #7
  8. Tester

    Ivan Ostres Guest

    Frames with length 64 are perfectly normal...
     
    Ivan Ostres, Jan 22, 2004
    #8
  9. Why? The FD device transmits whenever it wants. If the HD node
    happens to be mid-transmission and past the collision window, a late
    collision results. Note that the FD device can and will transmit
    whether it has already begun receiving the HD node's transmission or
    not -- it's running FD, so it can transmit at any time.

    -Terry
     
    Terry Baranski, Jan 23, 2004
    #9
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.