This Page will describe in a short (and hopefully fast) way how to use and connect TCP/IP in the

IOG20. Happy Pinging, FTPing, FTAMing and TELNETing towards the IOG20 over TCP/IP. For general questions about TCP/IP on IOG20 send your questions to EGS AP or check the EGS web page for contact information for the other hubs. For questions related to this page send an email to me. // Torgny

Contents: 1. General 2. Functionality 1. Function Specification 2. Command 3. FTP Session 4. Automatic File transfer using FTAM protocol over TCP/IP 3. Software Requirements 1. CN-M level 2. CN-Is 4. Hardware Requirements 5. Security 6. Installation 1. FTP Definition 2. New TCP/IP Port Installation 3. Installation of TCP/IP Port on already installed IOG20 4. Definition of FTAM Destinations 7. History

1. General
The main features of the TCP/IP is: * enable FTP access to the virtual OD-2, last HD volume (OD_A/OD_B), on the IOG. * 70 simultaneously telnet (command) sessions. * possibility to do FTAM transfer to billing centers over a TCP/IP network.
It is only possible to define one TCP/IP port ( = one IP address ) on the IOG20. The physical port is duplicated, one in each node. TCP/IP is only available on IOG20, so forget the IOG11.

2. Functionality

2.1 Function Specifications

These are the FS that describes the TCP/IP functionality in IOG20: Name: Doc. No: Authority check of operators at logon and execution of 1/155 17-ANZ 218 20 Uen Rev commands A Network Interface Management in SP Socket Interface in SP Telnet Protocol in SP File Transfer Protocol in SP AXE-I/O Transport Services on Top of the TCP LOAD TEST REPORT, ST - IOG 20 TCP/IP 103/152 83-ANZ 219 20/1 rev C 22/155 17-ANZ 216 20 Uen Rev B 26/155 17-ANZ 216 20 Uen Rev B 61/155 17-ANZ 216 20 Uen Rev B 62/155 17-ANZ 216 20 Uen Rev B 73/155 17-ANZ 216 20 Uen Rev A

2.2 Command Sessions

Command session through the TCP/IP port is set up as a standard Telnet session, by accessing different port number on the IOG20s IP address different functionality is achieved. 500x x= 1 if alarm printout is wanted to the NVT, 0=no alarm printouts. 50x0 x= 1 if a specific NVT number is wanted, question on which NVT number you want to connect to then shows up. 5x00 x= 1 if connection is wanted to the CP SB side, same functionality as a SEParated AT. Port number 5000 or 23 5001 5010 5011 5100 5101 5110 5111 Connected to CP SB side No No No No Yes Yes Yes Yes Specified NVT number No No Yes Yes No No Yes Yes Print All Alarms No Yes No Yes No Yes No Yes

For more information see the User Guide for Telnet Client in IOG Network (pdf) or ( sgml ), 1/198 17-ANZ 216 20 Here are web interfaces to the AXE that has been created by using the TCP/IP interface:

UAB I/O design in stersund's IOWEB

EUS web interface to AXE

2.3 FTP Session

File Transfer Protocol (FTP) enables the user to send or receive file(s) from the IOG to any computer with FTP capability. FTP access can only be done to OD-2. The OD-2 is a virtual OD and is in fact the last volumes on each node. When the HD is formatted the last volume is created as a single volume, OD_A in node A and OD_B in node B, the volume size of OD volume should be 2423584 Sectors for 1.3GB OD or 1241609 Sectors for 640 MB OD. It is recommended that the volume of the virtual OD is the same size as the physical OD. On the IOG20M where there is no physical OD the recommended size is 1.3 GB. The virtual OD must also be defined in the HW table as OD-2. The user can transfer single files, multiple files or a whole ODs. For more information see the User Guide for FTP Client in IOG Network (pdf) or ( sgml ), 2/198 17-ANZ 216 20 Hints: Both Username and Password must be in Capital letters, i.e. "USER1/MYPSW1" will work but "user1/mypsw1" will fail. All FTP command in small letters. When coping CP/EMRP/RP blocks to the FTP area name them on the Unix/PC machine as they should look on the IOG, main file name followed by hyphen (-) then the file name and all in Capital letters e.g. LO-LADIRECT.

