Reference record for OID 1.3.6.1.4.1.9.9.42.1.2.18.1.7



parent
1.3.6.1.4.1.9.9.42.1.2.18.1 (rttMplsVpnMonReactEntry)
node code
7
node name
rttMplsVpnMonReactLpdRetryCount
dot oid
1.3.6.1.4.1.9.9.42.1.2.18.1.7
type
OBJECT-TYPE
asn1 oid
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) cisco(9) ciscoMgmt(9) ciscoRttMonMIB(42) ciscoRttMonObjects(1) rttMonCtrl(2) rttMplsVpnMonReactTable(18) rttMplsVpnMonReactEntry(1) rttMplsVpnMonReactLpdRetryCount(7)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) cisco(9) ciscoMgmt(9) ciscoRttMonMIB(42) ciscoRttMonObjects(1) rttMonCtrl(2) rttMplsVpnMonReactTable(18) rttMplsVpnMonReactEntry(1) rttMplsVpnMonReactLpdRetryCount(7)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) cisco(9) ciscoMgmt(9) ciscoRttMonMIB(42) ciscoRttMonObjects(1) rttMonCtrl(2) rttMplsVpnMonReactTable(18) rttMplsVpnMonReactEntry(1) rttMplsVpnMonReactLpdRetryCount(7)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) cisco(9) ciscoMgmt(9) ciscoRttMonMIB(42) ciscoRttMonObjects(1) rttMonCtrl(2) rttMplsVpnMonReactTable(18) rttMplsVpnMonReactEntry(1) rttMplsVpnMonReactLpdRetryCount(7)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) cisco(9) ciscoMgmt(9) ciscoRttMonMIB(42) ciscoRttMonObjects(1) rttMonCtrl(2) rttMplsVpnMonReactTable(18) rttMplsVpnMonReactEntry(1) rttMplsVpnMonReactLpdRetryCount(7)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) cisco(9) ciscoMgmt(9) ciscoRttMonMIB(42) ciscoRttMonObjects(1) rttMonCtrl(2) rttMplsVpnMonReactTable(18) rttMplsVpnMonReactEntry(1) rttMplsVpnMonReactLpdRetryCount(7)}
    • iri oid
  • /iso/identified-organization/dod/internet/private/enterprise/cisco/ciscoMgmt/ciscoRttMonMIB/ciscoRttMonObjects/rttMonCtrl/rttMplsVpnMonReactTable/rttMplsVpnMonReactEntry/rttMplsVpnMonReactLpdRetryCount
  • /iso/identified-organization/dod/internet/private/enterprises/cisco/ciscoMgmt/ciscoRttMonMIB/ciscoRttMonObjects/rttMonCtrl/rttMplsVpnMonReactTable/rttMplsVpnMonReactEntry/rttMplsVpnMonReactLpdRetryCount
  • /iso/org/dod/internet/private/enterprise/cisco/ciscoMgmt/ciscoRttMonMIB/ciscoRttMonObjects/rttMonCtrl/rttMplsVpnMonReactTable/rttMplsVpnMonReactEntry/rttMplsVpnMonReactLpdRetryCount
  • /iso/org/dod/internet/private/enterprises/cisco/ciscoMgmt/ciscoRttMonMIB/ciscoRttMonObjects/rttMonCtrl/rttMplsVpnMonReactTable/rttMplsVpnMonReactEntry/rttMplsVpnMonReactLpdRetryCount
  • /iso/iso-identified-organization/dod/internet/private/enterprise/cisco/ciscoMgmt/ciscoRttMonMIB/ciscoRttMonObjects/rttMonCtrl/rttMplsVpnMonReactTable/rttMplsVpnMonReactEntry/rttMplsVpnMonReactLpdRetryCount
  • /iso/iso-identified-organization/dod/internet/private/enterprises/cisco/ciscoMgmt/ciscoRttMonMIB/ciscoRttMonObjects/rttMonCtrl/rttMplsVpnMonReactTable/rttMplsVpnMonReactEntry/rttMplsVpnMonReactLpdRetryCount
    • iri by oid_info
    /ISO/Identified-Organization/6/1/4/1/9/9/42/1/2/18/1/7

    Description by circitor

    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.

    Parsed from file CISCO-RTTMON-MIB.mib
    Module: CISCO-RTTMON-MIB

    Description by cisco_v1

    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.

    Description by mibdepot

    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.

    Parsed from file cisco-rttmon.mib.txt
    Company: None
    Module: CISCO-RTTMON-MIB

    Description by cisco

    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.

    Information by circitor

    rttMplsVpnMonReactLpdRetryCount OBJECT-TYPE
    SYNTAX          Integer32 (1..16)
    UNITS           "attempts"
    MAX-ACCESS      read-create
    STATUS          current
    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."
    DEFVAL          { 1 } 
    ::= { rttMplsVpnMonReactEntry 7 }

    Information by cisco_v1

    rttMplsVpnMonReactLpdRetryCount OBJECT-TYPE
    SYNTAX INTEGER(1..16)


    ACCESS read-write
    STATUS mandatory
    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."
    DEFVAL { 1 }
    ::= { rttMplsVpnMonReactEntry 7 }

    Information by oid_info

    Vendor: Cisco
    Module: CISCO-RTTMON-MIB

    [Automatically extracted from oidview.com]

    Information by mibdepot

    rttMplsVpnMonReactLpdRetryCount OBJECT-TYPE
  SYNTAX      Integer32 (1..16)
  UNITS       "attempts"
  MAX-ACCESS  read-create
  STATUS      current
  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."
  DEFVAL      { 1 }
  ::= { rttMplsVpnMonReactEntry 7 }

    Information by cisco

    rttMplsVpnMonReactLpdRetryCount OBJECT-TYPE
    SYNTAX          Integer32 (1..16)
    UNITS           "attempts"
    MAX-ACCESS      read-create
    STATUS          current
    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."
    DEFVAL          { 1 } 
    ::= { rttMplsVpnMonReactEntry 7 }

    First Registration Authority (recovered by parent 1.3.6.1.4.1.9)

    Greg Satz

    Current Registration Authority (recovered by parent 1.3.6.1.4.1.9)

    Cisco Systems, Inc.

    Brothers (6)

    OIDNameSub childrenSub Nodes TotalDescription
    1.3.6.1.4.1.9.9.42.1.2.18.1.1 rttMplsVpnMonReactConnectionEnable 0 0 The value set for this will be applied as
    rttMonReactAdminConnectionEnable for individual probes created
    by the Auto SAA L3 MPLS …
    1.3.6.1.4.1.9.9.42.1.2.18.1.2 rttMplsVpnMonReactTimeoutEnable 0 0 The value set for this will be applied as
    rttMonReactAdminTimeoutEnable for individual probes created
    by the Auto SAA L3 MPLS VPN…
    1.3.6.1.4.1.9.9.42.1.2.18.1.3 rttMplsVpnMonReactThresholdType 0 0 The value corresponding to this object will be applied as
    rttMonReactAdminThresholdType for individual probes created by
    the Auto…
    1.3.6.1.4.1.9.9.42.1.2.18.1.4 rttMplsVpnMonReactThresholdCount 0 0 This object value will be applied as
    rttMonReactAdminThresholdCount for individual probes created by
    the Auto SAA L3 MPLS VPN.

    Thi…
    1.3.6.1.4.1.9.9.42.1.2.18.1.5 rttMplsVpnMonReactActionType 0 0 The value corresponding to this object will be applied as
    rttMonReactAdminActionType of individual probes created by
    this Auto SA…
    1.3.6.1.4.1.9.9.42.1.2.18.1.6 rttMplsVpnMonReactLpdNotifyType 0 0 This object specifies the type of LPD notifications to be
    generated for the current Auto SAA L3 MPLS VPN control row.

    This object…