WAN Subsystem Configuration and Management Manual

ManualsBrandsHP ManualsServerHP NonStop G-Series

WAN Subsystem

Configuration and

Management Manual

Abstract

This manual describes how to monitor, modify, and control the wide area network

(WAN) subsystem and configure a ServerNet wide area network (SWAN and SWAN 2)

concentrator on an HP Integrity Nonstop™ NS-series or HP NonStop S-series server.

This manual includes the Subsystem Control Facility (SCF) commands used with the

WAN subsystem and is written for anyone who configures, manages, or maintains this

subsystem and a SWAN concentrator.

Product Version

G06 and H01

Supported Release Version Updates (RVUs)

This manual supports G06.24 and all subsequent G-series RVUs and H06.03 and all

subsequent H-series RVUs until otherwise indicated in a new edition.

Part Number Published

522463-011 November 2006

Summary of content (288 pages)

PAGE 1
WAN Subsystem Configuration and Management Manual Abstract This manual describes how to monitor, modify, and control the wide area network (WAN) subsystem and configure a ServerNet wide area network (SWAN and SWAN 2) concentrator on an HP Integrity Nonstop™ NS-series or HP NonStop S-series server. This manual includes the Subsystem Control Facility (SCF) commands used with the WAN subsystem and is written for anyone who configures, manages, or maintains this subsystem and a SWAN concentrator.
PAGE 2
Document History Part Number Product Version Published 522463-007 F40 September 2004 522463-008 F40 December 2004 522463-009 F40 July 2005 522463-010 G06 and H01 April 2006 522463-011 G06 and H01 November 2006
PAGE 3
WAN Subsystem Configuration and Management Manual Index Examples What’s New in This Manual xi Manual Information xi New and Changed Information Figures Tables xi About This Manual xvii Who Should Use This Manual xvii How This Manual Is Organized xvii Related Manuals xviii Installing the SWAN Concentrator xviii Notation Conventions xx Abbreviations xxv 1. Configuration Quick Start Initial WAN Subsystem Configuration 1-1 Configuration File Contents 1-1 HP Manufacturing Naming Conventions (G06.
PAGE 4
2. Overview of the WAN Subsystem Contents Installing the SWAN Concentrator 1-25 Displaying the Configured Configuration Track-ID 1-26 Changing the Initial WAN Subsystem Configuration 1-27 2.
PAGE 5
3. Changing the Initial WAN Subsystem Configuration Contents Difference Between the SWAN and the SWAN 2 Concentrator 2-30 3.
PAGE 6
5. Managing the WAN Subsystem Contents 5.
PAGE 7
6.
PAGE 8
7.
PAGE 9
Examples Contents Example 1-3. Example 1-4. Example 1-5. Example 1-6. Example 1-7. Example 1-8. Example 1-9. Example 2-1. Example 3-1. Example 3-2. Example 3-3. Example 3-4. Example 3-5. Example 3-6. Example 3-7. Example 3-8. Example 3-9. Example 3-10. Example 3-11. Example 3-12. Example 3-13. Example 3-14. Example 3-15. Example 3-16. Example 3-17. Example 3-18. Example 3-19. Example 3-20. Example 4-1. Example 4-2. Example 4-3. Example 4-4. Example 4-5. Example 4-6. Example 4-7. Example 4-8. Example 4-9.
PAGE 10
Figures Contents Example 4-11. Example 4-12. Example 4-13. Example 4-14. Example 4-15. Example 4-16. Example 6-1. Example 6-2. Example 6-3. Example B-1.
PAGE 11
Contents Table 2-3. Table 2-4. Table 2-5. Table 2-6. Table 2-7. Table 2-8. Table 2-9. Table 2-10. Table 2-11. Table 2-12. Table 2-13. Table 2-14. Table 3-1. Table 3-2. Table 4-1. Table 4-2. Table 5-1. Table 5-2. Table 5-3. Table 5-4. Table 5-5. Table 5-6. Table 6-1. Table 6-2. Table 6-3. Table 6-4. Table 6-5. Table 6-6. Table 6-7.
PAGE 12
Contents WAN Subsystem Configuration and Management Manual—522463-011 x
PAGE 13
What’s New in This Manual Manual Information WAN Subsystem Configuration and Management Manual Abstract This manual describes how to monitor, modify, and control the wide area network (WAN) subsystem and configure a ServerNet wide area network (SWAN and SWAN 2) concentrator on an HP Integrity Nonstop™ NS-series or HP NonStop S-series server.
PAGE 14
What’s New in This Manual • • • • • • • • New and Changed Information for Previous Editions Changes have been made to Integrity NonStop NS-Series Server Connection on page 2-25. Changes have been made to Reconfiguring an Ethernet Port on page 3-6. Changes have been made to Planning for LAN Communications on page 4-2. Changes have been made to Step 1: Selecting E4SAs, FESAs, GESAs, or G4SAs on page 4-4. Number of LAN Adapters Supported By Enclosure Type on page 4-4.
PAGE 15
What’s New in This Manual • • • • • • • • • • • • • New and Changed Information for Previous Editions HP Manufacturing Naming Conventions (G06.26 and Earlier RVUs) on page 1-3 G4SA Naming Conventions (G06.24, G06.25, and G06.26 RVUs) on page 1-5 HP Manufacturing Naming Conventions (G06.27 and Later RVUs and H06.
PAGE 16
What’s New in This Manual • New and Changed Information for Previous Editions Ethernet Port Reconfiguration Example on page 3-7 Section 4: Adding a SWAN Concentrator • • • • • • • • • • • • • • • • • • • Overview of the Configuration Procedure on page 4-1 Planning for LAN Communications on page 4-2 Number of LAN Adapters Supported By Enclosure Type on page 4-4 Displaying the Configured Adapters on page 4-4 Displaying the Configured LIFs on page 4-5 Connecting the SWAN Concentrator Through an Ethernet
PAGE 17
What’s New in This Manual • • • • • • • • • • • • • • • New and Changed Information for Previous Editions process-name on page 6-39 process-name on page 6-40 process-name on page 6-42 INFO ADAPTER Command on page 6-55 INFO PATH Command on page 6-62 START ADAPTER Command on page 6-85 START PATH Command on page 6-89 START SERVER Command on page 6-91 START TASK Command on page 6-92 STATUS PATH Command on page 6-99 STATUS SERVER Command on page 6-102 STATUS TASK Command on page 6-106 STOP ADAPTER Command on
PAGE 18
What’s New in This Manual New and Changed Information for Previous Editions WAN Subsystem Configuration and Management Manual—522463-011 xvi
PAGE 19
About This Manual Note. Throughout this manual when a distinction between a SWAN concentrator (T3880) and a SWAN 2 concentrator (T3881) is not required, SWAN concentrator is used as a collective term.
PAGE 20
Related Manuals About This Manual Table i. Contents (page 2 of 2) Title 7 Upgrading to a SWAN 2 Concentrator Contents Describes considerations when upgrading to a SWAN 2 concentrator. A SCF Messages Describes error messages for the WAN subsystem. B Sample Router Configuration Shows a sample router configuration connecting a Cisco router to a SWAN concentrator. Related Manuals Manuals describing Integrity NonStop NS-series or NonStop S-series servers are organized into several sets of manuals.
PAGE 21
Updating the SWAN Concentrator Firmware About This Manual Updating the SWAN Concentrator Firmware The G06.nn Software Installation and Upgrade Guide and H06.nn Software Installation and Upgrade Guide cover RVU-specific information about updating SWAN firmware. WAN Wizard Pro WAN Wizard Pro is a graphical user interface (GUI) that guides you step-by-step through the configuration process of one or more SWAN concentrators.
PAGE 22
Understanding Event Messages About This Manual Understanding Event Messages The event messages generated by the WAN subsystem and the SWAN concentrators are described in the WANMGR and TRAPMUX sections of the Operator Messages 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.
PAGE 23
General Syntax Notation About This Manual each side of the list, or horizontally, enclosed in a pair of brackets and separated by vertical lines. For example: FC [ num ] [ -num ] [ text ] K [ X | D ] address { } 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.
PAGE 24
Notation for Messages About This Manual Line Spacing. If the syntax of a command is too long to fit on a single line, each continuation line is indented three spaces and is separated from the preceding line by 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 ]… !i and !o.
PAGE 25
Notation for Management Programming Interfaces About This Manual lowercase italic letters. Lowercase italic letters indicate variable items whose values are displayed or returned. For example: p-register process-name [ ] Brackets. Brackets enclose items that are sometimes, but not always, displayed.
PAGE 26
Notation for Subnet About This Manual UPPERCASE LETTERS. Uppercase letters indicate names from definition files. Type these names exactly as shown. For example: ZCOM-TKN-SUBJ-SERV lowercase letters. Words in lowercase letters are words that are part of the notation, including Data Definition Language (DDL) keywords. For example: token-type !r. The !r notation following a token or field name indicates that the token or field is required. For example: ZCOM-TKN-OBJNAME !o. token-type ZSPI-TYP-STRING.
PAGE 27
Abbreviations About This Manual Abbreviations ATM. Asynchronous Transfer Mode ATM3SA. ATM 3 ServerNet Adapter CCSA. Common Communication ServerNet Adapter CRU. Customer Replaceable Unit DIH. Driver Interrupt Handler DSM. Distributed Systems Management E4SA. Ethernet 4 ServerNet Adapter EMS. Event Management Service FCSA. Fibre-Channel ServerNet Adapter FESA. Fast Ethernet ServerNet Adapter GESA. Gigabit Ethernet ServerNet Adapter G4SA. Gigabit Ethernet 4-Port ServerNet Adapter IOAM.
PAGE 28
Abbreviations About This Manual POST. Power-on Self-test PVC. Permanent Virtual Circuit QIO. Queued Input/Output SAC. ServerNet Addressable Controller SAN. System Area Network SCF. Subsystem Control Facility SCP. Subsystem Control Point SEB. ServerNet Expansion Board SMB. Serial Maintenance Bus SLSA. ServerNet LAN Systems Access SP. Service Processor TCP/IP. Transmission Control Protocol/Internet Protocol TRSA. Token Ring ServerNet Adapter SWAN. ServerNet Wide Area Network VCC.
PAGE 29
1 Configuration Quick Start Note. Throughout this manual when a distinction between a SWAN concentrator (T3880) and a SWAN 2 concentrator (T3881) is not required, SWAN concentrator is used as a collective term. This section describes your initial WAN subsystem configuration and how to verify that all required WAN subsystem processes and objects are configured and started.
PAGE 30
Configuration Quick Start Configuration File Contents Contents of the SCF0000 File The SCF0000 file contains Subsystem Control Facility (SCF) commands that configure these WAN subsystem processes and objects: • • • • • • • WAN manager process ($ZZWAN) Concentrator manager (ConMgr) processes Trivial File Transfer Protocol (TFTP) server processes WANBoot processes Simple Network Management Protocol (SNMP) agent processes SNMP trap multiplexer processes ADAPTER, SERVER, PATH, DEVICE, and PROFILE objects T
PAGE 31
HP Manufacturing Naming Conventions (G06.26 and Earlier RVUs) Configuration Quick Start HP Manufacturing Naming Conventions (G06.26 and Earlier RVUs) HP manufacturing uses a naming convention for processes and devices that relates logical names to the physical location of devices. The WAN manager process automatically configures the WANBoot, TFTP server, and the SNMP trap multiplexer processes. Note. The SNMP trap multiplexer does not require a corresponding SNMP agent process.
PAGE 32
HP Manufacturing Naming Conventions (G06.26 and Earlier RVUs) Configuration Quick Start cabid is the two-digit number that identifies the enclosure. cabid Description Range of Values 0n The object is in processor enclosure n. 01-08 n1 The object is in I/O enclosure 1 attached to processor enclosure n. 11, 21, 31, 41, 51, 61, 71, or 81 n2 The object is in I/O enclosure 2 attached to processor enclosure n.
PAGE 33
G4SA Naming Conventions (G06.24, G06.25, and G06.26 RVUs) Configuration Quick Start G4SA Naming Conventions (G06.24, G06.25, and G06.26 RVUs) Table 1-2. Naming Conventions for G06.24, G06.25, and G06.26 RVUs Process or Device Type Convention Example LIF object Lcabid-module-portid $ZZLAN.L112A G4SA ADAPTER object Ggroup-module-slot $ZZLAN.G1123 A G4SA must be installed in an I/O adapter module (IOAM) enclosure. PMF Ethernet adapter $ZZLAN.MIOEprocessorid $ZZLAN.
PAGE 34
G4SA Naming Conventions (G06.24, G06.25, and G06.26 RVUs) Configuration Quick Start cabid is the group number of the IOAM that contains the G4SA. group Description Range of Values 1n The object is in I/O enclosure n. The I/O enclosure can be physically attached to as many as four processors in the inner tetrahedron, but will always have the processor enclosure number 1. 11,12,13,14,15 module identifies whether the G4SA is installed in module 2 or 3 of an IOAM. A module is either 2 or 3.
PAGE 35
HP Manufacturing Naming Conventions (G06.27 and Later RVUs and H06.03 and Later RVUs) Configuration Quick Start HP Manufacturing Naming Conventions (G06.27 and Later RVUs and H06.03 and Later RVUs) HP manufacturing uses a naming convention for processes and devices that relates logical names to the physical location of devices. The WAN manager process automatically configures the WANBoot, TFTP server, and the SNMP trap multiplexer processes. Note.
PAGE 36
Configuration Quick Start HP Manufacturing Naming Conventions (G06.27 and Later RVUs and H06.03 and Later RVUs) module See the LAN Configuration and Management Manual for a definition of module. slot See the LAN Configuration and Management Manual for a definition of slot. pif See the LAN Configuration and Management Manual for a definition of pif. number is the identifier for the first TCP/IP, TELSERV, or LISTNER process that is automatically configured for a corresponding LIF.
PAGE 37
Determining the Initial Configuration of a SWAN Concentrator Configuration Quick Start Determining the Initial Configuration of a SWAN Concentrator HP manufacturing configures all SWAN concentrators ordered with a NonStop server. An example of a SWAN concentrator configuration is shown in the following illustration. Processor 0 Processor 1 WAN Manager Process (Primary) $ZZWANP $ZZWAN.#0 $ZZWANB WAN Manager Process (Backup) $ZZWAN.
PAGE 38
Determining the Initial Configuration of a SWAN Concentrator Configuration Quick Start You can use the SCF commands described in the following subsections to determine how your SWAN concentrator is configured. As an alternative to using multiple Subsystem Control Facility (SCF) commands, you can also use the WAN Wizard Pro GUI, which guides you step-by-step through the configuration process (see WAN Wizard Pro on page xix).
PAGE 39
Determining the Initial Configuration of a SWAN Concentrator Configuration Quick Start Displaying SWAN Concentrator Configuration Information Use the SCF INFO ADAPTER command, the OSM Service Connection, or the TSM Service Application (G-series RVUs only) to display configuration information about each configured SWAN concentrator on your system. For more information on using OSM or TSM, see the online help within each application. The SCF command syntax is as follows: INFO ADAPTER $ZZWAN.
PAGE 40
Configuration Quick Start Determining the Initial Configuration of a SWAN Concentrator The information you need to know includes: TrackId is the configuration track-ID configured for this SWAN concentrator. TCP/IP Name is the name of the preferred TCP/IP process that supports this SWAN concentrator. ALTTCPIP Name is the name of the alternate TCP/IP process that supports this SWAN concentrator. Concentrator Type is the type of concentrator. The types supported are SYNC, SWAN2, and FWCTL. Note.
PAGE 41
Determining the Initial Configuration of a SWAN Concentrator Configuration Quick Start GATEWAYIP Addr is the gateway IP address assigned to the SWAN-side router IP address for Path A. A gateway IP address of 0 (0.0.0.0) indicates that the SWAN concentrator is on the same network as the host. ALTGATEWAYIP Address is the gateway IP address assigned to the alternate SWAN-side router IP address for Path B. A gateway IP address of 0 (0.0.0.
PAGE 42
Configuration Quick Start Determining the Initial Configuration of a SWAN Concentrator snmp-trap-multiplexer is the name of an SNMP trap multiplexer process configured on your system. To determine the name of the SNMP trap multiplexer processes configured on your system, use the SCF NAMES PROCESS command as shown in Example 1-4 on page 1-13. Example 1-5 shows an SCF INFO PROCESS command display for an SNMP trap multiplexer process named $ZZWAN.#ZTXAG. Example 1-5.
PAGE 43
Determining the Initial Configuration of a SWAN Concentrator Configuration Quick Start Example 1-6. Sample SCF INFO SUBNET Command Display 17-> info subnet $ztc.* TCP/IP Info SUBNET \TEST.$ZTC0.* Name Devicename #LOOP0 #SN1 \TEST1.$NOIOP \TEST.L11123A *IPADDRESS 127.0.0.1 172.16.45.16 TYPE *SUBNETMASK SuName LOOP-BACK %HFF000000 ETHERNET %HFFFFFF00 QIO *R OFF ON N N 17-> info subnet $ztc1.* TCP/IP Info SUBNET \TEST.$ZTC1.* Name Devicename #LOOP0 #SN1 \TEST1.$NOIOP \TEST.
PAGE 44
Determining the Initial Configuration of a SWAN Concentrator Configuration Quick Start Example 1-7 shows SCF INFO LIF commands that display information for LIFs L11123A and L11123B. Example 1-7. Sample SCF INFO LIF Command Display info lif $zzlan.L11123A SLSA Info LIF Name $ZZLAN.L11123A PIF G11123.0.A MAC Address 08:00:8E:00:97:B0 Type Ethernet info lif $zzlan.L1103B Name $ZZLAN.L11123B PIF G11123.0.B MAC Address 08:00.8E.00.7B.
PAGE 45
Determining the Initial Configuration of a SWAN Concentrator Configuration Quick Start Example 1-8 shows an SCF INFO PATH command display for a SWAN concentrator named $ZZWAN.#S01: Example 1-8. Sample SCF INFO PATH Command Display info path $zzwan.#S01.* WAN MANAGER Detailed Info Path \MYSYS.$ZZWAN.#S01.1.A *IPADDRESS ....... 172.016.035.024 WAN MANAGER Detailed Info Path \MYSYS.$ZZWAN.#S01.1.B *IPADDRESS ....... 172.016.045.024 WAN MANAGER Detailed Info Path \MYSYS.$ZZWAN.#S01.2.A *IPADDRESS ....... 172.
PAGE 46
Configuration Quick Start Verifying the Initial WAN Subsystem Configuration Verifying the Initial WAN Subsystem Configuration After you have determined your initial SWAN concentration configuration, verify that the required processes and objects are configured and started. Note. The WAN manager process automatically configures and starts the WANBoot, TFTP, and the SNMP trap multiplexer processes. The following subsections describe how to use the SCF commands to check the state of each process.
PAGE 47
Configuration Quick Start Checking the State of the TCP/IP Processes Checking the State of the TCP/IP Processes Use the SCF STATUS PROCESS command to determine the state of each preconfigured TCP/IP process. The command syntax for G06.26 and earlier RVUs is: STATUS PROCESS $ZBnnn.* nnn is the last three characters of the TCP/IP process name. How to determine the names of the preconfigured TCP/IP processes is described in Displaying SWAN Concentrator Configuration Information on page 1-11.
PAGE 48
Configuration Quick Start Checking the State of the WAN Subsystem Objects Checking the State of the Routes Use the SCF STATUS ROUTE command to determine the state of each preconfigured route. The command syntax for G06.26 and earlier RVUs is: STATUS ROUTE $ZBnnn.#R* nnn is the last three characters of the TCP/IP process name for which the route is configured. The command syntax for G06.27 and later RVUs and H06.03 and later RVUs is: STATUS ROUTE $ZTCnn.
PAGE 49
Configuration Quick Start Troubleshooting Tips returned by the WAN subsystem and SWAN concentrators are described in the WANMGR and TRAPMUX sections of the Operator Messages Manual. • Attempt to start the process or object by using the commands described in this subsection, or execute the STARTCOM file by entering this command at the TACL prompt: TACL /IN $SYSTEM.ZSYSCONF.STARTCOM, NAME / The STARTCOM file invokes the STARTSCF file.
PAGE 50
Configuration Quick Start Starting the WAN Manager Process Starting the WAN Manager Process If the WAN manager process is not in the STARTED state, try to start it by using this SCF command: START PROCESS $ZZKRN.#ZZWAN The priority of the WAN manager process should stay fairly constant over a period of time.
PAGE 51
Configuration Quick Start Starting a Route The command syntax for G06.27 and later RVUs and H06.03 and later RVUs is: START SUBNET $ZTCnn.#subnet nn is the last three characters of the TCP/IP process name for which the SUBNET is configured. subnet is the name of the SUBNET you want to start. Starting a Route If a TCP/IP route is not in the STARTED state, use the SCF START ROUTE command to start it. The command syntax for G06.26 and earlier RVUs is: START ROUTE $ZBnnn.
PAGE 52
Configuration Quick Start Starting a WAN Subsystem Object Starting an ADAPTER Object If an ADAPTER object is not in the STARTED state, use the SCF START command to start it and all of its subordinate objects (SERVER, PATH, and TASK). The command syntax is: START ADAPTER $ZZWAN.#conc_name, SUB ALL conc_name is the name of the SWAN concentrator (ADAPTER object) you want to start. Starting a SERVER Object If a SERVER object is not in the STARTED state, use the SCF START SERVER command to start it.
PAGE 53
Installing the SWAN Concentrator Configuration Quick Start Installing the SWAN Concentrator Before installing a preconfigured SWAN concentrator, verify that the configuration track-ID label physically located on the rear panel of your SWAN concentrator matches the track-ID preconfigured by HP Manufacturing (for more information, see Displaying the Configured Configuration Track-ID on page 1-26).
PAGE 54
Configuration Quick Start Displaying the Configured Configuration Track-ID Displaying the Configured Configuration Track-ID To display the configuration track-ID configured for your SWAN concentrator, use the SCF INFO ADAPTER command, OSM Service Connection, or TSM Service Application (G-series RVUs only). For more information about using OSM or TSM, see the online help within each application. The SCF command syntax is: INFO ADAPTER $ZZWAN.
PAGE 55
Configuration Quick Start Changing the Initial WAN Subsystem Configuration Changing the Initial WAN Subsystem Configuration After you have installed your SWAN concentrator, you might want to make certain changes to the initial WAN subsystem configuration.
PAGE 56
Configuration Quick Start Changing the Initial WAN Subsystem Configuration WAN Subsystem Configuration and Management Manual— 522463-011 1- 28
PAGE 57
2 Overview of the WAN Subsystem Note. Throughout this manual when a distinction between a SWAN concentrator (T3880) and a SWAN 2 concentrator (T3881) is not required, SWAN concentrator is used as a collective term. This section describes the architecture and components of the WAN subsystem, the SWAN and SWAN 2 concentrator, and the SWAN firmware.
PAGE 58
Overview of the WAN Subsystem WAN Subsystem Features Table 2-1. Data Communications Subsystems Configured by the WAN Subsystem (page 2 of 2) Subsystem Description Object Envoy Provides general-purpose protocol support that enables application programs or terminals to communicate over communications lines on the SWAN concentrator.
PAGE 59
Overview of the WAN Subsystem Architecture and Components of the WAN Subsystem Table 2-2.
PAGE 60
Overview of the WAN Subsystem Architecture and Components of the WAN Subsystem Figure 2-1. WAN Subsystem Software Components in the System Processors Application Management API WANBoot IOP Wan Manager WAN Shared Driver Config Database SNMP Trap Mux ConMgr TCP/IP TFTP Server Download Files SLSA ServerNet SAN Adapter Ethernet Router(s) SWAN Concentrator SWAN Concentrator VST 207.
PAGE 61
Overview of the WAN Subsystem WAN Manager Process WAN Manager Process The WAN manager process is created and managed by the NonStop Kernel subsystem as a subsystem manager process. The WAN manager process starts and manages the WAN subsystem processes, including the concentrator manager (ConMgr) process, the WANBoot processes, and the data-communications subsystem objects listed in Table 2-1 on page 2-1. Configuration information is stored in the configuration database.
PAGE 62
Overview of the WAN Subsystem WANBoot Process For more information on the TFTP server process, refer to TFTP Server Process Syntax on page 6-40. WANBoot Process The WANBoot process implements a BOOTP client and a BOOTP server for each TCP/IP process that supports the SWAN concentrator. The WANBoot process assigns Internet Protocol (IP) addresses to the SWAN concentrator.
PAGE 63
Overview of the WAN Subsystem SLSA If you have configured a SWAN concentrator by using conventional TCP/IP, you will notice some changes in the SCF commands to support the Parallel Library TCP/IP or NonStop TCP/IPv6 configuration. For information about configuring conventional TCP/IP, see the TCP/IP Configuration and Management Manual. For information about configuring Parallel Library TCP/IP, see the TCP/IP (Parallel Library) Configuration and Management Manual.
PAGE 64
Overview of the WAN Subsystem Power Requirements Power Requirements The SWAN concentrator power requirements are located on the physical label on the SWAN concentrator as shown in Figure 1-1 on page 1-25. Table 2-3. SWAN Concentrator Power Requirements Operating Voltage Range Frequency Range Input Power Power Supply SWAN: 85 to 264 VAC at 1A 47-63 Hz 115 VAC at 0.75 A Auto-range (custom built for high mean time between failures) Protocols Supported by the SWAN Concentrator Table 2-4.
PAGE 65
Overview of the WAN Subsystem Protocols and Line Speeds Protocols and Line Speeds A SWAN concentrator can support various line speeds based on the protocol used. With one exception, these line speeds are comparable to that of older controllers on the NonStop K-series servers. Byte-oriented protocols (Bisync and Async) are supported at a 19.2 Kbps single line per CLIP for SWAN concentrators.
PAGE 66
Overview of the WAN Subsystem Protocols and Line Speeds Figure 2-2 shows how the SWAN concentrator connects to the Ethernet ports on the NonStop S-series server. A SWAN concentrator can also connect to the Ethernet ports on a NonStop S-series I/O enclosure that connects to an Integrity NonStop NS-series server, as long as the S-series I/O enclosure has IOMF 2 components installed. Figure 2-2.
PAGE 67
Overview of the WAN Subsystem SWAN Concentrator Configuration Limits SWAN Concentrator Configuration Limits The SWAN concentrator configuration entities are the same for SWAN and SWAN 2. The configuration limits of various objects are the same for the SWAN, SWAN 2, or a mix of the two. Table 2-6.
PAGE 68
Overview of the WAN Subsystem SWAN Concentrator Configuration Limits WAN Ports and Communications Line Interface Processors (CLIPs) Three CLIPs are provided on a SWAN concentrator. Each CLIP has two WAN ports that can run different communications protocols or electrical interfaces simultaneously. For enhanced reliability, each CLIP has access to both Ethernet ports. This figure shows the six WAN ports on the front panel of the SWAN concentrator.
PAGE 69
Overview of the WAN Subsystem SWAN Firmware File SWAN Firmware File The SWAN firmware file is the 510 disk file that resides on an Integrity NonStop NS-series server or NonStop S-series server disk file and is downloaded to the SWAN concentrator. The SWAN firmware file contains the following: • • SWAN Bootcode (T7954), which is written into the flash programmable memory (PROM) on each CLIP on the SWAN concentrator.
PAGE 70
Overview of the WAN Subsystem Fault Tolerance and Fault Containment Fault Tolerance and Fault Containment Host-system connection fault tolerance is provided primarily by having two Ethernet connections to the host for each WAN port and allowing the SWAN concentrator to use either connection. Only one connection is needed for full functionality. Fault-containment is provided by the independence of the three CLIPs, each of which controls two WAN lines.
PAGE 71
Overview of the WAN Subsystem Path Switching Table 2-8. ConMgr Process PATH Switching Algorithm for TCP/IP (page 2 of 2) B. When these conditions are met... The ConMgr process will...
PAGE 72
Overview of the WAN Subsystem Path Switching These considerations apply to all the conditions listed in Table 2-8 on page 2-14: • • When a TCP/IP process has been selected, and subsequently fails, the ConMgr starts over to select an available path for the IOP.
PAGE 73
Overview of the WAN Subsystem • Multisystem Configuration Regardless of the CPU configuration for the Parallel Library TCP/IP (TCPSAM) process, the QIO sockets interface is used by the IOP to access the Parallel Library TCP/IP process. Multisystem Configuration A SWAN configuration can be accessed alternately by more than one system. The WAN configuration allows you to issue an SCF command to instruct another system to take control of the SWAN configuration.
PAGE 74
Overview of the WAN Subsystem Architecture and Components of the SWAN 2 Concentrator (T3881) Architecture and Components of the SWAN 2 Concentrator (T3881) Note. For more information about the SWAN concentrator (T3880), see Architecture and Components of the SWAN Concentrator (T3880) on page 2-7. The SWAN 2 concentrator is a communications device that connects bit-synchronous, byte-synchronous, and asynchronous devices to Integrity NonStop NS-series or NonStop S-series servers.
PAGE 75
Overview of the WAN Subsystem Supported Electrical and Physical Interfaces The SWAN 2 concentrator contains hardware components that you can replace yourself, which are called customer-replaceable units (CRUs). Table 2-10 lists these CRUs. Note. All the SWAN 2 concentrator CRUs can be replaced online without powering off the SWAN 2 concentrator, except for the chassis CRU. Table 2-10.
PAGE 76
Overview of the WAN Subsystem Supported Electrical and Physical Interfaces Figure 2-3. SWAN 2 Concentrator Front Panel With CRUs Labeled LAN Logic Boards (LBs) COMPAQ LAN2 LAN LAN1 LAN Power Supplies LINX OK 1 3 5 2 4 6 LINX OK 1 3 5 2 4 6 PWR2 PWR CLIPs (WAN LBs) WAN6 WAN WAN5 WAN WAN4 WAN 3881 WAN3 WAN WAN2 WAN PWR1 PWR WAN1 WAN VST901.vsd Figure 2-4 shows the back panel of the SWAN 2 concentrator with the CRUs and WAN serial ports (Line 1 and Line 0) labeled. Figure 2-4.
PAGE 77
Overview of the WAN Subsystem AC Power Requirements AC Power Requirements AC power requirements for the SWAN 2 concentrator are described on the physical label on the SWAN 2 concentrator as shown in Figure 2-5. Figure 2-5. SWAN 2 Concentrator Physical Label Power Requirements VST993.vsd Table 2-11 lists the AC power and environment requirements for the SWAN 2 concentrator. Table 2-11.
PAGE 78
Overview of the WAN Subsystem Protocols Supported by the SWAN 2 Concentrator Protocols Supported by the SWAN 2 Concentrator Table 2-12. Protocols and Electrical Interfaces Supported Protocols Supported IOP Electrical Interfaces Supported WANSNAX (T8168) SNAX/XF (T9064) RS-232, RS-449, V.35 WANSNXX21 (T0411) SNAX/XF (T9064) X.21 WANSNAX (T8168) SNAX/APN (T9564 RS-232, RS-449, V.35 WAN EXP LAPB (T1097 Expand LAPB) Expand (T9057) RS-232, RS-449, V.35 (X.
PAGE 79
Overview of the WAN Subsystem Protocols and Line Speeds Protocols and Line Speeds A SWAN 2 concentrator can support various line speeds based on the protocol used. With one exception, these line speeds are comparable to that of older controllers on the NonStop K-series servers. The maximum line speeds for the protocols supported by the SWAN 2 concentrator are described in Table 2-13. Table 2-13. Protocols and Maximum Lines Speeds Protocol Maximum Line Speed Lines Configured AM3270 19.
PAGE 80
Overview of the WAN Subsystem SWAN 2 Concentrator Configurations The SWAN concentrator configuration entities are the same for SWAN and SWAN 2 (see Table 2-6 on page 2-11). The SCF subsystem allows you to configure 3600 lines using any configuration of SWAN and SWAN2 concentrators. Table 2-14 assumes 6 CLIPs per ADAPTER for the SWAN 2 concentrator and shows the maximum configurations allowed. Table 2-14.
PAGE 81
Overview of the WAN Subsystem SWAN 2 Concentrator Connections SWAN 2 Concentrator Connections • • • Integrity NonStop NS-series server connection NonStop S-series server connection NonStop S-series I/O enclosure attached to an Integrity NonStop NS-series server connection SWAN 2 concentrator connections provide redundant ServerNet X and Y fabrics to the Ethernet adapters. If one ServerNet fabric fails, the Ethernet adapter can still be accessed using the remaining ServerNet fabric.
PAGE 82
Overview of the WAN Subsystem Ethernet Ports on SWAN 2 Concentrator Ethernet Ports on SWAN 2 Concentrator This figure shows how the SWAN 2 concentrator connects to the Ethernet ports on the Integrity NonStop NS-series server through the concentrator’s two 10/100 Base-T Ethernet ports. G4SAs NonStop NS-Series System G4SA G4SA G4SA Ethernet Ports 10/100 BaseT Ethernet Switch or Hub Ethernet Ports VST881.
PAGE 83
Overview of the WAN Subsystem Ethernet Ports on SWAN 2 Concentrator This figure shows how the SWAN 2 concentrator connects to the Ethernet ports on the NonStop S-series server through the concentrator’s two 10/100 Base-T Ethernet ports. A SWAN 2 concentrator can also connect to the Ethernet ports on a NonStop S-series I/O enclosure that connects to an Integrity NonStop NS-series server, as long as the S-series I/O enclosure has IOMF 2 components installed.
PAGE 84
Overview of the WAN Subsystem WAN Ports WAN Ports This figure shows the 12 WAN ports on the WAN BICs on the back panel of the SWAN 2 concentrator. Each WAN port has a 50-pin connector, which can support the RS-232, RS-449, X.21, and V.35 electrical interfaces, although this connector does not physically match any of the connectors used for these interfaces. Thumbscrews 6 WAN BICs Thumbscrews 12 WAN Ports Line 1 Line 0 VST937.
PAGE 85
Overview of the WAN Subsystem Communication Line Interface Processors (CLIPs) Communication Line Interface Processors (CLIPs) Note. The communications line interface processor (CLIP) is also known as a WAN logic board (LB). For enhanced reliability, each CLIP has access to both Ethernet ports. This figure shows the six CLIPs located on the front panel of the SWAN 2 concentrator. Each CLIP has an associated WAN BIC on the back panel.
PAGE 86
Overview of the WAN Subsystem Fault Tolerance and Fault-Containment Fault Tolerance and Fault-Containment Host-system connection fault tolerance is provided primarily by having two Ethernet connections to the host for each WAN port and allowing the SWAN concentrator to use either connection. Only one connection is needed for full functionality. Fault-containment is provided by the independence of the six CLIPs, each of which controls two WAN lines.
PAGE 87
3 Changing the Initial WAN Subsystem Configuration Note. Throughout this manual when a distinction between a SWAN concentrator (T3880) and a SWAN 2 concentrator (T3881) is not required, SWAN concentrator is used as a collective term. This section describes common changes made to the initial WAN subsystem. Use this section to modify the initial WAN subsystem configuration created for you by HP manufacturing.
PAGE 88
Changing the Initial WAN Subsystem Configuration WAN Subvolume Resolution Table 3-1. Types of System Configuration Files (page 2 of 2) File Type File Name Description Autosaved CONFIG CONFSAVE Contains an automatically saved version of the current CONFIG file that the operating system automatically creates when you load the system from a CONFBASE or CONFxxyy file to abandon a corrupt configuration.
PAGE 89
Changing the Initial WAN Subsystem Configuration WAN Subsystem SCF Interface 4. If the file does not exist in any of these subvolumes, an error is generated and the WAN manager process does not exit. 5. If the file was located in one of the subvolumes, the WAN manager process configures the object with the file resolved and saves the resolved subvolume in the system CONFIG database.
PAGE 90
Changing the Initial WAN Subsystem Configuration Change Procedure Table 3-2. WAN Subsystem Objects (page 2 of 2) Object Description SERVER Represents one communications line interface processor (CLIP). SUBSYS Represents the WAN manager process, $ZZWAN.* TASK Represents a data link control (DLC) task. *Because the WAN manager process is configured as a subsystem manager process in the NonStop Kernel subsystem, you must use the NonStop Kernel subsystem SCF interface to configure and control it.
PAGE 91
Changing the Initial WAN Subsystem Configuration Reconfiguring a DEVICE Object Example 4. Define a PROFILE object for the new line-handler process using the SCF ADD PROFILE command. 5. Define the DEVICE object for the new line-handler process using the SCF ADD DEVICE command. 6. Start the DEVICE object for the new line-handler process using the SCF START DEVICE command.
PAGE 92
Changing the Initial WAN Subsystem Configuration Reconfiguring an Ethernet Port Example 3-5. Sample SCF ADD DEVICE Command ADD DEVICE $ZZWAN.#X25P1, PROFILE PROFX25, & IOPOBJECT $SYSTEM.SYS00.X25OBJR, CPU 00, ALTCPU 01, & TYPE (61,63), RECSIZE 150, CLIP 1, LINE 0, ADAPTER S01, & PROGRAM $SYSTEM.SYS00.C1096P00 6. Start the DEVICE object for the new X25AM line-handler process by using the SCF START DEVICE command. Example 3-6. Sample SCF START DEVICE Command START DEVICE $ZZWAN.
PAGE 93
Changing the Initial WAN Subsystem Configuration Configuration Guidelines Configuration Guidelines • • • • • The SWAN concentrator can be configured to connect between any processors. The preferred and alternate TCP/IP processes that one SWAN concentrator is configured to use must be configured with separate SUBNETS. The IP addresses associated with Ethernet path A must be on the same SUBNET as the preferred TCP/IP process.
PAGE 94
Changing the Initial WAN Subsystem Configuration Ethernet Port Reconfiguration Example A PIF corresponds to a physical port and has the form: adapter-name.sac-unit#.pif-unit-letter For example, G11123.0.A identifies port A and G11123.0.B identifies port B and so on. 2. Use the SLSA subsystem SCF INFO LIF command to determine the LIF name configured for each port on each E4SA, FESA, GESA, or G4SA. Example 3-8. SLSA Subsystem SCF INFO LIF Command 2-> info lif $zzlan.* SLSA Info LIF Name $ZZLAN.L018 $ZZLAN.
PAGE 95
Changing the Initial WAN Subsystem Configuration Ethernet Port Reconfiguration Example . Example 3-9. TCP/IP Subsystem SCF INFO ROUTE and SUBNET Command 23-> info route $ztc1.* TCP/IP Info ROUTE \IDC14.$ZTC1.* Name #GW #RT2 #RT1 Subnetname #SN1 #SN1 #LOOP0 Destination 0.0.0.0 192.168.10.0 127.0.0.1 Gateway 192.168.10.1 192.168.10.3 127.0.0.1 Type G H 17-> info subnet $ztc*.* TCP/IP Info SUBNET \MYSYS.$ZTC0.* Name Devicename #LOOP0 #SN1 \NOSYS.$NOIOP \MYSYS.L11123A *IPADDRESS 127.0.0.1 172.16.40.
PAGE 96
Changing the Initial WAN Subsystem Configuration Reconfiguring the SWAN Concentrator IP Addresses SNMP trap multiplexer processes. The ADD command accepts the new HOSTIP attribute and the INFO command displays the configured HOSTIP for these processes. Reconfiguring the SWAN Concentrator IP Addresses The IP addresses that are downloaded to the SWAN concentrator might need to be replaced if the network is reconfigured.
PAGE 97
Changing the Initial WAN Subsystem Configuration IP Address Reconfiguration Example case because the preferred and alternate TCP/IP processes are configured on different SUBNETS.) IP Address Reconfiguration Example 1. Shut down an X25AM subsystem communications line by using the STOP LINE command. Example 3-11. Sample X25AM Subsystem STOP LINE Command STOP LINE $X25P1 2. Use the INFO PROCESS or the INFO SUBSYS, SUBNETLIST command to list the names of the WANBoot processes.
PAGE 98
Changing the Initial WAN Subsystem Configuration Reconfiguring TCP/IP Processes 5. Use the ALTER PATH command to reconfigure the SWAN concentrator IP address. Provide the applicable CLIP and path information. Example 3-14 reconfigures the IP address associated with path A on CLIP1 on the SWAN concentrator named $ZZWAN.#S01 Example 3-14. Sample ALTER PATH Command (Alter SWAN Concentrator IP Address) ALTER PATH $ZZWAN.#S01.1.A, IPADDRESS new_ip_address 6.
PAGE 99
Changing the Initial WAN Subsystem Configuration Configuration Guidelines Configuration Guidelines • • • The preferred and alternate TCP/IP processes that one SWAN concentrator is configured to use must be configured with separate SUBNETS. If the SWAN concentrator is on the same network as the host and you are not using any routers, the IP addresses associated with Ethernet path A must be on the same subnet as the preferred TCP/IP process.
PAGE 100
Changing the Initial WAN Subsystem Configuration Reconfiguring TCP/IP Processes Example Example 3-19 changes one SWAN concentrator IP address. Reissue this command for each SWAN concentrator CLIP and path IP address that needs to be changed. Example 3-19. Altering a SWAN Concentrator IP Address ALTER PATH $ZZWAN.#S01.1.A, IPADDRESS ip-address 6. Use the SCF START ADAPTER command with the SUB ALL option as shown in Example 3-20 to start the SWAN concentrator and the subordinate objects. Example 3-20.
PAGE 101
4 Adding a SWAN Concentrator This section describes how to add a new SWAN concentrator to your system configuration. Note. If you ordered your SWAN or SWAN 2 concentrator with a NonStop S-series server, do not use this section to configure your concentrator. Use Section 1, Configuration Quick Start instead.
PAGE 102
Adding a SWAN Concentrator • Planning for LAN Communications SWAN Concentrator Configuration Planning Form. See either: ° ° SWAN Concentrator (T3880) Configuration-Planning Form on page 4-12 SWAN 2 Concentrator (T3881) Configuration-Planning Form on page 4-13 3. Perform any site-planning tasks needed for the SWAN concentrator. This site planning can include planning cable routing and determining where the SWAN concentrator should be installed.
PAGE 103
Adding a SWAN Concentrator Planning for LAN Communications 3. Configure six or twelve (depending on the type of concentrator) Internet protocol (IP) addresses, one for each media access control (MAC) address on the SWAN concentrator. 4. Identify the configuration track-ID assigned to your SWAN concentrator.
PAGE 104
Adding a SWAN Concentrator Step 1: Selecting E4SAs, FESAs, GESAs, or G4SAs Step 1: Selecting E4SAs, FESAs, GESAs, or G4SAs HP recommends that you configure the SWAN concentrator to connect to ports on two E4SAs, FESAs, GESAs, G4SAs or VIO enclosures. This configuration provides fault tolerance for the input/output processes (IOPs) that use the SWAN concentrator in the event of a failure on one of the paths to the SWAN concentrator. Note.
PAGE 105
Adding a SWAN Concentrator Step 1: Selecting E4SAs, FESAs, GESAs, or G4SAs A PIF corresponds to a physical port and has the form: adapter-name.sac-unit#.pif-unit-letter For example, G11123.0.A identifies port A; G11123.0.B identifies port B, and so on. Note. For information about how to configure a LAN adapter, see the LAN Configuration and Management Manual.
PAGE 106
Adding a SWAN Concentrator Step 1: Selecting E4SAs, FESAs, GESAs, or G4SAs Connecting the SWAN Concentrator Through Ethernet Routers You can configure a SWAN concentrator that is connected to an Integrity NonStop NS-series or NonStop S-series server through a router (for more information, see Figure 4-1 on page 4-7). The configuration is the same as through a non-routed environment, except for: • • • • You must add a ROUTE object to the preferred and alternate TCP/IP processes.
PAGE 107
Adding a SWAN Concentrator Step 2: Identifying the TCP/IP Processes and Subnets Figure 4-1. Routed Configuration BootP Relay RFC 1542 192.168.10.1 192.168.11.1 192.168.12.1 192.168.13.1 192.168.10.0 192.168.11.0 192.168.13.0 192.168.10.10 192.168.11.10 192.168.12.0 PATH A 192.168.12.11 192.168.12.12 192.168.12.13 PATH B 192.168.13.11 192.168.13.12 192.168.13.13 VST999.vsd Step 2: Identifying the TCP/IP Processes and Subnets Note.
PAGE 108
Adding a SWAN Concentrator Step 3: Associating IP Addresses With MAC Addresses Example 4-4. Sample SCF INFO SUBNET Command 17-> info subnet $zt*.* TCP/IP Info SUBNET \MYSYS.$ZTC0.* Name Devicename #LOOP0 #SN1 \NOSYS.$NOIOP \MYSYS.L11123A *IPADDRESS TYPE *SUBNETMASK SuName QIO *R 127.0.0.1 LOOP-BACK %HFF000000 172.16.40.65 ETHERNET %HFFFFFF00 OFF N ON N TCP/IP Info SUBNET \MYSYS.$ZTC1.* Name Devicename #LOOP0 #SN1 \NOSYS.$NOIOP \MYSYS.
PAGE 109
Adding a SWAN Concentrator Step 3: Associating IP Addresses With MAC Addresses Figure 4-3 shows the location of the MAC address label on the rear panel of a SWAN 2 concentrator. Figure 4-3. SWAN 2 Concentrator Label, MAC Address Information MAC Address Track ID VST996.vsd During SWAN concentrator configuration, you must associate an IP address with each MAC address.
PAGE 110
Adding a SWAN Concentrator Step 4: Identifying the Configuration Track-ID Step 4: Identifying the Configuration Track-ID Figure 4-4 shows the location of the configuration track-ID on the rear panel of a SWAN concentrator (T3880) and Figure 4-5 shows the configuration track-ID located on the rear panel of a SWAN 2 concentrator (T3881).
PAGE 111
Adding a SWAN Concentrator SWAN Concentrator Configuration-Planning Forms SWAN Concentrator Configuration-Planning Forms Figure 4-6 on page 4-12 shows the SWAN concentrator configuration-planning form and Figure 4-7 on page 4-13 shows the SWAN 2 concentrator configuration-planning form. Complete one copy of this form for each concentrator you want to add. See Table 4-1 on page 4-14 for instructions about completing either form. Note. Adding a SWAN 2 concentrator might require several planning forms.
PAGE 112
Adding a SWAN Concentrator SWAN Concentrator Configuration-Planning Forms Figure 4-6.
PAGE 113
Adding a SWAN Concentrator SWAN Concentrator Configuration-Planning Forms Figure 4-7.
PAGE 114
Adding a SWAN Concentrator SWAN Concentrator Configuration-Planning Forms Table 4-1. Completing the SWAN Concentrator Configuration-Planning Form (page 1 of 3) Field Meaning These fields are information you will need for the ADD ADAPTER command: Concentrator Name Is the name you assign to the SWAN concentrator (#concname). Configuration Track-ID Is the name of the configuration track-ID located on the rear panel of the SWAN concentrator (TRACKID configuration track-ID).
PAGE 115
Adding a SWAN Concentrator SWAN Concentrator Configuration-Planning Forms Table 4-1. Completing the SWAN Concentrator Configuration-Planning Form (page 2 of 3) Field Meaning CLIP 1 Path A IP Address Is the IP address associated with this MAC address (IPADDRESS ip-address). You must configure six or twelve IP addresses (depending on the type of concentrator) to fully configure the SWAN concentrator.
PAGE 116
Adding a SWAN Concentrator SWAN Concentrator Configuration-Planning Forms Table 4-1. Completing the SWAN Concentrator Configuration-Planning Form (page 3 of 3) Field Meaning These fields are information you will need for the ADD DEVICE command: CLIP 1 Line 0 To configure each DEVICE object, you need this information: 1. Record the CLIP number and WAN line the DEVICE will use (CLIP clip-num and LINE line-num). 2. Record the path the DEVICE will prefer to use (PATH { A | B }). 3.
PAGE 117
Adding a SWAN Concentrator Configuring the SWAN Concentrator Configuring the SWAN Concentrator Note. As an alternative to using multiple Subsystem Control Facility (SCF) commands, you can configure one or more SWAN concentrators using WAN Wizard Pro, a graphical user interface (GUI) that guides you step-by-step through the configuration process. For information about how to access WAN Wizard Pro, see About This Manual.
PAGE 118
Adding a SWAN Concentrator Configuration Steps Table 4-2. WAN Subsystem SCF Commands Used to Configure a SWAN Concentrator Command Description ADD ADAPTER Configures the SWAN concentrator. ADD PATH Assigns an IP address to each Ethernet port interface (SCC1 and SCC2) on each CLIP on the SWAN concentrator. ADD PROCESS Configures the Concentrator Manager (ConMgr) process. ADD SERVER Configures the CLIPs on the SWAN concentrator.
PAGE 119
Adding a SWAN Concentrator Configuring and Starting the SWAN Concentrator Objects cpu-num indicates the processor in which the ConMgr process is to run. Possible values are 0 through n. For more information about creating ConMgr process names, see HP Manufacturing Naming Conventions (G06.26 and Earlier RVUs) on page 1-3 or HP Manufacturing Naming Conventions (G06.27 and Later RVUs and H06.03 and Later RVUs) on page 1-7.
PAGE 120
Adding a SWAN Concentrator Configuring and Starting the SWAN Concentrator Objects track-ID is located on the rear panel of each SWAN concentrator (For more information, see Figure 4-4 on page 4-10 and Figure 4-5 on page 4-10). Note. The value for the TRACKID is case-sensitive. If you specify the value incorrectly, you cannot use the SWAN concentrator because the WAN subsystem and the OSM or TSM discovery process will not find the SWAN concentrator when it is powered on.
PAGE 121
Adding a SWAN Concentrator Configuring and Starting the SWAN Concentrator Objects KERNELCODE $SYSTEM.CSSnn.C7953P00 (C7953Q00 for SWAN 2 concentrator) indicates the name of the firmware object code of the microcode file you want to run in the essential part of the FLASH memory. The file name specified must be secured with “N” read access. If you are using the 6763 Common Communications ServerNet adapter (commonly known as SS7), the KERNELCODE file is C0099P00. Note.
PAGE 122
Adding a SWAN Concentrator Configuring and Starting the SWAN Concentrator Objects ip-address indicates the IP address to be assigned to the path. These IP addresses appear on your SWAN Concentrator Configuration-Planning Forms on page 4-11. Starting the ADAPTER, SERVER, PATH, and TASK Objects After the WAN subsystem objects have been added to the configuration database, you must start them using the SCF START ADAPTER command with the SUB ALL option. Example 4-8.
PAGE 123
Adding a SWAN Concentrator Sample Configuration Sample Configuration This illustration shows a SWAN concentrator ($ZZWAN.#S01) configured between LIFs L11123A and L11124A on G4SA G11123 and G11124. A sample command file for this configuration follows this illustration. Processor 0 Processor 1 WAN Manager Process (Primary) $ZZWANP $ZZWAN.#0 $ZZWANB WAN Manager Process (Backup) $ZZWAN.
PAGE 124
Adding a SWAN Concentrator Sample Configuration These SCF commands were used in a command file to create the WAN subsystem processes and objects shown in the sample configuration. ALLOW ALL ERRORS ================================================================ == Configure and start the ConMgr processes == ================================================================ ADD PROCESS $ZZWAN.#0, IOPOBJECT $SYSTEM.SYS00.CONMGR ADD PROCESS $ZZWAN.#1, IOPOBJECT $SYSTEM.SYS00.CONMGR START PROCESS $ZZWAN.
PAGE 125
Adding a SWAN Concentrator Adding DEVICE Objects That Use the WAN Ports Adding DEVICE Objects That Use the WAN Ports After the SWAN concentrator is configured, you can configure the six WAN ports on the SWAN concentrator or twelve WAN ports on the SWAN 2 concentrator. To configure a WAN port, you must add one or more PROFILE objects (using the SCF ADD PROFILE command) along with one DEVICE object (using the SCF ADD DEVICE command) for each line that is needed.
PAGE 126
Adding a SWAN Concentrator Looking at the Contents of a PROFILE Object new profile exactly like the existing one by not specifying any modifiers in the command as shown in Example 4-10 on page 4-26. Example 4-10. Defining a PROFILE Object Using the LIKE Attribute ADD PROFILE $ZZWAN.#2nd_term, LIKE FILE my_term 3.
PAGE 127
Adding a SWAN Concentrator Looking at the Contents of a PROFILE Object Example 4-12. Sample INFO PROFILE Command -> INFO PROFILE $ZZWAN.#my_term WAN MANAGER Info profile \WILLOW.$ZZWAN.#my_term No devices or processes are using this profile.
PAGE 128
Adding a SWAN Concentrator Associating a PROFILE Object to a DEVICE Object Associating a PROFILE Object to a DEVICE Object After you have defined a WAN subsystem PROFILE object, you then make the PROFILE object available for use by the data communications subsystem object by adding it to the definition of the DEVICE object. You can associate a PROFILE object to a DEVICE object in any of the following ways: 1.
PAGE 129
Adding a SWAN Concentrator Associating a PROFILE Object to a DEVICE Object 3. Define a PROFILE object by issuing the ADD PROFILE command and alter two of the modifiers in the DEVICE definition. The syntax fragment in Example 4-14 on page 4-28 illustrates this configuration; the boldface text in this example highlights the relevant information that is being described. For simplicity, only a few of the modifiers are shown. a. First, a PROFILE object is defined and displayed, as shown in Example 4-15.
PAGE 130
Adding a SWAN Concentrator Associating a PROFILE Object to a DEVICE Object Example 4-16. Adding a DEVICE Object and Viewing Modifier Values 4-> 4-> 4-> 4-> ADD DEVICE $ZZWAN.#ATPDEV, ADAPTER SWAN38, ALTCPU 2 & , CLIP 1, CPU 3, IOPOBJECT $SYSTEM.SYS00.OATPCSS & , LINE 1, PATH B, PROFILE ATPPROF, RECSIZE 150 & , TYPE (53,0), NAME #MYTERM, RETRIES 25 5-> INFO DEVICE $ZZWAN.#ATPDEV, DETAIL WAN MANAGER Detailed Info Device \TAHITI.$ZZWAN.#ATPPPDEV *Adapter Name..... *Line ............ Profile...........
PAGE 131
Adding a SWAN Concentrator Configuration Requirements and Recommendations Configuration Requirements and Recommendations • • • • • • The WAN manager process is preconfigured by HP manufacturing and is running in processor 0 with the backup process running in processor 1. HP recommends that you configure the SWAN concentrator across two E4SAs, FESAs, GESAs, G4SAs or VIO enclosures for improved fault tolerance. (VIO enclosures are supported in H06.08 and subsequent H-series RVUs.
PAGE 132
Adding a SWAN Concentrator Configuration Requirements and Recommendations WAN Subsystem Configuration and Management Manual— 522463-011 4- 32
PAGE 133
5 Managing the WAN Subsystem Note. Throughout this manual when a distinction between a SWAN concentrator (T3880) and a SWAN 2 concentrator (T3881) is not required, SWAN concentrator is used as a collective term. This section describes the WAN subsystem Subsystem Control Facility (SCF) commands used to monitor, reconfigure, and control the WAN subsystem. For more information on SCF syntax, see Section 6, SCF Commands.
PAGE 134
Managing the WAN Subsystem Displaying Information About WAN Subsystem Processes and Objects Table 5-1. WAN Subsystem SCF Commands for Displaying Information (page 2 of 3) SCF Command NAMES STATUS SCF Object Type Description PROFILE Returns a list of the data-communications subsystem objects configured to use the specified profile and a list of the modifier keywords and corresponding values contained in the profile. SERVER Returns version information for a CLIP on a SWAN concentrator.
PAGE 135
Managing the WAN Subsystem Displaying Information About the WAN Manager Process Table 5-1. WAN Subsystem SCF Commands for Displaying Information (page 3 of 3) SCF Command VERSION SCF Object Type Description TASK Displays current status and configuration information about a DLC task. PROCESS Displays the version level of the ConMgr process. SUBSYS $ZZWAN Displays the version level of the $ZZWAN subsystem.
PAGE 136
Managing the WAN Subsystem Reconfiguring the WAN Subsystem Reconfiguring the WAN Subsystem WAN subsystem reconfiguration tasks include: • • • • • Adding WAN Subsystem Processes and Objects Adding the WAN Manager Process Deleting WAN Subsystem Processes and Objects Altering WAN Subsystem Processes and Objects Altering the WAN Manager Process Note.
PAGE 137
Managing the WAN Subsystem Deleting WAN Subsystem Processes and Objects Deleting WAN Subsystem Processes and Objects You use the WAN subsystem SCF DELETE command to delete WAN subsystem processes and objects. Table 5-3. WAN Subsystem SCF DELETE Command Objects Command Object Description DELETE ADAPTER Removes the definition of a SWAN concentrator from the configuration database. DEVICE Removes the definition of a data-communications subsystem object from the configuration database.
PAGE 138
Managing the WAN Subsystem Altering WAN Subsystem Processes and Objects Altering WAN Subsystem Processes and Objects You use the WAN subsystem SCF ALTER command to alter WAN subsystem processes and objects. Table 5-4. WAN Subsystem SCF ALTER Command Objects Command Object Description ALTER ADAPTER Changes the values of the attributes of a SWAN concentrator. DEVICE Changes the values of the attributes of a data-communications subsystem object.
PAGE 139
Managing the WAN Subsystem Altering the WAN Manager Process Altering the WAN Manager Process The WAN manager process is defined by the NonStop Kernel subsystem as a PROCESS object named $ZZKRN.#ZZWAN. It is preconfigured by HP manufacturing and started during the system load sequence. You can alter the configuration of the WAN manager process by using the NonStop Kernel subsystem SCF ALTER PROCESS command as described in the SCF Reference Manual for the Kernel Subsystem.
PAGE 140
Managing the WAN Subsystem Stopping the WAN Manager Process Table 5-5. WAN Subsystem SCF Commands for Stopping Processes and Objects (page 2 of 2) Command Object Description PROCESS Terminates the use of a ConMgr, an SNMP trap multiplexer, a TFTP server, or a WANBoot process. Terminating an autoconfigured process succeeds and requires you to start the process to be active. SERVER Terminates the use of a CLIP. TASK Terminates a DLC task.
PAGE 141
Managing the WAN Subsystem Starting the WAN Manager Process Caution. When starting a SWAN concentrator from a command file, you must include the ALLOW ALL ERRORS command. You will receive DIAG task errors. If you don’t include the ALLOW ALL ERRORS command, you cannot start WAN lines. When SCF is used in interactive mode, the default is ALLOW ALL errors and warnings. Starting the WAN Manager Process The WAN manager process is defined by the NonStop Kernel subsystem as a PROCESS object named $ZZKRN.#ZZWAN.
PAGE 142
Managing the WAN Subsystem Changing the Processor of the WAN Manager Process WAN Subsystem Configuration and Management Manual— 522463-011 5- 10
PAGE 143
6 SCF Commands Note. Throughout this manual when a distinction between a SWAN concentrator (T3880) and a SWAN 2 concentrator (T3881) is not required, SWAN concentrator is used as a collective term. This section describes the Subsystem Control Facility (SCF) interface to the WAN subsystem and provides SCF command syntax. For general information about running SCF, see the SCF Reference Manual for G-Series RVUs or the SCF Reference Manual for H-Series RVUs.
PAGE 144
SCF Commands Overview of the WAN Subsystem SCF Interface Overview of the WAN Subsystem SCF Interface The WAN subsystem SCF interface is provided to configure, control, and display information about configured objects within the WAN subsystem. WAN Subsystem Objects The SCF objects for the WAN subsystem correspond to components within the subsystem. There are eight WAN object types: • • • • • • • • SUBSYS ADAPTER DEVICE PROCESS PROFILE SERVER TASK PATH Figure 6-1.
PAGE 145
SCF Commands WAN Subsystem Objects SUBSYS Object The SUBSYS object represents the WAN manager process, $ZZWAN. There can be only one WAN manager process per system. The WAN manager can support from one to 16 ConMgr processes, one or more WANBoot processes, one or more ADAPTER objects, and up to 3600 DEVICE objects. Note.
PAGE 146
SCF Commands WAN Subsystem Objects DEVICE Object You configure one or more DEVICE objects depending on which data-communications subsystem you are configuring. DEVICE objects might, or might not, access the SWAN concentrator: • • When defining DEVICE objects that access the SWAN concentrator, the attributes in the ADD DEVICE command that configure the SWAN concentrator are required.
PAGE 147
SCF Commands Object States data communications subsystem object by specifying the profile name in the PROFILE attribute in the ADD DEVICE command. Object States Objects can have operational states, such as STOPPED or STARTED. The exact sequence of states an object goes through varies from object to object and from subsystem to subsystem. Some subsystem commands recognize only a few states. States are discussed with each subsystem description.
PAGE 148
SCF Commands Sensitive and Nonsensitive Commands Sensitive and Nonsensitive Commands SCF commands are either sensitive or nonsensitive. Sensitive commands can change the state or configuration of subsystem objects or change the values of statistics counters; they can cause communications to cease if improperly used. Nonsensitive commands request information or status but that do not affect operation.
PAGE 149
SCF Commands ABORT Command ABORT Command ABORT is a sensitive command that is used to terminate the operation of a WAN subsystem object as quickly as possible. Only enough processing is done to ensure that the object can run again when it is restarted. ABORT ADAPTER Command Use the ABORT ADAPTER command to terminate the operation of all CLIPs on a SWAN concentrator. The ABORT ADAPTER command places the ADAPTER object in the STOPPED state, which prevents further use of the CLIPs on the SWAN concentrator.
PAGE 150
SCF Commands ABORT PATH Command ONLY specifies that only the subordinate objects are affected. Considerations • • Existing activity over the WAN lines running in the SWAN concentrator is not affected by the ABORT command. You must issue a START ADAPTER command to allow commands on objects configured with that ADAPTER. ABORT PATH Command Use the ABORT PATH command to terminate the operation of a path to a CLIP.
PAGE 151
SCF Commands ABORT PROCESS Command ABORT PROCESS Command Use the ABORT PROCESS command to terminate the operation of a ConMgr, an SNMP trap multiplexer, a TFTP server, or a WANBoot process. The ABORT PROCESS command places the PROCESS object in the STOPPED state. The ABORT PROCESS command has this syntax: For a ConMgr process: ABORT PROCESS $ZZWAN.#cpu-num For an SNMP trap multiplexer, a TFTP server, or a WANBoot process: ABORT PROCESS $ZZWAN.
PAGE 152
SCF Commands ABORT PROCESS Command Considerations These notes describe considerations you should be aware of before using the ABORT PROCESS command to abort the ConMgr, SNMP trap multiplexer, TFTP server, or WANBoot process. ConMgr Process • • DEVICE objects use the ConMgr process to download data link control (DLC) tasks to the SWAN concentrator. DLC tasks cannot be downloaded when the ConMgr process that a device uses is stopped.
PAGE 153
SCF Commands ABORT SERVER Command ABORT SERVER Command Use the ABORT SERVER command to terminate the operation of a CLIP. The ABORT SERVER command places the SERVER object in the STOPPED state, which prevents further use of the CLIP. The ABORT SERVER command has this syntax: ABORT SERVER $ZZWAN.#conc-name.clip-num [ , SEL [ NOT ] sumstate ] [ , SUB { ALL | NONE | ONLY } ] conc-name.clip-num indicates a CLIP. Value: The SERVER name is the name of the SWAN concentrator, followed by the CLIP number.
PAGE 154
SCF Commands ABORT TASK Command ONLY specifies that only the subordinate objects are affected. Considerations • • • • • Existing activity over the WAN lines running in the CLIP is affected. You must issue a START SERVER command before you can start new WAN lines or download DLC tasks on the CLIP. The state of the SERVER indicates whether the CLIP is being controlled by this system. After an ABORT SERVER command issued, the WANBoot process does not respond to BOOTP requests from the CLIP.
PAGE 155
SCF Commands ADD Command Wild card: You can use the asterisk (*) to specify all configured SERVER objects. Considerations • • • Activity over the WAN line running in the port associated with the TASK will be terminated. You must issue a START TASK command before you can use the task. The ConMgr process must be running to be able to abort tasks. ADD Command ADD is a sensitive command that is used to define a WAN subsystem object to the configuration database.
PAGE 156
SCF Commands ADD ADAPTER Command Value: The SWAN concentrator name is a string of alphanumeric characters. The string is limited to the # sign followed by eight characters. The first character must be an alphabetic character. The name of each SWAN concentrator must be unique within the Integrity NonStop NS-series or NonStop S-series server. Default: None provided. ALTGATEWAYIP alt-router-ip-address indicates the alternate SWAN-side router IP address for Path B. A gateway IP address of 0 (0.0.0.
PAGE 157
SCF Commands ADD ADAPTER Command address portion of an IP address is subdivided into a subnet number that identifies a particular subnet and a host number that identifies a host within the subnet. Value: An IP address is a 4-octet (32-bit) numeric value. It is specified in dotted decimal notation, which represents 4 octets in ASCII, separated by periods; for example, 133.50.85.43. Each octet value is a number in the range 0 through 255. Default: None provided.
PAGE 158
SCF Commands ADD ADAPTER Command HOSTIP ip-address indicates the IP address assigned to a SUBNET on the preferred TCP/IP process (specified in the TCP/IP attribute). Value: An IP address is a 4-octet (32-bit) numeric value. It is specified in dotted decimal notation, which represents 4 octets in ASCII, separated by periods; for example, 133.50.85.43. Each octet value is a number in the range 0 through 255. Default: None provided.
PAGE 159
SCF Commands ADD ADAPTER Command address portion of an IP address is subdivided into a subnet number that identifies a particular subnet and a host number that identifies a host within the subnet. Value: An IP address is a 4-octet (32-bit) numeric value. It is specified in dotted decimal notation, which represents 4 octets in ASCII, separated by periods; for example, 133.50.85.43. Each octet value is a number in the range 0 through 255. Default: None provided.
PAGE 160
SCF Commands ADD ADAPTER Command discovery processes will not find the SWAN concentrator when the SWAN concentrator is powered on. • During the configuration of WAN objects, the WAN manager process is provided with files. The files are specified for the KERNELCODE attribute, SNMPCODE attribute, IOPOBJECT attribute, and PROFILE object. The WAN manager process uses the persistence principle to resolve the file in the current SYSnn/CSSnn to locate the files.
PAGE 161
SCF Commands ADD DEVICE Command If the given HOSTIP address is already configured with a different TCP/IP name in other ADAPTER configurations, an error results. For example, an error occurs if ADAPTER AA is configured with a HOSTIP address of 192.168.10.2 and a TCP/IP name of $ZTC1, and an ADD ADAPTER is attempted with a HOSTIP address of 192.168.10.2 and a TCP/IP name of $ZTC5. ADD DEVICE Command Use the ADD DEVICE command to define a data communications subsystem object to the configuration database.
PAGE 162
SCF Commands ADD DEVICE Command Value: The device name is a string of alphanumeric characters. The string is limited to the number sign (#) followed by seven characters. The first character must be an alphanumeric character. For subsystem-specific naming guidelines, see the manuals listed in Table 6-4 on page 6-21. Default: None provided. ADAPTER conc-name indicates the SWAN concentrator to be used by the DEVICE. Value: The name of the SWAN concentrator as specified in the ADD ADAPTER command.
PAGE 163
SCF Commands ADD DEVICE Command IOPOBJECT object-file-name indicates the file name of the executable object code for the data-communications subsystem object. See the manual listed in Table 6-4 for the name of the object code file used by the type of data-communications subsystem object you are configuring. Table 6-4.
PAGE 164
SCF Commands ADD DEVICE Command PATH path-name indicates which Ethernet path on the SWAN concentrator you prefer the device to use. Value: The possible values are A or B. A indicates the A Ethernet path. B indicates the B Ethernet path. Default: None provided. PROFILE [ existing-profile-name | LIKE #existing-device-name } existing-profile-name specifies a PROFILE name that defines the modifier-keywords and valid modifier-values for use by a DEVICE object. .
PAGE 165
SCF Commands • ADD PATH Command You must issue a START DEVICE command to start the DEVICE object, which must start the data- communications subsystem object before you can use it. ADD PATH Command Use the ADD PATH command to define, to the configuration database, IP addresses for the MAC addresses on SSC1 and SSC2 on each CLIP. You must use the ADD PATH command six or twelve times (depending on the type of concentrator) to define all IP addresses to one SWAN concentrator.
PAGE 166
SCF Commands ADD PROCESS Command Considerations • • • The SWAN concentrator must have been previously defined with the ADD ADAPTER and ADD SERVER commands. Add the PATH object with the ADD PATH command. The PATH object is defined and is placed in the STOPPED state. You must issue the ADD PATH command six times to configure both Ethernet paths on all three CLIPs on one SWAN concentrator. You must issue a START PATH command before you can use the Ethernet path.
PAGE 167
SCF Commands ADD PROCESS Command IOPOBJECT object-file-name indicates the file name of the executable object code for the ConMgr process. Value: The object file resides (by default) at $SYSTEM.SYSnn.CONMGR. Default: None provided. SNMP Trap Multiplexer, TFTP Server, WANBoot Process Syntax Starting with the G06.13 RVU, you do not need to configure the SNMP trap multiplexer, TFTP Server, or WANBoot processes. These processes are automatically configured when a new ADAPTER object is added.
PAGE 168
SCF Commands ADD PROFILE Command TFTP Server Process • • • • Starting with the G06.13 RVU, only one TFTP Server process can be configured for each subnet (the combination of TCP/IP process and HOSTIP defines a subnet for WAN configuration purposes). Starting with the G06.13 RVU of the WAN subsystem, the TFTP server process is automatically configured by WanMgr. Each subnet is automatically configured with this process as soon as the adapter is configured.
PAGE 169
SCF Commands ADD SERVER Command profile-name indicates the name of the profile. Value: The profile name is a string of alphanumeric characters. The string is limited to the number sign (#)followed by 10 characters. The first character must be an alphabetic character. The name of each profile must be unique within the Integrity NonStop NS-series or NonStop S-series server. Default: None provided.
PAGE 170
SCF Commands ALTER Command conc-name.clip-num indicates a CLIP. Value: The SERVER name is the name of the SWAN concentrator, followed by the CLIP number. conc-name is the name of the SWAN concentrator as specified in the ADD ADAPTER command. clip-num is the CLIP number. The possible values for the CLIP number are 1, 2, or 3 for a SWAN concentrator and 1, 2, 3, 4, 5, or 6 for a SWAN 2 concentrator. Default: None provided.
PAGE 171
SCF Commands ALTER ADAPTER Command The ALTER ADAPTER command has this syntax (you must specify one or more attributes): ALTER ADAPTER $ZZWAN.
PAGE 172
SCF Commands ALTER ADAPTER Command ALTHOSTIP ip-address indicates the IP address assigned to a SUBNET on the alternate TCP/IP process (specified in the ALTTCPIP attribute). Value: An IP address is a 4-octet (32-bit) numeric value. It is specified in dotted decimal notation, which represents 4 octets in ASCII, separated by periods; for example, 133.50.85.43. Each octet value is a number in the range 0 through 255. Default: None provided.
PAGE 173
SCF Commands ALTER ADAPTER Command HOSTIP ip-address indicates the IP address assigned to a SUBNET on the preferred TCP/IP process (specified in the TCP/IP attribute). Value: An IP address is a 4-octet (32-bit) numeric value. It is specified in dotted decimal notation, which represents 4 octets in ASCII, separated by periods; for example, 133.50.85.43. Each octet value is a number in the range 0 through 255. Default: None provided.
PAGE 174
SCF Commands ALTER ADAPTER Command TCP/IP tcpip-name indicates the name of the preferred TCP/IP process that supports the SWAN concentrator. Value: The name of the TCP/IP process as configured in the TCP/IP subsystem SCF ADD PROCESS command. Default: None provided. TRACKID "configuration-track-id" uniquely identifies the SWAN concentrator. The configuration track-ID is assigned when the SWAN concentrator is manufactured.
PAGE 175
SCF Commands ALTER ADAPTER Command The WAN manager process uses the persistence principle to resolve the file in the current SYSnn/CSSnn to locate the files. This keeps the most recent files being used even when the SYSnn/CSSnn changes. The WAN manager process resolves the subvolume using this algorithm: Note. This algorithm applies only if the volume is a system disk (usually $SYSTEM). 1. First, the WAN manager process checks for the file in the current SYSnn/CSSnn. 2.
PAGE 176
SCF Commands ALTER DEVICE Command ALTER DEVICE Command Use the ALTER DEVICE command to change the values of a data-communications subsystem object. The ALTER DEVICE command changes only the specified attributes of the target object. The ALTER DEVICE command has this syntax (you must specify one or more attributes): ALTER DEVICE $ZZWAN.
PAGE 177
SCF Commands ALTER DEVICE Command HIGHPIN "ON" | "OFF" indicates whether the data communications subsystem object is to be run highpin. Value: The possible values are ON or OFF. Default: OFF. IOPOBJECT object-file-name indicates the file name of the executable object code for the data-communications subsystem object. The manuals listed in Table 6-4 on page 6-21 describe the IOPOBJECT default file names for DEVICE objects.
PAGE 178
SCF Commands RESET ALTER PATH Command [ ( modifier-keyword [ modifier-keyword ... ] ) ] resets the specified modifier (or modifiers) back to its default value. The parenthesis are required if more than one modifier is specified. If no modifiers are specified, then all modifiers are reset to their default values. TYPE type , sub-type indicates the NonStop Kernel registered type and subtype for the DEVICE object.
PAGE 179
SCF Commands ALTER PROCESS Command conc-name.clip-num.path-name indicates the path name. Value: The path name is the name of the SWAN concentrator, followed by the CLIP number, followed by the path name. conc-name is the SWAN concentrator as specified in the ADD ADAPTER command. clip-num is the CLIP number. The possible values for the CLIP number are 1, 2, or 3 for a SWAN concentrator and 1, 2, 3, 4, 5, or 6 for a SWAN 2 concentrator. path-name is an Ethernet path.
PAGE 180
SCF Commands ALTER PROCESS Command ConMgr Process Syntax The ALTER PROCESS command has this syntax for a ConMgr process: ALTER PROCESS $ZZWAN.#cpu-num , IOPOBJECT object-file-name cpu-num indicates the name of the ConMgr process by specifying the processor the ConMgr process is to run in. The WAN subsystem names the ConMgr process $ZZWAN.nn where nn is the processor number. Value: The possible values are 0 through n. The ConMgr process name, when displayed from the WAN subsystem INFO command, is $ZZWAN.
PAGE 181
SCF Commands ALTER PROCESS Command process-name indicates the name of the SNMP trap multiplexer process. The SNMP trap multiplexer process name should follow the naming convention described in HP Manufacturing Naming Conventions (G06.26 and Earlier RVUs) on page 1-3 or HP Manufacturing Naming Conventions (G06.27 and Later RVUs and H06.03 and Later RVUs) on page 1-7. Value: The process name is a string of alphanumeric characters. The string is limited to the number sign (#)followed by five characters.
PAGE 182
SCF Commands ALTER PROCESS Command To determine the IP address of a SUBNET, use the INFO SUBNET command as shown in Example 6-1 on page 6-14. TCP/IP tcpip-name indicates the name of the preferred TCP/IP process that supports the SWAN concentrator. Value: The name of the TCP/IP process as configured in the TCP/IP subsystem SCF ADD PROCESS command. Default: None provided. TYPE type , sub-type indicates the NonStop Kernel registered type and subtype for the PROCESS object.
PAGE 183
SCF Commands ALTER PROCESS Command . Value: The process name is a string of alphanumeric characters. The string is limited to the number sign (#) followed by five characters. The first character must be an alphabetic character. The name of each process must be unique within the Integrity NonStop NS-series or NonStop S-series server. Default: None provided. ALTCPU alt-cpu-num indicates the processor in which you want the backup process to run when it is started by the WAN manager process.
PAGE 184
SCF Commands ALTER PROCESS Command STARTUP "$SYSTEM.CSSnn" specifies the location of the download files access by the TFTP server process. The default is $SYSTEM.CSSnn. The download files accessed by the TFTP server process must be secured with “N” read access. TCP/IP $tcpip-name indicates the name of a TCP/IP process that supports the SWAN concentrator. You must not specify a TCP/IP process used by another TFTP server process.
PAGE 185
SCF Commands ALTER PROCESS Command . Value: The process name is a string of alphanumeric characters. The string is limited to the number sign (#) followed by five characters. The first character must be an alphabetic character. The name of each process must be unique within the Integrity NonStop NS-series or NonStop S-series server. Default: None provided. ALTCPU alt-cpu-num indicates the processor in which you want the backup process to run when it is started by the WAN manager process.
PAGE 186
SCF Commands ALTER PROCESS Command STARTUP"TCP/IP tcpip-name,[DUMPVOL $dumps]" is an ASCII string representing the startup message that is passed to the WANBoot process when it is created and started. tcpip-name indicates the name of a TCP/IP process that supports the SWAN concentrator. Value: The name of the TCP/IP process as configured in the TCP/IP subsystem SCF ADD PROCESS command. Default: None provided. By default, WANBoot saves the SWAN CLIP DUMP files on $SYSTEM.ZWANDUMP subvolume.
PAGE 187
SCF Commands ALTER PROFILE Command WANBoot Process • • Since the WANBoot process is used to download IP addresses to the SWAN concentrator, any IP addresses associated with the same TCP/IP subnet as the WANBoot cannot be downloaded while the WANBoot process is aborted. If the SWAN concentrator is powered on while the WANBoot process is aborted, the SWAN concentrator cannot get its IP addresses downloaded, so no activity on the SWAN concentrator can take place.
PAGE 188
SCF Commands ALTER TASK Command ALTER TASK Command Use the ALTER TASK command to download task microcode to the CLIP FLASH memory. When the task is started, it is copied to the CLIP RAM. Each CLIP can be configured with one DLC0 task for WAN port 0 and one DLC1 task for WAN port 1. The ALTER TASK command has this syntax: ALTER TASK $ZZWAN.#conc-name.clip-num.dlc-task , PROGRAM download-file-name conc-name.clip-num.dlc-task indicates the task.
PAGE 189
SCF Commands ALTER TASK Command Table 6-5. DLC Task Microcode Files for a SWAN Concentrator (T3880) Device Object DLC Task Description File Name $SYSTEM.
PAGE 190
SCF Commands Considerations Table 6-6. DLC Task Microcode Files for a SWAN 2 (T3881) Concentrator Device Object DLC Task Description File Name $SYSTEM.
PAGE 191
SCF Commands DELETE Command The WAN manager process resolves the subvolume using this algorithm: Note. This algorithm applies only if the volume is a system disk (usually $SYSTEM). 1. First, the WAN manager process checks for the file in the current SYSnn/CSSnn. 2. If the file does not exist in the current SYSnn/CSSnn, then the WAN manager process checks for the file in the SYSTEM subvolume. 3.
PAGE 192
SCF Commands Considerations conc-name indicates the name of the SWAN concentrator. Value: The name of the SWAN concentrator as specified in the ADD ADAPTER command. Default: None provided. Wild card: You can use the asterisk (*) to specify all configured ADAPTER objects. SUB { ALL | NONE | ONLY } selects the subordinate objects the command affects. ALL specifies that the named object and the subordinate objects are affected.
PAGE 193
SCF Commands DELETE PATH Command device-name indicates the name of the DEVICE object in the configuration database and is also the name of the corresponding data-communications subsystem object. Value: The name of the data communications subsystem object as specified in the ADD DEVICE command. Default: None provided. Wild card: You can use the asterisk (*) to specify all configured DEVICE objects.
PAGE 194
SCF Commands DELETE PROCESS Command Considerations • • • You must stop any tasks that are active on the path before you can delete it. Use the STATUS PATH command to determine which tasks are active on the path. You must stop the PATH object by using the STOP PATH command before you can delete it. Only PATH objects that were added through the WAN subsystem ADD command can be deleted.
PAGE 195
SCF Commands DELETE PROFILE Command process-name indicates the name of the SNMP trap multiplexer, TFTP server, or WANBoot process. Value: The name of the process as specified in the ADD PROCESS command. Default: None provided. Wild card: You can use the asterisk (*) to specify all configured SNMP trap multiplexer, TFTP server, and WANBoot processes. Considerations • • • You must stop the process with the STOP PROCESS command before you can alter it.
PAGE 196
SCF Commands DELETE SERVER Command Considerations • • You cannot delete a profile if it is in use by a device. Determine if the profile is in use by any device using the INFO PROFILE command. Only PROFILE objects that were added with the WAN subsystem ADD command can be deleted. DELETE SERVER Command Use the DELETE SERVER command to remove a CLIP from the configuration database. The DELETE SERVER command has this syntax: DELETE SERVER $ZZWAN.#conc-name.
PAGE 197
SCF Commands INFO Command ONLY specifies that only the subordinate objects are affected. Considerations • • • You must stop any devices, paths, or tasks configured for the SERVER before you can delete the SERVER object. Issue the STOP SERVER command to stop the CLIP before you delete the SERVER object. Only SERVER objects that were added with the WAN subsystem ADD command can be deleted.
PAGE 198
SCF Commands INFO ADAPTER Command conc-name indicates the name of the SWAN concentrator. Value: The name of the SWAN concentrator as specified in the ADD ADAPTER command. Default: None provided. Wild card: You can use the asterisk (*) to specify all configured ADAPTER objects. ALTTCPIP specify this attribute to display only the alternate TCP/IP process that supports the SWAN concentrator. TCP/IP specify this attribute to display only the preferred TCP/IP process that supports the SWAN concentrator.
PAGE 199
SCF Commands INFO ADAPTER Command TrackId is the configuration track-ID configured for this SWAN concentrator. TCP/IP Name is the preferred TCP/IP process that supports this SWAN concentrator. ALTTCPIP Name is the alternate TCP/IP process that supports this SWAN concentrator. Concentrator Type is the type of concentrator. The types supported are SYNC, SWAN2, and FWCTL. Note. If a SWAN 2 concentrator is being configured, the value is SWAN 2. If SS7 DLCs are being configured, the value is FWCTL.
PAGE 200
SCF Commands INFO ADAPTER Command SUBNETMASK is the subnet mask for the SUBNET on the preferred TCP/IP process (shown in the TCP/IP Name field). ALTSUBNETMASK is the subnet mask for the SUBNET on the alternate TCP/IP process (shown in the ALTTCPIP Name field). The following display for the INFO ADAPTER command shows only the configuration track-ID for all configured SWAN concentrators. 37-> info adapter $zzwan.*,trackid WAN MANAGER Info Adapter \MYSYS.$ZZWAN.#S01 *TrackId..........
PAGE 201
SCF Commands INFO DEVICE Command INFO DEVICE Command Use the INFO DEVICE command to display the static configuration attribute values for a data communications subsystem object. The INFO DEVICE command has this syntax: INFO [ [ [ [ [ [ [ [ [ [ [ , , , , , , , , , , , OUT file-spec ] DEVICE $ZZWAN.#device-name ADAPTER ] CLIP ] DETAIL ] IOPOBJECT ] LINE ] PATH ] PROFILE ] RECSIZE ] TYPE ] OBEYFORM ] OUT file-spec causes any SCF output generated for this command to be directed to the specified file.
PAGE 202
SCF Commands INFO DEVICE Command LINE specify this attribute to display only the SWAN concentrator LINE. PATH specify this attribute to display only the SWAN concentrator PATH. PROFILE specify this attribute to display only the PROFILE object. RECSIZE specify this attribute to display only the RECSIZE attribute. TYPE for the INFO DEVICE command, specify this attribute to display only the type and subtype for the DEVICE.
PAGE 203
SCF Commands INFO DEVICE Command Profile is the PROFILE object the DEVICE is configured to use. RecSize is the RECSIZE object the DEVICE is configured to use. Preferred Cpu is the processor the DEVICE is configured to run in. Alternate Cpu is the backup processor the DEVICE is configured to run in. Type is the configured DEVICE type. MULTINAME is the MULTI attribute with which the DEVICE is configured. IOPOBJECT is the IOPOBJECT with which the DEVICE is configured.
PAGE 204
SCF Commands INFO PATH Command The format of the display for the INFO DEVICE command with the OBEYFORM option is 36-> info device $zzwan.* obeyform ADD DEVICE \IDC15.$ZZWAN.#A15 ADAPTER SWAN00 ,& CLIP 3 ,& LINE 1 ,& PATH A,& PROFILE TAEZ ,& RECSIZE 150 ,& CPU 1 ,& ALTCPU 0 ,& TYPE (61,63),& HIGHPIN ON,& IOPOBJECT $COMM.TAEZ.X25OBJ ,& ALTER DEVICE \IDC15.$ZZWAN.
PAGE 205
SCF Commands INFO PATH Command conc-name.clip-num.path-name indicates the path name. Value: The path name is the name of the SWAN concentrator, followed by the CLIP number, followed by the path name. conc-name is the name of the SWAN concentrator as specified in the ADD ADAPTER command. clip-num is the CLIP number. The possible values for the CLIP number are 1, 2, or 3 for a SWAN concentrator and 1, 2, 3, 4, 5, or 6 for a SWAN 2 concentrator. path-name is the name of the Ethernet path.
PAGE 206
SCF Commands INFO PATH Command The format of the display for the INFO PATH command is as follows: 40-> info path $zzwan.#S01.* WAN MANAGER Detailed Info Path \MYSYS.$ZZWAN.#S01.1.A *IPADDRESS ....... 172.016.035.024 WAN MANAGER Detailed Info Path \MYSYS.$ZZWAN.#S01.1.B *IPADDRESS ....... 172.016.045.024 WAN MANAGER Detailed Info Path \MYSYS.$ZZWAN.#S01.2.A *IPADDRESS ....... 172.016.035.025 WAN MANAGER Detailed Info Path \MYSYS.$ZZWAN.#S01.2.B *IPADDRESS ....... 172.016.045.
PAGE 207
SCF Commands INFO PROCESS Command INFO PROCESS Command Use the INFO PROCESS command to display the static configuration attribute values for a ConMgr, an SNMP trap multiplexer, a TFTP server, or a WANBoot process. The INFO PROCESS command has this syntax: For a ConMgr process: INFO [ , OUT file-spec ] PROCESS $ZZWAN.#cpu-num [ , IOPOBJECT ] [ , OBEYFORM ] For an SNMP trap multiplexer or a TFTP server process: INFO [ , OUT file-spec ] PROCESS $ZZWAN.
PAGE 208
SCF Commands INFO PROCESS Command IOPOBJECT specify this attribute to display only the process IOPOBJECT attribute. OBEYFORM causes the INFO command to display the information about the process in the form of ADD PROCESS commands. process-name indicates the name of the SNMP trap multiplexer, TFTP server, or WANBoot process. Value: The name of the process as specified in the ADD PROCESS command. Default: None provided.
PAGE 209
SCF Commands INFO PROCESS Command RecSize is the RECSIZE with which the PROCESS is configured. Type is the configured TYPE. Preferred Cpu is the processor the PROCESS is configured to run in. Alternate Cpu is the backup processor the PROCESS is configured to run in. HOSTIP Address indicates the IP address assigned to a SUBNET on the preferred TCP/IP process. IOPOBJECT is the IOPOBJECT with which the PROCESS is configured. TCP/IP Name is the TCP/IP process the PROCESS is configured to use.
PAGE 210
SCF Commands INFO PROFILE Command The format of the display for the INFO PROCESS command with the OBEYFORM option is : 36-> info process $zzwan.#* obeyform ADD PROCESS \MYSYS.$ZZWAN.#ZTF2 ,& TYPE ( 0,48) ,& CPU 1 ,& ALTCPU 0 ,& IOPOBJECT $SYSTEM.ZTCPIP.TFTPSRV,& TCP/IP $ZTC2 ,& STARTUP "$SYSTEM.CSS00 $system.css02" ADD PROCESS \MYSYS.$ZZWAN.#ZZPB3 TYPE ( 0,30) ,& CPU 1 ,& ALTCPU 0 ,& IOPOBJECT $COMM.JAGUAR.
PAGE 211
SCF Commands INFO PROFILE Command defined in profile-name, and modifier-value specifies a string of characters associated with the specified modifier-keyword. Value: See the manuals listed in Table 6-4 on page 6-21 for a description of the modifier keyword and modifier values that apply to each data communications subsystem. Default: None provided. OBEYFORM causes the INFO command to display the information about the profile in the form of ADD PROFILE commands.
PAGE 212
SCF Commands INFO PROFILE Command An example of the format of the display for the INFO PROFILE command (when you only want to look at specified modifiers) is 17-> info profile $zzwan.#pexfhdlc, program WAN MANAGER Info profile \MYSYS.$ZZWAN.#PEXFHDLC Devices using this profile Device.......... 1 Device.......... 2 : $XFHP0 : $XFHS0 DEVICE SPECIFIC MODIFIERS: PROGRAM C9312P00 The format of the display will vary, depending on which modifiers you specify.
PAGE 213
SCF Commands INFO SERVER Command Considerations The INFO PROFILE display does not indicate which disk file name was specified in the ADD PROFILE command. However, if you enter this command: INFO PROFILE $ZZWAN.#* the command response includes the name and contents of all PROFILE objects. If you only want to see a list of the names of all PROFILE objects, use this command instead: NAMES PROFILE $ZZWAN.
PAGE 214
SCF Commands INFO SUBSYS Command The format of the display for the INFO SERVER command is as follows: 32-> info server $zzwan.#s01.1 WAN MANAGER Info Server \IDC12.$ZZWAN.#S01.1 SERVER VERSION.... T7954G01^15JUL99^23JUN97AAB The format of the display for the INFO SERVER command with the OBEYFORM option is : 17-> info server $zzwan*,obeyform ADD SERVER \IDC15.$ZZWAN.#SWAN02.1 ADD SERVER \IDC15.$ZZWAN.#SWAN02.2 ADD SERVER \IDC15.$ZZWAN.#SWAN02.
PAGE 215
SCF Commands INFO SUBSYS Command OBEYFORM causes the INFO command to display information about the SUBSYS in the form of ADD SUBSYS commands. SUBNETLIST causes the INFO command to display SUBNET information for each process. The format of the display for the INFO SUBSYS command is as follows: 47-> info subsys $zzwan WAN MANAGER Detailed Info Subsys \MYSYS.$ZZWAN Config File....... $SYSTEM.SYSTEM.CONF IOPOBJECT......... \MYSYS.$SYSTEM.SYS01.WANMGR Config File is the current system configuration database.
PAGE 216
SCF Commands INFO TASK Command Considerations To restore the WAN configuration edit the obey file to remove the first two SCF header lines: SCF >Allow Errors >obey obeyfile This step executes a series of ADD commands found in the obeyfile. The ADD commands for each object succeed only if no two objects have the same name. INFO TASK Command Use the INFO TASK command to return information about data link control (DLC) and DIAG tasks that are running in a CLIP.
PAGE 217
SCF Commands NAMES Command PREFERREDPATH specify this attribute to display only the preferred PATH. PROGRAM specify this attribute to display only the path PROGRAM attribute. The format of the display for the INFO TASK command is as follows: 25-> info task $zzwan.#s01.3.* WAN MANAGER Detailed Info Task \MYSYS1.$ZZWAN.#S01.3.DIAG *Program.......... UNKNOWN IPPORT............ 5002 *Path............. ? WAN MANAGER Detailed Info Task \MYSYS1.$ZZWAN.#S01.3.DLC0 *Program.......... UNKNOWN IPPORT............
PAGE 218
SCF Commands NAMES DEVICE Command The format of the display for the NAMES ADAPTER command is as follows: 3-> names adapter $zzwan.#* WANMgr Names ADAPTER $ZZWAN.#* ADAPTER $ZZWAN.#S01 $ZZWAN.#S02 ADAPTER shows a list of the configured ADAPTER objects. NAMES DEVICE Command Use the NAMES DEVICE command to display a list of the names of all configured data- communications subsystem objects. The NAMES DEVICE command has this syntax: NAMES DEVICE $ZZWAN.
PAGE 219
SCF Commands NAMES PATH Command NAMES PATH Command Use the NAMES PATH command to display a list of the names of all configured paths on a SWAN concentrator. The NAMES PATH command has this syntax: NAMES PATH $ZZWAN.#conc-name.clip-num.path-name conc-name.clip-num.path-name indicates the path name. Value: The path name is the name of the SWAN concentrator, followed by the CLIP number, followed by the path name. conc-name is the name of the SWAN concentrator as specified in the ADD ADAPTER command.
PAGE 220
SCF Commands NAMES PROCESS Command NAMES PROCESS Command The NAMES PROCESS command displays a list of the names of all configured ConMgr, SNMP trap multiplexer, TFTP server, or WANBoot processes. The NAMES PROCESS command has this syntax: For a ConMgr process: NAMES PROCESS $ZZWAN.#cpu-num For an SNMP trap multiplexer, a TFTP server, or a WANBoot process: NAMES PROCESS $ZZWAN.#process-name cpu-num indicates the name of the ConMgr process by specifying the processor the ConMgr process is to run in.
PAGE 221
SCF Commands NAMES PROFILE Command The format of the display for the NAMES PROCESS command is as follows: 29-> names process $zzwan.#* WANMgr Names PROCESS $ZZWAN.#* PROCESS $ZZWAN.#0 $ZZWAN.#1 $ZZWAN.#ZTMX2 $ZZWAN.#ZF019 $ZZWAN.#ZF01D $ZZWAN.#ZW019 $ZZWAN.#ZW01D PROCESS shows a list of the configured ConMgr, SNMP trap multiplexer, TFTP server, and WANBoot processes. NAMES PROFILE Command Use the NAMES PROFILE command to display a list of the configured profiles.
PAGE 222
SCF Commands NAMES SERVER Command PROFILE shows a list of the configured profiles. NAMES SERVER Command Use the NAMES SERVER command to display a list of the configured CLIPs. The NAMES SERVER command has this syntax: NAMES SERVER $ZZWAN.#conc-name.clip-num conc-name.clip-num indicates the CLIP. Value: The SERVER name is the name of the SWAN concentrator, followed by the CLIP number. conc-name is the name of the SWAN concentrator as specified in the ADD ADAPTER command. clip-num is the CLIP number.
PAGE 223
SCF Commands NAMES SUBSYS Command NAMES SUBSYS Command Use the NAMES SUBSYS command to display the WAN manager process and all of its subordinate objects. The NAMES SUBSYS command has this syntax: NAMES SUBSYS $ZZWAN [ , SUB ALL ] SUB ALL indicates that the subordinate objects will be displayed.
PAGE 224
SCF Commands NAMES SUBSYS Command The format of the display for the NAMES SUBSYS command with the SUB ALL option is as follows: 36-> names subsys $zzwan, sub all WANMgr Names SUBSYS $ZZWAN SUBSYS $ZZWAN PROFILE $ZZWAN.#ATPPRT $ZZWAN.#ATPTERM $ZZWAN.#MLHSWAN $ZZWAN.#PATP5512 $ZZWAN.#PCP6ADCP $ZZWAN.#PEXFHDLC $ZZWAN.#PEXPNCP $ZZWAN.#PEXPSIP $ZZWAN.#PROFEVY $ZZWAN.#PX250061 $ZZWAN.#SLHIP $ZZWAN.#SLHSWAN $ZZWAN.#X25PROF PROCESS $ZZWAN.#0 $ZZWAN.#1 $ZZWAN.#ZTMX2 $ZZWAN.#ZF019 $ZZWAN.#ZF01D $ZZWAN.
PAGE 225
SCF Commands NAMES TASK Command PROCESS shows a list of the configured PROCESS objects (ConMgr, SNMP trap multiplexer, TFTP server, and WANBoot). DEVICE shows a list of the configured DEVICE objects. The following information is displayed for each configured ADAPTER object: ADAPTER shows a list of the configured ADAPTER objects. SERVER shows a list of the configured SERVER objects. PATH shows a list of the configured PATH objects. TASK shows a list of the configured TASK objects.
PAGE 226
SCF Commands NAMES TASK Command conc-name.clip-num.dlc-task indicates the task object. Value: The task name is the name of the task running on the SWAN concentrator. conc-name is the name of the SWAN concentrator as specified in the ADD ADAPTER command. clip-num is the CLIP number. The possible values for the CLIP number are 1, 2, or 3 for a SWAN concentrator and 1, 2, 3, 4, 5, or 6 for a SWAN 2 concentrator. dlc-task is the task running in a WAN port. The possible values are DLC0 or DLC1.
PAGE 227
SCF Commands PRIMARY Command PRIMARY Command PRIMARY is sensitive command that is used to change the preferred processor of the WAN manager process. The WAN manager process must have been configured to run as a NonStop process pair. The PRIMARY SUBSYS command has this syntax: PRIMARY SUBSYS $ZZWAN, CPU cpu-num CPU cpu-num indicates the new preferred processor in which the WAN manager process is to run. Value: The possible values are 0 through n. Default: None provided.
PAGE 228
SCF Commands START DEVICE Command SUB { ALL | NONE | ONLY } selects the subordinate object that the command affects. ALL specifies that the named object and the subordinate objects are affected. NONE specifies that the named object is affected but that the subordinate objects are not. NONE is the default. ONLY specifies that only the subordinate objects are affected. Considerations • • The SWAN concentrator must have been previously defined through the ADD ADAPTER, ADD SERVER, and ADD PATH commands.
PAGE 229
SCF Commands START DEVICE Command SEL [ NOT ] sumstate directs the command only at objects in the specified state or only at objects not in the specified state. Value: Valid states are STARTED, STARTING, STOPPED, and STOPPING. Default: None provided. SUB { NONE } selects the subordinate objects the command affects. NONE specifies that the named object is affected but that the subordinate objects are not. NONE is the default.
PAGE 230
SCF Commands START DEVICE Command Table 6-7. Activate Path Requests and WanMgr Requests to Download Adapter Type File Name From IOP Adapter Type Matches File Type SWAN C1094P00 Yes Download Existing. Activate Request. SWAN C1094Q00 Yes Download Irrespective of file name, if adapter type matches: download. SWAN 2 C1094P00 Yes Download Irrespective of file name, if adapter type matches: download. SWAN 2 C1094Q00 Yes Download Normal. Activate request.
PAGE 231
SCF Commands START PATH Command START PATH Command Use the START PATH command to place a path on a CLIP in the STARTED state. You can also use the OSM Service Connection or the TSM Service Application (G-series RVUs only). For more information about using OSM or TSM, see the online help within each application. The START PATH command has this syntax: START PATH $ZZWAN.#conc-name.clip-num.path-name conc-name.clip-num.path-name indicates the path name.
PAGE 232
SCF Commands START PROCESS Command The START PROCESS command has this syntax: For a ConMgr process: START PROCESS $ZZWAN.#cpu-num cpu-num indicates the name of the ConMgr process by specifying the processor the ConMgr process is to run in. The WAN subsystem names the ConMgr process $ZZWAN.nn where nn is the processor number. Value: The possible values are 0 through n. The ConMgr process name, when displayed from the WAN subsystem INFO command, is $ZZWAN.
PAGE 233
SCF Commands START SERVER Command These configuration errors occur most often during a migration to G06.13 or later RVUs. START SERVER Command Use the START SERVER command to place a CLIP in the STARTED state. You can also use the OSM Service Connection or the TSM Service Application (G-series RVUs only). For more information about using OSM or TSM, refer to the online help within each application. The START SERVER command has this syntax: START SERVER $ZZWAN.#conc-name.
PAGE 234
SCF Commands START TASK Command Considerations • • • • • The SWAN concentrator must have been previously defined through the ADD ADAPTER, ADD SERVER, and ADD PATH commands. The ADAPTER object must have been previously started through the START ADAPTER command. The START SERVER command issues a restart command to the CLIP and takes over control of the CLIP. A START SERVER command forces any other system in control of the CLIP to relinquish control.
PAGE 235
SCF Commands STATUS Command conc-name.clip-num.dlc-task indicates the task. Value: The task name is the name of the task running on the SWAN concentrator. conc-name is the name of the SWAN concentrator as specified in the ADD ADAPTER command. clip-num is the CLIP number. The possible values for the CLIP number are 1, 2, or 3 for a SWAN concentrator and 1, 2, 3, 4, 5, or 6 for a SWAN 2 concentrator. dlc-task is the task running in a WAN port. The possible values are DLC0 or DLC1.
PAGE 236
SCF Commands STATUS ADAPTER Command conc-name indicates the name of the SWAN concentrator. Value: The name of the name of the SWAN concentrator as specified in the ADD ADAPTER command. Default: None provided. Wild card: You can use the asterisk (*) to specify all configured ADAPTER objects. SUB { ALL | NONE | ONLY } selects the subordinate objects the command affects. ALL specifies that the named object and the subordinate objects are affected.
PAGE 237
SCF Commands STATUS ADAPTER Command State indicates the state of the ADAPTER object. Number of clips indicates how many CLIPs are configured for the specified ADAPTER object. Clip 1 (1-6) status indicates which CLIPS are configured for the specified ADAPTER object.
PAGE 238
SCF Commands STATUS ADAPTER Command The format of the display for the STATUS ADAPTER command with the SUB ALL option is as follows (only the detailed information for one CLIP is included in the display): 3-> status adapter $zzwan.#s01, sub all WAN Manager STATUS ADAPTER for ADAPTER State........... STARTED \MYSYS1.$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 Path A..........
PAGE 239
SCF Commands STATUS ADAPTER Command State indicates the state of the ADAPTER object. Number of clips indicates how many CLIPs are configured for the specified ADAPTER object. Clip 1 (2,3,4,5, or 6) status indicates which CLIPS are configured for the specified ADAPTER object. The following information is displayed for each configured CLIP: State indicates the state of the ADAPTER object. Path A indicates if PATH A is configured. Path B indicates if PATH B is configured.
PAGE 240
SCF Commands STATUS DEVICE Command Status of Fans indicates the status of the FANs. Status of Batteries indicates the status of the batteries. Status of Power Supply indicates the status of the power supplies. Status of LAN Paths indicates the status of the LAN paths. Status of POST indicates the status of POST (power-on-self-test). CLIP VPROC indicates the VPROC of the CLIP.
PAGE 241
SCF Commands STATUS PATH Command State indicates the state of the DEVICE object. STARTED indicates that the DEVICE process is running and an LDEV is allocated. STOPPED indicates that the DEVICE process is not running. LDEV number indicates the logical device number (LDEV) that was allocated to the DEVICE when it was started by the WAN manager process. STATUS PATH Command Use the STATUS PATH command to display current status and configuration information about a path on a CLIP.
PAGE 242
SCF Commands STATUS PROCESS Command MEDIAADDRESS specify this attribute to display only the media access control (MAC) address. The format of the display for the STATUS PATH command is as follows: 9-> status path $zzwan.#s01.1.a WAN Manager STATUS PATH for PATH State :......... STARTED \MYSYS1.$ZZWAN.#S01.1.A MEDIA TYPE...... ETHERNET MEDIA ADDRESS... %H08008E004814 STATE indicates the state of the path. STARTED indicates that the path is in the STARTED state and can be used by a task.
PAGE 243
SCF Commands STATUS PROCESS Command cpu-num indicates the name of the ConMgr process by specifying the processor the ConMgr process is to run in. The WAN subsystem names the ConMgr process $ZZWAN.nn where nn is the processor number. Value: The possible values are 0 through n. The ConMgr process name, when displayed from the WAN subsystem INFO command, is $ZZWAN.#0 for the ConMgr process configured to run in processor 0, $ZZWAN.#1 for the ConMgr process configured to run in processor 1, and so on.
PAGE 244
SCF Commands STATUS SERVER Command The format of the display for the STATUS PROCESS command (the display only includes one sample of each type of PROCESS object) is as follows: 22-> status process $zzwan.#* WAN Manager STATUS PROCESS for PROCESS State :......... STARTED LDEV Number..... 44 PPIN............ 0 ,265 \MYSYS1.$ZZWAN.#0 Process traced.. NO need snmp trap mux WAN Manager STATUS PROCESS for PROCESS State :......... STARTED PPIN............
PAGE 245
SCF Commands STATUS SERVER Command The STATUS SERVER command has this syntax: STATUS SERVER $ZZWAN.#conc-name.clip-num [ , SUB { ALL | NONE | ONLY } ] [ , DETAIL ] [, HWSTATUS ] conc-name.clip-num indicates the CLIP. Value: The SERVER name is the name of the SWAN concentrator, followed by the CLIP number. conc-name is the name of the SWAN concentrator as specified in the ADD ADAPTER command. clip-num is the CLIP number.
PAGE 246
SCF Commands STATUS SERVER Command type on one of the CLIPS. The HWSTATUS attribute is supported on the SWAN 2 concentrator only. The format of the display for the STATUS SERVER command is as follows: 15-> status server $zzwan.#s01.1 WAN Manager STATUS SERVER for CLIP State :......... STARTED \MYSYS1.$ZZWAN.#S01.1 Path A..........: CONFIGURED Path B..........: CONFIGURED Number of lines. 2 Line............ 0 Line............ 1 : $SAT23A : $SAT23B State indicates the state of the SERVER object.
PAGE 247
SCF Commands STATUS SERVER Command The format of the display for the STATUS SERVER (CLIP) command with the HWSTATUS option is as follows: 3-> status adapter $zzwan.
PAGE 248
SCF Commands STATUS TASK Command STATUS TASK Command Use the STATUS TASK command to display current status and configuration information about a DLC0 or DLC1 task. You can also use the OSM Service Connection or the TSM Service Application (G-series RVUs only). For more information about using OSM or TSM, see the online help within each application. The STATUS TASK command gets the status of the DLC/DIAG tasks from the CLIP. The STATUS TASK command has this syntax: STATUS TASK $ZZWAN.#conc-name.clip-num.
PAGE 249
SCF Commands STATUS TASK Command TCPPORT specify this attribute to display only the port number. The format of the display for the STATUS TASK command is as follows: status task $zzwan.#s01.1.* WAN Manager STATUS TASK for TASK State :........... STOPPED \MYSYS1.$ZZWAN.#S01.1.DIAG WAN Manager STATUS TASK for TASK State :........... STARTED \MYSYS1.$ZZWAN.#S01.1.DLC0 CLIP Path Name.... A TCP/IP Port used... 5000 CLIP Protocol Id.. 1 Interface Type.... 0 Clip Program...... $SYSTEM.CSS01.
PAGE 250
SCF Commands STOP Command CLIP Program indicates the download task file used by the IOP for creating the task. Program Timestamp indicates the program/binder timestamp for the download task file. STOP Command STOP is a sensitive command that is used to halt the operation of a specified object in an orderly manner. STOP ADAPTER Command Use the STOP ADAPTER command to prevent the use of all three CLIPs on a SWAN concentrator.
PAGE 251
SCF Commands STOP DEVICE Command NONE specifies that the named object is affected but that the subordinate objects are not. NONE is the default. ONLY specifies that only the subordinate objects are affected. Considerations The subordinate SERVER objects must first be placed in the STOPPED state, or the STOP ADAPTER command is rejected. STOP DEVICE Command Use the STOP DEVICE command to stop a data-communications subsystem object. The STOP DEVICE command has this syntax: STOP DEVICE $ZZWAN.
PAGE 252
SCF Commands STOP PATH Command STOP PATH Command Use the STOP PATH command to terminate the use of a path on a communications line interface processor (CLIP). The STOP PATH command places the PATH object in the STOPPED state. You can also use the OSM Service Connection or the TSM Service Application (G-series RVUs only). For more information about using OSM or TSM, see the online help within each application. The STOP PATH command has this syntax: STOP PATH $ZZWAN.#conc-name.clip-num.path-name conc-name.
PAGE 253
SCF Commands STOP PROCESS Command The STOP PROCESS command has this syntax: For a ConMgr process: STOP PROCESS $ZZWAN.#cpu-num For an SNMP trap multiplexer, a TFTP server, or a WANBoot process: STOP PROCESS $ZZWAN.#process-name cpu-num indicates the name of the ConMgr process by specifying the processor the ConMgr process is to run in. The WAN subsystem names the ConMgr process $ZZWAN.nn where nn is the processor number. Value: The possible values are 0 through n.
PAGE 254
SCF Commands STOP SERVER Command ConMgr Process • • DEVICE objects use the ConMgr process when they want to download DLC tasks to the SWAN concentrator, so this activity cannot take place when the ConMgr process that a device uses is stopped. Otherwise, device activity is not interrupted by aborting the ConMgr.
PAGE 255
SCF Commands STOP SERVER Command conc-name.clip-num indicates the server, or CLIP. Value: The SERVER name is the name of the SWAN concentrator, followed by the CLIP number. conc-name is the name of the SWAN concentrator as specified in the ADD ADAPTER command. clip-num is the CLIP number. The possible values for the CLIP number are 1, 2, or 3 for a SWAN concentrator and 1, 2, 3, 4, 5, or 6 for a SWAN 2 concentrator. Default: None provided.
PAGE 256
SCF Commands STOP TASK Command STOP TASK Command Use the STOP TASK command to terminate a DLC task. The STOP TASK command places the TASK object in the STOPPED state. You can also use the OSM Service Connection or the TSM Service Application (G-series RVUs only). For more information about using OSM or TSM, see the online help within each application. The STOP TASK command has this syntax: STOP TASK $ZZWAN.#conc-name.clip-num.dlc-task conc-name.clip-num.dlc-task indicates the task.
PAGE 257
SCF Commands VERSION Command VERSION Command VERSION is a nonsensitive command that is used to display the version level of the ConMgr process. The VERSION command has this syntax: VERSION PROCESS $ZZWAN.#cpu-num cpu-num indicates the name of the ConMgr process by specifying the processor the ConMgr process is to run in. The WAN subsystem names the ConMgr process $ZZWAN.nn where nn is the processor number. Value: The possible values are 0 through n.
PAGE 258
SCF Commands VERSION Command WAN Subsystem Configuration and Management Manual— 522463-011 6-116
PAGE 259
7 Upgrading to a SWAN 2 Concentrator Note. Throughout this manual when a distinction between a SWAN concentrator (T3880) and a SWAN 2 concentrator (T3881) is not required, SWAN concentrator is used as a collective term. This section describes considerations when upgrading to a SWAN 2 concentrator. It is intended for system managers who are planning to include a SWAN 2 concentrator in their existing configuration. WAN Subsystem Configuration Changes Starting with the G06.
PAGE 260
Upgrading to a SWAN 2 Concentrator Updating the WAN Configuration Files Updating the WAN Configuration Files This section summarizes the SCF command changes that are required to support adding a SWAN 2 concentrator to your configuration. If you do not plan to add a SWAN 2 concentrator, no changes are required. SCF Changes Required to Configure a SWAN 2 Concentrator Note. For more information about SCF commands, see Section 6, SCF Commands.
PAGE 261
A SCF Messages Note. Throughout this manual when a distinction between a SWAN concentrator (T3880) and a SWAN 2 concentrator (T3881) is not required, SWAN concentrator is used as a collective term. This appendix describes the types of Subsystem Control Facility (SCF) errors that apply to the WAN subsystem. Messages with positive error numbers are generated by the WAN subsystem. Messages with negative numbers are general SCF messages.
PAGE 262
SCF Messages WAN 00003 00003 object-type object-name is not configured Cause. A required object is not configured. This error can occur for the ADD or ALTER commands. For example, if you issue the ADD DEVICE command specifying a PROFILE that doesn’t exist, you will receive an error like this: WAN E000004 PROFILE PROFATP is not configured. Effect. The command has no effect. Recovery. Add the object specified in the error message, then retry the command.
PAGE 263
SCF Messages Recovery. Examine the command syntax in Section 6, SCF Commands. Supply the missing attribute, and retry the command. WAN 00007 00007 attribute-name value attribute-value is incorrect. explanation. Cause. The value of the specified attribute is not in the allowable range. explanation further describes the error. Effect. The command has no effect. Recovery. Examine the command syntax in Section 6, SCF Commands. Correct the attribute value, and retry the command.
PAGE 264
SCF Messages Recovery. Use the STOP or ABORT command first. When the specified object is in the stopped state, retry the DELETE command. WAN 00011 00011 Error returned from proc-name : error-code, explanation. Cause. The WAN manager process received the specified error-code in response to a message sent to the ConMgr or WANBoot processes. explanation further describes what is wrong with the specified error-code. Effect. The command has no effect. Recovery. Contact your service provider.
PAGE 265
SCF Messages Recovery. Reissue the command with a unique attribute name and value combination. You can use the appropriate INFO command to determine which object is using the specified attribute name and value combination.
PAGE 266
SCF Messages WAN 00017 00017 object-type object-name is not in summary state. Cause. The specified object is not in the specified summary state. Effect. The command has no effect. Recovery. Place the specified object mentioned in the specified state, and retry the command. WAN 00018 00018 Error while [ START | STOP ] ing object-type object-name. Cause. The WAN manager process is unable to start or stop the specified object.
PAGE 267
SCF Messages Effect. The command has no effect. Recovery. Change the object name or delete the object from the subsystem that owns it, and retry the command. You can determine the owner by using the TACL PPD command. For example, if the object name you specified was $Z06P: 5> ppd $Z06P Name Primary Backup $Z06P 0,313 Ancestor $ZZSTO The command response shows that the Storage subsystem ($ZZSTO) owns the process. WAN 00021 00021 Error error-number occurred while reserving the name.
PAGE 268
SCF Messages WAN 00023 00023 device-name Abort/Stop the line before STOPPING the process-name. Cause. The communications line must be stopped before stopping the indicated device-name. Effect. The command has no effect. Recovery. Stop or abort the line, then stop the device. WAN 00024 00024 object-name object-type Not Responding to the command-name Request. Cause. The indicated object did not respond to a STOP request from the WAN manager process. Effect. The command has no effect. Recovery.
PAGE 269
SCF Messages WAN 00027 00027 object-name procedure-name returned Error: errornumber, Error Detail: error-detail Cause. Both PROFILE and LIKE cannot be specified while adding the device. Effect. The command has no effect. Recovery. Add the device by specifying the PROFILE or LIKE attribute. WAN 00028 00028object-name procedure-name returned Error: error-number, Error Detail: error-detail Cause. Error reading in configured SERVER file. The file may not exist or have the wrong format. Effect.
PAGE 270
SCF Messages WAN 00030 00030 FILE: file name file code is invalid. Valid file codes are:file-code(s) Cause. A mismatch was found in the filecode of the file in the command. Valid filecodes for adding or altering a device, process, task, or profile are as follows: Object-Type Valid Filecodes DEVICE 100 & 700 PROCESS 100 PROFILE 832 TASK 510 Effect. The command has no effect. Recovery. Verify that the filecode matches the allowable filecodes, then retry the command.
PAGE 271
SCF Messages Recovery. Check the type of the device and also its name before adding again. Only numeric ConMgr names can be configured as type 50. WAN 00034 00034 The preferred HostIp pref-hostip is already configured with different TCP/IP tcpip-name Cause. The specified HostIp has already been configured by another TCP/IP. The TCP/IP and the HostIp combination within the system must be unique. This error can occur for the ADD or ALTER commands. Effect. The command has no effect. Recovery.
PAGE 272
SCF Messages WAN 00037 00037 No adapters are configured for the HOSTIP hostip Cause. The process is added with a HOSTIP to which none of the adapters are configured. This error can occur for the ADD or ALTER commands. Effect. The command has no effect. Recovery. Add an adapter with process' hostip or DELETE the process. WAN 00038 00038 The specified HOSTIP hostip is already configured with another process proc-name Cause. The specified HOSTIP has already been configured with another process .
PAGE 273
SCF Messages WAN 00041 00041 Error while STARTing PROC-NAME Cause. The WAN manager process is unable to start the specified process because of an internal error. This error might have occurred due to one of these errors: Internal-error Explanation 0000001 NO ADAPTER CONFIGURED FOR THE HOSTIP 0000002 NO HOSTIP CONFIGURED 0000003 ANOTHER PROCESS IS ALREADY CONFIGURED FOR THE HOSTIP Effect. The command has no effect. Recovery.
PAGE 274
SCF Messages WAN 00045 00045 Adapter(s) TYPE cannot be alterred from SYNC/ASYNC/FWCTL to SWAN2 or vice versa Cause. The specified adapter TYPE configured as SYNC/ASYNC/FWCTL was altered to SWAN 3881 or vice versa. This error can occur for the ALTER command. Effect. The command has no effect. Recovery. No recovery is necessary. WAN 00046 00046 KERNELCODE does not match with the Adapter(s) TYPE Cause. The specified KERNELCODE does not match with the adapter TYPE. This error can occur for the ALTER command.
PAGE 275
SCF Messages WAN 00049 00049 The IOPOBJECT, PROGRAM, SNMPCODE, and ESSENTIALCODE cannot be on a remote node. Cause. The WANMgr process is unable to launch a process on a remote machine. Effect. The configuration of a concentrator, device, process, profile, and task failed. Recovery. Use IOPOBJECT, PROGRAM, SNMPCODE, and ESSENTIALCODE available in the current node. WAN 00500 00500 Duplicate attribute: attribute-name. Cause. The specified attribute has been included more than once in the command. Effect.
PAGE 276
SCF Messages Recovery. Examine the command syntax in Section 6, SCF Commands. Include the required attribute, and retry the command. WAN 00504 00504 Invalid value for attribute: attribute-name. Cause. The value of the specified attribute is not in the allowable range. Effect. The command has no effect. Recovery. Examine the command syntax in Section 6, SCF Commands. Correct the attribute value, and retry the command. WAN 00505 00505 Invalid object name Cause. The syntax of the object name is invalid.
PAGE 277
SCF Messages WAN 00508 00508 Too many values given Cause. Too many values were included in the command syntax. Effect. The command has no effect. Recovery. Examine the command syntax in Section 6, SCF Commands. Remove the extra values, and retry the command. WAN 00509 00509 Attribute attribute-name is invalid Cause. The specified attribute is not valid for the specified command. Effect. The command has no effect. Recovery. Examine the command syntax in Section 6, SCF Commands.
PAGE 278
SCF Messages WAN Subsystem Configuration and Management Manual— 522463-011 A-18
PAGE 279
B Sample Router Configuration Example B-1 on page B-2 illustrates a sample router configuration connecting a Cisco router to a SWAN concentrator. Note. This sample is a vendor configuration and has not been tested by HP Computers. Assumptions For the sample router configuration, we have made these assumptions: • • • Two NonStop S-series servers are located in networks NSK1 and NSK2. SWAN concentrators are located in networks SWAN1 and SWAN2. A Cisco router is being used with an IOS greater than 10.0.
PAGE 280
Sample Router Configuration Configuration Steps Example B-1. Sample Router Configuration ! Partial Cisco Router Config which highlights only the changes required. ! Assumptions: ! NSK1 network is 192.168.10.0 ! NSK2 network is 192.168.11.0 ! SWAN1 network is 192.168.12.0 ! SWAN2 network is 192.168.13.0 ! Enable ip forwarding of all bootpc and bootps packets ip forward protocol udp bootpc ip forward protocol udp bootps ! ! Config of NSK1 interface int ethernet 0 ip address 192.168.10.1 255.255.255.
PAGE 281
Index A ABORT ADAPTER command 6-7 ABORT PATH command 6-8 ABORT PROCESS command 6-9 ABORT SERVER command 6-11 ABORT TASK command 6-12 ADAPTER object altering 5-6, 6-28 configuring 4-19, 5-4, 6-13 deleting 5-5, 6-49 displaying information about 5-1, 6-55, 6-75 displaying the state of 1-20, 6-93 general description of 6-3 starting 1-24, 4-22, 5-8, 6-85 stopping 5-7, 6-7, 6-108 ADD ADAPTER command 6-13 ADD DEVICE command 6-19 ADD PATH command 6-23 ADD PROCESS command 6-24 ADD PROFILE command 6-26 ADD SERVER com
PAGE 282
Index D ConMgr processes altering 5-6, 6-37 configuring 4-18, 5-4, 6-24 deleting 5-5, 6-52 displaying information about 5-1, 6-65, 6-78 displaying the state of 1-18, 5-2, 6-100 displaying version level of 5-3, 6-115 general description of 2-5 starting 1-22, 5-8, 6-89 stopping 5-8, 6-9, 6-110 CP6100 description 2-1 D Data communications subsystems changing objects for 5-6, 6-34 defining objects for 5-4 displaying information about objects for 5-1, 6-59, 6-76 displaying the state of objects for 5-2, 6-98 r
PAGE 283
Index G G G4SA naming convention for 1-5 Gigabit Ethernet 4-port ServerNet adapter (G4SA) 1-2 naming convention 1-3 Gigabit Ethernet ServerNet adapter (GESA) 1-2 naming convention 1-3 Line speeds, SWAN 2 concentrator 2-23 LISTNER process naming convention for (G-Series) 1-5 naming convention for (H-Series) 1-7 Logical interfaces (LIFs) displaying configured 4-5 general description of 4-4 naming convention for 1-3 Logical states 6-5 H M HP NonStop TCP/IP processes, reconfiguring 3-12 MAC addresses ass
PAGE 284
Index O O Obeyform support 6-6 Objects, WAN subsystem general description of 6-2 states of 6-5 Operator messages 5-3 P PATH object altering 5-6, 6-36 configuring 4-21, 5-4, 6-23 deleting 5-5 displaying information about 5-1, 6-62, 6-77 displaying the state of 1-20, 5-2, 6-99 general description of 6-3 starting 1-24, 4-22, 5-8, 6-89 stopping 5-7, 6-8, 6-110 Path switching, SWAN and SWAN 2 concentrator 2-14, 2-30 Physical interface (PIF) 4-4 PMF Ethernet adapter CRU naming convention for 1-5 Ports on a SWA
PAGE 285
Index S SERVER object displaying information about 5-2, 6-71, 6-80 displaying the state of 1-20, 5-2, 6-102 general description of 6-3 starting 1-24, 4-22, 5-8, 6-91 stopping 5-7, 6-11, 6-112 SNAX/APN description 2-2 SNAX/XF description 2-2 SNMP agent processes displaying the state of 1-18 naming convention for 1-3, 1-7 SNMP trap multiplexer processes altering 5-6, 6-38 configuring 5-4 deleting 5-5, 6-52 displaying information about 5-1, 6-65, 6-78 displaying the state of 1-18, 5-2, 6-100 general descript
PAGE 286
Index T SWAN 2 concentrator (T3881), DLC microcode files 6-48 SWAN 2 firmware file 2-29 SWAN and SWAN 2 concentrator difference between 2-30 multi-system configuration 2-17 path switching 2-14, 2-30 reconfiguring Ethernet ports 3-6/3-10 WAN line configuration 3-4 WAN ports, reconfiguring 3-4 SWAN concentrator (T3880) architecture 2-7/2-17 components 2-7/2-17 DLC microcode files for 6-47 firmware file, contents of 2-13 line speeds supported 2-9 power requirements 2-8 protocols supported 2-8, 2-9 updating f
PAGE 287
Index V V Versatile I/O (VIO) enclosure and G4SA SLSA ADAPTER Type 1-2 Integrity NonStop NS-Series Server connection 2-25 number supported 4-4 planning LAN operations for 4-2 supported LAN adapters 1-2 VERSION PROCESS command 6-115 W WAN driver software 2-13 WAN LB See CLIP WAN line configuration changing initial 3-4 initial 1-17 WAN manager process altering 5-7 changing the preferred processor for 5-9, 6-85 configuring 5-4 deleting 5-5 displaying information about 5-2, 5-3, 6-72 displaying the state of
PAGE 288
Index X WAN Subsystem Configuration and Management Manual— 522463-011 Index-8