2.4 Automatic File transfer using FTAM protocol over TCP/IP

All definitions for FTAM are the same for transfer over X.25 and TCP/IP. The only difference when defining a FTAM link over TCP/IP instead of a X.25 session is that when defining destination with cmd ILDNI to use parameter IPDEST instead of NTN. The IOG20 will then direct all request to the IPDEST directly out to the TCP/IP port. For more information about documents and definition see my FTAM page

3. Software Requirements
3.1 CN-M level
TCP/IP functionality is released for all IOG20s, on CNM3 level, see APZ PLM home page, both the CP and SP must be upgraded before TCP/IP functionality is available If the SP is upgraded before the CP an AC, K16LL-0287, must be loaded to ensure that IO contact remains after the function change. The reason for this is that with the new telnet functionality, NVTs, the IOG send signals to CP block NVT which is a new block in the APZ on CNM3 level.

System Information
In CME20 system this means CN-M-4 which comes in R7 CN-A-2 (R7.1) on SS side and in R8 on BSC side. If you have information about on which level other system has included CNM3 let me know and I will put a little note about it here.

3.2 CN-Is
These are the CN-Is that is required to get TCP/IP working in the IOG20, all off them are included in CN-M3.

3.2.1 CP CN-Is
The following CP CN-Is must be loaded APZ 211 11-0567 IOG SP FC Maintainability (CP) APZ 211 11-0631 Authority System adaptation and Telnet terminal in the CP APZ 211 11-0636 Preparation for common CP-dumps supporting IOG and APIO 1.0 APZ 211 11-0668 Introduction of support for AP-IO in CP For the latest ACs see MHS.

3.2.2 SP CN-Is
APZ 211 11-0605 IOG11, COMPATIBILITY RELEASE OF AXIOFTADM APZ 211 11-0610 IOG11, COMPATIBILITY RELEASE OF TRANSPORT ROUTING APZ 211 11-0615 IOG20, Telnet protocol in SP APZ 211 11-0642 IOG, FPU ADAPTATION TO SUPPORT FTAM OVER TCP/IP. APZ 211 11-0613 IOG20, Introduction of virtual optical disk function APZ 211 11-0684 "RAPID CN-I" IOG, handling of exchange data on OD-3 fails. APZ 211 11-0564 IOG SP FC MAINTAINABILITY (SP) APZ 211 11-0691 "RAPID CN-I",IOG,OD VOLUME INDEX NOT EQUAL TO OD MEDIA INDEX APZ 211 11-0698 "RAPID CN-I", IOG, COMMAND INVOE DOES NOT WORK WITH OD APZ 211 11-0622 IOG, Adaptation of AXIOFRA to SP Load Control APZ 211 11-0616 IOG, SP Load Control and Measurement APZ 211 11-0731 "RAPID CN-I", IOG, Volume information is missing

APZ 211 11-0846 FTAM initiator restart cause 80 APZ 212 20/2-90 IOG20, INTRODUCTION OF INTERNET INTERFACE. APZ 212 20/2-91 IOG20, INTRODUCTION OF INTERNET DESTINATION CONVERSION. APZ 212 20/2-92 IOG20, INTRODUCTION OF TRANSPORT ROUTING

3.2.3 SW list
Check this list to see the CP blocks and SP modules included in the above mentioned CN-Is.

4. Hardware Requirements
The new LUM board, ROJ 207 012/6, for the IOG20 is released with CNI 109 22-APZ 212 20/289. The TCP/IP (Ethernet) port is located at the top position on LUM board ROJ 207 012/6, the TCP/IP daughter board is ROF 197 4208/1, the rest of the ports on the board are V interface ports. One LUM should be placed in each node at the same position and defined as TWIN, to get redundancy. The ports will have the same NP and IP address but the LUMs have different MAC (Ethernet) addresses. At a switch over of the LUMs, B nodes LUM becomes EX instead of the A nodes or vice verse, the IOG sends out a broadcast message that the new EX LUM with MAC address x is connected to the IP address of the IOG20. The MAC addresses are fixed on the LUM boards and can not be changed. Note: It may take up 3 - 4 minutes for a swap over of port from one LUM to another due to required timeouts for the IP protocol in the Router/HUB the the IOG20 is connected to. From each port you should have one (single) cable to a HUB/Router/etc. Cables to use are: TSR 487 0215, Twisted pair, 10Base T, RJ45, or TSR 487 0213, AUI, 15 pin D-sub female connector. These cables are Single types and therefore two cables are needed per IOG20, they are available in lengths of 5 or 20 meter. Any standard router or hub can be connected by using the above described cables.

