Site Planning

Myriad Pre-Install Network Worksheet

IMPORTANT! Review all the requirements below, and then download the Myriad Pre-Install Network Worksheet. The document provides instructions and information for setting up a Myriad cluster system. It includes a worksheet with various settings and requirements that need to be completed before the installation process. The document also mentions the importance of reviewing this Site Planning page.

The worksheet includes sections for initializing cluster settings, creating password settings, configuring Network Time Protocol (NTP) settings, setting up Unified UI (UUI) admin user settings, and managing certificate settings. Each section has a table with specific fields that need to be filled in.

The network requirements section outlines the inputs needed for the Setup Wizard during the initial configuration of the Myriad cluster. These requirements include providing a cluster name, an Ingress FQDN (fully qualified domain name) for accessing the cluster, an Autonomous System Number (ASN) for the cluster (with a default value of 65000), CIDR notation for the internal subnet, external IPv4 range (in CIDR notation), NTP server information, and SSL certificate options.

The document also includes a table that summarizes the TCP/UDP ports used on the external interfaces of the Myriad cluster. The table lists the node types, interfaces, ports, protocols, directions, and purposes for each port.

In summary, the document provides a comprehensive guide for preparing and configuring the network settings for a Myriad cluster system, including the necessary inputs for the Setup Wizard and information about the TCP/UDP ports used by the system.

Border Gateway Protocol (BGP) Requirements

BGP is an external routing protocol used across WANs and the internet. To connect a Myriad cluster, your switch or switches require the Myriad-facing ports to be configured for BGP with unnumbered interfaces and Equal Cost Multipath (ECMP); using unnumbered interfaces eliminates the need to explicitly assign IP addresses, saving time and conserving addresses. ECMP provides load balancing of incoming connections across all Myriad load balancer node interfaces.

Note: Use of a peer group is optional, but recommended.

If you do not use BGP for routing throughout the datacenter network, then you must advertise or configure routes to the Myriad cluster using some method other than BGP, so that clients who need to access to the Myriad cluster can locate it.

Common Questions and Answers

This section answers some questions related to Myriad networking.

How do I configure my switches to use BGP, ECMP, and unnumbered interfaces? Quantum is unable to provide vendor-specific switch configuration guidance, because Quantum does not have expert knowledge of every layer-3 switch. As a customer, you understand the details of your network architecture and configuration. For help configuring your switches, reach out to your switch hardware and/or switch vendor.
Does Myriad have to use BGP? Is there an alternative? Myriad requires BGP support on the switches to which it is connected.
Do I need to use BGP routing throughout my entire datacenter to use Myriad? No, only the switches directly connected to Myriad require BGP support. Keep in mind that if you are not using BGP throughout your network you will need to advertise routes to Myriad using another routing protocol or configure static routes as appropriate.

I do not currently have Layer 3 features like BGP and ECMP enabled on my switches. What is required to enable these features? Depending on your switch make, model, operating system, and current license tier, you might need additional licenses to enable L3 functionality like BGP, for which there might be a fee. The following table summarizes some information, but contact your switch or switch OS vendor for guidance:

Switch Vendor	L3 Function Licensing Info
Arista	Routing functionality including BGP requires the E license.
Cisco	License level varies by product, search for BGP at https://cfnng.cisco.com/browse/switching/features. Cisco licensing is extremely complex. Contact your Cisco vendor for guidance.
HPE/Aruba	All CX Series Layer 3 switches appear to support BGP, with the exception of the CX 6200. BGP functionality is included in the base Foundation license tier.
Juniper	Juniper Layer 3 switches support BGP with the Advanced 1 software license.
Netgear	M4500-series switches support BGP, no additional license required.
Nvidia/Mellanox	Nvidia switches are OCP devices that support a variety of switch operating systems. Consult the chosen switch OS provider for information on BGP support and licensing.

Can I connect clients directly to the ports on the Load Balancer nodes? No, the Load Balancer node ports must be connected to an L3-capable switch to enable BGP and ECMP to work.

Network Requirements

The customer site must contain an available GbE connection to the network within 2 meters (approximately 6 feet) of the Myriad system for Quantum Professional Services purposes. If the customer site contains separate management and data networks, then a connection to each is required.

The following network-related items are needed as inputs to the Setup Wizard when you initially configure you Myriad cluster.

