CL Command Reference - ADDTCPIFC

CL Command List > ADDTCPIFC Reference

Description:

The Add TCP/IP Interface (ADDTCPIFC) command is used to define a new interface to the Transmission Control Protocol/Internet Protocol (TCP/IP) configuration. The interfaces defined by the ADDTCPIFC command are logical interfaces. They are not physical interfaces. Each interface is associated with a line description. The line description is the physical connection from the local system to the TCP/IP network.

The i5/OS TCP/IP implementation supports multihoming. This allows you to specify either a single interface or multiple interfaces per line description. You can have your system appear as any one or combination of the following:
. A single host on a network over a communications line
. Multiple hosts on the same network over the same communications line
. Multiple hosts on different networks over the same communications line
. Multiple hosts on the same network over multiple communications lines
. Multiple hosts on different networks over multiple communications lines

Notes:
1. In SNMP, the interface is a physical interface. The physical interface relates directly to an input/output processor (IOP).
2. The interface table is shipped with a default interface of 127.0.0.1. The line description value associated with the 127.0.0.1 interface is *LOOPBACK. The host table is also shipped with an entry that has an internet address of 127.0.0.1 and host names of LOOPBACK and LOCALHOST.
3. A maximum of 16K interfaces can be defined and up to 2K interfaces can be active on any one line with the Start TCP/IP Interface (STRTCPIFC) command at any given time. This is true for all line types (for example; token-ring, Ethernet, frame relay, and so forth).

Attention: Before attempting to start an X.25 interface, ensure that the remote system information (RSI) for non-DDN X.25 interfaces that use a permanent virtual circuit (PVC) is configured. Use the Add TCP/IP Remote System Information (ADDTCPRSI) command to do this. Incoming data from a remote system on the X.25 network is not processed unless an RSI entry for the PVC is configured on the X.25 interface before the interface is started.

Restrictions:

. You must have input/output system configuration (*IOSYSCFG) special authority to run this command.


Examples:

Example 1: Adding a Non-AUTOSTART Interface

ADDTCPIFC INTNETADR(¡¯130.14.3.5¡¯) LIND(COTTAGELAN)
AUTOSTART(*NO) SUBNETMASK(¡¯255.255.255.0¡¯)

Let¡¯s assume that an Ethernet line has been created named COTTAGELAN using the CRTLINETH command, this command adds the interface 130.14.3.5 to the TCP/IP configuration. This interface uses the line description named COTTAGELAN. It is not automatically started when the STRTCP command is run. This interface must be started using the Start TCP/IP Interface (STRTCPIFC) command. The STRTCPIFC can be issued either directly from a command line or by using option 9 from either of the following lists:
. The Work with TCP/IP Interface Status list. Use menu option 1 from the menu displayed when the Work With TCP/IP Status (WRKTCPSTS) command is issued to display this list.
. The Work with TCP/IP Interfaces list. Use menu option 1 from the menu displayed when the Configure TCP/IP (CFGTCP) command is issued to display this list.


Example 2: Adding an AUTOSTART Interface

ADDTCPIFC INTNETADR(¡¯8.77.0.21¡¯) LIND(COTTAGEX25)
IDLVCTTIMO(45) MAXSVC(15) DDN(*YES)
SUBNETMASK(¡¯255.255.255.0¡¯) AUTOSTART(*YES)
AUTOSTART(*YES)

Let¡¯s assume that an X.25 line has been created named COTTAGEX25 using the CRTLINX25 command, this command adds interface 8.77.0.21 to the TCP/IP configuration. This interface uses the line description named COTTAGEX25. When TCP/IP is started using the Start TCP/IP (STRTCP) command, the interface is automatically started. The idle virtual circuit timeout is 45 seconds. The maximum number of concurrent SVCs allowed to be used by TCP/IP on this interface is 15. This interface is connected to the Defense Data Network. You do not need to define any remote system information (RSI) entries for this X.25 network because it is a DDN network.


Example 3: Adding an Interface for a Twinax Line that is using an Associated Local Interface

ADDTCPIFC INTNETADR(¡¯199.1.1.99¡¯) LIND(TDLCLINE)
SUBNETMASK(255.255.255.0) LCLIFC(¡¯199.1.1.1¡¯)

This command will add a TCP/IP interface for the twinax line named TDLCLINE. This interface will be associated with local interface 199.1.1.1. This means that the devices attached to twinax line 199.1.1.99 can take advantage of ¡¯appearing¡¯ to be on the same network as the local 199.1.1.1 interface (transparent subnetting). No special routing is required to ensure packets from the twinax connnected hosts can travel to the local 199.1.1.0 network. Also, hosts on the 199.1.1.0 network can also reach the twinax hosts without any additional routing on the host systems.


Example 4: Adding an Interface with an Alias

ADDTCPIFC INTNETADR(¡¯123.17.5.1¡¯) LIND(ETHLINE)
SUBNETMASK(¡¯255.255.255.0¡¯)
ALIASNAME(TEST_NETWORK)

This command will add a TCP/IP interface for the Ethernet line named ETHLINE. This interface will have the alias name TEST_NETWORK. When starting or ending this interface, the alias name of TEST_NETWORK can be used in place of the IP address.