All MIBs › CISCO-RTTMON-MIB › rttMplsVpnMonReactLpdRetryCount
rttMplsVpnMonReactLpdRetryCount
Module: CISCO-RTTMON-MIB
OID (symbolic): CISCO-RTTMON-MIB::rttMplsVpnMonReactLpdRetryCount
OID (numeric): 1.3.6.1.4.1.9.9.42.1.2.18.1.7
Node type: OBJECT-TYPE
Type: Integer32
Access: read-create
Description:
This object value specifies the number of attempts to be performed before declaring the path as 'down'. Each 'single probe' which is part of 'lspGroup' probe will be retried these many times before marking it as 'down'.
This object will be applicable only when LSP Path Discovery is enabled for this row.
- When rttMplsVpnMonTypeSecFreqType is not configured, the failure count will be incremented at the next cycle of 'lspGroup' probe at interval's of rttMplsVpnMonScheduleFrequency value.
For example: Assume there are 10 paths discovered and on the first run of the 'lspGroup' probe first two paths failed and rest passed. On the second run all the probes will be run again. The probes 1 and 2 will be retried till the rttMplsVpnMonReactLpdRetryCount value, and then marked as 'down' and rttMonLpdGrpStatusNotification will be sent if configured.
- When rttMplsVpnMonTypeSecFreqType value is anything other than 'none', the retry will happen for the failed probes at the rttMplsVpnMonTypeSecFreqValue and only the failed probes will be retried.
For example: Assume there are 10 paths discovered and on the first run of the 'lspGroup' probe first two paths failed and rest passed. The secondary frequency will be applied to the failed probes. At secondary frequency interval the first two probes will be run again. The probes 1 and 2 will be retried till the rttMplsVpnMonReactLpdRetryCount value, and then marked as 'down' and rttMonLpdGrpStatusNotification will be sent if configured.
What is rttMplsVpnMonReactLpdRetryCount?
This object specifies the number of probe retry attempts before declaring an MPLS LSP (Label Switched Path) as down during path discovery operations. It controls how many times a single probe within an LSP group will be retried after failure. An operator would configure this to balance fast failure detection against tolerance for intermittent network issues in MPLS VPN monitoring.
OID Breakdown
| Numeric OID | Name | Module |
|---|---|---|
| 1 | iso | LANART-AGENT |
| 1.3 | org | BIANCA-BRICK-PPP-MIB |
| 1.3.6 | dod | BIANCA-BRICK-PPP-MIB |
| 1.3.6.1 | internet | BIANCA-BRICK-PPP-MIB |
| 1.3.6.1.4 | private | BIANCA-BRICK-PPP-MIB |
| 1.3.6.1.4.1 | enterprises | ANIROOT-MIB |
| 1.3.6.1.4.1.9 | cisco | CISCO-SMI |
| 1.3.6.1.4.1.9.9 | ciscoMgmt | CISCO-SMI |
| 1.3.6.1.4.1.9.9.42 | ciscoRttMonMIB | CISCO-RTTMON-MIB |
| 1.3.6.1.4.1.9.9.42.1 | ciscoRttMonObjects | CISCO-RTTMON-MIB |
| 1.3.6.1.4.1.9.9.42.1.2 | rttMonCtrl | CISCO-RTTMON-MIB |
| 1.3.6.1.4.1.9.9.42.1.2.18 | rttMplsVpnMonReactTable | CISCO-RTTMON-MIB |
| 1.3.6.1.4.1.9.9.42.1.2.18.1 | rttMplsVpnMonReactEntry | CISCO-RTTMON-MIB |
| 1.3.6.1.4.1.9.9.42.1.2.18.1.7 | rttMplsVpnMonReactLpdRetryCount | CISCO-RTTMON-MIB |