The routing on CSM vlans is as follow's and I've got a arp entry for the gateway.
vlan 402 client
ip address 10.81.24.36 255.255.255.240 alt 10.81.24.37 255.255.255.240
alias 10.81.24.38 255.255.255.240
vlan 406 server
ip address 10.81.24.129 255.255.255.192 alt 10.81.24.130 255.255.255.192
alias 10.81.24.131 255.255.255.192
The routing is server, CSM, interface on Cat and then firewall but when doing a tcpdump on firewall I can't see anything when the server starts a connect but I can ping the destination server from the cat and see that on the firewall.
The SW on the CSM is vers 4.2.3 and I've done a tcpdump from the server and it looks like the CSM is resetting the connection.
This is working ok on other CSM's in the platform but they have SW vers 4.2.2.
Thanks for the info, I also noticed that we were having issues with another vserver, that was being routed via the gateway address. It was marked as OOS even with no probe (arp) but the gateway address was in the CSM's arp table. I reset the CSM and this cleared both issues.
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...