CNS 7 User's Guide. Communications. CNS 7 A2 In/On Line Tests CNS 7. Software. Subject : Special instructions : Software supported :

Transcription

1 Communications CNS 7 User's Guide CNS 7 A2 In/On Line Tests CNS 7 Software Subject : This guide tells CNP 7 network operators how to test the components of a DSA network. The CNP 7 (Communications Network Processor 7) is the fully integrated front-end processor of the DPS 7000 computer. The CNP 7 runs under the CNS 7 (Communications Network Software 7) operating system. Special instructions : Software supported : CNS 7 A2 Date : November 1992 Bull Electronics Angers S.A. Bull HN Information Systems Inc. CEDOC Publication Order Entry Atelier de reprographie FAX: (508) , Avenue Patton MA02/423S ANGERS Cedex 01 Technology Park FRANCE Billerica, MA U.S.A. 39 A2 35DN Rev01

2 Copyright Bull S.A., 1992 Bull acknowledges the rights of proprietors of trademarks mentioned herein. Suggestions and criticisms concerning the form, content, and presentation of this manual are invited. A form is provided at the end of this manual for this purpose. Bull disclaims the implied warranties of merchantability and fitness for a particular purpose and makes no express warranties except as may be stated in its written agreement with and for its customer. In no event is Bull liable to anyone for any indirect, special, or consequential damages. The information and specifications in this document are subject to change without notice. Consult your Bull Marketing Representative for product or service availability. 39 A2 35DN Rev01

3 Preface This manual has been written for the Bull DPS 7000 network operator, or the operator at the Bull DPS 7000 console, who desires to test the elements of the integrated communications processor (CNP 7) as well as elements of the OSI/DSA network to which it is connected. The ELNA (LAN) and TX25 (X.25) tests can now be run using OSI or Open systems Interconnections protocols. OSI is the network architecture model proposed by the ISO, or International Organization for Standardization based in Geneva. Each test is clearly explained and there are examples of the commands to be entered and of the system responses throughout. Complete error code information is also included. Although written primarily for the network operator, maintenance personnel will also find this manual useful when analysing error information and verifying corrective action. The first section is an introduction giving general information about all the tests including a guide that indicates which test to use depending on the real or suspected problem. The second section describes the tests supervisor program giving the commands used by the operator to run the tests. There is a separate section devoted to each test. The sections are in the alphabetical order of the names of the tests. At the end of each test section there is an example. Each test section is organized in the following way: 1. An explanation of the purpose of the test, 2. A graphic presentation of the test, 3. An explanation of the operator commands and procedures to run the test, 4. An explanation of test results and how errors are indicated, 5. An example of the test. 39 A2 35DN Rev01 iii

4 CNS 7 A2 In/On Line Tests The following conventions and symbols are used in this manual: Square brackets [ ] indicate an optional entry. Round brackets ( ) enclose something given for information only. Braces { } enclose items from which you must make a choice. The valid choices are separated by vertical lines. Lower case letters, most often enclosed by angular brackets <>, provide the description of a variable whose exact value should be provided by the operator or the system, for example: <test name>. Uppercase letters indicate commands or parameters that must be reproduced exactly as shown, for example:??ex TL ELNA. Decimal values can be indicated with a lowercase letter v. Hexadecimal values can be indicated with a lowercase h. MANUAL DIRECTORY The following list gives the titles and order numbers of manuals related to the CNS 7 A2 In/On-Line Tests Manual: CNS 7 A2 - Documentation Directory A4 30DN CNS 7 A2 - SRB A4 31DN CNS 7 A2 - NGL Reference Manual A2 32DN CNS 7 A2 - Terminal Management A2 33DN CNS 7 A2 - NOI Operator Guide A2 34DN CNS 7 A2 In/On-Line Tests A2 35DN FPG 7 - Simple Generation Guide A2 46DM DNS V4 - Concepts A4 20DN DNS V4 - System Generation A2 22DN OSI/DSA Network Systems Messages and Return Codes A2 26DM Complementary manuals are listed in the following documentation directories: DNS Documentation Directory A4 27DN Bull Datanet - Documentation Directory...39 A DSA Documentation Directory...39 A Bull Datanet, Bull CpNet and DNS Documentation Directory...39 A DPS7 GCOS Bibliography A2 02UG The manuals listed above may be ordered from the following address: Bull Electronics Angers S.A. CEDOC Atelier de reprographie 331, Avenue Patton ANGERS Cedex 01 FRANCE Bull HN Information Systems Inc. Publication Order Entry FAX: (508) MA02/423S Technology Park Billerica, MA U.S.A. iv 39 A2 35DN Rev01

5 Table of Contents 1. Introduction and Guide INTRODUCTION TEST ENVIRONMENT OSI/DSA Objects Administrative Components Network Configuration Elements of an OSI/DSA Network Running the In and On Line Tests NOI Connection from the Network Operator Terminal NOI Connection from the DPS 7000 Operator Console Network Control Language (NCL); Commands Returning Network to Original Status Disconnection After Using Tests THE TESTS Functional Description The In Line Tests The On Line Tests The Tests and Network Elements Tested WHICH TEST DO I NEED? A2 35DN Rev01 v

6 CNS 7 A2 In/On Line Tests 2. The Tests Supervisor INTRODUCTION THE EXECUTION COMMAND (EX TL) General Response Formats CNS 7 Administration Tests Supervisor Response Format Options Common to all the Tests The Options by Default EX TL Command With Option Possibilities Common to All Tests Examples of EX TL TEST ATTRIBUTES AND OPERATOR HELP (DA TL - GA TL) Test Attributes Operator Help TEST HISTORY REPORT (GH TL) GH TL Execution The Error and Reason Codes OPERATOR RESPONSE COMMAND (TX TL) TX TL Execution Response Formats TX TL Example MODIFICATION OF TEST OPTIONS (UP TL) Command Syntax Options That Can be Modified Response Formats Example Showing Use of UP TL TEST CLOSE COMMAND (CL TL) CL TL Execution Response Formats vi 39 A2 35DN Rev01

