draft-ietf-snmpv2-smi-ds-03.txt   draft-ietf-snmpv2-smi-ds-04.txt 
Structure of Management Information Structure of Management Information
for Version 2 of the for Version 2 of the
Simple Network Management Protocol (SNMPv2) Simple Network Management Protocol (SNMPv2)
20 September 1995 | 25 September 1995 |
draft-ietf-snmpv2-smi-ds-03.txt | draft-ietf-snmpv2-smi-ds-04.txt |
Keith McCloghrie Keith McCloghrie
Editor + Editor +
Cisco Systems, Inc. Cisco Systems, Inc.
kzm@cisco.com kzm@cisco.com
Status of this Memo - Status of this Memo -
This document is an Internet-Draft. Internet-Drafts are working This document is an Internet-Draft. Internet-Drafts are working
documents of the Internet Engineering Task Force (IETF), its areas, and documents of the Internet Engineering Task Force (IETF), its areas, and
skipping to change at page 2, line 48 skipping to change at page 2, line 48
(3) Notification definitions are used when describing unsolicited (3) Notification definitions are used when describing unsolicited
transmissions of management information. An ASN.1 macro, transmissions of management information. An ASN.1 macro,
NOTIFICATION-TYPE, is used to concisely convey the syntax and NOTIFICATION-TYPE, is used to concisely convey the syntax and
semantics of a notification. semantics of a notification.
1.1. A Note on Terminology 1.1. A Note on Terminology
For the purpose of exposition, the original Internet-standard Network For the purpose of exposition, the original Internet-standard Network
Management Framework, as described in RFCs 1155, 1157, and 1212, is Management Framework, as described in RFCs 1155, 1157, and 1212, is
termed the SNMP version 1 framework (SNMPv1). The current framework is termed the SNMP version 1 framework (SNMPv1). The current framework is |
termed the SNMP version 2 framework (SNMPv2). termed the SNMP version 2 framework (SNMPv2), as described in [8]. |
2. Definitions 2. Definitions
SNMPv2-SMI DEFINITIONS ::= BEGIN SNMPv2-SMI DEFINITIONS ::= BEGIN
-- the path to the root -- the path to the root
org OBJECT IDENTIFIER ::= { iso 3 } org OBJECT IDENTIFIER ::= { iso 3 }
dod OBJECT IDENTIFIER ::= { org 6 } dod OBJECT IDENTIFIER ::= { org 6 }
internet OBJECT IDENTIFIER ::= { dod 1 } internet OBJECT IDENTIFIER ::= { dod 1 }
skipping to change at page 8, line 30 skipping to change at page 8, line 30
timeticks-value timeticks-value
TimeTicks, TimeTicks,
arbitrary-value arbitrary-value
Opaque, Opaque,
big-counter-value big-counter-value
Counter64, Counter64,
old-unsigned-integer-value unsigned-integer-value -- includes Gauge32 -
UInteger32,
unsigned-integer-value -- includes Gauge32
Unsigned32 Unsigned32
} }
-- in network-byte order -- in network-byte order
-- (this is a tagged type for historical reasons) -- (this is a tagged type for historical reasons)
IpAddress ::= IpAddress ::=
[APPLICATION 0] [APPLICATION 0]
IMPLICIT OCTET STRING (SIZE (4)) IMPLICIT OCTET STRING (SIZE (4))
-- this wraps -- this wraps
skipping to change at page 9, line 31 skipping to change at page 10, line 5
-- for backward-compatibility only -- for backward-compatibility only
Opaque ::= Opaque ::=
[APPLICATION 4] [APPLICATION 4]
IMPLICIT OCTET STRING IMPLICIT OCTET STRING
-- for counters that wrap in less than one hour with only 32 bits -- for counters that wrap in less than one hour with only 32 bits
Counter64 ::= Counter64 ::=
[APPLICATION 6] [APPLICATION 6]
IMPLICIT INTEGER (0..18446744073709551615) IMPLICIT INTEGER (0..18446744073709551615)
UInteger32 ::= -- definition for objects -
[APPLICATION 7]
IMPLICIT INTEGER (0..4294967295)
OBJECT-TYPE MACRO ::= OBJECT-TYPE MACRO ::=
BEGIN BEGIN
TYPE NOTATION ::= TYPE NOTATION ::=
"SYNTAX" Syntax "SYNTAX" Syntax
UnitsPart UnitsPart
"MAX-ACCESS" Access "MAX-ACCESS" Access
"STATUS" Status "STATUS" Status
"DESCRIPTION" Text "DESCRIPTION" Text
ReferPart ReferPart
skipping to change at page 32, line 11 skipping to change at page 32, line 11
subordinate columnar objects of the base conceptual row being augmented. subordinate columnar objects of the base conceptual row being augmented.
As such, note that creation of a base conceptual row implies the As such, note that creation of a base conceptual row implies the
correspondent creation of any conceptual row augmentations. correspondent creation of any conceptual row augmentations.
For example, a MIB designer might wish to define additional columns in For example, a MIB designer might wish to define additional columns in
an "enterprise-specific" MIB which logically extend a conceptual row in an "enterprise-specific" MIB which logically extend a conceptual row in
a "standard" MIB. The "standard" MIB definition of the conceptual row a "standard" MIB. The "standard" MIB definition of the conceptual row
would include the INDEX clause and the "enterprise-specific" MIB would would include the INDEX clause and the "enterprise-specific" MIB would
contain the definition of a conceptual row using the AUGMENTS clause. contain the definition of a conceptual row using the AUGMENTS clause.
On the other hand, it would be incorrect to use the AUGMENTS clause for On the other hand, it would be incorrect to use the AUGMENTS clause for
the relationship between RFC 1573's ifTable and the many media-specific | the relationship between RFC 1573's ifTable and the many media-specific
MIBs | MIBs which extend it for specific media (e.g., the dot3Table in RFC
which extend it for specific media (e.g., the dot3Table in RFC 1650), 1650), since not all interfaces are of the same media.
since not all interfaces are of the same media.
Note that a base conceptual row may be augmented by multiple conceptual Note that a base conceptual row may be augmented by multiple conceptual
row augmentations. row augmentations.
7.8.1. Relation between INDEX and AUGMENTS clauses 7.8.1. Relation between INDEX and AUGMENTS clauses
When defining instance identification information for a conceptual When defining instance identification information for a conceptual
table: table:
(1) If there is a one-to-one correspondence between the conceptual rows (1) If there is a one-to-one correspondence between the conceptual rows
skipping to change at page 38, line 12 skipping to change at page 38, line 12
cross-reference to a notification defined in some other information cross-reference to a notification defined in some other information
module. This is useful when de-osifying a MIB module produced by some module. This is useful when de-osifying a MIB module produced by some
other organization. other organization.
8.5. Mapping of the NOTIFICATION-TYPE value 8.5. Mapping of the NOTIFICATION-TYPE value
The value of an invocation of the NOTIFICATION-TYPE macro is the name of The value of an invocation of the NOTIFICATION-TYPE macro is the name of
the notification, which is an OBJECT IDENTIFIER, an administratively the notification, which is an OBJECT IDENTIFIER, an administratively
assigned name. In order to achieve compatibility with the procedures assigned name. In order to achieve compatibility with the procedures
employed by proxy agents (see Section 3.1.2 of [7]), the next to last | employed by proxy agents (see Section 3.1.2 of [7]), the next to last
sub-identifier in | sub-identifier in the name of any newly-defined notification must have
the name of any newly-defined notification must have the value zero. the value zero.
Sections 4.2.6 and 4.2.7 of [6] describe how the NOTIFICATION-TYPE macro Sections 4.2.6 and 4.2.7 of [6] describe how the NOTIFICATION-TYPE macro
is used to generate a SNMPv2-Trap-PDU or InformRequest-PDU, is used to generate a SNMPv2-Trap-PDU or InformRequest-PDU,
respectively. respectively.
8.6. Usage Example 8.6. Usage Example
Consider how a linkUp trap might be described: Consider how a linkUp trap might be described:
linkUp NOTIFICATION-TYPE linkUp NOTIFICATION-TYPE
skipping to change at page 39, line 22 skipping to change at page 39, line 22
DESCRIPTION DESCRIPTION
"A linkUp trap signifies that the SNMPv2 entity, acting in "A linkUp trap signifies that the SNMPv2 entity, acting in
an agent role, recognizes that one of the communication an agent role, recognizes that one of the communication
links represented in its configuration has come up." links represented in its configuration has come up."
::= { snmpTraps 4 } ::= { snmpTraps 4 }
According to this invocation, the trap authoritatively identified as According to this invocation, the trap authoritatively identified as
{ snmpTraps 4 } { snmpTraps 4 }
is used to report a link coming up. - is used to report a link coming up.
9. Refined Syntax 9. Refined Syntax
Some macros have clauses which allows syntax to be refined, Some macros have clauses which allows syntax to be refined,
specifically: the SYNTAX clause of the OBJECT-TYPE macro, and the specifically: the SYNTAX clause of the OBJECT-TYPE macro, and the
SYNTAX/WRITE-SYNTAX clauses of the MODULE-COMPLIANCE and AGENT- SYNTAX/WRITE-SYNTAX clauses of the MODULE-COMPLIANCE and AGENT-
CAPABILITIES macros [2]. However, not all refinements of syntax are CAPABILITIES macros [2]. However, not all refinements of syntax are
appropriate. In particular, the object's primitive or application type appropriate. In particular, the object's primitive or application type
must not be changed. must not be changed.
skipping to change at page 52, line 12 skipping to change at page 52, line 12
Glenn Waters (Bell-Northern Research) Glenn Waters (Bell-Northern Research)
Bert Wijnen (IBM) Bert Wijnen (IBM)
15. References 15. References
[1] Information processing systems - Open Systems Interconnection - [1] Information processing systems - Open Systems Interconnection -
Specification of Abstract Syntax Notation One (ASN.1), Specification of Abstract Syntax Notation One (ASN.1),
International Organization for Standardization. International International Organization for Standardization. International
Standard 8824, (December, 1987). Standard 8824, (December, 1987).
[2] McCloghrie, K., Editor, "Conformance Statements for Version 2 of | [2] McCloghrie, K., Editor, |
the Simple Network Management Protocol (SNMPv2)", | "Conformance Statements for Version 2 of the Simple Network
Internet Draft, Cisco Systems, September 1995. | Management Protocol (SNMPv2)", Internet Draft, Cisco Systems, |
September 1995. |
[3] McCloghrie, K., Editor, "Textual Conventions for Version 2 of the | [3] McCloghrie, K., Editor, |
Simple Network Management Protocol (SNMPv2)", | "Textual Conventions for Version 2 of the Simple Network Management
Internet Draft, Cisco Systems, September 1995. | Protocol (SNMPv2)", Internet Draft, Cisco Systems, September 1995. |
[4] Information processing systems - Open Systems Interconnection - [4] Information processing systems - Open Systems Interconnection -
Specification of Basic Encoding Rules for Abstract Syntax Notation Specification of Basic Encoding Rules for Abstract Syntax Notation
One (ASN.1), International Organization for Standardization. One (ASN.1), International Organization for Standardization.
International Standard 8825, (December, 1987). International Standard 8825, (December, 1987).
[5] McCloghrie, K., Editor, | [5] McCloghrie, K., Editor, |
"Management Information Base for Version 2 of the Simple Network "Management Information Base for Version 2 of the Simple Network
Management Protocol (SNMPv2)", Internet Draft, Cisco Systems, | Management Protocol (SNMPv2)", Internet Draft, Cisco Systems, |
September 1995. | September 1995. |
[6] McCloghrie, K., Editor, | [6] McCloghrie, K., Editor, |
"Protocol Operations for Version 2 of the Simple Network Management "Protocol Operations for Version 2 of the Simple Network Management
Protocol (SNMPv2)", Internet Draft, Cisco Systems, September 1995. | Protocol (SNMPv2)", Internet Draft, Cisco Systems, September 1995. |
[7] McCloghrie, K., Editor, | [7] McCloghrie, K., Editor, |
"Coexistence between Version 1 and Version 2 of the Internet- "Coexistence between Version 1 and Version 2 of the Internet-
standard Network Management Framework", Internet Draft, Cisco | standard Network Management Framework", Internet Draft, Cisco |
Systems, September 1995. | Systems, September 1995. |
[8] McCloghrie, K., Editor, "Introduction to Version 2 of the |
Internet-standard Network Management Framework", Internet Draft, |
Cisco Systems, September 1995. |
16. Security Considerations 16. Security Considerations
Security issues are not discussed in this memo. Security issues are not discussed in this memo.
17. Editor's Address 17. Editor's Address
Keith McCloghrie - Keith McCloghrie -
Cisco Systems, Inc. Cisco Systems, Inc.
170 West Tasman Drive | 170 West Tasman Drive
San Jose, CA 95134-1706 | San Jose, CA 95134-1706
US | US
Phone: +1 408 526 5260 Phone: +1 408 526 5260
Email: kzm@cisco.com Email: kzm@cisco.com
Table of Contents - Table of Contents -
1 Introduction .................................................... 2 1 Introduction .................................................... 2
1.1 A Note on Terminology ......................................... 2 1.1 A Note on Terminology ......................................... 2
2 Definitions ..................................................... 4 2 Definitions ..................................................... 4
3.1 The MODULE-IDENTITY macro ..................................... 5 3.1 The MODULE-IDENTITY macro ..................................... 5
 End of changes. 13 change blocks. 
29 lines changed or deleted 27 lines changed or added

This html diff was produced by rfcdiff 1.34. The latest version is available from http://tools.ietf.org/tools/rfcdiff/