1. traffic hit unsecured port 80 vserver CLEAR-APP
2. Gets translated to https:// (Serverfarm "REDIRECT-APP" and policy "APP-policy")
3. Finally served by Vserver SECURE-APP
virtual 188.8.131.52 tcp www
virtual 184.108.40.206 tcp https
map MAP1 header
match protocol http header Host header-value www3*
no nat client
webhost relocation 220.127.116.11/%p 301
I am trying to probe the redirected servers used in redirect vserver config.
I thought changing the "serverfarm REDIRECT-APP" as following will achieve the objective.My problem is that the redirected server is already defined on the CSM as VServer, as a result CSM doesnt allow me to add vserver/real under redirect-vserver submode.
Not sure that I fully follow what you are trying to do here, but I will have a go.
A redirect vserver will not handle reception of traffic and balancing to real servers, so there would be no need to monitor its relocation address at this point, ie for the redirect vserver to track the state of reals.
Normally you might configure another vserver which accepts the redirected traffic and this is the place that probing would be appropriate. As you would probe the new vservers reals, this new vserver would track the state of its reals.
Typically when using a redirect, its not an option in that you always want it in effect, so theres not a requirement to associate a probe to it.
You could use the global load balance feature to redirect to another site if the local reals were down.
Its not valid to configure a vserver and a real with the same IP, on the same CSM.
Objective is to make sure that the servers where traffic is redirected (using webhost relocation command) are avaialable. If the servers are OOS then the redirected server farm should not try to forward the traffic.
Our problem is the redirect-vserver always stays up on the CSM (even though the destination servers are not available and hence failing the connections)
What action would you require if the redirected host/s was not up? You should be able to achieve this using an additional vserver.
Functionality to do exactly what you require does not exist for the CSM, but there may be a way to achieve this. The simplest would be to configure a vserver to receive the redirect traffic plus configure a backup serverfarm for that vserver, which might go to a "sorry page" server. But because the relocation serverfarm does not involve a real server (it might be a DNS name for example), there is no way to associate a probe with it directly.
I think the GSS product or the CSM global load balance feature are more what you are looking for here.
VMware Trunk Port Group is supported from ACI version 2.1
VMM integration must be configured properly
ASA device package must be uploaded to APIC
ASAv version must be compatible with ACI and device package version
In the Previous articles of ACI Automation, we are using Postman/Newman as the Rest API tool to automate the ACI Configuration.
In this article I’m going to discuss on usin...
One of the first steps in building your ACI Fabric is to go through Fabric Discovery. While Fabric Discovery is usually a straightforward process, there are various issues that may prevent you from discovering an ACI switch. This article wil...