ACC SNAPlus2 Link Software
User’s Guide
Edition 4
HP 9000 Networking
Manufacturing Part Number: Z7485-90001
E0400
© Copyright 2000 Hewlett-Packard Company
2
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. A copy of the specific warranty terms applicable to your
Hewlett- Packard product and replacement parts can be obtained from
your local Sales and Service Office.
Restricted Rights Legend. Use, duplication or disclosure by the U.S.
Government is subject to restrictions as set forth in subparagraph (c) (1)
(ii) of the Rights in Technical Data and Computer Software clause a t
DFARS 252.227-7013 for DOD agencies, and subparagraphs (c) (1) and
(c) (2) of the Commercial Computer Software Restricted Rights clause at
FAR 52.227-19 for other agencies.
HEWLETT-PACKARD COMPANY 3000 Hanover Street Palo Alto,
California 94304 U.S.A.
Use of this manual and flexible disk(s) or tape cartridge(s) supplied for
this pack is restricted to this product only. Additional copies of the
programs may be made for security and back-up purposes only. Resale of
the programs in their present form or with alterations, is expressly
prohibited.
Copyright Notices. © copyright 1983-2000 Hewlett-Packard Company,
all rights reserved.
Reproduction, adaptation, or translation of this document without prior
written permission is prohibited, except as allowed under the copyright
laws.
©copyright 1979, 1980, 1983, 1985-93 Regents of the University of
California
3
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.
© opyright 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.
© copyright 1990, 1991, 1992 Cornell University
© copyright 1989-1991 The University of Maryland
© copyright 1988 Carnegie Mellon University
© copyright 1989-1997 Data Connection Limited
Trademark Notices UNIX is a registered trademark in the United
States and other countries, licensed exclusively through X/Open
Company Limited.
X Window System is a trademark of the Massachusetts Institute of
Technology.
MS-DOS and Microsoft are U.S. registered trademarks of Microsoft
Corporation.
OSF/Motif is a trademark of the Open Software Foundation, Inc. in the
U.S. and other countries.
4
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.See your HP sales representative for details.
First Edition Nov 1996 Release 2.22
Second Edition August 1997 Release B.02.39 and B.02.40
Third Edition March 1999 Release B.03.02
Fourth Edition April 2000 Release B.03.10
5
6
Contents
1. About ACC SNAPlus2 Link Software
Introduction................................................10
ProductFeatures............................................11
RequirementsandConsiderations..............................12
OSVersionsSupported .....................................12
ACCHardwareSupported...................................12
Pre-requisiteSoftware......................................12
Usage..................................................12
UsingSNAOverSDLC....................................12
UsingSNAOverX.25.....................................13
ACCHardwareNotaPre-requisite............................13
TheSNAPlus2LinkwithSNA/ACC.............................14
SupportedDevices...........................................15
ModeofOperation...........................................16
DataRates ...............................................16
References .................................................17
2. Software Installation and Verification
Introduction................................................20
SoftwareInstallation.........................................21
Running Swinstall . . . . .....................................21
SoftwareIdentification.......................................23
InstallationVerification ......................................24
LoopbackConfigurationRequirements.........................24
LoopbackConfigurationFile.................................24
BringingUpZCOM ........................................26
7
Contents
SNA/ACCSoftwareVerification..............................27
SNAplus2Configuration..................................27
SNAplus2OverSNA/ACCVerification ......................30
3. Using SNA plus2 via SNA/ACC
Introduction...............................................32
CheckingSNAplus2Status................................... 33
A. Files, Utilities, and Daemons
sna_node.cfgFile ........................................... 36
8
1 About ACC SNAPlus2 Link
Software
9
About ACC SNAPlus2 Link Software
Introduction
Introduction
The ACC SNAPlus2 Link Software product allows Hewlett-Packard’s
HP-UX SNAplus products to be used with SDLC over Multi-channel
ACC Multiplexer products. This manual provides installation and
configuration information that is specific to the SNA/ACC Software.
Refer to the ACC Error Guide for information about SNA/ACC error
codes.
The ACC SNAPlus2 Link Software product may be obtained for the
8-Channel HP-PB (NIO), the 8-Channel EISA, the 8-Channel PCI, and
the 2-Channel HP-PB (NIO) interfaces.
NOTE The ACC SNAPlus2 Link Software is needed when theSNAPlus2 Linkis
to be used with SDLC via multi-channel ACC. For SNA over X.25, only
the X.25/ACC (ACC and X.25/9000 Link Software) and SNAplus2
products are required.
When ACC SNAPlus2 Link Software is installed, the ACC interface
supports SNAplus2 running over SDLC, X25 or other protocols
simultaneously on the same ACC multiplexer card.
10 Chapter1
About ACC SNAPlus2 Link Software
Product Features
Product Features
SNA/ACC software enables the use of HP-UX SNAplus2 products over
SDLC via the multi-channel, multi-protocol ACC Interface.
The SNA/ACC product includes the following features:
• Installs with SD-UX utility swinstall
• Auto-Dial feature fully supported
• SNAplus2 communicates with ACC via either SDLC or X.25
• snaacc_tool utilities which provide debugging resources
Chapter 1 11
About ACC SNAPlus2 Link Software
Requirements and Considerations
Requirements and Considerations
OS Versions Supported
The ACC SNAPlus2 Link Software product supports HP-UX 11.0.
ACC Hardware Supported
The ACC Base Software product and the ACC and X.25/9000 Software
Bundle product may be ordered to use with the following ACC hardware
products:
• 8-Channel HP-PB (NIO) ACC Multi-channel Interface
• 8-Channel EISA ACC Multi-channel Interface
• 8-Channel PCI ACC Multi-channel Interface
• 2-Channel HP-PB (NIO) ACC Multi-channel Interface
Pre-requisite Software
You must have the followingproducts already installed on your computer
before you start the SNA/ACC installation procedure:
• SNAplus2, version 6.0
• ACC Base Software, version 3.02 or later
or
ACC and X.25/9000 Software Bundle, version 3.02 or later
Usage
The SNAplus2 features can be used with multi-channel ACC products
over SDLC and over X.25.
Using SNA Over SDLC
Touse SNAplus2 over SDLC with the ACC cards, the SNAplus2 software
product, the ACC Base Software and the ACC SNAplus2 Link Software
must be installed on your system.
12 Chapter1
About ACC SNAPlus2 Link Software
Requirements and Considerations
Using SNA Over X.25
To use SNAplus2 over X.25 with the ACC cards, both the SNAplus2 and
the X.25/ACC products must be installed on your system. The SNA/ACC
product is not required.
ACC Hardware Not a Pre-requisite
It is not a requirement that you install your ACC cards first before
installing the pre-requisite ACC software mentioned above or the ACC
SNAPlus2 Link Software. You may install the ACC software first, and
then install your ACC cards later on.
However, in the case of the pre-requisite ACC software, if you install
your ACC cards after this software has been installed, then you will need
to do some configuration to update this installed ACC software to
recognize these new cards. For details on this, refer to the ACC
Installation and C onfiguration Guide that is provided with the ACC
Base Software product, or the X.25/ACC Installation and Configuration
Guide that is provided with the ACC and X.25/9000 Software Bundle
product.
Chapter 1 13
SNAplus2
SNA/ACC
About ACC SNAPlus2 Link Software
The SNAPlus2 Link with SNA/ACC
The SNAPlus2 Link with SNA/ACC
The diagram shown below illustrates the relationship between the
SNAplus2 product and the SNA/ACC software described in this
document.
X.25/ACC
8-Channel
EISA
ACC
Base ACC Product
Software
ACC Mux I/F
8-Channel
NIO
ACC
14 Chapter1
8-Channel
PCI
ACC
2-Channel
NIO
ACC
Hardware
About ACC SNAPlus2 Link Software
Supported Devices
Supported Devices
HP-UX SNAPlus2 Link software provides services with any compatible
device conforming to IBM’s Logical Unit types 0-3 and LU 6 .2
architectures, which allows for APPC, LUA and CPI-C data exchanges in
a Systems Network Architecture (SNA).
SNA/ACC provides HP-9000/SNAplus2 servers with expanded
(multi-channel and multi-protocol) WAN access at conventional data
rates via the HP-PB (NIO) 8-Channel and EISA 8-Channel ACC
Multiplexer interfaces. It also provides high-rate WAN access via the
HP-PB (NIO) 2-Channel interface and the 8-Channel PCI interface.
Chapter 1 15
About ACC SNAPlus2 Link Software
Mode of Operation
Mode of Operation
SNA/ACC supports the running of SNAPlus2 Link in a client/server
environment,provided the required LAN/9000 Series 700 or Series800
software components, such as, the ARPA/Berkeley Sockets are
configured.
Support for running SNAPlus2 Link using QLLC via SNA/ACC requires
installation of ACC and X.25/9000 software. Support for running
SNAPlus2 L ink using SDL C via the Multi-proto col ACC Base System
software and the ACC SNAPlus2 link Software.
Data Rates
Data rates are available up to 76.8k baud for 8-channel ACC multiplexer
cards using the HP-PB-standard backplane, or 128k baud for 8-channel
cards installed in the EISA-standard backplane. The S NA/ACC product
can be used at higher rates with high-speedACC multiplexer cards, such
as the 8-Channel PCI and 2-Channel ACC products with 512K baud
capability.
16 Chapter1
About ACC SNAPlus2 Link Software
References
References
Forinformation on installing the ACC Base Software product and how to
start up the ACC Subsystem, refer to the ACC Installation and
Configuration Guide, which is provided with the ACC and X.25/9000
Software Bundle and the ACC Base Software products.
For information on using the utilities related to the ACC products, refer
to the ACC Utilities Reference Guide.
For information on installingthe X.25 protocolon ACC products, refer to
the X.25/ACC Installation and Configuration Guide.
For information on SNA/ACC error codes and other ACC error, status,
and warning messages, refer to the ACC Error Guide.
Chapter 1 17
About ACC SNAPlus2 Link Software
References
18 Chapter1
2 Software Installation and
Verification
19
Software Installation and Verification
Introduction
Introduction
This chapter describes how to install the ACC SNAPlus2 Link Software
product using the swinstall utility.
NOTE Successful completion of SNA/ACC software installation relies upon
PRIOR INSTALLATION OF THE ACC BASE SOFTWARE. Use swlist
-l bundle to confirm prior installation. You may disregard this if you
are instal ling SNA/ACC concurrently with the ACC Base Software
product.
The SNAplus2 Link product may be installed either before or after the
SNA/ACC product. However, the SNAplus2 product must eventually be
installed so that you can use its SAM SNAplus2 GUI to configure the
SNA/ACC driver into system kernel.
If you intend to use SNAplus2 services over X.25/ACC, you must first
install the ACC and X.25/9000 Software Bundle product or the ACC Base
Software and the ACC X.25/9000 Link Software.
20 Chapter2
Software Installation and Verification
Software Installation
Software Installation
Running Swinstall
The SNA/ACC software is read from the HP-UX Application CD-ROM, in
superuser mode, using the swinstall utility. The steps are shown below.
Step 1. Log in to the system as “root”.
Step 2. Place the media in a local or remote CD-ROM drive and mount the
CD-ROM drive. For example:
% mkdir /cdrom
% mount /dev/dsk/c1t1d0 /cdrom
Step 3. Run .swinstall, which behaves the same in the GUI interface as for the
terminal interface. When the “Specify Source” box opens, select “Source
Depot Type” to “Local CDROM”, or for a remote CD-ROM driver, select
for “Network Directory/CDROM” and set “Source Host Name...”. Select
“OK”.
Step 4. When you have made certain that the ACC Base Software or the ACC
and X.25/9000 Software Bundle product is already installed, select the
ACC SNAPlus2 Link Software item from the list of software bundles;
open the “Actions” menu and select “Mark for Install”.
Step 5. When all items have been marked, select “Install (analysis)”; select “OK”
and proceed.
The “Install (analysis)” window allows you to track summary progress of
theinstallationprocess.Usethe“Logfile”featuretodisplayadetailed
status, which is logged to /var/adm/sw/swagent.log.
Step 6. Exit swinstall.
Step 7. Run sam (see Figure 2-1). When the SAM GUI window opens, select and
open the “Networking and Communications” window. When it opens,
select and open the “SNAplus2 Installation” window.
Chapter 2 21
Software Installation and Verification
Software Installation
Step 8. Find the SDLC (ACC) item and double-click to execute the “Actions >
Add Component” function. Repeat for the QLLC (X.25) item, if the
status message reads Not Added (See screen illustration below).
Figure 2-1 SNAplus2 Installation Using SAM
Step 9. Click on “Yes” when SAM prompts you to exit, and click on “Yes” at the
“Create New Kernel” prompt.
CAUTION A final Confirmation message informs you that a new kernel will be
rebuilt using the filesets installed, and the system will reboot. When you
are ready, select “Yes”.
22 Chapter2
Software Installation and Verification
Software Identification
Software Identification
•Thewhat utility can be run on /stand/vmunix to show what version
of drivers are actually generated into the system.
• If you need to check version status for ACC core firmware files
installed on your system, use what on /opt/acc/sys,
/opt/acc/protocol, and /opt/acc/<card-type> directories.
• Use the SD utility swverify to check dependency relationships,file
integrity and software states if needed.
• Once the system is up and running, the zmntr utility can be used to
determinetherevisionsoffirmwarefilesthathavebeendownloaded
to the mux. Refer to the ACC Utilities R eference Guide for more
information on the use of the zmntr utility.
• You can check to see that the SNA/ACC library libsnaacc.a is
installed in the kernel along with the SNAPlus2 libraries.
Chapter 2 23
Software Installation and Verification
Installation V e rification
Installation Verification
If this is the first-time installation of an ACC card, the full procedure
found in ACC Installation and Configuration Guide,Chapter2,section
“Installation Verification” can be used to verify that the ACC hardware
and software have been properly installed and are functional. Otherwise
skip that section and continue below.
Loopback Configuration Requirements
The ACC product providesa loopback protocol module which can be used
to runa loopback test to exercisethe ACC multiplexercard, any attached
panel, and the specified port. The loopbacktest is run using the loopback
test feature of the zmntr utility. (Refer to the ACC Utilities Reference
Guide.)
The test requires the following:
• At least one ACC interface card must be installed into the system,
and it must have a panel (or RS-232 cable if mux card is 2-Channel)
attached.
• The ACC Base Software or the ACC and X.25/9000 Software Bundle
product must be installed andthe system must have been rebuilt and
rebooted.
Loopback Configuration File
A loopback configuration file /opt/acc/cfg /loopback .answ is
automatically created when the ACC Base Software was installed. It
reflects the location of any ACC cards installed at the time swinstall was
run. The ttgen utility is also automatically run on this file to create
/opt/acc/cfg/lo opback.tm em. Refer to ACC Installation and
Configuration Guide, Chapter 2, if the ACC Mux cards have been moved
within the s ystem, or if additional cards have b een added to the system.
Your ACC .answ file should look like the following:
24 Chapter2
Software Installation and Verification
#include ”/opt/acc/cfg/ttgendefine”
ttgen
Configuration
system-name ”SNA/ACC Interface sample ttgen input file”
program-zlu 100
terminal-zlu 800
logical-term 400
physical-term 400
buffer-pool 3000000
logical-size 256
queue-Limit 200
transmit-limit 100
unack-limit 5000
port-limit 20000
E1T1-Port-Limit 100000
node-entry 1
Interface-Definition
<card-type> 0 <bus:slot> /opt/acc/<card-type>/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 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
Installation Verification
Terminal-Definition
Term 600 0:0 HDLC.FRAME 0000h 0000h 410000"SNAPLUS device"
Term 601 0:1 HDLC.FRAME 0000h 0000h 410000"SNAPLUS device"
* ^^^ ^^^ ^^^^^ ^^
* ZLU _____| | | |
* mux:port_____| | |
* poll word; use 0000h for | |
* 2-wire or 0080h for 4-wire_| |
* application number; 41 for SNAplus2_____|
Node-Definition
Local-Node 123
End$
Chapter 2 25
Software Installation and Verification
Installation V e rification
NOTE Versions of SNA/ACC prior to B02.40 dynamically handled the creating
of terminal definitions. Versions of SNA/ACC for 3.02 and above require
the user to define terminals statically in the .answ files as illustrated in
the example .answ file. You must add the Term entries to your .answ file
and modify them appropriately for your configuration requirements.
Bringing Up ZCOM
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. Invoke zmasterd as follows:
% zmasterd cold /opt/acc/cfg/loopback.tmem
Messages indicating whether or not the ZCOM Mux subsystem was
started successfully willbe logged to the file /var/opt/acc/log/XXX.tlog,
where XXX represents the day of the week, for example, mon.tlog and
tue.tlog.
If any error is reported during the start up procedure, it may be
necessary to s top the ZCOM subsystem by running:
% zmasterd stop
The error should then be addressed, and then the ZCOM subsystem
should be restarted. Refer to the ACC Error Guide for detailed
information about messages reported by zmlog.
26 Chapter2
Software Installation and Verification
Installation Verification
SNA/ACC Software Verification
When it is determined that the ACC Multiplexer hardware and ACC
Base Software are fully operational with no problems, the peer-to-peer
test procedures in this section should be run to verify that the SNA/ACC
installation is correct and the SNAplus2 software can work with it.
The SNAplus2 GUI, shown below (Figure 2-2), is convenient for this
verification phase. If the SNAplus2 software is not running, issue the
following command to manually start SNAplus2:
% /opt/sna/bin/snap start
SNAplus2 Configuration
Run the xsnapadmin program and set items found in the “Services”
menu windows (Figure 2-2) per the following steps:
Step 1. Make the following selections under “Configure” in the Node Parameters
window:
Control point name: USHWP01.<host_name>
Control point alias: <host_name>
Node ID: 05F FFFFF
Step 2. Make the following selections under “Connectivity” in the “New Port”
window:
Port using: ACC SDLC card
SNA port name: SDLCP0
ACC SDLC card number: 0
Port number: 0
Initially active: depressed (red)
Line details:
Type: Leased line
Link role: Secondary
Encoding: NRZ
Duplex setting: Half duplex
Chapter 2 27
Software Installation and Verification
Installation V e rification
Figure 2-2 The xsnapadmin Screen (SNAplus2 GUI)
Ports Link Stations
-+
Node
28 Chapter2
Software Installation and Verification
Installation Verification
Step 3. Make the following selections under “Connectivity” in the “New Port”
window:
Port using: ACC SDLC card
SNA port name: SDLCP1
ACC SDLC card number: 0
Port number: 1
Initially active: depressed (red)
Line details:
Type: Leased line
Link role: Primary
Encoding: NRZ
Duplex setting: Half duplex
Step 4. Make the following selections under “Connectivity” in the “New link
station” window:
Add link station to: SDLCP0
Name: SDLCL0
SNA port name: SDLCP0
Activation: By administrator
LU traffic: Dependent only
Local node ID: 05F FFFFF
Remote node ID: <blank> <blank>
Contact information:
Poll address: C1
Click on the “Advanced...” button. Select the following:
Max send BTU size: 265 (should be the default)
Host type: SNA
Send format 3 XID: depressed (red)
Don’t send local node name: depressed (red)
Reactivate link station after failure: not depressed (grey)
Chapter 2 29
Software Installation and Verification
Installation V e rification
Step 5. Make the following selections under “Connectivity” in the “New link
station” window:
Add link station to: SDLCP0
Name: SDLCL1
SNA port name: SDLCP1
Activation: By administrator
LU traffic: Independent only
Remote node... USHWP01.ACCP01
Contact information:
Poll address: C1
SNAplus2 Over SNA/ACC Verification
Use the xsnapadmin program t o activate the ports and link stations:
1. Activate the node first.
2. Activate the ports.
3. Activate the primary link station first. (Use the Zoom feature in the
GUI if you need to configure a station as primary.)
4. Activate the primary link station first. (Use the Zoom feature in the
GUI if you need to configure a station as primary.)
5. While the primary link station is “Starting”, activate the secondary
link station.
In its “Connectivity and dependent LUs” section, the xsnapadmin screen
should show the status of both ports and link stations as “Active” when
the verification procedure has been successful.
30 Chapter2
3 Using SNAplus2 via SNA/ACC
31
Using SNAplus2 via SNA/ACC
Introduction
Introduction
For a complete description of the communication formats, refer to the
documents referenced on page 1 7 in Chapter 1 , “About A CC SNAPlus2
Link Software,” of this manual.
Data transmitted at Level 2 over an SNAplus2 link via ACC is in the
SDLC format. When a QLLC link is used the data transmitted at Level 3
is framed into standard X.25 packet format.
ThescopeofthisChapterisconfinedtoactivationoftheSNAplus2
software, after which the ACC interface is merely a transparent or
“pass-through” entity in the path.
32 Chapter3
Using SNAplus2 via SNA/ACC
Checking SNAplus2 Status
Checking SNAplus2 Status
If the new kernel has booted successfully (Chapter 2, Section Software
Installation, Step #8), the SNAplus2 software is probably running. Use
the following command to check for the status of SNAplus2 on your
system:
/opt/sna/bin/X11/xsnapadmin
NOTE Use of xsnapadmin requires Motif interface software and a bit-mapped
display to run X11. Use snapadmin as an alternative if necessary.
The xsnapadmin window appears as shown in Figure 3-1. If the
SNAplus2 software is not running, issue the following command to
manually start SNAplus2:
/opt/sna/bin/snap start
If this is unsuccessful, refer to the HP-UX SNAplus2 Installation Guide
for detailed procedures.
Chapter 3 33
Using SNAplus2 via SNA/ACC
Checking SNAplus2 Status
Figure 3-1 xsnapadmin Window
34 Chapter3
A Files, Utilities, and Daemons
This appendix provides a sample of the SNAplus2 configuration file,
which can be edited to reflect different host names, etc. on different
systems. Note that editing this file is equivalent t o running the
xsnapadmin program.
35
Files, Utilities, and Daemons
sna_node.cfg File
sna_node.cfg File
/etc/opt/sna/sna_node.cfg--
[define_node_config_file]
major_version = 5
minor_version = 1
update_release = 1
revision_level = 18
[define_node]
node_name = <host_name>
description = ““
node_type = LEN_NODE
fqcp_name = USHWP01.<HOST_NAME>
cp_alias = <host_name>
mode_to_cos_map_supp = NO
mds_supported = YES
node_id = <05ffffff>
max_locates = 100
dir_cache_size = 255
max_dir_entries = 0
locate_timeout = 60
reg_with_nn = YES
reg_with_cds = YES
mds_send_alert_q_size = 100
cos_cache_size = 24
tree_cache_size = 40
tree_cache_use_limit = 40
max_tdm_nodes = 0
max_tdm_tgs = 0
max_isr_sessions = 1000
isr_sessions_upper_threshold = 900
isr_sessions_lower_threshold = 800
isr_max_ru_size = 16384
isr_rcv_pac_window = 8
store_endpt_rscvs = NO
store_isr_rscvs = NO
store_dlur_rscvs = NO
dlur_support = NO
pu_conc_support = NO
nn_rar = 128
ptf_flags = NONE
36 AppendixA
[define_sdlc_dlc]
dlc_name = SDLC0
description = ““
neg_ls_supp = YES
card_type = HP_ACC
initially_active = NO
adapter_number = 0
mu_credit = 4
stats_support = YES
num_ports = 8
[define_sdlc_port]
port_name = SDLCP0
description = ““
dlc_name = SDLC0
port_type = PORT_NONSWITCHED
port_number = 0
max_rcv_btu_size = 265
tot_link_act_lim = 1
inb_link_act_lim = 0
out_link_act_lim = 1
ls_role = LS_SEC
act_xid_exchange_limit = 10
nonact_xid_exchange_limit = 10
ls_xmit_rcv_cap = LS_TWA
max_ifrm_rcvd = 7
target_pacing_count = 7
max_send_btu_size = 265
address = 0x00
implicit_cp_cp_sess_support = NO
implicit_limited_resource = NO
implicit_deact_timer = 0
effect_cap = 9600
connect_cost = 0
byte_cost = 0
security = SEC_NONSECURE
prop_delay = PROP_DELAY_TELEPHONE
user_def_parm_1 = 0
user_def_parm_2 = 0
user_def_parm_3 = 0
initially_active = YES
idle_timer = 1000
idle_timer_retry = 60
np_rcv_timer = 1000
np_rcv_timer_retry = 30
write_timer = 1000
write_timer_retry = 5
link_conn_timer = 1000
link_conn_timer_retry = 60
pri_fdplx = NO
sec_fdplx = NO
Files, Utilities, and Daemons
sna_node.cfg File
Appendix A 37
Files, Utilities, and Daemons
sna_node.cfg File
use_rej = NO
spec_port_type = LEASED
max_xid_size = 256
max_retry_count = 10
opt1 = NONE
opt2 = NONE
linesp = 0
rcv_pool_size = 8
poll_wait = 1
hmod_data = ““
contact_timer = 3000
contact_timer_retry = 10
contact_timer2 = 10000
contact_timer_retry2 = 65535
disc_timer = 10000
disc_timer_retry = 2
nve_poll_timer = 100
nve_poll_timer_retry = 65535
nve_poll_timer2 = 500
nve_poll_timer_retry2 = 65535
no_resp_timer = 2000
no_resp_timer_retry = 10
rem_busy_timer = 2000
rem_busy_timer_retry = 10
rr_timer = 0
poll_frame = XID
poll_on_iframe = YES
[define_sdlc_port]
port_name = SDLCP1
description = ““
dlc_name = SDLC0
port_type = PORT_NONSWITCHED
port_number = 1
max_rcv_btu_size = 265
tot_link_act_lim = 1
inb_link_act_lim = 0
out_link_act_lim = 1
ls_role = LS_PRI
act_xid_exchange_limit = 10
nonact_xid_exchange_limit = 10
ls_xmit_rcv_cap = LS_TWA
max_ifrm_rcvd = 7
target_pacing_count = 7
max_send_btu_size = 265
address = 0x00
implicit_cp_cp_sess_support = NO
implicit_limited_resource = NO
implicit_deact_timer = 0
effect_cap = 9600
connect_cost = 0
38 AppendixA
byte_cost = 0
security = SEC_NONSECURE
prop_delay = PROP_DELAY_TELEPHONE
user_def_parm_1 = 0
user_def_parm_2 = 0
user_def_parm_3 = 0
initially_active = YES
idle_timer = 1000
idle_timer_retry = 60
np_rcv_timer = 1000
np_rcv_timer_retry = 30
write_timer = 1000
write_timer_retry = 5
link_conn_timer = 1000
link_conn_timer_retry = 60
pri_fdplx = NO
sec_fdplx = NO
use_rej = NO
spec_port_type = LEASED
max_xid_size = 256
max_retry_count = 10
opt1 = NONE
opt2 = NONE
linesp = 0
rcv_pool_size = 8
poll_wait = 1
hmod_data = ““
contact_timer = 3000
contact_timer_retry = 10
contact_timer2 = 10000
contact_timer_retry2 = 65535
disc_timer = 10000
disc_timer_retry = 2
nve_poll_timer = 100
nve_poll_timer_retry = 65535
nve_poll_timer2 = 500
nve_poll_timer_retry2 = 65535
no_resp_timer = 2000
no_resp_timer_retry = 10
rem_busy_timer = 2000
rem_busy_timer_retry = 10
rr_timer = 0
poll_frame = XID
poll_on_iframe = YES
Files, Utilities, and Daemons
sna_node.cfg File
[define_sdlc_ls]
ls_name = SDLCL0
description = ““
port_name = SDLCP0
adj_cp_name = <0000000000000000000000000000000000>
adj_cp_type = HOST_XID3
Appendix A 39
Files, Utilities, and Daemons
sna_node.cfg File
address = 0xc1
auto_act_supp = NO
tg_number = 0
limited_resource = NO
solicit_sscp_sessions = YES
pu_name = SDLCL0
disable_remote_act = NO
default_nn_server = NO
dspu_services = NONE
dspu_name = <0000000000000000>
dlus_name = <0000000000000000000000000000000000>
bkup_dlus_name = <0000000000000000000000000000000000>
link_deact_timer = 0
use_default_tg_chars = YES
ls_attributes = SUPPRESS_CP_NAME
adj_node_id = <05ffffff>
local_node_id = <00000000>
cp_cp_sess_support = NO
effect_cap = 9600
connect_cost = 0
byte_cost = 0
security = SEC_NONSECURE
prop_delay = PROP_DELAY_TELEPHONE
user_def_parm_1 = 0
user_def_parm_2 = 0
user_def_parm_3 = 0
target_pacing_count = 7
max_send_btu_size = 265
ls_role = USE_PORT_DEFAULTS
initially_active = NO
react_timer = 30
react_timer_retry = 0
contact_timer = 3000
contact_timer_retry = 10
contact_timer2 = 10000
contact_timer_retry2 = 65535
disc_timer = 10000
disc_timer_retry = 2
nve_poll_timer = 100
nve_poll_timer_retry = 65535
nve_poll_timer2 = 500
nve_poll_timer_retry2 = 65535
no_resp_timer = 2000
no_resp_timer_retry = 10
rem_busy_timer = 2000
rem_busy_timer_retry = 10
rr_timer = 0
poll_frame = XID
poll_on_iframe = YES
opt1 = NONE
linesp = 0
40 AppendixA
Files, Utilities, and Daemons
sna_node.cfg File
hmod_data = ““
[define_sdlc_ls]
ls_name = SDLCL1
description = ““
port_name = SDLCP1
adj_cp_name = USHWP01.<REMOTE_HOST_NAME>
adj_cp_type = END_NODE
address = 0xc1
auto_act_supp = NO
tg_number = 0
limited_resource = NO
solicit_sscp_sessions = NO
pu_name = <0000000000000000>
disable_remote_act = NO
default_nn_server = NO
dspu_services = NONE
dspu_name = <0000000000000000>
dlus_name = <0000000000000000000000000000000000>
bkup_dlus_name = <0000000000000000000000000000000000>
link_deact_timer = 0
use_default_tg_chars = YES
ls_attributes = SNA
adj_node_id = <00000000>
local_node_id = <00000000>
cp_cp_sess_support = NO
effect_cap = 9600
connect_cost = 0
byte_cost = 0
security = SEC_NONSECURE
prop_delay = PROP_DELAY_TELEPHONE
user_def_parm_1 = 0
user_def_parm_2 = 0
user_def_parm_3 = 0
target_pacing_count = 7
max_send_btu_size = 265
ls_role = USE_PORT_DEFAULTS
initially_active = NO
react_timer = 30
react_timer_retry = 0
contact_timer = 3000
contact_timer_retry = 10
contact_timer2 = 10000
contact_timer_retry2 = 65535
disc_timer = 10000
disc_timer_retry = 2
nve_poll_timer = 100
nve_poll_timer_retry = 65535
nve_poll_timer2 = 500
nve_poll_timer_retry2 = 65535
no_resp_timer = 2000
Appendix A 41
Files, Utilities, and Daemons
sna_node.cfg File
no_resp_timer_retry = 10
rem_busy_timer = 2000
rem_busy_timer_retry = 10
rr_timer = 0
poll_frame = XID
poll_on_iframe = YES
opt1 = NONE
linesp = 0
hmod_data = ““
[define_directory_entry]
resource_name = USHWP01.<REMOTE_HOST_NAME>
resource_type = ENCP_RESOURCE
description = (Auto defined - remote node)
parent_name = <0000000000000000000000000000000000>
parent_type = ENCP_RESOURCE
[define_directory_entry]
resource_name = USHWP01.<REMOTE_HOST_NAME>
resource_type = LU_RESOURCE
description = (Auto defined - CP LU)
parent_name = USHWP01.<REMOTE_HOST_NAME>
parent_type = ENCP_RESOURCE
42 AppendixA
Files, Utilities, and Daemons
sna_node.cfg File
Appendix A 43
Files, Utilities, and Daemons
sna_node.cfg File
44 AppendixA
Files, Utilities, and Daemons
sna_node.cfg File
Appendix A 45
Files, Utilities, and Daemons
sna_node.cfg File
46 AppendixA
Files, Utilities, and Daemons
sna_node.cfg File
Appendix A 47
Files, Utilities, and Daemons
sna_node.cfg File
48 AppendixA
Loading...