My question has to do with the probe used to check the health of the servers, and more so clarify my understanding of the probes behavior. You'll notice that the http probe doesn't have a port specified. To my understanding (based on reading the config guide), the HTTP probe will inheret (and therefore use) the ports attached to each of the real servers when performing the GET. That is perform a GET on 220.127.116.11:50100 and 18.104.22.168:51000 respectively. Is this correct?
When testing this, i noticed that the probe fails on both servers...i'm hoping i don't need to configure a TCL script to check the health of the servers given this configuration.
Note, usually we have both servers recieving connections on the same port number...however in this situation each server is recieving connections on different ports.
Re: CSM: HTTP probe to check health of a farm with real servers
Your understanding of the probe port inheritance is correct. The CSM should be sending the probe to each of the two servers on different ports with your config. Would it be possible to get a sniffer capture of the server reply to confirm if it is giving a 200 ok response?
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...