PAM Configuration and Management Manual Abstract This manual describes the Port Access Method (PAM) subsystem, which allows applications running on HP NonStop™ S-series servers and HP Integrity NonStop™ NS-series servers access to Ethernet and token-ring networks. This manual is written for systems managers, operators, and others who configure and manage network subsystems on NonStop S-series servers and Integrity NonStop NS-series servers.
Document History Part Number Product Version Published 120564 Port Access Method G05 February 1998 142480 Port Access Method G06 August 1998 523349-001 Port Access Method G06 February 2002 523349-002 Port Access Method G06 December 2004 523349-003 Port Access Method G06 October 2005
PAM Configuration and Management Manual Index Figures What’s New in This Manual vii Manual Information vii New and Changed Information About This Manual ix Who Should Use This Manual What’s in This Manual ix Other Manuals ix Notation Conventions x Abbreviations xiii Tables vii ix 1.
3. SCF for PAM Contents 3.
3. SCF for PAM (continued) Contents 3.
C. SCF Error Messages Contents C.
Figures Contents Figures Figure 2-1. Figure 2-2. Figure 2-3. Figure 2-4. Figure 3-1. PAM Components 2-2 PAM Process and EMS 2-5 PAM SCF Object Hierarchy 2-8 PAM Programmatic Interfaces 2-10 PAM SCF Object Hierarchy 3-4 Tables Table i. Table 2-1. Table 3-1. Table 3-2. Table 3-3. Table A-1. Table A-2. Table A-3.
Tables Contents PAM Configuration and Management Manual—523349-003 vi
What’s New in This Manual Manual Information PAM Configuration and Management Manual Abstract This manual describes the Port Access Method (PAM) subsystem, which allows applications running on HP NonStop™ S-series servers and HP Integrity NonStop™ NS-series servers access to Ethernet and token-ring networks. This manual is written for systems managers, operators, and others who configure and manage network subsystems on NonStop S-series servers and Integrity NonStop NS-series servers.
What’s New in This Manual New and Changed Information PAM Configuration and Management Manual—523349-003 viii
About This Manual This manual describes how to configure and operate the PAM subsystem on a NonStop S-series server and on an Integrity NonStop NS-series server. It includes detailed descriptions of the Subsystem Control Facility (SCF) commands used with the PAM subsystem and a quick-reference section to the command syntax.
Notation Conventions About This Manual Notation Conventions General Syntax Notation The following list summarizes the notation conventions for syntax presentation in this manual. UPPERCASE LETTERS. Uppercase letters indicate keywords and reserved words; enter these items exactly as shown. Items not enclosed in brackets are required. For example: MAXATTACH lowercase italic letters. Lowercase italic letters indicate variable items that you supply. Items not enclosed in brackets are required.
Notation for Messages About This Manual … Ellipsis. An ellipsis immediately following a pair of brackets or braces indicates that you can repeat the enclosed sequence of syntax items any number of times. For example: M address-1 [ , new-value ]... [ - ] {0|1|2|3|4|5|6|7|8|9}... An ellipsis immediately following a single syntax item indicates that you can repeat that syntax item any number of times. For example: "s-char..." Punctuation.
Change Bar Notation About This Manual lowercase italic letters. Lowercase italic letters indicate variable items whose values are displayed or returned. For example: p-register process-name [ ] Brackets. Brackets enclose items that are sometimes, but not always, displayed. For example: Event number = number [ Subject = first-subject-value ] A group of items enclosed in brackets is a list of all possible items that can be displayed, of which one or none might actually be displayed.
Abbreviations About This Manual The CRE has many new message types and some new message type codes for old message types. In the CRE, the message type SYSTEM includes all messages except LOGICAL-CLOSE and LOGICAL-OPEN. Abbreviations E4SA. Ethernet 4 ServerNet adapter MD. Message descriptor PAM. Port Access Method SAP. Service access point SCF. Subsystem Control Facility SDU. Service data unit SLSA. ServerNet LAN systems access SPI. Subsystem Programmatic Interface TLAM. HP Tandem LAN access method TRSA.
Abbreviations About This Manual PAM Configuration and Management Manual—523349-003 xiv
1 Configuration Quick Start This section provides PAM startup examples using the persistence manager and HP Tandem Advanced Command Language (TACL) and configuration examples for SNAX and port clients. If you prefer to read introductory material about PAM before proceeding with this quick start, see Section 2, Introduction. Task Summary: Configuring PAM 1. Start the PAM manager process. 2. Select a running LIF and determine the primary and backup processors. 3.
Task 3: Start PAM Using the Persistence Manager Configuration Quick Start This display shows the results of STATUS LIF $ZZLAN.lif-name. (The possible primary and backup processors are 0, 1, 2, and 3): SLSA Detailed Status LIF \SYSTEM.$ZZLAN.LAN01 Access State............... CPUs with Data Path........ Potential Access CPUs...... State...................... Trace Filename............. Trace Status............... UP ( 0, 1, 2, 3) ( 0, 1, 2, 3) STARTED Task 3: Start PAM Using the Persistence Manager 1.
Task 4: Configure the PORT Interface Configuration Quick Start Task 4: Configure the PORT Interface 1. Assume the PAM process. ->ASSUME LINE $PAM1 2. Start the LINE object. (Skip this step if you specified STARTUP in Task 2.) ->START LINE $PAM1 3. Add a PORT object. ->ADD PORT $PAM1.#EPORT1, ADDRESS %H0808, TYPE ETHERNET 4. Start the PORT object. ->START PORT $PAM1.#EPORT1 Task 5: Configure the MSAP Interface for PAM Over Token Ring Skip this task if you specified MSAPSTARTUP in Task 2. 1.
Configuration Quick Start Task 5: Configure the MSAP Interface for PAM Over Token Ring PAM Configuration and Management Manual—523349-003 1 -4
2 Introduction This section provides an overview of PAM and of the facilities for managing PAM. It includes these topics: • • • Overview of Features and Architecture explains the role of PAM within the system and describes the features, standards compliance, and components of PAM. Distributed Systems Management (DSM) Facilities on page 2-6 provides an overview of all aspects of PAM subsystem management. Startup Parameters on page 2-12 describes how to start the PAM subsystem.
The PAM Subsystem’s Role Within the System Introduction (TRSA) provide the LAN connections on NonStop S-series servers and Integrity NonStop NS-series servers. The PAM Subsystem’s Role Within the System The PAM subsystem consists only of software processes and interfaces and uses the services provided by the SLSA subsystem to access the Ethernet and token-ring LANs connected to the NonStop S-series server and the Integrity NonStop NS-series server.
The PAM Subsystem’s Role Within the System Introduction PAM Components The components of the PAM subsystem (shown in Figure 2-1 on page 2-2) are: • • • • • • • • • PAM clients on page 2-3 A file-system interface on page 2-3 for applications that need to access the port A message-system interface (on page 2-3) that enables the SNAX Extended Facility (SNAX/XF) or the SNAX Advanced Peer Networking (SNAX/APN) products to access the TRSA The SPI on page 2-4 for management applications and event management Th
The PAM Subsystem’s Role Within the System Introduction Management Interfaces The PAM management interfaces consist of the Subsystem Control Facility (SCF) and SPI. SCF provides an interactive interface for control-and-inquiry and accesses the PAM subsystem through SPI. SPI transfers SCF commands to the PAM subsystem and also provides an interface for writing management applications that perform control-and-inquiry and event management.
The PAM Subsystem’s Role Within the System Introduction Figure 2-2. PAM Process and EMS Management Application 3 Filter Consumer Distributor 4 Event Log 2 1 Event Collector ($0) Event Messages PAM VST0202.vsd The event-management activities shown in Figure 2-2 occur as follows: 1. The PAM process reports the event by sending an event message to the local EMS event collector. 2. The EMS event collector sends the event message to the EMS event log. 3.
Distributed Systems Management (DSM) Facilities Introduction $ZZPAM through the SCP process and how $ZZPAM, in turn, communications with the PAM process. MFIOB (Multifunction I/O Board/Ethernet) The MFIOB is a ServerNet adapter that is integrated into the processor multifunction (PMF) CRU and the I/O multifunction (IOMF) CRU. The MFIOB provides testing functions.
Interactive Interfaces Introduction The SPI is used for building commands to, decoding responses from, and obtaining event messages issued by the PAM subsystem. The commands, responses, and event messages that are sent to and received from the PAM subsystem are made up of special codes called tokens. Each token contains a particular piece of information, such as the command number of a command or one element of an event message. Tokens can be single values or structures consisting of several values.
Interactive Interfaces Introduction Figure 2-3. PAM SCF Object Hierarchy PROCESS LINE PORT MSAP SNATR ETHERNET LLC1 LLC2 SESSION VST0203.vsd PROCESS Object The PAM PROCESS object determines whether a PAM process is running in the system. The PAM PROCESS object provides the interface to the ServerNet LAN Systems Access (SLSA) subsystem for Ethernet and token ring. The PAM process also generates EMS messages. A PAM process is associated with a LIF in the SLSA subsystem.
Interactive Interfaces Introduction Your application (other than SNAX over token-ring applications) uses the file system to communicate with the PAM subsystem. How your application interacts with PORTs is similar to how an application interacts with files. The application can open PORTs, perform reads and writes to exchange data with a remote LAN entity, then close them.
Management Commands Introduction Figure 2-4. PAM Programmatic Interfaces Use the File System Interface LLC2 appl. Ethernet appl. SNAX/TR appl. LLC1 appl. PORT Object Uses the Message System Interface LLC1 Ethernet LLC2 Port Interface PORT Object SESSION Object PAM E4SA or FESA TRSA MSAP Object TRSA VST0204.vsd SESSION Object The SESSION object defines the link station for LLC2-type connections and a SNAX session over a token-ring LAN.
Management Commands Introduction Table 2-1. PAM Management Commands Command Action ABORT Abruptly stops the operation of an object. ADD Defines an object to the subsystem. ALTER Changes the values of an object’s attributes. DELETE Removes an object definition from the subsystem. INFO Returns an object’s current attribute values. LISTOPENS Returns the process IDs of an object’s openers. NAMES Returns the fully qualified names specified by the object.
Management Commands Introduction • • • • LISTOPENS STATISTICS STATUS VERSION Startup Parameters PAM processes has one required and four optional parameters: LIF is the name of the LIF to the ServerNet LAN systems access (SLSA) subsystem. The LIF corresponds to the LIF on the adapter and, therefore, to one of the Ethernet or token-ring LANs attached to the system. A PAM process is needed for each LIF that the PAM subsystem uses.
Starting PAM Using the Persistence Manager Introduction QUE-DEPTH (or Q) is the maximum number of application messages PAM queues after it receives a queue-full indication from the SLSA LAN driver. Queue depth must be within the range of 256 through 4096. The default is 1024. Starting PAM Using the Persistence Manager Starting PAM through the persistence manager is recommended. The persistence manager starts the PAM process automatically when the system is brought up or the processor is reloaded.
Starting PAM Using TACL Introduction PAM Configuration and Management Manual—523349-003 2- 14
3 SCF for PAM This section describes the SCF commands you can use to manage PAM. Table 3-1 lists the SCF commands and objects that are applicable to the PAM subsystem (with page numbers indicating where the command is described). For a detailed description of SCF, refer to the SCF Reference Manual for G-Series RVUs or the SCF Reference Manual for H-Series RVUs. User-written DSM application programs can perform the same management functions using the DSM programmatic interface.
Sensitive and Nonsensitive Commands SCF for PAM Table 3-1. SCF Commands and Objects (page 2 of 2) Command Objects LINE MSAP STOP Command on page 3-56 X X TRACE Command on page 3-60 X VERSION Command on page 3-63 X null PORT PROCESS X X SESSION X Sensitive and Nonsensitive Commands Some SCF commands are sensitive, meaning that they can have detrimental effects if improperly used, so special qualification is required to use them.
SCF Object Definitions SCF for PAM SCF Object Definitions SCF for PAM supports the PROCESS, LINE, PORT, MSAP, and SESSION objects, which are defined here. PROCESS Object The PROCESS object is either the PAM manager process, $ZZPAM, which receives all SPI requests from your application, or any PAM process that you create to manage LINE objects. A PROCESS name must be preceded by a dollar sign ($) and consist of a maximum of seven alphanumeric characters, the first of which must be alphabetic.
NULL Object SCF for PAM A PORT name must be preceded by a pound sign (#) and consist of a maximum of seven alphanumeric characters, the first of which must be alphabetic. The PORT name must be qualified with its LINE name. An example of a PORT name is: $LAN01.#PORT1 NULL Object The null object type is not an actual object type. The term null is used to represent the lack of a specified object. Any SCF command that supports the null object type is issued without the specification of an object type.
SCF Object States SCF for PAM The PORT and the MSAP are on the same level but differ in the method with which clients access them. Clients that use the file system access the PORT, but clients that use the message system access the MSAP. SNAX over token ring is the only supported message-system client. The PORT and MSAP are related because PAM dynamically creates an LLC2-type PORT when SNAX sends an Open SAP request through the MSAP.
Generic Processes SCF for PAM Table 3-3. Possible Operational States for PAM Objects (page 2 of 2) Possible States Object STOPPING STOPPED STARTING STARTED SUSPENDED PORT X X X X X PROCESS X SESSION X X X X Generic Processes A generic process is created by the operating system or a user to perform a task. PAMMAN is a generic process controlled by the persistence manager. $ZZPAM and other PAM processes are also system-managed, generic processes.
ABORT MSAP Command SCF for PAM LINE line-name is the name of the line. LINE has the same name as the PAM PROCESS; for example, $PAMA. SUB [ ALL | NONE | ONLY ] directs the command at a set of subordinate objects. ONLY specifies that only the subordinate objects are affected. ALL specifies that the named object and the subordinate objects are affected. NONE specifies that none of the subordinate objects are affected.
ABORT PORT Command SCF for PAM SUB [ ALL | NONE | ONLY ] directs the command at a set of subordinate objects. ONLY specifies that only the subordinate objects are affected. ALL specifies that the named object and the subordinate objects are affected. NONE specifies that none of the subordinate objects are affected. SEL [NOT] state directs the command only to objects in the specified state or only to those not in the specified state. Valid states are STARTED, STARTING, STOPPED, STOPPING, and SUSPENDED.
ABORT PROCESS Command SCF for PAM SEL [NOT] state directs the command only to objects in the specified state or only to those not in the specified state. Valid states are STARTED, STARTING, STOPPED, STOPPING, and SUSPENDED. Considerations • • The ABORT PORT command aborts any openers on the file-system interface (if the port supports the file-system interface). If the port is LLC2, the ABORT PORT command aborts any SNAX sessions and deletes the port and sessions.
ABORT SESSION Command SCF for PAM Example This process aborts the process named $PAMA: ->ABORT PROCESS $PAMA ABORT SESSION Command The ABORT SESSION command halts the operation of the specified session as quickly as possible. Command Syntax ABORT [ /OUT file-spec/ ] SESSION session-name [, SEL [NOT] state ] OUT file-spec directs any SCF output generated for this command to the specified file. SESSION session-name is the name of the session. Considerations There are no considerations for this command.
ADD Command SCF for PAM ADD Command ADD is a sensitive command that defines an object to the PAM subsystem. The fully qualified name assigned to the created object must be unique. The ADD command changes the specified object from an unknown entity to a PAM object in the defined summary state. You do not have to use SCF interactively to add objects to the PAM environment.
ADD PORT Command SCF for PAM The value for the port address has these restrictions, depending on the type of port specified: • • • Ethernet port addresses must be a number greater than 1536 (%h 600). LLC1 port addresses must be an even number in the range 2 through 255. LLC2 port addresses must be a multiple of 4 in the range 0 through 255 (excluding 0). DATAFORWARDCOUNT count is the maximum number of inbound messages from LAN to be queued in PAM before they are delivered to the application.
ADD PORT Command SCF for PAM change a port’s GROUPMACADDRESS back to the adapter’s default MAC address. LLC2ENABLED allows LLC1 ports to provide send and receive access to LLC2 connection-oriented frames. The implementation of the LLC2 protocol is the responsibility of your application. Specifying the LLC2ENABLED attribute allows applications to send and receive LLC2-type frames over LLC2-enabled LLC1 ports.
ALTER Command SCF for PAM • You can have a maximum of 128 Ethernet ports, a maximum of 127 LLC1 ports, or a maximum of 63 LLC2 ports. However, the total maximum number of ports is 128 for a PAM process. (For example if you have 127 Ethernet ports, you would only be able to add one LLC1 port.) Examples This example adds an Ethernet port, #PORT1, to $PAMA: -> ADD PORT $PAMA.
ALTER PORT Command SCF for PAM Example This example sets the maximum number of ports to 50: ->ALTER MSAP $PAMA.#SNATR, MAXPORTS 50 ALTER PORT Command The ALTER PORT command alters the attributes of a PORT object.
ALTER PORT Command SCF for PAM is thousandths of a second (milliseconds). The valid range is 0.01 second (10 milliseconds) through 60 seconds. The decimal point is significant. Fractions of a second must be entered with a zero preceding the decimal point (for example, 0.01). If the message should wait indefinitely, the keyword INFINITE must be specified.
DELETE Command SCF for PAM DELETE Command The DELETE command is a sensitive command that removes objects from the subsystem. Only objects that were added with the ADD command can be deleted. DELETE PORT Command The DELETE PORT command removes the specified port from the PAM subsystem. Command Syntax DELETE [ /OUT file-spec/ ] PORT port-name OUT file-spec directs any SCF output generated for this command to the specified file. port-name is the name of the port.
INFO Command SCF for PAM INFO Command The INFO command is a nonsensitive command that displays the current or default attribute values for the specified objects. INFO LINE Command The INFO LINE command displays information about the LINE object. Command Syntax INFO [ /OUT file-spec/ ] LINE line-name [SUB , [ ALL | NONE | ONLY ] ] [ , SEL [ NOT ] state ] OUT file-spec directs any SCF output generated for this command to the specified file. LINE line-name is the name of the line.
INFO MSAP Command SCF for PAM INFO LINE Display The display for the INFO LINE command has this format: PAM Info LINE Name MAXREQUESTSIZE LIF NAME $LAN24 32000 LANTR1 LIF TYPE LIF MAC ADDRESS TR 08:00:8E:00:D1:95 Name is the name of the line. MAXREQUESTSIZE is the maximum file-system request size, in bytes, that can be accepted by the PAM process. LIF NAME is the name of the logical interface (LIF) for the line. For more information about LIFs, see the LAN Configuration and Management Manual.
INFO PORT Command SCF for PAM Example This example requests information about the MSAP object: -> INFO MSAP $PAM5.#SNATR INFO MSAP Display The display for the INFO MSAP #SNATR command has this format: INFO MSAP $PAM5.#SNATR Max Ports 63 Max Ports is the maximum number of ports that can be opened through this MSAP. INFO PORT Command The INFO PORT command displays the information about the PORT object.
INFO PORT Command SCF for PAM INFO PORT Display for LLC1 Ports The display for the INFO PORT command for LLC1 ports has this format: PAM INFO PORT $PAM1.#LLC1 TYPE................... LLC1 *ADDRESS 0008H *GROUPMACADDRESS........ *DELIVERYMODE........... SERIAL *REQUESTSIZE............ 32000 *DATAFORWARDTIME........ INFINITE *DATAFORWARDCOUNT....... 8 *LLC2ENABLED............. NO TYPE is the port type. ADDRESS is the address for all traffic through the port.
INFO PORT Command SCF for PAM REQUESTSIZE is the maximum size, in bytes, of a message that the port can write and read. This attribute’s value cannot be greater than the line’s MAXREQUESTSIZE. The minimum value that must be specified for this attribute is 49 bytes for LLC1-type ports. The range of values is 1 through 32000. The default value is 32000. DATAFORWARDTIME is the maximum amount of time an inbound message from the LAN should wait before it is delivered to the application.
INFO PORT Command SCF for PAM REQUESTSIZE is the maximum size, in bytes, of a message that the port can write and read. This attribute’s value cannot be greater than the line’s MAXREQUESTSIZE. The minimum value that must be specified for this attribute is 32 bytes for Ethernet-type ports and 49 bytes for LLC1-type ports. The range of values is 1 through 32000. The default is 32000.
INFO PORT Command SCF for PAM INFO PORT Display for Ethernet Ports The display for the INFO PORT command for Ethernet ports has this format: PAM Info PORT $LAN54.#E1P2056 TYPE.................... ETHERNET *ADDRESS................ 0808H *GROUPMACADDRESS........ *DELIVERYMODE........... SERIAL *REQUESTSIZE............ 32000 *DATAFORWARDTIME........ INFINITE *DATAFORWARDCOUNT....... 1 TYPE is the port type. ADDRESS is the address for all traffic through the port.
LISTOPENS Command SCF for PAM DATAFORWARDTIME is the maximum amount of time an inbound message from the LAN should wait before it is delivered to the application. The value must be specified in HH:MM:SS.xxx format, where HH is hours, MM is minutes, SS is seconds, and xxx is thousandths of a second (milliseconds). The valid range is 0.01 second (10 milliseconds) through 60 seconds. The decimal point is significant.
NAMES Command SCF for PAM Example This example requests a list of the open sessions for the specified port: -> LISTOPENS PORT $PAM1.#LL4309 LISTOPENS PORT Display The display for the LISTOPENS PORT command has this format: PAM Listopens PORT $PAM1.#LL4309 Openers $TRMP PPID 2,107 BPID 5,097 Openers is a list of the names of processes that have opened the PORT object. PPID and BPID are the primary-process and backup-process IDs associated with the openers of the PORT object.
NAMES null Command SCF for PAM ALL specifies that the named object and the subordinate objects are affected. NONE specifies that none of the subordinate objects are affected. ONLY specifies that only the subordinate objects are affected. SEL [NOT] state directs the command only to objects in the specified state or only to those not in the specified state. Valid states are STARTED, STARTING, STOPPED, STOPPING, and SUSPENDED. Consideration There are no considerations for the NAMES LINE command.
NAMES null Command SCF for PAM Consideration You must enter the name of the PAM manager (PAMMAN) process ($ZZPAM) with the NAMES null command. Example This example requests names for all objects running in the PAM subsystem: -> NAMES $ZZPAM NAMES null Display This example shows the display for the NAMES null command when issued to the PAM manager process: PAM Names \SAMCAT.$ZZPAM PROCESS $LAN24 $ZZPAM LINE $LAN24 PORT $LAN24.#L1P0002 $LAN24.#L1P0004 MSAP $LAN24.
NAMES PORT Command SCF for PAM NAMES PORT Command The NAMES PORT command displays all the fully qualified names specified by the PORT name. Command Syntax NAMES [ /OUT file-spec/ ] PORT port-name OUT file-spec directs any SCF output generated for this command to the specified file. PORT port-name is the name of the port. Consideration There are no considerations for this command.
NAMES SESSION SCF for PAM Consideration NAMES PROCESS applies only to the PAMMAN process ($ZZPAM). Example This example requests the fully qualified names for the process: -> NAMES PROCESS $ZZPAM NAMES PROCESS Display The display for the NAMES PROCESS command has this format: PAM Names PROCESS \SYS08.$ZZPAM.* PROCESS $ZZPAM.#LLCT1 $ZZPAM.#LLCT2 $ZZPAM.#LLCT3 NAMES SESSION The NAMES SESSION command requests all the fully qualified names for the specified SESSION object.
PRIMARY Command SCF for PAM NAMES SESSION Display The display for the NAMES SESSION command has this format: PAM Names SESSION \SYS08.$LINE01.* SESSION $LINEO1.#LLCT1 $LINE01.#LLCT2 $LINE01.#LLCT3 PRIMARY Command The primary command makes the backup processor the primary processor and the primary processor the backup processor for the specified object. This is a sensitive command. PRIMARY LINE Command The PRIMARY LINE command alternates the primary and backup processor for the line.
START Command SCF for PAM switch to the backup processor only if the backup processor has data-path access to the associated LIF. Example This example switches the line’s primary processor to CPU 1: -> PRIMARY LINE $PAMA, CPU 1 START Command The START command is a sensitive command that initiates the operation of an object. Successful completion of the START command leaves the object in either the STARTED or STARTING summary state.
START MSAP Command SCF for PAM Consideration There are no considerations for this command. Example This example starts the LINE named $PAM1: ->START LINE $PAM1 START MSAP Command The START MSAP command starts an MSAP object. Command Syntax START [ /OUT file-spec/ ] MSAP msap-name OUT file-spec directs any SCF output generated for this command to the specified file. MSAP msap-name is the name of the MSAP. #SNATR is the only valid MSAP name.
STATISTICS (STATS) Command SCF for PAM Command Syntax START [ /OUT file-spec/ ] PORT port-name OUT file-spec directs any SCF output generated for this command to the specified file. PORT port-name is the name of the port. Consideration LLC2 ports cannot be started by using the PAM SCF interface. SCF error E00015 will be returned. The SNAX interface adds and maintains LLC2 ports. Example This example starts an Ethernet port named #ENET1: ->START PORT $PAM1.
STATS LINE Command SCF for PAM line-name is the name of the line. RESET restores all the statistics counters to their initial values after the statistics are displayed. This is a sensitive command option. Consideration There are no considerations for this command.
STATS LINE Command SCF for PAM STATS LINE Display The display for the STATS LINE command has this format: PAM Stats LINE $PAM1 Sample Time..... 24 Nov 1997, 11:13:44.702 Reset Time...... 24 Nov 1997, 11:09:58.240 Messages IN Requests............... 14D Replies................ 13D Cancels................ 0D Messages OUT Requests............... Replies................ Cancels................ Send errors............ Last Send Error........ 0D 0D 0D 0D 0 LIF OUT Stats Register Requests......
STATS LINE Command SCF for PAM Replies is the number of replies to message system requests received by PAM. Cancels is the number of cancels received by PAM to message-system requests previously received by PAM. Messages Out Requests is the number of message system requests sent by PAM to other processes (such as SNAX). Replies is the number of replies received by PAM to message-system requests it sent. Cancels is the number of internally generated cancels sent by PAM.
STATS LINE Command SCF for PAM Q PUTs is the number of QIO queue puts to the LIF and PAMMAN. (A PUT is a driver call to output data.) Q PUT Fails is the number of QIO queue puts that failed. Access Downs is the number of “Access Down” messages received from the LIF. LIF IN Stats Deregister Requests is the number of LIF deregister calls made by PAM. A STOP PORT SCF command results in Deregister, for example. Deregister Fails is the number of LIF deregister calls that failed.
STATS LINE Command SCF for PAM Total Allocations is the total number of buffer allocations so far. Total Deallocations is the total number of buffer deallocations so far. Last Failure Size is the size of the buffer for which the last allocation failed. Failure Count is the total number of buffer allocation failures. QIO MD OUT Stats Outbound MD Gets is the number of message descriptor (MD) Gets issued by PAM to send messages to the LIF or PAMMAN. (MD is an internal QIO data structure.
STATS MSAP Command SCF for PAM STATS MSAP Command The STATS MSAP command returns statistical information about an MSAP object. When the RESET option is used, the statistics counters reset to 0. The STATS MSAP command becomes a sensitive command when the RESET option is specified. You must have the SUPER ID to reset the counters. Command Syntax STATS [ /OUT file-spec/ ] MSAP msap-name [ , RESET ] OUT file-spec directs any SCF output generated for this command to the specified file.
STATS PORT Command SCF for PAM Open SAP Reqs Rejected is the number of open SAP requests that were rejected. Close SAP Reqs Recvd is the number of requests received from SNAX to close a SAP. Close SAP Reqs Rejected is the number of requests rejected from SNAX to close a SAP. STATS PORT Command The STATS PORT command returns statistical information about a port. When the RESET option is used, the statistics counters reset to 0.
STATS PORT Command SCF for PAM STATS PORT Display The display for the STATS PORT command, for LLC1 ports, has this format: PAM STATS PORT $PAMA.#LCTEST Sample Time..... 05 Oct 1997, 8:03:42.638 Reset Time...... 04 Oct 1997, 14:52:44.340 Delivered AG SDUs........ Undelivered AG SDUs...... Sent AG SDUs............. Not Sent AG SDUs......... 1149D 0D 14D 0D File System Requests Control... WriteRead. Open...... CPUDown... GetParam.. 0D 0D 8D 0D 0D Read....... SetMode.... Close...... CPUUp...... SetParam..
STATS SESSION Command SCF for PAM STATS SESSION Command The STATS SESSION command returns statistical information about a port. When the RESET option is used, the statistics counters reset to 0. The STATS SESSION command becomes a sensitive command when the RESET option is specified. You must have the SUPER ID to reset the counters. Command Syntax STATS [ /OUT file-spec/ ] SESSION session-name [ , RESET ] SESSION session-name is the name of the session.
STATS SESSION Command SCF for PAM I Frames Sent/Received specifies the number of I frames sent and received by this session. RNR Frames Sent/Received specifies the number of RNR frames sent and received by this session. REJ Frames Sent/Received specifies the number of REJ frames sent and received by this session. SABME Frames Sent/Received specifies the number of SABME frames sent and received by this session. FRMR Frames Sent/Received specifies the number of FRMR frames sent and received by this session.
STATUS Command SCF for PAM STATUS Command The STATUS command is a nonsensitive command that displays the dynamic state, last error, and modifiable characteristics of the specified object. STATUS also displays specific PAM subsystem attributes and values. STATUS LINE Command The STATUS LINE command shows the status of a line, including the state, name, and primary and backup processors.
STATUS LINE Command SCF for PAM Examples These examples return status information for the specified line with and without detail: -> status line $lan24 -> status line $jcpm,detail STATUS LINE Command Display The display for the STATUS LINE command without the DETAIL option has this format: PAM Status LINE Name $LAN24 State STARTED Primary CPU PIN 1 278 Backup CPU PIN -1 -1 Trace OFF Name is the name of the line. State is the current summary state of the line.
STATUS MSAP Command SCF for PAM Trace indicates whether or not a trace of this line is active. Primary CPU is the primary processor number. Backup CPU is the backup processor number. A value of -1 in this field indicates that the line is running without a backup process. Primary Pin is the PIN of the primary process. Backup Pin is the PIN of the backup process. Logical Device is the logical device (LDEV) number for this line. Number of Ports is the number of ports (PORT objects) configured on this line.
STATUS MSAP Command SCF for PAM DETAIL causes the STATUS command to display a list of detailed information about the status of the MSAP object. However, STATUS MSAP with and without the DETAIL option provide the same information at this time. Consideration There are no considerations for the STATUS MSAP command. Example This example returns status information for the MSAP: -> STATUS MSAP $PAMA.
STATUS PORT Command SCF for PAM STATUS PORT Command The STATUS PORT command displays the current status of the specified PORT object. Command Syntax STATUS [ /OUT file-spec/ ] PORT port-name [ , SUB [ ALL | NONE | ONLY ] ] [ , SEL [ NOT ] state ] [ , DETAIL ] OUT file-spec directs any SCF output generated for this command to the specified file. PORT port-name is the name of the port. Consideration There are no considerations for the STATUS PORT command.
STATUS PORT Command SCF for PAM Openers is the current number of file-system OPENs against the port. SDU Data Size is the maximum size possible for the data portion of the SDU. STATUS PORT Display for LLC2 The display for a STATUS PORT command for an LLC2 port has this format: PAM Status PORT Name State SNAX Window Sessions $LAN24.#SAP004 STARTED 50 PAM Window 50 1 Name is the name of the port. State is the current summary state of the PORT object.
STATUS SESSION Command SCF for PAM STATUS PORT Display for Ethernet The display for a STATUS PORT command for an Ethernet port has this format: PAM Status PORT Name Size $LAN54.#E1P2056 State Openers SDU Data STOPPED 0 0 Name is the name of the port. State is the summary state of the port. Openers is the current number of file-system OPENs against the port. SDU Data Size is the maximum size possible for the data portion of the SDU.
STATUS SESSION Command SCF for PAM Examples These examples return session status information with and without detail. -> status session $lan24.* -> status session $lan24.*, detail STATUS SESSION Display This example shows the response display for STATUS SESSION without detail: PAM Status SESSION Name $LAN24.#SAP004.LS004001 State DEFINED Session State ADM Name is the name of the session. Session State is the data transfer state of the session.
STATUS SESSION Command SCF for PAM STATUS SESSION Display With Detail The display for STATUS SESSION with DETAIL is: PAM Detailed Status SESSION $LAN24.#SAP004.LS004001 State....................DEFINED Remote MAC Address...... 08 008E 00D18F H Remote SAP Address...... 4 Session State........ ADM Requester Session ID.... 1 PAM Session ID...... 1 I-Frame Xmit Window..... 7 I-Frame Recv Window.. 7 Max Info Field Length ...1024 Access Priority ..... 0 Max Retries .............5 Response Timer ....0:33:20.
STATUS SESSION Command SCF for PAM PAM Session ID is a unique ID used by PAM for this session. I_Frame Xmit Window specifies how many transmitted I frame acknowledgments can be outstanding at any time. I-Frame Recv Window specifies how many I-frames can be received before an acknowledgment must be sent. Max Info Field Length is the maximum information field-length that can be received by this session. Access Priority is the priority to place in the AC field of all frames sent from this session.
STATUS SESSION Command SCF for PAM Lost Link No Ack indicates that the link-station (LS) has entered the reset state because of an exhausted retry count. A SABME command has been sent to the remote LS. Lost Link Remote Busy indicates that the LS has entered the reset state because of an exhausted retrycount while receiving RNR frames. A SABME command has been sent to the remote LS. A CLOSE_LS command should be issued.
STOP Command SCF for PAM Reset Done indicates that the reset procedure initiated from the local LS is accepted by the remote LS and the reset is complete. The LS has returned to normal data transfer state. All pending outbound frames are intact, and all inbound frames start to flow. STATUS_CODE_MOD: none. Reset Failure indicates that the local LS has failed to complete the reset procedure because of no response or a bad response from the remote LS. The LS has entered the disc state.
STOP MSAP Command SCF for PAM SEL [NOT] state directs the command only to objects in the specified state or only to those not in the specified state. Valid states are STARTED, STARTING, STOPPED, STOPPING, and SUSPENDED. Consideration There are no considerations for this command. Example This example stops the line named $PAMA: STOP LINE $PAMA STOP MSAP Command The STOP MSAP command halts the operation of the specified MSAP object.
STOP PORT Command SCF for PAM Considerations • • • The STOP MSAP #SNATR command stops the SNATR interface and makes it inaccessible to SNAX. The #SNATR MSAP can be stopped only if there are no subordinate LLC2 PORT objects. For an immediate shutdown, use the ABORT MSAP command. This command also aborts all active sessions. Example This example stops the MSAP named $PAM1.#SNATR: STOP MSAP $PAM1.#SNATR STOP PORT Command The STOP PORT command halts the operation of the specified PORT object.
STOP PROCESS Command SCF for PAM STOP PROCESS Command The STOP PROCESS command halts the operation of the specified PROCESS object. Command Syntax STOP [ /OUT file-spec/ ] PROCESS process-name OUT file-spec directs any SCF output generated for this command to the specified file. PROCESS process-name is the name of the PROCESS object to be stopped. The process name can be $ZZPAM or the name of a PAM process.
TRACE Command SCF for PAM TRACE Command The TRACE command is a sensitive command that can request the capture of target-defined data items, alter trace parameters, and end tracing. An SCF trace creates a trace file that can be displayed using the commands available in the PTrace program. The PTrace program is described in the PTrace Reference Manual. TRACE LINE Command Use the TRACE LINE command to collect trace information about LINE objects.
TRACE LINE Command SCF for PAM 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 LINE Command SCF for PAM OPENER Traces OPENERs PORT Traces port events SNATR Traces #SNATR MSAP interface events LIF Traces the LIF LIFDI Traces the LIF data in LIFDO Traces the LIF data out 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.
VERSION Command SCF for PAM VERSION Command The VERSION command supplies product information about PAM. VERSION is a nonsensitive command. VERSION PROCESS Command VERSION PROCESS returns information about the PAM manager process. Command Syntax VERSION [ / OUT file-spec / ] PROCESS process-name OUT file-spec directs any SCF output generated for this command to the specified file. PROCESS process-name is the PAM manager process. Considerations There are no considerations for VERSION PROCESS.
SCF for PAM VERSION LINE Command PAM Configuration and Management Manual—523349-003 3- 64
A TLAM to PAM Migration Guide This appendix compares the components and functions of the HP Tandem LAN Access Method (TLAM) and PAM subsystem. PAM and TLAM Subsystem Comparison The PAM subsystem provides many of the functions provided by the TLAM subsystem, but within the context of the system architecture for G-series and H-series RVUs.
Software Components TLAM to PAM Migration Guide Software Components Table A-1. Comparison of PAM and TLAM Software Component PAM Component TLAM Component Comments PAM manager process (PAMMAN) TLAM manager process (MLMAN) PAMMAN is a process pair that provides the interface between the PAM subsystem and the Subsystem Control Point (SCP). MLMAN is a process pair that provides the interface between the TLAM subsystem and the SCP.
Programmatic Interfaces TLAM to PAM Migration Guide The major hardware components associated with the PAM subsystem are: • • • • The Ethernet 4 ServerNet adapter (E4SA) The Gigabit 4 ServerNet adapter (G4SA) The Fast Ethernet ServerNet adapter (FESA) The Token-Ring ServerNet adapter (TRSA) The PAM subsystem does not support token-bus connections.
Management Interfaces TLAM to PAM Migration Guide Management Interfaces These Distributed Systems Management (DSM) interfaces are provided to manage both the PAM and the TLAM subsystems: • • • Subsystem Programmatic Interface (SPI), which provides a programmatic control-and-inquiry and event management interface for writing management applications Event Management Service (EMS), which provides an event-management interface that includes printing and a compatibility distributor process that can print or
Object Types TLAM to PAM Migration Guide Table A-3. PAM and TLAM Object Comparison (page 2 of 2) Object Name PAM TLAM Comments PORT Yes Yes Both subsystems provide these port types: • • • Ethernet LLC1 LLC2 Only the TLAM subsystem provides these port types: • • • • SNAP IPX8022 IPX8023 TR8025 In PAM, the TR8025 port type is part of the LLC1 interface. MSAP Yes Yes Both subsystems provide a SNATR object.
TLAM to PAM Migration Guide PAM Configuration and Management Manual—523349-003 A- 6 Object Types
B SCF Command Summary ABORT [ /OUT file-spec/ ] LINE line-name [ , SUB [ ALL | NONE | ONLY ] ] [, SEL [NOT] state ] ABORT [ /OUT file-spec/ ] MSAP msap-name [ , SUB [ ALL | NONE | ONLY ] ] [, SEL [NOT] state ] ABORT [ /OUT file-spec/ ] PORT port-name [, SEL [NOT] state ] ABORT [ /OUT file-spec/ ] PROCESS process-name ADD [ /OUT file-spec/ ] PORT port-name {, {, [, [, [, [, [, [, ADDRESS port-address } TYPE { ETHERNET | LLC1 } } DATAFORWARDCOUNT integer ] DATAFORWARDTIME { timevalue | INFINITE } ] DEL
SCF Command Summary ALTER [ /OUT file-spec/ ] PORT port-name { [, [, [, [, [, DATAFORWARDCOUNT 1-22 ] DATAFORWARDTIME { timevalue | INFINITE } ] DELIVERYMODE { SERIAL | PARALLEL } ] GROUPMACADDRESS { macaddress | DEFAULT } ] REQUESTSIZE integer ] } DELETE [ /OUT file-spec/ ] PORT port-name INFO [ /OUT file-spec/ ] LINE line-name [SUB , [ ALL | NONE | ONLY ] ] [ , SEL [ NOT ] state ] INFO [ /OUT file-spec/ ] MSAP msap-name INFO [ /OUT file-spec/ ] PORT port-name LISTOPENS [ /OUT file-spec/ ] PORT port
SCF Command Summary PRIMARY [ /OUT file-spec/ ] LINE line-name [ , CPU cpu-number ] START [ /OUT file-spec/ ] LINE line-name [ SUB , [ ALL | NONE | ONLY ] ] [ , SEL [ NOT ] state ] START [ /OUT file-spec/ ] MSAP msap-name START [ /OUT file-spec/ ] PORT port-name STATS [ /OUT file-spec/ ] LINE line-name [ , RESET ] STATS [ /OUT file-spec/ ] MSAP msap-name [ , RESET ] STATS [ /OUT file-spec/ ] PORT port-name [ , RESET ] STATS [ /OUT file-spec/ ] SESSION session-name [ , RESET ] STATUS [ /OUT file-spe
SCF Command Summary STATUS [ /OUT file-spec/ ] MSAP msap-name [ , SUB [ ALL | NONE | ONLY ] ] [ , SEL [ NOT ] state ] [ , DETAIL ] STATUS [ /OUT file-spec/ ] PORT port-name [ , SUB [ ALL | NONE | ONLY ] ] [ , SEL [ NOT ] state ] [ , DETAIL ] STATUS [ , / OUT file-spec /) SESSION session-name [ , DETAIL ] STOP [ /OUT file-spec/ ] LINE line-name [ , SUB [ ALL | NONE | ONLY ] ] [ , SEL [ NOT ] state ] STOP [ /OUT file-spec/ ] MSAP msap-name [ , SUB [ ALL | NONE | ONLY ] ] [ , SEL [ NOT ] state ] STOP [ /
SCF Command Summary TRACE [ /OUT file-spec/ ] LINE line-name { , STOP [ , BACKUP ] } { [ , BULKIO | NOBULKIO ] [ , BACKUP ] [ , COUNT count ] [ , NOCOLL ] [ , PAGES pages ] [ , RECSIZE size ] [ , SELECT select-spec ] [ , TO file-spec ] [ , WRAP ] } VERSION [ / OUT file-spec / ] PROCESS process-name VERSION LINE [ / OUT file-spec / ] LINE line-name PAM Configuration and Management Manual—523349-003 B- 5
SCF Command Summary PAM Configuration and Management Manual—523349-003 B- 6
C SCF Error Messages This appendix lists the error messages that SCF can return for PAM and describes the cause and recovery for each error. 00001 PAM 00001 Cannot delete object because subordinate object is not deleted. Cause. A DELETE command was received while the object still had subordinate objects configured. Recovery. Specify the SUB ALL modifier or otherwise stop subordinate objects before attempting to delete this object.
00005 SCF Error Messages 00005 PAM 00005 Cannot stop object because object has active opens. Cause. At least one of this object’s subordinates is active. (That is, a subordinate object has an outstanding OPEN request.). Recovery. Close any subordinate objects and try again, or use the ABORT command instead of the STOP command. 00006 PAM 00006 Associated LIF is down. Cause. The LIF associated with the PAM process was down when the command was issued. Recovery.
00010 SCF Error Messages 00010 PAM 00010 Trace function invalid for object. Cause. An unsupported trace select function was specified in the TRACE command. Recovery. Specify only supported trace select options. 00011 PAM 00011 Port LSAP address has already been defined by another port. Cause. An incorrect LSAP PORT address was specified. Recovery. Specify another LSAP address. 00012 PAM 00012 MSAP attribute cannot be modified in current summary state. Cause.
00015 SCF Error Messages 00015 PAM 00015 Object: Command not supported for LLC2 ports Cause. An SCF command that is not applicable to LLC2 type ports was issued. Recovery. Use the applicable SCF command. 00016 PAM 00016 MSAP #SNATR not stopped. PORT objects. Line has subordinate LLC2 Cause. An SCF STOP MSAP #SNATR command was issued when SAPs were open. Recovery. Use the SCF ABORT MSAP command to abort the SAPs and stop the MSAP. 00017 PAM 00017 Attribute not valid for this controller type. Cause.
00020 SCF Error Messages 00020 PAM 00020 PAM Internal Error: Unable to perform PORT command. Cause. An internal error occurred in PAM while performing an SCF command. Recovery. Contact your service provider with the EMS log. 09990 PAM 09990 The specified time interval exceeds two digits right of the decimal point. Cause. The operator or management application specified a time interval that has more than two digits to the right of the decimal point. Recovery.
09994 SCF Error Messages Recovery. Reissue the command using a valid subtype. 09994 PAM 09994 Specified Mac Address does not have group bit set. Cause. The specified MAC address does not have the group bit set. Recovery. Specify a MAC address with the group bit set. Bit 0 of byte 0 must be set to 1. 09995 PAM 09995 Specified Mac Address has individual bit set or local bit reset. Cause. The specified MAC address has the individual bit set or the local bit reset. Recovery.
09999 SCF Error Messages 09999 PAM 09999 Duplicate attribute specified. Cause. An attribute has been specified more than once in a single command. Recovery. Check the command for duplicate attributes, remove any duplicates, and reissue the command.
09999 SCF Error Messages PAM Configuration and Management Manual—523349-003 C- 8
Index Numbers 00001 SCF error message 00002 SCF error message 00003 SCF error message 00004 SCF error message 00005 SCF error message 00006 SCF error message 00007 SCF error message 00008 SCF error message 00009 SCF error message 00010 SCF error message 00011 SCF error message 00012 SCF error message 00013 SCF error message 00014 SCF error message 00015 SCF error message 00016 SCF error message 00017 SCF error message 00018 SCF error message 00019 SCF error message 09990 SCF error message 09991 SCF error me
E Index Deregister Requests (in STATS LINE display) 3-38 DISC Frames Sent/Received (in STATS SESSION display) 3-44 Distributed Systems Management Facilities 2-6 DM Frames Sent/Received (in STATS SESSION display) 3-44 DSM 2-6 Inbound MD Gets (in STATS LINE display) 3-39 Inbound MD Highwater (in STATS LINE display) 3-39 Inbound MD Returns (in STATS LINE display) 3-39 INFO command 3-18/3-25 Interactive interfaces 2-7 L E EMS 2-4 end-of-file mark 3-62 F Failure Count (in STATS LINE display) 3-39 Features,
N Index MSAPSTARTDOWN see start-up parameters MSAPSTARTUP see start-up parameters Multifunction I/O board 2-6 N NAMES command 3-26/3-31 NOBULKIO 3-60 NOCOLL 3-61 Nonsensitive commands, description 2-11 Not Sent AG SDUs (in STATS PORT display) 3-42 Number of Ports 3-47 O Object hierarchy 2-7 Open SAP Reqs Recvd (in STATS MSAP display) 3-40 Open SAP Reqs Rejected (in STATS MSAP display) 3-41 Outbound Dup MD Gets (in STATS LINE display) 3-39 Outbound MD Gets (in STATS LINE display) 3-39 Outbound MD Highwat
S Index Replies (in STATS LINE display) 3-37 Requests (in STATS LINE display) 3-36, 3-37 REQUESTSIZE 3-13 Reset Time (in STATS LINE display) 3-36 Reset Time (in STATS MSAP display) 3-40 Reset Time (in STATS PORT display) 3-42 Reset Time (in STATS SESSION display) 3-43 RNR Frames Sent/Received (in STATS SESSION display) 3-44 Role, of PAM 2-2 S SABME Frames Sent/Received (in STATS SESSION display) 3-44 Sample Time (in STATS LINE display) 3-36 Sample Time (in STATS MSAP display) 3-40 Sample Time (in STATS P
U Index U Undelivered AG SDUs (in STATS PORT display) 3-42 V VERSION command 3-63 W WRAP 3-62 PAM Configuration and Management Manual—523349-003 Index -5
W Index PAM Configuration and Management Manual—523349-003 Index -6
