So you have checked the zCommandUsername and zCommandPassword for the device and/or you have set up key files and zKeyPath is correct in the device's Configuration Properties?
You say you can successfully authenticate from the collector host? How did you test this?
| Subject: |
RE: Linux modelling using FQDN - error |
| Author: |
Manoj M |
| Posted: |
2017-11-29 04:54 |
Yes Jane,
I have setup the correct credentials in zCommandUsername and zCommandPassword in the device's Configuration Properties?I'm able to successfully authenticate using password and as well as key-based from Modeller and command container of Collector host. ( and from collector host as well)
Nslookup to FQDN of the device looks good as well.
If I use ip-address , I'm able to model the device. But if I model the device using FQDN omitting the ip-address, im getting the below said error.
ERROR zen.SshClient: Connection was refused by other side: 111: Connection refused.We are not supposed to use ip-address in this environment, as they were dynamic.
Windows Device works fine using FQDN. (It makes sense as we provide
zWinKDC and
zWinRMServerName).
Please help on this.
------------------------------
Manoj M
Cognizant
------------------------------
| Subject: |
RE: Linux modelling using FQDN - error |
| Author: |
Jane Curry |
| Posted: |
2017-11-30 13:58 |
This sounds more like a DNS issue than an ssh issue if it works by IP address but not by fully-qualified domain name (FQDN).
The other possibility might be that the known_hosts under the .ssh directory probably for the zenoss user, has a bad host key; I guess this will be in the zencommand container. Have you command-line tested ssh from that zencommand container, using both IP and FQDN?
Cheers,
Jane
------------------------------
Jane Curry
Skills 1st United Kingdom
jane.curry@skills-1st.co.uk
------------------------------
