I am trying to acheive a reliable keepalive mechanism which mimics a HTTP user authenticating with the service, but the service port is 7002.
I have looked at the above script (port 80), what do I need to do to enable this to happen under the 'service' configuration and the script itself (ie do I just need to change script to reflect port 7002 as apposed to 80 etc).
I changed script and uploaded ok. When the script is part of the keepalive it appears to work.
However, to check authentication was working okay, I changed the username:password to something random (therefore should have failed and marked service as down), but the service is still alive. No matter what I change this value to, as long as it is in the same format ie x:y then its alive. If I omit the username:password field altogether then service is never alive (ie always down), so it appears to be looking at this field.
use a sniffer and see if anonymous is getting through for authentication. Normally a web browser will try to use an anonymouse access first and if your server authentication is letting it through this would be why you are still not failing. A sniffer will show this.
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...