Cisco Crosswork Data Gateway 7.2 Installation and Configuration Guide for Cloud Applications

Resource requirements for Crosswork Data Gateway

Updated: January 29, 2026

Want to summarize with AI?

Details the resource requirements for Crosswork Data Gateway virtual machines, including hardware specifications, supported virtualization platforms, interface configurations, and deployment considerations for traffic management.

VM requirements

This table lists the resource requirements for a Crosswork Data Gateway virtual machine.

Table 1. Resource requirements
Requirement	Description
Data Center	VMware VMware vCenter server 6.7, ESXi 6.5 VMware vCenter Server 7.0.3, ESXi 6.5 and 6.7 VMware vCenter Server 8.0.3 and ESXi 8.0.3 OpenStack OpenStack OSP16 Note While these versions are used for testing, we are not responsible for applying security patches or updates. You need to coordinate with VMware and monitor OpenStack forums to remain informed about the latest security fixes and feature improvements.
Memory	32 GB
Total Disk space (Boot disk + Data disk)	74 GB (50 GB + 24 GB) Note The data disk space is optional. For information on the disk sizing, see the Data Disk Size parameter's description in Configuration parameters required for Crosswork Data Gateway deployment.
vCPU	8

Supported interfaces

The number of interfaces configured on Crosswork Data Gateway affects these areas:

Traffic distribution: Determines which type of traffic flows through each interface.
IP addressing: Defines how many IP addresses are required to uniquely identify the Crosswork Data Gateway.
Port usage: Specifies the type of traffic that must be allowed through each IP address, port, or network connection.

These tables provide detailed configuration options and requirements for each interface setup.

Table 2. Supported interfaces
Number of vNICs	vNIC0	vNIC1	vNIC2	Description
1 vNIC	Management traffic	—	—	All traffic is handled through a single vNIC.
2 vNICs	Management traffic	Southbound data traffic Control/Northbound External data traffic	—	vNIC0 handles management traffic, and vNIC1 handles both control/northbound external data and southbound data traffic.
3 vNICs	Management traffic	Control/Northbound External data traffic	Southbound data traffic	vNIC0 handles management traffic, vNIC1 handles control/northbound external data traffic, and vNIC2 handles southbound data traffic.

Note

Management traffic: Used for accessing the Interactive Console and troubleshooting the Crosswork Data Gateway VM.

Control/Northbound external data traffic: Manages the configuration of collection jobs that are received from Crosswork Cloud and forwards the collected data back to the cloud.

For Crosswork Data Gateway to connect to the cloud, the control or data interface must have internet access.

Southbound data traffic: Handles device management and telemetry data.

Deployment considerations

When deploying with multiple vNICs, you can assign traffic types to the different vNICs based on your network design. For instance, in a 2 vNIC deployment, you can allocate these traffic types:

vNIC0: Management traffic
vNIC1: Control/Northbound external data traffic or Southbound data traffic

Need help?

Open a support case

(Requires a Cisco Service Contract)

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.