The following sections provide guidance for troubleshooting connectivity issues:
Before performing further troubleshooting, verify that you have an available route between
PowerProtect Data Manager and the affected components. Try to ping the affected component and verify that the affected component is online.
Unable to resolve a
protection engine
Connect to the
PowerProtect Data Manager console and change to the root user. Using a Linux text editor, open
/etc/resolv.conf and verify that the DNS server details are correct.
Unable to connect to an appliance or file server
Verify that the network connections between
PowerProtect Data Manager, the
protection engines, and the appliance or file server are operational.
Error messages during
protection engine or Search Engine node deployment
You may receive HTTP 503 service unavailable errors, messages about
Certificate window disabled, or connection errors. Ensure that the local DNS service provides hostname and FQDN resolution for all components.
Unable to connect to a
protection storage system
This symptom includes being unable to verify the connection to a
protection storage system and connection timeouts.
Ensure that the stored security certificate for the
protection storage system is valid. Verify that
DD Boost is enabled. Verify that the
protection storage system has enough available space.
Unable to add an asset source
If you can ping the asset source, connect to the
PowerProtect Data Manager console as the admin user. Try to establish a connection on the applicable port with the command
curl -S
asset:port. Observe the output from
curl.
Unable to connect to a
protection engine after deployment
Verify whether
PowerProtect Data Manager and the
protection engine are on the same virtual network (VLAN).
Data is not available for the Topic
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: <>()\