7 Table of Contents 2.8 TEST TERMINATIONS The End of Test Message Error Codes Fatal Errors CNS 7 Administration (* REJECT B) Error Codes Errors Concerning Specific Tests The Basic Network Session Exerciser Tests (BNSE1&2) PURPOSE DIAGRAM PROCEDURES Getting Ready Running BNSE1& TEST RESULTS Normal Ending - No Errors Errors are Detected Error Codes EXAMPLES Echo Mode CNP 7 calls the DPS CNP 7 calls another CNP CNP 7 calls a Bull Datanet Drop Mode From CNP 7 to a DPS From CNP 7 to another CNP From CNP 7 to a Bull Datanet A2 35DN Rev01 vii

8 CNS 7 A2 In/On Line Tests 4. The Terminal On Line Test (ECHO) PURPOSE DIAGRAM PROCEDURES Getting Ready Running ECHO EXAMPLES In Default Mode Terminal Operator Enters Characters The Local Area Network On Line Tests (ELNA1&2) PURPOSE DIAGRAM PROCEDURES General The Physical Lines Test Execution Command Test Options RESULTS Test Terminations Error Codes EXAMPLES ELNA1 with All Correspondents and 100 Iterations ELNA2 with One Distant Correspondent (PLR3) ELNA2 with One Distant Correspondent (PLR1) and an Error ELNA2 with All Correspondents viii 39 A2 35DN Rev01

9 Table of Contents 6. The Local Area Network Connections Tests (RLNA1&2) PURPOSE DIAGRAM PROCEDURES General Getting Ready Test Execution Command Test Options RESULTS No Errors Errors Are Detected Error Codes EXAMPLE The Local Area Network Status Test (SLNA) PURPOSE DIAGRAM PROCEDURES General The Physical Lines Test Execution Command RESULTS General Status Information Address Information and Test Terminations Error Codes A2 35DN Rev01 ix

10 CNS 7 A2 In/On Line Tests 7.5 EXAMPLES Status Test Using the PL CSM1 Named PLR Status Test with an Error Using the PL CSM1 Named PLR Status Test Using All the Known PL CSM The Network Operator Terminals Test (TDEV) PURPOSE DIAGRAM PROCEDURES General The Execution Command RESULTS At the Terminal At the Network Operator Terminal The Error Codes EXAMPLES Logical Disconnection of Terminal to be Tested Starting TDEV at the Network Operator Terminal Receipt of the Test Lines at the Terminal Being Tested Communication Lines Tests (TPL1,2&3) PURPOSE DIAGRAM PROCEDURES General DA CT and DA PL to Verify the PL Object TPL1, 2&3 Test Commands Test Options x 39 A2 35DN Rev01

11 Table of Contents 9.4 RESULTS No Errors Errors are Detected Error Codes EXAMPLES X.25 Network Tests (TX251,TX252,TX253 & TX254) PURPOSE DIAGRAM PROCEDURES Organization of the TX25 Tests X.25 Tests Organization Table Test Modes and Commands for the Three Test Loops Test Options Test Execution Operator Responses DSA addressing OSI addressing Closed User Group RESULTS Test Endings Error Codes EXAMPLES The Self-Calling Loop The Remote Subscriber Loop The Dummy Subscriber Loop A2 35DN Rev01 xi

12 CNS 7 A2 In/On Line Tests Appendix A. Abbreviations List... A-1 Index... i-1 xii 39 A2 35DN Rev01

13 Table of Contents Illustrations Figures 1-1 An OSI/DSA Network through a CNP In and On Line Tests Environment Terminals, Synchronous Lines and HDLC Lines X.25 Networking Local Area Network and ISL Connections Tests of the Logical Connections at Session Level (BNSE1&2) The BNSE1&2 Tests The ECHO Test The ELNA Test Testing the Local Area Network Connections The SLNA Local Area Network Test The TDEV Terminal Logical Connection Test The TPL1, TPL2 and TPL3 In Line Tests of DCA, DCE, DCB, DCBE and MLNA Controllers Testing an X.25 Network from the CNP A2 35DN Rev01 xiii

14 CNS 7 A2 In/On Line Tests xiv 39 A2 35DN Rev01

15 1. Introduction and Guide 1.1 INTRODUCTION The In and On Line Tests verify the functioning of the Communications Network Processor 7 (CNP 7), which is the communications processor integrated in the cabinet of the Bull DPS 7000 computer. They test the functioning of the major components of the processor itself, as well as the connections linking it to other network components. The CNP 7 has its own operating system software called Communications Network Software 7 (CNS 7). The In/On-Line Tests described in this manual run under this CNS 7 operating system. These tests are similar to the In and On Line Tests that are run from the Bull Datanet and the Bull CpNet network processors under the DNS operating system. Since CNS 7 and DNS are compatible under Bull's Open Systems Interconnection / Distributed Systems Architecture (OSI/DSA), this similarity facilitates maintenance throughout a OSI/DSA network. The tests are run by the Bull DPS 7000 network operator. They should be used whenever there is a problem within the network or even if you only suspect a problem. This section gives a general overview of each test, the test environment and provides an illustrated guide for choosing and running the tests that you need. In Line or On Line? An IN LINE TEST requires the exclusive use of at least one hardware or software component. Before testing takes place, some of the objects may need to be suspended (or locked) from any networking activity during the test. 39 A2 35DN Rev01 1-1

16 CNS 7 A2 In/On Line Tests The following are In Line Tests: ECHO RLNA1 RLNA2 TDEV TPL1 TPL2 TPL3 An ON LINE TEST requires the object or objects to be at least ready for use in the network. Some of these objects, depending on the level of network connections at which it is acting, should be in use during the test. The On Line Tests are: BNSE1 BNSE2 ELNA1 ELNA2 SLNA TX251 TX252 TX253 TX A2 35DN Rev01

