Hypervisor and vCenter

• VMware vCenter Server 6.7 Update 3b or later (ESXi 6.7 Update 1 installed on hosts).

• VMware vCenter Server 6.5 Update 2d or later (ESXi 6.5 Update 2 installed on hosts)

Memory

96 GB

Storage

Storage requirements vary based on factors such as the number of devices being supported, and the type of deployment selected.

For demos and lab environments, Cisco recommends the thin provision format as it requires the least amount of storage on the host machine. This deployment configuration uses roughly 23 GB of storage.

For live systems, Cisco recommends the Thick provision eager zeroed format which allocates 1 TB of storage by default. This should be sufficient for most customer use cases. Due to their performance, solid state drives (SSD) are preferred over traditional hard disk drives (HDD). If you are using HDD, the minimum speed should be 10,000 RPM.

For more information, see the volume requirements displayed in the VMware GUI when configuring disk space, as shown in Install Cisco Crosswork Optimization Engine.

vCPU

16 vCPUs

CPU Planning (avoid overcommittment)

CPU/memory overcommitment occurs when the vCPUs are running on a host are more than the total number of physical processor cores in that host. VMware vCenter/ESXi allows this for the flexibility in deploying and running the VMs on physical hosts. It is natural to assume that the vCenter users will try to maximize the physical resources usage by deploying and running a reasonably high amount of VMs on a specific ESXi host. However, it can lead to a problem manifested in a "soft lockup" situation, where a VM will not be able to get a vCPU allocated in a reasonable amount of time.

Network Connections

For live deployments, Cisco recommends using dual interfaces, one for the management network and one for the data network between Cisco Crosswork Optimization Engine and Cisco Crosswork Data Gateway.

IP Addresses

Two IP addresses (IPv4): One public IP for the Management Network virtual interface and one public or private IP for the Data Network virtual interface.

NTP Servers

The IPv4 addresses or host names of the NTP servers you plan to use. If you want to enter multiple NTP servers, separate them with spaces. These should be the same NTP servers you use to synchronize devices, clients, and servers across your network. Confirm that the NTP servers are reachable on the network before attempting the install. The install will fail if the servers cannot be reached.

DNS Servers

The IPv4 addresses of the DNS servers you plan to use. These should be the same DNS servers you use to resolve host names across your network. Confirm that the DNS servers are reachable on the network before attempting the install. The install will fail if the servers cannot be reached.

DNS Search Domain

The search domain you want to use with the DNS servers (for example, cisco.com). You can only have one search domain.

Disclaimer

The text of the legal disclaimer displayed to clients accessing the VM via the command line. Consult your organization's IT or legal department for the content of this text.

6.6.3 + SMU¹

• 6.5.3 + SMU (CSCvp83001)

• 6.6.3 + SMU

  See footnote 1

• 6.5.3 + SMU (CSCvp83001)²

• 6.6.3 + SMU

  See footnote 1 and 2

6.6.3 + SMU ³

See footnote 1

6.6.3 + SMU

See footnote 1

• 6.5.3 + SMU (CSCvp83001)

• 6.6.3 + SMU

  See footnote 1

Cisco Network Services Orchestrator (Cisco NSO)

4.4.5.3

Cisco IOS XR Network Element Driver (NED)

6.6.1

Cisco IOS Network Element Driver

5.9.2

SR Policy Visualization and Provisioning

• 5,000 nodes

• 50,000 interfaces

2,000 SR Policies

RSVP-TE Tunnel (PCE initiated) Visualization and Provisioning

• 5,000 nodes

• 50,000 interfaces

2,000 RSVP-TE Tunnels

RSVP-TE Tunnel (PCC initiated) Visualization only

• 5,000 nodes

• 50,000 interfaces

2,000 RSVP-TE Tunnels

Bandwidth Optimization Function Pack

• 2,000 nodes

• 20,000 interfaces

—

Bandwidth On Demand Function Pack (with Priority Mode)

• 5,000 nodes

• 50,000 interfaces

—

Bandwidth On Demand Function Pack (without Priority Mode)

• 2,000 nodes

• 20,000 interfaces

—

Demand Deduction Function Pack

500 nodes

—

Topology Visualization (including SR Policies)

Supported

Supported

Egress Peer Engineering (EPE) is limited to EPE adjacency segment IDs (SIDs)

SR Policy Creation, Modification, and Deletion

Supported

Supported

EPE is limited to EPE adjacency SIDs

Bandwidth on Demand Function Pack

Supported

Supported

Not Supported

Bandwidth Optimization Function Pack

Only single area is supported

Only single level is supported

Not Supported

RSVP TE

Supported

Supported

Supported with IGP between ASes but not EPE.

PCC Initiatied

Requires Autoroute Announce configuration in individual tunnel interface:

int tunnel-te <id>
autoroute-announce
exclude-traffic segment-routing

Requires Static Route configuration pointing to the tunnel interface:

router static
address-family ipv4 unicast
<destination-ip> <tunnel-interface>

PCE Initiatied

Requires Autoroute Announce configuration under MPLS TE:

mpls traffic-eng
pcc
stateful-client
autoroute-announce

Google Chrome

(recommended)

75 or later

Mozilla Firefox

70 or later

22

TCP

Remote SSH traffic

323

UDP

Network Time Protocol (NTP) listener

30603

TCP

User interface (NGINX server listens for secure connections on port 443)

30607

TCP

To collect vitals from and download images to Cisco Crosswork Data Gateway

30649

TCP

To monitor Cisco Crosswork Data Gateway status.

30993

TCP

Cisco Crosswork Data Gateway sends the collected data to Crosswork Kafka destination.

7

TCP/UDP

Discover endpoints using ICMP

53

TCP/UDP

Connect to DNS

123

UDP

Network Time Protocol (NTP)

830

TCP

Initiate NETCONF