Comware

 View Only
  • 1.  Errors on interface connected to WAN

    Posted Feb 27, 2009 09:46 AM
    Afternoon All,

    Why am i getting alot of the following errors on the uplink interface to the WAN Router.

    Drops Rx 222,234
    Collisions TX 800,000
    Late Colln 169,766
    Deferred Tx 1,3921,499

    Interface 1 on Switch set to Full Duplex @ 100

    Interface 1 on Router set to Full Duplex @ 100

    No VLAN is tagged on uplink / uplink is assigned to Data VLAN and untagged.


    Quick over on Switch.
    3x VLANs
    Vid1 (Default)
    Vid2 (Data)
    Vid3 (VoIP)

    using default route 0.0.0.0 0.0.0.0 192.168.0.254


    Any Ideas?
    Thx!




  • 2.  RE: Errors on interface connected to WAN

    Posted Feb 27, 2009 09:48 AM
    Ignore Vid 2 Please!!!
    Data is all on Default.
    Thx.


  • 3.  RE: Errors on interface connected to WAN

    Posted Feb 27, 2009 10:11 AM
    You shouldn't be seeing collisions increase in Full Duplex mode, by definition.

    So the obvious question is "are you *sure* that the switch interface 1 is operating in Full Duplex mode?" Sorry for having to ask it.


  • 4.  RE: Errors on interface connected to WAN

    Posted Feb 27, 2009 10:49 AM
    Thanks for you reply Richard,

    I can confirm the interface is set to Manual @ 100 Full Duplex.

    Looking to replace Uplink cable asap.
    Any other recommedations or tips?
    Thanks,
    Karl


  • 5.  RE: Errors on interface connected to WAN

    Posted Feb 27, 2009 01:31 PM
    many collisions and packet drop issue be happen aoutonegotiation division between two device


    aoutonegotiation being between two device each device check speed dublex and mdi mode,freame size etc.

    so if make set on two port for example 100-full very good

    my advice
    now you must be set mdi mode on swithc port
    if you have patch ceble strain through cable (standart 568 A or B cable)
    take switch port mdix mode not to leave auto

    for example
    switch(eth-14)# mdix-mode mdix [enter]




  • 6.  RE: Errors on interface connected to WAN

    Posted Mar 03, 2009 05:02 AM
    It feels like an autonegotiation problem, even if it shouldn't be one. If it's in FD mode, collision detection should be disabled.

    Not sure what to suggest, except bringing the link up and down, seeing if that changes everything. I'd be tempted to try autonegotation or even forcing HD at both ends (keeping track of the counter differences).

    I assume the WAN link is likely less that 100Mbit/s, if so running the link to it HD is going to make no practical difference, as long as it's reasonably error free.


  • 7.  RE: Errors on interface connected to WAN

    Posted Mar 03, 2009 02:35 PM
    Evening Chaps,

    Thanks for all the replys!!!

    Replaced the MDIx cable and forced the interface to MDIx not auto and the counters are staying at 0

    PS the WAN link speed is 100Mb.

    Cheers,
    Karl.