manualshive.com logo in svg

Compaq DECnet SNA Gateway for Synchronous Transport, Problem Solving

Share
Download
Compaq DECnet SNA Gateway for Synchronous Transport Problem Solving Download Page 104

You may also receive IBM sense codes. Most of the error messages are in the
standard OpenVMS message format. Section A.2 describes the format of the
error messages and refers you to documentation where the meaning of the
error messages is provided.

A.1 Interpreting Event Messages

Event messages logged by OPCOM have the following format:

DECnet SNA event

nnn.nn event-text

From node

node-address (node-name), dd-mmm-yyyy hh:mm:ss.cc

component component-id, Severity = level

message1_text

message2_text

where

nnn.nn

Is the DECnet event code. All Gateway-ST event
messages have a code greater than 255.

event-text

Is the text that always appears with the event class
and type.

node-address (node-name)

Is the Gateway-ST node address and node name.

dd-mmm-yyyy

Is the date when the event occurred.

hh:mm:ss.cc

Is the time when the event occurred.

component component-id

Is the name and ID of the Gateway-ST component
sending the event messages.

level

Is the severity level of the event.

message1_text
message2_text

Are messages giving you the details of the event. The
second of these messages can be a VAX or AXP system
message. For information about VAX or AXP system
messages, refer to OpenVMS System Messages and
Recovery Procedures.

If the text contains SNANCP error messages, refer to
the DECnet SNA Gateway-CT and ST Management
book.

A–2 Interpreting System Messages

Summary of Contents for DECnet SNA Gateway for Synchronous Transport

Page 1: ...f the DECnet SNA Gateway for Synchronous Transport and its related OpenVMS products This manual also discusses diagnostic tools and describes how to report problems with the DECnet SNA Gateway products Revision Update Information This is a revised manual Operating System and Version OpenVMS VAX V5 4 or later OpenVMS AXP V1 5 Software Version DECnet SNA Gateway for Synchronous Transport V1 2 ...

Page 2: ...or its affiliated companies Restricted Rights Use duplication or disclosure by the U S Government is subject to restrictions as set forth in subparagraph c 1 ii of the Rights in Technical Data and Computer Software clause at DFARS 252 227 7013 Copyright 1991 1993 Digital Equipment Corporation All Rights Reserved The following are trademarks of Digital Equipment Corporation AXP DEC DEC CMS DEC MSS ...

Page 3: ... Loopback Test 2 9 2 2 2 Cable Loopback Test 2 10 2 2 3 Modem Loopback Tests 2 10 2 3 DEC MicroServer Loopback Tests 2 10 2 3 1 Loopback Points 2 11 2 3 2 General Test Procedure 2 12 2 3 3 The test Command 2 12 2 3 4 Sample Test Procedure 2 12 2 3 4 1 Connect to the DEC MicroServer 2 13 2 3 4 2 Stop the System Software 2 13 2 3 4 3 DEC MicroServer I O Port Testing 2 13 2 3 4 4 Adapter Cable and Mo...

Page 4: ... I O Trace 3 3 3 2 1 3 Generalized PIU Trace 3 3 3 2 1 4 VTAM Line Trace 3 4 3 2 1 5 SDAID Trace Program 3 4 3 2 1 6 VTAM Internal Trace 3 5 4 Up Line Dumps 5 Reporting Your Problems 5 1 Gathering Information 5 1 5 2 Reporting Problems to Digital Equipment Corporation 5 4 A Interpreting System Messages A 1 Interpreting Event Messages A 2 A 1 1 Event Classes A 3 A 1 2 Event Types A 3 A 2 Interpreti...

Page 5: ...ecting to the DEC MicroServer D 2 D 3 Detaching the Console D 3 D 4 Halting the Software D 3 D 5 Testing the DEC MicroServer D 3 D 5 1 Data Loopback Tests D 4 D 5 2 Modem Signal Tests D 5 D 5 3 Cable Type Tests D 7 D 5 4 Soak Testing the DEC MicroServer D 7 D 6 Monitoring the DEC MicroServer Status D 8 D 7 Reloading the System D 9 D 8 Dumping the Contents of Memory D 9 D 9 Console Password D 9 D 9...

Page 6: ...nel C 2 D 1 Loopback Point Command Qualifiers D 5 D 2 Loopback Points for the Modem Signal Test D 6 Tables 2 1 Faults Indicated by Loopback Testing 2 16 5 1 Documenting a Problem 5 2 A 1 Event Classes and Location A 3 A 2 Sample IBM Sense Codes A 6 C 1 Power Up Display Values C 3 C 2 Dump Display Values C 4 C 3 Error Code Values C 5 D 1 Summary of Remote Console Commands D 1 E 1 The DEC MicroServe...

Page 7: ...ctions between the DEC MicroServer the four port server product and the DEC MicroServer SP the single port server product are noted This manual provides information to help solve problems that could arise during the day to day use of the Gateway ST software products managed from an OpenVMS operating system Use this manual with other Digital and IBM documentation The material in this guide reflects...

Page 8: ...tion begins by listing the problems covered in that section Check the list to find a problem similar to your own Chapter 2 Using Loopback Tests describes loopback tests Chapter 3 Traces describes the different types of Gateway Management and IBM traces Chapter 4 Up Line Dumps explains the procedure that is performed to obtain an up line dump Chapter 5 Reporting Your Problems describes how to repor...

Page 9: ...ive error codes Appendix D DEC MicroServer Facilities for Problem Solving describes how to connect to the DEC MicroServer as a remote console It also describes the remote console commands and their functions Appendix E DEC MicroServer Configuration Guidelines contains guidelines for using the DEC MicroServer synchronous ports Appendix F Adapter Cable Pin Signals describes the supported pin signals...

Page 10: ...Microserver Systems Cystems Configuration Card Installing the DEC MicroServer SP DEC MicroServer SP Systems Configuration Card DECnet SNA Gateway for Synchronous Transport Software Manuals The following manuals are part of the DECnet SNA Gateway for Synchronous Transport documentation kit DECnet SNA Gateway ST Guide to IBM Parameters DECnet SNA Gateway ST Installation DECnet SNA Gateway ST Problem...

