Description
Summary of Topic
These steps help determine if a Collector is successfully communicating and sending events to the Super.
If either of these are in question then follow these steps.
Solution Steps
1. Open SSH session on Collector
2. Run ‘pwd’ for making sure if you are ~ directory
If there is a problem on network connectivity, you will see an error message such as ‘Timeout’.
Or, you will see warning message/error message for certificate if there is a problem on it.
Output example
Resolving saas... 172.16.1.151
Connecting to saas|172.16.1.151|:443... connected.
WARNING: cannot verify saas's certificate, issued by `/C=US/ST=California/L=somecity/O=xxxx.xxx/CN=CA/emailAddress=xxx@xxxx.xxx':
Self-signed certificate encountered.
HTTP request sent, awaiting response... 200 OK
Length: 288 [text/html]
Saving to: `index.html'
100%[=======================================>] 288 --.-K/s in 0s
14:03:47 (8.32 MB/s) - `index.html' saved [288/288]
Additional Information
You may need generic network troubleshooting if you see a network connectivity issue.
If you see Certificate warning/error, please refer to “Setting up a proper CA-signed certificate” section in User guide.
Refere also to the related KB article "How to apply a Self-Signed or Certificate Authority Certificate to AccelOps".
Version Application
All
