Page 1 SunLink™ SNA 9.1 PU2.1 Server Conﬁguration Guide Sun Microsystems Computer Company A Sun Microsystems, Inc. Business 2550 Garcia Avenue Mountain View, CA 94043 USA 415 960-1300 fax 415 969-9131 Part No.: 802-2673-12 Revision A, August 1997...
Page 2 Sun, Sun Microsystems, the Sun logo, AnswerBook, SunDocs, SunLink, OpenWindows, and Solaris are trademarks, registered trademarks, or service marks of Sun Microsystems, Inc. in the U. S. and other countries. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc.
Page 3: Table Of Contents
Contents Preface ..........1.
Page 4 2.3.5 Events Window ......SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 5 2.3.6 Resource Window ......2.4 Managing Windows ....... 2.5 Selecting Items .
Page 6 8.2 Modifying Dependent LUs ......8.3 Deleting Dependent LUs ......SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 7 8.4 Creating an LU Pool ....... 8.5 Modifying an LU Pool ......8-11 9.
Page 8 11.5.3 Making an Off-line Conﬁguration Active ..11-16 11.6 Controlling the Status of Resources ....11-17 viii SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 9 12. Troubleshooting ........12-1 12.1 Diagnostic Tools .
Page 10 A.12 Users Resource Form ......A-8 SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 11 A.13 Group Resource Form ......A-9 A.14 Client Conﬁguration Requirements ....A-9 B.
Page 12 F.4.2 SDLC Connection ......F-14 SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 13 G. LUType 6.2 Security ........G-1 G.1 Session-Level Security .
Page 14 SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 15 Figures Figure 1-1 Sun PU2.1 SNA Server and Clients..... . . Figure 1-2 Sample Configuration (Single System)....Figure 1-3 Sample Configuration (Multiple Systems).
Page 16 SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 17 Tables Table 2-1 Window Management Tasks ......Table 2-2 SunGMI Toolbar ........2-11 Table 2-3 Dialog Action Buttons.
Page 18 SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 19: Before You Read This Book
This book is geared towards network administrators familiar with the SNA protocol, Unix, Windows, and server technology and who are responsible for the installation and maintenance of the SunLink SNA 9.1 PU2.1 server. Sun assumes that you are familiar with network administration, network management, and the related terminology therein.
Page 20 50% or fewer of the manager systems are available, how to modify the active conﬁguration and how to save and distribute the updates, how to create and modify off-line SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 21 conﬁgurations and how to activate an off-line conﬁguration, how to start and stop connections to the SNA network, and how to make resources unavailable or available for client use. Chapter 12, “Troubleshooting,” covers the diagnostic tools provided to help you and SunLink Technical Support staff determine the cause of any problems you may encounter.
Page 22: Typographic Conventions
The following table shows the default system prompt and superuser prompt for the C shell, Bourne shell, and Korn shell. Shell Prompt C shell machine_name% C shell superuser machine_name# Bourne shell and Korn shell Bourne shell and Korn shell superuser xxii SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 23: Related Documents
Related Documents The following Sun documents contain topics that relate to the information in SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide. Application Deliverable Partnumber Installation SunLink SNA 9.1 End Node Planning and Installation Guide 802-2665-12 Administration SunLink SNA/X.25 9.1 Conﬁguration and Administration Guide 802-3166-12 Conﬁguration and user...
Page 24: Other Publications
Systems Application Architecture Common Programming Interface Communications Reference, SC26-4399 IBM Token Ring • IBM Token-Ring Network Architecture Reference, SC30-3374 X.25 • IBM X.25 Network Control Program Packet Switching Interface, Planning and Installation, SC30-3501 xxiv SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 25: Sun Welcomes Your Comments
Ordering Sun Documents SunDocs is a distribution program for Sun Microsystems technical documentation. Easy, convenient ordering and quick delivery is available from SunExpress. You can ﬁnd a full listing of available documentation on the World Wide Web: http://www.sun.com/sunexpress/ Table P-1 SunExpress Contact Information...
Page 26 SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 27: Overview
Overview This chapter contains the following sections: • Overview - provides a brief description of the Sun PU2.1 SNA Server. • Sun PU2.1 SNA Server Components - describes the components of the Sun PU2.1 SNA Server that you will most frequently encounter. •...
Page 28: Overview
Processor Sun PU2.1 SNA Server AS/400 SNA 5250 Emulation SNA LU6.2 FTP to Host Router Network Program TCP/IP and SPX/IPX SNA 3770 TN3270E Emulation Figure 1-1 Sun PU2.1 SNA Server and Clients SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 29: System Manager
1.2 Sun PU2.1 SNA Server Components The Sun PU2.1 SNA Server consists of several software components that cooperate with each other to manage the distributed environment. The following sections describe those components you will encounter most frequently when using the server. 1.2.1 Graphical Management Interface The Sun Graphical Management Interface (SunGMI) provides a graphical interface for managing the Sun PU2.1 SNA Server.
Page 30: Pu2.1 Server Process
LUs. In addition, if the network is conﬁgured appropriately, the Sun Name Server can direct the client to the system in the most suitable geographical location. For more information, refer to Appendix E, “Load Balancing.” SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 31: Conﬁguration Options
1.2.6 Conﬁguration Options You can install the components of the Sun PU2.1 SNA Server in a variety of ways, depending on your needs. For example, you could install all the components on a single system. In this case, you would install one SunGMI, one SunGMAN, and one SunSMAN.
Page 32: Figure 1-3 Sample Configuration (Multiple Systems)
As a ﬁnal example, you could create a manager network by installing multiple instances of the SunGMAN. Refer to the following ﬁgure. For more information about manager networks, refer to Section 1.10, “Manager Network,” on page 1-19. SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 33: Figure 1-4 Sample Configuration (Manager Network)
System 1 System 2 SunGMAN SunGMAN System 4 System 3 SunSMAN SunSMAN SunPU2.1 SunPU2.1 Figure 1-4 Sample Conﬁguration (Manager Network) 1.3 Systems and Servers The Sun PU2.1 SNA Server allows you to conﬁgure systems and PU2.1 servers. When you conﬁgure a system, you deﬁne the machines that connect to your SNA network and the distribution of functions among those machines.
Page 34: Lan Connections
Other supported features include: • Point-to-point lines (full duplex). • Multi-point lines (half duplex). • Primary, secondary, and negotiable station roles. • NRZ and NRZI encoding. SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 35: Pu2.1 Emulation
To have an XID-3 exchange and independent LU support, you must set DLC Role to Negotiable. Otherwise, SDLC support is PU 2.0 only. 1.4.3 QLLC Connections You can use the Qualiﬁed Logical Link Control (QLLC) protocol to connect the Sun PU2.1 SNA Server to an IBM communications controller over X.25 Packet Switched Data Networks (PSDNs) by using X.25 virtual circuits (VCs).
Page 36: Lu Emulation
LUs. For more information, refer to the following section. • Independent LUs - Independent LUs are activated locally either through auto-activation or through operator control. Independent LUs can be LUType 6.2 only. 1-10 SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 37: Lu Pools
For independent LU-LU sessions, either independent LU can initiate the session. In addition, multiple sessions, known as parallel sessions, can be established between two independent LUs. For both SSCP-LU control sessions and LU-LU application sessions, the Sun PU2.1 SNA Server enforces the SNA protocols. For more information about conﬁguring dependent LUs, refer to Chapter 8, “Conﬁguring Dependent LUs.”...
Page 38: Users And User Groups
LU to restrict the LU to that client connection. Note – If you use an LU as the default resource and a system or network outage occurs, the client may not be connected since the LU is not available. 1-12 SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 39 • LU pool - Allows you to maximize access to the host system. A client does not depend on a system or a connection to access the host system, but can connect to a dependent LU as long as the LU is available from the pool. •...
Page 40: Supported Clients
TCP/IP on your mainframe. You can conﬁgure LUs for traditional TN3270 clients as either terminals or printers. Typically, use LU pools for assignment of terminal clients and use speciﬁc LU assignment for printer clients. 1-14 SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 41: Extended Telnet 3270E
Because a traditional TN3270 client cannot specify a resource to connect to, the Sun PU2.1 SNA Server allows you to deﬁne a user record for the client. The user record includes either an IP address or an IP hostname to identify the client and one or more default resources to be used by the client.
Page 42: Sun 3270
For more information about creating an LU pool, refer to Section 8.4, “Creating an LU Pool,” on page 8-9. For more information about conﬁguring a user record, refer to Chapter 10, “Conﬁguring Users.” 1-16 SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 43: Sun Appc
1.9.5 Sun APPC Advanced Program-to-Program Communication (APPC) allows programs on peer systems to communicate with each other over an SNA network. Sun APPC (SUNWappc) allows you use the SunLU6.2 Transaction Programmer's Reference verbs or the Common Programming Interface for Communications (CPI-C) calls to write APPC transaction programs (TPs) to interact with both IBM mainframe and SNA peer applications.
Page 44: Telnet 5250 And Sun 5250
Independent LU,” on page 9-2. For information on conﬁguring a dependent LU, refer to Chapter 8, “Conﬁguring Dependent LUs.” • Partner LU for the local LU. For more information, refer to Section 9.2, “Conﬁguring a Partner LU,” on page 9-4. 1-18 SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 45: Other Sun Sna Clients
• Session mode for the LU-LU pair. For more information, refer to Section 9.3, “Conﬁguring the Session Mode,” on page 9-7. • LU6.2 users that can access the local LU. For more information, refer to Section 9.4, “Conﬁguring an LUType 6.2 User,” on page 9-12. •...
Page 46 For more information on creating manager systems, refer to Section 11.3.2, “Adding a Manager System,” on page 11-9. 1-20 SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 47: Peer-To-Peer Operations
1.11 Peer-to-Peer Operations The Sun PU2.1 SNA Server supports peer-to-peer operations between a PU2.1 device and either a PU4 or PU5 device or another PU2.1 device, as follows: • PU4 or PU5 device - The physical connection between the PU2.1 device and a PU4 or PU5 device, such as a 3745 communications controller or an ES/9000 mainframe, can be through any of the supported connection types.
Page 48 1-22 SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 49: Using The Administration Program
Using the Administration Program This chapter contains the following sections: • Starting the SNA Server Administration Program - describes how to start the Sun Graphical Management Interface (sungmi). • Using the Main Window - describes the components of the main window. •...
Page 50 Domain Name System (DNS) domain implemented by the Sun PU2.1 SNA Server. If you do not specify a domain name, the software displays the Connect to domain dialog box. SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 51: Using The Main Window
To specify a domain name: 1. Enter the following information: Domain Name The DNS domain implemented by the Sun PU2.1 SNA Server. Note that if you enter the IP hostname or address of a system running the server, you may not connect to the primary server.
Page 52 The middle area is the progress meter, which displays the progress of operations in both text and bar form. Whenever the SunGMI is communicating with the Sun Gateway Manager (SunGMAN), SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 53: Using Sub-Windows
the progress bar displays a blue bar that moves back and forth. The right- most area indicates when messages are being sent to (Tx) and received from (Rx) the SunGMAN. • Sub-window - A window that contains domain or resource information. For information about the supported sub-windows, refer to the following section.
Page 54: Managers Window
The Applications window displays a list of application programs currently connected to the Sun PU2.1 SNA Server. The list includes all instances of the → SunGMI that are connected. Select Window Application List to display the Applications window. SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 55: Traces Window
2.3.4 Traces Window The Traces window displays information about traces currently in effect. Select → Window Active Traces List to display the Traces window. 2.3.5 Events Window The Events window displays event information about the current domain. → Select Window Event Log to display the Events window.
Page 56: Resource Window
To display the resource window for a conﬁguration, double-click the conﬁguration in the conﬁguration window. The title bar of the resource window contains the conﬁguration name and the current position in the hierarchy. Resource tree Resource table SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 57: Managing Windows
The resource window contains the following areas: • Resource tree - The left area of the resource window contains the resource tree, which shows a tree representation of the complete contents of the conﬁguration. To expand or contract elements in the tree, either double-click the element with the left mouse button (MB1) or click and hold the right mouse button (MB3) and then select Expand Entry or Contract Entry from the popup menu.
Page 58: Selecting Items
Select a menu command. For more information, refer to Section 2.6.2, “Menu Commands,” on page 2-12. • Position the mouse pointer on the appropriate resource, click and hold the right mouse button (MB3), and select the action from the popup menu. 2-10 SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 59: Toolbar Buttons
Note – Throughout this manual, whenever you are directed to initiate an action, only one of the above methods is described. In most cases, you can use any of the other methods as well. 2.6.1 Toolbar Buttons The following table describes the toolbar buttons you can use to initiate an action from the SunGMI.
Page 60: Menu Commands
Unavailable menu commands are grayed out and cannot be selected. The following sections describe the commands available for each of the menus in the menu bar. 2-12 SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 61: File Menu
2.6.2.1 File Menu Command Description Connect Connects to a domain. Disconnect Disconnects from a domain. Open Opens a conﬁguration. Close Closes a conﬁguration. Save Saves a conﬁguration. Save As Saves a conﬁguration with a new name. Exit Exits the program. 2.6.2.2 Edit Menu Command Description...
Page 62 12-17. Enable Enables a disabled dependent LU. Disable Disables a dependent LU without affecting sessions or client connections. Forced Disable Disables a dependent LU, destroying sessions and client connections. 2-14 SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 63: Options Menu
2.6.2.4 Options Menu Command Description Table Formats Allows you to modify the format of a resource table in a resource window. For more information, refer to Section 12.1.1.2, “Customizing a Table Format,” on page 12-2. Save settings Saves any settings you changed in this session. 2.6.2.5 Window Menu Command Description...
Page 64: Using Dialog Boxes
You specify the setting of a parameter either by entering data into a text box, by selecting an item from a drop-down menu, or by checking/clearing a check box. Dialog boxes also contain action buttons. The action buttons are described in the following table. 2-16 SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 65: Table 2-3 Dialog Action Buttons
Table 2-3 Dialog Action Buttons Button Action Accept the parameter settings. Cancel Exit the dialog box without accepting the parameter settings. Reset Return all parameters to their initial default settings. Advanced Display the Advanced dialog box. Basic Display the Basic dialog box. Help Display the contents of the Help system for the object.
Page 66 2-18 SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 67: Getting Started
Getting Started This chapter contains the following sections: • Overview of Configuration Tasks - a list of the tasks required to get you up and running with the Sun PU2.1 SNA Server as quickly as possible. • Starting the SunGMAN - describes how to start the Sun Gateway Manager. •...
Page 68: Overview Of Conﬁguration Tasks
2. Update the Domain Name System (DNS) conﬁguration, if necessary. Refer to Section B.3, “Updating the DNS Conﬁguration,” on page B-5. 3. Install any required communication hardware and software. Refer to the appropriate Sun PU2.1 SNA Server Planning and Installation Guide. SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 69: Starting The Sungman
4. Install the Sun Gateway Manager (SunGMAN) and Sun Graphical Management Interface (SunGMI) software. Refer to the appropriate Sun PU2.1 SNA Server Planning and Installation Guide. 5. Install the Sun PU2.1 SNA Server software on the system that contains the communication hardware that connects to your IBM SNA environment.
Page 70: Starting The Sungmi
Managers List to display the list of the manager systems that are deﬁned for config1 → 3. Select Edit New Manager from the menu bar to display the Create Manager dialog box. SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 71: Conﬁguring A System
4. In the Host ﬁeld, enter the hostname of the machine on which you installed the SunGMAN software. 5. Typically, you can leave the default settings for the remaining parameters. If you want to change any of the other parameters, refer to Section 11.3.2, “Adding a Manager System,”...
Page 72: Adding A Pu2.1 Server
(including @, #, and $). Tabs and spaces are not allowed. The ﬁrst character cannot be a number. The name cannot be the same as any other PU2.1 server name. SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 73: Adding A Connection
6. In the CP Name ﬁeld, enter either the CP Name assigned by your IBM network administrator or the name you entered in the Name ﬁeld. 7. Click Advanced, tab to the SunOp Service ﬁeld, and enter sunadmin_pu2 if necessary. (Note that is the name of the service added to sunadmin_pu2 the database during installation.)
Page 74 2. Double-click the PU2.1 server name to open its subordinate entries. 3. Click SDLC Lines in the resource tree. → → 4. From the main window, select Edit SDLC Line to display the Create SDLC Line dialog box. SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 75 5. In the Line Name ﬁeld, enter a name for the new SDLC line. The name can contain up to eight alphanumeric characters (including @, #, and $). Tabs and spaces are not allowed. The ﬁrst character cannot be a number. The name cannot be the same as any other connection name.
Page 76: Adding A Pu
DLC (PU2) to display the Create DLC dialog box. Note – The dialog box shown is for a LAN connection. The parameters available for SDLC, QLLC, and channel connections may vary. 3-10 SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 77: Adding A Dependent Lu
4. In the DLC Name ﬁeld, enter the name for the new PU. The name can contain up to eight alphanumeric characters (including @, #, and $). Tabs and spaces are not allowed. The ﬁrst character cannot be a number. Lowercase letters are converted to uppercase.
Page 78 Basic and Advanced dialog boxes. If you want to change any of the other parameters, refer to Chapter 8, “Conﬁguring Dependent LUs." 7. Click OK to add the dependent LU. 3-12 SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 79: Saving The New Conﬁguration
3.4.7 Saving the New Conﬁguration To save the new conﬁguration: → 1. From the main window, either select File Save to save the conﬁguration → as config1 or select File Save As to save the conﬁguration with a new name. The screen displays the Save dialog box. 2.
Page 80 3-14 SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 81: Conﬁguring Systems
Conﬁguring Systems This chapter describes how to conﬁgure the systems that make up your Sun PU2.1 SNA Server. Before you begin, identify the systems that provide connectivity into your SNA network and deﬁne the distribution of functions among these systems. Use the hardware and software conﬁguration planning forms in Appendix A, “Resource Planning Forms,”...
Page 82: Basic System Conﬁguration
The platform on which the servers run. This setting assures that platform- speciﬁc parameters are controlled correctly. Select Generic for unsupported platforms. Sun recommends that you always select an appropriate platform and that you do not select the Generic option. SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 83: Advanced System Conﬁguration
4.2 Advanced System Conﬁguration Initial Status The initial status of the system when it is initialized. The value can be Active or Inactive. If you select Active, the Sun System Manager (sunsman) is activated when the system is initialized. If you select Inactive, you must manually activate the sunsman.
Page 84: Table 4-1 Command Line Options
Set the time sunsman should wait for a response when attempting to acquire an LU from a PU2.1 server to number_seconds. 1. Do not use this command line option unless you are instructed to do so by Sun Technical Support. SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 85: Using Appc File Transfer Protocol
Enable AFTP Server? Indicates whether the AFTP (APPC File Transfer Protocol) server functions are enabled. Check the box to enable the AFTP server. Clear the box to disable the AFTP server. Note – This parameter is available only if you have conﬁgured a partner LU. For more information, refer to Section 9.2, “Configuring a Partner LU,”...
Page 86: Sample Setup For Vm/Esa
ConWinner and ConLoser: for example, 4 of each is typical. 4. Conﬁgure the AFTP LU 6.2 Deﬁnition in VTAMLST: T015L000 LU LOCADDR=0, DLOGMOD=SNASVCMG 4.3.1 Sample setup for VM/ESA 1. Set up a UserID for AVSVM, which provides the APPC Support under SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 87 USER AVSVM AVSVM 32M 64M BG * AVS virtual machine INCLUDE GCSPROF ACCOUNT 7 P390 IUCV ANY IUCV *IDENT GATEANY GATEWAY REVOKE IUCV ALLOW OPTION COMSRV MAXCONN 20 ACCT CONSOLE 01F 3215 T OPERATOR LINK MAINT 193 193 RR MDISK 191 FB-512 16 3504 AVSVM MR ALL...
Page 88 * Configurator generated USERID Fri Nov 22 10:53:49 1996 INCLUDE USERPROF IPL CMS PARM AUTOCR LINK 5654025 LINK 5654025 MDISK 191 FB-512 16 AFT191 MR ALL 5. Set up the AFTPD Proﬁle Exec: SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 89 'SP CONS START CL A MAINT' ; 'ACC 2C2 B' ; 'ACC 29A C' ; 'CP SET PF12 RETRIEVE' ; 'CP SET RUN ON' ; 'SET SERVER ON' ; 'SET AUTOREAD OFF' ; 'SET FULLSCREEN OFF' ; 'EXEC AFTPD' ; 'EXIT ;...
Page 90: Connecting To The Sunlink 9.1 Aftp Client And Transferring Files
230 User user_id logged in. ftp> Note that the ftp is to the SunLink System. SunLink supports only one AFTP Client per System. 4. Use remotehelp to get help information from the host: 4-10 SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 91 ftp> remotehelp 214-The following commands are recognized (* =>'s unimplemented). USER APPE* DELE XRMD PASS MLFL* ACCT* MAIL* XCWD XPWD SMNT* MSND* LIST CDUP REIN* MSOM* NLST XCUP QUIT MSAM* SITE STOU* PORT MRSQ* SYST AUTH* PASV MRCP* STAT ADAT* TYPE ALLO* HELP...
Page 92 200 Type set to BINARY. ftp> quote recfm v 250 RECFM set to v 4-12 SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 93: Conﬁguring Pu2.1 Servers
Conﬁguring PU2.1 Servers This chapter describes how to conﬁgure PU2.1 servers. To conﬁgure a PU2.1 server: 1. Double-click Systems in the resource tree to display a list of systems. 2. Double-click the system name in the resource tree to open its subordinate entries.
Page 94: Basic Pu2.1 Server Conﬁguration
ﬁle. Check the box if you want to /etc/passwd verify the information. Clear the box if you do not want to verify the information. This parameter is appropriate for APPC transactions only. SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 95: Advanced Pu2.1 Server Conﬁguration
For more information, refer to Section G.5, “Unix-Level Security,” on page G-5. Default User The user ID for remotely invoked APPC transaction programs. The default value is sunlu62 Note – You must add the Default User name manually (either or any sunlu62 other name you specify) to the database ﬁle.
Page 96: Table 5-1 Command Line Options
The name of the TCP/IP service that the server uses when running the sunOP troubleshooting utility. The service name must be in the NIS services database or in the database ﬁle. /etc/services SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 97 Note – If you are running multiple PU2.1 servers on the same system, the SunOP service name must be unique for each server. LU6.2 Service The name of the TCP/IP service that the server uses to provide the LU6.2 transaction program (TP) interface. The service name must appear in the NIS services database or in the database ﬁle.
Page 98 LAN connection. LLC Device The Unix pathname for the special ﬁle required for LLC. Use this parameter only when the server is operating over a LAN connection. SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 99: Conﬁguring Connections
Conﬁguring Connections This chapter contains the following sections: • Adding a LAN Connection - describes how to add a Token Ring, Ethernet, or FDDI connection. • Adding an SDLC Connection - describes how to add a Synchronous Data Link Control connection. •...
Page 100: Basic Lan Conﬁguration
An entry is required in this ﬁeld. However, if you specify an appropriate system type, a default device is automatically provided. For more information, refer to Type in Chapter 4, “Conﬁguring Systems." SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 101: Advanced Lan Conﬁguration
Local MAC Address A 12-character hexadecimal string representing the Medium Access Control (MAC) ring station address of the host machine interface. See your host network administrator for the proper setting of this parameter. You must specify the MAC address. Note – On most systems, the MAC address can be obtained from ROM on the LAN adapter.
Page 102: Adding An Sdlc Connection
Max Data in Chapter 7, “Conﬁguring PUs." 6.2 Adding an SDLC Connection To add an SDLC connection: 1. Double-click PU2.1 Servers in the resource tree to display the name of the PU2.1 server. SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 103: Basic Sdlc Conﬁguration
2. Using the right mouse button (MB3), click and hold the server name in → the resource tree and select New SDLC Line from the popup menu. The screen displays the Create SDLC Line dialog box. 3. Enter the appropriate information in the Basic dialog box and then click Advanced to display the Advanced dialog box.
Page 104: Advanced Sdlc Conﬁguration
XID messages on the link. If you select Switched, the link responds to XID requests from the host. If you select Leased, the link does not respond to XID requests from the host. SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 105: Adding A Qllc Connection
Clock Source The clock source for the synchronous line. The value can be Internal or External. The default is External. If you are using a modem, select External. If a cable directly connects the hardware running the Sun PU2.1 SNA Server and the SNA Communications Controller, the value you select depends on whether the Sun PU2.1 SNA Server provides the clocking.
Page 106: Basic Qllc Conﬁguration
A free-form text area that you can use to further qualify and describe the name or provide additional information. Connection Type The connection type. The value can be Permanent VC (virtual circuit) or Switched VC. SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 107: Advanced Qllc Conﬁguration
Accept Incoming Calls? Indicates whether the server should accept incoming switched VC calls. Check the box if you want the server to accept incoming calls. Clear the box if you do not want the server to accept incoming calls. Host DTE Address The X.25 PSDN address of the NPSI system.
Page 108: Index
X.25 call request RPOA selection facility and represent the Data Network Identiﬁcation Code (DNIC) addresses of the preferred RPOAs. You enter a string of up to 24 characters (up to 6 non-separated, 4-digit RPOA codes). 6-10 SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 109 IP Host The name of the host that is running the sunX25 server. The default is the local host. Max Connects The number of times the server tries to connect to the sunX25 server before declaring the QLLC line inoperative. This setting applies only to the console of the sunX25 server.
Page 110 6-12 SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 111: Conﬁguring Pus
Conﬁguring PUs This chapter describes how to conﬁgure physical units (PUs). To add a PU to a connection: 1. Double-click the PU2.1 server name in the resource tree to open its subordinate entries. 2. Double-click the appropriate connection icon (LAN Connections, SDLC Lines, or QLLC Lines) to display the name of the connection.
Page 112: Basic Dlc (Pu2) Conﬁguration
7.1 Basic DLC (PU2) Conﬁguration LAN Connection SDLC or QLLC Connection Channel Connection SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 113 DLC Name The name that identiﬁes the physical unit. The name can contain up to eight alphanumeric characters (including @, #, and $). Tabs and spaces are not allowed. The ﬁrst character cannot be a number. Lowercase letters are converted to uppercase. You must specify the name of the physical unit. The name cannot be the same as any other PU, dependent LU, independent LU, or LU pool name.
Page 114: Advanced Dlc (Pu2) Conﬁguration
7.2 Advanced DLC (PU2) Conﬁguration Figure 7-1 LAN Connection SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 115 Figure 7-2 SDLC or QLLC Connection Group LSAP for PU A 2-digit hexadecimal string representing the group Service Access Point (SAP) for this PU. The default is x’05’. This parameter is available only for LAN connections. Local LSAP for PU A 2-digit hexadecimal string representing the SAP for this PU in increments of x’04’.
Page 116 PU in the network. Refer to Local Terminal ID for a list of supported devices. If speciﬁed, this value is used to validate the incoming XID. The connection is not established if the values do not match. If not speciﬁed, validation is not performed. SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 117 Remote CP Name A name that is used to verify the incoming XID. The format of the Remote CP Name is netid.netname, where netid is the returned ID of the SNA network and netname is the name of the server within the SNA network. Each ﬁeld can contain up to eight alphanumeric characters (including @, #, and $).
Page 118 30. This value is used in XID poll time-outs for peer-to-peer connections for PU2.1. PMaximum Retries The maximum number of consecutive retries to attempt before declaring an error. The value can range from 1 to 255. SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 119 Ack Count The number of acknowledged incoming frames to be received before the dynamic window is incremented. The value can range from 1 to 127. This parameter is available only for LAN connections and should be modiﬁed only for complex networks that are having problems with IBM Token Ring bridge products.
Page 120 7-10 SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 121: Conﬁguring Dependent Lus
Conﬁguring Dependent LUs This chapter contains the following sections: • Adding Dependent LUs - describes how to conﬁgure a single dependent logical unit (LU) or multiple dependent LUs. • Modifying Dependent LUs - describes how to modify a single dependent LU or a group of multiple LUs.
Page 122: Adding Dependent Lus
Basic and Advanced dialog boxes. 6. To accept the settings, click OK. To exit a dialog box without accepting the settings, click Cancel. To return to the default settings, click Reset. SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 123: Basic Dependent Lu Conﬁguration
8.1.1 Basic Dependent LU Conﬁguration Name The network name of a single dependent LU or a group of dependent LUs, as deﬁned by the host network administrator. The name can contain up to eight alphanumeric characters (including @, #, and $). Tabs and spaces are not allowed.
Page 124 Note that the addresses generated for additional LUs in a group of multiple LUs are sequential, starting with the Base LOCADDR. If the addresses assigned by your host administrator are not sequential, you must modify the SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 125 numbers of individual LUs after they have been created. For more information on modifying dependent LUs, refer to Section 8.2, “Modifying Dependent LUs,” on page 8-8. Number of LUs The number of LUs you want to add. For a single LU, use the default value of 1. For a group of multiple LUs, the value can range from 1 to 254.
Page 126: Advanced Dependent Lu Conﬁguration
The ﬁrst character cannot be a number. Lowercase letters are converted to uppercase. Enable TCP/IP Keepalive Indicates whether to enable the TCP/IP keep-alive socket option. Check the box to enable the keep-alive option. Clear the box to disable the keep-alive option. SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 127 Note – The setting of this parameter is overridden by the equivalent setting in the user record. For more information about setting this parameter in the user record, refer to Section 10.1.2, “Advanced User Record Conﬁguration,” on page 10-3. PU2.1 Keepalive Timer The time interval (in minutes) at which the Sun PU2.1 SNA Server sends keep- alive signals to the client.
Page 128: Modifying Dependent Lus
LUs, you cannot change the Base LOCADDR parameter. 5. To accept the settings, click OK. To exit a dialog box without accepting the settings, click Cancel. To return to the default settings, click Reset. SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 129: Deleting Dependent Lus
8.3 Deleting Dependent LUs To delete a single dependent LU or a group of dependent LUs: 1. Click the PU name in the resource tree to display the list of dependent LUs. 2. Select the dependent LU(s) you want to delete. For more information on selecting multiple dependent LUs, refer to Section 2.5, “Selecting Items,”...
Page 130 Note – Access control is not applicable to LUType 6.2. 4. To accept the settings, click OK. To exit a dialog box without accepting the settings, click Cancel. To return to the default settings, click Reset. 8-10 SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 131: Modifying An Lu Pool
8.5 Modifying an LU Pool To modify an LU pool: 1. Double-click Pools in the resource tree to display the list of LU pools. 2. Click the LU pool you want to modify to select it. → 3. Select Edit Modify from the menu bar to display the Modify Pool dialog box.
Page 132 8-12 SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 133: Conﬁguring For Lutype 6.2
Conﬁguring for LUType 6.2 This chapter contains the following sections: • Configuring an Independent LU - describes how to conﬁgure a local independent logical unit (LU). • Configuring a Partner LU - describes how to conﬁgure a partner LU for a local independent or dependent LU.
Page 134: Conﬁguring An Independent Lu
Basic and Advanced dialog boxes. 7. To accept the settings, click OK. To exit a dialog box without accepting the settings, click Cancel. To return to the default settings, click Reset. 9.1.1 Basic Independent LU Conﬁguration SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 135: Advanced Independent Lu Conﬁguration
Name The name of the local independent LU. The name can contain up to eight alphanumeric characters (including @, #, and $). Tabs and spaces are not allowed. The ﬁrst character cannot be a number. You must specify the LU name.
Page 136: Conﬁguring A Partner Lu
Note – Before you can conﬁgure a partner LU, you must conﬁgure either a local dependent LU or a local independent LU. To conﬁgure a partner LU: 1. Double-click the PU2.1 server name to open its subordinate entries. SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 137: Basic Partner Lu Conﬁguration
→ → 2. From the main window, select Edit Partner LU to display the Create Partner LU dialog box. 3. Enter the appropriate information in the Basic dialog box and then click Advanced to display the Advanced dialog box. The following sections describe the parameters in the Basic and Advanced dialog boxes.
Page 138: Advanced Partner Lu Conﬁguration
Lowercase letters are converted to uppercase. The default Uninterpreted Name is the partner LU name. Note – This parameter applies only to dependent LU sessions on the INIT- SELF and TERM-SELF. SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 139: Conﬁguring The Session Mode
Session Init Type The type of session that the SSCP initiates with this partner LU (Init Only or Init or Queue). Use Init Only if you do not want the INIT-SELF that is sent to the SSCP to be queued. Use Init or Queue if the SSCP can queue the INIT-SELF until the partner LU becomes available.
Page 140: Basic Session Mode Conﬁguration
The ﬁrst character cannot be a number. Lowercase characters are converted to uppercase. The mode name on the local LU must match the mode name on the partner SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 141: Advanced Session Mode Conﬁguration
DLC Name The name of the data link connection (PU) associated with the mode. Use Local to specify an intranode mode. In this case, symmetric deﬁnitions are required for the local LU and the partner LU. The association between mode and DLC is related to the Class of Service (COS) required.
Page 142 The value can range from 0 to 127. This parameter is available only if both parallel sessions and CNOS are supported for the partner LU. For more information, refer to Parallel Sessions Supported? and CNOS Supported?. 9-10 SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 143 Maximum Sessions The maximum number of sessions over this mode. The default equals Min Contention Winners + Min Contention Losers. This parameter is available only if both parallel sessions and CNOS are supported for the partner LU. For more information, refer to Parallel Sessions Supported? and CNOS Supported?.
Page 144: Conﬁguring An Lutype 6.2 User
Note – If the Use UNIX Security? parameter is enabled for the PU2.1 server, you do not have to specify a password here. Received passwords will be veriﬁed against the Unix ﬁle. If the Use UNIX Security? /etc/passwd 9-12 SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 145: Conﬁguring A Transaction Program
parameter is disabled for the PU2.1 server, you must specify a password here. For information, refer to Section 5.1, “Basic PU2.1 Server Conﬁguration,” on page 5-2. Profile List The names of the proﬁles to be used for conversation-level security veriﬁcation. You can specify up to 16 proﬁle entries for each LUType 6.2 user. Separate each proﬁle name with a comma.
Page 146 The name of the local LU. Select Any if the TP can run with any pair of LUs. Command Path The complete command line used to start the TP process. Sun recommends that you specify the command with an absolute pathname. 9-14 SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 147: Advanced Transaction Program Conﬁguration
9.5.2 Advanced Transaction Program Conﬁguration Initial Status The initial status of the transaction program. The value can be Enabled, Temporarily Disabled, or Permanently Disabled. Security Verification The security veriﬁcation that is performed on incoming Attach requests. The values are described below: Security Veriﬁcation Description...
Page 148 Indicates whether the TP supports incoming Attach requests for basic conversations. Check the box if the TP supports basic conversations. Clear the box if the TP does not support basic conversations. 9-16 SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 149 Mapped Conv Allowed? Indicates whether the TP supports incoming Attach requests for mapped conversations. Check the box if the TP supports mapped conversations. Clear the box if the TP does not support mapped conversations. PIP Data Allowed? Indicates whether Attach requests containing PIP data are supported by the TP. Check the box if the TP supports PIP data.
Page 150: Conﬁguring A Tp Resource Access List
LUType 6.2 user. For more information, refer to Proﬁle List. 6. To accept the settings, click OK. To exit a dialog box without accepting the settings, click Cancel. To return to the default settings, click Reset. 9-18 SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 151: Conﬁguring Users
Conﬁguring Users This chapter contains the following sections: • Deﬁning a User Record - describes how to deﬁne a user record. • Setting up a User Group - describes how to set up a user group. • Managing Users and Groups - describes how to modify or delete a user record, how to delete a user from a group, and how to delete access to a dependent LU from a user or user group.
Page 152: Basic User Record Conﬁguration
You can specify multiple resources and mix types of resources. If you specify multiple resources, enter them in the order in which you want them considered and separate each resource name with a space. For example, if you want the 10-2 SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 153: Advanced User Record Conﬁguration
software to use the dependent LU if it is available, and if DEPLU02 DEPLU02 not available, you want the software to use any LU in the LU pool , enter POOL1 in the ﬁeld. DEPLU02 POOL1 The name of each resource can have up to 8 characters. You can enter a total of 256 characters in the ﬁeld.
Page 154 (MAC) address. Note that each pair of hexadecimal characters is separated by a colon, such as . This parameter is available only if the 00:00:c0:d5:4b:7c Client Address Type is IPX Address. 10-4 SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 155 Privileges A command that determines the resources that a user can access. The format of the command for a system/network administrator (operator) is oper=(resource_specifier [, resource_specifier ]... ) where resource_speciﬁer indicates the top-level resource in the active conﬁguration that the operator can conﬁgure and control. For example, if resource_speciﬁer indicates a particular PU, the operator can conﬁgure and control the PU and any LUs deﬁned under the PU.
Page 156 LU session, and the LU becomes available for another client connection. Note – The setting of this parameter overrides the equivalent setting in the dependent LU conﬁguration. For more information, refer to Section 8.1.2, “Advanced Dependent LU Conﬁguration,” on page 8-6. 10-6 SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 157: Setting Up A User Group
No Session Idle Timeout The idle time-out period for connections between the client and the host when the client is attached to an LU but has not yet gone into session by starting an application. If no application is started during the speciﬁed time period, the LU is freed and becomes available for another client connection.
Page 158: Managing Users And Groups
Modify from the menu bar to display the Modify User dialog box. 4. Modify the user record, as necessary. For information about the meaning of the parameters, refer to Section 10.1, “Deﬁning a User Record,” on page 10-1. 10-8 SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 159: Deleting A User Record
5. To accept the settings, click OK. To exit a dialog box without accepting the settings, click Cancel. To return to the default settings, click Reset. Note – You must modify a user record if you delete the resource speciﬁed in the Default Resource parameter.
Page 160: Deleting Access To A Dependent Lu
5. To accept the settings, click OK. To exit a dialog box without accepting the settings, click Cancel. To return to the default settings, click Reset. 10-10 SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 161: Managing The Server
Managing the Server This chapter contains the following sections: • Controlling Access to the Sun PU2.1 SNA Server - describes how to control access to the Sun PU2.1 SNA Server by clients (users) and by operators (system/network administrators). • Managing Licenses - describes how to add and delete license information. •...
Page 162: Controlling Client Access
LU depends on whether the client speciﬁes the name of the LU or the name of the LU pool that the LU is in. Refer to the following ﬂow diagram. 11-2 SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 163 Client LU has Client speciﬁes access control list? listed? LU pool Client has access control list? listed? Both LU and Client LU pool have speciﬁc empty access control list? ACCESS DENIED LU pool ACCESS has empty access GRANTED control list ACCESS DENIED Managing the Server...
Page 164: Figure 11-1 Controlling Client Access
In the following ﬁgure, clients at Acme Corp. can access LUs in POOLA only. Clients in Bonzo Inc. can access LUs in POOLB only. Figure 11-1 Controlling Client Access 11-4 SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 165: Controlling Operator Access
To display a list of the client connections to each system, double-click System in the resource tree, double-click the system name, and then click Client Connections. Refer to the following Figure 11-2. Figure 11-2 Displaying Client Connections 11.1.2 Controlling Operator Access The Sun PU2.1 SNA Server supports the following types of operators (system/network administrators): •...
Page 166: Managing Licenses
You may have to add licenses to allow additional client connections. You may have to delete licenses if they have expired or before adding new licenses. The following sections describe how to add and delete licenses. 11-6 SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 167: Adding A License
11.2.1 Adding a License To add a new license: Note – Before adding a new license, make sure that you get all the necessary information from the Sun licensing center. → 1. Select Window Licenses List to display the Licenses window. 2.
Page 168: Deleting A License
If you have only two manager systems, set one of them to be the preferred primary manager system. The primary manager system will continue to operate as a primary manager system even if the second manager system 11-8 SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 169: Adding A Manager System
fails. Note, however, that if the primary manager system fails, the second manager system will not be able to take over as the primary manager system. • If the Sun PU2.1 SNA Server running in multiple physical sites, deﬁne one manager system for each physical site.
Page 170: Recovering From A Loss Of Quorum
1. Restart the SunGMI by entering the following command at the shell prompt. sungmi & Do not specify the domain name in the command line. This ensures that the screen displays the Connect to domain dialog box. 11-10 SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 171: Managing The Active Conﬁguration
2. In the Domain Name ﬁeld of the Connect to domain dialog box, enter the TCP/IP hostname of one of the manager systems that is up and running. Do not enter the name of the domain. If you enter the domain name when a quorum of manager systems is not available, the SunGMI may not connect to the manager network.
Page 172: Modifying The Active Conﬁguration
If you selected multiple resources, parameters that cannot be modiﬁed are grayed out. 5. To accept the settings, click OK. To exit the dialog box without accepting the settings, click Cancel. To return to the default settings, click Reset. 11-12 SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 173: Saving Changes To The Active Conﬁguration
11.4.2 Saving Changes to the Active Conﬁguration To save changes to the active conﬁguration: → 1. Select File Save. The screen displays the Save Type dialog box. 2. Select one of the following options to specify how you want the updates to be applied to the active conﬁguration: Wait for servers to become idle - If a modiﬁed server still has active client connections, the software sets the state of the server to Draining.
Page 174: Creating An Off-Line Conﬁguration
4. To accept the settings, click OK. An exact copy of the existing conﬁguration is created under the new name. To exit a dialog box without accepting the settings, click Cancel. To return to the default settings, click Reset. 11-14 SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 175: Modifying An Off-Line Conﬁguration
5. Save the conﬁguration by highlighting the conﬁguration in the → conﬁguration window and then selecting File Save from the menu bar. 11.5.2 Modifying an Off-line Conﬁguration Note – Only one operator can make changes in a particular system at a particular time.
Page 176: Making An Off-Line Conﬁguration Active
The off-line conﬁguration information is downloaded to each of the systems and PU2.1 servers deﬁned in the off-line conﬁguration, and the systems and PU2.1 servers are started if their initial status is set to Active. 11-16 SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 177: Controlling The Status Of Resources
11.6 Controlling the Status of Resources You can control the status of resources in the active conﬁguration, as follows: • You can specify the initial status of systems and PU2.1 servers (Active or Inactive). If you select Active, the system or PU2.1 server is activated when the system is initialized.
Page 178: Table 11-1 Stop And Start Results By Resource Type
Makes the dependent LU unavailable. Existing sessions and client connections are not affected. Forced Makes the dependent LU unavailable. Existing Disable sessions and client connections are destroyed. Enable Makes the dependent LU available for client connections. 11-18 SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 179: Troubleshooting
Troubleshooting This chapter contains the following sections: • Diagnostic Tools - describes the diagnostic tools provided by the Sun PU2.1 SNA Server to help you and the Sun Technical Support staff determine the cause of any problems you may encounter. •...
Page 180: Resource Information Tables
12.1.1.2 Customizing a Table Format To customize the format of a conﬁguration, status, or RTM table: → 1. Select Options Table Formats to display the Table Formats dialog box. 12-2 SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 181 2. Enter the following information: Select Format The type of table format you want to modify. You can select one of the preset table formats or you can click New to create a new table format. Clicking New displays the Create Format dialog box. In the Format Name ﬁeld, you can enter a name for the new format and click OK.
Page 182 Display Status. For example, if you select a server, the software displays information about all the servers conﬁgured on the system. If you select a LAN connection, the software displays information 12-4 SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 183: Table 12-1 Status Table Mib Variables
about all the PUs conﬁgured on that LAN connection. The particular information displayed and the headings used for that information depend on the way you set up your status table format. For more information, refer to Section 12.1.1.2, “Customizing a Table Format,” on page 12-2. The following table describes the MIB variables that you can use in a status table for each of the supported resources.
Page 184 (fields that cannot handle the MAXPDU). lanStatsRcvSize The number of frames received since start-up with length exceeding the maximum frame size. lanStatsRcvAllocb The number of receive buffer allocation failures since start-up. 12-6 SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 185 Table 12-1 Status Table MIB Variables (3 of 9) Resource MIB Variable Description lanStatsRcvCanput The number of receive upstream connection congestion errors since start-up. (cont.) lanStatsMsgsSent The number of packets transmitted since start-up. lanStatsCharsSent The number of bytes transmitted since start-up.
Page 186 The number of frames received since start-up with CRC errors. sdlcStatsRcvSize The number of frames received since start-up with length exceeding the maximum frame size. sdlcStatsRcvFA The number of aborted frames received since start-up. 12-8 SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 187 Table 12-1 Status Table MIB Variables (5 of 9) Resource MIB Variable Description SDLC sdlcStatsRcvOvr The number of receiver overrun connection frames received since start-up. (cont.) sdlcStatsRcvAllocb The number of receive buffer allocation failures since start-up. sdlcStatsRcvCanput The number of receive upstream congestion errors since start-up.
Page 188 PU, a client SNA program is attached to the PU port, and the SSCP-PU session is active. pu2ConfigStatus The current configuration status of the PU. The value can be Default, Added, Modified, or Deleted. 12-10 SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 189 Table 12-1 Status Table MIB Variables (7 of 9) Resource MIB Variable Description PU (cont.) pu2StatsMsgsSent The total number of information frames transmitted by this link station since start-up. pu2StatsCharsSent The total number of information frame (data and control) bytes transmitted by this link station since start-up.
Page 190 The number of PIUs received on the LU-LU session since the session was activated. luSessOutBRuCharCnt The number of Request Unit (RU) characters received on the LU-LU session since the session was activated. 12-12 SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 191 Table 12-1 Status Table MIB Variables (9 of 9) Resource MIB Variable Description Dependent luSessStartTime The time the LU-LU session was LU (cont.) activated. luAvailStatus Indicates whether the dependent LU is currently available for administrative purposes. luUserName The name of the user currently attached to the dependent LU.
Page 192 For more information, refer to Section 12.1.1.2, “Customizing a Table Format,” on page 12-2. The following table describes the MIB variables that you can use in an RTM table for dependent LUs. 12-14 SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 193: Table 12-2 Rtm Table Mib Variables
Table 12-2 RTM Table MIB Variables (1 of 2) MIB Variable Description luRTMActive Indicates whether NetView has activated RTM for this 3270. The value can be Yes or No. luRTMSendOnOv Indicates whether the Sun PU2.1 SNA Server will send RTM statistics if any of its counters overﬂow. The value can be Yes or No.
Page 194: Event Log
Use this utility to capture a line trace of problem scenarios for subsequent diagnosis. The following sections describe how to conﬁgure your system for line tracing, how to start a line trace, and how to read the output of a line trace. 12-16 SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 195 12.1.3.1 Conﬁguring Your Systems for Line Tracing The Sun Graphical Management Interface (SunGMI) starts the Sunscope utility on the selected server’s system by invoking the Unix remote shell ( command. Each operator who wants to run the Sunscope utility must be allowed to remotely access the server systems from the systems on which they run the SunGMI.
Page 196 If you do not enter a ﬁle name, the data is displayed only on the screen. Note – Output log ﬁles can grow very quickly, so choose a ﬁle system with sufﬁcient free space. 12-18 SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 197: Table 12-3 Sunscope Command Line Options
Sunscope Options The command line options that you can use when activating the Sunscope utility. Separate command line options with a space. Valid command line options are as follows: Table 12-3 Sunscope Command Line Options Options Description Display hexadecimal numbers as EBCDIC characters. Required for all LAN devices (IBM Token Ring, Ethernet, FDDI).s Required for channel devices on Integrated Gateway...
Page 198 Separate command line options with a space. The following table lists some valid command line options. Use the command to display a man xterm complete list of command line options. 12-20 SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 199: Table 12-4 Xterm Command Line Options
Table 12-4 xterm Command Line Options Command Line Options Description Jump scroll. Enable scroll bars. -sl number Save the last number lines of output. For example, to save the last 1,000 lines of output, enter -sl 1000. -geometry columnxline Create a window that is column columns wide and line lines high.
Page 200 *-----> scope log data for line: /dev/ttys0 <-----* # Host sends connect request (SNRM) to our # station (c1). We respond (UA). R:c193 S:c173 # 4 digit messages ending in 1 are Receiver Ready # messages (RR). R:c111 12-22 SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 201 S:c111 # Host sends activate PU (ACTPU=11) request. # We respond. R:c1002d00000001e9 6b80001102010500 00000004 A..Z,.. R:c111 S:c1202d00000001e9 eb80001111404040 4040404040000007A..Z..01000000000000 ..S:c131 # Host sends activate LU (ACTLU=0d) requests. R:c1222d00020001ed 6b80000d0201 A..,..R:c1242d00030001ee 6b80000d0201 A..,..R:c1262d00040001ef 6b80000d0201 A..,..# Host may send other types of messages like # this Response Time Monitor (RTM) request # (NMVT=41038d).
Page 202 S:c1402c0000020002 838000 A ..c.. S:c151 R:c131 S:c151 # Host sends BIND request (BIND=31) and # we respond. R:c1242d00020101f0 6b800031010303b1 903080000187c701A..0,..gG. 0002000000000018 5000007e000005c3 d5d4f0f100 ..&..=...CNM01. R:c131 S:c1622d00010201f0 eb800031 A..0..S:c171 R:c151 S:c171 12-24 SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 203 ﬁrst, followed by XID polling after the route is determined. The sample Token Ring output is continued below. Comments are in italics. (C) Copyright 1997 Sun Microsystems, Inc. *-----> scope log data for line: /dev/nit <-----* # sunPU21 is sending out route determination...
Page 204 ..` ..# For sun3270, the host sends a login banner. # First piece, some removed. R:4000246835794000 1234567804040404 2c00020000010380..` .... 00e6c5d3c3d6d4c5 40e3d640e3c8c540 c9c2d440e3c5e2e3 .WELCOME TO THE S:4000123456784000 2468357904040406 002c000002000187..`..g 900008310000 ..12-26 SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 205: Pu2.1 Server Trace
R:4000246835794000 1234567804050106 ..` ..# Host sends a disconnect command # we respond. R:4000246835794000 12345678040453 ..` ..S:4000123456784000 24683579040573 ..`... 12.1.4 PU2.1 Server Trace The Sun PU2.1 SNA Server allows you to activate up to 32 internal traces on each PU2.1 server.
Page 206 ﬂags. If you want to use other values, contact X’ffffffff’ the Sun Technical Support staff for assistance. Output File (traceFileName) The full pathname of the trace ﬁle on the target system. You must enter an output ﬁle name. 12-28 SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 207 Start Time (traceStartTime) The time to start the trace in the format HH.MM.SS. The default is Now. Duration (traceDuration) The length of time in seconds that you want the trace to run. (When the trace ﬁle becomes full, the trace ends even if the speciﬁed time has not elapsed.) Records Per File (traceNumTracePts) The number of trace points to write to the trace ﬁle.
Page 208: Lu Information Screen
For more information on how to specify the AID key, refer to the 3270 Help Screen Display Key deﬁnition in Section 11.5.1, “Creating an Off-line Conﬁguration,” on page 11-14. The following ﬁgure shows a sample LU information screen. 12-30 SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 209: Figure 12-1 Sample Lu Information Screen
LU Name: NLU2 Client Address: 199.97.127.56:42491 Server Address: 199.97.127.56:8023 Connect Time: Mon Jan 27 14:26:15 1997 LU Status: Active Session User Name: TESTUSER Pool Name: Not Available Current AID for LU address information is: PF1 Press ENTER to return to previous screen or press another AID key to use for LU address information prompting during this session.
Page 210: Error Messages
The release notes are located in the installation directory ( , by default) and can be /opt/SUNWpu21 displayed by selecting Release Note from the Help menu. 12-32 SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 211: The Sungmi Does Not Start
12.3.1 The SunGMI Does Not Start If you are using Solaris, the SunGMI will not run unless the Motif Runtime package is installed and you have the environment variable LD_LIBRARY_PATH deﬁned to include the directories that contain the Motif shared libraries. These directories are normally /usr/openwin/lib /usr/dt/lib...
Page 212: The Suncpd Process Is Not Running
For a description of the port names and values needed, refer to the installation log ﬁle in the product installation directory. 12-34 SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 213: The Sun Pu2.1 Sna Server Conﬁguration Does Not Start Automatically
12.3.5 The Sun PU2.1 SNA Server Conﬁguration Does Not Start Automatically If the SunGMAN process is installed correctly and starts, but does not initialize the conﬁgured systems and servers at start time, the manager network may have 50% or fewer of the conﬁgured managers active. SunGMAN will wait until at least 50% are active before activating the conﬁguration.
Page 214: Connection Loops
• For SDLC, verify that the Station Address matches the IBM Addr parameter. • The IBM PU is not active. 12.3.10 Client Connections Are Failing If a client connection fails, try one of the following: 12-36 SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 215: Service Name Parameters
• Check the Events window of the SunGMI. If no event messages are listed, verify that the client can establish a TCP/IP connection to the SunGMAN system. Enter the command , where machinename is the ping machinename system running the SunGMAN software. •...
Page 216: Getting Help
• Analysis of network performance. • Customized setup of the Sun LU6.2 and Sun LU0 features. • Diagnostics for Sun LU6.2 program failures. To contact Professional Services, call your Service Representative. 12-38 SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 217: Resource Planning Forms
Resource Planning Forms Before you begin designing your network, you should answer the following: • How many users will need a connection to the network? • How many LUs are needed? • How many servers are needed? • How are users connected to your TCP/IP network today? •...
Page 218: Communication Devices
A.5 Installation Utilities • Solaris - Use pkgadd to install each product. A product may contain multiple packages. pkgadd prompts for drivers to be installed. A.6 Domain Planning Form Domain Name: Status: Connections: SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 219: Remote Systems To Connect To
Domain Name: A.7 Remote Systems to Connect to A.8 Manager Planning Form Host: Comment: A.9 Server Planning Forms A.9.1 General Information Name: CP Name: Initial Status: Command Options: Comment: Resource Planning Forms...
Page 220: Lutype 6.2 Parameters
A.9.3 LLC Parameters Use Source Routing? Table Size: Time-out: Retries: Time to Live: Max PDU Size: LLC Device: A.10 System Planning Form A.10.1 General Information Host: Comment: Platform Type: Initial Status: Command Options: SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 221: Independent Lus
A.10.2 Independent LUs Name: Comment: Session Limit: Allow Partner LU to Queue BIND Rep? Sync Level SYNCPT Supported? A.10.3 Dependent LUs Name: Network Qualiﬁed Name: LU Type: Base LOCADDR: Number of LUs: Pacing Window: Pool Name: Associated Printer: A.10.4 Partner LUs Partner LU Name: Network Qual Name: Uninterrupted Name:...
Page 222: Transaction Programs
Command Path: Initial Status: Security Veriﬁcation: Maximum Instances: Command Path: Basic Conversations Allowed? Mapped Conversations Allowed? PIP Data Allowed? Sync None Allowed? Sync Conﬁrm Allowed? Sync SYNCPT Allowed? Pass FMH Data to TP? SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 223: Sdlc Lines
CNOS Verbs Allowed? Session Control Verbs Allowed? Display Verbs Allowed? Service TPs Allowed? A.10.6 SDLC Lines Line Name: Comment: Device: Special Device: Max Rcv Frame: Duplex: Line Type: Clock Source: Line Speed: Poll Pause Timer: Monitor Carrier Detected? Use NRZI Encoding? Physical Link Type: Resource Planning Forms...
Page 224: Lan Connections
Local MAC Address: Enable Source Routing: LAN Speed: Maximum Data Size: A.11 Pool Resource Form Name: Comment: Access Control: A.12 Users Resource Form Name: Full Name: User ID: IP Address: Default Resource: SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 225: A.13 Group Resource Form
A.13 Group Resource Form Name: Comment: Members: A.14 Client Conﬁguration Requirements sun3270 LUType 2: Local Address: Pool Name: Access Control: sun3287 LUType 1 or LUType 2: Local Address: Pool Name: sun5250 LUType 6.2: Pool Name: Session Limit: Access Control: sun3770 LUType 1: Pool Name: Number of LUs:...
Page 226 A-10 SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 227: B.1 Domain Name System
Name Resolution This appendix contains the following sections: • Domain Name System - describes the Domain Name System (DNS). • Sun Name Server - describes the Sun Name Server. • Updating the DNS Configuration - describes how to update the DNS conﬁguration before you use the Sun Name Server.
Page 228 ﬁrst querying the root name server. The root name server refers the local name server to the next level domain by returning the addresses of its name servers. SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 229: B.2 Sun Name Server
The local name server then reissues its query to the next-level name server, and so on. When the requested host is located, the local name server returns the name and network address of the host to the client. If a name is not fully- qualiﬁed, the local name server expects the name to be (or to be in) one of its own subdomains.
Page 230 Server resolves the name request, selects a host to service the connection, and then sends the IP address of the host to the client. When the client receives the name resolution, the client sends its open request to the resolved address. SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 231: B.3 Updating The Dns Conﬁguration
When the Sun Name Server receives a name resolution request, it assumes that the name is an SNA resource (PU, LU, or LU pool) and checks its resource database for the name. If the name is not an SNA resource, the Sun Name Server then checks its user database for the name.
Page 232 DNS does not run on the local host. For example, to access the name server on hosts 199.97.127.10 and 199.97.127.20, ﬁle would contain the following directive: resolv.conf nameserver SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 233: B.4 Using The Sun Name Server With Appc
nameserver 199.97.127.10 nameserver 199.97.127.20 Some domain name servers support a directive to override the search default order in which domains are searched. Referring to Figure B-2, to query before the default domain , the acme.com corp.acme.com ﬁle would contain the following directive: resolv.conf search...
Page 234 “LUSP1”); if (lu62_open(&open_req) == LU62_ERROR) { printf("lu62_open error, 0x%x\n", lu62_errno); exit(1); Similarly, SUNWappc CPI-C programs issue the call to connect to a Open_LU() server and local LU as follows: Open_LU(“LUSP1.sna”, “LUSP1”, &retcode); SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 235: C.1 Hierarchical Sna
SNA Concepts This appendix contains the following sections: • Hierarchical SNA - describes the traditional, host-based hierarchical SNA (Systems Network Architecture) networks. • Peer-to-Peer SNA - describes the distributed, peer-to-peer networks that use Advanced Peer-to-Peer Networking (APPN). • PU2.1 and PU2 Nodes - describes the differences between PU2.1 and PU2 nodes.
Page 236: C.1.1 Physical Components
JES2, POWER, IMS, NetView, CICS, and TSO. The communications controllers are specialized communications devices that route data between the host and cluster controllers and between networks. An IBM 3745 is an example of a communications controller. SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 237 The cluster controllers control the input and output of attached devices, such as display stations and printers. A 3174 or 3274 Control Unit is an example of a cluster controller. The Sun PU2.1 SNA Server emulates a cluster controller with attached devices.
Page 238: C.1.2 Logical Components
LUs on SNA hosts are typically associated with large applications such as CICS, TSO, NetView, JES2, and IMS. LUs on cluster controllers send data to and receive data from the SNA network for terminal users. SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 239: C.1.3 Sessions
Dependent LUs require a host-based SSCP to establish sessions and can be LUType 0, LUType 1, LUType 2, LUType 3, or LUType 6.2. The following ﬁgure illustrates the relationship between the logical components in a hierarchical SNA network. Mainframe X.25 PSDN Token Ring Cluster Controller...
Page 240: C.2 Peer-To-Peer Sna
SNA protocol stack: Path Control (PC), Data Link Control (DLC), and the actual physical communications medium. The physical medium can be telecommunications lines, such as SDLC and X.25, or local area networks, such SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 241: C.2.2 Logical Components
as IBM Token Ring and Ethernet. PU2.1 nodes can interconnect LUType 6.2- based applications running on the same system. This is known as an intranode session. The following ﬁgure illustrates the connection of two PU2.1 nodes over an SNA transport network. Applications on either the AS/400 or the System/36 can communicate either with applications on the other (peer) machine or with applications resident on the same (local) machine.
Page 242 LUs. Only LUType 6.2 on a PU2.1 node can act as an independent LU. Dependent LUs require a host-based SSCP to establish sessions. Dependent LUs can be LUType 0, LUType 1, LUType 2, LUType 3, or LUType 6.2. SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 243: C.2.3 Sessions
C.2.3 Sessions Like data in hierarchical SNA networks, data in peer-to-peer SNA networks is transferred between logical components using SNA sessions. A session provides a logical communications pipe between end users and host applications. The following table describes the two types of peer-to-peer SNA sessions.
Page 244: C.3 Pu2.1 And Pu2 Nodes
NNs. An example organization of APPN network nodes, with APPN end nodes and LEN end nodes, is shown in the following ﬁgure. C-10 SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 245: C.5 Appc And Lutype 6.2
APPN APPN Figure C-5 Example APPN Network C.5 APPC and LUType 6.2 The APPC architecture deﬁnes the LUType 6.2 and is intended to support communication between application programs running on any APPC-based nodes in an SNA network. This enables distributed processing, in which two or more TPs running on different systems cooperate to perform a task.
Page 246: C.5.1 Transaction Programs
Therefore, the local TP connects to its local LUType 6.2, which in turn is in session with its partner (or remote) LUType 6.2. The remote TP is located at the partner LU. C-12 SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 247: C.5.2 Conversations And Verbs
C.5.2 Conversations and Verbs TPs always communicate in pairs. A logical connection called a conversation is established between the two TPs. Conversations make temporary use of sessions set up between the TPs' respective LUs. Programs communicate on conversations using the verbs deﬁned on the conversation protocol boundary between the TP and its local LUType 6.2.
Page 248: C.5.4 Independent Or Dependent Lutype 6.2S
LUType 6.2 is owned by a local PU type 2 (and has a conﬁgured LOCADDR) and requires the support of a host (SSCP) to establish a single session with a remote LUType 6.2. C-14 SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 249: D.1 Overview
IBM Token Ring Concepts This appendix contains the following sections: • Overview - provides an overview of the IBM Token Ring network. • Frame Formats - describes the frame formats used to transmit information on a IBM Token Ring network. •...
Page 250 Token Ring. For more details on the capabilities of the Token Ring adapter chipset and the functions provided by the various servers, refer to the appropriate documentation. SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 251: D.2 Frame Formats
The IBM Token Ring is a compatible superset of the standard established by the IEEE standards board and the American National Standards Institute (ANSI) standard for a ring utilizing token passing as the access method: IEEE Standard 802.5-1989. Data rates for the IBM Token Ring are 4 million bits per second (4 Mb/s) and 16 Mb/s.
Page 252 LLC frames carry SNA data. The LLC frame format is shown in the following ﬁgure. Figure D-2 LLC Frame Format LLC frames consist of the following: • Destination Service Access Point (DSAP). SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 253: D.2.1 Addressing
• Source Service Access Point (SSAP). • One or two bytes of control information. • Zero or more bytes of data information. The SAPs are used as logical ports, or addresses, from the higher-level communication and network models, such as OSI, SNA, and TCP/IP, into the LLC sublayer.
Page 254 MAC addresses in hexadecimal format, such as X'40001A67F527' D.2.1.2 LLC Entities LLC addresses are represented by SAPs and are one byte in length. The format is shown in the following ﬁgure. SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 255: D.3 Source Routing And Multiple-Ring Operation
Figure D-4 LLC Address Format Each LLC PDU consists of one destination SAP and one source SAP. Bits 0 through 5 consist of the actual address bits. Bit 6 identiﬁes whether the SAP address is user-deﬁned (set to 0) or deﬁned by the IEEE (set to 1). Bit 7 identiﬁes whether the SAP is an individual SAP (set to 0) or a group SAP (set to 1).
Page 256 Token Ring network. The originating station transmits the frame with the nonbroadcast source route attached. The Token Ring bridge, depending on how it is conﬁgured, optionally transmits the frame on its second ring. SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 257 Conﬁguration issues that determine whether to transmit to the second ring include internal bridge congestion, matching ring and bridge numbers, and largest frame passable by the bridge. • All-routes broadcast - Used when the path to the destination ring station is not known.
Page 258 Finally, Sun products can be run without source routing. All values, including source routing, ring station discovery attempts, and maximum frame size, are user-conﬁgurable. D-10 SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 259: E.1 Overview
Load Balancing This appendix contains the following sections: • Overview - provides a brief description of load balancing. • Normal Load Balancing - describes normal load balancing and provides an example. • Geographical Load Balancing - describes geographical load balancing and provides an example.
Page 260: E.2.1 Normal Load Balancing Description
TN3270E client connections use the following connection parameters: • Hostname: foo.sna.sun.com • Connection Resource: The user record speciﬁes the following: • Name: • Default Resource: POOL-1 PUBLIC Refer to the following ﬁgure as you follow the procedure. SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 261 Sun PU2.1 SunSMAN SNA Server SunPU2.1 SunGMAN Client Figure E-1 Normal Load Balancing 1. The client requests a connection to the domain, using the name of the user record ( ) as the resource name ( ). The connection request is handled by the DNS and sent to SunGMAN for name resolution.
Page 262: E.3 Geographical Load Balancing
7. The client is now connected to the IBM host using the selected LU. E.3 Geographical Load Balancing The following sections provide a description of geographical load balancing and a geographical load balancing example. SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 263: E.3.1 Geographical Load Balancing Description
E.3.1 Geographical Load Balancing Description Geographical load balancing is useful if your LUs are geographically dispersed or if you want all clients to connect to a resource using the same name. Geographical load balancing is more difﬁcult to implement, requiring a detailed knowledge of the TCP/IP infrastructure relevant to IP addressing, netmasking, and hostnames.
Page 264: E.3.2 Geographical Load Balancing Example
Note – Instead of specifying the Client Address Type as IP ADDRESS, you can specify the Client Address Type as IP HOSTNAME. In this case, you specify the IP Hostname parameter instead of the IP Address and Mask parameters. SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 265 Refer to Figure E-1 on page E-3 as you follow the procedure. 1. A client requests a connection to the domain, using the geographical load balancing keyword ( ). The connection request is handled by DNS and sent to SunGMAN for name resolution. A sample connection request is as follows: suntn3270x -h glb.sna.sun.com 2.
Page 266 SunSMAN process then passes this connection to the Sun PU2.1 server process (sunPU21) that has the selected LU conﬁgured. 7. The client is now connected to the IBM host using the selected LU. SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 267: F.1 3270 Clients
Host Conﬁgurations This appendix describes how to coordinate host conﬁgurations for the following clients: • 3270 clients • sun3770/RJE clients • APPC clients • 5250 clients F.1 3270 Clients The following table lists the Sun PU2.1 SNA Server conﬁguration parameters speciﬁc to 3270 clients that you must coordinate with the host conﬁguration.
Page 268 LOGMODE formatting characteristics, maximum message sizes, and session protocol deﬁnitions. The following example is a entry suitable for a sun3270 client: LOGMODE LOG32782 MODEENT LOGMODE=LOG32782, FMPROF=X'03', TSPROF=X'03', PRIPROT=X'B1', SECPROT=X'90', COMPROT=X'3080', RUSIZES=X'85C7', PSNDPAC=0, SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 269 SRCVPAC=0, SSNDPAC=0, PSERVIC=X'028000000000185000007E00' Note – To execute ﬁle transfers with a 3270 client, the ﬁrst two bytes of the PSERVIC parameter must be . The deﬁnes the LU as an LUType 2 and 0280 indicates that structured queries are supported. The following example is a entry for an LUType 1 printer client: LOGMODE...
Page 270: F.2 Sun3770/Rje Clients
The association between the LU and its entry is created in the LU macro of the VTAM/NCP gen or in LOGMODE the deﬁnition of a superior resource: group, line, or PU. SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 271 entry deﬁnes session and presentation values that are included in LOGMODE the session activation request ( ) sent by the SNA host application to the BIND sun3770/RJE client. The entry values specify the expected screen size, LOGMODE display formatting characteristics, maximum message sizes, and session protocol deﬁnitions.
Page 272: F.3 Appc Clients
You can deﬁne a network-qualiﬁed name or a fully-qualiﬁed name with the Network Qual Name parameter as , where [ NETID .] NODEID NETID is an optional network identiﬁer and NODEID is a node identiﬁer. SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 273 Note – When connecting to a host as a dependent LU, set the uninterpreted LU name, , to the host-conﬁgured value to ensure proper SSCP UI_LU_NAME translation. Independent LUs connecting to a host are not associated with a speciﬁc local address and must be speciﬁed as LOCADDR=0 Independent LUs have no corresponding PU.
Page 274: F.3.2 Partner Lu
VTAM deﬁnes resources that are viewed as remote LUs by the Sun PU2.1 SNA Server with the APPC resource deﬁnition directive. The following parameters are of particular interest: APPC PARSESS =YES (for independent LUs) (for dependent LUs) SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 275 F.3.2.2 CICS When connecting with CICS for partner LU deﬁnition, make sure that you examine the following aspects of the connection deﬁnition: CONNECTION PROPERTIES SINGLESESS SECURITY BINDPASSWORD For deﬁning the terminal control table, , with respect to the partner LU DFHTCT deﬁnition, the following parameters are relevant: FEATURE...
Page 276: F.3.3 Session Mode
OBJECT CHARACTERISTICS SESSION_IDENTIFIERS MODENAME SENDSIZE RECEIVESIZE For deﬁning the terminal control table, , with respect to the mode DFHTCT deﬁnition, the following parameters are relevant: MODENAME= mode-name FEATURE= features RUSIZE=n F-10 SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 277: F.3.4 Transaction Program
F.3.3.3 AS/400 When connecting to an AS/400 for mode deﬁnition, verify the following parameters for the line description, controller description, and device descriptions: CRTDEVAPPC MODE= mode-name MODE DESCRIPTION MODD=mode-name COS=class-of-service-name MAXSSN=maximum-sessions MAXCNV=maximum-conversations LCLCTLSSN=locally-controlled-sessions PREESTSSN=pre-established-sessions INPACING=inbound-pacing-value OUTPACING=outbound-pacing-value MAXLENRU=maximum-length-of-request-unit F.3.4 Transaction Program The TP conﬁguration deﬁnes transaction programs to which incoming Attach requests are directed.
Page 278: F.4 5250 Clients
The following table lists the Sun PU2.1 SNA Server conﬁguration parameters that you must coordinate with the AS/400 conﬁguration. If you change any of these parameters in one conﬁguration, you must make the corresponding changes in the other conﬁguration. F-12 SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 279 Table F-3 PU2.1 SNA Server AS/400 Conﬁguration Parameters Sun Resource Resource Parameter AS/400 Object AS/400 Parameter PU2.1 server CP Name CTL(APPC) Remote network identiﬁer Remote control point Type LIN(TRLAN) Connection type connection LAN Speed Line speed Local MAC Address CTL(APPC) Remote adapter address Remote MAC Address...
Page 280: F.4.2 Sdlc Connection
), which corresponds LCLLOCNAME to the partner LU name. Use the AS/400 display network attributes ) command to determine this value. Make sure that you use the DSPNETA default local location name value. F-14 SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 281 • The mode name, which must be common in both conﬁgurations. If installed, the PC Support/400 installation creates the mode description, QPCSUPP Host Conﬁgurations F-15...
Page 282 F-16 SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 283: G.1 Session-Level Security
LUType 6.2 Security This appendix contains the following sections: • Session-Level Security - describes session-level security for peer-to-peer operations. • Conversation-Level Security - describes conversation-level security for peer-to-peer operations. • Security Access Veriﬁcation - describes how to specify minimum security requirements for peer-to-peer operations.
Page 284: G.2 Conversation-Level Security
LU. Since the partner LU trusts the local LU, no password is sent. The use of the user ID, password, and proﬁle for conversation-level security and Unix-level security is shown in the following ﬁgure. SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 285 CMALLC/ALLOCATE/ MC_ALLOCATE FMH-5 (ATTACH) Verify against Security deﬁned Partner LU for this LU Minimum Security Partner LU Perform security access minimum security veriﬁcation against UserID/ valid Password/Proﬁle using Security Access List and Partner LU Minimum Security match criteria Reject Attach Perform resource access veriﬁcation against Security Access...
Page 286: G.3 Security Access Veriﬁcation
Proﬁle - The proﬁle must exist in the TP resource access list. • User ID and proﬁle - Both the user ID and proﬁle must exist in the TP resource access list. SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 287: G.5 Unix-Level Security
G.5 Unix-Level Security By default, Unix-level security controls only how processes are invoked from remote systems to the local system. The Sun PU2.1 SNA Server provides additional Unix-level security by not allowing user processes to be invoked as root. Whenever the server invokes a user process, the server sets the user ID of the process to the Default User name speciﬁed for the PU2.1 server.
Page 288 SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 289 Index Numerics Advanced Program-to-Program Communications, see APPC 3270 Help Screen Display Key AFTP server, enabling, 4-5 parameter, 11-14 AID key, 12-30 3270, see Sun3270, TN3270, TN3270E specifying, 11-14 3770, see Sun3770 Allow Partner LU to Queue BIND Rsp? 5250, see Sun5250, TN5250 parameter, 9-4 APPC (Advanced Program-to-Program Communications)
Page 290 Common problems, 12-32 Create Transaction Program dialog box, 9- Conﬁguration creating off-line, 11-14 Create User dialog box, 10-1 displaying information, 12-2 CUG, see Closed User Group modifying, 11-12, 11-15 options, 1-5 Index-2 SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 291 Error handling, 12-32 Ethernet, 1-8, 1-9 Data Link Control, see PUs see also LAN connections Data size, specifying for LAN Event log, 12-16 connections, 6-4 Events window, 2-7 Default Group parameter, 5-3 Expiry Date parameter, 11-7 Default resource, 1-12 Extended TN3270E, see TN3270E parameter (user), 10-2 Default User parameter, 5-3 Deﬁnition Verbs? parameter, 9-17...
Page 292 Invoking actions, 2-10 line trace, 12-16 IP Address parameter, 10-4 PU2.1 server trace, 12-27 IP Host parameter (QLLC connections), 6- Logical units, see Dependent LUs, Independent LUs IP Hostname parameter (user), 10-4 Index-4 SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 293 Loss of quorum, 11-10 Maximizing a window, 2-9 Low Entry Networking, see LEN Maximum Data Size parameter (LAN connections), 6-4 Lowest Max Receive RU Size parameter, 9-9 Maximum Retries parameter, 7-8 Lowest Max Send RU Size parameter, 9- Maximum Sessions parameter, 9-11 May Alloc Service TPs? parameter, 9-17 LU information screen, 11-14, 12-30 Medium Access Control, see MAC...
Page 294 Password parameter PU2.1 server trace, 12-27 connecting to domain, 2-3 PU2.1 servers, 1-7 LUType 6.2 user, 9-12 conﬁguring, 5-1 user, 10-4 PUs (physical units), 1-9, 1-13 P-Bit Timeout parameter, 7-8 conﬁguring, 7-1 Index-6 SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 295 specifying name, 9-9 Resources parameter, 12-28 PVC Logical Channel No parameter, 6-9 Response Count parameter, 7-8 Response Time Monitor, see RTM Response Timer parameter, 7-8 Restoring QLLC connections, 1-9, 1-10 manager network, 11-10 conﬁguring, 6-7 window, 2-10 Qualiﬁed Logical Link Control, see QLLC Restricted operators, 11-5 connections Retries parameter, 5-5...
Page 296 System Manager, see SunSMAN Sun Name Server, 1-4, B-3 System parameter, 12-28 using with APPC, B-7 Systems, 1-7 Sun PU2.1 server process, see PU2.1 server conﬁguring, 4-1 process Systems Network Architecture Index-8 SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...
Page 297 see SNA TWA, specifying, 7-9 Two-way alternating/simultaneous, specifying, 7-9 TWS, specifying, 7-9 Table Type parameter customizing, 12-2 LAN connection, 6-2 displaying, 12-2 system, 4-2 RTM information, 12-14 selecting type, 12-2 status information, 12-4 Table Formats dialog box, 12-2 Uninterpreted Name parameter, 9-6 Table Size parameter, 5-5 Unique Session Name parameter, 9-9 Technical support, 12-38...
Page 298 2-9 resource, 2-8 restoring, 2-10 tiling, 2-10 Traces, 2-7 Window Increment parameter, 7-9 Window Size parameter, 6-10 Working Directory parameter, 12-18 X.25 PSDN address, specifying, 6-9, 6-10 Xterm Command parameter, 12-20 Index-10 SunLink SNA 9.1 PU2.1 Server Conﬁguration Guide—August 1997...

Sun Microsystems SunLink SNA 9.1 PU2.1 Configuration Manual

1 Overview

2 Using the Administration Program

3 Getting Started

4 Conﬁguring Systems

5 Conﬁguring PU2.1 Servers

6 Conﬁguring Connections

7 Conﬁguring Pus

8 Conﬁguring Dependent Lus

9 Conﬁguring for Lutype 6.2

10 Conﬁguring Users

11 Managing the Server

12 Troubleshooting

Resource Planning Forms

Quick Links

Need help?

Questions and answers

Related Manuals for Sun Microsystems SunLink SNA 9.1 PU2.1

Summary of Contents for Sun Microsystems SunLink SNA 9.1 PU2.1