Jump to content United States-English
HP.com Home Products and Services Support and Drivers Solutions How to Buy
» Contact HP
More options
HP.com home
X.25/ACC Installation and Configuration Guide > Appendix C Utilities, Servers, and Scripts

Configuration Scripts

» 

Technical documentation

Complete book in PDF
» Feedback
Content starts here

 » Table of Contents

 » Index

/opt/acc/lbin/acc_bld_lpbk

This script is used to produce a sample loopback ttgen configuration file, for example the x25_loop.answ file mentioned in Chapter 2. It is run automatically when the ACC and X.25/ACC products are 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 section “Sample X.25/ACC ttgen Configuration File” on “Sample X.25/ACC ttgen Configuration File” for an example.)

The script is run as follows:

% /opt/acc/lbin/acc_bld_lpbk -o <output file> \
-t <ttgen file header> [-p <protocol>]

The output file parameter indicates where the .answ file that is being built will be written. This file name should have a .answ suffix, and it is suggested that its path be /opt/acc/cfg/.

The ttgen file header parameter refers to a file that contains the TTGEN file configuration fields that occur before the Interface-Definition statement. The file /opt/acc/cfg/sample_header is provided for this purpose. The script uses this as the header of the .answ file being created.

The script creates Mux statements for each ACC Mux card that is currently installed in the system. It uses the protocol parameter if it is provided, or it uses loopback if the protocol parameter is not specified.

The script then creates port definition statements for each port for each mux that is installed. It defines the ports differently for 4-Channel interface cards, as shown in the examples that follow. Even numbered ports are defined as internally clocked, and odd ports are externally clocked.

PORTTEST term entries are created for each port. This allows the zmntr loopback test to be run on each port.

A MONITOR term entry is created for each mux so that it can be used with the watch feature.

Sample X.25/ACC ttgen Configuration File

The /opt/acc/cfg/x25_loop.answ file is a sample ttgen configuration file. The sample file is automatically created when the X.25/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. In the case that the ACC Mux cards are moved within the system after the product is installed, it may be necessary to either manually modify the x25_loop.answ file, or to recreate the file to reflect the new hardware location.

The sample ttgen configuration file used by the X.25/ACC product file may be recreated by running:

% cd /opt/acc/cfg
% /opt/acc/lbin/acc_bld_lpbk -o x25_loop.answ -t sample_header -p x25

Once the configuration file is created or modified, the ttgen utility must be run to create a downloadable file:

%  cd /opt/acc/cfg
% /opt/acc/bin/ttgen -os x25_loop.answ x25_loop.tmem > x25_loop.tlist
ttgen: END$ 0 Disasters, 0 Errors, 0 Warnings

The following is an example of a file created by the acc_bld_lpbk script on a system that has one 4-Channel NIO ACC Multiplexer card installed.

NOTE: The Port-Definition parameters must match the T1/E1 line mode configured on the 4-port Z7300A card. Refer to 4-Channel T1/E1 ACC Multiplexer Hardware Installation Guide, the “Pre-Installation Set-Up” section in Chapter 2, for details pertaining to selection of plug-in resistor modules.
* ACC Loopback test TTGEN input file

#include "/opt/acc/cfg/ttgendefine"
ttgen
Configuration
system-name "ACC X.25 protocol ttgen input file"
program-zlu 100
terminal-zlu 1000
logical-term 800
physical-term 800
buffer-pool 3000000
logical-size 256
logical-data 10.X25CNT,0,x25CNT_LDSIZE
queue-limit 9999
transmit-limit 100
unack-limit 5000
port-limit 20000
E1T1-Port_Limit 100000
node-entry 1
 Interface-Definition
z7300a 0 10:16:16 /opt/acc/z7300a/lapd.zabs

Port-Definition
Port 0:0 E1RJ45 Int CRCMF HDB3
Port 0:1 E1RJ45 Ext CRCMF HDB3
Port 0:2 E1RJ45 Int CRCMF HDB3
Port 0:3 E1RJ45 Ext CRCMF HDB3

Subchannel-Definition
* Mux 0, port 0,subchan 01, timeslot 1
Subch 0:0:01 HDLC INV=off ITBS=2 ts:01:FFh

* Mux 0, port 0,subchan 02, timeslot 2 to 7
Subch 0:0:02 HDLC INV=off ITBS=12 ~
ts:02:FFh ts:03:FFh ts:04:FFh ts:05:FFh ts:06:FFh ts:07:FFh

* Mux 0, port 0,subchan 03, timeslot 8 to 31
Subch 0:0:03 HDLC INV=off ITBS=48 ~
ts:08:FFh ts:09:FFh ts:10:FFh ts:11:FFh ts:12:FFh ts:13:FFh ~
ts:14:FFh ts:15:FFh ts:16:FFh ts:17:FFh ts:18:FFh ts:19:FFh ~
ts:20:FFh ts:21:FFh ts:22:FFh ts:23:FFh ts:24:FFh ts:25:FFh ~
ts:26:FFh ts:27:FFh ts:28:FFh ts:29:FFh ts:30:FFh ts:31:FFh

