NetApp certified support engineer - ONTAP specialist NS0-593 Exam Questions

Answer : B

The AUSO feature is a MetroCluster functionality that enables an automatic switchover to the surviving site in the event of a disaster that affects one site1.

The AUSO feature is only available in MetroCluster FC configurations, which use Fibre Channel (FC) switches and FC-to-SAS bridges to connect the nodes and disk shelves across sites1.

MetroCluster IP configurations, which use Ethernet switches and network adapters to connect the nodes and disk shelves across sites, do not support the AUSO feature2.

Instead, MetroCluster IP configurations use the ONTAP Mediator service, which is a software component that monitors the health and connectivity of the MetroCluster nodes and initiates a Mediator-assisted unplanned switchover when a disaster occurs3.

The Mediator-assisted unplanned switchover is similar to the AUSO feature, but it requires the ONTAP Mediator service to be configured and running on a separate host3.

Therefore, you would tell your customer that the AUSO feature is not available in MetroCluster IP installations by design, and that they need to use the ONTAP Mediator service instead for disaster recovery.Reference:

1: Understanding MetroCluster data protection and disaster recovery, ONTAP MetroCluster Documentation Center

2: Differences among the ONTAP MetroCluster configurations, ONTAP MetroCluster Documentation Center

3: Configure the ONTAP Mediator service from a MetroCluster IP configuration, ONTAP MetroCluster Documentation Center

Answer : D

The mailbox disks are the first two disks of the root aggregate on each node of an HA pair. They store the HA state information and the panic dump files.The mailbox disks are used for communication between the HA partners and for takeover and giveback operations1

The mailbox destroy local command is used to destroy the mailbox disks on the local node. This command is only available in maintenance mode and should be used with extreme caution.The command is intended for situations where the mailbox disks are corrupted or inaccessible and need to be recreated2

If the mailbox destroy local command is executed on a node that is in takeover mode, the node will panic with the message ''Permanent errors on all HA mailbox disks''.This is because the node will lose the HA state information and the panic dump files of the partner node, and will not be able to communicate with the partner node or perform a giveback operation3

Therefore, if the motherboard of Node-01 is being replaced, and a takeover was initiated from Node-02, and Node-02 panics showing the string ''Permanent errors on all HA mailbox disks'', the most likely cause is that the mailbox destroy local command was executed on Node-02 while in maintenance mode.This is a serious error that can result in data loss and system downtime4

1: ONTAP 9 - High-Availability Configuration Guide - The Open Group2: ONTAP 9 - Commands: Manual Page Reference - The Open Group3: How to troubleshoot a ''Permanent errors on all HA mailbox disks'' panic - NetApp Knowledge Base4: One node PANIC : Permanent errors on all HA mailbox disks - NetApp Knowledge Base

Answer : D

FabricPool is an ONTAP feature that enables tiering of cold data from SSD aggregates to low-cost object storage, either on-premises or in the cloud1.FabricPool requires a license to be installed on the cluster, and the license type depends on the cloud tier being used2.In this scenario, the cloud tier is another ONTAP cluster (FAS8300), which is not supported by the new Cloud Tiering license that is used for most FabricPool configurations3.Therefore, the old FabricPool license that is retained for dark sites or MetroCluster systems using FabricPool Mirror must be used3.The FabricPool license defines the amount of capacity that can be tiered to the cloud tier, and it can be increased by add-on orders4.Reference:

1: FabricPool overview5

2: FabricPool requirements6

3: Install a FabricPool license2

4: ONTAP FabricPool (FP) Licensing Overview1

Answer : B

The error message indicates that the ONTAP Select Deploy VM cannot connect to the vCenter server due to a network issue1.

One possible cause of this issue is that the IP address of the ONTAP Select Deploy VM is conflicting with another device on the same network2.

To correct this problem, you need to change the IP address of the ONTAP Select Deploy VM to a unique and valid address that can reach the vCenter server2.

You can change the IP address of the ONTAP Select Deploy VM by using the Deploy web interface or the Deploy CLI2.

After changing the IP address, you need to restart the Deploy services and re-add the vCenter server to the inventory2.Reference:

1: Credential authentication failed with: HostConnectionFailed, NetApp Knowledge Base

2: Changing the IP address of the Deploy VM, ONTAP Select 9 Documentation Center

Answer : B, D

To enable DDNS updates to work, two actions should be performed:

Remove the NFS protocol from the cifs_01 data LIF.This is because DDNS updates are only supported for LIFs that have only one data protocol enabled1. The cifs_01 LIF has both NFS and CIFS protocols enabled, which prevents it from registering its DNS record dynamically. By removing the NFS protocol from the cifs_01 LIF, it will become eligible for DDNS updates.

Enable the -is-enabled parameter for the SVM DDNS services.This is because the -is-enabled parameter controls whether the SVM sends DDNS updates to the DNS servers2. The exhibit shows that the -is-enabled parameter is set to false for the svm1 SVM, which means that it does not send any DDNS updates. By enabling the -is-enabled parameter, the SVM will start sending DDNS updates for its eligible LIFs.Reference:

1: Configure dynamic DNS services3

2: Manage DNS/DDNS services with System Manager4

Answer : B

SnapMirror is a data replication technology that allows efficient and flexible data protection and disaster recovery for NetApp ONTAP storage systems1

SnapMirror transfers data between source and destination volumes using a network connection.SnapMirror can use storage efficiency features such as compression and deduplication to reduce the amount of data transferred and stored1

SnapMirror transfers are scheduled and controlled by policies that define the frequency, retention, and priority of the transfers.SnapMirror policies can also specify the network bandwidth limit for the transfers2

SnapMirror transfers are considered background tasks that run in the absence of user workload.SnapMirror transfers can consume CPU and disk resources on both source and destination systems, depending on the amount and type of data being replicated3

SnapMirror transfers can throttle up or down depending on the availability of system resources and network bandwidth. SnapMirror transfers will throttle up when there is no user workload, and throttle down when there is user workload.This is to ensure that SnapMirror transfers do not impact the performance of user operations3

Therefore, if a customer is concerned with high CPU and disk utilization on their SnapMirror destination system, the best answer is to explain that background tasks such as SnapMirror throttle up in the absence of user workload.This is normal and expected behavior, and it does not indicate a problem with the system3

1: ONTAP 9 Data Protection - SnapMirror - The Open Group2: ONTAP 9 Data Protection - SnapMirror Policies - The Open Group3: SnapMirror storage efficiency configurations and behavior - Resolution Guide - NetApp Knowledge Base

Answer : C

A LIF (Logical Interface) is a logical entity that represents a network connection point on a node1.

A VIP LIF (Virtual IP LIF) is a LIF that can fail over across subnets within an IPspace2.

BGP (Border Gateway Protocol) is a routing protocol that enables VIP LIFs to advertise their IP addresses to external routers and to update the routing tables when a failover occurs3.

To connect a NetApp ONTAP cluster to a complex network that requires LIFs to fail over across subnets, you need to configure VIP LIFs using BGP on the cluster and on the external routers3.

This way, you can ensure that the network traffic is routed to the optimal node and port for each VIP LIF, and that the network connectivity is maintained in the event of a node or port failure3.Reference:

1: Logical Interfaces, ONTAP 9 Documentation Center

2: VIP LIFs, ONTAP 9 Documentation Center

3: Configuring BGP on a cluster, ONTAP 9 Documentation Center