Installation Requirements

This section contains the following topics:

Profile Specifications

This table provides an overview of the scale support for various features and the hardware specifications for each profile in Cisco Crosswork Planning.

Table 1. Profile Specifications

Parameters

Profile 1

Profile 2

Profile 3

Scale Support

Total number of network devices

1000

3000

6000

Total number of interfaces

10000

25000

50000

Total number of demands

50000

100000

500000

Total number of policies (SR and RSVP)

2000

5000

10000

Total number of VPNs

4

Endpoints per VPN service: 30

4

Endpoints per VPN service: 60

8

Endpoints per VPN service: 60

Hardware Requirements

Number of VMs

1

2

2

CPU

16 vCPU

16 vCPU

24 vCPU

Memory

128 GB

128 GB

256 GB

Disk space

1 TB

1 TB

2 TB

Note

There is no provision to tune the resource usage settings for individual services.

VMware Settings

If your vCenter data center does not meet these requirements, the Virtual Machine (VMs) has to be deployed individually. For more information on manual installation, see Install Cisco Crosswork Planning Using the vCenter vSphere UI.

  • Hypervisor and vCenter supported:

    • VMware vCenter Server 8.0 (U2c or later) and ESXi 8.0 (U2b or later)

    • VMware vCenter Server 7.0 (U3p or later) and ESXi 7.0 (U3p or later)

  • The machine where you run the installer must have high speed network connectivity to the vCenter data center where you plan to install Cisco Crosswork Planning.

  • Cisco Crosswork Planning VM must be hosted on hardware with Hyper Threading disabled.

  • Ensure that profile-driven storage is enabled by the vCenter admin user. Query permissions for the vCenter user at the root level (for all resources) of the vCenter.

  • The networks required for the Crosswork Management and Data networks need to be built and configured in the data centers, and must allow low latency L2 communication (latency with RTT <= 10 ms).

  • Ensure the user account you use for accessing vCenter has the following privileges:

    • VM (Provisioning): Clone VM on the VM you are cloning.

    • VM (Provisioning): Customize on the VM or VM folder if you are customizing the guest operating system.

    • VM (Inventory): Create from the existing VM on the data center or VM folder.

    • VM (Configuration): Add new disk on the data center or VM folder.

    • Resource: Assign a VM to resource pool on the destination host or resource pool.

    • Datastore: Allocate space on the destination datastore or datastore folder.

    • Network: Assign the network to which the VM will be assigned.

    • Profile-driven storage (Query): This permission setting needs to be allowed at the root of the data center tree level.

  • We also recommend you to enable vCenter storage control.

Cisco Crosswork Planning VM Requirements

This section explains the resource requirements per VM to deploy Cisco Crosswork Planning.

Table 2. Network Requirements

Requirement

Description

Network Connections

For production deployments, we recommend that you use dual interfaces, one for the Management network and one for the Data network.

For optimal performance, the Management and Data networks should use links configured at a minimum of 10 Gbps with a latency of less than 10 milliseconds.

IP Addresses

Four IPv4 or IPv6 addresses: A management and data IP address for the Cisco Crosswork Planning node being deployed and two additional IP addresses to be used as the Virtual IP (VIP) address (one for the Management network and one for the Data network).

Note

 

  • Cisco Crosswork Planning does not support dual-stack configurations. Therefore, all addresses for the environment must be either IPv4 or IPv6.

  • The IP addresses must be able to reach the gateway address for the network, or the installation will fail.

  • When deploying with IPv6, the installation needs to run on an IPv6 enabled container/VM.

  • At this time, your IP allocation is permanent and cannot be changed without re-deployment. For more information, contact the Cisco Customer Experience team.

Interfaces

Cisco Crosswork Planning is deployed on a single VM with two interfaces.

  • No. of NICs: 2

  • vNIC0: Management Traffic (for accessing the interactive console and passing the Control/Data information between servers).

  • vNIC1: Device Access Traffic (for device access and data collection).

NTP Server