* Mux 0, port 1,subchan 01, timeslot 1
Subch 0:1:01 HDLC INV=off ITBS=2 ts:01:FFh

* Mux 0, port 1,subchan 02, timeslot 2 to 7
Subch 0:1:02 HDLC INV=off ITBS=12 ~
ts:02:FFh ts:03:FFh ts:04:FFh ts:05:FFh ts:06:FFh ts:07:FFh

* Mux 0, port 1,subchan 03, timeslot 8 to 31
Subch 0:1:03 HDLC INV=off ITBS=48 ~
ts:08:FFh ts:09:FFh ts:10:FFh ts:11:FFh ts:12:FFh ts:13:FFh ~
ts:14:FFh ts:15:FFh ts:16:FFh ts:17:FFh ts:18:FFh ts:19:FFh ~
ts:20:FFh ts:21:FFh ts:22:FFh ts:23:FFh ts:24:FFh ts:25:FFh ~
ts:26:FFh ts:27:FFh ts:28:FFh ts:29:FFh ts:30:FFh ts:31:FFh
* Mux 0, port 2,subchan 01, timeslot 1
Subch 0:2:01 HDLC INV=off ITBS=2 ts:01:FFh


* Mux 0, port 2,subchan 02, timeslot 2 to 7
Subch 0:2:02 HDLC INV=off ITBS=12 ~
ts:02:FFh ts:03:FFh ts:04:FFh ts:05:FFh ts:06:FFh ts:07:FFh

* Mux 0, port 2,subchan 03, timeslot 8 to 31
Subch 0:2:03 HDLC INV=off ITBS=48 ~
ts:08:FFh ts:09:FFh ts:10:FFh ts:11:FFh ts:12:FFh ts:13:FFh ~
ts:14:FFh ts:15:FFh ts:16:FFh ts:17:FFh ts:18:FFh ts:19:FFh ~
ts:20:FFh ts:21:FFh ts:22:FFh ts:23:FFh ts:24:FFh ts:25:FFh ~
ts:26:FFh ts:27:FFh ts:28:FFh ts:29:FFh ts:30:FFh ts:31:FFh

* Mux 0, port 3,subchan 01, timeslot 1
Subch 0:3:01 HDLC INV=off ITBS=2 ts:01:FFh

* Mux 0, port 3,subchan 02, timeslot 2 to 7
Subch 0:3:02 HDLC INV=off ITBS=12 ~
ts:02:FFh ts:03:FFh ts:04:FFh ts:05:FFh ts:06:FFh ts:07:FFh

* Mux 0, port 3,subchan 03, timeslot 8 to 31
Subch 0:3:03 HDLC INV=off ITBS=48 ~
ts:08:FFh ts:09:FFh ts:10:FFh ts:11:FFh ts:12:FFh ts:13:FFh ~
ts:14:FFh ts:15:FFh ts:16:FFh ts:17:FFh ts:18:FFh ts:19:FFh ~
ts:20:FFh ts:21:FFh ts:22:FFh ts:23:FFh ts:24:FFh ts:25:FFh ~
ts:26:FFh ts:27:FFh ts:28:FFh ts:29:FFh ts:30:FFh ts:31:FFh


Terminal-Definition


Node-Definition
Local-Node 123

End$

This second example shows a file created by the acc_bld_lpbk script on a system that has one 8-Channel HP-PB ACC Multiplexer card installed.

* ACC Loopback test TTGEN input file

#include "/opt/acc/cfg/ttgendefine"
ttgen
Configuration
system-name "ACC Loopback test TTGEN File"
program-zlu 100
terminal-zlu 800
logical-term 400
physical-term 400
buffer-pool 3000000
logical-size 256
logical-data 10 X25CNT,0,X25CNT_LDSIZE
queue-limit 9999
transmit-limit 100
unack-limit 5000
port-limit 20000
node-entry 1

Interface-Definition
z7200a 0 0:4 /opt/acc/z7200a/x25.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 57600 Int SDLC x1 NRZ
Port 0:5 RS232 57600 Ext SDLC x1 NRZ
Port 0:6 RS232 57600 Int SDLC x1 NRZ
Port 0:7 RS232 57600 Ext SDLC x1 NRZ

Terminal-Definition
Term 0600 0:0 PORTTEST 0000h 0000h 99 0 0 0 0 "Loopback term"
Term 0601 0:1 PORTTEST 0000h 0000h 99 0 0 0 0 "Loopback term"
Term 0602 0:2 PORTTEST 0000h 0000h 99 0 0 0 0 "Loopback term"
Term 0603 0:3 PORTTEST 0000h 0000h 99 0 0 0 0 "Loopback term"
Term 0604 0:4 PORTTEST 0000h 0000h 99 0 0 0 0 "Loopback term"
Term 0605 0:5 PORTTEST 0000h 0000h 99 0 0 0 0 "Loopback term"
Term 0606 0:6 PORTTEST 0000h 0000h 99 0 0 0 0 "Loopback term"
Term 0607 0:7 PORTTEST 0000h 0000h 99 0 0 0 0 "Loopback term"

