Sizer 6.0 demos

Cluster Templates-16Jan2023

 

Cluster Template: 

Multi Cloud solutions:

Workflow Redesign:

 

Expert Library:

Collector 4.1

Nutanix Collector 4.1 release is focused on the stability of the data collection, enhancements & bug fixes. Below is a summary of the changes. 

ENHANCEMENTS

Following are the feature enhancements made in this release:

  • ONTAP CIFS Shares

Collector can now identify the storage associated with CIFS Share Home Directories

“Search Path” column is added for CIFS shares configured as home directories, this helps in mapping Volume associated with Home Directories

  • Added Support to report Storage associated via Volume Groups

VolumeGroups sheet now reports all the volume groups that are associated with the discovered VMs – 

vDisk sheet now reports the vDisks that are part of Volume Group. Additional columns under vDisk are – Volume Group Name, Volume Group Disk, Volume Group Shared, Disk UUID, Volume Group UUID

vmList sheet now reports if the VM has Volume Groups attached. Additional columns under vmList are – Volume Group Attached, Volume Group Capacity (MiB) & Volume Group Consumed (MiB)

  • Added support to gather multiple NICs associated with a VM via Prism Element

If a VM supports multiple Network Interface Cards (NICs), the Collector output exported as an XLSX shows all the supported NICs in the vNetwork tab.

COLLECTOR PORTAL ENHANCEMENTS

The below enhancements are available in Collector Portal as part of his release

  • Collector Portal now supports a simple 1-click option to export NetApp ONTAP projects to Size Nutanix Files

Export to Sizer is supported for Collections gathered via Collector 4.1 and later versions

Export to XLSX is supported for Collections irrespective of Collector version

  • When exporting data to Sizer, the “Provisioned Capacity” is the default storage selection

Users are free to switch to “Consumed Capacity”

Defaulting to “Provisioned Capacity” is applied for both compute based workloads and Netapp ONTAP capacity workloads

  • Optimized the process of fetching VM information when dealing with a large number (1K+) of VMs
  • Improved the histogram chart under the VMs Summary tab by ignoring the powered OFF VMs when showing the distribution of VMs by CPU utilization. 
  • Collector provides a specific error message and suggests actions when the user is not registered on the Sizer portal and tries to export Collector Project to Sizer. 

RESOLVED ISSUES

The following issues are resolved in this release:

  • Resolved an issue where the Collector Portal was unable to generate an XLSX file when NetApp ONTAP Volume did not report Consumed Capacity & Snapshot Reserved Capacity.
  • Significantly improved the time taken to gather information via Prism when Collector is unable to gather Guest OS information.
  • Resolved an issue with Data Collection when gathering data via Prism due to the failure of Prism APIs. 
  • Resolved the cluster connection issue when trying to gather data via the Prism version AOS 5.15.4
  • Data collection completes successfully when clusters intermittently fail to report performance data.  
  • Resolved an issue in collecting the vNetwork data for AOS 5.20.2.1 (AHV – 20201105.2244) and higher versions.
  • Resolved the data center name identified by the Collector for the Prism Element clusters.

RESOURCES

Short Demo link: Collector ONTAP Export to Sizer

CALL TO ACTION

Simplify your requirement gathering by downloading Collector

Download Collector via Collector Login Page

Public URL: Collector Download Link for Prospects

MyNutanix URL: Collector Download Link for MyNutanix Users 

Report issues in Collector via this Google form

Thank you,

Team Nutanix Collector

Nutanix Validated Design (NVD) – On-Prem

Nutanix Validated Design – On-Prem  :

The

Nutanix delivers the Hybrid Cloud Validated Design – On Premises, based on the Hybrid Cloud Reference Architecture, as a bundled solution for general server virtualization that includes hardware, software, and services to accelerate and simplify the deployment and implementation process. This Validated Design features a full-stack solution for hybrid cloud deployments that integrates multiple products including AOS, AHV, Prism Pro, Calm, Flow, Leap, Mine, and HYCU.The Hybrid Cloud Validated Design – On Premises sizer reference scenarios have the following features:

 

  • A baseline configuration for each Availability Zone is comprised of three clusters:
    • Management – 4-node cluster based on NX-1175S for Prism Central, Active Directory, IPAM, Load Balancing, SYSLOG, and any other management services.
    • Workload – 4-16 nodes of NX-3170-G8 for general purpose server virtualization workloads.
    • Backup – 4-node cluster of NX-8155-G8 for Mine/Hycu

 

A dedicated management cluster in each Availability Zone provides increased availability, security, operations, and performance. The workload cluster has a defined maximum size of 16 nodes, which provides a reasonable maintenance window for rolling firmware and software upgrades. Smaller workload clusters can be deployed, but the maximum size should not exceed 16 nodes.

 

  •  NVD Defines standard VM “t-shirt” sizes for deployment via Calm:

 

Small Medium Large
1 vCPU 2 vCPU 4 vCPU
8 GB RAM 16 GB RAM 32GB RAM
50GB SSD 100GB SSD 200GB SSD
Max 124 VMs/Node Max 92 VMs/Node Max 46 VMs/Node

 

  • When using the defined VM sizes, the per-workload cluster maximums are:

 

Small VMs Medium VMs Large VMs
Maximum running VMs per workload cluster building block 1,860 1,380 690
Maximum deployed VMs per workload cluster building block to allow for disaster recovery capacity 930 690 345

 

  • Due to quoting limitations, a single Availability Zone has two sizer scenarios: Management + Workload cluster, and Backup Cluster. Note that the Hycu software license is not included, and must be purchased separately via other channels. 
  • Services SKUs are not included in the Sizer reference scenarios. Review the BOM in the NVD appendix for the complete list of Services SKUs which should be included.
  • For a full Disaster Recovery solution, two AZs should be quoted which mirror each other. The design should call for running each workload cluster in the AZ at less than 50% capacity, to enable full fail-over capability for all workloads. 

 

It is extremely important to review the entire <doc name> on the Solutions Support portal to understand the complete Hybrid Cloud validated solution. 

 

For questions or additional information: