Network Working Group M. Allen
Request for Comments: 2051 Wall Data Inc.
Category: Standards Track B. Clouston
Z. Kielczewski
Cisco Systems
W. Kwan
Jupiter Technology Inc.
B. Moore
IBM
October 1996
Definitions of Managed Objects for APPC using SMIv2
Status of this Memo
This document specifies an Internet standards track protocol for the
Internet community, and requests discussion and suggestions for
improvements. Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol. Distribution of this memo is unlimited.
Table of Contents
1. IntrodUCtion ........................................... 1
2. The SNMP Network Management Framework .................. 1
3. Overview ............................................... 2
3.1 APPC MIB structure ...................................... 4
4. Definitions ............................................ 10
5. Acknowledgments ........................................ 123
6. References ............................................. 123
7. Security Considerations ................................ 123
8. Authors" Addresses ..................................... 124
1. Introduction
This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community.
In particular, it defines objects for managing the configuration,
monitoring and controlling of network devices with APPC (Advanced
Program-to-Program Communications) capabilities. This memo
identifies managed objects for the SNA LU6.2 protocols.
2. The SNMP Network Management Framework
The SNMP Network Management Framework consists of several components.
For the purpose of this specification, the applicable components of
the Framework are the SMI and related documents [2, 3, 4], which
define the mechanisms used for describing and naming objects for the
purpose of management.
The Framework permits new objects to be defined for the purpose of
eXPerimentation and evaluation.
3. Overview
This document identifies the proposed set of objects for managing the
configuration, monitoring and controlling devices with APPC
capabilities. APPC is the ASPect of SNA which supports peer-to-peer
communication, and provides the interface for applications to
communicate. In this document, we will describe LU6.2 protocol-
specific managed objects.
This document describes both dependent and independent LU 6.2
protocols.
A dependent LU requires assistance from an SSCP in order to activate
an LU 6.2 session. An independent LU is able to activate an LU 6.2
session without assistance from the SSCP. If the agent supports
dependent LU 6.2 only, the SNA NAU MIB, RFC1666 [7] is used instead
to represent those objects.
Local LUs and partner LUs connect with each other using sessions.
Multiple different sessions can be established between LUs with
characteristics defined by Modes. Session limits within a defined
Mode are negotiated between the local and partner LUs using a
protocol called CNOS (Change Number of Sessions).
Transaction Programs (TPs) are applications that use sessions to
communicate with each other. Multiple TPs can use the same session,
but not at the same time. A single usage of a session is called a
conversation. While a session can stay active for a long time, a
conversation can come up and down based on usage by the TPs.
Common Programming Interface - Communications (CPI-C) is a standard
API (Application Programming Interface) for APPC and OSI TP that is
used by TPs for Accessing conversations. Although, many of the CPI-C
objects in this MIB are relevant to both APPC and OSI TP, the
intention is for managing APPC products only.
SNA names such as LU names, CP names, mode names, and COS names can
be padded with space characters in SNA formats. These space
characters are insignificant. For example, in a BIND RU a mode name
of "#INTER" with a length of 6 is identical to a mode name of "#INTER
" with a length of 8. However, in this MIB, insignificant space
characters are not included by the agent. Using the mode name from
the previous example, an agent would return a length of 6 and the
string "#INTER" with no space characters for appcModeAdminModeName,
regardless of how it appears in the BIND RU or in internal storage.
The lone exception is the all blank mode name, for which the agent
returns a length of 8 and the string " " (8 space characterss).
When an SNA name is functioning as a table index, an agent shall
treat trailing space characters as significant. If a Management
Station requests the objects from a row with index "#INTER ", the
agent does not match this to the row with index "#INTER". Since an
agent has no insignificant space characters in any of its table
indices, the only reason for a Management Station to include them
would be to start GetNext processing at a chosen point in a table.
For example, a GetNext request with index "M " would start
retrieval from a table at the first row with an 8-character index
beginning with M or a letter after M.
The SNA/APPC terms and overall architecture are documented in [1],
[5], and [6].
Highlights of the management functions supported by the APPC MIB
module include the following:
o Activating and deactivating statistics keeping and counting.
o Activating and deactivating tracing.
o Issuing CNOS processing verbs/commands for
INITIALIZE_SESSION_LIMIT, CHANGE_SESSION_LIMIT and
RESET_SESSION_LIMIT.
o Monitoring of parameters related to local LU, partner LU, modes,
TPs and CPI-C side information.
o Deactivating sessions.
o Monitoring of LU6.2-specific session operational parameters and
statistics, historical information about abnormally terminated
sessions, and information about APPC sessions that are
transported by APPN HPR.
o Monitoring of conversation operational parameters, and
historical information about abnormally terminated sessions.
This MIB module does not support:
o Modifying APPC defaults.
o Creating and deleting partner LUs, modes, TPs, and CPI-C side
information tables.
o Modifying parameters related to local LU, partner LU, modes,
TPs, and CPI-C side information.
o Activating or deactivating local LUs.
o Activating or deactivating partner LUs.
o Activating or deactivating conversations.
o Activating or deactivating Transaction Programs.
o Activating sessions.
o Traps
3.1. APPC MIB Structure
The APPC MIB module contains six groups of objects:
o appcGlobal - objects related to global defaults and controls.
In addition, CNOS processing objects are also part of this group.
o appcLu - objects related to LU6.2-specific local and partner
LU, mode definition, monitoring and control.
o appcTp - objects related to transaction program definition,
monitoring and control.
o appcSession - objects related to LU6.2-specific session
monitoring.
o appcConversation - objects related to conversation monitoring.
o appcCPIC - objects related to related CPI-C side information.
These groups are described below in more detail.
The objects related to LU6.2 are generally organized into two types of
tables: the Admin and Oper tables.
The "Admin" table contains read-only objects which contain default or
expected configuration values. This MIB does not create or modify
configuration values. The "Oper" table contains objects which
provide current operational values, such as state values or
negotiated parameters, for dynamic or configured objects. Dynamic
objects are created by the APPC system using one of the templates
provided in the "Admin" table. Configured objects usually have a
one-to-one relationship between "Admin" and "Oper" entries. However,
some "Admin" values may have changed since the object became
operational, such that the "Oper" values may no longer be based on
the "Admin" values. The "Admin" entry could even be deleted. For
example, some implementations may allow a mode definition
(appcModeAdminEntry) to be deleted even while an active session was
using this mode (appcModeOperEntry still exists). Where appropriate,
the "Oper" table may include initial starting values for objects that
can be reconfigured while operational. How the "Admin" values are
changed or deleted is outside the scope of this MIB.
3.1.1. appcGlobal group
The appcGlobal group consists of the following tables and objects:
1) appcCntrlAdminGroup
This group of objects controls whether certain statistics and
counters (e.g., session counters and RSCV collection) should be
maintained by the Agent. In addition, the ability to activate and
deactivate tracing is also supported through objects in this group.
These objects are for Agent implementations that wish to provide this
level of operational control and are optional.
The objects in this group represent the desired state, with the
actual operational values in appcCntlOperGroup.
These objects can be generated initially, after startup of SNA
service, by the Agent which uses information from the Node
configuration file. Subsequent modifications of object values is
possible by a Management station. The modifications to these objects
can be saved in the Node configuration file for the next startup
(i.e., restart or next initialization) of SNA service, but the
mechanism for this function is not defined in this document.
2) appcCntrlOperGroup
This group of objects monitors whether certain statistics and
counters (e.g., session counters and RSCV collection ) are maintained
by an Agent. In addition, the ability to monitor tracing activity is
also supported through objects in this group.
This table represents the actual operational state. These states can
be modified via objects in the appcCntrlAdminGroup.
3) appcGlobalObjects
These objects describe global information such as APPC system start
time, the control point name, and default LU 6.2 configuration
values. The type of default configuration information includes mode
name, LU, and maximum logical record size.
4) appcCnosControl
These objects allows for issuing of CNOS commands relative to a local
and partner LU pair and a Mode. They support the following CNOS
commands: INITIALIZE_SESSION_LIMIT, CHANGE_SESSION_LIMIT and
RESET_SESSION_LIMIT.
The objects in this group can be modified by a Management Station.
This group consists of objects that are relevant to the CNOS commands
parameters, which a Management Station needs to set. After setting
the parameters of a CNOS command, the Management Station will set the
control object (appcCnosCommand) to request the Agent to issue the
appropriate CNOS command.
3.1.2. appcLu group
The appcLu group consists of the following tables:
1) appcLluAdminTable
This table contains objects which describe specific LU6.2 local LU
configuration information. The type of information includes the
maximum number of sessions supported and compression parameters.
2) appcLluOperTable
This table contains objects which describe specific LU6.2 local LU
operational information. The type of information includes the maximum
number of sessions supported, the number of sessions currently
active, and compression parameters.
3) appcLuPairAdminTable
This table contains objects which describe local LU and partner LU
configuration information. The type of information includes security
information and whether parallel sessions are supported.
For those implementations that have partner LU definitions associated
with each local LU, multiple entries with the same
appcLuPairAdminParLuName could exist with different
appcLuPairAdminLocLuName. For those implementations in which partner
LU definitions apply to all local LUs, the appcLuPairAdminLocLuName
is set to "*ALL".
4) appcLuPairOperTable
This table contains objects which describe partner/local LU pair run-
time operational information. The type of information includes
security information and whether parallel sessions are supported.
Although the Admin (appcLuPairAdminTable) table entries could be
global to all local LUs in a Node, an entry in this Oper table is
always associated with one local LU.
A row in this table is created as soon as there is an active session
between the local and partner LU. Two entries are present when both
LUs in a pair are local.
5) appcModeAdminTable
This table contains objects which describe Mode configuration
information. The type of information includes the mode name and
maximum session limit.
For those implementations that have Mode definitions associated with
each local and partner LU pair, multiple entries with the same
appcModeAdminModeName could exist with different
appcModeAdminLocLuName and appcModeAdminParLuName. For those
implementations in which Mode definitions apply to all local and/or
all partner LUs, the appcModeAdminLocLuName and/or
appcModeAdminParLuName are set to "*ALL".
6) appcModeOperTable
This table contains objects which describe Mode run-time operational
information for each local/partner LU pair. The type of information
includes the mode name and maximum session limit.
Although the Admin table entries could be global to all local and
partner LUs in a Node, the Oper table entries are always associated
with one local and partner LU pair.
A row in this table is created as soon as there is an active session
between local and partner LU for this Mode. Two entries are present
when both LUs in a pair are local.
3.1.3. appcTp group
The appcTp group consists of the following table:
1) appcTpAdminTable
This table contains objects which describe transaction program (TP)
configuration information. The type of information includes the TP
name and TP operation, indicating how the TP will be started.
For those implementations that have TP definitions associated with
each local LU, multiple entries with the same appcTpAdminTpName could
exist with different appcTpAdminLocLuName. For those implementations
in which TP definition applies to all local LUs, it will have
appcTpAdminLocLuName set to "*ALL".
There is no appcTpOperTable. Run-time information about TP tends to
be product-specific (e.g., process Id), and much of the information
can be derived from the conversation tables.
3.1.4. appcSession group
The appcSession group consists of the following tables:
1) appcActSessTable
This table contains objects which describe LU6.2 session information.
The type of information includes the PCID and the pacing counts.
2) appcSessStatsTable
This table contains statistical information about LU 6.2 sessions.
The type of information includes counters of bytes and RUs sent and
received.
3) appcHistSessTable
This table contains historical information about APPC sessions that
have terminated abnormally. The type of information includes the
unbind type and sense data.
4) appcSessRtpTable
This table contains information about LU 6.2 sesions that are being
transported by High Performance Routing. The type of information
includes the NCEID and TCID.
3.1.5. appcConversation group
The appcConversation group consists of the following tables:
1) appcActiveConvTable
This table contains objects which describe active conversation
information. The type of information includes the state and type. An
entry is created by an Agent when the conversation is started, and is
removed when the conversation ends.
2) appcHistConvTable
This table contains objects which describe historical conversation
information about abnormally terminated conversations. The number of
entries and how long they are kept depends on the Agent
implementation. The type of information inclues the sense data and
log data.
3.1.6. appcCPIC group
The appcCPIC group consists of the following tables:
1) appcCpicAdminTable
This table contains objects which describe CPI-C side information.
The type of information includes the symbolic destination name and
partner LU name.
For those implementations that have CPI-C definition associated with
each local LU, multiple entries with the same
appcCpicAdminSymbDestName could exist with different
appcCpicAdminLocLuName. For those implementations in which CPI-C
definition applies to all local LUs, it will have
appcCpicAdminLocLuName set to "*ALL".
2) appcCpicOperTable
This table contains objects which describe CPI-C run-time operational
information. The type of information includes the symbolic
destination name and partner LU name.
4. Definitions
APPC-MIB DEFINITIONS ::= BEGIN
IMPORTS
DisplayString, InstancePointer, TEXTUAL-CONVENTION, DateAndTime
FROM SNMPv2-TC
mib-2, Counter32, Gauge32, Integer32, TimeTicks,
OBJECT-TYPE, MODULE-IDENTITY
FROM SNMPv2-SMI
snanauMIB
FROM SNA-NAU-MIB
MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF;
appcMIB MODULE-IDENTITY
LAST-UPDATED "9512150000Z"
ORGANIZATION "IETF SNA NAU MIB Working Group"
CONTACT-INFO
"
Michael Allen
Wall Data Inc.
P.O.Box 1120
Duval, WA 98019, USA
Tel: 1 206 844 3505
E-mail: mallen@hq.walldata.com
Bob Clouston
Cisco Systems
7025 Kit Creek Road
P.O. Box 14987
Research Triangle Park, NC 27709, USA
Tel: 1 919 472 2333
E-mail: clouston@cisco.com
Zbigniew Kielczewski
Cisco Systems
3100 Smoketree Court
Raleigh, NC 27604, USA
Tel: 1 919 871 6326
E-mail: zbig@cisco.com
William Kwan
Jupiter Technology Inc.
200 Prospect Street
Waltham, MA 02254, USA
Tel: 1 617 894 9300, x423
E-mail: billk@jti.com
Bob Moore
IBM Corporation
800 Park Offices Drive
CNMA/664
P.O. Box 12195
Research Triangle Park, NC 27709, USA
Tel: 1 919 254 4436
E-mail: remoore@ralvm6.vnet.ibm.com
"
DESCRIPTION
"This is the MIB module for objects used to manage network
devices with APPC capabilities."
::= { snanauMIB 3 }
appcObjects OBJECT IDENTIFIER ::= { appcMIB 1 }
appcGlobal OBJECT IDENTIFIER ::= { appcObjects 1 }
appcLu OBJECT IDENTIFIER ::= { appcObjects 2 }
appcTp OBJECT IDENTIFIER ::= { appcObjects 3 }
appcSession OBJECT IDENTIFIER ::= { appcObjects 4 }
appcConversation OBJECT IDENTIFIER ::= { appcObjects 5 }
appcCPIC OBJECT IDENTIFIER ::= { appcObjects 6 }
-- *********************************************************************
-- Objects in this MIB are used to model an SNA device that supports
-- APPC LUs.
-- Following is the overall organization of the MIB.
--
-- 1. APPC Global Objects - global values, defaults,
-- controls (including CNOS)
-- 2. APPC Defined Lu Tables - Admin and Oper
-- 3. APPC Defined LU Pair Tables - Admin and Oper
-- 4. APPC Mode Tables - Admin and Oper
-- 5. APPC TP Tables - Admin only
-- 6. APPC Session Tables - Active, Stats, History, RTP
-- 7. APPC Conversation Table - Active, History
-- 8. APPC CPIC side info - Admin and Oper
-- *********************************************************************
-- *********************************************************************
-- Textual Convention
-- ---------------------------------------------------------------------
SnaSenseData ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"To facilitate their display by a Management Station, sense
data objects in the MIB are represented as DisplayStrings of
size 8. Eight "0" characters indicates that no sense data
identifying an SNA error condition is available."
SYNTAX DisplayString (SIZE (8))
-- *********************************************************************
-- APPC Control Objects
-- ---------------------------------------------------------------------
-- The following objects allow:
-- * the collection of APPC Session information counters
-- to be started and stopped
-- * the collection of APPC Session RSCVs
-- to be started and stopped
-- * the collection of APPC tracing information to be started and
-- stopped
--
-- These objects are for implementations that wish to provide
-- this level of operational control. This group is
-- conditionally mandatory in the conformance section of the MIB.
--
-- *********************************************************************
-- *********************************************************************
-- Control Admin
-- These objects contain the desired states for the controls.
-- The actual states are in the Oper objects.
-- *********************************************************************
appcCntrlAdminGroup OBJECT IDENTIFIER ::= { appcGlobal 1 }
appcCntrlAdminStat OBJECT-TYPE
SYNTAX INTEGER {
notActive(1),
active(2)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Indicates the desired state of statistics collection:
notActive collection of counters is not active.
active collection of counters is active.
When this object is set to notActive, all of the entries are
removed from the appcSessStatsTable."
::= { appcCntrlAdminGroup 1 }
appcCntrlAdminRscv OBJECT-TYPE
SYNTAX INTEGER {
notActive(1),
active(2)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Indicates the desired state of RSCV information collection:
notActive collection of route selection control vectors
is not active.
active collection of route selection control vectors
is active."
::= { appcCntrlAdminGroup 2 }
appcCntrlAdminTrace OBJECT-TYPE
SYNTAX INTEGER {
notActive(1),
active(2)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Indicates the desired state of tracing:
notActive collection of tracing information is not active
active collection of tracing information is active"
::= { appcCntrlAdminGroup 3 }
appcCntrlAdminTraceParm OBJECT-TYPE
SYNTAX DisplayString (SIZE (0..128))
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Specifies the parameter to be used in conjunction with
activating tracing. The actual content is implementation
dependent."
::= { appcCntrlAdminGroup 4 }
-- *********************************************************************
-- Control Oper
-- These objects contain the actual states of the controls.
-- *********************************************************************
appcCntrlOperGroup OBJECT IDENTIFIER ::= { appcGlobal 2 }
appcCntrlOperStat OBJECT-TYPE
SYNTAX INTEGER {
notActive(1),
active(2)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Indicates the current collection options in effect:
notActive collection of counters is not active.
active collection of counters is active.
Statistical entries are present in the appcSessStatsTable
only when the value of this object is "active"."
::= { appcCntrlOperGroup 1 }
appcCntrlOperStatTime OBJECT-TYPE
SYNTAX TimeTicks
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Time since the appcCntrlOperStat object last changed.
This time is in hundreds of a second."
::= { appcCntrlOperGroup 2 }
appcCntrlOperRscv OBJECT-TYPE
SYNTAX INTEGER {
notActive(1),
active(2)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Indicates the current collection options in effect:
notActive collection of route selection control vectors
is not active.
active collection of route selection control vectors
is active."
::= { appcCntrlOperGroup 3 }
appcCntrlOperRscvTime OBJECT-TYPE
SYNTAX TimeTicks
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Time since the appcCntrlOperRscv object last changed.
This time is in hundreds of a second."
::= { appcCntrlOperGroup 4 }
appcCntrlOperTrace OBJECT-TYPE
SYNTAX INTEGER {
notActive(1),
active(2)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Indicates the current state of tracing:
notActive collection of tracing information is not active.
active collection of tracing information is active."
::= { appcCntrlOperGroup 5 }
appcCntrlOperTraceTime OBJECT-TYPE
SYNTAX TimeTicks
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Time since the appcCntrlOperTrace object last changed.
This time is in hundreds of a second."
::= { appcCntrlOperGroup 6 }
appcCntrlOperTraceParm OBJECT-TYPE
SYNTAX DisplayString (SIZE (0..128))
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Specifies the parameter used in conjunction with activating
tracing. The actual content is implementation dependent."
::= { appcCntrlOperGroup 7 }
-- ******************************************************************
--
-- APPC global settings
--
-- ******************************************************************
appcGlobalObjects OBJECT IDENTIFIER ::= { appcGlobal 3 }
appcUpTime OBJECT-TYPE
SYNTAX TimeTicks
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The time, in hundredths of a second, since the
APPC portion of the system was last reinitialized."
::= { appcGlobalObjects 1 }
appcDefaultModeName OBJECT-TYPE
SYNTAX DisplayString (SIZE (1..8))
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Specifies the mode name to be used under the following
conditions:
When an incoming BIND request contains a mode name not
defined at the local node. The parameters defined for
this mode are used for the inbound implicit mode
capability.
When an APPC program issues an [MC_]ALLOCATE,
[MC_]SEND_CONVERSATION, or CNOS verb, or when a CPI-C
program issues an Allocate (CMALLC) call,
specifying a mode name not defined at the local node. The
parameters defined for this mode are used for the outbound
implicit mode capability.
This mode name must match a defined entry in the
appcModeAdminTable."
::= { appcGlobalObjects 2 }
appcDefaultLuName OBJECT-TYPE
SYNTAX DisplayString (SIZE (1..17))
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Specifies the name of the local LU that is to serve as the
default LU. This is the default LU to which are routed inbound
BIND requests that exclude the secondary LU name. This field
is from 1 to 17 characters in length, including a period (.)
which separates the NetId from the NAU name if the NetId is
present. This local LU name must match a defined entry in the
appcLluAdminTable."
::= { appcGlobalObjects 3 }
appcDefaultImplInbndPlu OBJECT-TYPE
SYNTAX INTEGER {
no(1),
yes(2)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Specifies whether or not inbound implicit partner LU support
is enabled. The following values are defined:
no - Specifies that inbound implicit partner LU support
is disabled, which means that an incoming bind that
specifies a partner LU that is not defined at the
local node will be rejected.
yes - Specifies that inbound implicit partner LU support
is enabled, which provides the capability to accept
an incoming BIND request that contains a partner LU
name that is not defined at the local node."
::= { appcGlobalObjects 4 }
appcDefaultMaxMcLlSndSize OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Specifies the maximum size of a logical record to be used for
a mapped conversation when sending data to either the inbound
or outbound implicit partner LU. This size is the maximum
number of bytes in a single logical record, as indicated in the
LL field of the record. The default value is 32767.
Note that this object does not limit the maximum size that an
application program can supply on the Send Data call for a
mapped conversation."
::= { appcGlobalObjects 5 }
appcDefaultFileSpec OBJECT-TYPE
SYNTAX DisplayString (SIZE (0..80))
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The local file specification that is to be searched by the
APPC attach manager when no DEFINE_TP verb has been issued
for the TP name received on an incoming attach. In this
case, the attach manager will attempt to start a program
whose file name is the same as the incoming TP name. If
found, the program is loaded. If not found, the attach is
rejected.
The value "*" indicates that the normal search path for
executable programs is to be used for locating an undefined
transaction program.
A null string indicates that there is no default file
specification for undefined transaction programs."
::= { appcGlobalObjects 6 }
appcDefaultTpOperation OBJECT-TYPE
SYNTAX INTEGER {
other(1),
queuedOperatorStarted(2),
queuedOperatorPreloaded(3),
queuedAmStarted(4),
nonqueuedAmStarted(5)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Specifies how the program will be started.
other - Specifies that the default TP operation is none of
the methods specified below. It may be a
product-specific method.
queuedOperatorStarted - Specifies that one version of the
program will be run at a time. If an incoming
attach arrives and the program has not been started
yet, APPC will issue a message to the operator to
start the specified program. Subsequent attaches
that arrive while the program is active will be
queued.
queuedOperatorPreloaded - Specifies that one version
of the program will be run at a time. If an
incoming attach arrives and the program has not
been started yet, the Attach will be rejected. The
APPC attach manager determines that a TP has
started upon reception of an APPC RECEIVE_ALLOCATE
verb, or a CPI-C Accept_Conversation (CMACCP) or
Specify_Local_TP_Name (CMSLTP) call. No message is
sent to the operator. Subsequent attaches that
arrive while the program is active are queued.
queuedAmStarted - Specifies that one version of the
program will be run at a time and will be started
by the APPC attach manager. Subsequent attaches
that arrive while the program is active will be
queued.
nonqueuedAmStarted - Specifies that multiple copies of
the program will be run at a time and will be
started by the APPC attach manager. "
::= { appcGlobalObjects 7 }
appcDefaultTpConvSecRqd OBJECT-TYPE
SYNTAX INTEGER {
no(1),
yes(2)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Specifies whether or not conversation security will be used
for default TPs.
no - Specifies that the incoming attach does not have to
contain security information.
yes - Specifies that the incoming attach must contain
valid authentication information (e.g., user ID and
passWord)."
::= { appcGlobalObjects 8 }
appcLocalCpName OBJECT-TYPE
SYNTAX DisplayString (SIZE (0..17))
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Specifies the name of the local control point. This field is
from 0 to 17 characters in length, including a period (.) which
separates the NetId from the NAU name if the NetId is present.
A null string indicates that the value is unknown."
::= { appcGlobalObjects 9 }
appcActiveSessions OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Specifies the total number of active APPC sessions supported
by this implementation. Sessions for which both LUs are local
are counted twice."
::= { appcGlobalObjects 10 }
appcActiveHprSessions OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Specifies the total number of active HPR APPC sessions."
::= { appcGlobalObjects 11 }
-- ******************************************************************
-- APPC CNOS control
--
-- This group contains objects for issuing APPC Change-Number-of-Session
-- (CNOS) commands to a specific mode. Specifically, the commands
-- supported are:
-- INITIALIZE_SESSION_LIMIT
-- CHANGE_SESSION_LIMIT
-- RESET_SESSION_LIMIT
--
--
-- ******************************************************************
appcCnosControl OBJECT IDENTIFIER ::= { appcGlobal 4 }
appcCnosCommand OBJECT-TYPE
SYNTAX INTEGER {
initSesslimit(1),
changeSesslimit(2),
resetSesslimit(3)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Specifies the CNOS command or verb to issue. First set the
values of the particular CNOS parameter objects (from the range
{ appcCnosControl 2 } through { appcCnosControl 8 }) that apply
to the CNOS command to be executed, set the three CNOS target
objects ({ appcCnosControl 9 } through { appcCnosControl 11 }),
then set this object to the command to be executed.
Here is the list of parameter objects that must be set for each
of the CNOS commands:
INIT_SESSION_LIMIT -
appcCnosMaxSessLimit
appcCnosMinCwinLimit
appcCnosMinClosLimit
appcCnosTargetLocLuName
appcCnosTargetParLuName
appcCnosTargetModeName
CHANGE_SESSION_LIMIT -
appcCnosMaxSessLimit
appcCnosMinCwinLimit
appcCnosMinClosLimit
appcCnosResponsible
appcCnosTargetLocLuName
appcCnosTargetParLuName
appcCnosTargetModeName
RESET_SESSION_LIMIT -
appcCnosResponsible
appcCnosDrainPart
appcCnosForce
appcCnosTargetLocLuName
appcCnosTargetParLuName
appcCnosTargetModeName
"
::= { appcCnosControl 1 }
appcCnosMaxSessLimit OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Specifies the maximum value that the local LU is to use,
during CNOS processing, for the session limit. The local LU,
as a target LU, will negotiate a higher session limit it
receives in the CNOS request down to this maximum value. The
local LU, as a source LU, will restrict the session limit it
sends in a CNOS request to a value less than or equal to this
maximum value.
If set (i.e., greater than 0), this overrides the maximum
session limit defined in the appcModeAdminTable.
This parameter should be set to the desired value before
setting the command (appcCnosCommand).
This parameter applies to the INITIALIZE_SESSION_LIMIT and
CHANGE_SESSION_LIMIT verbs."
DEFVAL { 0 }
::= { appcCnosControl 2 }
appcCnosMinCwinLimit OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Specifies the default minimum contention winner sessions
limit.
This parameter should be set to the desired value before
setting the command (appcCnosCommand).
This parameter applies to the INITIALIZE_SESSION_LIMIT and
CHANGE_SESSION_LIMIT verbs."
DEFVAL { 0 }
::= { appcCnosControl 3 }
appcCnosMinClosLimit OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Specifies the default minimum contention loser sessions limit.
This parameter should be set to the desired value before
setting the command (appcCnosCommand).
This parameter applies to the INITIALIZE_SESSION_LIMIT and
CHANGE_SESSION_LIMIT verbs."
DEFVAL { 0 }
::= { appcCnosControl 4 }
appcCnosDrainSelf OBJECT-TYPE
SYNTAX INTEGER {
no(1),
yes(2)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Specifies whether the local LU is draining its conversations
for this mode. When a mode session limit is reset (via a CNOS
RESET_SESSION_LIMIT request), the local LU could be set to
process all queued conversations before deactivating all of the
sessions (using the SNA Bracket Initiation Stopped or BIS
protocol).
This parameter should be set to the desired value before
setting the command (appcCnosCommand).
This parameter applies only to the RESET_SESSION_LIMIT verb."
DEFVAL { no }
::= { appcCnosControl 5 }
appcCnosDrainPart OBJECT-TYPE
SYNTAX INTEGER {
no(1),
yes(2)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Specifies whether the partner LU is draining its conversations
for this mode. When a mode session limit is reset (via a CNOS
RESET_SESSION_LIMIT request), the partner LU could be set to
process all queued conversations before deactivating all of the
sessions (using the SNA Bracket Initiation Stop or BIS
protocol).
This parameter should be set to the desired value before
setting the command (appcCnosCommand).
This parameter applies only to the RESET_SESSION_LIMIT verb."
DEFVAL { yes }
::= { appcCnosControl 6 }
appcCnosResponsible OBJECT-TYPE
SYNTAX INTEGER {
source(1),
target(2)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Specifies which LU is responsible for selecting and
deactivating sessions as a result of a change that decreases
the session limit or the maximum number of contention winner
sessions for the source or target LU. If no session need to be
deactivated, this parameter is ignored.
source - specifies that the source (local) LU is
responsible. The target (partner) LU
cannot negotiate this value.
target - specifies that the target (partner) LU is
responsible. The target LU can negotiate
this value to source.
This parameter should be set to the desired value before
setting the command (appcCnosCommand).
This parameter applies to the RESET_SESSION_LIMIT and
CHANGE_SESSION_LIMIT verbs."
DEFVAL { source }
::= { appcCnosControl 7 }
appcCnosForce OBJECT-TYPE
SYNTAX INTEGER {
no(1),
yes(2)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Specifies whether the local LU should force the resetting of
the session limit when certain error conditions occur that
prevent the successful exchange of CNOS request and reply.
This parameter should be set to the desired value before
setting the command (appcCnosCommand).
This parameter applies only to the RESET_SESSION_LIMIT verb."
DEFVAL { no }
::= { appcCnosControl 8 }
appcCnosTargetLocLuName OBJECT-TYPE
SYNTAX DisplayString (SIZE (1..17))
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The SNA name of the local LU to which the CNOS command is
to be applied. This field is from 1 to 17 characters in
length, including a period (.) which separates the
NetId from the NAU name if the NetId is present.
This object should be set to the desired value before setting
the command (appcCnosCommand).
This parameter applies to all CNOS verbs."
::= { appcCnosControl 9 }
appcCnosTargetParLuName OBJECT-TYPE
SYNTAX DisplayString (SIZE (1..17))
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The SNA name of the partner LU to which the CNOS command is
to be applied. This field is from 1 to 17 characters in
length, including a period (.) which separates the
NetId from the NAU name if the NetId is present.
This object should be set to the desired value before setting
the command (appcCnosCommand).
This parameter applies to all CNOS verbs."
::= { appcCnosControl 10 }
appcCnosTargetModeName OBJECT-TYPE
SYNTAX DisplayString (SIZE (1..8))
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Specifies the mode name to which the CNOS command is to be
applied.
This object should be set to the desired value before setting
the command (appcCnosCommand).
This parameter applies to all CNOS verbs."
::= { appcCnosControl 11 }
-- *********************************************************************
-- APPC LU information
-- ---------------------------------------------------------------------
-- Local LU
-- Partner LU
-- Mode
-- *********************************************************************
-- *********************************************************************
-- APPC Local LU
--
-- The entries in the following tables provide information for
-- independent and dependent LU 6.2.
--
-- *********************************************************************
-- *********************************************************************
-- APPC Local LU Admin Table
-- Objects in this table contain default or expected configuration
-- values for local 6.2 LUs.
-- *********************************************************************
appcLluAdminTable OBJECT-TYPE
SYNTAX SEQUENCE OF AppcLluAdminEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"APPC Local LU Admin Table."
::= { appcLu 1 }
appcLluAdminEntry OBJECT-TYPE
SYNTAX AppcLluAdminEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Information about local APPC LUs. "
INDEX { appcLluAdminName }
::= { appcLluAdminTable 1 }
AppcLluAdminEntry ::= SEQUENCE {
appcLluAdminName DisplayString,
appcLluAdminDepType INTEGER,
appcLluAdminLocalAddress OCTET STRING,
appcLluAdminSessLimit Integer32,
appcLluAdminBindRspMayQ INTEGER,
appcLluAdminCompression INTEGER,
appcLluAdminInBoundCompLevel INTEGER,
appcLluAdminOutBoundCompLevel INTEGER,
appcLluAdminCompRleBeforeLZ INTEGER,
appcLluAdminAlias DisplayString
}
appcLluAdminName OBJECT-TYPE
SYNTAX DisplayString (SIZE (1..17))
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Specifies the name of the local LU. This field is from 1 to
17 characters in length, including a period (.) which separates
the NetId from the NAU name if the NetId is present."
::= { appcLluAdminEntry 1 }
appcLluAdminDepType OBJECT-TYPE
SYNTAX INTEGER {
dependent(1),
independent(2)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This value identifies whether the LU is dependent or
independent."
::= { appcLluAdminEntry 2 }
appcLluAdminLocalAddress OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (1))
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The local address for this LU is a byte with a value ranging
from 0 to 254. For dependent LUs, this value ranges from 1 to
254; for independent LUs this value is always 0."
::= { appcLluAdminEntry 3 }
appcLluAdminSessLimit OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The maximum number of sessions supported by this LU."
::= { appcLluAdminEntry 4 }
appcLluAdminBindRspMayQ OBJECT-TYPE
SYNTAX INTEGER {
no(1),
yes(2)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Indicates whether or not the local LU, as the sender of a BIND
request, allows a partner partner LU to delay sending the BIND
response if the partner LU cannot process the BIND request
immediately."
::= { appcLluAdminEntry 5 }
appcLluAdminCompression OBJECT-TYPE
SYNTAX INTEGER {
prohibited(1),
required(2),
negotiable(3)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Specifies whether compression is supported. The local LU uses
this value for negotiation during session activation
(SNA BIND).
prohibited - specifies that no compression is to be used.
required - specifies that compression is required.
negotiable - specifies that the usage of compression
is to be negotiated between the LUs. The
level of compression is also negotiated."
::= { appcLluAdminEntry 6 }
appcLluAdminInBoundCompLevel OBJECT-TYPE
SYNTAX INTEGER {
none(1),
rle(2),
lz9(3),
lz10(4),
lz12(5)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Specifies the maximum level of compression supported for
inbound data. The local LU uses this value in conjunction with
appcLluAdminCompression for negotiation during session
activation (SNA BIND).
none - specifies that no compression is to be used.
rle - specifies run-length encoding compression
in which a 1 or 2 byte sequence substitution is
used for each repeated run of the same character.
lz9 - specifies Lempel-Ziv-like compression in which
9 bit codes are used to substitute repeated
substrings in the data stream. These codes are
indices that refer to entries in a common
dictionary generated adaptively at both sender and
receiver as the data flows and compression occurs.
The larger number bits used for the code, the more
storage space is required for the dictionary, but
the larger the compression ratio.
lz10 - specifies a 10 bit code Lempel-Ziv-like compression.
lz12 - specifies a 12 bit code Lempel-Ziv-like compression."
::= { appcLluAdminEntry 7 }
appcLluAdminOutBoundCompLevel OBJECT-TYPE
SYNTAX INTEGER {
none(1),
rle(2),
lz9(3),
lz10(4),
lz12(5)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Specifies the maximum level of compression supported for
outbound data. The local LU uses this value in conjunction
with appcLluAdminCompression for negotiation during session
activation (SNA BIND).
none - specifies that no compression is to be used.
rle - specifies run-length encoding compression
in which a 1 or 2 byte sequence substitution is
used for each repeated run of the same character.
lz9 - specifies Lempel-Ziv-like compression in which
9 bit codes are used to substitute repeated
substrings in the data stream. These codes are
indices that refer to entries in a common
dictionary generated adaptively at both sender and
receiver as the data flows and compression occurs.
The larger of number bits used for the code, the
more storage space is required for the dictionary,
but the larger the compression ratio.
lz10 - specifies a 10 bit code Lempel-Ziv-like compression.
lz12 - specifies a 12 bit code Lempel-Ziv-like compression."
::= { appcLluAdminEntry 8 }
appcLluAdminCompRleBeforeLZ OBJECT-TYPE
SYNTAX INTEGER {
no(1),
yes(2)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Specifies whether run-length encoding is to be applied to the
data before applying Lempel-Ziv-like compression. The local LU
uses this value for negotiation during session activation (SNA
BIND). This parameter is only supported if LZ compression is
used."
::= { appcLluAdminEntry 9 }
appcLluAdminAlias OBJECT-TYPE
SYNTAX DisplayString (SIZE (0..8))
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A local alias for the local LU. If not known or
not applicable, this object contains a zero-length
string."
::= { appcLluAdminEntry 10 }
-- *********************************************************************
-- APPC Local LU Oper Table
-- Objects in this table contain current operational values, such
-- as state values or negotiated parameters, for local 6.2 LUs.
-- *********************************************************************
appcLluOperTable OBJECT-TYPE
SYNTAX SEQUENCE OF AppcLluOperEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"APPC Local LU Operational Table."
::= { appcLu 2 }
appcLluOperEntry OBJECT-TYPE
SYNTAX AppcLluOperEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Information about local APPC LUs."
INDEX { appcLluOperName }
::= { appcLluOperTable 1 }
AppcLluOperEntry ::= SEQUENCE {
appcLluOperName DisplayString,
appcLluOperDepType INTEGER,
appcLluOperLocalAddress OCTET STRING,
appcLluOperSessLimit Integer32,
appcLluOperBindRspMayQ INTEGER,
appcLluOperCompression INTEGER,
appcLluOperInBoundCompLevel INTEGER,
appcLluOperOutBoundCompLevel INTEGER,
appcLluOperCompRleBeforeLZ INTEGER,
appcLluOperAlias DisplayString,
appcLluOperActiveSessions Gauge32
}
appcLluOperName OBJECT-TYPE
SYNTAX DisplayString (SIZE (1..17))
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Specifies the name of the local LU. This field is from 1 to
17 characters in length, including a period (.) which separates
the NetId from the NAU name if the NetId is present."
::= { appcLluOperEntry 1 }
appcLluOperDepType OBJECT-TYPE
SYNTAX INTEGER {
dependent(1),
independent(2)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This value identifies whether the LU is dependent or
independent."
::= { appcLluOperEntry 2 }
appcLluOperLocalAddress OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (1))
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The local address for this LU is a byte with a value ranging
from 0 to 254. For dependent LUs, this value ranges from 1 to
254; for independent LUs this value is always 0."
::= { appcLluOperEntry 3 }
appcLluOperSessLimit OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The maximum number of sessions supported by this LU."
::= { appcLluOperEntry 4 }
appcLluOperBindRspMayQ OBJECT-TYPE
SYNTAX INTEGER {
no(1),
yes(2)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Indicates whether or not the local LU, as the sender of a BIND
request, allows a partner LU to delay sending the BIND
response if the partner LU cannot process the BIND request
immediately."
::= { appcLluOperEntry 5 }
appcLluOperCompression OBJECT-TYPE
SYNTAX INTEGER {
prohibited(1),
required(2),
negotiable(3)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Specifies whether compression is supported. The local LU uses
this value for negotiation during session activation (SNA
BIND).
prohibited - specifies that no compression is to be used.
required - specifies that compression is required.
negotiable - specifies that the usage of compression
is to be negotiated between the LUs. The
level of compression is also negotiated."
::= { appcLluOperEntry 6 }
appcLluOperInBoundCompLevel OBJECT-TYPE
SYNTAX INTEGER {
none(1),
rle(2),
lz9(3),
lz10(4),
lz12(5)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Specifies the maximum level of compression supported for
inbound data. The local LU uses this value in conjunction with
appcLluOperCompression for negotiation during session
activation (SNA BIND).
none - specifies that no compression is to be used.
rle - specifies run-length encoding compression
in which a 1 or 2 byte sequence substitution is
used for each repeated run of the same character.
lz9 - specifies Lempel-Ziv-like compression in which
9 bit codes are used to substitute repeated
substrings in the data stream. These codes are
indices that refer to entries in a common
dictionary generated adaptively at both sender and
receiver as the data flows and compression occurs.
The larger of number bits used for the code, the
more storage space is required for the dictionary,
but the larger the compression ratio.
lz10 - specifies a 10 bit code Lempel-Ziv-like compression.
lz12 - specifies a 12 bit code Lempel-Ziv-like compression."
::= { appcLluOperEntry 7 }
appcLluOperOutBoundCompLevel OBJECT-TYPE
SYNTAX INTEGER {
none(1),
rle(2),
lz9(3),
lz10(4),
lz12(5)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Specifies the maximum level of compression supported for
outbound data. The local LU uses this value in conjunction
with appcLluAdminCompression for negotiation during session
activation (SNA BIND).
none - specifies that no compression is to be used.
rle - specifies run-length encoding compression
in which a 1 or 2 byte sequence substitution is
used for each repeated run of the same character.
lz9 - specifies Lempel-Ziv-like compression in which
9 bit codes are used to substitute repeated
substrings in the data stream. These codes are
indices that refer to entries in a common
dictionary generated adaptively at both sender and
receiver as the data flows and compression occurs.
The larger of number bits used for the code, the
more storage space is required for the dictionary,
but the larger the compression ratio.
lz10 - specifies a 10 bit code Lempel-Ziv-like compression.
lz12 - specifies a 12 bit code Lempel-Ziv-like compression."
::= { appcLluOperEntry 8 }
appcLluOperCompRleBeforeLZ OBJECT-TYPE
SYNTAX INTEGER {
no(1),
yes(2)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Specifies whether run-length encoding is to be applied to the
data before applying Lempel-Ziv-like compression. The local LU
uses this value for negotiation during session activation (SNA
BIND). This parameter is only supported if LZ compression is
used."
::= { appcLluOperEntry 9 }
appcLluOperAlias OBJECT-TYPE
SYNTAX DisplayString (SIZE (0..8))
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A local alias for the local LU. If not known or
not applicable, this object contains a zero-length
string."
::= { appcLluOperEntry 10 }
appcLluOperActiveSessions OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Specifies the total number of active APPC sessions for this
LU."
::= { appcLluOperEntry 11 }
-- *********************************************************************
-- APPC LU Pair Admin Table
-- Objects in this table contain default or expected configuration
-- values for 6.2 LU pairs. An LU pair consists of a local LU and
-- a partner LU, which may or may not be local.
-- *********************************************************************
appcLuPairAdminTable OBJECT-TYPE
SYNTAX SEQUENCE OF AppcLuPairAdminEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"APPC Partner LU administrative Table"
::= { appcLu 3 }
appcLuPairAdminEntry OBJECT-TYPE
SYNTAX AppcLuPairAdminEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Entry of APPC Partner LU Information Table.
It is indexed by the local and partner LU Names."
INDEX { appcLuPairAdminLocLuName,
appcLuPairAdminParLuName }
::= { appcLuPairAdminTable 1 }
AppcLuPairAdminEntry ::= SEQUENCE {
appcLuPairAdminLocLuName DisplayString,
appcLuPairAdminParLuName DisplayString,
appcLuPairAdminParLuAlias DisplayString,
appcLuPairAdminSessLimit Integer32,
appcLuPairAdminSessSec INTEGER,
appcLuPairAdminSecAccept INTEGER,
appcLuPairAdminLinkObjId InstancePointer,
appcLuPairAdminParaSessSup INTEGER
}
appcLuPairAdminLocLuName OBJECT-TYPE
SYNTAX DisplayString (SIZE (1..17))
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The SNA name of the local LU to which this partner LU
definition applies. This field is from 1 to 17 characters in
length, including a period (.) which separates the
NetId from the NAU name if the NetId is present.
The reserved value "*ALL" indicates that the partner LU
definition applies to all local LUs, and not just to a single
local LU."
::= { appcLuPairAdminEntry 1 }
appcLuPairAdminParLuName OBJECT-TYPE
SYNTAX DisplayString (SIZE (1..17))
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The SNA name of the partner LU.
This field is from 1 to 17 characters in
length, including a period (.) which separates the
NetId from the NAU name if the NetId is present."
::= { appcLuPairAdminEntry 2 }
appcLuPairAdminParLuAlias OBJECT-TYPE
SYNTAX DisplayString (SIZE (0..8))
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A local alias for the partner LU. If not known or
not applicable, this object contains a zero-length
string."
::= { appcLuPairAdminEntry 3 }
appcLuPairAdminSessLimit OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The maximum number of sessions supported by this partner LU."
::= { appcLuPairAdminEntry 4 }
appcLuPairAdminSessSec OBJECT-TYPE
SYNTAX INTEGER {
required(1),
accepted(2),
notAllowed(3)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Specifies the type of session-level security information that
a local LU will accept on BIND requests it receives from the
partner LU.
required - Specifies that the BIND request must carry
session level verification information that
will be verified upon receipt.
accepted - Specifies that the BIND request may carry
session level verification information that
will be verified upon receipt.
notAllowed - Specifies that the BIND request must not carry
session level verification information."
::= { appcLuPairAdminEntry 5 }
appcLuPairAdminSecAccept OBJECT-TYPE
SYNTAX INTEGER {
none(1),
conversation(2),
alreadyVerified(3),
persistentVerification(4),
aVandpV(5)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Specifies support for different levels of access security
information in ATTACH requests received from this partner LU.
Possible values are:
none - No access security information will be
accepted on allocation requests (ATTACH) from
this LU.
conversation
- Allocation requests will not be accepted that
include already verified or persistent
verification indicators. Accept
conversation-level access security
information, which must include both a user
Id and password, and may also include a
profile.
alreadyVerified
- Allocation requests will be accepted that
include already verified indicators.
Persistent verification indicators will not
be accepted.
persistentVerification
- Allocation requests will be accepted that
include persistent verification indicators.
Already verified indicators will not be
accepted.
aVandpV - Allocation requests will be accepted that
include already verified or persistent
verification indicators."
::= { appcLuPairAdminEntry 6 }
appcLuPairAdminLinkObjId OBJECT-TYPE
SYNTAX InstancePointer
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Specifies the link associated with this partner LU. This
value points to the row in the table containing information on
the link instance. (e.g., the sdlcLSAdminTable of the SNA DLC
MIB module). This object may be NULL if the link is not
specified or if a link is not applicable (as for APPN-level
nodes)."
::= { appcLuPairAdminEntry 7 }
appcLuPairAdminParaSessSup OBJECT-TYPE
SYNTAX INTEGER {
no(1),
yes(2)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Defined Parallel Sessions Supported.
Indicates whether or not multiple sessions between the partner
LU and its associated local LU are permitted. Parallel session
support also indicates that Change Number of Sessions (CNOS)
will be used to negotiate session limits between the LUs."
::= { appcLuPairAdminEntry 8 }
-- *********************************************************************
-- APPC LU Pair Oper Table
-- Objects in this table contain current operational values, such
-- as state values or negotiated parameters, for 6.2 LU pairs.
-- *********************************************************************
appcLuPairOperTable OBJECT-TYPE
SYNTAX SEQUENCE OF AppcLuPairOperEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Table of active partner/local LU pairs. Two entries are
present in the table when both LUs in a pair are local."
::= { appcLu 4 }
appcLuPairOperEntry OBJECT-TYPE
SYNTAX AppcLuPairOperEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Entry representing one partner/local LU pair."
INDEX { appcLuPairOperLocLuName,
appcLuPairOperParLuName }
::= { appcLuPairOperTable 1 }
AppcLuPairOperEntry ::= SEQUENCE {
appcLuPairOperLocLuName DisplayString,
appcLuPairOperParLuName DisplayString,
appcLuPairOperParLuAlias DisplayString,
appcLuPairOperSessLimit Integer32,
appcLuPairOperSessSec INTEGER,
appcLuPairOperSecAccept INTEGER,
appcLuPairOperLinkObjId InstancePointer,
appcLuPairOperParaSessSup INTEGER,
appcLuPairOperParaSessSupLS INTEGER,
appcLuPairOperState INTEGER
}
appcLuPairOperLocLuName OBJECT-TYPE
SYNTAX DisplayString (SIZE (1..17))
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The SNA name of the local LU. This field is from 1 to 17
characters in length, including a period (.) which separates
the NetId from the NAU name if the NetId is present.
If this object has the same value as appcLluOperName,
then the two entries being indexed apply to the same
resource (specifically, to the same local LU)."
::= { appcLuPairOperEntry 1 }
appcLuPairOperParLuName OBJECT-TYPE
SYNTAX D