MIB Discovery
1930 modules enregistrés
Chemin
MIX : 1 (iso). 3 (org). 6 (dod). 1 (internet). 2 (mgmt). 1 (mib-2). 79 (ptopoMIB). 1 (ptopoMIBObjects). 3 (ptopoConfig). 1 (ptopoConfigTrapInterval)
OID : 1.3.6.1.2.1.79.1.3.1
TXT : iso. org. dod. internet. mgmt. mib-2. ptopoMIB. ptopoMIBObjects. ptopoConfig. ptopoConfigTrapInterval
Enfants
Pas d'enfants disponibles pour cet OID
Détails
OID1.3.6.1.2.1.79.1.3.1
Module PTOPO-MIB (CISCO)
NomptopoConfigTrapInterval
Accesreadwrite
Statuscurrent
DescriptionThis object controls the transmission of PTOPO notifications. If this object has a value of zero, then no ptopoConfigChange notifications will be transmitted by the agent. If this object has a non-zero value, then the agent must not generate more than one ptopoConfigChange trap-event in the indicated period, where a 'trap-event' is the transmission of a single notification PDU type to a list of notification destinations. If additional configuration changes occur within the indicated throttling period, then these trap- events must be suppressed by the agent. An NMS should periodically check the value of ptopoLastChangeTime to detect any missed ptopoConfigChange trap-events, e.g. due to throttling or transmission loss. If notification transmission is enabled, the suggested default throttling period is 60 seconds, but transmission should be disabled by default. If the agent is capable of storing non-volatile configuration, then the value of this object must be restored after a re-initialization of the management system.
Uniteseconds
SyntaxeInteger32
Module PTOPO-MIB (ietf)
NomptopoConfigTrapInterval
Accesreadwrite
Statuscurrent
DescriptionThis object controls the transmission of PTOPO notifications. If this object has a value of zero, then no ptopoConfigChange notifications will be transmitted by the agent. If this object has a non-zero value, then the agent must not generate more than one ptopoConfigChange trap-event in the indicated period, where a 'trap-event' is the transmission of a single notification PDU type to a list of notification destinations. If additional configuration changes occur within the indicated throttling period, then these trap- events must be suppressed by the agent. An NMS should periodically check the value of ptopoLastChangeTime to detect any missed ptopoConfigChange trap-events, e.g. due to throttling or transmission loss. If notification transmission is enabled, the suggested default throttling period is 60 seconds, but transmission should be disabled by default. If the agent is capable of storing non-volatile configuration, then the value of this object must be restored after a re-initialization of the management system.
Uniteseconds
SyntaxeInteger32