On this page:
The AppDynamics integration with Cisco ACI™ solution provides end-to-end visibility into the application and network layers within a data center. The following sections provide instructions to integrate AppDynamics with Cisco ACI™ and verify inter-operability between the applications.
Ensure that the following minimum system requirements are met for the integration:
rootaccess permissions on the agent host to install the Network Agent
If your applications are running in a Kubernetes environment, enable the Kubernetes-ACI integration, before you proceed with the AppDynamics and Cisco ACI™ integration. For more information, see Cisco ACI and Kubernetes Integration
The Cisco APIC controller supports the import and storing of an SSL certificate and private key into the controller. After import, the certificate and private key can be used to create a secure and trusted environment between Cisco APIC controller and AppDynamics.
At a command prompt, change directories to the following location:
Import the self-signed certificate from the appropriate directory as follows:
keytool -import -keystore cacerts.jks -file /path/to/RootCA.crt
If you are using AppDynamics controller version 4.5.10 or earlier, enable the Cisco ACI Integration manually as follows.
Configure AppDynamics Controller for Cisco ACI integration as follows:
Use the password set for the root user of the controller when the controller was installed. For more information, refer to User Management.
In Controller Settings, search for netviz.aci.integration.enabled and set this field to true. Click Save.
If you are using AppDynamics controller version 4.5.11 or later, the Cisco ACI Integration feature is enabled by default. If you are using AppDynamics controller version 4.5.10 or earlier, enable Cisco ACI Integration manually before you configure your credentials.
Configure the Cisco ACI credentials to complete the integration as follows:
Log in to the AppDynamics controller as an administrator:
full URL along with the port details to the Cisco APIC Server. For example,
AppDynamics initiates the background processes required to inter-operate with the Cisco ACI solution.
The AppDynamics-Cisco ACI integration brings together the logical constructs of both the solutions. This enables the network operations admin and the application operations admin to obtain a comprehensive end-to-end view from the application to the network. Correlating or mapping the components of both solutions helps the admins triage and troubleshoot issues quickly.
AppDynamics application model serves as the framework around which AppDynamics organizes and presents application performance information. A typical application environment consists of different components that interact in multiple ways.
A business application is the top-level container in the AppDynamics model. A business application contains a set of related services and business transactions.
A node in the AppDynamics model corresponds to a monitored server or JVM in the application environment. A node is the smallest unit of the modeled environment. Depending on the agent type, a node may correspond to an individual application server, JVM, CLR, PHP application, and Apache Web server.
A tier is a unit in the AppDynamics application model which is a grouping of one or more nodes. There is no interaction among nodes within a single tier.
AppDynamics components are logically arranged as follows:
Application > Tiers > Nodes
Cisco ACI is a Software-Defined Networking (SDN) solution. It simplifies, optimizes, and accelerates infrastructure deployment and governance, and expedites the application deployment lifecycle.
Cisco ACI implements Cisco’s intent-based networking framework. It captures higher-level business and user intent in the form of a policy and converts this intent into the network constructs necessary to dynamically provision the network, security, and infrastructure services.
The infrastructure controller is the main architectural component of the Cisco ACI solution. It is the unified point of automation and management for the Cisco ACI fabric, policy enforcement, and health monitoring. The APIC appliance is a centralized, clustered controller that optimizes performance and unifies the operation of physical and virtual environments. The controller manages and operates a scalable multi-tenant Cisco ACI fabric.
A tenant is a logical container for policies that enable an administrator to exercise domain-based access control.
An application profile defines the policies, services, and relationships between endpoint groups (EPGs).
An EPG is a managed object that is a named logical entity. It is a collection of endpoints (EPs).
Endpoints are devices that are connected to the network directly or indirectly. They have an address (identity), a location, and attributes (such as version).
The logical topology in the Cisco APIC controller is as follows:
Application profile > EPGs > EPs
The following figure depicts the correlation of AppDynamics and Cisco ACI components.
After you configure Cisco ACI credentials, all AppDynamics applications are displayed in the AppDynamics Applications to ACI Tenant Mappings page.
These mappings are based on the mappings between AppDynamics nodes and Cisco ACI endpoints. When the endpoints in different tenants have the same IP address, a node-to-endpoint mapping conflict occurs. AppDynamics resolves these conflicts based on heuristic data. However, if the conflicts persist, you must resolve these conflicts manually, as described in Mapping Applications to Tenants Manually.
The application to Cisco ACI tenant map is left blank in AppDynamics Applications to ACI Tenant Mappings page when there is a conflict in auto-mapping. You can map applications to Cisco ACI tenants manually:
You can override the auto-map and map the application to another Cisco ACI tenant using the Map Application to Tenant window. To override the auto-map, Unmap the application to tenant map and map it to another Cisco ACI tenant.
To revert to auto-map, Unmap the application to tenant map and refresh the page. AppDynamics auto-maps the application to the corresponding Cisco ACI tenant.