Wired Intelligent Edge

 View Only
last person joined: 3 days ago 

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

Switch-Packet loss on switch 5406r

This thread has been viewed 2 times
  • 1.  Switch-Packet loss on switch 5406r

    Posted 6 hours ago

    When performing a file transfer on the network, the 5406 switch, which is in VSF, experiences packet loss on the network.

    Since it is the network router, clients lose connection to other servers and other destinations.

    The file transfer is performed on a server with a 1G network card, so there is no link overload.

    The file transfer occurs between an HP DL360 server and a Blade C3000 with an HP 1Gb Ethernet Pass-Thru Module switch.

    The switch is in version KB.16.11.0020



  • 2.  RE: Switch-Packet loss on switch 5406r

    MVP GURU
    Posted 4 hours ago
    Hi! to evaluate bottlenecks a strategy would involve measuring network throughput figures between hosts with a solution like iperf3. Say, having necessary resources, you're able to setup two hosts (I prefer with Linux as guest OS...) and those two hosts are physically connected directly to your core switch on two of its ports (both copper ports at 1 Gbps? OK, on different Modules? OK) then with IPerf you can measure two ways traffic bandwidth and see the generated traffic to easily saturate those ports' bandwidth. If it happens you can look for culprits (explaining noted disconnections) elsewhere and remove the Core Switch from the equation (you can test traffic A to B either evaluating switching and routing scenarios depending how you place/address the involved hosts).





  • 3.  RE: Switch-Packet loss on switch 5406r

    Posted 2 hours ago
      |   view attached

    We conducted tests using iperf on Linux and on other servers with Linux and Windows.

    The problem does not occur on other servers; it is only observed when iperf or a file transfer is performed on a RedHat server installed on a physical blade in the C3000, where the blade's switch is a pass-thru.

    We evaluated the Linux operating system on this server, and there are no spikes in I/O, bandwidth, memory, processing, etc.

    I created a diagram to try to show the network topology, and note that the Aruba 5406r switch, which stops responding on the network, is not the switch physically connected to the blade.


    Attachment(s)