Cluster Name: A name for the Myriad cluster to distinguish it from other systems.
Ingress FQDN: The fully qualified domain name (FQDN) that will be used to access the Myriad cluster.
ASN: This is the Autonomous System Number chosen for the Myriad cluster. Any ASN in the private range (64512 – 65534) is acceptable, as long as it is unique within your environment. The default ASN is 65000.
Internal Subnet: An IP range to be used by Myriad for the internal cluster network. This should be a non-routable range that is not otherwise in use by devices on the customer network that need access to this Myriad cluster. The range must be expressed in CIDR notation. Quantum recommends the default of 172.16.0.0/16, unless there is a conflict with this range.
External IPv4 Range (in CIDR notation): An IP range to be used by Myriad for the external network connections to your network. This should be a private IP range that is routable and must be expressed using CIDR notation. A block as small as /29 (which contains 8 IP addresses) is acceptable for Myriad clusters that may grow to contain up to 40 storage nodes. If more than 40 storage nodes are anticipated, a larger block should be assigned to avoid the need for reconfiguration in the future. The first IP in this range is assigned as the ingress IP for the cluster. The rest of the IP addresses in the range are used sequentially to provide egress IP addresses for the load balancer nodes (Quantum recommends this range is non-routable and not used by any devices on your network).
NTP: To enable NTP, you must provide the hostname or IP address of the chosen NTP server or server pool as well as the time zone.

Note: Your SMTP server must be configured to accept traffic from the entire Myriad external IPv4 range (for example, 192.168.1.16/28).
SSL Certificates: By default, Myriad uses a self-signed certificate for browser connectivity. Optionally, you can upload a certificate file and key file, or a PEM chain file.
DHCP must be able to assign an address to the 1 GbE deployment node management port (eth0).
All Myriad ethernet ports that connect to the customer’s network (1 GbE management and 100 GbE data) must be able to reach the same customer-designated DNS server’s IP address.

Ports and Protocols

The table below summarizes the TCP/UDP ports used on the external interfaces and the purpose for each.

Node Type	Interface(s)	Port	Protocol	Direction	Purpose
Deployment	1 GbE	443	TCP	In and Out	HTTPS Software Image Download
		67	UDP	In	DHCP
		68	UDP	Out	DHCP
		123	UDP	In and Out	NTP Time Synchronization
Load Balancer	100 GbE	2049	TCP	In	NFSv4 Server Listener
		6343	UDP	Out	sFLOW (Optional)
		161	UDP	In	SNMP (Optional)
		162	UDP	Out	SNMP (Optional)
		587	TCP	Out	SMTPS Email Alerts (Optional)
		123	UDP	In and Out	NTP Time Synchronization
		179	TCP	In and Out	BGP
		53	UDP	In and Out	DNS

NVMe Storage Node

Technical, Physical, and Environmental Specifications

This section lists the physical and environmental specifications for the NVMe storage node. See the Hardware Overview to view images of the NVMe storage node and its hardware specifications.

Rack Compatibility

The NVMe storage node is designed to be installed into a rack that meets the EIA-310 standard at a minimum. See EIA-310 Rack Standard of usable space measured from front rack frame to the rear rack frame. The NVMe storage node requires 1U of rack space.

Note: The NVMe storage node rails support both square and non-threaded round hole racks.

Dimensions

Height: 1.7 in. (4.3 cm)
Width: 17.2 in. (43.7 cm)
Depth: 23.5 in. (59.7 cm)

Environmental Requirements

The NVMe storage node must acclimate to ambient temperature prior to power up to avoid condensation or other effects of temperature change.

Operating Temperature: 10º to 35º C (50º to 95º F)
Non-operating Temperature: -40º to 60º C (-40º to 140º F)
Operating Relative Humidity: 8% to 90% (non-condensing)
Non-operating Relative Humidity: 5% to 95% (non-condensing)

Power Requirements

AC Input Voltages: 100-240 VAC
Rated Input Current: 8.5A to 6A
Rated Input Frequency: 50-60 Hz
Rated Output Power: 750W
Rated Output Voltages: +3.3V (25A), +5V (25A), +12V (700W: 58A at 100V-140V, 750W: 62A at 180V-240V), -12V (0.6A), +5Vsb (3A)
Power Consumption: 370 Watts maximum (standard I/O traffic), 465 Watts maximum (heavy I/O traffic)

Cloud-Based Analytics

Cloud-Based Analytics (CBA) is required for Myriad to function, and to enable Quantum to collect data about the Myriad system and environment performance. When CBA is enabled, Myriad telemetric data logs are uploaded to the remote CBA server for analysis. The data collected assists Quantum with early detection and diagnosis of any problems regarding your Myriad system.