17 Introduction and Guide 1.2 TEST ENVIRONMENT OSI/DSA Objects OSI/DSA objects and their relationships in CNS are described in the CNS 7 A2 - NOI Operator Guide to which you should refer. In particular, the following objects are of interest here, as they are those which are involved in the testing: MB (Mailbox), NR (Network Route), NS (Network Subscription), PL (Physical Line) Administrative Components The following are administrative components under CNS in the tests environment: NOI: NAD: The Network Operator Interface,NOI, connects the operator to the NAD. The Node ADministrator. The NAD provides interface between the NOI and the test task. It receives the execution command from the operator, controls execution and provides the results Network Configuration There are some special considerations concerning the tests, that must be taken into account when configuring the network. The following CNS 7 generation directives are necessary to allow the system to use the tests. AC - for NAD connection to the NOI, AF - for NAD connection to the NOI, AG - for connection to the NOI, OP - for connection to the NOI, MB - for application and/or terminal location. 39 A2 35DN Rev01 1-3

18 CNS 7 A2 In/On Line Tests Note: Concerning the OP directive, it may be necessary to raise the test operator's Messages Threshold if test messages are lost. For example you can use the following command: UP OP TEST -THR 100 The NOI must be configured with an associated OP directive to enable network administration and control of the tests. The NAD in the node which will execute the tests, must be configured to receive the NOI connection. To do this, the CNS 7 configuration file must contain: AF NOI, AC NOI, AF NAD and AC NAD. This is an example of the specific generation directives used in the CNS 7 generation to configure the mailboxes used by the In and On Line Tests: MB $NSE USER -CNX VSEQY -NO_SES MB $NSF USER -CNX VSEQX -NO_SES MB $ECHO USER -CNX VSEQO For further information, refer to the CNS 7 A2 - NGL Reference Manual. For the TPL2 communications lines test, a physical loop-back plug must be used. The following Bull order numbers are for the plugs needed for the different electrical connection types. Electrical Interface: Bulkhead Plug V.24/V.28 X.24/V.11 V.24/V Electrical Interface: Cable Plug V.24/V.28 X.24/V A2 35DN Rev01

19 Introduction and Guide Elements of an OSI/DSA Network This diagram shows how various elements of an OSI/DSA Network can be connected through the CNP 7 integrated front end processor of a Bull DPS 7000 computer. Bull DPS 7000 SPA DPS 7000 Operator's console CNP7 ISL GCU2F D C A T L N A S P I L N A L N A T D C E D C B L A N E-LAN StarLAN LAN Station DSA System M M M M DSA or X.25 NETWORK ASYNCHRONOUS SYNCHRONOUS HDLC X.21 (DCBE only) M: Modem T: Transceiver DSA System Figure 1-1. An OSI/DSA Network through a CNP 7 39 A2 35DN Rev01 1-5

20 CNS 7 A2 In/On Line Tests Running the In and On Line Tests The In and On Line Tests are resident in the CNS 7 operating system software. The tests software consists of a tests supervisor program and the individual tests. The supervisor controls the tests, as explained in detail in Section 2. The tests are normally run from any terminal in the network that can connect to the node where the tests are located. They can also be run by the Bull DPS 7000 operator required under the Enter DSA Dialogue Facility (EDD) of the GCOS 7 V.3 operating system. The operator can test an object located on another node by including the -AT option in the test execution command, as explained in Section 2. The operator must connect to the NOI before commands can be sent or messages received. The procedures for connection to the NOI are slightly different for the network operator's terminal connected directly to the CNP 7 and for the DPS 7000 operator's console NOI Connection from the Network Operator Terminal Any terminal in the network that can connect to the NOI can be the Network Operator Terminal. The connection command is as follows: $*$CN -DMB $NOI -SC <node name> [-PW <password>] (cr) Note: A password is normally used for network operator identification. Many operators find it easier to set up a substitute connection procedure using the CO correspondent directive in the system generation. This allows the operator to connect using an easily remembered name which automatically defines all the appropriate connection parameters. In which case, the connection command could look like this: $*$CN NOI (cr) The system responds with: $$ 0100 YOU ARE CONNECTED TO $NOI <node name> SESSION: <number> Notes: 1. (cr) represents the Carriage Return/Enter/Return/Transmit key which must always be pressed at the end of a command line, to send the command. In the rest of this manual, this notation has been omitted. 2. The secondary dialogue implicit command prompt ($*$) is sent by the Terminal Manager. To display it on an asynchronous terminal, press CTL and W simultaneously. On a synchronous terminal, type $*$. However, these procedures may vary from site to site, depending on the system generation. 3. The $$ is the default secondary dialogue messages prompt. It appears before each local dialogue message A2 35DN Rev01

21 Introduction and Guide In order to display the NOI prompt (?? ), press the CTL and A keys simultaneously, or Break on an asynchronous terminal, or type $*$BRK on a synchronous terminal. Before typing a test command, the NOI prompt must be displayed. You are now ready to use the commands of the Tests Supervisor which run and control the In and On Line Tests. These commands are described in detail in Section NOI Connection from the DPS 7000 Operator Console The DPS 7000 operator working under the GCOS 7 operating system has a special facility to be able to operate with the networking software. This is called the Enter DSA Dialogue (EDD) facility. It is used in the following way: First, obtain the system prompt (S:) by pressing the Break key. Then type the EDD Start command (ST) shown below: S: EDD ST This is an example of the system's answer: X5396 IN ADM_EDD OP1 P SPR=7 MAIN X5396 STARTED ADM_EDD OP1 P Next, you have to connect to the NOI. There are several ways to do this. In the following example, the System Help Facility (?) is used to display additional comments after each entry. The command to enter the System Help Facility is: S: EDD? The system then asks a series of questions. An answer or "carriage return" is required after each colon (:). ENTER_DSA_DIALOG COMMAND : (cr) FE41 FECM STARTED FOR ENTER DSA DIALOG RSYS remote system : <node name of CNP 7> (from DSA generation) APPL $NOI $DEBUG : (cr) SETDFLT set RSYS and APPL default values : (cr) CONNECT connect to DNS or CNS system : 1 (1=yes under GCOS 7) PASSWORD mandatory with CONNECT : <password> DISCONNECT disconnect from DNS or CNS system : ; The EDD? help facility would continue to send a series of parameters and comments. The ";" entered by the operator at this point stops the EDD help dialogue, since it is no longer needed. An example of the system answer is: FE45 BC92 $NOI CONNECTION IS ESTABLISHED 39 A2 35DN Rev01 1-7

