Figure 1. SupportAssist configuration panel. Available options differ on older firmware versions.
You may observe either of the following messages in the SupportAssist configuration dialog.
Last SupportAssist logs upload failed. An MC internal error has occurred. Last SupportAssist Event upload failed. An MC internal error has occurred.
If may be a situation that the site where the PowerVault ME4 is located lost Internet connectivity temporarily or there may have been congestion or disruption on the network preventing the successful transmission of telemetry data.
NOTE: If the site where the PowerVault ME4 is located does not have Internet connectivity or security policies deny Internet access. The SupportAssist service cannot be use. Clear the Enable SupportAssist box and click Apply.
Click Check Connections to test if a successful session can be established. If the test connection fails, follow the steps below to eliminate potential causes.
Both controller module management interfaces must be connected to the LAN and configured with a valid IP address, subnet mask and gateway address. There should be a network path possible to route traffic to the site Internet gateway. This can be tested from the command-line interface (CLI) using the ping command. For more details using the CLI to troubleshoot SupportAssist see KB: CloudIQ: ME4 - How to troubleshoot CloudIQ upload failures.
A common reason SupportAssist fails to send telemetry data occurs when the PowerVault ME4 is not configured to resolve DNS names or DNS services are unreachable.
Work with your network administrator to ensure that the firewall does not block outbound TCP connections on port 443 to any of the following addresses.
Hostname | Public IP Address | Port Number |
---|---|---|
web1.compellent.com | 143.166.147.73 | 443 |
stor.g3.ph.dell.com | 143.166.135.19 (Primary) | 443 |
stor.g3.ph.dell.com | 143.166.147.73 (Secondary) | 443 |
If your organization uses a proxy server, check that the settings are correct and that the user authentication credentials are correct.
It should be possible to test connectivity to the proxy server using the ping command in PowerVault CLI. For an example using the ping command see KB: CloudIQ: ME4 - How to troubleshoot CloudIQ upload failures.
If the proxy server is reachable from the ME4, but no connection is possible check with your network administrator that firewall settings are not preventing transmission from the proxy server.
Each controller module contains a Management Controller (MC) processor and a Storage Controller (SC) processor. When necessary, you can restart or shut down these processors for one controller or both controllers. Restarting Storage controller causes the controller module that is selected to restart and may be production impacting.
Restarting management controller (MC) does not impact production however access to PowerVault Manager is not possible on a controller while MC starts. There is a disconnect to the management interface for one or two minutes before access is restored.
Perform the following steps to restart a management controller:
If restarting management controller (MC) resolves the issue, ensure you are running the latest controller firmware for the PowerVault ME4 available from dell.com/support. There are several issues affecting earlier controller firmware versions that cause MC to become unresponsive causing SupportAssist transmission to fail.
If the above steps fail to resolve and your PowerVault ME4 is covered by an active ProSupport contract, gather the support logs from the ME4 and contact Dell technical support for further assistance.
See related KB article: PowerVault: How to collect PowerVault ME4 support logs