5 Essential Tips for Maximizing Your Experience at Nutanix .NEXT for Bloggers
Hello @rockstershiny When deploying a Mine cluster, you now have to option to use an existing Veeam Backup & Replication server instead of deploying a new server within the Mine. Foundation for Mine with Veeam automatically installs Veeam Backup & Replication version 11 Cumulative Patch 2 (11.0.0.837 P20210525). If you are going to use the existing v9.5, I guess it would work, as Mine v1.0 supports Veeam v9.5 Veeam socket license it related to backup ESXi and Hyper-V not related to use Mine as Network share or DAS repo Hello @MoustafaThank you for the answer. I have Mine v3 installed, I suppose there is no official documentation to see whether Veeam v9.5 is supported as an existing server? Actually in the Mine with Veeam installer it asks to upload a .lic licence file for Instance-based license (This is from documentation):
Hi bcaballero,Thank you for your reply. I still quite don’t understand how a shared IPMI port (1G) or its failover (10G) can be used for imaging, because I encountered the errors in my screenshot above (NIC flap).
Hi, thank you for your detailed answer. My question is about whether I can do this: Connect one cable to the dedicated IPMI, and the other to the Shared IPMI (instead of a 10G data port)? I’m asking because I tried doing it in a greenfield deployment last week, and Foundation could not proceed (fatal error: waiting for installer to boot up) with the following error in Phoenix kernel: eth1 did not provide connectivity to (Workstation IP) I ended up using the 10Gb SFP port instead of the Shared IPMI, and it worked. I guess Foundation need to see (at least some of) the networks interfaces to setup the cluster. what you describe looks more like the phoenix process than the foundation process. Foundation process is dedicated to setup a whole cluster, Phoenix is dedicated to just image a node, so you can integrated it to an existing cluster, or just for recovery purpose. Using phoenix you can probably be able to image you nodes independently and after use
Hi @rockstershiny Which hardware are you using? Regards! NX-8155-G8
Hi @rockstershiny I suppose that you are going to perform a bare metal foundation on a flat switch, with that being said: If you are using Supermicro hardware (NX models) the answer is yes, nodes come factory configured with IPMI interface in failover, which behaves in the following way. On boot if dedicated IPMI interface is connected that one will be used otherwise the shared IPMI port will be used. On my own experience what worked best for me is plugging one cable to the IPMI and another to one of the BASE-T ports. Speaking about Dell and HPE, as far as i know the don’t have a shared IPMI port and you have to connect one cable to the IPMI and another to the 10G ports. Hope this helps Regards! Hi, thank you for your detailed answer.My question is about whether I can do this: Connect one cable to the dedicated IPMI, and the other to the Shared IPMI (instead of a 10G data port)?I’m asking because I tried doing it in a greenfield deployment last week, and Foundation could not pr
Hi @rockstershiny Your switches needs to be “stacked” among them and if using Active-Backup the only thing to be configured on switch ports is the trunk and default/native VLAN. Why do you need the stack? Imagine that the uplink from SW1, which have the active nic of the nodes fails. Your nodes will continue using that nic because the switch is “alive” and traffic will flow through the switch stack to the “live” uplink on SW2. Hope this helps Regards! Hi @bcaballero. I get it now. Thank you again for your time in explaining this.Kind regards,
One more question if I may, if we go with the default active-backup bond, and the switches have vPC configured between them, doesn’t that mean that the AHV hosts will have to be configured for LACP as well? Hello Reckershiny, In Active-Standby (Active-Backup) scenario you won’t have to configure LACP, the only scenario which needs LACP is Active-Active (Balance-TCP) configuration. Regards, Hindawi Hello @Moustafa Hindawi. Thank you for the clarification. In this case the switches are stackable managed switches, I’m understanding that there is no need for configuring the switches in case of Active-Backup, so in this scenario no vPC or Stack is required?
Hi @rockstershiny I’ve seen your reddit post but i’ll be answering here. Hope this helps Regards! Hi Bcaballero, I thank you so much for this detailed breakdown. It sure helped a lot to understand. One more question if I may, if we go with the default active-backup bond, and the switches have vPC configured between them, doesn’t that mean that the AHV hosts will have to be configured for LACP as well?
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.