I'm using a Local Director 416 v4.2.4 and have a problem using http redirect. We were using generic sticky sessions but soon want requests to come via 1 proxied address - SSL sticky doesn't work too well because IE has a habit of creating a new SSLID all the time.
I have a virtual server 10.1.1.2 and real servers 10.1.1.21,22,23 (web01, web02, web01). As I understood it (!) the local director would see a request come into www and redirect the client browser to web01, web02, web03. I have registered the web01 etc with DNS although they're all on the same address - this is fine under generic sticky using bind, of course.
When I go to www.site.co.uk, would I expect to see my browser redirect to web01.site.co.uk. Also the documentation on the release notes is a bit vague - it gives the impression that you need to register the INTERNAL addresses on DNS, surely I must have misunderstood this - if the browser does redirect to web01 and I've got that registered as 10.1.1.21 instead of the external address surely the client will instantly hit 'page not found'.
Any information would be appreciated as I can't find much on this. Also any debugging tips would be a help.
Connections to the main virtual (should be port 80) will get redirected to one of
the three names, web01, web02, or web03. Each one of these names should be registered in DNS as a unique IP address. The reason for this is to ensure that a user is stuck a particular server for the duration of their session.
Hmm.. This seems a bit stupid. It means all of a sudden I have to have an external IP address for all my Web servers - what happened to the concept of virtual servers, NAT etc? Why can't the load balancer still handle using a virtual address seeing as it knows that Web01 = 10.1.1.21, Web02 = 10.1.1.22 etc.
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...