Cisco Cyber Vision Performance and Scale Guide, Release 5.5.x

PDF

Cloud sizing guidance

Want to summarize with AI?

Log in

Overview

Use each cloud sizing table only for the Cisco Cyber Vision cloud platform that the table names.

Use this sizing guidance for Cisco Cyber Vision Center deployments on AWS, Azure, and Google Cloud. Size CVSM and Global Center deployments separately.

Cloud sizing scope

Cloud sizing values are platform-specific. Do not translate AWS, Azure, or Google Cloud sizing values from one cloud platform to another.

The Center tables list only the reviewed Release 5.5.x Center sizing points. CVSM and Global Center sizing are separate from these Center component-count tiers.

Before final sizing, use the cloud installation and compatibility documentation for the target release and cloud platform.

Table 1. AWS sizing tiers

Size point

CPU

RAM

Storage

Up to 20,000 components and 150 Sensors without Center DPI

Intel Xeon, 16 cores

64 GB minimum

1 TB SSD minimum with provisioned IOPS

Up to 70,000 components, 400 Sensors, and 21 million stored flows, or with Center DPI

Intel Xeon, 32 cores

192 GB minimum

2 TB SSD minimum with provisioned IOPS

Table 2. Azure sizing tiers

Size point

VM size

RAM

Storage

Up to 20,000 components and 150 Sensors without Center DPI

D16s_v4, 16 vCPUs

64 GB minimum

1 TB managed disk with provisioned IOPS

Up to 70,000 components, 400 Sensors, and 21 million stored flows, or with Center DPI

D48s_v4, 48 vCPUs

192 GB minimum

1 TB managed disk with provisioned IOPS

Table 3. Google Cloud sizing tiers

Size point

CPU

RAM

Storage

Up to 20,000 components and 150 Sensors without Center DPI

Intel Xeon, 32 vCPUs

128 GB minimum

1 TB Hyperdisk with provisioned IOPS

Up to 70,000 components, 400 Sensors, and 21 million stored flows, or with Center DPI

Intel Xeon, 64 vCPUs

256 GB minimum

1 TB Hyperdisk with provisioned IOPS

Google Cloud performance constraints

  • Use Hyperdisk for Center storage. Hyperdisk provides higher IOPS and throughput limits than Persistent Disk.

  • Use N2 or C3 machine series for production environments.

  • Account for AMQP traffic over TCP port 5671 between Centers, Global Centers, and Sensors that exchange data.