Customer has an ACE installed as attached. With the server set with a DG of the ACE and traffic directed at the servers real IP address (ping, for example), we never seem to receive a response. I've configured the VLAN interfaces on both sides of the ACE with "permit ip any any" ACLs.
Should I expect the ACE to act like a router in this instance (and not care) or is it trying to act like a stateful device i.e. it should see the echo request first?
Yes, the only caveat was applying it in the right virtual context. After I applied it to the correct interfaces in the right context, ping worked fine. It was covered in this section of the configuration guide:
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...