ATM Configuration and Management Manual Abstract This manual describes how to configure, operate, and manage the ATM subsystem on an HP NonStop™ S-series server. The manual includes descriptions of the Subsystem Control Facility (SCF) commands used with the ATM subsystem and a quick-reference section showing the command syntax. Product Version ATM G06 Supported Release Version Updates (RVUs) This manual supports G06.21 and all subsequent RVUs until otherwise indicated in a new edition.
Document History Part Number Product Version Published 126059 ATM G06 May 1998 422840-001 ATM G06 June 1999 522307-001 ATM G06 November 2001 522307-002 ATM G06 September 2003 522307-003 ATM G06 March 2004
ATM Configuration and Management Manual Glossary Index What’s New in This Manual ix Manual Information ix New and Changed Information Figures Tables ix About This Manual xi Who Should Use This Manual xi What’s in This Manual xi Where to Get More Information xii Notation Conventions xii Abbreviations xvii 1.
2. Overview of the ATM Subsystem (continued) Contents 2. Overview of the ATM Subsystem (continued) Driver/Interrupt Handler (DIH) 2-9 ATM ADAPTER 2-10 Interim Local Management Interface (ILMI) ATM ATMSAPs 2-11 ATM LINE 2-11 ATM NULL 2-11 ATM PVC 2-11 ATM SUBSYS 2-11 ATM SVC 2-12 2-10 3.
4. SCF Commands Contents 4.
4. SCF Commands (continued) Contents 4.
4. SCF Commands (continued) Contents 4. SCF Commands (continued) STATUS Command 4-80 STATUS ADAPTER Command 4-80 STATUS ATMSAP Command 4-84 STATUS LINE Command 4-85 STATUS PROCESS Command 4-87 STATUS PVC Command 4-91 STATUS SUBSYS Command 4-92 STATUS SVC Command 4-96 TRACE Command 4-97 TRACE ADAPTER Command 4-98 TRACE PROCESS Command 4-101 TRACE SUBSYS Command 4-104 VERSION Command 4-107 VERSION ADAPTER Command 4-107 VERSION PROCESS Command 4-108 VERSION SUBSYS Command 4-110 A. SCF Command Summary B.
B. ATM Event Messages (continued) Contents B. ATM Event Messages (continued) 603 604 605 606 607 608 609 610 700 701 800 801 1000 1001 1006 1200 1201 1300 1400 1500 1501 1600 1700 1801 1802 1803 1804 1805 1806 1807 1900 1901 1902 1903 B-17 B-19 B-21 B-22 B-23 B-26 B-27 B-28 B-29 B-30 B-31 B-32 B-33 B-33 B-34 B-35 B-36 B-36 B-37 B-39 B-39 B-40 B-41 B-42 B-43 B-44 B-45 B-47 B-48 B-49 B-50 B-51 B-52 B-54 C.
D. ATM Error Codes Contents D. ATM Error Codes ATM Driver Error Codes D-1 ATM Signaling Error Codes D-3 ATM API Error Codes D-3 ATM Network Error Code D-5 Glossary Index Figures Figure 2-1. Figure 2-2. Figure 2-3. Figure 2-4. Figure 2-5. Figure 2-6. Figure 2-7. Figure 3-1. Figure 4-1. Figure 4-2. Figure 4-3.
Contents ATM Configuration and Management Manual—522307-003 viii
What’s New in This Manual Manual Information ATM Configuration and Management Manual Abstract This manual describes how to configure, operate, and manage the ATM subsystem on an HP NonStop™ S-series server. The manual includes descriptions of the Subsystem Control Facility (SCF) commands used with the ATM subsystem and a quick-reference section showing the command syntax. Product Version ATM G06 Supported Release Version Updates (RVUs) This manual supports G06.
What’s New in This Manual • ° New and Changed Information Examples on page 3-9 Corrected the ASM Process in Task 2: Creating the ASM Process on page 1-2.
About This Manual This manual describes how to configure, operate, and manage the ATM subsystem on a NonStop S-series server. The manual includes detailed descriptions of the SCF commands used with the ATM subsystem and a quick-reference section showing the command syntax. Who Should Use This Manual This manual is written for anyone who is responsible for installing, configuring, managing, or monitoring the ATM subsystem on a NonStop S-series server. Note.
Where to Get More Information About This Manual Where to Get More Information Depending on the tasks you are performing, you might need the following manuals: • • • • • OSM Migration Guide OSM User’s Guide QIO Configuration and Management Manual TCP/IPv6 Configuration and Management Manual TSM Online User Guide Notation Conventions Hypertext Links Blue underline is used to indicate a hypertext link within text.
General Syntax Notation About This Manual [ ] Brackets. Brackets enclose optional syntax items. For example: TERM [\system-name.]$terminal-name INT[ERRUPTS] A group of items enclosed in brackets is a list from which you can choose one item or none. The items in the list can be arranged either vertically, with aligned brackets on 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.
Notation for Messages About This Manual Item Spacing. Spaces shown between items are required unless one of the items is a punctuation symbol such as a parenthesis or a comma. For example: CALL STEPMOM ( process-id ) ; If there is no space between two items, spaces are not permitted. In this example, no spaces are permitted between the period and any other items: $process-name.#su-name Line Spacing.
Notation for Messages About This Manual Bold Text. Bold text in an example indicates user input typed at the terminal. For example: ENTER RUN CODE ?123 CODE RECEIVED: 123.00 The user must press the Return key after typing the input. Nonitalic text. Nonitalic letters, numbers, and punctuation indicate text that is displayed or returned exactly as shown. For example: Backup Up. lowercase italic letters. Lowercase italic letters indicate variable items whose values are displayed or returned.
Notation for Management Programming Interfaces About This Manual % Percent Sign. A percent sign precedes a number that is not in decimal notation. The % notation precedes an octal number. The %B notation precedes a binary number. The %H notation precedes a hexadecimal number.
Abbreviations About This Manual Abbreviations The following list defines abbreviations and acronyms used in this manual. Both industry-standard terms and HP terms are included. Because this list covers ATM subsystem as a whole, not all of the terms given here are used in this particular manual. AAL. ATM Adaptation Layer AMP. ATM Management Process API. Application Program Interface ARP. Address Resolution Protocol ASM. ATM Subsystem Manager ATM.
Abbreviations About This Manual LLC. Logical Link Control MAC. Media Access Control MIB. Management Information Base NNI. Network-Node Interface NSAP. Network Service Access Point PIN. Process Identification Number PPD. Process-Pair Directory PVC. Permanent Virtual Circuit RFC. Request for Comment SAP. Service Access Point SAR. Segmentation and reassembly SCF. Subsystem Control Facility SCP. Subsystem Control Point SDU. Service Data Unit SLSA . ServerNet LAN Systems Access SM.
Abbreviations About This Manual VCI. Virtual Channel Identifier VP. Virtual Path VPI. Virtual Path Identifier WAN.
Abbreviations About This Manual ATM Configuration and Management Manual— 522307-003 xx
1 Configuration Quick Start This section is a configuration quick start for the ATM subsystem. This procedure explains how to set up the initial ATM processes, objects, and adapters on a NonStop S-series server. To help you complete the configuration tasks quickly, this section recommends you accept the default values provided by the ATM subsystem.
Task 1: Logging On to the NonStop S-Series Server Configuration Quick Start Task 1: Logging On to the NonStop S-Series Server Log on to the NonStop S-series server using the super ID (SUPER.SUPER) and enter the correct password at the Password: prompt. > logon super.super Password: Task 2: Creating the ASM Process To add the ASM process to the ATM subsystem: 1. Use the SCF ADD PROCESS command to add the PROCESS to the ATM subsystem. -> add process $zzkrn.#zzatm, & name $zzatm, & program $system.system.
Task 3: Adding an Adapter Configuration Quick Start Task 2 is required only when you configure the ATM subsystem for the first time. Task 3: Adding an Adapter To add an adapter to the ATM subsystem: 1. Fill out a configuration form for the adapter as described in Section 3, Configuring the ATM Subsystem. 2. Install the adapter in the system. For more information on how to install an ATM3SA ServerNet adapter, see the ATM Adapter Installation and Support Guide. 3.
Task 6: Starting the ATMSAP Object Configuration Quick Start Task 6: Starting the ATMSAP Object The ATMSAP object must be started to complete your ATM subsystem configuration. Note. The LINE and ATMSAP objects are created automatically by the ASM. To start the ATMSAP object, use the SCF START ATMSAP command. ->START ATMSAP $AM1.#IP Task 7: Adding the Permanent Virtual Circuit (PVC) Object The PVC object must be added using the SCF ADD PVC command. 1.
2 Overview of the ATM Subsystem The ATM subsystem provides access to ATM networks from a NonStop S-series server. The ATM subsystem supports the ATM User-Network Interface (UNI) specification over a 155Mbps OC-3 Synchronous Optical Network (SONET) connection. The Asynchronous Transfer Mode (ATM) Protocol The ATM protocol is a packet-switched, broadband network architecture that uses a cell-relay mechanism for transmitting data, voice, and video information. ATM is organized into layers and planes.
The Asynchronous Transfer Mode (ATM) Protocol Overview of the ATM Subsystem The layers are: Physical Layer Corresponds to layer 1 of the seven layer OSI reference model. This layer handles bit-timing and checks the validity of cells created and transmitted. ATM Layer Creates cell headers and trailers, defines virtual channels and paths – and gives them unique identifiers, and multiplexes or demultiplexes cells. This layer is service-independent.
ATM Cells Overview of the ATM Subsystem The UNI connects an end user to the network through an ATM switch or other device, thus supplying network access to the end user. The NNI connects nodes within a network to each other and provides network routing. ATM Cells ATM cells consist of a 5-octet header and 48-octet data or payload section. The 48-octet payload is a SAR protocol data unit (SAR PDU) to which the header is attached. Most of the bits in the header are used for path and channel identification.
Overview of the ATM Subsystem ATM Standards Supported ATM Standards Supported • • ATM UNI Specification: ATM forum Version 3.0 and Version 3.
System-Level Processes and Libraries Overview of the ATM Subsystem Figure 2-2 shows the relationship between the elements of the ATM subsystem. These elements are described in the following subsections. Figure 2-2. ATM Subsystem Architecture QIO Subsystem TCP/IP AMP ASM ATM Drivers and DIH ServerNet SAN Adapter SVC PVC Adapter SVC PVC VST202.
ATM Clients Overview of the ATM Subsystem QIO API clients are protocol subsystems that communicate with the ATM service provider directly through QIO.
ATM Subsystem Manager (ASM) Overview of the ATM Subsystem Note. Programmatic management of the ATM subsystem through the Subsystem Programmatic Interface (SPI) is not supported The SCF objects for the ATM subsystem consist of manager and monitor processes and several other objects that correspond to components of the ATM adapters that connect the ATM network to the server. The process and monitor objects correspond to the processes that manage (ASM) and monitor (AMPs) the ATM subsystem through SCF.
ATM Manager Process (AMP) Overview of the ATM Subsystem • • • Accepts all Distributed Systems Management (DSM) requests from the SCF product module through the Subsystem Control Point (SCP) Starts each manager process (AMPs) in each processor and maintains each process persistently across failures Handles the assignment of ADAPTERs to specific AMP processes Figure 2-5.
Driver/Interrupt Handler (DIH) Overview of the ATM Subsystem AMP names are defined by $ZZATM. The AMP name is composed of the letter Z followed by the adapter name and one hexadecimal digit between 1 and F (identifies the processor number in which the AMP is running). For example, $ZAM11. Figure 2-6.
ATM ADAPTER Overview of the ATM Subsystem Figure 2-7. Driver/Interrupt Handler (DIH) CPU 0 CPU 1 TCP/IP TCP/IP AMP QIO Subsystem QIO Subsystem AMP ATM Drivers and DIH ATM Drivers and DIH ServerNet SAN Adapter VST207.vsd ATM ADAPTER The ADAPTER object represents an ATM3SA adapter. One ADAPTER object is specified for each ATM adapter. The ADAPTER object is created using the SCF ADD ADAPTER command.
Overview of the ATM Subsystem ATM ATMSAPs ATM ATMSAPs The ATMSAP object represents a service access point (SAP) for native-mode clients. Native-mode clients, such as TCP/IP, register to the service-access points. ATMSAP objects are created by the subsystem after the ADAPTER has been started. Currently, the only ATMSAP object is #IP. ATMSAP names have the form $line-name.#ATMSAP-name, where $line-name is the name of the ATM logical line. #ATMSAP-name is the name of the ATMSAP.
Overview of the ATM Subsystem ATM SVC The name of the subsystem manager is $ZZATM. ATM SVC The SVC object represents a switched virtual circuit. SVCs are created when an ATM circuit is established. SVC names have the format $line-name. #atmsap-name.svc-name. $line-name is the name of the ATM line to whom the SVC is subordinate. $atmsap-name is the name of the SAP to which service is being provided. svc-name is the name assigned by the adapter to identify the circuit. For example: $AM1.#IP.SVC00001 Note.
3 Configuring the ATM Subsystem This section describes the configuration of the ATM subsystem on a NonStop S-series server. It also describes the prerequisites to getting started and provides a configuration quick start that takes you through each step of the configuration. For information on configuring TCP/IP over the ATM subsystem, see the TCP/IPv6 Configuration and Management Manual.
Configuring the ATM Subsystem Configuration Forms 6. Check that the $ZNET subsystem manager process is started. $ZNET configures the SCP management process. 7. Check that the QIO subsystem is started. QIO is preconfigured and started during the system-load sequence as a generic process. Generic processes are part of the SCF Kernel subsystem ($ZZKRN). For more information about generic processes, see the SCF Reference Manual for the Kernel Subsystem.
Configuration Forms Configuring the ATM Subsystem Figure 3-1. ATM3SA Configuration Form (sample entries) ATM ServerNet Adapter (ATM3SA) Configuration Form System Name Date Group ATM ATM Address: ServerNet ATM Adapter Adapter Name: $AM1 LINE Name: $AM1 01 Module 01 \Case1 05/15/98 Slot 53 h4700dd01272b4a00000000000000000000000100 SAC Access List: 0, 1, 2, 3 VST301.
Configuring the ATM Subsystem Configuration File Configuration File You can use a TACL macro to configure the ATM subsystem or use SCF interactively. The following TACL macro configures and starts an ATM3SA adapter. For the SCF steps, see Configuration Quick Start on page 3-5.
Configuration Quick Start Configuring the ATM Subsystem Configuration Quick Start To configure ATM ServerNet connections: Task Tool Used Step 1: Create and Start the ASM Process on page 3-5. SCF interface to the Kernel subsystem Step 2: Create and Start the ATM Adapter on page 3-10. SCF interface to the ATM subsystem Step 3: Configure the ATM Address and Start the Line on page 3-14.
Configuring the ATM Subsystem ADD PROCESS Command $ZZKRN.#gpname specifies the name of the generic process controlled by the Kernel subsystem manager process ($ZZKRN). AUTORESTART n optionally specifies the number of times that the $ZPM persistence manager tries to restart this process within a 10-minute interval after an abnormal termination. (For example, the process abends or stops by a means other than the ABORT command.) If n is 0 (the default), the process is not automatically restarted.
Configuring the ATM Subsystem ADD PROCESS Command INFILE {$device | [[$vol.]subvol.]filename } optionally specifies the input file or process name sent to this process (in the startup message) when it is started. NAME $ZZATM specifies the process name of this process, as recognized by TACL. This attribute is required. The length limitation is six characters.
Configuring the ATM Subsystem START PROCESS Command OFF specifies that a saveabend file is not created automatically if the process ends abnormally. STARTMODE { KERNEL|SYSTEM|APPLICATION|MANUAL|DISABLED } specifies when the process is started. KERNEL specifies that the process is started early during system load or processor reload. The value must be KERNEL. STARTUPMSG "text" optionally specifies a text message to be sent to the $ZPM persistence manager when the generic process is started.
Verifying the ASM Process Configuring the ATM Subsystem Verifying the ASM Process To make sure the ASM process has started successfully, enter the following command at the TACL prompt: -> STATUS SUBSYS $ZZATM If the ASM process was started successfully, you will see a display similar to: -> STATUS SUBSYS $ZZATM ATM Status $ZZATM Name State PID Pri Trace $AM201 STARTED 1, 21 180 OFF If the ASM process was not started successfully, the following message appears: (Process does not exist) Examples
Configuring the ATM Subsystem Step 2: Create and Start the ATM Adapter Step 2: Create and Start the ATM Adapter Each ATM adapter on a NonStop S-series server must be created and started using the SCF interface to the ATM subsystem. The adapters must be created and started by using the SCF ADD ADAPTER and START ADAPTER commands ADD ADAPTER Command To create an ADAPTER object, use the ATM subsystem SCF ADD ADAPTER command.
Configuring the ATM Subsystem ADD ADAPTER Command ACCESSLIST cpu-list specifies the CPUs from which the adapter is made accessible. The list may consist of a single CPU number, a list of CPU numbers separated by commas enclosed in parenthesis, or the keyword ALL indicating the adapter is accessible from all CPUs in the system. For each CPU specified in the list, an AMP process is created to run in the CPU. This attribute is required.
Configuring the ATM Subsystem ADD ADAPTER Command AUTOFIRMUP { ON | OFF } specifies whether the adapter firmware is automatically updated with the newer firmware. An ON value indicates the adapter software is automatically updated if the version of the firmware in the file specified by the FIRMWFILENAME attribute is newer than the version of the firmware file name or the name of the default file currently running on the adapter.
Configuring the ATM Subsystem Example SYSNAME string specifies the system name. The string specified must be in the range 0 through 256. This attribute is for informational purposes only. Default: blanks. SYSOBJID string specifies the vendor’s authoritative ID of the Network Management subsystem contained in the entity. The string specified must be in the range 0 through 256. This attribute is for informational purposes only. Default: blanks.
Configuring the ATM Subsystem START ADAPTER Command START ADAPTER Command To start the ADAPTER, use the ATM subsystem SCF START ADAPTER command: START ADAPTER $AM1 ADAPTER adapter-name specifies the adapter you want to start. Example The following command starts the adapter: -> START ADAPTER $AM1 Step 3: Configure the ATM Address and Start the Line Configuring the ATM address is optional.
Configuring the ATM Subsystem ALTER LINE Command LINE line-name specifies the name to be assigned to the line. The ATM LINE name is defined by the adapter name. ATMADDRESS atm-address specifies the address for ISONSAP is a 40 hexadecimal digit. The AFI (first two digits) value must be %h39, %h45, and %h47. The address for E164 is 20 digits. For example, the format for the ATM address must be: ATMADDR (isonsap:%h4700dd01272b4a00000000000000000000000100) Default: Resets the address to all 0s.
Configuring the ATM Subsystem ALTER LINE Command MAXVCIBITS digit specifies the address width and the maximum number of VCI bits that can be active for this interface. Value: 0 through 16. Default: 10. UMECOMMUNITY community-name specifies the UNI community name for the management entity. The community name is specified as a text string enclosed in parenthesis. The value specified must be in the range 0 through 255. Default: “ ”. UMEVPI digit specifies the UME virtual path ID. Value: 0 through 255.
Configuring the ATM Subsystem START LINE Command START LINE Command The START LINE command initiates the operation of the LINE object. When the subsystem has successfully completed processing this command, the LINE object is placed in the STARTED summary state. If the ATM address was not previously specified, the address will be created during the START LINE process.
Configuring the ATM Subsystem Step 4: Start the ATMSAP Object Step 4: Start the ATMSAP Object Start the ATMSAP object to complete your ATM ServerNet configuration. You can issue the SCF START ATMSAP command or start the ATMSAP object by using the START LINE command with the SUB ALL option. For more information on using this command, see Section 4, SCF Commands. Note. The LINE and ATMSAP objects are created automatically by the ASM.
Configuring the ATM Subsystem Example PVC pvc-name specifies the name of the PVC. The pvc-name is associated with the ATMSAP name. Pvc-name is the name assigned by the adapter to identify the circuit. The pvc-name consists of up to eight alphanumeric characters with a leading alphabetic character; for example, $AM1.#IP.PVC0. VPI { 0-255 } specifies the virtual path identifier (VPI). Value: 0 through 255. Default: Required. VCI { 32-3071 } specifies the virtual circuit identifier (ID).
Configuring the ATM Subsystem ATM Configuration and Management Manual— 522307-003 3- 20 Example
4 SCF Commands This section describes the following topics: • • • • • An overview of the SCF features and operation, and of the objects on which SCF operates A general description of the SCF interface to the ATM subsystem The SCF commands supported by the ATM subsystem and the object types supported for each command Sensitive and nonsensitive commands The following detailed information about each SCF command: ° ° ° ° A description of the command function The command syntax, including the supported obj
Overview SCF Commands Figure 4-1. SCF and SCP Overview Terminal Application Process SCF SCF Command File Log File SCP ($ZNET) $ZZATM VST401.vsd The default SCP process, known to the system as $ZNET, is a generic process that provides access for application programs (local or remote) to monitor and control a SCF subsystem. If $ZNET is not running, SCF starts its own SCP process (which is removed from the system when SCF is stopped). SCF automatically opens and closes the SCP.
Subsystem Control Point (SCP) SCF Commands Subsystem Control Point (SCP) SCP is a network management process for receiving and redistributing the messages that SCF sends to its subsystems. SCP provides security, version control, and tracing support for many of these subsystems. SCP is used interactively. The interactive interface (using SCF) allows you either to let a person perform an action or to automate the action. The interactive interface is described in this section under How SCF Works on page 4-4.
How SCF Works SCF Commands Several commands are available for displaying and changing SCF session parameters. For example, the SYSTEM and VOLUME commands control the default system, volume, and subvolume names used for expanding file names. The OBEY and OUT commands control the files used for command input and display output. The ASSUME command defines a default object to be used when the object is omitted from an SCF command. You can use the HELP command in several ways.
SCF Objects SCF Commands SCF performs most commands in the following sequence: 1. When SCF receives a command, it interprets the command and performs the necessary steps to execute it. Some commands can be handled by SCF with no interaction with SCP (for example, VOLUME and OUT). 2. If the command involves control or configuration of an object or a request for information about an object, SCF produces an SPI message that describes the object and the operation to be performed on it.
General SCF Command Format SCF Commands General SCF Command Format An SCF command always begins with a keyword identifying the command (such as, START, VOLUME, or TRACE). The keyword is followed by the object type and the object name. Specific information about the format of each SCF command is described later in this section.
SCF Object States SCF Commands SCF Object States Objects have operational states, such as STOPPED or STARTED. The exact sequence of states that an object goes through varies from object to object and from subsystem to subsystem. Some subsystem commands recognize only a few states. States are described in the SCF Reference Manual for G-Series RVUs. The operational state of an object at a given instant is important.
Running SCF SCF Commands run-option is one or more of the following RUN options, separated by a comma: CPU num specifies the number of the processor in which SCF is to execute. The variable num is an integer in the range 0 through 15. If you omit this option, SCF executes in the same processor as TACL. (However, if you omit the CPU option and a $CMON process exists, $CMON may specify a processor other than the one in which the current TACL process is executing.
Running SCF SCF Commands NOWAIT specifies that TACL does not wait while the program runs. TACL sends the startup message to the new process and returns its command input prompt so you can do other work while SCF runs in noninteractive mode. If you omit this option, TACL pauses until SCF completes the command string. OUT [ listfile ] specifies a file code 101 edit-type output file for the SCF process.
Ending an SCF Session SCF Commands $process is the name of an existing SCP process. This action is equivalent to opening an SCP process using the SCF OPEN command (described in the SCF Reference Manual for G-Series RVUs). You can use this parameter if you want communication with an SCP process other than the $ZNET default SCP process. command is any valid SCF command described in the SCF Reference Manual for G-Series RVUs. Consideration Do not specify HIGHPIN as an SCF run option.
Modes of Operation SCF Commands The following methods of using SCF are examples of interactive mode: ° Running SCF from the TACL prompt without specifying a command. For example: > SCF -> ° Using TACL INLINE. TACL INLINE (discussed in the TACL Reference Manual) allows a user to write a TACL program to simulate a user at a terminal. The INLINE facility is a special case of INV, in which the input variable is implicitly formed by TACL from the lines with the INLPREFIX that is in effect.
Input Sources SCF Commands The preceding command is an example of what is sometimes called commandline mode. Command-line mode is defined as a series of noninteractive mode commands that have the same IN and OUT file; when command execution is finished, control is returned to the same TACL prompt from where execution started. Input Sources SCF accepts command input from a terminal or a disk file. The initial input source is determined by the form of the RUN command used to initiate SCF.
Output Destinations SCF Commands OBEY File Consideration OBEY commands can appear within command files. Command files can be nested to a depth of ten. If a depth of ten is exceeded, the file is not executed and an error message is displayed. Output Destinations SCF can direct output to a disk file, an application process, a terminal, or a printer. The initial output destination is determined by the form of the RUN command used to initiate SCF.
Logging Input and Output to a File SCF Commands Logging Input and Output to a File To record both the input commands and the corresponding output displays in a single file, use the LOG command, which is described in the SCF Reference Manual for G-Series RVUs. Specifying a log file does not change either the input source or the output destination; instead, a copy of the commands and displays is sent to the specified file. For example, the following LOG command creates a file named $DATA.SCF.
SCF Menu-Mode Help SCF Commands SCF Menu-Mode Help The menu-mode help facility presents a series of menus with options. Menu-mode help is for interactive mode only. You invoke it by entering the HELP command without any parameters. After menu-mode help is invoked, you can exit at any prompt by entering QUIT or by pressing Ctrl-Y. Either of these entries returns you to the SCF prompt. Figure 4-2.
ATM Subsystem SCF Commands SCF Commands ATM Subsystem SCF Commands This section describes the SCF commands you can use to manage the ATM subsystem. Table 4-1 lists the objects and SCF commands applicable to the ATM subsystem. For a detailed description of SCF, see the SCF Reference Manual for GSeries RVUs. Table 4-1.
Sensitive and Nonsensitive Commands SCF Commands Sensitive and Nonsensitive Commands Some SCF commands are sensitive because they can have detrimental effects if improperly used, so special qualification is required to use them. Sensitive commands can change the state or configuration of subsystem objects, start or stop tracing, or change the values of statistics counters.
SCF Object States SCF Commands Figure 4-3. SCF Object Hierarchy ATM ServerNet Adapter ATM Subsystem Manager ($ZZATM) SUBSYS (ASM) ADAPTER ATM Management Process ATM Line PROCESS (AMP) LINE SVC PVC ATMSAP VST403.vsd SCF Object States SCF objects can be in different operations states, depending on the SCF command issued to that object. The different operational states are: Unknown The system has not created the process.
Generic Processes SCF Commands Table 4-3. Possible Object States for ATM Objects Possible States Object Unknown STOPPED STARTING STARTED ADAPTER x x x x ATMSAP x x x x LINE x x x x PROCESS x x SUBSYS x x PVC x x x SVC x x Generic Processes A generic process is a process created by the operating system or a user to perform a task. The ASM process is created by the operating system and configured as a generic processes.
ABORT Command SCF Commands ABORT Command The ABORT command terminates the operation of objects as quickly as possible. Only enough processing is done to ensure the integrity of the subsystem. The object is left in the STOPPED state. ABORT is a sensitive command. The ABORT command is supported for the following ATM subsystem objects: • • • • • • ADAPTER ATMSAP LINE PVC SUBSYS SVC Considerations • • • • • All activities being performed by the specified objects are terminated.
ABORT ADAPTER Command SCF Commands ADAPTER adapter-name specifies the name of the ADAPTER to be aborted. The ADAPTER name has the form $AM1. SUB { ALL | NONE | ONLY } selects the subordinate objects the command affects. ALL specifies that the named object and the subordinate objects are affected. NONE specifies that the name object is affected but that the subordinate objects are not. Default: NONE ONLY specifies that only the subordinate objects are affected.
ABORT ATMSAP Command SCF Commands ABORT ATMSAP Command The ABORT ATMSAP command terminates the operation of an ATMSAP and places the ATMSAP object in the STOPPED summary state. This is a sensitive command. Command Syntax ABORT [/OUT file-spec/ ] ATMSAP atmsap-name OUT file-spec causes any SCF output generated for this command to be directed to the specified file. ATMSAP atmsap-name specifies the name of the ATMSAP to be aborted. The ATMSAP name has the form $AM1.#IP.
ABORT LINE Command SCF Commands ABORT LINE Command The ABORT LINE command terminates the operation of an ATM connection and places the LINE object in the STOPPED summary state. This is a sensitive command. Command Syntax ABORT [/OUT file-spec/ ] LINE line-name [, SUB { ALL | NONE | ONLY } ] OUT file-spec causes any SCF output generated for this command to be directed to the specified file. LINE line-name specifies the name of the LINE to be aborted. The LINE name has the form $ATM.
ABORT PVC Command SCF Commands Examples These examples show the ABORT LINE command: -> ABORT LINE $AM1 -> ABORT LINE ($AM1,$AM2) -> ABORT LINE $AM1, SUB ALL ABORT PVC Command The ABORT PVC command terminates the operation of a PVC and places the PVC object in the STOPPED summary state. This is a sensitive command. Command Syntax ABORT [/OUT file-spec/ ] PVC pvc-name OUT file-spec causes any SCF output generated for this command to be directed to the specified file.
ABORT SUBSYS Command SCF Commands ABORT SUBSYS Command The ABORT SUBSYS command halts the operation of the specified ASM manager process ($ZZATM) as quickly as possible and puts it in the STOPPED state. Only enough processing is done to ensure that the object can run again when it is restarted. Command Syntax ABORT [/OUT file-spec/ ] SUBSYS subsys-name OUT file-spec causes any SCF output generated for this command to be directed to the specified file.
ABORT SVC Command SCF Commands ABORT SVC Command The ABORT SVC command terminates the operation of an SVC and deletes the SVC object from the subsystem. This is a sensitive command. Command Syntax ABORT [/OUT file-spec/ ] SVC svc-name OUT file-spec causes any SCF output generated for this command to be directed to the specified file. SVC svc-name specifies the name of the SVC to be aborted. The SVC name has the form $linename.#atmsap-name.svc-name. The #atmsap-name is preconfigured with the name #IP.
ADD Command SCF Commands ADD Command The ADD command defines an object to the ATM subsystem. The fully qualified name assigned to the created object must be unique. If an attribute for a given object is not assigned a value in the ADD command, the attribute's default value is used. However, some attributes do not have default values and must be assigned values in the ADD command. This is a sensitive command.
ADD ADAPTER Command SCF Commands Command Syntax ADD [/OUT file-spec/] ADAPTER adapter-name , ACCESSLIST cpu-list , LOCATION ( group, enclosure, slot ) [ , AMPFILENAME string ] [ , DLFILENAME string ] [ , FIRMWFILENAME string ] [ , DUMPFILENAME string ] [ , AUTODUMP { ON | OFF } ] [ , AUTOFIRMUP { ON | OFF } ] [ , AUTORELOAD { ON | OFF } ] [ , PROBEINTERVAL 1/100th second ] [ , PROBECOUNT digit ] [ , SYSCONTACT string ] [ , SYSDESC string ] [ , SYSLOCATION string ] [ , SYSNAME string ] [ , SYSOBJID string
ADD ADAPTER Command SCF Commands LOCATION ( group, enclosure, slot ) specifies the physical location of the ADAPTER in the system. The location is specified as a tuple indicating the group, module, and slot enclosed in parenthesis. This attribute is required. AMPFILENAME string specifies the program name for AMP. Default: $SYSTEM.SYS*.AMP. Where SYS* indicates the SYSnn of the current running system. DLFILENAME string specifies the name of the download file to set up the ADAPTER. Default: $SYSTEM.SYS*.
ADD ADAPTER Command SCF Commands AUTORELOAD { ON | OFF } specifies if the ADAPTER is automatically reloaded following an ADAPTER reset. An ON value indicates the ADAPTER software is automatically reloaded. Default: ON. PROBEINTERVAL milliseconds specifies the time interval in 1/100th of a second in which the AMP will send a probe message to the ADAPTER to verify the adapter path and to verify the adapter is operational. Default: 3 seconds.
ADD ADAPTER Command SCF Commands SYSOBJID string specifies the vendor’s authoritative ID of the Network Management subsystem contained in the entity. The string specified must be in the range 0 through 256. This attribute is for informational purposes only. Default: blanks. SYSSERVICE digit 1-7 specifies the services offered for this entity. This attribute is for informational purposes only.
ADD PVC Command SCF Commands • When an ADAPTER is added to the subsystem, the subsystem is automatically creates a subordinate LINE object. Example This example shows the ADD ADAPTER command: -> ADD ADAPTER $ZZATM.$AM1, LOCATION (1,1,53), & ACCESSLIST (1,2,3) ADD PVC Command The ADD PVC command creates a PVC object for the ATM subsystem. The PVC object is supported only for native operation. LAN emulation is not supported.
ALTER Command SCF Commands Considerations • • The name of the PVC includes the name of the ATMSAP or SAP with which the PVC is associated. The initial state of the object after being added is the STOPPED summary state. Example This example shows the ADD PVC command: -> ADD PVC $AM1.#IP.PVC01, VPI 1, VCI 33 ALTER Command The ALTER command is used to alter the attributes of an object to the ATM subsystem. This is a sensitive command.
ALTER ADAPTER Command SCF Commands Command Syntax ALTER [/OUT file-spec/] ADAPTER adapter-name [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ , , , , , , , , , , , , , , , , DLFILENAME filename ] FIRMWFILENAME filename ] DUMPFILENAME filename ] AUTODUMP { ON | OFF } ] AUTOFIRMUP { ON | OFF } ] AUTORELOAD { ON | OFF } ] PROBEINTERVAL 1/100 seconds ] PROBECOUNT digit ] SYSCONTACT string ] SYSDESC string ] SYSLOCATION string ] SYSNAME string ] SYSOBJID string ] SYSSERVICE digit 1-7 ] DFC digit 1-50 ] DFT (1-200)/1000th s
ALTER ADAPTER Command SCF Commands AUTODUMP { ON | OFF } specifies whether the ADAPTER software is automatically dumped to the dump file when the subsystem detects the ADAPTER software abended abnormally. An ON value indicates that the ADAPTER software is automatically dumped. The default value is ON. AUTOFIRMUP { ON | OFF } specifies whether the ADAPTER firmware is automatically updated with the newer firmware.
ALTER ADAPTER Command SCF Commands SYSDESC string specifies the full name and version ID of the system hardware and software, operating system, and networking components. The string specified must be in the range 0 through 256. This attribute is for informational purposes only. Default: blanks. SYSLOCATION string specifies the physical location of the device. The string specified must be in the range 0 through 256. This attribute is for informational purposes only. Default: blanks.
ALTER LINE Command SCF Commands DFC digit 1-50 specifies how many packets the adapter receives before sending them to the host. If the DFC is set to 1, packets are forwarded immediately, and DFT is disabled. The default is 2. DFT (1-200)/1000th seconds specifies how many milliseconds the adapter waits before packets are sent to the host. The default is 1. Considerations • • • A valid ADAPTER name must be specified.
ALTER LINE Command SCF Commands Command Syntax ALTER [ [ [ [ [ [ [ [ [ [ [ [ [/OUT file-spec/] LINE line-name , ATMADDR atm-address ] , MAXPVCVCI digit ] , MAXPVCVPI digit ] , MAXVPCS digit ] , MAXPVCCS digit ] , MAXVPIBITS digit ] , MAXVCIBITS digit ] , UMECOMMUNITY community-name ] , UMEVPI digit ] , UMEVCI digit ] , UNIPORTTYPE {public|private} , UNIVERSION {3.0|3.1} OUT file-spec causes any SCF output generated for this command to be directed to the specified file.
ALTER LINE Command SCF Commands MAXVPCS digit specifies the maximum number of VP connections. The value specified must be in the range 0 through 256. Default: 100. MAXVCCS digit specifies the maximum number of VC connections. The value specified must be in the range 0 through 3072. Default: 100. MAXVPIBITS digit specifies the address width and the maximum number of VPI bits that can be active for this interface. The value specified must be in the range 0 through 8. Default: 8.
ALTER PVC Command SCF Commands UNIVERSION {3.0|3.1} specifies the UNI version supported by the interface. The value specified must be 3.0 or 3.1. Default: 3.0. Considerations The LINE object must be in a STOPPED summary state. Example This example shows the ALTER LINE command: -> ALTER LINE $AM1, UMEVPI 1, UMEVCI 16 ALTER PVC Command The ALTER PVC command changes the value of one or more attributes of the PVC object. The PVC object must be in a STOPPED state. This is a sensitive command.
DELETE Command SCF Commands Considerations The PVC must be in a STOPPED summary state. Example This example shows the ALTER PVC command: -> ALTER PVC $AM1.#IP.PVC1, VPI 0, VCI 75 DELETE Command The DELETE command deletes an object from the ATM subsystem. This is a sensitive command. The DELETE command is supported for the following ATM subsystem objects: • • ADAPTER PVC Considerations • • • Before you can delete an object the object must be in the STOPPED summary state.
DELETE PVC Command SCF Commands ADAPTER adapter-name specifies the name of the ADAPTER to be deleted. The ADAPTER name has the form $AM1. SUB { ALL | NONE | ONLY } selects the subordinate objects the command affects. ALL specifies that the named object and the subordinate objects are affected. NONE specifies that the name object is affected but that the subordinate objects are not. ONLY specifies that only the subordinate objects are affected. DEFAULT: None.
DUMP Command SCF Commands PVC pvc-name specifies the name of the PVC object to be deleted. The pvc-name has the form $AM1.#IP.PVC1. Considerations The PVC object must be in the STOPPED state with no registered users before it can be deleted. Examples The first example deletes the PVC named $AM1.#IP.PVC01 from the ATM subsystem. The second example deletes all AM1 PVCs: -> DELETE PVC $AM1.#IP.PVC01 -> DELETE PVC $AM1.#IP.
INFO Command SCF Commands Command Syntax DUMP [/OUT file-spec/] ADAPTER-name [, DUMPFILENAME string ] OUT file-spec causes any SCF output generated for this command to be directed to the specified file. ADAPTER adapter-name specifies the name of the ADAPTER to be dumped. The ADAPTER name has the form $AM1. DUMPFILENAME specifies the dump file to be used by AMP. If a dump file is not specified, the default value is used.
INFO ADAPTER Command SCF Commands • SVC For more information enter: HELP subsys cmd object-type -> HELP ATM INFO object-type INFO ADAPTER Command The INFO ADAPTER command displays current attribute settings for ADAPTER objects. Command Syntax INFO [/OUT file-spec/ ] ADAPTER adapter-name [ , SUB { ALL | NONE | ONLY ] OUT file-spec causes any SCF output generated for this command to be directed to the specified file.
INFO ADAPTER Command SCF Commands INFO ADAPTER Display The display for the INFO ADAPTER command is as follows: -> info ada $am1 ATM Info ADAPTER \KIKI.$AM1 LOCATION (grp,mod,slot).. 1 ,1 ,54 ACCESSLIST............... 0, 1, 2, 3 AMP Filename (in use).... \KIKI.$SYSTEM.SYS01.AMP *AMPFILENAME ............ $SYSTEM.SYS*.AMP DownLd Filename (in use). \KIKI.$SYSTEM.SYS01.C7838P00 *DLFILENAME .............$SYSTEM.SYS*.C7838P00 Downld File Version......T7838G06^04APR99^30Mar99 Dump Filename (in use)... $OSS.
INFO ADAPTER Command SCF Commands AMP Filename (in use) specifies the program file currently being used by the AMPs. AMPFILENAME specifies the program file that was configured for the ADAPTER. The value is defined by the AMPFILENAME attribute of the ADD ADAPTER command. DownLd Filename specifies the name of the download file currently downloaded or the name of the file to be downloaded to the ADAPTER. DLFILENAME specifies the name of the download file that was configured for the ADAPTER.
INFO ADAPTER Command SCF Commands AUTORELOAD specifies whether the ADAPTER software is automatically reloaded when the subsystem detects the ADAPTER software abended abnormally. An ON value indicates the ADAPTER software is automatically dumped. The value is defined by the AUTORELOAD attribute of the ADD ADAPTER and ALTER ADAPTER commands. AUTOFIRMUP specifies whether the ADAPTER firmware is automatically updated with the newer firmware.
INFO ADAPTER Command SCF Commands The value is defined by the SYSDESC attribute of the ADD ADAPTER and ALTER ADAPTER commands. SYSOBJID specifies the vendor’s authoritative ID of the Network Management subsystem contained in the entity. The string specified must be in the range 0 through 256. This attribute is for informational purposes only. The value is defined by the SYSOBJID attribute of the ADD ADAPTER and ALTER ADAPTER commands. SYSCONTACT specifies the contact person for this managed node.
INFO ATMSAP Command SCF Commands 6 - Undefined 7 - Applications (for example, mail relays) The value is defined by the SYSSERVICE attribute of the ADD ADAPTER and ALTER ADAPTER commands. The default value is 4. DFC digit 1-50 specifies how many packets the adapter receives before sending them to the host. If the DFC is set to 1, packets are forwarded immediately, and DFT is disabled. The default is 2.
INFO ATMSAP Command SCF Commands INFO ATMSAP Display The display for the INFO ATMSAP command is as follows: -> INFO ATMSAP $AM1.#IP ATM Info ATMSAP \HANSOLO.$AM1.#IP Call Type AAL Mode................ AAL fwd sdu size........ High Layer.............. QOS forward............. CLASS0 Bearer Class............ Bearer Config........... MESSAGE 9188 0 CLASS0 AAL AAL Low QOS Stype................... NULL bwd sdu size............ 9188 Layer................... 0 Backward................
INFO ATMSAP Command SCF Commands QOS Forward specifies the Quality of Service Class. The possible values are: CLASS0 QoS class 0 (unspecified QoS class) CLASS1 QoS class 1 CLASS2 QoS class 2 CLASS3 QoS class 3 CLASS4 QoS class 4 QOS Backward specifies the Quality of Service Class. Bearer Class specifies the broadband bearer capability. The possible values are: CLASS-A BCOB-A CLASS-C BCOB-C CLASS-X BCOB-X Bearer Susceptibility specifies the susceptibility to clipping.
INFO LINE Command SCF Commands INFO LINE Command The INFO LINE command displays the current attribute setting for the specified LINE. Command Syntax INFO [/OUT file-spec/ ] LINE line-name OUT file-spec causes any SCF output generated for this command to be directed to the specified file. LINE line-name specifies the name of the LINE for which information is to be displayed. If you do not specify a LINE, the SCF subsystem displays information for all line objects.
INFO LINE Command SCF Commands Registered Atm Address specifies the registered ATM address for the LINE. Currently, the registered and configured ATM addresses are the same. UNIVERSION specifies the UNI version supported by the LINE. The value is defined by the UNIVERSION attribute of the ALTER LINE command. Default: 3.1. UME: UMECOMMUNITY specifies the UNI Management Entity (UME) version supported by the LINE. The value is defined by the UMEVPI attribute of the ALTER LINE command. Default: “ ”.
INFO LINE Command SCF Commands Phys Layer Xmit Type specifies the physical transmission type used. ATM Layer: MAXVPCS specifies the maximum number of PVCs supported by the LINE. The value is defined by the MAXVPCS attribute of the ALTER LINE command. Default: 100. MAXVCCS specifies the maximum number of VCCs supported by the LINE. The value is defined by the MAXVCCS attribute of the ALTER LINE command. Default: 1000. MAXVPIBITS specifies the maximum number of bits used to define a VPI.
INFO PROCESS Command SCF Commands INFO PROCESS Command The INFO PROCESS command displays the current attribute setting for the specified PROCESS. Command Syntax INFO [/OUT file-spec/ ] PROCESS process-name OUT file-spec causes any SCF output generated for this command to be directed to the specified file. PROCESS process-name specifies the name of the PROCESS for which information is to be displayed. If you do not specify a process name, SCF displays the list of all processes.
INFO PVC Command SCF Commands Library File Creation specifies the library file creation timestamp. Configuration File Name specifies the ATM configuration file name. Configuration File Creation specifies the ATM configuration file creation timestamp. Ems File Name specifies the name of the EMS collector that includes EMS event messages currently sent by AMP. INFO PVC Command The INFO PVC command displays the current attribute setting for the specified PVC object.
INFO SUBSYS Command SCF Commands VPI specifies the VPI. The value is defined by the VPI attribute in the ADD PVC or ALTER PVC command. VCI specifies the VCI. The value is defined by the VCI attribute in the ADD PVC or ALTER PVC command. INFO SUBSYS Command The INFO SUBSYS command displays the current attribute setting for the specified SUBSYS object.
INFO SVC Command SCF Commands ATM Config File Creation specifies the ATM configuration file creation timestamp. INFO SVC Command The INFO SVC command displays the current attribute setting for the specified SVC object. Command Syntax INFO [/OUT file-spec/ ] SVC svc-name OUT file-spec causes any SCF output generated for this command to be directed to the specified file. SVC svc-name specifies the name of the SVC to for which information is to be displayed.
NAMES Command SCF Commands NAMES Command The NAMES command displays all of the fully qualified names specified by the object name. This is a nonsensitive command. The NAMES command is supported for the following ATM subsystem objects: • • • • • • • ADAPTER ATMSAP LINE PROCESS PVC SUBSYS SVC For more information enter: HELP subsys cmd object-type -> HELP ATM NAMES object-type NAMES ADAPTER Command The NAMES ADAPTER command displays the names of all adapter objects in the ATM subsystem.
NAMES ATMSAP Command SCF Commands NONE specifies that the name object is affected but that the subordinate objects are not. ONLY specifies that only the subordinate objects are affected. Default: None. Example This example shows the NAMES ADAPTER command: -> NAMES ADAPTER $AM1 NAMES ATMSAP Command The NAMES ATMSAP command displays the names of the ATMSAP objects.
NAMES LINE Command SCF Commands NAMES LINE Command The NAMES LINE command displays the name of the line objects in the ATM subsystem. Command Syntax NAMES [/OUT file-spec / ] LINE line-name [ SUB { ALL | NONE | ONLY } ] OUT file-spec causes any SCF output generated for this command to be directed to the specified file. LINE line-name specifies the LINE for which a name is displayed. SUB { ALL | NONE | ONLY } selects the subordinate objects the command affects.
NAMES PROCESS Command SCF Commands NAMES PROCESS Command The NAMES PROCESS command displays the names of ATM process objects. Command Syntax NAMES [/OUT file-spec / ] PROCESS process-name OUT file-spec causes any SCF output generated for this command to be directed to the specified file. PROCESS process-name specifies the PVC for which a list of subordinate process objects is to be displayed. For AMP, $process is $ZZATM.
NAMES SUBSYS Command SCF Commands NAMES SUBSYS Command The NAMES SUBSYS command displays the names of the SUBSYS objects in the ATM subsystem. Command Syntax NAMES [/OUT file-spec / ] SUBSYS subsys-name OUT file-spec causes any SCF output generated for this command to be directed to the specified file. SUBSYS subsys-name specifies the SUBSYS for which a list of subordinate objects is to be displayed.
START Command SCF Commands START Command The START command initiates the operation of the specified object. When the ATM subsystem has successfully completed processing this command, the object is placed in the STARTED or STARTING state. This is a sensitive command. The START command is supported for the following ATM subsystem objects: • • • • • ADAPTER ATMSAP LINE PVC SUBSYS Considerations • • • When you use the START command, the object should be in the STOPPED summary state.
START ADAPTER Command SCF Commands SUB { ALL | NONE | ONLY } selects the subordinate objects the command affects. ALL specifies that the named object and the subordinate objects are affected. NONE specifies that the name object is affected but that the subordinate objects are not. Default: None. ONLY specifies that only the subordinate objects are affected. Considerations • • • • When you use the START ADAPTER command, the object should be in the STOPPED summary state.
START ATMSAP Command SCF Commands START ATMSAP Command The START ATMSAP command initiates the operation of the ATMSAP object. When the subsystem has successfully completed processing this command, the ATMSAP object is placed in the STARTED summary state. Command Syntax START [/OUT file-spec / ] ATMSAP atmsap-name [ SUB { ALL | NONE | ONLY } ] OUT file-spec causes any SCF output generated for this command to be directed to the specified file.
START LINE Command SCF Commands START LINE Command The START LINE command initiates the operation of the LINE object. When the subsystem has successfully completed processing this command, the LINE object is placed in the STARTED summary state. Command Syntax START [/OUT file-spec / ] LINE line-name [ SUB { ALL | NONE | ONLY } ] OUT file-spec causes any SCF output generated for this command to be directed to the specified file. LINE line-name specifies the LINE name to be placed in the STARTED state.
START PVC Command SCF Commands Examples These examples start the line named $ATM: -> START LINE $AM1 -> START LINE $AM1, SUB ALL START PVC Command The START PVC command initiates the operation of the PVC object. When the subsystem has successfully completed processing this command, the PVC object is placed in the STARTED (or STARTING) summary state. Command Syntax START [/OUT file-spec/ ] PVC pvc-name OUT file-spec causes any SCF output generated for this command to be directed to the specified file.
START SUBSYS Command SCF Commands START SUBSYS Command The START SUBSYS command initiates the specified SUBSYS object and puts it in the STARTED state. Command Syntax START [/OUT file-spec/ ] SUBSYS subsys-name OUT file-spec causes any SCF output generated for this command to be directed to the specified file. SUBSYS subsys-name specifies the name of the SUBSYS to be started. Considerations • • When you use the START SUBSYS command, the object should be in the STOPPED summary state.
STATS Command SCF Commands STATS Command The STATS command displays statistical information for ATM objects. This is a nonsensitive command. The STATS command is supported for the following ATM subsystem objects: • • • • • ATMSAP LINE PROCESS PVC SVC For more information enter: HELP subsys cmd object-type -> HELP ATM STATS object-type STATS ATMSAP Command The STATS ATMSAP command displays statistical information for the specified ATMSAP object.
STATS LINE Command SCF Commands STATS ATMSAP Display The format of the display for the STATS ATMSAP command is: -> STATS ATMSAP $AM1.#IP ATM Stats ATMSAP \HANSOLO.$AM1.#IP Sample Time.............. 10 Feb 1998, 14:00:47.947 Reset Time............... 10 Feb 1998, 13:49:09.195 Frames Sent.............. 3000D Frames Recvd......... 2558D Sample Time specifies the time the statistics sample was taken. Reset Time specifies the time the statistics counters were last reset.
STATS LINE Command SCF Commands RESET specifies the statistical counters are to be reset to their initial values after the statistics are sampled. This is a sensitive command. STATS LINE Display The format of the display for the STATS LINE command is: -> STATS LINE $AM1 ATM Stats LINE \HANSOLO.$AM1 Sample Time.............. Reset Time............... No. Times Line Down...... Cells Received........... Cells Dropped............ Congestion............... Fifo Overrun............. CRC Error................
STATS PROCESS Command SCF Commands Fifo Overrun indicates the number of times the error occurs while NEC is receiving the packet. Max Length Error specifies the number of received cells which exceed the maximum number of segments shown in the VC table. CRC Error indicates the number of times the error occurs while NEC is receiving on AAL-5 packet. User Abort indicates the length field within the trailer has received a packet equal to 0000H.
STATS PROCESS Command SCF Commands Command Syntax STATS [/OUT /] PROCESS process-name [ , RESET ] OUT file-spec causes any SCF output generated for this command to be directed to the specified file. PROCESS process-name specifies the name of the PROCESS for which statistics are to be displayed. RESET specifies the statistical counters are to be reset. STATS PROCESS Display The format of the display for the STATS PROCESS command is: -> STATS PROCESS $ZAM1 ATM Stats PROCESS \HANSOLO.
STATS PROCESS Command SCF Commands Configured Count specifies the number of probe errors to be detected before declaring the adapter or SNET path to the adapter as inaccessible. No. Times Inaccessible specifies the number of times the ServerNet path to the adapter was declared inaccessible. Probes Sent specifies the number of probe messages sent. Timeouts specifies the number of probe response timeouts that has been detected. Good Responses specifies the number of good probe responses received.
STATS PVC Command SCF Commands Nsk Events specifies the number of NSK (QIO) events processed. Nsk Event Errors specifies the number of NSK (QIO) error or unexpected events processed. Get Md Attempts specifies the number of errors detected on shared memory Get MD attempts. Get Md Errors specifies the number of errors detected on shared memory Get MD attempts. Return Md Attempts specifies the number of shared memory Return MD attempts.
STATS SVC Command SCF Commands STATS PVC Display The format of the display for the STATS PVC command is as follows: -> STATS PVC $AM1.#IP.PVC09 ATM Stats PVC \HANSOLO.$AM1.#IP.PVC09 Sample Time.............. Reset Time............... Frames Sent.............. Bytes Sent............... 10 Feb 1998, 10 Feb 1998, 2121D 5446656D 13:25:47.476 11:32:50.260 Frames Received......... 0D Bytes Received.......... 0D Sample Time specifies the time the statistics sample was taken.
STATS SVC Command SCF Commands Command Syntax STATS [/OUT /] SVC pvc-name [ , RESET ] OUT file-spec causes any SCF output generated for this command to be directed to the specified file. SVC svc-name specifies the name of the SVC for which statistics are to be displayed. RESET specifies the statistical counters are to be reset to their initial values after the statistics are sampled. This is a sensitive command.
STATUS Command SCF Commands Example This example shows the STATS SVC command: -> STATS SVC $AM1.#IP.SVC00001, RESET STATUS Command The STATUS command displays status information for ATM objects. This is a nonsensitive command.
STATUS ADAPTER Command SCF Commands ALL specifies that the named object and the subordinate objects are affected. NONE specifies that the name object is affected but that the subordinate objects are not. ONLY specifies that only the subordinate objects are affected. DETAIL causes the STATUS command to display a list of detailed information about the adapter. Without this parameter, the command displays only a subset of the STATUS ADAPTER display. Default: None.
STATUS ADAPTER Command SCF Commands Sub State specifies the current sub state or the operation being performed by the ADAPTER. Values are as follows: Value Description RESETING The adapter is being reset. RESET The adapter reset operation completed. PRIMING The adapted is being placed in boot state. PRIMED The adapter init boot operation completed. LOADING The adapter is being downloaded.
STATUS ADAPTER Command SCF Commands System Up Time specifies the time in 1/100th of a second that the adapter software has been running. Firmware Version specifies the name of the version of the firmware or boot code currently running in the adapter. POST STATUS: The post status specifies post status returned by the adapter in response to a Get Status BootCode command. Code Running specifies the code type currently running on the adapter.
STATUS ATMSAP Command SCF Commands STATUS ATMSAP Command The STATUS ATMSAP command displays the dynamic state of the ATM service access point (ATMSAP). The state of an ATMSAP object can be either STARTED or STOPPED. This is a nonsensitive command. Command Syntax STATUS [/OUT file-spec/ ] ATMSAP atmsap-name [ SUB { ALL | NONE | ONLY }] OUT file-spec causes any SCF output generated for this command to be directed to the specified file.
STATUS LINE Command SCF Commands The format of the display for the STATUS ATMSAP command with the DETAIL option is: -> STATUS ATMSAP $AM1.#IP, DETAIL ATM Detailed Status ATMSAP \HANSOLO.$AM1.#IP State............. STARTED Active PVCs....... 0 Active SVCs....... 0 State specifies the current summary state of the object. Active PVCs specifies the number of active PVCs. Active SVCs specifies the number of active SVCs. Example This example shows the STATUS ATMSAP command: -> STATUS ATMSAP $AM1.
STATUS LINE Command SCF Commands ALL specifies that the named object and the subordinate objects are affected. NONE specifies that the name object is affected but that the subordinate objects are not. ONLY specifies that only the subordinate objects are affected. Default: None. STATUS LINE Display The format of the display for the STATUS LINE command is: -> STATUS LINE $AM1 ATM Status LINE \HANSOLO.
STATUS PROCESS Command SCF Commands Active SVCs specifies the number of active SVCs. Time Last Down specifies the time the ATM line was last down or in the stopped state. Example This example shows the STATUS LINE command: -> STATUS LINE $AM1, DETAIL STATUS PROCESS Command The STATUS PROCESS command displays the dynamic state of AMP. The state of a PROCESS object can be either STARTED or STOPPED. This is a nonsensitive command.
STATUS PROCESS Command SCF Commands The format of the display for the STATUS PROCESS command with the detail option: -> STATUS PROCESS $ZAM1, DETAIL ATM Detailed Status PROCESS \HANSOLO.$ZAM1 State..................... Time Last State Change.... Reason Last State Change.. Last Error................ CPU Pin................... Priority.................. Trace..................... STARTED 10 Feb 1998, 11:31:36.617 OPERATOR REQUESTED 0 1 ,21 180 OFF Adapter Probe Status...... ServerNet Path Status.....
STATUS PROCESS Command SCF Commands SNet Path/Probe Related: Adapter Probe Status specifies the status of the probing operation. The values are: Value Description ACTIVE The process is sending probe messages to the adapter. INACTIVE The process is not sending probe messages to the adapter. ServerNet Path Status specifies the status ServerNet path between AMP and the adapter.
STATUS PROCESS Command SCF Commands Shared Memory Related: Segment Attach Status specifies whether AMP is currently attached to the shared memory segment. Module ID specifies the module ID assigned by the Shared Memory subsystem. Mds Allocated specifies the number of Shared Memory Message descriptors that were allocated by calling the SM_MD_GET method. Mds Freed specifies the number of Shared Memory Message descriptors released by calling the SM_MD_RETURN_ method.
STATUS PVC Command SCF Commands STATUS PVC Command The STATUS PVC command displays the dynamic state of the PVC object. The state of a PVC object can be either STARTED or STOPPED. This is a nonsensitive command. Command Syntax STATUS [/OUT file-spec/ ] PVC pvc-name [ , DETAIL ] OUT file-spec causes any SCF output generated for this command to be directed to the specified file. PVC pvc-name specifies the name of the PVC for which status is to be returned.
STATUS SUBSYS Command SCF Commands State specifies the current summary state of the object. VPI specifies the VPI. VCI specifies the VP and virtual channel identifier (VCI). Example This example shows the STATUS PVC command: -> STATUS PVC $AM1.#IP.PVC01 STATUS SUBSYS Command The STATUS SUBSYS command displays the dynamic state of the SUBSYS object. The state of a SUBSYS object can be either STARTED or STOPPED. This is a nonsensitive command.
STATUS SUBSYS Command SCF Commands STATUS SUBSYS Display The format of the display for the STATUS SUBSYS command is: -> STATUS SUBSYS $ZZATM ATM Status SUBSYS Name $ZZATM $ZZATM-B State STARTED CREATED PPID 0, 22 1, 22 Pri 180 180 Trace OFF OFF The format of the display for the STATUS SUBSYS command with the detail option is: -> STATUS SUBSYS $ZZATM, DETAIL ATM Detailed Status SUBSYS \HANSOLO.$ZZATM State..................... Time Last State Change.... Reason Last State Change.. Last Error...........
STATUS SUBSYS Command SCF Commands Last Error specifies the last error detected by the primary ASM. Cpu Pin specifies the CPU and PIN of the primary ASM process. Priority specifies the priority primary ASM process. Trace specifies whether tracing for the primary ASM process is active. Heap Released: Idle Heap Free Space specifies the free heap space after the primary ASM process has initialized. Idle Heap Used Space specifies the used heap space after the primary ASM process has initialized.
STATUS SUBSYS Command SCF Commands Priority specifies the priority backup ASM process. Trace specifies whether tracing for the backup ASM process is active. AMP Related: Name specifies the name of AMP. State specifies the current summary state of AMP. PPID specifies the CPU and PIN of AMP. Pri specifies the priority of AMP. Pri specifies the priority of AMP. Trace specifies whether tracing is currently active in AMP.
STATUS SVC Command SCF Commands STATUS SVC Command The STATUS SVC command displays the dynamic state of the SVC object. The state of a SVC object can be either STARTED or STOPPED. This is a nonsensitive command. Command Syntax STATUS [/OUT file-spec/ ] SVC svc-name [ , DETAIL ] OUT file-spec causes any SCF output generated for this command to be directed to the specified file. SVC svc-name specifies the name of the SVC for which status is to be returned.
TRACE Command SCF Commands State specifies the current summary state of the object. VPI specifies the VPI. VCI specifies the VCI. Remote ATM Address specifies the remote ATM address of the end node. Local ATM Address specifies the ATM address of the local node. Example This example shows the STATUS SVC command: -> STATUS SVC $AM1.#IP.*, DETAIL TRACE Command The TRACE command initiates trace mode on the specified object. You can use the TRACE command as a diagnostic tool. This is a sensitive command.
TRACE ADAPTER Command SCF Commands TRACE ADAPTER Command The TRACE ADAPTER command executes a trace on the specified ADAPTER object. Command Syntax TRACE [/OUT file-spec/ ] ADAPTER adapter-name { STOP } { [, BULKIO | NOBULKIO ] [ , COUNT count ] [ , NOCOLL ] [ , PAGES pages ] [ , RECSIZE size ] [ , SELECT select-spec ] [ , TO file-spec ] [ , WRAP ] ... } OUT file-spec causes any SCF output generated for this command to be directed to the specified file.
TRACE ADAPTER Command SCF Commands NOCOLL specifies that trace data from the extended segment is written to the disk file specified in TO file-spec only when one of the following occurs: • • The trace is stopped. The number of trace records written to the extended data segment is equal to the count specified in the TRACE command that started the trace.
TRACE ADAPTER Command SCF Commands Table 4-4.
TRACE PROCESS Command SCF Commands • The parameters COUNT, RECSIZE, and SELECT can be changed during an ongoing trace. Other trace parameters cannot be modified during an ongoing trace. Example This example starts a trace for all traceable items in $AM1 file-spec: -> TRACE ADAPTER $AM1, TO file-spec, SELECT (DI, DO) TRACE PROCESS Command The TRACE PROCESS command initiates a trace on the specified PROCESS.
TRACE PROCESS Command SCF Commands specified. Bulk I/O tracing is faster and should eliminate most data loss. The default is BULKIO. BULKIO cannot be used with NOCOLL. COUNT count specifies the number of trace records to be captured. count is an integer in the range -1 through 32767. If COUNT is omitted or if count equals -1, records are accumulated until the trace is stopped.
TRACE PROCESS Command SCF Commands keyword is subsystem-specific. See Table 4-5 for the list of keywords that can be used for the PROCESS objects. number is the numeric value that a keyword represents. See Table 4-5 for the list of numbers that can be used for the PROCESS objects TO file-spec specifies the file to which trace information is to be written. The file might have been previously created as an unstructured file with file code 830. An old file is purged of data before the trace is initiated.
TRACE SUBSYS Command SCF Commands Example This example starts a trace for all traceable items in $AM1: -> TRACE PROCESS $AM1, STOP TRACE SUBSYS Command The TRACE SUBSYS command initiates a trace on the SUBSYS object. Command Syntax TRACE [/OUT file-spec/ ] SUBSYS subsys-name { , STOP [ , BACKUP { , [ , BACKUP { , [ , BULKIO | NOBULKIO [ , COUNT count [ , LOCKSIZE locksize [ , NOCOLL [ , PAGES pages [ , RECSIZE size [ , SELECT select-spec [ , TO file-spec [ , WRAP } ] ] ] ] ] ] ] ] ] ] ...
TRACE SUBSYS Command SCF Commands COUNT count specifies the number of trace records to be captured. count is an integer in the range -1 through 32767. If COUNT is omitted or if count equals -1, records are accumulated until the trace is stopped. LOCKSIZE locksize designates how much memory space, in units of pages, is locked down at one time. LOCKSIZE can be specified only when a trace is initiated. locksize is an integer in the range 4 through 1024. locksize must be less than or equal to pagesize.
TRACE SUBSYS Command SCF Commands { number } { ( number [ , number ] ... ) } keyword is subsystem-specific. See Table 4-4 on page 4-100 for the list of keywords that can be used for the ADAPTER objects. number is the numeric value that a keyword represents. See Table 4-4 on page 4-100 for the list of numbers that can be used for the ADAPTER objects. TO file-spec specifies the file to which the trace information is to be written.
VERSION Command SCF Commands VERSION Command The VERSION command displays version information about the ATM subsystem and the level of support for security and tracing. The VERSION command is a nonsensitive command. The TRACE command is supported for the following ATM subsystem objects: • • • ADAPTER PROCESS SUBSYS For more information enter: HELP subsys cmd object-type -> HELP ATM VERSION object-type VERSION ADAPTER Command The VERSION ADAPTER command displays the version information of AMP.
VERSION PROCESS Command SCF Commands VERSION ADAPTER Display The format of the display for the VERSION ADAPTER command is: -> VERSION ADAPTER $AM2 ATM VERSION ADAPTER Download Code Banner..... ATM - T7838G02-15AUG97-(22APR97) Firmware Version Banner.. T8158G01^15NOV96^21JAN97 Download Code Banner specifies the version of the downloaded software currently running on the adapter. Firmware Version Banner specifies the version of the firmware currently running on the adapter.
VERSION PROCESS Command SCF Commands VERSION PROCESS Display The format of the display for the VERSION PROCESS command is: -> VERSION PROCESS $ZZAM22 VERSION PROCESS $ZZAM22: ATAP Processs - T7839G02 - 15FEB98 - Ver. 1.0 The format of the display for the VERSION PROCESS command with the DETAIL option is: -> VERSION PROCESS $ZAM22, DETAIL Detailed VERSION PROCESS \HANSOLO.$ZZAM22 SYSTEM \HANSOLO ATM Mgmt Process - T7839G02 - 15FEB98 - Ver. 1.
VERSION SUBSYS Command SCF Commands VERSION SUBSYS Command The VERSION SUBSYS command displays the version information for ASM software. Command Syntax VERSION [/OUT file-spec/ ] SUBSYS subsys-name [ , DETAIL ] OUT file-spec causes any SCF output generated for this command to be directed to the specified file. SUBSYS subsys-name specifies the SUBSYS for version information is to be displayed. DETAIL displays version information about the SCF Kernel and the SCF ATM PRODUCT MODULE.
VERSION SUBSYS Command SCF Commands GUARDIAN specifies the version of ASM. SCF Kernel specifies the version of the SCF Kernel. ATM PM specifies the version of the ATM SCF PRODUCT MODULE.
SCF Commands VERSION SUBSYS Command ATM Configuration and Management Manual— 522307-003 4 -112
A SCF Command Summary ABORT [/OUT file-spec/ ] [ ADAPTER adapter-name ] [, SUB { ALL | NONE | ONLY } ] ABORT [/OUT file-spec/ ] [ ATMSAP atmsap-name ] ABORT [/OUT file-spec/ ] [ LINE line-name ] [, SUB { ALL | NONE | ONLY } ] ABORT [/OUT file-spec/ ] [ PVC pvc-name ] ABORT [/OUT file-spec/ ] [ SUBSYS subsys-name ] ABORT [/OUT file-spec/ ] [ SVC svc-name ] ATM Configuration and Management Manual— 522307-003 A- 1
SCF Command Summary ADD [/OUT file-spec/] [ ADAPTER adapter-name ] , ACCESSLIST cpu-list , LOCATION ( group, enclosure, slot ) [ , AMPFILENAME string ] [ , DLFILENAME string ] [ , FIRMWFILENAME string ] [ , DUMPFILENAME string ] [ , AUTODUMP { ON | OFF } ] [ , AUTOFIRMUP { ON | OFF } ] [ , AUTORELOAD { ON | OFF } ] [ , PROBEINTERVAL 1/100th second ] [ , PROBECOUNT digit ] [ , SYSCONTACT string ] [ , SYSDESC string ] [ , SYSLOCATION string ] [ , SYSNAME string ] [ , SYSOBJID string ] [ , SYSSERVICE digit 1-
SCF Command Summary ALTER [ [ [ [ [ [ [ [ [ [ [ [ [/OUT file-spec/] [ LINE line-name ] , ATMADDR atm-address ] , MAXPVCVCI digit ] , MAXPVCVPI digit ] , MAXVPCS digit ] , MAXPVCCS digit ] , MAXVPIBITS digit ] , MAXVCIBITS digit ] , UMECOMMUNITY community-name ] , UMEVPI digit ] , UMEVCI digit ] , UNIPORTTYPE {public|private} , UNIVERSION {3.0|3.
SCF Command Summary INFO [/OUT file-spec/ ] [ LINE line-name ] INFO [/OUT file-spec/ ] [ PROCESS process-name ] INFO [/OUT file-spec/ ] [ PVC pvc-name ] INFO [/OUT file-spec/ ] [ SUBSYS subsys-name ] INFO [/OUT file-spec/ ] [ SVC svc-name ] LISTOPENS [/OUT file-spec / ] [ATMSAP atmsap-name ] LOAD [/OUT file-spec / ] [LOAD adapter-name ] [FIRMWARE filename ] NAMES [/OUT file-spec / ] [ADAPTER adapter-name ] [ SUB { ALL | NONE | ONLY } ] NAMES [/OUT file-spec / ] [ ATMSAP atmsap-name ] NAMES [/OUT f
SCF Command Summary NAMES [/OUT file-spec / ] [ PROCESS process-name ] NAMES [/OUT file-spec / ] [ PVC pvc-name ] NAMES [/OUT file-spec / ] [ SUBSYS subsys-name ] NAMES [/OUT file-spec / ] [ SVC svc-name ] START [/OUT file-spec / ] [ ADAPTER adapter-name ] [ SUB { ALL | NONE | ONLY } ] START [/OUT file-spec / ] [ ATMSAP atmsap-name ] [ SUB { ALL | NONE | ONLY } ] START [/OUT file-spec / ] [ LINE line-name ] [ SUB { ALL | NONE | ONLY } ] START [/OUT file-spec/ ] [ PVC pvc-name ] START [/OUT file-spe
SCF Command Summary STATS [/OUT /] [ PVC pvc-name ] [ , RESET ] STATS [/OUT /] [ SVC pvc-name ] [ , RESET ] STATUS [/OUT file-spec/ ] [ ADAPTER adapter-name ] [ SUB { ALL | NONE | ONLY } ] [ , DETAIL ] STATUS [/OUT file-spec/ ] [ ATMSAP atmsap-name ] [ SUB { ALL | NONE | ONLY }] STATUS [/OUT file-spec/ ] [ LINE line-name ] [ SUB { ALL | NONE | ONLY } ] STATUS [/OUT file-spec/ ] [ PROCESS process-name ] [ , DETAIL ] STATUS [/OUT file-spec/ ] [ PVC pvc-name ] [ , DETAIL ] STATUS
SCF Command Summary TRACE [/OUT file-spec/ ] [ ADAPTER adapter-name ] { , STOP { , [, BULKIO | NOBULKIO [ , COUNT count [ , NOCOLL [ , PAGES pages [ , RECSIZE size [ , SELECT select-spec [ , TO file-spec [ , WRAP } ] ] ] ] ] ] ] ] ... } TRACE [/OUT file-spec/ ] [ PROCESS amp-name ] { , STOP [ , BACKUP { , [ , BACKUP { , [ , BULKIO | NOBULKIO [ , COUNT count [ , NOCOLL [ , PAGES pages [ , RECSIZE size [ , SELECT select-spec [ , TO file-spec [ , WRAP } ] ] ] ] ] ] ] ] ] ...
SCF Command Summary VERSION [/OUT file-spec/ ][ PROCESS process-name ][ , DETAIL ] VERSION [/OUT file-spec/ ][ SUBSYS subsys-name ][ , DETAIL ] ATM Configuration and Management Manual— 522307-003 A- 8
B ATM Event Messages This appendix describes the event messages for the ATM subsystem that might appear in the $0 log. 100 00100 ATM: Guardian Procedure Call Error subject, Severity: severity [, secondary subject], Procedure: procedure name, Error: error [, Symptom String: symptom string] [, Reporting method: reporting method] subject specifies the subject for the event as Amp-Process. severity specifies the severity of the event.
101 ATM Event Messages 101 00101 ATM: New Exception subject, Severity: severity [, secondary subject], Class: class [, Name: name] [, Size: size] [, heap Used: heap used, Heap Free: heap free] [, Symptom String: symptom string] [, Reporting Method: reporting method] subject specifies the subject for the event as Amp-Process. severity specifies the severity of the event. The possible values are: Indeterminate Critical secondary subject specifies the secondary subject for the event.
102 ATM Event Messages Cause. Specifies the process was unable to allocate memory for the C++ new operation. Effect. The operation or request being processed is terminated with an error. Recovery. This error is serious. Contact your service provider.
103 ATM Event Messages I/O size specifies the I/O size for the file operation. eof address specifies the end-of-file address. block count specifies the block count. next block address specifies the next block address. record size specifies the record size. max record size specifies the maximum allowed record size. directory address specifies the directory end address. symptom string specifies where the error was detected. reporting method specifies where the error was generated. Cause.
104 ATM Event Messages Atm-Adapter Atm-Atmsap Atm-Pvc severity specifies the severity of the event as Informational. secondary subject specifies the secondary subject for the event. object type specifies the DSM object type. reason specifies the reason why the object was added. Cause. An SCF ADD command was successfully completed or an internally generated add request was successfully completed. Effect. The object was added to the ATM subsystem. Recovery. None. This is an informational event.
105 ATM Event Messages Cause. Specifies an SCF ALTER command was successfully completed. Effect. Attributes for the object were altered. Recovery. None. This is an informational event. 105 00105 Object Deleted subject, Severity: severity [,secondary subject ], Object Type: object type, Reason: reason subject specifies the subject for the event. The possible values are: Atm-Adapter Atm-Atmsap Atm-Pvc severity specifies the severity of the event as Informational.
200 ATM Event Messages severity specifies the severity of the event. The possible values are: Indeterminate Critical secondary subject specifies the secondary subject for the event as Config-File. procedure name specifies the name of the procedure which returned the error. error specifies the returned error code. error detail specifies the returned detailed error code. item type specifies the name of the item or record type. item name specifies the name of the item.
202 ATM Event Messages 202 00202 ATM: Data Base Err subject, Err: error, Err Detail: error detail, AT location [, Type: item type, Name: item name ] subject specifies the subject for the event as Atm-Mgr. error specifies the error returned from the database procedure. error detail specifies the error detail. location specifies where the event was generated. item type specifies the item type. item name specifies the name of the item. Cause.
302 ATM Event Messages location specifies where the event was generated. Cause. Specifies the process encountered a heap allocation error. Effect. The process was unable to allocate memory. Recovery. This error is serious. Contact your service provider. 302 00302 ATM: ASM Internal Err: event name, subject, AT reporting method [, Info Num: error ][, Detail: detail] [, Type: object type, Name: object name] event name specifies the event name of the intended error.
402 ATM Event Messages 402 00402 Object Available subject, Event Number: event, Reason: reason, Previous State: state, Current State: state [, Manager: manager name ] [, Batch ID: jobid ] [, User Content: text ] subject specifies the subject for the event as Amp-Process. event displayed as Amp-Started. reason specifies the reason the object became available. state in the previous state field, state specifies the state the object was in before becoming available.
404 ATM Event Messages event displayed as Amp-Stopped. reason specifies the reason the object became unavailable. state in the previous state field, state specifies the state the object was in before becoming unavailable. In the current state field, state specifies the state of the object after it became unavailable. manager name specifies the ASM. text provides additional information about the event. Cause. The adapter was deleted from the ATM subsystem, or the AMP process aborted abnormally. Effect.
502 ATM Event Messages text provides additional information about the cause for the event. error specifies the ATM subsystem defined error code. error detail specifies the detail of the error. symptom string specifies where the error was detected. reporting method specifies where the error was generated. Cause. Specifies where in the software the event was generated. Effect. The operation or request being processed is terminated with an error. Recovery. This error is serious.
503 ATM Event Messages text provides additional information about the event. Cause. An SCF START command was successfully processed or the ATM subsystem internally started the object. Effect. The ATM subsystem can access the object. Recovery. None. This is an informational event.
600 ATM Event Messages 600 00600 Object Available subject, Event Number: event, Reason: reason, Previous State: state, Current State: state, [, Manager: manager name ] [, Batch ID: jobid ] [, User Content: text ] subject specifies the subject for the event as ATM-Adapter. event displayed as Adapter-Started. reason specifies the reason the object became available. state in the previous state field, state specifies the state the object was in before becoming available.
602 ATM Event Messages event displayed as Adapter-Stopped. reason specifies the reason the object became unavailable. state in the previous state field, state specifies the state the object was in before becoming unavailable. In the current state field, state specifies the state of the object after it became unavailable. manager name specifies the ASM. text provides additional information about the event. Cause.
602 ATM Event Messages Adapter-Local-Abort-Request Adapter-Init-QServ-Request Adapter-Reset-Request subject specifies the subject for the event as Atm-Adapter. severity specifies the severity of the event as Informational. secondary subject specifies the secondary subject for the even as Amp-Process. group specifies the physical group location of the adapter. module specifies the physical module location of the adapter. slot specifies the physical slot location of the adapter.
603 ATM Event Messages Cause. The AMP received an adapter request which contained a command such as a START, ABORT, and DUMP. Effect. The operations required to perform the request has been initiated. Recovery. None. This is an informational event.
603 ATM Event Messages module specifies the physical module location of the adapter. slot specifies the physical slot location of the adapter. cpu specifies the process the AMP is running on. pin specifies the process ID of the AMP. download file name specifies the download file being used. download file version specifies the download file version. firmware file specifies the firmware file being used. firmware file version specifies the firmware file version. dump file name specifies the dump file. Cause.
604 ATM Event Messages 604 00604 ATM: request Failed subject, Severity: severity [, secondary subject], Adapter Location: (GRP group, MOD module, SLOT slot), By AMP In: (CPU cpu, PIN pin) [, Error: error] [, Download file: download file name] [DownloadVersion: download file version] [, Firmware Version: firmware file version] [, DumpFile: dump file name] [, Symptom String: symptom string] [, Reporting Method: reporting method] request specifies the request being started.
604 ATM Event Messages slot specifies the physical slot location of the adapter. cpu specifies the process the AMP is running on. pin specifies the process ID of the AMP. error specifies the ATM subsystem defined error code. download file name specifies the download file being used. download file version specifies the download file version. firmware file specifies the firmware file being used. firmware file version specifies the firmware file version. dump file name specifies the dump file.
605 ATM Event Messages 605 00605 ATM: operation Started subject, Severity: severity [, secondary subject] Adapter Location: (GRP group, MOD module, SLOT slot) [, Download File: download file] [, Download Version: download version] [Firmware File: firmware file] [, Firmware Version: firmware version] [Dump File: dump file] operation specifies the request being started.
606 ATM Event Messages slot specifies the physical slot location of the adapter. download file name specifies the download file being used. download file version specifies the download file version. firmware file specifies the firmware file being used. firmware file version specifies the firmware file version. dump file name specifies the dump file. Cause. Specifies that the AMP started an adapter operation or sent a command to the adapter to initiate an operation. Effect.
607 ATM Event Messages Adapter-Dsm-Configure Adapter-Adapter-Start Adapter-Adapter-Dump Adapter-Adapter-Load-Ram-Boot Adapter-Exec-Boot-Code subject specifies the subject for the event as Atm-Adapter. severity specifies the severity of the event as Informational. secondary subject specifies the secondary subject for the event as Amp-Process. group specifies the physical group location of the adapter. module specifies the physical module location of the adapter.
607 ATM Event Messages Unknown Adapter-Reset Adapter-Run-Post Adapter-Prime Adapter-Get-Post Adapter-Fetch-Version Adapter-Load-Ram-Op-Code Adapter-Exec-Op-Code Adapter-Init-QServ Adapter-Dsm-Configure Adapter-Adapter-Start Adapter-Adapter-Dump Adapter-Adapter-Load-Ram-Boot Adapter-Exec-Boot-Code subject specifies the subject for the event as Atm-Adapter. severity specifies the severity of the event.
607 ATM Event Messages symptom string specifies where in the software the error was detected. reporting method specifies where in the software the error was generated. download file name specifies the download file being used. download file version specifies the download file version. firmware file specifies the firmware file being used. firmware file version specifies the firmware file version. dump file name specifies the dump file. symptom string specifies where in the software the error was detected.
608 ATM Event Messages 608 00608 ATM: Adapter Post Status Error subject, Severity: severity [, secondary subject], Adapter Location: (GRP group, MOD module, SLOT slot) [Post Test Failures: failures, Post Test No: test mumber, Test Data: test data 1, test data 2, test data 3, test data 4, test data 5, test data 6] [, Firmware Version: firmware version] [, Symptoom String: symptom string] [, Reporting Method: reporting method] subject specifies the subject for the event as Atm-Adapter.
609 ATM Event Messages symptom string specifies where in the software the error was detected. reporting method specifies where in the software the error was generated. Cause. The AMP read the power on self-test results from the adapter which indicated the tests detected an error. Effect. The adapter cannot be started. Recovery. If an SCF command was issued, retry the command. If the problem persists, replace the adapter or update the firmware.
610 ATM Event Messages minor specifies the adapter defined minor error code. info specifies the adapter defined informational code. pc specifies the program counter of the adapter. version string specifies the version string of the adapter. error string specifies the error string of the adapter. file name specifies the software file name of the adapter where the trap was detected. line number specifies the software line number where the traps were detected.
700 ATM Event Messages secondary subject specifies the secondary subject for the event as Amp-Process. group specifies the physical group location of the adapter. module specifies the physical module location of the adapter. slot specifies the physical slot location of the adapter. dump file name specifies the dump file. oxblock address specifies the address of the dump block. block size specifies the size of the dump block. symptom string specifies where in the software the error was detected.
701 ATM Event Messages event displayed as Line-Started. reason specifies the reason the object became available. state in the previous state field, state specifies the state the object was in before becoming available. In the current state field, state specifies the state of the object after it became available. manager name specifies the ASM. text provides additional information about the event. Cause. An SCF START command was successfully processed or the ATM subsystem internally started the object.
800 ATM Event Messages state in the previous state field, state specifies the state the object was in before becoming unavailable. In the current state field, state specifies the state of the object after it became unavailable. manager name specifies the ASM. text provides additional information about the event. Cause. An SCF ABORT command was successfully processed or the ATM subsystem internally aborted the object. Effect. The ATM subsystem cannot access the object. Recovery. None.
801 ATM Event Messages Cause. An SCF START command was successfully processed or the ATM subsystem internally started the object. Effect. The ATM subsystem can access the object. Recovery. None. This is an informational event.
1000 ATM Event Messages 1000 01000 Object Available subject, Event Number: event, Reason: reason, Previous State: state, Current State: state, [, Manager: manager name ] [ Batch ID: jobid ] [, User Content: text ] subject specifies the subject for the event as ATM-Pvc. event displayed as Pvc-Started. reason specifies the reason the object became available. state in the previous state field, state specifies the state the object was in before becoming available.
1006 ATM Event Messages event displayed as Pvc-Stopped. reason specifies the reason the object became unavailable. state in the previous state field, state specifies the state the object was in before becoming unavailable. In the current state field, state specifies the state of the object after it became unavailable. manager name specifies the ASM. text provides additional information about the event. Cause.
1200 ATM Event Messages 1200 01200 ATM: ATMDIH Error subject, Severity: severity, [, secondary subject ], Procedure: procedure name, Error: error [, Sympton String: symptom string ] [, Reporting Method: reporting method ] subject specifies the subject for the event. The possible values are: Atm-Adapter Atm-Line Atm-Atmsap Amp-Process severity specifies the severity of the event. The possible values are: Indeterminate Critical secondary subject specifies the secondary subject for the event.
1201 ATM Event Messages 1201 01201 ATM: ATMDIH STRUCT Error subject, Procedure: procedure name, Struct-Addr: structure address [, Symptom String: symptom string ] [, Reporting Method: reporting method ] subject specifies the subject for the event as Atm-DIH-Client. procedure name specifies the name of the procedure which returned the error. structure address specifies the structure address. symptom string specifies where in the software the error was detected.
1400 ATM Event Messages AtmDih-Receive-Error AtmDih-Send-Error AtmDih-Qio-Msg AtmDih-C2H-Tpmp AtmDih-PTC2H-Interrupt AtmDih-Msg-Unknown AtmDih-Q-Full-Msg AtmDih-Path-Switch AtmDih-Buffer-Path-Enable AtmDih-Snet-Paths-Disabled AtmDih-Snet-Paths-Disabled AtmDih-Set-XFer-Path secondary subject specifies the secondary subject for the event as ATM-Adapter. procedure Id specifies the procedure ID where the event was generated. Cause. Specifies the process encountered an internal error. Effect.
1400 ATM Event Messages secondary subject specifies the secondary subject for the event. procedure name specifies the name of the procedure which returned the error. error specifies the error returned from the shared memory procedure. SM Lib Version specifies the version of the shared memory library (SMLIB). module Id specifies the shared memory module ID. queue name specifies the queue name. queue Id specifies the shared memory queue ID. mdlen specifies the message descriptor length.
1500 ATM Event Messages 1500 01500 Object Available subject, Event Number: event, Reason: reason, Previous State: state, Current State: state, [, Manager: manager name ] [, Batch ID: jobid ] [, User Content: text ] subject specifies the subject for the event as ATM-Process. event displayed as SNet-Path-Available. reason specifies the reason the object became available. state in the previous state field, state specifies the state the object was in before becoming available.
1600 ATM Event Messages event displayed as SNet-Path-Unavailable. reason specifies the reason the object became unavailable. state in the previous state field, state specifies the state the object was in before becoming unavailable. In the current state field, state specifies the state of the object after it became unavailable. manager name specifies the ASM. text provides additional information about the event. Cause.
1700 ATM Event Messages reporting method specifies where in the software the event was generated. Cause. Specifies the process encountered an internal error. Effect. The process was unable to continue. Recovery. This error is serious. Contact your service provider. 1700 01700 ATM: SIG Error subject, Procedure: procedure name, Error: error [, Symptom String: symptom string ] [, Reporting Method: reporting method ] subject specifies the subject for the event as Atm-DIH-Client.
1801 ATM Event Messages 1801 01801 ATM: Internal DSM Object Error subject, Severity: severity, secondary subject, Text: text, Error: error, Error Detail: error Detail [, ObjName: object name] [, ObjState: object state] [, Superior ObjName: superior object name] [, Superior ObjType: superior object type] [, Superior ObjState: superior object state] [, Symptom String: symptom string] [, Reporting method: reporting method] subject specifies the subject for the event as Amp-Process.
1802 ATM Event Messages superior object name specifies the superior object name. superior object type specifies the DSM defined object type of the superior object. superior object state specifies the DSM summary state of the superior object. symptom string specifies where the error was detected. reporting method specifies where the error was generated. Cause. Specifies the process encountered an internal error related to DSM object. Effect.
1803 ATM Event Messages error specifies the ATM subsystem defined error code. error detail specifies the detail of the error. object type specifies a DSM object type supported by the ATM subsystem. symptom string specifies where the error was detected. reporting method specifies where the error was generated. Cause. Specifies the process encountered an internal error relating to an object manager. Effect. The operation or request being processed is terminated with an error. Recovery.
1804 ATM Event Messages error specifies the ATM subsystem defined error code. error detail specifies the detail of the error. timer name specifies the timer name. timer Id specifies the timer ID. timer tag specifies the internal tag value used by the timer. request Id specifies the request ID. symptom string specifies where the error was detected. reporting method specifies where in the software the error was generated. Cause.
1804 ATM Event Messages severity specifies the severity of the event. The possible values are: Indeterminate Critical secondary subject specifies the secondary subject for the event as Atm-Adapter. text provides additional informational about the cause for the event. error specifies the ATM subsystem defined error code. error detail specifies the detail of the error. state specifies the current state of the state machine displayed as a number.
1805 ATM Event Messages symptom string specifies where in the software the error was detected. reporting method specifies where in the software the error was generated. Cause. Specifies the process encountered an internal error relating to the AMP’s state-machine. Effect. The operation or request being process is terminated with an error. Recovery. This error is serious. Contact your service provider.
1806 ATM Event Messages queue Id specifies the queue ID. symptom string specifies where the error was detected. reporting method specifies where the error was generated. Cause. Specifies the process encountered an internal error related to a shared memory queue. Effect. The operation or request being processed is terminated with an error. Recovery. This error is serious. Contact your service provider.
1807 ATM Event Messages error detail specifies the detail of the error. received length specifies the received length for the request. expected length specifies the expected length for the request. symptom string specifies where in the software the error was detected. reporting method specifies where in the software the error was generated. Cause. Specifies the process encountered an internal error while processing a request from the ASM. Effect. The request from the ASM will be rejected with an error.
1900 ATM Event Messages error specifies the ATM subsystem defined error code. allocated length specifies the allocated length for the response. used length specifies the current used length of the response. token code specifies the token code being processed. token length specifies the token length for the request. symptom string specifies where the error was detected. reporting method specifies where the error was generated. Cause.
1901 ATM Event Messages atmsap name specifies the ATMSAP name. Cause. Specifies the process encountered an internal error. Effect. The process was able to continue. Recovery. None. This is an informational event. 1901 01901 ATM: Slam Event subject, Slam Event: event, Occurrences: occurrences, First Time: first time, Last Time: last time [, Msg: message ] subject specifies the subject for the event as Atm-Adapter. event specifies the adapter defined event.
1902 ATM Event Messages 1902 01902 ATM: Slam Response Error subject, Severity: severity [,secondary subject], Text: text, Error: error, Error Detail: error detail [, Received Len: received length] [, Token Code: token code, Token Len: token length] [, Expected Length: expected length] [Client name: client name] [Obj Name: object name, type: object type] [Source RouteId: source route Id, Service Id: service Id, Function: function, Modifier: modifier, Misc: Misc, Request Id: request Id, Route Id: route Id,
1902 ATM Event Messages token code specifies the received token code. token length specifies the received token length. expected length specifies the expected token length. client name specifies the client which received the response. object name specifies the object name. object type specifies the object type. symptom string specifies where the error was detected. reporting method specifies where the error was generated.
1903 ATM Event Messages The following information describes the information received in the AMP/Adapter Interface Management message header: Message Header Description mgmtVersion Version mgmtCommand Command mgmtObjType Object type mgmtObjName Object name mgmtError Management error mgmtErrorQualifier Management error qualifier mgmtNextObjType Next object name mgmtNextObjName Next object type Cause.
1903 ATM Event Messages text provides additional information about the cause for the event. error specifies the ATM subsystem defined error code. error detail specifies the detail of the error. request Id specifies the request ID. symptom string specifies where the error was detected. reporting method specifies where the error was generated. Cause. Specifies the process encountered an internal error while generating a request to the adapter. Effect. A request or message is not sent to the adapter.
1903 ATM Event Messages ATM Configuration and Management Manual— 522307-003 B -56
C Tracing for QIO TRACE Command The TRACE command initiates trace mode on the specified object. You can use the TRACE command as a diagnostic tool. This is a sensitive command. An SCF trace produces a trace file that can be displayed using the commands available in the PTrace program. SCP creates the trace file. For more information on PTrace, see the PTrace Reference Manual.
TRACE ADAPTER Command Tracing for QIO STOP discontinues the trace currently in progress. If BACKUP is specified, only the backup process trace is stopped. BULKIO | NOBULKIO designates whether or not TRACE should use bulk I/O for tracing. BULKIO specifies that the TRACE collector use Bulk I/O to write data to the disk file, thus reducing the number of missing frame errors reported by PTrace. A limitation of Bulk I/O is that only one user can access the file at a time.
TRACE ADAPTER Command Tracing for QIO RECSIZE size specifies the length of the data in the trace data records. size is an integer in the range 500 through 4050, and zero. The length of the trace header, which is eight bytes, is not included in size. If RECSIZE is omitted or if size equals zero, the default value of 120 bytes is assumed. SELECT select-spec select-spec is one: { { { { keyword } ( keyword [ , keyword ] ... ) } number } ( number [ , number ] ... ) } keyword is subsystem-specific.
Tracing for QIO TRACE ADAPTER Command ATM Configuration and Management Manual— 522307-003 C- 4
D ATM Error Codes ATM Driver Error Codes Error Error Code (page 1 of 2) ZATM_DR_ERR_ATMSAP_EXISTS 510 ZATM_DR_ERR_ATMSAP_INUSE 511 ZATM_DR_ERR_ATMSAP_NOT_AVAILABLE 512 ZATM_DR_ERR_ATMSAP_NOT_DOWN 513 ZATM_DR_ERR_ATMSAP_NOT_FOUND 514 ZATM_DR_ERR_ATMSAP_NOT_REGD 515 ZATM_DR_ERR_ATMSAP_REGD_ALREADY 516 ZATM_DR_ERR_EP_NOT_FOUND 517 ZATM_DR_ERR_DEV_DOWN 518 ZATM_DR_ERR_DEV_NOT_FOUND 519 ZATM_DR_ERR_INVALID_EPQ 520 ZATM_DR_ERR_INVALID_QNAME 521 ZATM_DR_ERR_INVALID_NAME_LENGTH 522 ZAT
ATM Driver Error Codes ATM Error Codes Error Error Code (page 2 of 2) ZATM_DR_ERR_BUFMAP_FAIL 542 ZATM_DR_ERR_NULL_MD_CHAIN 543 ZATM_DR_ERR_INIT_BUFD_FAIL 544 ZATM_DR_ERR_GET_STATUS_FAILED 545 ZATM_DR_ERR_FETCH_FIRMWARE_FAILED 546 ZATM_DR_ERR_ENBL_INTERRUPT 547 ZATM_DR_ERR_DUMP_RAM_FAILED 548 ZATM_DR_ERR_INVALID_BOOT_STATE 549 ZATM_DR_ERR_INVALID_ADAPTER_TYPE 550 ZATM_DR_ERR_CONFIG_CRU_FETCH_FAILED 551 ATM Configuration and Management Manual— 522307-003 D- 2
ATM Signaling Error Codes ATM Error Codes ATM Signaling Error Codes Error Error Code ZATM_DR_ERR_CONFIG_CRU_FETCH_FAILED 1000 ZATM_SIG_ERR_ATMSAP_ALREADY_REGISTERED 1001 ZATM_SIG_ERR_ATMSAP_NOT_REGISTERED 1002 ZATM_SIG_ERR_ATMSAP_IN_USE 1003 ZATM_SIG_ERR_ATMSAP_IN_WRONG_STATE 1004 ZATM_SIG_ERR_ATMSAP_NOT_FOUND 1005 ZATM_SIG_ERR_ATMSAP_REGISTER_DENIED 1006 ZATM_SIG_ERR_INV_CONNID 1007 ZATM_SIG_ERR_INV_POINTER 1008 ZATM_SIG_ERR_BAD_MSG 1009 ZATM_SIG_ERR_PVC_NOT_FOUND 1010 ZATM_SIG_ER
ATM API Error Codes ATM Error Codes Error Error Code (page 2 of 2) ZATM_API_ERR_MATCH_NOT_FOUND 2013 ZATM_API_ERR_SET_OPTION_COMPLETE 2014 ZATM_API_ERR_SET_OPTION_WAIT 2015 ZATM_API_ERR_ENDPOINT_SIG_RELEASED 2016 ZATM_API_ERR_ENDPOINT_NOT_CONNECTED 2017 ZATM_API_ERR_DEV_NOT_FOUND 2018 ZATM_API_ERR_CREATE_EP_FAILED 2019 ZATM_API_ERR_DR_REG_FAILED 2020 ZATM_API_ERR_DR_DEREG_FAILED 2021 ZATM_API_ERR_SIG_REG_FAILED 2022 ZATM_API_ERR_SIG_DEREG_FAILED 2023 ZATM_API_ERR_PUT_POOL_FAILED 2
ATM Network Error Code ATM Error Codes ATM Network Error Code Error Error Code (page 1 of 2) UnallocatedNumber 20001 NoRouteToSpecifiedTransit 20002 NoRouteToDest 20003 UnacceptableVPCI_VCI 20010 Normal 20016 UserBusy 20017 NoUserResponding 20018 CallRejected 20021 NumberChanged 20022 UserRejectsCLIRCalls 20023 DestinationOutOfOrder 20027 InvalidNumberFormat 20028 ResponseToStatusEnquiry 20030 Normal_Unspecified 20031 RequestedVPCIUnavailable 20035 VPCIAssignmentFailure 20
ATM Network Error Code ATM Error Codes Error Error Code (page 2 of 2) InvalidEndpointReference 20089 InvalidTransitNetSelection 20091 TooManyPendingAddPartyReqs 20092 AALParamsCantBeSupported_30 20093 MandatoryInfoElementMissing 20096 MessageTypeNonexistent 20097 InfoElemNonexistent 20099 InvalidInfoElemContents 20100 MessageCallStateNotComp 20101 RecoveryOnTimer 20102 IncorrectMessageLength 20104 UnspecifiedProtocolError 20111 ATM Configuration and Management Manual— 522307-003
Glossary 3865 Gigabit Ethernet ServerNet adapter (GESA). See Gigabit Ethernet ServerNet adapter (GESA). AAL. See ATM Adaptation Layer (AAL). AAL-5. See ATM Adaptation Layer Type 5 (AAL-5). adapter. See ServerNet adapter. Address Resolution Protocol (ARP) . The procedures and messages in a communications protocol that determine which physical network address corresponds to the IP address in the packet. AMP. See ATM Management Process (AMP). API. See application program interface (API).
ATM Address Glossary ATM Address. Defined in the UNI specification as 3 formats, each having 20 bytes in length including country, area and end-system identifiers. ATM Management Process (AMP). The process provided as part of the ATM subsystem that initializes the shared-memory interface, initializes the XIO subsystem, creates and monitors the Signaling Manager Process, initializes and downloads the ATM adapter, and provides configuration information to the ATM adapter. ATM Subsystem Manager (ASM).
Class-2 CRU Glossary Class-2 CRU. A customer-replaceable unit (CRU) that might cause a partial or total system outage if the documented replacement procedure is not followed correctly. Customers replacing Class-2 CRUs should have either three or more months of experience replacing NonStop S-series CRUs or equivalent training. Customers must be able to use the tools needed for the replacement procedure and must protect components from electrostatic discharge (ESD). Class-3 CRU.
connection Glossary CONFSAVE. See also system configuration database. In RVUs prior to the G-series, the configuration file is either the OSCONFIG file used by the Configuration Utility Program (COUP) or the CONFTEXT file used during system generation. connection. (1) The path between two protocol modules that provides reliable stream delivery service.
EEPROM Glossary EEPROM . See electrically erasable programmable read-only memory. electrically erasable programmable read-only memory. A type of PROM that is electrically reprogrammable in circuit but large chunks of it must be erased before new data is programmed in. EEPROM is often referred to as flash PROM. ELF. See extended link format (ELF). EMS collector. An Event Management Service (EMS) process to which subsystems report events. enclosure. Similar to a cabinet in NonStop S-series systems.
expansion service processor (ESP) Glossary expansion service processor (ESP). A service processor (SP) that is not a master service processor (MSP). ESPs occur in pairs in groups 02 through nn (not in group 01). See also master service processor (MSP). explicit DLL. See explicit dynamic-link library (explicit DLL). explicit dynamic-link library (explicit DLL). A dynamic-link library (DLL) that is named in the libList of a client or is a native-compiled loadfile associated with a client. export.
file transfer protocol (FTP) Glossary In the Guardian environment, disk file names include a node name, volume name, subvolume name, and file identifier; for example, \NODE.$DISK.SUBVOL.MYFILE. In the Open System Services (OSS) environment, a file is identified by a pathname; for example, /usr/john/workfile. See also filename. file transfer protocol (FTP). (1) The Internet-standard, high-level protocol for transferring files from one machine to another.
gigabyte (GB) Glossary • 3865 GESA-F (T523572): a single-port fiber version compliant with the 1000 Base-SX standard (802..z) gigabyte (GB). A unit of measurement equal to 1,073,741,824 bytes (1024 megabytes). See also kilobyte (KB), megabyte (MB), and terabyte (TB). global offset table (GOT). A table of indirect addresses of data, including function descriptors, that might reside in a different loadfile. The GOT is an artifact of the native compiler. globalized.
IEEE 802.5 Glossary IEEE 802.5. A Local Area Network protocol suite commonly known as Token Ring. A standard originated by IBM for a token passing ring network that can be configured in a star topology. Versions supported are 4 Mbps and 16 Mbps. implicit library. A library supplied by HP that is available in the read-only and execute-only globally mapped address space shared by all processes without being specified to the linker or loader. See also TNS system library and public library.
instance data Glossary instance data. For each process using a dynamic-link library, a data segment area containing the global variables used by the library. interactive mode. A mode of operation that is characterized by having the same input and output device (a terminal or a process) for the session. If a terminal is used, a person enters a command and presses RETURN.
LED Glossary • • The loader resolves a symbol that is unresolved by any loadfile on the linker searchList. The loader binds a symbol in a DLL to the first definition it finds on the program’s loadList, and this is not the first definition that was encountered on the linker searchList. For localized loadfiles, the linker and loader searchLists are the same, so late binding does not occur. LED. See light-emitting diode (LED). light-emitting diode (LED).
linking Glossary executable loadfile for a program or library. Compiling creates one linkfile per independent source module. Contrast with loadfile. linking. The operation of collecting, connecting, and relocating code and data blocks from one or more separately compiled object files to produce a target object file. local area network (LAN).
master service processor (MSP) Glossary is logically part of each subsystem. SCP is the management process for all subsystems controlled by SCF. master service processor (MSP). A service processor (SP) that provides the basic service processor functions as well as centralized system functions such as a console port, a modem port for remote support functions, and system-load control. The enclosure containing processors 0 and 1 (group 01) also contains a pair of MSPs.
Network Service Access Point (NSAP) Glossary Network Service Access Point (NSAP). The OSI generic standard for a network address consisting of 20 octets. ATM has specified E.164 for public network addressing and the NSAP address structure for private network addresses. noninteractive mode. A mode of operation that usually involves a command file (an EDIT file that contains a series of commands). See also interactive mode. nonsensitive command.
operating system (OS) Glossary operating system (OS). An organized collection of software that controls the basic operations of a computer system. The operating system on NonStop servers is the NonStop Kernel. operator message. A message, intended for an operator, that describes a significant event on a NonStop system. An operator message is the displayed-text form of an EMS event message. ordinary library. A dynamic-link library (DLL) or shared run-time library (SRL) that is not public.
position-independent code (PIC) Glossary position-independent code (PIC). Executable program or library code that is designed to be loaded and executed at any virtual memory address, without any modification. Addresses that can be modified by the loader do not appear in PIC code, only in data that can be modified by the loader. See also dynamic-link library (DLL). preset. A linker operation that sets the correct values (addresses) of imported symbols according to the environment seen by the linker.
public dynamic-link library (public DLL) Glossary public dynamic-link library (public DLL). Optional native-mode executable code modules available to all native user processes. A public library that is specified in the public library registry, supplied by HP or, optionally, a user. Contrast with ordinary dynamic-link library (ordinary DLL). public library.
run-time linker Glossary run-time linker. See linker. run-time loader. See loader. RVU. See release version update (RVU). SAAL. See Signaling ATM Adaptation Layer (SAAL). SAC. See ServerNet addressable controller (SAC). SAP. See service access point (SAP). SCF. See Subsystem Control Facility (SCF). searchList. For each loadfile, a list that is constructed and used by the linker and loader to tell them which libraries to examine, and in which order, to locate symbol definitions needed by that loadfile.
Glossary ServerNet LAN systems access (SLSA) subsystem ServerNet LAN systems access (SLSA) subsystem. A subsystem of the NonStop Kernel operating system for configuration and management of ServerNet local area network (LAN) objects in G-series release version updates (RVUs). ServerNet router. An application-specific integrated circuit (ASIC) responsible for routing ServerNet packets along ServerNet links in the ServerNet fabrics, using routing information that is present within the packets.
service provider Glossary service provider. (1) A person trained and qualified to service field-replaceable units (FRUs). (2) An organization, such as the Global Customer Support Center (GCSC), that helps you resolve problems with your NonStop S-series server. OSM and TSM allow you to use the help of a service provider by configuring client software to support remote notification and remote access. service specific connection oriented protocols (SSCOP).
SRL Glossary SRL. See shared run-time library (SRL). SSCOP. See service specific connection oriented protocols (SSCOP). state. In SCF, one of the generally defined possible conditions of an object with respect to the management of that object. Examples of states are DEFINED, STARTED, and STOPPED. storage pool. A set of physical disk volumes administered as a set of logical disk volumes. A logical disk volume can span multiple physical disk volumes.
subsystem manager Glossary subsystem manager. An SCF process that performs configuration and management functions for an SCF subsystem. SVC. See Switched Virtual Circuit (SVC). SWAN. See ServerNet wide area network (SWAN) concentrator. Switched Virtual Circuit (SVC). A connection established via signaling. The user defines the endpoints when the call is initiated. symbol. (1) The symbolic name of a value, typically a function entry point or a data location.
system configuration database Glossary system configuration database. The database file on the $SYSTEM.ZSYSCONF subvolume that contains configuration information for all system objects that can be configured by the Subsystem Control Facility (SCF). Configuration information for all system objects that can be configured during system generation is contained on the $SYSTEM.SYSnn subvolume. See also configuration file and SYSnn subvolume. system enclosure. An enclosure for system components.
Transmission Control Protocol/Internet Protocol (TCP/IP) Glossary Transmission Control Protocol/Internet Protocol (TCP/IP). A set of layered communication protocols for connecting workstations and larger systems in both local area networks (LANs) and wide area networks (WANs). See also HP NonStop TCP/IP and Parallel Library TCP/IP. TSM package. See Compaq TSM package UBR. See Unspecified Bit Rate (UBR). UDP. See User Datagram Protocol (UDP). UNI. See User-Network Interface (UNI).
wide area network (WAN) Glossary wide area network (WAN). A network that operates over a larger geographical area than that provided by a LAN. The elements of a WAN may be separated by distances great enough to require telephone communications. Contrast with local area network (LAN). wild-card character. A character that stands for any possible character or characters in a search string or in a name applying to multiple objects.
$ZZATM Glossary ATM Configuration and Management Manual— 522307-003 Glossary -26
Index A ABORT ADAPTER command 4-20 ABORT ATMSAP command 4-22 ABORT LINE command 4-23 ABORT PVC command 4-24 ABORT SUBSYS command 4-25 ABORT SVC command 4-26 Adapters, installing 1-3 ADD ADAPTER command 1-3 ADD command 4-27 ALTER ADAPTER command 4-33 ALTER command 4-33 ALTER LINE command 3-14, 4-37 ALTER PVC command 4-40 ATM Manager Process 2-8 ATM service providers 2-4, 2-5 ATM subsystem architecture 2-4 components of 4-17 Automatic address registration 2-10 C Cells, ATM 2-3 Changing input source 4-12 outp
F Index Example (continued) NAMES ATMSAP command 4-61 NAMES LINE command 4-62 NAMES PROCESS command 4-63 NAMES PVC command 4-63 NAMES SUBSYS command 4-64 START ADAPTER command 4-66 START ATMSAP command 4-67 START PVC command 4-69 START SUBSYS command 4-70 STATS ATMSAP command 4-72 STATS LINE command 4-74 STATS PROCESS command 4-77 STATS PVC command 4-78 STATS SVC command 4-80 STATUS ADAPTER command 4-83 STATUS ATMSAP command 4-85 STATUS LINE command 4-87 STATUS PROCESS command 4-90 STATUS SUBSYS command 4
N Index N S NAMES ADAPTER command 4-60 NAMES ATMSAP command 4-61 NAMES command 4-60 NAMES LINE command 4-62 NAMES PROCESS command 4-63 NAMES PVC command 4-63 NAMES SUBSYS command 4-64 Nested command files 4-13 Noninteractive mode command-line mode 4-12 defined 4-11 specified by NOWAIT option 4-9 Nonsensitive commands 4-4 definition 4-4 SAN 2-5 SCF ATM subsystem 4-16 command file 4-12 commands, general format of 4-6 ending a session 4-10 generic processes 4-19 input sources 4-12 nonsensitive commands 4-
T Index STATS LINE command 4-72 display 4-73 STATS PROCESS command 4-74 display 4-75 STATS PVC command 4-77 display 4-78 STATS SVC command 4-78 display 4-79 STATUS ADAPTER command 4-80 display 4-81 STATUS ATMSAP command 4-84 display 4-84, 4-85 STATUS command 4-80 STATUS LINE command 4-85 display 4-86 STATUS PROCESS command 4-87 display 4-87 STATUS PVC command 4-91 display 4-91 STATUS SUBSYS command 4-92 display 4-93 STATUS SVC command 4-96 display 4-96 SUB parameter 4-6 Subordinate objects 4-6 Subsystem C
