- Notes, cautions, and warnings
- Introduction
- New and enhanced features
- Minimum requirements to deploy and use Secure Connect Gateway
- Supported servers
- 16th generation PowerEdge servers
- 15th generation PowerEdge servers
- 14th generation PowerEdge servers
- 13th generation PowerEdge servers
- 12th generation PowerEdge servers
- 11th generation PowerEdge servers
- 10th generation PowerEdge servers
- 9th generation PowerEdge servers
- C series PowerEdge servers
- XE series PowerEdge servers
- XR series PowerEdge servers
- Datacenter Scalable Solutions
- AX nodes
- PowerVault devices
- Supported Integrated Remote Access Controllers (iDRAC)
- Supported chassis
- Supported data storage devices
- Supported networking switches
- Supported hypervisors
- Supported virtual machines
- Supported data protection devices
- Supported direct liquid cooling devices
- Supported converged and hyperconverged infrastructure appliances
- Supported systems management consoles
- Supported management and monitoring software
- Supported server operating systems and recommended OMSA version
- Support for OEM devices
- Secure Connect Gateway resources
- Contacting Dell Technologies
Secure Connect Gateway 5.x — Virtual Edition Support Matrix
Supported converged and hyperconverged infrastructure appliances
The following table lists the supported converged and hyperconverged infrastructure appliances:
| Model | TCP port or collection protocol | Direction | Source or Destination | Application name | Communication |
|---|---|---|---|---|---|
| APEX Cloud Platform | 22 | Inbound | From secure connect gateway | CLI (via SSH) | Remote support |
| Converged Management Software | HTTPS 9443 | Outbound | To secure connect gateway | REST | Service notification |
| 22 | Inbound | From secure connect gateway | CLI (via SSH) | Remote support | |
| 443 | Secure Web UI | ||||
| PowerFlex Appliance | HTTPS 9443 | Outbound | To secure connect gateway | REST | Service notification |
| 22 | Inbound | From secure connect gateway | CLI (via SSH) | Remote support | |
| 3389 and 3390 | Remote desktop | ||||
| 8080 | Web UI | ||||
| PowerFlex | HTTPS 9443 | Outbound | To secure connect gateway | REST | Service notification |
| 22 | Inbound | From secure connect gateway | CLI (via SSH) | Remote support | |
| 443 | PFMPHTTPS | ||||
| PowerFlex Rack | HTTPS 9443 | Outbound | To secure connect gateway | REST | Service notification |
| 22 | Inbound | From secure connect gateway | CLI (via SSH) | Remote support | |
| 3389 | Remote desktop | ||||
| 8080 | Secure Web UI | ||||
| 443 | PFMPHTTPS | ||||
| VxRail | HTTPS 9443 | Outbound | To secure connect gateway | REST | Service notification |
| HTTPS | ConnectEMC | ||||
| Passive FTP | |||||
| SMTP | |||||
| 22 | Inbound | From secure connect gateway | CLI (via SSH) | Remote support | |
| VxRack SDDC | HTTPS 9443 | Outbound | To secure connect gateway | REST | Service notification |
| 22 | Inbound | From secure connect gateway | CLI (via SSH) | Remote support | |
| Web-Scale | 9440 and 22 | — | — | — | — |
| REST and SSH |
NOTE:The use of HTTPS for service notifications depends on the version of ConnectEMC used by the managed device. For more information, see the product documentation. The default port for HTTPS is 443. The value for Passive Port Range in FTP is set to 21 and 5400 through 5413. This range indicates the data channel ports available for the response to the PASV commands. These ports are used for the Passive FTP mode of the Connect Home messages and for the GWExt loading and output.
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\