if i use the inbuilt http script, do i have to modify the script?
i want to poll both the servers on http port, where within the script i can mention the ip address of both servers. because witin the content rule i want to use server A as all user request should go only to server A. but if sever B port 80 goes down or server A port 80 goes down then server A should be out of service
I recently had a customer implement something very similar to what you're wanting to do. They had server A perform some kind of check on server B, and modify the contents of it's healthcheck page accordingly. If server B was accessible on port 80, server A changed it's healthcheck file to read 'UP'. If server B was not accessible, server A changed the contents to read 'DOWN'.
On the CSS we implemented a service similar to the following:
ip address 10.1.1.1
keepalive type http
keepalive port 80 (default)
keepalive method get
keepalive uri '/healthcheck.asp'
(optional) keepalive hash xxxxxxxxxxxxxx
To sum it up, server A was responsible for determining whether or not server B was accessible and updated its own healthcheck page accordingly. Server A could be up and responding on port 80, but because it failed it's keepalive (hash mismatch) the service was taken out of rotation on the LB. If server A were to really become inaccessible it would also keepalive due to port 80 not responding.
I don't really know how to implement this in a custom keepalive script, but you'd likely introduce unnecessary cpu usage to process that script continuously.
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...