Cloud Insights brings operational simplicity to platform engineering teams managing Kubernetes, so we're excited to introduce our latest addition to Cloud Insights, the Workload Health Page. This gives an at-a-glance view of your entire platform, including health, risks, and potential issues, and makes operating and troubleshooting your Kubernetes environment simpler and faster than ever before. Where problems are identified, you can zoom into every deployment and configuration change, helping you pinpoint issues and implement best practices promptly. 

Our goal with the Workload Health Page is to empower you in managing your Kubernetes environments. It allows for swift identification of issues and immediate application of best practices and enhances the performance of your Kubernetes operations overall.  

By integrating this tool into your workflow, you gain full visibility and control over your Kubernetes operations and underlying computing and storage, eliminating blind spots, which results in increased system productivity and reduced downtime. 

The Workload Health Page provides a simplified landing zone for Kubernetes platform administrators to make the most of Cloud Insights’ existing capabilities, such as tracking every deployment and configuration change and correlating them with incidents and alerts to quickly resolve problems. Plus, the platform provides advanced log ingest capabilities to help you understand what’s going on in your environment, in turn alerting you when there are issues that need your attention. Cloud Insights by NetApp delivers valuable insights, turning raw data into actionable intelligence for efficient troubleshooting. 

This builds on top of Cloud Insights Workload Map launched earlier this year, which helps identify and tackle issues efficiently by mapping workload dependencies. This performs automated mapping and analysis of traffic sources, data flows, and potential performance limitations in a single, easy-to-understand view. This comprehensive overview allows for a more streamlined management and troubleshooting process, making Cloud Insights stand out as more than just monitoring and metrics for Kubernetes. 

We encourage you to explore the benefits of our Workload Health Page today.  

Experience a seamless Kubernetes management process and enhance your troubleshooting efforts with this advanced tool. Dive into the world of streamlined Kubernetes operations with Cloud Insights by NetApp.  

The future of Kubernetes management and troubleshooting is here, and it is more efficient, simpler, and faster. 

Visit the Cloud Insights page to find out more about Cloud Insights for Kubernetes manageability, infrastructure observability or insider threat detection. If you want to get hands on, it’s easy to get started in your own environment with a free trial. 

In today's fast-paced IT landscape, the task of supervising and scrutinizing a broad spectrum of components, from intricate container architectures and powerful compute to sophisticated storage systems, can appear to be a significant undertaking.

With alert fatigue becoming an increasingly common problem among IT teams, Cloud Insights showcases its stronghold in the field, offering a comprehensive solution to optimize your IT infrastructure by reducing the noise and tracking every change, and providing insights into how changes affect Kubernetes health, availability, and performance.

Comprehensive Understanding of Your IT Infrastructure

NetApp Cloud Insights is a powerful tool that helps you keep an eye on all parts of your IT systems. It provides an in-depth view of computing infrastructure, storage systems, and containerized applications managed through Kubernetes. This all-encompassing visibility allows IT owners to understand how systems are performing and how to optimize them for better efficiency and reliability.

With Cloud Insights, you can track crucial metrics that reflect the health and performance of your systems. These metrics should be well-defined, actionable, informative, and impactful. They should provide valuable and relevant information about the systems being monitored and should be closely tied to the potential issues that could affect your business operations.

Tackling Alert Fatigue

Alert fatigue can be a significant issue in complex IT environments. It occurs when teams are overwhelmed by a flood of alerts, many irrelevant or nonactionable, leading to the potential overlooking of critical alerts. Cloud Insights addresses this by focusing on delivering alerts that truly matter.

Cloud Insights comes equipped out of the box with the ability to set up alerts that are immediately actionable and impactful, allowing teams to focus on significant events that could influence the system's health, availability, and performance.

The process can be customized to match your specific infrastructure and business requirements, ensuring the alerts you receive are timely, relevant, and valuable, including corrective actions.

Setting the appropriate thresholds is a vital part of this strategy, contributing to smoother operations and fewer disruptions. This approach keeps your team's attention on critical issues while reducing unnecessary noise and distractions.

 https://docs.netapp.com/us-en/cloudinsights/task_create_monitor.html

In-Depth Monitoring and Tracking of Changes

Cloud Insights stands out in terms of its ability to track every deployment and configuration change to your IT infrastructure. This tracking allows you to maintain a historical record of changes, aiding in the identification of when a change could have introduced an issue, and ability to revert. This level of traceability can be instrumental in diagnosing problems, minimizing the time spent troubleshooting, and avoiding potential system downtime.

