XYPLEX BOOTSTRAP CLIENT MIB 22 May 91
Definitions of Managed Objects
for Xyplex Bootstrap Clients
22 May 1991
Xyplex Document Number 420-0537-A
Xyplex, Inc.
330 Codman Hill Road
Boxborough, MA 01719
(508) 264-9900
support@xyplex.com
1. Status of this Memo
This document is submitted to the Internet MIB repository
and to Xyplex users as a Xyplex private extension to the
SNMP MIB. Distribution of this memo is unlimited. Please
express comments to Xyplex.
2. Abstract
This memo defines a private portion of the Management
Information Base (MIB), within the Xyplex branch, for use
[Page 1]
XYPLEX BOOTSTRAP CLIENT MIB 22 May 91
with SNMP over various transport services, such as UDP or
Ethernet. In particular, it defines objects for managing a
client of Xyplex bootstrap service.
This memo does not specify a standard for the Internet
community. It describes a standard for Xyplex products.
[Page 2]
XYPLEX BOOTSTRAP CLIENT MIB 22 May 91
3. Historical Perspective
As reported in RFC 1052, IAB Recommendations for the
Development of Internet Network Management Standards [1], a
two-prong strategy for network management of TCP/IP-based
internets was undertaken. In the short-term, the Simple
Network Management Protocol (SNMP), defined in RFC 1067, was
to be used to manage nodes in the Internet community. In
the long-term, the use of the OSI network management
framework was to be examined. Two documents were produced
to define the management information: RFC 1065, which
defined the Structure of Management Information (SMI), and
RFC 1066, which defined the Management Information Base
(MIB). Both of these documents were designed so as to be
compatible with both the SNMP and the OSI network management
framework.
This strategy was quite successful in the short-term:
Internet-based network management technology was fielded, by
both the research and commercial communities, within a few
months. As a result of this, portions of the Internet
community became network manageable in a timely fashion.
As reported in RFC 1109, Report of the Second Ad Hoc Network
Management Review Group [2], the requirements of the SNMP
and the OSI network management frameworks were more
different than anticipated. As such, the requirement for
compatibility between the SMI/MIB and both frameworks was
suspended. This action permitted the operational network
management framework, based on the SNMP, to respond to new
operational needs in the Internet community by producing
MIB-II.
In May of 1990, the core documents were elevated to
"Standard Protocols" with "Recommended" status. As such,
the Internet- standard network management framework consists
of: Structure and Identification of Management Information
for TCP/IP-based internets, RFC 1155 [4], which describes
how managed objects contained in the MIB are defined;
Management Information Base for Network Management of
TCP/IP-based internets, which describes the managed objects
contained in the MIB, RFC 1156 [5]; and, the Simple Network
Management Protocol, RFC 1157 [6], which defines the
protocol used to manage these objects.
Consistent with the IAB directive to produce simple,
[Page 3]
XYPLEX BOOTSTRAP CLIENT MIB 22 May 91
workable systems in the short-term, the list of managed
objects defined in the Internet-standard MIB was derived by
taking only those elements which are considered essential.
However, the SMI defined three extensibility mechanisms:
one, the addition of new standard objects through the
definitions of new versions of the MIB; two, the addition of
widely-available but non- standard objects through the
experimental subtree; and three, the addition of private
objects through the enterprises subtree. Such additional
objects can not only be used for vendor-specific elements,
but also for experimentation as required to further the
knowledge of which other objects are essential.
This memo defines extensions to the MIB using the third
method. It contains definitions of managed objects in
various Xyplex products, using ASN.1 conventions specified
in [10].
[Page 4]
XYPLEX BOOTSTRAP CLIENT MIB 22 May 91
4. Objects
Managed objects are accessed via a virtual information
store, termed the Management Information Base or MIB.
Objects in the MIB are defined using the subset of Abstract
Syntax Notation One (ASN.1) [7] defined in the SMI. In
particular, each object has a name, a syntax, and an
encoding. The name is an object identifier, an
administratively assigned name, which specifies an object
type. The object type together with an object instance
serves to uniquely identify a specific instantiation of the
object. For human convenience, we often use a textual
string, termed the OBJECT DESCRIPTOR, to also refer to the
object type.
The syntax of an object type defines the abstract data
structure corresponding to that object type. The ASN.1
language is used for this purpose. However, the SMI [4]
purposely restricts the ASN.1 constructs which may be used.
These restrictions are explicitly made for simplicity.
The encoding of an object type is simply how that object
type is represented using the object type's syntax.
Implicitly tied to the notion of an object type's syntax and
encoding is how the object type is represented when being
transmitted on the network.
The SMI specifies the use of the basic encoding rules of
ASN.1 [8], subject to the additional requirements imposed by
the SNMP.
4.1. Format of Definitions
Section 6 contains the specification of all object types
contained in this MIB module. The object types are defined
using the conventions defined in the SMI, as amended by the
extensions specified in [9].
[Page 5]
XYPLEX BOOTSTRAP CLIENT MIB 22 May 91
5. Overview
The Bootstrap Client MIB applies to Xyplex systems that use
the Xyplex bootstrap service to dump or load their system
image, while that system is incapable of running full-
featured software. Typically this is while the system is
running from Read-Only Memory (ROM), and the MIB available
will be only the Boostrap Client MIB. The Bootstrap Client
MIB is not intended for use when a full-function Xyplex SNMP
MIB is available.
The Bootstrap Client MIB is mandatory for all Xyplex systems
that use the bootstrap service. Widespread availability of
the Bootstrap Client MIB is likely to be slow, as it
requires changes to ROM code.
The MIB comprises one base object.
As a convenience to the reader, the base object is:
bootClientStatus
[Page 6]
XYPLEX BOOTSTRAP CLIENT MIB 22 May 91
6. Definitions
XYPLEX-BOOT-CLIENT-MIB DEFINITIONS ::= BEGIN
IMPORTS
enterprises
FROM RFC1155-SMI
DisplayString
FROM RFC1158-MIB
OBJECT-TYPE
FROM RFC1212-CONCISE-MIB;
xyplex OBJECT IDENTIFIER ::= { enterprises 33 }
bootClient OBJECT IDENTIFIER ::= { xyplex 12 }
-- This MIB module uses the extended OBJECT-TYPE macro as
-- defined in [9]
-- this is the MIB module for clients of Xyplex bootstrap
-- service
[Page 7]
XYPLEX BOOTSTRAP CLIENT MIB 22 May 91
-- the Bootstrap Client group
-- Implementation of this group is mandatory for all Xyplex
-- systems that use the Xyplex bootstrap service
bootClientStatus OBJECT-TYPE
SYNTAX DisplayString (SIZE (0..1400))
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The overall status of the bootstrapping operation,
including, for example, what is presently happening
and error information."
::= { bootClient 1 }
END
[Page 8]
XYPLEX BOOTSTRAP CLIENT MIB 22 May 91
7. References
[1] V. Cerf, IAB Recommendations for the Development of
Internet Network Management Standards. Internet Working
Group Request for Comments 1052. Network Information
Center, SRI International, Menlo Park, California, (April,
1988).
[2] V. Cerf, Report of the Second Ad Hoc Network Management
Review Group, Internet Working Group Request for Comments
1109. Network Information Center, SRI International, Menlo
Park, California, (August, 1989).
[3] M.T. Rose (editor), Management Information Base for
Network Management of TCP/IP-based internets, Internet
Working Group Request for Comments 1158. Network
Information Center, SRI International, Menlo Park,
California, (May, 1990).
[4] M.T. Rose and K. McCloghrie, Structure and
Identification of Management Information for TCP/IP-based
internets, Internet Working Group Request for Comments 1155.
Network Information Center, SRI International, Menlo Park,
California, (May, 1990).
[5] K. McCloghrie and M.T. Rose, Management Information
Base for Network Management of TCP/IP-based
internets:MIB-II, Internet Working Group Request for
Comments 1213. Network Information Center, SRI
International, Menlo Park, California, (March 1991).
[6] J.D. Case, M.S. Fedor, M.L. Schoffstall, and J.R.
Davin, Simple Network Management Protocol, Internet Working
Group Request for Comments 1157. Network Information
Center, SRI International, Menlo Park, California, (May,
1990).
[7] Information processing systems - Open Systems
Interconnection - Specification of Abstract Syntax Notation
One (ASN.1), International Organization for Standardization.
International Standard 8824, (December, 1987).
[8] Information processing systems - Open Systems
Interconnection - Specification of Basic Encoding Rules for
Abstract Notation One (ASN.1), International Organization
for Standardization. International Standard 8825,
[Page 9]
XYPLEX BOOTSTRAP CLIENT MIB 22 May 91
(December, 1987).
[9] M.T. Rose, K. McCloghrie (editors), Towards Concise MIB
Definitions, Internet Working Group Request for Comments
1212. Network Information Center, SRI International, Menlo
Park, California, (March, 1991).
[10] Definitions of Managed Objects for Xyplex Systems,
Xyplex document number 420-0545, (August, 1991).
[Page 10]