Community Feedback

 View Only
last person joined: 2 days ago 

How is the community doing? Do you have any questions or feedback related for the Airheads Community team? This is the place to let us know.
Expand all | Collapse all

Packet loss and latency on some devices after replacing previous HP switchs

This thread has been viewed 18 times
  • 1.  Packet loss and latency on some devices after replacing previous HP switchs

    Posted Jul 25, 2022 09:33 AM

    Hello everyone,

    I've replaced two previous HP switchs (1920S 48G 4SFP) by another two HP (1930 48G 4SFP/SFP+), and now I've some odd issues with those, and I really dont know why, but I hope that the Aruba community with more exp than me, can guide me here.

    On my previous setup, I was using only one firewall connected to one switch, and each switch was connected by only one ethernet cable. There was only one SFP transceiver in one connected to another secundary cabinet. Before installing this new solution, there was no packet loss's on the device that I've (I've around 25 devices on Switch A1 and around 40 on Switch A2), there was no latency for at least one of the services that my endusers reported having it.

    Network diagram:



    Switchs firmware versions:

    Switch A1: 1.0.1.0 (116)

    Switch A2: 1.0.2.0 (125)

    Switchs Configurations:

    Switch A1: https://pastebin.com/DiMsecQf

    Switch A2: https://pastebin.com/LZVnEfeH

    SFP and SFP+ tranceivers specs:

    - All tranceivers are equal per model.

    From Switch A1 and Switch A2, there are no errors and collisions per port (I've checked on 'port configuration' and 'RMON'),

    What I've done regarding that device (without success):

    - Changed the ethernet cable of that device.

    - Used another ethernet port of that device.

    - Connected that device on Switch A2 (it was connected on Switch A1).

    What I've done regarding the latency issue with one service hosted on intranet (connected to Switch A1), and used by office users:

    - Put on production Secundary Firewall, and that problem disappeared.

    NOTE: I've keeped disconnected one of those two SPF+ connections on trunk group, from the start but today I've connect both switchs with that missing link.



  • 2.  RE: Packet loss and latency on some devices after replacing previous HP switchs

    EMPLOYEE
    Posted Jul 26, 2022 04:43 AM
    You may have more success posting this question to the Aruba Instant ON community.

    When I look at the configuration, I see for example for TRK2 that on port 49 (sw-a1) there is the vlan configuration and a port speed config; on port 50 it is not.. it may make sense to get that aligned. Different switch types/models/OS behave different on if VLAN config needs to be done on the port, trunk or both. If the switch has a trunk on port 49&50, and if VLANs are missing on port 50, it may be that half of the packets are dropped when the switch tries to load-balance over both connections, but cannot send the packet because of the missing VLAN. To be clear, I don't know how Instant ON exactly behaves, therefor better to check on the dedicated community rather than the Aruba community.

    It may also be good to map your interfaces to the diagram, and see if the correct VLANs are set on all ports/trunks, and if you can see port errors (drops, resets, errors, port up/down).

    ------------------------------
    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: Packet loss and latency on some devices after replacing previous HP switchs

    Posted Jul 26, 2022 06:33 AM
    @Herman Robers thank you for your reply.

    I've connected that missing link on port 50, but I already had and still have now this problem.

    Didn't knew that there was a exclusive domain for arubainstanton.​