The following example shows the statements that would be added to the standard IBM TCP/IP configuration dataset PROFILE.TCPIP, when the Bus-Tech TCP controller is the only connection. In this example, we assume that two devices have been defined in the IOCP configuration as channel-to-channel adapters, with addresses 9F0 and 9F1. We assume that the network is an Ethernet "Class C" IP network, having a network IP address of 192.168.4.xxx, with 254 possible nodes. We also assume there is a router on the network with the IP address of 192.168.4.254, which knows how to reach other networks outside of 192.168.4.xxx.
..
DEVICE BTI9F0 LCS 9F0
LINK BTILINK ETHERNET 0 BTI9F0
.
HOME
192.168.4.1 BTILINK
.
GATEWAY
; Network First-hop Packet-size Subnet-mask Subnet-value
192.168.4 = BTILINK 1500 0DEFAULTNET 192.168.4.254 BTILINK DEFAULTSIZE.
START BTI9F0
The following example shows the statements (in boldface) that would be added to the standard IBM TCP/IP configuration dataset PROFILE.TCPIP, when the Bus-Tech TCP controller is being installed as an additional connection. In this example, we assume that there are 2 existing Token-Ring links, and Bus-Tech TCP controller is being added as a new Ethernet link. The new Ethernet link defines a "Class C" network having the address 198.162.4.xxx. Note that Token-Ring link TRLINK1 will still be the master link to the outside world, via its gateway router at 10.200.5.1.
DEVICE TRDEV8A0 LCS 8A0
LINK TRLINK1 IBMTR 0 TRDEV8A0
DEVICE TRDEV8C0 LCS 8C0
LINK TRLINK2 IBMTR 0 TRDEV8C0
DEVICE BTI9F0 LCS 9F0
LINK BTILINK ETHERNET 0 BTI9F0
..
HOME
10.200.5.2 TRLINK1
131.144.29.1 TRLINK2
192.168.4.1 BTILINK
.
GATEWAY
; Network First-hop Driver Packet-size Subnet-mask Subnet-value10 = TRLINK1 4000 0.255.255.0 0.200.5.0131.144 = TRLINK2 4000 0.0.255.0 0.0.29.0192.168.4 = BTILINK 1500 0DEFAULTNET 10.200.5.1 TRLINK1 DEFAULTSIZE 0.
START TRDEV8A0
START TRDEV8C0
START BTI9F0
The following example shows the statements that would be added to the standard TCP Access configuration member ACPCFG0x, when the Bus-Tech TCP controller is the only connection. In this example, we assume that two devices have been defined in the IOCP configuration as channel-to-channel adapters, with addresses 9F0 and 9F1. We assume that the network is a "Class C" IP network, on Ethernet wiring, having a network IP address of 192.168.4.xxx, with 254 possible nodes. We also assume there is a router on the network with the IP address of 192.168.4.254, which knows how to reach other networks outside of 192.168.4.xxx.
*** ICS.PARM(ACPCFG00)
*** LAN CONTROLLER DEFINITIONS SECTION
NETWORK HOST(192.168.4.2)
SUBNET(255.255.255.0)
NAME(‘Bus-Tech TCP controller’)
MSSDEF(1500)
MTU(1500)
LNID(TCPPLINK)
LNILCS CUTYPE(8232)
NAME(TCPPDEV)
DEVADDR(9F0)
LNILINK NAME(TCPPLINK)
DEVNAME(TCPPDEV)
ETHERNET
ADAPTER(0)
*** ROUTING STATEMENTS
ROUTE(0.0.0.0) DEST(192.168.4.254) NET(‘Bus-Tech TCP controller’)
ROUTE(0.0.0.0) DEST(192.168.4.254)
The following example shows the statements (in boldface) that would be added to the standard TCP Access configuration member ACPCFG0x, when the Bus-Tech TCP controller is being installed as an additional connection. In this example, we assume that there is 1 existing FDDI link, and Bus-Tech TCP controller is being added as a new Ethernet link. The new Ethernet link defines a "Class C" network having the address 198.162.4.xxx. Note that FDDILINK will still be the master link to the outside world, via its gateway router at 10.200.5.1.
*** ICS.PARM(ACPCFG00)
NETWORK HOST(10.200.5.2)
SUBNET(255.255.255.0)
NAME(‘FDDI BACKBONE’)
MSSDEF(32768)
MTU(32768)
LNID(FDDILINK)
LNILCS CUTYPE(8232)
NAME(FDDIDEV)
DEVADDR(8A0)
LNILINK NAME(FDDILINK)
DEVNAME(FDDIDEV)
FDDI
NETWORK HOST(192.168.4.2)
SUBNET(255.255.255.0)
NAME(‘Bus-Tech TCP controller’)
MSSDEF(1500)
MTU(1500)
LNID(TCPPLINK)
LNILCS CUTYPE(8232)
NAME(TCPPDEV)
DEVADDR(9F0)
LNILINK NAME(TCPPLINK)
DEVNAME(TCPPDEV)
ETHERNET
ADAPTER(0)
*** ROUTING STATEMENTS
ROUTE(0.0.0.0) DEST(10.200.5.1) NET(‘FDDI BACKBONE’)
ROUTE(0.0.0.0) DEST(192.168.4.254) NET(‘Bus-Tech TCP controller’)
ROUTE(0.0.0.0) DEST(10.200.5.1)
The following example shows a sample configuration of a single Bus-Tech MAN or ELC4VSE Ethernet controller. The configuration defines a single connection on a "Class C" network having the address 192.168.14.1, and it defines a gateway router at 192.168.14.254. This is not a complete configuration, and primarily shows the statements relevent to defining the ELC4VSE controller.
SET IPADDR = 192.168.14.1SET MASK = 255.255.255.000* Wait for VTAM Startup *WAIT VTAM* Define the Communication Links *DEFINE LINK,ID=ELCMAN,TYPE=3172,DEV=AF0,MTU=1500DEFINE ADAPTER,LINKID=ELCMMAN,NUMBER=0,TYPE=ETHERNET* Define Routine Information *DEFINE ROUTE,ID=DEFAULT,LINKID=ELCMAN,IPADDR=0.0.0.0,GATEWAY=192.168.14.254
Barnard Software TCP/IP-Tools
The following sample for a single MAN connection is a slight variation on the example for a 3172 LCS connection in the TCP/IP-Tools manual.The device address pair of AF0-AF1 is used for the channel connection.DEVICE ELCMAN LCS AF0 ETHERNET LINK ELCMAN 0 192.168.1.13 255.255.255.0 1500 ROUTE ELCMAN 192.168.1.0 255.255.255.0 0.0.0.0 * * THE FOLLOWING ROUTE INDICATES THAT TO GET TO * 192.168.1.12 WE MUST GO THROUGH 192.168.1.4 * ROUTE ELCMAN 192.168.1.12 255.255.255.255 192.168.1.4 1 * * THE FOLLOWING ROUTE IS THE DEFAULT ROUTE. * IF ALL ELSE FAILS SEND THE PACKET TO THIS DEVICE * AND TO THE SPECIFIED GATEWAY IP ADDRESS. * ROUTE ELCMAN 0.0.0.0 0.0.0.0 192.168.1.100 1 * * DEFINE THE DSN SERVERS IP ADDRESSES * THE 1ST DNS SPECIFIES PRIMARY, 2ND SECONDARY * DNS 192.168.1.2 DNS 192.168.1.3 * * HOSTS FILE DEFINITIONS * HOST JCB 192.168.1.1 HOST SERVER 192.168.1.2 HOST ROUTER 192.168.1.100