22 CNS 7 A2 In/On Line Tests You are now ready to use the CNS 7 commands of the Tests Supervisor which run and control the In and On Line Tests. These commands are described in detail in Section 2. They are entered after EDD and a space, and they are enclosed by single quotes. The syntax looks like this: S: EDD 'EX TL xxxx -OBJ xx:yyyy' To exit the EDD, the DPS 7000 operator enters this command: S: EDD TT An example of the system answer might be: FE42 FECM COMPLETED FOR ENTER_DSA_DIALOG OU10 RO 3 OUTPUTS RELEASED X COMPLETED ADM_EDD OP1 P Network Control Language (NCL); Commands A complete description of the CNS 7 NCL commands can be found in the CNS 7 A2 - NOI Operator Guide. Certain NCL commands are used for the In and On Line Tests, such as: DA CT GA PL UP PL Display Attributes of controller objects, Get (display) Attributes of physical line objects, Change (update) the state of a physical line object. The sections covering the individual tests explain where these commands are needed and give examples. The -AT parameter can be used to make the command execute at a named node, rather than at the default node. The default node is the one at which the operator is connected to the NOI. This is explained more in Section A2 35DN Rev01

23 Introduction and Guide Returning Network to Original Status IMPORTANT The operator must be careful to release any objects that have been locked for testing. Otherwise, these objects remain locked and can cripple the network. The objects can be released with this command:??up PL <xxxx> -ST ENBL Where: UP PL xxxx -ST ENBL Update (change) Physical Line Object Name Status Enable Disconnection After Using Tests After completing the tests, the network operator can disconnect the terminal manager from the NOI using the DIS local dialogue command (or DIS HOLD). The sequence looks like this: $*$DIS The system then answers: $$ 0200 YOU ARE DISCONNECTED:0301 Where: $$ Prompt 0200 Local Message Type YOU ARE DISCONNECTED Operator Message 0301 Normal Response to the DIS Command 39 A2 35DN Rev01 1-9

24 CNS 7 A2 In/On Line Tests 1.3 THE TESTS The figure below shows how the elements in a network relate to the In and On Line Tests and the operator interface to the tests via the NOI. Concentrator Terminals NIM Terminals CMSA/CD LAN (E-LAN Start LAN) LAN Station System FEP DSA HOST Bull DPS 7000 CNP 7 NOINAD T E S T S Synchronous/ Asynchronous Switched Network Gateway DUAL LAN SWITCH Terminals Terminals WAN(HDLC/X.21) LAN(CSMA/CD) System HDLC/X.21 Cluster Controller Synchronous Terminals WAN X.25 HDLC/X.21 PAD(PDN only) Concentrator Gateway Asynchronous CSMA/CD Terminals Terminals LAN FEP DSA HOS X.25 SWITCH WAN Figure 1-2. In and On Line Tests Environment A2 35DN Rev01

25 Introduction and Guide Functional Description The In Line Tests The In Line Tests can be used to pin-point malfunctions in adapters, controllers, lines, and so on. The elements being tested must be temporarily suspended from any network activity while the tests are running. The following are In Line Tests: ECHO Run by a terminal operator, ECHO tests a terminal's ability to receive ASCII characters sent from the CNP 7, as well as characters sent from the terminal and echoed back to the terminal from the CNP 7. RLNA1&2 These tests verify the functioning of the physical link between the LNA and the Local Area Network (a LAN can be an E-LAN or a StarLAN). Data frames are sent, then received and compared. The RLNA1 test is an internal check on the controller. RLNA2 checks the link to the LAN (up to the transceiver for an E-LAN or the top level HUB for a StarLAN). TDEV TDEV tests the connection up to the session layer, of a terminal or its mailbox. The terminals can be: synchronous, asynchronous, synchronous VIP, BSC 3270, and Minitel. TPL1,2&3 These tests verify the functioning of the lines associated with DCA, DCE, DCB, DCBE and MLNA (on the LNA board) controllers, for synchronous, asynchronous or HDLC connections. They also verify the functioning of the X.21 lines associated with DCBE controllers. TPL1 performs a check on an internal logical loop-back of the controller line. TPL2 performs this internal check followed by a check up to a loop-back plug installed on the bulkhead or at the cable end. In a similar way, TPL3 performs the internal check followed by a check of the connection up to a loop-back at the local modem (loop-back switch 3) or at the remote modem (loop-back switch 2). Data frames are sent, received and compared in the transmission mode used at the site concerned. In the special case of an X.21 line test, the test is executed in synchronous and HDLC mode. 39 A2 35DN Rev

26 CNS 7 A2 In/On Line Tests The On Line Tests The On Line Tests are used to find malfunctions within the OSI/DSA software layers and to check the overall functioning of a network substructure. You run these tests when the network is functioning as normal, therefore you do not need to lock or disconnect the elements being tested. The following are On Line Tests: BNSE1&2 The BNSE tests verify the logical connections at session level between two OSI/DSA systems or locally within a CNP 7. ELNA1&2 This test sends data to stations or systems on the LAN or to the DPS 7000 Service Processor (SPA) through the Inter System Link (ISL). The data is echoed back and compared with the original. ELNA1 is a regular flow test and ELNA2 is a fast flow test. SLNA This test requests and receives status information from the Service Processor and all the stations or systems on the LAN. However, you can specify just one station/system from which to collect information. TX251,2,3&4 These tests check the operation of CNP 7 at the network level and lower layers through public or private X.25 networks. They transmit, receive and compare data in three modes: 1. Self Calling Loop through the X.25 network. 2. Dummy Subscriber Loop in the X.25 public data network. 3. Remote Subscriber Loop through the X.25 network A2 35DN Rev01