5. Security
The authority system for a TCP/IP connection is a little bit different from a standard AT connection.

When a connection is set up the authority system checks if there are any user defined in the switch, The users are set up by using OPI MCS AUTHORITY SYSTEM, USER, INITIATE 21/154 31-CNZ 218 1035. Commands to use is: IOUAP to check defined users IOUAL to define users IOUAI to initiate user in the authority system. IOUAE to deactivate user in the authority system. All OPIs regarding the authority system has a name that starts with MCS AUTHORITY SYSTEM, If a user is defined ALL person trying to log on must give USERNAME and PASSWORD, then the user can only give the commands that he/she has authority for. If there is no user defined the connection is set up directly, no request for user or password, then there is no command check/restriction and a user can give any command he/she wants. This functionality is the same for both TELNET (command) and FTP sessions. There is no check on from where the session is set up, this means that everybody within the network can connect to the switch and log in. Before this functionality is introduced the security for the TCP/IP network should be checked so it fulfils the requested security level. If not all users should have contact with the switches a firewall should be installed. If the IP network can not be completely controlled by the operator some sort of encryption should be used, this functionality is not implemented in the IOG.

6. Installation
6.1 FTP Definition
6.1.1 FTP area / OD Volume
The accessible FTP area is the last volume on the HD and it is acting as a virtual OD, if the OD area is not created only the FTP functionality will be lost, TELNET and FTAM will work without any problem. The creation of the virtual OD can only be done when formatting the HD and creating the volumes.

The size of the Virtual OD should be the same of the physical OD. For the IOG20M where there is no physical OD the recommended size is 1.3 GB. In IOG20B the OD is located on board ROJ 207 085/x, x = 1 if the OD is a 640 MB type x = 2 if the OD is a 1.3 GB type In IOG20C the OD is located on together with the HD on either board ROJ 207 077/1 for a combination of 4GB HD and OD of 640 MB type. board ROJ 207 110/1 for a combination of 18GB HD and OD of 1.3 GB type Last commands when creating the volume should be: 1. 1.3 GB Virtual OD ISVOI:VOL=OD_A,IO=HD-1,NODE=A,REV=1,SIZE=2423584,EXPDATE=202012-31,LIMIT=80; ISVOI:VOL=OD_B,IO=HD-1,NODE=B,REV=1,SIZE=2423584,EXPDATE=202012-31,LIMIT=80; 2. 640 MB Virtual OD ISVOI:VOL=OD_A,IO=HD-1,NODE=A,REV=1,SIZE=1241609,EXPDATE=2020-1231,LIMIT=80; ISVOI:VOL=OD_B,IO=HD-1,NODE=B,REV=1,SIZE=1241609,EXPDATE=2020-1231,LIMIT=80; For more information regarding volume sizes see Not linked yet

6.1.2 HW Table
The virtual ODs must be inserted into the HW Table to get them working. Also the UFILD for CONFIG-1 must match the type of IOG20 you have. Change that with cmd: IMHWC:NODE=ex node,UNIT=CONFIG-1,NAME=CONFIGURATIO,UFIELD=iog20 type,INDEX=1; IOG20 Types:

IOG20P for IOG20B-P (Parallell RP bus) IOG20P for IOG20B (Serial RP bus) IOG20P for IOG20C IOG20M for IOG20M

you can redefine them by following OPI SP HARDWARE DATA, INSERT, 4/154 31-CNA 112 189. IMLCT:SPG=x; IMHWI:NODE=A,UNIT=OD-2; IMHWI:NODE=B,UNIT=OD-2; END;

6.1.3 Device files

Device files for the virtual OD-2 must created: Commands: INMCT:SPG=x; INFII: FILE=ODxA2,IO=OD2,NODE=A,RLENGTH=512,SIZE=16,EXP=64,TYPE=SEQ,FCLASS=DEV;