Furthermore, Cloud Insights' unique ability to correlate changes with incidents and alerts allows for faster identification and resolution of issues. This capability not only ensures swift incident response times but also reduces the time spent in the overall troubleshooting process, and data mining across many other tools.

https://docs.netapp.com/us-en/cloudinsights/concept_kubernetes_network_monitoring_and_map.html#dive-deep 

Conclusion

NetApp Cloud Insights offers a comprehensive solution to monitor and optimize your IT infrastructure. By providing in-depth visibility into your infrastructure, enabling the setting of appropriate alert thresholds, and offering meticulous change tracking, it fosters a more streamlined and efficient IT management process.

Free trial is available to check it out in your own environment, and it's easier than you think to get started https://bluexp.netapp.com/cloud-insights

With Cloud Insights, you can ensure that your infrastructure, whether container, compute, storage, or a hybrid, is performing optimally and supporting your business as intended.

I originally had Data Collectors setup in Cloud Insights using cluster admin credentials.  I just followed the steps at https://docs.netapp.com/us-en/cloudinsights/task_add_collector_svm.html#a-note-about-permissions in the "Permissions when adding via Cluster Management IP:"  section and the cmddirs in the role that was created all match and the ssh and ontapi access were granted, but when I switched the credentials in the collector to this new account the collectors fail and I get this when I test the connection "Configuration: Failed to execute test command on device - NetApp ONTAP zapi communication failed: cluster-identity-get failed: Insufficient privileges: user 'csuser' does not have read access to this resource."

Oriole::> security login role show -vserver Oriole -role csrole
           Role          Command/                                      Access
Vserver    Name          Directory                               Query Level
---------- ------------- --------- ----------------------------------- --------
Oriole     csrole        DEFAULT                                       none
                         event catalog                                 all
                         event filter                                  all
                         event notification                            all
                         event notification destination                all
                         network interface                             readonly
                         security certificate                          all
                         version                                       readonly
                         volume                                        readonly
                         volume snapshot       -snapshot cloudsecure_* all
                         vserver                                       readonly
                         vserver fpolicy                               all
12 entries were displayed.

Oriole::> security login show -role csrole

Vserver: Oriole
                                                                 Second
User/Group                 Authentication                 Acct   Authentication
Name           Application Method        Role Name        Locked Method
-------------- ----------- ------------- ---------------- ------ --------------
csuser         ontapi      password      csrole           no     none
csuser         ssh         password      csrole           no     none
2 entries were displayed.

While other storage systems may provide some ransomware protection, they do not provide protection from insider threats. NetApp® storage systems are different. Very different. We are unique in the use of AI/ML to build a “normal access” profile for each user then monitor all user actions to spot any behavioral anomalies that indicate a possible threat (either malicious or accidental), then use automatic policies to stop an attack before it causes even more damage.

Zero trust = zero tolerance

By establishing a zero-trust architecture, you're not solely reliant on a trusted internal network. Many insider threat incidents that compromise your data can be caused by negligent or careless individuals who are already trusted members of the network. The zero-trust approach is key to stepping up your security and protection. This means that whenever unusual behavior is noticed — even from the CEO — quick action to block those users to prevent further data theft or file damage is initiated.

These actions are just the first step. It can also help an enterprise by:

• Inspecting and analyzing all data access activity in real-time to detect malicious behaviors
• Zeroing in on the source of the suspicious behavior and attacks
• Alerting you immediately of a potential attack in progress
• Protecting user data and providing a safe restoration point if there’s a potential breach
• Increasing the speed at which you’re able to identify and recover potential damage
• Decreasing downtime

While ransomware gets most of the attention in compromising critical data, Insider Threats are actually more costly to remediate due to the reported frequency of these incidents. The average ransomware incident remediation cost is around $1.4M, but the Insider Threat cost, while lower on a per-incident basis, is many times higher overall. The average organization remediation cost is approximately $15.4M per year.  Ransomware protection is good, but it is only one part of the equation; NetApp is unique in providing storage systems protection, at the storage level, from insider threats, adding an additional layer of defense for business-critical data.

Cloud Insights – Infrastructure Monitoring | NetApp

