My question is in regard to using ACE Bridge mode to transition the current network to provide SLB.
To my understanding the purpose of "Bridge Mode" was to be able to bring up the network in SLB without having to make too many changes to the current vlan and ip address scheme used. The customers real servers are in the same subnet.
My lab setup has worked the other way, meaning I had to place the Severs in a different VLAN, which would require me to make changes to the port vlan configuration.
This is the lab setup I have (please see attached Configs)
Current Server VLAN (300) --- Bridged ----- Client VLAN (30, new)
IP address 192.168.1.1 (SVI L3 ip on the Sup)
RS1, 192.168.1.13, RS2192.168.1.17
Outside Client IP address:
172.16.30.10, 172.16.30.15 /24
With using the current VLAN 300 assigned to the servers, I can ping the VIP address from the (outside) client network host , but When I put in the VIP address I can not bring up the simple web page I have setup. I can go directly to the RS1, and RS2, and I am able to bring up the web page.
I had wireshark running in the background and I would never see the request coming in for the VIP address.
I swaped the VLAN number scheme, and It works fine.
Is this how the bridge mode is supposed to work? If this is the case, then I would need to change all the current vlan port configs that the severs are assigned to.
Please let me know if I am doing this wrong and provide any feedback/suggestion .
Why do you need native HA: The native HA feature allows two Cisco DCNM
appliances to run as active and standby applications, with their
embedded databases synchronized in real time. Therefore, when the active
DCNM is not functioning, the standby DCNM will...
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...