5.9 Configuring Linux Endpoints

The endpoint dynamically configures its own programs, so you do not have to update the configuration files for your communications software. However, your communications software must be configured and running correctly. Take the following steps to verify your network is ready for testing and monitoring:

  1. Determine the network addresses of the computers for use in tests.

  2. Verify the network connections.

5.9.1 Configuration for TCP/IP

The TCP and UDP protocols use TCP/IP software for network communications. TCP/IP offers two forms of network addresses: IP addresses and domain names. An IP address is a 32-bit numeric address. It is represented in dotted notation, such as 199.72.46.202. As an alternative, use domain names, which are in a format that is easier to recognize and remember. To use domain names, you need either a Domain Name Server (DNS) set up in your network or an /etc/hosts file on each computer.

5.9.2 Determining the IP Address for TAR and RPM Linux

To determine the IP address of the local computer you are using, enter the following at a command prompt:

/sbin/ifconfig

5.9.3 Determining the IP Address for Cobalt

Access the Welcome to Cobalt page on the Cobalt Web Server and click the link to the RAQ Server Management section.

After you enter the Administrator username and password, the IP address is shown on the Server Management Page.

5.9.4 Testing the TCP Connection

Ping is a simple utility program, included in all TCP/IP implementations. To test the connection from one computer to another, enter the following at a command prompt:

ping xx.xx.xx.xx -c 1

Replace the x’s with the IP address of the target computer. If Ping returns a message that says

1 packets transmitted, 1 packets received, 0% packet loss

then the Ping worked. Otherwise, there will be a delay, and you will see the following message:

1 packets transmitted, 0 packets received, 100% packet loss

This error message indicates the Ping failed, and you cannot reach the target computer.

From your AppManager, Vivinet Assessor, or Vivinet Diagnostics console computer, ensure you can run Ping successfully to each computer serving as Endpoint 1, and between each pair of endpoints involved in a test, before starting your testing with TCP/IP.

5.9.5 Sockets Port Number

TCP/IP applications use their network address to decide which computer to connect to in a network. They use a sockets port number to decide which application program to connect to within a computer.

The TCP/IP sockets port for endpoints is 10115. This port number is used during the initialization of a test; during the actual running of the test, other port numbers are used.

In Vivinet Assessor, you can configure the port number that is used.