Network Working Group B. Clouston, Editor Request for Comments: 2232 Cisco Systems Category: Standards Track B. Moore, Editor IBM Corporation November 1997
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.
Copyright (C) The Internet Society (1997). All Rights Reserved.
1. Status of this Memo
2. Introduction
3. The SNMP Network Management Framework
4. Overview
4.1 DLUR MIB structure
5. Definitions
6. Acknowledgments
7. References
8. Security Considerations
9. Authors' Addresses
10. Full Copyright Statement
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 controlling network devices with DLUR (Dependent LU Requester) capabilities. This memo identifies managed objects for the DLUR protocol.
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 [1, 2, 3], 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.
This document identifies objects for monitoring the configuration and active characteristics of devices with DLUR capabilities. Dependent LU requester/server (DLUR/S) is an extension to the Advanced Peer- to-Peer Networking (APPN) architecture that provides dependent LU services in APPN networks. See the SNANAU APPN MIB [4] for management of APPN networks.
The base APPN architecture only provided for transport of data between independent logical units (LUs). However, customers have an enormous investment in applications based on dependent LU types. DLUR/S provides for support of dependent LU sessions in an APPN network.
A dependent LU server (DLUS) is an APPN node that provides System Services Control Point (SSCP) services over an APPN network to remote secondary dependent LUs by using SSCP-PU (physical unit) and SSCP-LU sessions whose flows are encapsulated on LU 6.2 session flows between the DLUS node and the appropriate dependent LU requester (DLUR) node. The secondary dependent LUs may be local to the DLUR node, or in adjacent type 2.0 or 2.1 nodes.
The LU 6.2 control sessions between a DLUS node and a DLUR node are referred to as a CPSVRMGR pipe. CPSVRMGR refers to the mode used for 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 MIB module include the following:
This MIB module does not support:
Although DLUR is an extension to APPN, the DLUR MIB relies very little upon the APPN MIB. The dlurNodeCpName object in this MIB has the same value as the appnNodeCpName object in the APPN MIB. If the dlurPuLsName object in the MIB has the same value as the appnLsName object in the APPN MIB, then the two objects are referring to the same link station.
The DLUR MIB module contains the following collections of objects:
These are described below in more detail.
The dlurNodeInfo group consists of the following objects and table:
1) dlurNodeCapabilities group
These objects represent the capabilities and options of the DLUR implementation, such as the release level of the implementation
2) dlurDefaultDefBackupDlusTable
This table identifies the list of defined backup DLUSs for all PUs served by this DLUR, if there is no specific DLUS backup list for the PU. The list is in descending order of preference as a backup DLUS.
The dlurPuInfo group consists of the following tables:
1) dlurPuTable
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) dlurPuDefBackupDlusTable
This table contains the backup DLUS list defined on a PU basis. The table has an entry for each specifically defined backup DLUS on each PU. The first index to the entry is the PU name, which organizes the table by PU name. The second index is a ranking which further sorts the table in descending order of preference as a backup DLUS for the PU.
If a PU name is not found in this table, the
dlurDefaultDefBackupDlusNameTable is used as a backup list for that
PU.
This group consists of the following table:
1) dlurDlusTable
This table contains information about the control sessions (CPSVRMGR pipes) with the DLUS, including the control point (CP) name of the DLUS and the status of the control session.
OBJECT-TYPE, MODULE-IDENTITY, Unsigned32
FROM SNMPv2-SMI
MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF
snanauMIB
FROM SNA-NAU-MIB
SnaControlPointName
FROM APPN-MIB;
"
Bob Clouston
Cisco Systems
7025 Kit Creek Road
Tel: 1 919 472 2333 E-mail: clouston@cisco.com
Bob Moore
IBM Corporation
800 Park Offices Drive
RHJA/664
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 DLUR capabilities. This MIB contains information that is useful for managing an APPN product that implements a DLUR (Dependent Logical Unit
Requester). The DLUR product has a client/server relationship with an APPN product that implements a DLUS (Dependent Logical Unit Server)."
dlurObjects OBJECT IDENTIFIER ::= { dlurMIB 1 }
::= { dlurNodeCapabilities 1 }
encoded in CV51 is X'01', this object will contain the displayable string '01'."
::= { dlurNodeCapabilities 2 }
- 'continueOrStop' indicates that the DLUR implementation supports either ANS value (continue or stop) as specified by the DLUS on ACTPU for each PU. - 'stopOnly' indicates that the DLUR implementation only supports the ANS value of stop.
ANS = continue means that the DLUR node will keep LU-LU sessions active even if SSCP-PU and SSCP-LU control sessions are interrupted.
ANS = stop means that LU-LU sessions will be interrupted when the SSCP-PU and SSCP-LU sessions are interrupted."
::= { dlurNodeCapabilities 3 }
::= { dlurNodeCapabilities 4 }
particular PU by a defined primary DLUS for that PU, represented by the dlurPuDefPrimDlusName object."
::= { dlurNodeCapabilities 5 }
This object corresponds to byte 9. bit 3 of cv51."
::= { dlurNodeCapabilities 6 }
This object corresponds to byte 9. bit 4 of cv51."
::= { dlurNodeCapabilities 7 }
ordered from most preferred default backup DLUS to least preferred."
::= { dlurNodeInfo 2 }
INDEX { dlurDefaultDefBackupDlusIndex }
::= { dlurDefaultDefBackupDlusTable 1 }
dlurDefaultDefBackupDlusIndex Unsigned32, dlurDefaultDefBackupDlusName SnaControlPointName }
::= { dlurDefaultDefBackupDlusEntry 1 }
::= { dlurDefaultDefBackupDlusEntry 2 }
::= { dlurPuInfo 1 }
INDEX { dlurPuName }
::= { dlurPuTable 1 }
dlurPuName DisplayString, dlurPuSscpSuppliedName DisplayString, dlurPuStatus INTEGER, dlurPuAnsSupport INTEGER, dlurPuLocation INTEGER, dlurPuLsName DisplayString, dlurPuDlusSessnStatus INTEGER, dlurPuActiveDlusName DisplayString, dlurPuDefPrimDlusName DisplayString }
::= { dlurPuEntry 1 }
STATUS current
DESCRIPTION
"The SNA name of the PU. This value is supplied to a PU by the
SSCP that activated it. If a value has not been supplied, a
zero-length string is returned."
::= { dlurPuEntry 2 }
reset(1) - reset pendReqActpuRsp(2) - pending a response from the DLUS to a Request ACTPU pendActpu(3) - pending an ACTPU from the DLUS pendActpuRsp(4) - pending an ACTPU response from the PU active(5) - active pendLinkact(6) - pending activation of the link to a downstream PU pendDactpuRsp(7) - pending a DACTPU response from the PU pendInop(8) - the CPSVRMGR pipe became inoperative while the DLUR was pending an ACTPU response from the PU pendInopActpu(9) - when the DLUR was in the pendInop state, a CPSVRMGR pipe became active and a new ACTPU was received over it, before a response to the previous ACTPU was received from the PU." ::= { dlurPuEntry 3 }
continue(1),
stop(2)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The Automatic Network Shutdown (ANS) support configured for
this PU. This value (as configured by the network
administrator) is sent by DLUS with ACTPU for each PU.
- 'continue' means that the DLUR node will attempt to keep LU-LU sessions active even if SSCP-PU and SSCP-LU control sessions are interrupted. - 'stop' means that LU-LU sessions will be interrupted when the SSCP-PU and SSCP-LU sessions are interrupted." ::= { dlurPuEntry 4 }
internal(1) - internal to the APPN node itself (no link) downstream(2) - downstream of the APPN node (connected via a link)." ::= { dlurPuEntry 5 }
::= { dlurPuEntry 6 }
reset(1),
pendingActive(2),
active(3),
pendingInactive(4)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Status of the control session to the DLUS identified in
dlurPuActiveDlusName. This is a combination of the separate
states for the contention-winner and contention-loser sessions:
reset(1) - none of the cases below pendingActive(2) - either contention-winner session or contention-loser session is pending active active(3) - contention-winner and contention-loser sessions are both active pendingInactive(4) - either contention-winner session or contention-loser session is pending inactive - this test is made AFTER the 'pendingActive' test.
The following matrix provides a different representation of how the values of this object are related to the individual states of the contention-winner and contention-loser sessions:
Conwinner
| pA | pI | A | X = !(pA | pI | A) C ++++++++++++++++++++++++++++++++++
++++++++++++++++++++++++++++++++++ "
convention. A zero-length string indicates that the PU does not currently have an active DLUS."
::= { dlurPuEntry 8 }
::= { dlurPuEntry 9 }
::= { dlurPuInfo 2 }
INDEX { dlurPuDefBackupDlusPuName,
dlurPuDefBackupDlusIndex }
::= { dlurPuDefBackupDlusTable 1 }
dlurPuDefBackupDlusPuName DisplayString, dlurPuDefBackupDlusIndex Unsigned32, dlurPuDefBackupDlusName SnaControlPointName }
::= { dlurPuDefBackupDlusEntry 1 }
::= { dlurPuDefBackupDlusEntry 2 }
::= { dlurPuDefBackupDlusEntry 3 }
::= { dlurDlusInfo 1}
INDEX { dlurDlusName }
::= { dlurDlusTable 1 }
dlurDlusName SnaControlPointName, dlurDlusSessnStatus INTEGER }
::= { dlurDlusEntry 1 }
DESCRIPTION
"Status of the CPSVRMGR pipe between the DLUR and this DLUS.
This is a combination of the separate states for the
contention-winner and contention-loser sessions:
reset(1) - none of the cases below pendingActive(2) - either contention-winner session or contention-loser session is pending active active(3) - contention-winner and contention-loser sessions are both active pendingInactive(4) - either contention-winner session or contention-loser session is pending inactive - this test is made AFTER the 'pendingActive' test.
The following matrix provides a different representation of how the values of this object are related to the individual states of the contention-winner and contention-loser sessions:
Conwinner
| pA | pI | A | X = !(pA | pI | A) C ++++++++++++++++++++++++++++++++++
++++++++++++++++++++++++++++++++++ "
"The compliance statement for the SNMPv2 entities which implement the DLUR MIB."
MODULE -- this module
::= { dlurCompliances 1 }
::= { dlurGroups 1 }
This MIB module is the product of the IETF SNA NAU MIB WG and the AIW APPN/HPR MIBs SIG.
[1] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Structure of Management Information for version 2 of 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 Simple
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 Simple
Network Management Protocol (SNMPv2)", RFC 1904, January 1996.
[4] Clouston, B., and B. Moore, "Definition of Managed Objects for APPN", RFC 2155, June 1997.
[5] IBM, Systems Network Architecture Advanced Peer-to-Peer Networking Dependent LU Requester Architecture Reference, Version 1.2, SV40-1010-01, December 1995.
[6] IBM, SNA/MS Formats, GC31-8302-00.
In most cases, MIBs are not themselves security risks; if SNMP security is operating as intended, the use of a MIB to view information about a system, or to change some parameter at the 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. Some enterprises view their network configuration itself, as well as information about network usage and performance, as corporate assets; such enterprises may wish to restrict SNMP access to most of the objects in the MIB.
There are no read-write objects in the DLUR MIB.
Bob Clouston
Cisco Systems
7025 Kit Creek Road
Phone: +1 919 472 2333
EMail: clouston@cisco.com
Bob Moore
IBM Corporation
800 Park Offices Drive
CNMA/664
Phone: +1 919 254 4436
EMail: remoore@ralvm6.vnet.ibm.com
Copyright (C) The Internet Society (1997). All Rights Reserved.
This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English.
The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.