Amazon FSx for NetApp ONTAP is a native, fully managed AWS storage service with the full feature set of a NetApp® ONTAP® enterprise storage system—features such as multiprotocol support, NetApp Snapshot™ technology, backup, cloning, and replication. It has become the platform of choice for customers seeking to easily launch, run, and scale applications on AWS.

This blog illustrates the most common challenges and use cases that we see when working with customers who are extending or migrating workloads into AWS. We’ll also present a best practice blueprint for assessing, migrating, and protecting enterprise applications with FSx for ONTAP.

The need for a comprehensive hybrid cloud migration strategy

To continue digital transformation efforts, an ever-increasing number of organizations are modernizing data centers and looking for ways to move workloads to AWS.

Key objectives include:

• Modernizing data centers
• Reducing the number of data centers to manage
• Updating data protection strategies using a 3-2-1 backup strategy
• Using automation for ITOps
• Optimizing cloud costs

Many of these organizations have a mix of enterprise database workloads, general-purpose file shares, and virtualized workloads running on different storage arrays. Some data has been sitting idle in storage for so long that it’s virtually impossible to identify ownership and determine whether the content should be migrated. For all successful migration into AWS, we’ve identified five necessary steps to complete the journey:

• Step 1: Assessment
• Step 2: Discovery
• Step 3: Migration
• Step 4: Protection
• Step 5: Optimization

Step 1: Assessment

Assessment is a critical first step before any AWS migration to ensure that your applications’ requirements for performance, cost, compliance, and security can be delivered. NetApp offers several tools to help you understand your workloads and identify your migration strategy.

Evaluating workloads

NetApp Cloud Insights can identify all the resources to be moved and map them to analogous resources in FSx for ONTAP. Cloud Insights is able to quickly discover almost everything in the environment across data center and cloud boundaries, including virtual machines and storage volumes. Its flexible filters and finders help you search for assets at a granular level based on a wide range of criteria.

If you want your migration to be as cost effective as possible, you must rightsize resources as you migrate them. As shown in Figure 1, Cloud Insights also provides recommendations for the cloud compute and storage resources needed for each workload, including memory, throughput, and I/O requirements.

Figure 1) NetApp Cloud Insights rightsizing storage resources and estimated savings.

Existing NetApp customers can also use the NetApp Active IQ® Digital Advisor tool to identify application usage. In the example in Figures 2 and 3, Active IQ identifies six workloads to migrate to AWS:

• File shares
• Oracle
• SAP
• Microsoft SQL Server
• VMware
• SharePoint

FSx for ONTAP is a prime solution for each of these workloads, because it offers a fully managed ONTAP environment in AWS that can grow (and shrink) automatically as business needs dictate. FSx for ONTAP uses NetApp storage efficiency technologies to control storage costs by optimizing resource utilization and minimizing the amount of data stored. This results in a 3-year return on investment of as much as 61% with investment payback in under 6 months. It also costs, on average, 31% less than self-managed, on-premises storage. Read the full Forrester “Total Economic Impact of Amazon FSx for NetApp ONTAP” study.

Figure 2) In this example, Active IQ Digital Advisor identified six workloads to migrate to AWS.

Figure 3) A deeper dive into the six workloads.

Preparing data for migration

NetApp BlueXP classification service provides discovery, mapping, and classification of unstructured and structured data to give organizations visibility into their entire data estate, whether it’s in AWS, on premises, or both. Using AI-driven analysis, BlueXP classification provides critical information, such as type, size, time attributes, ownership, and user/group permissions. It also analyzes data to identify personal identifiable information (PII), such as emails, credit card numbers, international bank account numbers (IBANs), national IDs, IP addresses, passwords, ethnicities, religious beliefs, and more. It then classifies the PII into sensitivity levels (standard, personal, sensitive-personal) and categories (HR, legal, marketing, sales, finance, and so on).

By using BlueXP classification before migrating to the cloud, you can reduce costs and accelerate your migration by removing duplicate, stale, or unneeded data after cloning the storage volume. The cloned volume is then used as the source for migration. BlueXP classification can also use data context to identify and secure sensitive data.

Figure 4) NetApp BlueXP classification savings opportunities and data classification.

Step 2: Discovery