INFII: FILE=ODxB2,IO=OD2,NODE=B,RLENGTH=512,SIZE=16,EXP=64,TYPE=SEQ,FCLASS=DEV; END;

6.2 New TCP/IP Port Installation

This section is for new installations where no port has been defined where the TCP/IP port is placed and the correct LUM board is installed. 1. Define System file IPROTFILEx The file is called IPROTFILEx (x=SPG) and is used to store IP addresses used in routing information: INMCT:SPG=x; INFII:FILE=IPROTFILEx,VOL=OMFZLIBORD,TYPE=KEY,FCLASS=SPL,RL ENGTH=32,SIZE=4,EXP=10, FTYPE=KEY,FSTART=3,FLENGTH=6:FTYPE=DATA,FSTART=1,FLENGTH=2 ; END; 2. Define TSAP TELNET The new TELNET TSAP is introduced to get result printouts from the CP to the NVT device. Check if the TSAP already exist. EXTDP; If it does not exist define it with: EXTDI:SPG=0,TSAP=TELNET,NODE=A&B; 3. Define LUM 1. Check if the LUM board is already defined and has the Ethernet IMLCT:SPG=x; ILLUP:LU=cm-node-lu,DETAIL; 2. If it is not already defined, define it with cmd ILLUI:LU=cm-node-lu,TWIN,CHAR=79; 3. Deblock the LU in both nodes. ILBLE:LU=cm-node-lu; ILBLE:LU=cm-node-lu; 4. Verify that both LUM has the Ethernet (TCP/IP) daughter board in the first position. ILLUP:LU=cm-node-lu,DETAIL; Remaining command are taken from OPI INTERNET PORT, INITIATE ( 53/154 31ANZ 216 20 ) For this example if the IP address for the IOG20 is 111.222.333.444 For more information regarding IP addresses for host, gateway, network and network masks see IP address info page 4. Define Port 1. ILIPI:PORT=1-1-1-1,IP="111.222.333.444"; 2. Print the port and check if the default data is good. ILNPP:PORT=1-1-1-1,DETAIL; 3. If it is not correct, change it with: ILIPC:PORT=1-1-1-1,see COD; Verify which Ethernet version you are using when defining the port. (Common problem)

4. Define default address: ILIRI:IPADDR=DEFAULT,GWY="111.222.333.1"; 5. If necessary add more routing analysis for the internet destination address: ILIRI:IPADDR="IP address",NETMASK="netmask",GWY="111.222.333.2"; 6. Print the routing analysis: ILIRP:IPADDR=ALL; 7. Deblock the port ILBLE:PORT=1-1-1-1; 5. Test the port. From a command window (PC or Unix) do: #>ping 111.222.333.444 If ping doesn't work try do an #>tracert 111.222.333.444 to see if there is any problem in the routing towards the IOG.

6.3 Installation of TCP/IP Port on already installed IOG20

This section is for installations where there is a port defined where the TCP/IP port is going to be placed. 1. Ensure that you have the correct CP software: PCORP:BLOCK=NVT; This is a new block, released with CN-I -631, and if it is in the rest of the CP blocks should be OK. If you are uncertain, check the SW record against the required CP CN-Is. 2. Ensure that you have the correct SP software: LASYP:SPG=x,VNODE=y; LASSP:SPG=x,VNODE=y,MODULE=TELNET,SYSTEM=the active system from previous command; This is a new module, released with CN-I -615, and if it is in the rest of the SP modules should be OK. If you are uncertain, check the SW record against the required SP CN-Is. 3. Check what type of LUM board is on the place where the TCP/IP LUM is going to be IMLCT:SPG=x; ILLUP:LU=cm-node-lu,DETAIL; 4. Check Port definition on the LUM ILNPP:PORT=cm-node-lu; 5. Remove any ports that are not compatible with the new LUM board, ROJ 207 012/6. First position is the Ethernet port (T interface) the other three are V interface ports (V24/V35/V36/X21) See appropriate OPI: for X.25 ports use OPI DCS Communication Using X.25 Data Link, Delete, 22/154 31-ANZ 216 20, for AT ports use OPI ALPHANUMERIC TERMINAL IN SPG, DISCONNECT, 21/154 31-CNZ 218 1001 6. Block other ports on the LUM board that is going to be changed. ILBLI:NP=cm-node-lu-np;