27 Introduction and Guide The Tests and Network Elements Tested TEST BNSE1&2 ELEMENTS TESTED Logical Connections at session level. ECHO Any terminal connections to CNP 7. ELNA1&2 CNP 7 physical links to the stations or systems on the LAN with an Echo response. SPA connection through the ISL. RLNA1 RLNA2 SLNA TDEV TPL1 TPL2 TPL3 The CNP 7 LAN Controllers. The CNP 7 LAN Controllers. The LAN (E-LAN transceiver or StarLAN HUB) or ISL cable transceiver. CNP 7 physical links to the stations or systems on the LAN with a Status Response. SPA Connection through the ISL with a Status Response. CNP 7 connection to any terminal in the Network. Any CNP 7 communication line internally (DCA, DCE, DCB, DCBE & MLNA). Any CNP 7 communication line internally and up to the bulkhead/ cable end (DCA, DCE, DCB, DCBE & MLNA). Any CNP 7 communication line internally and up to, either a local or a remote modem (DCA, DCE, DCB, DCBE & MLNA). TX251 The X.25 networking operation of any CNP 7. TX252 TX253 TX254 The X.25 networking operation of any CNP 7 in Simultaneous Automatic Mode. The X.25 networking operation of any CNP 7 in Alternating Conversational Mode. The X.25 networking operation of any CNP 7 in Simultaneous Conversational Mode. 39 A2 35DN Rev

28 CNS 7 A2 In/On Line Tests 1.4 WHICH TEST DO I NEED? The following pages provide an illustrated guide to the tests. This table shows where to look for the illustration of the test that you need: If you have to check See Figure Synchronous, Asynchronous or HDLC lines 1-3 See Section 9: Communications Lines Tests (TPL1,2&3) Terminals;connections at session level 1-3 See Section 4: Terminal On Line Test (ECHO) See Section 8: Network Operator Terminals Test (TDEV) X.25 Networking 1-4 See Section 10: X.25 Network Tests (TX251, TX252, TX253 & TX254) Local Area Network (LAN); physical links and Inter 1-5 System Link (ISL) See Section 5: Local Area Network On Line Tests (ELNA 1&2) See Section 6: Local Area Network Connections Tests (RLNA 1&2) See Section 7: Local Area Network Status Test (SLNA) Session Level Logical Connections to systems 1-6 See Section 3: Basic Network Session Exerciser Tests (BNSE 1&2) A2 35DN Rev01

29 Introduction and Guide Network Operator's Console Bull DPS 7000 CNP7 ECHO Test Terminal Tests TDEV Test TPL TPL1 TPL2 TPL3 TPL3 Tests M M Line Tests SW3 SW2 TPL2 TPL2 Line: SYN ASYN HDLC M:Modem SW 3: Modem in loopback switch 3 SW 2: Modem in loopback switch 2 (or switch appropriate to your modem) (or switch appropriate to your modem) Figure 1-3. Terminals, Synchronous Lines and HDLC Lines 39 A2 35DN Rev

30 CNS 7 A2 In/On Line Tests Network Operator's Terminal Bull DPS 7000 CNP7 A B C X.25 Network Dummy* Subscriber Remote Subscriber The TX25 1, 2, 3, and 4 Test : A. Self Calling Loop B. Dummy Subscriber Loop C. Subscriber Loop * A Dummy Subscriber may or may not exist in your X.25 Network Figure 1-4. X.25 Networking A2 35DN Rev01

31 Introduction and Guide RLNA1 Test: ELNA1&2 Tests: SLNA Test: 1 RLNA2 Test: Echo Request Status Request 1 2 Echo Response Status Response Bull DPS 7000 Service Processor L N A L A N T C A B L E E-LAN E-LAN Station or system 1 Network Operator's console CNP7 1 T 2 L N A T L N A ISL L N A T T E-LAN Station or system n H H StarLAN Station or system 1 T : Transceiver H : HUB LNA : Local Network Adapter 2 H StarLAN StarLAN Station or system n Figure 1-5. Local Area Network and ISL Connections 39 A2 35DN Rev

32 CNS 7 A2 In/On Line Tests Bull DPS 7000 CNP 7 (CNS 7) Bull Datanet CpNet (DNS) Bull DPS 7000 Bull xxxxx Initiation CNP 7 (CNS 7) SESSION LEVEL CONNECTION DPS 7/7000 (GCOS 7) Bull xxxxx Figure 1-6. Tests of the Logical Connections at Session Level (BNSE1&2) A2 35DN Rev01

33 2. The Tests Supervisor 2.1 INTRODUCTION The In and On Line Tests Supervisor Program is an integral part of the CNS 7 operating system. It controls the execution of the tests and communications with the operator. The Supervisor commands, listed below, are explained in this section. Command CL TL DA TL EX TL GA TL GH TL TX TL UP TL Function Abort or close the test that is running. Display the In/On Line Test attributes or operator help (same effect as GA TL). Execute In/On Line Test. Get the In/On Line Test attributes or operator help (same effect as DA TL). Get the In/On Line Test history. Operator response command. Update or change an In/On Line Test option. Command syntax error codes are explained in the CNS 7 A2 - NOI Operator Guide. Note: Before typing a test command, always obtain the NOI prompt as explained in Section A2 35DN Rev01 2-1

34 CNS 7 A2 In/On Line Tests The -AT administrative parameter, followed by a space and the name of a node, can be entered by the operator after any command. This will make that command execute at the named node rather than at the node at which the operator is connected to the NOI, as would normally be the case. Note that the named node must already be connected to the NOI. Example:?? CL TL -AT <node name> This command will abort the test which is running at the named node. The above command must be entered using the same NOI connection as that where the original execution command (EX TL) was entered. This implies that in the example above, the execution command would also have used the -AT parameter to enable the test to be running at that node A2 35DN Rev01

