Connectivity


The Connectivity page allows you to test the network connectivity to your console controller before you start up the CCS server. This allows you to build confidence in your CCS Session configuration without having to actually run the CCS server.

Connectivity tab

GUID-5B750D05-905A-4CEF-BEB5-D18B21A5FDA1-low.jpg

The host name or IP address to test. Defaults to the value you entered in this field on the General tab.

Port

A single port to be tested when the Connect button to the right is pressed. No effect on the Ping command.

Ping

The Ping command performs the lowest level network connectivity test. The Ping command requires the upstream IP address to be entered. Typically this will be the IP address of the OSA-ICC, Visara, or 2074 controller. If DNS is properly set up, the DNS name may be entered as well. Once the host name or IP address is entered, click the Ping button. The results of the Ping command are displayed under Results.

A successful Ping ensures that the IP address is correct and that the network routing is configured properly to allow network traffic to the specified IP address and back. If the ping fails, ensure that the IP address is correct and consult your network administrator.

While the Ping command is most useful for testing the network connectivity between the MVCM server and the console controller, it can also be used to troubleshoot network issues to desktop computers running viewer software. Simply enter the IP address of the desktop computer and click Ping. If the Ping registers a successful result, firewall or configuration issues should be examined.

Connect

The Connect command ensures that a TCP/IP connection can be made between the MVCM server and the specified IP address. Both the Upstream IP address and Port are required. Typically, this will be the IP address of the controller and the TCP/IP port upon which the controller expects TCP/IP connections. Typically this will be 3270 for an OSA-ICC, but may be different.

The list of configured console sessions is displayed and you can test the low level socket connection as well as a complete TN3270 connection. The low level socket connection helps you verify that the IP address and port are correct, and the TN3270 Connection test helps you verify that the IP address is a console controller and the correct LU name is configured.

Socket Connect All Ports

If there are multiple sessions and they are using different port values - a common way to set up Visara controllers - this button will test connectivity one at a time to each port. The test will disconnect immediately after successfully connecting without attempting to validate session 3270 values, that functionality is provided by the next button.

TN3270 Connect All Ports

More in depth than the Socket Connect test, clicking this button will connect one at time for each of the defined sessions and validate both network connectivity and the validity of session 3270 settings such as model and LU name (if specified).

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*