Different switches support different load balancing methods eg. src/dst mac, src/dst IP, src/dst port but the one thing common to etherchannel load balancing is that a single conversation between two devices will always be sent down one specific link. This is what you are seeing ie. at one end you have the netapp device and the other the host. This is a single conversation so it will always use the same physical port in the etherchannel group.
Now lets say you had another host and started a conversation between that host and the netapp device. This is now seen as a different conversation and may well be allocated to the other link.
So what you are seeing is normal behaviour. If you actually needed more than 1Gbps throughput between a specific host and the the netapp device etherchannel is not the solution ie. you would need faster interfaces in the devices.
Question We run asr9001 with XR 6.1.3, and we have a very long delay to
login w/ SSH 1 or 2 to the device compare to IOS device. After
investigation, the there is 1s delay between the client KEXDH_INIT and
the server (XR) KEXDH_REPLY. After debug ssh serv...
Introduction The purpose of this document is to demonstrate the Open
Shortest Path First (OSPF) behavior when the V-bit (Virtual-link bit) is
present in a non-backbone area. The V-bit is signaled in Type-1 LSA only
if the router is the endpoint of one or ...
Hi, I am seeing quite a few issues with patch install and wanted to
share my experience and workaround to this. Login to admin via CLI, then
access root with the “shell” command Issue “df –h” and you’ll probably
see the following directory full or nearly ...