Description
What are tips for troubleshooting Saas collector registration issues?
On collector, make sure the collector can reach the AccelOps SaaS environment:
1. Nslookup for dns setting:
[root@accelops ~]# nslookup saas.accelops.net
Server: 10.1.200.138
Address: 10.1.200.138#53
Name: saas.accelops.net
Address: 209.235.239.77
2. Access saas https port
[root@accelops ~]# telnet saas.accelops.net 443
Trying 209.235.239.77...
Connected to saas.accelops.net.
Escape character is '^]'.
When we see this then that means that the collector is able to get past our firewall and is in good shape and the collector settings are normal. We block all IPs from Saas otherwise and that's why during setup an external IP from the customer is necessary.
Additional info:
Check the collector hostname. The hostname of collector input in the VMware console should have the same hostname which is contained within the AccelOps welcome letter.
Name: myCollectorName
User ID: admin
Password: admin*1
Cust/Org ID: abc .com
Cloud URL: https://saas.accelops.net
When you configure the collector on VMware console, the hostname must be myCollectorName or you will not be able to register and access the Saas environment.
