Case description: FAS2520 / Data ONTAP 7-Mode: aggr0 double degraded, replacement drives detected as SAS 15000 and not accepted as matching spares, maintenance disk stuck in testing. Current problem aggr0 is currently double degraded. The RAID group shows two FAILED data members. We have available spare disks, but the system is not using them for rebuild. A maintenance disk (0a.00.3) remains in testing status. Observed behavior From aggr status -r: Aggregate aggr0 (online, raid_dp, degraded) (block checksums) RAID group /aggr0/plex0/rg0 (double degraded, block checksums) Two data positions in the RAID group show as FAILED From aggr status -s: Current spare disks are: 0a.00.1 → SAS 15000 0a.00.8 → SAS 15000 (at one point shown as not zeroed) From aggr status -r: Existing RAID group members are shown as FSAS 7200 Maintenance disks section shows: 0a.00.3 → testing, FSAS 7200 From disk show -v: 0a.00.3 shows OWNER = FAILED Drive identification inconsistency From storage show disk -T -x: 0a.00.1 and 0a.00.8 are identified as: Model = X477_SMBPE04TA07 Rev = NA00 Type = SAS Most other data disks in the shelf are identified as: Model = X477_SMEGX04TA07 Rev = NA03 Type = FSAS We also replaced the disk in slot 0a.00.8 with another brand-new replacement drive, but the newly inserted disk was still detected as SAS / RPM 15000. What we already checked raid.disktype.enable = off raid.rpm.ata.enable = off Broken disks (empty) from aggr status -f Current spare disks are owned by the controller and use block checksum Another new replacement drive inserted into 0a.00.8 still shows as SAS 15000 Our concern It appears that the available replacement drives are not being accepted as valid matching spares for aggr0, possibly because the RAID group members are shown as FSAS 7200 while the replacement drives are detected as SAS 15000. We need help with Please confirm whether the replacement drives/FRUs are correct for this platform and RAID group. Please confirm whether there is a disk qualification / drive firmware / recognition issue causing the system to identify replacement drives as SAS instead of FSAS. Please advise the supported recovery procedure for aggr0 in the current double degraded state. Please advise how to handle maintenance disk 0a.00.3, which remains in testing and also appears as OWNER = FAILED. Commands / outputs available We can provide the outputs of: aggr status -r aggr status -s aggr status -f storage show disk -T -x storage show disk -x sysconfig -d disk show -v options raid.disktype.enable options raid.rpm.ata.enable Please advise next steps. Best regards ... View more

Recently I met that FAS2520 HDD failed issue (0a.00.1 and 0a.00.8 failed, 0a.00.3 in maintenance testing) and no available spare HDD. I order 3 new HDDs with same PN, and set spares to new 0a.00.1 and 0a.00.8 successfully. But system did not auto rebuilding. And detect 0a.00.1 and 0a.00.8 as SAS with RPM 15000 while others are FSAS with RPM7200. What is the best next plan? Thanks in advance for your advice. ... View more

Good day, I'm working as a consultant and my customer often asks me about creating restricted roles. It would be useful to have a full list of exixting cmddirnames, at lest to verify AI suggestions vs allucinations 😀 I know that it could be verified by using the cli, issuing incomplete commands and showing suggestions with TAB key. But the customer does not allow me to use the CLI with a role that can create other roles 🙄 Also a "ontap emulator" could be great. Any suggestions are welcome. Thanks in advance.   Alessandro ... View more

FAS2750 device, system ONTAP9.16. When controller A node 1 took over controller B node 2, I started the system of node 2 and entered the menu mode to select the fourth option to clear the configuration. During the restart process, there was a waiting for giveback. Then I returned the configuration in node 1 and entered a brand new node system (node 3). In node 1, I recreated the cluster and allowed node 3 to rejoin the cluster. The configuration of cluster IP, node IP, interface lif, vserver, etc. before node 2 is still in place. I want to remove the failed node 2, but the prerequisite is to delete or migrate the vserver lif and other configurations related to node 2. However, I tried modifying the cluster IP, node IP, interface lif, and so on, which showed Error: command failed: RPC: Could't make connection [from mgwd on node] "FAS2750-03" (VSID: -1) to vifmgr at 169.254.157.6]， I use commands FAS2750::*> cluster remove-node -node FAS2750-02 -force true Warning: This command will forcibly remove node "FAS2750-02" from the cluster. You must remove the failover partner as well. This will permanently remove from the cluster volumes that remain on that node and logical interfaces with that node as the home-node. Contact support for additional guidance. Do you want to continue? {y|n}: y [Job 1064] Cleaning cluster database Error: command failed: [Job 1064] Job failed: Failed to delete SAN configuration for lif with id 1032 from its current node (FAS2750-02):No nodes are available to process the command. Verify that all nodes are healthy using the "cluster show" command, then try the command again. And the system alarm displays: FAS2750::*> system he al show Node: FAS2750-01 Alert ID: ClusterSwitchlessConfig_Alert Resource: FAS2750 Severity: Major Indication Time: Wed May 13 16:39:20 2026 Suppress: false Acknowledge: false Probable Cause: No cluster switch is detected and the switchless option is not enabled. Possible Effect: Communication problems and cluster connectivity issues occur. Corrective Actions: 1) If the cluster network is configured as a two-node switchless cluster (TNSC), enable switchless detection by using the "network options detect-switchless-cluster modify -enabled true" command. No further action is required. 2) If the cluster network is configured with cluster switches, the nodes fail to detect the switches. Ensure that the network interfaces on the cluster switches connected to the node cluster ports are enabled on both sides. If the errors are corrected, stop. No further action is required. Otherwise, continue to step 3. 3) Check the physical connections between the nodes and the cluster switches. Replace network cables with known-good cables. If the errors are corrected, stop. No further action is required. Otherwise, continue to step 4. 4) Ensure that either CDP (for Cisco switches) or ISDP (for NetApp CN1610 and Broadcom BES-53248 switches) is enabled on the cluster switches. FAS2750::*> network options detect-switchless-cluster show Enable Switchless Cluster Detection: true   Big shots, please help me take a look and answer my questions. Thank you very much. ... View more