I haven't found the above combination to be particularly well documented by Cisco (and there appears to be no documentation on ASA and the VNMC replacement Prime Network Services controller).
Anyhow we have struggled through! The last hurdle seems to be getting the ASA vservice on the Nexus to connect to the ASA inside interface (192.168.10.1). This all works fine in terms of connectivity, ie I can ping it from the Nexus. We can enter the commands:
vservice node test type asa
ip address 192.168.10.1
without any errors. However, checking the status with sh vservice detail or any permutation of the sh vservice command doesn't return any information at all. Just a new prompt.
Does anyone have any experience of the Nexus and the ASAv? I can hardly find anything on Google or Cisco.
Cisco Champion Radio · S7|E30 Taming Your AI/ ML Workloads with Kubeflow
As organizations increasingly introduce machine learning (ML) capabilities to their existing products, their artificial intelligence (AI) projects and operations complexity g...
Cisco IOS-XE 17.3.1 – Catalyst Switching Updates
Table of Contents
Hardware Additions since IOS-XE 17.2.1
Key Summary Features
Platform and Infra Features
High Availability Features
Routing / MPLS / VPN Features
Hi Everyone,I have 2 queries1. After we configure the IPSec VPN in a Cisco Router, how do we identify and check that the traffic is flowing through the tunnel? Are there any commands and ways to find it out?2. What are some of t...
Cisco Champion Radio · S7|E29 Increase Visibility and Enhance Security with Cisco AI Endpoint Analytics
Cisco is on a journey to making networking smarter with artificial intelligence and machine learning. The latest stop in this journey, Cisco AI...