Setting this object to reset(2) causes a
transition to the START state of Fig 9-2 in
section 9 [IEEE 802.3 Std].
Setting this object to noReset(1) has no effect.
The agent will always return the value noReset(1)
when this object is read.
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.
As a result of this action a chipRptrResetEvent trap
should be sent.
Parsed from file isd_mib.txt
Company: None
Module: CHIPCOMMIB
Setting this object to reset(2) causes a
transition to the START state of Fig 9-2 in
section 9 [IEEE 802.3 Std].
Setting this object to noReset(1) has no effect.
The agent will always return the value noReset(1)
when this object is read.
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.
As a result of this action a chipRptrResetEvent trap
should be sent.
Parsed from file CHIPCOMMIB.mib
Module: CHIPCOMMIB
Vendor: Chippcom
Module: CHIPCOMMIB
[Automatically extracted from oidview.com]
chipRptrReset OBJECT-TYPE SYNTAX INTEGER { noReset(1), reset(2) } ACCESS read-write STATUS mandatory 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]. Setting this object to noReset(1) has no effect. The agent will always return the value noReset(1) when this object is read. 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. As a result of this action a chipRptrResetEvent trap should be sent." REFERENCE "Reference IEEE 802.3 Rptr Mgt, 19.2.3.3, acResetRepeater." ::= { chipRptrRptrInfoEntry 6 }
chipRptrReset OBJECT-TYPE SYNTAX INTEGER { noReset(1), reset(2) } ACCESS read-write STATUS mandatory 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]. Setting this object to noReset(1) has no effect. The agent will always return the value noReset(1) when this object is read. 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. As a result of this action a chipRptrResetEvent trap should be sent." REFERENCE "Reference IEEE 802.3 Rptr Mgt, 19.2.3.3, acResetRepeater." ::= { chipRptrRptrInfoEntry 6 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.49.2.3.1.5.2.5.1.1.1.1.1 | chipRptrRptrInfoSlotIndex | 0 | 0 | The slot number of the repeater module on which the isolated network identified by chipRptrRptrInfoNetID resides. If chipRptrRptr… |
| 1.3.6.1.4.1.49.2.3.1.5.2.5.1.1.1.1.2 | chipRptrRptrInfoNetID | 0 | 0 | The network index that uniquely identifies this repeater. |
| 1.3.6.1.4.1.49.2.3.1.5.2.5.1.1.1.1.3 | chipRptrGroupCapacity | 0 | 0 | The chipRptrGroupCapacity is the number of groups that can be contained within the repeater. Within each managed repeater, the g… |
| 1.3.6.1.4.1.49.2.3.1.5.2.5.1.1.1.1.4 | chipRptrOperStatus | 0 | 0 | The chipRptrOperStatus object indicates the operational state of the repeater. The chipRptrHealthText object may be consulted fo… |
| 1.3.6.1.4.1.49.2.3.1.5.2.5.1.1.1.1.5 | chipRptrHealthText | 0 | 0 | chipRptrHealthtext |
| 1.3.6.1.4.1.49.2.3.1.5.2.5.1.1.1.1.7 | chipRptrNonDisruptTest | 0 | 0 | Setting this object to selfTest(2) causes the repeater to perform a agent-specific, non- disruptive self-test that has the follow… |
| 1.3.6.1.4.1.49.2.3.1.5.2.5.1.1.1.1.8 | chipRptrTotalPartitionedPorts | 0 | 0 | This object returns the total number of ports in the repeater whose current state meets all three of the following criteria: chi… |