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
An administrator has recently deployed an NC2 on azure cluster, but does not have connectivity back to the on-premises environment. The administrator would like to start working on configuring the new cluster.
What is the best way to get access to Prism Central?
Jump Host Deployment: A Jump Host provides a secure method to access the NC2 environment when direct connectivity is unavailable. Deploying it in an external VNet allows flexibility in managing network access and security.
VNet Peering: By peering the external VNet (where the Jump Host is deployed) with the VNet containing Prism Central, the administrator can establish a communication pathway. This setup enables secure and controlled access to Prism Central from the Jump Host.
Azure VNet Peering Documentation
Nutanix NC2 Configuration and Access Guide
A new subnet needs to be created within Flow Virtual Networking to accommodate a new type of workload in the company's NC2 Azure instance.
Which type of network will satisfy this task?
Flow Virtual Networking: Nutanix Flow Virtual Networking allows for the creation of overlay networks to segment and manage network traffic.
Network Types:
Underlay: Refers to the physical network infrastructure.
Overlay: Logical network built on top of the physical infrastructure, providing flexibility for creating isolated subnets and accommodating different workloads.
VPC: Virtual Private Cloud, a network within a public cloud provider.
VNET: Azure-specific virtual network.
Requirement: Creating a subnet for new workloads within Flow Virtual Networking suggests using an overlay network for logical separation and management.
Conclusion: An overlay network within Flow Virtual Networking will satisfy the task of accommodating a new type of workload in the NC2 Azure instance.
Nutanix Flow Networking Guide
Frederica
2 days agoCharlie
9 days agoMicheline
17 days agoMalcom
26 days agoNathan
1 month agoAlva
1 month agoAlonso
2 months agoCordie
2 months agoJani
2 months agoTashia
2 months agoCarman
3 months agoAnnamaria
3 months agoPamella
3 months agoFletcher
3 months agoJoni
4 months agoDominque
4 months agoSusy
4 months agoAndra
4 months agoGertude
5 months agoJina
5 months agoKimberely
5 months agoMila
5 months agoArlyne
6 months agoCiara
6 months agoShaniqua
6 months agoRoyce
6 months agoCarman
6 months agoCecily
7 months agoJodi
7 months agoBronwyn
7 months agoCelestine
9 months agoJerlene
9 months agoNa
9 months agoCaprice
9 months agoRoslyn
10 months agoTawna
10 months agoMargurite
10 months agoSharen
11 months agoHubert
11 months agoEdison
11 months agoMargurite
12 months 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