IBM Support

CRTSRVCFG Command

Troubleshooting


Problem

This document provides the CRTSRVCFG parameters to be used in creating all configuration scenarios.

Resolving The Problem

This document provides the CRTSRVCFG parameters to be used in creating all configuration scenarios. The examples are for a Primary connection. A Primary and Backup connection configuration can be created.

It is highly recommended that systems be up to date on PTF levels.

N1021619: IBM i 7.1 Recommended Fixes - Electronic Services
N1021628: IBM i 7.2 Recommended Fixes - Electronic Services
N1021286: IBM i 7.3 Recommended Fixes - Electronic Services
 

R710 and higher:

  • Creating a Direct Internet Connection for the Local System

    NOTE: When creating a direct connection, the process first attempts to use HTTP/HTTPS to connect to IBM. If an HTTP/HTTPS connection fails, the process attempts to use VPN. If VPN fails, an attempt to use a modem, whether it exists or not, it tried.

    To create a direct internet connection for only the local system, type the following:

    CRTSRVCFG ROLE(*PRIMARY) CNNTYPE(*DIRECT) CNTRYID(*SELECT) STATE(*SELECT) CNNPNT(*NO)

    To create a Direct connection for only the local system with a proxy, type the following:

    CRTSRVCFG ROLE(*PRIMARY) CNNTYPE(*DIRECT) CNTRYID(*SELECT) STATE(*SELECT) CNNPNT(*NO) PROXY(XXXXXX *IBMSVR *TRYAFTER UUUUU (PPPPP))

    where XXXXXX is the TCP/IP address of the proxy, *IBMSVR is the port data, *TRYAFTER is the relative priority, UUUUU is the proxy user ID, and PPPPP is the proxy password. Press the Enter key.

     

    Notes:

    1. The user ID and password are only required if the proxy used requires a user ID and password. If not, the proxy parameter would look like this: PROXY(XXXXXX *IBMSVR *TRYAFTER)

    2. *TRYAFTER is the default; however, if the user wishes to have the proxy attempted first, they need to specify *TRYBEFORE.

    o Profiles QVPN01IBM1 and QVPN01IBM2 are created.

    3. If the user ID or password for the proxy is case sensitive, include single quotes around the values, ie 'uUUuu' ('PpppP')

     

 

  • Creating a Multihop HTTP/HTTPS Connection for the Local System

    Starting at V7R1, inventory and PM data cannot be sent to IBM using a VPN connection. At V7R2, inventory and PM data as well as PTF orders and problem reporting cannot use a VPN connection. A *MULTIHOP connection uses VPN thus should not be used for V7R1 and cannot be used for V7R2 and higher systems. To set up a multihop environment that uses HTTP/HTTPS, one system can be set up as an HTTP/HTTPS proxy HUB and then other systems can use this system as the proxy server.

    To create the primary HUB system which connects to IBM using HTTP/HTTPS:

    CRTSRVCFG ROLE(*PRIMARY) CNNTYPE(*DIRECT) CNNPNT(*YES ((*ALL)))

    The other systems will be configured to use the HUB system as a proxy server:

    CRTSRVCFG ROLE(*PRIMARY) CNNTYPE(*DIRECT) CNTRYID(*SELECT) STATE(*SELECT) CNNPNT(*NO) PROXY(HUB_System_Name *IBMSVR *TRYBEFORE)

     

 

 

R610 and lower releases:

  • Creating a VPN Primary Connection with Connectivity for Other Systems

    To create a VPN connection with connectivity for other systems (allowing another system to connect using this system), type the following:

    CRTSRVCFG ROLE(*PRIMARY) CNNTYPE(*DIRECT) CNNPNT(*YES ((*ALL)))

    Press the Enter key. This creates a direct VPN connection for both *ECS and *SRVAGT. This also creates a connection for remote systems to use the local direct connection for connectivity to IBM.

    o Profiles QVPN01IBM1, QVPN01IBM2, QMHINIBM1, QMHINIBM2, and QL2TPxx are created. The QL2TPxx profiles listen for L2TP connections on the selected interfaces.

     

 

  • Creating a Multihop VPN Connection for the Local System

    To create a Multihop VPN connection for only the local system, type the following:

    CRTSRVCFG ROLE(*PRIMARY) CNNTYPE(*MULTIHOP) RMTSYS(XXXXX)

    where XXXXX is the remote system that will be used as a gateway. Press the Enter key. This creates a multi-hop VPN connection for both *ECS and *SRVAGT to the remote system specified.

    o Profiles QVPN01IBM1 and QVPN01IBM2 are created.

    Note: If the remote system is in a State other than the local system, the local system must be configured with the same state as the remote system. For example, if the remote system is in Minnesota (MN) and the local system is in California (CA), the STATE for the local system MUST be MN, not CA. If not, transmissions will fail.

    Note: This type of connection is supported for HMC as the remote system for ECS, however the HMC is not supported as a connection for ESA.

     

 

  • Creating a Multihop VPN Primary Connection with Connectivity for Other Systems

    To create a Multihop VPN connection with connectivity for other systems (allowing another system to connect using this system), type the following:

    CRTSRVCFG ROLE(*PRIMARY) CNNTYPE(*MULTIHOP) RMTSYS(XXXXXX) CNNPNT(*YES ((*ALL)))

    where XXXXXX is the remote system that will be used as a gateway. Press the Enter key. This creates a multi-hop VPN connection for both *ECS and *SRVAGT to the remote system specified. This also creates a connection for remote systems to use the local multi-hop VPN connection for connectivity to IBM.

    o Profiles QVPN01IBM1, QVPN01IBM2, QMHINIBM1, QMHINIBM2, and QL2TPxx are created. The QL2TPxx profiles listen for L2TP connections on the selected interfaces. The HMC is also supported as a remote connection for, however, it is not supported for ESA. ESA is automatic problem reporting and inventory sending.

     

 

  • Creating an ISP VPN Connection for the Local System

    To create an ISP VPN connection for only the local system, type the following:

    CRTSRVCFG ROLE(*PRIMARY) CNNTYPE(*OTHERISP) ISPPRF(*SELECT) CNNPNT(*NO)

    Press the Enter key. This creates a VPN connection that utilizes an existing DIALISP profile for access through the ISP for both *ECS and *SRVAGT.

    o Profiles QVPN01IBM1 and QVPN01IBM2 are created.

     

 

  • Creating an ISP VPN Primary Connection with Connectivity for Other Systems

    To create an ISP VPN connection with connectivity for other systems (allowing another system to connect using this system), type the following:

    CRTSRVCFG ROLE(*PRIMARY) CNNTYPE(*OTHERISP) ISPPRF(*SELECT) CNNPNT(*YES ((*ALL)))

    Press the Enter key. This creates a VPN connection utilizing an existing DIALISP profile for access through their ISP for both *ECS and *SRVAGT. This also creates a connection for remote systems to use the local ISP VPN connection for connectivity to IBM.

    o Profiles QVPN01IBM1, QVPN01IBM2, QMHINIBM1, QMHINIBM2, and QL2TPxx are created. The QL2TPxx profiles listen for L2TP connections on the selected interfaces.

     

 

