The following table provides the maximum supported values for each collector instance for different footprints.

Note: For the VM based VMware Telco Cloud Service Assurance deployment, the maximum scaling support is 200 K devices, 80 million metrics, and 2 million notifications.
Collector Name Demo (750 devices) 7.5 K and above
Traffic Flows (per second) 1 K 1.25 K - 10 K
IPSLA collectors Maximum of 500 IPSLA devices supported across all footprints.
Supports 32 probes per device.
VMware Aria Operations collectors Maximum of 1K notifications per 5 minutes polling interval. Maximum of 6K notifications per 5 minutes polling interval.
Note:
  • 1 OI Server supports 6K notifications per 5 minutes polling interval.
  • 1 OI Server supports 1 VMware Aria collector
Number of CNFs supported per NFV-SOL collector Maximum of 100 CNFs. Maximum of 20K CNFs.
Note: 1 ESM Server supports 1 NFV-SOL collector.
Number of pods supported per VMware Aria Operations collector Maximum of 750 pods. Maximum of 100K pods.
Note: 1 ESM Server supports 1 VMware Aria collector.
VIMs 50 bono and 50 sprouts services.
Cisco ACI collectors Maximum of 150 switches per ACI collector.
Kafka to Kafka collector for M&R data ingestion 300 K metrics. 6 million metrics.
Kafka to Kafka collector for performance data ingestion 300 K metrics. Maximum limit is 80 million metrics.
Kafka to Kafka collector for Events 7500 events Maximum limit is 10 million events.
Note: For VM Based deployment the maximum limit is 2 million events

System Requirements for Remote Collector VMs

  • The maximum number of Remote data center supported is 150.
  • Per Remote data center (RDC) maximum of 60 collectors can be configured.
  • The recommended size for Remote Collector VMs is 16 vCPU and 32 GB RAM.
  • The latency between Domain Manager VM and collectors running on Remote Collector VM must be between 50 to 60 milliseconds.