Loading...
Loading...
Possible errors: Cluster configuration has failed. To attempt clustering again, the appliance or appliances must be placed back to their original factory default mode. Contact your service provider for assistance. To help diagnose the issue, it is highly recommended you gather support materials from the appliance as soon as possible. Further information is not provided. Depending on how far ICW progressed with clustering, management IP addresses may be configured.
A failed ICW can be caused by various issues.
The solutions that are listed here are some of the most commonly observed misconfiguration issues: PowerStoreX requires vCenter account with full Administrator privileges PowerStoreX requires valid vCenter and vSphere license to create Cluster vCenter requires specific ports to be open for communication with the ESXi nodes PowerStoreX network incorrectly configured Troubleshooting that may provide further information PowerStoreX requires vCenter account with full Administrator privileges. See PowerStore: Administrator account required for adding PowerStoreX to vCenter System . PowerStoreX requires valid vCenter and vSphere license to create Cluster. As per the PowerStore Installations-PowerStore Planning Guide, a valid vCenter Enterprise Plus license must be applied to the vCenter System before starting ICW. PowerStoreX model appliances include an embedded instance of VMware vSphere Enterprise 6.7. You can apply a license from an existing VMware ELA or purchase vSphere licenses from VMware or a partner. Ensure that your license usage has not reached its capacity, preventing the addition of ESXi nodes. vCenter requires specific ports to be open for communication with the ESXi nodes. 80 - TCP - vCenter Server requires port 80 for HTTP connections and WS-Management. 443 - TCP - Default port of vCenter System used to listen for connections from ESXi nodes. 902 - TCP/UDP - Default port used for the heartbeat by vCenter System to communicate with ESXi nodes. Port states can be confirmed from BASH on the vCSA, or PortQryUI if vCenter is installed on a host. vCSA: root@vcenter [ ~ ]# netcat <ESXi node IP Address> 902 220 VMware Authentication Daemon Version 1.10: SSL Required, ServerDaemonProtocol:SOAP, MKSDisplayProtocol:VNC , VMXARGS supported, NFCSSL supported/t Windows Standalone Server with vCenter: C:\PortQryV2>PortQry.exe -n <ESXi node IP Address> -e 902 Querying target system called: aa.bb.cc.dd Attempting to resolve IP address to a name... Failed to resolve IP address to name querying... TCP port 902 (unknown service): LISTENING C:\PortQryV2> For testing purposes, you may try manually adding the ESXi node to the target vCenter Cluster to confirm connectivity. PowerStoreX network incorrectly configured. As per "Dell PowerStore Network Configuration Guide for Dell PowerSwitch Series", Port_0 from Node A and Node B may not be connected to the same Top of Rack (ToR) Switch. The ports from the PowerStore nodes must be connected as follows: At a minimum, ports 0 and 1 on the node must be connected to the ToR switches. When cabling the nodes to the ToR switches: Port 0 and Port 1 on the same node must connect to opposite switches Port 0 on Node A, and Port 0 on Node B must connect to opposite switches Port 1 on Node A, and Port 1 on Node B must connect to opposite switches Troubleshooting that may provide further information vpxd.log from vCenter support bundle under /var/log/vmware/vpxd/ 2020-07-07T08:54:22.787Z warning vpxd[33041] [Originator@6876 sub=Default] Failed to connect socket; <io_obj p:0x000055cfc510bf20, h:-1, <TCP '0.0.0.0 : 59444'>, <TCP 'aa.bb.cc.dd : 443'> FD Closed>, e: 125(Operation canceled) 2020-07-07T08:54:22.798Z warning vpxd[33041] [Originator@6876 sub=Default] Operation cancelled 2020-07-07T08:54:22.812Z error vpxd[04863] [Originator@6876 sub=HostAccess opID=976c27a] Failed to discover version: N3Vim5Fault9HttpFault9ExceptionE(Fault cause: vim.fault.HttpFault
Click on a version to see all relevant bugs
Dell Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.