Deployment Prerequisites

System Hardware Requirements

For Installation, the system hardware requirements vary based on the number of nodes,

Nodes	Processor and Cores	RAM	Storage
8/16/32/64	x86/x64 based, 16-core CPU	32GB	160GB/320GB/640GB/1.2 TB
128	x86/x64 based, 16-core CPU	64GB	3 TB or more
256	x86/x64 based, 32-core CPU	128GB	6 TB or more
512	x86/x64 based, 32-core CPU	256GB	12 TB or more
1024	x86/x64 based, 64-core CPU	512GB	20 TB or more

The above requirements are only for devices connected through gNMI/ONES T-Agent

Firewall Configuration (Ports to be Opened)

Required Ports to be Open for NCP UI Access

Service	Port Number (TCP)
NCP Web GUI	443

Required Ports to be Open for NCP Chat UI Access

Service	Port Number (TCP)
NCP API	9001

Required Ports to be Open from Agent (Source) to NCP Controller (Destination)

Service	Port Number (TCP)
NCP Collector	50053

Required Ports to be Open from NCP controller(source) to Agent(Destination)

Service's	Port Number's (TCP)
Switch Access over SSH	22
NCP Monitoring	50052

Required Ports to be Open on NCP Controller for NCP Services

Service's	Port Number's (TCP)
gNMI Gateway (Telemetry)	9339
NCP Telemetry Database	5432
API-Server	8080
stream-processer	8093
ksqldb-server	8088
kafka-connect	8083
schema-registry	8081
broker	29092, 9101, 9092
Zookeeper	2181
NCP Collector	50053

These port numbers must be available and allowed through the firewall if the NCP Cotroller and nodes are in different DMZs.

---

You can use the following command to verify the currently used ports:

sudo iptables -L

Node Configuration Requirements

• Network reachability from the NCP Controller

• SSH access must be enabled

• ONES T-agent installed on SONiC switches
• SNMP must be enabled on non-SONiC switches

Browser Requirements for NCP Web GUI Access

• Google Chrome version 107 or later

• Mozilla Firefox version 106 or later