rptrInfoReset OBJECT-TYPE
SYNTAX INTEGER {
noReset(1),
reset(2)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Setting this object to reset(2) causes a
transition to the START state of Fig 9-2 in
section 9 [IEEE 802.3 Std] for a 10Mb/s repeater,
and to the START state of Fig 27-2 in section 27
of that standard for a 100Mb/s repeater.
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 to
reset(2), the agent is allowed to delay the reset
for a short period. For example, the implementor
may choose to delay the reset long enough to allow
the SNMP response to be transmitted. In any
event, the SNMP response must be transmitted.
This action does not reset the management counters
defined in this document nor does it affect the
portAdminStatus parameters. Included in this
action is the execution of a disruptive Self-Test
with the following characteristics: a) The nature
of the tests is not specified. b) The test resets
the repeater but without affecting management
information about the repeater. c) The test does
not inject packets onto any segment. d) Packets
received during the test may or may not be
transferred. e) The test does not interfere with
management functions.
After performing this self-test, the agent will
update the repeater health information (including
rptrInfoOperStatus), and send a rptrInfoResetEvent
notification."
REFERENCE
"[IEEE 802.3 Mgt], 30.4.1.2.1, acResetRepeater."
View at oid-info.com
Setting this object to reset(2) causes a
transition to the START state of Fig 9-2 in
section 9 [IEEE 802.3 Std] for a 10Mb/s repeater,
and to the START state of Fig 27-2 in section 27
of that standard for a 100Mb/s repeater.
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 to
reset(2), the agent is allowed to delay the reset
for a short period. For example, the implementor
may choose to delay the reset long enough to allow
the SNMP response to be transmitted. In any
event, the SNMP response must be transmitted.
This action does not reset the management counters
defined in this document nor does it affect the
portAdminStatus parameters. Included in this
action is the execution of a disruptive Self-Test
with the following characteristics: a) The nature
of the tests is not specified. b) The test resets
the repeater but without affecting management
information about the repeater. c) The test does
not inject packets onto any segment. d) Packets
received during the test may or may not be
transferred. e) The test does not interfere with
management functions.
After performing this self-test, the agent will
update the repeater health information (including
rptrInfoOperStatus), and send a rptrInfoResetEvent
notification.
Parsed from file rfc1516.mib.txt
Company: None
Module: SNMP-REPEATER-MIB
Setting this object to reset(2) causes a
transition to the START state of Fig 9-2 in
section 9 [IEEE 802.3 Std] for a 10Mb/s repeater,
and to the START state of Fig 27-2 in section 27
of that standard for a 100Mb/s repeater.
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 to
reset(2), the agent is allowed to delay the reset
for a short period. For example, the implementor
may choose to delay the reset long enough to allow
the SNMP response to be transmitted. In any
event, the SNMP response must be transmitted.
This action does not reset the management counters
defined in this document nor does it affect the
portAdminStatus parameters. Included in this
action is the execution of a disruptive Self-Test
with the following characteristics: a) The nature
of the tests is not specified. b) The test resets
the repeater but without affecting management
information about the repeater. c) The test does
not inject packets onto any segment. d) Packets
received during the test may or may not be
transferred. e) The test does not interfere with
management functions.
After performing this self-test, the agent will
update the repeater health information (including
rptrInfoOperStatus), and send a rptrInfoResetEvent
notification.
Parsed from file SNMP-REPEATER-MIB.mib
Module: SNMP-REPEATER-MIB
Automatically extracted from RFC2108
rptrInfoReset OBJECT-TYPE SYNTAX INTEGER { noReset(1), reset(2) } MAX-ACCESS read-write STATUS current DESCRIPTION "Setting this object to reset(2) causes a transition to the START state of Fig 9-2 in section 9 [IEEE 802.3 Std] for a 10Mb/s repeater, and to the START state of Fig 27-2 in section 27 of that standard for a 100Mb/s repeater. 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 to reset(2), the agent is allowed to delay the reset for a short period. For example, the implementor may choose to delay the reset long enough to allow the SNMP response to be transmitted. In any event, the SNMP response must be transmitted. This action does not reset the management counters defined in this document nor does it affect the portAdminStatus parameters. Included in this action is the execution of a disruptive Self-Test with the following characteristics: a) The nature of the tests is not specified. b) The test resets the repeater but without affecting management information about the repeater. c) The test does not inject packets onto any segment. d) Packets received during the test may or may not be transferred. e) The test does not interfere with management functions. After performing this self-test, the agent will update the repeater health information (including rptrInfoOperStatus), and send a rptrInfoResetEvent notification." REFERENCE "[IEEE 802.3 Mgt], 30.4.1.2.1, acResetRepeater." ::= { rptrInfoEntry 4 }
rptrInfoReset OBJECT-TYPE SYNTAX INTEGER { noReset(1), reset(2) } MAX-ACCESS read-write STATUS current DESCRIPTION "Setting this object to reset(2) causes a transition to the START state of Fig 9-2 in section 9 [IEEE 802.3 Std] for a 10Mb/s repeater, and to the START state of Fig 27-2 in section 27 of that standard for a 100Mb/s repeater. 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 to reset(2), the agent is allowed to delay the reset for a short period. For example, the implementor may choose to delay the reset long enough to allow the SNMP response to be transmitted. In any event, the SNMP response must be transmitted. This action does not reset the management counters defined in this document nor does it affect the portAdminStatus parameters. Included in this action is the execution of a disruptive Self-Test with the following characteristics: a) The nature of the tests is not specified. b) The test resets the repeater but without affecting management information about the repeater. c) The test does not inject packets onto any segment. d) Packets received during the test may or may not be transferred. e) The test does not interfere with management functions. After performing this self-test, the agent will update the repeater health information (including rptrInfoOperStatus), and send a rptrInfoResetEvent notification." REFERENCE "[IEEE 802.3 Mgt], 30.4.1.2.1, acResetRepeater." ::= { rptrInfoEntry 4 }
Internet Assigned Numbers Authority
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.2.1.22.1.4.1.1.1 | rptrInfoId | 0 | 0 | This object identifies the repeater for which this entry contains information. |
| 1.3.6.1.2.1.22.1.4.1.1.2 | rptrInfoRptrType | 0 | 0 | The rptrInfoRptrType returns a value that identifies the CSMA/CD repeater type. |
| 1.3.6.1.2.1.22.1.4.1.1.3 | rptrInfoOperStatus | 0 | 0 | The rptrInfoOperStatus object indicates the operational state of the repeater. |
| 1.3.6.1.2.1.22.1.4.1.1.5 | rptrInfoPartitionedPorts | 0 | 0 | This object returns the total number of ports in the repeater whose current state meets all three of the following criteria: rpt… |
| 1.3.6.1.2.1.22.1.4.1.1.6 | rptrInfoLastChange | 0 | 0 | The value of sysUpTime when any of the following conditions occurred: 1) agent cold- or warm-started; 2) this instance of repeater… |