MIB Discovery
1926 modules enregistr├ęs
Chemin
MIX : 1 (iso). 3 (org). 6 (dod). 1 (internet). 2 (mgmt). 1 (mib-2). 16 (rmon). 7 (filter). 2 (channelTable). 1 (channelEntry). 8 (channelEventStatus)
OID : 1.3.6.1.2.1.16.7.2.1.8
TXT : iso. org. dod. internet. mgmt. mib-2. rmon. filter. channelTable. channelEntry. channelEventStatus
Enfants
Pas d'enfants disponibles pour cet OID
D├ętails
OID1.3.6.1.2.1.16.7.2.1.8
Module RMON-MIB (CISCO)
NomchannelEventStatus
Accesreadwrite
Statuscurrent
DescriptionThe event status of this channel. If this channel is configured to generate events when packets are matched, a means of controlling the flow of those events is often needed. When this object is equal to eventReady(1), a single event may be generated, after which this object will be set by the probe to eventFired(2). While in the eventFired(2) state, no events will be generated until the object is modified to eventReady(1) (or eventAlwaysReady(3)). The management station can thus easily respond to a notification of an event by re-enabling this object. If the management station wishes to disable this flow control and allow events to be generated at will, this object may be set to eventAlwaysReady(3). Disabling the flow control is discouraged as it can result in high network traffic or other performance problems.
SyntaxeEnumeration (1-eventReady, 2-eventFired, 3-eventAlwaysReady)
Module RMON-MIB (DELL)
NomchannelEventStatus
Accesreadwrite
Statuscurrent
DescriptionThe event status of this channel. If this channel is configured to generate events when packets are matched, a means of controlling the flow of those events is often needed. When this object is equal to eventReady(1), a single event may be generated, after which this object will be set by the probe to eventFired(2). While in the eventFired(2) state, no events will be generated until the object is modified to eventReady(1) (or eventAlwaysReady(3)). The management station can thus easily respond to a notification of an event by re-enabling this object. If the management station wishes to disable this flow control and allow events to be generated at will, this object may be set to eventAlwaysReady(3). Disabling the flow control is discouraged as it can result in high network traffic or other performance problems.
SyntaxeEnumeration (1-eventReady, 2-eventFired, 3-eventAlwaysReady)
Module RFC1271-MIB (ietf)
NomchannelEventStatus
Accesreadwrite
Statusmandatory
DescriptionThe event status of this channel. If this channel is configured to generate events when packets are matched, a means of controlling the flow of those events is often needed. When this object is equal to eventReady(1), a single event may be generated, after which this object will be set by the probe to eventFired(2). While in the eventFired(2) state, no events will be generated until the object is modified to eventReady(1) (or eventAlwaysReady(3)). The management station can thus easily respond to a notification of an event by re-enabling this object. If the management station wishes to disable this flow control and allow events to be generated at will, this object may be set to eventAlwaysReady(3). Disabling the flow control is discouraged as it can result in high network traffic or other performance problems.
SyntaxeEnumeration (1-eventReady, 2-eventFired, 3-eventAlwaysReady)
Module RMON-MIB (ietf)
NomchannelEventStatus
Accesreadwrite
Statuscurrent
DescriptionThe event status of this channel. If this channel is configured to generate events when packets are matched, a means of controlling the flow of those events is often needed. When this object is equal to eventReady(1), a single event may be generated, after which this object will be set by the probe to eventFired(2). While in the eventFired(2) state, no events will be generated until the object is modified to eventReady(1) (or eventAlwaysReady(3)). The management station can thus easily respond to a notification of an event by re-enabling this object. If the management station wishes to disable this flow control and allow events to be generated at will, this object may be set to eventAlwaysReady(3). Disabling the flow control is discouraged as it can result in high network traffic or other performance problems.
SyntaxeEnumeration (1-eventReady, 2-eventFired, 3-eventAlwaysReady)
Module RMON-MIB (Alcatel)
NomchannelEventStatus
Accesreadwrite
Statuscurrent
DescriptionThe event status of this channel. If this channel is configured to generate events when packets are matched, a means of controlling the flow of those events is often needed. When this object is equal to eventReady(1), a single event may be generated, after which this object will be set by the probe to eventFired(2). While in the eventFired(2) state, no events will be generated until the object is modified to eventReady(1) (or eventAlwaysReady(3)). The management station can thus easily respond to a notification of an event by re-enabling this object. If the management station wishes to disable this flow control and allow events to be generated at will, this object may be set to eventAlwaysReady(3). Disabling the flow control is discouraged as it can result in high network traffic or other performance problems.
SyntaxeEnumeration (1-eventReady, 2-eventFired, 3-eventAlwaysReady)
Module RFC1271-MIB (Force10-9.14.2.1)
NomchannelEventStatus
Accesreadwrite
Statusmandatory
DescriptionThe event status of this channel. If this channel is configured to generate events when packets are matched, a means of controlling the flow of those events is often needed. When this object is equal to eventReady(1), a single event may be generated, after which this object will be set by the probe to eventFired(2). While in the eventFired(2) state, no events will be generated until the object is modified to eventReady(1) (or eventAlwaysReady(3)). The management station can thus easily respond to a notification of an event by re-enabling this object. If the management station wishes to disable this flow control and allow events to be generated at will, this object may be set to eventAlwaysReady(3). Disabling the flow control is discouraged as it can result in high network traffic or other performance problems.
SyntaxeEnumeration (1-eventReady, 2-eventFired, 3-eventAlwaysReady)
Module RMON-MIB (Force10-9.14.2.1)
NomchannelEventStatus
Accesreadwrite
Statuscurrent
DescriptionThe event status of this channel. If this channel is configured to generate events when packets are matched, a means of controlling the flow of those events is often needed. When this object is equal to eventReady(1), a single event may be generated, after which this object will be set by the probe to eventFired(2). While in the eventFired(2) state, no events will be generated until the object is modified to eventReady(1) (or eventAlwaysReady(3)). The management station can thus easily respond to a notification of an event by re-enabling this object. If the management station wishes to disable this flow control and allow events to be generated at will, this object may be set to eventAlwaysReady(3). Disabling the flow control is discouraged as it can result in high network traffic or other performance problems.
SyntaxeEnumeration (1-eventReady, 2-eventFired, 3-eventAlwaysReady)
Module RMON-MIB (FS)
NomchannelEventStatus
Accesreadwrite
Statuscurrent
DescriptionThe event status of this channel. If this channel is configured to generate events when packets are matched, a means of controlling the flow of those events is often needed. When this object is equal to eventReady(1), a single event may be generated, after which this object will be set by the probe to eventFired(2). While in the eventFired(2) state, no events will be generated until the object is modified to eventReady(1) (or eventAlwaysReady(3)). The management station can thus easily respond to a notification of an event by re-enabling this object. If the management station wishes to disable this flow control and allow events to be generated at will, this object may be set to eventAlwaysReady(3). Disabling the flow control is discouraged as it can result in high network traffic or other performance problems.
SyntaxeEnumeration (1-eventReady, 2-eventFired, 3-eventAlwaysReady)