NetApp BlueXP is the unified control plane for discovering on-premises ONTAP clusters and any existing AWS cloud environments, such as FSx for ONTAP, NetApp Cloud Volumes ONTAP, and Amazon S3. By bringing each of these environments into BlueXP, you can manage volumes and perform advanced data management—such as data replication, backup and recovery, data classification, and data tiering—across your entire hybrid cloud environment without ever leaving the BlueXP canvas.

BlueXP combines data protection through block-level, incremental-forever backup (including replication, mirroring, and synchronization options), with advanced ransomware protection to protect the entire data estate.

Step 3: Migrating to FSx for ONTAP

Migrating from NetApp ONTAP

Rehosting, also known as “lift and shift,” is one of the easiest, fastest, and least-expensive ways to migrate an existing workload into AWS. FSx for ONTAP makes this process easy because of its seamless integration with ONTAP-native workloads and flexible support for block and file workloads. You can lift and shift applications and workloads from on-premises storage into AWS without making significant architecture changes.

You can easily migrate file shares that reside on on-premises ONTAP systems to FSx for ONTAP by using NetApp SnapMirror® technology. Even for volumes with complex directory structures, over 50 million files, and very small file sizes (on the order of kilobytes), SnapMirror employs block-level replication between two ONTAP file systems to make it quick and efficient. During the migration, deduplicated and compressed data remains deduplicated and compressed, which reduces transfer times and the amount of bandwidth required. Snapshot copies on the source ONTAP volumes are preserved when migrated to the destination volumes. Figure 5 shows replication times for initial copy and incremental data changes with SnapMirror by capacity and network bandwidth.

Figure 5) Replication times for initial copy and incremental data changes with SnapMirror by capacity and network bandwidth.

Migrating your on-premises ONTAP file systems to FSx for ONTAP involves the following high-level tasks:

1. Create the destination volume in FSx for ONTAP.
2. Gather source and destination logical interfaces (LIFs).
3. Establish cluster peering between the source and destination file systems.
4. Create a storage virtual machine (SVM) peering relationship.
5. Create the SnapMirror relationship.
6. Maintain an updated destination cluster.
7. Cut over to your FSx for ONTAP file system.

For detailed information about any of these steps, check out the guide to migrating to FSx for ONTAP using SnapMirror in the AWS documentation library.

Figure 6) Typical enterprise workload migration architecture.

Migrating from third-party storage

To migrate data from different storage solutions to FSx for ONTAP, AWS DataSync is the tool for the task. AWS DataSync makes it easy to transfer data between on-premises volume exports/shares and FSx for ONTAP. It requires minimal setup, and you pay only for what you use.

Transferring files from a source to a destination using DataSync involves the following basic steps:

1. Download and deploy the DataSync agent in your on-premises environment and activate it.
2. Create a source and destination location.
3. Create and run the transfer task.

The AWS documentation library has more information about migrating to FSx for ONTAP by using AWS DataSync and a comprehensive AWS DataSync user guide. For techniques to improve planning and maintain sufficient capacity during data migration, check out this blog: Migrating file shares to Amazon FSx for NetApp ONTAP using AWS DataSync.

Step 4: Protecting on-premises and AWS workloads with a 3-2-1 data protection strategy

Although there are multiple approaches that an organization might take for data protection, the 3-2-1 data protection strategy has become an industry standard. With this strategy, you have three copies of data in two formats (for example, NFS and object), one of which is off site from where the backup was taken. A 3-2-1 strategy doesn’t guarantee that the data will never be compromised; rather, it’s sufficient for recovering from virtually any failure.

Figure 7) Typical 3-2-1 data protection architecture.

3-2-1 for on-premises workloads

For workloads that are on premises running on NetApp storage, you can use BlueXP to set up the following relationships:

• Three data copies:
  • One production copy on premises
  • One disaster recovery copy to FSx for ONTAP using SnapMirror from on-premises production storage
  • One archive copy to Amazon S3 using NetApp Cloud Backup from on-premises production storage
• Two formats:
  • ONTAP flash on premises and in the AWS Cloud
  • Object storage in Amazon S3
• One off-site copy:
  • FSx for ONTAP or Amazon S3

Figure  8 )  Dragging on-premises environment onto instances of FSx for ONTAP and Amazon S3 for disaster recovery, backup, and archive purposes.

3-2-1 for workloads in AWS

For the workloads that have migrated to FSx for ONTAP, setting up a 3-2-1 backup strategy is easy when you use native tools in AWS or drag-and-drop tools in NetApp BlueXP:

• Three data copies:
  • One production copy in FSx for ONTAP
  • One disaster recovery copy to another FSx for ONTAP instance in a second region by using SnapMirror cross-region replication
  • One archive copy to Amazon S3 by using AWS Backup from FSx for ONTAP production
• Two formats:
  • ONTAP flash in FSx for ONTAP
  • Object storage in Amazon S3
• One off-site copy:
  •  FSx for ONTAP instances in a second region or Amazon S3

Figure 9) Drag an FSx for ONTAP environment onto another instance of FSx for ONTAP for disaster recovery purposes; apply the automated backup copies by using AWS Backup from the production and disaster recovery FSx for ONTAP instances. The AWS Backup relationships (shown as green lines) do not appear in the BlueXP Canvas and are shown for illustrative purposes only.

You can then use BlueXP to modify mirroring and backup policies to fit your recovery time objective (RTO) and recovery point objective (RPO) requirements.

Figure 10) Setting protection policies.

Figure 11) Setting up data replication schedule policies.

Technical resources are available to help you as you replicate and protect critical applications and workloads such as SAP HANA, Microsoft SQL Server, and VMware, including the following blogs:

• VMware Cloud on AWS Disaster Recovery with Amazon FSx for NetApp ONTAP and SnapMirror
• Protect your SQL Server workloads using NetApp SnapCenter® with Amazon FSx for NetApp ONTAP
• Replicate and clone SAP HANA databases with Amazon FSx for NetApp ONTAP

Step 5: Optimization

After data is migrated and production has cut over to AWS running on FSx for ONTAP, it’s time to monitor and optimize the environment. This is where we recommend using NetApp Cloud Insights to monitor resource utilization. Cloud Insights can monitor things like:

• CPU utilization
• Memory utilization
• Storage utilization
• IOPS
• Throughput

 Cloud Insights provides performance and usage data that helps you rightsize AWS resources so that you aren’t paying for more performance or capacity than you need.

Figure 12) Cloud Insights dashboard showing total compute resources in your AWS environment.

Figure 13) Cloud Insights dashboard showing virtual reclamation and remediation.

When you use FSx for ONTAP, it can automatically tier cold or inactive data from high-performance SSD storage to capacity pool storage to optimize costs and utilization. There are four tiering policies you can choose from:

• Auto: Moves all cold data to the capacity pool tier as determined by the defined cooling period (2 to 183 days).
• Snapshot: Moves only Snapshot data to the capacity pool storage tier.
• All: Marks all user data and Snapshot data as cold.
• None: Keeps all data on the primary storage tier and prevents it from being moved to capacity storage.

Conclusion

Figure 14 shows the BlueXP canvas after you’ve migrated the workloads to FSx for ONTAP and set up a 3-2-1 data protection strategy. It provides a visual representation of the backup, replication, and copy-and-sync relationships between your on-premises and cloud storage environments.

Figure 14) BlueXP canvas depicting the replication and backup relationships between the on-premises and AWS storage environments. The AWS Backup relationships to Amazon S3 (shown as grey lines) do not appear in the BlueXP Canvas and are shown for illustrative purposes only.

In summary, using Amazon FSx for NetApp ONTAP for migration and data protection offers the following benefits:

• Cost savings:
  • Data compression automatically compresses data blocks, reducing the amount of storage space consumed—saving up to 87%, depending on the application.
  • Data deduplication eliminates duplicate data blocks by saving a pointer to the original block, reducing storage usage by as much as 90%, depending on the application.
  • Data compaction automatically combines remaining small chunks of data into single 4KB physical blocks.
  • Thin provisioning allocates storage only when data is being written to a volume rather than allocating ahead of time based on peak demand.
• Recovery point objective as low as 5 minutes.
• Recovery time objective in minutes with automatic failover to FSx for ONTAP.
• Improved cyber resilience with multiple data types—no single point of failure—with 3-2-1 backup.
• Storage-efficient data protection capabilities create additional savings:
  • NetApp Snapshot technology creates point-in-time Snapshot copies that are extremely space efficient, saving only data changes.
  • Using Snapshot technology, NetApp FlexClone® writable data clones are created instantaneously, consuming storage only for changes that are made to the clone.

This blog has presented a high-level overview of migrating workloads into AWS. There are many other specific areas you might need to pay attention to, such as workload separation and billing. If you have any questions, feel free to contact your account team at AWS and NetApp, and we’ll be glad to meet with you.

