> Essential > Storage > HyperScale X > Reference Architecture > Getting Started > Preparing the Environment > Setting Up the Hardware

Non-Cisco Storage Server Node Configuration

Prior to HyperScale X Reference Architecture software installation each server must meet basic minimum configuration requirements.

The steps outlined below apply only to non-Cisco Reference Design server nodes. Refer to server vendor's documentation for specific steps required to complete this configuration.

Ensure that all steps are completed for all servers that will be part of the HyperScale X Reference Architecture Storage Pool.

1.

Boot Drive

Except on N4 nodes, create a RAID1 volume using the two smaller SSD or M.2 drives assigned for the Operating System(OS).

Set BIOS to boot from RAID1 volume.

Configure the server to boot to UEFI only

Disable Secure Boot

2.

Metadata Drive -NVMe / SSD

Dedicated metadata flash drives require no further configuration.

Commvault HyperScale ISO will detect and format drive during initial imaging process.

3.

Storage Pool Drives

Storage Pool Large Form Factor (LFF) should have no RAID and no special configuration.

Commvault HyperScale ISO will detect and format drives during initial imaging process.

Hardware vendors each have unique label naming convention for storage pool drives.

Ensure all LFF drives are labeled as one of the following depending on vendor:

  • JBOD

  • Pass through

  • Non-RAID

  • Any other vendor specific label for unformatted drives without RAID

4.

Networking and Switch Configuration

Create a minimum of two VLAN:

  • VLAN 1 = Data protection network for public interface(s)

  • VLAN 2 = Storage pool network for private interface(s)

    Ensure all server network ports are connected to 10Gb (or faster) ports on network switches.

    If multiple VLAN are required for data protection, offsite copies, etc., ensure all VLANs are configured on switches.

    If multiple network cards are being used, ensure sufficient number of ports are available on switches.

    Total number of ethernet ports required will depend on number of client VLAN's used and whether tagged VLAN's are supported in the environment.

    If network bonding is being used, allow for 2x ports per VLAN.

Loading...