7. Block the LU in the SB node. ILBLI:LU=cm-node-lu; END: 8. Block the SB node. BLSNI:SPG=x,NODE=y; 9. Power off the SB node 10. Change the LUM board. 11. Power on the SB node 12. Deblock the LU in the SB node. IMLCT:SPG=x; ILBLE:LU=cm-node-lu; 13. Verify that the LUM in the SB node has the Ethernet (TCP/IP) daughter board in the first position. ILLUP:LU=cm-node-lu,DETAIL; END: 14. Deblock the SB node. BLSNE:SPG=x,NODE=y; 15. Block the EX node. BLSNI:SPG=x,NODE=y; Note: The EX node will restart, contact with the IOG will be lost for some minutes. 16. Block the LU in the SB node.(former EX) IMLCT:SPG=x; ILBLI:LU=cm-node-lu; 17. Power off the SB node (former EX) 18. Change the LUM board. 19. Power on the SB node 20. Deblock the LU in the SB node. ILBLE:LU=cm-node-lu; 21. Verify that both LUM has the Ethernet (TCP/IP) daughter board in the first position. ILLUP:LU=cm-node-lu,DETAIL; END: 22. Deblock the SB node. BLSNE:SPG=x,NODE=y; 23. Define System file IPROTFILEx The file is called IPROTFILEx (x=SPG) and is used to store IP addresses used in routing information: INMCT:SPG=0; INFII:FILE=IPROTFILE0,VOL=OMFZLIBORD,TYPE=KEY,FCLASS=SPL,RL ENGTH=32,SIZE=4,EXP=10, FTYPE=KEY,FSTART=3,FLENGTH=6:FTYPE=DATA,FSTART=1,FLENGTH=2 ; END; 24. Define TSAP TELNET Check if the TSAP already exist. EXTDP; If it does not exist define it with: EXTDI:SPG=0,TSAP=TELNET,NODE=A&B; Remaining command are taken from OPI INTERNET PORT, INITIATE ( 53/154 31ANZ 216 20 )

For this example the IP address for the IOG20 is 111.222.333.444 For more information regarding IP addresses for host, gateway, network and network masks see IP address info page 25. Define Port 1. ILIPI:PORT=1-1-1-1,IP="111.222.333.444"; 2. Print the port and check if the default data is good. ILNPP:PORT=1-1-1-1,DETAIL; 3. If it is not correct, change it with: ILIPC:PORT=1-1-1-1,see COD; Verify which Ethernet version you are using when defining the port. (Common problem) 4. Define default address: ILIRI:IPADDR=DEFAULT,GWY="111.222.333.1"; 5. If necessary add more routing analysis for the internet destination address: ILIRI:IPADDR="IP address",NETMASK="netmask",GWY="111.222.333.2"; 6. Print the routing analysis: ILIRP:IPADDR=ALL; 7. Deblock the port ILBLE:PORT=1-1-1-1; 8. Connect the cable to the port. 9. Print the status of the port, it should now be up working. ILNPP:PORT=1-1-1-1; 26. Test the port. From a command window (PC or Unix) do: #>ping 111.222.333.444 If ping doesn't work try do an #>tracert 111.222.333.444 to see if there is any problem in the routing towards the IOG.

6.4 Definition of FTAM Destinations

When definition of new FTAM destination is set up and TCP/IP is going to be used instead of an X.25 port, the destination definition with command ILDNI is given with parameter IPDEST, which is a IP address, instead of NTN (X.25 number). ILDNI:DEST=destination,IPDEST="IP address"; See OPI FTAM APPLICATION, REMOTE OSI DATA, DEFINE, 11/154 31-CRZ 216 01 For more information about FTAM definition you may also check out my (almost ready) FTAM page

7. History
Date Action: 28 September 1999 First created 1 October 1999 SW list linked

2 Mars 2000 10 April 2000 19 April 2000 20 April 2000

SW Installation information changed, new AC K16LL-0287 added. Clarified heading 2.4, spell check. Added tracert to test the port Added Doc: LOAD TEST REPORT, ST - IOG 20 TCP/IP

This page has been accessed

times since 10 March 2000