OID reference

dcLmpProductExtendedHelloDeadIvl

1.3.6.1.4.1.629.10.5.1.1.1.33

Description

When set to a non-zero value greater than lmpCcHelloDeadIntervalNegotiated, the object overrides the value of lmpCcHelloDeadIntervalNegotiated for a control channel to indicate how long the device should wait (in milliseconds) before declaring that control channel dead. When set to a non-zero value less than or equal …

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.629.10.5.1.1.1 (dcLmpProductEntry)
Node code
33
Node name
dcLmpProductExtendedHelloDeadIvl
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.629.10.5.1.1.1.33
URN notation
urn:oid:1.3.6.1.4.1.629.10.5.1.1.1.33
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 629 10 5 1 1 1 33}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nbase(629) opx(10) dcLmp(5) dcLmpObjects(1) dcLmpProductTable(1) dcLmpProductEntry(1) dcLmpProductExtendedHelloDeadIvl(33)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nbs(629) opx(10) dcLmp(5) dcLmpObjects(1) dcLmpProductTable(1) dcLmpProductEntry(1) dcLmpProductExtendedHelloDeadIvl(33)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nbase(629) opx(10) dcLmp(5) dcLmpObjects(1) dcLmpProductTable(1) dcLmpProductEntry(1) dcLmpProductExtendedHelloDeadIvl(33)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nbs(629) opx(10) dcLmp(5) dcLmpObjects(1) dcLmpProductTable(1) dcLmpProductEntry(1) dcLmpProductExtendedHelloDeadIvl(33)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nbase(629) opx(10) dcLmp(5) dcLmpObjects(1) dcLmpProductTable(1) dcLmpProductEntry(1) dcLmpProductExtendedHelloDeadIvl(33)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nbs(629) opx(10) dcLmp(5) dcLmpObjects(1) dcLmpProductTable(1) dcLmpProductEntry(1) dcLmpProductExtendedHelloDeadIvl(33)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nbase(629) opx(10) dcLmp(5) dcLmpObjects(1) dcLmpProductTable(1) dcLmpProductEntry(1) dcLmpProductExtendedHelloDeadIvl(33)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nbs(629) opx(10) dcLmp(5) dcLmpObjects(1) dcLmpProductTable(1) dcLmpProductEntry(1) dcLmpProductExtendedHelloDeadIvl(33)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) nbase(629) opx(10) dcLmp(5) dcLmpObjects(1) dcLmpProductTable(1) dcLmpProductEntry(1) dcLmpProductExtendedHelloDeadIvl(33)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) nbs(629) opx(10) dcLmp(5) dcLmpObjects(1) dcLmpProductTable(1) dcLmpProductEntry(1) dcLmpProductExtendedHelloDeadIvl(33)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) nbase(629) opx(10) dcLmp(5) dcLmpObjects(1) dcLmpProductTable(1) dcLmpProductEntry(1) dcLmpProductExtendedHelloDeadIvl(33)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) nbs(629) opx(10) dcLmp(5) dcLmpObjects(1) dcLmpProductTable(1) dcLmpProductEntry(1) dcLmpProductExtendedHelloDeadIvl(33)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) nbase(629) opx(10) dcLmp(5) dcLmpObjects(1) dcLmpProductTable(1) dcLmpProductEntry(1) dcLmpProductExtendedHelloDeadIvl(33)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) nbs(629) opx(10) dcLmp(5) dcLmpObjects(1) dcLmpProductTable(1) dcLmpProductEntry(1) dcLmpProductExtendedHelloDeadIvl(33)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) nbase(629) opx(10) dcLmp(5) dcLmpObjects(1) dcLmpProductTable(1) dcLmpProductEntry(1) dcLmpProductExtendedHelloDeadIvl(33)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) nbs(629) opx(10) dcLmp(5) dcLmpObjects(1) dcLmpProductTable(1) dcLmpProductEntry(1) dcLmpProductExtendedHelloDeadIvl(33)}
  • Additional combinations skipped.
