RFC relevance of reference

As per Relevance of the word reference, we have this rfc below:

Network Working Group J.
Request for Comments: 2266 Hewlett Packard
Category: Standards Track January 1998

Definitions of Managed Objects for IEEE 802.12 Repeater

Status of this

This document specifies an Internet standards track protocol for
Internet community, and requests discussion and suggestions
improvements. Please refer to the current edition of the "
Official Protocol Standards" (STD 1) for the standardization
and status of this protocol. Distribution of this memo is unlimited

Copyright

Copyright (C) The Internet Society (1998). All Rights Reserved

This memo defines a portion of the Management Information Base (MIB
for use with network management protocols in TCP/IP-based internets
In particular, it defines objects for managing network
based on IEEE 802.12.

Table of

1. The SNMP Network Management Framework ...................... 2
1.1. Object Definitions ....................................... 2
2. Overview ................................................... 2
2.1. Repeater Management Model ................................ 3
2.2. MAC Addresses ............................................ 4
2.3. Master Mode and Slave Mode ............................... 4
2.4. IEEE 802.12 Training Frames .............................. 4
2.5. Structure of the MIB ..................................... 6
2.5.1. Basic Definitions ...................................... 7
2.5.2. Monitor Definitions .................................... 7
2.5.3. Address Tracking Definitions ........................... 7
2.6. Relationship to other MIBs ............................... 7
2.6.1. Relationship to MIB-II ................................. 7
2.6.1.1. Relationship to the 'system' group ................... 7
2.6.1.2. Relationship to the 'interfaces' group ............... 8
2.6.2. Relationship to the 802.3 Repeater MIB ................. 8

Flick Standards Track [Page 1]

RFC 2266 IEEE 802.12 Repeater MIB January 1998

2.7. Mapping of IEEE 802.12 Managed Objects ................... 9
3. Definitions ................................................ 12
4. Acknowledgements ........................................... 53
5. References ................................................. 53
6. Security Considerations .................................... 54
7. Author's Address ........................................... 55
8. Full Copyright Statement ................................... 56

1. The SNMP Network Management

The SNMP Network Management Framework consists of several components
For the purpose of this specification, the applicable components
the Framework are the SMI and related documents [2, 3, 4],
define the mechanisms used for describing and naming objects for
purpose of management

The Framework permits new objects to be defined for the purpose
experimentation and evaluation

1.1. Object

Managed objects are accessed via a virtual information store,
the Management Information Base (MIB). Objects in the MIB
defined using the subset of Abstract Syntax Notation One (ASN.1) [1]
defined in the SMI [2]. In particular, each object type is named
an OBJECT IDENTIFIER, an administratively assigned name. The
type together with an object instance serves to uniquely identify
specific instantiation of the object. For human convenience,
often use a textual string, termed the descriptor, to refer to
object type

2.

Instances of these object types represent attributes of an
802.12 repeater, as defined by Section 12, "RMAC Protocol" in
Standard 802.12-1995 [6].

The definitions presented here are based on Section 13, "
management functions and services", and Annex C, "GDMO
for Demand Priority Managed Objects" of IEEE Standard 802.12-1995
[6].

Implementors of these MIB objects should note that the IEEE
explicitly describes (in the form of Pascal pseudocode) when, where
and how various repeater attributes are measured. The IEEE
also describes the effects of repeater actions that may be invoked
manipulating instances of the MIB objects defined here

Flick Standards Track [Page 2]

RFC 2266 IEEE 802.12 Repeater MIB January 1998

The counters in this document are defined to be the same as
counters in IEEE Standard 802.12-1995, with the intention that
same instrumentation can be used to implement both the IEEE and
management standards

2.1. Repeater Management

The model used in the design of this MIB allows for a managed
to contain one or more managed 802.12 repeaters, and one or
managed 802.12 repeater ports

A repeater port may be thought of as a source of traffic into
repeater in the system. The vgRptrBasicPortTable contains
for each physical repeater port in the managed system.
implementor may choose to separate these ports into "groups".
example, a group may be used to represent a field-replaceable unit
so that the port numbering may match the numbering in the
implementation. Note that this group mapping is recommended
optional. An implementor may choose to put all of the system's
into a single group, or to divide the ports into groups that do
match physical divisions. Each group within the system is
identified by a group number. Each port within a system is
identified by a combination of group number and port number.
method of numbering groups and ports is implementation-specific
Both groups and ports may be sparsely numbered

In addition to the externally visible ports, some implementations
have internal ports that are not obvious to the end-user but
nevertheless sources of traffic into the repeater system.
include internal management ports, through which an
communicates, and ports connecting to a backplane internal to
implementation. It is the decision of the implementor to select
appropriate group(s) in which to place internal ports

Managed repeaters in the system are represented by entries in
vgRptrInfoTable. There may be multiple repeaters in the
system. They are uniquely identified by a repeater number.
method of numbering repeaters is implementation-specific. Each
will either be associated with one of the repeaters, or isolated (
so-called "trivial" repeater). The set of ports associated with
single repeater will be in the same contention domain, and will
participating in the same instance of the Demand Priority
Method protocol. The mapping of ports to repeaters may be static
dynamic. A column in the vgRptrBasicPortTable
vgRptrPortRptrInfoIndex, indicates the repeater that the port
currently associated with. The method for assigning a port to
repeater is implementation-specific

Flick Standards Track [Page 3]

RFC 2266 IEEE 802.12 Repeater MIB January 1998

2.2. MAC

All representations of MAC addresses in this MIB module are
"canonical" order defined by 802.1a, i.e., as if it were
least significant bit first. This is true even if the repeater
operating in token ring framing mode, which requires MAC addresses
be transmitted most significant bit first

2.3. Master Mode and Slave

In an IEEE 802.12 network, "master" devices act as
controllers to decide when to grant requesting end-nodes
to transmit. These master devices may be repeaters, or other
controller devices such as switches

Devices which do not act as network controllers, such as end-nodes
passive switches, are considered to be operating in "slave" mode

An 802.12 repeater always acts in "master" mode on its local ports
which may connect to end nodes, switch or other device ports
in "slave" mode, or lower-level repeaters in a cascade. It acts
"slave" mode on cascade ports, which may connect to an upper-
repeater in a cascade, or to switch or other device ports
in "master" mode

2.4. IEEE 802.12 Training

Training frames are special MAC frames that are used only during
initialization. Training frames are initially constructed by
device at the "lower" end of a link, which is the slave mode
for the link. The training frame format is as follows

+----+----+------------+--------------+----------+-----+
| DA | SA | Req Config | Allow Config | Data | FCS |
+----+----+------------+--------------+----------+-----+

DA = destination address (six octets
SA = source address (six octets
Req Config = requested configuration (2 octets
Allow Config = allowed configuration (2 octets
Data = data (594 to 675 octets
FCS = frame check sequence (4 octets

Training frames are always sent with a null destination address.
pass training, an end node must use its source address in the
address field of the training frame. A repeater may use a non-
source address if it has one, or it may use a null source address

Flick Standards Track [Page 4]

RFC 2266 IEEE 802.12 Repeater MIB January 1998

The requested configuration field allows the slave mode device
inform the master mode device about itself and to
configuration options. The training response frame from the
mode device contains the slave mode device's requested
from the training request frame. The currently defined format of
requested configuration field as defined in the IEEE
802.12-1995 standard is shown below. Please refer to the
current version of the IEEE document for a more up to
description of this field. In particular, the reserved bits may
used in later versions of the standard

First Octet: Second Octet

7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
|v|v|v|r|r|r|r|r| |r|r|r|F|F|P|P|R
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+

vvv: The version of the 802.12 training protocol with
the training initiator is compliant. The current
is 100. Note that because of the different bit
used in IEEE and IETF documents, this value
to version 1.
r: Reserved bits (set to zero
FF: 00 = frameType88023
01 = frameType88025
10 =
11 =
PP: 00 =
01 =
10 =
11 =
R: 0 = the training initiator is an end
1 = the training initiator is a

The allowed configuration field allows the master mode device
respond with the allowed configuration. The slave mode device
the contents of this field to all zero bits. The master mode
sets the allowed configuration field as follows

First Octet: Second Octet

7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
|v|v|v|D|C|N|r|r| |r|r|r|F|F|P|P|R
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+

Flick Standards Track [Page 5]

RFC 2266 IEEE 802.12 Repeater MIB January 1998

vvv: The version of the 802.12 training protocol with
the training responder is compliant. The current
is 100. Note that because of the different bit
used in IEEE and IETF documents, this value
to version 1.
D: 0 = No duplicate address has been detected
1 = Duplicate address has been detected
C: 0 = The requested configuration is compatible with
network and the attached port
1 = The requested configuration is not compatible
the network and/or the attached port. In this case
the FF, PP, and R bits indicate a configuration
would be allowed
N: 0 = Access will be allowed, providing the
is compatible (C = 0).
1 = Access is not granted because of
restrictions
r: Reserved bits (set to zero).
FF: 00 = frameType88023 will be used
01 = frameType88025 will be used
10 =
11 =
PP: 00 =
01 =
10 =
11 =
R: 0 = Requested access as an end node is allowed
1 = Requested access as a repeater is allowed

Again, note that the most recent version of the IEEE 802.12
should be consulted for the most up to date definition of
requested configuration and allowed configuration fields

The data field contains between 594 and 675 octets and is filled
by the training initiator. The first 55 octets may be used
vendor specific protocol information. The remaining octets are
zeros. The length of the training frame combined with
requirement that 24 consecutive training frames be exchanged
error to complete training ensures that marginal links will
complete training

2.5. Structure of the

Objects in this MIB are arranged into OID subtrees, each of
contains a set of related objects within a broad functional category
These subtrees are intended for organizational convenience ONLY,
have no relation to the conformance groups defined later in
document

Flick Standards Track [Page 6]

RFC 2266 IEEE 802.12 Repeater MIB January 1998

2.5.1. Basic

The basic definitions include objects for managing the basic
and control parameters for each repeater within the managed system
for the port groups within the managed system, and for the
ports themselves

2.5.2. Monitor

The monitor definitions include monitoring statistics for
repeater within the system and for individual ports

2.5.3. Address Tracking

This collection includes objects for tracking the MAC addresses
the DTEs attached to the ports within the system

Note that this MIB also includes by reference a collection of
from the 802.3 Repeater MIB which may be used for mapping
topology of a network. These definitions are based on a
which has been patented by Hewlett-Packard Company (HP). HP
granted rights to this technology to implementors of this MIB.
[8] and [9] for details

2.6. Relationship to other

2.6.1. Relationship to MIB-

It is assumed that a repeater implementing this MIB will
implement (at least) the 'system' group defined in MIB-II [5].

2.6.1.1. Relationship to the 'system'

In MIB-II, the 'system' group is defined as being mandatory for
systems such that each managed entity contains one instance of
object in the 'system' group. Thus, those objects apply to
entity even if the entity's sole functionality is management
repeaters

Note that all of the managed repeaters (i.e. entries in
vgRptrInfoTable) will normally exist within a single naming scope
Therefore, there will normally only be a single instance of each
the objects in the system group for the entire managed
system regardless of how many managed repeaters there are in
system

Flick Standards Track [Page 7]

RFC 2266 IEEE 802.12 Repeater MIB January 1998

2.6.1.2. Relationship to the 'interfaces'

In MIB-II, the 'interfaces' group is defined as being mandatory
all systems and contains information on an entity's interfaces,
each interface is thought of as being attached to a 'subnetwork'.
(Note that this term is not to be confused with 'subnet' which
to an addressing partitioning scheme used in the Internet suite
protocols.)

This Repeater MIB uses the notion of ports on a repeater.
concept of a MIB-II interface has NO specific relationship to
repeater's port. Therefore, the 'interfaces' group applies only
the one (or more) network interfaces on which the entity managing
repeater sends and receives management protocol operations, and
not apply to the repeater's ports

This is consistent with the physical-layer nature of a repeater.
802.12 repeater has an RMAC implementation, which acts as
repeater end of the Demand Priority Access Method, but does
contain a DTE MAC implementation, and does not pass packets up
higher-level protocol entities for processing

(When a network management entity is observing a repeater, it
appear as though the repeater is passing packets to a higher-
protocol entity. However, this is only a means of
management, and this passing of management information is not part
the repeater functionality.)

2.6.2. Relationship to the 802.3 Repeater

An IEEE 802.12 repeater can be configured to operate in
ethernet or token ring framing mode. This only affects the
format and address bit order of the frames on the wire. An 802.12
network does not use the media access protocol for either ethernet
token ring. Instead, IEEE 802.12 defines its own media
protocol, the Demand Priority Access Method (DPAM).

There is an existing standards-track MIB module for
IEEE 802.3 repeaters [7]. That MIB module is designed to
the operation of the repeater in a network implementing the 802.3
media access protocol. Therefore, much of that MIB does not apply
802.12 repeaters

However, the 802.3 Repeater MIB also contains a collection of
that may be used to map the topology of a network. These objects
contained in a separable OBJECT-GROUP, are not 802.3-specific,
are considered useful for 802.12 repeaters. In addition, the

Flick Standards Track [Page 8]

RFC 2266 IEEE 802.12 Repeater MIB January 1998

management clause of the IEEE 802.12 specification includes
functionality. Therefore, vendors of agents for 802.12 repeaters
encouraged to implement the snmpRptrGrpRptrAddrSearch OBJECT-
defined in the 802.3 Repeater MIB

2.7. Mapping of IEEE 802.12 Managed

IEEE 802.12 Managed Object Corresponding SNMP

.aCurrentFramingType
.aDesiredFramingType
.aFramingCapability
.aMACAddress
.aRepeaterHealthState
.aRepeaterID
.aRepeaterSearchAddress SNMP-REPEATER-MIB -

.aRepeaterSearchGroup SNMP-REPEATER-MIB -

.aRepeaterSearchPort SNMP-REPEATER-MIB -

.aRepeaterSearchState SNMP-REPEATER-MIB -

.aRMACVersion
.acRepeaterSearchAddress SNMP-REPEATER-MIB -

.acResetRepeater
.nRepeaterHealth
.nRepeaterReset

.aGroupCablesBundled
.aGroupID
.aGroupPortCapacity

.aAllowableTrainingType
.aBroadcastFramesReceived
.aCentralMgmtDetectedDupAddr
.aDataErrorFramesReceived
.aHighPriorityFramesReceived
.aHighPriorityOctetsReceived vgRptrPortHCHighPriorityOctets,
vgRptrPortHighPriorityOctets

.aIPMFramesReceived
.aLastTrainedAddress
.aLastTrainingConfig

Flick Standards Track [Page 9]

RFC 2266 IEEE 802.12 Repeater MIB January 1998

.aLocalRptrDetectedDupAddr
.aMulticastFramesReceived
.aNormalPriorityFramesReceived
.aNormalPriorityOctetsReceived vgRptrPortHCNormPriorityOctets,
vgRptrPortNormPriorityOctets

.aNullAddressedFramesReceived
.aOctetsInUnreadableFramesRcvd vgRptrPortHCUnreadableOctets,
vgRptrPortUnreadableOctets

.aOversizeFramesReceived
.aPortAdministrativeState
.aPortID
.aPortStatus
.aPortType
.aPriorityEnable
.aPriorityPromotions
.aReadableFramesReceived
.aReadableOctetsReceived vgRptrPortHCReadableOctets,
vgRptrPortReadableOctets

.aSupportedCascadeMode
.aSupportedPromiscMode
.aTrainedAddressChanges
.aTrainingResult
.aTransitionsIntoTraining
.acPortAdministrativeControl

The following IEEE 802.12 managed objects have not been included
the 802.12 Repeater MIB for the indicated reasons

IEEE 802.12 Managed Object

.aGroupMap Can be determined by GetNext
of

.aRepeaterGroupCapacity Meaning is unclear in
repeater implementations.
example, some cards may
daughter cards which make
capacity change depending on
cards installed. Meaning is
unclear in a
implementation. Also,
groups are not required to
numbered from 1..capacity, but
be computed algorithmically

Flick Standards Track [Page 10]

RFC 2266 IEEE 802.12 Repeater MIB January 1998

related to Entity MIB indices
this object was not
useful

.aRepeaterHealthData Since the data is
specific and non-interoperable
it was not considered useful

.aRepeaterHealthText Implementation experience
similar object in 802.3 Rptr
indicated it was not useful

.acExecuteNonDisruptiveSelfTest Implementation experience
similar object in 802.3 Rptr
indicated it was not useful

.nGroupMapChange Since aGroupMap was not included
a notification of a change in
object was not needed

.aPortMap Can be determined by GetNext
of
.nPortMapChange Since aPortMap was not included
a notification of a change in
object was not needed

.aMediaType This object is a function of
Physical Media Dependent (PMD
layer, which is
differently for each type
network. For an 802.3 network
.aMediaType corresponds to the
definitions in the 802.3 MAU MIB
For management of an 802.12
network, mapping of this object
deferred to future work on
802.12 PMD MIB which will
both repeater and interface
information and redundant
support

Flick Standards Track [Page 11]

RFC 2266 IEEE 802.12 Repeater MIB January 1998

3.

DOT12-RPTR-MIB DEFINITIONS ::=

mib-2, Integer32, Counter32, Counter64,
OBJECT-TYPE, MODULE-IDENTITY, NOTIFICATION-
FROM SNMPv2-
MacAddress, TruthValue,
FROM SNMPv2-
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-
FROM SNMPv2-CONF

vgRptrMIB MODULE-
LAST-UPDATED "9705192256Z" -- May 19, 1997
ORGANIZATION "IETF 100VG-AnyLAN Working Group
CONTACT-
"WG E-mail: vgmib@hprnd.rose.hp.

Chair: Jeff
Postal: RedBack
2570 North First Street, Suite 410
San Jose, CA 95131
Tel: +1 408 571 2699
Fax: +1 408 571 2698
E-mail: jeff@redbacknetworks.

Editor: John
Postal: Hewlett Packard
8000 Foothills Blvd. M/S 5556
Roseville, CA 95747-5556
Tel: +1 916 785 4018
Fax: +1 916 785 3583
E-mail: johnf@hprnd.rose.hp.com

"This MIB module describes objects for
IEEE 802.12 repeaters."
::= { mib-2 53 }

vgRptrObjects OBJECT IDENTIFIER ::= { vgRptrMIB 1 }
vgRptrBasic OBJECT IDENTIFIER ::= { vgRptrObjects 1 }
vgRptrBasicRptr OBJECT IDENTIFIER ::= { vgRptrBasic 1 }

vgRptrInfoTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS

Flick Standards Track [Page 12]

RFC 2266 IEEE 802.12 Repeater MIB January 1998

"A table of information about each 802.12
in the managed system."
::= { vgRptrBasicRptr 1 }

vgRptrInfoEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS

"An entry in the table, containing
about a single repeater."
INDEX { vgRptrInfoIndex }
::= { vgRptrInfoTable 1 }

VgRptrInfoEntry ::=
SEQUENCE {
vgRptrInfoIndex Integer32,
vgRptrInfoMACAddress MacAddress
vgRptrInfoCurrentFramingType INTEGER
vgRptrInfoDesiredFramingType INTEGER
vgRptrInfoFramingCapability INTEGER
vgRptrInfoTrainingVersion INTEGER
vgRptrInfoOperStatus INTEGER
vgRptrInfoReset INTEGER
vgRptrInfoLastChange
}

vgRptrInfoIndex OBJECT-
SYNTAX Integer32 (1..2147483647)
MAX-ACCESS not-
STATUS

"A unique identifier for the repeater for
this entry contains information. The
scheme for repeaters is implementation specific."

"IEEE Standard 802.12-1995, 13.2.4.2.1,
aRepeaterID."
::= { vgRptrInfoEntry 1 }

vgRptrInfoMACAddress OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS

"The MAC address used by the repeater when
initiates training on the uplink port.
are allowed to train with an assigned MAC

Flick Standards Track [Page 13]

RFC 2266 IEEE 802.12 Repeater MIB January 1998

or a null (all zeroes) MAC address."

"IEEE Standard 802.12-1995, 13.2.4.2.1,
aMACAddress."
::= { vgRptrInfoEntry 2 }

vgRptrInfoCurrentFramingType OBJECT-
SYNTAX INTEGER {
frameType88023(1),
frameType88025(2)
}
MAX-ACCESS read-
STATUS

"The type of framing (802.3 or 802.5)
in use by the repeater."

"IEEE Standard 802.12-1995, 13.2.4.2.1,
aCurrentFramingType."
::= { vgRptrInfoEntry 3 }

vgRptrInfoDesiredFramingType OBJECT-
SYNTAX INTEGER {
frameType88023(1),
frameType88025(2)
}
MAX-ACCESS read-
STATUS

"The type of framing which will be used by
repeater after the next time it is reset

The value of this object should be
across repeater resets and power failures."

"IEEE Standard 802.12-1995, 13.2.4.2.1,
aDesiredFramingType."
::= { vgRptrInfoEntry 4 }

vgRptrInfoFramingCapability OBJECT-
SYNTAX INTEGER {
frameType88023(1),
frameType88025(2),
frameTypeEither(3)
}
MAX-ACCESS read-
STATUS

Flick Standards Track [Page 14]

RFC 2266 IEEE 802.12 Repeater MIB January 1998

"The type of framing this repeater is capable
supporting."

"IEEE Standard 802.12-1995, 13.2.4.2.1,
aFramingCapability."
::= { vgRptrInfoEntry 5 }

vgRptrInfoTrainingVersion OBJECT-
SYNTAX INTEGER (0..7)
MAX-ACCESS read-
STATUS

"The highest version bits (vvv bits) supported
the repeater during training."

"IEEE Standard 802.12-1995, 13.2.4.2.1,
aRMACVersion."
::= { vgRptrInfoEntry 6 }

vgRptrInfoOperStatus OBJECT-
SYNTAX INTEGER {
other(1),
ok(2),
generalFailure(3)
}
MAX-ACCESS read-
STATUS

"The vgRptrInfoOperStatus object indicates
operational state of the repeater."

"IEEE Standard 802.12-1995, 13.2.4.2.1,
aRepeaterHealthState."
::= { vgRptrInfoEntry 7 }

vgRptrInfoReset OBJECT-
SYNTAX INTEGER {
noReset(1),
reset(2)
}

MAX-ACCESS read-
STATUS

"Setting this object to reset(2) causes
repeater to transition to its initial state
specified in clause 12 [IEEE Std 802.12].

Flick Standards Track [Page 15]

RFC 2266 IEEE 802.12 Repeater MIB January 1998

Setting this object to noReset(1) has no effect
The agent will always return the value noReset(1)
when this object is read

After receiving a request to set this variable
reset(2), the agent is allowed to delay the
for a short period. For example, the
may choose to delay the reset long enough
allow the SNMP response to be transmitted.
any event, the SNMP response must be transmitted

This action does not reset the
counters defined in this document nor does
affect the vgRptrPortAdminStatus parameters
Included in this action is the execution of
disruptive Self-Test with the
characteristics

1) The nature of the tests is not specified
2) The test resets the repeater but
affecting configurable
information about the repeater
3) Packets received during the test may
may not be transferred
4) The test does not interfere
management functions

After performing this self-test, the agent
update the repeater health information (
vgRptrInfoOperStatus), and send
vgRptrResetEvent."

"IEEE Standard 802.12-1995, 13.2.4.2.2,
acResetRepeater."
::= { vgRptrInfoEntry 8 }

vgRptrInfoLastChange OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS

"The value of sysUpTime when any of the
conditions occurred

1) agent cold- or warm-started
2) this instance of repeater was
(such as when a device or module
added to the system);

Flick Standards Track [Page 16]

RFC 2266 IEEE 802.12 Repeater MIB January 1998

3) a change in the value
vgRptrInfoOperStatus
4) ports were added or removed as members
the repeater;
5) any of the counters associated with
repeater had a discontinuity."
::= { vgRptrInfoEntry 9 }

