How we can set a load balance or load sharing over WAE cluster
Hi, At this time we have a cluster with two WAEs 7341 ( 4 HDD with 300GB each) connected to a Cisco 7609 router, they are communicating using layer 2 for redirect and return packets between them, the WAEs are caching HTTP, DNS, HTTP and FTP-NATIVE, we think in an acceptable perfomance, but we see more load over WAE1 than WAE2. The WAEs have the same configuration, by this behavior the diskS usage from WAE 1 is dramatically highest versus disks usage WAE 2, the traffic amount handled by wae cluster is in average 700Mbits in rush hours.
We are trying to find a way/configuration to achieve a better load balance/sharing like 50/50 for both WAEs. This is our current problem. Thanks for the help you can brings us.
Re: How we can set a load balance or load sharing over WAE clus
It appears that you are using the default mask-assign value of 0x1741. Using the default value will sometimes create a situation where one WAE will be more utilized than the other. You can change the mask-assign value depending on your internal IP addressing scheme which will yield a better ratio of utilization. Below is some information regarding mask-assign values. It was taken from the following link.
Mask assignment can further enhance the performance of L2 redirection. The ternary content addressable memory (TCAM) can be programmed with a combined mask assignment table and redirect list. All redirected packets are switched in hardware, potentially at line rate. The current Catalyst platform supports a 7-bit mask, with default mask of 0x1741 on the source IP address. Fine tuning of the mask can yield better traffic distribution to the WAEs. For example, if a network uses only 191.x.x.x address space, the most significant bit can be re-used on the last 3 octets, such as 0x0751, because the leading octet (191) is always the same.
The following examples show output from show ip wccp 61detail with a mask of 0x7. Notice that four WAEs are equally distributed from address 0 to 7.
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
In the Previous articles of ACI Automation, we are using Postman/Newman as the Rest API tool to automate the ACI Configuration.
In this article I’m going to discuss on usin...
One of the first steps in building your ACI Fabric is to go through Fabric Discovery. While Fabric Discovery is usually a straightforward process, there are various issues that may prevent you from discovering an ACI switch. This article wil...