System Requirements for AWS

Software Requirements

You can deploy Routing Director on Amazon Web Services (AWS).

You must have login credentials to AWS with permissions to create, modify, and delete VMs, security groups, load balancers, IAM roles and policies, along with access to the S3 bucket.

Hardware Requirements

This section describes the minimum hardware resources that are required on each node virtual machine (VM) in the Routing Director deployment cluster, for evaluation purposes or for small deployments.

The compute, memory, and disk requirements of the cluster nodes can vary based on the intended capacity of the system. The intended capacity depends on the number of devices to be onboarded and monitored, types of sensors, and frequency of telemetry messages. If you increase the number of devices, you'll need higher CPU and memory capacities. Ensure that CPU and memory resources are not oversubscribed.

The bare minimum resources required for each of the nodes in a Routing Director deployment cluster are:

The host servers must have enough CPU, memory, and disk space to accommodate the hardware resources listed in this section.

To ensure high availability, we recommend that you distribute the nodes across separate fault domains. For AWS deployments, place each node in separate availability zones to ensure node and infrastructure high availability.

Network Requirements

The nodes must be able to communicate with each other through SSH. The nodes must be able to sync to an NTP server. SSH is enabled automatically during the VM creation, and you will be asked to enter the NTP server address during the cluster creation. Ensure that there is no firewall blocking NTP or blocking SSH traffic between the nodes in case they are on different servers.

• Cluster in Single or Multiple Subnets
• Cluster with Multiple NICs
• Configure IPv4 Addresses and Hostnames

In AWS deployments, clusters can be deployed across a single or multiple subnets. Multi-subnet deployments are typically used to support high availability by distributing resources across multiple Availability Zones.

You need to have the following IP addresses and hostnames available for the installation.

• Interface IP addresses, one for each of the nodes.

• Internet gateway IP address.

• Primary and secondary DNS server IPv4 addresses.

• NTP server information.

• AWS generated hostnames are available as DNS names when you create the network loadbalancers. You need the following hostnames:

  • Generic ingress hostname shared between gNMI, NETCONF (SSH connections from devices), and the Web GUI—This is a general-purpose hostname that is shared between multiple services and used to access Routing Director from outside the cluster.

  • Active Assurance Test Agent gateway (TAGW)—This hostname serves HTTP-based traffic to the Active Assurance Test Agent endpoint.

  • PCE server—This hostname address is used to establish Path Computational Element Protocol (PCEP) sessions between Routing Director and the devices. You must resolve this hostname (using the nslookup DNS-name command) to determine the corresponding IP address before you deploy the cluster.

    The PCE server hostname configuration is necessary to view dynamic topology updates in your network in real-time. For information on establishing BGP-LS peering and PCEP sessions, see Dynamic Topology Workflow.

  • Routing observability cRPD—This hostname is used by external network devices as BGP Monitoring Protocol (BMP) station IP address to establish the BMP session. You must resolve this hostname (using the nslookup DNS-name command) to determine the corresponding IP address before you deploy the cluster.

  • Routing observability IPFIX—This hostname is used to collect IPFIX data to view predictor events. Predictor events indicate routing, forwarding, and OS exceptions that are identified by Routing Director as a potential indicator of traffic loss. You must resolve this hostname (using the nslookup DNS-name command) to determine the corresponding IP address before you deploy the cluster.

Firewall Requirements

The following section lists the ports that firewalls must allow for communication within and from outside of the cluster.

The following table details the security group that is attached to the EC2 instance and allows traffic flow to and from the VMs.

The following table details the security group that is applied to the AWS load balancer to allow intracluster communication between the nodes.

Allow from everywhere

The following ports must be open for communication from outside the cluster.

Web Browser Requirements

The latest versions of Google Chrome, Mozilla Firefox, and Safari.