Currently disbanded:

Important: June 30, 2018, AT&T discontinued Dial features in the United States. All remaining non-US countries were discontinued on June 30, 2017. All clients must migrate to broadband via the appropriate means. IBM will not seek to offer an alternative provider and requests all clients to move to broadband technology for call home and remote support services.

 

  • Creating AT&T Dial Connections for the Local System

    To create AT&T dial connections for only the local system, type the following:

    CRTSRVCFG ROLE(*PRIMARY) CNNTYPE(*LCLDIAL) CNTRYID(*SELECT) STATE(*SELECT) TELNBR1(*SELECT) TELNBR2(*SELECT) RSRCNAME(*SELECT) MODEM(*SELECT) CNNPNT(*NO)

    Press the Enter key. This creates an AT&T dial connection for both *ECS and *SRVAGT.

    o Profiles QLCLDIAL01, QVPN01IBM1, and QVPN01IBM2 are created.

     

 

  • Creating a Remote AT&T Dial Connection

    To create a remote AT&T dial connection (connecting to another system), type the following:

    CRTSRVCFG ROLE(*PRIMARY) CNNTYPE(*RMTDIAL) CNTRYID(*SELECT) STATE(*SELECT) RMTSYS(XXXXX)

    where XXXXX is the remote system that will be used as a gateway. Press the Enter key. This creates an AT&T dial connection for both *ECS and *SRVAGT to IBM through the modem of the remote system that is specified.

    o Profiles QRMTDIAL01, QVPN01IBM1, and QVPN01IBM2 are created.

     

 

  • Creating Primary AT&T Dial Connection with Connectivity for Other Systems

    To create an AT&T dial connection with connectivity for other systems (allowing another system to connect using this system), type the following:

    CRTSRVCFG ROLE(*PRIMARY) CNNTYPE(*LCLDIAL) RSRCNAME(*SELECT) MODEM(*SELECT) CNNPNT(*YES ((*ALL)))

    Press the Enter key. This creates an AT&T dial connection for both *ECS and *SRVAGT. This also creates a connection for remote systems to use the local modem for connectivity to IBM. This system is the system that other systems will connect through.

    o Profiles QLCLDIAL01, QVPN01IBM1, QVPN01IBM2, and QL2TPxx are created. The QL2TPxx profiles listen for L2TP connections on the selected interfaces.

     

[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SWG60","label":"IBM i"},"Component":"Basic System Environment Functions (BSEF)","Platform":[{"code":"PF012","label":"IBM i"}],"Version":"5.4.0;5.4.5;6.1.0;6.1.1;7.1.0;7.2.0;7.3.0","Edition":""},{"Product":{"code":"SSC3X7","label":"IBM i 6.1"},"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Component":" ","Platform":[{"code":"","label":""}],"Version":"","Edition":""},{"Product":{"code":"SSC52E","label":"IBM i 7.1"},"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Component":" ","Platform":[{"code":"","label":""}],"Version":"","Edition":""},{"Product":{"code":"SSTS2D","label":"IBM i 7.3"},"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Component":" ","Platform":[{"code":"","label":null}],"Version":"","Edition":""},{"Product":{"code":"SSC5L9","label":"IBM i 7.2"},"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Component":" ","Platform":[{"code":"","label":null}],"Version":"","Edition":""}]

Historical Number

482884886

Document Information

Modified date:
18 December 2019

UID

nas8N1018762