Expand Configuration and Management Manual Abstract This manual describes how to plan, configure, manage, and troubleshoot the Expand subsystem on an HP Integrity NonStop™ BladeSystem and HP Integrity NonStop NSseries server. The Expand subsystem can connect as many as 255 geographically dispersed NonStop servers to create a network with the reliability, capacity to preserve data integrity, and potential for expansion of a single server.
Document History Part Number Product Version Published 529522-008 Expand H01 June 2010 529522-009 Expand H01 August 2010 529522-010 Expand H01 August 2012 529522-011 Expand H01 February 2013 529522-012 Expand H01 April 2013 529522-013 Expand H01 February 2014
Legal Notices © Copyright 2014 Hewlett-Packard Development Company L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
Expand Configuration and Management Manual Glossary Index Examples Figures Tables Legal Notices What’s New in This Manual xxvii Manual Information xxvii New and Changed Information xxvii About This Manual xxxiii Who Should Use This Manual xxxiii How This Manual Is Organized xxxiii Related Documentation xxxvii Notation Conventions xxxix Abbreviations xliii HP Encourages Your Comments xlv Part I. Getting Started 1.
2. Expand Overview Contents Starting Lines in a Multi-Line Path 1-18 2. Expand Overview Network Transparency 2-1 Interactive Access 2-1 Programmatic Access 2-2 Expand Subsystem and the NonStop Operating System Multiple Communications Environments 2-5 Leased and Satellite Connections 2-5 X.
4. Planning for ServerNet Clusters Contents Defining Paths Between Systems 3-7 When to Use a Single-Line Expand Line-Handler Process When to Use a Multi-Line Path 3-7 When to Use a Multi-CPU Path 3-9 Selecting Special Features 3-11 Multipacket Frame Feature 3-11 Variable Packet Size Feature 3-11 Congestion Control Feature 3-12 Designing the Network Topology 3-12 Common Network Topologies 3-12 Topology Limitations 3-14 Creating a Network Diagram 3-15 3-7 4.
. Configuring Expand-Over-IP Lines Contents Required Hardware and Software 7-2 QIO Subsystem 7-3 Wide Area Network (WAN) Shared Driver 7-3 NonStop TCP/IP Process 7-3 Local Area Network (LAN) Driver and Interrupt Handlers (DIHs) ServerNet Wide Area Network (SWAN) Concentrator 7-4 Topology Considerations 7-4 Summary of Configuration Steps 7-5 Step 1: Find an Available WAN Line 7-5 Step 2: Create a Profile for the Line-Handler Process 7-7 ADD Profile Command 7-7 Examples 7-8 Step 3: Create the Line-Handler
. Configuring Expand-Over-ATM Lines Contents Select a SUBNET for NonStop TCP/IPv6 Use 8-11 Select a TCP6SAM Process 8-13 Creating an Ethernet Subnet 8-14 Step 1 (C): Select a Process and SUBNET for CIP Use 8-15 Select a CIPSAM Process 8-15 Obtain an IP Address to associate with your Expand Line- Handler Process 8-15 Step 2 (A): Identify an Available UDP Port Number 8-17 Step 2 (B): Identify an Available UDP Port Number for NonStop TCP/IPv6 Use 8-18 Step 2 (C): Identify an available UDP Port Number for CI
. Configuring Expand-Over-X.25 Lines Contents Example 9-12 Step 3: Create the Line-Handler Process 9-12 ADD DEVICE Command 9-12 Considerations 9-16 Examples 9-16 Step 4: Start the Line-Handler Process 9-17 Step 5: Start the Line 9-17 Profile Modifiers 9-18 Recommended Modifiers 9-18 Modifiers for Special Features 9-19 PEXQSATM Modifiers 9-19 10. Configuring Expand-Over-X.
Contents 11. Configuring Expand-Over-SNA Lines 11.
13.
14. Subsystem Control Facility (SCF) Commands Contents Path-Logical Device Modifiers 13-16 Modifiers for Special Features 13-16 PEXPPATH Modifiers 13-16 Line-Logical Device Modifiers 13-18 X25AM Process Modifiers 13-18 PEXQMSWN and PEXQMSAT Modifiers PEXQMNAM Modifiers 13-20 PEXQMIP Modifiers 13-21 PEXQMATM Modifiers 13-22 13-18 Part III. Subsystem Control Facility (SCF) 14.
Contents 14.
. Tracing Contents Expand-Over-ServerNet, Expand-Over-X.
. Expand Modifiers Contents Example 15-8 HEX Command 15-8 Example 15-9 LABEL Command 15-9 Example 15-9 NEXT Command 15-9 Example 15-10 OCTAL Command 15-10 Example 15-10 OUT Command 15-11 Example 15-11 RECORD Command 15-11 Examples 15-12 SELECT Command 15-12 Part IV. Reference Information 16.
16.
17. Subsystem Description Contents TIMERINACTIVITY n 16-26 TIMERPROBE n 16-26 TIMERRECONNECT n 16-27 TXWINDOW n 16-27 V6DESTIPADDR n 16-28 V6SRCIPADDR n 16-29 Profiles 16-29 Single-Line Expand Line-Handler Process Modifiers Multi-Line Path Modifiers 16-32 16-29 17.
Contents 17.
18. Managing the Network Contents Part V. Management, Tuning, and Troubleshooting 18.
19. Tuning Contents 19.
A. SCF Error Messages Contents $NCP Problems 20-11 Expand Line-Handler Process Problems 20-12 SWAN Concentrator Problems 20-13 WAN Subsystem Problems 20-15 Expand-Over-X.
B. Expand and WAN SCF Comparison Contents B. Expand and WAN SCF Comparison Command Comparison B-1 ALTER Command Comparison B-7 Modifier-to-Attribute Comparison B-7 Altering Timeout Periods B-8 Glossary Index Examples Example 1-1. Example 1-2. Example 1-3. Example 6-1. Example 7-1. Example 8-1. Example 8-2. Example 8-3. Example 8-4. Example 8-5. Example 8-6. Example 8-7. Example 8-8. Example 8-9. Example 8-10. Example 8-11. Example 8-12. Example 8-13. Example 8-14. Example 8-15. Example 8-16.
Examples Contents Example 9-4. Example 9-5. Example 14-1. Example 14-2. Example 14-3. Example 14-4. Example 14-5. Example 14-6. Example 14-7. Example 14-8. Example 14-9. Example 14-10. Example 14-11. Example 14-12. Example 14-13. Example 14-14. Example 14-15. Example 14-16. Example 14-17. Example 14-18. Example 14-19. Example 14-20. Example 14-21. Example 14-22. Example 14-23. Example 14-24. Example 14-25. Example 14-26. Example 14-27.
Figures Contents Example 14-28. STATS LINE Command, Expand-Over-ATM Line-Handler Processes 14-87 Example 14-29. STATS LINE Command, Expand-Over-ServerNet Line-Handler Processes 14-89 Example 14-30. STATS LINE Command, SWAN Concentrator Lines 14-91 Example 14-31. STATS PROCESS $NCP Command, NETFLOW Option 14-99 Example 14-32. STATS PROCESS $NCP Command, LOCALFLOW Option 14-100 Example 14-33. STATUS PATH Command 14-101 Example 14-34. STATUS PATH, DETAIL Command 14-102 Example 14-35.
Figures Contents Figure 3-1. Figure 3-2. Figure 3-3. Figure 3-4. Figure 3-5. Figure 4-1. Figure 4-2. Figure 4-3. Figure 7-1. Figure 7-2. Figure 8-1. Figure 8-2. Figure 8-3. Figure 9-1. Figure 9-2. Figure 9-3. Figure 10-1. Figure 10-2. Figure 11-1. Figure 11-2. Figure 11-3. Figure 12-1. Figure 12-2. Figure 13-1. Figure 13-2. Figure 14-1. Figure 15-1. Figure 17-1. Figure 17-2. Figure 17-3. Figure 17-4. Figure 17-5. Figure 17-6. Figure 17-7. Figure 17-8. Figure 17-9.
Tables Contents Figure 17-10. Figure 17-11. Figure 17-12. Figure 17-13. Figure 17-14. Figure 17-15. Figure 17-16. Figure 17-17. Figure 17-18. Figure 17-19. Figure 17-20. Figure 17-21. Figure 17-22. Figure 17-23. Figure 19-1. Figure 19-2. Figure 19-3. Figure 19-4. Figure 19-5. Figure 19-6. Figure 20-1.
Tables Contents Table 5-1. Table 5-2. Table 7-1. Table 8-1. Table 9-1. Table 10-1. Table 11-1. Table 12-1. Table 12-2. Table 13-1. Table 13-2. Table 13-3. Table 13-4. Table 13-5. Table 13-6. Table 13-7. Table 14-1. Table 14-2. Table 14-3. Table 14-4. Table 14-5. Table 14-6. Table 14-7. Table 14-8. Table 14-9. Table 14-10. Table 15-1. Table 15-2. Table 15-3. Table 16-1. Table 16-2. Table 16-3. Table 16-4. Table 18-1. Table 18-2. Table 18-3. Table 18-4.
Tables Contents Table 18-5. Table 18-6. Table 18-7. Table 18-8. Table 18-9. Table 18-10. Table 18-11. Table 18-12. Table 19-1. Table 19-2. Table 19-3. Table 20-1. Table 20-2. Table 20-3. Table 20-4. Table 20-5. Table 20-6. Table 20-7. Table 20-8. Table 20-9. Table 20-10. Table 20-11. Table 20-12. Table 20-13. Table 20-14. Table 20-15. Table 20-16. Table 20-17. Table B-1.
Tables Contents Expand Configuration and Management Manual — 529522-013 xxvi
What’s New in This Manual Manual Information Expand Configuration and Management Manual Abstract This manual describes how to plan, configure, manage, and troubleshoot the Expand subsystem on an HP Integrity NonStop™ BladeSystem and HP Integrity NonStop NSseries server. The Expand subsystem can connect as many as 255 geographically dispersed NonStop servers to create a network with the reliability, capacity to preserve data integrity, and potential for expansion of a single server.
What’s New in This Manual • • • Changes to the 529522-012 manual: Added the following attributes and descriptions to the STATS PATH NODE command example. ° ° ° ° Average RTT RTT Std Dev Min RTT Max RTT Added a consideration the ALTER LINE Command on page 14-12.
What’s New in This Manual • • • • • • • • ° ° ° ° ° Changes to the H06.21/J06.10 manual: Modifiers for Special Features on page 9-19. Modifiers for Special Features on page 10-13. Modifiers for Special Features on page 11-15. Profile Modifiers on page 12-13. Path-Logical Device Modifiers on page 13-16. Updated the following tables with description of L4CWNDCLAMP modifier: ° ° ° ° ° ° PEXQSSWN and PEXQSSAT Modifiers on page 7-12. PEXQSIP Modifiers for Expand-over-IP Lines on page 8-34.
What’s New in This Manual • • Changes to the J06.04 Manual (529522-007 Edition) Added Local Area Network (LAN) Driver and Interrupt Handlers (DIHs) on page 10-4 for customer feedback. Corrected minor typographical errors throughout. Changes to the J06.04 Manual (529522-007 Edition) • • • • • • • • • • • • • • • Added the term, NonStop BladeSystems, in About This Manual on page xxxiii. Updated the description of Cluster I/O Protocols (CIP) Configuration and Management Manual on page xxxviii.
What’s New in This Manual • • • ° ° ° ° ° ° ° ° Changes to the H06.08 Manual ASSOCIATEDEV tcpip_process {IPVER_IPV4 | IPVER_IPV6} SRCIPADDR src_ipaddr SRCIPPORT src_ipport DESTIPADDR dest_ipaddr DESTIPPORT dest_ipport V6SRCIPADDR v6srcip-address V6DESTIPADDR v6destip-address Added examples to describe how to add a configured tunnel for an Expand Line for CIP on page 8-30. Updated the command name in Load Balancing on page 19-16.
What’s New in This Manual • • • • • • • • • • • • • • • • • • • • • • Changes to the H06.
About This Manual The Expand Configuration and Management Manual describes how to plan, configure, and manage the Expand subsystem on an HP Integrity NonStop™ NS-series server and NonStop BladeSystems.
Part I Contents About This Manual Part I Contents Part I, Getting Started, consists of Sections 1 through 4. Table i summarizes the contents of Part I. Table i. Summary of Contents—Part I Section Title Contents 1 Configuration Quick Start Provides the basic information required to enable you to quickly define, start, and modify Expand line-handler process. 2 Expand Overview Describes the Expand subsystem’s major features and capabilities.
Part III Contents About This Manual Table ii. Summary of Contents—Part II Section Title Contents (continued) 11 Configuring ExpandOver-SNA Lines Explains how to configure and start single-line Expand-over-SNA line-handler processes. 12 Configuring ExpandOver-ServerNet Lines Explains how to configure Expand-over-ServerNet line-handler processes. 13 Configuring Multi-Line Paths Explains how to configure and start multi-line paths.
Part V Contents About This Manual Part V Contents Part V, Management, Tuning, and Troubleshooting, consists of Sections 18 through 20. Table v summarizes the contents of Part V. Table v. Summary of Contents—Part V Section Title Contents 18 Managing the Network This section explains how to access network resources, set up network security, and monitor, reconfigure, and control an Expand network.
Related Documentation About This Manual Related Documentation You might need a guided procedure or related manuals when configuring and managing an Expand network: Guided Procedure for Configuring a ServerNet Node To prepare an Integrity NonStop NS-series server to become a node in a ServerNet cluster, see the guided procedure online help for configuring a ServerNet node, which: • • Creates a ServerNet cluster for the first time Adds a node to an already configured ServerNet cluster Manuals • ASAP M
Manuals About This Manual • Cluster I/O Protocols (CIP) Configuration and Management Manual This manual provides overview about the HP NonStop Cluster I/O Protocols (CIP) subsystem and the procedures for configuring, managing, and migrating to CIP. • Operator Messages Manual This manual describes all messages that are distributed by the Event Management Service (EMS).
Notation Conventions About This Manual Notation Conventions Hypertext Links Blue underline is used to indicate a hypertext link within text. By clicking a passage of text with a blue underline, you are taken to the location described. For example: This requirement is described under Backup DAM Volumes and Physical Disk Drives on page 3-2. General Syntax Notation This list summarizes the notation conventions for syntax presentation in this manual. UPPERCASE LETTERS.
General Syntax Notation About This Manual { } Braces. A group of items enclosed in braces is a list from which you are required to choose one item. The items in the list can be arranged either vertically, with aligned braces on each side of the list, or horizontally, enclosed in a pair of braces and separated by vertical lines. For example: LISTOPENS PROCESS { $appl-mgr-name } { $process-name } ALLOWSU { ON | OFF } | Vertical Line.
Notation for Messages About This Manual a blank line. This spacing distinguishes items in a continuation line from items in a vertical list of selections. For example: ALTER [ / OUT file-spec / ] LINE [ , attribute-spec ]… Notation for Messages This list summarizes the notation conventions for the presentation of displayed messages in this manual. Bold Text. Bold text in an example indicates user input typed at the terminal. For example: ENTER RUN CODE ?123 CODE RECEIVED: 123.
Notation for Subnet About This Manual either vertically, with aligned braces on each side of the list, or horizontally, enclosed in a pair of braces and separated by vertical lines. For example: LBU { X | Y } POWER FAIL process-name State changed from old-objstate to objstate { Operator Request. } { Unknown. } | Vertical Line. A vertical line separates alternatives in a horizontal list that is enclosed in brackets or braces. For example: Transfer status: { OK | Failed } % Percent Sign.
Abbreviations About This Manual Abbreviations This list defines abbreviations and acronyms used in this guide. Both industry-standard terms and HP terms are included. API. Application Program Interface ATM. Asynchronous Transfer Mode ATM3SA. ATM 3 ServerNet Adapter ASAP. Availability Statistics and Performance CAP. Communications Access Protocol CIP. Cluster I/O Protocols CLIM. CLuster I/O Module CLIP. Communications Line Interface Processor ConMgr. Concentrator Manager Process DLC. Data Link Control DSM.
Abbreviations About This Manual LAN. Local Area Network LNP. Logical Network Partitioning LU. Logical Unit MPT. Multiple Path Table MSH. Modified Split Horizon NAM. Network Access Method NCP. Network Control Process NRT. Network Routing Table OOS. Out Of Sequence OSI. Open Systems Interconnection OSS. Open System Services PIN. Process Identification Number PU. Physical Unit PVC. Permanent Virtual Circuit RPT. Reverse Pairing Table SAN. System Area Network SCF. Subsystem Control Facility SCP.
HP Encourages Your Comments About This Manual TF. Time Factor TFTP. Trivial File Transfer Protocol UDP. User Datagram Protocol WAN. Wide Area Network X25AM. X.25 Access Method $NCP. Network Control Process name $$ZCIP. Cluster I/O Protocols subsystem $ZEXP. Expand Manager Process name $ZNET. Subsystem Control Point process name $ZNUP. Network Utility Process name $ZPM. Persistence Manager Process name $ZZKRN. Kernel Subsystem Manager Process name $ZZLAN. SLSA Subsystem Manager Process name $ZZSCL.
About This Manual HP Encourages Your Comments Expand Configuration and Management Manual—529522-013 xlvi
Part I.
Part I.
1 Configuration Quick Start Note. The Integrity NonStop NS1000 server does not support ServerNet clusters. This section provides the basic information to define and start an Expand line-handler process. This procedure requires that you use the default values provided by the Expand subsystem for most configuration modifiers. If you want a customized configuration, or if you want to change your configuration, see Part II, Configuring the Expand Subsystem.
Configuration Quick Start Task 1: Configure and Start $NCP Task 1: Configure and Start $NCP The network control process ($NCP) is responsible for initiating and terminating serverto-server connections and maintaining network-related system tables, including routing information. $NCP must be running at every node in the Expand network before Expand lines can be started. To configure and start the network control process, perform these steps: 1.
Configuration Quick Start Task 2: Start the Expand Manager Process Task 2: Start the Expand Manager Process 1. The Expand subsystem requires that the Expand manager process ($ZEXP) be running during network operation. To start the Expand manager process, enter this command at the TACL prompt: > RUN $SYSTEM.SYSnn.
Task 3: Add the Expand Line-Handler Profile(s) Configuration Quick Start Task 3: Add the Expand Line-Handler Profile(s) HP provides profiles, which contain modifiers and default modifier values, for each type of Expand line-handler process. You can use these profiles to create profiles for your Expand line-handler processes. To add a profile for an Expand line-handler, perform these steps: Note.
Where to Find More Information About This Task Configuration Quick Start where name2 is the name you want to assign to the profile and profile_name is the name of a profile listed in Table 1-2: Table 1-2.
Configuration Quick Start Task 4: Add the Expand Line-Handler Process Task 4: Add the Expand Line-Handler Process The Expand subsystem supports a variety of different protocols and communications methods to enable you to connect systems together in local area network (LAN) and wide area network (WAN) topologies. These types of Expand line-handler processes can be configured: • • • • • • • Direct-connect Satellite-connect Expand-over-IP Expand-over-ATM Expand-over-X.
Creating a Single-Line Expand Line-Handler Process Configuration Quick Start Example 1-1. SCF STATUS ADAPTER Command WAN Manager STATUS ADAPTER for ADAPTER State........... STARTED \NODEA.$ZZWAN.#S01 Number of clips. 3 Clip 1 status : CONFIGURED Clip 2 status : CONFIGURED Clip 3 status : CONFIGURED WAN Manager STATUS SERVER for CLIP State :......... STARTED \NODEA.$ZZWAN.#S01.1 Path A..........: CONFIGURED Path B..........: CONFIGURED Number of lines. 2 Line............ 0 Line............
Creating a Single-Line Expand Line-Handler Process Configuration Quick Start 3. Using the name of the SWAN concentrator with the available WAN line from Step 2a, determine the names of the preferred and alternate NonStop TCP/IP processes configured for the SWAN concentrator. -> INFO ADAPTER $ZZWAN.
Creating a Single-Line Expand Line-Handler Process Configuration Quick Start Example 1-3. SCF STATUS PROCESS Command -> STATUS PROCESS $ZB018 TCPIP Status process \NODEA.$ZB018 Status: Started PPID............. ( 0,319) BPID................ ( 1,292) Proto TCP TCP TCP Faddr 0.0.0.0 0.0.0.0 0.0.0.0 Status LISTEN LISTEN LISTEN Laddr 0.0.0.0 0.0.0.0 0.0.0.0 Lport ftp finger echo Fport * * * SendQ 0 0 0 RecvQ 0 0 0 -> STATUS PROCESS $ZB01C TCPIP Status process \NODEA.$ZB01C Status: Started PPID......
Creating a Single-Line Expand Line-Handler Process Configuration Quick Start Table 1-3. SCF ADD DEVICE Command Worksheet Parameter Value/Description device_name The name you want to assign to the Expand line-handler process. name The name of the profile you created in Task 3: Add the Expand LineHandler Profile(s) on page 1-4.
Creating a Single-Line Expand Line-Handler Process Configuration Quick Start If you want to use IPv6 communications, add the device as: -> ADD DEVICE $ZZWAN.#device_name, PROFILE name,& IOPOBJECT $SYSTEM.SYS00.LHOBJ, CPU cpunum, ALTCPU altcpu,& TYPE (63,0), RSIZE 0, PATHTF 2, NEXTSYS sysnum,& ASSOCIATEDEV tcp6sam_process or cipsam_process, IPVER_IPV6,& V6SRCIPADDR ipv6srcaddress, V6DESTIPADDR ipv6destaddress,& SRCIPPORT sipport, DESTIPPORT dipport Note.
Creating a Single-Line Expand Line-Handler Process Configuration Quick Start Table 1-4. SCF ADD DEVICE Syntax: Expand-Over-IP (page 2 of 2) Parameter Description cipsam_process* The name of the CIP transport-service provider process you want to associate with the Expand-over-IP line-handler process. The CIPSAM process does not need to be configured in the same processor pair as the Expand-over-IP line-handler process. In CIP, the monitor process ($ZZCIP.
Creating a Single-Line Expand Line-Handler Process Configuration Quick Start 1. Add the Expand-over-ATM line-handler process as a device to the WAN subsystem Use this command syntax if the Expand-over-ATM line-handler process will use a PVC connection: -> ADD DEVICE $ZZWAN.#device_name, PROFILE name,& IOPOBJECT $SYSTEM.SYS00.
Creating a Single-Line Expand Line-Handler Process Configuration Quick Start Table 1-5. SCF ADD DEVICE Syntax: Expand-Over-ATM (page 2 of 2) Parameter Description pvc_name The name of the permanent virtual circuit (PVC) used by the Expandover-ATM line-handler process. This modifier is only applicable to Expand-over-ATM line-handler processes that use PVC connections. selector-byte A selector byte for the ATM line used by this Expand-over-ATM linehandler process.
Creating a Multi-Line Path Configuration Quick Start TYPE (63,subtype), RSIZE 0, PATHTF 3, ASSOCIATEDEV process, & ASSOCIATESUBDEV #subdevice, NEXTSYS sysnum Note. If you want the Expand-over-X.25 or Expand-over-SNA line-handler process to be part of a multi-CPU path, specify the SUPERPATH_ON modifier in the SCF ADD DEVICE command. You can configure a maximum of 16 paths in a multi-CPU path. Expand-overServerNet line-handler processes cannot participate as a member of a multi-CPU path (superpath).
Creating a Multi-Line Path Configuration Quick Start 1. Create the path-logical device. -> ADD DEVICE $ZZWAN.#path_name, PROFILE name,& IOPOBJECT $SYSTEM.SYS00.LHOBJ, CPU cpunum, ALTCPU altcpu,& TYPE (63,1), RSIZE 0, PATHTF 3, NEXTSYS sysnum Note. If you want the multi-line path to be part of a multi-CPU path, specify the SUPERPATH_ON modifier in the SCF ADD DEVICE command. You can configure a maximum of 16 paths in a multi-CPU path. Table 1-7.
Where to Find More Information About This Task Configuration Quick Start 2. To create lines in the multi-line path (called line-logical devices), use the SCF ADD DEVICE command syntax shown for configuring single-line Expand line-handler processes (see Creating a Single-Line Expand Line-Handler Process on page 1-6), but with these exceptions: • Use the TYPE modifier values as shown in Table 1-8. Table 1-8.
Configuration Quick Start Task 5: Start the Expand Line-Handler Process Section 12, Configuring Expand-Over-ServerNet Lines Section 13, Configuring Multi-Line Paths Task 5: Start the Expand Line-Handler Process Start the single-line Expand line-handler process or path-logical device. When you use this command to start a path-logical device, the line-logical devices associated with the path are also started. -> START DEVICE $ZZWAN.
2 Expand Overview The Expand subsystem enables you to connect as many as 255 geographically dispersed NonStop servers to create a network with the reliability, capacity to preserve data integrity, and potential for expansion of a single NonStop server.
Programmatic Access Expand Overview Programmatic Access When accessing a file or another resource programmatically across an Expand network, you use the same procedure calls you would use when writing a local application. With a few exceptions, applications that were written to run in a local environment can be used virtually unchanged in a network environment. Expand Subsystem and the NonStop Operating System The Expand subsystem is an extension of the HP NonStop operating system.
Expand Subsystem and the NonStop Operating System Expand Overview Single-Server Process Communications Figure 2-1 illustrates how a process on one processor uses the file system to make an inquiry of a process residing on another processor in the same server. The message system relays the request through the ServerNet system area network (ServerNet SAN). Figure 2-1.
Expand Subsystem and the NonStop Operating System Expand Overview Multi-Node Process Communications Figure 2-2 illustrates the same file-system request as Figure 2-1 on page 2-3, except that the disk process resides on another node in the network rather than on another processor in the same server. Figure 2-2.
Multiple Communications Environments Expand Overview Multiple Communications Environments Nodes in an Expand network can be connected using a variety of data communications technologies and protocols. A single network can consist of any combination of these different data communications methods. Nodes in an Expand network can be connected by • • • • • • Full-duplex leased lines or satellite connections using the High-Level Data Link Control (HDLC) protocol X.
Systems Network Architecture (SNA) Networks Expand Overview Systems Network Architecture (SNA) Networks SNA was developed by IBM for connecting IBM systems and networks. Expand-overSNA connections are provided with the HP SNAX/Advanced Peer Networking (SNAX/APN) product. The Expand subsystem uses the NETNAM protocol to communicate with the SNAX/APN line-handler process. Internet Protocol (IP) Networks An IP network adheres to the Internet Protocol—a computer-industry standard protocol.
Distributed Control Expand Overview Distributed Control The control function of the Expand subsystem is distributed throughout the network. Unlike a hierarchical network, in which a central computer, or host, controls the communications environment, nodes in an Expand network communicate with each other as peers. Distributed networks have these additional advantages: • • • Distributed applications. Applications can be distributed so that multiple nodes share the processing load.
Priority Routing Expand Overview Priority Routing You can assign different priorities to messages sent over an Expand network. Priority routing allows an important message to reach its destination even when the network is congested. Fault-Tolerant Operation Using careful configuration and network-topology design, you can configure an Expand network to be continuously available. You can configure as many as eight lines between the same two nodes using the Expand subsystem’s multi-line path feature.
Subsystem Control Facility (SCF) Expand Overview Note. For more information on managing Expand using SCF, see Part III of this manual, Subsystem Control Facility (SCF). Subsystem Control Facility (SCF) SCF is a Distributed Systems Management (DSM) interface that can be used interactively to control, configure, and monitor the Expand subsystem. The SCF interfaces to the Expand and wide area network (WAN) subsystems are used to configure and manage the Expand subsystem.
Online Expansion and Reconfiguration Expand Overview Online Expansion and Reconfiguration You can add a new node or new lines to a network or move an existing node to a different location without disrupting network activity. You can make changes to your Expand configuration online using the Subsystem Control Facility (SCF) interfaces to the Expand and WAN subsystems. Table 2-1 shows the online expansion and reconfiguration tasks that can be performed with these interfaces. Table 2-1.
Network Security Expand Overview Network Security The Expand subsystem provides security features to control access to remote servers and files. Remote Passwords To access a remote server, you must have a username and user ID on the remote server that is identical to those on the local server.
Expand Overview Enhanced Security Techniques Expand Configuration and Management Manual — 529522-013 2 - 12
3 Planning a Network Design This section describes the network design decisions you must make before installing and configuring a new Expand network or when modifying an existing Expand network. Topics described in this section include • • • • • Selecting Line Protocols on page 3-1 Defining Paths Between Systems on page 3-7 Selecting Special Features on page 3-11 Designing the Network Topology on page 3-12 Creating a Network Diagram on page 3-15 Note.
Planning a Network Design Satellite Connections Satellite Connections The satellite-connect line-handler process implements the satellite-efficient version of the HDLC protocol, HDLC Extended Mode. HDLC Extended Mode allows a maximum window size of 61 frames (the maximum window size is the number of outstanding frames that can be sent before an acknowledgment is required) and implements the selective-reject feature. Selective reject causes only frames that arrive in error to be retransmitted.
Planning a Network Design • • Systems Network Architecture (SNA) Connections Low capital cost/high connectivity. X.25 provides a way to connect a large number of systems through a single line between a NonStop server and an X.25 network. This feature can lower communications capital costs by reducing the number of modems and controller ports that must be purchased. For example, a fully connected network of 4 servers requires 6 links, 12 modems, and 12 hardware ports. An X.
Planning a Network Design Internet Protocol (IP) Networks Internet Protocol (IP) Networks The IP suite is an important industry standard. Expand-over-IP allows NonStop systems to be interconnected via inexpensive IP-based routers, making a separate Expand network unnecessary. Expand-over-IP uses a NonStop TCP/IP process to implement the TCP/IP protocol stack. The Expand-over-IP line-handler process communicates with the NonStop TCP/IP process through the shared memory of the QIO subsystem.
Planning a Network Design Asynchronous Transfer Mode (ATM) Networks When you are planning your Expand-over-IP environment, you can use LNP to control over which network interfaces (IP addresses) the Expand line-handler processes run. For examples of working with logical network partitioning, see Step 1 (B): Select a Process and SUBNET for NonStop TCP/IPv6 Use on page 8-11. To determine which TCP/IP subsystem is running on your system, use the SCF LISTDEV TCPIP command. The text after the last period (.
Planning a Network Design • • • ServerNet Connections Fault-tolerance. You can use the multi-line path feature to enhance the reliability of Expand-over-ATM connections. Using this feature, you can configure up to eight parallel lines between nodes. High-speed connectivity and increased throughput. The ATM subsystem supports the ATM User-Network Interface (UNI) Specification Version 3.0 over a 155 Mbps SONET STS-3c connection. Passthrough capability.
Planning a Network Design Defining Paths Between Systems Defining Paths Between Systems Each system in an Expand network can have up to 255 Expand line-handler processes. An Expand line-handler process can be configured to handle a single line or a path consisting of up to eight parallel lines. You can also associate up to 16 Expand line-handler processes in separate processors with one another to form a multi-CPU path.
When to Use a Multi-Line Path Planning a Network Design varying speeds. For example, if the multi-line path contains both 9600 and 56K byte lines, it is likely that frames traveling on the fast line are received at the destination ahead of the frames traveling on the slower line. If many OOS packets are received, the receiving node might require an OOS buffer space that is larger than the default buffer size.
When to Use a Multi-CPU Path Planning a Network Design Figure 3-2 illustrates an eight-line configuration. Figure 3-2. Multi-Line Path With Eight Lines and Eight SWAN Concentrators $LINE1 SWAN $LINE2 SWAN $LINE3 SWAN $LINE4 SWAN $LINE5 SWAN $LINE6 SWAN $PATH2 $LINE7 $X25AM1 SWAN $LINE8 $X25AM2 SWAN VST026.vsd When to Use a Multi-CPU Path The Expand multi-CPU feature enables you to connect multiple Expand line-handler processes, each in a separate processor, between two nodes.
When to Use a Multi-CPU Path Planning a Network Design • Maximum throughput is significantly increased, especially for Expand-over-IP connections. An Expand-over-IP line-handler process and its associated NonStop TCP/IP process must be configured in the same processor pair, placing the burden of processing the entire communications protocol stack for each Expand-over-IP line on one processor.
Planning a Network Design Selecting Special Features For more information on the multi-CPU paths, see Multi-CPU Feature on page 17-72. Note. You use the SUPERPATH_ON modifier to configure an Expand line-handler process as part of a multi-CPU path. If you configure parallel paths between two nodes without using the SUPERPATH_ON modifier, only one path is used at a given time.
Planning a Network Design Congestion Control Feature The variable packet size feature allows you to configure a maximum packet size, which is used for both single-packet and multipacket frames, on a per-path basis. This feature effectively overrides the packet size calculated from the FRAMESIZE modifier value. For a complete technical overview of the variable packet size feature, see Variable Packet Size Feature on page 17-67.
Common Network Topologies Planning a Network Design Figure 3-4. Common Network Topologies STAR TREE RING BUS MESH VST028 Star Topology In a star topology, all systems join at a central node, creating a star-shaped configuration. Because all nodes are connected through the central node, a star network’s reliability depends on the central node; if the central node fails, the entire network fails. Split-Star Topology Used for ServerNet clusters, the split-star topology connects two star topologies.
Planning a Network Design Topology Limitations Tri-Star Topology Used for ServerNet clusters, the tri-star topology connects three star topologies. Each star contains a cluster switch. The three cluster switches are connected by fiber optic cables, each of which can be up to one kilometer in length. This topology can be used for up to 24 nodes. For examples of this topology, see Section 4, Planning for ServerNet Clusters.
Creating a Network Diagram Planning a Network Design Creating a Network Diagram Before you configure your Expand network, HP recommends that you create a diagram of the complete network topology. This network diagram shows the network nodes and the lines that connect the nodes. This type of diagram can help you and the operations staff monitor systems, recognize problems, and prepare for configuration changes. Figure 3-5 shows one way to create a network diagram.
Planning a Network Design Creating a Network Diagram Expand Configuration and Management Manual — 529522-013 3 - 16
4 Planning for ServerNet Clusters Note. The Integrity NonStop NS1000 server does not support ServerNet clusters. This section describes how to plan for the configuration of Expand over ServerNet clusters, discusses considerations for ServerNet topologies, and provides examples of configuring Expand over ServerNet clusters, ServerNet clusters in combination with ServerNet/FX, ServerNet clusters in combination with ATM and IP networks, and ServerNet clusters with other communication methods.
Planning for ServerNet Clusters Configuration Considerations for Expand and ServerNet Clusters Configuration Considerations for Expand and ServerNet Clusters Major configuration considerations for Expand and ServerNet clusters include: • • • • • • • • A route between two nodes that involves a change in technology invokes the use of the Expand line handlers at every node along the route (including the source and destination nodes).
Planning for ServerNet Clusters ServerNet Clusters Coexisting With ATM or IP Networks would set the LINETF as 1 for ServerNet, 2 for ATM, and a value greater than 2 for all the other paths. For more information on time factors, including how they are specified and calculated, see Routing and Time Factors on page 17-22. ServerNet Clusters Coexisting With ATM or IP Networks Note. The Integrity NonStop NS1000 server does not support ServerNet clusters.
Planning for ServerNet Clusters Examples of ServerNet Clusters Coexisting With ATM or IP Connection, log onto the system being added, select the Configure a ServerNet Node action for the System object, and perform the action. A guided procedure is launched, with online help available to assist you in performing the procedure.
Examples of ServerNet Clusters Coexisting With ATM or IP Planning for ServerNet Clusters Figure 4-1. ServerNet Clusters Connected by ATM or IP Lines 5-Node ServerNet Cluster 4-Node ServerNet Cluster ATM or IP \BBB #2 \CCC #3 Cluster Switch \FFF #4 \EEE #5 \HHH #6 ATM or IP ATM or IP \AAA #1 \DDD #7 Cluster Switch \GGG #9 \JJJ #8 ATM or IP VST062 ServerNet Clusters Connected By a Single ATM or IP Line (Not Recommended) Note.
Examples of ServerNet Clusters Coexisting With ATM or IP Planning for ServerNet Clusters Figure 4-2. ServerNet Clusters Connected by a Single ATM or IP Line (Not Recommended) 5-Node ServerNet Cluster 4-Node ServerNet Cluster \BBB #2 \AAA #1 \CCC #3 Cluster Switch \FFF #4 \EEE #5 \HHH #6 ATM or IP \DDD #7 Cluster Switch \GGG #9 \JJJ #8 VST063 ServerNet Clusters Using Layered Topology With Connections to Nodes Outside the Cluster Note.
Examples of ServerNet Clusters Coexisting With ATM or IP Planning for ServerNet Clusters Figure 4-3.
Planning for ServerNet Clusters Examples of ServerNet Clusters Coexisting With ATM or IP Expand Configuration and Management Manual — 529522-013 4-8
Part II. Configuring the Expand Subsystem Part II consists of these sections, which provide an overview of the configuration process and explain how to configure the various types of Expand line-handler processes: Section 5 Configuration Overview Section 6 Configuring the Network Control Process Section 7 Configuring Direct-Connect and Satellite-Connect Lines Section 8 Configuring Expand-Over-IP Lines Section 9 Configuring Expand-Over-ATM Lines Section 10 Configuring Expand-Over-X.
Part II.
5 Configuration Overview This section provides an overview of the Expand subsystem configuration process. Before using this section and the remaining sections in this manual, you should be familiar with: • • • • Section 3, Planning a Network Design. This section describes network design considerations such as selecting line protocols. You should design your network and create a network diagram before attempting to perform the tasks described in this and the remaining sections of this manual.
Summary of Configuration Steps Configuration Overview Summary of Configuration Steps Configuring the Expand subsystem involves a number of steps. Table 5-1 lists each step and indicates where in this manual the step is described. Table 5-1. Configuration Steps Step Description Where This Step Is Described 1. Start the Expand manager process. For step 1, information is located in Starting the Expand Manager Process on page 5-4 of this section. 2.
Creating a Profile Configuration Overview Creating a Profile A profile template is a disk file that contains modifiers and default modifier values. HP provides profile templates for the network control process ($NCP) and for the different types of Expand line-handler processes. Table 5-2 lists the profile templates for the Expand subsystem. These profile templates are installed in $SYSTEM.SYSnn. The modifiers in each profile template are described in the sections listed in Table 5-1 on page 5-2.
Configuration Overview Creating Wide Area Network (WAN) Subsystem Devices Creating Wide Area Network (WAN) Subsystem Devices The network control process and Expand line-handler processes are defined as WAN subsystem devices. The DEVICE object represents $NCP and Expand line-handler processes in the WAN subsystem. You use the WAN subsystem SCF ADD DEVICE command to create the network control process and Expand line-handler processes.
6 Configuring the Network Control Process This section explains how to configure and start the network control process ($NCP). Configuring and starting $NCP involves these steps: Step 1: Create a Profile for $NCP on page 6-1 Step 2: Create $NCP on page 6-2 Step 3: Start $NCP on page 6-4 You can perform all these steps using the SCF interface to the WAN subsystem. This section also describes the $NCP profile modifiers in $NCP Modifiers on page 6-4.
Configuring the Network Control Process Example modifier_value is the value you want to assign to the modifier specified by modifier_keyword. Specifying a value in modifier_value assigns a new value to modifier_keyword in profile_name. Default values and ranges of values for modifiers in the PEXPNCP profile are described in $NCP Modifiers on page 6-4. Example This example creates a profile named NCPPROF1. The ALGORITHM modifier in the profile is set to 1 to specify split horizon.
Configuring the Network Control Process Considerations CPU cpunum indicates the processor where $NCP will normally run. HP recommends that you configure $NCP to run in processors other than 0 and 1. ALTCPU altcpunum indicates the processor where the backup $NCP will normally run. HP recommends that you configure the backup $NCP to run in processors other than 0 and 1. TYPE (62,6) is the device type and subtype for $NCP. The device type is always 62 and the subtype is always 6 for $NCP.
Step 3: Start $NCP Configuring the Network Control Process Step 3: Start $NCP To start $NCP, use the WAN subsystem SCF START DEVICE command. The command syntax is: START DEVICE $ZZWAN.#NCP To make sure $NCP has started successfully, enter this command at the TACL prompt: > STATUS $NCP If $NCP was started successfully, you will see a display similar to Example 6-1: Example 6-1.
Configuring the Network Control Process $NCP Modifiers ALGORITHM n Default: Units: Range: 0 (MSH) Not applicable 0 or 1 This modifier identifies $NCP routing algorithm to be used. Specify 0 for MSH or 1 for split horizon (SH). The ALGORITHM modifier must be set to the same value on all systems in the network. Modified split horizon (MSH) and split horizon (SH) algorithms are explained in detail in Routing Algorithms on page 17-28.
Configuring the Network Control Process $NCP Modifiers FRAMESIZE n Default: Units: Range: 132 Words 64 through 250 The $NCP FRAMESIZE modifier specifies the maximum packet size that $NCP can send in the network. This value must be less than or equal to the Expand line-handler process’s FRAMESIZE modifier but, it cannot be greater than 250. It is not required that this modifier be the same for each $NCP in the network.
Configuring the Network Control Process • • • $NCP Modifiers -1, the auto-rebalance is switched off and the user must manually trigger rebalance. 0, the auto-rebalance occurs normally without taking into cognizance this modifier value. Greater than 0, the auto-rebalance occurs if the path has revived after being down beyond the time period mentioned in this modifier.
Configuring the Network Control Process Expand Configuration and Management Manual — 529522-013 6-8 $NCP Modifiers
7 Configuring Direct-Connect and Satellite-Connect Lines The direct-connect line-handler process implements the High-Level Data Link Control (HDLC) Normal protocol and operates with conventional voice-grade leased-line and switched-line facilities, private facilities, and fractional Transmission Group 1 (T1) facilities. The satellite-connect line-handler process implements the satellite-efficient version of the HDLC protocol, HDLC Extended mode.
Required Hardware and Software Configuring Direct-Connect and Satellite-Connect Lines Required Hardware and Software Several hardware and software components are required in addition to the directconnect or satellite-connect line-handler process to provide direct-connect or satelliteconnect connectivity. These components are illustrated in Figure 7-1 and are explained in these subsections. Figure 7-1.
Configuring Direct-Connect and Satellite-Connect Lines QIO Subsystem QIO Subsystem QIO is a mechanism for transferring data between processes through a shared memory segment. The QIO subsystem is preconfigured and started during the system load sequence. The QIO subsystem must be started before Expand line-handler processes can be started. For more information on the QIO subsystem, see the QIO Configuration and Management Manual.
Configuring Direct-Connect and Satellite-Connect Lines ServerNet Wide Area Network (SWAN) Concentrator ServerNet Wide Area Network (SWAN) Concentrator The SWAN concentrator is a communications device that provides WAN connections. HP recommends that you configure your satellite-connect or direct-connect line-handler process in the same processor pair as the SWAN concentrator. For more information on the SWAN concentrator, see the WAN Subsystem Configuration and Management Manual.
Summary of Configuration Steps Configuring Direct-Connect and Satellite-Connect Lines Summary of Configuration Steps After all hardware and software requirements have been met (see Required Hardware and Software on page 7-2 for details), configuring and starting a single-line directconnect or satellite-connect line-handler process involves these steps: Step Tool Used Step 1: Find an Available WAN Line SCF interface to the WAN subsystem Step 2: Create a Profile for the Line-Handler Process SCF interfa
Step 1: Find an Available WAN Line Configuring Direct-Connect and Satellite-Connect Lines Example 7-1. SCF STATUS ADAPTER Command -> status adapter $zzwan.#*, sub all WAN Manager STATUS ADAPTER for ADAPTER State........... STARTED \NODEA.$ZZWAN.#S01 Number of clips. 3 Clip 1 status : CONFIGURED Clip 2 status : CONFIGURED Clip 3 status : CONFIGURED WAN Manager STATUS SERVER for CLIP \NODEA.$ZZWAN.#S01.1 State :......... STARTED Path A..........: CONFIGURED Path B..........: CONFIGURED Number of lines.
Configuring Direct-Connect and Satellite-Connect Lines Step 2: Create a Profile for the Line-Handler Process Step 2: Create a Profile for the Line-Handler Process You can create a profile for a single-line direct-connect line-handler process using the PEXQSSWN profile. You can create a profile for a single-line satellite-connect line-handler process using the PEXQSSAT profile. Both profiles are provided in the $SYSTEM.SYSnn subvolume.
Configuring Direct-Connect and Satellite-Connect Lines Examples PEXQSSWN and PEXQSSAT profiles are described in Profile Modifiers on page 7-12. Examples In the first example, a profile named SLHSAT is created for a single-line satelliteconnect line-handler process using the PEXQSSAT profile. The L4TIMEOUT modifier is set to 1000 in the profile. -> ADD PROFILE $ZZWAN.#SLHSAT, FILE $SYSTEM.SYS01.
Configuring Direct-Connect and Satellite-Connect Lines ADD DEVICE Command IOPOBJECT $SYSTEM.SYSnn.LHOBJ is the name of the object file containing the executable object for code for an Expand line-handler process. This value must be $SYSTEM.SYSnn.LHOBJ. PROFILE profile_name is the name of the profile you created for this Expand line-handler process in Step 2: Create a Profile for the Line-Handler Process. CPU cpunumber indicates the processor where this Expand line-handler process will normally run.
Configuring Direct-Connect and Satellite-Connect Lines Considerations PATH { A | B } is the path (A or B) on the CLIP specified by clipnum that you prefer. The path must be configured. NEXTSYS sys_number is a required modifier that specifies the number (from 0 to 254) of the system connected to the other end of the line. If you do not specify the NEXTSYS modifier, it defaults to an invalid value (255) and an operator message occurs during the initialization of the Expand line-handler process.
Configuring Direct-Connect and Satellite-Connect Lines Step 4: Start the Line-Handler Process In the next example, a device named $SAT1 is created for a single-line satelliteconnect line-handler process that uses a SWAN concentrator named S02. -> ADD DEVICE $ZZWAN.#SAT1, PROFILE SLHSAT, IOPOBJECT & $SYSTEM.SYSTEM.
Profile Modifiers Configuring Direct-Connect and Satellite-Connect Lines Profile Modifiers This subsection lists the modifiers provided for configuring special features. It also describes default values and value ranges for the modifiers contained in the PEXQSSWN and PEXQSSAT profiles. Note. Different profiles are provided for direct-connect and satellite-connect lines that are part of a multi-line path; these profiles are described in Section 13, Configuring Multi-Line Paths.
Configuring Direct-Connect and Satellite-Connect Lines PEXQSSWN and PEXQSSAT Modifiers Table 7-1.
Configuring Direct-Connect and Satellite-Connect Lines PEXQSSWN and PEXQSSAT Modifiers Table 7-1. PEXQSSWN and PEXQSSAT Modifiers (page 3 of 3) Modifier Default Value Range of Values LINEPRIORITY 1 1 through 9 LINETF 0 0 through 186 NEXTSYS1 255 0 to 254 OSSPACE 32767 3072 through 32767 OSTIMEOUT 300 10 through 32767 PATHBLOCKBYTES 0 0 through 4095 PATHPACKETBYTES 1024 0 through 4095 PATHTF 0 0 through 186 PROGRAM $SYSTEM.CSSnn. C1097P00 (directconnect) $SYSTEM.CSSnn.
8 Configuring Expand-Over-IP Lines The Expand-over-IP line-handler process provides connectivity to an Internet Protocol (IP) network. The Expand-over-IP line-handler process uses the services of the NonStop TCP/IP subsystem to provide Expand-over-IP connections. NonStop TCP/IPv6 and CIP support IP version 6 (IPv6) communications. IPv6 supports a larger, 128-bit (16-byte) IP address that helps to address the growing number of machines and devices on the Internet.
Required Hardware and Software Configuring Expand-Over-IP Lines Required Hardware and Software Several hardware and software components are required in addition to the Expandover-IP line-handler process to provide Expand-over-IP connectivity. Note. The CLIM hardware component is supported only on systems running J06.04 and later J-series RVUs. Figure 8-1 shows the relationship between the Expand subsystem, the NonStop TCP/IP subsystem and the LAN adapter or CLuster I/O Module (CLIM).
QIO Subsystem Configuring Expand-Over-IP Lines Figure 8-2 illustrates the required components when an ATM 3 ServerNet adapter (ATM3SA) is used to provide connectivity to an IP network. In this configuration, the TCP/IP process can only be NonStop TCP/IP; NonStop TCP/IPv6 and CIP do not support ATM communications. Figure 8-2.
Configuring Expand-Over-IP Lines NonStop TCP/IP Process NonStop TCP/IP Process The Expand-over-IP line-handler process uses the services of a NonStop TCP/IP process to provide TCP/IP connectivity. The NonStop TCP/IP process and SUBNET associated with the Expand-over-IP line-handler process must be defined and started before the Expand-over-IP line-handler process can be started. It must be configured in the same processor pair as the Expand-over-IP line-handler process.
Configuring Expand-Over-IP Lines Local Area Network (LAN) Driver and Interrupt Handlers (DIHs) greater bandwidth and fault tolerance. However, all elements, including the network itself, must have redundancy to obtain full benefit of the configurations.
Configuring Expand-Over-IP Lines Asynchronous Transfer Mode (ATM) Subsystem Asynchronous Transfer Mode (ATM) Subsystem NonStop TCP/IP processes might interface to an IP network through the Asynchronous Transfer Mode (ATM) subsystem. The ATM subsystem provides software that allows NonStop TCP/IP processes to connect to an ATM ServerNet adapter (ATM3SA).
Topology Considerations Configuring Expand-Over-IP Lines Topology Considerations In a single-line path configuration, you configure one Expand-over-IP line-handler process for each path to an adjacent node. In a multi-CPU path configuration, you configure multiple Expand-over-IP line-handler processes, usually in separate processors, for each path to an adjacent node. In a multi-line path configuration, you configure a path that consists of multiple lines between two adjacent nodes.
Configuring Expand-Over-IP Lines Summary of Configuration Steps Summary of Configuration Steps After all hardware and software requirements have been met (see Required Hardware and Software on page 8-2 for details), configuring and starting a single-line Expandover-IP line-handler process involves these steps. Use Steps A or B depending on which version of TCP/IP you want to use.
Step 1 (A): Select a Process and SUBNET for NonStop TCP/IP Use Configuring Expand-Over-IP Lines Step 1 (A): Select a Process and SUBNET for NonStop TCP/IP Use Note. These instructions assume that a NonStop TCP/IP process has already been created. For more information on creating NonStop TCP/IP processes, see the TCP/IP Configuration and Management Manual. A NonStop TCP/IP SUBNET associates a NonStop TCP/IP process with a connection to a network and an IP address.
Select a SUBNET for NonStop TCP/IP Configuring Expand-Over-IP Lines Select a SUBNET for NonStop TCP/IP You can use the SCF INFO SUBNET command to determine if a SUBNET has been configured for the NonStop TCP/IP process you plan to associate with the Expandover-IP line-handler process. Example 8-2 shows an example of an SCF INFO SUBNET command for a NonStop TCP/IP process named $ZTC01. Example 8-2. SCF INFO SUBNET Command 2-> INFO SUBNET $ZB01A.#* TCPIP Info SUBNET \NODEA.$ZB01A.
Configuring Expand-Over-IP Lines Step 1 (B): Select a Process and SUBNET for NonStop TCP/IPv6 Use After the SUBNET is defined, it must be started using the SCF START SUBNET command. This SCF START SUBNET command shown starts the SUBNET named #SN1: -> START SUBNET $ZTC01.#SN1 Note. You must also perform this step on the destination system before you can define the local Expand-over-IP line-handler process.
Configuring Expand-Over-IP Lines Select a SUBNET for NonStop TCP/IPv6 Use Example 8-3 shows a sample result of the SCF INFO SUBNET, DETAIL command. Example 8-3. SCF INFO SUBNET, DETAIL Command TCPIPV6 Detailed Info SUBNET \NODEA.$ZZTCP.#ZPTMF.* AF_INET: Name Devicename *IPADDRESS/DST_IPADDR TYPE *SUBNETMASK SN116 \NODEA.FEF0A 172.10.188.140 ETHERNET %HFFFFFF00 Trace Status ........ OFF Trace Filename ...... Interface MTU ....... 1500 ---Multicast Groups-----State--224.0.0.1 STARTED LNP... $ZB01A Index...
Select a TCP6SAM Process Configuring Expand-Over-IP Lines only TCP6SAM process that has access to the LNP that SUBNET SN116 and its IP address 172.10.188.140 form. Note also that SN117 shows DEFAULT in the LNP field. If you want to use the default LNP, select a SUBNET that has DEFAULT in the LNP field. Select a TCP6SAM Process The TCP/IP socket access method (TCP6SAM) is the process that provides access to the NonStop TCP/IPv6 environment.
Configuring Expand-Over-IP Lines Creating an Ethernet Subnet 1. Issue the SCF INFO SUBNET $ZZTCP.*, DETAIL command. 2. Identify all TCP6SAM processes that are listed in the LNP field of the SUBNET display and make a note of these process names. 3. Issue the SCF LISTDEV TCPIP command. 4. Use your list of TCP6SAM names to eliminate the LNP-assigned TCP6SAM processes. The remaining TCP6SAM process(es) is associated with the default LNP. This process has access only to the SUBNETs in the default partition.
Step 1 (C): Select a Process and SUBNET for CIP Use Configuring Expand-Over-IP Lines Step 1 (C): Select a Process and SUBNET for CIP Use Note. The following instructions assume that a CIP environment has already been started. For information on starting a CIP environment, see the Cluster I/O Protocols (CIP) Configuration and Management Manual. Step 1 (C) is for use with CIP only.
Obtain an IP Address to associate with your Expand Line- Handler Process Configuring Expand-Over-IP Lines Example 8-6. SCF INFO SUBNET $ZSAM0 CIP Info SUBNET $\MYSYS.$ZSAM0.* Name Devicename *IPADDRESS TYPE *SUBNETMASK SuName QIO *R #SN0001 lo 127.0.0.1 LOOP-BACK %HFF000000 OFF N #SN0002 DL395N.eth1 172.17.190.101 ETHERNET %HFFFFFF00 ON N #SN0003 DL385N.ETH2 172.17.190.102 ETHERNET %HFFFFFF00 ON N #SN0004 DL385N.ETH3 172.17.190.103 ETHERNET %HFFFFFF00 ON N #SN0005 DL385N.
Step 2 (A): Identify an Available UDP Port Number Configuring Expand-Over-IP Lines Step 2 (A): Identify an Available UDP Port Number A User Datagram Protocol (UDP) port number enables multiple applications to use the same IP address. An Expand-over-IP line-handler process might share a local IP address with other applications or with other Expand-over-IP processes. Each must specify a different port number.
Configuring Expand-Over-IP Lines Step 2 (B): Identify an Available UDP Port Number for NonStop TCP/IPv6 Use you define the Expand-over-IP line-handler process in Step 4: Create the Line-Handler Process. Note. You must also perform this step on the destination system before you can define the local Expand-over-IP line-handler process. The destination UDP port number must be specified when the local Expand-over-IP line-handler process is defined.
Step 2 (B): Identify an Available UDP Port Number for NonStop TCP/IPv6 Use Configuring Expand-Over-IP Lines Example 8-8. SCF STATUS MON Command 3-> STATUS MON $ZZTCP.* TCPIPV6 Status MON \NODEC.$ZZTCP.#ZPTM0 Status: STARTED, MASTER PID............ ( 0,275) Proto State UDP Laddr 16.107.187.84 Lport 5550 Faddr 0.0.0.0 Fport * SendQ 0 RecvQ 0 Faddr Fport SendQ RecvQ Laddr Lport Faddr Fport 16.107.187.84 21600 0.0.0.
Step 2 (C): Identify an available UDP Port Number for CIP Use Configuring Expand-Over-IP Lines Step 2 (C): Identify an available UDP Port Number for CIP Use A User Datagram Protocol (UDP) port number enables multiple applications to use the same IP address. An Expand-over-IP line-handler process might share a local IP address with other applications or with other Expand-over-IP processes. Each must specify a different port number.
Configuring Expand-Over-IP Lines Step 2 (C): Identify an available UDP Port Number for CIP Use The LISTOPENS MON command does not display which IP addresses the port numbers are associated with. However, the LISTOPENS PROVIDER $ZZCIP., DETAIL command displays IP addresses with the ports for the specified Provider. You might need the INFO PROVIDER $ZZCIP.* command to find the PROVIDER name associated with the CIPSAM name.
Configuring Expand-Over-IP Lines Step 3: Create a Profile for the Line-Handler Process Step 3: Create a Profile for the Line-Handler Process You can create a profile for a single-line Expand-over-IP line-handler process using the PEXQSIP profile. This profile is provided in the $SYSTEM.SYSnn subvolume. You can also create a new profile from an existing profile, or you can create your own profile. For complete information about profiles, see the WAN Subsystem Configuration and Management Manual.
Configuring Expand-Over-IP Lines Example Example In this example, a profile named SLHIP is created for a single-line Expand-over-IP linehandler process using the PEXQSIP profile. The AFTERMAXRETIRES_DOWN modifier is set in the profile. -> ADD PROFILE $ZZWAN.#SLHIP, FILE $SYSTEM.SYS01.PEXQSIP, & AFTERMAXRETRIES_DOWN Step 4: Create the Line-Handler Process You create a single-line Expand-over-IP line-handler process by adding it as a device to the WAN subsystem. Note.
Configuring Expand-Over-IP Lines ADD DEVICE Command PROFILE profile_name is the name of the profile you created for this Expand line-handler process in Step 3: Create a Profile for the Line-Handler Process. CPU cpunumber indicates the processor where this Expand line-handler process runs. This must be the same processor as configured for the primary NonStop TCP/IP process. If you are using NonStop TCP/IPv6 or CIP, you need not have the line-handler on the same CPU as the TCP6SAM or CIPSAM process.
Configuring Expand-Over-IP Lines ADD DEVICE Command SRCIPADDR src_ipaddr if IPVER is IPv4 (the default), this is a required modifier that specifies an IP address associated with the NonStop TCP/IP, CIPSAM, or TCP6SAM process used by this Expand-over-IP line-handler process. This is the IP address you selected in Step 1 (A): Select a Process and SUBNET for NonStop TCP/IP Use, Step 1 (B): Select a Process and SUBNET for NonStop TCP/IPv6 Use, or Step 1 (C): Select a Process and SUBNET for CIP Use.
Configuring Expand-Over-IP Lines Considerations Use. The address must be specified by number (for example, 31CA:B145:5489:1034:1784:B245:4029:1257). It is not validated and need not be accessible. (This attribute applies to NonStop TCP/IPv6 and CIP only.) V6DESTIPADDR v6destip-address if IPVER is IPv6, this is a required modifier that specifies the IP address used by the remote (destination) Expand-over-IP line-handler process.
Configuring Expand-Over-IP Lines Example Example In this example, a device named $IPLIN1 is created for a single-line Expand-over-IP line-handler process. The PATHPACKETBYTES modifiers are recommended for Expand-over-IP lines. (The default for the L4EXTPACKETS_ON and L4CONGCTRL_ON modifiers is ON.) -> ADD DEVICE $ZZWAN.#IPLIN1, PROFILE SLHIP, IOPOBJECT & $SYSTEM.SYSTEM.LHOBJ, CPU 0, ALTCPU 1, TYPE (63,0), & RSIZE 0, PATHTF 3, NEXTSYS 251, ASSOCIATEDEV $ZB01A, & DESTIPADDR 130.252.31.
Configuring Expand-Over-IP Lines Step 6: Start the Line Step 6: Start the Line To start an Expand-over-IP line, use the Expand subsystem SCF START LINE command. The command syntax is: START LINE $device_name device_name is the device name of the Expand-over-IP line-handler process. The successful completion of this command leaves the line in the STARTED state.
Configuring Expand-Over-IP Lines Add a Configured Tunnel for an Expand Line Example 8-11 shows how to add an Expand line from \NodeB to \NodeC. Example 8-11. Add an Expand Line to \NodeC allow all errors abort line $giplco1 stop device $zzwan.#giplco1 delete device $zzwan.#giplco1 == Add profile of IP line ADD PROFILE $zzwan.#afkslhip, file $data00.t9057afk.sippfr == Add Expand line handler. ADD DEVICE $ZZWAN.#giplco1, CPU 2, ALTCPU 3, PROFILE afkslhip,& IOPOBJECT $data00.t9057afk.
Configuring Expand-Over-IP Lines Add a Configured Tunnel for an Expand Line for CIP Example 8-13 shows how to add an Expand line from \NodeC to \NodeB. Example 8-13. Add an Expand Line to \NodeB allow all errors abort line $giplba1 stop device $zzwan.#giplba1 delete device $zzwan.#giplba1 == Add profile of IP line ADD PROFILE $zzwan.#afkslhip, file $data00.t9057afk.sippfr == Add Expand line handler. ADD DEVICE $ZZWAN.#giplba1, CPU 2, ALTCPU 3, PROFILE afkslhip,& IOPOBJECT $data00.t9057afk.
Configuring Expand-Over-IP Lines Add a Configured Tunnel for an Expand Line for CIP Example 8-15 shows how to add an Expand line from \NodeB to \NodeC. Example 8-15. Add an Expand Line to \NodeC allow all errors abort line $giplco1 stop device $zzwan.#giplco1 delete device $zzwan.#giplco1 == Add profile of IP line ADD PROFILE $zzwan.#afkslhip, file $data00.t9057afk.sippfr == Add Expand line handler. ADD DEVICE $ZZWAN.#giplco1, CPU 2, ALTCPU 3, PROFILE afkslhip,& IOPOBJECT $data00.t9057afk.
Configuring Expand-Over-IP Lines Profile Modifiers Example 8-17 shows how to add an Expand line from \NodeC to \NodeB. Example 8-17. Add an Expand Line to \NodeB allow all errors abort line $giplba1 stop device $zzwan.#giplba1 delete device $zzwan.#giplba1 == Add profile of IP line ADD PROFILE $zzwan.#afkslhip, file $data00.t9057afk.sippfr == Add Expand line handler. ADD DEVICE $ZZWAN.#giplba1, CPU 2, ALTCPU 3, PROFILE afkslhip,& IOPOBJECT $data00.t9057afk.
Configuring Expand-Over-IP Lines Modifiers for Special Features L4CONGCTRL is a path parameter and the path profile sets L4CONGCTRL_OFF because it is shared by all line types. Therefore, multi-line IP paths default to L4CONGCTRL_OFF and must specify L4CONGCTRL_ON. The L4CONGCTRL_ON modifier is also recommended for Expand line-handler processes that are part of a multi-CPU path.
PEXQSIP Modifiers Configuring Expand-Over-IP Lines For a complete description of the modifiers listed in this table, see Section 16, Expand Modifiers. Table 8-1. PEXQSIP Modifiers for Expand-over-IP Lines (page 1 of 2) Modifier Default Value Range of Values AFTERMAXRETRIES_DOWN AFTERMAXRETRIES_PASSIVE 3 ASSOCIATEDEV1 None Any 8-character string COMPRESS_OFF COMPRESS_ON 3 CONNECTTYPE_ACTIVEANDPASSIVE 3 CONNECTTYPE_PASSIVE DESTIPADDR2 0.0.0.
PEXQSIP Modifiers Configuring Expand-Over-IP Lines Table 8-1. PEXQSIP Modifiers for Expand-over-IP Lines (page 2 of 2) Modifier Default Value Range of Values PATHTF 0 0 through 186 QUALITYTHRESHOLD 0 0 to 99 QUALITYTIMER 60 0 to 77600 (12hrs) RETRYPROBE 19 1 through 255 RXWINDOW 7 2 through 15 SPEED 0 0 through 224000 SPEEDK NOT_SET 0 through 4,000,000,000 SRCIPADDR2 0.0.0.
Configuring Expand-Over-IP Lines Expand Configuration and Management Manual — 529522-013 8 - 36 PEXQSIP Modifiers
9 Configuring Expand-Over-ATM Lines The Expand-over-ATM line-handler process provides connectivity to an Asynchronous Transfer Mode (ATM) network. In addition, the Expand-over-ATM line-handler process can use the services of the ServerNet LAN systems access (SLSA) subsystem to provide Expand-over-ATM connections. The ATM subsystem provides a PVC and SVC connection, whereas the SLSA subsystem provides an ATMSAP with lifname connection that enables you to manage PVC connections under SLSA.
Required Hardware and Software Configuring Expand-Over-ATM Lines Required Hardware and Software Several hardware and software components are required in addition to the Expandover-ATM line-handler process to provide Expand-over-ATM connectivity. These components are illustrated in Figure 9-1 and are explained in these subsections. Figure 9-1.
Configuring Expand-Over-ATM Lines ATM Subsystem ATM Subsystem ATM is a cell-switching and multiplexing technology that combines the benefits of circuit switching (constant transmission delay and guaranteed capacity) with those of packet switching (flexibility and intermittent traffic). The ATM subsystem is the HP implementation of the ATM technology. The ATM subsystem supports the ATM UserNetwork Interface (UNI) Specification Version 3.0 over a 155 Mbps SONET STS-3c connection.
Topology Considerations Configuring Expand-Over-ATM Lines Topology Considerations In a single-line configuration, you configure one Expand-over-ATM line-handler process for each path to an adjacent node. In a multi-CPU path configuration, you configure multiple Expand-over-ATM line-handler processes, usually in separate processors, for each path to an adjacent node. In a multi-line path configuration, you configure a path that consists of multiple lines between adjacent nodes.
Summary of Configuration Steps Configuring Expand-Over-ATM Lines Summary of Configuration Steps After all hardware and software requirements have been met (see Required Hardware and Software on page 9-2 for details), configuring and starting a single-line Expandover-ATM line-handler process involves these steps: Step Tool Used Step 1: Identify the ATM Connection SCF interface to the ATM subsystem Step 2: Create a Profile for the Line-Handler Process SCF interface to the WAN subsystem Step 3: Create
Configuring an Expand Line-Handler Process That Uses a PVC Configuring Expand-Over-ATM Lines Configuring an Expand Line-Handler Process That Uses a PVC If your Expand-over-ATM line-handler process will use a PVC connection, you must identify the PVC you plan to use. The SCF INFO PVC command displays the configured name of a PVC. Example 9-1 shows an example of an SCF INFO PVC command for an ATM line named $AM1. Example 9-1. SCF INFO PVC Command 1-> INFO PVC $AM1.#IP.* ATM Info PVC Name $AM1.#IP.
Configuring an Expand Line-Handler Process That Uses an SVC Configuring Expand-Over-ATM Lines your local and remote Expand-over-ATM line-handler processes. Specifying a selector byte when configuring an Expand-over-ATM line-handler process is described in Step 3: Create the Line-Handler Process.
Configuring an Expand Line-Handler Process That Uses an SVC Configuring Expand-Over-ATM Lines Specifying an ATM address when configuring an Expand-over-ATM line-handler process in described in Step 3: Create the Line-Handler Process.
Configuring an Expand Line-Handler Process That Uses ATMSAP Configuring Expand-Over-ATM Lines Configuring an Expand Line-Handler Process That Uses ATMSAP The SLSA ATMSAP connection offers an ATM Native Mode network interconnect support similar to that offered by the PVC object within the ATM subsystem. Expand issues native mode frames directly to the ATM product via a LIF associated with an ATMSAP object. Figure 9-3 illustrates ATMSAP use by Expand. Figure 9-3.
Configuring an Expand Line-Handler Process That Uses ATMSAP Configuring Expand-Over-ATM Lines Verifying the Line-Handler Process Example 9-4 shows an example of an Expand subsystem SCF INFO LINE command with the DETAIL option of an Expand-over-ATM line-handler process named $ATM2BAT and a CallType of ATMSAP. Example 9-4. Expand Subsystem SCF INFO LINE, DETAIL Command for ATMSAP -> INFO LINE $ATM2BAT, DETAIL EXPAND Detailed Info L2Protocol Framesize.... *LinePriority... *DownIfBadQuality *Txwindow...
Configuring Expand-Over-ATM Lines Step 2: Create a Profile for the Line-Handler Process Step 2: Create a Profile for the Line-Handler Process You can create a profile for a single-line Expand-over-ATM line-handler process using the PEXQSATM profile. This profile is provided in the $SYSTEM.SYSnn subvolume. You can also create a new profile from an existing profile, or you can create your own profile. For complete information about profiles, see the WAN Subsystem Configuration and Management Manual.
Configuring Expand-Over-ATM Lines Example Example In this example, a profile named SLHATM is created for a single-line Expand-over-ATM line-handler process using the PEXQSATM profile. The AFTERMAXRETIRES_DOWN modifier is set in the profile. -> ADD PROFILE $ZZWAN.#SLHATM, FILE $SYSTEM.SYS01.PEXQSATM, & AFTERMAXRETRIES_DOWN Step 3: Create the Line-Handler Process You create a single-line Expand-over-ATM line-handler process by adding it as a device to the WAN subsystem. Note.
Configuring Expand-Over-ATM Lines ADD DEVICE Command Syntax for SVC Connections Use this command syntax if the Expand-over-ATM line-handler process will use an SVC connection: ADD , , , , , , , , , , , , [, DEVICE $ZZWAN.#device_name IOPOBJECT $SYSTEM.SYSTEM.
Configuring Expand-Over-ATM Lines ADD DEVICE Command CPU cpunumber indicates the processor where this Expand line-handler process will normally run. ALTCPU altcpunumber indicates the processor where the backup Expand line-handler process will normally run. TYPE (63,0) is the device type and subtype for this Expand line-handler process. The device type is always 63 for Expand line-handler processes. The subtype is 0 for singleline Expand-over-ATM line-handler processes.
Configuring Expand-Over-ATM Lines ADD DEVICE Command PVCNAME pvc-name is the name of the permanent virtual circuit (PVC) that will be used. This is the PVC name you identified in Step 1: Identify the ATM Connection on page 9-5. For example, PVC01. This modifier is only applicable to Expand-over-ATM line-handler processes that use PVC connections. ATMSEL selector-byte is a hexadecimal selector byte for the ATM line used by this Expand-over-ATM line-handler process.
Configuring Expand-Over-ATM Lines Considerations modifier_value is the value you want to assign to the optional modifier specified by modifier_keyword. modifier_value assigns a value to modifier_keyword in the device record for this Expand line-handler process. Default values and ranges of values for modifiers in the PEXQSATM profile are described in Profile Modifiers on page 9-18. Considerations • • Not all modifiers have associated values (for example, L4EXTPACKETS_ON).
Configuring Expand-Over-ATM Lines Step 4: Start the Line-Handler Process In the last example, a device named ATMLIN3 is created for a single-line Expand-overATM line-handler process that uses an ATMSAP connection through the SLSA subsystem. -> ADD DEVICE $ZZWAN.#ATMLIN3, PROFILE SLHATM, IOPOBJECT & $SYSTEM.SYSTEM.
Configuring Expand-Over-ATM Lines Profile Modifiers Profile Modifiers This subsection lists the recommended modifiers for single-line Expand-over-ATM line-handler processes and describes the modifiers provided for configuring special features. It also describes default values and value ranges for all the modifiers contained in the PEXQSATM profile. Note.
Modifiers for Special Features Configuring Expand-Over-ATM Lines L4EXTPACKETS_ON Default: Units: Range: ON Not applicable ON or OFF This modifier is required for the variable packet size and congestion control features (see L4CONGCTRL_ON and PATHPACKETBYTES n above). It is also required for Expand line-handler processes that are part of multi-CPU path. The L4EXTPACKETS_ON modifier is described in detail in Section 16, Expand Modifiers.
PEXQSATM Modifiers Configuring Expand-Over-ATM Lines Table 9-1. PEXQSATM Modifiers for Expand-over-ATM Lines (page 2 of 3) Modifier Default Value Range of Values CALLTYPE_ATMSAP4 COMPRESS_OFF7 COMPRESS_ON 3 CONNECTTYPE_ACTIVEANDPASSIVE 3 CONNECTTYPE_PASSIVE DESTATMADDR2 (ISONSAP: %H00...
PEXQSATM Modifiers Configuring Expand-Over-ATM Lines Table 9-1. PEXQSATM Modifiers for Expand-over-ATM Lines (page 3 of 3) Modifier Default Value Range of Values RETRYPROBE 19 1 through 255 RXWINDOW 7 2 through 15 SPEED 0 0 or 1200 through 224000 SPEEDK NOT_SET 0 through 4,000,000,000 STARTUP_OFF 3 STARTUP_ON SUPERPATH_OFF 3 SUPERPATH_ON TIMERPROBE 1 1 through 32767 TIMERRECONNECT 30 30 through 32767 TXWINDOW 7 2 through 25 1. This is a required modifier. 2.
Configuring Expand-Over-ATM Lines Expand Configuration and Management Manual — 529522-013 9 - 22 PEXQSATM Modifiers
10 Configuring Expand-Over-X.25 Lines X.25 is a standard for private and public networks that use packet-switching technology. Expand-over-X.25 connections are provided by the HP X.25 Access Method (X25AM) product. The Expand-over-X.25 line-handler process uses the NETNAM protocol to access the network access method (NAM) interface provided by an X25AM line-handler process. An Expand-over-X.
Required Hardware and Software Configuring Expand-Over-X.25 Lines Required Hardware and Software Several hardware and software components are required in addition to the Expandover-X.25 line-handler process to provide Expand-over-X.25 connectivity. These components are illustrated in Figure 10-1 and are explained in these subsections. Figure 10-1. Expand-Over-X.25 Line-Handler Process Components Processor Expand-over-X.
Configuring Expand-Over-X.25 Lines X25AM Line-Handler Process X25AM Line-Handler Process The Expand-over-X.25 line-handler process uses the services of an X25AM line-handler process to provide access to X.25 packet-switched data networks (PSDNs). Each X25AM line-handler process controls a single data communications line and supports both permanent virtual circuits (PVCs) and switched virtual circuits (SVCs). The X25AM line-handler process associated with the Expand-over-X.
Configuring Expand-Over-X.25 Lines Local Area Network (LAN) Driver and Interrupt Handlers (DIHs) Local Area Network (LAN) Driver and Interrupt Handlers (DIHs) NonStop TCP/IP processes can interface to the network through the ServerNet LAN Systems Access (SLSA) subsystem. The SLSA subsystem provides QIO-based driver and interrupt handlers (DIHs) that allow NonStop TCP/IP processes to connect to a LAN adapter. The SLSA subsystem is preconfigured and started during the system load sequence.
Topology Considerations Configuring Expand-Over-X.25 Lines Topology Considerations An Expand-over-X.25 network must be configured as a logical fully connected mesh. In a single-line path configuration, you configure one Expand-over-X.25 line-handler process for each destination node in the network. In a multi-CPU configuration, you configure multiple Expand-over-X.25 line-handler processes, usually in separate processors, for each destination node in the network.
Summary of Configuration Steps Configuring Expand-Over-X.25 Lines Summary of Configuration Steps After all hardware and software requirements have been met (see Required Hardware and Software on page 10-2 for details), configuring and starting a single-line Expandover-X.25 line-handler process involves these steps.
Configuring Expand-Over-X.25 Lines Step 1: Add a NAM Subdevice to the X25AM Line Step 1: Add a NAM Subdevice to the X25AM Line Note. This procedure assumes that an X25AM line-handler process has already been created. To create an such a process, you must add it as a device to the WAN subsystem. For complete information about creating X25AM processes, see the WAN Subsystem Configuration and Management Manual. An Expand-over-X.25 line-handler process must have access to a NAM subdevice of an X25AM line.
Configuring Expand-Over-X.25 Lines Step 3: Create a Profile for the Expand-Over-X.25 Line-Handler Process Step 3: Create a Profile for the Expand-OverX.25 Line-Handler Process You can create a profile for a single-line Expand-over-X.25 line-handler process using the PEXQSNAM profile. This profile is provided in the $SYSTEM.SYSnn subvolume. You can also create a new profile from an existing profile, or you can create your own profile.
Configuring Expand-Over-X.25 Lines Example Example In this example, a profile named SLHX25 is created for a single-line Expand-over-X.25 line-handler process using the PEXQSNAM profile. The COMPRESS_OFF modifier is added to the profile. -> ADD PROFILE $ZZWAN.#SLHX25, FILE $SYSTEM.SYS01.PEXQSNAM, & COMPRESS_OFF Step 4: Create the Expand-Over-X.25 Line-Handler Process You create a single-line Expand-over-X.25 line-handler process by adding it as a device to the WAN subsystem. Note.
Configuring Expand-Over-X.25 Lines ADD DEVICE Command CPU cpunumber indicates the processor where this Expand line-handler process will normally run. ALTCPU altcpunumber indicates the processor where the backup Expand line-handler process will normally run. TYPE (63,0) is the device type and subtype for this Expand line-handler process. The device type is always 63 for Expand line-handler processes. The subtype is 0 for singleline Expand-over-X.25 line-handler processes.
Configuring Expand-Over-X.25 Lines Considerations modifier_value is the value you want to assign to the optional modifier specified by modifier_keyword. modifier_value assigns a value to modifier_keyword in the device record for this Expand line-handler process. Default values and ranges of values for modifiers in the PEXQSNAM profile are described in Profile Modifiers on page 10-13. Considerations • • Not all modifiers have associated values (for example, L4EXTPACKETS_ON).
Configuring Expand-Over-X.25 Lines Step 5: Start the Expand-Over-X.25 Line-Handler Process Step 5: Start the Expand-Over-X.25 Line-Handler Process To start a single-line Expand-over-X.25 line-handler process, use the WAN subsystem SCF START DEVICE command. The command syntax is: START DEVICE $ZZWAN.#device_name $ZZWAN.device_name specifies, via the WAN subsystem, the device name of the Expand-over-X.25 line-handler process.
Configuring Expand-Over-X.25 Lines Profile Modifiers Profile Modifiers This subsection lists the recommended modifiers for Expand-over-X.25 line-handler processes and describes the modifiers provided for configuring special features. It also describes default values and value ranges for all the modifiers contained in the PEXQSNAM profile. Note. A different profile is provided for Expand-over-X.
X25AM Line-Handler Process Modifiers Configuring Expand-Over-X.25 Lines For configuration considerations for these features, see Section 17, Subsystem Description. For more information on the advantages and disadvantages of these features, see Section 3, Planning a Network Design. The PATHBLOCKBYTES, PATHPACKETBYTES, L4CONGCTRL_ON, SUPERPATH_ON, and L4CWNDCLAMP modifiers are described in detail in Section 16, Expand Modifiers.
PEXQSNAM Modifiers Configuring Expand-Over-X.25 Lines Table 10-1. PEXQSNAM Modifiers for Expand-over-X.
PEXQSNAM Modifiers Configuring Expand-Over-X.25 Lines Table 10-1. PEXQSNAM Modifiers for Expand-over-X.25 Lines (page 3 of 3) Modifier Default Value Range of Values TIMERRECONNECT 30 0 through 32767 TXWINDOW 4 2 through 7 1. This is a required modifier. It has no default value. 2. This is a required modifier. The default value is invalid and must be changed.
11 Configuring Expand-Over-SNA Lines Systems Network Architecture (SNA) was developed by IBM for connecting IBM systems and networks. Expand-over-SNA connections are provided with the HP SNAX/Advanced Peer Networking (SNAX/APN) product. The Expand-over-SNA line-handler process uses the NETNAM protocol to access the network access method (NAM) interface provided by a SNAX/APN line-handler process.
Required Hardware and Software Configuring Expand-Over-SNA Lines Required Hardware and Software Several hardware and software components are required in addition to the Expandover-SNA line-handler process to provide Expand-over-SNA connectivity. These components are illustrated in Figure 11-1 and are explained in these subsections. Figure 11-1.
Configuring Expand-Over-SNA Lines SNAX/APN Line-Handler Process SNAX/APN Line-Handler Process The Expand-over-SNA line-handler process uses the services of a SNAX/APN line-handler process to provide access to an IBM SNA network. The SNA network can be a traditional network of host mainframes and front end processors, an advanced peer-to-peer network of AS400 systems or other workstations, or a mix of these types of networks.
Configuring Expand-Over-SNA Lines NonStop TCP/IP Process NonStop TCP/IP Process The NonStop TCP/IP subsystem provides TCP/IP data communications connectivity. NonStop TCP/IP processes are used by the LAN adapters and SWAN concentrators. The NonStop TCP/IP processes that support these adapters and SWAN concentrators are preconfigured and started during the system load sequence.
Topology Considerations Configuring Expand-Over-SNA Lines Topology Considerations An Expand-over-SNA network must be configured as a logical fully connected mesh. In a single-line path configuration, you configure one Expand-over-SNA line-handler process for each destination node in the network. In a multi-CPU configuration, you configure multiple Expand-over-SNA line-handler processes, usually in separate processors, for each destination node in the network.
Configuring Expand-Over-SNA Lines Summary of Configuration Steps Summary of Configuration Steps After all hardware and software requirements have been met (see Required Hardware and Software on page 11-2 for details), configuring and starting a single-line Expandover-SNA line-handler process involves these steps: Step Tool Used Step 1: Add the SNAX/APN Line SCF interface to the SNAX/APN subsystem Step 2: Add the LUs for the SNAX/APN Line SCF interface to the SNAX/APN subsystem Step 3: Start the SNAX
Configuring Expand-Over-SNA Lines Step 1: Add the SNAX/APN Line Step 1: Add the SNAX/APN Line Note. These instructions assume that a SNAX/APN line-handler process has already been created. To create such a process, you must add it as a device to the WAN subsystem. For more information on creating SNAX/APN line-handler processes, see the WAN Subsystem Configuration and Management Manual.
Configuring Expand-Over-SNA Lines Step 2: Add the LUs for the SNAX/APN Line Step 2: Add the LUs for the SNAX/APN Line You must configure a local and a remote logical unit (LU) for the SNAX/APN line. The Expand-over-SNA line-handler process is configured to use a particular local LU. You use the SNAX/APN subsystem SCF ADD LU command to add the local LU. For example, this command creates a local LU with a subdevice name of #LLUA for the SNAX/APN line $SNAPA: -> ADD LU $SNAPA.
Example Configuring Expand-Over-SNA Lines Example Figure 11-3 shows the SCF commands used to configure a SNAX/APN line, local LU, remote PU, and remote LU at two nodes in an Expand network. Figure 11-3. SNAX/APN Line Configuration Example System \A Expand Line-Handler Process SNAX/APN Line-Handler Process ($SNAPA) SWAN SNA Network SCF Commands for System \A ADD LINE $SNAPA , RECSIZE 524 , MAXPUS 1 , MAXLUS 30 , STATION PRIMARY , MAXLOCALLUS 10 , POLLINT 0.01 ADD LU $SNAPA.
Configuring Expand-Over-SNA Lines Step 3: Start the SNAX/APN Line Step 3: Start the SNAX/APN Line Before you can start the Expand-over-SNA line, the SNAX/APN line (and its associated PUs and LUs) must be started. To start a SNAX/APN line, use the SNAX/APN subsystem SCF START LINE command. This command starts a SNAX/APN line named $SNAPA and its associated PUs and LUs: -> START LINE $SNAPA, SUB ALL For details about starting SNAX/APN lines, see the SNAX/XF and SNAX/APN Configuration and Management Manual.
Example Configuring Expand-Over-SNA Lines modifier_keyword is the name of a modifier in profile_name. Modifier names in the PEXQSNAM profile are listed in Profile Modifiers on page 11-15. modifier_value is the value you want to assign to the modifier specified by modifier_keyword. Specifying a modifier_value assigns a new value to modifier_keyword in profile_name. Default values and ranges of values for modifiers in the PEXQSNAM profile are described in Profile Modifiers on page 11-15.
Configuring Expand-Over-SNA Lines ADD DEVICE Command $ZZWAN.#device_name specifies, via the WAN subsystem, the device name of the Expand line-handler process to add. IOPOBJECT $SYSTEM.SYSnn.LHOBJ is the name of the object file containing the executable object for code for an Expand line-handler process. This value must be $SYSTEM.SYSnn.LHOBJ.
Configuring Expand-Over-SNA Lines Considerations NEXTSYS sys_number is a required modifier that specifies the number (from 0 through 254) of the system connected to the other end of the line. If you do not specify NEXTSYS, this modifier defaults to an invalid value (255) and an operator message occurs during the initialization of the Expand-over-SNA line-handler process.
Configuring Expand-Over-SNA Lines Step 6: Start the Expand-Over-SNA Line-Handler Process In the next example, the same device is created as part of a multi-CPU path. The SUPERPATH_ON and L4EXTPACKETS_ON modifiers are required for line-handler processes that are part of a multi-CPU path. The L4CONGCTRL_ON modifier is recommended for Expand line-handler processes that are part of a multi-CPU path. -> ADD DEVICE $ZZWAN.#EXPS14, PROFILE SLHSNA, IOPOBJECT & $SYSTEM.SYSTEM.
Configuring Expand-Over-SNA Lines Profile Modifiers Profile Modifiers This subsection lists the recommended modifiers for Expand-over-SNA line-handler processes and describes the modifiers provided for configuring special features. It also describes default values and value ranges for all the modifiers contained in the PEXQSNAM profile. Note. A different profile is provided for Expand-over-SNA lines that are part of a multi-line path; this profile is described in Section 13, Configuring Multi-Line Paths.
PEXQSNAM Modifiers Configuring Expand-Over-SNA Lines For configuration considerations for these features, see Section 17, Subsystem Description. For more information on the advantages and disadvantages of these features, see Section 3, Planning a Network Design. The PATHBLOCKBYTES, PATHPACKETBYTES, L4CONGCTRL_ON, SUPERPATH_ON, and L4CWNDCLAMP modifiers are described in detail in Section 16, Expand Modifiers. PEXQSNAM Modifiers The disk file $SYSTEM.SYSnn.
PEXQSNAM Modifiers Configuring Expand-Over-SNA Lines Table 11-1.
Configuring Expand-Over-SNA Lines Expand Configuration and Management Manual — 529522-013 11 -18 PEXQSNAM Modifiers
12 Configuring Expand-Over-ServerNet Lines Note. The Integrity NonStop NS1000 server does not support ServerNet clusters. The Expand-over-ServerNet line-handler process provides connectivity to a ServerNet Cluster, which uses this process to provide a high-speed interconnect between systems over a limited geographic range. The Expand-over-ServerNet line-handler process uses the NETNAM protocol to access the network access method (NAM) interface of the ServerNet cluster monitor process, $ZZSCL.
Required Hardware and Software Configuring Expand-Over-ServerNet Lines Required Hardware and Software Several hardware and software components are required in addition to the Expandover-ServerNet line-handler process to provide Expand-over-ServerNet connectivity. Figure 12-1 illustrates the process of a local application sending a message to a remote node. Figure 12-1. Expand-Over-ServerNet Connectivity Components Local Node Processor 1 Processor 2 Application $ZZSCL Processor 3 Processor ...
Configuring Expand-Over-ServerNet Lines Expand Manager Process ($ZEXP) The components shown for this communications request and other components necessary for Expand-over-ServerNet lines are described in subsequent sections. Expand Manager Process ($ZEXP) The Expand subsystem requires that the Expand manager process ($ZEXP) be running during network operation. For more information on running this process, see Task 2: Start the Expand Manager Process on page 1-3.
Network Control Process ($NCP) Configuring Expand-Over-ServerNet Lines Network Control Process ($NCP) The network control process ($NCP) initiates and terminates server-to-server connections and maintains network-related system tables, including routing information. $NCP must be running at every node in the Expand network before Expand lines can be started. Cluster Switch A cluster switch is a 12-port network switch designed for use in ServerNet networks.
Configuring Expand-Over-ServerNet Lines ServerNet Cluster Product persistence manager starts a new ServerNet cluster monitor process. Because data traffic does not involve the ServerNet monitor, it could continue during this time. $ZZSCL must be configured and started before the Expand-over-ServerNet line-handler processes can be started. For more information on configuring $ZZSCL, see the ServerNet Cluster Manual. ServerNet Cluster Product Note.
Topology Considerations Configuring Expand-Over-ServerNet Lines Topology Considerations Note. The Integrity NonStop NS1000 server does not support ServerNet clusters. A ServerNet cluster must be configured as a logical fully connected mesh—each server must have one Expand-over-ServerNet line-handler process for each other node in the ServerNet cluster. A ServerNet cluster can consist of up to 24 nodes.
Summary of Configuration Steps Configuring Expand-Over-ServerNet Lines Summary of Configuration Steps After all hardware and software requirements have been met (see Required Hardware and Software on page 12-2 for details), configuring Expand-over-ServerNet connections involves these steps: Step Tool Used Step 1: Create a Profile for the Expand-OverServerNet Line-Handler Process SCF interface to the WAN subsystem Step 2: Create a Device for the Expand-OverServerNet Line-Handler Process SCF interface
Configuring Expand-Over-ServerNet Lines Step 1: Create a Profile for the Expand-OverServerNet Line-Handler Process Step 1: Create a Profile for the Expand-OverServerNet Line-Handler Process You can create a profile for the Expand-over-ServerNet line-handler processes using the PEXPSSN profile. This profile is provided in the $SYSTEM.SYSnn subvolume. You can also create a new profile from an existing profile, or you can create your own profile.
Configuring Expand-Over-ServerNet Lines Example Example In this example, a profile named PEXPSSN is created for an Expand-over-ServerNet line-handler process using the PEXPSSN profile. The AFTERMAXRETRIES_DOWN modifier is set in the profile. -> ADD PROFILE $ZZWAN.#PEXPSSN, FILE $SYSTEM.SYS01.PEXPSSN &, AFTERMAXRETRIES_DOWN Step 2: Create a Device for the Expand-OverServerNet Line-Handler Process You create an Expand-over-ServerNet line-handler process by adding it as a device to the WAN subsystem.
Configuring Expand-Over-ServerNet Lines ADD DEVICE Command CPU cpunumber indicates the processor where this Expand-over-ServerNet line-handler process will normally run. Note. HP recommends that you use the Notation Conventions to configure line handlers, to avoid configuring them in processors 0 and 1. For more information, see Considerations on page 12-11. ALTCPU altcpunumber indicates the processor where the backup Expand-over-ServerNet line-handler process will normally run.
Configuring Expand-Over-ServerNet Lines Considerations modifier_value is the value you want to assign to the modifier specified by modifier_keyword. modifier_value assigns a value to modifier_keyword in the device record for this Expand line-handler process. Default values and ranges of values for modifiers in the PEXPSSN profile are described in Profile Modifiers on page 12-13. Considerations • • • Not all modifiers have associated values (for example, L4EXTPACKETS_ON).
Configuring Expand-Over-ServerNet Lines Step 3: Start the Expand-Over-ServerNet LineHandler Processes Step 3: Start the Expand-Over-ServerNet LineHandler Processes To start an Expand-over-ServerNet line-handler process, use the WAN subsystem SCF START DEVICE command. You must start each Expand-over-ServerNet line-handler process that you created in Step 2: Create a Device for the Expand-Over-ServerNet Line-Handler Process. The command syntax is: START DEVICE $ZZWAN.#device_name $ZZWAN.
Profile Modifiers Configuring Expand-Over-ServerNet Lines For the next steps, such as installing a new cluster, migration, or adding a node, see the ServerNet Cluster Manual or the ServerNet Cluster 6780 Planning and Installation Guide . Profile Modifiers This subsection lists the modifiers provided for configuring special features. It also describes default values and value ranges for all the modifiers contained in the PEXPSSN profile.
PEXPSSN Modifiers Configuring Expand-Over-ServerNet Lines Table 12-2.
13 Configuring Multi-Line Paths The Expand multi-line path feature enables you to configure as many as eight lines between the two adjacent nodes. The Expand subsystem can simultaneously transmit data over all the lines in a multi-line path, thus increasing overall bandwidth, and will automatically retransmit data over remaining lines if one or more lines fail. A multi-line path can be part of a multi-CPU path. This section explains how to configure the Expand multi-line path feature. Note.
Configuring Multi-Line Paths Configuration Considerations Configuration Considerations Consider these when configuring a multi-line path: • • • • • You can configure a maximum of eight lines in a multi-line path. The lines in a multi-line path can be all the same type (for example, all dedicated), or they can be any combination of dedicated lines, X.25 connections, and SNAX connections. You cannot mix satellite-connect, Expand-over-ATM, and Expandover-IP lines with other line types.
Summary of Configuration Steps Configuring Multi-Line Paths Summary of Configuration Steps Configuring and starting a multi-line path involves these steps: Task Tool Used Step 1: Create a Profile for the Path-Logical Device SCF interface to the WAN subsystem Step 2: Create a Profile for Each Line Type SCF interface to the WAN subsystem Step 3: Create a Path-Logical Device SCF interface to the WAN subsystem Step 4: Create the Line-Logical Devices SCF interface to the WAN subsystem Step 5: Start t
Configuring Multi-Line Paths Step 2: Create a Profile for Each Line Type reference this profile_name when you create the device for the path in Step 3: Create a Path-Logical Device. FILE $SYSTEM.SYSnn.PEXPPATH specifies the name of an existing disk file that will be used to create the new profile. PEXPPATH is the disk filename of the profile provided for path-logical devices. modifier_keyword is the name of a modifier in profile_name.
ADD PROFILE Command Configuring Multi-Line Paths specifies, via the WAN subsystem, a user-defined name of up to eight alphanumeric characters that will be used to identify the new profile. You will reference this profile_name when you create the device for the line in Step 4: Create the Line-Logical Devices. FILE $SYSTEM.SYSnn.diskfile_name specifies the name of an existing disk file that will be used to create the new profile.
Configuring Multi-Line Paths Step 3: Create a Path-Logical Device Step 3: Create a Path-Logical Device You create a path-logical device by adding a device to the WAN subsystem. ADD DEVICE Command To create a path-logical device, use the WAN subsystem SCF ADD DEVICE command. The command syntax is: ADD , , , , , , , [, DEVICE $ZZWAN.#path_name IOPOBJECT $SYSTEM.SYSnn.LHOBJ PROFILE profile_name CPU cpunumber ALTCPU altcpunumber TYPE (63,1) RSIZE 0 NEXTSYS sys_number modifier_keyword [ modifier_value ] ] ..
Configuring Multi-Line Paths Considerations NEXTSYS sys_number is a required modifier that specifies the number (from 0 through 254) of the system connected to the other end of the path. If you do not specify NEXTSYS, this modifier defaults to an invalid value (255) and an operator message occurs during the initialization of the path-logical device.
Configuring Multi-Line Paths Step 4: Create the Line-Logical Devices Step 4: Create the Line-Logical Devices You must create a line-logical device for each line in the multi-line path. You create a line-logical device by adding it as a device to the WAN subsystem. All line-logical devices must be configured in the same processor pair as the path-logical device with which they are associated. ADD DEVICE Command To create a line-logical device, use the WAN subsystem SCF ADD DEVICE command.
ADD DEVICE Command Configuring Multi-Line Paths TYPE devsubtype is the device subtype for this line-logical device. The device subtypes for linelogical devices are listed in Table 13-2. Table 13-2.
Configuring Multi-Line Paths ADD DEVICE Command LINE linenum is the number of an available WAN line on the CLIP specified by clipnum. For more information on identifying line numbers, see Step 1: Find an Available WAN Line on page 7-5. Valid values are 0 or 1. PATH { A | B } is the path (A or B) on the CLIP specified by clipnum that you prefer. The path must be configured. For more information on adding Ethernet paths, see the WAN Subsystem Configuration and Management Manual.
Configuring Multi-Line Paths ADD DEVICE Command DESTIPADDR dest_ipaddr is a required modifier that specifies the IP address used by the remote (destination) Expand-over-IP line. It is the IP address specified in the remote line’s SRCIPADDR modifier. Determining IP addresses is described in Step 1 (A): Select a Process and SUBNET for NonStop TCP/IP Use on page 8-9. The address must be specified by number (for example, 130.252.12.3). It is not validated and need not be accessible. The default is 0.0.0.1.
Configuring Multi-Line Paths ADD DEVICE Command CALLTYPE_PVC indicates that a permanent virtual circuit (PVC) connection will be used. Either CALLTYPE_ATMSAP, CALLTYPE_PVC, or CALLTYPE_SVC is required. CALLTYPE_SVC indicates that a switched virtual circuit (SVC) connection will be used. Either CALLTYPE_ATMSAP, CALLTYPE_PVC, or CALLTYPE_SVC is required. LIFNAME lif_name is the name of the ATMSAP connection that will be used. For example, LIF01.
Configuring Multi-Line Paths Considerations Required Modifiers for Expand-Over-NAM Lines ASSOCIATEDEV $nam_process is a required modifier that specifies the device name of the X25AM line-handler process or SNAX/APN line-handler process you want to associate with this Expand-over-X.25 or Expand-over-SNA line. ASSOCIATESUBDEV #subdevice is a required modifier that specifies the name of an X25AM subdevice to which the Expand-over-X.
Configuring Multi-Line Paths Step 6: Start the Lines Step 6: Start the Lines To start all the lines in the multi-line path, use the Expand subsystem SCF START PATH command. The command syntax is: START PATH $device_name device_name is the path-logical device name. The successful completion of this command leaves the path and all the lines in the path in the STARTED state. Starting Specific Lines To start specific lines in a multi-line path, use the Expand subsystem SCF START LINE command.
Configuration Example Configuring Multi-Line Paths Configuration Example This example shows a multi-line path with one direct-connect line and one Expandover-SNA line. Figure 13-2 illustrates the configuration of this example. Figure 13-2. Multi-Line Configuration Example MULTI $LINE1 SWAN003A $PATH $LINE2 MULTI $SNA1 SWANxxxxx ASSOCIATEDEV VST046.vsd Note. The SWAN concentrator used by the SNAX/APN process $SNA1 is shown as a transparent box because it is not configured in this command example.
Configuring Multi-Line Paths • Path-Logical Device Modifiers This SCF ADD DEVICE command creates a line-logical device named $LINE1 for the direct-connect line. Note MLHDIR profile created above is used. -> ADD DEVICE $ZZWAN.#LINE1, PROFILE MLHDIR, IOPOBJECT & $SYSTEM.SYSTEM.LHOBJ, CPU 0, ALTCPU 1, TYPE (63,5), & RSIZE 0, LINETF 2, MULTI $PATH, CLIP 2, LINE 0, & ADAPTER SWAN003A, PATH A • This SCF ADD DEVICE command creates a line-logical device named $LINE2 for the Expand-over-SNA line.
PEXPPATH Modifiers Configuring Multi-Line Paths Table 13-3.
Line-Logical Device Modifiers Configuring Multi-Line Paths Line-Logical Device Modifiers This subsection lists the modifiers for line-logical devices and describes the default value and range of values for each modifier in the PEXQMSWN, PEXQMNAM, PEXQMSAT, PEXQMATM, and PEXQMIP profiles. For a complete description of the modifiers listed in this subsection, see Section 16, Expand Modifiers. Note. There are no required modifiers for direct-connect and satellite-connect lines in a multiline path.
PEXQMSWN and PEXQMSAT Modifiers Configuring Multi-Line Paths Table 13-4.
PEXQMNAM Modifiers Configuring Multi-Line Paths PEXQMNAM Modifiers The disk file $SYSTEM.SYSnn.PEXQMNAM defines modifiers for Expand-over-NAM lines in multi-line paths. Table 13-5 lists the default value and range of values for each modifier in this profile, if applicable. For modifiers that are mutually exclusive, a check mark (3) is shown in the “Default Value” column to indicate which modifier is present in the profile. Table 13-5.
PEXQMIP Modifiers Configuring Multi-Line Paths PEXQMIP Modifiers The disk file $SYSTEM.SYSnn.PEXQMIP defines modifiers for Expand-over-IP lines in multi-line paths. Table 13-6 lists the default value and range of values for each modifier in this profile, if applicable. For modifiers that are mutually exclusive, a check mark (3) is shown in the “Default Value” column to indicate which modifier is present in the profile. Table 13-6.
PEXQMATM Modifiers Configuring Multi-Line Paths Table 13-6. PEXQMIP Modifiers (page 2 of 2) Modifier Default Value Range of Values V6DESTIPADDR 0000:0000:0000: 0000:0000:0000: 0000:0000 Any 45-character string V6SRCIPADDR 0000:0000:0000: 0000:0000:0000: 0000:0000 Any 45-character string 1. This is a required modifier. 2. This is a required modifier.
PEXQMATM Modifiers Configuring Multi-Line Paths Table 13-7. PEXQMATM Modifiers (page 2 of 2) Modifier Default Value Range of Values QUALITYTHRESHOLD 0 0 to 99 QUALITYTIMER 60 seconds 0 to 77600 (12hrs) RXWINDOW 7 2 through 15 SPEED 0 0 or 1200 through 224000 SPEEDK NOT_SET 0 through 4,000,000,000 STARTUP_OFF 3 STARTUP_ON TXWINDOW 7 2 through 25 1. This is a required modifier. 2. This modifier is required for Expand-over-ATM line-handler processes that use SVC connections. 3.
Configuring Multi-Line Paths Expand Configuration and Management Manual — 529522-013 13 - 24 PEXQMATM Modifiers
Part III.
Part III.
14 Subsystem Control Facility (SCF) Commands This section describes the Subsystem Control Facility (SCF) interface to the Expand subsystem and provides SCF command syntax. For general information about running SCF, see the SCF Reference Manual for H-Series RVUs.
Overview of the Expand Subsystem SCF Interface Subsystem Control Facility (SCF) Commands Overview of the Expand Subsystem SCF Interface The Expand subsystem SCF interface is provided to configure, control, and display information about configured objects within the Expand subsystem.
Subsystem Control Facility (SCF) Commands • • Expand Subsystem Objects The path function corresponds to the functions defined by Layers 3 and 4 of the Open Systems Interconnection (OSI) Reference Model. You specify the PATH object when you want to display Layer 3 and 4 information or alter Layer 3 and 4 attributes for a single-line Expand line-handler process. The line function corresponds to the functions defined by Layer 2 of the OSI Reference Model.
Subsystem Control Facility (SCF) Commands Object States These are some typical device names: $SYS1 An Expand line-handler process that manages a single line to the node named \SYS1 $PATH A path logical device $LINE1, $LINE2, and so on Line logical devices PROCESS Object The PROCESS object type might see the Expand manager process ($ZEXP), the network control process ($NCP), or an Expand line-handler process. ENTRY Object The ENTRY object type identifies an entry in the network routing table (NRT).
SCF Commands and Objects Subsystem Control Facility (SCF) Commands SCF Commands and Objects Table 14-1 lists the SCF commands and objects that are applicable to the Expand subsystem. Table 14-1.
Wild-Card Support Subsystem Control Facility (SCF) Commands Table 14-2 lists the sensitive and nonsensitive Expand SCF commands. Table 14-2.
Subsystem Control Facility (SCF) Commands SCF and the WAN Subsystem SCF and the WAN Subsystem On Integrity NonStop NS-series servers, you use the SCF interface to the WAN subsystem to create $NCP and the Expand line-handler processes. You can also use the SCF interface to the WAN subsystem to perform certain network-management tasks. The SCF interface to the WAN subsystem is described in the WAN Subsystem Configuration and Management Manual.
Subsystem Control Facility (SCF) Commands • SCF and the SLSA Subsystem Use the Expand subsystem STOP PATH or STOP LINE command before you use the STOP DEVICE command to stop the Expand line-handler process in the primary and backup processors. For a complete comparison of the Expand and WAN subsystem SCF interfaces, see Appendix B, Expand and WAN SCF Comparison.
Subsystem Control Facility (SCF) Commands • Examples You can abort several lines or paths with a single ABORT command by specifying multiple PATH or LINE objects using parentheses as: PATH ( path-name , path-name [ , path-name ] ...) LINE ( line-name , line-name [ , line-name ] ...
Subsystem Control Facility (SCF) Commands ALTER Command ALTER Command The ALTER command changes the values for PATH object types, LINE object types, and the PROCESS $NCP object type. ALTER is a sensitive command. The ALTER command syntax is: ALTER { PROCESS $NCP | PATH path-name | LINE line-name } ALTER DEVICE Command The WAN subsystem ALTER DEVICE command changes the values of a data communications subsystem object. The ALTER DEVICE command changes only the specified attributes of the target object.
Subsystem Control Facility (SCF) Commands ALTER PATH Command ALTER PATH Command The ALTER PATH command is described below. The PATH object type takes this form: PATH path-name attribute-spec [, attribute-spec ] ...
Subsystem Control Facility (SCF) Commands Considerations Considerations • You can alter several paths with a single ALTER command by specifying multiple PATH objects using parentheses as: -> PATH ( path-name , path-name [ , path-name ] ... ) Examples This SCF command changes the value of the path’s NEXTSYS attribute to system 100 and the value of its TIMERINACTIVITY attribute to 9 minutes and 30 seconds: -> ALTER PATH $PATH1, NEXTSYS 100, TIMERINACTIVITY 9:30.
Subsystem Control Facility (SCF) Commands [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ ALTER LINE Command AFTERMAXRETRIES { DOWN | PASSIVE } ] ASSOCIATEDEV device-name ] ASSOCIATESUBDEV subdevice-name ] ATMSEL selector-byte ] CALLTYPE { PVC | SVC | ATMSAP} ] CLBDWNLOADRETRIES integer ] CLBDWNLOADTIMR time ] CLBIDLETIMER time ] CLOCKMODE { DTE | DCE } ] CLOCKSPEED { 600 | 1200 | 2400 | 4800 | 9600 | 19200 | 38400 | 56000 | 115200 } ] CONNECTTYPE { ACTIVEANDPASS
Subsystem Control Facility (SCF) Commands ALTER LINE Command Table 14-4 lists the line attributes that have corresponding profile modifiers. Table 14-4.
Subsystem Control Facility (SCF) Commands ALTER LINE Command Table 14-4.
ALTER LINE Command Subsystem Control Facility (SCF) Commands The valid range for this attribute is 0 to 5:27.67 minutes. The default is 10.00 seconds. DSRTIMER time specifies the amount of time that the line-handler process should wait after a Data Set Ready (DSR) signal from the modem has shut off before it returns a modem status message. This attribute applies to ServerNet wide area network (SWAN) concentrators only. The time interval is specified in the format described in Time Values on page 14-6.
ALTER LINE Command Subsystem Control Facility (SCF) Commands The TIMERBIND attribute does not apply to Expand-over-IP and Expand-over-ATM line-handler processes. A value of 0 indicates an indefinite interval (no timer). The valid range for this attribute is 0 to 9:06:07.00 hours. The default value for Expand-over-NAM lines is 30.00 seconds and the default value for Expand-overServerNet lines is 60.00 seconds.
Considerations Subsystem Control Facility (SCF) Commands Expand-over-X.25 lines: 300 Expand-over-SNA lines: 300 Expand-over-ServerNet lines: 30 TIMERRECONNECT time specifies the time interval that the Expand-over-NAM, Expand-over-ATM, Expandover-IP, or Expand-over-ServerNet line-handler process will wait for a connection request to succeed. The range does not include 0. The time interval is specified in the format described in Time Values on page 14-6.
Considerations Subsystem Control Facility (SCF) Commands Table 14-5 specifies the applicable ALTER LINE attributes for the different types of line-handler processes. Table 14-5.
Examples Subsystem Control Facility (SCF) Commands Table 14-5.
Subsystem Control Facility (SCF) Commands ALTER PROCESS Command ALTER PROCESS Command The ALTER PROCESS command changes the values of the attributes of the network control process ($NCP). This command changes only the specified attributes of $NCP. ALTER PROCESS is a sensitive command. The ALTER PROCESS command for $NCP has this syntax: ALTER PROCESS $NCP attribute-spec [ attribute-spec ] ...
Subsystem Control Facility (SCF) Commands ALTER PROCESS Command AUTOREBAL { ON | OFF } enables (ON) or disables (OFF) automatic rebalancing of the multi-CPU paths on the system. The time at which automatic rebalancing will occur is determined by the AUTOREBALTIME attribute. The default value is ON. AUTOREBALTIME time | ( time, start-time ) determines when automatic rebalancing of multi-CPU paths on the system will occur.
Subsystem Control Facility (SCF) Commands Example MSG46 { ON | OFF } enables (ON) or disables (OFF) the reporting of event message 46 to the EMS collector, $0. Event message 46 is equivalent to console message 46. This is not a critical message. It means a connection has been made with the indicated remote system. The default value is OFF. MSG48 { ON | OFF } enables (ON) or disables (OFF) the reporting of event message 48 to the EMS collector, $0. Event message 48 is equivalent to console message 48.
Subsystem Control Facility (SCF) Commands Examples Examples This SCF command removes from the NRT all the names of systems that are not connected within the network: -> DELETE ENTRY $NCP.* This SCF command removes the system name \NODEA from the NRT if the system named \NODEA is not connected within the network: -> DELETE ENTRY $NCP.\NODEA INFO Command The INFO command displays the current or default attribute values for the specified objects. INFO is a nonsensitive command.
INFO PATH Command Subsystem Control Facility (SCF) Commands INFO PATH Command The display for a path without the DETAIL option has the format as shown in Example 14-1. The asterisk (*) indicates that the attribute can be altered using the ALTER command, described earlier in this section. Example 14-1. INFO PATH Command -> INFO PATH $LHPATH EXPAND Info Path Name $LHPATH *Compress ON *Nextsys #255 *L4Retries 3 *L4Timeout 0:00:20.00 Name is the device name of the path.
INFO PATH Command Subsystem Control Facility (SCF) Commands Example 14-2 shows the display format for a path with the DETAIL option. The asterisk (*) indicates that the attribute can be altered using the ALTER command, described earlier in this section. Example 14-2. INFO PATH, DETAIL Command -> INFO PATH $LHPATH, DETAIL EXPAND Detailed Info PATH $LHPATH *Compress.... ON *OStimeout... 0:00:03.00 *L4Timeout... 0:00:20.00 *L4ExtPackets ON *L4CWNDClamp.
Subsystem Control Facility (SCF) Commands INFO PATH Command PATHTF setting is a constant value assigned to the time factor for the path. If PATHTF is left unset (a zero value), this parameter is not used in setting the time factor. L4Timeout reports the time interval for the Layer 4 timer. L4SendWindow is the maximum number of outstanding packet send requests in any single transport connection. TimeFactor reports the current time factor for this path.
Subsystem Control Facility (SCF) Commands INFO PATH Command has congestion control enabled and the receiver supports it. The receiver does not have to have the congestion control feature enabled to support it. L4CWNDCLAMP Specifies the maximum value for the congestion control transmit window. The packet rate transmitted over the path does not exceed the L4CWNDCLAMP value. Expand uses a window scale factor of 5, for packet sequencing and window values.
Subsystem Control Facility (SCF) Commands INFO PATH Command Negotiated Amount that is currently in use; the lesser of the Local and Remote values Maximum Maximum value available on this path PathPacketBytes shows the variable packet parameters for these four fields: Local Currently configured local value Remote Most recent value from the remote path Negotiated Amount that is currently in use; the lesser of the Local and Remote values Maximum Maximum value available on this path Expand Configur
Subsystem Control Facility (SCF) Commands OBEYFORM Option OBEYFORM Option The output is in the form of an ALTER PATH command. This allows for easy creation of SCF command files for configuration backup. Example 14-3. INFO PATH $LHPATH, OBEYFORM command -> INFO PATH $LHPATH,OBEYFORM ALTER PATH $LHPATH ,& COMPRESS ON ,& NEXTSYS 144 ,& OSSPACE 32767 ,& OSTIMEOUT 0:00:03.00 ,& L4RETRIES 3 ,& PATHTF 0 ,& L4TIMEOUT 0:00:20.
INFO LINE Command Subsystem Control Facility (SCF) Commands INFO LINE Command The format of the INFO LINE display varies according to the line-handler process type. The first three lines of the display are common for all line types. The rest of the lines vary according to the line type.
Subsystem Control Facility (SCF) Commands Direct-Connect and Satellite-Connect Line-Handler Processes SpeedK calculates the time factor of the line for the Expand routing algorithm. A value of NOT_SET means that this parameter was not set. For a discussion of SPEEDK, see SPEEDK n on page 16-23. L2Timeout reports the time interval of the Layer 2 T1 timer.
Subsystem Control Facility (SCF) Commands Direct-Connect and Satellite-Connect Line-Handler Processes Framesize specifies the maximum size frame that can be sent in the network; smaller frames can be sent. The Expand subsystem also uses the FRAMESIZE modifier value to calculate the packet size and determine the size of the frame buffers. If the default FRAMESIZE modifier value is used, the packet size is 132 words. Rsize specifies the time factor of the line for the Expand routing algorithm.
Subsystem Control Facility (SCF) Commands Direct-Connect and Satellite-Connect Line-Handler Processes in the QualityThreshold before taking the action specified in the parameter DownIfBadQuality. TxWindow reports the number of Expand packets that the line-handler process can send before receiving a reply. Address specifies the Layer 2 primary and secondary addresses. Addresses are system numbers.
Subsystem Control Facility (SCF) Commands Direct-Connect and Satellite-Connect Line-Handler Processes DRtimeout specifies the time interval that the line-handler process Communications Access Process (CAP) will wait for a response to a request it has sent to the communications line interface processor (CLIP). CLBIdleTimer specifies the time interval between communications line interface processor (CLIP) status probes.
Expand-Over-IP Line-Handler Processes Subsystem Control Facility (SCF) Commands Program reports the file name of the communications line interface processor (CLIP) program that will be downloaded. LineTF is the line time factor. LINETF has a range of 0 to 186, with a default of 0 (unset). If you set LINETF, it overrides the RSIZE, SPEED, or SPEEDK parameters in calculating the time factor for the line (PATHTF overrides all parameters, including LINETF).
Expand-Over-IP Line-Handler Processes Subsystem Control Facility (SCF) Commands Aftermaxretries is the line state after retries have been exhausted for the line. DOWN means the line state will be down. PASSIVE means the Expand-over-IP process will issue passive connect requests. Example 14-7 shows the display format for a LINE object with the DETAIL option for Expand-over-IP line-handler processes for IPv4 lines. The asterisk (*) indicates an alterable attribute. Example 14-7.
Expand-Over-IP Line-Handler Processes Subsystem Control Facility (SCF) Commands Example 14-8. INFO LINE, DETAIL Command, Expand-Over-IP Line-Handler Processes for IPv6 Lines -> INFO LINE $IPTAH0, DETAIL EXPAND Detailed Info LINE $IPTAH0 (LDEV 175) L2Protocol Net^Ip TimeFactor...... 3 Framesize....... 132 -Rsize........... 3 *LinePriority.... 1 StartUp......... OFF *DownIfBadQuality OFF *QualityThreshold 96 *Txwindow........ 7 *Maxreconnects... 0 *Timerreconnect 0:00:30.00 *Retryprobe......
Subsystem Control Facility (SCF) Commands Expand-Over-IP Line-Handler Processes LinePriority This can be set in the range 1 to 9. The default is 1. The higher the number, the lower priority to use that line. If lines have equal priority, the relative line speeds and transmission delays are used to select the next line. Startup indicates whether the line will be enabled (ON) or disabled (OFF) after a system load. Delay is the expected line time required for a bit to arrive at the other end of the line.
Subsystem Control Facility (SCF) Commands Expand-Over-IP Line-Handler Processes Timerreconnect is the time interval the Expand-over-IP line-handler process will wait for a successful connection. Retryprobe is the number of times the Expand-over-IP line-handler process will retry the probe of the remote Expand-over-IP line-handler process before concluding that the network is unavailable.
Subsystem Control Facility (SCF) Commands Expand-Over-ATM Line-Handler Processes SrcIpAddr is the TCP/IP address used by the local Expand-over-IP line-handler process. It is used only if the IPVER is IPv4. SrcIpPort is the port number used by the local Expand-over-IP line-handler process. It is used for both IPVER IPv4 and IPv6. V6DestIpAddr is the destination NonStop TCP/IPv6 address used by the remote Expand-over-IP line-handler process. It is used only if the IPVER is IPv6.
Expand-Over-ATM Line-Handler Processes Subsystem Control Facility (SCF) Commands Associatedev reports the name of the ATM line associated with the Expand-over-ATM linehandler process. Associatesubdev reports the name of the ATM service access point (SAP). The only currently supported ATM SAP is #IP. Example 14-10 shows the display format for a LINE object with the DETAIL option for Expand-over-ATM line-handler processes that use permanent virtual circuits (PVCs).
Subsystem Control Facility (SCF) Commands Expand-Over-ATM Line-Handler Processes Rsize specifies the time factor of the line for the Expand routing algorithm. RSIZE can be 0 if the time factor is set using some other modifier. Speed calculates the time factor of the line for the Expand routing algorithm. LinePriority This can be set in the range 1 to 9. The default is 1. The higher the number, the lower priority to use that line.
Subsystem Control Facility (SCF) Commands Expand-Over-ATM Line-Handler Processes Maxreconnects is the maximum number of times the Expand-over-ATM line-handler process will try to connect to the remote system. AfterMaxRetries is the line state after all retries have been exhausted for the line. Timerreconnect is the time interval the Expand-over-ATM line-handler process will wait for a successful connection.
Subsystem Control Facility (SCF) Commands OBEYFORM Option PvcName is the name of the permanent virtual circuit (PVC). LineTF is the line time factor. LINETF has a range of 0 to 186, with a default of 0 (unset). If you set LINETF, it overrides the RSIZE, SPEED, or SPEEDK parameters in calculating the time factor for the line (PATHTF overrides all parameters, including LINETF). If LINETF is left unset (a zero value), this parameter is not used in setting the time factor.
Subsystem Control Facility (SCF) Commands Expand-Over-NAM and Expand-Over-ServerNet Line-Handler Processes Expand-Over-NAM and Expand-Over-ServerNet Line-Handler Processes For Expand-over-NAM and Expand-over-ServerNet line-handler processes, the display for a LINE object without the DETAIL option has the format as shown in Example 14-12. The asterisk (*) indicates an alterable attribute. Example 14-12.
Subsystem Control Facility (SCF) Commands Expand-Over-NAM and Expand-Over-ServerNet Line-Handler Processes it is the subdevice name of a SNAX/APN logical unit (LU). This field is not used by Expand-over-ServerNet line-handler processes. Example 14-13 shows the display format for a LINE object with the DETAIL option for Expand-over-NAM or Expand-over-ServerNet line-handler processes. The asterisk (*) indicates an alterable attribute. Example 14-13.
Subsystem Control Facility (SCF) Commands Expand-Over-NAM and Expand-Over-ServerNet Line-Handler Processes LinePriority can be set in the range 1 to 9. The default is 1. The higher the number, the lower priority to use that line. If lines have equal priority, the relative line speeds and transmission delays are used to select the next line. StartUp shows that the line will be disabled (OFF) or enabled (ON) after a system load. Delay reports the time interval between transmissions.
Subsystem Control Facility (SCF) Commands Expand-Over-NAM and Expand-Over-ServerNet Line-Handler Processes Expand-over-ServerNet line-handler processes that have the MAXRECONNECTS modifier set to a nonzero value. Timerreconnect specifies the time interval that the Expand-over-NAM or Expand-over-ServerNet line-handler process will wait for a connection request to succeed. For a description of the time interval format, see Time Values on page 14-6.
Subsystem Control Facility (SCF) Commands Considerations LineTF is the line time factor. LINETF has a range of 0 to 186, with a default of 0 (unset). If you set LINETF, it overrides the RSIZE, SPEED, or SPEEDK parameters in calculating the time factor for the line (PATHTF overrides all parameters, including LINETF). If LINETF is left unset (a zero value), this parameter is not used in setting the time factor.
Subsystem Control Facility (SCF) Commands INFO PROCESS Command LINESET displays the status of a selected path and the status of the started lines that make up that path. Note. The LINESET option only displays information on active lines (lines that have been started at least after a system load). To see information on all configured lines, use the SCF command LISTDEV TYPE 63. NETMAP displays the status of the network as seen from a specific system.
Subsystem Control Facility (SCF) Commands INFO PROCESS Command sys-c is {\system-name | system-number }. If the NETMAP, SUPERPATH, or RPT option is chosen, only one system can be specified. If the SUPERPATH option is chosen, the display lists the multi-CPU paths on a remote node. If the RPT option is chosen, the display lists the reverse pairing table (RPT) on a remote node. If the AT option is omitted, the SCF target system is assumed.
INFO PROCESS Command Subsystem Control Facility (SCF) Commands The display for the INFO PROCESS $NCP command without the DETAIL option has the format as shown in Example 14-14. The asterisk (*) denotes an alterable attribute. Example 14-14. INFO PROCESS $NCP Command -> INFO PROCESS $NCP EXPAND Info PROCESS $NCP AT \NODEA (151) Name $NCP AutomaticMaptimer ON Framesize #132 *Maxtimeouts 3 *Maxconnects 5 Name is the device name of the network control process ($NCP).
INFO PROCESS Command Subsystem Control Facility (SCF) Commands The display for the INFO PROCESS $NCP command with the DETAIL option has the format as shown in Example 14-15. The asterisk (*) denotes an alterable attribute. Example 14-15. INFO PROCESS $NCP, DETAIL Command -> INFO PROCESS $NCP, DETAIL EXPAND Detailed Info PROCESS Max System Number.. Algorithm.......... *Connecttime........ *Maxtimeouts........ *NetworkDiameter.... *Message 43......... Message 45......... Message 47......... *Message 49..
Subsystem Control Facility (SCF) Commands INFO PROCESS Command Framesize is used by $NCP to compute the maximum size, in words, of a distance vector (DV) packet. Note. The network control process FRAMESIZE modifier and the Layer 2 SCF FRAMESIZE modifier have the same name. Both the network control process and the Layer 2 FRAMESIZE modifiers are configured using the SCF interface to the WAN subsystem.
Subsystem Control Facility (SCF) Commands INFO PROCESS Command Message 47 reports whether the reporting of event message 47 to $0 is enabled (ON). Message 47 is a critical message. It means that an end-to-end acknowledgment was not received from the indicated system within the configured Layer 4 timeout interval. Message 48 reports whether the reporting of event message 48 to $0 is enabled (ON) or disabled (OFF). Message 48 is a critical message.
CONNECTS Option Subsystem Control Facility (SCF) Commands RebalThreshold specifies the threshold time for auto-rebalance. It also helps to enable and disable auto-rebalance. RebalThreshold can have the following values: • • • -1, the auto-rebalance is switched off and the user must manually trigger rebalance. 0, the auto-rebalance occurs normally without taking into cognizance this modifier value.
Subsystem Control Facility (SCF) Commands LINESET Option Time(Dist) these entries show the time factor (TIME) and number of hops (DISTANCE) for each path between systems in the network and the selected system. A value of inf (--) (for infinite) indicates that there is no connection to the selected system. Each row and column entry represents a path connecting the selected system to the system listed in the leftmost column. (For more information on the TF, see Routing and Time Factors on page 17-22.
Subsystem Control Facility (SCF) Commands LINESET Option Note. If a pre-G06.12 system that can support only 63 linehandlers runs the command, INFO PROCESS $NCP, LINESET, AT \NEW to send the LINESET request to a system that can display 255 linehandlers, the number of entries in the reply is limited to 63, the number of entries that the pre-G06.12 system can display.
LINESET Option Subsystem Control Facility (SCF) Commands The display for the INFO PROCESS $NCP command with the LINESET option has the format as shown in Example 14-17: Example 14-17.
Subsystem Control Facility (SCF) Commands LINESET Option TF indicates time factors in this display. To use old time-factor values, use the command INFO PROCESS $NCP, OLDLINESET. If you are using the OLDLINESET option on a G06.20 node, the command INFO PROCESS $NCP, LINESET, AT \remote, where \remote is a G06.19 node, displays super time factor information, and the command INFO PROCESS $NCP, OLDLINESET, AT \remote displays non-super time factor information. PID is the process ID.
NETMAP Option Subsystem Control Facility (SCF) Commands NETMAP Option The display for the INFO PROCESS $NCP command with the NETMAP option has the format as shown in Example 14-18: Example 14-18.
Subsystem Control Facility (SCF) Commands NETMAP Option #LINESETS=n indicates that there are n communications paths (LINESETS) directly connected to the selected system. The LINESETS are listed in detail after the NETMAP table. The systems in the network are listed by the system number followed by the system name. SYSTEM indicates the number and the name of the system, or node.
Subsystem Control Facility (SCF) Commands OBEYFORM Option TF indicates time factors in this display. If you are using the OLDNETMAP option on a G06.20 node, the command INFO PROCESS $NCP, LINESET, AT \remote, where \remote is a G06.19 node, displays super time factor information, and the command INFO PROCESS $NCP, OLDLINESET, AT \remote displays non-super time factor information. PID is the process ID. LINE indicates the device name of a line.
PATHSET Option Subsystem Control Facility (SCF) Commands Note. The OBEYFORM option cannot be used in combination with the DETAIL option. PATHSET Option The PATHSET option displays the NCP pathmap information, similar to the LINESET option but in a different format. This format displays both the line-handler LDEV and name in addition to the other information already in the LINESET option. Example 14-20.
RPT Option Subsystem Control Facility (SCF) Commands Line indicates the line number. Name indicates the device name of the line. Ldev indicates the logical device (LDEV) number associated with each line logical device. Status indicates the status of the line; whether it is ready or not ready. FileErr shows the most recent file system error number, if any, associated with each line. For recovery information on file errors, see Identifying Network Problems on page 20-3.
SUPERPATH Option Subsystem Control Facility (SCF) Commands entries with valid LDEVs are displayed. For more information on the RPT, see Network Routing Table (NRT) and Multiple Path Table (MPT) on page 17-25. NEIGHBOR indicates the neighbor node that data is transmitted to over the path. SYS/LDEV indicates the number and the name of the system, or node, and the logical device (LDEV) number.
SYSTEMS Option Subsystem Control Facility (SCF) Commands TF indicates super time factors in this display. LF indicates the load factor for the path in a multi-CPU path (superpath). The effective time factor (ETF) is calculated based on the load factor (ETF = LF * TF). LCPU indicates the local processor number. RCPU indicates the remote processor number.
Subsystem Control Facility (SCF) Commands SYSTEMS Option Time(Dist) These entries show the time factor (TIME) and number of hops (DISTANCE) for each path between systems in the network and the selected system. A value of inf (--) (for infinite) indicates that there is no connection to the selected system. Each row and column entry represents a path connecting the selected system to the system listed in the leftmost column. (For more information on the TF, see Routing and Time Factors on page 17-22.
Subsystem Control Facility (SCF) Commands PRIMARY PROCESS Command PRIMARY PROCESS Command The PRIMARY PROCESS command causes the backup process to become the primary process and the primary to become the backup. PRIMARY PROCESS is a sensitive command. The PRIMARY PROCESS command has this syntax: PRIMARY PROCESS { line-name | path-name | $NCP } , cpu-number line-name | path-name is the name of the line or path to be switched to the backup processor.
Subsystem Control Facility (SCF) Commands PROBE PROCESS Command This SCF command causes the backup processor (CPU 1) to become the primary processor and the primary to become the backup for $NCP: -> PRIMARY PROCESS $NCP, 1 This SCF command causes the backup processor (CPU 0) to become the primary processor and the primary to become the backup for $LHCOM and $LHBAL: -> PRIMARY PROCESS ($LHCOM, $LHBAL), 0 PROBE PROCESS Command The PROBE PROCESS command applies only to $NCP.
Subsystem Control Facility (SCF) Commands PROBE PROCESS Command system-list identifies the system, or systems, to which the probe is made. * denotes all accessible systems in the network. That is, the probe is made to all accessible systems. If the TO parameter is omitted, * is assumed and the probe is made to all accessible systems in the network.
Subsystem Control Facility (SCF) Commands START Command value in parentheses (00002 ms) indicates that the round-trip time for this probe was 2 milliseconds. 6 \NODER - \NODED - \NODEW - \NODEH - \NODEB - * (00003 ms) indicates that the probe was made from \NODEA to \NODER. The list begins with \NODER and ends at the system from which the probe was made, indicated by the asterisk *. The systems in between are \NODED, \NODEW, \NODEH, and \NODEB.
Subsystem Control Facility (SCF) Commands • Examples You can start several lines or paths with a single START command by specifying multiple LINE or PATH objects using parentheses as: -> LINE ( line-name , line-name [ , line-name ] ... ) -> PATH ( path-name , path-name [ , path-name ] ...
STATS PATH Command Subsystem Control Facility (SCF) Commands nnn is the decimal node number. node-name is the name of the node, such as \NODEA. RESET resets the statistical counters for the specified path. This is a sensitive command. The display for a PATH object has the format as shown in Example 14-25: Example 14-25. STATS PATH Command -> STATS PATH $ENS21 EXPAND Stats PATH $ENS21, PPID ( 0, Reset Time....
Subsystem Control Facility (SCF) Commands STATS PATH Command PPID is the primary process ID. BPID is the backup process ID. Reset Time is the last time the statistics counters were reinitialized. Sample Time is the time of the current statistics display. Current Ext Mem KBytes Used is the current amount of extended memory used, in KBytes. Max Ext Mem KBytes Used is the maximum amount, in KBytes, of extended memory used because the last statistics reset or line-handler process start.
Subsystem Control Facility (SCF) Commands STATS PATH Command Max QIO KBytes Used is the maximum total number of kilobytes of QIO memory space because the last statistics reset or line-handler process start, including overhead and control data, that was used at any one instant to support messages over the specified path. Current QIO MDs Used indicates the current QIO message descriptors used. A message descriptor is an internal structure used for sending and receiving messages to and from QIO.
Subsystem Control Facility (SCF) Commands ENQ PING STATS PATH Command ENQUIRY request PING requests and replies Note. The sum of PING requests and PING replies is shown because PING requests and PING replies only occur in pairs. The Expand message types are defined and described in Message Handling and Buffer Allocation on page 17-38. L4 Packets Discarded is the number of incoming Level 4 packets discarded because they were duplicates or received too far out of sequence.
Subsystem Control Facility (SCF) Commands STATS PATH Command Bad Dest Pin Rcvd is the number of incoming packets discarded because they contained an invalid destination ID. Bad Src Pin Rcvd is the number of incoming packets discarded because they contained an invalid source ID. Bad Checksum Rcvd is the number of incoming packets discarded because they contained an invalid checksum value. Looping Packets is the number of incoming packets discarded because they contained the same source ID as the receiver.
Subsystem Control Facility (SCF) Commands Considerations L5 Waiting EXT/Shared Memory is the current or maximum number of level 5 requests awaiting extended or shared memory. L4 Waiting Shared Memory is the current or maximum number of level 4 requests awaiting shared memory. LEVEL 4 / CONGESTION CONTROL displays the congestion control statistics for the specified path. Xmit Timeouts is the number of transmission timeouts. ReXmit Timeouts is the number of retransmission timeouts.
Subsystem Control Facility (SCF) Commands STATS PATH NODE Command STATS PATH NODE Command The STATS PATH NODE command has this syntax: STATS [ / OUT file-spec / ] PATH path-name [ , TO { nnn | \node-name } ] [ , RESET ] / OUT file-spec / causes any SCF output generated by the command to be directed to the specified file. path-name is the name of the path. TO nnn is the destination system, where nnn is the decimal node number. node-name is the destination node name, such as \NODEA.
STATS PATH NODE Command Subsystem Control Facility (SCF) Commands The display for a NODE object has the format as shown in Example 14-26: Example 14-26. STATS PATH NODE Command SCF > STATS PATH $ENS21,TO \CRYPTO EXPAND Stats PATH $ENS21, PPID ( 0, 909), BPID ( 1, 1033) STATS TO NODE \CRYPTO (254) Reset Time.... AUG 7,2013 17:17:40 Sample Time.. AUG 8,2013 11:15:49 ---------------------------- MESSAGE HISTOGRAM -------------------------<= 64 .. 1583 <= 128 .. 36 <= 256.. 15 <= 512 .. 8 <= 1024 ..
Subsystem Control Facility (SCF) Commands STATS PATH NODE Command MESSAGE HISTOGRAM is the overall count of messages sent and received by this node over this path, classified by size in bytes because statistics were last reset using the STATS RESET command, or because the line-handler process was started. The counts do not include any passthrough traffic. Note that not every request is completed, because a CANCEL request might have been issued.
Subsystem Control Facility (SCF) Commands STATS PATH NODE Command ReIdle Timeouts is the number of idle timeouts causing the congestion window to be reduced. Current CWND displays the current congestion control window (CWND) value. Max CWND displays the maximum congestion control window (CWND) value attained. Average RTT displays the average Round Trip Time (RTT) value. RTT Std Dev displays the RTT Standard Deviation Time value. Min RTT displays the Minimum Round Trip Time (RTT) value.
Examples Subsystem Control Facility (SCF) Commands Active displays the number of messages received from the remote node and linked to the local processes. Oos displays the number of out-of-sequence packets.
Subsystem Control Facility (SCF) Commands Expand-Over-IP Line-Handler Processes PPID is the primary process ID. BPID is the backup process ID. Resettime is the last time the statistics counters were reinitialized. Sampletime is the last time the statistics were collected. Conn Cmd is the command used to initiate a connect with a remote system. A connect command is similar to the HDLC SABM frame. Conn Resp is the response to a connect command.
Expand-Over-ATM Line-Handler Processes Subsystem Control Facility (SCF) Commands Tx Window Available indicates the number of outstanding messages waiting for a reply. Mem Low is the number of times a memory low indication was given to the Expand-over-IP line-handler process from QIO. If the number is increasing, then the QIO resources are running low. Line Quality is the line-quality value computed every 500 frames. This value is not alterable.
Subsystem Control Facility (SCF) Commands Expand-Over-ATM Line-Handler Processes Sampletime is the last time the statistics were collected. Conn Cmd is the command used to initiate a connect with a remote system. A connect command is similar to the HDLC SABM frame. Conn Resp is the response to a connect command. This command completes the lowest level of Expand-over-ATM connection establishment. Data is the number of data frames sent and received.
Expand-Over-ServerNet, Expand-Over-X.25, and Expand-Over-SNA Line-Handler Processes Subsystem Control Facility (SCF) Commands Line Quality is the line-quality value computed every 500 frames. This value is not alterable. Line quality is computed using this formula: 100 * (( TOTAL FRAMES - ERROR FRAMES ) / TOTAL FRAMES) Line Quality reports a value below 100 only when the result of the formula is 95 or less; that is, when less than 95 percent of the packets are error-free.
Subsystem Control Facility (SCF) Commands Expand-Over-ServerNet, Expand-Over-X.25, and Expand-Over-SNA Line-Handler Processes Sampletime is the last time the statistics were collected. Bind indicates the line handler bind to an associate device (such as $ZZSCL or $X25AM). Aconn indicates the number of connects while in active mode. Pconn indicates the number of connects while in passive mode. An active connect message is expected as the reply.
SWAN Concentrator Lines Subsystem Control Facility (SCF) Commands notifies the linehandler of any process changes on the remote system or the connection (such as if the phandle changes). Data indicates the number of data frames received. Normal ServerNet traffic is not counted here because normal data traffic by-passes the line handler for these processes. Proc lookup failures process lookup failures indicate the number of failures to see the associate device.
Subsystem Control Facility (SCF) Commands SWAN Concentrator Lines BPID is the backup process ID. Resettime is the last timestamp that the statistics counters were reinitialized. Sampletime is the last timestamp that the statistics were collected. LEVEL 2 shows the counts of the Layer 2 frames sent and received by this input-output process (IOP) because statistics were last reset using the STATS RESET command or because the line-handler process was started.
Subsystem Control Facility (SCF) Commands SWAN Concentrator Lines SAMB specifies set asynchronous balanced mode. DISC specifies disconnect. UA specifies unnumbered acknowledgment frame counts. DM specifies disconnect mode. CMDR specifies command reject frame counts. RR specifies receive ready frames. RNR specifies receive not ready frames. REJ specifies reject frames. SREJ specifies selective reject frames. These apply only to satellite-connect lines. I-FRM specifies information frames.
Subsystem Control Facility (SCF) Commands SWAN Concentrator Lines number of frames was last transmitted. THRESHOLD applies only to lines attached to the SWAN concentrator. Line Quality is the line-quality value computed every 500 frames. This value is not alterable.
Subsystem Control Facility (SCF) Commands Considerations FCS Errs is the number of Frame Checksum (FCS) errors detected in frames received from the modem. Addr Errs is the number of frames received with the wrong address field detected by the Layer 2 protocol running in the CLIP. Length Errs is the number of U-frames and S-frames received that were longer than the expected frame size. Rcv Abort is the number of frames that ended in the abort sequence.
Subsystem Control Facility (SCF) Commands Examples This SCF command displays the statistical information for two lines named $LHSL2 and $LHSL3: -> STATS LINE ($LHSL2,$LHSL3) Expand Configuration and Management Manual — 529522-013 14 - 96
Subsystem Control Facility (SCF) Commands STATS PROCESS Command STATS PROCESS Command The STATS PROCESS command displays statistical information about the network control process ($NCP).
Subsystem Control Facility (SCF) Commands STATS PROCESS Command If the NETFLOW option is chosen, only one system name or number can be specified. If the AT option is omitted, the SCF target system name is used. If * is specified and the LOCALFLOW option is chosen, the aggregate packet statistics occurring at all accessible systems in the network are displayed. TO { system-list | * } where system-list is ( [ sys-a [ , sys-b [ , sys-c [ , .... ]]]] ). sys-a is { \system-name | system-number }.
STATS PROCESS Command Subsystem Control Facility (SCF) Commands The resulting display has the format as shown in Example 14-31 (example display of $NCP statistics with NETFLOW option): Example 14-31. STATS PROCESS $NCP Command, NETFLOW Option ->STATS PROCESS $NCP, NETFLOW, AT \N1, TO ( 2, 4, 5, 6, 7, 9, 10, 13, 14, 15) EXPAND Stats Process $NCP, NETFLOW Sampletime....
STATS PROCESS Command Subsystem Control Facility (SCF) Commands TOTAL PKTS-RCVD reports the total number of packets received by this system from a selected system because the line-handler process was started. Assume that you have entered this command: -> STATS PROCESS $NCP, LOCALFLOW, AT (\NODEC,\NODET,5,6,7,9) The resulting display has the format as shown in Example 14-32: Example 14-32.
STATUS Command Subsystem Control Facility (SCF) Commands STATUS Command The STATUS command displays the dynamic state, last error, and modifiable values of the specified object. It also displays specific subsystem attributes and values. STATUS is a nonsensitive command. The STATUS command has this syntax: STATUS [ / OUT file-spec / ] { PATH path-name | LINE line-name } [, DETAIL ] / OUT file-spec / causes any SCF output generated for the command to be directed to the specified file.
STATUS PATH Command Subsystem Control Facility (SCF) Commands PPID is the primary process ID. BPID is the backup process ID. Lines # reports the total number of lines associated with the path. The display for a path with the DETAIL option has the format as shown in Example 14-34: Example 14-34. STATUS PATH, DETAIL Command -> STATUS PATH $PATM4WI, DETAIL EXPAND Detailed Status PPID........ ( 1, 295) State....... STARTED Trace Status OFF Line LDEVs.. 148 184 Trace File Name.... PATH $PATM4WI BPID.......
Considerations Subsystem Control Facility (SCF) Commands configured with SUPERPATH_ON or the multi-CPU path feature will not be enabled. The configured value can be displayed using the INFO PATH command. Line LDEVs displays the LDEV identifiers for all the lines (up to eight) associated with the path. Trace File Name the name of the trace file specified in the SCF TRACE command.
STATUS LINE Command Subsystem Control Facility (SCF) Commands STATUS indicates the status of the line: ready or not ready. PPID is the primary process ID. BPID is the backup process ID. CIU-Path indicates which ServerNet wide area network (SWAN) concentrator path (A or B) is being used by this line to communicate with the SWAN concentrator. This field only applies to lines connected to a SWAN concentrator. ConMgr-LDEV is the logical device (LDEV) number of the concentrator manager (ConMgr) process.
Subsystem Control Facility (SCF) Commands STATUS LINE Command Path LDEV contains the logical device (LDEV) number of the path associated with this line. Trace Status indicates whether the line is being traced. Clip Status indicates the state of the communications line interface processor (CLIP) on the ServerNet wide area network (SWAN) concentrator used by this line. ConMgr-LDEV is the logical device (LDEV) number of the concentrator manager (ConMgr) process.
Subsystem Control Facility (SCF) Commands STATUS LINE Command Trace File Name the name of the trace file specified in the SCF TRACE command. For an Expand-over-IP, Expand-over-ATM, Expand-over-ServerNet, or Expand-overNAM line-handler process, the display for a LINE object with the DETAIL option has the format as shown in Example 14-37: Example 14-37. STATUS LINE, DETAIL Command, LINE Object -> STATUS LINE $SC151, DETAIL EXPAND Detailed Status PPID............... State.............. Trace Status.......
Subsystem Control Facility (SCF) Commands STATUS LINE Command BINDING indicates that the Expand-over-IP or line-handler process is binding to the local NonStop TCP/IP process, that the Expand-over-ATM line-handler process is binding to the configured permanent virtual circuit (PVC) name, or that the Expand-over-NAM line-handler process is binding to the local network access method (NAM) process.
Subsystem Control Facility (SCF) Commands STATUS LINE Command system. This state applies to Expand-over-ATM line-handler processes that use SVC connections only. PASSIVE indicates that the Expand line-handler process is waiting for the remote (destination) Expand line-handler process to initiate a connection.
STATUS LINE Command Subsystem Control Facility (SCF) Commands WAIT indicates that the Expand line-handler process is waiting for another process or subsystem. For more information, see the Detailed Info field. Status indicates the readiness status of the line or whether there is an error. Detailed Info displays the last error message returned to the Expand-over-IP or Expand-overATM line-handler process; this field is not displayed for Expand-over-NAM or Expand-over-ServerNet line-handler processes.
Considerations Subsystem Control Facility (SCF) Commands Table 14-7. Messages and Corresponding Event Numbers (page 2 of 2) Message Event Number ATM LIF error, error nnn 28 ATM LIF not found 29 ATM LIF is stopped 30 ATM LIF access state is down 31 ATM LIF inaccessible 32 For cause, effect, and recovery information for the event numbers generated by the Expand subsystem, see the Operator Messages Manual.
Subsystem Control Facility (SCF) Commands STOP Command STOP Command The STOP command terminates the activity of an object normally. It nondisruptively deletes all connections to and from an object. Upon successful completion, configured objects are left in the STOPPED state and nonconfigured objects are deleted. This is a sensitive command.
Subsystem Control Facility (SCF) Commands TRACE Command TRACE Command The TRACE command can request the capture of target-defined data items, alter trace parameters, and end tracing. TRACE is a sensitive command. An SCF trace produces a trace file that can be displayed using the commands available in the PTrace program. The trace file is created by SCF. The PTrace program is described in the PTrace Reference Manual and in Section 15, Tracing.
Subsystem Control Facility (SCF) Commands TRACE Command The TRACE command has this syntax for tracing the network control process ($NCP): TRACE [ [ [ [ [ [ [ [ / , , , , , , , OUT file-spec / ] PROCESS $NCP BACKUP ] COUNT count ] NOCOLL] PAGES pages ] RECSIZE size] SELECT select-spec ] TO file-spec ] or TRACE PROCESS $NCP , STOP / OUT file-spec / causes any SCF output generated for the command to be directed to the specified file. PATH path-name is the device name of the path to be traced.
TRACE Command Subsystem Control Facility (SCF) Commands PAGES pages pages is an integer in the range 4 to 64. PAGES controls how much space, in units of pages, is allocated in the extended data segment used for tracing. PAGES can be specified only when the trace is being initiated. The default value is 64 pages. RECSIZE size size is an integer in the range 16 to 4050. It controls the length of the data in the trace data records. The trace header is not included in RECSIZE. The default is 120 bytes.
TRACE Command Subsystem Control Facility (SCF) Commands The select-spec for the LINE object is described in Table 14-9. Table 14-9.
Considerations Subsystem Control Facility (SCF) Commands Table 14-10. PATH Object Trace Records (page 2 of 2) Mask Keyword Trace Record Bits Meaning Type (decimal) 4 System abort messages 6 L5 5 Security events 198 ALL 0-31 Sets all 32 bits *Applies only to paths not attached to a ServerNet wide area network (SWAN) concentrator. TO file-spec file-spec specifies the file to which tracing is to be initiated.
Subsystem Control Facility (SCF) Commands Examples Examples This SCF command initiates a trace of communications line interface processor (CLIP) inbound and outbound frames for $LINE1. One-thousand trace records are captured.
Subsystem Control Facility (SCF) Commands Examples Examples These examples show the version information returned for a specified process. VERSION PROCESS Command Example 14-38 shows the displays for the VERSION PROCESS command: Example 14-38. VERSION PROCESS Command -> VERSION PROCESS $SC254, DETAIL Detailed VERSION PROCESS \DRP25.
15 Tracing This section describes the tracing process when the SCF TRACE command is used with commands available in the PTrace facility. The SCF TRACE command allows you to select the records that you want written to a disk file. PTrace commands allow you to select which of those records you want formatted and sent to an output device. The output device can be a terminal, spooler, or printer.
Why Tracing Is Important Tracing Why Tracing Is Important Tracing allows HP personnel to see the history of a data communications link, including significant points in the internal processing of the traced entity. Isolating a data communications problem using an Expand trace is easier than using a system dump. How to Use Tracing For tracing to be effective, make sure you follow these guidelines: • • • • Always trace both ends of a path.
Tracing a Line in a Multi-Line Path Tracing Tracing a Line in a Multi-Line Path To start a trace of a line that is part of a multi-line path, enter -> TRACE LINE $line-name, TO $file-name, SELECT ALL, WRAP To stop the trace, enter -> TRACE LINE $line-name, STOP $line-name specifies the name of the line logical device. $file-name specifies the name of the file to which the trace records will be written.
Tracing Using SCF Tracing Figure 15-1 shows the relationship of the tracing process components when SCF is used. Figure 15-1.
PTrace Command Overview Tracing PTrace Command Overview Consider these, when you are using the PTrace facility: • • • You have not been provided trace-format information to read these formats because you do not have the source code. Therefore, when reporting problems, select the ALL option available in the SCF TRACE command. You should always specify the source disk file using the PTrace FROM command before any other PTrace command.
FILTER Command Tracing FILTER Command The FILTER command prevents the selected type of information from being sent to the output device. FILTER { option | option,option,...option | RESET } option defines the type of information you do not want to display or print to the output device. You can specify one or more options separated by commas: NOHDR filters trace record header information. NOL2 filters Layer 2 frame header information. NOL2RR filters Layer 2 Receive Ready (RR) frame information.
Examples Tracing If you issue the FILTER command with one set of selection options and then reissue it with a different set of selection options, the options entered with the second FILTER command are used to determine the trace information sent to the output device. The previously entered selection options are overridden; selection options are not cumulative.
Examples Tracing enter the FIND command without a string parameter and no previous FIND command with a string parameter has been issued, an error is returned. While the PTrace facility processes the FIND command, trace records will not be sent to the output device. If the specified string is found in an output line, the entire record is sent to the output device.
Example Tracing Example ?HEX ON LABEL Command The LABEL command formats state machine entries, frames, packets, message headers, and message data when set to ON (or defaults). This command is useful only for personnel who have source code listings. LABEL { ON | OFF } ON | OFF ON enables formatting of trace record information. This is the default when first entering PTrace. OFF disables formatting of trace record information.
Example Tracing F-key is pressed to specify the number of lines to display at the 6530 terminal. Table 15-2 lists the number of lines that are sent when specific function keys are pressed. Table 15-2.
OUT Command Tracing OUT Command The OUT command allows you to direct trace records from your terminal screen to the spooler or to a line printer. OUT [ TO file-name ] | STOP file-name specifies the name of the spooler or line printer to which you want to direct the trace records. STOP closes the spooler or line printer specified in the previous OUT command. As a result, subsequent trace records are displayed at your terminal. Example ?OUT $s.
Examples Tracing Examples This example displays records numbered 1 through 36: ?RECORD 1/36 This example displays records numbered 5 through 200: ?RECORD 5,200 SELECT Command The SELECT command sets the selection criteria for the record types sent to the output device. When PTrace is determining which records to display in response to a NEXT, FIND, or RECORD command, it checks the selection bit mask to determine whether the record is of a type you want to display.
SELECT Command Tracing Hex Mask Octal Mask L2 02 %H20000000 %0400000000 0 L3 03 %H10000000 %0200000000 0 L4 04 %H08000000 %0100000000 0 X $NCP SCF Bit PATH Keyword Line Table 15-3.
SELECT Command Tracing Expand Configuration and Management Manual — 529522-013 15 - 14
Part IV.
Part IV.
16 Expand Modifiers The Expand subsystem provides many modifiers to allow you to customize your network. These modifiers are contained in the profiles. Some modifiers are required, some are optional, some only appear in certain profiles, and others appear in several profiles. This section describes the modifiers that are related to the configuration of Expand line-handler processes.
Required Modifiers Expand Modifiers Table 16-1. Required Modifiers (page 2 of 3) Modifier Description ASSOCIATESUBDEV Must be used to specify • • • The name of the X25AM subdevice to which an Expandover-X.25 line-handler process will bind. The subdevice name of the SNAX/APN logical unit (LU) used by an Expand-over-SNA line-handler process. The name of the Asynchronous Transfer Mode (ATM) service access point (SAP) used by an Expand-over-ATM line-handler process.
Required Modifiers Expand Modifiers Table 16-1. Required Modifiers (page 3 of 3) Modifier Description DESTIPADDR Specifies the Internet Protocol (IP) address used by a remote (destination) Expand-over-IP line-handler process. Required by: Expand-over-IP line-handler processes if IPVER is IPv4. Default: 0.0.0.0. DESTIPPORT Specifies the port number used by a remote (destination) Expand-over-IP line-handler process. Required by: Expand-over-IP line-handler processes if IPVER is IPv4. Default: 1024.
Modifier Dictionary Expand Modifiers Modifier Dictionary This subsection lists in alphabetical order all the modifiers used to configure Expand line-handler processes and describes each modifier in detail. Default values and value ranges are described, if applicable.
ASSOCIATESUBDEV #n Expand Modifiers ASSOCIATESUBDEV #n Default: Units: Range: No default for Expand-over-NAM line-handler processes #IP for Expand-over-ATM line-handler processes Not applicable Not applicable This modifier is required for Expand-over-NAM and Expand-over-ATM line-handler processes only. n might specify these: • • • The name of an X25AM subdevice to which the Expand-over-X.25 line-handler process will bind.
CLBIDLETIMER Expand Modifiers CLBIDLETIMER Default: Units: Range: 10 Seconds 0.001 through 5:27.0 This modifier is applicable only to SWAN SAT line, which applies to the connection from the NonStop operating system to the SWAN adapter. Default value is the best value. When the data connection from the operating system to the SWAN adapter is idle, the Timer determines how often the linehandler process on the operating system will send a status probe to the SWAN adapter.
COMPRESS_OFF/COMPRESS_ON Expand Modifiers COMPRESS_OFF/COMPRESS_ON Default: Units: Range: COMPRESS_ON Not applicable Not applicable These path modifiers are applicable to all Expand line types. The COMPRESS_ON modifier specifies that data compression will be performed. Data compression causes multiple blanks, zeros, and nulls to be removed before data transmission. You can stop data compression from being performed by using the COMPRESS_OFF modifier.
DELAY n Expand Modifiers For Expand-over-IP and Expand-over-ATM line-handler processes, the CONNECTTYPE_PASSIVE modifier indicates that the Expand-over-IP or Expandover-ATM line-handler process will wait for incoming call requests; it will not initiate connect requests. If specified with AFTERMAXRETRIES_PASSIVE, the CONNECTTYPE_PASSIVE modifier will revert to active connect mode. To get the line up in passive connect mode, add the AFTERMAXRETRIES_DOWN modifier. DELAY n Default: Units: Range: 10 (0.
DESTIPADDR n Expand Modifiers DESTIPADDR n Default: Units: Range: 0.0.0.1 Not applicable Any 36-character string This modifier is applicable to Expand-over-IP line-handler processes only. This modifier specifies the Internet Protocol (IP) address used by the remote (destination) Expandover-IP line-handler process. It is the IP address specified in the remote line-handler process’ SRCIPADDR modifier. The address must be specified by number (for example, 130.252.12.3).
FLAGFILL_OFF/ FLAGFILL_ON Expand Modifiers FLAGFILL_OFF/ FLAGFILL_ON Default: Units: Range: FLAGFILL_ON Not applicable ON or OFF These Layer 2 modifiers are applicable to direct-connect and satellite-connect Expand line-handler processes only. The FLAGFILL_ON modifier causes a specific bit pattern called FLAG to be set during the idle period for a line. You can use the FLAGFILL_OFF modifier to cause bit-synchronous controllers to keep an idle line in the MARK HOLD instead of the IDLE FLAGS state.
IPVER_IPV4/IPVER_IPV6 Expand Modifiers IPVER_IPV4/IPVER_IPV6 Default: Units: Range: IPv4 Not applicable Not applicable This modifier specifies whether to create an IPv4 or an IPv6 socket. If IPv4, the ASSOCIATEDEV parameter can see any NonStop TCP/IP product and the SRCIPADDR and DESTIPADDR modifiers are used for the local and remote IP addresses. If IPv6, the ASSOCIATEDEV parameter must see NonStop TCP/IPv6 and the V6SRCIPADDR and V6DESTIPADDR modifiers are used for the local and remote IP addresses.
L2TIMEOUT n Expand Modifiers The result of this algorithm is the point at which the Expand line-handler process will declare the line unusable and begin rerouting. For most networks the result will be a value that allows you to bridge 10-second to 30-second network outages. Note. The L2TIMEOUT modifier is the time interval that the Expand line-handler process will wait for a response to a request at Layer 2 before retrying. You can modify the Layer 2 timeout using the L2TIMEOUT modifier.
L4CONGCTRL_OFF/L4CONGCTRL_ON Expand Modifiers The result of these algorithms is a one-hundredth of a second value. Note. If you use the Expand subsystem SCF ALTER LINE command to set the L2TIMEOUT modifier, you must convert the result of this algorithm to a time interval. For example, if the result was 300 (3 seconds), you would enter this command: ALTER LINE $device_name, L2TIMEOUT 3.00.
L4EXTPACKETS_OFF/L4EXTPACKETS_ON Expand Modifiers To calculate the size of the congestion window, use the following formula: = bandwidth * delay Where, is the maximum amount of data on the network circuit in bits. (bandwidth delay product) bandwidth is the capacity of the data link in bits per second delay is the end-to-end delay in seconds (round trip time).
L4RETRIES n Expand Modifiers for all lines in a path. The extended packet header format allows increased throughput over high bandwidth and multi-line paths. The L4EXTPACKETS_ON modifier is required for the variable packet size and congestion control features and for Expand line-handler processes that are part of a multi-CPU path. The L4EXTPACKETS_ON modifier is also required to support the larger message size of 60K bytes. If the modifier is not set ON, the message size will be 32K bytes.
L4TIMEOUT n Expand Modifiers L4TIMEOUT n Default: Units: Range: 2000 (20.00 seconds) 0.01 seconds 50 through 32767 (0.5 seconds through 5:27.67 minutes) This path modifier is applicable to all Expand line types. This modifier specifies the time interval, in one-hundredth of a second increments, that the Expand line-handler process will wait for a response to an end-to-end (Layer 4) request before retrying.
LINEPRIORITY n Expand Modifiers LINEPRIORITY n Default: Units: Range: 1 Integers 1 through 9 This modifier is applicable to all multi-line types. It can be set in the range 1 to 9. The default is 1. The higher the number, the lower priority to use that line. If lines have equal priority, the relative line speeds and transmission delays are used to select the next line.
NEXTSYS n Expand Modifiers NEXTSYS n Default: Units: Range: 255 Not applicable 0 through 254 This path modifier is applicable to all Expand line types. This modifier specifies the number of the system connected to the other end of the line. If you do not specify the NEXTSYS modifier, it defaults to an invalid value (255), and an operator message occurs during the initialization of this Expand line-handler process.
PATHBLOCKBYTES n Expand Modifiers PATHBLOCKBYTES n Default: Units: Range: 0 Bytes 0 or 1024 through 9180 for Expand-over-ATM and Expand-over-IP lines 0 or 1024 through 4095 for all other Expand line types This path modifier is applicable to all Expand line types. This modifier specifies the maximum size, in bytes, of a multipacket frame. You should read the description of the multipacket frame feature in Section 17, Subsystem Description, before using this modifier.
PATHTF n Expand Modifiers where framesize is the configured frame size, in words, as specified by the FRAMESIZE modifier. If n is not greater than the result of this equation, PATHPACKETBYTES will be set to zero, the variable packet size feature will be permanently disabled, and an operator message will be logged. To enable the PATHPACKETBYTES modifier, the setting must be greater than or equal to 1024.
PVCNAME n Expand Modifiers when the line is started. For more information on the DLC tasks, see the WAN Subsystem Configuration and Management Manual. PVCNAME n Default: Units: Range: None Not applicable Not applicable This modifier is applicable to Expand-over-ATM line-handler processes that used permanent virtual circuit (PVC) connections. This modifier identifies the name of the PVC used by the Expand-over-ATM line-handler process.
RSIZE n Expand Modifiers (NAM), or how many times the Expand-over-IP or Expand-over-ATM line-handler process will retry the probe of the remote Expand-over-IP or Expand-over-ATM linehandler process before declaring the network unavailable. A value of 0 indicates that timeouts are ignored and the connect state is maintained. See also TIMERPROBE n and TIMERRECONNECT n.
SPEED n Expand Modifiers SPEED n Default: Units: Range: 0 bits per second (bps) 0 or 1200 through 224000 This modifier provides a way of creating the time factor, and has a maximum value of 224,000. Its use is no longer recommended. Starting with G06.20, you can use the new parameters, LINETF n and PATHTF n, to set time factors for lines that will override all other parameters in calculating time factors.
SPEEDK n Expand Modifiers Table 16-2 shows the time-factor conversions for various SPEEDK settings: Table 16-2.
SRCIPADDR n Expand Modifiers SRCIPADDR n Default: Units: Range: 0.0.0.1 Not applicable Any 36-character string This modifier is applicable to Expand-over-IP line-handler processes only. This modifier specifies the Internet Protocol (IP) address associated with the NonStop TCP/IP process used by the local Expand-over-IP line-handler process. Because a NonStop TCP/IP process can have more than one IP address, you must specify to the Expandover-IP line-handler process which IP address to use.
TIMERINACTIVITY n Expand Modifiers multi-CPU feature significantly increases the maximum throughput of an Expand path, especially for Expand-over-IP connections. When the SUPERPATH_ON modifier is specified and there is an existing multi-CPU path, the new path joins the multi-CPU path. If there is no existing multi-CPU path, then a multi-CPU path is created that has the new path as its sole member.
TIMERRECONNECT n Expand Modifiers This specifies time interval that the Expand-over-NAM or Expand-over-ServerNet linehandler process will wait to send out a probe to obtain the status of the NAM process, or the time interval that the Expand-over-IP or Expand-over-ATM line-handler process will wait to probe the remote Expand-over-IP or Expand-over-ATM line-handler process.
V6DESTIPADDR n Expand Modifiers send before receiving acknowledgment from the network access method (NAM) process. For satellite-connect and direct-connect line-handler processes, this modifier specifies the number of packets that the Expand line-handler process can send before receiving a reply. When using the multipacket frame feature with satellite-connect line-handler processes, you do not need to have a large TXWINDOW modifier value if the PATHBLOCKBYTES or PATHPACKETBYTES modifier value is large.
V6SRCIPADDR n Expand Modifiers V6SRCIPADDR n Default: Units: Range: 0000:0000:0000:0000:0000:0000:0000:0000 Not applicable Any 45-character string This modifier is applicable to Expand-over-IP line-handler processes only. This modifier specifies the source Internet Protocol (IP) address associated with the NonStop TCP/IPv6 process used by the local Expand-over-IP line-handler process.
Single-Line Expand Line-Handler Process Modifiers Expand Modifiers Table 16-3.
Single-Line Expand Line-Handler Process Modifiers Expand Modifiers Table 16-3.
Multi-Line Path Modifiers Expand Modifiers Table 16-3.
Multi-Line Path Modifiers Expand Modifiers Table 16-4.
Multi-Line Path Modifiers Expand Modifiers Table 16-4.
17 Subsystem Description This section provides a high-level technical description of the architecture and dynamics of the Expand subsystem. You should be familiar with the information presented in this section before you attempt to configure, manage, or troubleshoot the Expand subsystem.
Expand Subsystem Components Subsystem Description Expand Subsystem Components The Expand subsystem comprises these major components: • • • Expand Line-Handler Processes on page 17-2 Network Control Process ($NCP) on page 17-6 Expand Manager Process ($ZEXP) on page 17-7 Expand Line-Handler Processes An Expand line-handler process is responsible for • • • • Maintaining the communications path between two adjacent nodes. A path is a logical connection that can consist of one or more parallel lines.
Expand Line-Handler Processes Subsystem Description A multi-CPU path is created by associating Expand line-handler processes with one another using the SUPERPATH_ON modifier. Each line-handler process that is a member of a multi-CPU path is configured in a different processor. Note. The path and line functions of an Expand line-handler process are described in more detail in Expand Subsystem and the OSI Reference Model on page 17-9.
Expand Line-Handler Processes Subsystem Description Expand-Over-NAM Line-Handler Processes Expand-over-NAM line-handler processes use the NETNAM protocol to access the network access method (NAM) interface provided by an X25AM or a SNAX/APN line-handler process. Note. For more information on the Expand-to-NAM interface, see Expand-to-NAM Interface on page 17-49. Expand-Over-NAM With X25AM The X25AM subsystem provides access to X.25 packet-switched data networks (PSDNs).
Expand Line-Handler Processes Subsystem Description configured to use a particular SNAX/APN line and logical unit (LU). At least one SNAX/APN line and one Expand line must be configured and started at each end of the SNA network through which the Expand-over-SNA line-handler processes will communicate. Expand-Over-IP Line-Handler Process The Expand-over-IP line-handler process uses the NonStop TCP/IP subsystem to provide connectivity to an Internet Protocol (IP) network.
Network Control Process ($NCP) Subsystem Description The Expand-over-ServerNet line-handler process manages security-related messages and forwards packets outside the ServerNet cluster. Other messages, such as incoming and outgoing data, usually bypass the Expand-over-ServerNet line-handler process and are handled directly by the ServerNet fabrics and the NonStop cluster switches; the Expand software is not involved.
Expand Manager Process ($ZEXP) Subsystem Description The network control process runs as logical device number 1. Network Utility Process Functions The network utility process, $ZNUP, answers requests that must wait for system information. It also responds to requests for the time at remote systems, the process information of remote processes, device-information requests, and traffic statistics. The network utility process runs as logical device number 4.
Components Summary Subsystem Description Components Summary Figure 17-1 illustrates an Expand network environment. Figure 17-1. Expand Network Environment Node \B Node \A Server Application Requester Application Kernel Kernel $ZNUP $ZNUP File System Message System Expand Message System File System Server Application Requester Application Expand Expand LineHandler Process Expand LineHandler Process $NCP $NCP $ZEXP $ZEXP VST010.
Expand Subsystem and the OSI Reference Model Subsystem Description Expand Subsystem and the OSI Reference Model The Expand line-handler process and $NCP components of the Expand subsystem contain some of the functions defined in the lower five layers of the OSI Reference Model. The Expand subsystem does not provide any Application Layer or Presentation Layer functions; these functions in addition to some Session Layer functions, are provided by the message and file systems.
Subsystem Description Expand Line-Handler Process Layer Functions Expand Line-Handler Process Layer Functions An Expand line-handler process implements several different protocols, including the HP proprietary End-to-End protocol. These protocols provide some of the functions defined by the lower five layers of the OSI Reference Model. OSI Session Layer (Layer 5) The OSI Session Layer coordinates processes and is responsible for the setup and termination of a communications path.
Subsystem Description Expand Line-Handler Process Layer Functions OSI Data Link Layer (Layer 2) The OSI Data Link Layer defines the rules for transmission on the physical medium.
Subsystem Description $NCP Layer Functions $NCP Layer Functions As shown in Figure 17-2 on page 17-9, $NCP provides some functions of both the OSI Transport and Network Layers. $NCP at the OSI Transport Layer $NCP provides part of the OSI Transport Layer function because it monitors processor UP and DOWN notifications.
Subsystem Description Path Function of the Expand Subsystem Path Function of the Expand Subsystem This subsection describes the end-to-end (Layer 3) and packet routing (Layer 4) messages that are generated by the End-to-End protocol. Layers 3 and 4 of the Endto-End protocol provide the path function of the Expand subsystem.
Subsystem Description Protocol Packet Types Connection Reset (CONN RST) A CONN RST is a connection-establishment–reset-setup packet. This packet is sent by $NCP at one of the two end nodes if a packet sequence problem is detected during connection establishment. Node Status (NODE STAT) A NODE STAT is a connection-establishment–system-status setup packet.
Subsystem Description Protocol Packet Types Link Cancel Request (LCAN) An LCAN is a control packet that is sent in response to a user request to abort a prior LRQ. Data Packet Acknowledgment (ACK) An ACK is a control packet. It is a positive acknowledgment of a data packet (either an LRQ or an LCMP). LRQ and LCMP packets can include acknowledgments. An ACK is only used to acknowledge data packets if no other data packets are ready to be sent.
Subsystem Description Packet Synchronization Trace Request (TRACE) A TRACE is a data packet that is sent in response to an SCF PROBE command. It contains the identifier of each node it encounters on its route from its sender to its receiver. PING Message A PING message is sent by an Expand line-handler process to measure the round trip time to a neighbor node.
Subsystem Description Example of End-to-End Protocol Packet Exchanges Normal Data Exchange Figure 17-3 is an example of an error-free exchange of data. Node \A sends two LRQs to node \B. Node \B sends ACK sequence number 2 to indicate the positive acknowledgment of node \A’s LRQs and then replies to each LRQ with an LCMP. Node \A acknowledges node \B’s LCMPs by sending ACK sequence number 2. Note. The sequence number of an LCMP does not necessarily match the sequence number of a corresponding LRQ.
Example of End-to-End Protocol Packet Exchanges Subsystem Description Data Exchange With Lost Data Figure 17-4 shows a data exchange in which a packet is not received. This problem is usually caused by network congestion and/or line failures and is indicated by a large number of NAKs on the SCF STATS display. Figure 17-4. Lost Data NODE \A NODE \B LRQ (0) LRQ (1) Lost packet LRQ (2) Out-of-sequence (OOS) timeout period NAK (1) LRQ (1) LRQ (2) ACK (3) LCMP (0) LCMP (1) ACK (3) LCMP (2) VST013.
Example of End-to-End Protocol Packet Exchanges Subsystem Description If node \B did not acknowledge node \A’s ENQ, node \A would continue sending ENQs until it reached its Level 4 retry limit or until node \B acknowledged the ENQ, whichever came first. Note. The default OOS timeout is 300 (3 seconds). The OOS timeout can be controlled with the Expand SCF ALTER PATH command or the WAN subsystem SCF ALTER DEVICE command. You can control the Expand subsystem’s retry limit by setting the L4RETRIES modifier.
Example of End-to-End Protocol Packet Exchanges Subsystem Description Node \B receives the ENQ, responds by resending ACK sequence number 3 to acknowledge the three LRQs, and then sends an LCMP in response to each LRQ. Node \A acknowledges node \B’s LCMPs with ACK sequence number 3. If node \B did not acknowledge node \A’s ENQ, node A would continue to send ENQs until it reached its Level 4 retry limit or until node \B acknowledged the ENQ.
Subsystem Description Layer 4 Send Window Node \A looks for responses to send to node \B and sends LCMP sequence number 0. This LCMP is a response to a prior request from node \B. When node \B acknowledges the LCMP with ACK sequence number 1, it deallocates its buffer and releases sufficient resources to receive node \A’s LRQ. Node \A resends its initial LRQ (which is now assigned LRQ sequence number 1) along with two more LRQs.
Subsystem Description Routing and Time Factors Routing and Time Factors This subsection explains how $NCP implements its routing scheme.
Subsystem Description • Setting Time Factors Expand’s multi-CPU paths are made up of two or more direct paths to the same neighbor that operate in parallel. So the calculation of a multi-CPU path time factor is done in a very similar way as the time factor for a multi-line path (where you have parallel lines). The time factor for a path to a remote (multi-hop) node is calculated as the sum of the time factors for all direct (single-hop) paths that make up the path.
Subsystem Description Negotiating Path Time Factors RSIZE n has a range of 0 to 186 to designate the line time factor in selecting the best path to other nodes in the network. A smaller number indicates a more desirable path for routing. As always, the actual time factor used for a path between two immediate neighbors is negotiated and the larger of their respective calculations is used.
Subsystem Description • • Network Routing Table (NRT) and Multiple Path Table (MPT) If two or more routes have the same TF, the route that has the lowest hop count (HC)—the fewest intervening nodes—is selected. Each path between two nodes is one hop. For example, a route that includes one passthrough node has a HC of 2; a route that includes two passthrough nodes has an HC of 3, and so on.
Subsystem Description Network Routing Table (NRT) and Multiple Path Table (MPT) $NCP sends routing information to the $NCPs at its neighbor nodes at these times: • • As soon as $NCP becomes aware of a change in the network, such as a line going up or down or a node being added or deleted. During a regular maps exchange. (Maps exchanges are described in Regular Maps Exchanges on page 17-27.
Subsystem Description Calculating Route Time Factors Regular Maps Exchanges A maps exchange is a periodic sharing of network map information. Maps messages, called distance vector (DV) messages, are exchanged at variable-rate intervals by default. You can specify a fixed five-minute interval exchange by setting the AUTOMATICMAPTIMER modifier. Note. The AUTOMATICMAPTIMER modifier is explained in Section 6, Configuring the Network Control Process.
Subsystem Description Routing Algorithms Routing Algorithms Routing algorithms determine what and how much routing information $NCP will share with the $NCPs at its neighbor nodes. You can select from two different routing algorithms by setting the ALGORITHM modifier: modified split horizon (MSH) and split horizon (SH). MSH is the default algorithm. Note. ALGORITHM 0 specifies MSH, and ALGORITHM 1 specifies SH. The ALGORITHM modifier is explained in Section 6, Configuring the Network Control Process.
Subsystem Description Routing Algorithms Figure 17-9. Routing Information With the MSH Algorithm Node \A Node \B TF 4 TF 1 TF 1 TF 1 TF 1 NRT Node \C To Nodes Node \E Node \D \C Via Nodes \B \E \A 2 (2) -- -- \B -- 1 (1) -- \C 1 (1) -- -- \E -- -- 1 (1) VST018.
Subsystem Description Routing Algorithms Split Horizon (SH) When the split horizon (SH) algorithm is used, $NCP tells its neighbor $NCP the bestpath route or the second-best route to a destination node. If the best-path route leads through the neighbor being updated, $NCP will tell its neighbor $NCP its second-best route as long as that route does not lead directly through the neighbor being updated. Figure 17-10 shows the routing information known by node \D when the SH algorithm has been selected.
Subsystem Description Multi-CPU Paths The disadvantage of the SH algorithm is that it increases the occurrence of loop routing, which results in excessively long routes. Loop routing most often occurs in large, multi-ringed networks. For example, in Figure 17-10 on page 17-30, suppose the path fails between node \D and node \E. If a message is sent from node \A to node \E, the Expand subsystem will attempt to reroute traffic in this sequence: • • Through nodes \B, \A, \C, and \D.
Subsystem Description Multi-CPU Paths Neighbor Nodes For neighbor nodes, Expand line-handler pairs apply only to each source and destination processor combination, not to entire systems. This method allows traffic between neighbor nodes to be distributed over all the paths in the multi-CPU path. Message order is preserved only between processor pairs instead of between entire systems. $NCP does not establish Expand line-handler pairs with a neighbor node.
Subsystem Description Multi-CPU Paths Caution. A multi-CPU rebalance can introduce a temporary disruption in the network, similar to but in general less than that caused by an Expand path change. For that reason, it is recommended that rebalances be limited to off-peak hours unless an imbalance is clearly causing immediate problems. The three goals are handled in three separate steps. 1.
Subsystem Description • • • • • Multi-CPU Routing Examples When a new path comes up. (This is similar to what happens in normal paths when a new path that has a lower TF is discovered.) At configurable times during the day. You can use the SCF ALTER PROCESS, AUTOREBALANCE command to specify when rebalancing should occur. Both the time of day and the interval between rebalance attempts can be specified, allowing you to schedule a rebalance when traffic is minimal. Immediately.
Subsystem Description Multi-CPU Routing Examples In Figure 17-11, the network includes four normal paths and two multi-CPU paths. A multi-CPU path that consists of three paths is configured between node \B and node \C, and a multi-CPU path that consists of two paths is configured between node \C and node \E. Figure 17-11.
Subsystem Description Multi-CPU Routing Examples Combination 1: Local Source Node and Neighbor Destination Node In this scenario, the source node is the local node and the destination node is a neighbor; a message is sent directly from one node to the other. When the first message destined for each processor in the neighbor node is sent, the originating processor selects a local path to the destination node and selects a pair of Expand line-handlers for the source and destination processor combination.
Subsystem Description Multi-CPU Routing Examples entry in all processors in the system. If a message is received from a neighbor node and no RPT entry exists, the message is dropped. For example, in Figure 17-11 on page 17-35, when $NCP on node \A first detects the existence of node \C, $NCP sends a Connect Request message to node \B which is forwarded through multi-CPU path 1 to node \C.
Subsystem Description Message Handling and Buffer Allocation Message Handling and Buffer Allocation This subsection presents a high-level overview of how data is sent and received over an Expand network and how incoming and outgoing data is buffered. It is necessary to understand this information to effectively configure, manage, and troubleshoot an Expand network. This subsection describes these topics: • • Outgoing Traffic Flow on page 17-38 Incoming Traffic Flow on page 17-42 Note.
Subsystem Description Outgoing Traffic Flow Locally Originated Traffic Flow Figure 17-12 illustrates the path of a locally originated outgoing message. Figure 17-12.
Subsystem Description Outgoing Traffic Flow password exists for the destination node, the request is completed with an error (filesystem error 48, security violation) and is not sent. If the COMPRESS_ON modifier is set, the Expand line-handler process tries to compress the data in the message. When compression is configured, groups of consecutive zeros (0), spaces, and NULLs are replaced with indicator and count values.
Subsystem Description Outgoing Traffic Flow Note. Requests are formatted into request data packets, or LRQs. Replies are formatted into reply data packets, or LCMPs. LRQs and LCMPs are explained in Protocol Packet Types on page 17-13. $NCP and Passthrough Traffic Flow Figure 17-13 illustrates the path of outgoing $NCP and passthrough traffic. Figure 17-13.
Subsystem Description Incoming Traffic Flow When passthrough and $NCP traffic is queued to the outgoing list, it occupies buffer space in the Expand line-handler process buffer pool. $NCP formats $NCP messages into packets before sending them to the appropriate Expand line-handler process for transmission. Passthrough traffic is already in the form of packets; it is not reassembled into messages before being forwarded to the destination node. Note.
Subsystem Description Incoming Traffic Flow As shown in Figure 17-14, the Expand line-handler process manages different types of incoming packets differently. These subsections describe each type of packet and explain how each is processed by the Expand line-handler process. Figure 17-14.
Subsystem Description Incoming Traffic Flow Request Packets An incoming request packet, or an LRQ, is a fragment of a request message destined for a process at the local node. The first LRQ includes the length of the total message, in bytes. The Expand line-handler process reserves memory from its buffer pool for the total message based on the length information contained in the first packet. Note. LRQs are also described in Protocol Packet Types on page 17-13.
Subsystem Description Incoming Traffic Flow After the reply message is successfully processed, the message system routes the reply message to the appropriate process, and the Expand line-handler process releases the buffer pool used by the reply message. $NCP and Passthrough Packets An incoming $NCP packet is a packet received from the $NCP at a neighbor node and destined for the $NCP of the local node.
Subsystem Description Message Buffering Message Buffering The previous subsection showed that Expand line-handler processes buffer incoming and outgoing requests so that data can be transferred between processes on different nodes. This subsection describes in greater detail the data space allocated to the Expand line-handler process for message transfer and how you can affect the size of that buffer space.
Subsystem Description Global Variables Global Variables The global variables space contains the Expand subsystem software global variables. The Expand subsystem determines how much global variables space to allocate according to the number of lines in a path controlled by the Expand line-handler process. Stack The Expand subsystem allocates 700 words to the stack. Control Blocks The Expand subsystem preallocates space for many data structures that are likely to be used during normal operation.
Subsystem Description Shared Memory Area for QIO The SCF attribute EXTMEMSIZE n allows you to specify the base size of extended memory for the pool, from a default of 2 megabytes to as much as 32 megabytes. This extra memory will be of invaluable help to applications such as the Remote Database Facility (RDF) which in the past suffered from memory pool problems and thus reduced performance.
Subsystem Description Expand-to-NAM Interface Expand-to-NAM Interface This subsection describes how Expand-over-NAM and Expand-over-ServerNet linehandler processes access a network access method (NAM) interface. The information presented in this subsection will help you effectively configure, manage, and troubleshoot an Expand network that includes X.25, SNA, or ServerNet connections.
Subsystem Description Connection Establishment Connection Establishment Figure 17-16 illustrates the events that occur when Expand-over-NAM and Expandover-ServerNet line-handler processes successfully establish a connection through a NAM interface. Figure 17-16.
Subsystem Description Connection Establishment The Expand-over-NAM or Expand-over-ServerNet line-handler process accesses a subdevice by sending a bind request to the NAM process. A bind request is roughly equivalent to an OPEN procedure.
Subsystem Description Sending and Receiving Data connect request. If you specify the MAXRECCONNECTS modifier, you can also control what happens after the reconnect limit has been reached by specifying the AFTERMAXRETRIES_PASSIVE or AFTERMAXRETRIES_DOWN modifier. Passive Connect Request When the Expand-over-NAM or Expand-over-ServerNet line-handler process issues a passive connect request, the NAM waits for an incoming connect request.
Subsystem Description Expand-to-IP Interface Expand-to-IP Interface This subsection describes how the Expand-over-IP line-handler process accesses an Internet Protocol (IP) network. You should be familiar with the information presented in this subsection before attempting to configure, manage, or troubleshoot an Expand network that includes IP connections.
Subsystem Description Expand-over-IP Connection Establishment Each NonStop TCP/IP process appears to an IP network as a separate host and is associated with a separate IP address. An IP address is a 4-octet (32-bit) numeric value identifying a particular network (network address portion) and a local host on that network (local address portion). A NonStop TCP/IP process can be associated with more than one IP address.
Subsystem Description Expand-over-IP Connection Establishment received, the local Expand-over-IP line-handler process considers the line to be up. Various path parameters are then exchanged with the remote Expand-over-IP linehandler process. If the local Expand-over-IP line-handler process does not receive a response within the timeout period, it sends another Connect Command frame. It will continue to send Connect Command frames indefinitely until a response is received.
Subsystem Description Sending and Receiving Data Sending and Receiving Data After a connection has been established, the local and remote Expand-over-IP linehandler processes communicate through their associated NonStop TCP/IP or TCP6SAM processes using the QIO mechanism. You can control how many packets the Expand-over-IP line-handler process can send to the NonStop TCP/IP process before waiting for a reply by specifying the TXWINDOW modifier. Note.
Subsystem Description Forwarding Expand-over-IP Packets to Other Expand Line-Handler Processes Figure 17-17. Expand-Over-IP Packet Forwarding Node 1 Application Message System Expand LineHandler Process Node 2 TCP/IP Process IP Network Message System Expand Line-Handler Process Expand LineHandler Process TCP/IP Process Node 3 Application Message System Direct-Connect Connection Expand Line-Handler Process VST034.
Expand-to-ATM Interface Subsystem Description Expand-to-ATM Interface This subsection describes how the Expand-over-ATM line-handler process accesses an Asynchronous Transfer Mode (ATM) network. You should be familiar with the information presented in this subsection before attempting to configure, manage, or troubleshoot an Expand network that includes ATM connections.
Expand-over-ATM Connection Establishment Subsystem Description SVC Connections An SVC is a dynamically established virtual circuit. Each SVC is automatically assigned an SVC name by the ATM3SA when the circuit is established. An SVC is described by the SVC object, which is subordinate to the LINE object.
Expand-over-ATM Connection Establishment Subsystem Description The default connect method is active connect. You can cause the Expand-over-ATM line-handler process to use the active connect method by specifying the CONNECTTYPE_ACTIVEANDPASSIVE modifier. Active Connect Request When the Expand-over-ATM line-handler process issues an active connect request, it tries to initiate a connection by sending a Connect Command frame to the remote Expand-over-ATM line-handler process.
Sending and Receiving Data Subsystem Description attribute does not correspond to an Expand modifier and can therefore be changed only by using the SCF interface to the Expand subsystem.) You can limit the number of times the Expand-over-ATM line-handler process will send a Connect Command frame by specifying the MAXRECONNECTS modifier.
Forwarding Expand-over-ATM Packets to Other Expand Line-Handler Processes Subsystem Description Forwarding Expand-over-ATM Packets to Other Expand LineHandler Processes Packets received by an Expand-over-ATM line-handler process can be forwarded to another type of Expand line-handler process, either on the same processor or on a different processor. Packet forwarding is performed via the message system; this allows servers without Expand-over-ATM line-handler processes to access an ATM network.
Multipacket Frame Feature Subsystem Description Multipacket Frame Feature The multipacket frame feature is a performance enhancement designed to increase throughput and processor efficiency on all connection types. This subsection briefly describes how the multipacket frame feature works so that you can effectively configure and use this feature in your network.
Constructing Multipacket Frames Subsystem Description • • If the Layer 2 protocol is NETIP, each Expand packet is handled as a separate UDP frame. If the Layer 2 protocol is NETATM, each Expand packet is handled as a separate ATM frame. Figure 17-19 shows how Expand packets are sent over a direct-connect (HDLC) connection when the multipacket frame feature is not selected. In Figure 17-19, a message is passed to a direct-connect Expand line-handler process that requires six Expand packets.
Path Initialization Subsystem Description When constructing a multipacket frame, an Expand line-handler process continues to add packets to the multipacket frame until the frame can no longer accommodate another full packet or until the current number of packets in the multipacket frame is equal to 32. Figure 17-20. Multipacket Frame Feature Selected Message Direct-Connect Expand LineHandler Process Multipacket Frame 1 2 3 4 5 6 1 2 3 4 5 6 HDLC-Type Frame VST032.
Multipacket Frame Configuration Subsystem Description Multipacket Frame Configuration The FRAMESIZE modifier determines the maximum Expand packet size, in bytes, according to this formula: packet_size = ( FRAMESIZE - 4 ) * 2 For example, the default value for the FRAMESIZE modifier is 132, establishing a maximum packet size of 128 words (or 256 bytes). The FRAMESIZE modifier must be the same value for every Expand line-handler process in the network. Note.
Variable Packet Size Feature Subsystem Description Variable Packet Size Feature The variable packet size feature is a performance enhancement designed to improve bulk transfers over all connection types. The variable packet size feature effectively overrides the packet size calculated from the FRAMESIZE modifier value by allowing you to configure a maximum packet size, which is used for both single-packet and multipacket frames, on a per-path basis.
Mixing Extended and Nonextended Packets Subsystem Description • • • The variable packet size feature does not provide any benefit on paths configured with the L4EXTPACKETS_OFF modifier, which specifies that the extended 64-byte packet header format not be used. Nonextended frames are not fragmentable and therefore must use the network-wide FRAMESIZE modifier value.
Considerations for Paths Using the Variable Packet Size Feature and the Multipacket Frame Feature Subsystem Description Considerations for Paths Using the Variable Packet Size Feature and the Multipacket Frame Feature The main difference between the variable packet size feature and the multipacket frame feature is that the multipacket frame feature benefits users who send many small concurrent requests, while the variable packet size feature benefits users who send large blocks of data (bulk transfers).
Congestion Control Feature Subsystem Description Figure 17-22. Congestion Control Not Enabled Node \B Node \A Node \C On Off On Off L4CONGCTRL_ON L4CONGCTRL_OFF L4CONGCTRL_ON Congestion Control On Congestion Control On VST014.vsd Nodes that support congestion control are compatible with nodes that do not. However, connections between such nodes will not use congestion control. In Figure 17-23, congestion control is enabled on nodes \A and \C but is not enabled on node \B.
Congestion Control Configuration Subsystem Description The congestion control feature uses end-to-end mechanisms for congestion control and error-recovery. It does not provide any mechanisms for indicating congestion along intermediate nodes. Congestion Control Configuration You select the congestion control feature by specifying the L4CONGCTRL_ON modifier. This modifier enables the congestion control mechanism for sending packets on a specific path.
Multi-CPU Feature Subsystem Description Multi-CPU Feature The Expand multi-CPU feature enables you to spread the communications load over multiple processors by connecting multiple Expand line-handler process, each in a separate processor, between two adjacent nodes.
Multi-CPU Considerations Subsystem Description modifier and one or more the existing paths are in a multi-CPU path, then the new path joins the multi-CPU path. If there is no preexisting multi-CPU path, then a multi-CPU path is created with the new path as its sole member. When a path comes up, it negotiates its multi-CPU membership with the Expand linehandler process on the other end of the connection.
Subsystem Description Multi-CPU Considerations Expand Configuration and Management Manual — 529522-013 17 - 74
Part V.
Part V.
18 Managing the Network This section explains how to access network resources, set up network security, and monitor, reconfigure, and control an Expand network.
Using TACL to Manage Remote Files Managing the Network Using TACL to Manage Remote Files One of the major features of the Expand subsystem is network transparency. Because access to the network is transparent to the user, the Expand subsystem does not include its own network commands. This subsection describes how to use TACL commands to manage remote files. Note. Selected TACL commands are described in this subsection.
Changing Your Default Values Managing the Network Changing Your Default Values Each user on the system has two sets of default values: current default values and saved default values. Saved default values are in effect when you log on. Current default values define your present location or frame of reference in the system and network. You can move around on the system and network by changing the current system, volume, and subvolume defaults.
Gaining Access to Remote Nodes Managing the Network Note. Changing the current default node does not log you onto the other node. To log onto a node other than the one where your current TACL process is running, you must first start a remote TACL process on that node. Logging on to a remote node is described in Starting and Quitting a Remote TACL Process on page 18-4.
Gaining Access to Remote Nodes Managing the Network is part of a network that includes the \HERST node, you can start a TACL process on \HERST by entering this command: \HERST.TACL The TACL program returns the initial TACL prompt, and you can now log onto the \HERST system. A remote TACL started this way does not have a backup process. If you want the remote TACL process to run as a process pair, enter this command instead of the previous command: \HERST.
Gaining Access to Remote Nodes Managing the Network Running a Program on a Remote Node When you want to run a program on the network, the program file must reside on the node where the program is to run. You can use the explicit and implicit RUN commands to run a program at a remote node the same way you would use these commands to run a program on the local node. Note. These examples and explanations assume that the proper network access rights are in effect.
Setting Up Network Security Managing the Network Setting Up Network Security One of the first tasks you must perform after completing the network configuration is to set up access to remote resources for network users. To access a process, device, or file on a remote system, a user must have the appropriate access.
Establishing Remote Passwords Managing the Network GROUP . USER ADMIN .BILL I.D. # 6,14 SECURITY NONO DEFAULT VOLUMEID $PUBS.BILL Establishing Remote Passwords After user IDs for network users are added to relevant nodes on the network, remote passwords must be established for each remote node. Remote passwords are specified with the TACL REMOTEPASSWORD command or the RPASSWRD program. For example, ADMIN.BILL (user ID 6,14) was added at nodes \WEST and \EAST.
Remote Process Security Managing the Network When the appropriate passwords are established for a user, the user can access files remotely without being aware of the network passwords. • • The absence of an allow-access password prevents remote access by anyone acting as that user. Thus, if MARKETING.SUE does not supply an allow-access password, no remote user with the same user ID can access MARKETING.SUE’s home system as MARKETING.SUE.
Remote TACL Processes Managing the Network Remote TACL Processes Openers of a file are either local or remote with respect to the file. A local user is logged onto the node on which the file resides. A remote user is logged on to a different node in the same network. A remote accessor of a node can become a local accessor by running a TACL process in the remote node and logging on. For example, if remote passwords are established so that user ADMIN.BILL at \WEST can access node \EAST, ADMIN.
Subnetwork Security Managing the Network managers. The local password is different for each node and is given only to users who are allowed to access all nodes on the network. Only users who know the local password can log on as NET.ACCESS. While logged on as NET.ACCESS, these users can access remote files. For example, this command allows users to access remote files secured for access by NET.ACCESS: LOGON NET.
Additional Security Techniques Managing the Network Additional Security Techniques The Safeguard security system extends the security offered by the NonStop operating system. Safeguard does not need to be installed on every system on the network and can be controlled by a single system.
Monitoring Network Activity Managing the Network Monitoring Network Activity Network monitoring includes gathering statistical information, checking the status of hardware and software components, and displaying configuration values.
Displaying $NCP Information Managing the Network Table 18-1. Expand SCF Commands for $NCP Information (page 2 of 2) SCF Command Information Reported INFO PROCESS $NCP, PATHSETS Displays the NCP pathmap information similar to the LINESET command, but displays it in a different format. This format displays both the line-handler LDEV and name in addition to the other information already in the LINESET command.
Displaying Expand Line-Handler Process Information Managing the Network Table 18-2 lists the WAN subsystem SCF commands that display $NCP information. Table 18-2. WAN SCF Commands for $NCP Information SCF Command Information Reported INFO DEVICE $ZZWAN.#NCP Displays the primary and backup processors, type, record size, object file, and profile used by $NCP. The DETAIL option can be used to display device-specific modifiers and modifier values. INFO PROFILE $ZZWAN.
Displaying Expand Line-Handler Process Information Managing the Network Table 18-4 lists the subtype values associated with single-line Expand line-handler processes. Table 18-4. Subtype Values for Single-Line Line-Handler Processes Line Type Subtype Direct-connect 5 Satellite-connect 5 Expand-over-NAM 0 Expand-over-IP 0 Expand-over-ATM 0 Expand-over-ServerNet 4 Table 18-5 lists the subtype values associated with multi-line paths (path and line logical devices). Table 18-5.
Displaying Expand Line-Handler Process Information Managing the Network Table 18-6. WAN SCF Commands for Expand Line-Handler Process Information (page 2 of 2) SCF Command Information Reported STATUS DEVICE $ZZWAN.#device_name Displays the dynamic state, logical device (LDEV) number, and primary and backup process identification numbers (PINs) for a selected Expand linehandler process.
Displaying Expand Line-Handler Process Information Managing the Network Table 18-7. Expand SCF Commands for Line Information (page 2 of 2) SCF Command Information Reported STATUS LINE $device_name Displays status information for a selected Expand linehandler process. Information displayed includes the summary state of the line, primary process ID (PID), and backup process ID (PID).
Starting and Stopping Tracing Managing the Network Starting and Stopping Tracing The Expand subsystem SCF TRACE command allows you to select the records that you want written to a disk file. You can then use PTrace commands to select records to be formatted and sent to an output device. Table 18-9 lists the Expand subsystem SCF commands that can be used to start and stop tracing. Table 18-9.
Reconfiguring the Network Managing the Network Reconfiguring the Network Network reconfiguration tasks include: • • • • • • • • Adding and Deleting Expand Line-Handler Processes Adding and Deleting $NCP Changing $NCP Modifiers Changing Expand Line-Handler Process Modifiers Changing Profiles Adding Nodes to the Network Removing Nodes From the Network Changing System Names and Numbers Note.
Changing Expand Line-Handler Process Modifiers Managing the Network Changing Expand Line-Handler Process Modifiers You can use the WAN subsystem SCF ALTER DEVICE command to change any modifier or modifier value in the device record for a specific Expand line-handler process. You can use the Expand subsystem SCF ALTER LINE and ALTER PATH commands to change certain Expand line-handler process modifiers and modifier values.
Removing Nodes From the Network Managing the Network Creating and starting Expand line-handler processes is explained in detail in Section II, Configuring the Expand Subsystem. Note. Before you can start an Expand line-handler process, other processes might need to be present and running in your system. For more information, see Section II, Configuring the Expand Subsystem.
Changing System Names and Numbers Managing the Network Step 1: Stop the lines You must stop the Expand lines at the local node and the corresponding Expand lines at adjacent (or neighbor) nodes using one of these Expand subsystem SCF commands: ABORT LINE $device_name ABORT PATH $device_name Note. Use the Expand subsystem SCF ABORT PATH command for multi-line paths.
Changing System Names and Numbers Managing the Network The SCF SAVE command is described in detail in the SCF Reference Manual for GSeries RVUs. Step 2: Isolate the duplicate nodes You must isolate all nodes with the duplicate names or numbers from the network by stopping all connections between these nodes and those adjacent to them using one of these Expand subsystem SCF commands: ABORT LINE $device_name ABORT PATH $device_name Note. Use the ABORT PATH command for multi-line paths.
Changing System Names and Numbers Managing the Network If you are changing both the system name and system number, you can more efficiently use system resources (because these attributes are stored in the server hardware) by grouping them into one command rather than by entering each separately; for example: ALTER, SYSTEM_NAME \EAST, SYSTEM_NUMBER 44 Caution. Be sure that you enter the ALTER command correctly.
Controlling the Network Managing the Network Step 7: Delete the system name and/or system number from all NRTs After the system name or system number have been changed and the system loaded, this Expand subsystem SCF command should be performed: DELETE ENTRY $NCP.* The above command should be performed at every other node in the network to avoid conflicts in the network routing tables (NRTs) such as duplicate system names or numbers.
Stopping and Starting Lines and Paths Managing the Network Stopping and Starting Lines and Paths The SCF interface to the Expand subsystem provides commands to control lines and paths. Table 18-11 describes each of these commands and the actions they perform. Table 18-11. Expand SCF Control Commands SCF Command Action Performed ABORT LINE $device_name Terminates the operation of a line as quickly as possible. Only enough processing is done to ensure the security of the subsystem.
Switching Primary and Backup Processes Managing the Network Switching Primary and Backup Processes The SCF interface to the Expand subsystem provides commands to change the primary and backup processes, Table 18-12 describes these commands. Table 18-12.
19 Tuning This section provides guidelines for improving network performance and describes the tools available for measuring performance. • • • • The Role of Network Tuning on page 19-1 Performance Factors on page 19-2 Measuring and Mapping an Expand Network on page 19-22 Tuning Examples on page 19-28 To obtain the greatest benefit from this section, you should be familiar with the material presented in Section 2, Expand Overview and Section 3, Planning a Network Design. Note.
Performance Factors Tuning Performance Factors This subsection describes the factors that can be adjusted to improve Expand linehandler process performance and processor utilization. Performance factors, and their relative effect on the tuning goals described earlier in this section, are shown in Table 19-1. How to Use the Performance Factors Table To use Table 19-1, vertically scan the Tuning Goals columns.
Multipacket Frame Size Tuning Multipacket Frame Size The multipacket frame feature is designed to reduce processor use at nodes where the workload is high and the configured frame size must remain unchanged. This feature enables multiple packets to be placed in a single frame (instead of a single packet in a single frame). The multipacket frame feature is supported for all line types.
Multipacket Frame Size Tuning Figure 19-1 shows throughput gains and losses resulting from the use of multipacket frames. Figure 19-1. Throughput With and Without Multipacket Frames Kilobits per second 1800 1600 1400 1200 1000 800 600 400 200 0 132 516 744 Framesize (in words) Single-packet Multipacket VST074.vsd Processor Use and Message Size Multipacket frames can improve the processor efficiency of all line types.
Variable Packet Size Tuning Multipacket Frame Configuration The multipacket frame size is determined by the value assigned to the PATHBLOCKBYTES modifier. When the variable packet-size feature (PATHPACKETBYTES modifier) is used, the Expand subsystem should be able to send a full variable-size packet inside a multipacket frame. For this reason, the PATHBLOCKBYTES modifier must be set to a value greater than or equal to the PATHPACKETBYTES modifier value.
Variable Packet Size Tuning larger bulk transfers are much more expensive to form into small packets and route in multihop networks. Extended Packet Format The extended packet format (L4EXTPACKETS_ON modifier) provides a means to fragment packets in transit across the network. The extended packet format must be enabled for the variable packet-size feature to function.
Application Message Size Tuning Note. If you use the Expand subsystem SCF ALTER LINE command to set the L2TIMEOUT modifier, you must convert the result of this formula to a time interval. For example, if the result is 300 (3 seconds), you will enter this command: ALTER LINE $device_name, L2TIMEOUT 3.00 For more information on configuring the variable packet-size feature, see Variable Packet Size Feature on page 17-67.
Application Message Size Tuning As shown in Figure 19-2 on page 19-7, QIO recognizes that the data is to be sent to an application that is not on the local node, and it routes the request to the appropriate Expand line-handler process. If the Expand packet size is large enough to hold all the message from the application, the Expand line-handler process puts the message into a single packet.
Packet Format Tuning Packet Format The Expand subsystem enforces a minimum value of 1024 bytes for the variablepacket size (set with the PATHPACKETBYTES modifier). The default value for PATHPACKETBYTES (1024 bytes) yields the same data-per-packet percentage as nonextended packets with a frame size of 132 words. Table 19-2 compares the data-per-packet percentages for nonextended packet (L4EXTPACKETS_OFF modifier) and extended packet (L4EXTPACKETS_ON modifier) header formats.
Layer 2 Window Size Tuning Expand-Over-IP Connections Expand-over-IP line-handler processes use the User Datagram Protocol (UDP) services provided by a NonStop TCP/IP process to transmit data across an Internet Protocol (IP) network. Because data transfer with UDP is not guaranteed, the Expand End-to-End protocol is used to achieve reliable communications for Expand-over-IP connections.
Processor Type Tuning Processor Type The processing power of the Integrity NonStop NS-series servers (through which a message is transmitted) determines throughput if there are no bottlenecks in the other components of the network. The relative processor power factors are a good starting point for estimating Expand line-handler process performance limits. Process location and load balancing within a system can also have a major impact on network performance.
NAM Interface Tuning NAM Interface When a NAM interface is used, Layer 2 functions are managed by the NAM process, thus reducing the load on the Expand line-handler process. Although the Expand linehandler process has a potentially greater upper throughput limit when it uses a NAM interface, overall system processor requirements are not reduced because some of the workload is shifted to the NAM process.
Multi-Line Paths Tuning Multi-Line Paths The multi-line path feature enables you to configure eight parallel lines between the same two nodes. The advantages of multi-line paths include increased fault-tolerance and additional bandwidth. The main disadvantage of multi-line paths is increased processor overhead, which occurs primarily because extra processing must be done to select the best line for each frame transmitted and to guarantee sequencing of packets received across multiple lines.
Multi-CPU Paths Tuning Window Size If a line is added to a path using a different protocol or telecommunications network at Layer 1, the path might have different delay characteristics from the original single line. It might be necessary to change the Layer 2 window size (TXWINDOW modifier) to minimize any delays introduced by switches or new protocols. In some situations, the HDLC Extended protocol might be advantageous on terrestrial links.
Multi-CPU Paths Tuning The main disadvantage of the Expand multi-CPU feature is that its advantages are available only when traffic fits a certain pattern. For example, if most traffic occurs between the same two nodes—or if these nodes are direct neighbors and traffic is sent between the same two processors in one direction—then the Expand multi-CPU feature cannot spread the load effectively.
Multi-CPU Paths Tuning Load Balancing When a multi-CPU path initially assigns paths to each pair of endpoints, the traffic pattern is usually not yet known. Load balancing is used to correct this problem as more information is gathered by moving Expand line-handler process pairs from more heavily loaded paths to more lightly loaded paths within the multi-CPU path. A slight disruption occurs in message transfer occurs when pairs are changed.
Multi-CPU Paths Tuning Superpath Load Distribution The Superpaths feature does not distribute the load equally over all paths. A superpath distributes the load based on three criteria: • • • CPU Matching Load Factor Balancing Pair Count Balancing CPU Matching This takes effect when the two systems are directly connected with a superpath; that is, they are direct neighbors.
Multi-CPU Paths Tuning Load Factor Balancing If there are no matching CPUs, then the load would be distributed based on the load factor of the paths in the superpath. If a process on \A in CPU 0 is communicating with a process on \B in CPU 2, the line handler chosen is based on the load factor of the two lines. After the CPU pair has been established the line handler is used for all communication between the two CPUs.
Multi-CPU Paths Tuning In reference to \A, \B is a neighbor and \C and \D are non-neighbors. When \A makes a connection to \C, the load is not distributed over different paths, but only one path is used for all traffic to \C. The \B records which line handler is used for \A's connection to \C to make sure that the correct path is used. This is done by setting an entry in the reverse pairing table so \B knows which line handler to send the packets from \C to \A.
Network Topology Tuning load factor to each other line handler and predict the resulting change in load factors. Choose the single move that results in the lowest predicted load factor spread, put it on the output change list, update the load factors according to the predicted changes, and check the new load factor spread value. This is continued until the load factor spread is less than 0.5 or no moves can be found that improve the load factor spread. 3. Lastly, the pair counts are balanced.
Summary of Tuning Strategies Tuning Passthrough data has a 4-to-1 priority over locally originated data. This ratio is tuned fairly well for small passthrough packets. If all nodes in a route are configured for a large variable packet size (PATHPACKETBYTES modifier) such as 4095 bytes, the intermediate nodes can send up to 16 Kbytes of passthrough traffic between packets of a locally originated message.
Measuring and Mapping an Expand Network Tuning Measuring and Mapping an Expand Network Effective network tuning must begin with an accurate picture of the network and its significant traffic. All networks are fully defined topologically by their nodes and links. Network traffic is fully defined by the intensity of the traffic, the service times of the working components, and the capacities of passive resources such as buffers and queues. These parameters can all be measured by HP utilities.
Using Measure Tuning Using Measure The Expand components reported on by Measure are called entities. After you have mapped your network and selected the nodes you want to measure, you can characterize the network traffic by measuring these entities: • • • • • SYSTEM Entity NETLINE Entity LINE Entity PROCESS Entity CPU Entity Note. The values shown in these diagrams are in units per second (the Measure SET REPORT RATE ON command was used).
Using Measure Tuning NETLINE Entity The NETLINE entity reports several values that you need when modeling traffic on a path. NETLINE reports part of the path performance associated with a particular Expand line-handler process, logical device, and ServerNet wide area network (SWAN) concentrator. The number of data bytes received is shown in Din4-Bytes and the number of bytes sent is shown in Dout4-Bytes. NETLINE also shows the distribution of message sizes in message-size ranges.
Using Measure Tuning Example 19-3. LINE Entity Display Comm Line $X25TAH Device Type 61 Subdevice Type 63 Logical Device 170 Trackid SWAN24 Clip 2 Line 1 Local System \COWBOY From 7 Feb 1997, 10:23:51 For 44.3 Seconds Requests Write-busy-Time Read-busy-Time Input-Bytes Input-Data-Bytes Transactions 6.03 1.21 % 85.52 % 946.94 770.93 Retries Writes Reads Output-Bytes Output-Data-Bytes Response-Time 11.97 12.
Using Measure Tuning Example 19-4. PROCESS Entity Display Process 3,14 ($B30S) Pri 199 Pg Size 16384 Bytes Program $SYSTEM.SYS01.LHOBJ (Native) Userid 255,255 Creatorid 255,255 Ancestor 1,275 ($ZZWAN) Local System \TAHITI From 7 Feb 1997, 11:53:36 For 3.3 Minutes Cpu-Busy-Time Mem-Qtime Page-Faults Pres-Pages-Qtime Ext-Segs-Qtime Recv-Qtime Messages-Sent Sent-Bytes Returned-Bytes MQC-Allocations MQCs-Inuse-Qtime Checkpoints File-Open-Calls UCL-Qtime Accel-Busy-Time TNSR-Busy-Time Begin-Trans 31.
Using Measure Tuning Determining Processor Use To determine the processor use of an Expand line-handler process, you must add a fraction of the Intr-Busy-Time count from the processor where the Expand line-handler process is running to the Cpu-Busy-Time value for the Expand line-handler process.
Measuring Passthrough Traffic Tuning Measuring Passthrough Traffic Although passthrough traffic is reported in the SYSTEM entity (SENT-FWD and RCVDFWD counters), Measure does not directly account for the source and destination of passthrough traffic when examining a path. An Expand line-handler process only sees the node to which it is connected. The only way to map the passthrough traffic accurately is to know the topology of your network and to measure each Expand linehandler process on each node.
Example 1: Changing Packet Size Tuning Example 19-6. SCF PATH STATS Display -------------------- LEVEL 4 MESSAGE HISTOGRAM --------------------------<= 64 .. 71027 <= 128 .. 25609 <= 256.. 4211 <= 512 .. 1676 <= 1024 .. 1466 <= 2048.. 370 <= 4096 .. 179 > 4096 .. 2288 -------------------- LEVEL 4 / LEVEL 3------------Average--------Average--Packets Forwards Links Packets/Block Bytes/Block Sent 230144 0 24888 1.0 238 Rcvd 94921 0 28559 1.0 178 L4 Packets Discarded.........
Example 1: Changing Packet Size Tuning because the number of messages and the size of the messages is the same in both cases. For messages sent, changing the packet size to 1024 bytes improves the packets-perlink ratio by about five times. Increasing the packet size to 2048 bytes could further improve efficiency on the path (but this is not possible for all line types): 1024-Byte Packets 2048-Byte Packets Messages Sent (average message size=1776 bytes) 46043/24888 = 1.85 24888/24888 = 1.
Example 2: Reducing Passthrough Traffic Tuning Figure 19-6 shows a comparison of the bandwidths used for packets of 245, 1024, and 2048 bytes. Figure 19-6. Packet Size/Bandwidth Comparison Bits per message 20000 15000 10000 5000 0 256 1024 2048 Packet Size (Bytes) VST029.vsd Example 2: Reducing Passthrough Traffic It is common for the role of a node in an Expand network to change over a period of time.
Tuning Example 2: Reducing Passthrough Traffic through to other nodes. Passthrough traffic is shown in the SENT-FWD and RCVDFWD counters. Total passthrough traffic is shown in the TOTAL FORWARD column. Notice that the source and destination of passthrough traffic cannot be identified from Measure data. Example 19-7.
Example 2: Reducing Passthrough Traffic Tuning Example 19-8. Passthrough Traffic in a Network Local System \HERE Frames % Send % Send Rcv % Rcv Remote Msgs Rcvd Frames Frames Total Pass Pass Pass Pass System Sent Sent Rcvd Rcvd Hops Thru Thru Thru Thru ---------------------------------------------------------------------------\OAHU 40856 87030 81732 9.87% 4 522180 10.14% 490392 14.37% \CANTON 39259 79444 78637 9.50% 4 476664 9.25% 471822 13.83% \SAIPAN 10438 76652 77156 9.32% 1 0 0.00% 0 0.
Tuning Example 2: Reducing Passthrough Traffic Expand Configuration and Management Manual — 529522-013 19 - 34
20 Troubleshooting To quickly and efficiently identify and resolve network problems, HP recommends that you use a standard network troubleshooting methodology.
Measure Troubleshooting information about Expand subsystem components. Table 20-1 lists the TYPE identifiers you can use to show information about Expand subsystem components and related subsystems. Table 20-1.
Identifying Network Problems Troubleshooting Identifying Network Problems There are a number of sources from which to obtain information to identify a network problem. Many of these sources are the same as those used to verify normal system operation. When a network problem occurs, usually more than one problem is reported (for example, the user might encounter a file-system error at the same time that an event message is reported).
User Complaints Troubleshooting User Complaints Most troubleshooting starts with user complaints, which can result from either application or hardware problems. The best approach is always to check the obvious first.
SCF Commands Troubleshooting Example 20-1 shows an SCF LISTDEV display produced by a LISTDEV TYPE 63 command. Example 20-1. SCF LISTDEV Display LDev Name PPID BPID Type 26 66 68 71 87 88 89 124 2,13 2,14 1,18 2,11 2,10 2,13 2,13 1,23 3,13 3,12 0,17 3,15 3,16 3,13 3,13 0,23 (63,1 ) (63,6 ) (63,0 ) (63,0 ) (63,5 ) (63,6 ) (63,6 ) (63,30) $PBAL4 $A10 $IPCOW $EX25COW $B30S $B21 $B20 $ZEXP RSize Pri Program 0 12 3 12 12 12 12 132 199 199 199 199 199 199 199 180 \TAHITI.$SYSTEM.T9057.LHOBJ \TAHITI.
SCF Commands Troubleshooting Example 20-2. SCF STATS Display 3-> stats line $b30s EXPAND Stats LINE $B30S, PPID ( 2, 10), BPID ( 3, 16) Resettime... FEB 18,1997 10:38:12 Sampletime...
SCF Commands Troubleshooting The SCF INFO PROCESS $NCP LINESET command is useful for displaying the status of a selected path and the lines in that path. The SCF INFO PROCESS $NCP, LINESET command also displays the current file-system error. Example 20-4 shows an example of an SCF INFO PROCESS $NCP, LINESET display. Example 20-4.
SCF Commands Troubleshooting Table 20-4. Common File-System Errors (page 2 of 2) Error Cause Recovery 140 This error indicates that the Expand line has been disconnected. The cause could be a problem with modem-tosystem communications or with a phone line, a cable, or an X.25 connection. Examine the physical connections and modem settings to ensure that cables are plugged into the correct line interface unit (LIU).
SCF Commands Troubleshooting Example 20-5.
Problem Check-List Summary Troubleshooting The SCF PROBE PROCESS, $NCP command is useful for displaying the intermediate nodes in a path and the typical time to each destination node. Example 20-6 shows a sample display of the SCF PROBE PROCESS, $NCP command. Example 20-6.
Resolving Specific Network Problems Troubleshooting Resolving Specific Network Problems This subsection provides checklists for solving these specific network problems: • • • • • • • $NCP Problems Expand Line-Handler Process Problems SWAN Concentrator Problems WAN Subsystem Problems Expand-Over-X.25 Problems Expand-Over-IP Problems Multi-CPU Path Problems $NCP Problems Table 20-6 lists SCF commands that are useful for diagnosing problems with $NCP. Table 20-6.
Expand Line-Handler Process Problems Troubleshooting Table 20-6. Identifying $NCP Problems With SCF Commands Command Use INFO PROCESS $NCP, SYSTEMS Displays all known systems. If no connection is established, the SYSTEMS option displays an infinite time factor and hop count. The SYSTEMS option is similar to the CONNECTS option, except that the CONNECTS option displays only the systems connected.
SWAN Concentrator Problems Troubleshooting Table 20-7. Expand Line-Handler Process Problem-Resolution Procedures (page 2 of 2) Problem Procedure Expand Layer 2 protocol You can use the SCF STATS LINE command to examine Layer 2 statistics. Figure 20-1 on page 20-3 (earlier in this section) is an example of an SCF STATS LINE command.
SWAN Concentrator Problems Troubleshooting Table 20-8. SWAN Concentrator Problem-Resolution Check List (page 2 of 2) Task Procedure Check the Ethernet paths configured for each CLIP on the SWAN concentrator. To determine the state of the Ethernet paths configured for each CLIP on a specific SWAN concentrator, use these SCF commands: STATUS STATUS STATUS STATUS STATUS STATUS PATH PATH PATH PATH PATH PATH $ZZWAN.#conc-name.1.a $ZZWAN.#conc-name.1.b $ZZWAN.#conc-name.2.a $ZZWAN.#conc-name.2.b $ZZWAN.
WAN Subsystem Problems Troubleshooting Ethernet ports to the same segment, either omit ALTTCPIP or set it to a NonStop TCP/IP process that does not exist. Both solutions will cause this EMS message: “Connected to Wrong ETHERNET PORT.” • • The SWAN concentrator’s Ethernet ports are reversed. If the ports are reversed, you will receive this EMS message: “Connected to Wrong ETHERNET PORT.” There is a firmware failure in a communications line interface processor (CLIP) before the FIRMUP procedure.
WAN Subsystem Problems Troubleshooting Table 20-9. WAN Subsystem Problem-Resolution Check List (page 2 of 2) Task Procedure Check the state of the default Subsystem Control Point (SCP) manager process ($ZNET). To determine if $ZNET is running, use this command at the TACL prompt: STATUS $ZNET Typically, there should be a permanent SCP process called $ZNET on each Integrity NonStop server that SCF uses by default.
WAN Subsystem Problems Troubleshooting Common WAN Subsystem Problems This is a list of common WAN subsystem problems: • • The SNMPCODE, KERNELCODE, or PROGRAM file is not in the correct subvolume or is not secured for “N” read access (the leftmost character in the file security string). SNMPCODE and KERNELCODE are download files for the SWAN concentrator; PROGRAM is a microcode file where the data link control (DLC) task is located.
Expand-Over-X.25 Problems Troubleshooting Expand-Over-X.25 Problems Table 20-10 provides general suggestions to help you solve problems with Expandover-X.25 lines. Table 20-10. Expand-Over-X.25 Problem-Resolution Procedures Task Procedure Check the X25AM process that controls the X.25 line to make sure that the line is operational and that the appropriate subdevice(s) are started. To verify that a subdevice is correct, use the X25AM subsystem SCF INFO SU command.
Expand-Over-IP Problems Troubleshooting Expand-Over-IP Problems You can diagnose most Expand-over-IP line-handler process problems using information provided by the Expand subsystem SCF STATUS LINE command with the DETAIL option. This command provides error information in the Detailed State and Detailed Info fields. Example 20-7 shows an SCF STATUS LINE, DETAIL command display. (The Detailed State and Detailed Info fields are shown in boldface type.) Example 20-7.
Expand-Over-IP Problems Troubleshooting Table 20-11. Detailed States (Expand-Over-IP) (page 2 of 3) Detailed State Cause/Effect Recovery DOWN The Layer 2 functions of the Expand-over-IP line-handler process are down. The operator might have brought the line down, the line was never started, or a problem occurred that prevented the line from starting. If an error has occurred, additional information will appear in the Detailed Info field.
Expand-Over-IP Problems Troubleshooting Table 20-11. Detailed States (Expand-Over-IP) (page 3 of 3) Detailed State Cause/Effect Recovery SOCKET_SPACE This is an internal state that should not persist. Try to restart the line. If this state persists, contact your HP representative. WAIT The Expand-over-IP line-handler process is waiting for another process or subsystem. For more specific error information, see the Detailed Info field.
Expand-Over-IP Problems Troubleshooting Example 20-9. SCF INFO LINE, DETAIL Command (Expand-Over-IP) -> INFO LINE $IPTAH0, DETAIL EXPAND Detailed Info LINE L2Protocol Net^Ip Framesize....... 132 *LinePriority.... 1 *DownIfBadQuality OFF *Txwindow........ 7 *Timerreconnect 0:00:30.00 *Associatedev.... $ZTC02 *IPVer IPV4 *DestIpAddr 16.107.189.66 16.107.188.54 *SrcIpAddr *V6DestIpAddr :: *V6SrcIpAddr :: $IPTAH0 (LDEV 175) TimeFactor...... -Rsize........... StartUp.........
Expand-Over-ATM Problems Troubleshooting Detailed Info Field for Expand-Over-IP Lines The Detailed Info field displays the last error message returned to the Expand-over-IP line-handler process. This field provides more information about the current detailed state. Each message returned to this field corresponds to an Event Management Service (EMS) event number generated by the Expand subsystem. Table 20-13 describes the messages that can be returned to the Detailed Info field. Table 20-13.
Expand-Over-ATM Problems Troubleshooting Detailed State Field for Expand-Over-ATM Lines Table 20-14 describes the detailed states displayed in the Detailed State field for Expand-over-ATM line-handler processes. Table 20-14. Detailed States (Expand-Over-ATM) (page 1 of 2) Detailed State Cause/Effect Recovery ACCEPT A switched virtual circuit (SVC) connection has been accepted from the remote system. This state is normal. No recovery is required.
Expand-Over-ATM Problems Troubleshooting Table 20-14. Detailed States (Expand-Over-ATM) (page 2 of 2) Detailed State Cause/Effect Recovery LISTEN The Expand-over-ATM line-handler process is waiting for switched virtual circuit (SVC) connection establishment from the remote system. This state is normal. No recovery is required.
Expand-Over-ATM Problems Troubleshooting Resolving Expand-Over-ATM Connection Problems If the SCF STATUS LINE, DETAIL command displays CONNECTING in the Detailed State field, use the SCF STATS LINE command to obtain more information about the problem. Example 20-11 shows an SCF STATS LINE command. Example 20-11. SCF STATS LINE Command (Expand-Over-ATM) -> STATS LINE $LNFIJ EXPAND Stats LINE $LNFIJ, PPID ( 2, 69), BPID ( 3, 69) Resettime... JUN 14,2000 16:06:48 Sampletime...
Expand-Over-ATM Problems Troubleshooting Resolving Expand-Over-ATM Wait Problems If the SCF STATUS LINE command with the DETAIL option displays WAIT in the Detailed State field, check the Detailed Info field for more detailed error information. Table 20-15 describes the messages that might be displayed in the Detailed Info field. Table 20-15. Messages Displayed in the Detailed Info Field (Expand-Over-ATM) Message Description Shared memory system unavailable The QIO subsystem is not available.
Multi-CPU Path Problems Troubleshooting Multi-CPU Path Problems This subsection provides multi-CPU path troubleshooting guidelines and identifies common multi-CPU path problems. Troubleshooting Check List Table 20-16 provides general suggestions to help you solve problems with multi-CPU paths. Table 20-16. Multi-CPU Path Problem Resolution Procedures Task Procedure Check that the multi-CPU path is enabled.
Reporting Network Problems Troubleshooting Common Multi-CPU Path Problems This is a list of common multi-CPU path problems: • • You received this EMS message during load balancing: “Network Requests Aborted.” This message does not indicate that a problem exists; it is generated when an Expand line-handler process pair is changed and messages that were in transit are aborted. These messages are retried by the file system.
Tracing Troubleshooting • • If the data rate is high, or if the trace is expected to run for many hours, preallocate the file space for the trace file using the File Utility Program (FUP). A 3- or 4megabyte file is generally sufficient for all but the longest or most work-intensive traces. Gather a $NCP trace even if you don’t think the problem involves $NCP. It is preferable to have too much rather than too little information. Note.
Resolving Common Network Problems Troubleshooting Resolving Common Network Problems This subsection shows you, through examples, how to solve several common network problems. These problems include: • • • • Slow Response Time Network Congestion Node Not Available • Path Down • Line(s) Down Duplicate Node Slow Response Time Slow response time is indicated when network response is worse than expected relative to normal day-to-day performance.
Slow Response Time Troubleshooting Step 2: Display routing data After you have isolated the path to the nodes causing the bottleneck, use this Expand subsystem SCF command to display the routing data of the network control process ($NCP) at one end of the slow path: INFO PROCESS $NCP, NETMAP, AT \system-name Example 20-5 on page 20-9 shows an example of an INFO PROCESS $NCP, NETMAP display.
Network Congestion Troubleshooting Network Congestion Slow response time indicate network congestion, which can be caused by these conditions: • • • • • • Too much traffic for the current network capacity. A node or nodes that are fully operational but unable to process the traffic, causing bottlenecks. Peak loading of the network, causing temporary congestion. A downed path causing rerouting of traffic to other nodes (see Path Down on page 20-34).
Node Not Available Troubleshooting If the path displays a plus sign (+), you should first attempt to resolve the outstanding request problem by issuing an Expand subsystem SCF ABORT PATH command to the identified path and then issuing an Expand subsystem SCF START PATH command to start it again. If the path constantly displays the plus sign (+), this indicates that the connection cannot be established.
Node Not Available Troubleshooting • • • NEXTSYS modifier value. A large number of Level-2 DISC (disconnect) supervisory frames usually indicates an incorrect NEXTSYS number. Interface selection (RS-232 or RS-422). The controller defines its pinouts by the proper setting of the interface. ASSOCIATEDEV modifier and the system load command files for Expand-overX.25, Expand-over-SNA, and Expand-over-IP, and Expand-over-ATM line-handler processes.
Adding Low-Speed Lines to a Multi-Line Path Troubleshooting Adding Low-Speed Lines to a Multi-Line Path Adding more low-speed lines to a multi-line path can increase the number of OOS frames that a path must reassemble. The effect in this case is not on the buffer space used but on the total time taken for the sending Expand line-handler process to receive its ACK. As a result, the sending node might experience an increase in Layer 4 timeouts.
A SCF Error Messages This appendix contains error messages returned by the SCF subsystem when you run SCF commands. For other Expand network-related errors, see the Operator Messages Manual. Expand Error 00001 EXPAND 00001 Too many object names. Object Name: object-name. Cause. You specified more than 30 object names in an SCF command. Effect. The SCF command was not executed. Recovery. Re-enter the command using fewer that 30 object names. Expand Error 00002 EXPAND 00002 Negative LH response.
Expand Error 00005 SCF Error Messages Expand Error 00005 EXPAND 00005 Object type and name mismatched. OBJNAME: object-name OBJTYPE: object-type. Cause. The subtype of an Expand line-handler process object name does not match the expected object type. For example, you might have entered a path logical device name after specifying a LINE object type in the SCF command. Effect. The SCF command was not executed. Recovery. Re-enter the command with matching object types and object names.
Expand Error 00009 SCF Error Messages Expand Error 00009 EXPAND 00009 Negative $NCP response. OBJNAME: File system err: #R##. object-name. Cause. The SCF command was rejected by the network control process ($NCP). Effect. The SCF command was not executed. Recovery. Correct the file-system error, then re-enter the command. Expand Error 00010 EXPAND 00010 INTERNAL ERR: Rcvd Bad Network trace from SYSTEM #R# to SYSTEM #R#. Cause.
Expand Error 00013 SCF Error Messages Expand Error 00013 EXPAND 00013 The SYSTEM system-number is not defined. Cause. The system number specified in the SCF command is not recognized by the network control process ($NCP). Effect. The SCF command was not executed. Recovery. Re-enter the command making sure to use the correct system number. Expand Error 00014 EXPAND 00014 All paths to the SYSTEM system-number are down. Cause. All paths to the specified system are down. Effect.
Expand Error 00017 SCF Error Messages Expand Error 00017 EXPAND 00017 Not supported for a down-version system. Cause. The SCF command was rejected by the Expand manager process ($ZEXP). The information requested cannot be obtained from an older (down-version) system. Effect. The SCF command was not executed. Recovery. No action is required. Expand Error 00018 EXPAND E00018 Configuration error or Memory allocation failure. Cause.
Expand Error 00021 SCF Error Messages Expand Error 00021 EXPAND E00021 System sysnum is not a multi-CPU path neighbor. Cause. The SCF INFO PROCESS $NCP, RPT command was rejected because there is no multi-CPU path connected to the specified system. Effect. The SCF command is not executed. Recovery. No action is required.
B Expand and WAN SCF Comparison This appendix compares the commands provided by the SCF interface to the Expand subsystem with the commands provided by the SCF interface to the WAN subsystem. For a general comparison of the two SCF interfaces, see Section 14, Subsystem Control Facility (SCF) Commands. Command Comparison Table B-1 provides a command-to-command comparison of Expand SCF and WAN SCF commands and explains which command to use to perform a specific task. Table B-1.
Command Comparison Expand and WAN SCF Comparison Table B-1. Expand and WAN SCF Command Comparison (page 2 of 6) Expand Subsystem SCF Command WAN Subsystem SCF Command Command Function ALTER ALTER Expand SCF: • • Use the ALTER LINE and ALTER PATH commands to make temporary changes to attributes and attribute values for a selected Expand line-handler process. Use the ALTER PROCESS command to make temporary changes to attributes and attribute values for the network control process ($NCP).
Command Comparison Expand and WAN SCF Comparison Table B-1. Expand and WAN SCF Command Comparison (page 3 of 6) Expand Subsystem SCF Command WAN Subsystem SCF Command Command Function INFO INFO Expand SCF: • • • • Use the INFO LINE command to display current Layer 2 attributes and attribute values for a selected Expand line-handler process. Use the INFO PATH command to display current Layer 4 attributes and attribute values for a selected Expand line-handler process.
Command Comparison Expand and WAN SCF Comparison Table B-1. Expand and WAN SCF Command Comparison (page 4 of 6) Expand Subsystem SCF Command WAN Subsystem SCF Command Command Function PRIMARY PRIMARY Expand SCF: • Use the PRIMARY PROCESS command to cause the backup processor to become the primary processor and the primary processor to become the backup processor for a selected Expand line-handler process or for the network control process ($NCP).
Command Comparison Expand and WAN SCF Comparison Table B-1. Expand and WAN SCF Command Comparison (page 5 of 6) Expand Subsystem SCF Command WAN Subsystem SCF Command Command Function STATUS STATUS Expand SCF: • • • Use the STATUS LINE command to display the dynamic state, primary process ID (PPID), backup process ID (BPID), and other information about a selected Expand line.
Command Comparison Expand and WAN SCF Comparison Table B-1. Expand and WAN SCF Command Comparison (page 6 of 6) Expand Subsystem SCF Command WAN Subsystem SCF Command Command Function VERSION VERSION Expand SCF: • Use the VERSION PROCESS command to display the version level of the Expand manager process ($ZEXP), the network control process ($NCP), or a selected Expand line-handler process. WAN SCF: • Use the VERSION SUBSYS command to display the version level of the WAN manager process ($ZZWAN).
ALTER Command Comparison Expand and WAN SCF Comparison ALTER Command Comparison You can use the SCF interface to the WAN subsystem to permanently change the value of any Expand modifier used by an Expand line-handler process or the network control process ($NCP). Expand modifiers are described in Section 16, Expand Modifiers. Modifier-to-Attribute Comparison Most—but not all—Expand modifiers have corresponding attribute names in Expand SCF.
Expand and WAN SCF Comparison Altering Timeout Periods Altering Timeout Periods Certain Expand SCF attributes are used to set a timeout period (for example, the OSTIMEOUT attribute specifies the Expand out-of-sequence packet timeout period). These Expand SCF attributes accept different units of time than the Expand modifiers with which they correspond.
Glossary active connect request. The default connect request method used by an Expand linehandler process when it tries to establish an end-to-end connection. When an Expandover-NAM line-handler process issues an active connect request, the network access method (NAM) process tries to initiate a connection. When an Expand-over-IP or Expand-over-ATM line-handler process issues an active connect request, it sends a Connect Command frame to the remote Expand-over-IP or Expand-over-ATM linehandler process.
congestion control Glossary congestion control. A feature that allows you to control system resources to avoid network bottleneck and resource contention situations. You can enable or disable congestion control using the Expand subsystem SCF ALTER PATH command or the WAN subsystem SCF ALTER DEVICE command. control block pool. A portion of the Expand line-handler process data space that contains control blocks. A control block is allocated for each node in the network. direct-connect line-handler process.
Glossary Expand line-handler process pair shared memory of the QIO subsystem. See also network access method (NAM) and NETNAM protocol. Expand line-handler process pair. The Expand line-handler processes at the source and destination node on a multi-CPU path. Expand line-handler processes at each source and destination node on a multi-CPU path are paired to guarantee message order; all messages between that source and destination node are sent through this Expand line-handler process pair.
Expand packet Glossary Expand packet. See Expand frame. Expand priority. The priority of an Expand message. The Expand priority is based on the priority level of the application process that created the message, unless the SETMODE 71 procedure is used. frame. See Expand frame. global variables space. A portion of the Expand line-handler process data space that contains Expand software global variables.
Layer 3 Glossary corresponds to the LINE object referred to by the Expand Subsystem Control Facility (SCF) interface. Layer 3. A term that is used to refer to the Network Layer of the Open Systems Interconnection (OSI) Reference Model. Layer 3 governs the switching and routing of information between systems in the network and is responsible for error checking and recovery.
load factor Glossary using the SCF ALTER PROCESS command. See also rebalancing algorithm and Expand line-handler process pair. load factor. The ratio between a path’s effective time factor (ETF) and its base time factor (TF). See also effective time factor (ETF). local system. A term used to refer to the system to which your terminal is directly connected. logical device name. The name assigned to an input-output process (IOP) during its configuration. logical device number.
multipacket frame Glossary systems. The Expand subsystem will simultaneously transmit data over all the lines in the path, increasing overall bandwidth. The Expand subsystem also automatically reroutes data over remaining lines if one or more lines fail. See also line, path, and route. Contrast single-line path. multipacket frame. A data structure that contains multiple Expand packets. The multipacket frame feature is enabled using the PATHBLOCKBYTES modifier.
network routing table (NRT) Glossary network routing table (NRT). A table that resides in each processor in each system in the network. The NRT associates each destination system with the logical device (LDEV) number of the best-path route Expand line-handler process to use to send messages to that system. See also best-path route and network control process (NCP). network topology. The pattern of interconnection of systems in a network.
packet Glossary packet. A block of information that contains fields for addressing, sequencing of information, priority indicators, and a portion of a message or an entire message. See also Expand frame. packet header. The portion of an Expand frame that contains control information added by the Expand line-handler process. By default, D20 and later Expand frames use an extended packet header format of 64 bytes. passive connect request.
profile modifier Glossary WAN subsystem (ADD DEVICE and ALTER DEVICE commands). Profiles are provided on NonStop NS-series servers only. profile modifier. A configuration modifier in a profile. See also profile. PU. See physical unit (PU). PVC. See persistence. QIO. A mechanism for transferring data between processes through a shared memory segment. The QIO subsystem is preconfigured and started during the system load sequence. QIOMON. The QIO Monitor process.
ServerNet adapter Glossary ServerNet adapter. A component that connects peripheral devices to the rest of the system through a ServerNet bus interface (SBI). ServerNet cluster. ServerNet clusters enable multiple NonStop NS-series servers to work together and appear to client applications as one large processing entity. ServerNet clusters extend the ServerNet X and Y fabrics outside the system boundary and allow the ServerNet protocol to be used for intersystem messaging. ServerNet cluster monitor process.
$ZPM Glossary $ZPM. The process name of the persistence manager process. $ZZKRN. The process name of the Kernel subsystem manager process. $ZZLAN. The process name of the ServerNet LAN systems access (SLSA) subsystem manager process. $ZZSCL. The process name of the ServerNet monitor process. $ZZTCP. The management process for the NonStop TCP/IPv6 subsystem. $ZZWAN. The process name of the wide area network (WAN) subsystem manager process.
Index A ABORT command 14-8/14-9 ABORT LINE command 18-27 ABORT PATH command 18-27 ABORTTIMER attribute ALTER PROCESS $NCP command and 14-21 INFO PROCESS $NCP command and 14-54 ABORTTIMER modifier 6-4, 17-28 ACK 17-15 ACTIVATE command 14-9 ACTIVATE PROCESS $NCP 18-28 Active connect request 17-51, 17-54, 17-60 ADD DEVICE command 18-20 ADDRESS attribute, INFO LINE command and 14-34 AFTERMAXRETRIES attribute ALTER LINE command and 14-14 INFO LINE command and 14-37, 14-39, 14-44, 14-48 AFTERMAXRETRIES_DOWN modif
B Index B BCC Errors, STATS LINE command and 14-94 Best-path routing 2-7, 17-24, 20-33 Bind requests 17-51 Bottlenecks, avoiding 17-69 Buffer errors, STATS LINE command and 14-94 Buffer pool description of 17-47 EXTMEMSIZE 17-48 inadequate allocation of 20-12 insufficient space in 17-20 Buffers 17-47 Bulk transfers 19-5 Bus topology 3-14 C Calculating a path time factor, formula 17-22 CALLTYPE_ATMSAP modifier 16-5 CALLTYPE_PVC modifier 16-5 CALLTYPE_SVC modifier 16-5 Cancel request packet 17-15 CIP selec
D Index Connection establishment Expand-over-ATM 17-59 Expand-over-FOX 17-50 Expand-over-IP 17-54 Expand-over-NAM 17-50 Connection requests active 17-51, 17-54, 17-60 packets 17-13 passive 17-52, 17-55, 17-60 Connection reset packets 17-14 Connection response packets 17-13 CONNECTS option 14-50, 14-57 CONNECTTIME attribute ALTER PROCESS $NCP command and 14-21 INFO PROCESS $NCP command and 14-54 CONNECTTIME modifier 6-5 CONNECTTYPE attribute ALTER LINE command 14-14 INFO LINE command and 14-49 CONNECTTYPE_
E Index DOWNIFBADQUALITY modifier 16-9 Driver problems 20-35 DSRTIMEOUT attribute, INFO LINE command and 14-35 DSRTIMER attribute ALTER LINE command and 14-16 INFO LINE command and 14-34 DV messages 17-27 E Effective time factor (ETF), displaying 18-14, 20-12 End-to-End protocol description of 17-13 resolving problems with 20-12 ENQ 17-15 Error Frames, STATS LINE command and 14-94 Error messages A-1/A-6 Errors BCC 20-32, 20-35 FCS 20-32, 20-35 file-system 20-7 ETF, displaying 18-14, 20-12 Ethernet 17-65,
F Index Expand-over-X.25 line-handler process configuring 10-1/10-16 features of 3-2, 17-4 Expand-over-X.
K Index INFO PROFILE command 18-15 INFO SU command 20-18 Information frames (I-frames) 20-32 Information frames, STATS LINE command and 14-92 Interactive network access 2-1 INTERFACE attribute ALTER LINE command and 14-14 INFO LINE command and 14-34 INTERFACE_RS232 modifier 16-10 INTERFACE_RS422 modifier 16-10 Internet Protocol (IP) 17-53 IP network routes, redundancy in 8-4 IP networks 3-4 IPADDRESS attribute 20-17 IPv4 addresses 8-24 display format 14-37 mode 8-14 IPv6 addresses 8-24 display format 14-3
M Index LABEL command 15-9 Latency 19-4, 19-6 Layer 1, Expand functions at 17-11 Layer 2 displaying frames at 14-92 Expand functions at 17-11 statistics, analyzing 20-32 windowing, effect on performance of 19-10 Layer 3, Expand functions at 17-10 Layer 4 Expand functions at 17-10 retries at 17-15 send window 17-21 statistics, analyzing 20-32 STATS PATH command and 14-77, 14-83 timeout for 17-15 Layer 5, Expand functions at 17-10 LCAN 17-15 LCMP 17-14, 17-44 Leased lines advantages and disadvantages of 2-5
M Index MAXRECONNECTS attribute ALTER LINE command and 14-14 INFO LINE command and 14-36, 14-39, 14-44, 14-48 MAXRECONNECTS modifier 16-16/16-17, 17-52 MAXTIMEOUTS attribute ALTER PROCESS $NCP command and 14-21 INFO PROCESS $NCP command and 14-53/14-55 MAXTIMEOUTS modifier 6-6 Measure CPU entity of 19-26 features of 2-9, 20-10 LINE entity of 19-24 monitoring performance with 20-2 NETLINE entity of 19-24 PROCESS entity of 19-25 setting measurement intervals for 19-28 SYSTEM entity of 19-23 tuning the netwo
N Index displaying paths in 14-51, 18-14 displaying rebalancing time for 14-56 displaying reverse pairing table (RPT) for 14-66 displaying status of 14-102 extended packet format and 16-26 guarantee message order 17-31 initiating an immediate rebalance of 14-9 load balancing for 17-72 parallel connections 8-4 performance tuning for 19-14 rebalancing 18-28, 19-16 resolving problems with 20-28 tuning 19-14 Multi-CPU rebalance, temporary disruption in network 17-33 Multi-line paths benefits and disadvantages
O Index Network-related TACL commands REMOTEPASSWORD 18-8 SYSTEM 18-3, 18-6 WHO 18-4 NEXT command 15-9 NEXTSYS attribute ALTER PATH command and 14-11 INFO PATH command and 14-25/14-26 NEXTSYS modifier 16-18, 20-18, 20-35 NODE ACK 17-14 node name character limitation 18-2 definition 18-2 NODE STAT 17-14 Node status acknowledgment 17-14 packets 17-14 NonStop TCP/IP and the line-handler process 17-5 architecture and relationship to Expand 8-2 overview 17-53 selecting as environment 1-10, 1-11 troubleshooting
P Index Packet-switched data networks 2-5, 3-2 Pair count balancing 17-32, 19-18/19-19 partially qualified file name 18-2 Passive connect requests 17-52, 17-55, 17-60 Passthrough traffic effect on performance of 19-20 handling of 17-41, 17-45 measuring 19-28, 19-31 reducing 19-31 routing 2-7 Passwords global 18-10 remote 2-11, 18-8/18-9 Path change status packet 17-15 Path change status response packet 17-15 Path logical device 13-1, 17-2 PATHBLOCKBYTES attribute ALTER PATH command and 14-11 INFO PATH com
Q Index Pool failures 20-12 PORT modifier 20-18 Port numbers 8-17/8-18, 8-20, 17-54 PRIMARY PROCESS command 14-70, 18-28 Prioritization, message 17-40 Priority routing 2-8, 17-40 PROBE PROCESS command 20-5 PROBE PROCESS $NCP command 14-71/14-73, 18-13, 20-10, 20-12, 20-31 Processes accessing remote 18-9 location of 19-11 Processor overhead 19-13 Processor type, effect on performance of 19-11 Profiles changing 18-21 creating 5-3 displaying modifiers in 18-15 line logical device 13-5 path logical device 13-
S Index Remote passwords 2-11, 17-44, 18-8 Remote processes 18-9 Remote programs, running 18-6 REMOTEPASSWORD command 2-11, 18-8, 18-10 Reply packets 17-44 Request packets 17-44 Resource use 19-1 Response time, slow 20-31, 20-33 Retries, Layer 4 14-25, 17-15 RETRYPROBE attribute ALTER LINE command and 14-14, 14-16 description of 17-52 INFO LINE command and 14-40, 14-44, 14-49 RETRYPROBE modifier 16-21 Reverse pairing table (RPT) description of 17-25 displaying 14-66 Route, definition of 17-27 Routing dete
S Index SNAX/APN line-handler process Layer 2 functions of 17-49 SNAX/APN process 11-3, 17-4 SNMPCODE file 20-17 SPEED attribute ALTER LINE command and 14-15 INFO LINE command and 14-33, 14-38, 14-43, 14-47 SPEED modifier 16-23, 17-23 SPEEDK attribute ALTER LINE command and 14-15 INFO LINE command and 14-32, 14-38, 14-42, 14-47 SPEEDK modifier 16-23, 17-23 Split-star topology 3-13 SPRINTNET 3-2 SRCIPADDR attribute ALTER LINE command and 14-15 INFO LINE command and 14-41 SRCIPADDR modifier 16-25 SRCIPPORT
T Index Super ID user 18-11 SUPERPATH attribute ALTER PATH command and 14-11 INFO PATH command and 14-28 STATUS PATH command and 14-102 SUPERPATH option 14-67 Superpath rebalance 14-68, 19-19 Superpaths feature 19-17 SUPERPATH_OFF modifier 16-25 SUPERPATH_ON modifier 7-12, 10-13, 11-15, 16-25 Supervisory frames, STATS LINE command and 14-92 SVC connections 9-1, 17-59 SVCs 9-5, 17-58 SWAN concentrator 7-3/7-4, 10-3/10-4, 11-4 SWAN concentrator, resolving problems with 20-13/20-15 Switched virtual circuits
U Index description of 17-52 INFO LINE command and 14-40, 14-44, 14-49 TIMERINACTIVITY modifier 16-26 TIMERPROBE attribute ALTER LINE command and 14-15, 14-17 description of 17-52 INFO LINE command and 14-40, 14-44, 14-49 TIMERPROBE modifier 16-26 TIMERRECONNECT attribute ALTER LINE command and 14-15, 14-18 configuring 17-51/17-52 INFO LINE command and 14-40, 14-44, 14-49 TIMERRECONNECT modifier 16-27 Topology, effect on performance of 19-20 TRACE command 14-112/14-117 TRACE LINE command 18-19 TRACE PATH
W Index Volume name 18-2 W WAN shared driver 7-3, 11-3 WAN subsystem description of 5-4 manager process 20-15 resolving problems with 20-15/20-17 WANBoot processes 20-16 WHO command 18-4 Window size 19-14 X X25AM line-handler process, layer 2 functions of 17-49 X25AM process 10-3, 17-4, 20-18 X.25 Access Method (X25AM) 2-5 X.
Special Characters Index Expand Configuration and Management Manual — 529522-013 Index - 18