OID-IRI notation
  • /1/3/6/1/4/1/629/10/5/1/1/1/33
  • /ISO/Identified-Organization/6/1/4/1/629/10/5/1/1/1/33
  • /ISO/3/6/1/4/1/629/10/5/1/1/1/33
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/nbase/opx/dcLmp/dcLmpObjects/dcLmpProductTable/dcLmpProductEntry/dcLmpProductExtendedHelloDeadIvl
  • /iso/identified-organization/dod/internet/private/enterprise/nbs/opx/dcLmp/dcLmpObjects/dcLmpProductTable/dcLmpProductEntry/dcLmpProductExtendedHelloDeadIvl
  • /iso/identified-organization/dod/internet/private/enterprises/nbase/opx/dcLmp/dcLmpObjects/dcLmpProductTable/dcLmpProductEntry/dcLmpProductExtendedHelloDeadIvl
  • /iso/identified-organization/dod/internet/private/enterprises/nbs/opx/dcLmp/dcLmpObjects/dcLmpProductTable/dcLmpProductEntry/dcLmpProductExtendedHelloDeadIvl
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/nbase/opx/dcLmp/dcLmpObjects/dcLmpProductTable/dcLmpProductEntry/dcLmpProductExtendedHelloDeadIvl
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/nbs/opx/dcLmp/dcLmpObjects/dcLmpProductTable/dcLmpProductEntry/dcLmpProductExtendedHelloDeadIvl
  • /iso/identified-organization/dod/internet/private/vendor-objects/nbase/opx/dcLmp/dcLmpObjects/dcLmpProductTable/dcLmpProductEntry/dcLmpProductExtendedHelloDeadIvl
  • /iso/identified-organization/dod/internet/private/vendor-objects/nbs/opx/dcLmp/dcLmpObjects/dcLmpProductTable/dcLmpProductEntry/dcLmpProductExtendedHelloDeadIvl
  • /iso/org/dod/internet/private/enterprise/nbase/opx/dcLmp/dcLmpObjects/dcLmpProductTable/dcLmpProductEntry/dcLmpProductExtendedHelloDeadIvl
  • /iso/org/dod/internet/private/enterprise/nbs/opx/dcLmp/dcLmpObjects/dcLmpProductTable/dcLmpProductEntry/dcLmpProductExtendedHelloDeadIvl
  • /iso/org/dod/internet/private/enterprises/nbase/opx/dcLmp/dcLmpObjects/dcLmpProductTable/dcLmpProductEntry/dcLmpProductExtendedHelloDeadIvl
  • /iso/org/dod/internet/private/enterprises/nbs/opx/dcLmp/dcLmpObjects/dcLmpProductTable/dcLmpProductEntry/dcLmpProductExtendedHelloDeadIvl
  • /iso/org/dod/internet/private/ldap-enterprise/nbase/opx/dcLmp/dcLmpObjects/dcLmpProductTable/dcLmpProductEntry/dcLmpProductExtendedHelloDeadIvl
  • /iso/org/dod/internet/private/ldap-enterprise/nbs/opx/dcLmp/dcLmpObjects/dcLmpProductTable/dcLmpProductEntry/dcLmpProductExtendedHelloDeadIvl
  • /iso/org/dod/internet/private/vendor-objects/nbase/opx/dcLmp/dcLmpObjects/dcLmpProductTable/dcLmpProductEntry/dcLmpProductExtendedHelloDeadIvl
  • /iso/org/dod/internet/private/vendor-objects/nbs/opx/dcLmp/dcLmpObjects/dcLmpProductTable/dcLmpProductEntry/dcLmpProductExtendedHelloDeadIvl
  • Additional combinations skipped.

SNMP properties

Value type
Unsigned32
Units
milliseconds
Maximum access defined by MIB
read-create
Status in MIB
current
Default value
0
Allowed ranges
0–4294967295

Using this OID with SNMP

At least one MIB declaration places this object in a table row. A value belongs to a row instance; its suffix depends on the row's INDEX or AUGMENTS definition. The index encoding is not inferred here.

Published row index: dcLmpProductIndex.

snmpwalk [connection options] DEVICE .1.3.6.1.4.1.629.10.5.1.1.1.33

Replace the placeholders with your connection and authentication options. Available permissions and device support can differ from the MIB.

Properties come from available MIB definitions. Actual device support and access can differ. See source records below for original files and qualifications.

The displayed source records contain one distinct definition. Compare its source records.

