Wired Intelligent Edge

 View Only
last person joined: yesterday 

Bring performance and reliability to your network with the Aruba Core, Aggregation, and Access layer switches. Discuss the latest features and functionality of the ArubaOS-Switch and ArubaOS-CX devices, and find ways to improve security across your network to bring together a mobile first solution.
Expand all | Collapse all

High collision or drop rate messages on 2930f Switch

This thread has been viewed 8 times
  • 1.  High collision or drop rate messages on 2930f Switch

    Posted 3 days ago
    Can anyone help?

    Hello,

    I have a 2930f Switch which is showing warning messages - "High collision or drop rates" on the same 2 - 3 Ports - see below.  These are Trunk Ports connected to some Customer Servers.

    All the Ports on the Switch are configured with the same Speed-duplex settings, but only these ports are showing collisions and drops.

    The ports on the connected Server are 1Gbit, so I don't think there is a Speed-duplex configuration mismatch.

    Could this problem be caused by something else, perhaps a  Loop somewhere in the system? is that possible?

    If I could establish a possible cause, then I could try something out during the quiet period.

    Any help or advice would be brilliant.

    Many thanks! - Paul B


    Show Logging and int brief:

    W 11/23/22 01:34:02 00331 FFI: ST1-CMDR: port 2/19-High collision or drop rate.
    See help.
    W 11/23/22 01:39:40 00331 FFI: ST1-CMDR: port 1/19-High collision or drop rate.
    See help.
    W 11/23/22 02:06:57 00331 FFI: ST1-CMDR: port 2/19-High collision or drop rate.
    See help.
    W 11/23/22 03:07:17 00331 FFI: ST1-CMDR: port 2/19-High collision or drop rate.
    See help.
    W 11/23/22 03:07:34 00331 FFI: ST1-CMDR: port 1/19-High collision or drop rate.
    See help.
    W 11/23/22 04:51:30 00331 FFI: ST1-CMDR: port 2/18-High collision or drop rate.
    See help.
    W 11/23/22 05:30:26 00331 FFI: ST1-CMDR: port 1/17-High collision or drop rate.

    ===============================================================

    1/13            100/1000T | No Yes Down 1000FDx Auto off 0
    1/14            100/1000T | No Yes Down 1000FDx Auto off 0
    1/15            100/1000T | No Yes Down 1000FDx Auto off 0
    1/16            100/1000T | No Yes Down 1000FDx Auto off 0
    1/17-Trk17 100/1000T | No Yes Up      1000FDx MDI off 0
    1/18-Trk18 100/1000T | No Yes Up      1000FDx MDI off 0
    1/19-Trk19 100/1000T | No Yes Up      1000FDx MDIX off 0
    1/20            100/1000T | No Yes Down 1000FDx Auto off 0
    1/21            100/1000T | No Yes Down 1000FDx Auto off 0
    1/25            100/1000T | No Yes Up      1000FDx MDI off 0
    1/26            100/1000T | No Yes Up      1000FDx MDI off 0
    1/27            100/1000T | No Yes Up      1000FDx MDIX off 0
    1/28            100/1000T | No Yes Up      1000FDx MDIX off 0



  • 2.  RE: High collision or drop rate messages on 2930f Switch

    EMPLOYEE
    Posted 3 days ago
    If the ports are on full duplex, it must be a drop. That typically happens if there is more traffic to be sent than there is capacity on the link. Can you check on each of the ports what are the error counters: "show interfaces 1/19" (and similar for the other interfaces). If you can do that and capture interface statistics just before and after such a log, you may be able to find the differences ans if it is mostly Tx/Rx and Unicast or Broadcast, and you can see the category of the drops.

    Broadcast traffic (especially with loops) is most likely to generate so much traffic that the egress interface cannot deliver. Do you only have 1Gbps ports? Or also higher / 10Gbps?

    ------------------------------
    Herman Robers
    ------------------------
    If you have urgent issues, always contact your Aruba partner, distributor, or Aruba TAC Support. Check https://www.arubanetworks.com/support-services/contact-support/ for how to contact Aruba TAC. Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.

    In case your problem is solved, please invest the time to post a follow-up with the information on how you solved it. Others can benefit from that.
    ------------------------------



  • 3.  RE: High collision or drop rate messages on 2930f Switch

    Posted yesterday

     

    @Hermann.Robers

     

    Thank you very much for getting back to me. Apologies for the late reply, I read your suggestions but have not had a chance to get back.

     

    I will come back later with a more definitive answer, but at the moment I am fire fighting a load of customer emails.

     

    I will post some screen shots, but what I can say is – the drop count is incrementing steadily over the course of the day.

     

     

    Paul Burns
    Systems Administrator

    DTS Systeme GmbH   Schrewestrasse 2   32051 Herford
    +49 5221 101 3230  
    Paul.Burns@dts.de
    www.dts.de

     

     

    Follow us:


    Geschaeftsfuehrer: Ulrich Moeller, Kai Mallmann, Paul Schoettner, Sitz: Herford, AG Bad Oeynhausen HRB 6847, USt-IdNr. DE125346465
    Unsere Datenschutzhinweise (entsprechend Art. 13 Datenschutz-Grundverordnung) werden Ihnen hier zur Verfuegung gestellt.






  • 4.  RE: High collision or drop rate messages on 2930f Switch

    MVP GURU
    Posted 8 hours ago
    Hello Paul, would you be so kind to post the sanitized output - with e.g, no S/N(s), yes partially/totally anonymized MAC addresses - of show trunks and show lacp CLI commands? also a show interface port-utilization would be of help during potential congestion timeframes (for each port on the switch that command provides a real-time display of the rate at which data is received (Rx) and transmitted (Tx) in terms of kilobits per second (KBits/s), number of packets per second (Pkts/s), and utilization (Util) expressed as a percentage of the total bandwidth available). Are servers, on problematic moments, performing backups or huge files transfers maybe?





  • 5.  RE: High collision or drop rate messages on 2930f Switch

    Posted 2 days ago
    I'm suspicious that the affected ports are to servers. In theory you should observe the high drops on ports facing the storm. Loop protect with inform only would tell you for sure.

    Some servers have LACP but only when configured correctly. Certainly not when the OS is not installed when first setting up. On Comware the LACP edge port only opens on physical port until LACP is negotiated.

    If LACP is ok you could kill a single link and observe the effect. Some servers have dual links but not LACP. Our Nutanix hypervisors have proprietary failover ports. Setting lacp on those would cause problems like this.