35 The Tests Supervisor 2.2 THE EXECUTION COMMAND (EX TL) General The EX TL command is used to execute a test. You can add optional parameters to tailor the test to your own requirements. To enter the execution command, the operator needs: the test name, the name and the class of the object to be tested, any options to be applied to the test sequence. The test execution command EX TL is followed by the test name, the -OBJ designation, and the object type and class. Any options that are required are listed at the end. Each of these is separated by a space, as shown below:??ex TL <xxxx> -OBJ <yy:zzzz> [-options] Where:?? NOI Prompt (not typed by operator) EX TL xxxx -OBJ yy zzzz In/On Line Test Execution Command Test Name Object Object Class (two alphabetic characters) Object Name -options See options paragraph in Notes: 1. The supervisor runs one test at a time. 2. The test name and the object can not be modified during the test. 3. If the object to be tested is supposed to be locked, but the operator has omitted to do so, the test supervisor displays the following message: CNS NNNN HH:MM:SS TX TL PLEASE LOCK <yy:zzzz> FOR <xxxx> TEST 39 A2 35DN Rev01 2-3

36 CNS 7 A2 In/On Line Tests Where: CNS NNNN HH:MM:SS TX TL PLEASE LOCK yy: zzzz xxxx Communications Network Software Node Name Hours, Minutes, Seconds Text In and On Line Tests Message to the Operator Object Type Object Name Test Name To continue with the test execution, you must lock the object. To do this, use the UP command as follows: UP <object name> -ST LOCK Once the object has been locked, the test will commence. If however you prefer to cancel the test execution at this stage, you can do so by using the CL TL command, which is explained later in this section. The test will be cancelled and an end of test message displayed. If there is no reply to the test supervisor prompt as above, the message is repeated three times at 30 second intervals. If there continues to be no response from the operator, the test supervisor displays the following message: CNS NNNN HH:MM:SS TX TL END <xxxx> <yy:zzzz> EOT / FATAL 06 where FATAL 06 is the reason code which indicates that the selected object has not been locked. Where appropriate, this manual explains how to lock a test object A2 35DN Rev01

37 The Tests Supervisor Response Formats In general, there are two types of response format, one is from the CNS 7 operating system administration and the other from the tests supervisor CNS 7 Administration If the command is correct, the response is: CNS NNNN HH:MM:SS TL TID TNM OBJ RPRT 0 <xxxx> <yy:zzzz> 14/00 Where: xxxx yy:zzzz RPRT Name of the Test Object Class and Name Report ( 14 = tests, 00 = command has been accepted) If the command is incorrect the response is: * REJECT B REASON = 14/x (x = refusal code) (B = Before processing) The refusal codes are as follows: 01 Generation Error 02 Command Not Supported 03 Test Already Running 04 Test Name Not Found 07 Bad Class or Object For This Test 08 No Test Running 0C 0D 0E Buffer Space Error Test Not Started Test Already Ending 10 Bad Option 11 Object Not Being Tested 12 No Test Dialogue 39 A2 35DN Rev01 2-5

38 CNS 7 A2 In/On Line Tests 13 Bad Class or Object 15 Originator Reject 16 Bad Test Selection 17 Text Format Reject 18 Text Length is Null 19 Bad Network Node 20 No Test Started 21 Syntax Error 24 Object in SPARE Status 25 Help in Progress F0 Parameter Error The OSI/DSA Network Systems Messages and Return Codes Manual contains more information about these codes Tests Supervisor Response Format CNS NNNN HH:MM:SS TX TL EX TL <xxxx> <yy:zzzz> <report> The report can be: BUILD TASK ERROR WRONG RELEASE STARTED REL X.YY (This means the test has started, where X.YY is the release number of the test. For the CNS A2 release, X.YY is 2.00, meaning CNS version A2 and internal test release 00.) After this message, the UP TL and CL TL commands can be used, otherwise, they are rejected as follows: * REJECT B REASON 14/ A2 35DN Rev01

39 The Tests Supervisor Options Common to all the Tests These options determine how the test is to be run and how any errors should be reported. These options apply to all the tests. The operator enters the desired options at the end of the test execution command (EX TL) line. Once entered, options may be modified with the UP TL command, which is explained later. -DLY<hh:mm:ss> This option is used to specify the duration of the test. The maximum possible duration is 9 hours, 6 minutes and 6 seconds. The -DLY default value is 30 minutes. This option can be used with the -RPT option, which specifies the number of times the test is to be repeated. These options are particularly useful in locating intermittent failures. See the table at the end of this paragraph for a more detailed explanation of the relation between -DLY and -RPT. -ERR {D S N} This option governs the information that is provided for the operator when errors are detected. It is followed by a space and a parameter (D, S or N). These are explained below: D This displays detailed error information at the occurrence of each error, during the test. You should use this parameter with the -NHLT, -DLY and -RPT options. An example of the error information that is displayed is: CNS NNNN HH:MM:SS TX TL <xxxx> <yy:zzzz> NRPT:<u> ERR:<v> Where: xxxx yy:zzzz u v S Test Name Object Type and Name Number of Test Repetitions Error Code Value This displays error statistics which have been collected during the test. You should use this parameter with -NHLT, -DLY and -RPT options. They are displayed at the end of the test, in the form below: CNS NNNN HH:MM:SS TX TL <xxxx> <yy:zzzz> NRPT NERR ERR CNS NNNN HH:MM:SS TX TL u v w CNS NNNN HH:MM:SS TX TL r s t 39 A2 35DN Rev01 2-7

40 CNS 7 A2 In/On Line Tests Where: xxxx Test Name yy:zzzz Object Type and Name NRPT Number of Times Test Repeated (u, r) NERR ERR Error Code (w, t) N Number of Errors Detected (v, s) which are identified with error code w and t. No error listing is displayed during the test, but if any errors have occurred a single error code will be displayed at the end of the test. This is the default parameter associated with the -ERR option. You should use it when you are using the other default options. -HLT -NHLT -RPT This is the default option. It stops the test when an error is encountered. The test continues to run until a fatal error occurs. Other errors do not cause the test to stop. This option should be followed by a space and a number, to define how many times the test is to be repeated. The maximum number of repetitions is and the default value is 1. It can be used with the -DLY option. The table on the next page explains the relationships between -DLY and - RPT. The relationship between -DLY and -RPT: -DLY -RPT EXECUTION none none Y Y none X none X The test uses the default values of one test cycle and a maximum duration of 30 minutes; the test stops after completing one cycle or when it reaches the maximum duration. X test cycles and a maximum duration of 9 hrs, 6 min and 6 sec; the test stops at the end of the maximum duration or when it has repeated the test X times, whichever occurs first. The test runs as many cycles as it can in the duration Y. The test stops either when the duration Y is reached or if the test is repeated the maximum number of times (65535), whichever occurs first. The test runs for X cycles and for a duration of Y, stopping at either X or Y, whichever occurs first A2 35DN Rev01