Learn more about Amazon FSx for NetApp ONTAP.

What is Cold Data?

By default, data that is not accessed for 31 days becomes inactive, which is displayed at the aggregate, cluster, and volume levels. This data is known as inactive (cold) data. The default setting for data to become inactive in ONTAP is after 30 days as defined by the volume tiering policy. This can be changed to suit your business needs. 

Benefits of identifying Cold Storage

NetApp AFF systems offer best-in-class performance with an all-flash architecture with front-end NVMe/FC host connectivity along with back-end NVMe-attached SSDs that help achieve latencies as low as 100µs. But this extra performance comes at higher cost and is best utilized on more frequently accessed (hot) data. By identifying your non accessed (cold) data, you can save data storage space on your high-performance systems by moving the cold data to a lower cost cloud solution such as Amazon S3 object storage. This saves on storage costs and allows you maximize both your high-performance data system space as well as your cold data storage by separating the two. 

Cold Data Dashboard 

The NetApp Cloud Insights Cold Data Dashboard allows you to quickly identify the source and location of cold data so it can be moved to a lower cost storage option. When you first enter the cold data dashboard, you can see immediately how much cold data you have, what type of drives it is on and what volumes the data is on. As you can see here, there is 91.7 TiB of cold data in this environment, 66.3 TiB is residing on high performance SSD drives, 18.8 TiB on HDD drives and 140.7GiB on Virtual drives. 

The Cold Data Volumes report will break down all the volumes with cold data on them, including size cold, disk type, aggregate name, etc.

The Cold Data Dashboard also has a breakdown of how cold the data is. You can not only identify data that is cold but also how infrequently the data is accessed. You can also get a breakdown of your hot and cold data distribution across your data tier. 

Finally, you can get a list of the cold data by cluster as well as broken out by drive types. If you would like you can also export these reports to CSV files. 

The Cold Data Dashboard can quickly help you identify infrequently accessed (cold) data taking up space on your high performance tiers. This will help you move the cold data to a lower cost solution, saving you money on cold storage but also freeing up space on your high performance systems allowing you to efficiently use the storage that you have already purchased instead of overspending your storage budget, maximizing your overall storage environment.  

Hey all,

We have a new Amazon S3 data collector that we can add to your Cloud Insights tenant if you would like early access.

You should be able to reuse your service account details from EC2 discovery in this new collector - no additional rights should be required

Send me a PM with your CI tenant URL if you'd like to have this preview made available,

Thanks

Matt

When creating our company Cloud Insights account, there's been a typo made in the account name.  Who can I contact to have this rectified asap before we start deploying Data Collectors and start using it?

Hi Team,

I would like to know which pattern of MU numbers from 1 to 3 is required to monitor the following systems with CI.

CVO for Azure 10TB (raw size)
Blob Storage 50TB (bucket size) for Fabric Pool

1. 16MU
10TB / 4TB >> 3MU
50TB / 4TB >> 13MU

2. 15MU
60TB / 4TB >> 15MU

3. 3MU
10TB / 4TB >> 3MU
50TB >> Cannot be monitored

best regards

Hi Experts

Currently I am planning to monitor Unity storage with Cloud Insight.

I had successfully deployed AU and trying to create data collector.

At the test connection step, I found error just like image at below.

Compatibility is not a problem.

And prompt from uemcli is successful.

Any suggestion on this?

Hello Team,

my customer is facing the following issue:

what are we doing wrong?

Thanks

I tried serveral times to Install the cloudinsights-au-1.202.0.msi file on a VM.

Always I get the same ERROR.

I also got this error with Version 1.199.

 I do have admin rights.

Does anyone know why I get this error?

Thanks

Horst

What error is this?

Internal error: Cannot update server (Failed to execute the http method for request https://0da44afd-4051-474e-8a1e-5ab17b9f33ed.c02.cloudinsights.netapp.com/compose/originatorUpdate/SANSCREEN/2 500 error is Internal Server Error)

I've been getting pretty generic 401: Not Authorized or Inventory Failed from the ONTAP Data Collector. Sometimes the Test Config succeeds and sometimes it fails to execute test command on device without re-entering the password. I can log directly into OnCommand on the FAS and all the appropriate services on the Data Collector VM appear to be running.

Edit: Just got another 401 error: Invalid login credentials: 401 Unauthorized.