vgRptrBasicGroup OBJECT IDENTIFIER ::= { vgRptrBasic 2 }

vgRptrBasicGroupTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS

"A table containing information about groups
ports."
::= { vgRptrBasicGroup 1 }

vgRptrBasicGroupEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS

"An entry in the vgRptrBasicGroupTable,
information about a single group of ports."
INDEX { vgRptrGroupIndex }
::= { vgRptrBasicGroupTable 1 }

VgRptrBasicGroupEntry ::=
SEQUENCE {
vgRptrGroupIndex Integer32,
vgRptrGroupObjectID OBJECT IDENTIFIER
vgRptrGroupOperStatus INTEGER
vgRptrGroupPortCapacity Integer32,
vgRptrGroupCablesBundled
}

vgRptrGroupIndex OBJECT-
SYNTAX Integer32 (1..2146483647)
MAX-ACCESS not-
STATUS

"This object identifies the group within
system for which this entry contains information
The numbering scheme for groups is
specific."

Flick Standards Track [Page 17]

RFC 2266 IEEE 802.12 Repeater MIB January 1998

"IEEE Standard 802.12-1995, 13.2.4.4.1,
aGroupID."
::= { vgRptrBasicGroupEntry 1 }

vgRptrGroupObjectID OBJECT-
SYNTAX OBJECT
MAX-ACCESS read-
STATUS

