Reference record for OID 1.3.6.1.4.1.51735.1.34.1.2.3.4.1

Parent
1.3.6.1.4.1.51735.1.34.1.2.3.4 (hiscomLldpConfigMedGlobal)
Node code
1
Node name
hiscomLldpConfigMedGlobalFastRepeatCount
Numeric OID
1.3.6.1.4.1.51735.1.34.1.2.3.4.1
URN notation
urn:oid:1.3.6.1.4.1.51735.1.34.1.2.3.4.1
ASN.1 notation

{1 3 6 1 4 1 51735 1 34 1 2 3 4 1}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) hiscom(51735) hiscomSwitchMgmt(1) hiscomLldpMib(34) hiscomLldpMibObjects(1) hiscomLldpConfig(2) hiscomLldpConfigMed(3) hiscomLldpConfigMedGlobal(4) hiscomLldpConfigMedGlobalFastRepeatCount(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) hiscom(51735) hiscomSwitchMgmt(1) hiscomLldpMib(34) hiscomLldpMibObjects(1) hiscomLldpConfig(2) hiscomLldpConfigMed(3) hiscomLldpConfigMedGlobal(4) hiscomLldpConfigMedGlobalFastRepeatCount(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) hiscom(51735) hiscomSwitchMgmt(1) hiscomLldpMib(34) hiscomLldpMibObjects(1) hiscomLldpConfig(2) hiscomLldpConfigMed(3) hiscomLldpConfigMedGlobal(4) hiscomLldpConfigMedGlobalFastRepeatCount(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) hiscom(51735) hiscomSwitchMgmt(1) hiscomLldpMib(34) hiscomLldpMibObjects(1) hiscomLldpConfig(2) hiscomLldpConfigMed(3) hiscomLldpConfigMedGlobal(4) hiscomLldpConfigMedGlobalFastRepeatCount(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) hiscom(51735) hiscomSwitchMgmt(1) hiscomLldpMib(34) hiscomLldpMibObjects(1) hiscomLldpConfig(2) hiscomLldpConfigMed(3) hiscomLldpConfigMedGlobal(4) hiscomLldpConfigMedGlobalFastRepeatCount(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) hiscom(51735) hiscomSwitchMgmt(1) hiscomLldpMib(34) hiscomLldpMibObjects(1) hiscomLldpConfig(2) hiscomLldpConfigMed(3) hiscomLldpConfigMedGlobal(4) hiscomLldpConfigMedGlobalFastRepeatCount(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) hiscom(51735) hiscomSwitchMgmt(1) hiscomLldpMib(34) hiscomLldpMibObjects(1) hiscomLldpConfig(2) hiscomLldpConfigMed(3) hiscomLldpConfigMedGlobal(4) hiscomLldpConfigMedGlobalFastRepeatCount(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) hiscom(51735) hiscomSwitchMgmt(1) hiscomLldpMib(34) hiscomLldpMibObjects(1) hiscomLldpConfig(2) hiscomLldpConfigMed(3) hiscomLldpConfigMedGlobal(4) hiscomLldpConfigMedGlobalFastRepeatCount(1)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) hiscom(51735) hiscomSwitchMgmt(1) hiscomLldpMib(34) hiscomLldpMibObjects(1) hiscomLldpConfig(2) hiscomLldpConfigMed(3) hiscomLldpConfigMedGlobal(4) hiscomLldpConfigMedGlobalFastRepeatCount(1)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) hiscom(51735) hiscomSwitchMgmt(1) hiscomLldpMib(34) hiscomLldpMibObjects(1) hiscomLldpConfig(2) hiscomLldpConfigMed(3) hiscomLldpConfigMedGlobal(4) hiscomLldpConfigMedGlobalFastRepeatCount(1)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) hiscom(51735) hiscomSwitchMgmt(1) hiscomLldpMib(34) hiscomLldpMibObjects(1) hiscomLldpConfig(2) hiscomLldpConfigMed(3) hiscomLldpConfigMedGlobal(4) hiscomLldpConfigMedGlobalFastRepeatCount(1)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) hiscom(51735) hiscomSwitchMgmt(1) hiscomLldpMib(34) hiscomLldpMibObjects(1) hiscomLldpConfig(2) hiscomLldpConfigMed(3) hiscomLldpConfigMedGlobal(4) hiscomLldpConfigMedGlobalFastRepeatCount(1)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) hiscom(51735) hiscomSwitchMgmt(1) hiscomLldpMib(34) hiscomLldpMibObjects(1) hiscomLldpConfig(2) hiscomLldpConfigMed(3) hiscomLldpConfigMedGlobal(4) hiscomLldpConfigMedGlobalFastRepeatCount(1)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) hiscom(51735) hiscomSwitchMgmt(1) hiscomLldpMib(34) hiscomLldpMibObjects(1) hiscomLldpConfig(2) hiscomLldpConfigMed(3) hiscomLldpConfigMedGlobal(4) hiscomLldpConfigMedGlobalFastRepeatCount(1)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) hiscom(51735) hiscomSwitchMgmt(1) hiscomLldpMib(34) hiscomLldpMibObjects(1) hiscomLldpConfig(2) hiscomLldpConfigMed(3) hiscomLldpConfigMedGlobal(4) hiscomLldpConfigMedGlobalFastRepeatCount(1)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) hiscom(51735) hiscomSwitchMgmt(1) hiscomLldpMib(34) hiscomLldpMibObjects(1) hiscomLldpConfig(2) hiscomLldpConfigMed(3) hiscomLldpConfigMedGlobal(4) hiscomLldpConfigMedGlobalFastRepeatCount(1)}
OID-IRI notation
  • /1/3/6/1/4/1/51735/1/34/1/2/3/4/1
  • /ISO/Identified-Organization/6/1/4/1/51735/1/34/1/2/3/4/1
  • /ISO/3/6/1/4/1/51735/1/34/1/2/3/4/1
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/hiscom/hiscomSwitchMgmt/hiscomLldpMib/hiscomLldpMibObjects/hiscomLldpConfig/hiscomLldpConfigMed/hiscomLldpConfigMedGlobal/hiscomLldpConfigMedGlobalFastRepeatCount
  • /iso/identified-organization/dod/internet/private/enterprises/hiscom/hiscomSwitchMgmt/hiscomLldpMib/hiscomLldpMibObjects/hiscomLldpConfig/hiscomLldpConfigMed/hiscomLldpConfigMedGlobal/hiscomLldpConfigMedGlobalFastRepeatCount
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/hiscom/hiscomSwitchMgmt/hiscomLldpMib/hiscomLldpMibObjects/hiscomLldpConfig/hiscomLldpConfigMed/hiscomLldpConfigMedGlobal/hiscomLldpConfigMedGlobalFastRepeatCount
  • /iso/identified-organization/dod/internet/private/vendor-objects/hiscom/hiscomSwitchMgmt/hiscomLldpMib/hiscomLldpMibObjects/hiscomLldpConfig/hiscomLldpConfigMed/hiscomLldpConfigMedGlobal/hiscomLldpConfigMedGlobalFastRepeatCount
  • /iso/org/dod/internet/private/enterprise/hiscom/hiscomSwitchMgmt/hiscomLldpMib/hiscomLldpMibObjects/hiscomLldpConfig/hiscomLldpConfigMed/hiscomLldpConfigMedGlobal/hiscomLldpConfigMedGlobalFastRepeatCount
  • /iso/org/dod/internet/private/enterprises/hiscom/hiscomSwitchMgmt/hiscomLldpMib/hiscomLldpMibObjects/hiscomLldpConfig/hiscomLldpConfigMed/hiscomLldpConfigMedGlobal/hiscomLldpConfigMedGlobalFastRepeatCount
  • /iso/org/dod/internet/private/ldap-enterprise/hiscom/hiscomSwitchMgmt/hiscomLldpMib/hiscomLldpMibObjects/hiscomLldpConfig/hiscomLldpConfigMed/hiscomLldpConfigMedGlobal/hiscomLldpConfigMedGlobalFastRepeatCount
  • /iso/org/dod/internet/private/vendor-objects/hiscom/hiscomSwitchMgmt/hiscomLldpMib/hiscomLldpMibObjects/hiscomLldpConfig/hiscomLldpConfigMed/hiscomLldpConfigMedGlobal/hiscomLldpConfigMedGlobalFastRepeatCount
  • /iso/iso-identified-organization/dod/internet/private/enterprise/hiscom/hiscomSwitchMgmt/hiscomLldpMib/hiscomLldpMibObjects/hiscomLldpConfig/hiscomLldpConfigMed/hiscomLldpConfigMedGlobal/hiscomLldpConfigMedGlobalFastRepeatCount
  • /iso/iso-identified-organization/dod/internet/private/enterprises/hiscom/hiscomSwitchMgmt/hiscomLldpMib/hiscomLldpMibObjects/hiscomLldpConfig/hiscomLldpConfigMed/hiscomLldpConfigMedGlobal/hiscomLldpConfigMedGlobalFastRepeatCount
  • /iso/iso-identified-organization/dod/internet/private/ldap-enterprise/hiscom/hiscomSwitchMgmt/hiscomLldpMib/hiscomLldpMibObjects/hiscomLldpConfig/hiscomLldpConfigMed/hiscomLldpConfigMedGlobal/hiscomLldpConfigMedGlobalFastRepeatCount
  • /iso/iso-identified-organization/dod/internet/private/vendor-objects/hiscom/hiscomSwitchMgmt/hiscomLldpMib/hiscomLldpMibObjects/hiscomLldpConfig/hiscomLldpConfigMed/hiscomLldpConfigMedGlobal/hiscomLldpConfigMedGlobalFastRepeatCount
  • /iso/iso-organization/dod/internet/private/enterprise/hiscom/hiscomSwitchMgmt/hiscomLldpMib/hiscomLldpMibObjects/hiscomLldpConfig/hiscomLldpConfigMed/hiscomLldpConfigMedGlobal/hiscomLldpConfigMedGlobalFastRepeatCount
  • /iso/iso-organization/dod/internet/private/enterprises/hiscom/hiscomSwitchMgmt/hiscomLldpMib/hiscomLldpMibObjects/hiscomLldpConfig/hiscomLldpConfigMed/hiscomLldpConfigMedGlobal/hiscomLldpConfigMedGlobalFastRepeatCount
  • /iso/iso-organization/dod/internet/private/ldap-enterprise/hiscom/hiscomSwitchMgmt/hiscomLldpMib/hiscomLldpMibObjects/hiscomLldpConfig/hiscomLldpConfigMed/hiscomLldpConfigMedGlobal/hiscomLldpConfigMedGlobalFastRepeatCount
  • /iso/iso-organization/dod/internet/private/vendor-objects/hiscom/hiscomSwitchMgmt/hiscomLldpMib/hiscomLldpMibObjects/hiscomLldpConfig/hiscomLldpConfigMed/hiscomLldpConfigMedGlobal/hiscomLldpConfigMedGlobalFastRepeatCount

