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

= The NetApp Cloud Volumes ONTAP Release Notes provide the most up-to-date and accurate

information about the storage limits for different cloud platforms, licenses, and configurations. The

release notes also include details about supported features, known issues, and limitations for each

version of Cloud Volumes ONTAP. Reference = Storage limits - NetApp, Storage limits | NetApp

Documentation, Storage limits in AWS | NetApp Documentation, Storage limits in Azure | NetApp

Documentation

To access a LUN on a FAS 8300 system from a VMware ESXi server through the FC protocol, the

customer must configure the FC service on the SVM that owns the LUN. The FC service enables the

SVM to act as an FC target and communicate with the FC initiators on the host. Without the FC

service, the LUN will not be visible to the host, even if the LUN is mapped to an igroup and the FC

LIFs are up. The exhibit shows that the FC service is not configured on the SVM, as the output of the

command vserver fcp initiator show -vserver SVM1 is empty. Therefore, the reason for the problem

is that the FC service has not been configured on the SVM. Reference = Configure an SVM for

FC, Create an FC protocol service, Single IQN iSCSI session with ESXi on ONTAP when igroup has two

IQNs

The error message indicates that the access is denied for user ‘anonymous user’ (Vserver 50), from

client IP 10.10.10.10 accessing resource ‘/offload-target’. This means that the application is not

providing a valid user name or access key to authenticate with the ONTAP S3 server. According to the

NetApp documentation1, ONTAP S3 server supports both v2 and v4 signatures, but v2 signatures are

deprecated and not recommended. Therefore, the application should use v4 signatures to access the

ONTAP S3 bucket. Additionally, the application should specify the bucket name in the host name, not

in the resource path, as shown in the following example2:

https://bucket-name.s3-server-name.com/object-name

Reference = 1 ONTAP S3 Server Overview - NetApp Documentation 2 Accessing an ONTAP S3 bucket -

NetApp Documentation

Here is my reasoning:

The system node hardware unified-connect show command displays the status and configuration of

the Unified Connect ports on a node1. This command can help you identify if the ports are

configured correctly and if they have any errors or faults.

The ports 0e and 0f on the AFF A300 are 10GbE ports that support both Ethernet and Fibre Channel

over Ethernet (FCoE) protocols2. These ports are part of the Unified Connect feature, which enables

you to use the same physical port for different protocols without requiring additional hardware3.

If the ports are offline, it could indicate a problem with the port configuration, the cable connection,

the switch configuration, or the protocol settings. The system node hardware unified-connect

show command can help you troubleshoot these issues by showing you the port mode, speed,

duplex, state, and error count1.

The other commands in the options are not as helpful for troubleshooting the port issue, because

they show different information that is not related to the Unified Connect feature or the port status.

For example:

The vserver fcp wwpn-alias show command displays the World Wide Port Name (WWPN) aliases for

the Fibre Channel Protocol (FCP) logical interfaces (LIFs) on a Vserver4. This command can help you

manage the FCP LIFs, but it does not show the status of the physical ports or the Unified Connect

feature.

The storage port show command displays the status and configuration of the storage ports on a

node5. This command can help you manage the storage ports, but it does not show the status of the

Unified Connect ports or the FCoE protocol.

The vserver fcp interface show command displays the status and configuration of the FCP LIFs on a

Vserver6. This command can help you manage the FCP LIFs, but it does not show the status of the

physical ports or the Unified Connect feature.

Here are some

that might help you:

1: system node hardware unified-connect show - NetApp 2: AFF A300 system installation -

NetApp 3: Unified Connect - NetApp 4: vserver fcp wwpn-alias show - NetApp 5: storage port show -

NetApp 6: vserver fcp interface show - NetApp

= CPU utilization in ONTAP is not a linear measure of the system load, nor can it be used alone as a

measure of the overall system utilization. ONTAP uses a Coarse Symmetric Multiprocessing (CSMP)

design which partitions system functions into logical processing domains, each with its own

scheduling rules and resource availability. Therefore, a high CPU utilization does not necessarily

indicate a performance problem, unless it is accompanied by other contributing factors such as high

latency, low throughput, or high queue depth. ONTAP has several mechanisms to optimize CPU

usage and balance the workload across the cores, such as WAFL parallelization, exempt processing,

and CPU pinning. The CPU utilization reported by the sysstat command is an average across all cores

and domains, and does not reflect the actual CPU activity or availability for each domain. Therefore,

the CPU is not a first-order monitoring metric for ONTAP, and other metrics such as latency,

throughput, and queue depth should be considered first. Reference = What is CPU utilization in Data

ONTAP: Scheduling and Monitoring?, How to measure CPU utilization, What are CPU as a compute

resource and the CPU domains in ONTAP 9?, Monitoring CPU utilization before ONTAP upgrade

= AutoSupport is enabled by default for Cloud Manager and ONTAP Cloud systems. It proactively

monitors the health of your systems and sends messages to NetApp technical support. To enable

AutoSupport, you must provide your NetApp Support site credentials to Cloud Manager. If your

credentials are incorrect or expired, Cloud Manager will not be able to send AutoSupport messages

to NetApp. Therefore, the solution for this issue is to verify that your NetApp Support site credentials

are correctly added to Cloud Manager. Reference = Troubleshooting Cloud Manager and ONTAP

Cloud, Set up AutoSupport

According to the NetApp Knowledge Base, packet traces are stored in the /etc/log/packet_traces

directory of the node hosting the LIF. This applies to ONTAP 9.10 and above systems. For ONTAP 9.2

to 9.9 systems, the procedure to capture packet traces is similar, but the command syntax is slightly

different. For ONTAP pre-9.2 systems, the procedure is different and requires the use of the tcpdump

command. Reference = How to capture packet traces on ONTAP 9.10+ systems, How to capture

packet traces (tcpdump) on ONTAP 9.2 to 9.9 systems, How to capture packet traces in ONTAP pre-

9.2

= When a SnapMirror resync operation is performed, the destination volume is reverted to the most

recent common snapshot copy with the source volume. Any newer snapshot copies that exist on the

destination volume are deleted automatically, unless they are marked as busy or locked. This is done

to ensure that the destination volume is consistent with the source volume and to avoid data loss or

corruption. Therefore, if the customer complains about missing snapshot copies on the destination

volume after a SnapMirror resync, the most likely cause is that those snapshot copies were newer

than the common snapshot that was chosen for resync and were removed automatically by the

system. Reference = SnapMirror resync operation, SnapMirror resync or update failed No Snapshot

copies found on volume, Even though there is common snapshot, SnapMirror resync fails with error:

No common snapshot copy found between source and destination volume

= The FIFO message before NMI is useful for investigating the issue because it shows the state of the

system before the non-maskable interrupt (NMI) was triggered by the L2 watchdog timeout. The

FIFO message contains information about the CPU registers, the stack pointer, the instruction

pointer, and the last executed instructions. This can help identify the cause of the system hang or

deadlock that led to the watchdog reset. The other FIFO messages are not useful because they show

the state of the system after the reset or shutdown, which may not reflect the original

problem. Reference = https://kb.netapp.com/onprem/ontap/hardware/Handling_L2_Watchdog_Res

ets_on_the_FAS8200_and_AFF_A300_platforms

https://docs.netapp.com/us-en/ontap-metrocluster/install-ip/task_sw_config_restore_defaults.html