"The vendor's authoritative identification of
group. This value may be allocated within
SMI enterprises subtree (1.3.6.1.4.1)
provides a straight-forward and unambiguous
for determining what kind of group is
managed

For example, this object could take the
1.3.6.1.4.1.4242.1.2.14 if vendor 'Flintstones
Inc.' was assigned the subtree 1.3.6.1.4.1.4242,
and had assigned the
1.3.6.1.4.1.4242.1.2.14 to its 'Wilma
6-Port Plug-in Module.'"
::= { vgRptrBasicGroupEntry 2 }

vgRptrGroupOperStatus OBJECT-
SYNTAX INTEGER {
other(1),
operational(2),
malfunctioning(3),
notPresent(4),
underTest(5),
resetInProgress(6)
}
MAX-ACCESS read-
STATUS

"An object that indicates the operational
of the group

A status of notPresent(4) indicates that
group is temporarily or permanently
and/or logically not a part of the system.
is an implementation-specific matter as
whether the agent effectively removes
entries from the table

A status of operational(2) indicates that
group is functioning, and a status

Flick Standards Track [Page 18]

RFC 2266 IEEE 802.12 Repeater MIB January 1998

malfunctioning(3) indicates that the group
malfunctioning in some way."
::= { vgRptrBasicGroupEntry 3 }

vgRptrGroupPortCapacity OBJECT-
SYNTAX Integer32 (1..2146483647)
MAX-ACCESS read-
STATUS

"The vgRptrGroupPortCapacity is the number
ports that can be contained within the group
Valid range is 1-2147483647. Within each group
the ports are uniquely numbered in the range
1 to vgRptrGroupPortCapacity

Some ports may not be present in the system,
which case the actual number of ports present
be less than the value of vgRptrGroupPortCapacity
The number of ports present is never greater
the value of vgRptrGroupPortCapacity

Note: In practice, this will generally be
number of ports on a module, card, or board,
the port numbers will correspond to numbers
on the physical embodiment."

"IEEE Standard 802.12-1995, 13.2.4.4.1,
aGroupPortCapacity."
::= { vgRptrBasicGroupEntry 4 }

vgRptrGroupCablesBundled OBJECT-
SYNTAX INTEGER {
someCablesBundled(1),
noCablesBundled(2)
}
MAX-ACCESS read-
STATUS

"This object is used to indicate whether there
any four-pair UTP links connected to this
that are contained in a cable bundle with
four-pair groups (e.g. a 25-pair bundle).
cable may only be used for repeater-to-end
links where the end node is not in
mode

When a broadcast or multicast packet is
from a port on this group that is not

Flick Standards Track [Page 19]

RFC 2266 IEEE 802.12 Repeater MIB January 1998

promiscuous or cascaded port, the packet will
buffered completely before being repeated
this object is set to 'someCablesBundled(1)'.
When this object is equal to 'noCablesBundled(2)',
all packets received from ports on this group
be repeated as the frame is being received

Note that the value 'someCablesBundled(1)'
work in the vast majority of all installations
regardless of whether or not any cables
physically in a bundle, since packets
from promiscuous and cascaded ports
avoid the store and forward. The main
in which 'noCablesBundled(2)' is beneficial
when there is a large amount of multicast
and the cables are not in a bundle

The value of this object should be
across repeater resets and power failures."

"IEEE Standard 802.12-1995, 13.2.4.4.1,
aGroupCablesBundled."
::= { vgRptrBasicGroupEntry 5 }

vgRptrBasicPort OBJECT IDENTIFIER ::= { vgRptrBasic 3 }

vgRptrBasicPortTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS

"A table containing configuration and
information about 802.12 repeater ports in
system. The number of entries is independent
the number of repeaters in the managed system."
::= { vgRptrBasicPort 1 }

vgRptrBasicPortEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS

"An entry in the vgRptrBasicPortTable,
information about a single port."
INDEX { vgRptrGroupIndex, vgRptrPortIndex }
::= { vgRptrBasicPortTable 1 }