41 The Tests Supervisor The Options by Default If the operator enters only the default options, the test runs under the following default conditions: 1. Execution does not exceed 30 minutes (-DLY 00:30:00). 2. The test stops on the first error (-HLT). 3. No error report is provided during the test. If an error has occurred during the test, a single error code is displayed at the end of the test (-ERR N). 4. The test runs only once (-RPT 1) EX TL Command With Option Possibilities Common to All Tests The following is an example of the execution command when all the common options are used:??ex TL <xxxx> -OBJ <yy:zzzz> [-DLY hh:mm:ss] [-RPT n] [ {-HLT -NHLT} ] [-ERR {D S N} ] [-AT <name>] Note: The specific options that apply to each test are described together with the test concerned. These are: -OBJ2, when a second object is required, -DATL, to change data frame length, -VAL, to change the data frame content. 39 A2 35DN Rev01 2-9

42 CNS 7 A2 In/On Line Tests Examples of EX TL The following examples of the test execution command illustrate the use of different option combinations. They indicate the type of test execution that can be particularly useful to isolate intermittent failures. Example 1:??EX TL TPL1 -OBJ PL:PLS1 -ERR D -RPT 100 -NHLT Where: EX TL TPL1 -OBJ PL:PLS1 -ERR D -RPT 100 -NHLT Execute the TPL1 test PLS1 is the object to be tested Output detailed information when an error occurs Run (repeat) TPL1 one hundred times Do not stop the test when a non fatal error occurs Example 2:??EX TL TPL1 -OBJ PL:PLS1 -ERR S -RPT 35 -DLY 00:10:00 -NHLT Where: EX TL TPL1 -OBJ PL:PLS1 -ERR S -RPT -DLY -NHLT Execute the TPL1 test PLS1 is the object to be tested Display error statistics Run (repeat) TPL1 35 times The duration of the test is 10 minutes. However, in this example, the -RPT and -DLY are used together. The test will stop on whichever occurs first, the repetition of 35 tests or the time limit of 10 minutes. Do not stop the test when a non fatal error occurs A2 35DN Rev01

43 The Tests Supervisor 2.3 TEST ATTRIBUTES AND OPERATOR HELP (DA TL - GA TL) The DA TL (Display Attributes for In/On Line Test) and the GA TL (Get Attributes for In/On Line Test) commands have the same effect. They provide the characteristics of the test that is running or operator help Test Attributes DA TL and GA TL provide the operator with the attributes of the test that is running. The operator enters the command as follows:??ga TL [<test name>] [-OBJ <object type and name>] The CNS 7 administration answers: CNS NNNN HH:MM:SS TL TID TNM OBJ DLY RPT ER HL [OBJ2] [DATL] [VAL] 0 XXXX YY:ZZZZ HH:MM:SS 100 N HE Where: CNS NNNN HH:MM:SS Communications Network Software Node Name Time TID Test Identifier; here it is 0 TNM OBJ DLY Test Name; here it is XXXX Object Name and Type; here it is YY:ZZZZ Time Delay (duration) Option; here it is HH:MM:SS RPT Repetitions Option (1 to 65535; here it is 100) ER Error Report Option (D,S or N; here it is N) HL [OBJ2] [DATL] [VAL] Halt on Error Option (HE = halt on error, CE = Continue on Error; here the option is HE) Name of the Second Object Frame Length Frame Content 39 A2 35DN Rev

44 CNS 7 A2 In/On Line Tests If the command is not correct, this message is sent: * REJECT B REASON = 14/x where x is an error code. For a complete list of error codes, consult paragraph and the OSI/DSA Network Systems Messages and Return Codes Manual Operator Help Either DA TL or GA TL, followed by a space and HELP, gives an initial display telling where to find help for a specific test or problem. The initial display looks like this:??da TL HELP CNS NNNN HH:MM:SS TL TID TNM OBJ 0 HELP TL:HELP CNS NNNN HH:MM:SS TX TL GENERAL HELP CNS NNNN HH:MM:SS TX TL CNS NNNN HH:MM:SS TX TL TYPE : FOR : CNS NNNN HH:MM:SS TX TL CNS NNNN HH:MM:SS TX TL GA TL CMDE : COMMANDS HELP CNS NNNN HH:MM:SS TX TL CNS NNNN HH:MM:SS TX TL GA TL ERR : GENERAL ERRORS HELP CNS NNNN HH:MM:SS TX TL CNS NNNN HH:MM:SS TX TL GA TL TPL : TPL1, TPL2, TPL3 TESTS HELP CNS NNNN HH:MM:SS TX TL CNS NNNN HH:MM:SS TX TL GA TL RLNA : RLNA1, RLNA2 TESTS HELP CNS NNNN HH:MM:SS TX TL CNS NNNN HH:MM:SS TX TL GA TL ELNA : ELNA1, ELNA2 TESTS HELP CNS NNNN HH:MM:SS TX TL CNS NNNN HH:MM:SS TX TL GA TL SLNA : SLNA TEST HELP CNS NNNN HH:MM:SS TX TL CNS NNNN HH:MM:SS TX TL GA TL TDEV : TDEV TEST HELP CNS NNNN HH:MM:SS TX TL CNS NNNN HH:MM:SS TX TL GA TL TX25 : TX251,2,3,4 TESTS HELP CNS NNNN HH:MM:SS TX TL CNS NNNN HH:MM:SS TX TL GA TL BNSE : BNSE1,2 TESTS HELP CNS NNNN HH:MM:SS TX TL CNS NNNN HH:MM:SS TX TL GA TL ECHO : ECHO TEST HELP CNS NNNN HH:MM:SS TX TL CNS NNNN HH:MM:SS TX TL FOR COMPLETE INFORMATION SEE : CNS NNNN HH:MM:SS TX TL TIL OPERATOR'S GUIDE : 39 A2 44 DM The operator can enter GA TL (or DA TL) followed by a blank and CMDE or ERR, for general help information. Otherwise, enter GA TL (or DA TL) followed by the name of the test to display test-specific information. For example, if you type: GA TL RLNA you will see specific help information about the RLNA1 and RLNA2 tests A2 35DN Rev01

