-- <interface> "." <address>, where <interface> is the
-- decimal representation of ipNetToMediaIfIndex and
-- <address> is ipNetToMediaNetAddress in
-- "dot notation".
REGISTERED AS {attributes 8};
ipNetToMediaIfIndex ATTRIBUTE
WITH ATTRIBUTE SYNTAX OIM-Module.Integer;
MATCHES FOR Equality;
-- SEE MIB II [16] for attribute semantics
REGISTERED AS {ipNetToMediaEntry 1};
ipNetToMediaNetAddress ATTRIBUTE
WITH ATTRIBUTE SYNTAX
RFC1065-SMI.IpAddress;
MATCHES FOR Equality;
-- SEE MIB II [16] for attribute semantics
REGISTERED AS {ipNetToMediaEntry 3};
ipNetToMediaPhysAddress ATTRIBUTE
WITH ATTRIBUTE SYNTAX
OIM-Module.PhysAddress;
MATCHES FOR Equality;
-- SEE MIB II [16] for attribute semantics
REGISTERED AS {ipNetToMediaEntry 2};
ipNetToMediaTableId ATTRIBUTE
WITH ATTRIBUTE SYNTAX
OIM-Module.PrintString;
MATCHES FOR Equality;
-- This is the distinguishing attribute for the
-- Ip Net to Media Table.
-- An empty string is used for a single instance.
REGISTERED AS {attributes 7};
ipNetToMediaType ATTRIBUTE
WITH ATTRIBUTE SYNTAX
OIM-Module.IpNetToMediaType;
MATCHES FOR Equality;
-- SEE MIB II [16] for attribute semantics
REGISTERED AS {ipNetToMediaEntry 4};
ipOutDiscards ATTRIBUTE
WITH ATTRIBUTE SYNTAX RFC1065-SMI.Counter;
MATCHES FOR Equality, Ordering;
-- SEE MIB II [16] for attribute semantics
REGISTERED AS {ip 11};
ipOutNoRoutes ATTRIBUTE
WITH ATTRIBUTE SYNTAX RFC1065-SMI.Counter;
MATCHES FOR Equality, Ordering;
-- SEE MIB II [16] for attribute semantics
REGISTERED AS {ip 12};
ipOutRequests ATTRIBUTE
WITH ATTRIBUTE SYNTAX RFC1065-SMI.Counter;
MATCHES FOR Equality, Ordering;
-- SEE MIB II [16] for attribute semantics
REGISTERED AS {ip 10};
ipReasmFails ATTRIBUTE
WITH ATTRIBUTE SYNTAX RFC1065-SMI.Counter;
MATCHES FOR Equality, Ordering;
-- SEE MIB II [16] for attribute semantics
REGISTERED AS {ip 16};
ipReasmOKs ATTRIBUTE
WITH ATTRIBUTE SYNTAX RFC1065-SMI.Counter;
MATCHES FOR Equality, Ordering;
-- SEE MIB II [16] for attribute semantics
REGISTERED AS {ip 15};
ipReasmReqds ATTRIBUTE
WITH ATTRIBUTE SYNTAX RFC1065-SMI.Counter;
MATCHES FOR Equality, Ordering;
-- SEE MIB II [16] for attribute semantics
REGISTERED AS {ip 14};
ipReasmTimeout ATTRIBUTE
WITH ATTRIBUTE SYNTAX OIM-Module.Integer;
MATCHES FOR Equality, Ordering;
-- SEE MIB II [16] for attribute semantics
REGISTERED AS {ip 13};
ipRouteAge ATTRIBUTE
WITH ATTRIBUTE SYNTAX OIM-Module.Integer;
MATCHES FOR Equality, Ordering;
-- SEE MIB II [16] for attribute semantics
REGISTERED AS {ipRouteEntry 10};
ipRouteDest ATTRIBUTE
WITH ATTRIBUTE SYNTAX RFC1065-SMI.IpAddress;
MATCHES FOR Equality;
-- SEE MIB II [16] for attribute semantics
REGISTERED AS {ipRouteEntry 1};
ipRouteEntryId ATTRIBUTE
WITH ATTRIBUTE SYNTAX
OIM-Module.PrintString;
MATCHES FOR Equality;
-- This attribute identifies the ip route table entry.
-- The format is <dest>, where <dest> is
-- ipRouteDest represented in "dot notation.
REGISTERED AS {attributes 20};
ipRouteIfIndex ATTRIBUTE
WITH ATTRIBUTE SYNTAX OIM-Module.Integer;
MATCHES FOR Equality;
-- SEE MIB II [16] for attribute semantics
REGISTERED AS {ipRouteEntry 2};
ipRouteInfo ATTRIBUTE
WITH ATTRIBUTE SYNTAX OIM-Module.ObjectId;
MATCHES FOR Equality;
-- SEE MIB II [16] for attribute semantics
REGISTERED AS {ipRouteEntry 13};
ipRouteMask ATTRIBUTE
WITH ATTRIBUTE SYNTAX RFC1065-SMI.IpAddress;
MATCHES FOR Equality;
-- SEE MIB II [16] for attribute semantics
REGISTERED AS {ipRouteEntry 11};
ipRouteMetric1 ATTRIBUTE
WITH ATTRIBUTE SYNTAX OIM-Module.Integer;
MATCHES FOR Equality, Ordering;
-- SEE MIB II [16] for attribute semantics
REGISTERED AS {ipRouteEntry 3};
ipRouteMetric2 ATTRIBUTE
WITH ATTRIBUTE SYNTAX OIM-Module.Integer;
MATCHES FOR Equality, Ordering;
-- SEE MIB II [16] for attribute semantics
REGISTERED AS {ipRouteEntry 4};
ipRouteMetric3 ATTRIBUTE
WITH ATTRIBUTE SYNTAX OIM-Module.Integer;
MATCHES FOR Equality, Ordering;
-- SEE MIB II [16] for attribute semantics
REGISTERED AS {ipRouteEntry 5};
ipRouteMetric4 ATTRIBUTE
WITH ATTRIBUTE SYNTAX OIM-Module.Integer;
MATCHES FOR Equality, Ordering;
-- SEE MIB II [16] for attribute semantics
REGISTERED AS {ipRouteEntry 6};
ipRouteMetric5 ATTRIBUTE
WITH ATTRIBUTE SYNTAX OIM-Module.Integer;
MATCHES FOR Equality, Ordering;
-- SEE MIB II [16] for attribute semantics
REGISTERED AS {ipRouteEntry 12};
ipRouteNextHop ATTRIBUTE
WITH ATTRIBUTE SYNTAX RFC1065-SMI.IpAddress;
MATCHES FOR Equality;
-- SEE MIB II [16] for attribute semantics
REGISTERED AS {ipRouteEntry 7};
ipRouteProto ATTRIBUTE
WITH ATTRIBUTE SYNTAX OIM-Module.IpRouteProto;
MATCHES FOR Equality;
-- SEE MIB II [16] for attribute semantics
REGISTERED AS {ipRouteEntry 9};
ipRouteType ATTRIBUTE
WITH ATTRIBUTE SYNTAX OIM-Module.IpRouteType;
MATCHES FOR Equality;
-- SEE MIB II [16] for attribute semantics
REGISTERED AS {ipRouteEntry 8};
ipRoutingDiscards ATTRIBUTE
WITH ATTRIBUTE SYNTAX RFC1065-SMI.Counter;
MATCHES FOR Equality, Ordering;
-- SEE MIB II [16] for attribute semantics
REGISTERED AS {ip 23};
ipRoutingTableId ATTRIBUTE
WITH ATTRIBUTE SYNTAX
OIM-Module.PrintString;
MATCHES FOR Equality;
-- unique id which identifies the
-- Ip Routing Table instance.
-- An empty string is used for a single instance.
REGISTERED AS {attributes 6};
snmpEnableAuthenTraps ATTRIBUTE
WITH ATTRIBUTE SYNTAX
OIM-Module.SnmpEnableAuthenTraps;
MATCHES FOR Equality;
-- SEE MIB II [16] for attribute semantics
REGISTERED AS {snmp 30};
snmpId ATTRIBUTE
WITH ATTRIBUTE SYNTAX
OIM-Module.PrintString;
MATCHES FOR Equality;
-- naming attribute for snmp
-- An empty string is used for a single instance.
REGISTERED AS {attributes 18};
snmpInASNParseErrs ATTRIBUTE
WITH ATTRIBUTE SYNTAX
RFC1065-SMI.Counter;
MATCHES FOR Equality, Ordering;
-- SEE MIB II [16] for attribute semantics
REGISTERED AS {snmp 6};
snmpInBadCommunityNames ATTRIBUTE
WITH ATTRIBUTE SYNTAX
RFC1065-SMI.Counter;
MATCHES FOR Equality, Ordering;
-- SEE MIB II [16] for attribute semantics
REGISTERED AS {snmp 4};
snmpInBadCommunityUses ATTRIBUTE
WITH ATTRIBUTE SYNTAX
RFC1065-SMI.Counter;
MATCHES FOR Equality, Ordering;
-- SEE MIB II [16] for attribute semantics
REGISTERED AS {snmp 5};
snmpInBadValues ATTRIBUTE
WITH ATTRIBUTE SYNTAX
RFC1065-SMI.Counter;
MATCHES FOR Equality, Ordering;
-- SEE MIB II [16] for attribute semantics
REGISTERED AS {snmp 10};
snmpInBadVersions ATTRIBUTE
WITH ATTRIBUTE SYNTAX
RFC1065-SMI.Counter;
MATCHES FOR Equality, Ordering;
-- SEE MIB II [16] for attribute semantics
REGISTERED AS {snmp 3};
snmpInGenErrs ATTRIBUTE
WITH ATTRIBUTE SYNTAX RFC1065-SMI.Counter;
MATCHES FOR Equality, Ordering;
-- SEE MIB II [16] for attribute semantics
REGISTERED AS {snmp 12};
snmpInGetNexts ATTRIBUTE
WITH ATTRIBUTE SYNTAX
RFC1065-SMI.Counter;
MATCHES FOR Equality, Ordering;
-- SEE MIB II [16] for attribute semantics
REGISTERED AS {snmp 16};
snmpInGetRequests ATTRIBUTE
WITH ATTRIBUTE SYNTAX
RFC1065-SMI.Counter;
MATCHES FOR Equality, Ordering;
-- SEE MIB II [16] for attribute semantics
REGISTERED AS {snmp 15};
snmpInGetResponses ATTRIBUTE
WITH ATTRIBUTE SYNTAX
RFC1065-SMI.Counter;
MATCHES FOR Equality, Ordering;
-- SEE MIB II [16] for attribute semantics
REGISTERED AS {snmp 18};
snmpInNoSuchNames ATTRIBUTE
WITH ATTRIBUTE SYNTAX
RFC1065-SMI.Counter;
MATCHES FOR Equality, Ordering;
-- SEE MIB II [16] for attribute semantics
REGISTERED AS {snmp 9};
snmpInPkts ATTRIBUTE
WITH ATTRIBUTE SYNTAX RFC1065-SMI.Counter;
MATCHES FOR Equality, Ordering;
-- SEE MIB II [16] for attribute semantics
REGISTERED AS {snmp 1};
snmpInReadOnlys ATTRIBUTE
WITH ATTRIBUTE SYNTAX
RFC1065-SMI.Counter;
MATCHES FOR Equality, Ordering;
-- SEE MIB II [16] for attribute semantics
REGISTERED AS {snmp 11};
snmpInSetRequests ATTRIBUTE
WITH ATTRIBUTE SYNTAX
RFC1065-SMI.Counter;
MATCHES FOR Equality, Ordering;
-- SEE MIB II [16] for attribute semantics
REGISTERED AS {snmp 17};
snmpInTooBigs ATTRIBUTE
WITH ATTRIBUTE SYNTAX RFC1065-SMI.Counter;
MATCHES FOR Equality, Ordering;
-- SEE MIB II [16] for attribute semantics
REGISTERED AS {snmp 8};
snmpInTotalReqVars ATTRIBUTE
WITH ATTRIBUTE SYNTAX
RFC1065-SMI.Counter;
MATCHES FOR Equality, Ordering;
-- SEE MIB II [16] for attribute semantics
REGISTERED AS {snmp 13};
snmpInTotalSetVars ATTRIBUTE
WITH ATTRIBUTE SYNTAX
RFC1065-SMI.Counter;
MATCHES FOR Equality, Ordering;
-- SEE MIB II [16] for attribute semantics
REGISTERED AS {snmp 14};
snmpInTraps ATTRIBUTE
WITH ATTRIBUTE SYNTAX RFC1065-SMI.Counter;
MATCHES FOR Equality, Ordering;
-- SEE MIB II [16] for attribute semantics
REGISTERED AS {snmp 19};
snmpOutBadValues ATTRIBUTE
WITH ATTRIBUTE SYNTAX
RFC1065-SMI.Counter;
MATCHES FOR Equality, Ordering;
-- SEE MIB II [16] for attribute semantics
REGISTERED AS {snmp 22};
snmpOutGenErrs ATTRIBUTE
WITH ATTRIBUTE SYNTAX
RFC1065-SMI.Counter;
MATCHES FOR Equality, Ordering;
-- SEE MIB II [16] for attribute semantics
REGISTERED AS {snmp 24};
snmpOutGetNexts ATTRIBUTE
WITH ATTRIBUTE SYNTAX
RFC1065-SMI.Counter;
MATCHES FOR Equality, Ordering;
-- SEE MIB II [16] for attribute semantics
REGISTERED AS {snmp 26};
snmpOutGetRequests ATTRIBUTE
WITH ATTRIBUTE SYNTAX
RFC1065-SMI.Counter;
MATCHES FOR Equality, Ordering;
-- SEE MIB II [16] for attribute semantics
REGISTERED AS {snmp 25};
snmpOutGetResponses ATTRIBUTE
WITH ATTRIBUTE SYNTAX
RFC1065-SMI.Counter;
MATCHES FOR Equality, Ordering;
-- SEE MIB II [16] for attribute semantics
REGISTERED AS {snmp 28};
snmpOutNoSuchNames ATTRIBUTE
WITH ATTRIBUTE SYNTAX
RFC1065-SMI.Counter;
MATCHES FOR Equality, Ordering;
-- SEE MIB II [16] for attribute semantics
REGISTERED AS {snmp 21};
snmpOutPkts ATTRIBUTE
WITH ATTRIBUTE SYNTAX RFC1065-SMI.Counter;
MATCHES FOR Equality, Ordering;
-- SEE MIB II [16] for attribute semantics
REGISTERED AS {snmp 2};
snmpOutSetRequests ATTRIBUTE
WITH ATTRIBUTE SYNTAX
RFC1065-SMI.Counter;
MATCHES FOR Equality, Ordering;
-- SEE MIB II [16] for attribute semantics
REGISTERED AS {snmp 27};
snmpOutTooBigs ATTRIBUTE
WITH ATTRIBUTE SYNTAX
RFC1065-SMI.Counter;
MATCHES FOR Equality, Ordering;
-- SEE MIB II [16] for attribute semantics
REGISTERED AS {snmp 20};
snmpOutTraps ATTRIBUTE
WITH ATTRIBUTE SYNTAX RFC1065-SMI.Counter;
MATCHES FOR Equality, Ordering;
-- SEE MIB II [16] for attribute semantics
REGISTERED AS {snmp 29};
sysContact ATTRIBUTE
WITH ATTRIBUTE SYNTAX
OIM-Module.PrintString;
MATCHES FOR Equality;
-- SEE MIB II [16] for attribute semantics
REGISTERED AS {system 4};
sysDescr ATTRIBUTE
WITH ATTRIBUTE SYNTAX
OIM-Module.PrintString;
MATCHES FOR Equality;
-- SEE MIB II [16] for attribute semantics
REGISTERED AS {system 1};
sysLocation ATTRIBUTE
WITH ATTRIBUTE SYNTAX
OIM-Module.PrintString;
MATCHES FOR Equality;
-- SEE MIB II [16] for attribute semantics
REGISTERED AS {system 6};
sysName ATTRIBUTE
WITH ATTRIBUTE SYNTAX
OIM-Module.PrintString;
MATCHES FOR Equality;
-- SEE MIB II [16] for attribute semantics
-- The nodes domain name.
REGISTERED AS {system 5};
sysObjectId ATTRIBUTE
WITH ATTRIBUTE SYNTAX OIM-Module.ObjectId;
MATCHES FOR Equality;
-- SEE MIB II [16] for attribute semantics
REGISTERED AS {system 2};
sysServices ATTRIBUTE
WITH ATTRIBUTE SYNTAX OIM-Module.Integer128;
MATCHES FOR Equality;
-- SEE MIB II [16] for attribute semantics
REGISTERED AS {system 7};
sysUpTime ATTRIBUTE
WITH ATTRIBUTE SYNTAX RFC1065-SMI.TimeTicks;
MATCHES FOR Equality, Ordering;
-- SEE MIB II [16] for attribute semantics
REGISTERED AS {system 3};
tcpActiveOpens ATTRIBUTE
WITH ATTRIBUTE SYNTAX RFC1065-SMI.Counter;
MATCHES FOR Equality, Ordering;
-- SEE MIB II [16] for attribute semantics
REGISTERED AS {tcp 5};
tcpAttemptFails ATTRIBUTE
WITH ATTRIBUTE SYNTAX
RFC1065-SMI.Counter;
MATCHES FOR Equality, Ordering;
-- SEE MIB II [16] for attribute semantics
REGISTERED AS {tcp 7};
tcpConnId ATTRIBUTE
WITH ATTRIBUTE SYNTAX
OIM-Module.PrintString;
MATCHES FOR Equality;
-- identifies an instance of tcpConnEntry
-- <laddr> "." <lport> "." <raddr> "." <rport>, where
-- <laddr> is the "dot notation" representation of
-- tcpConnLocalAddress,
-- <lport> is the decimal representation of
-- tcpConnLocalPort,
-- <raddr> is the "dot notation" representation of
-- tcpConnRemAddress, and
--<rport> is the decimal representation of
-- tcpConnRemPort.
REGISTERED AS {attributes 12};
tcpConnLocalAddress ATTRIBUTE
WITH ATTRIBUTE SYNTAX RFC1065-SMI.IpAddress;
MATCHES FOR Equality;
-- SEE MIB II [16] for attribute semantics
REGISTERED AS {tcpConnEntry 2};
tcpConnLocalPort ATTRIBUTE
WITH ATTRIBUTE SYNTAX OIM-Module.Integer64k;
MATCHES FOR Equality, Ordering;
-- SEE MIB II [16] for attribute semantics
REGISTERED AS {tcpConnEntry 3};
tcpConnRemAddress ATTRIBUTE
WITH ATTRIBUTE SYNTAX RFC1065-SMI.IpAddress;
MATCHES FOR Equality;
-- SEE MIB II [16] for attribute semantics
REGISTERED AS {tcpConnEntry 4};
tcpConnRemPort ATTRIBUTE
WITH ATTRIBUTE SYNTAX OIM-Module.Integer64k;
MATCHES FOR Equality, Ordering;
-- SEE MIB II [16] for attribute semantics
REGISTERED AS {tcpConnEntry 5};
tcpConnState ATTRIBUTE
WITH ATTRIBUTE SYNTAX OIM-Module.TcpConnState;
MATCHES FOR Equality;
-- SEE MIB II [16] for attribute semantics
REGISTERED AS {tcpConnEntry 1};
tcpConnTableId ATTRIBUTE
WITH ATTRIBUTE SYNTAX
OIM-Module.PrintString;
MATCHES FOR Equality;
-- This attribute defines a unique index of
-- tcpConnEntry in the TCP Connection Table
-- An empty string is used for a single instance.
REGISTERED AS {attributes 11};
tcpCurrEstab ATTRIBUTE
WITH ATTRIBUTE SYNTAX RFC1065-SMI.Gauge;
MATCHES FOR Equality, Ordering;
-- SEE MIB II [16] for attribute semantics
REGISTERED AS {tcp 9};
tcpEstabResets ATTRIBUTE
WITH ATTRIBUTE SYNTAX RFC1065-SMI.Counter;
MATCHES FOR Equality, Ordering;
-- SEE MIB II [16] for attribute semantics
REGISTERED AS {tcp 8};
tcpId ATTRIBUTE
WITH ATTRIBUTE SYNTAX
OIM-Module.PrintString;
MATCHES FOR Equality;
-- This attribute uniquely identified a tcp
-- object instance
-- An empty string is used for a single instance.
REGISTERED AS {attributes 10};
tcpInErrs ATTRIBUTE
WITH ATTRIBUTE SYNTAX
RFC1065-SMI.Counter;
MATCHES FOR Equality, Ordering;
-- SEE MIB II [16] for attribute semantics
REGISTERED AS {tcp 14};
tcpInSegs ATTRIBUTE
WITH ATTRIBUTE SYNTAX RFC1065-SMI.Counter;
MATCHES FOR Equality, Ordering;
-- SEE MIB II [16] for attribute semantics
REGISTERED AS {tcp 10};
tcpMaxConn ATTRIBUTE
WITH ATTRIBUTE SYNTAX OIM-Module.Integer;
MATCHES FOR Equality, Ordering;
-- SEE MIB II [16] for attribute semantics
REGISTERED AS {tcp 4};
tcpOutRsts ATTRIBUTE
WITH ATTRIBUTE SYNTAX
RFC1065-SMI.Counter;
MATCHES FOR Equality, Ordering;
-- SEE MIB II [16] for attribute semantics
REGISTERED AS {tcp 15};
tcpOutSegs ATTRIBUTE
WITH ATTRIBUTE SYNTAX RFC1065-SMI.Counter;
MATCHES FOR Equality, Ordering;
-- SEE MIB II [16] for attribute semantics
REGISTERED AS {tcp 11};
tcpPassiveOpens ATTRIBUTE
WITH ATTRIBUTE SYNTAX
RFC1065-SMI.Counter;
MATCHES FOR Equality, Ordering;
-- SEE MIB II [16] for attribute semantics
REGISTERED AS {tcp 6};
tcpRetransSegs ATTRIBUTE
WITH ATTRIBUTE SYNTAX RFC1065-SMI.Counter;
MATCHES FOR Equality, Ordering;
-- SEE MIB II [16] for attribute semantics
REGISTERED AS {tcp 12};
tcpRtoAlgorithm ATTRIBUTE
WITH ATTRIBUTE SYNTAX
OIM-Module.TcpRtoAlgorithm;
MATCHES FOR Equality;
-- SEE MIB II [16] for attribute semantics
REGISTERED AS {tcp 1};
tcpRtoMax ATTRIBUTE
WITH ATTRIBUTE SYNTAX OIM-Module.Integer;
MATCHES FOR Equality;
-- SEE MIB II [16] for attribute semantics
REGISTERED AS {tcp 3};
tcpRtoMin ATTRIBUTE
WITH ATTRIBUTE SYNTAX OIM-Module.Integer;
MATCHES FOR Equality;
-- SEE MIB II [16] for attribute semantics
REGISTERED AS {tcp 2};
udpEntryId ATTRIBUTE
WITH ATTRIBUTE SYNTAX
OIM-Module.PrintString;
MATCHES FOR Equality;
-- This attribute defines an entry
-- for the UDP Listener Table
-- <port> "." <address>, where <port> is the decimal
-- representation of udpLocalPort and <address> is
-- udpLocalAddress represented in "dot notation".
REGISTERED AS {attributes 15};
udpId ATTRIBUTE
WITH ATTRIBUTE SYNTAX
OIM-Module.PrintString;
MATCHES FOR Equality;
-- This attribute provides a unique id to
-- identify the UDP entity.
-- An empty string is used for a single instance.
REGISTERED AS {attributes 13};
udpInDatagrams ATTRIBUTE
WITH ATTRIBUTE SYNTAX RFC1065-SMI.Counter;
MATCHES FOR Equality, Ordering;
-- SEE MIB II [16] for attribute semantics
REGISTERED AS {udp 1};
udpInErrors ATTRIBUTE
WITH ATTRIBUTE SYNTAX RFC1065-SMI.Counter;
MATCHES FOR Equality, Ordering;
-- SEE MIB II [16] for attribute semantics
REGISTERED AS {udp 3};
udpLocalAddress ATTRIBUTE
WITH ATTRIBUTE SYNTAX
RFC1065-SMI.IpAddress;
MATCHES FOR Equality;
-- SEE MIB II [16] for attribute semantics
REGISTERED AS {udpEntry 1};
udpLocalPort ATTRIBUTE
WITH ATTRIBUTE SYNTAX
OIM-Module.Integer64k;
MATCHES FOR Equality, Ordering;
-- SEE MIB II [16] for attribute semantics
REGISTERED AS {udpEntry 2};
udpNoPorts ATTRIBUTE
WITH ATTRIBUTE SYNTAX RFC1065-SMI.Counter;
MATCHES FOR Equality, Ordering;
-- SEE MIB II [16] for attribute semantics
REGISTERED AS {udp 2};
udpOutDatagrams ATTRIBUTE
WITH ATTRIBUTE SYNTAX
RFC1065-SMI.Counter;
MATCHES FOR Equality, Ordering;
-- SEE MIB II [16] for attribute semantics
REGISTERED AS {udp 4};
udpTableId ATTRIBUTE
WITH ATTRIBUTE SYNTAX
OIM-Module.PrintString;
MATCHES FOR Equality;
-- This attribute defines a unique id
-- for the UDP Listener Table
-- An empty string is used for a single instance.
REGISTERED AS {attributes 14};
6. Notifications
Notification templates for the notifications referenced in the
managed object class templates of section 5 are listed here in
alphabetical order.
coldStartEvent NOTIFICATION
-- clause 4.1.6.1 of RFC1157
-- emitted by system
MODE NON-CONFIRMED;
WITH INFORMATION SYNTAX OIM-Module.SnmpTrapInfo
REGISTERED AS {events 0};
egpNeighborLossEvent NOTIFICATION
-- clause 4.1.6.6 of RFC1157
-- with generic-trap = 5
-- The first VarBindList element
-- contains the name and value of the
-- egpNeighAddr of the affected
-- neighbor.
-- emitted by egpNeighEntry
MODE NON-CONFIRMED;
WITH INFORMATION SYNTAX OIM-Module.SnmpTrapInfo;
REGISTERED AS {events 5};
linkDownEvent NOTIFICATION
-- clause 4.1.6.3 of RFC1157
-- emitted by ifEntry
-- with generic-trap = 2
MODE NON-CONFIRMED;
WITH INFORMATION SYNTAX OIM-Module.SnmpTrapInfo;
REGISTERED AS {events 2};
linkUpEvent NOTIFICATION
-- clause 4.1.6.4 of RFC1157
-- emitted by ifEntry
-- with generic-trap = 3
MODE NON-CONFIRMED;
WITH INFORMATION SYNTAX OIM-Module.SnmpTrapInfo;
REGISTERED AS {events 3};
snmpAuthentFailureEvent NOTIFICATION
-- clause 4.1.6.5 of RFC1157
-- emitted by snmp
MODE NON-CONFIRMED;
WITH INFORMATION SYNTAX OIM-Module.SnmpTrapInfo;
REGISTERED AS {events 4};
entSpecificEvent NOTIFICATION
-- clause 4.1.6.7 of RFC1157
-- emitted by system
MODE NON-CONFIRMED;
WITH INFORMATION SYNTAX OIM-Module.SnmpTrapInfo;
REGISTERED AS {events 6};
warmStartEvent NOTIFICATION
-- clause 4.1.6.2 of RFC1157
-- emitted by system
MODE NON-CONFIRMED;
WITH INFORMATION SYNTAX OIM-Module.SnmpTrapInfo;
REGISTERED AS {events 1};
7. The Containment Hierarchy
Name Binding templates that define the containment hierarchy for the
OIM MIB-II are listed here in alphabetical order. The containment
hierarchy within a managed system begins at the "system" managed
object.
atEntry-nf NAME BINDING
SUBORDINATE OBJECT CLASS atEntry;
NAMED BY SUPERIOR OBJECT CLASS atTable;
WITH ATTRIBUTE atEntryId;
CREATE;
DELETE only-if-no-contained-objects;
REGISTERED AS { nameForms 5};
atTable-nf NAME BINDING
SUBORDINATE OBJECT CLASS atTable;
NAMED BY SUPERIOR OBJECT CLASS system;
WITH ATTRIBUTE atTableId;
REGISTERED AS { nameForms 4};
egp-nf NAME BINDING
SUBORDINATE OBJECT CLASS egp;
NAMED BY SUPERIOR OBJECT CLASS system;
WITH ATTRIBUTE egpId;
REGISTERED AS { nameForms 20};
egpNeighEntry-nf NAME BINDING
SUBORDINATE OBJECT CLASS egpNeighEntry;
NAMED BY SUPERIOR OBJECT CLASS egpNeighTable;
WITH ATTRIBUTE egpNeighEntryId;
CREATE;
DELETE only-if-no-contained-objects;
REGISTERED AS { nameForms 22};
egpNeighTable-nf NAME BINDING
SUBORDINATE OBJECT CLASS egpNeighTable;
NAMED BY SUPERIOR OBJECT CLASS egp;
WITH ATTRIBUTE egpNeighTableId;
REGISTERED AS { nameForms 21};
icmp-nf NAME BINDING
SUBORDINATE OBJECT CLASS icmp;
NAMED BY SUPERIOR OBJECT CLASS system;
WITH ATTRIBUTE icmpId;
REGISTERED AS { nameForms 13};
interfaces-nf NAME BINDING
SUBORDINATE OBJECT CLASS interfaces;
NAMED BY SUPERIOR OBJECT CLASS system;
WITH ATTRIBUTE ifId;
REGISTERED AS { nameForms 24};
ifEntry-nf NAME BINDING
SUBORDINATE OBJECT CLASS ifEntry;
NAMED BY SUPERIOR OBJECT CLASS ifTable;
WITH ATTRIBUTE ifEntryId;
CREATE;
DELETE only-if-no-contained-objects;
REGISTERED AS { nameForms 3};
ifTable-nf NAME BINDING
SUBORDINATE OBJECT CLASS ifTable;
NAMED BY SUPERIOR OBJECT CLASS interfaces;
WITH ATTRIBUTE ifTableId;
REGISTERED AS { nameForms 2};
ip-nf NAME BINDING
SUBORDINATE OBJECT CLASS ip;
NAMED BY SUPERIOR OBJECT CLASS system;
WITH ATTRIBUTE ipId;
REGISTERED AS { nameForms 6};
ipAddrEntry-nf NAME BINDING
SUBORDINATE OBJECT CLASS ipAddrEntry;
NAMED BY SUPERIOR OBJECT CLASS ipAddrTable;
WITH ATTRIBUTE ipAdEntryId;
CREATE;
DELETE only-if-no-contained-objects;
REGISTERED AS { nameForms 8};
ipAddrTable-nf NAME BINDING
SUBORDINATE OBJECT CLASS ipAddrTable;
NAMED BY SUPERIOR OBJECT CLASS ip;
WITH ATTRIBUTE ipAddrTableId;
REGISTERED AS { nameForms 7};
ipNetToMediaEntry-nf NAME BINDING
SUBORDINATE OBJECT CLASS ipNetToMediaEntry;
NAMED BY SUPERIOR OBJECT CLASS ipNetToMediaTable;
WITH ATTRIBUTE ipNetToMediaEntryId;
CREATE;
DELETE only-if-no-contained-objects;
REGISTERED AS { nameForms 12};
ipNetToMediaTable-nf NAME BINDING
SUBORDINATE OBJECT CLASS ipNetToMediaTable;
NAMED BY SUPERIOR OBJECT CLASS ip;
WITH ATTRIBUTE ipNetToMediaTableId;
REGISTERED AS { nameForms 11};
ipRouteEntry-nf NAME BINDING
SUBORDINATE OBJECT CLASS ipRouteEntry;
NAMED BY SUPERIOR OBJECT CLASS ipRoutingTable;
WITH ATTRIBUTE ipRouteEntryId;
CREATE;
DELETE only-if-no-contained-objects;
REGISTERED AS { nameForms 10};
ipRoutingTable-nf NAME BINDING
SUBORDINATE OBJECT CLASS ipRoutingTable;
NAMED BY SUPERIOR OBJECT CLASS ip;
WITH ATTRIBUTE ipRoutingTableId;
REGISTERED AS { nameForms 9};
snmp-nf NAME BINDING
SUBORDINATE OBJECT CLASS snmp;
NAMED BY SUPERIOR OBJECT CLASS system;
WITH ATTRIBUTE snmpId;
REGISTERED AS { nameForms 23};
system-nf NAME BINDING
SUBORDINATE OBJECT CLASS system;
NAMED BY SUPERIOR OBJECT CLASS root;
WITH ATTRIBUTE sysName;
REGISTERED AS { nameForms 1 };
tcp-nf NAME BINDING
SUBORDINATE OBJECT CLASS tcp;
NAMED BY SUPERIOR OBJECT CLASS system;
WITH ATTRIBUTE tcpid;
REGISTERED AS { nameForms 14};
tcpConnEntry-nf NAME BINDING
SUBORDINATE OBJECT CLASS tcpConnEntry;
NAMED BY SUPERIOR OBJECT CLASS tcpConnTable;
WITH ATTRIBUTE tcpConnId;
REGISTERED AS { nameForms 16};
tcpConnTable-nf NAME BINDING
SUBORDINATE OBJECT CLASS tcpConnTable;
NAMED BY SUPERIOR OBJECT CLASS tcp;
WITH ATTRIBUTE tcpConnTableId;
REGISTERED AS { nameForms 15};
udp-nf NAME BINDING
SUBORDINATE OBJECT CLASS udp;
NAMED BY SUPERIOR OBJECT CLASS system;
WITH ATTRIBUTE udpId;
REGISTERED AS { nameForms 17};
udpEntry-nf NAME BINDING
SUBORDINATE OBJECT CLASS udpEntry;
NAMED BY SUPERIOR OBJECT CLASS udpTable;
WITH ATTRIBUTE udpEntryId;
REGISTERED AS { nameForms 19};
udpTable-nf NAME BINDING
SUBORDINATE OBJECT CLASS udpTable;
NAMED BY SUPERIOR OBJECT CLASS udp;
WITH ATTRIBUTE udpTableId;
REGISTERED AS { nameForms 18};
8. ASN.1 Definitions
The ASN.1 syntax referenced by the attribute templates in section 6
are either defined in RFC1065-SMI, the Attribute-ASN1Module of
ISO/IEC DIS 10165-2, or in the OIM-Module defined in this section.
This module includes some syntax definitions taken from the RFC1158
since they were not included in that document inside an ASN.1 module
and hence could not be externally referenced.
OIM-Module {iso org(3) dod(6) internet(1) mgmt(2) mib(1)
oim(9) misc(4) 1}
DEFINITIONS ::=
BEGIN
-- EXPORTS Everything
IMPORTS ObjectClass, ObjectInstance
FROM CMIP-1{joint-iso-ccitt ms(9) cmip(1)
modules(0) protocol(3)}
ObjectName, ObjectSyntax
FROM RFC1065-SMI;
mib OBJECT IDENTIFIER ::= {iso org(3) dod(6)
internet(1) mgmt(2) 1}
at OBJECT IDENTIFIER ::= {mib 3}
oim OBJECT IDENTIFIER ::= {mib 9}
cmotVersion OBJECT IDENTIFIER ::= {oim 1}
cmotACSEInfo OBJECT IDENTIFIER ::= {oim 2}
cmotSystemId OBJECT IDENTIFIER ::= {oim 3}
misc OBJECT IDENTIFIER ::= {oim 4}
objects OBJECT IDENTIFIER ::= {oim 5}
attributes OBJECT IDENTIFIER ::= {oim 6}
events OBJECT IDENTIFIER ::= {oim 7}
nameforms OBJECT IDENTIFIER ::= {oim 8}
actions OBJECT IDENTIFIER ::= {oim 9}
-- Generic and MIB specific syntax
EgpNeighEventTrigger ::= INTEGER {
start(1),
stop(2)
}
EgpNeighMode ::= INTEGER {
active(1),
passive(2)
}
EgpNeighState ::= INTEGER {
idle(1),
acquisition(2),
down(3),
up(4),
cease(5)
}
Integer ::= INTEGER
Integer128 ::= INTEGER (0..127)
Integer64k ::= INTEGER (0..65535)
IfAdminStatus ::= INTEGER {
up(1), -- ready to pass packets
down(2),
testing(3) -- in some test mode
}
IfOperStatus ::= INTEGER {
up(1), -- ready to pass packets
down(2),
testing(3) -- in some test mode
}
IfType INTEGER {
other(1), -- none of the following
regular1822(2),
hdh1822(3),
ddn-x25(4),
rfc877-x25(5),
ethernet-csmacd(6),
iso88023-csmacd(7),
iso88024-tokenBus(8),
iso88025-tokenRing(9),
iso88026-man(10),
starLan(11),
proteon-10Mbit(12),
proteon-80Mbit(13),
hyperchannel(14),
fddi(15),
lapb(16),
sdlc(17),
ds1(18),
e1(19), -- european equivalent
-- of T-1
basicISDN(20),
primaryISDN(21),
-- proprietary serial
propPointToPointSerial(22),
ppp(23),
softwareLoopback(24),
eon(25), -- CLNP over IP
ethernet-3Mbit(26),
nsip(27), -- XNS over IP
slip(28), -- generic SLIP
ultra(29), -- ULTRA technologies
ds3(30), -- T-3
sip(31), -- SMDS
frame-relay(32)
}
IpForwarding ::= INTEGER {
forwarding(1), -- acting as a gateway
not-forwarding(2) -- NOT acting as
-- a gateway
}
IpNetToMediaType ::= INTEGER {
other(1), -- none of the
-- following
invalid(2), -- an invalidated
-- mapping
dynamic(3),
static(4) }
IpRouteProto ::= INTEGER {
other(1), -- none of the
-- following
local(2), -- configured entries
netmgmt(3), -- mgmt protocol
icmp(4), -- obtained via ICMP,
-- e.g., redirect
egp(5),
ggp(6),
hello(7),
rip(8),
is-is(9),
es-is(10),
ciscoIgrp(11),
bbnSpfIgp(12),
ospf(13),
bgp(14)
}
IpRouteType ::= INTEGER {
other(1), -- none of the
-- following
invalid(2), -- an invalidated
-- route
direct(3), -- route to directly
-- connected
-- subnetwork
indirect(4) -- route to a
-- non-local
-- host/network/
-- subnet
}
ObjectId ::= OBJECT IDENTIFIER
OctetString ::= OCTET STRING
PhysAddress ::= OCTET STRING
PrintString ::= DisplayString (SIZE (0..255))
DisplayString ::= OCTET STRING
--
-- DisplayString is restricted to the NVT ASCII character set as
-- defined in pages 10-11 of RFC854 "TELNET Protocol
-- Specification", May 1983 [15].
--
-- SNMP trap syntax
SnmpEnableAuthenTraps ::= INTEGER {
enabled(1),
disabled(2)
}
SnmpTrapInfo ::= SEQUENCE {
enterprise -- type of device generating
-- event
-- see sysObjectId
OBJECT IDENTIFIER,
agent-addr -- address of device generating
-- the event
NetworkAddress,
generic-trap INTEGER {coldStart (0),
warmStart (1),
linkDown (2),
linkUp (3),
authenticationFailure (4),
egpNeighborLoss (5),
enterpriseSpecific (6) },
specific-trap INTEGER OPTIONAL, -- enterprise specific
variable-bindings VarBindList OPTIONAL}
VarBindList ::= SEQUENCE OF VarBind
VarBind ::= SEQUENCE {
name ObjectName,
ovalue ObjectSyntax}
TcpConnState ::= INTEGER {
closed(1),
listen(2),
synSent(3),
synReceived(4),
established(5),
finWait1(6),
finWait2(7),
closeWait(8),
lastAck(9),
closing(10),
timeWait(11),
deleteTCP(12) }
TcpRtoAlgorithm ::= INTEGER {
other(1), -- none of the
-- following
constant(2), -- a constant rto
rsre(3), -- MIL-STD-1778,
-- Appendix B
vanj(4) -- Van Jacobsons alg.
}
END
9. Acknowledgements
The editor acknowledges the contributions of the members of the OIM
working group. Particular thanks are made to the following for their
comments and assistance:
Marvin Solomon, University of Wisconsin
Nancy Hall, University of Wisconsin
Subhendu Ghatak, University of Tennessee at Knoxville
References
1. ISO 8824: Information Processing - Open System Interconnection -
Specification of Abstract Syntax Notation One (ASN.1), February
1989.
2. ISO/IEC 7498-4, Information Processing Systems- Open Systems
Interconnection - Basic Reference Model Part 4 - OSI Management
Framework.
3. Warrier, U., Besaw, L., and LaBarre, L., and B. Handspicker, "The
Common Management Information Services and Protocol for the
Internet (CMOT and CMIP)", RFC1189, Netlabs, Hewlett-Packard,
The Mitre Corporation, Digital Equipment Corporation, October
1990.
4. ISO/IEC DIS 10165-1, Information Processing Systems - Open
Systems Interconnection-Structure of Management Information -
Part 1: Management Information Model, July 1990.
5. ISO/IEC DIS 10165-2 (ISO/IEC JTC1/SC21 N4072), Information
Processing Systems -Open Systems Interconnection - Structure of
Management Information - Part 2: Definition of Management
Information, July 1990.
6. ISO/IEC DIS 10165-4 (ISO/IEC JTC1/SC21 N4065), Information
Processing Systems - Open Systems Interconnection - Structure of
Management Information - Part 4: Guidelines for the Definition of
Managed Objects, June 1990.
7. ISO 9595, Information Processing Systems - Open Systems
Interconnection - Management Information Service Definition -
Common Management Information Service, November 1990.
8. ISO 9596, Information Processing Systems - Open Systems
Interconnection - Management Information Protocol Specification -
Common Management Information Protocol, November 1990.
9. ISO 8649, Information Processing Systems - Open Systems
Interconnection, Service Definition for the Association Control
Service Element.
10. ISO 9072-1, Information Processing Systems - Text Communication,
Remote Operations: Model, Notation and Service Definition,
Gloucester, Nov 1987.
11. Rose, M., and K. McCloghrie, "Structure and Identification of
Management Information for TCP/IP-based internets", RFC1155,
Performance Systems International, Hughes LAN Systems, May 1990.
12. Rose, M., Editor, "Management Information Base for Network
Management of TCP/IP-based internets: MIB-II", RFC1158,
Performance Systems International, May 1990.
13. Cerf, V., "Report of the Second Ad Hoc Network Management Review
Group", RFC1109, NRI, August 1989.
14. Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple
Network Management Protocol (SNMP)", RFC1157, SNMP Research,
Performance Systems International, Performance Systems
International, MIT Laboratory for Computer Science, May 1990.
15. Postel, J., and J. Reynolds, "Telnet Protocol Specification", RFC
854, USC/Information Sciences Institute, May 1983.
16. McCloghrie, K., and M. Rose, "Management Information Base for
Network Management of TCP/IP-based internets: MIB-II", RFC1213,
Hughes LAN Systems, Performance Systems International, March
1991.
17. Working Implementation Agreements for Open Systems
Interconnection Protocols, December 1990.
Appendix 1: Notational Tools for Managed Object Definition
This section provides descriptions of the notational tools used to
define the templates defined in this memorandum. The text is
excerpted and paraphrased from reference 6. Only the templates used
in this document are included here. For a complete description of
the notational tools specified for OSI management, see reference 6.
A1.1 Overview of Notational Tools
The "Templates" defined in this clause provide a common set of tools
and a common format for the representation of the various aspects of
a managed object class definition and its associated naming
structure. Formal definitions of each template will be found in
clauses A1.3 -A1.11 inclusive; the syntactic conventions used in
these formal definitions are specified in clause A1.2. Examples of
the use of these tools may be found in Annex A (of 10165-4).
The structure and behaviour of a managed object class is primarily
defined by means of the Managed Object Class Template. This template
identifies the inheritance relationships that exist between the class
and other managed object classes, the packages of class specific
behaviour, the attributes that are associated with the class, the
notifications that the class may issue and the operations that may be
performed upon the class. In order to allow re-use of parts of this
specification in the specification of other managed object classes,
additional templates are defined to provide for the specification of
attributes (individual and group), behaviour, actions, notifications
and conditional packages. These other templates are "called up" by
the Managed Object Class template by means of the referencing
mechanism defined in clause A1.2; this mechanism allows references to
be made in one standard to specifications that are contained in other
standards, hence allowing "generic" specifications to be made
available for use in managed object class definitions in addition to
local specifications. Templates may also be included "in-line" if so
desired.
The naming of a managed object class is defined by means of the Name
Binding template. This template identifies the managed object class
being named and defines the relative distinguished name that will be
used to name instances of the class in the context of a particular
superior class. This template also provides for the specification of
relationships that exist between two object classes as a consequence
of a particular name binding.
A1.2 Conventions Used in Template Definitions
The templates definitions contained in this clause are based on the
following syntactic conventions:
- Strings surrounded by [ ] delimit parts of the template that may
either be present or absent in each instance of use of the
template. If the closing brace is followed by an asterisk,
e.g., [ ]*, the contents of the braces may appear zero or more
times. The circumstances under which these parts of the
definition may be omitted or repeated are dependent upon the
template type;
- Strings surrounded by < > delimit strings that must be replaced in
each instance of use of the template. The structure and meaning
of the replacement string is dependent upon the string type;
- Upper case strings denote Keywords which are required to be
present in each instance of use of the template, unless they are
enclosed in [ ];
- The solidus, |, is used to separate alternative strings in the
template;
- Spaces and carriage returns are significant only as string
delimiters;
- In order to simplify the structure of the templates, particularly
where the same syntactic structure is repeated in the template
definitions, supporting syntactic definitions may be defined. If
any such supporting syntactic definitions are required in order to
complete the template definition, these appear following the
keywords "supporting productions" at the end of the template
definition. These supporting definitions take the general form
definition-label-> syntactic-definition
where definition-label allows the definition to be referenced by the
template definition and syntactic-definition gives the expansion of
the definition, using the above notational rules;
- The templates themselves have the general structure:
<template-label>TEMPLATE NAME
[ELEMENT NAME [<element-definition>] ;]*
[REGISTERED AS <object-identifier> ;]
[supporting productions
[<definition-label> -> <syntactic-definition >]*]
Each instance of use of a template therefore declares a template-
label by which that instance may be referenced from other templates,
and if the REGISTERED AS clause is present, assigns a value of an
ASN.1 OBJECT IDENTIFIER under which the instance has been registered;
- Semicolons are used to mark the end of each distinct element in
the template. In an instance of use of the template, any text
inserted between a semicolon and the next valid keyword is
assumed to be a comment;
- The notation used for representing object identifiers is the
normal notation defined in ASN.1 for object identifier values;
i.e., the production:
object-identifier-> <ASN.l ObjectIdentifierValue notation>
is assumed to be a supporting production for all template
definitions in this document;
- Further definitions, such as the nature of the element definitions,
follow the syntactic definition of the template;
- Template labels shall be unique within the standard or document
in which they are declared. Where a template-label is declared in
document A and referenced in document B, the reference in
document B shall be prefixed by the globally unique name of
document A. In the case of documents named by an
internationally recognized naming authority such as
[CCITT|ISO/IEC], the registered name of the document shall be
used as the identifier, such as [Recommendation X.722|ISO/IEC
10165-4]. Where a globally unique name is not already available,
it is permissible to assign the value of an OBJECT IDENTIFIER to
the referenced document, and use this value as a globally unique
document name. The syntax of a template-label, defined using the
above notation, is defined as follows:
[<document-identifier> :] < label-string>
document-identifier-> "<standard-name>" | <object-identifier>
A label-string may include any number of the following characters:
- upper or lower case alphabetic characters;
- the digits 0-9;
- the hyphen character (-);
in any order, commencing with a lower case character. For example,
the following template-label:
"ISO/IEC 10165/4":exampleObjectClass
constitutes a globally unique label for the definition of
exampleObjectClass contained in Annex A of 10165-4.
Label references that are not prefixed by a document-identifier are
assumed to refer to labels declared in the document in which the
reference appears.
- Whenever a template-label is present in a template as a
pointer to another template, it may be replaced by the entire
text of the referenced template itself (including the
template's label).
A1.3 Managed Object Class Template
A1.3.1 Overview
The Managed Object Class template forms the basis of the formal
definition of a managed object. Elements in the template allow the
class to be placed at the appropriate node of the inheritance tree,
the various attributes of the class to be specified, and the
behaviour of the class to be defined. The major elements of the
definition are:
- Inheritance. Each managed object class defines the
superclass(es) from which it has been derived. All
characteristics of the superclass(es) are inherited by the
subclass; the subclass definition may add to these
characteristics (refinement) but may not remove any
characteristics of the superclass. Ultimately, all classes are
subclasses of TOP;
- Allomorphs. If the class supports allomorphism, the set of
classes that are legitimate allomorphic views of the class must
be defined. These classes must all be superclasses of the class
being defined;
- Mandatory Packages. The managed object class definition
includes the packages of behaviour, attributes, operations and
notifications that provide a complete specification of the
behaviour that is common to all instances of the class;
- Conditional Packages. The managed object class definition
includes the specification of packages of behaviour, attributes,
operations and notifications that are present or absent in
instances of that class as a consequence of a specified condition;
Note: Attributes, Operations and Notifications that form part of a
class definition may only be omitted from an instance of that class
if they are defined as features of a Conditional Package and are
omitted in accordance with the condition defined for that package.
- Class Naming. The managed object class definition must include a
class name which may be used to refer to the class in CMIP. This
is achieved by registration of an Object Identifier value which
corresponds to the class.
A1.3.2 Template Structure
<class-label> MANAGED OBJECT CLASS