VgRptrBasicPortEntry ::=

Flick Standards Track [Page 20]

RFC 2266 IEEE 802.12 Repeater MIB January 1998

SEQUENCE {
vgRptrPortIndex Integer32,
vgRptrPortType INTEGER
vgRptrPortAdminStatus INTEGER
vgRptrPortOperStatus INTEGER
vgRptrPortSupportedPromiscMode INTEGER
vgRptrPortSupportedCascadeMode INTEGER
vgRptrPortAllowedTrainType INTEGER
vgRptrPortLastTrainConfig OCTET STRING
vgRptrPortTrainingResult OCTET STRING
vgRptrPortPriorityEnable TruthValue
vgRptrPortRptrInfoIndex Integer32
}

vgRptrPortIndex OBJECT-
SYNTAX Integer32 (1..2147483647)
MAX-ACCESS not-
STATUS

"This object identifies the port within the
for which this entry contains information.
identifies the port independently from
repeater it may be attached to. The
scheme for ports is implementation specific
however, this value can never be greater
vgRptrGroupPortCapacity for the associated group."

"IEEE Standard 802.12-1995, 13.2.4.5.1,
aPortID."
::= { vgRptrBasicPortEntry 1 }

vgRptrPortType OBJECT-
SYNTAX INTEGER {
cascadeExternal(1),
cascadeInternal(2),
localExternal(3),
localInternal(4)
}
MAX-ACCESS read-
STATUS

"Describes the type of port. One of
following

cascadeExternal - Port is an uplink
physical connections
are externally
cascadeInternal - Port is an uplink

Flick Standards Track [Page 21]

RFC 2266 IEEE 802.12 Repeater MIB January 1998

physical connections
are not externally visible
such as a connection to
internal backplane in

localExternal - Port is a downlink or
port with
visible
localInternal - Port is a downlink or
port with connections
are not externally visible
such as a connection to
internal

'internal' is used to identify ports which
traffic into the repeater, but do not have
external connections. Note that both DTE
cascaded repeater downlinks are
'local' ports."

"IEEE Standard 802.12-1995, 13.2.4.5.1,
aPortType."
::= { vgRptrBasicPortEntry 2 }

vgRptrPortAdminStatus OBJECT-
SYNTAX INTEGER {
enabled(1),
disabled(2)
}
MAX-ACCESS read-
STATUS

"Port enable/disable function. Enabling
disabled port will cause training to
initiated by the training initiator (the
mode device) on the link. Setting this object
disabled(2) disables the port

A disabled port neither transmits nor receives
Once disabled, a port must be explicitly
to restore operation. A port which is
when power is lost or when a reset is
shall remain disabled when normal
resumes

The value of this object should be
across repeater resets and power failures."

Flick Standards Track [Page 22]

RFC 2266 IEEE 802.12 Repeater MIB January 1998

"IEEE Standard 802.12-1995, 13.2.4.5.1,
aPortAdministrativeState."
::= { vgRptrBasicPortEntry 3 }

vgRptrPortOperStatus OBJECT-
SYNTAX INTEGER {
active(1),
inactive(2),
training(3)
}
MAX-ACCESS read-
STATUS

"Current status for the port as specified by
PORT_META_STATE in the port process module
clause 12 [IEEE Std 802.12].

During initialization or any link
conditions, vgRptrPortStatus will
'inactive(2)'.

When Training_Up is received by the repeater on
local port (or when Training_Down is received
a cascade port), vgRptrPortStatus will change
'training(3)' and vgRptrTrainingResult can
monitored to see the detailed status
training

When 24 consecutive good FCS packets are
and the configuration bits are OK
vgRptrPortStatus will change to 'active(1)'.

A disabled port shall have a port status
'inactive(2)'."

"IEEE Standard 802.12, 13.2.4.5.1,
aPortStatus."
::= { vgRptrBasicPortEntry 4 }

vgRptrPortSupportedPromiscMode OBJECT-
SYNTAX INTEGER {
singleModeOnly(1),
singleOrPromiscMode(2),
promiscModeOnly(3)
}
MAX-ACCESS read-
STATUS

Flick Standards Track [Page 23]

RFC 2266 IEEE 802.12 Repeater MIB January 1998

"This object describes whether the port
is capable of supporting promiscuous mode,
address mode (i.e., repeater filters unicasts
addressed to the end station attached to
port), or both. A port for which
is equal to 'cascadeInternal' or 'cascadeExternal
will always have a value of 'promiscModeOnly'
this object."

"IEEE Standard 802.12-1995, 13.2.4.5.1,
aSupportedPromiscMode."
::= { vgRptrBasicPortEntry 5 }

vgRptrPortSupportedCascadeMode OBJECT-
SYNTAX INTEGER {
endNodesOnly(1),
endNodesOrRepeaters(2),
cascadePort(3)
}
MAX-ACCESS read-
STATUS

"This object describes whether the port
is capable of supporting cascaded repeaters,
nodes, or both. A port for which
is equal to 'cascadeInternal'
'cascadeExternal' will always have a value
'cascadePort' for this object."

"IEEE Standard 802.12-1995, 13.2.4.5.1,
aSupportedCascadeMode."
::= { vgRptrBasicPortEntry 6 }

vgRptrPortAllowedTrainType OBJECT-
SYNTAX INTEGER {
allowEndNodesOnly(1),
allowPromiscuousEndNodes(2),
allowEndNodesOrRepeaters(3),
allowAnything(4)
}
MAX-ACCESS read-
STATUS

"This security object is set by the
manager to configure what type of device
permitted to connect to the port. One of
following values

Flick Standards Track [Page 24]

RFC 2266 IEEE 802.12 Repeater MIB January 1998

allowEndNodesOnly - only non
promiscuous
nodes permitted
allowPromiscuousEndNodes - promiscuous
non-
end

allowEndNodesOrRepeaters - repeaters or non
promiscuous
nodes
allowAnything - repeaters
promiscuous
non-
end

For a port for which vgRptrPortType is equal
'cascadeInternal' or 'cascadeExternal',
corresponding instance of this object may not
set to 'allowEndNodesOnly'
'allowPromiscuousEndNodes'.

The agent must reject a SET of this object if
value includes no capabilities that
supported by this port's hardware, as defined
the values of the corresponding instances
vgRptrPortSupportedPromiscMode
vgRptrPortSupportedCascadeMode

Note that vgRptrPortSupportPromiscMode
vgRptrPortSupportedCascadeMode represent what
port hardware is capable of supporting
vgRptrPortAllowedTrainType is used for setting
administrative policy for a port. The actual
of training configurations that will be
to succeed on a port is the intersection of
the hardware will support and what
administratively allowed. The above
on what values may be set to this object says
the intersection of what is supported and what
allowed must be non-empty. In other words,
must not result in a situation in which
would be allowed to train on that port. However
a value can be set to this object as long as
combination of this object and what is
by the hardware would still leave at least
configuration that could successfully train on
port

Flick Standards Track [Page 25]

RFC 2266 IEEE 802.12 Repeater MIB January 1998

The value of this object should be
across repeater resets and power failures."

"IEEE Standard 802.12-1995, 13.2.4.5.1,
aAllowableTrainingType."
::= { vgRptrBasicPortEntry 7 }

vgRptrPortLastTrainConfig OBJECT-
SYNTAX OCTET STRING (SIZE(2))
MAX-ACCESS read-
STATUS

"This object is a 16 bit field. For local ports
this object contains the requested
field from the most recent error-free
request frame sent by the device connected
the port. For cascade ports, this object
the responder's allowed configuration field
the most recent error-free training response
received in response to training initiated by
repeater. The format of the current version
this field is described in section 3.2.
refer to the most recent version of the
802.12 standard for the most up-to-date
of the format of this object."

"IEEE Standard 802.12-1995, 13.2.4.5.1,
aLastTrainingConfig."
::= { vgRptrBasicPortEntry 8 }

vgRptrPortTrainingResult OBJECT-
SYNTAX OCTET STRING (SIZE(3))
MAX-ACCESS read-
STATUS

"This 18 bit field is used to indicate the
of training. It contains two bits which
if error-free training frames have been received
and it also contains the 16 bits of the
configuration field from the most
error-free training response frame on the port

First Octet: Second and Third Octets
7 6 5 4 3 2 1 0
+-+-+-+-+-+-+-+-+-----------------------------+
|0|0|0|0|0|0|V|G| allowed configuration field |
+-+-+-+-+-+-+-+-+-----------------------------+

Flick Standards Track [Page 26]

RFC 2266 IEEE 802.12 Repeater MIB January 1998

V: Valid: set when at least one error-
training frame has been received
Indicates the 16 training
bits in vgRptrPortLastTrainConfig
vgRptrPortTrainingResult contain
information. This bit is cleared
vgRptrPortStatus transitions to
'inactive' or 'training' state
G: LinkGood: indicates the link hardware
OK. Set if 24 consecutive error-
training packets have been exchanged
Cleared when a training packet
errors is received, or
vgRptrPortStatus transitions to
'inactive' or 'training' state

The format of the current version of the
configuration field is described in section 3.2.
Please refer to the most recent version of
IEEE 802.12 standard for the most up-to-
definition of the format of this field

If the port is in training, a management
can examine this object to see if any
packets have been passed successfully. If
have been any good training packets, the
bit will be set and the management station
examine the allowed configuration field to see
there is a duplicate address, configuration,
security problem

Note that on a repeater local port, this
generates the training response bits, while
a cascade port, the device at the upper end
the link originated the training response bits."

"IEEE Standard 802.12-1995, 13.2.4.5.1,
aTrainingResult."
::= { vgRptrBasicPortEntry 9 }
vgRptrPortPriorityEnable OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS

"A configuration flag used to determine
the repeater will service high priority
received on the port as high priority or
priority. When 'false', high priority

Flick Standards Track [Page 27]

RFC 2266 IEEE 802.12 Repeater MIB January 1998

on this port will be serviced as normal priority

The setting of this object has no effect on
cascade port. Also note that the setting of
object has no effect on a port connected to
cascaded repeater. In both of these cases,
setting is treated as always 'true'. The
'false' only has an effect when the port is
localInternal or localExternal port connected
an end node

The value of this object should be
across repeater resets and power failures."

"IEEE Standard 802.12-1995, 13.2.4.5.1,
aPriorityEnable."
::= { vgRptrBasicPortEntry 10 }

vgRptrPortRptrInfoIndex OBJECT-
SYNTAX Integer32 (0..2147483647)
MAX-ACCESS read-
STATUS

"This object identifies the repeater that
port is currently mapped to. The
identified by a particular value of this
is the same as that identified by the same
of vgRptrInfoIndex. A value of zero
that this port is not currently mapped to
repeater."
::= { vgRptrBasicPortEntry 11 }

vgRptrMonitor OBJECT IDENTIFIER ::= { vgRptrObjects 2 }

vgRptrMonRepeater OBJECT IDENTIFIER ::= { vgRptrMonitor 1 }

vgRptrMonitorTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS

"A table of performance and error statistics
each repeater in the system. The instance of
vgRptrInfoLastChange associated with a
is used to indicate possible discontinuities
the counters in this table that are
with the same repeater."

Flick Standards Track [Page 28]

RFC 2266 IEEE 802.12 Repeater MIB January 1998

::= { vgRptrMonRepeater 1 }

vgRptrMonitorEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS

"An entry in the table, containing
for a single repeater."
INDEX { vgRptrInfoIndex }
::= { vgRptrMonitorTable 1 }

VgRptrMonitorEntry ::=
SEQUENCE {
vgRptrMonTotalReadableFrames Counter32,
vgRptrMonTotalReadableOctets Counter32,
vgRptrMonReadableOctetRollovers Counter32,
vgRptrMonHCTotalReadableOctets Counter64,
vgRptrMonTotalErrors Counter32
}

vgRptrMonTotalReadableFrames OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS

"The total number of good frames of valid
length that have been received on all ports
this repeater. If an implementation
obtain a count of frames as seen by the
itself, this counter may be implemented as
summation of the values of
vgRptrPortReadableFrames counters for all of
ports in this repeater

This counter may experience a discontinuity
the value of the corresponding instance
vgRptrInfoLastChange changes."
::= { vgRptrMonitorEntry 1 }

vgRptrMonTotalReadableOctets OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS

"The total number of octets contained in
frames that have been received on all ports
this repeater. If an implementation

Flick Standards Track [Page 29]

RFC 2266 IEEE 802.12 Repeater MIB January 1998

obtain a count of octets as seen by the
itself, this counter may be implemented as
summation of the values of
vgRptrPortReadableOctets counters for all of
ports in this repeater

Note that this counter can roll over
quickly. A management station is advised
also poll the
object, or to use the 64-bit counter defined
vgRptrMonHCTotalReadableOctets instead of
two 32-bit counters

This two-counter mechanism is provided for
network management protocols that do not
64-bit counters (e.g. SNMPv1). Note
retrieval of these two counters in the same
is NOT guaranteed to be atomic

This counter may experience a discontinuity
the value of the corresponding instance
vgRptrInfoLastChange changes."
::= { vgRptrMonitorEntry 2 }

vgRptrMonReadableOctetRollovers OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS

"The total number of times that the
instance of the
counter has rolled over

This two-counter mechanism is provided for
network management protocols that do not
64-bit counters (e.g. SNMPv1). Note
retrieval of these two counters in the same
is NOT guaranteed to be atomic

This counter may experience a discontinuity
the value of the corresponding instance
vgRptrInfoLastChange changes."
::= { vgRptrMonitorEntry 3 }

vgRptrMonHCTotalReadableOctets OBJECT-
SYNTAX Counter64
MAX-ACCESS read-
STATUS

Flick Standards Track [Page 30]

RFC 2266 IEEE 802.12 Repeater MIB January 1998

"The total number of octets contained in
frames that have been received on all ports
this repeater. If an implementation
obtain a count of octets as seen by the
itself, this counter may be implemented as
summation of the values of
vgRptrPortHCReadableOctets counters for all of
ports in this repeater

This counter is a 64 bit version
vgRptrMonTotalReadableOctets. It should be
by Network Management protocols which support 64
bit counters (e.g. SNMPv2).

This counter may experience a discontinuity
the value of the corresponding instance
vgRptrInfoLastChange changes."
::= { vgRptrMonitorEntry 4 }

vgRptrMonTotalErrors OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS

"The total number of errors which have occurred
all of the ports in this repeater. If
implementation cannot obtain a count of
errors as seen by the repeater itself,
counter may be implemented as the summation of
values of the vgRptrPortIPMFrames
vgRptrPortOversizeFrames,
vgRptrPortDataErrorFrames counters for all of
ports in this repeater

This counter may experience a discontinuity
the value of the corresponding instance
vgRptrInfoLastChange changes."
::= { vgRptrMonitorEntry 5 }

vgRptrMonGroup OBJECT IDENTIFIER ::= { vgRptrMonitor 2 }
-- Currently

vgRptrMonPort OBJECT IDENTIFIER ::= { vgRptrMonitor 3 }

vgRptrMonPortTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-

Flick Standards Track [Page 31]

RFC 2266 IEEE 802.12 Repeater MIB January 1998

STATUS

"A table of performance and error statistics
the ports. The columnar
vgRptrPortLastChange is used to indicate
discontinuities of counter type columnar
in this table."
::= { vgRptrMonPort 1 }

vgRptrMonPortEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS

"An entry in the vgRptrMonPortTable,
performance and error statistics for a
port."
INDEX { vgRptrGroupIndex, vgRptrPortIndex }
::= { vgRptrMonPortTable 1 }

VgRptrMonPortEntry ::=
SEQUENCE {
vgRptrPortReadableFrames Counter32,
vgRptrPortReadableOctets Counter32,
vgRptrPortReadOctetRollovers Counter32,
vgRptrPortHCReadableOctets Counter64,
vgRptrPortUnreadableOctets Counter32,
vgRptrPortUnreadOctetRollovers Counter32,
vgRptrPortHCUnreadableOctets Counter64,
vgRptrPortHighPriorityFrames Counter32,
vgRptrPortHighPriorityOctets Counter32,
vgRptrPortHighPriOctetRollovers Counter32,
vgRptrPortHCHighPriorityOctets Counter64,
vgRptrPortNormPriorityFrames Counter32,
vgRptrPortNormPriorityOctets Counter32,
vgRptrPortNormPriOctetRollovers Counter32,
vgRptrPortHCNormPriorityOctets Counter64,
vgRptrPortBroadcastFrames Counter32,
vgRptrPortMulticastFrames Counter32,
vgRptrPortNullAddressedFrames Counter32,
vgRptrPortIPMFrames Counter32,
vgRptrPortOversizeFrames Counter32,
vgRptrPortDataErrorFrames Counter32,
vgRptrPortPriorityPromotions Counter32,
vgRptrPortTransitionToTrainings Counter32,
vgRptrPortLastChange
}

Flick Standards Track [Page 32]

RFC 2266 IEEE 802.12 Repeater MIB January 1998

vgRptrPortReadableFrames OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS

"This object is the number of good frames
valid frame length that have been received
this port. This counter is incremented by
for each frame received on the port which is
counted by any of the following error counters
vgRptrPortIPMFrames, vgRptrPortOversizeFrames
vgRptrPortNullAddressedFrames,
vgRptrPortDataErrorFrames

This counter may experience a discontinuity
the value of the corresponding instance
vgRptrPortLastChange changes."

"IEEE Standard 802.12-1995, 13.2.4.5.1,
aReadableFramesReceived."
::= { vgRptrMonPortEntry 1 }

vgRptrPortReadableOctets OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS

"This object is a count of the number of
contained in good frames that have been
on this port. This counter is incremented
OctetCount for each frame received on this
which has been determined to be a readable
(i.e. each frame counted
vgRptrPortReadableFrames).

Note that this counter can roll over
quickly. A management station is advised
also poll the
object, or to use the 64-bit counter defined
vgRptrPortHCReadableOctets instead of the
32-bit counters

This two-counter mechanism is provided for
network management protocols that do not
64-bit counters (e.g. SNMPv1). Note
retrieval of these two counters in the same
is NOT guaranteed to be atomic

Flick Standards Track [Page 33]

RFC 2266 IEEE 802.12 Repeater MIB January 1998

This counter may experience a discontinuity
the value of the corresponding instance
vgRptrPortLastChange changes."

"IEEE Standard 802.12-1995, 13.2.4.5.1,
aReadableOctetsReceived."
::= { vgRptrMonPortEntry 2 }

vgRptrPortReadOctetRollovers OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS

"This object is a count of the number of
that the associated instance of
vgRptrPortReadableOctets counter has rolled over

This two-counter mechanism is provided for
network management protocols that do not
64-bit counters (e.g. SNMPv1). Note
retrieval of these two counters in the same
is NOT guaranteed to be atomic

This counter may experience a discontinuity
the value of the corresponding instance
vgRptrPortLastChange changes."

"IEEE Standard 802.12-1995, 13.2.4.5.1,
aReadableOctetsReceived."
::= { vgRptrMonPortEntry 3 }

vgRptrPortHCReadableOctets OBJECT-
SYNTAX Counter64
MAX-ACCESS read-
STATUS

"This object is a count of the number of
contained in good frames that have been
on this port. This counter is incremented
OctetCount for each frame received on this
which has been determined to be a readable
(i.e. each frame counted
vgRptrPortReadableFrames).

This counter is a 64 bit version
vgRptrPortReadableOctets. It should be used
Network Management protocols which support 64
counters (e.g. SNMPv2).

Flick Standards Track [Page 34]

RFC 2266 IEEE 802.12 Repeater MIB January 1998

This counter may experience a discontinuity
the value of the corresponding instance
vgRptrPortLastChange changes."

"IEEE Standard 802.12-1995, 13.2.4.5.1,
aReadableOctetsReceived."
::= { vgRptrMonPortEntry 4 }

vgRptrPortUnreadableOctets OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS

"This object is a count of the number of
contained in invalid frames that have
received on this port. This counter
incremented by OctetCount for each frame
on this port which is counted
vgRptrPortIPMFrames, vgRptrPortOversizeFrames
vgRptrPortNullAddressedFrames,
vgRptrPortDataErrorFrames. This counter can
combined with vgRptrPortReadableOctets
calculate network utilization

Note that this counter can roll over
quickly. A management station is advised
also poll the
object, or to use the 64-bit counter defined
vgRptrPortHCUnreadableOctets instead of the
32-bit counters

This two-counter mechanism is provided for
network management protocols that do not
64-bit counters (e.g. SNMPv1). Note
retrieval of these two counters in the same
is NOT guaranteed to be atomic

This counter may experience a discontinuity
the value of the corresponding instance
vgRptrPortLastChange changes."

"IEEE Standard 802.12-1995, 13.2.4.5.1,
aOctetsInUnreadableFramesRcvd."
::= { vgRptrMonPortEntry 5 }

vgRptrPortUnreadOctetRollovers OBJECT-
SYNTAX Counter32
MAX-ACCESS read-

Flick Standards Track [Page 35]

RFC 2266 IEEE 802.12 Repeater MIB January 1998

STATUS

"This object is a count of the number of
that the associated instance of
vgRptrPortUnreadableOctets counter has
over

This two-counter mechanism is provided for
network management protocols that do not
64-bit counters (e.g. SNMPv1). Note
retrieval of these two counters in the same
is NOT guaranteed to be atomic

This counter may experience a discontinuity
the value of the corresponding instance
vgRptrPortLastChange changes."

"IEEE Standard 802.12-1995, 13.2.4.5.1,
aOctetsInUnreadableFramesRcvd."
::= { vgRptrMonPortEntry 6 }

vgRptrPortHCUnreadableOctets OBJECT-
SYNTAX Counter64
MAX-ACCESS read-
STATUS

"This object is a count of the number of
contained in invalid frames that have
received on this port. This counter
incremented by OctetCount for each frame
on this port which is counted
vgRptrPortIPMFrames, vgRptrPortOversizeFrames
vgRptrPortNullAddressedFrames,
vgRptrPortDataErrorFrames. This counter can
combined with vgRptrPortHCReadableOctets
calculate network utilization

This counter is a 64 bit version
vgRptrPortUnreadableOctets. It should be
by Network Management protocols which support 64
bit counters (e.g. SNMPv2).

This counter may experience a discontinuity
the value of the corresponding instance
vgRptrPortLastChange changes."

"IEEE Standard 802.12-1995, 13.2.4.5.1,
aOctetsInUnreadableFramesRcvd."

Flick Standards Track [Page 36]

RFC 2266 IEEE 802.12 Repeater MIB January 1998

::= { vgRptrMonPortEntry 7 }

vgRptrPortHighPriorityFrames OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS

"This object is a count of high priority
that have been received on this port.
counter is incremented by one for each
priority frame received on this port.
counter includes both good and bad high
frames, as well as high priority training frames
This counter does not include normal
frames which were priority promoted

This counter may experience a discontinuity
the value of the corresponding instance
vgRptrPortLastChange changes."

"IEEE Standard 802.12-1995, 13.2.4.5.1,
aHighPriorityFramesReceived."
::= { vgRptrMonPortEntry 8 }

vgRptrPortHighPriorityOctets OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS

"This object is a count of the number of
contained in high priority frames that have
received on this port. This counter
incremented by OctetCount for each frame
on this port which is counted
vgRptrPortHighPriorityFrames

Note that this counter can roll over
quickly. A management station is advised
also poll the
object, or to use the 64-bit counter defined
vgRptrPortHCHighPriorityOctets instead of the
32-bit counters

This two-counter mechanism is provided for
network management protocols that do not
64-bit counters (e.g. SNMPv1). Note
retrieval of these two counters in the same
is NOT guaranteed to be atomic

Flick Standards Track [Page 37]

RFC 2266 IEEE 802.12 Repeater MIB January 1998

This counter may experience a discontinuity
the value of the corresponding instance
vgRptrPortLastChange changes."

"IEEE Standard 802.12-1995, 13.2.4.5.1,
aHighPriorityOctetsReceived."
::= { vgRptrMonPortEntry 9 }

vgRptrPortHighPriOctetRollovers OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS

"This object is a count of the number of
that the associated instance of
vgRptrPortHighPriorityOctets counter has
over

This two-counter mechanism is provided for
network management protocols that do not
64-bit counters (e.g. SNMPv1). Note
retrieval of these two counters in the same
is NOT guaranteed to be atomic

This counter may experience a discontinuity
the value of the corresponding instance
vgRptrPortLastChange changes."

"IEEE Standard 802.12-1995, 13.2.4.5.1,
aHighPriorityOctetsReceived."
::= { vgRptrMonPortEntry 10 }

vgRptrPortHCHighPriorityOctets OBJECT-
SYNTAX Counter64
MAX-ACCESS read-
STATUS

"This object is a count of the number of
contained in high priority frames that have
received on this port. This counter
incremented by OctetCount for each frame
on this port which is counted
vgRptrPortHighPriorityFrames

This counter is a 64 bit version
vgRptrPortHighPriorityOctets. It should be
by Network Management protocols which
64 bit counters (e.g. SNMPv2).

Flick Standards Track [Page 38]

RFC 2266 IEEE 802.12 Repeater MIB January 1998

This counter may experience a discontinuity
the value of the corresponding instance
vgRptrPortLastChange changes."

"IEEE Standard 802.12-1995, 13.2.4.5.1,
aHighPriorityOctetsReceived."
::= { vgRptrMonPortEntry 11 }

vgRptrPortNormPriorityFrames OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS

"This object is a count of normal priority
that have been received on this port.
counter is incremented by one for each
priority frame received on this port.
counter includes both good and bad
priority frames, as well as normal
training frames and normal priority frames
were priority promoted

This counter may experience a discontinuity
the value of the corresponding instance
vgRptrPortLastChange changes."

"IEEE Standard 802.12-1995, 13.2.4.5.1,
aNormalPriorityFramesReceived."
::= { vgRptrMonPortEntry 12 }

vgRptrPortNormPriorityOctets OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS

"This object is a count of the number of
contained in normal priority frames that
been received on this port. This counter
incremented by OctetCount for each frame
on this port which is counted
vgRptrPortNormPriorityFrames

Note that this counter can roll over
quickly. A management station is advised
also poll the
object, or to use the 64-bit counter defined
vgRptrPortHCNormPriorityOctets instead of the
32-bit counters

Flick Standards Track [Page 39]

RFC 2266 IEEE 802.12 Repeater MIB January 1998

This two-counter mechanism is provided for
network management protocols that do not
64-bit counters (e.g. SNMPv1). Note
retrieval of these two counters in the same
is NOT guaranteed to be atomic

This counter may experience a discontinuity
the value of the corresponding instance
vgRptrPortLastChange changes."

"IEEE Standard 802.12-1995, 13.2.4.5.1,
aNormalPriorityOctetsReceived."
::= { vgRptrMonPortEntry 13 }

vgRptrPortNormPriOctetRollovers OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS

"This object is a count of the number of
that the associated instance of
vgRptrPortNormPriorityOctets counter has
over

This two-counter mechanism is provided for
network management protocols that do not
64-bit counters (e.g. SNMPv1). Note
retrieval of these two counters in the same
is NOT guaranteed to be atomic

This counter may experience a discontinuity
the value of the corresponding instance
vgRptrPortLastChange changes."

"IEEE Standard 802.12-1995, 13.2.4.5.1,
aNormalPriorityOctetsReceived."

::= { vgRptrMonPortEntry 14 }

vgRptrPortHCNormPriorityOctets OBJECT-
SYNTAX Counter64
MAX-ACCESS read-
STATUS

"This object is a count of the number of
contained in normal priority frames that
been received on this port. This counter
incremented by OctetCount for each frame

Flick Standards Track [Page 40]

RFC 2266 IEEE 802.12 Repeater MIB January 1998

on this port which is counted
vgRptrPortNormPriorityFrames

This counter is a 64 bit version
vgRptrPortNormPriorityOctets. It should be
by Network Management protocols which
64 bit counters (e.g. SNMPv2).

This counter may experience a discontinuity
the value of the corresponding instance
vgRptrPortLastChange changes."

"IEEE Standard 802.12-1995, 13.2.4.5.1,
aNormalPriorityOctetsReceived."
::= { vgRptrMonPortEntry 15 }

vgRptrPortBroadcastFrames OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS

"This object is a count of broadcast packets
have been received on this port. This counter
incremented by one for each readable
received on this port whose destination
address is the broadcast address.
counted by this counter are also counted
vgRptrPortReadableFrames

This counter may experience a discontinuity
the value of the corresponding instance
vgRptrPortLastChange changes."

"IEEE Standard 802.12-1995, 13.2.4.5.1,
aBroadcastFramesReceived."
::= { vgRptrMonPortEntry 16 }

vgRptrPortMulticastFrames OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS

"This object is a count of multicast packets
have been received on this port. This counter
incremented by one for each readable
received on this port whose destination
address has the group address bit set, but is
the broadcast address. Frames counted by

Flick Standards Track [Page 41]

RFC 2266 IEEE 802.12 Repeater MIB January 1998

counter are also counted
vgRptrPortReadableFrames, but not
vgRptrPortBroadcastFrames. Note that when
value of the instance
for the repeater that this port is
with is equal to 'frameType88025', this
includes packets addressed to
addresses

This counter may experience a discontinuity
the value of the corresponding instance
vgRptrPortLastChange changes."

"IEEE Standard 802.12-1995, 13.2.4.5.1,
aMulticastFramesReceived."
::= { vgRptrMonPortEntry 17 }

vgRptrPortNullAddressedFrames OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS

"This object is a count of null addressed
that have been received on this port.
counter is incremented by one for each
received on this port with a destination
address consisting of all zero bits. Both
and training frames are included in
counter

This counter may experience a discontinuity
the value of the corresponding instance
vgRptrPortLastChange changes."

"IEEE Standard 802.12-1995, 13.2.4.5.1,
aNullAddressedFramesReceived."
::= { vgRptrMonPortEntry 18 }

vgRptrPortIPMFrames OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS

"This object is a count of the number of
that have been received on this port with
invalid packet marker and no PMI errors.
repeater will write an invalid packet marker
the end of a frame containing errors as it

Flick Standards Track [Page 42]

RFC 2266 IEEE 802.12 Repeater MIB January 1998

forwarded through the repeater to the
ports. This counter is incremented by one
each frame received on this port which has had
invalid packet marker added to the end of
frame

This counter indicates problems occurring in
domain of other repeaters, as opposed to
with cables or devices directly attached to
repeater

This counter may experience a discontinuity
the value of the corresponding instance
vgRptrPortLastChange changes."

"IEEE Standard 802.12-1995, 13.2.4.5.1,
aIPMFramesReceived."
::= { vgRptrMonPortEntry 19 }

vgRptrPortOversizeFrames OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS

"This object is a count of oversize
received on this port. This counter
incremented by one for each frame received
this port whose OctetCount is larger than
maximum legal frame size

The frame size which causes this counter
increment is dependent on the current value
vgRptrInfoCurrentFramingType for the repeater
the port is associated with.
vgRptrInfoCurrentFramingType is equal
frameType88023 this counter will increment
frames that are 1519 octets or larger.
vgRptrInfoCurrentFramingType is equal
frameType88025 this counter will increment
frames that are 4521 octets or larger

This counter may experience a discontinuity
the value of the corresponding instance
vgRptrPortLastChange changes."

"IEEE Standard 802.12-1995, 13.2.4.5.1,
aOversizeFramesReceived."
::= { vgRptrMonPortEntry 20 }

Flick Standards Track [Page 43]

RFC 2266 IEEE 802.12 Repeater MIB January 1998

vgRptrPortDataErrorFrames OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS

"This object is a count of errored
received on this port. This counter
incremented by one for each frame received
this port with any of the following errors:
FCS (with no IPM), PMI errors (excluding
with an IPM error as the only PMI error),
undersize (with no IPM). Does not
packets counted by vgRptrPortIPMFrames
vgRptrPortOversizeFrames,
vgRptrPortNullAddressedFrames

This counter indicates problems with cables
devices directly connected to this repeater,
vgRptrPortIPMFrames indicates problems
in the domain of other repeaters

This counter may experience a discontinuity
the value of the corresponding instance
vgRptrPortLastChange changes."

"IEEE Standard 802.12-1995, 13.2.4.5.1,
aDataErrorFramesReceived."
::= { vgRptrMonPortEntry 21 }

vgRptrPortPriorityPromotions OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS

"This counter is incremented by one each time
priority promotion timer has expired on this
and a normal priority frame is
promoted

This counter may experience a discontinuity
the value of the corresponding instance
vgRptrPortLastChange changes."

"IEEE Standard 802.12-1995, 13.2.4.5.1,
aPriorityPromotions."
::= { vgRptrMonPortEntry 22 }

vgRptrPortTransitionToTrainings OBJECT-

Flick Standards Track [Page 44]

RFC 2266 IEEE 802.12 Repeater MIB January 1998

SYNTAX Counter32
MAX-ACCESS read-
STATUS

"This counter is incremented by one each time
vgRptrPortStatus object for this port
into the 'training' state

This counter may experience a discontinuity
the value of the corresponding instance
vgRptrPortLastChange changes."

"IEEE Standard 802.12-1995, 13.2.4.5.1,
aTransitionsIntoTraining."
::= { vgRptrMonPortEntry 23 }

vgRptrPortLastChange OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS

"The value of sysUpTime when the last of
following occurred
1) the agent cold- or warm-started
2) the row for the port was
(such as when a device or module
added to the system);
3) any condition that would cause one
the counters for the row to
a discontinuity."
::= { vgRptrMonPortEntry 24 }

vgRptrAddrTrack OBJECT IDENTIFIER ::= { vgRptrObjects 3 }

OBJECT IDENTIFIER ::= { vgRptrAddrTrack 1 }

-- Currently

OBJECT IDENTIFIER ::= { vgRptrAddrTrack 2 }
-- Currently

OBJECT IDENTIFIER ::= { vgRptrAddrTrack 3 }

vgRptrAddrTrackTable OBJECT-

Flick Standards Track [Page 45]

RFC 2266 IEEE 802.12 Repeater MIB January 1998

SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS

"Table of address mapping information about
ports."
::= { vgRptrAddrTrackPort 1 }

vgRptrAddrTrackEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS

"An entry in the table, containing address
information about a single port."
INDEX { vgRptrGroupIndex, vgRptrPortIndex }
::= { vgRptrAddrTrackTable 1 }

VgRptrAddrTrackEntry ::=
SEQUENCE {
vgRptrAddrLastTrainedAddress OCTET STRING
vgRptrAddrTrainedAddrChanges Counter32,
vgRptrRptrDetectedDupAddress TruthValue
vgRptrMgrDetectedDupAddress
}

vgRptrAddrLastTrainedAddress OBJECT-
SYNTAX OCTET STRING (SIZE(0 | 6))
MAX-ACCESS read-
STATUS

"This object is the MAC address of the
station which succeeded in training on this port
A cascaded repeater may train using the
address. If no stations have succeeded
training on this port since the agent
monitoring the port activity, the agent
return a string of length zero."

"IEEE Standard 802.12-1995, 13.2.4.5.1,
aLastTrainedAddress."
::= { vgRptrAddrTrackEntry 1 }

vgRptrAddrTrainedAddrChanges OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS

Flick Standards Track [Page 46]

RFC 2266 IEEE 802.12 Repeater MIB January 1998

"This counter is incremented by one for each
that the vgRptrAddrLastTrainedAddress object
this port changes."

"IEEE Standard 802.12-1995, 13.2.4.5.1,
aTrainedAddressChanges."
::= { vgRptrAddrTrackEntry 2 }

vgRptrRptrDetectedDupAddress OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS

"This object is used to indicate that
repeater detected an error-free training frame
this port with a non-null source MAC address
matches the value of
of another active port in the same repeater.
is reset to 'false' when an error-free
frame is received with a non-null source
address which does not
vgRptrAddrLastTrainedAddress of another port
is active in the same repeater

For the cascade port, this object will be 'true
if the 'D' bit in the most recently
error-free training response frame was set
indicating the device at the other end of the
believes that this repeater's cascade port
using a duplicate address. This may be
the device at the other end of the link detected
duplicate address itself, or, if the other
is also a repeater, it could be
vgRptrMgrDetectedDupAddress was set to 'true'
the port that this repeater's cascade port
connected to."

"IEEE Standard 802.12-1995, 13.2.4.5.1,
aLocalRptrDetectedDupAddr."
::= { vgRptrAddrTrackEntry 3 }

vgRptrMgrDetectedDupAddress OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS

"This object can be set by a management

Flick Standards Track [Page 47]

RFC 2266 IEEE 802.12 Repeater MIB January 1998

when it detects that there is a duplicate
address. This object is OR'd
vgRptrRptrDetectedDupAddress to form the value
the 'D' bit in training response frames on
port

The purpose of this object is to provide a
for network management software to inform an
station that it is using a duplicate
address. Setting this object does not affect
current state of the link; the end station
not be informed of the duplicate address until
retrains for some reason. Note that
of its station address, the end station will
be able to train successfully until the
management software has set this object back
'false'. Although this object exists
cascade ports, it does not perform any
since this repeater is the initiator of
on a cascade port."

"IEEE Standard 802.12-1995, 13.2.4.5.1,
aCentralMgmtDetectedDupAddr."
::= { vgRptrAddrTrackEntry 4 }

vgRptrTraps OBJECT IDENTIFIER ::= { vgRptrMIB 2 }
vgRptrTrapPrefix OBJECT IDENTIFIER ::= { vgRptrTraps 0 }

vgRptrHealth NOTIFICATION-
OBJECTS { vgRptrInfoOperStatus }
STATUS

"A vgRptrHealth trap conveys information
to the operational state of a repeater. This
is sent when the value of an instance
vgRptrInfoOperStatus changes. The
trap is not sent as a result of powering up
repeater

The vgRptrHealth trap must contain the instance
the vgRptrInfoOperStatus object associated
the affected repeater

The agent must throttle the generation
consecutive vgRptrHealth traps so that there is
least a five-second gap between traps of
type. When traps are throttled, they are dropped

Flick Standards Track [Page 48]

RFC 2266 IEEE 802.12 Repeater MIB January 1998

not queued for sending at a future time. (
that 'generating' a trap means sending to
configured recipients.)"

"IEEE 802.12, Layer Management, 13.2.4.2.3,
nRepeaterHealth."
::= { vgRptrTrapPrefix 1 }

vgRptrResetEvent NOTIFICATION-
OBJECTS { vgRptrInfoOperStatus }
STATUS

