Re: Local Director unable to detect a failed web site
Your problem is based in the Operating system, not the Local Director. The LD is a layer 3 device. Microsoft put their application architecture together different from the Unix world, ie: Any ip address bound to a MS box is answered for by the OS - not the application (IIS in this case) If IIS is hosed up the OS will still answer for the IP you have bound to the NIC of the OS - the OS does not care at layer 3 that you want a higher level reply - LD does its availability checking at Layer 3 - the OS layer for MS. In the Unix world when an application is bound to a port - ie: Apache to port 80, then the apache deamon answers for that ip/port - not the OS - Apache panics and it will not respond at Layer 3 - the OS could be fine, but the LD will know that ip/port is not responding and will take the appropriate actions by your LD config.
Check out the httpprobe feature of the LD - it lets you test for a file in a URL inside the LD.
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...
Cisco Documents are usually accurate, but when it came to the document
on Cisco APIC Signature-Based Transactions it was slightly off the mark.
This document is for those novices to API like me who cant seem to
figure out how to go about performing signat...