Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error when adding an IBM i Host #34

Open
brynpg opened this issue Feb 2, 2023 · 4 comments
Open

Error when adding an IBM i Host #34

brynpg opened this issue Feb 2, 2023 · 4 comments

Comments

@brynpg
Copy link

brynpg commented Feb 2, 2023

Hi

I'm trying to add an IBM i host which can only be connected to via secure ports (947* range).

SSL/TLS has been configured successfully - required certificates added to the Nagios keystore.
This has been proven by completing the same process on an IBM i host that can be connected on unsecure ports (847* range).

When I complete the wizard (screen shot attached) it fails with the error:
Register profile error:
java.net.SocketTimeoutException: connect timed out
Insert host failed

Does anyone have any suggestions on how I can overcome this issue?

Thanks
Nagios XI - Add IBM i Host Error

@williamlea1
Copy link

Hi,

Firstly, as its the wizard then IBM will be the place to go to get assistance with it.

Secondly have you tried to putty from Nagios server to the IBM i securely. Just to ensure certs are in place?

@SebeekS
Copy link

SebeekS commented Feb 7, 2023

I think you have to temporarily open unsecure ports, add services and then close those non-ssl ports

@brynpg
Copy link
Author

brynpg commented Feb 10, 2023

@SebeekS @williamlea1 Thanks for your replies.

Some good news ... I've found a way around this - well, it worked for me anyway.

  1. Create a local host table entry on the Nagios server for the LPAR in question but give it the IP address of an LPAR that you can communicate with over unsecure ports
  2. Run the Nagios for IBM i add host config script
    /bin/bash /usr/local/nagios/libexec/host_config.sh -i
  3. Change the local host table back to its original value

You can then configure your services to communicate over TLS/SSL for the host in question.

@SebeekS
Copy link

SebeekS commented Feb 11, 2023

@brynpg good idea. But if you have different credentials on both, you will have to change it on the secondary server so it matches later

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants