The method of sampling the selected statistic and
calculating the value to be compared against
cnpdThresholdConfigRising or
cnpdThresholdConfigFalling thresholds.
If the value of this object is absoluteValue(1),
the value at the end of the sampling interval
cnpdThresholdConfigInterval, will be compared
with the cnpdThresholdConfigRising and
cnpdThresholdConfigFalling thresholds.
In this mode, when cnpdThresholdConfigStatsSelect is
byte or packet based, a maximum of two
cnpdThresholdHistory entries will be created per
application, as these byte and packet counts
monotonically increase from zero.
If the value of this object is deltaValue(2),
the difference between the samples at the
beginning and end of the cnpdThresholdConfigInterval
will be compared with the cnpdThresholdConfigRising
and cnpdThresholdConfigFalling thresholds.
Because the difference in the previous and current
samples are compared over the sample period
cnpdThresholdConfigInterval, this mode provides
more granularity to the thresholds because the NMS
is now provided with the gradient or change in the
cnpdThresholdConfigStatsSelect.
Note that even though the sample value is monotonically
increasing for byte and packet counts,
cnpdThresholdConfigSampleType set to deltaValue, can
generate falling cnpdThresholdHistory entries, because
the gradient can be lower than the
cnpdThresholdConfigFalling value.
Parsed from file CISCO-NBAR-PROTOCOL-DISCOVERY-MIB.mib
Module: CISCO-NBAR-PROTOCOL-DISCOVERY-MIB
The method of sampling the selected statistic and
calculating the value to be compared against
cnpdThresholdConfigRising or
cnpdThresholdConfigFalling thresholds.
If the value of this object is absoluteValue(1),
the value at the end of the sampling interval
cnpdThresholdConfigInterval, will be compared
with the cnpdThresholdConfigRising and
cnpdThresholdConfigFalling thresholds.
In this mode, when cnpdThresholdConfigStatsSelect is
byte or packet based, a maximum of two
cnpdThresholdHistory entries will be created per
application, as these byte and packet counts
monotonically increase from zero.
If the value of this object is deltaValue(2),
the difference between the samples at the
beginning and end of the cnpdThresholdConfigInterval
will be compared with the cnpdThresholdConfigRising
and cnpdThresholdConfigFalling thresholds.
Because the difference in the previous and current
samples are compared over the sample period
cnpdThresholdConfigInterval, this mode provides
more granularity to the thresholds because the NMS
is now provided with the gradient or change in the
cnpdThresholdConfigStatsSelect.
Note that even though the sample value is monotonically
increasing for byte and packet counts,
cnpdThresholdConfigSampleType set to deltaValue, can
generate falling cnpdThresholdHistory entries, because
the gradient can be lower than the
cnpdThresholdConfigFalling value.
The method of sampling the selected statistic and
calculating the value to be compared against
cnpdThresholdConfigRising or
cnpdThresholdConfigFalling thresholds.
If the value of this object is absoluteValue(1),
the value at the end of the sampling interval
cnpdThresholdConfigInterval, will be compared
with the cnpdThresholdConfigRising and
cnpdThresholdConfigFalling thresholds.
In this mode, when cnpdThresholdConfigStatsSelect is
byte or packet based, a maximum of two
cnpdThresholdHistory entries will be created per
application, as these byte and packet counts
monotonically increase from zero.
If the value of this object is deltaValue(2),
the difference between the samples at the
beginning and end of the cnpdThresholdConfigInterval
will be compared with the cnpdThresholdConfigRising
and cnpdThresholdConfigFalling thresholds.
Because the difference in the previous and current
samples are compared over the sample period
cnpdThresholdConfigInterval, this mode provides
more granularity to the thresholds because the NMS
is now provided with the gradient or change in the
cnpdThresholdConfigStatsSelect.
Note that even though the sample value is monotonically
increasing for byte and packet counts,
cnpdThresholdConfigSampleType set to deltaValue, can
generate falling cnpdThresholdHistory entries, because
the gradient can be lower than the
cnpdThresholdConfigFalling value.
Parsed from file CISCO-NBAR-PROTOCOL-DISCOVERY-MIB.my.txt
Company: None
Module: CISCO-NBAR-PROTOCOL-DISCOVERY-MIB
The method of sampling the selected statistic and
calculating the value to be compared against
cnpdThresholdConfigRising or
cnpdThresholdConfigFalling thresholds.
If the value of this object is absoluteValue(1),
the value at the end of the sampling interval
cnpdThresholdConfigInterval, will be compared
with the cnpdThresholdConfigRising and
cnpdThresholdConfigFalling thresholds.
In this mode, when cnpdThresholdConfigStatsSelect is
byte or packet based, a maximum of two
cnpdThresholdHistory entries will be created per
application, as these byte and packet counts
monotonically increase from zero.
If the value of this object is deltaValue(2),
the difference between the samples at the
beginning and end of the cnpdThresholdConfigInterval
will be compared with the cnpdThresholdConfigRising
and cnpdThresholdConfigFalling thresholds.
Because the difference in the previous and current
samples are compared over the sample period
cnpdThresholdConfigInterval, this mode provides
more granularity to the thresholds because the NMS
is now provided with the gradient or change in the
cnpdThresholdConfigStatsSelect.
Note that even though the sample value is monotonically
increasing for byte and packet counts,
cnpdThresholdConfigSampleType set to deltaValue, can
generate falling cnpdThresholdHistory entries, because
the gradient can be lower than the
cnpdThresholdConfigFalling value.
cnpdThresholdConfigSampleType OBJECT-TYPE SYNTAX INTEGER { absoluteValue (1), deltaValue (2) } MAX-ACCESS read-create STATUS current DESCRIPTION "The method of sampling the selected statistic and calculating the value to be compared against cnpdThresholdConfigRising or cnpdThresholdConfigFalling thresholds. If the value of this object is absoluteValue(1), the value at the end of the sampling interval cnpdThresholdConfigInterval, will be compared with the cnpdThresholdConfigRising and cnpdThresholdConfigFalling thresholds. In this mode, when cnpdThresholdConfigStatsSelect is byte or packet based, a maximum of two cnpdThresholdHistory entries will be created per application, as these byte and packet counts monotonically increase from zero. If the value of this object is deltaValue(2), the difference between the samples at the beginning and end of the cnpdThresholdConfigInterval will be compared with the cnpdThresholdConfigRising and cnpdThresholdConfigFalling thresholds. Because the difference in the previous and current samples are compared over the sample period cnpdThresholdConfigInterval, this mode provides more granularity to the thresholds because the NMS is now provided with the gradient or change in the cnpdThresholdConfigStatsSelect. Note that even though the sample value is monotonically increasing for byte and packet counts, cnpdThresholdConfigSampleType set to deltaValue, can generate falling cnpdThresholdHistory entries, because the gradient can be lower than the cnpdThresholdConfigFalling value." DEFVAL { absoluteValue } ::= { cnpdThresholdConfigEntry 4 }
cnpdThresholdConfigSampleType OBJECT-TYPE SYNTAX INTEGER { absoluteValue(1), deltaValue(2) } ACCESS read-write STATUS mandatory DESCRIPTION "The method of sampling the selected statistic and calculating the value to be compared against cnpdThresholdConfigRising or cnpdThresholdConfigFalling thresholds. If the value of this object is absoluteValue(1), the value at the end of the sampling interval cnpdThresholdConfigInterval, will be compared with the cnpdThresholdConfigRising and cnpdThresholdConfigFalling thresholds. In this mode, when cnpdThresholdConfigStatsSelect is byte or packet based, a maximum of two cnpdThresholdHistory entries will be created per application, as these byte and packet counts monotonically increase from zero. If the value of this object is deltaValue(2), the difference between the samples at the beginning and end of the cnpdThresholdConfigInterval will be compared with the cnpdThresholdConfigRising and cnpdThresholdConfigFalling thresholds. Because the difference in the previous and current samples are compared over the sample period cnpdThresholdConfigInterval, this mode provides more granularity to the thresholds because the NMS is now provided with the gradient or change in the cnpdThresholdConfigStatsSelect. Note that even though the sample value is monotonically increasing for byte and packet counts, cnpdThresholdConfigSampleType set to deltaValue, can generate falling cnpdThresholdHistory entries, because the gradient can be lower than the cnpdThresholdConfigFalling value." DEFVAL { absoluteValue } ::= { cnpdThresholdConfigEntry 4 }
Vendor: Cisco
Module: CISCO-NBAR-PROTOCOL-DISCOVERY-MIB
[Automatically extracted from oidview.com]
cnpdThresholdConfigSampleType OBJECT-TYPE SYNTAX INTEGER { absoluteValue (1), deltaValue (2) } MAX-ACCESS read-create STATUS current DESCRIPTION "The method of sampling the selected statistic and calculating the value to be compared against cnpdThresholdConfigRising or cnpdThresholdConfigFalling thresholds. If the value of this object is absoluteValue(1), the value at the end of the sampling interval cnpdThresholdConfigInterval, will be compared with the cnpdThresholdConfigRising and cnpdThresholdConfigFalling thresholds. In this mode, when cnpdThresholdConfigStatsSelect is byte or packet based, a maximum of two cnpdThresholdHistory entries will be created per application, as these byte and packet counts monotonically increase from zero. If the value of this object is deltaValue(2), the difference between the samples at the beginning and end of the cnpdThresholdConfigInterval will be compared with the cnpdThresholdConfigRising and cnpdThresholdConfigFalling thresholds. Because the difference in the previous and current samples are compared over the sample period cnpdThresholdConfigInterval, this mode provides more granularity to the thresholds because the NMS is now provided with the gradient or change in the cnpdThresholdConfigStatsSelect. Note that even though the sample value is monotonically increasing for byte and packet counts, cnpdThresholdConfigSampleType set to deltaValue, can generate falling cnpdThresholdHistory entries, because the gradient can be lower than the cnpdThresholdConfigFalling value." DEFVAL { absoluteValue } ::= { cnpdThresholdConfigEntry 4 }
cnpdThresholdConfigSampleType OBJECT-TYPE SYNTAX INTEGER { absoluteValue (1), deltaValue (2) } MAX-ACCESS read-create STATUS current DESCRIPTION "The method of sampling the selected statistic and calculating the value to be compared against cnpdThresholdConfigRising or cnpdThresholdConfigFalling thresholds. If the value of this object is absoluteValue(1), the value at the end of the sampling interval cnpdThresholdConfigInterval, will be compared with the cnpdThresholdConfigRising and cnpdThresholdConfigFalling thresholds. In this mode, when cnpdThresholdConfigStatsSelect is byte or packet based, a maximum of two cnpdThresholdHistory entries will be created per application, as these byte and packet counts monotonically increase from zero. If the value of this object is deltaValue(2), the difference between the samples at the beginning and end of the cnpdThresholdConfigInterval will be compared with the cnpdThresholdConfigRising and cnpdThresholdConfigFalling thresholds. Because the difference in the previous and current samples are compared over the sample period cnpdThresholdConfigInterval, this mode provides more granularity to the thresholds because the NMS is now provided with the gradient or change in the cnpdThresholdConfigStatsSelect. Note that even though the sample value is monotonically increasing for byte and packet counts, cnpdThresholdConfigSampleType set to deltaValue, can generate falling cnpdThresholdHistory entries, because the gradient can be lower than the cnpdThresholdConfigFalling value." DEFVAL { absoluteValue } ::= { cnpdThresholdConfigEntry 4 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.9.9.244.1.5.1.1.1 | cnpdThresholdConfigIndex | 0 | 0 | A monotonically increasing integer which uniquely identifies an entry in the cnpdThresholdConfigTable. |
| 1.3.6.1.4.1.9.9.244.1.5.1.1.2 | cnpdThresholdConfigIfIndex | 0 | 0 | This object allows the management station to select the interface, which Protocol Discovery is running on, to be used to create t… |
| 1.3.6.1.4.1.9.9.244.1.5.1.1.3 | cnpdThresholdConfigInterval | 0 | 0 | The interval in seconds over which the data is sampled and compared with cnpdThresholdConfigRising and cnpdThresholdConfigFalling… |
| 1.3.6.1.4.1.9.9.244.1.5.1.1.5 | cnpdThresholdConfigProtocol | 0 | 0 | The application or protocol which the management station wishes to configure a threshold on. This object is an index into the Suppo… |
| 1.3.6.1.4.1.9.9.244.1.5.1.1.6 | cnpdThresholdConfigProtocolAny | 0 | 0 | If set to 'true' - this threshold is configured to check for any protocol which meets the threshold criteria. This means that mul… |
| 1.3.6.1.4.1.9.9.244.1.5.1.1.7 | cnpdThresholdConfigStatsSelect | 0 | 0 | This object allows the management station to select the statistic used to base the threshold on. For example a cnpdThresholdConfig… |
| 1.3.6.1.4.1.9.9.244.1.5.1.1.8 | cnpdThresholdConfigStartup | 0 | 0 | This controls the type of notification that is sent when this threshold entry is first enabled. Because there is no previous sam… |
| 1.3.6.1.4.1.9.9.244.1.5.1.1.9 | cnpdThresholdConfigRising | 0 | 0 | This is the threshold object which the managment station sets to determine if it gets breached. It indicates the statistic being … |
| 1.3.6.1.4.1.9.9.244.1.5.1.1.10 | cnpdThresholdConfigFalling | 0 | 0 | This is the threshold object which the management station sets to determine if it gets breached. It indicates the statistic being… |
| 1.3.6.1.4.1.9.9.244.1.5.1.1.12 | cnpdThresholdConfigStatus | 0 | 0 | This object is used to create or delete the row entry in cnpdThresholdConfigTable. When creating a row entry the management stat… |