I85PREP
⌘ K
Dell PowerScale Deploy study materials
Dell PowerScale Deploy study resources

Dell PowerScale Deploy: Cluster Installation and Configuration

Dell PowerScale Deploy · Work through your exam, one topic at a time.

All guide sections

Cluster Installation and Configuration

Domain overview

Cluster Installation and Configuration tests the sequence from racking nodes to a working, licensed cluster with authentication and client access. Expect questions on initial setup, node join, network configuration, and verification.

Installation sequence

  • Rack and cable nodes, connect power, and attach serial consoles. Confirm back-end links before applying power.
  • Install or verify the OneFS version on each node; all nodes must run compatible software before they can form a cluster.
  • Run the initial setup workflow on the first node to create the cluster, set the admin password, and configure basic network settings.
  • Add remaining nodes, verify that they join, and confirm cluster health before configuring clients.

Configuration areas

  • Cluster identity: name, contact, time zone, NTP, and DNS. NTP is not optional; Kerberos and AD authentication depend on correct time.
  • Networking: groupnet, subnet, IP pool, SmartConnect zone, VLANs, and link aggregation.
  • Authentication: join Active Directory or configure LDAP/NIS/local providers; set the system access zone and any additional access zones.
  • Protocols: create SMB shares and NFS exports only after authentication and networking are verified.
  • Licensing: activate base and optional licenses before enabling dependent features.

Verification

Use cluster status and health checks to confirm nodes, drives, and network links are healthy. Check that each node has the expected interfaces, that the SmartConnect name resolves, and that a test client can authenticate and read/write.

Worked example

A four-node cluster is built, but node 4 never appears in cluster status. The admin can ping node 4 on the management network. Check the back-end cabling and switch ports first, then confirm the OneFS version matches the other nodes, then review the serial console for join errors. Client network reachability does not prove back-end membership; the cluster uses the back-end network for node discovery and data.

Traps

  • Skipping NTP and then blaming AD for authentication failures.
  • Applying an optional license before the base configuration is stable.
  • Testing only management IP reachability instead of back-end membership.
  • Creating shares before DNS, authentication, and access zones are correct.