Skip to main content
Omnitracs Knowledge Base

Point-to-Point Connection Profile

Appendix K - Point-to-Point Connection Profile

This appendix describes the attributes of the TCP/IP Point-to-Point Connection Profile (PPP). The QTRACS Communications Manager uses the PPP when it initiates a switched (dial) connection to the Customer Gateway (CGW) at the NMC. The name of the profile is OMPTPPRF. It must be created and maintained via the Operations Navigator interface. Operations Navigator is a component of the Client Express software and the OS/400 operating system. Client Express is a licensed program of OS/400 that allows integration with Windows clients. Operations Navigator provides a GUI to various management tasks on the AS/400.

This profile is explicitly started/ended by the QTRACS Communications Manager when it is configured to connect to the NMC via TCP-Dial mode. This profile contains all of the information necessary to create and maintain the connection. There are no other communications-related virtual devices that must be manually established on the AS/400 to support a TCP-Dial connection.

The following snapshots show the various dialogue panels presented by the Operations Navigator when creating a new point-to-point connection profile. (The dialogue snapshots presented within this appendix are from the v5r1 version of Client Access Express. Other versions are slightly different.) The attributes must be set as shown.

To create (or maintain) a point-to-point connection profile:

  • Start the Operations Navigator.
  • Under the desired iSeries machine, select Network, then Remote Access Services, then Originator Connection Profiles.
  • Right-click the Originator Connection Profiles item and select New Profile. The following dialogue panel appears:
  • Leave the defaults as shown and click OK. The General panel appears.
  • Type the name and description as shown above.
  • Click the Authentication tab.
  • Check Allow the remote system to verify the identity of this AS/400. CHAP is required by the remote system. This security algorithm also demands a User Name and Password that will be authenticated by the Cisco 5400 Remote Access Server. This password is not the same as that used by the QTRACS Comm Manager to sign on to the NMC.
  • Click the TCP/IP Settings tab.
  • Allow the remote system to dynamically assign both the Local IP address and the Remote IP address. The remote system is not the NMC; rather it is another computer (the Cisco 5400 Remote Access Server) on the remote network that handles the remote end of our point-to-point connection.
  • Select Define additional static routes and click the Routes button.
  • Press the Add button and define the route as shown above.
  • Click OK.
  • Click the DNS tab.
  • Do not specify a DNS here. This DNS is supplemental to the DNS's already used by the AS/400. The Qualcomm DNS entries should be entered as normal in the CFGTCP green-screen dialogue. Typically, there are two DNS entries that are required to access Qualcomm machines; one for the machines at the San Diego NMC, and another for the machines at the Las Vegas NMC.
  • Click the Other tab.
  • Leave the default subsystem.
  • No connection scripts are necessary; leave unchecked.
  • Click the Connection tab.
  • Set the Connections allowed attribute to Dial. You don't want to accept incoming calls via this connection.
  • Leave the remaining attributes at their defaults as shown.
  • Click the Link tab.
  • Specify a line speed of 9600 bps. Significant throughput gains are not realized by setting the line speed to a higher value. In addition, 9600 bps provides a very reliable connection.

The remaining attributes found under the Limits, Modem, Security, and Additional Parameters tabs may be left at their default values. It is not necessary to visit those.

  • Click OK to return to the OMPTPPRF Connection panel.
  • Press OK again to complete the definition of the PPP connection profile.
  • Was this article helpful?