APIC CLUSTER M3 SERVER - Application Policy Infrastructure Controller #cisco #server #network

Показать описание

Cisco Application Policy Infrastructure Controller (APIC) features

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 multitenant Cisco ACI fabric.

The main features of the APIC include the following:

●      Application-centric network policies

●      Data-model-based declarative provisioning

●      Application and topology monitoring and troubleshooting

●      Third-party integration

◦    Layer 4 through Layer 7 (L4-L7) services

◦    VMware vCenter and vShield

◦    Microsoft Hyper-V, System Center Virtual Machine Manager (SCVMM), and Azure Pack

◦    Open Virtual Switch (OVS) and OpenStack

◦    Kubernetes, RedHat OpenShift, Docker Enterprise

●      Image management (spine and leaf)

●      Cisco ACI inventory and configuration

●      Implementation on a distributed framework across a cluster of appliances

●      Health scores for critical managed objects (tenants, application profiles, switches, etc.)

●      Fault, event, and performance management

●      Cisco Application Virtual Edge, which can be used as a virtual leaf switch

The controller framework enables broad ecosystem and industry interoperability with Cisco ACI. It enables interoperability between a Cisco ACI environment and management, orchestration, virtualization, and L4-L7 services from a broad range of vendors.

Cisco APIC cluster

The APIC appliance is deployed as a cluster. A minimum of three infrastructure controllers are configured in a cluster to provide control of the scale-out Cisco ACI fabric (Figure 2). The ultimate size of the controller cluster is directly proportionate to the size of the Cisco ACI deployment and is based on the transaction-rate requirements. Any controller in the cluster can service any user for any operation, and a controller can be transparently added to or removed from the cluster.

Medium cluster M3

APIC-CLUSTER-M3

Cluster of 3 APIC-M3 with medium-size CPU, hard ¹drive, and memory configurations (up to 1200 edge ports)

Processor

1.7 GHz Xeon Scalable 3106/85W 8C/11MB Cache/DDR4 2133M x 2

Memory

16GB DDR4-2666-MHz RDIMM/PC4-21300/single rank/x4/1.2v x 6

12

Hard Drive

1 TB 12G SAS 7.2K RPM SFF HDD x 2

PCI Express (PCIe) slots

Cisco UCS VIC 1455 Quad Port 10/25G SFP28 CNA PCIE

Power supply

770W power supply

Cisco medium form factor virtual APIC requirements

Cisco Virtual APIC Requirements

Processor

16 vCPU of 3 GHz or Higher

Memory

96 GB of RAM

DiskSpace

Disk 1: SSD or NVMe – 120GB (root disk)

Disk 2: SSD or NVMe – 360GB (data disk)

I/O latency of 20ms

ESxi

7.0

Cisco ACI licensing components

Cisco ACI licenses are categorized in two key components:

3.1

For Virtual APIC deployments only, a subscription license is required.

3.2 On-premises physical ACI fabric

The on-premises ACI fabric is licensed per Cisco Nexus 9000 device (leaf switch only) running in the ACI fabric. There are tiered license options along with add-on licenses for on-premises ACI deployments.

3.3 Cisco Cloud ACI

Cisco Cloud ACI is a comprehensive solution for simplified operations, automated network connectivity, consistent policy management, and visibility for multiple on-premises data centers and public cloud environments.

Cisco Cloud APIC, which runs natively on a public cloud, is the key component of this solution. The Cloud APIC enables policy translation of ACI policies into cloud-native policies and programs it in every Virtual Machine (VM) workload running application logic. The Cloud APIC is licensed per workload managed by the solution.