-- units of conformance
dot12ConfigGroup OBJECT-GROUP
OBJECTS { dot12DesiredFramingType,
dot12FramingCapability,
dot12DesiredPromiscStatus,
dot12TrainingVersion,
dot12LastTrainingConfig,
dot12Commands, dot12Status,
dot12CurrentFramingType,
dot12ControlMode }
STATUS current
DESCRIPTION
"A collection of objects for managing the status
and configuration of IEEE 802.12 interfaces."
::= { dot12Groups 1 }
dot12StatsGroup OBJECT-GROUP
OBJECTS { dot12InHighPriorityFrames,
dot12InHighPriorityOctets,
dot12InNormPriorityFrames,
dot12InNormPriorityOctets,
dot12InIPMErrors,
dot12InOversizeFrameErrors,
dot12InDataErrors,
dot12InNullAddressedFrames,
dot12OutHighPriorityFrames,
dot12OutHighPriorityOctets,
dot12TransitionIntoTrainings,
dot12HCInHighPriorityOctets,
dot12HCInNormPriorityOctets,
dot12HCOutHighPriorityOctets }
STATUS current
DESCRIPTION
"A collection of objects providing statistics for
IEEE 802.12 interfaces."
::= { dot12Groups 2 }
END
5. Acknowledgements
This document was produced by the IETF 100VG-AnyLAN Working Group.
It is based on the work of IEEE 802.12.
6. References
[1] Information processing systems - Open Systems Interconnection -
Specification of Abstract Syntax Notation One (ASN.1),
International Organization for Standardization. International
Standard 8824 (December, 1987).
[2] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and
S. Waldbusser, "Structure of Management Information for Version
2 of the Simple Network Management Protocol (SNMPv2)", RFC1902,
SNMP Research, Inc., Cisco Systems, Inc., Dover Beach
Consulting, Inc., International Network Services, January 1996.
[3] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and
S. Waldbusser, "Textual Conventions for Version 2 of the Simple
Network Management Protocol (SNMPv2)", RFC1903, SNMP Research,
Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc.,
International Network Services, January 1996.
[4] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and
S. Waldbusser, "Conformance Statements for Version 2 of the
Simple Network Management Protocol (SNMPv2)", RFC1904, SNMP
Research, Inc., Cisco Systems, Inc., Dover Beach Consulting,
Inc., International Network Services, January 1996.
[5] McCloghrie, K., and M. Rose, "Management Information Base for
Network Management of TCP/IP-based internets - MIB-II", STD 17,
RFC1213, Hughes LAN Systems, Performance Systems International,
March 1991.
[6] IEEE, "Demand Priority Access Method, Physical Layer and
Repeater Specifications for 100 Mb/s Operation", IEEE Standard
802.12-1995"
[7] McCloghrie, K., and Kastenholz, F., "Evolution of the Interfaces
Group of MIB-II", RFC1573, Hughes LAN Systems, FTP Software,
January 1994.
[8] Kastenholz, F., "Definitions of Managed Objects for the
Ethernet-like Interface Types", STD 50, RFC1643, FTP Software,
Inc., July, 1994.
[9] Kastenholz, F., "Definitions of Managed Objects for the
Ethernet-like Interface Types using SMIv2", RFC1650, FTP
Software, Inc., August, 1994.
[10] McCloghrie, K., and Decker, E., "IEEE 802.5 MIB using SMIv2",
RFC1748, Cisco Systems, Inc., December, 1994.
[11] McCloghrie, K., Baker, F., and Decker, E., "IEEE 802.5 Station
Source Routing MIB using SMIv2", RFC1749, Cisco Systems, Inc.,
December, 1994.
7. Security Considerations
Security issues are not discussed in this memo.
8. Author's Address
John Flick
Hewlett Packard Company
8000 Foothills Blvd. M/S 5556
Roseville, CA 95747-5556
Phone: +1 916 785 4018
Email: johnf@hprnd.rose.hp.com