HP 9000 Installation And Configuration Manual
Hide thumbs
Also See for 9000:
- Administration manual (386 pages) ,
- User manual (234 pages) ,
- Manual (165 pages)
Related Manuals for HP 9000
Summary of Contents for HP 9000
- Page 1 ACC Installation and Configuration Guide Edition 1 HP 9000 Networking Manufacturing Part Number: Z7345-90001 E0204 © Copyright 2004 Hewlett-Packard Company.
-
Page 3: Legal Notices
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. - Page 4 This software is based in part on the Fourth Berkeley Software Distribution under license from the Regents of the University of California. ©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.
-
Page 5: Publishing History
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. See your HP sales representative for details. First Edition February 2004... -
Page 7: Table Of Contents
Contents 1. ACC Overview Introduction ............16 Advanced Communications Controller . - Page 8 Contents 3. Protocol Configuration Overview ............. . 50 Firmware Related Files .
- Page 9 Contents B. Tuning and Sizing ZCOM_MEM_SIZE ........... . . 80 C.
- Page 10 Contents...
- Page 11 Preface Hewlett-Packard’s Multiprotocol Advanced Communications Controller (ACC) is a wide area networking product for the HP 9000 family of computer systems. This manual explains how to install and configure the ACC product, and provides an introduction to configuring the ACC for use with various protocols.
-
Page 12: About This Manual
About This Manual This manual provides ACC Base Software product installation and configuration information, as well as general information regarding installation of optional protocol modules. Protocol specific installation and configuration details are included in the respective Installation and Configuration Guide for each protocol. Intended Audience The ACC Installation and Configuration Guide is intended for system managers whose responsibilities include the following tasks:... -
Page 13: Manual Organization
Manual Organization This manual contains the following chapters and appendices: Chapter 1 Overview - presents an overview of the ACC Base Software, and the features that are supported. Chapter 2 Software Installation and Verification - describes how to install the ACC Base Software. It describes how to verify that the ACC software and hardware have been installed and are functional, and how to bring up the ACC subsystem. -
Page 14: Related Documentation
ACC X.25 Protocol User’s Guide • ACC X.25/ISDN Data Analyzer User’s Guide • ACC HDLC/LAP-B (ABM) Protocol User’s Guide • HDLC-NRM (SDLC) Protocol User’s Guide • X.25/ACC Installation and Configuration Guide • X.25/ACC Update Guide • X.25/9000 User’s Guide • X.25/9000 Programmer’s Guide... -
Page 15: Acc Overview
ACC Overview Chapter 1... -
Page 16: Introduction
ACC Overview Introduction Introduction This chapter describes the Multiprotocol ACC family of products. It contains the following sections: • Advanced Communications Controller • Product Features • ACC Software • ACC Hardware • Protocol Module Accessories • High Availability Features Chapter 1... -
Page 17: Advanced Communications Controller
The Multiprotocol Advanced Communications Controller (ACC) is a family of high performance, multi-port Multiprotocol wide area network (WAN) adapters for HP 9000 computers. The ACC products support two or eight RS232/V.35/RS449/X.21 connections, or four E1/T1 connections on a single HP-PB, EISA, or PCI network interface board.. -
Page 18: Product Features
ACC Overview Product Features Product Features The ACC Product provides a network interface card for HP9000 systems and workstations: • 8-channel PCI ACC Mux port transmits at speeds up to 2.048 Mbits per second (Mb/s). The ACC Product provides a high-connectivity solution with: •... - Page 19 ACC Overview Product Features Highly flexible solutions may be created using the ACC product: • Multiple protocols are supported. The ACC Protocols for Application Developers product provides all the supported protocol modules. • The ACC supports multiple protocols, combinations of protocols, and data communications speeds simultaneously on different ports of the same ACC multiplexer card.
-
Page 20: Acc Software
ACC Software ACC Software The architecture of the ACC Base Software product allows protocols to be implemented on an HP 9000 computer system, and then downloaded to the ACC interface card. The software provided by the ACC Base Software product includes: •... - Page 21 Program X.25 TCP/IP Other high level X.25 Level3 protocol Prog. Accs. Low level ..ZCOM I/F ZCOM HP-UX Drivers (LDM/DAM) HP 9000 System ACC Mux I/F ZCOM Mux Kernel ZCOM ZCOM ZCOM ZCOM Protocol Protocol...
- Page 22 ZCOM programmatic interface. The ACC Programmer’s Reference Guide describes this interface. Other optional ACC protocol products, such as the ACC X.25/9000 Link Software, include a ZCOM protocol module plus additional driver software, utilities, and programmatic interface related software. These...
-
Page 23: Acc Hardware
The single interface panels are designed to connect to one ACC interface card. The dual interface configurations can connect one panel to two ACC interface cards operating in two HP 9000 systems in a high availability configuration. Mux Interchange Panel Products for 8-Channel PCI ACC Interface Cards •... -
Page 24: Ordering Hardware Components
ACC Overview ACC Hardware Ordering Hardware Components All ACC interface hardware must be ordered separately from the ACC software. Use the following table to determine what ACC software and hardware products are available for your ACC installation. Table 1-1 Ordering Options Hardware Product Options ACC Mulitplexer Z7430A... -
Page 25: Protocol Module Accessories
This is referred to as X.25/ACC, and includes the ACC Base Software module ACC X.25/9000 Link Software, and the HP J2793B X.25/9000 product. It provides industry standard X.25 programmatic interfaces, services, and utilities as they are provided by the HP J2793B X.25/9000 product. HDLC/LAP-B This protocol module provides access to HDLC/LAP-B via the low level ZCOM Programmatic interface. - Page 26 ACC Overview Protocol Module Accessories This product provides the same functionality as the ACC and X.25/9000 Software Bundle, except that the ACC Base Software and HP X.25/9000 software are not included. That is, both products must be ordered separately. Chapter 1...
-
Page 27: High Availability Features
ACC Overview High Availability Features High Availability Features The ACC product provides features that make it uniquely suited for creating highly available systems: • Remote Node access • Daemon monitoring and recovery • Dual Interface Configuration Remote Node Access The Remote Node access feature provided by the ACC Mux Subsystem provides the ability to access remote ACC Mux ports in the same manner as local Mux ports are accessed. -
Page 28: Dual Interface Configuration
ACC Overview High Availability Features Dual Interface Configuration The Dual Interface options for ACC Mux cards provide the ability to connect two Mux cards to the network in a high-availability configuration. Such connections should be used to give one Mux card access (but ONLY one), while the other remains in a hot-standby mode. -
Page 29: Software Installation And Verification
Software Installation and Verification Chapter 2... -
Page 30: Introduction
1. Remove the previous version (if any) of the ACC product and ACC accessory products using swremove. 2. Install the ACC Mux interface card or cards on your HP 9000 computer. (Refer to the appropriate ACC Multiplexer Hardware Installation and Reference Manual.) 3. -
Page 31: Software Removal
Software Installation and Verification Software Removal Software Removal If a previous version of the ACC product or any ACC accessory product is already installed on the target system, you must remove it and rebuild the kernel before installing the new software. CAUTION It is very important to follow the instructions provided with the current version of ACC software installed in the system to shutdown and remove... - Page 32 Software Installation and Verification Software Removal 5. If removal is successful, make sure that swremove rebuilds the kernel and reboots the system. If this does not occur, you should manually rebuild the kernel by entering: # cd /stand # mk_kernel When this succeeds, replace the currently running kernel with the new kernel: # kmupdate...
-
Page 33: Hardware Installation
Software Installation and Verification Hardware Installation Hardware Installation Install the ACC Mux card or cards on your HP 9000 computer according to the instructions in the appropriate ACC Multiplexer Hardware Installation and Reference Manual. We highly recommend that you install the hardware before the ACC software is installed. The ACC installation process creates ttgen configuration files based on the actual locations of installed ACC Mux cards. -
Page 34: Software Installation
You must consult the Release Notes with this product for important CAUTION details, particularly about required HP-UX patches. Install them before proceeding. 1. Log in to the system as “root”. 2. Place the media in a local or remote CD-ROM drive. -
Page 35: Software Identification
(nacc1 for 4-port cards or nacc2 for 8-port PCI cards) has claimed the newly-installed card in the desired slot. Then ACC software start-up can proceed normally. Otherwise contact your HP Support representative. Software Identification After the ACC product has been installed, you may use the what utility to provide version information. -
Page 36: Important Installation And Configuration Notes
If a valid ACC Mux card is found, zmon automatically re-creates the ACC Mux device file for that hardware location. Re-creation of device files is necessary because the HP-UX kernel may assign a different device major number to the ACC subsystem during system bootup. -
Page 37: Kernel Configuration
Software Installation and Verification Important Installation and Configuration Notes Kernel Configuration If the error message ENOSPC is encountered during download of the ZCOM Subsystem, it may be due to an insufficient value in configurable parameter semmnu. To increase the value of this parameter: 1. -
Page 38: Installation Verification
Software Installation and Verification Installation Verification Installation Verification The loopback test can be used to verify that the ACC hardware and software have been properly installed, and are functional. This test assumes that at least one ACC multiplexer card will be used. If NOTE no multiplexer cards will be used on the system, refer to the section “Systems Without Mux Cards”... -
Page 39: Loopback Configuration Requirements
Software Installation and Verification Installation Verification Loopback Configuration Requirements The ACC product provides a loopback protocol module (PORTTEST) which is included in the download file. This can be used to run a loopback test which exercises the ACC multiplexer card, any attached multiplexer interchange panel or cable, and the specified multiplexer port. -
Page 40: Cabling And Clock Source Requirements
Software Installation and Verification Installation Verification Cabling and Clock Source Requirements When testing a single port looped back on itself, you connect a terminated connector or loopback hood to one of the ports on the multiplexer panel. This serves to connect the Receive Clock (RC) to the External Timing Clock (ETC), or CCITT circuit 115 to CCITT circuit 113. - Page 41 Software Installation and Verification Installation Verification If you intend to test a single port looped back on itself, it is convenient to choose one of the predefined even-numbered ports, since the configuration file provides the required clock mode. Alternatively, edit the loopback.answ configuration file to reflect your needs.
-
Page 42: Bringing Up Zcom Mux Subsystem
Software Installation and Verification Installation Verification Bringing Up ZCOM Mux Subsystem Before any of the features of the ZCOM Mux Subsystem can be accessed, it must be started up by running zmasterd (located in /opt/acc/bin) with an appropriate .tmem file. The /opt/acc/cfg/loopback.tmem file should be used, followed by performing the loopback verification test: # zmasterd cold /opt/acc/cfg/loopback.tmem Messages indicating whether or not the ZCOM Mux subsystem was... - Page 43 Software Installation and Verification Installation Verification Zmasterd starts the daemons that are listed with “start” statements in the /opt/acc/cfg/zmasterd_list file. For the base ACC product, zmasterd starts the zmlog logging facility, zmon, and znode. If any error is reported during the start up procedure, it may be necessary to stop the ZCOM subsystem by running: # /opt/acc/bin/zmasterd stop The error should be addressed, and then the ZCOM subsystem should be...
-
Page 44: Performing The Loopback Test
RS-232 or V.35 test on 8-Channel interfaces). This will verify the following: • The ACC Mux card has been properly installed, and has been recognized by the HP-UX system. • The ACC driver software has been configured into the system properly. - Page 45 Software Installation and Verification Installation Verification In the second example, both internal and external tests are performed by using the ie test option. In this example, the loopback hood is not connected to the port being tested, and therefore the external tests fail. Example 2 ZMNTR>...
-
Page 46: Systems Without Mux Cards
Software Installation and Verification Systems Without Mux Cards Systems Without Mux Cards The ACC Subsystem can be used with no cards installed on the local system. Application programs can be run on this system and make requests to control ACC Mux cards that reside on remote systems accessible via LAN. -
Page 47: Performing Verification Test
Software Installation and Verification Systems Without Mux Cards ------------------------------------------------------------------ Tue Jun 20 18:14:35 1998: zmlog: message logging resumed ------------------------------------------------------------------ 18:14:34 zmast 00101 Launched daemon zmlog, pid 2709. 18:14:34 zmast 00117 Zmasterd daemon start running... 18:14:34 zmast 00101 Launched daemon zmon, pid 2711. 18:14:35 zmon 00002 Resource manager (Rev 1.32) for ZCOM 6.2.0.0... - Page 48 Software Installation and Verification Systems Without Mux Cards Chapter 2...
-
Page 49: Protocol Configuration
Protocol Configuration Chapter 3... -
Page 50: Overview
Protocol Configuration Overview Overview The ACC product provides the base ZCOM firmware. Relevant protocol modules are included with the ACC bundled products or link products. A full set of available protocol modules are bundled in the ACC Protocols for Application Developers product. Each ACC protocol module includes a manual that describes the use of that protocol, protocol specific configuration details, and how to install the protocol module. -
Page 51: Firmware Related Files
Protocol Configuration Firmware Related Files Firmware Related Files The ACC product provides the following firmware related files: Figure 3-1 Firmware Related Files /opt/acc/ /var/opt/acc/ cfg/ protocol/ msg/ sys/ <card-type>/ log/ dmp/ *.zrel ttgendefine *.zrel *.txt *.zsnp zcomdevice.txt *.hlp zcomdevice *.msg sample_header loopback.answ loopback.tmem... -
Page 52: Ttgendefine
Protocol Configuration Firmware Related Files ttgendefine The ttgen configuration files include this file by putting the following statement at the top of the file: #include ”/opt/acc/cfg/ttgendefine” This file contains symbolic definitions for a variety of configuration parameters that may be used in the ttgen configuration file. zcomdevice.txt and zcomdevice The device definition file zcomdevice.txt is an ASCII editable file containing default protocol configuration information. -
Page 53: Loopback.tmem
Protocol Configuration Firmware Related Files loopback.tmem This file is produced when the ttgen utility is run on the loopback.answ file. This file is automatically created during the ACC installation process. The loopback .tmem file must be recreated whenever the loopback.answ file is changed. The file can be created/recreated by running: % ttgen -o /opt/acc/cfg/loopback.answ /opt/acc/cfg/loopback.tmem Refer to the “TTGEN - ZCOM System Table Generator”... -
Page 54: Files In /Opt/Acc/Sys
Protocol Configuration Firmware Related Files If an application program also makes use of the zmlog utility for logging its messages, its text file should also be placed in this directory. Files in /opt/acc/sys This directory contains all relocatable (zrel) files related to the ACC mux kernel software for the various ACC interface cards. - Page 55 This prevents card memory dumps from being uploaded should the card hardware/firmware fail. You should create this directory if you wish to have Mux memory dumps saved for HP analysis. The dump files could be over 15 Mbytes in size, depending on the type of ACC card.
-
Page 56: Creating A Ttgen Configuration File
Protocol Configuration Creating a ttgen Configuration File Creating a ttgen Configuration File The ttgen configuration file configures how the ACC MUX cards will be used. The ACC protocol accessory products may provide a template configuration file. If none is provided, /opt/acc/cfg/loopback.answ (a file which is created when the ACC product is installed) can be used. -
Page 57: Dual Interface Configurations
Dual Interface Configurations Chapter 4... -
Page 58: Introduction
ACC cards to be connected to a single network port. The interconnect panel is typical used to connect two ACC cards installed in two separate HP 9000 systems, but the panel can also connect two cards in the same system. (This may be useful for prototyping and test situations.) -
Page 59: Affecting Port Mode
Dual Interface Configurations Affecting Port Mode Affecting Port Mode The port mode can be affected in the following ways: • It is affected by the port configuration in the ttgen configuration .answ file that corresponds to the .tmem file used to bring up the ACC MUX subsystem. - Page 60 Dual Interface Configurations Affecting Port Mode All ZLUs on a given port must be disabled before the port mode can be NOTE changed. If the port is being taken out of Loopback mode, the ZLUs on that port can now be brought up in the manner that is appropriate to the protocol being used.
-
Page 61: Application Interface
Dual Interface Configurations Affecting Port Mode % zterm 11:04:47 ZCOM Interactive command utility 11:04:47 Primary ZLU is 802 ZTERM> cn,1,200,di ZTERM> pt,5,6,2,3,0,0 ZTERM> cn,1,200,en ZTERM> cn,1,200,ac ZTERM> exit The first command to ZTERM issues a control request to disable the ZLUS on the port. -
Page 62: Watch Feature
Dual Interface Configurations Affecting Port Mode All ZLUs on a given port must be disabled before the port mode can be NOTE changed. watch Feature The watch feature provides a heartbeat mechanism between the ACC MUX card and the host system in which it is installed. Any card which has the MONITOR protocol configured will place all of its ports into loopback mode when a heartbeat is no longer being received from the host system. -
Page 63: Default Port Modes
Dual Interface Configurations Default Port Modes Default Port Modes The following list shows the mode of the ports. • All ports on all ACC cards are in Loopback (Tri-state) mode when the system in which the cards are installed is powered down. •... -
Page 64: Checking Port Modes
Dual Interface Configurations Checking Port Modes Checking Port Modes Use the mx command of the zmntr utility to view the current mode of the ports on a given MUX. For example, to view the ports on MUX 1 of an 8 channel ACC card: HPAMS1R>... - Page 65 Dual Interface Configurations Checking Port Modes This example shows that the mode of all ports on this ACC card is “Tri-state” which is the same as Loopback. The following example shows ACC card 0 having all ports in RS-232 mode: ZMNTR>...
- Page 66 Dual Interface Configurations Checking Port Modes Chapter 4...
-
Page 67: Files, Utilities, And Daemons
Files, Utilities, and Daemons This appendix provides a list of the device files, log files, and configuration files that are used by the ACC Base Software product. It also lists related daemon and utility programs. Appendix A... -
Page 68: Device Files
Files, Utilities, and Daemons Device Files Device Files The device files that are used by the ACC product are automatically created as they are needed. If a daemon requires a device file that does not exist, the daemon will create it. If an application program that makes use of the ZCOM programmatic interface requires a device file that does not exist, the ZCOM Interface library call that requires the device file will create it.The following list shows the device files that are used by the... - Page 69 Files, Utilities, and Daemons Device Files A device file is required for each ACC MUX card that will be accessed on the system. The naming convention of the device file depends on the type of system being used. For systems that have no extended bus converter addressing, the naming convention for the device files is/dev/zmuxbYYsZZ.
- Page 70 -f | grep ACC Some typical examples are as shown below. Example #1 The following ioscan -f output denotes a standard HP-PB system with no bus converter and the 8-channel ACC card has a card address of 4: Class H/W Path...
- Page 71 Files, Utilities, and Daemons Device Files Example #3 The following ioscan -f output denotes a standard HP-PB system with bus converters where the 8-channel ACC card has a bus converter address of 10/16 and a card address of 8: Class...
-
Page 72: Daemons
Files, Utilities, and Daemons Daemons Daemons The following daemons are provided by the ACC product. These daemons are documented in theACC Utilities Reference Guide. zmlog This daemon displays the log messages that are reported via the drivers and daemons provided with the ACC product family. -
Page 73: Utilities
Files, Utilities, and Daemons Utilities Utilities The following utilities are provided by the ACC product. These programs are also documented in the ACC Utilities Reference Guide. ttgen This utility must be run on the .answ ttgen configuration files in order to produce the .tmem files. The .tmem files are used by zmon to bring up the ZCOM MUX Subsystem. -
Page 74: Log Files
Files, Utilities, and Daemons Log Files Log Files The following log files may contain messages regarding the installation and/or use of the ACC product: /var/opt/acc/log/*.tlog These ASCII text log files are created by the /etc/zmlog daemon. One file is created per day: mon.tlog, tue.tlog, wed.tlog, etc. -
Page 75: Configuration Scripts
Files, Utilities, and Daemons Configuration Scripts Configuration Scripts acc_bld_lpbk This script is used to produce a sample loopback ttgen configuration file. It is run automatically when the ACC product is installed. If additional ACC MUX cards are installed into the system, or if ACC MUX cards are moved within the system, this script can be useful for recreating a loopback configuration file. -
Page 76: Sample Ttgen Configuration File
Files, Utilities, and Daemons Sample ttgen Configuration File Sample ttgen Configuration File The /opt/acc/cfg/loopback.answ file is a sample ttgen configuration file. The sample file is automatically created when the ACC product is installed. The MUX-Definition statements in this file are created to match the hardware that is installed on the system at the time the file is created. - Page 77 Files, Utilities, and Daemons Sample ttgen Configuration File 0:12 /opt/acc/z7200a/loopback.zabs 0:16 /opt/acc/z7350a/loopback.zabs Port-Definition Port 0:0 RS232 57600 Int SDLC x1 NRZ Port 0:1 RS232 57600 Ext SDLC x1 NRZ Port 0:2 RS232 57600 Int SDLC x1 NRZ Port 0:3 RS232 57600 Ext SDLC x1 NRZ Port 0:4 RS232...
- Page 78 Files, Utilities, and Daemons Sample ttgen Configuration File The /opt/acc/cfg/loopback.answ file will be created whether or not there are ACC interface cards on the system at the time acc_bld_lpbk is run. In the case that there are no ACC interface cards installed, the loopback.answ file will be similar to the one shown, except that there will be no Mux, Port, or Term statements.
-
Page 79: Tuning And Sizing
Tuning and Sizing This appendix describes parameters related to the ACC Base Software product that may be modified to reflect system requirements. Appendix B... -
Page 80: Zcom_Mem_Size
Tuning and Sizing ZCOM_MEM_SIZE ZCOM_MEM_SIZE The ACC Mux Subsystem reserves a contiguous block of kernel memory for tables for its use. This block of memory is used for table space and for data buffering internal to the ACC Mux Subsystem product. The maximum size of the memory block is set by the value of the zcom_mem_size parameter in the “system”... - Page 81 Tuning and Sizing ZCOM_MEM_SIZE An appropriate value for zcom_mem_size can be estimated using the following algorithm: zcom_mem_size = <card> * <rate> * <time> * (<length> + 200) * 1.5 where: <card> number of mux cards on the system <rate> maximum number of messages per second per mux card (Refer to the calculation shown below.) <time>...
- Page 82 Tuning and Sizing ZCOM_MEM_SIZE Appendix B...
-
Page 83: Acc Service Guard Configuration Notes
ACC Service Guard Configuration Notes This appendix provides an example of using zconfig() in the Loopback mode in a Service Guard clustered environment. Appendix C... -
Page 84: Overview
There are 2 cases that need to be considered. • In the first case, the primary system has an unexpected, catastrophic failure or HP-UX panic. • In the second case, the primary system is shutdown (gracefully). The SG cluster configuration is controlled by a script, run on each system when the system joins the cluster. -
Page 85: Examples
ACC Service Guard Configuration Notes Overview 3. In the start up, /etc/rc.config.d/acc file, make sure that the start flag is 0 (START_ZCOM=0). This allows the Service Guard script to control when to start/stop ACC, so that ACC will not restart automatically following a panic, or powerout event and interfere with the other system. - Page 86 # a 5 sec sleep is recommended here (SR # 5000-716977) sleep 5 /opt/acc/bin/zmasterd kill ******************* Example /opt/acc/cfg/zmasterd_list ************** # HP Z7250A- /opt/acc/cfg/zmaster_list file # Start these daemons when zmasterd is started, and monitor them: # Start zmlog with -nd option for no console logging. start zmlog -nd start zmon cold /opt/acc/cfg/sna_acc_sdlc.tmem...
- Page 87 ACC Service Guard Configuration Notes Overview pt,0,3,2,3,0000H,8000H pt,0,4,2,3,0000H,8000H pt,0,5,2,3,0000H,8000H pt,0,6,2,3,0000H,8000H pt,0,7,2,3,0000H,8000H ** example network configuration sna_acc_sdlc.answ (sna_acc_sdlc.tmem) ** Network configuration (ttgen input) file sna_acc_sdlc.answ example for Service Guard #include "/opt/acc/cfg/ttgendefine" ttgen Configuration system-name "SNA/ACC Interface sample ttgen input file for SDLC" program-zlu terminal-zlu 1000...
- Page 88 ACC Service Guard Configuration Notes Overview Term 0005 0:4 HDLC.FRAME 0000h 0000h 41 0 0 0 0 "SNAPLUS" Term 0006 0:5 HDLC.FRAME 0000h 0000h 41 0 0 0 0 "SNAPLUS" Term 0007 0:6 HDLC.FRAME 0000h 0000h 41 0 0 0 0 "SNAPLUS" Term 0008 0:7 HDLC.FRAME 0000h 0000h 41 0 0 0 0 "SNAPLUS"...