WE have a BGP configuration that advertises the Main site Internet router subnet to the PE router. If the Main site looses Internet connectivity, the BGP configuration will advertise the Main site Internet subnet to the DR PE router.
This allows the DNS to stay the same during Failover situations.
We have a CSS at the Main site that has VIP addresses in the 184.108.40.206 subnet and web requests are sent to it, then if the corresponding service is up, it gets sent to the Main site server, if that server is down, they get sent to DR through the Main site, then through the MPLS network.
I want to do the same thing in reverse at the DR site, to (if just Main site internet is down) route to the Main site 220.127.116.11 subnet which will be a CSS VIP, sitting in the DR site switch between the DR router and DR PIX.
If that server is down to redirect web requests to the DR server.
This way DNS never gets changed.
CAn I have the Dr CSS interface in the DR subnet of 18.104.22.168
and have the VIP address in the Main site subnet of 22.214.171.124?
Would it be benificial to have the CSS devices communicate via an app service?
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...