I've configured port-channel for my backup servers and also applied load balancing on the switch (NEXUS 5548 with 2248 FEX). The server is configured with NIC teaming and is set on auto, which negotiates to use 802.3ad for the channel.
All seems to be working fine however the ports do not seem to be balancing the traffic when transmitting unicast traffic as shown from below N5K output:
ChanId Port Rx-Ucst Tx-Ucst Rx-Mcst Tx-Mcst Rx-Bcst Tx-Bcst
The above shows the server is receiving traffic only on one port and not balancing it on another. Server is WIn 2008 R2. These are 1 Gig links with PO are 2 Gig, the backup server needs the 2 Gig but somehow it doesnt seem to utilize the port-channel for incoming traffic.
Currently the load balancing on the N5K platform is set as follows:
N5K# show port-channel load-balance
Port Channel Load-Balancing Configuration: System: source-dest-port
Port Channel Load-Balancing Addresses Used Per-Protocol: Non-IP: source-dest-mac IP: source-dest-port source-dest-ip source-dest-mac
My question here is can i load balance the Tx-Ucst to both ports?
Is there some other way I can utilize both NIC cards on the server to receive traffic?
You seem to be using the recommended hashing algorithm. I would use the "show port-channel load-balance forwarding-path" command to verify that your traffic would actually load balance. Because you mention these are backup servers, I'm concerned there may not be enough entropy in the packets to load balance as you'd like.
Param(s) used to calculate load-balance (Unknown unicast, multicast and broadcas
vlan id: 1
If the "show port-channel load-balance forwarding-path" commands shows that your traffic should transmit out eth102/1/5 or eth102/1/29, then it's possible you are having bug issues. There are known bugs that were fixed in 5.2(9) and 6.1(4) that affect load balancing.
Topology & Design:
Two ACI fabrics
Stretching VLANs using OTV
Both fabrics are advertising BD subnets into same routing domain
Some BDs(or say VLANs) are stretched, but some are not.
Endpoints can move betwee...
VMware Trunk Port Group is supported from ACI version 2.1
VMM integration must be configured properly
ASA device package must be uploaded to APIC
ASAv version must be compatible with ACI and device package version
Topology &Design:Traffic flow within same fabric:Endpoint moves to Fabric-2Bounce Entry Times OutTraffic Black-holedSummarySolutionAppendix:
In the Previous articles of ACI Automation, we are using Postman/Newman a...