Descriptions

hiscomLldpConfigMedGlobalFastRepeatCount — Belden, GarrettCom and Hirschmann IT official standalone MIBs

Number of times to repeat LLDP frame transmission at fast start Rapid startup and Emergency Call Service Location Identification Discovery of endpoints is a critically important aspect of VoIP systems in general. In addition, it is best to advertise only those pieces of information which are specifically relevant to particular endpoint types (for example only advertise the voice network policy to permitted voice-capable devices), both in order to conserve the limited LLDPU space and to reduce security and system integrity issues that can come with inappropriate knowledge of the network policy. With this in mind LLDP-MED defines an LLDP-MED Fast Start interaction between the protocol and the application layers on top of the protocol, in order to achieve these related properties. Initially, a Network Connectivity Device will only transmit LLDP TLVs in an LLDPDU. Only after an LLDP-MED Endpoint Device is detected, will an LLDP-MED capable Network Connectivity Device start to advertise LLDP-MED TLVs in outgoing LLDPDUs on the associated port. The LLDP-MED application will temporarily speed up the transmission of the LLDPDU to start within a second, when a new LLDP-MED neighbor has been detected in order share LLDP-MED information as fast as possible to new neighbors. Because there is a risk of an LLDP frame being lost during transmission between neighbors, it is recommended to repeat the fast start transmission multiple times to increase the possibility of the neighbors receiving the LLDP frame. With fast start repeat count it is possible to specify the number of times the fast start transmission would be repeated. The recommended value is 4 times, given that 4 LLDP frames with a 1 second interval will be transmitted, when an LLDP frame with new information is received. It should be noted that LLDP-MED and the LLDP-MED Fast Start mechanism is only intended to run on links between LLDP-MED Network Connectivity Devices and Endpoint Devices, and as such does not apply to links between LAN infrastructure elements, including Network Connectivity Devices, or other types of links.

