rfc1696.txt
来自「RFC 的详细文档！」· 文本 代码 · 共 1,740 行 · 第 1/4 页
TXT
1,740 行
Network Working Group J. Barnes
Request for Comments: 1696 Xylogics, Inc.
Category: Standards Track L. Brown
Motorola
R. Royston
US Robotics, Inc.
S. Waldbusser
Carnegie Mellon University
August 1994
Modem Management Information Base (MIB) 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 SNMPv2 Network Management Framework ...................... 2
2.1 Object Definitions ......................................... 2
3 Definitions .................................................. 2
4 Acknowledgements ............................................. 30
5. Security Considerations ..................................... 30
6. Authors' Addresses .......................................... 31
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 describes managed objects used for managing dial-up
modems and similar dial-up devices. This MIB module provides a set
of objects that are the minimum necessary to provide the ability to
monitor and control those devices, and is consistent with the SNMP
framework and existing SNMP standards.
Barnes, Brown, Royston & Waldbusser [Page 1]
RFC 1696 Modem MIB August 1994
2. The SNMPv2 Network Management Framework
The SNMPv2 Network Management Framework consists of four major
components. They are:
o RFC 1442 which defines the SMI, the mechanisms used for
describing and naming objects for the purpose of management.
o STD 17, RFC 1213 defines MIB-II, the core set of managed objects
for the Internet suite of protocols.
o RFC 1445 which defines the administrative and other
architectural aspects of the framework.
o RFC 1448 which defines the protocol used for network access to
managed objects.
The Framework permits new objects to be defined for the purpose of
experimentation and evaluation.
2.1. Object Definitions
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)
defined in the SMI. In particular, each object object type is named
by an OBJECT IDENTIFIER, an administratively assigned name. 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 descriptor, to
refer to the object type.
3. Definitions
Modem-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, OBJECT-IDENTITY,
Counter32, Integer32 FROM SNMPv2-SMI
DisplayString FROM SNMPv2-TC
MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF
mib-2 FROM RFC1213-MIB;
mdmMIB MODULE-IDENTITY
LAST-UPDATED "9406120000Z"
ORGANIZATION "IETF Modem Management Working Group"
Barnes, Brown, Royston & Waldbusser [Page 2]
RFC 1696 Modem MIB August 1994
CONTACT-INFO
" Steven Waldbusser
Postal: Carnegie Mellon University
5000 Forbes Ave
Pittsburgh, PA, 15213
US
Tel: +1 412 268 6628
Fax: +1 412 268 4987
E-mail: waldbusser@cmu.edu"
DESCRIPTION
"The MIB module for management of dial-up modems."
::= { mdmMIB 1 }
mdmMib OBJECT IDENTIFIER ::= { mib-2 38 }
mdmMIBObjects OBJECT IDENTIFIER ::= { mdmMIB 1 }
-- conformance information
mdmConformance OBJECT IDENTIFIER ::= { mdmMIB 2 }
mdmCompliances OBJECT IDENTIFIER ::= { mdmConformance 1 }
mdmGroups OBJECT IDENTIFIER ::= { mdmConformance 2 }
-- units of conformance
mdmIDGroup OBJECT-GROUP
OBJECTS { mdmIDManufacturerOID, mdmIDProductDetails }
STATUS current
DESCRIPTION
"A collection of objects that identify the manufacturer and
model information for a modem."
::= { mdmGroups 1 }
mdmLineInterfaceGroup OBJECT-GROUP
OBJECTS { mdmLineCarrierLossTime,
mdmLineState, mdmLineCapabilitiesID,
mdmLineCapabilitiesEnableRequested,
mdmLineCapabilitiesEnableGranted }
STATUS current
DESCRIPTION
"A collection of objects that describe the configuration and
state of the modem's line interface."
::= { mdmGroups 2 }
mdmDTEInterfaceGroup OBJECT-GROUP
Barnes, Brown, Royston & Waldbusser [Page 3]
RFC 1696 Modem MIB August 1994
OBJECTS { mdmDTEActionDTROnToOff, mdmDTEActionDTROffToOn,
mdmDTESyncTimingSource, mdmDTESyncAsyncMode,
mdmDTEInactivityTimeout }
STATUS current
DESCRIPTION
"A collection of objects that describe the configuration and
state of the modem's DTE interface."
::= { mdmGroups 3 }
mdmCallControlGroup OBJECT-GROUP
OBJECTS { mdmCCRingsBeforeAnswer,
mdmCCCallSetUpFailTimer, mdmCCResultCodeEnable,
mdmCCEscapeAction, mdmCCCallDuration,
mdmCCConnectionFailReason, mdmCCStoredDialString }
STATUS current
DESCRIPTION
"A collection of objects that describe the configuration of
call control capabilities on the modem and the status of
calls placed with this modem."
::= { mdmGroups 4 }
mdmErrorControlGroup OBJECT-GROUP
OBJECTS { mdmECErrorControlUsed }
STATUS current
DESCRIPTION
"A collection of objects that describe the configuration and
state of error control on a modem."
::= { mdmGroups 5 }
mdmDataCompressionGroup OBJECT-GROUP
OBJECTS { mdmDCCompressionTypeUsed }
STATUS current
DESCRIPTION
"A collection of objects that describe the configuration and
state of data compression on a modem."
::= { mdmGroups 6 }
mdmSignalConvertorGroup OBJECT-GROUP
OBJECTS { mdmSCCurrentLineReceiveRate, mdmSCCurrentLineTransmitRate,
mdmSCInitialLineReceiveRate, mdmSCInitialLineTransmitRate,
mdmSCModulationSchemeUsed }
STATUS current
DESCRIPTION
"A collection of objects that describe the configuration and
state of error control on a modem."
::= { mdmGroups 7 }
mdmStatisticsGroup OBJECT-GROUP
Barnes, Brown, Royston & Waldbusser [Page 4]
RFC 1696 Modem MIB August 1994
OBJECTS { mdmStatsRingNoAnswers,
mdmStatsIncomingConnectionFailures,
mdmStatsIncomingConnectionCompletions,
mdmStatsFailedDialAttempts,
mdmStatsOutgoingConnectionFailures,
mdmStatsOutgoingConnectionCompletions,
mdmStatsRetrains,
mdmStats2400OrLessConnections, mdmStats2400To14400Connections,
mdmStatsGreaterThan14400Connections,
mdmStatsErrorControlledConnections,
mdmStatsCompressedConnections,
mdmStatsCompressionEfficiency,
mdmStatsSentOctets, mdmStatsReceivedOctets,
mdmStatsSentDataFrames, mdmStatsReceivedDataFrames,
mdmStatsResentFrames, mdmStatsErrorFrames }
STATUS current
DESCRIPTION
"A collection of objects that describe the state of calls on
this modem."
::= { mdmGroups 8 }
mdmNumber OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of modem rows in the modem table. This value
defines the maximum value of the mdmIndex object."
::= { mdmMIBObjects 1 }
-- The modem ID table.
mdmIDTable OBJECT-TYPE
SYNTAX SEQUENCE OF MdmIDEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The base table for the modems managed by this MIB. The
mdmLineTable, mdmDTEInterfaceTable, mdmCallControlTable, and
mdmStatsTable all augment the rows defined in this table."
::= { mdmMIBObjects 2 }
mdmIDEntry OBJECT-TYPE
SYNTAX MdmIDEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Entries in this table are created only by the agent. One
Barnes, Brown, Royston & Waldbusser [Page 5]
RFC 1696 Modem MIB August 1994
entry exists for each modem managed by the agent."
INDEX { mdmIndex }
::= { mdmIDTable 1 }
MdmIDEntry ::= SEQUENCE {
mdmIndex Integer32,
mdmIDManufacturerOID OBJECT IDENTIFIER,
mdmIDProductDetails DisplayString
}
mdmIndex OBJECT-TYPE
SYNTAX Integer32 (1..65535)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A unique number for each modem that ranges from 1 to
mdmNumber. The value must remain constant at least from one
re-initialization of the network management agent to the
next."
::= { mdmIDEntry 1 }
mdmIDManufacturerOID OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This value is intended to identify the manufacturer, model,
and version of this modem. This may be used to identify the
existance of enterprise-specific functions and behaviours."
REFERENCE
"V.58 attribute manufacturerID subfield ManufacturerOI"
::= { mdmIDEntry 2 }
mdmIDProductDetails OBJECT-TYPE
SYNTAX DisplayString (SIZE (0..79))
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A textual description of this device, including the
manufacturer's name, modem model name, hardware revision,
firmware revision, and optionally, its serial number. The
exact format of this description is defined by the vendor.
This description may only contain characters from the NVT
ASCII character set."
REFERENCE
"V.58 attribute manufacturerID subfield productDetails"
::= { mdmIDEntry 3 }
Barnes, Brown, Royston & Waldbusser [Page 6]
RFC 1696 Modem MIB August 1994
-- The modem Line Interface Table
mdmLineTable OBJECT-TYPE
SYNTAX SEQUENCE OF MdmLineEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The modem Line Table augments the modem ID table."
::= { mdmMIBObjects 3 }
mdmLineEntry OBJECT-TYPE
SYNTAX MdmLineEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Entries in this table are created only by the agent. One
entry exists for each modem managed by the agent."
AUGMENTS { mdmIDEntry }
::= { mdmLineTable 1 }
MdmLineEntry ::= SEQUENCE {
mdmLineCarrierLossTime Integer32,
mdmLineState INTEGER
}
mdmLineCarrierLossTime OBJECT-TYPE
SYNTAX Integer32 (1..255)
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Duration in 10ths of a second the modem waits after loss of
carrier before hanging up. If this value is set to `255',
the modem will not hang up upon loss of carrier. This
allows the modem to distinguish between a momentary lapse in
line quality and a true disconnect and can be useful to tune
the tolerance of the modem to lines of poor quality."
REFERENCE "V.58 lineSignalFailDisconnectTimer"
::= { mdmLineEntry 1 }
mdmLineState OBJECT-TYPE
SYNTAX INTEGER {
unknown(1),
onHook(2),
offHook(3), -- and not connected
connected(4),
busiedOut(5),
reset(6)
}
Barnes, Brown, Royston & Waldbusser [Page 7]
RFC 1696 Modem MIB August 1994
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Allows the inspection and alteration of the state of the
modem. Management commands may change the state to `on-
hook', `busied-out', or `reset' from any state. No other
alterations are permitted from the management protocol.
When this object is set to reset, the modem shall be reset
and the value will change to the modem's new, implementation
dependent state."
::= { mdmLineEntry 2 }
mdmLineCapabilitiesTable OBJECT-TYPE
SYNTAX SEQUENCE OF MdmLineCapabilitiesEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A list of protocol capabilities for this modem."
::= { mdmMIBObjects 4 }
mdmLineCapabilitiesEntry OBJECT-TYPE
SYNTAX MdmLineCapabilitiesEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A listing of the protocol(s) that this modem is capable of.
Entries in this table are created only by the agent. One
entry exists for each protocol that the modem is capable of,
regardless of whether that protocol is enabled or not.
This table is useful for providing an inventory of the
capabilities on a modem, and allowing the manager to enable
or disable capabilities from the menu of available
possibilities. Row creation is not required to enable or
disable capabilities."
INDEX { mdmIndex, mdmLineCapabilitiesIndex }
::= { mdmLineCapabilitiesTable 1 }
⌨️ 快捷键说明
复制代码Ctrl + C
搜索代码Ctrl + F
全屏模式F11
增大字号Ctrl + =
减小字号Ctrl + -
显示快捷键?