Node-Definition
Local-Node 123

End$

/opt/acc/bin/make_n2z_x25init

This script is provided to create configuration files that are intended specifically for use in running the loopback installation verification tests.

usage:make_n2Z_x25init.-t.<template>.[-s.num_of_subchans].\
[-m.<mux_num>...]

If the -m parameter is not used the mux numbers will be 0 to n, where n is one less than the number of ACC cards installed on the system. The make_n2z_x25init script uses the template file (/etc/x25/x25init.sample) to build x25init files for each subchannel on each port of each mux on the system.

Make_n2z_x25init creates x25init configuration files based on the given template file. In the case of the 4-Channel interface, one is created for each subchannel on each port of each multiplexer card. For all other interfaces one is created for each mux port of each of the specified multiplexers.

If XX represents the mux number, and Y represents a port on that mux, with ZZ representing a subchannel on that port:

  • The files are named
    /etc/x25/XXYlooptest or
    /etc/x25/XXYZZlooptest if 4-Channel

  • The X.121 addresses are set to
    4087465XXY00 or
    4087465XXYZZ if 4-Channel

  • The programmatic name parameters are set to
    nataccXXY or
    nataccXXYZZ if 4-Channel

  • The device files referred to are
    /dev/zx25mXXpY or
    /dev/zx25mXXpYsZZ if 4-Channel

  • The type parameters for each port on a given multiplexer are made to alternate between DTE_TT and DCE_TT. The TT is based on the type parameter in the template file.

    For example, if the template file specifies DTE_80, the types for ports 0, 2, 4, and 6 for a given 8-channel multiplexer will be DTE_80, and the types for ports 1, 3, 5, and 7 will be DCE_80.

The following table shows some examples of files that can be created using make_n2z_x25init:

Mux#

Port#

Subch#

File Name (/etc/x25/)

X.121 Address

L3 Name

Device File (/dev/)

2-Channel/8-Channel Interface
XXYZZXXYlooptest4087465XXY00nataccXXYzx25mXXpYsZZ
00 00looptest408746500000natacc000zx25m0p0
01 01looptest408746500100natacc001zx25m0p1
127 127looptest408746512700natacc127zx25m12p7
4-Channel Interface
XXYZZXXYZZlooptest4087465XXYZZnataccXXYZZzx25mXXpYsZZ
23702307looptest408746502307natacc02307zx25m2p3s7
012200122looptest408746500122natacc00122zx25m0p1s22

Note that if additional ACC Mux cards are added to the system, the make_n2z_x25init script can be rerun to create the appropriate x25init files.

The following example x25init file was created by make_n2z_x25init for port 7 of mux 1 on an 8-channel ACC card. The values that were customized by this script (i.e. that are different than the template file) are noted in BOLD.

#
# X.25 Initialization File 17looptest
#
#
x.121 408746501700
x.121_packetaddr 408746501700
device zx25m1p7
name natacc017
#
# Level 2 Parameters
#
t1 1600
t3 60000
framesize 149
n2 10
l2window 7
#
# Level 3 Parameters
#
networktype DCE_80
#
# Circuit Table Definition
#
# LCI TYPE HOW MANY
lci 1 svc 8
#
# Flow Control, Throughput Class, Fast Select and Reverse Charge Settings
#
flowcontrol off
thruputclass off
fast_select_accept disabled
reverse_charge disabled
def_inpacketsize 128
def_outpacketsize 128
def_inwindow 7
def_outwindow 7
def_inthruputclass 11
def_outthruputclass 11
#
# IP Parameters
#
# ipaddress 130.9.192.17
# idletimer 45
# holdtimer 30
# mtu 2048

This second example x25init file was created by make_n2z_x25init for subchannel 7, port 3 of mux 2 on a 4-channel ACC card. The values that were customized by this script (i.e. that are different than the template file) are noted in BOLD.

#
# X.25 Initialization File 020307looptest
#
#
x.121 408746502307
x.121_packetaddr 408746502307
device zx25m2p3s7
name natacc02307
#
# Level 2 Parameters
#
t1 1600
t3 60000
framesize 149
n2 10
l2window 7
#
# Level 3 Parameters
#
networktype DCE_80
#
# Circuit Table Definition
#
# LCI TYPE HOW MANY
lci 1 svc 8
#
# Flow Control, Throughput Class, Fast Select and Reverse Charge Settings
#
flowcontrol off
thruputclass off
fast_select_accept disabled
reverse_charge disabled
def_inpacketsize 128
def_outpacketsize 128
def_inwindow 7
def_outwindow 7
def_inthruputclass 11
def_outthruputclass 11
#
# IP Parameters
#
# ipaddress 130.9.23.7
# idletimer 45
# holdtimer 30
# mtu 2048
Printable version
Privacy statement Using this site means you accept its terms Feedback to webmaster
© 2000 Hewlett-Packard Development Company, L.P.