45 The Tests Supervisor 2.4 TEST HISTORY REPORT (GH TL) The GH TL (Get History) test command provides the operator with information on the test that is running or on the last test executed GH TL Execution The operator first enters the command:??gh TL [<test name>] [-OBJ <object type and name>] CNS 7 answers as follows: CNS NNNN HH:MM:SS TL (1)= 0 (2)= xxxx (5)= yy:zzzz (6)= yy:aaaa (9)= hh:mm:ss (10)= i (11)= j (12)= k (15)= 1 Where: CNS NNNN HH:MM:SS Communications Network Software Node Name Hours, Minutes, Seconds (1)= 0 Test Identifier (2)= xxxx Test Name (5)= yy:zzzz Object Type and Name (6)= yy:aaaa Type and Name of Second Object, if it exists (9)= hh:mm:ss Execution Duration: - for the entire test if the test has been completed, - up till the present if the test is still running. (10)= i Number of Test Cycles Executed (11)= j Number of Frames Sent (j = 0 to 65535) (12)= k Number of Frames Received (15)= l Number of Errors Detected 39 A2 35DN Rev

46 CNS 7 A2 In/On Line Tests The Error and Reason Codes If the command is incorrect this message is sent to the operator: REASON = 14/x: Where 14 refers to tests and x is an error code See paragraph for a list of the refusal codes and the OSI/DSA Network Systems Messages and Return Codes Manual, for detailed information on error and reason codes A2 35DN Rev01

47 The Tests Supervisor 2.5 OPERATOR RESPONSE COMMAND (TX TL) TX TL Execution The operator uses TX TL to send a message to the test program to answer a question or enter a parameter requested by the test. The command looks like this:??tx TL -MSG <operator response> Response Formats CNS 7 administration response if the command is correct: CNS NNNN HH:MM:SS TL TID TNM OBJ RPRT 0 xxxx yy:zzzz 14/00 Where: TL In and On Line Tests TID Test ID; here it is 0 TNM OBJ RPRT Test Name; here it is xxxx Type and Name of Object Being Tested; here yy:zzzz Report (14 = tests, 00 = command accepted) If the command is incorrect, the first response is by the CNS 7 administration: * REJECT B REASON = 14/x where x is the error code. If the operator does not respond to a question or a request for information, the question or request is sent three times. If the response is incorrect, the question is asked two more times. If the response is still incorrect or if no dialogue is established by the operator, the supervisor sends this message ending the test with a fatal error code 26. CNS NNNN HH:MM:SS TX TL END xxxx yy:zzzz EOT / FATAL 26 See paragraph for error codes applicable to the tests supervisor and paragraph for fatal errors, or see the OSI/DSA Network Systems Messages and Return Codes Manual for a more complete listing of error codes. 39 A2 35DN Rev

48 CNS 7 A2 In/On Line Tests TX TL Example Question asked by the test: CNS RES1 23:11:44 TX TL CALLED SUBSCRIBER X25 NUMBER : Operator response using TX TL: TX TL -MSG CNS 7 administration answers: CNS NNNN HH:MM:SS TL TID TNM OBJ RPRT 0 TX253 NS:NS23 14/ A2 35DN Rev01

49 The Tests Supervisor 2.6 MODIFICATION OF TEST OPTIONS (UP TL) During execution of a test, an option can be changed. To do this, the operator must use the UP TL command Command Syntax The general format of the command is:?? UP TL [<test name>] [-OBJ <xx:yyyy>] <-new option> Where: UP TL -OBJ xx:yyyy -new option Update In/On Line Test Command Object Object Type and Name See each individual test and the EX TL command under the tests supervisor for the possible options Options That Can be Modified The following common options can be modified as indicated: -DLYA -RPT -ERR -NHLT -HLT A new duration can be requested in format: hh:mm:ss. The maximum time that can be accepted is 09:06:06; 9 hours, 6 minutes and 6 seconds. The number of test iterations can be changed. You can select from 1 to 65,535 repetitions. The way in which errors are reported can be altered. You may select D detailed, S statistics, or N no error reports. Changes the option from Halt to No Halt on error detection (except fatal errors). Reverses the -NHLT and instructs the test to halt when an error is encountered. The specific options of individual tests can also be modified by UP TL during test execution. These options are -DATL and -VAL. 39 A2 35DN Rev

50 CNS 7 A2 In/On Line Tests Response Formats If the command is correct, the CNS 7 administration responds: CNS NNNN HH:MM:SS TL TID TNM OATT NATT OBJ RPRT 0 xxxx aa bb yy:zzzz 14/00 Where: TL In and On line Tests TID Test ID (0) TNM OATT NATT yy:zzzz Test Name (xxxx) Old Attribute (in this case, aa = old option) New Attribute (in this case, bb = new option) Object Tested 14 In and On Line Tests 00 Command Accepted The tests supervisor then responds: CNS NNNN HH:MM:SS TX TL UP TL xxxx yy:zzzz <report> The report can be: OATT MODIFIED (Command accepted) END IN PROGRESS (Command rejected) NO TEST RUNNING (Command rejected) If the command is incorrect the CNS 7 administration response is as follows: * REJECT B REASON = 14/x where x is an error code. Error codes applicable to the tests supervisor are given in paragraph For further information on error and reason codes, see OSI/DSA Network Systems Messages and Return Codes Manual A2 35DN Rev01