ACC Installation and Configuration Guide Edition 1 HP 9000 Networking Manufacturing Part Number: Z7345-90001 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.
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. ©copyright 1986 Digital Equipment Corporation. ©copyright 1990 Motorola, Inc.
Publishing 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.
Contents 1. ACC Overview Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Advanced Communications Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Product Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ACC Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents 3. Protocol Configuration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Firmware Related Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Files in /opt/acc/cfg . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ttgendefine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents B. Tuning and Sizing ZCOM_MEM_SIZE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 C. ACC Service Guard Configuration Notes Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents 10
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. It contains information for both first-time ACC software installation and ACC software updates.
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.
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.
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 • • • • • • • • • • • • • 14 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.
1 Chapter 1 ACC Overview 15
ACC Overview Introduction Introduction This chapter describes the Multiprotocol ACC family of products.
ACC Overview Advanced Communications Controller 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.. HP’s ACC supports one or multiple protocols on a single card. Supported protocols include: • X.
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).
ACC Overview Product Features Highly flexible solutions may be created using the ACC product: Chapter 1 • 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. • Custom protocols may also be developed.
ACC Overview 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: • HP-UX Drivers for the ACC Interface card (see Figure 1-1, Multiprotocol ACC,). • ZCOM Mux Kernel (operating system) which is downloaded to the ACC Mux card (see Figure 1-1, Multiprotocol ACC,).
ACC Overview ACC Software Figure 1-1 Multiprotocol ACC Application or Utility Program Application or Utility Program X.25 TCP/IP Other high level protocol X.25 Level3 Prog. Accs. . . . . . . Application or Utility Program . . . . . . Low level ZCOM I/F ZCOM HP-UX Drivers (LDM/DAM) HP 9000 System ACC Mux I/F ZCOM Mux Kernel ZCOM Protocol Module ZCOM Protocol Module ZCOM Protocol Module . . . . . . ZCOM Protocol Module (X.
ACC Overview ACC Software The ACC Base Software product supplies the protocol modules that can be used to verify that the product and the mux panel are installed and functional, and that can be used to sense failures between the mux card and the host system. These include a loopback, “NULL”, and monitoring protocol module. Other protocol modules are available by ordering the ACC Protocols for Application Developers product. These protocols may be accessed via the low level ZCOM programmatic interface.
ACC Overview ACC Hardware ACC Hardware The ACC Base Software product requires one of the ACC Multiplexer Interface cards listed in the current HP Configuration and Ordering Guide. For this release, the interface cards include: • 8-Channel PCI The 8 channel ACC interface cards are compatible with several different interchange panels, allowing connections to a variety of physical interfaces. The single interface panels are designed to connect to one ACC interface card.
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 24 Ordering Options Hardware Product Options ACC Mulitplexer Ordering Option Z7430A 8 Ch PCI RS-232 panel, cable, and test kit Z7321A V.35 panel, cable, and test kit Z7322A RS-449 panel, cable, and test kit Z7323A X.
ACC Overview Protocol Module Accessories Protocol Module Accessories Protocol modules are ordered as separate products to the ACC Base Software product. Protocol module accessories include: X.25 Packet This protocol module provides X.25 protocol support, which may be accessed via the low level ZCOM Programmatic interface. This module is included in the ACC Protocols for Application Developers product. ACC and X.25/9000 Software Bundle This is referred to as X.
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.
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.
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. In the case that the “live” Mux card fails, the other card can be activated with little or no interruption of service.
2 Chapter 2 Software Installation and Verification 29
Software Installation and Verification Introduction Introduction This chapter describes how to install the ACC software using the swinstall utility. It also describes how to verify that the product has been successfully installed and is functional.
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 that software. This procedure may change between major releases of the ACC product. 1.
Software Installation and Verification Software Removal 5. If removal is successful, make sure that swremove rebuilds the kernel and reboots the system.
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.
Software Installation and Verification Software Installation Software Installation Read the ACC software from the installation media, in superuser mode, using the swinstall utility. CAUTION You must consult the Release Notes with this product for important 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. 3.
Software Installation and Verification Software Identification NOTE Before starting the ACC Base software installed on a Multiplexer interface, you MUST run ioscan -f to verify that the driver nacc0 (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 Installation and Verification Important Installation and Configuration Notes Important Installation and Configuration Notes Adding or Moving Hardware After Installation The process of running swinstall to install the ACC product creates the loopback configuration file /opt/acc/cfg/loopback.answ, based on the location of the ACC card(s). Adding or moving ACC cards after software installation will affect the correctness of ttgen configuration files.
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. Run SAM (logged in as superuser) and select the “Kernel Configuration” menu. 2.
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. NOTE 38 This test assumes that at least one ACC multiplexer card will be used. If no multiplexer cards will be used on the system, refer to the section “Systems Without Mux Cards” on page 46.
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. The loopback test is run using the loopback test feature (the lb command of the zmntr utility. (See the ACC Utilities Reference Guide.
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. Refer to the hardware reference manual for more details.
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. The .answ file is generated with entries for an RS-232 panel, if you are using a different panel type (e.g. RS-449, X.21, V.35), you must edit the loopback.
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.
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 restarted.
Software Installation and Verification Installation Verification Performing the Loopback Test The loopback test is run by using the lb command of zmntr utility program. You should run both the internal and external loopback tests (as well as either the RS-232 or V.35 test on 8-Channel interfaces). This will verify the following: NOTE • 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.
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> lb 1 0 ie 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 ..
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. This is done by using the Remote Node Access feature introduced in the section “High Availability Features” on page 27 of Chapter 1, and is further explained in the ACC Utilities Reference Guide.
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.
Software Installation and Verification Systems Without Mux Cards 48 Chapter 2
3 Chapter 3 Protocol Configuration 49
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.
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/ cfg/ protocol/ ttgendefine *.zrel zcomdevice.txt zcomdevice sample_header loopback.answ loopback.tmem zmasterd_list msg/ *.txt *.hlp *.msg /var/opt/acc/ sys/ / log/ *.zrel *.zsnp loopback.zabs loopback.zlnk loopback.
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.
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.
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. These files must be in this directory, and they should not be altered.
Protocol Configuration Firmware Related Files When the zmlog logging daemon is run, it creates text log files in this directory. This information is usually also logged to the system console, depending on how zmlog is run. Refer to the ACC Error Guide, for information on interpreting the log messages. Refer to the “ZMLOG - Diagnostic Message Logging” chapter of the ACC Utilities Reference Guide for more information on zmlog. The /var/opt/acc/dmp/ directory is used to store Mux interface card memory dumps.
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. (Note that this file is shown in Appendix A, “Files, Utilities, and Daemons,” on page 67.
4 Chapter 4 Dual Interface Configurations 57
Dual Interface Configurations Introduction Introduction The dual MUX interconnect panels or cables are designed to allow two 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.
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. • It can be affected interactively via the zterm utility. • It can be affected by an application program that calls the zconfig() or zport() ZCOM subroutines.
Dual Interface Configurations Affecting Port Mode NOTE All ZLUs on a given port must be disabled before the port mode can be 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. For example, if the X.25 protocol is being used, the ZLU corresponding to the Level 2 X.25 connection could now be brought up. Refer to the ACC Utilities Reference Guide for details on using the zterm utility.
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. The next request is the ZPORT command. This time, the upper two bits of the second configuration word must be cleared to indicate RS-232 mode.
Dual Interface Configurations Affecting Port Mode NOTE All ZLUs on a given port must be disabled before the port mode can be 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. This would occur, for example, if the system were to panic.
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. • All ports on all cards are in Loopback mode when the system is powered up, but the zmon utility has not yet been run in order to bring up the ZCOM subsystem. • The ports may be in Loopback, RS-232, X.21, etc.
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> zmntr ZMNTR: ZCOM 6.2.0.0 Runtime Monitor, Rev 1.0 ZMNTR> mx,1 Interface card information for ACC X.25 ttgen input file TTGEN source /usr/zcom/opt/acc/cfg/duplex.answ object /usr/zcom/opt/acc/cfg/duplex.
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> mx,0 Interface card information for ACC X.25 ttgen input file TTGEN source /usr/zcom/opt/acc/cfg/duplex.answ object /usr/zcom/opt/acc/cfg/duplex.tmem Mux:00 Bus:00/01 Slot:02 Trms:0004 Card Stat:Up and active Hardware Revison: Rev.
Dual Interface Configurations Checking Port Modes 66 Chapter 4
A 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.
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 ACC product.
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. The YY and ZZ represent the values that make up the hardware path to the card. The YY represents the bus converter address and the ZZ represents the card address.
Files, Utilities, and Daemons Device Files The hardware path for the ACC card can be found by entering: ioscan -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 I H/W Path Driver S/W State H/W Type Descr.
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 I H/W Path Driver S/W State H/W Type Descr. nacc 0 10/16/8 CLAIMED ACC MUX nacc0 INTERFACE The corresponding mux statement in the ttgen configuration file should be: Mux 0 10:16:8 /opt/acc/z7200a/sample.zabs.
Files, Utilities, and Daemons Daemons Daemons The following daemons are provided by the ACC product. These daemons are documented in theACC Utilities Reference Guide. 72 zmlog This daemon displays the log messages that are reported via the drivers and daemons provided with the ACC product family. zmon This daemon is responsible for initializing and managing the ZCOM Subsystem. znode This daemon is required in order to use the Remote Node access feature.
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. Appendix A 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. zlink This utility is used to create custom downloadable firmware files from .zrel relocatable protocol 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. Information logged in these files includes information that relates to the ACC product being brought up, or being shutdown.
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. (Refer to the following section, “Sample ttgen Configuration File” and examples.
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.
Files, Utilities, and Daemons Sample ttgen Configuration File Mux Mux 0 1 0:12 0:16 Port-Definition Port 0:0 RS232 Port 0:1 RS232 Port 0:2 RS232 Port 0:3 RS232 Port 0:4 RS232 Port 0:5 RS232 Port 0:6 RS232 Port 0:7 RS232 Port 1:0 Port 1:1 RS232 RS232 57600 57600 57600 57600 57600 57600 57600 57600 /opt/acc/z7200a/loopback.zabs /opt/acc/z7350a/loopback.
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. The /opt/acc/cfg/loopback.tmem will also still be created, and can be used to bring up the ACC MUX Subsystem.
B Tuning and Sizing This appendix describes parameters related to the ACC Base Software product that may be modified to reflect system requirements.
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” file used to build your kernel. Typically, this is the file /stand/system. The default value is 4 M-Byte.
Tuning and Sizing ZCOM_MEM_SIZE An appropriate value for zcom_mem_size can be estimated using the following algorithm: zcom_mem_size = * *
Tuning and Sizing ZCOM_MEM_SIZE 82 Appendix B
C ACC Service Guard Configuration Notes This appendix provides an example of using zconfig() in the Loopback mode in a Service Guard clustered environment.
ACC Service Guard Configuration Notes Overview Overview In the examples, there are two systems that each have one or more ACC cards, using the dual connect ACC distribution panel accessories. One system is a primary, and one is a secondary. The primary system has the ACC links in active use, and the secondary either does not start the ACC subsystem, or has each link (pmode) in the loopback mode. There are 2 cases that need to be considered.
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. 4. Edit the Service Guard cluster control script to start and configure the ACC cards when the script is entered as start.
ACC Service Guard Configuration Notes Overview # disable the ports to "lback" # See example "setLBACK.zterm" script below. /opt/acc/bin/zterm /opt/acc/cfg/setLBACK.
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 ex ** example network configuration sna_acc_sdlc.answ (sna_acc_sdlc.tmem) ** * * Network configuration (ttgen input) file sna_acc_sdlc.
ACC Service Guard Configuration Notes Overview Term Term Term Term 0005 0006 0007 0008 Term Term Term Term Term Term Term Term Term 600 601 602 603 604 605 606 607 608 0:4 0:5 0:6 0:7 0:0 0:1 0:2 0:3 0:4 0:5 0:6 0:7 0:0 HDLC.FRAME HDLC.FRAME HDLC.FRAME HDLC.