Source records

hiscomLldpConfigMedGlobalFastRepeatCount

Status in source: current.

Names: hiscomLldpConfigMedGlobalFastRepeatCount

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "hiscomLldpConfigMedGlobalFastRepeatCount",
    "OBJECT-TYPE",
    "SYNTAX",
    "HISCOMUnsigned8",
    "(",
    "1",
    ".",
    ".",
    "10",
    ")",
    "MAX-ACCESS",
    "read-write",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"Number of times to repeat LLDP frame transmission at fast start Rapid startup and Emergency Call Service Location Identification Discovery of endpoints is a critically important aspect of VoIP systems in general. In addition, it is best to advertise only those pieces of information which are specifically relevant to particular endpoint types (for example only advertise the voice network policy to permitted voice-capable devices), both in order to conserve the limited LLDPU space and to reduce security and system integrity issues that can come with inappropriate knowledge of the network policy. With this in mind LLDP-MED defines an LLDP-MED Fast Start interaction between the protocol and the application layers on top of the protocol, in order to achieve these related properties. Initially, a Network Connectivity Device will only transmit LLDP TLVs in an LLDPDU. Only after an LLDP-MED Endpoint Device is detected, will an LLDP-MED capable Network Connectivity Device start to advertise LLDP-MED TLVs in outgoing LLDPDUs on the associated port. The LLDP-MED application will temporarily speed up the transmission of the LLDPDU to start within a second, when a new LLDP-MED neighbor has been detected in order share LLDP-MED information as fast as possible to new neighbors. Because there is a risk of an LLDP frame being lost during transmission between neighbors, it is recommended to repeat the fast start transmission multiple times to increase the possibility of the neighbors receiving the LLDP frame. With fast start repeat count it is possible to specify the number of times the fast start transmission would be repeated. The recommended value is 4 times, given that 4 LLDP frames with a 1 second interval will be transmitted, when an LLDP frame with new information is received. It should be noted that LLDP-MED and the LLDP-MED Fast Start mechanism is only intended to run on links between LLDP-MED Network Connectivity Devices and Endpoint Devices, and as such does not apply to links between LAN infrastructure elements, including Network Connectivity Devices, or other types of links.\"",
    "::=",
    "{",
    "hiscomLldpConfigMedGlobal",
    "1",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "HISCOMUnsigned8",
      [
        "integerSubType",
        [
          [
            1,
            10
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "Number of times to repeat LLDP frame transmission at fast start Rapid startup and Emergency Call Service Location Identification Discovery of endpoints is a critically important aspect of VoIP systems in general. In addition, it is best to advertise only those pieces of information which are specifically relevant to particular endpoint types (for example only advertise the voice network policy to permitted voice-capable devices), both in order to conserve the limited LLDPU space and to reduce security and system integrity issues that can come with inappropriate knowledge of the network policy. With this in mind LLDP-MED defines an LLDP-MED Fast Start interaction between the protocol and the application layers on top of the protocol, in order to achieve these related properties. Initially, a Network Connectivity Device will only transmit LLDP TLVs in an LLDPDU. Only after an LLDP-MED Endpoint Device is detected, will an LLDP-MED capable Network Connectivity Device start to advertise LLDP-MED TLVs in outgoing LLDPDUs on the associated port. The LLDP-MED application will temporarily speed up the transmission of the LLDPDU to start within a second, when a new LLDP-MED neighbor has been detected in order share LLDP-MED information as fast as possible to new neighbors. Because there is a risk of an LLDP frame being lost during transmission between neighbors, it is recommended to repeat the fast start transmission multiple times to increase the possibility of the neighbors receiving the LLDP frame. With fast start repeat count it is possible to specify the number of times the fast start transmission would be repeated. The recommended value is 4 times, given that 4 LLDP frames with a 1 second interval will be transmitted, when an LLDP frame with new information is received. It should be noted that LLDP-MED and the LLDP-MED Fast Start mechanism is only intended to run on links between LLDP-MED Network Connectivity Devices and Endpoint Devices, and as such does not apply to links between LAN infrastructure elements, including Network Connectivity Devices, or other types of links."
    ],
    null,
    null,
    null,
    null
  ]
}
  • Belden, GarrettCom and Hirschmann IT official standalone MIBs · Publisher's source file: HISCOM-LLDP-MIB.mib

    Module: HISCOM-LLDP-MIB

    Published definition
    hiscomLldpConfigMedGlobalFastRepeatCount OBJECT-TYPE
        SYNTAX      HISCOMUnsigned8 (1..10)
        MAX-ACCESS  read-write
        STATUS      current
        DESCRIPTION
            "Number of times to repeat LLDP frame transmission at fast start
             
             Rapid startup and Emergency Call Service Location Identification
             Discovery of endpoints is a critically important aspect of VoIP systems
             in general. In addition, it is best to advertise only those pieces of
             information which are specifically relevant to particular endpoint
             types (for example only advertise the voice network policy to permitted
             voice-capable devices), both in order to conserve the limited LLDPU
             space and to reduce security and system integrity issues that can come
             with inappropriate knowledge of the network policy.
             
             With this in mind LLDP-MED defines an LLDP-MED Fast Start interaction
             between the protocol and the application layers on top of the protocol,
             in order to achieve these related properties. Initially, a Network
             Connectivity Device will only transmit LLDP TLVs in an LLDPDU. Only
             after an LLDP-MED Endpoint Device is detected, will an LLDP-MED capable
             Network Connectivity Device start to advertise LLDP-MED TLVs in
             outgoing LLDPDUs on the associated port. The LLDP-MED application will
             temporarily speed up the transmission of the LLDPDU to start within a
             second, when a new LLDP-MED neighbor has been detected in order share
             LLDP-MED information as fast as possible to new neighbors.
             
             Because there is a risk of an LLDP frame being lost during transmission
             between neighbors, it is recommended to repeat the fast start
             transmission multiple times to increase the possibility of the
             neighbors receiving the LLDP frame. With fast start repeat count it is
             possible to specify the number of times the fast start transmission
             would be repeated. The recommended value is 4 times, given that 4 LLDP
             frames with a 1 second interval will be transmitted, when an LLDP frame
             with new information is received.
             
             It should be noted that LLDP-MED and the LLDP-MED Fast Start mechanism
             is only intended to run on links between LLDP-MED Network Connectivity
             Devices and Endpoint Devices, and as such does not apply to links
             between LAN infrastructure elements, including Network Connectivity
             Devices, or other types of links."
        ::= { hiscomLldpConfigMedGlobal 1 }
    Module imports
    {'HISCOM-TC': ['HISCOMDisplayString', 'HISCOMInteger64', 'HISCOMInterfaceIndex', 'HISCOMRowEditorState', 'HISCOMUnsigned16', 'HISCOMUnsigned64', 'HISCOMUnsigned8'], 'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'TruthValue'], 'HISCOM-SMI': ['hiscomSwitchMgmt'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'Integer32', 'Unsigned32'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP']}

    Related source files and packages:


    Source location: HISCOM-LLDP-MIB::hiscomLldpConfigMedGlobalFastRepeatCount.
    Source version and references

    Downloaded: 2026-10-24T12:48:04.691334+00:00.

Current Registration Authority (inferred from ancestor 1.3.6.1.4.1.51735)

Shanghai Hite-Belden Network Technology Co., Ltd.

Siblings (7)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.51735.1.34.1.2.3.4.2 hiscomLldpConfigMedGlobalLatitude00
1.3.6.1.4.1.51735.1.34.1.2.3.4.3 hiscomLldpConfigMedGlobalLongitude00
1.3.6.1.4.1.51735.1.34.1.2.3.4.4 hiscomLldpConfigMedGlobalAltitudeType00
1.3.6.1.4.1.51735.1.34.1.2.3.4.5 hiscomLldpConfigMedGlobalAltitude00
1.3.6.1.4.1.51735.1.34.1.2.3.4.6 hiscomLldpConfigMedGlobalElinAddr00
1.3.6.1.4.1.51735.1.34.1.2.3.4.7 hiscomLldpConfigMedGlobalDatum00
1.3.6.1.4.1.51735.1.34.1.2.3.4.8 hiscomLldpConfigMedGlobalCountryCode00