As per Relevance of the word sessions, we have this rfc below:
Network Working Group B. Clouston,
Request for Comments: 2232 Cisco
Category: Standards Track B. Moore,
IBM
November 1997
Definitions of Managed
for DLUR using SMIv
Status of this
This document specifies an Internet standards track protocol for
Internet community, and requests discussion and suggestions
improvements. Please refer to the current edition of the "
Official Protocol Standards" (STD 1) for the standardization
and status of this protocol. Distribution of this memo is unlimited
Copyright
Copyright (C) The Internet Society (1997). All Rights Reserved
Table of
1. Status of this Memo .................................... 1
2. Introduction ........................................... 1
3. The SNMP Network Management Framework .................. 2
4. Overview ............................................... 2
4.1 DLUR MIB structure .................................... 3
5. Definitions ............................................ 5
6. Acknowledgments ........................................ 18
7. References ............................................. 19
8. Security Considerations ................................ 19
9. Authors' Addresses ..................................... 20
10. Full Copyright Statement ................................ 21
2.
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 monitoring and
network devices with DLUR (Dependent LU Requester) capabilities
This memo identifies managed objects for the DLUR protocol
Clouston & Moore Standards Track [Page 1]
RFC 2232 Managed Objects for DLUR using SMIv2 November 1997
3. The SNMP Network Management
The SNMP Network Management Framework consists of several components
For the purpose of this specification, the applicable components
the Framework are the SMI and related documents [1, 2, 3],
define the mechanisms used for describing and naming objects for
purpose of management
The Framework permits new objects to be defined for the purpose
experimentation and evaluation
4.
This document identifies objects for monitoring the configuration
active characteristics of devices with DLUR capabilities.
LU requester/server (DLUR/S) is an extension to the Advanced Peer
to-Peer Networking (APPN) architecture that provides dependent
services in APPN networks. See the SNANAU APPN MIB [4]
management of APPN networks
The base APPN architecture only provided for transport of
between independent logical units (LUs). However, customers have
enormous investment in applications based on dependent LU types
DLUR/S provides for support of dependent LU sessions in an
network
A dependent LU server (DLUS) is an APPN node that provides
Services Control Point (SSCP) services over an APPN network to
secondary dependent LUs by using SSCP-PU (physical unit) and SSCP-
sessions whose flows are encapsulated on LU 6.2 session flows
the DLUS node and the appropriate dependent LU requester (DLUR) node
The secondary dependent LUs may be local to the DLUR node, or
adjacent type 2.0 or 2.1 nodes
The LU 6.2 control sessions between a DLUS node and a DLUR node
referred to as a CPSVRMGR pipe. CPSVRMGR refers to the mode used
the sessions
In this document, we describe DLUR managed objects
The DLUR terms and overall architecture are described in [5].
Highlights of the management functions supported by the DLUR
module include the following
Clouston & Moore Standards Track [Page 2]
RFC 2232 Managed Objects for DLUR using SMIv2 November 1997
o Identifying the node's DLUR
o Displaying the physical units (PUs) this node is
o Identification of Dependent LU
o Displaying the state of control sessions to Dependent
Servers
This MIB module does not support
o Management of dependent LU
o Configuration of DLUR nodes
o Changing the state of control session to the
o Displaying the dependent LUs this node is
o Traps. The APPN MIB contains a trap for Alert conditions
may affect DLUR resources. The value for the
object contained in the alertTrap is determined by
implementation. It may contain a VariablePointer from the
MIB. The APPN/DLUR Alerts are defined in [6].
4.1. DLUR MIB
Although DLUR is an extension to APPN, the DLUR MIB relies
little upon the APPN MIB. The dlurNodeCpName object in this MIB
the same value as the appnNodeCpName object in the APPN MIB. If
dlurPuLsName object in the MIB has the same value as the
object in the APPN MIB, then the two objects are referring to
same link station
The DLUR MIB module contains the following collections of objects
o dlurNodeInfo--objects representing the capabilities
architecture options supported by the DLUR implementation,
well as default primary and backup DLUSs
o dlurPuInfo--objects describing the PUs that this APPN node
supporting with DLUR
o dlurDlusInfo--objects describing the control sessions
DLUSs
These are described below in more detail
Clouston & Moore Standards Track [Page 3]
RFC 2232 Managed Objects for DLUR using SMIv2 November 1997
4.1.1. dlurNodeInfo
The dlurNodeInfo group consists of the following objects and table
1) dlurNodeCapabilities
These objects represent the capabilities and options of the
implementation, such as the release level of the
2)
This table identifies the list of defined backup DLUSs for all
served by this DLUR, if there is no specific DLUS backup list for
PU. The list is in descending order of preference as a backup DLUS
4.1.2. dlurPuInfo
The dlurPuInfo group consists of the following tables
1)
This table has an entry for each PU this node is supporting via DLUR
including the locally known name, the SSCP supplied name (if known),
and the PU status
2)
This table contains the backup DLUS list defined on a PU basis.
table has an entry for each specifically defined backup DLUS on
PU. The first index to the entry is the PU name, which organizes
table by PU name. The second index is a ranking which further
the table in descending order of preference as a backup DLUS for
PU
If a PU name is not found in this table,
dlurDefaultDefBackupDlusNameTable is used as a backup list for
PU
4.1.3. dlurDlusInfo
This group consists of the following table
1)
This table contains information about the control sessions (
pipes) with the DLUS, including the control point (CP) name of
DLUS and the status of the control session
Clouston & Moore Standards Track [Page 4]
RFC 2232 Managed Objects for DLUR using SMIv2 November 1997
5.
APPN-DLUR-MIB DEFINITIONS ::=
DisplayString,
FROM SNMPv2-
OBJECT-TYPE, MODULE-IDENTITY, Unsigned32
FROM SNMPv2-
MODULE-COMPLIANCE, OBJECT-
FROM SNMPv2-
FROM SNA-NAU-
FROM APPN-MIB
dlurMIB MODULE-
LAST-UPDATED "9705101500Z
ORGANIZATION "IETF SNA NAU MIB WG / AIW APPN/HPR MIBs SIG
CONTACT-
"
Bob
Cisco
7025 Kit Creek
P.O. Box 14987
Research Triangle Park, NC 27709,
Tel: 1 919 472 2333
E-mail: clouston@cisco.
Bob
IBM
800 Park Offices
RHJA/664
P.O. Box 12195
Research Triangle Park, NC 27709,
Tel: 1 919 254 4436
E-mail: remoore@ralvm6.vnet.ibm.
"
"This is the MIB module for objects used to
network devices with DLUR capabilities. This
contains information that is useful for managing an
product that implements a DLUR (Dependent Logical
Clouston & Moore Standards Track [Page 5]
RFC 2232 Managed Objects for DLUR using SMIv2 November 1997
Requester). The DLUR product has a client/
relationship with an APPN product that implements a
(Dependent Logical Unit Server)."
::= { snanauMIB 5 }
-- snanauMIB ::= { mib-2 34 }
-- *********************************************************************
-- Textual
-- *********************************************************************
-- SnaControlPointName is imported from the APPN
-- *********************************************************************
dlurObjects OBJECT IDENTIFIER ::= { dlurMIB 1 }
-- *********************************************************************
dlurNodeInfo OBJECT IDENTIFIER ::= { dlurObjects 1 }
-- *********************************************************************
-- DLUR Capabilities of the
--
-- This group represents the capabilities and options of the
-- implementation
-- *********************************************************************
dlurNodeCapabilities OBJECT IDENTIFIER ::= { dlurNodeInfo 1 }
dlurNodeCpName OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"Administratively assigned network name for the APPN node
this DLUR implementation resides. If this object has the
value as the appnNodeCpName object in the APPN MIB, then
two objects are referring to the same APPN node."
::= { dlurNodeCapabilities 1 }
dlurReleaseLevel OBJECT-
SYNTAX DisplayString (SIZE (2))
MAX-ACCESS read-
STATUS
"The DLUR release level of this implementation. This is
value that is encoded in the DLUR/DLUS Capabilites (CV 51).
To insure consistent display, this one-byte value is
here as two displayable characters that are equivalent to
hexadecimal display. For example, if the one-byte value
Clouston & Moore Standards Track [Page 6]
RFC 2232 Managed Objects for DLUR using SMIv2 November 1997
encoded in CV51 is X'01', this object will contain
displayable string '01'."
::= { dlurNodeCapabilities 2 }
dlurAnsSupport OBJECT-
SYNTAX INTEGER {
continueOrStop(1),
stopOnly(2)
}
MAX-ACCESS read-
STATUS
"Automatic Network Shutdown (ANS) capability of this node
- 'continueOrStop' indicates that the DLUR
supports either ANS value (continue or stop)
specified by the DLUS on ACTPU for each PU
- 'stopOnly' indicates that the DLUR implementation
supports the ANS value of stop
ANS = continue means that the DLUR node will keep LU-
sessions active even if SSCP-PU and SSCP-LU control
are interrupted
ANS = stop means that LU-LU sessions will be interrupted
the SSCP-PU and SSCP-LU sessions are interrupted."
::= { dlurNodeCapabilities 3 }
dlurMultiSubnetSupport OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"Indication of whether this DLUR implementation can
CPSVRMGR sessions that cross NetId boundaries."
::= { dlurNodeCapabilities 4 }
dlurDefaultDefPrimDlusName OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The SNA name of the defined default primary DLUS for all
the PUs served by this DLUR. This can be overridden for
Clouston & Moore Standards Track [Page 7]
RFC 2232 Managed Objects for DLUR using SMIv2 November 1997
particular PU by a defined primary DLUS for that PU
represented by the dlurPuDefPrimDlusName object."
::= { dlurNodeCapabilities 5 }
dlurNetworkNameForwardingSupport OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"Indication of whether this DLUR implementation
forwarding of Network Name control vectors on ACTPUs
ACTLUs to DLUR-served PUs and their associated LUs
This object corresponds to byte 9. bit 3 of cv51."
::= { dlurNodeCapabilities 6 }
dlurNondisDlusDlurSessDeactSup OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"Indication of whether this DLUR implementation
nondisruptive deactivation of its DLUR-DLUS sessions
Upon receiving from a DLUS an UNBIND for the CPSVRMGR
with sense data X'08A0 000B', a DLUR that supports
option immediately begins attempting to activate a
pipe with a DLUS other than the one that sent the UNBIND
This object corresponds to byte 9. bit 4 of cv51."
::= { dlurNodeCapabilities 7 }
-- *********************************************************************
-- DLUR default defined backup DLUS
-- *********************************************************************
dlurDefaultDefBackupDlusTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
"This table contains an ordered list of defined backup
for all of the PUs served by this DLUR. These can
overridden for a particular PU by a list of defined
DLUSs for that PU, represented by
dlurPuDefBackupDlusNameTable. Entries in this table
Clouston & Moore Standards Track [Page 8]
RFC 2232 Managed Objects for DLUR using SMIv2 November 1997
ordered from most preferred default backup DLUS to
preferred."
::= { dlurNodeInfo 2 }
dlurDefaultDefBackupDlusEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"This table is indexed by an integer-valued index,
orders the entries from most preferred default backup
to least preferred."
INDEX { dlurDefaultDefBackupDlusIndex }
::= { dlurDefaultDefBackupDlusTable 1 }
DlurDefaultDefBackupDlusEntry ::= SEQUENCE {
dlurDefaultDefBackupDlusIndex Unsigned32,
dlurDefaultDefBackupDlusName
}
dlurDefaultDefBackupDlusIndex OBJECT-
SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS not-
STATUS
"Index for this table. The index values start at 1,
which identifies the most preferred default backup DLUS."
::= { dlurDefaultDefBackupDlusEntry 1 }
dlurDefaultDefBackupDlusName OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"Fully qualified name of a default backup DLUS for PUs
by this DLUR."
::= { dlurDefaultDefBackupDlusEntry 2 }
-- *********************************************************************
-- PU
--
-- The following table carries information about the PUs that this
-- node is supporting via DLUR
Clouston & Moore Standards Track [Page 9]
RFC 2232 Managed Objects for DLUR using SMIv2 November 1997
-- *********************************************************************
dlurPuInfo OBJECT IDENTIFIER ::= { dlurObjects 2 }
dlurPuTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
"Information about the PUs supported by this DLUR."
::= { dlurPuInfo 1 }
dlurPuEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"Entry in a table of PU information, indexed by PU name."
INDEX { dlurPuName }
::= { dlurPuTable 1 }
DlurPuEntry ::= SEQUENCE {
dlurPuName DisplayString
dlurPuSscpSuppliedName DisplayString
dlurPuStatus INTEGER
dlurPuAnsSupport INTEGER
dlurPuLocation INTEGER
dlurPuLsName DisplayString
dlurPuDlusSessnStatus INTEGER
dlurPuActiveDlusName DisplayString
dlurPuDefPrimDlusName
}
dlurPuName OBJECT-
SYNTAX DisplayString (SIZE (1..17))
MAX-ACCESS not-
STATUS
"Locally administered name of the PU."
::= { dlurPuEntry 1 }
dlurPuSscpSuppliedName OBJECT-
SYNTAX DisplayString (SIZE (0..17))
MAX-ACCESS read-
Clouston & Moore Standards Track [Page 10]
RFC 2232 Managed Objects for DLUR using SMIv2 November 1997
STATUS
"The SNA name of the PU. This value is supplied to a PU by
SSCP that activated it. If a value has not been supplied,
zero-length string is returned."
::= { dlurPuEntry 2 }
dlurPuStatus OBJECT-
SYNTAX INTEGER {
reset(1),
pendReqActpuRsp(2),
pendActpu(3),
pendActpuRsp(4),
active(5),
pendLinkact(6),
pendDactpuRsp(7),
pendInop(8),
pendInopActpu(9)
}
MAX-ACCESS read-
STATUS
"Status of the DLUR-supported PU. The following values
defined
reset(1) -
pendReqActpuRsp(2) - pending a response from the
to a Request
pendActpu(3) - pending an ACTPU from the
pendActpuRsp(4) - pending an ACTPU response from the
active(5) -
pendLinkact(6) - pending activation of the link to
downstream
pendDactpuRsp(7) - pending a DACTPU response from the
pendInop(8) - the CPSVRMGR pipe became
while the DLUR was pending an
response from the
pendInopActpu(9) - when the DLUR was in the
state, a CPSVRMGR pipe became
and a new ACTPU was received over it
before a response to the
ACTPU was received from the PU."
::= { dlurPuEntry 3 }
dlurPuAnsSupport OBJECT-
SYNTAX INTEGER {
Clouston & Moore Standards Track [Page 11]
RFC 2232 Managed Objects for DLUR using SMIv2 November 1997
continue(1),
stop(2)
}
MAX-ACCESS read-
STATUS
"The Automatic Network Shutdown (ANS) support configured
this PU. This value (as configured by the
administrator) is sent by DLUS with ACTPU for each PU
- 'continue' means that the DLUR node will attempt to
LU-LU sessions active even if SSCP-PU and SSCP-
control sessions are interrupted
- 'stop' means that LU-LU sessions will be
when the SSCP-PU and SSCP-LU sessions are interrupted."
::= { dlurPuEntry 4 }
dlurPuLocation OBJECT-
SYNTAX INTEGER {
internal(1),
downstream(2) }
MAX-ACCESS read-
STATUS
"Location of the DLUR-support PU
internal(1) - internal to the APPN node itself (no link
downstream(2) - downstream of the APPN node (connected
a link)."
::= { dlurPuEntry 5 }
dlurPuLsName OBJECT-
SYNTAX DisplayString (SIZE (0..10))
MAX-ACCESS read-
STATUS
"Administratively assigned name of the link station
which a downstream PU is connected to this DLUR. A zero-
string is returned for internal PUs. If this object has
same value as the appnLsName object in the APPN MIB, then
two are identifying the same link station."
::= { dlurPuEntry 6 }
dlurPuDlusSessnStatus OBJECT-
SYNTAX INTEGER {
Clouston & Moore Standards Track [Page 12]
RFC 2232 Managed Objects for DLUR using SMIv2 November 1997
reset(1),
pendingActive(2),
active(3),
pendingInactive(4)
}
MAX-ACCESS read-
STATUS
"Status of the control session to the DLUS identified
dlurPuActiveDlusName. This is a combination of the
states for the contention-winner and contention-loser sessions
reset(1) - none of the cases
pendingActive(2) - either contention-winner session
contention-loser session is pending
active(3) - contention-winner and contention-
sessions are both
pendingInactive(4) - either contention-winner session
contention-loser session is
inactive - this test is made AFTER
'pendingActive' test
The following matrix provides a different representation
how the values of this object are related to the
states of the contention-winner and contention-loser sessions
| pA | pI | A | X = !(pA | pI | A
C ++++++++++++++++++++++++++++++++++
o pA | 2 | 2 | 2 | 2
n ++++++++++++++++++++++++++++++++++
l pI | 2 | 4 | 4 | 4
o ++++++++++++++++++++++++++++++++++
s A | 2 | 4 | 3 | 1
e ++++++++++++++++++++++++++++++++++
r X | 2 | 4 | 1 | 1
++++++++++++++++++++++++++++++++++
"
::= { dlurPuEntry 7 }
dlurPuActiveDlusName OBJECT-
SYNTAX DisplayString (SIZE (0..17))
MAX-ACCESS read-
STATUS
"The SNA name of the active DLUS for this PU. If its
is not zero, this name follows the SnaControlPointName
Clouston & Moore Standards Track [Page 13]
RFC 2232 Managed Objects for DLUR using SMIv2 November 1997
convention. A zero-length string indicates that the PU
not currently have an active DLUS."
::= { dlurPuEntry 8 }
dlurPuDefPrimDlusName OBJECT-
SYNTAX DisplayString (SIZE (0..17))
MAX-ACCESS read-
STATUS
"The SNA name of the defined primary DLUS for this PU, if
has been defined. If present, this name follows
SnaControlPointName textual convention. A zero-length
indicates that no primary DLUS has been defined for this PU,
which case the global default represented by
dlurDefaultDefPrimDlusName object is used."
::= { dlurPuEntry 9 }
-- *****************************************
-- Defined backup DLUS table for a
-- *****************************************
dlurPuDefBackupDlusTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
"This table contains an ordered list of defined backup
for those PUs served by this DLUR that have their own
backup DLUSs. PUs that have no entries in this table use
global default backup DLUSs for the DLUR, represented by
dlurDefaultDefBackupDlusNameTable. Entries in this table
ordered from most preferred backup DLUS to least preferred
each PU."
::= { dlurPuInfo 2 }
dlurPuDefBackupDlusEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"This table is indexed by PU name and by an integer-
index, which orders the entries from most preferred backup
for the PU to least preferred."
INDEX { dlurPuDefBackupDlusPuName
Clouston & Moore Standards Track [Page 14]
RFC 2232 Managed Objects for DLUR using SMIv2 November 1997
dlurPuDefBackupDlusIndex }
::= { dlurPuDefBackupDlusTable 1 }
DlurPuDefBackupDlusEntry ::= SEQUENCE {
dlurPuDefBackupDlusPuName DisplayString
dlurPuDefBackupDlusIndex Unsigned32,
dlurPuDefBackupDlusName
}
dlurPuDefBackupDlusPuName OBJECT-
SYNTAX DisplayString (SIZE (1..17))
MAX-ACCESS not-
STATUS
"Locally administered name of the PU. If this object has
same value as the dlurPuName object, then the two
identifying the same PU."
::= { dlurPuDefBackupDlusEntry 1 }
dlurPuDefBackupDlusIndex OBJECT-
SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS not-
STATUS
"Secondary index for this table. The index values start at 1,
which identifies the most preferred backup DLUS for the PU."
::= { dlurPuDefBackupDlusEntry 2 }
dlurPuDefBackupDlusName OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"Fully qualified name of a backup DLUS for this PU."
::= { dlurPuDefBackupDlusEntry 3 }
-- *********************************************************************
-- DLUS Control Sessions (CPSVRMGR Pipes
--
-- This table contains information about DLUS control sessions,
-- known as CPSVRMGR pipes. Although DLUR uses a pair of
-- sessions for communication, for the purpose of status,
-- about these two sessions is combined to yield a single status for
-- requester/server connection
Clouston & Moore Standards Track [Page 15]
RFC 2232 Managed Objects for DLUR using SMIv2 November 1997
-- *********************************************************************
dlurDlusInfo OBJECT IDENTIFIER ::= { dlurObjects 3 }
dlurDlusTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
"Information about DLUS control sessions."
::= { dlurDlusInfo 1}
dlurDlusEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"This entry is indexed by the name of the DLUS."
INDEX { dlurDlusName }
::= { dlurDlusTable 1 }
DlurDlusEntry ::= SEQUENCE {
dlurDlusName SnaControlPointName
dlurDlusSessnStatus
}
dlurDlusName OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"The SNA name of a DLUS with which this DLUR currently has
CPSVRMGR pipe established."
::= { dlurDlusEntry 1 }
dlurDlusSessnStatus OBJECT-
SYNTAX INTEGER {
reset(1),
pendingActive(2),
active(3),
pendingInactive(4)
}
MAX-ACCESS read-
STATUS
Clouston & Moore Standards Track [Page 16]
RFC 2232 Managed Objects for DLUR using SMIv2 November 1997
"Status of the CPSVRMGR pipe between the DLUR and this DLUS
This is a combination of the separate states for
contention-winner and contention-loser sessions
reset(1) - none of the cases
pendingActive(2) - either contention-winner session
contention-loser session is pending
active(3) - contention-winner and contention-
sessions are both
pendingInactive(4) - either contention-winner session
contention-loser session is
inactive - this test is made AFTER
'pendingActive' test
The following matrix provides a different representation
how the values of this object are related to the
states of the contention-winner and contention-loser sessions
| pA | pI | A | X = !(pA | pI | A
C ++++++++++++++++++++++++++++++++++
o pA | 2 | 2 | 2 | 2
n ++++++++++++++++++++++++++++++++++
l pI | 2 | 4 | 4 | 4
o ++++++++++++++++++++++++++++++++++
s A | 2 | 4 | 3 | 1
e ++++++++++++++++++++++++++++++++++
r X | 2 | 4 | 1 | 1
++++++++++++++++++++++++++++++++++
"
::= { dlurDlusEntry 2 }
-- ***************************************************************
-- Conformance
-- ***************************************************************
dlurConformance OBJECT IDENTIFIER ::= { dlurMIB 2 }
dlurCompliances OBJECT IDENTIFIER ::= { dlurConformance 1 }
dlurGroups OBJECT IDENTIFIER ::= { dlurConformance 2 }
-- Compliance
dlurCompliance MODULE-
STATUS
Clouston & Moore Standards Track [Page 17]
RFC 2232 Managed Objects for DLUR using SMIv2 November 1997
"The compliance statement for the SNMPv2 entities
implement the DLUR MIB."
MODULE -- this
-- Unconditionally mandatory
MANDATORY-GROUPS { dlurConfGroup }
::= { dlurCompliances 1 }
-- Units of
dlurConfGroup OBJECT-
OBJECTS {
dlurNodeCpName
dlurReleaseLevel
dlurAnsSupport
dlurMultiSubnetSupport
dlurNetworkNameForwardingSupport
dlurNondisDlusDlurSessDeactSup
dlurDefaultDefPrimDlusName
dlurDefaultDefBackupDlusName
dlurPuSscpSuppliedName
dlurPuStatus
dlurPuAnsSupport
dlurPuLocation
dlurPuLsName
dlurPuDlusSessnStatus
dlurPuActiveDlusName
dlurPuDefPrimDlusName
dlurPuDefBackupDlusName
}
STATUS
"A collection of objects providing information on
implementation of APPN DLUR."
::= { dlurGroups 1 }
-- end of conformance
6.
This MIB module is the product of the IETF SNA NAU MIB WG and the
APPN/HPR MIBs SIG
Clouston & Moore Standards Track [Page 18]
RFC 2232 Managed Objects for DLUR using SMIv2 November 1997
7.
[1] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser
"Structure of Management Information for version 2
the Simple Network Management Protocol (SNMPv2)", RFC 1902,
January 1996.
[2] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser
"Textual Conventions for Version 2 of the
Network Management Protocol (SNMPv2)", RFC 1903, January 1996.
[3] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser
"Conformance Statements for Version 2 of the
Network Management Protocol (SNMPv2)", RFC 1904, January 1996.
[4] Clouston, B., and B. Moore, "Definition of Managed Objects
APPN", RFC 2155, June 1997.
[5] IBM, Systems Network Architecture Advanced Peer-to-
Networking Dependent LU Requester Architecture Reference
Version 1.2, SV40-1010-01, December 1995.
[6] IBM, SNA/MS Formats, GC31-8302-00.
8. Security
In most cases, MIBs are not themselves security risks; if
security is operating as intended, the use of a MIB to
information about a system, or to change some parameter at
system, is a tool, not a threat
None of the read-only objects in the DLUR MIB reports a password
user data, or anything else that is particularly sensitive.
enterprises view their network configuration itself, as well
information about network usage and performance, as corporate assets
such enterprises may wish to restrict SNMP access to most of
objects in the MIB
There are no read-write objects in the DLUR MIB
Clouston & Moore Standards Track [Page 19]
RFC 2232 Managed Objects for DLUR using SMIv2 November 1997
9. Authors'
Bob
Cisco
7025 Kit Creek
P.O. Box 14987
Research Triangle Park, NC 27709,
Phone: +1 919 472 2333
EMail: clouston@cisco.
Bob
IBM
800 Park Offices
CNMA/664
P.O. Box 12195
Research Triangle Park, NC 27709,
Phone: +1 919 254 4436
EMail: remoore@ralvm6.vnet.ibm.
Clouston & Moore Standards Track [Page 20]
RFC 2232 Managed Objects for DLUR using SMIv2 November 1997
10. Full Copyright
Copyright (C) The Internet Society (1997). All Rights Reserved
This document and translations of it may be copied and furnished
others, and derivative works that comment on or otherwise explain
or assist in its implementation may be prepared, copied,
and distributed, in whole or in part, without restriction of
kind, provided that the above copyright notice and this paragraph
included on all such copies and derivative works. However,
document itself may not be modified in any way, such as by
the copyright notice or references to the Internet Society or
Internet organizations, except as needed for the purpose
developing Internet standards in which case the procedures
copyrights defined in the Internet Standards process must
followed, or as required to translate it into languages other
English
The limited permissions granted above are perpetual and will not
revoked by the Internet Society or its successors or assigns
This document and the information contained herein is provided on
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED,
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE
Clouston & Moore Standards Track [Page 21]
if you see any problems within the linking, don't worry be happy,
this is version 0.1 of the Relevance System and you gotta expect some crappy subroutines sometimes,
just be content we did not write this in Java, which would have made this "bigger and better" HAHAHHA.
RFC documents can be found at I.E.T.F.
Relevance System Copyright © 2002 Spectrum WorldResearch
other technical nosh by ServerMasters Corporation
collaboration of BobX
