Solved! Go to solution.
Hi Don,
Any MX HA pair relies on the VRRP heartbeat for successful communication. This is regardless of other technologies in play in the deployment. As long as the MX can send and receive VRRP traffic form the peer it will operate as expected.
Hi Don,
Any MX HA pair relies on the VRRP heartbeat for successful communication. This is regardless of other technologies in play in the deployment. As long as the MX can send and receive VRRP traffic form the peer it will operate as expected.
APart from that: I have never heard of an ACI device package for Meraki MX. So I'd guess the answer is "no".
That seems like a bit of a misstep by Cisco since they own both technologies. You'd think that they'd want to create an ACI Device Package for integrating their own L4-L7 Service Appliances.
You don't need a device package and this should work fine...device package is certainly nice but can introduce some complexity as well depending on your use case. If you are generally static without a ton of change (spinning workloads up and down etc.) then you can just use it as you would any other firewall and leverage policy in the ACI fabric to direct traffic to it. Here's a good example of how:https://community.cisco.com/t5/data-center-documents/aci-unmanaged-mode-configuration-example-using-...
@RedneckofTech wrote:You don't need a device package and this should work fine...device package is certainly nice but can introduce some complexity as well depending on your use case. If you are generally static without a ton of change (spinning workloads up and down etc.) then you can just use it as you would any other firewall and leverage policy in the ACI fabric to direct traffic to it. Here's a good example of how:https://community.cisco.com/t5/soundcloud downloader data-center-documents/aci-unmanaged-mode-configuration-example-using-asav-in-routed/ta-p/3313318
Thanks for the thorough explanations, I appreciate it.