ACC Utilities Reference Guide Edition 1 HP 9000 Networking Manufacturing Part Number : Z7345-90002 E0204 © Copyright 2004 Hewlett-Packard Company.
Legal Notices The information in this document is subject to change without notice. Hewlett-Packard makes no warranty of any kind with regard to this manual, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Hewlett-Packard shall not be held liable for errors contained herein or direct, indirect, special, incidental or consequential damages in connection with the furnishing, performance, or use of this material. Warranty.
© copyright 1980, 1984, 1986 Novell, Inc. © copyright 1986-1992 Sun Microsystems, Inc. © copyright 1985-86, 1988 Massachusetts Institute of Technology. © copyright 1989-93 The Open Software Foundation, Inc. © copyright 1986 Digital Equipment Corporation. © copyright 1990 Motorola, Inc.
Printing History The manual publishing date and part number indicate its current edition. The publishing date will change when a new edition is published. Minor changes may be made without changing the publishing date. The manual part number will change when extensive changes are made. Manual updates may be issued between editions to correct errors or document product changes. To ensure that you receive the updated or new editions, you should subscribe to the appropriate product support service.
Related Documentation The documentation available for the Multiprotocol ACC family of products includes the following hardware and software manuals: Hardware Manuals • 8 Channel PCI ACC Multiplexer Hardware Installation and Reference Manual Software Manuals • • • • • • • • • • • • ACC Installation and Configuration Guide ACC Utilities Reference Guide ACC Programmer’s Reference Guide ACC Error Guide HDLC Frame Protocol User’s Guide ACC X.25 Protocol User’s Guide ACC X.
Contents 1. ZDGEN - ZCOM Device Table Generator Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Changing the Device File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Device Definition File Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Compiled Device File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Unack-Limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Port-Limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Interface-Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . nn . . .
Contents Summary of Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ?? - Display Help List of Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ! - Execute a shell command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . /E - Exit from ZMNTR . . .
Contents LQ - Allocate Logical Terminal Queue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LS - Allocate Logical Terminal Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LU - Update Logical Terminal Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MG - Move Logical Terminal Between Physical Terminal Group . . . . . . . . . . . . . . MP - ZLU Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents 5. ZSCAN - Display ZCOM Tables & Buffers Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Running ZSCAN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Scanning Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Some examples of running ZSCAN: . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents 7. ZMON - ZCOM Control Program Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ZMON Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ZMON Command Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Important Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198 10. WATCH - Mux Shutdown Feature Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuration Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Running watch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents 16
1 Chapter 1 ZDGEN - ZCOM Device Table Generator 17
ZDGEN - ZCOM Device Table Generator Introduction Introduction The term “ZCOM” refers to the HP Advanced Communications Controller (ACC) family of products. The ZCOM device (or terminal) definitions are stored in a configuration file, which is used by the TTGEN program each time it compiles a TTGEN configuration file. The ZDGEN program is responsible for converting an ASCII editable file of definitions into a binary device definition file. This allows new terminals to be defined with a minimum of effort.
ZDGEN - ZCOM Device Table Generator Changing the Device File Changing the Device File The device definition file in the ZCOM system is an editable ASCII file. Every device is defined by one line in the file. Lines beginning with an asterisk (*) or a semicolon (;) are treated as comments. Any text after an exclamation mark (!) on a line is also treated as a comment. Spaces or commas may be used as parameter separators. The definition format is as follows: Type Name........
ZDGEN - ZCOM Device Table Generator Device Definition File Example Device Definition File Example NOTE The information in this example may be out of date and should NOT be used when configuring a ZCOM subsystem. Refer to the current Device Definition file supplied (/opt/acc/cfg/zcomdevice.txt). ;==========================================================================+ ; ; ; ZCOM device type description Rev.01.C <960325.
ZDGEN - ZCOM Device Table Generator Device Definition File Example 02, 03, 04, 05, 06, 07, 08, 09, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, MONITOR 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 21 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 99 00 00 00 00 00 00 00 00 00 00 00 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 2 0 0 0 0 0 0 0 0 0 0
ZDGEN - ZCOM Device Table Generator Device Definition File Example 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, HDLCNRM.PT HDLCNRM.S HDLCNRM.PBT HDLCNRM.PRT HDLCNRM.SBT HDLC.LAPB X25.LAPB X25.PVC X25.SVC X25.SVC.OUT X25.SVC.AUTO X25.SVC.IN X25.SVC.IO X25.SVC.NULL X25.SVC.IO.
ZDGEN - ZCOM Device Table Generator Compiled Device File Compiled Device File The device definition file is compiled into a binary device file by ZDGEN. The binary device file is used by TTGEN (via the getdevice routine). Each record of this file contains data on one device type. The sequential record number is the device number used internally within the ZCOM system. The format of each record is shown in Figure 1-1.
ZDGEN - ZCOM Device Table Generator Running ZDGEN Running ZDGEN The ZDGEN program reads the ASCII device definition file and generates a binary file that is used by TTGEN to build the memory image file for the ZCOM system. The run string for ZDGEN is as follows: zdgen - is the ASCII file - is the generated binary device file Remember to specify as much of the directory path of each of the file names as is necessary.
ZDGEN - ZCOM Device Table Generator ZDGEN Errors ZDGEN Errors File handling errors that occur while running ZDGEN are reported by HP-UX. For further explanation of any file handling errors, refer to the Hewlett-Packard HP-UX Reference Manual, under PERROR(3) and ERRNO(3). Other messages produced by ZDGEN are described below: Device number not in sequence, line# n Explanation: The device type number must commence at 1 and be incremented by 1 for each device type in the file.
ZDGEN - ZCOM Device Table Generator ZDGEN Errors 26 Chapter 1
2 Chapter 2 TTGEN - ZCOM System Table Generator 27
TTGEN - ZCOM System Table Generator Introduction Introduction The program TTGEN creates the file used to initialize and start up the run-time ZCOM sub-system. TTGEN reads an ascii configuration file that contains the details of the network structure and generates a binary memory image file to be used by ZMON. The file structure is detailed under “Tables and Data Structures” in the Multi-protocol ACC Programmer’s Reference Guide.
TTGEN - ZCOM System Table Generator Memory Image File Overview Memory Image File Overview ZCOM System Header The ZCOM System Header contains fixed information such as the location and number of all the tables in the ZCOM sub-system, and also the size of the buffer pool. For more detail, see the data structure zheader_type in /opt/acc/include/zcom/zcomsys.h. Node Entries The Node Entries table contain information about the remote ZCOM sub-systems that communicate with the local ZCOM sub-system.
TTGEN - ZCOM System Table Generator Memory Image File Overview number of terminals. This means that there may be more logical terminal tables than physical terminals. For more detail, see the data structure zltt_type in /opt/acc/include/zcom/zcomsys.h.
TTGEN - ZCOM System Table Generator Memory Image File Overview Buffer Pool The buffer pool is a piece of fixed-size, contiguous memory. Its total size is specified in the TTGEN configuration file. The system allocates memory from this pool for ZCOM requests that require buffering (for example, zsend), and returns memory to this pool on completion. The memory allocated is always large enough to hold the whole request in one contiguous memory block.
TTGEN - ZCOM System Table Generator Creating the TTGEN Configuration File Creating the TTGEN Configuration File Overview The TTGEN configuration file is an ASCII text file that describes the size and configuration information of a ZCOM system. TTGEN compiles this file and generates a corresponding binary “memory image file,” which will be used by ZMON to initialize and start up the run-time ZCOM sub-system with the specified configuration.
TTGEN - ZCOM System Table Generator Creating the TTGEN Configuration File Chapter 2 1234H for hexadecimal 1234h for hexadecimal 01234h for hexadecimal 33
TTGEN - ZCOM System Table Generator Creating the TTGEN Configuration File TTGen Control Line This line must precede all the other configuration and definition sections. It is to indicate that the source file is for TTGEN. TTGEN will complain if this line is missing. There is no configuration information that goes with this section. Comments or “#include” statements may appear before this line.
TTGEN - ZCOM System Table Generator Creating the TTGEN Configuration File Configuration System-name Program-ZLU Terminal-ZLU Logical-Term Physical-Term Interface-Table Node-Entry Buffer-Pool Logical-Size Logical-Data . . .
TTGEN - ZCOM System Table Generator Creating the TTGEN Configuration File Program-ZLU Number of spare program ZLUs to be allocated. Program ZLUs are only associated with programs and drivers that use the ZCOM API. Each program uses at least one program ZLU. The default number of spare program ZLUs is 256. The valid range of values is 1…10000 (ZCOM_MAXPZLU in /opt/acc/include/zcom/zcomsys.h). Terminal-ZLU The maximum number of terminal ZLUs that may be defined in this system.
TTGEN - ZCOM System Table Generator Creating the TTGEN Configuration File Node-Entry Total number of node entries in this configuration. Each “Local-Node” and “Remote-Node” definition in the Node-Definition section requires one node entry. This value may be greater than the number of nodes defined. The unused entries may be used to dynamically create a node definition using the Dynamic System Configuration services (currently not supported).
TTGEN - ZCOM System Table Generator Creating the TTGEN Configuration File Interface-Table Total number of interface tables in this configuration. Each entry in the “Interface-Definition” section uses one interface table. The interface tables are numbered from 0, hence this value must be at least one greater than the number of ACC card statements in Interface-Definition section. That is, it must be larger than the largest interface card number defined.
TTGEN - ZCOM System Table Generator Creating the TTGEN Configuration File Example: For a 100% busy system with 8 mux cards with 57.6k links, and an average message length of 100 bytes, the Buffer-Pool size should be at least: 8 x 576 x 5 x (100 + 200) x 1.5 = 10 Mbytes Logical-Size The size in bytes of an LTT extension area. An extension area can be associated with a logical terminal table (LTT).
TTGEN - ZCOM System Table Generator Creating the TTGEN Configuration File the offset of the reserved space within the spare data area. This field starts from 0 up to (Logical-Size - 1), in multiples of 8. the number of bytes, in multiples of 8, to be reserved Queue-Limit The default maximum number of messages that can be queued on a program ZLU if the limit is not specified in the zopen call.
TTGEN - ZCOM System Table Generator Creating the TTGEN Configuration File Port-Limit The default limit (in bytes) of all unacknowledged transmit messages to terminals on a port. This parameter controls how much outbound data is allowed onto the ACC card for each port. Each port has 24,000 bytes of memory available for outbound data buffers (including protocol packets).
TTGEN - ZCOM System Table Generator Creating the TTGEN Configuration File Interface-Definition The Interface-Definition section is used to specify the ACC cards to be included in the system. For each interface defined, ttgen reserves an interface table, which contains all required information for controlling the hardware. The Interface-Definition section takes either one of the two forms shown, where the second form refers to HP 9000 Series K systems.
TTGEN - ZCOM System Table Generator Creating the TTGEN Configuration File Chapter 2 0 1 0:4 /opt/acc//x25.zabs 0:12 /opt/acc//x25.
TTGEN - ZCOM System Table Generator Creating the TTGEN Configuration File Series 890/T500 Systems For these systems, the address information returned from ioscan is in the format of BB/CC, where BB is the bus converter address and CC is the card address. For example, if the ioscan returns that the first ACC card on the system is at card address 4, and a second card is at 12, the corresponding ttgen Interface-Definition statements would be: 0 1 2:8 /opt/acc//x25.
TTGEN - ZCOM System Table Generator Creating the TTGEN Configuration File Optional Z7340A Tunable Parameters The parameters listed below may be specified immediately after an 8-channel PCI serial interface card definition, on the following line or lines, in any order. Their purpose is to allow some flexibility in the allocation of memory and resources on the ACC card. The total memory available on this card is 16M-bytes.
TTGEN - ZCOM System Table Generator Creating the TTGEN Configuration File The firmware on the 8-channel PCI cards use fixed sized I/O buffers to hold inbound and outbound data messages and protocol packets. If a data message is larger than the buffer size, multiple buffers are allocated to hold the message. The buffer size may be increased or decreased to allow for the most common expected message size.
TTGEN - ZCOM System Table Generator Creating the TTGEN Configuration File zbufnbr number of buffer entries (1-1M) The maximum number of buffers available on the card. The size of each buffer is determined by the zbufsize parameter. The default is ACC card type dependent. For the Z7340A 8-channel PCI ACC, this parameter should not be specified, as it will default to using all remaining free memory for ACC buffers.
TTGEN - ZCOM System Table Generator Creating the TTGEN Configuration File The following parameters have defaults set according to the requirements of the firmware. They should not be modified unless otherwise instructed by Hewlett Packard. ttablesize 48 size of terminal table entries in bytes (160-1024, multiple of 16). The default size of the terminal table entries is 224 bytes.
TTGEN - ZCOM System Table Generator Creating the TTGEN Configuration File tsize:t0:t1:t2:t3 t0 is the size of 10ms timer table in bytes, (8-256000, multiple of 8) t1 is the size of 100ms timer table in bytes, (8-256000, multiple of 8) t3 is the size of 10s timer table in bytes (8-256000, multiple of 8) t2 is the size of 1s timer table in bytes, (8-256000, multiple of 8) These parameters represent the number internal timer resources in the ACC card.
TTGEN - ZCOM System Table Generator Creating the TTGEN Configuration File NOTE 50 The tracesize parameter should only be adjusted to a larger value on advice of Hewlett-Packard support personnel.
TTGEN - ZCOM System Table Generator Creating the TTGEN Configuration File traceopt firmware trace option flags This parameter specifies the options for the internal firmware tracing. A value of 0 disables all firmware tracing. The traceopt keyword may be specified multiple times for a single interface. The values specified will be ORed together to produce the desired value of the traceopt parameter.
TTGEN - ZCOM System Table Generator Creating the TTGEN Configuration File Memory Usage Considerations The terminal tables, buffers, message headers, and timer tables occupy a fixed amount of memory. The amount of memory used is: ttablesize*ttablenbr+zbufsize*zbufnbr+mheadnbr*80+”tsize parameters”+tracesize If this exceeds the available space (16M-bytes), “zmon” will report the problem when the firmware is being downloaded to the ACC card.
TTGEN - ZCOM System Table Generator Creating the TTGEN Configuration File Port-Definition In the Port-Definition section, a port entry must be defined for all ports that are referenced by the terminal definitions in the Terminal-Definition section. The parameters must be specified in the order shown, since some of the parameters are dependent on those that occur earlier in the line.
TTGEN - ZCOM System Table Generator Creating the TTGEN Configuration File INTEXTExInDPLL- Use internal baud rate generator Use external clock Use external clock for X.21 interface Use DPLL output (phase locked loop) INT must be used for ASYNC Mode mode Operating mode of port ASYNCBISYNCSDLC- mult Clock multiplier.
TTGEN - ZCOM System Table Generator Creating the TTGEN Configuration File STP1STP1.5STP2- 1 stop bit 1.
TTGEN - ZCOM System Table Generator Creating the TTGEN Configuration File Terminal-Definition This section specifies all the terminals on the system. Note that the term “terminal” is used to generically refer to any type of physical device or logical entity (such as an X.25 Virtual Circuit).
TTGEN - ZCOM System Table Generator Creating the TTGEN Configuration File Chapter 2 ZLU The terminal ZLU number. The terminal ZLU numbers do not have to be allocated sequentially, but must be unique for each terminal. The valid range of values is 1…Terminal-ZLU (defined in the Configuration section). in:p The V or X series interface number and port number through which the terminal ZLU is communicating to the system.
TTGEN - ZCOM System Table Generator Creating the TTGEN Configuration File appl The application number for the terminal provides a means to control which terminals are used for which program. Application programs are then able to query the application number to determine if they should communicate with this terminal. Use application numbers greater than 1000 for user defined applications. inst The number of the institution owning the terminal (or other application-specific information).
TTGEN - ZCOM System Table Generator Creating the TTGEN Configuration File Pterm A method of defining a physical terminal which has a number of logical terminals associated with it. The subparameter Term, above, creates a one-to-one correspondence of physical terminals to logical terminals. Thus Pterm consists of a subset of the subparameters used for the Term parameter. (See under Term above.
TTGEN - ZCOM System Table Generator Creating the TTGEN Configuration File Ldata is associated with the Term or Lterm parameter previously defined before it. Term and Lterm entries have application numbers associated with them. Ldata resides in a Logical-Data area that has an application number associated with it. The application number of this Logical-Data area and the Term or Lterm parameter must match, or the application number of the Logical-Data area must be zero (0). Else an error will be reported.
TTGEN - ZCOM System Table Generator Creating the TTGEN Configuration File Ldata Ldata Ldata 0 NAME:X25CNT:0 NAME:X25CNT:4 STRING BYTES INT16 ”User-Data” 0,7,200,255 3000, 5000, 60000 The above example defines the first 9 bytes of extension area to be ASCII “User-Data”, the first 4 bytes of region “X25CNT” to be binary 0, 7, 200, and 255, and the next 3 16-bit values (i.e., 6 bytes) of the same region to be 3000, 5000, and 60000.
TTGEN - ZCOM System Table Generator Creating the TTGEN Configuration File Repeat The Repeat keyword is used to replicate Term, Pterm, or Lterm entries. When the Repeat statement is encountered, it will duplicate the Term, Pterm, or Lterm defined immediately before the repeat statement by the number of times indicated. The ZLU numbers of the replicated entries are assigned by incrementing the original ZLU number by one for each entry created. For example, the statements: Term 060 1:1 X25.SVC.
TTGEN - ZCOM System Table Generator Creating the TTGEN Configuration File When the number of pending messages on the ZNODE queue reaches the high-water mark, programs initiating remote requests are suspended to avoid excessive buffers being held on the ZNODE queue. When the number of messages in the ZNODE queue drops below the low-water mark, such suspended programs are allowed to resume execution.
TTGEN - ZCOM System Table Generator Running TTGEN Running TTGEN TTGEN is driven from a configuration file that describes the configuration of the ZCOM subsystem. It produces a memory image file that is used by ZMON to initialize the ZCOM runtime system. The runstring for TTGEN is as follows: TTGEN [options] [-m mfile] ifile [ofile] Options: -o overwrite output file if it already exists.
TTGEN - ZCOM System Table Generator TTGEN Errors TTGEN Errors TTGEN groups the problems it detects from a configuration file into four categories: TTGEN SUMMARY MESSAGE: TTGEN summary message. Displayed after TTGEN is run regardless of TTGEN run options. DISASTER: Very serious problem. TTGEN will stop immediately when it is detected. No output file or listing will be produced. Example: ERROR: Problem in opening or reading the source configuration file.
TTGEN - ZCOM System Table Generator TTGEN Errors Any file handling errors that occur while running TTGEN are reported by HP-UX. For further explanation of any file handling errors, refer to the Hewlett-Packard HP-UX Reference Manual, under PERROR(3) and ERRNO(3). See the “TTGEN Error Messages” chapter in the ACC Error Guide for lists of errors and other messages which may be produced by TTGEN.
3 Chapter 3 ZMNTR - ZCOM Runtime Monitor 67
ZMNTR - ZCOM Runtime Monitor Overview Overview The purpose of ZMNTR is to present a comprehensive view of the ZCOM runtime system by making available important configuration and state information. The ZMNTR utility also allows interactive control over the ZCOM runtime system.
ZMNTR - ZCOM Runtime Monitor Running ZMNTR (ZCOM Runtime Monitor) Running ZMNTR (ZCOM Runtime Monitor) ZMNTR has the following runstring options: Usage: zmntr [-m mfile] [-k] Options: -m mfile Alternate message file (default /opt/acc/msg/default.msg) -k Don't fork “ied” to get Korn shell like command stack The -m option is to specify an alternate message file other than the default one comes with the ACC product installation.
ZMNTR - ZCOM Runtime Monitor Running ZMNTR (ZCOM Runtime Monitor) will start ZMNTR, execute the TT command, and then exit from ZMNTR returning to the shell prompt. This command may also be entered with commas as delimiters between the command parameters, but must have a space between ZMNTR and the TT command, for example: $ zmntr tt,1,5 is allowed, but: $ zmntr,tt,1,5 is not allowed. Running from a command file ZMNTR may also be run from a command file. The command file may be invoked in two ways.
ZMNTR - ZCOM Runtime Monitor Running ZMNTR (ZCOM Runtime Monitor) Output to a file The output from ZMNTR is usually displayed on the terminal. However if ZMNTR is run with standard out redirected to an alternate destination, then only the ZMNTR prompts will be seen on the terminal. For example, the usual dialog for two TT commands is shown below: $ zmntr ZMNTR> tt 1 5 ZLU# Mx p:sc Terminal Description.. Rx.Mes Tx.
ZMNTR - ZCOM Runtime Monitor Running ZMNTR (ZCOM Runtime Monitor) 0005 **** ZLU# 0006 0007 0008 0009 0010 **** $ 00 ** Mx 00 00 00 01 01 ** 4L00 L2 DCE 1 6 ** Message totals 7 36 p:sc Terminal Description.. Rx.Mes Tx.Mes 5L00 L2 DCE 1 6 6L00 L2 DCE 1 6 7L00 L2 DCE 1 6 0L00 L2 DCE 1 6 1L00 L2 DCE 1 6 ** Message totals 5 30 0 0.00% Up,Link Estbd 0 .00% ************ Error E.Rate State....... 0 0.00% Up,Link Estbd 0 0.00% Up,Link Estbd 0 0.00% Up,Link Estbd 0 0.00% Up,Link Estbd 0 0.00% Up,Link Estbd 0 .
ZMNTR - ZCOM Runtime Monitor Command Modifiers Command Modifiers A number of the commands have selection modifiers to restrict their action to only those that meet certain criteria. The commands are immediately followed by one or more of the following modifiers: V X.25 Virtual circuits L X.25 Link circuits N X.25 Link terminal configuration X X.
ZMNTR - ZCOM Runtime Monitor Command Modifiers 74 ttm,50 Will display all terminals in the same multiplexed group if ZLU 50 is a multiplexed terminal. ttp,50 Will display all terminals on the same port as ZLU 50. ttvp,50 Will display all X25 virtual circuits on the same port as ZLU 50. ttx,1,100 Will display all X25 link terminals with their statistical data, in the given range. tta,1,100 Will display all terminal ZLUs configured in the range 1 to 100 including those on absent ACC cards.
ZMNTR - ZCOM Runtime Monitor Command Modifiers The following commands can use the O, V, and L subset of the modifiers. Chapter 3 EN,DI,AC,DE Terminal control (enable etc.
ZMNTR - ZCOM Runtime Monitor Summary of Commands Summary of Commands The commands available through ZMNTR, in alphabetic order, are as follows. Specific help for a particular command is obtained by entering “??” followed by the command for which help is required. For information on how the commands can be used for X.25, enter “?? X25”.
ZMNTR - ZCOM Runtime Monitor Commands Commands ?? - Display Help List of Commands Format: ?? ZMNTR> ?? Code Description................... EX - Exit program (or /E) AC - Activate terminals (RE) EN - Enable terminals (SU) MX - Display mux configuration RC - Reset rx.mes, tx.mes, errs cnts PT - Display terminals on a port R - Repeat Enable/Disable LL - Set new list file SET- Set or display ZMNTR settings Code DC DE DI LB TT TR TM TO ! - Description..................
ZMNTR - ZCOM Runtime Monitor Commands ! - Execute a shell command Format: !shell_command_string Temporarily suspend “zmntr” and execute a shell command. /E - Exit from ZMNTR Format: /E The /E command is used to exit ZMNTR. It is also possible to use EX, which has exactly the same effect. DC - Display Configuration (Terminals) Format: DC,mm,nn,[name] This command displays the configuration information of the terminals in the ZLU range mm to nn. The [name] parameter is optional.
ZMNTR - ZCOM Runtime Monitor Commands ZMNTR> dcv 10 Zlu# Mx p:sc 0100 00 0V01 0200 00 1V01 0300 00 0V02 0301 00 0V02 310 Tmnl.type...... X25.SVC.IN X25.SVC.AUTO X25.SVC.IN X25.SVC.IN Configuration............................ VC=0000 #=226633011 X.25 SVC in from 33011 VC=0000 #=226633011 X.25 XVC out to 33011 VC=0001 #=No address L3 svc VC=0002 #=No address L3 svc T1 is the value of the timer configured in the “select” parameter, # is either the X.25 number that will be called, or the X.
ZMNTR - ZCOM Runtime Monitor Commands EN - Enable terminals (and DI, AC, DE) Format: EN,mm,nn or ’DI’, ’AC’, ’DE’ These commands control the state of the terminals ranging from mm to nn inclusive. If nn is omitted then only mm is affected. DI- Disables the terminals. EN- Enables the terminals. DE- Deactivates the terminals. AC- Activates the terminals. Notes:These commands can use the X.25 modifiers L, V, and O. A DI command will abort any untransmitted data destined for terminals in the range.
ZMNTR - ZCOM Runtime Monitor Commands For serial cards the external loopback is performed using RS-232 or V.35 signaling depending on the type of panel attached. If no options are specified, the assumed default is “i”. For any type of ACC card, all terminals on the port must be disabled before the test is run. NOTE The test can only be run if the following two conditions are met: 1. The PORTTEST protocol has been included in the download file. 2.
ZMNTR - ZCOM Runtime Monitor Commands The following is an example of a PORTTEST Term entry for port 3 of ACC card 1: TERM 500 1:3 PORTTEST 0000h 0000h 99,0,0,0,0 ”For Loopback Testing” For E1/T1 ACC cards there is no special configuration required to run the port test. Also there is no need to select a signalling type (ie. option “2”). The loopback test is performed using all available timeslots that use the E1 standard.
ZMNTR - ZCOM Runtime Monitor Commands ZMNTR> lb 1 0 ie2 Loopback test on Mux 01 port 0, zlu Loopback protocol functionality .. RS232 RTS/CTS internal loopback .. RS232 RTS/CTS external loopback .. RS232 DTR/DCD internal loopback .. RS232 DTR/DCD external loopback .. RS232 DTR/DSR external loopback .. ISCC data loopback test .......... RS232 internal data loopback ..... RS232 external data loopback .....
ZMNTR - ZCOM Runtime Monitor Commands The [opts] parameter allows the additional display of the TEXT, FILENAME, and NAM records from the ACC card download file. The options can be in any order. The options are: N - Display TNAM records T - Display TEXT records F - Display FILE records P - Display port configurations (default) S - Display subchannel and timeslot configurations If no options are specified, P is assumed.
ZMNTR - ZCOM Runtime Monitor Commands Slot The slot within the backplane bus where this interface is installed. Trms The number of terminals configured on this ACC card. Card Stat This is the current card state. For normal operation, this should be Up and Active.
ZMNTR - ZCOM Runtime Monitor Commands Status 86 The Status field shows the port status. The value of this display can be the following: Up Port is up and usable. Down Port has failed the selftest or the port was configured with an invalid configuration value. The port is unusable. TxLim Port buffer usage has reached the TXlim value.
ZMNTR - ZCOM Runtime Monitor Commands Example: Display the NAM records from the firmware download file. This command opens and reads the download file. ZMNTR> mx 1 1 n Interface card information for ACC ttgen input file TTGEN source /opt/acc/cfg/loopback.answ object /opt/acc/cfg/loopback.tmem Mux:01 Bus:00/00 Slot:01 Trms:0009 Card Stat:Up and active Hardware Revision: Rev.A Firmware download file: /opt/acc/z7400a/loopback.zabs Module: VMUX-1.1 Linktime: Wed Sep 10 05:43:06 1997 ROM-ID: Z7400A [01.
ZMNTR - ZCOM Runtime Monitor Commands 0549 0550 0551 0552 0553 0554 0555 0556 0557 0558 0559 0560 **** 01 01 01 01 01 01 01 01 01 01 01 01 ** 0V00 SVCI =n/c No 0V00 SVCI =n/c No 0V00 SVCI =n/c No 0V00 SVCI =n/c No 0V00 SVCI =n/c No 0V00 SVCI =n/c No 0V00 SVCI =n/c No 0V00 SVCI =n/c No 0V00 SVCI =n/c No 0V00 SVCI =n/c No 0V00 SVCI =n/c No 0V00 SVCI =n/c No ** Message totals address address address address address address address address address address address address 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0
ZMNTR - ZCOM Runtime Monitor Commands RC - Reset Rx, Tx and Error Counters Format: RC,nn,[mm] This command resets the counters of terminals in the range nn to mm. If only nn is entered, then the request is performed for only the one terminal. After the request has been made, the system asks for confirmation: Reset counters for ZLUs nn to mm, ok? - Answer YES to reset the counters or NO to abort the command. The RCX command resets the Level 2 X.25 statistical counters for all X.
ZMNTR - ZCOM Runtime Monitor Commands TM - Set Auto Repeat Time Interval Format: TM,nn The command sets the timeout value to “nn” seconds between 0 and 200. If set to 0, the timeout is cleared and the command does not repeat. Otherwise the last command entered will be repeated every “nn” seconds. Enter TM and the repeat time (anything between 1 and 5 inclusive is treated as 5 seconds). Then enter the command to be repeated. Use TM,0 to cancel the auto-repeat timeout and return to normal operation.
ZMNTR - ZCOM Runtime Monitor Commands NOTE While most ZMNTR commands are not case sensitive (ie upper and lower case are treated the same), the filename in the TR command must be entered with the correct case. The file must contain the ZMNTR commands to be executed. They are entered as they would be in the interactive mode. Comment lines must begin with an asterisk followed by a space, followed by the comment. Blank lines are allowed. For example the file example.
ZMNTR - ZCOM Runtime Monitor Commands TT - Display Terminal Information Format: TT,mm,nn,[name] This command displays information about the terminals in the ZLU range “mm” to “nn”. The [name] parameter is optional. If specified, then only terminals whose descriptions contain the string are shown. The TT command may be immediately followed by one or more of the command modifiers (See “Command Modifiers” on page 73). Example ZMNTR> tt 6 10 ZLU# Mx p:sc Terminal Description.. Rx.Mes Tx.
ZMNTR - ZCOM Runtime Monitor Commands Down The terminal is enabled and activated but the line is DOWN (or not connected). Usually a hardware problem. There is nothing waiting on its transmit queues. Dn,Sending Terminal is same as “Down” above. In addition, there is something pending in its transmit queues. Deactivated The terminal is enabled but not activated. Messages may usually be transmitted but not received from the terminal. There may be protocol-specific exceptions to this.
ZMNTR - ZCOM Runtime Monitor Commands Disabling Commenced disable of link X.25 Switched Virtual Circuits (SVCs): No call No call is established Call Setup In the process of setting up a call Call Estb The call has been established Resetting The call is being reset. Unacknowledged messages are discarded Clearing In the process of clearing the call X.
ZMNTR - ZCOM Runtime Monitor Commands Terminal descriptions for the virtual circuits are: SVC SVCO SVCI PVC - switched virtual circuit (two-way) switched virtual circuit (outgoing) switched virtual circuit (incoming) permanent virtual circuit Each of these may be followed by “=n/c” if the call is not connected, or by a logical channel number if the call is connected. To the right of this information, there is the X.121 address.
ZMNTR - ZCOM Runtime Monitor Commands 96 Chapter 3
4 Chapter 4 ZTERM - Interactive Routine Interface 97
ZTERM - Interactive Routine Interface Overview Overview ZTERM provides an interactive method of communicating with the ZCOM subsystem. In particular it provides interactive access to the ZCOM Application Program Interface (API). Using ZTERM it is possible to send messages to ZLUs, read from the ZTERM program’s primary ZLU input queue, peek at the primary ZLU, and send terminal control functions to terminal ZLUs.
ZTERM - Interactive Routine Interface Running ZTERM Interactively Running ZTERM Interactively To run ZTERM from the shell prompt $: $ zterm [commandfilename] ZTERM is usually invoked interactively, in which case the command file name is not specified.
ZTERM - Interactive Routine Interface Running ZTERM Interactively $ zterm 18:35:44 ZCOM Interactive command utility Rev4.02 18:35:44 Primary ZLU is 1106 ZTERM> dz,120 18:35:50 ZLU entry for ZLU # 120 Lcn .00. .01. .02. .03. .04. .05. .06. .07. .08. 000 E64F 0001 009F 0000 0000 544D 3030 3132 3020 010 0000 0000 0000 0000 007A 7EC8 0000 0000 0000 ZTERM> dz,121 18:35:54 ZLU entry for ZLU # 121 Lcn .00. .01. .02. .03. .04. .05. .06. .07. .08.
ZTERM - Interactive Routine Interface Running ZTERM from a Command File Running ZTERM from a Command File ZTERM may also be run from a command file to allow frequently used command sequences to be executed more conveniently. To invoke this mode and to pass the name of the command file, enter the file name as the second parameter after ZTERM: $ zterm For example, the file /tmp/test1.
ZTERM - Interactive Routine Interface ZTERM Available Commands ZTERM Available Commands The commands available in ZTERM (displayed by entering ?) are: ZTERM> Code CL CN CW DI DL DN DP DZ IT LG LP LQ LS LU MG MP MV MX TV RV ND - ? Description...................
ZTERM - Interactive Routine Interface ZTERM Available Commands /E - Exit Program Format: /E This command terminates ZTERM, closing its ZLU. This command has the same effect as EX. CL - Close ZLU Format: CL,ZLU Closes the specified program ZLU. Returns the ZLU to the ZCOM subsystem for reuse. Uses the zclos routine call. CN - Control Requests Format:CN,ZLU1,ZLU2,req,[mode],[port,type,poll,select],[t1,t2] The CN command is used to send control requests to terminal ZLUs in the range ZLU1 to ZLU2.
ZTERM - Interactive Routine Interface ZTERM Available Commands Functions in the same way as the SE command but in this case the zcntl routine is used to generate a control write request, rather than zsend (which generates a write request). ZTERM responds with: Input message (max 80 chars) Enter text for the control write, then press . DI - Control Displays Format: DI,on/off/error Controls the display of messages by commands that send or receive messages (e.g.
ZTERM - Interactive Routine Interface ZTERM Available Commands DL - Display Logical Terminal Table Information Format: DL,ZLU1 [,ZLU2] [,+Q] Displays the logical terminal information for the specified terminal ZLU or range of ZLUs. The information is in hexadecimal and ASCII. The +Q option suppresses the hexadecimal listing. See under “Terminal Table Pages” in the section on Tables and Data Structures in the ACC Programmer’s Reference Guide, for the logical terminal table layout.
ZTERM - Interactive Routine Interface ZTERM Available Commands 140 2020 2020 150 0000 4F46 160 0000 0000 170 0000 0000 180 0001 001F 190 0000 0000 200 0000 0000 210 0000 0000 220 0000 0000 230 0000 0000 240 0000 0000 250 0000 0000 260 0000 0000 270 0000 0000 09:03:50 * 2020 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 2020 0000 0000 0000 FFFF 0000 0000 0000 0000 0000 0000 0000 0000 0000 2020 0000 0000 0000 0007 0000 0000 0000 0000 0000 0000 0000 0000 0000 2020 0000 0000 0000 0007 00
ZTERM - Interactive Routine Interface ZTERM Available Commands 20:11:27 20:11:27 20:11:27 20:11:27 X25 VC number Tx Msg count Rx Msg count Error count 0 0 0 0 Lcn .00. .01. .02. .03. .04. .05. .06. .07. .08. .09. ASCII.....ASCII....
ZTERM - Interactive Routine Interface ZTERM Available Commands EX - Exit Program Format: /E This command terminates ZTERM, closing its ZLU. This command has the same effect as /E. IT - Interface Table Information Format: IT,card This command displays the interface table information for the specified ACC card, in hexadecimal and ASCII, as per the DZ command.
ZTERM - Interactive Routine Interface ZTERM Available Commands 260 0000 0000 00AD 3EA0 0000 0000 00AD 3EB0 0000 0000 270 00AD 3EC0 0000 0000 00AD 3EE0 0000 0000 00AD 7F00 280 0000 0000 007A AEC8 0000 0000 007A AE70 -> ->@ ->0 ->` z.H z.p LG - Get Logical Terminal Data From Queue Format: LG,zlu,[queue] This command retrieves logical terminal queue data from the specified logical terminal data queue.
ZTERM - Interactive Routine Interface ZTERM Available Commands LS - Allocate Logical Terminal Storage Format: LS,appl,label,size appl application number (0 for general allocation) label storage label (up to 6 ASCII characters) size Bit 15 = 0 : allocate if new Bit 15 = 1 : do not allocate Bits 14-0 : size of storage in words This command will find an existing storage for this application with matching label and size.
ZTERM - Interactive Routine Interface ZTERM Available Commands cannot be the only terminal linked to the original physical terminal; otherwise an error will be returned. This command uses the zltmg routine. MP - ZLU Mapping Format: MP,ZLU,MZLU Sets up a ZLU mapping. All messages for the ZLU are mapped to the MZLU as specified in the command. Uses the zmapr routine call.
ZTERM - Interactive Routine Interface ZTERM Available Commands MV - Move Message Format: MV,[zlu],[dzlu] Moves message between queues. If the first zlu is not specified, then the ZTERM primary program ZLU is assumed. If the destination dzlu is not specified, then the message is discarded, otherwise it is moved to the destination queue. This command moves the first message only from the head of the first ZLU queue. Uses the zqmve routine call.
ZTERM - Interactive Routine Interface ZTERM Available Commands DN - Display a node entry Format: ND, node or: DNI, index DN displays the node entry for node number “node”. DNI displays the node entry for node index “index”.
ZTERM - Interactive Routine Interface ZTERM Available Commands NM - Retrieve ZLU from Name Format: NM,name,[node] Retrieves the ZLU from the name only. Enter the name of the ZLU, (8 bytes maximum). If there is a ZLU of that name, the system will respond with “ZLU is nnn”. The remote node call is not currently implemented. Uses the zname routine call. OP - Open Program ZLU Format: OP,[name],[PRIM] Opens a program ZLU. If PRIM is not specified, then the program ZLU will be an auxiliary.
ZTERM - Interactive Routine Interface ZTERM Available Commands 000 5468 6973 2069 7320 6120 7465 7374 206D 6573 7361 This is a test message 010 6765 e.
ZTERM - Interactive Routine Interface ZTERM Available Commands PT - Set Port Parameters Format: PT,card,port,rcode,param,[config1],[config2] Sets port parameters. The parameters are similar to those used in the zport call. See under zport in the ACC Programmer’s Reference Guide. All terminals on the port must be disabled before this command is used.
ZTERM - Interactive Routine Interface ZTERM Available Commands ZTERM> pu 10 96 2 16:03:50 Input word 0001 - 1 16:03:53 Input word 0002 - 2 ZTERM> Chapter 4 117
ZTERM - Interactive Routine Interface ZTERM Available Commands PZ - Peek at ZLU Format: PZ,ZLU,[wait] Format: PZHD,ZLU,[wait] Peeks at any program ZLU. This command is the same as the PE command, except that any program ZLU can be entered. If wait is specified, then the program will display the messages as they are received. If no messages are received then an INT signal can be used to interrupt the wait (this can usually be generated by using a ^C).
ZTERM - Interactive Routine Interface ZTERM Available Commands Reads the ZTERM program primary ZLU. If wait is specified, then the program will continue to read the ZLU display the messages as they are received. If no messages are received then an INT signal can be used to interrupt the wait (this can usually be generated by using a ^C). ZTERM> re 08:12:54 Message from program ZLU #0802 length 22 tag1=0000 tag2=0000 Lcn .00. .01. .02. .03. .04. .05. .06. .07. .08. .09. ASCII....ASCII....
ZTERM - Interactive Routine Interface ZTERM Available Commands done with buffers shorter than 10 bytes. The latency statistics are displayed when the RL command terminates or is terminated. sendmode The mode as explained under zsend in the ZCOM routine calls section of the ACC Programmer’s Reference Guide. Each received message is resent with this mode. dzlu The ZLU to which the message is to be routed (default to source if not specified).
ZTERM - Interactive Routine Interface ZTERM Available Commands RV - Receive and validate messages Format: RV,[LI],[AC],[maxtime] Receive and validate messages from primary ZLU. This command works in conjunction with the TV command in another copy of ZTERM to validate both message content and sequence. Optionally LI may be specified to list the incoming data in hex as it is received. AC may also be specified if the protocol module requires reactivation after each received message.
ZTERM - Interactive Routine Interface ZTERM Available Commands RZ - Read ZLU Format: RZ,ZLU,[wait] Format: RZHD,ZLU,[wait] Reads any program ZLU. This command functions in exactly the same way as the RE command, however as a ZLU number is entered, any program ZLU can be read. Uses the zread routine call.
ZTERM - Interactive Routine Interface ZTERM Available Commands S7 - SS7 processing Format: S7, [OF] This command enables special processing for SS7 Level-1 devices. S7,OF disables the SS7 processing. When SS7 processing is enabled the RV, TX, RX, XM, and RL commands are modified for testing with an SS7 level-1 protocol. In particular, the first 2 bytes of all transmitted frames are sequenced to ensure that any two consecutive frames will always contain different data in these bytes.
ZTERM - Interactive Routine Interface ZTERM Available Commands 16:17:31 Driver status: Initialized,Enabled,Inactive,Available 16:17:31 1 Receive msgs, 0 Transmit msgs, 131072 Errors 16:17:31 * ZTERM> ST translates some of the physical terminal table fields (as provided in the DP command) into the above information. SW - Swap Physical Terminal Tables Format: SW,ZLUA,ZLUB The physical terminal table data and associated logical terminals are exchanged by this command. Makes use of the zxcpt call.
ZTERM - Interactive Routine Interface ZTERM Available Commands SZ - Queue Size Format: SZ,[zlu] Gets program queue size. Returns the number of messages queued to the specified program ZLU. (Cannot be a terminal ZLU.) If a ZLU is not entered, the ZTERM program ZLU is used. The system responds with “ZLU nnn has queue depth nnnn”. Uses the zqsze routine call. TM - Timeouts Format: TM,ZLU,time Sets the timeout on specific program ZLU in seconds.
ZTERM - Interactive Routine Interface ZTERM Available Commands tagp Terminal tag parameter (mrqtag) maxtime Optional maximum runtime apno If set this must match the ltapno field in the logical terminal table of the terminal ZLU, otherwise no messages will be sent on that ZLU.
ZTERM - Interactive Routine Interface ZTERM Available Commands apno If set this must match the ltapno field in the logical terminal table of the terminal ZLU, otherwise no messages will be sent on that ZLU. The test proceeds until the total number of messages are sent or the test is interrupted using sigint (usually ^C).
ZTERM - Interactive Routine Interface ZTERM Available Commands 128 Chapter 4
5 Chapter 5 ZSCAN - Display ZCOM Tables & Buffers 129
ZSCAN - Display ZCOM Tables & Buffers Overview Overview ZSCAN is a utility provided to allow the contents of the ZCOM kernel tables and buffers to be viewed.
ZSCAN - Display ZCOM Tables & Buffers Running ZSCAN Running ZSCAN To run ZSCAN interactively from the shell prompt $ enter: $ zscan ZSCAN: ZCOM 6.2.0.0 System Memory Display Utility, Rev 2.0 Memory image file is of 32-bit kernel zscan> When started up, ZSCAN displays the version of ZCOM it expects and its own software version. It opens the memory image file and shows whether the file is from a 32-bit or 64-bit kernel. Note that the memory image file is of the same layout for both 32/64-bit kernel.
ZSCAN - Display ZCOM Tables & Buffers Running ZSCAN Usage: zscan [options] [-m mfile] [-i ifile] [-k kfile] Options: -c Memory image file is a system core file mfile Message text file (standard default) ifile Memory image file (default: /dev/zmon - running system) kfile Kernel file: required if -c specified (default: /stand/vmunix) Normal use of ZSCAN is with no parameters on the runstring, so it defaults to the running system, default message file (/opt/acc/msg/default.msg) and non-core file mode.
ZSCAN - Display ZCOM Tables & Buffers Running ZSCAN To run against a core file vmcore.3 with corresponding kernel file vmunix.3: % zscan -c -i /var/adm/crash/vmcore.3 \ -k /var/adm/crash/vmunix.3 To run against core file vmcore.1 with current kernel: % zscan -c -i /var/adm/crash/vmcore.1 To run with a text message file: % zscan -m def.zscan.
ZSCAN - Display ZCOM Tables & Buffers ZSCAN Available Commands ZSCAN Available Commands The commands available in ZSCAN (displayed by entering ?, ?? or help) are as follows: zscan> ?? Command en zl pt te qh nd dsc !cmd ?, ?? - Description ................ Display ZCOM environment Display ZLU information Display physical terminal Display PTTs on a mux Display program queue header Display node information Dynamic System Config. info.
ZSCAN - Display ZCOM Tables & Buffers ZSCAN Available Commands Message type 2 Tag1 1 Response code 0 Tag2 0 Data length 100 bytes Request code 0 Term# 0 Lcn .00. .01. .02. .03. .04. .05. 000 5A74 3032 3039 3100 206D 6573 010 2030 3030 3031 206C 656E 6774 020 6F70 7172 7374 7576 7758 797A 030 494A 4B4C 4D4E 4F50 5172 5354 040 6364 6566 6768 696A 6B4C 6D6E From: node 123, ZLU 10001 (60386) To: node 123, ZLU 10001 (60386) Aux: node 0, ZLU 0 (00000) Status 0x00 Tag 0x00 .06. .07. .08. .09. ASCII.....ASCII....
ZSCAN - Display ZCOM Tables & Buffers ZSCAN Available Commands DM - Display ZCOM Memory in HEX and ASCII Format: dm [loc] [value] The DM command is used to display ZCOM memory in hex and ASCII at address [loc] for size [value]. If [loc] is specified as one of the following keywords (rather than an address), the relevant table entry is displayed: Loc........ header node zlu ltt ptt ift lookup response queue Table displayed..................
ZSCAN - Display ZCOM Tables & Buffers ZSCAN Available Commands DSC - Dynamic System Configuration Format: dsc This command shows some internal kernel information about the dynamic system configuration of the ZCOM subsystem. The DSC feature allows the ZCOM configuration (as defined in the TTGEN file) to be modified while the system is running. When a DSC request is in-progress, some system activities must be suspended.
ZSCAN - Display ZCOM Tables & Buffers ZSCAN Available Commands Example: zscan> Header System Source Object en label: name: file: file: ZCOM ZCOM Rev: 6.2.0.0 ACC ttgen input file /opt/acc/cfg/loopback.answ /opt/acc/cfg/loopback.tmem Area............... System Header Node Entries ZLU Entries Logical Terminals Physical Terminals Interface Tables Response Records Queue Headers Buffer Pool System Total: LTT.Storage 1 2 Label X25CNT ANLYZR Address (hex)......
ZSCAN - Display ZCOM Tables & Buffers ZSCAN Available Commands Displays interface table information for interface (or Mux) [iftno]. If [iftno] is not specified, zero is used. The information returned is further described under the interface table subsection of the Tables and Data Structures section of the ACC Programmer’s Reference Guide.
ZSCAN - Display ZCOM Tables & Buffers ZSCAN Available Commands 2 IFQok 2 DRQok zscan> 0 0 0 00000000:00000000 0 00000000:00000000 0 0 0 2147483647M 0 2147483647M Note that the values in the Head:Tail column are the buffer addresses that may be used by the BF command to view the buffer contents. LT - Logical Terminal Table Format: it [first] [last] [c|q|r] Displays logical terminal table information from the Logical Terminal Table (LTT) numbers [first] to [last].
ZSCAN - Display ZCOM Tables & Buffers ZSCAN Available Commands Example: zscan> lt 1 2 LTT# ZLU# NxtZ# 1 1 1 2 300 300 PTT# SHQ.Msg DQ1.MSG DQ2.Msg DQ3.Msg DQ4.Msg 1 0 0 0 0 0 2 0 0 0 0 0 zscan> lt 1 2 c LTT# ZLU# MxZLU RcZLU Dtype Ltype Flags Lstat Appno Name................ 1 1 0 0 48 99 0000h 0000h 10 L2 DCE 2 300 0 0 49 99 0000h 0000h 99 L3 pvc zscan> lt 1 2 r LTT# ZLU# MxZLU(Node#) PRZLU(Node#) SHARED RCVRS(Node#) 1 1 0(00000) 0(00000) 2 300 0(00000) 0(00000) zscan> lt 1 2 q LTT# Queue N.
ZSCAN - Display ZCOM Tables & Buffers ZSCAN Available Commands Examples: zscan> nd Local node number: Node table size: Node# T.Out Hosts 222 0 0 111 5 1 ZNODE.Queue N.Msg 0 222 10 ZNODE pid: ZNODE signal: ZNODE idle: State Up Up In.Msg 24 0 1945 16 0 In.Bytes 23432 0 Queue low: Queue high: Queue waiter: Out.Msg 12 0 5 10000 0 Out.Bytes 1232 0 N.Bytes Head:Tail(hex)... Waits Total.Msg Max.M Limit...... 0 00000000:00000000 0 0 2147483647M zscan> nd 111 Node# T.
ZSCAN - Display ZCOM Tables & Buffers ZSCAN Available Commands zscan> pt 1 2 q PTT# Queue N.Msg 1 XPSok 0 1 HTXok 0 1 LTXok 0 1 UAQok 0 2 XPSok 0 2 HTXok 0 2 LTXok 0 2 UAQok 0 N.Bytes 0 0 0 0 0 0 0 0 Head:Tail(hex)... Waits Total.Msg Max.M Limit......
ZSCAN - Display ZCOM Tables & Buffers ZSCAN Available Commands QH - List Queue Header Format: qh [first] [last] This command displays the program queue headers in the range [first] to [last]. If [last] is omitted only [first] queue header is displayed. If [first] and [last] are omitted then queue header 0 (free queue) is displayed. The free queue manages the list of free buffers in the system. The other queues (1,2,3...
ZSCAN - Display ZCOM Tables & Buffers ZSCAN Available Commands 6 Stop Total: 0 4 0 00000000:00000000 3185992 0 0 0M For the meaning of the queue header fields, see under the Queue Header subsection of the Tables and Data Structures section of the ACC Programmer’s Reference Guide. Note that for FreeQ, the “Limit” value actually shows the total number of buffers allocated to other queues.
ZSCAN - Display ZCOM Tables & Buffers ZSCAN Available Commands QS - Scan All Non-Empty Buffer Queues Format: qs This command gives a detailed report of buffer distribution within all buffer queues in the system. It goes through all legal ZCOM buffer queue headers, and displays all queues that have messages. Since the scan is interleaved with other ZCOM activities, the report may have minor inconsistencies in a busy ZCOM system. Example: zscan> qs Checking remote data queue (ZNODE queue) ...
ZSCAN - Display ZCOM Tables & Buffers ZSCAN Available Commands Example: zscan> rr 1 9 RspID Address. Type... R.Code Seq.Number 1 00000000 0 0 2 00000000 0 0 3 00000000 0 0 4 00000000 0 0 5 00000000 0 0 6 00000000 0 0 7 00000000 0 0 8 00000000 0 0 9 00000000 0 0 Time R.Node Q.Msg Q.Head:Tail(hex).
ZSCAN - Display ZCOM Tables & Buffers ZSCAN Available Commands zscan> te 0 q PTT# Queue N.Msg 1 XPSok 0 1 HTXok 0 1 LTXok 0 1 UAQok 0 2 XPSok 0 2 HTXok 0 2 LTXok 0 2 UAQok 0 3 XPSok 0 . . . 37 XPSok 0 37 HTXok 0 37 LTXok 0 37 UAQok 0 38 XPSok 0 38 HTXok 0 38 LTXok 0 38 UAQok 0 zscan> N.Bytes 0 0 0 0 0 0 0 0 0 . 0 0 0 0 0 0 0 0 Head:Tail(hex)... Waits Total.Msg Max.M Limit......
ZSCAN - Display ZCOM Tables & Buffers ZSCAN Available Commands Note that the table shown in the examples have had lines removed to reduce the size of the display. The “. . . .” represent one or more lines that have been deleted. ZL - List ZLUs Format: zl [first] [last] [options] Displays ZLU information from ZLU number “first” to “last”.
ZSCAN - Display ZCOM Tables & Buffers ZSCAN Available Commands 19 20 Not initialized Not initialized zscan> zl 1 9999 p ZLU#(Cksum) Name.... 1001(30214) pcapt00 1002(56185) X25CN 1003(63457) Zt01875 1004(63439) Za01875 Owner Status...............................
6 Chapter 6 ZMLOG - Diagnostic Message Logging 151
ZMLOG - Diagnostic Message Logging ZCOM Diagnostic Message Logging Mechanism ZCOM Diagnostic Message Logging Mechanism The ZCOM subsystem has a centralized diagnostic message logging mechanism that keeps a sequenced, and time stamped record of events generated by ZCOM and its related components. The messages are usually displayed on a terminal device as well as being logged to files. The actual combination of logging devices and files may be customized to meet individual system requirements.
ZMLOG - Diagnostic Message Logging ZCOM Diagnostic Message Logging Mechanism and utility programs, or by application programs. The ZCOM software library supplies the routines that may be called by application programs to log messages. The messages are written by the drivers or programs in a binary form which is passed to ZMLOG via the device file /dev/zmlog.
ZMLOG - Diagnostic Message Logging ZCOM Diagnostic Message Logging Mechanism After 7 days, the system reuses the daily files. When files must be saved for longer than 7 days, they must be moved or renamed so they do not get recycled. Running Without ZMLOG Usually the ZCOM system uses ZMLOG as the message logging daemon, however ZCOM will work correctly without ZMLOG - and will discard all the messages that are generated.
ZMLOG - Diagnostic Message Logging ZCOM Diagnostic Message Logging Mechanism /etc/zmlog -t -nb -p 0 -z /dev/zmlog -m /opt/acc/msg/default.msg \ -l /var/opt/acc/log -d /dev/console The run string (including options) for ZMLOG is: Usage: zmlog [options] [-p pri] [-z zfile] [-m mfile] [-B bmax] [-T tmax] [-l lpath] [-d dev] ...
ZMLOG - Diagnostic Message Logging ZCOM Diagnostic Message Logging Mechanism message priorities are specified in the message file and may be customized if required. If this parameter is not specified 0 is used as the priority level. 156 -z Specify an alternate file to read the diagnostic message stream from. The name of the new file is . If this parameter is not specified then /dev/zmlog is used. -m Specify the message file for expanding the binary logs to text.
ZMLOG - Diagnostic Message Logging ZCOM Diagnostic Message Logging Mechanism Setting Up Customized or Application Specific Messages Each message that can be generated by ZCOM, its daemons, its utilities, or application programs using the ZCOM services, must have a corresponding entry in the message file. The entries in the message file are organized by program or module name, and message number within that program or module. The message file is generated from one or more text files.
ZMLOG - Diagnostic Message Logging ZCOM Diagnostic Message Logging Mechanism This uses the input file /opt/acc/msg/french.txt and generates the output file /opt/acc/msg/french.msg. The txt2msg output file is used by ZMLOG to expand the binary log messages generated by ZCOM subsystem to readable text. Use the -m option or specify the environment variable LANG to make ZMLOG select a message file other than the default. See the above description for the -m option.
ZMLOG - Diagnostic Message Logging ZCOM Diagnostic Message Logging Mechanism 3. In (b),(d), the second $ is ignored. It is used to mark the beginning of message text. This mechanism allows leading spaces to be specified. 4. Long text may be spread across multiple lines. The lines will just be merged together (LineFeed removed), until the next line begins with $ is found. A ~ may be used as the first character of a continuation line. A LineFeed will be inserted between each ~ continuation line. 5.
ZMLOG - Diagnostic Message Logging ZCOM Diagnostic Message Logging Mechanism $(1) Message 1 of PROGX (not progx). $(2)$ Message 2 of PROGX (not progx). In the preceding example, error message “Test Error Message on Channel, int(%1$d)” is assigned to error message 3, from program progx. Error message 3 has a priority of 2. Note that each error message can have zero or more variables. For instance, error message 25 is composed of text plus 2 variables.
ZMLOG - Diagnostic Message Logging ZCOM Diagnostic Message Logging Mechanism #include #include long long message_number,error_number,numb_vars; var_descriptor,var_value; /* During program initialization setup the program name - max 5 chars */ zcomlname (”progx”); . . .
ZMLOG - Diagnostic Message Logging ZCOM Diagnostic Message Logging Mechanism #define #define #define #define #define #define #define #define #define #define #define ZCOM_AT_STR ZCOM_AT_ERRNO ZCOM_AT_ZERROR ZCOM_AT_ZERR2 ZCOM_AT_ZSTAT ZCOM_AT_XSTAT ZCOM_AT_FMPERROR ZCOM_AT_UCHAR ZCOM_AT_USINT ZCOM_AT_INT64 ZCOM_AT_UINT64 4 5 6 7 8 9 10 11 12 13 14 /* /* /* /* /* /* /* /* /* /* /* string */ file system error */ ZCOM error */ ZCOM error (short int) */ ZCOM status */ X25 status */ FMP error */ unsigned cha
ZMLOG - Diagnostic Message Logging ZCOM Diagnostic Message Logging Mechanism NOTE ZMLOG internally uses sprintf() to convert the arguments to display text. However, due to technical difficulty with sprintf() in supporting arbitrary 64-bit parameters (i.e. ZCOM_AT_INT64 or ZCOM_AT_UINT64), ZMLOG can only display the value of the lower 32-bit for each 64-bit argument logged.
ZMLOG - Diagnostic Message Logging ZCOM Diagnostic Message Logging Mechanism Format of ZMLOG Messages Usually, ZMLOG extracts and prints the error log messages generated by the ZCOM subsystem. However a user application can be used in the place of ZMLOG if specialized processing of the messages is required. To replace ZMLOG with user supplied program it is necessary to understand the format of the binary message buffer output from the device file /dev/zmlog.
ZMLOG - Diagnostic Message Logging ZCOM Diagnostic Message Logging Mechanism Field Description Error code 4 Message number 4 Variable 1 - Argument type 1 Variable 1 - Data length 1 Variable 1 - Data variable (specified in data length) ... Chapter 6 Length in bytes ... ... ...
ZMLOG - Diagnostic Message Logging ZCOM Diagnostic Message Logging Mechanism User Error Logging Application The following code shows sections from a program intended to read from the ZCOM message log device file /dev/zmlog. Note the header file /opt/acc/include/zcom/zcomsys.
ZMLOG - Diagnostic Message Logging ZCOM Diagnostic Message Logging Mechanism len = read (fd,&mlog,sizeof(mlog)); /*blocked read if no data. if there is data, then read will be satisfied on either ’buffer 1/3 threshold logic’ or in 1 sec. */ /* check buffer log size */ if (mlog.blen != ZCOM_MLSIZE - (sizeof(mlog) - len)) {handle_error() } /* detected bad zcom log header */ /* so skip this log buffer */ /* check for overrun errors */ if (mlog.
ZMLOG - Diagnostic Message Logging ZCOM Diagnostic Message Logging Mechanism 168 Chapter 6
7 Chapter 7 ZMON - ZCOM Control Program 169
ZMON - ZCOM Control Program Overview Overview ZMON is the program responsible for initializing and managing the ZCOM subsystem. Its operation is closely integrated with the ZCOM LDM (Logical Device Manager). Its primary tasks are: • Loading the TTGEN output file into the ZCOM kernel memory. • Sequencing the startup of the ZCOM system with the assistance of the LDM. • Downloading and initializing the Mux cards. • Restarting the Mux cards after a powerfail or Mux firmware panic.
ZMON - ZCOM Control Program ZMON Options ZMON Options ZMON has several options that can be selected with parameters in the run string. If ZMON is run with no parameters, it will display all the possible options and parameters. It is highly recommended that you only execute zmon cold and stop commands through the zmasterd program.
ZMON - ZCOM Control Program ZMON Command Descriptions ZMON Command Descriptions Cold Function: Cold start ZCOM subsystem Format: zmon cold The cold start command is used to initialize the run-time portion of the ZCOM subsystem. The file specified by filename is the output file from TTGEN. It contains an image of many of the ZCOM tables. ZMON downloads this file to the ZCOM kernel memory through the device file /dev/zmon.
ZMON - ZCOM Control Program ZMON Command Descriptions 15:24:13 zmon 15:24:13 zmon 15:24:13 zmon 00110 00020 00004 Card 0 startup successful, card READY Cold start completed, ZCOM system ready Waiting for ZMON requests ... The message “zmon 00004 Waiting for ZMON requests ...” indicates that ZCOM is up and ready for use. NOTE Although you may use ZMON directly to initialize and startup the ZCOM sub-system, it is highly recommended that you startup the ZCOM sub-system using “zmasterd cold ”.
ZMON - ZCOM Control Program ZMON Command Descriptions Status Function: Display ZCOM subsystem status Format: zmon status The STATUS request command is used to display the ZCOM system status in the ZCOM message log. For example if ZCOM is running The following would be expected: zmon status 14:32:18 zmon 00002 14:32:18 zmon 00006 14:32:18 zmon 00062 -Ready(running) Resource manager (Rev 1.32) for ZCOM 6.2.0.0 Getting ZCOM system status ...
ZMON - ZCOM Control Program ZMON Command Descriptions Restart Function: Restart Mux card Format: zmon restart This command is used to manually restart the firmware on a Mux card. This may be required for example to update the software on the card. When the card is restarted the card is reset, downloaded, configured, and restored to the state immediately before the restart.
ZMON - ZCOM Control Program ZMON Command Descriptions p2 selects which LDM module to log debug message. Each different LDM module has a different file ID. Only the module with the matching id will log the debug messages. If this parameter is zero (0), then all LDM modules will log debug messages. Nodebug Function: Disable LDM driver debugging Format: zmon nodebug This command disables the logging of debug messages from the LDM driver.
8 Chapter 8 ZNODE - Remote Node Daemon 177
ZNODE - Remote Node Daemon Overview Overview The programmatic interface that is provided by the ACC Mux Subsystem provides the ability to control the muxes that are attached to the node on which the program is running, as well as muxes on remote nodes. The znode daemon provides this functionality. The znode daemon allows programs to communicate to any ACC Mux subsystems that reside on other systems in the same manner that they communicate to the local subsystem. The use of znode requires the following: 1.
ZNODE - Remote Node Daemon znode Options znode Options The runstring for znode is the following: % znode [-h ] [-s ] [-d] where: -h Sets the znode heart beat timeout to n seconds (default is 5 seconds). This is useful on slow LANs (or WANs). -s Sets the interval in seconds for updating the node status and statistics kept in the ZCOM system. Default is 2 seconds. -d Debug mode. Does not run as daemon; only prints useful information. The znode program must be started after zmon is started.
ZNODE - Remote Node Daemon Remote Node TTGEN Configuration Requirements Remote Node TTGEN Configuration Requirements Node configuration information used by the znode daemon must be added to both the local and remote node TTGEN configuration files. The first item that must be configured is the number of nodes that will be communicated with by the programs on the system, including the local node. For example, if a program will communicate with 4 remote nodes, the total number of nodes will be 5.
ZNODE - Remote Node Daemon Remote Node TTGEN Configuration Requirements The last parameters provide addressing information for how to reach the node. A single address can be given, in which case all requests from the local node to the remote node will be sent to this address. Up to four addresses can be given, in which case the requests that are sent from the local node to the remote node will be load-shared across all of the addresses.
ZNODE - Remote Node Daemon Accessing Remote Nodes Accessing Remote Nodes Remote Nodes may be accessed by making ZCOM Interface calls. Those requests that can be made to remote nodes have an input parameter of type zaddr_type. This parameter indicates which zlu is to be affected, and what node that zlu resides on.
ZNODE - Remote Node Daemon Demonstrating Remote Node Functionality Demonstrating Remote Node Functionality To demonstrate that the remote nodes are correctly configured and are communicating with the local node, an example is shown below. The entries typed are shown in bold type and the sequence is indicated by a number to the left of each entry. Note that the entries are typed in sequence at both nodes A and B.
ZNODE - Remote Node Daemon Demonstrating Remote Node Functionality Node B (Number 20) # zterm 11:19:50 ZCOM Interactive command utility 11:19:50 Primary ZLU is 3001 3 ZTERM> rl 11:20:03 11:20:03 11:20:03 11:20:03 11:20:03 11:20:03 11:20:03 11:20:03 11:20:03 11:20:03 Msg Msg Msg Msg Msg Msg Msg Msg Msg Msg from from from from from from from from from from prog prog prog prog prog prog prog prog prog prog ZLU#03001(00010) ZLU#03001(00010) ZLU#03001(00010) ZLU#03001(00010) ZLU#03001(00010) ZLU#03001(00010
9 Chapter 9 ZMASTERD - Daemon Monitoring Feature 185
ZMASTERD - Daemon Monitoring Feature Overview Overview The ACC ZCOM subsystem requires the use of daemon programs to provide its features. For example, the logging facility requires the zmlog daemon. For the multinode processing feature, the znode daemon is required. Other protocol accessory products to the ACC Mux subsystem product may also require daemon programs, for example, the X.25 Protocol module and the ACC X.25/9000 Link Software require the use of the zx25d_init daemon.
ZMASTERD - Daemon Monitoring Feature zmasterd Usage zmasterd Usage The zmasterd daemon is run as follows: usage: zmasterd zmasterd zmasterd zmasterd zmasterd zmasterd cold stop deact act [ ””] kill Zmasterd makes use of the file /opt/acc/cfg/zmasterd_list, which contains the daemons that zmasterd is responsible for starting, stopping, and monitoring.
ZMASTERD - Daemon Monitoring Feature zmasterd_list File Format zmasterd_list File Format The file /opt/acc/cfg/zmasterd_list contains the following: • A list of daemons to be started and monitored by zmasterd when it is run with no runstring parameter. This list also includes the runstring parameters to use when starting the daemons. • A list of programs to be scheduled “once” by zmasterd when it is run with no runstring parameter or with the cold option.
ZMASTERD - Daemon Monitoring Feature Sample zmasterd_list File Sample zmasterd_list File The /opt/acc/cfg/zmasterd_list file that is provided with the ACC Base product contains the following: # HP - /opt/acc/cfg/zmasterd_list file # Start these daemons when zmasterd is started, and monitor them: start zmlog start zmon cold /opt/acc/cfg/loopback.tmem start znode # Stop these daemons when zmasterd is run with the stop option.
ZMASTERD - Daemon Monitoring Feature Typical Usage Typical Usage The typical use of zmasterd is the following: • The ACC Base software will provide an appropriate zmasterd_list file. • The ACC protocol software will automatically customize the zmasterd_list file to add in any daemons they require. • The daemons for the ACC Subsystem and any protocol accessory products that are installed will be started up when either of the following is run: % zmasterd % zmasterd cold /opt/acc/cfg/loopback.
ZMASTERD - Daemon Monitoring Feature Special Assumptions Special Assumptions Zmasterd makes special assumptions about zmlog and zmon, and takes special action with these daemons. Chapter 9 • Zmasterd will always bring up zmlog. If there is no zmasterd_list file, or if there is a file but zmlog is not in it, zmasterd will still start zmlog with no runstring parameters. This is so that the fact that zmasterd was started will always be recorded.
ZMASTERD - Daemon Monitoring Feature Bringing Up the ACC Subsystem Bringing Up the ACC Subsystem The ACC Subsystem is brought up by running zmasterd with no runstring parameters or with the cold parameters. This causes zmasterd to read the zmasterd_list and take the following actions: 1. Zmasterd checks to see if the zmasterd daemon is already running in the system. If the zmasterd daemon is already active and zmon cold has been scheduled successfully, the second invocation of zmasterd will exit.
ZMASTERD - Daemon Monitoring Feature Bringing Up the ACC Subsystem error will be logged. Note that zmasterd can only monitor daemons that it starts: Daemons that are in its start list, but are already running at this point will not be monitored! 6. If any daemon that zmasterd has started terminates, zmasterd will immediately detect this and then restart that daemon (however, zmasterd will not restart a terminated daemon if that daemon has terminated for more than three times within a 5-minute interval).
ZMASTERD - Daemon Monitoring Feature Restarting Terminated Daemons Restarting Terminated Daemons If zmasterd detects that a daemon that it started has terminated, it will attempt to restart that daemon. 194 • If the daemon that has terminated is zmon, it will be restarted with the queue parameter. This will cause zmon to continue functioning and processing requests without re-downloading the .tmem file.
ZMASTERD - Daemon Monitoring Feature Stopping Daemons Stopping Daemons Daemons that zmasterd is managing may be stopped by running zmasterd stop. When daemons managed by zmasterd are stopped by running zmasterd stop, the following actions occur: 1. zmasterd rereads the /opt/acc/cfg/zmasterd_list file if it exists. 2. If no zmasterd_list exists, zmasterd invokes zmon stop to stop the ACC Mux subsystem and zmasterd stops all running daemons except zmlog. 3.
ZMASTERD - Daemon Monitoring Feature Deactivate Option Deactivate Option The deactivate directive is used to terminate a daemon that was started by zmasterd and to cause it to no longer be monitored. The format of the command is: %zmasterd deact This will cause the daemon to be killed, and zmasterd will not try to restart that daemon. Note that zmon may not be deactivated. In order to terminate zmon, zmasterd stop must be run.
ZMASTERD - Daemon Monitoring Feature Activate Option Activate Option The activate directive is used to cause zmasterd to start a daemon, and to monitor that daemon. This can be used to restart a daemon that has been deactivated, or it can be used to start a daemon that was not in the original zmasterd_list file.
ZMASTERD - Daemon Monitoring Feature Important Notes Important Notes 198 • zmasterd can only handle daemons that are provided by the ACC products. • These daemons must reside in /opt/acc/bin/. • In the case that zmasterd and all daemons it has launched need to be terminated, use the kill option (zmasterd kill). • After the ACC system is brought up, zmasterd will run as a daemon to monitor the other running ACC daemons.
10 Chapter 10 WATCH - Mux Shutdown Feature 199
WATCH - Mux Shutdown Feature Overview Overview The Dual Interface Configurations allow two ACC interface cards to be connected to a one mux panel/cable. In order for the interface ports to be accessed, they must be configured as LOOPBACK from one interface card, and as RS232, X.21 (or whatever is appropriate) from the other interface card.
WATCH - Mux Shutdown Feature Configuration Requirements Configuration Requirements The following configuration requirements must be met to use the watch feature: • The .zlnk file used to create the .zabs file being used must include monitor.zrel. Note that monitor.zrel is included in all .zlnk files that are provided by the ACC base product, and is therefore available via all .zabs files that are provided. • The ttgen .answ file that corresponds to the .
WATCH - Mux Shutdown Feature Running watch Running watch The watch program can be run manually as follows: # watch [] If no timeout parameter is given, the default time between the mux card and the watch daemon is 10 seconds. This can be changed to be between 1 and 127 seconds. The watch program must be started up after zmon is started. In the case that zmon is terminated, watch will also terminate. It must then be restarted after zmon is restarted.
WATCH - Mux Shutdown Feature Observing the watch Feature Observing the watch Feature The watch functionality can be observed by doing the following: • Create a configuration that meets all of the requirements listed in the previous section. • Bring up the ACC Mux subsystem, including the watch program. • Reboot the system by running reboot -h. • Wait for 2 times the timeout value. The light on the mux card should turn yellow, indicating that the mux has been shutdown.
WATCH - Mux Shutdown Feature Observing the watch Feature 204 Chapter 10
A Appendix A TTGEN Configuration File 205
TTGEN Configuration File TTGEN Configuration File Example TTGEN Configuration File Example The following example is intended as a guide only, and will not work with all hardware configurations. TTGEN -sto x25.answ x25.
TTGEN Configuration File TTGEN Configuration File Example first_insvc last_insvc first_svc last_svc first_outsvc last_outsvc def_inpacket def_outpacket def_inwindow def_outwindow T1_timer T2_timer T3_T4_timer 1 9 0 0 0 0 7 /* 128 7 /* 128 2 2 res_100ms, res_100ms, res_1s, Term 0001 0:0 x25.svc.out Repeat 8 byte pkt size */ byte pkt size */ 20 10 60 /* T1 = 2 seconds */ /* T2 = 1 second */ /* T4 = 60 seconds */ 0h 0h 99 0 0 0 0 ”L3 svc” Term 0601 0:1 X25.
TTGEN Configuration File TTGEN Configuration File Example def_outwindow T1_timer T2_timer T3_T4_timer 2 res_100ms, 20 res_100ms, 10 res_1s, 60 /* T1 = 2 seconds */ /* T2 = 1 second */ /* T4 = 60 seconds */ Term 0021 0:2 x25.svc.out 0000h 6200h 99 0 0 0 0 ”L3 svc” Repeat 8 Term 0603 0:3 X25.
TTGEN Configuration File TTGEN Configuration File Example option no_autostart last_pvc first_insvc last_insvc first_svc last_svc first_outsvc last_outsvc def_inpacket def_outpacket def_inwindow def_outwindow T1_timer T2_timer T3_T4_timer 37h 0 1 9 0 0 0 0 7 /* 128 7 /* 128 2 2 res_100ms, res_100ms, res_1s, byte pkt size */ byte pkt size */ 20 10 60 /* T1 = 2 seconds */ /* T2 = 1 second */ /* T3 = 60 seconds */ Term 0606 0:6 X25.
TTGEN Configuration File TTGEN Configuration File Example def_inpacket def_outpacket def_inwindow def_outwindow T1_timer T2_timer T3_T4_timer 7 /* 128 7 /* 128 2 2 res_100ms, res_100ms, res_1s, byte pkt size */ byte pkt size */ 20 10 60 /* T1 = 2 seconds */ /* T2 = 1 second */ /* T3 = 60 seconds */ Term 0071 0:7 x25.svc.
TTGEN Configuration File System Response System Response Below is the listing that results from the preceding runstring: TTGEN -sto x25.answ x25.tmem Note that any undefined ports on each interface are reported. Page 1 ttlst: x25.tmem System Summary Fri Jan 14 16:32:13 2000 FILENAMES Source file: /opt/acc/cfg/x25.answ Object file: /opt/acc/cfg/x25.tmem REVISIONS ZCOM Rev: TTGEN Rev: 6.2.0.0 1.1.0.
TTGEN Configuration File System Response Logical Terminals Starting offset: Total size: Size of table: Number of tables: Unused tables: 45856 (0x0000B320) 328000 bytes (9.1%) 656 bytes (user data = 256 bytes) 500 0 Physical Terminals Starting offset: Total size: Size of table: Number of tables: Unused tables: 373856 (0x0005B460) 200000 bytes (5.5%) 400 bytes 500 0 Interface Tables Starting offset: Total size: Size of table: Number of tables: Unused tables: 573024 (0x0008C1A0) 8000 bytes (0.
TTGEN Configuration File System Response Node Information Local node number: Node entries: 123 1 (max.) Node# Timeout Host Names ----- ------- ----------------------------------------------123 0 Storage Labels Number of labels: Appln ----10 99 Label ------X25CNT X25UDT Offset -----308 308 Queue Labels Number of labels: Default Queue Limits Program queue: Transmit queue: Unack queue: Port tx limit: 2 Bytes ----88 24 0 200 messages 100 messages 5000 bytes 20000 bytes Page 3 ttlst: x25.
TTGEN Configuration File System Response Download module: Link time: Req’d Protocol: X25 X25 B3270SE Page 4 ttlst: x25.
TTGEN Configuration File System Response 10 0 0 25 0x37 0x8209 0x4BEA 601 11 62 0x00 0x0000 0x0000 99 700 L2 DTE 10 0 0 0 Loopback term 99 0 0 0 99 INTERFACE CARD 0 PORT 1 Defined Terminals: Port Tx Limit: 10 20000 bytes Port Configuration Port mode: Baud rate: Clock source: Operating mode: Clock Multiplier: Encoding mode: Parity: Term# Area# --------0 0 1 0 RS232 57600 Ext SDLC x1 NRZ Ptype Optn Poll Select TerminalName/CallNumber Ltype ZLU# ----- ---- ------ ------ ---------------------
TTGEN Configuration File System Response Encoding mode: Parity: NRZ Term# Ptype Optn Poll Area# Ltype ZLU# ----- ----- ---- ---------- ----- ---0 25 0x37 0x0209 0 99 602 1 26 0x40 0x0000 0 99 21 2 26 0x40 0x0000 0 99 22 3 26 0x40 0x0000 0 99 23 4 26 0x40 0x0000 0 99 24 5 26 0x40 0x0000 0 99 25 6 26 0x40 0x0000 0 99 26 7 26 0x40 0x0000 0 99 27 8 26 0x40 0x0000 0 99 28 9 26 0x40 0x0000 0 99 29 10 62 0x00 0x0000 0 99 702 Select TerminalName/CallNumber Appl# Inst# Brch# Wkst# ------ -------------------
TTGEN Configuration File System Response --------0 0 1 0 2 0 3 0 4 0 5 0 6 0 7 0 8 0 9 0 10 0 ----- ---- ---------- ---25 0x37 0x8209 99 603 26 0x40 0x0000 99 31 26 0x40 0x0000 99 32 26 0x40 0x0000 99 33 26 0x40 0x0000 99 34 26 0x40 0x0000 99 35 26 0x40 0x0000 99 36 26 0x40 0x0000 99 37 26 0x40 0x0000 99 38 26 0x40 0x0000 99 39 62 0x00 0x0000 99 703 ------ ----------------------- ----- ----- ----- ----- 0x4BEA L2 DTE 10 0 0 0 0x6200 L3 svc 99 0 0 0 0x6200 L3 svc 99 0 0 0 0x6200 L3
TTGEN Configuration File System Response 4 0 26 99 0x40 0x0000 44 0x6200 L3 svc Page 7 ttlst: x25.
TTGEN Configuration File System Response 7 0x40 57 8 26 0x40 0 99 58 9 26 0x40 0 99 59 10 62 0x00 0 99 705 0 26 0x0000 0x6200 L3 svc 99 0 0 0 0x0000 0x6200 L3 svc 99 0 0 0 0x0000 0x6200 L3 svc 99 0 0 0 99 0 0 0 99 0x0000 0x0000 Loopback term INTERFACE CARD 0 PORT 6 Defined Terminals: Port Tx Limit: 11 20000 bytes Port Configuration Port mode: Baud rate: Clock source: Operating mode: Clock Multiplier: Encoding mode: Parity: RS232 57600 Int SDLC x1 NRZ Page 8 ttlst: x25.
TTGEN Configuration File System Response 10 0 99 62 0x00 0x0000 0x0000 oopback term 706 99 0 0 0 INTERFACE CARD 0 PORT 7 Defined Terminals: Port Tx Limit: 11 20000 bytes Port Configuration Port mode: Baud rate: Clock source: Operating mode: Clock Multiplier: Encoding mode: Parity: Term# Area# --------0 0 1 0 2 0 3 0 4 0 5 0 6 0 7 0 8 0 RS232 57600 Ext SDLC x1 NRZ Ptype Optn Poll Ltype ZLU# ----- ---- ---------- ---25 0x37 0x8209 99 607 26 0x40 0x0000 99 71 26 0x40 0x0000 99 72 26 0x40 0x0000 99
TTGEN Configuration File System Response If there are any errors, then the system summary and the terminal table will not be printed nor will a valid object file be created. Ensure that an error-free TTGEN is run before starting the system. If zcom_mem_size is less than the “TOTAL SIZE” reported under the heading “SYSTEM INFORMATION”, you will be unable to startup ZCOM subsystem using this configuration file.
TTGEN Configuration File System Response 222 Appendix A
