Hi, we have a pair of servers that are load balanced for port 80 traffic to 198.x.x.21 using the h_www_tcp:80 content rule . I recently got a request that port 80 traffic directed to 198.x.x.21/apps/auction be directed only to one of the load balanced servers. I created a service and content rule r_auction_tcp:80, but traffic still seems to matching the load balancing content rule and going to the wrong server (the /app/auction site only exits on the first server).
I thought it might be sticyness so I experimented by assigning my pc IP addresses that have not be used and I would still end up on the wrong server with some of the addresses.
content h_www_tcp:80 vip address 198.x.x.21 port 80 protocol tcp advanced-balance sticky-srcip add service webwa1.1_tcp:80 add service webwa2.1_tcp:80 redundant-index 1064 sticky-inact-timeout 480 active
service webwa1.1_tcp:80 ip address 10.6.3.30 protocol tcp port 80 keepalive type tcp keepalive port 80 redundant-index 130 active
service webwa2.1_tcp:80 ip address 10.6.3.31 protocol tcp port 80 keepalive type tcp keepalive port 80 redundant-index 140 active
content r_auction_tcp:80 vip address 198.x.x.21 redundant-index 1077 add service webwa1.1-auction_tcp:80 port 80 protocol tcp url "/apps/auction/*" active
service webwa1.1-auction_tcp:80 ip address 10.6.3.30 protocol tcp port 80 keepalive type tcp keepalive port 80 redundant-index 131 active
It does work about half the time. Seems to depend on the source IP address, once it doesn't work on a certain address it seems to "never" work. I tried adding the flow-timeout-multiplier 50 to each of the content rules but still have the same result.
Why don't you just disable service webwa1.1_tcp:80 or service webwa2.1_tcp:80? If you disable one of them, by default all traffic will go to the other. Currently, both appear to set as active which means they are available for requests.
The unmanaged mode is also known as Network only switching, which is introduced in Brazos release. It adds the flexibility for customer to use only network automation for service appliance.
If a device is configured a...
Usually, we can access ESXi Shell by pressing Alt+F1 from ESXi DCUI (Direct Console User Interface).
But on HyperFlex system, it just shows black window.
This is expected behavior because HyperFlex redirects ESXi Shell output to SoL...
Configuring an Export Policy Using the GUI
This procedure explains how to configure an Export policy using the APIC GUI. Follow these steps to trigger a backup of your data:
On the menu bar, choose Admi...