Page 11: ... DECnet SNA Gateway ST Guide to IBM Parameters Installing the DEC MicroServer Installing the DEC MicroServer SP DECnet SNA Gateway ST Installation OpenVMS DECnet SNA Gateway CT Gateway ST Managing Planning Installing and Configuring Problem Solving Chapters 2 4 Management OpenVMS DECnet SNA Gateway ST Problem Solving OpenVMS xi ...

Page 12: ...erface for OpenVMS Interactive Access DECnet SNA 3270 Terminal Emulator for OpenVMS DECnet SNA VMS Distributed Host Command Facility Office Information Transfer DECnet SNA VMS DDXF External Document Exchange with IBM DISOSS VAX Message Router S Gateway VAX Message Router P Gateway For a list of the documentation for the preceding products see DECnet SNA Gateway for Channel Transport and Gateway fo...

Page 13: ...ease 7 Problem Determination Guide IBM Order No SC33 0242 IBM System 360 and System 370 I O Interface Channel to Control Unit Original Equipment Manufacturers Information IBM Order No GA22 6974 IBM Virtual Storage Extended Advanced Functions Service Aids Version 2 Release 2 IBM Order No SC33 6195 MVS Extended Architecture System Programming Library Service Aids IBM Order No GC28 1159 NetView Opera...

Page 14: ...ute specific information opt arg Square brackets enclose optional parts of a command Return An enclosed key name indicates that you press that key on the keyboard Ctrl x An enclosed control key sequence is used to indicate that you hold down the Ctrl key while you press another key represented by x When you issue NCP NCL and SNANCP commands many component names parameters and qualifiers require ad...

Page 15: ...ed to the circuit E address A string of 12 hexadecimal digits represented by 6 bytes separated by hyphens for example AA 00 04 00 AB 04 The string indicates the Ethernet hardware address line id A string of characters whose exact syntax is that for a DECnet or SNA line identification On DECnet nodes line identification takes one of the following formats dev c dev A device name c A decimal number 0...

Page 16: ...red to as IBM NCP API DECnet SNA Application Programming Interface for OpenVMS APPC LU6 2 DECnet SNA APPC LU6 2 Programming Interface for OpenVMS CICS VS Customer Information Control System Virtual Storage also referred to as CICS DECnet NCP Digital s Network Control Program also referred to as NCP DDXF DECnet SNA VMS DISOSS Document Exchange Facility DHCF DECnet SNA VMS Distributed Host Command F...

Page 17: ... Entry for OpenVMS RU Request response unit SDLC Synchronous Data Link Control SLU Secondary logical unit SNA IBM s Systems Network Architecture SNANCP DECnet SNA Gateway Network Control Program SNAP DECnet SNA Gateway Management display utility SNATRACE DECnet SNA Gateway Management protocol trace utility SSCP System services control point 3270 DS DECnet SNA 3270 Data Stream Programming Interface...

Page 18: ......

Page 19: ...your problem check the IBM and Digital documentation for the product you are using Also check the release notes for the product you are using for up to date information on known problems For information about interpreting OpenVMS and DECnet error messages refer to the OpenVMS System Messages and Recovery Procedures 1 1 Hardware Problems Problem Number Symptom 1 The DEC MicroServer does not power u...

Page 20: ...Problem Number Symptom 6 The Gateway ST loads but the circuit remains in the on starting state 1 2 Solving DECnet SNA Gateway for Synchronous Transport Problems ...

Page 21: ...he control panel of the DEC MicroServer Determine whether the plug on the end of the cord is properly inserted into the wall socket 2 Ensure that there is power to the wall socket 3 Determine whether the DEC MicroServer s circuit breaker has been tripped If it has reset the circuit breaker shown in Figure 1 1 and power up the unit again NOTE Figure 1 1 shows the control panel of the four port DEC ...

Page 22: ...ing Make sure the main voltage selector on the control panel is correctly set for your supply voltage see Figure 1 2 NOTE Figure 1 2 shows the control panel of the four port DEC MicroServer If necessary change the setting on the voltage selector and try to power up the unit again If the selector is correctly set but the breaker still trips unplug the unit and call Digital service representative 1 ...

Page 23: ...Figure 1 2 Checking the Voltage Selector LKG 4905 93I Solving DECnet SNA Gateway for Synchronous Transport Problems 1 5 ...

Page 24: ...s do not turn but the power indicator lights there is a problem with the DEC MicroServer Contact Digital service representative If the power indicator does not light but the fans turn the power indicator might be faulty Try to boot the system Even if the system works you should contact Customer Service to replace the unit as soon as possible If the system does not boot there is a problem with the ...

Page 25: ...ION If you change an adapter cable be careful not to accidentally press the DUMP switch 4 Check the local modem Make sure the modem is turned on Make sure the communications line is correctly connected to the modem Test the modem using its self test facilities if any The manufacturer s information tells you what facilities are available and how to use them Use modem signal loopback tests to make s...

Page 26: ...s port might be faulty For more information see Installing the DEC MicroServer If the test program proceeds normally it is likely that there is no fault on that port To perform any further fault isolation on the line read the information on loopback testing in Chapter 2 One faulty port on the DEC MicroServer does not necessarily prevent you from using the DECnet SNA Gateway for Synchronous Transpo...

Page 27: ...on about these parameters To ensure that the correct values are supplied the next time the Gateway ST is down line loaded edit the SNA configuration file on the load host SYS COMMON SNA CSV SNAGATEWAY_gateway node name_SNA COM After you have edited the configuration file reload the Gateway ST 3 Check your modems If a modem is defective replace it Work through the following procedures to test your ...

Page 28: ...dem Make sure that all the cables between the DEC MicroServer and the modems are correctly connected If you find any loose connections correct them then reload the system if necessary Use loopback tests to check the adapter cable and any modem extension cables Chapter 2 describes loopback tests Ensure that you have the appropriate adapter cables In particular note that some early revisions to the ...

Page 29: ...dundancy Check errors there are two possible causes for the errors IBM test frames on the line can cause CRC errors Ask your IBM system programmer to check the line for test frames There might be a problem with the line or the modem If you have already verified that there are no IBM test frames on the line call your Digital service representative to report the problem as a hardware problem 3 If th...

Page 30: ...epresentative 4 If the counter shows Frame too long error messages change the buffer length by issuing the following SNANCP command SNANCP SET LINE line id BUFFER SIZE n where n is the BUFFER LENGTH This value should be the same as the value of the MAXDATA parameter in the IBM system The problem might be a temporary one caused by extraordinary circumstances Monitor the problem line Regularly clear...

Page 31: ...he IBM line and PU are active See the IBM system manager 3 Check that you completed Part 2 of the SNACST CONFIGURE COM procedure and that the following file was created SYS COMMON SNA CSV SNAGATEWAY__gateway node name_SNA COM 4 Check the IBM parameters against the values specified in the DECnet SNA Gateway ST Guide to IBM Parameters In particular make sure the NRZI setting for the IBM NCP LINE mac...

Page 32: ...d reload the system CAUTION If you change an adapter cable be careful not to accidentally press the DUMP switch 6 Check the DEC MicroServer synchronous ports Hardware Problem 3 describes the steps necessary to check the synchronous ports 7 Check the local and the remote modems on the lines that did not come up In particular check the following items Make sure the modems are powered on and working ...

Page 33: ...s but the line counters indicate less than normal activity or no activity 7 The Gateway ST boots but the circuit remains in the on starting state 8 The PU does not become active 9 Errors occur in the Gateway ST initialization process 10 The Gateway ST node does not recognize the DECnet node name you specify 11 You receive an error message when you try to use a component or access name that you def...

Page 34: ...ver is working properly Make sure that the power indicator is lit and the fans are turning If the indicator is not lit or the fans do not turn see Hardware Problem 1 Turn off the DEC MicroServer disconnect the Ethernet cable and attach the Ethernet loopback connector Type H4080 CAUTION If you power down the DEC MicroServer wait at least 3 seconds before powering it up again Power up the DEC MicroS...

Page 35: ... MicroServer Refer to Appendix C for DEC MicroServer display values 5 Check that the load host is running properly Try to load the Gateway ST again 6 Check that each load host has a physical connection to the same Ethernet as the DEC MicroServer 7 Check that each load host has a database entry for the DEC MicroServer Identify the load hosts and perform the following actions Enter the following com...

Page 36: ... match the Ethernet address of the Gateway ST node You can find the DEC MicroServer Ethernet hardware address on the label on the back of the DEC MicroServer Check that the load file specification is SYS COMMON SNA CSV SNACSTnnn SYS where nnn is the product version number Correct any errors you find Use the DIRECTORY command to check that the Gateway ST load file exists Try to load the Gateway ST ...

Page 37: ...A gives the format of event logging and error messages Also check the MOM LOG files in SYS MANAGER for error messages from the maintenance operation module MOM Check if the proxy information is correct by looking at SYS COMMON SNA CSV NETSERVER LOG for the following message Connect request received at dd mmm yyyy hh mm ss cc from remote process gateway node name 0 SNA GO for Object SYS COMMON SYSE...

Page 38: ...t Check that the software load file SNACTSnnn SYS located in SYS COMMON SNA CSV has the correct protection code S RWED O RWED G W 13 If the configuration file has become corrupted redo it 14 Reload the DEC MicroServer 1 20 Solving DECnet SNA Gateway for Synchronous Transport Problems ...

Page 39: ... any errors that you find and load the system again Initialization Problem 1 provides more information about these items 2 Use the following NCP command to check for unknown load hosts NCP TELL gateway node name SHOW EXECUTOR CHARACTERISTICS One line in this display gives the name of the node that loaded the DEC MicroServer If you do not want that node to be a load host you can prevent it from loa...

Page 40: ...ST Solutions See the solutions for Initialization Problem 1 If you receive these event messages and your Gateway ST is booted the events are the result of other systems requests for services from your load host These messages have no bearing on the Gateway ST 1 22 Solving DECnet SNA Gateway for Synchronous Transport Problems ...

Page 41: ...ntroller Correct any errors and issue the LOAD command again 2 Verify that the node that executes the LOAD command Is a load host for the DEC MicroServer by verifying that the DECnet database has an entry for the DEC MicroServer and that the following entries are correct DECnet node address Service circuit Hardware address Load file specification To check these entries issue the following command ...

Page 42: ...SET CIRCUIT circuit id SERVICE ENABLED NCP SET CIRCUIT circuit id STATE ON Correct any errors in the database and reissue the command Has a connection to the Ethernet used by the DEC MicroServer Correct any errors and issue the LOAD command again 3 Make sure the executor node has all the necessary load files in the correct directories Check the DECnet SNA Gateway ST Installation for a list of the ...

Page 43: ...TUP SNAGM EVL_STARTUP To ensure that Gateway ST events are logged the next time the host system is booted insert the preceding command in the system startup file For more information about SNAEVL refer to DECnet SNA Gateway CT and ST Management If the display from this command does not list EVL enter the following command to start DECnet event logging on your system NCP SET LOGGING MONITOR STATE O...

Page 44: ...t receive messages Check this setting with the following DCL command SHOW TERMINAL If necessary issue the following DCL command to set your terminal to broadcast mode SET TERMINAL BROADCAST If you still do not receive event messages check whether you have screened out OPCOM messages with the following DCL command SHOW BROADCAST If necessary issue the following DCL command to set broadcasting for O...

Page 45: ...e file and check the SET LINE command in the file for the line state Ensure that the NRZI setting of the ACF NCP LINE macro matches the SIGNALLING setting on the Gateway ST node Check that the value set for the PU address ADDR is the same as the value specified for the SDLC station address on the Gateway ST node Use ADDR in ACF NCP or ADDR on VTAM switched node definitions for this value Verify th...

Page 46: ...t line state next time it is loaded edit the SNA configuration file on the load host SYS COMMON SNA CSV SNAGATEWAY_gateway node name_SNA COM 5 Check the DEC MicroServer s synchronous port s by using the procedure described in Hardware Problem 3 6 This problem might also be caused by incorrect circuit parameters See Initialization Problem 7 1 28 Solving DECnet SNA Gateway for Synchronous Transport ...

Page 47: ...llowing file was created SYS COMMON SNA CSV SNAGATEWAY_gateway node name_SNA COM Review the contents of the above file and check the SET CIRCUIT command in the file For information about the correct syntax of the SNANCP SET CIRCUIT command see the DECnet SNA Gateway CT and ST Management book 4 Check for SNAEVL event messages that indicate a problem with the configuration file 5 Check that the circ...

Page 48: ...wing command to check if there are circuit level errors SNANCP SHOW CIRCUIT circuit id COUNTERS Circuit level errors often indicate a configuration problem Check that the circuit response mode is set correctly For more information see the DECnet SNA Gateway CT and ST Management book Also check that the PU segment size and line buffer size are the same and that these sizes match the value of the IB...

Page 49: ...ommand in the file For information about the correct syntax of the SNANCP SET PU command see the DECnet SNA Gateway CT and ST Management book 4 Check for SNAEVL event messages that indicate a problem with the configuration file Messages are found in SYS COMMON SNA CSV NETSERVER LOG 5 If the SNANCP SHOW command shows that the PU state is inactive check that The circuit is operational see Initializa...

Page 50: ... of some of the causes for this problem The SNAINI object may not be defined To see if it is defined issue the NCP command for Phase IV NCP SHOW OBJECT SNAINI CHARACTERISTICS and for Phase V NCL SHOW SESSION CONTROL APPL SNAINI ALL The display from this command should be the following Object Volatile Characteristics as of dd mmm yyyy hh mm ss Object snaini Number 39 File id SYS COMMON SNA CSV SNAI...

Page 51: ... of the Gateway ST configuration again Check to determine if incoming proxies are enabled with the following command NCP SHOW EXECUTOR CHARACTERISTICS If incoming proxies are not enabled enter the following command to enable them NCP SET EXECUTOR INCOMING PROXY ENABLE When the Gateway ST was initialized the command procedure could not read or encountered errors in the SNA configuration file Event ...

Page 52: ...re information about the problem 3 For nodes outside the area you can modify the Gateway ST node s DECnet database while the Gateway ST is running Issue the following NCP commands NCP SET EXECUTOR NODE gateway node nameUSERusername _PASSWORD password NCP SET NODE node address NAME DECnet node name To ensure that a node outside the area is defined the next time the Gateway ST loaded edit the node c...

Page 53: ...eck NETSERVER LOG for errors Reboot the Gateway ST using the NCP TRIGGER command from a load host For Phase IV enter NCP TRIGGER NODE gateway node name For Phase V enter NCL BOOT MOP CLIENT gateway 2 You might have an error in the component or access name definition in the SNA configuration file Correct any errors To ensure that the components and access names are defined next time the Gateway ST ...

Page 54: ...tion You might have purged your network object database Redefine the object on Phase IV by executing SYS COMMON SNA CSV DEFINE_gateway node name_ON_load host node name COM and on Phase V by executing SYS STARTUP NET APPLICATION_STARTUP_NCL 1 36 Solving DECnet SNA Gateway for Synchronous Transport Problems ...

Page 55: ...teway ST system is unreachable 3 The Gateway ST boots and comes up but does not initialize completely NOTE To access the Gateway ST you must be licensed to use DECnet If DECnet is not enabled you cannot set the lines and circuits to the ON state Solving DECnet SNA Gateway for Synchronous Transport Problems 1 37 ...

Page 56: ...sages that are specific to DECnet SNA products 2 If error messages suggest the problem is with your load host node make sure all the components required for the DECnet SNA Gateway for Synchronous Transport and its products have been correctly installed configured and loaded 3 If error messages suggest the problem is with the Gateway ST node the DEC MicroServer refer to the problems described in Se...

Page 57: ...ceiver connection and the Ethernet interface to the DECnet network 4 Ensure that the Gateway ST software is installed and configured correctly 5 Your DECnet network might not be configured correctly For Phase V use DNS to see that the node is known to the network For Phase IV Use the following command to check that your load host has the Gateway ST DECnet node address defined correctly ncp SHOW NO...

Page 58: ... event message displayed during successful initialization is DECnet SNA event 266 0 Gateway initialization From node aa ssss nodename dd mmm yyyy hh mm ss cc SNA gateway management Severity informational Completed Normal successful completion Check the messages in the SYS COMMON SNA CSV NETSERVER LOG file and correct any problems 1 40 Solving DECnet SNA Gateway for Synchronous Transport Problems ...

Page 59: ...n you enter the first command to initiate a session 5 Nothing happens when you try to initiate your session even after a reasonable wait for normal session establishment 6 The session hangs while in progress 7 Sessions terminate abnormally 8 An excessive number of line errors occur 9 An excessive number of circuit errors occur 10 Response time or file transfer time increases significantly Solving ...

Page 60: ...command SNANCP SHOW KNOWN ACCESS NAME CHARACTERISTICS Use the following SNANCP command to define access names on the Gateway ST node SNANCP SET ACCESS NAME access name id For information on using SNANCP commands to define access names refer to the DECnet SNA Gateway CT and ST Management book To ensure that the Gateway ST is initialized with the correct access names next time it is loaded edit the ...

Page 61: ... activated If the PU name is not defined use the following SNANCP command to define it SNANCP SET PU pu id For information on using SNANCP commands to define PUs refer to the DECnet SNA Gateway CT and ST Management book To ensure that the Gateway ST is initialized with this PU next time it is loaded edit the SNA configuration file on the load host SYS COMMON SNA CSV SNAGATEWAY_gateway node name_SN...

Page 62: ...nt to use are defined and are active If the LUs are not defined use the following SNANCP command to define them on the Gateway ST SNANCP SET PU pu id LU LIST lu list For information on defining LUs with SNANCP commands refer to the DECnet SNA Gateway CT and ST Management book To ensure that the Gateway ST is initialized with these LUs next time it is loaded edit the SNA configuration file on the l...

Page 63: ...tates that there is no such SNA component line circuit PU LU access name or server one of the following might be the cause of the problem You specified the name of the component incorrectly The component name you specified is not defined For more information see Section 1 2 Initialization Problems and the Session Problems in this section 4 If the error message states that access is rejected due to...

Page 64: ...P command to see if the range of LUs for the access name corresponds to the correct LU on the IBM host SNANCP SHOW ACCESS NAME access name CHARACTERISTICS 8 If an error message containing an IBM sense code appears it probably indicates a session problem Verify that your application id and session parameters are correct Receiving an IBM sense code indicates that the lines circuits PUs and LUs are f...

Page 65: ...or normal session establishment Solution There may be a problem with the IBM system The IBM system may be busy or there may be an IBM configuration problem either with VTAM or with the application with which you are trying to communicate Solving DECnet SNA Gateway for Synchronous Transport Problems 1 47 ...

Page 66: ...achable from the Gateway ST see Session Problem 5 in this section 2 DECnet problems may be occurring between the load host and the Gateway ST See Section 1 3 DECnet Problems 3 The IBM host might not be working properly or might be overloaded see Session Problem 5 in this section 1 48 Solving DECnet SNA Gateway for Synchronous Transport Problems ...

Page 67: ...ncluding Frame too long Ensure that the PU segment size matches the line buffer size Check the circuit counters with the following command SNANCP SHOW KNOWN CIRCUITS COUNTERS If the display includes the following message change the buffer size to reflect the value of MAXDATA specified in the IBM system 1 Remote station errors including FRMR sent I frame too long 1 Data errors inbound including Fra...

Page 68: ...r Line errors are usually caused by either the cables or the modem Use the SNANCP LOOP LINE command to test the communications line This command helps you trace the line problem to the controller cable or modem If line errors occur on only one circuit try moving the line to one of the other ports if available If the problem remains replace the cable For additional information on line problems refe...

Page 69: ...se your system is incorrectly configured follow A FRMR sent I frame too long error message is often caused by an insufficient line buffer size A Reject received error message is often caused by setting the PU segment size larger than the IBM MAXDATA parameter size Transmit and receive errors can be caused by incorrectly setting the circuit duplex parameter to FULL when the IBM parameter is set to ...

Page 70: ...n of noisy lines Report the problem to your operations manager 2 Use SNANCP commands to check the following The MODEM parameter this should be normal if you are not using IBM diagnostic modems SNANCP SHOW LINE line id CHARACTERISTICS Do not specify a modem type of diagnostic unless you are using diagnostic modems Check the adequacy of your host system resources Probable causes of slowed response t...

Page 71: ...ommunications device connecting the Gateway ST node to the SNA network See Section 1 1 Problems 5 and 6 for more information If the problem persists ask your Digital service representative to check this device Solving DECnet SNA Gateway for Synchronous Transport Problems 1 53 ...

Page 72: ......

Page 73: ...DECnet error messages you should run these tests The tests are described in Section 2 1 SNANCP loopback tests These tests check the communications hardware from the Gateway ST to the modem at the IBM site You should run SNANCP loopback tests in either of the following cases If you have been receiving SNANCP error messages or SNA related event messages If the SNANCP command SHOW LINE line id COUNTE...

Page 74: ...e 2 1 shows which parts of the network the loopback tests check Figure 2 1 Loopback Tests DECnet SNA GWY ST LKG 2948 89R DECnet Host IBM Network DEMSA or DEMSB NCP Tests SNANCP Tests 2 2 Using Loopback Tests ...

Page 75: ...gure 2 2 If the first set of tests are successful run the tests shown in Figure 2 3 Run the tests in the order shown in the figures unless you know that the problem is in a particular area If the first test you run does not isolate the problem continue testing in the order shown until you find the problem Using Loopback Tests 2 3 ...

Page 76: ... Invoke NCP Yes No Yes No Run executor loopback test OK loopback test Run circuit level Yes No OK Contact your Digital representative DECnet problem on node running loopback test See Figure 2 3 Fault in DECnet SNA Gateway ST communications OK 2 4 Using Loopback Tests ...

Page 77: ...cal modem Yes No Run SNATRACE or IBM traces Fault in remote modem Contact your Digital representative Invoke SNANCP Run controller loopback test OK Run cable test OK Run local modem test OK Run remote modem test OK Faulty synchronous port Fault in cable Using Loopback Tests 2 5 ...

Page 78: ...work The tests described in this section are Remote loopback test This loopback test checks the DECnet software and logical link between the local DECnet node and the Gateway ST regardless of the circuit see Section 2 1 1 Executor loopback test This loopback test checks the DECnet software in the local node see Section 2 1 2 Circuit level loopback test This loopback test checks the service circuit...

Page 79: ...t your DECnet node Then issue the LOOP NODE command NCP SET NODE gateway node name NONPRIVILEGED USER username _PASSWORD password NCP LOOP NODE gateway node name NCP CLEAR NODE gateway node name NONPRIVILEGED USER PASSWORD Note that all connections issued from your DECnet node to the specified Gateway ST can potentially use the default access control you have established Therefore be sure to leave...

Page 80: ...ult service is enabled If you want to verify that service is enabled issue the following command NCP SHOW CIRCUIT circuit id CHARACTERISTICS If the service is not enabled enter the following commands NCP SET CIRCUIT circuit id OFF NCP SET CIRCUIT circuit id SERVICE ENABLED If the service is enabled enter the following command NCP LOOP CIRCUIT circuit id NODE gateway node name For example enter the...

Page 81: ...ollowing command to verify the state of the line SNANCP SHOW LINE line id STATUS If the line state is not OFF issue the following SNANCP command SNANCP SET LINE line id STATE OFF Refer to the DECnet SNA Gateway CT and ST Management book for information on SNANCP commands 2 2 1 Controller Loopback Test Use this loopback test to check the communications device on the Gateway ST To use the controller...

Page 82: ...f the communications path by physically setting it to loopback mode see the manufacturer s instructions If the test fails have the modem repaired If the test is successful run a similar test on the remote modem to further isolate the problem For this test the local modem should be set for normal communications and the remote modem should be set to loopback mode see the manufacturer s instructions ...

Page 83: ...oServer Communications link Loopback points Modem Loopback connectors can be attached to any of the following loopback points To the socket on the DEC MicroServer At the end of the adapter cable At the end of the modem cable if any Some modems provide loopback functions at the following loopback points On the communications link side of the modem At the remote modem By doing a series of tests each...

Page 84: ...hat the modem cable is faulty 2 3 3 The test Command To do the testing use the DEC MicroServer s remote console facilities See Appendix D for information on the DEC MicroServer s remote console facility and commands Use the TEST command to perform each loopback test Each time you use the TEST command to perform a loopback test it displays one of the following messages If the test is successful Suc...

Page 85: ...onsole command HALT Once the DEC MicroServer has been halted the only way to restore normal Gateway ST operations is to load the Gateway See Section 2 3 4 7 for information about using the console BOOT command 2 3 4 3 DEC MicroServer I O Port Testing Test the 50 way port on the DEC MicroServer by doing the following 1 Remove the adapter cable from the 50 way port 2 Attach the 50 way loopback conne...

Page 86: ... the modem 3 Put the appropriate loopback connector on the end of the modem cable 4 Enter the following command at the console TEST DATA_LOOPBACK CHn As before replace n by the number of the synchronous port If this fails go to Section 2 3 5 If this test succeeds reconnect the cable to the modem and test the local modem 2 3 4 5 Local Modem Testing A modem control signal sent to the modem from the ...

Page 87: ...rm the following steps 1 Switch the modem so that it loops data back refer to the manufacturer s instructions 2 Enter the command TEST DATA_LOOPBACK CHn MANUAL Replace n with the number of the port 0 1 2 or 3 If the test fails go to Section 2 3 5 If this test succeeds reset the modem and then test the remote link 2 3 4 5 3 Modems with No Test Facilities If your modem does not have built in test fa...

Page 88: ...oServer BOOT Booting the DEC MicroServer takes a few minutes because the system performs its self tests and then loads the Gateway ST image During this time remote console commands are not accepted and control is returned to the DECnet NCP utility 2 3 5 Additional Procedures If one of the previously described tests has failed use Table 2 1 to find the cause of the problem and suggested solutions T...

Page 89: ...dem is not working ask the remote site to correct the fault on their modem If all the tests complete successfully and you still have trouble on the link check the DEC MicroServer s configuration including data speeds Also allow for intermittent faults by repeating the tests two or more times Some conditions such as electrical storms may cause errors even though all the equipment is working properl...

Page 90: ......

Page 91: ...ows the SNA protocol exchange between a Gateway ST node and an IBM node You can use SNATRACE or Netrace to isolate problems associated with the Gateway ST and its access routines For information about using SNATRACE refer to the DECnet SNA Gateway CT and ST Management book 3 1 1 Types of Traces You can use three types of Gateway Management traces to isolate problems in the DECnet SNA environment C...

Page 92: ... run a PU trace 3 1 1 3 Session Level Traces Run a session level trace if you perceive a protocol problem with a particular session Any of the symptoms listed in previous sections can indicate the need for a session level trace 3 2 IBM Traces Gateway ST users might need data from IBM traces to isolate problems in the Gateway ST environment You use trace data to show protocol sequences on the line ...

Page 93: ...ce to trace path information units PIUs being sent to and received from a VTAM application program 3 2 1 2 VTAM I O Trace The VTAM I O trace TYPE RNIO records the order in which PIUs flow between network nodes and VTAM You might use this trace to determine whether the Gateway ST software receives all the responses that it should and whether VTAM forwards all the requests issued by the Gateway ST T...

Page 94: ...u suspect a problem with a device attached to the IBM 37xx communications controller When you receive the error message Circuit is not active This message indicates that you cannot activate the line between the Gateway ST and IBM When the line to IBM from the Gateway ST does not activate Note Before using a line trace you should use a generalized PIU trace to verify whether the problem is in VTAM ...

Page 95: ...PTION API traces the IBM application program interface calls OPTION PIU traces all messages originating from VTAM or intended for processing by VTAM Like the buffer contents trace it helps you isolate problems with the hardware NCP or VTAM OPTION SSCP traces session initiation and session termination It helps isolate VTAM problems to a specific VTAM module or component For example you can use the ...

Page 96: ......

Page 97: ...he Ethernet calling for any node on the Ethernet to receive an up line memory dump 3 Entries in the DECnet configuration database of each node on the Ethernet determine whether that node recognizes the Gateway ST and whether the necessary service is enabled Any node that can accept a dump sends a message back to the Gateway ST 4 The Gateway ST then dumps its memory onto the node that responds firs...

Page 98: ...ST and whether the necessary service is enabled Any node that can perform the load sends a message back to the Gateway ST The Gateway ST then loads from the node that responds first If no node responds to the Gateway ST node s request to load the system image the Gateway ST node repeats the process in step 5 4 2 Up Line Dumps ...

Page 99: ... you if you have this service Section 5 1 describes the information you should include with a problem report Section 5 2 provides more information about SPRs 5 1 Gathering Information Table 5 1 lists the documentation that you should collect while trying to isolate a problem Entries in separate columns in the table indicate which type of information can help you or Digital Equipment Corporation to...

Page 100: ...ER R A A PU trace using SNATRACE O O A circuit trace using SNATRACE O O A session trace using SNATRACE O O Listing of your SNA configuration file SNAGATEWAY_gnn_SNA COM A A A A Listing of your DECnet configuration file sNAGATEWAY_gnn_DNA COM A A A A description or map of your DNA network showing operating system versions A A A A description of your SNA environment A A A hard copy of events logged ...

Page 101: ...efinitions R R Listing of VTAM application node definitions R R Logon mode table for this GROUP LINE PU LU R R Listing of CICS terminal control table definitions R R Listing of IMS control block definitions R R LOG files from the workstation the job and NETSERVER R R Listing of JES2 JES3 startup parameter definitions R Note For RJE and DHCF problems please supply both the Gateway ST software versi...

Page 102: ...ervices you should complete one of these forms when you are unable to solve a critical problem Your local area office can provide you with additional forms Each SPR form has attached instructions to follow when completing the form In addition to the data requested on the form include any other information on the problem as described in Section 3 1 of the SPR form When your SPR form is complete sub...

Page 103: ...stem program called OPCOM logs events When you have decided at which terminal you want OPCOM to dispay the messages the terminal can be a console enter the following command from that terminal to set it as an operator s terminal REPLY ENABLE NETWORK You will receive all Gateway ST event messages and DECnet network messages at that teminal Section A 1 describes the format and meaning of event messa...

Page 104: ... greater than 255 event text Is the text that always appears with the event class and type node address node name Is the Gateway ST node address and node name dd mmm yyyy Is the date when the event occurred hh mm ss cc Is the time when the event occurred component component id Is the name and ID of the Gateway ST component sending the event messages level Is the severity level of the event message...

Page 105: ...Event 256 Line 257 Circuit 258 Physical Unit 259 Session 265 Counters 266 Gateway management Initialization Logging 268 DHCF GAS 269 RJE A 1 2 Event Types Event types are categorized according to the class of events to which they belong This section lists and explains all event types The text that follows the type and describes the event is not displayed on the Gateway ST node However the text is ...

Page 106: ... change Session protocol error Access denied Counter Automatic counters Counters zeroed Counter overflow Initialization Gateway initialization Initialization failure Initialization message Logging Logging sink state change Event logging sink failure Server Gateway Access server message RJE server message DHCF server message A 4 Interpreting System Messages ...

Page 107: ...ere error IDENT Is the identification of the message text TEXT Is one or more lines of information A 2 1 Interpreting OpenVMS and DECnet Error Messages OpenVMS System Messages and Recovery Procedures lists and explains both the OpenVMS and DECnet error messages A 2 2 Interpreting Gateway Utility Error Messages DECnet SNA Gateway CT and ST Management lists and explains error messages you may receiv...

Page 108: ...M host reports these sense codes to the Gateway ST user without a Gateway ST related error message The IBM manual System Network Architecture Formats contains a key to these sense codes Table A 2 contains information about some of the common IBM SNA sense codes Table A 2 Sample IBM Sense Codes IBM SNA Sense Code Code Meaning Gateway Meaning X 08xx Request reject You are unable to connect to IBM fo...

Page 109: ...te off OPCOM dd mmm yyyy hh mm ss cc Message from user SYSTEM on nodename DECnet SNA event 266 0 Gateway initialization From node aa ssss nodename dd mmm yyyy hh mm ss cc SNA gateway management Severity informational Started DECnet SNA Gateway ST V1 1 OPCOM dd mmm yyyy hh mm ss cc Message from user SYSTEM on nodename DECnet SNA event 266 0 Gateway initialization From node aa ssss nodename dd mmm y...

Page 110: ...After you load and initialize the software without error you will see the following display OPCOM dd mmm yyyy hh mm ss cc Message from user SYSTEM on nodename DECnet SNA event 266 0 Gateway initialization From node aa ssss nodename dd mmm yyyy hh mm ss cc SNA gateway management Severity informational Complete status success When the IBM system responds to the Gateway ST you see the following displ...

Page 111: ...s test and load sequence is progressing The DEC MicroServer also uses this display to Show that the unit is connected to the electrical supply Report any errors that the internal test detects Indicate the progress of a dump sequence Figure C 1 shows the location of the display on the control panel of the DEC Microserver The following sections describe the DEC MicroServer display The DEC MicroServe...

Page 112: ...E 3 C 1 Power Up Sequence On power up the DEC MicroServer performs the following actions Lights the decimal point of the display Tests the display Tests the internal circuitry Asks for software to be loaded Receives the software Runs the software C 2 The DEC MicroServer Display Panel ...

Page 113: ...is loaded across the Ethernet This value shows that the load is taking place 3 The load has failed because no load host responded The DEC MicroServer will wait before sending the message again Circling pattern two segments light at a time Software running normally C 1 1 Normal Power Up Sequence Without Retry In a normal load sequence the display shows one of the following values 1 or 2 C 1 2 Power...

Page 114: ...DEC MicroServer dumps the system s contents across the Ethernet to the host As with the power up sequence the DEC MicroServer might have to retry sending its request for a host to receive the dump This is reflected in the values that appear on the display C 2 1 Normal Dump Sequence Without Retry In a normal dump sequence the display shows the following 5 6 The display then continues with a power u...

Page 115: ...each value For detailed information about resolving the problems indicated by each of these codes refer to the DECnet SNA Gateway for Synchronous Transport problem solving information in Chapter 1 Table C 3 Error Code Values Display Value Meaning F Fault detected in the DEC MicroServer Contact Digital Customer Service E Ethernet connection fault either within the DEC MicroServer box or between the...

Page 116: ......

Page 117: ...commands to Control the operation of the system Get information Test the communications line s Section D 1 provides a summary of the remote console commands Section D 2 describes how to logically connect a terminal as a remote console Sections D 4 through D 10 describe the remote console s features and commands D 1 Command Summary Table D 1 shows the format of the remote console commands Table D 1...

Page 118: ...onnect from a load host that runs OpenVMS perform the following steps 1 Log in 2 Issue the following command to invoke NCP RUN SYS SYSTEM NCP 3 Enter the remote console command CONNECT NCP CONNECT NODE node name Replace node name with the node name of the DEC Microserver If there is a service password to protect the console use the following form of the CONNECT command NCP CONNECT NODE node name S...

Page 119: ...mands BOOT DUMP TEST D 5 Testing the DEC MicroServer The remote console TEST command has two formats that you can use to test the DEC MicroServer The first format lets you test the synchronous communications ports their modem control lines and the adapter cables The second format allows you to run continuous tests of the DEC MicroServer The first format of the remote console TEST command is TEST t...

Page 120: ... and give examples of their use D 5 1 Data Loopback Tests The data loopback tests use a connector in the communications path This loopback connector joins the transmit and receive paths and enables all information sent to be returned The tests send data along the line and wait for the looped data to return The returned data is then compared with the transmitted data Differences between the two ver...

Page 121: ...OPBACK CH1 MANUAL Use the first command if your modem recognizes the local loop modem signal Use the second if you have to manually set the modem to loopback mode for example by pressing a switch on the modem Chapter 2 provides more information on using these commands to test a communications line D 5 2 Modem Signal Tests The modem signal tests check the modem signals between the DEC MicroServer a...

Page 122: ...r SP 3 If the test is successful the following message appears on your terminal Successful Modem Signal Loopback on Channel n If the test fails the following message appears on your terminal Modem Signal Loopback Failed on Channel n Modem signal tests can be used to isolate a faulty adapter cable For example you can attach the 50 way loopback connector to the DEC MicroServer s synchronous port and...

Page 123: ... test cannot determine the type of cable it displays the following message Unsupported Cable on Channel n Cable Code xxxx If this message appears for a supported cable check that the cable is correctly connected to the socket and then retry the test If the message appears again the adapter cable is probably faulty D 5 4 Soak Testing the DEC MicroServer The DEC MicroServer s internal tests are usua...

Page 124: ...ice password as a 16 digit hexadecimal number STATE Displays the current system state This system state can be one of the following Halted Requesting Boot Booting Deferring Boot Requesting Dump Dumping Deferring Running The following is an example of the display the SHOW PASSWORD command produces SHOW PASSWORD Service Password FEFEFEFEFEFEFEFE The following is an example of the display the SHOW ST...

Page 125: ...ually use the DEC MicroServer s DUMP switch to perform a system dump you can also use the remote console command DUMP The DUMP command causes the DEC MicroServer to 1 Send a dump request on the Ethernet and wait for a host node to reply 2 Send the contents of memory including the internal error log to the host node that answers the request 3 Run its internal test and reboot when the dump is comple...

Page 126: ...so has a prompting mode If you do not enter a password after the command but simply press Ret the system prompts you for a password The system does not echo the password you enter The system then prompts you for verification Enter the password again As with all passwords you should change the service password regularly This helps to maintain security To change the password simply use the SET PASSW...

Page 127: ...ommands and their formats use the HELP command HELP This command produces a display similar to the following Available Commands B oot DU mp HA lt H elp More Test SE t PASSWORD SH ow PASSWORD STATE TE st keyword keyword_qualifiers UPPERCASE required letters lowercase optional letters Optional Select One The remote console recognizes additional commands but these are for use by Digital support peopl...

Page 128: ......

Page 129: ...ynchronous communication link The DEC MicroServer SP can support data communications speeds up to 19 2K bits per second Table E 1 shows the only configuration available with the DEC MicroServer SP Table E 1 The DEC MicroServer SP Port Data Speed in bits per second Number of Lines Port Up to 19 2K bps 1 0 The DEC MicroServer can support data communication speeds up to 256K bps The range of speeds i...

Page 130: ...ow many lines you can use 4 Use only the ports listed for your speed band For example you might want to use one DEC MicroServer line at 64K bps and another at 128K bps In this case the maximum data speed is in the middle band Only two ports 0 and 1 can be used E 2 Other Configurations The configurations listed in Table E 2 are the only ones supported by Digital Equipment Corporation Other configur...

Page 131: ...al name refers to wires A and B of a twisted pair The description of the V 24 RS 232 C adapter connector includes both the male and the female connectors Table F 1 V 35 34 Way Square Connector Male Pin Signal Name Pin Signal Name a TX CLOCK B r RX DATA A b DTE GROUND s TX DATA B c RTS t RX DATA B d CTS u AUX CLOCK A e DSR A v RX CLOCK A f DCD I A w AUX CLOCK B h DTR x RX CLOCK B j RI y TX CLOCK A ...

Page 132: ...0 DTR 5 CTS 21 REM LOOP 6 DSR 22 RI 7 GROUND 23 SPEED SELECT 8 DCD 24 CLOCK 15 TX CLOCK 25 TEST INDICATE Table F 3 V 24 RS 232 C 25 Way D Type Adapter Male and Female Pin Signal Name Pin Signal Name 2 TX DATA 15 TX CLOCK 3 RX DATA 17 RX CLOCK 4 RTS 20 DTR 5 CTS 22 RI 6 DSR 24 CLOCK 7 GROUND 25 TEST INDICATE 8 DCD F 2 Adapter Cable Pin Signals ...

Page 133: ...p display for C 4 retry dump display for C 4 error codes C 5 halt codes C 5 power up normal load display for C 3 retry load display for C 3 power up sequence C 2 DEC MicroServer loopback tests 2 10 DEC MicroServer power up failure 1 3 DEC MicroServer problems wrong software loaded 1 21 DEC MicroServer remote console commands D 1 to D 11 DECnet configuration database DEC MicroServer entries for 1 2...

Page 134: ... 1 3 faulty synchronous port 1 8 Gateway ST boots dial up fails 1 9 Hardware problems cont d Gateway ST loads but some lines do not come up 1 13 line counter Receive failures 1 11 remote modem connection failure 1 7 Help at remote console D 11 I IBM parameters 1 27 1 29 IBM sense codes 1 46 A 6 IBM traces 3 2 to 3 5 generalized PIU 3 3 SDAID Trace program 3 4 VTAM buffer contents 3 3 VTAM internal...

Page 135: ... executor 2 7 remote 2 6 P Physical unit level traces 3 2 Power up failure 1 3 Problems reporting 5 1 R Receive failures CRC Cyclic Redundancy Check errors 1 11 Frame too long errors 1 12 Receive overrun errors 1 11 Remote console clearing the password D 10 connecting to the DEC MicroServer D 2 detaching from the DEC MicroServer D 3 setting the password for D 9 showing the password for D 10 Remote...

Page 136: ... 1 29 station id entry in 1 29 SNANCP loopback tests 2 9 to 2 10 cable 2 10 controller 2 9 DEC MicroServer 2 10 modem 2 10 SNANCP messages A 5 SNAP messages A 5 SNATRACE messages A 5 Software Performance Report SPR 5 4 Synchronous port problem 1 8 System messages event 1 40 IBM sense codes 1 46 A 6 T Traces 3 1 to 3 5 Circuit level 3 1 Gateway Management 3 1 generalized PIU 3 3 IBM 3 2 to 3 5 Phys...

Reviews:

No comments

Brands by name

Popular brands

Load more brands