Verifying the connection function

 

The Verify Connection function that is located under Management Central is different from the function that is located under My Connection. This topic discusses the purpose of each function and how they differ from each other.

 

Verifying Connection from My Connection

My Connections > Right-click a system > Diagnostics > Verify Connection

This Verify Connection function pings the different host servers to see if they are up and running correctly and can be reached from the PC. Since it is restricted to single system Navigator functions, it is one of the first things you should rule out when you are troubleshooting a Management Central connection failure. (Many Management Central functions build on the single system functions.) After you have confirmed that the connection to the endpoint systems, under My Connections is successful, then you can proceed to verify the connection from Management Central.

 

Verifying Connection from Management Central

Right-click Management Central > Verify Connection

The Verify Connection function from the Management Central container is a diagnostic tool that checks the most common factors that can cause a failed connection. It then displays the status of these tests. If it reports any failures, you can obtain specific information about the failure as well as recovery information by clicking Details. The following is a list of what Management Central verifies.

• The Java™ setup is correct on the Central System (This includes verifying that certain .jar files are present, and that certain integrated file system file and folder authorities have not been changed

• The required files that were shipped with the operating system have not been deleted from the Central System, are not damaged, and are being journaled

• The TCP/IP configuration on the Central System is valid (This includes verifying that the host name of both the Central System and the PC are in the host tables or in the DNS as appropriate

• That a simple Navigator connection can be made to the Central System

• The VRM, host name, the IP address of the Central system, and the VRM of iSeries™ Navigator

• That the ports that Management Central uses are not in use by another application on the central system

• That on the central system, the user profiles that are needed to run Management Central have not been deleted, or disabled and that they have valid, unexpired passwords.

• That if SSL is being used on the central system, it is configured correctly and that both the PC and central system are using SSL.

• That the central system isn't marked as a "secondary system" in an Management Central High Availability environment (Secondary systems cannot be used as central systems.)

• That the Management Central servers are up and running on the central system

• It reports what types of authentication are supported on the central system

iSeries Navigator uses the Java toolbox code on the client side (PC) to start the Management Central Verify Connection function. If the toolbox code is not working correctly then the Verify Connection function will not start. If the Java Virtual Machine (JVM) or the toolbox code on the server side is not working correctly, the Verify Connection function will work until the last few checks. The JVM must start before these last few checks can be performed.

 

Parent topic:

Installing Management Central

 

Related information

IBM Toolbox for Java