MIB Discovery
1930 modules enregistr├ęs
Chemin
MIX : 1 (iso). 3 (org). 6 (dod). 1 (internet). 2 (mgmt). 1 (mib-2). 88 (dismanEventMIB). 1 (dismanEventMIBObjects). 2 (mteTrigger). 2 (mteTriggerTable). 1 (mteTriggerEntry). 6 (mteTriggerValueID)
OID : 1.3.6.1.2.1.88.1.2.2.1.6
TXT : iso. org. dod. internet. mgmt. mib-2. dismanEventMIB. dismanEventMIBObjects. mteTrigger. mteTriggerTable. mteTriggerEntry. mteTriggerValueID
Enfants
Pas d'enfants disponibles pour cet OID
D├ętails
OID1.3.6.1.2.1.88.1.2.2.1.6
Module DISMAN-EVENT-MIB (CISCO)
NommteTriggerValueID
Accesreadwrite
Statuscurrent
DescriptionThe object identifier of the MIB object to sample to see if the trigger should fire. This may be wildcarded by truncating all or part of the instance portion, in which case the value is obtained as if with a GetNext function, checking multiple values if they exist. If such wildcarding is applied, mteTriggerValueIDWildcard must be 'true' and if not it must be 'false'. Bad object identifiers or a mismatch between truncating the identifier and the value of mteTriggerValueIDWildcard result in operation as one would expect when providing the wrong identifier to a Get or GetNext operation. The Get will fail or get the wrong object. The GetNext will indeed get whatever is next, proceeding until it runs past the initial part of the identifier and perhaps many unintended objects for confusing results. If the value syntax of those objects is not usable, that results in a 'badType' error that terminates the scan. Each instance that fills the wildcard is independent of any additional instances, that is, wildcarded objects operate as if there were a separate table entry for each instance that fills the wildcard without having to actually predict all possible instances ahead of time.
SyntaxeObjectIdentifier
Module DISMAN-EVENT-MIB (ietf)
NommteTriggerValueID
Accesreadwrite
Statuscurrent
DescriptionThe object identifier of the MIB object to sample to see if the trigger should fire. This may be wildcarded by truncating all or part of the instance portion, in which case the value is obtained as if with a GetNext function, checking multiple values if they exist. If such wildcarding is applied, mteTriggerValueIDWildcard must be 'true' and if not it must be 'false'. Bad object identifiers or a mismatch between truncating the identifier and the value of mteTriggerValueIDWildcard result in operation as one would expect when providing the wrong identifier to a Get or GetNext operation. The Get will fail or get the wrong object. The GetNext will indeed get whatever is next, proceeding until it runs past the initial part of the identifier and perhaps many unintended objects for confusing results. If the value syntax of those objects is not usable, that results in a 'badType' error that terminates the scan. Each instance that fills the wildcard is independent of any additional instances, that is, wildcarded objects operate as if there were a separate table entry for each instance that fills the wildcard without having to actually predict all possible instances ahead of time.
SyntaxeObjectIdentifier