I have following configuration on the content switch and it send the request to both the servers. due to two tcp stream from going via two different server it second request fails and generate false alerts.
It was working fine but since last week it is giving lot of false alerts.
vip address X.X.X.X
add service W8PRAKLQLM01_StateVMS_8HTTP3
add service W8PRAKLQLM02_StateVMS_8HTTP3
Please let me know what should I check to get this fixed. I hardly work with content switch.
Is there a way I can set up to send all the request to primary server and when it dies then and only then it send a request to secondary and when primary comes back online it restore back to primary ????
I am fine if it does not load balance .. but at least it stop sending false alerts..
service sorry !--- This is the server to which you want to default if the primary fails.
ip address 10.10.10.12
keepalive type tcp
vip address 172.17.63.239
add service server1
primarySorryServer sorry !--- This is important here.
Note: After the CSS 11xxx directs requests to a primary sorry server, the switch continues to use the primary sorry server, even when the original server becomes functional. In order to force the connection back to the original server, you must suspend the primary sorry server or wait until the connection is dropped or times out. When the CSS 11xxx initiates a new session, the connection goes back to the original server.
You have configured sticky based on src-ip which means that as long as src IP remains same the user would be sent to the same server.
Now a situation where CSS starts sending the request to different servers could be due to the fact that sticky table was full. In that situation a new connection from same user will be load balanced according to the LB method. If the sticky table is full and none of the sticky entries has expired, the CSS rejects the new sticky request.
You can use sticky-inact-timeout to ensure that sticky entries flush out after they have been inactive for some amount of time.
Please visit the below link for more details about it.
Why do you need native HA: The native HA feature allows two Cisco DCNM
appliances to run as active and standby applications, with their
embedded databases synchronized in real time. Therefore, when the active
DCNM is not functioning, the standby DCNM will...
This document will provide screenshots to outline the steps to setup
TACACS+ configuration to ACI and also the configuration required on
Cisco ACS server. Please find the official Cisco guide for configuring
TACACS+ Authentication to ACI:
Is it supported or NOT supported? It's a frequently asked question.
Before APIC, release 2.3(1f), transit routing was not supported within a
single L3Out profile. In APIC, release 2.3(1f) and later, you can
configure transit routing with a single L3Out pr...