Loading...
Loading...
Customers may experience one or more of the following symptoms: IOE workflow fails during execution Error messages indicating: "Unable to establish SSH connection" "Connection timed out" "Host unreachable" Manual SSH access to VxRail nodes from the IOE network is unsuccessful
This issue is caused by network restrictions in the customer environment, including: Firewall rules blocking TCP port 22 (SSH) Network segmentation preventing IOE access to the VxRail management network Access Control Lists (ACLs) denying SSH traffic Security appliances (IPS/IDS) terminating or inspecting SSH sessions The Intelligent Orchestration Engine relies on SSH to perform required orchestration, configuration, and validation tasks across VxRail components.
Ensure that TCP port 22 (SSH) is open and allowed bi‑directionally between the IOE environment and all VxRail system components. Required Network Connectivity: The following access must be permitted: Source: Intelligent Orchestration Engine (IOE) or Secure Connect Gateway (SCG) or Embedded Service Enabler (ESE) Destination: VxRail Manager Any additional VxRail management components (as applicable) Protocol: TCP Port: 22 (SSH) NOTE: Firewall, ACL, and security policies must allow this traffic across the entire network path. Customer Verification Steps: Customers should work with their network or security teams to perform the following checks: Validate SSH Connectivity Test SSH connectivity from the IOE network to each VxRail node. Example commands: telnet <VxRail_Node_IP> 22 Or nc -zv <VxRail_Node_IP> 22 Review Firewall and Security Policies Confirm Network Routing Retry the IOE Operation
Click on a version to see all relevant bugs
Dell Integration
Learn more about where this data comes from
BugZero Plan
Streamline upgrades with automated vendor bug scrubs
BugZero Prevent
Wish you caught this bug sooner? Get proactive today.