Definitions of Managed Objects for Extended Border Node
RFC 2457
|
| Document |
Type |
|
RFC - Proposed Standard
(November 1998; No errata)
|
|
Last updated |
|
2013-03-02
|
|
Stream |
|
IETF
|
|
Formats |
|
plain text
pdf
html
bibtex
|
| Stream |
WG state
|
|
(None)
|
|
Document shepherd |
|
No shepherd assigned
|
| IESG |
IESG state |
|
RFC 2457 (Proposed Standard)
|
|
Consensus Boilerplate |
|
Unknown
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
Network Working Group B. Clouston
Request for Comments: 2457 Cisco Systems
Category: Standards Track B. Moore
IBM Corporation
November 1998
Definitions of Managed Objects
for Extended Border Node
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.
Copyright Notice
Copyright (C) The Internet Society (1998). All Rights Reserved.
Abstract
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 APPN (Advanced Peer-to-Peer Network) EBN
(Extended Border Node) capabilities. This memo identifies managed
objects for the EBN architecture.
Table of Contents
1.0 Introduction . . . . . . . . . . . . . . . . . . . . . . . 2
2.0 The SNMP Network Management Framework . . . . . . . . . . 2
3.0 Overview . . . . . . . . . . . . . . . . . . . . . . . . . 3
3.1 EBN MIB Structure . . . . . . . . . . . . . . . . . . . . 4
3.1.1 enbDir group . . . . . . . . . . . . . . . . . . . . . 5
3.1.2 ebnIsRscv group . . . . . . . . . . . . . . . . . . . 5
3.1.3 ebnDirConfig group . . . . . . . . . . . . . . . . . . 7
3.1.4 ebnCos group . . . . . . . . . . . . . . . . . . . . . 8
3.1.5 ebnSubnetRoutingList group . . . . . . . . . . . . . . 8
3.1.6 hbn group . . . . . . . . . . . . . . . . . . . . . . 8
4.0 Definitions . . . . . . . . . . . . . . . . . . . . . . . 9
5.0 Security Considerations . . . . . . . . . . . . . . . . . 24
6.0 Intellectual Property . . . . . . . . . . . . . . . . . . 25
7.0 Acknowledgments . . . . . . . . . . . . . . . . . . . . . 25
8.0 References . . . . . . . . . . . . . . . . . . . . . . . . 25
Clouston & Moore Standards Track [Page 1]
RFC 2457 Extended Border Node MIB November 1998
9.0 Authors' Addresses . . . . . . . . . . . . . . . . . . . . 27
10.0 Full Copyright Statement . . . . . . . . . . . . . . . . 28
1.0 Introduction
This document is a product of the SNA NAU Services MIB Working Group.
It defines a MIB module for managing devices with Advanced Peer-to-
Peer Networking (APPN) Extended Border Node (EBN) capabilities.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119, reference
[13].
2.0 The SNMP Network Management Framework
The SNMP Network Management Framework presently consists of six major
components. They are:
o the overall architecture, described in RFC 2271 [7].
o the SMI, described in RFC 1902 [3], - the mechanisms used for
describing and naming objects for the purpose of management.
o the MIB-II, STD 17, RFC 1213 [2], - the core set of managed
objects for the Internet suite of protocols.
o the protocol, STD 15, RFC 1157 [1] and/or RFC 1905 [6] and/or RFC
2272 [8] -- the protocol for accessing managed information.
o the user-based security model defined in RFC 2274 [10].
o the view-based access control model defined in RFC 2275 [11].
Textual conventions are defined in RFC 1903 [4], and conformance
statements are defined in RFC 1904 [5]. Common applications are
defined in RFC 2273 [9].
The Framework permits new objects to be defined for the purpose of
experimentation and evaluation.
This memo specifies a MIB module that is compliant to the SMIv2. A
MIB conforming to the SMIv1 can be produced through the appropriate
translation.
Clouston & Moore Standards Track [Page 2]
RFC 2457 Extended Border Node MIB November 1998
3.0 Overview
This document identifies the proposed set of objects for monitoring
the configuration and active characteristics of devices with EBN
capabilities. The Extended Border Node function is an APPN
enhancement for an APPN network node (NN). It supports topology
isolation, subnet interconnection, and session establishment between
subnets.
In a single APPN network, all network topology information is
propagated to all network nodes. Directory searches can also be
Show full document text