Example: a new two-controller AFF HA pair with one external shelf and two management switches. This is a planning example, not a port map; the port map must come from the exact system model guide.
Commands and screens can differ by release and platform. Replace example names and documentation IP addresses. Check prerequisites, impact, current health and rollback with your change owner.
1. Prepare a model-specific worksheet
- Record the controller model, serial numbers, shelf and module type, number of shelves, ONTAP release, rail kit, and switch models. Download the exact platform installation guide and Hardware Universe entry.
- Reserve rack units, verify rack depth, weight, cooling, grounding, redundant PDUs, lifting assistance, power connectors, and console access. Label intended rack positions before equipment arrives.
- Create a port-to-port matrix for controller A and B: cluster/HA, management, NAS/SAN host, storage shelf, and switch endpoint. Plan separate power feeds. Confirm transceivers and cable lengths.
Acceptance evidence: approved rack elevation, port map, IP plan, power plan, and inventory.
2. Rack and cable
- Install shelves and controllers with the supplied rails and lifting procedure. Secure chassis and cable-management arms; keep ventilation and service clearance.
- Cable cluster/HA and management using the platform-specific switched or switchless diagram. Cable host networks and shelves with the specified module ports and multipath pattern. Label both ends and have another person trace every cable against the worksheet.
- Do not infer port numbers from a different AFF or FAS model. Connector orientation and shelf module port names can vary.
Confirm both controllers reach their planned switches and each required shelf path is present in the approved diagram.
3. Power on and accept
- Follow the platform guide for shelf IDs and power-on sequence. Assign unique shelf IDs where required, allow any required power cycle, then bring up controllers with a console connected.
- Record boot messages and hardware faults. Complete cluster setup only after the hardware is discovered as expected.
- Verify nodes, HA, ports, shelves, and system health; record serials, shelf IDs, ONTAP and firmware versions, management addresses, and any exceptions in the handover.
cluster show
storage failover show
network port show
system health alert showBoth nodes healthy and eligible; HA ready; expected ports and shelves present; no unresolved hardware alert.
If validation fails
- If a shelf is missing, stop cluster setup. Compare the actual shelf module and controller ports to the model diagram, then check cable seating and link indicators. Do not swap live storage paths without an approved maintenance procedure.
- If a controller will not boot, capture console output, power supply indicators and serial numbers. Confirm independent power feeds and follow the platform fault guide before reseating components.
- If both nodes boot but HA is not ready, inspect cluster/HA cabling, switch configuration and health alerts. Preserve the original cable map for support escalation.
Re-run the original validation and record the observed result, exact error, time, and corrective action.