New AFF/FAS cluster commissioning · existing-data recovery is a different procedure
Example values: cluster name LAB-ONTAP, cluster management 192.0.2.20, node management 192.0.2.21 and .22. Replace these documentation IPs with your approved addresses.
About the command and output examples
Names, addresses and results are illustrative. Commands have not been executed against a live storage system or SAN switch for this publication. Confirm syntax and compatibility for your release, then rehearse in an approved lab. Existing-data recovery and destructive changes need an environment-specific plan. Read the editorial standards.
01Collect prerequisites
- Verify supported ONTAP release, platform, licensing, cluster switch topology, node cabling, and management reachability. Record gateway, subnet mask, DNS, NTP, and administrator credential handling.
- Reserve unique cluster and node management addresses. Do not use client data addresses for cluster interconnect. Arrange access to each serial console before starting.
Two reachable consoles and an approved addressing worksheet.
02Create and join
- Power on the first node and use System Manager discovery or the cluster setup wizard to create the cluster. Enter cluster name, management address, and administrator details.
- Join the second node to the existing cluster using the platform setup flow. Confirm both nodes appear in the cluster and their management interfaces are reachable.
- Set DNS and time synchronization; configure AutoSupport and management access according to policy. Do not enable client protocols until the cluster is healthy.
cluster show
network interface show
storage failover show
system health alert show03Prove readiness
- Check cluster quorum and node eligibility. Check HA takeover readiness, management LIF reachability from the admin network, DNS resolution, and synchronized time.
- Document the configuration and collect a baseline before provisioning SVMs. If one node is missing, investigate interconnect cabling and cluster ports before retrying setup.
All planned nodes healthy; HA ready; no critical health alert; management reachable from the intended subnet.
04Commissioning worksheet and readiness gates
| Object | Example | Acceptance |
|---|---|---|
| Cluster management | LAB-ONTAP / 192.0.2.20 | Reachable from the approved administration network |
| Node management | 192.0.2.21 and 192.0.2.22 | Each node is independently reachable |
| Cluster interconnect | Platform-specific non-client network | Planned cluster links and node eligibility are healthy |
| DNS / NTP | Approved organization services | Resolution and time are correct before AD/Kerberos use |
| AutoSupport / support access | Approved support policy | Configuration and delivery check are recorded |
- Open both consoles and capture the initial setup state. Distinguish a new/uninitialized node from a node that belongs to a cluster or contains data. A commissioning wizard is not a recovery procedure for existing storage.
- Create the cluster on the first node and join the second using the matching release procedure. Validate the cluster and management networks independently; one can work while the other is miswired.
- After DNS, NTP and management controls are set, access the cluster from a second administration session before closing the console. Keep a documented authorized recovery access path.
05Acceptance evidence before the first production SVM
Example diagnosis: node management .22 responds, but node 2 is not eligible in the intended cluster. Retrying SVM creation does not fix membership. Inspect the cluster interconnect and join state first, retaining the exact error. Conversely, a healthy two-node cluster with unreachable cluster management points to the administration path, LIF placement or routing.
cluster show
network interface show
storage failover show
cluster time-service ntp server show
system health alert showPlanned membership and HA state are healthy, both node management endpoints and cluster management are usable, and every unresolved alert has an owner before data service begins.
Use the section links to revisit a step, or follow a related guide below.
Official references and further reading
Choose the matching release in the vendor documentation before using a command or design. References open on the publisher’s website; linked material remains with its publisher.