If the vserver to vserver connection is made between devices in the same subnet and the client uses the vsever address (rather than a vip address) then this will not be seen via the CSM at all. If the client vserver targets the vip address, then it is probable that you will require source nat to make it work. If a vserver starts a connection to another vserver addess (not vip) in a different subnet and the connection flows via the CSM, then the CSM will show this in its connection table. You can test this via "telnet " and check the connection table. Any working vserver to vip connections will be visible in the connection table. Matthew
Join us live on Thursday, April 8 at 10 am PT (and on demand after) as we join Cisco and HashiCorp executives to discuss the importance of IaC automation, Intersight Service for Terraform, and how to better manage hybrid cloud infrastructure at scale...
Join us live on Thursday, April 8 at 10 am PT (and on demand after) where Cisco and HashiCorp executives will discuss the importance of IaC automation, Cisco Intersight Service for Hashicorp Terraform, and how to better manage hybrid cloud infrastructure...
How to START with Infrastructure as a code for Cisco Cloud Solutions
ACI Ansible Modules Documentation Guide
Cisco Collections on Ansible Galaxy
Cisco DevNet Learning Labs
DevNet Introduction to ACI and Ansible
DevNet Introduction to ACI a...
Here's how to get notified about Cisco software releases, like the Application Policy Infrastructure Controller (APIC) (APIC Software)
Go to software.cisco.com - where you download all Cisco software
Select Software Download