wsCcStatsTrapCtrlConftable
View at oid-info.com
This table configures thresholds that can be monitored for:
- all MUs and/or
- all Portals and/or
- all WLANs and/or
- for the entire switch
When a given threshold is crossed, it generates the
appropriate corresponding notification, (ccSumStats_:
_MU, _Portal, _WLAN, or _Switch).
Some thresholds result in notifications when exceeded,
and some when the current value sinks below the
threshold. This is indicated by the wording of the
entry in the entry's _Descr value.
In all cases, the summary stat being monitored is the
Short value, never the Long value.
Note that for thresholds of type thresholdsAvgMuSignal &
thresholdsAvgMuNoise, the values being 'watched' are
actually negative. In these cases the threshold is
specified as a Unsigned32. For example, if you wish to
trap on Signal being worse than -75dBm, enter '70'. This
works since a user would never want to trap on a threshold
of Sinal worse than +10dBm. (SNR is not an issue, since
that is a positive value).
Any values reported as var-binds in the resultant trap(s)
are likewise reported as positive values.
Finally, since SNMP does not support decimals,
all the threshold values are 100 times their
actual values. So, a value of 563 means 5.63.
Likewise, when the user wants to set the
thresholds, he should set the value to 1000
for an actual value of 10.
Parsed from file WS-CC-STATS-MIB.mib.txt
Company: motorola
Module: WS-CC-STATS-MIB
Vendor: Motorola
Module: WS-CC-STATS-MIB (WS-CC-STATS-MIB.mib)
Type: TABLE
Access: not-accessible
Syntax: SEQUENCE OF
Automatically extracted from www.mibdepot.com
wsCcStatsTrapCtrlConfTable OBJECT-TYPE SYNTAX SEQUENCE OF WsCcStatsTrapCtrlConfEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table configures thresholds that can be monitored for: - all MUs and/or - all Portals and/or - all WLANs and/or - for the entire switch When a given threshold is crossed, it generates the appropriate corresponding notification, (ccSumStats_: _MU, _Portal, _WLAN, or _Switch). Some thresholds result in notifications when exceeded, and some when the current value sinks below the threshold. This is indicated by the wording of the entry in the entry's _Descr value. In all cases, the summary stat being monitored is the Short value, never the Long value. Note that for thresholds of type thresholdsAvgMuSignal & thresholdsAvgMuNoise, the values being 'watched' are actually negative. In these cases the threshold is specified as a Unsigned32. For example, if you wish to trap on Signal being worse than -75dBm, enter '70'. This works since a user would never want to trap on a threshold of Sinal worse than +10dBm. (SNR is not an issue, since that is a positive value). Any values reported as var-binds in the resultant trap(s) are likewise reported as positive values. Finally, since SNMP does not support decimals, all the threshold values are 100 times their actual values. So, a value of 563 means 5.63. Likewise, when the user wants to set the thresholds, he should set the value to 1000 for an actual value of 10." ::= { wsCcStatsTrapCtrlConf 1 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.388.14.3.3.1.5.1.1 | wsCcStatsTrapCtrlConfEntry | 11 | 11 | The rows/instances in this table occur at the exact same indices as the corresponding monitored data occurs in the _SumStats tabl… |
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.388.14.3.3.1.5.2 | wsCcStatsTrapCtrlConfMinPktsForTrap | 1 | 1 | This node IS NOT DESCRIBED YET |