Symantec Server information - FQDN, IP Addresses and Port required for CallHome Configuration

Compute Node nodename Time Monitoring Ran: Sat Apr 11 2015 00:57:13 EEST CALLHOME status: Not able to upload callhome data Error: 500 read failed: Please contact Symantec Support to resolve this issue.

AutoSupport: Symantec Server information - FQDN, IP Addresses and Port required for CallHome Configuration

• Article: TECH211136

• Updated: December 2, 2013

• Article URL: http://www.symantec.com/docs/TECH211136

ProblemThe Symantec appliance should have Internet access, either directly or via a proxy server, to communicate with Symantec Web servers/services for Symantec AutoSupport. Users may encounter issues when they enable CallHome via the GUI if the Symantec servers are not reachable from their appliance due to network constraints like firewalls. Solution

• The CallHome agent initiates communication with https://www.symappmon.com (IP address 216.168.252.222 and 69.58.182.57) every 15 or 30 minutes to send appliance health information.

• The NetBackup Product Improvement Program agent initiates communication with https://telemetrics.symantec.com (IP address 216.10.195.50) to send appliance log files.

• The Registration server https://api.appliance.symantec.com (IP address 216.168.252.139) to enable CallHome communication with Symantec.

The Symantec appliance should have Internet access, either directly or via a proxy server, to communicate with Symantec Web servers/services for Symantec AutoSupport. The Symantec appliances use a Secure Socket Layer (SSL) communication over port 443/tcp to communicate with the following Symantec servers, hosted in a secure data center:Please note that communication, by nature, is two-way and the agent requests a config file hosted on the telemetrics server.Please consult with your network administrator to find out if a proxy server is required and/or if firewall rules need to be updated to communicate with Symantec servers.

Note: Use FQDN instead of specific IP addresses for firewall/proxy settings as the IP addresses may change with subsequent infrastructure changes.