Universal StationX Troubleshooting, UX13-400
Contents
1. The network architecture and configuration influences the type and number of active Internet daemons Using the descriptions covered in TCP IP Services and Processes compare the current process listing with the expected Internet daemon activity Check these items if you suspect missing daemon processes 1 Is the daemon running note some daemons run only as needed 2 Is the daemon executable 3 Start the daemon manually in an HPterm window for tcpd or telnetd start using the debugging options as listed in the man pages The basic syntax to invoke the daemons in debug mode is etc tcpd d foff lt RETURN gt etc named d lt RETURN gt etc ftpd d lt RETURN gt trpt in conjunction with telnet Continued on next page 34 Universal Station Troubleshooting 12 93 3 5 Troubleshooting Steps continued Determine the name server Using the nslookup method Using the look for server link method To make sure the administrative node is running find out which node the host or gateway is using to resolve addresses There are several methods to determine the nameserver node used by a host to provide resolve the TCP IP address from the hostname query The first method attempts the nslookup command of NS ARPA Services Network Services to resolve an address query where the nameserver will respond with the query result and identify itself by hostname and TCP IP address This command exercis2. R2 ED a B L1 DI OD A Ca R3 SO z 5 RO s DREI 2 D Q a lt 60 SCSI Interface Modem See Note 3 Hard Drive and DAT Drive WSIVO ASSY NO 51304791 100 REV B Terminal Printer Video uk Mi i See Note 1 See Note 2 1 EN Access Printer Unit Note 1 Not normally used Can be used to connect a dumb terminal for in depth troubleshooting of the coprocessor Note 2 Not normally used Can be used to connect a VGA monitor for in depth troubleshooting of the coprocessor Note 3 Connects to free standing modem for TAC coprocessor troubleshooting access 10232 14 Universal StationX Troubleshooting 12 93 2 5 Determining if UNIX is Operational Testing with a UNIX console Observe the attempted boot What to do next If you have a loss of display problem the first step is to determine if UNIX is operational Because you cannot communicate with the coprocessor through the Universal StationX keyboard and monitor you must connect a UNIX console directly to the coprocessor Then you can observe the boot process and try keyboard input Connect a console terminal to the coprocessor as described in the previous subsection Turn on power to initiate the bootload process Watch the console terminal and observe whether the bootload process starts and if so how it terminates and what error messages if any are reported A bootload
3. Table 2 5 Meaning of the Display Indicators r m o Indication Meaning On or blinking Network transmit in progress On or blinking Network receive in progress On or blinking Disk access in progress Pulsing Operating system running heartbeat Off Always off if operating system is running Off Always off if operating system is running Off Always off if operating system is running TOT MUOD P Off Always off if operating system is running Continued on next page 16 Universal Station Troubleshooting 12 93 2 6 Coprocessor Diagnostic LED Status Display continued Display when UNIX is running No heartbeat Display when UNIX is not running Hardware failure Table 2 5 shows the normal behavior of the LEDs in the display The operating system running flag LED D will normally pulse as an indication of a heartbeat indicating that the UNIX kernel is running LEDs A B and C will normally blink at intermittent rates to indicate the activities shown LEDs E F G and H will always be off in normal operation If LED D the heartbeat LED is not pulsing at a regular rate approximately 1 second on and one second off try resetting the node by turning power off for a few seconds and then turning it back on again If the heartbeat doesn t start within 2 minutes continue with the following procedures You may be able to obtain add
4. No display interaction Usually indicates a failure of the TPDG TPDG VO Touchscreen or Keyboard CAUTION This problem can possibly be the result of attempts to interact with a window that is not the current active window Ensure that the cursor is physically positioned within the window before attempting to interact with the application running there 12 93 Universal Station Troubleshooting 9 2 2 Personality Load Problems The personality load process The Universal Station Personality is stored on disk media maintained by the coprocessor When a load operation is requested by depressing the LOAD key the following steps occur Table 2 2 Steps in the Universal StationX Load Process Step Action 1 The prompt W 1 2 3 4 N is presented on the screen The user presses W and then the ENTER key to initiate a load of Universal StationX by the coprocessor 2 The K2LCN firmware sends a message to the coprocessor requesting a load of the default Universal StationX Personality software 3 The coprocessor program Icndaemon locates the Universal StationX Personality files and loads them into K2LCN memory Dialog messages are presented on the screen indicating the progress of the load 4 The coprocessor program Icndaemon sends an EXECUTE message back to the K2LCN firmware 5 The K2LCN firmware checksums the image in memory and then transfers
5. About This Publication The Universal Stations up2 s up2 X Troubleshooting Guide provides the preliminary troubleshooting information necessary to assist Honeywell and customer technical personnel to isolate a TDC 3000X Universal StationX problem to a particular component or area It is not intended to be a service manual it is intended to help identify the area that requires service For service information refer to the Universal StationXService manual in this binder 12 93 Universal Station Troubleshooting Universal Station Troubleshooting 12 93 Table of Contents SECTION 1 GENERAL INFORMATION ese ee ee ee ese ss ke ek ee nn nn nn an ER RE RR RR AR Re ae ann RE RR RR Re 1 1 1 OVEeVieW EO EE N N Ed 1 1 2 Universal Station Basie da 3 1 3 High Level Diagnosis oooooccccconcccconnnoccnnnnnnccnnnnnnccnnonanccnnnnnncrnnnnnnrrnnnnnners 6 SECTION 2 UNIVERSAL STATIONX PROBLEMS AND FIXES ese ese see ee ee ee ee 9 2 1 Display Problems ER RE RE EE OE 9 2 2 Personality Load Problems iese see ee de ee RR ee RR ee dd ee RR ee ee RR ee ee ee ee 10 2 3 UNIX Software Problems ee sesse eed de de RA ER AA ee ee ed ee ee 12 2 4 Connecting a Coprocessor Console AA ee 13 2 5 Determining if UNIX is Operational 422444snnnnnnnnnnennnnnnnnnnnnenn 15 2 6 Coprocessor Diagnostic LED Status Display iii ee sek se de de ke ee ee 16 2 7 Troubleshooting if UNIX is not Operational i
6. s function and interaction with the other protocols The tools provided for this are landiag netstat ping dtcb and mdb The netstat tool provides network status information used to locate problems at the network layer The ping tool verifies a remote system to be active and available on the network and secondarily confirms a functional path physical layer between the systems Listing the current To list all currently running processes use the process status command ps processes and arguments to help confirm proper process activity Determine the daemon s that should be running and check the process status Remember many daemons are only active when a connection is open To list your processes type ps lt RETURN gt to produce this output PID TTY TIME COMMAND To list all processes type ps e lt RETURN gt to produce this output PID TTY TIME COMMAND To list full information on all processes type ps ef lt RETURN gt to produce this output UID PID PPID C STIME TTY TIME COMMAND To view one page at a time type ps ef more lt RETURN gt use lt space gt to page down lt RETURN gt to line down To locate a specific process type grep ProcessName ps ef lt RETURN gt to produce this output UID PID PPID STIME TTY TIME COMMAND Continued on next page 12 93 Universal Station Troubleshooting 33 3 5 Troubleshooting Steps continued Compare current with expected status
7. Black Canyon Highway Phoenix Arizona 85023 3099
8. Universal Station with Extensions SERE A Workstation Interface 12 93 Universal Station Troubleshooting vii References Publication Publication Binder Binder Title Number Title Number Universal Station Service US13 400 LCN Service 1 TDC 2060 Five Ten Slot Module Service LC13 400 LCN Service 1 TDC 2060 TDC 3000X Universal Station UX03 400 Universal Station TDC 2093 Specification and Technical Data Universal Station X User Guide UX09 400 Universal Station TDC 2093 Universal StationX System Administration UX11 400 Universal Station TDC 2093 Manual Universal StationX Service UX13 410 Universal Station TDC 2093 Universal StationX Ergonomic Service UX13 430 Universal Station TDC 2093 Troubleshooting HP UX Systems 92453 90026 Hewlett Packard Manual Error Diagnosis and Recovery viii Universal StationX Troubleshooting 12 93 Section 1 General Information 1 1 Overview Introduction Intended audience What is covered The Universal StationX Troubleshooting Guide provides information to help you isolate a Universal Station UXS problem to a particular component or area It is not intended to be a service manual it is intended to help identify the area that requires service This guide is intended for Honeywell and customer technical personnel It is assumed that the users of this document are experienced in the installation configuration and usage of traditional Universal Stations have been exposed to
9. connector will fit on J5 and the cable extends the interface out of the I O card cage so that amodem cable can be connected without shutting down the station Appendix B includes a wiring diagram for a modem cable that will work with many modems Consult with TAC for specific situations If your modem has option switches check with TAC for the appropriate settings As we mentioned earlier in conjunction with the console terminal interface it is important to try these interfaces before trouble necessitates their use If you anticipate using a modem for troubleshooting do a trial when the system is running if possible to ensure that the configuration cable and modem are proper 12 93 Universal Station Troubleshooting 23 24 Universal Station Troubleshooting 12 93 Section 3 Troubleshooting the Ethernet LAN 3 1 Local Area Networking LAN Overview Related publications Network standards IEEE 802 standard The Hewlett Packard publications covering ARPA NFS and NS Services detail the use and configuration of networking services available on the TCP IP Local Area Network LAN These publications are not required to troubleshoot faults with the physical components such as loose cable connections or improper termination This manual covers the tools and techniques required to locate and correct common internet faults with the physical layer of the OSI Open System Interconnection reference model Ad
10. control The node begins startup and the message NODE STARTING UP is displayed Continued on next page 10 Universal Station Troubleshooting 12 93 2 2 Personality Load Problems continued Failure of the Table 2 3 shows some of the failures that can occur during a Universal personality load StationX Personality load and suggests corrective action for each Table 2 3 Correcting Universal Station Personality Load Failures Symptom Possible Cause and Corrective Action No prompt K2LCN Keyboard or TPDG is not functioning Check K2LCN TPDG Keyboard No load messages K2LCN is not functioning properly WSI is not operational coprocessor is not running lcndaemon is not running or WSI interface is not operational Ensure that coprocessor is running properly Login window should be displayed at the bottom of the screen If it is not proceed to UNIX Software Problems Attempt to load from a local Bernoulli or select N at the prompt to ensure that a standard Universal Station personality OPR ENG or UNP can be loaded as opposed to the Universal Station Personality Load completes personality fails to start or run Personality image may be corrupt on disk media personality may be wrong version or LCN problem prevents startup Attempt to load from a local Bernoulli or select N at the prompt to ensure that a standard personality can be loaded If this fails tro
11. of server node failure Each system has a minimum etc hosts file and a etc resolv conf file to configure host to query the appropriate name server pointer THIS FILE IS LOADED ON ALL to TCP IP HOSTS NOT RUNNING named THE NAMED DAEMON resolv conf 129 30 3 20 Network 129 30 3 129 30 3 7 hosts 129 30 121 46 129 30 116 16 Network 129 30 114 Network 129 30 116 Two name servers with host infomation using named boot The Master is a router in Minneapolis and serves as our secondary nameserver The Slave is a local gateway router and serves as our primary nameserver Changes to the name service are performed at the Master server and automatic updates for all Slaves are transmitted across the internet 13225 12 93 Universal Station Troubleshooting 29 3 3 TCP IP Services and Processes What is a daemon TCP IP daemons The server process necessary to provide TCP IP services These processes are run in the background transparent to user on TCP IP hosts The daemons provide the following e Control user access to network resources e Respond to requests for data e Record statistics concerning health of the network e Control external communication pathways outside the local network Daemons used to provide TCP IP services are e routed dynamically maintains network routing tables It starts at boot time on all nodes but is stopped on host nodes after routed initializes the local routing table Gateway nodes run t
12. publications You can communicate your thoughts to us by fax mail or toll free telephone call We would like to acknowledge your comments please include your complet name and address BYFAX Use this form and fax to us at 602 313 4108 BY TELEPHONE In the U S A use our toll free number 1 800 822 7673 available in the 48 contiguous states except Arizona in Arizona dial 1 602 313 5558 BY MAIL Use this form detach fold tape closed and mail to us Title of Publication Universal StationX Troubleshooting Issue Date 12 93 Publication Number UX13 400 Writer R Evans COMMENTS RECOMMENDATIONS NAME DATE TITLE COMPANY ADDRESS CITY STATE ZIP TELEPHONE FAX If returning by mail please tape closed Postal regulations prohibit use of staples Communications concerning technical publications should be directed to Automation College Industrial Automation and Control Honeywell Inc 2820 West Kelton Lane Phoenix Arizona 85023 3028 BUSINESS REPLY MAIL FIRST CLASS PERMIT NO 4332 PHOENIX ARIZONA POSTAGE WILL BE PAID BY Honeywell Industrial Automation and Control 2820 West Kelton Lane Phoenix Arizona 85023 3028 Attention Manager Quality NO POSTAGE NECESSARY IF MAILED IN THE USA Cut Along Line Honeywell Industrial Automation and Control Helping You Control Your World Honeywell Inc 16404 North
13. that you have a fundamental understanding of the components and processes of a Universal StationX before attempting to troubleshoot the station This subsection will describe the main functional components hardware and software of the Universal StationX and describe how these components operate and interact Primary functional The Universal StationX is a hybrid combination that includes both a components of a standard Universal Station and a coprocessor that provides the full Universal StationX functional services of a UNIX workstation Figure 1 1 shows the primary functional components of a Universal StationX and their physical relationships Figure 1 1 Universal StationX Primary Functional Components Display Monitor Bernoulli Disk TDC 3000 Printer Pointing Device Keyboard l Laser Printer Gee TPDG Communications Modem gt mmm DAT Tape Drive HP 9000 382 gt WSI Hard Disk Drive 802 3 LAN Interface x TDC 3000 LCN Interface K2LCN gt Continued on next page 12 93 Universal Station Troubleshooting 3 1 2 Universal StationX Basics continued TPDG functions WSI functions K2LCN functions Backplane interaction UXS Universal Personality As shown in Figure 1 1 the primary Universal StationX user interactive interfaces display keyboard and pointer device are supported by the Turbo P
14. the Universal StationX provides a resolution of 1280 by 1024 pixels which is much greater than the standard Universal Station 640 by 448 pixels Therefore a standard full screen Universal Station display can be presented on a Universal StationX screen using less than 1 4 of the display surface When Universal Station is operating in the X Window mode this method of display for the standard or native LCN display window is the default This window shares the display with other windows and can be manipulated sized and moved the same as for all other windows When the X Window manager is running the display data generated by the Universal StationX Personality is presented on the screen in its own individual window which shares the display surface with other windows owned by other programs running in the UNIX environment on the coprocessor If for any reason the coprocessor should fail or be intentionally shut down the TPDG automatically reverts to a mode of operation identical to that of the standard Universal Station In this mode the native window display data occupies a full screen image The failure of the coprocessor has no other impact on the Universal Station Personality Similarly shutdown or failure of the Universal StationX Personality has no effect on the software programs running on the coprocessor A brief disruption of displays can occur whenever the K2LCN processor is reset as this requires the TPDG to also be reset
15. the correct installation and configuration of the Universal Station Refer to the LCN System Installation manual SW20 400 in the LCN Installation binder You may also find helpful information in the appropriate Universal StationX Service manual UX 13 410 old furniture or UX13 430 new furniture Both are in the Universal Station binder Ensure that all external cable connections for power LCN LAN and peripheral devices keyboard and mouse track ball as well as internal devices monitor floppy Bernoulli disk and DAT tape are properly installed Second determine the nature of the difficulty and the associated platform The functions provided by Universal StationX are supported on two separate hardware platforms that are integrated in the same electronics enclosure Most TDC 3000X functions are provided by a standard Universal Station kernel and provided by the K2LCN TPDG electronics The control of all windows operating mode functions is provided by the WSI coprocessor Use this differentiation as a basic guide to determine which processor is affected Continued on next page Universal Station Troubleshooting 12 93 1 3 High Level Diagnosis continued Visual inspection example Functional Testing Summary of initial checks For example if the standard cursor gt is displayed in the upper left corner of the display screen after reset and the node responds to the LOAD key with the correct prompt the
16. to Send 6 6 Data Set Ready 7 7 Signal Ground 8 e 8 Data Carrier Detect 9 20 Data Terminal Ready D 9 Female D 25 Male Notes 1 Dashed connections may or may not be required by your terminal 2 Connections on pins 2 and 3 may need to be reversed at one end and or the D 25 may need to be a female connector depending on the characteristics of your terminal 13052 12 93 Universal Station Troubleshooting 41 B 2 Modem Cable Suggested cable for modem connection Figure B 2 Modem Cable UXS Connector Modem Connector WSI VO J5 1 1 Frame Ground Transmitted Data 2 2 Transmitted Data Received Data 3 3 Received Data Pa ae 4 4 Request to Send Ground S gt 5 Clear to Send 6 6 Data Set Ready 7 7 Signal Ground 8 8 Data Carrier Detect 9 20 Data Terminal Ready D 9 Female D 25 Male 13051 42 Universal StationX Troubleshooting 12 93 Index A B C Connecting a Coprocessor Console Terminal 3 Console Terminal Cable 4 Coprocessor Diagnostic LED Status Display Display when UNIX is not running 17 Display when UNIX is running 17 Function of the display 6 Hardware failure 7 Interpreting the display 6 Location of the display 16 No heartbeat 7 Correcting Universal Station Personality Load Failures 77 D E F G Degraded Operation Causes and things to check 2 Definition 2 Determining if UNIX is Operation
17. topologies protocols and media Continued on next page 12 93 Universal Station Troubleshooting 25 3 1 Local Area Networking LAN Overview continued How TCP IP fits OSI The TCP IP protocol suite s relationship to the ISO OSI model and IEEE s 802 standard is shown below The software utilities and their test programs perform discreet functions corresponding to each OSI layer ISO OSI IEEE 802 TCP IP TCP IP MODEL STANDARDS PROTOCOLS TESTS APPLICATION Ty LAYER 7 tp PRESENTATION telnet with trpt LAYER 6 SESSION TELNET LAYER 5 netstat TRANSPORT LAYER 4 mbd NETWORK LAYER 3 DATA LINK LAYER 2 PHYSICAL LAYER 1 13226 Layer 7 This layer consists of application programs and serves as the window or network interface through which all exchange of data occurs between communication users Layer 6 This layer performs data conversions and ensures that data is exchanged in an understandable format Layer 5 This layer sets up and terminates communications on the network and manages the dialogue between users and systems Layer 4 This layer controls the quality of data transmission It is mainly implemented by communications software protocols such as TCP Layer 3 This layer determines the path that the data will take through the network Packets of information contain routing information that aid passage through the network Layer 2
18. Honeywell Universal Station X Troubleshooting UX13 400 Honeywell Universal StationX Universal StationX Troubleshooting UX13 400 12 93 Copyright Notices and Trademarks Printed in U S A Copyright 1993 by Honeywell Inc Revision 01 December 15 1993 While this information is presented in good faith and believed to be accurate Honeywell 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 Honeywell liable to anyone for any indirect special or consequential damages The information and specifications in this document are subject to change without notice This document was prepared using Information Mapping methodologies and formatting principles TDC 3000 is a trademark of Honeywell Inc Universal StationX is trademark of Honeywell Inc Information Mapping is a trademark of Information Mapping Inc OSF OSF Motif and Motif are trademarks of the Open Software Foundation Inc UNIX is a trademark of AT amp T Technologies Inc Macintosh is a trademark of Apple Computer Inc TotalPlant is a trademark of Honeywell Inc Windows is a trademark of Microsoft Corporation Honeywell Industrial Automation and Control Automation College 2820 West Kelton Lane Phoenix AZ 85023 602 789 5669 Universal Station Troubleshooting 12 93
19. This level packages data for transmission and unpackages it for receipt Layer 1 This layer defines the physical connection connector and pin assignments voltage levels and the initial cable connections between a computer and network and also controls the transmission of information 26 Universal StationX Troubleshooting 12 93 3 2 TCP IP Overview Standard protocol Protocol vs physical device TCP IP utilities Hosts gateways bridges and routers The Transmission Control Protocol TCP and the Internet Protocol IP referred to as TCP IP provide services allowing dissimilar computer systems to communicate and exchange data The original TCP IP development by the Defense Advanced Research Projects Agency DARPA has received widespread support from computer manufacturers of all types TCP IP protocols were designed to provide communications services over a variety of physical networks from computer networks to radio networks The protocols define how to send and receive messages but not what the physical device must do to send or receive messages This enables vendors to create device drivers specific to the hardware The utilities provided through TCP IP are telnet provides communications using the Telnet Protocol e ftp File Transfer Protocol transfers files to from a remote site e 1pr Remote Line Printer queues and prints files to shared printers e rcp Remote Copy of files betw
20. al Observe the attempted boot 15 Testing with a UNIX console 15 What to do next 15 Display Problems Incorrect display 9 No display 9 H J K L High Level Diagnosis Determining what has failed 6 Functional Testing 7 Introduction 6 Summary of initial checks 7 Visual inspection example 7 Visual inspection of Universal StationX 6 HP 9000 382 Display Status Codes 39 M N O Modem Cable 42 P Q R S T Personality Load Problems Failure of the personality load The personality load process 70 Troubleshooting if UNIX is Operational Check the Honeywell support software 9 Overview 19 U V Universal StationX Basics Backplane interaction 4 Behavior without Universal Station Personality 5 Behavior without UNIX X Windows 5 Coprocessor software 5 Introduction 3 K2LCN functions 4 LCN Native Window 5 Primary functional components of 3 TPDG functions 4 UXS Universal Personality 4 WSI functions 4 Universal StationX Problems and Fixes 9 UNIX is not Operational Disk failure 18 File system corruption amp Overview 18 UNIX Software Problems Categories of errors 12 Loss of display no login window 12 Loss of function 72 W X Y Z WSI I O Board Connector Locations and Functions 4 12 93 Universal Station Troubleshooting 43 44 Universal Station Troubleshooting 12 93 READER COMMENTS Honeywell IAC Automation College welcomes your comments and suggestions to improve future editions of this and other
21. and reinitialized 12 93 Universal StationX Troubleshooting 5 1 3 High Level Diagnosis Introduction Determining what has failed Visual inspection of Universal Station The Universal StationX functionality is designed to provide reliable display services and operator interaction with LCN and PIN Plant Information Network software simultaneously If the full functionality of the Universal Station is impaired the following guidelines should help in determining the basic cause of the problem The following procedures will help you determine the type of failure and the functional group of software or hardware where the problem exists Once the group has been determined you will find guidelines that indicate the suggested steps to take to correct the problem The first step in determining a failure cause is to locate the general area or group of functions that are not working properly This is accomplished by both visual inspection and functional testing of the Universal Station In most cases the differentiation between what works and what does not will be obvious to the user however there are some modes of failure or degradation of function that are unigue to Universal Station For this reason the user should always determine if the loss of function is associated with the coprocessor only the K2LCN environment only or both This step is important to determine the next appropriate action First verify
22. as monitored on the terminal begins with the copyright information This is followed by a self test the bootload of system software and initiation of internal processes A successful bootload ends with the prompt Console Login on the terminal screen If UNIX appears to be operational go to the subsection titled Troubleshooting if UNIX is Operational If UNIX does not appear operational continue with the next subsection to perform additional checks 12 93 Universal Station Troubleshooting 15 2 6 Coprocessor Diagnostic LED Status Display Function of the display Location of the display Interpreting the display The Diagnostic LED Display indicates the current status of the HP 9000 382 coprocessor The display consists of eight LEDs that provide information about the status of the hardware and the UNIX kernel The LED diagnostic display is located on the HP coprocessor board which is mounted as a daughter board on the WSI board The WSI board is located in Slot 2 of the Five Slot Module Figure 2 2 shows the location of the display A flashlight and small nonconductive mirror will help you view the display Figure 2 2 Coprocessor Diagnostic LED Display ITVTONONON0000000000000UOOOOO000000000000000UUT000N E WUUUUOOONOOOO000000000000000000000000 LED Diagnostic Display Coprocessor Daughter Board A PHHH gt WSI Board 51402026 100 K 10226
23. ctor list 00001000 Resetting all interfaces 00001001 Searching for console display 00001010 IODC test RAM under test 00001101 Console failure 00001110 Failed boot ROM checksum 00001111 Preloading memory for main test 00010000 Testing memory 00010001 Insufficient memory 00010010 ROM system failure 0001001 1 Boot error 00010100 Operating system 00010101 Not enough memory for OS 00010110 Failure during system scan 00100000 4mstimer problem Continued on next page 12 93 Universal Station Troubleshooting 39 A 1 WSI Coprocessor Diagnostic Display Status Codes continued Table of codes Table A 1 HP 9000 382 Display Status Codes continued continued LED Display Error Indication ABCDEFGH 00100001 EEPROM malformed 00100010 Failure of HP HIL circuit 00100100 Failure of HP IB circuit 00101000 Failure of DMA circuit 01000000 Failure of DIO interface 40 Universal StationX Troubleshooting 12 93 Section B Cables B 1 Console Terminal Cable Suggested cable for terminal connection Figure B 1 Console Terminal Cable UXS Connector Terminal Connector WSI VO J1 1 1 Frame Ground Transmitted Data 2 2 Transmitted Data Received Data 3 3 Received Data 4 at 4 Request to Send Ground 5 e 5 Clear
24. ditionally this manual suggests corrective actions for problems with the data link network and transport layers and identifies the appropriate Hewlett Packard publication The publications of interest are Publication Publication Title Number Networking Overview B1012 90003 Using ARPA Services B1014 90000 Installing and Administering ARPA Services B1014 90001 ARPA Berkeley Reference Pages B1014 90002 Installing and Administering NFS Services B1013 90001 Installing and Administering Network Services B1012 90001 The International Standards Organizations ISO has developed the Open System Interconnection OSI model A design by which individual components of the communications system may be replaced allowing computers from any vendors to exchange data without regards to the operating system or processor hardware The approach was to divide the communications system into its functional components and specify a hierarchical method of designing protocols so that each layer connects only to the layer above and below it This design structure allows an ethernet cable to carry multiple protocols simultaneously The Institute of Electrical and Electronic Engineers established standards that specify interface and protocol specifications for various LAN topologies The 802 standard corresponds with the Physical and Data Link layers of the OSI model and provides a common interface to the higher layers of software over networks with differing
25. e coordinated with TAC to ensure modem compatibility and to schedule time A discussion of the problem symptoms and history should precede a modem session Configure the modem Before a modem session you must configure the modem port Use the port procedure in Table 2 7 to configure the modem port This procedure requires the coprocessor root password Table 2 7 Procedure to Configure the Modem Port Step Action 1 Log in as engineer 2 Position the cursor in the workspace where there are no windows and press and hold down the left mouse or trackball button to display the Engineer Menu 3 As shown in Figure 2 3 while holding down the mouse or trackball button select System Menu then Configuration and then System Configuration Release the mouse or trackball button 4 In response to the Password prompt enter the coprocessor root password 5 Use the down arrow key to select Peripheral Devices and then press lt RETURN gt 6 Use the down arrow key to select Add a Terminal or Modem and then press ENTER 7 Use the down arrow key to position the cursor block in front of modem and then enter x in that position to select modem 8 In response to the question Do you want the device for calling out enter n 9 In response to the question Is this a CCITT modem provide the appropriate response y or n In the United State
26. een e Check for the UNIX login banner at the bottom of the screen 12 93 Universal Station Troubleshooting 7 Universal StationX Troubleshooting 12 93 Section 2 Universal StationX Problems and Fixes 2 1 Display Problems No display Incorrect display This problem is usually indicative of a failure of either the TPDG and TPDG V O modules or the monitor As a minimum you should observe a cursor on the screen after the node has been powered on or reset Remember that all displays for both the K2LCN and coprocessor are provided by the TPDG and that the coprocessor is not required to obtain basic Universal Station display functions If a cursor is visible a login window should appear on the bottom portion of the screen If the login window fails to appear it is an indication that the coprocessor is not functioning properly Proceed to the subsection titled UNIX Software Problems This category includes a variety of possible symptoms A few are given in the following table Table 2 1 Incorrect Display Types and Possible Causes Symptom Possible Cause Incorrect colors Can be caused by of a failed monitor TPDG or TPDG VO or possible incorrect or corrupted system software configuration Fuzzy wavy displays Usually indicates a failed monitor or TPDG Refer to the Universal StationX Service manual UX13 410 old furniture or UX13 430 new furniture for Universal StationX monitor service
27. een machines e rexec Execution of commands on a remote system e rlogin Login to a remote host e remsh Execute a shell command on a remote host Computers that use the TCP IP protocols to communicate are called TCP IP hosts A host can also be a gateway bridge or router to another network Gateways connect two incompatible networks providing a physical link that 1s transparent to the users Communications between users on separate networks is routed through the gateway that provides translation of all seven OSI protocol layers For example a gateway must translate the protocols and the physical interface connections when joining TCP IP over Ethernet to Apple Computer s AppleTalk protocol over LocalTalk cabling Bridges connect two similar networks allowing each to function independently Traffic addressed to users on the remote network is routed across the bridge connection yet local traffic is isolated to its respective network Routers connect networks with different protocols but similar cabling systems The router provides protocol translation only Continued on next page 12 93 Universal StationX Troubleshooting 27 3 2 TCP IP Overview continued Host names How etc hosts is used Name servers Overview of BIND The Internet Protocol s ability to correlate alias names host names to address numbers allows users to reference systems on the LAN by a name assigned on the basis of the com
28. er information on appropriate actions to take in the case refer to the Hewlett Packard reference manual Troubleshooting HP UX Systems Error Diagnosis and Recovery Another potential reason for a nonfunctional UNIX system is the failure of the local disk storage unit When the Universal StationX is powered on the HP 9000 382 firmware will automatically search for a boot file on all attached disk and tape units This search is indicated on the console device If the local disk storage device has failed the system will remain in system search mode indefinitely until appropriate action is taken The recommended method of recovering from this failure is to replace the disk unit with a new unit provided by Honeywell The new unit if provided by Honeywell will have the complete basic Universal StationX software suite already installed Once this action has been taken the original system configuration and user files can be restored from the most recent backup 18 Universal StationX Troubleshooting 12 93 2 8 Troubleshooting if UNIX is Operational Overview If you do not get the login banner on the Universal StationX console and observation of the diagnostic LED display indicates that UNIX is running the next step is to check the status of Honeywell Universal StationX support software The console terminal connection described in subsection 2 4 is required to ascertain this information Check the Ho
29. eripheral Display Generator TPDG board Physical interfaces are provided by the companion TPDG VO board In addition the TPDG provides support for Bernoulli cartridge disk and TDC 3000 console printer options This functionality is the same as that provided in the standard Universal Station The UNIX workstation support is provided by the WSI board This board has a coprocessor board mounted on it The coprocessor is a Hewlett Packard 9000 382 The HP 9000 382 coprocessor uses a 400 MB hard disk drive for program and data storage an IEEE 802 3 compatible Local Area Network LAN interface and optional peripheral devices for printing tape backup and remote communications over telephone lines Physical interfaces are provided by the WSI I O board The TDC 3000X software the Universal StationX personality executes in the K2LCN which also provides the LCN interface in conjunction with the LCN VO board All three electronics modules the TPDG WSL and K2LCN are connected together by a standard Five Slot Module backplane The backplane provides Direct Memory Access DMA to the memory RAM on the K2LCN for the TPDG and WSI boards All bus arbitration and control is provided by the K2LCN The full Universal StationX functionality involves software in both the K2LCN and the coprocessor The K2LCN provides the execution environment for the Universal StationX Personality This software personality is identical to the standard Uni
30. es network communications and will identify hosts that are not registered with the name service nslookup example nslookup ac_usx2 lt RETURN gt Returns this response from the nameserver Name Server fishery honeywell com Addresses 129 30 3 416 Name ac usx2 iac honeywell com Addresses 129 30 114 22 The second method is to list the etc directory and look for a link to the etc hosts file The link shows the hostname of the administrative node Type is S etc lt RETURN gt Look for this link indication hosts gt tcp_admin etc hosts tcp admin gt admin_host Where admin_host will be the hostname of the administrative node Continued on next page 12 93 Universal Station Troubleshooting 35 3 5 Troubleshooting Steps continued Check the Where admin_host will be the hostname of the administrative node administrative nameserver Now see if the name server administrative node is operational Type ping admin_host count 5 lt RETURN gt The administrative node response should resemble this example PING admin host 0 data byte 8 bytes from 129 30 114 2 icmp_seq 0 8 bytes from 129 30 114 2 icmp_seq 1 8 bytes from 129 30 114 2 icmp_seq 2 8 bytes from 129 30 114 2 icmp_seq 3 8 bytes from 129 30 114 2 icmp_seq 4 admin_host PING Statistics 5 packets transmitted 5 packets received 0 packet loss If there is packet loss noted but it is less than 100 several possibilitie
31. h creates a new daemon process etc telnetd assigned to interpret the user s internet commands This process will die at completion of the logout sequence 12 93 Universal Station Troubleshooting 31 3 4 Troubleshooting Steps Overview of troubleshooting process Initial tests Detailed protocol tests The LAN administrator will be a valuable resource when troubleshooting coprocessor LAN communication problems The goal of the troubleshooting process is to identify the problem node Documentation of the network s design and layout is extremely important as are any changes you may make as a result of the corrective actions Inform the network administrator of any changes including descriptions of the problems indication suspected component s and the resolution or work around with printed copies of configuration changes It is important during the initial tests to locate the suspect node and if possible the protocol layer before proceeding to the detailed software testing The initial procedures test the physical hardware and will quickly identify the problem node Specific tests are performed at the suspect node to confirm the fault and determine the corrective action The software tests produce a significant amount of data and require time to interpret Always test on the principal of from the local to the remote Confirm local communications with yourself through software loopback connection and progre
32. his daemon continuously e inetd this is a single process started by etc rc at boot and serves as a super daemon invoking the appropriate Internet servers as services are requested The inetd process must be running to use the servers ftpd telnetd rexecd rlogind remshd or tftpd e ftpd this server daemon is run by inetd as requests for File Transfer Protocol FTP services are received e telnetd this server daemon is run by inetd as requests for Telnet services are received e rexecd this server daemon is run by inetd as requests from hosts to execute UNIX commands remotely are received rexecd must receive a valid user ID and password from rexec e rlogind this server daemon is run by inetd as requests from hosts for remote logins are received Users can login on any host running remshd and if the remote host is listed in etc hosts equiv no password is required to connect e remshd this server daemon is run by inetd as requests from hosts a remote shell server servicing requests from the rsh program and the rcmd functions Users can execute UNIX commands on hosts running remshd and if the remote host is listed in etc hosts equiv no password is required to connect e tftpd this server daemon is run on demand by inetd as requests for Trivial File Transfer Protocol TFTP are received Continued on next page 30 Universal Station Troubleshooting 12 93 3 3 TCP IP Services and Processe
33. is ee ee de Re ee 18 2 8 Troubleshooting if UNIX is Operational iese RA ee ee 20 2 9 Degraded oe Ee EE N AE EE OE EE iralaie 22 2 10 Using the Modem Port iese see ee ee EE ee ee ee ee ee EE ee ek ek ee ee ee ee 23 SECTION 3 TROUBLESHOOTING THE ETHERNET LAN ee esse ee ee ee ese ss se ek ee ee 25 3 1 Local Area Networking LAN OvervieW iss ees eke ee RA ee 25 3 2 TCP IP Overvi W uses esse cette et ee ee ERA ER AA EA conc Ee AA Ede ede ER rn ER AA eek ede nenn 27 3 3 TCP IP Services and ProcesSeS ie RA RR RR AA ee ee ee 30 3 4 Troubleshooting Steps ee dd ee RA ER EA ee Ad ee AA ER ee ee ee de ee ee ke 32 3 6 Check the Software LoopbacK ie ss ee AR ER ee ke RA ER ee ee ee ee 37 SECTION A DIAGNOSTIC DISPLAY CODES uuuuunsnnnnennnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnn 39 A 1 WSI Coprocessor Diagnostic Display Status Codes 39 SECTION B CABLES EE N EE N 41 B 1 Console Terminal Cable uuuunsunsssnnnsnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnn 41 B 2 Modem Cape EE EE SE RENE GE ERG ee EE ER AE athens cate tues bane 42 12 93 Universal Station Troubleshooting Figures and Tables Figure 1 1 Figure 2 1 Figure 2 2 Figure 2 3 Figure B 1 Figure B 2 Table 2 1 Table 2 2 Table 2 3 Table 2 4 Table 2 5 Table 2 6 Table 2 7 Table A 1 Universal Station Primary Functional Components 3 WSI VO Board Connector Locations and Functi
34. itional diagnostic information by checking the status of the LED display when heartbeat is not present After a power on or reset the coprocessor firmware conducts a sequence of self tests and then boot procedures that normally culminate in a functioning kernel The diagnostic LEDs illuminate in seemingly random patterns during this startup phase If a failure is detected the LEDs will freeze with the pattern indicating the specific error that occurred Appendix A contains a table of these patterns and their meanings Record the error information if you discuss your problem with Honeywell TAC it may provide useful information Generally if the LEDs freeze in a pattern that is listed in the appendix this indicates a hardware failure The procedure in this case is to replace the WSI and coprocessor assembly as a unit however before you do this you should perform the procedures in the next subsection to check for a corrupt file system or hard drive problem 12 93 Universal Station Troubleshooting 17 2 7 Troubleshooting if UNIX is not Operational Overview File system corruption Disk failure If there is no heartbeat indicated on the LED display the UNIX kernel is not running The next step is to determine why the UNIX kernel cannot run The console terminal connection described in subsection 2 4 is required to monitor the boot process The most common problem affecting UNIX s ability to boot is file sys
35. m with all DIP switches in the factory default position ATTENTION The terminal connection described here is a powerful diagnostic aid and will be invaluable for troubleshooting certain types of failures We strongly suggest that you try this connection ahead of time if possible so that you test your terminal or emulation software and cable This simple preparation will save time and allow you to focus on the problem rather than the test equipment should a problem arise The following procedure includes node shutdown and power turnoff It is generally accepted practice to connect and disconnect RS 232 cables with power on However since our goal is to observe the boot process we suggest turning off power here unless doing so would adversely affect or risk your process Table 2 4 Procedure to Connect a Coprocessor Console Step Action 1 If your Universal StationX has a personality loaded and is online with the LCN do a shutdown of the node 2 Turn off the power switch on the Five Slot Module 3 Connect the communications cable to the terminal or PC and to J1 on the WSI VO board see Figure 2 1 4 If you are using a PC with VT 100 emulation software invoke the emulation software Continued on next page 12 93 Universal Station Troubleshooting 13 2 4 Connecting a Coprocessor Console continued Figure 2 1 WSI VO Board Connector Locations and Functions gL
36. master that provides host to internet address mapping for the other systems on the LAN The master system is configured with the IP daemon named to resolve host to address requests Flexibility in configuration can provide continuous operation by secondary name servers should the primary fail or be shutdown for maintenance Updating the master s etc hosts file initiates a transfer of the update information to all secondary servers and gateways Continued on next page 28 Universal Station Troubleshooting 12 93 3 2 TCP IP Overview continued Overview of BIND continued Typical name server Using the name service eliminates problems caused by incorrect or missing etc hosts entries Problems are eliminated by supplying the address from the master server s etc hosts file when starting a communications session Communication tasks can be automated without fear of future address changes requiring any alteration to the scripts Referencing the system by hostname ensures the address is looked up each time the script is executed This shows a typical configuration of the name server in a workstation architecture environment The name service is run on each internet segment s gateway node to reduce traffic on the main segment and provide secondary servers in case
37. neywell One cause for this type of failure is incomplete installation of a Universal support software StationX software update This type of failure is indicated by error messages that can be observed at the console device during system boot and startup or by analysis of log files kept by the Honeywell software subsystems To obtain further information perform the steps in Table 2 6 to obtain a list of running Honeywell tasks Table 2 6 Procedure to List Running Honeywell Tasks Step Action 1 Connect a console terminal as described in subsection 2 4 2 At the console device enter the following command ps ef more This command will provide a listing of all running processes 3 Determine if the primary processes required for Universal StationX are running These processes are X The X11 window manager tsdaemon The Honeywell manager daemon There should be two copies of this process lcndaemon The Honeywell LCN interface manager There should be two copies of this process running iwsm The Honeywell Industrial Work Space Manager startusx The Universal StationX display manager startup script usxinitrc The Universal StationX display manager initialization script Continued on next page 12 93 Universal Station Troubleshooting 19 2 8 Troubleshooting if UNIX is Operational continued Check the Honeywell support software continued Table 2 6 Procedure to List Running Honeywell Tasks continued 4 If any of the above processes lis
38. ons 13 Coprocessor Diagnostic LED Display sees see ede ee ke ee ee ee 15 Accessing the Menu to Change System Configuration 23 Console Terminal Cable REG RE EER EG SEGE AE GR GER ER Roe ER Ke 41 Modem Gable He di GE EE Sina ee GEM 42 Incorrect Display Types and Possible CauseS ees see RA 9 Steps in the Universal StationX Load Process 10 Correcting Universal StationX Personality Load Failures 11 Procedure to Connect a Coprocessor Consol ee see ee 13 Meaning of the Display Indicators 44444444H nennen ee ee nn 16 Procedure to List Running Honeywell Tasks 20 Procedure to Configure the Modem Polt seceeesseeeeeeeeeeeeeeeees 23 HP 9000 382 Display Status Codes ee sees ee see ee ae ee Re ee de Ge 40 Vi Universal Station Troubleshooting 12 93 Acronyms Al EE EE EE ER DAN EE ives Application Integration Architecture A DO N DR ee Computer Integrated Manufacturing WSM ES Ee Ee A elect eet ER EE Ee ge ED ee Industrial Work Space Manager WAN RA AE N EE EE EE Local Area Network do EE ME EE EE N AEE Local Control Network OSPa Rd A eee a un ie bald Open Systems Foundation OST e reo ae Open Systems Interconnection TDG ea HH Total Distributed Control di PER ites A ER N Turbo Peripheral Display Generator die ma AR Die Universal Control Network Bls EE EE EE een Bes tia OR Universal Personality X Re ee
39. or trained to use Universal Station and have a thorough understanding of UNIX commands and user interfaces Some of the steps recommended in this guide will require the user to log in to the Universal StationX for purposes of examination and problem correction This will require authorization to use the root account to perform these tasks This guide covers the initial diagnosis of a Universal StationX The goal of this diagnosis is to determine the most likely reason for a failure or problem so that corrective actions can be focused on the most probable causes In addition this guide is intended to provide a quick tutorial on the operational characteristics of Universal StationX that are unique or differ from those of a standard Universal Station After identifying a problem refer to Universal StationX Service in this binder for corrective action procedures Continued on next page 12 93 Universal Station Troubleshooting 1 1 1 Overview Continued Types of failures addressed Importance of skilled operation and maintenance Using this guide The types of failures addressed here are those that are unique to Universal StationX and include problems of the Universal StationX coprocessor Ethernet LAN interface High Performance Display Generator TPDG keyboard and mouse trackball pointing devices This guide also addresses equipment failures and problems introduced through user error Experience has sho
40. prevents the user interactive windows session from being initiated When such a failure occurs it is impossible to differentiate the loss of display interaction from total UNIX failure This problem indicates a loss of display integration services and may even indicate total failure of the UNIX environment This problem cannot be investigated directly from the Universal StationX console keyboard Direct access to the coprocessor is required to determine the nature of the problem To obtain direct access to the coprocessor it is necessary to connect a UNIX console directly to the coprocessor This is covered in the next subsection 12 Universal StationX Troubleshooting 12 93 2 4 Connecting a Coprocessor Console Connecting a console to the coprocessor ATTENTION Use the procedures below to connect a terminal to J1 of the WSI I O board Figure 2 1 shows the connector locations and functions for the WSI VO board Appendix B gives the wiring for a typical cable that might be used If possible choose a terminal that is Digital Equipment Corporation DEC VT 100 compatible You may also use a PC running suitable terminal emulation software such as Microsoft Windows Terminal to provide VT 100 compatible terminal capability Configure the terminal for 9600 bits second full duplex 8 bits character and no parity Honeywell s TAC Technical Assistance Center recommends a US Robotics Sportster 14 400 baud mode
41. puters function or location for example Inventory VS Unit1 Station3 This hostname is aliased to the internet address by its entry in the etc hosts file At boot time each computer on the network must have a minimum host file on its local disk to initialize the hostname to internet address mapping Once the host has loaded the appropriate name server service is used to resolve hostname to Internet protocol requests A minimum etc hosts file contains the following entries The form for each entry is lt internet address gt lt official hostname gt lt aliases gt See the hosts 4 manual page for more information Note Th ntries cannot be preceded by a space To use subnet masking uncomment the defaultmask entry and enter the desired value e g 255 255 255 0 Zo 200820020 defaultmask 127 0 0 1 localhost loopback 127 0 0 2 unknown ttt ttt HEH ARA hostname alias_for_hostname Where the hostname entry will resemble this 129 80 14 2 LL uxs iac honeywell com uxsl The Internet Protocol defines services to simplify etc hosts file maintenance on large networks The Berkeley Internet Name Domain BIND service is often referred to as the name server The configuration and troubleshooting of the domain name service is covered by Hewlett Packard s publication Installing and Configuring ARPA Services With BIND service the etc hosts file is maintained on one system the primary or
42. re is a high probability that most if not all of the hardware associated with standard Universal Station functions is operational On the other hand if the blue login dialog box is displayed on the bottom of the display screen this is a good indication that all of the coprocessor functions are operational After the proper installation and configuration of the Universal StationX has been determined to be satisfactory but normal operation of the station has not been restored it is necessary to perform some functional tests to determine the area or group of functions that are at fault The basic steps in determining component failure are described in the Universal StationX Service manual UX 13 410 old furniture or UX13 430 new furniture These manuals include information about the status indicators on the K2LCN TPDG and WSI boards They also include information about board pinning and cabling as well as maintenance and service information on drives keyboards and the monitor The following is a brief summary of the initial checks that you should make e Check board and cable installation e Check board pinning e Check status indicators on the power supply K2LCN WSI and TPDG boards Checking the diagnostic display on the WSI coprocessor is covered separately in a later subsection of this publication e Check that the node address is properly displayed on the K2LCN e Check for the LCN cursor in the top left of the scr
43. s continued TCP IP daemons continued TCP IP daemons vs processes Boot sequence e xwhod this daemon is run by the etc rc file at boot time and provides an Internet system status server rwhod maintains a database of status information used by the rwho and ruptime programs e gated this routing daemon uses Routing Information Protocol RIP and HELLO protocol to collect information from within one network and the Exterior Gateway Protocol EGP to announce its routes to another system System operation consists of individual applications providing a portion of the system functionality as it is needed Network services require various daemons to enable the communication protocols and complete the logical connection between operating systems The communication daemons providing the network services are initialized during the UNIX boot process The system run commands file etc rc is executed at boot time to initialize the daemon processes that provide system services These processes continue to execute listening for requests as long as the coprocessor is operational and powered ON They are said to be background processes or daemons and are not directly visible to the network users They remain executing as user s login during network operations etc inetd appears to respond to your telnet requests However the user s original telnet request is redirected by the daemon process etc inetd whic
44. s should be investigated The node s processor loading may prevent a timely response to the ping command or there may be a crashed node generating noise on the LAN network through its Ethernet interface If the packet loss is 100 the most likely problem is an open cable segment on the Ethernet LAN 36 Universal Station Troubleshooting 12 93 3 6 Check the Software Loopback Check configuration of TCP IP provides a software loopback interface to troubleshoot the local local host software from the network layer up Use the software loopback interface to check local TCP IP software operation This is done by sending a message to internet address 127 0 0 1 which by convention is assigned the host name localhost This address and host name should be included in the networks etc hosts file and the localhost line should be uncommented in the file etc netlinkrc as shown in bold below case SNODENAME in SROOTSERVER etc ifconfig lan0 inet 129 30 255 255 netmask 255 255 255 0 up etc lanconfig lan0 i etc ifconfig lan0 inet hostname up etc lanconfig lan0 ether ieee esac etc ifconfig 100 inet 127 0 0 1 up Check operation of the Use the software loopback interface to check local TCP IP software local host operation This is done by sending a message to internet address 127 0 0 1 which by convention is assigned the host name localhost Sending to this software loopback is equivalen
45. s this will undoubtedly be n button and click the GJ 10 Select DONE position the cursor on the DONI left mouse or trackball button 11 For Select Code enter 6 and for Port Number enter 3 12 Select PERFORM TASK and then EXIT TASK Continued on next page 22 Universal StationX Troubleshooting 12 93 2 10 Using the Modem Port continued Selecting process to change system configuration Figure 2 3 Accessing the Menu to Change System Configuration Engineer Menu X Menu Application System Menu gt gt System Commands Configuration gt Configuration Update Software gt IWSM Configuration Add Remove Users system Configuration Backup Restore Set Time Timezon Gated Daemon gt 12594 Connect the modem Prepare ahead Connect the modem to J5 on the WSI I O board Because of the location of J5 see Figure 2 1 you will need to remove the WSI I O board to make this connection This will require shutting down the node and powering down the station Also because of space constraints a D 9 connector with full size hood cannot be installed on J5 One way to avoid both of the above problems is to install a short 9 pin ribbon cable with a male ribbon connector on one end and a female connector on the other The ribbon
46. ss in steps to the big picture Tests of communications with hosts located across components such as LAN router or gateway nodes may identify problems with the other resources Again the network diagram will direct your troubleshooting efforts Communication failures caused by software problems are generally easy to identify They often show the physical hardware connections to be functional The node s ability to communicate with other Internet hosts depends on many processes possibly executing on computers outside of your area of operations For example the domain name server is located administered at the corporate headquarters and has not been updated with the latest network changes Consult your network administrator and follow local procedures concerning the updating testing of these remote resources It is suggested that you check the TCP IP software on each host and gateway involved For example ensure that the etc inetd daemon is running and does start the etc telnetd process when telnet is invoked The TCP IP error messages identify the common problems and point you toward the node or software layer most likely to contain the fault Continued on next page 32 Universal Station Troubleshooting 12 93 3 5 Troubleshooting Steps continued Detailed protocol tests continued If the error message doesn t readily identify the problem the network troubleshooting utilities will be needed to observe each protocol
47. t to sending to your own address The IP protocol command ping uses only the etc inetd daemon process for communications Under normal conditions the etc inetd daemon is active on all coprocessors awaiting network traffic from the LAN connection To use ping Type ping hostname count lt RETURN gt Where count number of ICMP requests use 3 10 to limit network traffic As an alternative use the following options Type etc ping option hostname count lt RETURN gt d Displays debugging information r Send direct without route information if node is on same network v Verbose output Lists ICMP packets other than ECHO RESPONSE See the man pages about ping for more information 12 93 Universal Station Troubleshooting 37 38 Universal Station Troubleshooting 12 93 Section A Diagnostic Display Codes A 1 WSI Coprocessor Diagnostic Display Status Codes Table of codes In the following table the LED Display column 0 indicates LED off and 1 indicates LED on Refer to Figure 2 2 for LED location Table A 1 HP 9000 382 Display Status Codes LED Display Error Indication ABCDEFGH 00000000 No failure 00000001 Failed CPU register test 00000010 Testing top 16 K of memory 00000011 Top 16 K of memory failed 000001 000001 00000110 Executing extension ROM 0 Top 16 K of memory missing ojo 1 Searching for user ROM 00000111 Starting test ve
48. ted in the previous step are not running there is a problem in the startup sequence of the Universal StationX Check the log files in the directory tmp for indications of why this process is not functioning properly These log files are tmp Xlogfile log tmp Tpdg_server log tmp LCN_daemon log 5 If there has been a recent installation of a software update inspect the file tmp update log to determine if an error occurred during the installation 20 Universal Station Troubleshooting 12 93 2 9 Degraded Operation Definition Causes and things to check A degraded operation problem is one that prevents the use of a specific function where all or most others continue to function normally These types of failures are usually caused by the incorrect setting of user authorizations privileges and X window display attributes These parameters should be installed and maintained by the system administrator however a user can inadvertently alter his own configuration causing problems unique to that user All user attributes that affect specific display client software are selected by default selections contained in the file usr 1ib X11 system Xdefaults Attributes that affect the display of windows and associated resources common to all users are defaulted in the file usr lib X11 system mwnrc These default attributes can be over ridden by the individual user by local files in the users home director
49. tem corruption typically caused by improper shutdown or a failure of power to the coprocessor and its subsystems If the station is improperly shut down the latest changes to files may not have been updated to disk resulting in file system corruption For performance reasons file system writes are cached or accumulated in memory until they can be written to the disk in an efficient manner If the system is improperly shut down manually or by power failure or crash while disk data are cached there will be a difference between what UNIX thinks is on the disk and what is actually there A process called fsck File System Check is run automatically at boot time to check for and correct this and other problems Usually this process will correct the problems automatically however multiple power failures occurring in a short period of time can cause the process to be interrupted This can result in an inconsistency that cannot be corrected automatically When this occurs the boot process will pause in the fsck process and prompt the user to enter a choice of corrective action from the console To determine if this is the reason your Universal Station is not functioning attach the console device to the TERMO port J1 on the WSI VO board Reset the system and monitor the boot process on the console to determine if the fsck process is waiting for input If so provide the appropriate input to allow the process to complete For furth
50. ubleshoot same as failure to load any Universal Station If this works reinstall current Universal StationX software Personality continuously prompts NCF N 1 2 3 4 Universal Station is not properly connected to the LCN network and or cannot access History Module Validate LCN connections Ensure that LCN Re Connect is not in progress Is Universal Station Personality version compatible with others on LCN 12 93 Universal Station Troubleshooting 11 2 3 UNIX Software Problems Categories of errors Loss of function Loss of display no login window The coprocessor UNIX environment provides all management of windows display resources In addition the coprocessor is the host for all Universal StationX enhanced features Any failure that occurs within these functions usually will not affect the functioning of Universal Station in the standard Universal Station mode of operation Errors in the UNIX operating environment can be categorized in two basic groups e Loss of function e Degraded operation A loss of function problem is defined as one that prevents the normal Operation of the station prevents user interaction or appears to indicate total coprocessor failure In most cases troubleshooting of a loss of function problem will require direct access to the UNIX environment This may not be directly possible from the Universal StationX console keyboard and screen when the failure
51. versal Personality with the addition of software elements that control the exchange of data with the coprocessor through K2LCN memory The Universal StationX Personality provides the complete functionality of a standard Universal Station independent of the coprocessor Continued on next page Universal StationX Troubleshooting 12 93 1 2 Universal StationX Basics continued Coprocessor software LCN Native Window Behavior without UNIX X Windows Behavior without Universal StationX Personality The coprocessor provides the execution environment for UNIX applications programs as well as associated software to enhance the display capabilities of Universal StationX the X Window display manager and utility programs The display manager provides display resource control and services that allow multiple programs to display their information on the same screen simultaneously in individual windows The X Window display mode is operational only when a valid user login has been executed When there is no user logged in the Universal Station operates without windows in a manner identical to that of a standard Universal Station The display of data on the screen of the Universal Station is controlled by the TPDG All standard TDC 3000X displays generated by the Universal Station Personality on the K2LCN are presented in a window reserved for this purpose This window is known as the LCN Native Window The display monitor in
52. wn that many Universal StationX problems are the result of incorrect or inappropriate system configuration or operation by end users Errors of this type can cause the software to appear to function improperly but this should not be mistaken for failure Such errors are usually recoverable with little difficulty however further damage can be done by inappropriate troubleshooting procedures Before you take any troubleshooting action be sure you are familiar with UNIX system administration procedures are aware of what used to work and how or what events occurred prior to the failure or degradation In extreme cases such user error can require the reinstallation of system software For this reason it is important that your Universal StationX system should be maintained by experienced and trained personnel and that appropriate file system configuration and maintenance is performed regularly to ensure timely recovery from loss of data through user error This guide is structured to provide step by step isolation of a failure in a Universal StationX to the failing component The types of failures are grouped by initial appearance or behavior For example No Display or Personality will not load Once the group has been identified the specific nature of a failure within that group can then be determined Universal StationX Troubleshooting 12 93 1 2 Universal StationX Basics Introduction It is important
53. y These files are xdefaults mwmrc and session These files should be inspected carefully whenever a specific software function fails to operate for a single user Additional client software configuration attributes are found in the directory usr lib X11 app defaults Files in this directory provide the default resources for specific client software programs To take advantage of these defaults a user must have a local shell variable set that provides a path to these variables By default this variable is normally named XAPPLRESDIR and should be set to usr lib X11 app defaults Check for this whenever a user has difficulty using a specific or newly installed software application Incorrect settings of access rights is another problem that can affect execution of specific software functions A user can be denied access to a needed file or directory if these rights are incorrectly set All of the configuration settings and any problems resulting from these settings are normally handled by the responsible Universal StationX system administrator The responsible individual should be trained or have appropriate experience in the required tasks 12 93 Universal StationX Troubleshooting 21 2 10 Using the Modem Port Coordinate with TAC The modem port J5 on the WSI I O board can be used for remote maintenance and support by the Honeywell Technical Assistance Center TAC This procedure must b
Download Pdf Manuals
Related Search