"A vgRptrResetEvent trap conveys
related to the operational state of a repeater
This trap is sent on completion of a
reset action. A repeater reset action is
as a transition to its initial state as
in clause 12 [IEEE Std 802.12] when triggered
a management command

The vgRptrResetEvent trap is not sent when
agent restarts and sends an SNMP coldStart
warmStart trap

The vgRptrResetEvent trap must contain
instance of the vgRptrInfoOperStatus
associated with the affected repeater

The agent must throttle the generation
consecutive vgRptrResetEvent traps so that
is at least a five-second gap between traps
this type. When traps are throttled, they
dropped, not queued for sending at a future time
(Note that 'generating' a trap means sending
all configured recipients.)"

"IEEE 802.12, Layer Management, 13.2.4.2.3,
nRepeaterReset."
::= { vgRptrTrapPrefix 2 }

-- conformance

vgRptrConformance OBJECT IDENTIFIER ::= { vgRptrMIB 3 }

OBJECT IDENTIFIER ::= { vgRptrConformance 1 }

vgRptrGroups OBJECT IDENTIFIER ::= { vgRptrConformance 2 }

Flick Standards Track [Page 49]

RFC 2266 IEEE 802.12 Repeater MIB January 1998

-- compliance

vgRptrCompliance MODULE-
STATUS

"The compliance statement for managed 802.12
repeaters."

MODULE -- this
MANDATORY-GROUPS { vgRptrConfigGroup
vgRptrStatsGroup
vgRptrAddrGroup
vgRptrNotificationsGroup }

GROUP vgRptrStats64

"Implementation of this group is
for systems which can support Counter64."

OBJECT
MIN-ACCESS read-

"Write access to this object is not
in a repeater system that does not
configuration of framing types."

MODULE SNMP-REPEATER-
GROUP

"Implementation of this group is
for systems which have the
instrumentation to search all incoming
streams for a particular source MAC address."
::= { vgRptrCompliances 1 }

-- units of

vgRptrConfigGroup OBJECT-
OBJECTS {
vgRptrInfoMACAddress
vgRptrInfoCurrentFramingType
vgRptrInfoDesiredFramingType
vgRptrInfoFramingCapability
vgRptrInfoTrainingVersion
vgRptrInfoOperStatus
vgRptrInfoReset
vgRptrInfoLastChange
vgRptrGroupObjectID

Flick Standards Track [Page 50]

RFC 2266 IEEE 802.12 Repeater MIB January 1998

vgRptrGroupOperStatus
vgRptrGroupPortCapacity
vgRptrGroupCablesBundled
vgRptrPortType
vgRptrPortAdminStatus
vgRptrPortOperStatus
vgRptrPortSupportedPromiscMode
vgRptrPortSupportedCascadeMode
vgRptrPortAllowedTrainType
vgRptrPortLastTrainConfig
vgRptrPortTrainingResult
vgRptrPortPriorityEnable

}
STATUS

"A collection of objects for managing the
and configuration of IEEE 802.12 repeaters."
::= { vgRptrGroups 1 }

vgRptrStatsGroup OBJECT-
OBJECTS {
vgRptrMonTotalReadableFrames
vgRptrMonTotalReadableOctets
vgRptrMonReadableOctetRollovers
vgRptrMonTotalErrors
vgRptrPortReadableFrames
vgRptrPortReadableOctets
vgRptrPortReadOctetRollovers
vgRptrPortUnreadableOctets
vgRptrPortUnreadOctetRollovers
vgRptrPortHighPriorityFrames
vgRptrPortHighPriorityOctets
vgRptrPortHighPriOctetRollovers
vgRptrPortNormPriorityFrames
vgRptrPortNormPriorityOctets
vgRptrPortNormPriOctetRollovers
vgRptrPortBroadcastFrames
vgRptrPortMulticastFrames
vgRptrPortNullAddressedFrames
vgRptrPortIPMFrames
vgRptrPortOversizeFrames
vgRptrPortDataErrorFrames
vgRptrPortPriorityPromotions
vgRptrPortTransitionToTrainings

}
STATUS

Flick Standards Track [Page 51]

RFC 2266 IEEE 802.12 Repeater MIB January 1998

"A collection of objects for providing
for IEEE 802.12 repeaters. Systems which
Counter64 should also
vgRptrStats64Group."
::= { vgRptrGroups 2 }

vgRptrStats64Group OBJECT-
OBJECTS {
vgRptrMonHCTotalReadableOctets
vgRptrPortHCReadableOctets
vgRptrPortHCUnreadableOctets
vgRptrPortHCHighPriorityOctets

}
STATUS

"A collection of objects for providing
for IEEE 802.12 repeaters in a system
supports Counter64."
::= { vgRptrGroups 3 }

vgRptrAddrGroup OBJECT-
OBJECTS {
vgRptrAddrLastTrainedAddress
vgRptrAddrTrainedAddrChanges
vgRptrRptrDetectedDupAddress

}
STATUS

"A collection of objects for tracking
on IEEE 802.12 repeaters."
::= { vgRptrGroups 4 }

vgRptrNotificationsGroup NOTIFICATION-
NOTIFICATIONS {
vgRptrHealth

}
STATUS

"A collection of notifications used to
802.12 repeater general status changes."
::= { vgRptrGroups 5 }

Flick Standards Track [Page 52]

RFC 2266 IEEE 802.12 Repeater MIB January 1998

4.

This document was produced by the IETF 100VG-AnyLAN Working Group
whose efforts were greatly advanced by the contributions of
following people

Paul
Bob
Jeff
Karen
David
Jason
Kaj

This document is based on the work of IEEE 802.12.

5.

[1] Information processing systems - Open Systems Interconnection -
Specification of Abstract Syntax Notation One (ASN.1),
International Organization for Standardization.
Standard 8824 (December, 1987).

[2] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M.
S. Waldbusser, "Structure of Management Information for Version 2
of the Simple Network Management Protocol (SNMPv2)", RFC 1902,
January 1996.

[3] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M.
S. Waldbusser, "Textual Conventions for Version 2 of the
Network Management Protocol (SNMPv2)", RFC 1903, January 1996.

[4] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M.
S. Waldbusser, "Conformance Statements for Version 2 of
Simple Network Management Protocol (SNMPv2)", RFC 1904,
1996.

[5] McCloghrie, K. and M. Rose, "Management Information Base
Network Management of TCP/IP-based internets - MIB-II", STD 17,
RFC 1213, March 1991.

[6] IEEE, "Demand Priority Access Method, Physical Layer
Repeater Specifications for 100 Mb/s Operation", IEEE
802.12-1995"

Flick Standards Track [Page 53]

RFC 2266 IEEE 802.12 Repeater MIB January 1998

[7] de Graaf, K., D. Romascanu, D. McMaster, and K. McCloghrie
"Definitions of Managed Objects for IEEE 802.3 Repeater Devices",
RFC 2108, 3Com Corporation, Madge Networks (Israel) Ltd.,
Systems, Inc., February, 1997.

[8] McAnally, G., Gilbert, D. and J. Flick, "Conditional Grant
Rights to Specific Hewlett-Packard Patents In Conjunction
the Internet Engineering Task Force's Internet-Standard
Management Framework", RFC 1988, August 1996.

[9] Hewlett-Packard Company, US Patents 5,293,635 and 5,421,024.

6. Security

Certain management information defined in this MIB may be
sensitive in some network environments. Therefore, authentication
received SNMP requests and controlled access to
information should be employed in such environments. The method
this authentication is a function of the SNMP
Framework, and has not been expanded by this MIB

Several objects in the vgRptrConfigGroup allow write access.
these objects can have a serious effect on the operation of
network, including modifying the framing type of the network
resetting the repeater, enabling and disabling individual ports,
modifying the allowed capabilities of end stations attached to
port. It is recommended that implementers seriously consider
set operations should be allowed without providing, at a minimum
authentication of request origin

One particular object in this MIB, vgRptrPortAllowedTrainType,
considered significant for providing operational security in
802.12 network. It is recommended that network
configure this object to the 'allowEndNodesOnly' value on all
except ports which the administrator knows are attached to
repeaters or devices which require promiscuous receive
(bridges, switches, RMON probes, etc.). This will
unauthorized users from extending the network (by attaching
repeaters or bridges) without the administrator's knowledge, and
prevent unauthorized end nodes from listening promiscuously
network traffic

Flick Standards Track [Page 54]

RFC 2266 IEEE 802.12 Repeater MIB January 1998

7. Author's

John
Hewlett Packard
8000 Foothills Blvd. M/S 5556
Roseville, CA 95747-5556

Phone: +1 916 785 4018
Email: johnf@hprnd.rose.hp.

Flick Standards Track [Page 55]

RFC 2266 IEEE 802.12 Repeater MIB January 1998

8. Full Copyright

Copyright (C) The Internet Society (1998). All Rights Reserved

This document and translations of it may be copied and furnished
others, and derivative works that comment on or otherwise explain
or assist in its implementation may be prepared, copied,
and distributed, in whole or in part, without restriction of
kind, provided that the above copyright notice and this paragraph
included on all such copies and derivative works. However,
document itself may not be modified in any way, such as by
the copyright notice or references to the Internet Society or
Internet organizations, except as needed for the purpose
developing Internet standards in which case the procedures
copyrights defined in the Internet Standards process must
followed, or as required to translate it into languages other
English

The limited permissions granted above are perpetual and will not
revoked by the Internet Society or its successors or assigns

This document and the information contained herein is provided on
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED,
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE

Flick Standards Track [Page 56]

if you see any problems within the linking, don't worry be happy,
this is version 0.1 of the Relevance System and you gotta expect some crappy subroutines sometimes,
just be content we did not write this in Java, which would have made this "bigger and better" HAHAHHA.

RFC documents can be found at I.E.T.F.

Relevance System Copyright © 2002 Spectrum WorldResearch
other technical nosh by ServerMasters Corporation
collaboration of BobX