Offline foundation applet not detecting nodes (Lenovo)

  • 18 November 2021
  • 1 reply

hi Friends,


We have a 3-node Lenovo SR530 with IPMI IPs set. We are trying to install and Setup the Cluster remotely (vpn). Below are the details of IPs,

XCC IPs - 172.31.199.x (all 3 nodes of same subnet)

AHV IPs - 172.31.199.x (all 3 AHVs IPs of same subnet as XCC)

CVM IPs - 192.168.5.x (All CVM IPs with thier default IPs)



  • I have installed Foundation Applet 5.1 and while running on my laptop, its not able to detect the nodes. Any idea on what to check?
  • The other way suggested in one of the forums was execute the cluster create command in one of CVMs. But all the CVMs have same IPs ( Should I change the IPs of all CVMs with unique IPs matching with AHV and XCC Subnet IPs and then execute cluster create command?
  • How can I know the CVM IP address from the AHV cli

Foundation Applet error message

Java Web Start 11.311.2.11
Using JRE version 1.8.0_311-b11 Java HotSpot(TM) Client VM
JRE expiration date: 19/2/22 12:00 AM
console.user.home = C:\Users\KishoreSalipalli
c:   clear console window
f:   finalize objects on finalization queue
g:   garbage collect
h:   display this help message
m:   print memory usage
o:   trigger logging
p:   reload proxy configuration
q:   hide console
r:   reload policy configuration
s:   dump system and deployment properties
t:   dump thread list
v:   dump thread stack
0-5: set trace level to <n>
Nov 18, 2021 5:42:09 PM info
INFO: Running discovery
name:eth1 (Bluetooth Device (Personal Area Network))
name:wlan0 (Microsoft Wi-Fi Direct Virtual Adapter #2)
name:wlan1 (Intel(R) Wi-Fi 6 AX201 160MHz)
name:wlan2 (Microsoft Wi-Fi Direct Virtual Adapter)
name:eth6 (Cisco AnyConnect Secure Mobility Client Virtual Miniport Adapter for Windows x64)
name:eth6 (Cisco AnyConnect Secure Mobility Client Virtual Miniport Adapter for Windows x64)
name:eth7 (Intel(R) Ethernet Connection (13) I219-LM)
Starting 7 discovery threads.
Nov 18, 2021 5:42:11 PM info
INFO: Discovery complete
Nov 18, 2021 5:42:11 PM info
INFO: Discovered 0 nodes


1 reply

Userlevel 3
Badge +5

@Kishore Salipalli The CVM IPs which are in the 192.168.5.x subnet is used only for CVM-hypervisor communication. Those CVM IPs are not used for external CVM communication. 

Each CVM and AHV hypervisor has two networks associated with it:

  1. External network - which is used to connect to the AHV host/CVM externally (which is 172.31.199.x network in your case)
  2. Internal Nutanix network - generally used for CVM-host storage communication (192.168.5.x network). This network is not recommended to be used for external CVM/host communication. This internal network is set up during the initial node imaging and should not be modified later. 

Hence, in your case, you will need to configure external IP addresses for CVMs as well. (belonging to the same subnet as AHV hosts - 172.31.199.x network). 

Since you have not created a cluster as of yet and only have the factory imaged nodes (i.e., AHV hypervisor + CVM is present on the node), hence you can use the following guide to configure CVM external IP address manually -


Refer to the Foundation field installation guide for more details about cluster creation using foundation.