dcLmpProductExtendedHelloDeadIvl OBJECT-TYPE 
      SYNTAX      Unsigned32 (0..4294967295)
      UNITS       "milliseconds"
      MAX-ACCESS  read-create
      STATUS      current
      DESCRIPTION
        "When set to a non-zero value greater than                  
         lmpCcHelloDeadIntervalNegotiated, the object overrides the 
         value of lmpCcHelloDeadIntervalNegotiated for a control    
         channel to indicate how long the device should wait (in    
         milliseconds) before declaring that control channel dead.  
                                                                    
         When set to a non-zero value less than or equal to         
         lmpCcHelloDeadIntervalNegotiated for a control channel,    
         this field has no effect for that control channel.         
                                                                    
         When set to zero (the default value), this field is not    
         used by LMP.                                               
                                                                    
         Use of this object is strongly discouraged because not     
         detecting control channel failure in a timely manner can   
         cause negative effects.  For example, as follows.          
                                                                    
         -  BeginVerify messages will continue to be retried after  
            lmpCcHelloDeadIntervalNegotiated has expired, which     
            will block anonymous verification of TELs with other    
            neighbors.  On hardware with limited termination        
            capability for sending Test messages, this behaviour    
            might block all link verification to all neighbors, not 
            just anonymous verification.                            
                                                                    
         -  If there are multiple control channels to a neighbor    
            and the primary control channel fails, DC-LMP will      
            continue using the failed control channel to send all   
            message types that are not control channel specific,    
            rather than another control channel becoming the        
            primary control channel.  Hence the neighbor will not   
            receive any of these messages.                          
                                                                    
         -  Hello messages, and message types that are not control  
            channel specific, continue to be sent over the control  
            channel after the lmpCcHelloDeadIntervalNegotiated has  
            expired.  This behavior does not conform to RFC 4204.   
                                                                    
         However, this object can be set to a non-zero value when   
                                                                    
         -  the local node wishes to support LMP Graceful Restart   
            procedures for neighbors that restart and                   
         -  LMP neighbors may take longer to restart than the       
            maximum possible value for the                          
            lmpCcHelloDeadIntervalNegotiated.                       
                                                                    
         The object should be set to a value that is as small as     
         possible because of the negative effects listed above.     
                                                                    
         This field may be changed at any time.  The new value is   
         used the next time that the HelloDead timer is started for 
         each Control Channel."                                      
      DEFVAL { 0 }
     ::= { dcLmpProductEntry 33 }

Meaning

Descriptions

1 unique

Identical descriptions are grouped. Different wording and device-specific notes are retained.

When set to a non-zero value greater than lmpCcHelloDeadIntervalNegotiated, the object overrides the value of lmpCcHelloDeadIntervalNegotiated for a control channel to indicate how long the device should wait (in milliseconds) before declaring that control channel dead. When set to a non-zero value less than or equal to lmpCcHelloDeadIntervalNegotiated for a control channel, this field has no effect for that control channel. When set to zero (the default value), this field is not used by LMP. Use of this object is strongly discouraged because not detecting control channel failure in a timely manner can cause negative effects. For example, as follows. - BeginVerify messages will continue to be retried after lmpCcHelloDeadIntervalNegotiated has expired, which will block anonymous verification of TELs with other neighbors. On hardware with limited termination capability for sending Test messages, this behaviour might block all link verification to all neighbors, not just anonymous verification. - If there are multiple control channels to a neighbor and the primary control channel fails, DC-LMP will continue using the failed control channel to send all message types that are not control channel specific, rather than another control channel becoming the primary control channel. Hence the neighbor will not receive any of these messages. - Hello messages, and message types that are not control channel specific, continue to be sent over the control channel after the lmpCcHelloDeadIntervalNegotiated has expired. This behavior does not conform to RFC 4204. However, this object can be set to a non-zero value when - the local node wishes to support LMP Graceful Restart procedures for neighbors that restart and - LMP neighbors may take longer to restart than the maximum possible value for the lmpCcHelloDeadIntervalNegotiated. The object should be set to a value that is as small as possible because of the negative effects listed above. This field may be changed at any time. The new value is used the next time that the HelloDead timer is started for each Control Channel.

Sources for this description

Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)

See 1 matching source record

Evidence

Source records

1 records

Matching descriptions are grouped; open a group to compare definitions and supporting files.

