In OSCP, some hello packets are generated periodically
while others are triggered by events. Specifically,
event-triggered hellos are sent upon every state change
(except 'oneWay' to 'twoWay') and when a change occurs in
the bundle identifier. To avoid potential system
misbehavior in which hello packets would be triggered in
an uncontrolled fashion, a hello hold down timer is
introduced that prevents successive event-triggered hellos
from being sent in too short a time interval.
This object contains the minimum time between (triggered)
hellos.
This value must be smaller than 75% of the value of
coscpHelloInterval.
Parsed from file CISCO-OSCP-MIB.mib
Module: CISCO-OSCP-MIB
In OSCP, some hello packets are generated periodically
while others are triggered by events. Specifically,
event-triggered hellos are sent upon every state change
(except 'oneWay' to 'twoWay') and when a change occurs in
the bundle identifier. To avoid potential system
misbehavior in which hello packets would be triggered in
an uncontrolled fashion, a hello hold down timer is
introduced that prevents successive event-triggered hellos
from being sent in too short a time interval.
This object contains the minimum time between (triggered)
hellos.
This value must be smaller than 75% of the value of
coscpHelloInterval.
In OSCP, some hello packets are generated periodically
while others are triggered by events. Specifically,
event-triggered hellos are sent upon every state change
(except 'oneWay' to 'twoWay') and when a change occurs in
the bundle identifier. To avoid potential system
misbehavior in which hello packets would be triggered in
an uncontrolled fashion, a hello hold down timer is
introduced that prevents successive event-triggered hellos
from being sent in too short a time interval.
This object contains the minimum time between (triggered)
hellos.
This value must be smaller than 75% of the value of
coscpHelloInterval.
Parsed from file CISCO-OSCP-MIB.my.txt
Company: None
Module: CISCO-OSCP-MIB
In OSCP, some hello packets are generated periodically
while others are triggered by events. Specifically,
event-triggered hellos are sent upon every state change
(except 'oneWay' to 'twoWay') and when a change occurs in
the bundle identifier. To avoid potential system
misbehavior in which hello packets would be triggered in
an uncontrolled fashion, a hello hold down timer is
introduced that prevents successive event-triggered hellos
from being sent in too short a time interval.
This object contains the minimum time between (triggered)
hellos.
This value must be smaller than 75% of the value of
coscpHelloInterval.
coscpHelloHoldDown OBJECT-TYPE SYNTAX Unsigned32 (100..10000) UNITS "milliseconds" MAX-ACCESS read-write STATUS current DESCRIPTION "In OSCP, some hello packets are generated periodically while others are triggered by events. Specifically, event-triggered hellos are sent upon every state change (except 'oneWay' to 'twoWay') and when a change occurs in the bundle identifier. To avoid potential system misbehavior in which hello packets would be triggered in an uncontrolled fashion, a hello hold down timer is introduced that prevents successive event-triggered hellos from being sent in too short a time interval. This object contains the minimum time between (triggered) hellos. This value must be smaller than 75% of the value of coscpHelloInterval." DEFVAL { 100 } ::= { ciscoOscpBaseGroup 5 }
coscpHelloHoldDown OBJECT-TYPE SYNTAX Gauge(100..10000) ACCESS read-write STATUS mandatory DESCRIPTION "In OSCP, some hello packets are generated periodically while others are triggered by events. Specifically, event-triggered hellos are sent upon every state change (except 'oneWay' to 'twoWay') and when a change occurs in the bundle identifier. To avoid potential system misbehavior in which hello packets would be triggered in an uncontrolled fashion, a hello hold down timer is introduced that prevents successive event-triggered hellos from being sent in too short a time interval. This object contains the minimum time between (triggered) hellos. This value must be smaller than 75% of the value of coscpHelloInterval." DEFVAL { 100 } ::= { ciscoOscpBaseGroup 5 }
Vendor: Cisco
Module: CISCO-OSCP-MIB
[Automatically extracted from oidview.com]
coscpHelloHoldDown OBJECT-TYPE SYNTAX Unsigned32 (100..10000) UNITS "milliseconds" MAX-ACCESS read-write STATUS current DESCRIPTION "In OSCP, some hello packets are generated periodically while others are triggered by events. Specifically, event-triggered hellos are sent upon every state change (except 'oneWay' to 'twoWay') and when a change occurs in the bundle identifier. To avoid potential system misbehavior in which hello packets would be triggered in an uncontrolled fashion, a hello hold down timer is introduced that prevents successive event-triggered hellos from being sent in too short a time interval. This object contains the minimum time between (triggered) hellos. This value must be smaller than 75% of the value of coscpHelloInterval." DEFVAL { 100 } ::= { ciscoOscpBaseGroup 5 }
coscpHelloHoldDown OBJECT-TYPE SYNTAX Unsigned32 (100..10000) UNITS "milliseconds" MAX-ACCESS read-write STATUS current DESCRIPTION "In OSCP, some hello packets are generated periodically while others are triggered by events. Specifically, event-triggered hellos are sent upon every state change (except 'oneWay' to 'twoWay') and when a change occurs in the bundle identifier. To avoid potential system misbehavior in which hello packets would be triggered in an uncontrolled fashion, a hello hold down timer is introduced that prevents successive event-triggered hellos from being sent in too short a time interval. This object contains the minimum time between (triggered) hellos. This value must be smaller than 75% of the value of coscpHelloInterval." DEFVAL { 100 } ::= { ciscoOscpBaseGroup 5 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.9.9.202.1.1.5.0 | coscpHelloHoldDown | 0 | 0 | None |
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.9.9.202.1.1.1 | coscpHighestVersion | 1 | 1 | The highest version of OSCP that the software in this switch is capable of executing. If the version of a received hello packet i… |
| 1.3.6.1.4.1.9.9.202.1.1.2 | coscpLowestVersion | 1 | 1 | The lowest version of OSCP that the software in this switch is capable of executing. If the version of a received hello packet is… |
| 1.3.6.1.4.1.9.9.202.1.1.3 | coscpSwitchId | 1 | 1 | The value this switch is using to represent itself as a network node. This should be a globally unique identifier. Typically this… |
| 1.3.6.1.4.1.9.9.202.1.1.4 | coscpPriorityChangeMode | 1 | 1 | This value defines how OSCP will react to a change in the configured value of coscpLinkSelPriority. If the value is set to 'immed… |
| 1.3.6.1.4.1.9.9.202.1.1.6 | coscpHelloInterval | 1 | 1 | The average time interval between successive hellos sent by this switch on each link running OSCP, in the absence of triggered he… |
| 1.3.6.1.4.1.9.9.202.1.1.7 | coscpHelloInactivityFactor | 1 | 1 | The value for the Hello Inactivity factor that this switch will use to determine when a link has gone down. A link will be return… |
| 1.3.6.1.4.1.9.9.202.1.1.8 | coscpNotifiesEnabled | 1 | 1 | Notifications that OSCP has gone down on a link are enabled if this value is set to 'true'. |