An administrator is deploying an NC2 cluster in Azure and observes on NC2 console that nodes will not progress and continue in a Booting state.
What is the most likely cause for the node not continuing to deploy?
Azure Subscription Validation: When deploying an NC2 cluster, the Azure subscription must be validated and allowlisted by Microsoft. This is a crucial step to ensure that the necessary permissions and configurations are set up for the deployment.
Booting State Issue: If the nodes are stuck in the Booting state, it often indicates that the subscription has not been properly validated and allowlisted. This prevents the deployment from progressing as required resources and permissions are not fully accessible.
Checking Allowlisting Status: Administrators should verify that their subscription has been allowlisted by contacting Azure support or checking the status through the Azure portal.
Resolution: Once the subscription is validated and allowlisted by Microsoft, the deployment should proceed without the nodes getting stuck in the Booting state.
Nutanix NC2 on Azure Documentation
Azure Subscription Management
An administrator deploys an NC2 cluster in Azure and uses 10.100.0.0/16 for one of the VNets.
The cluster is configured as follows:
* 8 nodes
* Prism Central Deployed
* Files Deployed
Following the deployment, the administrator experiences network connectivity issues.
Which reason explains the connectivity issues?
Network Configuration: Using a specific IP range for a VNet can cause conflicts if that range is reserved or already in use by the cluster's internal operations.
Internal Usage: In NC2, certain IP ranges are reserved for internal cluster functions and should not be used for VNets to avoid IP conflicts and connectivity issues.
Impact: If the 10.100.0.0/16 range is reserved for internal usage, using it for a VNet would lead to IP conflicts, causing network connectivity issues.
Verification: It's important to verify the reserved IP ranges in the NC2 documentation before assigning them to VNets.
Conclusion: The connectivity issues are likely due to using the 10.100.0.0/16 range, which is reserved for internal cluster usage.
Nutanix Networking Guidelines
Azure Virtual Network Documentation
Which entity should be contacted for cloud hardware support (EC2 instances, VPC, etc) related to NC2?
Cloud Hardware Support: For issues related to cloud hardware, such as EC2 instances or VPC configurations, the responsible entity is typically the public cloud vendor.
Nutanix Responsibility: Nutanix manages the software layer and integration aspects of the NC2 service, but the underlying hardware support is managed by the cloud provider (e.g., AWS, Azure).
Support Process:
Public Cloud Vendor: Contact the public cloud vendor for issues directly related to the hardware, as they own and manage the physical infrastructure.
Nutanix: For software and configuration issues specific to the NC2 service, contact Nutanix support.
Conclusion: For cloud hardware-related support, the appropriate contact is the public cloud vendor.
Nutanix Support Guide
Azure Support Documentation
An administrator needs to open the following ports in the firewall between an on-premises cluster and azure for disaster recovery:
* 22
* 2009
* 2020
* 2049
* 3260
* 9440
Which rile-type should be created on the firewall for communication to be appropriately established?
Port Requirements: The specified ports (22, 2009, 2020, 2049, 3260, 9440) are commonly used for various services and require TCP communication.
Port 22: SSH
Port 2009: Used for Nutanix internal communication
Port 2020: Nutanix services
Port 2049: NFS
Port 3260: iSCSI
Port 9440: Nutanix Prism management
Communication Type: To ensure proper disaster recovery setup, bi-directional communication is needed to allow traffic to flow both from on-premises to Azure and vice versa.
TCP Protocol: These ports use the TCP protocol, which provides reliable communication between devices.
Conclusion: Creating a bi-directional (TCP) rule on the firewall allows the necessary communication for disaster recovery processes.
Nutanix Networking and Security Documentation
Azure Networking Documentation
An administrator is deploying an NC2 cluster in Azure and observes on NC2 console that nodes will not progress and continue in a Booting state.
What is the most likely cause for the node not continuing to deploy?
Azure Subscription Validation: When deploying an NC2 cluster, the Azure subscription must be validated and allowlisted by Microsoft. This is a crucial step to ensure that the necessary permissions and configurations are set up for the deployment.
Booting State Issue: If the nodes are stuck in the Booting state, it often indicates that the subscription has not been properly validated and allowlisted. This prevents the deployment from progressing as required resources and permissions are not fully accessible.
Checking Allowlisting Status: Administrators should verify that their subscription has been allowlisted by contacting Azure support or checking the status through the Azure portal.
Resolution: Once the subscription is validated and allowlisted by Microsoft, the deployment should proceed without the nodes getting stuck in the Booting state.
Nutanix NC2 on Azure Documentation
Vernell
10 days agoSommer
17 days agoFrederica
25 days agoCharlie
1 month agoMicheline
1 month agoMalcom
2 months agoNathan
2 months agoAlva
2 months agoAlonso
2 months agoCordie
3 months agoJani
3 months agoTashia
3 months agoCarman
3 months agoAnnamaria
4 months agoPamella
4 months agoFletcher
4 months agoJoni
4 months agoDominque
5 months agoSusy
5 months agoAndra
5 months agoGertude
5 months agoJina
6 months agoKimberely
6 months agoMila
6 months agoArlyne
6 months agoCiara
7 months agoShaniqua
7 months agoRoyce
7 months agoCarman
7 months agoCecily
7 months agoJodi
7 months agoBronwyn
7 months agoCelestine
9 months agoJerlene
9 months agoNa
10 months agoCaprice
10 months agoRoslyn
10 months agoTawna
11 months agoMargurite
11 months agoSharen
12 months agoHubert
1 year agoEdison
1 year agoMargurite
1 year agoShawnee
1 year agoTuyet
1 year agoClare
1 year agoBong
1 year agoSarah
1 year agoJoseph
1 year agoSharika
1 year agoAn
1 year agoYan
1 year ago