Records for description 1Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)1 record · 1 source

Description 1

dcLmpProductExtendedHelloDeadIvl · currentMultiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)1 source

Status in source: current.

Names: dcLmpProductExtendedHelloDeadIvl

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "dcLmpProductExtendedHelloDeadIvl",
    "OBJECT-TYPE",
    "SYNTAX",
    "Unsigned32",
    "(",
    "0",
    ".",
    ".",
    "4294967295",
    ")",
    "UNITS",
    [
      "literal",
      "226d696c6c697365636f6e647322"
    ],
    "MAX-ACCESS",
    "read-create",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"When set to a non-zero value greater than lmpCcHelloDeadIntervalNegotiated, the object overrides the value of lmpCcHelloDeadIntervalNegotiated for a control channel to indicate how long the device should wait (in milliseconds) before declaring that control channel dead. When set to a non-zero value less than or equal to lmpCcHelloDeadIntervalNegotiated for a control channel, this field has no effect for that control channel. When set to zero (the default value), this field is not used by LMP. Use of this object is strongly discouraged because not detecting control channel failure in a timely manner can cause negative effects. For example, as follows. - BeginVerify messages will continue to be retried after lmpCcHelloDeadIntervalNegotiated has expired, which will block anonymous verification of TELs with other neighbors. On hardware with limited termination capability for sending Test messages, this behaviour might block all link verification to all neighbors, not just anonymous verification. - If there are multiple control channels to a neighbor and the primary control channel fails, DC-LMP will continue using the failed control channel to send all message types that are not control channel specific, rather than another control channel becoming the primary control channel. Hence the neighbor will not receive any of these messages. - Hello messages, and message types that are not control channel specific, continue to be sent over the control channel after the lmpCcHelloDeadIntervalNegotiated has expired. This behavior does not conform to RFC 4204. However, this object can be set to a non-zero value when - the local node wishes to support LMP Graceful Restart procedures for neighbors that restart and - LMP neighbors may take longer to restart than the maximum possible value for the lmpCcHelloDeadIntervalNegotiated. The object should be set to a value that is as small as possible because of the negative effects listed above. This field may be changed at any time. The new value is used the next time that the HelloDead timer is started for each Control Channel.\"",
    "DEFVAL",
    "{",
    "0",
    "}",
    "::=",
    "{",
    "dcLmpProductEntry",
    "33",
    "}"
  ],
  "syntax_tree": [
    [
      "ApplicationSyntax",
      "Unsigned32",
      [
        "integerSubType",
        [
          [
            0,
            4294967295
          ]
        ]
      ]
    ],
    [
      "UNITS",
      "milliseconds"
    ],
    [
      "MaxAccessPart",
      "read-create"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "When set to a non-zero value greater than lmpCcHelloDeadIntervalNegotiated, the object overrides the value of lmpCcHelloDeadIntervalNegotiated for a control channel to indicate how long the device should wait (in milliseconds) before declaring that control channel dead. When set to a non-zero value less than or equal to lmpCcHelloDeadIntervalNegotiated for a control channel, this field has no effect for that control channel. When set to zero (the default value), this field is not used by LMP. Use of this object is strongly discouraged because not detecting control channel failure in a timely manner can cause negative effects. For example, as follows. - BeginVerify messages will continue to be retried after lmpCcHelloDeadIntervalNegotiated has expired, which will block anonymous verification of TELs with other neighbors. On hardware with limited termination capability for sending Test messages, this behaviour might block all link verification to all neighbors, not just anonymous verification. - If there are multiple control channels to a neighbor and the primary control channel fails, DC-LMP will continue using the failed control channel to send all message types that are not control channel specific, rather than another control channel becoming the primary control channel. Hence the neighbor will not receive any of these messages. - Hello messages, and message types that are not control channel specific, continue to be sent over the control channel after the lmpCcHelloDeadIntervalNegotiated has expired. This behavior does not conform to RFC 4204. However, this object can be set to a non-zero value when - the local node wishes to support LMP Graceful Restart procedures for neighbors that restart and - LMP neighbors may take longer to restart than the maximum possible value for the lmpCcHelloDeadIntervalNegotiated. The object should be set to a value that is as small as possible because of the negative effects listed above. This field may be changed at any time. The new value is used the next time that the HelloDead timer is started for each Control Channel."
    ],
    null,
    null,
    null,
    [
      "DEFVAL",
      0
    ]
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.629)

Rotenstein Sergiu

Siblings (37)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.629.10.5.1.1.1.1 dcLmpProductIndex00
1.3.6.1.4.1.629.10.5.1.1.1.2 dcLmpProductNodeId00
1.3.6.1.4.1.629.10.5.1.1.1.3 dcLmpProductSocketIfIndex00
1.3.6.1.4.1.629.10.5.1.1.1.4 dcLmpProductSocketBufPoolSize00
1.3.6.1.4.1.629.10.5.1.1.1.5 dcLmpProductDLMIBufPoolSize00
1.3.6.1.4.1.629.10.5.1.1.1.6 dcLmpProductResendInterval00
1.3.6.1.4.1.629.10.5.1.1.1.7 dcLmpProductResendDelta00
1.3.6.1.4.1.629.10.5.1.1.1.8 dcLmpProductHelloIntvalDflt00
1.3.6.1.4.1.629.10.5.1.1.1.9 dcLmpProductHelloIntvalDfltMin00
1.3.6.1.4.1.629.10.5.1.1.1.10 dcLmpProductHelloIntvalDfltMax00
1.3.6.1.4.1.629.10.5.1.1.1.11 dcLmpProductHelloDeadIvlDflt00
1.3.6.1.4.1.629.10.5.1.1.1.12 dcLmpProductHelloDeadIvlDfltMin00
1.3.6.1.4.1.629.10.5.1.1.1.13 dcLmpProductHelloDeadIvlDfltMax00
1.3.6.1.4.1.629.10.5.1.1.1.14 dcLmpProductLinkVerifyInterval00
1.3.6.1.4.1.629.10.5.1.1.1.15 dcLmpProductLnkMismatchNotifEnbl00
1.3.6.1.4.1.629.10.5.1.1.1.16 dcLmpProductUnprotNotifEnable00
1.3.6.1.4.1.629.10.5.1.1.1.17 dcLmpProductCcUpDownNotifEnable00
1.3.6.1.4.1.629.10.5.1.1.1.18 dcLmpProductTeLinkNotifEnable00
1.3.6.1.4.1.629.10.5.1.1.1.19 dcLmpProductTelCorrNotifEnable00
1.3.6.1.4.1.629.10.5.1.1.1.20 dcLmpProductDataLinkNotifEnable00
1.3.6.1.4.1.629.10.5.1.1.1.21 dcLmpProductNeighborAutoGen00
1.3.6.1.4.1.629.10.5.1.1.1.22 dcLmpProductTeLinkAutoLink00
1.3.6.1.4.1.629.10.5.1.1.1.23 dcLmpProductUniRepeatInterval00
1.3.6.1.4.1.629.10.5.1.1.1.24 dcLmpProductUniCompletionIntval00
1.3.6.1.4.1.629.10.5.1.1.1.25 dcLmpDestIpAddrAsUni00
1.3.6.1.4.1.629.10.5.1.1.1.26 dcLmpProductRestarted00
1.3.6.1.4.1.629.10.5.1.1.1.27 dcLmpProductAdminStatus00
1.3.6.1.4.1.629.10.5.1.1.1.28 dcLmpProductOperStatus00
1.3.6.1.4.1.629.10.5.1.1.1.29 dcLmpProductRowStatus00
1.3.6.1.4.1.629.10.5.1.1.1.30 dcLmpProductWdmMode00
1.3.6.1.4.1.629.10.5.1.1.1.31 dcLmpProductWdmRole00
1.3.6.1.4.1.629.10.5.1.1.1.32 dcLmpSrcIpAddrNodeID00
1.3.6.1.4.1.629.10.5.1.1.1.34 mrvLmpProductTestPort00
1.3.6.1.4.1.629.10.5.1.1.1.35 mrvLmpProductTestWavelength00
1.3.6.1.4.1.629.10.5.1.1.1.36 mrvLmpProductLinkVerifyDeadInterval00
1.3.6.1.4.1.629.10.5.1.1.1.37 mrvLmpProductAttenWithEdfa00
1.3.6.1.4.1.629.10.5.1.1.1.38 mrvLmpProductAttenWithoutEdfa00