The IPv4 or IPv6 addresses or host names of the NTP server 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 the Cisco Crosswork Planning VM clock, devices, clients, and servers across your network.

Ensure that the NTP servers are reachable on the network before attempting installation. The installation will fail if the servers cannot be reached.

DNS Servers

The IPv4 or IPv6 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.

Ensure that the DNS servers are reachable on the network before attempting installation. The installation 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 have only one search domain.

Backup Server

Cisco Crosswork Planning will back up the configuration of the system to an external server using SCP. The SCP server storage requirements will vary slightly but you must have at least 25 GB of storage.

FQDN (Optional)

The installation process supports using either a VIP (Virtual IP address) or an FQDN (Fully Qualified Domain Name) to access the VM.

If you choose to use the FQDN, you will need one for the Management and one for the Data network.

Cisco Crosswork Planning deployed on a single VM does not support dual-stack configurations. Therefore, all FQDN addresses configured for the deployment environment must be either IPv4 or IPv6.

Note

 

If you choose to supply the FQDNs during the initial installation, the DNS server must be populated with them before the VM is powered on; otherwise, the installation script will fail to complete the environment setup.

IOS XR Version Support

Cisco Crosswork Planning supports the following Cisco IOS XR software versions.

Table 3. IOS XR Version Support

Device

Tested with version

SR-PCE

7.7.2, 7.11.2, 24.1.2, 24.2.1

XRv 9000

7.7.2, 7.11.2, 24.1.2, 24.2.1

ASR 9000

7.7.2, 7.11.2, 24.1.2, 24.2.1

NCS 5500

7.7.2, 7.11.2, 24.1.2, 24.2.1

NCS 540

7.7.2, 7.11.2, 24.1.2, 24.2.1

Cisco 8000 series routers

7.7.2, 7.11.2, 24.1.2, 24.2.1

Supported Web Browsers

The following table lists the supported browser versions for Cisco Crosswork Planning:

Browser

Version

Google Chrome

127 or later

Mozilla Firefox

128 or later

Port Requirements

The following TCP/UDP port numbers need to be allowed through any external firewall or access-list rules deployed by the data center administrator.

Table 4. Internal Ports Used by Cisco Crosswork Planning Deployment
Port Protocol Used for

111

TCP/UDP

GlusterFS (port mapper)

279

TCP

Calico BGP (Kubernetes)

500

UDP

IPSec

2379/2380

TCP

Kubernetes etcd

4500

UDP

IPSec

6443

TCP

kube-apiserver (Kubernetes)

9100

TCP

Kubernetes metamonitoring

10250

TCP

kubelet (Kubernetes)

24007

TCP

GlusterFS

30606

TCP

Docker Registry

30742

TCP

WAE Modeling Daemon (WMD)

30744

TCP

OPM/RPC

31210

UDP

NetFlow packets

49152:49370

TCP

GlusterFS
Table 5. Ports Used by Cisco Crosswork Planning Deployment on the Management Network
Port Protocol Used for Direction
30602 TCP Monitoring the installation (Cisco Crosswork Planning) Inbound
30603 TCP Cisco Crosswork Planning Web user interface (NGINX server listens for secure connections on port 443) Inbound
7 TCP/UDP Discovering endpoints using ICMP Outbound
22 TCP Initiating SSH connections with managed devices Outbound
22 TCP Remote SSH connection Inbound
53 TCP/UDP Connecting to DNS Outbound
123 UDP Network Time Protocol (NTP) Outbound
830 TCP Initiating NETCONF Outbound
Table 6. Ports Used by Cisco Crosswork Planning Deployment on the Device Network
Port Protocol Used for Direction

161

 UDP SNMP Collector Outbound

30621

TCP

FTP (available on data interface only). The additional ports used for file transfer are 31121 (TCP), 31122 (TCP), and 31123 (TCP).

This port is available only when the supported application is installed on Cisco Crosswork and the FTP settings are enabled.

Inbound

30622

TCP

SFTP (available on data interface only)

This port is available only when the supported application is installed on Cisco Crosswork and the SFTP settings are enabled.

Inbound